{"id":"CVE-2026-23394","aliases":["AZL-84053","BELL-CVE-2026-23394","DEBIAN-CVE-2026-23394","EUVD-2026-15396","GHSA-p5pc-67g7-qcv2","OESA-2026-1862","OESA-2026-1863","OESA-2026-1864","ROOT-OS-DEBIAN-12-CVE-2026-23394","ROOT-OS-UBUNTU-2404-CVE-2026-23394","SUSE-SU-2026:22742-1","SUSE-SU-2026:22769-1","SUSE-SU-2026:22812-1","SUSE-SU-2026:22835-1","UBUNTU-CVE-2026-23394","USN-8277-1","USN-8277-2","USN-8278-1","USN-8278-2","USN-8289-1","USN-8289-2","USN-8296-1","USN-8296-2","USN-8310-1","USN-8374-1","USN-8393-1","USN-8440-1","USN-8499-1","USN-8508-1","openSUSE-SU-2026:21388-1"],"status":"published","title":"af_unix: Give up GC if MSG_PEEK intervened.","description":"In the Linux kernel, the following vulnerability has been resolved:\n\naf_unix: Give up GC if MSG_PEEK intervened.\n\nIgor Ushakov reported that GC purged the receive queue of\nan alive socket due to a race with MSG_PEEK with a nice repro.\n\nThis is the exact same issue previously fixed by commit\ncbcf01128d0a (\"af_unix: fix garbage collect vs MSG_PEEK\").\n\nAfter GC was replaced with the current algorithm, the cited\ncommit removed the locking dance in unix_peek_fds() and\nreintroduced the same issue.\n\nThe problem is that MSG_PEEK bumps a file refcount without\ninteracting with GC.\n\nConsider an SCC containing sk-A and sk-B, where sk-A is\nclose()d but can be recv()ed via sk-B.\n\nThe bad thing happens if sk-A is recv()ed with MSG_PEEK from\nsk-B and sk-B is close()d while GC is checking unix_vertex_dead()\nfor sk-A and sk-B.\n\n  GC thread                    User thread\n  ---------                    -----------\n  unix_vertex_dead(sk-A)\n  -\u003e true   \u003c------.\n                    \\\n                     `------   recv(sk-B, MSG_PEEK)\n              invalidate !!    -\u003e sk-A's file refcount : 1 -\u003e 2\n\n                               close(sk-B)\n                               -\u003e sk-B's file refcount : 2 -\u003e 1\n  unix_vertex_dead(sk-B)\n  -\u003e true\n\nInitially, sk-A's file refcount is 1 by the inflight fd in sk-B\nrecvq.  GC thinks sk-A is dead because the file refcount is the\nsame as the number of its inflight fds.\n\nHowever, sk-A's file refcount is bumped silently by MSG_PEEK,\nwhich invalidates the previous evaluation.\n\nAt this moment, sk-B's file refcount is 2; one by the open fd,\nand one by the inflight fd in sk-A.  The subsequent close()\nreleases one refcount by the former.\n\nFinally, GC incorrectly concludes that both sk-A and sk-B are dead.\n\nOne option is to restore the locking dance in unix_peek_fds(),\nbut we can resolve this more elegantly thanks to the new algorithm.\n\nThe point is that the issue does not occur without the subsequent\nclose() and we actually do not need to synchronise MSG_PEEK with\nthe dead SCC detection.\n\nWhen the issue occurs, close() and GC touch the same file refcount.\nIf GC sees the refcount being decremented by close(), it can just\ngive up garbage-collecting the SCC.\n\nTherefore, we only need to signal the race during MSG_PEEK with\na proper memory barrier to make it visible to the GC.\n\nLet's use seqcount_t to notify GC when MSG_PEEK occurs and let\nit defer the SCC to the next run.\n\nThis way no locking is needed on the MSG_PEEK side, and we can\navoid imposing a penalty on every MSG_PEEK unnecessarily.\n\nNote that we can retry within unix_scc_dead() if MSG_PEEK is\ndetected, but we do not do so to avoid hung task splat from\nabusive MSG_PEEK calls.","severity":{"version":"3.1","score":4.7,"vector":"CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:H","level":"medium","assessor":"primary","from":"nvd"},"epss":{"day":"2026-11-11","score":0.00097,"percentile":0.00704,"model":"v2026.06.15"},"facts":{"in_kev":false,"known_exploited":false,"public_exploit":false,"fix_available":true},"cwes":["CWE-362"],"published":"2026-03-25T10:33:18Z","modified":"2026-11-11T09:39:30Z","fixes":[{"ecosystem":"Azure Linux:3","package":"kernel","fixed_in":["6.6.142.1-1"],"sources":["osv"]},{"ecosystem":"Alpaquita:23","package":"linux-lts","fixed_in":["6.1.189-r0"],"sources":["osv"]},{"ecosystem":"Alpaquita:25","package":"linux-lts","fixed_in":["6.12.92-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.183","6.6.142","6.12.92","6.18.23","6.19.10"],"sources":["osv"]},{"ecosystem":"Debian:12","package":"linux","fixed_in":["6.1.187-1"],"sources":["osv"]},{"ecosystem":"Debian:13","package":"linux","fixed_in":["6.12.94-1"],"sources":["osv"]},{"ecosystem":"Debian:14","package":"linux","fixed_in":["6.19.10-1"],"sources":["osv"]},{"ecosystem":"Root:Debian:12","package":"linux","fixed_in":["6.1.190-1.aikido.167"],"sources":["osv"]},{"ecosystem":"Root:Debian:12","package":"rootio-linux","fixed_in":["6.1.190-1.aikido.167"],"sources":["osv"]},{"ecosystem":"Root:Ubuntu:24.04","package":"linux","fixed_in":["6.8.0-149.149.aikido.91"],"sources":["osv"]},{"ecosystem":"Root:Ubuntu:24.04","package":"rootio-linux","fixed_in":["6.8.0-149.149.aikido.91"],"sources":["osv"]},{"ecosystem":"Ubuntu:22.04:LTS","package":"linux-aws-6.8","fixed_in":["6.8.0-1057.60~22.04.1"],"sources":["osv"]},{"ecosystem":"Ubuntu:22.04:LTS","package":"linux-azure-6.8","fixed_in":["6.8.0-1059.65~22.04.1"],"sources":["osv"]},{"ecosystem":"Ubuntu:22.04:LTS","package":"linux-azure-fde-6.8","fixed_in":["6.8.0-1058.65~22.04.1"],"sources":["osv"]},{"ecosystem":"Ubuntu:22.04:LTS","package":"linux-gcp-6.8","fixed_in":["6.8.0-1060.63~22.04.1"],"sources":["osv"]},{"ecosystem":"Ubuntu:22.04:LTS","package":"linux-hwe-6.8","fixed_in":["6.8.0-124.124~22.04.1"],"sources":["osv"]},{"ecosystem":"Ubuntu:22.04:LTS","package":"linux-ibm-6.8","fixed_in":["6.8.0-1055.56~22.04.1"],"sources":["osv"]},{"ecosystem":"Ubuntu:22.04:LTS","package":"linux-lowlatency-hwe-6.8","fixed_in":["6.8.0-117.117.1~22.04.1"],"sources":["osv"]},{"ecosystem":"Ubuntu:22.04:LTS","package":"linux-nvidia-6.8","fixed_in":["6.8.0-1054.57~22.04.1"],"sources":["osv"]},{"ecosystem":"Ubuntu:22.04:LTS","package":"linux-oracle-6.8","fixed_in":["6.8.0-1054.55~22.04.1"],"sources":["osv"]},{"ecosystem":"Ubuntu:22.04:LTS","package":"linux-riscv-6.8","fixed_in":["6.8.0-117.117~22.04.1"],"sources":["osv"]},{"ecosystem":"Ubuntu:Pro:Realtime:22.04:LTS","package":"linux-realtime-6.8","fixed_in":["6.8.1-1051.52~22.04.1"],"sources":["osv"]},{"ecosystem":"Ubuntu:24.04:LTS","package":"linux","fixed_in":["6.8.0-117.117"],"sources":["osv"]},{"ecosystem":"Ubuntu:24.04:LTS","package":"linux-aws","fixed_in":["6.8.0-1055.58"],"sources":["osv"]},{"ecosystem":"Ubuntu:24.04:LTS","package":"linux-aws-6.17","fixed_in":["6.17.0-1017.17~24.04.1"],"sources":["osv"]},{"ecosystem":"Ubuntu:24.04:LTS","package":"linux-azure","fixed_in":["6.8.0-1056.62"],"sources":["osv"]},{"ecosystem":"Ubuntu:24.04:LTS","package":"linux-azure-6.17","fixed_in":["6.17.0-1015.15~24.04.1"],"sources":["osv"]},{"ecosystem":"Ubuntu:24.04:LTS","package":"linux-azure-fde","fixed_in":["6.8.0-1058.65"],"sources":["osv"]},{"ecosystem":"Ubuntu:24.04:LTS","package":"linux-gcp","fixed_in":["6.8.0-1058.61"],"sources":["osv"]},{"ecosystem":"Ubuntu:24.04:LTS","package":"linux-gcp-6.17","fixed_in":["6.17.0-1018.19~24.04.1"],"sources":["osv"]},{"ecosystem":"Ubuntu:24.04:LTS","package":"linux-gke","fixed_in":["6.8.0-1054.60"],"sources":["osv"]},{"ecosystem":"Ubuntu:24.04:LTS","package":"linux-gkeop","fixed_in":["6.8.0-1041.44"],"sources":["osv"]},{"ecosystem":"Ubuntu:24.04:LTS","package":"linux-hwe-6.17","fixed_in":["6.17.0-29.29~24.04.1"],"sources":["osv"]},{"ecosystem":"Ubuntu:24.04:LTS","package":"linux-ibm","fixed_in":["6.8.0-1055.56"],"sources":["osv"]},{"ecosystem":"Ubuntu:24.04:LTS","package":"linux-lowlatency","fixed_in":["6.8.0-117.117.1"],"sources":["osv"]},{"ecosystem":"Ubuntu:24.04:LTS","package":"linux-nvidia","fixed_in":["6.8.0-1054.57"],"sources":["osv"]},{"ecosystem":"Ubuntu:24.04:LTS","package":"linux-nvidia-6.17","fixed_in":["6.17.0-1026.26"],"sources":["osv"]},{"ecosystem":"Ubuntu:24.04:LTS","package":"linux-nvidia-lowlatency","fixed_in":["6.8.0-1054.57.1"],"sources":["osv"]},{"ecosystem":"Ubuntu:24.04:LTS","package":"linux-nvidia-tegra","fixed_in":["6.8.0-1024.24"],"sources":["osv"]},{"ecosystem":"Ubuntu:24.04:LTS","package":"linux-oem-6.17","fixed_in":["6.17.0-1023.23"],"sources":["osv"]},{"ecosystem":"Ubuntu:24.04:LTS","package":"linux-oracle","fixed_in":["6.8.0-1054.55"],"sources":["osv"]},{"ecosystem":"Ubuntu:24.04:LTS","package":"linux-oracle-6.17","fixed_in":["6.17.0-1014.14~24.04.1"],"sources":["osv"]},{"ecosystem":"Ubuntu:24.04:LTS","package":"linux-raspi","fixed_in":["6.8.0-1056.60"],"sources":["osv"]},{"ecosystem":"Ubuntu:24.04:LTS","package":"linux-riscv-6.17","fixed_in":["6.17.0-29.29.1~24.04.1"],"sources":["osv"]},{"ecosystem":"Ubuntu:24.04:LTS","package":"linux-xilinx","fixed_in":["6.8.0-1032.33"],"sources":["osv"]},{"ecosystem":"Ubuntu:Nvidia-BlueField:24.04:LTS","package":"linux-bluefield","fixed_in":["6.8.0-1022.26"],"sources":["osv"]},{"ecosystem":"Ubuntu:Pro:Realtime:24.04:LTS","package":"linux-raspi-realtime","fixed_in":["6.8.0-2045.46"],"sources":["osv"]},{"ecosystem":"Ubuntu:Pro:Realtime:24.04:LTS","package":"linux-realtime","fixed_in":["6.8.1-1051.52"],"sources":["osv"]},{"ecosystem":"Ubuntu:Pro:Realtime:24.04:LTS","package":"linux-realtime-6.17","fixed_in":["6.17.0-1013.15~24.04.1"],"sources":["osv"]},{"ecosystem":"Ubuntu:Pro:FIPS-updates:24.04:LTS","package":"linux-aws-fips","fixed_in":["6.8.0-1055.58+fips1"],"sources":["osv"]},{"ecosystem":"Ubuntu:Pro:FIPS-updates:24.04:LTS","package":"linux-azure-fips","fixed_in":["6.8.0-1059.65+fips1"],"sources":["osv"]},{"ecosystem":"Ubuntu:Pro:FIPS-updates:24.04:LTS","package":"linux-fips","fixed_in":["6.8.0-116.116+fips1"],"sources":["osv"]},{"ecosystem":"Ubuntu:Pro:FIPS-updates:24.04:LTS","package":"linux-gcp-fips","fixed_in":["6.8.0-1058.61+fips1"],"sources":["osv"]},{"ecosystem":"Ubuntu:25.10","package":"linux","fixed_in":["6.17.0-29.29"],"sources":["osv"]},{"ecosystem":"Ubuntu:25.10","package":"linux-aws","fixed_in":["6.17.0-1015.15"],"sources":["osv"]},{"ecosystem":"Ubuntu:25.10","package":"linux-azure","fixed_in":["6.17.0-1015.15"],"sources":["osv"]},{"ecosystem":"Ubuntu:25.10","package":"linux-gcp","fixed_in":["6.17.0-1018.19"],"sources":["osv"]},{"ecosystem":"Ubuntu:25.10","package":"linux-oracle","fixed_in":["6.17.0-1014.14"],"sources":["osv"]},{"ecosystem":"Ubuntu:25.10","package":"linux-raspi","fixed_in":["6.17.0-1017.17"],"sources":["osv"]},{"ecosystem":"Ubuntu:25.10","package":"linux-realtime","fixed_in":["6.17.0-1013.15"],"sources":["osv"]},{"ecosystem":"Ubuntu:25.10","package":"linux-riscv","fixed_in":["6.17.0-29.29.1"],"sources":["osv"]}],"affected":[{"source":"osv","ecosystem":"Azure Linux:3","package":"kernel","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.6.142.1-1"}]}]},{"source":"osv","ecosystem":"Alpaquita:23","package":"linux-lts","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"6.1.182-r0"},{"fixed":"6.1.189-r0"}]}]},{"source":"osv","ecosystem":"Alpaquita:25","package":"linux-lts","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"6.12.87-r0"},{"fixed":"6.12.92-r0"}]}]},{"source":"osv","ecosystem":"Alpaquita:stream","package":"linux-lts","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"6.12.92-r1"},{"fixed":"6.18.35-r1"}]}]},{"source":"osv","ecosystem":"Linux","package":"Kernel","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.1.183"}]},{"type":"ECOSYSTEM","events":[{"introduced":"6.2.0"},{"fixed":"6.6.142"}]},{"type":"ECOSYSTEM","events":[{"introduced":"6.7.0"},{"fixed":"6.12.92"}]},{"type":"ECOSYSTEM","events":[{"introduced":"6.10.0"},{"fixed":"6.18.23"}]},{"type":"ECOSYSTEM","events":[{"introduced":"6.13.0"},{"fixed":"6.19.10"}]}]},{"source":"osv","ecosystem":"Debian:12","package":"linux","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.1.187-1"}]}],"versions":["6.1.106-1","6.1.106-2","6.1.106-3","6.1.112-1","6.1.115-1","6.1.119-1","6.1.123-1","6.1.124-1","6.1.128-1","6.1.129-1","6.1.133-1","6.1.135-1","6.1.137-1","6.1.139-1","6.1.140-1","6.1.147-1","6.1.148-1","6.1.153-1","6.1.158-1","6.1.159-1","6.1.162-1","6.1.164-1","6.1.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.27-1","6.1.37-1","6.1.38-1","6.1.38-2","6.1.38-2~bpo11+1","6.1.38-3","6.1.38-4","6.1.38-4~bpo11+1","6.1.52-1","6.1.55-1","6.1.55-1~bpo11+1","6.1.64-1","6.1.66-1","6.1.67-1","6.1.69-1","6.1.69-1~bpo11+1","6.1.76-1","6.1.76-1~bpo11+1","6.1.82-1","6.1.85-1","6.1.90-1","6.1.90-1~bpo11+1","6.1.94-1","6.1.94-1~bpo11+1","6.1.98-1","6.1.99-1"]},{"source":"osv","ecosystem":"Debian:13","package":"linux","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.12.94-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","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~bpo12+1"]},{"source":"osv","ecosystem":"Debian:14","package":"linux","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.19.10-1"}]}],"versions":["6.12.100-1","6.12.101-1","6.12.105-1","6.12.107-1","6.12.111-1","6.12.38-1","6.12.41-1","6.12.43-1","6.12.43-1~bpo12+1","6.12.48-1","6.12.57-1","6.12.57-1~bpo12+1","6.12.63-1","6.12.63-1~bpo12+1","6.12.69-1","6.12.69-1~bpo12+1","6.12.73-1","6.12.73-1~bpo12+1","6.12.74-1","6.12.74-2","6.12.74-2~bpo12+1","6.12.85-1","6.12.85-1~bpo12+1","6.12.86-1","6.12.86-1~bpo12+1","6.12.88-1","6.12.88-1~bpo12+1","6.12.90-1","6.12.90-1~bpo12+1","6.12.90-2","6.12.90-2~bpo12+1","6.12.94-1","6.12.94-1~bpo12+1","6.12.95-1","6.12.95-1~bpo12+1","6.12.96-1","6.13.10-1~exp1","6.13.11-1~exp1","6.13.2-1~exp1","6.13.3-1~exp1","6.13.4-1~exp1","6.13.5-1~exp1","6.13.6-1~exp1","6.13.7-1~exp1","6.13.8-1~exp1","6.13.9-1~exp1","6.13~rc6-1~exp1","6.13~rc7-1~exp1","6.14.3-1~exp1","6.14.5-1~exp1","6.14.6-1~exp1","6.15-1~exp1","6.15.1-1~exp1","6.15.2-1~exp1","6.15.3-1~exp1","6.15.4-1~exp1","6.15.5-1~exp1","6.15.6-1~exp1","6.15~rc7-1~exp1","6.16-1~exp1","6.16.1-1~exp1","6.16.10-1","6.16.11-1","6.16.12-1","6.16.12-1~bpo13+1","6.16.12-2","6.16.3-1","6.16.3-1~bpo13+1","6.16.5-1","6.16.6-1","6.16.7-1","6.16.8-1","6.16.9-1","6.16~rc7-1~exp1","6.17.10-1","6.17.11-1","6.17.12-1","6.17.13-1","6.17.13-1~bpo13+1","6.17.2-1~exp1","6.17.5-1~exp1","6.17.6-1","6.17.7-1","6.17.7-2","6.17.8-1","6.17.8-1~bpo13+1","6.17.9-1","6.18.1-1~exp1","6.18.10-1","6.18.12-1","6.18.12-1~bpo13+1","6.18.13-1","6.18.14-1","6.18.15-1","6.18.15-1~bpo13+1","6.18.2-1~exp1","6.18.3-1","6.18.5-1","6.18.5-1~bpo13+1","6.18.8-1","6.18.9-1","6.18.9-1~bpo13+1","6.18~rc4-1~exp1","6.18~rc4-1~exp2","6.18~rc5-1~exp1","6.18~rc6-1~exp1","6.18~rc7-1~exp1","6.19-1~exp1","6.19.10-1~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"]},{"source":"osv","ecosystem":"openEuler:24.03-LTS","package":"kernel","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.6.0-145.0.2.130.oe2403"}]}],"bundled":45},{"source":"osv","ecosystem":"openEuler:24.03-LTS-SP1","package":"kernel","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.6.0-145.0.2.142.oe2403sp1"}]}],"bundled":48},{"source":"osv","ecosystem":"openEuler:24.03-LTS-SP2","package":"kernel","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.6.0-145.0.2.143.oe2403sp2"}]}],"bundled":45},{"source":"osv","ecosystem":"Root:Debian:12","package":"linux","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.1.190-1.aikido.167"}]}]},{"source":"osv","ecosystem":"Root:Debian:12","package":"rootio-linux","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.1.190-1.aikido.167"}]}]},{"source":"osv","ecosystem":"Root:Ubuntu:24.04","package":"linux","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-149.149.aikido.91"}]}]},{"source":"osv","ecosystem":"Root:Ubuntu:24.04","package":"rootio-linux","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-149.149.aikido.91"}]}]},{"source":"osv","ecosystem":"SUSE:Linux Micro Extras 6.2","package":"kernel-obs-build","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.12.0-160000.36.1"}]}],"bundled":255},{"source":"osv","ecosystem":"SUSE:Linux Micro Extras 6.2","package":"kernel-syms","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.12.0-160000.36.1"}]}],"bundled":255},{"source":"osv","ecosystem":"SUSE:Linux Micro 6.2","package":"kernel-64kb","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.12.0-160000.36.1"}]}],"bundled":255},{"source":"osv","ecosystem":"SUSE:Linux Micro 6.2","package":"kernel-default","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.12.0-160000.36.1"}]}],"bundled":255},{"source":"osv","ecosystem":"SUSE:Linux Micro 6.2","package":"kernel-default-base","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.12.0-160000.36.1.160000.2.17"}]}],"bundled":255},{"source":"osv","ecosystem":"SUSE:Linux Micro 6.2","package":"kernel-rt","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.12.0-160000.36.1"}]}],"bundled":255},{"source":"osv","ecosystem":"SUSE:Linux Micro 6.2","package":"kernel-source","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.12.0-160000.36.1"}]}],"bundled":255},{"source":"osv","ecosystem":"SUSE:Linux Enterprise High Availability Extension 16.0","package":"kernel-default","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.12.0-160000.36.1"}]}],"bundled":255},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server 16.0","package":"kernel-64kb","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.12.0-160000.36.1"}]}],"bundled":255},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server 16.0","package":"kernel-azure","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.12.0-160000.36.1"}]}],"bundled":255},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server 16.0","package":"kernel-default","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.12.0-160000.36.1"}]}],"bundled":255},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server 16.0","package":"kernel-default-base","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.12.0-160000.36.1.160000.2.17"}]}],"bundled":255},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server 16.0","package":"kernel-docs","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.12.0-160000.36.1"}]}],"bundled":255},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server 16.0","package":"kernel-kvmsmall","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.12.0-160000.36.1"}]}],"bundled":255},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server 16.0","package":"kernel-obs-qa","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.12.0-160000.36.1"}]}],"bundled":255},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server 16.0","package":"kernel-source","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.12.0-160000.36.1"}]}],"bundled":255},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server 16.0","package":"kernel-syms","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.12.0-160000.36.1"}]}],"bundled":255},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server 16.0","package":"kernel-zfcpdump","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.12.0-160000.36.1"}]}],"bundled":255},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server for SAP applications 16.0","package":"kernel-64kb","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.12.0-160000.36.1"}]}],"bundled":255},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server for SAP applications 16.0","package":"kernel-azure","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.12.0-160000.36.1"}]}],"bundled":255},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server for SAP applications 16.0","package":"kernel-default","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.12.0-160000.36.1"}]}],"bundled":255},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server for SAP applications 16.0","package":"kernel-default-base","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.12.0-160000.36.1.160000.2.17"}]}],"bundled":255},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server for SAP applications 16.0","package":"kernel-docs","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.12.0-160000.36.1"}]}],"bundled":255},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server for SAP applications 16.0","package":"kernel-kvmsmall","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.12.0-160000.36.1"}]}],"bundled":255},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server for SAP applications 16.0","package":"kernel-obs-qa","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.12.0-160000.36.1"}]}],"bundled":255},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server for SAP applications 16.0","package":"kernel-source","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.12.0-160000.36.1"}]}],"bundled":255},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server for SAP applications 16.0","package":"kernel-syms","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.12.0-160000.36.1"}]}],"bundled":255},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server for SAP applications 16.0","package":"kernel-zfcpdump","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.12.0-160000.36.1"}]}],"bundled":255},{"source":"osv","ecosystem":"Ubuntu:16.04:LTS","package":"linux-hwe-edge","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["4.8.0-28.30~16.04.1","4.8.0-30.32~16.04.1","4.8.0-32.34~16.04.1","4.8.0-34.36~16.04.1","4.10.0-14.16~16.04.1","4.10.0-19.21~16.04.1","4.10.0-20.22~16.04.1","4.10.0-21.23~16.04.1","4.10.0-22.24~16.04.1","4.10.0-24.28~16.04.1","4.10.0-26.30~16.04.1","4.11.0-13.19~16.04.1","4.11.0-14.20~16.04.1","4.13.0-16.19~16.04.3","4.13.0-17.20~16.04.1","4.13.0-19.22~16.04.1","4.13.0-21.24~16.04.1","4.13.0-25.29~16.04.2","4.15.0-13.14~16.04.1","4.15.0-15.16~16.04.1","4.15.0-20.21~16.04.1","4.15.0-22.24~16.04.1","4.15.0-23.25~16.04.1"]},{"source":"osv","ecosystem":"Ubuntu:18.04:LTS","package":"linux-aws-5.0","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.0.0-1021.24~18.04.1","5.0.0-1022.25~18.04.1","5.0.0-1023.26~18.04.1","5.0.0-1024.27~18.04.1","5.0.0-1025.28","5.0.0-1027.30"]},{"source":"osv","ecosystem":"Ubuntu:18.04:LTS","package":"linux-aws-5.3","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.3.0-1016.17~18.04.1","5.3.0-1017.18~18.04.1","5.3.0-1019.21~18.04.1","5.3.0-1023.25~18.04.1","5.3.0-1028.30~18.04.1","5.3.0-1030.32~18.04.1","5.3.0-1032.34~18.04.2","5.3.0-1033.35","5.3.0-1034.36","5.3.0-1035.37"]},{"source":"osv","ecosystem":"Ubuntu:18.04:LTS","package":"linux-azure","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["4.15.0-1002.2","4.15.0-1003.3","4.15.0-1004.4","4.15.0-1008.8","4.15.0-1009.9","4.15.0-1012.12","4.15.0-1013.13","4.15.0-1014.14","4.15.0-1018.18","4.15.0-1019.19","4.15.0-1021.21","4.15.0-1022.23","4.15.0-1023.24","4.15.0-1025.26","4.15.0-1028.29","4.15.0-1030.31","4.15.0-1031.32","4.15.0-1032.33","4.15.0-1035.36","4.15.0-1036.38","4.15.0-1037.39","4.18.0-1011.11~18.04.1","4.18.0-1013.13~18.04.1","4.18.0-1014.14~18.04.1","4.18.0-1018.18~18.04.1","4.18.0-1019.19~18.04.1","4.18.0-1020.20~18.04.1","4.18.0-1023.24~18.04.1","4.18.0-1024.25~18.04.1","4.18.0-1025.27~18.04.1","5.0.0-1014.14~18.04.1","5.0.0-1016.17~18.04.1","5.0.0-1018.19~18.04.1","5.0.0-1020.21~18.04.1","5.0.0-1022.23~18.04.1","5.0.0-1023.24~18.04.1","5.0.0-1025.27~18.04.1","5.0.0-1027.29~18.04.1","5.0.0-1028.30~18.04.1","5.0.0-1029.31~18.04.1","5.0.0-1031.33","5.0.0-1032.34","5.0.0-1035.37","5.0.0-1036.38"]},{"source":"osv","ecosystem":"Ubuntu:18.04:LTS","package":"linux-azure-5.3","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.3.0-1007.8~18.04.1","5.3.0-1008.9~18.04.1","5.3.0-1009.10~18.04.1","5.3.0-1010.11~18.04.1","5.3.0-1012.13~18.04.1","5.3.0-1013.14~18.04.1","5.3.0-1016.17~18.04.1","5.3.0-1018.19~18.04.1","5.3.0-1019.20~18.04.1","5.3.0-1020.21~18.04.1","5.3.0-1022.23~18.04.1","5.3.0-1028.29~18.04.1","5.3.0-1031.32~18.04.1","5.3.0-1032.33~18.04.1","5.3.0-1034.35~18.04.1","5.3.0-1035.36"]},{"source":"osv","ecosystem":"Ubuntu:18.04:LTS","package":"linux-azure-edge","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["4.18.0-1006.6~18.04.1","4.18.0-1007.7~18.04.1","4.18.0-1008.8~18.04.1","5.0.0-1012.12~18.04.2"]},{"source":"osv","ecosystem":"Ubuntu:18.04:LTS","package":"linux-gcp","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["4.15.0-1001.1","4.15.0-1003.3","4.15.0-1005.5","4.15.0-1006.6","4.15.0-1008.8","4.15.0-1009.9","4.15.0-1010.10","4.15.0-1014.14","4.15.0-1015.15","4.15.0-1017.18","4.15.0-1018.19","4.15.0-1019.20","4.15.0-1021.22","4.15.0-1023.24","4.15.0-1024.25","4.15.0-1025.26","4.15.0-1026.27","4.15.0-1027.28","4.15.0-1028.29","4.15.0-1029.31","4.15.0-1030.32","4.15.0-1032.34","4.15.0-1033.35","4.15.0-1034.36","4.15.0-1036.38","4.15.0-1037.39","4.15.0-1040.42","4.15.0-1042.45","4.15.0-1044.70","5.0.0-1020.20~18.04.1","5.0.0-1021.21~18.04.1","5.0.0-1025.26~18.04.1","5.0.0-1026.27~18.04.1","5.0.0-1028.29~18.04.1","5.0.0-1029.30~18.04.1","5.0.0-1031.32","5.0.0-1033.34","5.0.0-1034.35"]},{"source":"osv","ecosystem":"Ubuntu:18.04:LTS","package":"linux-gcp-5.3","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.3.0-1008.9~18.04.1","5.3.0-1009.10~18.04.1","5.3.0-1010.11~18.04.1","5.3.0-1012.13~18.04.1","5.3.0-1014.15~18.04.1","5.3.0-1016.17~18.04.1","5.3.0-1017.18~18.04.1","5.3.0-1018.19~18.04.1","5.3.0-1020.22~18.04.1","5.3.0-1026.28~18.04.1","5.3.0-1029.31~18.04.1","5.3.0-1030.32~18.04.1","5.3.0-1032.34~18.04.1"]},{"source":"osv","ecosystem":"Ubuntu:18.04:LTS","package":"linux-gke-4.15","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["4.15.0-1030.32","4.15.0-1032.34","4.15.0-1033.35","4.15.0-1034.36","4.15.0-1036.38","4.15.0-1037.39","4.15.0-1040.42","4.15.0-1041.43","4.15.0-1042.44","4.15.0-1044.46","4.15.0-1045.48","4.15.0-1046.49","4.15.0-1048.51","4.15.0-1049.52","4.15.0-1050.53","4.15.0-1052.55","4.15.0-1055.58","4.15.0-1057.60","4.15.0-1058.61","4.15.0-1059.62","4.15.0-1063.66","4.15.0-1064.67","4.15.0-1066.69","4.15.0-1067.70","4.15.0-1069.72","4.15.0-1070.73","4.15.0-1072.76","4.15.0-1073.78","4.15.0-1074.79","4.15.0-1076.81","4.15.0-1077.82","4.15.0-1078.83","4.15.0-1079.84"]},{"source":"osv","ecosystem":"Ubuntu:18.04:LTS","package":"linux-gke-5.4","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.4.0-1025.25~18.04.1","5.4.0-1027.28~18.04.1","5.4.0-1029.31~18.04.1","5.4.0-1030.32~18.04.1","5.4.0-1032.34~18.04.1","5.4.0-1033.35~18.04.1","5.4.0-1035.37~18.04.1","5.4.0-1036.38~18.04.1","5.4.0-1037.39~18.04.1","5.4.0-1039.41~18.04.1","5.4.0-1040.42~18.04.1","5.4.0-1042.44~18.04.1","5.4.0-1043.45~18.04.1","5.4.0-1044.46~18.04.1","5.4.0-1046.48~18.04.1","5.4.0-1049.52~18.04.1","5.4.0-1051.54~18.04.1","5.4.0-1052.55~18.04.1","5.4.0-1053.56~18.04.1","5.4.0-1054.57~18.04.1","5.4.0-1055.58~18.04.1","5.4.0-1056.59~18.04.1","5.4.0-1057.60~18.04.1","5.4.0-1059.62~18.04.1","5.4.0-1061.64~18.04.1","5.4.0-1062.65~18.04.1","5.4.0-1063.66~18.04.1","5.4.0-1065.68~18.04.1","5.4.0-1066.69~18.04.1","5.4.0-1067.70~18.04.1","5.4.0-1068.71~18.04.1","5.4.0-1071.76~18.04.3","5.4.0-1072.77~18.04.1","5.4.0-1074.79~18.04.1","5.4.0-1076.82~18.04.1","5.4.0-1078.84~18.04.1","5.4.0-1080.86~18.04.1"]},{"source":"osv","ecosystem":"Ubuntu:18.04:LTS","package":"linux-gkeop-5.4","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.4.0-1001.1","5.4.0-1003.3","5.4.0-1004.5","5.4.0-1005.6","5.4.0-1007.8~18.04.1","5.4.0-1008.9~18.04.1","5.4.0-1009.10~18.04.1","5.4.0-1010.11~18.04.1","5.4.0-1011.12~18.04.2","5.4.0-1012.13~18.04.1","5.4.0-1013.14~18.04.1","5.4.0-1014.15~18.04.1","5.4.0-1015.16~18.04.1","5.4.0-1016.17~18.04.1","5.4.0-1018.19~18.04.1","5.4.0-1021.22~18.04.1","5.4.0-1022.23~18.04.1","5.4.0-1023.24~18.04.1","5.4.0-1024.25~18.04.1","5.4.0-1025.26~18.04.1","5.4.0-1026.27~18.04.1","5.4.0-1027.28~18.04.1","5.4.0-1029.30~18.04.2","5.4.0-1031.32~18.04.1","5.4.0-1032.33~18.04.1","5.4.0-1033.34~18.04.1","5.4.0-1034.35~18.04.1","5.4.0-1036.37~18.04.1","5.4.0-1037.38~18.04.1","5.4.0-1038.39~18.04.1","5.4.0-1039.40~18.04.1","5.4.0-1040.41~18.04.1","5.4.0-1043.44~18.04.1","5.4.0-1046.48~18.04.1","5.4.0-1048.51~18.04.1","5.4.0-1049.52~18.04.1","5.4.0-1051.54~18.04.1"]},{"source":"osv","ecosystem":"Ubuntu:18.04:LTS","package":"linux-hwe","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["4.18.0-13.14~18.04.1","4.18.0-14.15~18.04.1","4.18.0-15.16~18.04.1","4.18.0-16.17~18.04.1","4.18.0-17.18~18.04.1","4.18.0-18.19~18.04.1","4.18.0-20.21~18.04.1","4.18.0-21.22~18.04.1","4.18.0-22.23~18.04.1","4.18.0-24.25~18.04.1","4.18.0-25.26~18.04.1","5.0.0-23.24~18.04.1","5.0.0-25.26~18.04.1","5.0.0-27.28~18.04.1","5.0.0-29.31~18.04.1","5.0.0-31.33~18.04.1","5.0.0-32.34~18.04.2","5.0.0-35.38~18.04.1","5.0.0-36.39~18.04.1","5.0.0-37.40~18.04.1","5.3.0-26.28~18.04.1","5.3.0-28.30~18.04.1","5.3.0-40.32~18.04.1","5.3.0-42.34~18.04.1","5.3.0-45.37~18.04.1","5.3.0-46.38~18.04.1","5.3.0-51.44~18.04.2","5.3.0-53.47~18.04.1","5.3.0-59.53~18.04.1","5.3.0-61.55~18.04.1","5.3.0-62.56~18.04.1","5.3.0-64.58~18.04.1","5.3.0-65.59","5.3.0-66.60","5.3.0-67.61","5.3.0-68.63","5.3.0-69.65","5.3.0-70.66","5.3.0-72.68","5.3.0-73.69","5.3.0-74.70","5.3.0-75.71","5.3.0-76.72"]},{"source":"osv","ecosystem":"Ubuntu:18.04:LTS","package":"linux-hwe-edge","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.0.0-15.16~18.04.1","5.0.0-16.17~18.04.1","5.0.0-17.18~18.04.1","5.0.0-19.20~18.04.1","5.0.0-20.21~18.04.1","5.3.0-19.20~18.04.2","5.3.0-22.24~18.04.1","5.3.0-23.25~18.04.1","5.3.0-23.25~18.04.2","5.3.0-24.26~18.04.2"]},{"source":"osv","ecosystem":"Ubuntu:18.04:LTS","package":"linux-oem","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["4.15.0-1002.3","4.15.0-1004.5","4.15.0-1006.9","4.15.0-1008.11","4.15.0-1009.12","4.15.0-1012.15","4.15.0-1013.16","4.15.0-1015.18","4.15.0-1017.20","4.15.0-1018.21","4.15.0-1021.24","4.15.0-1024.29","4.15.0-1026.31","4.15.0-1028.33","4.15.0-1030.35","4.15.0-1033.38","4.15.0-1034.39","4.15.0-1035.40","4.15.0-1036.41","4.15.0-1038.43","4.15.0-1039.44","4.15.0-1043.48","4.15.0-1045.50","4.15.0-1050.57","4.15.0-1056.65","4.15.0-1057.66","4.15.0-1059.68","4.15.0-1063.72","4.15.0-1064.73","4.15.0-1065.75","4.15.0-1066.76","4.15.0-1067.77","4.15.0-1069.79","4.15.0-1073.83","4.15.0-1076.86","4.15.0-1079.89","4.15.0-1080.90","4.15.0-1081.91","4.15.0-1087.97","4.15.0-1090.100","4.15.0-1091.101","4.15.0-1093.103","4.15.0-1094.104","4.15.0-1096.106","4.15.0-1097.107","4.15.0-1099.109","4.15.0-1100.110","4.15.0-1101.112","4.15.0-1102.113","4.15.0-1103.114"]},{"source":"osv","ecosystem":"Ubuntu:18.04:LTS","package":"linux-oracle-5.0","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.0.0-1007.12~18.04.1","5.0.0-1008.13~18.04.1","5.0.0-1009.14~18.04.1","5.0.0-1010.15~18.04.1","5.0.0-1011.16","5.0.0-1013.18","5.0.0-1014.19"]},{"source":"osv","ecosystem":"Ubuntu:18.04:LTS","package":"linux-oracle-5.3","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.3.0-1011.12~18.04.1","5.3.0-1013.14~18.04.1","5.3.0-1014.15~18.04.1","5.3.0-1016.18~18.04.1","5.3.0-1018.20~18.04.1","5.3.0-1024.26~18.04.1","5.3.0-1027.29~18.04.1","5.3.0-1028.30~18.04.1","5.3.0-1030.32~18.04.1"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-aws-5.11","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.11.0-1009.9~20.04.2","5.11.0-1014.15~20.04.1","5.11.0-1016.17~20.04.1","5.11.0-1017.18~20.04.1","5.11.0-1019.20~20.04.1","5.11.0-1020.21~20.04.2","5.11.0-1021.22~20.04.2","5.11.0-1022.23~20.04.1","5.11.0-1023.24~20.04.1","5.11.0-1025.27~20.04.1","5.11.0-1027.30~20.04.1","5.11.0-1028.31~20.04.1"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-aws-5.13","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.13.0-1008.9~20.04.2","5.13.0-1011.12~20.04.1","5.13.0-1012.13~20.04.1","5.13.0-1014.15~20.04.1","5.13.0-1017.19~20.04.1","5.13.0-1019.21~20.04.1","5.13.0-1021.23~20.04.2","5.13.0-1022.24~20.04.1","5.13.0-1023.25~20.04.1","5.13.0-1025.27~20.04.1","5.13.0-1028.31~20.04.1","5.13.0-1029.32~20.04.1","5.13.0-1031.35~20.04.1"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-aws-5.8","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.8.0-1035.37~20.04.1","5.8.0-1038.40~20.04.1","5.8.0-1041.43~20.04.1","5.8.0-1042.44~20.04.1"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-azure-5.11","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.11.0-1007.7~20.04.2","5.11.0-1012.13~20.04.1","5.11.0-1013.14~20.04.1","5.11.0-1015.16~20.04.1","5.11.0-1017.18~20.04.1","5.11.0-1019.20~20.04.1","5.11.0-1020.21~20.04.1","5.11.0-1021.22~20.04.1","5.11.0-1022.23~20.04.1","5.11.0-1023.24~20.04.1","5.11.0-1025.27~20.04.1","5.11.0-1027.30~20.04.1","5.11.0-1028.31~20.04.2"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-azure-5.13","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.13.0-1009.10~20.04.2","5.13.0-1012.14~20.04.1","5.13.0-1013.15~20.04.1","5.13.0-1014.16~20.04.1","5.13.0-1017.19~20.04.1","5.13.0-1021.24~20.04.1","5.13.0-1022.26~20.04.1","5.13.0-1023.27~20.04.1","5.13.0-1025.29~20.04.1","5.13.0-1028.33~20.04.1","5.13.0-1029.34~20.04.1","5.13.0-1031.37~20.04.1"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-azure-5.8","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.8.0-1033.35~20.04.1","5.8.0-1036.38~20.04.1","5.8.0-1039.42~20.04.1","5.8.0-1040.43~20.04.1","5.8.0-1041.44~20.04.1","5.8.0-1042.45~20.04.1","5.8.0-1043.46~20.04.1"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-azure-fde","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.4.0-1063.66+cvm2.2","5.4.0-1063.66+cvm3.2","5.4.0-1064.67+cvm1.1","5.4.0-1065.68+cvm2.1","5.4.0-1067.70+cvm1.1","5.4.0-1068.71+cvm1.1","5.4.0-1069.72+cvm1.1","5.4.0-1070.73+cvm1.1","5.4.0-1072.75+cvm1.1","5.4.0-1073.76+cvm1.1","5.4.0-1074.77+cvm1.1","5.4.0-1076.79+cvm1.1","5.4.0-1078.81+cvm1.1","5.4.0-1080.83+cvm1.1","5.4.0-1083.87+cvm1.1","5.4.0-1085.90+cvm1.1","5.4.0-1085.90+cvm2.1","5.4.0-1086.91+cvm1.1","5.4.0-1089.94+cvm1.2","5.4.0-1090.95+cvm1.1","5.4.0-1091.96+cvm1.1","5.4.0-1092.97+cvm1.1","5.4.0-1095.101+cvm1.1","5.4.0-1098.104+cvm1.1","5.4.0-1100.106+cvm1.1","5.4.0-1103.109+cvm1.1"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-gcp-5.11","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.11.0-1009.10~20.04.1","5.11.0-1014.16~20.04.1","5.11.0-1017.19~20.04.1","5.11.0-1018.20~20.04.2","5.11.0-1020.22~20.04.1","5.11.0-1021.23~20.04.1","5.11.0-1022.24~20.04.1","5.11.0-1023.25~20.04.1","5.11.0-1024.26~20.04.1","5.11.0-1026.29~20.04.1","5.11.0-1028.32~20.04.1","5.11.0-1029.33~20.04.3"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-gcp-5.13","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.13.0-1008.9~20.04.3","5.13.0-1012.15~20.04.1","5.13.0-1013.16~20.04.1","5.13.0-1015.18~20.04.1","5.13.0-1019.23~20.04.1","5.13.0-1021.25~20.04.1","5.13.0-1023.28~20.04.1","5.13.0-1024.29~20.04.1","5.13.0-1025.30~20.04.1","5.13.0-1027.32~20.04.1","5.13.0-1030.36~20.04.1","5.13.0-1031.37~20.04.1","5.13.0-1033.40~20.04.1"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-gcp-5.8","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.8.0-1032.34~20.04.1","5.8.0-1035.37~20.04.1","5.8.0-1038.40~20.04.1","5.8.0-1039.41"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-gke","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.4.0-1033.35","5.4.0-1035.37","5.4.0-1036.38","5.4.0-1037.39","5.4.0-1039.41","5.4.0-1041.43","5.4.0-1042.44","5.4.0-1043.45","5.4.0-1044.46","5.4.0-1046.48","5.4.0-1049.52","5.4.0-1051.54","5.4.0-1052.55","5.4.0-1053.56","5.4.0-1054.57","5.4.0-1055.58","5.4.0-1056.59","5.4.0-1057.60","5.4.0-1059.62","5.4.0-1061.64","5.4.0-1062.65","5.4.0-1063.66","5.4.0-1065.68","5.4.0-1066.69","5.4.0-1067.70","5.4.0-1068.71","5.4.0-1071.76","5.4.0-1072.77","5.4.0-1074.79","5.4.0-1076.82","5.4.0-1078.84","5.4.0-1080.86","5.4.0-1081.87","5.4.0-1083.89","5.4.0-1084.90","5.4.0-1086.93","5.4.0-1087.94","5.4.0-1090.97","5.4.0-1091.98","5.4.0-1094.101","5.4.0-1095.102","5.4.0-1096.103","5.4.0-1097.104","5.4.0-1098.105","5.4.0-1099.106","5.4.0-1100.107","5.4.0-1101.108","5.4.0-1102.109","5.4.0-1103.110","5.4.0-1104.111","5.4.0-1105.112"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-gke-5.15","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.15.0-1011.14~20.04.1","5.15.0-1014.17~20.04.1","5.15.0-1015.18~20.04.1","5.15.0-1016.19~20.04.1","5.15.0-1019.23~20.04.1","5.15.0-1020.25~20.04.1","5.15.0-1023.28~20.04.2","5.15.0-1027.32~20.04.1","5.15.0-1028.33~20.04.1","5.15.0-1029.34~20.04.1","5.15.0-1031.36~20.04.1","5.15.0-1032.37~20.04.1","5.15.0-1033.38~20.04.1","5.15.0-1034.39~20.04.1","5.15.0-1036.41~20.04.1","5.15.0-1037.42~20.04.1","5.15.0-1038.43~20.04.1","5.15.0-1039.44~20.04.1"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-gkeop","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.4.0-1008.9","5.4.0-1009.10","5.4.0-1010.11","5.4.0-1011.12","5.4.0-1012.13","5.4.0-1013.14","5.4.0-1014.15","5.4.0-1015.16","5.4.0-1016.17","5.4.0-1018.19","5.4.0-1021.22","5.4.0-1022.23","5.4.0-1023.24","5.4.0-1024.25","5.4.0-1025.26","5.4.0-1026.27","5.4.0-1027.28","5.4.0-1029.30","5.4.0-1031.32","5.4.0-1032.33","5.4.0-1033.34","5.4.0-1034.35","5.4.0-1036.37","5.4.0-1037.38","5.4.0-1038.39","5.4.0-1039.40","5.4.0-1040.41","5.4.0-1043.44","5.4.0-1046.48","5.4.0-1048.51","5.4.0-1049.52","5.4.0-1051.54","5.4.0-1052.55","5.4.0-1053.56","5.4.0-1054.57","5.4.0-1056.60","5.4.0-1057.61","5.4.0-1060.64","5.4.0-1061.65","5.4.0-1062.66","5.4.0-1064.68","5.4.0-1065.69","5.4.0-1066.70","5.4.0-1067.71","5.4.0-1068.72","5.4.0-1069.73","5.4.0-1070.74","5.4.0-1071.75","5.4.0-1072.76","5.4.0-1073.77","5.4.0-1074.78","5.4.0-1075.79","5.4.0-1076.80","5.4.0-1077.81","5.4.0-1078.82","5.4.0-1079.83","5.4.0-1080.84","5.4.0-1081.85","5.4.0-1083.87","5.4.0-1084.88","5.4.0-1085.89","5.4.0-1086.90","5.4.0-1087.91","5.4.0-1088.92","5.4.0-1089.93","5.4.0-1090.94","5.4.0-1091.95","5.4.0-1092.96","5.4.0-1093.97","5.4.0-1094.98","5.4.0-1095.99","5.4.0-1096.100","5.4.0-1097.101","5.4.0-1098.102","5.4.0-1099.103","5.4.0-1100.104","5.4.0-1101.105","5.4.0-1102.106"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-gkeop-5.15","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.15.0-1003.5~20.04.2","5.15.0-1005.7~20.04.1","5.15.0-1007.10~20.04.1","5.15.0-1008.12~20.04.1","5.15.0-1011.15~20.04.2","5.15.0-1012.16~20.04.1","5.15.0-1013.17~20.04.1","5.15.0-1015.19~20.04.1","5.15.0-1016.21~20.04.1","5.15.0-1017.22~20.04.1","5.15.0-1018.23~20.04.1","5.15.0-1019.24~20.04.1","5.15.0-1020.25~20.04.1","5.15.0-1021.26~20.04.1","5.15.0-1022.27~20.04.1","5.15.0-1023.28~20.04.1","5.15.0-1024.29~20.04.1","5.15.0-1025.30~20.04.1","5.15.0-1026.31~20.04.1","5.15.0-1027.32~20.04.1","5.15.0-1028.33~20.04.1","5.15.0-1030.35~20.04.1","5.15.0-1031.37~20.04.1","5.15.0-1032.38~20.04.1","5.15.0-1033.39~20.04.1","5.15.0-1034.40~20.04.1","5.15.0-1035.41~20.04.1","5.15.0-1036.42~20.04.1","5.15.0-1037.43~20.04.1","5.15.0-1038.44~20.04.1","5.15.0-1039.45~20.04.1","5.15.0-1040.46~20.04.1","5.15.0-1043.50~20.04.1","5.15.0-1044.51~20.04.1","5.15.0-1045.52~20.04.1","5.15.0-1046.53~20.04.1","5.15.0-1047.54~20.04.1","5.15.0-1048.55~20.04.1","5.15.0-1049.56~20.04.1","5.15.0-1050.57~20.04.1","5.15.0-1051.58~20.04.1","5.15.0-1052.59~20.04.1","5.15.0-1053.60~20.04.1","5.15.0-1054.61~20.04.1","5.15.0-1055.62~20.04.1"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-hwe-5.11","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.11.0-22.23~20.04.1","5.11.0-25.27~20.04.1","5.11.0-27.29~20.04.1","5.11.0-34.36~20.04.1","5.11.0-36.40~20.04.1","5.11.0-37.41~20.04.2","5.11.0-38.42~20.04.1","5.11.0-40.44~20.04.2","5.11.0-41.45~20.04.1","5.11.0-43.47~20.04.2","5.11.0-44.48~20.04.2","5.11.0-46.51~20.04.1"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-hwe-5.13","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.13.0-21.21~20.04.1","5.13.0-22.22~20.04.1","5.13.0-23.23~20.04.2","5.13.0-25.26~20.04.1","5.13.0-27.29~20.04.1","5.13.0-28.31~20.04.1","5.13.0-30.33~20.04.1","5.13.0-35.40~20.04.1","5.13.0-37.42~20.04.1","5.13.0-39.44~20.04.1","5.13.0-40.45~20.04.1","5.13.0-41.46~20.04.1","5.13.0-44.49~20.04.1","5.13.0-48.54~20.04.1","5.13.0-51.58~20.04.1","5.13.0-52.59~20.04.1"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-hwe-5.8","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.8.0-23.24~20.04.1","5.8.0-25.26~20.04.1","5.8.0-28.30~20.04.1","5.8.0-29.31~20.04.1","5.8.0-31.33~20.04.1","5.8.0-33.36~20.04.1","5.8.0-34.37~20.04.2","5.8.0-36.40~20.04.1","5.8.0-38.43~20.04.1","5.8.0-40.45~20.04.1","5.8.0-41.46~20.04.1","5.8.0-43.49~20.04.1","5.8.0-44.50~20.04.1","5.8.0-45.51~20.04.1","5.8.0-48.54~20.04.1","5.8.0-49.55~20.04.1","5.8.0-50.56~20.04.1","5.8.0-53.60~20.04.1","5.8.0-55.62~20.04.1","5.8.0-59.66~20.04.1","5.8.0-63.71~20.04.1"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-intel-5.13","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.13.0-1007.7","5.13.0-1008.8","5.13.0-1009.9","5.13.0-1010.10","5.13.0-1011.11","5.13.0-1014.15","5.13.0-1017.19"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-oem-5.10","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.10.0-1008.9","5.10.0-1011.12","5.10.0-1013.14","5.10.0-1014.15","5.10.0-1016.17","5.10.0-1017.18","5.10.0-1019.20","5.10.0-1021.22","5.10.0-1022.23","5.10.0-1023.24","5.10.0-1025.26","5.10.0-1026.27","5.10.0-1029.30","5.10.0-1032.33","5.10.0-1033.34","5.10.0-1034.35","5.10.0-1038.40","5.10.0-1044.46","5.10.0-1045.47","5.10.0-1049.51","5.10.0-1050.52","5.10.0-1051.53","5.10.0-1052.54","5.10.0-1053.55","5.10.0-1055.58","5.10.0-1057.61"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-oem-5.13","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.13.0-1009.10","5.13.0-1010.11","5.13.0-1012.16","5.13.0-1014.18","5.13.0-1017.21","5.13.0-1019.23","5.13.0-1020.24","5.13.0-1021.25","5.13.0-1022.26","5.13.0-1026.32","5.13.0-1028.35","5.13.0-1029.36"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-oem-5.14","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.14.0-1004.4","5.14.0-1005.5","5.14.0-1007.7","5.14.0-1008.8","5.14.0-1010.10","5.14.0-1011.11","5.14.0-1013.13","5.14.0-1018.19","5.14.0-1020.22","5.14.0-1022.24","5.14.0-1024.26","5.14.0-1027.30","5.14.0-1029.32","5.14.0-1031.34","5.14.0-1032.35","5.14.0-1033.36","5.14.0-1034.37","5.14.0-1036.40","5.14.0-1038.42","5.14.0-1042.47","5.14.0-1044.49","5.14.0-1045.51","5.14.0-1046.53","5.14.0-1047.54","5.14.0-1048.55","5.14.0-1049.56","5.14.0-1050.57","5.14.0-1051.58","5.14.0-1052.59","5.14.0-1054.61","5.14.0-1055.62","5.14.0-1056.63","5.14.0-1057.64","5.14.0-1058.66","5.14.0-1059.67"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-oem-5.6","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.6.0-1007.7","5.6.0-1008.8","5.6.0-1010.10","5.6.0-1011.11","5.6.0-1013.13","5.6.0-1017.17","5.6.0-1018.18","5.6.0-1020.20","5.6.0-1021.21","5.6.0-1023.23","5.6.0-1026.26","5.6.0-1027.27","5.6.0-1028.28","5.6.0-1031.32","5.6.0-1032.33","5.6.0-1033.35","5.6.0-1034.36","5.6.0-1035.37","5.6.0-1036.39","5.6.0-1039.43","5.6.0-1042.46","5.6.0-1047.51","5.6.0-1048.52","5.6.0-1050.54","5.6.0-1052.56","5.6.0-1053.57","5.6.0-1054.58","5.6.0-1055.59","5.6.0-1056.60"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-oracle-5.11","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.11.0-1008.8~20.04.1","5.11.0-1013.14~20.04.1","5.11.0-1016.17~20.04.1","5.11.0-1017.18~20.04.1","5.11.0-1019.20~20.04.1","5.11.0-1020.21~20.04.1","5.11.0-1021.22~20.04.1","5.11.0-1022.23~20.04.1","5.11.0-1023.24~20.04.1","5.11.0-1025.27~20.04.1","5.11.0-1027.30~20.04.1","5.11.0-1028.31~20.04.1"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-oracle-5.13","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.13.0-1011.13~20.04.2","5.13.0-1015.19~20.04.1","5.13.0-1016.20~20.04.1","5.13.0-1018.22~20.04.1","5.13.0-1021.26~20.04.1","5.13.0-1025.30~20.04.1","5.13.0-1027.32~20.04.1","5.13.0-1028.33~20.04.1","5.13.0-1030.35~20.04.1","5.13.0-1033.39~20.04.1","5.13.0-1034.40~20.04.1","5.13.0-1036.43~20.04.1"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-oracle-5.8","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.8.0-1031.32~20.04.2","5.8.0-1033.34~20.04.1","5.8.0-1034.35~20.04.2","5.8.0-1037.38~20.04.1","5.8.0-1038.39~20.04.1"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-raspi2","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.3.0-1007.8","5.3.0-1014.16","5.3.0-1015.17","5.3.0-1017.19","5.4.0-1004.4","5.4.0-1006.6"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-riscv","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.4.0-24.28","5.4.0-26.30","5.4.0-27.31","5.4.0-28.32","5.4.0-30.34","5.4.0-31.35","5.4.0-33.37","5.4.0-34.38","5.4.0-36.41","5.4.0-37.42","5.4.0-39.44","5.4.0-40.45"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-riscv-5.11","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.11.0-1015.16~20.04.1","5.11.0-1017.18~20.04.1","5.11.0-1018.19~20.04.2","5.11.0-1020.21~20.04.1","5.11.0-1021.22~20.04.1","5.11.0-1022.23~20.04.1","5.11.0-1023.24~20.04.1","5.11.0-1024.25~20.04.1","5.11.0-1026.28~20.04.1","5.11.0-1028.31~20.04.1","5.11.0-1029.32~20.04.1","5.11.0-1030.34","5.11.0-1031.35"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-riscv-5.8","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.8.0-14.16~20.04.1","5.8.0-14.16~20.04.3","5.8.0-16.18~20.04.1","5.8.0-17.19~20.04.1","5.8.0-18.20~20.04.1","5.8.0-20.22~20.04.1","5.8.0-22.24~20.04.1","5.8.0-25.27~20.04.1","5.8.0-26.28~20.04.1","5.8.0-29.31~20.04.1"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-allwinner-5.19","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.19.0-1007.7~22.04.1","5.19.0-1009.9~22.04.1","5.19.0-1010.10~22.04.1","5.19.0-1011.11~22.04.1","5.19.0-1012.12~22.04.1","5.19.0-1013.13~22.04.1","5.19.0-1014.14~22.04.1","5.19.0-1015.15~22.04.1"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-aws-5.19","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.19.0-1019.20~22.04.1","5.19.0-1020.21~22.04.1","5.19.0-1022.23~22.04.1","5.19.0-1023.24~22.04.1","5.19.0-1024.25~22.04.1","5.19.0-1025.26~22.04.1","5.19.0-1026.27~22.04.1","5.19.0-1027.28~22.04.1","5.19.0-1028.29~22.04.1","5.19.0-1029.30~22.04.1"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-aws-6.2","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["6.2.0-1005.5~22.04.1","6.2.0-1006.6~22.04.1","6.2.0-1007.7~22.04.1","6.2.0-1008.8~22.04.1","6.2.0-1009.9~22.04.3","6.2.0-1010.10~22.04.1","6.2.0-1011.11~22.04.1","6.2.0-1012.12~22.04.1","6.2.0-1013.13~22.04.1","6.2.0-1014.14~22.04.1","6.2.0-1015.15~22.04.1","6.2.0-1016.16~22.04.1","6.2.0-1017.17~22.04.1","6.2.0-1018.18~22.04.1"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-aws-6.5","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["6.5.0-1008.8~22.04.1","6.5.0-1010.10~22.04.1","6.5.0-1011.11~22.04.1","6.5.0-1012.12~22.04.1","6.5.0-1014.14~22.04.1","6.5.0-1015.15~22.04.1","6.5.0-1016.16~22.04.1","6.5.0-1017.17~22.04.2","6.5.0-1018.18~22.04.1","6.5.0-1020.20~22.04.1","6.5.0-1021.21~22.04.1","6.5.0-1022.22~22.04.1","6.5.0-1023.23~22.04.1","6.5.0-1024.24~22.04.1"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-aws-6.8","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1057.60~22.04.1"}]}],"versions":["6.8.0-1009.9~22.04.2","6.8.0-1010.10~22.04.2","6.8.0-1011.12~22.04.1","6.8.0-1013.14~22.04.1","6.8.0-1014.15~22.04.1","6.8.0-1015.16~22.04.1","6.8.0-1016.17~22.04.2","6.8.0-1017.18~22.04.1","6.8.0-1018.19~22.04.1","6.8.0-1019.21~22.04.1","6.8.0-1020.22~22.04.1","6.8.0-1021.23~22.04.1","6.8.0-1023.25~22.04.1","6.8.0-1024.26~22.04.1","6.8.0-1027.29~22.04.1","6.8.0-1028.30~22.04.1","6.8.0-1029.31~22.04.1","6.8.0-1030.32~22.04.1","6.8.0-1031.33~22.04.1","6.8.0-1032.34~22.04.1","6.8.0-1033.35~22.04.1","6.8.0-1035.37~22.04.1","6.8.0-1036.38~22.04.1","6.8.0-1039.41~22.04.1","6.8.0-1040.42~22.04.1","6.8.0-1041.43~22.04.1","6.8.0-1042.44~22.04.1","6.8.0-1043.45~22.04.1","6.8.0-1044.46~22.04.1","6.8.0-1045.47~22.04.1","6.8.0-1046.49~22.04.1","6.8.0-1047.50~22.04.1","6.8.0-1050.53~22.04.1","6.8.0-1051.54~22.04.1","6.8.0-1052.55~22.04.1","6.8.0-1053.56~22.04.1","6.8.0-1055.58~22.04.1"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-azure-5.19","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.19.0-1020.21~22.04.1","5.19.0-1021.22~22.04.1","5.19.0-1022.23~22.04.1","5.19.0-1023.24~22.04.1","5.19.0-1025.28~22.04.1","5.19.0-1026.29~22.04.1","5.19.0-1027.30~22.04.2"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-azure-6.2","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["6.2.0-1005.5~22.04.1","6.2.0-1006.6~22.04.1","6.2.0-1007.7~22.04.1","6.2.0-1008.8~22.04.1","6.2.0-1009.9~22.04.3","6.2.0-1011.11~22.04.1","6.2.0-1012.12~22.04.1","6.2.0-1014.14~22.04.1","6.2.0-1015.15~22.04.1","6.2.0-1016.16~22.04.1","6.2.0-1017.17~22.04.1","6.2.0-1018.18~22.04.1","6.2.0-1019.19~22.04.1"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-azure-6.5","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["6.5.0-1007.7~22.04.1","6.5.0-1009.9~22.04.1","6.5.0-1010.10~22.04.1","6.5.0-1011.11~22.04.1","6.5.0-1015.15~22.04.1","6.5.0-1016.16~22.04.1","6.5.0-1017.17~22.04.1","6.5.0-1018.19~22.04.2","6.5.0-1019.20~22.04.1","6.5.0-1021.22~22.04.1","6.5.0-1022.23~22.04.1","6.5.0-1023.24~22.04.1","6.5.0-1024.25~22.04.1","6.5.0-1025.26~22.04.1"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-azure-6.8","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1059.65~22.04.1"}]}],"versions":["6.8.0-1008.8~22.04.1","6.8.0-1009.9~22.04.1","6.8.0-1010.10~22.04.1","6.8.0-1012.14~22.04.1","6.8.0-1013.15~22.04.1","6.8.0-1014.16~22.04.1","6.8.0-1015.17~22.04.2","6.8.0-1017.20~22.04.1","6.8.0-1018.21~22.04.1","6.8.0-1020.23~22.04.1","6.8.0-1021.25~22.04.1","6.8.0-1025.30~22.04.1","6.8.0-1026.31~22.04.1","6.8.0-1027.32~22.04.1","6.8.0-1028.33~22.04.1","6.8.0-1029.34~22.04.1","6.8.0-1030.35~22.04.1","6.8.0-1031.36~22.04.1","6.8.0-1034.39~22.04.1","6.8.0-1036.42~22.04.1","6.8.0-1040.46~22.04.1","6.8.0-1041.47~22.04.1","6.8.0-1044.50~22.04.1","6.8.0-1051.57~22.04.1","6.8.0-1052.58~22.04.1"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-azure-fde-5.19","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.19.0-1025.28~22.04.1.1","5.19.0-1026.29~22.04.1.1","5.19.0-1027.30~22.04.2.1"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-azure-fde-6.2","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["6.2.0-1008.8~22.04.1.1","6.2.0-1009.9~22.04.3.1","6.2.0-1011.11~22.04.1.1","6.2.0-1012.12~22.04.1.1","6.2.0-1014.14~22.04.1.1","6.2.0-1015.15~22.04.1.1","6.2.0-1016.16~22.04.1.1","6.2.0-1017.17~22.04.1.1","6.2.0-1018.18~22.04.1.1","6.2.0-1019.19~22.04.1.1"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-azure-fde-6.8","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1058.65~22.04.1"}]}],"versions":["6.8.0-1041.48~22.04.1","6.8.0-1042.49~22.04.1","6.8.0-1044.51~22.04.1","6.8.0-1046.53~22.04.1","6.8.0-1053.60~22.04.1"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-gcp-5.19","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.19.0-1020.22~22.04.2","5.19.0-1021.23~22.04.1","5.19.0-1022.24~22.04.1","5.19.0-1024.26~22.04.1","5.19.0-1025.27~22.04.1","5.19.0-1026.28~22.04.1","5.19.0-1027.29~22.04.1","5.19.0-1030.32~22.04.1"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-gcp-6.2","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["6.2.0-1009.9~22.04.3","6.2.0-1010.10~22.04.1","6.2.0-1011.11~22.04.1","6.2.0-1011.11~22.04.3","6.2.0-1012.12~22.04.1","6.2.0-1013.13~22.04.1","6.2.0-1014.14~22.04.1","6.2.0-1016.18~22.04.1","6.2.0-1017.19~22.04.1","6.2.0-1018.20~22.04.1","6.2.0-1019.21~22.04.1","6.2.0-1021.23~22.04.1"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-gcp-6.5","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["6.5.0-1010.10~22.04.3","6.5.0-1011.11~22.04.1","6.5.0-1013.13~22.04.1","6.5.0-1014.14~22.04.1","6.5.0-1015.15~22.04.1","6.5.0-1016.16~22.04.1","6.5.0-1017.17~22.04.1","6.5.0-1018.18~22.04.1","6.5.0-1020.20~22.04.1","6.5.0-1022.24~22.04.1","6.5.0-1023.25~22.04.1","6.5.0-1024.26~22.04.1","6.5.0-1025.27~22.04.1"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-gcp-6.8","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1060.63~22.04.1"}]}],"versions":["6.8.0-1010.11~22.04.1","6.8.0-1011.12~22.04.1","6.8.0-1012.13~22.04.1","6.8.0-1013.14~22.04.1","6.8.0-1014.16~22.04.1","6.8.0-1015.17~22.04.1","6.8.0-1016.18~22.04.1","6.8.0-1017.19~22.04.1","6.8.0-1018.20~22.04.1","6.8.0-1019.21~22.04.1","6.8.0-1020.22~22.04.1","6.8.0-1021.23~22.04.1","6.8.0-1024.26~22.04.1","6.8.0-1025.27~22.04.1","6.8.0-1026.28~22.04.1","6.8.0-1027.29~22.04.1","6.8.0-1028.30~22.04.1","6.8.0-1029.31~22.04.1","6.8.0-1030.32~22.04.1","6.8.0-1031.33~22.04.1","6.8.0-1032.34~22.04.1","6.8.0-1033.35~22.04.1","6.8.0-1034.36~22.04.2","6.8.0-1036.38~22.04.1","6.8.0-1037.39~22.04.1","6.8.0-1040.42~22.04.1","6.8.0-1041.43~22.04.1","6.8.0-1042.45~22.04.1","6.8.0-1043.46~22.04.1","6.8.0-1044.47~22.04.1","6.8.0-1045.48~22.04.1","6.8.0-1046.49~22.04.1","6.8.0-1047.50~22.04.2","6.8.0-1048.51~22.04.1","6.8.0-1052.55~22.04.1","6.8.0-1053.56~22.04.1","6.8.0-1054.57~22.04.1","6.8.0-1058.61~22.04.1"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-hwe-5.19","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.19.0-28.29~22.04.1","5.19.0-32.33~22.04.1","5.19.0-35.36~22.04.1","5.19.0-38.39~22.04.1","5.19.0-40.41~22.04.1","5.19.0-41.42~22.04.1","5.19.0-42.43~22.04.1","5.19.0-43.44~22.04.1","5.19.0-45.46~22.04.1","5.19.0-46.47~22.04.1","5.19.0-50.50"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-hwe-6.2","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["6.2.0-25.25~22.04.2","6.2.0-26.26~22.04.1","6.2.0-31.31~22.04.1","6.2.0-32.32~22.04.1","6.2.0-33.33~22.04.1","6.2.0-34.34~22.04.1","6.2.0-35.35~22.04.1","6.2.0-36.37~22.04.1","6.2.0-37.38~22.04.1","6.2.0-39.40~22.04.1"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-hwe-6.5","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["6.5.0-14.14~22.04.1","6.5.0-15.15~22.04.1","6.5.0-17.17~22.04.1","6.5.0-18.18~22.04.1","6.5.0-21.21~22.04.1","6.5.0-25.25~22.04.1","6.5.0-26.26~22.04.1","6.5.0-27.28~22.04.1","6.5.0-28.29~22.04.1","6.5.0-35.35~22.04.1","6.5.0-41.41~22.04.2","6.5.0-44.44~22.04.1","6.5.0-45.45~22.04.1"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-hwe-6.8","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-124.124~22.04.1"}]}],"versions":["6.8.0-38.38~22.04.1","6.8.0-39.39~22.04.1","6.8.0-40.40~22.04.3","6.8.0-45.45~22.04.1","6.8.0-47.47~22.04.1","6.8.0-48.48~22.04.1","6.8.0-49.49~22.04.1","6.8.0-50.51~22.04.1","6.8.0-51.52~22.04.1","6.8.0-52.53~22.04.1","6.8.0-57.59~22.04.1","6.8.0-58.60~22.04.1","6.8.0-59.61~22.04.1","6.8.0-60.63~22.04.1","6.8.0-64.67~22.04.1","6.8.0-65.68~22.04.1","6.8.0-78.78~22.04.1","6.8.0-79.79~22.04.1","6.8.0-83.83~22.04.1","6.8.0-84.84~22.04.1","6.8.0-85.85~22.04.1","6.8.0-86.87~22.04.1","6.8.0-87.88~22.04.1","6.8.0-88.89~22.04.2","6.8.0-90.91~22.04.1","6.8.0-94.96~22.04.1","6.8.0-100.100~22.04.1","6.8.0-101.101~22.04.1","6.8.0-106.106~22.04.1","6.8.0-107.107~22.04.1","6.8.0-110.110~22.04.1","6.8.0-111.111~22.04.1","6.8.0-117.117~22.04.1"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-ibm-6.8","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1055.56~22.04.1"}]}],"versions":["6.8.0-1008.8~22.04.1","6.8.0-1010.10~22.04.1","6.8.0-1011.11~22.04.1","6.8.0-1012.12~22.04.1","6.8.0-1013.13~22.04.1","6.8.0-1014.14~22.04.1","6.8.0-1015.15~22.04.1","6.8.0-1016.16~22.04.1","6.8.0-1017.17~22.04.1","6.8.0-1018.18~22.04.1","6.8.0-1019.19~22.04.1","6.8.0-1023.23~22.04.1","6.8.0-1024.24~22.04.1","6.8.0-1025.25~22.04.1","6.8.0-1026.26~22.04.1","6.8.0-1027.27~22.04.1","6.8.0-1028.28~22.04.1","6.8.0-1029.29~22.04.1","6.8.0-1030.30~22.04.1","6.8.0-1033.33~22.04.1","6.8.0-1036.36~22.04.1","6.8.0-1037.37~22.04.1","6.8.0-1038.38~22.04.1","6.8.0-1039.39~22.04.1","6.8.0-1040.40~22.04.1","6.8.0-1041.41~22.04.1","6.8.0-1042.42~22.04.1","6.8.0-1043.43~22.04.1","6.8.0-1044.44~22.04.1","6.8.0-1045.45~22.04.1","6.8.0-1049.49~22.04.1","6.8.0-1050.50~22.04.1","6.8.0-1051.51~22.04.1","6.8.0-1052.52~22.04.1"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-intel-iot-realtime","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.15.0-1073.75"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-lowlatency-hwe-5.19","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.19.0-1017.18~22.04.1","5.19.0-1018.19~22.04.1","5.19.0-1021.22~22.04.1","5.19.0-1022.23~22.04.1","5.19.0-1023.24~22.04.1","5.19.0-1024.25~22.04.1","5.19.0-1025.26~22.04.1","5.19.0-1027.28~22.04.1","5.19.0-1028.29~22.04.1","5.19.0-1030.30"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-lowlatency-hwe-6.2","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["6.2.0-1008.8~22.04.1","6.2.0-1009.9~22.04.1","6.2.0-1011.11~22.04.1","6.2.0-1012.12~22.04.1","6.2.0-1013.13~22.04.1","6.2.0-1014.14~22.04.1","6.2.0-1015.15~22.04.1","6.2.0-1016.16~22.04.1","6.2.0-1017.17~22.04.1","6.2.0-1018.18~22.04.1"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-lowlatency-hwe-6.5","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["6.5.0-14.14.1~22.04.1","6.5.0-15.15.1.1~22.04.1","6.5.0-17.17.1.1.1~22.04.1","6.5.0-21.21.1~22.04.1","6.5.0-25.25.1~22.04.1","6.5.0-26.26.1~22.04.1","6.5.0-27.28.1~22.04.1","6.5.0-28.29.1~22.04.1","6.5.0-35.35.1~22.04.1","6.5.0-41.41.1~22.04.1","6.5.0-42.42.1~22.04.1","6.5.0-44.44.1~22.04.1","6.5.0-45.45.1~22.04.1"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-lowlatency-hwe-6.8","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-117.117.1~22.04.1"}]}],"versions":["6.8.0-38.38.1~22.04.2","6.8.0-40.40.1~22.04.1","6.8.0-44.44.1~22.04.1","6.8.0-45.45.1~22.04.1","6.8.0-47.47.1~22.04.1","6.8.0-48.48.3~22.04.1","6.8.0-49.49.1~22.04.1","6.8.0-50.51.1~22.04.1","6.8.0-51.52.1~22.04.1","6.8.0-52.53.1~22.04.1","6.8.0-54.56.1~22.04.1","6.8.0-55.57.1~22.04.1","6.8.0-56.58.1~22.04.1","6.8.0-57.59.1~22.04.1","6.8.0-58.60.1~22.04.1","6.8.0-59.61.1~22.04.1","6.8.0-60.63.1~22.04.1","6.8.0-62.65.1~22.04.1","6.8.0-63.66.1~22.04.1","6.8.0-64.67.1~22.04.1","6.8.0-65.68.1~22.04.1","6.8.0-78.78.1~22.04.1","6.8.0-79.79.1~22.04.1","6.8.0-83.83.1~22.04.1","6.8.0-84.84.1~22.04.1","6.8.0-85.85.1~22.04.1","6.8.0-86.87.1~22.04.1","6.8.0-87.88.1~22.04.1","6.8.0-88.89.1~22.04.1","6.8.0-90.91.1~22.04.1","6.8.0-94.96.1~22.04.1","6.8.0-100.100.1~22.04.1","6.8.0-101.101.1~22.04.1","6.8.0-106.106.1~22.04.1","6.8.0-107.107.1~22.04.1","6.8.0-110.110.1~22.04.1","6.8.0-111.111.1~22.04.1"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-nvidia-6.2","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["6.2.0-1003.3~22.04.1","6.2.0-1009.9","6.2.0-1010.10","6.2.0-1011.11","6.2.0-1012.12","6.2.0-1013.13","6.2.0-1015.15"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-nvidia-6.5","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["6.5.0-1004.4","6.5.0-1007.7","6.5.0-1013.13","6.5.0-1014.14","6.5.0-1015.15","6.5.0-1018.18","6.5.0-1019.19","6.5.0-1021.22","6.5.0-1022.23","6.5.0-1023.24","6.5.0-1024.25"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-nvidia-6.8","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1054.57~22.04.1"}]}],"versions":["6.8.0-1008.8~22.04.1","6.8.0-1009.9~22.04.1","6.8.0-1010.10~22.04.1","6.8.0-1011.11~22.04.1","6.8.0-1012.12~22.04.1","6.8.0-1013.14~22.04.1","6.8.0-1014.15~22.04.1","6.8.0-1015.16~22.04.1","6.8.0-1017.19~22.04.1","6.8.0-1018.20~22.04.1","6.8.0-1019.21~22.04.1","6.8.0-1020.22~22.04.1","6.8.0-1021.23~22.04.1","6.8.0-1022.25~22.04.2","6.8.0-1023.26~22.04.1","6.8.0-1024.27~22.04.1","6.8.0-1025.28~22.04.1","6.8.0-1026.29~22.04.1","6.8.0-1027.30~22.04.1","6.8.0-1028.31~22.04.1","6.8.0-1029.32~22.04.1","6.8.0-1030.33~22.04.1","6.8.0-1031.34~22.04.1","6.8.0-1032.35~22.04.1","6.8.0-1035.38~22.04.1","6.8.0-1036.39~22.04.1","6.8.0-1038.41~22.04.1","6.8.0-1039.42~22.04.1","6.8.0-1040.43~22.04.1","6.8.0-1041.44~22.04.2","6.8.0-1042.45~22.04.1","6.8.0-1043.46~22.04.1","6.8.0-1044.47~22.04.1","6.8.0-1045.48~22.04.1","6.8.0-1046.49~22.04.1","6.8.0-1047.50~22.04.1","6.8.0-1049.52~22.04.1","6.8.0-1050.53~22.04.1","6.8.0-1051.54~22.04.1","6.8.0-1052.55~22.04.1"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-oem-5.17","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.17.0-1003.3","5.17.0-1004.4","5.17.0-1006.6","5.17.0-1011.12","5.17.0-1012.13","5.17.0-1013.14","5.17.0-1014.15","5.17.0-1015.16","5.17.0-1016.17","5.17.0-1017.18","5.17.0-1018.19","5.17.0-1019.20","5.17.0-1020.21","5.17.0-1021.22","5.17.0-1024.25","5.17.0-1025.26","5.17.0-1026.27","5.17.0-1027.28","5.17.0-1028.29","5.17.0-1029.30","5.17.0-1030.31","5.17.0-1031.32","5.17.0-1032.33","5.17.0-1033.34","5.17.0-1034.35","5.17.0-1035.36"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-oem-6.0","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["6.0.0-1006.6","6.0.0-1007.7","6.0.0-1008.8","6.0.0-1009.9","6.0.0-1010.10","6.0.0-1011.11","6.0.0-1012.12","6.0.0-1013.13","6.0.0-1014.14","6.0.0-1015.15","6.0.0-1016.16","6.0.0-1017.17","6.0.0-1018.18","6.0.0-1019.19","6.0.0-1020.20","6.0.0-1021.21"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-oem-6.1","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["6.1.0-1004.4","6.1.0-1006.6","6.1.0-1007.7","6.1.0-1008.8","6.1.0-1009.9","6.1.0-1010.10","6.1.0-1012.12","6.1.0-1013.13","6.1.0-1014.14","6.1.0-1015.15","6.1.0-1016.16","6.1.0-1017.17","6.1.0-1019.19","6.1.0-1020.20","6.1.0-1021.21","6.1.0-1022.22","6.1.0-1023.23","6.1.0-1024.24","6.1.0-1025.25","6.1.0-1026.26","6.1.0-1027.27","6.1.0-1028.28","6.1.0-1029.29","6.1.0-1033.33","6.1.0-1034.34","6.1.0-1035.35","6.1.0-1036.36"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-oem-6.5","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["6.5.0-1003.3","6.5.0-1004.4","6.5.0-1006.6","6.5.0-1007.7","6.5.0-1008.8","6.5.0-1009.10","6.5.0-1011.12","6.5.0-1013.14","6.5.0-1014.15","6.5.0-1015.16","6.5.0-1016.17","6.5.0-1018.19","6.5.0-1019.20","6.5.0-1020.21","6.5.0-1022.23","6.5.0-1023.24","6.5.0-1024.25","6.5.0-1025.26","6.5.0-1027.28"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-oracle-6.5","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["6.5.0-1013.13~22.04.4","6.5.0-1014.14~22.04.1","6.5.0-1015.15~22.04.1","6.5.0-1016.16~22.04.1","6.5.0-1018.18~22.04.1","6.5.0-1019.19~22.04.1","6.5.0-1020.20~22.04.1","6.5.0-1021.21~22.04.1","6.5.0-1023.23~22.04.1","6.5.0-1024.24~22.04.1","6.5.0-1025.25~22.04.1","6.5.0-1026.26~22.04.1","6.5.0-1027.27~22.04.1"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-oracle-6.8","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1054.55~22.04.1"}]}],"versions":["6.8.0-1006.6~22.04.3","6.8.0-1008.8~22.04.1","6.8.0-1010.10~22.04.1","6.8.0-1011.11~22.04.1","6.8.0-1012.12~22.04.1","6.8.0-1013.13~22.04.1","6.8.0-1014.14~22.04.1","6.8.0-1015.15~22.04.1","6.8.0-1016.17~22.04.1","6.8.0-1017.18~22.04.1","6.8.0-1018.19~22.04.1","6.8.0-1019.20~22.04.1","6.8.0-1020.21~22.04.1","6.8.0-1021.22~22.04.1","6.8.0-1022.23~22.04.1","6.8.0-1023.24~22.04.1","6.8.0-1024.25~22.04.1","6.8.0-1025.26~22.04.1","6.8.0-1026.27~22.04.1","6.8.0-1027.28~22.04.1","6.8.0-1028.29~22.04.1","6.8.0-1029.30~22.04.1","6.8.0-1030.31~22.04.1","6.8.0-1032.33~22.04.1","6.8.0-1033.34~22.04.1","6.8.0-1035.36~22.04.1","6.8.0-1037.38~22.04.1","6.8.0-1038.39~22.04.1","6.8.0-1039.40~22.04.1","6.8.0-1040.41~22.04.1","6.8.0-1041.42~22.04.1","6.8.0-1042.43~22.04.1","6.8.0-1043.44~22.04.1","6.8.0-1044.45~22.04.1","6.8.0-1047.48~22.04.1","6.8.0-1049.50~22.04.1","6.8.0-1050.51~22.04.1","6.8.0-1052.53~22.04.1"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-realtime","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.15.0-1032.35"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-riscv","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.13.0-1004.4","5.13.0-1006.6+22.04.1","5.13.0-1007.7+22.04.1","5.13.0-1010.11+22.04.1","5.15.0-1004.4","5.15.0-1005.5","5.15.0-1006.6","5.15.0-1007.7","5.15.0-1008.8","5.15.0-1011.12","5.15.0-1012.13","5.15.0-1014.16","5.15.0-1015.17","5.15.0-1016.18","5.15.0-1017.19","5.15.0-1018.21","5.15.0-1019.22","5.15.0-1020.23","5.15.0-1022.26","5.15.0-1023.27","5.15.0-1026.30","5.15.0-1027.31","5.15.0-1028.32"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-riscv-5.19","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.19.0-1012.13~22.04.1","5.19.0-1015.16~22.04.1","5.19.0-1016.17~22.04.1","5.19.0-1017.18~22.04.1","5.19.0-1018.19~22.04.1","5.19.0-1019.21~22.04.1","5.19.0-1020.22~22.04.1","5.19.0-1021.23~22.04.1"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-riscv-6.5","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["6.5.0-17.17.1.1~22.04.1","6.5.0-21.21.1~22.04.1","6.5.0-25.25.1~22.04.1","6.5.0-26.26.1~22.04.1","6.5.0-27.28.1~22.04.1","6.5.0-28.29.1~22.04.1","6.5.0-35.35.1~22.04.1","6.5.0-40.40.1~22.04.1","6.5.0-42.42.1~22.04.1","6.5.0-45.45.1~22.04.1"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-riscv-6.8","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-117.117~22.04.1"}]}],"versions":["6.8.0-38.38.1~22.04.1","6.8.0-39.39.1~22.04.1","6.8.0-40.40.1~22.04.1","6.8.0-41.41.1~22.04.1","6.8.0-44.44.1~22.04.1","6.8.0-47.47.1~22.04.1","6.8.0-48.48.1~22.04.2","6.8.0-49.49.1~22.04.1","6.8.0-50.51.1~22.04.1","6.8.0-51.52.1~22.04.1","6.8.0-52.53.1~22.04.1","6.8.0-53.55.1~22.04.1","6.8.0-55.57.1~22.04.1","6.8.0-56.58.1~22.04.1","6.8.0-57.59.1~22.04.1","6.8.0-58.60.1~22.04.1","6.8.0-59.61.1~22.04.1","6.8.0-62.65~22.04.1","6.8.0-63.66~22.04.1","6.8.0-64.67~22.04.1","6.8.0-71.71~22.04.1","6.8.0-78.78~22.04.1","6.8.0-79.79~22.04.1","6.8.0-83.83~22.04.1","6.8.0-84.84~22.04.1","6.8.0-86.87~22.04.1","6.8.0-87.88~22.04.1","6.8.0-88.89~22.04.1","6.8.0-90.91~22.04.1","6.8.0-94.96~22.04.1","6.8.0-100.100~22.04.1","6.8.0-101.101~22.04.1","6.8.0-106.106~22.04.1","6.8.0-107.107~22.04.1","6.8.0-110.110~22.04.1","6.8.0-111.111~22.04.1"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-starfive-5.19","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.19.0-1014.16~22.04.1","5.19.0-1015.17~22.04.1","5.19.0-1016.18~22.04.1","5.19.0-1017.19~22.04.1","5.19.0-1018.20~22.04.1","5.19.0-1019.21~22.04.1","5.19.0-1020.22~22.04.1"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-starfive-6.2","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["6.2.0-1006.7~22.04.1","6.2.0-1007.8~22.04.1","6.2.0-1009.10~22.04.1"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-starfive-6.5","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["6.5.0-1007.8~22.04.1","6.5.0-1008.9~22.04.1","6.5.0-1009.10~22.04.1","6.5.0-1010.11~22.04.1","6.5.0-1011.12~22.04.1","6.5.0-1012.13~22.04.1","6.5.0-1014.15~22.04.1","6.5.0-1015.16~22.04.1","6.5.0-1016.17~22.04.1","6.5.0-1017.18~22.04.1","6.5.0-1018.19~22.04.1"]},{"source":"osv","ecosystem":"Ubuntu:Pro:Realtime:22.04:LTS","package":"linux-realtime-6.8","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.1-1051.52~22.04.1"}]}],"versions":["6.8.1-1004.4~22.04.1","6.8.1-1005.5~22.04.2","6.8.1-1006.6~22.04.1","6.8.1-1007.7~22.04.1","6.8.1-1008.8~22.04.1","6.8.1-1009.9~22.04.1","6.8.1-1010.10~22.04.1","6.8.1-1011.11~22.04.1","6.8.1-1012.12~22.04.1","6.8.1-1013.14~22.04.1","6.8.1-1014.15~22.04.1","6.8.1-1015.16~22.04.1","6.8.1-1016.17~22.04.1","6.8.1-1017.18~22.04.1","6.8.1-1018.19~22.04.1","6.8.1-1019.20~22.04.1","6.8.1-1020.21~22.04.1","6.8.1-1021.22~22.04.1","6.8.1-1022.23~22.04.1","6.8.1-1023.24~22.04.1","6.8.1-1024.25~22.04.1","6.8.1-1025.26~22.04.1","6.8.1-1026.27~22.04.1","6.8.1-1030.31~22.04.1","6.8.1-1031.32~22.04.1","6.8.1-1034.35~22.04.1","6.8.1-1035.36~22.04.1","6.8.1-1036.37~22.04.1","6.8.1-1037.38~22.04.1","6.8.1-1038.39~22.04.1","6.8.1-1039.40~22.04.1","6.8.1-1040.41~22.04.1","6.8.1-1041.42~22.04.1","6.8.1-1042.43~22.04.1","6.8.1-1045.46~22.04.1","6.8.1-1046.47~22.04.2","6.8.1-1047.48~22.04.1","6.8.1-1048.49~22.04.1"]},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-117.117"}]}],"versions":["6.5.0-9.9","6.6.0-14.14","6.8.0-11.11","6.8.0-20.20","6.8.0-22.22","6.8.0-28.28","6.8.0-31.31","6.8.0-35.35","6.8.0-36.36","6.8.0-38.38","6.8.0-39.39","6.8.0-40.40","6.8.0-41.41","6.8.0-44.44","6.8.0-45.45","6.8.0-47.47","6.8.0-48.48","6.8.0-49.49","6.8.0-50.51","6.8.0-51.52","6.8.0-52.53","6.8.0-53.55","6.8.0-54.56","6.8.0-55.57","6.8.0-56.58","6.8.0-57.59","6.8.0-58.60","6.8.0-59.61","6.8.0-60.63","6.8.0-62.65","6.8.0-63.66","6.8.0-64.67","6.8.0-71.71","6.8.0-78.78","6.8.0-79.79","6.8.0-83.83","6.8.0-84.84","6.8.0-85.85","6.8.0-86.87","6.8.0-87.88","6.8.0-88.89","6.8.0-90.91","6.8.0-94.96","6.8.0-100.100","6.8.0-101.101","6.8.0-106.106","6.8.0-107.107","6.8.0-110.110","6.8.0-111.111"]},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-aws","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1055.58"}]}],"versions":["6.5.0-1008.8","6.6.0-1001.1","6.8.0-1001.1","6.8.0-1006.6","6.8.0-1008.8","6.8.0-1009.9","6.8.0-1010.10","6.8.0-1011.12","6.8.0-1012.13","6.8.0-1013.14","6.8.0-1014.15","6.8.0-1015.16","6.8.0-1016.17","6.8.0-1017.18","6.8.0-1018.20","6.8.0-1019.21","6.8.0-1020.22","6.8.0-1021.23","6.8.0-1023.25","6.8.0-1024.26","6.8.0-1025.27","6.8.0-1026.28","6.8.0-1027.29","6.8.0-1028.30","6.8.0-1029.31","6.8.0-1030.32","6.8.0-1031.33","6.8.0-1032.34","6.8.0-1033.35","6.8.0-1035.37","6.8.0-1036.38","6.8.0-1038.40","6.8.0-1039.41","6.8.0-1040.42","6.8.0-1041.43","6.8.0-1042.44","6.8.0-1043.45","6.8.0-1044.46","6.8.0-1045.47","6.8.0-1046.49","6.8.0-1047.50","6.8.0-1050.53","6.8.0-1051.54","6.8.0-1052.55","6.8.0-1053.56"]},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-aws-6.14","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["6.14.0-1007.7~24.04.1","6.14.0-1009.9~24.04.1","6.14.0-1010.10~24.04.1","6.14.0-1011.11~24.04.1","6.14.0-1012.12~24.04.1","6.14.0-1013.13~24.04.1","6.14.0-1014.14~24.04.1","6.14.0-1015.15~24.04.1","6.14.0-1016.16~24.04.1","6.14.0-1017.17~24.04.1","6.14.0-1018.18~24.04.1"]},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-aws-6.17","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.17.0-1017.17~24.04.1"}]}],"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"]},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-azure","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1056.62"}]}],"versions":["6.5.0-1007.7","6.6.0-1001.1","6.8.0-1001.1","6.8.0-1005.5","6.8.0-1006.6","6.8.0-1007.7","6.8.0-1008.8","6.8.0-1009.9","6.8.0-1010.10","6.8.0-1012.14","6.8.0-1013.15","6.8.0-1014.16","6.8.0-1015.17","6.8.0-1016.18","6.8.0-1017.20","6.8.0-1018.21","6.8.0-1020.23","6.8.0-1021.25","6.8.0-1025.30","6.8.0-1026.31","6.8.0-1027.32","6.8.0-1028.33","6.8.0-1029.34","6.8.0-1030.35","6.8.0-1031.36","6.8.0-1034.39","6.8.0-1038.44","6.8.0-1040.46","6.8.0-1041.47","6.8.0-1042.48","6.8.0-1044.50","6.8.0-1046.52","6.8.0-1051.57","6.8.0-1052.58","6.8.0-1054.60"]},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-azure-6.11","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["6.11.0-1008.8~24.04.1","6.11.0-1012.12~24.04.1","6.11.0-1013.13~24.04.1","6.11.0-1014.14~24.04.1","6.11.0-1015.15~24.04.1","6.11.0-1017.17~24.04.1","6.11.0-1018.18~24.04.1"]},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-azure-6.14","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["6.14.0-1010.10~24.04.1","6.14.0-1012.12~24.04.1","6.14.0-1013.13~24.04.1","6.14.0-1014.14~24.04.1","6.14.0-1017.17~24.04.1"]},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-azure-6.17","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.17.0-1015.15~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"]},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-azure-fde","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1058.65"}]}],"versions":["6.8.0-1041.48","6.8.0-1044.51","6.8.0-1046.53","6.8.0-1053.60"]},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-azure-fde-6.14","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["6.14.0-1012.12~24.04.1","6.14.0-1013.13~24.04.1","6.14.0-1014.14~24.04.1","6.14.0-1015.15~24.04.1","6.14.0-1017.17~24.04.1"]},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-azure-nvidia-6.14","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["6.14.0-1003.3","6.14.0-1006.6","6.14.0-1007.7"]},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-gcp","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1058.61"}]}],"versions":["6.5.0-1007.7","6.6.0-1001.1","6.8.0-1002.2","6.8.0-1005.5","6.8.0-1006.6","6.8.0-1007.7","6.8.0-1008.9","6.8.0-1009.10","6.8.0-1010.11","6.8.0-1011.12","6.8.0-1012.13","6.8.0-1013.14","6.8.0-1014.16","6.8.0-1015.17","6.8.0-1016.18","6.8.0-1017.19","6.8.0-1018.20","6.8.0-1019.21","6.8.0-1020.22","6.8.0-1021.23","6.8.0-1024.26","6.8.0-1025.27","6.8.0-1026.28","6.8.0-1027.29","6.8.0-1028.30","6.8.0-1029.31","6.8.0-1030.32","6.8.0-1031.33","6.8.0-1032.34","6.8.0-1033.35","6.8.0-1034.36","6.8.0-1036.38","6.8.0-1037.39","6.8.0-1039.41","6.8.0-1040.42","6.8.0-1041.43","6.8.0-1042.45","6.8.0-1043.46","6.8.0-1044.47","6.8.0-1045.48","6.8.0-1046.49","6.8.0-1047.50","6.8.0-1048.51","6.8.0-1052.55","6.8.0-1053.56","6.8.0-1054.57","6.8.0-1055.58"]},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-gcp-6.11","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["6.11.0-1006.6~24.04.2","6.11.0-1011.11~24.04.1","6.11.0-1013.13~24.04.1","6.11.0-1014.14~24.04.1","6.11.0-1015.15~24.04.1","6.11.0-1016.16~24.04.1","6.11.0-1017.17~24.04.1"]},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-gcp-6.14","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["6.14.0-1007.7~24.04.1","6.14.0-1011.11~24.04.1","6.14.0-1012.12~24.04.1","6.14.0-1014.15~24.04.1","6.14.0-1015.16~24.04.1","6.14.0-1016.17~24.04.1","6.14.0-1017.18~24.04.1","6.14.0-1018.19~24.04.1","6.14.0-1019.20~24.04.1","6.14.0-1020.21~24.04.1","6.14.0-1021.22~24.04.1"]},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-gcp-6.17","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.17.0-1018.19~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"]},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-gke","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1054.60"}]}],"versions":["6.8.0-1003.5","6.8.0-1004.7","6.8.0-1005.8","6.8.0-1006.9","6.8.0-1007.10","6.8.0-1008.11","6.8.0-1009.12","6.8.0-1010.13","6.8.0-1011.14","6.8.0-1012.15","6.8.0-1013.17","6.8.0-1014.18","6.8.0-1015.19","6.8.0-1016.20","6.8.0-1017.21","6.8.0-1019.23","6.8.0-1020.24","6.8.0-1021.25","6.8.0-1022.26","6.8.0-1023.27","6.8.0-1024.28","6.8.0-1025.29","6.8.0-1026.30","6.8.0-1027.31","6.8.0-1028.32","6.8.0-1029.33","6.8.0-1032.36","6.8.0-1033.37","6.8.0-1035.39","6.8.0-1036.40","6.8.0-1037.41","6.8.0-1038.43","6.8.0-1039.44","6.8.0-1040.45","6.8.0-1041.46","6.8.0-1042.47","6.8.0-1043.48","6.8.0-1044.49","6.8.0-1048.53","6.8.0-1049.54","6.8.0-1050.56","6.8.0-1051.57"]},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-gkeop","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1041.44"}]}],"versions":["6.8.0-1001.3","6.8.0-1002.4","6.8.0-1003.5","6.8.0-1004.6","6.8.0-1006.8","6.8.0-1007.9","6.8.0-1008.10","6.8.0-1009.11","6.8.0-1010.12","6.8.0-1011.13","6.8.0-1012.14","6.8.0-1013.15","6.8.0-1014.16","6.8.0-1015.17","6.8.0-1016.18","6.8.0-1019.21","6.8.0-1020.22","6.8.0-1022.24","6.8.0-1023.25","6.8.0-1024.26","6.8.0-1025.28","6.8.0-1026.29","6.8.0-1027.30","6.8.0-1028.31","6.8.0-1029.32","6.8.0-1030.33","6.8.0-1031.34","6.8.0-1035.38","6.8.0-1036.39","6.8.0-1037.40","6.8.0-1038.41"]},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-hwe-6.11","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["6.11.0-17.17~24.04.2","6.11.0-19.19~24.04.1","6.11.0-21.21~24.04.1","6.11.0-24.24~24.04.1","6.11.0-25.25~24.04.1","6.11.0-26.26~24.04.1","6.11.0-28.28~24.04.1","6.11.0-29.29~24.04.1"]},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-hwe-6.14","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["6.14.0-24.24~24.04.3","6.14.0-27.27~24.04.1","6.14.0-28.28~24.04.1","6.14.0-29.29~24.04.1","6.14.0-32.32~24.04.1","6.14.0-33.33~24.04.1","6.14.0-34.34~24.04.1","6.14.0-35.35~24.04.1","6.14.0-36.36~24.04.1","6.14.0-37.37~24.04.1"]},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-hwe-6.17","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.17.0-29.29~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"]},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-ibm","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1055.56"}]}],"versions":["6.5.0-1009.9","6.8.0-1001.1","6.8.0-1003.3","6.8.0-1004.4","6.8.0-1005.5","6.8.0-1006.6","6.8.0-1007.7","6.8.0-1008.8","6.8.0-1009.9","6.8.0-1010.10","6.8.0-1011.11","6.8.0-1012.12","6.8.0-1013.13","6.8.0-1014.14","6.8.0-1015.15","6.8.0-1016.16","6.8.0-1017.17","6.8.0-1018.18","6.8.0-1019.19","6.8.0-1022.22","6.8.0-1023.23","6.8.0-1024.24","6.8.0-1025.25","6.8.0-1026.26","6.8.0-1027.27","6.8.0-1028.28","6.8.0-1029.29","6.8.0-1030.30","6.8.0-1033.33","6.8.0-1036.36","6.8.0-1037.37","6.8.0-1038.38","6.8.0-1039.39","6.8.0-1040.40","6.8.0-1041.41","6.8.0-1042.42","6.8.0-1043.43","6.8.0-1044.44","6.8.0-1045.45","6.8.0-1049.49","6.8.0-1050.50","6.8.0-1051.51","6.8.0-1052.52"]},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-lowlatency","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-117.117.1"}]}],"versions":["6.5.0-9.9.1","6.6.0-14.14.1","6.8.0-7.7.1","6.8.0-25.25.3","6.8.0-28.28.1","6.8.0-31.31.1","6.8.0-35.35.1","6.8.0-36.36.1","6.8.0-38.38.1","6.8.0-39.39.1","6.8.0-40.40.1","6.8.0-41.41.1","6.8.0-44.44.1","6.8.0-45.45.1","6.8.0-47.47.1","6.8.0-48.48.3","6.8.0-49.49.1","6.8.0-50.51.1","6.8.0-51.52.1","6.8.0-52.53.1","6.8.0-53.55.2","6.8.0-54.56.1","6.8.0-55.57.1","6.8.0-56.58.1","6.8.0-57.59.1","6.8.0-58.60.1","6.8.0-59.61.1","6.8.0-60.63.1","6.8.0-62.65.1","6.8.0-63.66.1","6.8.0-64.67.1","6.8.0-65.68.1","6.8.0-78.78.1","6.8.0-79.79.1","6.8.0-83.83.1","6.8.0-84.84.1","6.8.0-85.85.1","6.8.0-86.87.1","6.8.0-87.88.1","6.8.0-88.89.1","6.8.0-90.91.1","6.8.0-94.96.1","6.8.0-100.100.1","6.8.0-101.101.1","6.8.0-106.106.1","6.8.0-107.107.1","6.8.0-110.110.1","6.8.0-111.111.1"]},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-lowlatency-hwe-6.11","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["6.11.0-1009.10~24.04.1","6.11.0-1011.12~24.04.1","6.11.0-1012.13~24.04.1","6.11.0-1013.14~24.04.1","6.11.0-1014.15~24.04.1","6.11.0-1015.16~24.04.2","6.11.0-1016.17~24.04.1"]},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-nvidia","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1054.57"}]}],"versions":["6.8.0-1007.7","6.8.0-1008.8","6.8.0-1009.9","6.8.0-1010.10","6.8.0-1011.11","6.8.0-1012.12","6.8.0-1013.14","6.8.0-1014.15","6.8.0-1015.16","6.8.0-1017.19","6.8.0-1018.20","6.8.0-1019.21","6.8.0-1020.22","6.8.0-1021.23","6.8.0-1022.25","6.8.0-1023.26","6.8.0-1024.27","6.8.0-1025.28","6.8.0-1026.29","6.8.0-1027.30","6.8.0-1028.31","6.8.0-1029.32","6.8.0-1030.33","6.8.0-1031.34","6.8.0-1032.35","6.8.0-1035.38","6.8.0-1036.39","6.8.0-1038.41","6.8.0-1039.42","6.8.0-1040.43","6.8.0-1041.44","6.8.0-1042.45","6.8.0-1043.46","6.8.0-1044.47","6.8.0-1045.48","6.8.0-1046.49","6.8.0-1047.50","6.8.0-1049.52","6.8.0-1050.53","6.8.0-1051.54","6.8.0-1052.55"]},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-nvidia-6.11","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["6.11.0-1002.2","6.11.0-1003.3","6.11.0-1007.7","6.11.0-1010.10","6.11.0-1011.11","6.11.0-1012.12","6.11.0-1013.13","6.11.0-1016.16"]},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-nvidia-6.17","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.17.0-1026.26"}]}],"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"]},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-nvidia-lowlatency","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1054.57.1"}]}],"versions":["6.8.0-1009.9.1","6.8.0-1011.11.1","6.8.0-1012.12.1","6.8.0-1013.14.1","6.8.0-1014.15.1","6.8.0-1015.16.1","6.8.0-1017.19.1","6.8.0-1018.20.1","6.8.0-1019.21.1","6.8.0-1020.22.1","6.8.0-1021.23.1","6.8.0-1022.25.2","6.8.0-1023.26.1","6.8.0-1024.27.1","6.8.0-1025.28.1","6.8.0-1026.29.1","6.8.0-1027.30.1","6.8.0-1028.31.1","6.8.0-1029.32.1","6.8.0-1030.33.1","6.8.0-1031.34.1","6.8.0-1032.35.1","6.8.0-1035.38.1","6.8.0-1036.39.1","6.8.0-1038.41.1","6.8.0-1039.42.1","6.8.0-1040.43.1","6.8.0-1041.44.1","6.8.0-1042.45.1","6.8.0-1043.46.1","6.8.0-1044.47.1","6.8.0-1045.48.1","6.8.0-1046.49.1","6.8.0-1047.50.1","6.8.0-1049.52.1","6.8.0-1050.53.1","6.8.0-1051.54.1","6.8.0-1052.55.1"]},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-nvidia-tegra","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1024.24"}]}],"versions":["6.8.0-1003.3","6.8.0-1004.4","6.8.0-1008.8","6.8.0-1009.9","6.8.0-1010.10","6.8.0-1012.12","6.8.0-1013.13","6.8.0-1016.16","6.8.0-1019.19","6.8.0-1020.20","6.8.0-1021.21","6.8.0-1022.22","6.8.0-1023.23"]},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-oem-6.11","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["6.11.0-1007.7","6.11.0-1008.8","6.11.0-1009.9","6.11.0-1010.10","6.11.0-1011.11","6.11.0-1012.12","6.11.0-1013.13","6.11.0-1015.15","6.11.0-1016.16","6.11.0-1017.17","6.11.0-1018.18","6.11.0-1020.20","6.11.0-1021.21","6.11.0-1022.22","6.11.0-1023.23","6.11.0-1024.24","6.11.0-1025.25","6.11.0-1027.27"]},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-oem-6.14","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["6.14.0-1004.4","6.14.0-1005.5","6.14.0-1006.6","6.14.0-1007.7","6.14.0-1008.8","6.14.0-1010.10","6.14.0-1011.11","6.14.0-1012.12","6.14.0-1013.13","6.14.0-1014.14","6.14.0-1015.15","6.14.0-1016.16","6.14.0-1017.17","6.14.0-1018.18","6.14.0-1019.19","6.14.0-1020.20"]},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-oem-6.17","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.17.0-1023.23"}]}],"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"]},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-oem-6.8","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["6.8.0-1003.3","6.8.0-1004.4","6.8.0-1005.5","6.8.0-1006.6","6.8.0-1007.7","6.8.0-1008.8","6.8.0-1009.9","6.8.0-1010.10","6.8.0-1011.11","6.8.0-1012.12","6.8.0-1013.13","6.8.0-1014.14","6.8.0-1016.16","6.8.0-1017.17","6.8.0-1018.18","6.8.0-1019.19","6.8.0-1020.20","6.8.0-1024.24","6.8.0-1025.25","6.8.0-1026.26","6.8.0-1027.27","6.8.0-1028.28","6.8.0-1029.29","6.8.0-1030.30","6.8.0-1031.31","6.8.0-1032.32"]},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-oracle","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1054.55"}]}],"versions":["6.5.0-1010.10","6.6.0-1001.1","6.8.0-1001.1","6.8.0-1004.4","6.8.0-1005.5","6.8.0-1006.6","6.8.0-1008.8","6.8.0-1010.10","6.8.0-1011.11","6.8.0-1012.12","6.8.0-1013.13","6.8.0-1014.14","6.8.0-1015.16","6.8.0-1016.17","6.8.0-1017.18","6.8.0-1018.19","6.8.0-1019.20","6.8.0-1020.21","6.8.0-1021.22","6.8.0-1022.23","6.8.0-1023.24","6.8.0-1024.25","6.8.0-1025.26","6.8.0-1026.27","6.8.0-1027.28","6.8.0-1028.29","6.8.0-1029.30","6.8.0-1030.31","6.8.0-1032.33","6.8.0-1033.34","6.8.0-1035.36","6.8.0-1037.38","6.8.0-1038.39","6.8.0-1039.40","6.8.0-1040.41","6.8.0-1041.42","6.8.0-1042.43","6.8.0-1043.44","6.8.0-1044.45","6.8.0-1047.48","6.8.0-1049.50","6.8.0-1050.51","6.8.0-1052.53"]},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-oracle-6.14","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["6.14.0-1007.7~24.04.1","6.14.0-1009.9~24.04.1","6.14.0-1010.10~24.04.1","6.14.0-1011.11~24.04.1","6.14.0-1012.12~24.04.1","6.14.0-1013.13~24.04.1","6.14.0-1014.14~24.04.1","6.14.0-1015.15~24.04.1","6.14.0-1016.16~24.04.1","6.14.0-1017.17~24.04.1","6.14.0-1018.18~24.04.1"]},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-oracle-6.17","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.17.0-1014.14~24.04.1"}]}],"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"]},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-raspi","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1056.60"}]}],"versions":["6.5.0-1005.7","6.7.0-1001.1","6.8.0-1001.1","6.8.0-1002.2","6.8.0-1003.3","6.8.0-1004.4","6.8.0-1005.5","6.8.0-1006.6","6.8.0-1007.7","6.8.0-1008.8","6.8.0-1009.10","6.8.0-1010.11","6.8.0-1011.12","6.8.0-1012.13","6.8.0-1013.14","6.8.0-1014.16","6.8.0-1015.17","6.8.0-1016.18","6.8.0-1017.19","6.8.0-1018.20","6.8.0-1019.23","6.8.0-1020.24","6.8.0-1024.28","6.8.0-1028.32","6.8.0-1029.33","6.8.0-1030.34","6.8.0-1031.35","6.8.0-1032.36","6.8.0-1035.39","6.8.0-1036.40","6.8.0-1038.42","6.8.0-1039.43","6.8.0-1040.44","6.8.0-1041.45","6.8.0-1042.46","6.8.0-1043.47","6.8.0-1044.48","6.8.0-1045.49","6.8.0-1047.51","6.8.0-1048.52","6.8.0-1050.54","6.8.0-1051.55","6.8.0-1052.56","6.8.0-1053.57"]},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-raspi-realtime","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["6.8.0-2019.20"]},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-realtime","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["6.8.1-1015.16"]},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-riscv","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["6.5.0-9.9.1","6.8.0-20.20.1","6.8.0-28.28.1","6.8.0-31.31.1","6.8.0-35.35.1","6.8.0-36.36.1","6.8.0-38.38.1","6.8.0-39.39.1","6.8.0-40.40.1","6.8.0-41.41.1","6.8.0-44.44.1","6.8.0-47.47.1","6.8.0-48.48.1","6.8.0-49.49.1","6.8.0-50.51.1","6.8.0-51.52.1","6.8.0-52.53.1","6.8.0-53.55.1","6.8.0-55.57.1","6.8.0-56.58.1","6.8.0-57.59.1","6.8.0-58.60.1","6.8.0-59.61.1","6.8.0-60.63.1"]},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-riscv-6.14","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["6.14.0-22.22.1~24.04.1","6.14.0-23.23.1~24.04.1","6.14.0-24.24.1~24.04.1","6.14.0-27.27.1~24.04.1","6.14.0-28.28.1~24.04.1","6.14.0-29.29.1~24.04.1","6.14.0-32.32.1~24.04.1","6.14.0-33.33.1~24.04.1","6.14.0-34.34.1~24.04.1","6.14.0-35.35.1~24.04.1","6.14.0-36.36.1~24.04.1","6.14.0-37.37.1~24.04.1"]},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-riscv-6.17","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.17.0-29.29.1~24.04.1"}]}],"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"]},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-xilinx","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1032.33"}]}],"versions":["6.8.0-1008.9","6.8.0-1009.10","6.8.0-1011.12","6.8.0-1012.13","6.8.0-1013.14","6.8.0-1014.15","6.8.0-1015.16","6.8.0-1017.18","6.8.0-1018.19","6.8.0-1019.20","6.8.0-1020.21","6.8.0-1021.22","6.8.0-1022.23","6.8.0-1023.24","6.8.0-1024.25","6.8.0-1028.29","6.8.0-1029.30"]},{"source":"osv","ecosystem":"Ubuntu:Nvidia-BlueField:24.04:LTS","package":"linux-bluefield","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1022.26"}]}],"versions":["6.8.0-1011.15","6.8.0-1012.16","6.8.0-1013.17","6.8.0-1014.18","6.8.0-1016.20","6.8.0-1017.21"]},{"source":"osv","ecosystem":"Ubuntu:Pro:Realtime:24.04:LTS","package":"linux-raspi-realtime","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-2045.46"}]}],"versions":["6.7.0-2001.1","6.8.0-2001.1","6.8.0-2002.2","6.8.0-2004.4","6.8.0-2005.5","6.8.0-2006.6","6.8.0-2007.7","6.8.0-2008.8","6.8.0-2009.9","6.8.0-2010.10","6.8.0-2011.11","6.8.0-2012.12","6.8.0-2013.14","6.8.0-2014.15","6.8.0-2015.16","6.8.0-2016.17","6.8.0-2017.18","6.8.0-2018.19","6.8.0-2019.20","6.8.0-2022.23","6.8.0-2023.24","6.8.0-2024.25","6.8.0-2025.26","6.8.0-2026.27","6.8.0-2028.29","6.8.0-2029.30","6.8.0-2030.31","6.8.0-2031.32","6.8.0-2032.33","6.8.0-2033.34","6.8.0-2034.35","6.8.0-2035.36","6.8.0-2036.37","6.8.0-2037.38","6.8.0-2038.39","6.8.0-2040.41","6.8.0-2041.42","6.8.0-2042.43","6.8.0-2043.44"]},{"source":"osv","ecosystem":"Ubuntu:Pro:Realtime:24.04:LTS","package":"linux-realtime","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.1-1051.52"}]}],"versions":["6.8.0-1008.19","6.8.1-1001.1","6.8.1-1002.2","6.8.1-1003.3","6.8.1-1004.4","6.8.1-1005.5","6.8.1-1006.6","6.8.1-1007.7","6.8.1-1008.8","6.8.1-1009.9","6.8.1-1010.10","6.8.1-1011.11","6.8.1-1012.12","6.8.1-1013.14","6.8.1-1014.15","6.8.1-1015.16","6.8.1-1016.17","6.8.1-1017.18","6.8.1-1018.19","6.8.1-1019.20","6.8.1-1020.21","6.8.1-1021.22","6.8.1-1022.23","6.8.1-1023.24","6.8.1-1024.25","6.8.1-1025.26","6.8.1-1026.27","6.8.1-1030.31","6.8.1-1031.32","6.8.1-1033.34","6.8.1-1034.35","6.8.1-1035.36","6.8.1-1036.37","6.8.1-1037.38","6.8.1-1038.39","6.8.1-1039.40","6.8.1-1040.41","6.8.1-1041.42","6.8.1-1042.43","6.8.1-1045.46","6.8.1-1046.47","6.8.1-1047.48","6.8.1-1048.49"]},{"source":"osv","ecosystem":"Ubuntu:Pro:Realtime:24.04:LTS","package":"linux-realtime-6.14","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["6.14.0-1003.3~24.04.3","6.14.0-1010.10~24.04.1","6.14.0-1011.11~24.04.1","6.14.0-1012.12~24.04.1","6.14.0-1013.13~24.04.1","6.14.0-1014.14~24.04.1","6.14.0-1015.15~24.04.1","6.14.0-1016.16~24.04.1","6.14.0-1017.17~24.04.1"]},{"source":"osv","ecosystem":"Ubuntu:Pro:Realtime:24.04:LTS","package":"linux-realtime-6.17","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.17.0-1013.15~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"]},{"source":"osv","ecosystem":"Ubuntu:Pro:FIPS-updates:24.04:LTS","package":"linux-aws-fips","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1055.58+fips1"}]}],"versions":["6.8.0-1035.37+fips1","6.8.0-1036.38+fips1","6.8.0-1038.40+fips1","6.8.0-1039.41+fips1","6.8.0-1040.42+fips1","6.8.0-1041.43+fips1","6.8.0-1042.44+fips1","6.8.0-1043.45+fips1","6.8.0-1044.46+fips1","6.8.0-1045.47+fips1","6.8.0-1046.49+fips1","6.8.0-1047.50+fips1","6.8.0-1050.53+fips1","6.8.0-1051.54+fips1","6.8.0-1052.55+fips1","6.8.0-1053.56+fips1"]},{"source":"osv","ecosystem":"Ubuntu:Pro:FIPS-updates:24.04:LTS","package":"linux-azure-fips","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1059.65+fips1"}]}],"versions":["6.8.0-1034.39+fips1","6.8.0-1040.46+fips1","6.8.0-1044.50+fips1","6.8.0-1046.52+fips1","6.8.0-1047.53+fips1","6.8.0-1052.58+fips1","6.8.0-1053.59+fips1","6.8.0-1054.60+fips1"]},{"source":"osv","ecosystem":"Ubuntu:Pro:FIPS-updates:24.04:LTS","package":"linux-fips","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-116.116+fips1"}]}],"versions":["6.8.0-38.38+fips4","6.8.0-78.78+fips1","6.8.0-79.79+fips1","6.8.0-83.83+fips1","6.8.0-84.84+fips1","6.8.0-85.85+fips1","6.8.0-86.87+fips1","6.8.0-87.88+fips1","6.8.0-88.89+fips1","6.8.0-90.91+fips1","6.8.0-94.96+fips1","6.8.0-100.100+fips1","6.8.0-101.101+fips1","6.8.0-106.106+fips1","6.8.0-107.107+fips1","6.8.0-110.110+fips2","6.8.0-111.111+fips1"]},{"source":"osv","ecosystem":"Ubuntu:Pro:FIPS-updates:24.04:LTS","package":"linux-gcp-fips","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1058.61+fips1"}]}],"versions":["6.8.0-1036.38+fips1","6.8.0-1037.39+fips1","6.8.0-1039.41+fips1","6.8.0-1040.42+fips1","6.8.0-1041.43+fips1","6.8.0-1042.45+fips1","6.8.0-1043.46+fips1","6.8.0-1044.47+fips1","6.8.0-1045.48+fips1","6.8.0-1046.49+fips1","6.8.0-1047.50+fips1","6.8.0-1048.51+fips1","6.8.0-1052.55+fips1","6.8.0-1053.56+fips1","6.8.0-1054.57+fips1","6.8.0-1055.58+fips1"]},{"source":"osv","ecosystem":"Ubuntu:25.10","package":"linux","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.17.0-29.29"}]}],"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"]},{"source":"osv","ecosystem":"Ubuntu:25.10","package":"linux-aws","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.17.0-1015.15"}]}],"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"]},{"source":"osv","ecosystem":"Ubuntu:25.10","package":"linux-azure","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.17.0-1015.15"}]}],"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"]},{"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"},{"fixed":"6.17.0-1018.19"}]}],"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"]},{"source":"osv","ecosystem":"Ubuntu:25.10","package":"linux-oracle","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.17.0-1014.14"}]}],"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"]},{"source":"osv","ecosystem":"Ubuntu:25.10","package":"linux-raspi","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.17.0-1017.17"}]}],"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"]},{"source":"osv","ecosystem":"Ubuntu:25.10","package":"linux-realtime","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.17.0-1013.15"}]}],"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"]},{"source":"osv","ecosystem":"Ubuntu:25.10","package":"linux-riscv","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.17.0-29.29.1"}]}],"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"]},{"source":"osv","ecosystem":"Ubuntu:26.04:LTS","package":"linux-vmware","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["7.0.0-1006.6"]},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-hwe-6.17","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.17.0-29.29~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"],"bundled":20},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-oem-6.17","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.17.0-1023.23"}]}],"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"],"bundled":20},{"source":"osv","ecosystem":"Ubuntu:Pro:Realtime:24.04:LTS","package":"linux-realtime-6.17","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.17.0-1013.15~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"],"bundled":20},{"source":"osv","ecosystem":"Ubuntu:25.10","package":"linux","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.17.0-29.29"}]}],"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"],"bundled":20},{"source":"osv","ecosystem":"Ubuntu:25.10","package":"linux-aws","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.17.0-1015.15"}]}],"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"],"bundled":20},{"source":"osv","ecosystem":"Ubuntu:25.10","package":"linux-oracle","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.17.0-1014.14"}]}],"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"],"bundled":20},{"source":"osv","ecosystem":"Ubuntu:25.10","package":"linux-raspi","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.17.0-1017.17"}]}],"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"],"bundled":20},{"source":"osv","ecosystem":"Ubuntu:25.10","package":"linux-realtime","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.17.0-1013.15"}]}],"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"],"bundled":20},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-oracle-6.17","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.17.0-1014.14~24.04.1"}]}],"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"],"bundled":20},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-ibm-6.8","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1055.56~22.04.1"}]}],"versions":["6.8.0-1008.8~22.04.1","6.8.0-1010.10~22.04.1","6.8.0-1011.11~22.04.1","6.8.0-1012.12~22.04.1","6.8.0-1013.13~22.04.1","6.8.0-1014.14~22.04.1","6.8.0-1015.15~22.04.1","6.8.0-1016.16~22.04.1","6.8.0-1017.17~22.04.1","6.8.0-1018.18~22.04.1","6.8.0-1019.19~22.04.1","6.8.0-1023.23~22.04.1","6.8.0-1024.24~22.04.1","6.8.0-1025.25~22.04.1","6.8.0-1026.26~22.04.1","6.8.0-1027.27~22.04.1","6.8.0-1028.28~22.04.1","6.8.0-1029.29~22.04.1","6.8.0-1030.30~22.04.1","6.8.0-1033.33~22.04.1","6.8.0-1036.36~22.04.1","6.8.0-1037.37~22.04.1","6.8.0-1038.38~22.04.1","6.8.0-1039.39~22.04.1","6.8.0-1040.40~22.04.1","6.8.0-1041.41~22.04.1","6.8.0-1042.42~22.04.1","6.8.0-1043.43~22.04.1","6.8.0-1044.44~22.04.1","6.8.0-1045.45~22.04.1","6.8.0-1049.49~22.04.1","6.8.0-1050.50~22.04.1","6.8.0-1051.51~22.04.1","6.8.0-1052.52~22.04.1"],"bundled":196},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-lowlatency-hwe-6.8","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-117.117.1~22.04.1"}]}],"versions":["6.8.0-38.38.1~22.04.2","6.8.0-40.40.1~22.04.1","6.8.0-44.44.1~22.04.1","6.8.0-45.45.1~22.04.1","6.8.0-47.47.1~22.04.1","6.8.0-48.48.3~22.04.1","6.8.0-49.49.1~22.04.1","6.8.0-50.51.1~22.04.1","6.8.0-51.52.1~22.04.1","6.8.0-52.53.1~22.04.1","6.8.0-54.56.1~22.04.1","6.8.0-55.57.1~22.04.1","6.8.0-56.58.1~22.04.1","6.8.0-57.59.1~22.04.1","6.8.0-58.60.1~22.04.1","6.8.0-59.61.1~22.04.1","6.8.0-60.63.1~22.04.1","6.8.0-62.65.1~22.04.1","6.8.0-63.66.1~22.04.1","6.8.0-64.67.1~22.04.1","6.8.0-65.68.1~22.04.1","6.8.0-78.78.1~22.04.1","6.8.0-79.79.1~22.04.1","6.8.0-83.83.1~22.04.1","6.8.0-84.84.1~22.04.1","6.8.0-85.85.1~22.04.1","6.8.0-86.87.1~22.04.1","6.8.0-87.88.1~22.04.1","6.8.0-88.89.1~22.04.1","6.8.0-90.91.1~22.04.1","6.8.0-94.96.1~22.04.1","6.8.0-100.100.1~22.04.1","6.8.0-101.101.1~22.04.1","6.8.0-106.106.1~22.04.1","6.8.0-107.107.1~22.04.1","6.8.0-110.110.1~22.04.1","6.8.0-111.111.1~22.04.1"],"bundled":196},{"source":"osv","ecosystem":"Ubuntu:Pro:Realtime:22.04:LTS","package":"linux-realtime-6.8","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.1-1051.52~22.04.1"}]}],"versions":["6.8.1-1004.4~22.04.1","6.8.1-1005.5~22.04.2","6.8.1-1006.6~22.04.1","6.8.1-1007.7~22.04.1","6.8.1-1008.8~22.04.1","6.8.1-1009.9~22.04.1","6.8.1-1010.10~22.04.1","6.8.1-1011.11~22.04.1","6.8.1-1012.12~22.04.1","6.8.1-1013.14~22.04.1","6.8.1-1014.15~22.04.1","6.8.1-1015.16~22.04.1","6.8.1-1016.17~22.04.1","6.8.1-1017.18~22.04.1","6.8.1-1018.19~22.04.1","6.8.1-1019.20~22.04.1","6.8.1-1020.21~22.04.1","6.8.1-1021.22~22.04.1","6.8.1-1022.23~22.04.1","6.8.1-1023.24~22.04.1","6.8.1-1024.25~22.04.1","6.8.1-1025.26~22.04.1","6.8.1-1026.27~22.04.1","6.8.1-1030.31~22.04.1","6.8.1-1031.32~22.04.1","6.8.1-1034.35~22.04.1","6.8.1-1035.36~22.04.1","6.8.1-1036.37~22.04.1","6.8.1-1037.38~22.04.1","6.8.1-1038.39~22.04.1","6.8.1-1039.40~22.04.1","6.8.1-1040.41~22.04.1","6.8.1-1041.42~22.04.1","6.8.1-1042.43~22.04.1","6.8.1-1045.46~22.04.1","6.8.1-1046.47~22.04.2","6.8.1-1047.48~22.04.1","6.8.1-1048.49~22.04.1"],"bundled":196},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-117.117"}]}],"versions":["6.5.0-9.9","6.6.0-14.14","6.8.0-11.11","6.8.0-20.20","6.8.0-22.22","6.8.0-28.28","6.8.0-31.31","6.8.0-35.35","6.8.0-36.36","6.8.0-38.38","6.8.0-39.39","6.8.0-40.40","6.8.0-41.41","6.8.0-44.44","6.8.0-45.45","6.8.0-47.47","6.8.0-48.48","6.8.0-49.49","6.8.0-50.51","6.8.0-51.52","6.8.0-52.53","6.8.0-53.55","6.8.0-54.56","6.8.0-55.57","6.8.0-56.58","6.8.0-57.59","6.8.0-58.60","6.8.0-59.61","6.8.0-60.63","6.8.0-62.65","6.8.0-63.66","6.8.0-64.67","6.8.0-71.71","6.8.0-78.78","6.8.0-79.79","6.8.0-83.83","6.8.0-84.84","6.8.0-85.85","6.8.0-86.87","6.8.0-87.88","6.8.0-88.89","6.8.0-90.91","6.8.0-94.96","6.8.0-100.100","6.8.0-101.101","6.8.0-106.106","6.8.0-107.107","6.8.0-110.110","6.8.0-111.111"],"bundled":196},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-aws","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1055.58"}]}],"versions":["6.5.0-1008.8","6.6.0-1001.1","6.8.0-1001.1","6.8.0-1006.6","6.8.0-1008.8","6.8.0-1009.9","6.8.0-1010.10","6.8.0-1011.12","6.8.0-1012.13","6.8.0-1013.14","6.8.0-1014.15","6.8.0-1015.16","6.8.0-1016.17","6.8.0-1017.18","6.8.0-1018.20","6.8.0-1019.21","6.8.0-1020.22","6.8.0-1021.23","6.8.0-1023.25","6.8.0-1024.26","6.8.0-1025.27","6.8.0-1026.28","6.8.0-1027.29","6.8.0-1028.30","6.8.0-1029.31","6.8.0-1030.32","6.8.0-1031.33","6.8.0-1032.34","6.8.0-1033.35","6.8.0-1035.37","6.8.0-1036.38","6.8.0-1038.40","6.8.0-1039.41","6.8.0-1040.42","6.8.0-1041.43","6.8.0-1042.44","6.8.0-1043.45","6.8.0-1044.46","6.8.0-1045.47","6.8.0-1046.49","6.8.0-1047.50","6.8.0-1050.53","6.8.0-1051.54","6.8.0-1052.55","6.8.0-1053.56"],"bundled":196},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-gcp","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1058.61"}]}],"versions":["6.5.0-1007.7","6.6.0-1001.1","6.8.0-1002.2","6.8.0-1005.5","6.8.0-1006.6","6.8.0-1007.7","6.8.0-1008.9","6.8.0-1009.10","6.8.0-1010.11","6.8.0-1011.12","6.8.0-1012.13","6.8.0-1013.14","6.8.0-1014.16","6.8.0-1015.17","6.8.0-1016.18","6.8.0-1017.19","6.8.0-1018.20","6.8.0-1019.21","6.8.0-1020.22","6.8.0-1021.23","6.8.0-1024.26","6.8.0-1025.27","6.8.0-1026.28","6.8.0-1027.29","6.8.0-1028.30","6.8.0-1029.31","6.8.0-1030.32","6.8.0-1031.33","6.8.0-1032.34","6.8.0-1033.35","6.8.0-1034.36","6.8.0-1036.38","6.8.0-1037.39","6.8.0-1039.41","6.8.0-1040.42","6.8.0-1041.43","6.8.0-1042.45","6.8.0-1043.46","6.8.0-1044.47","6.8.0-1045.48","6.8.0-1046.49","6.8.0-1047.50","6.8.0-1048.51","6.8.0-1052.55","6.8.0-1053.56","6.8.0-1054.57","6.8.0-1055.58"],"bundled":196},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-gke","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1054.60"}]}],"versions":["6.8.0-1003.5","6.8.0-1004.7","6.8.0-1005.8","6.8.0-1006.9","6.8.0-1007.10","6.8.0-1008.11","6.8.0-1009.12","6.8.0-1010.13","6.8.0-1011.14","6.8.0-1012.15","6.8.0-1013.17","6.8.0-1014.18","6.8.0-1015.19","6.8.0-1016.20","6.8.0-1017.21","6.8.0-1019.23","6.8.0-1020.24","6.8.0-1021.25","6.8.0-1022.26","6.8.0-1023.27","6.8.0-1024.28","6.8.0-1025.29","6.8.0-1026.30","6.8.0-1027.31","6.8.0-1028.32","6.8.0-1029.33","6.8.0-1032.36","6.8.0-1033.37","6.8.0-1035.39","6.8.0-1036.40","6.8.0-1037.41","6.8.0-1038.43","6.8.0-1039.44","6.8.0-1040.45","6.8.0-1041.46","6.8.0-1042.47","6.8.0-1043.48","6.8.0-1044.49","6.8.0-1048.53","6.8.0-1049.54","6.8.0-1050.56","6.8.0-1051.57"],"bundled":196},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-gkeop","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1041.44"}]}],"versions":["6.8.0-1001.3","6.8.0-1002.4","6.8.0-1003.5","6.8.0-1004.6","6.8.0-1006.8","6.8.0-1007.9","6.8.0-1008.10","6.8.0-1009.11","6.8.0-1010.12","6.8.0-1011.13","6.8.0-1012.14","6.8.0-1013.15","6.8.0-1014.16","6.8.0-1015.17","6.8.0-1016.18","6.8.0-1019.21","6.8.0-1020.22","6.8.0-1022.24","6.8.0-1023.25","6.8.0-1024.26","6.8.0-1025.28","6.8.0-1026.29","6.8.0-1027.30","6.8.0-1028.31","6.8.0-1029.32","6.8.0-1030.33","6.8.0-1031.34","6.8.0-1035.38","6.8.0-1036.39","6.8.0-1037.40","6.8.0-1038.41"],"bundled":196},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-ibm","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1055.56"}]}],"versions":["6.5.0-1009.9","6.8.0-1001.1","6.8.0-1003.3","6.8.0-1004.4","6.8.0-1005.5","6.8.0-1006.6","6.8.0-1007.7","6.8.0-1008.8","6.8.0-1009.9","6.8.0-1010.10","6.8.0-1011.11","6.8.0-1012.12","6.8.0-1013.13","6.8.0-1014.14","6.8.0-1015.15","6.8.0-1016.16","6.8.0-1017.17","6.8.0-1018.18","6.8.0-1019.19","6.8.0-1022.22","6.8.0-1023.23","6.8.0-1024.24","6.8.0-1025.25","6.8.0-1026.26","6.8.0-1027.27","6.8.0-1028.28","6.8.0-1029.29","6.8.0-1030.30","6.8.0-1033.33","6.8.0-1036.36","6.8.0-1037.37","6.8.0-1038.38","6.8.0-1039.39","6.8.0-1040.40","6.8.0-1041.41","6.8.0-1042.42","6.8.0-1043.43","6.8.0-1044.44","6.8.0-1045.45","6.8.0-1049.49","6.8.0-1050.50","6.8.0-1051.51","6.8.0-1052.52"],"bundled":196},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-lowlatency","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-117.117.1"}]}],"versions":["6.5.0-9.9.1","6.6.0-14.14.1","6.8.0-7.7.1","6.8.0-25.25.3","6.8.0-28.28.1","6.8.0-31.31.1","6.8.0-35.35.1","6.8.0-36.36.1","6.8.0-38.38.1","6.8.0-39.39.1","6.8.0-40.40.1","6.8.0-41.41.1","6.8.0-44.44.1","6.8.0-45.45.1","6.8.0-47.47.1","6.8.0-48.48.3","6.8.0-49.49.1","6.8.0-50.51.1","6.8.0-51.52.1","6.8.0-52.53.1","6.8.0-53.55.2","6.8.0-54.56.1","6.8.0-55.57.1","6.8.0-56.58.1","6.8.0-57.59.1","6.8.0-58.60.1","6.8.0-59.61.1","6.8.0-60.63.1","6.8.0-62.65.1","6.8.0-63.66.1","6.8.0-64.67.1","6.8.0-65.68.1","6.8.0-78.78.1","6.8.0-79.79.1","6.8.0-83.83.1","6.8.0-84.84.1","6.8.0-85.85.1","6.8.0-86.87.1","6.8.0-87.88.1","6.8.0-88.89.1","6.8.0-90.91.1","6.8.0-94.96.1","6.8.0-100.100.1","6.8.0-101.101.1","6.8.0-106.106.1","6.8.0-107.107.1","6.8.0-110.110.1","6.8.0-111.111.1"],"bundled":196},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-raspi","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1056.60"}]}],"versions":["6.5.0-1005.7","6.7.0-1001.1","6.8.0-1001.1","6.8.0-1002.2","6.8.0-1003.3","6.8.0-1004.4","6.8.0-1005.5","6.8.0-1006.6","6.8.0-1007.7","6.8.0-1008.8","6.8.0-1009.10","6.8.0-1010.11","6.8.0-1011.12","6.8.0-1012.13","6.8.0-1013.14","6.8.0-1014.16","6.8.0-1015.17","6.8.0-1016.18","6.8.0-1017.19","6.8.0-1018.20","6.8.0-1019.23","6.8.0-1020.24","6.8.0-1024.28","6.8.0-1028.32","6.8.0-1029.33","6.8.0-1030.34","6.8.0-1031.35","6.8.0-1032.36","6.8.0-1035.39","6.8.0-1036.40","6.8.0-1038.42","6.8.0-1039.43","6.8.0-1040.44","6.8.0-1041.45","6.8.0-1042.46","6.8.0-1043.47","6.8.0-1044.48","6.8.0-1045.49","6.8.0-1047.51","6.8.0-1048.52","6.8.0-1050.54","6.8.0-1051.55","6.8.0-1052.56","6.8.0-1053.57"],"bundled":196},{"source":"osv","ecosystem":"Ubuntu:Pro:Realtime:24.04:LTS","package":"linux-raspi-realtime","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-2045.46"}]}],"versions":["6.7.0-2001.1","6.8.0-2001.1","6.8.0-2002.2","6.8.0-2004.4","6.8.0-2005.5","6.8.0-2006.6","6.8.0-2007.7","6.8.0-2008.8","6.8.0-2009.9","6.8.0-2010.10","6.8.0-2011.11","6.8.0-2012.12","6.8.0-2013.14","6.8.0-2014.15","6.8.0-2015.16","6.8.0-2016.17","6.8.0-2017.18","6.8.0-2018.19","6.8.0-2019.20","6.8.0-2022.23","6.8.0-2023.24","6.8.0-2024.25","6.8.0-2025.26","6.8.0-2026.27","6.8.0-2028.29","6.8.0-2029.30","6.8.0-2030.31","6.8.0-2031.32","6.8.0-2032.33","6.8.0-2033.34","6.8.0-2034.35","6.8.0-2035.36","6.8.0-2036.37","6.8.0-2037.38","6.8.0-2038.39","6.8.0-2040.41","6.8.0-2041.42","6.8.0-2042.43","6.8.0-2043.44"],"bundled":196},{"source":"osv","ecosystem":"Ubuntu:Pro:Realtime:24.04:LTS","package":"linux-realtime","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.1-1051.52"}]}],"versions":["6.8.0-1008.19","6.8.1-1001.1","6.8.1-1002.2","6.8.1-1003.3","6.8.1-1004.4","6.8.1-1005.5","6.8.1-1006.6","6.8.1-1007.7","6.8.1-1008.8","6.8.1-1009.9","6.8.1-1010.10","6.8.1-1011.11","6.8.1-1012.12","6.8.1-1013.14","6.8.1-1014.15","6.8.1-1015.16","6.8.1-1016.17","6.8.1-1017.18","6.8.1-1018.19","6.8.1-1019.20","6.8.1-1020.21","6.8.1-1021.22","6.8.1-1022.23","6.8.1-1023.24","6.8.1-1024.25","6.8.1-1025.26","6.8.1-1026.27","6.8.1-1030.31","6.8.1-1031.32","6.8.1-1033.34","6.8.1-1034.35","6.8.1-1035.36","6.8.1-1036.37","6.8.1-1037.38","6.8.1-1038.39","6.8.1-1039.40","6.8.1-1040.41","6.8.1-1041.42","6.8.1-1042.43","6.8.1-1045.46","6.8.1-1046.47","6.8.1-1047.48","6.8.1-1048.49"],"bundled":196},{"source":"osv","ecosystem":"Ubuntu:Pro:FIPS-updates:24.04:LTS","package":"linux-aws-fips","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1055.58+fips1"}]}],"versions":["6.8.0-1035.37+fips1","6.8.0-1036.38+fips1","6.8.0-1038.40+fips1","6.8.0-1039.41+fips1","6.8.0-1040.42+fips1","6.8.0-1041.43+fips1","6.8.0-1042.44+fips1","6.8.0-1043.45+fips1","6.8.0-1044.46+fips1","6.8.0-1045.47+fips1","6.8.0-1046.49+fips1","6.8.0-1047.50+fips1","6.8.0-1050.53+fips1","6.8.0-1051.54+fips1","6.8.0-1052.55+fips1","6.8.0-1053.56+fips1"],"bundled":196},{"source":"osv","ecosystem":"Ubuntu:Pro:FIPS-updates:24.04:LTS","package":"linux-gcp-fips","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1058.61+fips1"}]}],"versions":["6.8.0-1036.38+fips1","6.8.0-1037.39+fips1","6.8.0-1039.41+fips1","6.8.0-1040.42+fips1","6.8.0-1041.43+fips1","6.8.0-1042.45+fips1","6.8.0-1043.46+fips1","6.8.0-1044.47+fips1","6.8.0-1045.48+fips1","6.8.0-1046.49+fips1","6.8.0-1047.50+fips1","6.8.0-1048.51+fips1","6.8.0-1052.55+fips1","6.8.0-1053.56+fips1","6.8.0-1054.57+fips1","6.8.0-1055.58+fips1"],"bundled":196},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-azure","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1056.62"}]}],"versions":["6.5.0-1007.7","6.6.0-1001.1","6.8.0-1001.1","6.8.0-1005.5","6.8.0-1006.6","6.8.0-1007.7","6.8.0-1008.8","6.8.0-1009.9","6.8.0-1010.10","6.8.0-1012.14","6.8.0-1013.15","6.8.0-1014.16","6.8.0-1015.17","6.8.0-1016.18","6.8.0-1017.20","6.8.0-1018.21","6.8.0-1020.23","6.8.0-1021.25","6.8.0-1025.30","6.8.0-1026.31","6.8.0-1027.32","6.8.0-1028.33","6.8.0-1029.34","6.8.0-1030.35","6.8.0-1031.36","6.8.0-1034.39","6.8.0-1038.44","6.8.0-1040.46","6.8.0-1041.47","6.8.0-1042.48","6.8.0-1044.50","6.8.0-1046.52","6.8.0-1051.57","6.8.0-1052.58","6.8.0-1054.60"],"bundled":196},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-nvidia","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1054.57"}]}],"versions":["6.8.0-1007.7","6.8.0-1008.8","6.8.0-1009.9","6.8.0-1010.10","6.8.0-1011.11","6.8.0-1012.12","6.8.0-1013.14","6.8.0-1014.15","6.8.0-1015.16","6.8.0-1017.19","6.8.0-1018.20","6.8.0-1019.21","6.8.0-1020.22","6.8.0-1021.23","6.8.0-1022.25","6.8.0-1023.26","6.8.0-1024.27","6.8.0-1025.28","6.8.0-1026.29","6.8.0-1027.30","6.8.0-1028.31","6.8.0-1029.32","6.8.0-1030.33","6.8.0-1031.34","6.8.0-1032.35","6.8.0-1035.38","6.8.0-1036.39","6.8.0-1038.41","6.8.0-1039.42","6.8.0-1040.43","6.8.0-1041.44","6.8.0-1042.45","6.8.0-1043.46","6.8.0-1044.47","6.8.0-1045.48","6.8.0-1046.49","6.8.0-1047.50","6.8.0-1049.52","6.8.0-1050.53","6.8.0-1051.54","6.8.0-1052.55"],"bundled":195},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-nvidia-lowlatency","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1054.57.1"}]}],"versions":["6.8.0-1009.9.1","6.8.0-1011.11.1","6.8.0-1012.12.1","6.8.0-1013.14.1","6.8.0-1014.15.1","6.8.0-1015.16.1","6.8.0-1017.19.1","6.8.0-1018.20.1","6.8.0-1019.21.1","6.8.0-1020.22.1","6.8.0-1021.23.1","6.8.0-1022.25.2","6.8.0-1023.26.1","6.8.0-1024.27.1","6.8.0-1025.28.1","6.8.0-1026.29.1","6.8.0-1027.30.1","6.8.0-1028.31.1","6.8.0-1029.32.1","6.8.0-1030.33.1","6.8.0-1031.34.1","6.8.0-1032.35.1","6.8.0-1035.38.1","6.8.0-1036.39.1","6.8.0-1038.41.1","6.8.0-1039.42.1","6.8.0-1040.43.1","6.8.0-1041.44.1","6.8.0-1042.45.1","6.8.0-1043.46.1","6.8.0-1044.47.1","6.8.0-1045.48.1","6.8.0-1046.49.1","6.8.0-1047.50.1","6.8.0-1049.52.1","6.8.0-1050.53.1","6.8.0-1051.54.1","6.8.0-1052.55.1"],"bundled":195},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-nvidia-6.8","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1054.57~22.04.1"}]}],"versions":["6.8.0-1008.8~22.04.1","6.8.0-1009.9~22.04.1","6.8.0-1010.10~22.04.1","6.8.0-1011.11~22.04.1","6.8.0-1012.12~22.04.1","6.8.0-1013.14~22.04.1","6.8.0-1014.15~22.04.1","6.8.0-1015.16~22.04.1","6.8.0-1017.19~22.04.1","6.8.0-1018.20~22.04.1","6.8.0-1019.21~22.04.1","6.8.0-1020.22~22.04.1","6.8.0-1021.23~22.04.1","6.8.0-1022.25~22.04.2","6.8.0-1023.26~22.04.1","6.8.0-1024.27~22.04.1","6.8.0-1025.28~22.04.1","6.8.0-1026.29~22.04.1","6.8.0-1027.30~22.04.1","6.8.0-1028.31~22.04.1","6.8.0-1029.32~22.04.1","6.8.0-1030.33~22.04.1","6.8.0-1031.34~22.04.1","6.8.0-1032.35~22.04.1","6.8.0-1035.38~22.04.1","6.8.0-1036.39~22.04.1","6.8.0-1038.41~22.04.1","6.8.0-1039.42~22.04.1","6.8.0-1040.43~22.04.1","6.8.0-1041.44~22.04.2","6.8.0-1042.45~22.04.1","6.8.0-1043.46~22.04.1","6.8.0-1044.47~22.04.1","6.8.0-1045.48~22.04.1","6.8.0-1046.49~22.04.1","6.8.0-1047.50~22.04.1","6.8.0-1049.52~22.04.1","6.8.0-1050.53~22.04.1","6.8.0-1051.54~22.04.1","6.8.0-1052.55~22.04.1"],"bundled":195},{"source":"osv","ecosystem":"Ubuntu:Pro:FIPS-updates:24.04:LTS","package":"linux-fips","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-116.116+fips1"}]}],"versions":["6.8.0-38.38+fips4","6.8.0-78.78+fips1","6.8.0-79.79+fips1","6.8.0-83.83+fips1","6.8.0-84.84+fips1","6.8.0-85.85+fips1","6.8.0-86.87+fips1","6.8.0-87.88+fips1","6.8.0-88.89+fips1","6.8.0-90.91+fips1","6.8.0-94.96+fips1","6.8.0-100.100+fips1","6.8.0-101.101+fips1","6.8.0-106.106+fips1","6.8.0-107.107+fips1","6.8.0-110.110+fips2","6.8.0-111.111+fips1"],"bundled":189},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-nvidia-tegra","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1024.24"}]}],"versions":["6.8.0-1003.3","6.8.0-1004.4","6.8.0-1008.8","6.8.0-1009.9","6.8.0-1010.10","6.8.0-1012.12","6.8.0-1013.13","6.8.0-1016.16","6.8.0-1019.19","6.8.0-1020.20","6.8.0-1021.21","6.8.0-1022.22","6.8.0-1023.23"],"bundled":189},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-azure-6.17","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.17.0-1015.15~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"],"bundled":22},{"source":"osv","ecosystem":"Ubuntu:25.10","package":"linux-azure","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.17.0-1015.15"}]}],"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"],"bundled":22},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-aws-6.17","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.17.0-1017.17~24.04.1"}]}],"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"],"bundled":40},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-gcp-6.17","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.17.0-1018.19~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"],"bundled":40},{"source":"osv","ecosystem":"Ubuntu:25.10","package":"linux-gcp","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.17.0-1018.19"}]}],"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"],"bundled":40},{"source":"osv","ecosystem":"Ubuntu:Pro:FIPS-updates:24.04:LTS","package":"linux-azure-fips","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1059.65+fips1"}]}],"versions":["6.8.0-1034.39+fips1","6.8.0-1040.46+fips1","6.8.0-1044.50+fips1","6.8.0-1046.52+fips1","6.8.0-1047.53+fips1","6.8.0-1052.58+fips1","6.8.0-1053.59+fips1","6.8.0-1054.60+fips1"],"bundled":218},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-azure-6.8","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1059.65~22.04.1"}]}],"versions":["6.8.0-1008.8~22.04.1","6.8.0-1009.9~22.04.1","6.8.0-1010.10~22.04.1","6.8.0-1012.14~22.04.1","6.8.0-1013.15~22.04.1","6.8.0-1014.16~22.04.1","6.8.0-1015.17~22.04.2","6.8.0-1017.20~22.04.1","6.8.0-1018.21~22.04.1","6.8.0-1020.23~22.04.1","6.8.0-1021.25~22.04.1","6.8.0-1025.30~22.04.1","6.8.0-1026.31~22.04.1","6.8.0-1027.32~22.04.1","6.8.0-1028.33~22.04.1","6.8.0-1029.34~22.04.1","6.8.0-1030.35~22.04.1","6.8.0-1031.36~22.04.1","6.8.0-1034.39~22.04.1","6.8.0-1036.42~22.04.1","6.8.0-1040.46~22.04.1","6.8.0-1041.47~22.04.1","6.8.0-1044.50~22.04.1","6.8.0-1051.57~22.04.1","6.8.0-1052.58~22.04.1"],"bundled":393},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-xilinx","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1032.33"}]}],"versions":["6.8.0-1008.9","6.8.0-1009.10","6.8.0-1011.12","6.8.0-1012.13","6.8.0-1013.14","6.8.0-1014.15","6.8.0-1015.16","6.8.0-1017.18","6.8.0-1018.19","6.8.0-1019.20","6.8.0-1020.21","6.8.0-1021.22","6.8.0-1022.23","6.8.0-1023.24","6.8.0-1024.25","6.8.0-1028.29","6.8.0-1029.30"],"bundled":516},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-nvidia-6.17","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.17.0-1026.26"}]}],"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"],"bundled":84},{"source":"osv","ecosystem":"openSUSE:Leap 16.0","package":"dtb-aarch64","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.12.0-160000.36.1"}]}],"bundled":255},{"source":"osv","ecosystem":"openSUSE:Leap 16.0","package":"kernel-64kb","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.12.0-160000.36.1"}]}],"bundled":255},{"source":"osv","ecosystem":"openSUSE:Leap 16.0","package":"kernel-azure","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.12.0-160000.36.1"}]}],"bundled":255},{"source":"osv","ecosystem":"openSUSE:Leap 16.0","package":"kernel-default","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.12.0-160000.36.1"}]}],"bundled":255},{"source":"osv","ecosystem":"openSUSE:Leap 16.0","package":"kernel-default-base","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.12.0-160000.36.1.160000.2.17"}]}],"bundled":255},{"source":"osv","ecosystem":"openSUSE:Leap 16.0","package":"kernel-docs","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.12.0-160000.36.1"}]}],"bundled":255},{"source":"osv","ecosystem":"openSUSE:Leap 16.0","package":"kernel-kvmsmall","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.12.0-160000.36.1"}]}],"bundled":255},{"source":"osv","ecosystem":"openSUSE:Leap 16.0","package":"kernel-obs-build","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.12.0-160000.36.1"}]}],"bundled":255},{"source":"osv","ecosystem":"openSUSE:Leap 16.0","package":"kernel-obs-qa","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.12.0-160000.36.1"}]}],"bundled":255},{"source":"osv","ecosystem":"openSUSE:Leap 16.0","package":"kernel-rt","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.12.0-160000.36.1"}]}],"bundled":255},{"source":"osv","ecosystem":"openSUSE:Leap 16.0","package":"kernel-source","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.12.0-160000.36.1"}]}],"bundled":255},{"source":"osv","ecosystem":"openSUSE:Leap 16.0","package":"kernel-syms","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.12.0-160000.36.1"}]}],"bundled":255},{"source":"osv","ecosystem":"openSUSE:Leap 16.0","package":"kernel-zfcpdump","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.12.0-160000.36.1"}]}],"bundled":255}],"products":[{"vendor":"linux","product":"linux"},{"vendor":"linux","product":"linux_kernel"}],"references":[{"url":"https://git.kernel.org/stable/c/980999a96e1ad043f1197606e5d637219cb102b9","tags":["web"]},{"url":"https://git.kernel.org/stable/c/3106f326f67c03dd9da4ca64663d11e40138cf40","tags":["web"]},{"url":"https://git.kernel.org/stable/c/e3dd56fb5683ba80bf8d7a2f9aa21cfa53f05202","tags":["web"]},{"url":"https://git.kernel.org/stable/c/72cf49ad50c16270b52bc512d9c2df5743922968","tags":["Patch","web"]},{"url":"https://git.kernel.org/stable/c/37dd7ab332396eb8dd80b2dc7ea4b61abf767436","tags":["Patch","web","report"]},{"url":"https://git.kernel.org/stable/c/e5b31d988a41549037b8d8721a3c3cae893d8670","tags":["Patch","web","report"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-23394","tags":["web","advisory"]},{"url":"https://github.com/advisories/GHSA-p5pc-67g7-qcv2"},{"url":"https://docs.bell-sw.com/security/cves/CVE-2026-23394","tags":["advisory"]},{"url":"https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/23xxx/CVE-2026-23394.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-23394","tags":["advisory"]},{"url":"https://www.openeuler.org/zh/security/security-bulletins/detail/?id=openEuler-SA-2026-1862","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-68315","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-68727","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-23231","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-23240","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-23245","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-23254","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-23255","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-23270","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-23274","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-23276","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-23277","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-23278","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-23293","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-23300","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-23302","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-23303","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-23304","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-23310","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-23321","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-23343","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-23351","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-23362","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-23365","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-23368","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-23371","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-23375","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-23381","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-23391","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-23392","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-23393","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-23395","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-23397","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-23399","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-23401","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-23403","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-23404","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-23405","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-23408","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-23409","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-23410","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-23411","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-23413","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-23414","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-31788","tags":["advisory"]},{"url":"https://www.openeuler.org/zh/security/security-bulletins/detail/?id=openEuler-SA-2026-1863","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-71089","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-23096","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-23171","tags":["advisory"]},{"url":"https://www.openeuler.org/zh/security/security-bulletins/detail/?id=openEuler-SA-2026-1864","tags":["advisory"]},{"url":"https://www.suse.com/support/update/announcement/2026/suse-su-202622742-1/","tags":["advisory"]},{"url":"https://bugzilla.suse.com/1149651","tags":["report"]},{"url":"https://bugzilla.suse.com/1204315","tags":["report"]},{"url":"https://bugzilla.suse.com/1236743","tags":["report"]},{"url":"https://bugzilla.suse.com/1255029","tags":["report"]},{"url":"https://bugzilla.suse.com/1257506","tags":["report"]},{"url":"https://bugzilla.suse.com/1258538","tags":["report"]},{"url":"https://bugzilla.suse.com/1259800","tags":["report"]},{"url":"https://bugzilla.suse.com/1260565","tags":["report"]},{"url":"https://bugzilla.suse.com/1261250","tags":["report"]},{"url":"https://bugzilla.suse.com/1261256","tags":["report"]},{"url":"https://bugzilla.suse.com/1261562","tags":["report"]},{"url":"https://bugzilla.suse.com/1261604","tags":["report"]},{"url":"https://bugzilla.suse.com/1262085","tags":["report"]},{"url":"https://bugzilla.suse.com/1262392","tags":["report"]},{"url":"https://bugzilla.suse.com/1262430","tags":["report"]},{"url":"https://bugzilla.suse.com/1262618","tags":["report"]},{"url":"https://bugzilla.suse.com/1262620","tags":["report"]},{"url":"https://bugzilla.suse.com/1262674","tags":["report"]},{"url":"https://bugzilla.suse.com/1262748","tags":["report"]},{"url":"https://bugzilla.suse.com/1262765","tags":["report"]},{"url":"https://bugzilla.suse.com/1262798","tags":["report"]},{"url":"https://bugzilla.suse.com/1263057","tags":["report"]},{"url":"https://bugzilla.suse.com/1263072","tags":["report"]},{"url":"https://bugzilla.suse.com/1263133","tags":["report"]},{"url":"https://bugzilla.suse.com/1263137","tags":["report"]},{"url":"https://bugzilla.suse.com/1263143","tags":["report"]},{"url":"https://bugzilla.suse.com/1263169","tags":["report"]},{"url":"https://bugzilla.suse.com/1263178","tags":["report"]},{"url":"https://bugzilla.suse.com/1263319","tags":["report"]},{"url":"https://bugzilla.suse.com/1263563","tags":["report"]},{"url":"https://bugzilla.suse.com/1263568","tags":["report"]},{"url":"https://bugzilla.suse.com/1263573","tags":["report"]},{"url":"https://bugzilla.suse.com/1263578","tags":["report"]},{"url":"https://bugzilla.suse.com/1263581","tags":["report"]},{"url":"https://bugzilla.suse.com/1263796","tags":["report"]},{"url":"https://bugzilla.suse.com/1263930","tags":["report"]},{"url":"https://bugzilla.suse.com/1263934","tags":["report"]},{"url":"https://bugzilla.suse.com/1263993","tags":["report"]},{"url":"https://bugzilla.suse.com/1263996","tags":["report"]},{"url":"https://bugzilla.suse.com/1263998","tags":["report"]},{"url":"https://bugzilla.suse.com/1264001","tags":["report"]},{"url":"https://bugzilla.suse.com/1264007","tags":["report"]},{"url":"https://bugzilla.suse.com/1264010","tags":["report"]},{"url":"https://bugzilla.suse.com/1264012","tags":["report"]},{"url":"https://bugzilla.suse.com/1264015","tags":["report"]},{"url":"https://bugzilla.suse.com/1264045","tags":["report"]},{"url":"https://bugzilla.suse.com/1264056","tags":["report"]},{"url":"https://bugzilla.suse.com/1264067","tags":["report"]},{"url":"https://bugzilla.suse.com/1264084","tags":["report"]},{"url":"https://bugzilla.suse.com/1264145","tags":["report"]},{"url":"https://bugzilla.suse.com/1264230","tags":["report"]},{"url":"https://bugzilla.suse.com/1264231","tags":["report"]},{"url":"https://bugzilla.suse.com/1264236","tags":["report"]},{"url":"https://bugzilla.suse.com/1264239","tags":["report"]},{"url":"https://bugzilla.suse.com/1264241","tags":["report"]},{"url":"https://bugzilla.suse.com/1264250","tags":["report"]},{"url":"https://bugzilla.suse.com/1264254","tags":["report"]},{"url":"https://bugzilla.suse.com/1264258","tags":["report"]},{"url":"https://bugzilla.suse.com/1264261","tags":["report"]},{"url":"https://bugzilla.suse.com/1264263","tags":["report"]},{"url":"https://bugzilla.suse.com/1264266","tags":["report"]},{"url":"https://bugzilla.suse.com/1264270","tags":["report"]},{"url":"https://bugzilla.suse.com/1264286","tags":["report"]},{"url":"https://bugzilla.suse.com/1264294","tags":["report"]},{"url":"https://bugzilla.suse.com/1264295","tags":["report"]},{"url":"https://bugzilla.suse.com/1264302","tags":["report"]},{"url":"https://bugzilla.suse.com/1264304","tags":["report"]},{"url":"https://bugzilla.suse.com/1264320","tags":["report"]},{"url":"https://bugzilla.suse.com/1264328","tags":["report"]},{"url":"https://bugzilla.suse.com/1264333","tags":["report"]},{"url":"https://bugzilla.suse.com/1264337","tags":["report"]},{"url":"https://bugzilla.suse.com/1264372","tags":["report"]},{"url":"https://bugzilla.suse.com/1264386","tags":["report"]},{"url":"https://bugzilla.suse.com/1264429","tags":["report"]},{"url":"https://bugzilla.suse.com/1264449","tags":["report"]},{"url":"https://bugzilla.suse.com/1264532","tags":["report"]},{"url":"https://bugzilla.suse.com/1264544","tags":["report"]},{"url":"https://bugzilla.suse.com/1264545","tags":["report"]},{"url":"https://bugzilla.suse.com/1264548","tags":["report"]},{"url":"https://bugzilla.suse.com/1264549","tags":["report"]},{"url":"https://bugzilla.suse.com/1264556","tags":["report"]},{"url":"https://bugzilla.suse.com/1264561","tags":["report"]},{"url":"https://bugzilla.suse.com/1264580","tags":["report"]},{"url":"https://bugzilla.suse.com/1264595","tags":["report"]},{"url":"https://bugzilla.suse.com/1264603","tags":["report"]},{"url":"https://bugzilla.suse.com/1264610","tags":["report"]},{"url":"https://bugzilla.suse.com/1264612","tags":["report"]},{"url":"https://bugzilla.suse.com/1264614","tags":["report"]},{"url":"https://bugzilla.suse.com/1264624","tags":["report"]},{"url":"https://bugzilla.suse.com/1264643","tags":["report"]},{"url":"https://bugzilla.suse.com/1264734","tags":["report"]},{"url":"https://bugzilla.suse.com/1264740","tags":["report"]},{"url":"https://bugzilla.suse.com/1264741","tags":["report"]},{"url":"https://bugzilla.suse.com/1264744","tags":["report"]},{"url":"https://bugzilla.suse.com/1264763","tags":["report"]},{"url":"https://bugzilla.suse.com/1264789","tags":["report"]},{"url":"https://bugzilla.suse.com/1264790","tags":["report"]},{"url":"https://bugzilla.suse.com/1264794","tags":["report"]},{"url":"https://bugzilla.suse.com/1264852","tags":["report"]},{"url":"https://bugzilla.suse.com/1264974","tags":["report"]},{"url":"https://bugzilla.suse.com/1264978","tags":["report"]},{"url":"https://bugzilla.suse.com/1264997","tags":["report"]},{"url":"https://bugzilla.suse.com/1265000","tags":["report"]},{"url":"https://bugzilla.suse.com/1265005","tags":["report"]},{"url":"https://bugzilla.suse.com/1265020","tags":["report"]},{"url":"https://bugzilla.suse.com/1265023","tags":["report"]},{"url":"https://bugzilla.suse.com/1265073","tags":["report"]},{"url":"https://bugzilla.suse.com/1265079","tags":["report"]},{"url":"https://bugzilla.suse.com/1265082","tags":["report"]},{"url":"https://bugzilla.suse.com/1265084","tags":["report"]},{"url":"https://bugzilla.suse.com/1265091","tags":["report"]},{"url":"https://bugzilla.suse.com/1265097","tags":["report"]},{"url":"https://bugzilla.suse.com/1265103","tags":["report"]},{"url":"https://bugzilla.suse.com/1265112","tags":["report"]},{"url":"https://bugzilla.suse.com/1265113","tags":["report"]},{"url":"https://bugzilla.suse.com/1265123","tags":["report"]},{"url":"https://bugzilla.suse.com/1265128","tags":["report"]},{"url":"https://bugzilla.suse.com/1265129","tags":["report"]},{"url":"https://bugzilla.suse.com/1265142","tags":["report"]},{"url":"https://bugzilla.suse.com/1265143","tags":["report"]},{"url":"https://bugzilla.suse.com/1265628","tags":["report"]},{"url":"https://bugzilla.suse.com/1265629","tags":["report"]},{"url":"https://bugzilla.suse.com/1266008","tags":["report"]},{"url":"https://bugzilla.suse.com/1266214","tags":["report"]},{"url":"https://bugzilla.suse.com/1266283","tags":["report"]},{"url":"https://bugzilla.suse.com/1266284","tags":["report"]},{"url":"https://bugzilla.suse.com/1266290","tags":["report"]},{"url":"https://bugzilla.suse.com/1266390","tags":["report"]},{"url":"https://bugzilla.suse.com/1266396","tags":["report"]},{"url":"https://bugzilla.suse.com/1266397","tags":["report"]},{"url":"https://bugzilla.suse.com/1266398","tags":["report"]},{"url":"https://bugzilla.suse.com/1266452","tags":["report"]},{"url":"https://bugzilla.suse.com/1266458","tags":["report"]},{"url":"https://bugzilla.suse.com/1266686","tags":["report"]},{"url":"https://bugzilla.suse.com/1266693","tags":["report"]},{"url":"https://bugzilla.suse.com/1266697","tags":["report"]},{"url":"https://bugzilla.suse.com/1266698","tags":["report"]},{"url":"https://bugzilla.suse.com/1266700","tags":["report"]},{"url":"https://bugzilla.suse.com/1266704","tags":["report"]},{"url":"https://bugzilla.suse.com/1266705","tags":["report"]},{"url":"https://bugzilla.suse.com/1266717","tags":["report"]},{"url":"https://bugzilla.suse.com/1266718","tags":["report"]},{"url":"https://bugzilla.suse.com/1266722","tags":["report"]},{"url":"https://bugzilla.suse.com/1266726","tags":["report"]},{"url":"https://bugzilla.suse.com/1266734","tags":["report"]},{"url":"https://bugzilla.suse.com/1266740","tags":["report"]},{"url":"https://bugzilla.suse.com/1266750","tags":["report"]},{"url":"https://bugzilla.suse.com/1266754","tags":["report"]},{"url":"https://bugzilla.suse.com/1266761","tags":["report"]},{"url":"https://bugzilla.suse.com/1266773","tags":["report"]},{"url":"https://bugzilla.suse.com/1266805","tags":["report"]},{"url":"https://bugzilla.suse.com/1266830","tags":["report"]},{"url":"https://bugzilla.suse.com/1266838","tags":["report"]},{"url":"https://bugzilla.suse.com/1266840","tags":["report"]},{"url":"https://bugzilla.suse.com/1266847","tags":["report"]},{"url":"https://bugzilla.suse.com/1266878","tags":["report"]},{"url":"https://bugzilla.suse.com/1266883","tags":["report"]},{"url":"https://bugzilla.suse.com/1266892","tags":["report"]},{"url":"https://bugzilla.suse.com/1266893","tags":["report"]},{"url":"https://bugzilla.suse.com/1266895","tags":["report"]},{"url":"https://bugzilla.suse.com/1266899","tags":["report"]},{"url":"https://bugzilla.suse.com/1266903","tags":["report"]},{"url":"https://bugzilla.suse.com/1266916","tags":["report"]},{"url":"https://bugzilla.suse.com/1266922","tags":["report"]},{"url":"https://bugzilla.suse.com/1266925","tags":["report"]},{"url":"https://bugzilla.suse.com/1266929","tags":["report"]},{"url":"https://bugzilla.suse.com/1266933","tags":["report"]},{"url":"https://bugzilla.suse.com/1267208","tags":["report"]},{"url":"https://bugzilla.suse.com/1267218","tags":["report"]},{"url":"https://bugzilla.suse.com/1267228","tags":["report"]},{"url":"https://bugzilla.suse.com/1267238","tags":["report"]},{"url":"https://bugzilla.suse.com/1267251","tags":["report"]},{"url":"https://bugzilla.suse.com/1267360","tags":["report"]},{"url":"https://bugzilla.suse.com/1267361","tags":["report"]},{"url":"https://bugzilla.suse.com/1267365","tags":["report"]},{"url":"https://bugzilla.suse.com/1267369","tags":["report"]},{"url":"https://bugzilla.suse.com/1267387","tags":["report"]},{"url":"https://bugzilla.suse.com/1267419","tags":["report"]},{"url":"https://bugzilla.suse.com/1267427","tags":["report"]},{"url":"https://bugzilla.suse.com/1267431","tags":["report"]},{"url":"https://bugzilla.suse.com/1267437","tags":["report"]},{"url":"https://bugzilla.suse.com/1267458","tags":["report"]},{"url":"https://bugzilla.suse.com/1267493","tags":["report"]},{"url":"https://bugzilla.suse.com/1267505","tags":["report"]},{"url":"https://bugzilla.suse.com/1267548","tags":["report"]},{"url":"https://bugzilla.suse.com/1267582","tags":["report"]},{"url":"https://bugzilla.suse.com/1267591","tags":["report"]},{"url":"https://bugzilla.suse.com/1267600","tags":["report"]},{"url":"https://bugzilla.suse.com/1267618","tags":["report"]},{"url":"https://bugzilla.suse.com/1267624","tags":["report"]},{"url":"https://bugzilla.suse.com/1267626","tags":["report"]},{"url":"https://bugzilla.suse.com/1267628","tags":["report"]},{"url":"https://bugzilla.suse.com/1267635","tags":["report"]},{"url":"https://bugzilla.suse.com/1267637","tags":["report"]},{"url":"https://bugzilla.suse.com/1267640","tags":["report"]},{"url":"https://bugzilla.suse.com/1267654","tags":["report"]},{"url":"https://bugzilla.suse.com/1267682","tags":["report"]},{"url":"https://bugzilla.suse.com/1267684","tags":["report"]},{"url":"https://bugzilla.suse.com/1267685","tags":["report"]},{"url":"https://bugzilla.suse.com/1267697","tags":["report"]},{"url":"https://bugzilla.suse.com/1267717","tags":["report"]},{"url":"https://bugzilla.suse.com/1267722","tags":["report"]},{"url":"https://bugzilla.suse.com/1267732","tags":["report"]},{"url":"https://bugzilla.suse.com/1267744","tags":["report"]},{"url":"https://bugzilla.suse.com/1267816","tags":["report"]},{"url":"https://bugzilla.suse.com/1267824","tags":["report"]},{"url":"https://bugzilla.suse.com/1267825","tags":["report"]},{"url":"https://bugzilla.suse.com/1267937","tags":["report"]},{"url":"https://bugzilla.suse.com/1267966","tags":["report"]},{"url":"https://bugzilla.suse.com/1267992","tags":["report"]},{"url":"https://bugzilla.suse.com/1267993","tags":["report"]},{"url":"https://bugzilla.suse.com/1267994","tags":["report"]},{"url":"https://bugzilla.suse.com/1268022","tags":["report"]},{"url":"https://bugzilla.suse.com/1268037","tags":["report"]},{"url":"https://bugzilla.suse.com/1268237","tags":["report"]},{"url":"https://bugzilla.suse.com/1268238","tags":["report"]},{"url":"https://bugzilla.suse.com/1268276","tags":["report"]},{"url":"https://bugzilla.suse.com/1268307","tags":["report"]},{"url":"https://bugzilla.suse.com/1268335","tags":["report"]},{"url":"https://bugzilla.suse.com/1268428","tags":["report"]},{"url":"https://bugzilla.suse.com/1268660","tags":["report"]},{"url":"https://bugzilla.suse.com/1268661","tags":["report"]},{"url":"https://bugzilla.suse.com/1268989","tags":["report"]},{"url":"https://bugzilla.suse.com/1269022","tags":["report"]},{"url":"https://bugzilla.suse.com/1269031","tags":["report"]},{"url":"https://bugzilla.suse.com/1269033","tags":["report"]},{"url":"https://bugzilla.suse.com/1269036","tags":["report"]},{"url":"https://bugzilla.suse.com/1269087","tags":["report"]},{"url":"https://bugzilla.suse.com/1269103","tags":["report"]},{"url":"https://bugzilla.suse.com/1269135","tags":["report"]},{"url":"https://bugzilla.suse.com/1269136","tags":["report"]},{"url":"https://bugzilla.suse.com/1269137","tags":["report"]},{"url":"https://bugzilla.suse.com/1269151","tags":["report"]},{"url":"https://bugzilla.suse.com/1269159","tags":["report"]},{"url":"https://bugzilla.suse.com/1269164","tags":["report"]},{"url":"https://bugzilla.suse.com/1269188","tags":["report"]},{"url":"https://bugzilla.suse.com/1269193","tags":["report"]},{"url":"https://bugzilla.suse.com/1269199","tags":["report"]},{"url":"https://bugzilla.suse.com/1269230","tags":["report"]},{"url":"https://bugzilla.suse.com/1269234","tags":["report"]},{"url":"https://bugzilla.suse.com/1269252","tags":["report"]},{"url":"https://bugzilla.suse.com/1269262","tags":["report"]},{"url":"https://bugzilla.suse.com/1269288","tags":["report"]},{"url":"https://bugzilla.suse.com/1269310","tags":["report"]},{"url":"https://bugzilla.suse.com/1269389","tags":["report"]},{"url":"https://bugzilla.suse.com/1269392","tags":["report"]},{"url":"https://bugzilla.suse.com/1269397","tags":["report"]},{"url":"https://bugzilla.suse.com/1269398","tags":["report"]},{"url":"https://bugzilla.suse.com/1269416","tags":["report"]},{"url":"https://bugzilla.suse.com/1269418","tags":["report"]},{"url":"https://bugzilla.suse.com/1269493","tags":["report"]},{"url":"https://bugzilla.suse.com/1269506","tags":["report"]},{"url":"https://bugzilla.suse.com/1269519","tags":["report"]},{"url":"https://bugzilla.suse.com/1269527","tags":["report"]},{"url":"https://bugzilla.suse.com/1269531","tags":["report"]},{"url":"https://bugzilla.suse.com/1269532","tags":["report"]},{"url":"https://bugzilla.suse.com/1269537","tags":["report"]},{"url":"https://bugzilla.suse.com/1269587","tags":["report"]},{"url":"https://bugzilla.suse.com/1269617","tags":["report"]},{"url":"https://bugzilla.suse.com/1269645","tags":["report"]},{"url":"https://bugzilla.suse.com/1269646","tags":["report"]},{"url":"https://bugzilla.suse.com/1269647","tags":["report"]},{"url":"https://bugzilla.suse.com/1269651","tags":["report"]},{"url":"https://bugzilla.suse.com/1269680","tags":["report"]},{"url":"https://bugzilla.suse.com/1269690","tags":["report"]},{"url":"https://bugzilla.suse.com/1269691","tags":["report"]},{"url":"https://bugzilla.suse.com/1269700","tags":["report"]},{"url":"https://bugzilla.suse.com/1269708","tags":["report"]},{"url":"https://bugzilla.suse.com/1269710","tags":["report"]},{"url":"https://bugzilla.suse.com/1269768","tags":["report"]},{"url":"https://bugzilla.suse.com/1269795","tags":["report"]},{"url":"https://bugzilla.suse.com/1269798","tags":["report"]},{"url":"https://bugzilla.suse.com/1269809","tags":["report"]},{"url":"https://bugzilla.suse.com/1269814","tags":["report"]},{"url":"https://bugzilla.suse.com/1269821","tags":["report"]},{"url":"https://bugzilla.suse.com/1269904","tags":["report"]},{"url":"https://bugzilla.suse.com/1269982","tags":["report"]},{"url":"https://bugzilla.suse.com/1269989","tags":["report"]},{"url":"https://bugzilla.suse.com/1269992","tags":["report"]},{"url":"https://bugzilla.suse.com/1270000","tags":["report"]},{"url":"https://bugzilla.suse.com/1270022","tags":["report"]},{"url":"https://bugzilla.suse.com/1270042","tags":["report"]},{"url":"https://bugzilla.suse.com/1270059","tags":["report"]},{"url":"https://bugzilla.suse.com/1270226","tags":["report"]},{"url":"https://bugzilla.suse.com/1271366","tags":["report"]},{"url":"https://www.suse.com/security/cve/CVE-2025-10263","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-39894","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-40341","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23248","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23394","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23451","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-31414","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-31429","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-31438","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-31450","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-31452","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-31466","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-31469","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-31479","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-31492","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-31495","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-31499","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-31502","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-31555","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-31560","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-31580","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-31596","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-31646","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-31647","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-31663","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-31664","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-31665","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-31670","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-31673","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-31674","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-31680","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-31693","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-31743","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-31752","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-31771","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-43010","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-43014","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-43015","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-43016","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-43022","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-43024","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-43028","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-43034","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-43035","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-43036","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-43053","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-43057","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-43074","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-43080","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-43081","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-43083","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-43085","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-43086","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-43089","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-43090","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-43092","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-43093","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-43094","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-43101","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-43107","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-43119","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-43124","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-43128","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-43130","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-43132","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-43139","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-43145","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-43157","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-43158","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-43161","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-43167","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-43171","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-43175","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-43187","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-43191","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-43194","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-43198","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-43199","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-43205","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-43213","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-43226","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-43233","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-43238","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-43240","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-43248","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-43260","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-43283","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-43284","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-43298","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-43303","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-43336","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-43337","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-43339","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-43345","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-43351","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-43373","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-43374","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-43383","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-43384","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-43386","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-43403","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-43405","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-43406","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-43407","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-43415","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-43449","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-43450","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-43452","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-43456","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-43457","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-43458","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-43465","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-43466","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-43468","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-43469","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-43470","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-43471","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-43491","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-43492","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-43502","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-45837","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-45838","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-45840","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-45841","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-45848","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-45857","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-45858","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-45861","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-45862","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-45870","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-45884","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-45888","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-45891","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-45894","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-45899","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-45901","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-45912","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-45920","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-45922","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-45933","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-45940","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-45948","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-45961","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-45964","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-45965","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-45974","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-45983","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-45985","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-45997","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-45999","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-46005","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-46024","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-46037","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-46046","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-46050","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-46051","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-46053","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-46063","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-46065","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-46069","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-46071","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-46076","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-46078","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-46079","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-46091","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-46093","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-46099","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-46101","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-46111","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-46112","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-46116","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-46119","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-46120","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-46124","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-46150","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-46160","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-46161","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-46162","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-46172","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-46173","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-46178","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-46185","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-46214","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-46227","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-46242","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-46244","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-46253","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-46254","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-46259","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-46266","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-46289","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-46291","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-46314","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-46319","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-46320","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-46322","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-46328","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-46331","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-52908","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-52909","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-52919","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-52923","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-52924","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-52933","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-52943","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-52954","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-52955","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-52957","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-52962","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-52975","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-52980","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-52993","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-53015","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-53021","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-53036","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-53039","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-53040","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-53041","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-53049","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-53050","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-53053","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-53060","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-53075","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-53078","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-53081","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-53086","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-53090","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-53103","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-53122","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-53133","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-53139","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-53156","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-53167","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-53168","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-53176","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-53178","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-53194","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-53215","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-53216","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-53217","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-53229","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-53249","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-53258","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-53262","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-53263","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-53266","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-53272","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-53274","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-53281","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-53285","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-53286","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-53287","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-53306","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-53359","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-53362","tags":["web"]},{"url":"https://www.suse.com/support/update/announcement/2026/suse-su-202622769-1/","tags":["advisory"]},{"url":"https://www.suse.com/support/update/announcement/2026/suse-su-202622812-1/","tags":["advisory"]},{"url":"https://www.suse.com/support/update/announcement/2026/suse-su-202622835-1/","tags":["advisory"]},{"url":"https://ubuntu.com/security/CVE-2026-23394","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2026-23394","tags":["report"]},{"url":"https://git.kernel.org/linus/e5b31d988a41549037b8d8721a3c3cae893d8670","tags":["report"]},{"url":"https://ubuntu.com/security/notices/USN-8277-1","tags":["advisory"]},{"url":"https://ubuntu.com/security/notices/USN-8278-1","tags":["advisory"]},{"url":"https://ubuntu.com/security/notices/USN-8289-1","tags":["advisory"]},{"url":"https://ubuntu.com/security/notices/USN-8277-2","tags":["advisory"]},{"url":"https://ubuntu.com/security/notices/USN-8296-1","tags":["advisory"]},{"url":"https://ubuntu.com/security/notices/USN-8296-2","tags":["advisory"]},{"url":"https://ubuntu.com/security/notices/USN-8289-2","tags":["advisory"]},{"url":"https://ubuntu.com/security/notices/USN-8278-2","tags":["advisory"]},{"url":"https://ubuntu.com/security/notices/USN-8310-1","tags":["advisory"]},{"url":"https://ubuntu.com/security/notices/USN-8374-1","tags":["advisory"]},{"url":"https://ubuntu.com/security/notices/USN-8393-1","tags":["advisory"]},{"url":"https://ubuntu.com/security/notices/USN-8440-1","tags":["advisory"]},{"url":"https://ubuntu.com/security/notices/USN-8499-1","tags":["advisory"]},{"url":"https://ubuntu.com/security/notices/USN-8508-1","tags":["advisory"]},{"url":"https://ubuntu.com/security/CVE-2025-71088","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71090","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71127","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71134","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71139","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71141","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71142","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71144","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71152","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71155","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23274","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23351","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31419","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31431","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31504","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31533","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43033","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43077","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43078","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50004","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-58096","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-58097","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-37926","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38201","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38591","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40039","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40082","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40149","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68351","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68358","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68365","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68725","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68749","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68803","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68823","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71160","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-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-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-71220","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71222","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71224","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71225","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71268","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-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-22984","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-22990","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-22991","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-22992","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-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-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-23010","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23011","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-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-23035","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-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-23053","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23054","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-23068","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23069","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23071","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23073","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23075","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23076","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23078","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23080","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23083","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23084","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23085","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-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-23091","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-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-23107","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23108","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23110","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23113","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23116","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-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-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-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-23139","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23140","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23141","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23142","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23144","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23145","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23146","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-23156","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23159","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23160","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23163","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23164","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-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-23176","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23178","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23179","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23180","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23182","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23187","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23190","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23191","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23193","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23198","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23200","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23202","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23204","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23205","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23206","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23212","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23213","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23214","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23215","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23216","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23254","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23256","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23257","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23258","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23260","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23261","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23262","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23264","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23454","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43276","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31676","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43284","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43494","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43500","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43503","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-45966","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-45998","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46000","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46028","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46300","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46333","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-47326","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-47327","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-47328","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-47329","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-47330","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-47332","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-47333","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-47334","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-47337","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-47331","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-47335","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-47336","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-36347","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-57795","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-22022","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-22111","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38022","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38234","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40164","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40325","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68206","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68254","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68255","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68256","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68257","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68258","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68259","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68261","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68263","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68264","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68265","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68266","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68291","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68325","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68332","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68335","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68336","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68337","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68344","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68345","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68346","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68347","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68349","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68354","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68362","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68363","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68364","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68366","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68367","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68369","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68371","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68372","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68374","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68378","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68379","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68380","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68724","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68727","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68728","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68732","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68733","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68740","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68741","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68742","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68744","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68746","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68753","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68755","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68756","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68757","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68758","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68759","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68763","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68764","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68765","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68766","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68767","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68769","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68770","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68771","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68772","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68773","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68774","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68775","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68776","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68777","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68778","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68780","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68782","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68783","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68785","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68786","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68787","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68788","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68794","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68795","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68796","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68797","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68798","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68799","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68800","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68801","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68804","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68806","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68808","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68809","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68810","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68811","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68813","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68814","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68815","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68816","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68817","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68818","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68819","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68820","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68821","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71064","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71065","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71066","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71067","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71068","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71069","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71071","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71072","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71075","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71077","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71078","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71079","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71081","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71082","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71083","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71084","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71085","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71086","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71087","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71089","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71091","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71093","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71094","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71095","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71096","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71097","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71098","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71101","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71102","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71104","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71105","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71107","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71108","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71109","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71111","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71112","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71113","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71114","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71116","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71118","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71119","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71120","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71121","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71122","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71123","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71125","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71126","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71130","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71131","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71132","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71133","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71135","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71136","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71137","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71138","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71140","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71143","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71147","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71148","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71150","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71151","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71153","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71154","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23112","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23209","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23231","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43362","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46323","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40005","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71229","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71231","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71232","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71233","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71235","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71236","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71237","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71238","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71239","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71265","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71266","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71267","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71272","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71273","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71274","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71286","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71291","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71292","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71294","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71295","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71297","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71304","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71305","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23100","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23169","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23220","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23221","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23222","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23228","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23229","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23230","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23233","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23234","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23235","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23236","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23237","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23238","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23241","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23242","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23243","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23249","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23266","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23267","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23272","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23278","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23392","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23428","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23450","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23455","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31402","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31411","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31418","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31436","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31448","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31478","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31607","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31637","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31649","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31657","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31659","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31668","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31669","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31682","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31685","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31687","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31693","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43011","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43037","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43038","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43071","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43114","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43117","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43123","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43124","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43128","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43130","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43132","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43133","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43134","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43135","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43136","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43137","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43139","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43140","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43141","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43143","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43145","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43147","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43148","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43149","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43150","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43152","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43153","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43156","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43157","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43158","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43159","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43163","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43167","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43168","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43169","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43170","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43171","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43173","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43175","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43180","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43182","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43183","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43184","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43186","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43187","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43189","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43190","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43194","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43196","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43199","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43200","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43201","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43202","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43203","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43205","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43206","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43207","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43209","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43211","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43212","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43214","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43215","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43218","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43221","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43222","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43223","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43225","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43226","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43227","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43230","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43231","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43232","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43233","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43236","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43238","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43239","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43241","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43242","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43244","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43246","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43248","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43249","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43250","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43251","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43253","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43255","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43256","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43257","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43258","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43261","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43262","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43264","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43266","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43268","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43269","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43270","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43271","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43273","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43275","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43277","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43278","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43279","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43283","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43287","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43288","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43289","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43291","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43295","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43296","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43297","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43300","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43302","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43304","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43312","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43313","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43314","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43315","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43316","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43317","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43318","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43319","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43320","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43341","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43378","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43383","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43384","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43406","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43407","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43414","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43493","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43501","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-45847","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-45848","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-45849","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-45851","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-45852","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-45856","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-45857","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-45859","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-45860","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-45861","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-45862","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-45864","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-45865","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-45866","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-45867","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-45868","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-45869","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-45870","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-45871","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-45872","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-45873","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-45875","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-45877","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-45878","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-45879","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-45880","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-45881","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-45882","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-45883","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-45884","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-45885","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-45886","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-45890","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-45891","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-45893","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-45895","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-45902","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-45904","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-45905","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-45910","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-45912","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-45913","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-45914","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-45915","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-45916","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-45917","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-45919","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-45921","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-45923","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-45928","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-45935","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-45936","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-45938","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-45941","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-45946","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-45947","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-45948","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-45954","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-45957","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-45960","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-45962","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-45964","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-45965","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-45968","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-45969","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-45970","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-45973","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-45974","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-45976","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-45978","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-45981","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-45982","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-45983","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-45984","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-45988","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46043","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46115","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46119","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46135","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46185","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46195","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46243","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46244","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46246","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46247","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46249","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46250","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46251","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46253","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46254","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46255","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46259","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46261","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46265","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46266","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46267","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46270","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46289","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46328","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23273","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23427","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31635","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31718","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43083","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43125","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43197","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43376","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43402","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-45898","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46039","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46316","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46325","tags":["report"]},{"url":"","tags":["advisory"]}],"sources":{"cve":[{"id":"CVE-2026-23394","title":"af_unix: Give up GC if MSG_PEEK intervened.","description":"In the Linux kernel, the following vulnerability has been resolved:\n\naf_unix: Give up GC if MSG_PEEK intervened.\n\nIgor Ushakov reported that GC purged the receive queue of\nan alive socket due to a race with MSG_PEEK with a nice repro.\n\nThis is the exact same issue previously fixed by commit\ncbcf01128d0a (\"af_unix: fix garbage collect vs MSG_PEEK\").\n\nAfter GC was replaced with the current algorithm, the cited\ncommit removed the locking dance in unix_peek_fds() and\nreintroduced the same issue.\n\nThe problem is that MSG_PEEK bumps a file refcount without\ninteracting with GC.\n\nConsider an SCC containing sk-A and sk-B, where sk-A is\nclose()d but can be recv()ed via sk-B.\n\nThe bad thing happens if sk-A is recv()ed with MSG_PEEK from\nsk-B and sk-B is close()d while GC is checking unix_vertex_dead()\nfor sk-A and sk-B.\n\n  GC thread                    User thread\n  ---------                    -----------\n  unix_vertex_dead(sk-A)\n  -\u003e true   \u003c------.\n                    \\\n                     `------   recv(sk-B, MSG_PEEK)\n              invalidate !!    -\u003e sk-A's file refcount : 1 -\u003e 2\n\n                               close(sk-B)\n                               -\u003e sk-B's file refcount : 2 -\u003e 1\n  unix_vertex_dead(sk-B)\n  -\u003e true\n\nInitially, sk-A's file refcount is 1 by the inflight fd in sk-B\nrecvq.  GC thinks sk-A is dead because the file refcount is the\nsame as the number of its inflight fds.\n\nHowever, sk-A's file refcount is bumped silently by MSG_PEEK,\nwhich invalidates the previous evaluation.\n\nAt this moment, sk-B's file refcount is 2; one by the open fd,\nand one by the inflight fd in sk-A.  The subsequent close()\nreleases one refcount by the former.\n\nFinally, GC incorrectly concludes that both sk-A and sk-B are dead.\n\nOne option is to restore the locking dance in unix_peek_fds(),\nbut we can resolve this more elegantly thanks to the new algorithm.\n\nThe point is that the issue does not occur without the subsequent\nclose() and we actually do not need to synchronise MSG_PEEK with\nthe dead SCC detection.\n\nWhen the issue occurs, close() and GC touch the same file refcount.\nIf GC sees the refcount being decremented by close(), it can just\ngive up garbage-collecting the SCC.\n\nTherefore, we only need to signal the race during MSG_PEEK with\na proper memory barrier to make it visible to the GC.\n\nLet's use seqcount_t to notify GC when MSG_PEEK occurs and let\nit defer the SCC to the next run.\n\nThis way no locking is needed on the MSG_PEEK side, and we can\navoid imposing a penalty on every MSG_PEEK unnecessarily.\n\nNote that we can retry within unix_scc_dead() if MSG_PEEK is\ndetected, but we do not do so to avoid hung task splat from\nabusive MSG_PEEK calls.","status":"published","published":"2026-03-25T10:33:18.18Z","modified":"2026-08-19T16:27:54.571Z","updated_at":"2026-11-02T13:42:04.39372Z"}],"euvd":[{"id":"EUVD-2026-15396","description":"In the Linux kernel, the following vulnerability has been resolved:\n\naf_unix: Give up GC if MSG_PEEK intervened.\n\nIgor Ushakov reported that GC purged the receive queue of\nan alive socket due to a race with MSG_PEEK with a nice repro.\n\nThis is the exact same issue previously fixed by commit\ncbcf01128d0a (\"af_unix: fix garbage collect vs MSG_PEEK\").\n\nAfter GC was replaced with the current algorithm, the cited\ncommit removed the locking dance in unix_peek_fds() and\nreintroduced the same issue.\n\nThe problem is that MSG_PEEK bumps a file refcount without\ninteracting with GC.\n\nConsider an SCC containing sk-A and sk-B, where sk-A is\nclose()d but can be recv()ed via sk-B.\n\nThe bad thing happens if sk-A is recv()ed with MSG_PEEK from\nsk-B and sk-B is close()d while GC is checking unix_vertex_dead()\nfor sk-A and sk-B.\n\n  GC thread                    User thread\n  ---------                    -----------\n  unix_vertex_dead(sk-A)\n  -\u003e true   \u003c------.\n                    \\\n                     `------   recv(sk-B, MSG_PEEK)\n              invalidate !!    -\u003e sk-A's file refcount : 1 -\u003e 2\n\n                               close(sk-B)\n                               -\u003e sk-B's file refcount : 2 -\u003e 1\n  unix_vertex_dead(sk-B)\n  -\u003e true\n\nInitially, sk-A's file refcount is 1 by the inflight fd in sk-B\nrecvq.  GC thinks sk-A is dead because the file refcount is the\nsame as the number of its inflight fds.\n\nHowever, sk-A's file refcount is bumped silently by MSG_PEEK,\nwhich invalidates the previous evaluation.\n\nAt this moment, sk-B's file refcount is 2; one by the open fd,\nand one by the inflight fd in sk-A.  The subsequent close()\nreleases one refcount by the former.\n\nFinally, GC incorrectly concludes that both sk-A and sk-B are dead.\n\nOne option is to restore the locking dance in unix_peek_fds(),\nbut we can resolve this more elegantly thanks to the new algorithm.\n\nThe point is that the issue does not occur without the subsequent\nclose() and we actually do not need to synchronise MSG_PEEK with\nthe dead SCC detection.\n\nWhen the issue occurs, close() and GC touch the same file refcount.\nIf GC sees the refcount being decremented by close(), it can just\ngive up garbage-collecting the SCC.\n\nTherefore, we only need to signal the race during MSG_PEEK with\na proper memory barrier to make it visible to the GC.\n\nLet's use seqcount_t to notify GC when MSG_PEEK occurs and let\nit defer the SCC to the next run.\n\nThis way no locking is needed on the MSG_PEEK side, and we can\navoid imposing a penalty on every MSG_PEEK unnecessarily.\n\nNote that we can retry within unix_scc_dead() if MSG_PEEK is\ndetected, but we do not do so to avoid hung task splat from\nabusive MSG_PEEK calls.","status":"published","published":"2026-03-25T10:33:18Z","modified":"2026-08-19T16:27:54Z","updated_at":"2026-11-02T18:01:42.811156Z"}],"ghsa":[{"id":"GHSA-p5pc-67g7-qcv2","title":"In the Linux kernel, the following vulnerability has been resolved:\n\naf_unix: Give up GC if...","description":"In the Linux kernel, the following vulnerability has been resolved:\n\naf_unix: Give up GC if MSG_PEEK intervened.\n\nIgor Ushakov reported that GC purged the receive queue of\nan alive socket due to a race with MSG_PEEK with a nice repro.\n\nThis is the exact same issue previously fixed by commit\ncbcf01128d0a (\"af_unix: fix garbage collect vs MSG_PEEK\").\n\nAfter GC was replaced with the current algorithm, the cited\ncommit removed the locking dance in unix_peek_fds() and\nreintroduced the same issue.\n\nThe problem is that MSG_PEEK bumps a file refcount without\ninteracting with GC.\n\nConsider an SCC containing sk-A and sk-B, where sk-A is\nclose()d but can be recv()ed via sk-B.\n\nThe bad thing happens if sk-A is recv()ed with MSG_PEEK from\nsk-B and sk-B is close()d while GC is checking unix_vertex_dead()\nfor sk-A and sk-B.\n\n  GC thread                    User thread\n  ---------                    -----------\n  unix_vertex_dead(sk-A)\n  -\u003e true   \u003c------.\n                    \\\n                     `------   recv(sk-B, MSG_PEEK)\n              invalidate !!    -\u003e sk-A's file refcount : 1 -\u003e 2\n\n                               close(sk-B)\n                               -\u003e sk-B's file refcount : 2 -\u003e 1\n  unix_vertex_dead(sk-B)\n  -\u003e true\n\nInitially, sk-A's file refcount is 1 by the inflight fd in sk-B\nrecvq.  GC thinks sk-A is dead because the file refcount is the\nsame as the number of its inflight fds.\n\nHowever, sk-A's file refcount is bumped silently by MSG_PEEK,\nwhich invalidates the previous evaluation.\n\nAt this moment, sk-B's file refcount is 2; one by the open fd,\nand one by the inflight fd in sk-A.  The subsequent close()\nreleases one refcount by the former.\n\nFinally, GC incorrectly concludes that both sk-A and sk-B are dead.\n\nOne option is to restore the locking dance in unix_peek_fds(),\nbut we can resolve this more elegantly thanks to the new algorithm.\n\nThe point is that the issue does not occur without the subsequent\nclose() and we actually do not need to synchronise MSG_PEEK with\nthe dead SCC detection.\n\nWhen the issue occurs, close() and GC touch the same file refcount.\nIf GC sees the refcount being decremented by close(), it can just\ngive up garbage-collecting the SCC.\n\nTherefore, we only need to signal the race during MSG_PEEK with\na proper memory barrier to make it visible to the GC.\n\nLet's use seqcount_t to notify GC when MSG_PEEK occurs and let\nit defer the SCC to the next run.\n\nThis way no locking is needed on the MSG_PEEK side, and we can\navoid imposing a penalty on every MSG_PEEK unnecessarily.\n\nNote that we can retry within unix_scc_dead() if MSG_PEEK is\ndetected, but we do not do so to avoid hung task splat from\nabusive MSG_PEEK calls.","status":"published","published":"2026-03-25T12:30:24Z","modified":"2026-08-19T18:33:03Z","cvss":[{"version":"3.1","score":4.7,"vector":"CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:H","level":"medium"}],"cwes":["CWE-362"],"updated_at":"2026-11-02T15:10:43.503566Z"}],"nvd":[{"id":"CVE-2026-23394","description":"In the Linux kernel, the following vulnerability has been resolved:\n\naf_unix: Give up GC if MSG_PEEK intervened.\n\nIgor Ushakov reported that GC purged the receive queue of\nan alive socket due to a race with MSG_PEEK with a nice repro.\n\nThis is the exact same issue previously fixed by commit\ncbcf01128d0a (\"af_unix: fix garbage collect vs MSG_PEEK\").\n\nAfter GC was replaced with the current algorithm, the cited\ncommit removed the locking dance in unix_peek_fds() and\nreintroduced the same issue.\n\nThe problem is that MSG_PEEK bumps a file refcount without\ninteracting with GC.\n\nConsider an SCC containing sk-A and sk-B, where sk-A is\nclose()d but can be recv()ed via sk-B.\n\nThe bad thing happens if sk-A is recv()ed with MSG_PEEK from\nsk-B and sk-B is close()d while GC is checking unix_vertex_dead()\nfor sk-A and sk-B.\n\n  GC thread                    User thread\n  ---------                    -----------\n  unix_vertex_dead(sk-A)\n  -\u003e true   \u003c------.\n                    \\\n                     `------   recv(sk-B, MSG_PEEK)\n              invalidate !!    -\u003e sk-A's file refcount : 1 -\u003e 2\n\n                               close(sk-B)\n                               -\u003e sk-B's file refcount : 2 -\u003e 1\n  unix_vertex_dead(sk-B)\n  -\u003e true\n\nInitially, sk-A's file refcount is 1 by the inflight fd in sk-B\nrecvq.  GC thinks sk-A is dead because the file refcount is the\nsame as the number of its inflight fds.\n\nHowever, sk-A's file refcount is bumped silently by MSG_PEEK,\nwhich invalidates the previous evaluation.\n\nAt this moment, sk-B's file refcount is 2; one by the open fd,\nand one by the inflight fd in sk-A.  The subsequent close()\nreleases one refcount by the former.\n\nFinally, GC incorrectly concludes that both sk-A and sk-B are dead.\n\nOne option is to restore the locking dance in unix_peek_fds(),\nbut we can resolve this more elegantly thanks to the new algorithm.\n\nThe point is that the issue does not occur without the subsequent\nclose() and we actually do not need to synchronise MSG_PEEK with\nthe dead SCC detection.\n\nWhen the issue occurs, close() and GC touch the same file refcount.\nIf GC sees the refcount being decremented by close(), it can just\ngive up garbage-collecting the SCC.\n\nTherefore, we only need to signal the race during MSG_PEEK with\na proper memory barrier to make it visible to the GC.\n\nLet's use seqcount_t to notify GC when MSG_PEEK occurs and let\nit defer the SCC to the next run.\n\nThis way no locking is needed on the MSG_PEEK side, and we can\navoid imposing a penalty on every MSG_PEEK unnecessarily.\n\nNote that we can retry within unix_scc_dead() if MSG_PEEK is\ndetected, but we do not do so to avoid hung task splat from\nabusive MSG_PEEK calls.","status":"published","published":"2026-03-25T11:16:40.19Z","modified":"2026-08-19T17:18:45.96Z","cvss":[{"version":"3.1","score":4.7,"vector":"CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:H","level":"medium","assessor":"primary"}],"cwes":["CWE-362"],"updated_at":"2026-11-02T14:12:11.077116Z"}],"osv":[{"id":"BELL-CVE-2026-23394","status":"published","published":"2026-03-26T06:08:26.985698Z","modified":"2026-10-07T07:15:16.061033315Z","cvss":[{"version":"3.1","score":4.7,"vector":"CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:H","level":"medium"}],"updated_at":"2026-11-02T15:28:23.315185Z"},{"id":"DEBIAN-CVE-2026-23394","description":"In the Linux kernel, the following vulnerability has been resolved:  af_unix: Give up GC if MSG_PEEK intervened.  Igor Ushakov reported that GC purged the receive queue of an alive socket due to a race with MSG_PEEK with a nice repro.  This is the exact same issue previously fixed by commit cbcf01128d0a (\"af_unix: fix garbage collect vs MSG_PEEK\").  After GC was replaced with the current algorithm, the cited commit removed the locking dance in unix_peek_fds() and reintroduced the same issue.  The problem is that MSG_PEEK bumps a file refcount without interacting with GC.  Consider an SCC containing sk-A and sk-B, where sk-A is close()d but can be recv()ed via sk-B.  The bad thing happens if sk-A is recv()ed with MSG_PEEK from sk-B and sk-B is close()d while GC is checking unix_vertex_dead() for sk-A and sk-B.    GC thread                    User thread   ---------                    -----------   unix_vertex_dead(sk-A)   -\u003e true   \u003c------.                     \\                      `------   recv(sk-B, MSG_PEEK)               invalidate !!    -\u003e sk-A's file refcount : 1 -\u003e 2                                 close(sk-B)                                -\u003e sk-B's file refcount : 2 -\u003e 1   unix_vertex_dead(sk-B)   -\u003e true  Initially, sk-A's file refcount is 1 by the inflight fd in sk-B recvq.  GC thinks sk-A is dead because the file refcount is the same as the number of its inflight fds.  However, sk-A's file refcount is bumped silently by MSG_PEEK, which invalidates the previous evaluation.  At this moment, sk-B's file refcount is 2; one by the open fd, and one by the inflight fd in sk-A.  The subsequent close() releases one refcount by the former.  Finally, GC incorrectly concludes that both sk-A and sk-B are dead.  One option is to restore the locking dance in unix_peek_fds(), but we can resolve this more elegantly thanks to the new algorithm.  The point is that the issue does not occur without the subsequent close() and we actually do not need to synchronise MSG_PEEK with the dead SCC detection.  When the issue occurs, close() and GC touch the same file refcount. If GC sees the refcount being decremented by close(), it can just give up garbage-collecting the SCC.  Therefore, we only need to signal the race during MSG_PEEK with a proper memory barrier to make it visible to the GC.  Let's use seqcount_t to notify GC when MSG_PEEK occurs and let it defer the SCC to the next run.  This way no locking is needed on the MSG_PEEK side, and we can avoid imposing a penalty on every MSG_PEEK unnecessarily.  Note that we can retry within unix_scc_dead() if MSG_PEEK is detected, but we do not do so to avoid hung task splat from abusive MSG_PEEK calls.","status":"published","published":"2026-03-25T11:16:40.19Z","modified":"2026-10-01T03:02:32.131748628Z","cvss":[{"version":"3.1","score":4.7,"vector":"CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:H","level":"medium"}],"updated_at":"2026-11-02T15:45:53.516942Z"},{"id":"OESA-2026-1862","title":"kernel security update","description":"The Linux Kernel, the operating system core itself.\r\n\r\nSecurity Fix(es):\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nf2fs: fix to detect potential corrupted nid in free_nid_list\n\nAs reported, on-disk footer.ino and footer.nid is the same and\nout-of-range, let\u0026apos;s add sanity check on f2fs_alloc_nid() to detect\nany potential corruption in free_nid_list.(CVE-2025-68315)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nntfs3: Fix uninit buffer allocated by __getname()\n\nFix uninit errors caused after buffer allocation given to \u0026apos;de\u0026apos;; by\ninitializing the buffer with zeroes. The fix was found by using KMSAN.(CVE-2025-68727)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnetfilter: nf_tables: fix use-after-free in nf_tables_addchain()\n\nnf_tables_addchain() publishes the chain to table-\u0026gt;chains via\nlist_add_tail_rcu() (in nft_chain_add()) before registering hooks.\nIf nf_tables_register_hook() then fails, the error path calls\nnft_chain_del() (list_del_rcu()) followed by nf_tables_chain_destroy()\nwith no RCU grace period in between.\n\nThis creates two use-after-free conditions:\n\n 1) Control-plane: nf_tables_dump_chains() traverses table-\u0026gt;chains\n    under rcu_read_lock(). A concurrent dump can still be walking\n    the chain when the error path frees it.\n\n 2) Packet path: for NFPROTO_INET, nf_register_net_hook() briefly\n    installs the IPv4 hook before IPv6 registration fails.  Packets\n    entering nft_do_chain() via the transient IPv4 hook can still be\n    dereferencing chain-\u0026gt;blob_gen_X when the error path frees the\n    chain.\n\nAdd synchronize_rcu() between nft_chain_del() and the chain destroy\nso that all RCU readers -- both dump threads and in-flight packet\nevaluation -- have finished before the chain is freed.(CVE-2026-23231)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ntls: Fix race condition in tls_sw_cancel_work_tx()\n\nThis issue was discovered during a code audit.\n\nAfter cancel_delayed_work_sync() is called from tls_sk_proto_close(),\ntx_work_handler() can still be scheduled from paths such as the\nDelayed ACK handler or ksoftirqd.\nAs a result, the tx_work_handler() worker may dereference a freed\nTLS object.\n\nThe following is a simple race scenario:\n\n          cpu0                         cpu1\n\ntls_sk_proto_close()\n  tls_sw_cancel_work_tx()\n                                 tls_write_space()\n                                   tls_sw_write_space()\n                                     if (!test_and_set_bit(BIT_TX_SCHEDULED, \u0026amp;tx_ctx-\u0026gt;tx_bitmask))\n    set_bit(BIT_TX_SCHEDULED, \u0026amp;ctx-\u0026gt;tx_bitmask);\n    cancel_delayed_work_sync(\u0026amp;ctx-\u0026gt;tx_work.work);\n                                     schedule_delayed_work(\u0026amp;tx_ctx-\u0026gt;tx_work.work, 0);\n\nTo prevent this race condition, cancel_delayed_work_sync() is\nreplaced with disable_delayed_work_sync().(CVE-2026-23240)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnet/sched: act_gate: snapshot parameters with RCU on replace\n\nThe gate action can be replaced while the hrtimer callback or dump path is\nwalking the schedule list.\n\nConvert the parameters to an RCU-protected snapshot and swap updates under\ntcf_lock, freeing the previous snapshot via call_rcu(). When REPLACE omits\nthe entry list, preserve the existing schedule so the effective state is\nunchanged.(CVE-2026-23245)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnet: gro: fix outer network offset\n\nThe udp GRO complete stage assumes that all the packets inserted the RX\nhave the `encapsulation` flag zeroed. Such assumption is not true, as a\nfew H/W NICs can set such flag when H/W offloading the checksum for\nan UDP encapsulated traffic, the tun driver can inject GSO packets with\nUDP encapsulation and the problematic layout can also be created via\na veth based setup.\n\nDue to the above, in the problematic scenarios, udp4_gro_complete() uses\nthe wrong network offset (inner instead of outer) to compute the outer\nUDP header pseudo checksum, leading to csum validation errors later on\nin packet processing.\n\nAddress the issue always clearing the encapsulation flag at GRO completion\ntime. Such flag will be set again as needed for encapsulated packets by\nudp_gro_complete().(CVE-2026-23254)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnet: add proper RCU protection to /proc/net/ptype\n\nYin Fengwei reported an RCU stall in ptype_seq_show() and provided\na patch.\n\nReal issue is that ptype_seq_next() and ptype_seq_show() violate\nRCU rules.\n\nptype_seq_show() runs under rcu_read_lock(), and reads pt-\u0026gt;dev\nto get device name without any barrier.\n\nAt the same time, concurrent writers can remove a packet_type structure\n(which is correctly freed after an RCU grace period) and clear pt-\u0026gt;dev\nwithout an RCU grace period.\n\nDefine ptype_iter_state to carry a dev pointer along seq_net_private:\n\nstruct ptype_iter_state {\n\tstruct seq_net_private\tp;\n\tstruct net_device\t*dev; // added in this patch\n};\n\nWe need to record the device pointer in ptype_get_idx() and\nptype_seq_next() so that ptype_seq_show() is safe against\nconcurrent pt-\u0026gt;dev changes.\n\nWe also need to add full RCU protection in ptype_seq_next().\n(Missing READ_ONCE() when reading list.next values)\n\nMany thanks to Dong Chenchen for providing a repro.(CVE-2026-23255)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnet/sched: Only allow act_ct to bind to clsact/ingress qdiscs and shared blocks\n\nAs Paolo said earlier [1]:\n\n\u0026quot;Since the blamed commit below, classify can return TC_ACT_CONSUMED while\nthe current skb being held by the defragmentation engine. As reported by\nGangMin Kim, if such packet is that may cause a UaF when the defrag engine\nlater on tries to tuch again such packet.\u0026quot;\n\nact_ct was never meant to be used in the egress path, however some users\nare attaching it to egress today [2]. Attempting to reach a middle\nground, we noticed that, while most qdiscs are not handling\nTC_ACT_CONSUMED, clsact/ingress qdiscs are. With that in mind, we\naddress the issue by only allowing act_ct to bind to clsact/ingress\nqdiscs and shared blocks. That way it\u0026apos;s still possible to attach act_ct to\negress (albeit only with clsact).\n\n[1] https://lore.kernel.org/netdev/674b8cbfc385c6f37fb29a1de08d8fe5c2b0fbee.1771321118.git.pabeni@redhat.com/\n[2] https://lore.kernel.org/netdev/(CVE-2026-23270)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnetfilter: xt_IDLETIMER: reject rev0 reuse of ALARM timer labels\n\nIDLETIMER revision 0 rules reuse existing timers by label and always call\nmod_timer() on timer-\u0026gt;timer.\n\nIf the label was created first by revision 1 with XT_IDLETIMER_ALARM,\nthe object uses alarm timer semantics and timer-\u0026gt;timer is never initialized.\nReusing that object from revision 0 causes mod_timer() on an uninitialized\ntimer_list, triggering debugobjects warnings and possible panic when\npanic_on_warn=1.\n\nFix this by rejecting revision 0 rule insertion when an existing timer with\nthe same label is of ALARM type.(CVE-2026-23274)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnet: add xmit recursion limit to tunnel xmit functions\n\nTunnel xmit functions (iptunnel_xmit, ip6tunnel_xmit) lack their own\nrecursion limit. When a bond device in broadcast mode has GRE tap\ninterfaces as slaves, and those GRE tunnels route back through the\nbond, multicast/broadcast traffic triggers infinite recursion between\nbond_xmit_broadcast() and ip_tunnel_xmit()/ip6_tnl_xmit(), causing\nkernel stack overflow.\n\nThe existing XMIT_RECURSION_LIMIT (8) in the no-qdisc path is not\nsufficient because tunnel recursion involves route lookups and full IP\noutput, consuming much more stack per level. Use a lower limit of 4\n(IP_TUNNEL_RECURSION_LIMIT) to prevent overflow.\n\nAdd recursion detection using dev_xmit_recursion helpers directly in\niptunnel_xmit() and ip6tunnel_xmit() to cover all IPv4/IPv6 tunnel\npaths including UDP encapsulated tunnels (VXLAN, Geneve, etc.).\n\nMove dev_xmit_recursion helpers from net/core/dev.h to public header\ninclude/linux/netdevice.h so they can be used by tunnel code.\n\n BUG: KASAN: stack-out-of-bounds in blake2s.constprop.0+0xe7/0x160\n Write of size 32 at addr ffff88810033fed0 by task kworker/0:1/11\n Workqueue: mld mld_ifc_work\n Call Trace:\n  \u0026lt;TASK\u0026gt;\n  __build_flow_key.constprop.0 (net/ipv4/route.c:515)\n  ip_rt_update_pmtu (net/ipv4/route.c:1073)\n  iptunnel_xmit (net/ipv4/ip_tunnel_core.c:84)\n  ip_tunnel_xmit (net/ipv4/ip_tunnel.c:847)\n  gre_tap_xmit (net/ipv4/ip_gre.c:779)\n  dev_hard_start_xmit (net/core/dev.c:3887)\n  sch_direct_xmit (net/sched/sch_generic.c:347)\n  __dev_queue_xmit (net/core/dev.c:4802)\n  bond_dev_queue_xmit (drivers/net/bonding/bond_main.c:312)\n  bond_xmit_broadcast (drivers/net/bonding/bond_main.c:5279)\n  bond_start_xmit (drivers/net/bonding/bond_main.c:5530)\n  dev_hard_start_xmit (net/core/dev.c:3887)\n  __dev_queue_xmit (net/core/dev.c:4841)\n  ip_finish_output2 (net/ipv4/ip_output.c:237)\n  ip_output (net/ipv4/ip_output.c:438)\n  iptunnel_xmit (net/ipv4/ip_tunnel_core.c:86)\n  gre_tap_xmit (net/ipv4/ip_gre.c:779)\n  dev_hard_start_xmit (net/core/dev.c:3887)\n  sch_direct_xmit (net/sched/sch_generic.c:347)\n  __dev_queue_xmit (net/core/dev.c:4802)\n  bond_dev_queue_xmit (drivers/net/bonding/bond_main.c:312)\n  bond_xmit_broadcast (drivers/net/bonding/bond_main.c:5279)\n  bond_start_xmit (drivers/net/bonding/bond_main.c:5530)\n  dev_hard_start_xmit (net/core/dev.c:3887)\n  __dev_queue_xmit (net/core/dev.c:4841)\n  ip_finish_output2 (net/ipv4/ip_output.c:237)\n  ip_output (net/ipv4/ip_output.c:438)\n  iptunnel_xmit (net/ipv4/ip_tunnel_core.c:86)\n  ip_tunnel_xmit (net/ipv4/ip_tunnel.c:847)\n  gre_tap_xmit (net/ipv4/ip_gre.c:779)\n  dev_hard_start_xmit (net/core/dev.c:3887)\n  sch_direct_xmit (net/sched/sch_generic.c:347)\n  __dev_queue_xmit (net/core/dev.c:4802)\n  bond_dev_queue_xmit (drivers/net/bonding/bond_main.c:312)\n  bond_xmit_broadcast (drivers/net/bonding/bond_main.c:5279)\n  bond_start_xmit (drivers/net/bonding/bond_main.c:5530)\n  dev_hard_start_xmit (net/core/dev.c:3887)\n  __dev_queue_xmit (net/core/dev.c:4841)\n  mld_sendpack\n  mld_ifc_work\n  process_one_work\n  worker_thread\n  \u0026lt;/TASK\u0026gt;(CVE-2026-23276)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnet/sched: teql: fix NULL pointer dereference in iptunnel_xmit on TEQL slave xmit\n\nteql_master_xmit() calls netdev_start_xmit(skb, slave) to transmit\nthrough slave devices, but does not update skb-\u0026gt;dev to the slave device\nbeforehand.\n\nWhen a gretap tunnel is a TEQL slave, the transmit path reaches\niptunnel_xmit() which saves dev = skb-\u0026gt;dev (still pointing to teql0\nmaster) and later calls iptunnel_xmit_stats(dev, pkt_len). This\nfunction does:\n\n    get_cpu_ptr(dev-\u0026gt;tstats)\n\nSince teql_master_setup() does not set dev-\u0026gt;pcpu_stat_type to\nNETDEV_PCPU_STAT_TSTATS, the core network stack never allocates tstats\nfor teql0, so dev-\u0026gt;tstats is NULL. get_cpu_ptr(NULL) computes\nNULL + __per_cpu_offset[cpu], resulting in a page fault.\n\n BUG: unable to handle page fault for address: ffff8880e6659018\n #PF: supervisor write access in kernel mode\n #PF: error_code(0x0002) - not-present page\n PGD 68bc067 P4D 68bc067 PUD 0\n Oops: Oops: 0002 [#1] SMP KASAN PTI\n RIP: 0010:iptunnel_xmit (./include/net/ip_tunnels.h:664 net/ipv4/ip_tunnel_core.c:89)\n Call Trace:\n  \u0026lt;TASK\u0026gt;\n  ip_tunnel_xmit (net/ipv4/ip_tunnel.c:847)\n  __gre_xmit (net/ipv4/ip_gre.c:478)\n  gre_tap_xmit (net/ipv4/ip_gre.c:779)\n  teql_master_xmit (net/sched/sch_teql.c:319)\n  dev_hard_start_xmit (net/core/dev.c:3887)\n  sch_direct_xmit (net/sched/sch_generic.c:347)\n  __dev_queue_xmit (net/core/dev.c:4802)\n  neigh_direct_output (net/core/neighbour.c:1660)\n  ip_finish_output2 (net/ipv4/ip_output.c:237)\n  __ip_finish_output.part.0 (net/ipv4/ip_output.c:315)\n  ip_mc_output (net/ipv4/ip_output.c:369)\n  ip_send_skb (net/ipv4/ip_output.c:1508)\n  udp_send_skb (net/ipv4/udp.c:1195)\n  udp_sendmsg (net/ipv4/udp.c:1485)\n  inet_sendmsg (net/ipv4/af_inet.c:859)\n  __sys_sendto (net/socket.c:2206)\n\nFix this by setting skb-\u0026gt;dev = slave before calling\nnetdev_start_xmit(), so that tunnel xmit functions see the correct\nslave device with properly allocated tstats.(CVE-2026-23277)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnetfilter: nf_tables: always walk all pending catchall elements\n\nDuring transaction processing we might have more than one catchall element:\n1 live catchall element and 1 pending element that is coming as part of the\nnew batch.\n\nIf the map holding the catchall elements is also going away, its\nrequired to toggle all catchall elements and not just the first viable\ncandidate.\n\nOtherwise, we get:\n WARNING: ./include/net/netfilter/nf_tables.h:1281 at nft_data_release+0xb7/0xe0 [nf_tables], CPU#2: nft/1404\n RIP: 0010:nft_data_release+0xb7/0xe0 [nf_tables]\n [..]\n __nft_set_elem_destroy+0x106/0x380 [nf_tables]\n nf_tables_abort_release+0x348/0x8d0 [nf_tables]\n nf_tables_abort+0xcf2/0x3ac0 [nf_tables]\n nfnetlink_rcv_batch+0x9c9/0x20e0 [..](CVE-2026-23278)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnet: vxlan: fix nd_tbl NULL dereference when IPv6 is disabled\n\nWhen booting with the \u0026apos;ipv6.disable=1\u0026apos; parameter, the nd_tbl is never\ninitialized because inet6_init() exits before ndisc_init() is called\nwhich initializes it. If an IPv6 packet is injected into the interface,\nroute_shortcircuit() is called and a NULL pointer dereference happens on\nneigh_lookup().\n\n BUG: kernel NULL pointer dereference, address: 0000000000000380\n Oops: Oops: 0000 [#1] SMP NOPTI\n [...]\n RIP: 0010:neigh_lookup+0x20/0x270\n [...]\n Call Trace:\n  \u0026lt;TASK\u0026gt;\n  vxlan_xmit+0x638/0x1ef0 [vxlan]\n  dev_hard_start_xmit+0x9e/0x2e0\n  __dev_queue_xmit+0xbee/0x14e0\n  packet_sendmsg+0x116f/0x1930\n  __sys_sendto+0x1f5/0x200\n  __x64_sys_sendto+0x24/0x30\n  do_syscall_64+0x12f/0x1590\n  entry_SYSCALL_64_after_hwframe+0x76/0x7e\n\nFix this by adding an early check on route_shortcircuit() when protocol\nis ETH_P_IPV6. Note that ipv6_mod_enabled() cannot be used here because\nVXLAN can be built-in even when IPv6 is built as a module.(CVE-2026-23293)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnet: ipv6: fix panic when IPv4 route references loopback IPv6 nexthop\n\nWhen a standalone IPv6 nexthop object is created with a loopback device\n(e.g., \u0026quot;ip -6 nexthop add id 100 dev lo\u0026quot;), fib6_nh_init() misclassifies\nit as a reject route. This is because nexthop objects have no destination\nprefix (fc_dst=::), causing fib6_is_reject() to match any loopback\nnexthop. The reject path skips fib_nh_common_init(), leaving\nnhc_pcpu_rth_output unallocated. If an IPv4 route later references this\nnexthop, __mkroute_output() dereferences NULL nhc_pcpu_rth_output and\npanics.\n\nSimplify the check in fib6_nh_init() to only match explicit reject\nroutes (RTF_REJECT) instead of using fib6_is_reject(). The loopback\npromotion heuristic in fib6_is_reject() is handled separately by\nip6_route_info_create_nh(). After this change, the three cases behave\nas follows:\n\n1. Explicit reject route (\u0026quot;ip -6 route add unreachable 2001:db8::/64\u0026quot;):\n   RTF_REJECT is set, enters reject path, skips fib_nh_common_init().\n   No behavior change.\n\n2. Implicit loopback reject route (\u0026quot;ip -6 route add 2001:db8::/32 dev lo\u0026quot;):\n   RTF_REJECT is not set, takes normal path, fib_nh_common_init() is\n   called. ip6_route_info_create_nh() still promotes it to reject\n   afterward. nhc_pcpu_rth_output is allocated but unused, which is\n   harmless.\n\n3. Standalone nexthop object (\u0026quot;ip -6 nexthop add id 100 dev lo\u0026quot;):\n   RTF_REJECT is not set, takes normal path, fib_nh_common_init() is\n   called. nhc_pcpu_rth_output is properly allocated, fixing the crash\n   when IPv4 routes reference this nexthop.(CVE-2026-23300)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnet: annotate data-races around sk-\u0026gt;sk_{data_ready,write_space}\n\nskmsg (and probably other layers) are changing these pointers\nwhile other cpus might read them concurrently.\n\nAdd corresponding READ_ONCE()/WRITE_ONCE() annotations\nfor UDP, TCP and AF_UNIX.(CVE-2026-23302)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nsmb: client: Don\u0026apos;t log plaintext credentials in cifs_set_cifscreds\n\nWhen debug logging is enabled, cifs_set_cifscreds() logs the key\npayload and exposes the plaintext username and password. Remove the\ndebug log to avoid exposing credentials.(CVE-2026-23303)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nipv6: fix NULL pointer deref in ip6_rt_get_dev_rcu()\n\nl3mdev_master_dev_rcu() can return NULL when the slave device is being\nun-slaved from a VRF. All other callers deal with this, but we lost\nthe fallback to loopback in ip6_rt_pcpu_alloc() -\u0026gt; ip6_rt_get_dev_rcu()\nwith commit 4832c30d5458 (\u0026quot;net: ipv6: put host and anycast routes on\ndevice with address\u0026quot;).\n\n  KASAN: null-ptr-deref in range [0x0000000000000108-0x000000000000010f]\n  RIP: 0010:ip6_rt_pcpu_alloc (net/ipv6/route.c:1418)\n  Call Trace:\n   ip6_pol_route (net/ipv6/route.c:2318)\n   fib6_rule_lookup (net/ipv6/fib6_rules.c:115)\n   ip6_route_output_flags (net/ipv6/route.c:2607)\n   vrf_process_v6_outbound (drivers/net/vrf.c:437)\n\nI was tempted to rework the un-slaving code to clear the flag first\nand insert synchronize_rcu() before we remove the upper. But looks like\nthe explicit fallback to loopback_dev is an established pattern.\nAnd I guess avoiding the synchronize_rcu() is nice, too.(CVE-2026-23304)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nbpf/bonding: reject vlan+srcmac xmit_hash_policy change when XDP is loaded\n\nbond_option_mode_set() already rejects mode changes that would make a\nloaded XDP program incompatible via bond_xdp_check().  However,\nbond_option_xmit_hash_policy_set() has no such guard.\n\nFor 802.3ad and balance-xor modes, bond_xdp_check() returns false when\nxmit_hash_policy is vlan+srcmac, because the 802.1q payload is usually\nabsent due to hardware offload.  This means a user can:\n\n1. Attach a native XDP program to a bond in 802.3ad/balance-xor mode\n   with a compatible xmit_hash_policy (e.g. layer2+3).\n2. Change xmit_hash_policy to vlan+srcmac while XDP remains loaded.\n\nThis leaves bond-\u0026gt;xdp_prog set but bond_xdp_check() now returning false\nfor the same device.  When the bond is later destroyed, dev_xdp_uninstall()\ncalls bond_xdp_set(dev, NULL, NULL) to remove the program, which hits\nthe bond_xdp_check() guard and returns -EOPNOTSUPP, triggering:\n\nWARN_ON(dev_xdp_install(dev, mode, bpf_op, NULL, 0, NULL))\n\nFix this by rejecting xmit_hash_policy changes to vlan+srcmac when an\nXDP program is loaded on a bond in 802.3ad or balance-xor mode.\n\ncommit 39a0876d595b (\u0026quot;net, bonding: Disallow vlan+srcmac with XDP\u0026quot;)\nintroduced bond_xdp_check() which returns false for 802.3ad/balance-xor\nmodes when xmit_hash_policy is vlan+srcmac.  The check was wired into\nbond_xdp_set() to reject XDP attachment with an incompatible policy, but\nthe symmetric path -- preventing xmit_hash_policy from being changed to an\nincompatible value after XDP is already loaded -- was left unguarded in\nbond_option_xmit_hash_policy_set().\n\nNote:\ncommit 094ee6017ea0 (\u0026quot;bonding: check xdp prog when set bond mode\u0026quot;)\nlater added a similar guard to bond_option_mode_set(), but\nbond_option_xmit_hash_policy_set() remained unprotected.(CVE-2026-23310)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nmptcp: pm: in-kernel: always mark signal+subflow endp as used\n\nSyzkaller managed to find a combination of actions that was generating\nthis warning:\n\n  msk-\u0026gt;pm.local_addr_used == 0\n  WARNING: net/mptcp/pm_kernel.c:1071 at __mark_subflow_endp_available net/mptcp/pm_kernel.c:1071 [inline], CPU#1: syz.2.17/961\n  WARNING: net/mptcp/pm_kernel.c:1071 at mptcp_nl_remove_subflow_and_signal_addr net/mptcp/pm_kernel.c:1103 [inline], CPU#1: syz.2.17/961\n  WARNING: net/mptcp/pm_kernel.c:1071 at mptcp_pm_nl_del_addr_doit+0x81d/0x8f0 net/mptcp/pm_kernel.c:1210, CPU#1: syz.2.17/961\n  Modules linked in:\n  CPU: 1 UID: 0 PID: 961 Comm: syz.2.17 Not tainted 6.19.0-08368-gfafda3b4b06b #22 PREEMPT(full)\n  Hardware name: QEMU Ubuntu 25.10 PC v2 (i440FX + PIIX, + 10.1 machine, 1996), BIOS 1.17.0-debian-1.17.0-1build1 04/01/2014\n  RIP: 0010:__mark_subflow_endp_available net/mptcp/pm_kernel.c:1071 [inline]\n  RIP: 0010:mptcp_nl_remove_subflow_and_signal_addr net/mptcp/pm_kernel.c:1103 [inline]\n  RIP: 0010:mptcp_pm_nl_del_addr_doit+0x81d/0x8f0 net/mptcp/pm_kernel.c:1210\n  Code: 89 c5 e8 46 30 6f fe e9 21 fd ff ff 49 83 ed 80 e8 38 30 6f fe 4c 89 ef be 03 00 00 00 e8 db 49 df fe eb ac e8 24 30 6f fe 90 \u0026lt;0f\u0026gt; 0b 90 e9 1d ff ff ff e8 16 30 6f fe eb 05 e8 0f 30 6f fe e8 9a\n  RSP: 0018:ffffc90001663880 EFLAGS: 00010293\n  RAX: ffffffff82de1a6c RBX: 0000000000000000 RCX: ffff88800722b500\n  RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000000000000\n  RBP: ffff8880158b22d0 R08: 0000000000010425 R09: ffffffffffffffff\n  R10: ffffffff82de18ba R11: 0000000000000000 R12: ffff88800641a640\n  R13: ffff8880158b1880 R14: ffff88801ec3c900 R15: ffff88800641a650\n  FS:  00005555722c3500(0000) GS:ffff8880f909d000(0000) knlGS:0000000000000000\n  CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033\n  CR2: 00007f66346e0f60 CR3: 000000001607c000 CR4: 0000000000350ef0\n  Call Trace:\n   \u0026lt;TASK\u0026gt;\n   genl_family_rcv_msg_doit+0x117/0x180 net/netlink/genetlink.c:1115\n   genl_family_rcv_msg net/netlink/genetlink.c:1195 [inline]\n   genl_rcv_msg+0x3a8/0x3f0 net/netlink/genetlink.c:1210\n   netlink_rcv_skb+0x16d/0x240 net/netlink/af_netlink.c:2550\n   genl_rcv+0x28/0x40 net/netlink/genetlink.c:1219\n   netlink_unicast_kernel net/netlink/af_netlink.c:1318 [inline]\n   netlink_unicast+0x3e9/0x4c0 net/netlink/af_netlink.c:1344\n   netlink_sendmsg+0x4aa/0x5b0 net/netlink/af_netlink.c:1894\n   sock_sendmsg_nosec net/socket.c:727 [inline]\n   __sock_sendmsg+0xc9/0xf0 net/socket.c:742\n   ____sys_sendmsg+0x272/0x3b0 net/socket.c:2592\n   ___sys_sendmsg+0x2de/0x320 net/socket.c:2646\n   __sys_sendmsg net/socket.c:2678 [inline]\n   __do_sys_sendmsg net/socket.c:2683 [inline]\n   __se_sys_sendmsg net/socket.c:2681 [inline]\n   __x64_sys_sendmsg+0x110/0x1a0 net/socket.c:2681\n   do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline]\n   do_syscall_64+0x143/0x440 arch/x86/entry/syscall_64.c:94\n   entry_SYSCALL_64_after_hwframe+0x77/0x7f\n  RIP: 0033:0x7f66346f826d\n  Code: ff c3 66 2e 0f 1f 84 00 00 00 00 00 90 f3 0f 1e fa 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 \u0026lt;48\u0026gt; 3d 01 f0 ff ff 73 01 c3 48 c7 c1 e8 ff ff ff f7 d8 64 89 01 48\n  RSP: 002b:00007ffc83d8bdc8 EFLAGS: 00000246 ORIG_RAX: 000000000000002e\n  RAX: ffffffffffffffda RBX: 00007f6634985fa0 RCX: 00007f66346f826d\n  RDX: 00000000040000b0 RSI: 0000200000000740 RDI: 0000000000000007\n  RBP: 0000000000000000 R08: 0000000000000000 R09: 0000000000000000\n  R10: 0000000000000000 R11: 0000000000000246 R12: 00007f6634985fa8\n  R13: 00007f6634985fac R14: 0000000000000000 R15: 0000000000001770\n   \u0026lt;/TASK\u0026gt;\n\nThe actions that caused that seem to be:\n\n - Set the MPTCP subflows limit to 0\n - Create an MPTCP endpoint with both the \u0026apos;signal\u0026apos; and \u0026apos;subflow\u0026apos; flags\n - Create a new MPTCP connection from a different address: an ADD_ADDR\n   linked to the MPTCP endpoint will be sent (\u0026apos;signal\u0026apos; flag), but no\n   subflows is initiated (\u0026apos;subflow\u0026apos; flag)\n - Remove the MPTCP endpoint\n\n---truncated---(CVE-2026-23321)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nxdp: produce a warning when calculated tailroom is negative\n\nMany ethernet drivers report xdp Rx queue frag size as being the same as\nDMA write size. However, the only user of this field, namely\nbpf_xdp_frags_increase_tail(), clearly expects a truesize.\n\nSuch difference leads to unspecific memory corruption issues under certain\ncircumstances, e.g. in ixgbevf maximum DMA write size is 3 KB, so when\nrunning xskxceiver\u0026apos;s XDP_ADJUST_TAIL_GROW_MULTI_BUFF, 6K packet fully uses\nall DMA-writable space in 2 buffers. This would be fine, if only\nrxq-\u0026gt;frag_size was properly set to 4K, but value of 3K results in a\nnegative tailroom, because there is a non-zero page offset.\n\nWe are supposed to return -EINVAL and be done with it in such case, but due\nto tailroom being stored as an unsigned int, it is reported to be somewhere\nnear UINT_MAX, resulting in a tail being grown, even if the requested\noffset is too much (it is around 2K in the abovementioned test). This later\nleads to all kinds of unspecific calltraces.\n\n[ 7340.337579] xskxceiver[1440]: segfault at 1da718 ip 00007f4161aeac9d sp 00007f41615a6a00 error 6\n[ 7340.338040] xskxceiver[1441]: segfault at 7f410000000b ip 00000000004042b5 sp 00007f415bffecf0 error 4\n[ 7340.338179]  in libc.so.6[61c9d,7f4161aaf000+160000]\n[ 7340.339230]  in xskxceiver[42b5,400000+69000]\n[ 7340.340300]  likely on CPU 6 (core 0, socket 6)\n[ 7340.340302] Code: ff ff 01 e9 f4 fe ff ff 0f 1f 44 00 00 4c 39 f0 74 73 31 c0 ba 01 00 00 00 f0 0f b1 17 0f 85 ba 00 00 00 49 8b 87 88 00 00 00 \u0026lt;4c\u0026gt; 89 70 08 eb cc 0f 1f 44 00 00 48 8d bd f0 fe ff ff 89 85 ec fe\n[ 7340.340888]  likely on CPU 3 (core 0, socket 3)\n[ 7340.345088] Code: 00 00 00 ba 00 00 00 00 be 00 00 00 00 89 c7 e8 31 ca ff ff 89 45 ec 8b 45 ec 85 c0 78 07 b8 00 00 00 00 eb 46 e8 0b c8 ff ff \u0026lt;8b\u0026gt; 00 83 f8 69 74 24 e8 ff c7 ff ff 8b 00 83 f8 0b 74 18 e8 f3 c7\n[ 7340.404334] Oops: general protection fault, probably for non-canonical address 0x6d255010bdffc: 0000 [#1] SMP NOPTI\n[ 7340.405972] CPU: 7 UID: 0 PID: 1439 Comm: xskxceiver Not tainted 6.19.0-rc1+ #21 PREEMPT(lazy)\n[ 7340.408006] Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.17.0-5.fc42 04/01/2014\n[ 7340.409716] RIP: 0010:lookup_swap_cgroup_id+0x44/0x80\n[ 7340.410455] Code: 83 f8 1c 73 39 48 ba ff ff ff ff ff ff ff 03 48 8b 04 c5 20 55 fa bd 48 21 d1 48 89 ca 83 e1 01 48 d1 ea c1 e1 04 48 8d 04 90 \u0026lt;8b\u0026gt; 00 48 83 c4 10 d3 e8 c3 cc cc cc cc 31 c0 e9 98 b7 dd 00 48 89\n[ 7340.412787] RSP: 0018:ffffcc5c04f7f6d0 EFLAGS: 00010202\n[ 7340.413494] RAX: 0006d255010bdffc RBX: ffff891f477895a8 RCX: 0000000000000010\n[ 7340.414431] RDX: 0001c17e3fffffff RSI: 00fa070000000000 RDI: 000382fc7fffffff\n[ 7340.415354] RBP: 00fa070000000000 R08: ffffcc5c04f7f8f8 R09: ffffcc5c04f7f7d0\n[ 7340.416283] R10: ffff891f4c1a7000 R11: ffffcc5c04f7f9c8 R12: ffffcc5c04f7f7d0\n[ 7340.417218] R13: 03ffffffffffffff R14: 00fa06fffffffe00 R15: ffff891f47789500\n[ 7340.418229] FS:  0000000000000000(0000) GS:ffff891ffdfaa000(0000) knlGS:0000000000000000\n[ 7340.419489] CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033\n[ 7340.420286] CR2: 00007f415bfffd58 CR3: 0000000103f03002 CR4: 0000000000772ef0\n[ 7340.421237] PKRU: 55555554\n[ 7340.421623] Call Trace:\n[ 7340.421987]  \u0026lt;TASK\u0026gt;\n[ 7340.422309]  ? softleaf_from_pte+0x77/0xa0\n[ 7340.422855]  swap_pte_batch+0xa7/0x290\n[ 7340.423363]  zap_nonpresent_ptes.constprop.0.isra.0+0xd1/0x270\n[ 7340.424102]  zap_pte_range+0x281/0x580\n[ 7340.424607]  zap_pmd_range.isra.0+0xc9/0x240\n[ 7340.425177]  unmap_page_range+0x24d/0x420\n[ 7340.425714]  unmap_vmas+0xa1/0x180\n[ 7340.426185]  exit_mmap+0xe1/0x3b0\n[ 7340.426644]  __mmput+0x41/0x150\n[ 7340.427098]  exit_mm+0xb1/0x110\n[ 7340.427539]  do_exit+0x1b2/0x460\n[ 7340.427992]  do_group_exit+0x2d/0xc0\n[ 7340.428477]  get_signal+0x79d/0x7e0\n[ 7340.428957]  arch_do_signal_or_restart+0x34/0x100\n[ 7340.429571]  exit_to_user_mode_loop+0x8e/0x4c0\n[ 7340.430159]  do_syscall_64+0x188/\n---truncated---(CVE-2026-23343)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnetfilter: nft_set_pipapo: split gc into unlink and reclaim phase\n\nYiming Qian reports Use-after-free in the pipapo set type:\n  Under a large number of expired elements, commit-time GC can run for a very\n  long time in a non-preemptible context, triggering soft lockup warnings and\n  RCU stall reports (local denial of service).\n\nWe must split GC in an unlink and a reclaim phase.\n\nWe cannot queue elements for freeing until pointers have been swapped.\nExpired elements are still exposed to both the packet path and userspace\ndumpers via the live copy of the data structure.\n\ncall_rcu() does not protect us: dump operations or element lookups starting\nafter call_rcu has fired can still observe the free\u0026apos;d element, unless the\ncommit phase has made enough progress to swap the clone and live pointers\nbefore any new reader has picked up the old version.\n\nThis a similar approach as done recently for the rbtree backend in commit\n35f83a75529a (\u0026quot;netfilter: nft_set_rbtree: don\u0026apos;t gc elements on insert\u0026quot;).(CVE-2026-23351)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ncan: bcm: fix locking for bcm_op runtime updates\n\nCommit c2aba69d0c36 (\u0026quot;can: bcm: add locking for bcm_op runtime updates\u0026quot;)\nadded a locking for some variables that can be modified at runtime when\nupdating the sending bcm_op with a new TX_SETUP command in bcm_tx_setup().\n\nUsually the RX_SETUP only handles and filters incoming traffic with one\nexception: When the RX_RTR_FRAME flag is set a predefined CAN frame is\nsent when a specific RTR frame is received. Therefore the rx bcm_op uses\nbcm_can_tx() which uses the bcm_tx_lock that was only initialized in\nbcm_tx_setup(). Add the missing spin_lock_init() when allocating the\nbcm_op in bcm_rx_setup() to handle the RTR case properly.(CVE-2026-23362)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnet: usb: kalmia: validate USB endpoints\n\nThe kalmia driver should validate that the device it is probing has the\nproper number and types of USB endpoints it is expecting before it binds\nto it.  If a malicious device were to not have the same urbs the driver\nwill crash later on when it blindly accesses these endpoints.(CVE-2026-23365)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnet: phy: register phy led_triggers during probe to avoid AB-BA deadlock\n\nThere is an AB-BA deadlock when both LEDS_TRIGGER_NETDEV and\nLED_TRIGGER_PHY are enabled:\n\n[ 1362.049207] [\u0026lt;8054e4b8\u0026gt;] led_trigger_register+0x5c/0x1fc             \u0026lt;-- Trying to get lock \u0026quot;triggers_list_lock\u0026quot; via down_write(\u0026amp;triggers_list_lock);\n[ 1362.054536] [\u0026lt;80662830\u0026gt;] phy_led_triggers_register+0xd0/0x234\n[ 1362.060329] [\u0026lt;8065e200\u0026gt;] phy_attach_direct+0x33c/0x40c\n[ 1362.065489] [\u0026lt;80651fc4\u0026gt;] phylink_fwnode_phy_connect+0x15c/0x23c\n[ 1362.071480] [\u0026lt;8066ee18\u0026gt;] mtk_open+0x7c/0xba0\n[ 1362.075849] [\u0026lt;806d714c\u0026gt;] __dev_open+0x280/0x2b0\n[ 1362.080384] [\u0026lt;806d7668\u0026gt;] __dev_change_flags+0x244/0x24c\n[ 1362.085598] [\u0026lt;806d7698\u0026gt;] dev_change_flags+0x28/0x78\n[ 1362.090528] [\u0026lt;807150e4\u0026gt;] dev_ioctl+0x4c0/0x654                       \u0026lt;-- Hold lock \u0026quot;rtnl_mutex\u0026quot; by calling rtnl_lock();\n[ 1362.094985] [\u0026lt;80694360\u0026gt;] sock_ioctl+0x2f4/0x4e0\n[ 1362.099567] [\u0026lt;802e9c4c\u0026gt;] sys_ioctl+0x32c/0xd8c\n[ 1362.104022] [\u0026lt;80014504\u0026gt;] syscall_common+0x34/0x58\n\nHere LED_TRIGGER_PHY is registering LED triggers during phy_attach\nwhile holding RTNL and then taking triggers_list_lock.\n\n[ 1362.191101] [\u0026lt;806c2640\u0026gt;] register_netdevice_notifier+0x60/0x168      \u0026lt;-- Trying to get lock \u0026quot;rtnl_mutex\u0026quot; via rtnl_lock();\n[ 1362.197073] [\u0026lt;805504ac\u0026gt;] netdev_trig_activate+0x194/0x1e4\n[ 1362.202490] [\u0026lt;8054e28c\u0026gt;] led_trigger_set+0x1d4/0x360                 \u0026lt;-- Hold lock \u0026quot;triggers_list_lock\u0026quot; by down_read(\u0026amp;triggers_list_lock);\n[ 1362.207511] [\u0026lt;8054eb38\u0026gt;] led_trigger_write+0xd8/0x14c\n[ 1362.212566] [\u0026lt;80381d98\u0026gt;] sysfs_kf_bin_write+0x80/0xbc\n[ 1362.217688] [\u0026lt;8037fcd8\u0026gt;] kernfs_fop_write_iter+0x17c/0x28c\n[ 1362.223174] [\u0026lt;802cbd70\u0026gt;] vfs_write+0x21c/0x3c4\n[ 1362.227712] [\u0026lt;802cc0c4\u0026gt;] ksys_write+0x78/0x12c\n[ 1362.232164] [\u0026lt;80014504\u0026gt;] syscall_common+0x34/0x58\n\nHere LEDS_TRIGGER_NETDEV is being enabled on an LED. It first takes\ntriggers_list_lock and then RTNL. A classical AB-BA deadlock.\n\nphy_led_triggers_registers() does not require the RTNL, it does not\nmake any calls into the network stack which require protection. There\nis also no requirement the PHY has been attached to a MAC, the\ntriggers only make use of phydev state. This allows the call to\nphy_led_triggers_registers() to be placed elsewhere. PHY probe() and\nrelease() don\u0026apos;t hold RTNL, so solving the AB-BA deadlock.(CVE-2026-23368)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nsched/deadline: Fix missing ENQUEUE_REPLENISH during PI de-boosting\n\nRunning stress-ng --schedpolicy 0 on an RT kernel on a big machine\nmight lead to the following WARNINGs (edited).\n\n sched: DL de-boosted task PID 22725: REPLENISH flag missing\n\n WARNING: CPU: 93 PID: 0 at kernel/sched/deadline.c:239 dequeue_task_dl+0x15c/0x1f8\n ... (running_bw underflow)\n Call trace:\n  dequeue_task_dl+0x15c/0x1f8 (P)\n  dequeue_task+0x80/0x168\n  deactivate_task+0x24/0x50\n  push_dl_task+0x264/0x2e0\n  dl_task_timer+0x1b0/0x228\n  __hrtimer_run_queues+0x188/0x378\n  hrtimer_interrupt+0xfc/0x260\n  ...\n\nThe problem is that when a SCHED_DEADLINE task (lock holder) is\nchanged to a lower priority class via sched_setscheduler(), it may\nfail to properly inherit the parameters of potential DEADLINE donors\nif it didn\u0026apos;t already inherit them in the past (shorter deadline than\ndonor\u0026apos;s at that time). This might lead to bandwidth accounting\ncorruption, as enqueue_task_dl() won\u0026apos;t recognize the lock holder as\nboosted.\n\nThe scenario occurs when:\n1. A DEADLINE task (donor) blocks on a PI mutex held by another\n   DEADLINE task (holder), but the holder doesn\u0026apos;t inherit parameters\n   (e.g., it already has a shorter deadline)\n2. sched_setscheduler() changes the holder from DEADLINE to a lower\n   class while still holding the mutex\n3. The holder should now inherit DEADLINE parameters from the donor\n   and be enqueued with ENQUEUE_REPLENISH, but this doesn\u0026apos;t happen\n\nFix the issue by introducing __setscheduler_dl_pi(), which detects when\na DEADLINE (proper or boosted) task gets setscheduled to a lower\npriority class. In case, the function makes the task inherit DEADLINE\nparameters of the donoer (pi_se) and sets ENQUEUE_REPLENISH flag to\nensure proper bandwidth accounting during the next enqueue operation.(CVE-2026-23371)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nmm: thp: deny THP for files on anonymous inodes\n\nfile_thp_enabled() incorrectly allows THP for files on anonymous inodes\n(e.g. guest_memfd and secretmem). These files are created via\nalloc_file_pseudo(), which does not call get_write_access() and leaves\ninode-\u0026gt;i_writecount at 0. Combined with S_ISREG(inode-\u0026gt;i_mode) being\ntrue, they appear as read-only regular files when\nCONFIG_READ_ONLY_THP_FOR_FS is enabled, making them eligible for THP\ncollapse.\n\nAnonymous inodes can never pass the inode_is_open_for_write() check\nsince their i_writecount is never incremented through the normal VFS\nopen path. The right thing to do is to exclude them from THP eligibility\naltogether, since CONFIG_READ_ONLY_THP_FOR_FS was designed for real\nfilesystem files (e.g. shared libraries), not for pseudo-filesystem\ninodes.\n\nFor guest_memfd, this allows khugepaged and MADV_COLLAPSE to create\nlarge folios in the page cache via the collapse path, but the\nguest_memfd fault handler does not support large folios. This triggers\nWARN_ON_ONCE(folio_test_large(folio)) in kvm_gmem_fault_user_mapping().\n\nFor secretmem, collapse_file() tries to copy page contents through the\ndirect map, but secretmem pages are removed from the direct map. This\ncan result in a kernel crash:\n\n    BUG: unable to handle page fault for address: ffff88810284d000\n    RIP: 0010:memcpy_orig+0x16/0x130\n    Call Trace:\n     collapse_file\n     hpage_collapse_scan_file\n     madvise_collapse\n\nSecretmem is not affected by the crash on upstream as the memory failure\nrecovery handles the failed copy gracefully, but it still triggers\nconfusing false memory failure reports:\n\n    Memory failure: 0x106d96f: recovery action for clean unevictable\n    LRU page: Recovered\n\nCheck IS_ANON_FILE(inode) in file_thp_enabled() to deny THP for all\nanonymous inode files.(CVE-2026-23375)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnet: bridge: fix nd_tbl NULL dereference when IPv6 is disabled\n\nWhen booting with the \u0026apos;ipv6.disable=1\u0026apos; parameter, the nd_tbl is never\ninitialized because inet6_init() exits before ndisc_init() is called\nwhich initializes it. Then, if neigh_suppress is enabled and an ICMPv6\nNeighbor Discovery packet reaches the bridge, br_do_suppress_nd() will\ndereference ipv6_stub-\u0026gt;nd_tbl which is NULL, passing it to\nneigh_lookup(). This causes a kernel NULL pointer dereference.\n\n BUG: kernel NULL pointer dereference, address: 0000000000000268\n Oops: 0000 [#1] PREEMPT SMP NOPTI\n [...]\n RIP: 0010:neigh_lookup+0x16/0xe0\n [...]\n Call Trace:\n  \u0026lt;IRQ\u0026gt;\n  ? neigh_lookup+0x16/0xe0\n  br_do_suppress_nd+0x160/0x290 [bridge]\n  br_handle_frame_finish+0x500/0x620 [bridge]\n  br_handle_frame+0x353/0x440 [bridge]\n  __netif_receive_skb_core.constprop.0+0x298/0x1110\n  __netif_receive_skb_one_core+0x3d/0xa0\n  process_backlog+0xa0/0x140\n  __napi_poll+0x2c/0x170\n  net_rx_action+0x2c4/0x3a0\n  handle_softirqs+0xd0/0x270\n  do_softirq+0x3f/0x60\n\nFix this by replacing IS_ENABLED(IPV6) call with ipv6_mod_enabled() in\nthe callers. This is in essence disabling NS/NA suppression when IPv6 is\ndisabled.(CVE-2026-23381)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnetfilter: xt_CT: drop pending enqueued packets on template removal\n\nTemplates refer to objects that can go away while packets are sitting in\nnfqueue refer to:\n\n- helper, this can be an issue on module removal.\n- timeout policy, nfnetlink_cttimeout might remove it.\n\nThe use of templates with zone and event cache filter are safe, since\nthis just copies values.\n\nFlush these enqueued packets in case the template rule gets removed.(CVE-2026-23391)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnetfilter: nf_tables: release flowtable after rcu grace period on error\n\nCall synchronize_rcu() after unregistering the hooks from error path,\nsince a hook that already refers to this flowtable can be already\nregistered, exposing this flowtable to packet path and nfnetlink_hook\ncontrol plane.\n\nThis error path is rare, it should only happen by reaching the maximum\nnumber hooks or by failing to set up to hardware offload, just call\nsynchronize_rcu().\n\nThere is a check for already used device hooks by different flowtable\nthat could result in EEXIST at this late stage. The hook parser can be\nupdated to perform this check earlier to this error path really becomes\nrarely exercised.\n\nUncovered by KASAN reported as use-after-free from nfnetlink_hook path\nwhen dumping hooks.(CVE-2026-23392)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nbridge: cfm: Fix race condition in peer_mep deletion\n\nWhen a peer MEP is being deleted, cancel_delayed_work_sync() is called\non ccm_rx_dwork before freeing. However, br_cfm_frame_rx() runs in\nsoftirq context under rcu_read_lock (without RTNL) and can re-schedule\nccm_rx_dwork via ccm_rx_timer_start() between cancel_delayed_work_sync()\nreturning and kfree_rcu() being called.\n\nThe following is a simple race scenario:\n\n           cpu0                                     cpu1\n\nmep_delete_implementation()\n  cancel_delayed_work_sync(ccm_rx_dwork);\n                                           br_cfm_frame_rx()\n                                             // peer_mep still in hlist\n                                             if (peer_mep-\u0026gt;ccm_defect)\n                                               ccm_rx_timer_start()\n                                                 queue_delayed_work(ccm_rx_dwork)\n  hlist_del_rcu(\u0026amp;peer_mep-\u0026gt;head);\n  kfree_rcu(peer_mep, rcu);\n                                           ccm_rx_work_expired()\n                                             // on freed peer_mep\n\nTo prevent this, cancel_delayed_work_sync() is replaced with\ndisable_delayed_work_sync() in both peer MEP deletion paths, so\nthat subsequent queue_delayed_work() calls from br_cfm_frame_rx()\nare silently rejected.\n\nThe cc_peer_disable() helper retains cancel_delayed_work_sync()\nbecause it is also used for the CC enable/disable toggle path where\nthe work must remain re-schedulable.(CVE-2026-23393)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\naf_unix: Give up GC if MSG_PEEK intervened.\n\nIgor Ushakov reported that GC purged the receive queue of\nan alive socket due to a race with MSG_PEEK with a nice repro.\n\nThis is the exact same issue previously fixed by commit\ncbcf01128d0a (\u0026quot;af_unix: fix garbage collect vs MSG_PEEK\u0026quot;).\n\nAfter GC was replaced with the current algorithm, the cited\ncommit removed the locking dance in unix_peek_fds() and\nreintroduced the same issue.\n\nThe problem is that MSG_PEEK bumps a file refcount without\ninteracting with GC.\n\nConsider an SCC containing sk-A and sk-B, where sk-A is\nclose()d but can be recv()ed via sk-B.\n\nThe bad thing happens if sk-A is recv()ed with MSG_PEEK from\nsk-B and sk-B is close()d while GC is checking unix_vertex_dead()\nfor sk-A and sk-B.\n\n  GC thread                    User thread\n  ---------                    -----------\n  unix_vertex_dead(sk-A)\n  -\u0026gt; true   \u0026lt;------.\n                    \\\n                     `------   recv(sk-B, MSG_PEEK)\n              invalidate !!    -\u0026gt; sk-A\u0026apos;s file refcount : 1 -\u0026gt; 2\n\n                               close(sk-B)\n                               -\u0026gt; sk-B\u0026apos;s file refcount : 2 -\u0026gt; 1\n  unix_vertex_dead(sk-B)\n  -\u0026gt; true\n\nInitially, sk-A\u0026apos;s file refcount is 1 by the inflight fd in sk-B\nrecvq.  GC thinks sk-A is dead because the file refcount is the\nsame as the number of its inflight fds.\n\nHowever, sk-A\u0026apos;s file refcount is bumped silently by MSG_PEEK,\nwhich invalidates the previous evaluation.\n\nAt this moment, sk-B\u0026apos;s file refcount is 2; one by the open fd,\nand one by the inflight fd in sk-A.  The subsequent close()\nreleases one refcount by the former.\n\nFinally, GC incorrectly concludes that both sk-A and sk-B are dead.\n\nOne option is to restore the locking dance in unix_peek_fds(),\nbut we can resolve this more elegantly thanks to the new algorithm.\n\nThe point is that the issue does not occur without the subsequent\nclose() and we actually do not need to synchronise MSG_PEEK with\nthe dead SCC detection.\n\nWhen the issue occurs, close() and GC touch the same file refcount.\nIf GC sees the refcount being decremented by close(), it can just\ngive up garbage-collecting the SCC.\n\nTherefore, we only need to signal the race during MSG_PEEK with\na proper memory barrier to make it visible to the GC.\n\nLet\u0026apos;s use seqcount_t to notify GC when MSG_PEEK occurs and let\nit defer the SCC to the next run.\n\nThis way no locking is needed on the MSG_PEEK side, and we can\navoid imposing a penalty on every MSG_PEEK unnecessarily.\n\nNote that we can retry within unix_scc_dead() if MSG_PEEK is\ndetected, but we do not do so to avoid hung task splat from\nabusive MSG_PEEK calls.(CVE-2026-23394)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nBluetooth: L2CAP: Fix accepting multiple L2CAP_ECRED_CONN_REQ\n\nCurrently the code attempts to accept requests regardless of the\ncommand identifier which may cause multiple requests to be marked\nas pending (FLAG_DEFER_SETUP) which can cause more than\nL2CAP_ECRED_MAX_CID(5) to be allocated in l2cap_ecred_rsp_defer\ncausing an overflow.\n\nThe spec is quite clear that the same identifier shall not be used on\nsubsequent requests:\n\n\u0026apos;Within each signaling channel a different Identifier shall be used\nfor each successive request or indication.\u0026apos;\nhttps://www.bluetooth.com/wp-content/uploads/Files/Specification/HTML/Core-62/out/en/host/logical-link-control-and-adaptation-protocol-specification.html#UUID-32a25a06-4aa4-c6c7-77c5-dcfe3682355d\n\nSo this attempts to check if there are any channels pending with the\nsame identifier and rejects if any are found.(CVE-2026-23395)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnfnetlink_osf: validate individual option lengths in fingerprints\n\nnfnl_osf_add_callback() validates opt_num bounds and string\nNUL-termination but does not check individual option length fields.\nA zero-length option causes nf_osf_match_one() to enter the option\nmatching loop even when foptsize sums to zero, which matches packets\nwith no TCP options where ctx-\u0026gt;optp is NULL:\n\n Oops: general protection fault\n KASAN: null-ptr-deref in range [0x0000000000000000-0x0000000000000007]\n RIP: 0010:nf_osf_match_one (net/netfilter/nfnetlink_osf.c:98)\n Call Trace:\n  nf_osf_match (net/netfilter/nfnetlink_osf.c:227)\n  xt_osf_match_packet (net/netfilter/xt_osf.c:32)\n  ipt_do_table (net/ipv4/netfilter/ip_tables.c:293)\n  nf_hook_slow (net/netfilter/core.c:623)\n  ip_local_deliver (net/ipv4/ip_input.c:262)\n  ip_rcv (net/ipv4/ip_input.c:573)\n\nAdditionally, an MSS option (kind=2) with length \u0026lt; 4 causes\nout-of-bounds reads when nf_osf_match_one() unconditionally accesses\noptp[2] and optp[3] for MSS value extraction.  While RFC 9293\nsection 3.2 specifies that the MSS option is always exactly 4\nbytes (Kind=2, Length=4), the check uses \u0026quot;\u0026lt; 4\u0026quot; rather than\n\u0026quot;!= 4\u0026quot; because lengths greater than 4 do not cause memory\nsafety issues -- the buffer is guaranteed to be at least\nfoptsize bytes by the ctx-\u0026gt;optsize == foptsize check.\n\nReject fingerprints where any option has zero length, or where an MSS\noption has length less than 4, at add time rather than trusting these\nvalues in the packet matching hot path.(CVE-2026-23397)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnf_tables: nft_dynset: fix possible stateful expression memleak in error path\n\nIf cloning the second stateful expression in the element via GFP_ATOMIC\nfails, then the first stateful expression remains in place without being\nreleased.\n\n   unreferenced object (percpu) 0x607b97e9cab8 (size 16):\n     comm \u0026quot;softirq\u0026quot;, pid 0, jiffies 4294931867\n     hex dump (first 16 bytes on cpu 3):\n       00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00\n     backtrace (crc 0):\n       pcpu_alloc_noprof+0x453/0xd80\n       nft_counter_clone+0x9c/0x190 [nf_tables]\n       nft_expr_clone+0x8f/0x1b0 [nf_tables]\n       nft_dynset_new+0x2cb/0x5f0 [nf_tables]\n       nft_rhash_update+0x236/0x11c0 [nf_tables]\n       nft_dynset_eval+0x11f/0x670 [nf_tables]\n       nft_do_chain+0x253/0x1700 [nf_tables]\n       nft_do_chain_ipv4+0x18d/0x270 [nf_tables]\n       nf_hook_slow+0xaa/0x1e0\n       ip_local_deliver+0x209/0x330(CVE-2026-23399)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nKVM: x86/mmu: Drop/zap existing present SPTE even when creating an MMIO SPTE\n\nWhen installing an emulated MMIO SPTE, do so *after* dropping/zapping the\nexisting SPTE (if it\u0026apos;s shadow-present).  While commit a54aa15c6bda3 was\nright about it being impossible to convert a shadow-present SPTE to an\nMMIO SPTE due to a _guest_ write, it failed to account for writes to guest\nmemory that are outside the scope of KVM.\n\nE.g. if host userspace modifies a shadowed gPTE to switch from a memslot\nto emulted MMIO and then the guest hits a relevant page fault, KVM will\ninstall the MMIO SPTE without first zapping the shadow-present SPTE.\n\n  ------------[ cut here ]------------\n  is_shadow_present_pte(*sptep)\n  WARNING: arch/x86/kvm/mmu/mmu.c:484 at mark_mmio_spte+0xb2/0xc0 [kvm], CPU#0: vmx_ept_stale_r/4292\n  Modules linked in: kvm_intel kvm irqbypass\n  CPU: 0 UID: 1000 PID: 4292 Comm: vmx_ept_stale_r Not tainted 7.0.0-rc2-eafebd2d2ab0-sink-vm #319 PREEMPT\n  Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 0.0.0 02/06/2015\n  RIP: 0010:mark_mmio_spte+0xb2/0xc0 [kvm]\n  Call Trace:\n   \u0026lt;TASK\u0026gt;\n   mmu_set_spte+0x237/0x440 [kvm]\n   ept_page_fault+0x535/0x7f0 [kvm]\n   kvm_mmu_do_page_fault+0xee/0x1f0 [kvm]\n   kvm_mmu_page_fault+0x8d/0x620 [kvm]\n   vmx_handle_exit+0x18c/0x5a0 [kvm_intel]\n   kvm_arch_vcpu_ioctl_run+0xc55/0x1c20 [kvm]\n   kvm_vcpu_ioctl+0x2d5/0x980 [kvm]\n   __x64_sys_ioctl+0x8a/0xd0\n   do_syscall_64+0xb5/0x730\n   entry_SYSCALL_64_after_hwframe+0x4b/0x53\n  RIP: 0033:0x47fa3f\n   \u0026lt;/TASK\u0026gt;\n  ---[ end trace 0000000000000000 ]---(CVE-2026-23401)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\napparmor: fix memory leak in verify_header\n\nThe function sets `*ns = NULL` on every call, leaking the namespace\nstring allocated in previous iterations when multiple profiles are\nunpacked. This also breaks namespace consistency checking since *ns\nis always NULL when the comparison is made.\n\nRemove the incorrect assignment.\nThe caller (aa_unpack) initializes *ns to NULL once before the loop,\nwhich is sufficient.(CVE-2026-23403)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\napparmor: replace recursive profile removal with iterative approach\n\nThe profile removal code uses recursion when removing nested profiles,\nwhich can lead to kernel stack exhaustion and system crashes.\n\nReproducer:\n  $ pf=\u0026apos;a\u0026apos;; for ((i=0; i\u0026lt;1024; i++)); do\n      echo -e \u0026quot;profile $pf { \\n }\u0026quot; | apparmor_parser -K -a;\n      pf=\u0026quot;$pf//x\u0026quot;;\n  done\n  $ echo -n a \u0026gt; /sys/kernel/security/apparmor/.remove\n\nReplace the recursive __aa_profile_list_release() approach with an\niterative approach in __remove_profile(). The function repeatedly\nfinds and removes leaf profiles until the entire subtree is removed,\nmaintaining the same removal semantic without recursion.(CVE-2026-23404)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\napparmor: fix: limit the number of levels of policy namespaces\n\nCurrently the number of policy namespaces is not bounded relying on\nthe user namespace limit. However policy namespaces aren\u0026apos;t strictly\ntied to user namespaces and it is possible to create them and nest\nthem arbitrarily deep which can be used to exhaust system resource.\n\nHard cap policy namespaces to the same depth as user namespaces.(CVE-2026-23405)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\napparmor: Fix double free of ns_name in aa_replace_profiles()\n\nif ns_name is NULL after\n1071         error = aa_unpack(udata, \u0026amp;lh, \u0026amp;ns_name);\n\nand if ent-\u0026gt;ns_name contains an ns_name in\n1089                 } else if (ent-\u0026gt;ns_name) {\n\nthen ns_name is assigned the ent-\u0026gt;ns_name\n1095                         ns_name = ent-\u0026gt;ns_name;\n\nhowever ent-\u0026gt;ns_name is freed at\n1262                 aa_load_ent_free(ent);\n\nand then again when freeing ns_name at\n1270         kfree(ns_name);\n\nFix this by NULLing out ent-\u0026gt;ns_name after it is transferred to ns_name\n\n\u0026quot;)(CVE-2026-23408)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\napparmor: fix differential encoding verification\n\nDifferential encoding allows loops to be created if it is abused. To\nprevent this the unpack should verify that a diff-encode chain\nterminates.\n\nUnfortunately the differential encode verification had two bugs.\n\n1. it conflated states that had gone through check and already been\n   marked, with states that were currently being checked and marked.\n   This means that loops in the current chain being verified are treated\n   as a chain that has already been verified.\n\n2. the order bailout on already checked states compared current chain\n   check iterators j,k instead of using the outer loop iterator i.\n   Meaning a step backwards in states in the current chain verification\n   was being mistaken for moving to an already verified state.\n\nMove to a double mark scheme where already verified states get a\ndifferent mark, than the current chain being kept. This enables us\nto also drop the backwards verification check that was the cause of\nthe second error as any already verified state is already marked.(CVE-2026-23409)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\napparmor: fix race on rawdata dereference\n\nThere is a race condition that leads to a use-after-free situation:\nbecause the rawdata inodes are not refcounted, an attacker can start\nopen()ing one of the rawdata files, and at the same time remove the\nlast reference to this rawdata (by removing the corresponding profile,\nfor example), which frees its struct aa_loaddata; as a result, when\nseq_rawdata_open() is reached, i_private is a dangling pointer and\nfreed memory is accessed.\n\nThe rawdata inodes weren\u0026apos;t refcounted to avoid a circular refcount and\nwere supposed to be held by the profile rawdata reference.  However\nduring profile removal there is a window where the vfs and profile\ndestruction race, resulting in the use after free.\n\nFix this by moving to a double refcount scheme. Where the profile\nrefcount on rawdata is used to break the circular dependency. Allowing\nfor freeing of the rawdata once all inode references to the rawdata\nare put.(CVE-2026-23410)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\napparmor: fix race between freeing data and fs accessing it\n\nAppArmor was putting the reference to i_private data on its end after\nremoving the original entry from the file system. However the inode\ncan aand does live beyond that point and it is possible that some of\nthe fs call back functions will be invoked after the reference has\nbeen put, which results in a race between freeing the data and\naccessing it through the fs.\n\nWhile the rawdata/loaddata is the most likely candidate to fail the\nrace, as it has the fewest references. If properly crafted it might be\npossible to trigger a race for the other types stored in i_private.\n\nFix this by moving the put of i_private referenced data to the correct\nplace which is during inode eviction.(CVE-2026-23411)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nclsact: Fix use-after-free in init/destroy rollback asymmetry\n\nFix a use-after-free in the clsact qdisc upon init/destroy rollback asymmetry.\nThe latter is achieved by first fully initializing a clsact instance, and\nthen in a second step having a replacement failure for the new clsact qdisc\ninstance. clsact_init() initializes ingress first and then takes care of the\negress part. This can fail midway, for example, via tcf_block_get_ext(). Upon\nfailure, the kernel will trigger the clsact_destroy() callback.\n\nCommit 1cb6f0bae504 (\u0026quot;bpf: Fix too early release of tcx_entry\u0026quot;) details the\nway how the transition is happening. If tcf_block_get_ext on the q-\u0026gt;ingress_block\nends up failing, we took the tcx_miniq_inc reference count on the ingress\nside, but not yet on the egress side. clsact_destroy() tests whether the\n{ingress,egress}_entry was non-NULL. However, even in midway failure on the\nreplacement, both are in fact non-NULL with a valid egress_entry from the\nprevious clsact instance.\n\nWhat we really need to test for is whether the qdisc instance-specific ingress\nor egress side previously got initialized. This adds a small helper for checking\nthe miniq initialization called mini_qdisc_pair_inited, and utilizes that upon\nclsact_destroy() in order to fix the use-after-free scenario. Convert the\ningress_destroy() side as well so both are consistent to each other.(CVE-2026-23413)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ntls: Purge async_hold in tls_decrypt_async_wait()\n\nThe async_hold queue pins encrypted input skbs while\nthe AEAD engine references their scatterlist data. Once\ntls_decrypt_async_wait() returns, every AEAD operation\nhas completed and the engine no longer references those\nskbs, so they can be freed unconditionally.\n\nA subsequent patch adds batch async decryption to\ntls_sw_read_sock(), introducing a new call site that\nmust drain pending AEAD operations and release held\nskbs. Move __skb_queue_purge(\u0026amp;ctx-\u0026gt;async_hold) into\ntls_decrypt_async_wait() so the purge is centralized\nand every caller -- recvmsg\u0026apos;s drain path, the -EBUSY\nfallback in tls_do_decryption(), and the new read_sock\nbatch path -- releases held skbs on synchronization\nwithout each site managing the purge independently.\n\nThis fixes a leak when tls_strp_msg_hold() fails part-way through,\nafter having added some cloned skbs to the async_hold\nqueue. tls_decrypt_sg() will then call tls_decrypt_async_wait() to\nprocess all pending decrypts, and drop back to synchronous mode, but\ntls_sw_recvmsg() only flushes the async_hold queue when one record has\nbeen processed in \u0026quot;fully-async\u0026quot; mode, which may not be the case here.\n\n[(CVE-2026-23414)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nxen/privcmd: restrict usage in unprivileged domU\n\nThe Xen privcmd driver allows to issue arbitrary hypercalls from\nuser space processes. This is normally no problem, as access is\nusually limited to root and the hypervisor will deny any hypercalls\naffecting other domains.\n\nIn case the guest is booted using secure boot, however, the privcmd\ndriver would be enabling a root user process to modify e.g. kernel\nmemory contents, thus breaking the secure boot feature.\n\nThe only known case where an unprivileged domU is really needing to\nuse the privcmd driver is the case when it is acting as the device\nmodel for another guest. In this case all hypercalls issued via the\nprivcmd driver will target that other guest.\n\nFortunately the privcmd driver can already be locked down to allow\nonly hypercalls targeting a specific domain, but this mode can be\nactivated from user land only today.\n\nThe target domain can be obtained from Xenstore, so when not running\nin dom0 restrict the privcmd driver to that target domain from the\nbeginning, resolving the potential problem of breaking secure boot.\n\nThis is XSA-482\n\n---\nV2:\n- defer reading from Xenstore if Xenstore isn\u0026apos;t ready yet (Jan Beulich)\n- wait in open() if target domain isn\u0026apos;t known yet\n- issue message in case no target domain found (Jan Beulich)(CVE-2026-31788)","status":"published","published":"2026-04-11T11:10:52Z","modified":"2026-08-18T01:19:47.332682492Z","cvss":[{"version":"3.1","score":9.8,"vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H","level":"critical"}],"updated_at":"2026-11-02T15:52:46.087701Z"},{"id":"OESA-2026-1863","title":"kernel security update","description":"The Linux Kernel, the operating system core itself.\r\n\r\nSecurity Fix(es):\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nf2fs: fix to detect potential corrupted nid in free_nid_list\n\nAs reported, on-disk footer.ino and footer.nid is the same and\nout-of-range, let\u0026apos;s add sanity check on f2fs_alloc_nid() to detect\nany potential corruption in free_nid_list.(CVE-2025-68315)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nntfs3: Fix uninit buffer allocated by __getname()\n\nFix uninit errors caused after buffer allocation given to \u0026apos;de\u0026apos;; by\ninitializing the buffer with zeroes. The fix was found by using KMSAN.(CVE-2025-68727)\n\nIn the Linux kernel, a security vulnerability exists in the IOMMU Shared Virtual Addressing (SVA) feature. On x86 architecture when CONFIG_X86 is set, IOMMU hardware caches kernel page table entries. Due to the lack of notification mechanism for kernel page table changes, when kernel page table pages are freed and reused, the IOMMU may retain stale entries, leading to Use-After-Free (UAF) and Write-After-Free (WAF) conditions. This can be exploited to cause arbitrary physical memory DMA access or privilege escalation.(CVE-2025-71089)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nuacce: fix cdev handling in the cleanup path\n\nWhen cdev_device_add fails, it internally releases the cdev memory,\nand if cdev_device_del is then executed, it will cause a hang error.\nTo fix it, we check the return value of cdev_device_add() and clear\nuacce-\u0026gt;cdev to avoid calling cdev_device_del in the uacce_remove.(CVE-2026-23096)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nbonding: fix use-after-free due to enslave fail after slave array update\n\nFix a use-after-free which happens due to enslave failure after the new\nslave has been added to the array. Since the new slave can be used for Tx\nimmediately, we can use it after it has been freed by the enslave error\ncleanup path which frees the allocated slave memory. Slave update array is\nsupposed to be called last when further enslave failures are not expected.\nMove it after xdp setup to avoid any problems.\n\nIt is very easy to reproduce the problem with a simple xdp_pass prog:\n ip l add bond1 type bond mode balance-xor\n ip l set bond1 up\n ip l set dev bond1 xdp object xdp_pass.o sec xdp_pass\n ip l add dumdum type dummy\n\nThen run in parallel:\n while :; do ip l set dumdum master bond1 1\u0026gt;/dev/null 2\u0026gt;\u0026amp;1; done;\n mausezahn bond1 -a own -b rand -A rand -B 1.1.1.1 -c 0 -t tcp \u0026quot;dp=1-1023, flags=syn\u0026quot;\n\nThe crash happens almost immediately:\n [  605.602850] Oops: general protection fault, probably for non-canonical address 0xe0e6fc2460000137: 0000 [#1] SMP KASAN NOPTI\n [  605.602916] KASAN: maybe wild-memory-access in range [0x07380123000009b8-0x07380123000009bf]\n [  605.602946] CPU: 0 UID: 0 PID: 2445 Comm: mausezahn Kdump: loaded Tainted: G    B               6.19.0-rc6+ #21 PREEMPT(voluntary)\n [  605.602979] Tainted: [B]=BAD_PAGE\n [  605.602998] Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.16.3-debian-1.16.3-2 04/01/2014\n [  605.603032] RIP: 0010:netdev_core_pick_tx+0xcd/0x210\n [  605.603063] Code: 48 89 fa 48 c1 ea 03 80 3c 02 00 0f 85 3e 01 00 00 48 b8 00 00 00 00 00 fc ff df 4c 8b 6b 08 49 8d 7d 30 48 89 fa 48 c1 ea 03 \u0026lt;80\u0026gt; 3c 02 00 0f 85 25 01 00 00 49 8b 45 30 4c 89 e2 48 89 ee 48 89\n [  605.603111] RSP: 0018:ffff88817b9af348 EFLAGS: 00010213\n [  605.603145] RAX: dffffc0000000000 RBX: ffff88817d28b420 RCX: 0000000000000000\n [  605.603172] RDX: 00e7002460000137 RSI: 0000000000000008 RDI: 07380123000009be\n [  605.603199] RBP: ffff88817b541a00 R08: 0000000000000001 R09: fffffbfff3ed8c0c\n [  605.603226] R10: ffffffff9f6c6067 R11: 0000000000000001 R12: 0000000000000000\n [  605.603253] R13: 073801230000098e R14: ffff88817d28b448 R15: ffff88817b541a84\n [  605.603286] FS:  00007f6570ef67c0(0000) GS:ffff888221dfa000(0000) knlGS:0000000000000000\n [  605.603319] CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033\n [  605.603343] CR2: 00007f65712fae40 CR3: 000000011371b000 CR4: 0000000000350ef0\n [  605.603373] Call Trace:\n [  605.603392]  \u0026lt;TASK\u0026gt;\n [  605.603410]  __dev_queue_xmit+0x448/0x32a0\n [  605.603434]  ? __pfx_vprintk_emit+0x10/0x10\n [  605.603461]  ? __pfx_vprintk_emit+0x10/0x10\n [  605.603484]  ? __pfx___dev_queue_xmit+0x10/0x10\n [  605.603507]  ? bond_start_xmit+0xbfb/0xc20 [bonding]\n [  605.603546]  ? _printk+0xcb/0x100\n [  605.603566]  ? __pfx__printk+0x10/0x10\n [  605.603589]  ? bond_start_xmit+0xbfb/0xc20 [bonding]\n [  605.603627]  ? add_taint+0x5e/0x70\n [  605.603648]  ? add_taint+0x2a/0x70\n [  605.603670]  ? end_report.cold+0x51/0x75\n [  605.603693]  ? bond_start_xmit+0xbfb/0xc20 [bonding]\n [  605.603731]  bond_start_xmit+0x623/0xc20 [bonding](CVE-2026-23171)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnetfilter: nf_tables: fix use-after-free in nf_tables_addchain()\n\nnf_tables_addchain() publishes the chain to table-\u0026gt;chains via\nlist_add_tail_rcu() (in nft_chain_add()) before registering hooks.\nIf nf_tables_register_hook() then fails, the error path calls\nnft_chain_del() (list_del_rcu()) followed by nf_tables_chain_destroy()\nwith no RCU grace period in between.\n\nThis creates two use-after-free conditions:\n\n 1) Control-plane: nf_tables_dump_chains() traverses table-\u0026gt;chains\n    under rcu_read_lock(). A concurrent dump can still be walking\n    the chain when the error path frees it.\n\n 2) Packet path: for NFPROTO_INET, nf_register_net_hook() briefly\n    installs the IPv4 hook before IPv6 registration fails.  Packets\n    entering nft_do_chain() via the transient IPv4 hook can still be\n    dereferencing chain-\u0026gt;blob_gen_X when the error path frees the\n    chain.\n\nAdd synchronize_rcu() between nft_chain_del() and the chain destroy\nso that all RCU readers -- both dump threads and in-flight packet\nevaluation -- have finished before the chain is freed.(CVE-2026-23231)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ntls: Fix race condition in tls_sw_cancel_work_tx()\n\nThis issue was discovered during a code audit.\n\nAfter cancel_delayed_work_sync() is called from tls_sk_proto_close(),\ntx_work_handler() can still be scheduled from paths such as the\nDelayed ACK handler or ksoftirqd.\nAs a result, the tx_work_handler() worker may dereference a freed\nTLS object.\n\nThe following is a simple race scenario:\n\n          cpu0                         cpu1\n\ntls_sk_proto_close()\n  tls_sw_cancel_work_tx()\n                                 tls_write_space()\n                                   tls_sw_write_space()\n                                     if (!test_and_set_bit(BIT_TX_SCHEDULED, \u0026amp;tx_ctx-\u0026gt;tx_bitmask))\n    set_bit(BIT_TX_SCHEDULED, \u0026amp;ctx-\u0026gt;tx_bitmask);\n    cancel_delayed_work_sync(\u0026amp;ctx-\u0026gt;tx_work.work);\n                                     schedule_delayed_work(\u0026amp;tx_ctx-\u0026gt;tx_work.work, 0);\n\nTo prevent this race condition, cancel_delayed_work_sync() is\nreplaced with disable_delayed_work_sync().(CVE-2026-23240)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnet/sched: act_gate: snapshot parameters with RCU on replace\n\nThe gate action can be replaced while the hrtimer callback or dump path is\nwalking the schedule list.\n\nConvert the parameters to an RCU-protected snapshot and swap updates under\ntcf_lock, freeing the previous snapshot via call_rcu(). When REPLACE omits\nthe entry list, preserve the existing schedule so the effective state is\nunchanged.(CVE-2026-23245)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnet: gro: fix outer network offset\n\nThe udp GRO complete stage assumes that all the packets inserted the RX\nhave the `encapsulation` flag zeroed. Such assumption is not true, as a\nfew H/W NICs can set such flag when H/W offloading the checksum for\nan UDP encapsulated traffic, the tun driver can inject GSO packets with\nUDP encapsulation and the problematic layout can also be created via\na veth based setup.\n\nDue to the above, in the problematic scenarios, udp4_gro_complete() uses\nthe wrong network offset (inner instead of outer) to compute the outer\nUDP header pseudo checksum, leading to csum validation errors later on\nin packet processing.\n\nAddress the issue always clearing the encapsulation flag at GRO completion\ntime. Such flag will be set again as needed for encapsulated packets by\nudp_gro_complete().(CVE-2026-23254)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnet: add proper RCU protection to /proc/net/ptype\n\nYin Fengwei reported an RCU stall in ptype_seq_show() and provided\na patch.\n\nReal issue is that ptype_seq_next() and ptype_seq_show() violate\nRCU rules.\n\nptype_seq_show() runs under rcu_read_lock(), and reads pt-\u0026gt;dev\nto get device name without any barrier.\n\nAt the same time, concurrent writers can remove a packet_type structure\n(which is correctly freed after an RCU grace period) and clear pt-\u0026gt;dev\nwithout an RCU grace period.\n\nDefine ptype_iter_state to carry a dev pointer along seq_net_private:\n\nstruct ptype_iter_state {\n\tstruct seq_net_private\tp;\n\tstruct net_device\t*dev; // added in this patch\n};\n\nWe need to record the device pointer in ptype_get_idx() and\nptype_seq_next() so that ptype_seq_show() is safe against\nconcurrent pt-\u0026gt;dev changes.\n\nWe also need to add full RCU protection in ptype_seq_next().\n(Missing READ_ONCE() when reading list.next values)\n\nMany thanks to Dong Chenchen for providing a repro.(CVE-2026-23255)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnet/sched: Only allow act_ct to bind to clsact/ingress qdiscs and shared blocks\n\nAs Paolo said earlier [1]:\n\n\u0026quot;Since the blamed commit below, classify can return TC_ACT_CONSUMED while\nthe current skb being held by the defragmentation engine. As reported by\nGangMin Kim, if such packet is that may cause a UaF when the defrag engine\nlater on tries to tuch again such packet.\u0026quot;\n\nact_ct was never meant to be used in the egress path, however some users\nare attaching it to egress today [2]. Attempting to reach a middle\nground, we noticed that, while most qdiscs are not handling\nTC_ACT_CONSUMED, clsact/ingress qdiscs are. With that in mind, we\naddress the issue by only allowing act_ct to bind to clsact/ingress\nqdiscs and shared blocks. That way it\u0026apos;s still possible to attach act_ct to\negress (albeit only with clsact).\n\n[1] https://lore.kernel.org/netdev/674b8cbfc385c6f37fb29a1de08d8fe5c2b0fbee.1771321118.git.pabeni@redhat.com/\n[2] https://lore.kernel.org/netdev/(CVE-2026-23270)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnetfilter: xt_IDLETIMER: reject rev0 reuse of ALARM timer labels\n\nIDLETIMER revision 0 rules reuse existing timers by label and always call\nmod_timer() on timer-\u0026gt;timer.\n\nIf the label was created first by revision 1 with XT_IDLETIMER_ALARM,\nthe object uses alarm timer semantics and timer-\u0026gt;timer is never initialized.\nReusing that object from revision 0 causes mod_timer() on an uninitialized\ntimer_list, triggering debugobjects warnings and possible panic when\npanic_on_warn=1.\n\nFix this by rejecting revision 0 rule insertion when an existing timer with\nthe same label is of ALARM type.(CVE-2026-23274)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnet: add xmit recursion limit to tunnel xmit functions\n\nTunnel xmit functions (iptunnel_xmit, ip6tunnel_xmit) lack their own\nrecursion limit. When a bond device in broadcast mode has GRE tap\ninterfaces as slaves, and those GRE tunnels route back through the\nbond, multicast/broadcast traffic triggers infinite recursion between\nbond_xmit_broadcast() and ip_tunnel_xmit()/ip6_tnl_xmit(), causing\nkernel stack overflow.\n\nThe existing XMIT_RECURSION_LIMIT (8) in the no-qdisc path is not\nsufficient because tunnel recursion involves route lookups and full IP\noutput, consuming much more stack per level. Use a lower limit of 4\n(IP_TUNNEL_RECURSION_LIMIT) to prevent overflow.\n\nAdd recursion detection using dev_xmit_recursion helpers directly in\niptunnel_xmit() and ip6tunnel_xmit() to cover all IPv4/IPv6 tunnel\npaths including UDP encapsulated tunnels (VXLAN, Geneve, etc.).\n\nMove dev_xmit_recursion helpers from net/core/dev.h to public header\ninclude/linux/netdevice.h so they can be used by tunnel code.\n\n BUG: KASAN: stack-out-of-bounds in blake2s.constprop.0+0xe7/0x160\n Write of size 32 at addr ffff88810033fed0 by task kworker/0:1/11\n Workqueue: mld mld_ifc_work\n Call Trace:\n  \u0026lt;TASK\u0026gt;\n  __build_flow_key.constprop.0 (net/ipv4/route.c:515)\n  ip_rt_update_pmtu (net/ipv4/route.c:1073)\n  iptunnel_xmit (net/ipv4/ip_tunnel_core.c:84)\n  ip_tunnel_xmit (net/ipv4/ip_tunnel.c:847)\n  gre_tap_xmit (net/ipv4/ip_gre.c:779)\n  dev_hard_start_xmit (net/core/dev.c:3887)\n  sch_direct_xmit (net/sched/sch_generic.c:347)\n  __dev_queue_xmit (net/core/dev.c:4802)\n  bond_dev_queue_xmit (drivers/net/bonding/bond_main.c:312)\n  bond_xmit_broadcast (drivers/net/bonding/bond_main.c:5279)\n  bond_start_xmit (drivers/net/bonding/bond_main.c:5530)\n  dev_hard_start_xmit (net/core/dev.c:3887)\n  __dev_queue_xmit (net/core/dev.c:4841)\n  ip_finish_output2 (net/ipv4/ip_output.c:237)\n  ip_output (net/ipv4/ip_output.c:438)\n  iptunnel_xmit (net/ipv4/ip_tunnel_core.c:86)\n  gre_tap_xmit (net/ipv4/ip_gre.c:779)\n  dev_hard_start_xmit (net/core/dev.c:3887)\n  sch_direct_xmit (net/sched/sch_generic.c:347)\n  __dev_queue_xmit (net/core/dev.c:4802)\n  bond_dev_queue_xmit (drivers/net/bonding/bond_main.c:312)\n  bond_xmit_broadcast (drivers/net/bonding/bond_main.c:5279)\n  bond_start_xmit (drivers/net/bonding/bond_main.c:5530)\n  dev_hard_start_xmit (net/core/dev.c:3887)\n  __dev_queue_xmit (net/core/dev.c:4841)\n  ip_finish_output2 (net/ipv4/ip_output.c:237)\n  ip_output (net/ipv4/ip_output.c:438)\n  iptunnel_xmit (net/ipv4/ip_tunnel_core.c:86)\n  ip_tunnel_xmit (net/ipv4/ip_tunnel.c:847)\n  gre_tap_xmit (net/ipv4/ip_gre.c:779)\n  dev_hard_start_xmit (net/core/dev.c:3887)\n  sch_direct_xmit (net/sched/sch_generic.c:347)\n  __dev_queue_xmit (net/core/dev.c:4802)\n  bond_dev_queue_xmit (drivers/net/bonding/bond_main.c:312)\n  bond_xmit_broadcast (drivers/net/bonding/bond_main.c:5279)\n  bond_start_xmit (drivers/net/bonding/bond_main.c:5530)\n  dev_hard_start_xmit (net/core/dev.c:3887)\n  __dev_queue_xmit (net/core/dev.c:4841)\n  mld_sendpack\n  mld_ifc_work\n  process_one_work\n  worker_thread\n  \u0026lt;/TASK\u0026gt;(CVE-2026-23276)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnet/sched: teql: fix NULL pointer dereference in iptunnel_xmit on TEQL slave xmit\n\nteql_master_xmit() calls netdev_start_xmit(skb, slave) to transmit\nthrough slave devices, but does not update skb-\u0026gt;dev to the slave device\nbeforehand.\n\nWhen a gretap tunnel is a TEQL slave, the transmit path reaches\niptunnel_xmit() which saves dev = skb-\u0026gt;dev (still pointing to teql0\nmaster) and later calls iptunnel_xmit_stats(dev, pkt_len). This\nfunction does:\n\n    get_cpu_ptr(dev-\u0026gt;tstats)\n\nSince teql_master_setup() does not set dev-\u0026gt;pcpu_stat_type to\nNETDEV_PCPU_STAT_TSTATS, the core network stack never allocates tstats\nfor teql0, so dev-\u0026gt;tstats is NULL. get_cpu_ptr(NULL) computes\nNULL + __per_cpu_offset[cpu], resulting in a page fault.\n\n BUG: unable to handle page fault for address: ffff8880e6659018\n #PF: supervisor write access in kernel mode\n #PF: error_code(0x0002) - not-present page\n PGD 68bc067 P4D 68bc067 PUD 0\n Oops: Oops: 0002 [#1] SMP KASAN PTI\n RIP: 0010:iptunnel_xmit (./include/net/ip_tunnels.h:664 net/ipv4/ip_tunnel_core.c:89)\n Call Trace:\n  \u0026lt;TASK\u0026gt;\n  ip_tunnel_xmit (net/ipv4/ip_tunnel.c:847)\n  __gre_xmit (net/ipv4/ip_gre.c:478)\n  gre_tap_xmit (net/ipv4/ip_gre.c:779)\n  teql_master_xmit (net/sched/sch_teql.c:319)\n  dev_hard_start_xmit (net/core/dev.c:3887)\n  sch_direct_xmit (net/sched/sch_generic.c:347)\n  __dev_queue_xmit (net/core/dev.c:4802)\n  neigh_direct_output (net/core/neighbour.c:1660)\n  ip_finish_output2 (net/ipv4/ip_output.c:237)\n  __ip_finish_output.part.0 (net/ipv4/ip_output.c:315)\n  ip_mc_output (net/ipv4/ip_output.c:369)\n  ip_send_skb (net/ipv4/ip_output.c:1508)\n  udp_send_skb (net/ipv4/udp.c:1195)\n  udp_sendmsg (net/ipv4/udp.c:1485)\n  inet_sendmsg (net/ipv4/af_inet.c:859)\n  __sys_sendto (net/socket.c:2206)\n\nFix this by setting skb-\u0026gt;dev = slave before calling\nnetdev_start_xmit(), so that tunnel xmit functions see the correct\nslave device with properly allocated tstats.(CVE-2026-23277)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnetfilter: nf_tables: always walk all pending catchall elements\n\nDuring transaction processing we might have more than one catchall element:\n1 live catchall element and 1 pending element that is coming as part of the\nnew batch.\n\nIf the map holding the catchall elements is also going away, its\nrequired to toggle all catchall elements and not just the first viable\ncandidate.\n\nOtherwise, we get:\n WARNING: ./include/net/netfilter/nf_tables.h:1281 at nft_data_release+0xb7/0xe0 [nf_tables], CPU#2: nft/1404\n RIP: 0010:nft_data_release+0xb7/0xe0 [nf_tables]\n [..]\n __nft_set_elem_destroy+0x106/0x380 [nf_tables]\n nf_tables_abort_release+0x348/0x8d0 [nf_tables]\n nf_tables_abort+0xcf2/0x3ac0 [nf_tables]\n nfnetlink_rcv_batch+0x9c9/0x20e0 [..](CVE-2026-23278)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnet: vxlan: fix nd_tbl NULL dereference when IPv6 is disabled\n\nWhen booting with the \u0026apos;ipv6.disable=1\u0026apos; parameter, the nd_tbl is never\ninitialized because inet6_init() exits before ndisc_init() is called\nwhich initializes it. If an IPv6 packet is injected into the interface,\nroute_shortcircuit() is called and a NULL pointer dereference happens on\nneigh_lookup().\n\n BUG: kernel NULL pointer dereference, address: 0000000000000380\n Oops: Oops: 0000 [#1] SMP NOPTI\n [...]\n RIP: 0010:neigh_lookup+0x20/0x270\n [...]\n Call Trace:\n  \u0026lt;TASK\u0026gt;\n  vxlan_xmit+0x638/0x1ef0 [vxlan]\n  dev_hard_start_xmit+0x9e/0x2e0\n  __dev_queue_xmit+0xbee/0x14e0\n  packet_sendmsg+0x116f/0x1930\n  __sys_sendto+0x1f5/0x200\n  __x64_sys_sendto+0x24/0x30\n  do_syscall_64+0x12f/0x1590\n  entry_SYSCALL_64_after_hwframe+0x76/0x7e\n\nFix this by adding an early check on route_shortcircuit() when protocol\nis ETH_P_IPV6. Note that ipv6_mod_enabled() cannot be used here because\nVXLAN can be built-in even when IPv6 is built as a module.(CVE-2026-23293)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnet: ipv6: fix panic when IPv4 route references loopback IPv6 nexthop\n\nWhen a standalone IPv6 nexthop object is created with a loopback device\n(e.g., \u0026quot;ip -6 nexthop add id 100 dev lo\u0026quot;), fib6_nh_init() misclassifies\nit as a reject route. This is because nexthop objects have no destination\nprefix (fc_dst=::), causing fib6_is_reject() to match any loopback\nnexthop. The reject path skips fib_nh_common_init(), leaving\nnhc_pcpu_rth_output unallocated. If an IPv4 route later references this\nnexthop, __mkroute_output() dereferences NULL nhc_pcpu_rth_output and\npanics.\n\nSimplify the check in fib6_nh_init() to only match explicit reject\nroutes (RTF_REJECT) instead of using fib6_is_reject(). The loopback\npromotion heuristic in fib6_is_reject() is handled separately by\nip6_route_info_create_nh(). After this change, the three cases behave\nas follows:\n\n1. Explicit reject route (\u0026quot;ip -6 route add unreachable 2001:db8::/64\u0026quot;):\n   RTF_REJECT is set, enters reject path, skips fib_nh_common_init().\n   No behavior change.\n\n2. Implicit loopback reject route (\u0026quot;ip -6 route add 2001:db8::/32 dev lo\u0026quot;):\n   RTF_REJECT is not set, takes normal path, fib_nh_common_init() is\n   called. ip6_route_info_create_nh() still promotes it to reject\n   afterward. nhc_pcpu_rth_output is allocated but unused, which is\n   harmless.\n\n3. Standalone nexthop object (\u0026quot;ip -6 nexthop add id 100 dev lo\u0026quot;):\n   RTF_REJECT is not set, takes normal path, fib_nh_common_init() is\n   called. nhc_pcpu_rth_output is properly allocated, fixing the crash\n   when IPv4 routes reference this nexthop.(CVE-2026-23300)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnet: annotate data-races around sk-\u0026gt;sk_{data_ready,write_space}\n\nskmsg (and probably other layers) are changing these pointers\nwhile other cpus might read them concurrently.\n\nAdd corresponding READ_ONCE()/WRITE_ONCE() annotations\nfor UDP, TCP and AF_UNIX.(CVE-2026-23302)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nsmb: client: Don\u0026apos;t log plaintext credentials in cifs_set_cifscreds\n\nWhen debug logging is enabled, cifs_set_cifscreds() logs the key\npayload and exposes the plaintext username and password. Remove the\ndebug log to avoid exposing credentials.(CVE-2026-23303)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nipv6: fix NULL pointer deref in ip6_rt_get_dev_rcu()\n\nl3mdev_master_dev_rcu() can return NULL when the slave device is being\nun-slaved from a VRF. All other callers deal with this, but we lost\nthe fallback to loopback in ip6_rt_pcpu_alloc() -\u0026gt; ip6_rt_get_dev_rcu()\nwith commit 4832c30d5458 (\u0026quot;net: ipv6: put host and anycast routes on\ndevice with address\u0026quot;).\n\n  KASAN: null-ptr-deref in range [0x0000000000000108-0x000000000000010f]\n  RIP: 0010:ip6_rt_pcpu_alloc (net/ipv6/route.c:1418)\n  Call Trace:\n   ip6_pol_route (net/ipv6/route.c:2318)\n   fib6_rule_lookup (net/ipv6/fib6_rules.c:115)\n   ip6_route_output_flags (net/ipv6/route.c:2607)\n   vrf_process_v6_outbound (drivers/net/vrf.c:437)\n\nI was tempted to rework the un-slaving code to clear the flag first\nand insert synchronize_rcu() before we remove the upper. But looks like\nthe explicit fallback to loopback_dev is an established pattern.\nAnd I guess avoiding the synchronize_rcu() is nice, too.(CVE-2026-23304)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nbpf/bonding: reject vlan+srcmac xmit_hash_policy change when XDP is loaded\n\nbond_option_mode_set() already rejects mode changes that would make a\nloaded XDP program incompatible via bond_xdp_check().  However,\nbond_option_xmit_hash_policy_set() has no such guard.\n\nFor 802.3ad and balance-xor modes, bond_xdp_check() returns false when\nxmit_hash_policy is vlan+srcmac, because the 802.1q payload is usually\nabsent due to hardware offload.  This means a user can:\n\n1. Attach a native XDP program to a bond in 802.3ad/balance-xor mode\n   with a compatible xmit_hash_policy (e.g. layer2+3).\n2. Change xmit_hash_policy to vlan+srcmac while XDP remains loaded.\n\nThis leaves bond-\u0026gt;xdp_prog set but bond_xdp_check() now returning false\nfor the same device.  When the bond is later destroyed, dev_xdp_uninstall()\ncalls bond_xdp_set(dev, NULL, NULL) to remove the program, which hits\nthe bond_xdp_check() guard and returns -EOPNOTSUPP, triggering:\n\nWARN_ON(dev_xdp_install(dev, mode, bpf_op, NULL, 0, NULL))\n\nFix this by rejecting xmit_hash_policy changes to vlan+srcmac when an\nXDP program is loaded on a bond in 802.3ad or balance-xor mode.\n\ncommit 39a0876d595b (\u0026quot;net, bonding: Disallow vlan+srcmac with XDP\u0026quot;)\nintroduced bond_xdp_check() which returns false for 802.3ad/balance-xor\nmodes when xmit_hash_policy is vlan+srcmac.  The check was wired into\nbond_xdp_set() to reject XDP attachment with an incompatible policy, but\nthe symmetric path -- preventing xmit_hash_policy from being changed to an\nincompatible value after XDP is already loaded -- was left unguarded in\nbond_option_xmit_hash_policy_set().\n\nNote:\ncommit 094ee6017ea0 (\u0026quot;bonding: check xdp prog when set bond mode\u0026quot;)\nlater added a similar guard to bond_option_mode_set(), but\nbond_option_xmit_hash_policy_set() remained unprotected.(CVE-2026-23310)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nmptcp: pm: in-kernel: always mark signal+subflow endp as used\n\nSyzkaller managed to find a combination of actions that was generating\nthis warning:\n\n  msk-\u0026gt;pm.local_addr_used == 0\n  WARNING: net/mptcp/pm_kernel.c:1071 at __mark_subflow_endp_available net/mptcp/pm_kernel.c:1071 [inline], CPU#1: syz.2.17/961\n  WARNING: net/mptcp/pm_kernel.c:1071 at mptcp_nl_remove_subflow_and_signal_addr net/mptcp/pm_kernel.c:1103 [inline], CPU#1: syz.2.17/961\n  WARNING: net/mptcp/pm_kernel.c:1071 at mptcp_pm_nl_del_addr_doit+0x81d/0x8f0 net/mptcp/pm_kernel.c:1210, CPU#1: syz.2.17/961\n  Modules linked in:\n  CPU: 1 UID: 0 PID: 961 Comm: syz.2.17 Not tainted 6.19.0-08368-gfafda3b4b06b #22 PREEMPT(full)\n  Hardware name: QEMU Ubuntu 25.10 PC v2 (i440FX + PIIX, + 10.1 machine, 1996), BIOS 1.17.0-debian-1.17.0-1build1 04/01/2014\n  RIP: 0010:__mark_subflow_endp_available net/mptcp/pm_kernel.c:1071 [inline]\n  RIP: 0010:mptcp_nl_remove_subflow_and_signal_addr net/mptcp/pm_kernel.c:1103 [inline]\n  RIP: 0010:mptcp_pm_nl_del_addr_doit+0x81d/0x8f0 net/mptcp/pm_kernel.c:1210\n  Code: 89 c5 e8 46 30 6f fe e9 21 fd ff ff 49 83 ed 80 e8 38 30 6f fe 4c 89 ef be 03 00 00 00 e8 db 49 df fe eb ac e8 24 30 6f fe 90 \u0026lt;0f\u0026gt; 0b 90 e9 1d ff ff ff e8 16 30 6f fe eb 05 e8 0f 30 6f fe e8 9a\n  RSP: 0018:ffffc90001663880 EFLAGS: 00010293\n  RAX: ffffffff82de1a6c RBX: 0000000000000000 RCX: ffff88800722b500\n  RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000000000000\n  RBP: ffff8880158b22d0 R08: 0000000000010425 R09: ffffffffffffffff\n  R10: ffffffff82de18ba R11: 0000000000000000 R12: ffff88800641a640\n  R13: ffff8880158b1880 R14: ffff88801ec3c900 R15: ffff88800641a650\n  FS:  00005555722c3500(0000) GS:ffff8880f909d000(0000) knlGS:0000000000000000\n  CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033\n  CR2: 00007f66346e0f60 CR3: 000000001607c000 CR4: 0000000000350ef0\n  Call Trace:\n   \u0026lt;TASK\u0026gt;\n   genl_family_rcv_msg_doit+0x117/0x180 net/netlink/genetlink.c:1115\n   genl_family_rcv_msg net/netlink/genetlink.c:1195 [inline]\n   genl_rcv_msg+0x3a8/0x3f0 net/netlink/genetlink.c:1210\n   netlink_rcv_skb+0x16d/0x240 net/netlink/af_netlink.c:2550\n   genl_rcv+0x28/0x40 net/netlink/genetlink.c:1219\n   netlink_unicast_kernel net/netlink/af_netlink.c:1318 [inline]\n   netlink_unicast+0x3e9/0x4c0 net/netlink/af_netlink.c:1344\n   netlink_sendmsg+0x4aa/0x5b0 net/netlink/af_netlink.c:1894\n   sock_sendmsg_nosec net/socket.c:727 [inline]\n   __sock_sendmsg+0xc9/0xf0 net/socket.c:742\n   ____sys_sendmsg+0x272/0x3b0 net/socket.c:2592\n   ___sys_sendmsg+0x2de/0x320 net/socket.c:2646\n   __sys_sendmsg net/socket.c:2678 [inline]\n   __do_sys_sendmsg net/socket.c:2683 [inline]\n   __se_sys_sendmsg net/socket.c:2681 [inline]\n   __x64_sys_sendmsg+0x110/0x1a0 net/socket.c:2681\n   do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline]\n   do_syscall_64+0x143/0x440 arch/x86/entry/syscall_64.c:94\n   entry_SYSCALL_64_after_hwframe+0x77/0x7f\n  RIP: 0033:0x7f66346f826d\n  Code: ff c3 66 2e 0f 1f 84 00 00 00 00 00 90 f3 0f 1e fa 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 \u0026lt;48\u0026gt; 3d 01 f0 ff ff 73 01 c3 48 c7 c1 e8 ff ff ff f7 d8 64 89 01 48\n  RSP: 002b:00007ffc83d8bdc8 EFLAGS: 00000246 ORIG_RAX: 000000000000002e\n  RAX: ffffffffffffffda RBX: 00007f6634985fa0 RCX: 00007f66346f826d\n  RDX: 00000000040000b0 RSI: 0000200000000740 RDI: 0000000000000007\n  RBP: 0000000000000000 R08: 0000000000000000 R09: 0000000000000000\n  R10: 0000000000000000 R11: 0000000000000246 R12: 00007f6634985fa8\n  R13: 00007f6634985fac R14: 0000000000000000 R15: 0000000000001770\n   \u0026lt;/TASK\u0026gt;\n\nThe actions that caused that seem to be:\n\n - Set the MPTCP subflows limit to 0\n - Create an MPTCP endpoint with both the \u0026apos;signal\u0026apos; and \u0026apos;subflow\u0026apos; flags\n - Create a new MPTCP connection from a different address: an ADD_ADDR\n   linked to the MPTCP endpoint will be sent (\u0026apos;signal\u0026apos; flag), but no\n   subflows is initiated (\u0026apos;subflow\u0026apos; flag)\n - Remove the MPTCP endpoint\n\n---truncated---(CVE-2026-23321)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nxdp: produce a warning when calculated tailroom is negative\n\nMany ethernet drivers report xdp Rx queue frag size as being the same as\nDMA write size. However, the only user of this field, namely\nbpf_xdp_frags_increase_tail(), clearly expects a truesize.\n\nSuch difference leads to unspecific memory corruption issues under certain\ncircumstances, e.g. in ixgbevf maximum DMA write size is 3 KB, so when\nrunning xskxceiver\u0026apos;s XDP_ADJUST_TAIL_GROW_MULTI_BUFF, 6K packet fully uses\nall DMA-writable space in 2 buffers. This would be fine, if only\nrxq-\u0026gt;frag_size was properly set to 4K, but value of 3K results in a\nnegative tailroom, because there is a non-zero page offset.\n\nWe are supposed to return -EINVAL and be done with it in such case, but due\nto tailroom being stored as an unsigned int, it is reported to be somewhere\nnear UINT_MAX, resulting in a tail being grown, even if the requested\noffset is too much (it is around 2K in the abovementioned test). This later\nleads to all kinds of unspecific calltraces.\n\n[ 7340.337579] xskxceiver[1440]: segfault at 1da718 ip 00007f4161aeac9d sp 00007f41615a6a00 error 6\n[ 7340.338040] xskxceiver[1441]: segfault at 7f410000000b ip 00000000004042b5 sp 00007f415bffecf0 error 4\n[ 7340.338179]  in libc.so.6[61c9d,7f4161aaf000+160000]\n[ 7340.339230]  in xskxceiver[42b5,400000+69000]\n[ 7340.340300]  likely on CPU 6 (core 0, socket 6)\n[ 7340.340302] Code: ff ff 01 e9 f4 fe ff ff 0f 1f 44 00 00 4c 39 f0 74 73 31 c0 ba 01 00 00 00 f0 0f b1 17 0f 85 ba 00 00 00 49 8b 87 88 00 00 00 \u0026lt;4c\u0026gt; 89 70 08 eb cc 0f 1f 44 00 00 48 8d bd f0 fe ff ff 89 85 ec fe\n[ 7340.340888]  likely on CPU 3 (core 0, socket 3)\n[ 7340.345088] Code: 00 00 00 ba 00 00 00 00 be 00 00 00 00 89 c7 e8 31 ca ff ff 89 45 ec 8b 45 ec 85 c0 78 07 b8 00 00 00 00 eb 46 e8 0b c8 ff ff \u0026lt;8b\u0026gt; 00 83 f8 69 74 24 e8 ff c7 ff ff 8b 00 83 f8 0b 74 18 e8 f3 c7\n[ 7340.404334] Oops: general protection fault, probably for non-canonical address 0x6d255010bdffc: 0000 [#1] SMP NOPTI\n[ 7340.405972] CPU: 7 UID: 0 PID: 1439 Comm: xskxceiver Not tainted 6.19.0-rc1+ #21 PREEMPT(lazy)\n[ 7340.408006] Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.17.0-5.fc42 04/01/2014\n[ 7340.409716] RIP: 0010:lookup_swap_cgroup_id+0x44/0x80\n[ 7340.410455] Code: 83 f8 1c 73 39 48 ba ff ff ff ff ff ff ff 03 48 8b 04 c5 20 55 fa bd 48 21 d1 48 89 ca 83 e1 01 48 d1 ea c1 e1 04 48 8d 04 90 \u0026lt;8b\u0026gt; 00 48 83 c4 10 d3 e8 c3 cc cc cc cc 31 c0 e9 98 b7 dd 00 48 89\n[ 7340.412787] RSP: 0018:ffffcc5c04f7f6d0 EFLAGS: 00010202\n[ 7340.413494] RAX: 0006d255010bdffc RBX: ffff891f477895a8 RCX: 0000000000000010\n[ 7340.414431] RDX: 0001c17e3fffffff RSI: 00fa070000000000 RDI: 000382fc7fffffff\n[ 7340.415354] RBP: 00fa070000000000 R08: ffffcc5c04f7f8f8 R09: ffffcc5c04f7f7d0\n[ 7340.416283] R10: ffff891f4c1a7000 R11: ffffcc5c04f7f9c8 R12: ffffcc5c04f7f7d0\n[ 7340.417218] R13: 03ffffffffffffff R14: 00fa06fffffffe00 R15: ffff891f47789500\n[ 7340.418229] FS:  0000000000000000(0000) GS:ffff891ffdfaa000(0000) knlGS:0000000000000000\n[ 7340.419489] CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033\n[ 7340.420286] CR2: 00007f415bfffd58 CR3: 0000000103f03002 CR4: 0000000000772ef0\n[ 7340.421237] PKRU: 55555554\n[ 7340.421623] Call Trace:\n[ 7340.421987]  \u0026lt;TASK\u0026gt;\n[ 7340.422309]  ? softleaf_from_pte+0x77/0xa0\n[ 7340.422855]  swap_pte_batch+0xa7/0x290\n[ 7340.423363]  zap_nonpresent_ptes.constprop.0.isra.0+0xd1/0x270\n[ 7340.424102]  zap_pte_range+0x281/0x580\n[ 7340.424607]  zap_pmd_range.isra.0+0xc9/0x240\n[ 7340.425177]  unmap_page_range+0x24d/0x420\n[ 7340.425714]  unmap_vmas+0xa1/0x180\n[ 7340.426185]  exit_mmap+0xe1/0x3b0\n[ 7340.426644]  __mmput+0x41/0x150\n[ 7340.427098]  exit_mm+0xb1/0x110\n[ 7340.427539]  do_exit+0x1b2/0x460\n[ 7340.427992]  do_group_exit+0x2d/0xc0\n[ 7340.428477]  get_signal+0x79d/0x7e0\n[ 7340.428957]  arch_do_signal_or_restart+0x34/0x100\n[ 7340.429571]  exit_to_user_mode_loop+0x8e/0x4c0\n[ 7340.430159]  do_syscall_64+0x188/\n---truncated---(CVE-2026-23343)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnetfilter: nft_set_pipapo: split gc into unlink and reclaim phase\n\nYiming Qian reports Use-after-free in the pipapo set type:\n  Under a large number of expired elements, commit-time GC can run for a very\n  long time in a non-preemptible context, triggering soft lockup warnings and\n  RCU stall reports (local denial of service).\n\nWe must split GC in an unlink and a reclaim phase.\n\nWe cannot queue elements for freeing until pointers have been swapped.\nExpired elements are still exposed to both the packet path and userspace\ndumpers via the live copy of the data structure.\n\ncall_rcu() does not protect us: dump operations or element lookups starting\nafter call_rcu has fired can still observe the free\u0026apos;d element, unless the\ncommit phase has made enough progress to swap the clone and live pointers\nbefore any new reader has picked up the old version.\n\nThis a similar approach as done recently for the rbtree backend in commit\n35f83a75529a (\u0026quot;netfilter: nft_set_rbtree: don\u0026apos;t gc elements on insert\u0026quot;).(CVE-2026-23351)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ncan: bcm: fix locking for bcm_op runtime updates\n\nCommit c2aba69d0c36 (\u0026quot;can: bcm: add locking for bcm_op runtime updates\u0026quot;)\nadded a locking for some variables that can be modified at runtime when\nupdating the sending bcm_op with a new TX_SETUP command in bcm_tx_setup().\n\nUsually the RX_SETUP only handles and filters incoming traffic with one\nexception: When the RX_RTR_FRAME flag is set a predefined CAN frame is\nsent when a specific RTR frame is received. Therefore the rx bcm_op uses\nbcm_can_tx() which uses the bcm_tx_lock that was only initialized in\nbcm_tx_setup(). Add the missing spin_lock_init() when allocating the\nbcm_op in bcm_rx_setup() to handle the RTR case properly.(CVE-2026-23362)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnet: usb: kalmia: validate USB endpoints\n\nThe kalmia driver should validate that the device it is probing has the\nproper number and types of USB endpoints it is expecting before it binds\nto it.  If a malicious device were to not have the same urbs the driver\nwill crash later on when it blindly accesses these endpoints.(CVE-2026-23365)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnet: phy: register phy led_triggers during probe to avoid AB-BA deadlock\n\nThere is an AB-BA deadlock when both LEDS_TRIGGER_NETDEV and\nLED_TRIGGER_PHY are enabled:\n\n[ 1362.049207] [\u0026lt;8054e4b8\u0026gt;] led_trigger_register+0x5c/0x1fc             \u0026lt;-- Trying to get lock \u0026quot;triggers_list_lock\u0026quot; via down_write(\u0026amp;triggers_list_lock);\n[ 1362.054536] [\u0026lt;80662830\u0026gt;] phy_led_triggers_register+0xd0/0x234\n[ 1362.060329] [\u0026lt;8065e200\u0026gt;] phy_attach_direct+0x33c/0x40c\n[ 1362.065489] [\u0026lt;80651fc4\u0026gt;] phylink_fwnode_phy_connect+0x15c/0x23c\n[ 1362.071480] [\u0026lt;8066ee18\u0026gt;] mtk_open+0x7c/0xba0\n[ 1362.075849] [\u0026lt;806d714c\u0026gt;] __dev_open+0x280/0x2b0\n[ 1362.080384] [\u0026lt;806d7668\u0026gt;] __dev_change_flags+0x244/0x24c\n[ 1362.085598] [\u0026lt;806d7698\u0026gt;] dev_change_flags+0x28/0x78\n[ 1362.090528] [\u0026lt;807150e4\u0026gt;] dev_ioctl+0x4c0/0x654                       \u0026lt;-- Hold lock \u0026quot;rtnl_mutex\u0026quot; by calling rtnl_lock();\n[ 1362.094985] [\u0026lt;80694360\u0026gt;] sock_ioctl+0x2f4/0x4e0\n[ 1362.099567] [\u0026lt;802e9c4c\u0026gt;] sys_ioctl+0x32c/0xd8c\n[ 1362.104022] [\u0026lt;80014504\u0026gt;] syscall_common+0x34/0x58\n\nHere LED_TRIGGER_PHY is registering LED triggers during phy_attach\nwhile holding RTNL and then taking triggers_list_lock.\n\n[ 1362.191101] [\u0026lt;806c2640\u0026gt;] register_netdevice_notifier+0x60/0x168      \u0026lt;-- Trying to get lock \u0026quot;rtnl_mutex\u0026quot; via rtnl_lock();\n[ 1362.197073] [\u0026lt;805504ac\u0026gt;] netdev_trig_activate+0x194/0x1e4\n[ 1362.202490] [\u0026lt;8054e28c\u0026gt;] led_trigger_set+0x1d4/0x360                 \u0026lt;-- Hold lock \u0026quot;triggers_list_lock\u0026quot; by down_read(\u0026amp;triggers_list_lock);\n[ 1362.207511] [\u0026lt;8054eb38\u0026gt;] led_trigger_write+0xd8/0x14c\n[ 1362.212566] [\u0026lt;80381d98\u0026gt;] sysfs_kf_bin_write+0x80/0xbc\n[ 1362.217688] [\u0026lt;8037fcd8\u0026gt;] kernfs_fop_write_iter+0x17c/0x28c\n[ 1362.223174] [\u0026lt;802cbd70\u0026gt;] vfs_write+0x21c/0x3c4\n[ 1362.227712] [\u0026lt;802cc0c4\u0026gt;] ksys_write+0x78/0x12c\n[ 1362.232164] [\u0026lt;80014504\u0026gt;] syscall_common+0x34/0x58\n\nHere LEDS_TRIGGER_NETDEV is being enabled on an LED. It first takes\ntriggers_list_lock and then RTNL. A classical AB-BA deadlock.\n\nphy_led_triggers_registers() does not require the RTNL, it does not\nmake any calls into the network stack which require protection. There\nis also no requirement the PHY has been attached to a MAC, the\ntriggers only make use of phydev state. This allows the call to\nphy_led_triggers_registers() to be placed elsewhere. PHY probe() and\nrelease() don\u0026apos;t hold RTNL, so solving the AB-BA deadlock.(CVE-2026-23368)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nsched/deadline: Fix missing ENQUEUE_REPLENISH during PI de-boosting\n\nRunning stress-ng --schedpolicy 0 on an RT kernel on a big machine\nmight lead to the following WARNINGs (edited).\n\n sched: DL de-boosted task PID 22725: REPLENISH flag missing\n\n WARNING: CPU: 93 PID: 0 at kernel/sched/deadline.c:239 dequeue_task_dl+0x15c/0x1f8\n ... (running_bw underflow)\n Call trace:\n  dequeue_task_dl+0x15c/0x1f8 (P)\n  dequeue_task+0x80/0x168\n  deactivate_task+0x24/0x50\n  push_dl_task+0x264/0x2e0\n  dl_task_timer+0x1b0/0x228\n  __hrtimer_run_queues+0x188/0x378\n  hrtimer_interrupt+0xfc/0x260\n  ...\n\nThe problem is that when a SCHED_DEADLINE task (lock holder) is\nchanged to a lower priority class via sched_setscheduler(), it may\nfail to properly inherit the parameters of potential DEADLINE donors\nif it didn\u0026apos;t already inherit them in the past (shorter deadline than\ndonor\u0026apos;s at that time). This might lead to bandwidth accounting\ncorruption, as enqueue_task_dl() won\u0026apos;t recognize the lock holder as\nboosted.\n\nThe scenario occurs when:\n1. A DEADLINE task (donor) blocks on a PI mutex held by another\n   DEADLINE task (holder), but the holder doesn\u0026apos;t inherit parameters\n   (e.g., it already has a shorter deadline)\n2. sched_setscheduler() changes the holder from DEADLINE to a lower\n   class while still holding the mutex\n3. The holder should now inherit DEADLINE parameters from the donor\n   and be enqueued with ENQUEUE_REPLENISH, but this doesn\u0026apos;t happen\n\nFix the issue by introducing __setscheduler_dl_pi(), which detects when\na DEADLINE (proper or boosted) task gets setscheduled to a lower\npriority class. In case, the function makes the task inherit DEADLINE\nparameters of the donoer (pi_se) and sets ENQUEUE_REPLENISH flag to\nensure proper bandwidth accounting during the next enqueue operation.(CVE-2026-23371)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nmm: thp: deny THP for files on anonymous inodes\n\nfile_thp_enabled() incorrectly allows THP for files on anonymous inodes\n(e.g. guest_memfd and secretmem). These files are created via\nalloc_file_pseudo(), which does not call get_write_access() and leaves\ninode-\u0026gt;i_writecount at 0. Combined with S_ISREG(inode-\u0026gt;i_mode) being\ntrue, they appear as read-only regular files when\nCONFIG_READ_ONLY_THP_FOR_FS is enabled, making them eligible for THP\ncollapse.\n\nAnonymous inodes can never pass the inode_is_open_for_write() check\nsince their i_writecount is never incremented through the normal VFS\nopen path. The right thing to do is to exclude them from THP eligibility\naltogether, since CONFIG_READ_ONLY_THP_FOR_FS was designed for real\nfilesystem files (e.g. shared libraries), not for pseudo-filesystem\ninodes.\n\nFor guest_memfd, this allows khugepaged and MADV_COLLAPSE to create\nlarge folios in the page cache via the collapse path, but the\nguest_memfd fault handler does not support large folios. This triggers\nWARN_ON_ONCE(folio_test_large(folio)) in kvm_gmem_fault_user_mapping().\n\nFor secretmem, collapse_file() tries to copy page contents through the\ndirect map, but secretmem pages are removed from the direct map. This\ncan result in a kernel crash:\n\n    BUG: unable to handle page fault for address: ffff88810284d000\n    RIP: 0010:memcpy_orig+0x16/0x130\n    Call Trace:\n     collapse_file\n     hpage_collapse_scan_file\n     madvise_collapse\n\nSecretmem is not affected by the crash on upstream as the memory failure\nrecovery handles the failed copy gracefully, but it still triggers\nconfusing false memory failure reports:\n\n    Memory failure: 0x106d96f: recovery action for clean unevictable\n    LRU page: Recovered\n\nCheck IS_ANON_FILE(inode) in file_thp_enabled() to deny THP for all\nanonymous inode files.(CVE-2026-23375)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnet: bridge: fix nd_tbl NULL dereference when IPv6 is disabled\n\nWhen booting with the \u0026apos;ipv6.disable=1\u0026apos; parameter, the nd_tbl is never\ninitialized because inet6_init() exits before ndisc_init() is called\nwhich initializes it. Then, if neigh_suppress is enabled and an ICMPv6\nNeighbor Discovery packet reaches the bridge, br_do_suppress_nd() will\ndereference ipv6_stub-\u0026gt;nd_tbl which is NULL, passing it to\nneigh_lookup(). This causes a kernel NULL pointer dereference.\n\n BUG: kernel NULL pointer dereference, address: 0000000000000268\n Oops: 0000 [#1] PREEMPT SMP NOPTI\n [...]\n RIP: 0010:neigh_lookup+0x16/0xe0\n [...]\n Call Trace:\n  \u0026lt;IRQ\u0026gt;\n  ? neigh_lookup+0x16/0xe0\n  br_do_suppress_nd+0x160/0x290 [bridge]\n  br_handle_frame_finish+0x500/0x620 [bridge]\n  br_handle_frame+0x353/0x440 [bridge]\n  __netif_receive_skb_core.constprop.0+0x298/0x1110\n  __netif_receive_skb_one_core+0x3d/0xa0\n  process_backlog+0xa0/0x140\n  __napi_poll+0x2c/0x170\n  net_rx_action+0x2c4/0x3a0\n  handle_softirqs+0xd0/0x270\n  do_softirq+0x3f/0x60\n\nFix this by replacing IS_ENABLED(IPV6) call with ipv6_mod_enabled() in\nthe callers. This is in essence disabling NS/NA suppression when IPv6 is\ndisabled.(CVE-2026-23381)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnetfilter: xt_CT: drop pending enqueued packets on template removal\n\nTemplates refer to objects that can go away while packets are sitting in\nnfqueue refer to:\n\n- helper, this can be an issue on module removal.\n- timeout policy, nfnetlink_cttimeout might remove it.\n\nThe use of templates with zone and event cache filter are safe, since\nthis just copies values.\n\nFlush these enqueued packets in case the template rule gets removed.(CVE-2026-23391)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnetfilter: nf_tables: release flowtable after rcu grace period on error\n\nCall synchronize_rcu() after unregistering the hooks from error path,\nsince a hook that already refers to this flowtable can be already\nregistered, exposing this flowtable to packet path and nfnetlink_hook\ncontrol plane.\n\nThis error path is rare, it should only happen by reaching the maximum\nnumber hooks or by failing to set up to hardware offload, just call\nsynchronize_rcu().\n\nThere is a check for already used device hooks by different flowtable\nthat could result in EEXIST at this late stage. The hook parser can be\nupdated to perform this check earlier to this error path really becomes\nrarely exercised.\n\nUncovered by KASAN reported as use-after-free from nfnetlink_hook path\nwhen dumping hooks.(CVE-2026-23392)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nbridge: cfm: Fix race condition in peer_mep deletion\n\nWhen a peer MEP is being deleted, cancel_delayed_work_sync() is called\non ccm_rx_dwork before freeing. However, br_cfm_frame_rx() runs in\nsoftirq context under rcu_read_lock (without RTNL) and can re-schedule\nccm_rx_dwork via ccm_rx_timer_start() between cancel_delayed_work_sync()\nreturning and kfree_rcu() being called.\n\nThe following is a simple race scenario:\n\n           cpu0                                     cpu1\n\nmep_delete_implementation()\n  cancel_delayed_work_sync(ccm_rx_dwork);\n                                           br_cfm_frame_rx()\n                                             // peer_mep still in hlist\n                                             if (peer_mep-\u0026gt;ccm_defect)\n                                               ccm_rx_timer_start()\n                                                 queue_delayed_work(ccm_rx_dwork)\n  hlist_del_rcu(\u0026amp;peer_mep-\u0026gt;head);\n  kfree_rcu(peer_mep, rcu);\n                                           ccm_rx_work_expired()\n                                             // on freed peer_mep\n\nTo prevent this, cancel_delayed_work_sync() is replaced with\ndisable_delayed_work_sync() in both peer MEP deletion paths, so\nthat subsequent queue_delayed_work() calls from br_cfm_frame_rx()\nare silently rejected.\n\nThe cc_peer_disable() helper retains cancel_delayed_work_sync()\nbecause it is also used for the CC enable/disable toggle path where\nthe work must remain re-schedulable.(CVE-2026-23393)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\naf_unix: Give up GC if MSG_PEEK intervened.\n\nIgor Ushakov reported that GC purged the receive queue of\nan alive socket due to a race with MSG_PEEK with a nice repro.\n\nThis is the exact same issue previously fixed by commit\ncbcf01128d0a (\u0026quot;af_unix: fix garbage collect vs MSG_PEEK\u0026quot;).\n\nAfter GC was replaced with the current algorithm, the cited\ncommit removed the locking dance in unix_peek_fds() and\nreintroduced the same issue.\n\nThe problem is that MSG_PEEK bumps a file refcount without\ninteracting with GC.\n\nConsider an SCC containing sk-A and sk-B, where sk-A is\nclose()d but can be recv()ed via sk-B.\n\nThe bad thing happens if sk-A is recv()ed with MSG_PEEK from\nsk-B and sk-B is close()d while GC is checking unix_vertex_dead()\nfor sk-A and sk-B.\n\n  GC thread                    User thread\n  ---------                    -----------\n  unix_vertex_dead(sk-A)\n  -\u0026gt; true   \u0026lt;------.\n                    \\\n                     `------   recv(sk-B, MSG_PEEK)\n              invalidate !!    -\u0026gt; sk-A\u0026apos;s file refcount : 1 -\u0026gt; 2\n\n                               close(sk-B)\n                               -\u0026gt; sk-B\u0026apos;s file refcount : 2 -\u0026gt; 1\n  unix_vertex_dead(sk-B)\n  -\u0026gt; true\n\nInitially, sk-A\u0026apos;s file refcount is 1 by the inflight fd in sk-B\nrecvq.  GC thinks sk-A is dead because the file refcount is the\nsame as the number of its inflight fds.\n\nHowever, sk-A\u0026apos;s file refcount is bumped silently by MSG_PEEK,\nwhich invalidates the previous evaluation.\n\nAt this moment, sk-B\u0026apos;s file refcount is 2; one by the open fd,\nand one by the inflight fd in sk-A.  The subsequent close()\nreleases one refcount by the former.\n\nFinally, GC incorrectly concludes that both sk-A and sk-B are dead.\n\nOne option is to restore the locking dance in unix_peek_fds(),\nbut we can resolve this more elegantly thanks to the new algorithm.\n\nThe point is that the issue does not occur without the subsequent\nclose() and we actually do not need to synchronise MSG_PEEK with\nthe dead SCC detection.\n\nWhen the issue occurs, close() and GC touch the same file refcount.\nIf GC sees the refcount being decremented by close(), it can just\ngive up garbage-collecting the SCC.\n\nTherefore, we only need to signal the race during MSG_PEEK with\na proper memory barrier to make it visible to the GC.\n\nLet\u0026apos;s use seqcount_t to notify GC when MSG_PEEK occurs and let\nit defer the SCC to the next run.\n\nThis way no locking is needed on the MSG_PEEK side, and we can\navoid imposing a penalty on every MSG_PEEK unnecessarily.\n\nNote that we can retry within unix_scc_dead() if MSG_PEEK is\ndetected, but we do not do so to avoid hung task splat from\nabusive MSG_PEEK calls.(CVE-2026-23394)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nBluetooth: L2CAP: Fix accepting multiple L2CAP_ECRED_CONN_REQ\n\nCurrently the code attempts to accept requests regardless of the\ncommand identifier which may cause multiple requests to be marked\nas pending (FLAG_DEFER_SETUP) which can cause more than\nL2CAP_ECRED_MAX_CID(5) to be allocated in l2cap_ecred_rsp_defer\ncausing an overflow.\n\nThe spec is quite clear that the same identifier shall not be used on\nsubsequent requests:\n\n\u0026apos;Within each signaling channel a different Identifier shall be used\nfor each successive request or indication.\u0026apos;\nhttps://www.bluetooth.com/wp-content/uploads/Files/Specification/HTML/Core-62/out/en/host/logical-link-control-and-adaptation-protocol-specification.html#UUID-32a25a06-4aa4-c6c7-77c5-dcfe3682355d\n\nSo this attempts to check if there are any channels pending with the\nsame identifier and rejects if any are found.(CVE-2026-23395)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnfnetlink_osf: validate individual option lengths in fingerprints\n\nnfnl_osf_add_callback() validates opt_num bounds and string\nNUL-termination but does not check individual option length fields.\nA zero-length option causes nf_osf_match_one() to enter the option\nmatching loop even when foptsize sums to zero, which matches packets\nwith no TCP options where ctx-\u0026gt;optp is NULL:\n\n Oops: general protection fault\n KASAN: null-ptr-deref in range [0x0000000000000000-0x0000000000000007]\n RIP: 0010:nf_osf_match_one (net/netfilter/nfnetlink_osf.c:98)\n Call Trace:\n  nf_osf_match (net/netfilter/nfnetlink_osf.c:227)\n  xt_osf_match_packet (net/netfilter/xt_osf.c:32)\n  ipt_do_table (net/ipv4/netfilter/ip_tables.c:293)\n  nf_hook_slow (net/netfilter/core.c:623)\n  ip_local_deliver (net/ipv4/ip_input.c:262)\n  ip_rcv (net/ipv4/ip_input.c:573)\n\nAdditionally, an MSS option (kind=2) with length \u0026lt; 4 causes\nout-of-bounds reads when nf_osf_match_one() unconditionally accesses\noptp[2] and optp[3] for MSS value extraction.  While RFC 9293\nsection 3.2 specifies that the MSS option is always exactly 4\nbytes (Kind=2, Length=4), the check uses \u0026quot;\u0026lt; 4\u0026quot; rather than\n\u0026quot;!= 4\u0026quot; because lengths greater than 4 do not cause memory\nsafety issues -- the buffer is guaranteed to be at least\nfoptsize bytes by the ctx-\u0026gt;optsize == foptsize check.\n\nReject fingerprints where any option has zero length, or where an MSS\noption has length less than 4, at add time rather than trusting these\nvalues in the packet matching hot path.(CVE-2026-23397)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnf_tables: nft_dynset: fix possible stateful expression memleak in error path\n\nIf cloning the second stateful expression in the element via GFP_ATOMIC\nfails, then the first stateful expression remains in place without being\nreleased.\n\n   unreferenced object (percpu) 0x607b97e9cab8 (size 16):\n     comm \u0026quot;softirq\u0026quot;, pid 0, jiffies 4294931867\n     hex dump (first 16 bytes on cpu 3):\n       00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00\n     backtrace (crc 0):\n       pcpu_alloc_noprof+0x453/0xd80\n       nft_counter_clone+0x9c/0x190 [nf_tables]\n       nft_expr_clone+0x8f/0x1b0 [nf_tables]\n       nft_dynset_new+0x2cb/0x5f0 [nf_tables]\n       nft_rhash_update+0x236/0x11c0 [nf_tables]\n       nft_dynset_eval+0x11f/0x670 [nf_tables]\n       nft_do_chain+0x253/0x1700 [nf_tables]\n       nft_do_chain_ipv4+0x18d/0x270 [nf_tables]\n       nf_hook_slow+0xaa/0x1e0\n       ip_local_deliver+0x209/0x330(CVE-2026-23399)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nKVM: x86/mmu: Drop/zap existing present SPTE even when creating an MMIO SPTE\n\nWhen installing an emulated MMIO SPTE, do so *after* dropping/zapping the\nexisting SPTE (if it\u0026apos;s shadow-present).  While commit a54aa15c6bda3 was\nright about it being impossible to convert a shadow-present SPTE to an\nMMIO SPTE due to a _guest_ write, it failed to account for writes to guest\nmemory that are outside the scope of KVM.\n\nE.g. if host userspace modifies a shadowed gPTE to switch from a memslot\nto emulted MMIO and then the guest hits a relevant page fault, KVM will\ninstall the MMIO SPTE without first zapping the shadow-present SPTE.\n\n  ------------[ cut here ]------------\n  is_shadow_present_pte(*sptep)\n  WARNING: arch/x86/kvm/mmu/mmu.c:484 at mark_mmio_spte+0xb2/0xc0 [kvm], CPU#0: vmx_ept_stale_r/4292\n  Modules linked in: kvm_intel kvm irqbypass\n  CPU: 0 UID: 1000 PID: 4292 Comm: vmx_ept_stale_r Not tainted 7.0.0-rc2-eafebd2d2ab0-sink-vm #319 PREEMPT\n  Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 0.0.0 02/06/2015\n  RIP: 0010:mark_mmio_spte+0xb2/0xc0 [kvm]\n  Call Trace:\n   \u0026lt;TASK\u0026gt;\n   mmu_set_spte+0x237/0x440 [kvm]\n   ept_page_fault+0x535/0x7f0 [kvm]\n   kvm_mmu_do_page_fault+0xee/0x1f0 [kvm]\n   kvm_mmu_page_fault+0x8d/0x620 [kvm]\n   vmx_handle_exit+0x18c/0x5a0 [kvm_intel]\n   kvm_arch_vcpu_ioctl_run+0xc55/0x1c20 [kvm]\n   kvm_vcpu_ioctl+0x2d5/0x980 [kvm]\n   __x64_sys_ioctl+0x8a/0xd0\n   do_syscall_64+0xb5/0x730\n   entry_SYSCALL_64_after_hwframe+0x4b/0x53\n  RIP: 0033:0x47fa3f\n   \u0026lt;/TASK\u0026gt;\n  ---[ end trace 0000000000000000 ]---(CVE-2026-23401)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\napparmor: fix memory leak in verify_header\n\nThe function sets `*ns = NULL` on every call, leaking the namespace\nstring allocated in previous iterations when multiple profiles are\nunpacked. This also breaks namespace consistency checking since *ns\nis always NULL when the comparison is made.\n\nRemove the incorrect assignment.\nThe caller (aa_unpack) initializes *ns to NULL once before the loop,\nwhich is sufficient.(CVE-2026-23403)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\napparmor: replace recursive profile removal with iterative approach\n\nThe profile removal code uses recursion when removing nested profiles,\nwhich can lead to kernel stack exhaustion and system crashes.\n\nReproducer:\n  $ pf=\u0026apos;a\u0026apos;; for ((i=0; i\u0026lt;1024; i++)); do\n      echo -e \u0026quot;profile $pf { \\n }\u0026quot; | apparmor_parser -K -a;\n      pf=\u0026quot;$pf//x\u0026quot;;\n  done\n  $ echo -n a \u0026gt; /sys/kernel/security/apparmor/.remove\n\nReplace the recursive __aa_profile_list_release() approach with an\niterative approach in __remove_profile(). The function repeatedly\nfinds and removes leaf profiles until the entire subtree is removed,\nmaintaining the same removal semantic without recursion.(CVE-2026-23404)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\napparmor: fix: limit the number of levels of policy namespaces\n\nCurrently the number of policy namespaces is not bounded relying on\nthe user namespace limit. However policy namespaces aren\u0026apos;t strictly\ntied to user namespaces and it is possible to create them and nest\nthem arbitrarily deep which can be used to exhaust system resource.\n\nHard cap policy namespaces to the same depth as user namespaces.(CVE-2026-23405)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\napparmor: Fix double free of ns_name in aa_replace_profiles()\n\nif ns_name is NULL after\n1071         error = aa_unpack(udata, \u0026amp;lh, \u0026amp;ns_name);\n\nand if ent-\u0026gt;ns_name contains an ns_name in\n1089                 } else if (ent-\u0026gt;ns_name) {\n\nthen ns_name is assigned the ent-\u0026gt;ns_name\n1095                         ns_name = ent-\u0026gt;ns_name;\n\nhowever ent-\u0026gt;ns_name is freed at\n1262                 aa_load_ent_free(ent);\n\nand then again when freeing ns_name at\n1270         kfree(ns_name);\n\nFix this by NULLing out ent-\u0026gt;ns_name after it is transferred to ns_name\n\n\u0026quot;)(CVE-2026-23408)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\napparmor: fix differential encoding verification\n\nDifferential encoding allows loops to be created if it is abused. To\nprevent this the unpack should verify that a diff-encode chain\nterminates.\n\nUnfortunately the differential encode verification had two bugs.\n\n1. it conflated states that had gone through check and already been\n   marked, with states that were currently being checked and marked.\n   This means that loops in the current chain being verified are treated\n   as a chain that has already been verified.\n\n2. the order bailout on already checked states compared current chain\n   check iterators j,k instead of using the outer loop iterator i.\n   Meaning a step backwards in states in the current chain verification\n   was being mistaken for moving to an already verified state.\n\nMove to a double mark scheme where already verified states get a\ndifferent mark, than the current chain being kept. This enables us\nto also drop the backwards verification check that was the cause of\nthe second error as any already verified state is already marked.(CVE-2026-23409)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\napparmor: fix race on rawdata dereference\n\nThere is a race condition that leads to a use-after-free situation:\nbecause the rawdata inodes are not refcounted, an attacker can start\nopen()ing one of the rawdata files, and at the same time remove the\nlast reference to this rawdata (by removing the corresponding profile,\nfor example), which frees its struct aa_loaddata; as a result, when\nseq_rawdata_open() is reached, i_private is a dangling pointer and\nfreed memory is accessed.\n\nThe rawdata inodes weren\u0026apos;t refcounted to avoid a circular refcount and\nwere supposed to be held by the profile rawdata reference.  However\nduring profile removal there is a window where the vfs and profile\ndestruction race, resulting in the use after free.\n\nFix this by moving to a double refcount scheme. Where the profile\nrefcount on rawdata is used to break the circular dependency. Allowing\nfor freeing of the rawdata once all inode references to the rawdata\nare put.(CVE-2026-23410)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\napparmor: fix race between freeing data and fs accessing it\n\nAppArmor was putting the reference to i_private data on its end after\nremoving the original entry from the file system. However the inode\ncan aand does live beyond that point and it is possible that some of\nthe fs call back functions will be invoked after the reference has\nbeen put, which results in a race between freeing the data and\naccessing it through the fs.\n\nWhile the rawdata/loaddata is the most likely candidate to fail the\nrace, as it has the fewest references. If properly crafted it might be\npossible to trigger a race for the other types stored in i_private.\n\nFix this by moving the put of i_private referenced data to the correct\nplace which is during inode eviction.(CVE-2026-23411)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nclsact: Fix use-after-free in init/destroy rollback asymmetry\n\nFix a use-after-free in the clsact qdisc upon init/destroy rollback asymmetry.\nThe latter is achieved by first fully initializing a clsact instance, and\nthen in a second step having a replacement failure for the new clsact qdisc\ninstance. clsact_init() initializes ingress first and then takes care of the\negress part. This can fail midway, for example, via tcf_block_get_ext(). Upon\nfailure, the kernel will trigger the clsact_destroy() callback.\n\nCommit 1cb6f0bae504 (\u0026quot;bpf: Fix too early release of tcx_entry\u0026quot;) details the\nway how the transition is happening. If tcf_block_get_ext on the q-\u0026gt;ingress_block\nends up failing, we took the tcx_miniq_inc reference count on the ingress\nside, but not yet on the egress side. clsact_destroy() tests whether the\n{ingress,egress}_entry was non-NULL. However, even in midway failure on the\nreplacement, both are in fact non-NULL with a valid egress_entry from the\nprevious clsact instance.\n\nWhat we really need to test for is whether the qdisc instance-specific ingress\nor egress side previously got initialized. This adds a small helper for checking\nthe miniq initialization called mini_qdisc_pair_inited, and utilizes that upon\nclsact_destroy() in order to fix the use-after-free scenario. Convert the\ningress_destroy() side as well so both are consistent to each other.(CVE-2026-23413)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ntls: Purge async_hold in tls_decrypt_async_wait()\n\nThe async_hold queue pins encrypted input skbs while\nthe AEAD engine references their scatterlist data. Once\ntls_decrypt_async_wait() returns, every AEAD operation\nhas completed and the engine no longer references those\nskbs, so they can be freed unconditionally.\n\nA subsequent patch adds batch async decryption to\ntls_sw_read_sock(), introducing a new call site that\nmust drain pending AEAD operations and release held\nskbs. Move __skb_queue_purge(\u0026amp;ctx-\u0026gt;async_hold) into\ntls_decrypt_async_wait() so the purge is centralized\nand every caller -- recvmsg\u0026apos;s drain path, the -EBUSY\nfallback in tls_do_decryption(), and the new read_sock\nbatch path -- releases held skbs on synchronization\nwithout each site managing the purge independently.\n\nThis fixes a leak when tls_strp_msg_hold() fails part-way through,\nafter having added some cloned skbs to the async_hold\nqueue. tls_decrypt_sg() will then call tls_decrypt_async_wait() to\nprocess all pending decrypts, and drop back to synchronous mode, but\ntls_sw_recvmsg() only flushes the async_hold queue when one record has\nbeen processed in \u0026quot;fully-async\u0026quot; mode, which may not be the case here.\n\n[(CVE-2026-23414)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nxen/privcmd: restrict usage in unprivileged domU\n\nThe Xen privcmd driver allows to issue arbitrary hypercalls from\nuser space processes. This is normally no problem, as access is\nusually limited to root and the hypervisor will deny any hypercalls\naffecting other domains.\n\nIn case the guest is booted using secure boot, however, the privcmd\ndriver would be enabling a root user process to modify e.g. kernel\nmemory contents, thus breaking the secure boot feature.\n\nThe only known case where an unprivileged domU is really needing to\nuse the privcmd driver is the case when it is acting as the device\nmodel for another guest. In this case all hypercalls issued via the\nprivcmd driver will target that other guest.\n\nFortunately the privcmd driver can already be locked down to allow\nonly hypercalls targeting a specific domain, but this mode can be\nactivated from user land only today.\n\nThe target domain can be obtained from Xenstore, so when not running\nin dom0 restrict the privcmd driver to that target domain from the\nbeginning, resolving the potential problem of breaking secure boot.\n\nThis is XSA-482\n\n---\nV2:\n- defer reading from Xenstore if Xenstore isn\u0026apos;t ready yet (Jan Beulich)\n- wait in open() if target domain isn\u0026apos;t known yet\n- issue message in case no target domain found (Jan Beulich)(CVE-2026-31788)","status":"published","published":"2026-04-11T11:10:52Z","modified":"2026-08-18T01:19:47.495909169Z","cvss":[{"version":"3.1","score":9.8,"vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H","level":"critical"}],"updated_at":"2026-11-02T15:52:46.087701Z"},{"id":"OESA-2026-1864","title":"kernel security update","description":"The Linux Kernel, the operating system core itself.\r\n\r\nSecurity Fix(es):\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nf2fs: fix to detect potential corrupted nid in free_nid_list\n\nAs reported, on-disk footer.ino and footer.nid is the same and\nout-of-range, let\u0026apos;s add sanity check on f2fs_alloc_nid() to detect\nany potential corruption in free_nid_list.(CVE-2025-68315)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nntfs3: Fix uninit buffer allocated by __getname()\n\nFix uninit errors caused after buffer allocation given to \u0026apos;de\u0026apos;; by\ninitializing the buffer with zeroes. The fix was found by using KMSAN.(CVE-2025-68727)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnetfilter: nf_tables: fix use-after-free in nf_tables_addchain()\n\nnf_tables_addchain() publishes the chain to table-\u0026gt;chains via\nlist_add_tail_rcu() (in nft_chain_add()) before registering hooks.\nIf nf_tables_register_hook() then fails, the error path calls\nnft_chain_del() (list_del_rcu()) followed by nf_tables_chain_destroy()\nwith no RCU grace period in between.\n\nThis creates two use-after-free conditions:\n\n 1) Control-plane: nf_tables_dump_chains() traverses table-\u0026gt;chains\n    under rcu_read_lock(). A concurrent dump can still be walking\n    the chain when the error path frees it.\n\n 2) Packet path: for NFPROTO_INET, nf_register_net_hook() briefly\n    installs the IPv4 hook before IPv6 registration fails.  Packets\n    entering nft_do_chain() via the transient IPv4 hook can still be\n    dereferencing chain-\u0026gt;blob_gen_X when the error path frees the\n    chain.\n\nAdd synchronize_rcu() between nft_chain_del() and the chain destroy\nso that all RCU readers -- both dump threads and in-flight packet\nevaluation -- have finished before the chain is freed.(CVE-2026-23231)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ntls: Fix race condition in tls_sw_cancel_work_tx()\n\nThis issue was discovered during a code audit.\n\nAfter cancel_delayed_work_sync() is called from tls_sk_proto_close(),\ntx_work_handler() can still be scheduled from paths such as the\nDelayed ACK handler or ksoftirqd.\nAs a result, the tx_work_handler() worker may dereference a freed\nTLS object.\n\nThe following is a simple race scenario:\n\n          cpu0                         cpu1\n\ntls_sk_proto_close()\n  tls_sw_cancel_work_tx()\n                                 tls_write_space()\n                                   tls_sw_write_space()\n                                     if (!test_and_set_bit(BIT_TX_SCHEDULED, \u0026amp;tx_ctx-\u0026gt;tx_bitmask))\n    set_bit(BIT_TX_SCHEDULED, \u0026amp;ctx-\u0026gt;tx_bitmask);\n    cancel_delayed_work_sync(\u0026amp;ctx-\u0026gt;tx_work.work);\n                                     schedule_delayed_work(\u0026amp;tx_ctx-\u0026gt;tx_work.work, 0);\n\nTo prevent this race condition, cancel_delayed_work_sync() is\nreplaced with disable_delayed_work_sync().(CVE-2026-23240)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnet/sched: act_gate: snapshot parameters with RCU on replace\n\nThe gate action can be replaced while the hrtimer callback or dump path is\nwalking the schedule list.\n\nConvert the parameters to an RCU-protected snapshot and swap updates under\ntcf_lock, freeing the previous snapshot via call_rcu(). When REPLACE omits\nthe entry list, preserve the existing schedule so the effective state is\nunchanged.(CVE-2026-23245)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnet: gro: fix outer network offset\n\nThe udp GRO complete stage assumes that all the packets inserted the RX\nhave the `encapsulation` flag zeroed. Such assumption is not true, as a\nfew H/W NICs can set such flag when H/W offloading the checksum for\nan UDP encapsulated traffic, the tun driver can inject GSO packets with\nUDP encapsulation and the problematic layout can also be created via\na veth based setup.\n\nDue to the above, in the problematic scenarios, udp4_gro_complete() uses\nthe wrong network offset (inner instead of outer) to compute the outer\nUDP header pseudo checksum, leading to csum validation errors later on\nin packet processing.\n\nAddress the issue always clearing the encapsulation flag at GRO completion\ntime. Such flag will be set again as needed for encapsulated packets by\nudp_gro_complete().(CVE-2026-23254)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnet: add proper RCU protection to /proc/net/ptype\n\nYin Fengwei reported an RCU stall in ptype_seq_show() and provided\na patch.\n\nReal issue is that ptype_seq_next() and ptype_seq_show() violate\nRCU rules.\n\nptype_seq_show() runs under rcu_read_lock(), and reads pt-\u0026gt;dev\nto get device name without any barrier.\n\nAt the same time, concurrent writers can remove a packet_type structure\n(which is correctly freed after an RCU grace period) and clear pt-\u0026gt;dev\nwithout an RCU grace period.\n\nDefine ptype_iter_state to carry a dev pointer along seq_net_private:\n\nstruct ptype_iter_state {\n\tstruct seq_net_private\tp;\n\tstruct net_device\t*dev; // added in this patch\n};\n\nWe need to record the device pointer in ptype_get_idx() and\nptype_seq_next() so that ptype_seq_show() is safe against\nconcurrent pt-\u0026gt;dev changes.\n\nWe also need to add full RCU protection in ptype_seq_next().\n(Missing READ_ONCE() when reading list.next values)\n\nMany thanks to Dong Chenchen for providing a repro.(CVE-2026-23255)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnet/sched: Only allow act_ct to bind to clsact/ingress qdiscs and shared blocks\n\nAs Paolo said earlier [1]:\n\n\u0026quot;Since the blamed commit below, classify can return TC_ACT_CONSUMED while\nthe current skb being held by the defragmentation engine. As reported by\nGangMin Kim, if such packet is that may cause a UaF when the defrag engine\nlater on tries to tuch again such packet.\u0026quot;\n\nact_ct was never meant to be used in the egress path, however some users\nare attaching it to egress today [2]. Attempting to reach a middle\nground, we noticed that, while most qdiscs are not handling\nTC_ACT_CONSUMED, clsact/ingress qdiscs are. With that in mind, we\naddress the issue by only allowing act_ct to bind to clsact/ingress\nqdiscs and shared blocks. That way it\u0026apos;s still possible to attach act_ct to\negress (albeit only with clsact).\n\n[1] https://lore.kernel.org/netdev/674b8cbfc385c6f37fb29a1de08d8fe5c2b0fbee.1771321118.git.pabeni@redhat.com/\n[2] https://lore.kernel.org/netdev/(CVE-2026-23270)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnetfilter: xt_IDLETIMER: reject rev0 reuse of ALARM timer labels\n\nIDLETIMER revision 0 rules reuse existing timers by label and always call\nmod_timer() on timer-\u0026gt;timer.\n\nIf the label was created first by revision 1 with XT_IDLETIMER_ALARM,\nthe object uses alarm timer semantics and timer-\u0026gt;timer is never initialized.\nReusing that object from revision 0 causes mod_timer() on an uninitialized\ntimer_list, triggering debugobjects warnings and possible panic when\npanic_on_warn=1.\n\nFix this by rejecting revision 0 rule insertion when an existing timer with\nthe same label is of ALARM type.(CVE-2026-23274)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnet: add xmit recursion limit to tunnel xmit functions\n\nTunnel xmit functions (iptunnel_xmit, ip6tunnel_xmit) lack their own\nrecursion limit. When a bond device in broadcast mode has GRE tap\ninterfaces as slaves, and those GRE tunnels route back through the\nbond, multicast/broadcast traffic triggers infinite recursion between\nbond_xmit_broadcast() and ip_tunnel_xmit()/ip6_tnl_xmit(), causing\nkernel stack overflow.\n\nThe existing XMIT_RECURSION_LIMIT (8) in the no-qdisc path is not\nsufficient because tunnel recursion involves route lookups and full IP\noutput, consuming much more stack per level. Use a lower limit of 4\n(IP_TUNNEL_RECURSION_LIMIT) to prevent overflow.\n\nAdd recursion detection using dev_xmit_recursion helpers directly in\niptunnel_xmit() and ip6tunnel_xmit() to cover all IPv4/IPv6 tunnel\npaths including UDP encapsulated tunnels (VXLAN, Geneve, etc.).\n\nMove dev_xmit_recursion helpers from net/core/dev.h to public header\ninclude/linux/netdevice.h so they can be used by tunnel code.\n\n BUG: KASAN: stack-out-of-bounds in blake2s.constprop.0+0xe7/0x160\n Write of size 32 at addr ffff88810033fed0 by task kworker/0:1/11\n Workqueue: mld mld_ifc_work\n Call Trace:\n  \u0026lt;TASK\u0026gt;\n  __build_flow_key.constprop.0 (net/ipv4/route.c:515)\n  ip_rt_update_pmtu (net/ipv4/route.c:1073)\n  iptunnel_xmit (net/ipv4/ip_tunnel_core.c:84)\n  ip_tunnel_xmit (net/ipv4/ip_tunnel.c:847)\n  gre_tap_xmit (net/ipv4/ip_gre.c:779)\n  dev_hard_start_xmit (net/core/dev.c:3887)\n  sch_direct_xmit (net/sched/sch_generic.c:347)\n  __dev_queue_xmit (net/core/dev.c:4802)\n  bond_dev_queue_xmit (drivers/net/bonding/bond_main.c:312)\n  bond_xmit_broadcast (drivers/net/bonding/bond_main.c:5279)\n  bond_start_xmit (drivers/net/bonding/bond_main.c:5530)\n  dev_hard_start_xmit (net/core/dev.c:3887)\n  __dev_queue_xmit (net/core/dev.c:4841)\n  ip_finish_output2 (net/ipv4/ip_output.c:237)\n  ip_output (net/ipv4/ip_output.c:438)\n  iptunnel_xmit (net/ipv4/ip_tunnel_core.c:86)\n  gre_tap_xmit (net/ipv4/ip_gre.c:779)\n  dev_hard_start_xmit (net/core/dev.c:3887)\n  sch_direct_xmit (net/sched/sch_generic.c:347)\n  __dev_queue_xmit (net/core/dev.c:4802)\n  bond_dev_queue_xmit (drivers/net/bonding/bond_main.c:312)\n  bond_xmit_broadcast (drivers/net/bonding/bond_main.c:5279)\n  bond_start_xmit (drivers/net/bonding/bond_main.c:5530)\n  dev_hard_start_xmit (net/core/dev.c:3887)\n  __dev_queue_xmit (net/core/dev.c:4841)\n  ip_finish_output2 (net/ipv4/ip_output.c:237)\n  ip_output (net/ipv4/ip_output.c:438)\n  iptunnel_xmit (net/ipv4/ip_tunnel_core.c:86)\n  ip_tunnel_xmit (net/ipv4/ip_tunnel.c:847)\n  gre_tap_xmit (net/ipv4/ip_gre.c:779)\n  dev_hard_start_xmit (net/core/dev.c:3887)\n  sch_direct_xmit (net/sched/sch_generic.c:347)\n  __dev_queue_xmit (net/core/dev.c:4802)\n  bond_dev_queue_xmit (drivers/net/bonding/bond_main.c:312)\n  bond_xmit_broadcast (drivers/net/bonding/bond_main.c:5279)\n  bond_start_xmit (drivers/net/bonding/bond_main.c:5530)\n  dev_hard_start_xmit (net/core/dev.c:3887)\n  __dev_queue_xmit (net/core/dev.c:4841)\n  mld_sendpack\n  mld_ifc_work\n  process_one_work\n  worker_thread\n  \u0026lt;/TASK\u0026gt;(CVE-2026-23276)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnet/sched: teql: fix NULL pointer dereference in iptunnel_xmit on TEQL slave xmit\n\nteql_master_xmit() calls netdev_start_xmit(skb, slave) to transmit\nthrough slave devices, but does not update skb-\u0026gt;dev to the slave device\nbeforehand.\n\nWhen a gretap tunnel is a TEQL slave, the transmit path reaches\niptunnel_xmit() which saves dev = skb-\u0026gt;dev (still pointing to teql0\nmaster) and later calls iptunnel_xmit_stats(dev, pkt_len). This\nfunction does:\n\n    get_cpu_ptr(dev-\u0026gt;tstats)\n\nSince teql_master_setup() does not set dev-\u0026gt;pcpu_stat_type to\nNETDEV_PCPU_STAT_TSTATS, the core network stack never allocates tstats\nfor teql0, so dev-\u0026gt;tstats is NULL. get_cpu_ptr(NULL) computes\nNULL + __per_cpu_offset[cpu], resulting in a page fault.\n\n BUG: unable to handle page fault for address: ffff8880e6659018\n #PF: supervisor write access in kernel mode\n #PF: error_code(0x0002) - not-present page\n PGD 68bc067 P4D 68bc067 PUD 0\n Oops: Oops: 0002 [#1] SMP KASAN PTI\n RIP: 0010:iptunnel_xmit (./include/net/ip_tunnels.h:664 net/ipv4/ip_tunnel_core.c:89)\n Call Trace:\n  \u0026lt;TASK\u0026gt;\n  ip_tunnel_xmit (net/ipv4/ip_tunnel.c:847)\n  __gre_xmit (net/ipv4/ip_gre.c:478)\n  gre_tap_xmit (net/ipv4/ip_gre.c:779)\n  teql_master_xmit (net/sched/sch_teql.c:319)\n  dev_hard_start_xmit (net/core/dev.c:3887)\n  sch_direct_xmit (net/sched/sch_generic.c:347)\n  __dev_queue_xmit (net/core/dev.c:4802)\n  neigh_direct_output (net/core/neighbour.c:1660)\n  ip_finish_output2 (net/ipv4/ip_output.c:237)\n  __ip_finish_output.part.0 (net/ipv4/ip_output.c:315)\n  ip_mc_output (net/ipv4/ip_output.c:369)\n  ip_send_skb (net/ipv4/ip_output.c:1508)\n  udp_send_skb (net/ipv4/udp.c:1195)\n  udp_sendmsg (net/ipv4/udp.c:1485)\n  inet_sendmsg (net/ipv4/af_inet.c:859)\n  __sys_sendto (net/socket.c:2206)\n\nFix this by setting skb-\u0026gt;dev = slave before calling\nnetdev_start_xmit(), so that tunnel xmit functions see the correct\nslave device with properly allocated tstats.(CVE-2026-23277)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnetfilter: nf_tables: always walk all pending catchall elements\n\nDuring transaction processing we might have more than one catchall element:\n1 live catchall element and 1 pending element that is coming as part of the\nnew batch.\n\nIf the map holding the catchall elements is also going away, its\nrequired to toggle all catchall elements and not just the first viable\ncandidate.\n\nOtherwise, we get:\n WARNING: ./include/net/netfilter/nf_tables.h:1281 at nft_data_release+0xb7/0xe0 [nf_tables], CPU#2: nft/1404\n RIP: 0010:nft_data_release+0xb7/0xe0 [nf_tables]\n [..]\n __nft_set_elem_destroy+0x106/0x380 [nf_tables]\n nf_tables_abort_release+0x348/0x8d0 [nf_tables]\n nf_tables_abort+0xcf2/0x3ac0 [nf_tables]\n nfnetlink_rcv_batch+0x9c9/0x20e0 [..](CVE-2026-23278)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnet: vxlan: fix nd_tbl NULL dereference when IPv6 is disabled\n\nWhen booting with the \u0026apos;ipv6.disable=1\u0026apos; parameter, the nd_tbl is never\ninitialized because inet6_init() exits before ndisc_init() is called\nwhich initializes it. If an IPv6 packet is injected into the interface,\nroute_shortcircuit() is called and a NULL pointer dereference happens on\nneigh_lookup().\n\n BUG: kernel NULL pointer dereference, address: 0000000000000380\n Oops: Oops: 0000 [#1] SMP NOPTI\n [...]\n RIP: 0010:neigh_lookup+0x20/0x270\n [...]\n Call Trace:\n  \u0026lt;TASK\u0026gt;\n  vxlan_xmit+0x638/0x1ef0 [vxlan]\n  dev_hard_start_xmit+0x9e/0x2e0\n  __dev_queue_xmit+0xbee/0x14e0\n  packet_sendmsg+0x116f/0x1930\n  __sys_sendto+0x1f5/0x200\n  __x64_sys_sendto+0x24/0x30\n  do_syscall_64+0x12f/0x1590\n  entry_SYSCALL_64_after_hwframe+0x76/0x7e\n\nFix this by adding an early check on route_shortcircuit() when protocol\nis ETH_P_IPV6. Note that ipv6_mod_enabled() cannot be used here because\nVXLAN can be built-in even when IPv6 is built as a module.(CVE-2026-23293)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnet: ipv6: fix panic when IPv4 route references loopback IPv6 nexthop\n\nWhen a standalone IPv6 nexthop object is created with a loopback device\n(e.g., \u0026quot;ip -6 nexthop add id 100 dev lo\u0026quot;), fib6_nh_init() misclassifies\nit as a reject route. This is because nexthop objects have no destination\nprefix (fc_dst=::), causing fib6_is_reject() to match any loopback\nnexthop. The reject path skips fib_nh_common_init(), leaving\nnhc_pcpu_rth_output unallocated. If an IPv4 route later references this\nnexthop, __mkroute_output() dereferences NULL nhc_pcpu_rth_output and\npanics.\n\nSimplify the check in fib6_nh_init() to only match explicit reject\nroutes (RTF_REJECT) instead of using fib6_is_reject(). The loopback\npromotion heuristic in fib6_is_reject() is handled separately by\nip6_route_info_create_nh(). After this change, the three cases behave\nas follows:\n\n1. Explicit reject route (\u0026quot;ip -6 route add unreachable 2001:db8::/64\u0026quot;):\n   RTF_REJECT is set, enters reject path, skips fib_nh_common_init().\n   No behavior change.\n\n2. Implicit loopback reject route (\u0026quot;ip -6 route add 2001:db8::/32 dev lo\u0026quot;):\n   RTF_REJECT is not set, takes normal path, fib_nh_common_init() is\n   called. ip6_route_info_create_nh() still promotes it to reject\n   afterward. nhc_pcpu_rth_output is allocated but unused, which is\n   harmless.\n\n3. Standalone nexthop object (\u0026quot;ip -6 nexthop add id 100 dev lo\u0026quot;):\n   RTF_REJECT is not set, takes normal path, fib_nh_common_init() is\n   called. nhc_pcpu_rth_output is properly allocated, fixing the crash\n   when IPv4 routes reference this nexthop.(CVE-2026-23300)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnet: annotate data-races around sk-\u0026gt;sk_{data_ready,write_space}\n\nskmsg (and probably other layers) are changing these pointers\nwhile other cpus might read them concurrently.\n\nAdd corresponding READ_ONCE()/WRITE_ONCE() annotations\nfor UDP, TCP and AF_UNIX.(CVE-2026-23302)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nsmb: client: Don\u0026apos;t log plaintext credentials in cifs_set_cifscreds\n\nWhen debug logging is enabled, cifs_set_cifscreds() logs the key\npayload and exposes the plaintext username and password. Remove the\ndebug log to avoid exposing credentials.(CVE-2026-23303)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nipv6: fix NULL pointer deref in ip6_rt_get_dev_rcu()\n\nl3mdev_master_dev_rcu() can return NULL when the slave device is being\nun-slaved from a VRF. All other callers deal with this, but we lost\nthe fallback to loopback in ip6_rt_pcpu_alloc() -\u0026gt; ip6_rt_get_dev_rcu()\nwith commit 4832c30d5458 (\u0026quot;net: ipv6: put host and anycast routes on\ndevice with address\u0026quot;).\n\n  KASAN: null-ptr-deref in range [0x0000000000000108-0x000000000000010f]\n  RIP: 0010:ip6_rt_pcpu_alloc (net/ipv6/route.c:1418)\n  Call Trace:\n   ip6_pol_route (net/ipv6/route.c:2318)\n   fib6_rule_lookup (net/ipv6/fib6_rules.c:115)\n   ip6_route_output_flags (net/ipv6/route.c:2607)\n   vrf_process_v6_outbound (drivers/net/vrf.c:437)\n\nI was tempted to rework the un-slaving code to clear the flag first\nand insert synchronize_rcu() before we remove the upper. But looks like\nthe explicit fallback to loopback_dev is an established pattern.\nAnd I guess avoiding the synchronize_rcu() is nice, too.(CVE-2026-23304)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nbpf/bonding: reject vlan+srcmac xmit_hash_policy change when XDP is loaded\n\nbond_option_mode_set() already rejects mode changes that would make a\nloaded XDP program incompatible via bond_xdp_check().  However,\nbond_option_xmit_hash_policy_set() has no such guard.\n\nFor 802.3ad and balance-xor modes, bond_xdp_check() returns false when\nxmit_hash_policy is vlan+srcmac, because the 802.1q payload is usually\nabsent due to hardware offload.  This means a user can:\n\n1. Attach a native XDP program to a bond in 802.3ad/balance-xor mode\n   with a compatible xmit_hash_policy (e.g. layer2+3).\n2. Change xmit_hash_policy to vlan+srcmac while XDP remains loaded.\n\nThis leaves bond-\u0026gt;xdp_prog set but bond_xdp_check() now returning false\nfor the same device.  When the bond is later destroyed, dev_xdp_uninstall()\ncalls bond_xdp_set(dev, NULL, NULL) to remove the program, which hits\nthe bond_xdp_check() guard and returns -EOPNOTSUPP, triggering:\n\nWARN_ON(dev_xdp_install(dev, mode, bpf_op, NULL, 0, NULL))\n\nFix this by rejecting xmit_hash_policy changes to vlan+srcmac when an\nXDP program is loaded on a bond in 802.3ad or balance-xor mode.\n\ncommit 39a0876d595b (\u0026quot;net, bonding: Disallow vlan+srcmac with XDP\u0026quot;)\nintroduced bond_xdp_check() which returns false for 802.3ad/balance-xor\nmodes when xmit_hash_policy is vlan+srcmac.  The check was wired into\nbond_xdp_set() to reject XDP attachment with an incompatible policy, but\nthe symmetric path -- preventing xmit_hash_policy from being changed to an\nincompatible value after XDP is already loaded -- was left unguarded in\nbond_option_xmit_hash_policy_set().\n\nNote:\ncommit 094ee6017ea0 (\u0026quot;bonding: check xdp prog when set bond mode\u0026quot;)\nlater added a similar guard to bond_option_mode_set(), but\nbond_option_xmit_hash_policy_set() remained unprotected.(CVE-2026-23310)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nmptcp: pm: in-kernel: always mark signal+subflow endp as used\n\nSyzkaller managed to find a combination of actions that was generating\nthis warning:\n\n  msk-\u0026gt;pm.local_addr_used == 0\n  WARNING: net/mptcp/pm_kernel.c:1071 at __mark_subflow_endp_available net/mptcp/pm_kernel.c:1071 [inline], CPU#1: syz.2.17/961\n  WARNING: net/mptcp/pm_kernel.c:1071 at mptcp_nl_remove_subflow_and_signal_addr net/mptcp/pm_kernel.c:1103 [inline], CPU#1: syz.2.17/961\n  WARNING: net/mptcp/pm_kernel.c:1071 at mptcp_pm_nl_del_addr_doit+0x81d/0x8f0 net/mptcp/pm_kernel.c:1210, CPU#1: syz.2.17/961\n  Modules linked in:\n  CPU: 1 UID: 0 PID: 961 Comm: syz.2.17 Not tainted 6.19.0-08368-gfafda3b4b06b #22 PREEMPT(full)\n  Hardware name: QEMU Ubuntu 25.10 PC v2 (i440FX + PIIX, + 10.1 machine, 1996), BIOS 1.17.0-debian-1.17.0-1build1 04/01/2014\n  RIP: 0010:__mark_subflow_endp_available net/mptcp/pm_kernel.c:1071 [inline]\n  RIP: 0010:mptcp_nl_remove_subflow_and_signal_addr net/mptcp/pm_kernel.c:1103 [inline]\n  RIP: 0010:mptcp_pm_nl_del_addr_doit+0x81d/0x8f0 net/mptcp/pm_kernel.c:1210\n  Code: 89 c5 e8 46 30 6f fe e9 21 fd ff ff 49 83 ed 80 e8 38 30 6f fe 4c 89 ef be 03 00 00 00 e8 db 49 df fe eb ac e8 24 30 6f fe 90 \u0026lt;0f\u0026gt; 0b 90 e9 1d ff ff ff e8 16 30 6f fe eb 05 e8 0f 30 6f fe e8 9a\n  RSP: 0018:ffffc90001663880 EFLAGS: 00010293\n  RAX: ffffffff82de1a6c RBX: 0000000000000000 RCX: ffff88800722b500\n  RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000000000000\n  RBP: ffff8880158b22d0 R08: 0000000000010425 R09: ffffffffffffffff\n  R10: ffffffff82de18ba R11: 0000000000000000 R12: ffff88800641a640\n  R13: ffff8880158b1880 R14: ffff88801ec3c900 R15: ffff88800641a650\n  FS:  00005555722c3500(0000) GS:ffff8880f909d000(0000) knlGS:0000000000000000\n  CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033\n  CR2: 00007f66346e0f60 CR3: 000000001607c000 CR4: 0000000000350ef0\n  Call Trace:\n   \u0026lt;TASK\u0026gt;\n   genl_family_rcv_msg_doit+0x117/0x180 net/netlink/genetlink.c:1115\n   genl_family_rcv_msg net/netlink/genetlink.c:1195 [inline]\n   genl_rcv_msg+0x3a8/0x3f0 net/netlink/genetlink.c:1210\n   netlink_rcv_skb+0x16d/0x240 net/netlink/af_netlink.c:2550\n   genl_rcv+0x28/0x40 net/netlink/genetlink.c:1219\n   netlink_unicast_kernel net/netlink/af_netlink.c:1318 [inline]\n   netlink_unicast+0x3e9/0x4c0 net/netlink/af_netlink.c:1344\n   netlink_sendmsg+0x4aa/0x5b0 net/netlink/af_netlink.c:1894\n   sock_sendmsg_nosec net/socket.c:727 [inline]\n   __sock_sendmsg+0xc9/0xf0 net/socket.c:742\n   ____sys_sendmsg+0x272/0x3b0 net/socket.c:2592\n   ___sys_sendmsg+0x2de/0x320 net/socket.c:2646\n   __sys_sendmsg net/socket.c:2678 [inline]\n   __do_sys_sendmsg net/socket.c:2683 [inline]\n   __se_sys_sendmsg net/socket.c:2681 [inline]\n   __x64_sys_sendmsg+0x110/0x1a0 net/socket.c:2681\n   do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline]\n   do_syscall_64+0x143/0x440 arch/x86/entry/syscall_64.c:94\n   entry_SYSCALL_64_after_hwframe+0x77/0x7f\n  RIP: 0033:0x7f66346f826d\n  Code: ff c3 66 2e 0f 1f 84 00 00 00 00 00 90 f3 0f 1e fa 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 \u0026lt;48\u0026gt; 3d 01 f0 ff ff 73 01 c3 48 c7 c1 e8 ff ff ff f7 d8 64 89 01 48\n  RSP: 002b:00007ffc83d8bdc8 EFLAGS: 00000246 ORIG_RAX: 000000000000002e\n  RAX: ffffffffffffffda RBX: 00007f6634985fa0 RCX: 00007f66346f826d\n  RDX: 00000000040000b0 RSI: 0000200000000740 RDI: 0000000000000007\n  RBP: 0000000000000000 R08: 0000000000000000 R09: 0000000000000000\n  R10: 0000000000000000 R11: 0000000000000246 R12: 00007f6634985fa8\n  R13: 00007f6634985fac R14: 0000000000000000 R15: 0000000000001770\n   \u0026lt;/TASK\u0026gt;\n\nThe actions that caused that seem to be:\n\n - Set the MPTCP subflows limit to 0\n - Create an MPTCP endpoint with both the \u0026apos;signal\u0026apos; and \u0026apos;subflow\u0026apos; flags\n - Create a new MPTCP connection from a different address: an ADD_ADDR\n   linked to the MPTCP endpoint will be sent (\u0026apos;signal\u0026apos; flag), but no\n   subflows is initiated (\u0026apos;subflow\u0026apos; flag)\n - Remove the MPTCP endpoint\n\n---truncated---(CVE-2026-23321)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nxdp: produce a warning when calculated tailroom is negative\n\nMany ethernet drivers report xdp Rx queue frag size as being the same as\nDMA write size. However, the only user of this field, namely\nbpf_xdp_frags_increase_tail(), clearly expects a truesize.\n\nSuch difference leads to unspecific memory corruption issues under certain\ncircumstances, e.g. in ixgbevf maximum DMA write size is 3 KB, so when\nrunning xskxceiver\u0026apos;s XDP_ADJUST_TAIL_GROW_MULTI_BUFF, 6K packet fully uses\nall DMA-writable space in 2 buffers. This would be fine, if only\nrxq-\u0026gt;frag_size was properly set to 4K, but value of 3K results in a\nnegative tailroom, because there is a non-zero page offset.\n\nWe are supposed to return -EINVAL and be done with it in such case, but due\nto tailroom being stored as an unsigned int, it is reported to be somewhere\nnear UINT_MAX, resulting in a tail being grown, even if the requested\noffset is too much (it is around 2K in the abovementioned test). This later\nleads to all kinds of unspecific calltraces.\n\n[ 7340.337579] xskxceiver[1440]: segfault at 1da718 ip 00007f4161aeac9d sp 00007f41615a6a00 error 6\n[ 7340.338040] xskxceiver[1441]: segfault at 7f410000000b ip 00000000004042b5 sp 00007f415bffecf0 error 4\n[ 7340.338179]  in libc.so.6[61c9d,7f4161aaf000+160000]\n[ 7340.339230]  in xskxceiver[42b5,400000+69000]\n[ 7340.340300]  likely on CPU 6 (core 0, socket 6)\n[ 7340.340302] Code: ff ff 01 e9 f4 fe ff ff 0f 1f 44 00 00 4c 39 f0 74 73 31 c0 ba 01 00 00 00 f0 0f b1 17 0f 85 ba 00 00 00 49 8b 87 88 00 00 00 \u0026lt;4c\u0026gt; 89 70 08 eb cc 0f 1f 44 00 00 48 8d bd f0 fe ff ff 89 85 ec fe\n[ 7340.340888]  likely on CPU 3 (core 0, socket 3)\n[ 7340.345088] Code: 00 00 00 ba 00 00 00 00 be 00 00 00 00 89 c7 e8 31 ca ff ff 89 45 ec 8b 45 ec 85 c0 78 07 b8 00 00 00 00 eb 46 e8 0b c8 ff ff \u0026lt;8b\u0026gt; 00 83 f8 69 74 24 e8 ff c7 ff ff 8b 00 83 f8 0b 74 18 e8 f3 c7\n[ 7340.404334] Oops: general protection fault, probably for non-canonical address 0x6d255010bdffc: 0000 [#1] SMP NOPTI\n[ 7340.405972] CPU: 7 UID: 0 PID: 1439 Comm: xskxceiver Not tainted 6.19.0-rc1+ #21 PREEMPT(lazy)\n[ 7340.408006] Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.17.0-5.fc42 04/01/2014\n[ 7340.409716] RIP: 0010:lookup_swap_cgroup_id+0x44/0x80\n[ 7340.410455] Code: 83 f8 1c 73 39 48 ba ff ff ff ff ff ff ff 03 48 8b 04 c5 20 55 fa bd 48 21 d1 48 89 ca 83 e1 01 48 d1 ea c1 e1 04 48 8d 04 90 \u0026lt;8b\u0026gt; 00 48 83 c4 10 d3 e8 c3 cc cc cc cc 31 c0 e9 98 b7 dd 00 48 89\n[ 7340.412787] RSP: 0018:ffffcc5c04f7f6d0 EFLAGS: 00010202\n[ 7340.413494] RAX: 0006d255010bdffc RBX: ffff891f477895a8 RCX: 0000000000000010\n[ 7340.414431] RDX: 0001c17e3fffffff RSI: 00fa070000000000 RDI: 000382fc7fffffff\n[ 7340.415354] RBP: 00fa070000000000 R08: ffffcc5c04f7f8f8 R09: ffffcc5c04f7f7d0\n[ 7340.416283] R10: ffff891f4c1a7000 R11: ffffcc5c04f7f9c8 R12: ffffcc5c04f7f7d0\n[ 7340.417218] R13: 03ffffffffffffff R14: 00fa06fffffffe00 R15: ffff891f47789500\n[ 7340.418229] FS:  0000000000000000(0000) GS:ffff891ffdfaa000(0000) knlGS:0000000000000000\n[ 7340.419489] CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033\n[ 7340.420286] CR2: 00007f415bfffd58 CR3: 0000000103f03002 CR4: 0000000000772ef0\n[ 7340.421237] PKRU: 55555554\n[ 7340.421623] Call Trace:\n[ 7340.421987]  \u0026lt;TASK\u0026gt;\n[ 7340.422309]  ? softleaf_from_pte+0x77/0xa0\n[ 7340.422855]  swap_pte_batch+0xa7/0x290\n[ 7340.423363]  zap_nonpresent_ptes.constprop.0.isra.0+0xd1/0x270\n[ 7340.424102]  zap_pte_range+0x281/0x580\n[ 7340.424607]  zap_pmd_range.isra.0+0xc9/0x240\n[ 7340.425177]  unmap_page_range+0x24d/0x420\n[ 7340.425714]  unmap_vmas+0xa1/0x180\n[ 7340.426185]  exit_mmap+0xe1/0x3b0\n[ 7340.426644]  __mmput+0x41/0x150\n[ 7340.427098]  exit_mm+0xb1/0x110\n[ 7340.427539]  do_exit+0x1b2/0x460\n[ 7340.427992]  do_group_exit+0x2d/0xc0\n[ 7340.428477]  get_signal+0x79d/0x7e0\n[ 7340.428957]  arch_do_signal_or_restart+0x34/0x100\n[ 7340.429571]  exit_to_user_mode_loop+0x8e/0x4c0\n[ 7340.430159]  do_syscall_64+0x188/\n---truncated---(CVE-2026-23343)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnetfilter: nft_set_pipapo: split gc into unlink and reclaim phase\n\nYiming Qian reports Use-after-free in the pipapo set type:\n  Under a large number of expired elements, commit-time GC can run for a very\n  long time in a non-preemptible context, triggering soft lockup warnings and\n  RCU stall reports (local denial of service).\n\nWe must split GC in an unlink and a reclaim phase.\n\nWe cannot queue elements for freeing until pointers have been swapped.\nExpired elements are still exposed to both the packet path and userspace\ndumpers via the live copy of the data structure.\n\ncall_rcu() does not protect us: dump operations or element lookups starting\nafter call_rcu has fired can still observe the free\u0026apos;d element, unless the\ncommit phase has made enough progress to swap the clone and live pointers\nbefore any new reader has picked up the old version.\n\nThis a similar approach as done recently for the rbtree backend in commit\n35f83a75529a (\u0026quot;netfilter: nft_set_rbtree: don\u0026apos;t gc elements on insert\u0026quot;).(CVE-2026-23351)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ncan: bcm: fix locking for bcm_op runtime updates\n\nCommit c2aba69d0c36 (\u0026quot;can: bcm: add locking for bcm_op runtime updates\u0026quot;)\nadded a locking for some variables that can be modified at runtime when\nupdating the sending bcm_op with a new TX_SETUP command in bcm_tx_setup().\n\nUsually the RX_SETUP only handles and filters incoming traffic with one\nexception: When the RX_RTR_FRAME flag is set a predefined CAN frame is\nsent when a specific RTR frame is received. Therefore the rx bcm_op uses\nbcm_can_tx() which uses the bcm_tx_lock that was only initialized in\nbcm_tx_setup(). Add the missing spin_lock_init() when allocating the\nbcm_op in bcm_rx_setup() to handle the RTR case properly.(CVE-2026-23362)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnet: usb: kalmia: validate USB endpoints\n\nThe kalmia driver should validate that the device it is probing has the\nproper number and types of USB endpoints it is expecting before it binds\nto it.  If a malicious device were to not have the same urbs the driver\nwill crash later on when it blindly accesses these endpoints.(CVE-2026-23365)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnet: phy: register phy led_triggers during probe to avoid AB-BA deadlock\n\nThere is an AB-BA deadlock when both LEDS_TRIGGER_NETDEV and\nLED_TRIGGER_PHY are enabled:\n\n[ 1362.049207] [\u0026lt;8054e4b8\u0026gt;] led_trigger_register+0x5c/0x1fc             \u0026lt;-- Trying to get lock \u0026quot;triggers_list_lock\u0026quot; via down_write(\u0026amp;triggers_list_lock);\n[ 1362.054536] [\u0026lt;80662830\u0026gt;] phy_led_triggers_register+0xd0/0x234\n[ 1362.060329] [\u0026lt;8065e200\u0026gt;] phy_attach_direct+0x33c/0x40c\n[ 1362.065489] [\u0026lt;80651fc4\u0026gt;] phylink_fwnode_phy_connect+0x15c/0x23c\n[ 1362.071480] [\u0026lt;8066ee18\u0026gt;] mtk_open+0x7c/0xba0\n[ 1362.075849] [\u0026lt;806d714c\u0026gt;] __dev_open+0x280/0x2b0\n[ 1362.080384] [\u0026lt;806d7668\u0026gt;] __dev_change_flags+0x244/0x24c\n[ 1362.085598] [\u0026lt;806d7698\u0026gt;] dev_change_flags+0x28/0x78\n[ 1362.090528] [\u0026lt;807150e4\u0026gt;] dev_ioctl+0x4c0/0x654                       \u0026lt;-- Hold lock \u0026quot;rtnl_mutex\u0026quot; by calling rtnl_lock();\n[ 1362.094985] [\u0026lt;80694360\u0026gt;] sock_ioctl+0x2f4/0x4e0\n[ 1362.099567] [\u0026lt;802e9c4c\u0026gt;] sys_ioctl+0x32c/0xd8c\n[ 1362.104022] [\u0026lt;80014504\u0026gt;] syscall_common+0x34/0x58\n\nHere LED_TRIGGER_PHY is registering LED triggers during phy_attach\nwhile holding RTNL and then taking triggers_list_lock.\n\n[ 1362.191101] [\u0026lt;806c2640\u0026gt;] register_netdevice_notifier+0x60/0x168      \u0026lt;-- Trying to get lock \u0026quot;rtnl_mutex\u0026quot; via rtnl_lock();\n[ 1362.197073] [\u0026lt;805504ac\u0026gt;] netdev_trig_activate+0x194/0x1e4\n[ 1362.202490] [\u0026lt;8054e28c\u0026gt;] led_trigger_set+0x1d4/0x360                 \u0026lt;-- Hold lock \u0026quot;triggers_list_lock\u0026quot; by down_read(\u0026amp;triggers_list_lock);\n[ 1362.207511] [\u0026lt;8054eb38\u0026gt;] led_trigger_write+0xd8/0x14c\n[ 1362.212566] [\u0026lt;80381d98\u0026gt;] sysfs_kf_bin_write+0x80/0xbc\n[ 1362.217688] [\u0026lt;8037fcd8\u0026gt;] kernfs_fop_write_iter+0x17c/0x28c\n[ 1362.223174] [\u0026lt;802cbd70\u0026gt;] vfs_write+0x21c/0x3c4\n[ 1362.227712] [\u0026lt;802cc0c4\u0026gt;] ksys_write+0x78/0x12c\n[ 1362.232164] [\u0026lt;80014504\u0026gt;] syscall_common+0x34/0x58\n\nHere LEDS_TRIGGER_NETDEV is being enabled on an LED. It first takes\ntriggers_list_lock and then RTNL. A classical AB-BA deadlock.\n\nphy_led_triggers_registers() does not require the RTNL, it does not\nmake any calls into the network stack which require protection. There\nis also no requirement the PHY has been attached to a MAC, the\ntriggers only make use of phydev state. This allows the call to\nphy_led_triggers_registers() to be placed elsewhere. PHY probe() and\nrelease() don\u0026apos;t hold RTNL, so solving the AB-BA deadlock.(CVE-2026-23368)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nsched/deadline: Fix missing ENQUEUE_REPLENISH during PI de-boosting\n\nRunning stress-ng --schedpolicy 0 on an RT kernel on a big machine\nmight lead to the following WARNINGs (edited).\n\n sched: DL de-boosted task PID 22725: REPLENISH flag missing\n\n WARNING: CPU: 93 PID: 0 at kernel/sched/deadline.c:239 dequeue_task_dl+0x15c/0x1f8\n ... (running_bw underflow)\n Call trace:\n  dequeue_task_dl+0x15c/0x1f8 (P)\n  dequeue_task+0x80/0x168\n  deactivate_task+0x24/0x50\n  push_dl_task+0x264/0x2e0\n  dl_task_timer+0x1b0/0x228\n  __hrtimer_run_queues+0x188/0x378\n  hrtimer_interrupt+0xfc/0x260\n  ...\n\nThe problem is that when a SCHED_DEADLINE task (lock holder) is\nchanged to a lower priority class via sched_setscheduler(), it may\nfail to properly inherit the parameters of potential DEADLINE donors\nif it didn\u0026apos;t already inherit them in the past (shorter deadline than\ndonor\u0026apos;s at that time). This might lead to bandwidth accounting\ncorruption, as enqueue_task_dl() won\u0026apos;t recognize the lock holder as\nboosted.\n\nThe scenario occurs when:\n1. A DEADLINE task (donor) blocks on a PI mutex held by another\n   DEADLINE task (holder), but the holder doesn\u0026apos;t inherit parameters\n   (e.g., it already has a shorter deadline)\n2. sched_setscheduler() changes the holder from DEADLINE to a lower\n   class while still holding the mutex\n3. The holder should now inherit DEADLINE parameters from the donor\n   and be enqueued with ENQUEUE_REPLENISH, but this doesn\u0026apos;t happen\n\nFix the issue by introducing __setscheduler_dl_pi(), which detects when\na DEADLINE (proper or boosted) task gets setscheduled to a lower\npriority class. In case, the function makes the task inherit DEADLINE\nparameters of the donoer (pi_se) and sets ENQUEUE_REPLENISH flag to\nensure proper bandwidth accounting during the next enqueue operation.(CVE-2026-23371)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nmm: thp: deny THP for files on anonymous inodes\n\nfile_thp_enabled() incorrectly allows THP for files on anonymous inodes\n(e.g. guest_memfd and secretmem). These files are created via\nalloc_file_pseudo(), which does not call get_write_access() and leaves\ninode-\u0026gt;i_writecount at 0. Combined with S_ISREG(inode-\u0026gt;i_mode) being\ntrue, they appear as read-only regular files when\nCONFIG_READ_ONLY_THP_FOR_FS is enabled, making them eligible for THP\ncollapse.\n\nAnonymous inodes can never pass the inode_is_open_for_write() check\nsince their i_writecount is never incremented through the normal VFS\nopen path. The right thing to do is to exclude them from THP eligibility\naltogether, since CONFIG_READ_ONLY_THP_FOR_FS was designed for real\nfilesystem files (e.g. shared libraries), not for pseudo-filesystem\ninodes.\n\nFor guest_memfd, this allows khugepaged and MADV_COLLAPSE to create\nlarge folios in the page cache via the collapse path, but the\nguest_memfd fault handler does not support large folios. This triggers\nWARN_ON_ONCE(folio_test_large(folio)) in kvm_gmem_fault_user_mapping().\n\nFor secretmem, collapse_file() tries to copy page contents through the\ndirect map, but secretmem pages are removed from the direct map. This\ncan result in a kernel crash:\n\n    BUG: unable to handle page fault for address: ffff88810284d000\n    RIP: 0010:memcpy_orig+0x16/0x130\n    Call Trace:\n     collapse_file\n     hpage_collapse_scan_file\n     madvise_collapse\n\nSecretmem is not affected by the crash on upstream as the memory failure\nrecovery handles the failed copy gracefully, but it still triggers\nconfusing false memory failure reports:\n\n    Memory failure: 0x106d96f: recovery action for clean unevictable\n    LRU page: Recovered\n\nCheck IS_ANON_FILE(inode) in file_thp_enabled() to deny THP for all\nanonymous inode files.(CVE-2026-23375)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnet: bridge: fix nd_tbl NULL dereference when IPv6 is disabled\n\nWhen booting with the \u0026apos;ipv6.disable=1\u0026apos; parameter, the nd_tbl is never\ninitialized because inet6_init() exits before ndisc_init() is called\nwhich initializes it. Then, if neigh_suppress is enabled and an ICMPv6\nNeighbor Discovery packet reaches the bridge, br_do_suppress_nd() will\ndereference ipv6_stub-\u0026gt;nd_tbl which is NULL, passing it to\nneigh_lookup(). This causes a kernel NULL pointer dereference.\n\n BUG: kernel NULL pointer dereference, address: 0000000000000268\n Oops: 0000 [#1] PREEMPT SMP NOPTI\n [...]\n RIP: 0010:neigh_lookup+0x16/0xe0\n [...]\n Call Trace:\n  \u0026lt;IRQ\u0026gt;\n  ? neigh_lookup+0x16/0xe0\n  br_do_suppress_nd+0x160/0x290 [bridge]\n  br_handle_frame_finish+0x500/0x620 [bridge]\n  br_handle_frame+0x353/0x440 [bridge]\n  __netif_receive_skb_core.constprop.0+0x298/0x1110\n  __netif_receive_skb_one_core+0x3d/0xa0\n  process_backlog+0xa0/0x140\n  __napi_poll+0x2c/0x170\n  net_rx_action+0x2c4/0x3a0\n  handle_softirqs+0xd0/0x270\n  do_softirq+0x3f/0x60\n\nFix this by replacing IS_ENABLED(IPV6) call with ipv6_mod_enabled() in\nthe callers. This is in essence disabling NS/NA suppression when IPv6 is\ndisabled.(CVE-2026-23381)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnetfilter: xt_CT: drop pending enqueued packets on template removal\n\nTemplates refer to objects that can go away while packets are sitting in\nnfqueue refer to:\n\n- helper, this can be an issue on module removal.\n- timeout policy, nfnetlink_cttimeout might remove it.\n\nThe use of templates with zone and event cache filter are safe, since\nthis just copies values.\n\nFlush these enqueued packets in case the template rule gets removed.(CVE-2026-23391)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnetfilter: nf_tables: release flowtable after rcu grace period on error\n\nCall synchronize_rcu() after unregistering the hooks from error path,\nsince a hook that already refers to this flowtable can be already\nregistered, exposing this flowtable to packet path and nfnetlink_hook\ncontrol plane.\n\nThis error path is rare, it should only happen by reaching the maximum\nnumber hooks or by failing to set up to hardware offload, just call\nsynchronize_rcu().\n\nThere is a check for already used device hooks by different flowtable\nthat could result in EEXIST at this late stage. The hook parser can be\nupdated to perform this check earlier to this error path really becomes\nrarely exercised.\n\nUncovered by KASAN reported as use-after-free from nfnetlink_hook path\nwhen dumping hooks.(CVE-2026-23392)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nbridge: cfm: Fix race condition in peer_mep deletion\n\nWhen a peer MEP is being deleted, cancel_delayed_work_sync() is called\non ccm_rx_dwork before freeing. However, br_cfm_frame_rx() runs in\nsoftirq context under rcu_read_lock (without RTNL) and can re-schedule\nccm_rx_dwork via ccm_rx_timer_start() between cancel_delayed_work_sync()\nreturning and kfree_rcu() being called.\n\nThe following is a simple race scenario:\n\n           cpu0                                     cpu1\n\nmep_delete_implementation()\n  cancel_delayed_work_sync(ccm_rx_dwork);\n                                           br_cfm_frame_rx()\n                                             // peer_mep still in hlist\n                                             if (peer_mep-\u0026gt;ccm_defect)\n                                               ccm_rx_timer_start()\n                                                 queue_delayed_work(ccm_rx_dwork)\n  hlist_del_rcu(\u0026amp;peer_mep-\u0026gt;head);\n  kfree_rcu(peer_mep, rcu);\n                                           ccm_rx_work_expired()\n                                             // on freed peer_mep\n\nTo prevent this, cancel_delayed_work_sync() is replaced with\ndisable_delayed_work_sync() in both peer MEP deletion paths, so\nthat subsequent queue_delayed_work() calls from br_cfm_frame_rx()\nare silently rejected.\n\nThe cc_peer_disable() helper retains cancel_delayed_work_sync()\nbecause it is also used for the CC enable/disable toggle path where\nthe work must remain re-schedulable.(CVE-2026-23393)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\naf_unix: Give up GC if MSG_PEEK intervened.\n\nIgor Ushakov reported that GC purged the receive queue of\nan alive socket due to a race with MSG_PEEK with a nice repro.\n\nThis is the exact same issue previously fixed by commit\ncbcf01128d0a (\u0026quot;af_unix: fix garbage collect vs MSG_PEEK\u0026quot;).\n\nAfter GC was replaced with the current algorithm, the cited\ncommit removed the locking dance in unix_peek_fds() and\nreintroduced the same issue.\n\nThe problem is that MSG_PEEK bumps a file refcount without\ninteracting with GC.\n\nConsider an SCC containing sk-A and sk-B, where sk-A is\nclose()d but can be recv()ed via sk-B.\n\nThe bad thing happens if sk-A is recv()ed with MSG_PEEK from\nsk-B and sk-B is close()d while GC is checking unix_vertex_dead()\nfor sk-A and sk-B.\n\n  GC thread                    User thread\n  ---------                    -----------\n  unix_vertex_dead(sk-A)\n  -\u0026gt; true   \u0026lt;------.\n                    \\\n                     `------   recv(sk-B, MSG_PEEK)\n              invalidate !!    -\u0026gt; sk-A\u0026apos;s file refcount : 1 -\u0026gt; 2\n\n                               close(sk-B)\n                               -\u0026gt; sk-B\u0026apos;s file refcount : 2 -\u0026gt; 1\n  unix_vertex_dead(sk-B)\n  -\u0026gt; true\n\nInitially, sk-A\u0026apos;s file refcount is 1 by the inflight fd in sk-B\nrecvq.  GC thinks sk-A is dead because the file refcount is the\nsame as the number of its inflight fds.\n\nHowever, sk-A\u0026apos;s file refcount is bumped silently by MSG_PEEK,\nwhich invalidates the previous evaluation.\n\nAt this moment, sk-B\u0026apos;s file refcount is 2; one by the open fd,\nand one by the inflight fd in sk-A.  The subsequent close()\nreleases one refcount by the former.\n\nFinally, GC incorrectly concludes that both sk-A and sk-B are dead.\n\nOne option is to restore the locking dance in unix_peek_fds(),\nbut we can resolve this more elegantly thanks to the new algorithm.\n\nThe point is that the issue does not occur without the subsequent\nclose() and we actually do not need to synchronise MSG_PEEK with\nthe dead SCC detection.\n\nWhen the issue occurs, close() and GC touch the same file refcount.\nIf GC sees the refcount being decremented by close(), it can just\ngive up garbage-collecting the SCC.\n\nTherefore, we only need to signal the race during MSG_PEEK with\na proper memory barrier to make it visible to the GC.\n\nLet\u0026apos;s use seqcount_t to notify GC when MSG_PEEK occurs and let\nit defer the SCC to the next run.\n\nThis way no locking is needed on the MSG_PEEK side, and we can\navoid imposing a penalty on every MSG_PEEK unnecessarily.\n\nNote that we can retry within unix_scc_dead() if MSG_PEEK is\ndetected, but we do not do so to avoid hung task splat from\nabusive MSG_PEEK calls.(CVE-2026-23394)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nBluetooth: L2CAP: Fix accepting multiple L2CAP_ECRED_CONN_REQ\n\nCurrently the code attempts to accept requests regardless of the\ncommand identifier which may cause multiple requests to be marked\nas pending (FLAG_DEFER_SETUP) which can cause more than\nL2CAP_ECRED_MAX_CID(5) to be allocated in l2cap_ecred_rsp_defer\ncausing an overflow.\n\nThe spec is quite clear that the same identifier shall not be used on\nsubsequent requests:\n\n\u0026apos;Within each signaling channel a different Identifier shall be used\nfor each successive request or indication.\u0026apos;\nhttps://www.bluetooth.com/wp-content/uploads/Files/Specification/HTML/Core-62/out/en/host/logical-link-control-and-adaptation-protocol-specification.html#UUID-32a25a06-4aa4-c6c7-77c5-dcfe3682355d\n\nSo this attempts to check if there are any channels pending with the\nsame identifier and rejects if any are found.(CVE-2026-23395)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnfnetlink_osf: validate individual option lengths in fingerprints\n\nnfnl_osf_add_callback() validates opt_num bounds and string\nNUL-termination but does not check individual option length fields.\nA zero-length option causes nf_osf_match_one() to enter the option\nmatching loop even when foptsize sums to zero, which matches packets\nwith no TCP options where ctx-\u0026gt;optp is NULL:\n\n Oops: general protection fault\n KASAN: null-ptr-deref in range [0x0000000000000000-0x0000000000000007]\n RIP: 0010:nf_osf_match_one (net/netfilter/nfnetlink_osf.c:98)\n Call Trace:\n  nf_osf_match (net/netfilter/nfnetlink_osf.c:227)\n  xt_osf_match_packet (net/netfilter/xt_osf.c:32)\n  ipt_do_table (net/ipv4/netfilter/ip_tables.c:293)\n  nf_hook_slow (net/netfilter/core.c:623)\n  ip_local_deliver (net/ipv4/ip_input.c:262)\n  ip_rcv (net/ipv4/ip_input.c:573)\n\nAdditionally, an MSS option (kind=2) with length \u0026lt; 4 causes\nout-of-bounds reads when nf_osf_match_one() unconditionally accesses\noptp[2] and optp[3] for MSS value extraction.  While RFC 9293\nsection 3.2 specifies that the MSS option is always exactly 4\nbytes (Kind=2, Length=4), the check uses \u0026quot;\u0026lt; 4\u0026quot; rather than\n\u0026quot;!= 4\u0026quot; because lengths greater than 4 do not cause memory\nsafety issues -- the buffer is guaranteed to be at least\nfoptsize bytes by the ctx-\u0026gt;optsize == foptsize check.\n\nReject fingerprints where any option has zero length, or where an MSS\noption has length less than 4, at add time rather than trusting these\nvalues in the packet matching hot path.(CVE-2026-23397)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnf_tables: nft_dynset: fix possible stateful expression memleak in error path\n\nIf cloning the second stateful expression in the element via GFP_ATOMIC\nfails, then the first stateful expression remains in place without being\nreleased.\n\n   unreferenced object (percpu) 0x607b97e9cab8 (size 16):\n     comm \u0026quot;softirq\u0026quot;, pid 0, jiffies 4294931867\n     hex dump (first 16 bytes on cpu 3):\n       00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00\n     backtrace (crc 0):\n       pcpu_alloc_noprof+0x453/0xd80\n       nft_counter_clone+0x9c/0x190 [nf_tables]\n       nft_expr_clone+0x8f/0x1b0 [nf_tables]\n       nft_dynset_new+0x2cb/0x5f0 [nf_tables]\n       nft_rhash_update+0x236/0x11c0 [nf_tables]\n       nft_dynset_eval+0x11f/0x670 [nf_tables]\n       nft_do_chain+0x253/0x1700 [nf_tables]\n       nft_do_chain_ipv4+0x18d/0x270 [nf_tables]\n       nf_hook_slow+0xaa/0x1e0\n       ip_local_deliver+0x209/0x330(CVE-2026-23399)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nKVM: x86/mmu: Drop/zap existing present SPTE even when creating an MMIO SPTE\n\nWhen installing an emulated MMIO SPTE, do so *after* dropping/zapping the\nexisting SPTE (if it\u0026apos;s shadow-present).  While commit a54aa15c6bda3 was\nright about it being impossible to convert a shadow-present SPTE to an\nMMIO SPTE due to a _guest_ write, it failed to account for writes to guest\nmemory that are outside the scope of KVM.\n\nE.g. if host userspace modifies a shadowed gPTE to switch from a memslot\nto emulted MMIO and then the guest hits a relevant page fault, KVM will\ninstall the MMIO SPTE without first zapping the shadow-present SPTE.\n\n  ------------[ cut here ]------------\n  is_shadow_present_pte(*sptep)\n  WARNING: arch/x86/kvm/mmu/mmu.c:484 at mark_mmio_spte+0xb2/0xc0 [kvm], CPU#0: vmx_ept_stale_r/4292\n  Modules linked in: kvm_intel kvm irqbypass\n  CPU: 0 UID: 1000 PID: 4292 Comm: vmx_ept_stale_r Not tainted 7.0.0-rc2-eafebd2d2ab0-sink-vm #319 PREEMPT\n  Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 0.0.0 02/06/2015\n  RIP: 0010:mark_mmio_spte+0xb2/0xc0 [kvm]\n  Call Trace:\n   \u0026lt;TASK\u0026gt;\n   mmu_set_spte+0x237/0x440 [kvm]\n   ept_page_fault+0x535/0x7f0 [kvm]\n   kvm_mmu_do_page_fault+0xee/0x1f0 [kvm]\n   kvm_mmu_page_fault+0x8d/0x620 [kvm]\n   vmx_handle_exit+0x18c/0x5a0 [kvm_intel]\n   kvm_arch_vcpu_ioctl_run+0xc55/0x1c20 [kvm]\n   kvm_vcpu_ioctl+0x2d5/0x980 [kvm]\n   __x64_sys_ioctl+0x8a/0xd0\n   do_syscall_64+0xb5/0x730\n   entry_SYSCALL_64_after_hwframe+0x4b/0x53\n  RIP: 0033:0x47fa3f\n   \u0026lt;/TASK\u0026gt;\n  ---[ end trace 0000000000000000 ]---(CVE-2026-23401)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\napparmor: fix memory leak in verify_header\n\nThe function sets `*ns = NULL` on every call, leaking the namespace\nstring allocated in previous iterations when multiple profiles are\nunpacked. This also breaks namespace consistency checking since *ns\nis always NULL when the comparison is made.\n\nRemove the incorrect assignment.\nThe caller (aa_unpack) initializes *ns to NULL once before the loop,\nwhich is sufficient.(CVE-2026-23403)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\napparmor: replace recursive profile removal with iterative approach\n\nThe profile removal code uses recursion when removing nested profiles,\nwhich can lead to kernel stack exhaustion and system crashes.\n\nReproducer:\n  $ pf=\u0026apos;a\u0026apos;; for ((i=0; i\u0026lt;1024; i++)); do\n      echo -e \u0026quot;profile $pf { \\n }\u0026quot; | apparmor_parser -K -a;\n      pf=\u0026quot;$pf//x\u0026quot;;\n  done\n  $ echo -n a \u0026gt; /sys/kernel/security/apparmor/.remove\n\nReplace the recursive __aa_profile_list_release() approach with an\niterative approach in __remove_profile(). The function repeatedly\nfinds and removes leaf profiles until the entire subtree is removed,\nmaintaining the same removal semantic without recursion.(CVE-2026-23404)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\napparmor: fix: limit the number of levels of policy namespaces\n\nCurrently the number of policy namespaces is not bounded relying on\nthe user namespace limit. However policy namespaces aren\u0026apos;t strictly\ntied to user namespaces and it is possible to create them and nest\nthem arbitrarily deep which can be used to exhaust system resource.\n\nHard cap policy namespaces to the same depth as user namespaces.(CVE-2026-23405)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\napparmor: Fix double free of ns_name in aa_replace_profiles()\n\nif ns_name is NULL after\n1071         error = aa_unpack(udata, \u0026amp;lh, \u0026amp;ns_name);\n\nand if ent-\u0026gt;ns_name contains an ns_name in\n1089                 } else if (ent-\u0026gt;ns_name) {\n\nthen ns_name is assigned the ent-\u0026gt;ns_name\n1095                         ns_name = ent-\u0026gt;ns_name;\n\nhowever ent-\u0026gt;ns_name is freed at\n1262                 aa_load_ent_free(ent);\n\nand then again when freeing ns_name at\n1270         kfree(ns_name);\n\nFix this by NULLing out ent-\u0026gt;ns_name after it is transferred to ns_name\n\n\u0026quot;)(CVE-2026-23408)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\napparmor: fix differential encoding verification\n\nDifferential encoding allows loops to be created if it is abused. To\nprevent this the unpack should verify that a diff-encode chain\nterminates.\n\nUnfortunately the differential encode verification had two bugs.\n\n1. it conflated states that had gone through check and already been\n   marked, with states that were currently being checked and marked.\n   This means that loops in the current chain being verified are treated\n   as a chain that has already been verified.\n\n2. the order bailout on already checked states compared current chain\n   check iterators j,k instead of using the outer loop iterator i.\n   Meaning a step backwards in states in the current chain verification\n   was being mistaken for moving to an already verified state.\n\nMove to a double mark scheme where already verified states get a\ndifferent mark, than the current chain being kept. This enables us\nto also drop the backwards verification check that was the cause of\nthe second error as any already verified state is already marked.(CVE-2026-23409)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\napparmor: fix race on rawdata dereference\n\nThere is a race condition that leads to a use-after-free situation:\nbecause the rawdata inodes are not refcounted, an attacker can start\nopen()ing one of the rawdata files, and at the same time remove the\nlast reference to this rawdata (by removing the corresponding profile,\nfor example), which frees its struct aa_loaddata; as a result, when\nseq_rawdata_open() is reached, i_private is a dangling pointer and\nfreed memory is accessed.\n\nThe rawdata inodes weren\u0026apos;t refcounted to avoid a circular refcount and\nwere supposed to be held by the profile rawdata reference.  However\nduring profile removal there is a window where the vfs and profile\ndestruction race, resulting in the use after free.\n\nFix this by moving to a double refcount scheme. Where the profile\nrefcount on rawdata is used to break the circular dependency. Allowing\nfor freeing of the rawdata once all inode references to the rawdata\nare put.(CVE-2026-23410)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\napparmor: fix race between freeing data and fs accessing it\n\nAppArmor was putting the reference to i_private data on its end after\nremoving the original entry from the file system. However the inode\ncan aand does live beyond that point and it is possible that some of\nthe fs call back functions will be invoked after the reference has\nbeen put, which results in a race between freeing the data and\naccessing it through the fs.\n\nWhile the rawdata/loaddata is the most likely candidate to fail the\nrace, as it has the fewest references. If properly crafted it might be\npossible to trigger a race for the other types stored in i_private.\n\nFix this by moving the put of i_private referenced data to the correct\nplace which is during inode eviction.(CVE-2026-23411)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nclsact: Fix use-after-free in init/destroy rollback asymmetry\n\nFix a use-after-free in the clsact qdisc upon init/destroy rollback asymmetry.\nThe latter is achieved by first fully initializing a clsact instance, and\nthen in a second step having a replacement failure for the new clsact qdisc\ninstance. clsact_init() initializes ingress first and then takes care of the\negress part. This can fail midway, for example, via tcf_block_get_ext(). Upon\nfailure, the kernel will trigger the clsact_destroy() callback.\n\nCommit 1cb6f0bae504 (\u0026quot;bpf: Fix too early release of tcx_entry\u0026quot;) details the\nway how the transition is happening. If tcf_block_get_ext on the q-\u0026gt;ingress_block\nends up failing, we took the tcx_miniq_inc reference count on the ingress\nside, but not yet on the egress side. clsact_destroy() tests whether the\n{ingress,egress}_entry was non-NULL. However, even in midway failure on the\nreplacement, both are in fact non-NULL with a valid egress_entry from the\nprevious clsact instance.\n\nWhat we really need to test for is whether the qdisc instance-specific ingress\nor egress side previously got initialized. This adds a small helper for checking\nthe miniq initialization called mini_qdisc_pair_inited, and utilizes that upon\nclsact_destroy() in order to fix the use-after-free scenario. Convert the\ningress_destroy() side as well so both are consistent to each other.(CVE-2026-23413)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ntls: Purge async_hold in tls_decrypt_async_wait()\n\nThe async_hold queue pins encrypted input skbs while\nthe AEAD engine references their scatterlist data. Once\ntls_decrypt_async_wait() returns, every AEAD operation\nhas completed and the engine no longer references those\nskbs, so they can be freed unconditionally.\n\nA subsequent patch adds batch async decryption to\ntls_sw_read_sock(), introducing a new call site that\nmust drain pending AEAD operations and release held\nskbs. Move __skb_queue_purge(\u0026amp;ctx-\u0026gt;async_hold) into\ntls_decrypt_async_wait() so the purge is centralized\nand every caller -- recvmsg\u0026apos;s drain path, the -EBUSY\nfallback in tls_do_decryption(), and the new read_sock\nbatch path -- releases held skbs on synchronization\nwithout each site managing the purge independently.\n\nThis fixes a leak when tls_strp_msg_hold() fails part-way through,\nafter having added some cloned skbs to the async_hold\nqueue. tls_decrypt_sg() will then call tls_decrypt_async_wait() to\nprocess all pending decrypts, and drop back to synchronous mode, but\ntls_sw_recvmsg() only flushes the async_hold queue when one record has\nbeen processed in \u0026quot;fully-async\u0026quot; mode, which may not be the case here.\n\n[(CVE-2026-23414)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nxen/privcmd: restrict usage in unprivileged domU\n\nThe Xen privcmd driver allows to issue arbitrary hypercalls from\nuser space processes. This is normally no problem, as access is\nusually limited to root and the hypervisor will deny any hypercalls\naffecting other domains.\n\nIn case the guest is booted using secure boot, however, the privcmd\ndriver would be enabling a root user process to modify e.g. kernel\nmemory contents, thus breaking the secure boot feature.\n\nThe only known case where an unprivileged domU is really needing to\nuse the privcmd driver is the case when it is acting as the device\nmodel for another guest. In this case all hypercalls issued via the\nprivcmd driver will target that other guest.\n\nFortunately the privcmd driver can already be locked down to allow\nonly hypercalls targeting a specific domain, but this mode can be\nactivated from user land only today.\n\nThe target domain can be obtained from Xenstore, so when not running\nin dom0 restrict the privcmd driver to that target domain from the\nbeginning, resolving the potential problem of breaking secure boot.\n\nThis is XSA-482\n\n---\nV2:\n- defer reading from Xenstore if Xenstore isn\u0026apos;t ready yet (Jan Beulich)\n- wait in open() if target domain isn\u0026apos;t known yet\n- issue message in case no target domain found (Jan Beulich)(CVE-2026-31788)","status":"published","published":"2026-04-11T11:10:53Z","modified":"2026-08-18T01:19:47.108291933Z","cvss":[{"version":"3.1","score":9.8,"vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H","level":"critical"}],"updated_at":"2026-11-02T15:52:46.087701Z"},{"id":"ROOT-OS-DEBIAN-12-CVE-2026-23394","title":"CVE-2026-23394 in linux - Patched by Root","description":"Root has patched CVE-2026-23394 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:23.076752211Z","cvss":[{"version":"3.1","score":4.7,"vector":"CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:H","level":"medium"}],"updated_at":"2026-11-02T15:53:31.773105Z"},{"id":"ROOT-OS-UBUNTU-2404-CVE-2026-23394","title":"CVE-2026-23394 in linux - Patched by Root","description":"Root has patched CVE-2026-23394 in the linux package for Root:Ubuntu:24.04. Multiple fixed versions available.","status":"published","published":"2026-11-06T15:54:27Z","modified":"2026-11-06T16:17:53.12989573Z","cvss":[{"version":"3.1","score":4.7,"vector":"CVSS:3.1/AV:L/AC:H/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-23394","description":"In the Linux kernel, the following vulnerability has been resolved: af_unix: Give up GC if MSG_PEEK intervened. Igor Ushakov reported that GC purged the receive queue of an alive socket due to a race with MSG_PEEK with a nice repro. This is the exact same issue previously fixed by commit cbcf01128d0a (\"af_unix: fix garbage collect vs MSG_PEEK\"). After GC was replaced with the current algorithm, the cited commit removed the locking dance in unix_peek_fds() and reintroduced the same issue. The problem is that MSG_PEEK bumps a file refcount without interacting with GC. Consider an SCC containing sk-A and sk-B, where sk-A is close()d but can be recv()ed via sk-B. The bad thing happens if sk-A is recv()ed with MSG_PEEK from sk-B and sk-B is close()d while GC is checking unix_vertex_dead() for sk-A and sk-B.   GC thread                    User thread   ---------                    -----------   unix_vertex_dead(sk-A)   -\u003e true   \u003c------.                     \\                      `------   recv(sk-B, MSG_PEEK)               invalidate !!    -\u003e sk-A's file refcount : 1 -\u003e 2                                close(sk-B)                                -\u003e sk-B's file refcount : 2 -\u003e 1   unix_vertex_dead(sk-B)   -\u003e true Initially, sk-A's file refcount is 1 by the inflight fd in sk-B recvq.  GC thinks sk-A is dead because the file refcount is the same as the number of its inflight fds. However, sk-A's file refcount is bumped silently by MSG_PEEK, which invalidates the previous evaluation. At this moment, sk-B's file refcount is 2; one by the open fd, and one by the inflight fd in sk-A.  The subsequent close() releases one refcount by the former. Finally, GC incorrectly concludes that both sk-A and sk-B are dead. One option is to restore the locking dance in unix_peek_fds(), but we can resolve this more elegantly thanks to the new algorithm. The point is that the issue does not occur without the subsequent close() and we actually do not need to synchronise MSG_PEEK with the dead SCC detection. When the issue occurs, close() and GC touch the same file refcount. If GC sees the refcount being decremented by close(), it can just give up garbage-collecting the SCC. Therefore, we only need to signal the race during MSG_PEEK with a proper memory barrier to make it visible to the GC. Let's use seqcount_t to notify GC when MSG_PEEK occurs and let it defer the SCC to the next run. This way no locking is needed on the MSG_PEEK side, and we can avoid imposing a penalty on every MSG_PEEK unnecessarily. Note that we can retry within unix_scc_dead() if MSG_PEEK is detected, but we do not do so to avoid hung task splat from abusive MSG_PEEK calls.","status":"published","published":"2026-03-25T11:16:00Z","modified":"2026-11-11T09:39:30.248453397Z","cvss":[{"version":"4.0","score":7.3,"vector":"CVSS:4.0/AV:L/AC:L/AT:P/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N","level":"high"},{"version":"3.1","score":4.7,"vector":"CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:H","level":"medium"}],"updated_at":"2026-11-11T10:01:26.670571Z"},{"id":"AZL-84053","title":"CVE-2026-23394 affecting package kernel for versions less than 6.6.142.1-1","description":"In the Linux kernel, the following vulnerability has been resolved:\n\naf_unix: Give up GC if MSG_PEEK intervened.\n\nIgor Ushakov reported that GC purged the receive queue of\nan alive socket due to a race with MSG_PEEK with a nice repro.\n\nThis is the exact same issue previously fixed by commit\ncbcf01128d0a (\"af_unix: fix garbage collect vs MSG_PEEK\").\n\nAfter GC was replaced with the current algorithm, the cited\ncommit removed the locking dance in unix_peek_fds() and\nreintroduced the same issue.\n\nThe problem is that MSG_PEEK bumps a file refcount without\ninteracting with GC.\n\nConsider an SCC containing sk-A and sk-B, where sk-A is\nclose()d but can be recv()ed via sk-B.\n\nThe bad thing happens if sk-A is recv()ed with MSG_PEEK from\nsk-B and sk-B is close()d while GC is checking unix_vertex_dead()\nfor sk-A and sk-B.\n\n  GC thread                    User thread\n  ---------                    -----------\n  unix_vertex_dead(sk-A)\n  -\u003e true   \u003c------.\n                    \\\n                     `------   recv(sk-B, MSG_PEEK)\n              invalidate !!    -\u003e sk-A's file refcount : 1 -\u003e 2\n\n                               close(sk-B)\n                               -\u003e sk-B's file refcount : 2 -\u003e 1\n  unix_vertex_dead(sk-B)\n  -\u003e true\n\nInitially, sk-A's file refcount is 1 by the inflight fd in sk-B\nrecvq.  GC thinks sk-A is dead because the file refcount is the\nsame as the number of its inflight fds.\n\nHowever, sk-A's file refcount is bumped silently by MSG_PEEK,\nwhich invalidates the previous evaluation.\n\nAt this moment, sk-B's file refcount is 2; one by the open fd,\nand one by the inflight fd in sk-A.  The subsequent close()\nreleases one refcount by the former.\n\nFinally, GC incorrectly concludes that both sk-A and sk-B are dead.\n\nOne option is to restore the locking dance in unix_peek_fds(),\nbut we can resolve this more elegantly thanks to the new algorithm.\n\nThe point is that the issue does not occur without the subsequent\nclose() and we actually do not need to synchronise MSG_PEEK with\nthe dead SCC detection.\n\nWhen the issue occurs, close() and GC touch the same file refcount.\nIf GC sees the refcount being decremented by close(), it can just\ngive up garbage-collecting the SCC.\n\nTherefore, we only need to signal the race during MSG_PEEK with\na proper memory barrier to make it visible to the GC.\n\nLet's use seqcount_t to notify GC when MSG_PEEK occurs and let\nit defer the SCC to the next run.\n\nThis way no locking is needed on the MSG_PEEK side, and we can\navoid imposing a penalty on every MSG_PEEK unnecessarily.\n\nNote that we can retry within unix_scc_dead() if MSG_PEEK is\ndetected, but we do not do so to avoid hung task splat from\nabusive MSG_PEEK calls.","status":"published","published":"2026-03-25T11:16:40Z","modified":"2026-11-05T05:40:51Z","updated_at":"2026-11-05T16:41:24.988217Z"},{"id":"CVE-2026-23394","title":"af_unix: Give up GC if MSG_PEEK intervened.","description":"In the Linux kernel, the following vulnerability has been resolved:\n\naf_unix: Give up GC if MSG_PEEK intervened.\n\nIgor Ushakov reported that GC purged the receive queue of\nan alive socket due to a race with MSG_PEEK with a nice repro.\n\nThis is the exact same issue previously fixed by commit\ncbcf01128d0a (\"af_unix: fix garbage collect vs MSG_PEEK\").\n\nAfter GC was replaced with the current algorithm, the cited\ncommit removed the locking dance in unix_peek_fds() and\nreintroduced the same issue.\n\nThe problem is that MSG_PEEK bumps a file refcount without\ninteracting with GC.\n\nConsider an SCC containing sk-A and sk-B, where sk-A is\nclose()d but can be recv()ed via sk-B.\n\nThe bad thing happens if sk-A is recv()ed with MSG_PEEK from\nsk-B and sk-B is close()d while GC is checking unix_vertex_dead()\nfor sk-A and sk-B.\n\n  GC thread                    User thread\n  ---------                    -----------\n  unix_vertex_dead(sk-A)\n  -\u003e true   \u003c------.\n                    \\\n                     `------   recv(sk-B, MSG_PEEK)\n              invalidate !!    -\u003e sk-A's file refcount : 1 -\u003e 2\n\n                               close(sk-B)\n                               -\u003e sk-B's file refcount : 2 -\u003e 1\n  unix_vertex_dead(sk-B)\n  -\u003e true\n\nInitially, sk-A's file refcount is 1 by the inflight fd in sk-B\nrecvq.  GC thinks sk-A is dead because the file refcount is the\nsame as the number of its inflight fds.\n\nHowever, sk-A's file refcount is bumped silently by MSG_PEEK,\nwhich invalidates the previous evaluation.\n\nAt this moment, sk-B's file refcount is 2; one by the open fd,\nand one by the inflight fd in sk-A.  The subsequent close()\nreleases one refcount by the former.\n\nFinally, GC incorrectly concludes that both sk-A and sk-B are dead.\n\nOne option is to restore the locking dance in unix_peek_fds(),\nbut we can resolve this more elegantly thanks to the new algorithm.\n\nThe point is that the issue does not occur without the subsequent\nclose() and we actually do not need to synchronise MSG_PEEK with\nthe dead SCC detection.\n\nWhen the issue occurs, close() and GC touch the same file refcount.\nIf GC sees the refcount being decremented by close(), it can just\ngive up garbage-collecting the SCC.\n\nTherefore, we only need to signal the race during MSG_PEEK with\na proper memory barrier to make it visible to the GC.\n\nLet's use seqcount_t to notify GC when MSG_PEEK occurs and let\nit defer the SCC to the next run.\n\nThis way no locking is needed on the MSG_PEEK side, and we can\navoid imposing a penalty on every MSG_PEEK unnecessarily.\n\nNote that we can retry within unix_scc_dead() if MSG_PEEK is\ndetected, but we do not do so to avoid hung task splat from\nabusive MSG_PEEK calls.","status":"published","published":"2026-03-25T10:33:18.18Z","modified":"2026-10-28T02:30:35.984019789Z","updated_at":"2026-11-02T15:44:59.079784Z"},{"id":"openSUSE-SU-2026:21388-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-10263: arm64: cputype: Add C1-Premium definitions (bsc#1266290).\n- CVE-2025-39894: netfilter: br_netfilter: do not check confirmed bit\n  in br_nf_local_in() after confirm (bsc#1262430).\n- CVE-2025-40341: futex: Don't leak robust_list pointer on exec race (bsc#1255029).\n- CVE-2026-23248: perf: Make perf_pmu_unregister() useable (bsc#1259800).\n- CVE-2026-23394: Revert: \"af_unix: Remove lock dance in unix_peek_fds().\" (bsc#1260565).\n- CVE-2026-23451: bonding: prevent potential infinite loop in bond_header_parse() (bsc#1261604).\n- CVE-2026-31414: netfilter: nf_conntrack_expect: use expect-\u003ehelper (bsc#1262085).\n- CVE-2026-31429: net: skb: fix cross-cache free of KFENCE-allocated skb head (bsc#1262392).\n- CVE-2026-31438: netfs: Fix kernel BUG in netfs_limit_iter() for ITER_KVEC iterators (bsc#1267824).\n- CVE-2026-31450: ext4: publish jinode after initialization (bsc#1262618).\n- CVE-2026-31452: ext4: convert inline data to extents when truncate exceeds inline size (bsc#1262620).\n- CVE-2026-31466: mm/huge_memory: fix folio isn't locked in softleaf_to_folio() (bsc#1267825).\n- CVE-2026-31469: virtio_net: Fix UAF on dst_ops when IFF_XMIT_DST_RELEASE is cleared and napi_tx is false\n  (bsc#1267816).\n- CVE-2026-31479: drm/xe: always keep track of remap prev/next (bsc#1262765).\n- CVE-2026-31492: RDMA/irdma: Initialize free_qp completion before using it (bsc#1262748).\n- CVE-2026-31495: netfilter: ctnetlink: use netlink policy range checks (bsc#1262798).\n- CVE-2026-31499: Bluetooth: L2CAP: Fix deadlock in l2cap_conn_del() (bsc#1262674).\n- CVE-2026-31502: team: fix header_ops type confusion with non-Ethernet ports (bsc#1263072).\n- CVE-2026-31555: futex: Clear stale exiting pointer in futex_lock_pi() retry path (bsc#1263178).\n- CVE-2026-31560: spi: spi-dw-dma: fix print error log when wait finish transaction (bsc#1263057).\n- CVE-2026-31596: ocfs2: handle invalid dinode in ocfs2_group_extend (bsc#1263319).\n- CVE-2026-31646: net: lan966x: fix page_pool error handling in lan966x_fdma_rx_alloc_page_pool() (bsc#1263796).\n- CVE-2026-31647: idpf: fix PREEMPT_RT raw/bh spinlock nesting for async VC handling (bsc#1263581).\n- CVE-2026-31663: xfrm: hold device only for the asynchronous decryption (bsc#1263133).\n- CVE-2026-31664: xfrm: clear trailing padding in build_polexpire() (bsc#1263578).\n- CVE-2026-31665: netfilter: nft_ct: fix use-after-free in timeout object destroy (bsc#1263137).\n- CVE-2026-31670: net: rfkill: prevent unlimited numbers of rfkill events from being created (bsc#1263573).\n- CVE-2026-31673: af_unix: read UNIX_DIAG_VFS data under unix_state_lock (bsc#1263143).\n- CVE-2026-31674: netfilter: ip6t_rt: reject oversized addrnr in rt_mt6_check() (bsc#1263568).\n- CVE-2026-31680: net: ipv6: flowlabel: defer exclusive option free until RCU teardown (bsc#1263563).\n- CVE-2026-31693: cifs: some missing initializations on replay (bsc#1267744).\n- CVE-2026-31743: nvmem: zynqmp_nvmem: Fix buffer size in DMA and memcpy (bsc#1264067).\n- CVE-2026-31752: bridge: br_nd_send: validate ND option lengths (bsc#1264045).\n- CVE-2026-31771: Bluetooth: hci_event: move wake reason storage into validated event handlers (bsc#1264145).\n- CVE-2026-43010: bpf: Reject sleepable kprobe_multi programs at attach time (bsc#1264015).\n- CVE-2026-43014,CVE-2026-43015: net: macb: fix clk handling on PCI glue driver removal (bsc#1264010 bsc#1264012).\n- CVE-2026-43016: bpf: sockmap: Fix use-after-free of sk-\u003esk_socket in sk_psock_verdict_data_ready() (bsc#1264007).\n- CVE-2026-43022: Bluetooth: hci_sync: hci_cmd_sync_queue_once() return -EEXIST if exists (bsc#1264001).\n- CVE-2026-43024: netfilter: nf_tables: reject immediate NF_QUEUE verdict (bsc#1263930).\n- CVE-2026-43028: netfilter: x_tables: ensure names are nul-terminated (bsc#1263934).\n- CVE-2026-43034: bnxt_en: set backing store type from query type (bsc#1263998).\n- CVE-2026-43035: net: sched: cls_api: fix tc_chain_fill_node to\n  initialize tcm_info to zero to prevent an info-leak (bsc#1263996).\n- CVE-2026-43036: net: use skb_header_pointer() for TCPv4 GSO frag_off check (bsc#1263993).\n- CVE-2026-43053: xfs: factor out xfs_attr3_node_entry_remove (bsc#1264084).\n- CVE-2026-43057: net: correctly handle tunneled traffic on IPV6_CSUM GSO fallback (bsc#1264056).\n- CVE-2026-43074: eventpoll: defer struct eventpoll free to RCU grace period (bsc#1264263).\n- CVE-2026-43080: l2tp: Drop large packets with UDP encap (bsc#1264236).\n- CVE-2026-43081: net: ipa: fix GENERIC_CMD register field masks for IPA v5.0+ (bsc#1264241).\n- CVE-2026-43083: net: ioam6: fix OOB and missing lock (bsc#1264266).\n- CVE-2026-43085: netfilter: nfnetlink_log: initialize nfgenmsg in NLMSG_DONE terminator (bsc#1264230).\n- CVE-2026-43086: ipvs: fix NULL deref in ip_vs_add_service error path (bsc#1264286).\n- CVE-2026-43089: xfrm_user: fix info leak in build_mapping() (bsc#1264261).\n- CVE-2026-43090: xfrm: fix refcount leak in xfrm_migrate_policy_find (bsc#1264250).\n- CVE-2026-43092: xsk: validate MTU against usable frame size on bind (bsc#1264270).\n- CVE-2026-43093: xsk: tighten UMEM headroom validation to account for tailroom and min frame (bsc#1264254).\n- CVE-2026-43094: ixgbevf: add missing negotiate_features op to Hyper-V ops table (bsc#1264231).\n- CVE-2026-43101: ipv6: ioam: fix potential NULL dereferences in __ioam6_fill_trace_data() (bsc#1264239).\n- CVE-2026-43107: xfrm: account XFRMA_IF_ID in aevent size calculation (bsc#1264258).\n- CVE-2026-43119: Bluetooth: hci_sync: annotate data-races around hdev-\u003ereq_status (bsc#1264561).\n- CVE-2026-43124: pstore: ram_core: fix incorrect success return when vmap() fails (bsc#1264545).\n- CVE-2026-43128: RDMA/umem: Fix double dma_buf_unpin in failure path (bsc#1264612).\n- CVE-2026-43130: iommu/vt-d: Flush dev-IOTLB only when PCIe device is accessible in scalable mode (bsc#1264532).\n- CVE-2026-43132: dm-verity: correctly handle dm_bufio_client_create() failure (bsc#1264614).\n- CVE-2026-43139: xfrm6: fix uninitialized saddr in xfrm6_get_saddr() (bsc#1264294).\n- CVE-2026-43145: remoteproc: imx_rproc: Fix invalid loaded resource table detection (bsc#1265091).\n- CVE-2026-43157: octeontx2-af: CGX: fix bitmap leaks (bsc#1264624).\n- CVE-2026-43158: xfs: fix freemap adjustments when adding xattrs to leaf blocks (bsc#1264595).\n- CVE-2026-43161: iommu/vt-d: Skip dev-iotlb flush for inaccessible PCIe device without scalable mode (bsc#1264333).\n- CVE-2026-43167: xfrm: always flush state and policy upon NETDEV_UNREGISTER event (bsc#1264580).\n- CVE-2026-43171: EFI/CPER: don't dump the entire memory region (bsc#1264549).\n- CVE-2026-43175: clk: rs9: Reserve 8 struct clk_hw slots for for 9FGV0841 (bsc#1264372).\n- CVE-2026-43187: xfs: delete attr leaf freemap entries when empty (bsc#1264603).\n- CVE-2026-43191: drm/amd/display: Adjust PHY FSM transition to TX_EN-to-PLL_ON for TMDS on DCN35 (bsc#1264548).\n- CVE-2026-43194: net: consume xmit errors of GSO frames (bsc#1264304).\n- CVE-2026-43198: tcp: fix potential race in tcp_v6_syn_recv_sock() (bsc#1264610).\n- CVE-2026-43199: net/mlx5e: Fix \"scheduling while atomic\" in IPsec MAC address query (bsc#1264556).\n- CVE-2026-43205: dpaa2-switch: validate num_ifs to prevent out-of-bounds write (bsc#1264328).\n- CVE-2026-43213: wifi: rtw89: pci: validate sequence number of TX release report (bsc#1264643).\n- CVE-2026-43226: net/rds: No shortcut out of RDS_CONN_ERROR (bsc#1264544).\n- CVE-2026-43233: netfilter: nf_conntrack_h323: fix OOB read in decode_choice() (bsc#1264337).\n- CVE-2026-43238: net/sched: act_skbedit: fix divide-by-zero in tcf_skbedit_hash() (bsc#1264320).\n- CVE-2026-43240: ima: verify the previous kernel's IMA buffer lies in addressable RAM (bsc#1264386).\n- CVE-2026-43248: vhost: move vdpa group bound check to vhost_vdpa (bsc#1264302).\n- CVE-2026-43260: bnxt_en: Fix RSS context delete logic (bsc#1264429).\n- CVE-2026-43283: net: ethernet: ec_bhf: Fix dma_free_coherent() dma handle (bsc#1264295).\n- CVE-2026-43298: drm/amdgpu: Skip vcn poison irq release on VF (bsc#1264852).\n- CVE-2026-43303: mm/page_alloc: clear page-\u003eprivate in free_pages_prepare() (bsc#1264974).\n- CVE-2026-43336: lib/crypto: chacha: Zeroize permuted_state before it leaves scope (bsc#1265113).\n- CVE-2026-43337: drm/amd/display: Fix NULL pointer dereference in dcn401_init_hw() (bsc#1265112).\n- CVE-2026-43339: ipv6: prevent possible UaF in addrconf_permanent_addr() (bsc#1264763).\n- CVE-2026-43345: net: ipa: fix event ring index not programmed for IPA v5.0+ (bsc#1265103).\n- CVE-2026-43351: KVM: arm64: gic: Set vgic_model before initing private IRQs (bsc#1265082).\n- CVE-2026-43373: net: ncsi: fix skb leak in error paths (bsc#1265079).\n- CVE-2026-43374: net: nexthop: fix percpu use-after-free in remove_nh_grp_entry (bsc#1265084).\n- CVE-2026-43383: net/tcp-md5: Fix MAC comparison to be constant-time (bsc#1264744).\n- CVE-2026-43384: net/tcp-ao: Fix MAC comparison to be constant-time (bsc#1265097).\n- CVE-2026-43386: staging: rtl8723bs: fix potential out-of-bounds read in rtw_restruct_wmm_ie (bsc#1264740).\n- CVE-2026-43403: nsfs: tighten permission checks for ns iteration ioctls (bsc#1265129).\n- CVE-2026-43405: libceph: Use u32 for non-negative values in ceph_monmap_decode() (bsc#1264741).\n- CVE-2026-43406: libceph: prevent potential out-of-bounds reads in process_message_header() (bsc#1265073).\n- CVE-2026-43407: libceph: Fix potential out-of-bounds access in ceph_handle_auth_reply() (bsc#1265020).\n- CVE-2026-43415: scsi: ufs: core: Fix SError in ufshcd_rtc_work() during UFS suspend (bsc#1265123).\n- CVE-2026-43449: nvme-pci: Fix slab-out-of-bounds in nvme_dbbuf_set (bsc#1265023).\n- CVE-2026-43450: netfilter: nfnetlink_cthelper: fix OOB read in nfnl_cthelper_dump_table() (bsc#1264794).\n- CVE-2026-43452: netfilter: x_tables: guard option walkers against 1-byte tail reads (bsc#1265142).\n- CVE-2026-43456: bonding: fix type confusion in bond_setup_by_slave() (bsc#1264734).\n- CVE-2026-43457: mctp: i2c: fix skb memory leak in receive path (bsc#1265000).\n- CVE-2026-43458: serial: caif: hold tty-\u003elink reference in ldisc_open and ser_release (bsc#1265005).\n- CVE-2026-43465: net/mlx5e: RX, Fix XDP multi-buf frag counting for striding RQ (bsc#1264997).\n- CVE-2026-43466: net/mlx5e: Fix DMA FIFO desync on error CQE SQ recovery (bsc#1264790).\n- CVE-2026-43468: net/mlx5: Fix deadlock between devlink lock and esw-\u003ewq (bsc#1264978).\n- CVE-2026-43469: xprtrdma: Decrement re_receiving on the early exit paths (bsc#1265143).\n- CVE-2026-43470: nfs: return EISDIR on nfs3_proc_create if d_alias is a dir (bsc#1265128).\n- CVE-2026-43471: scsi: ufs: core: Fix possible NULL pointer dereference in ufshcd_add_command_trace() (bsc#1264789).\n- CVE-2026-43491: net: qrtr: ns: Limit the maximum server registration per node (bsc#1265628).\n- CVE-2026-43492: lib/crypto: mpi: Fix integer underflow in mpi_read_raw_from_sgl() (bsc#1265629).\n- CVE-2026-43502: net/rds: handle zerocopy send cleanup before the message is queued (bsc#1266008).\n- CVE-2026-45837: Require (reasonably) normal mappings for MADV_DOFORK (bsc#1266398).\n- CVE-2026-45838: bpf: fix end-of-list detection in cgroup_storage_get_next_key() (bsc#1266396).\n- CVE-2026-45840: openvswitch: cap upcall PID array size and pre-size vport replies (bsc#1266397).\n- CVE-2026-45841: netfilter: nfnetlink_osf: fix divide-by-zero in OSF_WSS_MODULO (bsc#1266390).\n- CVE-2026-45848: apparmor: fix NULL sock in aa_sock_file_perm (bsc#1266734).\n- CVE-2026-45857: scsi: csiostor: Fix dereference of null pointer rn (bsc#1266458).\n- CVE-2026-45858: ext4: don't zero the entire extent if EXT4_EXT_DATA_PARTIAL_VALID1 (bsc#1266773).\n- CVE-2026-45861: gfs2: Fix slab-use-after-free in qd_put (bsc#1266754).\n- CVE-2026-45862: iommu/vt-d: Flush cache for PASID table before using it (bsc#1266705).\n- CVE-2026-45870: SUNRPC: auth_gss: fix memory leaks in XDR decoding error paths (bsc#1266704).\n- CVE-2026-45884: apparmor: avoid per-cpu hold underflow in aa_get_buffer (bsc#1266718).\n- CVE-2026-45888: md/raid1: fix memory leak in raid1_run() (bsc#1266761).\n- CVE-2026-45891: net: hns3: fix double free issue for tx spare buffer (bsc#1266717).\n- CVE-2026-45894: iommu/vt-d: Clear Present bit before tearing down PASID entry (bsc#1266895).\n- CVE-2026-45899: ext4: drop extent cache when splitting extent fails (bsc#1266883).\n- CVE-2026-45901: netfilter: nf_tables: revert commit_mutex usage in reset path (bsc#1266892).\n- CVE-2026-45912: ext4: don't cache extent during splitting extent (bsc#1266899).\n- CVE-2026-45920: ext4: fix dirtyclusters double decrement on fs shutdown (bsc#1266893).\n- CVE-2026-45922: RDMA/mlx5: Fix memory leak in GET_DATA_DIRECT_SYSFS_PATH handler (bsc#1266805).\n- CVE-2026-45933: bpf: Preserve id of register in sync_linked_regs() (bsc#1266693).\n- CVE-2026-45940: net: stmmac: fix oops when split header is enabled (bsc#1266916).\n- CVE-2026-45948: ext4: fix memory leak in ext4_ext_shift_extents() (bsc#1266929).\n- CVE-2026-45961: gfs2: fix memory leaks in gfs2_fill_super error path (bsc#1266933).\n- CVE-2026-45964: SUNRPC: fix gss_auth kref leak in gss_alloc_msg error path (bsc#1266698).\n- CVE-2026-45965: apparmor: fix invalid deref of rawdata when export_binary is unset (bsc#1267208).\n- CVE-2026-45974: btrfs: fix invalid leaf access in btrfs_quota_enable() if ref key not found (bsc#1266922).\n- CVE-2026-45983: nfsd: never defer requests during idmap lookup (bsc#1266697).\n- CVE-2026-45985: ext4: don't set EXT4_GET_BLOCKS_CONVERT when splitting before submitting I/O (bsc#1266700).\n- CVE-2026-45997: scsi: sd: fix missing put_disk() when device_add(\u0026disk_dev) fails (bsc#1266740).\n- CVE-2026-45999: erofs: fix unsigned underflow in z_erofs_lz4_handle_overlap() (bsc#1266750).\n- CVE-2026-46005: xfs: fix a resource leak in xfs_alloc_buftarg() (bsc#1267431).\n- CVE-2026-46024: libceph: Prevent potential null-ptr-deref in ceph_handle_auth_reply() (bsc#1267218).\n- CVE-2026-46037: ipv4: icmp: validate reply type before using icmp_pointers (bsc#1267361).\n- CVE-2026-46046: ext4: fix missing brelse() in ext4_xattr_inode_dec_ref_all() (bsc#1266726).\n- CVE-2026-46050: md/raid10: fix deadlock with check operation and nowait requests (bsc#1266686).\n- CVE-2026-46051: md/raid5: fix soft lockup in retry_aligned_read() (bsc#1267360).\n- CVE-2026-46053: net: rds: fix MR cleanup on copy error (bsc#1267427).\n- CVE-2026-46063: x86/shstk: Prevent deadlock during shstk sigreturn (bsc#1267228).\n- CVE-2026-46065: fbdev: defio: Disconnect deferred I/O from the lifetime of struct (bsc#1267458).\n- CVE-2026-46069: wifi: mwifiex: fix use-after-free in mwifiex_adapter_cleanup() (bsc#1267437).\n- CVE-2026-46071: KVM: nSVM: Avoid clearing VMCB_LBR in vmcb12 (bsc#1267591).\n- CVE-2026-46076: KVM: nSVM: Raise #UD if unhandled VMMCALL isn't intercepted by L1 (bsc#1267365).\n- CVE-2026-46078: erofs: fix the out-of-bounds nameoff handling for trailing dirents (bsc#1267505).\n- CVE-2026-46079: rbd: fix null-ptr-deref when device_add_disk() fails (bsc#1266452).\n- CVE-2026-46091: media: rc: igorplugusb: heed coherency rules (bsc#1267238).\n- CVE-2026-46093: mm/vmalloc: take vmap_purge_lock in shrinker (bsc#1267548).\n- CVE-2026-46099: net: ipv6: fix NOREF dst use in seg6 and rpl lwtunnels (bsc#1266722).\n- CVE-2026-46101: netfilter: reject zero shift in nft_bitwise (bsc#1266878).\n- CVE-2026-46111: Bluetooth: hci_conn: fix potential UAF in create_big_sync (bsc#1267626).\n- CVE-2026-46112: RDMA/hns: Fix unlocked call to hns_roce_qp_remove() (bsc#1267582).\n- CVE-2026-46116: xfrm: defensively unhash xfrm_state lists in __xfrm_state_delete (bsc#1267369).\n- CVE-2026-46119: libceph: Fix slab-out-of-bounds access in auth message processing (bsc#1267628).\n- CVE-2026-46120: ip6_gre: Use cached t-\u003enet in ip6erspan_changelink() (bsc#1267640).\n- CVE-2026-46124: isofs: validate block number from NFS file handle in isofs_export_iget (bsc#1266847).\n- CVE-2026-46150: fanotify: fix false positive on permission events (bsc#1267387).\n- CVE-2026-46160: btrfs: fix missing last_unlink_trans update when removing a directory (bsc#1267624).\n- CVE-2026-46161: md/raid10: fix divide-by-zero in setup_geo() with zero far_copies (bsc#1266838).\n- CVE-2026-46162: ice: fix double free in ice_sf_eth_activate() error path (bsc#1266840).\n- CVE-2026-46172: ipv6: xfrm6: release dst on error in xfrm6_rcv_encap() (bsc#1266903).\n- CVE-2026-46173: exit: prevent preemption of oopsing TASK_DEAD task (bsc#1267722).\n- CVE-2026-46178: RDMA/mlx4: Fix resource leak on error in mlx4_ib_create_srq() (bsc#1267493).\n- CVE-2026-46185: smb/client: fix out-of-bounds read in symlink_data() (bsc#1266830).\n- CVE-2026-46214: vsock/virtio: fix accept queue count leak on transport mismatch (bsc#1267717).\n- CVE-2026-46227: sctp: revalidate list cursor after sctp_sendmsg_to_asoc() in SCTP_SENDALL (bsc#1267697).\n- CVE-2026-46242: eventpoll: Fix integer overflow in ep_loop_check_proc() (bsc#1267618).\n- CVE-2026-46244: netfilter: nft_inner: Fix IPv6 inner_thoff desync (bsc#1267654).\n- CVE-2026-46253: pstore/ram: fix buffer overflow in persistent_ram_save_old() (bsc#1267635).\n- CVE-2026-46254: AppArmor: Allow apparmor to handle unaligned dfa tables (bsc#1267637).\n- CVE-2026-46259: procfs: fix missing RCU protection when reading real_parent in do_task_stat() (bsc#1267685).\n- CVE-2026-46266: inet: RAW sockets using IPPROTO_RAW MUST drop incoming ICMP (bsc#1267684).\n- CVE-2026-46289: lib/scatterlist: fix length calculations in extract_kvec_to_sg (bsc#1267966).\n- CVE-2026-46291: printk: add print_hex_dump_devel() (bsc#1267937).\n- CVE-2026-46314: drm/v3d: Reject empty multisync extension to prevent infinite loop (bsc#1267992).\n- CVE-2026-46319: net/sched: act_ct: Only release RCU read lock after ct_ft (bsc#1268022).\n- CVE-2026-46320: tap: free page on error paths in tap_get_user_xdp() (bsc#1267993).\n- CVE-2026-46322: tun: free page on build_skb failure in tun_xdp_one() (bsc#1267994).\n- CVE-2026-46328: apparmor: fix rlimit for posix cpu timers (bsc#1268037).\n- CVE-2026-52908: RDMA: During rereg_mr ensure that REREG_ACCESS is compatible (bsc#1268661).\n- CVE-2026-52909: ip6_vti: set netns_immutable on the fallback device (bsc#1268660).\n- CVE-2026-52919: batman-adv: fix tp_meter counter underflow during shutdown (bsc#1269031).\n- CVE-2026-52923: ipc: limit next_id allocation to the valid ID range (bsc#1269033).\n- CVE-2026-52924: sctp: purge outqueue on stale COOKIE-ECHO handling (bsc#1269036).\n- CVE-2026-52933: io_uring/poll: fix signed comparison in io_poll_get_ownership() (bsc#1268989).\n- CVE-2026-52943: net: skbuff: fix missing zerocopy reference in pskb_carve helpers (bsc#1269022).\n- CVE-2026-52954: libceph: handle rbtree insertion error in decode_choose_args() (bsc#1269137).\n- CVE-2026-52955: libceph: Fix potential out-of-bounds access in crush_decode() (bsc#1269159).\n- CVE-2026-52957: libceph: Fix potential null-ptr-deref in decode_choose_args() (bsc#1269103).\n- CVE-2026-52962: ceph: fix a buffer leak in __ceph_setxattr() (bsc#1269135).\n- CVE-2026-52975: bonding: 3ad: implement proper RCU rules for port-\u003eaggregator (bsc#1269234).\n- CVE-2026-52980: sched/fair: Clear rel_deadline when initializing forked entities (bsc#1269252).\n- CVE-2026-52993: tipc: fix double-free in tipc_buf_append() (bsc#1269193).\n- CVE-2026-53015: erofs: unify lcn as u64 for 32-bit platforms (bsc#1269087).\n- CVE-2026-53021: scsi: target: core: Fix integer overflow in UNMAP bounds check (bsc#1269151).\n- CVE-2026-53036: bpf, arm64: Reject out-of-range B.cond targets (bsc#1269389).\n- CVE-2026-53039: ocfs2: validate group add input before caching (bsc#1269392).\n- CVE-2026-53040: ocfs2: validate bg_bits during freefrag scan (bsc#1269397).\n- CVE-2026-53041: ocfs2: fix listxattr handling when the buffer is full (bsc#1269398).\n- CVE-2026-53049: gfs2: add some missing log locking (bsc#1269646).\n- CVE-2026-53050: quota: Fix race of dquot_scan_active() with quota deactivation (bsc#1269188).\n- CVE-2026-53053: iommu/amd: Fix clone_alias() to use the original device's devid (bsc#1269310).\n- CVE-2026-53060: dm cache metadata: fix memory leak on metadata abort retry (bsc#1269164).\n- CVE-2026-53075: ppp: require CAP_NET_ADMIN in target netns for unattached ioctls (bsc#1269690).\n- CVE-2026-53078: bpf: Fix same-register dst/src OOB read and pointer leak in sock_ops (bsc#1269700).\n- CVE-2026-53081: bpf: Enforce regsafe base id consistency for BPF_ADD_CONST scalars (bsc#1269708).\n- CVE-2026-53086: net: bcmgenet: move DESC_INDEX flow to ring 0 (bsc#1269537).\n- CVE-2026-53090: bpf: Fix ld_{abs,ind} failure path analysis in subprogs (bsc#1269532).\n- CVE-2026-53103: wifi: mt76: mt7925: fix potential deadlock in mt7925_roc_abort_sync (bsc#1269416).\n- CVE-2026-53122: btrfs: fix deadlock between reflink and transaction commit when using flushoncommit (bsc#1269418).\n- CVE-2026-53133: RDMA/umem: Fix truncation for block sizes \u003e= 4G (bsc#1269821).\n- CVE-2026-53139: drm/v3d: Skip CSD when it has zeroed workgroups (bsc#1269262).\n- CVE-2026-53156: nvmem: core: fix use-after-free bugs in error paths (bsc#1269288).\n- CVE-2026-53167: fuse: limit FUSE_NOTIFY_RETRIEVE to uptodate folios (bsc#1269768).\n- CVE-2026-53168: fuse: reject fuse_notify() pagecache ops on directories (bsc#1269645).\n- CVE-2026-53176: IB/isert: Reject login PDUs shorter than ISER_HEADERS_LEN (bsc#1269710).\n- CVE-2026-53178: staging: rtl8723bs: rtw_mlme: add bounds checks before ie_length subtraction (bsc#1269795).\n- CVE-2026-53215: net: mvpp2: refill RX buffers before XDP or skb use (bsc#1269680).\n- CVE-2026-53216: net: mvpp2: limit XDP frame size to the RX buffer (bsc#1269587).\n- CVE-2026-53217: net: mvpp2: sync RX data at the hardware packet offset (bsc#1269989).\n- CVE-2026-53229: net/mlx5e: xsk: Fix DMA and xdp_frame leak on XDP_TX xmit failure (bsc#1269691).\n- CVE-2026-53249: ipv4: restrict IPOPT_SSRR and IPOPT_LSRR options (bsc#1269992).\n- CVE-2026-53258: wifi: fix leak if split 6 GHz scanning fails (bsc#1269230).\n- CVE-2026-53262: l2tp: pppol2tp: hold reference to session in pppol2tp_ioctl() (bsc#1270000).\n- CVE-2026-53263: 6lowpan: fix off-by-one in multicast context address compression (bsc#1269647).\n- CVE-2026-53266: netfilter: bridge: make ebt_snat ARP rewrite writable (bsc#1269136).\n- CVE-2026-53272: erofs: fix use-after-free on sbi-\u003esync_decompress (bsc#1269809).\n- CVE-2026-53274: net/smc: fix sleep-inside-lock in __smc_setsockopt() causing local DoS (bsc#1269651).\n- CVE-2026-53281: iommu/vt-d: Avoid NULL pointer dereference or refcount corruption (bsc#1269519).\n- CVE-2026-53285: drm/amd/display: Wrap DCN32 phantom-plane allocation in DC_RUN_WITH_PREEMPTION_ENABLED (bsc#1269527).\n- CVE-2026-53286: idpf: fix double free and use-after-free in aux device error paths (bsc#1269531).\n- CVE-2026-53287: audit: fix incorrect inheritable capability in CAPSET records (bsc#1269506).\n- CVE-2026-53306: tty: hvc_iucv: fix off-by-one in number of supported devices (bsc#1269814).\n\nThe following non security issues were fixed:\n\n- accel/ivpu: Fix signed integer truncation in IPC receive (git-fixes).\n- ACPI: CPPC: Suppress UBSAN warning caused by field misuse (git-fixes).\n- ACPI: IPMI: Fix inverted interface check in ipmi_bmc_gone() (git-fixes).\n- ACPI: IPMI: Fix message kref handling on dead device (git-fixes).\n- ACPI: NFIT: core: Fix possible NULL pointer dereference (git-fixes).\n- ACPI: resource: Amend kernel-doc style (git-fixes).\n- agp/amd64: Fix broken error propagation in agp_amd64_probe() (git-fixes).\n- ALSA: aloop: Drop superfluous break (git-fixes).\n- ALSA: caiaq: fix out-of-bounds read in the Traktor Kontrol S4 input parser (git-fixes).\n- ALSA: cmipci: check snd_ctl_new1() return value (git-fixes).\n- ALSA: core: Fix unintuitive behavior of snd_power_ref_and_wait() (git-fixes).\n- ALSA: es1938: check snd_ctl_new1() return value (git-fixes).\n- ALSA: firewire: isight: bound the sample count to the packet payload (git-fixes).\n- ALSA: gus: check snd_ctl_new1() return value (git-fixes).\n- ALSA: hda/cs35l41: Fix firmware load work teardown (git-fixes).\n- ALSA: ice1712: check snd_ctl_new1() return value (git-fixes).\n- ALSA: scarlett2: Allow flash writes ending at segment boundary (git-fixes).\n- ALSA: scarlett2: Return ENOSPC for out-of-bounds flash writes (stable-fixes).\n- ALSA: seq: Clear variable event pointer on read (git-fixes).\n- ALSA: seq: Fix kernel heap address leak in bounce_error_event() (git-fixes).\n- ALSA: seq: Fix partial userptr event expansion (git-fixes).\n- ALSA: seq: Fix uninitialised heap leak in snd_seq_event_dup() (git-fixes).\n- ALSA: seq: midi: Serialize output teardown with event_input (git-fixes).\n- ALSA: timer: Fix UAF at snd_timer_user_params() (stable-fixes).\n- ALSA: timer: Forcibly close timer instances at closing (git-fixes).\n- ALSA: usb-audio: avoid kobject path lookup in DualSense match (git-fixes).\n- ALSA: usb-audio: Kill MIDI 2.0 URBs before freeing endpoints (git-fixes).\n- ALSA: usb-audio: Propagate errors in scarlett_ctl_enum_put() (git-fixes).\n- ALSA: usb-audio: Propagate US-16x08 write errors in route/mix EQ-switch put callbacks (git-fixes).\n- ALSA: usb-audio: Roll back quirk control caches on write errors (git-fixes).\n- ALSA: usb-audio: Update Babyface Pro control caches only after successful writes (git-fixes).\n- ALSA: usb-audio: Update US-16x08 EQ/comp shadow state after successful writes (git-fixes).\n- ALSA: virtio: Add missing 384 kHz PCM rate mapping (git-fixes).\n- ALSA: virtio: Validate control metadata from the device (git-fixes).\n- ALSA: ymfpci: check snd_ctl_new1() return value (git-fixes).\n- arm64: scripts/sorttable: Implement sorting mcount_loc at boot for arm64 (bsc#1267600).\n- ASoC: adau1372: Clear PLL_EN on failed PLL lock without reset GPIO (git-fixes).\n- ASoC: amd: acp-sdw-sof: Bound DAI link iteration (git-fixes).\n- ASoC: codecs: aw88261: fix incorrect masks for boost regs (git-fixes).\n- ASoC: codecs: hdac_hdmi: Validate written enum value (git-fixes).\n- ASoC: cs35l56: Cleanup if component_probe fails (git-fixes).\n- ASoC: cs35l56: Don't leave parent IRQ disabled if system_suspend fails (git-fixes).\n- ASoC: cs35l56: Fix missing calls to wm_adsp2_remove() (git-fixes).\n- ASoC: cs35l56: Fix possible uninitialized value in cs35l56_spi_system_reset() (git-fixes).\n- ASoC: fsl: fsl_audmix: Validate written enum values (git-fixes).\n- ASoC: fsl_asrc_dma: fix eDMA maxburst misalignment with channel count (git-fixes).\n- ASoC: mediatek: mt8183: Release reserved memory on cleanup (git-fixes).\n- ASoC: mediatek: mt8192: Release reserved memory on cleanup (git-fixes).\n- ASoC: meson: aiu: Validate written enum values (git-fixes).\n- ASoC: qcom: q6apm: fix NULL pointer dereference in graph_callback (git-fixes).\n- ASoC: SOF: ipc3-control: Fix heap overflow in bytes_ext put/get (git-fixes).\n- ASoC: SOF: ipc3-control: Fix TOCTOU in bytes_put and bytes_get (git-fixes).\n- ASoC: SOF: ipc3-control: Use overflow checks in control_update size calc (git-fixes).\n- ASoC: SOF: ipc3-control: Validate size in snd_sof_update_control (git-fixes).\n- ASoC: SOF: ipc4-control: Fix TOCTOU in sof_ipc4_bytes_put (git-fixes).\n- ASoC: SOF: topology: validate vendor array size before parsing (git-fixes).\n- ASoC: tegra: tegra210_ahub: Validate written enum value (git-fixes).\n- ASoC: tlv320aic3x: restrict CLKDIV bypass Q values in dual-rate mode (git-fixes).\n- ASoC: topology: Check PCM and DAI name strings before use (git-fixes).\n- ASoC: wm_adsp: Fix NULL dereference when removing firmware controls (git-fixes).\n- Bluetooth: 6lowpan: hold L2CAP conn across debugfs control (git-fixes).\n- Bluetooth: bnep: pin L2CAP connection during netdev registration (git-fixes).\n- Bluetooth: bpa10x: avoid OOB read of revision string in bpa10x_setup() (git-fixes).\n- Bluetooth: btmtk: fix URB leak in alloc_mtk_intr_urb error path (git-fixes).\n- Bluetooth: btmtksdio: fix infinite loop in btmtksdio_txrx_work() (git-fixes).\n- Bluetooth: btnxpuart: Fix out-of-bounds firmware read in nxp_recv_fw_req_v3() (git-fixes).\n- Bluetooth: btusb: fix use-after-free on marvell probe failure (git-fixes).\n- Bluetooth: btusb: fix use-after-free on registration failure (git-fixes).\n- Bluetooth: btusb: fix wakeup irq devres lifetime (git-fixes).\n- Bluetooth: btusb: fix wakeup source leak on probe failure (git-fixes).\n- Bluetooth: eir: Fix stack OOB write when prepending the Flags AD (git-fixes).\n- Bluetooth: fix UAF in bt_accept_dequeue() (git-fixes).\n- Bluetooth: hci: validate codec capability element length (git-fixes).\n- Bluetooth: hci_core: Fix UAF in hci_unregister_dev() (git-fixes).\n- Bluetooth: hci_qca: fix NULL pointer dereference in qca_dmp_hdr() for non-serdev device (git-fixes).\n- Bluetooth: hci_uart: clear HCI_UART_SENDING when write_work is canceled (git-fixes).\n- Bluetooth: ISO: avoid NULL deref of conn in iso_conn_big_sync() (git-fixes).\n- Bluetooth: ISO: exclude RFU bits from ISO_SDU_Length (git-fixes).\n- Bluetooth: ISO: Fix data-race on iso_pi fields in hci_get_route calls (git-fixes).\n- Bluetooth: ISO: fix malformed ISO_END/CONT handling (git-fixes).\n- Bluetooth: ISO: Fix not using bc_sid as advertisement SID (stable-fixes).\n- Bluetooth: L2CAP: reject BR/EDR signaling packets over MTUsig (stable-fixes).\n- Bluetooth: L2CAP: validate option length before reading conf opt value (git-fixes).\n- Bluetooth: MGMT: Fix adv monitor add failure cleanup (git-fixes).\n- Bluetooth: MGMT: Fix UAF of hci_conn_params in add_device_complete (git-fixes).\n- Bluetooth: sco: Fix a race condition in sco_sock_timeout() (git-fixes).\n- Bluetooth: vhci: validate devcoredump state before side effects (git-fixes).\n- bnxt_en: Fix NULL pointer dereference (bsc#1268307).\n- bpf: Free reuseport cBPF prog after RCU grace period (git-fixes).\n- bus: mhi: ep: Add missing state_lock protection for mhi_state access (git-fixes).\n- bus: mhi: ep: Fix potential deadlock in mhi_ep_reset_worker() (git-fixes).\n- bus: mhi: ep: Protect mhi_ep_handle_syserr() in the error path (git-fixes).\n- char: tlclk: fix use-after-free in tlclk_cleanup() (git-fixes).\n- crypto/hmac: reject keys shorter than 128 bits in fips mode (bsc#1266284 jsc#PED-15986).\n- crypto/testmgr: disallow ffdhe2048 in fips mode (bsc#1266284 jsc#PED-15986).\n- crypto/testmgr: disallow plain ecb() usage in fips mode (bsc#1266284 jsc#PED-15986).\n- crypto/testmgr: disallow sha224 + sha3-224 in fips mode (bsc#1266284 jsc#PED-15986).\n- crypto: af_alg - Cap AEAD AD length to 0x80000000 (git-fixes).\n- crypto: amlogic - avoid double cleanup in meson_crypto_probe() (git-fixes).\n- crypto: asymmetric_keys - fix OOB read in pefile_digest_pe_contents (git-fixes).\n- crypto: atmel-sha204a - fix blocking and non-blocking rng logic (git-fixes).\n- crypto: cavium/cpt - fix DMA cleanup using wrong loop index (git-fixes).\n- crypto: ccp - Do not initialize SNP for ioctl(SNP_COMMIT) (git-fixes).\n- crypto: ccp - Do not initialize SNP for ioctl(SNP_VLEK_LOAD) (git-fixes).\n- crypto: ccp - Do not initialize SNP for SEV ioctls (git-fixes).\n- crypto: ccp - Fix snp_filter_reserved_mem_regions() off-by-one (git-fixes).\n- crypto: ccp - Treat zero-length cert chain as query for blob lengths (git-fixes).\n- crypto: drbg - Fix drbg_max_addtl() on 64-bit kernels (git-fixes).\n- crypto: drbg - Fix returning success on failure in CTR_DRBG (git-fixes).\n- crypto: drbg - Fix the fips_enabled priority boost (git-fixes).\n- crypto: ecc - Fix carry overflow in vli multiplication (git-fixes).\n- crypto: ecrdsa - fix unknown OID check in ecrdsa_param_curve (git-fixes).\n- crypto: hisilicon/qm - disable error report before flr (git-fixes).\n- crypto: marvell/octeontx - fix DMA cleanup using wrong loop index (git-fixes).\n- crypto: pcrypt - restore callback for non-parallel fallback (git-fixes).\n- crypto: qat - protect service table iterations with service_lock (git-fixes).\n- crypto: qat - validate RSA CRT component lengths (git-fixes).\n- crypto: rng - Free default RNG on module exit (git-fixes).\n- crypto: tegra - Fix dma_free_coherent size error (git-fixes).\n- crypto: tegra - fix refcount leak in tegra_se_host1x_submit() (git-fixes).\n- crypto: tegra - Return ENOMEM when input buffer allocation fails for ccm (git-fixes).\n- dm init: ensure device probing has finished in dm-mod.waitfor= (git-fixes).\n- dmaengine: dma-axi-dmac: Properly free struct axi_dmac_desc (git-fixes).\n- dmaengine: dma-axi-dmac: use DMA pool to manange DMA descriptor (git-fixes).\n- dmaengine: dw-edma: Add spinlock to protect DONE_INT_MASK and ABORT_INT_MASK (git-fixes).\n- dmaengine: Fix possible use after free (git-fixes).\n- dmaengine: imx-sdma: Refine spba bus searching in probe (git-fixes).\n- dmaengine: qcom: gpi: set DMA_PRIVATE capability (git-fixes).\n- dmaengine: tegra: Fix burst size calculation (git-fixes).\n- driver core: reject devices with unregistered buses (git-fixes).\n- driver core: use READ_ONCE() for dev-\u003edriver in dev_has_sync_state() (git-fixes).\n- Drivers: hv: vmbus: Improve the logic of reserving fb_mmio on Gen2 VMs (git-fixes).\n- drm/amd/display: add missing CSC entries for BT.2020 for DCE IPs (stable-fixes).\n- drm/amd/display: Add missing kdoc for ALLM parameters (git-fixes).\n- drm/amd/display: Clamp VBIOS HDMI retimer register count to array size (stable-fixes).\n- drm/amd/pm: fix smu13 power limit default/cap calculation (stable-fixes).\n- drm/amd/pm: mark metrics.energy_accumulator is invalid for smu 14.0.2 (stable-fixes).\n- drm/amd/pm: remove trailing semicolon from AMDGPU_PM_POLICY_ATTR macro (git-fixes).\n- drm/amd/pm: smu_v14_0_0: use SoftMin for gfxclk in set_soft_freq_limited_range (stable-fixes).\n- drm/amdgpu: Fix amdgpu_bo_move() when old_mem and new_mem are both GTT (git-fixes).\n- drm/amdgpu: fix integer overflow in amdgpu_gem_align_pitch() (git-fixes).\n- drm/amdgpu: initialize irq.lock spinlock earlier (git-fixes).\n- drm/amdgpu: restart the CS if some parts of the VM are still invalidated (stable-fixes).\n- drm/amdgpu: set sub_block_index for mca ras sub-blocks (git-fixes).\n- drm/amdgpu: skip already suspended IP blocks in ip_suspend_phase2 (git-fixes).\n- drm/amdgpu: validate CP_GFX_SHADOW chunk size in CS pass1 (git-fixes).\n- drm/amdkfd: always resume_all after suspend_all (git-fixes).\n- drm/amdkfd: Avoid double-unpin of DOORBELL/MMIO BOs on free (git-fixes).\n- drm/amdkfd: Check for pdd drm file first in CRIU restore path (stable-fixes).\n- drm/amdkfd: fix list_del corruption in kfd_criu_resume_svm (git-fixes).\n- drm/amdkfd: fix NULL pointer bug in svm_range_set_attr (stable-fixes).\n- drm/amdkfd: Use exclusive bounds for SVM split alignment checks (git-fixes).\n- drm/amdkfd: Validate CRIU-restored IDs before idr_alloc (git-fixes).\n- drm/bridge: cdns-dsi: Replace deprecated UNIVERSAL_DEV_PM_OPS() (git-fixes).\n- drm/dp/mst: fix buffer overflows in sideband chunk accumulation (git-fixes).\n- drm/dp/mst: fix OOB reads in remote DPCD/I2C sideband reply parsers (git-fixes).\n- drm/dp/mst: fix OOB reads on 2-byte fields in sideband reply parsers (git-fixes).\n- drm/dp: Add eDP 1.5 bit definition (stable-fixes).\n- drm/edid: fix OOB read in drm_parse_tiled_block() (git-fixes).\n- drm/gpuvm: Do not prepare NULL objects (git-fixes).\n- drm/hisilicon/hibmc: move display contrl config to hibmc_probe() (git-fixes).\n- drm/hisilicon/hibmc: use clock to look up the PLL value (git-fixes).\n- drm/hyperv: use VMBUS_RING_SIZE() (git-fixes).\n- drm/i915/gem: Add missing nospec on parallel submit slot (git-fixes).\n- drm/i915/gem: Fix phys BO pread/pwrite with offset (git-fixes).\n- drm/i915/psr: Add defininitions for INTEL_WA_REGISTER_CAPS DPCD register (stable-fixes).\n- drm/i915: clear CRTC color blob pointers after dropping refs (git-fixes).\n- drm/imagination: Count paired job fence as dependency in prepare_job() (git-fixes).\n- drm/imagination: Fit paired fragment job in the correct CCCB (git-fixes).\n- drm/msm/dp: fix HPD state status bit shift value (git-fixes).\n- drm/msm/dp: Fix the ISR_* enum values (git-fixes).\n- drm/nouveau/acr: fix missing nvkm_done() in error path of nvkm_acr_oneinit() (git-fixes).\n- drm/nouveau/bios: specify correct display fuse register for Ampere and Ada (git-fixes).\n- drm/nouveau: fix reversed error cleanup order in ucopy functions (git-fixes).\n- drm/panthor: Fix kernel-doc warning in panthor_sched.c (git-fixes).\n- drm/radeon: fix integer overflow in radeon_align_pitch() (git-fixes).\n- drm/radeon: fix memory leak in radeon_ring_restore() on lock failure (git-fixes).\n- drm/rockchip: cdn-dp: add missing check in cdn_dp_config_video() (git-fixes).\n- drm/rockchip: Test for imported buffers with drm_gem_is_imported() (git-fixes).\n- drm/syncobj: Fix memory leak in drm_syncobj_find_fence() (git-fixes).\n- drm/tegra: dc: Fix device node reference leak in tegra_dc_has_output() (git-fixes).\n- drm/tegra: Fix iommu_map_sgtable() return value check (git-fixes).\n- drm/tidss: Drop extra drm_mode_config_reset() call (git-fixes).\n- drm/tidss: Fix missing drm_bridge_add() call (git-fixes).\n- drm/vc4: fix krealloc() memory leak (git-fixes).\n- drm/virtio: fix dma_fence refcount leak on error in virtio_gpu_dma_fence_wait() (git-fixes).\n- drm/virtio: Fix driver removal with disabled KMS (git-fixes).\n- drm/xe: fix refcount leak in xe_range_fence_insert() (git-fixes).\n- drm: renesas: rzg2l_mipi_dsi: Increase reset deassertion delay (git-fixes).\n- fbdev: Fix fb_new_modelist to prevent null-ptr-deref in fb_videomode_to_var (stable-fixes).\n- fbdev: fix use-after-free in store_modes() (stable-fixes).\n- fbdev: modedb: fix a possible UAF in fb_find_mode() (stable-fixes).\n- fbdev: modedb: Fix misaligned fields in the 1920x1080-60 mode (git-fixes).\n- firmware: arm_scmi: Fix OOB in scmi_power_name_get() (git-fixes).\n- firmware: arm_scmi: Read sensor config as 32-bit value (git-fixes).\n- firmware_loader: fix device reference leak in firmware_upload_register() (git-fixes).\n- firmware_loader: Fix recursive lock in device_cache_fw_images() (git-fixes).\n- fpga: dfl: add bounds check in dfh_get_param_size() (git-fixes).\n- fpga: microchip-spi: fix zero header_size OOB read in mpf_ops_parse_header() (git-fixes).\n- fpga: region: fix use-after-free in child_regions_with_firmware() (git-fixes).\n- ftrace: Check against is_kernel_text() instead of kaslr_offset() (bsc#1267600).\n- ftrace: Do not over-allocate ftrace memory (bsc#1267600).\n- ftrace: Have ftrace pages output reflect freed pages (bsc#1267600).\n- ftrace: Test mcount_loc addr before calling ftrace_call_addr() (bsc#1267600).\n- ftrace: Update the mcount_loc check of skipped entries (bsc#1267600).\n- gpio: mvebu: fix NULL pointer dereference in suspend/resume (git-fixes).\n- gpio: mxc: fix irq_high handling (git-fixes).\n- gpio: rockchip: convert bank-\u003eclk to devm_clk_get_enabled() (git-fixes).\n- gpio: virtuser: Fix uninitialized data bug in gpio_virtuser_direction_do_write() (git-fixes).\n- gpio: zynq: fix runtime PM leak on remove (git-fixes).\n- gpiolib: Extract gpiochip_choose_fwnode() for wider use (stable-fixes).\n- gpiolib: Remove redundant assignment of return variable (stable-fixes).\n- gpu: host1x: Allow entries in BO caches to be freed (git-fixes).\n- gpu: host1x: Fix device reference leak in host1x_device_parse_dt() error path (git-fixes).\n- gpu: host1x: Fix iommu_map_sgtable() return value check (git-fixes).\n- HID: core: Add printk_ratelimited variants to hid_warn() etc (stable-fixes).\n- HID: hid-goodix-spi: validate report size to prevent stack buffer overflow (git-fixes).\n- HID: letsketch: fix UAF on inrange_timer at driver unbind (git-fixes).\n- HID: lg-g15: cancel pending work on remove to fix a use-after-free (git-fixes).\n- HID: logitech-hidpp: remove excess kernel-doc member in hidpp_scroll_counter (git-fixes).\n- HID: picolcd: prevent NULL pointer dereference in picolcd_send_and_wait() (git-fixes).\n- HID: quirks: Add ALWAYS_POLL quirk for SIGMACHIP USB mouse (stable-fixes).\n- HID: rate-limit hid_warn to prevent log flooding (stable-fixes).\n- HID: remove duplicate hid_warn_ratelimited definition (git-fixes).\n- HID: wacom: Fix OOB write in wacom_hid_set_device_mode() (git-fixes).\n- HID: wacom: stop hardware after post-start probe failures (git-fixes).\n- HID: wiimote: Fix table layout and whitespace errors (git-fixes).\n- hv: utils: handle and propagate errors in kvp_register (git-fixes).\n- hv: utils: replace deprecated strcpy with strscpy in kvp_register (git-fixes).\n- hv_balloon: Simplify data output in hv_balloon_debug_show() (git-fixes).\n- hv_netvsc: use kmap_local_page in netvsc_copy_to_send_buf (git-fixes).\n- hwmon: (aspeed-g6-pwm-tach) Guard fan RPM calculation against divide-by-zero (git-fixes).\n- hwmon: (asus_atk0110) Check package count before accessing element (git-fixes).\n- hwmon: (it87) Clamp negative values to zero in set_fan() (git-fixes).\n- hwmon: (ltc2992) add missing 'select REGMAP_I2C' to Kconfig (git-fixes).\n- hwmon: (max1619) add missing 'select REGMAP' to Kconfig (git-fixes).\n- hwmon: (max6697) add missing 'select REGMAP_I2C' to Kconfig (git-fixes).\n- hwmon: (occ) unregister sysfs devices outside occ lock (git-fixes).\n- hwmon: adm1275: Prevent reading uninitialized stack (git-fixes).\n- hwrng: jh7110 - fix refcount leak in starfive_trng_read() (git-fixes).\n- hwrng: virtio: clamp device-reported used.len at copy_data() (git-fixes).\n- hyperv: Clean up and fix the guest ID comment in hvgdk.h (git-fixes).\n- i2c: core: disable runtime PM on adapter registration failure (git-fixes).\n- i2c: core: fix adapter debugfs creation (git-fixes).\n- i2c: core: fix adapter deregistration race (git-fixes).\n- i2c: core: fix adapter probe deferral loop (git-fixes).\n- i2c: core: fix adapter registration race (git-fixes).\n- i2c: core: fix hang on adapter registration failure (git-fixes).\n- i2c: core: fix irq domain leak on adapter registration failure (git-fixes).\n- i2c: core: fix NULL-deref on adapter registration failure (git-fixes).\n- i2c: dev: prevent integer overflow in I2C_TIMEOUT ioctl (stable-fixes).\n- i2c: imx-lpi2c: mark I2C adapter when hardware is powered down (git-fixes).\n- i2c: mpc: Fix timeout calculations (git-fixes).\n- i2c: qcom-cci: Fix NULL pointer dereference in cci_remove() (git-fixes).\n- i2c: riic: fix refcount leak in riic_i2c_resume_noirq() (git-fixes).\n- i2c: stm32f7: fix timing computation ignoring i2c-analog-filter (git-fixes).\n- i2c: stm32f7: truncate clock period instead of rounding it (git-fixes).\n- i2c: tegra: Fix NOIRQ suspend/resume (git-fixes).\n- i3c: master: Prevent reuse of dynamic address on device add failure (git-fixes).\n- i3c: master: Serialize i3c_set_hotjoin() with the maintenance lock (git-fixes).\n- ice: ptp: don't WARN when controlling PF is unavailable (bsc#1267251).\n- iio: accel: mma8452: handle I2C read error(s) in mma8452_read() (git-fixes).\n- iio: adc: ti-ads1298: add bounds check to pga_settings index (stable-fixes).\n- iio: adc: xilinx-ams: fix out-of-bounds channel lookup in event handling (git-fixes).\n- iio: backend: fix uninitialized data in debugfs (git-fixes).\n- iio: chemical: scd30: Cleanup initializations and fix sign-extension bug (git-fixes).\n- iio: chemical: scd30: fix division by zero in write_raw (git-fixes).\n- iio: chemical: scd30: Use guard(mutex) to allow early returns (stable-fixes).\n- iio: gyro: bmg160: bail out when bandwidth/filter is not in table (git-fixes).\n- iio: gyro: bmg160: wait full startup time after mode change at probe (git-fixes).\n- iio: light: opt3001: fix missing state reset on timeout (git-fixes).\n- iio: light: si1133: prevent race condition on timeout (git-fixes).\n- iio: light: si1133: reset counter to prevent race condition (git-fixes).\n- iio: light: veml6030: fix channel type when pushing events (git-fixes).\n- iio: light: veml6075: add bounds check to veml6075_it_ms index (stable-fixes).\n- iio: magnetometer: ak8975: Add missed pm_runtime_put_autosuspend() call (git-fixes).\n- iio: resolver: ad2s1210: notify trigger and clear state on fault read error (git-fixes).\n- iio: tcs3472: power down chip on probe failure (git-fixes).\n- iio: temperature: ltc2983: Fix n_wires default bypassing rotation check (git-fixes).\n- iio: temperature: ltc2983: Fix reinit_completion() called after conversion start (git-fixes).\n- Input: atkbd - add DMI quirk for Lenovo Yoga Air 14 (83QK) (stable-fixes).\n- Input: elan_i2c - validate firmware size before use (stable-fixes).\n- Input: synaptics - add LEN2058 to SMBus passlist for ThinkPad E490 (stable-fixes).\n- Input: xpad - add \"Nova 2 Lite\" from GameSir (stable-fixes).\n- Input: xpad - add support for ASUS ROG RAIKIRI II (stable-fixes).\n- io_uring/cancel: de-unionize file and user_data in struct io_cancel_data (git-fixes bsc#1261250).\n- io_uring/filetable: clamp alloc_hint to the configured alloc range (git-fixes bsc#1261250).\n- io_uring/io-wq: fix incorrect io_wq_for_each_worker() termination logic (git-fixes bsc#1261250).\n- io_uring/poll: ensure EPOLL_ONESHOT is propagated for EPOLL_URING_WAKE (git-fixes bsc#1261250).\n- io_uring/wait: fix min_timeout behavior (git-fixes bsc#1261250).\n- io_uring/waitid: clear waitid info before copying it to userspace (git-fixes).\n- io_uring: fix min_wait wakeups for SQPOLL (git-fixes bsc#1261250).\n- ipv4: account for fraggap on the paged allocation path (git-fixes).\n- ipv6: account for fraggap on the paged allocation path (git-fixes).\n- KEYS: fix overflow in keyctl_pkey_params_get_2() (git-fixes).\n- KEYS: Use acquire when reading state in keyring search (git-fixes).\n- KVM: arm64: PMU: Preserve AArch32 counter low bits (git-fixes).\n- KVM: arm64: vgic: Free private_irqs when init fails after allocation (git-fixes).\n- KVM: Don't WARN if memory is dirtied without a vCPU when the VM is dying (git-fixes).\n- KVM: nSVM: Always use NextRIP as vmcb02's NextRIP after first L2 VMRUN (git-fixes).\n- KVM: nSVM: Always use vmcb01 in VMLOAD/VMSAVE emulation (git-fixes).\n- KVM: nSVM: Ensure AVIC is inhibited when restoring a vCPU to guest mode (git-fixes).\n- KVM: nSVM: Mark all of vmcb02 dirty when restoring nested state (git-fixes).\n- KVM: nSVM: Sync interrupt shadow to cached vmcb12 after VMRUN of L2 (git-fixes).\n- KVM: nSVM: Sync NextRIP to cached vmcb12 after VMRUN of L2 (git-fixes).\n- KVM: nVMX: Immediately refresh APICv controls as needed on nested VM-Exit (git-fixes).\n- KVM: Replace guest-triggerable BUG_ON() in ioeventfd datamatch with get_unaligned() (git-fixes).\n- KVM: SEV: Add an anonymous \"psc\" struct to track current PSC metadata (git-fixes).\n- KVM: SEV: Decouple the need to sync the GHCB SA from the need to free the SA (git-fixes).\n- KVM: SEV: Don't terminate SNP VMs on #VMGEXIT without a registered GHCB (git-fixes).\n- KVM: SEV: Make it more obvious when KVM is writing back the current PSC index (git-fixes).\n- KVM: SEV: Move sev_free_vcpu() down below sev_es_unmap_ghcb() (git-fixes).\n- KVM: SEV: Read start/end indices of PSC requests exactly once per #VMGEXIT (git-fixes).\n- KVM: SEV: Return INVALID_EVENT for SNP-only #VMGEXIT from non-SNP guest (git-fixes).\n- KVM: SEV: Return INVALID_INPUT, not MISSING_INPUT, for bad GUEST_REQUEST input(s) (git-fixes).\n- KVM: SEV: Unmap and unpin the GHCB as needed on vCPU free (git-fixes).\n- KVM: SVM: Allow KVM_SET_NESTED_STATE to clear GIF when SVME==0 (git-fixes).\n- KVM: SVM: check validity of VMCB controls when returning from SMM (git-fixes).\n- KVM: SVM: Don't set GIF when clearing EFER.SVME (git-fixes).\n- KVM: SVM: Truncate INVLPGA address in compatibility mode (git-fixes).\n- KVM: Use vCPU specific memslots in __kvm_vcpu_map() (git-fixes).\n- KVM: VMX: Grab vmcs12 on CR8 interception update iff vCPU is in guest mode (git-fixes).\n- KVM: VMX: Read 32-bit GPR values for ENCLS instructions outside of 64-bit mode (git-fixes).\n- KVM: x86/mmu: Ensure hugepage is in by slot before checking max mapping level (git-fixes).\n- KVM: x86/mmu: Recursively zap orphaned nested TDP shadow pages on emulated writes (git-fixes).\n- KVM: x86/xen: Bug the VM if 32-bit KVM observes a 64-bit mode hypercall (git-fixes).\n- KVM: x86/xen: Don't truncate RAX when handling hypercall from protected guest (git-fixes).\n- KVM: x86: Consolidate CPUID fault handling for emulator and interception logic (git-fixes).\n- KVM: x86: Fix shadow paging use-after-free due to unexpected role (git-fixes).\n- KVM: x86: hyper-v: Bound the bank index when querying sparse banks (git-fixes).\n- KVM: x86: ioapic: Use old_dest_mode consistently in ioapic_write_indirect() (git-fixes).\n- KVM: x86: Move update_cr8_intercept() to lapic.c (git-fixes).\n- KVM: x86: Prioritize CPUID faulting over CPUID VM-exits in nested VMX (git-fixes).\n- KVM: x86: Trace hypercall register *after* truncating values for 32-bit (git-fixes).\n- KVM: x86: Unconditionally recompute CR8 intercept on PPR update (git-fixes).\n- mailbox: imx: Forward the timeout/ error in imx_mu_generic_tx() (git-fixes).\n- mailbox: mtk-adsp: fix UAF during device teardown (git-fixes).\n- misc: fastrpc: fix DMA address corruption due to find_vma misuse (git-fixes).\n- misc: fastrpc: Fix NULL pointer dereference in rpmsg callback (git-fixes).\n- misc: fastrpc: fix use-after-free of fastrpc_user in workqueue context (git-fixes).\n- misc: fastrpc: fix use-after-free race in fastrpc_map_create (git-fixes).\n- mm/vmstat: defer the refresh_zone_stat_thresholds after all CPUs bringup (bsc#1270042).\n- mtd: maps: vmu-flash: fix NULL pointer dereference in initialization (git-fixes).\n- mtd: rawnand: fix condition in 'nand_select_target()' (git-fixes).\n- mtd: rawnand: Pause continuous reads at block boundaries (git-fixes).\n- mtd: rawnand: pl353: fix probe resource allocation (git-fixes).\n- mtd: slram: remove failed entries from the device list (git-fixes).\n- mtd: spi-nor: Drop duplicate Kconfig dependency (git-fixes).\n- mtd: spi-nor: macronix: Add post_sfdp fixups for Quad Input Page Program (stable-fixes).\n- mtd: spi-nor: macronix: add support for mx66{l2, u1}g45g (stable-fixes).\n- mtd: spi-nor: spansion: use die erase for multi-die devices only (git-fixes).\n- mtd: spi-nor: swp: Improve locking user experience (git-fixes).\n- net: aquantia: Add missing descriptor cache invalidation on ATL2 (bsc#1268428).\n- net: ethtool: add ethtool COALESCE_RX_CQE_FRAMES/NSECS (bsc#1261256).\n- net: mana: Add ethtool counters for RX CQEs in coalesced type (bsc#1261256).\n- net: mana: Add support for PF device 0x00C1 (bsc#1268237).\n- net: mana: Add support for RX CQE Coalescing (bsc#1261256).\n- net: mana: Allocate interrupt context for each EQ when creating vPort (git-fixes).\n- net: mana: Cache MANA_QUERY_LINK_CONFIG result to avoid repeated HWC queries (bsc#1268238).\n- net: mana: Create separate EQs for each vPort (git-fixes).\n- net: mana: Fall back to standard MTU when PF reports adapter_mtu of 0 (git-fixes).\n- net: mana: guard TX wq object destroy with INVALID_MANA_HANDLE check (git-fixes).\n- net: mana: initialize gdma queue id to INVALID_QUEUE_ID (git-fixes).\n- net: mana: Introduce GIC context with refcounting for interrupt management (git-fixes).\n- net: mana: Optimize irq affinity for low vcpu configs (git-fixes).\n- net: mana: Query device capabilities and configure MSI-X sharing for EQs (git-fixes).\n- net: mana: Sync page pool RX frags for CPU (git-fixes).\n- net: mana: Use GIC functions to allocate global EQs (git-fixes).\n- net: mana: Validate the packet length reported by the NIC (git-fixes).\n- net: phy: sfp: free mii_bus in sfp_i2c_mdiobus_destroy (git-fixes).\n- net: usb: lan78xx: disable VLAN filter in promiscuous mode (git-fixes).\n- net: usb: net1080: validate packet_len before pad-byte access in rx_fixup (git-fixes).\n- net: wwan: iosm: bound device offsets in the MUX downlink decoder (git-fixes).\n- nfc: hci: fix out-of-bounds read in HCP header parsing (git-fixes).\n- nfc: llcp: Fix use-after-free in llcp_sock_release() (git-fixes).\n- nfc: llcp: Fix use-after-free race in nfc_llcp_recv_cc() (git-fixes).\n- packaging: Add nvidia kernel description.\n- packaging: compute-PATCHVERSION.sh -\u003e compute-PATCHVERSION.\n- page_pool: Fix PP_MAGIC_MASK to avoid crashing on some 32-bit arches (bsc#1261562).\n- page_pool: Move pp_magic check into helper functions (bsc#1261562).\n- page_pool: Track DMA-mapped pages and unmap them when destroying the pool (bsc#1261562).\n- PCI: Update saved_config_space upon resource assignment (git-fixes).\n- perf/x86/intel/uncore: Fix die ID init and look up bugs (bsc#1267419).\n- perf/x86/intel/uncore: Skip discovery table for offline dies (bsc#1267419).\n- platform/x86: dell-laptop: fix missing cleanups in init error path (git-fixes).\n- platform/x86: intel-hid: Protect ACPI notify handler against recursion (git-fixes).\n- platform/x86: xo15-ebook: Fix wakeup source and GPE handling (git-fixes).\n- PM: sleep: Use complete() in device_pm_sleep_init() (git-fixes).\n- power: reset: linkstation-poweroff: fix use-after-free in the linkstation_poweroff_init() (git-fixes).\n- power: supply: charger-manager: fix refcount leak in is_full_charged() (git-fixes).\n- power: supply: core: fix supplied_from allocations (git-fixes).\n- power: supply: cpcap-battery: Fix missing nvmem_device_put() causing reference leak (git-fixes).\n- powerpc/boot: Allow text relocations for pseries wrapper with binutils 2.46+ (git-fixes).\n- powerpc/fadump: define MIN_RMA in bytes rather than MB (bsc#1236743 git-fixes).\n- ppc/fadump: invoke kmsg_dump in fadump panic path (bsc#1270226 ltc#218302).\n- pwm: imx27: Fix variable truncation in .apply() (git-fixes).\n- RDMA/mana_ib: Allocate interrupt contexts on EQs (git-fixes).\n- RDMA/mana_ib: Use ib_get_eth_speed for reporting port speed (git-fixes).\n- regulator: scmi: fix of_node refcount leak in scmi_regulator_probe() (git-fixes).\n- Revert \"fs: don't block i_writecount during exec\" (bsc#1269982).\n- rtc: abx80x: fix the RTC_VL_CLR clearing all status flags (git-fixes).\n- rtc: cmos: unregister HPET IRQ handler on probe failure (git-fixes).\n- rtc: ds1307: Fix off-by-one issue with wday for rx8130 (git-fixes).\n- rtc: ds1307: handle oscillator stop flag for ds1337/ds1339/ds3231 (git-fixes).\n- rtc: mpfs: fix counter upload completion condition (git-fixes).\n- rtc: msc313: fix NULL deref in shared IRQ handler at probe (git-fixes).\n- scripts/sorttable: Add helper functions for Elf_Ehdr (bsc#1267600).\n- scripts/sorttable: Add helper functions for Elf_Shdr (bsc#1267600).\n- scripts/sorttable: Add helper functions for Elf_Sym (bsc#1267600).\n- scripts/sorttable: Allow matches to functions before function entry (bsc#1267600).\n- scripts/sorttable: Always use an array for the mcount_loc sorting (bsc#1267600).\n- scripts/sorttable: Convert Elf_Ehdr to union (bsc#1267600).\n- scripts/sorttable: Convert Elf_Sym MACRO over to a union (bsc#1267600).\n- scripts/sorttable: Fix endianness handling in build-time mcount sort (bsc#1267600).\n- scripts/sorttable: Get start/stop_mcount_loc from ELF file directly (bsc#1267600).\n- scripts/sorttable: Have mcount rela sort use direct values (bsc#1267600).\n- scripts/sorttable: Have the ORC code use the _r() functions to read (bsc#1267600).\n- scripts/sorttable: Make compare_extable() into two functions (bsc#1267600).\n- scripts/sorttable: Move code from sorttable.h into sorttable.c (bsc#1267600).\n- scripts/sorttable: Remove unneeded Elf_Rel (bsc#1267600).\n- scripts/sorttable: Remove unused macro defines (bsc#1267600).\n- scripts/sorttable: Remove unused write functions (bsc#1267600).\n- scripts/sorttable: Replace Elf_Shdr Macro with a union (bsc#1267600).\n- scripts/sorttable: Use a structure of function pointers for elf helpers (bsc#1267600).\n- scripts/sorttable: Use normal sort if theres no relocs in the mcount section (bsc#1267600).\n- scripts/sorttable: Use uint64_t for mcount sorting (bsc#1267600).\n- scripts/sorttable: Zero out weak functions in mcount_loc table (bsc#1267600).\n- scsi: smartpqi: Use shost_to_hba() in pqi_scan_finished() (bsc#1257506).\n- scsi: storvsc: Replace symbolic permissions with octal (git-fixes).\n- scsi: target: Fix hexadecimal CHAP_I handling (git-fixes).\n- selftests/bpf: Add BPF_STRICT_BUILD toggle (poo#202224).\n- selftests/bpf: Allow test_progs to link with a partial object set (poo#202224).\n- selftests/bpf: Avoid rebuilds when running emit_tests (poo#202224).\n- selftests/bpf: Consolidate kernel modules into common directory (poo#202224).\n- selftests/bpf: Copy test_kmods when installing selftest (poo#202224).\n- selftests/bpf: Fix runqslower cross-endian build (poo#202224).\n- selftests/bpf: Fix test_kmods KDIR to honor O= and distro kernels (poo#202224).\n- selftests/bpf: make BPF_TARGET_ENDIAN non-recursive to speed up *.bpf.o build (poo#202224).\n- selftests/bpf: Make skeleton headers order-only prerequisites of .test.d (poo#202224).\n- selftests/bpf: Provide weak definitions for cross-test functions (poo#202224).\n- selftests/bpf: Skip tests whose objects were not built (poo#202224).\n- selftests/bpf: Support cross-endian building (poo#202224).\n- selftests/bpf: Tolerate benchmark build failures (poo#202224).\n- selftests/bpf: Tolerate BPF and skeleton generation failures (poo#202224).\n- selftests/bpf: Tolerate missing files during install (poo#202224).\n- selftests/bpf: Tolerate test file compilation failures (poo#202224).\n- serial: 8250: dispatch SysRq character in serial8250_handle_irq() (git-fixes).\n- serial: 8250_dw: dispatch SysRq character in dw8250_handle_irq() (git-fixes).\n- serial: qcom_geni: Fix RX DMA stall when SE_DMA_RX_LEN_IN is zero (git-fixes).\n- slimbus: qcom-ngd-ctrl: Avoid ABBA on tx_lock/ctrl-\u003elock (git-fixes).\n- slimbus: qcom-ngd-ctrl: Balance pm_runtime enablement for NGD (git-fixes).\n- slimbus: qcom-ngd-ctrl: Correct PDR and SSR cleanup ownership (git-fixes).\n- slimbus: qcom-ngd-ctrl: fix OF node refcount (git-fixes).\n- slimbus: qcom-ngd-ctrl: Fix probe error path ordering (git-fixes).\n- slimbus: qcom-ngd-ctrl: Fix up platform_driver registration (git-fixes).\n- slimbus: qcom-ngd-ctrl: Initialize controller resources in controller (git-fixes).\n- slimbus: qcom-ngd-ctrl: Register callbacks after creating the ngd (git-fixes).\n- soc: qcom: ice: Fix race between qcom_ice_probe() and of_qcom_ice_get() (git-fixes).\n- soc: qcom: ice: Return -ENODEV if the ICE platform device is not found (git-fixes).\n- spi: at91-usart: drop dead runtime pm support (git-fixes).\n- spi: dw: fix wrong BAUDR setting after resume (git-fixes).\n- spi: ep93xx: fix double-free of zeropage on DMA setup failure (git-fixes).\n- spi: fsl-lpspi: replace dmaengine_terminate_all() with dmaengine_terminate_sync() (git-fixes).\n- spi: fsl-lpspi: terminate the RX channel on TX prepare failure path (git-fixes).\n- spi: hisi-kunpeng: Use dev_err_probe() for host registration failure (git-fixes).\n- spi: meson-spifc: fix runtime PM leak on remove (git-fixes).\n- spi: rpc-if: Use correct device for hardware reinitialization on resume (git-fixes).\n- spi: uniphier: Fix completion initialization order before devm_request_irq() (git-fixes).\n- spi: xilinx: use FIFO occupancy register to determine buffer size (git-fixes).\n- Split off kABI workaround for bsc#1267458 (bsc#1267458).\n- staging: most: video: avoid double free on video register failure (git-fixes).\n- staging: nvec: fix use-after-free in nvec_rx_completed() (git-fixes).\n- thermal: hwmon: Fix critical temperature attribute removal (git-fixes).\n- thermal: intel: Fix dangling resources on thermal_throttle_online() failure (git-fixes).\n- thermal: testing: reject missing command arguments (git-fixes).\n- thermal: testing: zone: Flush work items during cleanup (git-fixes).\n- thunderbolt: Bound root directory content to block size (git-fixes).\n- thunderbolt: Clamp XDomain response data copy to allocation size (git-fixes).\n- thunderbolt: debugfs: Don't stop reading SB registers if just one fails (git-fixes).\n- thunderbolt: debugfs: Fix margining error counter buffer leak (git-fixes).\n- thunderbolt: Limit XDomain response copy to actual frame size (git-fixes).\n- thunderbolt: Reject zero-length property entries in validator (git-fixes).\n- thunderbolt: Validate XDomain request packet size before type cast (git-fixes).\n- tools/power/x86/intel-speed-select: Harden daemon pidfile open (git-fixes).\n- tpm: fix event_size output in tpm1_binary_bios_measurements_show (git-fixes).\n- tpm: tpm2-sessions: wait for async KPP completion in tpm_buf_append_salt (git-fixes).\n- tpm: tpm_tis_spi: Use wait_woken() in wait_for_tmp_stat() (git-fixes).\n- usb: core: Fix SuperSpeed root hub wMaxPacketSize (stable-fixes).\n- usb: core: Fix up Interrupt IN endpoints with bogus wBytesPerInterval (stable-fixes).\n- usb: host: max3421: Fix shift-out-of-bounds in max3421_hub_control() (git-fixes).\n- usb: host: max3421: Reject hub port requests for non-existent ports (git-fixes).\n- USB: quirks: add NO_LPM for Lenovo ThinkPad USB-C Dock Gen2 hub controllers (git-fixes).\n- USB: serial: io_ti: fix heap overflow in build_i2c_fw_hdr() (git-fixes).\n- USB: serial: io_ti: fix heap overflow in get_manuf_info() (git-fixes).\n- USB: serial: kl5kusb105: fix bulk-out buffer overflow (git-fixes).\n- USB: serial: option: add usb-id for Dell Wireless DW5826e-m (stable-fixes).\n- usb: storage: Add quirks for PNY Elite Portable SSD (git-fixes).\n- usb: typec: altmodes/displayport: validate count before reading Status Update VDO (stable-fixes).\n- usb: typec: tcpm/tcpci_maxim: validate header NDO against RX_BYTE_CNT (stable-fixes).\n- usb: typec: tcpm: bound altmode_desc[] per iteration in svdm_consume_modes() (stable-fixes).\n- usb: typec: tcpm: validate VDO count in Discover Identity ACK handlers (stable-fixes).\n- usb: typec: ucsi: ccg: reject firmware images without a ':' record header (stable-fixes).\n- usb: typec: ucsi: displayport: NAK DP_CMD_CONFIGURE without a payload VDO (stable-fixes).\n- usb: typec: ucsi: validate connector number in ucsi_connector_change() (stable-fixes).\n- usb: typec: wcove: don't write past struct pd_message in wcove_read_rx_buffer() (stable-fixes).\n- usbnet: gl620a: fix out-of-bounds read in genelink_rx_fixup() (git-fixes).\n- vc_screen: fix null-ptr-deref in vcs_notifier() during concurrent vcs_write (git-fixes).\n- watchdog/hpwdt: Refine hpwdt message for UV platform (bsc#1269199).\n- watchdog: apple: Add \"apple,t8103-wdt\" compatible (git-fixes).\n- watchdog: sama5d4_wdt: Fix WDDIS detection on SAM9X60 and SAMA7G5 (git-fixes).\n- watchdog: sp5100_tco: Use EFCH MMIO for newer Hygon FCH (git-fixes).\n- watchdog: sprd_wdt: Remove redundant sprd_wdt_disable() on register failure (git-fixes).\n- watchdog: unregister PM notifier on watchdog unregister (git-fixes).\n- wifi: ath9k: fix OOB access from firmware tx status queue ID (git-fixes).\n- wifi: ath11k: fix warning when unbinding (git-fixes).\n- wifi: cfg80211: fix grammar in MLO group key error message (git-fixes).\n- wifi: iwlwifi: mvm: fix race condition in PTP removal (stable-fixes).\n- wifi: mac80211: fix monitor mode frame capture for real chanctx drivers (git-fixes).\n- wifi: mt76: fix argument to ieee80211_is_first_frag() (git-fixes).\n- wifi: mt76: mt76x2u: Add support for ELECOM WDC-867SU3S (stable-fixes).\n- wifi: mt76: mt792x: skip MLD header rewrite for 802.3 encap TX (git-fixes).\n- wifi: mt76: mt7915: fix potential tx_retries underflow (git-fixes).\n- wifi: mt76: mt7921: avoid undesired changes of the preset regulatory domain (stable-fixes).\n- wifi: mt76: mt7921: fix a potential scan no APs (stable-fixes).\n- wifi: mt76: mt7921: fix potential tx_retries underflow (git-fixes).\n- wifi: mt76: mt7925: clean up DMA on probe failure (git-fixes).\n- wifi: mt76: mt7925: don't disable AP BSS when removing TDLS peer (git-fixes).\n- wifi: mt76: mt7925: fix potential tx_retries underflow (git-fixes).\n- wifi: mt76: mt7925: fix stale pointer comparisons in change_vif_links (git-fixes).\n- wifi: mt76: mt7925: keep TX BA state in the primary WCID (git-fixes).\n- wifi: mt76: mt7996: fix potential tx_retries underflow (git-fixes).\n- wifi: rtlwifi: rtl8821ae: Fix C2H bit location in RX descriptor (git-fixes).\n- wifi: rtw88: fix OOB read from firmware RX descriptor exceeding DMA buffer (git-fixes).\n- wifi: rtw88: increase TX report timeout to fix race condition (git-fixes).\n- wifi: rtw88: usb: fix memory leaks on USB write failures (git-fixes).\n- wifi: rtw89: Correct data type for scan index to avoid infinite loop (git-fixes).\n- wifi: wcn36xx: fix heap overflow from oversized firmware HAL response (git-fixes).\n- wifi: wcn36xx: fix OOB read from firmware count in PRINT_REG_INFO indication (git-fixes).\n- wifi: wcn36xx: fix OOB read from short trigger BA firmware response (git-fixes).\n- x86/cpu/amd: Correct the microcode table for Zenbleed (git-fixes).\n- x86/cpu: Disable FRED when PTI is forced on (git-fixes).\n- x86/cpu: Properly parse CPUID leaf 0x2 TLB descriptor 0x63 (git-fixes).\n- x86/cpu: Validate CPUID leaf 0x2 EDX output (git-fixes).\n- x86/irq: Ensure initial PIR loads are performed exactly once (git-fixes).\n- x86/platform/uv: Expose the uv_hub_type() interface (jsc#PED-16390).\n- x86/tsc: Disable clocksource watchdog checking on recent and future UV platforms (jsc#PED-16390).\n- X.509: Fix validation of ASN.1 certificate header (git-fixes).\n- xfrm: Fix dev use-after-free in xfrm async resumption (bsc#1268276).\n","status":"published","published":"2026-07-21T08:27:32Z","modified":"2026-07-24T18:24:22.02722596Z","updated_at":"2026-11-02T16:58:41.885092Z"},{"id":"SUSE-SU-2026:22742-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-10263: arm64: cputype: Add C1-Premium definitions (bsc#1266290).\n- CVE-2025-39894: netfilter: br_netfilter: do not check confirmed bit\n  in br_nf_local_in() after confirm (bsc#1262430).\n- CVE-2025-40341: futex: Don't leak robust_list pointer on exec race (bsc#1255029).\n- CVE-2026-23248: perf: Make perf_pmu_unregister() useable (bsc#1259800).\n- CVE-2026-23394: Revert: \"af_unix: Remove lock dance in unix_peek_fds().\" (bsc#1260565).\n- CVE-2026-23451: bonding: prevent potential infinite loop in bond_header_parse() (bsc#1261604).\n- CVE-2026-31414: netfilter: nf_conntrack_expect: use expect-\u003ehelper (bsc#1262085).\n- CVE-2026-31429: net: skb: fix cross-cache free of KFENCE-allocated skb head (bsc#1262392).\n- CVE-2026-31438: netfs: Fix kernel BUG in netfs_limit_iter() for ITER_KVEC iterators (bsc#1267824).\n- CVE-2026-31450: ext4: publish jinode after initialization (bsc#1262618).\n- CVE-2026-31452: ext4: convert inline data to extents when truncate exceeds inline size (bsc#1262620).\n- CVE-2026-31466: mm/huge_memory: fix folio isn't locked in softleaf_to_folio() (bsc#1267825).\n- CVE-2026-31469: virtio_net: Fix UAF on dst_ops when IFF_XMIT_DST_RELEASE is cleared and napi_tx is false\n  (bsc#1267816).\n- CVE-2026-31479: drm/xe: always keep track of remap prev/next (bsc#1262765).\n- CVE-2026-31492: RDMA/irdma: Initialize free_qp completion before using it (bsc#1262748).\n- CVE-2026-31495: netfilter: ctnetlink: use netlink policy range checks (bsc#1262798).\n- CVE-2026-31499: Bluetooth: L2CAP: Fix deadlock in l2cap_conn_del() (bsc#1262674).\n- CVE-2026-31502: team: fix header_ops type confusion with non-Ethernet ports (bsc#1263072).\n- CVE-2026-31555: futex: Clear stale exiting pointer in futex_lock_pi() retry path (bsc#1263178).\n- CVE-2026-31560: spi: spi-dw-dma: fix print error log when wait finish transaction (bsc#1263057).\n- CVE-2026-31596: ocfs2: handle invalid dinode in ocfs2_group_extend (bsc#1263319).\n- CVE-2026-31646: net: lan966x: fix page_pool error handling in lan966x_fdma_rx_alloc_page_pool() (bsc#1263796).\n- CVE-2026-31647: idpf: fix PREEMPT_RT raw/bh spinlock nesting for async VC handling (bsc#1263581).\n- CVE-2026-31663: xfrm: hold device only for the asynchronous decryption (bsc#1263133).\n- CVE-2026-31664: xfrm: clear trailing padding in build_polexpire() (bsc#1263578).\n- CVE-2026-31665: netfilter: nft_ct: fix use-after-free in timeout object destroy (bsc#1263137).\n- CVE-2026-31670: net: rfkill: prevent unlimited numbers of rfkill events from being created (bsc#1263573).\n- CVE-2026-31673: af_unix: read UNIX_DIAG_VFS data under unix_state_lock (bsc#1263143).\n- CVE-2026-31674: netfilter: ip6t_rt: reject oversized addrnr in rt_mt6_check() (bsc#1263568).\n- CVE-2026-31680: net: ipv6: flowlabel: defer exclusive option free until RCU teardown (bsc#1263563).\n- CVE-2026-31693: cifs: some missing initializations on replay (bsc#1267744).\n- CVE-2026-31743: nvmem: zynqmp_nvmem: Fix buffer size in DMA and memcpy (bsc#1264067).\n- CVE-2026-31752: bridge: br_nd_send: validate ND option lengths (bsc#1264045).\n- CVE-2026-31771: Bluetooth: hci_event: move wake reason storage into validated event handlers (bsc#1264145).\n- CVE-2026-43010: bpf: Reject sleepable kprobe_multi programs at attach time (bsc#1264015).\n- CVE-2026-43014,CVE-2026-43015: net: macb: fix clk handling on PCI glue driver removal (bsc#1264010 bsc#1264012).\n- CVE-2026-43016: bpf: sockmap: Fix use-after-free of sk-\u003esk_socket in sk_psock_verdict_data_ready() (bsc#1264007).\n- CVE-2026-43022: Bluetooth: hci_sync: hci_cmd_sync_queue_once() return -EEXIST if exists (bsc#1264001).\n- CVE-2026-43024: netfilter: nf_tables: reject immediate NF_QUEUE verdict (bsc#1263930).\n- CVE-2026-43028: netfilter: x_tables: ensure names are nul-terminated (bsc#1263934).\n- CVE-2026-43034: bnxt_en: set backing store type from query type (bsc#1263998).\n- CVE-2026-43035: net: sched: cls_api: fix tc_chain_fill_node to\n  initialize tcm_info to zero to prevent an info-leak (bsc#1263996).\n- CVE-2026-43036: net: use skb_header_pointer() for TCPv4 GSO frag_off check (bsc#1263993).\n- CVE-2026-43053: xfs: factor out xfs_attr3_node_entry_remove (bsc#1264084).\n- CVE-2026-43057: net: correctly handle tunneled traffic on IPV6_CSUM GSO fallback (bsc#1264056).\n- CVE-2026-43074: eventpoll: defer struct eventpoll free to RCU grace period (bsc#1264263).\n- CVE-2026-43080: l2tp: Drop large packets with UDP encap (bsc#1264236).\n- CVE-2026-43081: net: ipa: fix GENERIC_CMD register field masks for IPA v5.0+ (bsc#1264241).\n- CVE-2026-43083: net: ioam6: fix OOB and missing lock (bsc#1264266).\n- CVE-2026-43085: netfilter: nfnetlink_log: initialize nfgenmsg in NLMSG_DONE terminator (bsc#1264230).\n- CVE-2026-43086: ipvs: fix NULL deref in ip_vs_add_service error path (bsc#1264286).\n- CVE-2026-43089: xfrm_user: fix info leak in build_mapping() (bsc#1264261).\n- CVE-2026-43090: xfrm: fix refcount leak in xfrm_migrate_policy_find (bsc#1264250).\n- CVE-2026-43092: xsk: validate MTU against usable frame size on bind (bsc#1264270).\n- CVE-2026-43093: xsk: tighten UMEM headroom validation to account for tailroom and min frame (bsc#1264254).\n- CVE-2026-43094: ixgbevf: add missing negotiate_features op to Hyper-V ops table (bsc#1264231).\n- CVE-2026-43101: ipv6: ioam: fix potential NULL dereferences in __ioam6_fill_trace_data() (bsc#1264239).\n- CVE-2026-43107: xfrm: account XFRMA_IF_ID in aevent size calculation (bsc#1264258).\n- CVE-2026-43119: Bluetooth: hci_sync: annotate data-races around hdev-\u003ereq_status (bsc#1264561).\n- CVE-2026-43124: pstore: ram_core: fix incorrect success return when vmap() fails (bsc#1264545).\n- CVE-2026-43128: RDMA/umem: Fix double dma_buf_unpin in failure path (bsc#1264612).\n- CVE-2026-43130: iommu/vt-d: Flush dev-IOTLB only when PCIe device is accessible in scalable mode (bsc#1264532).\n- CVE-2026-43132: dm-verity: correctly handle dm_bufio_client_create() failure (bsc#1264614).\n- CVE-2026-43139: xfrm6: fix uninitialized saddr in xfrm6_get_saddr() (bsc#1264294).\n- CVE-2026-43145: remoteproc: imx_rproc: Fix invalid loaded resource table detection (bsc#1265091).\n- CVE-2026-43157: octeontx2-af: CGX: fix bitmap leaks (bsc#1264624).\n- CVE-2026-43158: xfs: fix freemap adjustments when adding xattrs to leaf blocks (bsc#1264595).\n- CVE-2026-43161: iommu/vt-d: Skip dev-iotlb flush for inaccessible PCIe device without scalable mode (bsc#1264333).\n- CVE-2026-43167: xfrm: always flush state and policy upon NETDEV_UNREGISTER event (bsc#1264580).\n- CVE-2026-43171: EFI/CPER: don't dump the entire memory region (bsc#1264549).\n- CVE-2026-43175: clk: rs9: Reserve 8 struct clk_hw slots for for 9FGV0841 (bsc#1264372).\n- CVE-2026-43187: xfs: delete attr leaf freemap entries when empty (bsc#1264603).\n- CVE-2026-43191: drm/amd/display: Adjust PHY FSM transition to TX_EN-to-PLL_ON for TMDS on DCN35 (bsc#1264548).\n- CVE-2026-43194: net: consume xmit errors of GSO frames (bsc#1264304).\n- CVE-2026-43198: tcp: fix potential race in tcp_v6_syn_recv_sock() (bsc#1264610).\n- CVE-2026-43199: net/mlx5e: Fix \"scheduling while atomic\" in IPsec MAC address query (bsc#1264556).\n- CVE-2026-43205: dpaa2-switch: validate num_ifs to prevent out-of-bounds write (bsc#1264328).\n- CVE-2026-43213: wifi: rtw89: pci: validate sequence number of TX release report (bsc#1264643).\n- CVE-2026-43226: net/rds: No shortcut out of RDS_CONN_ERROR (bsc#1264544).\n- CVE-2026-43233: netfilter: nf_conntrack_h323: fix OOB read in decode_choice() (bsc#1264337).\n- CVE-2026-43238: net/sched: act_skbedit: fix divide-by-zero in tcf_skbedit_hash() (bsc#1264320).\n- CVE-2026-43240: ima: verify the previous kernel's IMA buffer lies in addressable RAM (bsc#1264386).\n- CVE-2026-43248: vhost: move vdpa group bound check to vhost_vdpa (bsc#1264302).\n- CVE-2026-43260: bnxt_en: Fix RSS context delete logic (bsc#1264429).\n- CVE-2026-43283: net: ethernet: ec_bhf: Fix dma_free_coherent() dma handle (bsc#1264295).\n- CVE-2026-43298: drm/amdgpu: Skip vcn poison irq release on VF (bsc#1264852).\n- CVE-2026-43303: mm/page_alloc: clear page-\u003eprivate in free_pages_prepare() (bsc#1264974).\n- CVE-2026-43336: lib/crypto: chacha: Zeroize permuted_state before it leaves scope (bsc#1265113).\n- CVE-2026-43337: drm/amd/display: Fix NULL pointer dereference in dcn401_init_hw() (bsc#1265112).\n- CVE-2026-43339: ipv6: prevent possible UaF in addrconf_permanent_addr() (bsc#1264763).\n- CVE-2026-43345: net: ipa: fix event ring index not programmed for IPA v5.0+ (bsc#1265103).\n- CVE-2026-43351: KVM: arm64: gic: Set vgic_model before initing private IRQs (bsc#1265082).\n- CVE-2026-43373: net: ncsi: fix skb leak in error paths (bsc#1265079).\n- CVE-2026-43374: net: nexthop: fix percpu use-after-free in remove_nh_grp_entry (bsc#1265084).\n- CVE-2026-43383: net/tcp-md5: Fix MAC comparison to be constant-time (bsc#1264744).\n- CVE-2026-43384: net/tcp-ao: Fix MAC comparison to be constant-time (bsc#1265097).\n- CVE-2026-43386: staging: rtl8723bs: fix potential out-of-bounds read in rtw_restruct_wmm_ie (bsc#1264740).\n- CVE-2026-43403: nsfs: tighten permission checks for ns iteration ioctls (bsc#1265129).\n- CVE-2026-43405: libceph: Use u32 for non-negative values in ceph_monmap_decode() (bsc#1264741).\n- CVE-2026-43406: libceph: prevent potential out-of-bounds reads in process_message_header() (bsc#1265073).\n- CVE-2026-43407: libceph: Fix potential out-of-bounds access in ceph_handle_auth_reply() (bsc#1265020).\n- CVE-2026-43415: scsi: ufs: core: Fix SError in ufshcd_rtc_work() during UFS suspend (bsc#1265123).\n- CVE-2026-43449: nvme-pci: Fix slab-out-of-bounds in nvme_dbbuf_set (bsc#1265023).\n- CVE-2026-43450: netfilter: nfnetlink_cthelper: fix OOB read in nfnl_cthelper_dump_table() (bsc#1264794).\n- CVE-2026-43452: netfilter: x_tables: guard option walkers against 1-byte tail reads (bsc#1265142).\n- CVE-2026-43456: bonding: fix type confusion in bond_setup_by_slave() (bsc#1264734).\n- CVE-2026-43457: mctp: i2c: fix skb memory leak in receive path (bsc#1265000).\n- CVE-2026-43458: serial: caif: hold tty-\u003elink reference in ldisc_open and ser_release (bsc#1265005).\n- CVE-2026-43465: net/mlx5e: RX, Fix XDP multi-buf frag counting for striding RQ (bsc#1264997).\n- CVE-2026-43466: net/mlx5e: Fix DMA FIFO desync on error CQE SQ recovery (bsc#1264790).\n- CVE-2026-43468: net/mlx5: Fix deadlock between devlink lock and esw-\u003ewq (bsc#1264978).\n- CVE-2026-43469: xprtrdma: Decrement re_receiving on the early exit paths (bsc#1265143).\n- CVE-2026-43470: nfs: return EISDIR on nfs3_proc_create if d_alias is a dir (bsc#1265128).\n- CVE-2026-43471: scsi: ufs: core: Fix possible NULL pointer dereference in ufshcd_add_command_trace() (bsc#1264789).\n- CVE-2026-43491: net: qrtr: ns: Limit the maximum server registration per node (bsc#1265628).\n- CVE-2026-43492: lib/crypto: mpi: Fix integer underflow in mpi_read_raw_from_sgl() (bsc#1265629).\n- CVE-2026-43502: net/rds: handle zerocopy send cleanup before the message is queued (bsc#1266008).\n- CVE-2026-45837: Require (reasonably) normal mappings for MADV_DOFORK (bsc#1266398).\n- CVE-2026-45838: bpf: fix end-of-list detection in cgroup_storage_get_next_key() (bsc#1266396).\n- CVE-2026-45840: openvswitch: cap upcall PID array size and pre-size vport replies (bsc#1266397).\n- CVE-2026-45841: netfilter: nfnetlink_osf: fix divide-by-zero in OSF_WSS_MODULO (bsc#1266390).\n- CVE-2026-45848: apparmor: fix NULL sock in aa_sock_file_perm (bsc#1266734).\n- CVE-2026-45857: scsi: csiostor: Fix dereference of null pointer rn (bsc#1266458).\n- CVE-2026-45858: ext4: don't zero the entire extent if EXT4_EXT_DATA_PARTIAL_VALID1 (bsc#1266773).\n- CVE-2026-45861: gfs2: Fix slab-use-after-free in qd_put (bsc#1266754).\n- CVE-2026-45862: iommu/vt-d: Flush cache for PASID table before using it (bsc#1266705).\n- CVE-2026-45870: SUNRPC: auth_gss: fix memory leaks in XDR decoding error paths (bsc#1266704).\n- CVE-2026-45884: apparmor: avoid per-cpu hold underflow in aa_get_buffer (bsc#1266718).\n- CVE-2026-45888: md/raid1: fix memory leak in raid1_run() (bsc#1266761).\n- CVE-2026-45891: net: hns3: fix double free issue for tx spare buffer (bsc#1266717).\n- CVE-2026-45894: iommu/vt-d: Clear Present bit before tearing down PASID entry (bsc#1266895).\n- CVE-2026-45899: ext4: drop extent cache when splitting extent fails (bsc#1266883).\n- CVE-2026-45901: netfilter: nf_tables: revert commit_mutex usage in reset path (bsc#1266892).\n- CVE-2026-45912: ext4: don't cache extent during splitting extent (bsc#1266899).\n- CVE-2026-45920: ext4: fix dirtyclusters double decrement on fs shutdown (bsc#1266893).\n- CVE-2026-45922: RDMA/mlx5: Fix memory leak in GET_DATA_DIRECT_SYSFS_PATH handler (bsc#1266805).\n- CVE-2026-45933: bpf: Preserve id of register in sync_linked_regs() (bsc#1266693).\n- CVE-2026-45940: net: stmmac: fix oops when split header is enabled (bsc#1266916).\n- CVE-2026-45948: ext4: fix memory leak in ext4_ext_shift_extents() (bsc#1266929).\n- CVE-2026-45961: gfs2: fix memory leaks in gfs2_fill_super error path (bsc#1266933).\n- CVE-2026-45964: SUNRPC: fix gss_auth kref leak in gss_alloc_msg error path (bsc#1266698).\n- CVE-2026-45965: apparmor: fix invalid deref of rawdata when export_binary is unset (bsc#1267208).\n- CVE-2026-45974: btrfs: fix invalid leaf access in btrfs_quota_enable() if ref key not found (bsc#1266922).\n- CVE-2026-45983: nfsd: never defer requests during idmap lookup (bsc#1266697).\n- CVE-2026-45985: ext4: don't set EXT4_GET_BLOCKS_CONVERT when splitting before submitting I/O (bsc#1266700).\n- CVE-2026-45997: scsi: sd: fix missing put_disk() when device_add(\u0026disk_dev) fails (bsc#1266740).\n- CVE-2026-45999: erofs: fix unsigned underflow in z_erofs_lz4_handle_overlap() (bsc#1266750).\n- CVE-2026-46005: xfs: fix a resource leak in xfs_alloc_buftarg() (bsc#1267431).\n- CVE-2026-46024: libceph: Prevent potential null-ptr-deref in ceph_handle_auth_reply() (bsc#1267218).\n- CVE-2026-46037: ipv4: icmp: validate reply type before using icmp_pointers (bsc#1267361).\n- CVE-2026-46046: ext4: fix missing brelse() in ext4_xattr_inode_dec_ref_all() (bsc#1266726).\n- CVE-2026-46050: md/raid10: fix deadlock with check operation and nowait requests (bsc#1266686).\n- CVE-2026-46051: md/raid5: fix soft lockup in retry_aligned_read() (bsc#1267360).\n- CVE-2026-46053: net: rds: fix MR cleanup on copy error (bsc#1267427).\n- CVE-2026-46063: x86/shstk: Prevent deadlock during shstk sigreturn (bsc#1267228).\n- CVE-2026-46065: fbdev: defio: Disconnect deferred I/O from the lifetime of struct (bsc#1267458).\n- CVE-2026-46069: wifi: mwifiex: fix use-after-free in mwifiex_adapter_cleanup() (bsc#1267437).\n- CVE-2026-46071: KVM: nSVM: Avoid clearing VMCB_LBR in vmcb12 (bsc#1267591).\n- CVE-2026-46076: KVM: nSVM: Raise #UD if unhandled VMMCALL isn't intercepted by L1 (bsc#1267365).\n- CVE-2026-46078: erofs: fix the out-of-bounds nameoff handling for trailing dirents (bsc#1267505).\n- CVE-2026-46079: rbd: fix null-ptr-deref when device_add_disk() fails (bsc#1266452).\n- CVE-2026-46091: media: rc: igorplugusb: heed coherency rules (bsc#1267238).\n- CVE-2026-46093: mm/vmalloc: take vmap_purge_lock in shrinker (bsc#1267548).\n- CVE-2026-46099: net: ipv6: fix NOREF dst use in seg6 and rpl lwtunnels (bsc#1266722).\n- CVE-2026-46101: netfilter: reject zero shift in nft_bitwise (bsc#1266878).\n- CVE-2026-46111: Bluetooth: hci_conn: fix potential UAF in create_big_sync (bsc#1267626).\n- CVE-2026-46112: RDMA/hns: Fix unlocked call to hns_roce_qp_remove() (bsc#1267582).\n- CVE-2026-46116: xfrm: defensively unhash xfrm_state lists in __xfrm_state_delete (bsc#1267369).\n- CVE-2026-46119: libceph: Fix slab-out-of-bounds access in auth message processing (bsc#1267628).\n- CVE-2026-46120: ip6_gre: Use cached t-\u003enet in ip6erspan_changelink() (bsc#1267640).\n- CVE-2026-46124: isofs: validate block number from NFS file handle in isofs_export_iget (bsc#1266847).\n- CVE-2026-46150: fanotify: fix false positive on permission events (bsc#1267387).\n- CVE-2026-46160: btrfs: fix missing last_unlink_trans update when removing a directory (bsc#1267624).\n- CVE-2026-46161: md/raid10: fix divide-by-zero in setup_geo() with zero far_copies (bsc#1266838).\n- CVE-2026-46162: ice: fix double free in ice_sf_eth_activate() error path (bsc#1266840).\n- CVE-2026-46172: ipv6: xfrm6: release dst on error in xfrm6_rcv_encap() (bsc#1266903).\n- CVE-2026-46173: exit: prevent preemption of oopsing TASK_DEAD task (bsc#1267722).\n- CVE-2026-46178: RDMA/mlx4: Fix resource leak on error in mlx4_ib_create_srq() (bsc#1267493).\n- CVE-2026-46185: smb/client: fix out-of-bounds read in symlink_data() (bsc#1266830).\n- CVE-2026-46214: vsock/virtio: fix accept queue count leak on transport mismatch (bsc#1267717).\n- CVE-2026-46227: sctp: revalidate list cursor after sctp_sendmsg_to_asoc() in SCTP_SENDALL (bsc#1267697).\n- CVE-2026-46242: eventpoll: Fix integer overflow in ep_loop_check_proc() (bsc#1267618).\n- CVE-2026-46244: netfilter: nft_inner: Fix IPv6 inner_thoff desync (bsc#1267654).\n- CVE-2026-46253: pstore/ram: fix buffer overflow in persistent_ram_save_old() (bsc#1267635).\n- CVE-2026-46254: AppArmor: Allow apparmor to handle unaligned dfa tables (bsc#1267637).\n- CVE-2026-46259: procfs: fix missing RCU protection when reading real_parent in do_task_stat() (bsc#1267685).\n- CVE-2026-46266: inet: RAW sockets using IPPROTO_RAW MUST drop incoming ICMP (bsc#1267684).\n- CVE-2026-46289: lib/scatterlist: fix length calculations in extract_kvec_to_sg (bsc#1267966).\n- CVE-2026-46291: printk: add print_hex_dump_devel() (bsc#1267937).\n- CVE-2026-46314: drm/v3d: Reject empty multisync extension to prevent infinite loop (bsc#1267992).\n- CVE-2026-46319: net/sched: act_ct: Only release RCU read lock after ct_ft (bsc#1268022).\n- CVE-2026-46320: tap: free page on error paths in tap_get_user_xdp() (bsc#1267993).\n- CVE-2026-46322: tun: free page on build_skb failure in tun_xdp_one() (bsc#1267994).\n- CVE-2026-46328: apparmor: fix rlimit for posix cpu timers (bsc#1268037).\n- CVE-2026-52908: RDMA: During rereg_mr ensure that REREG_ACCESS is compatible (bsc#1268661).\n- CVE-2026-52909: ip6_vti: set netns_immutable on the fallback device (bsc#1268660).\n- CVE-2026-52919: batman-adv: fix tp_meter counter underflow during shutdown (bsc#1269031).\n- CVE-2026-52923: ipc: limit next_id allocation to the valid ID range (bsc#1269033).\n- CVE-2026-52924: sctp: purge outqueue on stale COOKIE-ECHO handling (bsc#1269036).\n- CVE-2026-52933: io_uring/poll: fix signed comparison in io_poll_get_ownership() (bsc#1268989).\n- CVE-2026-52943: net: skbuff: fix missing zerocopy reference in pskb_carve helpers (bsc#1269022).\n- CVE-2026-52954: libceph: handle rbtree insertion error in decode_choose_args() (bsc#1269137).\n- CVE-2026-52955: libceph: Fix potential out-of-bounds access in crush_decode() (bsc#1269159).\n- CVE-2026-52957: libceph: Fix potential null-ptr-deref in decode_choose_args() (bsc#1269103).\n- CVE-2026-52962: ceph: fix a buffer leak in __ceph_setxattr() (bsc#1269135).\n- CVE-2026-52975: bonding: 3ad: implement proper RCU rules for port-\u003eaggregator (bsc#1269234).\n- CVE-2026-52980: sched/fair: Clear rel_deadline when initializing forked entities (bsc#1269252).\n- CVE-2026-52993: tipc: fix double-free in tipc_buf_append() (bsc#1269193).\n- CVE-2026-53015: erofs: unify lcn as u64 for 32-bit platforms (bsc#1269087).\n- CVE-2026-53021: scsi: target: core: Fix integer overflow in UNMAP bounds check (bsc#1269151).\n- CVE-2026-53036: bpf, arm64: Reject out-of-range B.cond targets (bsc#1269389).\n- CVE-2026-53039: ocfs2: validate group add input before caching (bsc#1269392).\n- CVE-2026-53040: ocfs2: validate bg_bits during freefrag scan (bsc#1269397).\n- CVE-2026-53041: ocfs2: fix listxattr handling when the buffer is full (bsc#1269398).\n- CVE-2026-53049: gfs2: add some missing log locking (bsc#1269646).\n- CVE-2026-53050: quota: Fix race of dquot_scan_active() with quota deactivation (bsc#1269188).\n- CVE-2026-53053: iommu/amd: Fix clone_alias() to use the original device's devid (bsc#1269310).\n- CVE-2026-53060: dm cache metadata: fix memory leak on metadata abort retry (bsc#1269164).\n- CVE-2026-53075: ppp: require CAP_NET_ADMIN in target netns for unattached ioctls (bsc#1269690).\n- CVE-2026-53078: bpf: Fix same-register dst/src OOB read and pointer leak in sock_ops (bsc#1269700).\n- CVE-2026-53081: bpf: Enforce regsafe base id consistency for BPF_ADD_CONST scalars (bsc#1269708).\n- CVE-2026-53086: net: bcmgenet: move DESC_INDEX flow to ring 0 (bsc#1269537).\n- CVE-2026-53090: bpf: Fix ld_{abs,ind} failure path analysis in subprogs (bsc#1269532).\n- CVE-2026-53103: wifi: mt76: mt7925: fix potential deadlock in mt7925_roc_abort_sync (bsc#1269416).\n- CVE-2026-53122: btrfs: fix deadlock between reflink and transaction commit when using flushoncommit (bsc#1269418).\n- CVE-2026-53133: RDMA/umem: Fix truncation for block sizes \u003e= 4G (bsc#1269821).\n- CVE-2026-53139: drm/v3d: Skip CSD when it has zeroed workgroups (bsc#1269262).\n- CVE-2026-53156: nvmem: core: fix use-after-free bugs in error paths (bsc#1269288).\n- CVE-2026-53167: fuse: limit FUSE_NOTIFY_RETRIEVE to uptodate folios (bsc#1269768).\n- CVE-2026-53168: fuse: reject fuse_notify() pagecache ops on directories (bsc#1269645).\n- CVE-2026-53176: IB/isert: Reject login PDUs shorter than ISER_HEADERS_LEN (bsc#1269710).\n- CVE-2026-53178: staging: rtl8723bs: rtw_mlme: add bounds checks before ie_length subtraction (bsc#1269795).\n- CVE-2026-53215: net: mvpp2: refill RX buffers before XDP or skb use (bsc#1269680).\n- CVE-2026-53216: net: mvpp2: limit XDP frame size to the RX buffer (bsc#1269587).\n- CVE-2026-53217: net: mvpp2: sync RX data at the hardware packet offset (bsc#1269989).\n- CVE-2026-53229: net/mlx5e: xsk: Fix DMA and xdp_frame leak on XDP_TX xmit failure (bsc#1269691).\n- CVE-2026-53249: ipv4: restrict IPOPT_SSRR and IPOPT_LSRR options (bsc#1269992).\n- CVE-2026-53258: wifi: fix leak if split 6 GHz scanning fails (bsc#1269230).\n- CVE-2026-53262: l2tp: pppol2tp: hold reference to session in pppol2tp_ioctl() (bsc#1270000).\n- CVE-2026-53263: 6lowpan: fix off-by-one in multicast context address compression (bsc#1269647).\n- CVE-2026-53266: netfilter: bridge: make ebt_snat ARP rewrite writable (bsc#1269136).\n- CVE-2026-53272: erofs: fix use-after-free on sbi-\u003esync_decompress (bsc#1269809).\n- CVE-2026-53274: net/smc: fix sleep-inside-lock in __smc_setsockopt() causing local DoS (bsc#1269651).\n- CVE-2026-53281: iommu/vt-d: Avoid NULL pointer dereference or refcount corruption (bsc#1269519).\n- CVE-2026-53285: drm/amd/display: Wrap DCN32 phantom-plane allocation in DC_RUN_WITH_PREEMPTION_ENABLED (bsc#1269527).\n- CVE-2026-53286: idpf: fix double free and use-after-free in aux device error paths (bsc#1269531).\n- CVE-2026-53287: audit: fix incorrect inheritable capability in CAPSET records (bsc#1269506).\n- CVE-2026-53306: tty: hvc_iucv: fix off-by-one in number of supported devices (bsc#1269814).\n\nThe following non security issues were fixed:\n\n- accel/ivpu: Fix signed integer truncation in IPC receive (git-fixes).\n- ACPI: CPPC: Suppress UBSAN warning caused by field misuse (git-fixes).\n- ACPI: IPMI: Fix inverted interface check in ipmi_bmc_gone() (git-fixes).\n- ACPI: IPMI: Fix message kref handling on dead device (git-fixes).\n- ACPI: NFIT: core: Fix possible NULL pointer dereference (git-fixes).\n- ACPI: resource: Amend kernel-doc style (git-fixes).\n- agp/amd64: Fix broken error propagation in agp_amd64_probe() (git-fixes).\n- ALSA: aloop: Drop superfluous break (git-fixes).\n- ALSA: caiaq: fix out-of-bounds read in the Traktor Kontrol S4 input parser (git-fixes).\n- ALSA: cmipci: check snd_ctl_new1() return value (git-fixes).\n- ALSA: core: Fix unintuitive behavior of snd_power_ref_and_wait() (git-fixes).\n- ALSA: es1938: check snd_ctl_new1() return value (git-fixes).\n- ALSA: firewire: isight: bound the sample count to the packet payload (git-fixes).\n- ALSA: gus: check snd_ctl_new1() return value (git-fixes).\n- ALSA: hda/cs35l41: Fix firmware load work teardown (git-fixes).\n- ALSA: ice1712: check snd_ctl_new1() return value (git-fixes).\n- ALSA: scarlett2: Allow flash writes ending at segment boundary (git-fixes).\n- ALSA: scarlett2: Return ENOSPC for out-of-bounds flash writes (stable-fixes).\n- ALSA: seq: Clear variable event pointer on read (git-fixes).\n- ALSA: seq: Fix kernel heap address leak in bounce_error_event() (git-fixes).\n- ALSA: seq: Fix partial userptr event expansion (git-fixes).\n- ALSA: seq: Fix uninitialised heap leak in snd_seq_event_dup() (git-fixes).\n- ALSA: seq: midi: Serialize output teardown with event_input (git-fixes).\n- ALSA: timer: Fix UAF at snd_timer_user_params() (stable-fixes).\n- ALSA: timer: Forcibly close timer instances at closing (git-fixes).\n- ALSA: usb-audio: avoid kobject path lookup in DualSense match (git-fixes).\n- ALSA: usb-audio: Kill MIDI 2.0 URBs before freeing endpoints (git-fixes).\n- ALSA: usb-audio: Propagate errors in scarlett_ctl_enum_put() (git-fixes).\n- ALSA: usb-audio: Propagate US-16x08 write errors in route/mix EQ-switch put callbacks (git-fixes).\n- ALSA: usb-audio: Roll back quirk control caches on write errors (git-fixes).\n- ALSA: usb-audio: Update Babyface Pro control caches only after successful writes (git-fixes).\n- ALSA: usb-audio: Update US-16x08 EQ/comp shadow state after successful writes (git-fixes).\n- ALSA: virtio: Add missing 384 kHz PCM rate mapping (git-fixes).\n- ALSA: virtio: Validate control metadata from the device (git-fixes).\n- ALSA: ymfpci: check snd_ctl_new1() return value (git-fixes).\n- arm64: scripts/sorttable: Implement sorting mcount_loc at boot for arm64 (bsc#1267600).\n- ASoC: adau1372: Clear PLL_EN on failed PLL lock without reset GPIO (git-fixes).\n- ASoC: amd: acp-sdw-sof: Bound DAI link iteration (git-fixes).\n- ASoC: codecs: aw88261: fix incorrect masks for boost regs (git-fixes).\n- ASoC: codecs: hdac_hdmi: Validate written enum value (git-fixes).\n- ASoC: cs35l56: Cleanup if component_probe fails (git-fixes).\n- ASoC: cs35l56: Don't leave parent IRQ disabled if system_suspend fails (git-fixes).\n- ASoC: cs35l56: Fix missing calls to wm_adsp2_remove() (git-fixes).\n- ASoC: cs35l56: Fix possible uninitialized value in cs35l56_spi_system_reset() (git-fixes).\n- ASoC: fsl: fsl_audmix: Validate written enum values (git-fixes).\n- ASoC: fsl_asrc_dma: fix eDMA maxburst misalignment with channel count (git-fixes).\n- ASoC: mediatek: mt8183: Release reserved memory on cleanup (git-fixes).\n- ASoC: mediatek: mt8192: Release reserved memory on cleanup (git-fixes).\n- ASoC: meson: aiu: Validate written enum values (git-fixes).\n- ASoC: qcom: q6apm: fix NULL pointer dereference in graph_callback (git-fixes).\n- ASoC: SOF: ipc3-control: Fix heap overflow in bytes_ext put/get (git-fixes).\n- ASoC: SOF: ipc3-control: Fix TOCTOU in bytes_put and bytes_get (git-fixes).\n- ASoC: SOF: ipc3-control: Use overflow checks in control_update size calc (git-fixes).\n- ASoC: SOF: ipc3-control: Validate size in snd_sof_update_control (git-fixes).\n- ASoC: SOF: ipc4-control: Fix TOCTOU in sof_ipc4_bytes_put (git-fixes).\n- ASoC: SOF: topology: validate vendor array size before parsing (git-fixes).\n- ASoC: tegra: tegra210_ahub: Validate written enum value (git-fixes).\n- ASoC: tlv320aic3x: restrict CLKDIV bypass Q values in dual-rate mode (git-fixes).\n- ASoC: topology: Check PCM and DAI name strings before use (git-fixes).\n- ASoC: wm_adsp: Fix NULL dereference when removing firmware controls (git-fixes).\n- Bluetooth: 6lowpan: hold L2CAP conn across debugfs control (git-fixes).\n- Bluetooth: bnep: pin L2CAP connection during netdev registration (git-fixes).\n- Bluetooth: bpa10x: avoid OOB read of revision string in bpa10x_setup() (git-fixes).\n- Bluetooth: btmtk: fix URB leak in alloc_mtk_intr_urb error path (git-fixes).\n- Bluetooth: btmtksdio: fix infinite loop in btmtksdio_txrx_work() (git-fixes).\n- Bluetooth: btnxpuart: Fix out-of-bounds firmware read in nxp_recv_fw_req_v3() (git-fixes).\n- Bluetooth: btusb: fix use-after-free on marvell probe failure (git-fixes).\n- Bluetooth: btusb: fix use-after-free on registration failure (git-fixes).\n- Bluetooth: btusb: fix wakeup irq devres lifetime (git-fixes).\n- Bluetooth: btusb: fix wakeup source leak on probe failure (git-fixes).\n- Bluetooth: eir: Fix stack OOB write when prepending the Flags AD (git-fixes).\n- Bluetooth: fix UAF in bt_accept_dequeue() (git-fixes).\n- Bluetooth: hci: validate codec capability element length (git-fixes).\n- Bluetooth: hci_core: Fix UAF in hci_unregister_dev() (git-fixes).\n- Bluetooth: hci_qca: fix NULL pointer dereference in qca_dmp_hdr() for non-serdev device (git-fixes).\n- Bluetooth: hci_uart: clear HCI_UART_SENDING when write_work is canceled (git-fixes).\n- Bluetooth: ISO: avoid NULL deref of conn in iso_conn_big_sync() (git-fixes).\n- Bluetooth: ISO: exclude RFU bits from ISO_SDU_Length (git-fixes).\n- Bluetooth: ISO: Fix data-race on iso_pi fields in hci_get_route calls (git-fixes).\n- Bluetooth: ISO: fix malformed ISO_END/CONT handling (git-fixes).\n- Bluetooth: ISO: Fix not using bc_sid as advertisement SID (stable-fixes).\n- Bluetooth: L2CAP: reject BR/EDR signaling packets over MTUsig (stable-fixes).\n- Bluetooth: L2CAP: validate option length before reading conf opt value (git-fixes).\n- Bluetooth: MGMT: Fix adv monitor add failure cleanup (git-fixes).\n- Bluetooth: MGMT: Fix UAF of hci_conn_params in add_device_complete (git-fixes).\n- Bluetooth: sco: Fix a race condition in sco_sock_timeout() (git-fixes).\n- Bluetooth: vhci: validate devcoredump state before side effects (git-fixes).\n- bnxt_en: Fix NULL pointer dereference (bsc#1268307).\n- bpf: Free reuseport cBPF prog after RCU grace period (git-fixes).\n- bus: mhi: ep: Add missing state_lock protection for mhi_state access (git-fixes).\n- bus: mhi: ep: Fix potential deadlock in mhi_ep_reset_worker() (git-fixes).\n- bus: mhi: ep: Protect mhi_ep_handle_syserr() in the error path (git-fixes).\n- char: tlclk: fix use-after-free in tlclk_cleanup() (git-fixes).\n- crypto/hmac: reject keys shorter than 128 bits in fips mode (bsc#1266284 jsc#PED-15986).\n- crypto/testmgr: disallow ffdhe2048 in fips mode (bsc#1266284 jsc#PED-15986).\n- crypto/testmgr: disallow plain ecb() usage in fips mode (bsc#1266284 jsc#PED-15986).\n- crypto/testmgr: disallow sha224 + sha3-224 in fips mode (bsc#1266284 jsc#PED-15986).\n- crypto: af_alg - Cap AEAD AD length to 0x80000000 (git-fixes).\n- crypto: amlogic - avoid double cleanup in meson_crypto_probe() (git-fixes).\n- crypto: asymmetric_keys - fix OOB read in pefile_digest_pe_contents (git-fixes).\n- crypto: atmel-sha204a - fix blocking and non-blocking rng logic (git-fixes).\n- crypto: cavium/cpt - fix DMA cleanup using wrong loop index (git-fixes).\n- crypto: ccp - Do not initialize SNP for ioctl(SNP_COMMIT) (git-fixes).\n- crypto: ccp - Do not initialize SNP for ioctl(SNP_VLEK_LOAD) (git-fixes).\n- crypto: ccp - Do not initialize SNP for SEV ioctls (git-fixes).\n- crypto: ccp - Fix snp_filter_reserved_mem_regions() off-by-one (git-fixes).\n- crypto: ccp - Treat zero-length cert chain as query for blob lengths (git-fixes).\n- crypto: drbg - Fix drbg_max_addtl() on 64-bit kernels (git-fixes).\n- crypto: drbg - Fix returning success on failure in CTR_DRBG (git-fixes).\n- crypto: drbg - Fix the fips_enabled priority boost (git-fixes).\n- crypto: ecc - Fix carry overflow in vli multiplication (git-fixes).\n- crypto: ecrdsa - fix unknown OID check in ecrdsa_param_curve (git-fixes).\n- crypto: hisilicon/qm - disable error report before flr (git-fixes).\n- crypto: marvell/octeontx - fix DMA cleanup using wrong loop index (git-fixes).\n- crypto: pcrypt - restore callback for non-parallel fallback (git-fixes).\n- crypto: qat - protect service table iterations with service_lock (git-fixes).\n- crypto: qat - validate RSA CRT component lengths (git-fixes).\n- crypto: rng - Free default RNG on module exit (git-fixes).\n- crypto: tegra - Fix dma_free_coherent size error (git-fixes).\n- crypto: tegra - fix refcount leak in tegra_se_host1x_submit() (git-fixes).\n- crypto: tegra - Return ENOMEM when input buffer allocation fails for ccm (git-fixes).\n- dm init: ensure device probing has finished in dm-mod.waitfor= (git-fixes).\n- dmaengine: dma-axi-dmac: Properly free struct axi_dmac_desc (git-fixes).\n- dmaengine: dma-axi-dmac: use DMA pool to manange DMA descriptor (git-fixes).\n- dmaengine: dw-edma: Add spinlock to protect DONE_INT_MASK and ABORT_INT_MASK (git-fixes).\n- dmaengine: Fix possible use after free (git-fixes).\n- dmaengine: imx-sdma: Refine spba bus searching in probe (git-fixes).\n- dmaengine: qcom: gpi: set DMA_PRIVATE capability (git-fixes).\n- dmaengine: tegra: Fix burst size calculation (git-fixes).\n- driver core: reject devices with unregistered buses (git-fixes).\n- driver core: use READ_ONCE() for dev-\u003edriver in dev_has_sync_state() (git-fixes).\n- Drivers: hv: vmbus: Improve the logic of reserving fb_mmio on Gen2 VMs (git-fixes).\n- drm/amd/display: add missing CSC entries for BT.2020 for DCE IPs (stable-fixes).\n- drm/amd/display: Add missing kdoc for ALLM parameters (git-fixes).\n- drm/amd/display: Clamp VBIOS HDMI retimer register count to array size (stable-fixes).\n- drm/amd/pm: fix smu13 power limit default/cap calculation (stable-fixes).\n- drm/amd/pm: mark metrics.energy_accumulator is invalid for smu 14.0.2 (stable-fixes).\n- drm/amd/pm: remove trailing semicolon from AMDGPU_PM_POLICY_ATTR macro (git-fixes).\n- drm/amd/pm: smu_v14_0_0: use SoftMin for gfxclk in set_soft_freq_limited_range (stable-fixes).\n- drm/amdgpu: Fix amdgpu_bo_move() when old_mem and new_mem are both GTT (git-fixes).\n- drm/amdgpu: fix integer overflow in amdgpu_gem_align_pitch() (git-fixes).\n- drm/amdgpu: initialize irq.lock spinlock earlier (git-fixes).\n- drm/amdgpu: restart the CS if some parts of the VM are still invalidated (stable-fixes).\n- drm/amdgpu: set sub_block_index for mca ras sub-blocks (git-fixes).\n- drm/amdgpu: skip already suspended IP blocks in ip_suspend_phase2 (git-fixes).\n- drm/amdgpu: validate CP_GFX_SHADOW chunk size in CS pass1 (git-fixes).\n- drm/amdkfd: always resume_all after suspend_all (git-fixes).\n- drm/amdkfd: Avoid double-unpin of DOORBELL/MMIO BOs on free (git-fixes).\n- drm/amdkfd: Check for pdd drm file first in CRIU restore path (stable-fixes).\n- drm/amdkfd: fix list_del corruption in kfd_criu_resume_svm (git-fixes).\n- drm/amdkfd: fix NULL pointer bug in svm_range_set_attr (stable-fixes).\n- drm/amdkfd: Use exclusive bounds for SVM split alignment checks (git-fixes).\n- drm/amdkfd: Validate CRIU-restored IDs before idr_alloc (git-fixes).\n- drm/bridge: cdns-dsi: Replace deprecated UNIVERSAL_DEV_PM_OPS() (git-fixes).\n- drm/dp/mst: fix buffer overflows in sideband chunk accumulation (git-fixes).\n- drm/dp/mst: fix OOB reads in remote DPCD/I2C sideband reply parsers (git-fixes).\n- drm/dp/mst: fix OOB reads on 2-byte fields in sideband reply parsers (git-fixes).\n- drm/dp: Add eDP 1.5 bit definition (stable-fixes).\n- drm/edid: fix OOB read in drm_parse_tiled_block() (git-fixes).\n- drm/gpuvm: Do not prepare NULL objects (git-fixes).\n- drm/hisilicon/hibmc: move display contrl config to hibmc_probe() (git-fixes).\n- drm/hisilicon/hibmc: use clock to look up the PLL value (git-fixes).\n- drm/hyperv: use VMBUS_RING_SIZE() (git-fixes).\n- drm/i915/gem: Add missing nospec on parallel submit slot (git-fixes).\n- drm/i915/gem: Fix phys BO pread/pwrite with offset (git-fixes).\n- drm/i915/psr: Add defininitions for INTEL_WA_REGISTER_CAPS DPCD register (stable-fixes).\n- drm/i915: clear CRTC color blob pointers after dropping refs (git-fixes).\n- drm/imagination: Count paired job fence as dependency in prepare_job() (git-fixes).\n- drm/imagination: Fit paired fragment job in the correct CCCB (git-fixes).\n- drm/msm/dp: fix HPD state status bit shift value (git-fixes).\n- drm/msm/dp: Fix the ISR_* enum values (git-fixes).\n- drm/nouveau/acr: fix missing nvkm_done() in error path of nvkm_acr_oneinit() (git-fixes).\n- drm/nouveau/bios: specify correct display fuse register for Ampere and Ada (git-fixes).\n- drm/nouveau: fix reversed error cleanup order in ucopy functions (git-fixes).\n- drm/panthor: Fix kernel-doc warning in panthor_sched.c (git-fixes).\n- drm/radeon: fix integer overflow in radeon_align_pitch() (git-fixes).\n- drm/radeon: fix memory leak in radeon_ring_restore() on lock failure (git-fixes).\n- drm/rockchip: cdn-dp: add missing check in cdn_dp_config_video() (git-fixes).\n- drm/rockchip: Test for imported buffers with drm_gem_is_imported() (git-fixes).\n- drm/syncobj: Fix memory leak in drm_syncobj_find_fence() (git-fixes).\n- drm/tegra: dc: Fix device node reference leak in tegra_dc_has_output() (git-fixes).\n- drm/tegra: Fix iommu_map_sgtable() return value check (git-fixes).\n- drm/tidss: Drop extra drm_mode_config_reset() call (git-fixes).\n- drm/tidss: Fix missing drm_bridge_add() call (git-fixes).\n- drm/vc4: fix krealloc() memory leak (git-fixes).\n- drm/virtio: fix dma_fence refcount leak on error in virtio_gpu_dma_fence_wait() (git-fixes).\n- drm/virtio: Fix driver removal with disabled KMS (git-fixes).\n- drm/xe: fix refcount leak in xe_range_fence_insert() (git-fixes).\n- drm: renesas: rzg2l_mipi_dsi: Increase reset deassertion delay (git-fixes).\n- fbdev: Fix fb_new_modelist to prevent null-ptr-deref in fb_videomode_to_var (stable-fixes).\n- fbdev: fix use-after-free in store_modes() (stable-fixes).\n- fbdev: modedb: fix a possible UAF in fb_find_mode() (stable-fixes).\n- fbdev: modedb: Fix misaligned fields in the 1920x1080-60 mode (git-fixes).\n- firmware: arm_scmi: Fix OOB in scmi_power_name_get() (git-fixes).\n- firmware: arm_scmi: Read sensor config as 32-bit value (git-fixes).\n- firmware_loader: fix device reference leak in firmware_upload_register() (git-fixes).\n- firmware_loader: Fix recursive lock in device_cache_fw_images() (git-fixes).\n- fpga: dfl: add bounds check in dfh_get_param_size() (git-fixes).\n- fpga: microchip-spi: fix zero header_size OOB read in mpf_ops_parse_header() (git-fixes).\n- fpga: region: fix use-after-free in child_regions_with_firmware() (git-fixes).\n- ftrace: Check against is_kernel_text() instead of kaslr_offset() (bsc#1267600).\n- ftrace: Do not over-allocate ftrace memory (bsc#1267600).\n- ftrace: Have ftrace pages output reflect freed pages (bsc#1267600).\n- ftrace: Test mcount_loc addr before calling ftrace_call_addr() (bsc#1267600).\n- ftrace: Update the mcount_loc check of skipped entries (bsc#1267600).\n- gpio: mvebu: fix NULL pointer dereference in suspend/resume (git-fixes).\n- gpio: mxc: fix irq_high handling (git-fixes).\n- gpio: rockchip: convert bank-\u003eclk to devm_clk_get_enabled() (git-fixes).\n- gpio: virtuser: Fix uninitialized data bug in gpio_virtuser_direction_do_write() (git-fixes).\n- gpio: zynq: fix runtime PM leak on remove (git-fixes).\n- gpiolib: Extract gpiochip_choose_fwnode() for wider use (stable-fixes).\n- gpiolib: Remove redundant assignment of return variable (stable-fixes).\n- gpu: host1x: Allow entries in BO caches to be freed (git-fixes).\n- gpu: host1x: Fix device reference leak in host1x_device_parse_dt() error path (git-fixes).\n- gpu: host1x: Fix iommu_map_sgtable() return value check (git-fixes).\n- HID: core: Add printk_ratelimited variants to hid_warn() etc (stable-fixes).\n- HID: hid-goodix-spi: validate report size to prevent stack buffer overflow (git-fixes).\n- HID: letsketch: fix UAF on inrange_timer at driver unbind (git-fixes).\n- HID: lg-g15: cancel pending work on remove to fix a use-after-free (git-fixes).\n- HID: logitech-hidpp: remove excess kernel-doc member in hidpp_scroll_counter (git-fixes).\n- HID: picolcd: prevent NULL pointer dereference in picolcd_send_and_wait() (git-fixes).\n- HID: quirks: Add ALWAYS_POLL quirk for SIGMACHIP USB mouse (stable-fixes).\n- HID: rate-limit hid_warn to prevent log flooding (stable-fixes).\n- HID: remove duplicate hid_warn_ratelimited definition (git-fixes).\n- HID: wacom: Fix OOB write in wacom_hid_set_device_mode() (git-fixes).\n- HID: wacom: stop hardware after post-start probe failures (git-fixes).\n- HID: wiimote: Fix table layout and whitespace errors (git-fixes).\n- hv: utils: handle and propagate errors in kvp_register (git-fixes).\n- hv: utils: replace deprecated strcpy with strscpy in kvp_register (git-fixes).\n- hv_balloon: Simplify data output in hv_balloon_debug_show() (git-fixes).\n- hv_netvsc: use kmap_local_page in netvsc_copy_to_send_buf (git-fixes).\n- hwmon: (aspeed-g6-pwm-tach) Guard fan RPM calculation against divide-by-zero (git-fixes).\n- hwmon: (asus_atk0110) Check package count before accessing element (git-fixes).\n- hwmon: (it87) Clamp negative values to zero in set_fan() (git-fixes).\n- hwmon: (ltc2992) add missing 'select REGMAP_I2C' to Kconfig (git-fixes).\n- hwmon: (max1619) add missing 'select REGMAP' to Kconfig (git-fixes).\n- hwmon: (max6697) add missing 'select REGMAP_I2C' to Kconfig (git-fixes).\n- hwmon: (occ) unregister sysfs devices outside occ lock (git-fixes).\n- hwmon: adm1275: Prevent reading uninitialized stack (git-fixes).\n- hwrng: jh7110 - fix refcount leak in starfive_trng_read() (git-fixes).\n- hwrng: virtio: clamp device-reported used.len at copy_data() (git-fixes).\n- hyperv: Clean up and fix the guest ID comment in hvgdk.h (git-fixes).\n- i2c: core: disable runtime PM on adapter registration failure (git-fixes).\n- i2c: core: fix adapter debugfs creation (git-fixes).\n- i2c: core: fix adapter deregistration race (git-fixes).\n- i2c: core: fix adapter probe deferral loop (git-fixes).\n- i2c: core: fix adapter registration race (git-fixes).\n- i2c: core: fix hang on adapter registration failure (git-fixes).\n- i2c: core: fix irq domain leak on adapter registration failure (git-fixes).\n- i2c: core: fix NULL-deref on adapter registration failure (git-fixes).\n- i2c: dev: prevent integer overflow in I2C_TIMEOUT ioctl (stable-fixes).\n- i2c: imx-lpi2c: mark I2C adapter when hardware is powered down (git-fixes).\n- i2c: mpc: Fix timeout calculations (git-fixes).\n- i2c: qcom-cci: Fix NULL pointer dereference in cci_remove() (git-fixes).\n- i2c: riic: fix refcount leak in riic_i2c_resume_noirq() (git-fixes).\n- i2c: stm32f7: fix timing computation ignoring i2c-analog-filter (git-fixes).\n- i2c: stm32f7: truncate clock period instead of rounding it (git-fixes).\n- i2c: tegra: Fix NOIRQ suspend/resume (git-fixes).\n- i3c: master: Prevent reuse of dynamic address on device add failure (git-fixes).\n- i3c: master: Serialize i3c_set_hotjoin() with the maintenance lock (git-fixes).\n- ice: ptp: don't WARN when controlling PF is unavailable (bsc#1267251).\n- iio: accel: mma8452: handle I2C read error(s) in mma8452_read() (git-fixes).\n- iio: adc: ti-ads1298: add bounds check to pga_settings index (stable-fixes).\n- iio: adc: xilinx-ams: fix out-of-bounds channel lookup in event handling (git-fixes).\n- iio: backend: fix uninitialized data in debugfs (git-fixes).\n- iio: chemical: scd30: Cleanup initializations and fix sign-extension bug (git-fixes).\n- iio: chemical: scd30: fix division by zero in write_raw (git-fixes).\n- iio: chemical: scd30: Use guard(mutex) to allow early returns (stable-fixes).\n- iio: gyro: bmg160: bail out when bandwidth/filter is not in table (git-fixes).\n- iio: gyro: bmg160: wait full startup time after mode change at probe (git-fixes).\n- iio: light: opt3001: fix missing state reset on timeout (git-fixes).\n- iio: light: si1133: prevent race condition on timeout (git-fixes).\n- iio: light: si1133: reset counter to prevent race condition (git-fixes).\n- iio: light: veml6030: fix channel type when pushing events (git-fixes).\n- iio: light: veml6075: add bounds check to veml6075_it_ms index (stable-fixes).\n- iio: magnetometer: ak8975: Add missed pm_runtime_put_autosuspend() call (git-fixes).\n- iio: resolver: ad2s1210: notify trigger and clear state on fault read error (git-fixes).\n- iio: tcs3472: power down chip on probe failure (git-fixes).\n- iio: temperature: ltc2983: Fix n_wires default bypassing rotation check (git-fixes).\n- iio: temperature: ltc2983: Fix reinit_completion() called after conversion start (git-fixes).\n- Input: atkbd - add DMI quirk for Lenovo Yoga Air 14 (83QK) (stable-fixes).\n- Input: elan_i2c - validate firmware size before use (stable-fixes).\n- Input: synaptics - add LEN2058 to SMBus passlist for ThinkPad E490 (stable-fixes).\n- Input: xpad - add \"Nova 2 Lite\" from GameSir (stable-fixes).\n- Input: xpad - add support for ASUS ROG RAIKIRI II (stable-fixes).\n- io_uring/cancel: de-unionize file and user_data in struct io_cancel_data (git-fixes bsc#1261250).\n- io_uring/filetable: clamp alloc_hint to the configured alloc range (git-fixes bsc#1261250).\n- io_uring/io-wq: fix incorrect io_wq_for_each_worker() termination logic (git-fixes bsc#1261250).\n- io_uring/poll: ensure EPOLL_ONESHOT is propagated for EPOLL_URING_WAKE (git-fixes bsc#1261250).\n- io_uring/wait: fix min_timeout behavior (git-fixes bsc#1261250).\n- io_uring/waitid: clear waitid info before copying it to userspace (git-fixes).\n- io_uring: fix min_wait wakeups for SQPOLL (git-fixes bsc#1261250).\n- ipv4: account for fraggap on the paged allocation path (git-fixes).\n- ipv6: account for fraggap on the paged allocation path (git-fixes).\n- KEYS: fix overflow in keyctl_pkey_params_get_2() (git-fixes).\n- KEYS: Use acquire when reading state in keyring search (git-fixes).\n- KVM: arm64: PMU: Preserve AArch32 counter low bits (git-fixes).\n- KVM: arm64: vgic: Free private_irqs when init fails after allocation (git-fixes).\n- KVM: Don't WARN if memory is dirtied without a vCPU when the VM is dying (git-fixes).\n- KVM: nSVM: Always use NextRIP as vmcb02's NextRIP after first L2 VMRUN (git-fixes).\n- KVM: nSVM: Always use vmcb01 in VMLOAD/VMSAVE emulation (git-fixes).\n- KVM: nSVM: Ensure AVIC is inhibited when restoring a vCPU to guest mode (git-fixes).\n- KVM: nSVM: Mark all of vmcb02 dirty when restoring nested state (git-fixes).\n- KVM: nSVM: Sync interrupt shadow to cached vmcb12 after VMRUN of L2 (git-fixes).\n- KVM: nSVM: Sync NextRIP to cached vmcb12 after VMRUN of L2 (git-fixes).\n- KVM: nVMX: Immediately refresh APICv controls as needed on nested VM-Exit (git-fixes).\n- KVM: Replace guest-triggerable BUG_ON() in ioeventfd datamatch with get_unaligned() (git-fixes).\n- KVM: SEV: Add an anonymous \"psc\" struct to track current PSC metadata (git-fixes).\n- KVM: SEV: Decouple the need to sync the GHCB SA from the need to free the SA (git-fixes).\n- KVM: SEV: Don't terminate SNP VMs on #VMGEXIT without a registered GHCB (git-fixes).\n- KVM: SEV: Make it more obvious when KVM is writing back the current PSC index (git-fixes).\n- KVM: SEV: Move sev_free_vcpu() down below sev_es_unmap_ghcb() (git-fixes).\n- KVM: SEV: Read start/end indices of PSC requests exactly once per #VMGEXIT (git-fixes).\n- KVM: SEV: Return INVALID_EVENT for SNP-only #VMGEXIT from non-SNP guest (git-fixes).\n- KVM: SEV: Return INVALID_INPUT, not MISSING_INPUT, for bad GUEST_REQUEST input(s) (git-fixes).\n- KVM: SEV: Unmap and unpin the GHCB as needed on vCPU free (git-fixes).\n- KVM: SVM: Allow KVM_SET_NESTED_STATE to clear GIF when SVME==0 (git-fixes).\n- KVM: SVM: check validity of VMCB controls when returning from SMM (git-fixes).\n- KVM: SVM: Don't set GIF when clearing EFER.SVME (git-fixes).\n- KVM: SVM: Truncate INVLPGA address in compatibility mode (git-fixes).\n- KVM: Use vCPU specific memslots in __kvm_vcpu_map() (git-fixes).\n- KVM: VMX: Grab vmcs12 on CR8 interception update iff vCPU is in guest mode (git-fixes).\n- KVM: VMX: Read 32-bit GPR values for ENCLS instructions outside of 64-bit mode (git-fixes).\n- KVM: x86/mmu: Ensure hugepage is in by slot before checking max mapping level (git-fixes).\n- KVM: x86/mmu: Recursively zap orphaned nested TDP shadow pages on emulated writes (git-fixes).\n- KVM: x86/xen: Bug the VM if 32-bit KVM observes a 64-bit mode hypercall (git-fixes).\n- KVM: x86/xen: Don't truncate RAX when handling hypercall from protected guest (git-fixes).\n- KVM: x86: Consolidate CPUID fault handling for emulator and interception logic (git-fixes).\n- KVM: x86: Fix shadow paging use-after-free due to unexpected role (git-fixes).\n- KVM: x86: hyper-v: Bound the bank index when querying sparse banks (git-fixes).\n- KVM: x86: ioapic: Use old_dest_mode consistently in ioapic_write_indirect() (git-fixes).\n- KVM: x86: Move update_cr8_intercept() to lapic.c (git-fixes).\n- KVM: x86: Prioritize CPUID faulting over CPUID VM-exits in nested VMX (git-fixes).\n- KVM: x86: Trace hypercall register *after* truncating values for 32-bit (git-fixes).\n- KVM: x86: Unconditionally recompute CR8 intercept on PPR update (git-fixes).\n- mailbox: imx: Forward the timeout/ error in imx_mu_generic_tx() (git-fixes).\n- mailbox: mtk-adsp: fix UAF during device teardown (git-fixes).\n- misc: fastrpc: fix DMA address corruption due to find_vma misuse (git-fixes).\n- misc: fastrpc: Fix NULL pointer dereference in rpmsg callback (git-fixes).\n- misc: fastrpc: fix use-after-free of fastrpc_user in workqueue context (git-fixes).\n- misc: fastrpc: fix use-after-free race in fastrpc_map_create (git-fixes).\n- mm/vmstat: defer the refresh_zone_stat_thresholds after all CPUs bringup (bsc#1270042).\n- mtd: maps: vmu-flash: fix NULL pointer dereference in initialization (git-fixes).\n- mtd: rawnand: fix condition in 'nand_select_target()' (git-fixes).\n- mtd: rawnand: Pause continuous reads at block boundaries (git-fixes).\n- mtd: rawnand: pl353: fix probe resource allocation (git-fixes).\n- mtd: slram: remove failed entries from the device list (git-fixes).\n- mtd: spi-nor: Drop duplicate Kconfig dependency (git-fixes).\n- mtd: spi-nor: macronix: Add post_sfdp fixups for Quad Input Page Program (stable-fixes).\n- mtd: spi-nor: macronix: add support for mx66{l2, u1}g45g (stable-fixes).\n- mtd: spi-nor: spansion: use die erase for multi-die devices only (git-fixes).\n- mtd: spi-nor: swp: Improve locking user experience (git-fixes).\n- net: aquantia: Add missing descriptor cache invalidation on ATL2 (bsc#1268428).\n- net: ethtool: add ethtool COALESCE_RX_CQE_FRAMES/NSECS (bsc#1261256).\n- net: mana: Add ethtool counters for RX CQEs in coalesced type (bsc#1261256).\n- net: mana: Add support for PF device 0x00C1 (bsc#1268237).\n- net: mana: Add support for RX CQE Coalescing (bsc#1261256).\n- net: mana: Allocate interrupt context for each EQ when creating vPort (git-fixes).\n- net: mana: Cache MANA_QUERY_LINK_CONFIG result to avoid repeated HWC queries (bsc#1268238).\n- net: mana: Create separate EQs for each vPort (git-fixes).\n- net: mana: Fall back to standard MTU when PF reports adapter_mtu of 0 (git-fixes).\n- net: mana: guard TX wq object destroy with INVALID_MANA_HANDLE check (git-fixes).\n- net: mana: initialize gdma queue id to INVALID_QUEUE_ID (git-fixes).\n- net: mana: Introduce GIC context with refcounting for interrupt management (git-fixes).\n- net: mana: Optimize irq affinity for low vcpu configs (git-fixes).\n- net: mana: Query device capabilities and configure MSI-X sharing for EQs (git-fixes).\n- net: mana: Sync page pool RX frags for CPU (git-fixes).\n- net: mana: Use GIC functions to allocate global EQs (git-fixes).\n- net: mana: Validate the packet length reported by the NIC (git-fixes).\n- net: phy: sfp: free mii_bus in sfp_i2c_mdiobus_destroy (git-fixes).\n- net: usb: lan78xx: disable VLAN filter in promiscuous mode (git-fixes).\n- net: usb: net1080: validate packet_len before pad-byte access in rx_fixup (git-fixes).\n- net: wwan: iosm: bound device offsets in the MUX downlink decoder (git-fixes).\n- nfc: hci: fix out-of-bounds read in HCP header parsing (git-fixes).\n- nfc: llcp: Fix use-after-free in llcp_sock_release() (git-fixes).\n- nfc: llcp: Fix use-after-free race in nfc_llcp_recv_cc() (git-fixes).\n- packaging: Add nvidia kernel description.\n- packaging: compute-PATCHVERSION.sh -\u003e compute-PATCHVERSION.\n- page_pool: Fix PP_MAGIC_MASK to avoid crashing on some 32-bit arches (bsc#1261562).\n- page_pool: Move pp_magic check into helper functions (bsc#1261562).\n- page_pool: Track DMA-mapped pages and unmap them when destroying the pool (bsc#1261562).\n- PCI: Update saved_config_space upon resource assignment (git-fixes).\n- perf/x86/intel/uncore: Fix die ID init and look up bugs (bsc#1267419).\n- perf/x86/intel/uncore: Skip discovery table for offline dies (bsc#1267419).\n- platform/x86: dell-laptop: fix missing cleanups in init error path (git-fixes).\n- platform/x86: intel-hid: Protect ACPI notify handler against recursion (git-fixes).\n- platform/x86: xo15-ebook: Fix wakeup source and GPE handling (git-fixes).\n- PM: sleep: Use complete() in device_pm_sleep_init() (git-fixes).\n- power: reset: linkstation-poweroff: fix use-after-free in the linkstation_poweroff_init() (git-fixes).\n- power: supply: charger-manager: fix refcount leak in is_full_charged() (git-fixes).\n- power: supply: core: fix supplied_from allocations (git-fixes).\n- power: supply: cpcap-battery: Fix missing nvmem_device_put() causing reference leak (git-fixes).\n- powerpc/boot: Allow text relocations for pseries wrapper with binutils 2.46+ (git-fixes).\n- powerpc/fadump: define MIN_RMA in bytes rather than MB (bsc#1236743 git-fixes).\n- ppc/fadump: invoke kmsg_dump in fadump panic path (bsc#1270226 ltc#218302).\n- pwm: imx27: Fix variable truncation in .apply() (git-fixes).\n- RDMA/mana_ib: Allocate interrupt contexts on EQs (git-fixes).\n- RDMA/mana_ib: Use ib_get_eth_speed for reporting port speed (git-fixes).\n- regulator: scmi: fix of_node refcount leak in scmi_regulator_probe() (git-fixes).\n- Revert \"fs: don't block i_writecount during exec\" (bsc#1269982).\n- rtc: abx80x: fix the RTC_VL_CLR clearing all status flags (git-fixes).\n- rtc: cmos: unregister HPET IRQ handler on probe failure (git-fixes).\n- rtc: ds1307: Fix off-by-one issue with wday for rx8130 (git-fixes).\n- rtc: ds1307: handle oscillator stop flag for ds1337/ds1339/ds3231 (git-fixes).\n- rtc: mpfs: fix counter upload completion condition (git-fixes).\n- rtc: msc313: fix NULL deref in shared IRQ handler at probe (git-fixes).\n- scripts/sorttable: Add helper functions for Elf_Ehdr (bsc#1267600).\n- scripts/sorttable: Add helper functions for Elf_Shdr (bsc#1267600).\n- scripts/sorttable: Add helper functions for Elf_Sym (bsc#1267600).\n- scripts/sorttable: Allow matches to functions before function entry (bsc#1267600).\n- scripts/sorttable: Always use an array for the mcount_loc sorting (bsc#1267600).\n- scripts/sorttable: Convert Elf_Ehdr to union (bsc#1267600).\n- scripts/sorttable: Convert Elf_Sym MACRO over to a union (bsc#1267600).\n- scripts/sorttable: Fix endianness handling in build-time mcount sort (bsc#1267600).\n- scripts/sorttable: Get start/stop_mcount_loc from ELF file directly (bsc#1267600).\n- scripts/sorttable: Have mcount rela sort use direct values (bsc#1267600).\n- scripts/sorttable: Have the ORC code use the _r() functions to read (bsc#1267600).\n- scripts/sorttable: Make compare_extable() into two functions (bsc#1267600).\n- scripts/sorttable: Move code from sorttable.h into sorttable.c (bsc#1267600).\n- scripts/sorttable: Remove unneeded Elf_Rel (bsc#1267600).\n- scripts/sorttable: Remove unused macro defines (bsc#1267600).\n- scripts/sorttable: Remove unused write functions (bsc#1267600).\n- scripts/sorttable: Replace Elf_Shdr Macro with a union (bsc#1267600).\n- scripts/sorttable: Use a structure of function pointers for elf helpers (bsc#1267600).\n- scripts/sorttable: Use normal sort if theres no relocs in the mcount section (bsc#1267600).\n- scripts/sorttable: Use uint64_t for mcount sorting (bsc#1267600).\n- scripts/sorttable: Zero out weak functions in mcount_loc table (bsc#1267600).\n- scsi: smartpqi: Use shost_to_hba() in pqi_scan_finished() (bsc#1257506).\n- scsi: storvsc: Replace symbolic permissions with octal (git-fixes).\n- scsi: target: Fix hexadecimal CHAP_I handling (git-fixes).\n- selftests/bpf: Add BPF_STRICT_BUILD toggle (poo#202224).\n- selftests/bpf: Allow test_progs to link with a partial object set (poo#202224).\n- selftests/bpf: Avoid rebuilds when running emit_tests (poo#202224).\n- selftests/bpf: Consolidate kernel modules into common directory (poo#202224).\n- selftests/bpf: Copy test_kmods when installing selftest (poo#202224).\n- selftests/bpf: Fix runqslower cross-endian build (poo#202224).\n- selftests/bpf: Fix test_kmods KDIR to honor O= and distro kernels (poo#202224).\n- selftests/bpf: make BPF_TARGET_ENDIAN non-recursive to speed up *.bpf.o build (poo#202224).\n- selftests/bpf: Make skeleton headers order-only prerequisites of .test.d (poo#202224).\n- selftests/bpf: Provide weak definitions for cross-test functions (poo#202224).\n- selftests/bpf: Skip tests whose objects were not built (poo#202224).\n- selftests/bpf: Support cross-endian building (poo#202224).\n- selftests/bpf: Tolerate benchmark build failures (poo#202224).\n- selftests/bpf: Tolerate BPF and skeleton generation failures (poo#202224).\n- selftests/bpf: Tolerate missing files during install (poo#202224).\n- selftests/bpf: Tolerate test file compilation failures (poo#202224).\n- serial: 8250: dispatch SysRq character in serial8250_handle_irq() (git-fixes).\n- serial: 8250_dw: dispatch SysRq character in dw8250_handle_irq() (git-fixes).\n- serial: qcom_geni: Fix RX DMA stall when SE_DMA_RX_LEN_IN is zero (git-fixes).\n- slimbus: qcom-ngd-ctrl: Avoid ABBA on tx_lock/ctrl-\u003elock (git-fixes).\n- slimbus: qcom-ngd-ctrl: Balance pm_runtime enablement for NGD (git-fixes).\n- slimbus: qcom-ngd-ctrl: Correct PDR and SSR cleanup ownership (git-fixes).\n- slimbus: qcom-ngd-ctrl: fix OF node refcount (git-fixes).\n- slimbus: qcom-ngd-ctrl: Fix probe error path ordering (git-fixes).\n- slimbus: qcom-ngd-ctrl: Fix up platform_driver registration (git-fixes).\n- slimbus: qcom-ngd-ctrl: Initialize controller resources in controller (git-fixes).\n- slimbus: qcom-ngd-ctrl: Register callbacks after creating the ngd (git-fixes).\n- soc: qcom: ice: Fix race between qcom_ice_probe() and of_qcom_ice_get() (git-fixes).\n- soc: qcom: ice: Return -ENODEV if the ICE platform device is not found (git-fixes).\n- spi: at91-usart: drop dead runtime pm support (git-fixes).\n- spi: dw: fix wrong BAUDR setting after resume (git-fixes).\n- spi: ep93xx: fix double-free of zeropage on DMA setup failure (git-fixes).\n- spi: fsl-lpspi: replace dmaengine_terminate_all() with dmaengine_terminate_sync() (git-fixes).\n- spi: fsl-lpspi: terminate the RX channel on TX prepare failure path (git-fixes).\n- spi: hisi-kunpeng: Use dev_err_probe() for host registration failure (git-fixes).\n- spi: meson-spifc: fix runtime PM leak on remove (git-fixes).\n- spi: rpc-if: Use correct device for hardware reinitialization on resume (git-fixes).\n- spi: uniphier: Fix completion initialization order before devm_request_irq() (git-fixes).\n- spi: xilinx: use FIFO occupancy register to determine buffer size (git-fixes).\n- Split off kABI workaround for bsc#1267458 (bsc#1267458).\n- staging: most: video: avoid double free on video register failure (git-fixes).\n- staging: nvec: fix use-after-free in nvec_rx_completed() (git-fixes).\n- thermal: hwmon: Fix critical temperature attribute removal (git-fixes).\n- thermal: intel: Fix dangling resources on thermal_throttle_online() failure (git-fixes).\n- thermal: testing: reject missing command arguments (git-fixes).\n- thermal: testing: zone: Flush work items during cleanup (git-fixes).\n- thunderbolt: Bound root directory content to block size (git-fixes).\n- thunderbolt: Clamp XDomain response data copy to allocation size (git-fixes).\n- thunderbolt: debugfs: Don't stop reading SB registers if just one fails (git-fixes).\n- thunderbolt: debugfs: Fix margining error counter buffer leak (git-fixes).\n- thunderbolt: Limit XDomain response copy to actual frame size (git-fixes).\n- thunderbolt: Reject zero-length property entries in validator (git-fixes).\n- thunderbolt: Validate XDomain request packet size before type cast (git-fixes).\n- tools/power/x86/intel-speed-select: Harden daemon pidfile open (git-fixes).\n- tpm: fix event_size output in tpm1_binary_bios_measurements_show (git-fixes).\n- tpm: tpm2-sessions: wait for async KPP completion in tpm_buf_append_salt (git-fixes).\n- tpm: tpm_tis_spi: Use wait_woken() in wait_for_tmp_stat() (git-fixes).\n- usb: core: Fix SuperSpeed root hub wMaxPacketSize (stable-fixes).\n- usb: core: Fix up Interrupt IN endpoints with bogus wBytesPerInterval (stable-fixes).\n- usb: host: max3421: Fix shift-out-of-bounds in max3421_hub_control() (git-fixes).\n- usb: host: max3421: Reject hub port requests for non-existent ports (git-fixes).\n- USB: quirks: add NO_LPM for Lenovo ThinkPad USB-C Dock Gen2 hub controllers (git-fixes).\n- USB: serial: io_ti: fix heap overflow in build_i2c_fw_hdr() (git-fixes).\n- USB: serial: io_ti: fix heap overflow in get_manuf_info() (git-fixes).\n- USB: serial: kl5kusb105: fix bulk-out buffer overflow (git-fixes).\n- USB: serial: option: add usb-id for Dell Wireless DW5826e-m (stable-fixes).\n- usb: storage: Add quirks for PNY Elite Portable SSD (git-fixes).\n- usb: typec: altmodes/displayport: validate count before reading Status Update VDO (stable-fixes).\n- usb: typec: tcpm/tcpci_maxim: validate header NDO against RX_BYTE_CNT (stable-fixes).\n- usb: typec: tcpm: bound altmode_desc[] per iteration in svdm_consume_modes() (stable-fixes).\n- usb: typec: tcpm: validate VDO count in Discover Identity ACK handlers (stable-fixes).\n- usb: typec: ucsi: ccg: reject firmware images without a ':' record header (stable-fixes).\n- usb: typec: ucsi: displayport: NAK DP_CMD_CONFIGURE without a payload VDO (stable-fixes).\n- usb: typec: ucsi: validate connector number in ucsi_connector_change() (stable-fixes).\n- usb: typec: wcove: don't write past struct pd_message in wcove_read_rx_buffer() (stable-fixes).\n- usbnet: gl620a: fix out-of-bounds read in genelink_rx_fixup() (git-fixes).\n- vc_screen: fix null-ptr-deref in vcs_notifier() during concurrent vcs_write (git-fixes).\n- watchdog/hpwdt: Refine hpwdt message for UV platform (bsc#1269199).\n- watchdog: apple: Add \"apple,t8103-wdt\" compatible (git-fixes).\n- watchdog: sama5d4_wdt: Fix WDDIS detection on SAM9X60 and SAMA7G5 (git-fixes).\n- watchdog: sp5100_tco: Use EFCH MMIO for newer Hygon FCH (git-fixes).\n- watchdog: sprd_wdt: Remove redundant sprd_wdt_disable() on register failure (git-fixes).\n- watchdog: unregister PM notifier on watchdog unregister (git-fixes).\n- wifi: ath9k: fix OOB access from firmware tx status queue ID (git-fixes).\n- wifi: ath11k: fix warning when unbinding (git-fixes).\n- wifi: cfg80211: fix grammar in MLO group key error message (git-fixes).\n- wifi: iwlwifi: mvm: fix race condition in PTP removal (stable-fixes).\n- wifi: mac80211: fix monitor mode frame capture for real chanctx drivers (git-fixes).\n- wifi: mt76: fix argument to ieee80211_is_first_frag() (git-fixes).\n- wifi: mt76: mt76x2u: Add support for ELECOM WDC-867SU3S (stable-fixes).\n- wifi: mt76: mt792x: skip MLD header rewrite for 802.3 encap TX (git-fixes).\n- wifi: mt76: mt7915: fix potential tx_retries underflow (git-fixes).\n- wifi: mt76: mt7921: avoid undesired changes of the preset regulatory domain (stable-fixes).\n- wifi: mt76: mt7921: fix a potential scan no APs (stable-fixes).\n- wifi: mt76: mt7921: fix potential tx_retries underflow (git-fixes).\n- wifi: mt76: mt7925: clean up DMA on probe failure (git-fixes).\n- wifi: mt76: mt7925: don't disable AP BSS when removing TDLS peer (git-fixes).\n- wifi: mt76: mt7925: fix potential tx_retries underflow (git-fixes).\n- wifi: mt76: mt7925: fix stale pointer comparisons in change_vif_links (git-fixes).\n- wifi: mt76: mt7925: keep TX BA state in the primary WCID (git-fixes).\n- wifi: mt76: mt7996: fix potential tx_retries underflow (git-fixes).\n- wifi: rtlwifi: rtl8821ae: Fix C2H bit location in RX descriptor (git-fixes).\n- wifi: rtw88: fix OOB read from firmware RX descriptor exceeding DMA buffer (git-fixes).\n- wifi: rtw88: increase TX report timeout to fix race condition (git-fixes).\n- wifi: rtw88: usb: fix memory leaks on USB write failures (git-fixes).\n- wifi: rtw89: Correct data type for scan index to avoid infinite loop (git-fixes).\n- wifi: wcn36xx: fix heap overflow from oversized firmware HAL response (git-fixes).\n- wifi: wcn36xx: fix OOB read from firmware count in PRINT_REG_INFO indication (git-fixes).\n- wifi: wcn36xx: fix OOB read from short trigger BA firmware response (git-fixes).\n- x86/cpu/amd: Correct the microcode table for Zenbleed (git-fixes).\n- x86/cpu: Disable FRED when PTI is forced on (git-fixes).\n- x86/cpu: Properly parse CPUID leaf 0x2 TLB descriptor 0x63 (git-fixes).\n- x86/cpu: Validate CPUID leaf 0x2 EDX output (git-fixes).\n- x86/irq: Ensure initial PIR loads are performed exactly once (git-fixes).\n- x86/platform/uv: Expose the uv_hub_type() interface (jsc#PED-16390).\n- x86/tsc: Disable clocksource watchdog checking on recent and future UV platforms (jsc#PED-16390).\n- X.509: Fix validation of ASN.1 certificate header (git-fixes).\n- xfrm: Fix dev use-after-free in xfrm async resumption (bsc#1268276).\n","status":"published","published":"2026-07-21T08:27:34Z","modified":"2026-07-23T18:24:18.071402846Z","updated_at":"2026-11-02T15:54:03.080707Z"},{"id":"SUSE-SU-2026:22769-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-10263: arm64: cputype: Add C1-Premium definitions (bsc#1266290).\n- CVE-2025-39894: netfilter: br_netfilter: do not check confirmed bit\n  in br_nf_local_in() after confirm (bsc#1262430).\n- CVE-2025-40341: futex: Don't leak robust_list pointer on exec race (bsc#1255029).\n- CVE-2026-23248: perf: Make perf_pmu_unregister() useable (bsc#1259800).\n- CVE-2026-23394: Revert: \"af_unix: Remove lock dance in unix_peek_fds().\" (bsc#1260565).\n- CVE-2026-23451: bonding: prevent potential infinite loop in bond_header_parse() (bsc#1261604).\n- CVE-2026-31414: netfilter: nf_conntrack_expect: use expect-\u003ehelper (bsc#1262085).\n- CVE-2026-31429: net: skb: fix cross-cache free of KFENCE-allocated skb head (bsc#1262392).\n- CVE-2026-31438: netfs: Fix kernel BUG in netfs_limit_iter() for ITER_KVEC iterators (bsc#1267824).\n- CVE-2026-31450: ext4: publish jinode after initialization (bsc#1262618).\n- CVE-2026-31452: ext4: convert inline data to extents when truncate exceeds inline size (bsc#1262620).\n- CVE-2026-31466: mm/huge_memory: fix folio isn't locked in softleaf_to_folio() (bsc#1267825).\n- CVE-2026-31469: virtio_net: Fix UAF on dst_ops when IFF_XMIT_DST_RELEASE is cleared and napi_tx is false\n  (bsc#1267816).\n- CVE-2026-31479: drm/xe: always keep track of remap prev/next (bsc#1262765).\n- CVE-2026-31492: RDMA/irdma: Initialize free_qp completion before using it (bsc#1262748).\n- CVE-2026-31495: netfilter: ctnetlink: use netlink policy range checks (bsc#1262798).\n- CVE-2026-31499: Bluetooth: L2CAP: Fix deadlock in l2cap_conn_del() (bsc#1262674).\n- CVE-2026-31502: team: fix header_ops type confusion with non-Ethernet ports (bsc#1263072).\n- CVE-2026-31555: futex: Clear stale exiting pointer in futex_lock_pi() retry path (bsc#1263178).\n- CVE-2026-31560: spi: spi-dw-dma: fix print error log when wait finish transaction (bsc#1263057).\n- CVE-2026-31596: ocfs2: handle invalid dinode in ocfs2_group_extend (bsc#1263319).\n- CVE-2026-31646: net: lan966x: fix page_pool error handling in lan966x_fdma_rx_alloc_page_pool() (bsc#1263796).\n- CVE-2026-31647: idpf: fix PREEMPT_RT raw/bh spinlock nesting for async VC handling (bsc#1263581).\n- CVE-2026-31663: xfrm: hold device only for the asynchronous decryption (bsc#1263133).\n- CVE-2026-31664: xfrm: clear trailing padding in build_polexpire() (bsc#1263578).\n- CVE-2026-31665: netfilter: nft_ct: fix use-after-free in timeout object destroy (bsc#1263137).\n- CVE-2026-31670: net: rfkill: prevent unlimited numbers of rfkill events from being created (bsc#1263573).\n- CVE-2026-31673: af_unix: read UNIX_DIAG_VFS data under unix_state_lock (bsc#1263143).\n- CVE-2026-31674: netfilter: ip6t_rt: reject oversized addrnr in rt_mt6_check() (bsc#1263568).\n- CVE-2026-31680: net: ipv6: flowlabel: defer exclusive option free until RCU teardown (bsc#1263563).\n- CVE-2026-31693: cifs: some missing initializations on replay (bsc#1267744).\n- CVE-2026-31743: nvmem: zynqmp_nvmem: Fix buffer size in DMA and memcpy (bsc#1264067).\n- CVE-2026-31752: bridge: br_nd_send: validate ND option lengths (bsc#1264045).\n- CVE-2026-31771: Bluetooth: hci_event: move wake reason storage into validated event handlers (bsc#1264145).\n- CVE-2026-43010: bpf: Reject sleepable kprobe_multi programs at attach time (bsc#1264015).\n- CVE-2026-43014,CVE-2026-43015: net: macb: fix clk handling on PCI glue driver removal (bsc#1264010 bsc#1264012).\n- CVE-2026-43016: bpf: sockmap: Fix use-after-free of sk-\u003esk_socket in sk_psock_verdict_data_ready() (bsc#1264007).\n- CVE-2026-43022: Bluetooth: hci_sync: hci_cmd_sync_queue_once() return -EEXIST if exists (bsc#1264001).\n- CVE-2026-43024: netfilter: nf_tables: reject immediate NF_QUEUE verdict (bsc#1263930).\n- CVE-2026-43028: netfilter: x_tables: ensure names are nul-terminated (bsc#1263934).\n- CVE-2026-43034: bnxt_en: set backing store type from query type (bsc#1263998).\n- CVE-2026-43035: net: sched: cls_api: fix tc_chain_fill_node to\n  initialize tcm_info to zero to prevent an info-leak (bsc#1263996).\n- CVE-2026-43036: net: use skb_header_pointer() for TCPv4 GSO frag_off check (bsc#1263993).\n- CVE-2026-43053: xfs: factor out xfs_attr3_node_entry_remove (bsc#1264084).\n- CVE-2026-43057: net: correctly handle tunneled traffic on IPV6_CSUM GSO fallback (bsc#1264056).\n- CVE-2026-43074: eventpoll: defer struct eventpoll free to RCU grace period (bsc#1264263).\n- CVE-2026-43080: l2tp: Drop large packets with UDP encap (bsc#1264236).\n- CVE-2026-43081: net: ipa: fix GENERIC_CMD register field masks for IPA v5.0+ (bsc#1264241).\n- CVE-2026-43083: net: ioam6: fix OOB and missing lock (bsc#1264266).\n- CVE-2026-43085: netfilter: nfnetlink_log: initialize nfgenmsg in NLMSG_DONE terminator (bsc#1264230).\n- CVE-2026-43086: ipvs: fix NULL deref in ip_vs_add_service error path (bsc#1264286).\n- CVE-2026-43089: xfrm_user: fix info leak in build_mapping() (bsc#1264261).\n- CVE-2026-43090: xfrm: fix refcount leak in xfrm_migrate_policy_find (bsc#1264250).\n- CVE-2026-43092: xsk: validate MTU against usable frame size on bind (bsc#1264270).\n- CVE-2026-43093: xsk: tighten UMEM headroom validation to account for tailroom and min frame (bsc#1264254).\n- CVE-2026-43094: ixgbevf: add missing negotiate_features op to Hyper-V ops table (bsc#1264231).\n- CVE-2026-43101: ipv6: ioam: fix potential NULL dereferences in __ioam6_fill_trace_data() (bsc#1264239).\n- CVE-2026-43107: xfrm: account XFRMA_IF_ID in aevent size calculation (bsc#1264258).\n- CVE-2026-43119: Bluetooth: hci_sync: annotate data-races around hdev-\u003ereq_status (bsc#1264561).\n- CVE-2026-43124: pstore: ram_core: fix incorrect success return when vmap() fails (bsc#1264545).\n- CVE-2026-43128: RDMA/umem: Fix double dma_buf_unpin in failure path (bsc#1264612).\n- CVE-2026-43130: iommu/vt-d: Flush dev-IOTLB only when PCIe device is accessible in scalable mode (bsc#1264532).\n- CVE-2026-43132: dm-verity: correctly handle dm_bufio_client_create() failure (bsc#1264614).\n- CVE-2026-43139: xfrm6: fix uninitialized saddr in xfrm6_get_saddr() (bsc#1264294).\n- CVE-2026-43145: remoteproc: imx_rproc: Fix invalid loaded resource table detection (bsc#1265091).\n- CVE-2026-43157: octeontx2-af: CGX: fix bitmap leaks (bsc#1264624).\n- CVE-2026-43158: xfs: fix freemap adjustments when adding xattrs to leaf blocks (bsc#1264595).\n- CVE-2026-43161: iommu/vt-d: Skip dev-iotlb flush for inaccessible PCIe device without scalable mode (bsc#1264333).\n- CVE-2026-43167: xfrm: always flush state and policy upon NETDEV_UNREGISTER event (bsc#1264580).\n- CVE-2026-43171: EFI/CPER: don't dump the entire memory region (bsc#1264549).\n- CVE-2026-43175: clk: rs9: Reserve 8 struct clk_hw slots for for 9FGV0841 (bsc#1264372).\n- CVE-2026-43187: xfs: delete attr leaf freemap entries when empty (bsc#1264603).\n- CVE-2026-43191: drm/amd/display: Adjust PHY FSM transition to TX_EN-to-PLL_ON for TMDS on DCN35 (bsc#1264548).\n- CVE-2026-43194: net: consume xmit errors of GSO frames (bsc#1264304).\n- CVE-2026-43198: tcp: fix potential race in tcp_v6_syn_recv_sock() (bsc#1264610).\n- CVE-2026-43199: net/mlx5e: Fix \"scheduling while atomic\" in IPsec MAC address query (bsc#1264556).\n- CVE-2026-43205: dpaa2-switch: validate num_ifs to prevent out-of-bounds write (bsc#1264328).\n- CVE-2026-43213: wifi: rtw89: pci: validate sequence number of TX release report (bsc#1264643).\n- CVE-2026-43226: net/rds: No shortcut out of RDS_CONN_ERROR (bsc#1264544).\n- CVE-2026-43233: netfilter: nf_conntrack_h323: fix OOB read in decode_choice() (bsc#1264337).\n- CVE-2026-43238: net/sched: act_skbedit: fix divide-by-zero in tcf_skbedit_hash() (bsc#1264320).\n- CVE-2026-43240: ima: verify the previous kernel's IMA buffer lies in addressable RAM (bsc#1264386).\n- CVE-2026-43248: vhost: move vdpa group bound check to vhost_vdpa (bsc#1264302).\n- CVE-2026-43260: bnxt_en: Fix RSS context delete logic (bsc#1264429).\n- CVE-2026-43283: net: ethernet: ec_bhf: Fix dma_free_coherent() dma handle (bsc#1264295).\n- CVE-2026-43298: drm/amdgpu: Skip vcn poison irq release on VF (bsc#1264852).\n- CVE-2026-43303: mm/page_alloc: clear page-\u003eprivate in free_pages_prepare() (bsc#1264974).\n- CVE-2026-43336: lib/crypto: chacha: Zeroize permuted_state before it leaves scope (bsc#1265113).\n- CVE-2026-43337: drm/amd/display: Fix NULL pointer dereference in dcn401_init_hw() (bsc#1265112).\n- CVE-2026-43339: ipv6: prevent possible UaF in addrconf_permanent_addr() (bsc#1264763).\n- CVE-2026-43345: net: ipa: fix event ring index not programmed for IPA v5.0+ (bsc#1265103).\n- CVE-2026-43351: KVM: arm64: gic: Set vgic_model before initing private IRQs (bsc#1265082).\n- CVE-2026-43373: net: ncsi: fix skb leak in error paths (bsc#1265079).\n- CVE-2026-43374: net: nexthop: fix percpu use-after-free in remove_nh_grp_entry (bsc#1265084).\n- CVE-2026-43383: net/tcp-md5: Fix MAC comparison to be constant-time (bsc#1264744).\n- CVE-2026-43384: net/tcp-ao: Fix MAC comparison to be constant-time (bsc#1265097).\n- CVE-2026-43386: staging: rtl8723bs: fix potential out-of-bounds read in rtw_restruct_wmm_ie (bsc#1264740).\n- CVE-2026-43403: nsfs: tighten permission checks for ns iteration ioctls (bsc#1265129).\n- CVE-2026-43405: libceph: Use u32 for non-negative values in ceph_monmap_decode() (bsc#1264741).\n- CVE-2026-43406: libceph: prevent potential out-of-bounds reads in process_message_header() (bsc#1265073).\n- CVE-2026-43407: libceph: Fix potential out-of-bounds access in ceph_handle_auth_reply() (bsc#1265020).\n- CVE-2026-43415: scsi: ufs: core: Fix SError in ufshcd_rtc_work() during UFS suspend (bsc#1265123).\n- CVE-2026-43449: nvme-pci: Fix slab-out-of-bounds in nvme_dbbuf_set (bsc#1265023).\n- CVE-2026-43450: netfilter: nfnetlink_cthelper: fix OOB read in nfnl_cthelper_dump_table() (bsc#1264794).\n- CVE-2026-43452: netfilter: x_tables: guard option walkers against 1-byte tail reads (bsc#1265142).\n- CVE-2026-43456: bonding: fix type confusion in bond_setup_by_slave() (bsc#1264734).\n- CVE-2026-43457: mctp: i2c: fix skb memory leak in receive path (bsc#1265000).\n- CVE-2026-43458: serial: caif: hold tty-\u003elink reference in ldisc_open and ser_release (bsc#1265005).\n- CVE-2026-43465: net/mlx5e: RX, Fix XDP multi-buf frag counting for striding RQ (bsc#1264997).\n- CVE-2026-43466: net/mlx5e: Fix DMA FIFO desync on error CQE SQ recovery (bsc#1264790).\n- CVE-2026-43468: net/mlx5: Fix deadlock between devlink lock and esw-\u003ewq (bsc#1264978).\n- CVE-2026-43469: xprtrdma: Decrement re_receiving on the early exit paths (bsc#1265143).\n- CVE-2026-43470: nfs: return EISDIR on nfs3_proc_create if d_alias is a dir (bsc#1265128).\n- CVE-2026-43471: scsi: ufs: core: Fix possible NULL pointer dereference in ufshcd_add_command_trace() (bsc#1264789).\n- CVE-2026-43491: net: qrtr: ns: Limit the maximum server registration per node (bsc#1265628).\n- CVE-2026-43492: lib/crypto: mpi: Fix integer underflow in mpi_read_raw_from_sgl() (bsc#1265629).\n- CVE-2026-43502: net/rds: handle zerocopy send cleanup before the message is queued (bsc#1266008).\n- CVE-2026-45837: Require (reasonably) normal mappings for MADV_DOFORK (bsc#1266398).\n- CVE-2026-45838: bpf: fix end-of-list detection in cgroup_storage_get_next_key() (bsc#1266396).\n- CVE-2026-45840: openvswitch: cap upcall PID array size and pre-size vport replies (bsc#1266397).\n- CVE-2026-45841: netfilter: nfnetlink_osf: fix divide-by-zero in OSF_WSS_MODULO (bsc#1266390).\n- CVE-2026-45848: apparmor: fix NULL sock in aa_sock_file_perm (bsc#1266734).\n- CVE-2026-45857: scsi: csiostor: Fix dereference of null pointer rn (bsc#1266458).\n- CVE-2026-45858: ext4: don't zero the entire extent if EXT4_EXT_DATA_PARTIAL_VALID1 (bsc#1266773).\n- CVE-2026-45861: gfs2: Fix slab-use-after-free in qd_put (bsc#1266754).\n- CVE-2026-45862: iommu/vt-d: Flush cache for PASID table before using it (bsc#1266705).\n- CVE-2026-45870: SUNRPC: auth_gss: fix memory leaks in XDR decoding error paths (bsc#1266704).\n- CVE-2026-45884: apparmor: avoid per-cpu hold underflow in aa_get_buffer (bsc#1266718).\n- CVE-2026-45888: md/raid1: fix memory leak in raid1_run() (bsc#1266761).\n- CVE-2026-45891: net: hns3: fix double free issue for tx spare buffer (bsc#1266717).\n- CVE-2026-45894: iommu/vt-d: Clear Present bit before tearing down PASID entry (bsc#1266895).\n- CVE-2026-45899: ext4: drop extent cache when splitting extent fails (bsc#1266883).\n- CVE-2026-45901: netfilter: nf_tables: revert commit_mutex usage in reset path (bsc#1266892).\n- CVE-2026-45912: ext4: don't cache extent during splitting extent (bsc#1266899).\n- CVE-2026-45920: ext4: fix dirtyclusters double decrement on fs shutdown (bsc#1266893).\n- CVE-2026-45922: RDMA/mlx5: Fix memory leak in GET_DATA_DIRECT_SYSFS_PATH handler (bsc#1266805).\n- CVE-2026-45933: bpf: Preserve id of register in sync_linked_regs() (bsc#1266693).\n- CVE-2026-45940: net: stmmac: fix oops when split header is enabled (bsc#1266916).\n- CVE-2026-45948: ext4: fix memory leak in ext4_ext_shift_extents() (bsc#1266929).\n- CVE-2026-45961: gfs2: fix memory leaks in gfs2_fill_super error path (bsc#1266933).\n- CVE-2026-45964: SUNRPC: fix gss_auth kref leak in gss_alloc_msg error path (bsc#1266698).\n- CVE-2026-45965: apparmor: fix invalid deref of rawdata when export_binary is unset (bsc#1267208).\n- CVE-2026-45974: btrfs: fix invalid leaf access in btrfs_quota_enable() if ref key not found (bsc#1266922).\n- CVE-2026-45983: nfsd: never defer requests during idmap lookup (bsc#1266697).\n- CVE-2026-45985: ext4: don't set EXT4_GET_BLOCKS_CONVERT when splitting before submitting I/O (bsc#1266700).\n- CVE-2026-45997: scsi: sd: fix missing put_disk() when device_add(\u0026disk_dev) fails (bsc#1266740).\n- CVE-2026-45999: erofs: fix unsigned underflow in z_erofs_lz4_handle_overlap() (bsc#1266750).\n- CVE-2026-46005: xfs: fix a resource leak in xfs_alloc_buftarg() (bsc#1267431).\n- CVE-2026-46024: libceph: Prevent potential null-ptr-deref in ceph_handle_auth_reply() (bsc#1267218).\n- CVE-2026-46037: ipv4: icmp: validate reply type before using icmp_pointers (bsc#1267361).\n- CVE-2026-46046: ext4: fix missing brelse() in ext4_xattr_inode_dec_ref_all() (bsc#1266726).\n- CVE-2026-46050: md/raid10: fix deadlock with check operation and nowait requests (bsc#1266686).\n- CVE-2026-46051: md/raid5: fix soft lockup in retry_aligned_read() (bsc#1267360).\n- CVE-2026-46053: net: rds: fix MR cleanup on copy error (bsc#1267427).\n- CVE-2026-46063: x86/shstk: Prevent deadlock during shstk sigreturn (bsc#1267228).\n- CVE-2026-46065: fbdev: defio: Disconnect deferred I/O from the lifetime of struct (bsc#1267458).\n- CVE-2026-46069: wifi: mwifiex: fix use-after-free in mwifiex_adapter_cleanup() (bsc#1267437).\n- CVE-2026-46071: KVM: nSVM: Avoid clearing VMCB_LBR in vmcb12 (bsc#1267591).\n- CVE-2026-46076: KVM: nSVM: Raise #UD if unhandled VMMCALL isn't intercepted by L1 (bsc#1267365).\n- CVE-2026-46078: erofs: fix the out-of-bounds nameoff handling for trailing dirents (bsc#1267505).\n- CVE-2026-46079: rbd: fix null-ptr-deref when device_add_disk() fails (bsc#1266452).\n- CVE-2026-46091: media: rc: igorplugusb: heed coherency rules (bsc#1267238).\n- CVE-2026-46093: mm/vmalloc: take vmap_purge_lock in shrinker (bsc#1267548).\n- CVE-2026-46099: net: ipv6: fix NOREF dst use in seg6 and rpl lwtunnels (bsc#1266722).\n- CVE-2026-46101: netfilter: reject zero shift in nft_bitwise (bsc#1266878).\n- CVE-2026-46111: Bluetooth: hci_conn: fix potential UAF in create_big_sync (bsc#1267626).\n- CVE-2026-46112: RDMA/hns: Fix unlocked call to hns_roce_qp_remove() (bsc#1267582).\n- CVE-2026-46116: xfrm: defensively unhash xfrm_state lists in __xfrm_state_delete (bsc#1267369).\n- CVE-2026-46119: libceph: Fix slab-out-of-bounds access in auth message processing (bsc#1267628).\n- CVE-2026-46120: ip6_gre: Use cached t-\u003enet in ip6erspan_changelink() (bsc#1267640).\n- CVE-2026-46124: isofs: validate block number from NFS file handle in isofs_export_iget (bsc#1266847).\n- CVE-2026-46150: fanotify: fix false positive on permission events (bsc#1267387).\n- CVE-2026-46160: btrfs: fix missing last_unlink_trans update when removing a directory (bsc#1267624).\n- CVE-2026-46161: md/raid10: fix divide-by-zero in setup_geo() with zero far_copies (bsc#1266838).\n- CVE-2026-46162: ice: fix double free in ice_sf_eth_activate() error path (bsc#1266840).\n- CVE-2026-46172: ipv6: xfrm6: release dst on error in xfrm6_rcv_encap() (bsc#1266903).\n- CVE-2026-46173: exit: prevent preemption of oopsing TASK_DEAD task (bsc#1267722).\n- CVE-2026-46178: RDMA/mlx4: Fix resource leak on error in mlx4_ib_create_srq() (bsc#1267493).\n- CVE-2026-46185: smb/client: fix out-of-bounds read in symlink_data() (bsc#1266830).\n- CVE-2026-46214: vsock/virtio: fix accept queue count leak on transport mismatch (bsc#1267717).\n- CVE-2026-46227: sctp: revalidate list cursor after sctp_sendmsg_to_asoc() in SCTP_SENDALL (bsc#1267697).\n- CVE-2026-46242: eventpoll: Fix integer overflow in ep_loop_check_proc() (bsc#1267618).\n- CVE-2026-46244: netfilter: nft_inner: Fix IPv6 inner_thoff desync (bsc#1267654).\n- CVE-2026-46253: pstore/ram: fix buffer overflow in persistent_ram_save_old() (bsc#1267635).\n- CVE-2026-46254: AppArmor: Allow apparmor to handle unaligned dfa tables (bsc#1267637).\n- CVE-2026-46259: procfs: fix missing RCU protection when reading real_parent in do_task_stat() (bsc#1267685).\n- CVE-2026-46266: inet: RAW sockets using IPPROTO_RAW MUST drop incoming ICMP (bsc#1267684).\n- CVE-2026-46289: lib/scatterlist: fix length calculations in extract_kvec_to_sg (bsc#1267966).\n- CVE-2026-46291: printk: add print_hex_dump_devel() (bsc#1267937).\n- CVE-2026-46314: drm/v3d: Reject empty multisync extension to prevent infinite loop (bsc#1267992).\n- CVE-2026-46319: net/sched: act_ct: Only release RCU read lock after ct_ft (bsc#1268022).\n- CVE-2026-46320: tap: free page on error paths in tap_get_user_xdp() (bsc#1267993).\n- CVE-2026-46322: tun: free page on build_skb failure in tun_xdp_one() (bsc#1267994).\n- CVE-2026-46328: apparmor: fix rlimit for posix cpu timers (bsc#1268037).\n- CVE-2026-52908: RDMA: During rereg_mr ensure that REREG_ACCESS is compatible (bsc#1268661).\n- CVE-2026-52909: ip6_vti: set netns_immutable on the fallback device (bsc#1268660).\n- CVE-2026-52919: batman-adv: fix tp_meter counter underflow during shutdown (bsc#1269031).\n- CVE-2026-52923: ipc: limit next_id allocation to the valid ID range (bsc#1269033).\n- CVE-2026-52924: sctp: purge outqueue on stale COOKIE-ECHO handling (bsc#1269036).\n- CVE-2026-52933: io_uring/poll: fix signed comparison in io_poll_get_ownership() (bsc#1268989).\n- CVE-2026-52943: net: skbuff: fix missing zerocopy reference in pskb_carve helpers (bsc#1269022).\n- CVE-2026-52954: libceph: handle rbtree insertion error in decode_choose_args() (bsc#1269137).\n- CVE-2026-52955: libceph: Fix potential out-of-bounds access in crush_decode() (bsc#1269159).\n- CVE-2026-52957: libceph: Fix potential null-ptr-deref in decode_choose_args() (bsc#1269103).\n- CVE-2026-52962: ceph: fix a buffer leak in __ceph_setxattr() (bsc#1269135).\n- CVE-2026-52975: bonding: 3ad: implement proper RCU rules for port-\u003eaggregator (bsc#1269234).\n- CVE-2026-52980: sched/fair: Clear rel_deadline when initializing forked entities (bsc#1269252).\n- CVE-2026-52993: tipc: fix double-free in tipc_buf_append() (bsc#1269193).\n- CVE-2026-53015: erofs: unify lcn as u64 for 32-bit platforms (bsc#1269087).\n- CVE-2026-53021: scsi: target: core: Fix integer overflow in UNMAP bounds check (bsc#1269151).\n- CVE-2026-53036: bpf, arm64: Reject out-of-range B.cond targets (bsc#1269389).\n- CVE-2026-53039: ocfs2: validate group add input before caching (bsc#1269392).\n- CVE-2026-53040: ocfs2: validate bg_bits during freefrag scan (bsc#1269397).\n- CVE-2026-53041: ocfs2: fix listxattr handling when the buffer is full (bsc#1269398).\n- CVE-2026-53049: gfs2: add some missing log locking (bsc#1269646).\n- CVE-2026-53050: quota: Fix race of dquot_scan_active() with quota deactivation (bsc#1269188).\n- CVE-2026-53053: iommu/amd: Fix clone_alias() to use the original device's devid (bsc#1269310).\n- CVE-2026-53060: dm cache metadata: fix memory leak on metadata abort retry (bsc#1269164).\n- CVE-2026-53075: ppp: require CAP_NET_ADMIN in target netns for unattached ioctls (bsc#1269690).\n- CVE-2026-53078: bpf: Fix same-register dst/src OOB read and pointer leak in sock_ops (bsc#1269700).\n- CVE-2026-53081: bpf: Enforce regsafe base id consistency for BPF_ADD_CONST scalars (bsc#1269708).\n- CVE-2026-53086: net: bcmgenet: move DESC_INDEX flow to ring 0 (bsc#1269537).\n- CVE-2026-53090: bpf: Fix ld_{abs,ind} failure path analysis in subprogs (bsc#1269532).\n- CVE-2026-53103: wifi: mt76: mt7925: fix potential deadlock in mt7925_roc_abort_sync (bsc#1269416).\n- CVE-2026-53122: btrfs: fix deadlock between reflink and transaction commit when using flushoncommit (bsc#1269418).\n- CVE-2026-53133: RDMA/umem: Fix truncation for block sizes \u003e= 4G (bsc#1269821).\n- CVE-2026-53139: drm/v3d: Skip CSD when it has zeroed workgroups (bsc#1269262).\n- CVE-2026-53156: nvmem: core: fix use-after-free bugs in error paths (bsc#1269288).\n- CVE-2026-53167: fuse: limit FUSE_NOTIFY_RETRIEVE to uptodate folios (bsc#1269768).\n- CVE-2026-53168: fuse: reject fuse_notify() pagecache ops on directories (bsc#1269645).\n- CVE-2026-53176: IB/isert: Reject login PDUs shorter than ISER_HEADERS_LEN (bsc#1269710).\n- CVE-2026-53178: staging: rtl8723bs: rtw_mlme: add bounds checks before ie_length subtraction (bsc#1269795).\n- CVE-2026-53215: net: mvpp2: refill RX buffers before XDP or skb use (bsc#1269680).\n- CVE-2026-53216: net: mvpp2: limit XDP frame size to the RX buffer (bsc#1269587).\n- CVE-2026-53217: net: mvpp2: sync RX data at the hardware packet offset (bsc#1269989).\n- CVE-2026-53229: net/mlx5e: xsk: Fix DMA and xdp_frame leak on XDP_TX xmit failure (bsc#1269691).\n- CVE-2026-53249: ipv4: restrict IPOPT_SSRR and IPOPT_LSRR options (bsc#1269992).\n- CVE-2026-53258: wifi: fix leak if split 6 GHz scanning fails (bsc#1269230).\n- CVE-2026-53262: l2tp: pppol2tp: hold reference to session in pppol2tp_ioctl() (bsc#1270000).\n- CVE-2026-53263: 6lowpan: fix off-by-one in multicast context address compression (bsc#1269647).\n- CVE-2026-53266: netfilter: bridge: make ebt_snat ARP rewrite writable (bsc#1269136).\n- CVE-2026-53272: erofs: fix use-after-free on sbi-\u003esync_decompress (bsc#1269809).\n- CVE-2026-53274: net/smc: fix sleep-inside-lock in __smc_setsockopt() causing local DoS (bsc#1269651).\n- CVE-2026-53281: iommu/vt-d: Avoid NULL pointer dereference or refcount corruption (bsc#1269519).\n- CVE-2026-53285: drm/amd/display: Wrap DCN32 phantom-plane allocation in DC_RUN_WITH_PREEMPTION_ENABLED (bsc#1269527).\n- CVE-2026-53286: idpf: fix double free and use-after-free in aux device error paths (bsc#1269531).\n- CVE-2026-53287: audit: fix incorrect inheritable capability in CAPSET records (bsc#1269506).\n- CVE-2026-53306: tty: hvc_iucv: fix off-by-one in number of supported devices (bsc#1269814).\n\nThe following non security issues were fixed:\n\n- accel/ivpu: Fix signed integer truncation in IPC receive (git-fixes).\n- ACPI: CPPC: Suppress UBSAN warning caused by field misuse (git-fixes).\n- ACPI: IPMI: Fix inverted interface check in ipmi_bmc_gone() (git-fixes).\n- ACPI: IPMI: Fix message kref handling on dead device (git-fixes).\n- ACPI: NFIT: core: Fix possible NULL pointer dereference (git-fixes).\n- ACPI: resource: Amend kernel-doc style (git-fixes).\n- agp/amd64: Fix broken error propagation in agp_amd64_probe() (git-fixes).\n- ALSA: aloop: Drop superfluous break (git-fixes).\n- ALSA: caiaq: fix out-of-bounds read in the Traktor Kontrol S4 input parser (git-fixes).\n- ALSA: cmipci: check snd_ctl_new1() return value (git-fixes).\n- ALSA: core: Fix unintuitive behavior of snd_power_ref_and_wait() (git-fixes).\n- ALSA: es1938: check snd_ctl_new1() return value (git-fixes).\n- ALSA: firewire: isight: bound the sample count to the packet payload (git-fixes).\n- ALSA: gus: check snd_ctl_new1() return value (git-fixes).\n- ALSA: hda/cs35l41: Fix firmware load work teardown (git-fixes).\n- ALSA: ice1712: check snd_ctl_new1() return value (git-fixes).\n- ALSA: scarlett2: Allow flash writes ending at segment boundary (git-fixes).\n- ALSA: scarlett2: Return ENOSPC for out-of-bounds flash writes (stable-fixes).\n- ALSA: seq: Clear variable event pointer on read (git-fixes).\n- ALSA: seq: Fix kernel heap address leak in bounce_error_event() (git-fixes).\n- ALSA: seq: Fix partial userptr event expansion (git-fixes).\n- ALSA: seq: Fix uninitialised heap leak in snd_seq_event_dup() (git-fixes).\n- ALSA: seq: midi: Serialize output teardown with event_input (git-fixes).\n- ALSA: timer: Fix UAF at snd_timer_user_params() (stable-fixes).\n- ALSA: timer: Forcibly close timer instances at closing (git-fixes).\n- ALSA: usb-audio: avoid kobject path lookup in DualSense match (git-fixes).\n- ALSA: usb-audio: Kill MIDI 2.0 URBs before freeing endpoints (git-fixes).\n- ALSA: usb-audio: Propagate errors in scarlett_ctl_enum_put() (git-fixes).\n- ALSA: usb-audio: Propagate US-16x08 write errors in route/mix EQ-switch put callbacks (git-fixes).\n- ALSA: usb-audio: Roll back quirk control caches on write errors (git-fixes).\n- ALSA: usb-audio: Update Babyface Pro control caches only after successful writes (git-fixes).\n- ALSA: usb-audio: Update US-16x08 EQ/comp shadow state after successful writes (git-fixes).\n- ALSA: virtio: Add missing 384 kHz PCM rate mapping (git-fixes).\n- ALSA: virtio: Validate control metadata from the device (git-fixes).\n- ALSA: ymfpci: check snd_ctl_new1() return value (git-fixes).\n- arm64: scripts/sorttable: Implement sorting mcount_loc at boot for arm64 (bsc#1267600).\n- ASoC: adau1372: Clear PLL_EN on failed PLL lock without reset GPIO (git-fixes).\n- ASoC: amd: acp-sdw-sof: Bound DAI link iteration (git-fixes).\n- ASoC: codecs: aw88261: fix incorrect masks for boost regs (git-fixes).\n- ASoC: codecs: hdac_hdmi: Validate written enum value (git-fixes).\n- ASoC: cs35l56: Cleanup if component_probe fails (git-fixes).\n- ASoC: cs35l56: Don't leave parent IRQ disabled if system_suspend fails (git-fixes).\n- ASoC: cs35l56: Fix missing calls to wm_adsp2_remove() (git-fixes).\n- ASoC: cs35l56: Fix possible uninitialized value in cs35l56_spi_system_reset() (git-fixes).\n- ASoC: fsl: fsl_audmix: Validate written enum values (git-fixes).\n- ASoC: fsl_asrc_dma: fix eDMA maxburst misalignment with channel count (git-fixes).\n- ASoC: mediatek: mt8183: Release reserved memory on cleanup (git-fixes).\n- ASoC: mediatek: mt8192: Release reserved memory on cleanup (git-fixes).\n- ASoC: meson: aiu: Validate written enum values (git-fixes).\n- ASoC: qcom: q6apm: fix NULL pointer dereference in graph_callback (git-fixes).\n- ASoC: SOF: ipc3-control: Fix heap overflow in bytes_ext put/get (git-fixes).\n- ASoC: SOF: ipc3-control: Fix TOCTOU in bytes_put and bytes_get (git-fixes).\n- ASoC: SOF: ipc3-control: Use overflow checks in control_update size calc (git-fixes).\n- ASoC: SOF: ipc3-control: Validate size in snd_sof_update_control (git-fixes).\n- ASoC: SOF: ipc4-control: Fix TOCTOU in sof_ipc4_bytes_put (git-fixes).\n- ASoC: SOF: topology: validate vendor array size before parsing (git-fixes).\n- ASoC: tegra: tegra210_ahub: Validate written enum value (git-fixes).\n- ASoC: tlv320aic3x: restrict CLKDIV bypass Q values in dual-rate mode (git-fixes).\n- ASoC: topology: Check PCM and DAI name strings before use (git-fixes).\n- ASoC: wm_adsp: Fix NULL dereference when removing firmware controls (git-fixes).\n- Bluetooth: 6lowpan: hold L2CAP conn across debugfs control (git-fixes).\n- Bluetooth: bnep: pin L2CAP connection during netdev registration (git-fixes).\n- Bluetooth: bpa10x: avoid OOB read of revision string in bpa10x_setup() (git-fixes).\n- Bluetooth: btmtk: fix URB leak in alloc_mtk_intr_urb error path (git-fixes).\n- Bluetooth: btmtksdio: fix infinite loop in btmtksdio_txrx_work() (git-fixes).\n- Bluetooth: btnxpuart: Fix out-of-bounds firmware read in nxp_recv_fw_req_v3() (git-fixes).\n- Bluetooth: btusb: fix use-after-free on marvell probe failure (git-fixes).\n- Bluetooth: btusb: fix use-after-free on registration failure (git-fixes).\n- Bluetooth: btusb: fix wakeup irq devres lifetime (git-fixes).\n- Bluetooth: btusb: fix wakeup source leak on probe failure (git-fixes).\n- Bluetooth: eir: Fix stack OOB write when prepending the Flags AD (git-fixes).\n- Bluetooth: fix UAF in bt_accept_dequeue() (git-fixes).\n- Bluetooth: hci: validate codec capability element length (git-fixes).\n- Bluetooth: hci_core: Fix UAF in hci_unregister_dev() (git-fixes).\n- Bluetooth: hci_qca: fix NULL pointer dereference in qca_dmp_hdr() for non-serdev device (git-fixes).\n- Bluetooth: hci_uart: clear HCI_UART_SENDING when write_work is canceled (git-fixes).\n- Bluetooth: ISO: avoid NULL deref of conn in iso_conn_big_sync() (git-fixes).\n- Bluetooth: ISO: exclude RFU bits from ISO_SDU_Length (git-fixes).\n- Bluetooth: ISO: Fix data-race on iso_pi fields in hci_get_route calls (git-fixes).\n- Bluetooth: ISO: fix malformed ISO_END/CONT handling (git-fixes).\n- Bluetooth: ISO: Fix not using bc_sid as advertisement SID (stable-fixes).\n- Bluetooth: L2CAP: reject BR/EDR signaling packets over MTUsig (stable-fixes).\n- Bluetooth: L2CAP: validate option length before reading conf opt value (git-fixes).\n- Bluetooth: MGMT: Fix adv monitor add failure cleanup (git-fixes).\n- Bluetooth: MGMT: Fix UAF of hci_conn_params in add_device_complete (git-fixes).\n- Bluetooth: sco: Fix a race condition in sco_sock_timeout() (git-fixes).\n- Bluetooth: vhci: validate devcoredump state before side effects (git-fixes).\n- bnxt_en: Fix NULL pointer dereference (bsc#1268307).\n- bpf: Free reuseport cBPF prog after RCU grace period (git-fixes).\n- bus: mhi: ep: Add missing state_lock protection for mhi_state access (git-fixes).\n- bus: mhi: ep: Fix potential deadlock in mhi_ep_reset_worker() (git-fixes).\n- bus: mhi: ep: Protect mhi_ep_handle_syserr() in the error path (git-fixes).\n- char: tlclk: fix use-after-free in tlclk_cleanup() (git-fixes).\n- crypto/hmac: reject keys shorter than 128 bits in fips mode (bsc#1266284 jsc#PED-15986).\n- crypto/testmgr: disallow ffdhe2048 in fips mode (bsc#1266284 jsc#PED-15986).\n- crypto/testmgr: disallow plain ecb() usage in fips mode (bsc#1266284 jsc#PED-15986).\n- crypto/testmgr: disallow sha224 + sha3-224 in fips mode (bsc#1266284 jsc#PED-15986).\n- crypto: af_alg - Cap AEAD AD length to 0x80000000 (git-fixes).\n- crypto: amlogic - avoid double cleanup in meson_crypto_probe() (git-fixes).\n- crypto: asymmetric_keys - fix OOB read in pefile_digest_pe_contents (git-fixes).\n- crypto: atmel-sha204a - fix blocking and non-blocking rng logic (git-fixes).\n- crypto: cavium/cpt - fix DMA cleanup using wrong loop index (git-fixes).\n- crypto: ccp - Do not initialize SNP for ioctl(SNP_COMMIT) (git-fixes).\n- crypto: ccp - Do not initialize SNP for ioctl(SNP_VLEK_LOAD) (git-fixes).\n- crypto: ccp - Do not initialize SNP for SEV ioctls (git-fixes).\n- crypto: ccp - Fix snp_filter_reserved_mem_regions() off-by-one (git-fixes).\n- crypto: ccp - Treat zero-length cert chain as query for blob lengths (git-fixes).\n- crypto: drbg - Fix drbg_max_addtl() on 64-bit kernels (git-fixes).\n- crypto: drbg - Fix returning success on failure in CTR_DRBG (git-fixes).\n- crypto: drbg - Fix the fips_enabled priority boost (git-fixes).\n- crypto: ecc - Fix carry overflow in vli multiplication (git-fixes).\n- crypto: ecrdsa - fix unknown OID check in ecrdsa_param_curve (git-fixes).\n- crypto: hisilicon/qm - disable error report before flr (git-fixes).\n- crypto: marvell/octeontx - fix DMA cleanup using wrong loop index (git-fixes).\n- crypto: pcrypt - restore callback for non-parallel fallback (git-fixes).\n- crypto: qat - protect service table iterations with service_lock (git-fixes).\n- crypto: qat - validate RSA CRT component lengths (git-fixes).\n- crypto: rng - Free default RNG on module exit (git-fixes).\n- crypto: tegra - Fix dma_free_coherent size error (git-fixes).\n- crypto: tegra - fix refcount leak in tegra_se_host1x_submit() (git-fixes).\n- crypto: tegra - Return ENOMEM when input buffer allocation fails for ccm (git-fixes).\n- dm init: ensure device probing has finished in dm-mod.waitfor= (git-fixes).\n- dmaengine: dma-axi-dmac: Properly free struct axi_dmac_desc (git-fixes).\n- dmaengine: dma-axi-dmac: use DMA pool to manange DMA descriptor (git-fixes).\n- dmaengine: dw-edma: Add spinlock to protect DONE_INT_MASK and ABORT_INT_MASK (git-fixes).\n- dmaengine: Fix possible use after free (git-fixes).\n- dmaengine: imx-sdma: Refine spba bus searching in probe (git-fixes).\n- dmaengine: qcom: gpi: set DMA_PRIVATE capability (git-fixes).\n- dmaengine: tegra: Fix burst size calculation (git-fixes).\n- driver core: reject devices with unregistered buses (git-fixes).\n- driver core: use READ_ONCE() for dev-\u003edriver in dev_has_sync_state() (git-fixes).\n- Drivers: hv: vmbus: Improve the logic of reserving fb_mmio on Gen2 VMs (git-fixes).\n- drm/amd/display: add missing CSC entries for BT.2020 for DCE IPs (stable-fixes).\n- drm/amd/display: Add missing kdoc for ALLM parameters (git-fixes).\n- drm/amd/display: Clamp VBIOS HDMI retimer register count to array size (stable-fixes).\n- drm/amd/pm: fix smu13 power limit default/cap calculation (stable-fixes).\n- drm/amd/pm: mark metrics.energy_accumulator is invalid for smu 14.0.2 (stable-fixes).\n- drm/amd/pm: remove trailing semicolon from AMDGPU_PM_POLICY_ATTR macro (git-fixes).\n- drm/amd/pm: smu_v14_0_0: use SoftMin for gfxclk in set_soft_freq_limited_range (stable-fixes).\n- drm/amdgpu: Fix amdgpu_bo_move() when old_mem and new_mem are both GTT (git-fixes).\n- drm/amdgpu: fix integer overflow in amdgpu_gem_align_pitch() (git-fixes).\n- drm/amdgpu: initialize irq.lock spinlock earlier (git-fixes).\n- drm/amdgpu: restart the CS if some parts of the VM are still invalidated (stable-fixes).\n- drm/amdgpu: set sub_block_index for mca ras sub-blocks (git-fixes).\n- drm/amdgpu: skip already suspended IP blocks in ip_suspend_phase2 (git-fixes).\n- drm/amdgpu: validate CP_GFX_SHADOW chunk size in CS pass1 (git-fixes).\n- drm/amdkfd: always resume_all after suspend_all (git-fixes).\n- drm/amdkfd: Avoid double-unpin of DOORBELL/MMIO BOs on free (git-fixes).\n- drm/amdkfd: Check for pdd drm file first in CRIU restore path (stable-fixes).\n- drm/amdkfd: fix list_del corruption in kfd_criu_resume_svm (git-fixes).\n- drm/amdkfd: fix NULL pointer bug in svm_range_set_attr (stable-fixes).\n- drm/amdkfd: Use exclusive bounds for SVM split alignment checks (git-fixes).\n- drm/amdkfd: Validate CRIU-restored IDs before idr_alloc (git-fixes).\n- drm/bridge: cdns-dsi: Replace deprecated UNIVERSAL_DEV_PM_OPS() (git-fixes).\n- drm/dp/mst: fix buffer overflows in sideband chunk accumulation (git-fixes).\n- drm/dp/mst: fix OOB reads in remote DPCD/I2C sideband reply parsers (git-fixes).\n- drm/dp/mst: fix OOB reads on 2-byte fields in sideband reply parsers (git-fixes).\n- drm/dp: Add eDP 1.5 bit definition (stable-fixes).\n- drm/edid: fix OOB read in drm_parse_tiled_block() (git-fixes).\n- drm/gpuvm: Do not prepare NULL objects (git-fixes).\n- drm/hisilicon/hibmc: move display contrl config to hibmc_probe() (git-fixes).\n- drm/hisilicon/hibmc: use clock to look up the PLL value (git-fixes).\n- drm/hyperv: use VMBUS_RING_SIZE() (git-fixes).\n- drm/i915/gem: Add missing nospec on parallel submit slot (git-fixes).\n- drm/i915/gem: Fix phys BO pread/pwrite with offset (git-fixes).\n- drm/i915/psr: Add defininitions for INTEL_WA_REGISTER_CAPS DPCD register (stable-fixes).\n- drm/i915: clear CRTC color blob pointers after dropping refs (git-fixes).\n- drm/imagination: Count paired job fence as dependency in prepare_job() (git-fixes).\n- drm/imagination: Fit paired fragment job in the correct CCCB (git-fixes).\n- drm/msm/dp: fix HPD state status bit shift value (git-fixes).\n- drm/msm/dp: Fix the ISR_* enum values (git-fixes).\n- drm/nouveau/acr: fix missing nvkm_done() in error path of nvkm_acr_oneinit() (git-fixes).\n- drm/nouveau/bios: specify correct display fuse register for Ampere and Ada (git-fixes).\n- drm/nouveau: fix reversed error cleanup order in ucopy functions (git-fixes).\n- drm/panthor: Fix kernel-doc warning in panthor_sched.c (git-fixes).\n- drm/radeon: fix integer overflow in radeon_align_pitch() (git-fixes).\n- drm/radeon: fix memory leak in radeon_ring_restore() on lock failure (git-fixes).\n- drm/rockchip: cdn-dp: add missing check in cdn_dp_config_video() (git-fixes).\n- drm/rockchip: Test for imported buffers with drm_gem_is_imported() (git-fixes).\n- drm/syncobj: Fix memory leak in drm_syncobj_find_fence() (git-fixes).\n- drm/tegra: dc: Fix device node reference leak in tegra_dc_has_output() (git-fixes).\n- drm/tegra: Fix iommu_map_sgtable() return value check (git-fixes).\n- drm/tidss: Drop extra drm_mode_config_reset() call (git-fixes).\n- drm/tidss: Fix missing drm_bridge_add() call (git-fixes).\n- drm/vc4: fix krealloc() memory leak (git-fixes).\n- drm/virtio: fix dma_fence refcount leak on error in virtio_gpu_dma_fence_wait() (git-fixes).\n- drm/virtio: Fix driver removal with disabled KMS (git-fixes).\n- drm/xe: fix refcount leak in xe_range_fence_insert() (git-fixes).\n- drm: renesas: rzg2l_mipi_dsi: Increase reset deassertion delay (git-fixes).\n- fbdev: Fix fb_new_modelist to prevent null-ptr-deref in fb_videomode_to_var (stable-fixes).\n- fbdev: fix use-after-free in store_modes() (stable-fixes).\n- fbdev: modedb: fix a possible UAF in fb_find_mode() (stable-fixes).\n- fbdev: modedb: Fix misaligned fields in the 1920x1080-60 mode (git-fixes).\n- firmware: arm_scmi: Fix OOB in scmi_power_name_get() (git-fixes).\n- firmware: arm_scmi: Read sensor config as 32-bit value (git-fixes).\n- firmware_loader: fix device reference leak in firmware_upload_register() (git-fixes).\n- firmware_loader: Fix recursive lock in device_cache_fw_images() (git-fixes).\n- fpga: dfl: add bounds check in dfh_get_param_size() (git-fixes).\n- fpga: microchip-spi: fix zero header_size OOB read in mpf_ops_parse_header() (git-fixes).\n- fpga: region: fix use-after-free in child_regions_with_firmware() (git-fixes).\n- ftrace: Check against is_kernel_text() instead of kaslr_offset() (bsc#1267600).\n- ftrace: Do not over-allocate ftrace memory (bsc#1267600).\n- ftrace: Have ftrace pages output reflect freed pages (bsc#1267600).\n- ftrace: Test mcount_loc addr before calling ftrace_call_addr() (bsc#1267600).\n- ftrace: Update the mcount_loc check of skipped entries (bsc#1267600).\n- gpio: mvebu: fix NULL pointer dereference in suspend/resume (git-fixes).\n- gpio: mxc: fix irq_high handling (git-fixes).\n- gpio: rockchip: convert bank-\u003eclk to devm_clk_get_enabled() (git-fixes).\n- gpio: virtuser: Fix uninitialized data bug in gpio_virtuser_direction_do_write() (git-fixes).\n- gpio: zynq: fix runtime PM leak on remove (git-fixes).\n- gpiolib: Extract gpiochip_choose_fwnode() for wider use (stable-fixes).\n- gpiolib: Remove redundant assignment of return variable (stable-fixes).\n- gpu: host1x: Allow entries in BO caches to be freed (git-fixes).\n- gpu: host1x: Fix device reference leak in host1x_device_parse_dt() error path (git-fixes).\n- gpu: host1x: Fix iommu_map_sgtable() return value check (git-fixes).\n- HID: core: Add printk_ratelimited variants to hid_warn() etc (stable-fixes).\n- HID: hid-goodix-spi: validate report size to prevent stack buffer overflow (git-fixes).\n- HID: letsketch: fix UAF on inrange_timer at driver unbind (git-fixes).\n- HID: lg-g15: cancel pending work on remove to fix a use-after-free (git-fixes).\n- HID: logitech-hidpp: remove excess kernel-doc member in hidpp_scroll_counter (git-fixes).\n- HID: picolcd: prevent NULL pointer dereference in picolcd_send_and_wait() (git-fixes).\n- HID: quirks: Add ALWAYS_POLL quirk for SIGMACHIP USB mouse (stable-fixes).\n- HID: rate-limit hid_warn to prevent log flooding (stable-fixes).\n- HID: remove duplicate hid_warn_ratelimited definition (git-fixes).\n- HID: wacom: Fix OOB write in wacom_hid_set_device_mode() (git-fixes).\n- HID: wacom: stop hardware after post-start probe failures (git-fixes).\n- HID: wiimote: Fix table layout and whitespace errors (git-fixes).\n- hv: utils: handle and propagate errors in kvp_register (git-fixes).\n- hv: utils: replace deprecated strcpy with strscpy in kvp_register (git-fixes).\n- hv_balloon: Simplify data output in hv_balloon_debug_show() (git-fixes).\n- hv_netvsc: use kmap_local_page in netvsc_copy_to_send_buf (git-fixes).\n- hwmon: (aspeed-g6-pwm-tach) Guard fan RPM calculation against divide-by-zero (git-fixes).\n- hwmon: (asus_atk0110) Check package count before accessing element (git-fixes).\n- hwmon: (it87) Clamp negative values to zero in set_fan() (git-fixes).\n- hwmon: (ltc2992) add missing 'select REGMAP_I2C' to Kconfig (git-fixes).\n- hwmon: (max1619) add missing 'select REGMAP' to Kconfig (git-fixes).\n- hwmon: (max6697) add missing 'select REGMAP_I2C' to Kconfig (git-fixes).\n- hwmon: (occ) unregister sysfs devices outside occ lock (git-fixes).\n- hwmon: adm1275: Prevent reading uninitialized stack (git-fixes).\n- hwrng: jh7110 - fix refcount leak in starfive_trng_read() (git-fixes).\n- hwrng: virtio: clamp device-reported used.len at copy_data() (git-fixes).\n- hyperv: Clean up and fix the guest ID comment in hvgdk.h (git-fixes).\n- i2c: core: disable runtime PM on adapter registration failure (git-fixes).\n- i2c: core: fix adapter debugfs creation (git-fixes).\n- i2c: core: fix adapter deregistration race (git-fixes).\n- i2c: core: fix adapter probe deferral loop (git-fixes).\n- i2c: core: fix adapter registration race (git-fixes).\n- i2c: core: fix hang on adapter registration failure (git-fixes).\n- i2c: core: fix irq domain leak on adapter registration failure (git-fixes).\n- i2c: core: fix NULL-deref on adapter registration failure (git-fixes).\n- i2c: dev: prevent integer overflow in I2C_TIMEOUT ioctl (stable-fixes).\n- i2c: imx-lpi2c: mark I2C adapter when hardware is powered down (git-fixes).\n- i2c: mpc: Fix timeout calculations (git-fixes).\n- i2c: qcom-cci: Fix NULL pointer dereference in cci_remove() (git-fixes).\n- i2c: riic: fix refcount leak in riic_i2c_resume_noirq() (git-fixes).\n- i2c: stm32f7: fix timing computation ignoring i2c-analog-filter (git-fixes).\n- i2c: stm32f7: truncate clock period instead of rounding it (git-fixes).\n- i2c: tegra: Fix NOIRQ suspend/resume (git-fixes).\n- i3c: master: Prevent reuse of dynamic address on device add failure (git-fixes).\n- i3c: master: Serialize i3c_set_hotjoin() with the maintenance lock (git-fixes).\n- ice: ptp: don't WARN when controlling PF is unavailable (bsc#1267251).\n- iio: accel: mma8452: handle I2C read error(s) in mma8452_read() (git-fixes).\n- iio: adc: ti-ads1298: add bounds check to pga_settings index (stable-fixes).\n- iio: adc: xilinx-ams: fix out-of-bounds channel lookup in event handling (git-fixes).\n- iio: backend: fix uninitialized data in debugfs (git-fixes).\n- iio: chemical: scd30: Cleanup initializations and fix sign-extension bug (git-fixes).\n- iio: chemical: scd30: fix division by zero in write_raw (git-fixes).\n- iio: chemical: scd30: Use guard(mutex) to allow early returns (stable-fixes).\n- iio: gyro: bmg160: bail out when bandwidth/filter is not in table (git-fixes).\n- iio: gyro: bmg160: wait full startup time after mode change at probe (git-fixes).\n- iio: light: opt3001: fix missing state reset on timeout (git-fixes).\n- iio: light: si1133: prevent race condition on timeout (git-fixes).\n- iio: light: si1133: reset counter to prevent race condition (git-fixes).\n- iio: light: veml6030: fix channel type when pushing events (git-fixes).\n- iio: light: veml6075: add bounds check to veml6075_it_ms index (stable-fixes).\n- iio: magnetometer: ak8975: Add missed pm_runtime_put_autosuspend() call (git-fixes).\n- iio: resolver: ad2s1210: notify trigger and clear state on fault read error (git-fixes).\n- iio: tcs3472: power down chip on probe failure (git-fixes).\n- iio: temperature: ltc2983: Fix n_wires default bypassing rotation check (git-fixes).\n- iio: temperature: ltc2983: Fix reinit_completion() called after conversion start (git-fixes).\n- Input: atkbd - add DMI quirk for Lenovo Yoga Air 14 (83QK) (stable-fixes).\n- Input: elan_i2c - validate firmware size before use (stable-fixes).\n- Input: synaptics - add LEN2058 to SMBus passlist for ThinkPad E490 (stable-fixes).\n- Input: xpad - add \"Nova 2 Lite\" from GameSir (stable-fixes).\n- Input: xpad - add support for ASUS ROG RAIKIRI II (stable-fixes).\n- io_uring/cancel: de-unionize file and user_data in struct io_cancel_data (git-fixes bsc#1261250).\n- io_uring/filetable: clamp alloc_hint to the configured alloc range (git-fixes bsc#1261250).\n- io_uring/io-wq: fix incorrect io_wq_for_each_worker() termination logic (git-fixes bsc#1261250).\n- io_uring/poll: ensure EPOLL_ONESHOT is propagated for EPOLL_URING_WAKE (git-fixes bsc#1261250).\n- io_uring/wait: fix min_timeout behavior (git-fixes bsc#1261250).\n- io_uring/waitid: clear waitid info before copying it to userspace (git-fixes).\n- io_uring: fix min_wait wakeups for SQPOLL (git-fixes bsc#1261250).\n- ipv4: account for fraggap on the paged allocation path (git-fixes).\n- ipv6: account for fraggap on the paged allocation path (git-fixes).\n- KEYS: fix overflow in keyctl_pkey_params_get_2() (git-fixes).\n- KEYS: Use acquire when reading state in keyring search (git-fixes).\n- KVM: arm64: PMU: Preserve AArch32 counter low bits (git-fixes).\n- KVM: arm64: vgic: Free private_irqs when init fails after allocation (git-fixes).\n- KVM: Don't WARN if memory is dirtied without a vCPU when the VM is dying (git-fixes).\n- KVM: nSVM: Always use NextRIP as vmcb02's NextRIP after first L2 VMRUN (git-fixes).\n- KVM: nSVM: Always use vmcb01 in VMLOAD/VMSAVE emulation (git-fixes).\n- KVM: nSVM: Ensure AVIC is inhibited when restoring a vCPU to guest mode (git-fixes).\n- KVM: nSVM: Mark all of vmcb02 dirty when restoring nested state (git-fixes).\n- KVM: nSVM: Sync interrupt shadow to cached vmcb12 after VMRUN of L2 (git-fixes).\n- KVM: nSVM: Sync NextRIP to cached vmcb12 after VMRUN of L2 (git-fixes).\n- KVM: nVMX: Immediately refresh APICv controls as needed on nested VM-Exit (git-fixes).\n- KVM: Replace guest-triggerable BUG_ON() in ioeventfd datamatch with get_unaligned() (git-fixes).\n- KVM: SEV: Add an anonymous \"psc\" struct to track current PSC metadata (git-fixes).\n- KVM: SEV: Decouple the need to sync the GHCB SA from the need to free the SA (git-fixes).\n- KVM: SEV: Don't terminate SNP VMs on #VMGEXIT without a registered GHCB (git-fixes).\n- KVM: SEV: Make it more obvious when KVM is writing back the current PSC index (git-fixes).\n- KVM: SEV: Move sev_free_vcpu() down below sev_es_unmap_ghcb() (git-fixes).\n- KVM: SEV: Read start/end indices of PSC requests exactly once per #VMGEXIT (git-fixes).\n- KVM: SEV: Return INVALID_EVENT for SNP-only #VMGEXIT from non-SNP guest (git-fixes).\n- KVM: SEV: Return INVALID_INPUT, not MISSING_INPUT, for bad GUEST_REQUEST input(s) (git-fixes).\n- KVM: SEV: Unmap and unpin the GHCB as needed on vCPU free (git-fixes).\n- KVM: SVM: Allow KVM_SET_NESTED_STATE to clear GIF when SVME==0 (git-fixes).\n- KVM: SVM: check validity of VMCB controls when returning from SMM (git-fixes).\n- KVM: SVM: Don't set GIF when clearing EFER.SVME (git-fixes).\n- KVM: SVM: Truncate INVLPGA address in compatibility mode (git-fixes).\n- KVM: Use vCPU specific memslots in __kvm_vcpu_map() (git-fixes).\n- KVM: VMX: Grab vmcs12 on CR8 interception update iff vCPU is in guest mode (git-fixes).\n- KVM: VMX: Read 32-bit GPR values for ENCLS instructions outside of 64-bit mode (git-fixes).\n- KVM: x86/mmu: Ensure hugepage is in by slot before checking max mapping level (git-fixes).\n- KVM: x86/mmu: Recursively zap orphaned nested TDP shadow pages on emulated writes (git-fixes).\n- KVM: x86/xen: Bug the VM if 32-bit KVM observes a 64-bit mode hypercall (git-fixes).\n- KVM: x86/xen: Don't truncate RAX when handling hypercall from protected guest (git-fixes).\n- KVM: x86: Consolidate CPUID fault handling for emulator and interception logic (git-fixes).\n- KVM: x86: Fix shadow paging use-after-free due to unexpected role (git-fixes).\n- KVM: x86: hyper-v: Bound the bank index when querying sparse banks (git-fixes).\n- KVM: x86: ioapic: Use old_dest_mode consistently in ioapic_write_indirect() (git-fixes).\n- KVM: x86: Move update_cr8_intercept() to lapic.c (git-fixes).\n- KVM: x86: Prioritize CPUID faulting over CPUID VM-exits in nested VMX (git-fixes).\n- KVM: x86: Trace hypercall register *after* truncating values for 32-bit (git-fixes).\n- KVM: x86: Unconditionally recompute CR8 intercept on PPR update (git-fixes).\n- mailbox: imx: Forward the timeout/ error in imx_mu_generic_tx() (git-fixes).\n- mailbox: mtk-adsp: fix UAF during device teardown (git-fixes).\n- misc: fastrpc: fix DMA address corruption due to find_vma misuse (git-fixes).\n- misc: fastrpc: Fix NULL pointer dereference in rpmsg callback (git-fixes).\n- misc: fastrpc: fix use-after-free of fastrpc_user in workqueue context (git-fixes).\n- misc: fastrpc: fix use-after-free race in fastrpc_map_create (git-fixes).\n- mm/vmstat: defer the refresh_zone_stat_thresholds after all CPUs bringup (bsc#1270042).\n- mtd: maps: vmu-flash: fix NULL pointer dereference in initialization (git-fixes).\n- mtd: rawnand: fix condition in 'nand_select_target()' (git-fixes).\n- mtd: rawnand: Pause continuous reads at block boundaries (git-fixes).\n- mtd: rawnand: pl353: fix probe resource allocation (git-fixes).\n- mtd: slram: remove failed entries from the device list (git-fixes).\n- mtd: spi-nor: Drop duplicate Kconfig dependency (git-fixes).\n- mtd: spi-nor: macronix: Add post_sfdp fixups for Quad Input Page Program (stable-fixes).\n- mtd: spi-nor: macronix: add support for mx66{l2, u1}g45g (stable-fixes).\n- mtd: spi-nor: spansion: use die erase for multi-die devices only (git-fixes).\n- mtd: spi-nor: swp: Improve locking user experience (git-fixes).\n- net: aquantia: Add missing descriptor cache invalidation on ATL2 (bsc#1268428).\n- net: ethtool: add ethtool COALESCE_RX_CQE_FRAMES/NSECS (bsc#1261256).\n- net: mana: Add ethtool counters for RX CQEs in coalesced type (bsc#1261256).\n- net: mana: Add support for PF device 0x00C1 (bsc#1268237).\n- net: mana: Add support for RX CQE Coalescing (bsc#1261256).\n- net: mana: Allocate interrupt context for each EQ when creating vPort (git-fixes).\n- net: mana: Cache MANA_QUERY_LINK_CONFIG result to avoid repeated HWC queries (bsc#1268238).\n- net: mana: Create separate EQs for each vPort (git-fixes).\n- net: mana: Fall back to standard MTU when PF reports adapter_mtu of 0 (git-fixes).\n- net: mana: guard TX wq object destroy with INVALID_MANA_HANDLE check (git-fixes).\n- net: mana: initialize gdma queue id to INVALID_QUEUE_ID (git-fixes).\n- net: mana: Introduce GIC context with refcounting for interrupt management (git-fixes).\n- net: mana: Optimize irq affinity for low vcpu configs (git-fixes).\n- net: mana: Query device capabilities and configure MSI-X sharing for EQs (git-fixes).\n- net: mana: Sync page pool RX frags for CPU (git-fixes).\n- net: mana: Use GIC functions to allocate global EQs (git-fixes).\n- net: mana: Validate the packet length reported by the NIC (git-fixes).\n- net: phy: sfp: free mii_bus in sfp_i2c_mdiobus_destroy (git-fixes).\n- net: usb: lan78xx: disable VLAN filter in promiscuous mode (git-fixes).\n- net: usb: net1080: validate packet_len before pad-byte access in rx_fixup (git-fixes).\n- net: wwan: iosm: bound device offsets in the MUX downlink decoder (git-fixes).\n- nfc: hci: fix out-of-bounds read in HCP header parsing (git-fixes).\n- nfc: llcp: Fix use-after-free in llcp_sock_release() (git-fixes).\n- nfc: llcp: Fix use-after-free race in nfc_llcp_recv_cc() (git-fixes).\n- packaging: Add nvidia kernel description.\n- packaging: compute-PATCHVERSION.sh -\u003e compute-PATCHVERSION.\n- page_pool: Fix PP_MAGIC_MASK to avoid crashing on some 32-bit arches (bsc#1261562).\n- page_pool: Move pp_magic check into helper functions (bsc#1261562).\n- page_pool: Track DMA-mapped pages and unmap them when destroying the pool (bsc#1261562).\n- PCI: Update saved_config_space upon resource assignment (git-fixes).\n- perf/x86/intel/uncore: Fix die ID init and look up bugs (bsc#1267419).\n- perf/x86/intel/uncore: Skip discovery table for offline dies (bsc#1267419).\n- platform/x86: dell-laptop: fix missing cleanups in init error path (git-fixes).\n- platform/x86: intel-hid: Protect ACPI notify handler against recursion (git-fixes).\n- platform/x86: xo15-ebook: Fix wakeup source and GPE handling (git-fixes).\n- PM: sleep: Use complete() in device_pm_sleep_init() (git-fixes).\n- power: reset: linkstation-poweroff: fix use-after-free in the linkstation_poweroff_init() (git-fixes).\n- power: supply: charger-manager: fix refcount leak in is_full_charged() (git-fixes).\n- power: supply: core: fix supplied_from allocations (git-fixes).\n- power: supply: cpcap-battery: Fix missing nvmem_device_put() causing reference leak (git-fixes).\n- powerpc/boot: Allow text relocations for pseries wrapper with binutils 2.46+ (git-fixes).\n- powerpc/fadump: define MIN_RMA in bytes rather than MB (bsc#1236743 git-fixes).\n- ppc/fadump: invoke kmsg_dump in fadump panic path (bsc#1270226 ltc#218302).\n- pwm: imx27: Fix variable truncation in .apply() (git-fixes).\n- RDMA/mana_ib: Allocate interrupt contexts on EQs (git-fixes).\n- RDMA/mana_ib: Use ib_get_eth_speed for reporting port speed (git-fixes).\n- regulator: scmi: fix of_node refcount leak in scmi_regulator_probe() (git-fixes).\n- Revert \"fs: don't block i_writecount during exec\" (bsc#1269982).\n- rtc: abx80x: fix the RTC_VL_CLR clearing all status flags (git-fixes).\n- rtc: cmos: unregister HPET IRQ handler on probe failure (git-fixes).\n- rtc: ds1307: Fix off-by-one issue with wday for rx8130 (git-fixes).\n- rtc: ds1307: handle oscillator stop flag for ds1337/ds1339/ds3231 (git-fixes).\n- rtc: mpfs: fix counter upload completion condition (git-fixes).\n- rtc: msc313: fix NULL deref in shared IRQ handler at probe (git-fixes).\n- scripts/sorttable: Add helper functions for Elf_Ehdr (bsc#1267600).\n- scripts/sorttable: Add helper functions for Elf_Shdr (bsc#1267600).\n- scripts/sorttable: Add helper functions for Elf_Sym (bsc#1267600).\n- scripts/sorttable: Allow matches to functions before function entry (bsc#1267600).\n- scripts/sorttable: Always use an array for the mcount_loc sorting (bsc#1267600).\n- scripts/sorttable: Convert Elf_Ehdr to union (bsc#1267600).\n- scripts/sorttable: Convert Elf_Sym MACRO over to a union (bsc#1267600).\n- scripts/sorttable: Fix endianness handling in build-time mcount sort (bsc#1267600).\n- scripts/sorttable: Get start/stop_mcount_loc from ELF file directly (bsc#1267600).\n- scripts/sorttable: Have mcount rela sort use direct values (bsc#1267600).\n- scripts/sorttable: Have the ORC code use the _r() functions to read (bsc#1267600).\n- scripts/sorttable: Make compare_extable() into two functions (bsc#1267600).\n- scripts/sorttable: Move code from sorttable.h into sorttable.c (bsc#1267600).\n- scripts/sorttable: Remove unneeded Elf_Rel (bsc#1267600).\n- scripts/sorttable: Remove unused macro defines (bsc#1267600).\n- scripts/sorttable: Remove unused write functions (bsc#1267600).\n- scripts/sorttable: Replace Elf_Shdr Macro with a union (bsc#1267600).\n- scripts/sorttable: Use a structure of function pointers for elf helpers (bsc#1267600).\n- scripts/sorttable: Use normal sort if theres no relocs in the mcount section (bsc#1267600).\n- scripts/sorttable: Use uint64_t for mcount sorting (bsc#1267600).\n- scripts/sorttable: Zero out weak functions in mcount_loc table (bsc#1267600).\n- scsi: smartpqi: Use shost_to_hba() in pqi_scan_finished() (bsc#1257506).\n- scsi: storvsc: Replace symbolic permissions with octal (git-fixes).\n- scsi: target: Fix hexadecimal CHAP_I handling (git-fixes).\n- selftests/bpf: Add BPF_STRICT_BUILD toggle (poo#202224).\n- selftests/bpf: Allow test_progs to link with a partial object set (poo#202224).\n- selftests/bpf: Avoid rebuilds when running emit_tests (poo#202224).\n- selftests/bpf: Consolidate kernel modules into common directory (poo#202224).\n- selftests/bpf: Copy test_kmods when installing selftest (poo#202224).\n- selftests/bpf: Fix runqslower cross-endian build (poo#202224).\n- selftests/bpf: Fix test_kmods KDIR to honor O= and distro kernels (poo#202224).\n- selftests/bpf: make BPF_TARGET_ENDIAN non-recursive to speed up *.bpf.o build (poo#202224).\n- selftests/bpf: Make skeleton headers order-only prerequisites of .test.d (poo#202224).\n- selftests/bpf: Provide weak definitions for cross-test functions (poo#202224).\n- selftests/bpf: Skip tests whose objects were not built (poo#202224).\n- selftests/bpf: Support cross-endian building (poo#202224).\n- selftests/bpf: Tolerate benchmark build failures (poo#202224).\n- selftests/bpf: Tolerate BPF and skeleton generation failures (poo#202224).\n- selftests/bpf: Tolerate missing files during install (poo#202224).\n- selftests/bpf: Tolerate test file compilation failures (poo#202224).\n- serial: 8250: dispatch SysRq character in serial8250_handle_irq() (git-fixes).\n- serial: 8250_dw: dispatch SysRq character in dw8250_handle_irq() (git-fixes).\n- serial: qcom_geni: Fix RX DMA stall when SE_DMA_RX_LEN_IN is zero (git-fixes).\n- slimbus: qcom-ngd-ctrl: Avoid ABBA on tx_lock/ctrl-\u003elock (git-fixes).\n- slimbus: qcom-ngd-ctrl: Balance pm_runtime enablement for NGD (git-fixes).\n- slimbus: qcom-ngd-ctrl: Correct PDR and SSR cleanup ownership (git-fixes).\n- slimbus: qcom-ngd-ctrl: fix OF node refcount (git-fixes).\n- slimbus: qcom-ngd-ctrl: Fix probe error path ordering (git-fixes).\n- slimbus: qcom-ngd-ctrl: Fix up platform_driver registration (git-fixes).\n- slimbus: qcom-ngd-ctrl: Initialize controller resources in controller (git-fixes).\n- slimbus: qcom-ngd-ctrl: Register callbacks after creating the ngd (git-fixes).\n- soc: qcom: ice: Fix race between qcom_ice_probe() and of_qcom_ice_get() (git-fixes).\n- soc: qcom: ice: Return -ENODEV if the ICE platform device is not found (git-fixes).\n- spi: at91-usart: drop dead runtime pm support (git-fixes).\n- spi: dw: fix wrong BAUDR setting after resume (git-fixes).\n- spi: ep93xx: fix double-free of zeropage on DMA setup failure (git-fixes).\n- spi: fsl-lpspi: replace dmaengine_terminate_all() with dmaengine_terminate_sync() (git-fixes).\n- spi: fsl-lpspi: terminate the RX channel on TX prepare failure path (git-fixes).\n- spi: hisi-kunpeng: Use dev_err_probe() for host registration failure (git-fixes).\n- spi: meson-spifc: fix runtime PM leak on remove (git-fixes).\n- spi: rpc-if: Use correct device for hardware reinitialization on resume (git-fixes).\n- spi: uniphier: Fix completion initialization order before devm_request_irq() (git-fixes).\n- spi: xilinx: use FIFO occupancy register to determine buffer size (git-fixes).\n- Split off kABI workaround for bsc#1267458 (bsc#1267458).\n- staging: most: video: avoid double free on video register failure (git-fixes).\n- staging: nvec: fix use-after-free in nvec_rx_completed() (git-fixes).\n- thermal: hwmon: Fix critical temperature attribute removal (git-fixes).\n- thermal: intel: Fix dangling resources on thermal_throttle_online() failure (git-fixes).\n- thermal: testing: reject missing command arguments (git-fixes).\n- thermal: testing: zone: Flush work items during cleanup (git-fixes).\n- thunderbolt: Bound root directory content to block size (git-fixes).\n- thunderbolt: Clamp XDomain response data copy to allocation size (git-fixes).\n- thunderbolt: debugfs: Don't stop reading SB registers if just one fails (git-fixes).\n- thunderbolt: debugfs: Fix margining error counter buffer leak (git-fixes).\n- thunderbolt: Limit XDomain response copy to actual frame size (git-fixes).\n- thunderbolt: Reject zero-length property entries in validator (git-fixes).\n- thunderbolt: Validate XDomain request packet size before type cast (git-fixes).\n- tools/power/x86/intel-speed-select: Harden daemon pidfile open (git-fixes).\n- tpm: fix event_size output in tpm1_binary_bios_measurements_show (git-fixes).\n- tpm: tpm2-sessions: wait for async KPP completion in tpm_buf_append_salt (git-fixes).\n- tpm: tpm_tis_spi: Use wait_woken() in wait_for_tmp_stat() (git-fixes).\n- usb: core: Fix SuperSpeed root hub wMaxPacketSize (stable-fixes).\n- usb: core: Fix up Interrupt IN endpoints with bogus wBytesPerInterval (stable-fixes).\n- usb: host: max3421: Fix shift-out-of-bounds in max3421_hub_control() (git-fixes).\n- usb: host: max3421: Reject hub port requests for non-existent ports (git-fixes).\n- USB: quirks: add NO_LPM for Lenovo ThinkPad USB-C Dock Gen2 hub controllers (git-fixes).\n- USB: serial: io_ti: fix heap overflow in build_i2c_fw_hdr() (git-fixes).\n- USB: serial: io_ti: fix heap overflow in get_manuf_info() (git-fixes).\n- USB: serial: kl5kusb105: fix bulk-out buffer overflow (git-fixes).\n- USB: serial: option: add usb-id for Dell Wireless DW5826e-m (stable-fixes).\n- usb: storage: Add quirks for PNY Elite Portable SSD (git-fixes).\n- usb: typec: altmodes/displayport: validate count before reading Status Update VDO (stable-fixes).\n- usb: typec: tcpm/tcpci_maxim: validate header NDO against RX_BYTE_CNT (stable-fixes).\n- usb: typec: tcpm: bound altmode_desc[] per iteration in svdm_consume_modes() (stable-fixes).\n- usb: typec: tcpm: validate VDO count in Discover Identity ACK handlers (stable-fixes).\n- usb: typec: ucsi: ccg: reject firmware images without a ':' record header (stable-fixes).\n- usb: typec: ucsi: displayport: NAK DP_CMD_CONFIGURE without a payload VDO (stable-fixes).\n- usb: typec: ucsi: validate connector number in ucsi_connector_change() (stable-fixes).\n- usb: typec: wcove: don't write past struct pd_message in wcove_read_rx_buffer() (stable-fixes).\n- usbnet: gl620a: fix out-of-bounds read in genelink_rx_fixup() (git-fixes).\n- vc_screen: fix null-ptr-deref in vcs_notifier() during concurrent vcs_write (git-fixes).\n- watchdog/hpwdt: Refine hpwdt message for UV platform (bsc#1269199).\n- watchdog: apple: Add \"apple,t8103-wdt\" compatible (git-fixes).\n- watchdog: sama5d4_wdt: Fix WDDIS detection on SAM9X60 and SAMA7G5 (git-fixes).\n- watchdog: sp5100_tco: Use EFCH MMIO for newer Hygon FCH (git-fixes).\n- watchdog: sprd_wdt: Remove redundant sprd_wdt_disable() on register failure (git-fixes).\n- watchdog: unregister PM notifier on watchdog unregister (git-fixes).\n- wifi: ath9k: fix OOB access from firmware tx status queue ID (git-fixes).\n- wifi: ath11k: fix warning when unbinding (git-fixes).\n- wifi: cfg80211: fix grammar in MLO group key error message (git-fixes).\n- wifi: iwlwifi: mvm: fix race condition in PTP removal (stable-fixes).\n- wifi: mac80211: fix monitor mode frame capture for real chanctx drivers (git-fixes).\n- wifi: mt76: fix argument to ieee80211_is_first_frag() (git-fixes).\n- wifi: mt76: mt76x2u: Add support for ELECOM WDC-867SU3S (stable-fixes).\n- wifi: mt76: mt792x: skip MLD header rewrite for 802.3 encap TX (git-fixes).\n- wifi: mt76: mt7915: fix potential tx_retries underflow (git-fixes).\n- wifi: mt76: mt7921: avoid undesired changes of the preset regulatory domain (stable-fixes).\n- wifi: mt76: mt7921: fix a potential scan no APs (stable-fixes).\n- wifi: mt76: mt7921: fix potential tx_retries underflow (git-fixes).\n- wifi: mt76: mt7925: clean up DMA on probe failure (git-fixes).\n- wifi: mt76: mt7925: don't disable AP BSS when removing TDLS peer (git-fixes).\n- wifi: mt76: mt7925: fix potential tx_retries underflow (git-fixes).\n- wifi: mt76: mt7925: fix stale pointer comparisons in change_vif_links (git-fixes).\n- wifi: mt76: mt7925: keep TX BA state in the primary WCID (git-fixes).\n- wifi: mt76: mt7996: fix potential tx_retries underflow (git-fixes).\n- wifi: rtlwifi: rtl8821ae: Fix C2H bit location in RX descriptor (git-fixes).\n- wifi: rtw88: fix OOB read from firmware RX descriptor exceeding DMA buffer (git-fixes).\n- wifi: rtw88: increase TX report timeout to fix race condition (git-fixes).\n- wifi: rtw88: usb: fix memory leaks on USB write failures (git-fixes).\n- wifi: rtw89: Correct data type for scan index to avoid infinite loop (git-fixes).\n- wifi: wcn36xx: fix heap overflow from oversized firmware HAL response (git-fixes).\n- wifi: wcn36xx: fix OOB read from firmware count in PRINT_REG_INFO indication (git-fixes).\n- wifi: wcn36xx: fix OOB read from short trigger BA firmware response (git-fixes).\n- x86/cpu/amd: Correct the microcode table for Zenbleed (git-fixes).\n- x86/cpu: Disable FRED when PTI is forced on (git-fixes).\n- x86/cpu: Properly parse CPUID leaf 0x2 TLB descriptor 0x63 (git-fixes).\n- x86/cpu: Validate CPUID leaf 0x2 EDX output (git-fixes).\n- x86/irq: Ensure initial PIR loads are performed exactly once (git-fixes).\n- x86/platform/uv: Expose the uv_hub_type() interface (jsc#PED-16390).\n- x86/tsc: Disable clocksource watchdog checking on recent and future UV platforms (jsc#PED-16390).\n- X.509: Fix validation of ASN.1 certificate header (git-fixes).\n- xfrm: Fix dev use-after-free in xfrm async resumption (bsc#1268276).\n","status":"published","published":"2026-07-21T08:27:34Z","modified":"2026-07-23T18:24:21.24177443Z","updated_at":"2026-11-02T15:54:03.080707Z"},{"id":"SUSE-SU-2026:22812-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-10263: arm64: cputype: Add C1-Premium definitions (bsc#1266290).\n- CVE-2025-39894: netfilter: br_netfilter: do not check confirmed bit\n  in br_nf_local_in() after confirm (bsc#1262430).\n- CVE-2025-40341: futex: Don't leak robust_list pointer on exec race (bsc#1255029).\n- CVE-2026-23248: perf: Make perf_pmu_unregister() useable (bsc#1259800).\n- CVE-2026-23394: Revert: \"af_unix: Remove lock dance in unix_peek_fds().\" (bsc#1260565).\n- CVE-2026-23451: bonding: prevent potential infinite loop in bond_header_parse() (bsc#1261604).\n- CVE-2026-31414: netfilter: nf_conntrack_expect: use expect-\u003ehelper (bsc#1262085).\n- CVE-2026-31429: net: skb: fix cross-cache free of KFENCE-allocated skb head (bsc#1262392).\n- CVE-2026-31438: netfs: Fix kernel BUG in netfs_limit_iter() for ITER_KVEC iterators (bsc#1267824).\n- CVE-2026-31450: ext4: publish jinode after initialization (bsc#1262618).\n- CVE-2026-31452: ext4: convert inline data to extents when truncate exceeds inline size (bsc#1262620).\n- CVE-2026-31466: mm/huge_memory: fix folio isn't locked in softleaf_to_folio() (bsc#1267825).\n- CVE-2026-31469: virtio_net: Fix UAF on dst_ops when IFF_XMIT_DST_RELEASE is cleared and napi_tx is false\n  (bsc#1267816).\n- CVE-2026-31479: drm/xe: always keep track of remap prev/next (bsc#1262765).\n- CVE-2026-31492: RDMA/irdma: Initialize free_qp completion before using it (bsc#1262748).\n- CVE-2026-31495: netfilter: ctnetlink: use netlink policy range checks (bsc#1262798).\n- CVE-2026-31499: Bluetooth: L2CAP: Fix deadlock in l2cap_conn_del() (bsc#1262674).\n- CVE-2026-31502: team: fix header_ops type confusion with non-Ethernet ports (bsc#1263072).\n- CVE-2026-31555: futex: Clear stale exiting pointer in futex_lock_pi() retry path (bsc#1263178).\n- CVE-2026-31560: spi: spi-dw-dma: fix print error log when wait finish transaction (bsc#1263057).\n- CVE-2026-31596: ocfs2: handle invalid dinode in ocfs2_group_extend (bsc#1263319).\n- CVE-2026-31646: net: lan966x: fix page_pool error handling in lan966x_fdma_rx_alloc_page_pool() (bsc#1263796).\n- CVE-2026-31647: idpf: fix PREEMPT_RT raw/bh spinlock nesting for async VC handling (bsc#1263581).\n- CVE-2026-31663: xfrm: hold device only for the asynchronous decryption (bsc#1263133).\n- CVE-2026-31664: xfrm: clear trailing padding in build_polexpire() (bsc#1263578).\n- CVE-2026-31665: netfilter: nft_ct: fix use-after-free in timeout object destroy (bsc#1263137).\n- CVE-2026-31670: net: rfkill: prevent unlimited numbers of rfkill events from being created (bsc#1263573).\n- CVE-2026-31673: af_unix: read UNIX_DIAG_VFS data under unix_state_lock (bsc#1263143).\n- CVE-2026-31674: netfilter: ip6t_rt: reject oversized addrnr in rt_mt6_check() (bsc#1263568).\n- CVE-2026-31680: net: ipv6: flowlabel: defer exclusive option free until RCU teardown (bsc#1263563).\n- CVE-2026-31693: cifs: some missing initializations on replay (bsc#1267744).\n- CVE-2026-31743: nvmem: zynqmp_nvmem: Fix buffer size in DMA and memcpy (bsc#1264067).\n- CVE-2026-31752: bridge: br_nd_send: validate ND option lengths (bsc#1264045).\n- CVE-2026-31771: Bluetooth: hci_event: move wake reason storage into validated event handlers (bsc#1264145).\n- CVE-2026-43010: bpf: Reject sleepable kprobe_multi programs at attach time (bsc#1264015).\n- CVE-2026-43014,CVE-2026-43015: net: macb: fix clk handling on PCI glue driver removal (bsc#1264010 bsc#1264012).\n- CVE-2026-43016: bpf: sockmap: Fix use-after-free of sk-\u003esk_socket in sk_psock_verdict_data_ready() (bsc#1264007).\n- CVE-2026-43022: Bluetooth: hci_sync: hci_cmd_sync_queue_once() return -EEXIST if exists (bsc#1264001).\n- CVE-2026-43024: netfilter: nf_tables: reject immediate NF_QUEUE verdict (bsc#1263930).\n- CVE-2026-43028: netfilter: x_tables: ensure names are nul-terminated (bsc#1263934).\n- CVE-2026-43034: bnxt_en: set backing store type from query type (bsc#1263998).\n- CVE-2026-43035: net: sched: cls_api: fix tc_chain_fill_node to\n  initialize tcm_info to zero to prevent an info-leak (bsc#1263996).\n- CVE-2026-43036: net: use skb_header_pointer() for TCPv4 GSO frag_off check (bsc#1263993).\n- CVE-2026-43053: xfs: factor out xfs_attr3_node_entry_remove (bsc#1264084).\n- CVE-2026-43057: net: correctly handle tunneled traffic on IPV6_CSUM GSO fallback (bsc#1264056).\n- CVE-2026-43074: eventpoll: defer struct eventpoll free to RCU grace period (bsc#1264263).\n- CVE-2026-43080: l2tp: Drop large packets with UDP encap (bsc#1264236).\n- CVE-2026-43081: net: ipa: fix GENERIC_CMD register field masks for IPA v5.0+ (bsc#1264241).\n- CVE-2026-43083: net: ioam6: fix OOB and missing lock (bsc#1264266).\n- CVE-2026-43085: netfilter: nfnetlink_log: initialize nfgenmsg in NLMSG_DONE terminator (bsc#1264230).\n- CVE-2026-43086: ipvs: fix NULL deref in ip_vs_add_service error path (bsc#1264286).\n- CVE-2026-43089: xfrm_user: fix info leak in build_mapping() (bsc#1264261).\n- CVE-2026-43090: xfrm: fix refcount leak in xfrm_migrate_policy_find (bsc#1264250).\n- CVE-2026-43092: xsk: validate MTU against usable frame size on bind (bsc#1264270).\n- CVE-2026-43093: xsk: tighten UMEM headroom validation to account for tailroom and min frame (bsc#1264254).\n- CVE-2026-43094: ixgbevf: add missing negotiate_features op to Hyper-V ops table (bsc#1264231).\n- CVE-2026-43101: ipv6: ioam: fix potential NULL dereferences in __ioam6_fill_trace_data() (bsc#1264239).\n- CVE-2026-43107: xfrm: account XFRMA_IF_ID in aevent size calculation (bsc#1264258).\n- CVE-2026-43119: Bluetooth: hci_sync: annotate data-races around hdev-\u003ereq_status (bsc#1264561).\n- CVE-2026-43124: pstore: ram_core: fix incorrect success return when vmap() fails (bsc#1264545).\n- CVE-2026-43128: RDMA/umem: Fix double dma_buf_unpin in failure path (bsc#1264612).\n- CVE-2026-43130: iommu/vt-d: Flush dev-IOTLB only when PCIe device is accessible in scalable mode (bsc#1264532).\n- CVE-2026-43132: dm-verity: correctly handle dm_bufio_client_create() failure (bsc#1264614).\n- CVE-2026-43139: xfrm6: fix uninitialized saddr in xfrm6_get_saddr() (bsc#1264294).\n- CVE-2026-43145: remoteproc: imx_rproc: Fix invalid loaded resource table detection (bsc#1265091).\n- CVE-2026-43157: octeontx2-af: CGX: fix bitmap leaks (bsc#1264624).\n- CVE-2026-43158: xfs: fix freemap adjustments when adding xattrs to leaf blocks (bsc#1264595).\n- CVE-2026-43161: iommu/vt-d: Skip dev-iotlb flush for inaccessible PCIe device without scalable mode (bsc#1264333).\n- CVE-2026-43167: xfrm: always flush state and policy upon NETDEV_UNREGISTER event (bsc#1264580).\n- CVE-2026-43171: EFI/CPER: don't dump the entire memory region (bsc#1264549).\n- CVE-2026-43175: clk: rs9: Reserve 8 struct clk_hw slots for for 9FGV0841 (bsc#1264372).\n- CVE-2026-43187: xfs: delete attr leaf freemap entries when empty (bsc#1264603).\n- CVE-2026-43191: drm/amd/display: Adjust PHY FSM transition to TX_EN-to-PLL_ON for TMDS on DCN35 (bsc#1264548).\n- CVE-2026-43194: net: consume xmit errors of GSO frames (bsc#1264304).\n- CVE-2026-43198: tcp: fix potential race in tcp_v6_syn_recv_sock() (bsc#1264610).\n- CVE-2026-43199: net/mlx5e: Fix \"scheduling while atomic\" in IPsec MAC address query (bsc#1264556).\n- CVE-2026-43205: dpaa2-switch: validate num_ifs to prevent out-of-bounds write (bsc#1264328).\n- CVE-2026-43213: wifi: rtw89: pci: validate sequence number of TX release report (bsc#1264643).\n- CVE-2026-43226: net/rds: No shortcut out of RDS_CONN_ERROR (bsc#1264544).\n- CVE-2026-43233: netfilter: nf_conntrack_h323: fix OOB read in decode_choice() (bsc#1264337).\n- CVE-2026-43238: net/sched: act_skbedit: fix divide-by-zero in tcf_skbedit_hash() (bsc#1264320).\n- CVE-2026-43240: ima: verify the previous kernel's IMA buffer lies in addressable RAM (bsc#1264386).\n- CVE-2026-43248: vhost: move vdpa group bound check to vhost_vdpa (bsc#1264302).\n- CVE-2026-43260: bnxt_en: Fix RSS context delete logic (bsc#1264429).\n- CVE-2026-43283: net: ethernet: ec_bhf: Fix dma_free_coherent() dma handle (bsc#1264295).\n- CVE-2026-43298: drm/amdgpu: Skip vcn poison irq release on VF (bsc#1264852).\n- CVE-2026-43303: mm/page_alloc: clear page-\u003eprivate in free_pages_prepare() (bsc#1264974).\n- CVE-2026-43336: lib/crypto: chacha: Zeroize permuted_state before it leaves scope (bsc#1265113).\n- CVE-2026-43337: drm/amd/display: Fix NULL pointer dereference in dcn401_init_hw() (bsc#1265112).\n- CVE-2026-43339: ipv6: prevent possible UaF in addrconf_permanent_addr() (bsc#1264763).\n- CVE-2026-43345: net: ipa: fix event ring index not programmed for IPA v5.0+ (bsc#1265103).\n- CVE-2026-43351: KVM: arm64: gic: Set vgic_model before initing private IRQs (bsc#1265082).\n- CVE-2026-43373: net: ncsi: fix skb leak in error paths (bsc#1265079).\n- CVE-2026-43374: net: nexthop: fix percpu use-after-free in remove_nh_grp_entry (bsc#1265084).\n- CVE-2026-43383: net/tcp-md5: Fix MAC comparison to be constant-time (bsc#1264744).\n- CVE-2026-43384: net/tcp-ao: Fix MAC comparison to be constant-time (bsc#1265097).\n- CVE-2026-43386: staging: rtl8723bs: fix potential out-of-bounds read in rtw_restruct_wmm_ie (bsc#1264740).\n- CVE-2026-43403: nsfs: tighten permission checks for ns iteration ioctls (bsc#1265129).\n- CVE-2026-43405: libceph: Use u32 for non-negative values in ceph_monmap_decode() (bsc#1264741).\n- CVE-2026-43406: libceph: prevent potential out-of-bounds reads in process_message_header() (bsc#1265073).\n- CVE-2026-43407: libceph: Fix potential out-of-bounds access in ceph_handle_auth_reply() (bsc#1265020).\n- CVE-2026-43415: scsi: ufs: core: Fix SError in ufshcd_rtc_work() during UFS suspend (bsc#1265123).\n- CVE-2026-43449: nvme-pci: Fix slab-out-of-bounds in nvme_dbbuf_set (bsc#1265023).\n- CVE-2026-43450: netfilter: nfnetlink_cthelper: fix OOB read in nfnl_cthelper_dump_table() (bsc#1264794).\n- CVE-2026-43452: netfilter: x_tables: guard option walkers against 1-byte tail reads (bsc#1265142).\n- CVE-2026-43456: bonding: fix type confusion in bond_setup_by_slave() (bsc#1264734).\n- CVE-2026-43457: mctp: i2c: fix skb memory leak in receive path (bsc#1265000).\n- CVE-2026-43458: serial: caif: hold tty-\u003elink reference in ldisc_open and ser_release (bsc#1265005).\n- CVE-2026-43465: net/mlx5e: RX, Fix XDP multi-buf frag counting for striding RQ (bsc#1264997).\n- CVE-2026-43466: net/mlx5e: Fix DMA FIFO desync on error CQE SQ recovery (bsc#1264790).\n- CVE-2026-43468: net/mlx5: Fix deadlock between devlink lock and esw-\u003ewq (bsc#1264978).\n- CVE-2026-43469: xprtrdma: Decrement re_receiving on the early exit paths (bsc#1265143).\n- CVE-2026-43470: nfs: return EISDIR on nfs3_proc_create if d_alias is a dir (bsc#1265128).\n- CVE-2026-43471: scsi: ufs: core: Fix possible NULL pointer dereference in ufshcd_add_command_trace() (bsc#1264789).\n- CVE-2026-43491: net: qrtr: ns: Limit the maximum server registration per node (bsc#1265628).\n- CVE-2026-43492: lib/crypto: mpi: Fix integer underflow in mpi_read_raw_from_sgl() (bsc#1265629).\n- CVE-2026-43502: net/rds: handle zerocopy send cleanup before the message is queued (bsc#1266008).\n- CVE-2026-45837: Require (reasonably) normal mappings for MADV_DOFORK (bsc#1266398).\n- CVE-2026-45838: bpf: fix end-of-list detection in cgroup_storage_get_next_key() (bsc#1266396).\n- CVE-2026-45840: openvswitch: cap upcall PID array size and pre-size vport replies (bsc#1266397).\n- CVE-2026-45841: netfilter: nfnetlink_osf: fix divide-by-zero in OSF_WSS_MODULO (bsc#1266390).\n- CVE-2026-45848: apparmor: fix NULL sock in aa_sock_file_perm (bsc#1266734).\n- CVE-2026-45857: scsi: csiostor: Fix dereference of null pointer rn (bsc#1266458).\n- CVE-2026-45858: ext4: don't zero the entire extent if EXT4_EXT_DATA_PARTIAL_VALID1 (bsc#1266773).\n- CVE-2026-45861: gfs2: Fix slab-use-after-free in qd_put (bsc#1266754).\n- CVE-2026-45862: iommu/vt-d: Flush cache for PASID table before using it (bsc#1266705).\n- CVE-2026-45870: SUNRPC: auth_gss: fix memory leaks in XDR decoding error paths (bsc#1266704).\n- CVE-2026-45884: apparmor: avoid per-cpu hold underflow in aa_get_buffer (bsc#1266718).\n- CVE-2026-45888: md/raid1: fix memory leak in raid1_run() (bsc#1266761).\n- CVE-2026-45891: net: hns3: fix double free issue for tx spare buffer (bsc#1266717).\n- CVE-2026-45894: iommu/vt-d: Clear Present bit before tearing down PASID entry (bsc#1266895).\n- CVE-2026-45899: ext4: drop extent cache when splitting extent fails (bsc#1266883).\n- CVE-2026-45901: netfilter: nf_tables: revert commit_mutex usage in reset path (bsc#1266892).\n- CVE-2026-45912: ext4: don't cache extent during splitting extent (bsc#1266899).\n- CVE-2026-45920: ext4: fix dirtyclusters double decrement on fs shutdown (bsc#1266893).\n- CVE-2026-45922: RDMA/mlx5: Fix memory leak in GET_DATA_DIRECT_SYSFS_PATH handler (bsc#1266805).\n- CVE-2026-45933: bpf: Preserve id of register in sync_linked_regs() (bsc#1266693).\n- CVE-2026-45940: net: stmmac: fix oops when split header is enabled (bsc#1266916).\n- CVE-2026-45948: ext4: fix memory leak in ext4_ext_shift_extents() (bsc#1266929).\n- CVE-2026-45961: gfs2: fix memory leaks in gfs2_fill_super error path (bsc#1266933).\n- CVE-2026-45964: SUNRPC: fix gss_auth kref leak in gss_alloc_msg error path (bsc#1266698).\n- CVE-2026-45965: apparmor: fix invalid deref of rawdata when export_binary is unset (bsc#1267208).\n- CVE-2026-45974: btrfs: fix invalid leaf access in btrfs_quota_enable() if ref key not found (bsc#1266922).\n- CVE-2026-45983: nfsd: never defer requests during idmap lookup (bsc#1266697).\n- CVE-2026-45985: ext4: don't set EXT4_GET_BLOCKS_CONVERT when splitting before submitting I/O (bsc#1266700).\n- CVE-2026-45997: scsi: sd: fix missing put_disk() when device_add(\u0026disk_dev) fails (bsc#1266740).\n- CVE-2026-45999: erofs: fix unsigned underflow in z_erofs_lz4_handle_overlap() (bsc#1266750).\n- CVE-2026-46005: xfs: fix a resource leak in xfs_alloc_buftarg() (bsc#1267431).\n- CVE-2026-46024: libceph: Prevent potential null-ptr-deref in ceph_handle_auth_reply() (bsc#1267218).\n- CVE-2026-46037: ipv4: icmp: validate reply type before using icmp_pointers (bsc#1267361).\n- CVE-2026-46046: ext4: fix missing brelse() in ext4_xattr_inode_dec_ref_all() (bsc#1266726).\n- CVE-2026-46050: md/raid10: fix deadlock with check operation and nowait requests (bsc#1266686).\n- CVE-2026-46051: md/raid5: fix soft lockup in retry_aligned_read() (bsc#1267360).\n- CVE-2026-46053: net: rds: fix MR cleanup on copy error (bsc#1267427).\n- CVE-2026-46063: x86/shstk: Prevent deadlock during shstk sigreturn (bsc#1267228).\n- CVE-2026-46065: fbdev: defio: Disconnect deferred I/O from the lifetime of struct (bsc#1267458).\n- CVE-2026-46069: wifi: mwifiex: fix use-after-free in mwifiex_adapter_cleanup() (bsc#1267437).\n- CVE-2026-46071: KVM: nSVM: Avoid clearing VMCB_LBR in vmcb12 (bsc#1267591).\n- CVE-2026-46076: KVM: nSVM: Raise #UD if unhandled VMMCALL isn't intercepted by L1 (bsc#1267365).\n- CVE-2026-46078: erofs: fix the out-of-bounds nameoff handling for trailing dirents (bsc#1267505).\n- CVE-2026-46079: rbd: fix null-ptr-deref when device_add_disk() fails (bsc#1266452).\n- CVE-2026-46091: media: rc: igorplugusb: heed coherency rules (bsc#1267238).\n- CVE-2026-46093: mm/vmalloc: take vmap_purge_lock in shrinker (bsc#1267548).\n- CVE-2026-46099: net: ipv6: fix NOREF dst use in seg6 and rpl lwtunnels (bsc#1266722).\n- CVE-2026-46101: netfilter: reject zero shift in nft_bitwise (bsc#1266878).\n- CVE-2026-46111: Bluetooth: hci_conn: fix potential UAF in create_big_sync (bsc#1267626).\n- CVE-2026-46112: RDMA/hns: Fix unlocked call to hns_roce_qp_remove() (bsc#1267582).\n- CVE-2026-46116: xfrm: defensively unhash xfrm_state lists in __xfrm_state_delete (bsc#1267369).\n- CVE-2026-46119: libceph: Fix slab-out-of-bounds access in auth message processing (bsc#1267628).\n- CVE-2026-46120: ip6_gre: Use cached t-\u003enet in ip6erspan_changelink() (bsc#1267640).\n- CVE-2026-46124: isofs: validate block number from NFS file handle in isofs_export_iget (bsc#1266847).\n- CVE-2026-46150: fanotify: fix false positive on permission events (bsc#1267387).\n- CVE-2026-46160: btrfs: fix missing last_unlink_trans update when removing a directory (bsc#1267624).\n- CVE-2026-46161: md/raid10: fix divide-by-zero in setup_geo() with zero far_copies (bsc#1266838).\n- CVE-2026-46162: ice: fix double free in ice_sf_eth_activate() error path (bsc#1266840).\n- CVE-2026-46172: ipv6: xfrm6: release dst on error in xfrm6_rcv_encap() (bsc#1266903).\n- CVE-2026-46173: exit: prevent preemption of oopsing TASK_DEAD task (bsc#1267722).\n- CVE-2026-46178: RDMA/mlx4: Fix resource leak on error in mlx4_ib_create_srq() (bsc#1267493).\n- CVE-2026-46185: smb/client: fix out-of-bounds read in symlink_data() (bsc#1266830).\n- CVE-2026-46214: vsock/virtio: fix accept queue count leak on transport mismatch (bsc#1267717).\n- CVE-2026-46227: sctp: revalidate list cursor after sctp_sendmsg_to_asoc() in SCTP_SENDALL (bsc#1267697).\n- CVE-2026-46242: eventpoll: Fix integer overflow in ep_loop_check_proc() (bsc#1267618).\n- CVE-2026-46244: netfilter: nft_inner: Fix IPv6 inner_thoff desync (bsc#1267654).\n- CVE-2026-46253: pstore/ram: fix buffer overflow in persistent_ram_save_old() (bsc#1267635).\n- CVE-2026-46254: AppArmor: Allow apparmor to handle unaligned dfa tables (bsc#1267637).\n- CVE-2026-46259: procfs: fix missing RCU protection when reading real_parent in do_task_stat() (bsc#1267685).\n- CVE-2026-46266: inet: RAW sockets using IPPROTO_RAW MUST drop incoming ICMP (bsc#1267684).\n- CVE-2026-46289: lib/scatterlist: fix length calculations in extract_kvec_to_sg (bsc#1267966).\n- CVE-2026-46291: printk: add print_hex_dump_devel() (bsc#1267937).\n- CVE-2026-46314: drm/v3d: Reject empty multisync extension to prevent infinite loop (bsc#1267992).\n- CVE-2026-46319: net/sched: act_ct: Only release RCU read lock after ct_ft (bsc#1268022).\n- CVE-2026-46320: tap: free page on error paths in tap_get_user_xdp() (bsc#1267993).\n- CVE-2026-46322: tun: free page on build_skb failure in tun_xdp_one() (bsc#1267994).\n- CVE-2026-46328: apparmor: fix rlimit for posix cpu timers (bsc#1268037).\n- CVE-2026-52908: RDMA: During rereg_mr ensure that REREG_ACCESS is compatible (bsc#1268661).\n- CVE-2026-52909: ip6_vti: set netns_immutable on the fallback device (bsc#1268660).\n- CVE-2026-52919: batman-adv: fix tp_meter counter underflow during shutdown (bsc#1269031).\n- CVE-2026-52923: ipc: limit next_id allocation to the valid ID range (bsc#1269033).\n- CVE-2026-52924: sctp: purge outqueue on stale COOKIE-ECHO handling (bsc#1269036).\n- CVE-2026-52933: io_uring/poll: fix signed comparison in io_poll_get_ownership() (bsc#1268989).\n- CVE-2026-52943: net: skbuff: fix missing zerocopy reference in pskb_carve helpers (bsc#1269022).\n- CVE-2026-52954: libceph: handle rbtree insertion error in decode_choose_args() (bsc#1269137).\n- CVE-2026-52955: libceph: Fix potential out-of-bounds access in crush_decode() (bsc#1269159).\n- CVE-2026-52957: libceph: Fix potential null-ptr-deref in decode_choose_args() (bsc#1269103).\n- CVE-2026-52962: ceph: fix a buffer leak in __ceph_setxattr() (bsc#1269135).\n- CVE-2026-52975: bonding: 3ad: implement proper RCU rules for port-\u003eaggregator (bsc#1269234).\n- CVE-2026-52980: sched/fair: Clear rel_deadline when initializing forked entities (bsc#1269252).\n- CVE-2026-52993: tipc: fix double-free in tipc_buf_append() (bsc#1269193).\n- CVE-2026-53015: erofs: unify lcn as u64 for 32-bit platforms (bsc#1269087).\n- CVE-2026-53021: scsi: target: core: Fix integer overflow in UNMAP bounds check (bsc#1269151).\n- CVE-2026-53036: bpf, arm64: Reject out-of-range B.cond targets (bsc#1269389).\n- CVE-2026-53039: ocfs2: validate group add input before caching (bsc#1269392).\n- CVE-2026-53040: ocfs2: validate bg_bits during freefrag scan (bsc#1269397).\n- CVE-2026-53041: ocfs2: fix listxattr handling when the buffer is full (bsc#1269398).\n- CVE-2026-53049: gfs2: add some missing log locking (bsc#1269646).\n- CVE-2026-53050: quota: Fix race of dquot_scan_active() with quota deactivation (bsc#1269188).\n- CVE-2026-53053: iommu/amd: Fix clone_alias() to use the original device's devid (bsc#1269310).\n- CVE-2026-53060: dm cache metadata: fix memory leak on metadata abort retry (bsc#1269164).\n- CVE-2026-53075: ppp: require CAP_NET_ADMIN in target netns for unattached ioctls (bsc#1269690).\n- CVE-2026-53078: bpf: Fix same-register dst/src OOB read and pointer leak in sock_ops (bsc#1269700).\n- CVE-2026-53081: bpf: Enforce regsafe base id consistency for BPF_ADD_CONST scalars (bsc#1269708).\n- CVE-2026-53086: net: bcmgenet: move DESC_INDEX flow to ring 0 (bsc#1269537).\n- CVE-2026-53090: bpf: Fix ld_{abs,ind} failure path analysis in subprogs (bsc#1269532).\n- CVE-2026-53103: wifi: mt76: mt7925: fix potential deadlock in mt7925_roc_abort_sync (bsc#1269416).\n- CVE-2026-53122: btrfs: fix deadlock between reflink and transaction commit when using flushoncommit (bsc#1269418).\n- CVE-2026-53133: RDMA/umem: Fix truncation for block sizes \u003e= 4G (bsc#1269821).\n- CVE-2026-53139: drm/v3d: Skip CSD when it has zeroed workgroups (bsc#1269262).\n- CVE-2026-53156: nvmem: core: fix use-after-free bugs in error paths (bsc#1269288).\n- CVE-2026-53167: fuse: limit FUSE_NOTIFY_RETRIEVE to uptodate folios (bsc#1269768).\n- CVE-2026-53168: fuse: reject fuse_notify() pagecache ops on directories (bsc#1269645).\n- CVE-2026-53176: IB/isert: Reject login PDUs shorter than ISER_HEADERS_LEN (bsc#1269710).\n- CVE-2026-53178: staging: rtl8723bs: rtw_mlme: add bounds checks before ie_length subtraction (bsc#1269795).\n- CVE-2026-53215: net: mvpp2: refill RX buffers before XDP or skb use (bsc#1269680).\n- CVE-2026-53216: net: mvpp2: limit XDP frame size to the RX buffer (bsc#1269587).\n- CVE-2026-53217: net: mvpp2: sync RX data at the hardware packet offset (bsc#1269989).\n- CVE-2026-53229: net/mlx5e: xsk: Fix DMA and xdp_frame leak on XDP_TX xmit failure (bsc#1269691).\n- CVE-2026-53249: ipv4: restrict IPOPT_SSRR and IPOPT_LSRR options (bsc#1269992).\n- CVE-2026-53258: wifi: fix leak if split 6 GHz scanning fails (bsc#1269230).\n- CVE-2026-53262: l2tp: pppol2tp: hold reference to session in pppol2tp_ioctl() (bsc#1270000).\n- CVE-2026-53263: 6lowpan: fix off-by-one in multicast context address compression (bsc#1269647).\n- CVE-2026-53266: netfilter: bridge: make ebt_snat ARP rewrite writable (bsc#1269136).\n- CVE-2026-53272: erofs: fix use-after-free on sbi-\u003esync_decompress (bsc#1269809).\n- CVE-2026-53274: net/smc: fix sleep-inside-lock in __smc_setsockopt() causing local DoS (bsc#1269651).\n- CVE-2026-53281: iommu/vt-d: Avoid NULL pointer dereference or refcount corruption (bsc#1269519).\n- CVE-2026-53285: drm/amd/display: Wrap DCN32 phantom-plane allocation in DC_RUN_WITH_PREEMPTION_ENABLED (bsc#1269527).\n- CVE-2026-53286: idpf: fix double free and use-after-free in aux device error paths (bsc#1269531).\n- CVE-2026-53287: audit: fix incorrect inheritable capability in CAPSET records (bsc#1269506).\n- CVE-2026-53306: tty: hvc_iucv: fix off-by-one in number of supported devices (bsc#1269814).\n\nThe following non security issues were fixed:\n\n- accel/ivpu: Fix signed integer truncation in IPC receive (git-fixes).\n- ACPI: CPPC: Suppress UBSAN warning caused by field misuse (git-fixes).\n- ACPI: IPMI: Fix inverted interface check in ipmi_bmc_gone() (git-fixes).\n- ACPI: IPMI: Fix message kref handling on dead device (git-fixes).\n- ACPI: NFIT: core: Fix possible NULL pointer dereference (git-fixes).\n- ACPI: resource: Amend kernel-doc style (git-fixes).\n- agp/amd64: Fix broken error propagation in agp_amd64_probe() (git-fixes).\n- ALSA: aloop: Drop superfluous break (git-fixes).\n- ALSA: caiaq: fix out-of-bounds read in the Traktor Kontrol S4 input parser (git-fixes).\n- ALSA: cmipci: check snd_ctl_new1() return value (git-fixes).\n- ALSA: core: Fix unintuitive behavior of snd_power_ref_and_wait() (git-fixes).\n- ALSA: es1938: check snd_ctl_new1() return value (git-fixes).\n- ALSA: firewire: isight: bound the sample count to the packet payload (git-fixes).\n- ALSA: gus: check snd_ctl_new1() return value (git-fixes).\n- ALSA: hda/cs35l41: Fix firmware load work teardown (git-fixes).\n- ALSA: ice1712: check snd_ctl_new1() return value (git-fixes).\n- ALSA: scarlett2: Allow flash writes ending at segment boundary (git-fixes).\n- ALSA: scarlett2: Return ENOSPC for out-of-bounds flash writes (stable-fixes).\n- ALSA: seq: Clear variable event pointer on read (git-fixes).\n- ALSA: seq: Fix kernel heap address leak in bounce_error_event() (git-fixes).\n- ALSA: seq: Fix partial userptr event expansion (git-fixes).\n- ALSA: seq: Fix uninitialised heap leak in snd_seq_event_dup() (git-fixes).\n- ALSA: seq: midi: Serialize output teardown with event_input (git-fixes).\n- ALSA: timer: Fix UAF at snd_timer_user_params() (stable-fixes).\n- ALSA: timer: Forcibly close timer instances at closing (git-fixes).\n- ALSA: usb-audio: avoid kobject path lookup in DualSense match (git-fixes).\n- ALSA: usb-audio: Kill MIDI 2.0 URBs before freeing endpoints (git-fixes).\n- ALSA: usb-audio: Propagate errors in scarlett_ctl_enum_put() (git-fixes).\n- ALSA: usb-audio: Propagate US-16x08 write errors in route/mix EQ-switch put callbacks (git-fixes).\n- ALSA: usb-audio: Roll back quirk control caches on write errors (git-fixes).\n- ALSA: usb-audio: Update Babyface Pro control caches only after successful writes (git-fixes).\n- ALSA: usb-audio: Update US-16x08 EQ/comp shadow state after successful writes (git-fixes).\n- ALSA: virtio: Add missing 384 kHz PCM rate mapping (git-fixes).\n- ALSA: virtio: Validate control metadata from the device (git-fixes).\n- ALSA: ymfpci: check snd_ctl_new1() return value (git-fixes).\n- arm64: scripts/sorttable: Implement sorting mcount_loc at boot for arm64 (bsc#1267600).\n- ASoC: adau1372: Clear PLL_EN on failed PLL lock without reset GPIO (git-fixes).\n- ASoC: amd: acp-sdw-sof: Bound DAI link iteration (git-fixes).\n- ASoC: codecs: aw88261: fix incorrect masks for boost regs (git-fixes).\n- ASoC: codecs: hdac_hdmi: Validate written enum value (git-fixes).\n- ASoC: cs35l56: Cleanup if component_probe fails (git-fixes).\n- ASoC: cs35l56: Don't leave parent IRQ disabled if system_suspend fails (git-fixes).\n- ASoC: cs35l56: Fix missing calls to wm_adsp2_remove() (git-fixes).\n- ASoC: cs35l56: Fix possible uninitialized value in cs35l56_spi_system_reset() (git-fixes).\n- ASoC: fsl: fsl_audmix: Validate written enum values (git-fixes).\n- ASoC: fsl_asrc_dma: fix eDMA maxburst misalignment with channel count (git-fixes).\n- ASoC: mediatek: mt8183: Release reserved memory on cleanup (git-fixes).\n- ASoC: mediatek: mt8192: Release reserved memory on cleanup (git-fixes).\n- ASoC: meson: aiu: Validate written enum values (git-fixes).\n- ASoC: qcom: q6apm: fix NULL pointer dereference in graph_callback (git-fixes).\n- ASoC: SOF: ipc3-control: Fix heap overflow in bytes_ext put/get (git-fixes).\n- ASoC: SOF: ipc3-control: Fix TOCTOU in bytes_put and bytes_get (git-fixes).\n- ASoC: SOF: ipc3-control: Use overflow checks in control_update size calc (git-fixes).\n- ASoC: SOF: ipc3-control: Validate size in snd_sof_update_control (git-fixes).\n- ASoC: SOF: ipc4-control: Fix TOCTOU in sof_ipc4_bytes_put (git-fixes).\n- ASoC: SOF: topology: validate vendor array size before parsing (git-fixes).\n- ASoC: tegra: tegra210_ahub: Validate written enum value (git-fixes).\n- ASoC: tlv320aic3x: restrict CLKDIV bypass Q values in dual-rate mode (git-fixes).\n- ASoC: topology: Check PCM and DAI name strings before use (git-fixes).\n- ASoC: wm_adsp: Fix NULL dereference when removing firmware controls (git-fixes).\n- Bluetooth: 6lowpan: hold L2CAP conn across debugfs control (git-fixes).\n- Bluetooth: bnep: pin L2CAP connection during netdev registration (git-fixes).\n- Bluetooth: bpa10x: avoid OOB read of revision string in bpa10x_setup() (git-fixes).\n- Bluetooth: btmtk: fix URB leak in alloc_mtk_intr_urb error path (git-fixes).\n- Bluetooth: btmtksdio: fix infinite loop in btmtksdio_txrx_work() (git-fixes).\n- Bluetooth: btnxpuart: Fix out-of-bounds firmware read in nxp_recv_fw_req_v3() (git-fixes).\n- Bluetooth: btusb: fix use-after-free on marvell probe failure (git-fixes).\n- Bluetooth: btusb: fix use-after-free on registration failure (git-fixes).\n- Bluetooth: btusb: fix wakeup irq devres lifetime (git-fixes).\n- Bluetooth: btusb: fix wakeup source leak on probe failure (git-fixes).\n- Bluetooth: eir: Fix stack OOB write when prepending the Flags AD (git-fixes).\n- Bluetooth: fix UAF in bt_accept_dequeue() (git-fixes).\n- Bluetooth: hci: validate codec capability element length (git-fixes).\n- Bluetooth: hci_core: Fix UAF in hci_unregister_dev() (git-fixes).\n- Bluetooth: hci_qca: fix NULL pointer dereference in qca_dmp_hdr() for non-serdev device (git-fixes).\n- Bluetooth: hci_uart: clear HCI_UART_SENDING when write_work is canceled (git-fixes).\n- Bluetooth: ISO: avoid NULL deref of conn in iso_conn_big_sync() (git-fixes).\n- Bluetooth: ISO: exclude RFU bits from ISO_SDU_Length (git-fixes).\n- Bluetooth: ISO: Fix data-race on iso_pi fields in hci_get_route calls (git-fixes).\n- Bluetooth: ISO: fix malformed ISO_END/CONT handling (git-fixes).\n- Bluetooth: ISO: Fix not using bc_sid as advertisement SID (stable-fixes).\n- Bluetooth: L2CAP: reject BR/EDR signaling packets over MTUsig (stable-fixes).\n- Bluetooth: L2CAP: validate option length before reading conf opt value (git-fixes).\n- Bluetooth: MGMT: Fix adv monitor add failure cleanup (git-fixes).\n- Bluetooth: MGMT: Fix UAF of hci_conn_params in add_device_complete (git-fixes).\n- Bluetooth: sco: Fix a race condition in sco_sock_timeout() (git-fixes).\n- Bluetooth: vhci: validate devcoredump state before side effects (git-fixes).\n- bnxt_en: Fix NULL pointer dereference (bsc#1268307).\n- bpf: Free reuseport cBPF prog after RCU grace period (git-fixes).\n- bus: mhi: ep: Add missing state_lock protection for mhi_state access (git-fixes).\n- bus: mhi: ep: Fix potential deadlock in mhi_ep_reset_worker() (git-fixes).\n- bus: mhi: ep: Protect mhi_ep_handle_syserr() in the error path (git-fixes).\n- char: tlclk: fix use-after-free in tlclk_cleanup() (git-fixes).\n- crypto/hmac: reject keys shorter than 128 bits in fips mode (bsc#1266284 jsc#PED-15986).\n- crypto/testmgr: disallow ffdhe2048 in fips mode (bsc#1266284 jsc#PED-15986).\n- crypto/testmgr: disallow plain ecb() usage in fips mode (bsc#1266284 jsc#PED-15986).\n- crypto/testmgr: disallow sha224 + sha3-224 in fips mode (bsc#1266284 jsc#PED-15986).\n- crypto: af_alg - Cap AEAD AD length to 0x80000000 (git-fixes).\n- crypto: amlogic - avoid double cleanup in meson_crypto_probe() (git-fixes).\n- crypto: asymmetric_keys - fix OOB read in pefile_digest_pe_contents (git-fixes).\n- crypto: atmel-sha204a - fix blocking and non-blocking rng logic (git-fixes).\n- crypto: cavium/cpt - fix DMA cleanup using wrong loop index (git-fixes).\n- crypto: ccp - Do not initialize SNP for ioctl(SNP_COMMIT) (git-fixes).\n- crypto: ccp - Do not initialize SNP for ioctl(SNP_VLEK_LOAD) (git-fixes).\n- crypto: ccp - Do not initialize SNP for SEV ioctls (git-fixes).\n- crypto: ccp - Fix snp_filter_reserved_mem_regions() off-by-one (git-fixes).\n- crypto: ccp - Treat zero-length cert chain as query for blob lengths (git-fixes).\n- crypto: drbg - Fix drbg_max_addtl() on 64-bit kernels (git-fixes).\n- crypto: drbg - Fix returning success on failure in CTR_DRBG (git-fixes).\n- crypto: drbg - Fix the fips_enabled priority boost (git-fixes).\n- crypto: ecc - Fix carry overflow in vli multiplication (git-fixes).\n- crypto: ecrdsa - fix unknown OID check in ecrdsa_param_curve (git-fixes).\n- crypto: hisilicon/qm - disable error report before flr (git-fixes).\n- crypto: marvell/octeontx - fix DMA cleanup using wrong loop index (git-fixes).\n- crypto: pcrypt - restore callback for non-parallel fallback (git-fixes).\n- crypto: qat - protect service table iterations with service_lock (git-fixes).\n- crypto: qat - validate RSA CRT component lengths (git-fixes).\n- crypto: rng - Free default RNG on module exit (git-fixes).\n- crypto: tegra - Fix dma_free_coherent size error (git-fixes).\n- crypto: tegra - fix refcount leak in tegra_se_host1x_submit() (git-fixes).\n- crypto: tegra - Return ENOMEM when input buffer allocation fails for ccm (git-fixes).\n- dm init: ensure device probing has finished in dm-mod.waitfor= (git-fixes).\n- dmaengine: dma-axi-dmac: Properly free struct axi_dmac_desc (git-fixes).\n- dmaengine: dma-axi-dmac: use DMA pool to manange DMA descriptor (git-fixes).\n- dmaengine: dw-edma: Add spinlock to protect DONE_INT_MASK and ABORT_INT_MASK (git-fixes).\n- dmaengine: Fix possible use after free (git-fixes).\n- dmaengine: imx-sdma: Refine spba bus searching in probe (git-fixes).\n- dmaengine: qcom: gpi: set DMA_PRIVATE capability (git-fixes).\n- dmaengine: tegra: Fix burst size calculation (git-fixes).\n- driver core: reject devices with unregistered buses (git-fixes).\n- driver core: use READ_ONCE() for dev-\u003edriver in dev_has_sync_state() (git-fixes).\n- Drivers: hv: vmbus: Improve the logic of reserving fb_mmio on Gen2 VMs (git-fixes).\n- drm/amd/display: add missing CSC entries for BT.2020 for DCE IPs (stable-fixes).\n- drm/amd/display: Add missing kdoc for ALLM parameters (git-fixes).\n- drm/amd/display: Clamp VBIOS HDMI retimer register count to array size (stable-fixes).\n- drm/amd/pm: fix smu13 power limit default/cap calculation (stable-fixes).\n- drm/amd/pm: mark metrics.energy_accumulator is invalid for smu 14.0.2 (stable-fixes).\n- drm/amd/pm: remove trailing semicolon from AMDGPU_PM_POLICY_ATTR macro (git-fixes).\n- drm/amd/pm: smu_v14_0_0: use SoftMin for gfxclk in set_soft_freq_limited_range (stable-fixes).\n- drm/amdgpu: Fix amdgpu_bo_move() when old_mem and new_mem are both GTT (git-fixes).\n- drm/amdgpu: fix integer overflow in amdgpu_gem_align_pitch() (git-fixes).\n- drm/amdgpu: initialize irq.lock spinlock earlier (git-fixes).\n- drm/amdgpu: restart the CS if some parts of the VM are still invalidated (stable-fixes).\n- drm/amdgpu: set sub_block_index for mca ras sub-blocks (git-fixes).\n- drm/amdgpu: skip already suspended IP blocks in ip_suspend_phase2 (git-fixes).\n- drm/amdgpu: validate CP_GFX_SHADOW chunk size in CS pass1 (git-fixes).\n- drm/amdkfd: always resume_all after suspend_all (git-fixes).\n- drm/amdkfd: Avoid double-unpin of DOORBELL/MMIO BOs on free (git-fixes).\n- drm/amdkfd: Check for pdd drm file first in CRIU restore path (stable-fixes).\n- drm/amdkfd: fix list_del corruption in kfd_criu_resume_svm (git-fixes).\n- drm/amdkfd: fix NULL pointer bug in svm_range_set_attr (stable-fixes).\n- drm/amdkfd: Use exclusive bounds for SVM split alignment checks (git-fixes).\n- drm/amdkfd: Validate CRIU-restored IDs before idr_alloc (git-fixes).\n- drm/bridge: cdns-dsi: Replace deprecated UNIVERSAL_DEV_PM_OPS() (git-fixes).\n- drm/dp/mst: fix buffer overflows in sideband chunk accumulation (git-fixes).\n- drm/dp/mst: fix OOB reads in remote DPCD/I2C sideband reply parsers (git-fixes).\n- drm/dp/mst: fix OOB reads on 2-byte fields in sideband reply parsers (git-fixes).\n- drm/dp: Add eDP 1.5 bit definition (stable-fixes).\n- drm/edid: fix OOB read in drm_parse_tiled_block() (git-fixes).\n- drm/gpuvm: Do not prepare NULL objects (git-fixes).\n- drm/hisilicon/hibmc: move display contrl config to hibmc_probe() (git-fixes).\n- drm/hisilicon/hibmc: use clock to look up the PLL value (git-fixes).\n- drm/hyperv: use VMBUS_RING_SIZE() (git-fixes).\n- drm/i915/gem: Add missing nospec on parallel submit slot (git-fixes).\n- drm/i915/gem: Fix phys BO pread/pwrite with offset (git-fixes).\n- drm/i915/psr: Add defininitions for INTEL_WA_REGISTER_CAPS DPCD register (stable-fixes).\n- drm/i915: clear CRTC color blob pointers after dropping refs (git-fixes).\n- drm/imagination: Count paired job fence as dependency in prepare_job() (git-fixes).\n- drm/imagination: Fit paired fragment job in the correct CCCB (git-fixes).\n- drm/msm/dp: fix HPD state status bit shift value (git-fixes).\n- drm/msm/dp: Fix the ISR_* enum values (git-fixes).\n- drm/nouveau/acr: fix missing nvkm_done() in error path of nvkm_acr_oneinit() (git-fixes).\n- drm/nouveau/bios: specify correct display fuse register for Ampere and Ada (git-fixes).\n- drm/nouveau: fix reversed error cleanup order in ucopy functions (git-fixes).\n- drm/panthor: Fix kernel-doc warning in panthor_sched.c (git-fixes).\n- drm/radeon: fix integer overflow in radeon_align_pitch() (git-fixes).\n- drm/radeon: fix memory leak in radeon_ring_restore() on lock failure (git-fixes).\n- drm/rockchip: cdn-dp: add missing check in cdn_dp_config_video() (git-fixes).\n- drm/rockchip: Test for imported buffers with drm_gem_is_imported() (git-fixes).\n- drm/syncobj: Fix memory leak in drm_syncobj_find_fence() (git-fixes).\n- drm/tegra: dc: Fix device node reference leak in tegra_dc_has_output() (git-fixes).\n- drm/tegra: Fix iommu_map_sgtable() return value check (git-fixes).\n- drm/tidss: Drop extra drm_mode_config_reset() call (git-fixes).\n- drm/tidss: Fix missing drm_bridge_add() call (git-fixes).\n- drm/vc4: fix krealloc() memory leak (git-fixes).\n- drm/virtio: fix dma_fence refcount leak on error in virtio_gpu_dma_fence_wait() (git-fixes).\n- drm/virtio: Fix driver removal with disabled KMS (git-fixes).\n- drm/xe: fix refcount leak in xe_range_fence_insert() (git-fixes).\n- drm: renesas: rzg2l_mipi_dsi: Increase reset deassertion delay (git-fixes).\n- fbdev: Fix fb_new_modelist to prevent null-ptr-deref in fb_videomode_to_var (stable-fixes).\n- fbdev: fix use-after-free in store_modes() (stable-fixes).\n- fbdev: modedb: fix a possible UAF in fb_find_mode() (stable-fixes).\n- fbdev: modedb: Fix misaligned fields in the 1920x1080-60 mode (git-fixes).\n- firmware: arm_scmi: Fix OOB in scmi_power_name_get() (git-fixes).\n- firmware: arm_scmi: Read sensor config as 32-bit value (git-fixes).\n- firmware_loader: fix device reference leak in firmware_upload_register() (git-fixes).\n- firmware_loader: Fix recursive lock in device_cache_fw_images() (git-fixes).\n- fpga: dfl: add bounds check in dfh_get_param_size() (git-fixes).\n- fpga: microchip-spi: fix zero header_size OOB read in mpf_ops_parse_header() (git-fixes).\n- fpga: region: fix use-after-free in child_regions_with_firmware() (git-fixes).\n- ftrace: Check against is_kernel_text() instead of kaslr_offset() (bsc#1267600).\n- ftrace: Do not over-allocate ftrace memory (bsc#1267600).\n- ftrace: Have ftrace pages output reflect freed pages (bsc#1267600).\n- ftrace: Test mcount_loc addr before calling ftrace_call_addr() (bsc#1267600).\n- ftrace: Update the mcount_loc check of skipped entries (bsc#1267600).\n- gpio: mvebu: fix NULL pointer dereference in suspend/resume (git-fixes).\n- gpio: mxc: fix irq_high handling (git-fixes).\n- gpio: rockchip: convert bank-\u003eclk to devm_clk_get_enabled() (git-fixes).\n- gpio: virtuser: Fix uninitialized data bug in gpio_virtuser_direction_do_write() (git-fixes).\n- gpio: zynq: fix runtime PM leak on remove (git-fixes).\n- gpiolib: Extract gpiochip_choose_fwnode() for wider use (stable-fixes).\n- gpiolib: Remove redundant assignment of return variable (stable-fixes).\n- gpu: host1x: Allow entries in BO caches to be freed (git-fixes).\n- gpu: host1x: Fix device reference leak in host1x_device_parse_dt() error path (git-fixes).\n- gpu: host1x: Fix iommu_map_sgtable() return value check (git-fixes).\n- HID: core: Add printk_ratelimited variants to hid_warn() etc (stable-fixes).\n- HID: hid-goodix-spi: validate report size to prevent stack buffer overflow (git-fixes).\n- HID: letsketch: fix UAF on inrange_timer at driver unbind (git-fixes).\n- HID: lg-g15: cancel pending work on remove to fix a use-after-free (git-fixes).\n- HID: logitech-hidpp: remove excess kernel-doc member in hidpp_scroll_counter (git-fixes).\n- HID: picolcd: prevent NULL pointer dereference in picolcd_send_and_wait() (git-fixes).\n- HID: quirks: Add ALWAYS_POLL quirk for SIGMACHIP USB mouse (stable-fixes).\n- HID: rate-limit hid_warn to prevent log flooding (stable-fixes).\n- HID: remove duplicate hid_warn_ratelimited definition (git-fixes).\n- HID: wacom: Fix OOB write in wacom_hid_set_device_mode() (git-fixes).\n- HID: wacom: stop hardware after post-start probe failures (git-fixes).\n- HID: wiimote: Fix table layout and whitespace errors (git-fixes).\n- hv: utils: handle and propagate errors in kvp_register (git-fixes).\n- hv: utils: replace deprecated strcpy with strscpy in kvp_register (git-fixes).\n- hv_balloon: Simplify data output in hv_balloon_debug_show() (git-fixes).\n- hv_netvsc: use kmap_local_page in netvsc_copy_to_send_buf (git-fixes).\n- hwmon: (aspeed-g6-pwm-tach) Guard fan RPM calculation against divide-by-zero (git-fixes).\n- hwmon: (asus_atk0110) Check package count before accessing element (git-fixes).\n- hwmon: (it87) Clamp negative values to zero in set_fan() (git-fixes).\n- hwmon: (ltc2992) add missing 'select REGMAP_I2C' to Kconfig (git-fixes).\n- hwmon: (max1619) add missing 'select REGMAP' to Kconfig (git-fixes).\n- hwmon: (max6697) add missing 'select REGMAP_I2C' to Kconfig (git-fixes).\n- hwmon: (occ) unregister sysfs devices outside occ lock (git-fixes).\n- hwmon: adm1275: Prevent reading uninitialized stack (git-fixes).\n- hwrng: jh7110 - fix refcount leak in starfive_trng_read() (git-fixes).\n- hwrng: virtio: clamp device-reported used.len at copy_data() (git-fixes).\n- hyperv: Clean up and fix the guest ID comment in hvgdk.h (git-fixes).\n- i2c: core: disable runtime PM on adapter registration failure (git-fixes).\n- i2c: core: fix adapter debugfs creation (git-fixes).\n- i2c: core: fix adapter deregistration race (git-fixes).\n- i2c: core: fix adapter probe deferral loop (git-fixes).\n- i2c: core: fix adapter registration race (git-fixes).\n- i2c: core: fix hang on adapter registration failure (git-fixes).\n- i2c: core: fix irq domain leak on adapter registration failure (git-fixes).\n- i2c: core: fix NULL-deref on adapter registration failure (git-fixes).\n- i2c: dev: prevent integer overflow in I2C_TIMEOUT ioctl (stable-fixes).\n- i2c: imx-lpi2c: mark I2C adapter when hardware is powered down (git-fixes).\n- i2c: mpc: Fix timeout calculations (git-fixes).\n- i2c: qcom-cci: Fix NULL pointer dereference in cci_remove() (git-fixes).\n- i2c: riic: fix refcount leak in riic_i2c_resume_noirq() (git-fixes).\n- i2c: stm32f7: fix timing computation ignoring i2c-analog-filter (git-fixes).\n- i2c: stm32f7: truncate clock period instead of rounding it (git-fixes).\n- i2c: tegra: Fix NOIRQ suspend/resume (git-fixes).\n- i3c: master: Prevent reuse of dynamic address on device add failure (git-fixes).\n- i3c: master: Serialize i3c_set_hotjoin() with the maintenance lock (git-fixes).\n- ice: ptp: don't WARN when controlling PF is unavailable (bsc#1267251).\n- iio: accel: mma8452: handle I2C read error(s) in mma8452_read() (git-fixes).\n- iio: adc: ti-ads1298: add bounds check to pga_settings index (stable-fixes).\n- iio: adc: xilinx-ams: fix out-of-bounds channel lookup in event handling (git-fixes).\n- iio: backend: fix uninitialized data in debugfs (git-fixes).\n- iio: chemical: scd30: Cleanup initializations and fix sign-extension bug (git-fixes).\n- iio: chemical: scd30: fix division by zero in write_raw (git-fixes).\n- iio: chemical: scd30: Use guard(mutex) to allow early returns (stable-fixes).\n- iio: gyro: bmg160: bail out when bandwidth/filter is not in table (git-fixes).\n- iio: gyro: bmg160: wait full startup time after mode change at probe (git-fixes).\n- iio: light: opt3001: fix missing state reset on timeout (git-fixes).\n- iio: light: si1133: prevent race condition on timeout (git-fixes).\n- iio: light: si1133: reset counter to prevent race condition (git-fixes).\n- iio: light: veml6030: fix channel type when pushing events (git-fixes).\n- iio: light: veml6075: add bounds check to veml6075_it_ms index (stable-fixes).\n- iio: magnetometer: ak8975: Add missed pm_runtime_put_autosuspend() call (git-fixes).\n- iio: resolver: ad2s1210: notify trigger and clear state on fault read error (git-fixes).\n- iio: tcs3472: power down chip on probe failure (git-fixes).\n- iio: temperature: ltc2983: Fix n_wires default bypassing rotation check (git-fixes).\n- iio: temperature: ltc2983: Fix reinit_completion() called after conversion start (git-fixes).\n- Input: atkbd - add DMI quirk for Lenovo Yoga Air 14 (83QK) (stable-fixes).\n- Input: elan_i2c - validate firmware size before use (stable-fixes).\n- Input: synaptics - add LEN2058 to SMBus passlist for ThinkPad E490 (stable-fixes).\n- Input: xpad - add \"Nova 2 Lite\" from GameSir (stable-fixes).\n- Input: xpad - add support for ASUS ROG RAIKIRI II (stable-fixes).\n- io_uring/cancel: de-unionize file and user_data in struct io_cancel_data (git-fixes bsc#1261250).\n- io_uring/filetable: clamp alloc_hint to the configured alloc range (git-fixes bsc#1261250).\n- io_uring/io-wq: fix incorrect io_wq_for_each_worker() termination logic (git-fixes bsc#1261250).\n- io_uring/poll: ensure EPOLL_ONESHOT is propagated for EPOLL_URING_WAKE (git-fixes bsc#1261250).\n- io_uring/wait: fix min_timeout behavior (git-fixes bsc#1261250).\n- io_uring/waitid: clear waitid info before copying it to userspace (git-fixes).\n- io_uring: fix min_wait wakeups for SQPOLL (git-fixes bsc#1261250).\n- ipv4: account for fraggap on the paged allocation path (git-fixes).\n- ipv6: account for fraggap on the paged allocation path (git-fixes).\n- KEYS: fix overflow in keyctl_pkey_params_get_2() (git-fixes).\n- KEYS: Use acquire when reading state in keyring search (git-fixes).\n- KVM: arm64: PMU: Preserve AArch32 counter low bits (git-fixes).\n- KVM: arm64: vgic: Free private_irqs when init fails after allocation (git-fixes).\n- KVM: Don't WARN if memory is dirtied without a vCPU when the VM is dying (git-fixes).\n- KVM: nSVM: Always use NextRIP as vmcb02's NextRIP after first L2 VMRUN (git-fixes).\n- KVM: nSVM: Always use vmcb01 in VMLOAD/VMSAVE emulation (git-fixes).\n- KVM: nSVM: Ensure AVIC is inhibited when restoring a vCPU to guest mode (git-fixes).\n- KVM: nSVM: Mark all of vmcb02 dirty when restoring nested state (git-fixes).\n- KVM: nSVM: Sync interrupt shadow to cached vmcb12 after VMRUN of L2 (git-fixes).\n- KVM: nSVM: Sync NextRIP to cached vmcb12 after VMRUN of L2 (git-fixes).\n- KVM: nVMX: Immediately refresh APICv controls as needed on nested VM-Exit (git-fixes).\n- KVM: Replace guest-triggerable BUG_ON() in ioeventfd datamatch with get_unaligned() (git-fixes).\n- KVM: SEV: Add an anonymous \"psc\" struct to track current PSC metadata (git-fixes).\n- KVM: SEV: Decouple the need to sync the GHCB SA from the need to free the SA (git-fixes).\n- KVM: SEV: Don't terminate SNP VMs on #VMGEXIT without a registered GHCB (git-fixes).\n- KVM: SEV: Make it more obvious when KVM is writing back the current PSC index (git-fixes).\n- KVM: SEV: Move sev_free_vcpu() down below sev_es_unmap_ghcb() (git-fixes).\n- KVM: SEV: Read start/end indices of PSC requests exactly once per #VMGEXIT (git-fixes).\n- KVM: SEV: Return INVALID_EVENT for SNP-only #VMGEXIT from non-SNP guest (git-fixes).\n- KVM: SEV: Return INVALID_INPUT, not MISSING_INPUT, for bad GUEST_REQUEST input(s) (git-fixes).\n- KVM: SEV: Unmap and unpin the GHCB as needed on vCPU free (git-fixes).\n- KVM: SVM: Allow KVM_SET_NESTED_STATE to clear GIF when SVME==0 (git-fixes).\n- KVM: SVM: check validity of VMCB controls when returning from SMM (git-fixes).\n- KVM: SVM: Don't set GIF when clearing EFER.SVME (git-fixes).\n- KVM: SVM: Truncate INVLPGA address in compatibility mode (git-fixes).\n- KVM: Use vCPU specific memslots in __kvm_vcpu_map() (git-fixes).\n- KVM: VMX: Grab vmcs12 on CR8 interception update iff vCPU is in guest mode (git-fixes).\n- KVM: VMX: Read 32-bit GPR values for ENCLS instructions outside of 64-bit mode (git-fixes).\n- KVM: x86/mmu: Ensure hugepage is in by slot before checking max mapping level (git-fixes).\n- KVM: x86/mmu: Recursively zap orphaned nested TDP shadow pages on emulated writes (git-fixes).\n- KVM: x86/xen: Bug the VM if 32-bit KVM observes a 64-bit mode hypercall (git-fixes).\n- KVM: x86/xen: Don't truncate RAX when handling hypercall from protected guest (git-fixes).\n- KVM: x86: Consolidate CPUID fault handling for emulator and interception logic (git-fixes).\n- KVM: x86: Fix shadow paging use-after-free due to unexpected role (git-fixes).\n- KVM: x86: hyper-v: Bound the bank index when querying sparse banks (git-fixes).\n- KVM: x86: ioapic: Use old_dest_mode consistently in ioapic_write_indirect() (git-fixes).\n- KVM: x86: Move update_cr8_intercept() to lapic.c (git-fixes).\n- KVM: x86: Prioritize CPUID faulting over CPUID VM-exits in nested VMX (git-fixes).\n- KVM: x86: Trace hypercall register *after* truncating values for 32-bit (git-fixes).\n- KVM: x86: Unconditionally recompute CR8 intercept on PPR update (git-fixes).\n- mailbox: imx: Forward the timeout/ error in imx_mu_generic_tx() (git-fixes).\n- mailbox: mtk-adsp: fix UAF during device teardown (git-fixes).\n- misc: fastrpc: fix DMA address corruption due to find_vma misuse (git-fixes).\n- misc: fastrpc: Fix NULL pointer dereference in rpmsg callback (git-fixes).\n- misc: fastrpc: fix use-after-free of fastrpc_user in workqueue context (git-fixes).\n- misc: fastrpc: fix use-after-free race in fastrpc_map_create (git-fixes).\n- mm/vmstat: defer the refresh_zone_stat_thresholds after all CPUs bringup (bsc#1270042).\n- mtd: maps: vmu-flash: fix NULL pointer dereference in initialization (git-fixes).\n- mtd: rawnand: fix condition in 'nand_select_target()' (git-fixes).\n- mtd: rawnand: Pause continuous reads at block boundaries (git-fixes).\n- mtd: rawnand: pl353: fix probe resource allocation (git-fixes).\n- mtd: slram: remove failed entries from the device list (git-fixes).\n- mtd: spi-nor: Drop duplicate Kconfig dependency (git-fixes).\n- mtd: spi-nor: macronix: Add post_sfdp fixups for Quad Input Page Program (stable-fixes).\n- mtd: spi-nor: macronix: add support for mx66{l2, u1}g45g (stable-fixes).\n- mtd: spi-nor: spansion: use die erase for multi-die devices only (git-fixes).\n- mtd: spi-nor: swp: Improve locking user experience (git-fixes).\n- net: aquantia: Add missing descriptor cache invalidation on ATL2 (bsc#1268428).\n- net: ethtool: add ethtool COALESCE_RX_CQE_FRAMES/NSECS (bsc#1261256).\n- net: mana: Add ethtool counters for RX CQEs in coalesced type (bsc#1261256).\n- net: mana: Add support for PF device 0x00C1 (bsc#1268237).\n- net: mana: Add support for RX CQE Coalescing (bsc#1261256).\n- net: mana: Allocate interrupt context for each EQ when creating vPort (git-fixes).\n- net: mana: Cache MANA_QUERY_LINK_CONFIG result to avoid repeated HWC queries (bsc#1268238).\n- net: mana: Create separate EQs for each vPort (git-fixes).\n- net: mana: Fall back to standard MTU when PF reports adapter_mtu of 0 (git-fixes).\n- net: mana: guard TX wq object destroy with INVALID_MANA_HANDLE check (git-fixes).\n- net: mana: initialize gdma queue id to INVALID_QUEUE_ID (git-fixes).\n- net: mana: Introduce GIC context with refcounting for interrupt management (git-fixes).\n- net: mana: Optimize irq affinity for low vcpu configs (git-fixes).\n- net: mana: Query device capabilities and configure MSI-X sharing for EQs (git-fixes).\n- net: mana: Sync page pool RX frags for CPU (git-fixes).\n- net: mana: Use GIC functions to allocate global EQs (git-fixes).\n- net: mana: Validate the packet length reported by the NIC (git-fixes).\n- net: phy: sfp: free mii_bus in sfp_i2c_mdiobus_destroy (git-fixes).\n- net: usb: lan78xx: disable VLAN filter in promiscuous mode (git-fixes).\n- net: usb: net1080: validate packet_len before pad-byte access in rx_fixup (git-fixes).\n- net: wwan: iosm: bound device offsets in the MUX downlink decoder (git-fixes).\n- nfc: hci: fix out-of-bounds read in HCP header parsing (git-fixes).\n- nfc: llcp: Fix use-after-free in llcp_sock_release() (git-fixes).\n- nfc: llcp: Fix use-after-free race in nfc_llcp_recv_cc() (git-fixes).\n- packaging: Add nvidia kernel description.\n- packaging: compute-PATCHVERSION.sh -\u003e compute-PATCHVERSION.\n- page_pool: Fix PP_MAGIC_MASK to avoid crashing on some 32-bit arches (bsc#1261562).\n- page_pool: Move pp_magic check into helper functions (bsc#1261562).\n- page_pool: Track DMA-mapped pages and unmap them when destroying the pool (bsc#1261562).\n- PCI: Update saved_config_space upon resource assignment (git-fixes).\n- perf/x86/intel/uncore: Fix die ID init and look up bugs (bsc#1267419).\n- perf/x86/intel/uncore: Skip discovery table for offline dies (bsc#1267419).\n- platform/x86: dell-laptop: fix missing cleanups in init error path (git-fixes).\n- platform/x86: intel-hid: Protect ACPI notify handler against recursion (git-fixes).\n- platform/x86: xo15-ebook: Fix wakeup source and GPE handling (git-fixes).\n- PM: sleep: Use complete() in device_pm_sleep_init() (git-fixes).\n- power: reset: linkstation-poweroff: fix use-after-free in the linkstation_poweroff_init() (git-fixes).\n- power: supply: charger-manager: fix refcount leak in is_full_charged() (git-fixes).\n- power: supply: core: fix supplied_from allocations (git-fixes).\n- power: supply: cpcap-battery: Fix missing nvmem_device_put() causing reference leak (git-fixes).\n- powerpc/boot: Allow text relocations for pseries wrapper with binutils 2.46+ (git-fixes).\n- powerpc/fadump: define MIN_RMA in bytes rather than MB (bsc#1236743 git-fixes).\n- ppc/fadump: invoke kmsg_dump in fadump panic path (bsc#1270226 ltc#218302).\n- pwm: imx27: Fix variable truncation in .apply() (git-fixes).\n- RDMA/mana_ib: Allocate interrupt contexts on EQs (git-fixes).\n- RDMA/mana_ib: Use ib_get_eth_speed for reporting port speed (git-fixes).\n- regulator: scmi: fix of_node refcount leak in scmi_regulator_probe() (git-fixes).\n- Revert \"fs: don't block i_writecount during exec\" (bsc#1269982).\n- rtc: abx80x: fix the RTC_VL_CLR clearing all status flags (git-fixes).\n- rtc: cmos: unregister HPET IRQ handler on probe failure (git-fixes).\n- rtc: ds1307: Fix off-by-one issue with wday for rx8130 (git-fixes).\n- rtc: ds1307: handle oscillator stop flag for ds1337/ds1339/ds3231 (git-fixes).\n- rtc: mpfs: fix counter upload completion condition (git-fixes).\n- rtc: msc313: fix NULL deref in shared IRQ handler at probe (git-fixes).\n- scripts/sorttable: Add helper functions for Elf_Ehdr (bsc#1267600).\n- scripts/sorttable: Add helper functions for Elf_Shdr (bsc#1267600).\n- scripts/sorttable: Add helper functions for Elf_Sym (bsc#1267600).\n- scripts/sorttable: Allow matches to functions before function entry (bsc#1267600).\n- scripts/sorttable: Always use an array for the mcount_loc sorting (bsc#1267600).\n- scripts/sorttable: Convert Elf_Ehdr to union (bsc#1267600).\n- scripts/sorttable: Convert Elf_Sym MACRO over to a union (bsc#1267600).\n- scripts/sorttable: Fix endianness handling in build-time mcount sort (bsc#1267600).\n- scripts/sorttable: Get start/stop_mcount_loc from ELF file directly (bsc#1267600).\n- scripts/sorttable: Have mcount rela sort use direct values (bsc#1267600).\n- scripts/sorttable: Have the ORC code use the _r() functions to read (bsc#1267600).\n- scripts/sorttable: Make compare_extable() into two functions (bsc#1267600).\n- scripts/sorttable: Move code from sorttable.h into sorttable.c (bsc#1267600).\n- scripts/sorttable: Remove unneeded Elf_Rel (bsc#1267600).\n- scripts/sorttable: Remove unused macro defines (bsc#1267600).\n- scripts/sorttable: Remove unused write functions (bsc#1267600).\n- scripts/sorttable: Replace Elf_Shdr Macro with a union (bsc#1267600).\n- scripts/sorttable: Use a structure of function pointers for elf helpers (bsc#1267600).\n- scripts/sorttable: Use normal sort if theres no relocs in the mcount section (bsc#1267600).\n- scripts/sorttable: Use uint64_t for mcount sorting (bsc#1267600).\n- scripts/sorttable: Zero out weak functions in mcount_loc table (bsc#1267600).\n- scsi: smartpqi: Use shost_to_hba() in pqi_scan_finished() (bsc#1257506).\n- scsi: storvsc: Replace symbolic permissions with octal (git-fixes).\n- scsi: target: Fix hexadecimal CHAP_I handling (git-fixes).\n- selftests/bpf: Add BPF_STRICT_BUILD toggle (poo#202224).\n- selftests/bpf: Allow test_progs to link with a partial object set (poo#202224).\n- selftests/bpf: Avoid rebuilds when running emit_tests (poo#202224).\n- selftests/bpf: Consolidate kernel modules into common directory (poo#202224).\n- selftests/bpf: Copy test_kmods when installing selftest (poo#202224).\n- selftests/bpf: Fix runqslower cross-endian build (poo#202224).\n- selftests/bpf: Fix test_kmods KDIR to honor O= and distro kernels (poo#202224).\n- selftests/bpf: make BPF_TARGET_ENDIAN non-recursive to speed up *.bpf.o build (poo#202224).\n- selftests/bpf: Make skeleton headers order-only prerequisites of .test.d (poo#202224).\n- selftests/bpf: Provide weak definitions for cross-test functions (poo#202224).\n- selftests/bpf: Skip tests whose objects were not built (poo#202224).\n- selftests/bpf: Support cross-endian building (poo#202224).\n- selftests/bpf: Tolerate benchmark build failures (poo#202224).\n- selftests/bpf: Tolerate BPF and skeleton generation failures (poo#202224).\n- selftests/bpf: Tolerate missing files during install (poo#202224).\n- selftests/bpf: Tolerate test file compilation failures (poo#202224).\n- serial: 8250: dispatch SysRq character in serial8250_handle_irq() (git-fixes).\n- serial: 8250_dw: dispatch SysRq character in dw8250_handle_irq() (git-fixes).\n- serial: qcom_geni: Fix RX DMA stall when SE_DMA_RX_LEN_IN is zero (git-fixes).\n- slimbus: qcom-ngd-ctrl: Avoid ABBA on tx_lock/ctrl-\u003elock (git-fixes).\n- slimbus: qcom-ngd-ctrl: Balance pm_runtime enablement for NGD (git-fixes).\n- slimbus: qcom-ngd-ctrl: Correct PDR and SSR cleanup ownership (git-fixes).\n- slimbus: qcom-ngd-ctrl: fix OF node refcount (git-fixes).\n- slimbus: qcom-ngd-ctrl: Fix probe error path ordering (git-fixes).\n- slimbus: qcom-ngd-ctrl: Fix up platform_driver registration (git-fixes).\n- slimbus: qcom-ngd-ctrl: Initialize controller resources in controller (git-fixes).\n- slimbus: qcom-ngd-ctrl: Register callbacks after creating the ngd (git-fixes).\n- soc: qcom: ice: Fix race between qcom_ice_probe() and of_qcom_ice_get() (git-fixes).\n- soc: qcom: ice: Return -ENODEV if the ICE platform device is not found (git-fixes).\n- spi: at91-usart: drop dead runtime pm support (git-fixes).\n- spi: dw: fix wrong BAUDR setting after resume (git-fixes).\n- spi: ep93xx: fix double-free of zeropage on DMA setup failure (git-fixes).\n- spi: fsl-lpspi: replace dmaengine_terminate_all() with dmaengine_terminate_sync() (git-fixes).\n- spi: fsl-lpspi: terminate the RX channel on TX prepare failure path (git-fixes).\n- spi: hisi-kunpeng: Use dev_err_probe() for host registration failure (git-fixes).\n- spi: meson-spifc: fix runtime PM leak on remove (git-fixes).\n- spi: rpc-if: Use correct device for hardware reinitialization on resume (git-fixes).\n- spi: uniphier: Fix completion initialization order before devm_request_irq() (git-fixes).\n- spi: xilinx: use FIFO occupancy register to determine buffer size (git-fixes).\n- Split off kABI workaround for bsc#1267458 (bsc#1267458).\n- staging: most: video: avoid double free on video register failure (git-fixes).\n- staging: nvec: fix use-after-free in nvec_rx_completed() (git-fixes).\n- thermal: hwmon: Fix critical temperature attribute removal (git-fixes).\n- thermal: intel: Fix dangling resources on thermal_throttle_online() failure (git-fixes).\n- thermal: testing: reject missing command arguments (git-fixes).\n- thermal: testing: zone: Flush work items during cleanup (git-fixes).\n- thunderbolt: Bound root directory content to block size (git-fixes).\n- thunderbolt: Clamp XDomain response data copy to allocation size (git-fixes).\n- thunderbolt: debugfs: Don't stop reading SB registers if just one fails (git-fixes).\n- thunderbolt: debugfs: Fix margining error counter buffer leak (git-fixes).\n- thunderbolt: Limit XDomain response copy to actual frame size (git-fixes).\n- thunderbolt: Reject zero-length property entries in validator (git-fixes).\n- thunderbolt: Validate XDomain request packet size before type cast (git-fixes).\n- tools/power/x86/intel-speed-select: Harden daemon pidfile open (git-fixes).\n- tpm: fix event_size output in tpm1_binary_bios_measurements_show (git-fixes).\n- tpm: tpm2-sessions: wait for async KPP completion in tpm_buf_append_salt (git-fixes).\n- tpm: tpm_tis_spi: Use wait_woken() in wait_for_tmp_stat() (git-fixes).\n- usb: core: Fix SuperSpeed root hub wMaxPacketSize (stable-fixes).\n- usb: core: Fix up Interrupt IN endpoints with bogus wBytesPerInterval (stable-fixes).\n- usb: host: max3421: Fix shift-out-of-bounds in max3421_hub_control() (git-fixes).\n- usb: host: max3421: Reject hub port requests for non-existent ports (git-fixes).\n- USB: quirks: add NO_LPM for Lenovo ThinkPad USB-C Dock Gen2 hub controllers (git-fixes).\n- USB: serial: io_ti: fix heap overflow in build_i2c_fw_hdr() (git-fixes).\n- USB: serial: io_ti: fix heap overflow in get_manuf_info() (git-fixes).\n- USB: serial: kl5kusb105: fix bulk-out buffer overflow (git-fixes).\n- USB: serial: option: add usb-id for Dell Wireless DW5826e-m (stable-fixes).\n- usb: storage: Add quirks for PNY Elite Portable SSD (git-fixes).\n- usb: typec: altmodes/displayport: validate count before reading Status Update VDO (stable-fixes).\n- usb: typec: tcpm/tcpci_maxim: validate header NDO against RX_BYTE_CNT (stable-fixes).\n- usb: typec: tcpm: bound altmode_desc[] per iteration in svdm_consume_modes() (stable-fixes).\n- usb: typec: tcpm: validate VDO count in Discover Identity ACK handlers (stable-fixes).\n- usb: typec: ucsi: ccg: reject firmware images without a ':' record header (stable-fixes).\n- usb: typec: ucsi: displayport: NAK DP_CMD_CONFIGURE without a payload VDO (stable-fixes).\n- usb: typec: ucsi: validate connector number in ucsi_connector_change() (stable-fixes).\n- usb: typec: wcove: don't write past struct pd_message in wcove_read_rx_buffer() (stable-fixes).\n- usbnet: gl620a: fix out-of-bounds read in genelink_rx_fixup() (git-fixes).\n- vc_screen: fix null-ptr-deref in vcs_notifier() during concurrent vcs_write (git-fixes).\n- watchdog/hpwdt: Refine hpwdt message for UV platform (bsc#1269199).\n- watchdog: apple: Add \"apple,t8103-wdt\" compatible (git-fixes).\n- watchdog: sama5d4_wdt: Fix WDDIS detection on SAM9X60 and SAMA7G5 (git-fixes).\n- watchdog: sp5100_tco: Use EFCH MMIO for newer Hygon FCH (git-fixes).\n- watchdog: sprd_wdt: Remove redundant sprd_wdt_disable() on register failure (git-fixes).\n- watchdog: unregister PM notifier on watchdog unregister (git-fixes).\n- wifi: ath9k: fix OOB access from firmware tx status queue ID (git-fixes).\n- wifi: ath11k: fix warning when unbinding (git-fixes).\n- wifi: cfg80211: fix grammar in MLO group key error message (git-fixes).\n- wifi: iwlwifi: mvm: fix race condition in PTP removal (stable-fixes).\n- wifi: mac80211: fix monitor mode frame capture for real chanctx drivers (git-fixes).\n- wifi: mt76: fix argument to ieee80211_is_first_frag() (git-fixes).\n- wifi: mt76: mt76x2u: Add support for ELECOM WDC-867SU3S (stable-fixes).\n- wifi: mt76: mt792x: skip MLD header rewrite for 802.3 encap TX (git-fixes).\n- wifi: mt76: mt7915: fix potential tx_retries underflow (git-fixes).\n- wifi: mt76: mt7921: avoid undesired changes of the preset regulatory domain (stable-fixes).\n- wifi: mt76: mt7921: fix a potential scan no APs (stable-fixes).\n- wifi: mt76: mt7921: fix potential tx_retries underflow (git-fixes).\n- wifi: mt76: mt7925: clean up DMA on probe failure (git-fixes).\n- wifi: mt76: mt7925: don't disable AP BSS when removing TDLS peer (git-fixes).\n- wifi: mt76: mt7925: fix potential tx_retries underflow (git-fixes).\n- wifi: mt76: mt7925: fix stale pointer comparisons in change_vif_links (git-fixes).\n- wifi: mt76: mt7925: keep TX BA state in the primary WCID (git-fixes).\n- wifi: mt76: mt7996: fix potential tx_retries underflow (git-fixes).\n- wifi: rtlwifi: rtl8821ae: Fix C2H bit location in RX descriptor (git-fixes).\n- wifi: rtw88: fix OOB read from firmware RX descriptor exceeding DMA buffer (git-fixes).\n- wifi: rtw88: increase TX report timeout to fix race condition (git-fixes).\n- wifi: rtw88: usb: fix memory leaks on USB write failures (git-fixes).\n- wifi: rtw89: Correct data type for scan index to avoid infinite loop (git-fixes).\n- wifi: wcn36xx: fix heap overflow from oversized firmware HAL response (git-fixes).\n- wifi: wcn36xx: fix OOB read from firmware count in PRINT_REG_INFO indication (git-fixes).\n- wifi: wcn36xx: fix OOB read from short trigger BA firmware response (git-fixes).\n- x86/cpu/amd: Correct the microcode table for Zenbleed (git-fixes).\n- x86/cpu: Disable FRED when PTI is forced on (git-fixes).\n- x86/cpu: Properly parse CPUID leaf 0x2 TLB descriptor 0x63 (git-fixes).\n- x86/cpu: Validate CPUID leaf 0x2 EDX output (git-fixes).\n- x86/irq: Ensure initial PIR loads are performed exactly once (git-fixes).\n- x86/platform/uv: Expose the uv_hub_type() interface (jsc#PED-16390).\n- x86/tsc: Disable clocksource watchdog checking on recent and future UV platforms (jsc#PED-16390).\n- X.509: Fix validation of ASN.1 certificate header (git-fixes).\n- xfrm: Fix dev use-after-free in xfrm async resumption (bsc#1268276).\n","status":"published","published":"2026-07-21T08:27:33Z","modified":"2026-07-28T18:24:06.778434145Z","updated_at":"2026-11-02T15:54:03.080707Z"},{"id":"SUSE-SU-2026:22835-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-10263: arm64: cputype: Add C1-Premium definitions (bsc#1266290).\n- CVE-2025-39894: netfilter: br_netfilter: do not check confirmed bit\n  in br_nf_local_in() after confirm (bsc#1262430).\n- CVE-2025-40341: futex: Don't leak robust_list pointer on exec race (bsc#1255029).\n- CVE-2026-23248: perf: Make perf_pmu_unregister() useable (bsc#1259800).\n- CVE-2026-23394: Revert: \"af_unix: Remove lock dance in unix_peek_fds().\" (bsc#1260565).\n- CVE-2026-23451: bonding: prevent potential infinite loop in bond_header_parse() (bsc#1261604).\n- CVE-2026-31414: netfilter: nf_conntrack_expect: use expect-\u003ehelper (bsc#1262085).\n- CVE-2026-31429: net: skb: fix cross-cache free of KFENCE-allocated skb head (bsc#1262392).\n- CVE-2026-31438: netfs: Fix kernel BUG in netfs_limit_iter() for ITER_KVEC iterators (bsc#1267824).\n- CVE-2026-31450: ext4: publish jinode after initialization (bsc#1262618).\n- CVE-2026-31452: ext4: convert inline data to extents when truncate exceeds inline size (bsc#1262620).\n- CVE-2026-31466: mm/huge_memory: fix folio isn't locked in softleaf_to_folio() (bsc#1267825).\n- CVE-2026-31469: virtio_net: Fix UAF on dst_ops when IFF_XMIT_DST_RELEASE is cleared and napi_tx is false\n  (bsc#1267816).\n- CVE-2026-31479: drm/xe: always keep track of remap prev/next (bsc#1262765).\n- CVE-2026-31492: RDMA/irdma: Initialize free_qp completion before using it (bsc#1262748).\n- CVE-2026-31495: netfilter: ctnetlink: use netlink policy range checks (bsc#1262798).\n- CVE-2026-31499: Bluetooth: L2CAP: Fix deadlock in l2cap_conn_del() (bsc#1262674).\n- CVE-2026-31502: team: fix header_ops type confusion with non-Ethernet ports (bsc#1263072).\n- CVE-2026-31555: futex: Clear stale exiting pointer in futex_lock_pi() retry path (bsc#1263178).\n- CVE-2026-31560: spi: spi-dw-dma: fix print error log when wait finish transaction (bsc#1263057).\n- CVE-2026-31596: ocfs2: handle invalid dinode in ocfs2_group_extend (bsc#1263319).\n- CVE-2026-31646: net: lan966x: fix page_pool error handling in lan966x_fdma_rx_alloc_page_pool() (bsc#1263796).\n- CVE-2026-31647: idpf: fix PREEMPT_RT raw/bh spinlock nesting for async VC handling (bsc#1263581).\n- CVE-2026-31663: xfrm: hold device only for the asynchronous decryption (bsc#1263133).\n- CVE-2026-31664: xfrm: clear trailing padding in build_polexpire() (bsc#1263578).\n- CVE-2026-31665: netfilter: nft_ct: fix use-after-free in timeout object destroy (bsc#1263137).\n- CVE-2026-31670: net: rfkill: prevent unlimited numbers of rfkill events from being created (bsc#1263573).\n- CVE-2026-31673: af_unix: read UNIX_DIAG_VFS data under unix_state_lock (bsc#1263143).\n- CVE-2026-31674: netfilter: ip6t_rt: reject oversized addrnr in rt_mt6_check() (bsc#1263568).\n- CVE-2026-31680: net: ipv6: flowlabel: defer exclusive option free until RCU teardown (bsc#1263563).\n- CVE-2026-31693: cifs: some missing initializations on replay (bsc#1267744).\n- CVE-2026-31743: nvmem: zynqmp_nvmem: Fix buffer size in DMA and memcpy (bsc#1264067).\n- CVE-2026-31752: bridge: br_nd_send: validate ND option lengths (bsc#1264045).\n- CVE-2026-31771: Bluetooth: hci_event: move wake reason storage into validated event handlers (bsc#1264145).\n- CVE-2026-43010: bpf: Reject sleepable kprobe_multi programs at attach time (bsc#1264015).\n- CVE-2026-43014,CVE-2026-43015: net: macb: fix clk handling on PCI glue driver removal (bsc#1264010 bsc#1264012).\n- CVE-2026-43016: bpf: sockmap: Fix use-after-free of sk-\u003esk_socket in sk_psock_verdict_data_ready() (bsc#1264007).\n- CVE-2026-43022: Bluetooth: hci_sync: hci_cmd_sync_queue_once() return -EEXIST if exists (bsc#1264001).\n- CVE-2026-43024: netfilter: nf_tables: reject immediate NF_QUEUE verdict (bsc#1263930).\n- CVE-2026-43028: netfilter: x_tables: ensure names are nul-terminated (bsc#1263934).\n- CVE-2026-43034: bnxt_en: set backing store type from query type (bsc#1263998).\n- CVE-2026-43035: net: sched: cls_api: fix tc_chain_fill_node to\n  initialize tcm_info to zero to prevent an info-leak (bsc#1263996).\n- CVE-2026-43036: net: use skb_header_pointer() for TCPv4 GSO frag_off check (bsc#1263993).\n- CVE-2026-43053: xfs: factor out xfs_attr3_node_entry_remove (bsc#1264084).\n- CVE-2026-43057: net: correctly handle tunneled traffic on IPV6_CSUM GSO fallback (bsc#1264056).\n- CVE-2026-43074: eventpoll: defer struct eventpoll free to RCU grace period (bsc#1264263).\n- CVE-2026-43080: l2tp: Drop large packets with UDP encap (bsc#1264236).\n- CVE-2026-43081: net: ipa: fix GENERIC_CMD register field masks for IPA v5.0+ (bsc#1264241).\n- CVE-2026-43083: net: ioam6: fix OOB and missing lock (bsc#1264266).\n- CVE-2026-43085: netfilter: nfnetlink_log: initialize nfgenmsg in NLMSG_DONE terminator (bsc#1264230).\n- CVE-2026-43086: ipvs: fix NULL deref in ip_vs_add_service error path (bsc#1264286).\n- CVE-2026-43089: xfrm_user: fix info leak in build_mapping() (bsc#1264261).\n- CVE-2026-43090: xfrm: fix refcount leak in xfrm_migrate_policy_find (bsc#1264250).\n- CVE-2026-43092: xsk: validate MTU against usable frame size on bind (bsc#1264270).\n- CVE-2026-43093: xsk: tighten UMEM headroom validation to account for tailroom and min frame (bsc#1264254).\n- CVE-2026-43094: ixgbevf: add missing negotiate_features op to Hyper-V ops table (bsc#1264231).\n- CVE-2026-43101: ipv6: ioam: fix potential NULL dereferences in __ioam6_fill_trace_data() (bsc#1264239).\n- CVE-2026-43107: xfrm: account XFRMA_IF_ID in aevent size calculation (bsc#1264258).\n- CVE-2026-43119: Bluetooth: hci_sync: annotate data-races around hdev-\u003ereq_status (bsc#1264561).\n- CVE-2026-43124: pstore: ram_core: fix incorrect success return when vmap() fails (bsc#1264545).\n- CVE-2026-43128: RDMA/umem: Fix double dma_buf_unpin in failure path (bsc#1264612).\n- CVE-2026-43130: iommu/vt-d: Flush dev-IOTLB only when PCIe device is accessible in scalable mode (bsc#1264532).\n- CVE-2026-43132: dm-verity: correctly handle dm_bufio_client_create() failure (bsc#1264614).\n- CVE-2026-43139: xfrm6: fix uninitialized saddr in xfrm6_get_saddr() (bsc#1264294).\n- CVE-2026-43145: remoteproc: imx_rproc: Fix invalid loaded resource table detection (bsc#1265091).\n- CVE-2026-43157: octeontx2-af: CGX: fix bitmap leaks (bsc#1264624).\n- CVE-2026-43158: xfs: fix freemap adjustments when adding xattrs to leaf blocks (bsc#1264595).\n- CVE-2026-43161: iommu/vt-d: Skip dev-iotlb flush for inaccessible PCIe device without scalable mode (bsc#1264333).\n- CVE-2026-43167: xfrm: always flush state and policy upon NETDEV_UNREGISTER event (bsc#1264580).\n- CVE-2026-43171: EFI/CPER: don't dump the entire memory region (bsc#1264549).\n- CVE-2026-43175: clk: rs9: Reserve 8 struct clk_hw slots for for 9FGV0841 (bsc#1264372).\n- CVE-2026-43187: xfs: delete attr leaf freemap entries when empty (bsc#1264603).\n- CVE-2026-43191: drm/amd/display: Adjust PHY FSM transition to TX_EN-to-PLL_ON for TMDS on DCN35 (bsc#1264548).\n- CVE-2026-43194: net: consume xmit errors of GSO frames (bsc#1264304).\n- CVE-2026-43198: tcp: fix potential race in tcp_v6_syn_recv_sock() (bsc#1264610).\n- CVE-2026-43199: net/mlx5e: Fix \"scheduling while atomic\" in IPsec MAC address query (bsc#1264556).\n- CVE-2026-43205: dpaa2-switch: validate num_ifs to prevent out-of-bounds write (bsc#1264328).\n- CVE-2026-43213: wifi: rtw89: pci: validate sequence number of TX release report (bsc#1264643).\n- CVE-2026-43226: net/rds: No shortcut out of RDS_CONN_ERROR (bsc#1264544).\n- CVE-2026-43233: netfilter: nf_conntrack_h323: fix OOB read in decode_choice() (bsc#1264337).\n- CVE-2026-43238: net/sched: act_skbedit: fix divide-by-zero in tcf_skbedit_hash() (bsc#1264320).\n- CVE-2026-43240: ima: verify the previous kernel's IMA buffer lies in addressable RAM (bsc#1264386).\n- CVE-2026-43248: vhost: move vdpa group bound check to vhost_vdpa (bsc#1264302).\n- CVE-2026-43260: bnxt_en: Fix RSS context delete logic (bsc#1264429).\n- CVE-2026-43283: net: ethernet: ec_bhf: Fix dma_free_coherent() dma handle (bsc#1264295).\n- CVE-2026-43298: drm/amdgpu: Skip vcn poison irq release on VF (bsc#1264852).\n- CVE-2026-43303: mm/page_alloc: clear page-\u003eprivate in free_pages_prepare() (bsc#1264974).\n- CVE-2026-43336: lib/crypto: chacha: Zeroize permuted_state before it leaves scope (bsc#1265113).\n- CVE-2026-43337: drm/amd/display: Fix NULL pointer dereference in dcn401_init_hw() (bsc#1265112).\n- CVE-2026-43339: ipv6: prevent possible UaF in addrconf_permanent_addr() (bsc#1264763).\n- CVE-2026-43345: net: ipa: fix event ring index not programmed for IPA v5.0+ (bsc#1265103).\n- CVE-2026-43351: KVM: arm64: gic: Set vgic_model before initing private IRQs (bsc#1265082).\n- CVE-2026-43373: net: ncsi: fix skb leak in error paths (bsc#1265079).\n- CVE-2026-43374: net: nexthop: fix percpu use-after-free in remove_nh_grp_entry (bsc#1265084).\n- CVE-2026-43383: net/tcp-md5: Fix MAC comparison to be constant-time (bsc#1264744).\n- CVE-2026-43384: net/tcp-ao: Fix MAC comparison to be constant-time (bsc#1265097).\n- CVE-2026-43386: staging: rtl8723bs: fix potential out-of-bounds read in rtw_restruct_wmm_ie (bsc#1264740).\n- CVE-2026-43403: nsfs: tighten permission checks for ns iteration ioctls (bsc#1265129).\n- CVE-2026-43405: libceph: Use u32 for non-negative values in ceph_monmap_decode() (bsc#1264741).\n- CVE-2026-43406: libceph: prevent potential out-of-bounds reads in process_message_header() (bsc#1265073).\n- CVE-2026-43407: libceph: Fix potential out-of-bounds access in ceph_handle_auth_reply() (bsc#1265020).\n- CVE-2026-43415: scsi: ufs: core: Fix SError in ufshcd_rtc_work() during UFS suspend (bsc#1265123).\n- CVE-2026-43449: nvme-pci: Fix slab-out-of-bounds in nvme_dbbuf_set (bsc#1265023).\n- CVE-2026-43450: netfilter: nfnetlink_cthelper: fix OOB read in nfnl_cthelper_dump_table() (bsc#1264794).\n- CVE-2026-43452: netfilter: x_tables: guard option walkers against 1-byte tail reads (bsc#1265142).\n- CVE-2026-43456: bonding: fix type confusion in bond_setup_by_slave() (bsc#1264734).\n- CVE-2026-43457: mctp: i2c: fix skb memory leak in receive path (bsc#1265000).\n- CVE-2026-43458: serial: caif: hold tty-\u003elink reference in ldisc_open and ser_release (bsc#1265005).\n- CVE-2026-43465: net/mlx5e: RX, Fix XDP multi-buf frag counting for striding RQ (bsc#1264997).\n- CVE-2026-43466: net/mlx5e: Fix DMA FIFO desync on error CQE SQ recovery (bsc#1264790).\n- CVE-2026-43468: net/mlx5: Fix deadlock between devlink lock and esw-\u003ewq (bsc#1264978).\n- CVE-2026-43469: xprtrdma: Decrement re_receiving on the early exit paths (bsc#1265143).\n- CVE-2026-43470: nfs: return EISDIR on nfs3_proc_create if d_alias is a dir (bsc#1265128).\n- CVE-2026-43471: scsi: ufs: core: Fix possible NULL pointer dereference in ufshcd_add_command_trace() (bsc#1264789).\n- CVE-2026-43491: net: qrtr: ns: Limit the maximum server registration per node (bsc#1265628).\n- CVE-2026-43492: lib/crypto: mpi: Fix integer underflow in mpi_read_raw_from_sgl() (bsc#1265629).\n- CVE-2026-43502: net/rds: handle zerocopy send cleanup before the message is queued (bsc#1266008).\n- CVE-2026-45837: Require (reasonably) normal mappings for MADV_DOFORK (bsc#1266398).\n- CVE-2026-45838: bpf: fix end-of-list detection in cgroup_storage_get_next_key() (bsc#1266396).\n- CVE-2026-45840: openvswitch: cap upcall PID array size and pre-size vport replies (bsc#1266397).\n- CVE-2026-45841: netfilter: nfnetlink_osf: fix divide-by-zero in OSF_WSS_MODULO (bsc#1266390).\n- CVE-2026-45848: apparmor: fix NULL sock in aa_sock_file_perm (bsc#1266734).\n- CVE-2026-45857: scsi: csiostor: Fix dereference of null pointer rn (bsc#1266458).\n- CVE-2026-45858: ext4: don't zero the entire extent if EXT4_EXT_DATA_PARTIAL_VALID1 (bsc#1266773).\n- CVE-2026-45861: gfs2: Fix slab-use-after-free in qd_put (bsc#1266754).\n- CVE-2026-45862: iommu/vt-d: Flush cache for PASID table before using it (bsc#1266705).\n- CVE-2026-45870: SUNRPC: auth_gss: fix memory leaks in XDR decoding error paths (bsc#1266704).\n- CVE-2026-45884: apparmor: avoid per-cpu hold underflow in aa_get_buffer (bsc#1266718).\n- CVE-2026-45888: md/raid1: fix memory leak in raid1_run() (bsc#1266761).\n- CVE-2026-45891: net: hns3: fix double free issue for tx spare buffer (bsc#1266717).\n- CVE-2026-45894: iommu/vt-d: Clear Present bit before tearing down PASID entry (bsc#1266895).\n- CVE-2026-45899: ext4: drop extent cache when splitting extent fails (bsc#1266883).\n- CVE-2026-45901: netfilter: nf_tables: revert commit_mutex usage in reset path (bsc#1266892).\n- CVE-2026-45912: ext4: don't cache extent during splitting extent (bsc#1266899).\n- CVE-2026-45920: ext4: fix dirtyclusters double decrement on fs shutdown (bsc#1266893).\n- CVE-2026-45922: RDMA/mlx5: Fix memory leak in GET_DATA_DIRECT_SYSFS_PATH handler (bsc#1266805).\n- CVE-2026-45933: bpf: Preserve id of register in sync_linked_regs() (bsc#1266693).\n- CVE-2026-45940: net: stmmac: fix oops when split header is enabled (bsc#1266916).\n- CVE-2026-45948: ext4: fix memory leak in ext4_ext_shift_extents() (bsc#1266929).\n- CVE-2026-45961: gfs2: fix memory leaks in gfs2_fill_super error path (bsc#1266933).\n- CVE-2026-45964: SUNRPC: fix gss_auth kref leak in gss_alloc_msg error path (bsc#1266698).\n- CVE-2026-45965: apparmor: fix invalid deref of rawdata when export_binary is unset (bsc#1267208).\n- CVE-2026-45974: btrfs: fix invalid leaf access in btrfs_quota_enable() if ref key not found (bsc#1266922).\n- CVE-2026-45983: nfsd: never defer requests during idmap lookup (bsc#1266697).\n- CVE-2026-45985: ext4: don't set EXT4_GET_BLOCKS_CONVERT when splitting before submitting I/O (bsc#1266700).\n- CVE-2026-45997: scsi: sd: fix missing put_disk() when device_add(\u0026disk_dev) fails (bsc#1266740).\n- CVE-2026-45999: erofs: fix unsigned underflow in z_erofs_lz4_handle_overlap() (bsc#1266750).\n- CVE-2026-46005: xfs: fix a resource leak in xfs_alloc_buftarg() (bsc#1267431).\n- CVE-2026-46024: libceph: Prevent potential null-ptr-deref in ceph_handle_auth_reply() (bsc#1267218).\n- CVE-2026-46037: ipv4: icmp: validate reply type before using icmp_pointers (bsc#1267361).\n- CVE-2026-46046: ext4: fix missing brelse() in ext4_xattr_inode_dec_ref_all() (bsc#1266726).\n- CVE-2026-46050: md/raid10: fix deadlock with check operation and nowait requests (bsc#1266686).\n- CVE-2026-46051: md/raid5: fix soft lockup in retry_aligned_read() (bsc#1267360).\n- CVE-2026-46053: net: rds: fix MR cleanup on copy error (bsc#1267427).\n- CVE-2026-46063: x86/shstk: Prevent deadlock during shstk sigreturn (bsc#1267228).\n- CVE-2026-46065: fbdev: defio: Disconnect deferred I/O from the lifetime of struct (bsc#1267458).\n- CVE-2026-46069: wifi: mwifiex: fix use-after-free in mwifiex_adapter_cleanup() (bsc#1267437).\n- CVE-2026-46071: KVM: nSVM: Avoid clearing VMCB_LBR in vmcb12 (bsc#1267591).\n- CVE-2026-46076: KVM: nSVM: Raise #UD if unhandled VMMCALL isn't intercepted by L1 (bsc#1267365).\n- CVE-2026-46078: erofs: fix the out-of-bounds nameoff handling for trailing dirents (bsc#1267505).\n- CVE-2026-46079: rbd: fix null-ptr-deref when device_add_disk() fails (bsc#1266452).\n- CVE-2026-46091: media: rc: igorplugusb: heed coherency rules (bsc#1267238).\n- CVE-2026-46093: mm/vmalloc: take vmap_purge_lock in shrinker (bsc#1267548).\n- CVE-2026-46099: net: ipv6: fix NOREF dst use in seg6 and rpl lwtunnels (bsc#1266722).\n- CVE-2026-46101: netfilter: reject zero shift in nft_bitwise (bsc#1266878).\n- CVE-2026-46111: Bluetooth: hci_conn: fix potential UAF in create_big_sync (bsc#1267626).\n- CVE-2026-46112: RDMA/hns: Fix unlocked call to hns_roce_qp_remove() (bsc#1267582).\n- CVE-2026-46116: xfrm: defensively unhash xfrm_state lists in __xfrm_state_delete (bsc#1267369).\n- CVE-2026-46119: libceph: Fix slab-out-of-bounds access in auth message processing (bsc#1267628).\n- CVE-2026-46120: ip6_gre: Use cached t-\u003enet in ip6erspan_changelink() (bsc#1267640).\n- CVE-2026-46124: isofs: validate block number from NFS file handle in isofs_export_iget (bsc#1266847).\n- CVE-2026-46150: fanotify: fix false positive on permission events (bsc#1267387).\n- CVE-2026-46160: btrfs: fix missing last_unlink_trans update when removing a directory (bsc#1267624).\n- CVE-2026-46161: md/raid10: fix divide-by-zero in setup_geo() with zero far_copies (bsc#1266838).\n- CVE-2026-46162: ice: fix double free in ice_sf_eth_activate() error path (bsc#1266840).\n- CVE-2026-46172: ipv6: xfrm6: release dst on error in xfrm6_rcv_encap() (bsc#1266903).\n- CVE-2026-46173: exit: prevent preemption of oopsing TASK_DEAD task (bsc#1267722).\n- CVE-2026-46178: RDMA/mlx4: Fix resource leak on error in mlx4_ib_create_srq() (bsc#1267493).\n- CVE-2026-46185: smb/client: fix out-of-bounds read in symlink_data() (bsc#1266830).\n- CVE-2026-46214: vsock/virtio: fix accept queue count leak on transport mismatch (bsc#1267717).\n- CVE-2026-46227: sctp: revalidate list cursor after sctp_sendmsg_to_asoc() in SCTP_SENDALL (bsc#1267697).\n- CVE-2026-46242: eventpoll: Fix integer overflow in ep_loop_check_proc() (bsc#1267618).\n- CVE-2026-46244: netfilter: nft_inner: Fix IPv6 inner_thoff desync (bsc#1267654).\n- CVE-2026-46253: pstore/ram: fix buffer overflow in persistent_ram_save_old() (bsc#1267635).\n- CVE-2026-46254: AppArmor: Allow apparmor to handle unaligned dfa tables (bsc#1267637).\n- CVE-2026-46259: procfs: fix missing RCU protection when reading real_parent in do_task_stat() (bsc#1267685).\n- CVE-2026-46266: inet: RAW sockets using IPPROTO_RAW MUST drop incoming ICMP (bsc#1267684).\n- CVE-2026-46289: lib/scatterlist: fix length calculations in extract_kvec_to_sg (bsc#1267966).\n- CVE-2026-46291: printk: add print_hex_dump_devel() (bsc#1267937).\n- CVE-2026-46314: drm/v3d: Reject empty multisync extension to prevent infinite loop (bsc#1267992).\n- CVE-2026-46319: net/sched: act_ct: Only release RCU read lock after ct_ft (bsc#1268022).\n- CVE-2026-46320: tap: free page on error paths in tap_get_user_xdp() (bsc#1267993).\n- CVE-2026-46322: tun: free page on build_skb failure in tun_xdp_one() (bsc#1267994).\n- CVE-2026-46328: apparmor: fix rlimit for posix cpu timers (bsc#1268037).\n- CVE-2026-52908: RDMA: During rereg_mr ensure that REREG_ACCESS is compatible (bsc#1268661).\n- CVE-2026-52909: ip6_vti: set netns_immutable on the fallback device (bsc#1268660).\n- CVE-2026-52919: batman-adv: fix tp_meter counter underflow during shutdown (bsc#1269031).\n- CVE-2026-52923: ipc: limit next_id allocation to the valid ID range (bsc#1269033).\n- CVE-2026-52924: sctp: purge outqueue on stale COOKIE-ECHO handling (bsc#1269036).\n- CVE-2026-52933: io_uring/poll: fix signed comparison in io_poll_get_ownership() (bsc#1268989).\n- CVE-2026-52943: net: skbuff: fix missing zerocopy reference in pskb_carve helpers (bsc#1269022).\n- CVE-2026-52954: libceph: handle rbtree insertion error in decode_choose_args() (bsc#1269137).\n- CVE-2026-52955: libceph: Fix potential out-of-bounds access in crush_decode() (bsc#1269159).\n- CVE-2026-52957: libceph: Fix potential null-ptr-deref in decode_choose_args() (bsc#1269103).\n- CVE-2026-52962: ceph: fix a buffer leak in __ceph_setxattr() (bsc#1269135).\n- CVE-2026-52975: bonding: 3ad: implement proper RCU rules for port-\u003eaggregator (bsc#1269234).\n- CVE-2026-52980: sched/fair: Clear rel_deadline when initializing forked entities (bsc#1269252).\n- CVE-2026-52993: tipc: fix double-free in tipc_buf_append() (bsc#1269193).\n- CVE-2026-53015: erofs: unify lcn as u64 for 32-bit platforms (bsc#1269087).\n- CVE-2026-53021: scsi: target: core: Fix integer overflow in UNMAP bounds check (bsc#1269151).\n- CVE-2026-53036: bpf, arm64: Reject out-of-range B.cond targets (bsc#1269389).\n- CVE-2026-53039: ocfs2: validate group add input before caching (bsc#1269392).\n- CVE-2026-53040: ocfs2: validate bg_bits during freefrag scan (bsc#1269397).\n- CVE-2026-53041: ocfs2: fix listxattr handling when the buffer is full (bsc#1269398).\n- CVE-2026-53049: gfs2: add some missing log locking (bsc#1269646).\n- CVE-2026-53050: quota: Fix race of dquot_scan_active() with quota deactivation (bsc#1269188).\n- CVE-2026-53053: iommu/amd: Fix clone_alias() to use the original device's devid (bsc#1269310).\n- CVE-2026-53060: dm cache metadata: fix memory leak on metadata abort retry (bsc#1269164).\n- CVE-2026-53075: ppp: require CAP_NET_ADMIN in target netns for unattached ioctls (bsc#1269690).\n- CVE-2026-53078: bpf: Fix same-register dst/src OOB read and pointer leak in sock_ops (bsc#1269700).\n- CVE-2026-53081: bpf: Enforce regsafe base id consistency for BPF_ADD_CONST scalars (bsc#1269708).\n- CVE-2026-53086: net: bcmgenet: move DESC_INDEX flow to ring 0 (bsc#1269537).\n- CVE-2026-53090: bpf: Fix ld_{abs,ind} failure path analysis in subprogs (bsc#1269532).\n- CVE-2026-53103: wifi: mt76: mt7925: fix potential deadlock in mt7925_roc_abort_sync (bsc#1269416).\n- CVE-2026-53122: btrfs: fix deadlock between reflink and transaction commit when using flushoncommit (bsc#1269418).\n- CVE-2026-53133: RDMA/umem: Fix truncation for block sizes \u003e= 4G (bsc#1269821).\n- CVE-2026-53139: drm/v3d: Skip CSD when it has zeroed workgroups (bsc#1269262).\n- CVE-2026-53156: nvmem: core: fix use-after-free bugs in error paths (bsc#1269288).\n- CVE-2026-53167: fuse: limit FUSE_NOTIFY_RETRIEVE to uptodate folios (bsc#1269768).\n- CVE-2026-53168: fuse: reject fuse_notify() pagecache ops on directories (bsc#1269645).\n- CVE-2026-53176: IB/isert: Reject login PDUs shorter than ISER_HEADERS_LEN (bsc#1269710).\n- CVE-2026-53178: staging: rtl8723bs: rtw_mlme: add bounds checks before ie_length subtraction (bsc#1269795).\n- CVE-2026-53215: net: mvpp2: refill RX buffers before XDP or skb use (bsc#1269680).\n- CVE-2026-53216: net: mvpp2: limit XDP frame size to the RX buffer (bsc#1269587).\n- CVE-2026-53217: net: mvpp2: sync RX data at the hardware packet offset (bsc#1269989).\n- CVE-2026-53229: net/mlx5e: xsk: Fix DMA and xdp_frame leak on XDP_TX xmit failure (bsc#1269691).\n- CVE-2026-53249: ipv4: restrict IPOPT_SSRR and IPOPT_LSRR options (bsc#1269992).\n- CVE-2026-53258: wifi: fix leak if split 6 GHz scanning fails (bsc#1269230).\n- CVE-2026-53262: l2tp: pppol2tp: hold reference to session in pppol2tp_ioctl() (bsc#1270000).\n- CVE-2026-53263: 6lowpan: fix off-by-one in multicast context address compression (bsc#1269647).\n- CVE-2026-53266: netfilter: bridge: make ebt_snat ARP rewrite writable (bsc#1269136).\n- CVE-2026-53272: erofs: fix use-after-free on sbi-\u003esync_decompress (bsc#1269809).\n- CVE-2026-53274: net/smc: fix sleep-inside-lock in __smc_setsockopt() causing local DoS (bsc#1269651).\n- CVE-2026-53281: iommu/vt-d: Avoid NULL pointer dereference or refcount corruption (bsc#1269519).\n- CVE-2026-53285: drm/amd/display: Wrap DCN32 phantom-plane allocation in DC_RUN_WITH_PREEMPTION_ENABLED (bsc#1269527).\n- CVE-2026-53286: idpf: fix double free and use-after-free in aux device error paths (bsc#1269531).\n- CVE-2026-53287: audit: fix incorrect inheritable capability in CAPSET records (bsc#1269506).\n- CVE-2026-53306: tty: hvc_iucv: fix off-by-one in number of supported devices (bsc#1269814).\n\nThe following non security issues were fixed:\n\n- accel/ivpu: Fix signed integer truncation in IPC receive (git-fixes).\n- ACPI: CPPC: Suppress UBSAN warning caused by field misuse (git-fixes).\n- ACPI: IPMI: Fix inverted interface check in ipmi_bmc_gone() (git-fixes).\n- ACPI: IPMI: Fix message kref handling on dead device (git-fixes).\n- ACPI: NFIT: core: Fix possible NULL pointer dereference (git-fixes).\n- ACPI: resource: Amend kernel-doc style (git-fixes).\n- agp/amd64: Fix broken error propagation in agp_amd64_probe() (git-fixes).\n- ALSA: aloop: Drop superfluous break (git-fixes).\n- ALSA: caiaq: fix out-of-bounds read in the Traktor Kontrol S4 input parser (git-fixes).\n- ALSA: cmipci: check snd_ctl_new1() return value (git-fixes).\n- ALSA: core: Fix unintuitive behavior of snd_power_ref_and_wait() (git-fixes).\n- ALSA: es1938: check snd_ctl_new1() return value (git-fixes).\n- ALSA: firewire: isight: bound the sample count to the packet payload (git-fixes).\n- ALSA: gus: check snd_ctl_new1() return value (git-fixes).\n- ALSA: hda/cs35l41: Fix firmware load work teardown (git-fixes).\n- ALSA: ice1712: check snd_ctl_new1() return value (git-fixes).\n- ALSA: scarlett2: Allow flash writes ending at segment boundary (git-fixes).\n- ALSA: scarlett2: Return ENOSPC for out-of-bounds flash writes (stable-fixes).\n- ALSA: seq: Clear variable event pointer on read (git-fixes).\n- ALSA: seq: Fix kernel heap address leak in bounce_error_event() (git-fixes).\n- ALSA: seq: Fix partial userptr event expansion (git-fixes).\n- ALSA: seq: Fix uninitialised heap leak in snd_seq_event_dup() (git-fixes).\n- ALSA: seq: midi: Serialize output teardown with event_input (git-fixes).\n- ALSA: timer: Fix UAF at snd_timer_user_params() (stable-fixes).\n- ALSA: timer: Forcibly close timer instances at closing (git-fixes).\n- ALSA: usb-audio: avoid kobject path lookup in DualSense match (git-fixes).\n- ALSA: usb-audio: Kill MIDI 2.0 URBs before freeing endpoints (git-fixes).\n- ALSA: usb-audio: Propagate errors in scarlett_ctl_enum_put() (git-fixes).\n- ALSA: usb-audio: Propagate US-16x08 write errors in route/mix EQ-switch put callbacks (git-fixes).\n- ALSA: usb-audio: Roll back quirk control caches on write errors (git-fixes).\n- ALSA: usb-audio: Update Babyface Pro control caches only after successful writes (git-fixes).\n- ALSA: usb-audio: Update US-16x08 EQ/comp shadow state after successful writes (git-fixes).\n- ALSA: virtio: Add missing 384 kHz PCM rate mapping (git-fixes).\n- ALSA: virtio: Validate control metadata from the device (git-fixes).\n- ALSA: ymfpci: check snd_ctl_new1() return value (git-fixes).\n- arm64: scripts/sorttable: Implement sorting mcount_loc at boot for arm64 (bsc#1267600).\n- ASoC: adau1372: Clear PLL_EN on failed PLL lock without reset GPIO (git-fixes).\n- ASoC: amd: acp-sdw-sof: Bound DAI link iteration (git-fixes).\n- ASoC: codecs: aw88261: fix incorrect masks for boost regs (git-fixes).\n- ASoC: codecs: hdac_hdmi: Validate written enum value (git-fixes).\n- ASoC: cs35l56: Cleanup if component_probe fails (git-fixes).\n- ASoC: cs35l56: Don't leave parent IRQ disabled if system_suspend fails (git-fixes).\n- ASoC: cs35l56: Fix missing calls to wm_adsp2_remove() (git-fixes).\n- ASoC: cs35l56: Fix possible uninitialized value in cs35l56_spi_system_reset() (git-fixes).\n- ASoC: fsl: fsl_audmix: Validate written enum values (git-fixes).\n- ASoC: fsl_asrc_dma: fix eDMA maxburst misalignment with channel count (git-fixes).\n- ASoC: mediatek: mt8183: Release reserved memory on cleanup (git-fixes).\n- ASoC: mediatek: mt8192: Release reserved memory on cleanup (git-fixes).\n- ASoC: meson: aiu: Validate written enum values (git-fixes).\n- ASoC: qcom: q6apm: fix NULL pointer dereference in graph_callback (git-fixes).\n- ASoC: SOF: ipc3-control: Fix heap overflow in bytes_ext put/get (git-fixes).\n- ASoC: SOF: ipc3-control: Fix TOCTOU in bytes_put and bytes_get (git-fixes).\n- ASoC: SOF: ipc3-control: Use overflow checks in control_update size calc (git-fixes).\n- ASoC: SOF: ipc3-control: Validate size in snd_sof_update_control (git-fixes).\n- ASoC: SOF: ipc4-control: Fix TOCTOU in sof_ipc4_bytes_put (git-fixes).\n- ASoC: SOF: topology: validate vendor array size before parsing (git-fixes).\n- ASoC: tegra: tegra210_ahub: Validate written enum value (git-fixes).\n- ASoC: tlv320aic3x: restrict CLKDIV bypass Q values in dual-rate mode (git-fixes).\n- ASoC: topology: Check PCM and DAI name strings before use (git-fixes).\n- ASoC: wm_adsp: Fix NULL dereference when removing firmware controls (git-fixes).\n- Bluetooth: 6lowpan: hold L2CAP conn across debugfs control (git-fixes).\n- Bluetooth: bnep: pin L2CAP connection during netdev registration (git-fixes).\n- Bluetooth: bpa10x: avoid OOB read of revision string in bpa10x_setup() (git-fixes).\n- Bluetooth: btmtk: fix URB leak in alloc_mtk_intr_urb error path (git-fixes).\n- Bluetooth: btmtksdio: fix infinite loop in btmtksdio_txrx_work() (git-fixes).\n- Bluetooth: btnxpuart: Fix out-of-bounds firmware read in nxp_recv_fw_req_v3() (git-fixes).\n- Bluetooth: btusb: fix use-after-free on marvell probe failure (git-fixes).\n- Bluetooth: btusb: fix use-after-free on registration failure (git-fixes).\n- Bluetooth: btusb: fix wakeup irq devres lifetime (git-fixes).\n- Bluetooth: btusb: fix wakeup source leak on probe failure (git-fixes).\n- Bluetooth: eir: Fix stack OOB write when prepending the Flags AD (git-fixes).\n- Bluetooth: fix UAF in bt_accept_dequeue() (git-fixes).\n- Bluetooth: hci: validate codec capability element length (git-fixes).\n- Bluetooth: hci_core: Fix UAF in hci_unregister_dev() (git-fixes).\n- Bluetooth: hci_qca: fix NULL pointer dereference in qca_dmp_hdr() for non-serdev device (git-fixes).\n- Bluetooth: hci_uart: clear HCI_UART_SENDING when write_work is canceled (git-fixes).\n- Bluetooth: ISO: avoid NULL deref of conn in iso_conn_big_sync() (git-fixes).\n- Bluetooth: ISO: exclude RFU bits from ISO_SDU_Length (git-fixes).\n- Bluetooth: ISO: Fix data-race on iso_pi fields in hci_get_route calls (git-fixes).\n- Bluetooth: ISO: fix malformed ISO_END/CONT handling (git-fixes).\n- Bluetooth: ISO: Fix not using bc_sid as advertisement SID (stable-fixes).\n- Bluetooth: L2CAP: reject BR/EDR signaling packets over MTUsig (stable-fixes).\n- Bluetooth: L2CAP: validate option length before reading conf opt value (git-fixes).\n- Bluetooth: MGMT: Fix adv monitor add failure cleanup (git-fixes).\n- Bluetooth: MGMT: Fix UAF of hci_conn_params in add_device_complete (git-fixes).\n- Bluetooth: sco: Fix a race condition in sco_sock_timeout() (git-fixes).\n- Bluetooth: vhci: validate devcoredump state before side effects (git-fixes).\n- bnxt_en: Fix NULL pointer dereference (bsc#1268307).\n- bpf: Free reuseport cBPF prog after RCU grace period (git-fixes).\n- bus: mhi: ep: Add missing state_lock protection for mhi_state access (git-fixes).\n- bus: mhi: ep: Fix potential deadlock in mhi_ep_reset_worker() (git-fixes).\n- bus: mhi: ep: Protect mhi_ep_handle_syserr() in the error path (git-fixes).\n- char: tlclk: fix use-after-free in tlclk_cleanup() (git-fixes).\n- crypto/hmac: reject keys shorter than 128 bits in fips mode (bsc#1266284 jsc#PED-15986).\n- crypto/testmgr: disallow ffdhe2048 in fips mode (bsc#1266284 jsc#PED-15986).\n- crypto/testmgr: disallow plain ecb() usage in fips mode (bsc#1266284 jsc#PED-15986).\n- crypto/testmgr: disallow sha224 + sha3-224 in fips mode (bsc#1266284 jsc#PED-15986).\n- crypto: af_alg - Cap AEAD AD length to 0x80000000 (git-fixes).\n- crypto: amlogic - avoid double cleanup in meson_crypto_probe() (git-fixes).\n- crypto: asymmetric_keys - fix OOB read in pefile_digest_pe_contents (git-fixes).\n- crypto: atmel-sha204a - fix blocking and non-blocking rng logic (git-fixes).\n- crypto: cavium/cpt - fix DMA cleanup using wrong loop index (git-fixes).\n- crypto: ccp - Do not initialize SNP for ioctl(SNP_COMMIT) (git-fixes).\n- crypto: ccp - Do not initialize SNP for ioctl(SNP_VLEK_LOAD) (git-fixes).\n- crypto: ccp - Do not initialize SNP for SEV ioctls (git-fixes).\n- crypto: ccp - Fix snp_filter_reserved_mem_regions() off-by-one (git-fixes).\n- crypto: ccp - Treat zero-length cert chain as query for blob lengths (git-fixes).\n- crypto: drbg - Fix drbg_max_addtl() on 64-bit kernels (git-fixes).\n- crypto: drbg - Fix returning success on failure in CTR_DRBG (git-fixes).\n- crypto: drbg - Fix the fips_enabled priority boost (git-fixes).\n- crypto: ecc - Fix carry overflow in vli multiplication (git-fixes).\n- crypto: ecrdsa - fix unknown OID check in ecrdsa_param_curve (git-fixes).\n- crypto: hisilicon/qm - disable error report before flr (git-fixes).\n- crypto: marvell/octeontx - fix DMA cleanup using wrong loop index (git-fixes).\n- crypto: pcrypt - restore callback for non-parallel fallback (git-fixes).\n- crypto: qat - protect service table iterations with service_lock (git-fixes).\n- crypto: qat - validate RSA CRT component lengths (git-fixes).\n- crypto: rng - Free default RNG on module exit (git-fixes).\n- crypto: tegra - Fix dma_free_coherent size error (git-fixes).\n- crypto: tegra - fix refcount leak in tegra_se_host1x_submit() (git-fixes).\n- crypto: tegra - Return ENOMEM when input buffer allocation fails for ccm (git-fixes).\n- dm init: ensure device probing has finished in dm-mod.waitfor= (git-fixes).\n- dmaengine: dma-axi-dmac: Properly free struct axi_dmac_desc (git-fixes).\n- dmaengine: dma-axi-dmac: use DMA pool to manange DMA descriptor (git-fixes).\n- dmaengine: dw-edma: Add spinlock to protect DONE_INT_MASK and ABORT_INT_MASK (git-fixes).\n- dmaengine: Fix possible use after free (git-fixes).\n- dmaengine: imx-sdma: Refine spba bus searching in probe (git-fixes).\n- dmaengine: qcom: gpi: set DMA_PRIVATE capability (git-fixes).\n- dmaengine: tegra: Fix burst size calculation (git-fixes).\n- driver core: reject devices with unregistered buses (git-fixes).\n- driver core: use READ_ONCE() for dev-\u003edriver in dev_has_sync_state() (git-fixes).\n- Drivers: hv: vmbus: Improve the logic of reserving fb_mmio on Gen2 VMs (git-fixes).\n- drm/amd/display: add missing CSC entries for BT.2020 for DCE IPs (stable-fixes).\n- drm/amd/display: Add missing kdoc for ALLM parameters (git-fixes).\n- drm/amd/display: Clamp VBIOS HDMI retimer register count to array size (stable-fixes).\n- drm/amd/pm: fix smu13 power limit default/cap calculation (stable-fixes).\n- drm/amd/pm: mark metrics.energy_accumulator is invalid for smu 14.0.2 (stable-fixes).\n- drm/amd/pm: remove trailing semicolon from AMDGPU_PM_POLICY_ATTR macro (git-fixes).\n- drm/amd/pm: smu_v14_0_0: use SoftMin for gfxclk in set_soft_freq_limited_range (stable-fixes).\n- drm/amdgpu: Fix amdgpu_bo_move() when old_mem and new_mem are both GTT (git-fixes).\n- drm/amdgpu: fix integer overflow in amdgpu_gem_align_pitch() (git-fixes).\n- drm/amdgpu: initialize irq.lock spinlock earlier (git-fixes).\n- drm/amdgpu: restart the CS if some parts of the VM are still invalidated (stable-fixes).\n- drm/amdgpu: set sub_block_index for mca ras sub-blocks (git-fixes).\n- drm/amdgpu: skip already suspended IP blocks in ip_suspend_phase2 (git-fixes).\n- drm/amdgpu: validate CP_GFX_SHADOW chunk size in CS pass1 (git-fixes).\n- drm/amdkfd: always resume_all after suspend_all (git-fixes).\n- drm/amdkfd: Avoid double-unpin of DOORBELL/MMIO BOs on free (git-fixes).\n- drm/amdkfd: Check for pdd drm file first in CRIU restore path (stable-fixes).\n- drm/amdkfd: fix list_del corruption in kfd_criu_resume_svm (git-fixes).\n- drm/amdkfd: fix NULL pointer bug in svm_range_set_attr (stable-fixes).\n- drm/amdkfd: Use exclusive bounds for SVM split alignment checks (git-fixes).\n- drm/amdkfd: Validate CRIU-restored IDs before idr_alloc (git-fixes).\n- drm/bridge: cdns-dsi: Replace deprecated UNIVERSAL_DEV_PM_OPS() (git-fixes).\n- drm/dp/mst: fix buffer overflows in sideband chunk accumulation (git-fixes).\n- drm/dp/mst: fix OOB reads in remote DPCD/I2C sideband reply parsers (git-fixes).\n- drm/dp/mst: fix OOB reads on 2-byte fields in sideband reply parsers (git-fixes).\n- drm/dp: Add eDP 1.5 bit definition (stable-fixes).\n- drm/edid: fix OOB read in drm_parse_tiled_block() (git-fixes).\n- drm/gpuvm: Do not prepare NULL objects (git-fixes).\n- drm/hisilicon/hibmc: move display contrl config to hibmc_probe() (git-fixes).\n- drm/hisilicon/hibmc: use clock to look up the PLL value (git-fixes).\n- drm/hyperv: use VMBUS_RING_SIZE() (git-fixes).\n- drm/i915/gem: Add missing nospec on parallel submit slot (git-fixes).\n- drm/i915/gem: Fix phys BO pread/pwrite with offset (git-fixes).\n- drm/i915/psr: Add defininitions for INTEL_WA_REGISTER_CAPS DPCD register (stable-fixes).\n- drm/i915: clear CRTC color blob pointers after dropping refs (git-fixes).\n- drm/imagination: Count paired job fence as dependency in prepare_job() (git-fixes).\n- drm/imagination: Fit paired fragment job in the correct CCCB (git-fixes).\n- drm/msm/dp: fix HPD state status bit shift value (git-fixes).\n- drm/msm/dp: Fix the ISR_* enum values (git-fixes).\n- drm/nouveau/acr: fix missing nvkm_done() in error path of nvkm_acr_oneinit() (git-fixes).\n- drm/nouveau/bios: specify correct display fuse register for Ampere and Ada (git-fixes).\n- drm/nouveau: fix reversed error cleanup order in ucopy functions (git-fixes).\n- drm/panthor: Fix kernel-doc warning in panthor_sched.c (git-fixes).\n- drm/radeon: fix integer overflow in radeon_align_pitch() (git-fixes).\n- drm/radeon: fix memory leak in radeon_ring_restore() on lock failure (git-fixes).\n- drm/rockchip: cdn-dp: add missing check in cdn_dp_config_video() (git-fixes).\n- drm/rockchip: Test for imported buffers with drm_gem_is_imported() (git-fixes).\n- drm/syncobj: Fix memory leak in drm_syncobj_find_fence() (git-fixes).\n- drm/tegra: dc: Fix device node reference leak in tegra_dc_has_output() (git-fixes).\n- drm/tegra: Fix iommu_map_sgtable() return value check (git-fixes).\n- drm/tidss: Drop extra drm_mode_config_reset() call (git-fixes).\n- drm/tidss: Fix missing drm_bridge_add() call (git-fixes).\n- drm/vc4: fix krealloc() memory leak (git-fixes).\n- drm/virtio: fix dma_fence refcount leak on error in virtio_gpu_dma_fence_wait() (git-fixes).\n- drm/virtio: Fix driver removal with disabled KMS (git-fixes).\n- drm/xe: fix refcount leak in xe_range_fence_insert() (git-fixes).\n- drm: renesas: rzg2l_mipi_dsi: Increase reset deassertion delay (git-fixes).\n- fbdev: Fix fb_new_modelist to prevent null-ptr-deref in fb_videomode_to_var (stable-fixes).\n- fbdev: fix use-after-free in store_modes() (stable-fixes).\n- fbdev: modedb: fix a possible UAF in fb_find_mode() (stable-fixes).\n- fbdev: modedb: Fix misaligned fields in the 1920x1080-60 mode (git-fixes).\n- firmware: arm_scmi: Fix OOB in scmi_power_name_get() (git-fixes).\n- firmware: arm_scmi: Read sensor config as 32-bit value (git-fixes).\n- firmware_loader: fix device reference leak in firmware_upload_register() (git-fixes).\n- firmware_loader: Fix recursive lock in device_cache_fw_images() (git-fixes).\n- fpga: dfl: add bounds check in dfh_get_param_size() (git-fixes).\n- fpga: microchip-spi: fix zero header_size OOB read in mpf_ops_parse_header() (git-fixes).\n- fpga: region: fix use-after-free in child_regions_with_firmware() (git-fixes).\n- ftrace: Check against is_kernel_text() instead of kaslr_offset() (bsc#1267600).\n- ftrace: Do not over-allocate ftrace memory (bsc#1267600).\n- ftrace: Have ftrace pages output reflect freed pages (bsc#1267600).\n- ftrace: Test mcount_loc addr before calling ftrace_call_addr() (bsc#1267600).\n- ftrace: Update the mcount_loc check of skipped entries (bsc#1267600).\n- gpio: mvebu: fix NULL pointer dereference in suspend/resume (git-fixes).\n- gpio: mxc: fix irq_high handling (git-fixes).\n- gpio: rockchip: convert bank-\u003eclk to devm_clk_get_enabled() (git-fixes).\n- gpio: virtuser: Fix uninitialized data bug in gpio_virtuser_direction_do_write() (git-fixes).\n- gpio: zynq: fix runtime PM leak on remove (git-fixes).\n- gpiolib: Extract gpiochip_choose_fwnode() for wider use (stable-fixes).\n- gpiolib: Remove redundant assignment of return variable (stable-fixes).\n- gpu: host1x: Allow entries in BO caches to be freed (git-fixes).\n- gpu: host1x: Fix device reference leak in host1x_device_parse_dt() error path (git-fixes).\n- gpu: host1x: Fix iommu_map_sgtable() return value check (git-fixes).\n- HID: core: Add printk_ratelimited variants to hid_warn() etc (stable-fixes).\n- HID: hid-goodix-spi: validate report size to prevent stack buffer overflow (git-fixes).\n- HID: letsketch: fix UAF on inrange_timer at driver unbind (git-fixes).\n- HID: lg-g15: cancel pending work on remove to fix a use-after-free (git-fixes).\n- HID: logitech-hidpp: remove excess kernel-doc member in hidpp_scroll_counter (git-fixes).\n- HID: picolcd: prevent NULL pointer dereference in picolcd_send_and_wait() (git-fixes).\n- HID: quirks: Add ALWAYS_POLL quirk for SIGMACHIP USB mouse (stable-fixes).\n- HID: rate-limit hid_warn to prevent log flooding (stable-fixes).\n- HID: remove duplicate hid_warn_ratelimited definition (git-fixes).\n- HID: wacom: Fix OOB write in wacom_hid_set_device_mode() (git-fixes).\n- HID: wacom: stop hardware after post-start probe failures (git-fixes).\n- HID: wiimote: Fix table layout and whitespace errors (git-fixes).\n- hv: utils: handle and propagate errors in kvp_register (git-fixes).\n- hv: utils: replace deprecated strcpy with strscpy in kvp_register (git-fixes).\n- hv_balloon: Simplify data output in hv_balloon_debug_show() (git-fixes).\n- hv_netvsc: use kmap_local_page in netvsc_copy_to_send_buf (git-fixes).\n- hwmon: (aspeed-g6-pwm-tach) Guard fan RPM calculation against divide-by-zero (git-fixes).\n- hwmon: (asus_atk0110) Check package count before accessing element (git-fixes).\n- hwmon: (it87) Clamp negative values to zero in set_fan() (git-fixes).\n- hwmon: (ltc2992) add missing 'select REGMAP_I2C' to Kconfig (git-fixes).\n- hwmon: (max1619) add missing 'select REGMAP' to Kconfig (git-fixes).\n- hwmon: (max6697) add missing 'select REGMAP_I2C' to Kconfig (git-fixes).\n- hwmon: (occ) unregister sysfs devices outside occ lock (git-fixes).\n- hwmon: adm1275: Prevent reading uninitialized stack (git-fixes).\n- hwrng: jh7110 - fix refcount leak in starfive_trng_read() (git-fixes).\n- hwrng: virtio: clamp device-reported used.len at copy_data() (git-fixes).\n- hyperv: Clean up and fix the guest ID comment in hvgdk.h (git-fixes).\n- i2c: core: disable runtime PM on adapter registration failure (git-fixes).\n- i2c: core: fix adapter debugfs creation (git-fixes).\n- i2c: core: fix adapter deregistration race (git-fixes).\n- i2c: core: fix adapter probe deferral loop (git-fixes).\n- i2c: core: fix adapter registration race (git-fixes).\n- i2c: core: fix hang on adapter registration failure (git-fixes).\n- i2c: core: fix irq domain leak on adapter registration failure (git-fixes).\n- i2c: core: fix NULL-deref on adapter registration failure (git-fixes).\n- i2c: dev: prevent integer overflow in I2C_TIMEOUT ioctl (stable-fixes).\n- i2c: imx-lpi2c: mark I2C adapter when hardware is powered down (git-fixes).\n- i2c: mpc: Fix timeout calculations (git-fixes).\n- i2c: qcom-cci: Fix NULL pointer dereference in cci_remove() (git-fixes).\n- i2c: riic: fix refcount leak in riic_i2c_resume_noirq() (git-fixes).\n- i2c: stm32f7: fix timing computation ignoring i2c-analog-filter (git-fixes).\n- i2c: stm32f7: truncate clock period instead of rounding it (git-fixes).\n- i2c: tegra: Fix NOIRQ suspend/resume (git-fixes).\n- i3c: master: Prevent reuse of dynamic address on device add failure (git-fixes).\n- i3c: master: Serialize i3c_set_hotjoin() with the maintenance lock (git-fixes).\n- ice: ptp: don't WARN when controlling PF is unavailable (bsc#1267251).\n- iio: accel: mma8452: handle I2C read error(s) in mma8452_read() (git-fixes).\n- iio: adc: ti-ads1298: add bounds check to pga_settings index (stable-fixes).\n- iio: adc: xilinx-ams: fix out-of-bounds channel lookup in event handling (git-fixes).\n- iio: backend: fix uninitialized data in debugfs (git-fixes).\n- iio: chemical: scd30: Cleanup initializations and fix sign-extension bug (git-fixes).\n- iio: chemical: scd30: fix division by zero in write_raw (git-fixes).\n- iio: chemical: scd30: Use guard(mutex) to allow early returns (stable-fixes).\n- iio: gyro: bmg160: bail out when bandwidth/filter is not in table (git-fixes).\n- iio: gyro: bmg160: wait full startup time after mode change at probe (git-fixes).\n- iio: light: opt3001: fix missing state reset on timeout (git-fixes).\n- iio: light: si1133: prevent race condition on timeout (git-fixes).\n- iio: light: si1133: reset counter to prevent race condition (git-fixes).\n- iio: light: veml6030: fix channel type when pushing events (git-fixes).\n- iio: light: veml6075: add bounds check to veml6075_it_ms index (stable-fixes).\n- iio: magnetometer: ak8975: Add missed pm_runtime_put_autosuspend() call (git-fixes).\n- iio: resolver: ad2s1210: notify trigger and clear state on fault read error (git-fixes).\n- iio: tcs3472: power down chip on probe failure (git-fixes).\n- iio: temperature: ltc2983: Fix n_wires default bypassing rotation check (git-fixes).\n- iio: temperature: ltc2983: Fix reinit_completion() called after conversion start (git-fixes).\n- Input: atkbd - add DMI quirk for Lenovo Yoga Air 14 (83QK) (stable-fixes).\n- Input: elan_i2c - validate firmware size before use (stable-fixes).\n- Input: synaptics - add LEN2058 to SMBus passlist for ThinkPad E490 (stable-fixes).\n- Input: xpad - add \"Nova 2 Lite\" from GameSir (stable-fixes).\n- Input: xpad - add support for ASUS ROG RAIKIRI II (stable-fixes).\n- io_uring/cancel: de-unionize file and user_data in struct io_cancel_data (git-fixes bsc#1261250).\n- io_uring/filetable: clamp alloc_hint to the configured alloc range (git-fixes bsc#1261250).\n- io_uring/io-wq: fix incorrect io_wq_for_each_worker() termination logic (git-fixes bsc#1261250).\n- io_uring/poll: ensure EPOLL_ONESHOT is propagated for EPOLL_URING_WAKE (git-fixes bsc#1261250).\n- io_uring/wait: fix min_timeout behavior (git-fixes bsc#1261250).\n- io_uring/waitid: clear waitid info before copying it to userspace (git-fixes).\n- io_uring: fix min_wait wakeups for SQPOLL (git-fixes bsc#1261250).\n- ipv4: account for fraggap on the paged allocation path (git-fixes).\n- ipv6: account for fraggap on the paged allocation path (git-fixes).\n- KEYS: fix overflow in keyctl_pkey_params_get_2() (git-fixes).\n- KEYS: Use acquire when reading state in keyring search (git-fixes).\n- KVM: arm64: PMU: Preserve AArch32 counter low bits (git-fixes).\n- KVM: arm64: vgic: Free private_irqs when init fails after allocation (git-fixes).\n- KVM: Don't WARN if memory is dirtied without a vCPU when the VM is dying (git-fixes).\n- KVM: nSVM: Always use NextRIP as vmcb02's NextRIP after first L2 VMRUN (git-fixes).\n- KVM: nSVM: Always use vmcb01 in VMLOAD/VMSAVE emulation (git-fixes).\n- KVM: nSVM: Ensure AVIC is inhibited when restoring a vCPU to guest mode (git-fixes).\n- KVM: nSVM: Mark all of vmcb02 dirty when restoring nested state (git-fixes).\n- KVM: nSVM: Sync interrupt shadow to cached vmcb12 after VMRUN of L2 (git-fixes).\n- KVM: nSVM: Sync NextRIP to cached vmcb12 after VMRUN of L2 (git-fixes).\n- KVM: nVMX: Immediately refresh APICv controls as needed on nested VM-Exit (git-fixes).\n- KVM: Replace guest-triggerable BUG_ON() in ioeventfd datamatch with get_unaligned() (git-fixes).\n- KVM: SEV: Add an anonymous \"psc\" struct to track current PSC metadata (git-fixes).\n- KVM: SEV: Decouple the need to sync the GHCB SA from the need to free the SA (git-fixes).\n- KVM: SEV: Don't terminate SNP VMs on #VMGEXIT without a registered GHCB (git-fixes).\n- KVM: SEV: Make it more obvious when KVM is writing back the current PSC index (git-fixes).\n- KVM: SEV: Move sev_free_vcpu() down below sev_es_unmap_ghcb() (git-fixes).\n- KVM: SEV: Read start/end indices of PSC requests exactly once per #VMGEXIT (git-fixes).\n- KVM: SEV: Return INVALID_EVENT for SNP-only #VMGEXIT from non-SNP guest (git-fixes).\n- KVM: SEV: Return INVALID_INPUT, not MISSING_INPUT, for bad GUEST_REQUEST input(s) (git-fixes).\n- KVM: SEV: Unmap and unpin the GHCB as needed on vCPU free (git-fixes).\n- KVM: SVM: Allow KVM_SET_NESTED_STATE to clear GIF when SVME==0 (git-fixes).\n- KVM: SVM: check validity of VMCB controls when returning from SMM (git-fixes).\n- KVM: SVM: Don't set GIF when clearing EFER.SVME (git-fixes).\n- KVM: SVM: Truncate INVLPGA address in compatibility mode (git-fixes).\n- KVM: Use vCPU specific memslots in __kvm_vcpu_map() (git-fixes).\n- KVM: VMX: Grab vmcs12 on CR8 interception update iff vCPU is in guest mode (git-fixes).\n- KVM: VMX: Read 32-bit GPR values for ENCLS instructions outside of 64-bit mode (git-fixes).\n- KVM: x86/mmu: Ensure hugepage is in by slot before checking max mapping level (git-fixes).\n- KVM: x86/mmu: Recursively zap orphaned nested TDP shadow pages on emulated writes (git-fixes).\n- KVM: x86/xen: Bug the VM if 32-bit KVM observes a 64-bit mode hypercall (git-fixes).\n- KVM: x86/xen: Don't truncate RAX when handling hypercall from protected guest (git-fixes).\n- KVM: x86: Consolidate CPUID fault handling for emulator and interception logic (git-fixes).\n- KVM: x86: Fix shadow paging use-after-free due to unexpected role (git-fixes).\n- KVM: x86: hyper-v: Bound the bank index when querying sparse banks (git-fixes).\n- KVM: x86: ioapic: Use old_dest_mode consistently in ioapic_write_indirect() (git-fixes).\n- KVM: x86: Move update_cr8_intercept() to lapic.c (git-fixes).\n- KVM: x86: Prioritize CPUID faulting over CPUID VM-exits in nested VMX (git-fixes).\n- KVM: x86: Trace hypercall register *after* truncating values for 32-bit (git-fixes).\n- KVM: x86: Unconditionally recompute CR8 intercept on PPR update (git-fixes).\n- mailbox: imx: Forward the timeout/ error in imx_mu_generic_tx() (git-fixes).\n- mailbox: mtk-adsp: fix UAF during device teardown (git-fixes).\n- misc: fastrpc: fix DMA address corruption due to find_vma misuse (git-fixes).\n- misc: fastrpc: Fix NULL pointer dereference in rpmsg callback (git-fixes).\n- misc: fastrpc: fix use-after-free of fastrpc_user in workqueue context (git-fixes).\n- misc: fastrpc: fix use-after-free race in fastrpc_map_create (git-fixes).\n- mm/vmstat: defer the refresh_zone_stat_thresholds after all CPUs bringup (bsc#1270042).\n- mtd: maps: vmu-flash: fix NULL pointer dereference in initialization (git-fixes).\n- mtd: rawnand: fix condition in 'nand_select_target()' (git-fixes).\n- mtd: rawnand: Pause continuous reads at block boundaries (git-fixes).\n- mtd: rawnand: pl353: fix probe resource allocation (git-fixes).\n- mtd: slram: remove failed entries from the device list (git-fixes).\n- mtd: spi-nor: Drop duplicate Kconfig dependency (git-fixes).\n- mtd: spi-nor: macronix: Add post_sfdp fixups for Quad Input Page Program (stable-fixes).\n- mtd: spi-nor: macronix: add support for mx66{l2, u1}g45g (stable-fixes).\n- mtd: spi-nor: spansion: use die erase for multi-die devices only (git-fixes).\n- mtd: spi-nor: swp: Improve locking user experience (git-fixes).\n- net: aquantia: Add missing descriptor cache invalidation on ATL2 (bsc#1268428).\n- net: ethtool: add ethtool COALESCE_RX_CQE_FRAMES/NSECS (bsc#1261256).\n- net: mana: Add ethtool counters for RX CQEs in coalesced type (bsc#1261256).\n- net: mana: Add support for PF device 0x00C1 (bsc#1268237).\n- net: mana: Add support for RX CQE Coalescing (bsc#1261256).\n- net: mana: Allocate interrupt context for each EQ when creating vPort (git-fixes).\n- net: mana: Cache MANA_QUERY_LINK_CONFIG result to avoid repeated HWC queries (bsc#1268238).\n- net: mana: Create separate EQs for each vPort (git-fixes).\n- net: mana: Fall back to standard MTU when PF reports adapter_mtu of 0 (git-fixes).\n- net: mana: guard TX wq object destroy with INVALID_MANA_HANDLE check (git-fixes).\n- net: mana: initialize gdma queue id to INVALID_QUEUE_ID (git-fixes).\n- net: mana: Introduce GIC context with refcounting for interrupt management (git-fixes).\n- net: mana: Optimize irq affinity for low vcpu configs (git-fixes).\n- net: mana: Query device capabilities and configure MSI-X sharing for EQs (git-fixes).\n- net: mana: Sync page pool RX frags for CPU (git-fixes).\n- net: mana: Use GIC functions to allocate global EQs (git-fixes).\n- net: mana: Validate the packet length reported by the NIC (git-fixes).\n- net: phy: sfp: free mii_bus in sfp_i2c_mdiobus_destroy (git-fixes).\n- net: usb: lan78xx: disable VLAN filter in promiscuous mode (git-fixes).\n- net: usb: net1080: validate packet_len before pad-byte access in rx_fixup (git-fixes).\n- net: wwan: iosm: bound device offsets in the MUX downlink decoder (git-fixes).\n- nfc: hci: fix out-of-bounds read in HCP header parsing (git-fixes).\n- nfc: llcp: Fix use-after-free in llcp_sock_release() (git-fixes).\n- nfc: llcp: Fix use-after-free race in nfc_llcp_recv_cc() (git-fixes).\n- packaging: Add nvidia kernel description.\n- packaging: compute-PATCHVERSION.sh -\u003e compute-PATCHVERSION.\n- page_pool: Fix PP_MAGIC_MASK to avoid crashing on some 32-bit arches (bsc#1261562).\n- page_pool: Move pp_magic check into helper functions (bsc#1261562).\n- page_pool: Track DMA-mapped pages and unmap them when destroying the pool (bsc#1261562).\n- PCI: Update saved_config_space upon resource assignment (git-fixes).\n- perf/x86/intel/uncore: Fix die ID init and look up bugs (bsc#1267419).\n- perf/x86/intel/uncore: Skip discovery table for offline dies (bsc#1267419).\n- platform/x86: dell-laptop: fix missing cleanups in init error path (git-fixes).\n- platform/x86: intel-hid: Protect ACPI notify handler against recursion (git-fixes).\n- platform/x86: xo15-ebook: Fix wakeup source and GPE handling (git-fixes).\n- PM: sleep: Use complete() in device_pm_sleep_init() (git-fixes).\n- power: reset: linkstation-poweroff: fix use-after-free in the linkstation_poweroff_init() (git-fixes).\n- power: supply: charger-manager: fix refcount leak in is_full_charged() (git-fixes).\n- power: supply: core: fix supplied_from allocations (git-fixes).\n- power: supply: cpcap-battery: Fix missing nvmem_device_put() causing reference leak (git-fixes).\n- powerpc/boot: Allow text relocations for pseries wrapper with binutils 2.46+ (git-fixes).\n- powerpc/fadump: define MIN_RMA in bytes rather than MB (bsc#1236743 git-fixes).\n- ppc/fadump: invoke kmsg_dump in fadump panic path (bsc#1270226 ltc#218302).\n- pwm: imx27: Fix variable truncation in .apply() (git-fixes).\n- RDMA/mana_ib: Allocate interrupt contexts on EQs (git-fixes).\n- RDMA/mana_ib: Use ib_get_eth_speed for reporting port speed (git-fixes).\n- regulator: scmi: fix of_node refcount leak in scmi_regulator_probe() (git-fixes).\n- Revert \"fs: don't block i_writecount during exec\" (bsc#1269982).\n- rtc: abx80x: fix the RTC_VL_CLR clearing all status flags (git-fixes).\n- rtc: cmos: unregister HPET IRQ handler on probe failure (git-fixes).\n- rtc: ds1307: Fix off-by-one issue with wday for rx8130 (git-fixes).\n- rtc: ds1307: handle oscillator stop flag for ds1337/ds1339/ds3231 (git-fixes).\n- rtc: mpfs: fix counter upload completion condition (git-fixes).\n- rtc: msc313: fix NULL deref in shared IRQ handler at probe (git-fixes).\n- scripts/sorttable: Add helper functions for Elf_Ehdr (bsc#1267600).\n- scripts/sorttable: Add helper functions for Elf_Shdr (bsc#1267600).\n- scripts/sorttable: Add helper functions for Elf_Sym (bsc#1267600).\n- scripts/sorttable: Allow matches to functions before function entry (bsc#1267600).\n- scripts/sorttable: Always use an array for the mcount_loc sorting (bsc#1267600).\n- scripts/sorttable: Convert Elf_Ehdr to union (bsc#1267600).\n- scripts/sorttable: Convert Elf_Sym MACRO over to a union (bsc#1267600).\n- scripts/sorttable: Fix endianness handling in build-time mcount sort (bsc#1267600).\n- scripts/sorttable: Get start/stop_mcount_loc from ELF file directly (bsc#1267600).\n- scripts/sorttable: Have mcount rela sort use direct values (bsc#1267600).\n- scripts/sorttable: Have the ORC code use the _r() functions to read (bsc#1267600).\n- scripts/sorttable: Make compare_extable() into two functions (bsc#1267600).\n- scripts/sorttable: Move code from sorttable.h into sorttable.c (bsc#1267600).\n- scripts/sorttable: Remove unneeded Elf_Rel (bsc#1267600).\n- scripts/sorttable: Remove unused macro defines (bsc#1267600).\n- scripts/sorttable: Remove unused write functions (bsc#1267600).\n- scripts/sorttable: Replace Elf_Shdr Macro with a union (bsc#1267600).\n- scripts/sorttable: Use a structure of function pointers for elf helpers (bsc#1267600).\n- scripts/sorttable: Use normal sort if theres no relocs in the mcount section (bsc#1267600).\n- scripts/sorttable: Use uint64_t for mcount sorting (bsc#1267600).\n- scripts/sorttable: Zero out weak functions in mcount_loc table (bsc#1267600).\n- scsi: smartpqi: Use shost_to_hba() in pqi_scan_finished() (bsc#1257506).\n- scsi: storvsc: Replace symbolic permissions with octal (git-fixes).\n- scsi: target: Fix hexadecimal CHAP_I handling (git-fixes).\n- selftests/bpf: Add BPF_STRICT_BUILD toggle (poo#202224).\n- selftests/bpf: Allow test_progs to link with a partial object set (poo#202224).\n- selftests/bpf: Avoid rebuilds when running emit_tests (poo#202224).\n- selftests/bpf: Consolidate kernel modules into common directory (poo#202224).\n- selftests/bpf: Copy test_kmods when installing selftest (poo#202224).\n- selftests/bpf: Fix runqslower cross-endian build (poo#202224).\n- selftests/bpf: Fix test_kmods KDIR to honor O= and distro kernels (poo#202224).\n- selftests/bpf: make BPF_TARGET_ENDIAN non-recursive to speed up *.bpf.o build (poo#202224).\n- selftests/bpf: Make skeleton headers order-only prerequisites of .test.d (poo#202224).\n- selftests/bpf: Provide weak definitions for cross-test functions (poo#202224).\n- selftests/bpf: Skip tests whose objects were not built (poo#202224).\n- selftests/bpf: Support cross-endian building (poo#202224).\n- selftests/bpf: Tolerate benchmark build failures (poo#202224).\n- selftests/bpf: Tolerate BPF and skeleton generation failures (poo#202224).\n- selftests/bpf: Tolerate missing files during install (poo#202224).\n- selftests/bpf: Tolerate test file compilation failures (poo#202224).\n- serial: 8250: dispatch SysRq character in serial8250_handle_irq() (git-fixes).\n- serial: 8250_dw: dispatch SysRq character in dw8250_handle_irq() (git-fixes).\n- serial: qcom_geni: Fix RX DMA stall when SE_DMA_RX_LEN_IN is zero (git-fixes).\n- slimbus: qcom-ngd-ctrl: Avoid ABBA on tx_lock/ctrl-\u003elock (git-fixes).\n- slimbus: qcom-ngd-ctrl: Balance pm_runtime enablement for NGD (git-fixes).\n- slimbus: qcom-ngd-ctrl: Correct PDR and SSR cleanup ownership (git-fixes).\n- slimbus: qcom-ngd-ctrl: fix OF node refcount (git-fixes).\n- slimbus: qcom-ngd-ctrl: Fix probe error path ordering (git-fixes).\n- slimbus: qcom-ngd-ctrl: Fix up platform_driver registration (git-fixes).\n- slimbus: qcom-ngd-ctrl: Initialize controller resources in controller (git-fixes).\n- slimbus: qcom-ngd-ctrl: Register callbacks after creating the ngd (git-fixes).\n- soc: qcom: ice: Fix race between qcom_ice_probe() and of_qcom_ice_get() (git-fixes).\n- soc: qcom: ice: Return -ENODEV if the ICE platform device is not found (git-fixes).\n- spi: at91-usart: drop dead runtime pm support (git-fixes).\n- spi: dw: fix wrong BAUDR setting after resume (git-fixes).\n- spi: ep93xx: fix double-free of zeropage on DMA setup failure (git-fixes).\n- spi: fsl-lpspi: replace dmaengine_terminate_all() with dmaengine_terminate_sync() (git-fixes).\n- spi: fsl-lpspi: terminate the RX channel on TX prepare failure path (git-fixes).\n- spi: hisi-kunpeng: Use dev_err_probe() for host registration failure (git-fixes).\n- spi: meson-spifc: fix runtime PM leak on remove (git-fixes).\n- spi: rpc-if: Use correct device for hardware reinitialization on resume (git-fixes).\n- spi: uniphier: Fix completion initialization order before devm_request_irq() (git-fixes).\n- spi: xilinx: use FIFO occupancy register to determine buffer size (git-fixes).\n- Split off kABI workaround for bsc#1267458 (bsc#1267458).\n- staging: most: video: avoid double free on video register failure (git-fixes).\n- staging: nvec: fix use-after-free in nvec_rx_completed() (git-fixes).\n- thermal: hwmon: Fix critical temperature attribute removal (git-fixes).\n- thermal: intel: Fix dangling resources on thermal_throttle_online() failure (git-fixes).\n- thermal: testing: reject missing command arguments (git-fixes).\n- thermal: testing: zone: Flush work items during cleanup (git-fixes).\n- thunderbolt: Bound root directory content to block size (git-fixes).\n- thunderbolt: Clamp XDomain response data copy to allocation size (git-fixes).\n- thunderbolt: debugfs: Don't stop reading SB registers if just one fails (git-fixes).\n- thunderbolt: debugfs: Fix margining error counter buffer leak (git-fixes).\n- thunderbolt: Limit XDomain response copy to actual frame size (git-fixes).\n- thunderbolt: Reject zero-length property entries in validator (git-fixes).\n- thunderbolt: Validate XDomain request packet size before type cast (git-fixes).\n- tools/power/x86/intel-speed-select: Harden daemon pidfile open (git-fixes).\n- tpm: fix event_size output in tpm1_binary_bios_measurements_show (git-fixes).\n- tpm: tpm2-sessions: wait for async KPP completion in tpm_buf_append_salt (git-fixes).\n- tpm: tpm_tis_spi: Use wait_woken() in wait_for_tmp_stat() (git-fixes).\n- usb: core: Fix SuperSpeed root hub wMaxPacketSize (stable-fixes).\n- usb: core: Fix up Interrupt IN endpoints with bogus wBytesPerInterval (stable-fixes).\n- usb: host: max3421: Fix shift-out-of-bounds in max3421_hub_control() (git-fixes).\n- usb: host: max3421: Reject hub port requests for non-existent ports (git-fixes).\n- USB: quirks: add NO_LPM for Lenovo ThinkPad USB-C Dock Gen2 hub controllers (git-fixes).\n- USB: serial: io_ti: fix heap overflow in build_i2c_fw_hdr() (git-fixes).\n- USB: serial: io_ti: fix heap overflow in get_manuf_info() (git-fixes).\n- USB: serial: kl5kusb105: fix bulk-out buffer overflow (git-fixes).\n- USB: serial: option: add usb-id for Dell Wireless DW5826e-m (stable-fixes).\n- usb: storage: Add quirks for PNY Elite Portable SSD (git-fixes).\n- usb: typec: altmodes/displayport: validate count before reading Status Update VDO (stable-fixes).\n- usb: typec: tcpm/tcpci_maxim: validate header NDO against RX_BYTE_CNT (stable-fixes).\n- usb: typec: tcpm: bound altmode_desc[] per iteration in svdm_consume_modes() (stable-fixes).\n- usb: typec: tcpm: validate VDO count in Discover Identity ACK handlers (stable-fixes).\n- usb: typec: ucsi: ccg: reject firmware images without a ':' record header (stable-fixes).\n- usb: typec: ucsi: displayport: NAK DP_CMD_CONFIGURE without a payload VDO (stable-fixes).\n- usb: typec: ucsi: validate connector number in ucsi_connector_change() (stable-fixes).\n- usb: typec: wcove: don't write past struct pd_message in wcove_read_rx_buffer() (stable-fixes).\n- usbnet: gl620a: fix out-of-bounds read in genelink_rx_fixup() (git-fixes).\n- vc_screen: fix null-ptr-deref in vcs_notifier() during concurrent vcs_write (git-fixes).\n- watchdog/hpwdt: Refine hpwdt message for UV platform (bsc#1269199).\n- watchdog: apple: Add \"apple,t8103-wdt\" compatible (git-fixes).\n- watchdog: sama5d4_wdt: Fix WDDIS detection on SAM9X60 and SAMA7G5 (git-fixes).\n- watchdog: sp5100_tco: Use EFCH MMIO for newer Hygon FCH (git-fixes).\n- watchdog: sprd_wdt: Remove redundant sprd_wdt_disable() on register failure (git-fixes).\n- watchdog: unregister PM notifier on watchdog unregister (git-fixes).\n- wifi: ath9k: fix OOB access from firmware tx status queue ID (git-fixes).\n- wifi: ath11k: fix warning when unbinding (git-fixes).\n- wifi: cfg80211: fix grammar in MLO group key error message (git-fixes).\n- wifi: iwlwifi: mvm: fix race condition in PTP removal (stable-fixes).\n- wifi: mac80211: fix monitor mode frame capture for real chanctx drivers (git-fixes).\n- wifi: mt76: fix argument to ieee80211_is_first_frag() (git-fixes).\n- wifi: mt76: mt76x2u: Add support for ELECOM WDC-867SU3S (stable-fixes).\n- wifi: mt76: mt792x: skip MLD header rewrite for 802.3 encap TX (git-fixes).\n- wifi: mt76: mt7915: fix potential tx_retries underflow (git-fixes).\n- wifi: mt76: mt7921: avoid undesired changes of the preset regulatory domain (stable-fixes).\n- wifi: mt76: mt7921: fix a potential scan no APs (stable-fixes).\n- wifi: mt76: mt7921: fix potential tx_retries underflow (git-fixes).\n- wifi: mt76: mt7925: clean up DMA on probe failure (git-fixes).\n- wifi: mt76: mt7925: don't disable AP BSS when removing TDLS peer (git-fixes).\n- wifi: mt76: mt7925: fix potential tx_retries underflow (git-fixes).\n- wifi: mt76: mt7925: fix stale pointer comparisons in change_vif_links (git-fixes).\n- wifi: mt76: mt7925: keep TX BA state in the primary WCID (git-fixes).\n- wifi: mt76: mt7996: fix potential tx_retries underflow (git-fixes).\n- wifi: rtlwifi: rtl8821ae: Fix C2H bit location in RX descriptor (git-fixes).\n- wifi: rtw88: fix OOB read from firmware RX descriptor exceeding DMA buffer (git-fixes).\n- wifi: rtw88: increase TX report timeout to fix race condition (git-fixes).\n- wifi: rtw88: usb: fix memory leaks on USB write failures (git-fixes).\n- wifi: rtw89: Correct data type for scan index to avoid infinite loop (git-fixes).\n- wifi: wcn36xx: fix heap overflow from oversized firmware HAL response (git-fixes).\n- wifi: wcn36xx: fix OOB read from firmware count in PRINT_REG_INFO indication (git-fixes).\n- wifi: wcn36xx: fix OOB read from short trigger BA firmware response (git-fixes).\n- x86/cpu/amd: Correct the microcode table for Zenbleed (git-fixes).\n- x86/cpu: Disable FRED when PTI is forced on (git-fixes).\n- x86/cpu: Properly parse CPUID leaf 0x2 TLB descriptor 0x63 (git-fixes).\n- x86/cpu: Validate CPUID leaf 0x2 EDX output (git-fixes).\n- x86/irq: Ensure initial PIR loads are performed exactly once (git-fixes).\n- x86/platform/uv: Expose the uv_hub_type() interface (jsc#PED-16390).\n- x86/tsc: Disable clocksource watchdog checking on recent and future UV platforms (jsc#PED-16390).\n- X.509: Fix validation of ASN.1 certificate header (git-fixes).\n- xfrm: Fix dev use-after-free in xfrm async resumption (bsc#1268276).\n","status":"published","published":"2026-07-21T08:27:34Z","modified":"2026-07-28T18:24:09.217846062Z","updated_at":"2026-11-02T15:54:03.080707Z"},{"id":"USN-8277-1","title":"linux, linux-aws, linux-hwe-6.17, linux-oem-6.17, linux-oracle, linux-raspi, linux-realtime, linux-realtime-6.17 vulnerabilities","description":"\nIt was discovered that the Linux kernel algif_aead module did not properly\nhandle in-place cryptographic operations. This flaw is known as Copy Fail.\nA local attacker could use this to escalate privileges, or possibly escape\na container. (CVE-2026-31431)\n\nSeveral security issues were discovered in the Linux kernel.\nAn attacker could possibly use these to compromise the system.\nThis update corrects flaws in the following subsystems:\n  - S390 architecture;\n  - Cryptographic API;\n  - GPU drivers;\n  - Ethernet bonding driver;\n  - Network file system (NFS) server daemon;\n  - Distributed Switch Architecture;\n  - Netfilter;\n  - Control group (cgroup);\n  - Kernel kexec() syscall;\n  - Memory management;\n  - MAC80211 subsystem;\n  - Multipath TCP;\n  - Packet sockets;\n  - TLS protocol;\n  - Unix domain sockets;\n(CVE-2025-71088, CVE-2025-71090, CVE-2025-71127, CVE-2025-71134,\nCVE-2025-71139, CVE-2025-71141, CVE-2025-71142, CVE-2025-71144,\nCVE-2025-71152, CVE-2025-71155, CVE-2026-23274, CVE-2026-23351,\nCVE-2026-23394, CVE-2026-31419, CVE-2026-31504, CVE-2026-31533,\nCVE-2026-43033, CVE-2026-43077, CVE-2026-43078)\n","status":"published","published":"2026-05-19T22:20:54Z","modified":"2026-11-05T19:01:10.09323183Z","updated_at":"2026-11-05T19:27:36.688147Z"},{"id":"USN-8277-2","title":"linux-oracle-6.17 vulnerabilities","description":"It was discovered that the Linux kernel algif_aead module did not properly\nhandle in-place cryptographic operations. This flaw is known as Copy Fail.\nA local attacker could use this to escalate privileges, or possibly escape\na container. (CVE-2026-31431)\n\nSeveral security issues were discovered in the Linux kernel.\nAn attacker could possibly use these to compromise the system.\nThis update corrects flaws in the following subsystems:\n  - S390 architecture;\n  - Cryptographic API;\n  - GPU drivers;\n  - Ethernet bonding driver;\n  - Network file system (NFS) server daemon;\n  - Distributed Switch Architecture;\n  - Netfilter;\n  - Control group (cgroup);\n  - Kernel kexec() syscall;\n  - Memory management;\n  - MAC80211 subsystem;\n  - Multipath TCP;\n  - Packet sockets;\n  - TLS protocol;\n  - Unix domain sockets;\n(CVE-2025-71088, CVE-2025-71090, CVE-2025-71127, CVE-2025-71134,\nCVE-2025-71139, CVE-2025-71141, CVE-2025-71142, CVE-2025-71144,\nCVE-2025-71152, CVE-2025-71155, CVE-2026-23274, CVE-2026-23351,\nCVE-2026-23394, CVE-2026-31419, CVE-2026-31504, CVE-2026-31533,\nCVE-2026-43033, CVE-2026-43077, CVE-2026-43078)\n","status":"published","published":"2026-05-22T14:05:12Z","modified":"2026-11-05T19:01:29.266816454Z","updated_at":"2026-11-05T19:27:36.688147Z"},{"id":"USN-8278-1","title":"linux, linux-aws, linux-aws-fips, linux-gcp, linux-gcp-fips, linux-gke, linux-gkeop, linux-ibm, linux-ibm-6.8, linux-lowlatency, linux-lowlatency-hwe-6.8, linux-raspi, linux-raspi-realtime, linux-realtime, linux-realtime-6.8 vulnerabilities","description":"It was discovered that the Linux kernel algif_aead module did not properly\nhandle in-place cryptographic operations. This flaw is known as Copy Fail.\nA local attacker could use this to escalate privileges, or possibly escape\na container. (CVE-2026-31431)\n\nSeveral security issues were discovered in the Linux kernel.\nAn attacker could possibly use these to compromise the system.\nThis update corrects flaws in the following subsystems:\n  - ARM64 architecture;\n  - x86 architecture;\n  - Cryptographic API;\n  - Compute Acceleration Framework;\n  - Drivers core;\n  - Null block device driver;\n  - Ublk userspace block driver;\n  - Bluetooth drivers;\n  - Counter interface drivers;\n  - DMA engine subsystem;\n  - DPLL subsystem;\n  - GPU drivers;\n  - HID subsystem;\n  - Intel Trace Hub HW tracing drivers;\n  - IIO ADC drivers;\n  - IIO subsystem;\n  - On-Chip Interconnect management framework;\n  - IRQ chip drivers;\n  - Modular ISDN driver;\n  - LED subsystem;\n  - Multiple devices driver;\n  - UACCE accelerator framework;\n  - MMC subsystem;\n  - Ethernet bonding driver;\n  - Network drivers;\n  - Mellanox network drivers;\n  - NVME drivers;\n  - PHY drivers;\n  - x86 platform drivers;\n  - i.MX PM domains;\n  - SCSI subsystem;\n  - SLIMbus drivers;\n  - SPI subsystem;\n  - TCM subsystem;\n  - W1 Dallas's 1-wire bus driver;\n  - Xen hypervisor drivers;\n  - BTRFS file system;\n  - EFI Variable file system;\n  - exFAT file system;\n  - Ext4 file system;\n  - HFS+ file system;\n  - Network file system (NFS) client;\n  - Network file system (NFS) server daemon;\n  - NTFS3 file system;\n  - SMB network file system;\n  - Scheduler infrastructure;\n  - Netfilter;\n  - NFC subsystem;\n  - Tracing infrastructure;\n  - io_uring subsystem;\n  - BPF subsystem;\n  - Perf events;\n  - Floating proportions library;\n  - Memory management;\n  - Bluetooth subsystem;\n  - CAN network layer;\n  - Ceph Core library;\n  - Networking core;\n  - IPv4 networking;\n  - IPv6 networking;\n  - L2TP protocol;\n  - MAC80211 subsystem;\n  - NET/ROM layer;\n  - Packet sockets;\n  - Network traffic control;\n  - SCTP protocol;\n  - TLS protocol;\n  - Unix domain sockets;\n  - VMware vSockets driver;\n  - Wireless networking;\n  - ALSA AC97 driver;\n  - Generic PCM loopback sound driver;\n  - Creative Sound Blaster X-Fi driver;\n  - AMD SoC Alsa drivers;\n  - Texas InstrumentS Audio (ASoC/HDA) drivers;\n  - USB sound devices;\n  - KVM subsystem;\n(CVE-2024-50004, CVE-2024-58096, CVE-2024-58097, CVE-2025-37926,\nCVE-2025-38201, CVE-2025-38591, CVE-2025-40039, CVE-2025-40082,\nCVE-2025-40149, CVE-2025-68351, CVE-2025-68358, CVE-2025-68365,\nCVE-2025-68725, CVE-2025-68749, CVE-2025-68803, CVE-2025-68823,\nCVE-2025-71160, CVE-2025-71162, CVE-2025-71163, CVE-2025-71180,\nCVE-2025-71182, CVE-2025-71183, CVE-2025-71184, CVE-2025-71185,\nCVE-2025-71186, CVE-2025-71188, CVE-2025-71189, CVE-2025-71190,\nCVE-2025-71191, CVE-2025-71192, CVE-2025-71193, CVE-2025-71194,\nCVE-2025-71195, CVE-2025-71196, CVE-2025-71197, CVE-2025-71198,\nCVE-2025-71199, CVE-2025-71200, CVE-2025-71220, CVE-2025-71222,\nCVE-2025-71224, CVE-2025-71225, CVE-2025-71268, CVE-2026-22976,\nCVE-2026-22977, CVE-2026-22978, CVE-2026-22979, CVE-2026-22980,\nCVE-2026-22982, CVE-2026-22984, CVE-2026-22990, CVE-2026-22991,\nCVE-2026-22992, CVE-2026-22994, CVE-2026-22996, CVE-2026-22997,\nCVE-2026-22998, CVE-2026-22999, CVE-2026-23000, CVE-2026-23001,\nCVE-2026-23003, CVE-2026-23005, CVE-2026-23006, CVE-2026-23010,\nCVE-2026-23011, CVE-2026-23019, CVE-2026-23020, CVE-2026-23021,\nCVE-2026-23025, CVE-2026-23026, CVE-2026-23030, CVE-2026-23031,\nCVE-2026-23032, CVE-2026-23033, CVE-2026-23035, CVE-2026-23037,\nCVE-2026-23038, CVE-2026-23047, CVE-2026-23049, CVE-2026-23050,\nCVE-2026-23053, CVE-2026-23054, CVE-2026-23056, CVE-2026-23057,\nCVE-2026-23058, CVE-2026-23059, CVE-2026-23061, CVE-2026-23062,\nCVE-2026-23063, CVE-2026-23064, CVE-2026-23065, CVE-2026-23068,\nCVE-2026-23069, CVE-2026-23071, CVE-2026-23073, CVE-2026-23075,\nCVE-2026-23076, CVE-2026-23078, CVE-2026-23080, CVE-2026-23083,\nCVE-2026-23084, CVE-2026-23085, CVE-2026-23086, CVE-2026-23087,\nCVE-2026-23088, CVE-2026-23089, CVE-2026-23090, CVE-2026-23091,\nCVE-2026-23093, CVE-2026-23094, CVE-2026-23095, CVE-2026-23096,\nCVE-2026-23097, CVE-2026-23098, CVE-2026-23099, CVE-2026-23101,\nCVE-2026-23102, CVE-2026-23103, CVE-2026-23105, CVE-2026-23107,\nCVE-2026-23108, CVE-2026-23110, CVE-2026-23113, CVE-2026-23116,\nCVE-2026-23119, CVE-2026-23120, CVE-2026-23121, CVE-2026-23123,\nCVE-2026-23124, CVE-2026-23125, CVE-2026-23126, CVE-2026-23128,\nCVE-2026-23129, CVE-2026-23131, CVE-2026-23133, CVE-2026-23135,\nCVE-2026-23136, CVE-2026-23139, CVE-2026-23140, CVE-2026-23141,\nCVE-2026-23142, CVE-2026-23144, CVE-2026-23145, CVE-2026-23146,\nCVE-2026-23148, CVE-2026-23150, CVE-2026-23151, CVE-2026-23156,\nCVE-2026-23159, CVE-2026-23160, CVE-2026-23163, CVE-2026-23164,\nCVE-2026-23166, CVE-2026-23167, CVE-2026-23168, CVE-2026-23170,\nCVE-2026-23172, CVE-2026-23173, CVE-2026-23176, CVE-2026-23178,\nCVE-2026-23179, CVE-2026-23180, CVE-2026-23182, CVE-2026-23187,\nCVE-2026-23190, CVE-2026-23191, CVE-2026-23193, CVE-2026-23198,\nCVE-2026-23200, CVE-2026-23202, CVE-2026-23204, CVE-2026-23205,\nCVE-2026-23206, CVE-2026-23212, CVE-2026-23213, CVE-2026-23214,\nCVE-2026-23215, CVE-2026-23216, CVE-2026-23254, CVE-2026-23256,\nCVE-2026-23257, CVE-2026-23258, CVE-2026-23260, CVE-2026-23261,\nCVE-2026-23262, CVE-2026-23264, CVE-2026-23274, CVE-2026-23351,\nCVE-2026-23394, CVE-2026-31419, CVE-2026-31504, CVE-2026-31533,\nCVE-2026-43033, CVE-2026-43077, CVE-2026-43078)\n","status":"published","published":"2026-05-19T22:33:02Z","modified":"2026-11-05T19:04:28.160890429Z","updated_at":"2026-11-05T19:27:14.534654Z"},{"id":"USN-8278-2","title":"linux-azure vulnerabilities","description":"It was discovered that the Linux kernel algif_aead module did not properly\nhandle in-place cryptographic operations. This flaw is known as Copy Fail.\nA local attacker could use this to escalate privileges, or possibly escape\na container. (CVE-2026-31431)\n\nSeveral security issues were discovered in the Linux kernel.\nAn attacker could possibly use these to compromise the system.\nThis update corrects flaws in the following subsystems:\n  - ARM64 architecture;\n  - x86 architecture;\n  - Cryptographic API;\n  - Compute Acceleration Framework;\n  - Drivers core;\n  - Null block device driver;\n  - Ublk userspace block driver;\n  - Bluetooth drivers;\n  - Counter interface drivers;\n  - DMA engine subsystem;\n  - DPLL subsystem;\n  - GPU drivers;\n  - HID subsystem;\n  - Intel Trace Hub HW tracing drivers;\n  - IIO ADC drivers;\n  - IIO subsystem;\n  - On-Chip Interconnect management framework;\n  - IRQ chip drivers;\n  - Modular ISDN driver;\n  - LED subsystem;\n  - Multiple devices driver;\n  - UACCE accelerator framework;\n  - MMC subsystem;\n  - Ethernet bonding driver;\n  - Network drivers;\n  - Mellanox network drivers;\n  - NVME drivers;\n  - PHY drivers;\n  - x86 platform drivers;\n  - i.MX PM domains;\n  - SCSI subsystem;\n  - SLIMbus drivers;\n  - SPI subsystem;\n  - TCM subsystem;\n  - W1 Dallas's 1-wire bus driver;\n  - Xen hypervisor drivers;\n  - BTRFS file system;\n  - EFI Variable file system;\n  - exFAT file system;\n  - Ext4 file system;\n  - HFS+ file system;\n  - Network file system (NFS) client;\n  - Network file system (NFS) server daemon;\n  - NTFS3 file system;\n  - SMB network file system;\n  - Scheduler infrastructure;\n  - Netfilter;\n  - NFC subsystem;\n  - Tracing infrastructure;\n  - io_uring subsystem;\n  - BPF subsystem;\n  - Perf events;\n  - Floating proportions library;\n  - Memory management;\n  - Bluetooth subsystem;\n  - CAN network layer;\n  - Ceph Core library;\n  - Networking core;\n  - IPv4 networking;\n  - IPv6 networking;\n  - L2TP protocol;\n  - MAC80211 subsystem;\n  - NET/ROM layer;\n  - Packet sockets;\n  - Network traffic control;\n  - SCTP protocol;\n  - TLS protocol;\n  - Unix domain sockets;\n  - VMware vSockets driver;\n  - Wireless networking;\n  - ALSA AC97 driver;\n  - Generic PCM loopback sound driver;\n  - Creative Sound Blaster X-Fi driver;\n  - AMD SoC Alsa drivers;\n  - Texas InstrumentS Audio (ASoC/HDA) drivers;\n  - USB sound devices;\n  - KVM subsystem;\n(CVE-2024-50004, CVE-2024-58096, CVE-2024-58097, CVE-2025-37926,\nCVE-2025-38201, CVE-2025-38591, CVE-2025-40039, CVE-2025-40082,\nCVE-2025-40149, CVE-2025-68351, CVE-2025-68358, CVE-2025-68365,\nCVE-2025-68725, CVE-2025-68749, CVE-2025-68803, CVE-2025-68823,\nCVE-2025-71160, CVE-2025-71162, CVE-2025-71163, CVE-2025-71180,\nCVE-2025-71182, CVE-2025-71183, CVE-2025-71184, CVE-2025-71185,\nCVE-2025-71186, CVE-2025-71188, CVE-2025-71189, CVE-2025-71190,\nCVE-2025-71191, CVE-2025-71192, CVE-2025-71193, CVE-2025-71194,\nCVE-2025-71195, CVE-2025-71196, CVE-2025-71197, CVE-2025-71198,\nCVE-2025-71199, CVE-2025-71200, CVE-2025-71220, CVE-2025-71222,\nCVE-2025-71224, CVE-2025-71225, CVE-2025-71268, CVE-2026-22976,\nCVE-2026-22977, CVE-2026-22978, CVE-2026-22979, CVE-2026-22980,\nCVE-2026-22982, CVE-2026-22984, CVE-2026-22990, CVE-2026-22991,\nCVE-2026-22992, CVE-2026-22994, CVE-2026-22996, CVE-2026-22997,\nCVE-2026-22998, CVE-2026-22999, CVE-2026-23000, CVE-2026-23001,\nCVE-2026-23003, CVE-2026-23005, CVE-2026-23006, CVE-2026-23010,\nCVE-2026-23011, CVE-2026-23019, CVE-2026-23020, CVE-2026-23021,\nCVE-2026-23025, CVE-2026-23026, CVE-2026-23030, CVE-2026-23031,\nCVE-2026-23032, CVE-2026-23033, CVE-2026-23035, CVE-2026-23037,\nCVE-2026-23038, CVE-2026-23047, CVE-2026-23049, CVE-2026-23050,\nCVE-2026-23053, CVE-2026-23054, CVE-2026-23056, CVE-2026-23057,\nCVE-2026-23058, CVE-2026-23059, CVE-2026-23061, CVE-2026-23062,\nCVE-2026-23063, CVE-2026-23064, CVE-2026-23065, CVE-2026-23068,\nCVE-2026-23069, CVE-2026-23071, CVE-2026-23073, CVE-2026-23075,\nCVE-2026-23076, CVE-2026-23078, CVE-2026-23080, CVE-2026-23083,\nCVE-2026-23084, CVE-2026-23085, CVE-2026-23086, CVE-2026-23087,\nCVE-2026-23088, CVE-2026-23089, CVE-2026-23090, CVE-2026-23091,\nCVE-2026-23093, CVE-2026-23094, CVE-2026-23095, CVE-2026-23096,\nCVE-2026-23097, CVE-2026-23098, CVE-2026-23099, CVE-2026-23101,\nCVE-2026-23102, CVE-2026-23103, CVE-2026-23105, CVE-2026-23107,\nCVE-2026-23108, CVE-2026-23110, CVE-2026-23113, CVE-2026-23116,\nCVE-2026-23119, CVE-2026-23120, CVE-2026-23121, CVE-2026-23123,\nCVE-2026-23124, CVE-2026-23125, CVE-2026-23126, CVE-2026-23128,\nCVE-2026-23129, CVE-2026-23131, CVE-2026-23133, CVE-2026-23135,\nCVE-2026-23136, CVE-2026-23139, CVE-2026-23140, CVE-2026-23141,\nCVE-2026-23142, CVE-2026-23144, CVE-2026-23145, CVE-2026-23146,\nCVE-2026-23148, CVE-2026-23150, CVE-2026-23151, CVE-2026-23156,\nCVE-2026-23159, CVE-2026-23160, CVE-2026-23163, CVE-2026-23164,\nCVE-2026-23166, CVE-2026-23167, CVE-2026-23168, CVE-2026-23170,\nCVE-2026-23172, CVE-2026-23173, CVE-2026-23176, CVE-2026-23178,\nCVE-2026-23179, CVE-2026-23180, CVE-2026-23182, CVE-2026-23187,\nCVE-2026-23190, CVE-2026-23191, CVE-2026-23193, CVE-2026-23198,\nCVE-2026-23200, CVE-2026-23202, CVE-2026-23204, CVE-2026-23205,\nCVE-2026-23206, CVE-2026-23212, CVE-2026-23213, CVE-2026-23214,\nCVE-2026-23215, CVE-2026-23216, CVE-2026-23254, CVE-2026-23256,\nCVE-2026-23257, CVE-2026-23258, CVE-2026-23260, CVE-2026-23261,\nCVE-2026-23262, CVE-2026-23264, CVE-2026-23274, CVE-2026-23351,\nCVE-2026-23394, CVE-2026-31419, CVE-2026-31504, CVE-2026-31533,\nCVE-2026-43033, CVE-2026-43077, CVE-2026-43078)\n","status":"published","published":"2026-05-26T19:00:47Z","modified":"2026-11-05T19:01:25.946958298Z","updated_at":"2026-11-05T19:27:36.688147Z"},{"id":"USN-8289-1","title":"linux-nvidia, linux-nvidia-lowlatency vulnerabilities","description":"\nIt was discovered that the Linux kernel algif_aead module did not properly\nhandle in-place cryptographic operations. This flaw is known as Copy Fail.\nA local attacker could use this to escalate privileges, or possibly escape\na container. (CVE-2026-31431)\n\nSeveral security issues were discovered in the Linux kernel.\nAn attacker could possibly use these to compromise the system.\nThis update corrects flaws in the following subsystems:\n  - ARM64 architecture;\n  - x86 architecture;\n  - Cryptographic API;\n  - Compute Acceleration Framework;\n  - Drivers core;\n  - Null block device driver;\n  - Ublk userspace block driver;\n  - Bluetooth drivers;\n  - Counter interface drivers;\n  - DMA engine subsystem;\n  - DPLL subsystem;\n  - GPU drivers;\n  - HID subsystem;\n  - Intel Trace Hub HW tracing drivers;\n  - IIO ADC drivers;\n  - IIO subsystem;\n  - On-Chip Interconnect management framework;\n  - IRQ chip drivers;\n  - Modular ISDN driver;\n  - LED subsystem;\n  - Multiple devices driver;\n  - UACCE accelerator framework;\n  - MMC subsystem;\n  - Ethernet bonding driver;\n  - Network drivers;\n  - Mellanox network drivers;\n  - NVME drivers;\n  - PHY drivers;\n  - x86 platform drivers;\n  - i.MX PM domains;\n  - SCSI subsystem;\n  - SLIMbus drivers;\n  - SPI subsystem;\n  - TCM subsystem;\n  - W1 Dallas's 1-wire bus driver;\n  - Xen hypervisor drivers;\n  - BTRFS file system;\n  - EFI Variable file system;\n  - exFAT file system;\n  - Ext4 file system;\n  - HFS+ file system;\n  - Network file system (NFS) client;\n  - Network file system (NFS) server daemon;\n  - NTFS3 file system;\n  - SMB network file system;\n  - Scheduler infrastructure;\n  - Netfilter;\n  - NFC subsystem;\n  - Tracing infrastructure;\n  - io_uring subsystem;\n  - BPF subsystem;\n  - Perf events;\n  - Floating proportions library;\n  - Memory management;\n  - Bluetooth subsystem;\n  - CAN network layer;\n  - Ceph Core library;\n  - Networking core;\n  - IPv4 networking;\n  - IPv6 networking;\n  - L2TP protocol;\n  - MAC80211 subsystem;\n  - NET/ROM layer;\n  - Packet sockets;\n  - Network traffic control;\n  - SCTP protocol;\n  - TLS protocol;\n  - Unix domain sockets;\n  - VMware vSockets driver;\n  - Wireless networking;\n  - ALSA AC97 driver;\n  - Generic PCM loopback sound driver;\n  - Creative Sound Blaster X-Fi driver;\n  - AMD SoC Alsa drivers;\n  - Texas InstrumentS Audio (ASoC/HDA) drivers;\n  - USB sound devices;\n  - KVM subsystem;\n(CVE-2024-50004, CVE-2024-58096, CVE-2024-58097, CVE-2025-37926,\nCVE-2025-38201, CVE-2025-38591, CVE-2025-40039, CVE-2025-40082,\nCVE-2025-40149, CVE-2025-68351, CVE-2025-68358, CVE-2025-68365,\nCVE-2025-68725, CVE-2025-68749, CVE-2025-68803, CVE-2025-68823,\nCVE-2025-71160, CVE-2025-71162, CVE-2025-71163, CVE-2025-71180,\nCVE-2025-71182, CVE-2025-71183, CVE-2025-71184, CVE-2025-71185,\nCVE-2025-71186, CVE-2025-71188, CVE-2025-71189, CVE-2025-71190,\nCVE-2025-71191, CVE-2025-71192, CVE-2025-71193, CVE-2025-71194,\nCVE-2025-71195, CVE-2025-71196, CVE-2025-71197, CVE-2025-71198,\nCVE-2025-71199, CVE-2025-71200, CVE-2025-71220, CVE-2025-71222,\nCVE-2025-71224, CVE-2025-71225, CVE-2025-71268, CVE-2026-22976,\nCVE-2026-22977, CVE-2026-22978, CVE-2026-22979, CVE-2026-22980,\nCVE-2026-22982, CVE-2026-22984, CVE-2026-22990, CVE-2026-22991,\nCVE-2026-22992, CVE-2026-22994, CVE-2026-22996, CVE-2026-22997,\nCVE-2026-22998, CVE-2026-22999, CVE-2026-23000, CVE-2026-23001,\nCVE-2026-23003, CVE-2026-23005, CVE-2026-23006, CVE-2026-23010,\nCVE-2026-23011, CVE-2026-23019, CVE-2026-23020, CVE-2026-23021,\nCVE-2026-23025, CVE-2026-23026, CVE-2026-23030, CVE-2026-23031,\nCVE-2026-23032, CVE-2026-23033, CVE-2026-23035, CVE-2026-23037,\nCVE-2026-23038, CVE-2026-23047, CVE-2026-23049, CVE-2026-23050,\nCVE-2026-23053, CVE-2026-23054, CVE-2026-23056, CVE-2026-23057,\nCVE-2026-23058, CVE-2026-23059, CVE-2026-23061, CVE-2026-23062,\nCVE-2026-23063, CVE-2026-23064, CVE-2026-23065, CVE-2026-23068,\nCVE-2026-23069, CVE-2026-23071, CVE-2026-23073, CVE-2026-23075,\nCVE-2026-23076, CVE-2026-23078, CVE-2026-23080, CVE-2026-23083,\nCVE-2026-23084, CVE-2026-23085, CVE-2026-23086, CVE-2026-23087,\nCVE-2026-23088, CVE-2026-23089, CVE-2026-23090, CVE-2026-23091,\nCVE-2026-23093, CVE-2026-23094, CVE-2026-23095, CVE-2026-23096,\nCVE-2026-23097, CVE-2026-23098, CVE-2026-23099, CVE-2026-23101,\nCVE-2026-23102, CVE-2026-23103, CVE-2026-23105, CVE-2026-23107,\nCVE-2026-23108, CVE-2026-23110, CVE-2026-23113, CVE-2026-23116,\nCVE-2026-23119, CVE-2026-23120, CVE-2026-23121, CVE-2026-23123,\nCVE-2026-23124, CVE-2026-23125, CVE-2026-23126, CVE-2026-23128,\nCVE-2026-23129, CVE-2026-23131, CVE-2026-23133, CVE-2026-23135,\nCVE-2026-23136, CVE-2026-23139, CVE-2026-23140, CVE-2026-23141,\nCVE-2026-23142, CVE-2026-23144, CVE-2026-23145, CVE-2026-23146,\nCVE-2026-23148, CVE-2026-23150, CVE-2026-23151, CVE-2026-23156,\nCVE-2026-23159, CVE-2026-23160, CVE-2026-23163, CVE-2026-23164,\nCVE-2026-23166, CVE-2026-23167, CVE-2026-23168, CVE-2026-23170,\nCVE-2026-23172, CVE-2026-23173, CVE-2026-23176, CVE-2026-23178,\nCVE-2026-23179, CVE-2026-23180, CVE-2026-23182, CVE-2026-23187,\nCVE-2026-23190, CVE-2026-23191, CVE-2026-23193, CVE-2026-23198,\nCVE-2026-23200, CVE-2026-23204, CVE-2026-23205, CVE-2026-23206,\nCVE-2026-23212, CVE-2026-23213, CVE-2026-23214, CVE-2026-23215,\nCVE-2026-23216, CVE-2026-23254, CVE-2026-23256, CVE-2026-23257,\nCVE-2026-23258, CVE-2026-23260, CVE-2026-23261, CVE-2026-23262,\nCVE-2026-23264, CVE-2026-23274, CVE-2026-23351, CVE-2026-23394,\nCVE-2026-31419, CVE-2026-31504, CVE-2026-31533, CVE-2026-43033,\nCVE-2026-43077, CVE-2026-43078)\n","status":"published","published":"2026-05-20T23:06:37Z","modified":"2026-11-05T19:03:53.913181128Z","updated_at":"2026-11-05T19:27:26.236035Z"},{"id":"USN-8289-2","title":"linux-nvidia-6.8 vulnerabilities","description":"It was discovered that the Linux kernel algif_aead module did not properly\nhandle in-place cryptographic operations. This flaw is known as Copy Fail.\nA local attacker could use this to escalate privileges, or possibly escape\na container. (CVE-2026-31431)\n\nSeveral security issues were discovered in the Linux kernel.\nAn attacker could possibly use these to compromise the system.\nThis update corrects flaws in the following subsystems:\n  - ARM64 architecture;\n  - x86 architecture;\n  - Cryptographic API;\n  - Compute Acceleration Framework;\n  - Drivers core;\n  - Null block device driver;\n  - Ublk userspace block driver;\n  - Bluetooth drivers;\n  - Counter interface drivers;\n  - DMA engine subsystem;\n  - DPLL subsystem;\n  - GPU drivers;\n  - HID subsystem;\n  - Intel Trace Hub HW tracing drivers;\n  - IIO ADC drivers;\n  - IIO subsystem;\n  - On-Chip Interconnect management framework;\n  - IRQ chip drivers;\n  - Modular ISDN driver;\n  - LED subsystem;\n  - Multiple devices driver;\n  - UACCE accelerator framework;\n  - MMC subsystem;\n  - Ethernet bonding driver;\n  - Network drivers;\n  - Mellanox network drivers;\n  - NVME drivers;\n  - PHY drivers;\n  - x86 platform drivers;\n  - i.MX PM domains;\n  - SCSI subsystem;\n  - SLIMbus drivers;\n  - SPI subsystem;\n  - TCM subsystem;\n  - W1 Dallas's 1-wire bus driver;\n  - Xen hypervisor drivers;\n  - BTRFS file system;\n  - EFI Variable file system;\n  - exFAT file system;\n  - Ext4 file system;\n  - HFS+ file system;\n  - Network file system (NFS) client;\n  - Network file system (NFS) server daemon;\n  - NTFS3 file system;\n  - SMB network file system;\n  - Scheduler infrastructure;\n  - Netfilter;\n  - NFC subsystem;\n  - Tracing infrastructure;\n  - io_uring subsystem;\n  - BPF subsystem;\n  - Perf events;\n  - Floating proportions library;\n  - Memory management;\n  - Bluetooth subsystem;\n  - CAN network layer;\n  - Ceph Core library;\n  - Networking core;\n  - IPv4 networking;\n  - IPv6 networking;\n  - L2TP protocol;\n  - MAC80211 subsystem;\n  - NET/ROM layer;\n  - Packet sockets;\n  - Network traffic control;\n  - SCTP protocol;\n  - TLS protocol;\n  - Unix domain sockets;\n  - VMware vSockets driver;\n  - Wireless networking;\n  - ALSA AC97 driver;\n  - Generic PCM loopback sound driver;\n  - Creative Sound Blaster X-Fi driver;\n  - AMD SoC Alsa drivers;\n  - Texas InstrumentS Audio (ASoC/HDA) drivers;\n  - USB sound devices;\n  - KVM subsystem;\n(CVE-2024-50004, CVE-2024-58096, CVE-2024-58097, CVE-2025-37926,\nCVE-2025-38201, CVE-2025-38591, CVE-2025-40039, CVE-2025-40082,\nCVE-2025-40149, CVE-2025-68351, CVE-2025-68358, CVE-2025-68365,\nCVE-2025-68725, CVE-2025-68749, CVE-2025-68803, CVE-2025-68823,\nCVE-2025-71160, CVE-2025-71162, CVE-2025-71163, CVE-2025-71180,\nCVE-2025-71182, CVE-2025-71183, CVE-2025-71184, CVE-2025-71185,\nCVE-2025-71186, CVE-2025-71188, CVE-2025-71189, CVE-2025-71190,\nCVE-2025-71191, CVE-2025-71192, CVE-2025-71193, CVE-2025-71194,\nCVE-2025-71195, CVE-2025-71196, CVE-2025-71197, CVE-2025-71198,\nCVE-2025-71199, CVE-2025-71200, CVE-2025-71220, CVE-2025-71222,\nCVE-2025-71224, CVE-2025-71225, CVE-2025-71268, CVE-2026-22976,\nCVE-2026-22977, CVE-2026-22978, CVE-2026-22979, CVE-2026-22980,\nCVE-2026-22982, CVE-2026-22984, CVE-2026-22990, CVE-2026-22991,\nCVE-2026-22992, CVE-2026-22994, CVE-2026-22996, CVE-2026-22997,\nCVE-2026-22998, CVE-2026-22999, CVE-2026-23000, CVE-2026-23001,\nCVE-2026-23003, CVE-2026-23005, CVE-2026-23006, CVE-2026-23010,\nCVE-2026-23011, CVE-2026-23019, CVE-2026-23020, CVE-2026-23021,\nCVE-2026-23025, CVE-2026-23026, CVE-2026-23030, CVE-2026-23031,\nCVE-2026-23032, CVE-2026-23033, CVE-2026-23035, CVE-2026-23037,\nCVE-2026-23038, CVE-2026-23047, CVE-2026-23049, CVE-2026-23050,\nCVE-2026-23053, CVE-2026-23054, CVE-2026-23056, CVE-2026-23057,\nCVE-2026-23058, CVE-2026-23059, CVE-2026-23061, CVE-2026-23062,\nCVE-2026-23063, CVE-2026-23064, CVE-2026-23065, CVE-2026-23068,\nCVE-2026-23069, CVE-2026-23071, CVE-2026-23073, CVE-2026-23075,\nCVE-2026-23076, CVE-2026-23078, CVE-2026-23080, CVE-2026-23083,\nCVE-2026-23084, CVE-2026-23085, CVE-2026-23086, CVE-2026-23087,\nCVE-2026-23088, CVE-2026-23089, CVE-2026-23090, CVE-2026-23091,\nCVE-2026-23093, CVE-2026-23094, CVE-2026-23095, CVE-2026-23096,\nCVE-2026-23097, CVE-2026-23098, CVE-2026-23099, CVE-2026-23101,\nCVE-2026-23102, CVE-2026-23103, CVE-2026-23105, CVE-2026-23107,\nCVE-2026-23108, CVE-2026-23110, CVE-2026-23113, CVE-2026-23116,\nCVE-2026-23119, CVE-2026-23120, CVE-2026-23121, CVE-2026-23123,\nCVE-2026-23124, CVE-2026-23125, CVE-2026-23126, CVE-2026-23128,\nCVE-2026-23129, CVE-2026-23131, CVE-2026-23133, CVE-2026-23135,\nCVE-2026-23136, CVE-2026-23139, CVE-2026-23140, CVE-2026-23141,\nCVE-2026-23142, CVE-2026-23144, CVE-2026-23145, CVE-2026-23146,\nCVE-2026-23148, CVE-2026-23150, CVE-2026-23151, CVE-2026-23156,\nCVE-2026-23159, CVE-2026-23160, CVE-2026-23163, CVE-2026-23164,\nCVE-2026-23166, CVE-2026-23167, CVE-2026-23168, CVE-2026-23170,\nCVE-2026-23172, CVE-2026-23173, CVE-2026-23176, CVE-2026-23178,\nCVE-2026-23179, CVE-2026-23180, CVE-2026-23182, CVE-2026-23187,\nCVE-2026-23190, CVE-2026-23191, CVE-2026-23193, CVE-2026-23198,\nCVE-2026-23200, CVE-2026-23204, CVE-2026-23205, CVE-2026-23206,\nCVE-2026-23212, CVE-2026-23213, CVE-2026-23214, CVE-2026-23215,\nCVE-2026-23216, CVE-2026-23254, CVE-2026-23256, CVE-2026-23257,\nCVE-2026-23258, CVE-2026-23260, CVE-2026-23261, CVE-2026-23262,\nCVE-2026-23264, CVE-2026-23274, CVE-2026-23351, CVE-2026-23394,\nCVE-2026-31419, CVE-2026-31504, CVE-2026-31533, CVE-2026-43033,\nCVE-2026-43077, CVE-2026-43078)\n","status":"published","published":"2026-05-25T17:48:27Z","modified":"2026-11-05T19:03:51.918692229Z","updated_at":"2026-11-05T19:27:26.236035Z"},{"id":"USN-8296-1","title":"linux-fips vulnerabilities","description":"Several security issues were discovered in the Linux kernel.\nAn attacker could possibly use these to compromise the system.\nThis update corrects flaws in the following subsystems:\n  - ARM64 architecture;\n  - x86 architecture;\n  - Compute Acceleration Framework;\n  - Drivers core;\n  - Null block device driver;\n  - Ublk userspace block driver;\n  - Bluetooth drivers;\n  - Counter interface drivers;\n  - DMA engine subsystem;\n  - DPLL subsystem;\n  - GPU drivers;\n  - HID subsystem;\n  - Intel Trace Hub HW tracing drivers;\n  - IIO ADC drivers;\n  - IIO subsystem;\n  - On-Chip Interconnect management framework;\n  - IRQ chip drivers;\n  - Modular ISDN driver;\n  - LED subsystem;\n  - Multiple devices driver;\n  - UACCE accelerator framework;\n  - MMC subsystem;\n  - Ethernet bonding driver;\n  - Network drivers;\n  - Mellanox network drivers;\n  - NVME drivers;\n  - PHY drivers;\n  - x86 platform drivers;\n  - i.MX PM domains;\n  - SCSI subsystem;\n  - SLIMbus drivers;\n  - SPI subsystem;\n  - TCM subsystem;\n  - W1 Dallas's 1-wire bus driver;\n  - Xen hypervisor drivers;\n  - BTRFS file system;\n  - EFI Variable file system;\n  - exFAT file system;\n  - Ext4 file system;\n  - HFS+ file system;\n  - Network file system (NFS) client;\n  - Network file system (NFS) server daemon;\n  - NTFS3 file system;\n  - SMB network file system;\n  - Scheduler infrastructure;\n  - Netfilter;\n  - NFC subsystem;\n  - Tracing infrastructure;\n  - io_uring subsystem;\n  - BPF subsystem;\n  - Perf events;\n  - Floating proportions library;\n  - Memory management;\n  - Bluetooth subsystem;\n  - CAN network layer;\n  - Ceph Core library;\n  - Networking core;\n  - IPv4 networking;\n  - IPv6 networking;\n  - L2TP protocol;\n  - MAC80211 subsystem;\n  - NET/ROM layer;\n  - Network traffic control;\n  - SCTP protocol;\n  - TLS protocol;\n  - Unix domain sockets;\n  - VMware vSockets driver;\n  - Wireless networking;\n  - ALSA AC97 driver;\n  - Generic PCM loopback sound driver;\n  - Creative Sound Blaster X-Fi driver;\n  - AMD SoC Alsa drivers;\n  - Texas InstrumentS Audio (ASoC/HDA) drivers;\n  - USB sound devices;\n  - KVM subsystem;\n(CVE-2024-50004, CVE-2024-58096, CVE-2024-58097, CVE-2025-37926,\nCVE-2025-38201, CVE-2025-38591, CVE-2025-40039, CVE-2025-40082,\nCVE-2025-40149, CVE-2025-68351, CVE-2025-68358, CVE-2025-68365,\nCVE-2025-68725, CVE-2025-68749, CVE-2025-68803, CVE-2025-68823,\nCVE-2025-71160, CVE-2025-71162, CVE-2025-71163, CVE-2025-71180,\nCVE-2025-71182, CVE-2025-71183, CVE-2025-71184, CVE-2025-71185,\nCVE-2025-71186, CVE-2025-71188, CVE-2025-71189, CVE-2025-71190,\nCVE-2025-71191, CVE-2025-71192, CVE-2025-71193, CVE-2025-71194,\nCVE-2025-71195, CVE-2025-71196, CVE-2025-71197, CVE-2025-71198,\nCVE-2025-71199, CVE-2025-71200, CVE-2025-71220, CVE-2025-71222,\nCVE-2025-71224, CVE-2025-71225, CVE-2025-71268, CVE-2026-22976,\nCVE-2026-22977, CVE-2026-22978, CVE-2026-22979, CVE-2026-22980,\nCVE-2026-22982, CVE-2026-22984, CVE-2026-22990, CVE-2026-22991,\nCVE-2026-22992, CVE-2026-22994, CVE-2026-22996, CVE-2026-22997,\nCVE-2026-22998, CVE-2026-22999, CVE-2026-23000, CVE-2026-23001,\nCVE-2026-23003, CVE-2026-23005, CVE-2026-23006, CVE-2026-23010,\nCVE-2026-23011, CVE-2026-23019, CVE-2026-23020, CVE-2026-23021,\nCVE-2026-23025, CVE-2026-23026, CVE-2026-23030, CVE-2026-23031,\nCVE-2026-23032, CVE-2026-23033, CVE-2026-23035, CVE-2026-23037,\nCVE-2026-23038, CVE-2026-23047, CVE-2026-23049, CVE-2026-23050,\nCVE-2026-23053, CVE-2026-23054, CVE-2026-23056, CVE-2026-23057,\nCVE-2026-23058, CVE-2026-23059, CVE-2026-23061, CVE-2026-23062,\nCVE-2026-23063, CVE-2026-23064, CVE-2026-23065, CVE-2026-23068,\nCVE-2026-23069, CVE-2026-23071, CVE-2026-23073, CVE-2026-23075,\nCVE-2026-23076, CVE-2026-23078, CVE-2026-23080, CVE-2026-23083,\nCVE-2026-23084, CVE-2026-23085, CVE-2026-23086, CVE-2026-23087,\nCVE-2026-23088, CVE-2026-23089, CVE-2026-23090, CVE-2026-23091,\nCVE-2026-23093, CVE-2026-23094, CVE-2026-23095, CVE-2026-23096,\nCVE-2026-23097, CVE-2026-23098, CVE-2026-23099, CVE-2026-23101,\nCVE-2026-23102, CVE-2026-23103, CVE-2026-23105, CVE-2026-23107,\nCVE-2026-23108, CVE-2026-23110, CVE-2026-23113, CVE-2026-23116,\nCVE-2026-23119, CVE-2026-23120, CVE-2026-23121, CVE-2026-23123,\nCVE-2026-23124, CVE-2026-23125, CVE-2026-23126, CVE-2026-23128,\nCVE-2026-23129, CVE-2026-23131, CVE-2026-23133, CVE-2026-23135,\nCVE-2026-23136, CVE-2026-23139, CVE-2026-23140, CVE-2026-23141,\nCVE-2026-23142, CVE-2026-23144, CVE-2026-23145, CVE-2026-23146,\nCVE-2026-23148, CVE-2026-23150, CVE-2026-23151, CVE-2026-23156,\nCVE-2026-23159, CVE-2026-23160, CVE-2026-23163, CVE-2026-23164,\nCVE-2026-23166, CVE-2026-23167, CVE-2026-23168, CVE-2026-23170,\nCVE-2026-23172, CVE-2026-23173, CVE-2026-23176, CVE-2026-23178,\nCVE-2026-23179, CVE-2026-23180, CVE-2026-23182, CVE-2026-23187,\nCVE-2026-23190, CVE-2026-23191, CVE-2026-23193, CVE-2026-23198,\nCVE-2026-23200, CVE-2026-23202, CVE-2026-23204, CVE-2026-23205,\nCVE-2026-23206, CVE-2026-23212, CVE-2026-23213, CVE-2026-23214,\nCVE-2026-23215, CVE-2026-23216, CVE-2026-23254, CVE-2026-23256,\nCVE-2026-23257, CVE-2026-23258, CVE-2026-23260, CVE-2026-23261,\nCVE-2026-23262, CVE-2026-23264, CVE-2026-23274, CVE-2026-23351,\nCVE-2026-23394)\n","status":"published","published":"2026-05-22T13:39:49Z","modified":"2026-11-04T20:02:47.669069853Z","updated_at":"2026-11-04T20:16:32.566315Z"},{"id":"USN-8296-2","title":"linux-nvidia-tegra vulnerabilities","description":"Several security issues were discovered in the Linux kernel.\nAn attacker could possibly use these to compromise the system.\nThis update corrects flaws in the following subsystems:\n  - ARM64 architecture;\n  - x86 architecture;\n  - Compute Acceleration Framework;\n  - Drivers core;\n  - Null block device driver;\n  - Ublk userspace block driver;\n  - Bluetooth drivers;\n  - Counter interface drivers;\n  - DMA engine subsystem;\n  - DPLL subsystem;\n  - GPU drivers;\n  - HID subsystem;\n  - Intel Trace Hub HW tracing drivers;\n  - IIO ADC drivers;\n  - IIO subsystem;\n  - On-Chip Interconnect management framework;\n  - IRQ chip drivers;\n  - Modular ISDN driver;\n  - LED subsystem;\n  - Multiple devices driver;\n  - UACCE accelerator framework;\n  - MMC subsystem;\n  - Ethernet bonding driver;\n  - Network drivers;\n  - Mellanox network drivers;\n  - NVME drivers;\n  - PHY drivers;\n  - x86 platform drivers;\n  - i.MX PM domains;\n  - SCSI subsystem;\n  - SLIMbus drivers;\n  - SPI subsystem;\n  - TCM subsystem;\n  - W1 Dallas's 1-wire bus driver;\n  - Xen hypervisor drivers;\n  - BTRFS file system;\n  - EFI Variable file system;\n  - exFAT file system;\n  - Ext4 file system;\n  - HFS+ file system;\n  - Network file system (NFS) client;\n  - Network file system (NFS) server daemon;\n  - NTFS3 file system;\n  - SMB network file system;\n  - Scheduler infrastructure;\n  - Netfilter;\n  - NFC subsystem;\n  - Tracing infrastructure;\n  - io_uring subsystem;\n  - BPF subsystem;\n  - Perf events;\n  - Floating proportions library;\n  - Memory management;\n  - Bluetooth subsystem;\n  - CAN network layer;\n  - Ceph Core library;\n  - Networking core;\n  - IPv4 networking;\n  - IPv6 networking;\n  - L2TP protocol;\n  - MAC80211 subsystem;\n  - NET/ROM layer;\n  - Network traffic control;\n  - SCTP protocol;\n  - TLS protocol;\n  - Unix domain sockets;\n  - VMware vSockets driver;\n  - Wireless networking;\n  - ALSA AC97 driver;\n  - Generic PCM loopback sound driver;\n  - Creative Sound Blaster X-Fi driver;\n  - AMD SoC Alsa drivers;\n  - Texas InstrumentS Audio (ASoC/HDA) drivers;\n  - USB sound devices;\n  - KVM subsystem;\n(CVE-2024-50004, CVE-2024-58096, CVE-2024-58097, CVE-2025-37926,\nCVE-2025-38201, CVE-2025-38591, CVE-2025-40039, CVE-2025-40082,\nCVE-2025-40149, CVE-2025-68351, CVE-2025-68358, CVE-2025-68365,\nCVE-2025-68725, CVE-2025-68749, CVE-2025-68803, CVE-2025-68823,\nCVE-2025-71160, CVE-2025-71162, CVE-2025-71163, CVE-2025-71180,\nCVE-2025-71182, CVE-2025-71183, CVE-2025-71184, CVE-2025-71185,\nCVE-2025-71186, CVE-2025-71188, CVE-2025-71189, CVE-2025-71190,\nCVE-2025-71191, CVE-2025-71192, CVE-2025-71193, CVE-2025-71194,\nCVE-2025-71195, CVE-2025-71196, CVE-2025-71197, CVE-2025-71198,\nCVE-2025-71199, CVE-2025-71200, CVE-2025-71220, CVE-2025-71222,\nCVE-2025-71224, CVE-2025-71225, CVE-2025-71268, CVE-2026-22976,\nCVE-2026-22977, CVE-2026-22978, CVE-2026-22979, CVE-2026-22980,\nCVE-2026-22982, CVE-2026-22984, CVE-2026-22990, CVE-2026-22991,\nCVE-2026-22992, CVE-2026-22994, CVE-2026-22996, CVE-2026-22997,\nCVE-2026-22998, CVE-2026-22999, CVE-2026-23000, CVE-2026-23001,\nCVE-2026-23003, CVE-2026-23005, CVE-2026-23006, CVE-2026-23010,\nCVE-2026-23011, CVE-2026-23019, CVE-2026-23020, CVE-2026-23021,\nCVE-2026-23025, CVE-2026-23026, CVE-2026-23030, CVE-2026-23031,\nCVE-2026-23032, CVE-2026-23033, CVE-2026-23035, CVE-2026-23037,\nCVE-2026-23038, CVE-2026-23047, CVE-2026-23049, CVE-2026-23050,\nCVE-2026-23053, CVE-2026-23054, CVE-2026-23056, CVE-2026-23057,\nCVE-2026-23058, CVE-2026-23059, CVE-2026-23061, CVE-2026-23062,\nCVE-2026-23063, CVE-2026-23064, CVE-2026-23065, CVE-2026-23068,\nCVE-2026-23069, CVE-2026-23071, CVE-2026-23073, CVE-2026-23075,\nCVE-2026-23076, CVE-2026-23078, CVE-2026-23080, CVE-2026-23083,\nCVE-2026-23084, CVE-2026-23085, CVE-2026-23086, CVE-2026-23087,\nCVE-2026-23088, CVE-2026-23089, CVE-2026-23090, CVE-2026-23091,\nCVE-2026-23093, CVE-2026-23094, CVE-2026-23095, CVE-2026-23096,\nCVE-2026-23097, CVE-2026-23098, CVE-2026-23099, CVE-2026-23101,\nCVE-2026-23102, CVE-2026-23103, CVE-2026-23105, CVE-2026-23107,\nCVE-2026-23108, CVE-2026-23110, CVE-2026-23113, CVE-2026-23116,\nCVE-2026-23119, CVE-2026-23120, CVE-2026-23121, CVE-2026-23123,\nCVE-2026-23124, CVE-2026-23125, CVE-2026-23126, CVE-2026-23128,\nCVE-2026-23129, CVE-2026-23131, CVE-2026-23133, CVE-2026-23135,\nCVE-2026-23136, CVE-2026-23139, CVE-2026-23140, CVE-2026-23141,\nCVE-2026-23142, CVE-2026-23144, CVE-2026-23145, CVE-2026-23146,\nCVE-2026-23148, CVE-2026-23150, CVE-2026-23151, CVE-2026-23156,\nCVE-2026-23159, CVE-2026-23160, CVE-2026-23163, CVE-2026-23164,\nCVE-2026-23166, CVE-2026-23167, CVE-2026-23168, CVE-2026-23170,\nCVE-2026-23172, CVE-2026-23173, CVE-2026-23176, CVE-2026-23178,\nCVE-2026-23179, CVE-2026-23180, CVE-2026-23182, CVE-2026-23187,\nCVE-2026-23190, CVE-2026-23191, CVE-2026-23193, CVE-2026-23198,\nCVE-2026-23200, CVE-2026-23202, CVE-2026-23204, CVE-2026-23205,\nCVE-2026-23206, CVE-2026-23212, CVE-2026-23213, CVE-2026-23214,\nCVE-2026-23215, CVE-2026-23216, CVE-2026-23254, CVE-2026-23256,\nCVE-2026-23257, CVE-2026-23258, CVE-2026-23260, CVE-2026-23261,\nCVE-2026-23262, CVE-2026-23264, CVE-2026-23274, CVE-2026-23351,\nCVE-2026-23394)\n","status":"published","published":"2026-05-25T16:46:50Z","modified":"2026-11-04T20:02:40.473452713Z","updated_at":"2026-11-04T20:16:32.566315Z"},{"id":"USN-8310-1","title":"linux-azure, linux-azure-6.17 vulnerabilities","description":"\nIt was discovered that the Linux kernel algif_aead module did not properly\nhandle in-place cryptographic operations. This flaw is known as Copy Fail.\nA local attacker could use this to escalate privileges, or possibly escape\na container. (CVE-2026-31431)\n\nSeveral security issues were discovered in the Linux kernel.\nAn attacker could possibly use these to compromise the system.\nThis update corrects flaws in the following subsystems:\n  - S390 architecture;\n  - Cryptographic API;\n  - GPU drivers;\n  - Ethernet bonding driver;\n  - Microsoft Azure Network Adapter (MANA) driver;\n  - Network file system (NFS) server daemon;\n  - Distributed Switch Architecture;\n  - Netfilter;\n  - Control group (cgroup);\n  - Kernel kexec() syscall;\n  - Memory management;\n  - MAC80211 subsystem;\n  - Multipath TCP;\n  - Packet sockets;\n  - TLS protocol;\n  - Unix domain sockets;\n(CVE-2025-71088, CVE-2025-71090, CVE-2025-71127, CVE-2025-71134,\nCVE-2025-71139, CVE-2025-71141, CVE-2025-71142, CVE-2025-71144,\nCVE-2025-71152, CVE-2025-71155, CVE-2026-23274, CVE-2026-23351,\nCVE-2026-23394, CVE-2026-23454, CVE-2026-31419, CVE-2026-31504,\nCVE-2026-31533, CVE-2026-43033, CVE-2026-43077, CVE-2026-43078,\nCVE-2026-43276)\n","status":"published","published":"2026-05-26T18:56:07Z","modified":"2026-11-05T19:03:53.161057114Z","updated_at":"2026-11-05T19:27:26.236035Z"},{"id":"USN-8374-1","title":"linux-aws-6.17, linux-gcp, linux-gcp-6.17 vulnerabilities","description":"It was discovered that the Linux kernel algif_aead module did not properly\nhandle in-place cryptographic operations. This flaw is known as Copy Fail.\nA local attacker could use this to escalate privileges, or possibly escape\na container. (CVE-2026-31431)\n\nIt was discovered that the Linux kernel did not properly handle shared page\nfragments during socket buffer operations, collectively known as Dirty\nFrag. A logic flaw existed in the XFRM ESP-in-TCP subsystem and in the\nRxRPC networking subsystem when processing paged fragments. A local\nattacker could use this to escalate privileges, or possibly escape a\ncontainer. (CVE-2026-43284, CVE-2026-43500, CVE-2026-45998, CVE-2026-46000)\n\nIt was discovered that a logic flaw existed in the XFRM ESP-in-TCP\nsubsystem in the Linux kernel when handling socket buffer fragments. This\nflaw is known as Fragnesia. A local attacker could use this to escalate\nprivileges, or possibly escape a container. (CVE-2026-43503,\nCVE-2026-46300)\n\nQualys discovered that a race condition existed in the ptrace subsystem of\nthe Linux kernel when privileged processes are exiting. An unprivileged\nlocal attacker could use this issue to expose sensitive information.\n(CVE-2026-46333)\n\nTristan Madani discovered that Ubuntu Linux kernel 6.8, 6.17 and 7.0\ncontain a memory leak when handling AppArmor notifications. A local\nattacker could use this to cause resource exhaustion. (CVE-2026-47326)\n\nTristan Madani discovered that Ubuntu Linux kernel 6.8, 6.17 and 7.0\ncontain a NULL pointer dereference when handling AppArmor notifications. A\nlocal attacker could use this to cause a kernel oops. (CVE-2026-47327)\n\nTristan Madani discovered that Ubuntu Linux kernel 6.8, 6.17 and 7.0\ncontained an invalid free when handling AppArmor notifications. A local\nattacker could use this to corrupt kernel memory. (CVE-2026-47328)\n\nTristan Madani discovered that Ubuntu Linux kernel 6.8, 6.17 and 7.0\ncontained insufficient validation of AppArmor notification responses. A\nlocal attacker could use this to allow crafted responses to be processed.\n(CVE-2026-47329)\n\nTristan Madani discovered that Ubuntu Linux kernel 6.8, 6.17 and 7.0 used\nan uninitialized variable when handling AppArmor notifications. A local\nattacker could use this to cause incorrect caching of data.\n(CVE-2026-47330)\n\nTristan Madani discovered that Ubuntu Linux kernel 6.8, 6.17 and 7.0\ncontained an out-of-bounds (OOB) read when handling AppArmor notifications.\nA local attacker could use this to cause information disclosure of kernel\nmemory. (CVE-2026-47332)\n\nTristan Madani discovered that Ubuntu Linux kernel 6.8, 6.17 and 7.0\ncontained a out-of-bounds (OOB) read when handling AppArmor notifications.\nA local attacker could use this to cause kernel memory corruption and,\ntheoretically, influence processing of AppArmor policies. (CVE-2026-47333)\n\nTristan Madani discovered that Ubuntu Linux kernel 6.8, 6.17 and 7.0\ncontained incorrect holding of locks when handling AppArmor notifications.\nA local attacker could use this to cause a kernel panic or deadlock.\n(CVE-2026-47334)\n\nTristan Madani and Trevor Lawrence have each independently discovered that\nUbuntu Linux kernel 6.8, 6.17 and 7.0 contained a NULL pointer dereference\nwhen handling AppArmor network socket mediation. A local attacker could use\nthis to cause a kernel oops. (CVE-2026-47337)\n\nSeveral security issues were discovered in the Linux kernel.\nAn attacker could possibly use these to compromise the system.\nThis update corrects flaws in the following subsystems:\n  - S390 architecture;\n  - Cryptographic API;\n  - GPU drivers;\n  - Ethernet bonding driver;\n  - Network file system (NFS) server daemon;\n  - Distributed Switch Architecture;\n  - Netfilter;\n  - Control group (cgroup);\n  - Kernel kexec() syscall;\n  - Memory management;\n  - MAC80211 subsystem;\n  - Multipath TCP;\n  - Packet sockets;\n  - RDS protocol;\n  - RxRPC session sockets;\n  - TLS protocol;\n  - Unix domain sockets;\n  - AppArmor security module;\n(CVE-2025-71088, CVE-2025-71090, CVE-2025-71127, CVE-2025-71134,\nCVE-2025-71139, CVE-2025-71141, CVE-2025-71142, CVE-2025-71144,\nCVE-2025-71152, CVE-2025-71155, CVE-2026-23274, CVE-2026-23351,\nCVE-2026-23394, CVE-2026-31419, CVE-2026-31504, CVE-2026-31533,\nCVE-2026-31676, CVE-2026-43033, CVE-2026-43077, CVE-2026-43078,\nCVE-2026-43494, CVE-2026-45966, CVE-2026-46028)\n","status":"published","published":"2026-06-02T18:00:00Z","modified":"2026-11-07T01:45:14.756351868Z","updated_at":"2026-11-07T01:57:06.567161Z"},{"id":"USN-8393-1","title":"linux-azure-fips vulnerabilities","description":"\nIt was discovered that the Linux kernel algif_aead module did not properly\nhandle in-place cryptographic operations. This flaw is known as Copy Fail.\nA local attacker could use this to escalate privileges, or possibly escape\na container. (CVE-2026-31431)\n\nIt was discovered that the Linux kernel did not properly handle shared page\nfragments during socket buffer operations, collectively known as Dirty\nFrag. A logic flaw existed in the XFRM ESP-in-TCP subsystem and in the\nRxRPC networking subsystem when processing paged fragments. A local\nattacker could use this to escalate privileges, or possibly escape a\ncontainer. (CVE-2026-43284, CVE-2026-43500, CVE-2026-45998, CVE-2026-46000)\n\nIt was discovered that a logic flaw existed in the XFRM ESP-in-TCP\nsubsystem in the Linux kernel when handling socket buffer fragments. This\nflaw is known as Fragnesia. A local attacker could use this to escalate\nprivileges, or possibly escape a container. (CVE-2026-43503,\nCVE-2026-46300)\n\nQualys discovered that a race condition existed in the ptrace subsystem of\nthe Linux kernel when privileged processes are exiting. An unprivileged\nlocal attacker could use this issue to expose sensitive information.\n(CVE-2026-46333)\n\nTristan Madani discovered that Ubuntu Linux kernel 6.8, 6.17 and 7.0\ncontain a memory leak when handling AppArmor notifications. A local\nattacker could use this to cause resource exhaustion. (CVE-2026-47326)\n\nTristan Madani discovered that Ubuntu Linux kernel 6.8, 6.17 and 7.0\ncontain a NULL pointer dereference when handling AppArmor notifications. A\nlocal attacker could use this to cause a kernel oops. (CVE-2026-47327)\n\nTristan Madani discovered that Ubuntu Linux kernel 6.8, 6.17 and 7.0\ncontained an invalid free when handling AppArmor notifications. A local\nattacker could use this to corrupt kernel memory. (CVE-2026-47328)\n\nTristan Madani discovered that Ubuntu Linux kernel 6.8, 6.17 and 7.0\ncontained insufficient validation of AppArmor notification responses. A\nlocal attacker could use this to allow crafted responses to be processed.\n(CVE-2026-47329)\n\nTristan Madani discovered that Ubuntu Linux kernel 6.8, 6.17 and 7.0 used\nan uninitialized variable when handling AppArmor notifications. A local\nattacker could use this to cause incorrect caching of data.\n(CVE-2026-47330)\n\nTristan Madani discovered that Ubuntu Linux kernel 6.8 contained a use-\nafter-free (UAF) bug. A local attacker could use this to cause memory\ncorruption and, theoretically, arbitrary code execution. (CVE-2026-47331)\n\nTristan Madani discovered that Ubuntu Linux kernel 6.8, 6.17 and 7.0\ncontained an out-of-bounds (OOB) read when handling AppArmor notifications.\nA local attacker could use this to cause information disclosure of kernel\nmemory. (CVE-2026-47332)\n\nTristan Madani discovered that Ubuntu Linux kernel 6.8, 6.17 and 7.0\ncontained a out-of-bounds (OOB) read when handling AppArmor notifications.\nA local attacker could use this to cause kernel memory corruption and,\ntheoretically, influence processing of AppArmor policies. (CVE-2026-47333)\n\nTristan Madani discovered that Ubuntu Linux kernel 6.8, 6.17 and 7.0\ncontained incorrect holding of locks when handling AppArmor notifications.\nA local attacker could use this to cause a kernel panic or deadlock.\n(CVE-2026-47334)\n\nTristan Madani discovered that Ubuntu Linux kernel 6.8 contained a NULL\npointer dereference when handling AppArmor notifications. A local attacker\ncould use this to cause a kernel panic. (CVE-2026-47335)\n\nTristan Madani discovered that Ubuntu Linux kernel 6.8 used an\nuninitialized variable when handling AppArmor AF_INET/AF_INET6 socket\nmediation. A local attacker could use this to influence processing of fine-\ngrained network socket mediation. (CVE-2026-47336)\n\nTristan Madani and Trevor Lawrence have each independently discovered that\nUbuntu Linux kernel 6.8, 6.17 and 7.0 contained a NULL pointer dereference\nwhen handling AppArmor network socket mediation. A local attacker could use\nthis to cause a kernel oops. (CVE-2026-47337)\n\nSeveral security issues were discovered in the Linux kernel.\nAn attacker could possibly use these to compromise the system.\nThis update corrects flaws in the following subsystems:\n  - ARM64 architecture;\n  - x86 architecture;\n  - Cryptographic API;\n  - Compute Acceleration Framework;\n  - Drivers core;\n  - Null block device driver;\n  - Ublk userspace block driver;\n  - Bluetooth drivers;\n  - Counter interface drivers;\n  - DMA engine subsystem;\n  - DPLL subsystem;\n  - GPU drivers;\n  - HID subsystem;\n  - Intel Trace Hub HW tracing drivers;\n  - IIO ADC drivers;\n  - IIO subsystem;\n  - On-Chip Interconnect management framework;\n  - IRQ chip drivers;\n  - Modular ISDN driver;\n  - LED subsystem;\n  - Multiple devices driver;\n  - UACCE accelerator framework;\n  - MMC subsystem;\n  - Ethernet bonding driver;\n  - Network drivers;\n  - Mellanox network drivers;\n  - NVME drivers;\n  - PHY drivers;\n  - x86 platform drivers;\n  - i.MX PM domains;\n  - SCSI subsystem;\n  - SLIMbus drivers;\n  - SPI subsystem;\n  - TCM subsystem;\n  - W1 Dallas's 1-wire bus driver;\n  - Xen hypervisor drivers;\n  - BTRFS file system;\n  - EFI Variable file system;\n  - exFAT file system;\n  - Ext4 file system;\n  - HFS+ file system;\n  - Network file system (NFS) client;\n  - Network file system (NFS) server daemon;\n  - NTFS3 file system;\n  - SMB network file system;\n  - Scheduler infrastructure;\n  - Netfilter;\n  - NFC subsystem;\n  - Tracing infrastructure;\n  - io_uring subsystem;\n  - BPF subsystem;\n  - Perf events;\n  - Floating proportions library;\n  - Memory management;\n  - Bluetooth subsystem;\n  - CAN network layer;\n  - Ceph Core library;\n  - Networking core;\n  - IPv4 networking;\n  - IPv6 networking;\n  - L2TP protocol;\n  - MAC80211 subsystem;\n  - NET/ROM layer;\n  - Packet sockets;\n  - RDS protocol;\n  - RxRPC session sockets;\n  - Network traffic control;\n  - SCTP protocol;\n  - TLS protocol;\n  - Unix domain sockets;\n  - VMware vSockets driver;\n  - Wireless networking;\n  - ALSA AC97 driver;\n  - Generic PCM loopback sound driver;\n  - Creative Sound Blaster X-Fi driver;\n  - AMD SoC Alsa drivers;\n  - Texas InstrumentS Audio (ASoC/HDA) drivers;\n  - USB sound devices;\n  - KVM subsystem;\n(CVE-2024-50004, CVE-2024-58096, CVE-2024-58097, CVE-2025-37926,\nCVE-2025-38201, CVE-2025-38591, CVE-2025-40039, CVE-2025-40082,\nCVE-2025-40149, CVE-2025-68351, CVE-2025-68358, CVE-2025-68365,\nCVE-2025-68725, CVE-2025-68749, CVE-2025-68803, CVE-2025-68823,\nCVE-2025-71160, CVE-2025-71162, CVE-2025-71163, CVE-2025-71180,\nCVE-2025-71182, CVE-2025-71183, CVE-2025-71184, CVE-2025-71185,\nCVE-2025-71186, CVE-2025-71188, CVE-2025-71189, CVE-2025-71190,\nCVE-2025-71191, CVE-2025-71192, CVE-2025-71193, CVE-2025-71194,\nCVE-2025-71195, CVE-2025-71196, CVE-2025-71197, CVE-2025-71198,\nCVE-2025-71199, CVE-2025-71200, CVE-2025-71220, CVE-2025-71222,\nCVE-2025-71224, CVE-2025-71225, CVE-2025-71268, CVE-2026-22976,\nCVE-2026-22977, CVE-2026-22978, CVE-2026-22979, CVE-2026-22980,\nCVE-2026-22982, CVE-2026-22984, CVE-2026-22990, CVE-2026-22991,\nCVE-2026-22992, CVE-2026-22994, CVE-2026-22996, CVE-2026-22997,\nCVE-2026-22998, CVE-2026-22999, CVE-2026-23000, CVE-2026-23001,\nCVE-2026-23003, CVE-2026-23005, CVE-2026-23006, CVE-2026-23010,\nCVE-2026-23011, CVE-2026-23019, CVE-2026-23020, CVE-2026-23021,\nCVE-2026-23025, CVE-2026-23026, CVE-2026-23030, CVE-2026-23031,\nCVE-2026-23032, CVE-2026-23033, CVE-2026-23035, CVE-2026-23037,\nCVE-2026-23038, CVE-2026-23047, CVE-2026-23049, CVE-2026-23050,\nCVE-2026-23053, CVE-2026-23054, CVE-2026-23056, CVE-2026-23057,\nCVE-2026-23058, CVE-2026-23059, CVE-2026-23061, CVE-2026-23062,\nCVE-2026-23063, CVE-2026-23064, CVE-2026-23065, CVE-2026-23068,\nCVE-2026-23069, CVE-2026-23071, CVE-2026-23073, CVE-2026-23075,\nCVE-2026-23076, CVE-2026-23078, CVE-2026-23080, CVE-2026-23083,\nCVE-2026-23084, CVE-2026-23085, CVE-2026-23086, CVE-2026-23087,\nCVE-2026-23088, CVE-2026-23089, CVE-2026-23090, CVE-2026-23091,\nCVE-2026-23093, CVE-2026-23094, CVE-2026-23095, CVE-2026-23096,\nCVE-2026-23097, CVE-2026-23098, CVE-2026-23099, CVE-2026-23101,\nCVE-2026-23102, CVE-2026-23103, CVE-2026-23105, CVE-2026-23107,\nCVE-2026-23108, CVE-2026-23110, CVE-2026-23113, CVE-2026-23116,\nCVE-2026-23119, CVE-2026-23120, CVE-2026-23121, CVE-2026-23123,\nCVE-2026-23124, CVE-2026-23125, CVE-2026-23126, CVE-2026-23128,\nCVE-2026-23129, CVE-2026-23131, CVE-2026-23133, CVE-2026-23135,\nCVE-2026-23136, CVE-2026-23139, CVE-2026-23140, CVE-2026-23141,\nCVE-2026-23142, CVE-2026-23144, CVE-2026-23145, CVE-2026-23146,\nCVE-2026-23148, CVE-2026-23150, CVE-2026-23151, CVE-2026-23156,\nCVE-2026-23159, CVE-2026-23160, CVE-2026-23163, CVE-2026-23164,\nCVE-2026-23166, CVE-2026-23167, CVE-2026-23168, CVE-2026-23170,\nCVE-2026-23172, CVE-2026-23173, CVE-2026-23176, CVE-2026-23178,\nCVE-2026-23179, CVE-2026-23180, CVE-2026-23182, CVE-2026-23187,\nCVE-2026-23190, CVE-2026-23191, CVE-2026-23193, CVE-2026-23198,\nCVE-2026-23200, CVE-2026-23202, CVE-2026-23204, CVE-2026-23205,\nCVE-2026-23206, CVE-2026-23212, CVE-2026-23213, CVE-2026-23214,\nCVE-2026-23215, CVE-2026-23216, CVE-2026-23254, CVE-2026-23256,\nCVE-2026-23257, CVE-2026-23258, CVE-2026-23260, CVE-2026-23261,\nCVE-2026-23262, CVE-2026-23264, CVE-2026-23274, CVE-2026-23351,\nCVE-2026-23394, CVE-2026-31419, CVE-2026-31504, CVE-2026-31533,\nCVE-2026-31676, CVE-2026-43033, CVE-2026-43077, CVE-2026-43078,\nCVE-2026-43494, CVE-2026-46028)\n","status":"published","published":"2026-06-04T22:10:25Z","modified":"2026-11-07T01:45:07.221179684Z","updated_at":"2026-11-07T01:57:16.198641Z"},{"id":"USN-8440-1","title":"linux-azure-6.8 vulnerabilities","description":"Josh Eads, Kristoffer Janke, Eduardo Vela Nava, Tavis Ormandy, and Matteo\nRizzo discovered that some AMD Zen processors did not properly verify the\nsignature of CPU microcode. This flaw is known as EntrySign. A privileged\nattacker could possibly use this issue to cause load malicious CPU\nmicrocode causing loss of integrity and confidentiality. (CVE-2024-36347)\n\nIt was discovered that the Linux kernel algif_aead module did not properly\nhandle in-place cryptographic operations. This flaw is known as Copy Fail.\nA local attacker could use this to escalate privileges, or possibly escape\na container. (CVE-2026-31431)\n\nIt was discovered that the Linux kernel did not properly handle shared page\nfragments during socket buffer operations, collectively known as Dirty\nFrag. A logic flaw existed in the XFRM ESP-in-TCP subsystem and in the\nRxRPC networking subsystem when processing paged fragments. A local\nattacker could use this to escalate privileges, or possibly escape a\ncontainer. (CVE-2026-43284, CVE-2026-43500, CVE-2026-45998, CVE-2026-46000)\n\nIt was discovered that a logic flaw existed in the XFRM ESP-in-TCP\nsubsystem in the Linux kernel when handling socket buffer fragments. This\nflaw is known as Fragnesia. A local attacker could use this to escalate\nprivileges, or possibly escape a container. (CVE-2026-43503,\nCVE-2026-46300)\n\nQualys discovered that a race condition existed in the ptrace subsystem of\nthe Linux kernel when privileged processes are exiting. An unprivileged\nlocal attacker could use this issue to expose sensitive information.\n(CVE-2026-46333)\n\nTristan Madani discovered that Ubuntu Linux kernel 6.8, 6.17 and 7.0\ncontain a memory leak when handling AppArmor notifications. A local\nattacker could use this to cause resource exhaustion. (CVE-2026-47326)\n\nTristan Madani discovered that Ubuntu Linux kernel 6.8, 6.17 and 7.0\ncontain a NULL pointer dereference when handling AppArmor notifications. A\nlocal attacker could use this to cause a kernel oops. (CVE-2026-47327)\n\nTristan Madani discovered that Ubuntu Linux kernel 6.8, 6.17 and 7.0\ncontained an invalid free when handling AppArmor notifications. A local\nattacker could use this to corrupt kernel memory. (CVE-2026-47328)\n\nTristan Madani discovered that Ubuntu Linux kernel 6.8, 6.17 and 7.0\ncontained insufficient validation of AppArmor notification responses. A\nlocal attacker could use this to allow crafted responses to be processed.\n(CVE-2026-47329)\n\nTristan Madani discovered that Ubuntu Linux kernel 6.8, 6.17 and 7.0 used\nan uninitialized variable when handling AppArmor notifications. A local\nattacker could use this to cause incorrect caching of data.\n(CVE-2026-47330)\n\nTristan Madani discovered that Ubuntu Linux kernel 6.8 contained a use-\nafter-free (UAF) bug. A local attacker could use this to cause memory\ncorruption and, theoretically, arbitrary code execution. (CVE-2026-47331)\n\nTristan Madani discovered that Ubuntu Linux kernel 6.8, 6.17 and 7.0\ncontained an out-of-bounds (OOB) read when handling AppArmor notifications.\nA local attacker could use this to cause information disclosure of kernel\nmemory. (CVE-2026-47332)\n\nTristan Madani discovered that Ubuntu Linux kernel 6.8, 6.17 and 7.0\ncontained a out-of-bounds (OOB) read when handling AppArmor notifications.\nA local attacker could use this to cause kernel memory corruption and,\ntheoretically, influence processing of AppArmor policies. (CVE-2026-47333)\n\nTristan Madani discovered that Ubuntu Linux kernel 6.8, 6.17 and 7.0\ncontained incorrect holding of locks when handling AppArmor notifications.\nA local attacker could use this to cause a kernel panic or deadlock.\n(CVE-2026-47334)\n\nTristan Madani discovered that Ubuntu Linux kernel 6.8 contained a NULL\npointer dereference when handling AppArmor notifications. A local attacker\ncould use this to cause a kernel panic. (CVE-2026-47335)\n\nTristan Madani discovered that Ubuntu Linux kernel 6.8 used an\nuninitialized variable when handling AppArmor AF_INET/AF_INET6 socket\nmediation. A local attacker could use this to influence processing of fine-\ngrained network socket mediation. (CVE-2026-47336)\n\nTristan Madani and Trevor Lawrence have each independently discovered that\nUbuntu Linux kernel 6.8, 6.17 and 7.0 contained a NULL pointer dereference\nwhen handling AppArmor network socket mediation. A local attacker could use\nthis to cause a kernel oops. (CVE-2026-47337)\n\nSeveral security issues were discovered in the Linux kernel.\nAn attacker could possibly use these to compromise the system.\nThis update corrects flaws in the following subsystems:\n  - ARM64 architecture;\n  - MIPS architecture;\n  - PowerPC architecture;\n  - x86 architecture;\n  - Block layer subsystem;\n  - Cryptographic API;\n  - Compute Acceleration Framework;\n  - ACPI drivers;\n  - Drivers core;\n  - Network block device driver;\n  - Null block device driver;\n  - Ublk userspace block driver;\n  - Bluetooth drivers;\n  - Character device driver;\n  - TPM device driver;\n  - Clock framework and drivers;\n  - Data acquisition framework and drivers;\n  - Counter interface drivers;\n  - Hardware crypto device drivers;\n  - DMA engine subsystem;\n  - DPLL subsystem;\n  - GPU drivers;\n  - HID subsystem;\n  - Hardware monitoring drivers;\n  - Intel Trace Hub HW tracing drivers;\n  - IIO ADC drivers;\n  - IIO subsystem;\n  - InfiniBand drivers;\n  - Input Device core drivers;\n  - On-Chip Interconnect management framework;\n  - IOMMU subsystem;\n  - IRQ chip drivers;\n  - Modular ISDN driver;\n  - LED subsystem;\n  - Macintosh device drivers;\n  - Multiple devices driver;\n  - Media drivers;\n  - UACCE accelerator framework;\n  - MMC subsystem;\n  - Ethernet bonding driver;\n  - Network drivers;\n  - Mellanox network drivers;\n  - STMicroelectronics network drivers;\n  - Ethernet team driver;\n  - MediaTek network drivers;\n  - NVME drivers;\n  - PA-RISC drivers;\n  - PHY drivers;\n  - Chrome hardware platform drivers;\n  - x86 platform drivers;\n  - i.MX PM domains;\n  - Voltage and Current Regulator drivers;\n  - SCSI subsystem;\n  - SLIMbus drivers;\n  - SPI subsystem;\n  - Media Oriented Systems Transport (MOST) driver;\n  - Realtek RTL8723BS SDIO drivers;\n  - TCM subsystem;\n  - USB Host Controller drivers;\n  - USB Type-C Connector System Software Interface driver;\n  - Backlight driver;\n  - W1 Dallas's 1-wire bus driver;\n  - Watchdog drivers;\n  - Xen hypervisor drivers;\n  - BFS file system;\n  - BTRFS file system;\n  - EFI Variable file system;\n  - exFAT file system;\n  - Ext4 file system;\n  - F2FS file system;\n  - FUSE (File system in Userspace);\n  - HFS+ file system;\n  - File systems infrastructure;\n  - Journaling layer for block devices (JBD2);\n  - Network file system (NFS) client;\n  - Network file system (NFS) server daemon;\n  - File system notification infrastructure;\n  - NTFS3 file system;\n  - OCFS2 file system;\n  - SMB network file system;\n  - BPF subsystem;\n  - Ethernet bridge;\n  - Scheduler infrastructure;\n  - Netfilter;\n  - NFC subsystem;\n  - Tracing infrastructure;\n  - io_uring subsystem;\n  - Perf events;\n  - Locking primitives;\n  - Shadow Call Stack mechanism;\n  - Floating proportions library;\n  - Memory management;\n  - Bluetooth subsystem;\n  - CAIF protocol;\n  - CAN network layer;\n  - Ceph Core library;\n  - Networking core;\n  - Ethtool driver;\n  - Handshake API;\n  - HSR network protocol;\n  - IPv4 networking;\n  - IPv6 networking;\n  - L2TP protocol;\n  - MAC80211 subsystem;\n  - Multipath TCP;\n  - NET/ROM layer;\n  - Open vSwitch;\n  - Packet sockets;\n  - RDS protocol;\n  - Rose network layer;\n  - RxRPC session sockets;\n  - Network traffic control;\n  - SCTP protocol;\n  - Network sockets;\n  - Sun RPC protocol;\n  - TLS protocol;\n  - Unix domain sockets;\n  - VMware vSockets driver;\n  - Wireless networking;\n  - Integrity Measurement Architecture(IMA) framework;\n  - Key management;\n  - Simplified Mandatory Access Control Kernel framework;\n  - ALSA AC97 driver;\n  - Generic PCM loopback sound driver;\n  - FireWire sound drivers;\n  - HD-audio driver;\n  - Turtle Beach Wavefront ALSA driver;\n  - Creative Sound Blaster X-Fi driver;\n  - AMD SoC Alsa drivers;\n  - Texas InstrumentS Audio (ASoC/HDA) drivers;\n  - STMicroelectronics SoC drivers;\n  - USB sound devices;\n  - KVM subsystem;\n(CVE-2024-50004, CVE-2024-57795, CVE-2024-58096, CVE-2024-58097,\nCVE-2025-22022, CVE-2025-22111, CVE-2025-37926, CVE-2025-38022,\nCVE-2025-38201, CVE-2025-38234, CVE-2025-38591, CVE-2025-40039,\nCVE-2025-40082, CVE-2025-40149, CVE-2025-40164, CVE-2025-40325,\nCVE-2025-68206, CVE-2025-68254, CVE-2025-68255, CVE-2025-68256,\nCVE-2025-68257, CVE-2025-68258, CVE-2025-68259, CVE-2025-68261,\nCVE-2025-68263, CVE-2025-68264, CVE-2025-68265, CVE-2025-68266,\nCVE-2025-68291, CVE-2025-68325, CVE-2025-68332, CVE-2025-68335,\nCVE-2025-68336, CVE-2025-68337, CVE-2025-68344, CVE-2025-68345,\nCVE-2025-68346, CVE-2025-68347, CVE-2025-68349, CVE-2025-68351,\nCVE-2025-68354, CVE-2025-68358, CVE-2025-68362, CVE-2025-68363,\nCVE-2025-68364, CVE-2025-68365, CVE-2025-68366, CVE-2025-68367,\nCVE-2025-68369, CVE-2025-68371, CVE-2025-68372, CVE-2025-68374,\nCVE-2025-68378, CVE-2025-68379, CVE-2025-68380, CVE-2025-68724,\nCVE-2025-68725, CVE-2025-68727, CVE-2025-68728, CVE-2025-68732,\nCVE-2025-68733, CVE-2025-68740, CVE-2025-68741, CVE-2025-68742,\nCVE-2025-68744, CVE-2025-68746, CVE-2025-68749, CVE-2025-68753,\nCVE-2025-68755, CVE-2025-68756, CVE-2025-68757, CVE-2025-68758,\nCVE-2025-68759, CVE-2025-68763, CVE-2025-68764, CVE-2025-68765,\nCVE-2025-68766, CVE-2025-68767, CVE-2025-68769, CVE-2025-68770,\nCVE-2025-68771, CVE-2025-68772, CVE-2025-68773, CVE-2025-68774,\nCVE-2025-68775, CVE-2025-68776, CVE-2025-68777, CVE-2025-68778,\nCVE-2025-68780, CVE-2025-68782, CVE-2025-68783, CVE-2025-68785,\nCVE-2025-68786, CVE-2025-68787, CVE-2025-68788, CVE-2025-68794,\nCVE-2025-68795, CVE-2025-68796, CVE-2025-68797, CVE-2025-68798,\nCVE-2025-68799, CVE-2025-68800, CVE-2025-68801, CVE-2025-68803,\nCVE-2025-68804, CVE-2025-68806, CVE-2025-68808, CVE-2025-68809,\nCVE-2025-68810, CVE-2025-68811, CVE-2025-68813, CVE-2025-68814,\nCVE-2025-68815, CVE-2025-68816, CVE-2025-68817, CVE-2025-68818,\nCVE-2025-68819, CVE-2025-68820, CVE-2025-68821, CVE-2025-68823,\nCVE-2025-71064, CVE-2025-71065, CVE-2025-71066, CVE-2025-71067,\nCVE-2025-71068, CVE-2025-71069, CVE-2025-71071, CVE-2025-71072,\nCVE-2025-71075, CVE-2025-71077, CVE-2025-71078, CVE-2025-71079,\nCVE-2025-71081, CVE-2025-71082, CVE-2025-71083, CVE-2025-71084,\nCVE-2025-71085, CVE-2025-71086, CVE-2025-71087, CVE-2025-71088,\nCVE-2025-71089, CVE-2025-71091, CVE-2025-71093, CVE-2025-71094,\nCVE-2025-71095, CVE-2025-71096, CVE-2025-71097, CVE-2025-71098,\nCVE-2025-71101, CVE-2025-71102, CVE-2025-71104, CVE-2025-71105,\nCVE-2025-71107, CVE-2025-71108, CVE-2025-71109, CVE-2025-71111,\nCVE-2025-71112, CVE-2025-71113, CVE-2025-71114, CVE-2025-71116,\nCVE-2025-71118, CVE-2025-71119, CVE-2025-71120, CVE-2025-71121,\nCVE-2025-71122, CVE-2025-71123, CVE-2025-71125, CVE-2025-71126,\nCVE-2025-71127, CVE-2025-71130, CVE-2025-71131, CVE-2025-71132,\nCVE-2025-71133, CVE-2025-71135, CVE-2025-71136, CVE-2025-71137,\nCVE-2025-71138, CVE-2025-71140, CVE-2025-71141, CVE-2025-71143,\nCVE-2025-71144, CVE-2025-71147, CVE-2025-71148, CVE-2025-71150,\nCVE-2025-71151, CVE-2025-71153, CVE-2025-71154, CVE-2025-71160,\nCVE-2025-71162, CVE-2025-71163, CVE-2025-71180, CVE-2025-71182,\nCVE-2025-71183, CVE-2025-71184, CVE-2025-71185, CVE-2025-71186,\nCVE-2025-71188, CVE-2025-71189, CVE-2025-71190, CVE-2025-71191,\nCVE-2025-71192, CVE-2025-71193, CVE-2025-71194, CVE-2025-71195,\nCVE-2025-71196, CVE-2025-71197, CVE-2025-71198, CVE-2025-71199,\nCVE-2025-71200, CVE-2025-71220, CVE-2025-71222, CVE-2025-71224,\nCVE-2025-71225, CVE-2025-71268, CVE-2026-22976, CVE-2026-22977,\nCVE-2026-22978, CVE-2026-22979, CVE-2026-22980, CVE-2026-22982,\nCVE-2026-22984, CVE-2026-22990, CVE-2026-22991, CVE-2026-22992,\nCVE-2026-22994, CVE-2026-22996, CVE-2026-22997, CVE-2026-22998,\nCVE-2026-22999, CVE-2026-23000, CVE-2026-23001, CVE-2026-23003,\nCVE-2026-23005, CVE-2026-23006, CVE-2026-23010, CVE-2026-23011,\nCVE-2026-23019, CVE-2026-23020, CVE-2026-23021, CVE-2026-23025,\nCVE-2026-23026, CVE-2026-23030, CVE-2026-23031, CVE-2026-23032,\nCVE-2026-23033, CVE-2026-23035, CVE-2026-23037, CVE-2026-23038,\nCVE-2026-23047, CVE-2026-23049, CVE-2026-23050, CVE-2026-23053,\nCVE-2026-23054, CVE-2026-23056, CVE-2026-23057, CVE-2026-23058,\nCVE-2026-23059, CVE-2026-23061, CVE-2026-23062, CVE-2026-23063,\nCVE-2026-23064, CVE-2026-23065, CVE-2026-23068, CVE-2026-23069,\nCVE-2026-23071, CVE-2026-23073, CVE-2026-23075, CVE-2026-23076,\nCVE-2026-23078, CVE-2026-23080, CVE-2026-23083, CVE-2026-23084,\nCVE-2026-23085, CVE-2026-23086, CVE-2026-23087, CVE-2026-23088,\nCVE-2026-23089, CVE-2026-23090, CVE-2026-23091, CVE-2026-23093,\nCVE-2026-23094, CVE-2026-23095, CVE-2026-23096, CVE-2026-23097,\nCVE-2026-23098, CVE-2026-23099, CVE-2026-23101, CVE-2026-23102,\nCVE-2026-23103, CVE-2026-23105, CVE-2026-23107, CVE-2026-23108,\nCVE-2026-23110, CVE-2026-23112, CVE-2026-23113, CVE-2026-23116,\nCVE-2026-23119, CVE-2026-23120, CVE-2026-23121, CVE-2026-23123,\nCVE-2026-23124, CVE-2026-23125, CVE-2026-23126, CVE-2026-23128,\nCVE-2026-23129, CVE-2026-23131, CVE-2026-23133, CVE-2026-23135,\nCVE-2026-23136, CVE-2026-23139, CVE-2026-23140, CVE-2026-23141,\nCVE-2026-23142, CVE-2026-23144, CVE-2026-23145, CVE-2026-23146,\nCVE-2026-23148, CVE-2026-23150, CVE-2026-23151, CVE-2026-23156,\nCVE-2026-23159, CVE-2026-23160, CVE-2026-23163, CVE-2026-23164,\nCVE-2026-23166, CVE-2026-23167, CVE-2026-23168, CVE-2026-23170,\nCVE-2026-23172, CVE-2026-23173, CVE-2026-23176, CVE-2026-23178,\nCVE-2026-23179, CVE-2026-23180, CVE-2026-23182, CVE-2026-23187,\nCVE-2026-23190, CVE-2026-23191, CVE-2026-23193, CVE-2026-23198,\nCVE-2026-23204, CVE-2026-23205, CVE-2026-23206, CVE-2026-23209,\nCVE-2026-23212, CVE-2026-23213, CVE-2026-23214, CVE-2026-23215,\nCVE-2026-23216, CVE-2026-23231, CVE-2026-23254, CVE-2026-23256,\nCVE-2026-23257, CVE-2026-23258, CVE-2026-23260, CVE-2026-23261,\nCVE-2026-23262, CVE-2026-23264, CVE-2026-23274, CVE-2026-23351,\nCVE-2026-23394, CVE-2026-31419, CVE-2026-31504, CVE-2026-31533,\nCVE-2026-31676, CVE-2026-43033, CVE-2026-43077, CVE-2026-43078,\nCVE-2026-43362, CVE-2026-43494, CVE-2026-46028, CVE-2026-46323)\n","status":"published","published":"2026-06-16T22:30:05Z","modified":"2026-11-07T01:45:16.546246471Z","updated_at":"2026-11-07T01:57:06.567161Z"},{"id":"USN-8499-1","title":"linux-xilinx vulnerabilities","description":"It was discovered that the Linux kernel algif_aead module did not properly\nhandle in-place cryptographic operations. This flaw is known as Copy Fail.\nA local attacker could use this to escalate privileges, or possibly escape\na container. (CVE-2026-31431)\n\nIt was discovered that the Linux kernel did not properly handle shared page\nfragments during socket buffer operations, collectively known as Dirty\nFrag. A logic flaw existed in the XFRM ESP-in-TCP subsystem and in the\nRxRPC networking subsystem when processing paged fragments. A local\nattacker could use this to escalate privileges, or possibly escape a\ncontainer. (CVE-2026-43284, CVE-2026-43500, CVE-2026-45998, CVE-2026-46000)\n\nIt was discovered that a logic flaw existed in the XFRM ESP-in-TCP\nsubsystem in the Linux kernel when handling socket buffer fragments. This\nflaw is known as Fragnesia. A local attacker could use this to escalate\nprivileges, or possibly escape a container. (CVE-2026-43503,\nCVE-2026-46300)\n\nQualys discovered that a race condition existed in the ptrace subsystem of\nthe Linux kernel when privileged processes are exiting. An unprivileged\nlocal attacker could use this issue to expose sensitive information.\n(CVE-2026-46333)\n\nTristan Madani discovered that Ubuntu Linux kernel 6.8, 6.17 and 7.0\ncontain a memory leak when handling AppArmor notifications. A local\nattacker could use this to cause resource exhaustion. (CVE-2026-47326)\n\nTristan Madani discovered that Ubuntu Linux kernel 6.8, 6.17 and 7.0\ncontain a NULL pointer dereference when handling AppArmor notifications. A\nlocal attacker could use this to cause a kernel oops. (CVE-2026-47327)\n\nTristan Madani discovered that Ubuntu Linux kernel 6.8, 6.17 and 7.0\ncontained an invalid free when handling AppArmor notifications. A local\nattacker could use this to corrupt kernel memory. (CVE-2026-47328)\n\nTristan Madani discovered that Ubuntu Linux kernel 6.8, 6.17 and 7.0\ncontained insufficient validation of AppArmor notification responses. A\nlocal attacker could use this to allow crafted responses to be processed.\n(CVE-2026-47329)\n\nTristan Madani discovered that Ubuntu Linux kernel 6.8, 6.17 and 7.0 used\nan uninitialized variable when handling AppArmor notifications. A local\nattacker could use this to cause incorrect caching of data.\n(CVE-2026-47330)\n\nTristan Madani discovered that Ubuntu Linux kernel 6.8 contained a use-\nafter-free (UAF) bug. A local attacker could use this to cause memory\ncorruption and, theoretically, arbitrary code execution. (CVE-2026-47331)\n\nTristan Madani discovered that Ubuntu Linux kernel 6.8, 6.17 and 7.0\ncontained an out-of-bounds (OOB) read when handling AppArmor notifications.\nA local attacker could use this to cause information disclosure of kernel\nmemory. (CVE-2026-47332)\n\nTristan Madani discovered that Ubuntu Linux kernel 6.8, 6.17 and 7.0\ncontained a out-of-bounds (OOB) read when handling AppArmor notifications.\nA local attacker could use this to cause kernel memory corruption and,\ntheoretically, influence processing of AppArmor policies. (CVE-2026-47333)\n\nTristan Madani discovered that Ubuntu Linux kernel 6.8, 6.17 and 7.0\ncontained incorrect holding of locks when handling AppArmor notifications.\nA local attacker could use this to cause a kernel panic or deadlock.\n(CVE-2026-47334)\n\nTristan Madani discovered that Ubuntu Linux kernel 6.8 contained a NULL\npointer dereference when handling AppArmor notifications. A local attacker\ncould use this to cause a kernel panic. (CVE-2026-47335)\n\nTristan Madani discovered that Ubuntu Linux kernel 6.8 used an\nuninitialized variable when handling AppArmor AF_INET/AF_INET6 socket\nmediation. A local attacker could use this to influence processing of fine-\ngrained network socket mediation. (CVE-2026-47336)\n\nTristan Madani and Trevor Lawrence have each independently discovered that\nUbuntu Linux kernel 6.8, 6.17 and 7.0 contained a NULL pointer dereference\nwhen handling AppArmor network socket mediation. A local attacker could use\nthis to cause a kernel oops. (CVE-2026-47337)\n\nSeveral security issues were discovered in the Linux kernel.\nAn attacker could possibly use these to compromise the system.\nThis update corrects flaws in the following subsystems:\n  - Foo-over-UDP (FOU);\n  - ARM64 architecture;\n  - MIPS architecture;\n  - PowerPC architecture;\n  - x86 architecture;\n  - Block layer subsystem;\n  - Cryptographic API;\n  - Intel NPU Driver;\n  - ACPI drivers;\n  - ATM drivers;\n  - Drivers core;\n  - Null block device driver;\n  - RNBD block device driver;\n  - Ublk userspace block driver;\n  - Bluetooth drivers;\n  - Bus devices;\n  - Character device driver;\n  - TPM device driver;\n  - Clock framework and drivers;\n  - Clocksource drivers;\n  - Counter interface drivers;\n  - CPU idle management framework;\n  - Hardware crypto device drivers;\n  - DMA engine subsystem;\n  - DPLL subsystem;\n  - EFI core;\n  - GPIO subsystem;\n  - GPU drivers;\n  - HID subsystem;\n  - Hardware monitoring drivers;\n  - Intel Trace Hub HW tracing drivers;\n  - IIO subsystem;\n  - IIO ADC drivers;\n  - InfiniBand drivers;\n  - On-Chip Interconnect management framework;\n  - IOMMU subsystem;\n  - IRQ chip drivers;\n  - Modular ISDN driver;\n  - LED subsystem;\n  - Multiple devices driver;\n  - Media drivers;\n  - Multifunction device drivers;\n  - Broadcom VK accelerator driver;\n  - UACCE accelerator framework;\n  - MMC subsystem;\n  - MOST (Media Oriented Systems Transport) drivers;\n  - MTD block device drivers;\n  - Ethernet bonding driver;\n  - Network drivers;\n  - Mellanox network drivers;\n  - STMicroelectronics network drivers;\n  - NTB driver;\n  - NVME drivers;\n  - PCI subsystem;\n  - Performance monitor drivers;\n  - PHY drivers;\n  - Pin controllers subsystem;\n  - x86 platform drivers;\n  - i.MX PM domains;\n  - Power supply drivers;\n  - RapidIO drivers;\n  - RAS (Reliability, Availability, Serviceability) subsystem;\n  - Remote Processor subsystem;\n  - RPMSG subsystem;\n  - S/390 drivers;\n  - SCSI subsystem;\n  - SLIMbus drivers;\n  - MediaTek SoC drivers;\n  - Texas Instruments SoC drivers;\n  - SPI subsystem;\n  - Greybus lights staging drivers;\n  - Realtek RTL8723BS SDIO drivers;\n  - TCM subsystem;\n  - UFS subsystem;\n  - ChipIdea USB driver;\n  - DesignWare USB3 driver;\n  - USB over IP driver;\n  - vDPA drivers;\n  - Virtio Host (VHOST) subsystem;\n  - Framebuffer layer;\n  - W1 Dallas's 1-wire bus driver;\n  - Xen hypervisor drivers;\n  - BTRFS file system;\n  - File systems infrastructure;\n  - Ceph distributed file system;\n  - EFI Variable file system;\n  - exFAT file system;\n  - Ext4 file system;\n  - F2FS file system;\n  - FAT file system;\n  - GFS2 file system;\n  - HFS+ file system;\n  - JFS file system;\n  - Network file system (NFS) client;\n  - Network file system (NFS) server daemon;\n  - NILFS2 file system;\n  - NTFS3 file system;\n  - OCFS2 file system;\n  - Proc file system;\n  - Pstore file system;\n  - Diskquota system;\n  - SMB network file system;\n  - XFS file system;\n  - Audit subsystem;\n  - Memory Management;\n  - Scheduler infrastructure;\n  - IPv6 networking;\n  - Netfilter;\n  - NFC subsystem;\n  - Tracing infrastructure;\n  - io_uring subsystem;\n  - BPF subsystem;\n  - Perf events;\n  - Kernel kexec() syscall;\n  - RCU subsystem;\n  - Floating proportions library;\n  - Scatterlist API;\n  - Memory management;\n  - 9P file system network protocol;\n  - Asynchronous Transfer Mode (ATM) subsystem;\n  - B.A.T.M.A.N. meshing protocol;\n  - Bluetooth subsystem;\n  - Ethernet bridge;\n  - CAN network layer;\n  - Ceph Core library;\n  - Networking core;\n  - IPv4 networking;\n  - KCM (Kernel Connection Multiplexor) sockets driver;\n  - L2TP protocol;\n  - MAC80211 subsystem;\n  - Multipath TCP;\n  - NET/ROM layer;\n  - Packet sockets;\n  - RDS protocol;\n  - RxRPC session sockets;\n  - Network traffic control;\n  - SCTP protocol;\n  - SMC sockets;\n  - Sun RPC protocol;\n  - TLS protocol;\n  - Unix domain sockets;\n  - VMware vSockets driver;\n  - Wireless networking;\n  - X.25 network layer;\n  - XFRM subsystem;\n  - AppArmor security module;\n  - Simplified Mandatory Access Control Kernel framework;\n  - ALSA AC97 driver;\n  - Generic PCM loopback sound driver;\n  - Creative Sound Blaster X-Fi driver;\n  - AMD SoC Alsa drivers;\n  - Texas InstrumentS Audio (ASoC/HDA) drivers;\n  - SOF drivers;\n  - USB sound devices;\n  - KVM subsystem;\n(CVE-2024-50004, CVE-2024-58096, CVE-2024-58097, CVE-2025-37926,\nCVE-2025-38201, CVE-2025-38591, CVE-2025-40005, CVE-2025-40039,\nCVE-2025-40082, CVE-2025-40149, CVE-2025-68351, CVE-2025-68358,\nCVE-2025-68365, CVE-2025-68725, CVE-2025-68749, CVE-2025-68803,\nCVE-2025-68823, CVE-2025-71160, CVE-2025-71162, CVE-2025-71163,\nCVE-2025-71180, CVE-2025-71182, CVE-2025-71183, CVE-2025-71184,\nCVE-2025-71185, CVE-2025-71186, CVE-2025-71188, CVE-2025-71189,\nCVE-2025-71190, CVE-2025-71191, CVE-2025-71192, CVE-2025-71193,\nCVE-2025-71194, CVE-2025-71195, CVE-2025-71196, CVE-2025-71197,\nCVE-2025-71198, CVE-2025-71199, CVE-2025-71200, CVE-2025-71220,\nCVE-2025-71222, CVE-2025-71224, CVE-2025-71225, CVE-2025-71229,\nCVE-2025-71231, CVE-2025-71232, CVE-2025-71233, CVE-2025-71235,\nCVE-2025-71236, CVE-2025-71237, CVE-2025-71238, CVE-2025-71239,\nCVE-2025-71265, CVE-2025-71266, CVE-2025-71267, CVE-2025-71268,\nCVE-2025-71272, CVE-2025-71273, CVE-2025-71274, CVE-2025-71286,\nCVE-2025-71291, CVE-2025-71292, CVE-2025-71294, CVE-2025-71295,\nCVE-2025-71297, CVE-2025-71304, CVE-2025-71305, CVE-2026-22976,\nCVE-2026-22977, CVE-2026-22978, CVE-2026-22979, CVE-2026-22980,\nCVE-2026-22982, CVE-2026-22984, CVE-2026-22990, CVE-2026-22991,\nCVE-2026-22992, CVE-2026-22994, CVE-2026-22996, CVE-2026-22997,\nCVE-2026-22998, CVE-2026-22999, CVE-2026-23000, CVE-2026-23001,\nCVE-2026-23003, CVE-2026-23005, CVE-2026-23006, CVE-2026-23010,\nCVE-2026-23011, CVE-2026-23019, CVE-2026-23020, CVE-2026-23021,\nCVE-2026-23025, CVE-2026-23026, CVE-2026-23030, CVE-2026-23031,\nCVE-2026-23032, CVE-2026-23033, CVE-2026-23035, CVE-2026-23037,\nCVE-2026-23038, CVE-2026-23047, CVE-2026-23049, CVE-2026-23050,\nCVE-2026-23053, CVE-2026-23054, CVE-2026-23056, CVE-2026-23057,\nCVE-2026-23058, CVE-2026-23059, CVE-2026-23061, CVE-2026-23062,\nCVE-2026-23063, CVE-2026-23064, CVE-2026-23065, CVE-2026-23068,\nCVE-2026-23069, CVE-2026-23071, CVE-2026-23073, CVE-2026-23075,\nCVE-2026-23076, CVE-2026-23078, CVE-2026-23080, CVE-2026-23083,\nCVE-2026-23084, CVE-2026-23085, CVE-2026-23086, CVE-2026-23087,\nCVE-2026-23088, CVE-2026-23089, CVE-2026-23090, CVE-2026-23091,\nCVE-2026-23093, CVE-2026-23094, CVE-2026-23095, CVE-2026-23096,\nCVE-2026-23097, CVE-2026-23098, CVE-2026-23099, CVE-2026-23100,\nCVE-2026-23101, CVE-2026-23102, CVE-2026-23103, CVE-2026-23105,\nCVE-2026-23107, CVE-2026-23108, CVE-2026-23110, CVE-2026-23113,\nCVE-2026-23116, CVE-2026-23119, CVE-2026-23120, CVE-2026-23121,\nCVE-2026-23123, CVE-2026-23124, CVE-2026-23125, CVE-2026-23126,\nCVE-2026-23128, CVE-2026-23129, CVE-2026-23131, CVE-2026-23133,\nCVE-2026-23135, CVE-2026-23136, CVE-2026-23139, CVE-2026-23140,\nCVE-2026-23141, CVE-2026-23142, CVE-2026-23144, CVE-2026-23145,\nCVE-2026-23146, CVE-2026-23148, CVE-2026-23150, CVE-2026-23151,\nCVE-2026-23156, CVE-2026-23159, CVE-2026-23160, CVE-2026-23163,\nCVE-2026-23164, CVE-2026-23166, CVE-2026-23167, CVE-2026-23168,\nCVE-2026-23169, CVE-2026-23170, CVE-2026-23172, CVE-2026-23173,\nCVE-2026-23176, CVE-2026-23178, CVE-2026-23179, CVE-2026-23180,\nCVE-2026-23182, CVE-2026-23187, CVE-2026-23190, CVE-2026-23191,\nCVE-2026-23193, CVE-2026-23198, CVE-2026-23200, CVE-2026-23202,\nCVE-2026-23204, CVE-2026-23205, CVE-2026-23206, CVE-2026-23212,\nCVE-2026-23213, CVE-2026-23214, CVE-2026-23215, CVE-2026-23216,\nCVE-2026-23220, CVE-2026-23221, CVE-2026-23222, CVE-2026-23228,\nCVE-2026-23229, CVE-2026-23230, CVE-2026-23233, CVE-2026-23234,\nCVE-2026-23235, CVE-2026-23236, CVE-2026-23237, CVE-2026-23238,\nCVE-2026-23241, CVE-2026-23242, CVE-2026-23243, CVE-2026-23249,\nCVE-2026-23254, CVE-2026-23256, CVE-2026-23257, CVE-2026-23258,\nCVE-2026-23260, CVE-2026-23261, CVE-2026-23262, CVE-2026-23264,\nCVE-2026-23266, CVE-2026-23267, CVE-2026-23272, CVE-2026-23274,\nCVE-2026-23278, CVE-2026-23351, CVE-2026-23392, CVE-2026-23394,\nCVE-2026-23428, CVE-2026-23450, CVE-2026-23455, CVE-2026-31402,\nCVE-2026-31411, CVE-2026-31418, CVE-2026-31419, CVE-2026-31436,\nCVE-2026-31448, CVE-2026-31478, CVE-2026-31504, CVE-2026-31533,\nCVE-2026-31607, CVE-2026-31637, CVE-2026-31649, CVE-2026-31657,\nCVE-2026-31659, CVE-2026-31668, CVE-2026-31669, CVE-2026-31676,\nCVE-2026-31682, CVE-2026-31685, CVE-2026-31687, CVE-2026-31693,\nCVE-2026-43011, CVE-2026-43033, CVE-2026-43037, CVE-2026-43038,\nCVE-2026-43071, CVE-2026-43077, CVE-2026-43078, CVE-2026-43114,\nCVE-2026-43117, CVE-2026-43123, CVE-2026-43124, CVE-2026-43128,\nCVE-2026-43130, CVE-2026-43132, CVE-2026-43133, CVE-2026-43134,\nCVE-2026-43135, CVE-2026-43136, CVE-2026-43137, CVE-2026-43139,\nCVE-2026-43140, CVE-2026-43141, CVE-2026-43143, CVE-2026-43145,\nCVE-2026-43147, CVE-2026-43148, CVE-2026-43149, CVE-2026-43150,\nCVE-2026-43152, CVE-2026-43153, CVE-2026-43156, CVE-2026-43157,\nCVE-2026-43158, CVE-2026-43159, CVE-2026-43163, CVE-2026-43167,\nCVE-2026-43168, CVE-2026-43169, CVE-2026-43170, CVE-2026-43171,\nCVE-2026-43173, CVE-2026-43175, CVE-2026-43180, CVE-2026-43182,\nCVE-2026-43183, CVE-2026-43184, CVE-2026-43186, CVE-2026-43187,\nCVE-2026-43189, CVE-2026-43190, CVE-2026-43194, CVE-2026-43196,\nCVE-2026-43199, CVE-2026-43200, CVE-2026-43201, CVE-2026-43202,\nCVE-2026-43203, CVE-2026-43205, CVE-2026-43206, CVE-2026-43207,\nCVE-2026-43209, CVE-2026-43211, CVE-2026-43212, CVE-2026-43214,\nCVE-2026-43215, CVE-2026-43218, CVE-2026-43221, CVE-2026-43222,\nCVE-2026-43223, CVE-2026-43225, CVE-2026-43226, CVE-2026-43227,\nCVE-2026-43230, CVE-2026-43231, CVE-2026-43232, CVE-2026-43233,\nCVE-2026-43236, CVE-2026-43238, CVE-2026-43239, CVE-2026-43241,\nCVE-2026-43242, CVE-2026-43244, CVE-2026-43246, CVE-2026-43248,\nCVE-2026-43249, CVE-2026-43250, CVE-2026-43251, CVE-2026-43253,\nCVE-2026-43255, CVE-2026-43256, CVE-2026-43257, CVE-2026-43258,\nCVE-2026-43261, CVE-2026-43262, CVE-2026-43264, CVE-2026-43266,\nCVE-2026-43268, CVE-2026-43269, CVE-2026-43270, CVE-2026-43271,\nCVE-2026-43273, CVE-2026-43275, CVE-2026-43277, CVE-2026-43278,\nCVE-2026-43279, CVE-2026-43283, CVE-2026-43287, CVE-2026-43288,\nCVE-2026-43289, CVE-2026-43291, CVE-2026-43295, CVE-2026-43296,\nCVE-2026-43297, CVE-2026-43300, CVE-2026-43302, CVE-2026-43304,\nCVE-2026-43312, CVE-2026-43313, CVE-2026-43314, CVE-2026-43315,\nCVE-2026-43316, CVE-2026-43317, CVE-2026-43318, CVE-2026-43319,\nCVE-2026-43320, CVE-2026-43341, CVE-2026-43378, CVE-2026-43383,\nCVE-2026-43384, CVE-2026-43406, CVE-2026-43407, CVE-2026-43414,\nCVE-2026-43493, CVE-2026-43494, CVE-2026-43501, CVE-2026-45847,\nCVE-2026-45848, CVE-2026-45849, CVE-2026-45851, CVE-2026-45852,\nCVE-2026-45856, CVE-2026-45857, CVE-2026-45859, CVE-2026-45860,\nCVE-2026-45861, CVE-2026-45862, CVE-2026-45864, CVE-2026-45865,\nCVE-2026-45866, CVE-2026-45867, CVE-2026-45868, CVE-2026-45869,\nCVE-2026-45870, CVE-2026-45871, CVE-2026-45872, CVE-2026-45873,\nCVE-2026-45875, CVE-2026-45877, CVE-2026-45878, CVE-2026-45879,\nCVE-2026-45880, CVE-2026-45881, CVE-2026-45882, CVE-2026-45883,\nCVE-2026-45884, CVE-2026-45885, CVE-2026-45886, CVE-2026-45890,\nCVE-2026-45891, CVE-2026-45893, CVE-2026-45895, CVE-2026-45902,\nCVE-2026-45904, CVE-2026-45905, CVE-2026-45910, CVE-2026-45912,\nCVE-2026-45913, CVE-2026-45914, CVE-2026-45915, CVE-2026-45916,\nCVE-2026-45917, CVE-2026-45919, CVE-2026-45921, CVE-2026-45923,\nCVE-2026-45928, CVE-2026-45935, CVE-2026-45936, CVE-2026-45938,\nCVE-2026-45941, CVE-2026-45946, CVE-2026-45947, CVE-2026-45948,\nCVE-2026-45954, CVE-2026-45957, CVE-2026-45960, CVE-2026-45962,\nCVE-2026-45964, CVE-2026-45965, CVE-2026-45968, CVE-2026-45969,\nCVE-2026-45970, CVE-2026-45973, CVE-2026-45974, CVE-2026-45976,\nCVE-2026-45978, CVE-2026-45981, CVE-2026-45982, CVE-2026-45983,\nCVE-2026-45984, CVE-2026-45988, CVE-2026-46028, CVE-2026-46043,\nCVE-2026-46115, CVE-2026-46119, CVE-2026-46135, CVE-2026-46185,\nCVE-2026-46195, CVE-2026-46243, CVE-2026-46244, CVE-2026-46246,\nCVE-2026-46247, CVE-2026-46249, CVE-2026-46250, CVE-2026-46251,\nCVE-2026-46253, CVE-2026-46254, CVE-2026-46255, CVE-2026-46259,\nCVE-2026-46261, CVE-2026-46265, CVE-2026-46266, CVE-2026-46267,\nCVE-2026-46270, CVE-2026-46289, CVE-2026-46323, CVE-2026-46328)\n","status":"published","published":"2026-07-02T15:56:51Z","modified":"2026-11-07T01:45:08.338519599Z","updated_at":"2026-11-07T01:57:16.198641Z"},{"id":"USN-8508-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  - ARM64 architecture;\n  - S390 architecture;\n  - Block layer subsystem;\n  - Cryptographic API;\n  - DMA engine subsystem;\n  - GPU drivers;\n  - InfiniBand drivers;\n  - Ethernet bonding driver;\n  - STMicroelectronics network drivers;\n  - Network drivers;\n  - NVME drivers;\n  - SCSI subsystem;\n  - USB over IP driver;\n  - File systems infrastructure;\n  - Ext4 file system;\n  - Network file system (NFS) server daemon;\n  - SMB network file system;\n  - Kernel thread helper (kthread);\n  - Distributed Switch Architecture;\n  - IPv6 networking;\n  - Netfilter;\n  - Tracing infrastructure;\n  - Control group (cgroup);\n  - Kernel exit() syscall;\n  - Scatterlist API;\n  - Memory management;\n  - B.A.T.M.A.N. meshing protocol;\n  - Ethernet bridge;\n  - Ceph Core library;\n  - IPv4 networking;\n  - MAC80211 subsystem;\n  - Multipath TCP;\n  - Packet sockets;\n  - RxRPC session sockets;\n  - SMC sockets;\n  - TLS protocol;\n  - Unix domain sockets;\n  - X.25 network layer;\n  - AppArmor security module;\n(CVE-2025-71088, CVE-2025-71090, CVE-2025-71127, CVE-2025-71134,\nCVE-2025-71141, CVE-2025-71142, CVE-2025-71144, CVE-2025-71152,\nCVE-2025-71155, CVE-2026-22984, CVE-2026-23112, CVE-2026-23231,\nCVE-2026-23272, CVE-2026-23273, CVE-2026-23274, CVE-2026-23278,\nCVE-2026-23351, CVE-2026-23392, CVE-2026-23394, CVE-2026-23427,\nCVE-2026-23428, CVE-2026-23450, CVE-2026-23455, CVE-2026-31402,\nCVE-2026-31418, CVE-2026-31419, CVE-2026-31436, CVE-2026-31448,\nCVE-2026-31478, CVE-2026-31504, CVE-2026-31533, 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-43033,\nCVE-2026-43037, CVE-2026-43038, CVE-2026-43071, CVE-2026-43077,\nCVE-2026-43078, CVE-2026-43083, CVE-2026-43114, CVE-2026-43117,\nCVE-2026-43125, CVE-2026-43186, CVE-2026-43197, CVE-2026-43304,\nCVE-2026-43341, CVE-2026-43376, CVE-2026-43378, CVE-2026-43383,\nCVE-2026-43384, CVE-2026-43402, CVE-2026-43406, CVE-2026-43407,\nCVE-2026-43414, CVE-2026-43493, CVE-2026-43501, CVE-2026-45898,\nCVE-2026-45966, CVE-2026-45988, CVE-2026-46028, CVE-2026-46039,\nCVE-2026-46043, CVE-2026-46115, CVE-2026-46119, CVE-2026-46135,\nCVE-2026-46185, CVE-2026-46195, CVE-2026-46243, CVE-2026-46244,\nCVE-2026-46266, CVE-2026-46289, CVE-2026-46316, CVE-2026-46325)\n","status":"published","published":"2026-07-06T08:48:58Z","modified":"2026-11-07T01:45:14.04907998Z","updated_at":"2026-11-07T01:57:06.567161Z"}]}}