{"id":"CVE-2022-50151","aliases":["CLSA-2026-1789958474","DEBIAN-CVE-2022-50151","EUVD-2022-55416","GHSA-gvgm-6pph-fj6g","OESA-2026-1341","RHSA-2023:2458","ROOT-OS-DEBIAN-11-CVE-2022-50151","SUSE-SU-2025:02264-1","SUSE-SU-2025:02321-1","SUSE-SU-2025:02322-1","SUSE-SU-2025:02537-1","SUSE-SU-2025:2264-1","UBUNTU-CVE-2022-50151"],"status":"published","title":"usb: cdns3: fix random warning message when driver load","description":"In the Linux kernel, the following vulnerability has been resolved:\n\nusb: cdns3: fix random warning message when driver load\n\nWarning log:\n[    4.141392] Unexpected gfp: 0x4 (GFP_DMA32). Fixing up to gfp: 0xa20 (GFP_ATOMIC). Fix your code!\n[    4.150340] CPU: 1 PID: 175 Comm: 1-0050 Not tainted 5.15.5-00039-g2fd9ae1b568c #20\n[    4.158010] Hardware name: Freescale i.MX8QXP MEK (DT)\n[    4.163155] Call trace:\n[    4.165600]  dump_backtrace+0x0/0x1b0\n[    4.169286]  show_stack+0x18/0x68\n[    4.172611]  dump_stack_lvl+0x68/0x84\n[    4.176286]  dump_stack+0x18/0x34\n[    4.179613]  kmalloc_fix_flags+0x60/0x88\n[    4.183550]  new_slab+0x334/0x370\n[    4.186878]  ___slab_alloc.part.108+0x4d4/0x748\n[    4.191419]  __slab_alloc.isra.109+0x30/0x78\n[    4.195702]  kmem_cache_alloc+0x40c/0x420\n[    4.199725]  dma_pool_alloc+0xac/0x1f8\n[    4.203486]  cdns3_allocate_trb_pool+0xb4/0xd0\n\npool_alloc_page(struct dma_pool *pool, gfp_t mem_flags)\n{\n\t...\n\tpage = kmalloc(sizeof(*page), mem_flags);\n\tpage-\u003evaddr = dma_alloc_coherent(pool-\u003edev, pool-\u003eallocation,\n\t\t\t\t\t \u0026page-\u003edma, mem_flags);\n\t...\n}\n\nkmalloc was called with mem_flags, which is passed down in\ncdns3_allocate_trb_pool() and have GFP_DMA32 flags.\nkmall_fix_flags() report warning.\n\nGFP_DMA32 is not useful at all. dma_alloc_coherent() will handle\nDMA memory region correctly by pool-\u003edev. GFP_DMA32 can be removed\nsafely.","severity":{"version":"3.1","score":7.8,"vector":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H","level":"high","assessor":"primary","from":"nvd"},"epss":{"day":"2026-11-11","score":0.00201,"percentile":0.10171,"model":"v2026.06.15"},"facts":{"in_kev":false,"known_exploited":false,"public_exploit":false,"fix_available":true},"published":"2024-09-16T09:02:33Z","modified":"2026-11-03T08:03:38Z","fixes":[{"ecosystem":"Linux","package":"Kernel","fixed_in":["5.15.63","5.19.2"],"sources":["osv"]},{"ecosystem":"Debian:12","package":"linux","fixed_in":["5.19.6-1"],"sources":["osv"]},{"ecosystem":"Debian:13","package":"linux","fixed_in":["5.19.6-1"],"sources":["osv"]},{"ecosystem":"Debian:14","package":"linux","fixed_in":["5.19.6-1"],"sources":["osv"]},{"ecosystem":"Root:Debian:11","package":"linux","fixed_in":["5.10.262-1.aikido.113","5.10.262-1.aikido.114"],"sources":["osv"]},{"ecosystem":"Root:Debian:11","package":"rootio-linux","fixed_in":["5.10.262-1.aikido.113","5.10.262-1.aikido.114"],"sources":["osv"]}],"affected":[{"source":"osv","ecosystem":"TuxCare:Ubuntu:20.04","package":"linux-buildinfo-5.4.0-238-generic","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.4.0-238.258+tuxcare.els1"}]}],"bundled":165},{"source":"osv","ecosystem":"TuxCare:Ubuntu:20.04","package":"linux-buildinfo-5.4.0-238-lowlatency","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.4.0-238.258+tuxcare.els1"}]}],"bundled":165},{"source":"osv","ecosystem":"TuxCare:Ubuntu:20.04","package":"linux-cloud-tools-5.4.0-238","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.4.0-238.258+tuxcare.els1"}]}],"bundled":165},{"source":"osv","ecosystem":"TuxCare:Ubuntu:20.04","package":"linux-cloud-tools-5.4.0-238-generic","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.4.0-238.258+tuxcare.els1"}]}],"bundled":165},{"source":"osv","ecosystem":"TuxCare:Ubuntu:20.04","package":"linux-cloud-tools-5.4.0-238-lowlatency","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.4.0-238.258+tuxcare.els1"}]}],"bundled":165},{"source":"osv","ecosystem":"TuxCare:Ubuntu:20.04","package":"linux-cloud-tools-common","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.4.0-238.258+tuxcare.els1"}]}],"bundled":165},{"source":"osv","ecosystem":"TuxCare:Ubuntu:20.04","package":"linux-doc","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.4.0-238.258+tuxcare.els1"}]}],"bundled":165},{"source":"osv","ecosystem":"TuxCare:Ubuntu:20.04","package":"linux-headers-5.4.0-238","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.4.0-238.258+tuxcare.els1"}]}],"bundled":165},{"source":"osv","ecosystem":"TuxCare:Ubuntu:20.04","package":"linux-headers-5.4.0-238-generic","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.4.0-238.258+tuxcare.els1"}]}],"bundled":165},{"source":"osv","ecosystem":"TuxCare:Ubuntu:20.04","package":"linux-headers-5.4.0-238-lowlatency","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.4.0-238.258+tuxcare.els1"}]}],"bundled":165},{"source":"osv","ecosystem":"TuxCare:Ubuntu:20.04","package":"linux-image-unsigned-5.4.0-238-generic","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.4.0-238.258+tuxcare.els1"}]}],"bundled":165},{"source":"osv","ecosystem":"TuxCare:Ubuntu:20.04","package":"linux-image-unsigned-5.4.0-238-lowlatency","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.4.0-238.258+tuxcare.els1"}]}],"bundled":165},{"source":"osv","ecosystem":"TuxCare:Ubuntu:20.04","package":"linux-libc-dev","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.4.0-238.258+tuxcare.els1"}]}],"bundled":165},{"source":"osv","ecosystem":"TuxCare:Ubuntu:20.04","package":"linux-modules-5.4.0-238-generic","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.4.0-238.258+tuxcare.els1"}]}],"bundled":165},{"source":"osv","ecosystem":"TuxCare:Ubuntu:20.04","package":"linux-modules-5.4.0-238-lowlatency","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.4.0-238.258+tuxcare.els1"}]}],"bundled":165},{"source":"osv","ecosystem":"TuxCare:Ubuntu:20.04","package":"linux-modules-extra-5.4.0-238-generic","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.4.0-238.258+tuxcare.els1"}]}],"bundled":165},{"source":"osv","ecosystem":"TuxCare:Ubuntu:20.04","package":"linux-source-5.4.0","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.4.0-238.258+tuxcare.els1"}]}],"bundled":165},{"source":"osv","ecosystem":"TuxCare:Ubuntu:20.04","package":"linux-tools-5.4.0-238","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.4.0-238.258+tuxcare.els1"}]}],"bundled":165},{"source":"osv","ecosystem":"TuxCare:Ubuntu:20.04","package":"linux-tools-5.4.0-238-generic","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.4.0-238.258+tuxcare.els1"}]}],"bundled":165},{"source":"osv","ecosystem":"TuxCare:Ubuntu:20.04","package":"linux-tools-5.4.0-238-lowlatency","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.4.0-238.258+tuxcare.els1"}]}],"bundled":165},{"source":"osv","ecosystem":"TuxCare:Ubuntu:20.04","package":"linux-tools-common","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.4.0-238.258+tuxcare.els1"}]}],"bundled":165},{"source":"osv","ecosystem":"TuxCare:Ubuntu:20.04","package":"linux-tools-host","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.4.0-238.258+tuxcare.els1"}]}],"bundled":165},{"source":"osv","ecosystem":"Linux","package":"Kernel","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"5.13.0"},{"fixed":"5.15.63"}]},{"type":"ECOSYSTEM","events":[{"introduced":"5.16.0"},{"fixed":"5.19.2"}]}]},{"source":"osv","ecosystem":"Debian:12","package":"linux","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.19.6-1"}]}]},{"source":"osv","ecosystem":"Debian:13","package":"linux","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.19.6-1"}]}]},{"source":"osv","ecosystem":"Debian:14","package":"linux","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.19.6-1"}]}]},{"source":"osv","ecosystem":"openEuler:22.03-LTS-SP4","package":"kernel","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.10.0-301.0.0.204.oe2203sp4"}]}],"bundled":58},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::appstream","package":"bpftool-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:7.0.0-284.11.1.el9_2"}]}],"bundled":409},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::appstream","package":"kernel-64k-debug-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-284.11.1.el9_2"}]}],"bundled":409},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::appstream","package":"kernel-64k-debug-devel","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-284.11.1.el9_2"}]}],"bundled":409},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::appstream","package":"kernel-64k-debug-devel-matched","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-284.11.1.el9_2"}]}],"bundled":409},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::appstream","package":"kernel-64k-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-284.11.1.el9_2"}]}],"bundled":409},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::appstream","package":"kernel-64k-devel","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-284.11.1.el9_2"}]}],"bundled":409},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::appstream","package":"kernel-64k-devel-matched","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-284.11.1.el9_2"}]}],"bundled":409},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::appstream","package":"kernel-debug-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-284.11.1.el9_2"}]}],"bundled":409},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::appstream","package":"kernel-debug-devel","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-284.11.1.el9_2"}]}],"bundled":409},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::appstream","package":"kernel-debug-devel-matched","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-284.11.1.el9_2"}]}],"bundled":409},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::appstream","package":"kernel-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-284.11.1.el9_2"}]}],"bundled":409},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::appstream","package":"kernel-debuginfo-common-aarch64","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-284.11.1.el9_2"}]}],"bundled":409},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::appstream","package":"kernel-debuginfo-common-ppc64le","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-284.11.1.el9_2"}]}],"bundled":409},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::appstream","package":"kernel-debuginfo-common-s390x","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-284.11.1.el9_2"}]}],"bundled":409},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::appstream","package":"kernel-debuginfo-common-x86_64","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-284.11.1.el9_2"}]}],"bundled":409},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::appstream","package":"kernel-devel","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-284.11.1.el9_2"}]}],"bundled":409},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::appstream","package":"kernel-devel-matched","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-284.11.1.el9_2"}]}],"bundled":409},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::appstream","package":"kernel-doc","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-284.11.1.el9_2"}]}],"bundled":409},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::appstream","package":"kernel-tools-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-284.11.1.el9_2"}]}],"bundled":409},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::appstream","package":"kernel-zfcpdump-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-284.11.1.el9_2"}]}],"bundled":409},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::appstream","package":"kernel-zfcpdump-devel","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-284.11.1.el9_2"}]}],"bundled":409},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::appstream","package":"kernel-zfcpdump-devel-matched","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-284.11.1.el9_2"}]}],"bundled":409},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::appstream","package":"perf","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-284.11.1.el9_2"}]}],"bundled":409},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::appstream","package":"perf-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-284.11.1.el9_2"}]}],"bundled":409},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::appstream","package":"python3-perf-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-284.11.1.el9_2"}]}],"bundled":409},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::appstream","package":"rtla","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-284.11.1.el9_2"}]}],"bundled":409},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::baseos","package":"bpftool","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:7.0.0-284.11.1.el9_2"}]}],"bundled":409},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::baseos","package":"bpftool-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:7.0.0-284.11.1.el9_2"}]}],"bundled":409},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::baseos","package":"kernel","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-284.11.1.el9_2"}]}],"bundled":409},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::baseos","package":"kernel-64k","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-284.11.1.el9_2"}]}],"bundled":409},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::baseos","package":"kernel-64k-core","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-284.11.1.el9_2"}]}],"bundled":409},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::baseos","package":"kernel-64k-debug","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-284.11.1.el9_2"}]}],"bundled":409},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::baseos","package":"kernel-64k-debug-core","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-284.11.1.el9_2"}]}],"bundled":409},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::baseos","package":"kernel-64k-debug-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-284.11.1.el9_2"}]}],"bundled":409},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::baseos","package":"kernel-64k-debug-modules","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-284.11.1.el9_2"}]}],"bundled":409},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::baseos","package":"kernel-64k-debug-modules-core","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-284.11.1.el9_2"}]}],"bundled":409},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::baseos","package":"kernel-64k-debug-modules-extra","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-284.11.1.el9_2"}]}],"bundled":409},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::baseos","package":"kernel-64k-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-284.11.1.el9_2"}]}],"bundled":409},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::baseos","package":"kernel-64k-modules","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-284.11.1.el9_2"}]}],"bundled":409},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::baseos","package":"kernel-64k-modules-core","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-284.11.1.el9_2"}]}],"bundled":409},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::baseos","package":"kernel-64k-modules-extra","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-284.11.1.el9_2"}]}],"bundled":409},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::baseos","package":"kernel-abi-stablelists","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-284.11.1.el9_2"}]}],"bundled":409},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::baseos","package":"kernel-core","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-284.11.1.el9_2"}]}],"bundled":409},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::baseos","package":"kernel-debug","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-284.11.1.el9_2"}]}],"bundled":409},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::baseos","package":"kernel-debug-core","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-284.11.1.el9_2"}]}],"bundled":409},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::baseos","package":"kernel-debug-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-284.11.1.el9_2"}]}],"bundled":409},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::baseos","package":"kernel-debug-modules","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-284.11.1.el9_2"}]}],"bundled":409},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::baseos","package":"kernel-debug-modules-core","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-284.11.1.el9_2"}]}],"bundled":409},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::baseos","package":"kernel-debug-modules-extra","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-284.11.1.el9_2"}]}],"bundled":409},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::baseos","package":"kernel-debug-uki-virt","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-284.11.1.el9_2"}]}],"bundled":409},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::baseos","package":"kernel-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-284.11.1.el9_2"}]}],"bundled":409},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::baseos","package":"kernel-debuginfo-common-aarch64","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-284.11.1.el9_2"}]}],"bundled":409},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::baseos","package":"kernel-debuginfo-common-ppc64le","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-284.11.1.el9_2"}]}],"bundled":409},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::baseos","package":"kernel-debuginfo-common-s390x","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-284.11.1.el9_2"}]}],"bundled":409},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::baseos","package":"kernel-debuginfo-common-x86_64","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-284.11.1.el9_2"}]}],"bundled":409},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::baseos","package":"kernel-modules","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-284.11.1.el9_2"}]}],"bundled":409},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::baseos","package":"kernel-modules-core","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-284.11.1.el9_2"}]}],"bundled":409},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::baseos","package":"kernel-modules-extra","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-284.11.1.el9_2"}]}],"bundled":409},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::baseos","package":"kernel-tools","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-284.11.1.el9_2"}]}],"bundled":409},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::baseos","package":"kernel-tools-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-284.11.1.el9_2"}]}],"bundled":409},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::baseos","package":"kernel-tools-libs","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-284.11.1.el9_2"}]}],"bundled":409},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::baseos","package":"kernel-uki-virt","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-284.11.1.el9_2"}]}],"bundled":409},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::baseos","package":"kernel-zfcpdump","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-284.11.1.el9_2"}]}],"bundled":409},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::baseos","package":"kernel-zfcpdump-core","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-284.11.1.el9_2"}]}],"bundled":409},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::baseos","package":"kernel-zfcpdump-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-284.11.1.el9_2"}]}],"bundled":409},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::baseos","package":"kernel-zfcpdump-modules","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-284.11.1.el9_2"}]}],"bundled":409},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::baseos","package":"kernel-zfcpdump-modules-core","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-284.11.1.el9_2"}]}],"bundled":409},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::baseos","package":"kernel-zfcpdump-modules-extra","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-284.11.1.el9_2"}]}],"bundled":409},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::baseos","package":"perf-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-284.11.1.el9_2"}]}],"bundled":409},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::baseos","package":"python3-perf","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-284.11.1.el9_2"}]}],"bundled":409},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::baseos","package":"python3-perf-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-284.11.1.el9_2"}]}],"bundled":409},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::crb","package":"bpftool-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:7.0.0-284.11.1.el9_2"}]}],"bundled":409},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::crb","package":"kernel-64k-debug-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-284.11.1.el9_2"}]}],"bundled":409},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::crb","package":"kernel-64k-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-284.11.1.el9_2"}]}],"bundled":409},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::crb","package":"kernel-debug-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-284.11.1.el9_2"}]}],"bundled":409},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::crb","package":"kernel-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-284.11.1.el9_2"}]}],"bundled":409},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::crb","package":"kernel-debuginfo-common-aarch64","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-284.11.1.el9_2"}]}],"bundled":409},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::crb","package":"kernel-debuginfo-common-ppc64le","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-284.11.1.el9_2"}]}],"bundled":409},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::crb","package":"kernel-debuginfo-common-s390x","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-284.11.1.el9_2"}]}],"bundled":409},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::crb","package":"kernel-debuginfo-common-x86_64","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-284.11.1.el9_2"}]}],"bundled":409},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::crb","package":"kernel-tools-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-284.11.1.el9_2"}]}],"bundled":409},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::crb","package":"kernel-tools-libs-devel","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-284.11.1.el9_2"}]}],"bundled":409},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::crb","package":"kernel-zfcpdump-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-284.11.1.el9_2"}]}],"bundled":409},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::crb","package":"perf-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-284.11.1.el9_2"}]}],"bundled":409},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::crb","package":"python3-perf-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-284.11.1.el9_2"}]}],"bundled":409},{"source":"osv","ecosystem":"Root:Debian:11","package":"linux","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.10.262-1.aikido.113"},{"fixed":"5.10.262-1.aikido.114"}]}]},{"source":"osv","ecosystem":"Root:Debian:11","package":"rootio-linux","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.10.262-1.aikido.113"},{"fixed":"5.10.262-1.aikido.114"}]}]},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Micro 5.5","package":"kernel-default","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.21-150500.55.113.1"}]}],"bundled":258},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Micro 5.5","package":"kernel-default-base","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.21-150500.55.113.1.150500.6.53.1"}]}],"bundled":258},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Micro 5.5","package":"kernel-source","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.21-150500.55.113.1"}]}],"bundled":258},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Live Patching 15 SP5","package":"kernel-default","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.21-150500.55.113.1"}]}],"bundled":258},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Live Patching 15 SP5","package":"kernel-livepatch-SLE15-SP5_Update_28","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1-150500.11.3.1"}]}],"bundled":258},{"source":"osv","ecosystem":"SUSE:Linux Enterprise High Performance Computing 15 SP5-ESPOS","package":"kernel-64kb","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.21-150500.55.113.1"}]}],"bundled":258},{"source":"osv","ecosystem":"SUSE:Linux Enterprise High Performance Computing 15 SP5-ESPOS","package":"kernel-default","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.21-150500.55.113.1"}]}],"bundled":258},{"source":"osv","ecosystem":"SUSE:Linux Enterprise High Performance Computing 15 SP5-ESPOS","package":"kernel-default-base","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.21-150500.55.113.1.150500.6.53.1"}]}],"bundled":258},{"source":"osv","ecosystem":"SUSE:Linux Enterprise High Performance Computing 15 SP5-ESPOS","package":"kernel-docs","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.21-150500.55.113.1"}]}],"bundled":258},{"source":"osv","ecosystem":"SUSE:Linux Enterprise High Performance Computing 15 SP5-ESPOS","package":"kernel-obs-build","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.21-150500.55.113.1"}]}],"bundled":258},{"source":"osv","ecosystem":"SUSE:Linux Enterprise High Performance Computing 15 SP5-ESPOS","package":"kernel-source","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.21-150500.55.113.1"}]}],"bundled":258},{"source":"osv","ecosystem":"SUSE:Linux Enterprise High Performance Computing 15 SP5-ESPOS","package":"kernel-syms","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.21-150500.55.113.1"}]}],"bundled":258},{"source":"osv","ecosystem":"SUSE:Linux Enterprise High Performance Computing 15 SP5-LTSS","package":"kernel-64kb","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.21-150500.55.113.1"}]}],"bundled":258},{"source":"osv","ecosystem":"SUSE:Linux Enterprise High Performance Computing 15 SP5-LTSS","package":"kernel-default","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.21-150500.55.113.1"}]}],"bundled":258},{"source":"osv","ecosystem":"SUSE:Linux Enterprise High Performance Computing 15 SP5-LTSS","package":"kernel-default-base","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.21-150500.55.113.1.150500.6.53.1"}]}],"bundled":258},{"source":"osv","ecosystem":"SUSE:Linux Enterprise High Performance Computing 15 SP5-LTSS","package":"kernel-docs","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.21-150500.55.113.1"}]}],"bundled":258},{"source":"osv","ecosystem":"SUSE:Linux Enterprise High Performance Computing 15 SP5-LTSS","package":"kernel-obs-build","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.21-150500.55.113.1"}]}],"bundled":258},{"source":"osv","ecosystem":"SUSE:Linux Enterprise High Performance Computing 15 SP5-LTSS","package":"kernel-source","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.21-150500.55.113.1"}]}],"bundled":258},{"source":"osv","ecosystem":"SUSE:Linux Enterprise High Performance Computing 15 SP5-LTSS","package":"kernel-syms","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.21-150500.55.113.1"}]}],"bundled":258},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server 15 SP5-LTSS","package":"kernel-64kb","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.21-150500.55.113.1"}]}],"bundled":258},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server 15 SP5-LTSS","package":"kernel-default","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.21-150500.55.113.1"}]}],"bundled":258},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server 15 SP5-LTSS","package":"kernel-default-base","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.21-150500.55.113.1.150500.6.53.1"}]}],"bundled":258},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server 15 SP5-LTSS","package":"kernel-docs","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.21-150500.55.113.1"}]}],"bundled":258},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server 15 SP5-LTSS","package":"kernel-obs-build","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.21-150500.55.113.1"}]}],"bundled":258},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server 15 SP5-LTSS","package":"kernel-source","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.21-150500.55.113.1"}]}],"bundled":258},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server 15 SP5-LTSS","package":"kernel-syms","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.21-150500.55.113.1"}]}],"bundled":258},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server 15 SP5-LTSS","package":"kernel-zfcpdump","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.21-150500.55.113.1"}]}],"bundled":258},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server for SAP Applications 15 SP5","package":"kernel-default","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.21-150500.55.113.1"}]}],"bundled":258},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server for SAP Applications 15 SP5","package":"kernel-default-base","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.21-150500.55.113.1.150500.6.53.1"}]}],"bundled":258},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server for SAP Applications 15 SP5","package":"kernel-docs","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.21-150500.55.113.1"}]}],"bundled":258},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server for SAP Applications 15 SP5","package":"kernel-obs-build","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.21-150500.55.113.1"}]}],"bundled":258},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server for SAP Applications 15 SP5","package":"kernel-source","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.21-150500.55.113.1"}]}],"bundled":258},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server for SAP Applications 15 SP5","package":"kernel-syms","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.21-150500.55.113.1"}]}],"bundled":258},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Micro 5.5","package":"kernel-rt","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.21-150500.13.100.2"}]}],"bundled":260},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Micro 5.5","package":"kernel-source-rt","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.21-150500.13.100.1"}]}],"bundled":260},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Micro 5.3","package":"kernel-rt","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.21-150400.15.124.1"}]}],"bundled":221},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Micro 5.3","package":"kernel-source-rt","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.21-150400.15.124.1"}]}],"bundled":221},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Micro 5.4","package":"kernel-rt","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.21-150400.15.124.1"}]}],"bundled":221},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Micro 5.4","package":"kernel-source-rt","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.21-150400.15.124.1"}]}],"bundled":221},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Micro 5.3","package":"kernel-default","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.21-150400.24.170.2"}]}],"bundled":221},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Micro 5.3","package":"kernel-default-base","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.21-150400.24.170.2.150400.24.86.2"}]}],"bundled":221},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Micro 5.4","package":"kernel-default","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.21-150400.24.170.2"}]}],"bundled":221},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Micro 5.4","package":"kernel-default-base","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.21-150400.24.170.2.150400.24.86.2"}]}],"bundled":221},{"source":"osv","ecosystem":"SUSE:Linux Enterprise High Availability Extension 15 SP4","package":"kernel-default","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.21-150400.24.170.2"}]}],"bundled":221},{"source":"osv","ecosystem":"SUSE:Linux Enterprise High Performance Computing 15 SP4-ESPOS","package":"kernel-64kb","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.21-150400.24.170.2"}]}],"bundled":221},{"source":"osv","ecosystem":"SUSE:Linux Enterprise High Performance Computing 15 SP4-ESPOS","package":"kernel-default","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.21-150400.24.170.2"}]}],"bundled":221},{"source":"osv","ecosystem":"SUSE:Linux Enterprise High Performance Computing 15 SP4-ESPOS","package":"kernel-default-base","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.21-150400.24.170.2.150400.24.86.2"}]}],"bundled":221},{"source":"osv","ecosystem":"SUSE:Linux Enterprise High Performance Computing 15 SP4-ESPOS","package":"kernel-docs","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.21-150400.24.170.1"}]}],"bundled":221},{"source":"osv","ecosystem":"SUSE:Linux Enterprise High Performance Computing 15 SP4-ESPOS","package":"kernel-obs-build","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.21-150400.24.170.2"}]}],"bundled":221},{"source":"osv","ecosystem":"SUSE:Linux Enterprise High Performance Computing 15 SP4-ESPOS","package":"kernel-source","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.21-150400.24.170.1"}]}],"bundled":221},{"source":"osv","ecosystem":"SUSE:Linux Enterprise High Performance Computing 15 SP4-ESPOS","package":"kernel-syms","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.21-150400.24.170.1"}]}],"bundled":221},{"source":"osv","ecosystem":"SUSE:Linux Enterprise High Performance Computing 15 SP4-LTSS","package":"kernel-64kb","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.21-150400.24.170.2"}]}],"bundled":221},{"source":"osv","ecosystem":"SUSE:Linux Enterprise High Performance Computing 15 SP4-LTSS","package":"kernel-default","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.21-150400.24.170.2"}]}],"bundled":221},{"source":"osv","ecosystem":"SUSE:Linux Enterprise High Performance Computing 15 SP4-LTSS","package":"kernel-default-base","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.21-150400.24.170.2.150400.24.86.2"}]}],"bundled":221},{"source":"osv","ecosystem":"SUSE:Linux Enterprise High Performance Computing 15 SP4-LTSS","package":"kernel-docs","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.21-150400.24.170.1"}]}],"bundled":221},{"source":"osv","ecosystem":"SUSE:Linux Enterprise High Performance Computing 15 SP4-LTSS","package":"kernel-obs-build","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.21-150400.24.170.2"}]}],"bundled":221},{"source":"osv","ecosystem":"SUSE:Linux Enterprise High Performance Computing 15 SP4-LTSS","package":"kernel-source","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.21-150400.24.170.1"}]}],"bundled":221},{"source":"osv","ecosystem":"SUSE:Linux Enterprise High Performance Computing 15 SP4-LTSS","package":"kernel-syms","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.21-150400.24.170.1"}]}],"bundled":221},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server 15 SP4-LTSS","package":"kernel-64kb","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.21-150400.24.170.2"}]}],"bundled":221},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server 15 SP4-LTSS","package":"kernel-default","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.21-150400.24.170.2"}]}],"bundled":221},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server 15 SP4-LTSS","package":"kernel-default-base","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.21-150400.24.170.2.150400.24.86.2"}]}],"bundled":221},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server 15 SP4-LTSS","package":"kernel-docs","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.21-150400.24.170.1"}]}],"bundled":221},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server 15 SP4-LTSS","package":"kernel-obs-build","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.21-150400.24.170.2"}]}],"bundled":221},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server 15 SP4-LTSS","package":"kernel-source","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.21-150400.24.170.1"}]}],"bundled":221},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server 15 SP4-LTSS","package":"kernel-syms","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.21-150400.24.170.1"}]}],"bundled":221},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server 15 SP4-LTSS","package":"kernel-zfcpdump","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.21-150400.24.170.2"}]}],"bundled":221},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server for SAP Applications 15 SP4","package":"kernel-default","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.21-150400.24.170.2"}]}],"bundled":221},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server for SAP Applications 15 SP4","package":"kernel-default-base","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.21-150400.24.170.2.150400.24.86.2"}]}],"bundled":221},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server for SAP Applications 15 SP4","package":"kernel-docs","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.21-150400.24.170.1"}]}],"bundled":221},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server for SAP Applications 15 SP4","package":"kernel-obs-build","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.21-150400.24.170.2"}]}],"bundled":221},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server for SAP Applications 15 SP4","package":"kernel-source","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.21-150400.24.170.1"}]}],"bundled":221},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server for SAP Applications 15 SP4","package":"kernel-syms","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.21-150400.24.170.1"}]}],"bundled":221},{"source":"osv","ecosystem":"SUSE:Manager Proxy 4.3","package":"kernel-default","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.21-150400.24.170.2"}]}],"bundled":221},{"source":"osv","ecosystem":"SUSE:Manager Proxy 4.3","package":"kernel-default-base","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.21-150400.24.170.2.150400.24.86.2"}]}],"bundled":221},{"source":"osv","ecosystem":"SUSE:Manager Proxy 4.3","package":"kernel-source","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.21-150400.24.170.1"}]}],"bundled":221},{"source":"osv","ecosystem":"SUSE:Manager Proxy 4.3","package":"kernel-syms","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.21-150400.24.170.1"}]}],"bundled":221},{"source":"osv","ecosystem":"SUSE:Manager Server 4.3","package":"kernel-default","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.21-150400.24.170.2"}]}],"bundled":221},{"source":"osv","ecosystem":"SUSE:Manager Server 4.3","package":"kernel-default-base","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.21-150400.24.170.2.150400.24.86.2"}]}],"bundled":221},{"source":"osv","ecosystem":"SUSE:Manager Server 4.3","package":"kernel-source","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.21-150400.24.170.1"}]}],"bundled":221},{"source":"osv","ecosystem":"SUSE:Manager Server 4.3","package":"kernel-syms","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.21-150400.24.170.1"}]}],"bundled":221},{"source":"osv","ecosystem":"SUSE:Manager Server 4.3","package":"kernel-zfcpdump","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.21-150400.24.170.2"}]}],"bundled":221},{"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-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-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-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-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-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-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-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-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-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: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"]}],"products":[{"vendor":"linux","product":"linux"},{"vendor":"linux","product":"linux_kernel"}],"references":[{"url":"https://git.kernel.org/stable/c/8e142744f0e96abc69ccd99e6d6c7eb662267f21","tags":["Patch","web","report"]},{"url":"https://git.kernel.org/stable/c/960a8a35a6027a08c4b511435bf59609b5d5e5cd","tags":["Patch","web","report"]},{"url":"https://git.kernel.org/stable/c/8659ab3d936fcf0084676f98b75b317017aa8f82","tags":["Patch","web","report"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-50151","tags":["advisory"]},{"url":"https://github.com/advisories/GHSA-gvgm-6pph-fj6g"},{"url":"https://errata.tuxcare.com/els_os/ubuntu20.04els/CLSA-2026-1789958474.html","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-1247","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-47519","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-50764","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-50864","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-54047","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-54150","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-49861","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-53179","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-53216","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-39826","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-39985","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-39987","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-40082","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-40137","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-40146","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-40160","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-40333","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-68188","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-68190","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-68217","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-68330","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-68750","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-68767","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-68771","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-68796","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-68797","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-23050","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-23105","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-23125","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-43015","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-43158","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-43198","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-43279","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-43421","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-43449","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-45856","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-45970","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-46209","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-46275","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-52920","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-52942","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-52991","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-53040","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-53130","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-53189","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-53264","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-53355","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-63814","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-63823","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-63904","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-63961","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-64237","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-64304","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-64305","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-64318","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-64320","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-64322","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-64323","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-64330","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-64340","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-64341","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-64342","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-64343","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-64344","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-64348","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-64351","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-64372","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-64375","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-64378","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-64379","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-64381","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-64420","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-64422","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-64423","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-64424","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-64438","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-64440","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-64442","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-64443","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-64445","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-64446","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-64448","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-64449","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-64452","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-64471","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-64483","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-64504","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-64505","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-64563","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-68121","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-68143","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-68144","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-68153","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-68156","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-68158","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-68160","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-68188","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-68199","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-68214","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-68335","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-68357","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-68363","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-68373","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-68376","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-68377","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-68402","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-72014","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-72047","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-72083","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-72171","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-72233","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-72234","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-72296","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-72299","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-72351","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-72374","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-72406","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-74255","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-74394","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-74402","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-74408","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-74444","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-74505","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-74548","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-74556","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-74580","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-74583","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-74588","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-74609","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-74630","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-74656","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-74660","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-74667","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-74679","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-74705","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-80558","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-80570","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-80590","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-80600","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-80601","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-80622","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-80732","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-80747","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-80785","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-80788","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-80812","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-80823","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-80844","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-80907","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-80908","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-80909","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-80948","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-89607","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-89674","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-89720","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-89724","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-89729","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-89733","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-89742","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-89777","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-89778","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-89780","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-89783","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-89784","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-89786","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-89789","tags":["advisory"]},{"url":"https://github.com/CVEProject/cvelistV5/tree/main/cves/2022/50xxx/CVE-2022-50151.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-2022-50151","tags":["advisory"]},{"url":"https://www.openeuler.org/zh/security/security-bulletins/detail/?id=openEuler-SA-2026-1341","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-49190","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-49309","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-49829","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-50159","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-50616","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-50735","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-52927","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-53250","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-53254","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-53521","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-53594","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-53712","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-53840","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-54048","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-54145","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-54321","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-21981","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-23138","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-37766","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-37770","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-37947","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-38068","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-38154","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-38250","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-38480","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-38556","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-38572","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-38574","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-38618","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-38676","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-38728","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-39676","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-39702","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-39744","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-39749","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-39797","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-39828","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-39853","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-39860","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-39913","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-39945","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-40018","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-40105","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-40215","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-40271","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-40280","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-40342","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-40346","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-68192","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-68285","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-68819","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-71084","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-71091","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-71120","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-22998","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-23038","tags":["advisory"]},{"url":"https://access.redhat.com/errata/RHSA-2023:2458","tags":["advisory"]},{"url":"https://access.redhat.com/security/updates/classification/#important","tags":["article"]},{"url":"https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/9/html/9.2_release_notes/index","tags":["article"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=1946801","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=1997177","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2004384","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2061703","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2073091","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2078466","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2089701","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2090723","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2104445","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2106830","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2107924","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2108691","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2114937","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2115631","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2116442","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2119809","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2122228","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2123056","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2123857","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2124788","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2130141","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2130487","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2133483","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2133490","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2134377","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2134380","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2134451","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2134506","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2134517","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2134528","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2137979","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2138321","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2138605","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2138866","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2139610","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2142657","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2143893","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2143943","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2144720","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2147364","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2149448","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2149790","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2150947","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2150960","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2150979","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2151270","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2152131","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2154171","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2154235","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2154879","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2160023","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2160028","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2160443","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2162120","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2165721","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2165741","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2166658","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2168246","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2168599","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2169017","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2176192","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2177371","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2179342","tags":["report"]},{"url":"https://security.access.redhat.com/data/csaf/v2/advisories/2023/rhsa-2023_2458.json","tags":["advisory"]},{"url":"https://access.redhat.com/security/cve/CVE-2021-26341","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2021-26341","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2021-26341","tags":["advisory"]},{"url":"https://grsecurity.net/amd_branch_mispredictor_part_2_where_no_cpu_has_gone_before","tags":["article"]},{"url":"https://www.amd.com/en/corporate/product-security/bulletin/amd-sb-1026","tags":["article"]},{"url":"https://www.amd.com/system/files/documents/software-techniques-for-managing-speculation.pdf","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2021-33631","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2261976","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2021-33631","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2021-33631","tags":["advisory"]},{"url":"https://seclists.org/oss-sec/2024/q1/65","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2021-33655","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2021-33655","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2021-33655","tags":["advisory"]},{"url":"https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=086ff84617185393a0bbf25830c4f36412a7d3f4","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2021-47393","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2282345","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2021-47393","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2021-47393","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024052147-CVE-2021-47393-ea1c@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2021-47441","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2282851","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2021-47441","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2021-47441","tags":["advisory"]},{"url":"https://access.redhat.com/security/cve/CVE-2021-47560","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2283389","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2021-47560","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2021-47560","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024052451-CVE-2021-47560-4a52@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2021-47592","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2293235","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2021-47592","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2021-47592","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024061919-CVE-2021-47592-7ca6@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2021-47671","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2360784","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2021-47671","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2021-47671","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025041735-CVE-2021-47671-9b1a@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-1462","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-1462","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-1462","tags":["advisory"]},{"url":"https://seclists.org/oss-sec/2022/q2/155","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-1789","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-1789","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-1789","tags":["advisory"]},{"url":"https://github.com/advisories/GHSA-v8pq-23qj-q7x7","tags":["advisory"]},{"url":"https://www.openwall.com/lists/oss-security/2022/05/25/2","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-1882","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-1882","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-1882","tags":["advisory"]},{"url":"https://git.kernel.org/linus/353f7988dd8413c4","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-2196","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-2196","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-2196","tags":["advisory"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-2663","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-2663","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-2663","tags":["advisory"]},{"url":"https://lore.kernel.org/netfilter-devel/20220826045658.100360-1-dgl@dgl.cx/T/","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-3028","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-3028","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-3028","tags":["advisory"]},{"url":"https://github.com/torvalds/linux/commit/ba953a9d89a00c078b85f4b190bc1dde66fe16b5","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-3435","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-3435","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-3435","tags":["advisory"]},{"url":"https://lore.kernel.org/netdev/20221005181257.8897-1-dsahern@kernel.org/T/#u","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-3522","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-3522","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-3522","tags":["advisory"]},{"url":"https://lore.kernel.org/all/20221004193400.110155-3-peterx@redhat.com/T/#u","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-3524","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-3524","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-3524","tags":["advisory"]},{"url":"https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=3c52c6bb831f6335c176a0fc7214e26f43adbd11","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-3566","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-3566","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-3566","tags":["advisory"]},{"url":"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=f49cd2f4d6170d27a2c61f1fecb03d8a70c91f57","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-3567","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-3567","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-3567","tags":["advisory"]},{"url":"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=364f997b5cfe1db0d63a390fe7c801fa2b3115f6","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-3619","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-3619","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-3619","tags":["advisory"]},{"url":"https://git.kernel.org/pub/scm/linux/kernel/git/bluetooth/bluetooth-next.git/commit/?id=97097c85c088e11651146da32a4e1cdb9dfa6193","tags":["article"]},{"url":"https://vuldb.com/?id.211918","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-3623","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-3623","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-3623","tags":["advisory"]},{"url":"https://git.kernel.org/pub/scm/linux/kernel/git/bpf/bpf-next.git/commit/?id=fac35ba763ed07ba93154c95ffc0c4a55023707f","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-3625","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-3625","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-3625","tags":["advisory"]},{"url":"https://git.kernel.org/pub/scm/linux/kernel/git/klassert/ipsec-next.git/commit/?id=6b4db2e528f650c7fb712961aac36455468d5902","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-3628","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-3628","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-3628","tags":["advisory"]},{"url":"https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/patch/drivers/net/wireless/broadcom/brcm80211/brcmfmac/fweh.c?id=6788ba8aed4e28e90f72d68a9d794e34eac17295","tags":["article"]},{"url":"https://seclists.org/oss-sec/2022/q4/60","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-3640","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-3640","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-3640","tags":["advisory"]},{"url":"https://git.kernel.org/pub/scm/linux/kernel/git/bluetooth/bluetooth-next.git/commit/?id=42cf46dea905a80f6de218e837ba4d4cc33d6979","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-3707","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-3707","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-3707","tags":["advisory"]},{"url":"https://lore.kernel.org/all/20221007013708.1946061-1-zyytlz.wz@163.com/","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-4128","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-4128","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-4128","tags":["advisory"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-4129","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-4129","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-4129","tags":["advisory"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-4662","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2155788","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-4662","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-4662","tags":["advisory"]},{"url":"https://lore.kernel.org/all/20220913140355.910732567@linuxfoundation.org/","tags":["article"]},{"url":"https://lore.kernel.org/all/CAB7eexLLApHJwZfMQ=X-PtRhw0BgO+5KcSMS05FNUYejJXqtSA@mail.gmail.com/","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-20141","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-20141","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-20141","tags":["advisory"]},{"url":"https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/net/ipv4/igmp.c?h=v5.19\u0026id=23d2b94043ca8835bd1e67749020e839f396a1c2","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-21505","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-21505","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-21505","tags":["advisory"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-28388","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-28388","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-28388","tags":["advisory"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-33743","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-33743","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-33743","tags":["advisory"]},{"url":"https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/drivers/net/xen-netfront.c?h=v5.19-rc7\u0026id=f63c2c2032c2e3caad9add3b82cc6e91c376fd26","tags":["article"]},{"url":"https://www.openwall.com/lists/oss-security/2022/07/05/5","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-36280","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2133450","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-36280","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-36280","tags":["advisory"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-36879","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2119855","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-36879","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-36879","tags":["advisory"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-39188","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-39188","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-39188","tags":["advisory"]},{"url":"https://bugs.chromium.org/p/project-zero/issues/detail?id=2329","tags":["article"]},{"url":"https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=b67fbebd4cf980aecbcc750e1462128bffe8ae15","tags":["article"]},{"url":"https://lore.kernel.org/stable/20220831191348.3388208-1-jannh@google.com/T/#u","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-39189","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-39189","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-39189","tags":["advisory"]},{"url":"https://bugs.chromium.org/p/project-zero/issues/detail?id=2309","tags":["article"]},{"url":"https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=6cd88243c7e03845a450795e134b488fc2afb736","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-41674","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-41674","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-41674","tags":["advisory"]},{"url":"https://www.openwall.com/lists/oss-security/2022/10/13/2","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-42703","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-42703","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-42703","tags":["advisory"]},{"url":"https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=2555283eb40df89945557273121e9393ef9b542b","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-42720","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-42720","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-42720","tags":["advisory"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-42721","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-42721","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-42721","tags":["advisory"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-42722","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-42722","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-42722","tags":["advisory"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-42896","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-42896","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-42896","tags":["advisory"]},{"url":"https://github.com/google/security-research/security/advisories/GHSA-pf87-6c9q-jvm4","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-43750","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-43750","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-43750","tags":["advisory"]},{"url":"https://github.com/torvalds/linux/commit/a659daf63d16aa883be42f3f34ff84235c302198","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-47929","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-47929","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-47929","tags":["advisory"]},{"url":"https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=96398560f26aa07e8f2969d73c8197e6a6d10407","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-48695","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2278999","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-48695","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-48695","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024050348-CVE-2022-48695-8a9e@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-48696","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2278959","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-48696","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-48696","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024050348-CVE-2022-48696-b671@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-48701","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2278950","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-48701","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-48701","tags":["advisory"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-48883","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2306404","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-48883","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-48883","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024082108-CVE-2022-48883-4df4@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-48884","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2306405","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-48884","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-48884","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024082108-CVE-2022-48884-b273@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-48885","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2306406","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-48885","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-48885","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024082108-CVE-2022-48885-c422@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-48915","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2307168","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-48915","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-48915","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024082216-CVE-2022-48915-6663@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-48934","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2307190","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-48934","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-48934","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024082224-CVE-2022-48934-6f50@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-48939","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2307195","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-48939","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-48939","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024082226-CVE-2022-48939-ff01@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-48942","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2307198","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-48942","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-48942","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024082227-CVE-2022-48942-ca91@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-48974","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2320729","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-48974","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-48974","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024102145-CVE-2022-48974-d2d0@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-48976","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2320792","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-48976","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-48976","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024102145-CVE-2022-48976-2980@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-48978","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2320665","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-48978","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-48978","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024102146-CVE-2022-48978-8a19@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-48992","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2320793","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-48992","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-48992","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024102148-CVE-2022-48992-2962@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-49010","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2320780","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-49010","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-49010","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024102152-CVE-2022-49010-f8e1@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-49022","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2320721","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-49022","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-49022","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024102154-CVE-2022-49022-c605@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-49049","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2347670","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-49049","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-49049","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025022651-CVE-2022-49049-d847@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-49058","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2348254","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-49058","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-49058","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025022653-CVE-2022-49058-5df2@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-49070","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2347832","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-49070","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-49070","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025022655-CVE-2022-49070-6511@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-49072","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2348209","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-49072","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-49072","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025022655-CVE-2022-49072-8479@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-49080","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2347644","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-49080","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-49080","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025022656-CVE-2022-49080-5718@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-49081","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2347739","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-49081","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-49081","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025022657-CVE-2022-49081-7a0f@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-49087","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2348272","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-49087","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-49087","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025022658-CVE-2022-49087-1127@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-49097","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2348060","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-49097","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-49097","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025022659-CVE-2022-49097-fb5e@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-49111","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2347952","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-49111","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-49111","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025022602-CVE-2022-49111-8795@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-49114","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2348136","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-49114","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-49114","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025022602-CVE-2022-49114-86bb@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-49116","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2347686","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-49116","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-49116","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025022603-CVE-2022-49116-8bf8@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-49136","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2348179","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-49136","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-49136","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025022606-CVE-2022-49136-033c@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-49204","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2348220","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-49204","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-49204","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025022618-CVE-2022-49204-38c3@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-49205","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2348068","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-49205","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-49205","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025022618-CVE-2022-49205-5180@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-49207","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2347653","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-49207","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-49207","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025022619-CVE-2022-49207-cfc1@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-49214","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2347932","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-49214","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-49214","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025022620-CVE-2022-49214-1b9a@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-49223","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2348190","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-49223","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-49223","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025022621-CVE-2022-49223-5a42@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-49236","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2348037","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-49236","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-49236","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025022624-CVE-2022-49236-e3f7@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-49275","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2347795","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-49275","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-49275","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025022630-CVE-2022-49275-9e36@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-49283","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2347823","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-49283","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-49283","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025022632-CVE-2022-49283-e19b@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-49294","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2348003","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-49294","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-49294","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025022625-CVE-2022-49294-a2fc@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-49319","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2347683","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-49319","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-49319","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025022637-CVE-2022-49319-f0b3@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-49323","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2347660","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-49323","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-49323","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025022638-CVE-2022-49323-7559@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-49328","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2348217","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-49328","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-49328","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025022638-CVE-2022-49328-ec2f@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-49333","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2347763","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-49333","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-49333","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025022639-CVE-2022-49333-8ae3@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-49345","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2347854","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-49345","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-49345","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025022641-CVE-2022-49345-5c80@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-49356","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2348053","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-49356","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-49356","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025022643-CVE-2022-49356-6195@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-49362","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2347808","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-49362","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-49362","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025022644-CVE-2022-49362-3299@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-49365","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2347917","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-49365","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-49365","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025022645-CVE-2022-49365-37e7@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-49371","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2348122","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-49371","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-49371","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025022646-CVE-2022-49371-30f9@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-49372","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2348024","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-49372","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-49372","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025022646-CVE-2022-49372-45e1@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-49376","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2347964","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-49376","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-49376","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025022646-CVE-2022-49376-9ec1@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-49379","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2348236","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-49379","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-49379","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025022647-CVE-2022-49379-722a@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-49401","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2347828","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-49401","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-49401","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025022651-CVE-2022-49401-2fa3@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-49416","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2347666","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-49416","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-49416","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025022653-CVE-2022-49416-7c8e@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-49429","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2347775","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-49429","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-49429","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025022655-CVE-2022-49429-c9a7@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-49434","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2348072","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-49434","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-49434","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025022656-CVE-2022-49434-4a2c@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-49442","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2347659","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-49442","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-49442","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025022657-CVE-2022-49442-ae21@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-49451","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2347940","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-49451","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-49451","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025022659-CVE-2022-49451-5d2f@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-49471","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2348322","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-49471","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-49471","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025022602-CVE-2022-49471-4e82@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-49492","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2347913","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-49492","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-49492","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025022606-CVE-2022-49492-6a2d@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-49511","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2347746","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-49511","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-49511","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025022609-CVE-2022-49511-100a@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-49513","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2348128","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-49513","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-49513","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025022609-CVE-2022-49513-f147@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-49519","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2348111","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-49519","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-49519","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025022610-CVE-2022-49519-3b0d@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-49520","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2347923","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-49520","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-49520","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025022611-CVE-2022-49520-465c@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-49539","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2347661","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-49539","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-49539","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025022614-CVE-2022-49539-9ea2@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-49541","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2348119","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-49541","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-49541","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025022614-CVE-2022-49541-7460@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-49548","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2347871","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-49548","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-49548","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025022615-CVE-2022-49548-47fe@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-49552","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2347947","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-49552","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-49552","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025022616-CVE-2022-49552-e30f@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-49562","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2347787","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-49562","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-49562","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025022618-CVE-2022-49562-1d2c@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-49565","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2347779","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-49565","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-49565","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025022605-CVE-2022-49565-e60d@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-49572","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2348047","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-49572","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-49572","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025022606-CVE-2022-49572-51d7@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-49573","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2348175","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-49573","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-49573","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025022607-CVE-2022-49573-e482@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-49574","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2348338","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-49574","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-49574","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025022607-CVE-2022-49574-018f@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-49575","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2347915","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-49575","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-49575","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025022607-CVE-2022-49575-ccf0@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-49577","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2348255","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-49577","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-49577","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025022607-CVE-2022-49577-da62@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-49578","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2347713","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-49578","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-49578","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025022607-CVE-2022-49578-6d9b@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-49579","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2348016","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-49579","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-49579","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025022608-CVE-2022-49579-4f40@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-49580","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2347671","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-49580","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-49580","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025022608-CVE-2022-49580-c398@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-49583","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2348151","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-49583","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-49583","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025022608-CVE-2022-49583-d8d5@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-49585","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2347801","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-49585","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-49585","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025022609-CVE-2022-49585-659c@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-49586","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2348169","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-49586","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-49586","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025022609-CVE-2022-49586-f70a@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-49587","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2347976","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-49587","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-49587","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025022609-CVE-2022-49587-33ba@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-49588","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2348182","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-49588","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-49588","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025022609-CVE-2022-49588-9a52@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-49589","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2347975","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-49589","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-49589","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025022609-CVE-2022-49589-fb90@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-49590","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2347769","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-49590","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-49590","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025022610-CVE-2022-49590-44d5@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-49592","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2347803","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-49592","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-49592","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025022610-CVE-2022-49592-f07c@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-49593","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2348172","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-49593","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-49593","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025022610-CVE-2022-49593-b98d@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-49594","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2348000","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-49594","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-49594","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025022610-CVE-2022-49594-5cb2@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-49595","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2348198","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-49595","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-49595","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025022610-CVE-2022-49595-6abc@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-49596","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2348325","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-49596","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-49596","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025022611-CVE-2022-49596-ebcf@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-49598","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2347827","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-49598","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-49598","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025022611-CVE-2022-49598-d784@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-49599","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2348356","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-49599","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-49599","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025022611-CVE-2022-49599-4a64@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-49600","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2347934","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-49600","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-49600","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025022611-CVE-2022-49600-9d38@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-49601","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2348150","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-49601","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-49601","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025022611-CVE-2022-49601-75fc@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-49602","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2347941","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-49602","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-49602","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025022612-CVE-2022-49602-0366@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-49603","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2348331","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-49603","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-49603","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025022612-CVE-2022-49603-e042@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-49604","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2347711","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-49604","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-49604","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025022612-CVE-2022-49604-eb2c@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-49612","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2347726","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-49612","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-49612","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025022613-CVE-2022-49612-8875@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-49629","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2348210","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-49629","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-49629","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025022616-CVE-2022-49629-c5d3@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-49630","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2348249","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-49630","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-49630","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025022616-CVE-2022-49630-71c3@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-49631","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2348158","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-49631","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-49631","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025022617-CVE-2022-49631-b546@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-49632","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2348197","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-49632","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-49632","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025022617-CVE-2022-49632-ea1e@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-49634","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2347966","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-49634","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-49634","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025022617-CVE-2022-49634-4a89@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-49636","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2347709","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-49636","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-49636","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025022618-CVE-2022-49636-b283@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-49637","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2348310","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-49637","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-49637","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025022618-CVE-2022-49637-402f@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-49638","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2348295","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-49638","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-49638","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025022618-CVE-2022-49638-e524@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-49639","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2348239","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-49639","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-49639","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025022618-CVE-2022-49639-a1b4@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-49641","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2347954","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-49641","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-49641","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025022618-CVE-2022-49641-00e7@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-49642","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2348085","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-49642","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-49642","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025022619-CVE-2022-49642-dbbe@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-49644","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2348280","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-49644","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-49644","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025022619-CVE-2022-49644-e3b0@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-49646","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2348256","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-49646","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-49646","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025022619-CVE-2022-49646-248b@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-49647","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2348050","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-49647","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-49647","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025022619-CVE-2022-49647-b3cb@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-49651","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2347649","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-49651","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-49651","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025022620-CVE-2022-49651-601b@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-49655","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2347645","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-49655","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-49655","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025022621-CVE-2022-49655-0370@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-49659","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2347817","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-49659","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-49659","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025022622-CVE-2022-49659-31c4@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-49666","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2348303","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-49666","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-49666","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025022623-CVE-2022-49666-98ab@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-49688","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2347700","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-49688","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-49688","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025022627-CVE-2022-49688-5c71@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-49700","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2348237","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-49700","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-49700","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025022629-CVE-2022-49700-2b3e@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-49723","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2347749","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-49723","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-49723","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025022633-CVE-2022-49723-ac32@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-49726","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2347948","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-49726","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-49726","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025022633-CVE-2022-49726-582f@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-49739","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2355515","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-49739","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-49739","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025032756-CVE-2022-49739-a93e@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-49753","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2355521","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-49753","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-49753","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025032701-CVE-2022-49753-d1ce@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-49848","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2363502","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-49848","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-49848","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025050143-CVE-2022-49848-0e49@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-49853","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2363383","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-49853","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-49853","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025050144-CVE-2022-49853-a5ef@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-49862","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2363458","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-49862","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-49862","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025050147-CVE-2022-49862-04f2@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-49872","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2363447","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-49872","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-49872","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025050151-CVE-2022-49872-0c67@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-49902","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2363385","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-49902","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-49902","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025050102-CVE-2022-49902-59fe@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-49903","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2363491","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-49903","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-49903","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025050102-CVE-2022-49903-23a6@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-49908","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2363373","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-49908","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-49908","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025050104-CVE-2022-49908-ad9a@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-49911","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2363421","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-49911","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-49911","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025050105-CVE-2022-49911-2e28@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-49920","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2363410","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-49920","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-49920","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025050108-CVE-2022-49920-667b@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-49925","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2363363","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-49925","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-49925","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025050110-CVE-2022-49925-2485@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-49934","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2373399","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-49934","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-49934","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025061845-CVE-2022-49934-108e@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-49935","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2373404","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-49935","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-49935","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025061847-CVE-2022-49935-bf21@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-49936","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2373402","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-49936","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-49936","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025061847-CVE-2022-49936-f434@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-49942","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2373421","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-49942","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-49942","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025061807-CVE-2022-49942-8f93@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-49943","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2373547","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-49943","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-49943","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025061807-CVE-2022-49943-7809@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-49944","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2373608","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-49944","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-49944","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025061807-CVE-2022-49944-b44c@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-49951","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2373687","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-49951","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-49951","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025061810-CVE-2022-49951-bc9b@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-49958","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2373618","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-49958","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-49958","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025061812-CVE-2022-49958-35f5@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-49959","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2373521","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-49959","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-49959","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025061813-CVE-2022-49959-d2b7@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-49960","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2373614","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-49960","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-49960","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025061813-CVE-2022-49960-d554@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-49961","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2373530","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-49961","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-49961","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025061814-CVE-2022-49961-b7fa@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-49962","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2373582","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-49962","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-49962","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025061814-CVE-2022-49962-aced@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-49964","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2373491","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-49964","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-49964","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025061815-CVE-2022-49964-ff03@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-49965","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2373583","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-49965","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-49965","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025061815-CVE-2022-49965-08f3@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-49966","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2373592","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-49966","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-49966","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025061815-CVE-2022-49966-6b06@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-49967","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2373651","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-49967","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-49967","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025061816-CVE-2022-49967-d167@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-49969","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2373635","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-49969","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-49969","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025061816-CVE-2022-49969-fd54@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-49970","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2373515","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-49970","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-49970","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025061817-CVE-2022-49970-2d63@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-49971","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2373584","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-49971","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-49971","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025061817-CVE-2022-49971-7e9c@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-49973","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2373445","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-49973","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-49973","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025061818-CVE-2022-49973-d4f3@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-49974","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2373643","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-49974","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-49974","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025061818-CVE-2022-49974-86bb@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-49979","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2373406","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-49979","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-49979","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025061820-CVE-2022-49979-f695@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-49980","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2373443","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-49980","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-49980","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025061820-CVE-2022-49980-982c@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-49981","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2373552","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-49981","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-49981","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025061821-CVE-2022-49981-305f@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-49982","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2373644","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-49982","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-49982","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025061821-CVE-2022-49982-cb7f@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-49983","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2373495","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-49983","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-49983","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025061821-CVE-2022-49983-dd32@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-49984","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2373410","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-49984","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-49984","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025061822-CVE-2022-49984-fa6b@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-49985","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2373540","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-49985","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-49985","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025061822-CVE-2022-49985-3e41@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-49986","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2373671","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-49986","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-49986","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025061823-CVE-2022-49986-d434@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-49990","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2373524","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-49990","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-49990","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025061824-CVE-2022-49990-a8af@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-49991","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2373639","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-49991","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-49991","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025061824-CVE-2022-49991-c44f@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-49992","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2373483","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-49992","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-49992","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025061825-CVE-2022-49992-c5f0@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-49993","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2373444","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-49993","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-49993","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025061825-CVE-2022-49993-f53f@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-49994","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2373407","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-49994","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-49994","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025061825-CVE-2022-49994-e212@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-49995","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2373560","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-49995","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-49995","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025061826-CVE-2022-49995-2d74@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-49998","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2373619","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-49998","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-49998","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025061827-CVE-2022-49998-d4dd@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-50002","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2373471","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-50002","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-50002","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025061828-CVE-2022-50002-9e5f@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-50003","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2373615","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-50003","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-50003","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025061829-CVE-2022-50003-8a4c@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-50006","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2373620","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-50006","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-50006","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025061830-CVE-2022-50006-6d77@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-50007","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2373594","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-50007","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-50007","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025061830-CVE-2022-50007-95d2@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-50014","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2373439","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-50014","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-50014","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025061833-CVE-2022-50014-2936@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-50015","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2373591","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-50015","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-50015","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025061833-CVE-2022-50015-4f7f@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-50016","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2373563","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-50016","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-50016","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025061833-CVE-2022-50016-ec03@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-50020","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2373630","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-50020","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-50020","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025061835-CVE-2022-50020-6f27@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-50021","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2373492","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-50021","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-50021","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025061835-CVE-2022-50021-2162@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-50022","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2373672","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-50022","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-50022","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025061835-CVE-2022-50022-98b6@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-50028","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2373467","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-50028","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-50028","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025061838-CVE-2022-50028-5f5e@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-50029","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2373641","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-50029","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-50029","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025061838-CVE-2022-50029-d0df@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-50032","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2373449","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-50032","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-50032","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025061839-CVE-2022-50032-9d7e@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-50033","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2373625","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-50033","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-50033","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025061839-CVE-2022-50033-75f2@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-50034","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2373665","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-50034","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-50034","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025061840-CVE-2022-50034-0d64@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-50035","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2373595","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-50035","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-50035","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025061840-CVE-2022-50035-ae6f@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-50037","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2373420","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-50037","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-50037","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025061841-CVE-2022-50037-ca44@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-50039","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2373422","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-50039","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-50039","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025061842-CVE-2022-50039-7dd9@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-50041","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2373609","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-50041","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-50041","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025061842-CVE-2022-50041-0e33@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-50044","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2373627","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-50044","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-50044","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025061843-CVE-2022-50044-0b6b@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-50046","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2373511","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-50046","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-50046","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025061844-CVE-2022-50046-9cac@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-50049","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2373440","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-50049","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-50049","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025061845-CVE-2022-50049-f6d9@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-50050","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2373423","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-50050","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-50050","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025061845-CVE-2022-50050-f90d@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-50051","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2373497","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-50051","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-50051","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025061846-CVE-2022-50051-57ac@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-50052","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2373537","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-50052","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-50052","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025061846-CVE-2022-50052-d9f4@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-50053","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2373553","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-50053","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-50053","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025061847-CVE-2022-50053-9359@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-50054","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2373531","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-50054","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-50054","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025061847-CVE-2022-50054-a29e@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-50055","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2373670","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-50055","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-50055","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025061847-CVE-2022-50055-67ab@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-50058","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2373509","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-50058","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-50058","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025061848-CVE-2022-50058-212f@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-50068","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2373573","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-50068","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-50068","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025061852-CVE-2022-50068-25c3@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-50069","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2373533","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-50069","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-50069","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025061852-CVE-2022-50069-9dba@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-50070","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2373435","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-50070","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-50070","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025061853-CVE-2022-50070-87b5@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-50079","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2373425","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-50079","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-50079","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025061856-CVE-2022-50079-b3a5@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-50081","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2373518","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-50081","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-50081","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025061857-CVE-2022-50081-80dc@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-50083","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-50083","tags":["advisory"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-50086","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2373611","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-50086","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-50086","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025061858-CVE-2022-50086-6b94@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-50088","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2373678","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-50088","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-50088","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025061859-CVE-2022-50088-32bf@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-50093","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2373601","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-50093","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-50093","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025061801-CVE-2022-50093-efbe@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-50100","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2373679","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-50100","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-50100","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025061803-CVE-2022-50100-bcf0@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-50111","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2373484","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-50111","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-50111","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025061807-CVE-2022-50111-686f@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-50113","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2373598","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-50113","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-50113","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025061808-CVE-2022-50113-bdef@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-50120","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2373624","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-50120","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-50120","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025061811-CVE-2022-50120-992d@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-50122","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2373656","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-50122","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-50122","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025061811-CVE-2022-50122-c494@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-50123","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2373577","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-50123","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-50123","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025061812-CVE-2022-50123-49ce@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-50124","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2373654","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-50124","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-50124","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025061812-CVE-2022-50124-18c3@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-50125","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2373585","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-50125","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-50125","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025061812-CVE-2022-50125-5895@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-50126","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2373442","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-50126","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-50126","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025061813-CVE-2022-50126-5c77@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-50129","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2373458","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-50129","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-50129","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025061814-CVE-2022-50129-dc2e@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-50131","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2373502","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-50131","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-50131","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025061815-CVE-2022-50131-4df3@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-50132","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2373479","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-50132","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-50132","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025061815-CVE-2022-50132-8e57@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-50133","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2373682","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-50133","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-50133","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025061815-CVE-2022-50133-6189@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-50136","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2373548","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-50136","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-50136","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025061816-CVE-2022-50136-f85e@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-50137","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2373514","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-50137","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-50137","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025061817-CVE-2022-50137-c539@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-50138","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2373512","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-50138","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-50138","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025061817-CVE-2022-50138-cd9d@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-50139","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2373499","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-50139","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-50139","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025061817-CVE-2022-50139-658f@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-50146","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2373535","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-50146","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-50146","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025061820-CVE-2022-50146-d641@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-50147","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2373455","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-50147","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-50147","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025061820-CVE-2022-50147-40b3@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-50148","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2373637","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-50148","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-50148","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025061821-CVE-2022-50148-371d@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-50149","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2373555","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-50149","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-50149","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025061821-CVE-2022-50149-5467@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-50151","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2373554","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-50151","tags":["advisory","report"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025061822-CVE-2022-50151-6132@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-50152","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2373430","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-50152","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-50152","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025061822-CVE-2022-50152-a463@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-50153","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2373447","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-50153","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-50153","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025061822-CVE-2022-50153-d408@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-50154","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2373454","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-50154","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-50154","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025061823-CVE-2022-50154-0e68@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-50156","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2373461","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-50156","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-50156","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025061824-CVE-2022-50156-3e2e@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-50157","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2373668","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-50157","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-50157","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025061824-CVE-2022-50157-14c2@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-50164","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2373419","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-50164","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-50164","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025061826-CVE-2022-50164-878e@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-50166","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2373486","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-50166","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-50166","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025061827-CVE-2022-50166-5ecc@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-50168","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2373546","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-50168","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-50168","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025061828-CVE-2022-50168-bf75@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-50172","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2373456","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-50172","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-50172","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025061829-CVE-2022-50172-0d81@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-50181","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2373666","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-50181","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-50181","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025061833-CVE-2022-50181-f573@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-50185","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2373431","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-50185","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-50185","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025061834-CVE-2022-50185-b741@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-50189","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2373414","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-50189","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-50189","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025061835-CVE-2022-50189-75d2@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-50190","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2373636","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-50190","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-50190","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025061836-CVE-2022-50190-5833@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-50194","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2373646","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-50194","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-50194","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025061837-CVE-2022-50194-536e@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-50196","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2373621","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-50196","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-50196","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025061838-CVE-2022-50196-4ce9@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-50206","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2373544","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-50206","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-50206","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025061842-CVE-2022-50206-24d2@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-50211","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2373662","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-50211","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-50211","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025061843-CVE-2022-50211-393a@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-50215","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2373545","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-50215","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-50215","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025061845-CVE-2022-50215-d5fc@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-50219","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2373517","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-50219","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-50219","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025061846-CVE-2022-50219-a138@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-50221","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2373496","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-50221","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-50221","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025061847-CVE-2022-50221-1b80@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-50224","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2373498","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-50224","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-50224","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025061848-CVE-2022-50224-7549@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-50226","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2373428","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-50226","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-50226","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025061849-CVE-2022-50226-9c73@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-50227","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2373504","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-50227","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-50227","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025061849-CVE-2022-50227-890e@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-50228","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2373529","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-50228","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-50228","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025061849-CVE-2022-50228-3904@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-50229","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2373460","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-50229","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-50229","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025061850-CVE-2022-50229-702e@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-50235","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2395362","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-50235","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-50235","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025091547-CVE-2022-50235-a5c0@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-50241","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2395429","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-50241","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-50241","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025091548-CVE-2022-50241-0f92@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-50243","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2395428","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-50243","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-50243","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025091548-CVE-2022-50243-4311@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-50263","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2395365","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-50263","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-50263","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025091503-CVE-2022-50263-040c@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-50271","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2395311","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-50271","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-50271","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025091505-CVE-2022-50271-2175@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-50285","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2395380","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-50285","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-50285","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025091507-CVE-2022-50285-955c@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-50299","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2395240","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-50299","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-50299","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025091557-CVE-2022-50299-9449@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-50302","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2395289","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-50302","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-50302","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025091558-CVE-2022-50302-89ee@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-50306","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2395351","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-50306","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-50306","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025091559-CVE-2022-50306-c1da@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-50308","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2395388","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-50308","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-50308","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025091559-CVE-2022-50308-8b1d@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-50318","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2395235","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-50318","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-50318","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025091552-CVE-2022-50318-6f5e@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-50325","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2395270","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-50325","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-50325","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025091554-CVE-2022-50325-d6bb@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-50326","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2395238","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-50326","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-50326","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025091554-CVE-2022-50326-7ffc@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-50344","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2395860","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-50344","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-50344","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025091639-CVE-2022-50344-8893@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-50348","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2395851","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-50348","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-50348","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025091640-CVE-2022-50348-534c@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-50350","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2395874","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-50350","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-50350","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025091640-CVE-2022-50350-31bb@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-50363","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2396129","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-50363","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-50363","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025091715-CVE-2022-50363-7e9b@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-50381","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2396420","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-50381","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-50381","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025091851-CVE-2022-50381-b83f@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-50385","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2396432","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-50385","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-50385","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025091852-CVE-2022-50385-7787@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-50388","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2396411","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-50388","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-50388","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025091852-CVE-2022-50388-02a2@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-50392","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2396392","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-50392","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-50392","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025091853-CVE-2022-50392-967e@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-50396","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2396378","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-50396","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-50396","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025091854-CVE-2022-50396-8b1b@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-50402","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2396522","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-50402","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-50402","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025091852-CVE-2022-50402-4c96@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-50403","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2396494","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-50403","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-50403","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025091852-CVE-2022-50403-0471@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-50405","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2396526","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-50405","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-50405","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025091852-CVE-2022-50405-8450@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-50408","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2396506","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-50408","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-50408","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025091853-CVE-2022-50408-5835@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-50410","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2396536","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-50410","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-50410","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025091853-CVE-2022-50410-edee@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-50418","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2396520","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-50418","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-50418","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025091855-CVE-2022-50418-deac@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-50425","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2400803","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-50425","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-50425","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025100156-CVE-2022-50425-6722@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-50427","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2400751","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-50427","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-50427","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025100157-CVE-2022-50427-87b9@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-50431","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2400812","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-50431","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-50431","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025100158-CVE-2022-50431-b165@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-50436","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2400725","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-50436","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-50436","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025100159-CVE-2022-50436-ad37@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-50439","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2400726","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-50439","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-50439","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025100100-CVE-2022-50439-6054@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-50445","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2400763","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-50445","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-50445","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025100115-CVE-2022-50445-5873@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-50452","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2400781","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-50452","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-50452","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025100117-CVE-2022-50452-055d@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-50459","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2400713","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-50459","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-50459","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025100119-CVE-2022-50459-2340@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-50465","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2400704","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-50465","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-50465","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025100121-CVE-2022-50465-fb12@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-50467","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2400723","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-50467","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-50467","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025100122-CVE-2022-50467-13ec@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-50484","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2401488","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-50484","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-50484","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025100440-CVE-2022-50484-1a6a@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-50487","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2401498","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-50487","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-50487","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025100441-CVE-2022-50487-f5ea@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-50496","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2401534","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-50496","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-50496","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025100419-CVE-2022-50496-6e44@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-50506","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2401575","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-50506","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-50506","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025100422-CVE-2022-50506-1642@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-50512","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2402229","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-50512","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-50512","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025100701-CVE-2022-50512-f95b@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-50516","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2402307","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-50516","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-50516","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025100703-CVE-2022-50516-3b07@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-50530","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2402291","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-50530","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-50530","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025100707-CVE-2022-50530-ef6b@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-50531","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2402274","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-50531","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-50531","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025100707-CVE-2022-50531-a29b@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-50534","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2402282","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-50534","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-50534","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025100708-CVE-2022-50534-8900@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-50546","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2402240","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-50546","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-50546","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025100757-CVE-2022-50546-ef71@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-50549","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2402251","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-50549","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-50549","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025100758-CVE-2022-50549-cb07@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-50554","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2402306","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-50554","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-50554","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025100700-CVE-2022-50554-f4fb@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-50555","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2402227","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-50555","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-50555","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025100700-CVE-2022-50555-18e1@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-50563","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2405757","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-50563","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-50563","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025102207-CVE-2022-50563-995f@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-50569","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2405765","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-50569","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-50569","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025102207-CVE-2022-50569-fdd1@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-50580","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2405744","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-50580","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-50580","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025102209-CVE-2022-50580-68e3@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-50583","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2419864","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-50583","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-50583","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025120822-CVE-2022-50583-a25a@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-50615","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2419866","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-50615","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-50615","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025120851-CVE-2022-50615-5c90@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-50622","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2419941","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-50622","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-50622","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025120852-CVE-2022-50622-9f34@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-50635","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2420274","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-50635","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-50635","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025120935-CVE-2022-50635-b2b8@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-50668","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2420350","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-50668","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-50668","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025120945-CVE-2022-50668-153a@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-50678","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2420341","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-50678","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-50678","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025120949-CVE-2022-50678-53a4@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-50679","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2420330","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-50679","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-50679","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025120949-CVE-2022-50679-b2b8@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-50698","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2424979","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-50698","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-50698","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025122417-CVE-2022-50698-0d67@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-50702","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2424985","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-50702","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-50702","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025122418-CVE-2022-50702-c339@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-50703","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2424949","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-50703","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-50703","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025122419-CVE-2022-50703-1c22@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-50714","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2425004","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-50714","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-50714","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025122415-CVE-2022-50714-32b3@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-50715","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2425055","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-50715","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-50715","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025122415-CVE-2022-50715-5640@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-50717","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2425070","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-50717","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-50717","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025122416-CVE-2022-50717-dc68@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-50723","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2425009","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-50723","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-50723","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025122417-CVE-2022-50723-a62d@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-50726","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2425054","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-50726","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-50726","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025122418-CVE-2022-50726-2f42@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-50730","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2425043","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-50730","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-50730","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025122420-CVE-2022-50730-a4ca@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-50738","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2425101","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-50738","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-50738","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025122447-CVE-2022-50738-d561@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-50744","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2425198","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-50744","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-50744","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025122449-CVE-2022-50744-bc80@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-50752","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2425203","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-50752","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-50752","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025122452-CVE-2022-50752-fa82@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-50768","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2425080","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-50768","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-50768","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025122457-CVE-2022-50768-2703@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-50773","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2425174","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-50773","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-50773","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025122459-CVE-2022-50773-b946@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-50778","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2425136","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-50778","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-50778","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025122400-CVE-2022-50778-0b9a@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-50783","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2425114","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-50783","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-50783","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025122402-CVE-2022-50783-3109@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-50816","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2426225","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-50816","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-50816","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025123014-CVE-2022-50816-3fda@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-50833","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2426258","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-50833","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-50833","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025123017-CVE-2022-50833-92af@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-50835","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2426077","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-50835","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-50835","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025123017-CVE-2022-50835-a5ba@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-50839","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2426156","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-50839","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-50839","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025123019-CVE-2022-50839-eca8@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-50843","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2426213","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-50843","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-50843","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025123020-CVE-2022-50843-ae87@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-50855","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2426188","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-50855","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-50855","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025123046-CVE-2022-50855-7845@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-50861","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2426034","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-50861","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-50861","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025123048-CVE-2022-50861-0a1c@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-50863","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2426100","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-50863","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-50863","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025123048-CVE-2022-50863-7f8b@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-50866","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2426212","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-50866","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-50866","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025123049-CVE-2022-50866-6082@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-50889","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2426118","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-50889","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-50889","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025123015-CVE-2022-50889-71c4@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-0394","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-0394","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-0394","tags":["advisory"]},{"url":"https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=cb3e9864cdbe35ff6378966660edbcbac955fe17","tags":["article"]},{"url":"https://www.openwall.com/lists/oss-security/2023/01/18/2","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-0461","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-0461","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-0461","tags":["advisory"]},{"url":"https://github.com/torvalds/linux/commit/2c02d41d71f90a5168391b6a5f2954112ba2307c","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-0590","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-0590","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-0590","tags":["advisory"]},{"url":"https://lore.kernel.org/all/20221018203258.2793282-1-edumazet@google.com/","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-1195","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-1195","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-1195","tags":["advisory"]},{"url":"https://github.com/torvalds/linux/commit/153695d36ead0ccc4d0256953c751cabf673e621","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-1382","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-1382","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-1382","tags":["advisory"]},{"url":"https://lore.kernel.org/netdev/bc7bd3183f1c275c820690fc65b708238fe9e38e.1668807842.git.lucien.xin@gmail.com/T/#u","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-2177","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2187953","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-2177","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-2177","tags":["advisory"]},{"url":"https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net.git/commit/?id=181d8d2066c0","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-2513","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2193097","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-2513","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-2513","tags":["advisory"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-22998","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2182429","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-22998","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-22998","tags":["advisory"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-52340","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2257979","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-52340","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-52340","tags":["advisory"]},{"url":"https://alas.aws.amazon.com/cve/html/CVE-2023-52340.html","tags":["article"]},{"url":"https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit?id=af6d10345ca76670c1b7c37799f0d5576ccef277","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-52905","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2306433","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-52905","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-52905","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024082113-CVE-2023-52905-53fd@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-53020","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2355434","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-53020","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-53020","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025032717-CVE-2023-53020-1042@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-53021","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2355484","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-53021","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-53021","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025032718-CVE-2023-53021-def9@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-53029","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2355436","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-53029","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-53029","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025032720-CVE-2023-53029-a670@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-53030","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2355471","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-53030","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-53030","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025032720-CVE-2023-53030-ba50@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-53033","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2355437","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-53033","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-53033","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025032721-CVE-2023-53033-9089@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-53064","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2363754","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-53064","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-53064","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025050211-CVE-2023-53064-fe53@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-53083","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2363709","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-53083","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-53083","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025050217-CVE-2023-53083-5b4e@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-53273","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2395699","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-53273","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-53273","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025091622-CVE-2023-53273-b873@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-53381","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2396406","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-53381","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-53381","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025091856-CVE-2023-53381-a774@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-53393","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2396376","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-53393","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-53393","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025091858-CVE-2023-53393-5e45@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-53552","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2401514","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-53552","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-53552","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025100447-CVE-2023-53552-5ba9@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-53606","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2401548","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-53606","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-53606","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025100432-CVE-2023-53606-8c1a@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-53634","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2402271","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-53634","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-53634","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025100714-CVE-2023-53634-8155@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-53765","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2419938","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-53765","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-53765","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025120845-CVE-2023-53765-0317@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-53809","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2420256","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-53809","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-53809","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025120944-CVE-2023-53809-ca78@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-53811","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2420237","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-53811","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-53811","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025120944-CVE-2023-53811-dc26@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2025-21867","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2355334","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2025-21867","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-21867","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025032732-CVE-2025-21867-3138@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2025-38393","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2383408","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2025-38393","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-38393","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025072508-CVE-2025-38393-f2e8@gregkh/T","tags":["article"]},{"url":"https://www.suse.com/support/update/announcement/2025/suse-su-202502264-1/","tags":["advisory"]},{"url":"https://bugzilla.suse.com/1065729","tags":["report"]},{"url":"https://bugzilla.suse.com/1156395","tags":["report"]},{"url":"https://bugzilla.suse.com/1193629","tags":["report"]},{"url":"https://bugzilla.suse.com/1194869","tags":["report"]},{"url":"https://bugzilla.suse.com/1198410","tags":["report"]},{"url":"https://bugzilla.suse.com/1199356","tags":["report"]},{"url":"https://bugzilla.suse.com/1199487","tags":["report"]},{"url":"https://bugzilla.suse.com/1201160","tags":["report"]},{"url":"https://bugzilla.suse.com/1201956","tags":["report"]},{"url":"https://bugzilla.suse.com/1202094","tags":["report"]},{"url":"https://bugzilla.suse.com/1202095","tags":["report"]},{"url":"https://bugzilla.suse.com/1202564","tags":["report"]},{"url":"https://bugzilla.suse.com/1202716","tags":["report"]},{"url":"https://bugzilla.suse.com/1202823","tags":["report"]},{"url":"https://bugzilla.suse.com/1202860","tags":["report"]},{"url":"https://bugzilla.suse.com/1203197","tags":["report"]},{"url":"https://bugzilla.suse.com/1203361","tags":["report"]},{"url":"https://bugzilla.suse.com/1205220","tags":["report"]},{"url":"https://bugzilla.suse.com/1205514","tags":["report"]},{"url":"https://bugzilla.suse.com/1205701","tags":["report"]},{"url":"https://bugzilla.suse.com/1206451","tags":["report"]},{"url":"https://bugzilla.suse.com/1206664","tags":["report"]},{"url":"https://bugzilla.suse.com/1206878","tags":["report"]},{"url":"https://bugzilla.suse.com/1206880","tags":["report"]},{"url":"https://bugzilla.suse.com/1207361","tags":["report"]},{"url":"https://bugzilla.suse.com/1207638","tags":["report"]},{"url":"https://bugzilla.suse.com/1211226","tags":["report"]},{"url":"https://bugzilla.suse.com/1212051","tags":["report"]},{"url":"https://bugzilla.suse.com/1213090","tags":["report"]},{"url":"https://bugzilla.suse.com/1218184","tags":["report"]},{"url":"https://bugzilla.suse.com/1218234","tags":["report"]},{"url":"https://bugzilla.suse.com/1218470","tags":["report"]},{"url":"https://bugzilla.suse.com/1222634","tags":["report"]},{"url":"https://bugzilla.suse.com/1223675","tags":["report"]},{"url":"https://bugzilla.suse.com/1224095","tags":["report"]},{"url":"https://bugzilla.suse.com/1224597","tags":["report"]},{"url":"https://bugzilla.suse.com/1225468","tags":["report"]},{"url":"https://bugzilla.suse.com/1225820","tags":["report"]},{"url":"https://bugzilla.suse.com/1226514","tags":["report"]},{"url":"https://bugzilla.suse.com/1226552","tags":["report"]},{"url":"https://bugzilla.suse.com/1230827","tags":["report"]},{"url":"https://bugzilla.suse.com/1232504","tags":["report"]},{"url":"https://bugzilla.suse.com/1234156","tags":["report"]},{"url":"https://bugzilla.suse.com/1234381","tags":["report"]},{"url":"https://bugzilla.suse.com/1235464","tags":["report"]},{"url":"https://bugzilla.suse.com/1235637","tags":["report"]},{"url":"https://bugzilla.suse.com/1236821","tags":["report"]},{"url":"https://bugzilla.suse.com/1236822","tags":["report"]},{"url":"https://bugzilla.suse.com/1237159","tags":["report"]},{"url":"https://bugzilla.suse.com/1237312","tags":["report"]},{"url":"https://bugzilla.suse.com/1237313","tags":["report"]},{"url":"https://bugzilla.suse.com/1238526","tags":["report"]},{"url":"https://bugzilla.suse.com/1238876","tags":["report"]},{"url":"https://bugzilla.suse.com/1241900","tags":["report"]},{"url":"https://bugzilla.suse.com/1242221","tags":["report"]},{"url":"https://bugzilla.suse.com/1242414","tags":["report"]},{"url":"https://bugzilla.suse.com/1242504","tags":["report"]},{"url":"https://bugzilla.suse.com/1242596","tags":["report"]},{"url":"https://bugzilla.suse.com/1242778","tags":["report"]},{"url":"https://bugzilla.suse.com/1242782","tags":["report"]},{"url":"https://bugzilla.suse.com/1242924","tags":["report"]},{"url":"https://bugzilla.suse.com/1243330","tags":["report"]},{"url":"https://bugzilla.suse.com/1243543","tags":["report"]},{"url":"https://bugzilla.suse.com/1243627","tags":["report"]},{"url":"https://bugzilla.suse.com/1243649","tags":["report"]},{"url":"https://bugzilla.suse.com/1243660","tags":["report"]},{"url":"https://bugzilla.suse.com/1243832","tags":["report"]},{"url":"https://bugzilla.suse.com/1244114","tags":["report"]},{"url":"https://bugzilla.suse.com/1244179","tags":["report"]},{"url":"https://bugzilla.suse.com/1244180","tags":["report"]},{"url":"https://bugzilla.suse.com/1244234","tags":["report"]},{"url":"https://bugzilla.suse.com/1244241","tags":["report"]},{"url":"https://bugzilla.suse.com/1244277","tags":["report"]},{"url":"https://bugzilla.suse.com/1244309","tags":["report"]},{"url":"https://bugzilla.suse.com/1244337","tags":["report"]},{"url":"https://bugzilla.suse.com/1244732","tags":["report"]},{"url":"https://bugzilla.suse.com/1244764","tags":["report"]},{"url":"https://bugzilla.suse.com/1244765","tags":["report"]},{"url":"https://bugzilla.suse.com/1244767","tags":["report"]},{"url":"https://bugzilla.suse.com/1244770","tags":["report"]},{"url":"https://bugzilla.suse.com/1244771","tags":["report"]},{"url":"https://bugzilla.suse.com/1244772","tags":["report"]},{"url":"https://bugzilla.suse.com/1244773","tags":["report"]},{"url":"https://bugzilla.suse.com/1244774","tags":["report"]},{"url":"https://bugzilla.suse.com/1244776","tags":["report"]},{"url":"https://bugzilla.suse.com/1244779","tags":["report"]},{"url":"https://bugzilla.suse.com/1244780","tags":["report"]},{"url":"https://bugzilla.suse.com/1244781","tags":["report"]},{"url":"https://bugzilla.suse.com/1244782","tags":["report"]},{"url":"https://bugzilla.suse.com/1244783","tags":["report"]},{"url":"https://bugzilla.suse.com/1244784","tags":["report"]},{"url":"https://bugzilla.suse.com/1244786","tags":["report"]},{"url":"https://bugzilla.suse.com/1244787","tags":["report"]},{"url":"https://bugzilla.suse.com/1244788","tags":["report"]},{"url":"https://bugzilla.suse.com/1244790","tags":["report"]},{"url":"https://bugzilla.suse.com/1244791","tags":["report"]},{"url":"https://bugzilla.suse.com/1244793","tags":["report"]},{"url":"https://bugzilla.suse.com/1244794","tags":["report"]},{"url":"https://bugzilla.suse.com/1244796","tags":["report"]},{"url":"https://bugzilla.suse.com/1244797","tags":["report"]},{"url":"https://bugzilla.suse.com/1244798","tags":["report"]},{"url":"https://bugzilla.suse.com/1244800","tags":["report"]},{"url":"https://bugzilla.suse.com/1244802","tags":["report"]},{"url":"https://bugzilla.suse.com/1244804","tags":["report"]},{"url":"https://bugzilla.suse.com/1244805","tags":["report"]},{"url":"https://bugzilla.suse.com/1244806","tags":["report"]},{"url":"https://bugzilla.suse.com/1244807","tags":["report"]},{"url":"https://bugzilla.suse.com/1244808","tags":["report"]},{"url":"https://bugzilla.suse.com/1244811","tags":["report"]},{"url":"https://bugzilla.suse.com/1244813","tags":["report"]},{"url":"https://bugzilla.suse.com/1244814","tags":["report"]},{"url":"https://bugzilla.suse.com/1244815","tags":["report"]},{"url":"https://bugzilla.suse.com/1244816","tags":["report"]},{"url":"https://bugzilla.suse.com/1244819","tags":["report"]},{"url":"https://bugzilla.suse.com/1244820","tags":["report"]},{"url":"https://bugzilla.suse.com/1244823","tags":["report"]},{"url":"https://bugzilla.suse.com/1244824","tags":["report"]},{"url":"https://bugzilla.suse.com/1244825","tags":["report"]},{"url":"https://bugzilla.suse.com/1244826","tags":["report"]},{"url":"https://bugzilla.suse.com/1244827","tags":["report"]},{"url":"https://bugzilla.suse.com/1244830","tags":["report"]},{"url":"https://bugzilla.suse.com/1244831","tags":["report"]},{"url":"https://bugzilla.suse.com/1244832","tags":["report"]},{"url":"https://bugzilla.suse.com/1244834","tags":["report"]},{"url":"https://bugzilla.suse.com/1244836","tags":["report"]},{"url":"https://bugzilla.suse.com/1244838","tags":["report"]},{"url":"https://bugzilla.suse.com/1244839","tags":["report"]},{"url":"https://bugzilla.suse.com/1244840","tags":["report"]},{"url":"https://bugzilla.suse.com/1244841","tags":["report"]},{"url":"https://bugzilla.suse.com/1244842","tags":["report"]},{"url":"https://bugzilla.suse.com/1244843","tags":["report"]},{"url":"https://bugzilla.suse.com/1244845","tags":["report"]},{"url":"https://bugzilla.suse.com/1244846","tags":["report"]},{"url":"https://bugzilla.suse.com/1244848","tags":["report"]},{"url":"https://bugzilla.suse.com/1244849","tags":["report"]},{"url":"https://bugzilla.suse.com/1244851","tags":["report"]},{"url":"https://bugzilla.suse.com/1244853","tags":["report"]},{"url":"https://bugzilla.suse.com/1244854","tags":["report"]},{"url":"https://bugzilla.suse.com/1244856","tags":["report"]},{"url":"https://bugzilla.suse.com/1244858","tags":["report"]},{"url":"https://bugzilla.suse.com/1244860","tags":["report"]},{"url":"https://bugzilla.suse.com/1244861","tags":["report"]},{"url":"https://bugzilla.suse.com/1244866","tags":["report"]},{"url":"https://bugzilla.suse.com/1244867","tags":["report"]},{"url":"https://bugzilla.suse.com/1244868","tags":["report"]},{"url":"https://bugzilla.suse.com/1244869","tags":["report"]},{"url":"https://bugzilla.suse.com/1244870","tags":["report"]},{"url":"https://bugzilla.suse.com/1244871","tags":["report"]},{"url":"https://bugzilla.suse.com/1244872","tags":["report"]},{"url":"https://bugzilla.suse.com/1244873","tags":["report"]},{"url":"https://bugzilla.suse.com/1244875","tags":["report"]},{"url":"https://bugzilla.suse.com/1244876","tags":["report"]},{"url":"https://bugzilla.suse.com/1244878","tags":["report"]},{"url":"https://bugzilla.suse.com/1244879","tags":["report"]},{"url":"https://bugzilla.suse.com/1244881","tags":["report"]},{"url":"https://bugzilla.suse.com/1244883","tags":["report"]},{"url":"https://bugzilla.suse.com/1244884","tags":["report"]},{"url":"https://bugzilla.suse.com/1244886","tags":["report"]},{"url":"https://bugzilla.suse.com/1244887","tags":["report"]},{"url":"https://bugzilla.suse.com/1244888","tags":["report"]},{"url":"https://bugzilla.suse.com/1244890","tags":["report"]},{"url":"https://bugzilla.suse.com/1244892","tags":["report"]},{"url":"https://bugzilla.suse.com/1244893","tags":["report"]},{"url":"https://bugzilla.suse.com/1244895","tags":["report"]},{"url":"https://bugzilla.suse.com/1244898","tags":["report"]},{"url":"https://bugzilla.suse.com/1244899","tags":["report"]},{"url":"https://bugzilla.suse.com/1244900","tags":["report"]},{"url":"https://bugzilla.suse.com/1244901","tags":["report"]},{"url":"https://bugzilla.suse.com/1244902","tags":["report"]},{"url":"https://bugzilla.suse.com/1244903","tags":["report"]},{"url":"https://bugzilla.suse.com/1244904","tags":["report"]},{"url":"https://bugzilla.suse.com/1244905","tags":["report"]},{"url":"https://bugzilla.suse.com/1244908","tags":["report"]},{"url":"https://bugzilla.suse.com/1244911","tags":["report"]},{"url":"https://bugzilla.suse.com/1244912","tags":["report"]},{"url":"https://bugzilla.suse.com/1244914","tags":["report"]},{"url":"https://bugzilla.suse.com/1244915","tags":["report"]},{"url":"https://bugzilla.suse.com/1244928","tags":["report"]},{"url":"https://bugzilla.suse.com/1244936","tags":["report"]},{"url":"https://bugzilla.suse.com/1244940","tags":["report"]},{"url":"https://bugzilla.suse.com/1244941","tags":["report"]},{"url":"https://bugzilla.suse.com/1244942","tags":["report"]},{"url":"https://bugzilla.suse.com/1244943","tags":["report"]},{"url":"https://bugzilla.suse.com/1244944","tags":["report"]},{"url":"https://bugzilla.suse.com/1244945","tags":["report"]},{"url":"https://bugzilla.suse.com/1244948","tags":["report"]},{"url":"https://bugzilla.suse.com/1244949","tags":["report"]},{"url":"https://bugzilla.suse.com/1244950","tags":["report"]},{"url":"https://bugzilla.suse.com/1244953","tags":["report"]},{"url":"https://bugzilla.suse.com/1244955","tags":["report"]},{"url":"https://bugzilla.suse.com/1244956","tags":["report"]},{"url":"https://bugzilla.suse.com/1244957","tags":["report"]},{"url":"https://bugzilla.suse.com/1244958","tags":["report"]},{"url":"https://bugzilla.suse.com/1244959","tags":["report"]},{"url":"https://bugzilla.suse.com/1244960","tags":["report"]},{"url":"https://bugzilla.suse.com/1244961","tags":["report"]},{"url":"https://bugzilla.suse.com/1244965","tags":["report"]},{"url":"https://bugzilla.suse.com/1244966","tags":["report"]},{"url":"https://bugzilla.suse.com/1244967","tags":["report"]},{"url":"https://bugzilla.suse.com/1244968","tags":["report"]},{"url":"https://bugzilla.suse.com/1244969","tags":["report"]},{"url":"https://bugzilla.suse.com/1244970","tags":["report"]},{"url":"https://bugzilla.suse.com/1244973","tags":["report"]},{"url":"https://bugzilla.suse.com/1244974","tags":["report"]},{"url":"https://bugzilla.suse.com/1244976","tags":["report"]},{"url":"https://bugzilla.suse.com/1244977","tags":["report"]},{"url":"https://bugzilla.suse.com/1244978","tags":["report"]},{"url":"https://bugzilla.suse.com/1244979","tags":["report"]},{"url":"https://bugzilla.suse.com/1244983","tags":["report"]},{"url":"https://bugzilla.suse.com/1244984","tags":["report"]},{"url":"https://bugzilla.suse.com/1244985","tags":["report"]},{"url":"https://bugzilla.suse.com/1244986","tags":["report"]},{"url":"https://bugzilla.suse.com/1244987","tags":["report"]},{"url":"https://bugzilla.suse.com/1244991","tags":["report"]},{"url":"https://bugzilla.suse.com/1244992","tags":["report"]},{"url":"https://bugzilla.suse.com/1244993","tags":["report"]},{"url":"https://bugzilla.suse.com/1245006","tags":["report"]},{"url":"https://bugzilla.suse.com/1245007","tags":["report"]},{"url":"https://bugzilla.suse.com/1245009","tags":["report"]},{"url":"https://bugzilla.suse.com/1245011","tags":["report"]},{"url":"https://bugzilla.suse.com/1245012","tags":["report"]},{"url":"https://bugzilla.suse.com/1245015","tags":["report"]},{"url":"https://bugzilla.suse.com/1245018","tags":["report"]},{"url":"https://bugzilla.suse.com/1245019","tags":["report"]},{"url":"https://bugzilla.suse.com/1245023","tags":["report"]},{"url":"https://bugzilla.suse.com/1245024","tags":["report"]},{"url":"https://bugzilla.suse.com/1245028","tags":["report"]},{"url":"https://bugzilla.suse.com/1245031","tags":["report"]},{"url":"https://bugzilla.suse.com/1245032","tags":["report"]},{"url":"https://bugzilla.suse.com/1245033","tags":["report"]},{"url":"https://bugzilla.suse.com/1245038","tags":["report"]},{"url":"https://bugzilla.suse.com/1245039","tags":["report"]},{"url":"https://bugzilla.suse.com/1245040","tags":["report"]},{"url":"https://bugzilla.suse.com/1245041","tags":["report"]},{"url":"https://bugzilla.suse.com/1245047","tags":["report"]},{"url":"https://bugzilla.suse.com/1245048","tags":["report"]},{"url":"https://bugzilla.suse.com/1245051","tags":["report"]},{"url":"https://bugzilla.suse.com/1245052","tags":["report"]},{"url":"https://bugzilla.suse.com/1245057","tags":["report"]},{"url":"https://bugzilla.suse.com/1245058","tags":["report"]},{"url":"https://bugzilla.suse.com/1245060","tags":["report"]},{"url":"https://bugzilla.suse.com/1245062","tags":["report"]},{"url":"https://bugzilla.suse.com/1245063","tags":["report"]},{"url":"https://bugzilla.suse.com/1245064","tags":["report"]},{"url":"https://bugzilla.suse.com/1245069","tags":["report"]},{"url":"https://bugzilla.suse.com/1245070","tags":["report"]},{"url":"https://bugzilla.suse.com/1245072","tags":["report"]},{"url":"https://bugzilla.suse.com/1245073","tags":["report"]},{"url":"https://bugzilla.suse.com/1245088","tags":["report"]},{"url":"https://bugzilla.suse.com/1245089","tags":["report"]},{"url":"https://bugzilla.suse.com/1245092","tags":["report"]},{"url":"https://bugzilla.suse.com/1245093","tags":["report"]},{"url":"https://bugzilla.suse.com/1245094","tags":["report"]},{"url":"https://bugzilla.suse.com/1245098","tags":["report"]},{"url":"https://bugzilla.suse.com/1245103","tags":["report"]},{"url":"https://bugzilla.suse.com/1245116","tags":["report"]},{"url":"https://bugzilla.suse.com/1245117","tags":["report"]},{"url":"https://bugzilla.suse.com/1245118","tags":["report"]},{"url":"https://bugzilla.suse.com/1245119","tags":["report"]},{"url":"https://bugzilla.suse.com/1245121","tags":["report"]},{"url":"https://bugzilla.suse.com/1245122","tags":["report"]},{"url":"https://bugzilla.suse.com/1245125","tags":["report"]},{"url":"https://bugzilla.suse.com/1245129","tags":["report"]},{"url":"https://bugzilla.suse.com/1245131","tags":["report"]},{"url":"https://bugzilla.suse.com/1245133","tags":["report"]},{"url":"https://bugzilla.suse.com/1245134","tags":["report"]},{"url":"https://bugzilla.suse.com/1245135","tags":["report"]},{"url":"https://bugzilla.suse.com/1245136","tags":["report"]},{"url":"https://bugzilla.suse.com/1245138","tags":["report"]},{"url":"https://bugzilla.suse.com/1245139","tags":["report"]},{"url":"https://bugzilla.suse.com/1245140","tags":["report"]},{"url":"https://bugzilla.suse.com/1245142","tags":["report"]},{"url":"https://bugzilla.suse.com/1245146","tags":["report"]},{"url":"https://bugzilla.suse.com/1245147","tags":["report"]},{"url":"https://bugzilla.suse.com/1245149","tags":["report"]},{"url":"https://bugzilla.suse.com/1245152","tags":["report"]},{"url":"https://bugzilla.suse.com/1245154","tags":["report"]},{"url":"https://bugzilla.suse.com/1245155","tags":["report"]},{"url":"https://bugzilla.suse.com/1245180","tags":["report"]},{"url":"https://bugzilla.suse.com/1245183","tags":["report"]},{"url":"https://bugzilla.suse.com/1245189","tags":["report"]},{"url":"https://bugzilla.suse.com/1245191","tags":["report"]},{"url":"https://bugzilla.suse.com/1245195","tags":["report"]},{"url":"https://bugzilla.suse.com/1245197","tags":["report"]},{"url":"https://bugzilla.suse.com/1245265","tags":["report"]},{"url":"https://bugzilla.suse.com/1245340","tags":["report"]},{"url":"https://bugzilla.suse.com/1245348","tags":["report"]},{"url":"https://bugzilla.suse.com/1245431","tags":["report"]},{"url":"https://bugzilla.suse.com/1245455","tags":["report"]},{"url":"https://www.suse.com/security/cve/CVE-2021-47557","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-47595","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-1679","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-2585","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-2586","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-2905","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-3903","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-4095","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-4662","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-49934","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-49935","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-49936","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-49937","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-49938","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-49940","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-49942","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-49943","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-49944","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-49945","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-49946","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-49948","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-49949","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-49950","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-49951","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-49952","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-49954","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-49956","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-49957","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-49958","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-49960","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-49962","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-49963","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-49964","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-49965","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-49966","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-49968","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-49969","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-49971","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-49972","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-49977","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-49978","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-49980","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-49981","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-49982","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-49983","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-49984","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-49985","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-49986","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-49987","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-49989","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-49990","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-49993","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-49995","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-49999","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-50002","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-50003","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-50005","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-50006","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-50008","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-50010","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-50011","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-50012","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-50015","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-50016","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-50019","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-50020","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-50021","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-50022","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-50023","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-50024","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-50026","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-50027","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-50028","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-50029","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-50030","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-50031","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-50032","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-50033","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-50034","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-50035","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-50036","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-50037","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-50038","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-50039","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-50040","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-50041","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-50044","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-50045","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-50046","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-50047","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-50049","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-50050","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-50051","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-50052","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-50053","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-50054","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-50055","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-50059","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-50060","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-50061","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-50062","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-50065","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-50066","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-50067","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-50068","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-50072","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-50073","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-50074","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-50076","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-50077","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-50079","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-50083","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-50084","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-50085","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-50086","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-50087","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-50092","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-50093","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-50094","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-50095","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-50097","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-50098","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-50099","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-50100","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-50101","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-50102","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-50103","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-50104","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-50108","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-50109","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-50110","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-50111","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-50112","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-50115","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-50116","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-50117","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-50118","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-50120","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-50121","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-50124","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-50125","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-50126","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-50127","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-50129","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-50131","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-50132","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-50133","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-50134","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-50135","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-50136","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-50137","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-50138","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-50139","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-50140","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-50141","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-50142","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-50143","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-50144","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-50145","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-50146","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-50149","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-50151","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-50152","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-50153","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-50154","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-50155","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-50156","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-50157","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-50158","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-50160","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-50161","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-50162","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-50164","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-50165","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-50166","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-50169","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-50171","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-50172","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-50173","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-50175","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-50176","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-50178","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-50179","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-50181","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-50183","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-50184","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-50185","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-50186","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-50187","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-50188","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-50190","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-50191","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-50192","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-50194","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-50196","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-50197","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-50198","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-50199","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-50200","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-50201","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-50202","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-50203","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-50204","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-50206","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-50207","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-50208","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-50209","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-50211","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-50212","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-50213","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-50215","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-50218","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-50220","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-50221","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-50222","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-50226","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-50228","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-50229","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-50231","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-3111","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-52924","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-52925","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-53046","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-53048","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-53076","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-53097","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-26808","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-26924","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-26935","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-27397","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-35840","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-36978","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-46800","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-53125","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-53141","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-53197","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-56770","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-57999","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-21700","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-21702","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-21703","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-21756","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-23141","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-23145","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-37752","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-37798","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-37823","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-37890","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-37932","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-37948","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-37953","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-37963","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-37997","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38000","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38001","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38014","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38060","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38083","tags":["web"]},{"url":"https://www.suse.com/support/update/announcement/2025/suse-su-202502321-1/","tags":["advisory"]},{"url":"https://bugzilla.suse.com/1228659","tags":["report"]},{"url":"https://bugzilla.suse.com/1231293","tags":["report"]},{"url":"https://bugzilla.suse.com/1234454","tags":["report"]},{"url":"https://bugzilla.suse.com/1238303","tags":["report"]},{"url":"https://bugzilla.suse.com/1238570","tags":["report"]},{"url":"https://bugzilla.suse.com/1239986","tags":["report"]},{"url":"https://bugzilla.suse.com/1240785","tags":["report"]},{"url":"https://bugzilla.suse.com/1241038","tags":["report"]},{"url":"https://bugzilla.suse.com/1241640","tags":["report"]},{"url":"https://bugzilla.suse.com/1242006","tags":["report"]},{"url":"https://www.suse.com/security/cve/CVE-2024-28956","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-37785","tags":["web"]},{"url":"https://www.suse.com/support/update/announcement/2025/suse-su-202502322-1/","tags":["advisory"]},{"url":"https://bugzilla.suse.com/1233551","tags":["report"]},{"url":"https://bugzilla.suse.com/1236333","tags":["report"]},{"url":"https://bugzilla.suse.com/1242417","tags":["report"]},{"url":"https://bugzilla.suse.com/1243001","tags":["report"]},{"url":"https://www.suse.com/security/cve/CVE-2024-53057","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-57947","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-37797","tags":["web"]},{"url":"https://www.suse.com/support/update/announcement/2025/suse-su-202502537-1/","tags":["advisory"]},{"url":"https://www.suse.com/support/update/announcement/2025/suse-su-20252264-1/","tags":["advisory"]},{"url":"https://ubuntu.com/security/CVE-2022-50151","tags":["report"]}],"sources":{"cve":[{"id":"CVE-2022-50151","title":"usb: cdns3: fix random warning message when driver load","description":"In the Linux kernel, the following vulnerability has been resolved:\n\nusb: cdns3: fix random warning message when driver load\n\nWarning log:\n[    4.141392] Unexpected gfp: 0x4 (GFP_DMA32). Fixing up to gfp: 0xa20 (GFP_ATOMIC). Fix your code!\n[    4.150340] CPU: 1 PID: 175 Comm: 1-0050 Not tainted 5.15.5-00039-g2fd9ae1b568c #20\n[    4.158010] Hardware name: Freescale i.MX8QXP MEK (DT)\n[    4.163155] Call trace:\n[    4.165600]  dump_backtrace+0x0/0x1b0\n[    4.169286]  show_stack+0x18/0x68\n[    4.172611]  dump_stack_lvl+0x68/0x84\n[    4.176286]  dump_stack+0x18/0x34\n[    4.179613]  kmalloc_fix_flags+0x60/0x88\n[    4.183550]  new_slab+0x334/0x370\n[    4.186878]  ___slab_alloc.part.108+0x4d4/0x748\n[    4.191419]  __slab_alloc.isra.109+0x30/0x78\n[    4.195702]  kmem_cache_alloc+0x40c/0x420\n[    4.199725]  dma_pool_alloc+0xac/0x1f8\n[    4.203486]  cdns3_allocate_trb_pool+0xb4/0xd0\n\npool_alloc_page(struct dma_pool *pool, gfp_t mem_flags)\n{\n\t...\n\tpage = kmalloc(sizeof(*page), mem_flags);\n\tpage-\u003evaddr = dma_alloc_coherent(pool-\u003edev, pool-\u003eallocation,\n\t\t\t\t\t \u0026page-\u003edma, mem_flags);\n\t...\n}\n\nkmalloc was called with mem_flags, which is passed down in\ncdns3_allocate_trb_pool() and have GFP_DMA32 flags.\nkmall_fix_flags() report warning.\n\nGFP_DMA32 is not useful at all. dma_alloc_coherent() will handle\nDMA memory region correctly by pool-\u003edev. GFP_DMA32 can be removed\nsafely.","status":"published","published":"2025-06-18T11:03:10.569Z","modified":"2026-08-15T12:23:11.047Z","updated_at":"2026-11-02T14:34:41.34666Z"}],"euvd":[{"id":"EUVD-2022-55416","description":"In the Linux kernel, the following vulnerability has been resolved:\n\nusb: cdns3: fix random warning message when driver load\n\nWarning log:\n[    4.141392] Unexpected gfp: 0x4 (GFP_DMA32). Fixing up to gfp: 0xa20 (GFP_ATOMIC). Fix your code!\n[    4.150340] CPU: 1 PID: 175 Comm: 1-0050 Not tainted 5.15.5-00039-g2fd9ae1b568c #20\n[    4.158010] Hardware name: Freescale i.MX8QXP MEK (DT)\n[    4.163155] Call trace:\n[    4.165600]  dump_backtrace+0x0/0x1b0\n[    4.169286]  show_stack+0x18/0x68\n[    4.172611]  dump_stack_lvl+0x68/0x84\n[    4.176286]  dump_stack+0x18/0x34\n[    4.179613]  kmalloc_fix_flags+0x60/0x88\n[    4.183550]  new_slab+0x334/0x370\n[    4.186878]  ___slab_alloc.part.108+0x4d4/0x748\n[    4.191419]  __slab_alloc.isra.109+0x30/0x78\n[    4.195702]  kmem_cache_alloc+0x40c/0x420\n[    4.199725]  dma_pool_alloc+0xac/0x1f8\n[    4.203486]  cdns3_allocate_trb_pool+0xb4/0xd0\n\npool_alloc_page(struct dma_pool *pool, gfp_t mem_flags)\n{\n\t...\n\tpage = kmalloc(sizeof(*page), mem_flags);\n\tpage-\u003evaddr = dma_alloc_coherent(pool-\u003edev, pool-\u003eallocation,\n\t\t\t\t\t \u0026page-\u003edma, mem_flags);\n\t...\n}\n\nkmalloc was called with mem_flags, which is passed down in\ncdns3_allocate_trb_pool() and have GFP_DMA32 flags.\nkmall_fix_flags() report warning.\n\nGFP_DMA32 is not useful at all. dma_alloc_coherent() will handle\nDMA memory region correctly by pool-\u003edev. GFP_DMA32 can be removed\nsafely.","status":"published","published":"2025-06-18T11:03:10Z","modified":"2026-08-15T12:23:11Z","updated_at":"2026-11-02T18:01:53.008072Z"}],"ghsa":[{"id":"GHSA-gvgm-6pph-fj6g","title":"In the Linux kernel, the following vulnerability has been resolved:\n\nusb: cdns3: fix random...","description":"In the Linux kernel, the following vulnerability has been resolved:\n\nusb: cdns3: fix random warning message when driver load\n\nWarning log:\n[    4.141392] Unexpected gfp: 0x4 (GFP_DMA32). Fixing up to gfp: 0xa20 (GFP_ATOMIC). Fix your code!\n[    4.150340] CPU: 1 PID: 175 Comm: 1-0050 Not tainted 5.15.5-00039-g2fd9ae1b568c #20\n[    4.158010] Hardware name: Freescale i.MX8QXP MEK (DT)\n[    4.163155] Call trace:\n[    4.165600]  dump_backtrace+0x0/0x1b0\n[    4.169286]  show_stack+0x18/0x68\n[    4.172611]  dump_stack_lvl+0x68/0x84\n[    4.176286]  dump_stack+0x18/0x34\n[    4.179613]  kmalloc_fix_flags+0x60/0x88\n[    4.183550]  new_slab+0x334/0x370\n[    4.186878]  ___slab_alloc.part.108+0x4d4/0x748\n[    4.191419]  __slab_alloc.isra.109+0x30/0x78\n[    4.195702]  kmem_cache_alloc+0x40c/0x420\n[    4.199725]  dma_pool_alloc+0xac/0x1f8\n[    4.203486]  cdns3_allocate_trb_pool+0xb4/0xd0\n\npool_alloc_page(struct dma_pool *pool, gfp_t mem_flags)\n{\n\t...\n\tpage = kmalloc(sizeof(*page), mem_flags);\n\tpage-\u003evaddr = dma_alloc_coherent(pool-\u003edev, pool-\u003eallocation,\n\t\t\t\t\t \u0026page-\u003edma, mem_flags);\n\t...\n}\n\nkmalloc was called with mem_flags, which is passed down in\ncdns3_allocate_trb_pool() and have GFP_DMA32 flags.\nkmall_fix_flags() report warning.\n\nGFP_DMA32 is not useful at all. dma_alloc_coherent() will handle\nDMA memory region correctly by pool-\u003edev. GFP_DMA32 can be removed\nsafely.","status":"published","published":"2025-06-18T12:30:50Z","modified":"2025-11-21T00:31:24Z","cvss":[{"version":"3.1","score":7.8,"vector":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H","level":"high"}],"updated_at":"2026-11-02T15:04:54.23412Z"}],"nvd":[{"id":"CVE-2022-50151","description":"In the Linux kernel, the following vulnerability has been resolved:\n\nusb: cdns3: fix random warning message when driver load\n\nWarning log:\n[    4.141392] Unexpected gfp: 0x4 (GFP_DMA32). Fixing up to gfp: 0xa20 (GFP_ATOMIC). Fix your code!\n[    4.150340] CPU: 1 PID: 175 Comm: 1-0050 Not tainted 5.15.5-00039-g2fd9ae1b568c #20\n[    4.158010] Hardware name: Freescale i.MX8QXP MEK (DT)\n[    4.163155] Call trace:\n[    4.165600]  dump_backtrace+0x0/0x1b0\n[    4.169286]  show_stack+0x18/0x68\n[    4.172611]  dump_stack_lvl+0x68/0x84\n[    4.176286]  dump_stack+0x18/0x34\n[    4.179613]  kmalloc_fix_flags+0x60/0x88\n[    4.183550]  new_slab+0x334/0x370\n[    4.186878]  ___slab_alloc.part.108+0x4d4/0x748\n[    4.191419]  __slab_alloc.isra.109+0x30/0x78\n[    4.195702]  kmem_cache_alloc+0x40c/0x420\n[    4.199725]  dma_pool_alloc+0xac/0x1f8\n[    4.203486]  cdns3_allocate_trb_pool+0xb4/0xd0\n\npool_alloc_page(struct dma_pool *pool, gfp_t mem_flags)\n{\n\t...\n\tpage = kmalloc(sizeof(*page), mem_flags);\n\tpage-\u003evaddr = dma_alloc_coherent(pool-\u003edev, pool-\u003eallocation,\n\t\t\t\t\t \u0026page-\u003edma, mem_flags);\n\t...\n}\n\nkmalloc was called with mem_flags, which is passed down in\ncdns3_allocate_trb_pool() and have GFP_DMA32 flags.\nkmall_fix_flags() report warning.\n\nGFP_DMA32 is not useful at all. dma_alloc_coherent() will handle\nDMA memory region correctly by pool-\u003edev. GFP_DMA32 can be removed\nsafely.","status":"published","published":"2025-06-18T11:15:45.19Z","modified":"2026-08-15T13:17:30.62Z","cvss":[{"version":"3.1","score":7.8,"vector":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H","level":"high","assessor":"primary"}],"updated_at":"2026-11-02T14:07:43.071398Z"}],"osv":[{"id":"DEBIAN-CVE-2022-50151","description":"In the Linux kernel, the following vulnerability has been resolved:  usb: cdns3: fix random warning message when driver load  Warning log: [    4.141392] Unexpected gfp: 0x4 (GFP_DMA32). Fixing up to gfp: 0xa20 (GFP_ATOMIC). Fix your code! [    4.150340] CPU: 1 PID: 175 Comm: 1-0050 Not tainted 5.15.5-00039-g2fd9ae1b568c #20 [    4.158010] Hardware name: Freescale i.MX8QXP MEK (DT) [    4.163155] Call trace: [    4.165600]  dump_backtrace+0x0/0x1b0 [    4.169286]  show_stack+0x18/0x68 [    4.172611]  dump_stack_lvl+0x68/0x84 [    4.176286]  dump_stack+0x18/0x34 [    4.179613]  kmalloc_fix_flags+0x60/0x88 [    4.183550]  new_slab+0x334/0x370 [    4.186878]  ___slab_alloc.part.108+0x4d4/0x748 [    4.191419]  __slab_alloc.isra.109+0x30/0x78 [    4.195702]  kmem_cache_alloc+0x40c/0x420 [    4.199725]  dma_pool_alloc+0xac/0x1f8 [    4.203486]  cdns3_allocate_trb_pool+0xb4/0xd0  pool_alloc_page(struct dma_pool *pool, gfp_t mem_flags) { \t... \tpage = kmalloc(sizeof(*page), mem_flags); \tpage-\u003evaddr = dma_alloc_coherent(pool-\u003edev, pool-\u003eallocation, \t\t\t\t\t \u0026page-\u003edma, mem_flags); \t... }  kmalloc was called with mem_flags, which is passed down in cdns3_allocate_trb_pool() and have GFP_DMA32 flags. kmall_fix_flags() report warning.  GFP_DMA32 is not useful at all. dma_alloc_coherent() will handle DMA memory region correctly by pool-\u003edev. GFP_DMA32 can be removed safely.","status":"published","published":"2025-06-18T11:15:45.19Z","modified":"2026-11-03T08:03:38.934837671Z","cvss":[{"version":"3.1","score":7.8,"vector":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H","level":"high"}],"updated_at":"2026-11-03T08:24:24.826312Z"},{"id":"OESA-2026-1341","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:kernel/resource: fix kfree() of bootmem memory againSince commit ebff7d8f270d ( mem hotunplug: fix kfree() of bootmemmemory ), we could get a resource allocated during boot viaalloc_resource().  And it s required to release the resource usingfree_resource().  Howerver, many people use kfree directly which willresult in kernel BUG.  In order to fix this without fixing every callsite, just leak a couple of bytes in such corner case.(CVE-2022-49190)\n\nIn the Linux kernel, the following vulnerability has been resolved:drivers: staging: rtl8723bs: Fix deadlock in rtw_surveydone_event_callback()There is a deadlock in rtw_surveydone_event_callback(),which is shown below:   (Thread 1)                  |      (Thread 2)                               | _set_timer()rtw_surveydone_event_callback()|  mod_timer() spin_lock_bh() //(1)          |  (wait a time) ...                           | rtw_scan_timeout_handler() del_timer_sync()              |  spin_lock_bh() //(2) (wait timer to stop)          |  ...We hold pmlmepriv-\u0026gt;lock in position (1) of thread 1 and usedel_timer_sync() to wait timer to stop, but timer handleralso need pmlmepriv-\u0026gt;lock in position (2) of thread 2.As a result, rtw_surveydone_event_callback() will block forever.This patch extracts del_timer_sync() from the protection ofspin_lock_bh(), which could let timer handler to obtainthe needed lock. What`s more, we change spin_lock_bh() inrtw_scan_timeout_handler() to spin_lock_irq(). Otherwise,spin_lock_bh() will also cause deadlock() in timer handler.(CVE-2022-49309)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ndrm/scheduler: fix fence ref counting\n\nWe leaked dependency fences when processes were beeing killed.\n\nAdditional to that grab a reference to the last scheduled fence.(CVE-2022-49829)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nusb: cdns3: fix random warning message when driver load\n\nWarning log:\n[    4.141392] Unexpected gfp: 0x4 (GFP_DMA32). Fixing up to gfp: 0xa20 (GFP_ATOMIC). Fix your code!\n[    4.150340] CPU: 1 PID: 175 Comm: 1-0050 Not tainted 5.15.5-00039-g2fd9ae1b568c #20\n[    4.158010] Hardware name: Freescale i.MX8QXP MEK (DT)\n[    4.163155] Call trace:\n[    4.165600]  dump_backtrace+0x0/0x1b0\n[    4.169286]  show_stack+0x18/0x68\n[    4.172611]  dump_stack_lvl+0x68/0x84\n[    4.176286]  dump_stack+0x18/0x34\n[    4.179613]  kmalloc_fix_flags+0x60/0x88\n[    4.183550]  new_slab+0x334/0x370\n[    4.186878]  ___slab_alloc.part.108+0x4d4/0x748\n[    4.191419]  __slab_alloc.isra.109+0x30/0x78\n[    4.195702]  kmem_cache_alloc+0x40c/0x420\n[    4.199725]  dma_pool_alloc+0xac/0x1f8\n[    4.203486]  cdns3_allocate_trb_pool+0xb4/0xd0\n\npool_alloc_page(struct dma_pool *pool, gfp_t mem_flags)\n{\n\t...\n\tpage = kmalloc(sizeof(*page), mem_flags);\n\tpage-\u0026gt;vaddr = dma_alloc_coherent(pool-\u0026gt;dev, pool-\u0026gt;allocation,\n\t\t\t\t\t \u0026amp;page-\u0026gt;dma, mem_flags);\n\t...\n}\n\nkmalloc was called with mem_flags, which is passed down in\ncdns3_allocate_trb_pool() and have GFP_DMA32 flags.\nkmall_fix_flags() report warning.\n\nGFP_DMA32 is not useful at all. dma_alloc_coherent() will handle\nDMA memory region correctly by pool-\u0026gt;dev. GFP_DMA32 can be removed\nsafely.(CVE-2022-50151)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nof: check previous kernel\u0026apos;s ima-kexec-buffer against memory bounds\n\nPresently ima_get_kexec_buffer() doesn\u0026apos;t check if the previous kernel\u0026apos;s\nima-kexec-buffer lies outside the addressable memory range. This can result\nin a kernel panic if the new kernel is booted with \u0026apos;mem=X\u0026apos; arg and the\nima-kexec-buffer was allocated beyond that range by the previous kernel.\nThe panic is usually of the form below:\n\n$ sudo kexec --initrd initrd vmlinux --append=\u0026apos;mem=16G\u0026apos;\n\n\u0026lt;snip\u0026gt;\n BUG: Unable to handle kernel data access on read at 0xc000c01fff7f0000\n Faulting instruction address: 0xc000000000837974\n Oops: Kernel access of bad area, sig: 11 [#1]\n\u0026lt;snip\u0026gt;\n NIP [c000000000837974] ima_restore_measurement_list+0x94/0x6c0\n LR [c00000000083b55c] ima_load_kexec_buffer+0xac/0x160\n Call Trace:\n [c00000000371fa80] [c00000000083b55c] ima_load_kexec_buffer+0xac/0x160\n [c00000000371fb00] [c0000000020512c4] ima_init+0x80/0x108\n [c00000000371fb70] [c0000000020514dc] init_ima+0x4c/0x120\n [c00000000371fbf0] [c000000000012240] do_one_initcall+0x60/0x2c0\n [c00000000371fcc0] [c000000002004ad0] kernel_init_freeable+0x344/0x3ec\n [c00000000371fda0] [c0000000000128a4] kernel_init+0x34/0x1b0\n [c00000000371fe10] [c00000000000ce64] ret_from_kernel_thread+0x5c/0x64\n Instruction dump:\n f92100b8 f92100c0 90e10090 910100a0 4182050c 282a0017 3bc00000 40810330\n 7c0802a6 fb610198 7c9b2378 f80101d0 \u0026lt;a1240000\u0026gt; 2c090001 40820614 e9240010\n ---[ end trace 0000000000000000 ]---\n\nFix this issue by checking returned PFN range of previous kernel\u0026apos;s\nima-kexec-buffer with page_is_ram() to ensure correct memory bounds.(CVE-2022-50159)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nregulator: core: Use different devices for resource allocation and DT lookup\n\nFollowing by the below discussion, there\u0026apos;s the potential UAF issue\nbetween regulator and mfd.\nhttps://lore.kernel.org/all/(CVE-2022-50616)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nwifi: mt76: do not run mt76u_status_worker if the device is not running\n\nFix the following NULL pointer dereference avoiding to run\nmt76u_status_worker thread if the device is not running yet.\n\nKASAN: null-ptr-deref in range\n[0x0000000000000000-0x0000000000000007]\nCPU: 0 PID: 98 Comm: kworker/u2:2 Not tainted 5.14.0+ #78 Hardware\nname: QEMU Standard PC (i440FX + PIIX, 1996), BIOS\nrel-1.12.1-0-ga5cab58e9a3f-prebuilt.qemu.org 04/01/2014\nWorkqueue: mt76 mt76u_tx_status_data\nRIP: 0010:mt76x02_mac_fill_tx_status.isra.0+0x82c/0x9e0\nCode: c5 48 b8 00 00 00 00 00 fc ff df 80 3c 02 00 0f 85 94 01 00 00\n48 b8 00 00 00 00 00 fc ff df 4d 8b 34 24 4c 89 f2 48 c1 ea 03 \u0026lt;0f\u0026gt;\nb6\n04 02 84 c0 74 08 3c 03 0f 8e 89 01 00 00 41 8b 16 41 0f b7\nRSP: 0018:ffffc900005af988 EFLAGS: 00010246\nRAX: dffffc0000000000 RBX: ffffc900005afae8 RCX: 0000000000000000\nRDX: 0000000000000000 RSI: ffffffff832fc661 RDI: ffffc900005afc2a\nRBP: ffffc900005afae0 R08: 0000000000000001 R09: fffff520000b5f3c\nR10: 0000000000000003 R11: fffff520000b5f3b R12: ffff88810b6132d8\nR13: 000000000000ffff R14: 0000000000000000 R15: ffffc900005afc28\nFS:  0000000000000000(0000) GS:ffff88811aa00000(0000)\nknlGS:0000000000000000\nCS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033\nCR2: 00007fa0eda6a000 CR3: 0000000118f17000 CR4: 0000000000750ef0\nPKRU: 55555554\nCall Trace:\n mt76x02_send_tx_status+0x1d2/0xeb0\n mt76x02_tx_status_data+0x8e/0xd0\n mt76u_tx_status_data+0xe1/0x240\n process_one_work+0x92b/0x1460\n worker_thread+0x95/0xe00\n kthread+0x3a1/0x480\n ret_from_fork+0x1f/0x30\nModules linked in:\n--[ end trace 8df5d20fc5040f65 ]--\nRIP: 0010:mt76x02_mac_fill_tx_status.isra.0+0x82c/0x9e0\nCode: c5 48 b8 00 00 00 00 00 fc ff df 80 3c 02 00 0f 85 94 01 00 00\n48 b8 00 00 00 00 00 fc ff df 4d 8b 34 24 4c 89 f2 48 c1 ea 03 \u0026lt;0f\u0026gt;\nb6\n04 02 84 c0 74 08 3c 03 0f 8e 89 01 00 00 41 8b 16 41 0f b7\nRSP: 0018:ffffc900005af988 EFLAGS: 00010246\nRAX: dffffc0000000000 RBX: ffffc900005afae8 RCX: 0000000000000000\nRDX: 0000000000000000 RSI: ffffffff832fc661 RDI: ffffc900005afc2a\nRBP: ffffc900005afae0 R08: 0000000000000001 R09: fffff520000b5f3c\nR10: 0000000000000003 R11: fffff520000b5f3b R12: ffff88810b6132d8\nR13: 000000000000ffff R14: 0000000000000000 R15: ffffc900005afc28\nFS:  0000000000000000(0000) GS:ffff88811aa00000(0000)\nknlGS:0000000000000000\nCS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033\nCR2: 00007fa0eda6a000 CR3: 0000000118f17000 CR4: 0000000000750ef0\nPKRU: 55555554\n\nMoreover move stat_work schedule out of the for loop.(CVE-2022-50735)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnetfilter: allow exp not to be removed in nf_ct_find_expectation\n\nCurrently nf_conntrack_in() calling nf_ct_find_expectation() will\nremove the exp from the hash table. However, in some scenario, we\nexpect the exp not to be removed when the created ct will not be\nconfirmed, like in OVS and TC conntrack in the following patches.\n\nThis patch allows exp not to be removed by setting IPS_CONFIRMED\nin the status of the tmpl.(CVE-2023-52927)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nfirmware: dmi-sysfs: Fix null-ptr-deref in dmi_sysfs_register_handle\n\nKASAN reported a null-ptr-deref error:\n\nKASAN: null-ptr-deref in range [0x0000000000000008-0x000000000000000f]\nCPU: 0 PID: 1373 Comm: modprobe\nHardware name: QEMU Standard PC (i440FX + PIIX, 1996)\nRIP: 0010:dmi_sysfs_entry_release\n...\nCall Trace:\n \u0026lt;TASK\u0026gt;\n kobject_put\n dmi_sysfs_register_handle (drivers/firmware/dmi-sysfs.c:540) dmi_sysfs\n dmi_decode_table (drivers/firmware/dmi_scan.c:133)\n dmi_walk (drivers/firmware/dmi_scan.c:1115)\n dmi_sysfs_init (drivers/firmware/dmi-sysfs.c:149) dmi_sysfs\n do_one_initcall (init/main.c:1296)\n ...\nKernel panic - not syncing: Fatal exception\nKernel Offset: 0x4000000 from 0xffffffff81000000\n---[ end Kernel panic - not syncing: Fatal exception ]---\n\nIt is because previous patch added kobject_put() to release the memory\nwhich will call  dmi_sysfs_entry_release() and list_del().\n\nHowever, list_add_tail(entry-\u0026gt;list) is called after the error block,\nso the list_head is uninitialized and cannot be deleted.\n\nMove error handling to after list_add_tail to fix this.(CVE-2023-53250)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ncacheinfo: Fix shared_cpu_map to handle shared caches at different levels\n\nThe cacheinfo sets up the shared_cpu_map by checking whether the caches\nwith the same index are shared between CPUs. However, this will trigger\nslab-out-of-bounds access if the CPUs do not have the same cache hierarchy.\nAnother problem is the mismatched shared_cpu_map when the shared cache does\nnot have the same index between CPUs.\n\nCPU0\tI\tD\tL3\nindex\t0\t1\t2\tx\n\t^\t^\t^\t^\nindex\t0\t1\t2\t3\nCPU1\tI\tD\tL2\tL3\n\nThis patch checks each cache is shared with all caches on other CPUs.(CVE-2023-53254)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nscsi: ses: Fix slab-out-of-bounds in ses_intf_remove()\n\nA fix for:\n\nBUG: KASAN: slab-out-of-bounds in ses_intf_remove+0x23f/0x270 [ses]\nRead of size 8 at addr ffff88a10d32e5d8 by task rmmod/12013\n\nWhen edev-\u0026gt;components is zero, accessing edev-\u0026gt;component[0] members is\nwrong.(CVE-2023-53521)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ndriver core: fix resource leak in device_add()\n\nWhen calling kobject_add() failed in device_add(), it will call\ncleanup_glue_dir() to free resource. But in kobject_add(),\ndev-\u0026gt;kobj.parent has been set to NULL. This will cause resource leak.\n\nThe process is as follows:\ndevice_add()\n\tget_device_parent()\n\t\tclass_dir_create_and_add()\n\t\t\tkobject_add()\t\t//kobject_get()\n\t...\n\tdev-\u0026gt;kobj.parent = kobj;\n\t...\n\tkobject_add()\t\t//failed, but set dev-\u0026gt;kobj.parent = NULL\n\t...\n\tglue_dir = get_glue_dir(dev)\t//glue_dir = NULL, and goto\n\t\t\t\t\t//\u0026quot;Error\u0026quot; label\n\t...\n\tcleanup_glue_dir()\t//becaues glue_dir is NULL, not call\n\t\t\t\t//kobject_put()\n\nThe preceding problem may cause insmod mac80211_hwsim.ko to failed.\nsysfs: cannot create duplicate filename \u0026apos;/devices/virtual/mac80211_hwsim\u0026apos;\nCall Trace:\n\u0026lt;TASK\u0026gt;\ndump_stack_lvl+0x8e/0xd1\nsysfs_warn_dup.cold+0x1c/0x29\nsysfs_create_dir_ns+0x224/0x280\nkobject_add_internal+0x2aa/0x880\nkobject_add+0x135/0x1a0\nget_device_parent+0x3d7/0x590\ndevice_add+0x2aa/0x1cb0\ndevice_create_groups_vargs+0x1eb/0x260\ndevice_create+0xdc/0x110\nmac80211_hwsim_new_radio+0x31e/0x4790 [mac80211_hwsim]\ninit_mac80211_hwsim+0x48d/0x1000 [mac80211_hwsim]\ndo_one_initcall+0x10f/0x630\ndo_init_module+0x19f/0x5e0\nload_module+0x64b7/0x6eb0\n__do_sys_finit_module+0x140/0x200\ndo_syscall_64+0x35/0x80\nentry_SYSCALL_64_after_hwframe+0x46/0xb0\n\u0026lt;/TASK\u0026gt;\nkobject_add_internal failed for mac80211_hwsim with -EEXIST, don\u0026apos;t try to\nregister things with the same name in the same directory.(CVE-2023-53594)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nARM: 9317/1: kexec: Make smp stop calls asynchronous\n\nIf a panic is triggered by a hrtimer interrupt all online cpus will be\nnotified and set offline. But as highlighted by commit 19dbdcb8039c\n(\u0026quot;smp: Warn on function calls from softirq context\u0026quot;) this call should\nnot be made synchronous with disabled interrupts:\n\n softdog: Initiating panic\n Kernel panic - not syncing: Software Watchdog Timer expired\n WARNING: CPU: 1 PID: 0 at kernel/smp.c:753 smp_call_function_many_cond\n   unwind_backtrace:\n     show_stack\n     dump_stack_lvl\n     __warn\n     warn_slowpath_fmt\n     smp_call_function_many_cond\n     smp_call_function\n     crash_smp_send_stop.part.0\n     machine_crash_shutdown\n     __crash_kexec\n     panic\n     softdog_fire\n     __hrtimer_run_queues\n     hrtimer_interrupt\n\nMake the smp call for machine_crash_nonpanic_core() asynchronous.(CVE-2023-53712)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nusb: early: xhci-dbc: Fix a potential out-of-bound memory access\n\nIf xdbc_bulk_write() fails, the values in \u0026apos;buf\u0026apos; can be anything. So the\nstring is not guaranteed to be NULL terminated when xdbc_trace() is called.\n\nReserve an extra byte, which will be zeroed automatically because \u0026apos;buf\u0026apos; is\na static variable, in order to avoid troubles, should it happen.(CVE-2023-53840)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nRDMA/bnxt_re: Prevent handling any completions after qp destroy\n\nHW may generate completions that indicates QP is destroyed.\nDriver should not be scheduling any more completion handlers\nfor this QP, after the QP is destroyed. Since CQs are active\nduring the QP destroy, driver may still schedule completion\nhandlers. This can cause a race where the destroy_cq and poll_cq\nrunning simultaneously.\n\nSnippet of kernel panic while doing bnxt_re driver load unload in loop.\nThis indicates a poll after the CQ is freed. \n\n[77786.481636] Call Trace:\n[77786.481640]  \u0026lt;TASK\u0026gt;\n[77786.481644]  bnxt_re_poll_cq+0x14a/0x620 [bnxt_re]\n[77786.481658]  ? kvm_clock_read+0x14/0x30\n[77786.481693]  __ib_process_cq+0x57/0x190 [ib_core]\n[77786.481728]  ib_cq_poll_work+0x26/0x80 [ib_core]\n[77786.481761]  process_one_work+0x1e5/0x3f0\n[77786.481768]  worker_thread+0x50/0x3a0\n[77786.481785]  ? __pfx_worker_thread+0x10/0x10\n[77786.481790]  kthread+0xe2/0x110\n[77786.481794]  ? __pfx_kthread+0x10/0x10\n[77786.481797]  ret_from_fork+0x2c/0x50\n\nTo avoid this, complete all completion handlers before returning the\ndestroy QP. If free_cq is called soon after destroy_qp,  IB stack\nwill cancel the CQ work before invoking the destroy_cq verb and\nthis will prevent any race mentioned.(CVE-2023-54048)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nbpf: drop unnecessary user-triggerable WARN_ONCE in verifierl log\n\nIt\u0026apos;s trivial for user to trigger \u0026quot;verifier log line truncated\u0026quot; warning,\nas verifier has a fixed-sized buffer of 1024 bytes (as of now), and there are at\nleast two pieces of user-provided information that can be output through\nthis buffer, and both can be arbitrarily sized by user:\n  - BTF names;\n  - BTF.ext source code lines strings.\n\nVerifier log buffer should be properly sized for typical verifier state\noutput. But it\u0026apos;s sort-of expected that this buffer won\u0026apos;t be long enough\nin some circumstances. So let\u0026apos;s drop the check. In any case code will\nwork correctly, at worst truncating a part of a single line output.(CVE-2023-54145)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ndriver core: fix potential null-ptr-deref in device_add()\n\nI got the following null-ptr-deref report while doing fault injection test:\n\nBUG: kernel NULL pointer dereference, address: 0000000000000058\nCPU: 2 PID: 278 Comm: 37-i2c-ds2482 Tainted: G    B   W        N 6.1.0-rc3+\nRIP: 0010:klist_put+0x2d/0xd0\nCall Trace:\n \u0026lt;TASK\u0026gt;\n klist_remove+0xf1/0x1c0\n device_release_driver_internal+0x196/0x210\n bus_remove_device+0x1bd/0x240\n device_add+0xd3d/0x1100\n w1_add_master_device+0x476/0x490 [wire]\n ds2482_probe+0x303/0x3e0 [ds2482]\n\nThis is how it happened:\n\nw1_alloc_dev()\n  // The dev-\u0026gt;driver is set to w1_master_driver.\n  memcpy(\u0026amp;dev-\u0026gt;dev, device, sizeof(struct device));\n  device_add()\n    bus_add_device()\n    dpm_sysfs_add() // It fails, calls bus_remove_device.\n\n    // error path\n    bus_remove_device()\n      // The dev-\u0026gt;driver is not null, but driver is not bound.\n      __device_release_driver()\n        klist_remove(\u0026amp;dev-\u0026gt;p-\u0026gt;knode_driver) \u0026lt;-- It causes null-ptr-deref.\n\n    // normal path\n    bus_probe_device() // It\u0026apos;s not called yet.\n      device_bind_driver()\n\nIf dev-\u0026gt;driver is set, in the error path after calling bus_add_device()\nin device_add(), bus_remove_device() is called, then the device will be\ndetached from driver. But device_bind_driver() is not called yet, so it\ncauses null-ptr-deref while access the \u0026apos;knode_driver\u0026apos;. To fix this, set\ndev-\u0026gt;driver to null in the error path before calling bus_remove_device().(CVE-2023-54321)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nsmb: client: fix use-after-free of signing key\n\nCustomers have reported use-after-free in @ses-\u0026gt;auth_key.response with\nSMB2.1 + sign mounts which occurs due to following race:\n\ntask A                         task B\ncifs_mount()\n dfs_mount_share()\n  get_session()\n   cifs_mount_get_session()    cifs_send_recv()\n    cifs_get_smb_ses()          compound_send_recv()\n     cifs_setup_session()        smb2_setup_request()\n      kfree_sensitive()           smb2_calc_signature()\n                                   crypto_shash_setkey() *UAF*\n\nFix this by ensuring that we have a valid @ses-\u0026gt;auth_key.response by\nchecking whether @ses-\u0026gt;ses_status is SES_GOOD or SES_EXITING with\n@ses-\u0026gt;ses_lock held.  After commit 24a9799aa8ef (\u0026quot;smb: client: fix UAF\nin smb2_reconnect_server()\u0026quot;), we made sure to call -\u0026gt;logoff() only\nwhen @ses was known to be good (e.g. valid -\u0026gt;auth_key.response), so\nit\u0026apos;s safe to access signing key when @ses-\u0026gt;ses_status == SES_EXITING.(CVE-2024-53179)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nice: fix memory leak in aRFS after reset\n\nFix aRFS (accelerated Receive Flow Steering) structures memory leak by\nadding a checker to verify if aRFS memory is already allocated while\nconfiguring VSI. aRFS objects are allocated in two cases:\n- as part of VSI initialization (at probe), and\n- as part of reset handling\n\nHowever, VSI reconfiguration executed during reset involves memory\nallocation one more time, without prior releasing already allocated\nresources. This led to the memory leak with the following signature:\n\n[root@os-delivery ~]# cat /sys/kernel/debug/kmemleak\nunreferenced object 0xff3c1ca7252e6000 (size 8192):\n  comm \u0026quot;kworker/0:0\u0026quot;, pid 8, jiffies 4296833052\n  hex dump (first 32 bytes):\n    00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................\n    00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................\n  backtrace (crc 0):\n    [\u0026lt;ffffffff991ec485\u0026gt;] __kmalloc_cache_noprof+0x275/0x340\n    [\u0026lt;ffffffffc0a6e06a\u0026gt;] ice_init_arfs+0x3a/0xe0 [ice]\n    [\u0026lt;ffffffffc09f1027\u0026gt;] ice_vsi_cfg_def+0x607/0x850 [ice]\n    [\u0026lt;ffffffffc09f244b\u0026gt;] ice_vsi_setup+0x5b/0x130 [ice]\n    [\u0026lt;ffffffffc09c2131\u0026gt;] ice_init+0x1c1/0x460 [ice]\n    [\u0026lt;ffffffffc09c64af\u0026gt;] ice_probe+0x2af/0x520 [ice]\n    [\u0026lt;ffffffff994fbcd3\u0026gt;] local_pci_probe+0x43/0xa0\n    [\u0026lt;ffffffff98f07103\u0026gt;] work_for_cpu_fn+0x13/0x20\n    [\u0026lt;ffffffff98f0b6d9\u0026gt;] process_one_work+0x179/0x390\n    [\u0026lt;ffffffff98f0c1e9\u0026gt;] worker_thread+0x239/0x340\n    [\u0026lt;ffffffff98f14abc\u0026gt;] kthread+0xcc/0x100\n    [\u0026lt;ffffffff98e45a6d\u0026gt;] ret_from_fork+0x2d/0x50\n    [\u0026lt;ffffffff98e083ba\u0026gt;] ret_from_fork_asm+0x1a/0x30\n    ...(CVE-2025-21981)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nwatch_queue: fix pipe accounting mismatch\n\nCurrently, watch_queue_set_size() modifies the pipe buffers charged to\nuser-\u0026gt;pipe_bufs without updating the pipe-\u0026gt;nr_accounted on the pipe\nitself, due to the if (!pipe_has_watch_queue()) test in\npipe_resize_ring(). This means that when the pipe is ultimately freed,\nwe decrement user-\u0026gt;pipe_bufs by something other than what than we had\ncharged to it, potentially leading to an underflow. This in turn can\ncause subsequent too_many_pipe_buffers_soft() tests to fail with -EPERM.\n\nTo remedy this, explicitly account for the pipe usage in\nwatch_queue_set_size() to match the number set via account_pipe_buffers()\n\n(It\u0026apos;s unclear why watch_queue_set_size() does not update nr_accounted;\nit may be due to intentional overprovisioning in watch_queue_set_size()?)(CVE-2025-23138)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ndrm/amd/pm: Prevent division by zero\n\nThe user can set any speed value.\nIf speed is greater than UINT_MAX/8, division by zero is possible.\n\nFound by Linux Verification Center (linuxtesting.org) with SVACE.(CVE-2025-37766)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ndrm/amd/pm: Prevent division by zero\n\nThe user can set any speed value.\nIf speed is greater than UINT_MAX/8, division by zero is possible.\n\nFound by Linux Verification Center (linuxtesting.org) with SVACE.(CVE-2025-37770)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nksmbd: prevent out-of-bounds stream writes by validating *pos\n\nksmbd_vfs_stream_write() did not validate whether the write offset\n(*pos) was within the bounds of the existing stream data length (v_len).\nIf *pos was greater than or equal to v_len, this could lead to an\nout-of-bounds memory write.\n\nThis patch adds a check to ensure *pos is less than v_len before\nproceeding. If the condition fails, -EINVAL is returned.(CVE-2025-37947)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ncrypto: lzo - Fix compression buffer overrun\n\nUnlike the decompression code, the compression code in LZO never\nchecked for output overruns.  It instead assumes that the caller\nalways provides enough buffer space, disregarding the buffer length\nprovided by the caller.\n\nAdd a safe compression interface that checks for the end of buffer\nbefore each write.  Use the safe interface in crypto/lzo.(CVE-2025-38068)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nbpf, sockmap: Avoid using sk_socket after free when sending\n\nThe sk-\u0026gt;sk_socket is not locked or referenced in backlog thread, and\nduring the call to skb_send_sock(), there is a race condition with\nthe release of sk_socket. All types of sockets(tcp/udp/unix/vsock)\nwill be affected.\n\nRace conditions:\n\u0026apos;\u0026apos;\u0026apos;\nCPU0                               CPU1\n\nbacklog::skb_send_sock\n  sendmsg_unlocked\n    sock_sendmsg\n      sock_sendmsg_nosec\n                                   close(fd):\n                                     ...\n                                     ops-\u0026gt;release() -\u0026gt; sock_map_close()\n                                     sk_socket-\u0026gt;ops = NULL\n                                     free(socket)\n      sock-\u0026gt;ops-\u0026gt;sendmsg\n            ^\n            panic here\n\u0026apos;\u0026apos;\u0026apos;\n\nThe ref of psock become 0 after sock_map_close() executed.\n\u0026apos;\u0026apos;\u0026apos;\nvoid sock_map_close()\n{\n    ...\n    if (likely(psock)) {\n    ...\n    // !! here we remove psock and the ref of psock become 0\n    sock_map_remove_links(sk, psock)\n    psock = sk_psock_get(sk);\n    if (unlikely(!psock))\n        goto no_psock; \u0026lt;=== Control jumps here via goto\n        ...\n        cancel_delayed_work_sync(\u0026amp;psock-\u0026gt;work); \u0026lt;=== not executed\n        sk_psock_put(sk, psock);\n        ...\n}\n\u0026apos;\u0026apos;\u0026apos;\n\nBased on the fact that we already wait for the workqueue to finish in\nsock_map_close() if psock is held, we simply increase the psock\nreference count to avoid race conditions.\n\nWith this patch, if the backlog thread is running, sock_map_close() will\nwait for the backlog thread to complete and cancel all pending work.\n\nIf no backlog running, any pending work that hasn\u0026apos;t started by then will\nfail when invoked by sk_psock_get(), as the psock reference count have\nbeen zeroed, and sk_psock_drop() will cancel all jobs via\ncancel_delayed_work_sync().\n\nIn summary, we require synchronization to coordinate the backlog thread\nand close() thread.\n\nThe panic I catched:\n\u0026apos;\u0026apos;\u0026apos;\nWorkqueue: events sk_psock_backlog\nRIP: 0010:sock_sendmsg+0x21d/0x440\nRAX: 0000000000000000 RBX: ffffc9000521fad8 RCX: 0000000000000001\n...\nCall Trace:\n \u0026lt;TASK\u0026gt;\n ? die_addr+0x40/0xa0\n ? exc_general_protection+0x14c/0x230\n ? asm_exc_general_protection+0x26/0x30\n ? sock_sendmsg+0x21d/0x440\n ? sock_sendmsg+0x3e0/0x440\n ? __pfx_sock_sendmsg+0x10/0x10\n __skb_send_sock+0x543/0xb70\n sk_psock_backlog+0x247/0xb80\n...\n\u0026apos;\u0026apos;\u0026apos;(CVE-2025-38154)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nBluetooth: hci_core: Fix use-after-free in vhci_flush()\n\nsyzbot reported use-after-free in vhci_flush() without repro. [0]\n\nFrom the splat, a thread close()d a vhci file descriptor while\nits device was being used by iotcl() on another thread.\n\nOnce the last fd refcnt is released, vhci_release() calls\nhci_unregister_dev(), hci_free_dev(), and kfree() for struct\nvhci_data, which is set to hci_dev-\u0026gt;dev-\u0026gt;driver_data.\n\nThe problem is that there is no synchronisation after unlinking\nhdev from hci_dev_list in hci_unregister_dev().  There might be\nanother thread still accessing the hdev which was fetched before\nthe unlink operation.\n\nWe can use SRCU for such synchronisation.\n\nLet\u0026apos;s run hci_dev_reset() under SRCU and wait for its completion\nin hci_unregister_dev().\n\nAnother option would be to restore hci_dev-\u0026gt;destruct(), which was\nremoved in commit 587ae086f6e4 (\u0026quot;Bluetooth: Remove unused\nhci-destruct cb\u0026quot;).  However, this would not be a good solution, as\nwe should not run hci_unregister_dev() while there are in-flight\nioctl() requests, which could lead to another data-race KCSAN splat.\n\nNote that other drivers seem to have the same problem, for exmaple,\nvirtbt_remove().\n\n[0]:\nBUG: KASAN: slab-use-after-free in skb_queue_empty_lockless include/linux/skbuff.h:1891 [inline]\nBUG: KASAN: slab-use-after-free in skb_queue_purge_reason+0x99/0x360 net/core/skbuff.c:3937\nRead of size 8 at addr ffff88807cb8d858 by task syz.1.219/6718\n\nCPU: 1 UID: 0 PID: 6718 Comm: syz.1.219 Not tainted 6.16.0-rc1-syzkaller-00196-g08207f42d3ff #0 PREEMPT(full)\nHardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 05/07/2025\nCall Trace:\n \u0026lt;TASK\u0026gt;\n dump_stack_lvl+0x189/0x250 lib/dump_stack.c:120\n print_address_description mm/kasan/report.c:408 [inline]\n print_report+0xd2/0x2b0 mm/kasan/report.c:521\n kasan_report+0x118/0x150 mm/kasan/report.c:634\n skb_queue_empty_lockless include/linux/skbuff.h:1891 [inline]\n skb_queue_purge_reason+0x99/0x360 net/core/skbuff.c:3937\n skb_queue_purge include/linux/skbuff.h:3368 [inline]\n vhci_flush+0x44/0x50 drivers/bluetooth/hci_vhci.c:69\n hci_dev_do_reset net/bluetooth/hci_core.c:552 [inline]\n hci_dev_reset+0x420/0x5c0 net/bluetooth/hci_core.c:592\n sock_do_ioctl+0xd9/0x300 net/socket.c:1190\n sock_ioctl+0x576/0x790 net/socket.c:1311\n vfs_ioctl fs/ioctl.c:51 [inline]\n __do_sys_ioctl fs/ioctl.c:907 [inline]\n __se_sys_ioctl+0xf9/0x170 fs/ioctl.c:893\n do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline]\n do_syscall_64+0xfa/0x3b0 arch/x86/entry/syscall_64.c:94\n entry_SYSCALL_64_after_hwframe+0x77/0x7f\nRIP: 0033:0x7fcf5b98e929\nCode: ff ff c3 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 40 00 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 \u0026lt;48\u0026gt; 3d 01 f0 ff ff 73 01 c3 48 c7 c1 a8 ff ff ff f7 d8 64 89 01 48\nRSP: 002b:00007fcf5c7b9038 EFLAGS: 00000246 ORIG_RAX: 0000000000000010\nRAX: ffffffffffffffda RBX: 00007fcf5bbb6160 RCX: 00007fcf5b98e929\nRDX: 0000000000000000 RSI: 00000000400448cb RDI: 0000000000000009\nRBP: 00007fcf5ba10b39 R08: 0000000000000000 R09: 0000000000000000\nR10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000\nR13: 0000000000000000 R14: 00007fcf5bbb6160 R15: 00007ffd6353d528\n \u0026lt;/TASK\u0026gt;\n\nAllocated by task 6535:\n kasan_save_stack mm/kasan/common.c:47 [inline]\n kasan_save_track+0x3e/0x80 mm/kasan/common.c:68\n poison_kmalloc_redzone mm/kasan/common.c:377 [inline]\n __kasan_kmalloc+0x93/0xb0 mm/kasan/common.c:394\n kasan_kmalloc include/linux/kasan.h:260 [inline]\n __kmalloc_cache_noprof+0x230/0x3d0 mm/slub.c:4359\n kmalloc_noprof include/linux/slab.h:905 [inline]\n kzalloc_noprof include/linux/slab.h:1039 [inline]\n vhci_open+0x57/0x360 drivers/bluetooth/hci_vhci.c:635\n misc_open+0x2bc/0x330 drivers/char/misc.c:161\n chrdev_open+0x4c9/0x5e0 fs/char_dev.c:414\n do_dentry_open+0xdf0/0x1970 fs/open.c:964\n vfs_open+0x3b/0x340 fs/open.c:1094\n do_open fs/namei.c:3887 [inline]\n path_openat+0x2ee5/0x3830 fs/name\n---truncated---(CVE-2025-38250)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ncomedi: Fix use of uninitialized data in insn_rw_emulate_bits()\n\nFor Comedi `INSN_READ` and `INSN_WRITE` instructions on \u0026quot;digital\u0026quot;\nsubdevices (subdevice types `COMEDI_SUBD_DI`, `COMEDI_SUBD_DO`, and\n`COMEDI_SUBD_DIO`), it is common for the subdevice driver not to have\n`insn_read` and `insn_write` handler functions, but to have an\n`insn_bits` handler function for handling Comedi `INSN_BITS`\ninstructions.  In that case, the subdevice\u0026apos;s `insn_read` and/or\n`insn_write` function handler pointers are set to point to the\n`insn_rw_emulate_bits()` function by `__comedi_device_postconfig()`.\n\nFor `INSN_WRITE`, `insn_rw_emulate_bits()` currently assumes that the\nsupplied `data[0]` value is a valid copy from user memory.  It will at\nleast exist because `do_insnlist_ioctl()` and `do_insn_ioctl()` in\n\u0026quot;comedi_fops.c\u0026quot; ensure at lease `MIN_SAMPLES` (16) elements are\nallocated.  However, if `insn-\u0026gt;n` is 0 (which is allowable for\n`INSN_READ` and `INSN_WRITE` instructions, then `data[0]` may contain\nuninitialized data, and certainly contains invalid data, possibly from a\ndifferent instruction in the array of instructions handled by\n`do_insnlist_ioctl()`.  This will result in an incorrect value being\nwritten to the digital output channel (or to the digital input/output\nchannel if configured as an output), and may be reflected in the\ninternal saved state of the channel.\n\nFix it by returning 0 early if `insn-\u0026gt;n` is 0, before reaching the code\nthat accesses `data[0]`.  Previously, the function always returned 1 on\nsuccess, but it is supposed to be the number of data samples actually\nread or written up to `insn-\u0026gt;n`, which is 0 in this case.(CVE-2025-38480)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nHID: core: Harden s32ton() against conversion to 0 bits\n\nTesting by the syzbot fuzzer showed that the HID core gets a\nshift-out-of-bounds exception when it tries to convert a 32-bit\nquantity to a 0-bit quantity.  Ideally this should never occur, but\nthere are buggy devices and some might have a report field with size\nset to zero; we shouldn\u0026apos;t reject the report or the device just because\nof that.\n\nInstead, harden the s32ton() routine so that it returns a reasonable\nresult instead of crashing when it is called with the number of bits\nset to 0 -- the same as what snto32() does.(CVE-2025-38556)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nipv6: reject malicious packets in ipv6_gso_segment()\n\nsyzbot was able to craft a packet with very long IPv6 extension headers\nleading to an overflow of skb-\u0026gt;transport_header.\n\nThis 16bit field has a limited range.\n\nAdd skb_reset_transport_header_careful() helper and use it\nfrom ipv6_gso_segment()\n\nWARNING: CPU: 0 PID: 5871 at ./include/linux/skbuff.h:3032 skb_reset_transport_header include/linux/skbuff.h:3032 [inline]\nWARNING: CPU: 0 PID: 5871 at ./include/linux/skbuff.h:3032 ipv6_gso_segment+0x15e2/0x21e0 net/ipv6/ip6_offload.c:151\nModules linked in:\nCPU: 0 UID: 0 PID: 5871 Comm: syz-executor211 Not tainted 6.16.0-rc6-syzkaller-g7abc678e3084 #0 PREEMPT(full)\nHardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 07/12/2025\n RIP: 0010:skb_reset_transport_header include/linux/skbuff.h:3032 [inline]\n RIP: 0010:ipv6_gso_segment+0x15e2/0x21e0 net/ipv6/ip6_offload.c:151\nCall Trace:\n \u0026lt;TASK\u0026gt;\n  skb_mac_gso_segment+0x31c/0x640 net/core/gso.c:53\n  nsh_gso_segment+0x54a/0xe10 net/nsh/nsh.c:110\n  skb_mac_gso_segment+0x31c/0x640 net/core/gso.c:53\n  __skb_gso_segment+0x342/0x510 net/core/gso.c:124\n  skb_gso_segment include/net/gso.h:83 [inline]\n  validate_xmit_skb+0x857/0x11b0 net/core/dev.c:3950\n  validate_xmit_skb_list+0x84/0x120 net/core/dev.c:4000\n  sch_direct_xmit+0xd3/0x4b0 net/sched/sch_generic.c:329\n  __dev_xmit_skb net/core/dev.c:4102 [inline]\n  __dev_queue_xmit+0x17b6/0x3a70 net/core/dev.c:4679(CVE-2025-38572)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\npptp: ensure minimal skb length in pptp_xmit()\n\nCommit aabc6596ffb3 (\u0026quot;net: ppp: Add bound checking for skb data\non ppp_sync_txmung\u0026quot;) fixed ppp_sync_txmunge()\n\nWe need a similar fix in pptp_xmit(), otherwise we might\nread uninit data as reported by syzbot.\n\nBUG: KMSAN: uninit-value in pptp_xmit+0xc34/0x2720 drivers/net/ppp/pptp.c:193\n  pptp_xmit+0xc34/0x2720 drivers/net/ppp/pptp.c:193\n  ppp_channel_bridge_input drivers/net/ppp/ppp_generic.c:2290 [inline]\n  ppp_input+0x1d6/0xe60 drivers/net/ppp/ppp_generic.c:2314\n  pppoe_rcv_core+0x1e8/0x760 drivers/net/ppp/pppoe.c:379\n  sk_backlog_rcv+0x142/0x420 include/net/sock.h:1148\n  __release_sock+0x1d3/0x330 net/core/sock.c:3213\n  release_sock+0x6b/0x270 net/core/sock.c:3767\n  pppoe_sendmsg+0x15d/0xcb0 drivers/net/ppp/pppoe.c:904\n  sock_sendmsg_nosec net/socket.c:712 [inline]\n  __sock_sendmsg+0x330/0x3d0 net/socket.c:727\n  ____sys_sendmsg+0x893/0xd80 net/socket.c:2566\n  ___sys_sendmsg+0x271/0x3b0 net/socket.c:2620\n  __sys_sendmmsg+0x2d9/0x7c0 net/socket.c:2709(CVE-2025-38574)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nvsock: Do not allow binding to VMADDR_PORT_ANY\n\nIt is possible for a vsock to autobind to VMADDR_PORT_ANY. This can\ncause a use-after-free when a connection is made to the bound socket.\nThe socket returned by accept() also has port VMADDR_PORT_ANY but is not\non the list of unbound sockets. Binding it will result in an extra\nrefcount decrement similar to the one fixed in fcdd2242c023 (vsock: Keep\nthe binding until socket destruction).\n\nModify the check in __vsock_bind_connectible() to also prevent binding\nto VMADDR_PORT_ANY.(CVE-2025-38618)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\niommu/amd: Avoid stack buffer overflow from kernel cmdline\n\nWhile the kernel command line is considered trusted in most environments,\navoid writing 1 byte past the end of \u0026quot;acpiid\u0026quot; if the \u0026quot;str\u0026quot; argument is\nmaximum length.(CVE-2025-38676)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nsmb3: fix for slab out of bounds on mount to ksmbd\n\nWith KASAN enabled, it is possible to get a slab out of bounds\nduring mount to ksmbd due to missing check in parse_server_interfaces()\n(see below):\n\n BUG: KASAN: slab-out-of-bounds in\n parse_server_interfaces+0x14ee/0x1880 [cifs]\n Read of size 4 at addr ffff8881433dba98 by task mount/9827\n\n CPU: 5 UID: 0 PID: 9827 Comm: mount Tainted: G\n OE       6.16.0-rc2-kasan #2 PREEMPT(voluntary)\n Tainted: [O]=OOT_MODULE, [E]=UNSIGNED_MODULE\n Hardware name: Dell Inc. Precision Tower 3620/0MWYPT,\n BIOS 2.13.1 06/14/2019\n Call Trace:\n  \u0026lt;TASK\u0026gt;\n dump_stack_lvl+0x9f/0xf0\n print_report+0xd1/0x670\n __virt_addr_valid+0x22c/0x430\n ? parse_server_interfaces+0x14ee/0x1880 [cifs]\n ? kasan_complete_mode_report_info+0x2a/0x1f0\n ? parse_server_interfaces+0x14ee/0x1880 [cifs]\n   kasan_report+0xd6/0x110\n   parse_server_interfaces+0x14ee/0x1880 [cifs]\n   __asan_report_load_n_noabort+0x13/0x20\n   parse_server_interfaces+0x14ee/0x1880 [cifs]\n ? __pfx_parse_server_interfaces+0x10/0x10 [cifs]\n ? trace_hardirqs_on+0x51/0x60\n SMB3_request_interfaces+0x1ad/0x3f0 [cifs]\n ? __pfx_SMB3_request_interfaces+0x10/0x10 [cifs]\n ? SMB2_tcon+0x23c/0x15d0 [cifs]\n smb3_qfs_tcon+0x173/0x2b0 [cifs]\n ? __pfx_smb3_qfs_tcon+0x10/0x10 [cifs]\n ? cifs_get_tcon+0x105d/0x2120 [cifs]\n ? do_raw_spin_unlock+0x5d/0x200\n ? cifs_get_tcon+0x105d/0x2120 [cifs]\n ? __pfx_smb3_qfs_tcon+0x10/0x10 [cifs]\n cifs_mount_get_tcon+0x369/0xb90 [cifs]\n ? dfs_cache_find+0xe7/0x150 [cifs]\n dfs_mount_share+0x985/0x2970 [cifs]\n ? check_path.constprop.0+0x28/0x50\n ? save_trace+0x54/0x370\n ? __pfx_dfs_mount_share+0x10/0x10 [cifs]\n ? __lock_acquire+0xb82/0x2ba0\n ? __kasan_check_write+0x18/0x20\n cifs_mount+0xbc/0x9e0 [cifs]\n ? __pfx_cifs_mount+0x10/0x10 [cifs]\n ? do_raw_spin_unlock+0x5d/0x200\n ? cifs_setup_cifs_sb+0x29d/0x810 [cifs]\n cifs_smb3_do_mount+0x263/0x1990 [cifs](CVE-2025-38728)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nscsi: qla4xxx: Prevent a potential error pointer dereference\n\nThe qla4xxx_get_ep_fwdb() function is supposed to return NULL on error,\nbut qla4xxx_ep_connect() returns error pointers.  Propagating the error\npointers will lead to an Oops in the caller, so change the error pointers\nto NULL.(CVE-2025-39676)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nipv6: sr: Fix MAC comparison to be constant-time\n\nTo prevent timing attacks, MACs need to be compared in constant time.\nUse the appropriate helper function for this.(CVE-2025-39702)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nrcu: Fix rcu_read_unlock() deadloop due to IRQ work\n\nDuring rcu_read_unlock_special(), if this happens during irq_exit(), we\ncan lockup if an IPI is issued. This is because the IPI itself triggers\nthe irq_exit() path causing a recursive lock up.\n\nThis is precisely what Xiongfeng found when invoking a BPF program on\nthe trace_tick_stop() tracepoint As shown in the trace below. Fix by\nmanaging the irq_work state correctly.\n\nirq_exit()\n  __irq_exit_rcu()\n    /* in_hardirq() returns false after this */\n    preempt_count_sub(HARDIRQ_OFFSET)\n    tick_irq_exit()\n      tick_nohz_irq_exit()\n\t    tick_nohz_stop_sched_tick()\n\t      trace_tick_stop()  /* a bpf prog is hooked on this trace point */\n\t\t   __bpf_trace_tick_stop()\n\t\t      bpf_trace_run2()\n\t\t\t    rcu_read_unlock_special()\n                              /* will send a IPI to itself */\n\t\t\t      irq_work_queue_on(\u0026amp;rdp-\u0026gt;defer_qs_iw, rdp-\u0026gt;cpu);\n\nA simple reproducer can also be obtained by doing the following in\ntick_irq_exit(). It will hang on boot without the patch:\n\n  static inline void tick_irq_exit(void)\n  {\n +\trcu_read_lock();\n +\tWRITE_ONCE(current-\u0026gt;rcu_read_unlock_special.b.need_qs, true);\n +\trcu_read_unlock();\n +\n\n[neeraj: Apply Frederic\u0026apos;s suggested fix for PREEMPT_RT](CVE-2025-39744)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nrcu: Protect -\u0026gt;defer_qs_iw_pending from data race\n\nOn kernels built with CONFIG_IRQ_WORK=y, when rcu_read_unlock() is\ninvoked within an interrupts-disabled region of code [1], it will invoke\nrcu_read_unlock_special(), which uses an irq-work handler to force the\nsystem to notice when the RCU read-side critical section actually ends.\nThat end won\u0026apos;t happen until interrupts are enabled at the soonest.\n\nIn some kernels, such as those booted with rcutree.use_softirq=y, the\nirq-work handler is used unconditionally.\n\nThe per-CPU rcu_data structure\u0026apos;s -\u0026gt;defer_qs_iw_pending field is\nupdated by the irq-work handler and is both read and updated by\nrcu_read_unlock_special().  This resulted in the following KCSAN splat:\n\n------------------------------------------------------------------------\n\nBUG: KCSAN: data-race in rcu_preempt_deferred_qs_handler / rcu_read_unlock_special\n\nread to 0xffff96b95f42d8d8 of 1 bytes by task 90 on cpu 8:\n rcu_read_unlock_special+0x175/0x260\n __rcu_read_unlock+0x92/0xa0\n rt_spin_unlock+0x9b/0xc0\n __local_bh_enable+0x10d/0x170\n __local_bh_enable_ip+0xfb/0x150\n rcu_do_batch+0x595/0xc40\n rcu_cpu_kthread+0x4e9/0x830\n smpboot_thread_fn+0x24d/0x3b0\n kthread+0x3bd/0x410\n ret_from_fork+0x35/0x40\n ret_from_fork_asm+0x1a/0x30\n\nwrite to 0xffff96b95f42d8d8 of 1 bytes by task 88 on cpu 8:\n rcu_preempt_deferred_qs_handler+0x1e/0x30\n irq_work_single+0xaf/0x160\n run_irq_workd+0x91/0xc0\n smpboot_thread_fn+0x24d/0x3b0\n kthread+0x3bd/0x410\n ret_from_fork+0x35/0x40\n ret_from_fork_asm+0x1a/0x30\n\nno locks held by irq_work/8/88.\nirq event stamp: 200272\nhardirqs last  enabled at (200272): [\u0026lt;ffffffffb0f56121\u0026gt;] finish_task_switch+0x131/0x320\nhardirqs last disabled at (200271): [\u0026lt;ffffffffb25c7859\u0026gt;] __schedule+0x129/0xd70\nsoftirqs last  enabled at (0): [\u0026lt;ffffffffb0ee093f\u0026gt;] copy_process+0x4df/0x1cc0\nsoftirqs last disabled at (0): [\u0026lt;0000000000000000\u0026gt;] 0x0\n\n------------------------------------------------------------------------\n\nThe problem is that irq-work handlers run with interrupts enabled, which\nmeans that rcu_preempt_deferred_qs_handler() could be interrupted,\nand that interrupt handler might contain an RCU read-side critical\nsection, which might invoke rcu_read_unlock_special().  In the strict\nKCSAN mode of operation used by RCU, this constitutes a data race on\nthe -\u0026gt;defer_qs_iw_pending field.\n\nThis commit therefore disables interrupts across the portion of the\nrcu_preempt_deferred_qs_handler() that updates the -\u0026gt;defer_qs_iw_pending\nfield.  This suffices because this handler is not a fast path.(CVE-2025-39749)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nxfrm: Duplicate SPI Handling\n\nThe issue originates when Strongswan initiates an XFRM_MSG_ALLOCSPI\nNetlink message, which triggers the kernel function xfrm_alloc_spi().\nThis function is expected to ensure uniqueness of the Security Parameter\nIndex (SPI) for inbound Security Associations (SAs). However, it can\nreturn success even when the requested SPI is already in use, leading\nto duplicate SPIs assigned to multiple inbound SAs, differentiated\nonly by their destination addresses.\n\nThis behavior causes inconsistencies during SPI lookups for inbound packets.\nSince the lookup may return an arbitrary SA among those with the same SPI,\npacket processing can fail, resulting in packet drops.\n\nAccording to RFC 4301 section 4.4.2 , for inbound processing a unicast SA\nis uniquely identified by the SPI and optionally protocol.\n\nReproducing the Issue Reliably:\nTo consistently reproduce the problem, restrict the available SPI range in\ncharon.conf : spi_min = 0x10000000 spi_max = 0x10000002\nThis limits the system to only 2 usable SPI values.\nNext, create more than 2 Child SA. each using unique pair of src/dst address.\nAs soon as the 3rd Child SA is initiated, it will be assigned a duplicate\nSPI, since the SPI pool is already exhausted.\nWith a narrow SPI range, the issue is consistently reproducible.\nWith a broader/default range, it becomes rare and unpredictable.\n\nCurrent implementation:\nxfrm_spi_hash() lookup function computes hash using daddr, proto, and family.\nSo if two SAs have the same SPI but different destination addresses, then\nthey will:\na. Hash into different buckets\nb. Be stored in different linked lists (byspi + h)\nc. Not be seen in the same hlist_for_each_entry_rcu() iteration.\nAs a result, the lookup will result in NULL and kernel allows that Duplicate SPI\n\nProposed Change:\nxfrm_state_lookup_spi_proto() does a truly global search - across all states,\nregardless of hash bucket and matches SPI and proto.(CVE-2025-39797)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\natm: atmtcp: Prevent arbitrary write in atmtcp_recv_control().\n\nsyzbot reported the splat below. [0]\n\nWhen atmtcp_v_open() or atmtcp_v_close() is called via connect()\nor close(), atmtcp_send_control() is called to send an in-kernel\nspecial message.\n\nThe message has ATMTCP_HDR_MAGIC in atmtcp_control.hdr.length.\nAlso, a pointer of struct atm_vcc is set to atmtcp_control.vcc.\n\nThe notable thing is struct atmtcp_control is uAPI but has a\nspace for an in-kernel pointer.\n\n  struct atmtcp_control {\n  \tstruct atmtcp_hdr hdr;\t/* must be first */\n  ...\n  \tatm_kptr_t vcc;\t\t/* both directions */\n  ...\n  } __ATM_API_ALIGN;\n\n  typedef struct { unsigned char _[8]; } __ATM_API_ALIGN atm_kptr_t;\n\nThe special message is processed in atmtcp_recv_control() called\nfrom atmtcp_c_send().\n\natmtcp_c_send() is vcc-\u0026gt;dev-\u0026gt;ops-\u0026gt;send() and called from 2 paths:\n\n  1. .ndo_start_xmit() (vcc-\u0026gt;send() == atm_send_aal0())\n  2. vcc_sendmsg()\n\nThe problem is sendmsg() does not validate the message length and\nuserspace can abuse atmtcp_recv_control() to overwrite any kptr\nby atmtcp_control.\n\nLet\u0026apos;s add a new -\u0026gt;pre_send() hook to validate messages from sendmsg().\n\n[0]:\nOops: general protection fault, probably for non-canonical address 0xdffffc00200000ab: 0000 [#1] SMP KASAN PTI\nKASAN: probably user-memory-access in range [0x0000000100000558-0x000000010000055f]\nCPU: 0 UID: 0 PID: 5865 Comm: syz-executor331 Not tainted 6.17.0-rc1-syzkaller-00215-gbab3ce404553 #0 PREEMPT(full)\nHardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 07/12/2025\nRIP: 0010:atmtcp_recv_control drivers/atm/atmtcp.c:93 [inline]\nRIP: 0010:atmtcp_c_send+0x1da/0x950 drivers/atm/atmtcp.c:297\nCode: 4d 8d 75 1a 4c 89 f0 48 c1 e8 03 42 0f b6 04 20 84 c0 0f 85 15 06 00 00 41 0f b7 1e 4d 8d b7 60 05 00 00 4c 89 f0 48 c1 e8 03 \u0026lt;42\u0026gt; 0f b6 04 20 84 c0 0f 85 13 06 00 00 66 41 89 1e 4d 8d 75 1c 4c\nRSP: 0018:ffffc90003f5f810 EFLAGS: 00010203\nRAX: 00000000200000ab RBX: 0000000000000000 RCX: 0000000000000000\nRDX: ffff88802a510000 RSI: 00000000ffffffff RDI: ffff888030a6068c\nRBP: ffff88802699fb40 R08: ffff888030a606eb R09: 1ffff1100614c0dd\nR10: dffffc0000000000 R11: ffffffff8718fc40 R12: dffffc0000000000\nR13: ffff888030a60680 R14: 000000010000055f R15: 00000000ffffffff\nFS:  00007f8d7e9236c0(0000) GS:ffff888125c1c000(0000) knlGS:0000000000000000\nCS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033\nCR2: 000000000045ad50 CR3: 0000000075bde000 CR4: 00000000003526f0\nCall Trace:\n \u0026lt;TASK\u0026gt;\n vcc_sendmsg+0xa10/0xc60 net/atm/common.c:645\n sock_sendmsg_nosec net/socket.c:714 [inline]\n __sock_sendmsg+0x219/0x270 net/socket.c:729\n ____sys_sendmsg+0x505/0x830 net/socket.c:2614\n ___sys_sendmsg+0x21f/0x2a0 net/socket.c:2668\n __sys_sendmsg net/socket.c:2700 [inline]\n __do_sys_sendmsg net/socket.c:2705 [inline]\n __se_sys_sendmsg net/socket.c:2703 [inline]\n __x64_sys_sendmsg+0x19b/0x260 net/socket.c:2703\n do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline]\n do_syscall_64+0xfa/0x3b0 arch/x86/entry/syscall_64.c:94\n entry_SYSCALL_64_after_hwframe+0x77/0x7f\nRIP: 0033:0x7f8d7e96a4a9\nCode: 28 00 00 00 75 05 48 83 c4 28 c3 e8 51 18 00 00 90 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 b0 ff ff ff f7 d8 64 89 01 48\nRSP: 002b:00007f8d7e923198 EFLAGS: 00000246 ORIG_RAX: 000000000000002e\nRAX: ffffffffffffffda RBX: 00007f8d7e9f4308 RCX: 00007f8d7e96a4a9\nRDX: 0000000000000000 RSI: 0000200000000240 RDI: 0000000000000005\nRBP: 00007f8d7e9f4300 R08: 65732f636f72702f R09: 65732f636f72702f\nR10: 65732f636f72702f R11: 0000000000000246 R12: 00007f8d7e9c10ac\nR13: 00007f8d7e9231a0 R14: 0000200000000200 R15: 0000200000000250\n \u0026lt;/TASK\u0026gt;\nModules linked in:(CVE-2025-39828)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ni40e: Fix potential invalid access when MAC list is empty\n\nlist_first_entry() never returns NULL - if the list is empty, it still\nreturns a pointer to an invalid object, leading to potential invalid\nmemory access when dereferenced.\n\nFix this by using list_first_entry_or_null instead of list_first_entry.(CVE-2025-39853)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nBluetooth: Fix use-after-free in l2cap_sock_cleanup_listen()\n\nsyzbot reported the splat below without a repro.\n\nIn the splat, a single thread calling bt_accept_dequeue() freed sk\nand touched it after that.\n\nThe root cause would be the racy l2cap_sock_cleanup_listen() call\nadded by the cited commit.\n\nbt_accept_dequeue() is called under lock_sock() except for\nl2cap_sock_release().\n\nTwo threads could see the same socket during the list iteration\nin bt_accept_dequeue():\n\n  CPU1                        CPU2 (close())\n  ----                        ----\n  sock_hold(sk)               sock_hold(sk);\n  lock_sock(sk)   \u0026lt;-- block close()\n  sock_put(sk)\n  bt_accept_unlink(sk)\n    sock_put(sk)  \u0026lt;-- refcnt by bt_accept_enqueue()\n  release_sock(sk)\n                              lock_sock(sk)\n                              sock_put(sk)\n                              bt_accept_unlink(sk)\n                                sock_put(sk)        \u0026lt;-- last refcnt\n                              bt_accept_unlink(sk)  \u0026lt;-- UAF\n\nDepending on the timing, the other thread could show up in the\n\u0026quot;Freed by task\u0026quot; part.\n\nLet\u0026apos;s call l2cap_sock_cleanup_listen() under lock_sock() in\nl2cap_sock_release().\n\n[0]:\nBUG: KASAN: slab-use-after-free in debug_spin_lock_before kernel/locking/spinlock_debug.c:86 [inline]\nBUG: KASAN: slab-use-after-free in do_raw_spin_lock+0x26f/0x2b0 kernel/locking/spinlock_debug.c:115\nRead of size 4 at addr ffff88803b7eb1c4 by task syz.5.3276/16995\nCPU: 3 UID: 0 PID: 16995 Comm: syz.5.3276 Not tainted syzkaller #0 PREEMPT(full)\nHardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.16.3-debian-1.16.3-2~bpo12+1 04/01/2014\nCall Trace:\n \u0026lt;TASK\u0026gt;\n __dump_stack lib/dump_stack.c:94 [inline]\n dump_stack_lvl+0x116/0x1f0 lib/dump_stack.c:120\n print_address_description mm/kasan/report.c:378 [inline]\n print_report+0xcd/0x630 mm/kasan/report.c:482\n kasan_report+0xe0/0x110 mm/kasan/report.c:595\n debug_spin_lock_before kernel/locking/spinlock_debug.c:86 [inline]\n do_raw_spin_lock+0x26f/0x2b0 kernel/locking/spinlock_debug.c:115\n spin_lock_bh include/linux/spinlock.h:356 [inline]\n release_sock+0x21/0x220 net/core/sock.c:3746\n bt_accept_dequeue+0x505/0x600 net/bluetooth/af_bluetooth.c:312\n l2cap_sock_cleanup_listen+0x5c/0x2a0 net/bluetooth/l2cap_sock.c:1451\n l2cap_sock_release+0x5c/0x210 net/bluetooth/l2cap_sock.c:1425\n __sock_release+0xb3/0x270 net/socket.c:649\n sock_close+0x1c/0x30 net/socket.c:1439\n __fput+0x3ff/0xb70 fs/file_table.c:468\n task_work_run+0x14d/0x240 kernel/task_work.c:227\n resume_user_mode_work include/linux/resume_user_mode.h:50 [inline]\n exit_to_user_mode_loop+0xeb/0x110 kernel/entry/common.c:43\n exit_to_user_mode_prepare include/linux/irq-entry-common.h:225 [inline]\n syscall_exit_to_user_mode_work include/linux/entry-common.h:175 [inline]\n syscall_exit_to_user_mode include/linux/entry-common.h:210 [inline]\n do_syscall_64+0x3f6/0x4c0 arch/x86/entry/syscall_64.c:100\n entry_SYSCALL_64_after_hwframe+0x77/0x7f\nRIP: 0033:0x7f2accf8ebe9\nCode: ff ff c3 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 40 00 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 \u0026lt;48\u0026gt; 3d 01 f0 ff ff 73 01 c3 48 c7 c1 a8 ff ff ff f7 d8 64 89 01 48\nRSP: 002b:00007ffdb6cb1378 EFLAGS: 00000246 ORIG_RAX: 00000000000001b4\nRAX: 0000000000000000 RBX: 00000000000426fb RCX: 00007f2accf8ebe9\nRDX: 0000000000000000 RSI: 000000000000001e RDI: 0000000000000003\nRBP: 00007f2acd1b7da0 R08: 0000000000000001 R09: 00000012b6cb166f\nR10: 0000001b30e20000 R11: 0000000000000246 R12: 00007f2acd1b609c\nR13: 00007f2acd1b6090 R14: ffffffffffffffff R15: 00007ffdb6cb1490\n \u0026lt;/TASK\u0026gt;\n\nAllocated by task 5326:\n kasan_save_stack+0x33/0x60 mm/kasan/common.c:47\n kasan_save_track+0x14/0x30 mm/kasan/common.c:68\n poison_kmalloc_redzone mm/kasan/common.c:388 [inline]\n __kasan_kmalloc+0xaa/0xb0 mm/kasan/common.c:405\n kasan_kmalloc include/linux/kasan.h:260 [inline]\n __do_kmalloc_node mm/slub.c:4365 [inline]\n __kmalloc_nopro\n---truncated---(CVE-2025-39860)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ntcp_bpf: Call sk_msg_free() when tcp_bpf_send_verdict() fails to allocate psock-\u0026gt;cork.\n\nsyzbot reported the splat below. [0]\n\nThe repro does the following:\n\n  1. Load a sk_msg prog that calls bpf_msg_cork_bytes(msg, cork_bytes)\n  2. Attach the prog to a SOCKMAP\n  3. Add a socket to the SOCKMAP\n  4. Activate fault injection\n  5. Send data less than cork_bytes\n\nAt 5., the data is carried over to the next sendmsg() as it is\nsmaller than the cork_bytes specified by bpf_msg_cork_bytes().\n\nThen, tcp_bpf_send_verdict() tries to allocate psock-\u0026gt;cork to hold\nthe data, but this fails silently due to fault injection + __GFP_NOWARN.\n\nIf the allocation fails, we need to revert the sk-\u0026gt;sk_forward_alloc\nchange done by sk_msg_alloc().\n\nLet\u0026apos;s call sk_msg_free() when tcp_bpf_send_verdict fails to allocate\npsock-\u0026gt;cork.\n\nThe \u0026quot;*copied\u0026quot; also needs to be updated such that a proper error can\nbe returned to the caller, sendmsg. It fails to allocate psock-\u0026gt;cork.\nNothing has been corked so far, so this patch simply sets \u0026quot;*copied\u0026quot;\nto 0.\n\n[0]:\nWARNING: net/ipv4/af_inet.c:156 at inet_sock_destruct+0x623/0x730 net/ipv4/af_inet.c:156, CPU#1: syz-executor/5983\nModules linked in:\nCPU: 1 UID: 0 PID: 5983 Comm: syz-executor Not tainted syzkaller #0 PREEMPT(full)\nHardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 07/12/2025\nRIP: 0010:inet_sock_destruct+0x623/0x730 net/ipv4/af_inet.c:156\nCode: 0f 0b 90 e9 62 fe ff ff e8 7a db b5 f7 90 0f 0b 90 e9 95 fe ff ff e8 6c db b5 f7 90 0f 0b 90 e9 bb fe ff ff e8 5e db b5 f7 90 \u0026lt;0f\u0026gt; 0b 90 e9 e1 fe ff ff 89 f9 80 e1 07 80 c1 03 38 c1 0f 8c 9f fc\nRSP: 0018:ffffc90000a08b48 EFLAGS: 00010246\nRAX: ffffffff8a09d0b2 RBX: dffffc0000000000 RCX: ffff888024a23c80\nRDX: 0000000000000100 RSI: 0000000000000fff RDI: 0000000000000000\nRBP: 0000000000000fff R08: ffff88807e07c627 R09: 1ffff1100fc0f8c4\nR10: dffffc0000000000 R11: ffffed100fc0f8c5 R12: ffff88807e07c380\nR13: dffffc0000000000 R14: ffff88807e07c60c R15: 1ffff1100fc0f872\nFS:  00005555604c4500(0000) GS:ffff888125af1000(0000) knlGS:0000000000000000\nCS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033\nCR2: 00005555604df5c8 CR3: 0000000032b06000 CR4: 00000000003526f0\nCall Trace:\n \u0026lt;IRQ\u0026gt;\n __sk_destruct+0x86/0x660 net/core/sock.c:2339\n rcu_do_batch kernel/rcu/tree.c:2605 [inline]\n rcu_core+0xca8/0x1770 kernel/rcu/tree.c:2861\n handle_softirqs+0x286/0x870 kernel/softirq.c:579\n __do_softirq kernel/softirq.c:613 [inline]\n invoke_softirq kernel/softirq.c:453 [inline]\n __irq_exit_rcu+0xca/0x1f0 kernel/softirq.c:680\n irq_exit_rcu+0x9/0x30 kernel/softirq.c:696\n instr_sysvec_apic_timer_interrupt arch/x86/kernel/apic/apic.c:1052 [inline]\n sysvec_apic_timer_interrupt+0xa6/0xc0 arch/x86/kernel/apic/apic.c:1052\n \u0026lt;/IRQ\u0026gt;(CVE-2025-39913)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ncnic: Fix use-after-free bugs in cnic_delete_task\n\nThe original code uses cancel_delayed_work() in cnic_cm_stop_bnx2x_hw(),\nwhich does not guarantee that the delayed work item \u0026apos;delete_task\u0026apos; has\nfully completed if it was already running. Additionally, the delayed work\nitem is cyclic, the flush_workqueue() in cnic_cm_stop_bnx2x_hw() only\nblocks and waits for work items that were already queued to the\nworkqueue prior to its invocation. Any work items submitted after\nflush_workqueue() is called are not included in the set of tasks that the\nflush operation awaits. This means that after the cyclic work items have\nfinished executing, a delayed work item may still exist in the workqueue.\nThis leads to use-after-free scenarios where the cnic_dev is deallocated\nby cnic_free_dev(), while delete_task remains active and attempt to\ndereference cnic_dev in cnic_delete_task().\n\nA typical race condition is illustrated below:\n\nCPU 0 (cleanup)              | CPU 1 (delayed work callback)\ncnic_netdev_event()          |\n  cnic_stop_hw()             | cnic_delete_task()\n    cnic_cm_stop_bnx2x_hw()  | ...\n      cancel_delayed_work()  | /* the queue_delayed_work()\n      flush_workqueue()      |    executes after flush_workqueue()*/\n                             | queue_delayed_work()\n  cnic_free_dev(dev)//free   | cnic_delete_task() //new instance\n                             |   dev = cp-\u0026gt;dev; //use\n\nReplace cancel_delayed_work() with cancel_delayed_work_sync() to ensure\nthat the cyclic delayed work item is properly canceled and that any\nongoing execution of the work item completes before the cnic_dev is\ndeallocated. Furthermore, since cancel_delayed_work_sync() uses\n__flush_work(work, true) to synchronously wait for any currently\nexecuting instance of the work item to finish, the flush_workqueue()\nbecomes redundant and should be removed.\n\nThis bug was identified through static analysis. To reproduce the issue\nand validate the fix, I simulated the cnic PCI device in QEMU and\nintroduced intentional delays — such as inserting calls to ssleep()\nwithin the cnic_delete_task() function — to increase the likelihood\nof triggering the bug.(CVE-2025-39945)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nipvs: Defer ip_vs_ftp unregister during netns cleanup\n\nOn the netns cleanup path, __ip_vs_ftp_exit() may unregister ip_vs_ftp\nbefore connections with valid cp-\u0026gt;app pointers are flushed, leading to a\nuse-after-free.\n\nFix this by introducing a global `exiting_module` flag, set to true in\nip_vs_ftp_exit() before unregistering the pernet subsystem. In\n__ip_vs_ftp_exit(), skip ip_vs_ftp unregister if called during netns\ncleanup (when exiting_module is false) and defer it to\n__ip_vs_cleanup_batch(), which unregisters all apps after all connections\nare flushed. If called during module exit, unregister ip_vs_ftp\nimmediately.(CVE-2025-40018)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nvfs: Don\u0026apos;t leak disconnected dentries on umount\n\nWhen user calls open_by_handle_at() on some inode that is not cached, we\nwill create disconnected dentry for it. If such dentry is a directory,\nexportfs_decode_fh_raw() will then try to connect this dentry to the\ndentry tree through reconnect_path(). It may happen for various reasons\n(such as corrupted fs or race with rename) that the call to\nlookup_one_unlocked() in reconnect_one() will fail to find the dentry we\nare trying to reconnect and instead create a new dentry under the\nparent. Now this dentry will not be marked as disconnected although the\nparent still may well be disconnected (at least in case this\ninconsistency happened because the fs is corrupted and .. doesn\u0026apos;t point\nto the real parent directory). This creates inconsistency in\ndisconnected flags but AFAICS it was mostly harmless. At least until\ncommit f1ee616214cb (\u0026quot;VFS: don\u0026apos;t keep disconnected dentries on d_anon\u0026quot;)\nwhich removed adding of most disconnected dentries to sb-\u0026gt;s_anon list.\nThus after this commit cleanup of disconnected dentries implicitely\nrelies on the fact that dput() will immediately reclaim such dentries.\nHowever when some leaf dentry isn\u0026apos;t marked as disconnected, as in the\nscenario described above, the reclaim doesn\u0026apos;t happen and the dentries\nare \u0026quot;leaked\u0026quot;. Memory reclaim can eventually reclaim them but otherwise\nthey stay in memory and if umount comes first, we hit infamous \u0026quot;Busy\ninodes after unmount\u0026quot; bug. Make sure all dentries created under a\ndisconnected parent are marked as disconnected as well.(CVE-2025-40105)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nxfrm: delete x-\u0026gt;tunnel as we delete x\n\nThe ipcomp fallback tunnels currently get deleted (from the various\nlists and hashtables) as the last user state that needed that fallback\nis destroyed (not deleted). If a reference to that user state still\nexists, the fallback state will remain on the hashtables/lists,\ntriggering the WARN in xfrm_state_fini. Because of those remaining\nreferences, the fix in commit f75a2804da39 (\u0026quot;xfrm: destroy xfrm_state\nsynchronously on net exit path\u0026quot;) is not complete.\n\nWe recently fixed one such situation in TCP due to defered freeing of\nskbs (commit 9b6412e6979f (\u0026quot;tcp: drop secpath at the same time as we\ncurrently drop dst\u0026quot;)). This can also happen due to IP reassembly: skbs\nwith a secpath remain on the reassembly queue until netns\ndestruction. If we can\u0026apos;t guarantee that the queues are flushed by the\ntime xfrm_state_fini runs, there may still be references to a (user)\nxfrm_state, preventing the timely deletion of the corresponding\nfallback state.\n\nInstead of chasing each instance of skbs holding a secpath one by one,\nthis patch fixes the issue directly within xfrm, by deleting the\nfallback state as soon as the last user state depending on it has been\ndeleted. Destruction will still happen when the final reference is\ndropped.\n\nA separate lockdep class for the fallback state is required since\nwe\u0026apos;re going to lock x-\u0026gt;tunnel while x is locked.(CVE-2025-40215)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nfs/proc: fix uaf in proc_readdir_de()\n\nPde is erased from subdir rbtree through rb_erase(), but not set the node\nto EMPTY, which may result in uaf access.  We should use RB_CLEAR_NODE()\nset the erased node to EMPTY, then pde_subdir_next() will return NULL to\navoid uaf access.\n\nWe found an uaf issue while using stress-ng testing, need to run testcase\ngetdent and tun in the same time.  The steps of the issue is as follows:\n\n1) use getdent to traverse dir /proc/pid/net/dev_snmp6/, and current\n   pde is tun3;\n\n2) in the [time windows] unregister netdevice tun3 and tun2, and erase\n   them from rbtree.  erase tun3 first, and then erase tun2.  the\n   pde(tun2) will be released to slab;\n\n3) continue to getdent process, then pde_subdir_next() will return\n   pde(tun2) which is released, it will case uaf access.\n\nCPU 0                                      |    CPU 1\n-------------------------------------------------------------------------\ntraverse dir /proc/pid/net/dev_snmp6/      |   unregister_netdevice(tun-\u0026gt;dev)   //tun3 tun2\nsys_getdents64()                           |\n  iterate_dir()                            |\n    proc_readdir()                         |\n      proc_readdir_de()                    |     snmp6_unregister_dev()\n        pde_get(de);                       |       proc_remove()\n        read_unlock(\u0026amp;proc_subdir_lock);    |         remove_proc_subtree()\n                                           |           write_lock(\u0026amp;proc_subdir_lock);\n        [time window]                      |           rb_erase(\u0026amp;root-\u0026gt;subdir_node, \u0026amp;parent-\u0026gt;subdir);\n                                           |           write_unlock(\u0026amp;proc_subdir_lock);\n        read_lock(\u0026amp;proc_subdir_lock);      |\n        next = pde_subdir_next(de);        |\n        pde_put(de);                       |\n        de = next;    //UAF                |\n\nrbtree of dev_snmp6\n                        |\n                    pde(tun3)\n                     /    \\\n                  NULL  pde(tun2)(CVE-2025-40271)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ntipc: Fix use-after-free in tipc_mon_reinit_self().\n\nsyzbot reported use-after-free of tipc_net(net)-\u0026gt;monitors[]\nin tipc_mon_reinit_self(). [0]\n\nThe array is protected by RTNL, but tipc_mon_reinit_self()\niterates over it without RTNL.\n\ntipc_mon_reinit_self() is called from tipc_net_finalize(),\nwhich is always under RTNL except for tipc_net_finalize_work().\n\nLet\u0026apos;s hold RTNL in tipc_net_finalize_work().\n\n[0]:\nBUG: KASAN: slab-use-after-free in __raw_spin_lock_irqsave include/linux/spinlock_api_smp.h:110 [inline]\nBUG: KASAN: slab-use-after-free in _raw_spin_lock_irqsave+0xa7/0xf0 kernel/locking/spinlock.c:162\nRead of size 1 at addr ffff88805eae1030 by task kworker/0:7/5989\n\nCPU: 0 UID: 0 PID: 5989 Comm: kworker/0:7 Not tainted syzkaller #0 PREEMPT_{RT,(full)}\nHardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 08/18/2025\nWorkqueue: events tipc_net_finalize_work\nCall Trace:\n \u0026lt;TASK\u0026gt;\n dump_stack_lvl+0x189/0x250 lib/dump_stack.c:120\n print_address_description mm/kasan/report.c:378 [inline]\n print_report+0xca/0x240 mm/kasan/report.c:482\n kasan_report+0x118/0x150 mm/kasan/report.c:595\n __kasan_check_byte+0x2a/0x40 mm/kasan/common.c:568\n kasan_check_byte include/linux/kasan.h:399 [inline]\n lock_acquire+0x8d/0x360 kernel/locking/lockdep.c:5842\n __raw_spin_lock_irqsave include/linux/spinlock_api_smp.h:110 [inline]\n _raw_spin_lock_irqsave+0xa7/0xf0 kernel/locking/spinlock.c:162\n rtlock_slowlock kernel/locking/rtmutex.c:1894 [inline]\n rwbase_rtmutex_lock_state kernel/locking/spinlock_rt.c:160 [inline]\n rwbase_write_lock+0xd3/0x7e0 kernel/locking/rwbase_rt.c:244\n rt_write_lock+0x76/0x110 kernel/locking/spinlock_rt.c:243\n write_lock_bh include/linux/rwlock_rt.h:99 [inline]\n tipc_mon_reinit_self+0x79/0x430 net/tipc/monitor.c:718\n tipc_net_finalize+0x115/0x190 net/tipc/net.c:140\n process_one_work kernel/workqueue.c:3236 [inline]\n process_scheduled_works+0xade/0x17b0 kernel/workqueue.c:3319\n worker_thread+0x8a0/0xda0 kernel/workqueue.c:3400\n kthread+0x70e/0x8a0 kernel/kthread.c:463\n ret_from_fork+0x439/0x7d0 arch/x86/kernel/process.c:148\n ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:245\n \u0026lt;/TASK\u0026gt;\n\nAllocated by task 6089:\n kasan_save_stack mm/kasan/common.c:47 [inline]\n kasan_save_track+0x3e/0x80 mm/kasan/common.c:68\n poison_kmalloc_redzone mm/kasan/common.c:388 [inline]\n __kasan_kmalloc+0x93/0xb0 mm/kasan/common.c:405\n kasan_kmalloc include/linux/kasan.h:260 [inline]\n __kmalloc_cache_noprof+0x1a8/0x320 mm/slub.c:4407\n kmalloc_noprof include/linux/slab.h:905 [inline]\n kzalloc_noprof include/linux/slab.h:1039 [inline]\n tipc_mon_create+0xc3/0x4d0 net/tipc/monitor.c:657\n tipc_enable_bearer net/tipc/bearer.c:357 [inline]\n __tipc_nl_bearer_enable+0xe16/0x13f0 net/tipc/bearer.c:1047\n __tipc_nl_compat_doit net/tipc/netlink_compat.c:371 [inline]\n tipc_nl_compat_doit+0x3bc/0x5f0 net/tipc/netlink_compat.c:393\n tipc_nl_compat_handle net/tipc/netlink_compat.c:-1 [inline]\n tipc_nl_compat_recv+0x83c/0xbe0 net/tipc/netlink_compat.c:1321\n genl_family_rcv_msg_doit+0x215/0x300 net/netlink/genetlink.c:1115\n genl_family_rcv_msg net/netlink/genetlink.c:1195 [inline]\n genl_rcv_msg+0x60e/0x790 net/netlink/genetlink.c:1210\n netlink_rcv_skb+0x208/0x470 net/netlink/af_netlink.c:2552\n genl_rcv+0x28/0x40 net/netlink/genetlink.c:1219\n netlink_unicast_kernel net/netlink/af_netlink.c:1320 [inline]\n netlink_unicast+0x846/0xa10 net/netlink/af_netlink.c:1346\n netlink_sendmsg+0x805/0xb30 net/netlink/af_netlink.c:1896\n sock_sendmsg_nosec net/socket.c:714 [inline]\n __sock_sendmsg+0x21c/0x270 net/socket.c:729\n ____sys_sendmsg+0x508/0x820 net/socket.c:2614\n ___sys_sendmsg+0x21f/0x2a0 net/socket.c:2668\n __sys_sendmsg net/socket.c:2700 [inline]\n __do_sys_sendmsg net/socket.c:2705 [inline]\n __se_sys_sendmsg net/socket.c:2703 [inline]\n __x64_sys_sendmsg+0x1a1/0x260 net/socket.c:2703\n do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline]\n do_syscall_64+0xfa/0x3b0 arch/\n---truncated---(CVE-2025-40280)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnvme-fc: use lock accessing port_state and rport state\n\nnvme_fc_unregister_remote removes the remote port on a lport object at\nany point in time when there is no active association. This races with\nwith the reconnect logic, because nvme_fc_create_association is not\ntaking a lock to check the port_state and atomically increase the\nactive count on the rport.(CVE-2025-40342)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\narch_topology: Fix incorrect error check in topology_parse_cpu_capacity()\n\nFix incorrect use of PTR_ERR_OR_ZERO() in topology_parse_cpu_capacity()\nwhich causes the code to proceed with NULL clock pointers. The current\nlogic uses !PTR_ERR_OR_ZERO(cpu_clk) which evaluates to true for both\nvalid pointers and NULL, leading to potential NULL pointer dereference\nin clk_get_rate().\n\nPer include/linux/err.h documentation, PTR_ERR_OR_ZERO(ptr) returns:\n\u0026quot;The error code within @ptr if it is an error pointer; 0 otherwise.\u0026quot;\n\nThis means PTR_ERR_OR_ZERO() returns 0 for both valid pointers AND NULL\npointers. Therefore !PTR_ERR_OR_ZERO(cpu_clk) evaluates to true (proceed)\nwhen cpu_clk is either valid or NULL, causing clk_get_rate(NULL) to be\ncalled when of_clk_get() returns NULL.\n\nReplace with !IS_ERR_OR_NULL(cpu_clk) which only proceeds for valid\npointers, preventing potential NULL pointer dereference in clk_get_rate().(CVE-2025-40346)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnet: usb: qmi_wwan: initialize MAC header offset in qmimux_rx_fixup\n\nRaw IP packets have no MAC header, leaving skb-\u0026gt;mac_header uninitialized.\nThis can trigger kernel panics on ARM64 when xfrm or other subsystems\naccess the offset due to strict alignment checks.\n\nInitialize the MAC header to prevent such crashes.\n\nThis can trigger kernel panics on ARM when running IPsec over the\nqmimux0 interface.\n\nExample trace:\n\n    Internal error: Oops: 000000009600004f [#1] SMP\n    CPU: 0 UID: 0 PID: 0 Comm: swapper/0 Not tainted 6.12.34-gbe78e49cb433 #1\n    Hardware name: LS1028A RDB Board (DT)\n    pstate: 60000005 (nZCv daif -PAN -UAO -TCO -DIT -SSBS BTYPE=--)\n    pc : xfrm_input+0xde8/0x1318\n    lr : xfrm_input+0x61c/0x1318\n    sp : ffff800080003b20\n    Call trace:\n     xfrm_input+0xde8/0x1318\n     xfrm6_rcv+0x38/0x44\n     xfrm6_esp_rcv+0x48/0xa8\n     ip6_protocol_deliver_rcu+0x94/0x4b0\n     ip6_input_finish+0x44/0x70\n     ip6_input+0x44/0xc0\n     ipv6_rcv+0x6c/0x114\n     __netif_receive_skb_one_core+0x5c/0x8c\n     __netif_receive_skb+0x18/0x60\n     process_backlog+0x78/0x17c\n     __napi_poll+0x38/0x180\n     net_rx_action+0x168/0x2f0(CVE-2025-68192)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nlibceph: fix potential use-after-free in have_mon_and_osd_map()\n\nThe wait loop in __ceph_open_session() can race with the client\nreceiving a new monmap or osdmap shortly after the initial map is\nreceived.  Both ceph_monc_handle_map() and handle_one_map() install\na new map immediately after freeing the old one\n\n    kfree(monc-\u0026gt;monmap);\n    monc-\u0026gt;monmap = monmap;\n\n    ceph_osdmap_destroy(osdc-\u0026gt;osdmap);\n    osdc-\u0026gt;osdmap = newmap;\n\nunder client-\u0026gt;monc.mutex and client-\u0026gt;osdc.lock respectively, but\nbecause neither is taken in have_mon_and_osd_map() it\u0026apos;s possible for\nclient-\u0026gt;monc.monmap-\u0026gt;epoch and client-\u0026gt;osdc.osdmap-\u0026gt;epoch arms in\n\n    client-\u0026gt;monc.monmap \u0026amp;\u0026amp; client-\u0026gt;monc.monmap-\u0026gt;epoch \u0026amp;\u0026amp;\n        client-\u0026gt;osdc.osdmap \u0026amp;\u0026amp; client-\u0026gt;osdc.osdmap-\u0026gt;epoch;\n\ncondition to dereference an already freed map.  This happens to be\nreproducible with generic/395 and generic/397 with KASAN enabled:\n\n    BUG: KASAN: slab-use-after-free in have_mon_and_osd_map+0x56/0x70\n    Read of size 4 at addr ffff88811012d810 by task mount.ceph/13305\n    CPU: 2 UID: 0 PID: 13305 Comm: mount.ceph Not tainted 6.14.0-rc2-build2+ #1266\n    ...\n    Call Trace:\n    \u0026lt;TASK\u0026gt;\n    have_mon_and_osd_map+0x56/0x70\n    ceph_open_session+0x182/0x290\n    ceph_get_tree+0x333/0x680\n    vfs_get_tree+0x49/0x180\n    do_new_mount+0x1a3/0x2d0\n    path_mount+0x6dd/0x730\n    do_mount+0x99/0xe0\n    __do_sys_mount+0x141/0x180\n    do_syscall_64+0x9f/0x100\n    entry_SYSCALL_64_after_hwframe+0x76/0x7e\n    \u0026lt;/TASK\u0026gt;\n\n    Allocated by task 13305:\n    ceph_osdmap_alloc+0x16/0x130\n    ceph_osdc_init+0x27a/0x4c0\n    ceph_create_client+0x153/0x190\n    create_fs_client+0x50/0x2a0\n    ceph_get_tree+0xff/0x680\n    vfs_get_tree+0x49/0x180\n    do_new_mount+0x1a3/0x2d0\n    path_mount+0x6dd/0x730\n    do_mount+0x99/0xe0\n    __do_sys_mount+0x141/0x180\n    do_syscall_64+0x9f/0x100\n    entry_SYSCALL_64_after_hwframe+0x76/0x7e\n\n    Freed by task 9475:\n    kfree+0x212/0x290\n    handle_one_map+0x23c/0x3b0\n    ceph_osdc_handle_map+0x3c9/0x590\n    mon_dispatch+0x655/0x6f0\n    ceph_con_process_message+0xc3/0xe0\n    ceph_con_v1_try_read+0x614/0x760\n    ceph_con_workfn+0x2de/0x650\n    process_one_work+0x486/0x7c0\n    process_scheduled_works+0x73/0x90\n    worker_thread+0x1c8/0x2a0\n    kthread+0x2ec/0x300\n    ret_from_fork+0x24/0x40\n    ret_from_fork_asm+0x1a/0x30\n\nRewrite the wait loop to check the above condition directly with\nclient-\u0026gt;monc.mutex and client-\u0026gt;osdc.lock taken as appropriate.  While\nat it, improve the timeout handling (previously mount_timeout could be\nexceeded in case wait_event_interruptible_timeout() slept more than\nonce) and access client-\u0026gt;auth_err under client-\u0026gt;monc.mutex to match\nhow it\u0026apos;s set in finish_auth().\n\nmonmap_show() and osdmap_show() now take the respective lock before\naccessing the map as well.(CVE-2025-68285)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nmedia: dvb-usb: dtv5100: fix out-of-bounds in dtv5100_i2c_msg()\n\nrlen value is a user-controlled value, but dtv5100_i2c_msg() does not\ncheck the size of the rlen value. Therefore, if it is set to a value\nlarger than sizeof(st-\u0026gt;data), an out-of-bounds vuln occurs for st-\u0026gt;data.\n\nTherefore, we need to add proper range checking to prevent this vuln.(CVE-2025-68819)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nRDMA/cm: Fix leaking the multicast GID table reference\n\nIf the CM ID is destroyed while the CM event for multicast creating is\nstill queued the cancel_work_sync() will prevent the work from running\nwhich also prevents destroying the ah_attr. This leaks a refcount and\ntriggers a WARN:\n\n   GID entry ref leak for dev syz1 index 2 ref=573\n   WARNING: CPU: 1 PID: 655 at drivers/infiniband/core/cache.c:809 release_gid_table drivers/infiniband/core/cache.c:806 [inline]\n   WARNING: CPU: 1 PID: 655 at drivers/infiniband/core/cache.c:809 gid_table_release_one+0x284/0x3cc drivers/infiniband/core/cache.c:886\n\nDestroy the ah_attr after canceling the work, it is safe to call this\ntwice.(CVE-2025-71084)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nteam: fix check for port enabled in team_queue_override_port_prio_changed()\n\nThere has been a syzkaller bug reported recently with the following\ntrace:\n\nlist_del corruption, ffff888058bea080-\u0026gt;prev is LIST_POISON2 (dead000000000122)\n------------[ cut here ]------------\nkernel BUG at lib/list_debug.c:59!\nOops: invalid opcode: 0000 [#1] SMP KASAN NOPTI\nCPU: 3 UID: 0 PID: 21246 Comm: syz.0.2928 Not tainted syzkaller #0 PREEMPT(full)\nHardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.16.3-debian-1.16.3-2~bpo12+1 04/01/2014\nRIP: 0010:__list_del_entry_valid_or_report+0x13e/0x200 lib/list_debug.c:59\nCode: 48 c7 c7 e0 71 f0 8b e8 30 08 ef fc 90 0f 0b 48 89 ef e8 a5 02 55 fd 48 89 ea 48 89 de 48 c7 c7 40 72 f0 8b e8 13 08 ef fc 90 \u0026lt;0f\u0026gt; 0b 48 89 ef e8 88 02 55 fd 48 89 ea 48 b8 00 00 00 00 00 fc ff\nRSP: 0018:ffffc9000d49f370 EFLAGS: 00010286\nRAX: 000000000000004e RBX: ffff888058bea080 RCX: ffffc9002817d000\nRDX: 0000000000000000 RSI: ffffffff819becc6 RDI: 0000000000000005\nRBP: dead000000000122 R08: 0000000000000005 R09: 0000000000000000\nR10: 0000000080000000 R11: 0000000000000001 R12: ffff888039e9c230\nR13: ffff888058bea088 R14: ffff888058bea080 R15: ffff888055461480\nFS:  00007fbbcfe6f6c0(0000) GS:ffff8880d6d0a000(0000) knlGS:0000000000000000\nCS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033\nCR2: 000000110c3afcb0 CR3: 00000000382c7000 CR4: 0000000000352ef0\nCall Trace:\n \u0026lt;TASK\u0026gt;\n __list_del_entry_valid include/linux/list.h:132 [inline]\n __list_del_entry include/linux/list.h:223 [inline]\n list_del_rcu include/linux/rculist.h:178 [inline]\n __team_queue_override_port_del drivers/net/team/team_core.c:826 [inline]\n __team_queue_override_port_del drivers/net/team/team_core.c:821 [inline]\n team_queue_override_port_prio_changed drivers/net/team/team_core.c:883 [inline]\n team_priority_option_set+0x171/0x2f0 drivers/net/team/team_core.c:1534\n team_option_set drivers/net/team/team_core.c:376 [inline]\n team_nl_options_set_doit+0x8ae/0xe60 drivers/net/team/team_core.c:2653\n genl_family_rcv_msg_doit+0x209/0x2f0 net/netlink/genetlink.c:1115\n genl_family_rcv_msg net/netlink/genetlink.c:1195 [inline]\n genl_rcv_msg+0x55c/0x800 net/netlink/genetlink.c:1210\n netlink_rcv_skb+0x158/0x420 net/netlink/af_netlink.c:2552\n genl_rcv+0x28/0x40 net/netlink/genetlink.c:1219\n netlink_unicast_kernel net/netlink/af_netlink.c:1320 [inline]\n netlink_unicast+0x5aa/0x870 net/netlink/af_netlink.c:1346\n netlink_sendmsg+0x8c8/0xdd0 net/netlink/af_netlink.c:1896\n sock_sendmsg_nosec net/socket.c:727 [inline]\n __sock_sendmsg net/socket.c:742 [inline]\n ____sys_sendmsg+0xa98/0xc70 net/socket.c:2630\n ___sys_sendmsg+0x134/0x1d0 net/socket.c:2684\n __sys_sendmsg+0x16d/0x220 net/socket.c:2716\n do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline]\n do_syscall_64+0xcd/0xfa0 arch/x86/entry/syscall_64.c:94\n entry_SYSCALL_64_after_hwframe+0x77/0x7f\n\nThe problem is in this flow:\n1) Port is enabled, queue_id != 0, in qom_list\n2) Port gets disabled\n        -\u0026gt; team_port_disable()\n        -\u0026gt; team_queue_override_port_del()\n        -\u0026gt; del (removed from list)\n3) Port is disabled, queue_id != 0, not in any list\n4) Priority changes\n        -\u0026gt; team_queue_override_port_prio_changed()\n        -\u0026gt; checks: port disabled \u0026amp;\u0026amp; queue_id != 0\n        -\u0026gt; calls del - hits the BUG as it is removed already\n\nTo fix this, change the check in team_queue_override_port_prio_changed()\nso it returns early if port is not enabled.(CVE-2025-71091)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nSUNRPC: svcauth_gss: avoid NULL deref on zero length gss_token in gss_read_proxy_verf\n\nA zero length gss_token results in pages == 0 and in_token-\u0026gt;pages[0]\nis NULL. The code unconditionally evaluates\npage_address(in_token-\u0026gt;pages[0]) for the initial memcpy, which can\ndereference NULL even when the copy length is 0. Guard the first\nmemcpy so it only runs when length \u0026gt; 0.(CVE-2025-71120)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnvme-tcp: fix NULL pointer dereferences in nvmet_tcp_build_pdu_iovec\n\nCommit efa56305908b (\u0026quot;nvmet-tcp: Fix a kernel panic when host sends an invalid H2C PDU length\u0026quot;)\nadded ttag bounds checking and data_offset\nvalidation in nvmet_tcp_handle_h2c_data_pdu(), but it did not validate\nwhether the command\u0026apos;s data structures (cmd-\u0026gt;req.sg and cmd-\u0026gt;iov) have\nbeen properly initialized before processing H2C_DATA PDUs.\n\nThe nvmet_tcp_build_pdu_iovec() function dereferences these pointers\nwithout NULL checks. This can be triggered by sending H2C_DATA PDU\nimmediately after the ICREQ/ICRESP handshake, before\nsending a CONNECT command or NVMe write command.\n\nAttack vectors that trigger NULL pointer dereferences:\n1. H2C_DATA PDU sent before CONNECT → both pointers NULL\n2. H2C_DATA PDU for READ command → cmd-\u0026gt;req.sg allocated, cmd-\u0026gt;iov NULL\n3. H2C_DATA PDU for uninitialized command slot → both pointers NULL\n\nThe fix validates both cmd-\u0026gt;req.sg and cmd-\u0026gt;iov before calling\nnvmet_tcp_build_pdu_iovec(). Both checks are required because:\n- Uninitialized commands: both NULL\n- READ commands: cmd-\u0026gt;req.sg allocated, cmd-\u0026gt;iov NULL\n- WRITE commands: both allocated(CVE-2026-22998)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\npnfs/flexfiles: Fix memory leak in nfs4_ff_alloc_deviceid_node()\n\nIn nfs4_ff_alloc_deviceid_node(), if the allocation for ds_versions fails,\nthe function jumps to the out_scratch label without freeing the already\nallocated dsaddrs list, leading to a memory leak.\n\nFix this by jumping to the out_err_drain_dsaddrs label, which properly\nfrees the dsaddrs list before cleaning up other resources.(CVE-2026-23038)","status":"published","published":"2026-02-13T11:10:22Z","modified":"2026-08-18T01:19:33.608094161Z","cvss":[{"version":"3.1","score":7.8,"vector":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H","level":"high"}],"updated_at":"2026-11-02T15:52:45.721983Z"},{"id":"RHSA-2023:2458","title":"Red Hat Security Advisory: kernel security, bug fix, and enhancement update","status":"published","published":"2024-09-16T09:02:33Z","modified":"2026-10-17T10:01:49Z","cvss":[{"version":"3.1","score":8.1,"vector":"CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N","level":"high"}],"updated_at":"2026-11-02T15:53:10.611604Z"},{"id":"ROOT-OS-DEBIAN-11-CVE-2022-50151","title":"CVE-2022-50151 in linux - Patched by Root","description":"Root has patched CVE-2022-50151 in the linux package for Root:Debian:11. Multiple fixed versions available.","status":"published","published":"2026-08-23T09:13:41Z","modified":"2026-08-23T10:15:44.766307836Z","cvss":[{"version":"3.1","score":7.8,"vector":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H","level":"high"}],"updated_at":"2026-11-02T15:53:28.80888Z"},{"id":"UBUNTU-CVE-2022-50151","description":"In the Linux kernel, the following vulnerability has been resolved: usb: cdns3: fix random warning message when driver load Warning log: [    4.141392] Unexpected gfp: 0x4 (GFP_DMA32). Fixing up to gfp: 0xa20 (GFP_ATOMIC). Fix your code! [    4.150340] CPU: 1 PID: 175 Comm: 1-0050 Not tainted 5.15.5-00039-g2fd9ae1b568c #20 [    4.158010] Hardware name: Freescale i.MX8QXP MEK (DT) [    4.163155] Call trace: [    4.165600]  dump_backtrace+0x0/0x1b0 [    4.169286]  show_stack+0x18/0x68 [    4.172611]  dump_stack_lvl+0x68/0x84 [    4.176286]  dump_stack+0x18/0x34 [    4.179613]  kmalloc_fix_flags+0x60/0x88 [    4.183550]  new_slab+0x334/0x370 [    4.186878]  ___slab_alloc.part.108+0x4d4/0x748 [    4.191419]  __slab_alloc.isra.109+0x30/0x78 [    4.195702]  kmem_cache_alloc+0x40c/0x420 [    4.199725]  dma_pool_alloc+0xac/0x1f8 [    4.203486]  cdns3_allocate_trb_pool+0xb4/0xd0 pool_alloc_page(struct dma_pool *pool, gfp_t mem_flags) { \t... \tpage = kmalloc(sizeof(*page), mem_flags); \tpage-\u003evaddr = dma_alloc_coherent(pool-\u003edev, pool-\u003eallocation, \t\t\t\t\t \u0026page-\u003edma, mem_flags); \t... } kmalloc was called with mem_flags, which is passed down in cdns3_allocate_trb_pool() and have GFP_DMA32 flags. kmall_fix_flags() report warning. GFP_DMA32 is not useful at all. dma_alloc_coherent() will handle DMA memory region correctly by pool-\u003edev. GFP_DMA32 can be removed safely.","status":"published","published":"2025-06-18T11:15:00Z","modified":"2026-09-09T14:33:59.327566993Z","cvss":[{"version":"3.1","score":7.8,"vector":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H","level":"high"}],"updated_at":"2026-11-02T16:54:09.234424Z"},{"id":"CLSA-2026-1789958474","title":"Fix of 167 CVEs","description":"   * CVE-2025-39826\n     - net: rose: convert 'use' field to refcount_t {CVE-2025-39826}\n   * CVE-2025-40146\n     - blk-mq: fix potential deadlock while nr_requests grown {CVE-2025-40146}\n   * CVE-2024-53216\n     - nfsd: release svc_expkey/svc_export with rcu_work {CVE-2024-53216}\n   * CVE-2026-89778\n     - isofs: fix out-of-bounds page array access on empty zisofs block\n       {CVE-2026-89778}\n   * CVE-2026-23050\n     - pNFS: Fix a deadlock when returning a delegation during open()\n       {CVE-2026-23050}\n   * CVE-2025-68796\n     - f2fs: fix to avoid updating zero-sized extent in extent cache\n       {CVE-2025-68796}\n   * CVE-2025-68330\n     - iio: accel: bmc150: Fix irq assumption regression {CVE-2025-68330}\n   * CVE-2025-40333\n     - f2fs: fix infinite loop in __insert_extent_tree() {CVE-2025-40333}\n   * CVE-2025-40160\n     - xen/events: Return -EEXIST for bound VIRQs {CVE-2025-40160}\n   * CVE-2023-54047\n     - drm/rockchip: dw_hdmi: cleanup drm encoder during unbind {CVE-2023-54047}\n   * CVE-2025-68190\n     - drm/amdgpu/atom: Check kcalloc() for WS buffer in\n       amdgpu_atom_execute_table_locked() {CVE-2025-68190}\n   * CVE-2025-68188\n     - tcp: use dst_dev_rcu() in tcp_fastopen_active_disable_ofo_check()\n       {CVE-2025-68188}\n   * CVE-2026-89786\n     - ext4: fix out-of-bounds read in ext4_read_inline_dir() {CVE-2026-89786}\n   * CVE-2022-50764\n     - ipv6/sit: use DEV_STATS_INC() to avoid data-races {CVE-2022-50764}\n   * CVE-2026-80785\n     - fbdev: serialize mode sysfs access with lock_fb_info() {CVE-2026-80785}\n   * CVE-2026-80788\n     - nvmet-tcp: Do not WARN on remotely-controlled oversized SGL allocations\n       {CVE-2026-80788}\n   * CVE-2026-80747\n     - drm/amdkfd: Add bounds check for CRAT subtype length {CVE-2026-80747}\n   * CVE-2026-80907\n     - drm/amdgpu: Fix UVD dpb min size calculation for H264 {CVE-2026-80907}\n   * CVE-2026-80908\n     - drm/amdgpu: Reject UVD message with dimensions above 4096 {CVE-2026-80908}\n   * CVE-2026-80812\n     - ALSA: dummy: Check card index validity at probe {CVE-2026-80812}\n   * CVE-2026-80948\n     - wifi: iwlwifi: dvm: fix memory leak in iwl_op_mode_dvm_start()\n       {CVE-2026-80948}\n   * CVE-2025-40137\n     - f2fs: fix to truncate first page in error path of f2fs_truncate()\n       {CVE-2025-40137}\n   * CVE-2023-54150\n     - drm/amd: Fix an out of bounds error in BIOS parser {CVE-2023-54150}\n   * CVE-2026-89784\n     - SUNRPC: check rpc_sockaddr2uaddr() return value in rpcb_register_inet4/6\n       {CVE-2026-89784}\n   * CVE-2026-89783\n     - xfrm6: fix out-of-bounds write in xfrm6_input_addr() when secpath is full\n       {CVE-2026-89783}\n   * CVE-2026-89780\n     - net: qualcomm: rmnet: restore skb-\u003edev on deaggregated frames\n       {CVE-2026-89780}\n   * CVE-2026-89777\n     - vfio/pci: clear vdev-\u003emsi_perm after freeing it on init failure\n       {CVE-2026-89777}\n   * CVE-2026-89789\n     - gtp: add synchronize_net() in gtp_newlink() error path to prevent\n       use-after-free {CVE-2026-89789}\n   * CVE-2025-68797\n     - char: applicom: fix NULL pointer dereference in ac_ioctl {CVE-2025-68797}\n   * CVE-2025-68767\n     - hfsplus: Verify inode mode when loading from disk {CVE-2025-68767}\n   * CVE-2026-63961\n     - usb: typec: altmodes/displayport: validate count before reading Status\n       Update VDO {CVE-2026-63961}\n   * CVE-2026-63904\n     - usb: usbtmc: check URB actual_length for interrupt-IN notifications\n       {CVE-2026-63904}\n   * CVE-2022-50864\n     - nilfs2: fix shift-out-of-bounds due to too large exponent of block size\n       {CVE-2022-50864}\n   * CVE-2025-68771\n     - ocfs2: fix kernel BUG in ocfs2_find_victim_chain {CVE-2025-68771}\n   * CVE-2025-68750\n     - usb: potential integer overflow in usbg_make_tpg() {CVE-2025-68750}\n   * CVE-2026-80909\n     - drm/amdgpu: Reject UVD message with invalid number of h265 refs\n       {CVE-2026-80909}\n   * CVE-2026-74402\n     - crypto: atmel-sha204a - fix blocking and non-blocking rng logic\n       {CVE-2026-74402}\n   * CVE-2026-80844\n     - xfrm: ah6: validate routing header segments_left {CVE-2026-80844}\n   * CVE-2026-80732\n     - ata: pata_sl82c105: fix bridge revision use-after-free {CVE-2026-80732}\n   * CVE-2026-80823\n     - nfc: st21nfca: validate ATR_REQ length against the received frame\n       {CVE-2026-80823}\n   * CVE-2026-89733\n     - usb: gadget: uvc: fix dangling pointers in uvc_function_bind() and\n       uvc_function_unbind() {CVE-2026-89733}\n   * CVE-2026-80570\n     - Input: synaptics-rmi4 - zero report size on F54 work error\n       {CVE-2026-80570}\n   * CVE-2026-80600\n     - batman-adv: dat: acquire ARP hw source only after skb realloc\n       {CVE-2026-80600}\n   * CVE-2026-74580\n     - vhost: reset the vring metadata cache on vring reconfiguration\n       {CVE-2026-74580}\n   * CVE-2026-74609\n     - tipc: read le-\u003elink under the node lock in tipc_node_link_down()\n       {CVE-2026-74609}\n   * CVE-2026-68188\n     - Bluetooth: RFCOMM: Fix session UAF in set_termios {CVE-2026-68188}\n   * CVE-2026-74505\n     - ALSA: 6fire: Fix UAF at error handling during probe {CVE-2026-74505}\n   * CVE-2026-74583\n     - net/sched: cls_route: fix fastmap use-after-free on filter\n       {CVE-2026-74583}\n   * CVE-2026-72299\n     - tipc: restrict socket queue dumps in enqueue tracepoints {CVE-2026-72299}\n   * CVE-2026-89607\n     - ecryptfs: reject oversized encrypted_key_size in parse_tag_3_packet\n       {CVE-2026-89607}\n   * CVE-2026-74444\n     - drm/vmwgfx: validate DRAW_PRIMITIVES header size before division\n       {CVE-2026-74444}\n   * CVE-2026-72234\n     - batman-adv: access unicast_ttvn skb-\u003edata only after skb realloc\n       {CVE-2026-72234}\n   * CVE-2026-68357\n     - watchdog: pretimeout: Fix UAF in watchdog_unregister_governor()\n       {CVE-2026-68357}\n   * CVE-2026-74588\n     - sctp: keep chunk-\u003etransport in step with the list it is queued on\n       {CVE-2026-74588}\n   * CVE-2026-74548\n     - forcedeth: fix UAF of txrx_stats in nv_remove {CVE-2026-74548}\n   * CVE-2026-64563\n     - rhashtable: clear stale iter-\u003ep on table restart {CVE-2026-64563}\n   * CVE-2026-68373\n     - wifi: at76c50x-usb: avoid length underflow in at76_guess_freq()\n       {CVE-2026-68373}\n   * CVE-2026-74556\n     - scsi: libiscsi_tcp: Bound SCSI Response data segment to the connection\n       buffer {CVE-2026-74556}\n   * CVE-2026-68158\n     - libceph: Fix multiplication overflow in decode_new_up_state_weight()\n       {CVE-2026-68158}\n   * CVE-2026-74656\n     - ipv4: fix use-after-free in fib_nhc_update_mtu() {CVE-2026-74656}\n   * CVE-2026-64483\n     - ALSA: firewire: isight: bound the sample count to the packet payload\n       {CVE-2026-64483}\n   * CVE-2026-63814\n     - f2fs: validate ACL entry sizes in f2fs_acl_from_disk() {CVE-2026-63814}\n   * CVE-2026-64505\n     - usb: gadget: function: rndis: add length check for header {CVE-2026-64505}\n   * CVE-2026-63823\n     - keys: Pin request_key_auth payload in instantiate paths {CVE-2026-63823}\n   * CVE-2026-72233\n     - batman-adv: bla: reacquire gw address after skb realloc {CVE-2026-72233}\n   * CVE-2026-68121\n     - pppoe: reload header pointer after dev_hard_header() {CVE-2026-68121}\n   * CVE-2026-74660\n     - netfilter: ebt_nflog: pin the NFLOG backend {CVE-2026-74660}\n   * CVE-2026-74255\n     - tipc: fix UAF in tipc_l2_send_msg() {CVE-2026-74255}\n   * CVE-2026-64504\n     - iio: accel: bmc150: clamp the device-reported FIFO frame count\n       {CVE-2026-64504}\n   * CVE-2026-72047\n     - ieee802154: ca8210: fix pointer truncation in kfifo on 64-bit\n       {CVE-2026-72047}\n   * CVE-2026-68214\n     - media: rtl2832: fix use-after-free in rtl2832_remove() {CVE-2026-68214}\n   * CVE-2026-68402\n     - wifi: cfg80211: bound element ID read when checking non-inheritance\n       {CVE-2026-68402}\n   * CVE-2026-72351\n     - gue: validate REMCSUM private option length {CVE-2026-72351}\n   * CVE-2026-72171\n     - mtd: slram: remove failed entries from the device list {CVE-2026-72171}\n   * CVE-2026-68144\n     - phonet: pep: fix use-after-free in pep_get_sb() {CVE-2026-68144}\n   * CVE-2026-74667\n     - net/packet: reset the MAC header on the packet-socket transmit path\n       {CVE-2026-74667}\n   * CVE-2026-80601\n     - batman-adv: gw: acquire ethernet header only after skb realloc\n       {CVE-2026-80601}\n   * CVE-2026-68377\n     - net/sched: act_tunnel_key: Defer dst_release to RCU callback\n       {CVE-2026-68377}\n   * CVE-2026-72374\n     - afs: Fix callback service message parsers to pass through -EAGAIN\n       {CVE-2026-72374}\n   * CVE-2026-74705\n     - udp: fix potential use-after-free in tunnel segmentation {CVE-2026-74705}\n   * CVE-2026-74630\n     - ipv6: prevent in6_dev_get() from resurrecting inet6_dev {CVE-2026-74630}\n   * CVE-2026-74679\n     - usb: gadget: f_ncm: Use unsigned int for ndp_index {CVE-2026-74679}\n   * CVE-2026-68153\n     - libceph: remove debugfs files before client teardown {CVE-2026-68153}\n   * CVE-2026-72083\n     - scsi: target: core: Fix iSCSI ISID use-after-free in REGISTER AND MOVE\n       {CVE-2026-72083}\n   * CVE-2026-68143\n     - net: slip: serialize receive against buffer reallocation {CVE-2026-68143}\n   * CVE-2026-68335\n     - rds: drop incoming messages that cross network namespace boundaries\n       {CVE-2026-68335}\n   * CVE-2026-72406\n     - net: sungem: fix probe error cleanup {CVE-2026-72406}\n   * CVE-2026-74394\n     - RDMA/srpt: fix integer overflow in immediate data length check\n       {CVE-2026-74394}\n   * CVE-2026-68376\n     - sctp: fix auth_hmacs array size in struct sctp_cookie {CVE-2026-68376}\n   * CVE-2026-72014\n     - drbd: reject data replies with an out-of-range payload size\n       {CVE-2026-72014}\n   * CVE-2026-64471\n     - Bluetooth: btusb: fix use-after-free on registration failure\n       {CVE-2026-64471}\n   * CVE-2026-80590\n     - inet: frags: strip GSO state from fragments before reassembly\n       {CVE-2026-80590}\n   * CVE-2026-74408\n     - wifi: ath9k: fix OOB access from firmware tx status queue ID\n       {CVE-2026-74408}\n   * CVE-2026-68160\n     - ceph: fix pre-auth out-of-bounds read on snaptrace in ceph_handle_caps()\n       {CVE-2026-68160}\n   * CVE-2026-72296\n     - net: ife: require ETH_HLEN to be pullable in ife_decode() {CVE-2026-72296}\n   * CVE-2026-80622\n     - char: tlclk: fix use-after-free in tlclk_cleanup() {CVE-2026-80622}\n   * CVE-2026-68363\n     - wifi: ath9k: hif_usb: don't dereference hif_dev after re-arming firmware\n       request {CVE-2026-68363}\n   * CVE-2026-80558\n     - libceph: Avoid using invalid osd indices from primary_temp\n       {CVE-2026-80558}\n   * CVE-2026-68199\n     - wifi: ath6kl: fix OOB access from firmware ADDBA window size\n       {CVE-2026-68199}\n   * CVE-2026-89724\n     - media: vicodec: fix out-of-bounds write in FWHT encoder {CVE-2026-89724}\n   * CVE-2026-89720\n     - ubifs: fix out-of-bounds read in signature length check {CVE-2026-89720}\n   * CVE-2026-89674\n     - nfsd: fix XDR length calculation in nfsd4_ff_encode_layoutget\n       {CVE-2026-89674}\n   * CVE-2026-89729\n     - HID: sensor-hub: Fix out-of-bounds write in sensor_hub_get_feature\n       {CVE-2026-89729}\n   * CVE-2026-89742\n     - rapidio: mport_cdev: fix use-after-free in dma_req_free() {CVE-2026-89742}\n   * CVE-2026-64375\n     - proc: protect ptrace_may_access() with exec_update_lock (FD links)\n       {CVE-2026-64375}\n   * CVE-2026-64378\n     - writeback: fix race between cgroup_writeback_umount() and\n       inode_switch_wbs() {CVE-2026-64378}\n   * CVE-2026-64448\n     - smb: client: restrict implied bcc[0] exemption to responses without data\n       area {CVE-2026-64448}\n   * CVE-2026-64381\n     - smb: client: Fix next buffer leak in receive_encrypted_standard()\n       {CVE-2026-64381}\n   * CVE-2026-64379\n     - smb: client: mask server-provided mode to 07777 in modefromsid\n       {CVE-2026-64379}\n   * CVE-2026-64445\n     - staging: rtl8723bs: fix WEP length underflow and OOB read in OnAuth()\n       {CVE-2026-64445}\n   * CVE-2026-64440\n     - staging: rtl8723bs: fix OOB write in HT_caps_handler() {CVE-2026-64440}\n   * CVE-2026-64446\n     - staging: rtl8723bs: fix heap buffer overflow in rtw_cfg80211_set_wpa_ie()\n       {CVE-2026-64446}\n   * CVE-2026-64442\n     - staging: rtl8723bs: fix OOB reads in IE loops in issue_assocreq() and\n       join_cmd_hdl() {CVE-2026-64442}\n   * CVE-2026-64443\n     - staging: rtl8723bs: fix OOB read in update_beacon_info() IE loop\n       {CVE-2026-64443}\n   * CVE-2026-64438\n     - crypto: qat - fix VF2PF work teardown race in adf_disable_sriov()\n       {CVE-2026-64438}\n   * CVE-2026-64305\n     - crypto: qat - protect service table iterations with service_lock\n       {CVE-2026-64305}\n   * CVE-2026-64341\n     - USB: iowarrior: fix use-after-free on disconnect race {CVE-2026-64341}\n   * CVE-2026-64344\n     - USB: idmouse: fix use-after-free on disconnect race {CVE-2026-64344}\n   * CVE-2026-64340\n     - USB: legousbtower: fix use-after-free on disconnect race {CVE-2026-64340}\n   * CVE-2026-64422\n     - net: ipv4: bound TCP reordering sysctl writes and MTU probe sizes\n       {CVE-2026-64422}\n   * CVE-2026-64424\n     - netpoll: fix a use-after-free on shutdown path {CVE-2026-64424}\n   * CVE-2026-64423\n     - ipv4: igmp: remove multicast group from hash table on device destruction\n       {CVE-2026-64423}\n   * CVE-2026-64420\n     - mfd: cros_ec: Delay dev_set_drvdata() until probe success {CVE-2026-64420}\n   * CVE-2026-64343\n     - USB: ldusb: fix use-after-free on disconnect race {CVE-2026-64343}\n   * CVE-2026-64330\n     - usb: typec: tcpm: Validate SVID index in svdm_consume_modes()\n       {CVE-2026-64330}\n   * CVE-2026-64449\n     - staging: vme_user: bound slave read/write to the kern_buf size\n       {CVE-2026-64449}\n   * CVE-2026-64348\n     - usb: free iso schedules on failed submit {CVE-2026-64348}\n   * CVE-2026-64304\n     - crypto: qat - validate RSA CRT component lengths {CVE-2026-64304}\n   * CVE-2026-64452\n     - 6lowpan: fix NHC entry use-after-free on error path {CVE-2026-64452}\n   * CVE-2026-64372\n     - cpufreq: pcc: fix use-after-free and double free in _OSC evaluation\n       {CVE-2026-64372}\n   * CVE-2026-64351\n     - net: usb: kalmia: bound RX frame length in kalmia_rx_fixup()\n       {CVE-2026-64351}\n   * CVE-2026-64342\n     - USB: iowarrior: fix use-after-free on disconnect {CVE-2026-64342}\n   * CVE-2026-64323\n     - udf: validate VAT header length against the VAT inode size\n       {CVE-2026-64323}\n   * CVE-2026-64322\n     - udf: validate sparing table length as an entry count, not a byte count\n       {CVE-2026-64322}\n   * CVE-2026-64318\n     - partitions: aix: bound the pp_count scan to the ppe array {CVE-2026-64318}\n   * CVE-2026-64320\n     - nvmet: fix pre-auth out-of-bounds heap read in Discovery Get Log Page\n       {CVE-2026-64320}\n   * CVE-2026-31727\n     - usb: gadget: u_ether: Fix NULL pointer deref in eth_get_drvinfo\n       {CVE-2026-31727}\n   * CVE-2026-46275\n     - Bluetooth: hci_uart: fix UAFs and race conditions in close and init paths\n       {CVE-2026-46275}\n   * CVE-2026-43449\n     - nvme-pci: Fix slab-out-of-bounds in nvme_dbbuf_set {CVE-2026-43449}\n   * CVE-2026-43015\n     - net: macb: fix clk handling on PCI glue driver removal {CVE-2026-43015}\n   * CVE-2026-68156\n     - libceph: refresh auth-\u003eauthorizer_buf{,_len} after authorizer update\n       {CVE-2026-68156}\n   * CVE-2025-39987\n     - can: hi311x: populate ndo_change_mtu() to prevent buffer overflow\n       {CVE-2025-39987}\n   * CVE-2025-39985\n     - can: mcba_usb: populate ndo_change_mtu() to prevent buffer overflow\n       {CVE-2025-39985}\n   * CVE-2026-64237\n     - Input: elan_i2c - validate firmware size before use {CVE-2026-64237}\n   * CVE-2025-68217\n     - Input: pegasus-notetaker - fix potential out-of-bounds access\n       {CVE-2025-68217}\n   * CVE-2026-43279\n     - ALSA: usb-audio: Add sanity check for OOB writes at silencing\n       {CVE-2026-43279}\n   * CVE-2026-52991\n     - sched/psi: fix race between file release and pressure write\n       {CVE-2026-52991}\n   * CVE-2026-53355\n     - net: rds: clear i_sends on setup unwind {CVE-2026-53355}\n   * CVE-2026-52942\n     - netfilter: nf_log: validate MAC header was set before dumping it\n       {CVE-2026-52942}\n   * CVE-2026-53189\n     - mm/huge_memory: update file PMD counter before folio_put()\n       {CVE-2026-53189}\n   * CVE-2026-53264\n     - net/sched: act_api: use RCU with deferred freeing for action lifecycle\n       {CVE-2026-53264}\n   * CVE-2026-45970\n     - bonding: alb: fix UAF in rlb_arp_recv during bond up/down {CVE-2026-45970}\n   * CVE-2026-52920\n     - netfilter: xt_policy: fix strict mode inbound policy matching\n       {CVE-2026-52920}\n   * CVE-2026-46209\n     - drm/gem: Fix inconsistent plane dimension calculation {CVE-2026-46209}\n   * CVE-2026-45856\n     - RDMA/uverbs: Validate wqe_size before using it in ib_uverbs_post_send\n       {CVE-2026-45856}\n   * CVE-2026-53040\n     - ocfs2: validate bg_bits during freefrag scan {CVE-2026-53040}\n   * CVE-2026-53130\n     - fs/omfs: reject s_sys_blocksize smaller than OMFS_DIR_START\n       {CVE-2026-53130}\n   * CVE-2026-43198\n     - tcp: fix potential race in tcp_v6_syn_recv_sock() {CVE-2026-43198}\n   * CVE-2025-40082\n     - hfsplus: fix slab-out-of-bounds read in hfsplus_uni2asc() {CVE-2025-40082}\n   * CVE-2024-53179\n     - cifs: fix use-after-free of signing key {CVE-2024-53179}\n   * CVE-2024-49861\n     - bpf: Fix helper writes to read-only maps {CVE-2024-49861}\n   * CVE-2022-50151\n     - usb: cdns3: fix random warning message when driver load {CVE-2022-50151}\n   * CVE-2022-47519\n     - wifi: wilc1000: validate length of IEEE80211_P2P_ATTR_OPER_CHANNEL\n       attribute {CVE-2022-47519}\n   * CVE-2026-23105\n     - net/sched: qfq: Use cl_is_active to determine whether class is active in\n       qfq_rm_from_ag {CVE-2026-23105}\n   * CVE-2026-43158\n     - xfs: fix freemap adjustments when adding xattrs to leaf blocks\n       {CVE-2026-43158}\n   * Miscellaneous upstream changes\n     - net: rose: split remove and free operations in rose_remove_neigh()\n     - af_unix: read the receive queue tail length under the queue lock in\n       unix_stream_data_wait()\n     - media: rc: Use the correct style for SPDX License Identifier\n     - Revert \"Revert \"sctp: Fix bundling of SHUTDOWN with COOKIE-ACK\"\"\n     - Revert \"sctp: Fix bundling of SHUTDOWN with COOKIE-ACK\"\n   * Bump ABI 5.4.0-238","status":"published","published":"2026-09-21T15:55:34Z","modified":"2026-10-26T09:43:27.456673278Z","updated_at":"2026-11-02T15:43:48.28229Z"},{"id":"CVE-2022-50151","title":"usb: cdns3: fix random warning message when driver load","description":"In the Linux kernel, the following vulnerability has been resolved:\n\nusb: cdns3: fix random warning message when driver load\n\nWarning log:\n[    4.141392] Unexpected gfp: 0x4 (GFP_DMA32). Fixing up to gfp: 0xa20 (GFP_ATOMIC). Fix your code!\n[    4.150340] CPU: 1 PID: 175 Comm: 1-0050 Not tainted 5.15.5-00039-g2fd9ae1b568c #20\n[    4.158010] Hardware name: Freescale i.MX8QXP MEK (DT)\n[    4.163155] Call trace:\n[    4.165600]  dump_backtrace+0x0/0x1b0\n[    4.169286]  show_stack+0x18/0x68\n[    4.172611]  dump_stack_lvl+0x68/0x84\n[    4.176286]  dump_stack+0x18/0x34\n[    4.179613]  kmalloc_fix_flags+0x60/0x88\n[    4.183550]  new_slab+0x334/0x370\n[    4.186878]  ___slab_alloc.part.108+0x4d4/0x748\n[    4.191419]  __slab_alloc.isra.109+0x30/0x78\n[    4.195702]  kmem_cache_alloc+0x40c/0x420\n[    4.199725]  dma_pool_alloc+0xac/0x1f8\n[    4.203486]  cdns3_allocate_trb_pool+0xb4/0xd0\n\npool_alloc_page(struct dma_pool *pool, gfp_t mem_flags)\n{\n\t...\n\tpage = kmalloc(sizeof(*page), mem_flags);\n\tpage-\u003evaddr = dma_alloc_coherent(pool-\u003edev, pool-\u003eallocation,\n\t\t\t\t\t \u0026page-\u003edma, mem_flags);\n\t...\n}\n\nkmalloc was called with mem_flags, which is passed down in\ncdns3_allocate_trb_pool() and have GFP_DMA32 flags.\nkmall_fix_flags() report warning.\n\nGFP_DMA32 is not useful at all. dma_alloc_coherent() will handle\nDMA memory region correctly by pool-\u003edev. GFP_DMA32 can be removed\nsafely.","status":"published","published":"2025-06-18T11:03:10.569Z","modified":"2026-10-28T02:30:30.855741554Z","updated_at":"2026-11-02T15:44:28.74679Z"},{"id":"SUSE-SU-2025:02264-1","title":"Security update for the Linux Kernel","description":"\nThe SUSE Linux Enterprise 15 SP5 kernel was updated to receive various security bugfixes.\n\n\nThe following security bugs were fixed:\n\n- CVE-2021-47557: net/sched: sch_ets: do not peek at classes beyond 'nbands' (bsc#1207361 bsc#1225468).\n- CVE-2021-47595: net/sched: sch_ets: do not remove idle classes from the round-robin list (bsc#1207361 bsc#1226552).\n- CVE-2023-52924: netfilter: nf_tables: do not skip expired elements during walk (bsc#1236821).\n- CVE-2023-52925: netfilter: nf_tables: do not fail inserts if duplicate has expired (bsc#1236822).\n- CVE-2024-26808: netfilter: nft_chain_filter: handle NETDEV_UNREGISTER for inet/ingress basechain (bsc#1222634).\n- CVE-2024-26924: scsi: lpfc: Release hbalock before calling lpfc_worker_wake_up() (bsc#1225820).\n- CVE-2024-27397: kabi: place tstamp needed for nftables set in a hole (bsc#1224095).\n- CVE-2024-36978: net: sched: sch_multiq: fix possible OOB write in multiq_tune() (bsc#1226514).\n- CVE-2024-46800: sch/netem: fix use after free in netem_dequeue (bsc#1230827).\n- CVE-2024-53125: bpf: sync_linked_regs() must preserve subreg_def (bsc#1234156).\n- CVE-2024-53141: netfilter: ipset: add missing range check in bitmap_ip_uadt (bsc#1234381).\n- CVE-2024-53197: ALSA: usb-audio: Fix potential out-of-bound accesses for Extigy and Mbox devices (bsc#1235464).\n- CVE-2024-56770: sch/netem: fix use after free in netem_dequeue (bsc#1235637).\n- CVE-2025-21700: net: sched: Disallow replacing of child qdisc from one parent to another (bsc#1237159).\n- CVE-2025-21702: pfifo_tail_enqueue: Drop new packet when sch-\u003elimit == 0 (bsc#1237312).\n- CVE-2025-21703: netem: Update sch-\u003eq.qlen before qdisc_tree_reduce_backlog() (bsc#1237313).\n- CVE-2025-21756: vsock: Orphan socket after transport release (bsc#1238876).\n- CVE-2025-23141: KVM: x86: Acquire SRCU in KVM_GET_MP_STATE to protect guest memory accesses (bsc#1242782).\n- CVE-2025-37752: net_sched: sch_sfq: move the limit validation (bsc#1242504).\n- CVE-2025-37823: net_sched: hfsc: Fix a potential UAF in hfsc_dequeue() too (bsc#1242924).\n- CVE-2025-37890: net_sched: hfsc: Fix a UAF vulnerability in class with netem as child qdisc (bsc#1243330).\n- CVE-2025-37997: netfilter: ipset: fix region locking in hash types (bsc#1243832).\n- CVE-2025-38000: sch_hfsc: Fix qlen accounting bug when using peek in hfsc_enqueue() (bsc#1244277).\n- CVE-2025-38001: net_sched: hfsc: Address reentrant enqueue adding class to eltree twice (bsc#1244234).\n- CVE-2025-38014: dmaengine: idxd: Refactor remove call with idxd_cleanup() helper (bsc#1244732).\n- CVE-2025-38060: bpf: abort verification if env-\u003ecur_state-\u003eloop_entry != NULL (bsc#1245155).\n- CVE-2025-38083: net_sched: prio: fix a race in prio_tune() (bsc#1245183).\n\nThe following non-security bugs were fixed:\n\n- ALSA: usb-audio: Fix a DMA to stack memory bug (git-fixes).\n- Fix reference in 'net_sched: sch_sfq: use a temporary work area for validating configuration' (bsc#1242504)\n- MyBS: Correctly generate build flags for non-multibuild package limit (bsc# 1244241) Fixes: 0999112774fc ('MyBS: Use buildflags to set which package to build')\n- MyBS: Do not build kernel-obs-qa with limit_packages Fixes: 58e3f8c34b2b ('bs-upload-kernel: Pass limit_packages also on multibuild')\n- MyBS: Simplify qa_expr generation Start with a 0 which makes the expression valid even if there are no QA repositories (currently does not happen). Then separator is always needed.\n- bs-upload-kernel: Pass limit_packages also on multibuild Fixes: 0999112774fc ('MyBS: Use buildflags to set which package to build') Fixes: 747f601d4156 ('bs-upload-kernel, MyBS, Buildresults: Support multibuild (JSC-SLE#5501, boo#1211226, bsc#1218184)')\n- hugetlb: unshare some PMDs when splitting VMAs (bsc#1245431).\n- kernel-source: Do not use multiple -r in sed parameters\n- kernel-source: Remove log.sh from sources\n- mkspec: Exclude rt flavor from kernel-syms dependencies (bsc#1244337).\n- mm/hugetlb: fix huge_pmd_unshare() vs GUP-fast race (bsc#1245431).\n- mm/hugetlb: unshare page tables during VMA split, not before (bsc#1245431).\n- net_sched: sch_fifo: implement lockless __fifo_dump() (bsc#1237312)\n- net_sched: sch_sfq: use a temporary work area for validating configuration (bsc#1232504)\n- ovl: fix use inode directly in rcu-walk mode (bsc#1241900).\n- powerpc/powernv/memtrace: Fix out of bounds issue in memtrace mmap (bsc#1244309 ltc#213790).\n- powerpc/vas: Return -EINVAL if the offset is non-zero in mmap() (bsc#1244309 ltc#213790).\n- scsi: storvsc: Do not report the host packet status as the hv status (git-fixes).\n- scsi: storvsc: Increase the timeouts to storvsc_timeout (bsc#1245455).\n","status":"published","published":"2025-07-10T08:25:54Z","modified":"2026-02-04T02:58:55.103311Z","updated_at":"2026-11-02T15:53:56.647031Z"},{"id":"SUSE-SU-2025:02321-1","title":"Security update for the Linux Kernel","description":"\nThe SUSE Linux Enterprise 15 SP5 RT kernel was updated to receive various security bugfixes.\n\n\nThe following security bugs were fixed:\n\n- CVE-2021-47557: net/sched: sch_ets: do not peek at classes beyond 'nbands' (bsc#1207361 bsc#1225468).\n- CVE-2021-47595: net/sched: sch_ets: do not remove idle classes from the round-robin list (bsc#1207361 bsc#1226552).\n- CVE-2023-52924: netfilter: nf_tables: do not skip expired elements during walk (bsc#1236821).\n- CVE-2023-52925: netfilter: nf_tables: do not fail inserts if duplicate has expired (bsc#1236822).\n- CVE-2024-26808: netfilter: nft_chain_filter: handle NETDEV_UNREGISTER for inet/ingress basechain (bsc#1222634).\n- CVE-2024-26924: scsi: lpfc: Release hbalock before calling lpfc_worker_wake_up() (bsc#1225820).\n- CVE-2024-27397: kabi: place tstamp needed for nftables set in a hole (bsc#1224095).\n- CVE-2024-28956: x86/its: Add support for ITS-safe indirect thunk (bsc#1242006).\n- CVE-2024-36978: net: sched: sch_multiq: fix possible OOB write in multiq_tune() (bsc#1226514).\n- CVE-2024-46800: sch/netem: fix use after free in netem_dequeue (bsc#1230827).\n- CVE-2024-53125: bpf: sync_linked_regs() must preserve subreg_def (bsc#1234156).\n- CVE-2024-53141: netfilter: ipset: add missing range check in bitmap_ip_uadt (bsc#1234381).\n- CVE-2024-53197: ALSA: usb-audio: Fix potential out-of-bound accesses for Extigy and Mbox devices (bsc#1235464).\n- CVE-2024-56770: sch/netem: fix use after free in netem_dequeue (bsc#1235637).\n- CVE-2025-21700: net: sched: Disallow replacing of child qdisc from one parent to another (bsc#1237159).\n- CVE-2025-21702: pfifo_tail_enqueue: Drop new packet when sch-\u003elimit == 0 (bsc#1237312).\n- CVE-2025-21703: netem: Update sch-\u003eq.qlen before qdisc_tree_reduce_backlog() (bsc#1237313).\n- CVE-2025-21756: vsock: Orphan socket after transport release (bsc#1238876).\n- CVE-2025-23141: KVM: x86: Acquire SRCU in KVM_GET_MP_STATE to protect guest memory accesses (bsc#1242782).\n- CVE-2025-37752: net_sched: sch_sfq: move the limit validation (bsc#1242504).\n- CVE-2025-37785: ext4: fix OOB read when checking dotdot dir (bsc#1241640).\n- CVE-2025-37823: net_sched: hfsc: Fix a potential UAF in hfsc_dequeue() too (bsc#1242924).\n- CVE-2025-37890: net_sched: hfsc: Fix a UAF vulnerability in class with netem as child qdisc (bsc#1243330).\n- CVE-2025-37997: netfilter: ipset: fix region locking in hash types (bsc#1243832).\n- CVE-2025-38000: sch_hfsc: Fix qlen accounting bug when using peek in hfsc_enqueue() (bsc#1244277).\n- CVE-2025-38001: net_sched: hfsc: Address reentrant enqueue adding class to eltree twice (bsc#1244234).\n- CVE-2025-38014: dmaengine: idxd: Refactor remove call with idxd_cleanup() helper (bsc#1244732).\n- CVE-2025-38060: bpf: abort verification if env-\u003ecur_state-\u003eloop_entry != NULL (bsc#1245155).\n- CVE-2025-38083: net_sched: prio: fix a race in prio_tune() (bsc#1245183).\n\nThe following non-security bugs were fixed:\n\n- ALSA: usb-audio: Fix a DMA to stack memory bug (git-fixes).\n- Fix conditional for selecting gcc-13 Fixes: 51dacec21eb1 ('Use gcc-13 for build on SLE16 (jsc#PED-10028).')\n- Fix reference in 'net_sched: sch_sfq: use a temporary work area for validating configuration' (bsc#1242504)\n- MyBS: Correctly generate build flags for non-multibuild package limit (bsc# 1244241) Fixes: 0999112774fc ('MyBS: Use buildflags to set which package to build')\n- MyBS: Do not build kernel-obs-qa with limit_packages Fixes: 58e3f8c34b2b ('bs-upload-kernel: Pass limit_packages also on multibuild')\n- MyBS: Simplify qa_expr generation Start with a 0 which makes the expression valid even if there are no QA repositories (currently does not happen). Then separator is always needed.\n- Require zstd in kernel-default-devel when module compression is zstd To use ksym-provides tool modules need to be uncompressed. Without zstd at least kernel-default-base does not have provides. Link: https://github.com/openSUSE/rpm-config-SUSE/pull/82\n- Use gcc-13 for build on SLE16 (jsc#PED-10028).\n- add nf_tables for iptables non-legacy network handling This is needed for example by docker on the Alpine Linux distribution, but can also be used on openSUSE.\n- bs-upload-kernel: Pass limit_packages also on multibuild Fixes: 0999112774fc ('MyBS: Use buildflags to set which package to build') Fixes: 747f601d4156 ('bs-upload-kernel, MyBS, Buildresults: Support multibuild (JSC-SLE#5501, boo#1211226, bsc#1218184)')\n- check-for-config-changes: Fix flag name typo\n- doc/README.SUSE: Point to the updated version of LKMPG\n- hugetlb: unshare some PMDs when splitting VMAs (bsc#1245431).\n- kernel-obs-qa: Use srchash for dependency as well\n- kernel-source: Also replace bin/env\n- kernel-source: Also update the search to match bin/env Fixes: dc2037cd8f94 ('kernel-source: Also replace bin/env'\n- kernel-source: Remove log.sh from sources\n- mkspec: Exclude rt flavor from kernel-syms dependencies (bsc#1244337).\n- mm/hugetlb: fix huge_pmd_unshare() vs GUP-fast race (bsc#1245431).\n- mm/hugetlb: unshare page tables during VMA split, not before (bsc#1245431).\n- net_sched: sch_fifo: implement lockless __fifo_dump() (bsc#1237312)\n- net_sched: sch_sfq: use a temporary work area for validating configuration (bsc#1232504)\n- ovl: fix use inode directly in rcu-walk mode (bsc#1241900).\n- packaging: Turn gcc version into config.sh variable Fixes: 51dacec21eb1 ('Use gcc-13 for build on SLE16 (jsc#PED-10028).')\n- powerpc/powernv/memtrace: Fix out of bounds issue in memtrace mmap (bsc#1244309 ltc#213790).\n- powerpc/vas: Return -EINVAL if the offset is non-zero in mmap() (bsc#1244309 ltc#213790).\n- rpm/check-for-config-changes: Add GCC_ASM_FLAG_OUTPUT_BROKEN\n- rpm/check-for-config-changes: Add GCC_ASM_FLAG_OUTPUT_BROKEN Both spellings are actually used\n- rpm/check-for-config-changes: add LD_CAN_ to IGNORED_CONFIGS_RE\n- rpm/check-for-config-changes: add more to IGNORED_CONFIGS_RE Useful when someone tries (needs) to build the kernel with clang.\n- rpm/check-for-config-changes: ignore DRM_MSM_VALIDATE_XML This option is dynamically enabled to build-test different configurations. This makes run_oldconfig.sh complain sporadically for arm64.\n- rpm/kernel-binary.spec.in: Also order against update-bootloader (boo#1228659, boo#1240785, boo#1241038).\n- rpm/kernel-binary.spec.in: Fix missing 20-kernel-default-extra.conf (bsc#1239986) sle_version was obsoleted for SLE16. It has to be combined with suse_version check.\n- rpm/kernel-binary.spec.in: Use OrderWithRequires (boo#1228659 boo#1241038). OrderWithRequires was introduced in rpm 4.9 (ie. SLE12+) to allow a package to inform the order of installation of other package without hard requiring that package. This means our kernel-binary packages no longer need to hard require perl-Bootloader or dracut, resolving the long-commented issue there. This is also needed for udev \u0026 systemd-boot to ensure those packages are installed before being called by dracut (boo#1228659)\n- rpm/kernel-binary.spec.in: fix KMPs build on 6.13+ (bsc#1234454)\n- rpm/kernel-docs.spec.in: Workaround for reproducible builds (bsc#1238303)\n- rpm/package-descriptions: Add rt and rt_debug descriptions\n- rpm/release-projects: Update the ALP projects again (bsc#1231293).\n- rpm/split-modules: Fix optional splitting with usrmerge (bsc#1238570)\n- rpm: Stop using is_kotd_qa macro\n- scsi: storvsc: Do not report the host packet status as the hv status (git-fixes).\n- scsi: storvsc: Increase the timeouts to storvsc_timeout (bsc#1245455).\n","status":"published","published":"2025-07-15T14:31:35Z","modified":"2026-03-23T04:48:33.753751Z","updated_at":"2026-11-02T15:53:56.647031Z"},{"id":"SUSE-SU-2025:02322-1","title":"Security update for the Linux Kernel","description":"\nThe SUSE Linux Enterprise 15 SP4 RT kernel was updated to receive various security bugfixes.\n\n\nThe following security bugs were fixed:\n\n- CVE-2021-47557: net/sched: sch_ets: do not peek at classes beyond 'nbands' (bsc#1207361 bsc#1225468).\n- CVE-2021-47595: net/sched: sch_ets: do not remove idle classes from the round-robin list (bsc#1207361 bsc#1226552).\n- CVE-2023-52924: netfilter: nf_tables: do not skip expired elements during walk (bsc#1236821).\n- CVE-2023-52925: netfilter: nf_tables: do not fail inserts if duplicate has expired (bsc#1236822).\n- CVE-2024-26808: netfilter: nft_chain_filter: handle NETDEV_UNREGISTER for inet/ingress basechain (bsc#1222634).\n- CVE-2024-26924: scsi: lpfc: Release hbalock before calling lpfc_worker_wake_up() (bsc#1225820).\n- CVE-2024-27397: kabi: place tstamp needed for nftables set in a hole (bsc#1224095).\n- CVE-2024-36978: net: sched: sch_multiq: fix possible OOB write in multiq_tune() (bsc#1226514).\n- CVE-2024-46800: sch/netem: fix use after free in netem_dequeue (bsc#1230827).\n- CVE-2024-53057: net/sched: stop qdisc_tree_reduce_backlog on TC_H_ROOT (bsc#1233551).\n- CVE-2024-53125: bpf: sync_linked_regs() must preserve subreg_def (bsc#1234156).\n- CVE-2024-53141: netfilter: ipset: add missing range check in bitmap_ip_uadt (bsc#1234381).\n- CVE-2024-56770: sch/netem: fix use after free in netem_dequeue (bsc#1235637).\n- CVE-2024-57947: netfilter: nf_set_pipapo: fix initial map fill (bsc#1236333).\n- CVE-2025-21700: net: sched: Disallow replacing of child qdisc from one parent to another (bsc#1237159).\n- CVE-2025-21702: pfifo_tail_enqueue: Drop new packet when sch-\u003elimit == 0 (bsc#1237312).\n- CVE-2025-21703: netem: Update sch-\u003eq.qlen before qdisc_tree_reduce_backlog() (bsc#1237313).\n- CVE-2025-21756: vsock: Orphan socket after transport release (bsc#1238876).\n- CVE-2025-23141: KVM: x86: Acquire SRCU in KVM_GET_MP_STATE to protect guest memory accesses (bsc#1242782).\n- CVE-2025-37752: net_sched: sch_sfq: move the limit validation (bsc#1242504).\n- CVE-2025-37797: net_sched: hfsc: Fix a UAF vulnerability in class handling (bsc#1242417).\n- CVE-2025-37823: net_sched: hfsc: Fix a potential UAF in hfsc_dequeue() too (bsc#1242924).\n- CVE-2025-37890: net_sched: hfsc: Fix a UAF vulnerability in class with netem as child qdisc (bsc#1243330).\n- CVE-2025-37997: netfilter: ipset: fix region locking in hash types (bsc#1243832).\n- CVE-2025-38000: sch_hfsc: Fix qlen accounting bug when using peek in hfsc_enqueue() (bsc#1244277).\n- CVE-2025-38001: net_sched: hfsc: Address reentrant enqueue adding class to eltree twice (bsc#1244234).\n- CVE-2025-38014: dmaengine: idxd: Refactor remove call with idxd_cleanup() helper (bsc#1244732).\n- CVE-2025-38083: net_sched: prio: fix a race in prio_tune() (bsc#1245183).\n\nThe following non-security bugs were fixed:\n\n- Fix conditional for selecting gcc-13 Fixes: 51dacec21eb1 ('Use gcc-13 for build on SLE16 (jsc#PED-10028).')\n- Fix reference in 'net_sched: sch_sfq: use a temporary work area for validating configuration' (bsc#1242504)\n- MyBS: Correctly generate build flags for non-multibuild package limit (bsc# 1244241) Fixes: 0999112774fc ('MyBS: Use buildflags to set which package to build')\n- MyBS: Do not build kernel-obs-qa with limit_packages Fixes: 58e3f8c34b2b ('bs-upload-kernel: Pass limit_packages also on multibuild')\n- MyBS: Simplify qa_expr generation Start with a 0 which makes the expression valid even if there are no QA repositories (currently does not happen). Then separator is always needed.\n- Require zstd in kernel-default-devel when module compression is zstd To use ksym-provides tool modules need to be uncompressed. Without zstd at least kernel-default-base does not have provides. Link: https://github.com/openSUSE/rpm-config-SUSE/pull/82\n- Test the correct macro to detect RT kernel build Fixes: 470cd1a41502 ('kernel-binary: Support livepatch_rt with merged RT branch')\n- Use gcc-13 for build on SLE16 (jsc#PED-10028).\n- add nf_tables for iptables non-legacy network handling This is needed for example by docker on the Alpine Linux distribution, but can also be used on openSUSE.\n- bs-upload-kernel: Pass limit_packages also on multibuild Fixes: 0999112774fc ('MyBS: Use buildflags to set which package to build') Fixes: 747f601d4156 ('bs-upload-kernel, MyBS, Buildresults: Support multibuild (JSC-SLE#5501, boo#1211226, bsc#1218184)')\n- check-for-config-changes: Fix flag name typo\n- doc/README.SUSE: Point to the updated version of LKMPG\n- hugetlb: unshare some PMDs when splitting VMAs (bsc#1245431).\n- kernel-binary: Support livepatch_rt with merged RT branch\n- kernel-obs-qa: Use srchash for dependency as well\n- kernel-source: Also replace bin/env\n- kernel-source: Also update the search to match bin/env Fixes: dc2037cd8f94 ('kernel-source: Also replace bin/env'\n- kernel-source: Do not use multiple -r in sed parameters\n- kernel-source: Remove log.sh from sources\n- mkspec: Exclude rt flavor from kernel-syms dependencies (bsc#1244337).\n- mm/hugetlb: fix huge_pmd_unshare() vs GUP-fast race (bsc#1245431).\n- mm/hugetlb: unshare page tables during VMA split, not before (bsc#1245431).\n- net_sched: sch_fifo: implement lockless __fifo_dump() (bsc#1237312)\n- net_sched: sch_sfq: use a temporary work area for validating configuration (bsc#1232504)\n- packaging: Patch Makefile to pre-select gcc version (jsc#PED-12251).\n- packaging: Turn gcc version into config.sh variable Fixes: 51dacec21eb1 ('Use gcc-13 for build on SLE16 (jsc#PED-10028).')\n- powerpc/powernv/memtrace: Fix out of bounds issue in memtrace mmap (bsc#1244309 ltc#213790).\n- powerpc/vas: Return -EINVAL if the offset is non-zero in mmap() (bsc#1244309 ltc#213790).\n- rpm/check-for-config-changes: Add GCC_ASM_FLAG_OUTPUT_BROKEN\n- rpm/check-for-config-changes: Add GCC_ASM_FLAG_OUTPUT_BROKEN Both spellings are actually used\n- rpm/check-for-config-changes: add LD_CAN_ to IGNORED_CONFIGS_RE\n- rpm/check-for-config-changes: add more to IGNORED_CONFIGS_RE Useful when someone tries (needs) to build the kernel with clang.\n- rpm/check-for-config-changes: ignore DRM_MSM_VALIDATE_XML This option is dynamically enabled to build-test different configurations. This makes run_oldconfig.sh complain sporadically for arm64.\n- rpm/kernel-binary.spec.in: Also order against update-bootloader (boo#1228659, boo#1240785, boo#1241038).\n- rpm/kernel-binary.spec.in: Fix missing 20-kernel-default-extra.conf (bsc#1239986) sle_version was obsoleted for SLE16. It has to be combined with suse_version check.\n- rpm/kernel-binary.spec.in: Use OrderWithRequires (boo#1228659 boo#1241038). OrderWithRequires was introduced in rpm 4.9 (ie. SLE12+) to allow a package to inform the order of installation of other package without hard requiring that package. This means our kernel-binary packages no longer need to hard require perl-Bootloader or dracut, resolving the long-commented issue there. This is also needed for udev \u0026 systemd-boot to ensure those packages are installed before being called by dracut (boo#1228659)\n- rpm/kernel-binary.spec.in: fix KMPs build on 6.13+ (bsc#1234454)\n- rpm/kernel-docs.spec.in: Workaround for reproducible builds (bsc#1238303)\n- rpm/package-descriptions: Add rt and rt_debug descriptions\n- rpm/release-projects: Update the ALP projects again (bsc#1231293).\n- rpm/split-modules: Fix optional splitting with usrmerge (bsc#1238570)\n- rpm: Stop using is_kotd_qa macro This macro is set by bs-upload-kernel, and a conditional in each spec file is used to determine when to build the spec file. This logic should not really be in the spec file. Previously this was done with package links and package meta for the individula links. However, the use of package links is rejected for packages in git based release projects (nothing to do with git actually, new policy). An alternative to package links is multibuild. However, for multibuild packages package meta cannot be used to set which spec file gets built. Use prjcon buildflags instead, and remove this conditional. Depends on bs-upload-kernel adding the build flag.\n- scsi: storvsc: Do not report the host packet status as the hv status (git-fixes).\n- scsi: storvsc: Increase the timeouts to storvsc_timeout (bsc#1245455).\n- wifi: cfg80211: Add my certificate (bsc#1243001).\n- wifi: cfg80211: fix certs build to not depend on file order (bsc#1243001).\n","status":"published","published":"2025-07-15T14:31:46Z","modified":"2026-03-23T04:46:32.095371Z","updated_at":"2026-11-02T15:53:56.647031Z"},{"id":"SUSE-SU-2025:02537-1","title":"Security update for the Linux Kernel","description":"\nThe SUSE Linux Enterprise 15 SP4 kernel was updated to receive various security bugfixes.\n\n\nThe following security bugs were fixed:\n\n- CVE-2021-47557: net/sched: sch_ets: do not peek at classes beyond 'nbands' (bsc#1207361 bsc#1225468).\n- CVE-2021-47595: net/sched: sch_ets: do not remove idle classes from the round-robin list (bsc#1207361 bsc#1226552).\n- CVE-2023-52924: netfilter: nf_tables: do not skip expired elements during walk (bsc#1236821).\n- CVE-2023-52925: netfilter: nf_tables: do not fail inserts if duplicate has expired (bsc#1236822).\n- CVE-2024-26808: netfilter: nft_chain_filter: handle NETDEV_UNREGISTER for inet/ingress basechain (bsc#1222634).\n- CVE-2024-26924: scsi: lpfc: Release hbalock before calling lpfc_worker_wake_up() (bsc#1225820).\n- CVE-2024-27397: kabi: place tstamp needed for nftables set in a hole (bsc#1224095).\n- CVE-2024-36978: net: sched: sch_multiq: fix possible OOB write in multiq_tune() (bsc#1226514).\n- CVE-2024-46800: sch/netem: fix use after free in netem_dequeue (bsc#1230827).\n- CVE-2024-53057: net/sched: stop qdisc_tree_reduce_backlog on TC_H_ROOT (bsc#1233551).\n- CVE-2024-53125: bpf: sync_linked_regs() must preserve subreg_def (bsc#1234156).\n- CVE-2024-53141: netfilter: ipset: add missing range check in bitmap_ip_uadt (bsc#1234381).\n- CVE-2024-56770: sch/netem: fix use after free in netem_dequeue (bsc#1235637).\n- CVE-2024-57947: netfilter: nf_set_pipapo: fix initial map fill (bsc#1236333).\n- CVE-2025-21700: net: sched: Disallow replacing of child qdisc from one parent to another (bsc#1237159).\n- CVE-2025-21702: pfifo_tail_enqueue: Drop new packet when sch-\u003elimit == 0 (bsc#1237312).\n- CVE-2025-21703: netem: Update sch-\u003eq.qlen before qdisc_tree_reduce_backlog() (bsc#1237313).\n- CVE-2025-21756: vsock: Orphan socket after transport release (bsc#1238876).\n- CVE-2025-23141: KVM: x86: Acquire SRCU in KVM_GET_MP_STATE to protect guest memory accesses (bsc#1242782).\n- CVE-2025-37752: net_sched: sch_sfq: move the limit validation (bsc#1242504).\n- CVE-2025-37797: net_sched: hfsc: Fix a UAF vulnerability in class handling (bsc#1242417).\n- CVE-2025-37823: net_sched: hfsc: Fix a potential UAF in hfsc_dequeue() too (bsc#1242924).\n- CVE-2025-37890: net_sched: hfsc: Fix a UAF vulnerability in class with netem as child qdisc (bsc#1243330).\n- CVE-2025-37997: netfilter: ipset: fix region locking in hash types (bsc#1243832).\n- CVE-2025-38000: sch_hfsc: Fix qlen accounting bug when using peek in hfsc_enqueue() (bsc#1244277).\n- CVE-2025-38001: net_sched: hfsc: Address reentrant enqueue adding class to eltree twice (bsc#1244234).\n- CVE-2025-38014: dmaengine: idxd: Refactor remove call with idxd_cleanup() helper (bsc#1244732).\n- CVE-2025-38083: net_sched: prio: fix a race in prio_tune() (bsc#1245183).\n\nThe following non-security bugs were fixed:\n\n- Fix conditional for selecting gcc-13 Fixes: 51dacec21eb1 ('Use gcc-13 for build on SLE16 (jsc#PED-10028).')\n- Fix reference in 'net_sched: sch_sfq: use a temporary work area for validating configuration' (bsc#1242504)\n- MyBS: Correctly generate build flags for non-multibuild package limit (bsc# 1244241) Fixes: 0999112774fc ('MyBS: Use buildflags to set which package to build')\n- MyBS: Do not build kernel-obs-qa with limit_packages Fixes: 58e3f8c34b2b ('bs-upload-kernel: Pass limit_packages also on multibuild')\n- MyBS: Simplify qa_expr generation Start with a 0 which makes the expression valid even if there are no QA repositories (currently does not happen). Then separator is always needed.\n- Require zstd in kernel-default-devel when module compression is zstd To use ksym-provides tool modules need to be uncompressed. Without zstd at least kernel-default-base does not have provides. Link: https://github.com/openSUSE/rpm-config-SUSE/pull/82\n- Use gcc-13 for build on SLE16 (jsc#PED-10028).\n- add nf_tables for iptables non-legacy network handling This is needed for example by docker on the Alpine Linux distribution, but can also be used on openSUSE.\n- bs-upload-kernel: Pass limit_packages also on multibuild Fixes: 0999112774fc ('MyBS: Use buildflags to set which package to build') Fixes: 747f601d4156 ('bs-upload-kernel, MyBS, Buildresults: Support multibuild (JSC-SLE#5501, boo#1211226, bsc#1218184)')\n- check-for-config-changes: Fix flag name typo\n- doc/README.SUSE: Point to the updated version of LKMPG\n- hugetlb: unshare some PMDs when splitting VMAs (bsc#1245431).\n- kernel-binary: Support livepatch_rt with merged RT branch\n- kernel-obs-qa: Use srchash for dependency as well\n- kernel-source: Also replace bin/env\n- kernel-source: Also update the search to match bin/env Fixes: dc2037cd8f94 ('kernel-source: Also replace bin/env'\n- kernel-source: Remove log.sh from sources\n- mkspec: Exclude rt flavor from kernel-syms dependencies (bsc#1244337).\n- mm/hugetlb: fix huge_pmd_unshare() vs GUP-fast race (bsc#1245431).\n- mm/hugetlb: unshare page tables during VMA split, not before (bsc#1245431).\n- net_sched: sch_fifo: implement lockless __fifo_dump() (bsc#1237312)\n- net_sched: sch_sfq: use a temporary work area for validating configuration (bsc#1232504)\n- packaging: Patch Makefile to pre-select gcc version (jsc#PED-12251).\n- packaging: Turn gcc version into config.sh variable Fixes: 51dacec21eb1 ('Use gcc-13 for build on SLE16 (jsc#PED-10028).')\n- powerpc/powernv/memtrace: Fix out of bounds issue in memtrace mmap (bsc#1244309 ltc#213790).\n- powerpc/vas: Return -EINVAL if the offset is non-zero in mmap() (bsc#1244309 ltc#213790).\n- rpm/check-for-config-changes: Add GCC_ASM_FLAG_OUTPUT_BROKEN\n- rpm/check-for-config-changes: Add GCC_ASM_FLAG_OUTPUT_BROKEN Both spellings are actually used\n- rpm/check-for-config-changes: add LD_CAN_ to IGNORED_CONFIGS_RE\n- rpm/check-for-config-changes: add more to IGNORED_CONFIGS_RE Useful when someone tries (needs) to build the kernel with clang.\n- rpm/check-for-config-changes: ignore DRM_MSM_VALIDATE_XML This option is dynamically enabled to build-test different configurations. This makes run_oldconfig.sh complain sporadically for arm64.\n- rpm/kernel-binary.spec.in: Also order against update-bootloader (boo#1228659, boo#1240785, boo#1241038).\n- rpm/kernel-binary.spec.in: Fix missing 20-kernel-default-extra.conf (bsc#1239986) sle_version was obsoleted for SLE16. It has to be combined with suse_version check.\n- rpm/kernel-binary.spec.in: Use OrderWithRequires (boo#1228659 boo#1241038).\n- rpm/kernel-binary.spec.in: fix KMPs build on 6.13+ (bsc#1234454)\n- rpm/kernel-docs.spec.in: Workaround for reproducible builds (bsc#1238303)\n- rpm/package-descriptions: Add rt and rt_debug descriptions\n- rpm/release-projects: Update the ALP projects again (bsc#1231293).\n- rpm/split-modules: Fix optional splitting with usrmerge (bsc#1238570)\n- rpm: Stop using is_kotd_qa macro\n- scsi: storvsc: Do not report the host packet status as the hv status (git-fixes).\n- scsi: storvsc: Increase the timeouts to storvsc_timeout (bsc#1245455).\n- wifi: cfg80211: Add my certificate (bsc#1243001).\n- wifi: cfg80211: fix certs build to not depend on file order (bsc#1243001).\n","status":"published","published":"2025-07-28T15:09:33Z","modified":"2026-02-05T10:54:52.351892Z","updated_at":"2026-11-02T15:53:56.647031Z"},{"id":"SUSE-SU-2025:2264-1","title":"Security update for the Linux Kernel","description":"\nThe SUSE Linux Enterprise 15 SP5 kernel was updated to receive various security bugfixes.\n\n\nThe following security bugs were fixed:\n\n- CVE-2021-47557: net/sched: sch_ets: do not peek at classes beyond 'nbands' (bsc#1207361 bsc#1225468).\n- CVE-2021-47595: net/sched: sch_ets: do not remove idle classes from the round-robin list (bsc#1207361 bsc#1226552).\n- CVE-2023-52924: netfilter: nf_tables: do not skip expired elements during walk (bsc#1236821).\n- CVE-2023-52925: netfilter: nf_tables: do not fail inserts if duplicate has expired (bsc#1236822).\n- CVE-2024-26808: netfilter: nft_chain_filter: handle NETDEV_UNREGISTER for inet/ingress basechain (bsc#1222634).\n- CVE-2024-26924: scsi: lpfc: Release hbalock before calling lpfc_worker_wake_up() (bsc#1225820).\n- CVE-2024-27397: kabi: place tstamp needed for nftables set in a hole (bsc#1224095).\n- CVE-2024-36978: net: sched: sch_multiq: fix possible OOB write in multiq_tune() (bsc#1226514).\n- CVE-2024-46800: sch/netem: fix use after free in netem_dequeue (bsc#1230827).\n- CVE-2024-53125: bpf: sync_linked_regs() must preserve subreg_def (bsc#1234156).\n- CVE-2024-53141: netfilter: ipset: add missing range check in bitmap_ip_uadt (bsc#1234381).\n- CVE-2024-53197: ALSA: usb-audio: Fix potential out-of-bound accesses for Extigy and Mbox devices (bsc#1235464).\n- CVE-2024-56770: sch/netem: fix use after free in netem_dequeue (bsc#1235637).\n- CVE-2025-21700: net: sched: Disallow replacing of child qdisc from one parent to another (bsc#1237159).\n- CVE-2025-21702: pfifo_tail_enqueue: Drop new packet when sch-\u003elimit == 0 (bsc#1237312).\n- CVE-2025-21703: netem: Update sch-\u003eq.qlen before qdisc_tree_reduce_backlog() (bsc#1237313).\n- CVE-2025-21756: vsock: Orphan socket after transport release (bsc#1238876).\n- CVE-2025-23141: KVM: x86: Acquire SRCU in KVM_GET_MP_STATE to protect guest memory accesses (bsc#1242782).\n- CVE-2025-37752: net_sched: sch_sfq: move the limit validation (bsc#1242504).\n- CVE-2025-37823: net_sched: hfsc: Fix a potential UAF in hfsc_dequeue() too (bsc#1242924).\n- CVE-2025-37890: net_sched: hfsc: Fix a UAF vulnerability in class with netem as child qdisc (bsc#1243330).\n- CVE-2025-37997: netfilter: ipset: fix region locking in hash types (bsc#1243832).\n- CVE-2025-38000: sch_hfsc: Fix qlen accounting bug when using peek in hfsc_enqueue() (bsc#1244277).\n- CVE-2025-38001: net_sched: hfsc: Address reentrant enqueue adding class to eltree twice (bsc#1244234).\n- CVE-2025-38014: dmaengine: idxd: Refactor remove call with idxd_cleanup() helper (bsc#1244732).\n- CVE-2025-38060: bpf: abort verification if env-\u003ecur_state-\u003eloop_entry != NULL (bsc#1245155).\n- CVE-2025-38083: net_sched: prio: fix a race in prio_tune() (bsc#1245183).\n\nThe following non-security bugs were fixed:\n\n- ALSA: usb-audio: Fix a DMA to stack memory bug (git-fixes).\n- Fix reference in 'net_sched: sch_sfq: use a temporary work area for validating configuration' (bsc#1242504)\n- MyBS: Correctly generate build flags for non-multibuild package limit (bsc# 1244241) Fixes: 0999112774fc ('MyBS: Use buildflags to set which package to build')\n- MyBS: Do not build kernel-obs-qa with limit_packages Fixes: 58e3f8c34b2b ('bs-upload-kernel: Pass limit_packages also on multibuild')\n- MyBS: Simplify qa_expr generation Start with a 0 which makes the expression valid even if there are no QA repositories (currently does not happen). Then separator is always needed.\n- bs-upload-kernel: Pass limit_packages also on multibuild Fixes: 0999112774fc ('MyBS: Use buildflags to set which package to build') Fixes: 747f601d4156 ('bs-upload-kernel, MyBS, Buildresults: Support multibuild (JSC-SLE#5501, boo#1211226, bsc#1218184)')\n- hugetlb: unshare some PMDs when splitting VMAs (bsc#1245431).\n- kernel-source: Do not use multiple -r in sed parameters\n- kernel-source: Remove log.sh from sources\n- mkspec: Exclude rt flavor from kernel-syms dependencies (bsc#1244337).\n- mm/hugetlb: fix huge_pmd_unshare() vs GUP-fast race (bsc#1245431).\n- mm/hugetlb: unshare page tables during VMA split, not before (bsc#1245431).\n- net_sched: sch_fifo: implement lockless __fifo_dump() (bsc#1237312)\n- net_sched: sch_sfq: use a temporary work area for validating configuration (bsc#1232504)\n- ovl: fix use inode directly in rcu-walk mode (bsc#1241900).\n- powerpc/powernv/memtrace: Fix out of bounds issue in memtrace mmap (bsc#1244309 ltc#213790).\n- powerpc/vas: Return -EINVAL if the offset is non-zero in mmap() (bsc#1244309 ltc#213790).\n- scsi: storvsc: Do not report the host packet status as the hv status (git-fixes).\n- scsi: storvsc: Increase the timeouts to storvsc_timeout (bsc#1245455).\n","status":"withdrawn","published":"2025-07-10T08:25:37Z","modified":"2026-04-03T13:02:15.125957Z","updated_at":"2026-11-02T15:54:00.344164Z"}]}}