{"id":"CVE-2021-46984","aliases":["ALSA-2024:7000","ALSA-2024:7001","CLSA-2026-1777614954","CLSA-2026-1782145985","CLSA-2026-1788449727","CLSA-2026-1792239979","DEBIAN-CVE-2021-46984","EUVD-2021-33632","GHSA-4qp7-5rvw-5428","OESA-2024-1483","OESA-2024-1484","RHSA-2024:7000","RHSA-2024:7001","RLSA-2024:7000","RLSA-2024:7001","SUSE-SU-2024:1454-1","SUSE-SU-2024:1465-1","SUSE-SU-2024:1489-1","SUSE-SU-2025:02846-1","UBUNTU-CVE-2021-46984"],"status":"published","title":"kyber: fix out of bounds access when preempted","description":"In the Linux kernel, the following vulnerability has been resolved:\n\nkyber: fix out of bounds access when preempted\n\n__blk_mq_sched_bio_merge() gets the ctx and hctx for the current CPU and\npasses the hctx to -\u003ebio_merge(). kyber_bio_merge() then gets the ctx\nfor the current CPU again and uses that to get the corresponding Kyber\ncontext in the passed hctx. However, the thread may be preempted between\nthe two calls to blk_mq_get_ctx(), and the ctx returned the second time\nmay no longer correspond to the passed hctx. This \"works\" accidentally\nmost of the time, but it can cause us to read garbage if the second ctx\ncame from an hctx with more ctx's than the first one (i.e., if\nctx-\u003eindex_hw[hctx-\u003etype] \u003e hctx-\u003enr_ctx).\n\nThis manifested as this UBSAN array index out of bounds error reported\nby Jakub:\n\nUBSAN: array-index-out-of-bounds in ../kernel/locking/qspinlock.c:130:9\nindex 13106 is out of range for type 'long unsigned int [128]'\nCall Trace:\n dump_stack+0xa4/0xe5\n ubsan_epilogue+0x5/0x40\n __ubsan_handle_out_of_bounds.cold.13+0x2a/0x34\n queued_spin_lock_slowpath+0x476/0x480\n do_raw_spin_lock+0x1c2/0x1d0\n kyber_bio_merge+0x112/0x180\n blk_mq_submit_bio+0x1f5/0x1100\n submit_bio_noacct+0x7b0/0x870\n submit_bio+0xc2/0x3a0\n btrfs_map_bio+0x4f0/0x9d0\n btrfs_submit_data_bio+0x24e/0x310\n submit_one_bio+0x7f/0xb0\n submit_extent_page+0xc4/0x440\n __extent_writepage_io+0x2b8/0x5e0\n __extent_writepage+0x28d/0x6e0\n extent_write_cache_pages+0x4d7/0x7a0\n extent_writepages+0xa2/0x110\n do_writepages+0x8f/0x180\n __writeback_single_inode+0x99/0x7f0\n writeback_sb_inodes+0x34e/0x790\n __writeback_inodes_wb+0x9e/0x120\n wb_writeback+0x4d2/0x660\n wb_workfn+0x64d/0xa10\n process_one_work+0x53a/0xa80\n worker_thread+0x69/0x5b0\n kthread+0x20b/0x240\n ret_from_fork+0x1f/0x30\n\nOnly Kyber uses the hctx, so fix it by passing the request_queue to\n-\u003ebio_merge() instead. BFQ and mq-deadline just use that, and Kyber can\nmap the queues itself to avoid the mismatch.","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":"cna","from":"cve"},"epss":{"day":"2026-11-12","score":0.00258,"percentile":0.17684,"model":"v2026.06.15"},"facts":{"in_kev":false,"known_exploited":false,"public_exploit":false,"fix_available":true},"cwes":["CWE-129"],"published":"2024-02-28T08:13:12Z","modified":"2026-11-12T17:22:55Z","fixes":[{"ecosystem":"Debian:12","package":"linux","fixed_in":["5.10.38-1"],"sources":["osv"]},{"ecosystem":"Debian:13","package":"linux","fixed_in":["5.10.38-1"],"sources":["osv"]},{"ecosystem":"Debian:14","package":"linux","fixed_in":["5.10.38-1"],"sources":["osv"]},{"ecosystem":"Ubuntu:18.04:LTS","package":"linux-aws-5.4","fixed_in":["5.4.0-1054.57~18.04.1"],"sources":["osv"]},{"ecosystem":"Ubuntu:18.04:LTS","package":"linux-azure-5.4","fixed_in":["5.4.0-1055.57~18.04.1"],"sources":["osv"]},{"ecosystem":"Ubuntu:18.04:LTS","package":"linux-gcp-5.4","fixed_in":["5.4.0-1049.53~18.04.1"],"sources":["osv"]},{"ecosystem":"Ubuntu:18.04:LTS","package":"linux-hwe-5.4","fixed_in":["5.4.0-80.90~18.04.1"],"sources":["osv"]},{"ecosystem":"Ubuntu:18.04:LTS","package":"linux-oracle-5.4","fixed_in":["5.4.0-1052.56~18.04.1"],"sources":["osv"]},{"ecosystem":"Ubuntu:18.04:LTS","package":"linux-raspi-5.4","fixed_in":["5.4.0-1041.45~18.04.1"],"sources":["osv"]},{"ecosystem":"Ubuntu:20.04:LTS","package":"linux","fixed_in":["5.4.0-80.90"],"sources":["osv"]},{"ecosystem":"Ubuntu:20.04:LTS","package":"linux-aws","fixed_in":["5.4.0-1054.57"],"sources":["osv"]},{"ecosystem":"Ubuntu:20.04:LTS","package":"linux-azure","fixed_in":["5.4.0-1055.57"],"sources":["osv"]},{"ecosystem":"Ubuntu:20.04:LTS","package":"linux-bluefield","fixed_in":["5.4.0-1016.19"],"sources":["osv"]},{"ecosystem":"Ubuntu:20.04:LTS","package":"linux-gcp","fixed_in":["5.4.0-1049.53"],"sources":["osv"]},{"ecosystem":"Ubuntu:20.04:LTS","package":"linux-gkeop","fixed_in":["5.4.0-1021.22"],"sources":["osv"]},{"ecosystem":"Ubuntu:20.04:LTS","package":"linux-kvm","fixed_in":["5.4.0-1044.46"],"sources":["osv"]},{"ecosystem":"Ubuntu:20.04:LTS","package":"linux-oracle","fixed_in":["5.4.0-1052.56"],"sources":["osv"]},{"ecosystem":"Ubuntu:20.04:LTS","package":"linux-raspi","fixed_in":["5.4.0-1041.45"],"sources":["osv"]},{"ecosystem":"Ubuntu:Pro:FIPS-updates:20.04:LTS","package":"linux-aws-fips","fixed_in":["5.4.0-1069.73+fips2"],"sources":["osv"]},{"ecosystem":"Ubuntu:Pro:FIPS-updates:20.04:LTS","package":"linux-azure-fips","fixed_in":["5.4.0-1073.76+fips1"],"sources":["osv"]},{"ecosystem":"Ubuntu:Pro:FIPS-updates:20.04:LTS","package":"linux-fips","fixed_in":["5.4.0-1031.36"],"sources":["osv"]},{"ecosystem":"Ubuntu:Pro:FIPS-updates:20.04:LTS","package":"linux-gcp-fips","fixed_in":["5.4.0-1067.71~20.04.1"],"sources":["osv"]}],"affected":[{"source":"osv","ecosystem":"AlmaLinux:8","package":"bpftool","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.18.0-553.22.1.el8_10"}]}],"bundled":145},{"source":"osv","ecosystem":"AlmaLinux:8","package":"kernel","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.18.0-553.22.1.el8_10"}]}],"bundled":145},{"source":"osv","ecosystem":"AlmaLinux:8","package":"kernel-abi-stablelists","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.18.0-553.22.1.el8_10"}]}],"bundled":145},{"source":"osv","ecosystem":"AlmaLinux:8","package":"kernel-core","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.18.0-553.22.1.el8_10"}]}],"bundled":145},{"source":"osv","ecosystem":"AlmaLinux:8","package":"kernel-cross-headers","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.18.0-553.22.1.el8_10"}]}],"bundled":145},{"source":"osv","ecosystem":"AlmaLinux:8","package":"kernel-debug","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.18.0-553.22.1.el8_10"}]}],"bundled":145},{"source":"osv","ecosystem":"AlmaLinux:8","package":"kernel-debug-core","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.18.0-553.22.1.el8_10"}]}],"bundled":145},{"source":"osv","ecosystem":"AlmaLinux:8","package":"kernel-debug-devel","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.18.0-553.22.1.el8_10"}]}],"bundled":145},{"source":"osv","ecosystem":"AlmaLinux:8","package":"kernel-debug-modules","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.18.0-553.22.1.el8_10"}]}],"bundled":145},{"source":"osv","ecosystem":"AlmaLinux:8","package":"kernel-debug-modules-extra","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.18.0-553.22.1.el8_10"}]}],"bundled":145},{"source":"osv","ecosystem":"AlmaLinux:8","package":"kernel-devel","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.18.0-553.22.1.el8_10"}]}],"bundled":145},{"source":"osv","ecosystem":"AlmaLinux:8","package":"kernel-doc","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.18.0-553.22.1.el8_10"}]}],"bundled":145},{"source":"osv","ecosystem":"AlmaLinux:8","package":"kernel-headers","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.18.0-553.22.1.el8_10"}]}],"bundled":145},{"source":"osv","ecosystem":"AlmaLinux:8","package":"kernel-modules","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.18.0-553.22.1.el8_10"}]}],"bundled":145},{"source":"osv","ecosystem":"AlmaLinux:8","package":"kernel-modules-extra","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.18.0-553.22.1.el8_10"}]}],"bundled":145},{"source":"osv","ecosystem":"AlmaLinux:8","package":"kernel-tools","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.18.0-553.22.1.el8_10"}]}],"bundled":145},{"source":"osv","ecosystem":"AlmaLinux:8","package":"kernel-tools-libs","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.18.0-553.22.1.el8_10"}]}],"bundled":145},{"source":"osv","ecosystem":"AlmaLinux:8","package":"kernel-tools-libs-devel","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.18.0-553.22.1.el8_10"}]}],"bundled":145},{"source":"osv","ecosystem":"AlmaLinux:8","package":"kernel-zfcpdump","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.18.0-553.22.1.el8_10"}]}],"bundled":145},{"source":"osv","ecosystem":"AlmaLinux:8","package":"kernel-zfcpdump-core","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.18.0-553.22.1.el8_10"}]}],"bundled":145},{"source":"osv","ecosystem":"AlmaLinux:8","package":"kernel-zfcpdump-devel","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.18.0-553.22.1.el8_10"}]}],"bundled":145},{"source":"osv","ecosystem":"AlmaLinux:8","package":"kernel-zfcpdump-modules","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.18.0-553.22.1.el8_10"}]}],"bundled":145},{"source":"osv","ecosystem":"AlmaLinux:8","package":"kernel-zfcpdump-modules-extra","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.18.0-553.22.1.el8_10"}]}],"bundled":145},{"source":"osv","ecosystem":"AlmaLinux:8","package":"perf","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.18.0-553.22.1.el8_10"}]}],"bundled":145},{"source":"osv","ecosystem":"AlmaLinux:8","package":"python3-perf","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.18.0-553.22.1.el8_10"}]}],"bundled":145},{"source":"osv","ecosystem":"AlmaLinux:8","package":"kernel-rt","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.18.0-553.22.1.rt7.363.el8_10"}]}],"bundled":129},{"source":"osv","ecosystem":"AlmaLinux:8","package":"kernel-rt-core","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.18.0-553.22.1.rt7.363.el8_10"}]}],"bundled":129},{"source":"osv","ecosystem":"AlmaLinux:8","package":"kernel-rt-debug","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.18.0-553.22.1.rt7.363.el8_10"}]}],"bundled":129},{"source":"osv","ecosystem":"AlmaLinux:8","package":"kernel-rt-debug-core","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.18.0-553.22.1.rt7.363.el8_10"}]}],"bundled":129},{"source":"osv","ecosystem":"AlmaLinux:8","package":"kernel-rt-debug-devel","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.18.0-553.22.1.rt7.363.el8_10"}]}],"bundled":129},{"source":"osv","ecosystem":"AlmaLinux:8","package":"kernel-rt-debug-kvm","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.18.0-553.22.1.rt7.363.el8_10"}]}],"bundled":129},{"source":"osv","ecosystem":"AlmaLinux:8","package":"kernel-rt-debug-modules","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.18.0-553.22.1.rt7.363.el8_10"}]}],"bundled":129},{"source":"osv","ecosystem":"AlmaLinux:8","package":"kernel-rt-debug-modules-extra","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.18.0-553.22.1.rt7.363.el8_10"}]}],"bundled":129},{"source":"osv","ecosystem":"AlmaLinux:8","package":"kernel-rt-devel","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.18.0-553.22.1.rt7.363.el8_10"}]}],"bundled":129},{"source":"osv","ecosystem":"AlmaLinux:8","package":"kernel-rt-kvm","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.18.0-553.22.1.rt7.363.el8_10"}]}],"bundled":129},{"source":"osv","ecosystem":"AlmaLinux:8","package":"kernel-rt-modules","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.18.0-553.22.1.rt7.363.el8_10"}]}],"bundled":129},{"source":"osv","ecosystem":"AlmaLinux:8","package":"kernel-rt-modules-extra","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.18.0-553.22.1.rt7.363.el8_10"}]}],"bundled":129},{"source":"osv","ecosystem":"TuxCare:CentOS:8.5","package":"bpftool","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.18.0-348.7.1.el8_5.tuxcare.els36"}]}],"bundled":37},{"source":"osv","ecosystem":"TuxCare:CentOS:8.5","package":"kernel","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.18.0-348.7.1.el8_5.tuxcare.els36"}]}],"bundled":37},{"source":"osv","ecosystem":"TuxCare:CentOS:8.5","package":"kernel-core","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.18.0-348.7.1.el8_5.tuxcare.els36"}]}],"bundled":37},{"source":"osv","ecosystem":"TuxCare:CentOS:8.5","package":"kernel-cross-headers","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.18.0-348.7.1.el8_5.tuxcare.els36"}]}],"bundled":37},{"source":"osv","ecosystem":"TuxCare:CentOS:8.5","package":"kernel-debug","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.18.0-348.7.1.el8_5.tuxcare.els36"}]}],"bundled":37},{"source":"osv","ecosystem":"TuxCare:CentOS:8.5","package":"kernel-debug-core","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.18.0-348.7.1.el8_5.tuxcare.els36"}]}],"bundled":37},{"source":"osv","ecosystem":"TuxCare:CentOS:8.5","package":"kernel-debug-devel","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.18.0-348.7.1.el8_5.tuxcare.els36"}]}],"bundled":37},{"source":"osv","ecosystem":"TuxCare:CentOS:8.5","package":"kernel-debug-modules","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.18.0-348.7.1.el8_5.tuxcare.els36"}]}],"bundled":37},{"source":"osv","ecosystem":"TuxCare:CentOS:8.5","package":"kernel-debug-modules-extra","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.18.0-348.7.1.el8_5.tuxcare.els36"}]}],"bundled":37},{"source":"osv","ecosystem":"TuxCare:CentOS:8.5","package":"kernel-debug-modules-internal","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.18.0-348.7.1.el8_5.tuxcare.els36"}]}],"bundled":37},{"source":"osv","ecosystem":"TuxCare:CentOS:8.5","package":"kernel-devel","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.18.0-348.7.1.el8_5.tuxcare.els36"}]}],"bundled":37},{"source":"osv","ecosystem":"TuxCare:CentOS:8.5","package":"kernel-headers","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.18.0-348.7.1.el8_5.tuxcare.els36"}]}],"bundled":37},{"source":"osv","ecosystem":"TuxCare:CentOS:8.5","package":"kernel-ipaclones-internal","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.18.0-348.7.1.el8_5.tuxcare.els36"}]}],"bundled":37},{"source":"osv","ecosystem":"TuxCare:CentOS:8.5","package":"kernel-modules","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.18.0-348.7.1.el8_5.tuxcare.els36"}]}],"bundled":37},{"source":"osv","ecosystem":"TuxCare:CentOS:8.5","package":"kernel-modules-extra","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.18.0-348.7.1.el8_5.tuxcare.els36"}]}],"bundled":37},{"source":"osv","ecosystem":"TuxCare:CentOS:8.5","package":"kernel-modules-internal","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.18.0-348.7.1.el8_5.tuxcare.els36"}]}],"bundled":37},{"source":"osv","ecosystem":"TuxCare:CentOS:8.5","package":"kernel-selftests-internal","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.18.0-348.7.1.el8_5.tuxcare.els36"}]}],"bundled":37},{"source":"osv","ecosystem":"TuxCare:CentOS:8.5","package":"kernel-tools","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.18.0-348.7.1.el8_5.tuxcare.els36"}]}],"bundled":37},{"source":"osv","ecosystem":"TuxCare:CentOS:8.5","package":"kernel-tools-libs","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.18.0-348.7.1.el8_5.tuxcare.els36"}]}],"bundled":37},{"source":"osv","ecosystem":"TuxCare:CentOS:8.5","package":"kernel-tools-libs-devel","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.18.0-348.7.1.el8_5.tuxcare.els36"}]}],"bundled":37},{"source":"osv","ecosystem":"TuxCare:CentOS:8.5","package":"perf","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.18.0-348.7.1.el8_5.tuxcare.els36"}]}],"bundled":37},{"source":"osv","ecosystem":"TuxCare:CentOS:8.5","package":"python3-perf","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.18.0-348.7.1.el8_5.tuxcare.els36"}]}],"bundled":37},{"source":"osv","ecosystem":"TuxCare:CentOS:8.4","package":"bpftool","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.18.0-305.25.1.el8_4.tuxcare.els42"}]}],"bundled":59},{"source":"osv","ecosystem":"TuxCare:CentOS:8.4","package":"kernel","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.18.0-305.25.1.el8_4.tuxcare.els42"}]}],"bundled":59},{"source":"osv","ecosystem":"TuxCare:CentOS:8.4","package":"kernel-core","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.18.0-305.25.1.el8_4.tuxcare.els42"}]}],"bundled":59},{"source":"osv","ecosystem":"TuxCare:CentOS:8.4","package":"kernel-cross-headers","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.18.0-305.25.1.el8_4.tuxcare.els42"}]}],"bundled":59},{"source":"osv","ecosystem":"TuxCare:CentOS:8.4","package":"kernel-debug","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.18.0-305.25.1.el8_4.tuxcare.els42"}]}],"bundled":59},{"source":"osv","ecosystem":"TuxCare:CentOS:8.4","package":"kernel-debug-core","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.18.0-305.25.1.el8_4.tuxcare.els42"}]}],"bundled":59},{"source":"osv","ecosystem":"TuxCare:CentOS:8.4","package":"kernel-debug-devel","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.18.0-305.25.1.el8_4.tuxcare.els42"}]}],"bundled":59},{"source":"osv","ecosystem":"TuxCare:CentOS:8.4","package":"kernel-debug-modules","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.18.0-305.25.1.el8_4.tuxcare.els42"}]}],"bundled":59},{"source":"osv","ecosystem":"TuxCare:CentOS:8.4","package":"kernel-debug-modules-extra","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.18.0-305.25.1.el8_4.tuxcare.els42"}]}],"bundled":59},{"source":"osv","ecosystem":"TuxCare:CentOS:8.4","package":"kernel-debug-modules-internal","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.18.0-305.25.1.el8_4.tuxcare.els42"}]}],"bundled":59},{"source":"osv","ecosystem":"TuxCare:CentOS:8.4","package":"kernel-devel","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.18.0-305.25.1.el8_4.tuxcare.els42"}]}],"bundled":59},{"source":"osv","ecosystem":"TuxCare:CentOS:8.4","package":"kernel-headers","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.18.0-305.25.1.el8_4.tuxcare.els42"}]}],"bundled":59},{"source":"osv","ecosystem":"TuxCare:CentOS:8.4","package":"kernel-ipaclones-internal","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.18.0-305.25.1.el8_4.tuxcare.els42"}]}],"bundled":59},{"source":"osv","ecosystem":"TuxCare:CentOS:8.4","package":"kernel-modules","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.18.0-305.25.1.el8_4.tuxcare.els42"}]}],"bundled":59},{"source":"osv","ecosystem":"TuxCare:CentOS:8.4","package":"kernel-modules-extra","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.18.0-305.25.1.el8_4.tuxcare.els42"}]}],"bundled":59},{"source":"osv","ecosystem":"TuxCare:CentOS:8.4","package":"kernel-modules-internal","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.18.0-305.25.1.el8_4.tuxcare.els42"}]}],"bundled":59},{"source":"osv","ecosystem":"TuxCare:CentOS:8.4","package":"kernel-selftests-internal","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.18.0-305.25.1.el8_4.tuxcare.els42"}]}],"bundled":59},{"source":"osv","ecosystem":"TuxCare:CentOS:8.4","package":"kernel-tools","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.18.0-305.25.1.el8_4.tuxcare.els42"}]}],"bundled":59},{"source":"osv","ecosystem":"TuxCare:CentOS:8.4","package":"kernel-tools-libs","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.18.0-305.25.1.el8_4.tuxcare.els42"}]}],"bundled":59},{"source":"osv","ecosystem":"TuxCare:CentOS:8.4","package":"kernel-tools-libs-devel","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.18.0-305.25.1.el8_4.tuxcare.els42"}]}],"bundled":59},{"source":"osv","ecosystem":"TuxCare:CentOS:8.4","package":"perf","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.18.0-305.25.1.el8_4.tuxcare.els42"}]}],"bundled":59},{"source":"osv","ecosystem":"TuxCare:CentOS:8.4","package":"python3-perf","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.18.0-305.25.1.el8_4.tuxcare.els42"}]}],"bundled":59},{"source":"osv","ecosystem":"TuxCare:Debian:10","package":"hyperv-daemons","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.19.325-2+tuxcare.els1"}]}],"bundled":237},{"source":"osv","ecosystem":"TuxCare:Debian:10","package":"libbpf-dev","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.19.325-2+tuxcare.els1"}]}],"bundled":237},{"source":"osv","ecosystem":"TuxCare:Debian:10","package":"libbpf4.19","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.19.325-2+tuxcare.els1"}]}],"bundled":237},{"source":"osv","ecosystem":"TuxCare:Debian:10","package":"libcpupower-dev","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.19.325-2+tuxcare.els1"}]}],"bundled":237},{"source":"osv","ecosystem":"TuxCare:Debian:10","package":"libcpupower1","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.19.325-2+tuxcare.els1"}]}],"bundled":237},{"source":"osv","ecosystem":"TuxCare:Debian:10","package":"linux-compiler-gcc-8-x86","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.19.325-2+tuxcare.els1"}]}],"bundled":237},{"source":"osv","ecosystem":"TuxCare:Debian:10","package":"linux-config-4.19","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.19.325-2+tuxcare.els1"}]}],"bundled":237},{"source":"osv","ecosystem":"TuxCare:Debian:10","package":"linux-cpupower","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.19.325-2+tuxcare.els1"}]}],"bundled":237},{"source":"osv","ecosystem":"TuxCare:Debian:10","package":"linux-doc-4.19","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.19.325-2+tuxcare.els1"}]}],"bundled":237},{"source":"osv","ecosystem":"TuxCare:Debian:10","package":"linux-headers-4.19.0-29-all","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.19.325-2+tuxcare.els1"}]}],"bundled":237},{"source":"osv","ecosystem":"TuxCare:Debian:10","package":"linux-headers-4.19.0-29-all-amd64","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.19.325-2+tuxcare.els1"}]}],"bundled":237},{"source":"osv","ecosystem":"TuxCare:Debian:10","package":"linux-headers-4.19.0-29-amd64","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.19.325-2+tuxcare.els1"}]}],"bundled":237},{"source":"osv","ecosystem":"TuxCare:Debian:10","package":"linux-headers-4.19.0-29-common","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.19.325-2+tuxcare.els1"}]}],"bundled":237},{"source":"osv","ecosystem":"TuxCare:Debian:10","package":"linux-image-4.19.0-29-amd64-unsigned","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.19.325-2+tuxcare.els1"}]}],"bundled":237},{"source":"osv","ecosystem":"TuxCare:Debian:10","package":"linux-image-amd64-signed-template","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.19.325-2+tuxcare.els1"}]}],"bundled":237},{"source":"osv","ecosystem":"TuxCare:Debian:10","package":"linux-kbuild-4.19","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.19.325-2+tuxcare.els1"}]}],"bundled":237},{"source":"osv","ecosystem":"TuxCare:Debian:10","package":"linux-libc-dev","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.19.325-2+tuxcare.els1"}]}],"bundled":237},{"source":"osv","ecosystem":"TuxCare:Debian:10","package":"linux-perf-4.19","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.19.325-2+tuxcare.els1"}]}],"bundled":237},{"source":"osv","ecosystem":"TuxCare:Debian:10","package":"linux-source-4.19","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.19.325-2+tuxcare.els1"}]}],"bundled":237},{"source":"osv","ecosystem":"TuxCare:Debian:10","package":"linux-support-4.19.0-29","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.19.325-2+tuxcare.els1"}]}],"bundled":237},{"source":"osv","ecosystem":"TuxCare:Debian:10","package":"linux-headers-4.19.0-29-all-arm64","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.19.325-2+tuxcare.els1"}]}],"bundled":237},{"source":"osv","ecosystem":"TuxCare:Debian:10","package":"linux-headers-4.19.0-29-arm64","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.19.325-2+tuxcare.els1"}]}],"bundled":237},{"source":"osv","ecosystem":"TuxCare:Debian:10","package":"linux-image-4.19.0-29-arm64-unsigned","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.19.325-2+tuxcare.els1"}]}],"bundled":237},{"source":"osv","ecosystem":"TuxCare:Debian:10","package":"linux-image-arm64-signed-template","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.19.325-2+tuxcare.els1"}]}],"bundled":237},{"source":"osv","ecosystem":"TuxCare:Debian:10","package":"linux-compiler-gcc-8-arm","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.19.325-2+tuxcare.els1"}]}],"bundled":237},{"source":"osv","ecosystem":"TuxCare:Debian:10","package":"linux-headers-4.19.0-29-all-armel","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.19.325-2+tuxcare.els1"}]}],"bundled":237},{"source":"osv","ecosystem":"TuxCare:Debian:10","package":"linux-headers-4.19.0-29-marvell","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.19.325-2+tuxcare.els1"}]}],"bundled":237},{"source":"osv","ecosystem":"TuxCare:Debian:10","package":"linux-headers-4.19.0-29-rpi","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.19.325-2+tuxcare.els1"}]}],"bundled":237},{"source":"osv","ecosystem":"TuxCare:Debian:10","package":"linux-image-4.19.0-29-marvell","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.19.325-2+tuxcare.els1"}]}],"bundled":237},{"source":"osv","ecosystem":"TuxCare:Debian:10","package":"linux-image-4.19.0-29-rpi","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.19.325-2+tuxcare.els1"}]}],"bundled":237},{"source":"osv","ecosystem":"TuxCare:CentOS-Stream:8","package":"bpftool","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.18.0-553.6.1.el8_10.tuxcare.els32"}]}],"bundled":83},{"source":"osv","ecosystem":"TuxCare:CentOS-Stream:8","package":"kernel","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.18.0-553.6.1.el8_10.tuxcare.els32"}]}],"bundled":83},{"source":"osv","ecosystem":"TuxCare:CentOS-Stream:8","package":"kernel-core","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.18.0-553.6.1.el8_10.tuxcare.els32"}]}],"bundled":83},{"source":"osv","ecosystem":"TuxCare:CentOS-Stream:8","package":"kernel-cross-headers","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.18.0-553.6.1.el8_10.tuxcare.els32"}]}],"bundled":83},{"source":"osv","ecosystem":"TuxCare:CentOS-Stream:8","package":"kernel-debug","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.18.0-553.6.1.el8_10.tuxcare.els32"}]}],"bundled":83},{"source":"osv","ecosystem":"TuxCare:CentOS-Stream:8","package":"kernel-debug-core","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.18.0-553.6.1.el8_10.tuxcare.els32"}]}],"bundled":83},{"source":"osv","ecosystem":"TuxCare:CentOS-Stream:8","package":"kernel-debug-devel","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.18.0-553.6.1.el8_10.tuxcare.els32"}]}],"bundled":83},{"source":"osv","ecosystem":"TuxCare:CentOS-Stream:8","package":"kernel-debug-modules","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.18.0-553.6.1.el8_10.tuxcare.els32"}]}],"bundled":83},{"source":"osv","ecosystem":"TuxCare:CentOS-Stream:8","package":"kernel-debug-modules-extra","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.18.0-553.6.1.el8_10.tuxcare.els32"}]}],"bundled":83},{"source":"osv","ecosystem":"TuxCare:CentOS-Stream:8","package":"kernel-debug-modules-internal","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.18.0-553.6.1.el8_10.tuxcare.els32"}]}],"bundled":83},{"source":"osv","ecosystem":"TuxCare:CentOS-Stream:8","package":"kernel-devel","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.18.0-553.6.1.el8_10.tuxcare.els32"}]}],"bundled":83},{"source":"osv","ecosystem":"TuxCare:CentOS-Stream:8","package":"kernel-headers","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.18.0-553.6.1.el8_10.tuxcare.els32"}]}],"bundled":83},{"source":"osv","ecosystem":"TuxCare:CentOS-Stream:8","package":"kernel-ipaclones-internal","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.18.0-553.6.1.el8_10.tuxcare.els32"}]}],"bundled":83},{"source":"osv","ecosystem":"TuxCare:CentOS-Stream:8","package":"kernel-modules","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.18.0-553.6.1.el8_10.tuxcare.els32"}]}],"bundled":83},{"source":"osv","ecosystem":"TuxCare:CentOS-Stream:8","package":"kernel-modules-extra","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.18.0-553.6.1.el8_10.tuxcare.els32"}]}],"bundled":83},{"source":"osv","ecosystem":"TuxCare:CentOS-Stream:8","package":"kernel-modules-internal","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.18.0-553.6.1.el8_10.tuxcare.els32"}]}],"bundled":83},{"source":"osv","ecosystem":"TuxCare:CentOS-Stream:8","package":"kernel-selftests-internal","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.18.0-553.6.1.el8_10.tuxcare.els32"}]}],"bundled":83},{"source":"osv","ecosystem":"TuxCare:CentOS-Stream:8","package":"kernel-tools","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.18.0-553.6.1.el8_10.tuxcare.els32"}]}],"bundled":83},{"source":"osv","ecosystem":"TuxCare:CentOS-Stream:8","package":"kernel-tools-libs","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.18.0-553.6.1.el8_10.tuxcare.els32"}]}],"bundled":83},{"source":"osv","ecosystem":"TuxCare:CentOS-Stream:8","package":"kernel-tools-libs-devel","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.18.0-553.6.1.el8_10.tuxcare.els32"}]}],"bundled":83},{"source":"osv","ecosystem":"TuxCare:CentOS-Stream:8","package":"perf","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.18.0-553.6.1.el8_10.tuxcare.els32"}]}],"bundled":83},{"source":"osv","ecosystem":"TuxCare:CentOS-Stream:8","package":"python3-perf","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.18.0-553.6.1.el8_10.tuxcare.els32"}]}],"bundled":83},{"source":"osv","ecosystem":"Debian:12","package":"linux","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.10.38-1"}]}]},{"source":"osv","ecosystem":"Debian:13","package":"linux","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.10.38-1"}]}]},{"source":"osv","ecosystem":"Debian:14","package":"linux","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.10.38-1"}]}]},{"source":"osv","ecosystem":"openEuler:20.03-LTS-SP1","package":"kernel","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.19.90-2404.2.0.0246.oe1"}]}],"bundled":46},{"source":"osv","ecosystem":"openEuler:20.03-LTS-SP4","package":"kernel","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.19.90-2404.2.0.0273.oe2003sp4"}]}],"bundled":46},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:8::baseos","package":"bpftool","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:4.18.0-553.22.1.el8_10"}]}],"bundled":151},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:8::baseos","package":"bpftool-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:4.18.0-553.22.1.el8_10"}]}],"bundled":151},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:8::baseos","package":"kernel","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:4.18.0-553.22.1.el8_10"}]}],"bundled":151},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:8::baseos","package":"kernel-abi-stablelists","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:4.18.0-553.22.1.el8_10"}]}],"bundled":151},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:8::baseos","package":"kernel-core","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:4.18.0-553.22.1.el8_10"}]}],"bundled":151},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:8::baseos","package":"kernel-debug","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:4.18.0-553.22.1.el8_10"}]}],"bundled":151},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:8::baseos","package":"kernel-debug-core","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:4.18.0-553.22.1.el8_10"}]}],"bundled":151},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:8::baseos","package":"kernel-debug-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:4.18.0-553.22.1.el8_10"}]}],"bundled":151},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:8::baseos","package":"kernel-debug-devel","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:4.18.0-553.22.1.el8_10"}]}],"bundled":151},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:8::baseos","package":"kernel-debug-modules","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:4.18.0-553.22.1.el8_10"}]}],"bundled":151},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:8::baseos","package":"kernel-debug-modules-extra","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:4.18.0-553.22.1.el8_10"}]}],"bundled":151},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:8::baseos","package":"kernel-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:4.18.0-553.22.1.el8_10"}]}],"bundled":151},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:8::baseos","package":"kernel-debuginfo-common-aarch64","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:4.18.0-553.22.1.el8_10"}]}],"bundled":151},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:8::baseos","package":"kernel-debuginfo-common-ppc64le","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:4.18.0-553.22.1.el8_10"}]}],"bundled":151},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:8::baseos","package":"kernel-debuginfo-common-s390x","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:4.18.0-553.22.1.el8_10"}]}],"bundled":151},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:8::baseos","package":"kernel-debuginfo-common-x86_64","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:4.18.0-553.22.1.el8_10"}]}],"bundled":151},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:8::baseos","package":"kernel-devel","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:4.18.0-553.22.1.el8_10"}]}],"bundled":151},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:8::baseos","package":"kernel-doc","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:4.18.0-553.22.1.el8_10"}]}],"bundled":151},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:8::baseos","package":"kernel-modules","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:4.18.0-553.22.1.el8_10"}]}],"bundled":151},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:8::baseos","package":"kernel-modules-extra","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:4.18.0-553.22.1.el8_10"}]}],"bundled":151},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:8::baseos","package":"kernel-tools","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:4.18.0-553.22.1.el8_10"}]}],"bundled":151},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:8::baseos","package":"kernel-tools-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:4.18.0-553.22.1.el8_10"}]}],"bundled":151},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:8::baseos","package":"kernel-tools-libs","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:4.18.0-553.22.1.el8_10"}]}],"bundled":151},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:8::baseos","package":"kernel-zfcpdump","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:4.18.0-553.22.1.el8_10"}]}],"bundled":151},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:8::baseos","package":"kernel-zfcpdump-core","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:4.18.0-553.22.1.el8_10"}]}],"bundled":151},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:8::baseos","package":"kernel-zfcpdump-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:4.18.0-553.22.1.el8_10"}]}],"bundled":151},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:8::baseos","package":"kernel-zfcpdump-devel","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:4.18.0-553.22.1.el8_10"}]}],"bundled":151},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:8::baseos","package":"kernel-zfcpdump-modules","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:4.18.0-553.22.1.el8_10"}]}],"bundled":151},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:8::baseos","package":"kernel-zfcpdump-modules-extra","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:4.18.0-553.22.1.el8_10"}]}],"bundled":151},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:8::baseos","package":"perf","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:4.18.0-553.22.1.el8_10"}]}],"bundled":151},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:8::baseos","package":"perf-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:4.18.0-553.22.1.el8_10"}]}],"bundled":151},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:8::baseos","package":"python3-perf","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:4.18.0-553.22.1.el8_10"}]}],"bundled":151},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:8::baseos","package":"python3-perf-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:4.18.0-553.22.1.el8_10"}]}],"bundled":151},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:8::crb","package":"bpftool-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:4.18.0-553.22.1.el8_10"}]}],"bundled":151},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:8::crb","package":"kernel-debug-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:4.18.0-553.22.1.el8_10"}]}],"bundled":151},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:8::crb","package":"kernel-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:4.18.0-553.22.1.el8_10"}]}],"bundled":151},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:8::crb","package":"kernel-debuginfo-common-aarch64","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:4.18.0-553.22.1.el8_10"}]}],"bundled":151},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:8::crb","package":"kernel-debuginfo-common-ppc64le","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:4.18.0-553.22.1.el8_10"}]}],"bundled":151},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:8::crb","package":"kernel-debuginfo-common-x86_64","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:4.18.0-553.22.1.el8_10"}]}],"bundled":151},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:8::crb","package":"kernel-tools-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:4.18.0-553.22.1.el8_10"}]}],"bundled":151},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:8::crb","package":"kernel-tools-libs-devel","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:4.18.0-553.22.1.el8_10"}]}],"bundled":151},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:8::crb","package":"perf-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:4.18.0-553.22.1.el8_10"}]}],"bundled":151},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:8::crb","package":"python3-perf-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:4.18.0-553.22.1.el8_10"}]}],"bundled":151},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:8::nfv","package":"kernel-rt","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:4.18.0-553.22.1.rt7.363.el8_10"}]}],"bundled":129},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:8::nfv","package":"kernel-rt-core","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:4.18.0-553.22.1.rt7.363.el8_10"}]}],"bundled":129},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:8::nfv","package":"kernel-rt-debug","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:4.18.0-553.22.1.rt7.363.el8_10"}]}],"bundled":129},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:8::nfv","package":"kernel-rt-debug-core","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:4.18.0-553.22.1.rt7.363.el8_10"}]}],"bundled":129},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:8::nfv","package":"kernel-rt-debug-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:4.18.0-553.22.1.rt7.363.el8_10"}]}],"bundled":129},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:8::nfv","package":"kernel-rt-debug-devel","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:4.18.0-553.22.1.rt7.363.el8_10"}]}],"bundled":129},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:8::nfv","package":"kernel-rt-debug-kvm","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:4.18.0-553.22.1.rt7.363.el8_10"}]}],"bundled":129},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:8::nfv","package":"kernel-rt-debug-modules","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:4.18.0-553.22.1.rt7.363.el8_10"}]}],"bundled":129},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:8::nfv","package":"kernel-rt-debug-modules-extra","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:4.18.0-553.22.1.rt7.363.el8_10"}]}],"bundled":129},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:8::nfv","package":"kernel-rt-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:4.18.0-553.22.1.rt7.363.el8_10"}]}],"bundled":129},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:8::nfv","package":"kernel-rt-debuginfo-common-x86_64","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:4.18.0-553.22.1.rt7.363.el8_10"}]}],"bundled":129},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:8::nfv","package":"kernel-rt-devel","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:4.18.0-553.22.1.rt7.363.el8_10"}]}],"bundled":129},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:8::nfv","package":"kernel-rt-kvm","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:4.18.0-553.22.1.rt7.363.el8_10"}]}],"bundled":129},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:8::nfv","package":"kernel-rt-modules","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:4.18.0-553.22.1.rt7.363.el8_10"}]}],"bundled":129},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:8::nfv","package":"kernel-rt-modules-extra","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:4.18.0-553.22.1.rt7.363.el8_10"}]}],"bundled":129},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:8::realtime","package":"kernel-rt","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:4.18.0-553.22.1.rt7.363.el8_10"}]}],"bundled":129},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:8::realtime","package":"kernel-rt-core","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:4.18.0-553.22.1.rt7.363.el8_10"}]}],"bundled":129},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:8::realtime","package":"kernel-rt-debug","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:4.18.0-553.22.1.rt7.363.el8_10"}]}],"bundled":129},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:8::realtime","package":"kernel-rt-debug-core","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:4.18.0-553.22.1.rt7.363.el8_10"}]}],"bundled":129},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:8::realtime","package":"kernel-rt-debug-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:4.18.0-553.22.1.rt7.363.el8_10"}]}],"bundled":129},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:8::realtime","package":"kernel-rt-debug-devel","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:4.18.0-553.22.1.rt7.363.el8_10"}]}],"bundled":129},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:8::realtime","package":"kernel-rt-debug-modules","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:4.18.0-553.22.1.rt7.363.el8_10"}]}],"bundled":129},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:8::realtime","package":"kernel-rt-debug-modules-extra","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:4.18.0-553.22.1.rt7.363.el8_10"}]}],"bundled":129},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:8::realtime","package":"kernel-rt-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:4.18.0-553.22.1.rt7.363.el8_10"}]}],"bundled":129},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:8::realtime","package":"kernel-rt-debuginfo-common-x86_64","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:4.18.0-553.22.1.rt7.363.el8_10"}]}],"bundled":129},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:8::realtime","package":"kernel-rt-devel","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:4.18.0-553.22.1.rt7.363.el8_10"}]}],"bundled":129},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:8::realtime","package":"kernel-rt-modules","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:4.18.0-553.22.1.rt7.363.el8_10"}]}],"bundled":129},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:8::realtime","package":"kernel-rt-modules-extra","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:4.18.0-553.22.1.rt7.363.el8_10"}]}],"bundled":129},{"source":"osv","ecosystem":"Rocky Linux:8","package":"kernel","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:4.18.0-553.22.1.el8_10"}]}],"bundled":147},{"source":"osv","ecosystem":"Rocky Linux:8","package":"kernel-rt","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:4.18.0-553.22.1.rt7.363.el8_10"}]}],"bundled":129},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Live Patching 15 SP2","package":"kernel-default","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.3.18-150200.24.188.1"}]}],"bundled":114},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Live Patching 15 SP2","package":"kernel-livepatch-SLE15-SP2_Update_47","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1-150200.5.3.3"}]}],"bundled":114},{"source":"osv","ecosystem":"SUSE:Linux Enterprise High Availability Extension 15 SP2","package":"kernel-default","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.3.18-150200.24.188.1"}]}],"bundled":114},{"source":"osv","ecosystem":"SUSE:Linux Enterprise High Performance Computing 15 SP2-LTSS","package":"kernel-default","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.3.18-150200.24.188.1"}]}],"bundled":114},{"source":"osv","ecosystem":"SUSE:Linux Enterprise High Performance Computing 15 SP2-LTSS","package":"kernel-default-base","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.3.18-150200.24.188.1.150200.9.95.3"}]}],"bundled":114},{"source":"osv","ecosystem":"SUSE:Linux Enterprise High Performance Computing 15 SP2-LTSS","package":"kernel-docs","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.3.18-150200.24.188.1"}]}],"bundled":114},{"source":"osv","ecosystem":"SUSE:Linux Enterprise High Performance Computing 15 SP2-LTSS","package":"kernel-obs-build","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.3.18-150200.24.188.1"}]}],"bundled":114},{"source":"osv","ecosystem":"SUSE:Linux Enterprise High Performance Computing 15 SP2-LTSS","package":"kernel-preempt","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.3.18-150200.24.188.1"}]}],"bundled":114},{"source":"osv","ecosystem":"SUSE:Linux Enterprise High Performance Computing 15 SP2-LTSS","package":"kernel-source","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.3.18-150200.24.188.1"}]}],"bundled":114},{"source":"osv","ecosystem":"SUSE:Linux Enterprise High Performance Computing 15 SP2-LTSS","package":"kernel-syms","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.3.18-150200.24.188.1"}]}],"bundled":114},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server 15 SP2-LTSS","package":"kernel-default","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.3.18-150200.24.188.1"}]}],"bundled":114},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server 15 SP2-LTSS","package":"kernel-default-base","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.3.18-150200.24.188.1.150200.9.95.3"}]}],"bundled":114},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server 15 SP2-LTSS","package":"kernel-docs","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.3.18-150200.24.188.1"}]}],"bundled":114},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server 15 SP2-LTSS","package":"kernel-obs-build","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.3.18-150200.24.188.1"}]}],"bundled":114},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server 15 SP2-LTSS","package":"kernel-preempt","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.3.18-150200.24.188.1"}]}],"bundled":114},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server 15 SP2-LTSS","package":"kernel-source","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.3.18-150200.24.188.1"}]}],"bundled":114},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server 15 SP2-LTSS","package":"kernel-syms","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.3.18-150200.24.188.1"}]}],"bundled":114},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server for SAP Applications 15 SP2","package":"kernel-default","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.3.18-150200.24.188.1"}]}],"bundled":114},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server for SAP Applications 15 SP2","package":"kernel-default-base","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.3.18-150200.24.188.1.150200.9.95.3"}]}],"bundled":114},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server for SAP Applications 15 SP2","package":"kernel-docs","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.3.18-150200.24.188.1"}]}],"bundled":114},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server for SAP Applications 15 SP2","package":"kernel-obs-build","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.3.18-150200.24.188.1"}]}],"bundled":114},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server for SAP Applications 15 SP2","package":"kernel-preempt","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.3.18-150200.24.188.1"}]}],"bundled":114},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server for SAP Applications 15 SP2","package":"kernel-source","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.3.18-150200.24.188.1"}]}],"bundled":114},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server for SAP Applications 15 SP2","package":"kernel-syms","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.3.18-150200.24.188.1"}]}],"bundled":114},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Micro 5.1","package":"kernel-rt","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.3.18-150300.166.1"}]}],"bundled":145},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Micro 5.1","package":"kernel-source-rt","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.3.18-150300.166.1"}]}],"bundled":145},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Micro 5.2","package":"kernel-rt","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.3.18-150300.166.1"}]}],"bundled":145},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Micro 5.2","package":"kernel-source-rt","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.3.18-150300.166.1"}]}],"bundled":145},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Live Patching 15 SP3","package":"kernel-default","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.3.18-150300.59.158.1"}]}],"bundled":157},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Live Patching 15 SP3","package":"kernel-livepatch-SLE15-SP3_Update_43","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1-150300.7.3.5"}]}],"bundled":157},{"source":"osv","ecosystem":"SUSE:Linux Enterprise High Availability Extension 15 SP3","package":"kernel-default","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.3.18-150300.59.158.1"}]}],"bundled":157},{"source":"osv","ecosystem":"SUSE:Linux Enterprise High Performance Computing 15 SP3-LTSS","package":"kernel-64kb","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.3.18-150300.59.158.1"}]}],"bundled":157},{"source":"osv","ecosystem":"SUSE:Linux Enterprise High Performance Computing 15 SP3-LTSS","package":"kernel-default","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.3.18-150300.59.158.1"}]}],"bundled":157},{"source":"osv","ecosystem":"SUSE:Linux Enterprise High Performance Computing 15 SP3-LTSS","package":"kernel-default-base","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.3.18-150300.59.158.1.150300.18.92.5"}]}],"bundled":157},{"source":"osv","ecosystem":"SUSE:Linux Enterprise High Performance Computing 15 SP3-LTSS","package":"kernel-docs","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.3.18-150300.59.158.1"}]}],"bundled":157},{"source":"osv","ecosystem":"SUSE:Linux Enterprise High Performance Computing 15 SP3-LTSS","package":"kernel-obs-build","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.3.18-150300.59.158.1"}]}],"bundled":157},{"source":"osv","ecosystem":"SUSE:Linux Enterprise High Performance Computing 15 SP3-LTSS","package":"kernel-preempt","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.3.18-150300.59.158.1"}]}],"bundled":157},{"source":"osv","ecosystem":"SUSE:Linux Enterprise High Performance Computing 15 SP3-LTSS","package":"kernel-source","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.3.18-150300.59.158.1"}]}],"bundled":157},{"source":"osv","ecosystem":"SUSE:Linux Enterprise High Performance Computing 15 SP3-LTSS","package":"kernel-syms","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.3.18-150300.59.158.1"}]}],"bundled":157},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server 15 SP3-LTSS","package":"kernel-64kb","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.3.18-150300.59.158.1"}]}],"bundled":157},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server 15 SP3-LTSS","package":"kernel-default","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.3.18-150300.59.158.1"}]}],"bundled":157},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server 15 SP3-LTSS","package":"kernel-default-base","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.3.18-150300.59.158.1.150300.18.92.5"}]}],"bundled":157},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server 15 SP3-LTSS","package":"kernel-docs","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.3.18-150300.59.158.1"}]}],"bundled":157},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server 15 SP3-LTSS","package":"kernel-obs-build","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.3.18-150300.59.158.1"}]}],"bundled":157},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server 15 SP3-LTSS","package":"kernel-preempt","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.3.18-150300.59.158.1"}]}],"bundled":157},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server 15 SP3-LTSS","package":"kernel-source","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.3.18-150300.59.158.1"}]}],"bundled":157},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server 15 SP3-LTSS","package":"kernel-syms","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.3.18-150300.59.158.1"}]}],"bundled":157},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server 15 SP3-LTSS","package":"kernel-zfcpdump","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.3.18-150300.59.158.1"}]}],"bundled":157},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server for SAP Applications 15 SP3","package":"kernel-default","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.3.18-150300.59.158.1"}]}],"bundled":157},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server for SAP Applications 15 SP3","package":"kernel-default-base","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.3.18-150300.59.158.1.150300.18.92.5"}]}],"bundled":157},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server for SAP Applications 15 SP3","package":"kernel-docs","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.3.18-150300.59.158.1"}]}],"bundled":157},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server for SAP Applications 15 SP3","package":"kernel-obs-build","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.3.18-150300.59.158.1"}]}],"bundled":157},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server for SAP Applications 15 SP3","package":"kernel-preempt","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.3.18-150300.59.158.1"}]}],"bundled":157},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server for SAP Applications 15 SP3","package":"kernel-source","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.3.18-150300.59.158.1"}]}],"bundled":157},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server for SAP Applications 15 SP3","package":"kernel-syms","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.3.18-150300.59.158.1"}]}],"bundled":157},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Micro 5.1","package":"kernel-default","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.3.18-150300.59.158.1"}]}],"bundled":157},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Micro 5.1","package":"kernel-default-base","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.3.18-150300.59.158.1.150300.18.92.5"}]}],"bundled":157},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Micro 5.2","package":"kernel-default","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.3.18-150300.59.158.1"}]}],"bundled":157},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Micro 5.2","package":"kernel-default-base","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.3.18-150300.59.158.1.150300.18.92.5"}]}],"bundled":157},{"source":"osv","ecosystem":"SUSE:Enterprise Storage 7.1","package":"kernel-64kb","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.3.18-150300.59.158.1"}]}],"bundled":157},{"source":"osv","ecosystem":"SUSE:Enterprise Storage 7.1","package":"kernel-default","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.3.18-150300.59.158.1"}]}],"bundled":157},{"source":"osv","ecosystem":"SUSE:Enterprise Storage 7.1","package":"kernel-default-base","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.3.18-150300.59.158.1.150300.18.92.5"}]}],"bundled":157},{"source":"osv","ecosystem":"SUSE:Enterprise Storage 7.1","package":"kernel-docs","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.3.18-150300.59.158.1"}]}],"bundled":157},{"source":"osv","ecosystem":"SUSE:Enterprise Storage 7.1","package":"kernel-obs-build","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.3.18-150300.59.158.1"}]}],"bundled":157},{"source":"osv","ecosystem":"SUSE:Enterprise Storage 7.1","package":"kernel-preempt","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.3.18-150300.59.158.1"}]}],"bundled":157},{"source":"osv","ecosystem":"SUSE:Enterprise Storage 7.1","package":"kernel-source","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.3.18-150300.59.158.1"}]}],"bundled":157},{"source":"osv","ecosystem":"SUSE:Enterprise Storage 7.1","package":"kernel-syms","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.3.18-150300.59.158.1"}]}],"bundled":157},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Live Patching 12 SP5","package":"kernel-default","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.12.14-122.269.1"}]}],"bundled":83},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Live Patching 12 SP5","package":"kgraft-patch-SLE12-SP5_Update_71","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1-8.3.1"}]}],"bundled":83},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server 12 SP5-LTSS","package":"kernel-default","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.12.14-122.269.1"}]}],"bundled":83},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server 12 SP5-LTSS","package":"kernel-source","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.12.14-122.269.1"}]}],"bundled":83},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server 12 SP5-LTSS","package":"kernel-syms","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.12.14-122.269.1"}]}],"bundled":83},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server LTSS Extended Security 12 SP5","package":"kernel-default","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.12.14-122.269.1"}]}],"bundled":83},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server LTSS Extended Security 12 SP5","package":"kernel-source","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.12.14-122.269.1"}]}],"bundled":83},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server LTSS Extended Security 12 SP5","package":"kernel-syms","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.12.14-122.269.1"}]}],"bundled":83},{"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.4","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.4.0-1054.57~18.04.1"}]}],"versions":["5.4.0-1018.18~18.04.1","5.4.0-1020.20~18.04.2","5.4.0-1022.22~18.04.1","5.4.0-1024.24~18.04.1","5.4.0-1025.25~18.04.1","5.4.0-1028.29~18.04.1","5.4.0-1029.30~18.04.1","5.4.0-1030.31~18.04.1","5.4.0-1032.33~18.04.1","5.4.0-1034.35~18.04.1","5.4.0-1035.37~18.04.1","5.4.0-1037.39~18.04.1","5.4.0-1038.40~18.04.1","5.4.0-1039.41~18.04.1","5.4.0-1041.43~18.04.1","5.4.0-1043.45~18.04.1","5.4.0-1045.47~18.04.1","5.4.0-1047.49~18.04.1","5.4.0-1048.50~18.04.1","5.4.0-1049.51~18.04.1","5.4.0-1051.53~18.04.1"]},{"source":"osv","ecosystem":"Ubuntu:18.04:LTS","package":"linux-azure-5.4","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.4.0-1055.57~18.04.1"}]}],"versions":["5.4.0-1020.20~18.04.1","5.4.0-1022.22~18.04.1","5.4.0-1023.23~18.04.1","5.4.0-1025.25~18.04.1","5.4.0-1026.26~18.04.1","5.4.0-1031.32~18.04.1","5.4.0-1032.33~18.04.1","5.4.0-1034.35~18.04.1","5.4.0-1035.36~18.04.1","5.4.0-1036.38~18.04.1","5.4.0-1039.41~18.04.1","5.4.0-1040.42~18.04.1","5.4.0-1041.43~18.04.1","5.4.0-1043.45~18.04.1","5.4.0-1044.46~18.04.1","5.4.0-1046.48~18.04.1","5.4.0-1047.49~18.04.1","5.4.0-1048.50~18.04.1","5.4.0-1049.51~18.04.1","5.4.0-1051.53~18.04.1"]},{"source":"osv","ecosystem":"Ubuntu:18.04:LTS","package":"linux-gcp-5.4","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.4.0-1049.53~18.04.1"}]}],"versions":["5.4.0-1019.19~18.04.2","5.4.0-1021.21~18.04.1","5.4.0-1022.22~18.04.1","5.4.0-1024.24~18.04.1","5.4.0-1025.25~18.04.1","5.4.0-1028.29~18.04.1","5.4.0-1029.31~18.04.1","5.4.0-1030.32~18.04.1","5.4.0-1032.34~18.04.1","5.4.0-1033.35~18.04.1","5.4.0-1034.37~18.04.1","5.4.0-1036.39~18.04.1","5.4.0-1037.40~18.04.1","5.4.0-1038.41~18.04.1","5.4.0-1040.43~18.04.1","5.4.0-1041.44~18.04.1","5.4.0-1042.45~18.04.1","5.4.0-1043.46~18.04.1","5.4.0-1044.47~18.04.2","5.4.0-1046.49~18.04.1"]},{"source":"osv","ecosystem":"Ubuntu:18.04:LTS","package":"linux-hwe-5.4","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.4.0-80.90~18.04.1"}]}],"versions":["5.4.0-37.41~18.04.1","5.4.0-39.43~18.04.1","5.4.0-40.44~18.04.1","5.4.0-42.46~18.04.1","5.4.0-45.49~18.04.2","5.4.0-47.51~18.04.1","5.4.0-48.52~18.04.1","5.4.0-51.56~18.04.1","5.4.0-52.57~18.04.1","5.4.0-53.59~18.04.1","5.4.0-54.60~18.04.1","5.4.0-56.62~18.04.1","5.4.0-58.64~18.04.1","5.4.0-59.65~18.04.1","5.4.0-60.67~18.04.1","5.4.0-62.70~18.04.1","5.4.0-64.72~18.04.1","5.4.0-65.73~18.04.1","5.4.0-66.74~18.04.2","5.4.0-67.75~18.04.1","5.4.0-70.78~18.04.1","5.4.0-71.79~18.04.1","5.4.0-72.80~18.04.1","5.4.0-73.82~18.04.1","5.4.0-74.83~18.04.1","5.4.0-77.86~18.04.1"]},{"source":"osv","ecosystem":"Ubuntu:18.04:LTS","package":"linux-oracle-5.4","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.4.0-1052.56~18.04.1"}]}],"versions":["5.4.0-1019.19~18.04.1","5.4.0-1021.21~18.04.1","5.4.0-1022.22~18.04.1","5.4.0-1024.24~18.04.1","5.4.0-1025.25~18.04.1","5.4.0-1028.29~18.04.1","5.4.0-1029.31~18.04.1","5.4.0-1030.32~18.04.1","5.4.0-1033.35","5.4.0-1034.36~18.04.1","5.4.0-1035.38~18.04.1","5.4.0-1037.40~18.04.1","5.4.0-1038.41~18.04.1","5.4.0-1039.42~18.04.1","5.4.0-1041.44~18.04.1","5.4.0-1042.45~18.04.1","5.4.0-1043.46~18.04.1","5.4.0-1044.47~18.04.1","5.4.0-1046.50~18.04.2","5.4.0-1048.52~18.04.1","5.4.0-1049.53~18.04.1"]},{"source":"osv","ecosystem":"Ubuntu:18.04:LTS","package":"linux-raspi-5.4","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.4.0-1041.45~18.04.1"}]}],"versions":["5.4.0-1013.13~18.04.1","5.4.0-1015.15~18.04.1","5.4.0-1016.17~18.04.1","5.4.0-1018.20~18.04.1","5.4.0-1019.21~18.04.1","5.4.0-1021.24~18.04.1","5.4.0-1022.25~18.04.1","5.4.0-1023.26~18.04.1","5.4.0-1025.28~18.04.1","5.4.0-1026.29~18.04.1","5.4.0-1028.31~18.04.1","5.4.0-1029.32~18.04.1","5.4.0-1030.33~18.04.1","5.4.0-1032.35~18.04.1","5.4.0-1033.36~18.04.1","5.4.0-1034.37~18.04.1","5.4.0-1035.38~18.04.1","5.4.0-1036.39~18.04.1","5.4.0-1038.41~18.04.1"]},{"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","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.4.0-80.90"}]}],"versions":["5.3.0-18.19","5.3.0-24.26","5.4.0-9.12","5.4.0-18.22","5.4.0-21.25","5.4.0-24.28","5.4.0-25.29","5.4.0-26.30","5.4.0-28.32","5.4.0-29.33","5.4.0-31.35","5.4.0-33.37","5.4.0-37.41","5.4.0-39.43","5.4.0-40.44","5.4.0-42.46","5.4.0-45.49","5.4.0-47.51","5.4.0-48.52","5.4.0-51.56","5.4.0-52.57","5.4.0-53.59","5.4.0-54.60","5.4.0-56.62","5.4.0-58.64","5.4.0-59.65","5.4.0-60.67","5.4.0-62.70","5.4.0-64.72","5.4.0-65.73","5.4.0-66.74","5.4.0-67.75","5.4.0-70.78","5.4.0-71.79","5.4.0-72.80","5.4.0-73.82","5.4.0-74.83","5.4.0-77.86"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-aws","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.4.0-1054.57"}]}],"versions":["5.3.0-1003.3","5.3.0-1008.9","5.3.0-1009.10","5.3.0-1010.11","5.4.0-1005.5","5.4.0-1007.7","5.4.0-1008.8","5.4.0-1009.9","5.4.0-1011.11","5.4.0-1015.15","5.4.0-1017.17","5.4.0-1018.18","5.4.0-1020.20","5.4.0-1021.21","5.4.0-1022.22","5.4.0-1024.24","5.4.0-1025.25","5.4.0-1028.29","5.4.0-1029.30","5.4.0-1030.31","5.4.0-1032.33","5.4.0-1034.35","5.4.0-1035.37","5.4.0-1037.39","5.4.0-1038.40","5.4.0-1039.41","5.4.0-1041.43","5.4.0-1043.45","5.4.0-1045.47","5.4.0-1047.49","5.4.0-1048.50","5.4.0-1049.51","5.4.0-1051.53"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-azure","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.4.0-1055.57"}]}],"versions":["5.3.0-1003.3","5.3.0-1008.9","5.3.0-1009.10","5.4.0-1006.6","5.4.0-1008.8","5.4.0-1009.9","5.4.0-1010.10","5.4.0-1012.12","5.4.0-1016.16","5.4.0-1019.19","5.4.0-1020.20","5.4.0-1022.22","5.4.0-1023.23","5.4.0-1025.25","5.4.0-1026.26","5.4.0-1031.32","5.4.0-1032.33","5.4.0-1034.35","5.4.0-1035.36","5.4.0-1036.38","5.4.0-1039.41","5.4.0-1040.42","5.4.0-1041.43","5.4.0-1043.45","5.4.0-1044.46","5.4.0-1046.48","5.4.0-1047.49","5.4.0-1048.50","5.4.0-1049.51","5.4.0-1051.53"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-bluefield","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.4.0-1016.19"}]}],"versions":["5.4.0-1007.10","5.4.0-1011.14","5.4.0-1012.15","5.4.0-1013.16"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-gcp","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.4.0-1049.53"}]}],"versions":["5.3.0-1004.4","5.3.0-1009.10","5.3.0-1011.12","5.4.0-1005.5","5.4.0-1007.7","5.4.0-1008.8","5.4.0-1009.9","5.4.0-1011.11","5.4.0-1015.15","5.4.0-1018.18","5.4.0-1019.19","5.4.0-1021.21","5.4.0-1022.22","5.4.0-1024.24","5.4.0-1025.25","5.4.0-1028.29","5.4.0-1029.31","5.4.0-1030.32","5.4.0-1032.34","5.4.0-1033.35","5.4.0-1034.37","5.4.0-1036.39","5.4.0-1037.40","5.4.0-1038.41","5.4.0-1040.43","5.4.0-1041.44","5.4.0-1042.45","5.4.0-1043.46","5.4.0-1044.47","5.4.0-1046.49"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-gkeop","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.4.0-1021.22"}]}],"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"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-kvm","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.4.0-1044.46"}]}],"versions":["5.3.0-1003.3","5.3.0-1008.9","5.3.0-1009.10","5.4.0-1004.4","5.4.0-1006.6","5.4.0-1007.7","5.4.0-1008.8","5.4.0-1009.9","5.4.0-1011.11","5.4.0-1015.15","5.4.0-1018.18","5.4.0-1020.20","5.4.0-1021.21","5.4.0-1023.23","5.4.0-1024.24","5.4.0-1026.27","5.4.0-1028.29","5.4.0-1030.31","5.4.0-1031.32","5.4.0-1032.33","5.4.0-1033.34","5.4.0-1034.35","5.4.0-1036.37","5.4.0-1037.38","5.4.0-1038.39","5.4.0-1039.40","5.4.0-1040.41","5.4.0-1041.42"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-oracle","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.4.0-1052.56"}]}],"versions":["5.3.0-1002.2","5.3.0-1007.8","5.3.0-1008.9","5.4.0-1005.5","5.4.0-1007.7","5.4.0-1008.8","5.4.0-1009.9","5.4.0-1011.11","5.4.0-1015.15","5.4.0-1018.18","5.4.0-1019.19","5.4.0-1021.21","5.4.0-1022.22","5.4.0-1024.24","5.4.0-1025.25","5.4.0-1028.29","5.4.0-1029.31","5.4.0-1030.32","5.4.0-1032.34","5.4.0-1034.36","5.4.0-1035.38","5.4.0-1037.40","5.4.0-1038.41","5.4.0-1039.42","5.4.0-1041.44","5.4.0-1042.45","5.4.0-1043.46","5.4.0-1045.49","5.4.0-1046.50","5.4.0-1048.52","5.4.0-1049.53"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-raspi","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.4.0-1041.45"}]}],"versions":["5.4.0-1007.7","5.4.0-1008.8","5.4.0-1011.11","5.4.0-1012.12","5.4.0-1013.13","5.4.0-1015.15","5.4.0-1016.17","5.4.0-1018.20","5.4.0-1019.21","5.4.0-1021.24","5.4.0-1022.25","5.4.0-1023.26","5.4.0-1025.28","5.4.0-1026.29","5.4.0-1028.31","5.4.0-1029.32","5.4.0-1030.33","5.4.0-1032.35","5.4.0-1033.36","5.4.0-1034.37","5.4.0-1035.38","5.4.0-1036.39","5.4.0-1038.41"]},{"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-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:Pro:FIPS-updates:20.04:LTS","package":"linux-aws-fips","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.4.0-1069.73+fips2"}]}],"versions":["5.4.0-1021.21+fips2"]},{"source":"osv","ecosystem":"Ubuntu:Pro:FIPS-updates:20.04:LTS","package":"linux-azure-fips","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.4.0-1073.76+fips1"}]}],"versions":["5.4.0-1022.22+fips1"]},{"source":"osv","ecosystem":"Ubuntu:Pro:FIPS-updates:20.04:LTS","package":"linux-fips","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.4.0-1031.36"}]}],"versions":["5.4.0-1026.30","5.4.0-1028.32"]},{"source":"osv","ecosystem":"Ubuntu:Pro:FIPS-updates:20.04:LTS","package":"linux-gcp-fips","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.4.0-1067.71~20.04.1"}]}],"versions":["5.4.0-1021.21+fips1"]},{"source":"osv","ecosystem":"Ubuntu:Pro:FIPS:20.04:LTS","package":"linux-aws-fips","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.4.0-1021.21+fips2"]},{"source":"osv","ecosystem":"Ubuntu:Pro:FIPS:20.04:LTS","package":"linux-azure-fips","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.4.0-1022.22+fips1"]},{"source":"osv","ecosystem":"Ubuntu:Pro:FIPS:20.04:LTS","package":"linux-fips","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.4.0-1007.8"]},{"source":"osv","ecosystem":"Ubuntu:Pro:FIPS:20.04:LTS","package":"linux-gcp-fips","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.4.0-1021.21+fips1"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-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-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-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-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-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-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-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-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-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:24.04:LTS","package":"linux-raspi-realtime","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["6.8.0-2019.20"]}],"products":[{"vendor":"linux","product":"linux"},{"vendor":"linux","product":"linux_kernel"}],"references":[{"url":"https://git.kernel.org/stable/c/0b6b4b90b74c27bea968c214d820ba4254b903a5","tags":["x_transferred","Patch","fix","report"]},{"url":"https://git.kernel.org/stable/c/54dbe2d2c1fcabf650c7a8b747601da355cd7f9f","tags":["x_transferred","Patch","fix","report"]},{"url":"https://git.kernel.org/stable/c/a287cd84e047045f5a4d4da793414e848de627c6","tags":["x_transferred","Patch","fix","report"]},{"url":"https://git.kernel.org/stable/c/2ef3c76540c49167a0bc3d5f80d00fd1fc4586df","tags":["x_transferred","Patch","fix","report"]},{"url":"https://git.kernel.org/stable/c/efed9a3337e341bd0989161b97453b52567bc59d","tags":["x_transferred","Patch","fix","report"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2021-46984","tags":["advisory"]},{"url":"https://github.com/advisories/GHSA-4qp7-5rvw-5428"},{"url":"https://access.redhat.com/errata/RHSA-2024:7000","tags":["advisory"]},{"url":"https://access.redhat.com/security/cve/CVE-2021-46984","tags":["report"]},{"url":"https://access.redhat.com/security/cve/CVE-2021-47097","tags":["report"]},{"url":"https://access.redhat.com/security/cve/CVE-2021-47101","tags":["report"]},{"url":"https://access.redhat.com/security/cve/CVE-2021-47287","tags":["report"]},{"url":"https://access.redhat.com/security/cve/CVE-2021-47289","tags":["report"]},{"url":"https://access.redhat.com/security/cve/CVE-2021-47321","tags":["report"]},{"url":"https://access.redhat.com/security/cve/CVE-2021-47338","tags":["report"]},{"url":"https://access.redhat.com/security/cve/CVE-2021-47352","tags":["report"]},{"url":"https://access.redhat.com/security/cve/CVE-2021-47383","tags":["report"]},{"url":"https://access.redhat.com/security/cve/CVE-2021-47384","tags":["report"]},{"url":"https://access.redhat.com/security/cve/CVE-2021-47385","tags":["report"]},{"url":"https://access.redhat.com/security/cve/CVE-2021-47386","tags":["report"]},{"url":"https://access.redhat.com/security/cve/CVE-2021-47393","tags":["report"]},{"url":"https://access.redhat.com/security/cve/CVE-2021-47412","tags":["report"]},{"url":"https://access.redhat.com/security/cve/CVE-2021-47432","tags":["report"]},{"url":"https://access.redhat.com/security/cve/CVE-2021-47441","tags":["report"]},{"url":"https://access.redhat.com/security/cve/CVE-2021-47455","tags":["report"]},{"url":"https://access.redhat.com/security/cve/CVE-2021-47466","tags":["report"]},{"url":"https://access.redhat.com/security/cve/CVE-2021-47497","tags":["report"]},{"url":"https://access.redhat.com/security/cve/CVE-2021-47527","tags":["report"]},{"url":"https://access.redhat.com/security/cve/CVE-2021-47560","tags":["report"]},{"url":"https://access.redhat.com/security/cve/CVE-2021-47582","tags":["report"]},{"url":"https://access.redhat.com/security/cve/CVE-2021-47609","tags":["report"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-48619","tags":["report"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-48754","tags":["report"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-48760","tags":["report"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-48804","tags":["report"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-48836","tags":["report"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-48866","tags":["report"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-52470","tags":["report"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-52476","tags":["report"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-52478","tags":["report"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-52522","tags":["report"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-52605","tags":["report"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-52683","tags":["report"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-52798","tags":["report"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-52800","tags":["report"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-52809","tags":["report"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-52817","tags":["report"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-52840","tags":["report"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-6040","tags":["report"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-23848","tags":["report"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-26595","tags":["report"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-26600","tags":["report"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-26638","tags":["report"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-26645","tags":["report"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-26649","tags":["report"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-26665","tags":["report"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-26717","tags":["report"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-26720","tags":["report"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-26769","tags":["report"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-26846","tags":["report"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-26855","tags":["report"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-26880","tags":["report"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-26894","tags":["report"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-26923","tags":["report"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-26939","tags":["report"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-27013","tags":["report"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-27042","tags":["report"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-35809","tags":["report"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-35877","tags":["report"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-35884","tags":["report"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-35944","tags":["report"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-35989","tags":["report"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-36883","tags":["report"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-36901","tags":["report"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-36902","tags":["report"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-36919","tags":["report"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-36920","tags":["report"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-36922","tags":["report"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-36939","tags":["report"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-36953","tags":["report"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-37356","tags":["report"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-38558","tags":["report"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-38559","tags":["report"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-38570","tags":["report"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-38579","tags":["report"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-38581","tags":["report"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-38619","tags":["report"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-39471","tags":["report"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-39499","tags":["report"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-39501","tags":["report"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-39506","tags":["report"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-40901","tags":["report"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-40904","tags":["report"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-40911","tags":["report"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-40912","tags":["report"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-40929","tags":["report"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-40931","tags":["report"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-40941","tags":["report"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-40954","tags":["report"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-40958","tags":["report"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-40959","tags":["report"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-40960","tags":["report"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-40972","tags":["report"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-40977","tags":["report"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-40978","tags":["report"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-40988","tags":["report"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-40989","tags":["report"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-40995","tags":["report"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-40997","tags":["report"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-40998","tags":["report"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-41005","tags":["report"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-41007","tags":["report"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-41008","tags":["report"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-41012","tags":["report"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-41013","tags":["report"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-41014","tags":["report"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-41023","tags":["report"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-41035","tags":["report"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-41038","tags":["report"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-41039","tags":["report"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-41040","tags":["report"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-41041","tags":["report"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-41044","tags":["report"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-41055","tags":["report"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-41056","tags":["report"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-41060","tags":["report"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-41064","tags":["report"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-41065","tags":["report"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-41071","tags":["report"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-41076","tags":["report"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-41090","tags":["report"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-41091","tags":["report"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-41097","tags":["report"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-42084","tags":["report"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-42090","tags":["report"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-42094","tags":["report"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-42096","tags":["report"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-42114","tags":["report"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-42124","tags":["report"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-42131","tags":["report"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-42152","tags":["report"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-42154","tags":["report"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-42225","tags":["report"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-42226","tags":["report"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-42228","tags":["report"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-42237","tags":["report"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-42238","tags":["report"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-42240","tags":["report"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-42246","tags":["report"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-42265","tags":["report"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-42322","tags":["report"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-43830","tags":["report"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-43871","tags":["report"]},{"url":"https://bugzilla.redhat.com/2258012","tags":["report"]},{"url":"https://bugzilla.redhat.com/2258013","tags":["report"]},{"url":"https://bugzilla.redhat.com/2260038","tags":["report"]},{"url":"https://bugzilla.redhat.com/2265799","tags":["report"]},{"url":"https://bugzilla.redhat.com/2265838","tags":["report"]},{"url":"https://bugzilla.redhat.com/2266358","tags":["report"]},{"url":"https://bugzilla.redhat.com/2266750","tags":["report"]},{"url":"https://bugzilla.redhat.com/2267036","tags":["report"]},{"url":"https://bugzilla.redhat.com/2267041","tags":["report"]},{"url":"https://bugzilla.redhat.com/2267795","tags":["report"]},{"url":"https://bugzilla.redhat.com/2267916","tags":["report"]},{"url":"https://bugzilla.redhat.com/2267925","tags":["report"]},{"url":"https://bugzilla.redhat.com/2268295","tags":["report"]},{"url":"https://bugzilla.redhat.com/2270103","tags":["report"]},{"url":"https://bugzilla.redhat.com/2271648","tags":["report"]},{"url":"https://bugzilla.redhat.com/2271796","tags":["report"]},{"url":"https://bugzilla.redhat.com/2272793","tags":["report"]},{"url":"https://bugzilla.redhat.com/2273141","tags":["report"]},{"url":"https://bugzilla.redhat.com/2273148","tags":["report"]},{"url":"https://bugzilla.redhat.com/2273180","tags":["report"]},{"url":"https://bugzilla.redhat.com/2275558","tags":["report"]},{"url":"https://bugzilla.redhat.com/2275661","tags":["report"]},{"url":"https://bugzilla.redhat.com/2275690","tags":["report"]},{"url":"https://bugzilla.redhat.com/2275742","tags":["report"]},{"url":"https://bugzilla.redhat.com/2277171","tags":["report"]},{"url":"https://bugzilla.redhat.com/2278220","tags":["report"]},{"url":"https://bugzilla.redhat.com/2278270","tags":["report"]},{"url":"https://bugzilla.redhat.com/2278447","tags":["report"]},{"url":"https://bugzilla.redhat.com/2281217","tags":["report"]},{"url":"https://bugzilla.redhat.com/2281317","tags":["report"]},{"url":"https://bugzilla.redhat.com/2281704","tags":["report"]},{"url":"https://bugzilla.redhat.com/2281720","tags":["report"]},{"url":"https://bugzilla.redhat.com/2281807","tags":["report"]},{"url":"https://bugzilla.redhat.com/2281847","tags":["report"]},{"url":"https://bugzilla.redhat.com/2282324","tags":["report"]},{"url":"https://bugzilla.redhat.com/2282345","tags":["report"]},{"url":"https://bugzilla.redhat.com/2282354","tags":["report"]},{"url":"https://bugzilla.redhat.com/2282355","tags":["report"]},{"url":"https://bugzilla.redhat.com/2282356","tags":["report"]},{"url":"https://bugzilla.redhat.com/2282357","tags":["report"]},{"url":"https://bugzilla.redhat.com/2282366","tags":["report"]},{"url":"https://bugzilla.redhat.com/2282401","tags":["report"]},{"url":"https://bugzilla.redhat.com/2282422","tags":["report"]},{"url":"https://bugzilla.redhat.com/2282440","tags":["report"]},{"url":"https://bugzilla.redhat.com/2282508","tags":["report"]},{"url":"https://bugzilla.redhat.com/2282511","tags":["report"]},{"url":"https://bugzilla.redhat.com/2282648","tags":["report"]},{"url":"https://bugzilla.redhat.com/2282669","tags":["report"]},{"url":"https://bugzilla.redhat.com/2282676","tags":["report"]},{"url":"https://bugzilla.redhat.com/2282757","tags":["report"]},{"url":"https://bugzilla.redhat.com/2282764","tags":["report"]},{"url":"https://bugzilla.redhat.com/2282851","tags":["report"]},{"url":"https://bugzilla.redhat.com/2282890","tags":["report"]},{"url":"https://bugzilla.redhat.com/2282903","tags":["report"]},{"url":"https://bugzilla.redhat.com/2282918","tags":["report"]},{"url":"https://bugzilla.redhat.com/2283389","tags":["report"]},{"url":"https://bugzilla.redhat.com/2283424","tags":["report"]},{"url":"https://bugzilla.redhat.com/2284271","tags":["report"]},{"url":"https://bugzilla.redhat.com/2284511","tags":["report"]},{"url":"https://bugzilla.redhat.com/2284515","tags":["report"]},{"url":"https://bugzilla.redhat.com/2284545","tags":["report"]},{"url":"https://bugzilla.redhat.com/2284596","tags":["report"]},{"url":"https://bugzilla.redhat.com/2284628","tags":["report"]},{"url":"https://bugzilla.redhat.com/2284630","tags":["report"]},{"url":"https://bugzilla.redhat.com/2284634","tags":["report"]},{"url":"https://bugzilla.redhat.com/2293247","tags":["report"]},{"url":"https://bugzilla.redhat.com/2293270","tags":["report"]},{"url":"https://bugzilla.redhat.com/2293273","tags":["report"]},{"url":"https://bugzilla.redhat.com/2293304","tags":["report"]},{"url":"https://bugzilla.redhat.com/2293377","tags":["report"]},{"url":"https://bugzilla.redhat.com/2293408","tags":["report"]},{"url":"https://bugzilla.redhat.com/2293414","tags":["report"]},{"url":"https://bugzilla.redhat.com/2293423","tags":["report"]},{"url":"https://bugzilla.redhat.com/2293440","tags":["report"]},{"url":"https://bugzilla.redhat.com/2293441","tags":["report"]},{"url":"https://bugzilla.redhat.com/2293658","tags":["report"]},{"url":"https://bugzilla.redhat.com/2294313","tags":["report"]},{"url":"https://bugzilla.redhat.com/2297471","tags":["report"]},{"url":"https://bugzilla.redhat.com/2297473","tags":["report"]},{"url":"https://bugzilla.redhat.com/2297478","tags":["report"]},{"url":"https://bugzilla.redhat.com/2297488","tags":["report"]},{"url":"https://bugzilla.redhat.com/2297495","tags":["report"]},{"url":"https://bugzilla.redhat.com/2297496","tags":["report"]},{"url":"https://bugzilla.redhat.com/2297513","tags":["report"]},{"url":"https://bugzilla.redhat.com/2297515","tags":["report"]},{"url":"https://bugzilla.redhat.com/2297525","tags":["report"]},{"url":"https://bugzilla.redhat.com/2297538","tags":["report"]},{"url":"https://bugzilla.redhat.com/2297542","tags":["report"]},{"url":"https://bugzilla.redhat.com/2297543","tags":["report"]},{"url":"https://bugzilla.redhat.com/2297544","tags":["report"]},{"url":"https://bugzilla.redhat.com/2297556","tags":["report"]},{"url":"https://bugzilla.redhat.com/2297561","tags":["report"]},{"url":"https://bugzilla.redhat.com/2297562","tags":["report"]},{"url":"https://bugzilla.redhat.com/2297572","tags":["report"]},{"url":"https://bugzilla.redhat.com/2297573","tags":["report"]},{"url":"https://bugzilla.redhat.com/2297579","tags":["report"]},{"url":"https://bugzilla.redhat.com/2297581","tags":["report"]},{"url":"https://bugzilla.redhat.com/2297582","tags":["report"]},{"url":"https://bugzilla.redhat.com/2297589","tags":["report"]},{"url":"https://bugzilla.redhat.com/2297706","tags":["report"]},{"url":"https://bugzilla.redhat.com/2297909","tags":["report"]},{"url":"https://bugzilla.redhat.com/2298079","tags":["report"]},{"url":"https://bugzilla.redhat.com/2298140","tags":["report"]},{"url":"https://bugzilla.redhat.com/2298177","tags":["report"]},{"url":"https://bugzilla.redhat.com/2298640","tags":["report"]},{"url":"https://bugzilla.redhat.com/2299240","tags":["report"]},{"url":"https://bugzilla.redhat.com/2299336","tags":["report"]},{"url":"https://bugzilla.redhat.com/2299452","tags":["report"]},{"url":"https://bugzilla.redhat.com/2300296","tags":["report"]},{"url":"https://bugzilla.redhat.com/2300297","tags":["report"]},{"url":"https://bugzilla.redhat.com/2300381","tags":["report"]},{"url":"https://bugzilla.redhat.com/2300402","tags":["report"]},{"url":"https://bugzilla.redhat.com/2300407","tags":["report"]},{"url":"https://bugzilla.redhat.com/2300408","tags":["report"]},{"url":"https://bugzilla.redhat.com/2300409","tags":["report"]},{"url":"https://bugzilla.redhat.com/2300410","tags":["report"]},{"url":"https://bugzilla.redhat.com/2300414","tags":["report"]},{"url":"https://bugzilla.redhat.com/2300429","tags":["report"]},{"url":"https://bugzilla.redhat.com/2300430","tags":["report"]},{"url":"https://bugzilla.redhat.com/2300434","tags":["report"]},{"url":"https://bugzilla.redhat.com/2300439","tags":["report"]},{"url":"https://bugzilla.redhat.com/2300440","tags":["report"]},{"url":"https://bugzilla.redhat.com/2300448","tags":["report"]},{"url":"https://bugzilla.redhat.com/2300453","tags":["report"]},{"url":"https://bugzilla.redhat.com/2300492","tags":["report"]},{"url":"https://bugzilla.redhat.com/2300533","tags":["report"]},{"url":"https://bugzilla.redhat.com/2300552","tags":["report"]},{"url":"https://bugzilla.redhat.com/2300709","tags":["report"]},{"url":"https://bugzilla.redhat.com/2300713","tags":["report"]},{"url":"https://bugzilla.redhat.com/2301477","tags":["report"]},{"url":"https://bugzilla.redhat.com/2301489","tags":["report"]},{"url":"https://bugzilla.redhat.com/2301496","tags":["report"]},{"url":"https://bugzilla.redhat.com/2301519","tags":["report"]},{"url":"https://bugzilla.redhat.com/2301522","tags":["report"]},{"url":"https://bugzilla.redhat.com/2301543","tags":["report"]},{"url":"https://bugzilla.redhat.com/2301544","tags":["report"]},{"url":"https://bugzilla.redhat.com/2303077","tags":["report"]},{"url":"https://bugzilla.redhat.com/2303505","tags":["report"]},{"url":"https://bugzilla.redhat.com/2303506","tags":["report"]},{"url":"https://bugzilla.redhat.com/2303508","tags":["report"]},{"url":"https://bugzilla.redhat.com/2303514","tags":["report"]},{"url":"https://bugzilla.redhat.com/2305410","tags":["report"]},{"url":"https://bugzilla.redhat.com/2305467","tags":["report"]},{"url":"https://bugzilla.redhat.com/2305488","tags":["report"]},{"url":"https://bugzilla.redhat.com/2306365","tags":["report"]},{"url":"https://errata.almalinux.org/8/ALSA-2024-7000.html","tags":["advisory"]},{"url":"https://access.redhat.com/errata/RHSA-2024:7001","tags":["advisory"]},{"url":"https://errata.almalinux.org/8/ALSA-2024-7001.html","tags":["advisory"]},{"url":"https://errata.tuxcare.com/els_os/centos8.5els/CLSA-2026-1777614954.html","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-50303","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-50543","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-50546","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-52796","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-53254","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-53376","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-53380","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-53559","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-53577","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-53578","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-54207","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-54317","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-26974","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-58240","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-37885","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-38068","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-38103","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-38129","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-38361","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-38375","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-38563","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-39689","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-39905","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-39973","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-40135","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-40149","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-40158","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-71085","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-22980","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-23001","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-23060","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-23089","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-23097","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-31431","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-43033","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-43077","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-43078","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-46028","tags":["advisory"]},{"url":"https://errata.tuxcare.com/els_os/centos8.4els/CLSA-2026-1782145985.html","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2019-10220","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2019-17075","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2019-7221","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2021-34866","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2021-47063","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2021-47101","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2021-47138","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2021-47226","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2021-47255","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2021-47277","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2021-47506","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2021-47517","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2021-47566","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-3640","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-49022","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-49696","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-50051","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-50258","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-28410","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-39189","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-53600","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-53827","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-53833","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-38004","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-40170","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-40259","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-68366","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-68724","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-71082","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-71091","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-71238","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-22984","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-23099","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-23191","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-23209","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-23243","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-23392","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-23397","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-23448","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-23455","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-31402","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-31405","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-31408","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-31452","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-31500","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-31532","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-31581","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-31586","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-31663","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-31669","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-31685","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-43020","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-43027","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-43051","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-43052","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-43110","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-43190","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-43370","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-43427","tags":["advisory"]},{"url":"https://errata.tuxcare.com/els_os/debian10els/CLSA-2026-1788449727.html","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2021-47049","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2021-47191","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2021-47352","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2021-47379","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2021-47391","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2021-47479","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-21546","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-39189","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-43945","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-48744","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-49026","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-49720","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-49975","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-50066","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-50103","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-50129","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-50300","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-50406","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-50422","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-50552","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-39197","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-51779","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-52434","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-52515","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-52531","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-52741","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-53000","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-53039","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-53111","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-53259","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-53282","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-53321","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-53333","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-53432","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-53510","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-53680","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-21803","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-26689","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-26828","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-26996","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-35791","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-35864","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-35932","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-38545","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-38588","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-40929","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-41013","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-42120","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-46731","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-46813","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-46818","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-46826","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-46859","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-49991","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-50036","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-50067","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-50073","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-50256","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-53090","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-53124","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-56593","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-56602","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-56603","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-56606","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-56631","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-56640","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-56650","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-56658","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-56748","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-56756","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-58072","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-21749","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-21858","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-22022","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-22083","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-22121","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-23156","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-23157","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-23158","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-37796","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-37798","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-37839","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-37879","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-37882","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-37923","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-37927","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-37932","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-38000","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-38024","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-38079","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-38102","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-38157","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-38211","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-38212","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-38348","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-38403","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-38445","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-38494","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-38497","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-38565","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-38572","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-38618","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-38652","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-38679","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-38708","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-38718","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-38728","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-38729","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-39684","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-39686","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-39702","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-39730","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-39760","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-39817","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-39823","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-39824","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-39839","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-39853","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-39863","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-39891","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-39901","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-39911","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-39955","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-71075","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-71093","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-71116","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-23073","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-23076","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-23083","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-23193","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-23204","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-23216","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-23231","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-23235","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-23281","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-23372","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-23378","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-23388","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-23406","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-23407","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-31396","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-31399","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-31494","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-31576","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-31597","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-31602","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-31622","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-31626","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-31627","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-31629","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-31659","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-31696","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-31747","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-31748","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-31778","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-31787","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-43040","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-43075","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-43076","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-43198","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-43206","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-43279","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-43281","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-43386","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-43450","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-43494","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-45893","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-46006","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-46022","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-46033","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-46069","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-46116","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-46150","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-46191","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-46208","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-46209","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-46218","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-46254","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-46259","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-46333","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-52919","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-52934","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-53009","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-53036","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-53040","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-53075","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-53091","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-53130","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-53136","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-53138","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-53186","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-53189","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-53224","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-53228","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-53246","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-53264","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-53270","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-53303","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-64567","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-64571","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-64580","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-64581","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-64582","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-64584","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-64585","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-64587","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-64593","tags":["advisory"]},{"url":"https://errata.tuxcare.com/els_os/centos-stream8els/CLSA-2026-1792239979.html","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-3424","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-49840","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-50220","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-50341","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-50430","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-52452","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-53006","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-53265","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-53286","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-53427","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-53446","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-53454","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-53484","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-54260","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-56558","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-38107","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-38161","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-38584","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-38684","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-39967","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-39981","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-40080","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-68347","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-68371","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-22998","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-31788","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-43491","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-46199","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-46230","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-63917","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-63921","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-64323","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-64341","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-64348","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-64375","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-64422","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-64438","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-64448","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-68096","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-68129","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-68188","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-68286","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-68294","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-68324","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-68362","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-68432","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-72055","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-72402","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-72413","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-72476","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-74255","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-74282","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-74283","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-74289","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-74408","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-74744","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-80529","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-80622","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-97445","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-98196","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-98217","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-98320","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-98342","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-98357","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-99999","tags":["advisory"]},{"url":"https://security-tracker.debian.org/tracker/CVE-2021-46984","tags":["advisory"]},{"url":"https://www.openeuler.org/en/security/safety-bulletin/detail.html?id=openEuler-SA-2024-1483","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2020-36783","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2021-47054","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2021-47056","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2021-47060","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2021-47061","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2021-47071","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2021-47074","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2021-47077","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2021-47078","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2021-47131","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2021-47142","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2021-47143","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2021-47144","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2021-47145","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2021-47146","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2021-47153","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2021-47159","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2021-47160","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2021-47161","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2021-47162","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2021-47163","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2021-47167","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2021-47170","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2021-47171","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2021-47173","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2021-47180","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-52464","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-52475","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-52500","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-52507","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-52510","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-52522","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-52530","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-52566","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-52578","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-52583","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-52587","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-52594","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-52595","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-52597","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-52598","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-52622","tags":["advisory"]},{"url":"https://www.openeuler.org/en/security/safety-bulletin/detail.html?id=openEuler-SA-2024-1484","tags":["advisory"]},{"url":"https://access.redhat.com/security/updates/classification/#important","tags":["article"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2258012","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2258013","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2260038","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2265799","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2265838","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2266358","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2266750","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2267036","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2267041","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2267795","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2267916","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2267925","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2268295","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2270103","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2271648","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2271796","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2272793","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2273141","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2273148","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2273180","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2275558","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2275661","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2275690","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2275742","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2277171","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2278220","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2278270","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2278447","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2281217","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2281317","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2281704","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2281720","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2281807","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2281847","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2282324","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2282345","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2282354","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2282355","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2282356","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2282357","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2282366","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2282401","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2282422","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2282440","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2282508","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2282511","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2282648","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2282669","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2282676","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2282757","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2282764","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2282851","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2282890","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2282903","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2282918","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2283389","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2283424","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2284271","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2284511","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2284515","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2284545","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2284596","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2284628","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2284630","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2284634","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2293247","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2293270","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2293273","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2293304","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2293377","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2293408","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2293414","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2293423","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2293440","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2293441","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2293658","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2294313","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2297471","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2297473","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2297478","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2297488","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2297495","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2297496","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2297513","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2297515","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2297525","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2297538","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2297542","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2297543","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2297544","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2297556","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2297561","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2297562","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2297572","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2297573","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2297579","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2297581","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2297582","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2297589","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2297706","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2297909","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2298079","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2298140","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2298177","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2298640","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2299240","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2299336","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2299452","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2300296","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2300297","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2300381","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2300402","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2300407","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2300408","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2300409","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2300410","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2300414","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2300429","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2300430","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2300434","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2300439","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2300440","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2300448","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2300453","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2300492","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2300533","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2300552","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2300709","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2300713","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2301477","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2301489","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2301496","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2301519","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2301522","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2301543","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2301544","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2303077","tags":["report"]},{"url":"https://issues.redhat.com/browse/RHEL-31515","tags":["article"]},{"url":"https://security.access.redhat.com/data/csaf/v2/advisories/2024/rhsa-2024_7000.json","tags":["advisory"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2021-46984","tags":["advisory","report"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024022824-CVE-2021-46984-e55e@gregkh/T/#u","tags":["article"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2021-47097","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2021-47097","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024030415-CVE-2021-47097-e7f4@gregkh/T","tags":["article"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2021-47101","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024030415-CVE-2021-47101-f3fa@gregkh/T","tags":["article"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2021-47287","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2021-47287","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024052121-CVE-2021-47287-6345@gregkh/T","tags":["article"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2021-47289","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2021-47289","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024052122-CVE-2021-47289-7cbb@gregkh/T","tags":["article"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2021-47321","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2021-47321","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024052132-CVE-2021-47321-1b9b@gregkh/T","tags":["article"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2021-47338","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2021-47338","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024052137-CVE-2021-47338-cd10@gregkh/T","tags":["article"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2021-47352","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024052141-CVE-2021-47352-df50@gregkh/T","tags":["article"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2021-47383","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2021-47383","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024052144-CVE-2021-47383-a8f4@gregkh/T","tags":["article"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2021-47384","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2021-47384","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024052144-CVE-2021-47384-f311@gregkh/T","tags":["article"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2021-47385","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2021-47385","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024052144-CVE-2021-47385-a7e7@gregkh/T","tags":["article"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2021-47386","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2021-47386","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024052145-CVE-2021-47386-2701@gregkh/T","tags":["article"]},{"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://www.cve.org/CVERecord?id=CVE-2021-47412","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2021-47412","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024052152-CVE-2021-47412-b362@gregkh/T","tags":["article"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2021-47432","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2021-47432","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024052143-CVE-2021-47432-5e69@gregkh/T","tags":["article"]},{"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://www.cve.org/CVERecord?id=CVE-2021-47455","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2021-47455","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024052244-CVE-2021-47455-c4a1@gregkh/T","tags":["article"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2021-47466","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2021-47466","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024052227-CVE-2021-47466-ff03@gregkh/T","tags":["article"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2021-47497","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2021-47497","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024052242-CVE-2021-47497-449e@gregkh/T","tags":["article"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2021-47527","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2021-47527","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024052435-CVE-2021-47527-e6f5@gregkh/T","tags":["article"]},{"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://www.cve.org/CVERecord?id=CVE-2021-47582","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2021-47582","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024061916-CVE-2021-47582-69aa@gregkh/T","tags":["article"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2021-47609","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2021-47609","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024061907-CVE-2021-47609-5ebf@gregkh/T","tags":["article"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-48619","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-48619","tags":["advisory"]},{"url":"https://cdn.kernel.org/pub/linux/kernel/v5.x/ChangeLog-5.17.10","tags":["article"]},{"url":"https://github.com/torvalds/linux/commit/409353cbe9fe48f6bc196114c442b1cff05a39bc","tags":["article"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-48754","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-48754","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024062006-CVE-2022-48754-4012@gregkh/T","tags":["article"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-48760","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-48760","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024062008-CVE-2022-48760-b80e@gregkh/T","tags":["article"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-48804","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-48804","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024071645-CVE-2022-48804-f191@gregkh/T","tags":["article"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-48836","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-48836","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024071620-CVE-2022-48836-fb3d@gregkh/T","tags":["article"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-48866","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-48866","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024071629-CVE-2022-48866-93bd@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-49226","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2347965","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-49226","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-49226","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025022622-CVE-2022-49226-b30c@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-49316","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2347650","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-49316","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-49316","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025022636-CVE-2022-49316-3e10@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-50072","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2373562","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-50072","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-50072","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025061853-CVE-2022-50072-de2b@gregkh/T","tags":["article"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-6040","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-6040","tags":["advisory"]},{"url":"https://www.openwall.com/lists/oss-security/2024/01/12/1","tags":["article"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-52470","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-52470","tags":["advisory"]},{"url":"https://git.kernel.org/stable/c/0b813a6a0087451cb702b6eb841f10856f49d088","tags":["article"]},{"url":"https://git.kernel.org/stable/c/14bbfaa5df273b26cde6707f6e655585700e6fe1","tags":["article"]},{"url":"https://git.kernel.org/stable/c/21b1645660717d6126dd4866c850fcc5c4703a41","tags":["article"]},{"url":"https://git.kernel.org/stable/c/57ca7984806d79b38af528de88fd803babf27feb","tags":["article"]},{"url":"https://git.kernel.org/stable/c/5d12c5d75f7c78b83a738025947651ec5c95b4d4","tags":["article"]},{"url":"https://git.kernel.org/stable/c/7a2464fac80d42f6f8819fed97a553e9c2f43310","tags":["article"]},{"url":"https://git.kernel.org/stable/c/c4ff55408187f2595066967047363ca84e76db85","tags":["article"]},{"url":"https://git.kernel.org/stable/c/fb2d8bc9b5e55848b8a7c3c028e2ee8d49f28f97","tags":["article"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-52476","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-52476","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024022921-CVE-2023-52476-e307@gregkh/T/#u","tags":["article"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-52478","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-52478","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024022921-CVE-2023-52478-c0a1@gregkh/T/#u","tags":["article"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-52522","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024030253-CVE-2023-52522-6abd@gregkh/T/#u","tags":["article"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-52605","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-52605","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024030647-CVE-2023-52605-292a@gregkh/T","tags":["article"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-52683","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-52683","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024051751-CVE-2023-52683-f280@gregkh/T","tags":["article"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-52798","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-52798","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024052158-CVE-2023-52798-374e@gregkh/T","tags":["article"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-52800","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-52800","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024052159-CVE-2023-52800-63da@gregkh/T","tags":["article"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-52809","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-52809","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024052102-CVE-2023-52809-f07c@gregkh/T","tags":["article"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-52817","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-52817","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024052104-CVE-2023-52817-ba29@gregkh/T","tags":["article"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-52840","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-52840","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024052111-CVE-2023-52840-8a3d@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-53847","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2420349","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-53847","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-53847","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025120959-CVE-2023-53847-1f94@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-54269","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2426013","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-54269","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-54269","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025123000-CVE-2023-54269-6fd7@gregkh/T","tags":["article"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-23848","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-23848","tags":["advisory"]},{"url":"https://lore.kernel.org/lkml/e9f42704-2f99-4f2c-ade5-f952e5fd53e5%40xs4all.nl/","tags":["article"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-26595","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-26595","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024022336-CVE-2024-26595-9a8d@gregkh/T/#u","tags":["article"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-26600","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-26600","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024022405-CVE-2024-26600-44a2@gregkh/T/#u","tags":["article"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-26638","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-26638","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/20240318101458.2835626-16-lee@kernel.org/T","tags":["article"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-26645","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-26645","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/20240326151722.1258576-4-lee@kernel.org/T","tags":["article"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-26649","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-26649","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/20240326175007.1388794-17-lee@kernel.org/T","tags":["article"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-26665","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-26665","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024040224-CVE-2024-26665-5daa@gregkh/T","tags":["article"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-26717","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-26717","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024040344-CVE-2024-26717-0d01@gregkh/T","tags":["article"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-26720","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-26720","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024040344-CVE-2024-26720-06fa@gregkh/T","tags":["article"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-26769","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-26769","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024040307-CVE-2024-26769-e9cc@gregkh/T","tags":["article"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-26846","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-26846","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024041717-CVE-2024-26846-9593@gregkh/T","tags":["article"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-26855","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-26855","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024041724-CVE-2024-26855-ac0d@gregkh/T","tags":["article"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-26880","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-26880","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024041740-CVE-2024-26880-25d6@gregkh/T","tags":["article"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-26894","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-26894","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024041743-CVE-2024-26894-53ad@gregkh/T","tags":["article"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-26923","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-26923","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024042418-CVE-2024-26923-f7f6@gregkh/T","tags":["article"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-26939","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-26939","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024050124-CVE-2024-26939-5314@gregkh/T","tags":["article"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-27013","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-27013","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024050149-CVE-2024-27013-2c26@gregkh/T","tags":["article"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-27042","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-27042","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024050113-CVE-2024-27042-e812@gregkh/T","tags":["article"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-35809","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-35809","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024051740-CVE-2024-35809-4a4e@gregkh/T","tags":["article"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-35877","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-35877","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024051943-CVE-2024-35877-39e6@gregkh/T","tags":["article"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-35884","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-35884","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024051946-CVE-2024-35884-d4a4@gregkh/T","tags":["article"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-35944","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-35944","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024051920-CVE-2024-35944-a860@gregkh/T","tags":["article"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-35989","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-35989","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024052020-CVE-2024-35989-c5da@gregkh/T","tags":["article"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-36883","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-36883","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024053032-CVE-2024-36883-b892@gregkh/T","tags":["article"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-36901","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-36901","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024053035-CVE-2024-36901-fb16@gregkh/T","tags":["article"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-36902","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-36902","tags":["advisory"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-36919","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-36919","tags":["advisory"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-36920","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-36920","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024053039-CVE-2024-36920-b4a7@gregkh/T","tags":["article"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-36922","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-36922","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024053039-CVE-2024-36922-f0df@gregkh/T","tags":["article"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-36939","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-36939","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024053043-CVE-2024-36939-8453@gregkh/T","tags":["article"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-36953","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-36953","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024053040-CVE-2024-36953-fc12@gregkh/T","tags":["article"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-37356","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-37356","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024062137-CVE-2024-37356-cc7b@gregkh/T","tags":["article"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-38558","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-38558","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024061953-CVE-2024-38558-ddfd@gregkh/T","tags":["article"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-38559","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-38559","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024061953-CVE-2024-38559-3e03@gregkh/T","tags":["article"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-38570","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-38570","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024061956-CVE-2024-38570-a8ef@gregkh/T","tags":["article"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-38579","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-38579","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024061947-CVE-2024-38579-e96a@gregkh/T","tags":["article"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-38581","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-38581","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024061948-CVE-2024-38581-592d@gregkh/T","tags":["article"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-38619","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-38619","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024062035-CVE-2024-38619-97c7@gregkh/T","tags":["article"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-39471","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-39471","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024062501-CVE-2024-39471-3dee@gregkh/T","tags":["article"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-39499","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-39499","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024071203-CVE-2024-39499-ed0a@gregkh/T","tags":["article"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-39501","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-39501","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024071204-CVE-2024-39501-058b@gregkh/T","tags":["article"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-39506","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-39506","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024071205-CVE-2024-39506-b0cc@gregkh/T","tags":["article"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-40901","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-40901","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024071207-CVE-2024-40901-05c4@gregkh/T","tags":["article"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-40904","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-40904","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024071208-CVE-2024-40904-48b1@gregkh/T","tags":["article"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-40911","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-40911","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024071210-CVE-2024-40911-2382@gregkh/T","tags":["article"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-40912","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-40912","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024071210-CVE-2024-40912-7286@gregkh/T","tags":["article"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-40929","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024071215-CVE-2024-40929-e1cb@gregkh/T","tags":["article"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-40931","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-40931","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024071216-CVE-2024-40931-77b2@gregkh/T","tags":["article"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-40941","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-40941","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024071219-CVE-2024-40941-9e5c@gregkh/T","tags":["article"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-40954","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-40954","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024071223-CVE-2024-40954-093b@gregkh/T","tags":["article"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-40958","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-40958","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024071225-CVE-2024-40958-8ed5@gregkh/T","tags":["article"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-40959","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-40959","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024071225-CVE-2024-40959-228e@gregkh/T","tags":["article"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-40960","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-40960","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024071225-CVE-2024-40960-d46f@gregkh/T","tags":["article"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-40972","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-40972","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024071229-CVE-2024-40972-1569@gregkh/T","tags":["article"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-40977","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-40977","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024071230-CVE-2024-40977-07c8@gregkh/T","tags":["article"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-40978","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-40978","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024071231-CVE-2024-40978-d135@gregkh/T","tags":["article"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-40988","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-40988","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024071249-CVE-2024-40988-490e@gregkh/T","tags":["article"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-40989","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-40989","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024071249-CVE-2024-40989-c8da@gregkh/T","tags":["article"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-40995","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-40995","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024071251-CVE-2024-40995-2a5c@gregkh/T","tags":["article"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-40997","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-40997","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024071251-CVE-2024-40997-df97@gregkh/T","tags":["article"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-40998","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-40998","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024071252-CVE-2024-40998-90d6@gregkh/T","tags":["article"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-41005","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-41005","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024071244-CVE-2024-41005-b2a5@gregkh/T","tags":["article"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-41007","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-41007","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024071513-CVE-2024-41007-777c@gregkh/T","tags":["article"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-41008","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-41008","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/20240716080357.2696435-2-lee@kernel.org/T","tags":["article"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-41012","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-41012","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024072314-CVE-2024-41012-a1cf@gregkh/T","tags":["article"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-41013","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024072908-CVE-2024-41013-2996@gregkh/T","tags":["article"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-41014","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-41014","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024072910-CVE-2024-41014-9186@gregkh/T","tags":["article"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-41023","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-41023","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024072917-CVE-2024-41023-32a0@gregkh/T","tags":["article"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-41035","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-41035","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024072922-CVE-2024-41035-5e6b@gregkh/T","tags":["article"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-41038","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-41038","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024072923-CVE-2024-41038-41ba@gregkh/T","tags":["article"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-41039","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-41039","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024072924-CVE-2024-41039-b3bc@gregkh/T","tags":["article"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-41040","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-41040","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024072924-CVE-2024-41040-63d5@gregkh/T","tags":["article"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-41041","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-41041","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024072924-CVE-2024-41041-ae0c@gregkh/T","tags":["article"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-41044","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-41044","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024072925-CVE-2024-41044-5b26@gregkh/T","tags":["article"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-41055","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-41055","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024072928-CVE-2024-41055-5764@gregkh/T","tags":["article"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-41056","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-41056","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024072930-CVE-2024-41056-c324@gregkh/T","tags":["article"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-41060","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-41060","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024072905-CVE-2024-41060-b7de@gregkh/T","tags":["article"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-41064","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-41064","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024072907-CVE-2024-41064-6ecb@gregkh/T","tags":["article"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-41065","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-41065","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024072907-CVE-2024-41065-2501@gregkh/T","tags":["article"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-41071","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-41071","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024072909-CVE-2024-41071-4eb6@gregkh/T","tags":["article"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-41076","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-41076","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024072910-CVE-2024-41076-6124@gregkh/T","tags":["article"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-41090","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-41090","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024072916-CVE-2024-41090-9830@gregkh","tags":["article"]},{"url":"https://www.openwall.com/lists/oss-security/2024/07/24/4","tags":["article"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-41091","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-41091","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024072918-CVE-2024-41091-35b7@gregkh","tags":["article"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-41097","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-41097","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024072954-CVE-2024-41097-248c@gregkh/T","tags":["article"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-42084","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-42084","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024072942-CVE-2024-42084-9283@gregkh/T","tags":["article"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-42090","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-42090","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024072946-CVE-2024-42090-5687@gregkh/T","tags":["article"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-42094","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-42094","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024072911-CVE-2024-42094-135f@gregkh/T","tags":["article"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-42096","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-42096","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024072911-CVE-2024-42096-67f3@gregkh/T","tags":["article"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-42114","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-42114","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024073022-CVE-2024-42114-4585@gregkh/T","tags":["article"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-42124","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-42124","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024073025-CVE-2024-42124-e4ad@gregkh/T","tags":["article"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-42131","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-42131","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024073027-CVE-2024-42131-2f7f@gregkh/T","tags":["article"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-42152","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-42152","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024073034-CVE-2024-42152-c248@gregkh/T","tags":["article"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-42154","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-42154","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024073034-CVE-2024-42154-cf82@gregkh/T","tags":["article"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-42225","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-42225","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024073038-CVE-2024-42225-bdfa@gregkh/T","tags":["article"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-42226","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-42226","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024073038-CVE-2024-42226-fa39@gregkh/T","tags":["article"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-42228","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-42228","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024073038-CVE-2024-42228-86f5@gregkh/T","tags":["article"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2303505","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-42237","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-42237","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024080740-CVE-2024-42237-eba4@gregkh/T","tags":["article"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2303506","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-42238","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-42238","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024080740-CVE-2024-42238-a5fd@gregkh/T","tags":["article"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2303508","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-42240","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-42240","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024080741-CVE-2024-42240-3d04@gregkh/T","tags":["article"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2303514","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-42246","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-42246","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024080742-CVE-2024-42246-0777@gregkh/T","tags":["article"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2305410","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-42265","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-42265","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024081737-CVE-2024-42265-a943@gregkh/T","tags":["article"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2305467","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-42322","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-42322","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024081755-CVE-2024-42322-e2ef@gregkh/T","tags":["article"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2305488","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-43830","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-43830","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024081727-CVE-2024-43830-3b85@gregkh/T","tags":["article"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2306365","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-43871","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-43871","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024082136-CVE-2024-43871-c2cd@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-45026","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2311723","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-45026","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-45026","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024091110-CVE-2024-45026-eaa8@gregkh/T","tags":["article"]},{"url":"https://security.access.redhat.com/data/csaf/v2/advisories/2024/rhsa-2024_7001.json","tags":["advisory"]},{"url":"https://errata.rockylinux.org/RLSA-2024:7000","tags":["advisory"]},{"url":"https://errata.rockylinux.org/RLSA-2024:7001","tags":["advisory"]},{"url":"https://www.suse.com/support/update/announcement/2024/suse-su-20241454-1/","tags":["advisory"]},{"url":"https://bugzilla.suse.com/1186060","tags":["report"]},{"url":"https://bugzilla.suse.com/1192145","tags":["report"]},{"url":"https://bugzilla.suse.com/1194516","tags":["report"]},{"url":"https://bugzilla.suse.com/1208995","tags":["report"]},{"url":"https://bugzilla.suse.com/1209635","tags":["report"]},{"url":"https://bugzilla.suse.com/1209657","tags":["report"]},{"url":"https://bugzilla.suse.com/1212514","tags":["report"]},{"url":"https://bugzilla.suse.com/1213456","tags":["report"]},{"url":"https://bugzilla.suse.com/1217987","tags":["report"]},{"url":"https://bugzilla.suse.com/1217988","tags":["report"]},{"url":"https://bugzilla.suse.com/1217989","tags":["report"]},{"url":"https://bugzilla.suse.com/1218336","tags":["report"]},{"url":"https://bugzilla.suse.com/1218447","tags":["report"]},{"url":"https://bugzilla.suse.com/1218479","tags":["report"]},{"url":"https://bugzilla.suse.com/1218562","tags":["report"]},{"url":"https://bugzilla.suse.com/1219170","tags":["report"]},{"url":"https://bugzilla.suse.com/1219264","tags":["report"]},{"url":"https://bugzilla.suse.com/1220320","tags":["report"]},{"url":"https://bugzilla.suse.com/1220340","tags":["report"]},{"url":"https://bugzilla.suse.com/1220366","tags":["report"]},{"url":"https://bugzilla.suse.com/1220411","tags":["report"]},{"url":"https://bugzilla.suse.com/1220413","tags":["report"]},{"url":"https://bugzilla.suse.com/1220442","tags":["report"]},{"url":"https://bugzilla.suse.com/1220445","tags":["report"]},{"url":"https://bugzilla.suse.com/1220468","tags":["report"]},{"url":"https://bugzilla.suse.com/1220484","tags":["report"]},{"url":"https://bugzilla.suse.com/1220521","tags":["report"]},{"url":"https://bugzilla.suse.com/1220528","tags":["report"]},{"url":"https://bugzilla.suse.com/1220529","tags":["report"]},{"url":"https://bugzilla.suse.com/1220532","tags":["report"]},{"url":"https://bugzilla.suse.com/1220536","tags":["report"]},{"url":"https://bugzilla.suse.com/1220554","tags":["report"]},{"url":"https://bugzilla.suse.com/1220556","tags":["report"]},{"url":"https://bugzilla.suse.com/1220560","tags":["report"]},{"url":"https://bugzilla.suse.com/1220561","tags":["report"]},{"url":"https://bugzilla.suse.com/1220566","tags":["report"]},{"url":"https://bugzilla.suse.com/1220575","tags":["report"]},{"url":"https://bugzilla.suse.com/1220580","tags":["report"]},{"url":"https://bugzilla.suse.com/1220583","tags":["report"]},{"url":"https://bugzilla.suse.com/1220611","tags":["report"]},{"url":"https://bugzilla.suse.com/1220615","tags":["report"]},{"url":"https://bugzilla.suse.com/1220625","tags":["report"]},{"url":"https://bugzilla.suse.com/1220631","tags":["report"]},{"url":"https://bugzilla.suse.com/1220638","tags":["report"]},{"url":"https://bugzilla.suse.com/1220640","tags":["report"]},{"url":"https://bugzilla.suse.com/1220641","tags":["report"]},{"url":"https://bugzilla.suse.com/1220662","tags":["report"]},{"url":"https://bugzilla.suse.com/1220669","tags":["report"]},{"url":"https://bugzilla.suse.com/1220687","tags":["report"]},{"url":"https://bugzilla.suse.com/1220692","tags":["report"]},{"url":"https://bugzilla.suse.com/1220697","tags":["report"]},{"url":"https://bugzilla.suse.com/1220703","tags":["report"]},{"url":"https://bugzilla.suse.com/1220706","tags":["report"]},{"url":"https://bugzilla.suse.com/1220739","tags":["report"]},{"url":"https://bugzilla.suse.com/1220743","tags":["report"]},{"url":"https://bugzilla.suse.com/1220745","tags":["report"]},{"url":"https://bugzilla.suse.com/1220749","tags":["report"]},{"url":"https://bugzilla.suse.com/1220751","tags":["report"]},{"url":"https://bugzilla.suse.com/1220764","tags":["report"]},{"url":"https://bugzilla.suse.com/1220768","tags":["report"]},{"url":"https://bugzilla.suse.com/1220769","tags":["report"]},{"url":"https://bugzilla.suse.com/1220777","tags":["report"]},{"url":"https://bugzilla.suse.com/1220779","tags":["report"]},{"url":"https://bugzilla.suse.com/1220785","tags":["report"]},{"url":"https://bugzilla.suse.com/1220790","tags":["report"]},{"url":"https://bugzilla.suse.com/1220794","tags":["report"]},{"url":"https://bugzilla.suse.com/1220826","tags":["report"]},{"url":"https://bugzilla.suse.com/1220829","tags":["report"]},{"url":"https://bugzilla.suse.com/1220836","tags":["report"]},{"url":"https://bugzilla.suse.com/1220846","tags":["report"]},{"url":"https://bugzilla.suse.com/1220850","tags":["report"]},{"url":"https://bugzilla.suse.com/1220861","tags":["report"]},{"url":"https://bugzilla.suse.com/1220871","tags":["report"]},{"url":"https://bugzilla.suse.com/1220883","tags":["report"]},{"url":"https://bugzilla.suse.com/1220946","tags":["report"]},{"url":"https://bugzilla.suse.com/1220969","tags":["report"]},{"url":"https://bugzilla.suse.com/1221044","tags":["report"]},{"url":"https://bugzilla.suse.com/1221058","tags":["report"]},{"url":"https://bugzilla.suse.com/1221061","tags":["report"]},{"url":"https://bugzilla.suse.com/1221077","tags":["report"]},{"url":"https://bugzilla.suse.com/1221088","tags":["report"]},{"url":"https://bugzilla.suse.com/1221293","tags":["report"]},{"url":"https://bugzilla.suse.com/1221532","tags":["report"]},{"url":"https://bugzilla.suse.com/1221534","tags":["report"]},{"url":"https://bugzilla.suse.com/1221541","tags":["report"]},{"url":"https://bugzilla.suse.com/1221548","tags":["report"]},{"url":"https://bugzilla.suse.com/1221575","tags":["report"]},{"url":"https://bugzilla.suse.com/1221605","tags":["report"]},{"url":"https://bugzilla.suse.com/1221606","tags":["report"]},{"url":"https://bugzilla.suse.com/1221608","tags":["report"]},{"url":"https://bugzilla.suse.com/1221830","tags":["report"]},{"url":"https://bugzilla.suse.com/1221934","tags":["report"]},{"url":"https://bugzilla.suse.com/1221935","tags":["report"]},{"url":"https://bugzilla.suse.com/1221949","tags":["report"]},{"url":"https://bugzilla.suse.com/1221952","tags":["report"]},{"url":"https://bugzilla.suse.com/1221965","tags":["report"]},{"url":"https://bugzilla.suse.com/1221966","tags":["report"]},{"url":"https://bugzilla.suse.com/1221969","tags":["report"]},{"url":"https://bugzilla.suse.com/1221989","tags":["report"]},{"url":"https://bugzilla.suse.com/1221991","tags":["report"]},{"url":"https://bugzilla.suse.com/1221992","tags":["report"]},{"url":"https://bugzilla.suse.com/1221993","tags":["report"]},{"url":"https://bugzilla.suse.com/1221994","tags":["report"]},{"url":"https://bugzilla.suse.com/1221997","tags":["report"]},{"url":"https://bugzilla.suse.com/1221998","tags":["report"]},{"url":"https://bugzilla.suse.com/1221999","tags":["report"]},{"url":"https://bugzilla.suse.com/1222000","tags":["report"]},{"url":"https://bugzilla.suse.com/1222001","tags":["report"]},{"url":"https://bugzilla.suse.com/1222002","tags":["report"]},{"url":"https://bugzilla.suse.com/1222004","tags":["report"]},{"url":"https://bugzilla.suse.com/1222117","tags":["report"]},{"url":"https://bugzilla.suse.com/1222422","tags":["report"]},{"url":"https://bugzilla.suse.com/1222585","tags":["report"]},{"url":"https://bugzilla.suse.com/1222619","tags":["report"]},{"url":"https://bugzilla.suse.com/1222660","tags":["report"]},{"url":"https://bugzilla.suse.com/1222664","tags":["report"]},{"url":"https://bugzilla.suse.com/1222669","tags":["report"]},{"url":"https://bugzilla.suse.com/1222706","tags":["report"]},{"url":"https://www.suse.com/security/cve/CVE-2020-36780","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2020-36782","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2020-36783","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-23134","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-46909","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-46921","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-46930","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-46938","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-46939","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-46943","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-46944","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-46950","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-46951","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-46958","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-46960","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-46961","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-46962","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-46963","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-46971","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-46981","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-46984","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-46988","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-46990","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-46991","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-46992","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-46998","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-47000","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-47006","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-47013","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-47015","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-47020","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-47034","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-47045","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-47049","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-47051","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-47055","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-47056","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-47058","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-47061","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-47063","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-47065","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-47068","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-47069","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-47070","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-47071","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-47073","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-47077","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-47082","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-47109","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-47110","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-47112","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-47114","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-47117","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-47118","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-47119","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-47120","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-47138","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-47139","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-47141","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-47142","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-47144","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-47153","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-47161","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-47165","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-47166","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-47167","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-47168","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-47169","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-47170","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-47171","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-47172","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-47173","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-47177","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-47179","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-47180","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-47181","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-47183","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-47185","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-47189","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-0487","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-4744","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-48626","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-0160","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-1192","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-28746","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-35827","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-52454","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-52469","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-52470","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-52474","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-52476","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-52477","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-52500","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-52509","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-52572","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-52575","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-52583","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-52590","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-52591","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-52607","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-52628","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-6270","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-6356","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-6531","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-6535","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-6536","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-7042","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-7192","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-22099","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-26600","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-26614","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-26642","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-26704","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-26733","tags":["web"]},{"url":"https://www.suse.com/support/update/announcement/2024/suse-su-20241465-1/","tags":["advisory"]},{"url":"https://bugzilla.suse.com/1220400","tags":["report"]},{"url":"https://bugzilla.suse.com/1220414","tags":["report"]},{"url":"https://bugzilla.suse.com/1220425","tags":["report"]},{"url":"https://bugzilla.suse.com/1220426","tags":["report"]},{"url":"https://bugzilla.suse.com/1220429","tags":["report"]},{"url":"https://bugzilla.suse.com/1220432","tags":["report"]},{"url":"https://bugzilla.suse.com/1220465","tags":["report"]},{"url":"https://bugzilla.suse.com/1220475","tags":["report"]},{"url":"https://bugzilla.suse.com/1220486","tags":["report"]},{"url":"https://bugzilla.suse.com/1220487","tags":["report"]},{"url":"https://bugzilla.suse.com/1220516","tags":["report"]},{"url":"https://bugzilla.suse.com/1220557","tags":["report"]},{"url":"https://bugzilla.suse.com/1220621","tags":["report"]},{"url":"https://bugzilla.suse.com/1220630","tags":["report"]},{"url":"https://bugzilla.suse.com/1220639","tags":["report"]},{"url":"https://bugzilla.suse.com/1220663","tags":["report"]},{"url":"https://bugzilla.suse.com/1220670","tags":["report"]},{"url":"https://bugzilla.suse.com/1220677","tags":["report"]},{"url":"https://bugzilla.suse.com/1220678","tags":["report"]},{"url":"https://bugzilla.suse.com/1220685","tags":["report"]},{"url":"https://bugzilla.suse.com/1220688","tags":["report"]},{"url":"https://bugzilla.suse.com/1220733","tags":["report"]},{"url":"https://bugzilla.suse.com/1220734","tags":["report"]},{"url":"https://bugzilla.suse.com/1220753","tags":["report"]},{"url":"https://bugzilla.suse.com/1220758","tags":["report"]},{"url":"https://bugzilla.suse.com/1220759","tags":["report"]},{"url":"https://bugzilla.suse.com/1220824","tags":["report"]},{"url":"https://bugzilla.suse.com/1220954","tags":["report"]},{"url":"https://bugzilla.suse.com/1220979","tags":["report"]},{"url":"https://bugzilla.suse.com/1220982","tags":["report"]},{"url":"https://bugzilla.suse.com/1220985","tags":["report"]},{"url":"https://bugzilla.suse.com/1220987","tags":["report"]},{"url":"https://bugzilla.suse.com/1221015","tags":["report"]},{"url":"https://bugzilla.suse.com/1221276","tags":["report"]},{"url":"https://bugzilla.suse.com/1221552","tags":["report"]},{"url":"https://bugzilla.suse.com/1221931","tags":["report"]},{"url":"https://bugzilla.suse.com/1221932","tags":["report"]},{"url":"https://bugzilla.suse.com/1221973","tags":["report"]},{"url":"https://bugzilla.suse.com/1221974","tags":["report"]},{"url":"https://bugzilla.suse.com/1221978","tags":["report"]},{"url":"https://bugzilla.suse.com/1221990","tags":["report"]},{"url":"https://bugzilla.suse.com/1221996","tags":["report"]},{"url":"https://bugzilla.suse.com/1222003","tags":["report"]},{"url":"https://bugzilla.suse.com/1222878","tags":["report"]},{"url":"https://www.suse.com/security/cve/CVE-2020-36781","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-46908","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-46911","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-46914","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-46917","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-46918","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-46919","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-46920","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-46922","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-46931","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-46933","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-46956","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-46959","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-46976","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-46980","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-46983","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-47001","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-47003","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-47009","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-47014","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-47017","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-47026","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-47035","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-47038","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-47044","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-47046","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-47087","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-47095","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-47097","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-47100","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-47101","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-47130","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-47136","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-47137","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-47150","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-47160","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-47164","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-47174","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-47175","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-47176","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-47202","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-52492","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-52508","tags":["web"]},{"url":"https://www.suse.com/support/update/announcement/2024/suse-su-20241489-1/","tags":["advisory"]},{"url":"https://bugzilla.suse.com/1184942","tags":["report"]},{"url":"https://www.suse.com/security/cve/CVE-2021-29155","tags":["web"]},{"url":"https://www.suse.com/support/update/announcement/2025/suse-su-202502846-1/","tags":["advisory"]},{"url":"https://bugzilla.suse.com/1171844","tags":["report"]},{"url":"https://bugzilla.suse.com/1205711","tags":["report"]},{"url":"https://bugzilla.suse.com/1210629","tags":["report"]},{"url":"https://bugzilla.suse.com/1220704","tags":["report"]},{"url":"https://bugzilla.suse.com/1223634","tags":["report"]},{"url":"https://bugzilla.suse.com/1223638","tags":["report"]},{"url":"https://bugzilla.suse.com/1225000","tags":["report"]},{"url":"https://bugzilla.suse.com/1230216","tags":["report"]},{"url":"https://bugzilla.suse.com/1230581","tags":["report"]},{"url":"https://bugzilla.suse.com/1237881","tags":["report"]},{"url":"https://bugzilla.suse.com/1238160","tags":["report"]},{"url":"https://bugzilla.suse.com/1238374","tags":["report"]},{"url":"https://bugzilla.suse.com/1238400","tags":["report"]},{"url":"https://bugzilla.suse.com/1240224","tags":["report"]},{"url":"https://bugzilla.suse.com/1240722","tags":["report"]},{"url":"https://bugzilla.suse.com/1242365","tags":["report"]},{"url":"https://bugzilla.suse.com/1242414","tags":["report"]},{"url":"https://bugzilla.suse.com/1242446","tags":["report"]},{"url":"https://bugzilla.suse.com/1242548","tags":["report"]},{"url":"https://bugzilla.suse.com/1242780","tags":["report"]},{"url":"https://bugzilla.suse.com/1242837","tags":["report"]},{"url":"https://bugzilla.suse.com/1242960","tags":["report"]},{"url":"https://bugzilla.suse.com/1243068","tags":["report"]},{"url":"https://bugzilla.suse.com/1243479","tags":["report"]},{"url":"https://bugzilla.suse.com/1244735","tags":["report"]},{"url":"https://bugzilla.suse.com/1244750","tags":["report"]},{"url":"https://bugzilla.suse.com/1244792","tags":["report"]},{"url":"https://bugzilla.suse.com/1244801","tags":["report"]},{"url":"https://bugzilla.suse.com/1244840","tags":["report"]},{"url":"https://bugzilla.suse.com/1244860","tags":["report"]},{"url":"https://bugzilla.suse.com/1244883","tags":["report"]},{"url":"https://bugzilla.suse.com/1245051","tags":["report"]},{"url":"https://bugzilla.suse.com/1245058","tags":["report"]},{"url":"https://bugzilla.suse.com/1245060","tags":["report"]},{"url":"https://bugzilla.suse.com/1245073","tags":["report"]},{"url":"https://bugzilla.suse.com/1245078","tags":["report"]},{"url":"https://bugzilla.suse.com/1245121","tags":["report"]},{"url":"https://bugzilla.suse.com/1245132","tags":["report"]},{"url":"https://bugzilla.suse.com/1245139","tags":["report"]},{"url":"https://bugzilla.suse.com/1245151","tags":["report"]},{"url":"https://bugzilla.suse.com/1245201","tags":["report"]},{"url":"https://bugzilla.suse.com/1245210","tags":["report"]},{"url":"https://bugzilla.suse.com/1245217","tags":["report"]},{"url":"https://bugzilla.suse.com/1245265","tags":["report"]},{"url":"https://bugzilla.suse.com/1245649","tags":["report"]},{"url":"https://bugzilla.suse.com/1245668","tags":["report"]},{"url":"https://bugzilla.suse.com/1245675","tags":["report"]},{"url":"https://bugzilla.suse.com/1245682","tags":["report"]},{"url":"https://bugzilla.suse.com/1245689","tags":["report"]},{"url":"https://bugzilla.suse.com/1245708","tags":["report"]},{"url":"https://bugzilla.suse.com/1245747","tags":["report"]},{"url":"https://bugzilla.suse.com/1245758","tags":["report"]},{"url":"https://bugzilla.suse.com/1245768","tags":["report"]},{"url":"https://bugzilla.suse.com/1245777","tags":["report"]},{"url":"https://bugzilla.suse.com/1245945","tags":["report"]},{"url":"https://bugzilla.suse.com/1245952","tags":["report"]},{"url":"https://bugzilla.suse.com/1245954","tags":["report"]},{"url":"https://bugzilla.suse.com/1245970","tags":["report"]},{"url":"https://bugzilla.suse.com/1245976","tags":["report"]},{"url":"https://bugzilla.suse.com/1245986","tags":["report"]},{"url":"https://bugzilla.suse.com/1246000","tags":["report"]},{"url":"https://bugzilla.suse.com/1246008","tags":["report"]},{"url":"https://bugzilla.suse.com/1246029","tags":["report"]},{"url":"https://bugzilla.suse.com/1246037","tags":["report"]},{"url":"https://bugzilla.suse.com/1246045","tags":["report"]},{"url":"https://bugzilla.suse.com/1246171","tags":["report"]},{"url":"https://bugzilla.suse.com/1246182","tags":["report"]},{"url":"https://bugzilla.suse.com/1246243","tags":["report"]},{"url":"https://bugzilla.suse.com/1246253","tags":["report"]},{"url":"https://bugzilla.suse.com/1246386","tags":["report"]},{"url":"https://bugzilla.suse.com/1246387","tags":["report"]},{"url":"https://bugzilla.suse.com/1246459","tags":["report"]},{"url":"https://bugzilla.suse.com/1246473","tags":["report"]},{"url":"https://bugzilla.suse.com/1246781","tags":["report"]},{"url":"https://bugzilla.suse.com/1247141","tags":["report"]},{"url":"https://bugzilla.suse.com/1247147","tags":["report"]},{"url":"https://bugzilla.suse.com/1247177","tags":["report"]},{"url":"https://bugzilla.suse.com/1247181","tags":["report"]},{"url":"https://bugzilla.suse.com/1247279","tags":["report"]},{"url":"https://bugzilla.suse.com/1247314","tags":["report"]},{"url":"https://bugzilla.suse.com/1247348","tags":["report"]},{"url":"https://bugzilla.suse.com/1247349","tags":["report"]},{"url":"https://bugzilla.suse.com/1247437","tags":["report"]},{"url":"https://www.suse.com/security/cve/CVE-2021-46987","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-4129","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-49138","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-49319","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-49323","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-49768","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-49825","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-49934","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-49948","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-49969","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-49993","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-50025","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-50027","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-50030","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-50033","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-50103","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-50149","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-50226","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-2176","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-52878","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-53020","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-53117","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-53118","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-26974","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-26982","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-44963","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-46713","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-49861","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-21731","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-21928","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-23163","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-37798","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-37856","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-37885","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-37920","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38034","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38035","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38040","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38051","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38058","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38064","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38068","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38074","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38079","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38094","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38105","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38108","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38112","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38115","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38126","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38147","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38157","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38161","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38166","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38177","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38180","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38181","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38192","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38193","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38198","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38200","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38211","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38212","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38213","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38222","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38249","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38250","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38264","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38312","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38319","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38323","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38337","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38350","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38375","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38391","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38403","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38415","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38420","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38468","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38477","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38494","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38495","tags":["web"]},{"url":"https://ubuntu.com/security/CVE-2021-46984","tags":["report"]},{"url":"https://git.kernel.org/linus/efed9a3337e341bd0989161b97453b52567bc59d","tags":["report"]}],"sources":{"cve":[{"id":"CVE-2021-46984","title":"kyber: fix out of bounds access when preempted","description":"In the Linux kernel, the following vulnerability has been resolved:\n\nkyber: fix out of bounds access when preempted\n\n__blk_mq_sched_bio_merge() gets the ctx and hctx for the current CPU and\npasses the hctx to -\u003ebio_merge(). kyber_bio_merge() then gets the ctx\nfor the current CPU again and uses that to get the corresponding Kyber\ncontext in the passed hctx. However, the thread may be preempted between\nthe two calls to blk_mq_get_ctx(), and the ctx returned the second time\nmay no longer correspond to the passed hctx. This \"works\" accidentally\nmost of the time, but it can cause us to read garbage if the second ctx\ncame from an hctx with more ctx's than the first one (i.e., if\nctx-\u003eindex_hw[hctx-\u003etype] \u003e hctx-\u003enr_ctx).\n\nThis manifested as this UBSAN array index out of bounds error reported\nby Jakub:\n\nUBSAN: array-index-out-of-bounds in ../kernel/locking/qspinlock.c:130:9\nindex 13106 is out of range for type 'long unsigned int [128]'\nCall Trace:\n dump_stack+0xa4/0xe5\n ubsan_epilogue+0x5/0x40\n __ubsan_handle_out_of_bounds.cold.13+0x2a/0x34\n queued_spin_lock_slowpath+0x476/0x480\n do_raw_spin_lock+0x1c2/0x1d0\n kyber_bio_merge+0x112/0x180\n blk_mq_submit_bio+0x1f5/0x1100\n submit_bio_noacct+0x7b0/0x870\n submit_bio+0xc2/0x3a0\n btrfs_map_bio+0x4f0/0x9d0\n btrfs_submit_data_bio+0x24e/0x310\n submit_one_bio+0x7f/0xb0\n submit_extent_page+0xc4/0x440\n __extent_writepage_io+0x2b8/0x5e0\n __extent_writepage+0x28d/0x6e0\n extent_write_cache_pages+0x4d7/0x7a0\n extent_writepages+0xa2/0x110\n do_writepages+0x8f/0x180\n __writeback_single_inode+0x99/0x7f0\n writeback_sb_inodes+0x34e/0x790\n __writeback_inodes_wb+0x9e/0x120\n wb_writeback+0x4d2/0x660\n wb_workfn+0x64d/0xa10\n process_one_work+0x53a/0xa80\n worker_thread+0x69/0x5b0\n kthread+0x20b/0x240\n ret_from_fork+0x1f/0x30\n\nOnly Kyber uses the hctx, so fix it by passing the request_queue to\n-\u003ebio_merge() instead. BFQ and mq-deadline just use that, and Kyber can\nmap the queues itself to avoid the mismatch.","status":"published","published":"2024-02-28T08:13:12.835Z","modified":"2026-08-05T08:45:23.565Z","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":"cna"}],"updated_at":"2026-11-02T14:33:03.320536Z"}],"euvd":[{"id":"EUVD-2021-33632","description":"In the Linux kernel, the following vulnerability has been resolved:\n\nkyber: fix out of bounds access when preempted\n\n__blk_mq_sched_bio_merge() gets the ctx and hctx for the current CPU and\npasses the hctx to -\u003ebio_merge(). kyber_bio_merge() then gets the ctx\nfor the current CPU again and uses that to get the corresponding Kyber\ncontext in the passed hctx. However, the thread may be preempted between\nthe two calls to blk_mq_get_ctx(), and the ctx returned the second time\nmay no longer correspond to the passed hctx. This \"works\" accidentally\nmost of the time, but it can cause us to read garbage if the second ctx\ncame from an hctx with more ctx's than the first one (i.e., if\nctx-\u003eindex_hw[hctx-\u003etype] \u003e hctx-\u003enr_ctx).\n\nThis manifested as this UBSAN array index out of bounds error reported\nby Jakub:\n\nUBSAN: array-index-out-of-bounds in ../kernel/locking/qspinlock.c:130:9\nindex 13106 is out of range for type 'long unsigned int [128]'\nCall Trace:\n dump_stack+0xa4/0xe5\n ubsan_epilogue+0x5/0x40\n __ubsan_handle_out_of_bounds.cold.13+0x2a/0x34\n queued_spin_lock_slowpath+0x476/0x480\n do_raw_spin_lock+0x1c2/0x1d0\n kyber_bio_merge+0x112/0x180\n blk_mq_submit_bio+0x1f5/0x1100\n submit_bio_noacct+0x7b0/0x870\n submit_bio+0xc2/0x3a0\n btrfs_map_bio+0x4f0/0x9d0\n btrfs_submit_data_bio+0x24e/0x310\n submit_one_bio+0x7f/0xb0\n submit_extent_page+0xc4/0x440\n __extent_writepage_io+0x2b8/0x5e0\n __extent_writepage+0x28d/0x6e0\n extent_write_cache_pages+0x4d7/0x7a0\n extent_writepages+0xa2/0x110\n do_writepages+0x8f/0x180\n __writeback_single_inode+0x99/0x7f0\n writeback_sb_inodes+0x34e/0x790\n __writeback_inodes_wb+0x9e/0x120\n wb_writeback+0x4d2/0x660\n wb_workfn+0x64d/0xa10\n process_one_work+0x53a/0xa80\n worker_thread+0x69/0x5b0\n kthread+0x20b/0x240\n ret_from_fork+0x1f/0x30\n\nOnly Kyber uses the hctx, so fix it by passing the request_queue to\n-\u003ebio_merge() instead. BFQ and mq-deadline just use that, and Kyber can\nmap the queues itself to avoid the mismatch.","status":"published","published":"2024-02-28T08:13:12Z","modified":"2026-08-05T08:45:23Z","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-02T18:02:22.159181Z"}],"ghsa":[{"id":"GHSA-4qp7-5rvw-5428","title":"In the Linux kernel, the following vulnerability has been resolved:\n\nkyber: fix out of bounds...","description":"In the Linux kernel, the following vulnerability has been resolved:\n\nkyber: fix out of bounds access when preempted\n\n__blk_mq_sched_bio_merge() gets the ctx and hctx for the current CPU and\npasses the hctx to -\u003ebio_merge(). kyber_bio_merge() then gets the ctx\nfor the current CPU again and uses that to get the corresponding Kyber\ncontext in the passed hctx. However, the thread may be preempted between\nthe two calls to blk_mq_get_ctx(), and the ctx returned the second time\nmay no longer correspond to the passed hctx. This \"works\" accidentally\nmost of the time, but it can cause us to read garbage if the second ctx\ncame from an hctx with more ctx's than the first one (i.e., if\nctx-\u003eindex_hw[hctx-\u003etype] \u003e hctx-\u003enr_ctx).\n\nThis manifested as this UBSAN array index out of bounds error reported\nby Jakub:\n\nUBSAN: array-index-out-of-bounds in ../kernel/locking/qspinlock.c:130:9\nindex 13106 is out of range for type 'long unsigned int [128]'\nCall Trace:\n dump_stack+0xa4/0xe5\n ubsan_epilogue+0x5/0x40\n __ubsan_handle_out_of_bounds.cold.13+0x2a/0x34\n queued_spin_lock_slowpath+0x476/0x480\n do_raw_spin_lock+0x1c2/0x1d0\n kyber_bio_merge+0x112/0x180\n blk_mq_submit_bio+0x1f5/0x1100\n submit_bio_noacct+0x7b0/0x870\n submit_bio+0xc2/0x3a0\n btrfs_map_bio+0x4f0/0x9d0\n btrfs_submit_data_bio+0x24e/0x310\n submit_one_bio+0x7f/0xb0\n submit_extent_page+0xc4/0x440\n __extent_writepage_io+0x2b8/0x5e0\n __extent_writepage+0x28d/0x6e0\n extent_write_cache_pages+0x4d7/0x7a0\n extent_writepages+0xa2/0x110\n do_writepages+0x8f/0x180\n __writeback_single_inode+0x99/0x7f0\n writeback_sb_inodes+0x34e/0x790\n __writeback_inodes_wb+0x9e/0x120\n wb_writeback+0x4d2/0x660\n wb_workfn+0x64d/0xa10\n process_one_work+0x53a/0xa80\n worker_thread+0x69/0x5b0\n kthread+0x20b/0x240\n ret_from_fork+0x1f/0x30\n\nOnly Kyber uses the hctx, so fix it by passing the request_queue to\n-\u003ebio_merge() instead. BFQ and mq-deadline just use that, and Kyber can\nmap the queues itself to avoid the mismatch.","status":"published","published":"2024-02-28T09:30:37Z","modified":"2024-12-06T15:32:21Z","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"}],"cwes":["CWE-129"],"updated_at":"2026-11-02T14:59:04.219575Z"}],"nvd":[{"id":"CVE-2021-46984","description":"In the Linux kernel, the following vulnerability has been resolved:\n\nkyber: fix out of bounds access when preempted\n\n__blk_mq_sched_bio_merge() gets the ctx and hctx for the current CPU and\npasses the hctx to -\u003ebio_merge(). kyber_bio_merge() then gets the ctx\nfor the current CPU again and uses that to get the corresponding Kyber\ncontext in the passed hctx. However, the thread may be preempted between\nthe two calls to blk_mq_get_ctx(), and the ctx returned the second time\nmay no longer correspond to the passed hctx. This \"works\" accidentally\nmost of the time, but it can cause us to read garbage if the second ctx\ncame from an hctx with more ctx's than the first one (i.e., if\nctx-\u003eindex_hw[hctx-\u003etype] \u003e hctx-\u003enr_ctx).\n\nThis manifested as this UBSAN array index out of bounds error reported\nby Jakub:\n\nUBSAN: array-index-out-of-bounds in ../kernel/locking/qspinlock.c:130:9\nindex 13106 is out of range for type 'long unsigned int [128]'\nCall Trace:\n dump_stack+0xa4/0xe5\n ubsan_epilogue+0x5/0x40\n __ubsan_handle_out_of_bounds.cold.13+0x2a/0x34\n queued_spin_lock_slowpath+0x476/0x480\n do_raw_spin_lock+0x1c2/0x1d0\n kyber_bio_merge+0x112/0x180\n blk_mq_submit_bio+0x1f5/0x1100\n submit_bio_noacct+0x7b0/0x870\n submit_bio+0xc2/0x3a0\n btrfs_map_bio+0x4f0/0x9d0\n btrfs_submit_data_bio+0x24e/0x310\n submit_one_bio+0x7f/0xb0\n submit_extent_page+0xc4/0x440\n __extent_writepage_io+0x2b8/0x5e0\n __extent_writepage+0x28d/0x6e0\n extent_write_cache_pages+0x4d7/0x7a0\n extent_writepages+0xa2/0x110\n do_writepages+0x8f/0x180\n __writeback_single_inode+0x99/0x7f0\n writeback_sb_inodes+0x34e/0x790\n __writeback_inodes_wb+0x9e/0x120\n wb_writeback+0x4d2/0x660\n wb_workfn+0x64d/0xa10\n process_one_work+0x53a/0xa80\n worker_thread+0x69/0x5b0\n kthread+0x20b/0x240\n ret_from_fork+0x1f/0x30\n\nOnly Kyber uses the hctx, so fix it by passing the request_queue to\n-\u003ebio_merge() instead. BFQ and mq-deadline just use that, and Kyber can\nmap the queues itself to avoid the mismatch.","status":"published","published":"2024-02-28T09:15:37.45Z","modified":"2026-08-04T10:16:39.817Z","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":"secondary"},{"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"}],"cwes":["CWE-129"],"updated_at":"2026-11-02T14:07:08.163458Z"}],"osv":[{"id":"CVE-2021-46984","description":"In the Linux kernel, the following vulnerability has been resolved:\n\nkyber: fix out of bounds access when preempted\n\n__blk_mq_sched_bio_merge() gets the ctx and hctx for the current CPU and\npasses the hctx to -\u003ebio_merge(). kyber_bio_merge() then gets the ctx\nfor the current CPU again and uses that to get the corresponding Kyber\ncontext in the passed hctx. However, the thread may be preempted between\nthe two calls to blk_mq_get_ctx(), and the ctx returned the second time\nmay no longer correspond to the passed hctx. This \"works\" accidentally\nmost of the time, but it can cause us to read garbage if the second ctx\ncame from an hctx with more ctx's than the first one (i.e., if\nctx-\u003eindex_hw[hctx-\u003etype] \u003e hctx-\u003enr_ctx).\n\nThis manifested as this UBSAN array index out of bounds error reported\nby Jakub:\n\nUBSAN: array-index-out-of-bounds in ../kernel/locking/qspinlock.c:130:9\nindex 13106 is out of range for type 'long unsigned int [128]'\nCall Trace:\n dump_stack+0xa4/0xe5\n ubsan_epilogue+0x5/0x40\n __ubsan_handle_out_of_bounds.cold.13+0x2a/0x34\n queued_spin_lock_slowpath+0x476/0x480\n do_raw_spin_lock+0x1c2/0x1d0\n kyber_bio_merge+0x112/0x180\n blk_mq_submit_bio+0x1f5/0x1100\n submit_bio_noacct+0x7b0/0x870\n submit_bio+0xc2/0x3a0\n btrfs_map_bio+0x4f0/0x9d0\n btrfs_submit_data_bio+0x24e/0x310\n submit_one_bio+0x7f/0xb0\n submit_extent_page+0xc4/0x440\n __extent_writepage_io+0x2b8/0x5e0\n __extent_writepage+0x28d/0x6e0\n extent_write_cache_pages+0x4d7/0x7a0\n extent_writepages+0xa2/0x110\n do_writepages+0x8f/0x180\n __writeback_single_inode+0x99/0x7f0\n writeback_sb_inodes+0x34e/0x790\n __writeback_inodes_wb+0x9e/0x120\n wb_writeback+0x4d2/0x660\n wb_workfn+0x64d/0xa10\n process_one_work+0x53a/0xa80\n worker_thread+0x69/0x5b0\n kthread+0x20b/0x240\n ret_from_fork+0x1f/0x30\n\nOnly Kyber uses the hctx, so fix it by passing the request_queue to\n-\u003ebio_merge() instead. BFQ and mq-deadline just use that, and Kyber can\nmap the queues itself to avoid the mismatch.","status":"published","published":"2024-02-28T09:15:37.45Z","modified":"2026-03-14T11:18:52.799586Z","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:44:22.18434Z"},{"id":"DEBIAN-CVE-2021-46984","description":"In the Linux kernel, the following vulnerability has been resolved:  kyber: fix out of bounds access when preempted  __blk_mq_sched_bio_merge() gets the ctx and hctx for the current CPU and passes the hctx to -\u003ebio_merge(). kyber_bio_merge() then gets the ctx for the current CPU again and uses that to get the corresponding Kyber context in the passed hctx. However, the thread may be preempted between the two calls to blk_mq_get_ctx(), and the ctx returned the second time may no longer correspond to the passed hctx. This \"works\" accidentally most of the time, but it can cause us to read garbage if the second ctx came from an hctx with more ctx's than the first one (i.e., if ctx-\u003eindex_hw[hctx-\u003etype] \u003e hctx-\u003enr_ctx).  This manifested as this UBSAN array index out of bounds error reported by Jakub:  UBSAN: array-index-out-of-bounds in ../kernel/locking/qspinlock.c:130:9 index 13106 is out of range for type 'long unsigned int [128]' Call Trace:  dump_stack+0xa4/0xe5  ubsan_epilogue+0x5/0x40  __ubsan_handle_out_of_bounds.cold.13+0x2a/0x34  queued_spin_lock_slowpath+0x476/0x480  do_raw_spin_lock+0x1c2/0x1d0  kyber_bio_merge+0x112/0x180  blk_mq_submit_bio+0x1f5/0x1100  submit_bio_noacct+0x7b0/0x870  submit_bio+0xc2/0x3a0  btrfs_map_bio+0x4f0/0x9d0  btrfs_submit_data_bio+0x24e/0x310  submit_one_bio+0x7f/0xb0  submit_extent_page+0xc4/0x440  __extent_writepage_io+0x2b8/0x5e0  __extent_writepage+0x28d/0x6e0  extent_write_cache_pages+0x4d7/0x7a0  extent_writepages+0xa2/0x110  do_writepages+0x8f/0x180  __writeback_single_inode+0x99/0x7f0  writeback_sb_inodes+0x34e/0x790  __writeback_inodes_wb+0x9e/0x120  wb_writeback+0x4d2/0x660  wb_workfn+0x64d/0xa10  process_one_work+0x53a/0xa80  worker_thread+0x69/0x5b0  kthread+0x20b/0x240  ret_from_fork+0x1f/0x30  Only Kyber uses the hctx, so fix it by passing the request_queue to -\u003ebio_merge() instead. BFQ and mq-deadline just use that, and Kyber can map the queues itself to avoid the mismatch.","status":"published","published":"2024-02-28T09:15:37.45Z","modified":"2026-10-23T18:04:17.698474746Z","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:45:36.081807Z"},{"id":"OESA-2024-1483","title":"kernel security update","description":"The Linux Kernel, the operating system core itself.\r\n\r\nSecurity Fix(es):\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\ni2c: img-scb: fix reference leak when pm_runtime_get_sync fails\r\n\r\nThe PM reference count is not expected to be incremented on\nreturn in functions img_i2c_xfer and img_i2c_init.\r\n\r\nHowever, pm_runtime_get_sync will increment the PM reference\ncount even failed. Forgetting to putting operation will result\nin a reference leak here.\r\n\r\nReplace it with pm_runtime_resume_and_get to keep usage\ncounter balanced.(CVE-2020-36783)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nkyber: fix out of bounds access when preempted\r\n\r\n__blk_mq_sched_bio_merge() gets the ctx and hctx for the current CPU and\npasses the hctx to -\u0026gt;bio_merge(). kyber_bio_merge() then gets the ctx\nfor the current CPU again and uses that to get the corresponding Kyber\ncontext in the passed hctx. However, the thread may be preempted between\nthe two calls to blk_mq_get_ctx(), and the ctx returned the second time\nmay no longer correspond to the passed hctx. This \u0026quot;works\u0026quot; accidentally\nmost of the time, but it can cause us to read garbage if the second ctx\ncame from an hctx with more ctx\u0026apos;s than the first one (i.e., if\nctx-\u0026gt;index_hw[hctx-\u0026gt;type] \u0026gt; hctx-\u0026gt;nr_ctx).\r\n\r\nThis manifested as this UBSAN array index out of bounds error reported\nby Jakub:\r\n\r\nUBSAN: array-index-out-of-bounds in ../kernel/locking/qspinlock.c:130:9\nindex 13106 is out of range for type \u0026apos;long unsigned int [128]\u0026apos;\nCall Trace:\n dump_stack+0xa4/0xe5\n ubsan_epilogue+0x5/0x40\n __ubsan_handle_out_of_bounds.cold.13+0x2a/0x34\n queued_spin_lock_slowpath+0x476/0x480\n do_raw_spin_lock+0x1c2/0x1d0\n kyber_bio_merge+0x112/0x180\n blk_mq_submit_bio+0x1f5/0x1100\n submit_bio_noacct+0x7b0/0x870\n submit_bio+0xc2/0x3a0\n btrfs_map_bio+0x4f0/0x9d0\n btrfs_submit_data_bio+0x24e/0x310\n submit_one_bio+0x7f/0xb0\n submit_extent_page+0xc4/0x440\n __extent_writepage_io+0x2b8/0x5e0\n __extent_writepage+0x28d/0x6e0\n extent_write_cache_pages+0x4d7/0x7a0\n extent_writepages+0xa2/0x110\n do_writepages+0x8f/0x180\n __writeback_single_inode+0x99/0x7f0\n writeback_sb_inodes+0x34e/0x790\n __writeback_inodes_wb+0x9e/0x120\n wb_writeback+0x4d2/0x660\n wb_workfn+0x64d/0xa10\n process_one_work+0x53a/0xa80\n worker_thread+0x69/0x5b0\n kthread+0x20b/0x240\n ret_from_fork+0x1f/0x30\r\n\r\nOnly Kyber uses the hctx, so fix it by passing the request_queue to\n-\u0026gt;bio_merge() instead. BFQ and mq-deadline just use that, and Kyber can\nmap the queues itself to avoid the mismatch.(CVE-2021-46984)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nbus: qcom: Put child node before return\r\n\r\nPut child node before return to fix potential reference count leak.\nGenerally, the reference count of child is incremented and decremented\nautomatically in the macro for_each_available_child_of_node() and should\nbe decremented manually if the loop is broken in loop body.(CVE-2021-47054)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\ncrypto: qat - ADF_STATUS_PF_RUNNING should be set after adf_dev_init\r\n\r\nADF_STATUS_PF_RUNNING is (only) used and checked by adf_vf2pf_shutdown()\nbefore calling adf_iov_putmsg()-\u0026gt;mutex_lock(vf2pf_lock), however the\nvf2pf_lock is initialized in adf_dev_init(), which can fail and when it\nfail, the vf2pf_lock is either not initialized or destroyed, a subsequent\nuse of vf2pf_lock will cause issue.\nTo fix this issue, only set this flag if adf_dev_init() returns 0.\r\n\r\n[    7.178404] BUG: KASAN: user-memory-access in __mutex_lock.isra.0+0x1ac/0x7c0\n[    7.180345] Call Trace:\n[    7.182576]  mutex_lock+0xc9/0xd0\n[    7.183257]  adf_iov_putmsg+0x118/0x1a0 [intel_qat]\n[    7.183541]  adf_vf2pf_shutdown+0x4d/0x7b [intel_qat]\n[    7.183834]  adf_dev_shutdown+0x172/0x2b0 [intel_qat]\n[    7.184127]  adf_probe+0x5e9/0x600 [qat_dh895xccvf](CVE-2021-47056)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nKVM: Stop looking for coalesced MMIO zones if the bus is destroyed\r\n\r\nAbort the walk of coalesced MMIO zones if kvm_io_bus_unregister_dev()\nfails to allocate memory for the new instance of the bus.  If it can\u0026apos;t\ninstantiate a new bus, unregister_dev() destroys all devices _except_ the\ntarget device.   But, it doesn\u0026apos;t tell the caller that it obliterated the\nbus and invoked the destructor for all devices that were on the bus.  In\nthe coalesced MMIO case, this can result in a deleted list entry\ndereference due to attempting to continue iterating on coalesced_zones\nafter future entries (in the walk) have been deleted.\r\n\r\nOpportunistically add curly braces to the for-loop, which encompasses\nmany lines but sneaks by without braces due to the guts being a single\nif statement.(CVE-2021-47060)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nKVM: Destroy I/O bus devices on unregister failure _after_ sync\u0026apos;ing SRCU\r\n\r\nIf allocating a new instance of an I/O bus fails when unregistering a\ndevice, wait to destroy the device until after all readers are guaranteed\nto see the new null bus.  Destroying devices before the bus is nullified\ncould lead to use-after-free since readers expect the devices on their\nreference of the bus to remain valid.(CVE-2021-47061)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\ndrm: bridge/panel: Cleanup connector on bridge detach\r\n\r\nIf we don\u0026apos;t call drm_connector_cleanup() manually in\npanel_bridge_detach(), the connector will be cleaned up with the other\nDRM objects in the call to drm_mode_config_cleanup(). However, since our\ndrm_connector is devm-allocated, by the time drm_mode_config_cleanup()\nwill be called, our connector will be long gone. Therefore, the\nconnector must be cleaned up when the bridge is detached to avoid\nuse-after-free conditions.\r\n\r\nv2: Cleanup connector only if it was created\r\n\r\nv3: Add FIXME\r\n\r\nv4: (Use connector-\u0026gt;dev) directly in if() block(CVE-2021-47063)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nuio_hv_generic: Fix a memory leak in error handling paths\r\n\r\nIf \u0026apos;vmbus_establish_gpadl()\u0026apos; fails, the (recv|send)_gpadl will not be\nupdated and \u0026apos;hv_uio_cleanup()\u0026apos; in the error handling path will not be\nable to free the corresponding buffer.\r\n\r\nIn such a case, we need to free the buffer explicitly.(CVE-2021-47071)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nnvme-loop: fix memory leak in nvme_loop_create_ctrl()\r\n\r\nWhen creating loop ctrl in nvme_loop_create_ctrl(), if nvme_init_ctrl()\nfails, the loop ctrl should be freed before jumping to the \u0026quot;out\u0026quot; label.(CVE-2021-47074)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nscsi: qedf: Add pointer checks in qedf_update_link_speed()\r\n\r\nThe following trace was observed:\r\n\r\n [   14.042059] Call Trace:\n [   14.042061]  \u0026lt;IRQ\u0026gt;\n [   14.042068]  qedf_link_update+0x144/0x1f0 [qedf]\n [   14.042117]  qed_link_update+0x5c/0x80 [qed]\n [   14.042135]  qed_mcp_handle_link_change+0x2d2/0x410 [qed]\n [   14.042155]  ? qed_set_ptt+0x70/0x80 [qed]\n [   14.042170]  ? qed_set_ptt+0x70/0x80 [qed]\n [   14.042186]  ? qed_rd+0x13/0x40 [qed]\n [   14.042205]  qed_mcp_handle_events+0x437/0x690 [qed]\n [   14.042221]  ? qed_set_ptt+0x70/0x80 [qed]\n [   14.042239]  qed_int_sp_dpc+0x3a6/0x3e0 [qed]\n [   14.042245]  tasklet_action_common.isra.14+0x5a/0x100\n [   14.042250]  __do_softirq+0xe4/0x2f8\n [   14.042253]  irq_exit+0xf7/0x100\n [   14.042255]  do_IRQ+0x7f/0xd0\n [   14.042257]  common_interrupt+0xf/0xf\n [   14.042259]  \u0026lt;/IRQ\u0026gt;\r\n\r\nAPI qedf_link_update() is getting called from QED but by that time\nshost_data is not initialised. This results in a NULL pointer dereference\nwhen we try to dereference shost_data while updating supported_speeds.\r\n\r\nAdd a NULL pointer check before dereferencing shost_data.(CVE-2021-47077)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nRDMA/rxe: Clear all QP fields if creation failed\r\n\r\nrxe_qp_do_cleanup() relies on valid pointer values in QP for the properly\ncreated ones, but in case rxe_qp_from_init() failed it was filled with\ngarbage and caused tot the following error.\r\n\r\n  refcount_t: underflow; use-after-free.\n  WARNING: CPU: 1 PID: 12560 at lib/refcount.c:28 refcount_warn_saturate+0x1d1/0x1e0 lib/refcount.c:28\n  Modules linked in:\n  CPU: 1 PID: 12560 Comm: syz-executor.4 Not tainted 5.12.0-syzkaller #0\n  Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011\n  RIP: 0010:refcount_warn_saturate+0x1d1/0x1e0 lib/refcount.c:28\n  Code: e9 db fe ff ff 48 89 df e8 2c c2 ea fd e9 8a fe ff ff e8 72 6a a7 fd 48 c7 c7 e0 b2 c1 89 c6 05 dc 3a e6 09 01 e8 ee 74 fb 04 \u0026lt;0f\u0026gt; 0b e9 af fe ff ff 0f 1f 84 00 00 00 00 00 41 56 41 55 41 54 55\n  RSP: 0018:ffffc900097ceba8 EFLAGS: 00010286\n  RAX: 0000000000000000 RBX: 0000000000000000 RCX: 0000000000000000\n  RDX: 0000000000040000 RSI: ffffffff815bb075 RDI: fffff520012f9d67\n  RBP: 0000000000000003 R08: 0000000000000000 R09: 0000000000000000\n  R10: ffffffff815b4eae R11: 0000000000000000 R12: ffff8880322a4800\n  R13: ffff8880322a4940 R14: ffff888033044e00 R15: 0000000000000000\n  FS:  00007f6eb2be3700(0000) GS:ffff8880b9d00000(0000) knlGS:0000000000000000\n  CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033\n  CR2: 00007fdbe5d41000 CR3: 000000001d181000 CR4: 00000000001506e0\n  DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000\n  DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400\n  Call Trace:\n   __refcount_sub_and_test include/linux/refcount.h:283 [inline]\n   __refcount_dec_and_test include/linux/refcount.h:315 [inline]\n   refcount_dec_and_test include/linux/refcount.h:333 [inline]\n   kref_put include/linux/kref.h:64 [inline]\n   rxe_qp_do_cleanup+0x96f/0xaf0 drivers/infiniband/sw/rxe/rxe_qp.c:805\n   execute_in_process_context+0x37/0x150 kernel/workqueue.c:3327\n   rxe_elem_release+0x9f/0x180 drivers/infiniband/sw/rxe/rxe_pool.c:391\n   kref_put include/linux/kref.h:65 [inline]\n   rxe_create_qp+0x2cd/0x310 drivers/infiniband/sw/rxe/rxe_verbs.c:425\n   _ib_create_qp drivers/infiniband/core/core_priv.h:331 [inline]\n   ib_create_named_qp+0x2ad/0x1370 drivers/infiniband/core/verbs.c:1231\n   ib_create_qp include/rdma/ib_verbs.h:3644 [inline]\n   create_mad_qp+0x177/0x2d0 drivers/infiniband/core/mad.c:2920\n   ib_mad_port_open drivers/infiniband/core/mad.c:3001 [inline]\n   ib_mad_init_device+0xd6f/0x1400 drivers/infiniband/core/mad.c:3092\n   add_client_context+0x405/0x5e0 drivers/infiniband/core/device.c:717\n   enable_device_and_get+0x1cd/0x3b0 drivers/infiniband/core/device.c:1331\n   ib_register_device drivers/infiniband/core/device.c:1413 [inline]\n   ib_register_device+0x7c7/0xa50 drivers/infiniband/core/device.c:1365\n   rxe_register_device+0x3d5/0x4a0 drivers/infiniband/sw/rxe/rxe_verbs.c:1147\n   rxe_add+0x12fe/0x16d0 drivers/infiniband/sw/rxe/rxe.c:247\n   rxe_net_add+0x8c/0xe0 drivers/infiniband/sw/rxe/rxe_net.c:503\n   rxe_newlink drivers/infiniband/sw/rxe/rxe.c:269 [inline]\n   rxe_newlink+0xb7/0xe0 drivers/infiniband/sw/rxe/rxe.c:250\n   nldev_newlink+0x30e/0x550 drivers/infiniband/core/nldev.c:1555\n   rdma_nl_rcv_msg+0x36d/0x690 drivers/infiniband/core/netlink.c:195\n   rdma_nl_rcv_skb drivers/infiniband/core/netlink.c:239 [inline]\n   rdma_nl_rcv+0x2ee/0x430 drivers/infiniband/core/netlink.c:259\n   netlink_unicast_kernel net/netlink/af_netlink.c:1312 [inline]\n   netlink_unicast+0x533/0x7d0 net/netlink/af_netlink.c:1338\n   netlink_sendmsg+0x856/0xd90 net/netlink/af_netlink.c:1927\n   sock_sendmsg_nosec net/socket.c:654 [inline]\n   sock_sendmsg+0xcf/0x120 net/socket.c:674\n   ____sys_sendmsg+0x6e8/0x810 net/socket.c:2350\n   ___sys_sendmsg+0xf3/0x170 net/socket.c:2404\n   __sys_sendmsg+0xe5/0x1b0 net/socket.c:2433\n   do_syscall_64+0x3a/0xb0 arch/x86/entry/common.c:47\n   entry_SYSCALL_64_after_hwframe+0\n---truncated---(CVE-2021-47078)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nasix: fix uninit-value in asix_mdio_read()\r\n\r\nasix_read_cmd() may read less than sizeof(smsr) bytes and in this case\nsmsr will be uninitialized.\r\n\r\nFail log:\nBUG: KMSAN: uninit-value in asix_check_host_enable drivers/net/usb/asix_common.c:82 [inline]\nBUG: KMSAN: uninit-value in asix_check_host_enable drivers/net/usb/asix_common.c:82 [inline] drivers/net/usb/asix_common.c:497\nBUG: KMSAN: uninit-value in asix_mdio_read+0x3c1/0xb00 drivers/net/usb/asix_common.c:497 drivers/net/usb/asix_common.c:497\n asix_check_host_enable drivers/net/usb/asix_common.c:82 [inline]\n asix_check_host_enable drivers/net/usb/asix_common.c:82 [inline] drivers/net/usb/asix_common.c:497\n asix_mdio_read+0x3c1/0xb00 drivers/net/usb/asix_common.c:497 drivers/net/usb/asix_common.c:497(CVE-2021-47101)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nnet/tls: Fix use-after-free after the TLS device goes down and up\r\n\r\nWhen a netdev with active TLS offload goes down, tls_device_down is\ncalled to stop the offload and tear down the TLS context. However, the\nsocket stays alive, and it still points to the TLS context, which is now\ndeallocated. If a netdev goes up, while the connection is still active,\nand the data flow resumes after a number of TCP retransmissions, it will\nlead to a use-after-free of the TLS context.\r\n\r\nThis commit addresses this bug by keeping the context alive until its\nnormal destruction, and implements the necessary fallbacks, so that the\nconnection can resume in software (non-offloaded) kTLS mode.\r\n\r\nOn the TX side tls_sw_fallback is used to encrypt all packets. The RX\nside already has all the necessary fallbacks, because receiving\nnon-decrypted packets is supported. The thing needed on the RX side is\nto block resync requests, which are normally produced after receiving\nnon-decrypted packets.\r\n\r\nThe necessary synchronization is implemented for a graceful teardown:\nfirst the fallbacks are deployed, then the driver resources are released\n(it used to be possible to have a tls_dev_resync after tls_dev_del).\r\n\r\nA new flag called TLS_RX_DEV_DEGRADED is added to indicate the fallback\nmode. It\u0026apos;s used to skip the RX resync logic completely, as it becomes\nuseless, and some objects may be released (for example, resync_async,\nwhich is allocated and freed by the driver).(CVE-2021-47131)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\ndrm/amdgpu: Fix a use-after-free\r\n\r\nlooks like we forget to set ttm-\u0026gt;sg to NULL.\nHit panic below\r\n\r\n[ 1235.844104] general protection fault, probably for non-canonical address 0x6b6b6b6b6b6b7b4b: 0000 [#1] SMP DEBUG_PAGEALLOC NOPTI\n[ 1235.989074] Call Trace:\n[ 1235.991751]  sg_free_table+0x17/0x20\n[ 1235.995667]  amdgpu_ttm_backend_unbind.cold+0x4d/0xf7 [amdgpu]\n[ 1236.002288]  amdgpu_ttm_backend_destroy+0x29/0x130 [amdgpu]\n[ 1236.008464]  ttm_tt_destroy+0x1e/0x30 [ttm]\n[ 1236.013066]  ttm_bo_cleanup_memtype_use+0x51/0xa0 [ttm]\n[ 1236.018783]  ttm_bo_release+0x262/0xa50 [ttm]\n[ 1236.023547]  ttm_bo_put+0x82/0xd0 [ttm]\n[ 1236.027766]  amdgpu_bo_unref+0x26/0x50 [amdgpu]\n[ 1236.032809]  amdgpu_amdkfd_gpuvm_alloc_memory_of_gpu+0x7aa/0xd90 [amdgpu]\n[ 1236.040400]  kfd_ioctl_alloc_memory_of_gpu+0xe2/0x330 [amdgpu]\n[ 1236.046912]  kfd_ioctl+0x463/0x690 [amdgpu](CVE-2021-47142)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nnet/smc: remove device from smcd_dev_list after failed device_add()\r\n\r\nIf the device_add() for a smcd_dev fails, there\u0026apos;s no cleanup step that\nrolls back the earlier list_add(). The device subsequently gets freed,\nand we end up with a corrupted list.\r\n\r\nAdd some error handling that removes the device from the list.(CVE-2021-47143)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\ndrm/amd/amdgpu: fix refcount leak\r\n\r\n[Why]\nthe gem object rfb-\u0026gt;base.obj[0] is get according to num_planes\nin amdgpufb_create, but is not put according to num_planes\r\n\r\n[How]\nput rfb-\u0026gt;base.obj[0] in amdgpu_fbdev_destroy according to num_planes(CVE-2021-47144)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nbtrfs: do not BUG_ON in link_to_fixup_dir\r\n\r\nWhile doing error injection testing I got the following panic\r\n\r\n  kernel BUG at fs/btrfs/tree-log.c:1862!\n  invalid opcode: 0000 [#1] SMP NOPTI\n  CPU: 1 PID: 7836 Comm: mount Not tainted 5.13.0-rc1+ #305\n  Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.13.0-2.fc32 04/01/2014\n  RIP: 0010:link_to_fixup_dir+0xd5/0xe0\n  RSP: 0018:ffffb5800180fa30 EFLAGS: 00010216\n  RAX: fffffffffffffffb RBX: 00000000fffffffb RCX: ffff8f595287faf0\n  RDX: ffffb5800180fa37 RSI: ffff8f5954978800 RDI: 0000000000000000\n  RBP: ffff8f5953af9450 R08: 0000000000000019 R09: 0000000000000001\n  R10: 000151f408682970 R11: 0000000120021001 R12: ffff8f5954978800\n  R13: ffff8f595287faf0 R14: ffff8f5953c77dd0 R15: 0000000000000065\n  FS:  00007fc5284c8c40(0000) GS:ffff8f59bbd00000(0000) knlGS:0000000000000000\n  CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033\n  CR2: 00007fc5287f47c0 CR3: 000000011275e002 CR4: 0000000000370ee0\n  Call Trace:\n   replay_one_buffer+0x409/0x470\n   ? btree_read_extent_buffer_pages+0xd0/0x110\n   walk_up_log_tree+0x157/0x1e0\n   walk_log_tree+0xa6/0x1d0\n   btrfs_recover_log_trees+0x1da/0x360\n   ? replay_one_extent+0x7b0/0x7b0\n   open_ctree+0x1486/0x1720\n   btrfs_mount_root.cold+0x12/0xea\n   ? __kmalloc_track_caller+0x12f/0x240\n   legacy_get_tree+0x24/0x40\n   vfs_get_tree+0x22/0xb0\n   vfs_kern_mount.part.0+0x71/0xb0\n   btrfs_mount+0x10d/0x380\n   ? vfs_parse_fs_string+0x4d/0x90\n   legacy_get_tree+0x24/0x40\n   vfs_get_tree+0x22/0xb0\n   path_mount+0x433/0xa10\n   __x64_sys_mount+0xe3/0x120\n   do_syscall_64+0x3d/0x80\n   entry_SYSCALL_64_after_hwframe+0x44/0xae\r\n\r\nWe can get -EIO or any number of legitimate errors from\nbtrfs_search_slot(), panicing here is not the appropriate response.  The\nerror path for this code handles errors properly, simply return the\nerror.(CVE-2021-47145)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nmld: fix panic in mld_newpack()\r\n\r\nmld_newpack() doesn\u0026apos;t allow to allocate high order page,\nonly order-0 allocation is allowed.\nIf headroom size is too large, a kernel panic could occur in skb_put().\r\n\r\nTest commands:\n    ip netns del A\n    ip netns del B\n    ip netns add A\n    ip netns add B\n    ip link add veth0 type veth peer name veth1\n    ip link set veth0 netns A\n    ip link set veth1 netns B\r\n\r\n    ip netns exec A ip link set lo up\n    ip netns exec A ip link set veth0 up\n    ip netns exec A ip -6 a a 2001:db8:0::1/64 dev veth0\n    ip netns exec B ip link set lo up\n    ip netns exec B ip link set veth1 up\n    ip netns exec B ip -6 a a 2001:db8:0::2/64 dev veth1\n    for i in {1..99}\n    do\n        let A=$i-1\n        ip netns exec A ip link add ip6gre$i type ip6gre \\\n\tlocal 2001:db8:$A::1 remote 2001:db8:$A::2 encaplimit 100\n        ip netns exec A ip -6 a a 2001:db8:$i::1/64 dev ip6gre$i\n        ip netns exec A ip link set ip6gre$i up\r\n\r\n        ip netns exec B ip link add ip6gre$i type ip6gre \\\n\tlocal 2001:db8:$A::2 remote 2001:db8:$A::1 encaplimit 100\n        ip netns exec B ip -6 a a 2001:db8:$i::2/64 dev ip6gre$i\n        ip netns exec B ip link set ip6gre$i up\n    done\r\n\r\nSplat looks like:\nkernel BUG at net/core/skbuff.c:110!\ninvalid opcode: 0000 [#1] SMP DEBUG_PAGEALLOC KASAN PTI\nCPU: 0 PID: 7 Comm: kworker/0:1 Not tainted 5.12.0+ #891\nWorkqueue: ipv6_addrconf addrconf_dad_work\nRIP: 0010:skb_panic+0x15d/0x15f\nCode: 92 fe 4c 8b 4c 24 10 53 8b 4d 70 45 89 e0 48 c7 c7 00 ae 79 83\n41 57 41 56 41 55 48 8b 54 24 a6 26 f9 ff \u0026lt;0f\u0026gt; 0b 48 8b 6c 24 20 89\n34 24 e8 4a 4e 92 fe 8b 34 24 48 c7 c1 20\nRSP: 0018:ffff88810091f820 EFLAGS: 00010282\nRAX: 0000000000000089 RBX: ffff8881086e9000 RCX: 0000000000000000\nRDX: 0000000000000089 RSI: 0000000000000008 RDI: ffffed1020123efb\nRBP: ffff888005f6eac0 R08: ffffed1022fc0031 R09: ffffed1022fc0031\nR10: ffff888117e00187 R11: ffffed1022fc0030 R12: 0000000000000028\nR13: ffff888008284eb0 R14: 0000000000000ed8 R15: 0000000000000ec0\nFS:  0000000000000000(0000) GS:ffff888117c00000(0000)\nknlGS:0000000000000000\nCS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033\nCR2: 00007f8b801c5640 CR3: 0000000033c2c006 CR4: 00000000003706f0\nDR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000\nDR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400\nCall Trace:\n ? ip6_mc_hdr.isra.26.constprop.46+0x12a/0x600\n ? ip6_mc_hdr.isra.26.constprop.46+0x12a/0x600\n skb_put.cold.104+0x22/0x22\n ip6_mc_hdr.isra.26.constprop.46+0x12a/0x600\n ? rcu_read_lock_sched_held+0x91/0xc0\n mld_newpack+0x398/0x8f0\n ? ip6_mc_hdr.isra.26.constprop.46+0x600/0x600\n ? lock_contended+0xc40/0xc40\n add_grhead.isra.33+0x280/0x380\n add_grec+0x5ca/0xff0\n ? mld_sendpack+0xf40/0xf40\n ? lock_downgrade+0x690/0x690\n mld_send_initial_cr.part.34+0xb9/0x180\n ipv6_mc_dad_complete+0x15d/0x1b0\n addrconf_dad_completed+0x8d2/0xbb0\n ? lock_downgrade+0x690/0x690\n ? addrconf_rs_timer+0x660/0x660\n ? addrconf_dad_work+0x73c/0x10e0\n addrconf_dad_work+0x73c/0x10e0\r\n\r\nAllowing high order page allocation could fix this problem.(CVE-2021-47146)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\ni2c: i801: Don\u0026apos;t generate an interrupt on bus reset\r\n\r\nNow that the i2c-i801 driver supports interrupts, setting the KILL bit\nin a attempt to recover from a timed out transaction triggers an\ninterrupt. Unfortunately, the interrupt handler (i801_isr) is not\nprepared for this situation and will try to process the interrupt as\nif it was signaling the end of a successful transaction. In the case\nof a block transaction, this can result in an out-of-range memory\naccess.\r\n\r\nThis condition was reproduced several times by syzbot:\nhttps://syzkaller.appspot.com/bug?extid=ed71512d469895b5b34e\nhttps://syzkaller.appspot.com/bug?extid=8c8dedc0ba9e03f6c79e\nhttps://syzkaller.appspot.com/bug?extid=c8ff0b6d6c73d81b610e\nhttps://syzkaller.appspot.com/bug?extid=33f6c360821c399d69eb\nhttps://syzkaller.appspot.com/bug?extid=be15dc0b1933f04b043a\nhttps://syzkaller.appspot.com/bug?extid=b4d3fd1dfd53e90afd79\r\n\r\nSo disable interrupts while trying to reset the bus. Interrupts will\nbe enabled again for the following transaction.(CVE-2021-47153)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nnet: dsa: fix a crash if -\u0026gt;get_sset_count() fails\r\n\r\nIf ds-\u0026gt;ops-\u0026gt;get_sset_count() fails then it \u0026quot;count\u0026quot; is a negative error\ncode such as -EOPNOTSUPP.  Because \u0026quot;i\u0026quot; is an unsigned int, the negative\nerror code is type promoted to a very high value and the loop will\ncorrupt memory until the system crashes.\r\n\r\nFix this by checking for error codes and changing the type of \u0026quot;i\u0026quot; to\njust int.(CVE-2021-47159)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nnet: dsa: mt7530: fix VLAN traffic leaks\r\n\r\nPCR_MATRIX field was set to all 1\u0026apos;s when VLAN filtering is enabled, but\nwas not reset when it is disabled, which may cause traffic leaks:\r\n\r\n\tip link add br0 type bridge vlan_filtering 1\n\tip link add br1 type bridge vlan_filtering 1\n\tip link set swp0 master br0\n\tip link set swp1 master br1\n\tip link set br0 type bridge vlan_filtering 0\n\tip link set br1 type bridge vlan_filtering 0\n\t# traffic in br0 and br1 will start leaking to each other\r\n\r\nAs port_bridge_{add,del} have set up PCR_MATRIX properly, remove the\nPCR_MATRIX write from mt7530_port_set_vlan_aware.(CVE-2021-47160)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nspi: spi-fsl-dspi: Fix a resource leak in an error handling path\r\n\r\n\u0026apos;dspi_request_dma()\u0026apos; should be undone by a \u0026apos;dspi_release_dma()\u0026apos; call in the\nerror handling path of the probe function, as already done in the remove\nfunction(CVE-2021-47161)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\ntipc: skb_linearize the head skb when reassembling msgs\r\n\r\nIt\u0026apos;s not a good idea to append the frag skb to a skb\u0026apos;s frag_list if\nthe frag_list already has skbs from elsewhere, such as this skb was\ncreated by pskb_copy() where the frag_list was cloned (all the skbs\nin it were skb_get\u0026apos;ed) and shared by multiple skbs.\r\n\r\nHowever, the new appended frag skb should have been only seen by the\ncurrent skb. Otherwise, it will cause use after free crashes as this\nappended frag skb are seen by multiple skbs but it only got skb_get\ncalled once.\r\n\r\nThe same thing happens with a skb updated by pskb_may_pull() with a\nskb_cloned skb. Li Shuang has reported quite a few crashes caused\nby this when doing testing over macvlan devices:\r\n\r\n  [] kernel BUG at net/core/skbuff.c:1970!\n  [] Call Trace:\n  []  skb_clone+0x4d/0xb0\n  []  macvlan_broadcast+0xd8/0x160 [macvlan]\n  []  macvlan_process_broadcast+0x148/0x150 [macvlan]\n  []  process_one_work+0x1a7/0x360\n  []  worker_thread+0x30/0x390\r\n\r\n  [] kernel BUG at mm/usercopy.c:102!\n  [] Call Trace:\n  []  __check_heap_object+0xd3/0x100\n  []  __check_object_size+0xff/0x16b\n  []  simple_copy_to_iter+0x1c/0x30\n  []  __skb_datagram_iter+0x7d/0x310\n  []  __skb_datagram_iter+0x2a5/0x310\n  []  skb_copy_datagram_iter+0x3b/0x90\n  []  tipc_recvmsg+0x14a/0x3a0 [tipc]\n  []  ____sys_recvmsg+0x91/0x150\n  []  ___sys_recvmsg+0x7b/0xc0\r\n\r\n  [] kernel BUG at mm/slub.c:305!\n  [] Call Trace:\n  []  \u0026lt;IRQ\u0026gt;\n  []  kmem_cache_free+0x3ff/0x400\n  []  __netif_receive_skb_core+0x12c/0xc40\n  []  ? kmem_cache_alloc+0x12e/0x270\n  []  netif_receive_skb_internal+0x3d/0xb0\n  []  ? get_rx_page_info+0x8e/0xa0 [be2net]\n  []  be_poll+0x6ef/0xd00 [be2net]\n  []  ? irq_exit+0x4f/0x100\n  []  net_rx_action+0x149/0x3b0\r\n\r\n  ...\r\n\r\nThis patch is to fix it by linearizing the head skb if it has frag_list\nset in tipc_buf_append(). Note that we choose to do this before calling\nskb_unshare(), as __skb_linearize() will avoid skb_copy(). Also, we can\nnot just drop the frag_list either as the early time.(CVE-2021-47162)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\ntipc: wait and exit until all work queues are done\r\n\r\nOn some host, a crash could be triggered simply by repeating these\ncommands several times:\r\n\r\n  # modprobe tipc\n  # tipc bearer enable media udp name UDP1 localip 127.0.0.1\n  # rmmod tipc\r\n\r\n  [] BUG: unable to handle kernel paging request at ffffffffc096bb00\n  [] Workqueue: events 0xffffffffc096bb00\n  [] Call Trace:\n  []  ? process_one_work+0x1a7/0x360\n  []  ? worker_thread+0x30/0x390\n  []  ? create_worker+0x1a0/0x1a0\n  []  ? kthread+0x116/0x130\n  []  ? kthread_flush_work_fn+0x10/0x10\n  []  ? ret_from_fork+0x35/0x40\r\n\r\nWhen removing the TIPC module, the UDP tunnel sock will be delayed to\nrelease in a work queue as sock_release() can\u0026apos;t be done in rtnl_lock().\nIf the work queue is schedule to run after the TIPC module is removed,\nkernel will crash as the work queue function cleanup_beareri() code no\nlonger exists when trying to invoke it.\r\n\r\nTo fix it, this patch introduce a member wq_count in tipc_net to track\nthe numbers of work queues in schedule, and  wait and exit until all\nwork queues are done in tipc_exit_net().(CVE-2021-47163)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nNFS: Fix an Oopsable condition in __nfs_pageio_add_request()\r\n\r\nEnsure that nfs_pageio_error_cleanup() resets the mirror array contents,\nso that the structure reflects the fact that it is now empty.\nAlso change the test in nfs_pageio_do_add_request() to be more robust by\nchecking whether or not the list is empty rather than relying on the\nvalue of pg_count.(CVE-2021-47167)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nUSB: usbfs: Don\u0026apos;t WARN about excessively large memory allocations\r\n\r\nSyzbot found that the kernel generates a WARNing if the user tries to\nsubmit a bulk transfer through usbfs with a buffer that is way too\nlarge.  This isn\u0026apos;t a bug in the kernel; it\u0026apos;s merely an invalid request\nfrom the user and the usbfs code does handle it correctly.\r\n\r\nIn theory the same thing can happen with async transfers, or with the\npacket descriptor table for isochronous transfers.\r\n\r\nTo prevent the MM subsystem from complaining about these bad\nallocation requests, add the __GFP_NOWARN flag to the kmalloc calls\nfor these buffers.(CVE-2021-47170)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nnet: usb: fix memory leak in smsc75xx_bind\r\n\r\nSyzbot reported memory leak in smsc75xx_bind().\nThe problem was is non-freed memory in case of\nerrors after memory allocation.\r\n\r\nbacktrace:\n  [\u0026lt;ffffffff84245b62\u0026gt;] kmalloc include/linux/slab.h:556 [inline]\n  [\u0026lt;ffffffff84245b62\u0026gt;] kzalloc include/linux/slab.h:686 [inline]\n  [\u0026lt;ffffffff84245b62\u0026gt;] smsc75xx_bind+0x7a/0x334 drivers/net/usb/smsc75xx.c:1460\n  [\u0026lt;ffffffff82b5b2e6\u0026gt;] usbnet_probe+0x3b6/0xc30 drivers/net/usb/usbnet.c:1728(CVE-2021-47171)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nmisc/uss720: fix memory leak in uss720_probe\r\n\r\nuss720_probe forgets to decrease the refcount of usbdev in uss720_probe.\nFix this by decreasing the refcount of usbdev by usb_put_dev.\r\n\r\nBUG: memory leak\nunreferenced object 0xffff888101113800 (size 2048):\n  comm \u0026quot;kworker/0:1\u0026quot;, pid 7, jiffies 4294956777 (age 28.870s)\n  hex dump (first 32 bytes):\n    ff ff ff ff 31 00 00 00 00 00 00 00 00 00 00 00  ....1...........\n    00 00 00 00 00 00 00 00 00 00 00 00 03 00 00 00  ................\n  backtrace:\n    [\u0026lt;ffffffff82b8e822\u0026gt;] kmalloc include/linux/slab.h:554 [inline]\n    [\u0026lt;ffffffff82b8e822\u0026gt;] kzalloc include/linux/slab.h:684 [inline]\n    [\u0026lt;ffffffff82b8e822\u0026gt;] usb_alloc_dev+0x32/0x450 drivers/usb/core/usb.c:582\n    [\u0026lt;ffffffff82b98441\u0026gt;] hub_port_connect drivers/usb/core/hub.c:5129 [inline]\n    [\u0026lt;ffffffff82b98441\u0026gt;] hub_port_connect_change drivers/usb/core/hub.c:5363 [inline]\n    [\u0026lt;ffffffff82b98441\u0026gt;] port_event drivers/usb/core/hub.c:5509 [inline]\n    [\u0026lt;ffffffff82b98441\u0026gt;] hub_event+0x1171/0x20c0 drivers/usb/core/hub.c:5591\n    [\u0026lt;ffffffff81259229\u0026gt;] process_one_work+0x2c9/0x600 kernel/workqueue.c:2275\n    [\u0026lt;ffffffff81259b19\u0026gt;] worker_thread+0x59/0x5d0 kernel/workqueue.c:2421\n    [\u0026lt;ffffffff81261228\u0026gt;] kthread+0x178/0x1b0 kernel/kthread.c:292\n    [\u0026lt;ffffffff8100227f\u0026gt;] ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:294(CVE-2021-47173)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nNFC: nci: fix memory leak in nci_allocate_device\r\n\r\nnfcmrvl_disconnect fails to free the hci_dev field in struct nci_dev.\nFix this by freeing hci_dev in nci_free_device.\r\n\r\nBUG: memory leak\nunreferenced object 0xffff888111ea6800 (size 1024):\n  comm \u0026quot;kworker/1:0\u0026quot;, pid 19, jiffies 4294942308 (age 13.580s)\n  hex dump (first 32 bytes):\n    00 00 00 00 00 00 00 00 00 60 fd 0c 81 88 ff ff  .........`......\n    00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................\n  backtrace:\n    [\u0026lt;000000004bc25d43\u0026gt;] kmalloc include/linux/slab.h:552 [inline]\n    [\u0026lt;000000004bc25d43\u0026gt;] kzalloc include/linux/slab.h:682 [inline]\n    [\u0026lt;000000004bc25d43\u0026gt;] nci_hci_allocate+0x21/0xd0 net/nfc/nci/hci.c:784\n    [\u0026lt;00000000c59cff92\u0026gt;] nci_allocate_device net/nfc/nci/core.c:1170 [inline]\n    [\u0026lt;00000000c59cff92\u0026gt;] nci_allocate_device+0x10b/0x160 net/nfc/nci/core.c:1132\n    [\u0026lt;00000000006e0a8e\u0026gt;] nfcmrvl_nci_register_dev+0x10a/0x1c0 drivers/nfc/nfcmrvl/main.c:153\n    [\u0026lt;000000004da1b57e\u0026gt;] nfcmrvl_probe+0x223/0x290 drivers/nfc/nfcmrvl/usb.c:345\n    [\u0026lt;00000000d506aed9\u0026gt;] usb_probe_interface+0x177/0x370 drivers/usb/core/driver.c:396\n    [\u0026lt;00000000bc632c92\u0026gt;] really_probe+0x159/0x4a0 drivers/base/dd.c:554\n    [\u0026lt;00000000f5009125\u0026gt;] driver_probe_device+0x84/0x100 drivers/base/dd.c:740\n    [\u0026lt;000000000ce658ca\u0026gt;] __device_attach_driver+0xee/0x110 drivers/base/dd.c:846\n    [\u0026lt;000000007067d05f\u0026gt;] bus_for_each_drv+0xb7/0x100 drivers/base/bus.c:431\n    [\u0026lt;00000000f8e13372\u0026gt;] __device_attach+0x122/0x250 drivers/base/dd.c:914\n    [\u0026lt;000000009cf68860\u0026gt;] bus_probe_device+0xc6/0xe0 drivers/base/bus.c:491\n    [\u0026lt;00000000359c965a\u0026gt;] device_add+0x5be/0xc30 drivers/base/core.c:3109\n    [\u0026lt;00000000086e4bd3\u0026gt;] usb_set_configuration+0x9d9/0xb90 drivers/usb/core/message.c:2164\n    [\u0026lt;00000000ca036872\u0026gt;] usb_generic_driver_probe+0x8c/0xc0 drivers/usb/core/generic.c:238\n    [\u0026lt;00000000d40d36f6\u0026gt;] usb_probe_device+0x5c/0x140 drivers/usb/core/driver.c:293\n    [\u0026lt;00000000bc632c92\u0026gt;] really_probe+0x159/0x4a0 drivers/base/dd.c:554(CVE-2021-47180)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nEDAC/thunderx: Fix possible out-of-bounds string access\r\n\r\nEnabling -Wstringop-overflow globally exposes a warning for a common bug\nin the usage of strncat():\r\n\r\n  drivers/edac/thunderx_edac.c: In function \u0026apos;thunderx_ocx_com_threaded_isr\u0026apos;:\n  drivers/edac/thunderx_edac.c:1136:17: error: \u0026apos;strncat\u0026apos; specified bound 1024 equals destination size [-Werror=stringop-overflow=]\n   1136 |                 strncat(msg, other, OCX_MESSAGE_SIZE);\n        |                 ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~\n   ...\n   1145 |                                 strncat(msg, other, OCX_MESSAGE_SIZE);\n   ...\n   1150 |                                 strncat(msg, other, OCX_MESSAGE_SIZE);\r\n\r\n   ...\r\n\r\nApparently the author of this driver expected strncat() to behave the\nway that strlcat() does, which uses the size of the destination buffer\nas its third argument rather than the length of the source buffer. The\nresult is that there is no check on the size of the allocated buffer.\r\n\r\nChange it to strlcat().\r\n\r\n  [ bp: Trim compiler output, fixup commit message. ](CVE-2023-52464)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nInput: powermate - fix use-after-free in powermate_config_complete\r\n\r\nsyzbot has found a use-after-free bug [1] in the powermate driver. This\nhappens when the device is disconnected, which leads to a memory free from\nthe powermate_device struct.  When an asynchronous control message\ncompletes after the kfree and its callback is invoked, the lock does not\nexist anymore and hence the bug.\r\n\r\nUse usb_kill_urb() on pm-\u0026gt;config to cancel any in-progress requests upon\ndevice disconnection.\r\n\r\n[1] https://syzkaller.appspot.com/bug?extid=0434ac83f907a1dbdd1e(CVE-2023-52475)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nscsi: pm80xx: Avoid leaking tags when processing OPC_INB_SET_CONTROLLER_CONFIG command\r\n\r\nTags allocated for OPC_INB_SET_CONTROLLER_CONFIG command need to be freed\nwhen we receive the response.(CVE-2023-52500)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nnfc: nci: assert requested protocol is valid\r\n\r\nThe protocol is used in a bit mask to determine if the protocol is\nsupported. Assert the provided protocol is less than the maximum\ndefined so it doesn\u0026apos;t potentially perform a shift-out-of-bounds and\nprovide a clearer error for undefined protocols vs unsupported ones.(CVE-2023-52507)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nieee802154: ca8210: Fix a potential UAF in ca8210_probe\r\n\r\nIf of_clk_add_provider() fails in ca8210_register_ext_clock(),\nit calls clk_unregister() to release priv-\u0026gt;clk and returns an\nerror. However, the caller ca8210_probe() then calls ca8210_remove(),\nwhere priv-\u0026gt;clk is freed again in ca8210_unregister_ext_clock(). In\nthis case, a use-after-free may happen in the second time we call\nclk_unregister().\r\n\r\nFix this by removing the first clk_unregister(). Also, priv-\u0026gt;clk could\nbe an error code on failure of clk_register_fixed_rate(). Use\nIS_ERR_OR_NULL to catch this case in ca8210_unregister_ext_clock().(CVE-2023-52510)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nRDMA/srp: Do not call scsi_done() from srp_abort()\r\n\r\nAfter scmd_eh_abort_handler() has called the SCSI LLD eh_abort_handler\ncallback, it performs one of the following actions:\n* Call scsi_queue_insert().\n* Call scsi_finish_command().\n* Call scsi_eh_scmd_add().\nHence, SCSI abort handlers must not call scsi_done(). Otherwise all\nthe above actions would trigger a use-after-free. Hence remove the\nscsi_done() call from srp_abort(). Keep the srp_free_req() call\nbefore returning SUCCESS because we may not see the command again if\nSUCCESS is returned.(CVE-2023-52515)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nnet: fix possible store tearing in neigh_periodic_work()\r\n\r\nWhile looking at a related syzbot report involving neigh_periodic_work(),\nI found that I forgot to add an annotation when deleting an\nRCU protected item from a list.\r\n\r\nReaders use rcu_deference(*np), we need to use either\nrcu_assign_pointer() or WRITE_ONCE() on writer side\nto prevent store tearing.\r\n\r\nI use rcu_assign_pointer() to have lockdep support,\nthis was the choice made in neigh_flush_dev().(CVE-2023-52522)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nwifi: mac80211: fix potential key use-after-free\r\n\r\nWhen ieee80211_key_link() is called by ieee80211_gtk_rekey_add()\nbut returns 0 due to KRACK protection (identical key reinstall),\nieee80211_gtk_rekey_add() will still return a pointer into the\nkey, in a potential use-after-free. This normally doesn\u0026apos;t happen\nsince it\u0026apos;s only called by iwlwifi in case of WoWLAN rekey offload\nwhich has its own KRACK protection, but still better to fix, do\nthat by returning an error code and converting that to success on\nthe cfg80211 boundary only, leaving the error for bad callers of\nieee80211_gtk_rekey_add().(CVE-2023-52530)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nnilfs2: fix potential use after free in nilfs_gccache_submit_read_data()\r\n\r\nIn nilfs_gccache_submit_read_data(), brelse(bh) is called to drop the\nreference count of bh when the call to nilfs_dat_translate() fails.  If\nthe reference count hits 0 and its owner page gets unlocked, bh may be\nfreed.  However, bh-\u0026gt;b_page is dereferenced to put the page after that,\nwhich may result in a use-after-free bug.  This patch moves the release\noperation after unlocking and putting the page.\r\n\r\nNOTE: The function in question is only called in GC, and in combination\nwith current userland tools, address translation using DAT does not occur\nin that function, so the code path that causes this issue will not be\nexecuted.  However, it is possible to run that code path by intentionally\nmodifying the userland GC library or by calling the GC ioctl directly.\r\n\r\n[konishi.ryusuke@gmail.com: NOTE added to the commit log](CVE-2023-52566)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nnet: bridge: use DEV_STATS_INC()\r\n\r\nsyzbot/KCSAN reported data-races in br_handle_frame_finish() [1]\nThis function can run from multiple cpus without mutual exclusion.\r\n\r\nAdopt SMP safe DEV_STATS_INC() to update dev-\u0026gt;stats fields.\r\n\r\nHandles updates to dev-\u0026gt;stats.tx_dropped while we are at it.\r\n\r\n[1]\nBUG: KCSAN: data-race in br_handle_frame_finish / br_handle_frame_finish\r\n\r\nread-write to 0xffff8881374b2178 of 8 bytes by interrupt on cpu 1:\nbr_handle_frame_finish+0xd4f/0xef0 net/bridge/br_input.c:189\nbr_nf_hook_thresh+0x1ed/0x220\nbr_nf_pre_routing_finish_ipv6+0x50f/0x540\nNF_HOOK include/linux/netfilter.h:304 [inline]\nbr_nf_pre_routing_ipv6+0x1e3/0x2a0 net/bridge/br_netfilter_ipv6.c:178\nbr_nf_pre_routing+0x526/0xba0 net/bridge/br_netfilter_hooks.c:508\nnf_hook_entry_hookfn include/linux/netfilter.h:144 [inline]\nnf_hook_bridge_pre net/bridge/br_input.c:272 [inline]\nbr_handle_frame+0x4c9/0x940 net/bridge/br_input.c:417\n__netif_receive_skb_core+0xa8a/0x21e0 net/core/dev.c:5417\n__netif_receive_skb_one_core net/core/dev.c:5521 [inline]\n__netif_receive_skb+0x57/0x1b0 net/core/dev.c:5637\nprocess_backlog+0x21f/0x380 net/core/dev.c:5965\n__napi_poll+0x60/0x3b0 net/core/dev.c:6527\nnapi_poll net/core/dev.c:6594 [inline]\nnet_rx_action+0x32b/0x750 net/core/dev.c:6727\n__do_softirq+0xc1/0x265 kernel/softirq.c:553\nrun_ksoftirqd+0x17/0x20 kernel/softirq.c:921\nsmpboot_thread_fn+0x30a/0x4a0 kernel/smpboot.c:164\nkthread+0x1d7/0x210 kernel/kthread.c:388\nret_from_fork+0x48/0x60 arch/x86/kernel/process.c:147\nret_from_fork_asm+0x11/0x20 arch/x86/entry/entry_64.S:304\r\n\r\nread-write to 0xffff8881374b2178 of 8 bytes by interrupt on cpu 0:\nbr_handle_frame_finish+0xd4f/0xef0 net/bridge/br_input.c:189\nbr_nf_hook_thresh+0x1ed/0x220\nbr_nf_pre_routing_finish_ipv6+0x50f/0x540\nNF_HOOK include/linux/netfilter.h:304 [inline]\nbr_nf_pre_routing_ipv6+0x1e3/0x2a0 net/bridge/br_netfilter_ipv6.c:178\nbr_nf_pre_routing+0x526/0xba0 net/bridge/br_netfilter_hooks.c:508\nnf_hook_entry_hookfn include/linux/netfilter.h:144 [inline]\nnf_hook_bridge_pre net/bridge/br_input.c:272 [inline]\nbr_handle_frame+0x4c9/0x940 net/bridge/br_input.c:417\n__netif_receive_skb_core+0xa8a/0x21e0 net/core/dev.c:5417\n__netif_receive_skb_one_core net/core/dev.c:5521 [inline]\n__netif_receive_skb+0x57/0x1b0 net/core/dev.c:5637\nprocess_backlog+0x21f/0x380 net/core/dev.c:5965\n__napi_poll+0x60/0x3b0 net/core/dev.c:6527\nnapi_poll net/core/dev.c:6594 [inline]\nnet_rx_action+0x32b/0x750 net/core/dev.c:6727\n__do_softirq+0xc1/0x265 kernel/softirq.c:553\ndo_softirq+0x5e/0x90 kernel/softirq.c:454\n__local_bh_enable_ip+0x64/0x70 kernel/softirq.c:381\n__raw_spin_unlock_bh include/linux/spinlock_api_smp.h:167 [inline]\n_raw_spin_unlock_bh+0x36/0x40 kernel/locking/spinlock.c:210\nspin_unlock_bh include/linux/spinlock.h:396 [inline]\nbatadv_tt_local_purge+0x1a8/0x1f0 net/batman-adv/translation-table.c:1356\nbatadv_tt_purge+0x2b/0x630 net/batman-adv/translation-table.c:3560\nprocess_one_work kernel/workqueue.c:2630 [inline]\nprocess_scheduled_works+0x5b8/0xa30 kernel/workqueue.c:2703\nworker_thread+0x525/0x730 kernel/workqueue.c:2784\nkthread+0x1d7/0x210 kernel/kthread.c:388\nret_from_fork+0x48/0x60 arch/x86/kernel/process.c:147\nret_from_fork_asm+0x11/0x20 arch/x86/entry/entry_64.S:304\r\n\r\nvalue changed: 0x00000000000d7190 -\u0026gt; 0x00000000000d7191\r\n\r\nReported by Kernel Concurrency Sanitizer on:\nCPU: 0 PID: 14848 Comm: kworker/u4:11 Not tainted 6.6.0-rc1-syzkaller-00236-gad8a69f361b9 #0(CVE-2023-52578)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nceph: fix deadlock or deadcode of misusing dget()\r\n\r\nThe lock order is incorrect between denty and its parent, we should\nalways make sure that the parent get the lock first.\r\n\r\nBut since this deadcode is never used and the parent dir will always\nbe set from the callers, let\u0026apos;s just remove it.(CVE-2023-52583)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nIB/ipoib: Fix mcast list locking\r\n\r\nReleasing the `priv-\u0026gt;lock` while iterating the `priv-\u0026gt;multicast_list` in\n`ipoib_mcast_join_task()` opens a window for `ipoib_mcast_dev_flush()` to\nremove the items while in the middle of iteration. If the mcast is removed\nwhile the lock was dropped, the for loop spins forever resulting in a hard\nlockup (as was reported on RHEL 4.18.0-372.75.1.el8_6 kernel):\r\n\r\n    Task A (kworker/u72:2 below)       | Task B (kworker/u72:0 below)\n    -----------------------------------+-----------------------------------\n    ipoib_mcast_join_task(work)        | ipoib_ib_dev_flush_light(work)\n      spin_lock_irq(\u0026amp;priv-\u0026gt;lock)       | __ipoib_ib_dev_flush(priv, ...)\n      list_for_each_entry(mcast,       | ipoib_mcast_dev_flush(dev = priv-\u0026gt;dev)\n          \u0026amp;priv-\u0026gt;multicast_list, list) |\n        ipoib_mcast_join(dev, mcast)   |\n          spin_unlock_irq(\u0026amp;priv-\u0026gt;lock) |\n                                       |   spin_lock_irqsave(\u0026amp;priv-\u0026gt;lock, flags)\n                                       |   list_for_each_entry_safe(mcast, tmcast,\n                                       |                  \u0026amp;priv-\u0026gt;multicast_list, list)\n                                       |     list_del(\u0026amp;mcast-\u0026gt;list);\n                                       |     list_add_tail(\u0026amp;mcast-\u0026gt;list, \u0026amp;remove_list)\n                                       |   spin_unlock_irqrestore(\u0026amp;priv-\u0026gt;lock, flags)\n          spin_lock_irq(\u0026amp;priv-\u0026gt;lock)   |\n                                       |   ipoib_mcast_remove_list(\u0026amp;remove_list)\n   (Here, `mcast` is no longer on the  |     list_for_each_entry_safe(mcast, tmcast,\n    `priv-\u0026gt;multicast_list` and we keep |                            remove_list, list)\n    spinning on the `remove_list` of   |  \u0026gt;\u0026gt;\u0026gt;  wait_for_completion(\u0026amp;mcast-\u0026gt;done)\n    the other thread which is blocked  |\n    and the list is still valid on     |\n    it\u0026apos;s stack.)\r\n\r\nFix this by keeping the lock held and changing to GFP_ATOMIC to prevent\neventual sleeps.\nUnfortunately we could not reproduce the lockup and confirm this fix but\nbased on the code review I think this fix should address such lockups.\r\n\r\ncrash\u0026gt; bc 31\nPID: 747      TASK: ff1c6a1a007e8000  CPU: 31   COMMAND: \u0026quot;kworker/u72:2\u0026quot;\n--\n    [exception RIP: ipoib_mcast_join_task+0x1b1]\n    RIP: ffffffffc0944ac1  RSP: ff646f199a8c7e00  RFLAGS: 00000002\n    RAX: 0000000000000000  RBX: ff1c6a1a04dc82f8  RCX: 0000000000000000\n                                  work (\u0026amp;priv-\u0026gt;mcast_task{,.work})\n    RDX: ff1c6a192d60ac68  RSI: 0000000000000286  RDI: ff1c6a1a04dc8000\n           \u0026amp;mcast-\u0026gt;list\n    RBP: ff646f199a8c7e90   R8: ff1c699980019420   R9: ff1c6a1920c9a000\n    R10: ff646f199a8c7e00  R11: ff1c6a191a7d9800  R12: ff1c6a192d60ac00\n                                                         mcast\n    R13: ff1c6a1d82200000  R14: ff1c6a1a04dc8000  R15: ff1c6a1a04dc82d8\n           dev                    priv (\u0026amp;priv-\u0026gt;lock)     \u0026amp;priv-\u0026gt;multicast_list (aka head)\n    ORIG_RAX: ffffffffffffffff  CS: 0010  SS: 0018\n--- \u0026lt;NMI exception stack\u0026gt; ---\n #5 [ff646f199a8c7e00] ipoib_mcast_join_task+0x1b1 at ffffffffc0944ac1 [ib_ipoib]\n #6 [ff646f199a8c7e98] process_one_work+0x1a7 at ffffffff9bf10967\r\n\r\ncrash\u0026gt; rx ff646f199a8c7e68\nff646f199a8c7e68:  ff1c6a1a04dc82f8 \u0026lt;\u0026lt;\u0026lt; work = \u0026amp;priv-\u0026gt;mcast_task.work\r\n\r\ncrash\u0026gt; list -hO ipoib_dev_priv.multicast_list ff1c6a1a04dc8000\n(empty)\r\n\r\ncrash\u0026gt; ipoib_dev_priv.mcast_task.work.func,mcast_mutex.owner.counter ff1c6a1a04dc8000\n  mcast_task.work.func = 0xffffffffc0944910 \u0026lt;ipoib_mcast_join_task\u0026gt;,\n  mcast_mutex.owner.counter = 0xff1c69998efec000\r\n\r\ncrash\u0026gt; b 8\nPID: 8        TASK: ff1c69998efec000  CPU: 33   COMMAND: \u0026quot;kworker/u72:0\u0026quot;\n--\n #3 [ff646f1980153d50] wait_for_completion+0x96 at ffffffff9c7d7646\n #4 [ff646f1980153d90] ipoib_mcast_remove_list+0x56 at ffffffffc0944dc6 [ib_ipoib]\n #5 [ff646f1980153de8] ipoib_mcast_dev_flush+0x1a7 at ffffffffc09455a7 [ib_ipoib]\n #6 [ff646f1980153e58] __ipoib_ib_dev_flush+0x1a4 at ffffffffc09431a4 [ib_ipoib]\n #7 [ff\n---truncated---(CVE-2023-52587)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nwifi: ath9k: Fix potential array-index-out-of-bounds read in ath9k_htc_txstatus()\r\n\r\nFix an array-index-out-of-bounds read in ath9k_htc_txstatus(). The bug\noccurs when txs-\u0026gt;cnt, data from a URB provided by a USB device, is\nbigger than the size of the array txs-\u0026gt;txstatus, which is\nHTC_MAX_TX_STATUS. WARN_ON() already checks it, but there is no bug\nhandling code after the check. Make the function return if that is the\ncase.\r\n\r\nFound by a modified version of syzkaller.\r\n\r\nUBSAN: array-index-out-of-bounds in htc_drv_txrx.c\nindex 13 is out of range for type \u0026apos;__wmi_event_txstatus [12]\u0026apos;\nCall Trace:\n ath9k_htc_txstatus\n ath9k_wmi_event_tasklet\n tasklet_action_common\n __do_softirq\n irq_exit_rxu\n sysvec_apic_timer_interrupt(CVE-2023-52594)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nwifi: rt2x00: restart beacon queue when hardware reset\r\n\r\nWhen a hardware reset is triggered, all registers are reset, so all\nqueues are forced to stop in hardware interface. However, mac80211\nwill not automatically stop the queue. If we don\u0026apos;t manually stop the\nbeacon queue, the queue will be deadlocked and unable to start again.\nThis patch fixes the issue where Apple devices cannot connect to the\nAP after calling ieee80211_restart_hw().(CVE-2023-52595)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nKVM: s390: fix setting of fpc register\r\n\r\nkvm_arch_vcpu_ioctl_set_fpu() allows to set the floating point control\n(fpc) register of a guest cpu. The new value is tested for validity by\ntemporarily loading it into the fpc register.\r\n\r\nThis may lead to corruption of the fpc register of the host process:\nif an interrupt happens while the value is temporarily loaded into the fpc\nregister, and within interrupt context floating point or vector registers\nare used, the current fp/vx registers are saved with save_fpu_regs()\nassuming they belong to user space and will be loaded into fp/vx registers\nwhen returning to user space.\r\n\r\ntest_fp_ctl() restores the original user space / host process fpc register\nvalue, however it will be discarded, when returning to user space.\r\n\r\nIn result the host process will incorrectly continue to run with the value\nthat was supposed to be used for a guest cpu.\r\n\r\nFix this by simply removing the test. There is another test right before\nthe SIE context is entered which will handles invalid values.\r\n\r\nThis results in a change of behaviour: invalid values will now be accepted\ninstead of that the ioctl fails with -EINVAL. This seems to be acceptable,\ngiven that this interface is most likely not used anymore, and this is in\naddition the same behaviour implemented with the memory mapped interface\n(replace invalid values with zero) - see sync_regs() in kvm-s390.c.(CVE-2023-52597)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\ns390/ptrace: handle setting of fpc register correctly\r\n\r\nIf the content of the floating point control (fpc) register of a traced\nprocess is modified with the ptrace interface the new value is tested for\nvalidity by temporarily loading it into the fpc register.\r\n\r\nThis may lead to corruption of the fpc register of the tracing process:\nif an interrupt happens while the value is temporarily loaded into the\nfpc register, and within interrupt context floating point or vector\nregisters are used, the current fp/vx registers are saved with\nsave_fpu_regs() assuming they belong to user space and will be loaded into\nfp/vx registers when returning to user space.\r\n\r\ntest_fp_ctl() restores the original user space fpc register value, however\nit will be discarded, when returning to user space.\r\n\r\nIn result the tracer will incorrectly continue to run with the value that\nwas supposed to be used for the traced process.\r\n\r\nFix this by saving fpu register contents with save_fpu_regs() before using\ntest_fp_ctl().(CVE-2023-52598)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\next4: avoid online resizing failures due to oversized flex bg\r\n\r\nWhen we online resize an ext4 filesystem with a oversized flexbg_size,\r\n\r\n     mkfs.ext4 -F -G 67108864 $dev -b 4096 100M\n     mount $dev $dir\n     resize2fs $dev 16G\r\n\r\nthe following WARN_ON is triggered:\n==================================================================\nWARNING: CPU: 0 PID: 427 at mm/page_alloc.c:4402 __alloc_pages+0x411/0x550\nModules linked in: sg(E)\nCPU: 0 PID: 427 Comm: resize2fs Tainted: G  E  6.6.0-rc5+ #314\nRIP: 0010:__alloc_pages+0x411/0x550\nCall Trace:\n \u0026lt;TASK\u0026gt;\n __kmalloc_large_node+0xa2/0x200\n __kmalloc+0x16e/0x290\n ext4_resize_fs+0x481/0xd80\n __ext4_ioctl+0x1616/0x1d90\n ext4_ioctl+0x12/0x20\n __x64_sys_ioctl+0xf0/0x150\n do_syscall_64+0x3b/0x90\n==================================================================\r\n\r\nThis is because flexbg_size is too large and the size of the new_group_data\narray to be allocated exceeds MAX_ORDER. Currently, the minimum value of\nMAX_ORDER is 8, the minimum value of PAGE_SIZE is 4096, the corresponding\nmaximum number of groups that can be allocated is:\r\n\r\n (PAGE_SIZE \u0026lt;\u0026lt; MAX_ORDER) / sizeof(struct ext4_new_group_data) ≈ 21845\r\n\r\nAnd the value that is down-aligned to the power of 2 is 16384. Therefore,\nthis value is defined as MAX_RESIZE_BG, and the number of groups added\neach time does not exceed this value during resizing, and is added multiple\ntimes to complete the online resizing. The difference is that the metadata\nin a flex_bg may be more dispersed.(CVE-2023-52622)","status":"published","published":"2024-04-19T11:06:55Z","modified":"2026-08-18T01:17:17.136339012Z","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:41.095407Z"},{"id":"OESA-2024-1484","title":"kernel security update","description":"The Linux Kernel, the operating system core itself.\r\n\r\nSecurity Fix(es):\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\ni2c: img-scb: fix reference leak when pm_runtime_get_sync fails\r\n\r\nThe PM reference count is not expected to be incremented on\nreturn in functions img_i2c_xfer and img_i2c_init.\r\n\r\nHowever, pm_runtime_get_sync will increment the PM reference\ncount even failed. Forgetting to putting operation will result\nin a reference leak here.\r\n\r\nReplace it with pm_runtime_resume_and_get to keep usage\ncounter balanced.(CVE-2020-36783)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nkyber: fix out of bounds access when preempted\r\n\r\n__blk_mq_sched_bio_merge() gets the ctx and hctx for the current CPU and\npasses the hctx to -\u0026gt;bio_merge(). kyber_bio_merge() then gets the ctx\nfor the current CPU again and uses that to get the corresponding Kyber\ncontext in the passed hctx. However, the thread may be preempted between\nthe two calls to blk_mq_get_ctx(), and the ctx returned the second time\nmay no longer correspond to the passed hctx. This \u0026quot;works\u0026quot; accidentally\nmost of the time, but it can cause us to read garbage if the second ctx\ncame from an hctx with more ctx\u0026apos;s than the first one (i.e., if\nctx-\u0026gt;index_hw[hctx-\u0026gt;type] \u0026gt; hctx-\u0026gt;nr_ctx).\r\n\r\nThis manifested as this UBSAN array index out of bounds error reported\nby Jakub:\r\n\r\nUBSAN: array-index-out-of-bounds in ../kernel/locking/qspinlock.c:130:9\nindex 13106 is out of range for type \u0026apos;long unsigned int [128]\u0026apos;\nCall Trace:\n dump_stack+0xa4/0xe5\n ubsan_epilogue+0x5/0x40\n __ubsan_handle_out_of_bounds.cold.13+0x2a/0x34\n queued_spin_lock_slowpath+0x476/0x480\n do_raw_spin_lock+0x1c2/0x1d0\n kyber_bio_merge+0x112/0x180\n blk_mq_submit_bio+0x1f5/0x1100\n submit_bio_noacct+0x7b0/0x870\n submit_bio+0xc2/0x3a0\n btrfs_map_bio+0x4f0/0x9d0\n btrfs_submit_data_bio+0x24e/0x310\n submit_one_bio+0x7f/0xb0\n submit_extent_page+0xc4/0x440\n __extent_writepage_io+0x2b8/0x5e0\n __extent_writepage+0x28d/0x6e0\n extent_write_cache_pages+0x4d7/0x7a0\n extent_writepages+0xa2/0x110\n do_writepages+0x8f/0x180\n __writeback_single_inode+0x99/0x7f0\n writeback_sb_inodes+0x34e/0x790\n __writeback_inodes_wb+0x9e/0x120\n wb_writeback+0x4d2/0x660\n wb_workfn+0x64d/0xa10\n process_one_work+0x53a/0xa80\n worker_thread+0x69/0x5b0\n kthread+0x20b/0x240\n ret_from_fork+0x1f/0x30\r\n\r\nOnly Kyber uses the hctx, so fix it by passing the request_queue to\n-\u0026gt;bio_merge() instead. BFQ and mq-deadline just use that, and Kyber can\nmap the queues itself to avoid the mismatch.(CVE-2021-46984)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nbus: qcom: Put child node before return\r\n\r\nPut child node before return to fix potential reference count leak.\nGenerally, the reference count of child is incremented and decremented\nautomatically in the macro for_each_available_child_of_node() and should\nbe decremented manually if the loop is broken in loop body.(CVE-2021-47054)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\ncrypto: qat - ADF_STATUS_PF_RUNNING should be set after adf_dev_init\r\n\r\nADF_STATUS_PF_RUNNING is (only) used and checked by adf_vf2pf_shutdown()\nbefore calling adf_iov_putmsg()-\u0026gt;mutex_lock(vf2pf_lock), however the\nvf2pf_lock is initialized in adf_dev_init(), which can fail and when it\nfail, the vf2pf_lock is either not initialized or destroyed, a subsequent\nuse of vf2pf_lock will cause issue.\nTo fix this issue, only set this flag if adf_dev_init() returns 0.\r\n\r\n[    7.178404] BUG: KASAN: user-memory-access in __mutex_lock.isra.0+0x1ac/0x7c0\n[    7.180345] Call Trace:\n[    7.182576]  mutex_lock+0xc9/0xd0\n[    7.183257]  adf_iov_putmsg+0x118/0x1a0 [intel_qat]\n[    7.183541]  adf_vf2pf_shutdown+0x4d/0x7b [intel_qat]\n[    7.183834]  adf_dev_shutdown+0x172/0x2b0 [intel_qat]\n[    7.184127]  adf_probe+0x5e9/0x600 [qat_dh895xccvf](CVE-2021-47056)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nKVM: Stop looking for coalesced MMIO zones if the bus is destroyed\r\n\r\nAbort the walk of coalesced MMIO zones if kvm_io_bus_unregister_dev()\nfails to allocate memory for the new instance of the bus.  If it can\u0026apos;t\ninstantiate a new bus, unregister_dev() destroys all devices _except_ the\ntarget device.   But, it doesn\u0026apos;t tell the caller that it obliterated the\nbus and invoked the destructor for all devices that were on the bus.  In\nthe coalesced MMIO case, this can result in a deleted list entry\ndereference due to attempting to continue iterating on coalesced_zones\nafter future entries (in the walk) have been deleted.\r\n\r\nOpportunistically add curly braces to the for-loop, which encompasses\nmany lines but sneaks by without braces due to the guts being a single\nif statement.(CVE-2021-47060)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nKVM: Destroy I/O bus devices on unregister failure _after_ sync\u0026apos;ing SRCU\r\n\r\nIf allocating a new instance of an I/O bus fails when unregistering a\ndevice, wait to destroy the device until after all readers are guaranteed\nto see the new null bus.  Destroying devices before the bus is nullified\ncould lead to use-after-free since readers expect the devices on their\nreference of the bus to remain valid.(CVE-2021-47061)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\ndrm: bridge/panel: Cleanup connector on bridge detach\r\n\r\nIf we don\u0026apos;t call drm_connector_cleanup() manually in\npanel_bridge_detach(), the connector will be cleaned up with the other\nDRM objects in the call to drm_mode_config_cleanup(). However, since our\ndrm_connector is devm-allocated, by the time drm_mode_config_cleanup()\nwill be called, our connector will be long gone. Therefore, the\nconnector must be cleaned up when the bridge is detached to avoid\nuse-after-free conditions.\r\n\r\nv2: Cleanup connector only if it was created\r\n\r\nv3: Add FIXME\r\n\r\nv4: (Use connector-\u0026gt;dev) directly in if() block(CVE-2021-47063)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nuio_hv_generic: Fix a memory leak in error handling paths\r\n\r\nIf \u0026apos;vmbus_establish_gpadl()\u0026apos; fails, the (recv|send)_gpadl will not be\nupdated and \u0026apos;hv_uio_cleanup()\u0026apos; in the error handling path will not be\nable to free the corresponding buffer.\r\n\r\nIn such a case, we need to free the buffer explicitly.(CVE-2021-47071)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nnvme-loop: fix memory leak in nvme_loop_create_ctrl()\r\n\r\nWhen creating loop ctrl in nvme_loop_create_ctrl(), if nvme_init_ctrl()\nfails, the loop ctrl should be freed before jumping to the \u0026quot;out\u0026quot; label.(CVE-2021-47074)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nscsi: qedf: Add pointer checks in qedf_update_link_speed()\r\n\r\nThe following trace was observed:\r\n\r\n [   14.042059] Call Trace:\n [   14.042061]  \u0026lt;IRQ\u0026gt;\n [   14.042068]  qedf_link_update+0x144/0x1f0 [qedf]\n [   14.042117]  qed_link_update+0x5c/0x80 [qed]\n [   14.042135]  qed_mcp_handle_link_change+0x2d2/0x410 [qed]\n [   14.042155]  ? qed_set_ptt+0x70/0x80 [qed]\n [   14.042170]  ? qed_set_ptt+0x70/0x80 [qed]\n [   14.042186]  ? qed_rd+0x13/0x40 [qed]\n [   14.042205]  qed_mcp_handle_events+0x437/0x690 [qed]\n [   14.042221]  ? qed_set_ptt+0x70/0x80 [qed]\n [   14.042239]  qed_int_sp_dpc+0x3a6/0x3e0 [qed]\n [   14.042245]  tasklet_action_common.isra.14+0x5a/0x100\n [   14.042250]  __do_softirq+0xe4/0x2f8\n [   14.042253]  irq_exit+0xf7/0x100\n [   14.042255]  do_IRQ+0x7f/0xd0\n [   14.042257]  common_interrupt+0xf/0xf\n [   14.042259]  \u0026lt;/IRQ\u0026gt;\r\n\r\nAPI qedf_link_update() is getting called from QED but by that time\nshost_data is not initialised. This results in a NULL pointer dereference\nwhen we try to dereference shost_data while updating supported_speeds.\r\n\r\nAdd a NULL pointer check before dereferencing shost_data.(CVE-2021-47077)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nRDMA/rxe: Clear all QP fields if creation failed\r\n\r\nrxe_qp_do_cleanup() relies on valid pointer values in QP for the properly\ncreated ones, but in case rxe_qp_from_init() failed it was filled with\ngarbage and caused tot the following error.\r\n\r\n  refcount_t: underflow; use-after-free.\n  WARNING: CPU: 1 PID: 12560 at lib/refcount.c:28 refcount_warn_saturate+0x1d1/0x1e0 lib/refcount.c:28\n  Modules linked in:\n  CPU: 1 PID: 12560 Comm: syz-executor.4 Not tainted 5.12.0-syzkaller #0\n  Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011\n  RIP: 0010:refcount_warn_saturate+0x1d1/0x1e0 lib/refcount.c:28\n  Code: e9 db fe ff ff 48 89 df e8 2c c2 ea fd e9 8a fe ff ff e8 72 6a a7 fd 48 c7 c7 e0 b2 c1 89 c6 05 dc 3a e6 09 01 e8 ee 74 fb 04 \u0026lt;0f\u0026gt; 0b e9 af fe ff ff 0f 1f 84 00 00 00 00 00 41 56 41 55 41 54 55\n  RSP: 0018:ffffc900097ceba8 EFLAGS: 00010286\n  RAX: 0000000000000000 RBX: 0000000000000000 RCX: 0000000000000000\n  RDX: 0000000000040000 RSI: ffffffff815bb075 RDI: fffff520012f9d67\n  RBP: 0000000000000003 R08: 0000000000000000 R09: 0000000000000000\n  R10: ffffffff815b4eae R11: 0000000000000000 R12: ffff8880322a4800\n  R13: ffff8880322a4940 R14: ffff888033044e00 R15: 0000000000000000\n  FS:  00007f6eb2be3700(0000) GS:ffff8880b9d00000(0000) knlGS:0000000000000000\n  CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033\n  CR2: 00007fdbe5d41000 CR3: 000000001d181000 CR4: 00000000001506e0\n  DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000\n  DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400\n  Call Trace:\n   __refcount_sub_and_test include/linux/refcount.h:283 [inline]\n   __refcount_dec_and_test include/linux/refcount.h:315 [inline]\n   refcount_dec_and_test include/linux/refcount.h:333 [inline]\n   kref_put include/linux/kref.h:64 [inline]\n   rxe_qp_do_cleanup+0x96f/0xaf0 drivers/infiniband/sw/rxe/rxe_qp.c:805\n   execute_in_process_context+0x37/0x150 kernel/workqueue.c:3327\n   rxe_elem_release+0x9f/0x180 drivers/infiniband/sw/rxe/rxe_pool.c:391\n   kref_put include/linux/kref.h:65 [inline]\n   rxe_create_qp+0x2cd/0x310 drivers/infiniband/sw/rxe/rxe_verbs.c:425\n   _ib_create_qp drivers/infiniband/core/core_priv.h:331 [inline]\n   ib_create_named_qp+0x2ad/0x1370 drivers/infiniband/core/verbs.c:1231\n   ib_create_qp include/rdma/ib_verbs.h:3644 [inline]\n   create_mad_qp+0x177/0x2d0 drivers/infiniband/core/mad.c:2920\n   ib_mad_port_open drivers/infiniband/core/mad.c:3001 [inline]\n   ib_mad_init_device+0xd6f/0x1400 drivers/infiniband/core/mad.c:3092\n   add_client_context+0x405/0x5e0 drivers/infiniband/core/device.c:717\n   enable_device_and_get+0x1cd/0x3b0 drivers/infiniband/core/device.c:1331\n   ib_register_device drivers/infiniband/core/device.c:1413 [inline]\n   ib_register_device+0x7c7/0xa50 drivers/infiniband/core/device.c:1365\n   rxe_register_device+0x3d5/0x4a0 drivers/infiniband/sw/rxe/rxe_verbs.c:1147\n   rxe_add+0x12fe/0x16d0 drivers/infiniband/sw/rxe/rxe.c:247\n   rxe_net_add+0x8c/0xe0 drivers/infiniband/sw/rxe/rxe_net.c:503\n   rxe_newlink drivers/infiniband/sw/rxe/rxe.c:269 [inline]\n   rxe_newlink+0xb7/0xe0 drivers/infiniband/sw/rxe/rxe.c:250\n   nldev_newlink+0x30e/0x550 drivers/infiniband/core/nldev.c:1555\n   rdma_nl_rcv_msg+0x36d/0x690 drivers/infiniband/core/netlink.c:195\n   rdma_nl_rcv_skb drivers/infiniband/core/netlink.c:239 [inline]\n   rdma_nl_rcv+0x2ee/0x430 drivers/infiniband/core/netlink.c:259\n   netlink_unicast_kernel net/netlink/af_netlink.c:1312 [inline]\n   netlink_unicast+0x533/0x7d0 net/netlink/af_netlink.c:1338\n   netlink_sendmsg+0x856/0xd90 net/netlink/af_netlink.c:1927\n   sock_sendmsg_nosec net/socket.c:654 [inline]\n   sock_sendmsg+0xcf/0x120 net/socket.c:674\n   ____sys_sendmsg+0x6e8/0x810 net/socket.c:2350\n   ___sys_sendmsg+0xf3/0x170 net/socket.c:2404\n   __sys_sendmsg+0xe5/0x1b0 net/socket.c:2433\n   do_syscall_64+0x3a/0xb0 arch/x86/entry/common.c:47\n   entry_SYSCALL_64_after_hwframe+0\n---truncated---(CVE-2021-47078)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nasix: fix uninit-value in asix_mdio_read()\r\n\r\nasix_read_cmd() may read less than sizeof(smsr) bytes and in this case\nsmsr will be uninitialized.\r\n\r\nFail log:\nBUG: KMSAN: uninit-value in asix_check_host_enable drivers/net/usb/asix_common.c:82 [inline]\nBUG: KMSAN: uninit-value in asix_check_host_enable drivers/net/usb/asix_common.c:82 [inline] drivers/net/usb/asix_common.c:497\nBUG: KMSAN: uninit-value in asix_mdio_read+0x3c1/0xb00 drivers/net/usb/asix_common.c:497 drivers/net/usb/asix_common.c:497\n asix_check_host_enable drivers/net/usb/asix_common.c:82 [inline]\n asix_check_host_enable drivers/net/usb/asix_common.c:82 [inline] drivers/net/usb/asix_common.c:497\n asix_mdio_read+0x3c1/0xb00 drivers/net/usb/asix_common.c:497 drivers/net/usb/asix_common.c:497(CVE-2021-47101)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nnet/tls: Fix use-after-free after the TLS device goes down and up\r\n\r\nWhen a netdev with active TLS offload goes down, tls_device_down is\ncalled to stop the offload and tear down the TLS context. However, the\nsocket stays alive, and it still points to the TLS context, which is now\ndeallocated. If a netdev goes up, while the connection is still active,\nand the data flow resumes after a number of TCP retransmissions, it will\nlead to a use-after-free of the TLS context.\r\n\r\nThis commit addresses this bug by keeping the context alive until its\nnormal destruction, and implements the necessary fallbacks, so that the\nconnection can resume in software (non-offloaded) kTLS mode.\r\n\r\nOn the TX side tls_sw_fallback is used to encrypt all packets. The RX\nside already has all the necessary fallbacks, because receiving\nnon-decrypted packets is supported. The thing needed on the RX side is\nto block resync requests, which are normally produced after receiving\nnon-decrypted packets.\r\n\r\nThe necessary synchronization is implemented for a graceful teardown:\nfirst the fallbacks are deployed, then the driver resources are released\n(it used to be possible to have a tls_dev_resync after tls_dev_del).\r\n\r\nA new flag called TLS_RX_DEV_DEGRADED is added to indicate the fallback\nmode. It\u0026apos;s used to skip the RX resync logic completely, as it becomes\nuseless, and some objects may be released (for example, resync_async,\nwhich is allocated and freed by the driver).(CVE-2021-47131)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\ndrm/amdgpu: Fix a use-after-free\r\n\r\nlooks like we forget to set ttm-\u0026gt;sg to NULL.\nHit panic below\r\n\r\n[ 1235.844104] general protection fault, probably for non-canonical address 0x6b6b6b6b6b6b7b4b: 0000 [#1] SMP DEBUG_PAGEALLOC NOPTI\n[ 1235.989074] Call Trace:\n[ 1235.991751]  sg_free_table+0x17/0x20\n[ 1235.995667]  amdgpu_ttm_backend_unbind.cold+0x4d/0xf7 [amdgpu]\n[ 1236.002288]  amdgpu_ttm_backend_destroy+0x29/0x130 [amdgpu]\n[ 1236.008464]  ttm_tt_destroy+0x1e/0x30 [ttm]\n[ 1236.013066]  ttm_bo_cleanup_memtype_use+0x51/0xa0 [ttm]\n[ 1236.018783]  ttm_bo_release+0x262/0xa50 [ttm]\n[ 1236.023547]  ttm_bo_put+0x82/0xd0 [ttm]\n[ 1236.027766]  amdgpu_bo_unref+0x26/0x50 [amdgpu]\n[ 1236.032809]  amdgpu_amdkfd_gpuvm_alloc_memory_of_gpu+0x7aa/0xd90 [amdgpu]\n[ 1236.040400]  kfd_ioctl_alloc_memory_of_gpu+0xe2/0x330 [amdgpu]\n[ 1236.046912]  kfd_ioctl+0x463/0x690 [amdgpu](CVE-2021-47142)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nnet/smc: remove device from smcd_dev_list after failed device_add()\r\n\r\nIf the device_add() for a smcd_dev fails, there\u0026apos;s no cleanup step that\nrolls back the earlier list_add(). The device subsequently gets freed,\nand we end up with a corrupted list.\r\n\r\nAdd some error handling that removes the device from the list.(CVE-2021-47143)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\ndrm/amd/amdgpu: fix refcount leak\r\n\r\n[Why]\nthe gem object rfb-\u0026gt;base.obj[0] is get according to num_planes\nin amdgpufb_create, but is not put according to num_planes\r\n\r\n[How]\nput rfb-\u0026gt;base.obj[0] in amdgpu_fbdev_destroy according to num_planes(CVE-2021-47144)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nbtrfs: do not BUG_ON in link_to_fixup_dir\r\n\r\nWhile doing error injection testing I got the following panic\r\n\r\n  kernel BUG at fs/btrfs/tree-log.c:1862!\n  invalid opcode: 0000 [#1] SMP NOPTI\n  CPU: 1 PID: 7836 Comm: mount Not tainted 5.13.0-rc1+ #305\n  Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.13.0-2.fc32 04/01/2014\n  RIP: 0010:link_to_fixup_dir+0xd5/0xe0\n  RSP: 0018:ffffb5800180fa30 EFLAGS: 00010216\n  RAX: fffffffffffffffb RBX: 00000000fffffffb RCX: ffff8f595287faf0\n  RDX: ffffb5800180fa37 RSI: ffff8f5954978800 RDI: 0000000000000000\n  RBP: ffff8f5953af9450 R08: 0000000000000019 R09: 0000000000000001\n  R10: 000151f408682970 R11: 0000000120021001 R12: ffff8f5954978800\n  R13: ffff8f595287faf0 R14: ffff8f5953c77dd0 R15: 0000000000000065\n  FS:  00007fc5284c8c40(0000) GS:ffff8f59bbd00000(0000) knlGS:0000000000000000\n  CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033\n  CR2: 00007fc5287f47c0 CR3: 000000011275e002 CR4: 0000000000370ee0\n  Call Trace:\n   replay_one_buffer+0x409/0x470\n   ? btree_read_extent_buffer_pages+0xd0/0x110\n   walk_up_log_tree+0x157/0x1e0\n   walk_log_tree+0xa6/0x1d0\n   btrfs_recover_log_trees+0x1da/0x360\n   ? replay_one_extent+0x7b0/0x7b0\n   open_ctree+0x1486/0x1720\n   btrfs_mount_root.cold+0x12/0xea\n   ? __kmalloc_track_caller+0x12f/0x240\n   legacy_get_tree+0x24/0x40\n   vfs_get_tree+0x22/0xb0\n   vfs_kern_mount.part.0+0x71/0xb0\n   btrfs_mount+0x10d/0x380\n   ? vfs_parse_fs_string+0x4d/0x90\n   legacy_get_tree+0x24/0x40\n   vfs_get_tree+0x22/0xb0\n   path_mount+0x433/0xa10\n   __x64_sys_mount+0xe3/0x120\n   do_syscall_64+0x3d/0x80\n   entry_SYSCALL_64_after_hwframe+0x44/0xae\r\n\r\nWe can get -EIO or any number of legitimate errors from\nbtrfs_search_slot(), panicing here is not the appropriate response.  The\nerror path for this code handles errors properly, simply return the\nerror.(CVE-2021-47145)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nmld: fix panic in mld_newpack()\r\n\r\nmld_newpack() doesn\u0026apos;t allow to allocate high order page,\nonly order-0 allocation is allowed.\nIf headroom size is too large, a kernel panic could occur in skb_put().\r\n\r\nTest commands:\n    ip netns del A\n    ip netns del B\n    ip netns add A\n    ip netns add B\n    ip link add veth0 type veth peer name veth1\n    ip link set veth0 netns A\n    ip link set veth1 netns B\r\n\r\n    ip netns exec A ip link set lo up\n    ip netns exec A ip link set veth0 up\n    ip netns exec A ip -6 a a 2001:db8:0::1/64 dev veth0\n    ip netns exec B ip link set lo up\n    ip netns exec B ip link set veth1 up\n    ip netns exec B ip -6 a a 2001:db8:0::2/64 dev veth1\n    for i in {1..99}\n    do\n        let A=$i-1\n        ip netns exec A ip link add ip6gre$i type ip6gre \\\n\tlocal 2001:db8:$A::1 remote 2001:db8:$A::2 encaplimit 100\n        ip netns exec A ip -6 a a 2001:db8:$i::1/64 dev ip6gre$i\n        ip netns exec A ip link set ip6gre$i up\r\n\r\n        ip netns exec B ip link add ip6gre$i type ip6gre \\\n\tlocal 2001:db8:$A::2 remote 2001:db8:$A::1 encaplimit 100\n        ip netns exec B ip -6 a a 2001:db8:$i::2/64 dev ip6gre$i\n        ip netns exec B ip link set ip6gre$i up\n    done\r\n\r\nSplat looks like:\nkernel BUG at net/core/skbuff.c:110!\ninvalid opcode: 0000 [#1] SMP DEBUG_PAGEALLOC KASAN PTI\nCPU: 0 PID: 7 Comm: kworker/0:1 Not tainted 5.12.0+ #891\nWorkqueue: ipv6_addrconf addrconf_dad_work\nRIP: 0010:skb_panic+0x15d/0x15f\nCode: 92 fe 4c 8b 4c 24 10 53 8b 4d 70 45 89 e0 48 c7 c7 00 ae 79 83\n41 57 41 56 41 55 48 8b 54 24 a6 26 f9 ff \u0026lt;0f\u0026gt; 0b 48 8b 6c 24 20 89\n34 24 e8 4a 4e 92 fe 8b 34 24 48 c7 c1 20\nRSP: 0018:ffff88810091f820 EFLAGS: 00010282\nRAX: 0000000000000089 RBX: ffff8881086e9000 RCX: 0000000000000000\nRDX: 0000000000000089 RSI: 0000000000000008 RDI: ffffed1020123efb\nRBP: ffff888005f6eac0 R08: ffffed1022fc0031 R09: ffffed1022fc0031\nR10: ffff888117e00187 R11: ffffed1022fc0030 R12: 0000000000000028\nR13: ffff888008284eb0 R14: 0000000000000ed8 R15: 0000000000000ec0\nFS:  0000000000000000(0000) GS:ffff888117c00000(0000)\nknlGS:0000000000000000\nCS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033\nCR2: 00007f8b801c5640 CR3: 0000000033c2c006 CR4: 00000000003706f0\nDR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000\nDR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400\nCall Trace:\n ? ip6_mc_hdr.isra.26.constprop.46+0x12a/0x600\n ? ip6_mc_hdr.isra.26.constprop.46+0x12a/0x600\n skb_put.cold.104+0x22/0x22\n ip6_mc_hdr.isra.26.constprop.46+0x12a/0x600\n ? rcu_read_lock_sched_held+0x91/0xc0\n mld_newpack+0x398/0x8f0\n ? ip6_mc_hdr.isra.26.constprop.46+0x600/0x600\n ? lock_contended+0xc40/0xc40\n add_grhead.isra.33+0x280/0x380\n add_grec+0x5ca/0xff0\n ? mld_sendpack+0xf40/0xf40\n ? lock_downgrade+0x690/0x690\n mld_send_initial_cr.part.34+0xb9/0x180\n ipv6_mc_dad_complete+0x15d/0x1b0\n addrconf_dad_completed+0x8d2/0xbb0\n ? lock_downgrade+0x690/0x690\n ? addrconf_rs_timer+0x660/0x660\n ? addrconf_dad_work+0x73c/0x10e0\n addrconf_dad_work+0x73c/0x10e0\r\n\r\nAllowing high order page allocation could fix this problem.(CVE-2021-47146)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\ni2c: i801: Don\u0026apos;t generate an interrupt on bus reset\r\n\r\nNow that the i2c-i801 driver supports interrupts, setting the KILL bit\nin a attempt to recover from a timed out transaction triggers an\ninterrupt. Unfortunately, the interrupt handler (i801_isr) is not\nprepared for this situation and will try to process the interrupt as\nif it was signaling the end of a successful transaction. In the case\nof a block transaction, this can result in an out-of-range memory\naccess.\r\n\r\nThis condition was reproduced several times by syzbot:\nhttps://syzkaller.appspot.com/bug?extid=ed71512d469895b5b34e\nhttps://syzkaller.appspot.com/bug?extid=8c8dedc0ba9e03f6c79e\nhttps://syzkaller.appspot.com/bug?extid=c8ff0b6d6c73d81b610e\nhttps://syzkaller.appspot.com/bug?extid=33f6c360821c399d69eb\nhttps://syzkaller.appspot.com/bug?extid=be15dc0b1933f04b043a\nhttps://syzkaller.appspot.com/bug?extid=b4d3fd1dfd53e90afd79\r\n\r\nSo disable interrupts while trying to reset the bus. Interrupts will\nbe enabled again for the following transaction.(CVE-2021-47153)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nnet: dsa: fix a crash if -\u0026gt;get_sset_count() fails\r\n\r\nIf ds-\u0026gt;ops-\u0026gt;get_sset_count() fails then it \u0026quot;count\u0026quot; is a negative error\ncode such as -EOPNOTSUPP.  Because \u0026quot;i\u0026quot; is an unsigned int, the negative\nerror code is type promoted to a very high value and the loop will\ncorrupt memory until the system crashes.\r\n\r\nFix this by checking for error codes and changing the type of \u0026quot;i\u0026quot; to\njust int.(CVE-2021-47159)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nnet: dsa: mt7530: fix VLAN traffic leaks\r\n\r\nPCR_MATRIX field was set to all 1\u0026apos;s when VLAN filtering is enabled, but\nwas not reset when it is disabled, which may cause traffic leaks:\r\n\r\n\tip link add br0 type bridge vlan_filtering 1\n\tip link add br1 type bridge vlan_filtering 1\n\tip link set swp0 master br0\n\tip link set swp1 master br1\n\tip link set br0 type bridge vlan_filtering 0\n\tip link set br1 type bridge vlan_filtering 0\n\t# traffic in br0 and br1 will start leaking to each other\r\n\r\nAs port_bridge_{add,del} have set up PCR_MATRIX properly, remove the\nPCR_MATRIX write from mt7530_port_set_vlan_aware.(CVE-2021-47160)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nspi: spi-fsl-dspi: Fix a resource leak in an error handling path\r\n\r\n\u0026apos;dspi_request_dma()\u0026apos; should be undone by a \u0026apos;dspi_release_dma()\u0026apos; call in the\nerror handling path of the probe function, as already done in the remove\nfunction(CVE-2021-47161)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\ntipc: skb_linearize the head skb when reassembling msgs\r\n\r\nIt\u0026apos;s not a good idea to append the frag skb to a skb\u0026apos;s frag_list if\nthe frag_list already has skbs from elsewhere, such as this skb was\ncreated by pskb_copy() where the frag_list was cloned (all the skbs\nin it were skb_get\u0026apos;ed) and shared by multiple skbs.\r\n\r\nHowever, the new appended frag skb should have been only seen by the\ncurrent skb. Otherwise, it will cause use after free crashes as this\nappended frag skb are seen by multiple skbs but it only got skb_get\ncalled once.\r\n\r\nThe same thing happens with a skb updated by pskb_may_pull() with a\nskb_cloned skb. Li Shuang has reported quite a few crashes caused\nby this when doing testing over macvlan devices:\r\n\r\n  [] kernel BUG at net/core/skbuff.c:1970!\n  [] Call Trace:\n  []  skb_clone+0x4d/0xb0\n  []  macvlan_broadcast+0xd8/0x160 [macvlan]\n  []  macvlan_process_broadcast+0x148/0x150 [macvlan]\n  []  process_one_work+0x1a7/0x360\n  []  worker_thread+0x30/0x390\r\n\r\n  [] kernel BUG at mm/usercopy.c:102!\n  [] Call Trace:\n  []  __check_heap_object+0xd3/0x100\n  []  __check_object_size+0xff/0x16b\n  []  simple_copy_to_iter+0x1c/0x30\n  []  __skb_datagram_iter+0x7d/0x310\n  []  __skb_datagram_iter+0x2a5/0x310\n  []  skb_copy_datagram_iter+0x3b/0x90\n  []  tipc_recvmsg+0x14a/0x3a0 [tipc]\n  []  ____sys_recvmsg+0x91/0x150\n  []  ___sys_recvmsg+0x7b/0xc0\r\n\r\n  [] kernel BUG at mm/slub.c:305!\n  [] Call Trace:\n  []  \u0026lt;IRQ\u0026gt;\n  []  kmem_cache_free+0x3ff/0x400\n  []  __netif_receive_skb_core+0x12c/0xc40\n  []  ? kmem_cache_alloc+0x12e/0x270\n  []  netif_receive_skb_internal+0x3d/0xb0\n  []  ? get_rx_page_info+0x8e/0xa0 [be2net]\n  []  be_poll+0x6ef/0xd00 [be2net]\n  []  ? irq_exit+0x4f/0x100\n  []  net_rx_action+0x149/0x3b0\r\n\r\n  ...\r\n\r\nThis patch is to fix it by linearizing the head skb if it has frag_list\nset in tipc_buf_append(). Note that we choose to do this before calling\nskb_unshare(), as __skb_linearize() will avoid skb_copy(). Also, we can\nnot just drop the frag_list either as the early time.(CVE-2021-47162)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\ntipc: wait and exit until all work queues are done\r\n\r\nOn some host, a crash could be triggered simply by repeating these\ncommands several times:\r\n\r\n  # modprobe tipc\n  # tipc bearer enable media udp name UDP1 localip 127.0.0.1\n  # rmmod tipc\r\n\r\n  [] BUG: unable to handle kernel paging request at ffffffffc096bb00\n  [] Workqueue: events 0xffffffffc096bb00\n  [] Call Trace:\n  []  ? process_one_work+0x1a7/0x360\n  []  ? worker_thread+0x30/0x390\n  []  ? create_worker+0x1a0/0x1a0\n  []  ? kthread+0x116/0x130\n  []  ? kthread_flush_work_fn+0x10/0x10\n  []  ? ret_from_fork+0x35/0x40\r\n\r\nWhen removing the TIPC module, the UDP tunnel sock will be delayed to\nrelease in a work queue as sock_release() can\u0026apos;t be done in rtnl_lock().\nIf the work queue is schedule to run after the TIPC module is removed,\nkernel will crash as the work queue function cleanup_beareri() code no\nlonger exists when trying to invoke it.\r\n\r\nTo fix it, this patch introduce a member wq_count in tipc_net to track\nthe numbers of work queues in schedule, and  wait and exit until all\nwork queues are done in tipc_exit_net().(CVE-2021-47163)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nNFS: Fix an Oopsable condition in __nfs_pageio_add_request()\r\n\r\nEnsure that nfs_pageio_error_cleanup() resets the mirror array contents,\nso that the structure reflects the fact that it is now empty.\nAlso change the test in nfs_pageio_do_add_request() to be more robust by\nchecking whether or not the list is empty rather than relying on the\nvalue of pg_count.(CVE-2021-47167)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nUSB: usbfs: Don\u0026apos;t WARN about excessively large memory allocations\r\n\r\nSyzbot found that the kernel generates a WARNing if the user tries to\nsubmit a bulk transfer through usbfs with a buffer that is way too\nlarge.  This isn\u0026apos;t a bug in the kernel; it\u0026apos;s merely an invalid request\nfrom the user and the usbfs code does handle it correctly.\r\n\r\nIn theory the same thing can happen with async transfers, or with the\npacket descriptor table for isochronous transfers.\r\n\r\nTo prevent the MM subsystem from complaining about these bad\nallocation requests, add the __GFP_NOWARN flag to the kmalloc calls\nfor these buffers.(CVE-2021-47170)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nnet: usb: fix memory leak in smsc75xx_bind\r\n\r\nSyzbot reported memory leak in smsc75xx_bind().\nThe problem was is non-freed memory in case of\nerrors after memory allocation.\r\n\r\nbacktrace:\n  [\u0026lt;ffffffff84245b62\u0026gt;] kmalloc include/linux/slab.h:556 [inline]\n  [\u0026lt;ffffffff84245b62\u0026gt;] kzalloc include/linux/slab.h:686 [inline]\n  [\u0026lt;ffffffff84245b62\u0026gt;] smsc75xx_bind+0x7a/0x334 drivers/net/usb/smsc75xx.c:1460\n  [\u0026lt;ffffffff82b5b2e6\u0026gt;] usbnet_probe+0x3b6/0xc30 drivers/net/usb/usbnet.c:1728(CVE-2021-47171)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nmisc/uss720: fix memory leak in uss720_probe\r\n\r\nuss720_probe forgets to decrease the refcount of usbdev in uss720_probe.\nFix this by decreasing the refcount of usbdev by usb_put_dev.\r\n\r\nBUG: memory leak\nunreferenced object 0xffff888101113800 (size 2048):\n  comm \u0026quot;kworker/0:1\u0026quot;, pid 7, jiffies 4294956777 (age 28.870s)\n  hex dump (first 32 bytes):\n    ff ff ff ff 31 00 00 00 00 00 00 00 00 00 00 00  ....1...........\n    00 00 00 00 00 00 00 00 00 00 00 00 03 00 00 00  ................\n  backtrace:\n    [\u0026lt;ffffffff82b8e822\u0026gt;] kmalloc include/linux/slab.h:554 [inline]\n    [\u0026lt;ffffffff82b8e822\u0026gt;] kzalloc include/linux/slab.h:684 [inline]\n    [\u0026lt;ffffffff82b8e822\u0026gt;] usb_alloc_dev+0x32/0x450 drivers/usb/core/usb.c:582\n    [\u0026lt;ffffffff82b98441\u0026gt;] hub_port_connect drivers/usb/core/hub.c:5129 [inline]\n    [\u0026lt;ffffffff82b98441\u0026gt;] hub_port_connect_change drivers/usb/core/hub.c:5363 [inline]\n    [\u0026lt;ffffffff82b98441\u0026gt;] port_event drivers/usb/core/hub.c:5509 [inline]\n    [\u0026lt;ffffffff82b98441\u0026gt;] hub_event+0x1171/0x20c0 drivers/usb/core/hub.c:5591\n    [\u0026lt;ffffffff81259229\u0026gt;] process_one_work+0x2c9/0x600 kernel/workqueue.c:2275\n    [\u0026lt;ffffffff81259b19\u0026gt;] worker_thread+0x59/0x5d0 kernel/workqueue.c:2421\n    [\u0026lt;ffffffff81261228\u0026gt;] kthread+0x178/0x1b0 kernel/kthread.c:292\n    [\u0026lt;ffffffff8100227f\u0026gt;] ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:294(CVE-2021-47173)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nNFC: nci: fix memory leak in nci_allocate_device\r\n\r\nnfcmrvl_disconnect fails to free the hci_dev field in struct nci_dev.\nFix this by freeing hci_dev in nci_free_device.\r\n\r\nBUG: memory leak\nunreferenced object 0xffff888111ea6800 (size 1024):\n  comm \u0026quot;kworker/1:0\u0026quot;, pid 19, jiffies 4294942308 (age 13.580s)\n  hex dump (first 32 bytes):\n    00 00 00 00 00 00 00 00 00 60 fd 0c 81 88 ff ff  .........`......\n    00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................\n  backtrace:\n    [\u0026lt;000000004bc25d43\u0026gt;] kmalloc include/linux/slab.h:552 [inline]\n    [\u0026lt;000000004bc25d43\u0026gt;] kzalloc include/linux/slab.h:682 [inline]\n    [\u0026lt;000000004bc25d43\u0026gt;] nci_hci_allocate+0x21/0xd0 net/nfc/nci/hci.c:784\n    [\u0026lt;00000000c59cff92\u0026gt;] nci_allocate_device net/nfc/nci/core.c:1170 [inline]\n    [\u0026lt;00000000c59cff92\u0026gt;] nci_allocate_device+0x10b/0x160 net/nfc/nci/core.c:1132\n    [\u0026lt;00000000006e0a8e\u0026gt;] nfcmrvl_nci_register_dev+0x10a/0x1c0 drivers/nfc/nfcmrvl/main.c:153\n    [\u0026lt;000000004da1b57e\u0026gt;] nfcmrvl_probe+0x223/0x290 drivers/nfc/nfcmrvl/usb.c:345\n    [\u0026lt;00000000d506aed9\u0026gt;] usb_probe_interface+0x177/0x370 drivers/usb/core/driver.c:396\n    [\u0026lt;00000000bc632c92\u0026gt;] really_probe+0x159/0x4a0 drivers/base/dd.c:554\n    [\u0026lt;00000000f5009125\u0026gt;] driver_probe_device+0x84/0x100 drivers/base/dd.c:740\n    [\u0026lt;000000000ce658ca\u0026gt;] __device_attach_driver+0xee/0x110 drivers/base/dd.c:846\n    [\u0026lt;000000007067d05f\u0026gt;] bus_for_each_drv+0xb7/0x100 drivers/base/bus.c:431\n    [\u0026lt;00000000f8e13372\u0026gt;] __device_attach+0x122/0x250 drivers/base/dd.c:914\n    [\u0026lt;000000009cf68860\u0026gt;] bus_probe_device+0xc6/0xe0 drivers/base/bus.c:491\n    [\u0026lt;00000000359c965a\u0026gt;] device_add+0x5be/0xc30 drivers/base/core.c:3109\n    [\u0026lt;00000000086e4bd3\u0026gt;] usb_set_configuration+0x9d9/0xb90 drivers/usb/core/message.c:2164\n    [\u0026lt;00000000ca036872\u0026gt;] usb_generic_driver_probe+0x8c/0xc0 drivers/usb/core/generic.c:238\n    [\u0026lt;00000000d40d36f6\u0026gt;] usb_probe_device+0x5c/0x140 drivers/usb/core/driver.c:293\n    [\u0026lt;00000000bc632c92\u0026gt;] really_probe+0x159/0x4a0 drivers/base/dd.c:554(CVE-2021-47180)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nEDAC/thunderx: Fix possible out-of-bounds string access\r\n\r\nEnabling -Wstringop-overflow globally exposes a warning for a common bug\nin the usage of strncat():\r\n\r\n  drivers/edac/thunderx_edac.c: In function \u0026apos;thunderx_ocx_com_threaded_isr\u0026apos;:\n  drivers/edac/thunderx_edac.c:1136:17: error: \u0026apos;strncat\u0026apos; specified bound 1024 equals destination size [-Werror=stringop-overflow=]\n   1136 |                 strncat(msg, other, OCX_MESSAGE_SIZE);\n        |                 ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~\n   ...\n   1145 |                                 strncat(msg, other, OCX_MESSAGE_SIZE);\n   ...\n   1150 |                                 strncat(msg, other, OCX_MESSAGE_SIZE);\r\n\r\n   ...\r\n\r\nApparently the author of this driver expected strncat() to behave the\nway that strlcat() does, which uses the size of the destination buffer\nas its third argument rather than the length of the source buffer. The\nresult is that there is no check on the size of the allocated buffer.\r\n\r\nChange it to strlcat().\r\n\r\n  [ bp: Trim compiler output, fixup commit message. ](CVE-2023-52464)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nInput: powermate - fix use-after-free in powermate_config_complete\r\n\r\nsyzbot has found a use-after-free bug [1] in the powermate driver. This\nhappens when the device is disconnected, which leads to a memory free from\nthe powermate_device struct.  When an asynchronous control message\ncompletes after the kfree and its callback is invoked, the lock does not\nexist anymore and hence the bug.\r\n\r\nUse usb_kill_urb() on pm-\u0026gt;config to cancel any in-progress requests upon\ndevice disconnection.\r\n\r\n[1] https://syzkaller.appspot.com/bug?extid=0434ac83f907a1dbdd1e(CVE-2023-52475)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nscsi: pm80xx: Avoid leaking tags when processing OPC_INB_SET_CONTROLLER_CONFIG command\r\n\r\nTags allocated for OPC_INB_SET_CONTROLLER_CONFIG command need to be freed\nwhen we receive the response.(CVE-2023-52500)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nnfc: nci: assert requested protocol is valid\r\n\r\nThe protocol is used in a bit mask to determine if the protocol is\nsupported. Assert the provided protocol is less than the maximum\ndefined so it doesn\u0026apos;t potentially perform a shift-out-of-bounds and\nprovide a clearer error for undefined protocols vs unsupported ones.(CVE-2023-52507)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nieee802154: ca8210: Fix a potential UAF in ca8210_probe\r\n\r\nIf of_clk_add_provider() fails in ca8210_register_ext_clock(),\nit calls clk_unregister() to release priv-\u0026gt;clk and returns an\nerror. However, the caller ca8210_probe() then calls ca8210_remove(),\nwhere priv-\u0026gt;clk is freed again in ca8210_unregister_ext_clock(). In\nthis case, a use-after-free may happen in the second time we call\nclk_unregister().\r\n\r\nFix this by removing the first clk_unregister(). Also, priv-\u0026gt;clk could\nbe an error code on failure of clk_register_fixed_rate(). Use\nIS_ERR_OR_NULL to catch this case in ca8210_unregister_ext_clock().(CVE-2023-52510)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nRDMA/srp: Do not call scsi_done() from srp_abort()\r\n\r\nAfter scmd_eh_abort_handler() has called the SCSI LLD eh_abort_handler\ncallback, it performs one of the following actions:\n* Call scsi_queue_insert().\n* Call scsi_finish_command().\n* Call scsi_eh_scmd_add().\nHence, SCSI abort handlers must not call scsi_done(). Otherwise all\nthe above actions would trigger a use-after-free. Hence remove the\nscsi_done() call from srp_abort(). Keep the srp_free_req() call\nbefore returning SUCCESS because we may not see the command again if\nSUCCESS is returned.(CVE-2023-52515)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nnet: fix possible store tearing in neigh_periodic_work()\r\n\r\nWhile looking at a related syzbot report involving neigh_periodic_work(),\nI found that I forgot to add an annotation when deleting an\nRCU protected item from a list.\r\n\r\nReaders use rcu_deference(*np), we need to use either\nrcu_assign_pointer() or WRITE_ONCE() on writer side\nto prevent store tearing.\r\n\r\nI use rcu_assign_pointer() to have lockdep support,\nthis was the choice made in neigh_flush_dev().(CVE-2023-52522)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nwifi: mac80211: fix potential key use-after-free\r\n\r\nWhen ieee80211_key_link() is called by ieee80211_gtk_rekey_add()\nbut returns 0 due to KRACK protection (identical key reinstall),\nieee80211_gtk_rekey_add() will still return a pointer into the\nkey, in a potential use-after-free. This normally doesn\u0026apos;t happen\nsince it\u0026apos;s only called by iwlwifi in case of WoWLAN rekey offload\nwhich has its own KRACK protection, but still better to fix, do\nthat by returning an error code and converting that to success on\nthe cfg80211 boundary only, leaving the error for bad callers of\nieee80211_gtk_rekey_add().(CVE-2023-52530)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nnilfs2: fix potential use after free in nilfs_gccache_submit_read_data()\r\n\r\nIn nilfs_gccache_submit_read_data(), brelse(bh) is called to drop the\nreference count of bh when the call to nilfs_dat_translate() fails.  If\nthe reference count hits 0 and its owner page gets unlocked, bh may be\nfreed.  However, bh-\u0026gt;b_page is dereferenced to put the page after that,\nwhich may result in a use-after-free bug.  This patch moves the release\noperation after unlocking and putting the page.\r\n\r\nNOTE: The function in question is only called in GC, and in combination\nwith current userland tools, address translation using DAT does not occur\nin that function, so the code path that causes this issue will not be\nexecuted.  However, it is possible to run that code path by intentionally\nmodifying the userland GC library or by calling the GC ioctl directly.\r\n\r\n[konishi.ryusuke@gmail.com: NOTE added to the commit log](CVE-2023-52566)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nnet: bridge: use DEV_STATS_INC()\r\n\r\nsyzbot/KCSAN reported data-races in br_handle_frame_finish() [1]\nThis function can run from multiple cpus without mutual exclusion.\r\n\r\nAdopt SMP safe DEV_STATS_INC() to update dev-\u0026gt;stats fields.\r\n\r\nHandles updates to dev-\u0026gt;stats.tx_dropped while we are at it.\r\n\r\n[1]\nBUG: KCSAN: data-race in br_handle_frame_finish / br_handle_frame_finish\r\n\r\nread-write to 0xffff8881374b2178 of 8 bytes by interrupt on cpu 1:\nbr_handle_frame_finish+0xd4f/0xef0 net/bridge/br_input.c:189\nbr_nf_hook_thresh+0x1ed/0x220\nbr_nf_pre_routing_finish_ipv6+0x50f/0x540\nNF_HOOK include/linux/netfilter.h:304 [inline]\nbr_nf_pre_routing_ipv6+0x1e3/0x2a0 net/bridge/br_netfilter_ipv6.c:178\nbr_nf_pre_routing+0x526/0xba0 net/bridge/br_netfilter_hooks.c:508\nnf_hook_entry_hookfn include/linux/netfilter.h:144 [inline]\nnf_hook_bridge_pre net/bridge/br_input.c:272 [inline]\nbr_handle_frame+0x4c9/0x940 net/bridge/br_input.c:417\n__netif_receive_skb_core+0xa8a/0x21e0 net/core/dev.c:5417\n__netif_receive_skb_one_core net/core/dev.c:5521 [inline]\n__netif_receive_skb+0x57/0x1b0 net/core/dev.c:5637\nprocess_backlog+0x21f/0x380 net/core/dev.c:5965\n__napi_poll+0x60/0x3b0 net/core/dev.c:6527\nnapi_poll net/core/dev.c:6594 [inline]\nnet_rx_action+0x32b/0x750 net/core/dev.c:6727\n__do_softirq+0xc1/0x265 kernel/softirq.c:553\nrun_ksoftirqd+0x17/0x20 kernel/softirq.c:921\nsmpboot_thread_fn+0x30a/0x4a0 kernel/smpboot.c:164\nkthread+0x1d7/0x210 kernel/kthread.c:388\nret_from_fork+0x48/0x60 arch/x86/kernel/process.c:147\nret_from_fork_asm+0x11/0x20 arch/x86/entry/entry_64.S:304\r\n\r\nread-write to 0xffff8881374b2178 of 8 bytes by interrupt on cpu 0:\nbr_handle_frame_finish+0xd4f/0xef0 net/bridge/br_input.c:189\nbr_nf_hook_thresh+0x1ed/0x220\nbr_nf_pre_routing_finish_ipv6+0x50f/0x540\nNF_HOOK include/linux/netfilter.h:304 [inline]\nbr_nf_pre_routing_ipv6+0x1e3/0x2a0 net/bridge/br_netfilter_ipv6.c:178\nbr_nf_pre_routing+0x526/0xba0 net/bridge/br_netfilter_hooks.c:508\nnf_hook_entry_hookfn include/linux/netfilter.h:144 [inline]\nnf_hook_bridge_pre net/bridge/br_input.c:272 [inline]\nbr_handle_frame+0x4c9/0x940 net/bridge/br_input.c:417\n__netif_receive_skb_core+0xa8a/0x21e0 net/core/dev.c:5417\n__netif_receive_skb_one_core net/core/dev.c:5521 [inline]\n__netif_receive_skb+0x57/0x1b0 net/core/dev.c:5637\nprocess_backlog+0x21f/0x380 net/core/dev.c:5965\n__napi_poll+0x60/0x3b0 net/core/dev.c:6527\nnapi_poll net/core/dev.c:6594 [inline]\nnet_rx_action+0x32b/0x750 net/core/dev.c:6727\n__do_softirq+0xc1/0x265 kernel/softirq.c:553\ndo_softirq+0x5e/0x90 kernel/softirq.c:454\n__local_bh_enable_ip+0x64/0x70 kernel/softirq.c:381\n__raw_spin_unlock_bh include/linux/spinlock_api_smp.h:167 [inline]\n_raw_spin_unlock_bh+0x36/0x40 kernel/locking/spinlock.c:210\nspin_unlock_bh include/linux/spinlock.h:396 [inline]\nbatadv_tt_local_purge+0x1a8/0x1f0 net/batman-adv/translation-table.c:1356\nbatadv_tt_purge+0x2b/0x630 net/batman-adv/translation-table.c:3560\nprocess_one_work kernel/workqueue.c:2630 [inline]\nprocess_scheduled_works+0x5b8/0xa30 kernel/workqueue.c:2703\nworker_thread+0x525/0x730 kernel/workqueue.c:2784\nkthread+0x1d7/0x210 kernel/kthread.c:388\nret_from_fork+0x48/0x60 arch/x86/kernel/process.c:147\nret_from_fork_asm+0x11/0x20 arch/x86/entry/entry_64.S:304\r\n\r\nvalue changed: 0x00000000000d7190 -\u0026gt; 0x00000000000d7191\r\n\r\nReported by Kernel Concurrency Sanitizer on:\nCPU: 0 PID: 14848 Comm: kworker/u4:11 Not tainted 6.6.0-rc1-syzkaller-00236-gad8a69f361b9 #0(CVE-2023-52578)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nceph: fix deadlock or deadcode of misusing dget()\r\n\r\nThe lock order is incorrect between denty and its parent, we should\nalways make sure that the parent get the lock first.\r\n\r\nBut since this deadcode is never used and the parent dir will always\nbe set from the callers, let\u0026apos;s just remove it.(CVE-2023-52583)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nIB/ipoib: Fix mcast list locking\r\n\r\nReleasing the `priv-\u0026gt;lock` while iterating the `priv-\u0026gt;multicast_list` in\n`ipoib_mcast_join_task()` opens a window for `ipoib_mcast_dev_flush()` to\nremove the items while in the middle of iteration. If the mcast is removed\nwhile the lock was dropped, the for loop spins forever resulting in a hard\nlockup (as was reported on RHEL 4.18.0-372.75.1.el8_6 kernel):\r\n\r\n    Task A (kworker/u72:2 below)       | Task B (kworker/u72:0 below)\n    -----------------------------------+-----------------------------------\n    ipoib_mcast_join_task(work)        | ipoib_ib_dev_flush_light(work)\n      spin_lock_irq(\u0026amp;priv-\u0026gt;lock)       | __ipoib_ib_dev_flush(priv, ...)\n      list_for_each_entry(mcast,       | ipoib_mcast_dev_flush(dev = priv-\u0026gt;dev)\n          \u0026amp;priv-\u0026gt;multicast_list, list) |\n        ipoib_mcast_join(dev, mcast)   |\n          spin_unlock_irq(\u0026amp;priv-\u0026gt;lock) |\n                                       |   spin_lock_irqsave(\u0026amp;priv-\u0026gt;lock, flags)\n                                       |   list_for_each_entry_safe(mcast, tmcast,\n                                       |                  \u0026amp;priv-\u0026gt;multicast_list, list)\n                                       |     list_del(\u0026amp;mcast-\u0026gt;list);\n                                       |     list_add_tail(\u0026amp;mcast-\u0026gt;list, \u0026amp;remove_list)\n                                       |   spin_unlock_irqrestore(\u0026amp;priv-\u0026gt;lock, flags)\n          spin_lock_irq(\u0026amp;priv-\u0026gt;lock)   |\n                                       |   ipoib_mcast_remove_list(\u0026amp;remove_list)\n   (Here, `mcast` is no longer on the  |     list_for_each_entry_safe(mcast, tmcast,\n    `priv-\u0026gt;multicast_list` and we keep |                            remove_list, list)\n    spinning on the `remove_list` of   |  \u0026gt;\u0026gt;\u0026gt;  wait_for_completion(\u0026amp;mcast-\u0026gt;done)\n    the other thread which is blocked  |\n    and the list is still valid on     |\n    it\u0026apos;s stack.)\r\n\r\nFix this by keeping the lock held and changing to GFP_ATOMIC to prevent\neventual sleeps.\nUnfortunately we could not reproduce the lockup and confirm this fix but\nbased on the code review I think this fix should address such lockups.\r\n\r\ncrash\u0026gt; bc 31\nPID: 747      TASK: ff1c6a1a007e8000  CPU: 31   COMMAND: \u0026quot;kworker/u72:2\u0026quot;\n--\n    [exception RIP: ipoib_mcast_join_task+0x1b1]\n    RIP: ffffffffc0944ac1  RSP: ff646f199a8c7e00  RFLAGS: 00000002\n    RAX: 0000000000000000  RBX: ff1c6a1a04dc82f8  RCX: 0000000000000000\n                                  work (\u0026amp;priv-\u0026gt;mcast_task{,.work})\n    RDX: ff1c6a192d60ac68  RSI: 0000000000000286  RDI: ff1c6a1a04dc8000\n           \u0026amp;mcast-\u0026gt;list\n    RBP: ff646f199a8c7e90   R8: ff1c699980019420   R9: ff1c6a1920c9a000\n    R10: ff646f199a8c7e00  R11: ff1c6a191a7d9800  R12: ff1c6a192d60ac00\n                                                         mcast\n    R13: ff1c6a1d82200000  R14: ff1c6a1a04dc8000  R15: ff1c6a1a04dc82d8\n           dev                    priv (\u0026amp;priv-\u0026gt;lock)     \u0026amp;priv-\u0026gt;multicast_list (aka head)\n    ORIG_RAX: ffffffffffffffff  CS: 0010  SS: 0018\n--- \u0026lt;NMI exception stack\u0026gt; ---\n #5 [ff646f199a8c7e00] ipoib_mcast_join_task+0x1b1 at ffffffffc0944ac1 [ib_ipoib]\n #6 [ff646f199a8c7e98] process_one_work+0x1a7 at ffffffff9bf10967\r\n\r\ncrash\u0026gt; rx ff646f199a8c7e68\nff646f199a8c7e68:  ff1c6a1a04dc82f8 \u0026lt;\u0026lt;\u0026lt; work = \u0026amp;priv-\u0026gt;mcast_task.work\r\n\r\ncrash\u0026gt; list -hO ipoib_dev_priv.multicast_list ff1c6a1a04dc8000\n(empty)\r\n\r\ncrash\u0026gt; ipoib_dev_priv.mcast_task.work.func,mcast_mutex.owner.counter ff1c6a1a04dc8000\n  mcast_task.work.func = 0xffffffffc0944910 \u0026lt;ipoib_mcast_join_task\u0026gt;,\n  mcast_mutex.owner.counter = 0xff1c69998efec000\r\n\r\ncrash\u0026gt; b 8\nPID: 8        TASK: ff1c69998efec000  CPU: 33   COMMAND: \u0026quot;kworker/u72:0\u0026quot;\n--\n #3 [ff646f1980153d50] wait_for_completion+0x96 at ffffffff9c7d7646\n #4 [ff646f1980153d90] ipoib_mcast_remove_list+0x56 at ffffffffc0944dc6 [ib_ipoib]\n #5 [ff646f1980153de8] ipoib_mcast_dev_flush+0x1a7 at ffffffffc09455a7 [ib_ipoib]\n #6 [ff646f1980153e58] __ipoib_ib_dev_flush+0x1a4 at ffffffffc09431a4 [ib_ipoib]\n #7 [ff\n---truncated---(CVE-2023-52587)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nwifi: ath9k: Fix potential array-index-out-of-bounds read in ath9k_htc_txstatus()\r\n\r\nFix an array-index-out-of-bounds read in ath9k_htc_txstatus(). The bug\noccurs when txs-\u0026gt;cnt, data from a URB provided by a USB device, is\nbigger than the size of the array txs-\u0026gt;txstatus, which is\nHTC_MAX_TX_STATUS. WARN_ON() already checks it, but there is no bug\nhandling code after the check. Make the function return if that is the\ncase.\r\n\r\nFound by a modified version of syzkaller.\r\n\r\nUBSAN: array-index-out-of-bounds in htc_drv_txrx.c\nindex 13 is out of range for type \u0026apos;__wmi_event_txstatus [12]\u0026apos;\nCall Trace:\n ath9k_htc_txstatus\n ath9k_wmi_event_tasklet\n tasklet_action_common\n __do_softirq\n irq_exit_rxu\n sysvec_apic_timer_interrupt(CVE-2023-52594)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nwifi: rt2x00: restart beacon queue when hardware reset\r\n\r\nWhen a hardware reset is triggered, all registers are reset, so all\nqueues are forced to stop in hardware interface. However, mac80211\nwill not automatically stop the queue. If we don\u0026apos;t manually stop the\nbeacon queue, the queue will be deadlocked and unable to start again.\nThis patch fixes the issue where Apple devices cannot connect to the\nAP after calling ieee80211_restart_hw().(CVE-2023-52595)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nKVM: s390: fix setting of fpc register\r\n\r\nkvm_arch_vcpu_ioctl_set_fpu() allows to set the floating point control\n(fpc) register of a guest cpu. The new value is tested for validity by\ntemporarily loading it into the fpc register.\r\n\r\nThis may lead to corruption of the fpc register of the host process:\nif an interrupt happens while the value is temporarily loaded into the fpc\nregister, and within interrupt context floating point or vector registers\nare used, the current fp/vx registers are saved with save_fpu_regs()\nassuming they belong to user space and will be loaded into fp/vx registers\nwhen returning to user space.\r\n\r\ntest_fp_ctl() restores the original user space / host process fpc register\nvalue, however it will be discarded, when returning to user space.\r\n\r\nIn result the host process will incorrectly continue to run with the value\nthat was supposed to be used for a guest cpu.\r\n\r\nFix this by simply removing the test. There is another test right before\nthe SIE context is entered which will handles invalid values.\r\n\r\nThis results in a change of behaviour: invalid values will now be accepted\ninstead of that the ioctl fails with -EINVAL. This seems to be acceptable,\ngiven that this interface is most likely not used anymore, and this is in\naddition the same behaviour implemented with the memory mapped interface\n(replace invalid values with zero) - see sync_regs() in kvm-s390.c.(CVE-2023-52597)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\ns390/ptrace: handle setting of fpc register correctly\r\n\r\nIf the content of the floating point control (fpc) register of a traced\nprocess is modified with the ptrace interface the new value is tested for\nvalidity by temporarily loading it into the fpc register.\r\n\r\nThis may lead to corruption of the fpc register of the tracing process:\nif an interrupt happens while the value is temporarily loaded into the\nfpc register, and within interrupt context floating point or vector\nregisters are used, the current fp/vx registers are saved with\nsave_fpu_regs() assuming they belong to user space and will be loaded into\nfp/vx registers when returning to user space.\r\n\r\ntest_fp_ctl() restores the original user space fpc register value, however\nit will be discarded, when returning to user space.\r\n\r\nIn result the tracer will incorrectly continue to run with the value that\nwas supposed to be used for the traced process.\r\n\r\nFix this by saving fpu register contents with save_fpu_regs() before using\ntest_fp_ctl().(CVE-2023-52598)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\next4: avoid online resizing failures due to oversized flex bg\r\n\r\nWhen we online resize an ext4 filesystem with a oversized flexbg_size,\r\n\r\n     mkfs.ext4 -F -G 67108864 $dev -b 4096 100M\n     mount $dev $dir\n     resize2fs $dev 16G\r\n\r\nthe following WARN_ON is triggered:\n==================================================================\nWARNING: CPU: 0 PID: 427 at mm/page_alloc.c:4402 __alloc_pages+0x411/0x550\nModules linked in: sg(E)\nCPU: 0 PID: 427 Comm: resize2fs Tainted: G  E  6.6.0-rc5+ #314\nRIP: 0010:__alloc_pages+0x411/0x550\nCall Trace:\n \u0026lt;TASK\u0026gt;\n __kmalloc_large_node+0xa2/0x200\n __kmalloc+0x16e/0x290\n ext4_resize_fs+0x481/0xd80\n __ext4_ioctl+0x1616/0x1d90\n ext4_ioctl+0x12/0x20\n __x64_sys_ioctl+0xf0/0x150\n do_syscall_64+0x3b/0x90\n==================================================================\r\n\r\nThis is because flexbg_size is too large and the size of the new_group_data\narray to be allocated exceeds MAX_ORDER. Currently, the minimum value of\nMAX_ORDER is 8, the minimum value of PAGE_SIZE is 4096, the corresponding\nmaximum number of groups that can be allocated is:\r\n\r\n (PAGE_SIZE \u0026lt;\u0026lt; MAX_ORDER) / sizeof(struct ext4_new_group_data) ≈ 21845\r\n\r\nAnd the value that is down-aligned to the power of 2 is 16384. Therefore,\nthis value is defined as MAX_RESIZE_BG, and the number of groups added\neach time does not exceed this value during resizing, and is added multiple\ntimes to complete the online resizing. The difference is that the metadata\nin a flex_bg may be more dispersed.(CVE-2023-52622)","status":"published","published":"2024-04-19T11:06:55Z","modified":"2026-08-18T01:18:25.302720118Z","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:41.095407Z"},{"id":"RHSA-2024:7000","title":"Red Hat Security Advisory: kernel security update","status":"published","published":"2024-10-02T05:07:40Z","modified":"2026-10-17T10:04:01Z","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:14.610978Z"},{"id":"RHSA-2024:7001","title":"Red Hat Security Advisory: kernel-rt security update","status":"published","published":"2024-10-02T05:07:25Z","modified":"2026-10-17T10:04:02Z","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:14.610978Z"},{"id":"RLSA-2024:7000","title":"Important: kernel security update","description":"The kernel packages contain the Linux kernel, the core of any Linux operating system.  \nSecurity Fix(es):\n\n CVE-2023-6040  CVE-2024-26595  CVE-2024-26600  CVE-2021-46984  CVE-2023-52478  CVE-2023-52476  CVE-2023-52522  CVE-2021-47101  CVE-2021-47097  CVE-2023-52605  CVE-2024-26638  CVE-2024-26645  CVE-2024-26665  CVE-2024-26720  CVE-2024-26717  CVE-2024-26769  CVE-2024-26846  CVE-2024-26894  CVE-2024-26880  CVE-2024-26855  CVE-2024-26923  CVE-2024-26939  CVE-2024-27013  CVE-2024-27042  CVE-2024-35809  CVE-2023-52683  CVE-2024-35884  CVE-2024-35877  CVE-2024-35944  CVE-2024-35989  CVE-2021-47412  CVE-2021-47393  CVE-2021-47386  CVE-2021-47385  CVE-2021-47384  CVE-2021-47383  CVE-2021-47432  CVE-2021-47352  CVE-2021-47338  CVE-2021-47321  CVE-2021-47289  CVE-2021-47287  CVE-2023-52798  CVE-2023-52809  CVE-2023-52817  CVE-2023-52840  CVE-2023-52800  CVE-2021-47441  CVE-2021-47466  CVE-2021-47455  CVE-2021-47497  CVE-2021-47560  CVE-2021-47527  CVE-2024-36883  CVE-2024-36922  CVE-2024-36920  CVE-2024-36902  CVE-2024-36953  CVE-2024-36939  CVE-2024-36919  CVE-2024-36901  CVE-2021-47582  CVE-2021-47609  CVE-2024-38619  CVE-2022-48754  CVE-2022-48760  CVE-2024-38581  CVE-2024-38579  CVE-2024-38570  CVE-2024-38559  CVE-2024-38558  CVE-2024-37356  CVE-2024-39471  CVE-2024-39499  CVE-2024-39501  CVE-2024-39506  CVE-2024-40904  CVE-2024-40911  CVE-2024-40912  CVE-2024-40929  CVE-2024-40931  CVE-2024-40941  CVE-2024-40954  CVE-2024-40958  CVE-2024-40959  CVE-2024-40960  CVE-2024-40972  CVE-2024-40977  CVE-2024-40978  CVE-2024-40988  CVE-2024-40989  CVE-2024-40995  CVE-2024-40997  CVE-2024-40998  CVE-2024-41005  CVE-2024-40901  CVE-2024-41007  CVE-2024-41008  CVE-2022-48804  CVE-2022-48836  CVE-2022-48866  CVE-2024-41090  CVE-2024-41091  CVE-2024-41012  CVE-2024-41013  CVE-2024-41014  CVE-2024-41023  CVE-2024-41035  CVE-2024-41038  CVE-2024-41039  CVE-2024-41040  CVE-2024-41041  CVE-2024-41044  CVE-2024-41055  CVE-2024-41056  CVE-2024-41060  CVE-2024-41064  CVE-2024-41065  CVE-2024-41071  CVE-2024-41076  CVE-2024-41097  CVE-2024-42084  CVE-2024-42090  CVE-2024-42094  CVE-2024-42096  CVE-2024-42114  CVE-2024-42124  CVE-2024-42131  CVE-2024-42152  CVE-2024-42154  CVE-2024-42225  CVE-2024-42226  CVE-2024-42228  CVE-2024-42237  CVE-2024-42238  CVE-2024-42240  CVE-2024-42246  CVE-2024-42322  CVE-2024-43830  CVE-2024-43871  For more details about the security issue(s), including the impact, a CVSS score, acknowledgments, and other related information, refer to the CVE page(s) listed in the References section.","status":"published","published":"2025-05-07T19:11:34.309952Z","modified":"2025-05-07T19:38:05.008508Z","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:24.923365Z"},{"id":"UBUNTU-CVE-2021-46984","description":"In the Linux kernel, the following vulnerability has been resolved: kyber: fix out of bounds access when preempted __blk_mq_sched_bio_merge() gets the ctx and hctx for the current CPU and passes the hctx to -\u003ebio_merge(). kyber_bio_merge() then gets the ctx for the current CPU again and uses that to get the corresponding Kyber context in the passed hctx. However, the thread may be preempted between the two calls to blk_mq_get_ctx(), and the ctx returned the second time may no longer correspond to the passed hctx. This \"works\" accidentally most of the time, but it can cause us to read garbage if the second ctx came from an hctx with more ctx's than the first one (i.e., if ctx-\u003eindex_hw[hctx-\u003etype] \u003e hctx-\u003enr_ctx). This manifested as this UBSAN array index out of bounds error reported by Jakub: UBSAN: array-index-out-of-bounds in ../kernel/locking/qspinlock.c:130:9 index 13106 is out of range for type 'long unsigned int [128]' Call Trace:  dump_stack+0xa4/0xe5  ubsan_epilogue+0x5/0x40  __ubsan_handle_out_of_bounds.cold.13+0x2a/0x34  queued_spin_lock_slowpath+0x476/0x480  do_raw_spin_lock+0x1c2/0x1d0  kyber_bio_merge+0x112/0x180  blk_mq_submit_bio+0x1f5/0x1100  submit_bio_noacct+0x7b0/0x870  submit_bio+0xc2/0x3a0  btrfs_map_bio+0x4f0/0x9d0  btrfs_submit_data_bio+0x24e/0x310  submit_one_bio+0x7f/0xb0  submit_extent_page+0xc4/0x440  __extent_writepage_io+0x2b8/0x5e0  __extent_writepage+0x28d/0x6e0  extent_write_cache_pages+0x4d7/0x7a0  extent_writepages+0xa2/0x110  do_writepages+0x8f/0x180  __writeback_single_inode+0x99/0x7f0  writeback_sb_inodes+0x34e/0x790  __writeback_inodes_wb+0x9e/0x120  wb_writeback+0x4d2/0x660  wb_workfn+0x64d/0xa10  process_one_work+0x53a/0xa80  worker_thread+0x69/0x5b0  kthread+0x20b/0x240  ret_from_fork+0x1f/0x30 Only Kyber uses the hctx, so fix it by passing the request_queue to -\u003ebio_merge() instead. BFQ and mq-deadline just use that, and Kyber can map the queues itself to avoid the mismatch.","status":"published","published":"2024-02-28T09:15:00Z","modified":"2026-11-12T17:22:55.602426774Z","cvss":[{"version":"4.0","score":7.3,"vector":"CVSS:4.0/AV:L/AC:H/AT:P/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N","level":"high"},{"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"},{"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-12T18:02:34.220621Z"},{"id":"ALSA-2024:7000","title":"Important: kernel security update","description":"The kernel packages contain the Linux kernel, the core of any Linux operating system.  \nSecurity Fix(es):\n\n CVE-2023-6040  CVE-2024-26595  CVE-2024-26600  CVE-2021-46984  CVE-2023-52478  CVE-2023-52476  CVE-2023-52522  CVE-2021-47101  CVE-2021-47097  CVE-2023-52605  CVE-2024-26638  CVE-2024-26645  CVE-2024-26665  CVE-2024-26720  CVE-2024-26717  CVE-2024-26769  CVE-2024-26846  CVE-2024-26894  CVE-2024-26880  CVE-2024-26855  CVE-2024-26923  CVE-2024-26939  CVE-2024-27013  CVE-2024-27042  CVE-2024-35809  CVE-2023-52683  CVE-2024-35884  CVE-2024-35877  CVE-2024-35944  CVE-2024-35989  CVE-2021-47412  CVE-2021-47393  CVE-2021-47386  CVE-2021-47385  CVE-2021-47384  CVE-2021-47383  CVE-2021-47432  CVE-2021-47352  CVE-2021-47338  CVE-2021-47321  CVE-2021-47289  CVE-2021-47287  CVE-2023-52798  CVE-2023-52809  CVE-2023-52817  CVE-2023-52840  CVE-2023-52800  CVE-2021-47441  CVE-2021-47466  CVE-2021-47455  CVE-2021-47497  CVE-2021-47560  CVE-2021-47527  CVE-2024-36883  CVE-2024-36922  CVE-2024-36920  CVE-2024-36902  CVE-2024-36953  CVE-2024-36939  CVE-2024-36919  CVE-2024-36901  CVE-2021-47582  CVE-2021-47609  CVE-2024-38619  CVE-2022-48754  CVE-2022-48760  CVE-2024-38581  CVE-2024-38579  CVE-2024-38570  CVE-2024-38559  CVE-2024-38558  CVE-2024-37356  CVE-2024-39471  CVE-2024-39499  CVE-2024-39501  CVE-2024-39506  CVE-2024-40904  CVE-2024-40911  CVE-2024-40912  CVE-2024-40929  CVE-2024-40931  CVE-2024-40941  CVE-2024-40954  CVE-2024-40958  CVE-2024-40959  CVE-2024-40960  CVE-2024-40972  CVE-2024-40977  CVE-2024-40978  CVE-2024-40988  CVE-2024-40989  CVE-2024-40995  CVE-2024-40997  CVE-2024-40998  CVE-2024-41005  CVE-2024-40901  CVE-2024-41007  CVE-2024-41008  CVE-2022-48804  CVE-2022-48836  CVE-2022-48866  CVE-2024-41090  CVE-2024-41091  CVE-2024-41012  CVE-2024-41013  CVE-2024-41014  CVE-2024-41023  CVE-2024-41035  CVE-2024-41038  CVE-2024-41039  CVE-2024-41040  CVE-2024-41041  CVE-2024-41044  CVE-2024-41055  CVE-2024-41056  CVE-2024-41060  CVE-2024-41064  CVE-2024-41065  CVE-2024-41071  CVE-2024-41076  CVE-2024-41097  CVE-2024-42084  CVE-2024-42090  CVE-2024-42094  CVE-2024-42096  CVE-2024-42114  CVE-2024-42124  CVE-2024-42131  CVE-2024-42152  CVE-2024-42154  CVE-2024-42225  CVE-2024-42226  CVE-2024-42228  CVE-2024-42237  CVE-2024-42238  CVE-2024-42240  CVE-2024-42246  CVE-2024-42322  CVE-2024-43830  CVE-2024-43871  For more details about the security issue(s), including the impact, a CVSS score, acknowledgments, and other related information, refer to the CVE page(s) listed in the References section.","status":"published","published":"2024-09-24T00:00:00Z","modified":"2026-10-29T11:12:05.203537698Z","updated_at":"2026-11-02T15:27:53.030731Z"},{"id":"ALSA-2024:7001","title":"Important: kernel-rt security update","description":"The kernel-rt packages provide the Real Time Linux Kernel, which enables fine-tuning for systems with extremely high determinism requirements.  \nSecurity Fix(es):\n\n CVE-2023-6040  CVE-2024-26595  CVE-2021-46984  CVE-2023-52478  CVE-2023-52476  CVE-2023-52522  CVE-2021-47101  CVE-2021-47097  CVE-2023-52605  CVE-2024-26645  CVE-2024-26665  CVE-2024-26720  CVE-2024-26717  CVE-2024-26769  CVE-2024-26894  CVE-2024-26880  CVE-2024-26855  CVE-2024-26923  CVE-2024-26939  CVE-2024-27013  CVE-2024-27042  CVE-2024-35809  CVE-2023-52683  CVE-2024-35884  CVE-2024-35877  CVE-2024-35944  CVE-2024-35989  CVE-2021-47412  CVE-2021-47393  CVE-2021-47386  CVE-2021-47385  CVE-2021-47384  CVE-2021-47383  CVE-2021-47432  CVE-2021-47352  CVE-2021-47338  CVE-2021-47321  CVE-2021-47289  CVE-2021-47287  CVE-2023-52817  CVE-2023-52840  CVE-2021-47441  CVE-2021-47466  CVE-2021-47455  CVE-2021-47497  CVE-2021-47560  CVE-2021-47527  CVE-2024-36883  CVE-2024-36920  CVE-2024-36902  CVE-2024-36953  CVE-2024-36939  CVE-2024-36901  CVE-2021-47582  CVE-2021-47609  CVE-2024-38619  CVE-2022-48754  CVE-2022-48760  CVE-2024-38581  CVE-2024-38570  CVE-2024-38559  CVE-2024-38558  CVE-2024-37356  CVE-2024-39471  CVE-2024-39499  CVE-2024-39501  CVE-2024-39506  CVE-2024-40904  CVE-2024-40911  CVE-2024-40912  CVE-2024-40929  CVE-2024-40931  CVE-2024-40941  CVE-2024-40954  CVE-2024-40958  CVE-2024-40959  CVE-2024-40960  CVE-2024-40972  CVE-2024-40977  CVE-2024-40978  CVE-2024-40988  CVE-2024-40989  CVE-2024-40995  CVE-2024-40997  CVE-2024-40998  CVE-2024-41005  CVE-2024-40901  CVE-2024-41007  CVE-2024-41008  CVE-2022-48804  CVE-2022-48836  CVE-2022-48866  CVE-2024-41090  CVE-2024-41091  CVE-2024-41012  CVE-2024-41013  CVE-2024-41014  CVE-2024-41035  CVE-2024-41038  CVE-2024-41039  CVE-2024-41040  CVE-2024-41041  CVE-2024-41044  CVE-2024-41055  CVE-2024-41056  CVE-2024-41060  CVE-2024-41071  CVE-2024-41076  CVE-2024-41097  CVE-2024-42084  CVE-2024-42090  CVE-2024-42096  CVE-2024-42114  CVE-2024-42124  CVE-2024-42131  CVE-2024-42152  CVE-2024-42154  CVE-2024-42226  CVE-2024-42228  CVE-2024-42237  CVE-2024-42238  CVE-2024-42240  CVE-2024-42246  CVE-2024-42322  CVE-2024-43871  For more details about the security issue(s), including the impact, a CVSS score, acknowledgments, and other related information, refer to the CVE page(s) listed in the References section.","status":"published","published":"2024-09-24T00:00:00Z","modified":"2026-10-29T11:12:09.653003898Z","updated_at":"2026-11-02T15:27:53.030731Z"},{"id":"CLSA-2026-1777614954","title":"kernel: Fix of 39 CVEs","description":"- crypto: algif_aead - Fix minimum RX size check for decryption\n- crypto: af_alg - Fix page reassignment overflow in af_alg_pull_tsgl\n- crypto: authencesn - Fix src offset when decrypting in-place\n- crypto: authencesn - Do not place hiseq at end of dst for out-of-place decryption\n- crypto: authenc - use memcpy_sglist() instead of null skcipher\n- crypto: algif_aead - snapshot IV for async AEAD requests\n- crypto: algif_aead - Revert to operating out-of-place\n- crypto: algif_aead - use memcpy_sglist() instead of null skcipher\n- crypto: scatterwalk - Backport memcpy_sglist()\n- crypto: authencesn - reject too-short AAD (assoclen\u003c8) to match ESP/ESN spec\n- macvlan: fix possible UAF in macvlan_forward_source() {CVE-2026-23001}\n- tls: Use __sk_dst_get() and dst_dev_rcu() in get_netdev_for_sock(). {CVE-2025-40149}\n- bpf, cpumap: Make sure kthread is running before map update returns {CVE-2023-53577}\n- net: qrtr: Fix an uninit variable access bug in qrtr_tx_resume() {CVE-2023-53578}\n- migrate: correct lock ordering for hugetlb file folios {CVE-2026-23097}\n- net/sched: sch_hfsc: upgrade 'rt' to 'sc' when it becomes a inner curve {CVE-2023-4623}\n- e1000e: fix heap overflow in e1000_set_eeprom {CVE-2025-39898}\n- ALSA: hda/ca0132: Fix buffer overflow in add_tuning_control {CVE-2025-39751}\n- md/raid10: fix null-ptr-deref of mreplace in raid10_sync_request {CVE-2023-53380}\n- HID: usbhid: Eliminate recurrent out-of-bounds bug in usbhid_parse() {CVE-2025-38103}\n- tls: separate no-async decryption request handling from async {CVE-2024-58240}\n- ftrace: Also allocate and copy hash for reading of filter files {CVE-2025-39689}\n- HID: uclogic: Correct devm device reference for hidinput input_dev name {CVE-2023-54207}\n- ipv6: BUG() in pskb_expand_head() as part of calipso_skbuff_setattr() {CVE-2025-71085}\n- ALSA: usb-audio: Fix use-after-free in snd_usb_mixer_free() {CVE-2026-23089}\n- nfsd: provide locking for v4_end_grace {CVE-2026-22980}\n- ext4: fix uninititialized value in 'ext4_evict_inode' {CVE-2022-50546}\n- ip_vti: fix potential slab-use-after-free in decode_session6 {CVE-2023-53559}\n- dm flakey: don't corrupt the zero page {CVE-2023-54317}\n- net: add dst_dev_rcu() helper for safe dst-\u003edev access {CVE-2025-40135}\n- xhci: simplify event ring dequeue tracking for transfer events\n- i40e: increase max descriptors for XL710\n- perf/core: Prevent VMA split of buffer mappings {CVE-2025-38563}\n- net/sched: sch_qfq: Avoid triggering might_sleep in atomic context in qfq_delete_class\n- KVM: x86: Reset IRTE to host control if *new* route isn't postable {CVE-2025-37885}\n- ipvlan: add ipvlan_route_v6_outbound() helper {CVE-2023-52796}\n- net: phylink: add lock for serializing concurrent pl-\u003ephydev writes with resolver {CVE-2025-39905}\n- kyber: fix out of bounds access when preempted {CVE-2021-46984}\n- page_pool: Fix use-after-free in page_pool_recycle_in_ring {CVE-2025-38129}\n- scsi: mpi3mr: Use number of bits to manage bitmap sizes {CVE-2023-53376}\n- crypto: lzo - Fix compression buffer overrun {CVE-2025-38068}\n- ipv6: use RCU for dst-\u003edev access in ip6_xmit, ip6_output, ip6_finish_output2 {CVE-2025-40135} {CVE-2025-40158}\n- HID: hyperv: Correctly access fields declared as __le16 {CVE-2025-38103}\n- i40e: add validation for ring_len param {CVE-2025-39973}\n- mmc: core: use sysfs_emit() instead of sprintf() {CVE-2022-49267}\n- cacheinfo: Fix shared_cpu_map to handle shared caches at different levels {CVE-2023-53254}\n- drm/amdkfd: Fix double release compute pasid {CVE-2022-50303}\n- drm/amd/display: Check dce_hwseq before dereferencing it {CVE-2025-38361}\n- RDMA/rxe: Fix mr-\u003emap double free {CVE-2022-50543}\n- virtio-net: ensure the received length does not exceed allocated size {CVE-2025-38375}\n- crypto: qat - resolve race condition during AER recovery {CVE-2024-26974}","status":"published","published":"2026-10-18T04:34:32Z","modified":"2026-10-26T09:31:44.842116954Z","updated_at":"2026-11-02T15:43:44.384419Z"},{"id":"CLSA-2026-1782145985","title":"kernel: Fix of 62 CVEs","description":"- libceph: prevent potential out-of-bounds reads in handle_auth_done() {CVE-2026-22984}\n- drm/i915: Fix NULL ptr deref by checking new_crtc_state {CVE-2023-53833}\n- netfilter: nf_tables: release flowtable after rcu grace period on error {CVE-2026-23392}\n- wifi: brcmfmac: validate bsscfg indices in IF events {CVE-2026-43110}\n- xfrm: hold dev ref until after transport_finish NF_HOOK {CVE-2026-31663}\n- mm: blk-cgroup: fix use-after-free in cgwb_release_workfn() {CVE-2026-31586}\n- scsi: sg: Do not sleep in atomic context {CVE-2025-40259}\n- Bluetooth: L2CAP: Fix use-after-free in l2cap_disconnect_{req,rsp} {CVE-2023-53827}\n- drm/i915/gem: add missing boundary check in vm_access {CVE-2023-28410}\n- ASoC: SOF: debug: Fix potential buffer overflow by snprintf() {CVE-2022-50051}\n- tipc: fix use-after-free Read in tipc_named_reinit {CVE-2022-49696}\n- wifi: mac8021: fix possible oob access in ieee80211_get_rate_duration {CVE-2022-49022}\n- ethtool: do not perform operations on net devices being unregistered {CVE-2021-47517}\n- cxgb4: avoid accessing registers when clearing filters {CVE-2021-47138}\n- bpf: Fix ringbuf helper function compatibility {CVE-2021-34866}\n- HID: wacom: fix out-of-bounds read in wacom_intuos_bt_irq {CVE-2026-43051}\n- Bluetooth: SCO: Fix use-after-free in sco_recv_frame() due to missing sock_hold {CVE-2026-31408}\n- net: usb: cdc_ncm: add ndpoffset to NDP16 nframes bounds check {CVE-2026-23448}\n- nbd: defer config unlock in nbd_genl_connect {CVE-2025-68366}\n- asix: fix uninit-value in asix_mdio_read() {CVE-2021-47101}\n- kyber: fix out of bounds access when preempted {CVE-2021-46984}\n- can: bcm: add locking for bcm_op runtime updates {CVE-2025-38004}\n- tls: separate no-async decryption request handling from async {CVE-2024-58240}\n- ftrace: Also allocate and copy hash for reading of filter files {CVE-2025-39689}\n- Make filldir[64]() verify the directory entry filename is valid {CVE-2019-10220}\n- scsi: qla2xxx: Fix bsg_done() causing double free {CVE-2025-71238}\n- team: fix check for port enabled in team_queue_override_port_prio_changed() {CVE-2025-71091}\n- bonding: limit BOND_MODE_8023AD to Ethernet devices {CVE-2026-23099}\n- Bluetooth: btusb: revert use of devm_kzalloc in btusb {CVE-2025-71082}\n- proc/vmcore: fix clearing user buffer by properly using clear_user() {CVE-2021-47566}\n- nfsd: fix use-after-free due to delegation race {CVE-2021-47506}\n- drm: bridge/panel: Cleanup connector on bridge detach {CVE-2021-47063}\n- usb: class: cdc-wdm: fix reordering issue in read code path {CVE-2026-43427}\n- nfsd: fix heap overflow in NFSv4.0 LOCK replay cache {CVE-2026-31402}\n- ext4: convert inline data to extents when truncate exceeds inline size {CVE-2026-31452}\n- wifi: mac80211: check tdls flag in ieee80211_tdls_oper {CVE-2026-43052}\n- netfilter: nfnetlink_osf: avoid OOB read {CVE-2023-39189}\n- crypto: asymmetric_keys - prevent overflow in asymmetric_key_generate_id {CVE-2025-68724}\n- ALSA: 6fire: fix use-after-free on disconnect {CVE-2026-31581}\n- Bluetooth: btintel: serialize btintel_hw_error() with hci_req_sync_lock {CVE-2026-31500}\n- drm/amdgpu: Fix use-after-free race in VM acquire {CVE-2026-43370}\n- net: use dst_dev_rcu() in sk_setup_caps() {CVE-2025-40170}\n- wifi: brcmfmac: Fix potential stack-out-of-bounds in brcmf_c_preinit_dcmds() {CVE-2022-50258}\n- x86/fpu: Invalidate FPU state after a failed XRSTOR from a user buffer {CVE-2021-47226}\n- kvm: LAPIC: Restore guard to prevent illegal APIC register access {CVE-2021-47255}\n- tunnels: fix kasan splat when generating ipv4 pmtu error {CVE-2023-53600}\n- macvlan: fix error recovery in macvlan_common_newlink() {CVE-2026-23209}\n- ALSA: aloop: Fix racy access at PCM trigger {CVE-2026-23191}\n- RDMA/cxgb4: Do not dma memory off of the stack {CVE-2019-17075}\n- netfilter: nf_conntrack_helper: pass helper to expect cleanup {CVE-2026-43027}\n- KVM: nVMX: unconditionally cancel preemption timer in free_nested (CVE-2019-7221) {CVE-2019-7221}\n- RDMA/umad: Reject negative data_len in ib_umad_write {CVE-2026-23243}\n- netfilter: nf_conntrack_h323: check for zero length in DecodeQ931() {CVE-2026-23455}\n- can: raw: fix ro-\u003euniq use-after-free in raw_rcv() {CVE-2026-31532}\n- can: af_can: export can_sock_destruct()\n- kvm: avoid speculation-based attacks from out-of-range memslot accesses {CVE-2021-47277}\n- Bluetooth: MGMT: validate LTK enc_size on load {CVE-2026-43020}\n- media: dvb-net: fix OOB access in ULE extension header tables {CVE-2026-31405}\n- netfilter: xt_tcpmss: check remaining length before reading optlen {CVE-2026-43190}\n- netfilter: ip6t_eui64: reject invalid MAC header for all packets {CVE-2026-31685}","status":"published","published":"2026-07-07T11:29:05Z","modified":"2026-10-26T09:43:52.493716151Z","updated_at":"2026-11-02T15:43:45.794021Z"},{"id":"CLSA-2026-1788449727","title":"Fix of 235 CVEs","description":"   * Bump kernel ABI to 29: ship the ELS kernel as 4.19.0-29-*, distinct from\n     the prior 4.19.0-28.\n   * CVE-2021-46984\n     - kyber: fix out of bounds access when preempted {CVE-2021-46984}\n   * CVE-2021-47049\n     - Drivers: hv: vmbus: Use after free in __vmbus_open()\n       {CVE-2021-47049}\n   * CVE-2021-47101\n     - asix: fix uninit-value in asix_mdio_read() {CVE-2021-47101}\n   * CVE-2021-47191\n     - scsi: scsi_debug: Fix out-of-bound read in resp_readcap16()\n       {CVE-2021-47191}\n   * CVE-2021-47352\n     - virtio-net: Add validation for used length {CVE-2021-47352}\n   * CVE-2021-47379\n     - blk-cgroup: fix UAF by grabbing blkcg lock before destroying blkg\n       pd {CVE-2021-47379}\n   * CVE-2021-47391\n     - RDMA/cma: Ensure rdma_addr_cancel() happens before issuing more\n       requests {CVE-2021-47391}\n   * CVE-2021-47479\n     - staging: rtl8712: fix use-after-free in rtl8712_dl_fw\n       {CVE-2021-47479}\n   * CVE-2022-21546\n     - scsi: target: Fix WRITE_SAME No Data Buffer crash {CVE-2022-21546}\n   * CVE-2022-39189\n     - KVM: x86: do not report a vCPU as preempted outside instruction\n       boundaries {CVE-2022-39189}\n   * CVE-2022-43945\n     - SUNRPC: Fix svcxdr_init_encode's buflen calculation\n       {CVE-2022-43945}\n     - NFSD: Cap rsize_bop result based on send buffer size\n       {CVE-2022-43945}\n   * CVE-2022-48744\n     - net/mlx5e: Avoid field-overflowing memcpy() {CVE-2022-48744}\n   * CVE-2022-49026\n     - e100: Fix possible use after free in e100_xmit_prepare\n       {CVE-2022-49026}\n   * CVE-2022-49720\n     - block: Fix handling of offline queues in\n       blk_mq_alloc_request_hctx() {CVE-2022-49720}\n   * CVE-2022-49975\n     - bpf: Don't redirect packets with invalid pkt_len {CVE-2022-49975}\n     - bpf: Move skb-\u003elen == 0 checks into __bpf_redirect\n       {CVE-2022-49975}\n   * CVE-2022-50066\n     - net: atlantic: fix aq_vec index out of range error\n       {CVE-2022-50066}\n   * CVE-2022-50103\n     - sched, cpuset: Fix dl_cpu_busy() panic due to empty\n       cs-\u003ecpus_allowed {CVE-2022-50103}\n   * CVE-2022-50129\n     - RDMA/srpt: Introduce a reference count in struct srpt_device\n       {CVE-2022-50129}\n     - RDMA/srpt: Fix a use-after-free {CVE-2022-50129}\n   * CVE-2022-50300\n     - btrfs: fix extent map use-after-free when handling missing device\n       in read_one_chunk {CVE-2022-50300}\n   * CVE-2022-50406\n     - iomap: iomap: fix memory corruption when recording errors during\n       writeback {CVE-2022-50406}\n   * CVE-2022-50422\n     - scsi: libsas: Fix use-after-free bug in smp_execute_task_sg()\n       {CVE-2022-50422}\n   * CVE-2022-50552\n     - blk-mq: use quiesced elevator switch when reinitializing queues\n       {CVE-2022-50552}\n   * CVE-2023-51779\n     - Bluetooth: af_bluetooth: Fix Use-After-Free in bt_sock_recvmsg\n       {CVE-2023-51779}\n   * CVE-2023-52434\n     - smb: client: fix potential OOBs in smb2_parse_contexts()\n       {CVE-2023-52434}\n   * CVE-2023-52515\n     - RDMA/srp: Do not call scsi_done() from srp_abort()\n       {CVE-2023-52515}\n   * CVE-2023-52531\n     - wifi: iwlwifi: mvm: Fix a memory corruption issue {CVE-2023-52531}\n   * CVE-2023-52741\n     - cifs: Fix use-after-free in rdata-\u003eread_into_pages()\n       {CVE-2023-52741}\n   * CVE-2023-53000\n     - netlink: prevent potential spectre v1 gadgets {CVE-2023-53000}\n   * CVE-2023-53039\n     - workqueue: Add resource managed version of delayed work init\n       {CVE-2023-53039}\n     - devm-helpers: Fix devm_delayed_work_autocancel() kerneldoc\n       {CVE-2023-53039}\n     - devm-helpers: Add resource managed version of work init\n       {CVE-2023-53039}\n     - HID: intel-ish-hid: ipc: Fix potential use-after-free in work\n       function {CVE-2023-53039}\n     - HID: intel-ish-hid: ipc: Fix dev_err usage with uninitialized\n       dev-\u003edevc {CVE-2023-53039}\n   * CVE-2023-53111\n     - loop: Fix use-after-free issues {CVE-2023-53111}\n   * CVE-2023-53254\n     - cacheinfo: Fix shared_cpu_map to handle shared caches at different\n       levels {CVE-2023-53254}\n   * CVE-2023-53259\n     - VMCI: check context-\u003enotify_page after call to\n       get_user_pages_fast() to avoid GPF {CVE-2023-53259}\n   * CVE-2023-53282\n     - scsi: lpfc: Fix use-after-free KFENCE violation during sysfs\n       firmware write {CVE-2023-53282}\n   * CVE-2023-53321\n     - wifi: mac80211_hwsim: drop short frames {CVE-2023-53321}\n   * CVE-2023-53333\n     - netfilter: conntrack: dccp: copy entire header to stack buffer,\n       not just basic one {CVE-2023-53333}\n     - netfilter: conntrack: dccp: try not to drop skb in conntrack\n       {CVE-2023-53333}\n   * CVE-2023-53432\n     - firewire: net: fix use after free in\n       fwnet_finish_incoming_packet() {CVE-2023-53432}\n   * CVE-2023-53510\n     - scsi: ufs: core: Fix handling of lrbp-\u003ecmd {CVE-2023-53510}\n   * CVE-2023-53577\n     - bpf, cpumap: Make sure kthread is running before map update\n       returns {CVE-2023-53577}\n   * CVE-2023-53680\n     - NFSD: Avoid calling OPDESC() with ops-\u003eopnum == OP_ILLEGAL\n       {CVE-2023-53680}\n   * CVE-2024-26689\n     - ceph: prevent use-after-free in encode_cap_msg() {CVE-2024-26689}\n   * CVE-2024-26828\n     - cifs: fix underflow in parse_server_interfaces() {CVE-2024-26828}\n   * CVE-2024-26996\n     - usb: gadget: f_ncm: Fix UAF ncm object at re-bind after usb ep\n       transport error {CVE-2024-26996}\n   * CVE-2024-35791\n     - KVM: SVM: Flush pages under kvm-\u003elock to fix UAF in\n       svm_register_enc_region() {CVE-2024-35791}\n   * CVE-2024-35864\n     - smb: client: fix potential UAF in smb2_is_valid_lease_break()\n       {CVE-2024-35864}\n   * CVE-2024-35932\n     - drm/vc4: don't check if plane-\u003estate-\u003efb == state-\u003efb\n       {CVE-2024-35932}\n   * CVE-2024-38545\n     - RDMA/hns: Fix UAF for cq async event {CVE-2024-38545}\n   * CVE-2024-38588\n     - ftrace: Fix possible use-after-free issue in ftrace_location()\n       {CVE-2024-38588}\n   * CVE-2024-40929\n     - wifi: iwlwifi: mvm: check n_ssids before accessing the ssids\n       {CVE-2024-40929}\n   * CVE-2024-41013\n     - xfs: don't walk off the end of a directory data block\n       {CVE-2024-41013}\n   * CVE-2024-42120\n     - drm/amd/display: Check pipe offset before setting vblank\n       {CVE-2024-42120}\n   * CVE-2024-46731\n     - drm/amd/pm: fix the Out-of-bounds read warning {CVE-2024-46731}\n   * CVE-2024-46813\n     - drm/amd/display: Check link_index before accessing dc-\u003elinks[]\n       {CVE-2024-46813}\n   * CVE-2024-46818\n     - drm/amd/display: Check gpio_id before used as array index\n       {CVE-2024-46818}\n   * CVE-2024-46826\n     - ELF: fix kernel.randomize_va_space double read {CVE-2024-46826}\n   * CVE-2024-46859\n     - platform/x86: panasonic-laptop: Fix sticky key init bug\n       {CVE-2024-46859}\n     - platform/x86: panasonic-laptop: Fix SINF array out of bounds\n       accesses {CVE-2024-46859}\n   * CVE-2024-49991\n     - drm/amdkfd: amdkfd_free_gtt_mem clear the correct pointer\n       {CVE-2024-49991}\n   * CVE-2024-50036\n     - net: do not delay dst_entries_add() in dst_release()\n       {CVE-2024-50036}\n   * CVE-2024-50067\n     - uprobe: avoid out-of-bounds memory access of fetching args\n       {CVE-2024-50067}\n   * CVE-2024-50073\n     - tty: n_gsm: Fix use-after-free in gsm_cleanup_mux {CVE-2024-50073}\n   * CVE-2024-50256\n     - netfilter: nf_reject_ipv6: fix potential crash in nf_send_reset6()\n       {CVE-2024-50256}\n   * CVE-2024-53090\n     - afs: Fix lock recursion {CVE-2024-53090}\n   * CVE-2024-53124\n     - net: fix data-races around sk-\u003esk_forward_alloc {CVE-2024-53124}\n   * CVE-2024-56593\n     - wifi: brcmfmac: Fix oops due to NULL pointer dereference in\n       brcmf_sdiod_sglist_rw() {CVE-2024-56593}\n   * CVE-2024-56602\n     - net: ieee802154: do not leave a dangling sk pointer in\n       ieee802154_create() {CVE-2024-56602}\n   * CVE-2024-56603\n     - net: af_can: do not leave a dangling sk pointer in can_create()\n       {CVE-2024-56603}\n   * CVE-2024-56606\n     - af_packet: avoid erroring out after sock_init_data() in\n       packet_create() {CVE-2024-56606}\n   * CVE-2024-56631\n     - scsi: sg: Fix slab-use-after-free read in sg_release()\n       {CVE-2024-56631}\n   * CVE-2024-56640\n     - net/smc: fix LGR and link use-after-free issue {CVE-2024-56640}\n   * CVE-2024-56650\n     - netfilter: x_tables: fix LED ID check in led_tg_check()\n       {CVE-2024-56650}\n   * CVE-2024-56658\n     - net: defer final 'struct net' free in netns dismantle\n       {CVE-2024-56658}\n   * CVE-2024-56748\n     - scsi: qedf: Fix a possible memory leak in qedf_alloc_and_init_sb()\n       {CVE-2024-56748}\n   * CVE-2024-56756\n     - nvme-pci: fix freeing of the HMB descriptor table {CVE-2024-56756}\n   * CVE-2024-57901\n     - af_packet: fix vlan_get_protocol_dgram() vs MSG_PEEK\n       {CVE-2024-57901}\n   * CVE-2024-58072\n     - wifi: rtlwifi: remove unused check_buddy_priv {CVE-2024-58072}\n   * CVE-2025-21749\n     - net: rose: add missing dev_put() on error in rose_bind\n       {CVE-2025-21749}\n   * CVE-2025-21858\n     - geneve: Fix use-after-free in geneve_find_dev(). {CVE-2025-21858}\n   * CVE-2025-22022\n     - usb: xhci: move link chain bit quirk checks into one helper\n       function. {CVE-2025-22022}\n     - usb: xhci: Apply the link chain quirk on NEC isoc endpoints\n       {CVE-2025-22022}\n     - usb: xhci: Don't unchain link TRBs on quirky HCs {CVE-2025-22022}\n   * CVE-2025-22083\n     - vhost-scsi: Fix handling of multiple calls to\n       vhost_scsi_set_endpoint {CVE-2025-22083}\n   * CVE-2025-22121\n     - ext4: introduce ITAIL helper {CVE-2025-22121}\n     - ext4: fix out-of-bound read in ext4_xattr_inode_dec_ref_all()\n       {CVE-2025-22121}\n   * CVE-2025-23156\n     - media: venus: hfi_parser: refactor hfi packet parsing logic\n       {CVE-2025-23156}\n   * CVE-2025-23157\n     - media: venus: hfi_parser: add check to avoid out of bound access\n       {CVE-2025-23157}\n   * CVE-2025-23158\n     - media: venus: hfi: add check to handle incorrect queue size\n       {CVE-2025-23158}\n   * CVE-2025-37796\n     - wifi: at76c50x: fix use after free access in at76_disconnect\n       {CVE-2025-37796}\n   * CVE-2025-37798\n     - codel: remove sch-\u003eq.qlen check before qdisc_tree_reduce_backlog()\n       {CVE-2025-37798}\n   * CVE-2025-37839\n     - jbd2: remove wrong sb-\u003es_sequence check {CVE-2025-37839}\n   * CVE-2025-37879\n     - 9p/net: fix improper handling of bogus negative read/write replies\n       {CVE-2025-37879}\n   * CVE-2025-37882\n     - usb: xhci: Fix isochronous Ring Underrun/Overrun event handling\n       {CVE-2025-37882}\n   * CVE-2025-37923\n     - tracing: Fix oob write in trace_seq_to_buffer() {CVE-2025-37923}\n     - tracing: Fix compilation warning on arm32 {CVE-2025-37923}\n   * CVE-2025-37927\n     - iommu/amd: Fix potential buffer overflow in parse_ivrs_acpihid\n       {CVE-2025-37927}\n   * CVE-2025-37932\n     - sch_htb: make htb_qlen_notify() idempotent {CVE-2025-37932}\n   * CVE-2025-37953\n     - sch_htb: make htb_deactivate() idempotent {CVE-2025-37953}\n   * CVE-2025-38000\n     - sch_hfsc: Fix qlen accounting bug when using peek in\n       hfsc_enqueue() {CVE-2025-38000}\n   * CVE-2025-38024\n     - RDMA/rxe: Zero out index member of struct rxe_queue\n       {CVE-2025-38024}\n     - RDMA/rxe: Fix slab-use-after-free Read in rxe_queue_cleanup bug\n       {CVE-2025-38024}\n   * CVE-2025-38068\n     - crypto: lzo - Fix compression buffer overrun {CVE-2025-38068}\n   * CVE-2025-38079\n     - crypto: algif_hash - fix double free in hash_accept\n       {CVE-2025-38079}\n   * CVE-2025-38102\n     - VMCI: fix race between vmci_host_setup_notify and\n       vmci_ctx_unset_notify {CVE-2025-38102}\n   * CVE-2025-38103\n     - HID: usbhid: Eliminate recurrent out-of-bounds bug in\n       usbhid_parse() {CVE-2025-38103}\n     - HID: usbhid: paper over wrong bNumDescriptor field\n       {CVE-2025-38103}\n   * CVE-2025-38157\n     - wifi: ath9k_htc: Abort software beacon handling if disabled\n       {CVE-2025-38157}\n   * CVE-2025-38211\n     - RDMA/iwcm: Fix use-after-free of work objects after cm_id\n       destruction {CVE-2025-38211}\n   * CVE-2025-38212\n     - ipc: fix to protect IPCS lookups using RCU {CVE-2025-38212}\n   * CVE-2025-38348\n     - wifi: p54: prevent buffer-overflow in p54_rx_eeprom_readback()\n       {CVE-2025-38348}\n   * CVE-2025-38350\n     - sch_drr: make drr_qlen_notify() idempotent {CVE-2025-38350}\n     - sch_qfq: make qfq_qlen_notify() idempotent {CVE-2025-38350}\n     - net/sched: Always pass notifications when child class becomes\n       empty {CVE-2025-38350}\n   * CVE-2025-38375\n     - virtio-net: ensure the received length does not exceed allocated\n       size {CVE-2025-38375}\n   * CVE-2025-38403\n     - vsock/vmci: Clear the vmci transport packet properly when\n       initializing it {CVE-2025-38403}\n   * CVE-2025-38445\n     - md/raid1: Fix stack memory use after return in raid1_reshape\n       {CVE-2025-38445}\n   * CVE-2025-38494\n     - HID: core: do not bypass hid_hw_raw_request {CVE-2025-38494}\n   * CVE-2025-38497\n     - usb: gadget: configfs: Fix OOB read on empty string write\n       {CVE-2025-38497}\n   * CVE-2025-38563\n     - perf/core: Prevent VMA split of buffer mappings {CVE-2025-38563}\n   * CVE-2025-38565\n     - perf/core: Exit early on perf_mmap() fail {CVE-2025-38565}\n   * CVE-2025-38572\n     - ipv6: reject malicious packets in ipv6_gso_segment()\n       {CVE-2025-38572}\n   * CVE-2025-38618\n     - vsock: Do not allow binding to VMADDR_PORT_ANY {CVE-2025-38618}\n   * CVE-2025-38652\n     - f2fs: fix to avoid out-of-boundary access in devs.path\n       {CVE-2025-38652}\n   * CVE-2025-38679\n     - media: venus: Fix OOB read due to missing payload bound check\n       {CVE-2025-38679}\n   * CVE-2025-38708\n     - drbd: add missing kref_get in handle_write_conflicts\n       {CVE-2025-38708}\n   * CVE-2025-38718\n     - sctp: linearize cloned gso packets in sctp_rcv {CVE-2025-38718}\n   * CVE-2025-38728\n     - smb3: fix for slab out of bounds on mount to ksmbd\n       {CVE-2025-38728}\n   * CVE-2025-38729\n     - ALSA: usb-audio: Validate UAC3 power domain descriptors, too\n       {CVE-2025-38729}\n   * CVE-2025-39684\n     - comedi: Fix use of uninitialized memory in do_insn_ioctl() and\n       do_insnlist_ioctl() {CVE-2025-39684}\n   * CVE-2025-39686\n     - comedi: Make insn_rw_emulate_bits() do insn-\u003en samples\n       {CVE-2025-39686}\n   * CVE-2025-39689\n     - ftrace: Also allocate and copy hash for reading of filter files\n       {CVE-2025-39689}\n   * CVE-2025-39702\n     - ipv6: sr: Fix MAC comparison to be constant-time {CVE-2025-39702}\n   * CVE-2025-39730\n     - NFS: Fix filehandle bounds checking in nfs_fh_to_dentry()\n       {CVE-2025-39730}\n   * CVE-2025-39760\n     - usb: core: config: Prevent OOB read in SS endpoint companion\n       parsing {CVE-2025-39760}\n     - usb: core: config: reverse the size check of the SSP isoc endpoint\n       descriptor {CVE-2025-39760}\n   * CVE-2025-39817\n     - efivarfs: Fix slab-out-of-bounds in efivarfs_d_compare\n       {CVE-2025-39817}\n   * CVE-2025-39823\n     - KVM: x86: use array_index_nospec with indices that come from guest\n       {CVE-2025-39823}\n     - KVM: X86: Fix array_index_nospec protection in __pv_send_ipi\n       {CVE-2025-39823}\n   * CVE-2025-39824\n     - HID: asus: fix UAF via HID_CLAIMED_INPUT validation\n       {CVE-2025-39824}\n   * CVE-2025-39839\n     - batman-adv: fix OOB read/write in network-coding decode\n       {CVE-2025-39839}\n   * CVE-2025-39853\n     - i40e: Fix potential invalid access when MAC list is empty\n       {CVE-2025-39853}\n   * CVE-2025-39863\n     - wifi: brcmfmac: fix use-after-free when rescheduling\n       brcmf_btcoex_info work {CVE-2025-39863}\n   * CVE-2025-39891\n     - wifi: mwifiex: Initialize the chan_stats array to zero\n       {CVE-2025-39891}\n   * CVE-2025-39901\n     - i40e: remove read access to debugfs files {CVE-2025-39901}\n   * CVE-2025-39911\n     - i40e: fix IRQ freeing in i40e_vsi_request_irq_msix error path\n       {CVE-2025-39911}\n   * CVE-2025-39955\n     - tcp: Clear tcp_sk(sk)-\u003efastopen_rsk in tcp_disconnect().\n       {CVE-2025-39955}\n   * CVE-2025-40186\n     - tcp: Don't call reqsk_fastopen_remove() in tcp_conn_request().\n       {CVE-2025-40186}\n   * CVE-2025-68305\n     - Bluetooth: hci_sock: Prevent race in socket write iter and sock\n       bind {CVE-2025-68305}\n   * CVE-2025-71075\n     - scsi: aic94xx: fix use-after-free in device removal path\n       {CVE-2025-71075}\n   * CVE-2025-71082\n     - Bluetooth: btusb: revert use of devm_kzalloc in btusb\n       {CVE-2025-71082}\n   * CVE-2025-71091\n     - team: fix check for port enabled in\n       team_queue_override_port_prio_changed() {CVE-2025-71091}\n   * CVE-2025-71093\n     - e1000: fix OOB in e1000_tbi_should_accept() {CVE-2025-71093}\n   * CVE-2025-71116\n     - libceph: make decode_pool() more resilient against corrupted\n       osdmaps {CVE-2025-71116}\n   * CVE-2026-22980\n     - nfsd: provide locking for v4_end_grace {CVE-2026-22980}\n   * CVE-2026-23001\n     - macvlan: fix possible UAF in macvlan_forward_source()\n       {CVE-2026-23001}\n   * CVE-2026-23073\n     - wifi: rsi: Fix memory corruption due to not set vif driver data\n       size {CVE-2026-23073}\n   * CVE-2026-23076\n     - ALSA: ctxfi: Fix potential OOB access in audio mixer handling\n       {CVE-2026-23076}\n   * CVE-2026-23083\n     - fou: Don't allow 0 for FOU_ATTR_IPPROTO. {CVE-2026-23083}\n   * CVE-2026-23089\n     - ALSA: usb-audio: Fix use-after-free in snd_usb_mixer_free()\n       {CVE-2026-23089}\n   * CVE-2026-23099\n     - bonding: limit BOND_MODE_8023AD to Ethernet devices\n       {CVE-2026-23099}\n   * CVE-2026-23191\n     - ALSA: aloop: Fix racy access at PCM trigger {CVE-2026-23191}\n   * CVE-2026-23193\n     - scsi: target: iscsi: Fix use-after-free in\n       iscsit_dec_session_usage_count() {CVE-2026-23193}\n   * CVE-2026-23204\n     - net: add skb_header_pointer_careful() helper {CVE-2026-23204}\n     - net/sched: cls_u32: use skb_header_pointer_careful()\n       {CVE-2026-23204}\n   * CVE-2026-23216\n     - scsi: target: iscsi: Fix use-after-free in\n       iscsit_dec_conn_usage_count() {CVE-2026-23216}\n   * CVE-2026-23231\n     - netfilter: nf_tables: fix use-after-free in nf_tables_addchain()\n       {CVE-2026-23231}\n   * CVE-2026-23235\n     - f2fs: fix out-of-bounds access in sysfs attribute read/write\n       {CVE-2026-23235}\n   * CVE-2026-23243\n     - RDMA/umad: Reject negative data_len in ib_umad_write\n       {CVE-2026-23243}\n   * CVE-2026-23273\n     - macvlan: observe an RCU grace period in macvlan_common_newlink()\n       error path {CVE-2026-23273}\n   * CVE-2026-23281\n     - wifi: libertas: fix use-after-free in lbs_free_adapter()\n       {CVE-2026-23281}\n   * CVE-2026-23372\n     - nfc: rawsock: cancel tx_work before socket teardown\n       {CVE-2026-23372}\n   * CVE-2026-23378\n     - net/sched: act_ife: Fix metalist update behavior {CVE-2026-23378}\n   * CVE-2026-23388\n     - Squashfs: check metadata block offset is within range\n       {CVE-2026-23388}\n   * CVE-2026-23406\n     - apparmor: fix side-effect bug in match_char() macro usage\n       {CVE-2026-23406}\n   * CVE-2026-23447\n     - net: usb: cdc_ncm: add ndpoffset to NDP32 nframes bounds check\n       {CVE-2026-23447}\n   * CVE-2026-23448\n     - net: usb: cdc_ncm: add ndpoffset to NDP16 nframes bounds check\n       {CVE-2026-23448}\n   * CVE-2026-31396\n     - net: macb: fix use-after-free access to PTP clock {CVE-2026-31396}\n   * CVE-2026-31399\n     - nvdimm/bus: Fix potential use after free in asynchronous\n       initialization {CVE-2026-31399}\n   * CVE-2026-31452\n     - ext4: convert inline data to extents when truncate exceeds inline\n       size {CVE-2026-31452}\n   * CVE-2026-31494\n     - net: macb: use the current queue number for stats {CVE-2026-31494}\n   * CVE-2026-31500\n     - Bluetooth: btintel: serialize btintel_hw_error() with\n       hci_req_sync_lock {CVE-2026-31500}\n   * CVE-2026-31532\n     - can: raw: fix ro-\u003euniq use-after-free in raw_rcv()\n       {CVE-2026-31532}\n   * CVE-2026-31576\n     - media: hackrf: fix to not free memory after the device is\n       registered in hackrf_probe() {CVE-2026-31576}\n   * CVE-2026-31581\n     - ALSA: 6fire: fix use-after-free on disconnect {CVE-2026-31581}\n   * CVE-2026-31597\n     - ocfs2: fix use-after-free in ocfs2_fault() when VM_FAULT_RETRY\n       {CVE-2026-31597}\n   * CVE-2026-31602\n     - ALSA: ctxfi: Limit PTP to a single page {CVE-2026-31602}\n   * CVE-2026-31622\n     - NFC: digital: Bounds check NFC-A cascade depth in SDD response\n       handler {CVE-2026-31622}\n   * CVE-2026-31626\n     - staging: rtl8723bs: initialize le_tmp64 in rtw_BIP_verify()\n       {CVE-2026-31626}\n   * CVE-2026-31627\n     - i2c: s3c24xx: check the size of the SMBUS message before using it\n       {CVE-2026-31627}\n   * CVE-2026-31629\n     - nfc: llcp: add missing return after LLCP_CLOSED checks\n       {CVE-2026-31629}\n   * CVE-2026-31659\n     - batman-adv: reject oversized global TT response buffers\n       {CVE-2026-31659}\n   * CVE-2026-31696\n     - rxrpc: Fix missing validation of ticket length in non-XDR key\n       preparsing {CVE-2026-31696}\n   * CVE-2026-31747\n     - comedi: me4000: Fix potential overrun of firmware buffer\n       {CVE-2026-31747}\n   * CVE-2026-31748\n     - comedi: me_daq: Fix potential overrun of firmware buffer\n       {CVE-2026-31748}\n   * CVE-2026-31778\n     - ALSA: caiaq: fix stack out-of-bounds read in init_card\n       {CVE-2026-31778}\n   * CVE-2026-31787\n     - xen/privcmd: fix double free via VMA splitting {CVE-2026-31787}\n   * CVE-2026-43020\n     - Bluetooth: MGMT: validate LTK enc_size on load {CVE-2026-43020}\n   * CVE-2026-43027\n     - netfilter: nf_conntrack_helper: pass helper to expect cleanup\n       {CVE-2026-43027}\n   * CVE-2026-43040\n     - net: ipv6: ndisc: fix ndisc_ra_useropt to initialize\n       nduseropt_padX fields to zero to prevent an info-leak\n       {CVE-2026-43040}\n   * CVE-2026-43052\n     - wifi: mac80211: check tdls flag in ieee80211_tdls_oper\n       {CVE-2026-43052}\n   * CVE-2026-43075\n     - ocfs2: fix out-of-bounds write in ocfs2_write_end_inline\n       {CVE-2026-43075}\n   * CVE-2026-43076\n     - ocfs2: validate inline data i_size during inode read\n       {CVE-2026-43076}\n   * CVE-2026-43198\n     - tcp: fix potential race in tcp_v6_syn_recv_sock() {CVE-2026-43198}\n   * CVE-2026-43206\n     - drm/amdkfd: Fix out-of-bounds write in kfd_event_page_set()\n       {CVE-2026-43206}\n   * CVE-2026-43279\n     - ALSA: usb-audio: Add sanity check for OOB writes at silencing\n       {CVE-2026-43279}\n   * CVE-2026-43281\n     - mailbox: Prevent out-of-bounds access in fw_mbox_index_xlate()\n       {CVE-2026-43281}\n   * CVE-2026-43370\n     - drm/amdgpu: Fix use-after-free race in VM acquire {CVE-2026-43370}\n   * CVE-2026-43386\n     - staging: rtl8723bs: fix potential out-of-bounds read in\n       rtw_restruct_wmm_ie {CVE-2026-43386}\n   * CVE-2026-43427\n     - usb: class: cdc-wdm: fix reordering issue in read code path\n       {CVE-2026-43427}\n   * CVE-2026-43450\n     - netfilter: nfnetlink_cthelper: fix OOB read in\n       nfnl_cthelper_dump_table() {CVE-2026-43450}\n   * CVE-2026-43494\n     - net/rds: reset op_nents when zerocopy page pin fails\n       {CVE-2026-43494}\n   * CVE-2026-45893\n     - apparmor: Fix \u0026 Optimize table creation from possibly unaligned\n       memory {CVE-2026-45893}\n   * CVE-2026-46006\n     - drm/nouveau: fix u32 overflow in pushbuf reloc bounds check\n       {CVE-2026-46006}\n   * CVE-2026-46022\n     - misc: ibmasm: fix OOB MMIO read in ibmasm_handle_mouse_interrupt()\n       {CVE-2026-46022}\n   * CVE-2026-46033\n     - crypto: authencesn - reject short ahash digests during instance\n       creation {CVE-2026-46033}\n   * CVE-2026-46069\n     - wifi: mwifiex: fix use-after-free in mwifiex_adapter_cleanup()\n       {CVE-2026-46069}\n   * CVE-2026-46116\n     - xfrm: defensively unhash xfrm_state lists in __xfrm_state_delete\n       {CVE-2026-46116}\n   * CVE-2026-46150\n     - fanotify: fix false positive on permission events {CVE-2026-46150}\n   * CVE-2026-46191\n     - fbcon: Avoid OOB font access if console rotation fails\n       {CVE-2026-46191}\n   * CVE-2026-46208\n     - batman-adv: stop tp_meter sessions during mesh teardown\n       {CVE-2026-46208}\n   * CVE-2026-46209\n     - drm/gem: Fix inconsistent plane dimension calculation in\n       drm_gem_fb_init_with_funcs() {CVE-2026-46209}\n   * CVE-2026-46218\n     - drm/amdgpu: Add bounds checking to ib_{get,set}_value\n       {CVE-2026-46218}\n   * CVE-2026-46254\n     - AppArmor: Allow apparmor to handle unaligned dfa tables\n       {CVE-2026-46254}\n   * CVE-2026-46259\n     - procfs: fix missing RCU protection when reading real_parent in\n       do_task_stat() {CVE-2026-46259}\n   * CVE-2026-46333\n     - ptrace: slightly saner 'get_dumpable()' logic {CVE-2026-46333}\n   * CVE-2026-52934\n     - batman-adv: tvlv: reject oversized TVLV packets {CVE-2026-52934}\n   * CVE-2026-53009\n     - ice: fix double-free of tx_buf skb {CVE-2026-53009}\n   * CVE-2026-53036\n     - bpf, arm64: Fix off-by-one in check_imm signed range check\n       {CVE-2026-53036}\n   * CVE-2026-53040\n     - ocfs2: validate bg_bits during freefrag scan {CVE-2026-53040}\n   * CVE-2026-53075\n     - ppp: require CAP_NET_ADMIN in target netns for unattached ioctls\n       {CVE-2026-53075}\n   * CVE-2026-53091\n     - net: pull headers in qdisc_pkt_len_segs_init() {CVE-2026-53091}\n   * CVE-2026-53130\n     - fs/omfs: reject s_sys_blocksize smaller than OMFS_DIR_START\n       {CVE-2026-53130}\n   * CVE-2026-53136\n     - drm/amd/display: Clamp VBIOS HDMI retimer register count to array\n       size {CVE-2026-53136}\n   * CVE-2026-53138\n     - drm/amd/display: Bound VBIOS record-chain walk loops\n       {CVE-2026-53138}\n   * CVE-2026-53186\n     - RDMA/srp: bound SRP_RSP sense copy by the received length\n       {CVE-2026-53186}\n   * CVE-2026-53189\n     - mm/huge_memory: update file PMD counter before folio_put()\n       {CVE-2026-53189}\n   * CVE-2026-53224\n     - sctp: validate embedded INIT chunk and address list lengths in\n       cookie {CVE-2026-53224}\n   * CVE-2026-53228\n     - ipv6: sit: reload inner IPv6 header after GSO offloads\n       {CVE-2026-53228}\n   * CVE-2026-53246\n     - sctp: validate cached peer INIT chunk length in COOKIE_ECHO\n       processing {CVE-2026-53246}\n   * CVE-2026-53264\n     - net/sched: act_api: use RCU with deferred freeing for action\n       lifecycle {CVE-2026-53264}\n   * CVE-2026-53270\n     - ipvs: clear the svc scheduler ptr early on edit {CVE-2026-53270}\n   * CVE-2026-53303\n     - f2fs: protect extension_list reading with sb_lock in\n       f2fs_sbi_show() {CVE-2026-53303}\n   * CVE-2026-64567\n     - btrfs: reject free space cache with more entries than pages\n       {CVE-2026-64567}\n   * CVE-2026-64571\n     - wifi: p54: validate RX frame length in p54_rx_eeprom_readback()\n       {CVE-2026-64571}\n   * CVE-2026-64580\n     - xfrm6: clear dst.dev on error to avoid double netdev_put in\n       xfrm6_fill_dst() {CVE-2026-64580}\n   * CVE-2026-64581\n     - xfrm: fix sk_dst_cache double-free in xfrm_user_policy()\n       {CVE-2026-64581}\n   * CVE-2026-64582\n     - RDMA/rxe: Fix a use-after-free problem in rxe_mmap\n       {CVE-2026-64582}\n   * CVE-2026-64584\n     - usb: gadget: f_midi: cancel pending IN work before freeing the\n       midi object {CVE-2026-64584}\n   * CVE-2026-64585\n     - can: esd_usb: kill anchored URBs before freeing netdevs\n       {CVE-2026-64585}\n   * CVE-2026-64587\n     - net: ethernet: arc: emac: quiesce interrupts before requesting IRQ\n       {CVE-2026-64587}\n   * CVE-2026-64593\n     - btrfs: do not trim a device which is not writeable\n       {CVE-2026-64593}","status":"published","published":"2026-10-19T13:06:01Z","modified":"2026-10-26T09:31:53.128542628Z","updated_at":"2026-11-02T15:43:47.591214Z"},{"id":"CLSA-2026-1792239979","title":"kernel: Fix of 73 CVEs","description":"- ipv4: validate checksum_start before completing checksum {CVE-2026-99999}\n- net: ip6_vti: require CAP_NET_ADMIN in the device netns for changelink {CVE-2026-72055}\n- ip6: vti: Use ip6_tnl.net in vti6_siocdevprivate(). {CVE-2026-63921}\n- ip6: vti: Use ip6_tnl.net in vti6_changelink(). {CVE-2026-63917}\n- bpf: Mask pseudo pointer values in verifier logs {CVE-2026-72402}\n- drop_monitor: perform u64_stats updates under IRQ-disabled section {CVE-2026-68286}\n- wifi: ath11k: fix NULL pointer dereference in ath11k_hal_srng_access_begin {CVE-2026-68362}\n- gve: fix Rx queue stall on alloc failure {CVE-2026-68129}\n- vxlan: require CAP_NET_ADMIN in the device netns for changelink {CVE-2026-68432}\n- net: qrtr: restrict socket creation to the initial network namespace {CVE-2026-68294}\n- nbd: restrict sockets to TCP and UDP {CVE-2025-40080}\n- audit: fix recursive locking deadlock in audit_dupe_exe() {CVE-2026-68096}\n- scsi: smartpqi: Fix device resources accessed after device removal {CVE-2025-68371}\n- cifs: fix oops during encryption {CVE-2022-50341}\n- net: qrtr: ns: Limit the maximum server registration per node {CVE-2026-43491}\n- mmc: vub300: fix warning - do not call blocking ops when !TASK_RUNNING {CVE-2022-50430}\n- ipvlan: inherit needed_headroom and needed_tailroom from phy_dev {CVE-2026-74744}\n- xfs: don't swallow dquot recovery verification errors {CVE-2026-80529}\n- xfs: dquot recovery does not validate the recovered dquot {CVE-2026-80529}\n- xfs: clean up dqblk extraction {CVE-2026-80529}\n- Bluetooth: RFCOMM: Fix session UAF in set_termios {CVE-2026-68188}\n- bpf: Fix accesses to uninit stack slots {CVE-2023-52452}\n- bpf: Allow reads from uninit stack {CVE-2023-52452}\n- fbdev: Fix incorrect page mapping clearance at fb_deferred_io_release() {CVE-2023-52731}\n- iommu/intel: Fix out-of-bounds memset in dmar_latency_disable() {CVE-2026-68324}\n- nfsd: make sure exp active before svc_export_show {CVE-2024-56558}\n- Input: elan_i2c - validate firmware size before use {CVE-2026-64237}\n- net/sched: ets: use old 'nbands' while purging unused classes {CVE-2025-38684}\n- net_sched: ets: fix a race in ets_qdisc_change() {CVE-2025-38107}\n- fbcon: Fix OOB access in font allocation {CVE-2025-39967}\n- fbcon: fix integer overflow in fbcon_do_set_font {CVE-2025-39967}\n- kyber: fix out of bounds access when preempted {CVE-2021-46984}\n- padata: Reset next CPU when reorder sequence wraps around {CVE-2025-38584}\n- padata: Fix pd UAF once and for all {CVE-2025-38584}\n- padata: Fix refcnt handling in padata_free_shell() {CVE-2023-52854}\n- xen/privcmd: unregister xenstore notifier on module exit {CVE-2026-31788}\n- xen/privcmd: restrict usage in unprivileged domU {CVE-2026-31788}\n- Bluetooth: MGMT: Fix memory leak in set_ssp_complete {CVE-2026-23151}\n- Bluetooth: MGMT: Fix possible UAFs {CVE-2025-39981}\n- xfrm: Fix dev use-after-free in xfrm async resumption {CVE-2026-72463}\n- xfrm: hold dev ref until after transport_finish NF_HOOK {CVE-2026-31663}\n- netfilter: conntrack: dccp: copy entire header to stack buffer, not just basic one {CVE-2023-53333}\n- nvme-tcp: fix NULL pointer dereferences in nvmet_tcp_build_pdu_iovec {CVE-2026-22998}\n- bpf, test_run: Fix alignment problem in bpf_prog_test_run_skb() {CVE-2022-49840}\n- ALSA: firewire-motu: add bounds check in put_user loop for DSP events {CVE-2025-68753}\n- ALSA: firewire-motu: fix buffer overflow in hwdep read for DSP events {CVE-2025-68347}\n- HID: multitouch: Add NULL check in mt_input_configured {CVE-2024-58020}\n- HID: multitouch: Correct devm device reference for hidinput input_dev name {CVE-2023-53454}\n- RDMA/mlx5: Fix error flow upon firmware failure for RQ destruction {CVE-2025-38161}\n- RDMA/mlx5: Return the firmware result upon destroying QP/RQ {CVE-2023-53286}\n- cifs: Fix warning and UAF when destroy the MR list {CVE-2023-53427}\n- cifs: Fix lost destroy smbd connection when MR allocate failed {CVE-2023-54260}\n- cifs: Fix oops due to uncleared server-\u003esmbd_conn in reconnect {CVE-2023-53006}\n- PCI/ASPM: Fix link state exit during switch upstream function removal {CVE-2024-58093}\n- PCI/ASPM: Disable ASPM on MFD function removal to avoid use-after-free {CVE-2023-53446}\n- ubi: Fix failure attaching when vid_hdr offset equals to (sub)page size {CVE-2023-53265}\n- ubi: ensure that VID header offset + VID header size \u003c= alloc, size {CVE-2023-53265}\n- usbnet: Prevents free active kevent {CVE-2025-68312}\n- usbnet: Fix linkwatch use-after-free on disconnect {CVE-2022-50220}\n- lib: cpu_rmap: Fix potential use-after-free in irq_cpu_rmap_release() {CVE-2023-53484}\n- lib: cpu_rmap: Avoid use after free on rmap-\u003eobj array entries {CVE-2023-53484}\n- misc: sgi-gru: fix use-after-free error in gru_set_context_option, gru_fault and gru_handle_user_call_os {CVE-2022-3424}\n- ipv4: fib: Don't dump dying fib_info in fib_leaf_notify(). {CVE-2026-74289}\n- tipc: fix UAF in tipc_l2_send_msg() {CVE-2026-74255}\n- sctp: fix err_chunk memory leaks in INIT handling {CVE-2026-72413}\n- char: tlclk: fix use-after-free in tlclk_cleanup() {CVE-2026-80622}\n- ACPICA: Enhance buffer validation in acpi_ut_walk_aml_resources() {CVE-2026-97445}\n- ACPICA: Apply pack(1) to union aml_resource {CVE-2026-97445}\n- IB/isert: wait for deferred control PDU completions before releasing the connection {CVE-2026-98357}\n- dmaengine: wait for RCU readers before releasing dma_device {CVE-2026-98342}\n- netfilter: flowtable: hold reference on ct until flow is released {CVE-2026-98320}\n- IB/mlx4: Fix use-after-free on pkey sysfs registration failure {CVE-2026-98217}\n- wifi: brcmsmac: fix UAF in brcms_free_timer() {CVE-2026-98196}\n- wifi: ath9k: fix OOB access from firmware tx status queue ID {CVE-2026-74408}\n- tipc: require net admin for TIPCv2 netlink mutators {CVE-2026-74283}\n- tipc: prevent snt_unacked underflow on CONN_ACK {CVE-2026-74282}\n- dmaengine: Fix possible use after free {CVE-2026-72476}\n- drm/amdgpu/vcn: fix integer overflow in dec_msg buffer count check {CVE-2026-89818}\n- drm/amdgpu/vcn3: Avoid overflow on msg bound check {CVE-2026-46237}\n- drm/amdgpu/vcn3: Prevent OOB reads when parsing dec msg {CVE-2026-46230}\n- drm/amdgpu/vcn4: Avoid overflow on msg bound check {CVE-2026-46217}\n- drm/amdgpu/vcn4: Prevent OOB reads when parsing dec msg {CVE-2026-46199}\n- smb: client: restrict implied bcc[0] exemption to responses without data area {CVE-2026-64448}\n- crypto: qat - fix VF2PF work teardown race in adf_disable_sriov() {CVE-2026-64438}\n- net: ipv4: bound TCP reordering sysctl writes and MTU probe sizes {CVE-2026-64422}\n- proc: protect ptrace_may_access() with exec_update_lock (FD links) {CVE-2026-64375}\n- proc/fd: In proc_fd_link use fget_task {CVE-2026-64375}\n- proc: convert the return type of proc_fd_access_allowed() to be boolean {CVE-2026-64375}\n- usb: free iso schedules on failed submit {CVE-2026-64348}\n- USB: iowarrior: fix use-after-free on disconnect race {CVE-2026-64341}\n- crypto: qat - protect service table iterations with service_lock {CVE-2026-64305}\n- crypto: qat - validate RSA CRT component lengths {CVE-2026-64304}\n- udf: validate VAT header length against the VAT inode size {CVE-2026-64323}\n- virtio-net: ensure the received length does not exceed allocated size {CVE-2025-38375}\n- virtio-net: build xdp_buff with multi buffers {CVE-2025-38375}\n- virtio-net: disable the hole mechanism for xdp {CVE-2025-38375}","status":"published","published":"2026-10-17T12:27:27Z","modified":"2026-10-26T09:43:43.476853338Z","updated_at":"2026-11-02T15:43:52.011757Z"},{"id":"RLSA-2024:7001","title":"Important: kernel-rt security update","description":"The kernel-rt packages provide the Real Time Linux Kernel, which enables fine-tuning for systems with extremely high determinism requirements.  \nSecurity Fix(es):\n\n CVE-2023-6040  CVE-2024-26595  CVE-2021-46984  CVE-2023-52478  CVE-2023-52476  CVE-2023-52522  CVE-2021-47101  CVE-2021-47097  CVE-2023-52605  CVE-2024-26645  CVE-2024-26665  CVE-2024-26720  CVE-2024-26717  CVE-2024-26769  CVE-2024-26894  CVE-2024-26880  CVE-2024-26855  CVE-2024-26923  CVE-2024-26939  CVE-2024-27013  CVE-2024-27042  CVE-2024-35809  CVE-2023-52683  CVE-2024-35884  CVE-2024-35877  CVE-2024-35944  CVE-2024-35989  CVE-2021-47412  CVE-2021-47393  CVE-2021-47386  CVE-2021-47385  CVE-2021-47384  CVE-2021-47383  CVE-2021-47432  CVE-2021-47352  CVE-2021-47338  CVE-2021-47321  CVE-2021-47289  CVE-2021-47287  CVE-2023-52817  CVE-2023-52840  CVE-2021-47441  CVE-2021-47466  CVE-2021-47455  CVE-2021-47497  CVE-2021-47560  CVE-2021-47527  CVE-2024-36883  CVE-2024-36920  CVE-2024-36902  CVE-2024-36953  CVE-2024-36939  CVE-2024-36901  CVE-2021-47582  CVE-2021-47609  CVE-2024-38619  CVE-2022-48754  CVE-2022-48760  CVE-2024-38581  CVE-2024-38570  CVE-2024-38559  CVE-2024-38558  CVE-2024-37356  CVE-2024-39471  CVE-2024-39499  CVE-2024-39501  CVE-2024-39506  CVE-2024-40904  CVE-2024-40911  CVE-2024-40912  CVE-2024-40929  CVE-2024-40931  CVE-2024-40941  CVE-2024-40954  CVE-2024-40958  CVE-2024-40959  CVE-2024-40960  CVE-2024-40972  CVE-2024-40977  CVE-2024-40978  CVE-2024-40988  CVE-2024-40989  CVE-2024-40995  CVE-2024-40997  CVE-2024-40998  CVE-2024-41005  CVE-2024-40901  CVE-2024-41007  CVE-2024-41008  CVE-2022-48804  CVE-2022-48836  CVE-2022-48866  CVE-2024-41090  CVE-2024-41091  CVE-2024-41012  CVE-2024-41013  CVE-2024-41014  CVE-2024-41035  CVE-2024-41038  CVE-2024-41039  CVE-2024-41040  CVE-2024-41041  CVE-2024-41044  CVE-2024-41055  CVE-2024-41056  CVE-2024-41060  CVE-2024-41071  CVE-2024-41076  CVE-2024-41097  CVE-2024-42084  CVE-2024-42090  CVE-2024-42096  CVE-2024-42114  CVE-2024-42124  CVE-2024-42131  CVE-2024-42152  CVE-2024-42154  CVE-2024-42226  CVE-2024-42228  CVE-2024-42237  CVE-2024-42238  CVE-2024-42240  CVE-2024-42246  CVE-2024-42322  CVE-2024-43871  For more details about the security issue(s), including the impact, a CVSS score, acknowledgments, and other related information, refer to the CVE page(s) listed in the References section.","status":"published","published":"2024-09-30T14:30:43.714585Z","modified":"2026-02-05T07:45:08.276415Z","updated_at":"2026-11-02T15:53:24.923365Z"},{"id":"SUSE-SU-2024:1454-1","title":"Security update for the Linux Kernel","description":"\n\nThe SUSE Linux Enterprise 15 SP2 kernel was updated to receive various security bugfixes.\n\nThe following security bugs were fixed:\n\n- CVE-2020-36780: Fixed a reference leak when pm_runtime_get_sync fails in i2c (bsc#1220556).\n- CVE-2020-36782: Fixed a reference leak when pm_runtime_get_sync fails in i2c imx-lpi2c (bsc#1220560).\n- CVE-2020-36783: Fixed a reference leak when pm_runtime_get_sync fails in i2c img-scb (bsc#1220561).\n- CVE-2021-23134: Fixed a use-after-free issue in nfc sockets (bsc#1186060).\n- CVE-2021-46909: Fixed a PCI interrupt mapping in ARM footbridge (bsc#1220442).\n- CVE-2021-46921: Fixed ordering in queued_write_lock_slowpath (bsc#1220468).\n- CVE-2021-46930: Fixed a list_head check warning caused by uninitialization of list_head in usb mtu3 (bsc#1220484).\n- CVE-2021-46938: Fixed a double free of blk_mq_tag_set in dev remove after table load fails in dm rq (bsc#1220554).\n- CVE-2021-46939: Fixed a denial of service in trace_clock_global() in tracing (bsc#1220580).\n- CVE-2021-46943: Fixed an oops in set_fmt error handling in media: staging/intel-ipu3 (bsc#1220583).\n- CVE-2021-46944: Fixed a memory leak in imu_fmt in media staging/intel-ipu3 (bsc#1220566).\n- CVE-2021-46950: Fixed a data corruption bug in raid1 arrays using bitmaps in md/raid1 (bsc#1220662).\n- CVE-2021-46951: Fixed an integer underflow of efi_tpm_final_log_size in tpm_read_log_efi in tpm efi (bsc#1220615).\n- CVE-2021-46958: Fixed a race between transaction aborts and fsyncs leading to use-after-free in btrfs (bsc#1220521).\n- CVE-2021-46960: Fixed a warning on smb2_get_enc_key in cifs (bsc#1220528).\n- CVE-2021-46961: Fixed an error on not enabling irqs when handling spurious interrups in irqchip/gic-v3 (bsc#1220529).\n- CVE-2021-46962: Fixed a resource leak in the remove function in mmc uniphier-sd (bsc#1220532).\n- CVE-2021-46963: Fixed a denial of service in qla2xxx_mqueuecommand() in scsi qla2xxx (bsc#1220536)\n- CVE-2021-46971: Fixed unconditional security_locked_down() call in perf/core (bsc#1220697).\n- CVE-2021-46981: Fixed a NULL pointer in flush_workqueue in nbd (bsc#1220611).\n- CVE-2021-46984: Fixed an out of bounds access in kyber_bio_merge() in kyber (bsc#1220631).\n- CVE-2021-46988: Fixed release page in error path to avoid BUG_ON in userfaultfd (bsc#1220706).\n- CVE-2021-46990: Fixed a denial of service when toggling entry flush barrier in powerpc/64s (bsc#1220743).\n- CVE-2021-46991: Fixed a use-after-free in i40e_client_subtask (bsc#1220575).\n- CVE-2021-46992: Fixed a bug to avoid overflows in nft_hash_buckets (bsc#1220638).\n- CVE-2021-46998: Fixed an use after free bug in enic_hard_start_xmit in ethernet/enic (bsc#1220625).\n- CVE-2021-47000: Fixed an inode leak on getattr error in __fh_to_dentry in ceph (bsc#1220669).\n- CVE-2021-47006: Fixed wrong check in overflow_handler hook in ARM 9064/1 hw_breakpoint (bsc#1220751).\n- CVE-2021-47013: Fixed a use after free in emac_mac_tx_buf_send (bsc#1220641).\n- CVE-2021-47015: Fixed a RX consumer index logic in the error path in bnxt_rx_pkt() in bnxt_en (bsc#1220794).\n- CVE-2021-47020: Fixed a memory leak in stream config error path in soundwire stream (bsc#1220785).\n- CVE-2021-47034: Fixed a kernel memory fault for pte update on radix in powerpc/64s (bsc#1220687).\n- CVE-2021-47045: Fixed a null pointer dereference in lpfc_prep_els_iocb() in scsi lpfc (bsc#1220640).\n- CVE-2021-47049: Fixed an after free in __vmbus_open() in hv vmbus (bsc#1220692).\n- CVE-2021-47051: Fixed a PM reference leak in lpspi_prepare_xfer_hardware() in spi fsl-lpspi (bsc#1220764).\n- CVE-2021-47055: Fixed missing permissions for locking and badblock ioctls in mtd (bsc#1220768).\n- CVE-2021-47056: Fixed a user-memory-access error on vf2pf_lock in crypto (bsc#1220769).\n- CVE-2021-47058: Fixed a possible user-after-free in set debugfs_name in regmap (bsc#1220779).\n- CVE-2021-47061: Fixed a bug in KVM by destroy I/O bus devices on unregister failure _after_  sync'ing SRCU (bsc#1220745).\n- CVE-2021-47063: Fixed a potential use-after-free during bridge detach in drm bridge/panel (bsc#1220777).\n- CVE-2021-47065: Fixed an array overrun in rtw_get_tx_power_params() in rtw88 (bsc#1220749).\n- CVE-2021-47068: Fixed a use-after-free issue in llcp_sock_bind/connect (bsc#1220739).\n- CVE-2021-47069: Fixed a crash due to relying on a stack reference past its expiry in ipc/mqueue, ipc/msg, ipc/sem (bsc#1220826).\n- CVE-2021-47070: Fixed a memory leak in error handling paths on memory allocated by vmbus_alloc_ring in uio_hv_generic (bsc#1220829).\n- CVE-2021-47071: Fixed a memory leak in error handling paths in hv_uio_cleanup() in uio_hv_generic (bsc#1220846).\n- CVE-2021-47073: Fixed a oops on rmmod dell_smbios exit_dell_smbios_wmi() in platform/x86 dell-smbios-wmi (bsc#1220850).\n- CVE-2021-47077: Fixed a NULL pointer dereference when in shost_data (bsc#1220861).\n- CVE-2021-47082: Fixed a double free in tun_free_netdev in tun (bsc#1220969).\n- CVE-2021-47109: Fixed an overflow in neighbour table in neighbour (bsc#1221534).\n- CVE-2021-47110: Fixed possible memory corruption when restoring from hibernation in x86/kvm (bsc#1221532).\n- CVE-2021-47112: Fixed possible memory corruption when restoring from hibernation in x86/kvm (bsc#1221541).\n- CVE-2021-47114: Fixed a data corruption by fallocate in ocfs2 (bsc#1221548).\n- CVE-2021-47117: Fixed a crash in ext4_es_cache_extent as ext4_split_extent_at failed in ext4 (bsc#1221575).\n- CVE-2021-47118: Fixed an use-after-free in init task's struct pid in pid (bsc#1221605).\n- CVE-2021-47119: Fixed a memory leak in ext4_fill_super in ext4 (bsc#1221608).\n- CVE-2021-47120: Fixed a NULL pointer dereference on disconnect in HID magicmouse (bsc#1221606).\n- CVE-2021-47138: Fixed an out-of-bound memory access during clearing filters in cxgb4 (bsc#1221934).\n- CVE-2021-47139: Fixed a race condition that lead to oops in netdevice registration in net hns3 (bsc#1221935).\n- CVE-2021-47141: Fixed a null pointer dereference on priv-\u003emsix_vectors when driver is unloaded in gve (bsc#1221949).\n- CVE-2021-47142: Fixed an use-after-free on ttm-\u003esg in drm/amdgpu (bsc#1221952).\n- CVE-2021-47144: Fixed a refcount leak in amdgpufb_create in drm/amd/amdgpu (bsc#1221989).\n- CVE-2021-47153: Fixed an out-of-range memory access during bus reset in the case of a block transaction in i2c/i801 (bsc#1221969).\n- CVE-2021-47161: Fixed a resource leak in an error handling path in the error handling path of the probe function in spi spi-fsl-dspi (bsc#1221966).\n- CVE-2021-47165: Fixed a NULL pointer dereference when component was not probed during shutdown in drm/mesonhe (bsc#1221965).\n- CVE-2021-47166: Fixed a data corruption of pg_bytes_written in nfs_do_recoalesce() in nfs (bsc#1221998).\n- CVE-2021-47167: Fixed an oopsable condition in __nfs_pageio_add_request() in nfs (bsc#1221991).\n- CVE-2021-47168: Fixed an incorrect limit in filelayout_decode_layout() in nfs (bsc#1222002).\n- CVE-2021-47169: Fixed a NULL pointer dereference in rp2_probe in serial rp2 (bsc#1222000).\n- CVE-2021-47170: Fixed a WARN about excessively large memory allocations in usb usbfs (bsc#1222004).\n- CVE-2021-47171: Fixed a memory leak in smsc75xx_bind in net usb (bsc#1221994).\n- CVE-2021-47172: Fixed a potential overflow due to non sequential channel numbers in adc/ad7124 (bsc#1221992).\n- CVE-2021-47173: Fixed a memory leak in uss720_probe in misc/uss720 (bsc#1221993).\n- CVE-2021-47177: Fixed a sysfs leak in alloc_iommu() in iommu/vt-d (bsc#1221997).\n- CVE-2021-47179: Fixed a NULL pointer dereference in pnfs_mark_matching_lsegs_return() in nfsv4 (bsc#1222001).\n- CVE-2021-47180: Fixed a memory leak in nci_allocate_device nfcmrvl_disconnect in nfc nci (bsc#1221999).\n- CVE-2021-47181: Fixed a null pointer dereference caused by calling platform_get_resource()  (bsc#1222660).\n- CVE-2021-47183: Fixed a null pointer dereference during link down processing in scsi lpfc (bsc#1192145, bsc#1222664).\n- CVE-2021-47185: Fixed a softlockup issue in flush_to_ldisc in tty tty_buffer (bsc#1222669).\n- CVE-2021-47189: Fixed denial of service due to memory ordering issues between normal and ordered work functions in btrfs (bsc#1222706).\n- CVE-2022-0487: Fixed an use-after-free vulnerability in rtsx_usb_ms_drv_remove() in drivers/memstick/host/rtsx_usb_ms.c (bsc#1194516).\n- CVE-2022-4744: Fixed a double-free that could lead to DoS or privilege escalation in TUN/TAP device driver functionality (bsc#1209635).\n- CVE-2022-48626: Fixed a potential use-after-free on remove path in moxart (bsc#1220366).\n- CVE-2023-0160: Fixed deadlock flaw in BPF that could allow a local user to potentially crash the system (bsc#1209657).\n- CVE-2023-1192: Fixed use-after-free in cifs_demultiplex_thread() (bsc#1208995).\n- CVE-2023-28746: Fixed Register File Data Sampling (bsc#1213456).\n- CVE-2023-35827: Fixed a use-after-free issue in ravb_tx_timeout_work() (bsc#1212514).\n- CVE-2023-52454: Fixed a kernel panic when host sends an invalid H2C PDU length in nvmet-tcp (bsc#1220320).\n- CVE-2023-52469: Fixed an use-after-free in kv_parse_power_table in drivers/amd/pm (bsc#1220411).\n- CVE-2023-52470: Fixed null-ptr-deref in radeon_crtc_init() (bsc#1220413).\n- CVE-2023-52474: Fixed a data corruption in user SDMA requests in IB/hfi1 (bsc#1220445).\n- CVE-2023-52476: Fixed possible unhandled page fault via perf sampling NMI during vsyscall (bsc#1220703).\n- CVE-2023-52477: Fixed USB Hub accesses to uninitialized BOS descriptors (bsc#1220790).\n- CVE-2023-52500: Fixed information leaking when processing OPC_INB_SET_CONTROLLER_CONFIG command (bsc#1220883).\n- CVE-2023-52500: Fixed leaking tags when processing  OPC_INB_SET_CONTROLLER_CONFIG command in scsi in pm80xx (bsc#1220883).\n- CVE-2023-52509: Fixed a use-after-free issue in ravb_tx_timeout_work() (bsc#1220836).\n- CVE-2023-52572: Fixed UAF in cifs_demultiplex_thread() in cifs (bsc#1220946).\n- CVE-2023-52575: Fixed SBPB enablement for spec_rstack_overflow=off (bsc#1220871).\n- CVE-2023-52583: Fixed deadlock or deadcode of misusing dget() inside ceph (bsc#1221058).\n- CVE-2023-52590: Fixed a possible ocfs2 filesystem corruption via directory renaming (bsc#1221088).\n- CVE-2023-52591: Fixed a possible reiserfs filesystem corruption via directory renaming (bsc#1221044).\n- CVE-2023-52607: Fixed null-pointer dereference in pgtable_cache_add kasprintf() in powerpc/mm (bsc#1221061).\n- CVE-2023-52628: Fixed 4-byte stack OOB write in nftables (bsc#1222117).\n- CVE-2023-6270: Fixed a use-after-free issue in aoecmd_cfg_pkts (bsc#1218562).\n- CVE-2023-6356: Fixed a NULL pointer dereference in nvmet_tcp_build_pdu_iovec (bsc#1217987).\n- CVE-2023-6531: Fixed a use-after-free flaw due to a race problem in the unix garbage collector's deletion of SKB races (bsc#1218447).\n- CVE-2023-6535: Fixed a NULL pointer dereference in nvmet_tcp_execute_request (bsc#1217988).\n- CVE-2023-6536: Fixed a NULL pointer dereference in __nvmet_req_complete (bsc#1217989).\n- CVE-2023-7042: Fixed a null pointer dereference in ath10k_wmi_tlv_op_pull_mgmt_tx_compl_ev() in drivers/net/wireless/ath/ath10k/wmi-tlv.c in net (bsc#1218336).\n- CVE-2023-7192: Fixed a memory leak problem in ctnetlink_create_conntrack in net/netfilter/nf_conntrack_netlink.c (bsc#1218479).\n- CVE-2024-22099: Fixed a null pointer dereference in /net/bluetooth/rfcomm/core.C in bluetooth (bsc#1219170).\n- CVE-2024-26600: Fixed null pointer dereference for SRP in phy-omap-usb2 (bsc#1220340).\n- CVE-2024-26614: Fixed the initialization of accept_queue's spinlocks (bsc#1221293).\n- CVE-2024-26642: Fixed the set of anonymous timeout flag in netfilter nf_tables (bsc#1221830).\n- CVE-2024-26704: Fixed a double-free of blocks due to wrong extents moved_len in ext4 (bsc#1222422).\n- CVE-2024-26733: Fixed an overflow in arp_req_get() in arp (bsc#1222585).\n\nThe following non-security bugs were fixed:\n\n- doc/README.SUSE: Update information about module support status (jsc#PED-5759)\n- usb: hub: Guard against accesses to uninitialized BOS descriptors (git-fixes).\n- fs,hugetlb: fix NULL pointer dereference in hugetlbs_fill_super (bsc#1219264).\n- tty: n_gsm: require CAP_NET_ADMIN to attach N_GSM0710 ldisc (bsc#1222619).\n","status":"published","published":"2024-04-26T15:11:05Z","modified":"2026-02-04T03:35:19.154104Z","updated_at":"2026-11-02T15:53:54.652421Z"},{"id":"SUSE-SU-2024:1465-1","title":"Security update for the Linux Kernel","description":"\n\nThe SUSE Linux Enterprise 15 SP3 RT kernel was updated to receive various security bugfixes.\n\nThe following security bugs were fixed:\n\n- CVE-2020-36780: Fixed a reference leak when pm_runtime_get_sync fails in i2c (bsc#1220556).\n- CVE-2020-36781: Fixed reference leak when pm_runtime_get_sync fails in i2c/imx (bsc#1220557).\n- CVE-2020-36782: Fixed a reference leak when pm_runtime_get_sync fails in i2c imx-lpi2c (bsc#1220560).\n- CVE-2020-36783: Fixed a reference leak when pm_runtime_get_sync fails in i2c img-scb (bsc#1220561).\n- CVE-2021-46908: Fixed incorrect permission flag for mixed signed bounds arithmetic in bpf (bsc#1220425).\n- CVE-2021-46909: Fixed a PCI interrupt mapping in ARM footbridge (bsc#1220442).\n- CVE-2021-46911: Fixed kernel panic (bsc#1220400).\n- CVE-2021-46914: Fixed unbalanced device enable/disable in suspend/resume in pci_disable_device() (bsc#1220465).\n- CVE-2021-46917: Fixed wq cleanup of WQCFG registers in idxd (bsc#1220432).\n- CVE-2021-46918: Fixed not clearing MSIX permission entry on shutdown in idxd (bsc#1220429).\n- CVE-2021-46919: Fixed wq size store permission state in idxd (bsc#1220414).\n- CVE-2021-46920: Fixed clobbering of SWERR overflow bit on writeback (bsc#1220426).\n- CVE-2021-46921: Fixed ordering in queued_write_lock_slowpath (bsc#1220468).\n- CVE-2021-46922: Fixed TPM reservation for seal/unseal (bsc#1220475).\n- CVE-2021-46930: Fixed usb/mtu3 list_head check warning (bsc#1220484).\n- CVE-2021-46931: Fixed wrong type casting in mlx5e_tx_reporter_dump_sq() (bsc#1220486).\n- CVE-2021-46933: Fixed possible underflow in ffs_data_clear() (bsc#1220487).\n- CVE-2021-46938: Fixed a double free of blk_mq_tag_set in dev remove after table load fails in dm rq (bsc#1220554).\n- CVE-2021-46939: Fixed a denial of service in trace_clock_global() in tracing (bsc#1220580).\n- CVE-2021-46943: Fixed an oops in set_fmt error handling in media: staging/intel-ipu3 (bsc#1220583).\n- CVE-2021-46944: Fixed a memory leak in imu_fmt in media staging/intel-ipu3 (bsc#1220566).\n- CVE-2021-46950: Fixed a data corruption bug in raid1 arrays using bitmaps in md/raid1 (bsc#1220662).\n- CVE-2021-46951: Fixed an integer underflow of efi_tpm_final_log_size in tpm_read_log_efi in tpm efi (bsc#1220615).\n- CVE-2021-46956: Fixed memory leak in virtio_fs_probe() (bsc#1220516).\n- CVE-2021-46958: Fixed a race between transaction aborts and fsyncs leading to use-after-free in btrfs (bsc#1220521).\n- CVE-2021-46959: Fixed use-after-free with devm_spi_alloc_* (bsc#1220734).\n- CVE-2021-46960: Fixed a warning on smb2_get_enc_key in cifs (bsc#1220528).\n- CVE-2021-46961: Fixed spurious interrup handling (bsc#1220529).\n- CVE-2021-46962: Fixed a resource leak in the remove function in mmc uniphier-sd (bsc#1220532).\n- CVE-2021-46963: Fixed crash in qla2xxx_mqueuecommand()  (bsc#1220536).\n- CVE-2021-46971: Fixed unconditional security_locked_down() call (bsc#1220697).\n- CVE-2021-46976: Fixed crash in auto_retire in drm/i915 (bsc#1220621).\n- CVE-2021-46980: Fixed not retrieving all the PDOs instead of just the first 4 in usb/typec/ucsi (bsc#1220663).\n- CVE-2021-46981: Fixed a NULL pointer in flush_workqueue in nbd (bsc#1220611).\n- CVE-2021-46983: Fixed NULL pointer dereference when SEND is completed with error (bsc#1220639).\n- CVE-2021-46984: Fixed an out of bounds access in kyber_bio_merge() in kyber (bsc#1220631).\n- CVE-2021-46988: Fixed release page in error path to avoid BUG_ON (bsc#1220706).\n- CVE-2021-46990: Fixed a denial of service when toggling entry flush barrier in powerpc/64s (bsc#1220743).\n- CVE-2021-46991: Fixed a use-after-free in i40e_client_subtask (bsc#1220575).\n- CVE-2021-46992: Fixed a bug to avoid overflows in nft_hash_buckets (bsc#1220638).\n- CVE-2021-46998: Fixed an use after free bug in enic_hard_start_xmit in ethernet/enic (bsc#1220625).\n- CVE-2021-47000: Fixed an inode leak on getattr error in __fh_to_dentry in ceph (bsc#1220669).\n- CVE-2021-47001: Fixed cwnd update ordering in xprtrdma (bsc#1220670).\n- CVE-2021-47003: Fixed potential null dereference on pointer status in idxd_cmd_exec (bsc#1220677).\n- CVE-2021-47006: Fixed wrong check in overflow_handler hook in ARM 9064/1 hw_breakpoint (bsc#1220751).\n- CVE-2021-47009: Fixed memory leak on object td (bsc#1220733).\n- CVE-2021-47014: Fixed wild memory access when clearing fragments in net/sched/act_ct (bsc#1220630).\n- CVE-2021-47015: Fixed a RX consumer index logic in the error path in bnxt_rx_pkt() in bnxt_en (bsc#1220794).\n- CVE-2021-47017: Fixed use after free in ath10k_htc_send_bundle (bsc#1220678).\n- CVE-2021-47020: Fixed a memory leak in stream config error path in soundwire stream (bsc#1220785).\n- CVE-2021-47026: Fixed not destroying sysfs after removing session from active list (bsc#1220685).\n- CVE-2021-47034: Fixed a kernel memory fault for pte update on radix in powerpc/64s (bsc#1220687).\n- CVE-2021-47035: Fixed wrong WO permissions on second-level paging entries in iommu/vt-d (bsc#1220688).\n- CVE-2021-47038: Fixed deadlock between hci_dev-\u003elock and socket lock in bluetooth (bsc#1220753).\n- CVE-2021-47044: Fixed shift-out-of-bounds in load_balance() in sched/fair (bsc#1220759).\n- CVE-2021-47045: Fixed a null pointer dereference in lpfc_prep_els_iocb() in scsi lpfc (bsc#1220640).\n- CVE-2021-47046: Fixed off by one in hdmi_14_process_transaction() (bsc#1220758).\n- CVE-2021-47049: Fixed an after free in __vmbus_open() in hv vmbus (bsc#1220692).\n- CVE-2021-47051: Fixed a PM reference leak in lpspi_prepare_xfer_hardware() in spi fsl-lpspi (bsc#1220764).\n- CVE-2021-47055: Fixed missing permissions for locking and badblock ioctls in mtd (bsc#1220768).\n- CVE-2021-47056: Fixed a user-memory-access error on vf2pf_lock in crypto (bsc#1220769).\n- CVE-2021-47058: Fixed a possible user-after-free in set debugfs_name in regmap (bsc#1220779).\n- CVE-2021-47063: Fixed a potential use-after-free during bridge detach in drm bridge/panel (bsc#1220777).\n- CVE-2021-47065: Fixed an array overrun in rtw_get_tx_power_params() in rtw88 (bsc#1220749).\n- CVE-2021-47068: Fixed a use-after-free issue in llcp_sock_bind/connect (bsc#1220739).\n- CVE-2021-47070: Fixed memory leak in error handling paths in uio_hv_generic (bsc#1220829).\n- CVE-2021-47071: Fixed a memory leak in error handling paths in hv_uio_cleanup() in uio_hv_generic (bsc#1220846).\n- CVE-2021-47073: Fixed oops on rmmod dell_smbios init_dell_smbios_wmi() (bsc#1220850).\n- CVE-2021-47077: Fixed a NULL pointer dereference when in shost_data (bsc#1220861).\n- CVE-2021-47082: Fixed ouble free in tun_free_netdev() (bsc#1220969).\n- CVE-2021-47087: Fixed incorrect page free bug in tee/optee (bsc#1220954).\n- CVE-2021-47095: Fixed missing initialization in ipmi/ssif (bsc#1220979).\n- CVE-2021-47097: Fixed stack out of bound access in elantech_change_report_id() (bsc#1220982).\n- CVE-2021-47100: Fixed UAF when uninstall in ipmi (bsc#1220985).\n- CVE-2021-47101: Fixed uninit-value in asix_mdio_read() (bsc#1220987).\n- CVE-2021-47109: Fixed NUD_NOARP entries to be forced GCed (bsc#1221534).\n- CVE-2021-47110: Fixed possible memory corruption when restoring from hibernation in x86/kvm (bsc#1221532).\n- CVE-2021-47112: Fixed possible memory corruption when restoring from hibernation in x86/kvm (bsc#1221541).\n- CVE-2021-47114: Fixed a data corruption by fallocate in ocfs2 (bsc#1221548).\n- CVE-2021-47117: Fixed a crash in ext4_es_cache_extent as ext4_split_extent_at failed in ext4 (bsc#1221575).\n- CVE-2021-47118: Fixed an use-after-free in init task's struct pid in pid (bsc#1221605).\n- CVE-2021-47119: Fixed a memory leak in ext4_fill_super in ext4 (bsc#1221608).\n- CVE-2021-47120: Fixed a NULL pointer dereference on disconnect in HID magicmouse (bsc#1221606).\n- CVE-2021-47130: Fixed freeing unallocated p2pmem in nvmet (bsc#1221552).\n- CVE-2021-47136: Fixed uninitialized memory access caused by allocation via zero-initialize tc skb extension in net (bsc#1221931).\n- CVE-2021-47137: Fixed memory corruption in RX ring in net/lantiq (bsc#1221932).\n- CVE-2021-47138: Fixed an out-of-bound memory access during clearing filters in cxgb4 (bsc#1221934).\n- CVE-2021-47139: Fixed a race condition that lead to oops in netdevice registration in net hns3 (bsc#1221935).\n- CVE-2021-47141: Fixed a null pointer dereference on priv-\u003emsix_vectors when driver is unloaded in gve (bsc#1221949).\n- CVE-2021-47142: Fixed an use-after-free on ttm-\u003esg in drm/amdgpu (bsc#1221952).\n- CVE-2021-47144: Fixed a refcount leak in amdgpufb_create in drm/amd/amdgpu (bsc#1221989).\n- CVE-2021-47150: Fixed the potential memory leak in fec_enet_init() (bsc#1221973).\n- CVE-2021-47153: Fixed wrongly generated interrupt on bus reset in i2c/i801 (bsc#1221969).\n- CVE-2021-47160: Fixed VLAN traffic leaks in dsa: mt7530 (bsc#1221974).\n- CVE-2021-47161: Fixed a resource leak in an error handling path in the error handling path of the probe function in spi spi-fsl-dspi (bsc#1221966).\n- CVE-2021-47164: Fixed null pointer dereference accessing lag dev in net/mlx5e (bsc#1221978).\n- CVE-2021-47165: Fixed shutdown crash when component not probed in drm/meson (bsc#1221965).\n- CVE-2021-47166: Fixed a data corruption of pg_bytes_written in nfs_do_recoalesce() in nfs (bsc#1221998).\n- CVE-2021-47167: Fixed an oopsable condition in __nfs_pageio_add_request() in nfs (bsc#1221991).\n- CVE-2021-47168: Fixed an incorrect limit in filelayout_decode_layout() in nfs (bsc#1222002).\n- CVE-2021-47169: Fixed a NULL pointer dereference in rp2_probe in serial rp2 (bsc#1222000).\n- CVE-2021-47170: Fixed a WARN about excessively large memory allocations in usb usbfs (bsc#1222004).\n- CVE-2021-47171: Fixed a memory leak in smsc75xx_bind in net usb (bsc#1221994).\n- CVE-2021-47172: Fixed a potential overflow due to non sequential channel numbers in adc/ad7124 (bsc#1221992).\n- CVE-2021-47173: Fixed a memory leak in uss720_probe in misc/uss720 (bsc#1221993).\n- CVE-2021-47174: Fixed missing check in irq_fpu_usable() (bsc#1221990).\n- CVE-2021-47175: Fixed OOB access in net/sched/fq_pie (bsc#1222003).\n- CVE-2021-47176: Fixed crash with illegal operation exception in dasd_device_tasklet in s390/dasd (bsc#1221996).\n- CVE-2021-47177: Fixed a sysfs leak in alloc_iommu() in iommu/vt-d (bsc#1221997).\n- CVE-2021-47179: Fixed a NULL pointer dereference in pnfs_mark_matching_lsegs_return() in nfsv4 (bsc#1222001).\n- CVE-2021-47180: Fixed a memory leak in nci_allocate_device nfcmrvl_disconnect in nfc nci (bsc#1221999).\n- CVE-2021-47181: Fixed a null pointer dereference caused by calling platform_get_resource()  (bsc#1222660).\n- CVE-2021-47183: Fixed a null pointer dereference during link down processing in scsi lpfc (bsc#1192145, bsc#1222664).\n- CVE-2021-47185: Fixed a softlockup issue in flush_to_ldisc in tty tty_buffer (bsc#1222669).\n- CVE-2021-47189: Fixed denial of service due to memory ordering issues between normal and ordered work functions in btrfs (bsc#1222706).\n- CVE-2021-47202: Fixed NULL pointer dereferences in of_thermal_ functions (bsc#1222878)\n- CVE-2022-48626: Fixed a potential use-after-free on remove path moxart (bsc#1220366).\n- CVE-2023-0160: Fixed deadlock flaw in BPF that could allow a local user to potentially crash the system (bsc#1209657).\n- CVE-2023-52454: Fixed a kernel panic when host sends an invalid H2C PDU length (bsc#1220320).\n- CVE-2023-52469: Fixed a use-after-free in kv_parse_power_table (bsc#1220411).\n- CVE-2023-52470: Fixed null-ptr-deref in radeon_crtc_init() (bsc#1220413).\n- CVE-2023-52474: Fixed a vulnerability with non-PAGE_SIZE-end multi-iovec user SDMA requests (bsc#1220445).\n- CVE-2023-52476: Fixed possible unhandled page fault via perf sampling NMI during vsyscall (bsc#1220703).\n- CVE-2023-52477: Fixed USB Hub accesses to uninitialized BOS descriptors (bsc#1220790).\n- CVE-2023-52492: Fixed a null-pointer-dereference in channel unregistration function __dma_async_device_channel_register() (bsc#1221276).\n- CVE-2023-52500: Fixed information leaking when processing OPC_INB_SET_CONTROLLER_CONFIG command (bsc#1220883).\n- CVE-2023-52508: Fixed null pointer dereference in nvme_fc_io_getuuid() (bsc#1221015).\n- CVE-2023-52509: Fixed a use-after-free issue in ravb_tx_timeout_work() (bsc#1220836).\n- CVE-2023-52572: Fixed UAF in cifs_demultiplex_thread() in cifs (bsc#1220946).\n- CVE-2023-52575: Fixed SBPB enablement for spec_rstack_overflow=off (bsc#1220871).\n- CVE-2023-52583: Fixed deadlock or deadcode of misusing dget() inside ceph (bsc#1221058).\n- CVE-2023-52590: Fixed a possible ocfs2 filesystem corruption via directory renaming (bsc#1221088).\n- CVE-2023-52591: Fixed a possible reiserfs filesystem corruption via directory renaming (bsc#1221044).\n- CVE-2023-52607: Fixed a null-pointer-dereference in pgtable_cache_add kasprintf() (bsc#1221061).\n- CVE-2023-52628: Fixed 4-byte stack OOB write in nftables (bsc#1222117).\n- CVE-2023-6270: Fixed a use-after-free issue in aoecmd_cfg_pkts (bsc#1218562).\n- CVE-2023-6531: Fixed a use-after-free flaw due to a race problem in the unix garbage collector's deletion of SKB races with unix_stream_read_generic()on the socket that the SKB is queued on (bsc#1218447).\n- CVE-2023-7042: Fixed a null-pointer-dereference in ath10k_wmi_tlv_op_pull_mgmt_tx_compl_ev() (bsc#1218336).\n- CVE-2023-7192: Fixed a memory leak problem in ctnetlink_create_conntrack in net/netfilter/nf_conntrack_netlink.c (bsc#1218479).\n- CVE-2024-22099: Fixed a null-pointer-dereference in rfcomm_check_security (bsc#1219170).\n- CVE-2024-26600: Fixed NULL pointer dereference for SRP in phy-omap-usb2 (bsc#1220340).\n- CVE-2024-26614: Fixed the initialization of accept_queue's spinlocks (bsc#1221293).\n- CVE-2024-26642: Fixed the set of anonymous timeout flag in netfilter nf_tables (bsc#1221830).\n- CVE-2024-26704: Fixed a double-free of blocks due to wrong extents moved_len in ext4 (bsc#1222422).\n- CVE-2024-26733: Fixed an overflow in arp_req_get() in arp (bsc#1222585).\n\nThe following non-security bugs were fixed:\n\n- doc/README.SUSE: Update information about module support status (jsc#PED-5759)\n- fs,hugetlb: fix NULL pointer dereference in hugetlbs_fill_super (bsc#1219264).\n- group-source-files.pl: Quote filenames (boo#1221077).\n- mm: fix gup_pud_range (bsc#1220824).\n- tty: n_gsm: require CAP_NET_ADMIN to attach N_GSM0710 ldisc (bsc#1222619).\n- usb: hub: Guard against accesses to uninitialized BOS descriptors (git-fixes). Altered because 5.3 does not do SSP\n","status":"published","published":"2024-04-29T12:57:44Z","modified":"2026-02-04T02:45:19.117454Z","updated_at":"2026-11-02T15:53:54.652421Z"},{"id":"SUSE-SU-2024:1489-1","title":"Security update for the Linux Kernel","description":"\nThe SUSE Linux Enterprise 15 SP3 LTSS kernel was updated to receive various security bugfixes.\n\n\nThe following security bugs were fixed:\n\n- CVE-2020-36781: Fixed reference leak when pm_runtime_get_sync fails in i2c/imx (bsc#1220557).\n- CVE-2021-46911: Fixed kernel panic (bsc#1220400).\n- CVE-2021-46914: Fixed unbalanced device enable/disable in suspend/resume in pci_disable_device() (bsc#1220465).\n- CVE-2021-46917: Fixed wq cleanup of WQCFG registers in idxd (bsc#1220432).\n- CVE-2021-46918: Fixed not clearing MSIX permission entry on shutdown in idxd (bsc#1220429).\n- CVE-2021-46919: Fixed wq size store permission state in idxd (bsc#1220414).\n- CVE-2021-46920: Fixed clobbering of SWERR overflow bit on writeback (bsc#1220426).\n- CVE-2021-46922: Fixed TPM reservation for seal/unseal (bsc#1220475).\n- CVE-2021-46930: Fixed usb/mtu3 list_head check warning (bsc#1220484).\n- CVE-2021-46931: Fixed wrong type casting in mlx5e_tx_reporter_dump_sq() (bsc#1220486).\n- CVE-2021-46933: Fixed possible underflow in ffs_data_clear() (bsc#1220487).\n- CVE-2021-46956: Fixed memory leak in virtio_fs_probe() (bsc#1220516).\n- CVE-2021-46959: Fixed use-after-free with devm_spi_alloc_* (bsc#1220734).\n- CVE-2021-46961: Fixed spurious interrup handling (bsc#1220529).\n- CVE-2021-46971: Fixed unconditional security_locked_down() call (bsc#1220697).\n- CVE-2021-46976: Fixed crash in auto_retire in drm/i915 (bsc#1220621).\n- CVE-2021-46980: Fixed not retrieving all the PDOs instead of just the first 4 in usb/typec/ucsi (bsc#1220663).\n- CVE-2021-46983: Fixed NULL pointer dereference when SEND is completed with error (bsc#1220639).\n- CVE-2021-46988: Fixed release page in error path to avoid BUG_ON (bsc#1220706).\n- CVE-2021-47001: Fixed cwnd update ordering in xprtrdma (bsc#1220670).\n- CVE-2021-47003: Fixed potential null dereference on pointer status in idxd_cmd_exec (bsc#1220677).\n- CVE-2021-47009: Fixed memory leak on object td (bsc#1220733).\n- CVE-2021-47014: Fixed wild memory access when clearing fragments in net/sched/act_ct (bsc#1220630).\n- CVE-2021-47017: Fixed use after free in ath10k_htc_send_bundle (bsc#1220678).\n- CVE-2021-47026: Fixed not destroying sysfs after removing session from active list (bsc#1220685).\n- CVE-2021-47035: Fixed wrong WO permissions on second-level paging entries in iommu/vt-d (bsc#1220688).\n- CVE-2021-47038: Fixed deadlock between hci_dev-\u003elock and socket lock in bluetooth (bsc#1220753).\n- CVE-2021-47044: Fixed shift-out-of-bounds in load_balance() in sched/fair (bsc#1220759).\n- CVE-2021-47046: Fixed off by one in hdmi_14_process_transaction() (bsc#1220758).\n- CVE-2021-47087: Fixed incorrect page free bug in tee/optee (bsc#1220954).\n- CVE-2021-47095: Fixed missing initialization in ipmi/ssif (bsc#1220979).\n- CVE-2021-47097: Fixed stack out of bound access in elantech_change_report_id() (bsc#1220982).\n- CVE-2021-47100: Fixed UAF when uninstall in ipmi (bsc#1220985).\n- CVE-2021-47101: Fixed uninit-value in asix_mdio_read() (bsc#1220987).\n- CVE-2021-47109: Fixed NUD_NOARP entries to be forced GCed (bsc#1221534).\n- CVE-2021-47130: Fixed freeing unallocated p2pmem in nvmet (bsc#1221552).\n- CVE-2021-47137: Fixed memory corruption in RX ring in net/lantiq (bsc#1221932).\n- CVE-2021-47150: Fixed the potential memory leak in fec_enet_init() (bsc#1221973).\n- CVE-2021-47160: Fixed VLAN traffic leaks in dsa: mt7530 (bsc#1221974).\n- CVE-2021-47164: Fixed null pointer dereference accessing lag dev in net/mlx5e (bsc#1221978).\n- CVE-2021-47174: Fixed missing check in irq_fpu_usable() (bsc#1221990).\n- CVE-2021-47175: Fixed OOB access in net/sched/fq_pie (bsc#1222003).\n- CVE-2021-47181: Fixed a null pointer dereference caused by calling platform_get_resource()  (bsc#1222660).\n- CVE-2021-47183: Fixed a null pointer dereference during link down processing in scsi lpfc (bsc#1192145, bsc#1222664).\n- CVE-2021-47185: Fixed a softlockup issue in flush_to_ldisc in tty tty_buffer (bsc#1222669).\n- CVE-2021-47189: Fixed denial of service due to memory ordering issues between normal and ordered work functions in btrfs (bsc#1222706).\n- CVE-2023-0160: Fixed deadlock flaw in BPF that could allow a local user to potentially crash the system (bsc#1209657).\n- CVE-2023-28746: Fixed Register File Data Sampling (bsc#1213456).\n- CVE-2023-52469: Fixed a use-after-free in kv_parse_power_table (bsc#1220411).\n- CVE-2023-52470: Fixed null-ptr-deref in radeon_crtc_init() (bsc#1220413).\n- CVE-2023-52474: Fixed a vulnerability with non-PAGE_SIZE-end multi-iovec user SDMA requests (bsc#1220445).\n- CVE-2023-52476: Fixed possible unhandled page fault via perf sampling NMI during vsyscall (bsc#1220703).\n- CVE-2023-52492: Fixed a null-pointer-dereference in channel unregistration function __dma_async_device_channel_register() (bsc#1221276).\n- CVE-2023-52500: Fixed information leaking when processing OPC_INB_SET_CONTROLLER_CONFIG command (bsc#1220883).\n- CVE-2023-52508: Fixed null pointer dereference in nvme_fc_io_getuuid() (bsc#1221015).\n- CVE-2023-52575: Fixed SBPB enablement for spec_rstack_overflow=off (bsc#1220871).\n- CVE-2023-52583: Fixed deadlock or deadcode of misusing dget() inside ceph (bsc#1221058).\n- CVE-2023-52607: Fixed a null-pointer-dereference in pgtable_cache_add kasprintf() (bsc#1221061).\n- CVE-2023-52628: Fixed 4-byte stack OOB write in nftables (bsc#1222117).\n- CVE-2023-6270: Fixed a use-after-free issue in aoecmd_cfg_pkts (bsc#1218562).\n- CVE-2023-6531: Fixed a use-after-free flaw due to a race problem in the unix garbage collector's deletion of SKB races with unix_stream_read_generic()on the socket that the SKB is queued on (bsc#1218447).\n- CVE-2023-7042: Fixed a null-pointer-dereference in ath10k_wmi_tlv_op_pull_mgmt_tx_compl_ev() (bsc#1218336).\n- CVE-2023-7192: Fixed a memory leak problem in ctnetlink_create_conntrack in net/netfilter/nf_conntrack_netlink.c (bsc#1218479).\n- CVE-2024-22099: Fixed a null-pointer-dereference in rfcomm_check_security (bsc#1219170).\n- CVE-2024-26600: Fixed NULL pointer dereference for SRP in phy-omap-usb2 (bsc#1220340).\n- CVE-2024-26614: Fixed the initialization of accept_queue's spinlocks (bsc#1221293).\n- CVE-2024-26642: Fixed the set of anonymous timeout flag in netfilter nf_tables (bsc#1221830).\n- CVE-2024-26704: Fixed a double-free of blocks due to wrong extents moved_len in ext4 (bsc#1222422).\n- CVE-2024-26733: Fixed an overflow in arp_req_get() in arp (bsc#1222585).\n\n\nThe following non-security bugs were fixed:\n\n- fs,hugetlb: fix NULL pointer dereference in hugetlbs_fill_super (bsc#1219264).\n- tty: n_gsm: require CAP_NET_ADMIN to attach N_GSM0710 ldisc (bsc#1222619).\n- group-source-files.pl: Quote filenames (boo#1221077).\n- kernel-binary: certs: Avoid trailing space\n- mm: fix gup_pud_range (bsc#1220824).\n","status":"published","published":"2024-05-03T07:36:42Z","modified":"2026-02-04T04:18:36.299328Z","updated_at":"2026-11-02T15:53:54.652421Z"},{"id":"SUSE-SU-2025:02846-1","title":"Security update for the Linux Kernel","description":"\nThe SUSE Linux Enterprise 12 SP5 kernel was updated to receive various security bugfixes.\n\n\nThe following security bugs were fixed:\n\n- CVE-2021-46984: Fixed an out of bounds access in kyber_bio_merge() in kyber (bsc#1220631).\n- CVE-2021-46987: btrfs: fix deadlock when cloning inline extents and using qgroups (bsc#1220704).\n- CVE-2022-4129: Fixed a denial of service with the Layer 2 Tunneling Protocol (L2TP). A missing lock when clearing sk_user_data can lead to a race condition and NULL pointer dereference (bsc#1205711).\n- CVE-2022-49138: Bluetooth: hci_event: Fix checking conn for le_conn_complete_evt (bsc#1238160).\n- CVE-2022-49319: iommu/arm-smmu-v3: check return value after calling platform_get_resource() (bsc#1238374).\n- CVE-2022-49323: iommu/arm-smmu: fix possible null-ptr-deref in arm_smmu_device_probe() (bsc#1238400).\n- CVE-2022-49768: 9p/fd: fix issue of list_del corruption in p9_fd_cancel() (bsc#1242446).\n- CVE-2022-49825: ata: libata-transport: fix error handling in ata_tport_add() (bsc#1242548).\n- CVE-2022-49934: wifi: mac80211: Fix UAF in ieee80211_scan_rx() (bsc#1245051).\n- CVE-2022-49948: vt: Clear selection before changing the font (bsc#1245058).\n- CVE-2022-49969: drm/amd/display: clear optc underflow before turn off odm clock (bsc#1245060).\n- CVE-2022-49993: loop: Check for overflow while configuring loop (bsc#1245121).\n- CVE-2022-50025: cxl: Fix a memory leak in an error handling path (bsc#1245132).\n- CVE-2022-50027: scsi: lpfc: Fix possible memory leak when failing to issue CMF WQE (bsc#1245073).\n- CVE-2022-50030: scsi: lpfc: Prevent buffer overflow crashes in debugfs with malformed user input (bsc#1245265).\n- CVE-2022-50033: usb: host: ohci-ppc-of: Fix refcount leak bug (bsc#1245139).\n- CVE-2022-50103: sched, cpuset: Fix dl_cpu_busy() panic due to empty cs-\u003ecpus_allowed (bsc#1244840).\n- CVE-2022-50149: driver core: fix potential deadlock in __driver_attach (bsc#1244883).\n- CVE-2022-50226: crypto: ccp - Use kzalloc for sev ioctl interfaces to prevent kernel memory leak (bsc#1244860).\n- CVE-2023-2176: Fixed an out-of-boundary read in compare_netdev_and_ip in drivers/infiniband/core/cma.c in RDMA (bsc#1210629).\n- CVE-2023-52878: can: dev: can_put_echo_skb(): do not crash kernel if can_priv::echo_skb is accessed out of bounds (bsc#1225000).\n- CVE-2023-53020: l2tp: close all race conditions in l2tp_tunnel_register() (bsc#1240224).\n- CVE-2023-53117: fs: prevent out-of-bounds array speculation when closing a file descriptor (bsc#1242780).\n- CVE-2023-53118: scsi: core: Fix a procfs host directory removal regression (bsc#1242365).\n- CVE-2024-26974: crypto: qat - resolve race condition during AER recovery (bsc#1223638).\n- CVE-2024-26982: Fixed Squashfs inode number check not to be an invalid value of zero (bsc#1223634).\n- CVE-2024-44963: btrfs: do not BUG_ON() when freeing tree block after error (bsc#1230216).\n- CVE-2024-46713: kabi fix for perf/aux: Fix AUX buffer serialization (bsc#1230581).\n- CVE-2024-49861: net: clear the dst when changing skb protocol (bsc#1245954).\n- CVE-2025-21731: nbd: do not allow reconnect after disconnect (bsc#1237881).\n- CVE-2025-21928: HID: intel-ish-hid: Fix use-after-free issue in ishtp_hid_remove() (bsc#1240722).\n- CVE-2025-23163: net: vlan: do not propagate flags on open (bsc#1242837).\n- CVE-2025-37856: btrfs: harden block_group::bg_list against list_del() races (bsc#1243068).\n- CVE-2025-37885: KVM: x86: Reset IRTE to host control if *new* route isn't postable (bsc#1242960).\n- CVE-2025-37920: kABI workaround for xsk: Fix race condition in AF_XDP generic RX path (bsc#1243479).\n- CVE-2025-38034: btrfs: correct the order of prelim_ref arguments in btrfs__prelim_ref (bsc#1244792).\n- CVE-2025-38035: nvmet-tcp: do not restore null sk_state_change (bsc#1244801).\n- CVE-2025-38040: serial: mctrl_gpio: split disable_ms into sync and no_sync APIs (bsc#1245078).\n- CVE-2025-38051: smb: client: Fix use-after-free in cifs_fill_dirent (bsc#1244750).\n- CVE-2025-38058: __legitimize_mnt(): check for MNT_SYNC_UMOUNT should be under mount_lock (bsc#1245151).\n- CVE-2025-38064: virtio: break and reset virtio devices on device_shutdown() (bsc#1245201).\n- CVE-2025-38068: crypto: lzo - Fix compression buffer overrun (bsc#1245210).\n- CVE-2025-38074: vhost-scsi: protect vq-\u003elog_used with vq-\u003emutex (bsc#1244735).\n- CVE-2025-38079: crypto: algif_hash - fix double free in hash_accept (bsc#1245217).\n- CVE-2025-38094: net: cadence: macb: Fix a possible deadlock in macb_halt_tx (bsc#1245649).\n- CVE-2025-38105: ALSA: usb-audio: Kill timer properly at removal (bsc#1245682).\n- CVE-2025-38108: net_sched: red: fix a race in __red_change() (bsc#1245675).\n- CVE-2025-38112: net: Fix TOCTOU issue in sk_is_readable() (bsc#1245668).\n- CVE-2025-38115: net_sched: sch_sfq: fix a potential crash on gso_skb handling (bsc#1245689).\n- CVE-2025-38126: net: stmmac: make sure that ptp_rate is not 0 before configuring timestamping (bsc#1245708).\n- CVE-2025-38147: calipso: unlock rcu before returning -EAFNOSUPPORT (bsc#1245768).\n- CVE-2025-38157: wifi: ath9k_htc: Abort software beacon handling if disabled (bsc#1245747).\n- CVE-2025-38161: RDMA/mlx5: Fix error flow upon firmware failure for RQ destruction (bsc#1245777).\n- CVE-2025-38166: bpf: fix ktls panic with sockmap (bsc#1245758).\n- CVE-2025-38180: net: atm: fix /proc/net/atm/lec handling (bsc#1245970).\n- CVE-2025-38181: calipso: Fix null-ptr-deref in calipso_req_{set,del}attr() (bsc#1246000).\n- CVE-2025-38193: net_sched: sch_sfq: reject invalid perturb period (bsc#1245945).\n- CVE-2025-38198: fbcon: Make sure modelist not set on unregistered console (bsc#1245952).\n- CVE-2025-38200: i40e: fix MMIO write access to an invalid page in i40e_clear_hw (bsc#1246045).\n- CVE-2025-38211: RDMA/iwcm: Fix use-after-free of work objects after cm_id destruction (bsc#1246008).\n- CVE-2025-38212: ipc: fix to protect IPCS lookups using RCU (bsc#1246029).\n- CVE-2025-38213: vgacon: Add check for vc_origin address range in vgacon_scroll() (bsc#1246037).\n- CVE-2025-38222: ext4: inline: fix len overflow in ext4_prepare_inline_data (bsc#1245976).\n- CVE-2025-38249: ALSA: usb-audio: Fix out-of-bounds read in snd_usb_get_audioformat_uac3() (bsc#1246171).\n- CVE-2025-38250: kABI workaround for bluetooth hci_dev changes (bsc#1246182).\n- CVE-2025-38264: llist: add interface to check if a node is on a list (bsc#1246387).\n- CVE-2025-38312: fbdev: core: fbcvt: avoid division by 0 in fb_cvt_hperiod() (bsc#1246386).\n- CVE-2025-38319: drm/amd/pp: Fix potential NULL pointer dereference in atomctrl_initialize_mc_reg_table (bsc#1246243).\n- CVE-2025-38323: net: atm: add lec_mutex (bsc#1246473).\n- CVE-2025-38337: jbd2: fix data-race and null-ptr-deref in jbd2_journal_dirty_metadata() (bsc#1246253).\n- CVE-2025-38350: net/sched: Always pass notifications when child class becomes empty (bsc#1246781).\n- CVE-2025-38375: virtio-net: ensure the received length does not exceed allocated size (bsc#1247177).\n- CVE-2025-38391: usb: typec: altmodes/displayport: do not index invalid pin_assignments (bsc#1247181).\n- CVE-2025-38403: vsock/vmci: Clear the vmci transport packet properly when initializing it (bsc#1247141).\n- CVE-2025-38415: Squashfs: check return result of sb_min_blocksize (bsc#1247147).\n- CVE-2025-38420: wifi: carl9170: do not ping device which has failed to load firmware (bsc#1247279).\n- CVE-2025-38468: net/sched: Return NULL when htb_lookup_leaf encounters an empty rbtree (bsc#1247437).\n- CVE-2025-38477: net/sched: sch_qfq: Avoid triggering might_sleep in atomic context in qfq_delete_class (bsc#1247314).\n- CVE-2025-38494: HID: core: do not bypass hid_hw_raw_request (bsc#1247349).\n- CVE-2025-38495: HID: core: ensure the allocated report buffer can contain the reserved report ID (bsc#1247348).\n\nThe following non-security bugs were fixed:\n\n- RDMA/core: Always release restrack object (git-fixes)\n- bdi: Fix up kabi for dev_name addition (bsc#1171844).\n- bdi: add a -\u003edev_name field to struct backing_dev_info (bsc#1171844).\n- l2tp: Do not sleep and disable BH under writer-side sk_callback_lock (git-fixes).\n- l2tp: fix a sock refcnt leak in l2tp_tunnel_register (git-fixes).\n- scsi: core: Fix a source code comment (git-fixes).\n- scsi: core: Fix unremoved procfs host directory regression (git-fixes).\n- scsi: drivers: base: Propagate errors through the transport component (bsc#1242548)\n- scsi: drivers: base: Support atomic version of attribute_container_device_trigger (bsc#1242548)\n- virtgpu: do not reset on shutdown (git-fixes).\n","status":"published","published":"2025-08-18T15:47:45Z","modified":"2026-02-04T03:59:07.214191Z","updated_at":"2026-11-02T15:53:57.111474Z"}]}}