{"id":"CVE-2024-41085","aliases":["AZL-48057","BELL-CVE-2024-41085","DEBIAN-CVE-2024-41085","EUVD-2024-38882","GHSA-2qvq-p8h3-vf5j","OESA-2024-1960","RHSA-2024:9315","SUSE-SU-2025:02254-1","SUSE-SU-2025:02307-1","SUSE-SU-2025:02333-1","UBUNTU-CVE-2024-41085","USN-7089-1","USN-7089-2","USN-7089-3","USN-7089-4","USN-7089-5","USN-7089-6","USN-7089-7","USN-7090-1","USN-7095-1","USN-7156-1"],"status":"published","title":"cxl/mem: Fix no cxl_nvd during pmem region auto-assembling","description":"In the Linux kernel, the following vulnerability has been resolved:\n\ncxl/mem: Fix no cxl_nvd during pmem region auto-assembling\n\nWhen CXL subsystem is auto-assembling a pmem region during cxl\nendpoint port probing, always hit below calltrace.\n\n BUG: kernel NULL pointer dereference, address: 0000000000000078\n #PF: supervisor read access in kernel mode\n #PF: error_code(0x0000) - not-present page\n RIP: 0010:cxl_pmem_region_probe+0x22e/0x360 [cxl_pmem]\n Call Trace:\n  \u003cTASK\u003e\n  ? __die+0x24/0x70\n  ? page_fault_oops+0x82/0x160\n  ? do_user_addr_fault+0x65/0x6b0\n  ? exc_page_fault+0x7d/0x170\n  ? asm_exc_page_fault+0x26/0x30\n  ? cxl_pmem_region_probe+0x22e/0x360 [cxl_pmem]\n  ? cxl_pmem_region_probe+0x1ac/0x360 [cxl_pmem]\n  cxl_bus_probe+0x1b/0x60 [cxl_core]\n  really_probe+0x173/0x410\n  ? __pfx___device_attach_driver+0x10/0x10\n  __driver_probe_device+0x80/0x170\n  driver_probe_device+0x1e/0x90\n  __device_attach_driver+0x90/0x120\n  bus_for_each_drv+0x84/0xe0\n  __device_attach+0xbc/0x1f0\n  bus_probe_device+0x90/0xa0\n  device_add+0x51c/0x710\n  devm_cxl_add_pmem_region+0x1b5/0x380 [cxl_core]\n  cxl_bus_probe+0x1b/0x60 [cxl_core]\n\nThe cxl_nvd of the memdev needs to be available during the pmem region\nprobe. Currently the cxl_nvd is registered after the endpoint port probe.\nThe endpoint probe, in the case of autoassembly of regions, can cause a\npmem region probe requiring the not yet available cxl_nvd. Adjust the\nsequence so this dependency is met.\n\nThis requires adding a port parameter to cxl_find_nvdimm_bridge() that\ncan be used to query the ancestor root port. The endpoint port is not\nyet available, but will share a common ancestor with its parent, so\nstart the query from there instead.","severity":{"version":"3.1","score":5.5,"vector":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H","level":"medium","assessor":"primary","from":"nvd"},"epss":{"day":"2026-11-11","score":0.00243,"percentile":0.15603,"model":"v2026.06.15"},"facts":{"in_kev":false,"known_exploited":false,"public_exploit":false,"fix_available":true},"cwes":["CWE-476"],"published":"2024-07-29T15:48:01Z","modified":"2026-11-05T14:17:02Z","fixes":[{"ecosystem":"Alpaquita:25","package":"linux-lts","fixed_in":["6.12.41-r0"],"sources":["osv"]},{"ecosystem":"Alpaquita:stream","package":"linux-lts","fixed_in":["6.12.41-r0"],"sources":["osv"]},{"ecosystem":"Linux","package":"Kernel","fixed_in":["6.6.158","6.9.8"],"sources":["osv"]},{"ecosystem":"Debian:13","package":"linux","fixed_in":["6.9.8-1"],"sources":["osv"]},{"ecosystem":"Debian:14","package":"linux","fixed_in":["6.9.8-1"],"sources":["osv"]},{"ecosystem":"Ubuntu:22.04:LTS","package":"linux-aws-6.8","fixed_in":["6.8.0-1018.19~22.04.1"],"sources":["osv"]},{"ecosystem":"Ubuntu:22.04:LTS","package":"linux-azure-6.8","fixed_in":["6.8.0-1017.20~22.04.1"],"sources":["osv"]},{"ecosystem":"Ubuntu:22.04:LTS","package":"linux-gcp-6.8","fixed_in":["6.8.0-1017.19~22.04.1"],"sources":["osv"]},{"ecosystem":"Ubuntu:22.04:LTS","package":"linux-hwe-6.8","fixed_in":["6.8.0-48.48~22.04.1"],"sources":["osv"]},{"ecosystem":"Ubuntu:22.04:LTS","package":"linux-lowlatency-hwe-6.8","fixed_in":["6.8.0-48.48.3~22.04.1"],"sources":["osv"]},{"ecosystem":"Ubuntu:22.04:LTS","package":"linux-nvidia-6.8","fixed_in":["6.8.0-1017.19~22.04.1"],"sources":["osv"]},{"ecosystem":"Ubuntu:22.04:LTS","package":"linux-oracle-6.8","fixed_in":["6.8.0-1015.15~22.04.1"],"sources":["osv"]},{"ecosystem":"Ubuntu:22.04:LTS","package":"linux-riscv-6.8","fixed_in":["6.8.0-48.48.1~22.04.2"],"sources":["osv"]},{"ecosystem":"Ubuntu:24.04:LTS","package":"linux","fixed_in":["6.8.0-48.48"],"sources":["osv"]},{"ecosystem":"Ubuntu:24.04:LTS","package":"linux-aws","fixed_in":["6.8.0-1018.20"],"sources":["osv"]},{"ecosystem":"Ubuntu:24.04:LTS","package":"linux-azure","fixed_in":["6.8.0-1017.20"],"sources":["osv"]},{"ecosystem":"Ubuntu:24.04:LTS","package":"linux-gcp","fixed_in":["6.8.0-1017.19"],"sources":["osv"]},{"ecosystem":"Ubuntu:24.04:LTS","package":"linux-gke","fixed_in":["6.8.0-1013.17"],"sources":["osv"]},{"ecosystem":"Ubuntu:24.04:LTS","package":"linux-gkeop","fixed_in":["6.8.0-1002.4"],"sources":["osv"]},{"ecosystem":"Ubuntu:24.04:LTS","package":"linux-ibm","fixed_in":["6.8.0-1015.15"],"sources":["osv"]},{"ecosystem":"Ubuntu:24.04:LTS","package":"linux-lowlatency","fixed_in":["6.8.0-48.48.3"],"sources":["osv"]},{"ecosystem":"Ubuntu:24.04:LTS","package":"linux-nvidia","fixed_in":["6.8.0-1017.19"],"sources":["osv"]},{"ecosystem":"Ubuntu:24.04:LTS","package":"linux-nvidia-lowlatency","fixed_in":["6.8.0-1017.19.1"],"sources":["osv"]},{"ecosystem":"Ubuntu:24.04:LTS","package":"linux-oem-6.8","fixed_in":["6.8.0-1016.16"],"sources":["osv"]},{"ecosystem":"Ubuntu:24.04:LTS","package":"linux-oracle","fixed_in":["6.8.0-1015.16"],"sources":["osv"]},{"ecosystem":"Ubuntu:24.04:LTS","package":"linux-raspi","fixed_in":["6.8.0-1014.16"],"sources":["osv"]},{"ecosystem":"Ubuntu:24.04:LTS","package":"linux-riscv","fixed_in":["6.8.0-48.48.1"],"sources":["osv"]},{"ecosystem":"Ubuntu:Pro:Realtime:24.04:LTS","package":"linux-raspi-realtime","fixed_in":["6.8.0-2013.14"],"sources":["osv"]},{"ecosystem":"Ubuntu:Pro:Realtime:24.04:LTS","package":"linux-realtime","fixed_in":["6.8.1-1011.11"],"sources":["osv"]}],"affected":[{"source":"osv","ecosystem":"Azure Linux:3","package":"kernel","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"last_affected":"6.6.161.1-1"}]}]},{"source":"osv","ecosystem":"Alpaquita:25","package":"linux-lts","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"6.6.89-r0"},{"fixed":"6.12.41-r0"}]}]},{"source":"osv","ecosystem":"Alpaquita:stream","package":"linux-lts","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"6.6.100-r0"},{"fixed":"6.12.41-r0"}]}]},{"source":"osv","ecosystem":"Linux","package":"Kernel","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"6.2.0"},{"fixed":"6.6.158"}]},{"type":"ECOSYSTEM","events":[{"introduced":"6.7.0"},{"fixed":"6.9.8"}]}]},{"source":"osv","ecosystem":"Debian:13","package":"linux","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.9.8-1"}]}]},{"source":"osv","ecosystem":"Debian:14","package":"linux","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.9.8-1"}]}]},{"source":"osv","ecosystem":"openEuler:24.03-LTS","package":"kernel","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.6.0-37.0.0.44.oe2403"}]}],"bundled":78},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::appstream","package":"bpftool-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:7.4.0-503.11.1.el9_5"}]}],"bundled":594},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::appstream","package":"kernel-64k-debug-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-503.11.1.el9_5"}]}],"bundled":594},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::appstream","package":"kernel-64k-debug-devel","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-503.11.1.el9_5"}]}],"bundled":594},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::appstream","package":"kernel-64k-debug-devel-matched","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-503.11.1.el9_5"}]}],"bundled":594},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::appstream","package":"kernel-64k-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-503.11.1.el9_5"}]}],"bundled":594},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::appstream","package":"kernel-64k-devel","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-503.11.1.el9_5"}]}],"bundled":594},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::appstream","package":"kernel-64k-devel-matched","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-503.11.1.el9_5"}]}],"bundled":594},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::appstream","package":"kernel-debug-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-503.11.1.el9_5"}]}],"bundled":594},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::appstream","package":"kernel-debug-devel","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-503.11.1.el9_5"}]}],"bundled":594},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::appstream","package":"kernel-debug-devel-matched","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-503.11.1.el9_5"}]}],"bundled":594},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::appstream","package":"kernel-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-503.11.1.el9_5"}]}],"bundled":594},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::appstream","package":"kernel-debuginfo-common-aarch64","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-503.11.1.el9_5"}]}],"bundled":594},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::appstream","package":"kernel-debuginfo-common-ppc64le","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-503.11.1.el9_5"}]}],"bundled":594},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::appstream","package":"kernel-debuginfo-common-s390x","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-503.11.1.el9_5"}]}],"bundled":594},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::appstream","package":"kernel-debuginfo-common-x86_64","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-503.11.1.el9_5"}]}],"bundled":594},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::appstream","package":"kernel-devel","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-503.11.1.el9_5"}]}],"bundled":594},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::appstream","package":"kernel-devel-matched","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-503.11.1.el9_5"}]}],"bundled":594},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::appstream","package":"kernel-doc","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-503.11.1.el9_5"}]}],"bundled":594},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::appstream","package":"kernel-rt-debug-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-503.11.1.el9_5"}]}],"bundled":594},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::appstream","package":"kernel-rt-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-503.11.1.el9_5"}]}],"bundled":594},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::appstream","package":"kernel-tools-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-503.11.1.el9_5"}]}],"bundled":594},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::appstream","package":"kernel-zfcpdump-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-503.11.1.el9_5"}]}],"bundled":594},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::appstream","package":"kernel-zfcpdump-devel","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-503.11.1.el9_5"}]}],"bundled":594},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::appstream","package":"kernel-zfcpdump-devel-matched","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-503.11.1.el9_5"}]}],"bundled":594},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::appstream","package":"libperf-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-503.11.1.el9_5"}]}],"bundled":594},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::appstream","package":"perf","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-503.11.1.el9_5"}]}],"bundled":594},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::appstream","package":"perf-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-503.11.1.el9_5"}]}],"bundled":594},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::appstream","package":"python3-perf-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-503.11.1.el9_5"}]}],"bundled":594},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::appstream","package":"rtla","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-503.11.1.el9_5"}]}],"bundled":594},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::appstream","package":"rv","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-503.11.1.el9_5"}]}],"bundled":594},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::baseos","package":"bpftool","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:7.4.0-503.11.1.el9_5"}]}],"bundled":594},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::baseos","package":"bpftool-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:7.4.0-503.11.1.el9_5"}]}],"bundled":594},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::baseos","package":"kernel","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-503.11.1.el9_5"}]}],"bundled":594},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::baseos","package":"kernel-64k","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-503.11.1.el9_5"}]}],"bundled":594},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::baseos","package":"kernel-64k-core","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-503.11.1.el9_5"}]}],"bundled":594},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::baseos","package":"kernel-64k-debug","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-503.11.1.el9_5"}]}],"bundled":594},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::baseos","package":"kernel-64k-debug-core","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-503.11.1.el9_5"}]}],"bundled":594},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::baseos","package":"kernel-64k-debug-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-503.11.1.el9_5"}]}],"bundled":594},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::baseos","package":"kernel-64k-debug-modules","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-503.11.1.el9_5"}]}],"bundled":594},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::baseos","package":"kernel-64k-debug-modules-core","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-503.11.1.el9_5"}]}],"bundled":594},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::baseos","package":"kernel-64k-debug-modules-extra","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-503.11.1.el9_5"}]}],"bundled":594},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::baseos","package":"kernel-64k-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-503.11.1.el9_5"}]}],"bundled":594},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::baseos","package":"kernel-64k-modules","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-503.11.1.el9_5"}]}],"bundled":594},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::baseos","package":"kernel-64k-modules-core","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-503.11.1.el9_5"}]}],"bundled":594},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::baseos","package":"kernel-64k-modules-extra","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-503.11.1.el9_5"}]}],"bundled":594},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::baseos","package":"kernel-abi-stablelists","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-503.11.1.el9_5"}]}],"bundled":594},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::baseos","package":"kernel-core","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-503.11.1.el9_5"}]}],"bundled":594},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::baseos","package":"kernel-debug","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-503.11.1.el9_5"}]}],"bundled":594},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::baseos","package":"kernel-debug-core","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-503.11.1.el9_5"}]}],"bundled":594},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::baseos","package":"kernel-debug-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-503.11.1.el9_5"}]}],"bundled":594},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::baseos","package":"kernel-debug-modules","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-503.11.1.el9_5"}]}],"bundled":594},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::baseos","package":"kernel-debug-modules-core","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-503.11.1.el9_5"}]}],"bundled":594},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::baseos","package":"kernel-debug-modules-extra","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-503.11.1.el9_5"}]}],"bundled":594},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::baseos","package":"kernel-debug-uki-virt","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-503.11.1.el9_5"}]}],"bundled":594},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::baseos","package":"kernel-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-503.11.1.el9_5"}]}],"bundled":594},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::baseos","package":"kernel-debuginfo-common-aarch64","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-503.11.1.el9_5"}]}],"bundled":594},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::baseos","package":"kernel-debuginfo-common-ppc64le","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-503.11.1.el9_5"}]}],"bundled":594},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::baseos","package":"kernel-debuginfo-common-s390x","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-503.11.1.el9_5"}]}],"bundled":594},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::baseos","package":"kernel-debuginfo-common-x86_64","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-503.11.1.el9_5"}]}],"bundled":594},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::baseos","package":"kernel-modules","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-503.11.1.el9_5"}]}],"bundled":594},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::baseos","package":"kernel-modules-core","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-503.11.1.el9_5"}]}],"bundled":594},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::baseos","package":"kernel-modules-extra","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-503.11.1.el9_5"}]}],"bundled":594},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::baseos","package":"kernel-rt-debug-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-503.11.1.el9_5"}]}],"bundled":594},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::baseos","package":"kernel-rt-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-503.11.1.el9_5"}]}],"bundled":594},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::baseos","package":"kernel-tools","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-503.11.1.el9_5"}]}],"bundled":594},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::baseos","package":"kernel-tools-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-503.11.1.el9_5"}]}],"bundled":594},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::baseos","package":"kernel-tools-libs","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-503.11.1.el9_5"}]}],"bundled":594},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::baseos","package":"kernel-uki-virt","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-503.11.1.el9_5"}]}],"bundled":594},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::baseos","package":"kernel-uki-virt-addons","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-503.11.1.el9_5"}]}],"bundled":594},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::baseos","package":"kernel-zfcpdump","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-503.11.1.el9_5"}]}],"bundled":594},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::baseos","package":"kernel-zfcpdump-core","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-503.11.1.el9_5"}]}],"bundled":594},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::baseos","package":"kernel-zfcpdump-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-503.11.1.el9_5"}]}],"bundled":594},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::baseos","package":"kernel-zfcpdump-modules","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-503.11.1.el9_5"}]}],"bundled":594},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::baseos","package":"kernel-zfcpdump-modules-core","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-503.11.1.el9_5"}]}],"bundled":594},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::baseos","package":"kernel-zfcpdump-modules-extra","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-503.11.1.el9_5"}]}],"bundled":594},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::baseos","package":"libperf-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-503.11.1.el9_5"}]}],"bundled":594},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::baseos","package":"perf-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-503.11.1.el9_5"}]}],"bundled":594},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::baseos","package":"python3-perf","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-503.11.1.el9_5"}]}],"bundled":594},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::baseos","package":"python3-perf-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-503.11.1.el9_5"}]}],"bundled":594},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::crb","package":"bpftool-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:7.4.0-503.11.1.el9_5"}]}],"bundled":594},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::crb","package":"kernel-64k-debug-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-503.11.1.el9_5"}]}],"bundled":594},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::crb","package":"kernel-64k-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-503.11.1.el9_5"}]}],"bundled":594},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::crb","package":"kernel-debug-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-503.11.1.el9_5"}]}],"bundled":594},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::crb","package":"kernel-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-503.11.1.el9_5"}]}],"bundled":594},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::crb","package":"kernel-debuginfo-common-aarch64","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-503.11.1.el9_5"}]}],"bundled":594},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::crb","package":"kernel-debuginfo-common-ppc64le","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-503.11.1.el9_5"}]}],"bundled":594},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::crb","package":"kernel-debuginfo-common-s390x","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-503.11.1.el9_5"}]}],"bundled":594},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::crb","package":"kernel-debuginfo-common-x86_64","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-503.11.1.el9_5"}]}],"bundled":594},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::crb","package":"kernel-rt-debug-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-503.11.1.el9_5"}]}],"bundled":594},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::crb","package":"kernel-rt-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-503.11.1.el9_5"}]}],"bundled":594},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::crb","package":"kernel-tools-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-503.11.1.el9_5"}]}],"bundled":594},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::crb","package":"kernel-tools-libs-devel","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-503.11.1.el9_5"}]}],"bundled":594},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::crb","package":"kernel-zfcpdump-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-503.11.1.el9_5"}]}],"bundled":594},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::crb","package":"libperf","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-503.11.1.el9_5"}]}],"bundled":594},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::crb","package":"libperf-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-503.11.1.el9_5"}]}],"bundled":594},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::crb","package":"perf-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-503.11.1.el9_5"}]}],"bundled":594},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::crb","package":"python3-perf-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-503.11.1.el9_5"}]}],"bundled":594},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::nfv","package":"bpftool-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:7.4.0-503.11.1.el9_5"}]}],"bundled":594},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::nfv","package":"kernel-debug-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-503.11.1.el9_5"}]}],"bundled":594},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::nfv","package":"kernel-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-503.11.1.el9_5"}]}],"bundled":594},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::nfv","package":"kernel-debuginfo-common-x86_64","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-503.11.1.el9_5"}]}],"bundled":594},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::nfv","package":"kernel-rt","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-503.11.1.el9_5"}]}],"bundled":594},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::nfv","package":"kernel-rt-core","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-503.11.1.el9_5"}]}],"bundled":594},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::nfv","package":"kernel-rt-debug","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-503.11.1.el9_5"}]}],"bundled":594},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::nfv","package":"kernel-rt-debug-core","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-503.11.1.el9_5"}]}],"bundled":594},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::nfv","package":"kernel-rt-debug-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-503.11.1.el9_5"}]}],"bundled":594},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::nfv","package":"kernel-rt-debug-devel","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-503.11.1.el9_5"}]}],"bundled":594},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::nfv","package":"kernel-rt-debug-kvm","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-503.11.1.el9_5"}]}],"bundled":594},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::nfv","package":"kernel-rt-debug-modules","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-503.11.1.el9_5"}]}],"bundled":594},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::nfv","package":"kernel-rt-debug-modules-core","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-503.11.1.el9_5"}]}],"bundled":594},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::nfv","package":"kernel-rt-debug-modules-extra","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-503.11.1.el9_5"}]}],"bundled":594},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::nfv","package":"kernel-rt-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-503.11.1.el9_5"}]}],"bundled":594},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::nfv","package":"kernel-rt-devel","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-503.11.1.el9_5"}]}],"bundled":594},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::nfv","package":"kernel-rt-kvm","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-503.11.1.el9_5"}]}],"bundled":594},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::nfv","package":"kernel-rt-modules","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-503.11.1.el9_5"}]}],"bundled":594},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::nfv","package":"kernel-rt-modules-core","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-503.11.1.el9_5"}]}],"bundled":594},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::nfv","package":"kernel-rt-modules-extra","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-503.11.1.el9_5"}]}],"bundled":594},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::nfv","package":"kernel-tools-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-503.11.1.el9_5"}]}],"bundled":594},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::nfv","package":"libperf-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-503.11.1.el9_5"}]}],"bundled":594},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::nfv","package":"perf-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-503.11.1.el9_5"}]}],"bundled":594},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::nfv","package":"python3-perf-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-503.11.1.el9_5"}]}],"bundled":594},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::realtime","package":"bpftool-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:7.4.0-503.11.1.el9_5"}]}],"bundled":594},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::realtime","package":"kernel-debug-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-503.11.1.el9_5"}]}],"bundled":594},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::realtime","package":"kernel-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-503.11.1.el9_5"}]}],"bundled":594},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::realtime","package":"kernel-debuginfo-common-x86_64","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-503.11.1.el9_5"}]}],"bundled":594},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::realtime","package":"kernel-rt","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-503.11.1.el9_5"}]}],"bundled":594},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::realtime","package":"kernel-rt-core","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-503.11.1.el9_5"}]}],"bundled":594},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::realtime","package":"kernel-rt-debug","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-503.11.1.el9_5"}]}],"bundled":594},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::realtime","package":"kernel-rt-debug-core","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-503.11.1.el9_5"}]}],"bundled":594},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::realtime","package":"kernel-rt-debug-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-503.11.1.el9_5"}]}],"bundled":594},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::realtime","package":"kernel-rt-debug-devel","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-503.11.1.el9_5"}]}],"bundled":594},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::realtime","package":"kernel-rt-debug-modules","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-503.11.1.el9_5"}]}],"bundled":594},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::realtime","package":"kernel-rt-debug-modules-core","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-503.11.1.el9_5"}]}],"bundled":594},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::realtime","package":"kernel-rt-debug-modules-extra","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-503.11.1.el9_5"}]}],"bundled":594},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::realtime","package":"kernel-rt-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-503.11.1.el9_5"}]}],"bundled":594},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::realtime","package":"kernel-rt-devel","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-503.11.1.el9_5"}]}],"bundled":594},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::realtime","package":"kernel-rt-modules","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-503.11.1.el9_5"}]}],"bundled":594},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::realtime","package":"kernel-rt-modules-core","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-503.11.1.el9_5"}]}],"bundled":594},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::realtime","package":"kernel-rt-modules-extra","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-503.11.1.el9_5"}]}],"bundled":594},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::realtime","package":"kernel-tools-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-503.11.1.el9_5"}]}],"bundled":594},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::realtime","package":"libperf-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-503.11.1.el9_5"}]}],"bundled":594},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::realtime","package":"perf-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-503.11.1.el9_5"}]}],"bundled":594},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::realtime","package":"python3-perf-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-503.11.1.el9_5"}]}],"bundled":594},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::appstream","package":"kernel-headers","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-503.11.1.el9_5"}]}],"bundled":594},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::crb","package":"kernel-cross-headers","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-503.11.1.el9_5"}]}],"bundled":594},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Module for Public Cloud 15 SP7","package":"kernel-azure","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.4.0-150700.20.6.1"}]}],"bundled":253},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Module for Public Cloud 15 SP7","package":"kernel-source-azure","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.4.0-150700.20.6.1"}]}],"bundled":253},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Module for Public Cloud 15 SP7","package":"kernel-syms-azure","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.4.0-150700.20.6.1"}]}],"bundled":253},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Module for Basesystem 15 SP7","package":"kernel-64kb","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.4.0-150700.53.6.1"}]}],"bundled":253},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Module for Basesystem 15 SP7","package":"kernel-default","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.4.0-150700.53.6.1"}]}],"bundled":253},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Module for Basesystem 15 SP7","package":"kernel-default-base","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.4.0-150700.53.6.1.150700.17.6.1"}]}],"bundled":253},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Module for Basesystem 15 SP7","package":"kernel-source","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.4.0-150700.53.6.1"}]}],"bundled":253},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Module for Basesystem 15 SP7","package":"kernel-zfcpdump","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.4.0-150700.53.6.1"}]}],"bundled":253},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Module for Development Tools 15 SP7","package":"kernel-docs","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.4.0-150700.53.6.1"}]}],"bundled":253},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Module for Development Tools 15 SP7","package":"kernel-obs-build","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.4.0-150700.53.6.1"}]}],"bundled":253},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Module for Development Tools 15 SP7","package":"kernel-source","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.4.0-150700.53.6.1"}]}],"bundled":253},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Module for Development Tools 15 SP7","package":"kernel-syms","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.4.0-150700.53.6.1"}]}],"bundled":253},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Module for Legacy 15 SP7","package":"kernel-default","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.4.0-150700.53.6.1"}]}],"bundled":253},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Live Patching 15 SP7","package":"kernel-default","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.4.0-150700.53.6.1"}]}],"bundled":253},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Live Patching 15 SP7","package":"kernel-livepatch-SLE15-SP7_Update_2","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1-150700.15.3.1"}]}],"bundled":253},{"source":"osv","ecosystem":"SUSE:Linux Enterprise High Availability Extension 15 SP7","package":"kernel-default","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.4.0-150700.53.6.1"}]}],"bundled":253},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Workstation Extension 15 SP7","package":"kernel-default","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.4.0-150700.53.6.1"}]}],"bundled":253},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Live Patching 15 SP7","package":"kernel-livepatch-SLE15-SP7-RT_Update_2","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1-150700.1.5.1"}]}],"bundled":253},{"source":"osv","ecosystem":"SUSE:Real Time Module 15 SP7","package":"kernel-rt","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.4.0-150700.7.8.1"}]}],"bundled":253},{"source":"osv","ecosystem":"SUSE:Real Time Module 15 SP7","package":"kernel-source-rt","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.4.0-150700.7.8.1"}]}],"bundled":253},{"source":"osv","ecosystem":"SUSE:Real Time Module 15 SP7","package":"kernel-syms-rt","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.4.0-150700.7.8.1"}]}],"bundled":253},{"source":"osv","ecosystem":"Ubuntu:16.04:LTS","package":"linux-hwe-edge","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["4.8.0-28.30~16.04.1","4.8.0-30.32~16.04.1","4.8.0-32.34~16.04.1","4.8.0-34.36~16.04.1","4.10.0-14.16~16.04.1","4.10.0-19.21~16.04.1","4.10.0-20.22~16.04.1","4.10.0-21.23~16.04.1","4.10.0-22.24~16.04.1","4.10.0-24.28~16.04.1","4.10.0-26.30~16.04.1","4.11.0-13.19~16.04.1","4.11.0-14.20~16.04.1","4.13.0-16.19~16.04.3","4.13.0-17.20~16.04.1","4.13.0-19.22~16.04.1","4.13.0-21.24~16.04.1","4.13.0-25.29~16.04.2","4.15.0-13.14~16.04.1","4.15.0-15.16~16.04.1","4.15.0-20.21~16.04.1","4.15.0-22.24~16.04.1","4.15.0-23.25~16.04.1"]},{"source":"osv","ecosystem":"Ubuntu:18.04:LTS","package":"linux-aws-5.0","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.0.0-1021.24~18.04.1","5.0.0-1022.25~18.04.1","5.0.0-1023.26~18.04.1","5.0.0-1024.27~18.04.1","5.0.0-1025.28","5.0.0-1027.30"]},{"source":"osv","ecosystem":"Ubuntu:18.04:LTS","package":"linux-aws-5.3","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.3.0-1016.17~18.04.1","5.3.0-1017.18~18.04.1","5.3.0-1019.21~18.04.1","5.3.0-1023.25~18.04.1","5.3.0-1028.30~18.04.1","5.3.0-1030.32~18.04.1","5.3.0-1032.34~18.04.2","5.3.0-1033.35","5.3.0-1034.36","5.3.0-1035.37"]},{"source":"osv","ecosystem":"Ubuntu:18.04:LTS","package":"linux-azure","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["4.15.0-1002.2","4.15.0-1003.3","4.15.0-1004.4","4.15.0-1008.8","4.15.0-1009.9","4.15.0-1012.12","4.15.0-1013.13","4.15.0-1014.14","4.15.0-1018.18","4.15.0-1019.19","4.15.0-1021.21","4.15.0-1022.23","4.15.0-1023.24","4.15.0-1025.26","4.15.0-1028.29","4.15.0-1030.31","4.15.0-1031.32","4.15.0-1032.33","4.15.0-1035.36","4.15.0-1036.38","4.15.0-1037.39","4.18.0-1011.11~18.04.1","4.18.0-1013.13~18.04.1","4.18.0-1014.14~18.04.1","4.18.0-1018.18~18.04.1","4.18.0-1019.19~18.04.1","4.18.0-1020.20~18.04.1","4.18.0-1023.24~18.04.1","4.18.0-1024.25~18.04.1","4.18.0-1025.27~18.04.1","5.0.0-1014.14~18.04.1","5.0.0-1016.17~18.04.1","5.0.0-1018.19~18.04.1","5.0.0-1020.21~18.04.1","5.0.0-1022.23~18.04.1","5.0.0-1023.24~18.04.1","5.0.0-1025.27~18.04.1","5.0.0-1027.29~18.04.1","5.0.0-1028.30~18.04.1","5.0.0-1029.31~18.04.1","5.0.0-1031.33","5.0.0-1032.34","5.0.0-1035.37","5.0.0-1036.38"]},{"source":"osv","ecosystem":"Ubuntu:18.04:LTS","package":"linux-azure-5.3","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.3.0-1007.8~18.04.1","5.3.0-1008.9~18.04.1","5.3.0-1009.10~18.04.1","5.3.0-1010.11~18.04.1","5.3.0-1012.13~18.04.1","5.3.0-1013.14~18.04.1","5.3.0-1016.17~18.04.1","5.3.0-1018.19~18.04.1","5.3.0-1019.20~18.04.1","5.3.0-1020.21~18.04.1","5.3.0-1022.23~18.04.1","5.3.0-1028.29~18.04.1","5.3.0-1031.32~18.04.1","5.3.0-1032.33~18.04.1","5.3.0-1034.35~18.04.1","5.3.0-1035.36"]},{"source":"osv","ecosystem":"Ubuntu:18.04:LTS","package":"linux-azure-edge","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["4.18.0-1006.6~18.04.1","4.18.0-1007.7~18.04.1","4.18.0-1008.8~18.04.1","5.0.0-1012.12~18.04.2"]},{"source":"osv","ecosystem":"Ubuntu:18.04:LTS","package":"linux-gcp","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["4.15.0-1001.1","4.15.0-1003.3","4.15.0-1005.5","4.15.0-1006.6","4.15.0-1008.8","4.15.0-1009.9","4.15.0-1010.10","4.15.0-1014.14","4.15.0-1015.15","4.15.0-1017.18","4.15.0-1018.19","4.15.0-1019.20","4.15.0-1021.22","4.15.0-1023.24","4.15.0-1024.25","4.15.0-1025.26","4.15.0-1026.27","4.15.0-1027.28","4.15.0-1028.29","4.15.0-1029.31","4.15.0-1030.32","4.15.0-1032.34","4.15.0-1033.35","4.15.0-1034.36","4.15.0-1036.38","4.15.0-1037.39","4.15.0-1040.42","4.15.0-1042.45","4.15.0-1044.70","5.0.0-1020.20~18.04.1","5.0.0-1021.21~18.04.1","5.0.0-1025.26~18.04.1","5.0.0-1026.27~18.04.1","5.0.0-1028.29~18.04.1","5.0.0-1029.30~18.04.1","5.0.0-1031.32","5.0.0-1033.34","5.0.0-1034.35"]},{"source":"osv","ecosystem":"Ubuntu:18.04:LTS","package":"linux-gcp-5.3","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.3.0-1008.9~18.04.1","5.3.0-1009.10~18.04.1","5.3.0-1010.11~18.04.1","5.3.0-1012.13~18.04.1","5.3.0-1014.15~18.04.1","5.3.0-1016.17~18.04.1","5.3.0-1017.18~18.04.1","5.3.0-1018.19~18.04.1","5.3.0-1020.22~18.04.1","5.3.0-1026.28~18.04.1","5.3.0-1029.31~18.04.1","5.3.0-1030.32~18.04.1","5.3.0-1032.34~18.04.1"]},{"source":"osv","ecosystem":"Ubuntu:18.04:LTS","package":"linux-gke-4.15","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["4.15.0-1030.32","4.15.0-1032.34","4.15.0-1033.35","4.15.0-1034.36","4.15.0-1036.38","4.15.0-1037.39","4.15.0-1040.42","4.15.0-1041.43","4.15.0-1042.44","4.15.0-1044.46","4.15.0-1045.48","4.15.0-1046.49","4.15.0-1048.51","4.15.0-1049.52","4.15.0-1050.53","4.15.0-1052.55","4.15.0-1055.58","4.15.0-1057.60","4.15.0-1058.61","4.15.0-1059.62","4.15.0-1063.66","4.15.0-1064.67","4.15.0-1066.69","4.15.0-1067.70","4.15.0-1069.72","4.15.0-1070.73","4.15.0-1072.76","4.15.0-1073.78","4.15.0-1074.79","4.15.0-1076.81","4.15.0-1077.82","4.15.0-1078.83","4.15.0-1079.84"]},{"source":"osv","ecosystem":"Ubuntu:18.04:LTS","package":"linux-gke-5.4","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.4.0-1025.25~18.04.1","5.4.0-1027.28~18.04.1","5.4.0-1029.31~18.04.1","5.4.0-1030.32~18.04.1","5.4.0-1032.34~18.04.1","5.4.0-1033.35~18.04.1","5.4.0-1035.37~18.04.1","5.4.0-1036.38~18.04.1","5.4.0-1037.39~18.04.1","5.4.0-1039.41~18.04.1","5.4.0-1040.42~18.04.1","5.4.0-1042.44~18.04.1","5.4.0-1043.45~18.04.1","5.4.0-1044.46~18.04.1","5.4.0-1046.48~18.04.1","5.4.0-1049.52~18.04.1","5.4.0-1051.54~18.04.1","5.4.0-1052.55~18.04.1","5.4.0-1053.56~18.04.1","5.4.0-1054.57~18.04.1","5.4.0-1055.58~18.04.1","5.4.0-1056.59~18.04.1","5.4.0-1057.60~18.04.1","5.4.0-1059.62~18.04.1","5.4.0-1061.64~18.04.1","5.4.0-1062.65~18.04.1","5.4.0-1063.66~18.04.1","5.4.0-1065.68~18.04.1","5.4.0-1066.69~18.04.1","5.4.0-1067.70~18.04.1","5.4.0-1068.71~18.04.1","5.4.0-1071.76~18.04.3","5.4.0-1072.77~18.04.1","5.4.0-1074.79~18.04.1","5.4.0-1076.82~18.04.1","5.4.0-1078.84~18.04.1","5.4.0-1080.86~18.04.1"]},{"source":"osv","ecosystem":"Ubuntu:18.04:LTS","package":"linux-gkeop-5.4","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.4.0-1001.1","5.4.0-1003.3","5.4.0-1004.5","5.4.0-1005.6","5.4.0-1007.8~18.04.1","5.4.0-1008.9~18.04.1","5.4.0-1009.10~18.04.1","5.4.0-1010.11~18.04.1","5.4.0-1011.12~18.04.2","5.4.0-1012.13~18.04.1","5.4.0-1013.14~18.04.1","5.4.0-1014.15~18.04.1","5.4.0-1015.16~18.04.1","5.4.0-1016.17~18.04.1","5.4.0-1018.19~18.04.1","5.4.0-1021.22~18.04.1","5.4.0-1022.23~18.04.1","5.4.0-1023.24~18.04.1","5.4.0-1024.25~18.04.1","5.4.0-1025.26~18.04.1","5.4.0-1026.27~18.04.1","5.4.0-1027.28~18.04.1","5.4.0-1029.30~18.04.2","5.4.0-1031.32~18.04.1","5.4.0-1032.33~18.04.1","5.4.0-1033.34~18.04.1","5.4.0-1034.35~18.04.1","5.4.0-1036.37~18.04.1","5.4.0-1037.38~18.04.1","5.4.0-1038.39~18.04.1","5.4.0-1039.40~18.04.1","5.4.0-1040.41~18.04.1","5.4.0-1043.44~18.04.1","5.4.0-1046.48~18.04.1","5.4.0-1048.51~18.04.1","5.4.0-1049.52~18.04.1","5.4.0-1051.54~18.04.1"]},{"source":"osv","ecosystem":"Ubuntu:18.04:LTS","package":"linux-hwe","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["4.18.0-13.14~18.04.1","4.18.0-14.15~18.04.1","4.18.0-15.16~18.04.1","4.18.0-16.17~18.04.1","4.18.0-17.18~18.04.1","4.18.0-18.19~18.04.1","4.18.0-20.21~18.04.1","4.18.0-21.22~18.04.1","4.18.0-22.23~18.04.1","4.18.0-24.25~18.04.1","4.18.0-25.26~18.04.1","5.0.0-23.24~18.04.1","5.0.0-25.26~18.04.1","5.0.0-27.28~18.04.1","5.0.0-29.31~18.04.1","5.0.0-31.33~18.04.1","5.0.0-32.34~18.04.2","5.0.0-35.38~18.04.1","5.0.0-36.39~18.04.1","5.0.0-37.40~18.04.1","5.3.0-26.28~18.04.1","5.3.0-28.30~18.04.1","5.3.0-40.32~18.04.1","5.3.0-42.34~18.04.1","5.3.0-45.37~18.04.1","5.3.0-46.38~18.04.1","5.3.0-51.44~18.04.2","5.3.0-53.47~18.04.1","5.3.0-59.53~18.04.1","5.3.0-61.55~18.04.1","5.3.0-62.56~18.04.1","5.3.0-64.58~18.04.1","5.3.0-65.59","5.3.0-66.60","5.3.0-67.61","5.3.0-68.63","5.3.0-69.65","5.3.0-70.66","5.3.0-72.68","5.3.0-73.69","5.3.0-74.70","5.3.0-75.71","5.3.0-76.72"]},{"source":"osv","ecosystem":"Ubuntu:18.04:LTS","package":"linux-oem","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["4.15.0-1002.3","4.15.0-1004.5","4.15.0-1006.9","4.15.0-1008.11","4.15.0-1009.12","4.15.0-1012.15","4.15.0-1013.16","4.15.0-1015.18","4.15.0-1017.20","4.15.0-1018.21","4.15.0-1021.24","4.15.0-1024.29","4.15.0-1026.31","4.15.0-1028.33","4.15.0-1030.35","4.15.0-1033.38","4.15.0-1034.39","4.15.0-1035.40","4.15.0-1036.41","4.15.0-1038.43","4.15.0-1039.44","4.15.0-1043.48","4.15.0-1045.50","4.15.0-1050.57","4.15.0-1056.65","4.15.0-1057.66","4.15.0-1059.68","4.15.0-1063.72","4.15.0-1064.73","4.15.0-1065.75","4.15.0-1066.76","4.15.0-1067.77","4.15.0-1069.79","4.15.0-1073.83","4.15.0-1076.86","4.15.0-1079.89","4.15.0-1080.90","4.15.0-1081.91","4.15.0-1087.97","4.15.0-1090.100","4.15.0-1091.101","4.15.0-1093.103","4.15.0-1094.104","4.15.0-1096.106","4.15.0-1097.107","4.15.0-1099.109","4.15.0-1100.110","4.15.0-1101.112","4.15.0-1102.113","4.15.0-1103.114"]},{"source":"osv","ecosystem":"Ubuntu:18.04:LTS","package":"linux-oracle-5.0","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.0.0-1007.12~18.04.1","5.0.0-1008.13~18.04.1","5.0.0-1009.14~18.04.1","5.0.0-1010.15~18.04.1","5.0.0-1011.16","5.0.0-1013.18","5.0.0-1014.19"]},{"source":"osv","ecosystem":"Ubuntu:18.04:LTS","package":"linux-oracle-5.3","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.3.0-1011.12~18.04.1","5.3.0-1013.14~18.04.1","5.3.0-1014.15~18.04.1","5.3.0-1016.18~18.04.1","5.3.0-1018.20~18.04.1","5.3.0-1024.26~18.04.1","5.3.0-1027.29~18.04.1","5.3.0-1028.30~18.04.1","5.3.0-1030.32~18.04.1"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-aws-5.11","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.11.0-1009.9~20.04.2","5.11.0-1014.15~20.04.1","5.11.0-1016.17~20.04.1","5.11.0-1017.18~20.04.1","5.11.0-1019.20~20.04.1","5.11.0-1020.21~20.04.2","5.11.0-1021.22~20.04.2","5.11.0-1022.23~20.04.1","5.11.0-1023.24~20.04.1","5.11.0-1025.27~20.04.1","5.11.0-1027.30~20.04.1","5.11.0-1028.31~20.04.1"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-aws-5.13","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.13.0-1008.9~20.04.2","5.13.0-1011.12~20.04.1","5.13.0-1012.13~20.04.1","5.13.0-1014.15~20.04.1","5.13.0-1017.19~20.04.1","5.13.0-1019.21~20.04.1","5.13.0-1021.23~20.04.2","5.13.0-1022.24~20.04.1","5.13.0-1023.25~20.04.1","5.13.0-1025.27~20.04.1","5.13.0-1028.31~20.04.1","5.13.0-1029.32~20.04.1","5.13.0-1031.35~20.04.1"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-aws-5.8","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.8.0-1035.37~20.04.1","5.8.0-1038.40~20.04.1","5.8.0-1041.43~20.04.1","5.8.0-1042.44~20.04.1"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-azure-5.11","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.11.0-1007.7~20.04.2","5.11.0-1012.13~20.04.1","5.11.0-1013.14~20.04.1","5.11.0-1015.16~20.04.1","5.11.0-1017.18~20.04.1","5.11.0-1019.20~20.04.1","5.11.0-1020.21~20.04.1","5.11.0-1021.22~20.04.1","5.11.0-1022.23~20.04.1","5.11.0-1023.24~20.04.1","5.11.0-1025.27~20.04.1","5.11.0-1027.30~20.04.1","5.11.0-1028.31~20.04.2"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-azure-5.13","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.13.0-1009.10~20.04.2","5.13.0-1012.14~20.04.1","5.13.0-1013.15~20.04.1","5.13.0-1014.16~20.04.1","5.13.0-1017.19~20.04.1","5.13.0-1021.24~20.04.1","5.13.0-1022.26~20.04.1","5.13.0-1023.27~20.04.1","5.13.0-1025.29~20.04.1","5.13.0-1028.33~20.04.1","5.13.0-1029.34~20.04.1","5.13.0-1031.37~20.04.1"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-azure-5.8","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.8.0-1033.35~20.04.1","5.8.0-1036.38~20.04.1","5.8.0-1039.42~20.04.1","5.8.0-1040.43~20.04.1","5.8.0-1041.44~20.04.1","5.8.0-1042.45~20.04.1","5.8.0-1043.46~20.04.1"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-azure-fde","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.4.0-1063.66+cvm2.2","5.4.0-1063.66+cvm3.2","5.4.0-1064.67+cvm1.1","5.4.0-1065.68+cvm2.1","5.4.0-1067.70+cvm1.1","5.4.0-1068.71+cvm1.1","5.4.0-1069.72+cvm1.1","5.4.0-1070.73+cvm1.1","5.4.0-1072.75+cvm1.1","5.4.0-1073.76+cvm1.1","5.4.0-1074.77+cvm1.1","5.4.0-1076.79+cvm1.1","5.4.0-1078.81+cvm1.1","5.4.0-1080.83+cvm1.1","5.4.0-1083.87+cvm1.1","5.4.0-1085.90+cvm1.1","5.4.0-1085.90+cvm2.1","5.4.0-1086.91+cvm1.1","5.4.0-1089.94+cvm1.2","5.4.0-1090.95+cvm1.1","5.4.0-1091.96+cvm1.1","5.4.0-1092.97+cvm1.1","5.4.0-1095.101+cvm1.1","5.4.0-1098.104+cvm1.1","5.4.0-1100.106+cvm1.1","5.4.0-1103.109+cvm1.1"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-gcp-5.11","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.11.0-1009.10~20.04.1","5.11.0-1014.16~20.04.1","5.11.0-1017.19~20.04.1","5.11.0-1018.20~20.04.2","5.11.0-1020.22~20.04.1","5.11.0-1021.23~20.04.1","5.11.0-1022.24~20.04.1","5.11.0-1023.25~20.04.1","5.11.0-1024.26~20.04.1","5.11.0-1026.29~20.04.1","5.11.0-1028.32~20.04.1","5.11.0-1029.33~20.04.3"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-gcp-5.13","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.13.0-1008.9~20.04.3","5.13.0-1012.15~20.04.1","5.13.0-1013.16~20.04.1","5.13.0-1015.18~20.04.1","5.13.0-1019.23~20.04.1","5.13.0-1021.25~20.04.1","5.13.0-1023.28~20.04.1","5.13.0-1024.29~20.04.1","5.13.0-1025.30~20.04.1","5.13.0-1027.32~20.04.1","5.13.0-1030.36~20.04.1","5.13.0-1031.37~20.04.1","5.13.0-1033.40~20.04.1"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-gcp-5.8","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.8.0-1032.34~20.04.1","5.8.0-1035.37~20.04.1","5.8.0-1038.40~20.04.1","5.8.0-1039.41"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-gke","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.4.0-1033.35","5.4.0-1035.37","5.4.0-1036.38","5.4.0-1037.39","5.4.0-1039.41","5.4.0-1041.43","5.4.0-1042.44","5.4.0-1043.45","5.4.0-1044.46","5.4.0-1046.48","5.4.0-1049.52","5.4.0-1051.54","5.4.0-1052.55","5.4.0-1053.56","5.4.0-1054.57","5.4.0-1055.58","5.4.0-1056.59","5.4.0-1057.60","5.4.0-1059.62","5.4.0-1061.64","5.4.0-1062.65","5.4.0-1063.66","5.4.0-1065.68","5.4.0-1066.69","5.4.0-1067.70","5.4.0-1068.71","5.4.0-1071.76","5.4.0-1072.77","5.4.0-1074.79","5.4.0-1076.82","5.4.0-1078.84","5.4.0-1080.86","5.4.0-1081.87","5.4.0-1083.89","5.4.0-1084.90","5.4.0-1086.93","5.4.0-1087.94","5.4.0-1090.97","5.4.0-1091.98","5.4.0-1094.101","5.4.0-1095.102","5.4.0-1096.103","5.4.0-1097.104","5.4.0-1098.105","5.4.0-1099.106","5.4.0-1100.107","5.4.0-1101.108","5.4.0-1102.109","5.4.0-1103.110","5.4.0-1104.111","5.4.0-1105.112"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-gke-5.15","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.15.0-1011.14~20.04.1","5.15.0-1014.17~20.04.1","5.15.0-1015.18~20.04.1","5.15.0-1016.19~20.04.1","5.15.0-1019.23~20.04.1","5.15.0-1020.25~20.04.1","5.15.0-1023.28~20.04.2","5.15.0-1027.32~20.04.1","5.15.0-1028.33~20.04.1","5.15.0-1029.34~20.04.1","5.15.0-1031.36~20.04.1","5.15.0-1032.37~20.04.1","5.15.0-1033.38~20.04.1","5.15.0-1034.39~20.04.1","5.15.0-1036.41~20.04.1","5.15.0-1037.42~20.04.1","5.15.0-1038.43~20.04.1","5.15.0-1039.44~20.04.1"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-hwe-5.11","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.11.0-22.23~20.04.1","5.11.0-25.27~20.04.1","5.11.0-27.29~20.04.1","5.11.0-34.36~20.04.1","5.11.0-36.40~20.04.1","5.11.0-37.41~20.04.2","5.11.0-38.42~20.04.1","5.11.0-40.44~20.04.2","5.11.0-41.45~20.04.1","5.11.0-43.47~20.04.2","5.11.0-44.48~20.04.2","5.11.0-46.51~20.04.1"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-hwe-5.13","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.13.0-21.21~20.04.1","5.13.0-22.22~20.04.1","5.13.0-23.23~20.04.2","5.13.0-25.26~20.04.1","5.13.0-27.29~20.04.1","5.13.0-28.31~20.04.1","5.13.0-30.33~20.04.1","5.13.0-35.40~20.04.1","5.13.0-37.42~20.04.1","5.13.0-39.44~20.04.1","5.13.0-40.45~20.04.1","5.13.0-41.46~20.04.1","5.13.0-44.49~20.04.1","5.13.0-48.54~20.04.1","5.13.0-51.58~20.04.1","5.13.0-52.59~20.04.1"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-hwe-5.8","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.8.0-23.24~20.04.1","5.8.0-25.26~20.04.1","5.8.0-28.30~20.04.1","5.8.0-29.31~20.04.1","5.8.0-31.33~20.04.1","5.8.0-33.36~20.04.1","5.8.0-34.37~20.04.2","5.8.0-36.40~20.04.1","5.8.0-38.43~20.04.1","5.8.0-40.45~20.04.1","5.8.0-41.46~20.04.1","5.8.0-43.49~20.04.1","5.8.0-44.50~20.04.1","5.8.0-45.51~20.04.1","5.8.0-48.54~20.04.1","5.8.0-49.55~20.04.1","5.8.0-50.56~20.04.1","5.8.0-53.60~20.04.1","5.8.0-55.62~20.04.1","5.8.0-59.66~20.04.1","5.8.0-63.71~20.04.1"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-intel-5.13","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.13.0-1007.7","5.13.0-1008.8","5.13.0-1009.9","5.13.0-1010.10","5.13.0-1011.11","5.13.0-1014.15","5.13.0-1017.19"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-oem-5.10","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.10.0-1008.9","5.10.0-1011.12","5.10.0-1013.14","5.10.0-1014.15","5.10.0-1016.17","5.10.0-1017.18","5.10.0-1019.20","5.10.0-1021.22","5.10.0-1022.23","5.10.0-1023.24","5.10.0-1025.26","5.10.0-1026.27","5.10.0-1029.30","5.10.0-1032.33","5.10.0-1033.34","5.10.0-1034.35","5.10.0-1038.40","5.10.0-1044.46","5.10.0-1045.47","5.10.0-1049.51","5.10.0-1050.52","5.10.0-1051.53","5.10.0-1052.54","5.10.0-1053.55","5.10.0-1055.58","5.10.0-1057.61"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-oem-5.13","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.13.0-1009.10","5.13.0-1010.11","5.13.0-1012.16","5.13.0-1014.18","5.13.0-1017.21","5.13.0-1019.23","5.13.0-1020.24","5.13.0-1021.25","5.13.0-1022.26","5.13.0-1026.32","5.13.0-1028.35","5.13.0-1029.36"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-oem-5.14","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.14.0-1004.4","5.14.0-1005.5","5.14.0-1007.7","5.14.0-1008.8","5.14.0-1010.10","5.14.0-1011.11","5.14.0-1013.13","5.14.0-1018.19","5.14.0-1020.22","5.14.0-1022.24","5.14.0-1024.26","5.14.0-1027.30","5.14.0-1029.32","5.14.0-1031.34","5.14.0-1032.35","5.14.0-1033.36","5.14.0-1034.37","5.14.0-1036.40","5.14.0-1038.42","5.14.0-1042.47","5.14.0-1044.49","5.14.0-1045.51","5.14.0-1046.53","5.14.0-1047.54","5.14.0-1048.55","5.14.0-1049.56","5.14.0-1050.57","5.14.0-1051.58","5.14.0-1052.59","5.14.0-1054.61","5.14.0-1055.62","5.14.0-1056.63","5.14.0-1057.64","5.14.0-1058.66","5.14.0-1059.67"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-oem-5.6","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.6.0-1007.7","5.6.0-1008.8","5.6.0-1010.10","5.6.0-1011.11","5.6.0-1013.13","5.6.0-1017.17","5.6.0-1018.18","5.6.0-1020.20","5.6.0-1021.21","5.6.0-1023.23","5.6.0-1026.26","5.6.0-1027.27","5.6.0-1028.28","5.6.0-1031.32","5.6.0-1032.33","5.6.0-1033.35","5.6.0-1034.36","5.6.0-1035.37","5.6.0-1036.39","5.6.0-1039.43","5.6.0-1042.46","5.6.0-1047.51","5.6.0-1048.52","5.6.0-1050.54","5.6.0-1052.56","5.6.0-1053.57","5.6.0-1054.58","5.6.0-1055.59","5.6.0-1056.60"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-oracle-5.11","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.11.0-1008.8~20.04.1","5.11.0-1013.14~20.04.1","5.11.0-1016.17~20.04.1","5.11.0-1017.18~20.04.1","5.11.0-1019.20~20.04.1","5.11.0-1020.21~20.04.1","5.11.0-1021.22~20.04.1","5.11.0-1022.23~20.04.1","5.11.0-1023.24~20.04.1","5.11.0-1025.27~20.04.1","5.11.0-1027.30~20.04.1","5.11.0-1028.31~20.04.1"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-oracle-5.13","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.13.0-1011.13~20.04.2","5.13.0-1015.19~20.04.1","5.13.0-1016.20~20.04.1","5.13.0-1018.22~20.04.1","5.13.0-1021.26~20.04.1","5.13.0-1025.30~20.04.1","5.13.0-1027.32~20.04.1","5.13.0-1028.33~20.04.1","5.13.0-1030.35~20.04.1","5.13.0-1033.39~20.04.1","5.13.0-1034.40~20.04.1","5.13.0-1036.43~20.04.1"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-oracle-5.8","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.8.0-1031.32~20.04.2","5.8.0-1033.34~20.04.1","5.8.0-1034.35~20.04.2","5.8.0-1037.38~20.04.1","5.8.0-1038.39~20.04.1"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-raspi2","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.3.0-1007.8","5.3.0-1014.16","5.3.0-1015.17","5.3.0-1017.19","5.4.0-1004.4","5.4.0-1006.6"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-riscv","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.4.0-24.28","5.4.0-26.30","5.4.0-27.31","5.4.0-28.32","5.4.0-30.34","5.4.0-31.35","5.4.0-33.37","5.4.0-34.38","5.4.0-36.41","5.4.0-37.42","5.4.0-39.44","5.4.0-40.45"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-riscv-5.11","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.11.0-1015.16~20.04.1","5.11.0-1017.18~20.04.1","5.11.0-1018.19~20.04.2","5.11.0-1020.21~20.04.1","5.11.0-1021.22~20.04.1","5.11.0-1022.23~20.04.1","5.11.0-1023.24~20.04.1","5.11.0-1024.25~20.04.1","5.11.0-1026.28~20.04.1","5.11.0-1028.31~20.04.1","5.11.0-1029.32~20.04.1","5.11.0-1030.34","5.11.0-1031.35"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-riscv-5.8","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.8.0-14.16~20.04.1","5.8.0-14.16~20.04.3","5.8.0-16.18~20.04.1","5.8.0-17.19~20.04.1","5.8.0-18.20~20.04.1","5.8.0-20.22~20.04.1","5.8.0-22.24~20.04.1","5.8.0-25.27~20.04.1","5.8.0-26.28~20.04.1","5.8.0-29.31~20.04.1"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-allwinner-5.19","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.19.0-1007.7~22.04.1","5.19.0-1009.9~22.04.1","5.19.0-1010.10~22.04.1","5.19.0-1011.11~22.04.1","5.19.0-1012.12~22.04.1","5.19.0-1013.13~22.04.1","5.19.0-1014.14~22.04.1","5.19.0-1015.15~22.04.1"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-aws-5.19","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.19.0-1019.20~22.04.1","5.19.0-1020.21~22.04.1","5.19.0-1022.23~22.04.1","5.19.0-1023.24~22.04.1","5.19.0-1024.25~22.04.1","5.19.0-1025.26~22.04.1","5.19.0-1026.27~22.04.1","5.19.0-1027.28~22.04.1","5.19.0-1028.29~22.04.1","5.19.0-1029.30~22.04.1"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-aws-6.2","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["6.2.0-1005.5~22.04.1","6.2.0-1006.6~22.04.1","6.2.0-1007.7~22.04.1","6.2.0-1008.8~22.04.1","6.2.0-1009.9~22.04.3","6.2.0-1010.10~22.04.1","6.2.0-1011.11~22.04.1","6.2.0-1012.12~22.04.1","6.2.0-1013.13~22.04.1","6.2.0-1014.14~22.04.1","6.2.0-1015.15~22.04.1","6.2.0-1016.16~22.04.1","6.2.0-1017.17~22.04.1","6.2.0-1018.18~22.04.1"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-aws-6.5","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["6.5.0-1008.8~22.04.1","6.5.0-1010.10~22.04.1","6.5.0-1011.11~22.04.1","6.5.0-1012.12~22.04.1","6.5.0-1014.14~22.04.1","6.5.0-1015.15~22.04.1","6.5.0-1016.16~22.04.1","6.5.0-1017.17~22.04.2","6.5.0-1018.18~22.04.1","6.5.0-1020.20~22.04.1","6.5.0-1021.21~22.04.1","6.5.0-1022.22~22.04.1","6.5.0-1023.23~22.04.1","6.5.0-1024.24~22.04.1"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-aws-6.8","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1018.19~22.04.1"}]}],"versions":["6.8.0-1009.9~22.04.2","6.8.0-1010.10~22.04.2","6.8.0-1011.12~22.04.1","6.8.0-1013.14~22.04.1","6.8.0-1014.15~22.04.1","6.8.0-1015.16~22.04.1","6.8.0-1016.17~22.04.2","6.8.0-1017.18~22.04.1"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-azure-5.19","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.19.0-1020.21~22.04.1","5.19.0-1021.22~22.04.1","5.19.0-1022.23~22.04.1","5.19.0-1023.24~22.04.1","5.19.0-1025.28~22.04.1","5.19.0-1026.29~22.04.1","5.19.0-1027.30~22.04.2"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-azure-6.2","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["6.2.0-1005.5~22.04.1","6.2.0-1006.6~22.04.1","6.2.0-1007.7~22.04.1","6.2.0-1008.8~22.04.1","6.2.0-1009.9~22.04.3","6.2.0-1011.11~22.04.1","6.2.0-1012.12~22.04.1","6.2.0-1014.14~22.04.1","6.2.0-1015.15~22.04.1","6.2.0-1016.16~22.04.1","6.2.0-1017.17~22.04.1","6.2.0-1018.18~22.04.1","6.2.0-1019.19~22.04.1"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-azure-6.5","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["6.5.0-1007.7~22.04.1","6.5.0-1009.9~22.04.1","6.5.0-1010.10~22.04.1","6.5.0-1011.11~22.04.1","6.5.0-1015.15~22.04.1","6.5.0-1016.16~22.04.1","6.5.0-1017.17~22.04.1","6.5.0-1018.19~22.04.2","6.5.0-1019.20~22.04.1","6.5.0-1021.22~22.04.1","6.5.0-1022.23~22.04.1","6.5.0-1023.24~22.04.1","6.5.0-1024.25~22.04.1","6.5.0-1025.26~22.04.1"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-azure-6.8","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1017.20~22.04.1"}]}],"versions":["6.8.0-1008.8~22.04.1","6.8.0-1009.9~22.04.1","6.8.0-1010.10~22.04.1","6.8.0-1012.14~22.04.1","6.8.0-1013.15~22.04.1","6.8.0-1014.16~22.04.1","6.8.0-1015.17~22.04.2"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-azure-fde-5.19","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.19.0-1025.28~22.04.1.1","5.19.0-1026.29~22.04.1.1","5.19.0-1027.30~22.04.2.1"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-azure-fde-6.2","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["6.2.0-1008.8~22.04.1.1","6.2.0-1009.9~22.04.3.1","6.2.0-1011.11~22.04.1.1","6.2.0-1012.12~22.04.1.1","6.2.0-1014.14~22.04.1.1","6.2.0-1015.15~22.04.1.1","6.2.0-1016.16~22.04.1.1","6.2.0-1017.17~22.04.1.1","6.2.0-1018.18~22.04.1.1","6.2.0-1019.19~22.04.1.1"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-gcp-5.19","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.19.0-1020.22~22.04.2","5.19.0-1021.23~22.04.1","5.19.0-1022.24~22.04.1","5.19.0-1024.26~22.04.1","5.19.0-1025.27~22.04.1","5.19.0-1026.28~22.04.1","5.19.0-1027.29~22.04.1","5.19.0-1030.32~22.04.1"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-gcp-6.2","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["6.2.0-1009.9~22.04.3","6.2.0-1010.10~22.04.1","6.2.0-1011.11~22.04.1","6.2.0-1011.11~22.04.3","6.2.0-1012.12~22.04.1","6.2.0-1013.13~22.04.1","6.2.0-1014.14~22.04.1","6.2.0-1016.18~22.04.1","6.2.0-1017.19~22.04.1","6.2.0-1018.20~22.04.1","6.2.0-1019.21~22.04.1","6.2.0-1021.23~22.04.1"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-gcp-6.5","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["6.5.0-1010.10~22.04.3","6.5.0-1011.11~22.04.1","6.5.0-1013.13~22.04.1","6.5.0-1014.14~22.04.1","6.5.0-1015.15~22.04.1","6.5.0-1016.16~22.04.1","6.5.0-1017.17~22.04.1","6.5.0-1018.18~22.04.1","6.5.0-1020.20~22.04.1","6.5.0-1022.24~22.04.1","6.5.0-1023.25~22.04.1","6.5.0-1024.26~22.04.1","6.5.0-1025.27~22.04.1"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-gcp-6.8","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1017.19~22.04.1"}]}],"versions":["6.8.0-1010.11~22.04.1","6.8.0-1011.12~22.04.1","6.8.0-1012.13~22.04.1","6.8.0-1013.14~22.04.1","6.8.0-1014.16~22.04.1","6.8.0-1015.17~22.04.1","6.8.0-1016.18~22.04.1"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-hwe-5.19","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.19.0-28.29~22.04.1","5.19.0-32.33~22.04.1","5.19.0-35.36~22.04.1","5.19.0-38.39~22.04.1","5.19.0-40.41~22.04.1","5.19.0-41.42~22.04.1","5.19.0-42.43~22.04.1","5.19.0-43.44~22.04.1","5.19.0-45.46~22.04.1","5.19.0-46.47~22.04.1","5.19.0-50.50"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-hwe-6.2","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["6.2.0-25.25~22.04.2","6.2.0-26.26~22.04.1","6.2.0-31.31~22.04.1","6.2.0-32.32~22.04.1","6.2.0-33.33~22.04.1","6.2.0-34.34~22.04.1","6.2.0-35.35~22.04.1","6.2.0-36.37~22.04.1","6.2.0-37.38~22.04.1","6.2.0-39.40~22.04.1"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-hwe-6.5","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["6.5.0-14.14~22.04.1","6.5.0-15.15~22.04.1","6.5.0-17.17~22.04.1","6.5.0-18.18~22.04.1","6.5.0-21.21~22.04.1","6.5.0-25.25~22.04.1","6.5.0-26.26~22.04.1","6.5.0-27.28~22.04.1","6.5.0-28.29~22.04.1","6.5.0-35.35~22.04.1","6.5.0-41.41~22.04.2","6.5.0-44.44~22.04.1","6.5.0-45.45~22.04.1"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-hwe-6.8","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-48.48~22.04.1"}]}],"versions":["6.8.0-38.38~22.04.1","6.8.0-39.39~22.04.1","6.8.0-40.40~22.04.3","6.8.0-45.45~22.04.1","6.8.0-47.47~22.04.1"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-intel-iot-realtime","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.15.0-1073.75"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-lowlatency-hwe-5.19","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.19.0-1017.18~22.04.1","5.19.0-1018.19~22.04.1","5.19.0-1021.22~22.04.1","5.19.0-1022.23~22.04.1","5.19.0-1023.24~22.04.1","5.19.0-1024.25~22.04.1","5.19.0-1025.26~22.04.1","5.19.0-1027.28~22.04.1","5.19.0-1028.29~22.04.1","5.19.0-1030.30"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-lowlatency-hwe-6.2","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["6.2.0-1008.8~22.04.1","6.2.0-1009.9~22.04.1","6.2.0-1011.11~22.04.1","6.2.0-1012.12~22.04.1","6.2.0-1013.13~22.04.1","6.2.0-1014.14~22.04.1","6.2.0-1015.15~22.04.1","6.2.0-1016.16~22.04.1","6.2.0-1017.17~22.04.1","6.2.0-1018.18~22.04.1"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-lowlatency-hwe-6.5","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["6.5.0-14.14.1~22.04.1","6.5.0-15.15.1.1~22.04.1","6.5.0-17.17.1.1.1~22.04.1","6.5.0-21.21.1~22.04.1","6.5.0-25.25.1~22.04.1","6.5.0-26.26.1~22.04.1","6.5.0-27.28.1~22.04.1","6.5.0-28.29.1~22.04.1","6.5.0-35.35.1~22.04.1","6.5.0-41.41.1~22.04.1","6.5.0-42.42.1~22.04.1","6.5.0-44.44.1~22.04.1","6.5.0-45.45.1~22.04.1"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-lowlatency-hwe-6.8","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-48.48.3~22.04.1"}]}],"versions":["6.8.0-38.38.1~22.04.2","6.8.0-40.40.1~22.04.1","6.8.0-44.44.1~22.04.1","6.8.0-45.45.1~22.04.1","6.8.0-47.47.1~22.04.1"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-nvidia-6.2","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["6.2.0-1003.3~22.04.1","6.2.0-1009.9","6.2.0-1010.10","6.2.0-1011.11","6.2.0-1012.12","6.2.0-1013.13","6.2.0-1015.15"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-nvidia-6.5","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["6.5.0-1004.4","6.5.0-1007.7","6.5.0-1013.13","6.5.0-1014.14","6.5.0-1015.15","6.5.0-1018.18","6.5.0-1019.19","6.5.0-1021.22","6.5.0-1022.23","6.5.0-1023.24","6.5.0-1024.25"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-nvidia-6.8","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1017.19~22.04.1"}]}],"versions":["6.8.0-1008.8~22.04.1","6.8.0-1009.9~22.04.1","6.8.0-1010.10~22.04.1","6.8.0-1011.11~22.04.1","6.8.0-1012.12~22.04.1","6.8.0-1013.14~22.04.1","6.8.0-1014.15~22.04.1","6.8.0-1015.16~22.04.1"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-oem-5.17","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.17.0-1003.3","5.17.0-1004.4","5.17.0-1006.6","5.17.0-1011.12","5.17.0-1012.13","5.17.0-1013.14","5.17.0-1014.15","5.17.0-1015.16","5.17.0-1016.17","5.17.0-1017.18","5.17.0-1018.19","5.17.0-1019.20","5.17.0-1020.21","5.17.0-1021.22","5.17.0-1024.25","5.17.0-1025.26","5.17.0-1026.27","5.17.0-1027.28","5.17.0-1028.29","5.17.0-1029.30","5.17.0-1030.31","5.17.0-1031.32","5.17.0-1032.33","5.17.0-1033.34","5.17.0-1034.35","5.17.0-1035.36"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-oem-6.0","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["6.0.0-1006.6","6.0.0-1007.7","6.0.0-1008.8","6.0.0-1009.9","6.0.0-1010.10","6.0.0-1011.11","6.0.0-1012.12","6.0.0-1013.13","6.0.0-1014.14","6.0.0-1015.15","6.0.0-1016.16","6.0.0-1017.17","6.0.0-1018.18","6.0.0-1019.19","6.0.0-1020.20","6.0.0-1021.21"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-oem-6.1","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["6.1.0-1004.4","6.1.0-1006.6","6.1.0-1007.7","6.1.0-1008.8","6.1.0-1009.9","6.1.0-1010.10","6.1.0-1012.12","6.1.0-1013.13","6.1.0-1014.14","6.1.0-1015.15","6.1.0-1016.16","6.1.0-1017.17","6.1.0-1019.19","6.1.0-1020.20","6.1.0-1021.21","6.1.0-1022.22","6.1.0-1023.23","6.1.0-1024.24","6.1.0-1025.25","6.1.0-1026.26","6.1.0-1027.27","6.1.0-1028.28","6.1.0-1029.29","6.1.0-1033.33","6.1.0-1034.34","6.1.0-1035.35","6.1.0-1036.36"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-oem-6.5","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["6.5.0-1003.3","6.5.0-1004.4","6.5.0-1006.6","6.5.0-1007.7","6.5.0-1008.8","6.5.0-1009.10","6.5.0-1011.12","6.5.0-1013.14","6.5.0-1014.15","6.5.0-1015.16","6.5.0-1016.17","6.5.0-1018.19","6.5.0-1019.20","6.5.0-1020.21","6.5.0-1022.23","6.5.0-1023.24","6.5.0-1024.25","6.5.0-1025.26","6.5.0-1027.28"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-oracle-6.5","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["6.5.0-1013.13~22.04.4","6.5.0-1014.14~22.04.1","6.5.0-1015.15~22.04.1","6.5.0-1016.16~22.04.1","6.5.0-1018.18~22.04.1","6.5.0-1019.19~22.04.1","6.5.0-1020.20~22.04.1","6.5.0-1021.21~22.04.1","6.5.0-1023.23~22.04.1","6.5.0-1024.24~22.04.1","6.5.0-1025.25~22.04.1","6.5.0-1026.26~22.04.1","6.5.0-1027.27~22.04.1"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-oracle-6.8","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1015.15~22.04.1"}]}],"versions":["6.8.0-1006.6~22.04.3","6.8.0-1008.8~22.04.1","6.8.0-1010.10~22.04.1","6.8.0-1011.11~22.04.1","6.8.0-1012.12~22.04.1","6.8.0-1013.13~22.04.1","6.8.0-1014.14~22.04.1"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-realtime","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.15.0-1032.35"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-riscv","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.13.0-1004.4","5.13.0-1006.6+22.04.1","5.13.0-1007.7+22.04.1","5.13.0-1010.11+22.04.1","5.15.0-1004.4","5.15.0-1005.5","5.15.0-1006.6","5.15.0-1007.7","5.15.0-1008.8","5.15.0-1011.12","5.15.0-1012.13","5.15.0-1014.16","5.15.0-1015.17","5.15.0-1016.18","5.15.0-1017.19","5.15.0-1018.21","5.15.0-1019.22","5.15.0-1020.23","5.15.0-1022.26","5.15.0-1023.27","5.15.0-1026.30","5.15.0-1027.31","5.15.0-1028.32"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-riscv-5.19","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.19.0-1012.13~22.04.1","5.19.0-1015.16~22.04.1","5.19.0-1016.17~22.04.1","5.19.0-1017.18~22.04.1","5.19.0-1018.19~22.04.1","5.19.0-1019.21~22.04.1","5.19.0-1020.22~22.04.1","5.19.0-1021.23~22.04.1"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-riscv-6.5","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["6.5.0-17.17.1.1~22.04.1","6.5.0-21.21.1~22.04.1","6.5.0-25.25.1~22.04.1","6.5.0-26.26.1~22.04.1","6.5.0-27.28.1~22.04.1","6.5.0-28.29.1~22.04.1","6.5.0-35.35.1~22.04.1","6.5.0-40.40.1~22.04.1","6.5.0-42.42.1~22.04.1","6.5.0-45.45.1~22.04.1"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-riscv-6.8","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-48.48.1~22.04.2"}]}],"versions":["6.8.0-38.38.1~22.04.1","6.8.0-39.39.1~22.04.1","6.8.0-40.40.1~22.04.1","6.8.0-41.41.1~22.04.1","6.8.0-44.44.1~22.04.1","6.8.0-47.47.1~22.04.1"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-starfive-5.19","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.19.0-1014.16~22.04.1","5.19.0-1015.17~22.04.1","5.19.0-1016.18~22.04.1","5.19.0-1017.19~22.04.1","5.19.0-1018.20~22.04.1","5.19.0-1019.21~22.04.1","5.19.0-1020.22~22.04.1"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-starfive-6.2","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["6.2.0-1006.7~22.04.1","6.2.0-1007.8~22.04.1","6.2.0-1009.10~22.04.1"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-starfive-6.5","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["6.5.0-1007.8~22.04.1","6.5.0-1008.9~22.04.1","6.5.0-1009.10~22.04.1","6.5.0-1010.11~22.04.1","6.5.0-1011.12~22.04.1","6.5.0-1012.13~22.04.1","6.5.0-1014.15~22.04.1","6.5.0-1015.16~22.04.1","6.5.0-1016.17~22.04.1","6.5.0-1017.18~22.04.1","6.5.0-1018.19~22.04.1"]},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-48.48"}]}],"versions":["6.5.0-9.9","6.6.0-14.14","6.8.0-11.11","6.8.0-20.20","6.8.0-22.22","6.8.0-28.28","6.8.0-31.31","6.8.0-35.35","6.8.0-36.36","6.8.0-38.38","6.8.0-39.39","6.8.0-40.40","6.8.0-41.41","6.8.0-44.44","6.8.0-45.45","6.8.0-47.47"]},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-aws","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1018.20"}]}],"versions":["6.5.0-1008.8","6.6.0-1001.1","6.8.0-1001.1","6.8.0-1006.6","6.8.0-1008.8","6.8.0-1009.9","6.8.0-1010.10","6.8.0-1011.12","6.8.0-1012.13","6.8.0-1013.14","6.8.0-1014.15","6.8.0-1015.16","6.8.0-1016.17","6.8.0-1017.18"]},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-azure","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1017.20"}]}],"versions":["6.5.0-1007.7","6.6.0-1001.1","6.8.0-1001.1","6.8.0-1005.5","6.8.0-1006.6","6.8.0-1007.7","6.8.0-1008.8","6.8.0-1009.9","6.8.0-1010.10","6.8.0-1012.14","6.8.0-1013.15","6.8.0-1014.16","6.8.0-1015.17","6.8.0-1016.18"]},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-gcp","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1017.19"}]}],"versions":["6.5.0-1007.7","6.6.0-1001.1","6.8.0-1002.2","6.8.0-1005.5","6.8.0-1006.6","6.8.0-1007.7","6.8.0-1008.9","6.8.0-1009.10","6.8.0-1010.11","6.8.0-1011.12","6.8.0-1012.13","6.8.0-1013.14","6.8.0-1014.16","6.8.0-1015.17","6.8.0-1016.18"]},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-gke","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1013.17"}]}],"versions":["6.8.0-1003.5","6.8.0-1004.7","6.8.0-1005.8","6.8.0-1006.9","6.8.0-1007.10","6.8.0-1008.11","6.8.0-1009.12","6.8.0-1010.13","6.8.0-1011.14","6.8.0-1012.15"]},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-gkeop","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1002.4"}]}],"versions":["6.8.0-1001.3"]},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-ibm","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1015.15"}]}],"versions":["6.5.0-1009.9","6.8.0-1001.1","6.8.0-1003.3","6.8.0-1004.4","6.8.0-1005.5","6.8.0-1006.6","6.8.0-1007.7","6.8.0-1008.8","6.8.0-1009.9","6.8.0-1010.10","6.8.0-1011.11","6.8.0-1012.12","6.8.0-1013.13","6.8.0-1014.14"]},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-lowlatency","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-48.48.3"}]}],"versions":["6.5.0-9.9.1","6.6.0-14.14.1","6.8.0-7.7.1","6.8.0-25.25.3","6.8.0-28.28.1","6.8.0-31.31.1","6.8.0-35.35.1","6.8.0-36.36.1","6.8.0-38.38.1","6.8.0-39.39.1","6.8.0-40.40.1","6.8.0-41.41.1","6.8.0-44.44.1","6.8.0-45.45.1","6.8.0-47.47.1"]},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-nvidia","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1017.19"}]}],"versions":["6.8.0-1007.7","6.8.0-1008.8","6.8.0-1009.9","6.8.0-1010.10","6.8.0-1011.11","6.8.0-1012.12","6.8.0-1013.14","6.8.0-1014.15","6.8.0-1015.16"]},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-nvidia-lowlatency","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1017.19.1"}]}],"versions":["6.8.0-1009.9.1","6.8.0-1011.11.1","6.8.0-1012.12.1","6.8.0-1013.14.1","6.8.0-1014.15.1","6.8.0-1015.16.1"]},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-oem-6.8","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1016.16"}]}],"versions":["6.8.0-1003.3","6.8.0-1004.4","6.8.0-1005.5","6.8.0-1006.6","6.8.0-1007.7","6.8.0-1008.8","6.8.0-1009.9","6.8.0-1010.10","6.8.0-1011.11","6.8.0-1012.12","6.8.0-1013.13","6.8.0-1014.14"]},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-oracle","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1015.16"}]}],"versions":["6.5.0-1010.10","6.6.0-1001.1","6.8.0-1001.1","6.8.0-1004.4","6.8.0-1005.5","6.8.0-1006.6","6.8.0-1008.8","6.8.0-1010.10","6.8.0-1011.11","6.8.0-1012.12","6.8.0-1013.13","6.8.0-1014.14"]},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-raspi","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1014.16"}]}],"versions":["6.5.0-1005.7","6.7.0-1001.1","6.8.0-1001.1","6.8.0-1002.2","6.8.0-1003.3","6.8.0-1004.4","6.8.0-1005.5","6.8.0-1006.6","6.8.0-1007.7","6.8.0-1008.8","6.8.0-1009.10","6.8.0-1010.11","6.8.0-1011.12","6.8.0-1012.13","6.8.0-1013.14"]},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-riscv","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-48.48.1"}]}],"versions":["6.5.0-9.9.1","6.8.0-20.20.1","6.8.0-28.28.1","6.8.0-31.31.1","6.8.0-35.35.1","6.8.0-36.36.1","6.8.0-38.38.1","6.8.0-39.39.1","6.8.0-40.40.1","6.8.0-41.41.1","6.8.0-44.44.1","6.8.0-47.47.1"]},{"source":"osv","ecosystem":"Ubuntu:Pro:Realtime:24.04:LTS","package":"linux-raspi-realtime","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-2013.14"}]}],"versions":["6.7.0-2001.1","6.8.0-2001.1","6.8.0-2002.2","6.8.0-2004.4","6.8.0-2005.5","6.8.0-2006.6","6.8.0-2007.7","6.8.0-2008.8","6.8.0-2009.9","6.8.0-2010.10","6.8.0-2011.11","6.8.0-2012.12"]},{"source":"osv","ecosystem":"Ubuntu:Pro:Realtime:24.04:LTS","package":"linux-realtime","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.1-1011.11"}]}],"versions":["6.8.0-1008.19","6.8.1-1001.1","6.8.1-1002.2","6.8.1-1003.3","6.8.1-1004.4","6.8.1-1005.5","6.8.1-1006.6","6.8.1-1007.7","6.8.1-1008.8","6.8.1-1009.9","6.8.1-1010.10"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-gcp-6.8","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1017.19~22.04.1"}]}],"versions":["6.8.0-1010.11~22.04.1","6.8.0-1011.12~22.04.1","6.8.0-1012.13~22.04.1","6.8.0-1013.14~22.04.1","6.8.0-1014.16~22.04.1","6.8.0-1015.17~22.04.1","6.8.0-1016.18~22.04.1"],"bundled":196},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-hwe-6.8","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-48.48~22.04.1"}]}],"versions":["6.8.0-38.38~22.04.1","6.8.0-39.39~22.04.1","6.8.0-40.40~22.04.3","6.8.0-45.45~22.04.1","6.8.0-47.47~22.04.1"],"bundled":196},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-48.48"}]}],"versions":["6.5.0-9.9","6.6.0-14.14","6.8.0-11.11","6.8.0-20.20","6.8.0-22.22","6.8.0-28.28","6.8.0-31.31","6.8.0-35.35","6.8.0-36.36","6.8.0-38.38","6.8.0-39.39","6.8.0-40.40","6.8.0-41.41","6.8.0-44.44","6.8.0-45.45","6.8.0-47.47"],"bundled":196},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-azure","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1017.20"}]}],"versions":["6.5.0-1007.7","6.6.0-1001.1","6.8.0-1001.1","6.8.0-1005.5","6.8.0-1006.6","6.8.0-1007.7","6.8.0-1008.8","6.8.0-1009.9","6.8.0-1010.10","6.8.0-1012.14","6.8.0-1013.15","6.8.0-1014.16","6.8.0-1015.17","6.8.0-1016.18"],"bundled":196},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-gcp","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1017.19"}]}],"versions":["6.5.0-1007.7","6.6.0-1001.1","6.8.0-1002.2","6.8.0-1005.5","6.8.0-1006.6","6.8.0-1007.7","6.8.0-1008.9","6.8.0-1009.10","6.8.0-1010.11","6.8.0-1011.12","6.8.0-1012.13","6.8.0-1013.14","6.8.0-1014.16","6.8.0-1015.17","6.8.0-1016.18"],"bundled":196},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-ibm","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1015.15"}]}],"versions":["6.5.0-1009.9","6.8.0-1001.1","6.8.0-1003.3","6.8.0-1004.4","6.8.0-1005.5","6.8.0-1006.6","6.8.0-1007.7","6.8.0-1008.8","6.8.0-1009.9","6.8.0-1010.10","6.8.0-1011.11","6.8.0-1012.12","6.8.0-1013.13","6.8.0-1014.14"],"bundled":196},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-aws-6.8","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1018.19~22.04.1"}]}],"versions":["6.8.0-1009.9~22.04.2","6.8.0-1010.10~22.04.2","6.8.0-1011.12~22.04.1","6.8.0-1013.14~22.04.1","6.8.0-1014.15~22.04.1","6.8.0-1015.16~22.04.1","6.8.0-1016.17~22.04.2","6.8.0-1017.18~22.04.1"],"bundled":196},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-oracle-6.8","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1015.15~22.04.1"}]}],"versions":["6.8.0-1006.6~22.04.3","6.8.0-1008.8~22.04.1","6.8.0-1010.10~22.04.1","6.8.0-1011.11~22.04.1","6.8.0-1012.12~22.04.1","6.8.0-1013.13~22.04.1","6.8.0-1014.14~22.04.1"],"bundled":196},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-aws","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1018.20"}]}],"versions":["6.5.0-1008.8","6.6.0-1001.1","6.8.0-1001.1","6.8.0-1006.6","6.8.0-1008.8","6.8.0-1009.9","6.8.0-1010.10","6.8.0-1011.12","6.8.0-1012.13","6.8.0-1013.14","6.8.0-1014.15","6.8.0-1015.16","6.8.0-1016.17","6.8.0-1017.18"],"bundled":196},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-oracle","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1015.16"}]}],"versions":["6.5.0-1010.10","6.6.0-1001.1","6.8.0-1001.1","6.8.0-1004.4","6.8.0-1005.5","6.8.0-1006.6","6.8.0-1008.8","6.8.0-1010.10","6.8.0-1011.11","6.8.0-1012.12","6.8.0-1013.13","6.8.0-1014.14"],"bundled":196},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-oem-6.8","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1016.16"}]}],"versions":["6.8.0-1003.3","6.8.0-1004.4","6.8.0-1005.5","6.8.0-1006.6","6.8.0-1007.7","6.8.0-1008.8","6.8.0-1009.9","6.8.0-1010.10","6.8.0-1011.11","6.8.0-1012.12","6.8.0-1013.13","6.8.0-1014.14"],"bundled":196},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-raspi","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1014.16"}]}],"versions":["6.5.0-1005.7","6.7.0-1001.1","6.8.0-1001.1","6.8.0-1002.2","6.8.0-1003.3","6.8.0-1004.4","6.8.0-1005.5","6.8.0-1006.6","6.8.0-1007.7","6.8.0-1008.8","6.8.0-1009.10","6.8.0-1010.11","6.8.0-1011.12","6.8.0-1012.13","6.8.0-1013.14"],"bundled":196},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-gke","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1013.17"}]}],"versions":["6.8.0-1003.5","6.8.0-1004.7","6.8.0-1005.8","6.8.0-1006.9","6.8.0-1007.10","6.8.0-1008.11","6.8.0-1009.12","6.8.0-1010.13","6.8.0-1011.14","6.8.0-1012.15"],"bundled":196},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-lowlatency-hwe-6.8","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-48.48.3~22.04.1"}]}],"versions":["6.8.0-38.38.1~22.04.2","6.8.0-40.40.1~22.04.1","6.8.0-44.44.1~22.04.1","6.8.0-45.45.1~22.04.1","6.8.0-47.47.1~22.04.1"],"bundled":196},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-lowlatency","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-48.48.3"}]}],"versions":["6.5.0-9.9.1","6.6.0-14.14.1","6.8.0-7.7.1","6.8.0-25.25.3","6.8.0-28.28.1","6.8.0-31.31.1","6.8.0-35.35.1","6.8.0-36.36.1","6.8.0-38.38.1","6.8.0-39.39.1","6.8.0-40.40.1","6.8.0-41.41.1","6.8.0-44.44.1","6.8.0-45.45.1","6.8.0-47.47.1"],"bundled":196},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-azure-6.8","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1017.20~22.04.1"}]}],"versions":["6.8.0-1008.8~22.04.1","6.8.0-1009.9~22.04.1","6.8.0-1010.10~22.04.1","6.8.0-1012.14~22.04.1","6.8.0-1013.15~22.04.1","6.8.0-1014.16~22.04.1","6.8.0-1015.17~22.04.2"],"bundled":198},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-nvidia-6.8","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1017.19~22.04.1"}]}],"versions":["6.8.0-1008.8~22.04.1","6.8.0-1009.9~22.04.1","6.8.0-1010.10~22.04.1","6.8.0-1011.11~22.04.1","6.8.0-1012.12~22.04.1","6.8.0-1013.14~22.04.1","6.8.0-1014.15~22.04.1","6.8.0-1015.16~22.04.1"],"bundled":197},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-nvidia","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1017.19"}]}],"versions":["6.8.0-1007.7","6.8.0-1008.8","6.8.0-1009.9","6.8.0-1010.10","6.8.0-1011.11","6.8.0-1012.12","6.8.0-1013.14","6.8.0-1014.15","6.8.0-1015.16"],"bundled":197},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-nvidia-lowlatency","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1017.19.1"}]}],"versions":["6.8.0-1009.9.1","6.8.0-1011.11.1","6.8.0-1012.12.1","6.8.0-1013.14.1","6.8.0-1014.15.1","6.8.0-1015.16.1"],"bundled":197},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-gkeop","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1002.4"}]}],"versions":["6.8.0-1001.3"],"bundled":607}],"products":[{"vendor":"linux","product":"linux"},{"vendor":"linux","product":"linux_kernel"}],"references":[{"url":"https://git.kernel.org/stable/c/bc262c6d32b6c1715e64220e2cbfa64a225cd266","tags":["web"]},{"url":"https://git.kernel.org/stable/c/1d064e4fbebcf5b18dc10c1f3973487eb163b600","tags":["x_transferred","Patch","web","report"]},{"url":"https://git.kernel.org/stable/c/84ec985944ef34a34a1605b93ce401aa8737af96","tags":["x_transferred","Patch","web","report"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-41085","tags":["web","advisory"]},{"url":"https://github.com/advisories/GHSA-2qvq-p8h3-vf5j"},{"url":"https://docs.bell-sw.com/security/cves/CVE-2024-41085","tags":["advisory"]},{"url":"https://github.com/CVEProject/cvelistV5/tree/main/cves/2024/41xxx/CVE-2024-41085.json","tags":["advisory"]},{"url":"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git","tags":["package"]},{"url":"https://security-tracker.debian.org/tracker/CVE-2024-41085","tags":["advisory"]},{"url":"https://www.openeuler.org/zh/security/security-bulletins/detail/?id=openEuler-SA-2024-1960","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-33619","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-35247","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-35848","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-35859","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-35966","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-36890","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-36896","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-36899","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-36901","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-36944","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-36964","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-38556","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-38576","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-38600","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-38606","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-38607","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-38617","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-39471","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-39473","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-39475","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-39481","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-39486","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-39493","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-39496","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-39503","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-40900","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-40906","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-40908","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-40913","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-40920","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-40921","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-40922","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-40935","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-40953","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-40962","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-40967","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-40981","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-41006","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-41010","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-41013","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-41014","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-41018","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-41019","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-41020","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-41021","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-41023","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-41039","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-41040","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-41041","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-41044","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-41045","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-41048","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-41049","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-41056","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-41062","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-41063","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-41064","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-41069","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-41072","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-41073","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-41074","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-41075","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-41076","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-41077","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-41080","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-41090","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-41091","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-41096","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-42068","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-42086","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-42097","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-42115","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-42126","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-42129","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-42155","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-42162","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-42228","tags":["advisory"]},{"url":"https://access.redhat.com/errata/RHSA-2024:9315","tags":["advisory"]},{"url":"https://docs.redhat.com/en/documentation/red_hat_enterprise_linux/9/html/9.5_release_notes/index","tags":["article"]},{"url":"https://access.redhat.com/security/updates/classification/#moderate","tags":["article"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=1832397","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2257406","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2260038","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2262241","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2263879","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2265648","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2265650","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2265654","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2265657","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2265793","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2265798","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2265800","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2265831","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2265833","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2265836","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2266210","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2266212","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2266247","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2266249","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2266296","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2266363","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2266916","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2267028","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2267038","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2267701","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2267705","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2267724","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2267730","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2267782","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2267789","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2267797","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2267804","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2267916","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2267920","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2268293","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2268315","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2268317","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2268335","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2269063","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2269183","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2269192","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2269201","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2269203","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2269211","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2270071","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2270084","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2270093","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2270097","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2270103","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2270133","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2271648","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2271682","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2271684","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2271688","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2271690","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2271788","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2271795","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2272692","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2272782","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2272784","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2272786","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2272788","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2272791","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2272795","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2272800","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2272804","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2272806","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2272808","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2272814","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2272818","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2272829","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2272836","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2272839","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2272842","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2273085","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2273098","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2273109","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2273113","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2273130","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2273143","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2273148","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2273158","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2273166","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2273168","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2273174","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2273185","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2273200","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2273204","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2273206","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2273208","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2273234","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2273242","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2273247","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2273260","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2273262","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2273268","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2273408","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2273425","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2273459","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2273461","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2273468","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2273650","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2273657","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2274478","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2274624","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2275558","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2275565","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2275573","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2275578","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2275580","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2275584","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2275624","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2275633","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2275635","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2275641","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2275645","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2275647","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2275650","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2275661","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2275666","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2275670","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2275672","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2275686","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2275694","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2275707","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2275711","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2275725","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2275727","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2275729","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2275737","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2275775","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2275790","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2275928","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2276665","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2277168","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2277844","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2277937","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2278169","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2278174","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2278178","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2278182","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2278193","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2278197","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2278200","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2278218","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2278220","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2278229","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2278231","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2278237","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2278240","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2278262","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2278266","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2278268","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2278270","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2278275","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2278277","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2278279","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2278291","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2278293","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2278316","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2278320","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2278322","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2278324","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2278327","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2278333","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2278350","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2278352","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2278356","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2278387","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2278406","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2278431","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2278447","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2278456","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2278484","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2278488","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2278492","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2278522","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2278524","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2278532","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2278537","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2278539","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2278939","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2278960","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2280440","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2280444","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2281045","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2281061","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2281069","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2281103","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2281113","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2281125","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2281141","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2281145","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2281155","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2281157","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2281165","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2281173","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2281183","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2281189","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2281192","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2281202","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2281207","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2281211","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2281215","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2281217","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2281219","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2281221","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2281225","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2281235","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2281243","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2281251","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2281253","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2281255","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2281268","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2281276","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2281282","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2281286","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2281288","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2281290","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2281303","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2281305","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2281311","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2281317","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2281324","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2281326","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2281332","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2281336","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2281356","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2281358","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2281360","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2281362","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2281510","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2281517","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2281519","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2281523","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2281526","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2281634","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2281636","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2281645","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2281651","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2281655","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2281664","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2281679","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2281684","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2281693","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2281697","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2281713","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2281718","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2281720","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2281725","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2281736","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2281742","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2281752","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2281754","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2281758","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2281760","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2281762","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2281763","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2281769","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2281773","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2281781","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2281783","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2281786","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2281807","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2281811","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2281817","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2281819","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2281833","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2281843","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2281863","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2281872","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2281884","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2281891","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2281923","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2281927","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2281933","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2281938","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2281942","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2281989","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2282088","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2282302","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2282304","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2282354","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2282356","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2282366","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2282612","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2282622","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2282623","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2282637","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2282640","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2282641","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2282646","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2282652","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2282653","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2282655","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2282670","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2282676","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2282679","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2282680","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2282690","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2282740","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2282741","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2282742","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2282743","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2282744","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2282745","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2282746","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2282748","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2282757","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2282762","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2282763","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2282772","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2282787","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2282901","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2282904","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2282918","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2282920","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2282950","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2283448","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2283786","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2284265","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2284269","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2284273","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2284277","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2284295","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2284410","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2284413","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2284427","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2284465","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2284468","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2284477","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2284488","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2284490","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2284494","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2284500","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2284502","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2284515","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2284519","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2284539","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2284545","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2284556","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2284567","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2284583","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2284586","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2284628","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2284634","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2290407","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2290408","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2292329","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2293000","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2293003","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2293329","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2293359","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2293361","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2293365","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2293367","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2293371","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2293408","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2293444","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2293639","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2293656","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2293684","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2293693","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2293696","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2293698","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2293700","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2294223","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2294268","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2294274","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2294313","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2296059","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2296064","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2296066","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2296278","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2296383","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2297057","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2297061","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2297469","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2297470","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=2297475","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2297480","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2297487","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2297490","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2297491","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2297497","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2297503","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2297506","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2297507","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2297508","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2297509","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2297514","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2297524","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2297529","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2297532","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2297549","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2297550","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2297551","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=2297581","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2297585","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2297702","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=2298817","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2299452","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2300363","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2300398","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=2300412","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2300422","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2300430","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2300431","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2300432","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2300434","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2300438","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2300440","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2300454","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2300456","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2300459","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2300480","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2300481","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2300486","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2300487","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2300488","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2300489","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2300490","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2300508","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2300516","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=2301464","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2301477","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2301488","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2301489","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2301490","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2301497","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2301506","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2301522","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2301530","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://bugzilla.redhat.com/show_bug.cgi?id=2304187","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2305446","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2306363","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2307861","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2307865","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2307884","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2309273","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2309791","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2309796","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2309801","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2309847","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2309868","tags":["report"]},{"url":"https://issues.redhat.com/browse/RHEL-17714","tags":["article"]},{"url":"https://issues.redhat.com/browse/RHEL-23575","tags":["article"]},{"url":"https://issues.redhat.com/browse/RHEL-26081","tags":["article"]},{"url":"https://issues.redhat.com/browse/RHEL-29437","tags":["article"]},{"url":"https://issues.redhat.com/browse/RHEL-31876","tags":["article"]},{"url":"https://issues.redhat.com/browse/RHEL-32199","tags":["article"]},{"url":"https://issues.redhat.com/browse/RHEL-35853","tags":["article"]},{"url":"https://issues.redhat.com/browse/RHEL-36182","tags":["article"]},{"url":"https://issues.redhat.com/browse/RHEL-36224","tags":["article"]},{"url":"https://issues.redhat.com/browse/RHEL-45158","tags":["article"]},{"url":"https://issues.redhat.com/browse/RHEL-7990","tags":["article"]},{"url":"https://issues.redhat.com/browse/RHEL-9096","tags":["article"]},{"url":"https://issues.redhat.com/browse/RHEL-9148","tags":["article"]},{"url":"https://issues.redhat.com/browse/RHEL-9429","tags":["article"]},{"url":"https://security.access.redhat.com/data/csaf/v2/advisories/2024/rhsa-2024_9315.json","tags":["advisory"]},{"url":"https://access.redhat.com/security/cve/CVE-2019-25162","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2019-25162","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2019-25162","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024022602-CVE-2019-25162-70ae@gregkh/","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2020-10135","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2020-10135","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2020-10135","tags":["advisory"]},{"url":"https://francozappa.github.io/about-bias/","tags":["article"]},{"url":"https://kb.cert.org/vuls/id/647177/","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2021-47098","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2021-47098","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2021-47098","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024030415-CVE-2021-47098-e11f@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2021-47101","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2021-47101","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2021-47101","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024030415-CVE-2021-47101-f3fa@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2021-47185","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2021-47185","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2021-47185","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024041033-CVE-2021-47185-c363@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2021-47384","tags":["report"]},{"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://access.redhat.com/security/cve/CVE-2021-47386","tags":["report"]},{"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://access.redhat.com/security/cve/CVE-2021-47428","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2021-47428","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2021-47428","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024052157-CVE-2021-47428-f3c0@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2021-47429","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2021-47429","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2021-47429","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024052157-CVE-2021-47429-e386@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2021-47432","tags":["report"]},{"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://access.redhat.com/security/cve/CVE-2021-47454","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2021-47454","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2021-47454","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024052243-CVE-2021-47454-e852@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2021-47457","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2021-47457","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2021-47457","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024052244-CVE-2021-47457-d807@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2021-47495","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2021-47495","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2021-47495","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024052242-CVE-2021-47495-a5f8@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2021-47497","tags":["report"]},{"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://access.redhat.com/security/cve/CVE-2021-47505","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2021-47505","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2021-47505","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024052452-CVE-2021-47505-427f@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-48669","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-48669","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-48669","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024050131-CVE-2022-48669-15cf@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-48672","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-48672","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-48672","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024050318-CVE-2022-48672-b6d9@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-48703","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-48703","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-48703","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024050351-CVE-2022-48703-3099@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-48804","tags":["report"]},{"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://access.redhat.com/security/cve/CVE-2022-48929","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2307185","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-48929","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-48929","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024082222-CVE-2022-48929-857d@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-49078","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2348091","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-49078","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-49078","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025022656-CVE-2022-49078-df00@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-49124","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2347834","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-49124","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-49124","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025022604-CVE-2022-49124-b593@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-49197","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2347924","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-49197","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-49197","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025022617-CVE-2022-49197-494d@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-49267","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2347734","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-49267","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-49267","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025022629-CVE-2022-49267-b3ac@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-49308","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2348348","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-49308","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-49308","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025022635-CVE-2022-49308-23f0@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-49329","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2348087","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-49329","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-49329","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025022639-CVE-2022-49329-ed73@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-49430","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2347819","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-49430","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-49430","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025022655-CVE-2022-49430-3b17@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-49549","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2348127","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-49549","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-49549","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025022615-CVE-2022-49549-db30@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-49675","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2348124","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-49675","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-49675","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025022624-CVE-2022-49675-17aa@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-49787","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2363396","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-49787","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-49787","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025050121-CVE-2022-49787-7fb0@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-49860","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2363384","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-49860","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-49860","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025050147-CVE-2022-49860-75f4@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-49941","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2373403","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-49941","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-49941","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025061849-CVE-2022-49941-b536@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-50019","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2373660","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-50019","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-50019","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025061834-CVE-2022-50019-181a@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-50073","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2373494","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-50073","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-50073","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025061854-CVE-2022-50073-7199@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-50096","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2373541","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-50096","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-50096","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025061802-CVE-2022-50096-0220@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-50141","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2373674","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-50141","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-50141","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025061818-CVE-2022-50141-fd0e@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-50177","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2373568","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-50177","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-50177","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025061831-CVE-2022-50177-1d63@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-50251","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2395251","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-50251","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-50251","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025091549-CVE-2022-50251-c216@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-50268","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2395281","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-50268","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-50268","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025091504-CVE-2022-50268-bcdf@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-50284","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2395425","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-50284","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-50284","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025091507-CVE-2022-50284-b5c2@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-50312","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2395391","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-50312","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-50312","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025091500-CVE-2022-50312-105d@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-50347","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2395843","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-50347","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-50347","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025091640-CVE-2022-50347-33c3@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-50353","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2396104","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-50353","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-50353","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025091711-CVE-2022-50353-2f1e@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-50468","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2400820","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-50468","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-50468","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025100122-CVE-2022-50468-3196@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-50486","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2401477","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-50486","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-50486","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025100441-CVE-2022-50486-da3d@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-50495","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2401512","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-50495","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-50495","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025100419-CVE-2022-50495-fdee@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-50541","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2402260","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-50541","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-50541","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025100756-CVE-2022-50541-e1fe@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-50625","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2419901","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-50625","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-50625","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025120853-CVE-2022-50625-a1e2@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-50640","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2420263","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-50640","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-50640","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025120935-CVE-2022-50640-324c@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-50653","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2420261","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-50653","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-50653","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025120938-CVE-2022-50653-6da2@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-50663","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2420360","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-50663","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-50663","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025120943-CVE-2022-50663-5606@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-50670","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2420313","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-50670","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-50670","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025120946-CVE-2022-50670-feb4@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-50720","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2425047","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-50720","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-50720","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025122417-CVE-2022-50720-0297@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-50748","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2425140","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-50748","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-50748","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025122451-CVE-2022-50748-0136@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-50761","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2425106","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-50761","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-50761","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025122455-CVE-2022-50761-0e67@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-50769","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2425084","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-50769","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-50769","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025122457-CVE-2022-50769-f4db@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-50846","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2426137","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-50846","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-50846","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025123021-CVE-2022-50846-caa2@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-50858","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2426081","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-50858","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-50858","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025123047-CVE-2022-50858-f41c@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-50886","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2426015","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-50886","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-50886","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025123021-CVE-2022-50886-a081@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-52445","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-52445","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-52445","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024022253-CVE-2023-52445-07a6@gregkh/T/#u","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-52451","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-52451","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-52451","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024022257-CVE-2023-52451-7bdb@gregkh/T/#u","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-52455","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-52455","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-52455","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024022331-CVE-2023-52455-a28f@gregkh/T/#u","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-52462","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-52462","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-52462","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024022335-CVE-2023-52462-b663@gregkh/T/#u","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-52464","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-52464","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-52464","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024022336-CVE-2023-52464-b17c@gregkh/T/#u","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-52466","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-52466","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-52466","tags":["advisory"]},{"url":"https://git.kernel.org/stable/c/3171e46d677a668eed3086da78671f1e4f5b8405","tags":["article"]},{"url":"https://git.kernel.org/stable/c/5b3e25efe16e06779a9a7c7610217c1b921ec179","tags":["article"]},{"url":"https://git.kernel.org/stable/c/bd26159dcaaa3e9a927070efd348e7ce7e5ee933","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-52467","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-52467","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-52467","tags":["advisory"]},{"url":"https://git.kernel.org/stable/c/3ef1130deee98997275904d9bfc37af75e1e906c","tags":["article"]},{"url":"https://git.kernel.org/stable/c/41673c66b3d0c09915698fec5c13b24336f18dd1","tags":["article"]},{"url":"https://git.kernel.org/stable/c/527e8c5f3d00299822612c495d5adf1f8f43c001","tags":["article"]},{"url":"https://git.kernel.org/stable/c/7f2c410ac470959b88e03dadd94b7a0b71df7973","tags":["article"]},{"url":"https://git.kernel.org/stable/c/927626a2073887ee30ba00633260d4d203f8e875","tags":["article"]},{"url":"https://git.kernel.org/stable/c/c3e3a2144bf50877551138ffce9f7aa6ddfe385b","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-52473","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-52473","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-52473","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024022547-CVE-2023-52473-c3cc@gregkh/T/#u","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-52475","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-52475","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-52475","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024022918-CVE-2023-52475-442e@gregkh/T/#u","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-52477","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-52477","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-52477","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024022921-CVE-2023-52477-6f20@gregkh/T/#u","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-52482","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-52482","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-52482","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024022922-CVE-2023-52482-9375@gregkh/T/#u","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-52486","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2269070","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-52486","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-52486","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/20240229155245.1571576-27-lee@kernel.org/T/#u","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-52492","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-52492","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-52492","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/20240229155245.1571576-33-lee@kernel.org/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-52498","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-52498","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-52498","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/20240229155245.1571576-39-lee@kernel.org/T/#u","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-52501","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-52501","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-52501","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024030248-CVE-2023-52501-75ba@gregkh/T/#u","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-52513","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-52513","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-52513","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024030251-CVE-2023-52513-5224@gregkh/T/#u","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-52520","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-52520","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-52520","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024030252-CVE-2023-52520-0a4e@gregkh/T/#u","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-52528","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-52528","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-52528","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024030254-CVE-2023-52528-c33b@gregkh/T/#u","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-52560","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-52560","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-52560","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024030252-CVE-2023-52560-c3de@gregkh/T/#u","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-52565","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-52565","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-52565","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024030254-CVE-2023-52565-07ce@gregkh/","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-52585","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-52585","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-52585","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024030643-CVE-2023-52585-7dbc@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-52594","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-52594","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-52594","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024030645-CVE-2023-52594-9b84@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-52595","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-52595","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-52595","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024030645-CVE-2023-52595-d018@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-52606","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-52606","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-52606","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024030647-CVE-2023-52606-fdcc@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-52614","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-52614","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-52614","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/20240318101458.2835626-9-lee@kernel.org/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-52615","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-52615","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-52615","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/20240318101458.2835626-10-lee@kernel.org/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-52619","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-52619","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-52619","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/20240318102117.2839904-9-lee@kernel.org/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-52621","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-52621","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-52621","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/20240326171931.1354035-4-lee@kernel.org/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-52622","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-52622","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-52622","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/20240326171931.1354035-5-lee@kernel.org/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-52624","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-52624","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-52624","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/20240326175007.1388794-10-lee@kernel.org/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-52625","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-52625","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-52625","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/20240326175007.1388794-11-lee@kernel.org/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-52632","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-52632","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-52632","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024040218-CVE-2023-52632-f7bb@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-52634","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-52634","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-52634","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024040219-CVE-2023-52634-27e0@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-52635","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-52635","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-52635","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024040219-CVE-2023-52635-8b18@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-52637","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-52637","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-52637","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024040332-CVE-2023-52637-5e37@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-52643","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-52643","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-52643","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024041701-CVE-2023-52643-8834@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-52648","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-52648","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-52648","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024050122-CVE-2023-52648-4e0d@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-52649","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-52649","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-52649","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024050109-CVE-2023-52649-4614@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-52650","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-52650","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-52650","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024050109-CVE-2023-52650-e2d1@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-52656","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-52656","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-52656","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024051338-CVE-2023-52656-6545@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-52659","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-52659","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-52659","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024051755-CVE-2023-52659-6f51@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-52661","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-52661","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-52661","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024051738-CVE-2023-52661-5539@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-52662","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-52662","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-52662","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024051740-CVE-2023-52662-1536@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-52663","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-52663","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-52663","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024051740-CVE-2023-52663-1045@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-52664","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-52664","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-52664","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024051756-CVE-2023-52664-dea1@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-52674","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-52674","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-52674","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024051747-CVE-2023-52674-2aec@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-52676","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-52676","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-52676","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024051749-CVE-2023-52676-e224@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-52679","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-52679","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-52679","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024051750-CVE-2023-52679-948f@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-52680","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-52680","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-52680","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024051750-CVE-2023-52680-1f4a@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-52683","tags":["report"]},{"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://access.redhat.com/security/cve/CVE-2023-52686","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-52686","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-52686","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024051752-CVE-2023-52686-4a08@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-52689","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-52689","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-52689","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024051753-CVE-2023-52689-f657@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-52690","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-52690","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-52690","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024051753-CVE-2023-52690-f225@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-52696","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-52696","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-52696","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024051755-CVE-2023-52696-d4ab@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-52697","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-52697","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-52697","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024051755-CVE-2023-52697-1b7f@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-52698","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-52698","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-52698","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024051756-CVE-2023-52698-bbc2@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-52703","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-52703","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-52703","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024052157-CVE-2023-52703-abcb@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-52730","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-52730","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-52730","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024052158-CVE-2023-52730-1c8f@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-52731","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-52731","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-52731","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024052159-CVE-2023-52731-29ab@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-52740","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-52740","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-52740","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024052101-CVE-2023-52740-3265@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-52749","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-52749","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-52749","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024052144-CVE-2023-52749-684e@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-52751","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-52751","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-52751","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024052144-CVE-2023-52751-69df@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-52756","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-52756","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-52756","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024052146-CVE-2023-52756-f694@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-52757","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-52757","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-52757","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024052146-CVE-2023-52757-5028@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-52758","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-52758","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-52758","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024052146-CVE-2023-52758-9b23@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-52762","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-52762","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-52762","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024052147-CVE-2023-52762-fe90@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-52775","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-52775","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-52775","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024052151-CVE-2023-52775-38a8@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-52784","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-52784","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-52784","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024052154-CVE-2023-52784-80ad@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-52788","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-52788","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-52788","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024052155-CVE-2023-52788-9cb4@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-52791","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-52791","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-52791","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024052156-CVE-2023-52791-f2b9@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-52811","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-52811","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-52811","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024052102-CVE-2023-52811-2a5f@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-52813","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-52813","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-52813","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024052103-CVE-2023-52813-0704@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-52814","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-52814","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-52814","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024052103-CVE-2023-52814-1cae@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-52817","tags":["report"]},{"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://access.redhat.com/security/cve/CVE-2023-52819","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-52819","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-52819","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024052105-CVE-2023-52819-98d5@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-52831","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-52831","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-52831","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024052108-CVE-2023-52831-ce31@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-52833","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-52833","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-52833","tags":["advisory"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-52834","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-52834","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-52834","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024052109-CVE-2023-52834-4c46@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-52837","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-52837","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-52837","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024052110-CVE-2023-52837-6490@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-52840","tags":["report"]},{"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-52859","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-52859","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-52859","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024052117-CVE-2023-52859-ad0e@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-52867","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-52867","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-52867","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024052119-CVE-2023-52867-3f26@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-52869","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-52869","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-52869","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024052120-CVE-2023-52869-6f57@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-52878","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-52878","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-52878","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024052122-CVE-2023-52878-d433@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-52902","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2306430","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-52902","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-52902","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024082113-CVE-2023-52902-d3fa@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-52932","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2355470","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-52932","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-52932","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025032720-CVE-2023-52932-434b@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-52935","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2355450","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-52935","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-52935","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025032720-CVE-2023-52935-1c3c@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-53059","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2363701","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-53059","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-53059","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025050209-CVE-2023-53059-47f3@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-53068","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2363687","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-53068","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-53068","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025050212-CVE-2023-53068-0127@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-53173","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2395244","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-53173","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-53173","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025091555-CVE-2023-53173-4180@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-53176","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2395382","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-53176","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-53176","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025091555-CVE-2023-53176-4194@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-53178","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2395358","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-53178","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-53178","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025091555-CVE-2023-53178-9d27@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-53182","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2395248","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-53182","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-53182","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025091556-CVE-2023-53182-dcdb@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-53220","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2395338","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-53220","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-53220","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025091512-CVE-2023-53220-e514@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-53230","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2395266","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-53230","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-53230","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025091514-CVE-2023-53230-6c94@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-53249","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2395320","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-53249","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-53249","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025091502-CVE-2023-53249-aab7@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-53264","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2395687","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-53264","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-53264","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025091602-CVE-2023-53264-9c17@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-53291","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2395686","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-53291","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-53291","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025091626-CVE-2023-53291-9fe7@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-53391","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2396423","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-53391","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-53391","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025091858-CVE-2023-53391-cea3@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-53395","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2396416","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-53395","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-53395","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025091859-CVE-2023-53395-939e@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-53397","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2396385","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-53397","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-53397","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025091859-CVE-2023-53397-2076@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-53401","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2396417","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-53401","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-53401","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025091800-CVE-2023-53401-b668@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-53402","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2396465","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-53402","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-53402","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025091800-CVE-2023-53402-4b40@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-53470","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2400755","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-53470","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-53470","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025100109-CVE-2023-53470-8c6a@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-53483","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2400788","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-53483","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-53483","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025100113-CVE-2023-53483-cf50@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-53503","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2400765","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-53503","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-53503","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025100127-CVE-2023-53503-d86c@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-53505","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2400785","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-53505","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-53505","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025100128-CVE-2023-53505-69f3@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-53531","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2400691","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-53531","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-53531","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025100136-CVE-2023-53531-3c7c@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-53558","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2401543","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-53558","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-53558","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025100449-CVE-2023-53558-e6f7@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-53572","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2401503","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-53572","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-53572","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025100453-CVE-2023-53572-ab85@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-53596","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2401501","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-53596","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-53596","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025100429-CVE-2023-53596-dbfb@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-53597","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2401466","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-53597","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-53597","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025100429-CVE-2023-53597-e30c@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-53613","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2401518","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-53613","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-53613","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025100434-CVE-2023-53613-bba8@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-53662","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2402190","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-53662","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-53662","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025100703-CVE-2023-53662-475f@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-53674","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2402263","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-53674","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-53674","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025100706-CVE-2023-53674-af85@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-53687","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2402288","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-53687","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-53687","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025100710-CVE-2023-53687-c50c@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-53697","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2405771","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-53697","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-53697","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025102211-CVE-2023-53697-3078@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-53702","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2405762","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-53702","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-53702","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025102211-CVE-2023-53702-a6b6@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-53704","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2405725","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-53704","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-53704","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025102212-CVE-2023-53704-9f42@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-53708","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2405783","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-53708","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-53708","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025102212-CVE-2023-53708-0bf0@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-53719","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2405740","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-53719","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-53719","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025102214-CVE-2023-53719-ad4c@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-53731","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2405719","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-53731","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-53731","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025102216-CVE-2023-53731-aef7@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-53744","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2419846","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-53744","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-53744","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025120841-CVE-2023-53744-c66e@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-53747","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2419903","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-53747","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-53747","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025120842-CVE-2023-53747-ae4a@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-53752","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2419915","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-53752","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-53752","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025120843-CVE-2023-53752-339f@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-53768","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2419848","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-53768","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-53768","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025120846-CVE-2023-53768-2b71@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-53858","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2420332","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-53858","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-53858","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025120904-CVE-2023-53858-87d4@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-53861","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2420351","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-53861","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-53861","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025120905-CVE-2023-53861-22c6@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-53997","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2424939","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-53997","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-53997","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025122426-CVE-2023-53997-8776@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-54010","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2424948","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-54010","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-54010","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025122430-CVE-2023-54010-9ff1@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-54019","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2424987","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-54019","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-54019","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025122433-CVE-2023-54019-95e0@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-54066","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2425023","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-54066","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-54066","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025122430-CVE-2023-54066-8ff7@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-54083","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2425134","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-54083","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-54083","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025122404-CVE-2023-54083-fc0e@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-54093","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2425122","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-54093","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-54093","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025122407-CVE-2023-54093-fcea@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-54095","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2425107","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-54095","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-54095","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025122408-CVE-2023-54095-7fe0@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-54113","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2425156","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-54113","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-54113","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025122414-CVE-2023-54113-de5f@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-54114","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2425196","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-54114","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-54114","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025122414-CVE-2023-54114-8362@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-54118","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2425126","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-54118","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-54118","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025122415-CVE-2023-54118-d92b@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-54136","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2425141","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-54136","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-54136","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025122421-CVE-2023-54136-b58d@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-54146","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2425157","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-54146","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-54146","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025122425-CVE-2023-54146-1510@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-54153","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2425153","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-54153","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-54153","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025122427-CVE-2023-54153-63a8@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-54165","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2426209","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-54165","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-54165","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025123019-CVE-2023-54165-1362@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-54172","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2426166","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-54172","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-54172","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025123021-CVE-2023-54172-bcdc@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-54194","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2426196","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-54194","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-54194","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025123028-CVE-2023-54194-a396@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-54198","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2426177","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-54198","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-54198","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025123029-CVE-2023-54198-1df4@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-54227","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2426105","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-54227","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-54227","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025123029-CVE-2023-54227-5c6c@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-54244","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2426096","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-54244","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-54244","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025123052-CVE-2023-54244-9a1f@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-54246","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2426152","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-54246","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-54246","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025123052-CVE-2023-54246-8abc@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-54267","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2426174","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-54267","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-54267","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025123059-CVE-2023-54267-6736@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-54268","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2426091","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-54268","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-54268","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025123000-CVE-2023-54268-3ba2@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-54271","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2426240","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-54271","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-54271","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025123001-CVE-2023-54271-d75a@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-54291","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2426074","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-54291","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-54291","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025123029-CVE-2023-54291-2983@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-54298","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2426121","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-54298","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-54298","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025123031-CVE-2023-54298-d33d@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-54299","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2426249","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-54299","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-54299","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025123032-CVE-2023-54299-ec86@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-54301","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2426231","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-54301","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-54301","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025123032-CVE-2023-54301-630e@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-54323","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2426157","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-54323","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-54323","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025123015-CVE-2023-54323-423a@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-0340","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-0340","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-0340","tags":["advisory"]},{"url":"https://lore.kernel.org/lkml/5kn47peabxjrptkqa6dwtyus35ahf4pcj4qm4pumse33kxqpjw@mec4se5relrc/T/","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-1151","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-1151","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-1151","tags":["advisory"]},{"url":"https://lore.kernel.org/all/20240207132416.1488485-1-aconole@redhat.com/","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-22099","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-22099","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-22099","tags":["advisory"]},{"url":"https://git.kernel.org/pub/scm/linux/kernel/git/bluetooth/bluetooth-next.git/commit/?id=6ec00b0737fe","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-23307","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-23307","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-23307","tags":["advisory"]},{"url":"https://bugzilla.openanolis.cn/show_bug.cgi?id=7975","tags":["article"]},{"url":"https://lore.kernel.org/linux-raid/20240112071017.16313-1-2045gemini@gmail.com/#r","tags":["article"]},{"url":"https://patchwork.kernel.org/project/linux-raid/patch/20240112071017.16313-1-2045gemini@gmail.com/","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-23848","tags":["report"]},{"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://access.redhat.com/security/cve/CVE-2024-24857","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-24857","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-24857","tags":["advisory"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-24858","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-24858","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-24858","tags":["advisory"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-24859","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-24859","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-24859","tags":["advisory"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-25739","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-25739","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-25739","tags":["advisory"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-26589","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-26589","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-26589","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024022257-CVE-2024-26589-0ee1@gregkh/T/#u","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-26591","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-26591","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-26591","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024022258-CVE-2024-26591-8b42@gregkh/T/#u","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-26601","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-26601","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-26601","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024022411-CVE-2024-26601-b6ac@gregkh/T/#u","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-26603","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-26603","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-26603","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024022415-CVE-2024-26603-42c2@gregkh/T/#u","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-26605","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-26605","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-26605","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024022419-CVE-2024-26605-7b06@gregkh/T/#u","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-26611","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-26611","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-26611","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/20240229155245.1571576-43-lee@kernel.org/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-26612","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-26612","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-26612","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/20240229155245.1571576-44-lee@kernel.org/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-26614","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-26614","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-26614","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/20240229155245.1571576-46-lee@kernel.org/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-26618","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-26618","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-26618","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/20240229155245.1571576-50-lee@kernel.org/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-26631","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-26631","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-26631","tags":["advisory"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-26638","tags":["report"]},{"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://access.redhat.com/security/cve/CVE-2024-26641","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-26641","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-26641","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/20240318102117.2839904-12-lee@kernel.org/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-26645","tags":["report"]},{"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://access.redhat.com/security/cve/CVE-2024-26646","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-26646","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-26646","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/20240326175007.1388794-14-lee@kernel.org/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-26650","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-26650","tags":["advisory"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-26656","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-26656","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-26656","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024040247-CVE-2024-26656-ffaa@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-26660","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-26660","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-26660","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024040222-CVE-2024-26660-3f40@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-26661","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-26661","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-26661","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024040223-CVE-2024-26661-bef6@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-26662","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-26662","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-26662","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024040223-CVE-2024-26662-863c@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-26663","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-26663","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-26663","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024040223-CVE-2024-26663-9705@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-26664","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-26664","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-26664","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024040223-CVE-2024-26664-03db@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-26669","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-26669","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-26669","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024040237-CVE-2024-26669-ca3c@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-26670","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-26670","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-26670","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024040238-CVE-2024-26670-ecbd@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-26672","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-26672","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-26672","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024040219-CVE-2024-26672-e96e@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-26674","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-26674","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-26674","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024040252-CVE-2024-26674-4ff9@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-26675","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-26675","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-26675","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024040252-CVE-2024-26675-5b19@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-26678","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-26678","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-26678","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024040253-CVE-2024-26678-2cf0@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-26679","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-26679","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-26679","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024040253-CVE-2024-26679-d520@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-26680","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-26680","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-26680","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024040253-CVE-2024-26680-d16c@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-26686","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-26686","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-26686","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024040335-CVE-2024-26686-b22f@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-26691","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-26691","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-26691","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024040336-CVE-2024-26691-fff7@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-26700","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-26700","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-26700","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024040339-CVE-2024-26700-a2b8@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-26704","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-26704","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-26704","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024040340-CVE-2024-26704-a082@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-26707","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-26707","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-26707","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024040341-CVE-2024-26707-1153@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-26708","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-26708","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-26708","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024040341-CVE-2024-26708-c98a@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-26712","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-26712","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-26712","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024040342-CVE-2024-26712-d713@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-26717","tags":["report"]},{"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://access.redhat.com/security/cve/CVE-2024-26719","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-26719","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-26719","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024040344-CVE-2024-26719-b66e@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-26725","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-26725","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-26725","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024040346-CVE-2024-26725-d16b@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-26733","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-26733","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-26733","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024040358-CVE-2024-26733-617f@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-26734","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2273244","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-26734","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-26734","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024040359-CVE-2024-26734-277b@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-26740","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-26740","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-26740","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024040300-CVE-2024-26740-4d6f@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-26743","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-26743","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-26743","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024040301-CVE-2024-26743-6034@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-26744","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-26744","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-26744","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024040301-CVE-2024-26744-d344@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-26746","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-26746","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-26746","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024040457-CVE-2024-26746-8aa9@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-26757","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-26757","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-26757","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024040304-CVE-2024-26757-7f96@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-26758","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-26758","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-26758","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024040304-CVE-2024-26758-dcc3@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-26759","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-26759","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-26759","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024040304-CVE-2024-26759-45f1@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-26761","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-26761","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-26761","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024040305-CVE-2024-26761-0646@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-26767","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-26767","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-26767","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024040306-CVE-2024-26767-bdac@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-26772","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-26772","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-26772","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024040308-CVE-2024-26772-5168@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-26774","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-26774","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-26774","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024040308-CVE-2024-26774-52d9@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-26782","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-26782","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-26782","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024040458-CVE-2024-26782-71ca@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-26785","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-26785","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-26785","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024040459-CVE-2024-26785-857d@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-26786","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-26786","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-26786","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024040459-CVE-2024-26786-802f@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-26803","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-26803","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-26803","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024040404-CVE-2024-26803-9985@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-26812","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-26812","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-26812","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024040550-CVE-2024-26812-1e08@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-26815","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-26815","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-26815","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024041006-CVE-2024-26815-7f4e@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-26835","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-26835","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-26835","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024041714-CVE-2024-26835-083d@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-26837","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-26837","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-26837","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024041715-CVE-2024-26837-753c@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-26838","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-26838","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-26838","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024041715-CVE-2024-26838-2fdb@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-26840","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-26840","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-26840","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024041715-CVE-2024-26840-057d@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-26843","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-26843","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-26843","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024041716-CVE-2024-26843-51a0@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-26846","tags":["report"]},{"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://access.redhat.com/security/cve/CVE-2024-26857","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-26857","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-26857","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024041724-CVE-2024-26857-75ac@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-26861","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-26861","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-26861","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024041736-CVE-2024-26861-3a78@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-26862","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-26862","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-26862","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024041736-CVE-2024-26862-2605@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-26863","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-26863","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-26863","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024041736-CVE-2024-26863-b742@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-26870","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-26870","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-26870","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024041738-CVE-2024-26870-7aea@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-26872","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-26872","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-26872","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024041738-CVE-2024-26872-2d38@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-26878","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-26878","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-26878","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024041740-CVE-2024-26878-5748@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-26882","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-26882","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-26882","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024041741-CVE-2024-26882-be35@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-26889","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-26889","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-26889","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024041742-CVE-2024-26889-edfc@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-26890","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-26890","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-26890","tags":["advisory"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-26892","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-26892","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-26892","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024041743-CVE-2024-26892-809e@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-26894","tags":["report"]},{"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://access.redhat.com/security/cve/CVE-2024-26899","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-26899","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-26899","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024041745-CVE-2024-26899-3f41@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-26900","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-26900","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-26900","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024041745-CVE-2024-26900-70a3@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-26901","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-26901","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-26901","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024041745-CVE-2024-26901-34e7@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-26903","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-26903","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-26903","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024041745-CVE-2024-26903-de5c@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-26906","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-26906","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-26906","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024041746-CVE-2024-26906-bb35@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-26907","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-26907","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-26907","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024041746-CVE-2024-26907-a02d@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-26915","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-26915","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-26915","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024041737-CVE-2024-26915-112b@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-26920","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-26920","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-26920","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024041738-CVE-2024-26920-a681@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-26921","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-26921","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-26921","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024041819-CVE-2024-26921-e3b3@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-26922","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-26922","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-26922","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024042317-CVE-2024-26922-896d@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-26924","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-26924","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-26924","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024042420-CVE-2024-26924-4d1e@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-26927","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-26927","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-26927","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024042844-CVE-2024-26927-3374@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-26928","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-26928","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-26928","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024042849-CVE-2024-26928-e543@gregkh/","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-26933","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-26933","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-26933","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024050123-CVE-2024-26933-c18d@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-26934","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-26934","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-26934","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024050123-CVE-2024-26934-e2fc@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-26937","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-26937","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-26937","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024050124-CVE-2024-26937-3d21@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-26938","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-26938","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-26938","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024050124-CVE-2024-26938-b3f9@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-26939","tags":["report"]},{"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://access.redhat.com/security/cve/CVE-2024-26940","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-26940","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-26940","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024050125-CVE-2024-26940-1785@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-26950","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-26950","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-26950","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024050127-CVE-2024-26950-4424@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-26951","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-26951","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-26951","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024050127-CVE-2024-26951-5cbe@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-26953","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-26953","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-26953","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024050128-CVE-2024-26953-8304@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-26958","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-26958","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-26958","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024050129-CVE-2024-26958-6c15@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-26960","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-26960","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-26960","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024050129-CVE-2024-26960-ad6b@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-26962","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-26962","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-26962","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024050130-CVE-2024-26962-cbb0@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-26964","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-26964","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-26964","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024050130-CVE-2024-26964-54c8@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-26973","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-26973","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-26973","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024050132-CVE-2024-26973-54a3@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-26975","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-26975","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-26975","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024050133-CVE-2024-26975-d184@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-26976","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-26976","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-26976","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024050133-CVE-2024-26976-60d4@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-26984","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-26984","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-26984","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024050142-CVE-2024-26984-3028@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-26987","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-26987","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-26987","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024050143-CVE-2024-26987-507c@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-26988","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-26988","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-26988","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024050143-CVE-2024-26988-c304@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-26989","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-26989","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-26989","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024050143-CVE-2024-26989-851d@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-26990","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-26990","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-26990","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024050143-CVE-2024-26990-0a1f@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-26992","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-26992","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-26992","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024050144-CVE-2024-26992-4f0e@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-27003","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-27003","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-27003","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024050146-CVE-2024-27003-c862@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-27004","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-27004","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-27004","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024050147-CVE-2024-27004-c429@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-27010","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-27010","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-27010","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024050148-CVE-2024-27010-5a68@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-27011","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-27011","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-27011","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024050148-CVE-2024-27011-2c70@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-27012","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-27012","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-27012","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024050148-CVE-2024-27012-5564@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-27013","tags":["report"]},{"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://access.redhat.com/security/cve/CVE-2024-27014","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-27014","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-27014","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024050149-CVE-2024-27014-d2dc@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-27015","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-27015","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-27015","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024050149-CVE-2024-27015-9ce1@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-27017","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-27017","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-27017","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024050150-CVE-2024-27017-d867@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-27023","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-27023","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-27023","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024050105-CVE-2024-27023-4810@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-27025","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-27025","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-27025","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024050107-CVE-2024-27025-babd@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-27038","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-27038","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-27038","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024050112-CVE-2024-27038-3af3@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-27042","tags":["report"]},{"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://access.redhat.com/security/cve/CVE-2024-27048","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-27048","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-27048","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024050114-CVE-2024-27048-016f@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-27057","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-27057","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-27057","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024050116-CVE-2024-27057-c0fb@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-27062","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-27062","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-27062","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024050130-CVE-2024-27062-3291@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-27079","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-27079","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-27079","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024050134-CVE-2024-27079-f478@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-27389","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-27389","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-27389","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024050135-CVE-2024-27389-fb3a@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-27395","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-27395","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-27395","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024050836-CVE-2024-27395-573e@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-27404","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-27404","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-27404","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024051738-CVE-2024-27404-ab54@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-27410","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-27410","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-27410","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024051701-CVE-2024-27410-874a@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-27414","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-27414","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-27414","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024051702-CVE-2024-27414-5c5d@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-27431","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-27431","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-27431","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024051723-CVE-2024-27431-30ae@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-27436","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-27436","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-27436","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024051711-CVE-2024-27436-2227@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-27437","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-27437","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-27437","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024040551-CVE-2024-27437-cc07@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-31076","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-31076","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-31076","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024062134-CVE-2024-31076-786e@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-35787","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-35787","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-35787","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024051707-CVE-2024-35787-dede@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-35794","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-35794","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-35794","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024051709-CVE-2024-35794-f42d@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-35795","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-35795","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-35795","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024051734-CVE-2024-35795-ee3e@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-35801","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-35801","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-35801","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024051738-CVE-2024-35801-8038@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-35805","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-35805","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-35805","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024051739-CVE-2024-35805-179f@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-35807","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-35807","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-35807","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024051740-CVE-2024-35807-2a9e@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-35808","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-35808","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-35808","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024051740-CVE-2024-35808-2bf6@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-35809","tags":["report"]},{"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://access.redhat.com/security/cve/CVE-2024-35810","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-35810","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-35810","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024051741-CVE-2024-35810-1b33@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-35812","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-35812","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-35812","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024051741-CVE-2024-35812-c804@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-35814","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-35814","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-35814","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024051742-CVE-2024-35814-98c7@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-35817","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-35817","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-35817","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024051743-CVE-2024-35817-d29b@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-35822","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-35822","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-35822","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024051744-CVE-2024-35822-410b@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-35824","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-35824","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-35824","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024051737-CVE-2024-35824-7302@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-35827","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-35827","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-35827","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024051741-CVE-2024-35827-822c@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-35831","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-35831","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-35831","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024051742-CVE-2024-35831-abcc@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-35835","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-35835","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-35835","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024051730-CVE-2024-35835-d75f@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-35838","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-35838","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-35838","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024051731-CVE-2024-35838-d072@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-35840","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-35840","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-35840","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024051756-CVE-2024-35840-99fa@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-35843","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-35843","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-35843","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024051717-CVE-2024-35843-516e@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-35847","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-35847","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-35847","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024051738-CVE-2024-35847-7e4b@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-35853","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-35853","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-35853","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024051740-CVE-2024-35853-869a@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-35854","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-35854","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-35854","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024051740-CVE-2024-35854-d17b@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-35855","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-35855","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-35855","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024051741-CVE-2024-35855-c1fb@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-35859","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-35859","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024051742-CVE-2024-35859-23c9@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-35861","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-35861","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-35861","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024051937-CVE-2024-35861-dcfe@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-35862","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-35862","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-35862","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024051937-CVE-2024-35862-eda2@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-35863","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-35863","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-35863","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024051938-CVE-2024-35863-7c05@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-35864","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-35864","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-35864","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024051938-CVE-2024-35864-3536@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-35865","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-35865","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-35865","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024051939-CVE-2024-35865-c095@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-35866","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-35866","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-35866","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024051939-CVE-2024-35866-97e5@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-35867","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-35867","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-35867","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024051939-CVE-2024-35867-15e3@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-35869","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-35869","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-35869","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024051940-CVE-2024-35869-73f8@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-35872","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-35872","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-35872","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024051941-CVE-2024-35872-4632@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-35876","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-35876","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-35876","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024051943-CVE-2024-35876-d9b5@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-35877","tags":["report"]},{"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://access.redhat.com/security/cve/CVE-2024-35878","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-35878","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-35878","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024051943-CVE-2024-35878-5af8@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-35880","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-35880","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-35880","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024051944-CVE-2024-35880-6ffb@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-35886","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-35886","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-35886","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024051946-CVE-2024-35886-19d4@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-35888","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-35888","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-35888","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024051947-CVE-2024-35888-1e04@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-35892","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-35892","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-35892","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024051949-CVE-2024-35892-0f0c@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-35894","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-35894","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-35894","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024051949-CVE-2024-35894-fd19@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-35900","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-35900","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-35900","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024051952-CVE-2024-35900-c2c9@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-35904","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-35904","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-35904","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024051953-CVE-2024-35904-7f85@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-35905","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-35905","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-35905","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024051954-CVE-2024-35905-d079@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-35908","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-35908","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-35908","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024051955-CVE-2024-35908-e78a@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-35912","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-35912","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-35912","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024051956-CVE-2024-35912-b093@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-35913","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-35913","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-35913","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024051956-CVE-2024-35913-72a4@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-35918","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-35918","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-35918","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024051912-CVE-2024-35918-3fed@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-35923","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-35923","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-35923","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024051914-CVE-2024-35923-ddae@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-35924","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-35924","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-35924","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024051914-CVE-2024-35924-90f6@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-35925","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-35925","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-35925","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024051914-CVE-2024-35925-fa17@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-35927","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-35927","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-35927","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024051915-CVE-2024-35927-2100@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-35928","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-35928","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-35928","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024051915-CVE-2024-35928-ead3@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-35930","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-35930","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-35930","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024051916-CVE-2024-35930-5571@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-35931","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-35931","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-35931","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024051916-CVE-2024-35931-430d@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-35938","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-35938","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-35938","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024051918-CVE-2024-35938-0100@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-35939","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-35939","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-35939","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024051919-CVE-2024-35939-f877@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-35942","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-35942","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-35942","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024051919-CVE-2024-35942-af72@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-35944","tags":["report"]},{"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://access.redhat.com/security/cve/CVE-2024-35946","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-35946","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-35946","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024051921-CVE-2024-35946-c2c2@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-35947","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-35947","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-35947","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024051952-CVE-2024-35947-09bb@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-35950","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-35950","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-35950","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024052015-CVE-2024-35950-41bf@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-35952","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-35952","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-35952","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024052017-CVE-2024-35952-645b@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-35954","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-35954","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-35954","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024052018-CVE-2024-35954-cdbf@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-35957","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-35957","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-35957","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024052019-CVE-2024-35957-8c83@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-35959","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-35959","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-35959","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024052019-CVE-2024-35959-6e06@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-35973","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-35973","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-35973","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024052024-CVE-2024-35973-1b5b@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-35976","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-35976","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-35976","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024052024-CVE-2024-35976-339b@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-35979","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-35979","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-35979","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024052025-CVE-2024-35979-2618@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-35983","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-35983","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-35983","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024052018-CVE-2024-35983-a607@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-35991","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-35991","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-35991","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024052020-CVE-2024-35991-5f06@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-35995","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-35995","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-35995","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024052021-CVE-2024-35995-abbc@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-36002","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2281961","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-36002","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-36002","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024052023-CVE-2024-36002-c5bc@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-36006","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-36006","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-36006","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024052025-CVE-2024-36006-c032@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-36010","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-36010","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-36010","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024052237-CVE-2024-36010-c98b@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-36015","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-36015","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-36015","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024052957-CVE-2024-36015-3c7c@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-36022","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-36022","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-36022","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024053013-CVE-2024-36022-fe0e@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-36028","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-36028","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-36028","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024053057-CVE-2024-36028-e4a3@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-36030","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-36030","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-36030","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024053057-CVE-2024-36030-51dc@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-36031","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-36031","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-36031","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024053000-CVE-2024-36031-46f2@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-36477","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-36477","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-36477","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024062150-CVE-2024-36477-7063@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-36881","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-36881","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-36881","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024053032-CVE-2024-36881-24d0@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-36882","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-36882","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-36882","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024053032-CVE-2024-36882-79ff@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-36884","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-36884","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-36884","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024053032-CVE-2024-36884-c00b@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-36885","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-36885","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-36885","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024053032-CVE-2024-36885-cb0b@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-36891","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-36891","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-36891","tags":["advisory"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-36896","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-36896","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024053034-CVE-2024-36896-783f@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-36901","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-36901","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024053035-CVE-2024-36901-fb16@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-36902","tags":["report"]},{"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://access.redhat.com/security/cve/CVE-2024-36905","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-36905","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-36905","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024053036-CVE-2024-36905-5884@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-36917","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-36917","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-36917","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024053039-CVE-2024-36917-f9e3@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-36920","tags":["report"]},{"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://access.redhat.com/security/cve/CVE-2024-36926","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-36926","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-36926","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024053040-CVE-2024-36926-c3a3@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-36927","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-36927","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-36927","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024053040-CVE-2024-36927-976e@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-36928","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2284498","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-36928","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-36928","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024053041-CVE-2024-36928-845b@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-36930","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-36930","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-36930","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024053041-CVE-2024-36930-8906@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-36932","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-36932","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-36932","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024053041-CVE-2024-36932-c22d@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-36933","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-36933","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-36933","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024053042-CVE-2024-36933-444e@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-36936","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-36936","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-36936","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024053042-CVE-2024-36936-3116@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-36939","tags":["report"]},{"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://access.redhat.com/security/cve/CVE-2024-36940","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-36940","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-36940","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024053043-CVE-2024-36940-0c83@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-36944","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-36944","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024053038-CVE-2024-36944-9d15@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-36945","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-36945","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-36945","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024053039-CVE-2024-36945-18ae@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-36955","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-36955","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-36955","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024053041-CVE-2024-36955-312f@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-36956","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-36956","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-36956","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024053041-CVE-2024-36956-59d8@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-36960","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-36960","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-36960","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024060341-CVE-2024-36960-d1bf@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-36961","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-36961","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-36961","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024060344-CVE-2024-36961-58bb@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-36967","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-36967","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-36967","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024060804-CVE-2024-36967-b73d@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-36974","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-36974","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-36974","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024061810-CVE-2024-36974-a482@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-36977","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-36977","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-36977","tags":["advisory"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-38388","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-38388","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-38388","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024062137-CVE-2024-38388-fb75@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-38555","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-38555","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-38555","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024061952-CVE-2024-38555-aefb@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-38581","tags":["report"]},{"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://access.redhat.com/security/cve/CVE-2024-38596","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-38596","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-38596","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024061956-CVE-2024-38596-f660@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-38598","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-38598","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-38598","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024061956-CVE-2024-38598-8629@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-38600","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-38600","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024061957-CVE-2024-38600-aa7e@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-38604","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-38604","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-38604","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024061924-CVE-2024-38604-a738@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-38605","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-38605","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-38605","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024061925-CVE-2024-38605-3dc4@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-38612","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2293351","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-38612","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-38612","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024061922-CVE-2024-38612-7fc1@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-38618","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-38618","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-38618","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024061923-CVE-2024-38618-35a9@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-38627","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-38627","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-38627","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024062140-CVE-2024-38627-9b57@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-38629","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-38629","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-38629","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024062141-CVE-2024-38629-47c6@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-38632","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-38632","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-38632","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024062142-CVE-2024-38632-eaf6@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-38635","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-38635","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-38635","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024062143-CVE-2024-38635-a3b1@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-39276","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-39276","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-39276","tags":["advisory"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-39291","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-39291","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-39291","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024062432-CVE-2024-39291-be2c@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-39298","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-39298","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-39298","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024062549-CVE-2024-39298-53e8@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-39471","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-39471","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024062501-CVE-2024-39471-3dee@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-39473","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-39473","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024070516-CVE-2024-39473-d28c@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-39474","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-39474","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-39474","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024070518-CVE-2024-39474-97cf@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-39479","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-39479","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-39479","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024070519-CVE-2024-39479-5bd1@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-39486","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-39486","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024070628-CVE-2024-39486-1ea1@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-39488","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-39488","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-39488","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024071013-CVE-2024-39488-f796@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-39491","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-39491","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-39491","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024071016-CVE-2024-39491-fb62@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-39497","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-39497","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-39497","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024071202-CVE-2024-39497-834c@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-39498","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-39498","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-39498","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024071203-CVE-2024-39498-8421@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-39499","tags":["report"]},{"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://access.redhat.com/security/cve/CVE-2024-39501","tags":["report"]},{"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://access.redhat.com/security/cve/CVE-2024-39503","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-39503","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024071204-CVE-2024-39503-e604@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-39507","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-39507","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-39507","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024071205-CVE-2024-39507-cbc6@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-39508","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-39508","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-39508","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024071206-CVE-2024-39508-20c3@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-40901","tags":["report"]},{"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://access.redhat.com/security/cve/CVE-2024-40903","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-40903","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-40903","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024071208-CVE-2024-40903-8fd1@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-40906","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-40906","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024071209-CVE-2024-40906-b9e3@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-40907","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-40907","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-40907","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024071209-CVE-2024-40907-5305@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-40913","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-40913","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024071210-CVE-2024-40913-5952@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-40919","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-40919","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-40919","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024071212-CVE-2024-40919-2997@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-40922","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-40922","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024071213-CVE-2024-40922-461c@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-40923","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-40923","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-40923","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024071213-CVE-2024-40923-5e9e@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-40924","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-40924","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-40924","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024071213-CVE-2024-40924-9b9b@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-40925","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-40925","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-40925","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024071214-CVE-2024-40925-d411@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-40930","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-40930","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-40930","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024071215-CVE-2024-40930-f6bb@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-40940","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-40940","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-40940","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024071218-CVE-2024-40940-5b9e@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-40945","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-40945","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-40945","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024071220-CVE-2024-40945-79e6@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-40948","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-40948","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-40948","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024071222-CVE-2024-40948-e1a6@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-40965","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-40965","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-40965","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024071227-CVE-2024-40965-d9b9@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-40966","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-40966","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-40966","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024071227-CVE-2024-40966-cea6@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-40967","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-40967","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024071227-CVE-2024-40967-665f@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-40988","tags":["report"]},{"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://access.redhat.com/security/cve/CVE-2024-40989","tags":["report"]},{"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://access.redhat.com/security/cve/CVE-2024-40997","tags":["report"]},{"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://access.redhat.com/security/cve/CVE-2024-41001","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-41001","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-41001","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024071253-CVE-2024-41001-7879@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-41007","tags":["report"]},{"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://access.redhat.com/security/cve/CVE-2024-41008","tags":["report"]},{"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://access.redhat.com/security/cve/CVE-2024-41012","tags":["report"]},{"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://access.redhat.com/security/cve/CVE-2024-41020","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-41020","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024072927-CVE-2024-41020-52c6@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-41032","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-41032","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-41032","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024072922-CVE-2024-41032-6284@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-41038","tags":["report"]},{"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://access.redhat.com/security/cve/CVE-2024-41039","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-41039","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024072924-CVE-2024-41039-b3bc@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-41042","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-41042","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-41042","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024072924-CVE-2024-41042-c338@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-41049","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-41049","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024072927-CVE-2024-41049-bf28@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-41056","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-41056","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024072930-CVE-2024-41056-c324@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-41057","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-41057","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-41057","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024072902-CVE-2024-41057-1d06@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-41058","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-41058","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-41058","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024072905-CVE-2024-41058-4593@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-41060","tags":["report"]},{"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://access.redhat.com/security/cve/CVE-2024-41063","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-41063","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024072906-CVE-2024-41063-b9bd@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-41065","tags":["report"]},{"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://access.redhat.com/security/cve/CVE-2024-41077","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-41077","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024072910-CVE-2024-41077-9c88@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-41079","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-41079","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-41079","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024072925-CVE-2024-41079-09c3@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-41082","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-41082","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-41082","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024072926-CVE-2024-41082-6e0a@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-41084","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-41084","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-41084","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024072951-CVE-2024-41084-c144@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-41085","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-41085","tags":["advisory","report"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024072951-CVE-2024-41085-9bbd@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-41089","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-41089","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-41089","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024072952-CVE-2024-41089-5d63@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-41092","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-41092","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-41092","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024072953-CVE-2024-41092-8bd7@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-41093","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-41093","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-41093","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024072953-CVE-2024-41093-9d6c@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-41094","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-41094","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-41094","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024072953-CVE-2024-41094-374d@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-41095","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-41095","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-41095","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024072954-CVE-2024-41095-7b63@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-42070","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-42070","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-42070","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024072952-CVE-2024-42070-b271@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-42078","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-42078","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-42078","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024072954-CVE-2024-42078-bd37@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-42084","tags":["report"]},{"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://access.redhat.com/security/cve/CVE-2024-42090","tags":["report"]},{"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://access.redhat.com/security/cve/CVE-2024-42101","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-42101","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-42101","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024073018-CVE-2024-42101-f246@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-42114","tags":["report"]},{"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://access.redhat.com/security/cve/CVE-2024-42123","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-42123","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-42123","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024073025-CVE-2024-42123-056d@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-42124","tags":["report"]},{"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://access.redhat.com/security/cve/CVE-2024-42125","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-42125","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-42125","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024073026-CVE-2024-42125-b515@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-42132","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-42132","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-42132","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024073028-CVE-2024-42132-49bf@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-42141","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-42141","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-42141","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024073030-CVE-2024-42141-9017@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-42154","tags":["report"]},{"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://access.redhat.com/security/cve/CVE-2024-42159","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-42159","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-42159","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024073036-CVE-2024-42159-c19e@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-42226","tags":["report"]},{"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://access.redhat.com/security/cve/CVE-2024-42228","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-42228","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024073038-CVE-2024-42228-86f5@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-42237","tags":["report"]},{"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://access.redhat.com/security/cve/CVE-2024-42238","tags":["report"]},{"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://access.redhat.com/security/cve/CVE-2024-42240","tags":["report"]},{"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://access.redhat.com/security/cve/CVE-2024-42245","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2303513","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-42245","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-42245","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024080742-CVE-2024-42245-1413@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-42258","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-42258","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-42258","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024081216-CVE-2024-42258-e3f3@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-42268","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2305413","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-42268","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-42268","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024081738-CVE-2024-42268-2084@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-42271","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2305416","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-42271","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-42271","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024081739-CVE-2024-42271-c501@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-42276","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2305421","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-42276","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-42276","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024081741-CVE-2024-42276-cb0a@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-42301","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-42301","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-42301","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024081749-CVE-2024-42301-4026@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-43817","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2305475","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-43817","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-43817","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024081723-CVE-2024-43817-2e95@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-43826","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2305484","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-43826","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-43826","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024081726-CVE-2024-43826-2a5f@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-43830","tags":["report"]},{"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://access.redhat.com/security/cve/CVE-2024-43842","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2305500","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-43842","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-43842","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024081730-CVE-2024-43842-31e7@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-43856","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2305514","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-43856","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-43856","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024081732-CVE-2024-43856-9087@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-43865","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2306357","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-43865","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-43865","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024082156-CVE-2024-43865-743d@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-43866","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2306358","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-43866","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-43866","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024082157-CVE-2024-43866-66ed@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-43869","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-43869","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-43869","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024082133-CVE-2024-43869-26aa@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-43870","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2306364","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-43870","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-43870","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024082135-CVE-2024-43870-2b6f@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-43879","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2306373","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-43879","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-43879","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024082137-CVE-2024-43879-95cb@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-43888","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-43888","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-43888","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024082659-CVE-2024-43888-5beb@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-43892","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-43892","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-43892","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024082604-CVE-2024-43892-584a@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-43911","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-43911","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-43911","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024082631-CVE-2024-43911-96bb@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-44947","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-44947","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-44947","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024090219-CVE-2024-44947-f49c@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-44960","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-44960","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-44960","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024090413-CVE-2024-44960-039b@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-44965","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-44965","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-44965","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024090415-CVE-2024-44965-d41d@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-44970","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-44970","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-44970","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024090456-CVE-2024-44970-f687@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-44984","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-44984","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-44984","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024090445-CVE-2024-44984-43ea@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-45005","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-45005","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-45005","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024090451-CVE-2024-45005-2297@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-58239","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2390320","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-58239","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-58239","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025082210-CVE-2024-58239-dd4f@gregkh/T","tags":["article"]},{"url":"https://www.suse.com/support/update/announcement/2025/suse-su-202502254-1/","tags":["advisory"]},{"url":"https://bugzilla.suse.com/1151679","tags":["report"]},{"url":"https://bugzilla.suse.com/1151680","tags":["report"]},{"url":"https://bugzilla.suse.com/1151794","tags":["report"]},{"url":"https://bugzilla.suse.com/1151927","tags":["report"]},{"url":"https://bugzilla.suse.com/1210025","tags":["report"]},{"url":"https://bugzilla.suse.com/1211226","tags":["report"]},{"url":"https://bugzilla.suse.com/1215199","tags":["report"]},{"url":"https://bugzilla.suse.com/1218184","tags":["report"]},{"url":"https://bugzilla.suse.com/1220112","tags":["report"]},{"url":"https://bugzilla.suse.com/1223008","tags":["report"]},{"url":"https://bugzilla.suse.com/1226498","tags":["report"]},{"url":"https://bugzilla.suse.com/1228478","tags":["report"]},{"url":"https://bugzilla.suse.com/1228557","tags":["report"]},{"url":"https://bugzilla.suse.com/1228854","tags":["report"]},{"url":"https://bugzilla.suse.com/1229491","tags":["report"]},{"url":"https://bugzilla.suse.com/1230337","tags":["report"]},{"url":"https://bugzilla.suse.com/1231913","tags":["report"]},{"url":"https://bugzilla.suse.com/1232504","tags":["report"]},{"url":"https://bugzilla.suse.com/1232882","tags":["report"]},{"url":"https://bugzilla.suse.com/1233482","tags":["report"]},{"url":"https://bugzilla.suse.com/1235064","tags":["report"]},{"url":"https://bugzilla.suse.com/1235490","tags":["report"]},{"url":"https://bugzilla.suse.com/1235728","tags":["report"]},{"url":"https://bugzilla.suse.com/1235968","tags":["report"]},{"url":"https://bugzilla.suse.com/1236208","tags":["report"]},{"url":"https://bugzilla.suse.com/1237200","tags":["report"]},{"url":"https://bugzilla.suse.com/1237312","tags":["report"]},{"url":"https://bugzilla.suse.com/1237887","tags":["report"]},{"url":"https://bugzilla.suse.com/1237895","tags":["report"]},{"url":"https://bugzilla.suse.com/1237905","tags":["report"]},{"url":"https://bugzilla.suse.com/1237910","tags":["report"]},{"url":"https://bugzilla.suse.com/1237913","tags":["report"]},{"url":"https://bugzilla.suse.com/1238212","tags":["report"]},{"url":"https://bugzilla.suse.com/1238478","tags":["report"]},{"url":"https://bugzilla.suse.com/1238495","tags":["report"]},{"url":"https://bugzilla.suse.com/1238508","tags":["report"]},{"url":"https://bugzilla.suse.com/1238741","tags":["report"]},{"url":"https://bugzilla.suse.com/1238859","tags":["report"]},{"url":"https://bugzilla.suse.com/1238965","tags":["report"]},{"url":"https://bugzilla.suse.com/1238982","tags":["report"]},{"url":"https://bugzilla.suse.com/1238995","tags":["report"]},{"url":"https://bugzilla.suse.com/1239063","tags":["report"]},{"url":"https://bugzilla.suse.com/1239090","tags":["report"]},{"url":"https://bugzilla.suse.com/1239485","tags":["report"]},{"url":"https://bugzilla.suse.com/1239925","tags":["report"]},{"url":"https://bugzilla.suse.com/1240170","tags":["report"]},{"url":"https://bugzilla.suse.com/1240180","tags":["report"]},{"url":"https://bugzilla.suse.com/1240577","tags":["report"]},{"url":"https://bugzilla.suse.com/1240579","tags":["report"]},{"url":"https://bugzilla.suse.com/1240589","tags":["report"]},{"url":"https://bugzilla.suse.com/1240610","tags":["report"]},{"url":"https://bugzilla.suse.com/1240650","tags":["report"]},{"url":"https://bugzilla.suse.com/1240686","tags":["report"]},{"url":"https://bugzilla.suse.com/1240696","tags":["report"]},{"url":"https://bugzilla.suse.com/1240702","tags":["report"]},{"url":"https://bugzilla.suse.com/1240710","tags":["report"]},{"url":"https://bugzilla.suse.com/1240723","tags":["report"]},{"url":"https://bugzilla.suse.com/1240798","tags":["report"]},{"url":"https://bugzilla.suse.com/1240814","tags":["report"]},{"url":"https://bugzilla.suse.com/1240823","tags":["report"]},{"url":"https://bugzilla.suse.com/1240866","tags":["report"]},{"url":"https://bugzilla.suse.com/1240998","tags":["report"]},{"url":"https://bugzilla.suse.com/1241166","tags":["report"]},{"url":"https://bugzilla.suse.com/1241191","tags":["report"]},{"url":"https://bugzilla.suse.com/1241278","tags":["report"]},{"url":"https://bugzilla.suse.com/1241298","tags":["report"]},{"url":"https://bugzilla.suse.com/1241340","tags":["report"]},{"url":"https://bugzilla.suse.com/1241388","tags":["report"]},{"url":"https://bugzilla.suse.com/1241414","tags":["report"]},{"url":"https://bugzilla.suse.com/1241457","tags":["report"]},{"url":"https://bugzilla.suse.com/1241492","tags":["report"]},{"url":"https://bugzilla.suse.com/1241519","tags":["report"]},{"url":"https://bugzilla.suse.com/1241538","tags":["report"]},{"url":"https://bugzilla.suse.com/1241544","tags":["report"]},{"url":"https://bugzilla.suse.com/1241572","tags":["report"]},{"url":"https://bugzilla.suse.com/1241576","tags":["report"]},{"url":"https://bugzilla.suse.com/1241590","tags":["report"]},{"url":"https://bugzilla.suse.com/1241592","tags":["report"]},{"url":"https://bugzilla.suse.com/1241595","tags":["report"]},{"url":"https://bugzilla.suse.com/1241617","tags":["report"]},{"url":"https://bugzilla.suse.com/1241625","tags":["report"]},{"url":"https://bugzilla.suse.com/1241635","tags":["report"]},{"url":"https://bugzilla.suse.com/1241644","tags":["report"]},{"url":"https://bugzilla.suse.com/1241654","tags":["report"]},{"url":"https://bugzilla.suse.com/1241689","tags":["report"]},{"url":"https://bugzilla.suse.com/1242035","tags":["report"]},{"url":"https://bugzilla.suse.com/1242044","tags":["report"]},{"url":"https://bugzilla.suse.com/1242086","tags":["report"]},{"url":"https://bugzilla.suse.com/1242163","tags":["report"]},{"url":"https://bugzilla.suse.com/1242343","tags":["report"]},{"url":"https://bugzilla.suse.com/1242414","tags":["report"]},{"url":"https://bugzilla.suse.com/1242501","tags":["report"]},{"url":"https://bugzilla.suse.com/1242504","tags":["report"]},{"url":"https://bugzilla.suse.com/1242508","tags":["report"]},{"url":"https://bugzilla.suse.com/1242512","tags":["report"]},{"url":"https://bugzilla.suse.com/1242514","tags":["report"]},{"url":"https://bugzilla.suse.com/1242515","tags":["report"]},{"url":"https://bugzilla.suse.com/1242520","tags":["report"]},{"url":"https://bugzilla.suse.com/1242521","tags":["report"]},{"url":"https://bugzilla.suse.com/1242524","tags":["report"]},{"url":"https://bugzilla.suse.com/1242529","tags":["report"]},{"url":"https://bugzilla.suse.com/1242530","tags":["report"]},{"url":"https://bugzilla.suse.com/1242531","tags":["report"]},{"url":"https://bugzilla.suse.com/1242532","tags":["report"]},{"url":"https://bugzilla.suse.com/1242556","tags":["report"]},{"url":"https://bugzilla.suse.com/1242559","tags":["report"]},{"url":"https://bugzilla.suse.com/1242563","tags":["report"]},{"url":"https://bugzilla.suse.com/1242564","tags":["report"]},{"url":"https://bugzilla.suse.com/1242565","tags":["report"]},{"url":"https://bugzilla.suse.com/1242566","tags":["report"]},{"url":"https://bugzilla.suse.com/1242567","tags":["report"]},{"url":"https://bugzilla.suse.com/1242568","tags":["report"]},{"url":"https://bugzilla.suse.com/1242569","tags":["report"]},{"url":"https://bugzilla.suse.com/1242573","tags":["report"]},{"url":"https://bugzilla.suse.com/1242574","tags":["report"]},{"url":"https://bugzilla.suse.com/1242575","tags":["report"]},{"url":"https://bugzilla.suse.com/1242577","tags":["report"]},{"url":"https://bugzilla.suse.com/1242578","tags":["report"]},{"url":"https://bugzilla.suse.com/1242584","tags":["report"]},{"url":"https://bugzilla.suse.com/1242587","tags":["report"]},{"url":"https://bugzilla.suse.com/1242591","tags":["report"]},{"url":"https://bugzilla.suse.com/1242709","tags":["report"]},{"url":"https://bugzilla.suse.com/1242724","tags":["report"]},{"url":"https://bugzilla.suse.com/1242725","tags":["report"]},{"url":"https://bugzilla.suse.com/1242727","tags":["report"]},{"url":"https://bugzilla.suse.com/1242729","tags":["report"]},{"url":"https://bugzilla.suse.com/1242758","tags":["report"]},{"url":"https://bugzilla.suse.com/1242760","tags":["report"]},{"url":"https://bugzilla.suse.com/1242761","tags":["report"]},{"url":"https://bugzilla.suse.com/1242764","tags":["report"]},{"url":"https://bugzilla.suse.com/1242766","tags":["report"]},{"url":"https://bugzilla.suse.com/1242770","tags":["report"]},{"url":"https://bugzilla.suse.com/1242781","tags":["report"]},{"url":"https://bugzilla.suse.com/1242782","tags":["report"]},{"url":"https://bugzilla.suse.com/1242785","tags":["report"]},{"url":"https://bugzilla.suse.com/1242792","tags":["report"]},{"url":"https://bugzilla.suse.com/1242834","tags":["report"]},{"url":"https://bugzilla.suse.com/1242846","tags":["report"]},{"url":"https://bugzilla.suse.com/1242849","tags":["report"]},{"url":"https://bugzilla.suse.com/1242850","tags":["report"]},{"url":"https://bugzilla.suse.com/1242863","tags":["report"]},{"url":"https://bugzilla.suse.com/1242865","tags":["report"]},{"url":"https://bugzilla.suse.com/1242871","tags":["report"]},{"url":"https://bugzilla.suse.com/1242873","tags":["report"]},{"url":"https://bugzilla.suse.com/1242906","tags":["report"]},{"url":"https://bugzilla.suse.com/1242907","tags":["report"]},{"url":"https://bugzilla.suse.com/1242908","tags":["report"]},{"url":"https://bugzilla.suse.com/1242909","tags":["report"]},{"url":"https://bugzilla.suse.com/1242930","tags":["report"]},{"url":"https://bugzilla.suse.com/1242940","tags":["report"]},{"url":"https://bugzilla.suse.com/1242943","tags":["report"]},{"url":"https://bugzilla.suse.com/1242945","tags":["report"]},{"url":"https://bugzilla.suse.com/1242946","tags":["report"]},{"url":"https://bugzilla.suse.com/1242947","tags":["report"]},{"url":"https://bugzilla.suse.com/1242948","tags":["report"]},{"url":"https://bugzilla.suse.com/1242949","tags":["report"]},{"url":"https://bugzilla.suse.com/1242952","tags":["report"]},{"url":"https://bugzilla.suse.com/1242953","tags":["report"]},{"url":"https://bugzilla.suse.com/1242954","tags":["report"]},{"url":"https://bugzilla.suse.com/1242955","tags":["report"]},{"url":"https://bugzilla.suse.com/1242957","tags":["report"]},{"url":"https://bugzilla.suse.com/1242959","tags":["report"]},{"url":"https://bugzilla.suse.com/1242961","tags":["report"]},{"url":"https://bugzilla.suse.com/1242964","tags":["report"]},{"url":"https://bugzilla.suse.com/1242966","tags":["report"]},{"url":"https://bugzilla.suse.com/1242967","tags":["report"]},{"url":"https://bugzilla.suse.com/1242973","tags":["report"]},{"url":"https://bugzilla.suse.com/1242974","tags":["report"]},{"url":"https://bugzilla.suse.com/1242977","tags":["report"]},{"url":"https://bugzilla.suse.com/1242982","tags":["report"]},{"url":"https://bugzilla.suse.com/1242990","tags":["report"]},{"url":"https://bugzilla.suse.com/1243000","tags":["report"]},{"url":"https://bugzilla.suse.com/1243006","tags":["report"]},{"url":"https://bugzilla.suse.com/1243011","tags":["report"]},{"url":"https://bugzilla.suse.com/1243015","tags":["report"]},{"url":"https://bugzilla.suse.com/1243049","tags":["report"]},{"url":"https://bugzilla.suse.com/1243051","tags":["report"]},{"url":"https://bugzilla.suse.com/1243055","tags":["report"]},{"url":"https://bugzilla.suse.com/1243060","tags":["report"]},{"url":"https://bugzilla.suse.com/1243074","tags":["report"]},{"url":"https://bugzilla.suse.com/1243076","tags":["report"]},{"url":"https://bugzilla.suse.com/1243082","tags":["report"]},{"url":"https://bugzilla.suse.com/1243330","tags":["report"]},{"url":"https://bugzilla.suse.com/1243342","tags":["report"]},{"url":"https://bugzilla.suse.com/1243456","tags":["report"]},{"url":"https://bugzilla.suse.com/1243467","tags":["report"]},{"url":"https://bugzilla.suse.com/1243469","tags":["report"]},{"url":"https://bugzilla.suse.com/1243470","tags":["report"]},{"url":"https://bugzilla.suse.com/1243471","tags":["report"]},{"url":"https://bugzilla.suse.com/1243472","tags":["report"]},{"url":"https://bugzilla.suse.com/1243473","tags":["report"]},{"url":"https://bugzilla.suse.com/1243475","tags":["report"]},{"url":"https://bugzilla.suse.com/1243476","tags":["report"]},{"url":"https://bugzilla.suse.com/1243480","tags":["report"]},{"url":"https://bugzilla.suse.com/1243506","tags":["report"]},{"url":"https://bugzilla.suse.com/1243509","tags":["report"]},{"url":"https://bugzilla.suse.com/1243511","tags":["report"]},{"url":"https://bugzilla.suse.com/1243514","tags":["report"]},{"url":"https://bugzilla.suse.com/1243515","tags":["report"]},{"url":"https://bugzilla.suse.com/1243516","tags":["report"]},{"url":"https://bugzilla.suse.com/1243517","tags":["report"]},{"url":"https://bugzilla.suse.com/1243522","tags":["report"]},{"url":"https://bugzilla.suse.com/1243523","tags":["report"]},{"url":"https://bugzilla.suse.com/1243524","tags":["report"]},{"url":"https://bugzilla.suse.com/1243528","tags":["report"]},{"url":"https://bugzilla.suse.com/1243529","tags":["report"]},{"url":"https://bugzilla.suse.com/1243530","tags":["report"]},{"url":"https://bugzilla.suse.com/1243534","tags":["report"]},{"url":"https://bugzilla.suse.com/1243536","tags":["report"]},{"url":"https://bugzilla.suse.com/1243537","tags":["report"]},{"url":"https://bugzilla.suse.com/1243538","tags":["report"]},{"url":"https://bugzilla.suse.com/1243540","tags":["report"]},{"url":"https://bugzilla.suse.com/1243542","tags":["report"]},{"url":"https://bugzilla.suse.com/1243543","tags":["report"]},{"url":"https://bugzilla.suse.com/1243544","tags":["report"]},{"url":"https://bugzilla.suse.com/1243545","tags":["report"]},{"url":"https://bugzilla.suse.com/1243548","tags":["report"]},{"url":"https://bugzilla.suse.com/1243551","tags":["report"]},{"url":"https://bugzilla.suse.com/1243559","tags":["report"]},{"url":"https://bugzilla.suse.com/1243560","tags":["report"]},{"url":"https://bugzilla.suse.com/1243562","tags":["report"]},{"url":"https://bugzilla.suse.com/1243567","tags":["report"]},{"url":"https://bugzilla.suse.com/1243571","tags":["report"]},{"url":"https://bugzilla.suse.com/1243572","tags":["report"]},{"url":"https://bugzilla.suse.com/1243573","tags":["report"]},{"url":"https://bugzilla.suse.com/1243574","tags":["report"]},{"url":"https://bugzilla.suse.com/1243575","tags":["report"]},{"url":"https://bugzilla.suse.com/1243589","tags":["report"]},{"url":"https://bugzilla.suse.com/1243620","tags":["report"]},{"url":"https://bugzilla.suse.com/1243621","tags":["report"]},{"url":"https://bugzilla.suse.com/1243624","tags":["report"]},{"url":"https://bugzilla.suse.com/1243625","tags":["report"]},{"url":"https://bugzilla.suse.com/1243626","tags":["report"]},{"url":"https://bugzilla.suse.com/1243627","tags":["report"]},{"url":"https://bugzilla.suse.com/1243628","tags":["report"]},{"url":"https://bugzilla.suse.com/1243649","tags":["report"]},{"url":"https://bugzilla.suse.com/1243659","tags":["report"]},{"url":"https://bugzilla.suse.com/1243660","tags":["report"]},{"url":"https://bugzilla.suse.com/1243664","tags":["report"]},{"url":"https://bugzilla.suse.com/1243698","tags":["report"]},{"url":"https://bugzilla.suse.com/1243774","tags":["report"]},{"url":"https://bugzilla.suse.com/1243782","tags":["report"]},{"url":"https://bugzilla.suse.com/1243823","tags":["report"]},{"url":"https://bugzilla.suse.com/1243827","tags":["report"]},{"url":"https://bugzilla.suse.com/1243832","tags":["report"]},{"url":"https://bugzilla.suse.com/1243836","tags":["report"]},{"url":"https://bugzilla.suse.com/1243847","tags":["report"]},{"url":"https://bugzilla.suse.com/1244100","tags":["report"]},{"url":"https://bugzilla.suse.com/1244145","tags":["report"]},{"url":"https://bugzilla.suse.com/1244172","tags":["report"]},{"url":"https://bugzilla.suse.com/1244174","tags":["report"]},{"url":"https://bugzilla.suse.com/1244176","tags":["report"]},{"url":"https://bugzilla.suse.com/1244229","tags":["report"]},{"url":"https://bugzilla.suse.com/1244234","tags":["report"]},{"url":"https://bugzilla.suse.com/1244241","tags":["report"]},{"url":"https://bugzilla.suse.com/1244261","tags":["report"]},{"url":"https://bugzilla.suse.com/1244274","tags":["report"]},{"url":"https://bugzilla.suse.com/1244275","tags":["report"]},{"url":"https://bugzilla.suse.com/1244277","tags":["report"]},{"url":"https://bugzilla.suse.com/1244309","tags":["report"]},{"url":"https://bugzilla.suse.com/1244313","tags":["report"]},{"url":"https://bugzilla.suse.com/1244337","tags":["report"]},{"url":"https://bugzilla.suse.com/1244626","tags":["report"]},{"url":"https://bugzilla.suse.com/1244725","tags":["report"]},{"url":"https://bugzilla.suse.com/1244727","tags":["report"]},{"url":"https://bugzilla.suse.com/1244729","tags":["report"]},{"url":"https://bugzilla.suse.com/1244731","tags":["report"]},{"url":"https://bugzilla.suse.com/1244732","tags":["report"]},{"url":"https://bugzilla.suse.com/1244736","tags":["report"]},{"url":"https://bugzilla.suse.com/1244737","tags":["report"]},{"url":"https://bugzilla.suse.com/1244738","tags":["report"]},{"url":"https://bugzilla.suse.com/1244739","tags":["report"]},{"url":"https://bugzilla.suse.com/1244743","tags":["report"]},{"url":"https://bugzilla.suse.com/1244746","tags":["report"]},{"url":"https://bugzilla.suse.com/1244747","tags":["report"]},{"url":"https://bugzilla.suse.com/1244759","tags":["report"]},{"url":"https://bugzilla.suse.com/1244789","tags":["report"]},{"url":"https://bugzilla.suse.com/1244862","tags":["report"]},{"url":"https://bugzilla.suse.com/1244906","tags":["report"]},{"url":"https://bugzilla.suse.com/1244938","tags":["report"]},{"url":"https://bugzilla.suse.com/1244995","tags":["report"]},{"url":"https://bugzilla.suse.com/1244996","tags":["report"]},{"url":"https://bugzilla.suse.com/1244999","tags":["report"]},{"url":"https://bugzilla.suse.com/1245001","tags":["report"]},{"url":"https://bugzilla.suse.com/1245003","tags":["report"]},{"url":"https://bugzilla.suse.com/1245004","tags":["report"]},{"url":"https://bugzilla.suse.com/1245025","tags":["report"]},{"url":"https://bugzilla.suse.com/1245042","tags":["report"]},{"url":"https://bugzilla.suse.com/1245046","tags":["report"]},{"url":"https://bugzilla.suse.com/1245078","tags":["report"]},{"url":"https://bugzilla.suse.com/1245081","tags":["report"]},{"url":"https://bugzilla.suse.com/1245082","tags":["report"]},{"url":"https://bugzilla.suse.com/1245083","tags":["report"]},{"url":"https://bugzilla.suse.com/1245101","tags":["report"]},{"url":"https://bugzilla.suse.com/1245155","tags":["report"]},{"url":"https://bugzilla.suse.com/1245183","tags":["report"]},{"url":"https://bugzilla.suse.com/1245193","tags":["report"]},{"url":"https://bugzilla.suse.com/1245210","tags":["report"]},{"url":"https://bugzilla.suse.com/1245217","tags":["report"]},{"url":"https://bugzilla.suse.com/1245225","tags":["report"]},{"url":"https://bugzilla.suse.com/1245226","tags":["report"]},{"url":"https://bugzilla.suse.com/1245228","tags":["report"]},{"url":"https://bugzilla.suse.com/1245431","tags":["report"]},{"url":"https://bugzilla.suse.com/1245455","tags":["report"]},{"url":"https://www.suse.com/security/cve/CVE-2023-52888","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-53146","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-26762","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-26831","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-41085","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-43869","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-49568","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-50034","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-50106","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-50293","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-56541","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-56613","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-56699","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-57982","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-57987","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-57988","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-57995","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-58004","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-58015","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-58053","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-58062","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-58077","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-58098","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-58099","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-58100","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-58237","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-21629","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-21658","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-21713","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-21720","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-21770","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-21805","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-21824","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-21842","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-21849","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-21868","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-21880","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-21898","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-21899","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-21901","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-21911","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-21920","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-21938","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-21939","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-21940","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-21959","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-21987","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-21997","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-22005","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-22023","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-22035","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-22066","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-22083","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-22089","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-22095","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-22111","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-22113","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-22119","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-22120","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-22124","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-23141","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-23142","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-23144","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-23146","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-23147","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-23148","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-23149","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-23151","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-23155","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-23156","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-23157","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-23158","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-23159","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-23161","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-23162","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-37738","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-37740","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-37741","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-37742","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-37743","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-37747","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-37752","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-37754","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-37756","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-37757","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-37758","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-37761","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-37763","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-37764","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-37765","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-37766","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-37767","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-37768","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-37769","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-37770","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-37771","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-37772","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-37781","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-37782","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-37786","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-37788","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-37791","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-37792","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-37793","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-37794","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-37796","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-37798","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-37800","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-37801","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-37805","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-37810","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-37811","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-37812","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-37813","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-37814","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-37815","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-37816","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-37819","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-37836","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-37837","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-37839","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-37840","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-37841","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-37844","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-37847","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-37848","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-37849","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-37850","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-37851","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-37852","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-37853","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-37854","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-37858","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-37859","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-37861","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-37862","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-37865","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-37867","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-37868","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-37869","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-37871","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-37873","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-37874","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-37875","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-37881","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-37884","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-37888","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-37889","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-37890","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-37891","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-37892","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-37897","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-37900","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-37901","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-37903","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-37905","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-37909","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-37911","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-37912","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-37913","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-37914","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-37915","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-37917","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-37918","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-37921","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-37923","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-37925","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-37927","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-37928","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-37929","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-37930","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-37931","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-37932","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-37933","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-37934","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-37936","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-37937","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-37938","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-37943","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-37944","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-37945","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-37946","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-37948","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-37951","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-37953","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-37954","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-37959","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-37961","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-37963","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-37965","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-37967","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-37968","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-37969","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-37970","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-37972","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-37973","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-37978","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-37979","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-37980","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-37981","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-37982","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-37983","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-37985","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-37986","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-37987","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-37989","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-37990","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-37992","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-37994","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-37995","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-37997","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-37998","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38000","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38001","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38003","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38004","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38005","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38007","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38009","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38010","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38011","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38013","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38014","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38015","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38018","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38020","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38022","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38023","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38024","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38027","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38031","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38040","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38043","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38044","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38045","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38053","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38055","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38057","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38059","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38060","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38065","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38068","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38072","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38077","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38078","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38079","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38080","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38081","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38083","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38104","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38240","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-39735","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-40014","tags":["web"]},{"url":"https://www.suse.com/support/update/announcement/2025/suse-su-202502307-1/","tags":["advisory"]},{"url":"https://bugzilla.suse.com/1012628","tags":["report"]},{"url":"https://www.suse.com/support/update/announcement/2025/suse-su-202502333-1/","tags":["advisory"]},{"url":"https://ubuntu.com/security/CVE-2024-41085","tags":["report"]},{"url":"https://git.kernel.org/linus/84ec985944ef34a34a1605b93ce401aa8737af96","tags":["report"]},{"url":"https://ubuntu.com/security/notices/USN-7089-1","tags":["advisory"]},{"url":"https://ubuntu.com/security/notices/USN-7090-1","tags":["advisory"]},{"url":"https://ubuntu.com/security/notices/USN-7089-2","tags":["advisory"]},{"url":"https://ubuntu.com/security/notices/USN-7089-3","tags":["advisory"]},{"url":"https://ubuntu.com/security/notices/USN-7095-1","tags":["advisory"]},{"url":"https://ubuntu.com/security/notices/USN-7089-4","tags":["advisory"]},{"url":"https://ubuntu.com/security/notices/USN-7089-5","tags":["advisory"]},{"url":"https://ubuntu.com/security/notices/USN-7089-6","tags":["advisory"]},{"url":"https://ubuntu.com/security/notices/USN-7089-7","tags":["advisory"]},{"url":"https://ubuntu.com/security/notices/USN-7156-1","tags":["advisory"]},{"url":"https://ubuntu.com/security/CVE-2023-52887","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2023-52888","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-25741","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-39486","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-39487","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-41007","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-41010","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-41012","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-41015","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-41017","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-41018","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-41019","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-41020","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-41021","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-41022","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-41023","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-41025","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-41027","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-41028","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-41029","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-41030","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-41031","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-41032","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-41033","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-41034","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-41035","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-41036","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-41037","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-41038","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-41039","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-41041","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-41042","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-41044","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-41045","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-41046","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-41047","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-41048","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-41049","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-41050","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-41051","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-41052","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-41053","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-41054","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-41055","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-41056","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-41057","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-41058","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-41059","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-41060","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-41061","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-41062","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-41063","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-41064","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-41065","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-41066","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-41067","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-41068","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-41069","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-41070","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-41071","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-41072","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-41073","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-41074","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-41075","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-41076","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-41077","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-41078","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-41079","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-41080","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-41081","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-41082","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-41083","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-41084","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-41086","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-41087","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-41088","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-41089","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-41090","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-41091","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-41092","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-41093","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-41094","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-41095","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-41096","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-41097","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-41098","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-42063","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-42064","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-42065","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-42066","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-42067","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-42068","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-42069","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-42070","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-42073","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-42074","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-42076","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-42077","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-42079","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-42080","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-42082","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-42084","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-42085","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-42086","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-42087","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-42088","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-42089","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-42090","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-42091","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-42092","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-42093","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-42094","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-42095","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-42096","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-42097","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-42098","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-42100","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-42101","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-42102","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-42103","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-42104","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-42105","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-42106","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-42108","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-42109","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-42110","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-42111","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-42112","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-42113","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-42114","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-42115","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-42117","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-42118","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-42119","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-42120","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-42121","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-42124","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-42126","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-42127","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-42128","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-42129","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-42130","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-42131","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-42132","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-42133","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-42135","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-42136","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-42137","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-42138","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-42140","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-42141","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-42142","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-42144","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-42145","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-42146","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-42147","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-42149","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-42150","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-42151","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-42152","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-42153","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-42155","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-42156","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-42157","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-42158","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-42161","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-42223","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-42225","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-42227","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-42229","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-42230","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-42231","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-42232","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-42234","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-42235","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-42236","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-42237","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-42238","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-42239","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-42240","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-42241","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-42243","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-42244","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-42245","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-42246","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-42247","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-42248","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-42250","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-42251","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-42252","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-42253","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-42271","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-42280","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-43855","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-43858","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-45001","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-45016","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2023-52889","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2023-52918","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-27022","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-39472","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-41009","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-42154","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-42159","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-42160","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-42224","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-42228","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-42258","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-42259","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-42260","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-42261","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-42262","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-42263","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-42264","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-42265","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-42267","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-42268","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-42269","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-42270","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-42272","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-42273","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-42274","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-42276","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-42277","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-42278","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-42279","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-42281","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-42283","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-42284","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-42285","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-42286","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-42287","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-42288","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-42289","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-42290","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-42291","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-42292","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-42294","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-42295","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-42296","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-42297","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-42298","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-42299","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-42301","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-42302","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-42303","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-42304","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-42305","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-42306","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-42307","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-42309","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-42310","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-42311","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-42312","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-42313","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-42314","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-42315","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-42316","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-42317","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-42318","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-42319","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-42320","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-42321","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-42322","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-43817","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-43818","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-43819","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-43820","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-43821","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-43823","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-43824","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-43825","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-43826","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-43827","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-43828","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-43829","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-43830","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-43831","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-43832","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-43833","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-43834","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-43835","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-43837","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-43839","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-43840","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-43841","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-43842","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-43843","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-43845","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-43846","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-43847","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-43849","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-43850","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-43852","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-43853","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-43854","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-43856","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-43857","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-43859","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-43860","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-43861","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-43863","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-43864","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-43866","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-43867","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-43868","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-43869","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-43870","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-43871","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-43873","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-43875","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-43876","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-43877","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-43879","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-43880","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-43881","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-43882","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-43883","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-43884","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-43886","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-43887","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-43888","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-43889","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-43890","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-43891","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-43892","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-43893","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-43894","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-43895","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-43899","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-43900","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-43902","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-43904","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-43905","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-43906","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-43907","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-43908","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-43909","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-43910","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-43911","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-43912","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-43913","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-43914","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-44931","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-44934","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-44935","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-44937","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-44938","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-44939","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-44940","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-44941","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-44942","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-44943","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-44944","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-44946","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-44947","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-44948","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-44950","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-44953","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-44954","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-44956","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-44957","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-44958","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-44959","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-44960","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-44961","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-44962","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-44963","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-44965","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-44966","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-44967","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-44969","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-44970","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-44971","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-44972","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-44973","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-44974","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-44975","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-44977","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-44978","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-44979","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-44980","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-44982","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-44983","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-44984","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-44985","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-44986","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-44987","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-44988","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-44989","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-44990","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-44991","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-44993","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-44995","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-44996","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-44998","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-44999","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-45000","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-45002","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-45003","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-45005","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-45006","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-45007","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-45008","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-45009","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-45010","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-45011","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-45012","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-45013","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-45015","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-45017","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-45018","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-45019","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-45020","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-45021","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-45022","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-45025","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-45026","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-45027","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-45028","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-45029","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-45030","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-46672","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-46673","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-46675","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-46676","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-46677","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-46678","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-46679","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-46680","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-46681","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-46683","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-46685","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-46686","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-46687","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-46689","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-46691","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-46692","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-46693","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-46694","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-46695","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-46697","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-46698","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-46701","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-46702","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-46703","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-46705","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-46706","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-46707","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-46708","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-46709","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-46710","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-46711","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-46713","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-46714","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-46715","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-46716","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-46717","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-46718","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-46719","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-46720","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-46721","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-46722","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-46723","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-46724","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-46725","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-46726","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-46727","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-46728","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-46729","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-46730","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-46731","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-46732","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-46733","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-46735","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-46737","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-46738","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-46739","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-46740","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-46741","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-46743","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-46744","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-46745","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-46746","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-46747","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-46749","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-46750","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-46751","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-46752","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-46753","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-46754","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-46755","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-46756","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-46757","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-46758","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-46759","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-46760","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-46761","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-46762","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-46763","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-46765","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-46766","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-46767","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-46768","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-46770","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-46771","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-46772","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-46773","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-46774","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-46775","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-46776","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-46777","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-46778","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-46779","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-46780","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-46781","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-46782","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-46783","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-46784","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-46785","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-46786","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-46787","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-46788","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-46791","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-46792","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-46793","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-46794","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-46795","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-46797","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-46798","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-46800","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-46802","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-46803","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-46804","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-46805","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-46806","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-46807","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-46808","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-46809","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-46810","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-46811","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-46812","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-46813","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-46814","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-46815","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-46816","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-46817","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-46818","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-46819","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-46821","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-46822","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-46823","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-46824","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-46825","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-46826","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-46827","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-46828","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-46829","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-46830","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-46831","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-46832","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-46834","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-46835","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-46836","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-46838","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-46840","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-46841","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-46842","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-46843","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-46844","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-46845","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-46846","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-46848","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-46849","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-46850","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-46851","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-46852","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-46853","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-46854","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-46855","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-46857","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-46858","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-46859","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-46860","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-46861","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-46864","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-46866","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-46867","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-46868","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-46870","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-46871","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-47658","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-47659","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-47660","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-47661","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-47662","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-47663","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-47664","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-47665","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-47666","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-47667","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-47668","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-47669","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-47674","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-47683","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-49984","tags":["report"]}],"sources":{"cve":[{"id":"CVE-2024-41085","title":"cxl/mem: Fix no cxl_nvd during pmem region auto-assembling","description":"In the Linux kernel, the following vulnerability has been resolved:\n\ncxl/mem: Fix no cxl_nvd during pmem region auto-assembling\n\nWhen CXL subsystem is auto-assembling a pmem region during cxl\nendpoint port probing, always hit below calltrace.\n\n BUG: kernel NULL pointer dereference, address: 0000000000000078\n #PF: supervisor read access in kernel mode\n #PF: error_code(0x0000) - not-present page\n RIP: 0010:cxl_pmem_region_probe+0x22e/0x360 [cxl_pmem]\n Call Trace:\n  \u003cTASK\u003e\n  ? __die+0x24/0x70\n  ? page_fault_oops+0x82/0x160\n  ? do_user_addr_fault+0x65/0x6b0\n  ? exc_page_fault+0x7d/0x170\n  ? asm_exc_page_fault+0x26/0x30\n  ? cxl_pmem_region_probe+0x22e/0x360 [cxl_pmem]\n  ? cxl_pmem_region_probe+0x1ac/0x360 [cxl_pmem]\n  cxl_bus_probe+0x1b/0x60 [cxl_core]\n  really_probe+0x173/0x410\n  ? __pfx___device_attach_driver+0x10/0x10\n  __driver_probe_device+0x80/0x170\n  driver_probe_device+0x1e/0x90\n  __device_attach_driver+0x90/0x120\n  bus_for_each_drv+0x84/0xe0\n  __device_attach+0xbc/0x1f0\n  bus_probe_device+0x90/0xa0\n  device_add+0x51c/0x710\n  devm_cxl_add_pmem_region+0x1b5/0x380 [cxl_core]\n  cxl_bus_probe+0x1b/0x60 [cxl_core]\n\nThe cxl_nvd of the memdev needs to be available during the pmem region\nprobe. Currently the cxl_nvd is registered after the endpoint port probe.\nThe endpoint probe, in the case of autoassembly of regions, can cause a\npmem region probe requiring the not yet available cxl_nvd. Adjust the\nsequence so this dependency is met.\n\nThis requires adding a port parameter to cxl_find_nvdimm_bridge() that\ncan be used to query the ancestor root port. The endpoint port is not\nyet available, but will share a common ancestor with its parent, so\nstart the query from there instead.","status":"published","published":"2024-07-29T15:48:01.267Z","modified":"2026-10-03T10:55:13.057Z","updated_at":"2026-11-02T14:34:04.00829Z"}],"euvd":[{"id":"EUVD-2024-38882","description":"In the Linux kernel, the following vulnerability has been resolved:\n\ncxl/mem: Fix no cxl_nvd during pmem region auto-assembling\n\nWhen CXL subsystem is auto-assembling a pmem region during cxl\nendpoint port probing, always hit below calltrace.\n\n BUG: kernel NULL pointer dereference, address: 0000000000000078\n #PF: supervisor read access in kernel mode\n #PF: error_code(0x0000) - not-present page\n RIP: 0010:cxl_pmem_region_probe+0x22e/0x360 [cxl_pmem]\n Call Trace:\n  \u003cTASK\u003e\n  ? __die+0x24/0x70\n  ? page_fault_oops+0x82/0x160\n  ? do_user_addr_fault+0x65/0x6b0\n  ? exc_page_fault+0x7d/0x170\n  ? asm_exc_page_fault+0x26/0x30\n  ? cxl_pmem_region_probe+0x22e/0x360 [cxl_pmem]\n  ? cxl_pmem_region_probe+0x1ac/0x360 [cxl_pmem]\n  cxl_bus_probe+0x1b/0x60 [cxl_core]\n  really_probe+0x173/0x410\n  ? __pfx___device_attach_driver+0x10/0x10\n  __driver_probe_device+0x80/0x170\n  driver_probe_device+0x1e/0x90\n  __device_attach_driver+0x90/0x120\n  bus_for_each_drv+0x84/0xe0\n  __device_attach+0xbc/0x1f0\n  bus_probe_device+0x90/0xa0\n  device_add+0x51c/0x710\n  devm_cxl_add_pmem_region+0x1b5/0x380 [cxl_core]\n  cxl_bus_probe+0x1b/0x60 [cxl_core]\n\nThe cxl_nvd of the memdev needs to be available during the pmem region\nprobe. Currently the cxl_nvd is registered after the endpoint port probe.\nThe endpoint probe, in the case of autoassembly of regions, can cause a\npmem region probe requiring the not yet available cxl_nvd. Adjust the\nsequence so this dependency is met.\n\nThis requires adding a port parameter to cxl_find_nvdimm_bridge() that\ncan be used to query the ancestor root port. The endpoint port is not\nyet available, but will share a common ancestor with its parent, so\nstart the query from there instead.","status":"published","published":"2024-07-29T15:48:01Z","modified":"2026-10-03T10:55:13Z","updated_at":"2026-11-02T17:27:41.962371Z"}],"ghsa":[{"id":"GHSA-2qvq-p8h3-vf5j","title":"In the Linux kernel, the following vulnerability has been resolved:\n\ncxl/mem: Fix no cxl_nvd...","description":"In the Linux kernel, the following vulnerability has been resolved:\n\ncxl/mem: Fix no cxl_nvd during pmem region auto-assembling\n\nWhen CXL subsystem is auto-assembling a pmem region during cxl\nendpoint port probing, always hit below calltrace.\n\n BUG: kernel NULL pointer dereference, address: 0000000000000078\n #PF: supervisor read access in kernel mode\n #PF: error_code(0x0000) - not-present page\n RIP: 0010:cxl_pmem_region_probe+0x22e/0x360 [cxl_pmem]\n Call Trace:\n  \u003cTASK\u003e\n  ? __die+0x24/0x70\n  ? page_fault_oops+0x82/0x160\n  ? do_user_addr_fault+0x65/0x6b0\n  ? exc_page_fault+0x7d/0x170\n  ? asm_exc_page_fault+0x26/0x30\n  ? cxl_pmem_region_probe+0x22e/0x360 [cxl_pmem]\n  ? cxl_pmem_region_probe+0x1ac/0x360 [cxl_pmem]\n  cxl_bus_probe+0x1b/0x60 [cxl_core]\n  really_probe+0x173/0x410\n  ? __pfx___device_attach_driver+0x10/0x10\n  __driver_probe_device+0x80/0x170\n  driver_probe_device+0x1e/0x90\n  __device_attach_driver+0x90/0x120\n  bus_for_each_drv+0x84/0xe0\n  __device_attach+0xbc/0x1f0\n  bus_probe_device+0x90/0xa0\n  device_add+0x51c/0x710\n  devm_cxl_add_pmem_region+0x1b5/0x380 [cxl_core]\n  cxl_bus_probe+0x1b/0x60 [cxl_core]\n\nThe cxl_nvd of the memdev needs to be available during the pmem region\nprobe. Currently the cxl_nvd is registered after the endpoint port probe.\nThe endpoint probe, in the case of autoassembly of regions, can cause a\npmem region probe requiring the not yet available cxl_nvd. Adjust the\nsequence so this dependency is met.\n\nThis requires adding a port parameter to cxl_find_nvdimm_bridge() that\ncan be used to query the ancestor root port. The endpoint port is not\nyet available, but will share a common ancestor with its parent, so\nstart the query from there instead.","status":"published","published":"2024-07-29T18:30:38Z","modified":"2026-10-03T12:31:01Z","cvss":[{"version":"3.1","score":5.5,"vector":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H","level":"medium"}],"cwes":["CWE-476"],"updated_at":"2026-11-02T15:12:44.85091Z"}],"nvd":[{"id":"CVE-2024-41085","description":"In the Linux kernel, the following vulnerability has been resolved:\n\ncxl/mem: Fix no cxl_nvd during pmem region auto-assembling\n\nWhen CXL subsystem is auto-assembling a pmem region during cxl\nendpoint port probing, always hit below calltrace.\n\n BUG: kernel NULL pointer dereference, address: 0000000000000078\n #PF: supervisor read access in kernel mode\n #PF: error_code(0x0000) - not-present page\n RIP: 0010:cxl_pmem_region_probe+0x22e/0x360 [cxl_pmem]\n Call Trace:\n  \u003cTASK\u003e\n  ? __die+0x24/0x70\n  ? page_fault_oops+0x82/0x160\n  ? do_user_addr_fault+0x65/0x6b0\n  ? exc_page_fault+0x7d/0x170\n  ? asm_exc_page_fault+0x26/0x30\n  ? cxl_pmem_region_probe+0x22e/0x360 [cxl_pmem]\n  ? cxl_pmem_region_probe+0x1ac/0x360 [cxl_pmem]\n  cxl_bus_probe+0x1b/0x60 [cxl_core]\n  really_probe+0x173/0x410\n  ? __pfx___device_attach_driver+0x10/0x10\n  __driver_probe_device+0x80/0x170\n  driver_probe_device+0x1e/0x90\n  __device_attach_driver+0x90/0x120\n  bus_for_each_drv+0x84/0xe0\n  __device_attach+0xbc/0x1f0\n  bus_probe_device+0x90/0xa0\n  device_add+0x51c/0x710\n  devm_cxl_add_pmem_region+0x1b5/0x380 [cxl_core]\n  cxl_bus_probe+0x1b/0x60 [cxl_core]\n\nThe cxl_nvd of the memdev needs to be available during the pmem region\nprobe. Currently the cxl_nvd is registered after the endpoint port probe.\nThe endpoint probe, in the case of autoassembly of regions, can cause a\npmem region probe requiring the not yet available cxl_nvd. Adjust the\nsequence so this dependency is met.\n\nThis requires adding a port parameter to cxl_find_nvdimm_bridge() that\ncan be used to query the ancestor root port. The endpoint port is not\nyet available, but will share a common ancestor with its parent, so\nstart the query from there instead.","status":"published","published":"2024-07-29T16:15:03.96Z","modified":"2026-10-03T11:17:30.73Z","cvss":[{"version":"3.1","score":5.5,"vector":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H","level":"medium","assessor":"primary"}],"cwes":["CWE-476"],"updated_at":"2026-11-02T14:10:14.437386Z"}],"osv":[{"id":"AZL-48057","title":"CVE-2024-41085 affecting package kernel 6.6.161.1-1","description":"In the Linux kernel, the following vulnerability has been resolved:\n\ncxl/mem: Fix no cxl_nvd during pmem region auto-assembling\n\nWhen CXL subsystem is auto-assembling a pmem region during cxl\nendpoint port probing, always hit below calltrace.\n\n BUG: kernel NULL pointer dereference, address: 0000000000000078\n #PF: supervisor read access in kernel mode\n #PF: error_code(0x0000) - not-present page\n RIP: 0010:cxl_pmem_region_probe+0x22e/0x360 [cxl_pmem]\n Call Trace:\n  \u003cTASK\u003e\n  ? __die+0x24/0x70\n  ? page_fault_oops+0x82/0x160\n  ? do_user_addr_fault+0x65/0x6b0\n  ? exc_page_fault+0x7d/0x170\n  ? asm_exc_page_fault+0x26/0x30\n  ? cxl_pmem_region_probe+0x22e/0x360 [cxl_pmem]\n  ? cxl_pmem_region_probe+0x1ac/0x360 [cxl_pmem]\n  cxl_bus_probe+0x1b/0x60 [cxl_core]\n  really_probe+0x173/0x410\n  ? __pfx___device_attach_driver+0x10/0x10\n  __driver_probe_device+0x80/0x170\n  driver_probe_device+0x1e/0x90\n  __device_attach_driver+0x90/0x120\n  bus_for_each_drv+0x84/0xe0\n  __device_attach+0xbc/0x1f0\n  bus_probe_device+0x90/0xa0\n  device_add+0x51c/0x710\n  devm_cxl_add_pmem_region+0x1b5/0x380 [cxl_core]\n  cxl_bus_probe+0x1b/0x60 [cxl_core]\n\nThe cxl_nvd of the memdev needs to be available during the pmem region\nprobe. Currently the cxl_nvd is registered after the endpoint port probe.\nThe endpoint probe, in the case of autoassembly of regions, can cause a\npmem region probe requiring the not yet available cxl_nvd. Adjust the\nsequence so this dependency is met.\n\nThis requires adding a port parameter to cxl_find_nvdimm_bridge() that\ncan be used to query the ancestor root port. The endpoint port is not\nyet available, but will share a common ancestor with its parent, so\nstart the query from there instead.","status":"published","published":"2024-07-29T16:15:03Z","modified":"2026-11-05T14:17:02.588376123Z","cvss":[{"version":"3.1","score":5.5,"vector":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H","level":"medium"}],"updated_at":"2026-11-05T16:41:20.321068Z"},{"id":"BELL-CVE-2024-41085","status":"published","published":"2024-07-31T05:58:51.719217Z","modified":"2026-01-26T09:37:54.307707Z","cvss":[{"version":"3.1","score":5.5,"vector":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H","level":"medium"}],"updated_at":"2026-11-02T15:28:20.200735Z"},{"id":"DEBIAN-CVE-2024-41085","description":"In the Linux kernel, the following vulnerability has been resolved:  cxl/mem: Fix no cxl_nvd during pmem region auto-assembling  When CXL subsystem is auto-assembling a pmem region during cxl endpoint port probing, always hit below calltrace.   BUG: kernel NULL pointer dereference, address: 0000000000000078  #PF: supervisor read access in kernel mode  #PF: error_code(0x0000) - not-present page  RIP: 0010:cxl_pmem_region_probe+0x22e/0x360 [cxl_pmem]  Call Trace:   \u003cTASK\u003e   ? __die+0x24/0x70   ? page_fault_oops+0x82/0x160   ? do_user_addr_fault+0x65/0x6b0   ? exc_page_fault+0x7d/0x170   ? asm_exc_page_fault+0x26/0x30   ? cxl_pmem_region_probe+0x22e/0x360 [cxl_pmem]   ? cxl_pmem_region_probe+0x1ac/0x360 [cxl_pmem]   cxl_bus_probe+0x1b/0x60 [cxl_core]   really_probe+0x173/0x410   ? __pfx___device_attach_driver+0x10/0x10   __driver_probe_device+0x80/0x170   driver_probe_device+0x1e/0x90   __device_attach_driver+0x90/0x120   bus_for_each_drv+0x84/0xe0   __device_attach+0xbc/0x1f0   bus_probe_device+0x90/0xa0   device_add+0x51c/0x710   devm_cxl_add_pmem_region+0x1b5/0x380 [cxl_core]   cxl_bus_probe+0x1b/0x60 [cxl_core]  The cxl_nvd of the memdev needs to be available during the pmem region probe. Currently the cxl_nvd is registered after the endpoint port probe. The endpoint probe, in the case of autoassembly of regions, can cause a pmem region probe requiring the not yet available cxl_nvd. Adjust the sequence so this dependency is met.  This requires adding a port parameter to cxl_find_nvdimm_bridge() that can be used to query the ancestor root port. The endpoint port is not yet available, but will share a common ancestor with its parent, so start the query from there instead.","status":"published","published":"2024-07-29T16:15:03.96Z","modified":"2026-11-02T12:02:58.789540469Z","cvss":[{"version":"3.1","score":5.5,"vector":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H","level":"medium"}],"updated_at":"2026-11-02T15:45:43.156294Z"},{"id":"OESA-2024-1960","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\nefi: libstub: only free priv.runtime_map when allocated\r\n\r\npriv.runtime_map is only allocated when efi_novamap is not set.\nOtherwise, it is an uninitialized value.  In the error path, it is freed\nunconditionally.  Avoid passing an uninitialized value to free_pool.\nFree priv.runtime_map only when it was allocated.\r\n\r\nThis bug was discovered and resolved using Coverity Static Analysis\nSecurity Testing (SAST) by Synopsys, Inc.(CVE-2024-33619)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nfpga: region: add owner module and take its refcount\r\n\r\nThe current implementation of the fpga region assumes that the low-level\nmodule registers a driver for the parent device and uses its owner pointer\nto take the module\u0026apos;s refcount. This approach is problematic since it can\nlead to a null pointer dereference while attempting to get the region\nduring programming if the parent device does not have a driver.\r\n\r\nTo address this problem, add a module owner pointer to the fpga_region\nstruct and use it to take the module\u0026apos;s refcount. Modify the functions for\nregistering a region to take an additional owner module parameter and\nrename them to avoid conflicts. Use the old function names for helper\nmacros that automatically set the module that registers the region as the\nowner. This ensures compatibility with existing low-level control modules\nand reduces the chances of registering a region without setting the owner.\r\n\r\nAlso, update the documentation to keep it consistent with the new interface\nfor registering an fpga region.(CVE-2024-35247)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\neeprom: at24: fix memory corruption race condition\r\n\r\nIf the eeprom is not accessible, an nvmem device will be registered, the\nread will fail, and the device will be torn down. If another driver\naccesses the nvmem device after the teardown, it will reference\ninvalid memory.\r\n\r\nMove the failure point before registering the nvmem device.(CVE-2024-35848)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nblock: fix module reference leakage from bdev_open_by_dev error path\r\n\r\nAt the time bdev_may_open() is called, module reference is grabbed\nalready, hence module reference should be released if bdev_may_open()\nfailed.\r\n\r\nThis problem is found by code review.(CVE-2024-35859)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nBluetooth: RFCOMM: Fix not validating setsockopt user input\r\n\r\nsyzbot reported rfcomm_sock_setsockopt_old() is copying data without\nchecking user input length.\r\n\r\nBUG: KASAN: slab-out-of-bounds in copy_from_sockptr_offset\ninclude/linux/sockptr.h:49 [inline]\nBUG: KASAN: slab-out-of-bounds in copy_from_sockptr\ninclude/linux/sockptr.h:55 [inline]\nBUG: KASAN: slab-out-of-bounds in rfcomm_sock_setsockopt_old\nnet/bluetooth/rfcomm/sock.c:632 [inline]\nBUG: KASAN: slab-out-of-bounds in rfcomm_sock_setsockopt+0x893/0xa70\nnet/bluetooth/rfcomm/sock.c:673\nRead of size 4 at addr ffff8880209a8bc3 by task syz-executor632/5064(CVE-2024-35966)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nmm/slab: make __free(kfree) accept error pointers\r\n\r\nCurrently, if an automatically freed allocation is an error pointer that\nwill lead to a crash.  An example of this is in wm831x_gpio_dbg_show().\r\n\r\n   171\tchar *label __free(kfree) = gpiochip_dup_line_label(chip, i);\n   172\tif (IS_ERR(label)) {\n   173\t\tdev_err(wm831x-\u0026gt;dev, \u0026quot;Failed to duplicate label\\n\u0026quot;);\n   174\t\tcontinue;\n   175  }\r\n\r\nThe auto clean up function should check for error pointers as well,\notherwise we\u0026apos;re going to keep hitting issues like this.(CVE-2024-36890)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nUSB: core: Fix access violation during port device removal\r\n\r\nTesting with KASAN and syzkaller revealed a bug in port.c:disable_store():\nusb_hub_to_struct_hub() can return NULL if the hub that the port belongs to\nis concurrently removed, but the function does not check for this\npossibility before dereferencing the returned value.\r\n\r\nIt turns out that the first dereference is unnecessary, since hub-\u0026gt;intfdev\nis the parent of the port device, so it can be changed easily.  Adding a\ncheck for hub == NULL prevents further problems.\r\n\r\nThe same bug exists in the disable_show() routine, and it can be fixed the\nsame way.(CVE-2024-36896)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\ngpiolib: cdev: Fix use after free in lineinfo_changed_notify\r\n\r\nThe use-after-free issue occurs as follows: when the GPIO chip device file\nis being closed by invoking gpio_chrdev_release(), watched_lines is freed\nby bitmap_free(), but the unregistration of lineinfo_changed_nb notifier\nchain failed due to waiting write rwsem. Additionally, one of the GPIO\nchip\u0026apos;s lines is also in the release process and holds the notifier chain\u0026apos;s\nread rwsem. Consequently, a race condition leads to the use-after-free of\nwatched_lines.\r\n\r\nHere is the typical stack when issue happened:\r\n\r\n[free]\ngpio_chrdev_release()\n  --\u0026gt; bitmap_free(cdev-\u0026gt;watched_lines)                  \u0026lt;-- freed\n  --\u0026gt; blocking_notifier_chain_unregister()\n    --\u0026gt; down_write(\u0026amp;nh-\u0026gt;rwsem)                          \u0026lt;-- waiting rwsem\n          --\u0026gt; __down_write_common()\n            --\u0026gt; rwsem_down_write_slowpath()\n                  --\u0026gt; schedule_preempt_disabled()\n                    --\u0026gt; schedule()\r\n\r\n[use]\nst54spi_gpio_dev_release()\n  --\u0026gt; gpio_free()\n    --\u0026gt; gpiod_free()\n      --\u0026gt; gpiod_free_commit()\n        --\u0026gt; gpiod_line_state_notify()\n          --\u0026gt; blocking_notifier_call_chain()\n            --\u0026gt; down_read(\u0026amp;nh-\u0026gt;rwsem);                  \u0026lt;-- held rwsem\n            --\u0026gt; notifier_call_chain()\n              --\u0026gt; lineinfo_changed_notify()\n                --\u0026gt; test_bit(xxxx, cdev-\u0026gt;watched_lines) \u0026lt;-- use after free\r\n\r\nThe side effect of the use-after-free issue is that a GPIO line event is\nbeing generated for userspace where it shouldn\u0026apos;t. However, since the chrdev\nis being closed, userspace won\u0026apos;t have the chance to read that event anyway.\r\n\r\nTo fix the issue, call the bitmap_free() function after the unregistration\nof lineinfo_changed_nb notifier chain.(CVE-2024-36899)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nipv6: prevent NULL dereference in ip6_output()\r\n\r\nAccording to syzbot, there is a chance that ip6_dst_idev()\nreturns NULL in ip6_output(). Most places in IPv6 stack\ndeal with a NULL idev just fine, but not here.\r\n\r\nsyzbot reported:\r\n\r\ngeneral protection fault, probably for non-canonical address 0xdffffc00000000bc: 0000 [#1] PREEMPT SMP KASAN PTI\nKASAN: null-ptr-deref in range [0x00000000000005e0-0x00000000000005e7]\nCPU: 0 PID: 9775 Comm: syz-executor.4 Not tainted 6.9.0-rc5-syzkaller-00157-g6a30653b604a #0\nHardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 03/27/2024\n RIP: 0010:ip6_output+0x231/0x3f0 net/ipv6/ip6_output.c:237\nCode: 3c 1e 00 49 89 df 74 08 4c 89 ef e8 19 58 db f7 48 8b 44 24 20 49 89 45 00 49 89 c5 48 8d 9d e0 05 00 00 48 89 d8 48 c1 e8 03 \u0026lt;42\u0026gt; 0f b6 04 38 84 c0 4c 8b 74 24 28 0f 85 61 01 00 00 8b 1b 31 ff\nRSP: 0018:ffffc9000927f0d8 EFLAGS: 00010202\nRAX: 00000000000000bc RBX: 00000000000005e0 RCX: 0000000000040000\nRDX: ffffc900131f9000 RSI: 0000000000004f47 RDI: 0000000000004f48\nRBP: 0000000000000000 R08: ffffffff8a1f0b9a R09: 1ffffffff1f51fad\nR10: dffffc0000000000 R11: fffffbfff1f51fae R12: ffff8880293ec8c0\nR13: ffff88805d7fc000 R14: 1ffff1100527d91a R15: dffffc0000000000\nFS:  00007f135c6856c0(0000) GS:ffff8880b9400000(0000) knlGS:0000000000000000\nCS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033\nCR2: 0000000020000080 CR3: 0000000064096000 CR4: 00000000003506f0\nDR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000\nDR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400\nCall Trace:\n \u0026lt;TASK\u0026gt;\n  NF_HOOK include/linux/netfilter.h:314 [inline]\n  ip6_xmit+0xefe/0x17f0 net/ipv6/ip6_output.c:358\n  sctp_v6_xmit+0x9f2/0x13f0 net/sctp/ipv6.c:248\n  sctp_packet_transmit+0x26ad/0x2ca0 net/sctp/output.c:653\n  sctp_packet_singleton+0x22c/0x320 net/sctp/outqueue.c:783\n  sctp_outq_flush_ctrl net/sctp/outqueue.c:914 [inline]\n  sctp_outq_flush+0x6d5/0x3e20 net/sctp/outqueue.c:1212\n  sctp_side_effects net/sctp/sm_sideeffect.c:1198 [inline]\n  sctp_do_sm+0x59cc/0x60c0 net/sctp/sm_sideeffect.c:1169\n  sctp_primitive_ASSOCIATE+0x95/0xc0 net/sctp/primitive.c:73\n  __sctp_connect+0x9cd/0xe30 net/sctp/socket.c:1234\n  sctp_connect net/sctp/socket.c:4819 [inline]\n  sctp_inet_connect+0x149/0x1f0 net/sctp/socket.c:4834\n  __sys_connect_file net/socket.c:2048 [inline]\n  __sys_connect+0x2df/0x310 net/socket.c:2065\n  __do_sys_connect net/socket.c:2075 [inline]\n  __se_sys_connect net/socket.c:2072 [inline]\n  __x64_sys_connect+0x7a/0x90 net/socket.c:2072\n  do_syscall_x64 arch/x86/entry/common.c:52 [inline]\n  do_syscall_64+0xf5/0x240 arch/x86/entry/common.c:83\n entry_SYSCALL_64_after_hwframe+0x77/0x7f(CVE-2024-36901)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nReapply \u0026quot;drm/qxl: simplify qxl_fence_wait\u0026quot;\r\n\r\nThis reverts commit 07ed11afb68d94eadd4ffc082b97c2331307c5ea.\r\n\r\nStephen Rostedt reports:\n \u0026quot;I went to run my tests on my VMs and the tests hung on boot up.\n  Unfortunately, the most I ever got out was:\r\n\r\n  [   93.607888] Testing event system initcall: OK\n  [   93.667730] Running tests on all trace events:\n  [   93.669757] Testing all events: OK\n  [   95.631064] ------------[ cut here ]------------\n  Timed out after 60 seconds\u0026quot;\r\n\r\nand further debugging points to a possible circular locking dependency\nbetween the console_owner locking and the worker pool locking.\r\n\r\nReverting the commit allows Steve\u0026apos;s VM to boot to completion again.\r\n\r\n[ This may obviously result in the \u0026quot;[TTM] Buffer eviction failed\u0026quot;\n  messages again, which was the reason for that original revert. But at\n  this point this seems preferable to a non-booting system... ](CVE-2024-36944)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nfs/9p: only translate RWX permissions for plain 9P2000\r\n\r\nGarbage in plain 9P2000\u0026apos;s perm bits is allowed through, which causes it\nto be able to set (among others) the suid bit. This was presumably not\nthe intent since the unix extended bits are handled explicitly and\nconditionally on .u.(CVE-2024-36964)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nnet/mlx5: Add a timeout to acquire the command queue semaphore\r\n\r\nPrevent forced completion handling on an entry that has not yet been\nassigned an index, causing an out of bounds access on idx = -22.\nInstead of waiting indefinitely for the sem, blocking flow now waits for\nindex to be allocated or a sem acquisition timeout before beginning the\ntimer for FW completion.\r\n\r\nKernel log example:\nmlx5_core 0000:06:00.0: wait_func_handle_exec_timeout:1128:(pid 185911): cmd[-22]: CREATE_UCTX(0xa04) No done completion(CVE-2024-38556)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nrcu: Fix buffer overflow in print_cpu_stall_info()\r\n\r\nThe rcuc-starvation output from print_cpu_stall_info() might overflow the\nbuffer if there is a huge difference in jiffies difference.  The situation\nmight seem improbable, but computers sometimes get very confused about\ntime, which can result in full-sized integers, and, in this case,\nbuffer overflow.\r\n\r\nAlso, the unsigned jiffies difference is printed using %ld, which is\nnormally for signed integers.  This is intentional for debugging purposes,\nbut it is not obvious from the code.\r\n\r\nThis commit therefore changes sprintf() to snprintf() and adds a\nclarifying comment about intention of %ld format.\r\n\r\nFound by Linux Verification Center (linuxtesting.org) with SVACE.(CVE-2024-38576)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nALSA: Fix deadlocks with kctl removals at disconnection\r\n\r\nIn snd_card_disconnect(), we set card-\u0026gt;shutdown flag at the beginning,\ncall callbacks and do sync for card-\u0026gt;power_ref_sleep waiters at the\nend.  The callback may delete a kctl element, and this can lead to a\ndeadlock when the device was in the suspended state.  Namely:\r\n\r\n* A process waits for the power up at snd_power_ref_and_wait() in\n  snd_ctl_info() or read/write() inside card-\u0026gt;controls_rwsem.\r\n\r\n* The system gets disconnected meanwhile, and the driver tries to\n  delete a kctl via snd_ctl_remove*(); it tries to take\n  card-\u0026gt;controls_rwsem again, but this is already locked by the\n  above.  Since the sleeper isn\u0026apos;t woken up, this deadlocks.\r\n\r\nAn easy fix is to wake up sleepers before processing the driver\ndisconnect callbacks but right after setting the card-\u0026gt;shutdown flag.\nThen all sleepers will abort immediately, and the code flows again.\r\n\r\nSo, basically this patch moves the wait_event() call at the right\ntiming.  While we\u0026apos;re at it, just to be sure, call wait_event_all()\ninstead of wait_event(), although we don\u0026apos;t use exclusive events on\nthis queue for now.(CVE-2024-38600)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\ncrypto: qat - validate slices count returned by FW\r\n\r\nThe function adf_send_admin_tl_start() enables the telemetry (TL)\nfeature on a QAT device by sending the ICP_QAT_FW_TL_START message to\nthe firmware. This triggers the FW to start writing TL data to a DMA\nbuffer in memory and returns an array containing the number of\naccelerators of each type (slices) supported by this HW.\nThe pointer to this array is stored in the adf_tl_hw_data data\nstructure called slice_cnt.\r\n\r\nThe array slice_cnt is then used in the function tl_print_dev_data()\nto report in debugfs only statistics about the supported accelerators.\nAn incorrect value of the elements in slice_cnt might lead to an out\nof bounds memory read.\nAt the moment, there isn\u0026apos;t an implementation of FW that returns a wrong\nvalue, but for robustness validate the slice count array returned by FW.(CVE-2024-38606)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nmacintosh/via-macii: Fix \u0026quot;BUG: sleeping function called from invalid context\u0026quot;\r\n\r\nThe via-macii ADB driver calls request_irq() after disabling hard\ninterrupts. But disabling interrupts isn\u0026apos;t necessary here because the\nVIA shift register interrupt was masked during VIA1 initialization.(CVE-2024-38607)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nkunit/fortify: Fix mismatched kvalloc()/vfree() usage\r\n\r\nThe kv*() family of tests were accidentally freeing with vfree() instead\nof kvfree(). Use kvfree() instead.(CVE-2024-38617)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\ndrm/amdgpu: add error handle to avoid out-of-bounds\r\n\r\nif the sdma_v4_0_irq_id_to_seq return -EINVAL, the process should\nbe stop to avoid out-of-bounds read, so directly return -EINVAL.(CVE-2024-39471)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nASoC: SOF: ipc4-topology: Fix input format query of process modules without base extension\r\n\r\nIf a process module does not have base config extension then the same\nformat applies to all of it\u0026apos;s inputs and the process-\u0026gt;base_config_ext is\nNULL, causing NULL dereference when specifically crafted topology and\nsequences used.(CVE-2024-39473)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nfbdev: savage: Handle err return when savagefb_check_var failed\r\n\r\nThe commit 04e5eac8f3ab(\u0026quot;fbdev: savage: Error out if pixclock equals zero\u0026quot;)\nchecks the value of pixclock to avoid divide-by-zero error. However\nthe function savagefb_probe doesn\u0026apos;t handle the error return of\nsavagefb_check_var. When pixclock is 0, it will cause divide-by-zero error.(CVE-2024-39475)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nmedia: mc: Fix graph walk in media_pipeline_start\r\n\r\nThe graph walk tries to follow all links, even if they are not between\npads. This causes a crash with, e.g. a MEDIA_LNK_FL_ANCILLARY_LINK link.\r\n\r\nFix this by allowing the walk to proceed only for MEDIA_LNK_FL_DATA_LINK\nlinks.(CVE-2024-39481)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\ndrm/drm_file: Fix pid refcounting race\r\n\r\n\u0026lt;maarten.lankhorst@linux.intel.com\u0026gt;, Maxime Ripard\n\u0026lt;mripard@kernel.org\u0026gt;, Thomas Zimmermann \u0026lt;tzimmermann@suse.de\u0026gt;\r\n\r\nfilp-\u0026gt;pid is supposed to be a refcounted pointer; however, before this\npatch, drm_file_update_pid() only increments the refcount of a struct\npid after storing a pointer to it in filp-\u0026gt;pid and dropping the\ndev-\u0026gt;filelist_mutex, making the following race possible:\r\n\r\nprocess A               process B\n=========               =========\n                        begin drm_file_update_pid\n                        mutex_lock(\u0026amp;dev-\u0026gt;filelist_mutex)\n                        rcu_replace_pointer(filp-\u0026gt;pid, \u0026lt;pid B\u0026gt;, 1)\n                        mutex_unlock(\u0026amp;dev-\u0026gt;filelist_mutex)\nbegin drm_file_update_pid\nmutex_lock(\u0026amp;dev-\u0026gt;filelist_mutex)\nrcu_replace_pointer(filp-\u0026gt;pid, \u0026lt;pid A\u0026gt;, 1)\nmutex_unlock(\u0026amp;dev-\u0026gt;filelist_mutex)\nget_pid(\u0026lt;pid A\u0026gt;)\nsynchronize_rcu()\nput_pid(\u0026lt;pid B\u0026gt;)   *** pid B reaches refcount 0 and is freed here ***\n                        get_pid(\u0026lt;pid B\u0026gt;)   *** UAF ***\n                        synchronize_rcu()\n                        put_pid(\u0026lt;pid A\u0026gt;)\r\n\r\nAs far as I know, this race can only occur with CONFIG_PREEMPT_RCU=y\nbecause it requires RCU to detect a quiescent state in code that is not\nexplicitly calling into the scheduler.\r\n\r\nThis race leads to use-after-free of a \u0026quot;struct pid\u0026quot;.\nIt is probably somewhat hard to hit because process A has to pass\nthrough a synchronize_rcu() operation while process B is between\nmutex_unlock() and get_pid().\r\n\r\nFix it by ensuring that by the time a pointer to the current task\u0026apos;s pid\nis stored in the file, an extra reference to the pid has been taken.\r\n\r\nThis fix also removes the condition for synchronize_rcu(); I think\nthat optimization is unnecessary complexity, since in that case we\nwould usually have bailed out on the lockless check above.(CVE-2024-39486)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\ncrypto: qat - Fix ADF_DEV_RESET_SYNC memory leak\r\n\r\nUsing completion_done to determine whether the caller has gone\naway only works after a complete call.  Furthermore it\u0026apos;s still\npossible that the caller has not yet called wait_for_completion,\nresulting in another potential UAF.\r\n\r\nFix this by making the caller use cancel_work_sync and then freeing\nthe memory safely.(CVE-2024-39493)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nbtrfs: zoned: fix use-after-free due to race with dev replace\r\n\r\nWhile loading a zone\u0026apos;s info during creation of a block group, we can race\nwith a device replace operation and then trigger a use-after-free on the\ndevice that was just replaced (source device of the replace operation).\r\n\r\nThis happens because at btrfs_load_zone_info() we extract a device from\nthe chunk map into a local variable and then use the device while not\nunder the protection of the device replace rwsem. So if there\u0026apos;s a device\nreplace operation happening when we extract the device and that device\nis the source of the replace operation, we will trigger a use-after-free\nif before we finish using the device the replace operation finishes and\nfrees the device.\r\n\r\nFix this by enlarging the critical section under the protection of the\ndevice replace rwsem so that all uses of the device are done inside the\ncritical section.(CVE-2024-39496)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nnetfilter: ipset: Fix race between namespace cleanup and gc in the list:set type\r\n\r\nLion Ackermann reported that there is a race condition between namespace cleanup\nin ipset and the garbage collection of the list:set type. The namespace\ncleanup can destroy the list:set type of sets while the gc of the set type is\nwaiting to run in rcu cleanup. The latter uses data from the destroyed set which\nthus leads use after free. The patch contains the following parts:\r\n\r\n- When destroying all sets, first remove the garbage collectors, then wait\n  if needed and then destroy the sets.\n- Fix the badly ordered \u0026quot;wait then remove gc\u0026quot; for the destroy a single set\n  case.\n- Fix the missing rcu locking in the list:set type in the userspace test\n  case.\n- Use proper RCU list handlings in the list:set type.\r\n\r\nThe patch depends on c1193d9bbbd3 (netfilter: ipset: Add list flush to cancel_gc).(CVE-2024-39503)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  cachefiles: remove requests from xarray during flushing requests  Even with CACHEFILES_DEAD set, we can still read the requests, so in the following concurrency the request may be used after it has been freed:       mount  |   daemon_thread1    |    daemon_thread2 ------------------------------------------------------------  cachefiles_ondemand_init_object   cachefiles_ondemand_send_req    REQ_A = kzalloc(sizeof(*req) + data_len)    wait_for_completion(\u0026amp;REQ_A-\u0026gt;done)             cachefiles_daemon_read              cachefiles_ondemand_daemon_read                                   // close dev fd                                   cachefiles_flush_reqs                                    complete(\u0026amp;REQ_A-\u0026gt;done)    kfree(REQ_A)               xa_lock(\u0026amp;cache-\u0026gt;reqs);               cachefiles_ondemand_select_req                 req-\u0026gt;msg.opcode != CACHEFILES_OP_READ                 // req use-after-free !!!               xa_unlock(\u0026amp;cache-\u0026gt;reqs);                                    xa_destroy(\u0026amp;cache-\u0026gt;reqs)  Hence remove requests from cache-\u0026gt;reqs when flushing them to avoid accessing freed requests.(CVE-2024-40900)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nnet/mlx5: Always stop health timer during driver removal\r\n\r\nCurrently, if teardown_hca fails to execute during driver removal, mlx5\ndoes not stop the health timer. Afterwards, mlx5 continue with driver\nteardown. This may lead to a UAF bug, which results in page fault\nOops[1], since the health timer invokes after resources were freed.\r\n\r\nHence, stop the health monitor even if teardown_hca fails.\r\n\r\n[1]\nmlx5_core 0000:18:00.0: E-Switch: Unload vfs: mode(LEGACY), nvfs(0), necvfs(0), active vports(0)\nmlx5_core 0000:18:00.0: E-Switch: Disable: mode(LEGACY), nvfs(0), necvfs(0), active vports(0)\nmlx5_core 0000:18:00.0: E-Switch: Disable: mode(LEGACY), nvfs(0), necvfs(0), active vports(0)\nmlx5_core 0000:18:00.0: E-Switch: cleanup\nmlx5_core 0000:18:00.0: wait_func:1155:(pid 1967079): TEARDOWN_HCA(0x103) timeout. Will cause a leak of a command resource\nmlx5_core 0000:18:00.0: mlx5_function_close:1288:(pid 1967079): tear_down_hca failed, skip cleanup\nBUG: unable to handle page fault for address: ffffa26487064230\nPGD 100c00067 P4D 100c00067 PUD 100e5a067 PMD 105ed7067 PTE 0\nOops: 0000 [#1] PREEMPT SMP PTI\nCPU: 0 PID: 0 Comm: swapper/0 Tainted: G           OE     -------  ---  6.7.0-68.fc38.x86_64 #1\nHardware name: Intel Corporation S2600WFT/S2600WFT, BIOS SE5C620.86B.02.01.0013.121520200651 12/15/2020\nRIP: 0010:ioread32be+0x34/0x60\nRSP: 0018:ffffa26480003e58 EFLAGS: 00010292\nRAX: ffffa26487064200 RBX: ffff9042d08161a0 RCX: ffff904c108222c0\nRDX: 000000010bbf1b80 RSI: ffffffffc055ddb0 RDI: ffffa26487064230\nRBP: ffff9042d08161a0 R08: 0000000000000022 R09: ffff904c108222e8\nR10: 0000000000000004 R11: 0000000000000441 R12: ffffffffc055ddb0\nR13: ffffa26487064200 R14: ffffa26480003f00 R15: ffff904c108222c0\nFS:  0000000000000000(0000) GS:ffff904c10800000(0000) knlGS:0000000000000000\nCS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033\nCR2: ffffa26487064230 CR3: 00000002c4420006 CR4: 00000000007706f0\nDR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000\nDR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400\nPKRU: 55555554\nCall Trace:\n \u0026lt;IRQ\u0026gt;\n ? __die+0x23/0x70\n ? page_fault_oops+0x171/0x4e0\n ? exc_page_fault+0x175/0x180\n ? asm_exc_page_fault+0x26/0x30\n ? __pfx_poll_health+0x10/0x10 [mlx5_core]\n ? __pfx_poll_health+0x10/0x10 [mlx5_core]\n ? ioread32be+0x34/0x60\n mlx5_health_check_fatal_sensors+0x20/0x100 [mlx5_core]\n ? __pfx_poll_health+0x10/0x10 [mlx5_core]\n poll_health+0x42/0x230 [mlx5_core]\n ? __next_timer_interrupt+0xbc/0x110\n ? __pfx_poll_health+0x10/0x10 [mlx5_core]\n call_timer_fn+0x21/0x130\n ? __pfx_poll_health+0x10/0x10 [mlx5_core]\n __run_timers+0x222/0x2c0\n run_timer_softirq+0x1d/0x40\n __do_softirq+0xc9/0x2c8\n __irq_exit_rcu+0xa6/0xc0\n sysvec_apic_timer_interrupt+0x72/0x90\n \u0026lt;/IRQ\u0026gt;\n \u0026lt;TASK\u0026gt;\n asm_sysvec_apic_timer_interrupt+0x1a/0x20\nRIP: 0010:cpuidle_enter_state+0xcc/0x440\n ? cpuidle_enter_state+0xbd/0x440\n cpuidle_enter+0x2d/0x40\n do_idle+0x20d/0x270\n cpu_startup_entry+0x2a/0x30\n rest_init+0xd0/0xd0\n arch_call_rest_init+0xe/0x30\n start_kernel+0x709/0xa90\n x86_64_start_reservations+0x18/0x30\n x86_64_start_kernel+0x96/0xa0\n secondary_startup_64_no_verify+0x18f/0x19b\n---[ end trace 0000000000000000 ]---(CVE-2024-40906)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nbpf: Set run context for rawtp test_run callback\r\n\r\nsyzbot reported crash when rawtp program executed through the\ntest_run interface calls bpf_get_attach_cookie helper or any\nother helper that touches task-\u0026gt;bpf_ctx pointer.\r\n\r\nSetting the run context (task-\u0026gt;bpf_ctx pointer) for test_run\ncallback.(CVE-2024-40908)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\ncachefiles: defer exposing anon_fd until after copy_to_user() succeeds\r\n\r\nAfter installing the anonymous fd, we can now see it in userland and close\nit. However, at this point we may not have gotten the reference count of\nthe cache, but we will put it during colse fd, so this may cause a cache\nUAF.\r\n\r\nSo grab the cache reference count before fd_install(). In addition, by\nkernel convention, fd is taken over by the user land after fd_install(),\nand the kernel should not call close_fd() after that, i.e., it should call\nfd_install() after everything is ready, thus fd_install() is called after\ncopy_to_user() succeeds.(CVE-2024-40913)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nnet: bridge: mst: fix suspicious rcu usage in br_mst_set_state\r\n\r\nI converted br_mst_set_state to RCU to avoid a vlan use-after-free\nbut forgot to change the vlan group dereference helper. Switch to vlan\ngroup RCU deref helper to fix the suspicious rcu usage warning.(CVE-2024-40920)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nnet: bridge: mst: pass vlan group directly to br_mst_vlan_set_state\r\n\r\nPass the already obtained vlan group pointer to br_mst_vlan_set_state()\ninstead of dereferencing it again. Each caller has already correctly\ndereferenced it for their context. This change is required for the\nfollowing suspicious RCU dereference fix. No functional changes\nintended.(CVE-2024-40921)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nio_uring/rsrc: don\u0026apos;t lock while !TASK_RUNNING\r\n\r\nThere is a report of io_rsrc_ref_quiesce() locking a mutex while not\nTASK_RUNNING, which is due to forgetting restoring the state back after\nio_run_task_work_sig() and attempts to break out of the waiting loop.\r\n\r\ndo not call blocking ops when !TASK_RUNNING; state=1 set at\n[\u0026lt;ffffffff815d2494\u0026gt;] prepare_to_wait+0xa4/0x380\nkernel/sched/wait.c:237\nWARNING: CPU: 2 PID: 397056 at kernel/sched/core.c:10099\n__might_sleep+0x114/0x160 kernel/sched/core.c:10099\nRIP: 0010:__might_sleep+0x114/0x160 kernel/sched/core.c:10099\nCall Trace:\n \u0026lt;TASK\u0026gt;\n __mutex_lock_common kernel/locking/mutex.c:585 [inline]\n __mutex_lock+0xb4/0x940 kernel/locking/mutex.c:752\n io_rsrc_ref_quiesce+0x590/0x940 io_uring/rsrc.c:253\n io_sqe_buffers_unregister+0xa2/0x340 io_uring/rsrc.c:799\n __io_uring_register io_uring/register.c:424 [inline]\n __do_sys_io_uring_register+0x5b9/0x2400 io_uring/register.c:613\n do_syscall_x64 arch/x86/entry/common.c:52 [inline]\n do_syscall_64+0xd8/0x270 arch/x86/entry/common.c:83\n entry_SYSCALL_64_after_hwframe+0x6f/0x77(CVE-2024-40922)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\ncachefiles: flush all requests after setting CACHEFILES_DEAD\r\n\r\nIn ondemand mode, when the daemon is processing an open request, if the\nkernel flags the cache as CACHEFILES_DEAD, the cachefiles_daemon_write()\nwill always return -EIO, so the daemon can\u0026apos;t pass the copen to the kernel.\nThen the kernel process that is waiting for the copen triggers a hung_task.\r\n\r\nSince the DEAD state is irreversible, it can only be exited by closing\n/dev/cachefiles. Therefore, after calling cachefiles_io_error() to mark\nthe cache as CACHEFILES_DEAD, if in ondemand mode, flush all requests to\navoid the above hungtask. We may still be able to read some of the cached\ndata before closing the fd of /dev/cachefiles.\r\n\r\nNote that this relies on the patch that adds reference counting to the req,\notherwise it may UAF.(CVE-2024-40935)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nKVM: Fix a data race on last_boosted_vcpu in kvm_vcpu_on_spin()\r\n\r\nUse {READ,WRITE}_ONCE() to access kvm-\u0026gt;last_boosted_vcpu to ensure the\nloads and stores are atomic.  In the extremely unlikely scenario the\ncompiler tears the stores, it\u0026apos;s theoretically possible for KVM to attempt\nto get a vCPU using an out-of-bounds index, e.g. if the write is split\ninto multiple 8-bit stores, and is paired with a 32-bit load on a VM with\n257 vCPUs:\r\n\r\n  CPU0                              CPU1\n  last_boosted_vcpu = 0xff;\r\n\r\n                                    (last_boosted_vcpu = 0x100)\n                                    last_boosted_vcpu[15:8] = 0x01;\n  i = (last_boosted_vcpu = 0x1ff)\n                                    last_boosted_vcpu[7:0] = 0x00;\r\n\r\n  vcpu = kvm-\u0026gt;vcpu_array[0x1ff];\r\n\r\nAs detected by KCSAN:\r\n\r\n  BUG: KCSAN: data-race in kvm_vcpu_on_spin [kvm] / kvm_vcpu_on_spin [kvm]\r\n\r\n  write to 0xffffc90025a92344 of 4 bytes by task 4340 on cpu 16:\n  kvm_vcpu_on_spin (arch/x86/kvm/../../../virt/kvm/kvm_main.c:4112) kvm\n  handle_pause (arch/x86/kvm/vmx/vmx.c:5929) kvm_intel\n  vmx_handle_exit (arch/x86/kvm/vmx/vmx.c:?\n\t\t arch/x86/kvm/vmx/vmx.c:6606) kvm_intel\n  vcpu_run (arch/x86/kvm/x86.c:11107 arch/x86/kvm/x86.c:11211) kvm\n  kvm_arch_vcpu_ioctl_run (arch/x86/kvm/x86.c:?) kvm\n  kvm_vcpu_ioctl (arch/x86/kvm/../../../virt/kvm/kvm_main.c:?) kvm\n  __se_sys_ioctl (fs/ioctl.c:52 fs/ioctl.c:904 fs/ioctl.c:890)\n  __x64_sys_ioctl (fs/ioctl.c:890)\n  x64_sys_call (arch/x86/entry/syscall_64.c:33)\n  do_syscall_64 (arch/x86/entry/common.c:?)\n  entry_SYSCALL_64_after_hwframe (arch/x86/entry/entry_64.S:130)\r\n\r\n  read to 0xffffc90025a92344 of 4 bytes by task 4342 on cpu 4:\n  kvm_vcpu_on_spin (arch/x86/kvm/../../../virt/kvm/kvm_main.c:4069) kvm\n  handle_pause (arch/x86/kvm/vmx/vmx.c:5929) kvm_intel\n  vmx_handle_exit (arch/x86/kvm/vmx/vmx.c:?\n\t\t\tarch/x86/kvm/vmx/vmx.c:6606) kvm_intel\n  vcpu_run (arch/x86/kvm/x86.c:11107 arch/x86/kvm/x86.c:11211) kvm\n  kvm_arch_vcpu_ioctl_run (arch/x86/kvm/x86.c:?) kvm\n  kvm_vcpu_ioctl (arch/x86/kvm/../../../virt/kvm/kvm_main.c:?) kvm\n  __se_sys_ioctl (fs/ioctl.c:52 fs/ioctl.c:904 fs/ioctl.c:890)\n  __x64_sys_ioctl (fs/ioctl.c:890)\n  x64_sys_call (arch/x86/entry/syscall_64.c:33)\n  do_syscall_64 (arch/x86/entry/common.c:?)\n  entry_SYSCALL_64_after_hwframe (arch/x86/entry/entry_64.S:130)\r\n\r\n  value changed: 0x00000012 -\u0026gt; 0x00000000(CVE-2024-40953)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nbtrfs: zoned: allocate dummy checksums for zoned NODATASUM writes\r\n\r\nShin\u0026apos;ichiro reported that when he\u0026apos;s running fstests\u0026apos; test-case\nbtrfs/167 on emulated zoned devices, he\u0026apos;s seeing the following NULL\npointer dereference in \u0026apos;btrfs_zone_finish_endio()\u0026apos;:\r\n\r\n  Oops: general protection fault, probably for non-canonical address 0xdffffc0000000011: 0000 [#1] PREEMPT SMP KASAN NOPTI\n  KASAN: null-ptr-deref in range [0x0000000000000088-0x000000000000008f]\n  CPU: 4 PID: 2332440 Comm: kworker/u80:15 Tainted: G        W          6.10.0-rc2-kts+ #4\n  Hardware name: Supermicro Super Server/X11SPi-TF, BIOS 3.3 02/21/2020\n  Workqueue: btrfs-endio-write btrfs_work_helper [btrfs]\n  RIP: 0010:btrfs_zone_finish_endio.part.0+0x34/0x160 [btrfs]\r\n\r\n  RSP: 0018:ffff88867f107a90 EFLAGS: 00010206\n  RAX: dffffc0000000000 RBX: 0000000000000000 RCX: ffffffff893e5534\n  RDX: 0000000000000011 RSI: 0000000000000004 RDI: 0000000000000088\n  RBP: 0000000000000002 R08: 0000000000000001 R09: ffffed1081696028\n  R10: ffff88840b4b0143 R11: ffff88834dfff600 R12: ffff88840b4b0000\n  R13: 0000000000020000 R14: 0000000000000000 R15: ffff888530ad5210\n  FS:  0000000000000000(0000) GS:ffff888e3f800000(0000) knlGS:0000000000000000\n  CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033\n  CR2: 00007f87223fff38 CR3: 00000007a7c6a002 CR4: 00000000007706f0\n  DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000\n  DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400\n  PKRU: 55555554\n  Call Trace:\n   \u0026lt;TASK\u0026gt;\n   ? __die_body.cold+0x19/0x27\n   ? die_addr+0x46/0x70\n   ? exc_general_protection+0x14f/0x250\n   ? asm_exc_general_protection+0x26/0x30\n   ? do_raw_read_unlock+0x44/0x70\n   ? btrfs_zone_finish_endio.part.0+0x34/0x160 [btrfs]\n   btrfs_finish_one_ordered+0x5d9/0x19a0 [btrfs]\n   ? __pfx_lock_release+0x10/0x10\n   ? do_raw_write_lock+0x90/0x260\n   ? __pfx_do_raw_write_lock+0x10/0x10\n   ? __pfx_btrfs_finish_one_ordered+0x10/0x10 [btrfs]\n   ? _raw_write_unlock+0x23/0x40\n   ? btrfs_finish_ordered_zoned+0x5a9/0x850 [btrfs]\n   ? lock_acquire+0x435/0x500\n   btrfs_work_helper+0x1b1/0xa70 [btrfs]\n   ? __schedule+0x10a8/0x60b0\n   ? __pfx___might_resched+0x10/0x10\n   process_one_work+0x862/0x1410\n   ? __pfx_lock_acquire+0x10/0x10\n   ? __pfx_process_one_work+0x10/0x10\n   ? assign_work+0x16c/0x240\n   worker_thread+0x5e6/0x1010\n   ? __pfx_worker_thread+0x10/0x10\n   kthread+0x2c3/0x3a0\n   ? trace_irq_enable.constprop.0+0xce/0x110\n   ? __pfx_kthread+0x10/0x10\n   ret_from_fork+0x31/0x70\n   ? __pfx_kthread+0x10/0x10\n   ret_from_fork_asm+0x1a/0x30\n   \u0026lt;/TASK\u0026gt;\r\n\r\nEnabling CONFIG_BTRFS_ASSERT revealed the following assertion to\ntrigger:\r\n\r\n  assertion failed: !list_empty(\u0026amp;ordered-\u0026gt;list), in fs/btrfs/zoned.c:1815\r\n\r\nThis indicates, that we\u0026apos;re missing the checksums list on the\nordered_extent. As btrfs/167 is doing a NOCOW write this is to be\nexpected.\r\n\r\nFurther analysis with drgn confirmed the assumption:\r\n\r\n  \u0026gt;\u0026gt;\u0026gt; inode = prog.crashed_thread().stack_trace()[11][\u0026apos;ordered\u0026apos;].inode\n  \u0026gt;\u0026gt;\u0026gt; btrfs_inode = drgn.container_of(inode, \u0026quot;struct btrfs_inode\u0026quot;, \\\n         \t\t\t\t\u0026quot;vfs_inode\u0026quot;)\n  \u0026gt;\u0026gt;\u0026gt; print(btrfs_inode.flags)\n  (u32)1\r\n\r\nAs zoned emulation mode simulates conventional zones on regular devices,\nwe cannot use zone-append for writing. But we\u0026apos;re only attaching dummy\nchecksums if we\u0026apos;re doing a zone-append write.\r\n\r\nSo for NOCOW zoned data writes on conventional zones, also attach a\ndummy checksum.(CVE-2024-40962)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nserial: imx: Introduce timeout when waiting on transmitter empty\r\n\r\nBy waiting at most 1 second for USR2_TXDC to be set, we avoid a potential\ndeadlock.\r\n\r\nIn case of the timeout, there is not much we can do, so we simply ignore\nthe transmitter state and optimistically try to continue.(CVE-2024-40967)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nbatman-adv: bypass empty buckets in batadv_purge_orig_ref()\r\n\r\nMany syzbot reports are pointing to soft lockups in\nbatadv_purge_orig_ref() [1]\r\n\r\nRoot cause is unknown, but we can avoid spending too much\ntime there and perhaps get more interesting reports.\r\n\r\n[1]\r\n\r\nwatchdog: BUG: soft lockup - CPU#0 stuck for 27s! [kworker/u4:6:621]\nModules linked in:\nirq event stamp: 6182794\n hardirqs last  enabled at (6182793): [\u0026lt;ffff8000801dae10\u0026gt;] __local_bh_enable_ip+0x224/0x44c kernel/softirq.c:386\n hardirqs last disabled at (6182794): [\u0026lt;ffff80008ad66a78\u0026gt;] __el1_irq arch/arm64/kernel/entry-common.c:533 [inline]\n hardirqs last disabled at (6182794): [\u0026lt;ffff80008ad66a78\u0026gt;] el1_interrupt+0x24/0x68 arch/arm64/kernel/entry-common.c:551\n softirqs last  enabled at (6182792): [\u0026lt;ffff80008aab71c4\u0026gt;] spin_unlock_bh include/linux/spinlock.h:396 [inline]\n softirqs last  enabled at (6182792): [\u0026lt;ffff80008aab71c4\u0026gt;] batadv_purge_orig_ref+0x114c/0x1228 net/batman-adv/originator.c:1287\n softirqs last disabled at (6182790): [\u0026lt;ffff80008aab61dc\u0026gt;] spin_lock_bh include/linux/spinlock.h:356 [inline]\n softirqs last disabled at (6182790): [\u0026lt;ffff80008aab61dc\u0026gt;] batadv_purge_orig_ref+0x164/0x1228 net/batman-adv/originator.c:1271\nCPU: 0 PID: 621 Comm: kworker/u4:6 Not tainted 6.8.0-rc7-syzkaller-g707081b61156 #0\nHardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 02/29/2024\nWorkqueue: bat_events batadv_purge_orig\npstate: 80400005 (Nzcv daif +PAN -UAO -TCO -DIT -SSBS BTYPE=--)\n pc : should_resched arch/arm64/include/asm/preempt.h:79 [inline]\n pc : __local_bh_enable_ip+0x228/0x44c kernel/softirq.c:388\n lr : __local_bh_enable_ip+0x224/0x44c kernel/softirq.c:386\nsp : ffff800099007970\nx29: ffff800099007980 x28: 1fffe00018fce1bd x27: dfff800000000000\nx26: ffff0000d2620008 x25: ffff0000c7e70de8 x24: 0000000000000001\nx23: 1fffe00018e57781 x22: dfff800000000000 x21: ffff80008aab71c4\nx20: ffff0001b40136c0 x19: ffff0000c72bbc08 x18: 1fffe0001a817bb0\nx17: ffff800125414000 x16: ffff80008032116c x15: 0000000000000001\nx14: 1fffe0001ee9d610 x13: 0000000000000000 x12: 0000000000000003\nx11: 0000000000000000 x10: 0000000000ff0100 x9 : 0000000000000000\nx8 : 00000000005e5789 x7 : ffff80008aab61dc x6 : 0000000000000000\nx5 : 0000000000000000 x4 : 0000000000000001 x3 : 0000000000000000\nx2 : 0000000000000006 x1 : 0000000000000080 x0 : ffff800125414000\nCall trace:\n  __daif_local_irq_enable arch/arm64/include/asm/irqflags.h:27 [inline]\n  arch_local_irq_enable arch/arm64/include/asm/irqflags.h:49 [inline]\n  __local_bh_enable_ip+0x228/0x44c kernel/softirq.c:386\n  __raw_spin_unlock_bh include/linux/spinlock_api_smp.h:167 [inline]\n  _raw_spin_unlock_bh+0x3c/0x4c kernel/locking/spinlock.c:210\n  spin_unlock_bh include/linux/spinlock.h:396 [inline]\n  batadv_purge_orig_ref+0x114c/0x1228 net/batman-adv/originator.c:1287\n  batadv_purge_orig+0x20/0x70 net/batman-adv/originator.c:1300\n  process_one_work+0x694/0x1204 kernel/workqueue.c:2633\n  process_scheduled_works kernel/workqueue.c:2706 [inline]\n  worker_thread+0x938/0xef4 kernel/workqueue.c:2787\n  kthread+0x288/0x310 kernel/kthread.c:388\n  ret_from_fork+0x10/0x20 arch/arm64/kernel/entry.S:860\nSending NMI from CPU 0 to CPUs 1:\nNMI backtrace for cpu 1\nCPU: 1 PID: 0 Comm: swapper/1 Not tainted 6.8.0-rc7-syzkaller-g707081b61156 #0\nHardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 02/29/2024\npstate: 80400005 (Nzcv daif +PAN -UAO -TCO -DIT -SSBS BTYPE=--)\n pc : arch_local_irq_enable+0x8/0xc arch/arm64/include/asm/irqflags.h:51\n lr : default_idle_call+0xf8/0x128 kernel/sched/idle.c:103\nsp : ffff800093a17d30\nx29: ffff800093a17d30 x28: dfff800000000000 x27: 1ffff00012742fb4\nx26: ffff80008ec9d000 x25: 0000000000000000 x24: 0000000000000002\nx23: 1ffff00011d93a74 x22: ffff80008ec9d3a0 x21: 0000000000000000\nx20: ffff0000c19dbc00 x19: ffff8000802d0fd8 x18: 1fffe00036804396\nx17: ffff80008ec9d000 x16: ffff8000802d089c x15: 0000000000000001\n---truncated---(CVE-2024-40981)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nnetrom: Fix a memory leak in nr_heartbeat_expiry()\r\n\r\nsyzbot reported a memory leak in nr_create() [0].\r\n\r\nCommit 409db27e3a2e (\u0026quot;netrom: Fix use-after-free of a listening socket.\u0026quot;)\nadded sock_hold() to the nr_heartbeat_expiry() function, where\na) a socket has a SOCK_DESTROY flag or\nb) a listening socket has a SOCK_DEAD flag.\r\n\r\nBut in the case \u0026quot;a,\u0026quot; when the SOCK_DESTROY flag is set, the file descriptor\nhas already been closed and the nr_release() function has been called.\nSo it makes no sense to hold the reference count because no one will\ncall another nr_destroy_socket() and put it as in the case \u0026quot;b.\u0026quot;\r\n\r\nnr_connect\n  nr_establish_data_link\n    nr_start_heartbeat\r\n\r\nnr_release\n  switch (nr-\u0026gt;state)\n  case NR_STATE_3\n    nr-\u0026gt;state = NR_STATE_2\n    sock_set_flag(sk, SOCK_DESTROY);\r\n\r\n                        nr_rx_frame\n                          nr_process_rx_frame\n                            switch (nr-\u0026gt;state)\n                            case NR_STATE_2\n                              nr_state2_machine()\n                                nr_disconnect()\n                                  nr_sk(sk)-\u0026gt;state = NR_STATE_0\n                                  sock_set_flag(sk, SOCK_DEAD)\r\n\r\n                        nr_heartbeat_expiry\n                          switch (nr-\u0026gt;state)\n                          case NR_STATE_0\n                            if (sock_flag(sk, SOCK_DESTROY) ||\n                               (sk-\u0026gt;sk_state == TCP_LISTEN\n                                 \u0026amp;\u0026amp; sock_flag(sk, SOCK_DEAD)))\n                               sock_hold()  // ( !!! )\n                               nr_destroy_socket()\r\n\r\nTo fix the memory leak, let\u0026apos;s call sock_hold() only for a listening socket.\r\n\r\nFound by InfoTeCS on behalf of Linux Verification Center\n(linuxtesting.org) with Syzkaller.\r\n\r\n[0]: https://syzkaller.appspot.com/bug?extid=d327a1f3b12e1e206c16(CVE-2024-41006)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nbpf: Fix too early release of tcx_entry\r\n\r\nPedro Pinto and later independently also Hyunwoo Kim and Wongi Lee reported\nan issue that the tcx_entry can be released too early leading to a use\nafter free (UAF) when an active old-style ingress or clsact qdisc with a\nshared tc block is later replaced by another ingress or clsact instance.\r\n\r\nEssentially, the sequence to trigger the UAF (one example) can be as follows:\r\n\r\n  1. A network namespace is created\n  2. An ingress qdisc is created. This allocates a tcx_entry, and\n     \u0026amp;tcx_entry-\u0026gt;miniq is stored in the qdisc\u0026apos;s miniqp-\u0026gt;p_miniq. At the\n     same time, a tcf block with index 1 is created.\n  3. chain0 is attached to the tcf block. chain0 must be connected to\n     the block linked to the ingress qdisc to later reach the function\n     tcf_chain0_head_change_cb_del() which triggers the UAF.\n  4. Create and graft a clsact qdisc. This causes the ingress qdisc\n     created in step 1 to be removed, thus freeing the previously linked\n     tcx_entry:\r\n\r\n     rtnetlink_rcv_msg()\n       =\u0026gt; tc_modify_qdisc()\n         =\u0026gt; qdisc_create()\n           =\u0026gt; clsact_init() [a]\n         =\u0026gt; qdisc_graft()\n           =\u0026gt; qdisc_destroy()\n             =\u0026gt; __qdisc_destroy()\n               =\u0026gt; ingress_destroy() [b]\n                 =\u0026gt; tcx_entry_free()\n                   =\u0026gt; kfree_rcu() // tcx_entry freed\r\n\r\n  5. Finally, the network namespace is closed. This registers the\n     cleanup_net worker, and during the process of releasing the\n     remaining clsact qdisc, it accesses the tcx_entry that was\n     already freed in step 4, causing the UAF to occur:\r\n\r\n     cleanup_net()\n       =\u0026gt; ops_exit_list()\n         =\u0026gt; default_device_exit_batch()\n           =\u0026gt; unregister_netdevice_many()\n             =\u0026gt; unregister_netdevice_many_notify()\n               =\u0026gt; dev_shutdown()\n                 =\u0026gt; qdisc_put()\n                   =\u0026gt; clsact_destroy() [c]\n                     =\u0026gt; tcf_block_put_ext()\n                       =\u0026gt; tcf_chain0_head_change_cb_del()\n                         =\u0026gt; tcf_chain_head_change_item()\n                           =\u0026gt; clsact_chain_head_change()\n                             =\u0026gt; mini_qdisc_pair_swap() // UAF\r\n\r\nThere are also other variants, the gist is to add an ingress (or clsact)\nqdisc with a specific shared block, then to replace that qdisc, waiting\nfor the tcx_entry kfree_rcu() to be executed and subsequently accessing\nthe current active qdisc\u0026apos;s miniq one way or another.\r\n\r\nThe correct fix is to turn the miniq_active boolean into a counter. What\ncan be observed, at step 2 above, the counter transitions from 0-\u0026gt;1, at\nstep [a] from 1-\u0026gt;2 (in order for the miniq object to remain active during\nthe replacement), then in [b] from 2-\u0026gt;1 and finally [c] 1-\u0026gt;0 with the\neventual release. The reference counter in general ranges from [0,2] and\nit does not need to be atomic since all access to the counter is protected\nby the rtnl mutex. With this in place, there is no longer a UAF happening\nand the tcx_entry is freed at the correct time.(CVE-2024-41010)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nxfs: don\u0026apos;t walk off the end of a directory data block\r\n\r\nThis adds sanity checks for xfs_dir2_data_unused and xfs_dir2_data_entry\nto make sure don\u0026apos;t stray beyond valid memory region. Before patching, the\nloop simply checks that the start offset of the dup and dep is within the\nrange. So in a crafted image, if last entry is xfs_dir2_data_unused, we\ncan change dup-\u0026gt;length to dup-\u0026gt;length-1 and leave 1 byte of space. In the\nnext traversal, this space will be considered as dup or dep. We may\nencounter an out of bound read when accessing the fixed members.\r\n\r\nIn the patch, we make sure that the remaining bytes large enough to hold\nan unused entry before accessing xfs_dir2_data_unused and\nxfs_dir2_data_unused is XFS_DIR2_DATA_ALIGN byte aligned. We also make\nsure that the remaining bytes large enough to hold a dirent with a\nsingle-byte name before accessing xfs_dir2_data_entry.(CVE-2024-41013)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nxfs: add bounds checking to xlog_recover_process_data\r\n\r\nThere is a lack of verification of the space occupied by fixed members\nof xlog_op_header in the xlog_recover_process_data.\r\n\r\nWe can create a crafted image to trigger an out of bounds read by\nfollowing these steps:\n    1) Mount an image of xfs, and do some file operations to leave records\n    2) Before umounting, copy the image for subsequent steps to simulate\n       abnormal exit. Because umount will ensure that tail_blk and\n       head_blk are the same, which will result in the inability to enter\n       xlog_recover_process_data\n    3) Write a tool to parse and modify the copied image in step 2\n    4) Make the end of the xlog_op_header entries only 1 byte away from\n       xlog_rec_header-\u0026gt;h_size\n    5) xlog_rec_header-\u0026gt;h_num_logops++\n    6) Modify xlog_rec_header-\u0026gt;h_crc\r\n\r\nFix:\nAdd a check to make sure there is sufficient space to access fixed members\nof xlog_op_header.(CVE-2024-41014)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nfs/ntfs3: Add a check for attr_names and oatbl\r\n\r\nAdded out-of-bound checking for *ane (ATTR_NAME_ENTRY).(CVE-2024-41018)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nfs/ntfs3: Validate ff offset\r\n\r\nThis adds sanity checks for ff offset. There is a check\non rt-\u0026gt;first_free at first, but walking through by ff\nwithout any check. If the second ff is a large offset.\nWe may encounter an out-of-bound read.(CVE-2024-41019)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nfilelock: Fix fcntl/close race recovery compat path\r\n\r\nWhen I wrote commit 3cad1bc01041 (\u0026quot;filelock: Remove locks reliably when\nfcntl/close race is detected\u0026quot;), I missed that there are two copies of the\ncode I was patching: The normal version, and the version for 64-bit offsets\non 32-bit kernels.\nThanks to Greg KH for stumbling over this while doing the stable\nbackport...\r\n\r\nApply exactly the same fix to the compat path for 32-bit kernels.(CVE-2024-41020)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\ns390/mm: Fix VM_FAULT_HWPOISON handling in do_exception()\r\n\r\nThere is no support for HWPOISON, MEMORY_FAILURE, or ARCH_HAS_COPY_MC on\ns390. Therefore we do not expect to see VM_FAULT_HWPOISON in\ndo_exception().\r\n\r\nHowever, since commit af19487f00f3 (\u0026quot;mm: make PTE_MARKER_SWAPIN_ERROR more\ngeneral\u0026quot;), it is possible to see VM_FAULT_HWPOISON in combination with\nPTE_MARKER_POISONED, even on architectures that do not support HWPOISON\notherwise. In this case, we will end up on the BUG() in do_exception().\r\n\r\nFix this by treating VM_FAULT_HWPOISON the same as VM_FAULT_SIGBUS, similar\nto x86 when MEMORY_FAILURE is not configured. Also print unexpected fault\nflags, for easier debugging.\r\n\r\nNote that VM_FAULT_HWPOISON_LARGE is not expected, because s390 cannot\nsupport swap entries on other levels than PTE level.(CVE-2024-41021)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nsched/deadline: Fix task_struct reference leak\r\n\r\nDuring the execution of the following stress test with linux-rt:\r\n\r\nstress-ng --cyclic 30 --timeout 30 --minimize --quiet\r\n\r\nkmemleak frequently reported a memory leak concerning the task_struct:\r\n\r\nunreferenced object 0xffff8881305b8000 (size 16136):\n  comm \u0026quot;stress-ng\u0026quot;, pid 614, jiffies 4294883961 (age 286.412s)\n  object hex dump (first 32 bytes):\n    02 40 00 00 00 00 00 00 00 00 00 00 00 00 00 00  .@..............\n    00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................\n  debug hex dump (first 16 bytes):\n    53 09 00 00 00 00 00 00 00 00 00 00 00 00 00 00  S...............\n  backtrace:\n    [\u0026lt;00000000046b6790\u0026gt;] dup_task_struct+0x30/0x540\n    [\u0026lt;00000000c5ca0f0b\u0026gt;] copy_process+0x3d9/0x50e0\n    [\u0026lt;00000000ced59777\u0026gt;] kernel_clone+0xb0/0x770\n    [\u0026lt;00000000a50befdc\u0026gt;] __do_sys_clone+0xb6/0xf0\n    [\u0026lt;000000001dbf2008\u0026gt;] do_syscall_64+0x5d/0xf0\n    [\u0026lt;00000000552900ff\u0026gt;] entry_SYSCALL_64_after_hwframe+0x6e/0x76\r\n\r\nThe issue occurs in start_dl_timer(), which increments the task_struct\nreference count and sets a timer. The timer callback, dl_task_timer,\nis supposed to decrement the reference count upon expiration. However,\nif enqueue_task_dl() is called before the timer expires and cancels it,\nthe reference count is not decremented, leading to the leak.\r\n\r\nThis patch fixes the reference leak by ensuring the task_struct\nreference count is properly decremented when the timer is canceled.(CVE-2024-41023)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nfirmware: cs_dsp: Fix overflow checking of wmfw header\r\n\r\nFix the checking that firmware file buffer is large enough for the\nwmfw header, to prevent overrunning the buffer.\r\n\r\nThe original code tested that the firmware data buffer contained\nenough bytes for the sums of the size of the structs\r\n\r\n\twmfw_header + wmfw_adsp1_sizes + wmfw_footer\r\n\r\nBut wmfw_adsp1_sizes is only used on ADSP1 firmware. For ADSP2 and\nHalo Core the equivalent struct is wmfw_adsp2_sizes, which is\n4 bytes longer. So the length check didn\u0026apos;t guarantee that there\nare enough bytes in the firmware buffer for a header with\nwmfw_adsp2_sizes.\r\n\r\nThis patch splits the length check into three separate parts. Each\nof the wmfw_header, wmfw_adsp?_sizes and wmfw_footer are checked\nseparately before they are used.(CVE-2024-41039)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nnet/sched: Fix UAF when resolving a clash\r\n\r\nKASAN reports the following UAF:\r\n\r\n BUG: KASAN: slab-use-after-free in tcf_ct_flow_table_process_conn+0x12b/0x380 [act_ct]\n Read of size 1 at addr ffff888c07603600 by task handler130/6469\r\n\r\n Call Trace:\n  \u0026lt;IRQ\u0026gt;\n  dump_stack_lvl+0x48/0x70\n  print_address_description.constprop.0+0x33/0x3d0\n  print_report+0xc0/0x2b0\n  kasan_report+0xd0/0x120\n  __asan_load1+0x6c/0x80\n  tcf_ct_flow_table_process_conn+0x12b/0x380 [act_ct]\n  tcf_ct_act+0x886/0x1350 [act_ct]\n  tcf_action_exec+0xf8/0x1f0\n  fl_classify+0x355/0x360 [cls_flower]\n  __tcf_classify+0x1fd/0x330\n  tcf_classify+0x21c/0x3c0\n  sch_handle_ingress.constprop.0+0x2c5/0x500\n  __netif_receive_skb_core.constprop.0+0xb25/0x1510\n  __netif_receive_skb_list_core+0x220/0x4c0\n  netif_receive_skb_list_internal+0x446/0x620\n  napi_complete_done+0x157/0x3d0\n  gro_cell_poll+0xcf/0x100\n  __napi_poll+0x65/0x310\n  net_rx_action+0x30c/0x5c0\n  __do_softirq+0x14f/0x491\n  __irq_exit_rcu+0x82/0xc0\n  irq_exit_rcu+0xe/0x20\n  common_interrupt+0xa1/0xb0\n  \u0026lt;/IRQ\u0026gt;\n  \u0026lt;TASK\u0026gt;\n  asm_common_interrupt+0x27/0x40\r\n\r\n Allocated by task 6469:\n  kasan_save_stack+0x38/0x70\n  kasan_set_track+0x25/0x40\n  kasan_save_alloc_info+0x1e/0x40\n  __kasan_krealloc+0x133/0x190\n  krealloc+0xaa/0x130\n  nf_ct_ext_add+0xed/0x230 [nf_conntrack]\n  tcf_ct_act+0x1095/0x1350 [act_ct]\n  tcf_action_exec+0xf8/0x1f0\n  fl_classify+0x355/0x360 [cls_flower]\n  __tcf_classify+0x1fd/0x330\n  tcf_classify+0x21c/0x3c0\n  sch_handle_ingress.constprop.0+0x2c5/0x500\n  __netif_receive_skb_core.constprop.0+0xb25/0x1510\n  __netif_receive_skb_list_core+0x220/0x4c0\n  netif_receive_skb_list_internal+0x446/0x620\n  napi_complete_done+0x157/0x3d0\n  gro_cell_poll+0xcf/0x100\n  __napi_poll+0x65/0x310\n  net_rx_action+0x30c/0x5c0\n  __do_softirq+0x14f/0x491\r\n\r\n Freed by task 6469:\n  kasan_save_stack+0x38/0x70\n  kasan_set_track+0x25/0x40\n  kasan_save_free_info+0x2b/0x60\n  ____kasan_slab_free+0x180/0x1f0\n  __kasan_slab_free+0x12/0x30\n  slab_free_freelist_hook+0xd2/0x1a0\n  __kmem_cache_free+0x1a2/0x2f0\n  kfree+0x78/0x120\n  nf_conntrack_free+0x74/0x130 [nf_conntrack]\n  nf_ct_destroy+0xb2/0x140 [nf_conntrack]\n  __nf_ct_resolve_clash+0x529/0x5d0 [nf_conntrack]\n  nf_ct_resolve_clash+0xf6/0x490 [nf_conntrack]\n  __nf_conntrack_confirm+0x2c6/0x770 [nf_conntrack]\n  tcf_ct_act+0x12ad/0x1350 [act_ct]\n  tcf_action_exec+0xf8/0x1f0\n  fl_classify+0x355/0x360 [cls_flower]\n  __tcf_classify+0x1fd/0x330\n  tcf_classify+0x21c/0x3c0\n  sch_handle_ingress.constprop.0+0x2c5/0x500\n  __netif_receive_skb_core.constprop.0+0xb25/0x1510\n  __netif_receive_skb_list_core+0x220/0x4c0\n  netif_receive_skb_list_internal+0x446/0x620\n  napi_complete_done+0x157/0x3d0\n  gro_cell_poll+0xcf/0x100\n  __napi_poll+0x65/0x310\n  net_rx_action+0x30c/0x5c0\n  __do_softirq+0x14f/0x491\r\n\r\nThe ct may be dropped if a clash has been resolved but is still passed to\nthe tcf_ct_flow_table_process_conn function for further usage. This issue\ncan be fixed by retrieving ct from skb again after confirming conntrack.(CVE-2024-41040)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nudp: Set SOCK_RCU_FREE earlier in udp_lib_get_port().\r\n\r\nsyzkaller triggered the warning [0] in udp_v4_early_demux().\r\n\r\nIn udp_v[46]_early_demux() and sk_lookup(), we do not touch the refcount\nof the looked-up sk and use sock_pfree() as skb-\u0026gt;destructor, so we check\nSOCK_RCU_FREE to ensure that the sk is safe to access during the RCU grace\nperiod.\r\n\r\nCurrently, SOCK_RCU_FREE is flagged for a bound socket after being put\ninto the hash table.  Moreover, the SOCK_RCU_FREE check is done too early\nin udp_v[46]_early_demux() and sk_lookup(), so there could be a small race\nwindow:\r\n\r\n  CPU1                                 CPU2\n  ----                                 ----\n  udp_v4_early_demux()                 udp_lib_get_port()\n  |                                    |- hlist_add_head_rcu()\n  |- sk = __udp4_lib_demux_lookup()    |\n  |- DEBUG_NET_WARN_ON_ONCE(sk_is_refcounted(sk));\n                                       `- sock_set_flag(sk, SOCK_RCU_FREE)\r\n\r\nWe had the same bug in TCP and fixed it in commit 871019b22d1b (\u0026quot;net:\nset SOCK_RCU_FREE before inserting socket into hashtable\u0026quot;).\r\n\r\nLet\u0026apos;s apply the same fix for UDP.\r\n\r\n[0]:\nWARNING: CPU: 0 PID: 11198 at net/ipv4/udp.c:2599 udp_v4_early_demux+0x481/0xb70 net/ipv4/udp.c:2599\nModules linked in:\nCPU: 0 PID: 11198 Comm: syz-executor.1 Not tainted 6.9.0-g93bda33046e7 #13\nHardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS rel-1.16.0-0-gd239552ce722-prebuilt.qemu.org 04/01/2014\nRIP: 0010:udp_v4_early_demux+0x481/0xb70 net/ipv4/udp.c:2599\nCode: c5 7a 15 fe bb 01 00 00 00 44 89 e9 31 ff d3 e3 81 e3 bf ef ff ff 89 de e8 2c 74 15 fe 85 db 0f 85 02 06 00 00 e8 9f 7a 15 fe \u0026lt;0f\u0026gt; 0b e8 98 7a 15 fe 49 8d 7e 60 e8 4f 39 2f fe 49 c7 46 60 20 52\nRSP: 0018:ffffc9000ce3fa58 EFLAGS: 00010293\nRAX: 0000000000000000 RBX: 0000000000000000 RCX: ffffffff8318c92c\nRDX: ffff888036ccde00 RSI: ffffffff8318c2f1 RDI: 0000000000000001\nRBP: ffff88805a2dd6e0 R08: 0000000000000001 R09: 0000000000000000\nR10: 0000000000000000 R11: 0001ffffffffffff R12: ffff88805a2dd680\nR13: 0000000000000007 R14: ffff88800923f900 R15: ffff88805456004e\nFS:  00007fc449127640(0000) GS:ffff88807dc00000(0000) knlGS:0000000000000000\nCS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033\nCR2: 00007fc449126e38 CR3: 000000003de4b002 CR4: 0000000000770ef0\nDR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000\nDR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000600\nPKRU: 55555554\nCall Trace:\n \u0026lt;TASK\u0026gt;\n ip_rcv_finish_core.constprop.0+0xbdd/0xd20 net/ipv4/ip_input.c:349\n ip_rcv_finish+0xda/0x150 net/ipv4/ip_input.c:447\n NF_HOOK include/linux/netfilter.h:314 [inline]\n NF_HOOK include/linux/netfilter.h:308 [inline]\n ip_rcv+0x16c/0x180 net/ipv4/ip_input.c:569\n __netif_receive_skb_one_core+0xb3/0xe0 net/core/dev.c:5624\n __netif_receive_skb+0x21/0xd0 net/core/dev.c:5738\n netif_receive_skb_internal net/core/dev.c:5824 [inline]\n netif_receive_skb+0x271/0x300 net/core/dev.c:5884\n tun_rx_batched drivers/net/tun.c:1549 [inline]\n tun_get_user+0x24db/0x2c50 drivers/net/tun.c:2002\n tun_chr_write_iter+0x107/0x1a0 drivers/net/tun.c:2048\n new_sync_write fs/read_write.c:497 [inline]\n vfs_write+0x76f/0x8d0 fs/read_write.c:590\n ksys_write+0xbf/0x190 fs/read_write.c:643\n __do_sys_write fs/read_write.c:655 [inline]\n __se_sys_write fs/read_write.c:652 [inline]\n __x64_sys_write+0x41/0x50 fs/read_write.c:652\n x64_sys_call+0xe66/0x1990 arch/x86/include/generated/asm/syscalls_64.h:2\n do_syscall_x64 arch/x86/entry/common.c:52 [inline]\n do_syscall_64+0x4b/0x110 arch/x86/entry/common.c:83\n entry_SYSCALL_64_after_hwframe+0x4b/0x53\nRIP: 0033:0x7fc44a68bc1f\nCode: 89 54 24 18 48 89 74 24 10 89 7c 24 08 e8 e9 cf f5 ff 48 8b 54 24 18 48 8b 74 24 10 41 89 c0 8b 7c 24 08 b8 01 00 00 00 0f 05 \u0026lt;48\u0026gt; 3d 00 f0 ff ff 77 31 44 89 c7 48 89 44 24 08 e8 3c d0 f5 ff 48\nRSP: 002b:00007fc449126c90 EFLAGS: 00000293 ORIG_RAX: 0000000000000001\nRAX: ffffffffffffffda RBX: 00000000004bc050 RCX: 00007fc44a68bc1f\nR\n---truncated---(CVE-2024-41041)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nppp: reject claimed-as-LCP but actually malformed packets\r\n\r\nSince \u0026apos;ppp_async_encode()\u0026apos; assumes valid LCP packets (with code\nfrom 1 to 7 inclusive), add \u0026apos;ppp_check_packet()\u0026apos; to ensure that\nLCP packet has an actual body beyond PPP_LCP header bytes, and\nreject claimed-as-LCP but actually malformed data otherwise.(CVE-2024-41044)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nbpf: Defer work in bpf_timer_cancel_and_free\r\n\r\nCurrently, the same case as previous patch (two timer callbacks trying\nto cancel each other) can be invoked through bpf_map_update_elem as\nwell, or more precisely, freeing map elements containing timers. Since\nthis relies on hrtimer_cancel as well, it is prone to the same deadlock\nsituation as the previous patch.\r\n\r\nIt would be sufficient to use hrtimer_try_to_cancel to fix this problem,\nas the timer cannot be enqueued after async_cancel_and_free. Once\nasync_cancel_and_free has been done, the timer must be reinitialized\nbefore it can be armed again. The callback running in parallel trying to\narm the timer will fail, and freeing bpf_hrtimer without waiting is\nsufficient (given kfree_rcu), and bpf_timer_cb will return\nHRTIMER_NORESTART, preventing the timer from being rearmed again.\r\n\r\nHowever, there exists a UAF scenario where the callback arms the timer\nbefore entering this function, such that if cancellation fails (due to\ntimer callback invoking this routine, or the target timer callback\nrunning concurrently). In such a case, if the timer expiration is\nsignificantly far in the future, the RCU grace period expiration\nhappening before it will free the bpf_hrtimer state and along with it\nthe struct hrtimer, that is enqueued.\r\n\r\nHence, it is clear cancellation needs to occur after\nasync_cancel_and_free, and yet it cannot be done inline due to deadlock\nissues. We thus modify bpf_timer_cancel_and_free to defer work to the\nglobal workqueue, adding a work_struct alongside rcu_head (both used at\n_different_ points of time, so can share space).\r\n\r\nUpdate existing code comments to reflect the new state of affairs.(CVE-2024-41045)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nskmsg: Skip zero length skb in sk_msg_recvmsg\r\n\r\nWhen running BPF selftests (./test_progs -t sockmap_basic) on a Loongarch\nplatform, the following kernel panic occurs:\r\n\r\n  [...]\n  Oops[#1]:\n  CPU: 22 PID: 2824 Comm: test_progs Tainted: G           OE  6.10.0-rc2+ #18\n  Hardware name: LOONGSON Dabieshan/Loongson-TC542F0, BIOS Loongson-UDK2018\n     ... ...\n     ra: 90000000048bf6c0 sk_msg_recvmsg+0x120/0x560\n    ERA: 9000000004162774 copy_page_to_iter+0x74/0x1c0\n   CRMD: 000000b0 (PLV0 -IE -DA +PG DACF=CC DACM=CC -WE)\n   PRMD: 0000000c (PPLV0 +PIE +PWE)\n   EUEN: 00000007 (+FPE +SXE +ASXE -BTE)\n   ECFG: 00071c1d (LIE=0,2-4,10-12 VS=7)\n  ESTAT: 00010000 [PIL] (IS= ECode=1 EsubCode=0)\n   BADV: 0000000000000040\n   PRID: 0014c011 (Loongson-64bit, Loongson-3C5000)\n  Modules linked in: bpf_testmod(OE) xt_CHECKSUM xt_MASQUERADE xt_conntrack\n  Process test_progs (pid: 2824, threadinfo=0000000000863a31, task=...)\n  Stack : ...\n  Call Trace:\n  [\u0026lt;9000000004162774\u0026gt;] copy_page_to_iter+0x74/0x1c0\n  [\u0026lt;90000000048bf6c0\u0026gt;] sk_msg_recvmsg+0x120/0x560\n  [\u0026lt;90000000049f2b90\u0026gt;] tcp_bpf_recvmsg_parser+0x170/0x4e0\n  [\u0026lt;90000000049aae34\u0026gt;] inet_recvmsg+0x54/0x100\n  [\u0026lt;900000000481ad5c\u0026gt;] sock_recvmsg+0x7c/0xe0\n  [\u0026lt;900000000481e1a8\u0026gt;] __sys_recvfrom+0x108/0x1c0\n  [\u0026lt;900000000481e27c\u0026gt;] sys_recvfrom+0x1c/0x40\n  [\u0026lt;9000000004c076ec\u0026gt;] do_syscall+0x8c/0xc0\n  [\u0026lt;9000000003731da4\u0026gt;] handle_syscall+0xc4/0x160\n  Code: ...\n  ---[ end trace 0000000000000000 ]---\n  Kernel panic - not syncing: Fatal exception\n  Kernel relocated by 0x3510000\n   .text @ 0x9000000003710000\n   .data @ 0x9000000004d70000\n   .bss  @ 0x9000000006469400\n  ---[ end Kernel panic - not syncing: Fatal exception ]---\n  [...]\r\n\r\nThis crash happens every time when running sockmap_skb_verdict_shutdown\nsubtest in sockmap_basic.\r\n\r\nThis crash is because a NULL pointer is passed to page_address() in the\nsk_msg_recvmsg(). Due to the different implementations depending on the\narchitecture, page_address(NULL) will trigger a panic on Loongarch\nplatform but not on x86 platform. So this bug was hidden on x86 platform\nfor a while, but now it is exposed on Loongarch platform. The root cause\nis that a zero length skb (skb-\u0026gt;len == 0) was put on the queue.\r\n\r\nThis zero length skb is a TCP FIN packet, which was sent by shutdown(),\ninvoked in test_sockmap_skb_verdict_shutdown():\r\n\r\n\tshutdown(p1, SHUT_WR);\r\n\r\nIn this case, in sk_psock_skb_ingress_enqueue(), num_sge is zero, and no\npage is put to this sge (see sg_set_page in sg_set_page), but this empty\nsge is queued into ingress_msg list.\r\n\r\nAnd in sk_msg_recvmsg(), this empty sge is used, and a NULL page is got by\nsg_page(sge). Pass this NULL page to copy_page_to_iter(), which passes it\nto kmap_local_page() and to page_address(), then kernel panics.\r\n\r\nTo solve this, we should skip this zero length skb. So in sk_msg_recvmsg(),\nif copy is zero, that means it\u0026apos;s a zero length skb, skip invoking\ncopy_page_to_iter(). We are using the EFAULT return triggered by\ncopy_page_to_iter to check for is_fin in tcp_bpf.c.(CVE-2024-41048)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nfilelock: fix potential use-after-free in posix_lock_inode\r\n\r\nLight Hsieh reported a KASAN UAF warning in trace_posix_lock_inode().\nThe request pointer had been changed earlier to point to a lock entry\nthat was added to the inode\u0026apos;s list. However, before the tracepoint could\nfire, another task raced in and freed that lock.\r\n\r\nFix this by moving the tracepoint inside the spinlock, which should\nensure that this doesn\u0026apos;t happen.(CVE-2024-41049)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nfirmware: cs_dsp: Use strnlen() on name fields in V1 wmfw files\r\n\r\nUse strnlen() instead of strlen() on the algorithm and coefficient name\nstring arrays in V1 wmfw files.\r\n\r\nIn V1 wmfw files the name is a NUL-terminated string in a fixed-size\narray. cs_dsp should protect against overrunning the array if the NUL\nterminator is missing.(CVE-2024-41056)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nbluetooth/l2cap: sync sock recv cb and release\r\n\r\nThe problem occurs between the system call to close the sock and hci_rx_work,\nwhere the former releases the sock and the latter accesses it without lock protection.\r\n\r\n           CPU0                       CPU1\n           ----                       ----\n           sock_close                 hci_rx_work\n\t   l2cap_sock_release         hci_acldata_packet\n\t   l2cap_sock_kill            l2cap_recv_frame\n\t   sk_free                    l2cap_conless_channel\n\t                              l2cap_sock_recv_cb\r\n\r\nIf hci_rx_work processes the data that needs to be received before the sock is\nclosed, then everything is normal; Otherwise, the work thread may access the\nreleased sock when receiving data.\r\n\r\nAdd a chan mutex in the rx callback of the sock to achieve synchronization between\nthe sock release and recv cb.\r\n\r\nSock is dead, so set chan data to NULL, avoid others use invalid sock pointer.(CVE-2024-41062)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nBluetooth: hci_core: cancel all works upon hci_unregister_dev()\r\n\r\nsyzbot is reporting that calling hci_release_dev() from hci_error_reset()\ndue to hci_dev_put() from hci_error_reset() can cause deadlock at\ndestroy_workqueue(), for hci_error_reset() is called from\nhdev-\u0026gt;req_workqueue which destroy_workqueue() needs to flush.\r\n\r\nWe need to make sure that hdev-\u0026gt;{rx_work,cmd_work,tx_work} which are\nqueued into hdev-\u0026gt;workqueue and hdev-\u0026gt;{power_on,error_reset} which are\nqueued into hdev-\u0026gt;req_workqueue are no longer running by the moment\r\n\r\n       destroy_workqueue(hdev-\u0026gt;workqueue);\n       destroy_workqueue(hdev-\u0026gt;req_workqueue);\r\n\r\nare called from hci_release_dev().\r\n\r\nCall cancel_work_sync() on these work items from hci_unregister_dev()\nas soon as hdev-\u0026gt;list is removed from hci_dev_list.(CVE-2024-41063)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\npowerpc/eeh: avoid possible crash when edev-\u0026gt;pdev changes\r\n\r\nIf a PCI device is removed during eeh_pe_report_edev(), edev-\u0026gt;pdev\nwill change and can cause a crash, hold the PCI rescan/remove lock\nwhile taking a copy of edev-\u0026gt;pdev-\u0026gt;bus.(CVE-2024-41064)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nASoC: topology: Fix references to freed memory\r\n\r\nMost users after parsing a topology file, release memory used by it, so\nhaving pointer references directly into topology file contents is wrong.\nUse devm_kmemdup(), to allocate memory as needed.(CVE-2024-41069)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nwifi: cfg80211: wext: add extra SIOCSIWSCAN data check\r\n\r\nIn \u0026apos;cfg80211_wext_siwscan()\u0026apos;, add extra check whether number of\nchannels passed via \u0026apos;ioctl(sock, SIOCSIWSCAN, ...)\u0026apos; doesn\u0026apos;t exceed\nIW_MAX_FREQUENCIES and reject invalid request with -EINVAL otherwise.(CVE-2024-41072)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nnvme: avoid double free special payload\r\n\r\nIf a discard request needs to be retried, and that retry may fail before\na new special payload is added, a double free will result. Clear the\nRQF_SPECIAL_LOAD when the request is cleaned.(CVE-2024-41073)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\ncachefiles: Set object to close if ondemand_id \u0026lt; 0 in copen\r\n\r\nIf copen is maliciously called in the user mode, it may delete the request\ncorresponding to the random id. And the request may have not been read yet.\r\n\r\nNote that when the object is set to reopen, the open request will be done\nwith the still reopen state in above case. As a result, the request\ncorresponding to this object is always skipped in select_req function, so\nthe read request is never completed and blocks other process.\r\n\r\nFix this issue by simply set object to close if its id \u0026lt; 0 in copen.(CVE-2024-41074)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\ncachefiles: add consistency check for copen/cread\r\n\r\nThis prevents malicious processes from completing random copen/cread\nrequests and crashing the system. Added checks are listed below:\r\n\r\n  * Generic, copen can only complete open requests, and cread can only\n    complete read requests.\n  * For copen, ondemand_id must not be 0, because this indicates that the\n    request has not been read by the daemon.\n  * For cread, the object corresponding to fd and req should be the same.(CVE-2024-41075)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nNFSv4: Fix memory leak in nfs4_set_security_label\r\n\r\nWe leak nfs_fattr and nfs4_label every time we set a security xattr.(CVE-2024-41076)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nnull_blk: fix validation of block size\r\n\r\nBlock size should be between 512 and PAGE_SIZE and be a power of 2. The current\ncheck does not validate this, so update the check.\r\n\r\nWithout this patch, null_blk would Oops due to a null pointer deref when\nloaded with bs=1536 [1].\r\n\r\n\n[axboe: remove unnecessary braces and != 0 check](CVE-2024-41077)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nio_uring: fix possible deadlock in io_register_iowq_max_workers()\r\n\r\nThe io_register_iowq_max_workers() function calls io_put_sq_data(),\nwhich acquires the sqd-\u0026gt;lock without releasing the uring_lock.\nSimilar to the commit 009ad9f0c6ee (\u0026quot;io_uring: drop ctx-\u0026gt;uring_lock\nbefore acquiring sqd-\u0026gt;lock\u0026quot;), this can lead to a potential deadlock\nsituation.\r\n\r\nTo resolve this issue, the uring_lock is released before calling\nio_put_sq_data(), and then it is re-acquired after the function call.\r\n\r\nThis change ensures that the locks are acquired in the correct\norder, preventing the possibility of a deadlock.(CVE-2024-41080)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\ncxl/mem: Fix no cxl_nvd during pmem region auto-assembling\r\n\r\nWhen CXL subsystem is auto-assembling a pmem region during cxl\nendpoint port probing, always hit below calltrace.\r\n\r\n BUG: kernel NULL pointer dereference, address: 0000000000000078\n #PF: supervisor read access in kernel mode\n #PF: error_code(0x0000) - not-present page\n RIP: 0010:cxl_pmem_region_probe+0x22e/0x360 [cxl_pmem]\n Call Trace:\n  \u0026lt;TASK\u0026gt;\n  ? __die+0x24/0x70\n  ? page_fault_oops+0x82/0x160\n  ? do_user_addr_fault+0x65/0x6b0\n  ? exc_page_fault+0x7d/0x170\n  ? asm_exc_page_fault+0x26/0x30\n  ? cxl_pmem_region_probe+0x22e/0x360 [cxl_pmem]\n  ? cxl_pmem_region_probe+0x1ac/0x360 [cxl_pmem]\n  cxl_bus_probe+0x1b/0x60 [cxl_core]\n  really_probe+0x173/0x410\n  ? __pfx___device_attach_driver+0x10/0x10\n  __driver_probe_device+0x80/0x170\n  driver_probe_device+0x1e/0x90\n  __device_attach_driver+0x90/0x120\n  bus_for_each_drv+0x84/0xe0\n  __device_attach+0xbc/0x1f0\n  bus_probe_device+0x90/0xa0\n  device_add+0x51c/0x710\n  devm_cxl_add_pmem_region+0x1b5/0x380 [cxl_core]\n  cxl_bus_probe+0x1b/0x60 [cxl_core]\r\n\r\nThe cxl_nvd of the memdev needs to be available during the pmem region\nprobe. Currently the cxl_nvd is registered after the endpoint port probe.\nThe endpoint probe, in the case of autoassembly of regions, can cause a\npmem region probe requiring the not yet available cxl_nvd. Adjust the\nsequence so this dependency is met.\r\n\r\nThis requires adding a port parameter to cxl_find_nvdimm_bridge() that\ncan be used to query the ancestor root port. The endpoint port is not\nyet available, but will share a common ancestor with its parent, so\nstart the query from there instead.(CVE-2024-41085)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\ntap: add missing verification for short frame\r\n\r\nThe cited commit missed to check against the validity of the frame length\nin the tap_get_user_xdp() path, which could cause a corrupted skb to be\nsent downstack. Even before the skb is transmitted, the\ntap_get_user_xdp()--\u0026gt;skb_set_network_header() may assume the size is more\nthan ETH_HLEN. Once transmitted, this could either cause out-of-bound\naccess beyond the actual length, or confuse the underlayer with incorrect\nor inconsistent header length in the skb metadata.\r\n\r\nIn the alternative path, tap_get_user() already prohibits short frame which\nhas the length less than Ethernet header size from being transmitted.\r\n\r\nThis is to drop any frame shorter than the Ethernet header size just like\nhow tap_get_user() does.\r\n\r\nCVE: CVE-2024-41090(CVE-2024-41090)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\ntun: add missing verification for short frame\r\n\r\nThe cited commit missed to check against the validity of the frame length\nin the tun_xdp_one() path, which could cause a corrupted skb to be sent\ndownstack. Even before the skb is transmitted, the\ntun_xdp_one--\u0026gt;eth_type_trans() may access the Ethernet header although it\ncan be less than ETH_HLEN. Once transmitted, this could either cause\nout-of-bound access beyond the actual length, or confuse the underlayer\nwith incorrect or inconsistent header length in the skb metadata.\r\n\r\nIn the alternative path, tun_get_user() already prohibits short frame which\nhas the length less than Ethernet header size from being transmitted for\nIFF_TAP.\r\n\r\nThis is to drop any frame shorter than the Ethernet header size just like\nhow tun_get_user() does.\r\n\r\nCVE: CVE-2024-41091(CVE-2024-41091)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nPCI/MSI: Fix UAF in msi_capability_init\r\n\r\nKFENCE reports the following UAF:\r\n\r\n BUG: KFENCE: use-after-free read in __pci_enable_msi_range+0x2c0/0x488\r\n\r\n Use-after-free read at 0x0000000024629571 (in kfence-#12):\n  __pci_enable_msi_range+0x2c0/0x488\n  pci_alloc_irq_vectors_affinity+0xec/0x14c\n  pci_alloc_irq_vectors+0x18/0x28\r\n\r\n kfence-#12: 0x0000000008614900-0x00000000e06c228d, size=104, cache=kmalloc-128\r\n\r\n allocated by task 81 on cpu 7 at 10.808142s:\n  __kmem_cache_alloc_node+0x1f0/0x2bc\n  kmalloc_trace+0x44/0x138\n  msi_alloc_desc+0x3c/0x9c\n  msi_domain_insert_msi_desc+0x30/0x78\n  msi_setup_msi_desc+0x13c/0x184\n  __pci_enable_msi_range+0x258/0x488\n  pci_alloc_irq_vectors_affinity+0xec/0x14c\n  pci_alloc_irq_vectors+0x18/0x28\r\n\r\n freed by task 81 on cpu 7 at 10.811436s:\n  msi_domain_free_descs+0xd4/0x10c\n  msi_domain_free_locked.part.0+0xc0/0x1d8\n  msi_domain_alloc_irqs_all_locked+0xb4/0xbc\n  pci_msi_setup_msi_irqs+0x30/0x4c\n  __pci_enable_msi_range+0x2a8/0x488\n  pci_alloc_irq_vectors_affinity+0xec/0x14c\n  pci_alloc_irq_vectors+0x18/0x28\r\n\r\nDescriptor allocation done in:\n__pci_enable_msi_range\n    msi_capability_init\n        msi_setup_msi_desc\n            msi_insert_msi_desc\n                msi_domain_insert_msi_desc\n                    msi_alloc_desc\n                        ...\r\n\r\nFreed in case of failure in __msi_domain_alloc_locked()\n__pci_enable_msi_range\n    msi_capability_init\n        pci_msi_setup_msi_irqs\n            msi_domain_alloc_irqs_all_locked\n                msi_domain_alloc_locked\n                    __msi_domain_alloc_locked =\u0026gt; fails\n                    msi_domain_free_locked\n                        ...\r\n\r\nThat failure propagates back to pci_msi_setup_msi_irqs() in\nmsi_capability_init() which accesses the descriptor for unmasking in the\nerror exit path.\r\n\r\nCure it by copying the descriptor and using the copy for the error exit path\nunmask operation.\r\n\r\n[ tglx: Massaged change log ](CVE-2024-41096)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nbpf: Take return from set_memory_ro() into account with bpf_prog_lock_ro()\r\n\r\nset_memory_ro() can fail, leaving memory unprotected.\r\n\r\nCheck its return and take it into account as an error.(CVE-2024-42068)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\niio: chemical: bme680: Fix overflows in compensate() functions\r\n\r\nThere are cases in the compensate functions of the driver that\nthere could be overflows of variables due to bit shifting ops.\nThese implications were initially discussed here [1] and they\nwere mentioned in log message of Commit 1b3bd8592780 (\u0026quot;iio:\nchemical: Add support for Bosch BME680 sensor\u0026quot;).\r\n\r\n[1]: https://lore.kernel.org/linux-iio/20180728114028.3c1bbe81@archlinux/(CVE-2024-42086)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nALSA: emux: improve patch ioctl data validation\r\n\r\nIn load_data(), make the validation of and skipping over the main info\nblock match that in load_guspatch().\r\n\r\nIn load_guspatch(), add checking that the specified patch length matches\nthe actually supplied data, like load_data() already did.(CVE-2024-42097)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\njffs2: Fix potential illegal address access in jffs2_free_inode\r\n\r\nDuring the stress testing of the jffs2 file system,the following\nabnormal printouts were found:\n[ 2430.649000] Unable to handle kernel paging request at virtual address 0069696969696948\n[ 2430.649622] Mem abort info:\n[ 2430.649829]   ESR = 0x96000004\n[ 2430.650115]   EC = 0x25: DABT (current EL), IL = 32 bits\n[ 2430.650564]   SET = 0, FnV = 0\n[ 2430.650795]   EA = 0, S1PTW = 0\n[ 2430.651032]   FSC = 0x04: level 0 translation fault\n[ 2430.651446] Data abort info:\n[ 2430.651683]   ISV = 0, ISS = 0x00000004\n[ 2430.652001]   CM = 0, WnR = 0\n[ 2430.652558] [0069696969696948] address between user and kernel address ranges\n[ 2430.653265] Internal error: Oops: 96000004 [#1] PREEMPT SMP\n[ 2430.654512] CPU: 2 PID: 20919 Comm: cat Not tainted 5.15.25-g512f31242bf6 #33\n[ 2430.655008] Hardware name: linux,dummy-virt (DT)\n[ 2430.655517] pstate: 20000005 (nzCv daif -PAN -UAO -TCO -DIT -SSBS BTYPE=--)\n[ 2430.656142] pc : kfree+0x78/0x348\n[ 2430.656630] lr : jffs2_free_inode+0x24/0x48\n[ 2430.657051] sp : ffff800009eebd10\n[ 2430.657355] x29: ffff800009eebd10 x28: 0000000000000001 x27: 0000000000000000\n[ 2430.658327] x26: ffff000038f09d80 x25: 0080000000000000 x24: ffff800009d38000\n[ 2430.658919] x23: 5a5a5a5a5a5a5a5a x22: ffff000038f09d80 x21: ffff8000084f0d14\n[ 2430.659434] x20: ffff0000bf9a6ac0 x19: 0169696969696940 x18: 0000000000000000\n[ 2430.659969] x17: ffff8000b6506000 x16: ffff800009eec000 x15: 0000000000004000\n[ 2430.660637] x14: 0000000000000000 x13: 00000001000820a1 x12: 00000000000d1b19\n[ 2430.661345] x11: 0004000800000000 x10: 0000000000000001 x9 : ffff8000084f0d14\n[ 2430.662025] x8 : ffff0000bf9a6b40 x7 : ffff0000bf9a6b48 x6 : 0000000003470302\n[ 2430.662695] x5 : ffff00002e41dcc0 x4 : ffff0000bf9aa3b0 x3 : 0000000003470342\n[ 2430.663486] x2 : 0000000000000000 x1 : ffff8000084f0d14 x0 : fffffc0000000000\n[ 2430.664217] Call trace:\n[ 2430.664528]  kfree+0x78/0x348\n[ 2430.664855]  jffs2_free_inode+0x24/0x48\n[ 2430.665233]  i_callback+0x24/0x50\n[ 2430.665528]  rcu_do_batch+0x1ac/0x448\n[ 2430.665892]  rcu_core+0x28c/0x3c8\n[ 2430.666151]  rcu_core_si+0x18/0x28\n[ 2430.666473]  __do_softirq+0x138/0x3cc\n[ 2430.666781]  irq_exit+0xf0/0x110\n[ 2430.667065]  handle_domain_irq+0x6c/0x98\n[ 2430.667447]  gic_handle_irq+0xac/0xe8\n[ 2430.667739]  call_on_irq_stack+0x28/0x54\nThe parameter passed to kfree was 5a5a5a5a, which corresponds to the target field of\nthe jffs_inode_info structure. It was found that all variables in the jffs_inode_info\nstructure were 5a5a5a5a, except for the first member sem. It is suspected that these\nvariables are not initialized because they were set to 5a5a5a5a during memory testing,\nwhich is meant to detect uninitialized memory.The sem variable is initialized in the\nfunction jffs2_i_init_once, while other members are initialized in\nthe function jffs2_init_inode_info.\r\n\r\nThe function jffs2_init_inode_info is called after iget_locked,\nbut in the iget_locked function, the destroy_inode process is triggered,\nwhich releases the inode and consequently, the target member of the inode\nis not initialized.In concurrent high pressure scenarios, iget_locked\nmay enter the destroy_inode branch as described in the code.\r\n\r\nSince the destroy_inode functionality of jffs2 only releases the target,\nthe fix method is to set target to NULL in jffs2_i_init_once.(CVE-2024-42115)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\npowerpc: Avoid nmi_enter/nmi_exit in real mode interrupt.\r\n\r\nnmi_enter()/nmi_exit() touches per cpu variables which can lead to kernel\ncrash when invoked during real mode interrupt handling (e.g. early HMI/MCE\ninterrupt handler) if percpu allocation comes from vmalloc area.\r\n\r\nEarly HMI/MCE handlers are called through DEFINE_INTERRUPT_HANDLER_NMI()\nwrapper which invokes nmi_enter/nmi_exit calls. We don\u0026apos;t see any issue when\npercpu allocation is from the embedded first chunk. However with\nCONFIG_NEED_PER_CPU_PAGE_FIRST_CHUNK enabled there are chances where percpu\nallocation can come from the vmalloc area.\r\n\r\nWith kernel command line \u0026quot;percpu_alloc=page\u0026quot; we can force percpu allocation\nto come from vmalloc area and can see kernel crash in machine_check_early:\r\n\r\n[    1.215714] NIP [c000000000e49eb4] rcu_nmi_enter+0x24/0x110\n[    1.215717] LR [c0000000000461a0] machine_check_early+0xf0/0x2c0\n[    1.215719] --- interrupt: 200\n[    1.215720] [c000000fffd73180] [0000000000000000] 0x0 (unreliable)\n[    1.215722] [c000000fffd731b0] [0000000000000000] 0x0\n[    1.215724] [c000000fffd73210] [c000000000008364] machine_check_early_common+0x134/0x1f8\r\n\r\nFix this by avoiding use of nmi_enter()/nmi_exit() in real mode if percpu\nfirst chunk is not embedded.(CVE-2024-42126)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nleds: mlxreg: Use devm_mutex_init() for mutex initialization\r\n\r\nIn this driver LEDs are registered using devm_led_classdev_register()\nso they are automatically unregistered after module\u0026apos;s remove() is done.\nled_classdev_unregister() calls module\u0026apos;s led_set_brightness() to turn off\nthe LEDs and that callback uses mutex which was destroyed already\nin module\u0026apos;s remove() so use devm API instead.(CVE-2024-42129)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\ns390/pkey: Wipe copies of protected- and secure-keys\r\n\r\nAlthough the clear-key of neither protected- nor secure-keys is\naccessible, this key material should only be visible to the calling\nprocess. So wipe all copies of protected- or secure-keys from stack,\neven in case of an error.(CVE-2024-42155)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\ngve: Account for stopped queues when reading NIC stats\r\n\r\nWe now account for the fact that the NIC might send us stats for a\nsubset of queues. Without this change, gve_get_ethtool_stats might make\nan invalid access on the priv-\u0026gt;stats_report-\u0026gt;stats array.(CVE-2024-42162)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\ndrm/amdgpu: Using uninitialized value *size when calling amdgpu_vce_cs_reloc\r\n\r\nInitialize the size before calling amdgpu_vce_cs_reloc, such as case 0x03000001.\nV2: To really improve the handling we would actually\n   need to have a separate value of 0xffffffff.(Christian)(CVE-2024-42228)","status":"published","published":"2024-08-09T11:07:25Z","modified":"2026-08-18T01:18:28.90840835Z","cvss":[{"version":"3.1","score":9.1,"vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:H","level":"critical"}],"updated_at":"2026-11-02T15:52:41.595342Z"},{"id":"RHSA-2024:9315","title":"Red Hat Security Advisory: kernel security update","status":"published","published":"2024-11-15T21:33:20Z","modified":"2026-10-20T10:31:15.230449418Z","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":"UBUNTU-CVE-2024-41085","description":"In the Linux kernel, the following vulnerability has been resolved: cxl/mem: Fix no cxl_nvd during pmem region auto-assembling When CXL subsystem is auto-assembling a pmem region during cxl endpoint port probing, always hit below calltrace.  BUG: kernel NULL pointer dereference, address: 0000000000000078  #PF: supervisor read access in kernel mode  #PF: error_code(0x0000) - not-present page  RIP: 0010:cxl_pmem_region_probe+0x22e/0x360 [cxl_pmem]  Call Trace:   \u003cTASK\u003e   ? __die+0x24/0x70   ? page_fault_oops+0x82/0x160   ? do_user_addr_fault+0x65/0x6b0   ? exc_page_fault+0x7d/0x170   ? asm_exc_page_fault+0x26/0x30   ? cxl_pmem_region_probe+0x22e/0x360 [cxl_pmem]   ? cxl_pmem_region_probe+0x1ac/0x360 [cxl_pmem]   cxl_bus_probe+0x1b/0x60 [cxl_core]   really_probe+0x173/0x410   ? __pfx___device_attach_driver+0x10/0x10   __driver_probe_device+0x80/0x170   driver_probe_device+0x1e/0x90   __device_attach_driver+0x90/0x120   bus_for_each_drv+0x84/0xe0   __device_attach+0xbc/0x1f0   bus_probe_device+0x90/0xa0   device_add+0x51c/0x710   devm_cxl_add_pmem_region+0x1b5/0x380 [cxl_core]   cxl_bus_probe+0x1b/0x60 [cxl_core] The cxl_nvd of the memdev needs to be available during the pmem region probe. Currently the cxl_nvd is registered after the endpoint port probe. The endpoint probe, in the case of autoassembly of regions, can cause a pmem region probe requiring the not yet available cxl_nvd. Adjust the sequence so this dependency is met. This requires adding a port parameter to cxl_find_nvdimm_bridge() that can be used to query the ancestor root port. The endpoint port is not yet available, but will share a common ancestor with its parent, so start the query from there instead.","status":"published","published":"2024-07-29T16:15:00Z","modified":"2026-04-22T15:02:09.099905Z","cvss":[{"version":"3.1","score":5.5,"vector":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H","level":"medium"}],"updated_at":"2026-11-02T16:54:58.679387Z"},{"id":"CVE-2024-41085","title":"cxl/mem: Fix no cxl_nvd during pmem region auto-assembling","description":"In the Linux kernel, the following vulnerability has been resolved:\n\ncxl/mem: Fix no cxl_nvd during pmem region auto-assembling\n\nWhen CXL subsystem is auto-assembling a pmem region during cxl\nendpoint port probing, always hit below calltrace.\n\n BUG: kernel NULL pointer dereference, address: 0000000000000078\n #PF: supervisor read access in kernel mode\n #PF: error_code(0x0000) - not-present page\n RIP: 0010:cxl_pmem_region_probe+0x22e/0x360 [cxl_pmem]\n Call Trace:\n  \u003cTASK\u003e\n  ? __die+0x24/0x70\n  ? page_fault_oops+0x82/0x160\n  ? do_user_addr_fault+0x65/0x6b0\n  ? exc_page_fault+0x7d/0x170\n  ? asm_exc_page_fault+0x26/0x30\n  ? cxl_pmem_region_probe+0x22e/0x360 [cxl_pmem]\n  ? cxl_pmem_region_probe+0x1ac/0x360 [cxl_pmem]\n  cxl_bus_probe+0x1b/0x60 [cxl_core]\n  really_probe+0x173/0x410\n  ? __pfx___device_attach_driver+0x10/0x10\n  __driver_probe_device+0x80/0x170\n  driver_probe_device+0x1e/0x90\n  __device_attach_driver+0x90/0x120\n  bus_for_each_drv+0x84/0xe0\n  __device_attach+0xbc/0x1f0\n  bus_probe_device+0x90/0xa0\n  device_add+0x51c/0x710\n  devm_cxl_add_pmem_region+0x1b5/0x380 [cxl_core]\n  cxl_bus_probe+0x1b/0x60 [cxl_core]\n\nThe cxl_nvd of the memdev needs to be available during the pmem region\nprobe. Currently the cxl_nvd is registered after the endpoint port probe.\nThe endpoint probe, in the case of autoassembly of regions, can cause a\npmem region probe requiring the not yet available cxl_nvd. Adjust the\nsequence so this dependency is met.\n\nThis requires adding a port parameter to cxl_find_nvdimm_bridge() that\ncan be used to query the ancestor root port. The endpoint port is not\nyet available, but will share a common ancestor with its parent, so\nstart the query from there instead.","status":"published","published":"2024-07-29T15:48:01.267Z","modified":"2026-10-28T02:31:07.406482379Z","updated_at":"2026-11-02T15:44:41.963899Z"},{"id":"SUSE-SU-2025:02254-1","title":"Security update for the Linux Kernel","description":"\nThe SUSE Linux Enterprise 15 SP7 Azure kernel was updated to receive various security bugfixes.\n\nThe following security bugs were fixed:\n\n- CVE-2023-52888: media: mediatek: vcodec: Only free buffer VA that is not NULL (bsc#1228557).\n- CVE-2024-49568: net/smc: check v2_ext_offset/eid_cnt/ism_gid_cnt when receiving proposal msg (bsc#1235728).\n- CVE-2024-57982: xfrm: state: fix out-of-bounds read during lookup (bsc#1237913).\n- CVE-2024-57995: wifi: ath12k: fix read pointer after free in ath12k_mac_assign_vif_to_vdev() (bsc#1237895).\n- CVE-2024-58053: rxrpc: Fix handling of received connection abort (bsc#1238982).\n- CVE-2025-21720: xfrm: delete intermediate secpath entry in packet offload mode (bsc#1238859).\n- CVE-2025-21868: kABI workaround for adding an header (bsc#1240180).\n- CVE-2025-21898: ftrace: Avoid potential division by zero in function_stat_show() (bsc#1240610).\n- CVE-2025-21899: tracing: Fix bad hist from corrupting named_triggers list (bsc#1240577).\n- CVE-2025-21920: vlan: enforce underlying device type (bsc#1240686).\n- CVE-2025-21938: mptcp: fix 'scheduling while atomic' in mptcp_pm_nl_append_new_local_addr (bsc#1240723).\n- CVE-2025-21959: netfilter: nf_conncount: Fully initialize struct nf_conncount_tuple in insert_tree() (bsc#1240814).\n- CVE-2025-21997: xsk: fix an integer overflow in xp_create_and_assign_umem() (bsc#1240823).\n- CVE-2025-22035: tracing: Fix use-after-free in print_graph_function_flags during tracer switching (bsc#1241544).\n- CVE-2025-22111: kABI fix for net: Remove RTNL dance for SIOCBRADDIF and SIOCBRDELIF (bsc#1241572).\n- CVE-2025-22113: ext4: define ext4_journal_destroy wrapper (bsc#1241617).\n- CVE-2025-23155: net: stmmac: Fix accessing freed irq affinity_hint (bsc#1242573).\n- CVE-2025-37738: ext4: ignore xattrs past end (bsc#1242846).\n- CVE-2025-37743: wifi: ath12k: Avoid memory leak while enabling statistics (bsc#1242163).\n- CVE-2025-37752: net_sched: sch_sfq: move the limit validation (bsc#1242504).\n- CVE-2025-37756: net: tls: explicitly disallow disconnect (bsc#1242515).\n- CVE-2025-37757: tipc: fix memory leak in tipc_link_xmit (bsc#1242521).\n- CVE-2025-37786: net: dsa: free routing table on probe failure (bsc#1242725).\n- CVE-2025-37800: driver core: fix potential NULL pointer dereference in dev_uevent() (bsc#1242849).\n- CVE-2025-37801: spi: spi-imx: Add check for spi_imx_setupxfer() (bsc#1242850).\n- CVE-2025-37811: usb: chipidea: ci_hdrc_imx: fix usbmisc handling (bsc#1242907).\n- CVE-2025-37837: iommu/tegra241-cmdqv: Fix warnings due to dmam_free_coherent() (bsc#1242952).\n- CVE-2025-37844: cifs: avoid NULL pointer dereference in dbg call (bsc#1242946).\n- CVE-2025-37859: page_pool: avoid infinite loop to schedule delayed worker (bsc#1243051).\n- CVE-2025-37862: HID: pidff: Fix null pointer dereference in pidff_find_fields (bsc#1242982).\n- CVE-2025-37865: net: dsa: mv88e6xxx: fix -ENOENT when deleting VLANs and MST is unsupported (bsc#1242954).\n- CVE-2025-37874: net: ngbe: fix memory leak in ngbe_probe() error path (bsc#1242940).\n- CVE-2025-37884: bpf: Fix deadlock between rcu_tasks_trace and event_mutex (bsc#1243060).\n- CVE-2025-37909: net: lan743x: Fix memleak issue when GSO enabled (bsc#1243467).\n- CVE-2025-37917: net: ethernet: mtk-star-emac: fix spinlock recursion issues on rx/tx poll (bsc#1243475).\n- CVE-2025-37921: vxlan: vnifilter: Fix unlocked deletion of default FDB entry (bsc#1243480).\n- CVE-2025-37923: tracing: Fix oob write in trace_seq_to_buffer() (bsc#1243551).\n- CVE-2025-37927: iommu/amd: Fix potential buffer overflow in parse_ivrs_acpihid (bsc#1243620).\n- CVE-2025-37933: octeon_ep: Fix host hang issue during device reboot (bsc#1243628).\n- CVE-2025-37936: perf/x86/intel: KVM: Mask PEBS_ENABLE loaded for guest with vCPU's value (bsc#1243537).\n- CVE-2025-37938: tracing: Verify event formats that have '%*p..' (bsc#1243544).\n- CVE-2025-37945: net: phy: allow MDIO bus PM ops to start/stop state machine for phylink-controlled PHY (bsc#1243538).\n- CVE-2025-37954: smb: client: Avoid race in open_cached_dir with lease breaks (bsc#1243664).\n- CVE-2025-37961: ipvs: fix uninit-value for saddr in do_output_route4 (bsc#1243523).\n- CVE-2025-37967: usb: typec: ucsi: displayport: Fix deadlock (bsc#1243572).\n- CVE-2025-37968: iio: light: opt3001: fix deadlock due to concurrent flag access (bsc#1243571).\n- CVE-2025-37987: pds_core: Prevent possible adminq overflow/stuck condition (bsc#1243542).\n- CVE-2025-37992: net_sched: Flush gso_skb list too during -\u003echange() (bsc#1243698).\n- CVE-2025-37995: module: ensure that kobject_put() is safe for module type kobjects (bsc#1243827).\n- CVE-2025-37997: netfilter: ipset: fix region locking in hash types (bsc#1243832).\n- CVE-2025-37998: openvswitch: Fix unsafe attribute parsing in output_userspace() (bsc#1243836).\n- CVE-2025-38000: sch_hfsc: Fix qlen accounting bug when using peek in hfsc_enqueue() (bsc#1244277).\n- CVE-2025-38001: net_sched: hfsc: Address reentrant enqueue adding class to eltree twice (bsc#1244234).\n- CVE-2025-38011: drm/amdgpu: csa unmap use uninterruptible lock (bsc#1244729).\n- CVE-2025-38018: net/tls: fix kernel panic when alloc_page failed (bsc#1244999).\n- CVE-2025-38053: idpf: fix null-ptr-deref in idpf_features_check (bsc#1244746).\n- CVE-2025-38055: perf/x86/intel: Fix segfault with PEBS-via-PT with sample_freq (bsc#1244747).\n- CVE-2025-38057: espintcp: fix skb leaks (bsc#1244862).\n- CVE-2025-38060: bpf: abort verification if env-\u003ecur_state-\u003eloop_entry != NULL (bsc#1245155).\n- CVE-2025-38072: libnvdimm/labels: Fix divide error in nd_label_data_init() (bsc#1244743).\n\nThe following non-security bugs were fixed:\n\n- accel/ivpu: Improve buffer object logging (git-fixes).\n- accel/ivpu: Use dma_resv_lock() instead of a custom mutex (git-fixes).\n- accel/qaic: Mask out SR-IOV PCI resources (stable-fixes).\n- acpi-cpufreq: Fix nominal_freq units to KHz in get_max_boost_ratio() (git-fixes).\n- ACPI: Add missing prototype for non CONFIG_SUSPEND/CONFIG_X86 case (stable-fixes).\n- ACPI: battery: negate current when discharging (stable-fixes).\n- ACPI: bus: Bail out if acpi_kobj registration fails (stable-fixes).\n- ACPI: CPPC: Fix NULL pointer dereference when nosmp is used (git-fixes).\n- ACPI: HED: Always initialize before evged (stable-fixes).\n- ACPI: OSI: Stop advertising support for '3.0 _SCP Extensions' (git-fixes).\n- ACPI: PNP: Add Intel OC Watchdog IDs to non-PNP device list (stable-fixes).\n- ACPICA: Avoid sequence overread in call to strncmp() (stable-fixes).\n- ACPICA: exserial: do not forget to handle FFixedHW opregions for reading (git-fixes).\n- ACPICA: fix acpi operand cache leak in dswstate.c (stable-fixes).\n- ACPICA: fix acpi parse and parseext cache leaks (stable-fixes).\n- ACPICA: utilities: Fix overflow check in vsnprintf() (stable-fixes).\n- ACPICA: Utilities: Fix spelling mistake 'Incremement' -\u003e 'Increment' (git-fixes).\n- ALSA: hda/intel: Add Thinkpad E15 to PM deny list (stable-fixes).\n- ALSA: hda/realtek: Add quirk for HP Spectre x360 15-df1xxx (stable-fixes).\n- ALSA: hda/realtek: Add quirk for Lenovo Yoga Pro 7 14ASP10 (stable-fixes).\n- ALSA: hda/realtek: enable headset mic on Latitude 5420 Rugged (stable-fixes).\n- ALSA: hda/realtek: Enable PC beep passthrough for HP EliteBook 855 G7 (stable-fixes).\n- ALSA: hda/realtek: Fix built-in mic on ASUS VivoBook X507UAR (git-fixes).\n- ALSA: hda/realtek: Fix built-in mic on ASUS VivoBook X513EA (git-fixes).\n- ALSA: pcm: Fix race of buffer access at PCM OSS layer (stable-fixes).\n- ALSA: seq: Improve data consistency at polling (stable-fixes).\n- ALSA: usb-audio: Accept multiple protocols in GTBs (stable-fixes).\n- ALSA: usb-audio: Add a quirk for Lenovo Thinkpad Thunderbolt 3 dock (stable-fixes).\n- ALSA: usb-audio: Add implicit feedback quirk for RODE AI-1 (stable-fixes).\n- ALSA: usb-audio: Add name for HP Engage Go dock (stable-fixes).\n- ALSA: usb-audio: Add Pioneer DJ DJM-V10 support (stable-fixes).\n- ALSA: usb-audio: Check shutdown at endpoint_set_interface() (stable-fixes).\n- ALSA: usb-audio: enable support for Presonus Studio 1824c within 1810c file (stable-fixes).\n- ALSA: usb-audio: Fix duplicated name in MIDI substream names (stable-fixes).\n- ALSA: usb-audio: Fix NULL pointer deref in snd_usb_power_domain_set() (git-fixes).\n- ALSA: usb-audio: Fix out-of-bounds read in snd_usb_get_audioformat_uac3() (git-fixes).\n- ALSA: usb-audio: mixer: Remove temporary string use in parse_clock_source_unit (stable-fixes).\n- ALSA: usb-audio: Rename ALSA kcontrol PCM and PCM1 for the KTMicro sound card (stable-fixes).\n- ALSA: usb-audio: Rename Pioneer mixer channel controls (git-fixes).\n- ALSA: usb-audio: Set MIDI1 flag appropriately for GTB MIDI 1.0 entry (stable-fixes).\n- ALSA: usb-audio: Skip setting clock selector for single connections (stable-fixes).\n- ALSA: usb-audio: Support multiple control interfaces (stable-fixes).\n- ALSA: usb-audio: Support read-only clock selector control (stable-fixes).\n- arm64: dts: marvell: uDPU: define pinctrl state for alarm LEDs (git-fixes)\n- ASoC: amd: yc: Add quirk for Lenovo Yoga Pro 7 14ASP9 (stable-fixes).\n- ASoC: apple: mca: Constrain channels according to TDM mask (git-fixes).\n- ASoC: codecs: hda: Fix RPM usage count underflow (git-fixes).\n- ASoC: codecs: pcm3168a: Allow for 24-bit in provider mode (stable-fixes).\n- ASoC: cs42l43: Disable headphone clamps during type detection (stable-fixes).\n- ASoC: imx-card: Adjust over allocation of memory in imx_card_parse_of() (stable-fixes).\n- ASoC: Intel: avs: Fix deadlock when the failing IPC is SET_D0IX (git-fixes).\n- ASoC: Intel: avs: Verify content returned by parse_int_array() (git-fixes).\n- ASoC: Intel: bytcr_rt5640: Add DMI quirk for Acer Aspire SW3-013 (stable-fixes).\n- ASoC: mediatek: mt6359: Add stub for mt6359_accdet_enable_jack_detect (stable-fixes).\n- ASoC: mediatek: mt8188: Add reference for dmic clocks (stable-fixes).\n- ASoC: mediatek: mt8188: Treat DMIC_GAINx_CUR as non-volatile (stable-fixes).\n- ASoC: mediatek: mt8195: Set ETDM1/2 IN/OUT to COMP_DUMMY() (git-fixes).\n- ASoC: meson: meson-card-utils: use of_property_present() for DT parsing (git-fixes).\n- ASoC: ops: Enforce platform maximum on initial value (stable-fixes).\n- ASoC: qcom: sdm845: Add error handling in sdm845_slim_snd_hw_params() (git-fixes).\n- ASoC: qcom: sm8250: explicitly set format in sm8250_be_hw_params_fixup() (stable-fixes).\n- ASoC: rt722-sdca: Add some missing readable registers (stable-fixes).\n- ASoC: soc-dai: check return value at snd_soc_dai_set_tdm_slot() (stable-fixes).\n- ASoC: SOF: Intel: hda-bus: Use PIO mode on ACE2+ platforms (git-fixes).\n- ASoC: SOF: ipc4-pcm: Adjust pipeline_list-\u003epipelines allocation type (git-fixes).\n- ASoC: sun4i-codec: support hp-det-gpios property (stable-fixes).\n- ASoC: tas2764: Add reg defaults for TAS2764_INT_CLK_CFG (stable-fixes).\n- ASoC: tas2764: Enable main IRQs (git-fixes).\n- ASoC: tas2764: Mark SW_RESET as volatile (stable-fixes).\n- ASoC: tas2764: Power up/down amp on mute ops (stable-fixes).\n- ASoC: tas2764: Reinit cache on part reset (git-fixes).\n- ASoC: tas2770: Power cycle amp on ISENSE/VSENSE change (stable-fixes).\n- ASoC: tegra210_ahub: Add check to of_device_get_match_data() (stable-fixes).\n- ASoC: ti: omap-hdmi: Re-add dai_link-\u003eplatform to fix card init (git-fixes).\n- ata: libata-eh: Do not use ATAPI DMA for a device limited to PIO mode (stable-fixes).\n- ata: pata_via: Force PIO for ATAPI devices on VT6415/VT6330 (stable-fixes).\n- ath10k: snoc: fix unbalanced IRQ enable in crash recovery (git-fixes).\n- backlight: pm8941: Add NULL check in wled_configure() (git-fixes).\n- Bluetooth: btintel_pcie: Fix driver not posting maximum rx buffers (git-fixes).\n- Bluetooth: btintel_pcie: Increase the tx and rx descriptor count (git-fixes).\n- Bluetooth: btintel_pcie: Reduce driver buffer posting to prevent race condition (git-fixes).\n- Bluetooth: btintel: Check dsbr size from EFI variable (git-fixes).\n- Bluetooth: eir: Fix possible crashes on eir_create_adv_data (git-fixes).\n- Bluetooth: Fix NULL pointer deference on eir_get_service_data (git-fixes).\n- Bluetooth: hci_conn: Fix UAF Write in __hci_acl_create_connection_sync (git-fixes).\n- Bluetooth: hci_conn: Only do ACL connections sequentially (stable-fixes).\n- Bluetooth: hci_core: fix list_for_each_entry_rcu usage (git-fixes).\n- Bluetooth: hci_event: Fix not using key encryption size when its known (git-fixes).\n- Bluetooth: hci_qca: move the SoC type check to the right place (git-fixes).\n- Bluetooth: hci_sync: Fix broadcast/PA when using an existing instance (git-fixes).\n- Bluetooth: hci_sync: Fix UAF in hci_acl_create_conn_sync (git-fixes).\n- Bluetooth: hci_sync: Fix UAF on hci_abort_conn_sync (git-fixes).\n- Bluetooth: L2CAP: Fix not responding with L2CAP_CR_LE_ENCRYPTION (git-fixes).\n- Bluetooth: MGMT: Fix sparse errors (git-fixes).\n- Bluetooth: MGMT: Fix UAF on mgmt_remove_adv_monitor_complete (git-fixes).\n- Bluetooth: MGMT: iterate over mesh commands in mgmt_mesh_foreach() (git-fixes).\n- Bluetooth: MGMT: Remove unused mgmt_pending_find_data (stable-fixes).\n- Bluetooth: Remove pending ACL connection attempts (stable-fixes).\n- bnxt: properly flush XDP redirect lists (git-fixes).\n- bpf: Force uprobe bpf program to always return 0 (git-fixes).\n- btrfs: fix fsync of files with no hard links not persisting deletion (git-fixes).\n- btrfs: fix invalid data space release when truncating block in NOCOW mode (git-fixes).\n- btrfs: fix qgroup reservation leak on failure to allocate ordered extent (git-fixes).\n- btrfs: fix wrong start offset for delalloc space release during mmap write (git-fixes).\n- btrfs: remove end_no_trans label from btrfs_log_inode_parent() (git-fixes).\n- btrfs: simplify condition for logging new dentries at btrfs_log_inode_parent() (git-fixes).\n- bus: fsl-mc: do not add a device-link for the UAPI used DPMCP device (git-fixes).\n- bus: fsl-mc: fix double-free on mc_dev (git-fixes).\n- bus: fsl-mc: fix GET/SET_TAILDROP command ids (git-fixes).\n- bus: fsl-mc: increase MC_CMD_COMPLETION_TIMEOUT_MS value (stable-fixes).\n- bus: mhi: host: Fix conflict between power_up and SYSERR (git-fixes).\n- calipso: Fix null-ptr-deref in calipso_req_{set,del}attr() (git-fixes).\n- can: c_can: Use of_property_present() to test existence of DT property (stable-fixes).\n- can: tcan4x5x: fix power regulator retrieval during probe (git-fixes).\n- ceph: allocate sparse_ext map only for sparse reads (git-fixes).\n- ceph: Fix incorrect flush end position calculation (git-fixes).\n- ceph: fix memory leaks in __ceph_sync_read() (git-fixes).\n- cgroup/cpuset: Do not allow creation of local partition over a remote one (bsc#1241166).\n- cgroup/cpuset: Fix race between newly created partition and dying one (bsc#1241166).\n- cifs: change tcon status when need_reconnect is set on it (git-fixes).\n- clocksource: Fix brown-bag boolean thinko in (git-fixes)\n- clocksource: Make watchdog and suspend-timing multiplication (git-fixes)\n- crypto: lrw - Only add ecb if it is not already there (git-fixes).\n- crypto: lzo - Fix compression buffer overrun (stable-fixes).\n- crypto: marvell/cesa - Avoid empty transfer descriptor (git-fixes).\n- crypto: marvell/cesa - Do not chain submitted requests (git-fixes).\n- crypto: marvell/cesa - Handle zero-length skcipher requests (git-fixes).\n- crypto: octeontx2 - suppress auth failure screaming due to negative tests (stable-fixes).\n- crypto: qat - add shutdown handler to qat_420xx (git-fixes).\n- crypto: qat - add shutdown handler to qat_4xxx (git-fixes).\n- crypto: skcipher - Zap type in crypto_alloc_sync_skcipher (stable-fixes).\n- crypto: sun8i-ce - move fallback ahash_request to the end of the struct (git-fixes).\n- crypto: sun8i-ce-cipher - fix error handling in sun8i_ce_cipher_prepare() (git-fixes).\n- crypto: sun8i-ss - do not use sg_dma_len before calling DMA functions (git-fixes).\n- crypto: xts - Only add ecb if it is not already there (git-fixes).\n- devlink: fix port dump cmd type (git-fixes).\n- devlink: Fix referring to hw_addr attribute during state validation (git-fixes).\n- dlm: mask sk_shutdown value (bsc#1228854).\n- dlm: use SHUT_RDWR for SCTP shutdown (bsc#1228854).\n- dmaengine: idxd: cdev: Fix uninitialized use of sva in idxd_cdev_open (stable-fixes).\n- dmaengine: ti: Add NULL check in udma_probe() (git-fixes).\n- drivers/rapidio/rio_cm.c: prevent possible heap overwrite (stable-fixes).\n- drm: Add valid clones check (stable-fixes).\n- drm: bridge: adv7511: fill stream capabilities (stable-fixes).\n- drm: rcar-du: Fix memory leak in rcar_du_vsps_init() (git-fixes).\n- drm/amd: Adjust output for discovery error handling (git-fixes).\n- drm/amd/display: Add debugging message for brightness caps (bsc#1240650).\n- drm/amd/display: Add null pointer check for get_first_active_display() (git-fixes).\n- drm/amd/display: Add support for disconnected eDP streams (stable-fixes).\n- drm/amd/display: calculate the remain segments for all pipes (stable-fixes).\n- drm/amd/display: Call FP Protect Before Mode Programming/Mode Support (stable-fixes).\n- drm/amd/display: check stream id dml21 wrapper to get plane_id (stable-fixes).\n- drm/amd/display: Configure DTBCLK_P with OPTC only for dcn401 (stable-fixes).\n- drm/amd/display: Correct timing_adjust_pending flag setting (stable-fixes).\n- drm/amd/display: Defer BW-optimization-blocked DRR adjustments (git-fixes).\n- drm/amd/display: Do not enable replay when vtotal update is pending (stable-fixes).\n- drm/amd/display: Do not treat wb connector as physical in create_validate_stream_for_sink (stable-fixes).\n- drm/amd/display: Do not try AUX transactions on disconnected link (stable-fixes).\n- drm/amd/display: Ensure DMCUB idle before reset on DCN31/DCN35 (stable-fixes).\n- drm/amd/display: Fix BT2020 YCbCr limited/full range input (stable-fixes).\n- drm/amd/display: fix dcn4x init failed (stable-fixes).\n- drm/amd/display: Fix default DC and AC levels (bsc#1240650).\n- drm/amd/display: Fix DMUB reset sequence for DCN401 (stable-fixes).\n- drm/amd/display: Fix incorrect DPCD configs while Replay/PSR switch (stable-fixes).\n- drm/amd/display: fix link_set_dpms_off multi-display MST corner case (stable-fixes).\n- drm/amd/display: Fix p-state type when p-state is unsupported (stable-fixes).\n- drm/amd/display: Guard against setting dispclk low for dcn31x (stable-fixes).\n- drm/amd/display: Guard against setting dispclk low when active (stable-fixes).\n- drm/amd/display: handle max_downscale_src_width fail check (stable-fixes).\n- drm/amd/display: Increase block_sequence array size (stable-fixes).\n- drm/amd/display: Initial psr_version with correct setting (stable-fixes).\n- drm/amd/display: not abort link train when bw is low (stable-fixes).\n- drm/amd/display: pass calculated dram_speed_mts to dml2 (stable-fixes).\n- drm/amd/display: Populate register address for dentist for dcn401 (stable-fixes).\n- drm/amd/display: Read LTTPR ALPM caps during link cap retrieval (stable-fixes).\n- drm/amd/display: remove minimum Dispclk and apply oem panel timing (stable-fixes).\n- drm/amd/display: Request HW cursor on DCN3.2 with SubVP (stable-fixes).\n- drm/amd/display: Skip checking FRL_MODE bit for PCON BW determination (stable-fixes).\n- drm/amd/display: Support multiple options during psr entry (stable-fixes).\n- drm/amd/display: Update CR AUX RD interval interpretation (stable-fixes).\n- drm/amd/display: Use Nominal vBlank If Provided Instead Of Capping It (stable-fixes).\n- drm/amd/display/dm: drop hw_support check in amdgpu_dm_i2c_xfer() (stable-fixes).\n- drm/amd/pm: Fetch current power limit from PMFW (stable-fixes).\n- drm/amd/pm: Skip P2S load for SMU v13.0.12 (stable-fixes).\n- drm/amd/pp: Fix potential NULL pointer dereference in atomctrl_initialize_mc_reg_table (git-fixes).\n- drm/amdgpu: adjust drm_firmware_drivers_only() handling (stable-fixes).\n- drm/amdgpu: Allow P2P access through XGMI (stable-fixes).\n- drm/amdgpu: Do not program AGP BAR regs under SRIOV in gfxhub_v1_0.c (stable-fixes).\n- drm/amdgpu: enlarge the VBIOS binary size limit (stable-fixes).\n- drm/amdgpu: Fix missing drain retry fault the last entry (stable-fixes).\n- drm/amdgpu: Fix the race condition for draining retry fault (stable-fixes).\n- drm/amdgpu: read back register after written for VCN v4.0.5 (stable-fixes).\n- drm/amdgpu: release xcp_mgr on exit (stable-fixes).\n- drm/amdgpu: remove all KFD fences from the BO on release (stable-fixes).\n- drm/amdgpu: reset psp-\u003ecmd to NULL after releasing the buffer (stable-fixes).\n- drm/amdgpu: Set snoop bit for SDMA for MI series (stable-fixes).\n- drm/amdgpu: Skip pcie_replay_count sysfs creation for VF (stable-fixes).\n- drm/amdgpu: switch job hw_fence to amdgpu_fence (git-fixes).\n- drm/amdgpu: Update SRIOV video codec caps (stable-fixes).\n- drm/amdgpu: Use active umc info from discovery (stable-fixes).\n- drm/amdgpu/discovery: check ip_discovery fw file available (stable-fixes).\n- drm/amdgpu/gfx11: do not read registers in mqd init (stable-fixes).\n- drm/amdgpu/gfx12: do not read registers in mqd init (stable-fixes).\n- drm/amdgpu/mes11: fix set_hw_resources_1 calculation (stable-fixes).\n- drm/amdkfd: Correct F8_MODE for gfx950 (git-fixes).\n- drm/amdkfd: fix missing L2 cache info in topology (stable-fixes).\n- drm/amdkfd: KFD release_work possible circular locking (stable-fixes).\n- drm/amdkfd: Set per-process flags only once cik/vi (stable-fixes).\n- drm/amdkfd: Set per-process flags only once for gfx9/10/11/12 (stable-fixes).\n- drm/amdkfd: set precise mem ops caps to disabled for gfx 11 and 12 (stable-fixes).\n- drm/ast: Find VBIOS mode from regular display size (stable-fixes).\n- drm/ast: Fix comment on modeset lock (git-fixes).\n- drm/atomic: clarify the rules around drm_atomic_state-\u003eallow_modeset (stable-fixes).\n- drm/bridge: cdns-dsi: Check return value when getting default PHY config (git-fixes).\n- drm/bridge: cdns-dsi: Fix connecting to next bridge (git-fixes).\n- drm/bridge: cdns-dsi: Fix phy de-init and flag it so (git-fixes).\n- drm/bridge: cdns-dsi: Fix the clock variable for mode_valid() (git-fixes).\n- drm/bridge: cdns-dsi: Wait for Clk and Data Lanes to be ready (git-fixes).\n- drm/bridge: lt9611uxc: Fix an error handling path in lt9611uxc_probe() (git-fixes).\n- drm/buddy: fix issue that force_merge cannot free all roots (stable-fixes).\n- drm/etnaviv: Protect the scheduler's pending list with its lock (git-fixes).\n- drm/i915: fix build error some more (git-fixes).\n- drm/i915/gem: Allow EXEC_CAPTURE on recoverable contexts on DG1 (git-fixes).\n- drm/i915/guc: Check if expecting reply before decrementing outstanding_submission_g2h (git-fixes).\n- drm/i915/guc: Handle race condition where wakeref count drops below 0 (git-fixes).\n- drm/i915/pmu: Fix build error with GCOV and AutoFDO enabled (git-fixes).\n- drm/i915/psr: Fix using wrong mask in REG_FIELD_PREP (git-fixes).\n- drm/mediatek: Fix kobject put for component sub-drivers (git-fixes).\n- drm/mediatek: mtk_dpi: Add checks for reg_h_fre_con existence (stable-fixes).\n- drm/mediatek: mtk_drm_drv: Fix kobject put for mtk_mutex device ptr (git-fixes).\n- drm/mediatek: mtk_drm_drv: Unbind secondary mmsys components on err (git-fixes).\n- drm/msm: Fix CP_RESET_CONTEXT_STATE bitfield names (git-fixes).\n- drm/msm/a6xx: Disable rgb565_predicator on Adreno 7c3 (git-fixes).\n- drm/msm/a7xx: Call CP_RESET_CONTEXT_STATE (git-fixes).\n- drm/msm/disp: Correct porch timing for SDM845 (git-fixes).\n- drm/msm/dpu: Clear CTL_FETCH_PIPE_ACTIVE before blend setup (git-fixes).\n- drm/msm/dpu: Clear CTL_FETCH_PIPE_ACTIVE on ctl_path reset (git-fixes).\n- drm/msm/dpu: enable SmartDMA on SC8180X (git-fixes).\n- drm/msm/dpu: enable SmartDMA on SM8150 (git-fixes).\n- drm/msm/dsi/dsi_phy_10nm: Fix missing initial VCO rate (git-fixes).\n- drm/msm/gpu: Fix crash when throttling GPU immediately during boot (git-fixes).\n- drm/nouveau: fix the broken marco GSP_MSG_MAX_SIZE (stable-fixes).\n- drm/nouveau/bl: increase buffer size to avoid truncate warning (git-fixes).\n- drm/panel-edp: Add Starry 116KHD024006 (stable-fixes).\n- drm/panel-simple: fix the warnings for the Evervision VGG644804 (git-fixes).\n- drm/panel: samsung-sofef00: Drop s6e3fc2x01 support (git-fixes).\n- drm/panic: add missing space (git-fixes).\n- drm/panthor: Fix GPU_COHERENCY_ACE[_LITE] definitions (git-fixes).\n- drm/panthor: Update panthor_mmu::irq::mask when needed (git-fixes).\n- drm/rockchip: vop2: Add uv swap for cluster window (stable-fixes).\n- drm/rockchip: vop2: Improve display modes handling on RK3588 HDMI0 (stable-fixes).\n- drm/ssd130x: fix ssd132x_clear_screen() columns (git-fixes).\n- drm/tegra: Assign plane type before registration (git-fixes).\n- drm/tegra: Fix a possible null pointer dereference (git-fixes).\n- drm/tegra: rgb: Fix the unbound reference count (git-fixes).\n- drm/udl: Unregister device before cleaning up on disconnect (git-fixes).\n- drm/v3d: Add clock handling (stable-fixes).\n- drm/v3d: Avoid NULL pointer dereference in `v3d_job_update_stats()` (stable-fixes).\n- drm/vc4: tests: Use return instead of assert (git-fixes).\n- drm/vkms: Adjust vkms_state-\u003eactive_planes allocation type (git-fixes).\n- drm/vmwgfx: Add error path for xa_store in vmw_bo_add_detached_resource (git-fixes).\n- drm/vmwgfx: Add seqno waiter for sync_files (git-fixes).\n- drm/vmwgfx: Fix dumb buffer leak (git-fixes).\n- drm/xe: Create LRC BO without VM (git-fixes).\n- drm/xe: Do not attempt to bootstrap VF in execlists mode (stable-fixes).\n- drm/xe: Fix memset on iomem (git-fixes).\n- drm/xe: Fix xe_tile_init_noalloc() error propagation (stable-fixes).\n- drm/xe: Make xe_gt_freq part of the Documentation (git-fixes).\n- drm/xe: Move suballocator init to after display init (stable-fixes).\n- drm/xe: Nuke VM's mapping upon close (stable-fixes).\n- drm/xe: Process deferred GGTT node removals on device unwind (git-fixes).\n- drm/xe: Reject BO eviction if BO is bound to current VM (stable-fixes).\n- drm/xe: remove unmatched xe_vm_unlock() from __xe_exec_queue_init() (git-fixes).\n- drm/xe: Retry BO allocation (stable-fixes).\n- drm/xe: Rework eviction rejection of bound external bos (git-fixes).\n- drm/xe: Save the gt pointer in lrc and drop the tile (stable-fixes).\n- drm/xe: Stop ignoring errors from xe_ttm_stolen_mgr_init() (stable-fixes).\n- drm/xe: Wire up device shutdown handler (stable-fixes).\n- drm/xe: xe_gen_wa_oob: replace program_invocation_short_name (stable-fixes).\n- drm/xe/bmg: Update Wa_16023588340 (git-fixes).\n- drm/xe/d3cold: Set power state to D3Cold during s2idle/s3 (git-fixes).\n- drm/xe/debugfs: Add missing xe_pm_runtime_put in wedge_mode_set (stable-fixes).\n- drm/xe/debugfs: fixed the return value of wedged_mode_set (stable-fixes).\n- drm/xe/display: Add check for alloc_ordered_workqueue() (git-fixes).\n- drm/xe/gt: Update handling of xe_force_wake_get return (stable-fixes).\n- drm/xe/oa: Ensure that polled read returns latest data (stable-fixes).\n- drm/xe/pf: Create a link between PF and VF devices (stable-fixes).\n- drm/xe/pf: Reset GuC VF config when unprovisioning critical resource (stable-fixes).\n- drm/xe/relay: Do not use GFP_KERNEL for new transactions (stable-fixes).\n- drm/xe/sa: Always call drm_suballoc_manager_fini() (stable-fixes).\n- drm/xe/sched: stop re-submitting signalled jobs (git-fixes).\n- drm/xe/vf: Retry sending MMIO request to GUC on timeout error (stable-fixes).\n- drm/xe/vm: move rebind_work init earlier (git-fixes).\n- drm/xe/xe2hpg: Add Wa_22021007897 (stable-fixes).\n- dummycon: Trigger redraw when switching consoles with deferred takeover (git-fixes).\n- e1000e: set fixed clock frequency indication for Nahum 11 and Nahum 13 (git-fixes).\n- efi/libstub: Describe missing 'out' parameter in efi_load_initrd (git-fixes).\n- fbcon: Make sure modelist not set on unregistered console (stable-fixes).\n- fbcon: Use correct erase colour for clearing in fbcon (stable-fixes).\n- fbdev: core: fbcvt: avoid division by 0 in fb_cvt_hperiod() (git-fixes).\n- fbdev: core: tileblit: Implement missing margin clearing for tileblit (stable-fixes).\n- fbdev: Fix do_register_framebuffer to prevent null-ptr-deref in fb_videomode_to_var (git-fixes).\n- fbdev: Fix fb_set_var to prevent null-ptr-deref in fb_videomode_to_var (git-fixes).\n- fbdev: fsl-diu-fb: add missing device_remove_file() (stable-fixes).\n- fbdev/efifb: Remove PM for parent device (bsc#1244261).\n- fgraph: Still initialize idle shadow stacks when starting (git-fixes).\n- firmware: arm_ffa: Reject higher major version as incompatible (stable-fixes).\n- firmware: arm_ffa: Set dma_mask for ffa devices (stable-fixes).\n- firmware: arm_scmi: Relax duplicate name constraint across protocol ids (stable-fixes).\n- firmware: psci: Fix refcount leak in psci_dt_init (git-fixes).\n- firmware: SDEI: Allow sdei initialization without ACPI_APEI_GHES (git-fixes).\n- fpga: altera-cvp: Increase credit timeout (stable-fixes).\n- fs/nfs/read: fix double-unlock bug in nfs_return_empty_folio() (git-fixes).\n- gpio: mlxbf3: only get IRQ for device instance 0 (git-fixes).\n- gpio: pca953x: fix IRQ storm on system wake up (git-fixes).\n- gpio: pca953x: Simplify code with cleanup helpers (stable-fixes).\n- gpio: pca953x: Split pca953x_restore_context() and pca953x_save_context() (stable-fixes).\n- gpiolib: Revert 'Do not WARN on gpiod_put() for optional GPIO' (stable-fixes).\n- gve: add missing NULL check for gve_alloc_pending_packet() in TX DQO (git-fixes).\n- gve: Fix RX_BUFFERS_POSTED stat to report per-queue fill_cnt (git-fixes).\n- HID: lenovo: Restrict F7/9/11 mode to compact keyboards only (git-fixes).\n- HID: quirks: Add ADATA XPG alpha wireless mouse support (stable-fixes).\n- HID: usbkbd: Fix the bit shift number for LED_KANA (stable-fixes).\n- HID: wacom: fix kobject reference count leak (git-fixes).\n- HID: wacom: fix memory leak on kobject creation failure (git-fixes).\n- HID: wacom: fix memory leak on sysfs attribute creation failure (git-fixes).\n- hwmon: (asus-ec-sensors) check sensor index in read_string() (git-fixes).\n- hwmon: (dell-smm) Increment the number of fans (stable-fixes).\n- hwmon: (ftsteutates) Fix TOCTOU race in fts_read() (git-fixes).\n- hwmon: (gpio-fan) Add missing mutex locks (stable-fixes).\n- hwmon: (nct6775): Actually make use of the HWMON_NCT6775 symbol namespace (git-fixes).\n- hwmon: (occ) fix unaligned accesses (git-fixes).\n- hwmon: (occ) Rework attribute registration for stack usage (git-fixes).\n- hwmon: (peci/dimmtemp) Do not provide fake thresholds data (git-fixes).\n- hwmon: (xgene-hwmon) use appropriate type for the latency value (stable-fixes).\n- hwmon: corsair-psu: add USB id of HX1200i Series 2023 psu (git-fixes).\n- i2c: designware: Invoke runtime suspend on quick slave re-registration (stable-fixes).\n- i2c: npcm: Add clock toggle recovery (stable-fixes).\n- i2c: pxa: fix call balance of i2c-\u003eclk handling routines (stable-fixes).\n- i2c: qup: Vote for interconnect bandwidth to DRAM (stable-fixes).\n- i2c: robotfuzz-osif: disable zero-length read messages (git-fixes).\n- i2c: tegra: check msg length in SMBUS block read (bsc#1242086)\n- i2c: tiny-usb: disable zero-length read messages (git-fixes).\n- i3c: master: svc: Fix implicit fallthrough in svc_i3c_master_ibi_work() (git-fixes).\n- i3c: master: svc: Fix missing STOP for master request (stable-fixes).\n- i3c: master: svc: Flush FIFO before sending Dynamic Address Assignment(DAA) (stable-fixes).\n- i40e: retry VFLR handling if there is ongoing VF reset (git-fixes).\n- i40e: return false from i40e_reset_vf if reset is in progress (git-fixes).\n- IB/cm: Drop lockdep assert and WARN when freeing old msg (git-fixes)\n- ice: create new Tx scheduler nodes for new queues only (git-fixes).\n- ice: Fix LACP bonds without SRIOV environment (git-fixes).\n- ice: fix rebuilding the Tx scheduler tree for large queue counts (git-fixes).\n- ice: fix Tx scheduler error handling in XDP callback (git-fixes).\n- ice: fix vf-\u003enum_mac count with port representors (git-fixes).\n- ieee802154: ca8210: Use proper setters and getters for bitwise types (stable-fixes).\n- iio: accel: fxls8962af: Fix temperature scan element sign (git-fixes).\n- iio: adc: ad7124: Fix 3dB filter frequency reading (git-fixes).\n- iio: adc: ad7606_spi: fix reg write value mask (git-fixes).\n- iio: filter: admv8818: fix band 4, state 15 (git-fixes).\n- iio: filter: admv8818: fix integer overflow (git-fixes).\n- iio: filter: admv8818: fix range calculation (git-fixes).\n- iio: filter: admv8818: Support frequencies \u003e= 2^32 (git-fixes).\n- iio: imu: inv_icm42600: Fix temperature calculation (git-fixes).\n- ima: process_measurement() needlessly takes inode_lock() on MAY_READ (stable-fixes).\n- ima: Suspend PCR extends and log appends when rebooting (bsc#1210025 ltc#196650).\n- Input: gpio-keys - fix possible concurrent access in gpio_keys_irq_timer() (git-fixes).\n- Input: ims-pcu - check record size in ims_pcu_flash_firmware() (git-fixes).\n- Input: sparcspkr - avoid unannotated fall-through (stable-fixes).\n- Input: xpad - add more controllers (stable-fixes).\n- intel_th: avoid using deprecated page-\u003emapping, index fields (stable-fixes).\n- iommu: Protect against overflow in iommu_pgsize() (git-fixes).\n- iommu: Skip PASID validation for devices without PASID capability (bsc#1244100)\n- iommu: Validate the PASID in iommu_attach_device_pasid() (bsc#1244100)\n- ip_tunnel: annotate data-races around t-\u003eparms.link (git-fixes).\n- ip6mr: fix tables suspicious RCU usage (git-fixes).\n- ipmr: fix incorrect parameter validation in the ip_mroute_getsockopt() function (git-fixes).\n- ipmr: fix tables suspicious RCU usage (git-fixes).\n- ipv4: Convert ip_route_input() to dscp_t (git-fixes).\n- ipv4: Correct/silence an endian warning in __ip_do_redirect (git-fixes).\n- ipv6: save dontfrag in cork (git-fixes).\n- ipvs: Always clear ipvs_property flag in skb_scrub_packet() (git-fixes).\n- isolcpus: fix bug in returning number of allocated cpumask (bsc#1243774).\n- jffs2: check jffs2_prealloc_raw_node_refs() result in few other places (git-fixes).\n- jffs2: check that raw node were preallocated before writing summary (git-fixes).\n- KVM: powerpc: Enable commented out BUILD_BUG_ON() assertion (bsc#1215199).\n- KVM: s390: rename PROT_NONE to PROT_TYPE_DUMMY (git-fixes bsc#1245225).\n- leds: pwm-multicolor: Add check for fwnode_property_read_u32 (stable-fixes).\n- loop: add file_start_write() and file_end_write() (git-fixes).\n- loop: Add sanity check for read/write_iter (git-fixes).\n- mailbox: use error ret code of of_parse_phandle_with_args() (stable-fixes).\n- md/raid1,raid10: do not handle IO error for REQ_RAHEAD and REQ_NOWAIT (git-fixes).\n- md/raid1: Add check for missing source disk in process_checks() (git-fixes).\n- media: adv7180: Disable test-pattern control on adv7180 (stable-fixes).\n- media: c8sectpfe: Call of_node_put(i2c_bus) only once in c8sectpfe_probe() (stable-fixes).\n- media: ccs-pll: Check for too high VT PLL multiplier in dual PLL case (git-fixes).\n- media: ccs-pll: Correct the upper limit of maximum op_pre_pll_clk_div (git-fixes).\n- media: ccs-pll: Start OP pre-PLL multiplier search from correct value (git-fixes).\n- media: ccs-pll: Start VT pre-PLL multiplier search from correct value (git-fixes).\n- media: cx231xx: set device_caps for 417 (stable-fixes).\n- media: cxusb: no longer judge rbuf when the write fails (git-fixes).\n- media: davinci: vpif: Fix memory leak in probe error path (git-fixes).\n- media: gspca: Add error handling for stv06xx_read_sensor() (git-fixes).\n- media: i2c: imx219: Correct the minimum vblanking value (stable-fixes).\n- media: imx-jpeg: Cleanup after an allocation error (git-fixes).\n- media: imx-jpeg: Drop the first error frames (git-fixes).\n- media: imx-jpeg: Move mxc_jpeg_free_slot_data() ahead (git-fixes).\n- media: imx-jpeg: Reset slot data pointers when freed (git-fixes).\n- media: intel/ipu6: Fix dma mask for non-secure mode (git-fixes).\n- media: ipu6: Remove workaround for Meteor Lake ES2 (git-fixes).\n- media: nxp: imx8-isi: better handle the m2m usage_count (git-fixes).\n- media: omap3isp: use sgtable-based scatterlist wrappers (git-fixes).\n- media: ov2740: Move pm-runtime cleanup on probe-errors to proper place (git-fixes).\n- media: ov5675: suppress probe deferral errors (git-fixes).\n- media: ov8856: suppress probe deferral errors (git-fixes).\n- media: platform: mtk-mdp3: Remove unused mdp_get_plat_device (git-fixes).\n- media: qcom: camss: csid: Only add TPG v4l2 ctrl if TPG hardware is available (stable-fixes).\n- media: rkvdec: Fix frame size enumeration (git-fixes).\n- media: tc358746: improve calculation of the D-PHY timing registers (stable-fixes).\n- media: test-drivers: vivid: do not call schedule in loop (stable-fixes).\n- media: uvcvideo: Add sanity check to uvc_ioctl_xu_ctrl_map (stable-fixes).\n- media: uvcvideo: Fix deferred probing error (git-fixes).\n- media: uvcvideo: Handle uvc menu translation inside uvc_get_le_value (stable-fixes).\n- media: uvcvideo: Return the number of processed controls (git-fixes).\n- media: v4l: Memset argument to 0 before calling get_mbus_config pad op (stable-fixes).\n- media: v4l2-dev: fix error handling in __video_register_device() (git-fixes).\n- media: venus: Fix probe error handling (git-fixes).\n- media: verisilicon: Free post processor buffers on error (git-fixes).\n- media: videobuf2: use sgtable-based scatterlist wrappers (git-fixes).\n- media: vidtv: Terminating the subsequent process of initialization failure (git-fixes).\n- media: vivid: Change the siize of the composing (git-fixes).\n- mfd: exynos-lpass: Avoid calling exynos_lpass_disable() twice in exynos_lpass_remove() (git-fixes).\n- mfd: stmpe-spi: Correct the name used in MODULE_DEVICE_TABLE (git-fixes).\n- mfd: tps65219: Remove TPS65219_REG_TI_DEV_ID check (stable-fixes).\n- mm, memcg: cg2 memory{.swap,}.peak write handlers (jsc#PED-12551).\n- mm/hugetlb: fix huge_pmd_unshare() vs GUP-fast race (bsc#1245431).\n- mm/hugetlb: unshare page tables during VMA split, not before (bsc#1245431).\n- mm/memcontrol: export memcg.swap watermark via sysfs for v2 memcg (jsc#PED-12551).\n- mmc: Add quirk to disable DDR50 tuning (stable-fixes).\n- mmc: dw_mmc: add exynos7870 DW MMC support (stable-fixes).\n- mmc: host: Wait for Vdd to settle on card power off (stable-fixes).\n- mmc: sdhci: Disable SD card clock before changing parameters (stable-fixes).\n- mtd: nand: ecc-mxic: Fix use of uninitialized variable ret (git-fixes).\n- mtd: nand: sunxi: Add randomizer configuration before randomizer enable (git-fixes).\n- mtd: rawnand: sunxi: Add randomizer configuration in sunxi_nfc_hw_ecc_write_chunk (git-fixes).\n- neighbour: Do not let neigh_forced_gc() disable preemption for long (git-fixes).\n- net_sched: ets: fix a race in ets_qdisc_change() (git-fixes).\n- net_sched: prio: fix a race in prio_tune() (git-fixes).\n- net_sched: red: fix a race in __red_change() (git-fixes).\n- net_sched: sch_fifo: implement lockless __fifo_dump() (bsc#1237312)\n- net_sched: sch_sfq: reject invalid perturb period (git-fixes).\n- net_sched: sch_sfq: use a temporary work area for validating configuration (bsc#1232504)\n- net_sched: tbf: fix a race in tbf_change() (git-fixes).\n- net: add rcu safety to rtnl_prop_list_size() (git-fixes).\n- net: Fix TOCTOU issue in sk_is_readable() (git-fixes).\n- net: fix udp gso skb_segment after pull from frag_list (git-fixes).\n- net: give more chances to rcu in netdev_wait_allrefs_any() (git-fixes).\n- net: ice: Perform accurate aRFS flow match (git-fixes).\n- net: Implement missing getsockopt(SO_TIMESTAMPING_NEW) (git-fixes).\n- net: ipv4: fix a memleak in ip_setup_cork (git-fixes).\n- net: linkwatch: use system_unbound_wq (git-fixes).\n- net: mana: Add support for Multi Vports on Bare metal (bsc#1244229).\n- net: mana: Record doorbell physical address in PF mode (bsc#1244229).\n- net: page_pool: fix warning code (git-fixes).\n- net: phy: clear phydev-\u003edevlink when the link is deleted (git-fixes).\n- net: phy: fix up const issues in to_mdio_device() and to_phy_device() (git-fixes).\n- net: phy: move phy_link_change() prior to mdio_bus_phy_may_suspend() (bsc#1243538)\n- net: phy: mscc: Fix memory leak when using one step timestamping (git-fixes).\n- net: phy: mscc: Stop clearing the the UDPv4 checksum for L2 frames (git-fixes).\n- net: sched: cls_u32: Fix allocation size in u32_init() (git-fixes).\n- net: sched: consistently use rcu_replace_pointer() in taprio_change() (git-fixes).\n- net: sched: em_text: fix possible memory leak in em_text_destroy() (git-fixes).\n- net: sched: fix erspan_opt settings in cls_flower (git-fixes).\n- net: usb: aqc111: debug info before sanitation (git-fixes).\n- net: usb: aqc111: fix error handling of usbnet read calls (git-fixes).\n- net: wwan: t7xx: Fix napi rx poll issue (git-fixes).\n- net/mdiobus: Fix potential out-of-bounds clause 45 read/write access (git-fixes).\n- net/mdiobus: Fix potential out-of-bounds read/write access (git-fixes).\n- net/mlx4_en: Prevent potential integer overflow calculating Hz (git-fixes).\n- net/mlx5_core: Add error handling inmlx5_query_nic_vport_qkey_viol_cntr() (git-fixes).\n- net/mlx5: Add error handling in mlx5_query_nic_vport_node_guid() (git-fixes).\n- net/mlx5: Ensure fw pages are always allocated on same NUMA (git-fixes).\n- net/mlx5: Fix ECVF vports unload on shutdown flow (git-fixes).\n- net/mlx5: Fix return value when searching for existing flow group (git-fixes).\n- net/mlx5e: Fix leak of Geneve TLV option object (git-fixes).\n- net/neighbor: clear error in case strict check is not set (git-fixes).\n- net/sched: fix use-after-free in taprio_dev_notifier (git-fixes).\n- netdev-genl: Hold rcu_read_lock in napi_get (git-fixes).\n- netlink: fix potential sleeping issue in mqueue_flush_file (git-fixes).\n- netlink: specs: dpll: replace underscores with dashes in names (git-fixes).\n- netpoll: hold rcu read lock in __netpoll_send_skb() (git-fixes).\n- netpoll: Use rcu_access_pointer() in __netpoll_setup (git-fixes).\n- NFC: nci: uart: Set tty-\u003edisc_data only in success path (git-fixes).\n- NFS: Do not allow waiting for exiting tasks (git-fixes).\n- nfsd: Initialize ssc before laundromat_work to prevent NULL dereference (git-fixes).\n- nfsd: Insulate nfsd4_encode_read_plus() from page boundaries in the encode buffer (git-fixes).\n- nfsd: nfsd4_spo_must_allow() must check this is a v4 compound request (git-fixes).\n- nfsd: validate the nfsd_serv pointer before calling svc_wake_up (git-fixes).\n- NFSv4: Check for delegation validity in nfs_start_delegation_return_locked() (git-fixes).\n- NFSv4: Treat ENETUNREACH errors as fatal for state recovery (git-fixes).\n- ntp: Clamp maxerror and esterror to operating range (git-fixes)\n- ntp: Remove invalid cast in time offset math (git-fixes)\n- ntp: Safeguard against time_constant overflow (git-fixes)\n- nvme-fc: do not reference lsrsp after failure (bsc#1245193).\n- nvme-pci: add NVME_QUIRK_NO_DEEPEST_PS quirk for SOLIDIGM P44 Pro (git-fixes).\n- nvme-pci: add quirks for device 126f:1001 (git-fixes).\n- nvme-pci: add quirks for WDC Blue SN550 15b7:5009 (git-fixes).\n- nvme: always punt polled uring_cmd end_io work to task_work (git-fixes).\n- nvme: fix command limits status code (git-fixes).\n- nvme: fix implicit bool to flags conversion (git-fixes).\n- nvmet-fc: free pending reqs on tgtport unregister (bsc#1245193).\n- nvmet-fc: take tgtport refs for portentry (bsc#1245193).\n- nvmet-fcloop: access fcpreq only when holding reqlock (bsc#1245193).\n- nvmet-fcloop: add missing fcloop_callback_host_done (bsc#1245193).\n- nvmet-fcloop: allocate/free fcloop_lsreq directly (bsc#1245193).\n- nvmet-fcloop: do not wait for lport cleanup (bsc#1245193).\n- nvmet-fcloop: drop response if targetport is gone (bsc#1245193).\n- nvmet-fcloop: prevent double port deletion (bsc#1245193).\n- nvmet-fcloop: refactor fcloop_delete_local_port (bsc#1245193).\n- nvmet-fcloop: refactor fcloop_nport_alloc and track lport (bsc#1245193).\n- nvmet-fcloop: remove nport from list on last user (bsc#1245193).\n- nvmet-fcloop: track ref counts for nports (bsc#1245193).\n- nvmet-fcloop: update refs on tfcp_req (bsc#1245193).\n- orangefs: Do not truncate file size (git-fixes).\n- page_pool: Fix use-after-free in page_pool_recycle_in_ring (git-fixes).\n- PCI: Add ACS quirk for Loongson PCIe (stable-fixes).\n- PCI: apple: Set only available ports up (git-fixes).\n- PCI: apple: Use gpiod_set_value_cansleep in probe flow (git-fixes).\n- PCI: brcmstb: Add a softdep to MIP MSI-X driver (stable-fixes).\n- PCI: brcmstb: Expand inbound window size up to 64GB (stable-fixes).\n- PCI: cadence-ep: Correct PBA offset in .set_msix() callback (git-fixes).\n- PCI: cadence: Fix runtime atomic count underflow (git-fixes).\n- PCI: dw-rockchip: Fix PHY function call sequence in rockchip_pcie_phy_deinit() (git-fixes).\n- PCI: dw-rockchip: Remove PCIE_L0S_ENTRY check from rockchip_pcie_link_up() (git-fixes).\n- PCI: dwc: ep: Correct PBA offset in .set_msix() callback (git-fixes).\n- PCI: dwc: ep: Ensure proper iteration over outbound map windows (stable-fixes).\n- PCI: endpoint: Retain fixed-size BAR size as well as aligned size (git-fixes).\n- PCI: Explicitly put devices into D0 when initializing (git-fixes).\n- PCI: Fix lock symmetry in pci_slot_unlock() (git-fixes).\n- PCI: Fix old_size lower bound in calculate_iosize() too (stable-fixes).\n- PCI: vmd: Disable MSI remapping bypass under Xen (stable-fixes).\n- PCI/DPC: Initialize aer_err_info before using it (git-fixes).\n- PCI/DPC: Log Error Source ID only when valid (git-fixes).\n- PCI/DPC: Use defines with DPC reason fields (git-fixes).\n- PCI/MSI: Size device MSI domain with the maximum number of vectors (git-fixes).\n- PCI/PM: Set up runtime PM even for devices without PCI PM (git-fixes).\n- phy: core: do not require set_mode() callback for phy_get_mode() to work (stable-fixes).\n- phy: qcom-qmp-usb: Fix an NULL vs IS_ERR() bug (git-fixes).\n- phy: renesas: rcar-gen3-usb2: Add support to initialize the bus (stable-fixes).\n- phy: renesas: rcar-gen3-usb2: Assert PLL reset on PHY power off (git-fixes).\n- phy: renesas: rcar-gen3-usb2: Lock around hardware registers and driver data (git-fixes).\n- phy: renesas: rcar-gen3-usb2: Move IRQ request in probe (stable-fixes).\n- pinctrl-tegra: Restore SFSEL bit when freeing pins (stable-fixes).\n- pinctrl: armada-37xx: propagate error from armada_37xx_gpio_get_direction() (stable-fixes).\n- pinctrl: armada-37xx: propagate error from armada_37xx_gpio_get() (stable-fixes).\n- pinctrl: armada-37xx: propagate error from armada_37xx_pmx_gpio_set_direction() (stable-fixes).\n- pinctrl: armada-37xx: propagate error from armada_37xx_pmx_set_by_name() (stable-fixes).\n- pinctrl: armada-37xx: set GPIO output value before setting direction (git-fixes).\n- pinctrl: armada-37xx: use correct OUTPUT_VAL register for GPIOs \u003e 31 (git-fixes).\n- pinctrl: at91: Fix possible out-of-boundary access (git-fixes).\n- pinctrl: bcm281xx: Use 'unsigned int' instead of bare 'unsigned' (stable-fixes).\n- pinctrl: devicetree: do not goto err when probing hogs in pinctrl_dt_to_map (stable-fixes).\n- pinctrl: mcp23s08: Reset all pins to input at probe (stable-fixes).\n- pinctrl: meson: define the pull up/down resistor value as 60 kOhm (stable-fixes).\n- pinctrl: qcom: pinctrl-qcm2290: Add missing pins (git-fixes).\n- pinctrl: st: Drop unused st_gpio_bank() function (git-fixes).\n- pinctrl: tegra: Fix off by one in tegra_pinctrl_get_group() (git-fixes).\n- platform/x86: amd: Use *-y instead of *-objs in Makefiles (jsc#PED-13094).\n- platform/x86: dell_rbu: Fix list usage (git-fixes).\n- platform/x86: dell_rbu: Stop overwriting data buffer (git-fixes).\n- platform/x86: fujitsu-laptop: Support Lifebook S2110 hotkeys (git-fixes).\n- platform/x86: fujitsu-laptop: Support Lifebook S2110 hotkeys (stable-fixes).\n- platform/x86: hp-bioscfg: Annotate struct bios_args with __counted_by (jsc#PED-13019).\n- platform/x86: hp-bioscfg: biosattr-interface (jsc#PED-13019).\n- platform/x86: hp-bioscfg: bioscfg (jsc#PED-13019).\n- platform/x86: hp-bioscfg: bioscfg-h (jsc#PED-13019).\n- platform/x86: hp-bioscfg: Change how enum possible values size is evaluated (jsc#PED-13019).\n- platform/x86: hp-bioscfg: Change how order list size is evaluated (jsc#PED-13019).\n- platform/x86: hp-bioscfg: Change how password encoding size is evaluated (jsc#PED-13019).\n- platform/x86: hp-bioscfg: Change how prerequisites size is evaluated (jsc#PED-13019).\n- platform/x86: hp-bioscfg: enum-attributes (jsc#PED-13019).\n- platform/x86: hp-bioscfg: fix a signedness bug in hp_wmi_perform_query() (jsc#PED-13019).\n- platform/x86: hp-bioscfg: Fix error handling in hp_add_other_attributes() (jsc#PED-13019).\n- platform/x86: hp-bioscfg: fix error reporting in hp_add_other_attributes() (jsc#PED-13019).\n- platform/x86: hp-bioscfg: Fix memory leaks in attribute packages (jsc#PED-13019).\n- platform/x86: hp-bioscfg: Fix reference leak (jsc#PED-13019).\n- platform/x86: hp-bioscfg: Fix uninitialized variable errors (jsc#PED-13019).\n- platform/x86: hp-bioscfg: int-attributes (jsc#PED-13019).\n- platform/x86: hp-bioscfg: Makefile (jsc#PED-13019).\n- platform/x86: hp-bioscfg: move mutex_lock() down in hp_add_other_attributes() (jsc#PED-13019).\n- platform/x86: hp-bioscfg: order-list-attributes (jsc#PED-13019).\n- platform/x86: hp-bioscfg: passwdobj-attributes (jsc#PED-13019).\n- platform/x86: hp-bioscfg: prevent a small buffer overflow (jsc#PED-13019).\n- platform/x86: hp-bioscfg: Remove duplicate use of variable in inner loop (jsc#PED-13019).\n- platform/x86: hp-bioscfg: Remove unused obj in hp_add_other_attributes() (jsc#PED-13019).\n- platform/x86: hp-bioscfg: Removed needless asm-generic (jsc#PED-13019).\n- platform/x86: hp-bioscfg: Replace the word HACK from source code (jsc#PED-13019).\n- platform/x86: hp-bioscfg: Simplify return check in hp_add_other_attributes() (jsc#PED-13019).\n- platform/x86: hp-bioscfg: spmobj-attributes (jsc#PED-13019).\n- platform/x86: hp-bioscfg: string-attributes (jsc#PED-13019).\n- platform/x86: hp-bioscfg: surestart-attributes (jsc#PED-13019).\n- platform/x86: hp-bioscfg: Update steps order list elements are evaluated (jsc#PED-13019).\n- platform/x86: hp-bioscfg: Use kmemdup() to replace kmalloc + memcpy (jsc#PED-13019).\n- platform/x86: ideapad-laptop: use usleep_range() for EC polling (git-fixes).\n- platform/x86: thinkpad_acpi: Ignore battery threshold change event notification (stable-fixes).\n- platform/x86: thinkpad_acpi: Support also NEC Lavie X1475JAS (git-fixes).\n- platform/x86: thinkpad_acpi: Support also NEC Lavie X1475JAS (stable-fixes).\n- platform/x86/amd: pmc: Clear metrics table at start of cycle (git-fixes).\n- platform/x86/amd/hsmp: acpi: Add sysfs files to display HSMP telemetry (jsc#PED-13094).\n- platform/x86/amd/hsmp: Add new error code and error logs (jsc#PED-13094).\n- platform/x86/amd/hsmp: Add support for HSMP protocol version 7 messages (jsc#PED-13094).\n- platform/x86/amd/hsmp: Change generic plat_dev name to hsmp_pdev (jsc#PED-13094).\n- platform/x86/amd/hsmp: Change the error type (jsc#PED-13094).\n- platform/x86/amd/hsmp: Convert amd_hsmp_rdwr() to a function pointer (jsc#PED-13094).\n- platform/x86/amd/hsmp: Create hsmp/ directory (jsc#PED-13094).\n- platform/x86/amd/hsmp: Create separate ACPI, plat and common drivers (jsc#PED-13094).\n- platform/x86/amd/hsmp: Create wrapper function init_acpi() (jsc#PED-13094).\n- platform/x86/amd/hsmp: fix building with CONFIG_HWMON=m (jsc#PED-13094).\n- platform/x86/amd/hsmp: Make amd_hsmp and hsmp_acpi as mutually exclusive drivers (jsc#PED-13094).\n- platform/x86/amd/hsmp: Make hsmp_pdev static instead of global (jsc#PED-13094).\n- platform/x86/amd/hsmp: mark hsmp_msg_desc_table as maybe_unused (git-fixes).\n- platform/x86/amd/hsmp: Move ACPI code to acpi.c (jsc#PED-13094).\n- platform/x86/amd/hsmp: Move platform device specific code to plat.c (jsc#PED-13094).\n- platform/x86/amd/hsmp: Move structure and macros to header file (jsc#PED-13094).\n- platform/x86/amd/hsmp: Report power via hwmon sensor (jsc#PED-13094).\n- platform/x86/amd/hsmp: Use a single DRIVER_VERSION for all hsmp modules (jsc#PED-13094).\n- platform/x86/amd/hsmp: Use dev_groups in the driver structure (jsc#PED-13094).\n- platform/x86/amd/hsmp: Use name space while exporting module symbols (jsc#PED-13094).\n- platform/x86/intel-uncore-freq: Fail module load when plat_info is NULL (git-fixes).\n- PM: runtime: fix denying of auto suspend in pm_suspend_timer_fn() (stable-fixes).\n- PM: sleep: Fix power.is_suspended cleanup for direct-complete devices (git-fixes).\n- PM: sleep: Print PM debug messages during hibernation (git-fixes).\n- PM: wakeup: Delete space in the end of string shown by pm_show_wakelocks() (git-fixes).\n- pNFS/flexfiles: Report ENETDOWN as a connection error (git-fixes).\n- power: reset: at91-reset: Optimize at91_reset() (git-fixes).\n- power: supply: bq27xxx: Retrieve again when busy (stable-fixes).\n- power: supply: collie: Fix wakeup source leaks on device unbind (stable-fixes).\n- powerpc/eeh: Fix missing PE bridge reconfiguration during VFIO EEH recovery (bsc#1215199).\n- powerpc/powernv/memtrace: Fix out of bounds issue in memtrace mmap (bsc#1244309 ltc#213790).\n- powerpc/pseries/msi: Avoid reading PCI device registers in reduced power states (bsc#1215199).\n- powerpc/vas: Return -EINVAL if the offset is non-zero in mmap() (bsc#1244309 ltc#213790).\n- pstore: Change kmsg_bytes storage size to u32 (git-fixes).\n- ptp: ocp: fix start time alignment in ptp_ocp_signal_set (git-fixes).\n- ptp: ocp: reject unsupported periodic output flags (git-fixes).\n- ptp: remove ptp-\u003en_vclocks check logic in ptp_vclock_in_use() (git-fixes).\n- r8152: add vendor/device ID pair for Dell Alienware AW1022z (git-fixes).\n- RDMA/core: Fix best page size finding when it can cross SG entries (git-fixes)\n- RDMA/uverbs: Propagate errors from rdma_lookup_get_uobject() (git-fixes)\n- regulator: ad5398: Add device tree support (stable-fixes).\n- regulator: max14577: Add error check for max14577_read_reg() (git-fixes).\n- regulator: max20086: Change enable gpio to optional (git-fixes).\n- regulator: max20086: Fix MAX200086 chip id (git-fixes).\n- regulator: max20086: Fix refcount leak in max20086_parse_regulators_dt() (git-fixes).\n- rtc: at91rm9200: drop unused module alias (git-fixes).\n- rtc: cmos: use spin_lock_irqsave in cmos_interrupt (git-fixes).\n- rtc: cpcap: drop unused module alias (git-fixes).\n- rtc: da9063: drop unused module alias (git-fixes).\n- rtc: ds1307: stop disabling alarms on probe (stable-fixes).\n- rtc: Fix offset calculation for .start_secs \u0026lt; 0 (git-fixes).\n- rtc: jz4740: drop unused module alias (git-fixes).\n- rtc: Make rtc_time64_to_tm() support dates before 1970 (stable-fixes).\n- rtc: pm8xxx: drop unused module alias (git-fixes).\n- rtc: rv3032: fix EERD location (stable-fixes).\n- rtc: s3c: drop unused module alias (git-fixes).\n- rtc: sh: assign correct interrupts with DT (git-fixes).\n- rtc: stm32: drop unused module alias (git-fixes).\n- s390/pci: Allow re-add of a reserved but not yet removed device (bsc#1244145).\n- s390/pci: Fix __pcilg_mio_inuser() inline assembly (git-fixes bsc#1245226).\n- s390/pci: Fix duplicate pci_dev_put() in disable_slot() when PF has child VFs (git-fixes bsc#1244145).\n- s390/pci: Fix potential double remove of hotplug slot (bsc#1244145).\n- s390/pci: introduce lock to synchronize state of zpci_dev's (jsc#PED-10253 bsc#1244145).\n- s390/pci: Prevent self deletion in disable_slot() (bsc#1244145).\n- s390/pci: remove hotplug slot when releasing the device (bsc#1244145).\n- s390/pci: Remove redundant bus removal and disable from zpci_release_device() (bsc#1244145).\n- s390/pci: rename lock member in struct zpci_dev (jsc#PED-10253 bsc#1244145).\n- s390/pci: Serialize device addition and removal (bsc#1244145).\n- s390/tty: Fix a potential memory leak bug (git-fixes bsc#1245228).\n- scsi: dc395x: Remove DEBUG conditional compilation (git-fixes).\n- scsi: dc395x: Remove leftover if statement in reselect() (git-fixes).\n- scsi: elx: efct: Fix memory leak in efct_hw_parse_filter() (git-fixes).\n- scsi: hisi_sas: Call I_T_nexus after soft reset for SATA disk (git-fixes).\n- scsi: hisi_sas: Fix I/O errors caused by hardware port ID changes (git-fixes).\n- scsi: Improve CDL control (git-fixes).\n- scsi: iscsi: Fix incorrect error path labels for flashnode operations (git-fixes).\n- scsi: megaraid_sas: Block zero-length ATA VPD inquiry (git-fixes).\n- scsi: mpi3mr: Add level check to control event logging (git-fixes).\n- scsi: mpt3sas: Fix _ctl_get_mpt_mctp_passthru_adapter() to return IOC pointer (git-fixes).\n- scsi: mpt3sas: Send a diag reset if target reset fails (git-fixes).\n- scsi: pm80xx: Set phy_attached to zero when device is gone (git-fixes).\n- scsi: qedf: Use designated initializer for struct qed_fcoe_cb_ops (git-fixes).\n- scsi: sd_zbc: block: Respect bio vector limits for REPORT ZONES buffer (git-fixes).\n- scsi: smartpqi: Fix smp_processor_id() call trace for preemptible kernels (git-fixes).\n- scsi: st: ERASE does not change tape location (git-fixes).\n- scsi: st: Restore some drive settings after reset (git-fixes).\n- scsi: st: Tighten the page format heuristics with MODE SELECT (git-fixes).\n- scsi: storvsc: Do not report the host packet status as the hv status (git-fixes).\n- scsi: storvsc: Increase the timeouts to storvsc_timeout (git-fixes).\n- selftests/bpf: Fix bpf_nf selftest failure (git-fixes).\n- selftests/mm: restore default nr_hugepages value during cleanup in hugetlb_reparenting_test.sh (git-fixes).\n- selftests/net: have `gro.sh -t` return a correct exit code (stable-fixes).\n- selftests/seccomp: fix syscall_restart test for arm compat (git-fixes).\n- serial: core: restore of_node information in sysfs (git-fixes).\n- serial: Fix potential null-ptr-deref in mlb_usio_probe() (git-fixes).\n- serial: imx: Restore original RXTL for console to fix data loss (git-fixes).\n- serial: jsm: fix NPE during jsm_uart_port_init (git-fixes).\n- serial: mctrl_gpio: split disable_ms into sync and no_sync APIs (git-fixes).\n- serial: sh-sci: Move runtime PM enable to sci_probe_single() (stable-fixes).\n- serial: sh-sci: Save and restore more registers (git-fixes).\n- serial: sh-sci: Update the suspend/resume support (stable-fixes).\n- smb: client: allow more DFS referrals to be cached (git-fixes).\n- smb: client: avoid unnecessary reconnects when refreshing referrals (git-fixes).\n- smb: client: change return value in open_cached_dir_by_dentry() if !cfids (git-fixes).\n- smb: client: do not retry DFS targets on server shutdown (git-fixes).\n- smb: client: do not trust DFSREF_STORAGE_SERVER bit (git-fixes).\n- smb: client: do not try following DFS links in cifs_tree_connect() (git-fixes).\n- smb: client: fix DFS interlink failover (git-fixes).\n- smb: client: fix DFS mount against old servers with NTLMSSP (git-fixes).\n- smb: client: fix hang in wait_for_response() for negproto (bsc#1242709).\n- smb: client: fix potential race in cifs_put_tcon() (git-fixes).\n- smb: client: fix return value of parse_dfs_referrals() (git-fixes).\n- smb: client: get rid of @nlsc param in cifs_tree_connect() (git-fixes).\n- smb: client: get rid of kstrdup() in get_ses_refpath() (git-fixes).\n- smb: client: get rid of TCP_Server_Info::refpath_lock (git-fixes).\n- smb: client: improve purging of cached referrals (git-fixes).\n- smb: client: introduce av_for_each_entry() helper (git-fixes).\n- smb: client: optimize referral walk on failed link targets (git-fixes).\n- smb: client: parse av pair type 4 in CHALLENGE_MESSAGE (git-fixes).\n- smb: client: parse DNS domain name from domain= option (git-fixes).\n- smb: client: provide dns_resolve_{unc,name} helpers (git-fixes).\n- smb: client: refresh referral without acquiring refpath_lock (git-fixes).\n- smb: client: remove unnecessary checks in open_cached_dir() (git-fixes).\n- smb: client: Use str_yes_no() helper function (git-fixes).\n- smb3: fix Open files on server counter going negative (git-fixes).\n- soc: aspeed: Add NULL check in aspeed_lpc_enable_snoop() (git-fixes).\n- soc: aspeed: lpc: Fix impossible judgment condition (git-fixes).\n- soc: qcom: smp2p: Fix fallback to qcom,ipc parse (git-fixes).\n- soc: ti: k3-socinfo: Do not use syscon helper to build regmap (stable-fixes).\n- soundwire: amd: change the soundwire wake enable/disable sequence (stable-fixes).\n- spi-rockchip: Fix register out of bounds access (stable-fixes).\n- spi: bcm63xx-hsspi: fix shared reset (git-fixes).\n- spi: bcm63xx-spi: fix shared reset (git-fixes).\n- spi: sh-msiof: Fix maximum DMA transfer size (git-fixes).\n- spi: spi-sun4i: fix early activation (stable-fixes).\n- spi: tegra210-quad: Fix X1_X2_X4 encoding and support x4 transfers (git-fixes).\n- spi: tegra210-quad: modify chip select (CS) deactivation (git-fixes).\n- spi: tegra210-quad: remove redundant error handling code (git-fixes).\n- spi: zynqmp-gqspi: Always acknowledge interrupts (stable-fixes).\n- staging: iio: ad5933: Correct settling cycles encoding per datasheet (git-fixes).\n- staging: rtl8723bs: Avoid memset() in aes_cipher() and aes_decipher() (git-fixes).\n- struct usci: hide additional member (git-fixes).\n- SUNRPC: Do not allow waiting for exiting tasks (git-fixes).\n- SUNRPC: handle SVC_GARBAGE during svc auth processing as auth error (git-fixes).\n- SUNRPC: Prevent hang on NFS mount with xprtsec=[m]tls (git-fixes).\n- SUNRPC: rpc_clnt_set_transport() must not change the autobind setting (git-fixes).\n- SUNRPC: rpcbind should never reset the port to the value '0' (git-fixes).\n- svsm: Add header with SVSM_VTPM_CMD helpers (bsc#1241191).\n- sysfb: Fix screen_info type check for VGA (git-fixes).\n- tcp_metrics: optimize tcp_metrics_flush_all() (git-fixes).\n- tcp: bring back NUMA dispersion in inet_ehash_locks_alloc() (git-fixes).\n- tcp/dccp: allow a connection when sk_max_ack_backlog is zero (git-fixes).\n- tcp/dccp: bypass empty buckets in inet_twsk_purge() (git-fixes).\n- tcp/dccp: complete lockless accesses to sk-\u003esk_max_ack_backlog (git-fixes).\n- thermal/drivers/mediatek/lvts: Fix debugfs unregister on failure (git-fixes).\n- thermal/drivers/qoriq: Power down TMU on system suspend (stable-fixes).\n- thunderbolt: Do not add non-active NVM if NVM upgrade is disabled for retimer (stable-fixes).\n- thunderbolt: Do not double dequeue a configuration request (stable-fixes).\n- thunderbolt: Fix a logic error in wake on connect (git-fixes).\n- thunderbolt: Improve redrive mode handling (git-fixes).\n- timekeeping: Fix bogus clock_was_set() invocation in (git-fixes)\n- timekeeping: Fix cross-timestamp interpolation corner case (git-fixes)\n- timekeeping: Fix cross-timestamp interpolation for non-x86 (git-fixes)\n- timekeeping: Fix cross-timestamp interpolation on counter (git-fixes)\n- tpm: Add SNP SVSM vTPM driver (bsc#1241191).\n- tpm: Make chip-\u003e{status,cancel,req_canceled} opt (bsc#1241191).\n- trace/trace_event_perf: remove duplicate samples on the first tracepoint event (git-fixes).\n- tracing: Add __print_dynamic_array() helper (bsc#1243544).\n- tracing: Add __string_len() example (bsc#1243544).\n- tracing: Fix cmp_entries_dup() to respect sort() comparison rules (git-fixes).\n- tracing: Fix compilation warning on arm32 (bsc#1243551).\n- tracing: Use atomic64_inc_return() in trace_clock_counter() (git-fixes).\n- tracing/eprobe: Fix to release eprobe when failed to add dyn_event (git-fixes).\n- truct dwc3 hide new member wakeup_pending_funcs (git-fixes).\n- tty: serial: 8250_omap: fix TX with DMA for am33xx (git-fixes).\n- ucsi_debugfs_entry: hide signedness change (git-fixes).\n- udp: annotate data-races around up-\u003epending (git-fixes).\n- udp: fix incorrect parameter validation in the udp_lib_getsockopt() function (git-fixes).\n- udp: fix receiving fraglist GSO packets (git-fixes).\n- udp: preserve the connected status if only UDP cmsg (git-fixes).\n- uprobes: Use kzalloc to allocate xol area (git-fixes).\n- usb: cdnsp: Fix issue with detecting command completion event (git-fixes).\n- usb: cdnsp: Fix issue with detecting USB 3.2 speed (git-fixes).\n- usb: dwc3: gadget: Make gadget_wakeup asynchronous (git-fixes).\n- usb: Flush altsetting 0 endpoints before reinitializating them after reset (git-fixes).\n- usb: misc: onboard_usb_dev: fix support for Cypress HX3 hubs (git-fixes).\n- usb: quirks: Add NO_LPM quirk for SanDisk Extreme 55AE (stable-fixes).\n- usb: renesas_usbhs: Reorder clock handling and power management in probe (git-fixes).\n- usb: serial: pl2303: add new chip PL2303GC-Q20 and PL2303GT-2AB (stable-fixes).\n- usb: storage: Ignore UAS driver for SanDisk 3.2 Gen2 storage device (stable-fixes).\n- usb: typec: tcpm: move tcpm_queue_vdm_unlocked to asynchronous work (git-fixes).\n- usb: typec: tcpm/tcpci_maxim: Fix bounds check in process_rx() (git-fixes).\n- usb: typec: ucsi: allow non-partner GET_PDOS for Qualcomm devices (git-fixes).\n- usb: typec: ucsi: fix Clang -Wsign-conversion warning (git-fixes).\n- usb: typec: ucsi: fix UCSI on buggy Qualcomm devices (git-fixes).\n- usb: typec: ucsi: limit the UCSI_NO_PARTNER_PDOS even further (git-fixes).\n- usb: typec: ucsi: Only enable supported notifications (git-fixes).\n- usb: usbtmc: Fix read_stb function and get_stb ioctl (git-fixes).\n- usb: usbtmc: Fix timeout value in get_stb (git-fixes).\n- usb: xhci: Do not change the status of stalled TDs on failed Stop EP (stable-fixes).\n- usbnet: asix AX88772: leave the carrier control to phylink (stable-fixes).\n- vgacon: Add check for vc_origin address range in vgacon_scroll() (git-fixes).\n- VMCI: fix race between vmci_host_setup_notify and vmci_ctx_unset_notify (git-fixes).\n- vmxnet3: correctly report gso type for UDP tunnels (bsc#1244626).\n- vmxnet3: support higher link speeds from vmxnet3 v9 (bsc#1244626).\n- vmxnet3: update MTU after device quiesce (bsc#1244626).\n- vt: remove VT_RESIZE and VT_RESIZEX from vt_compat_ioctl() (git-fixes).\n- watchdog: da9052_wdt: respect TWDMIN (stable-fixes).\n- watchdog: exar: Shorten identity name to fit correctly (git-fixes).\n- watchdog: fix watchdog may detect false positive of softlockup (stable-fixes).\n- watchdog: it87_wdt: add PWRGD enable quirk for Qotom QCML04 (git-fixes).\n- watchdog: mediatek: Add support for MT6735 TOPRGU/WDT (git-fixes).\n- wifi: ath11k: avoid burning CPU in ath11k_debugfs_fw_stats_request() (git-fixes).\n- wifi: ath11k: convert timeouts to secs_to_jiffies() (stable-fixes).\n- wifi: ath11k: do not use static variables in ath11k_debugfs_fw_stats_process() (git-fixes).\n- wifi: ath11k: do not wait when there is no vdev started (git-fixes).\n- wifi: ath11k: fix node corruption in ar-\u003earvifs list (git-fixes).\n- wifi: ath11k: Fix QMI memory reuse logic (stable-fixes).\n- wifi: ath11k: fix ring-buffer corruption (git-fixes).\n- wifi: ath11k: fix rx completion meta data corruption (git-fixes).\n- wifi: ath11k: fix soc_dp_stats debugfs file permission (stable-fixes).\n- wifi: ath11k: move some firmware stats related functions outside of debugfs (git-fixes).\n- wifi: ath11k: update channel list in worker when wait flag is set (bsc#1243847).\n- wifi: ath11k: validate ath11k_crypto_mode on top of ath11k_core_qmi_firmware_ready (git-fixes).\n- wifi: ath12k: ACPI band edge channel power support (bsc#1240998).\n- wifi: ath12k: ACPI CCA threshold support (bsc#1240998).\n- wifi: ath12k: ACPI SAR support (bsc#1240998).\n- wifi: ath12k: ACPI TAS support (bsc#1240998).\n- wifi: ath12k: add 6 GHz params in peer assoc command (bsc#1240998).\n- wifi: ath12k: Add additional checks for vif and sta iterators (bsc#1240998).\n- wifi: ath12k: add ATH12K_DBG_WOW log level (bsc#1240998).\n- wifi: ath12k: add basic WoW functionalities (bsc#1240998).\n- wifi: ath12k: add channel 2 into 6 GHz channel list (bsc#1240998).\n- wifi: ath12k: add EMA beacon support (bsc#1240998).\n- wifi: ath12k: Add firmware coredump collection support (bsc#1240998).\n- wifi: ath12k: Add htt_stats_dump file ops support (bsc#1240998).\n- wifi: ath12k: add hw_link_id in ath12k_pdev (bsc#1240998).\n- wifi: ath12k: Add lock to protect the hardware state (bsc#1240998).\n- wifi: ath12k: add MBSSID beacon support (bsc#1240998).\n- wifi: ath12k: Add missing htt_metadata flag in ath12k_dp_tx() (bsc#1240998).\n- wifi: ath12k: add missing lockdep_assert_wiphy() for ath12k_mac_op_ functions (bsc#1240998).\n- wifi: ath12k: Add MSDU length validation for TKIP MIC error (git-fixes).\n- wifi: ath12k: add multi device support for WBM idle ring buffer setup (bsc#1240998).\n- wifi: ath12k: add multiple radio support in a single MAC HW un/register (bsc#1240998).\n- wifi: ath12k: add panic handler (bsc#1240998).\n- wifi: ath12k: Add support to enable debugfs_htt_stats (bsc#1240998).\n- wifi: ath12k: add support to handle beacon miss for WCN7850 (bsc#1240998).\n- wifi: ath12k: Add support to parse requested stats_type (bsc#1240998).\n- wifi: ath12k: add WoW net-detect functionality (bsc#1240998).\n- wifi: ath12k: advertise driver capabilities for MBSSID and EMA (bsc#1240998).\n- wifi: ath12k: allocate dummy net_device dynamically (bsc#1240998).\n- wifi: ath12k: ath12k_mac_op_set_key(): fix uninitialized symbol 'ret' (bsc#1240998).\n- wifi: ath12k: ath12k_mac_op_sta_state(): clean up update_wk cancellation (bsc#1240998).\n- wifi: ath12k: ath12k_mac_set_key(): remove exit label (bsc#1240998).\n- wifi: ath12k: Avoid -Wflex-array-member-not-at-end warnings (bsc#1240998).\n- wifi: ath12k: avoid double SW2HW_MACID conversion (bsc#1240998).\n- wifi: ath12k: avoid duplicated vdev down (bsc#1240998).\n- wifi: ath12k: Avoid napi_sync() before napi_enable() (stable-fixes).\n- wifi: ath12k: avoid redundant code in Rx cookie conversion init (bsc#1240998).\n- wifi: ath12k: avoid stopping mac80211 queues in ath12k_core_restart() (bsc#1240998).\n- wifi: ath12k: avoid unnecessary MSDU drop in the Rx error process (bsc#1240998).\n- wifi: ath12k: Cache vdev configs before vdev create (bsc#1240998).\n- wifi: ath12k: change supports_suspend to true for WCN7850 (bsc#1240998).\n- wifi: ath12k: cleanup unneeded labels (bsc#1240998).\n- wifi: ath12k: configure MBSSID parameters in AP mode (bsc#1240998).\n- wifi: ath12k: configure MBSSID params in vdev create/start (bsc#1240998).\n- wifi: ath12k: convert struct ath12k_sta::update_wk to use struct wiphy_work (bsc#1240998).\n- wifi: ath12k: correct the capital word typo (bsc#1240998).\n- wifi: ath12k: create a structure for WMI vdev up parameters (bsc#1240998).\n- wifi: ath12k: debugfs: radar simulation support (bsc#1240998).\n- wifi: ath12k: decrease MHI channel buffer length to 8KB (bsc#1240998).\n- wifi: ath12k: delete NSS and TX power setting for monitor vdev (bsc#1240998).\n- wifi: ath12k: displace the Tx and Rx descriptor in cookie conversion table (bsc#1240998).\n- wifi: ath12k: do not dump SRNG statistics during resume (bsc#1240998).\n- wifi: ath12k: do not process consecutive RDDM event (bsc#1240998).\n- wifi: ath12k: do not use %pK in dmesg format strings (bsc#1240998).\n- wifi: ath12k: Dump additional Tx PDEV HTT stats (bsc#1240998).\n- wifi: ath12k: dynamic VLAN support (bsc#1240998).\n- wifi: ath12k: dynamically update peer puncturing bitmap for STA (bsc#1240998).\n- wifi: ath12k: enable service flag for survey dump stats (bsc#1240998).\n- wifi: ath12k: enable WIPHY_FLAG_DISABLE_WEXT (bsc#1240998).\n- wifi: ath12k: extend the link capable flag (bsc#1240998).\n- wifi: ath12k: fetch correct radio based on vdev status (bsc#1240998).\n- wifi: ath12k: Fetch regdb.bin file from board-2.bin (stable-fixes).\n- wifi: ath12k: fix a possible dead lock caused by ab-\u003ebase_lock (stable-fixes).\n- wifi: ath12k: fix A-MSDU indication in monitor mode (bsc#1240998).\n- wifi: ath12k: fix ack signal strength calculation (bsc#1240998).\n- wifi: ath12k: fix ACPI warning when resume (bsc#1240998).\n- wifi: ath12k: fix ath12k_hal_tx_cmd_ext_desc_setup() info1 override (stable-fixes).\n- wifi: ath12k: Fix buffer overflow in debugfs (bsc#1240998).\n- wifi: ath12k: fix build vs old compiler (bsc#1240998).\n- wifi: ath12k: fix calling correct function for rx monitor mode (bsc#1240998).\n- wifi: ath12k: fix cleanup path after mhi init (git-fixes).\n- wifi: ath12k: fix desc address calculation in wbm tx completion (bsc#1240998).\n- wifi: ath12k: Fix devmem address prefix when logging (bsc#1240998).\n- wifi: ath12k: fix driver initialization for WoW unsupported devices (bsc#1240998).\n- wifi: ath12k: Fix end offset bit definition in monitor ring descriptor (stable-fixes).\n- wifi: ath12k: fix failed to set mhi state error during reboot with hardware grouping (stable-fixes).\n- wifi: ath12k: fix flush failure in recovery scenarios (bsc#1240998).\n- wifi: ath12k: Fix for out-of bound access error (bsc#1240998).\n- wifi: ath12k: fix GCC_GCC_PCIE_HOT_RST definition for WCN7850 (git-fixes).\n- wifi: ath12k: fix hal_rx_buf_return_buf_manager documentation (bsc#1240998).\n- wifi: ath12k: fix incorrect CE addresses (stable-fixes).\n- wifi: ath12k: fix invalid access to memory (git-fixes).\n- wifi: ath12k: Fix invalid memory access while forming 802.11 header (git-fixes).\n- wifi: ath12k: fix key cache handling (bsc#1240998).\n- wifi: ath12k: fix legacy peer association due to missing HT or 6 GHz capabilities (bsc#1240998).\n- wifi: ath12k: fix link capable flags (bsc#1240998).\n- wifi: ath12k: fix link valid field initialization in the monitor Rx (stable-fixes).\n- wifi: ath12k: fix mac id extraction when MSDU spillover in rx error path (bsc#1240998).\n- wifi: ath12k: fix macro definition HAL_RX_MSDU_PKT_LENGTH_GET (stable-fixes).\n- wifi: ath12k: fix mbssid max interface advertisement (bsc#1240998).\n- wifi: ath12k: Fix memory leak during vdev_id mismatch (git-fixes).\n- wifi: ath12k: fix missing endianness conversion in wmi_vdev_create_cmd() (bsc#1240998).\n- wifi: ath12k: fix misspelling of 'dma' in num_rxmda_per_pdev (bsc#1240998).\n- wifi: ath12k: fix node corruption in ar-\u003earvifs list (git-fixes).\n- wifi: ath12k: fix NULL pointer access in ath12k_mac_op_get_survey() (bsc#1240998).\n- wifi: ath12k: fix one more memcpy size error (bsc#1240998).\n- wifi: ath12k: Fix pdev id sent to firmware for single phy devices (bsc#1240998).\n- wifi: ath12k: fix per pdev debugfs registration (bsc#1240998).\n- wifi: ath12k: fix reusing outside iterator in ath12k_wow_vif_set_wakeups() (bsc#1240998).\n- wifi: ath12k: fix ring-buffer corruption (git-fixes).\n- wifi: ath12k: fix skb_ext_desc leak in ath12k_dp_tx() error path (bsc#1240998).\n- wifi: ath12k: fix Smatch warnings on ath12k_core_suspend() (bsc#1240998).\n- wifi: ath12k: fix struct hal_rx_mpdu_start (bsc#1240998).\n- wifi: ath12k: fix struct hal_rx_phyrx_rssi_legacy_info (bsc#1240998).\n- wifi: ath12k: fix struct hal_rx_ppdu_end_user_stats (bsc#1240998).\n- wifi: ath12k: fix struct hal_rx_ppdu_start (bsc#1240998).\n- wifi: ath12k: fix survey dump collection in 6 GHz (bsc#1240998).\n- wifi: ath12k: fix the ampdu id fetch in the HAL_RX_MPDU_START TLV (stable-fixes).\n- wifi: ath12k: Fix the QoS control field offset to build QoS header (git-fixes).\n- wifi: ath12k: fix the stack frame size warning in ath12k_mac_op_hw_scan (bsc#1240998).\n- wifi: ath12k: fix use-after-free in ath12k_dp_cc_cleanup() (bsc#1240998).\n- wifi: ath12k: Fix WARN_ON during firmware crash in split-phy (bsc#1240998).\n- wifi: ath12k: fix warning on DMA ring capabilities event (bsc#1240998).\n- wifi: ath12k: Fix WMI tag for EHT rate in peer assoc (git-fixes).\n- wifi: ath12k: flush all packets before suspend (bsc#1240998).\n- wifi: ath12k: Handle error cases during extended skb allocation (git-fixes).\n- wifi: ath12k: handle keepalive during WoWLAN suspend and resume (bsc#1240998).\n- wifi: ath12k: handle symlink cleanup for per pdev debugfs dentry (bsc#1240998).\n- wifi: ath12k: implement hardware data filter (bsc#1240998).\n- wifi: ath12k: implement WoW enable and wakeup commands (bsc#1240998).\n- wifi: ath12k: Improve BSS discovery with hidden SSID in 6 GHz band (stable-fixes).\n- wifi: ath12k: improve the rx descriptor error information (bsc#1240998).\n- wifi: ath12k: initial debugfs support (bsc#1240998).\n- wifi: ath12k: Introduce device index (bsc#1240998).\n- wifi: ath12k: make read-only array svc_id static const (bsc#1240998).\n- wifi: ath12k: Modify add and remove chanctx ops for single wiphy support (bsc#1240998).\n- wifi: ath12k: modify ath12k mac start/stop ops for single wiphy (bsc#1240998).\n- wifi: ath12k: modify ath12k_get_arvif_iter() for MLO (bsc#1240998).\n- wifi: ath12k: modify ath12k_mac_op_bss_info_changed() for MLO (bsc#1240998).\n- wifi: ath12k: modify ath12k_mac_op_set_key() for MLO (bsc#1240998).\n- wifi: ath12k: modify ath12k_mac_vif_chan() for MLO (bsc#1240998).\n- wifi: ath12k: modify link arvif creation and removal for MLO (bsc#1240998).\n- wifi: ath12k: Modify print_array_to_buf() to support arrays with 1-based semantics (bsc#1240998).\n- wifi: ath12k: modify regulatory support for single wiphy architecture (bsc#1240998).\n- wifi: ath12k: modify remain on channel for single wiphy (bsc#1240998).\n- wifi: ath12k: Modify rts threshold mac op for single wiphy (bsc#1240998).\n- wifi: ath12k: Modify set and get antenna mac ops for single wiphy (bsc#1240998).\n- wifi: ath12k: move txbaddr/rxbaddr into struct ath12k_dp (bsc#1240998).\n- wifi: ath12k: no need to handle pktlog during suspend/resume (bsc#1240998).\n- wifi: ath12k: Optimize the lock contention of used list in Rx data path (bsc#1240998).\n- wifi: ath12k: pass ath12k_link_vif instead of vif/ahvif (bsc#1240998).\n- wifi: ath12k: Pass correct values of center freq1 and center freq2 for 160 MHz (stable-fixes).\n- wifi: ath12k: prepare sta data structure for MLO handling (bsc#1240998).\n- wifi: ath12k: prepare vif config caching for MLO (bsc#1240998).\n- wifi: ath12k: prepare vif data structure for MLO handling (bsc#1240998).\n- wifi: ath12k: Prevent sending WMI commands to firmware during firmware crash (bsc#1240998).\n- wifi: ath12k: read single_chip_mlo_support parameter from QMI PHY capability (bsc#1240998).\n- wifi: ath12k: rearrange IRQ enable/disable in reset path (bsc#1240998).\n- wifi: ath12k: refactor arvif security parameter configuration (bsc#1240998).\n- wifi: ath12k: refactor ath12k_hw_regs structure (stable-fixes).\n- wifi: ath12k: Refactor data path cmem init (bsc#1240998).\n- wifi: ath12k: Refactor error handler of Rxdma replenish (bsc#1240998).\n- wifi: ath12k: Refactor idle ring descriptor setup (bsc#1240998).\n- wifi: ath12k: refactor rx descriptor CMEM configuration (bsc#1240998).\n- wifi: ath12k: Refactor Rxdma buffer replinish argument (bsc#1240998).\n- wifi: ath12k: refactor SMPS configuration (bsc#1240998).\n- wifi: ath12k: Refactor the hardware cookie conversion init (bsc#1240998).\n- wifi: ath12k: Refactor the hardware recovery procedure (bsc#1240998).\n- wifi: ath12k: Refactor the hardware state (bsc#1240998).\n- wifi: ath12k: remove duplicate definition of MAX_RADIOS (bsc#1240998).\n- wifi: ath12k: remove duplicate definitions in wmi.h (bsc#1240998).\n- wifi: ath12k: remove invalid peer create logic (bsc#1240998).\n- wifi: ath12k: remove MHI LOOPBACK channels (bsc#1240998).\n- wifi: ath12k: remove obsolete struct wmi_start_scan_arg (bsc#1240998).\n- wifi: ath12k: remove redundant peer delete for WCN7850 (bsc#1240998).\n- wifi: ath12k: Remove unsupported tx monitor handling (bsc#1240998).\n- wifi: ath12k: Remove unused ath12k_base from ath12k_hw (bsc#1240998).\n- wifi: ath12k: Remove unused tcl_*_ring configuration (bsc#1240998).\n- wifi: ath12k: remove unused variable monitor_flags (bsc#1240998).\n- wifi: ath12k: remove unused variable monitor_present (bsc#1240998).\n- wifi: ath12k: rename MBSSID fields in wmi_vdev_up_cmd (bsc#1240998).\n- wifi: ath12k: Replace 'chip' with 'device' in hal Rx return buffer manager (bsc#1240998).\n- wifi: ath12k: Report proper tx completion status to mac80211 (stable-fixes).\n- wifi: ath12k: Resolve multicast packet drop by populating key_cipher in ath12k_install_key() (bsc#1240998).\n- wifi: ath12k: restore ASPM for supported hardwares only (bsc#1240998).\n- wifi: ath12k: scan statemachine changes for single wiphy (bsc#1240998).\n- wifi: ath12k: set mlo_capable_flags based on QMI PHY capability (bsc#1240998).\n- wifi: ath12k: skip sending vdev down for channel switch (bsc#1240998).\n- wifi: ath12k: support ARP and NS offload (bsc#1240998).\n- wifi: ath12k: Support BE OFDMA Pdev Rate Stats (bsc#1240998).\n- wifi: ath12k: Support DMAC Reset Stats (bsc#1240998).\n- wifi: ath12k: support get_survey mac op for single wiphy (bsc#1240998).\n- wifi: ath12k: support GTK rekey offload (bsc#1240998).\n- wifi: ath12k: Support pdev CCA Stats (bsc#1240998).\n- wifi: ath12k: Support pdev error stats (bsc#1240998).\n- wifi: ath12k: Support Pdev OBSS Stats (bsc#1240998).\n- wifi: ath12k: Support Pdev Scheduled Algorithm Stats (bsc#1240998).\n- wifi: ath12k: Support pdev Transmit Multi-user stats (bsc#1240998).\n- wifi: ath12k: Support Ring and SFM stats (bsc#1240998).\n- wifi: ath12k: Support Self-Generated Transmit stats (bsc#1240998).\n- wifi: ath12k: support SMPS configuration for 6 GHz (bsc#1240998).\n- wifi: ath12k: support suspend/resume (bsc#1240998).\n- wifi: ath12k: Support TQM stats (bsc#1240998).\n- wifi: ath12k: Support Transmit DE stats (bsc#1240998).\n- wifi: ath12k: Support Transmit Scheduler stats (bsc#1240998).\n- wifi: ath12k: switch to using wiphy_lock() and remove ar-\u003econf_mutex (bsc#1240998).\n- wifi: ath12k: unregister per pdev debugfs (bsc#1240998).\n- wifi: ath12k: update ath12k_mac_op_conf_tx() for MLO (bsc#1240998).\n- wifi: ath12k: update ath12k_mac_op_update_vif_offload() for MLO (bsc#1240998).\n- wifi: ath12k: use 128 bytes aligned iova in transmit path for WCN7850 (bsc#1240998).\n- wifi: ath12k: use correct MAX_RADIOS (bsc#1240998).\n- wifi: ath12k: use tail MSDU to get MSDU information (bsc#1240998).\n- wifi: ath12k: using msdu end descriptor to check for rx multicast packets (stable-fixes).\n- wifi: ath12k: vdev statemachine changes for single wiphy (bsc#1240998).\n- wifi: ath9k_htc: Abort software beacon handling if disabled (git-fixes).\n- wifi: ath9k: return by of_get_mac_address (stable-fixes).\n- wifi: carl9170: do not ping device which has failed to load firmware (git-fixes).\n- wifi: cfg80211: allow IR in 20 MHz configurations (stable-fixes).\n- wifi: iwlfiwi: mvm: Fix the rate reporting (git-fixes).\n- wifi: iwlwifi: Add missing MODULE_FIRMWARE for Qu-c0-jf-b0 (stable-fixes).\n- wifi: iwlwifi: add support for Killer on MTL (stable-fixes).\n- wifi: iwlwifi: do not warn during reprobe (stable-fixes).\n- wifi: iwlwifi: do not warn when if there is a FW error (stable-fixes).\n- wifi: iwlwifi: fix debug actions order (stable-fixes).\n- wifi: iwlwifi: fix the ECKV UEFI variable name (stable-fixes).\n- wifi: iwlwifi: mark Br device not integrated (stable-fixes).\n- wifi: iwlwifi: mvm: fix beacon CCK flag (stable-fixes).\n- wifi: iwlwifi: mvm: fix setting the TK when associated (stable-fixes).\n- wifi: iwlwifi: pcie: make sure to lock rxq-\u003eread (stable-fixes).\n- wifi: iwlwifi: use correct IMR dump variable (stable-fixes).\n- wifi: iwlwifi: w/a FW SMPS mode selection (stable-fixes).\n- wifi: mac80211_hwsim: Fix MLD address translation (stable-fixes).\n- wifi: mac80211_hwsim: Prevent tsf from setting if beacon is disabled (stable-fixes).\n- wifi: mac80211: do not offer a mesh path if forwarding is disabled (stable-fixes).\n- wifi: mac80211: do not unconditionally call drv_mgd_complete_tx() (stable-fixes).\n- wifi: mac80211: fix beacon interval calculation overflow (git-fixes).\n- wifi: mac80211: fix warning on disconnect during failed ML reconf (stable-fixes).\n- wifi: mac80211: remove misplaced drv_mgd_complete_tx() call (stable-fixes).\n- wifi: mac80211: set ieee80211_prep_tx_info::link_id upon Auth Rx (stable-fixes).\n- wifi: mac80211: validate SCAN_FLAG_AP in scan request during MLO (stable-fixes).\n- wifi: mac80211: VLAN traffic in multicast path (stable-fixes).\n- wifi: mt76: mt76x2: Add support for LiteOn WN4516R,WN4519R (stable-fixes).\n- wifi: mt76: mt7915: Fix null-ptr-deref in mt7915_mmio_wed_init() (git-fixes).\n- wifi: mt76: mt7921: add 160 MHz AP for mt7922 device (stable-fixes).\n- wifi: mt76: mt7925: ensure all MCU commands wait for response (git-fixes).\n- wifi: mt76: mt7925: fix fails to enter low power mode in suspend state (stable-fixes).\n- wifi: mt76: mt7925: fix host interrupt register initialization (git-fixes).\n- wifi: mt76: mt7925: introduce thermal protection (stable-fixes).\n- wifi: mt76: mt7925: load the appropriate CLC data based on hardware type (stable-fixes).\n- wifi: mt76: mt7925: prevent multiple scan commands (git-fixes).\n- wifi: mt76: mt7925: refine the sniffer commnad (git-fixes).\n- wifi: mt76: mt7996: drop fragments with multicast or broadcast RA (stable-fixes).\n- wifi: mt76: mt7996: fix RX buffer size of MCU event (git-fixes).\n- wifi: mt76: mt7996: revise TXS size (stable-fixes).\n- wifi: mt76: mt7996: set EHT max ampdu length capability (git-fixes).\n- wifi: mt76: only mark tx-status-failed frames as ACKed on mt76x0/2 (stable-fixes).\n- wifi: mwifiex: Fix HT40 bandwidth issue (stable-fixes).\n- wifi: p54: prevent buffer-overflow in p54_rx_eeprom_readback() (git-fixes).\n- wifi: rtlwifi: disable ASPM for RTL8723BE with subsystem ID 11ad:1723 (git-fixes).\n- wifi: rtw88: do not ignore hardware read error during DPK (git-fixes).\n- wifi: rtw88: Do not use static local variable in rtw8822b_set_tx_power_index_by_rate (stable-fixes).\n- wifi: rtw88: Fix __rtw_download_firmware() for RTL8814AU (stable-fixes).\n- wifi: rtw88: Fix download_firmware_validate() for RTL8814AU (stable-fixes).\n- wifi: rtw88: Fix rtw_desc_to_mcsrate() to handle MCS16-31 (stable-fixes).\n- wifi: rtw88: Fix rtw_init_ht_cap() for RTL8814AU (stable-fixes).\n- wifi: rtw88: Fix rtw_init_vht_cap() for RTL8814AU (stable-fixes).\n- wifi: rtw88: fix the 'para' buffer size to avoid reading out of bounds (git-fixes).\n- wifi: rtw88: sdio: call rtw_sdio_indicate_tx_status unconditionally (git-fixes).\n- wifi: rtw88: sdio: map mgmt frames to queue TX_DESC_QSEL_MGMT (git-fixes).\n- wifi: rtw88: usb: Reduce control message timeout to 500 ms (git-fixes).\n- wifi: rtw89: 8922a: fix incorrect STA-ID in EHT MU PPDU (stable-fixes).\n- wifi: rtw89: 8922a: fix TX fail with wrong VCO setting (stable-fixes).\n- wifi: rtw89: add wiphy_lock() to work that isn't held wiphy_lock() yet (stable-fixes).\n- wifi: rtw89: call power_on ahead before selecting firmware (stable-fixes).\n- wifi: rtw89: fw: get sb_sel_ver via get_unaligned_le32() (stable-fixes).\n- wifi: rtw89: fw: propagate error code from rtw89_h2c_tx() (stable-fixes).\n- wifi: rtw89: leave idle mode when setting WEP encryption for AP mode (stable-fixes).\n- wifi: rtw89: pci: enlarge retry times of RX tag to 1000 (git-fixes).\n- wifi: rtw89: phy: add dummy C2H event handler for report of TAS power (stable-fixes).\n- wireless: purelifi: plfxlc: fix memory leak in plfxlc_usb_wreq_asyn() (stable-fixes).\n- workqueue: Initialize wq_isolated_cpumask in workqueue_init_early() (bsc#1245101 jsc#PED-11934).\n- x86: Start moving AMD node functionality out of AMD_NB (jsc#PED-13094).\n- x86/acpi: Fix LAPIC/x2APIC parsing order (git-fixes).\n- x86/amd_nb, hwmon: (k10temp): Simplify amd_pci_dev_to_node_id() (jsc#PED-13094).\n- x86/amd_nb: Clean up early_is_amd_nb() (jsc#PED-13094).\n- x86/amd_nb: Move SMN access code to a new amd_node driver (jsc#PED-13094).\n- x86/amd_nb: Restrict init function to AMD-based systems (jsc#PED-13094).\n- x86/amd_nb: Simplify function 4 search (jsc#PED-13094).\n- x86/amd_nb: Simplify root device search (jsc#PED-13094).\n- x86/amd_node: Add SMN offsets to exclusive region access (jsc#PED-13094).\n- x86/amd_node: Add support for debugfs access to SMN registers (jsc#PED-13094).\n- x86/amd_node: Remove dependency on AMD_NB (jsc#PED-13094).\n- x86/amd_node: Update __amd_smn_rw() error paths (jsc#PED-13094).\n- x86/amd_node: Use defines for SMN register offsets (jsc#PED-13094).\n- x86/fred/signal: Prevent immediate repeat of single step trap on return from SIGTRAP handler (git-fixes).\n- x86/idle: Remove MFENCEs for X86_BUG_CLFLUSH_MONITOR in mwait_idle_with_hints() and prefer_mwait_c1_over_halt() (git-fixes).\n- x86/kaslr: Reduce KASLR entropy on most x86 systems (git-fixes).\n- x86/mce/amd: Remove shared threshold bank plumbing (jsc#PED-13094).\n- x86/microcode: Consolidate the loader enablement checking (git-fixes).\n- x86/microcode/AMD: Add get_patch_level() (git-fixes).\n- x86/microcode/AMD: Do not return error when microcode update is not necessary (git-fixes).\n- x86/microcode/AMD: Get rid of the _load_microcode_amd() forward declaration (git-fixes).\n- x86/microcode/AMD: Have __apply_microcode_amd() return bool (git-fixes).\n- x86/microcode/AMD: Make __verify_patch_size() return bool (git-fixes).\n- x86/microcode/AMD: Merge early_apply_microcode() into its single callsite (git-fixes).\n- x86/microcode/AMD: Remove ugly linebreak in __verify_patch_section() signature (git-fixes).\n- x86/microcode/AMD: Return bool from find_blobs_in_containers() (git-fixes).\n- x86/mm/init: Handle the special case of device private pages in add_pages(), to not increase max_pfn and trigger dma_addressing_limited() bounce buffers (git-fixes).\n- x86/platform/amd: Move the \u0026lt;asm/amd_hsmp.h\u003e header to \u0026lt;asm/amd/hsmp.h\u003e (jsc#PED-13094).\n- x86/sev: Add SVSM vTPM probe/send_command functions (bsc#1241191).\n- x86/sev: Provide guest VMPL level to userspace (bsc#1241191).\n- x86/sev: Register tpm-svsm platform device (bsc#1241191).\n- x86/xen: fix balloon target initialization for PVH dom0 (git-fixes).\n- xen/arm: call uaccess_ttbr0_enable for dm_op hypercall (git-fixes)\n- xen/x86: fix initial memory balloon target (git-fixes).\n- xhci: dbc: Avoid event polling busyloop if pending rx transfers are inactive (git-fixes).\n- xsk: always clear DMA mapping information when unmapping the pool (git-fixes).\n","status":"published","published":"2025-07-08T15:57:51Z","modified":"2026-03-23T04:48:32.644521Z","updated_at":"2026-11-02T15:53:56.647031Z"},{"id":"SUSE-SU-2025:02307-1","title":"Security update for the Linux Kernel","description":"\nThe SUSE Linux Enterprise 15 SP7 kernel was updated to receive various security bugfixes.\n\n\nThe following security bugs were fixed:\n\n- CVE-2023-52888: media: mediatek: vcodec: Only free buffer VA that is not NULL (bsc#1228557).\n- CVE-2024-49568: net/smc: check v2_ext_offset/eid_cnt/ism_gid_cnt when receiving proposal msg (bsc#1235728).\n- CVE-2024-57982: xfrm: state: fix out-of-bounds read during lookup (bsc#1237913).\n- CVE-2024-57995: wifi: ath12k: fix read pointer after free in ath12k_mac_assign_vif_to_vdev() (bsc#1237895).\n- CVE-2024-58053: rxrpc: Fix handling of received connection abort (bsc#1238982).\n- CVE-2025-21720: xfrm: delete intermediate secpath entry in packet offload mode (bsc#1238859).\n- CVE-2025-21868: kABI workaround for adding an header (bsc#1240180).\n- CVE-2025-21898: ftrace: Avoid potential division by zero in function_stat_show() (bsc#1240610).\n- CVE-2025-21899: tracing: Fix bad hist from corrupting named_triggers list (bsc#1240577).\n- CVE-2025-21920: vlan: enforce underlying device type (bsc#1240686).\n- CVE-2025-21938: mptcp: fix 'scheduling while atomic' in mptcp_pm_nl_append_new_local_addr (bsc#1240723).\n- CVE-2025-21959: netfilter: nf_conncount: Fully initialize struct nf_conncount_tuple in insert_tree() (bsc#1240814).\n- CVE-2025-21997: xsk: fix an integer overflow in xp_create_and_assign_umem() (bsc#1240823).\n- CVE-2025-22035: tracing: Fix use-after-free in print_graph_function_flags during tracer switching (bsc#1241544).\n- CVE-2025-22111: kABI fix for net: Remove RTNL dance for SIOCBRADDIF and SIOCBRDELIF (bsc#1241572).\n- CVE-2025-22113: ext4: define ext4_journal_destroy wrapper (bsc#1241617).\n- CVE-2025-23155: net: stmmac: Fix accessing freed irq affinity_hint (bsc#1242573).\n- CVE-2025-37738: ext4: ignore xattrs past end (bsc#1242846).\n- CVE-2025-37743: wifi: ath12k: Avoid memory leak while enabling statistics (bsc#1242163).\n- CVE-2025-37752: net_sched: sch_sfq: move the limit validation (bsc#1242504).\n- CVE-2025-37756: net: tls: explicitly disallow disconnect (bsc#1242515).\n- CVE-2025-37757: tipc: fix memory leak in tipc_link_xmit (bsc#1242521).\n- CVE-2025-37786: net: dsa: free routing table on probe failure (bsc#1242725).\n- CVE-2025-37800: driver core: fix potential NULL pointer dereference in dev_uevent() (bsc#1242849).\n- CVE-2025-37801: spi: spi-imx: Add check for spi_imx_setupxfer() (bsc#1242850).\n- CVE-2025-37811: usb: chipidea: ci_hdrc_imx: fix usbmisc handling (bsc#1242907).\n- CVE-2025-37837: iommu/tegra241-cmdqv: Fix warnings due to dmam_free_coherent() (bsc#1242952).\n- CVE-2025-37844: cifs: avoid NULL pointer dereference in dbg call (bsc#1242946).\n- CVE-2025-37859: page_pool: avoid infinite loop to schedule delayed worker (bsc#1243051).\n- CVE-2025-37862: HID: pidff: Fix null pointer dereference in pidff_find_fields (bsc#1242982).\n- CVE-2025-37865: net: dsa: mv88e6xxx: fix -ENOENT when deleting VLANs and MST is unsupported (bsc#1242954).\n- CVE-2025-37874: net: ngbe: fix memory leak in ngbe_probe() error path (bsc#1242940).\n- CVE-2025-37884: bpf: Fix deadlock between rcu_tasks_trace and event_mutex (bsc#1243060).\n- CVE-2025-37909: net: lan743x: Fix memleak issue when GSO enabled (bsc#1243467).\n- CVE-2025-37917: net: ethernet: mtk-star-emac: fix spinlock recursion issues on rx/tx poll (bsc#1243475).\n- CVE-2025-37921: vxlan: vnifilter: Fix unlocked deletion of default FDB entry (bsc#1243480).\n- CVE-2025-37923: tracing: Fix oob write in trace_seq_to_buffer() (bsc#1243551).\n- CVE-2025-37927: iommu/amd: Fix potential buffer overflow in parse_ivrs_acpihid (bsc#1243620).\n- CVE-2025-37933: octeon_ep: Fix host hang issue during device reboot (bsc#1243628).\n- CVE-2025-37936: perf/x86/intel: KVM: Mask PEBS_ENABLE loaded for guest with vCPU's value (bsc#1243537).\n- CVE-2025-37938: tracing: Verify event formats that have '%*p..' (bsc#1243544).\n- CVE-2025-37945: net: phy: allow MDIO bus PM ops to start/stop state machine for phylink-controlled PHY (bsc#1243538).\n- CVE-2025-37954: smb: client: Avoid race in open_cached_dir with lease breaks (bsc#1243664).\n- CVE-2025-37961: ipvs: fix uninit-value for saddr in do_output_route4 (bsc#1243523).\n- CVE-2025-37967: usb: typec: ucsi: displayport: Fix deadlock (bsc#1243572).\n- CVE-2025-37968: iio: light: opt3001: fix deadlock due to concurrent flag access (bsc#1243571).\n- CVE-2025-37987: pds_core: Prevent possible adminq overflow/stuck condition (bsc#1243542).\n- CVE-2025-37992: net_sched: Flush gso_skb list too during -\u003echange() (bsc#1243698).\n- CVE-2025-37995: module: ensure that kobject_put() is safe for module type kobjects (bsc#1243827).\n- CVE-2025-37997: netfilter: ipset: fix region locking in hash types (bsc#1243832).\n- CVE-2025-37998: openvswitch: Fix unsafe attribute parsing in output_userspace() (bsc#1243836).\n- CVE-2025-38000: sch_hfsc: Fix qlen accounting bug when using peek in hfsc_enqueue() (bsc#1244277).\n- CVE-2025-38001: net_sched: hfsc: Address reentrant enqueue adding class to eltree twice (bsc#1244234).\n- CVE-2025-38011: drm/amdgpu: csa unmap use uninterruptible lock (bsc#1244729).\n- CVE-2025-38018: net/tls: fix kernel panic when alloc_page failed (bsc#1244999).\n- CVE-2025-38053: idpf: fix null-ptr-deref in idpf_features_check (bsc#1244746).\n- CVE-2025-38055: perf/x86/intel: Fix segfault with PEBS-via-PT with sample_freq (bsc#1244747).\n- CVE-2025-38057: espintcp: fix skb leaks (bsc#1244862).\n- CVE-2025-38060: bpf: abort verification if env-\u003ecur_state-\u003eloop_entry != NULL (bsc#1245155).\n- CVE-2025-38072: libnvdimm/labels: Fix divide error in nd_label_data_init() (bsc#1244743).\n\nThe following non-security bugs were fixed:\n\n- ACPI: Add missing prototype for non CONFIG_SUSPEND/CONFIG_X86 case (stable-fixes).\n- ACPI: CPPC: Fix NULL pointer dereference when nosmp is used (git-fixes).\n- ACPI: HED: Always initialize before evged (stable-fixes).\n- ACPI: OSI: Stop advertising support for '3.0 _SCP Extensions' (git-fixes).\n- ACPI: PNP: Add Intel OC Watchdog IDs to non-PNP device list (stable-fixes).\n- ACPI: battery: negate current when discharging (stable-fixes).\n- ACPI: bus: Bail out if acpi_kobj registration fails (stable-fixes).\n- ACPICA: Avoid sequence overread in call to strncmp() (stable-fixes).\n- ACPICA: Utilities: Fix spelling mistake 'Incremement' -\u003e 'Increment' (git-fixes).\n- ACPICA: exserial: do not forget to handle FFixedHW opregions for reading (git-fixes).\n- ACPICA: fix acpi operand cache leak in dswstate.c (stable-fixes).\n- ACPICA: fix acpi parse and parseext cache leaks (stable-fixes).\n- ACPICA: utilities: Fix overflow check in vsnprintf() (stable-fixes).\n- ALSA: hda/intel: Add Thinkpad E15 to PM deny list (stable-fixes).\n- ALSA: hda/realtek: Add quirk for HP Spectre x360 15-df1xxx (stable-fixes).\n- ALSA: hda/realtek: Add quirk for Lenovo Yoga Pro 7 14ASP10 (stable-fixes).\n- ALSA: hda/realtek: Enable PC beep passthrough for HP EliteBook 855 G7 (stable-fixes).\n- ALSA: hda/realtek: Fix built-in mic on ASUS VivoBook X507UAR (git-fixes).\n- ALSA: hda/realtek: Fix built-in mic on ASUS VivoBook X513EA (git-fixes).\n- ALSA: hda/realtek: enable headset mic on Latitude 5420 Rugged (stable-fixes).\n- ALSA: pcm: Fix race of buffer access at PCM OSS layer (stable-fixes).\n- ALSA: seq: Improve data consistency at polling (stable-fixes).\n- ALSA: usb-audio: Accept multiple protocols in GTBs (stable-fixes).\n- ALSA: usb-audio: Add Pioneer DJ DJM-V10 support (stable-fixes).\n- ALSA: usb-audio: Add a quirk for Lenovo Thinkpad Thunderbolt 3 dock (stable-fixes).\n- ALSA: usb-audio: Add implicit feedback quirk for RODE AI-1 (stable-fixes).\n- ALSA: usb-audio: Add name for HP Engage Go dock (stable-fixes).\n- ALSA: usb-audio: Check shutdown at endpoint_set_interface() (stable-fixes).\n- ALSA: usb-audio: Fix NULL pointer deref in snd_usb_power_domain_set() (git-fixes).\n- ALSA: usb-audio: Fix duplicated name in MIDI substream names (stable-fixes).\n- ALSA: usb-audio: Fix out-of-bounds read in snd_usb_get_audioformat_uac3() (git-fixes).\n- ALSA: usb-audio: Rename ALSA kcontrol PCM and PCM1 for the KTMicro sound card (stable-fixes).\n- ALSA: usb-audio: Rename Pioneer mixer channel controls (git-fixes).\n- ALSA: usb-audio: Set MIDI1 flag appropriately for GTB MIDI 1.0 entry (stable-fixes).\n- ALSA: usb-audio: Skip setting clock selector for single connections (stable-fixes).\n- ALSA: usb-audio: Support multiple control interfaces (stable-fixes).\n- ALSA: usb-audio: Support read-only clock selector control (stable-fixes).\n- ALSA: usb-audio: enable support for Presonus Studio 1824c within 1810c file (stable-fixes).\n- ALSA: usb-audio: mixer: Remove temporary string use in parse_clock_source_unit (stable-fixes).\n- ASoC: Intel: avs: Fix deadlock when the failing IPC is SET_D0IX (git-fixes).\n- ASoC: Intel: avs: Verify content returned by parse_int_array() (git-fixes).\n- ASoC: Intel: bytcr_rt5640: Add DMI quirk for Acer Aspire SW3-013 (stable-fixes).\n- ASoC: SOF: Intel: hda-bus: Use PIO mode on ACE2+ platforms (git-fixes).\n- ASoC: SOF: ipc4-pcm: Adjust pipeline_list-\u003epipelines allocation type (git-fixes).\n- ASoC: amd: yc: Add quirk for Lenovo Yoga Pro 7 14ASP9 (stable-fixes).\n- ASoC: apple: mca: Constrain channels according to TDM mask (git-fixes).\n- ASoC: codecs: hda: Fix RPM usage count underflow (git-fixes).\n- ASoC: codecs: pcm3168a: Allow for 24-bit in provider mode (stable-fixes).\n- ASoC: cs42l43: Disable headphone clamps during type detection (stable-fixes).\n- ASoC: imx-card: Adjust over allocation of memory in imx_card_parse_of() (stable-fixes).\n- ASoC: mediatek: mt6359: Add stub for mt6359_accdet_enable_jack_detect (stable-fixes).\n- ASoC: mediatek: mt8188: Add reference for dmic clocks (stable-fixes).\n- ASoC: mediatek: mt8188: Treat DMIC_GAINx_CUR as non-volatile (stable-fixes).\n- ASoC: mediatek: mt8195: Set ETDM1/2 IN/OUT to COMP_DUMMY() (git-fixes).\n- ASoC: meson: meson-card-utils: use of_property_present() for DT parsing (git-fixes).\n- ASoC: ops: Enforce platform maximum on initial value (stable-fixes).\n- ASoC: qcom: sdm845: Add error handling in sdm845_slim_snd_hw_params() (git-fixes).\n- ASoC: qcom: sm8250: explicitly set format in sm8250_be_hw_params_fixup() (stable-fixes).\n- ASoC: rt722-sdca: Add some missing readable registers (stable-fixes).\n- ASoC: soc-dai: check return value at snd_soc_dai_set_tdm_slot() (stable-fixes).\n- ASoC: sun4i-codec: support hp-det-gpios property (stable-fixes).\n- ASoC: tas2764: Add reg defaults for TAS2764_INT_CLK_CFG (stable-fixes).\n- ASoC: tas2764: Enable main IRQs (git-fixes).\n- ASoC: tas2764: Mark SW_RESET as volatile (stable-fixes).\n- ASoC: tas2764: Power up/down amp on mute ops (stable-fixes).\n- ASoC: tas2764: Reinit cache on part reset (git-fixes).\n- ASoC: tas2770: Power cycle amp on ISENSE/VSENSE change (stable-fixes).\n- ASoC: tegra210_ahub: Add check to of_device_get_match_data() (stable-fixes).\n- ASoC: ti: omap-hdmi: Re-add dai_link-\u003eplatform to fix card init (git-fixes).\n- Bluetooth: Fix NULL pointer deference on eir_get_service_data (git-fixes).\n- Bluetooth: L2CAP: Fix not responding with L2CAP_CR_LE_ENCRYPTION (git-fixes).\n- Bluetooth: MGMT: Fix UAF on mgmt_remove_adv_monitor_complete (git-fixes).\n- Bluetooth: MGMT: Fix sparse errors (git-fixes).\n- Bluetooth: MGMT: Remove unused mgmt_pending_find_data (stable-fixes).\n- Bluetooth: MGMT: iterate over mesh commands in mgmt_mesh_foreach() (git-fixes).\n- Bluetooth: Remove pending ACL connection attempts (stable-fixes).\n- Bluetooth: btintel: Check dsbr size from EFI variable (git-fixes).\n- Bluetooth: btintel_pcie: Fix driver not posting maximum rx buffers (git-fixes).\n- Bluetooth: btintel_pcie: Increase the tx and rx descriptor count (git-fixes).\n- Bluetooth: btintel_pcie: Reduce driver buffer posting to prevent race condition (git-fixes).\n- Bluetooth: eir: Fix possible crashes on eir_create_adv_data (git-fixes).\n- Bluetooth: hci_conn: Fix UAF Write in __hci_acl_create_connection_sync (git-fixes).\n- Bluetooth: hci_conn: Only do ACL connections sequentially (stable-fixes).\n- Bluetooth: hci_core: fix list_for_each_entry_rcu usage (git-fixes).\n- Bluetooth: hci_event: Fix not using key encryption size when its known (git-fixes).\n- Bluetooth: hci_qca: move the SoC type check to the right place (git-fixes).\n- Bluetooth: hci_sync: Fix UAF in hci_acl_create_conn_sync (git-fixes).\n- Bluetooth: hci_sync: Fix UAF on hci_abort_conn_sync (git-fixes).\n- Bluetooth: hci_sync: Fix broadcast/PA when using an existing instance (git-fixes).\n- Documentation/rtla: Fix duplicate text about timerlat tracer (git-fixes).\n- Documentation/rtla: Fix typo in common_timerlat_description.rst (git-fixes).\n- Documentation/rtla: Fix typo in rtla-timerlat.rst (git-fixes).\n- Documentation: ACPI: Use all-string data node references (git-fixes).\n- Documentation: fix typo in root= kernel parameter description (git-fixes).\n- HID: lenovo: Restrict F7/9/11 mode to compact keyboards only (git-fixes).\n- HID: quirks: Add ADATA XPG alpha wireless mouse support (stable-fixes).\n- HID: usbkbd: Fix the bit shift number for LED_KANA (stable-fixes).\n- HID: wacom: fix kobject reference count leak (git-fixes).\n- HID: wacom: fix memory leak on kobject creation failure (git-fixes).\n- HID: wacom: fix memory leak on sysfs attribute creation failure (git-fixes).\n- IB/cm: Drop lockdep assert and WARN when freeing old msg (git-fixes)\n- Input: gpio-keys - fix possible concurrent access in gpio_keys_irq_timer() (git-fixes).\n- Input: ims-pcu - check record size in ims_pcu_flash_firmware() (git-fixes).\n- Input: sparcspkr - avoid unannotated fall-through (stable-fixes).\n- Input: xpad - add more controllers (stable-fixes).\n- KVM: powerpc: Enable commented out BUILD_BUG_ON() assertion (bsc#1215199).\n- KVM: s390: rename PROT_NONE to PROT_TYPE_DUMMY (git-fixes bsc#1245225).\n- MyBS: Correctly generate build flags for non-multibuild package limit (bsc# 1244241) Fixes: 0999112774fc ('MyBS: Use buildflags to set which package to build')\n- MyBS: Do not build kernel-obs-qa with limit_packages Fixes: 58e3f8c34b2b ('bs-upload-kernel: Pass limit_packages also on multibuild')\n- MyBS: Simplify qa_expr generation Start with a 0 which makes the expression valid even if there are no QA repositories (currently does not happen). Then separator is always needed.\n- NFC: nci: uart: Set tty-\u003edisc_data only in success path (git-fixes).\n- NFS: Do not allow waiting for exiting tasks (git-fixes).\n- NFSD: Insulate nfsd4_encode_read_plus() from page boundaries in the encode buffer (git-fixes).\n- NFSv4: Check for delegation validity in nfs_start_delegation_return_locked() (git-fixes).\n- NFSv4: Treat ENETUNREACH errors as fatal for state recovery (git-fixes).\n- PCI/DPC: Initialize aer_err_info before using it (git-fixes).\n- PCI/DPC: Log Error Source ID only when valid (git-fixes).\n- PCI/DPC: Use defines with DPC reason fields (git-fixes).\n- PCI/MSI: Size device MSI domain with the maximum number of vectors (git-fixes).\n- PCI/PM: Set up runtime PM even for devices without PCI PM (git-fixes).\n- PCI: Add ACS quirk for Loongson PCIe (stable-fixes).\n- PCI: Explicitly put devices into D0 when initializing (git-fixes).\n- PCI: Fix lock symmetry in pci_slot_unlock() (git-fixes).\n- PCI: Fix old_size lower bound in calculate_iosize() too (stable-fixes).\n- PCI: apple: Set only available ports up (git-fixes).\n- PCI: apple: Use gpiod_set_value_cansleep in probe flow (git-fixes).\n- PCI: brcmstb: Add a softdep to MIP MSI-X driver (stable-fixes).\n- PCI: brcmstb: Expand inbound window size up to 64GB (stable-fixes).\n- PCI: cadence-ep: Correct PBA offset in .set_msix() callback (git-fixes).\n- PCI: cadence: Fix runtime atomic count underflow (git-fixes).\n- PCI: dw-rockchip: Fix PHY function call sequence in rockchip_pcie_phy_deinit() (git-fixes).\n- PCI: dw-rockchip: Remove PCIE_L0S_ENTRY check from rockchip_pcie_link_up() (git-fixes).\n- PCI: dwc: ep: Correct PBA offset in .set_msix() callback (git-fixes).\n- PCI: dwc: ep: Ensure proper iteration over outbound map windows (stable-fixes).\n- PCI: endpoint: Retain fixed-size BAR size as well as aligned size (git-fixes).\n- PCI: vmd: Disable MSI remapping bypass under Xen (stable-fixes).\n- PM: runtime: fix denying of auto suspend in pm_suspend_timer_fn() (stable-fixes).\n- PM: sleep: Fix power.is_suspended cleanup for direct-complete devices (git-fixes).\n- PM: sleep: Print PM debug messages during hibernation (git-fixes).\n- PM: wakeup: Delete space in the end of string shown by pm_show_wakelocks() (git-fixes).\n- RDMA/core: Fix best page size finding when it can cross SG entries (git-fixes)\n- RDMA/uverbs: Propagate errors from rdma_lookup_get_uobject() (git-fixes)\n- Remove compress-vmlinux.sh /usr/lib/rpm/brp-suse.d/brp-99-compress-vmlinux was added in pesign-obs-integration during SLE12 RC. This workaround can be removed.\n- Remove host-memcpy-hack.h This might have been usefult at some point but we have more things that depend on specific library versions today.\n- Remove try-disable-staging-driver The config for linux-next is autogenerated from master config, and defaults filled for missing options. This is unlikely to enable any staging driver in the first place.\n- Revert 'ALSA: usb-audio: Skip setting clock selector for single connections' (stable-fixes).\n- Revert 'arm64: dts: allwinner: h6: Use RSB for AXP805 PMIC (git-fixes)\n- Revert 'bus: ti-sysc: Probe for l4_wkup and l4_cfg interconnect devices first' (stable-fixes).\n- Revert 'drm/amdgpu: do not allow userspace to create a doorbell BO' (stable-fixes).\n- Revert 'ipv6: save dontfrag in cork (git-fixes).'\n- Revert 'kABI: ipv6: save dontfrag in cork (git-fixes).'\n- Revert 'wifi: mt76: mt7996: fill txd by host driver' (stable-fixes).\n- Revert 'wifi: mwifiex: Fix HT40 bandwidth issue.' (git-fixes).\n- SUNRPC: Do not allow waiting for exiting tasks (git-fixes).\n- SUNRPC: Prevent hang on NFS mount with xprtsec=[m]tls (git-fixes).\n- SUNRPC: rpc_clnt_set_transport() must not change the autobind setting (git-fixes).\n- SUNRPC: rpcbind should never reset the port to the value '0' (git-fixes).\n- USB: serial: pl2303: add new chip PL2303GC-Q20 and PL2303GT-2AB (stable-fixes).\n- VMCI: fix race between vmci_host_setup_notify and vmci_ctx_unset_notify (git-fixes).\n- accel/ivpu: Improve buffer object logging (git-fixes).\n- accel/ivpu: Use dma_resv_lock() instead of a custom mutex (git-fixes).\n- accel/qaic: Mask out SR-IOV PCI resources (stable-fixes).\n- acpi-cpufreq: Fix nominal_freq units to KHz in get_max_boost_ratio() (git-fixes).\n- add bug reference to existing hv_storvsc change (bsc#1245455).\n- arm64: dts: marvell: uDPU: define pinctrl state for alarm LEDs (git-fixes)\n- ata: libata-eh: Do not use ATAPI DMA for a device limited to PIO mode (stable-fixes).\n- ata: pata_via: Force PIO for ATAPI devices on VT6415/VT6330 (stable-fixes).\n- ath10k: snoc: fix unbalanced IRQ enable in crash recovery (git-fixes).\n- backlight: pm8941: Add NULL check in wled_configure() (git-fixes).\n- bnxt: properly flush XDP redirect lists (git-fixes).\n- bpf: Force uprobe bpf program to always return 0 (git-fixes).\n- bs-upload-kernel: Pass limit_packages also on multibuild Fixes: 0999112774fc ('MyBS: Use buildflags to set which package to build') Fixes: 747f601d4156 ('bs-upload-kernel, MyBS, Buildresults: Support multibuild (JSC-SLE#5501, boo#1211226, bsc#1218184)')\n- btrfs: fix fsync of files with no hard links not persisting deletion (git-fixes).\n- btrfs: fix invalid data space release when truncating block in NOCOW mode (git-fixes).\n- btrfs: fix qgroup reservation leak on failure to allocate ordered extent (git-fixes).\n- btrfs: fix wrong start offset for delalloc space release during mmap write (git-fixes).\n- btrfs: remove end_no_trans label from btrfs_log_inode_parent() (git-fixes).\n- btrfs: simplify condition for logging new dentries at btrfs_log_inode_parent() (git-fixes).\n- bus: fsl-mc: do not add a device-link for the UAPI used DPMCP device (git-fixes).\n- bus: fsl-mc: fix GET/SET_TAILDROP command ids (git-fixes).\n- bus: fsl-mc: fix double-free on mc_dev (git-fixes).\n- bus: fsl-mc: increase MC_CMD_COMPLETION_TIMEOUT_MS value (stable-fixes).\n- bus: mhi: host: Fix conflict between power_up and SYSERR (git-fixes).\n- calipso: Fix null-ptr-deref in calipso_req_{set,del}attr() (git-fixes).\n- can: c_can: Use of_property_present() to test existence of DT property (stable-fixes).\n- can: tcan4x5x: fix power regulator retrieval during probe (git-fixes).\n- ceph: Fix incorrect flush end position calculation (git-fixes).\n- ceph: allocate sparse_ext map only for sparse reads (git-fixes).\n- ceph: fix memory leaks in __ceph_sync_read() (git-fixes).\n- cgroup/cpuset: Do not allow creation of local partition over a remote one (bsc#1241166).\n- cgroup/cpuset: Fix race between newly created partition and dying one (bsc#1241166).\n- cifs: change tcon status when need_reconnect is set on it (git-fixes).\n- clocksource: Fix brown-bag boolean thinko in (git-fixes)\n- clocksource: Make watchdog and suspend-timing multiplication (git-fixes)\n- crypto: lrw - Only add ecb if it is not already there (git-fixes).\n- crypto: lzo - Fix compression buffer overrun (stable-fixes).\n- crypto: marvell/cesa - Avoid empty transfer descriptor (git-fixes).\n- crypto: marvell/cesa - Do not chain submitted requests (git-fixes).\n- crypto: marvell/cesa - Handle zero-length skcipher requests (git-fixes).\n- crypto: octeontx2 - suppress auth failure screaming due to negative tests (stable-fixes).\n- crypto: qat - add shutdown handler to qat_420xx (git-fixes).\n- crypto: qat - add shutdown handler to qat_4xxx (git-fixes).\n- crypto: skcipher - Zap type in crypto_alloc_sync_skcipher (stable-fixes).\n- crypto: sun8i-ce - move fallback ahash_request to the end of the struct (git-fixes).\n- crypto: sun8i-ce-cipher - fix error handling in sun8i_ce_cipher_prepare() (git-fixes).\n- crypto: sun8i-ss - do not use sg_dma_len before calling DMA functions (git-fixes).\n- crypto: xts - Only add ecb if it is not already there (git-fixes).\n- devlink: Fix referring to hw_addr attribute during state validation (git-fixes).\n- devlink: fix port dump cmd type (git-fixes).\n- dlm: mask sk_shutdown value (bsc#1228854).\n- dlm: use SHUT_RDWR for SCTP shutdown (bsc#1228854).\n- dmaengine: idxd: cdev: Fix uninitialized use of sva in idxd_cdev_open (stable-fixes).\n- dmaengine: ti: Add NULL check in udma_probe() (git-fixes).\n- drivers/rapidio/rio_cm.c: prevent possible heap overwrite (stable-fixes).\n- drm/amd/display/dm: drop hw_support check in amdgpu_dm_i2c_xfer() (stable-fixes).\n- drm/amd/display: Add debugging message for brightness caps (bsc#1240650).\n- drm/amd/display: Add null pointer check for get_first_active_display() (git-fixes).\n- drm/amd/display: Add support for disconnected eDP streams (stable-fixes).\n- drm/amd/display: Call FP Protect Before Mode Programming/Mode Support (stable-fixes).\n- drm/amd/display: Configure DTBCLK_P with OPTC only for dcn401 (stable-fixes).\n- drm/amd/display: Correct timing_adjust_pending flag setting (stable-fixes).\n- drm/amd/display: Defer BW-optimization-blocked DRR adjustments (git-fixes).\n- drm/amd/display: Do not enable replay when vtotal update is pending (stable-fixes).\n- drm/amd/display: Do not treat wb connector as physical in create_validate_stream_for_sink (stable-fixes).\n- drm/amd/display: Do not try AUX transactions on disconnected link (stable-fixes).\n- drm/amd/display: Ensure DMCUB idle before reset on DCN31/DCN35 (stable-fixes).\n- drm/amd/display: Fix BT2020 YCbCr limited/full range input (stable-fixes).\n- drm/amd/display: Fix DMUB reset sequence for DCN401 (stable-fixes).\n- drm/amd/display: Fix default DC and AC levels (bsc#1240650).\n- drm/amd/display: Fix incorrect DPCD configs while Replay/PSR switch (stable-fixes).\n- drm/amd/display: Fix p-state type when p-state is unsupported (stable-fixes).\n- drm/amd/display: Guard against setting dispclk low for dcn31x (stable-fixes).\n- drm/amd/display: Guard against setting dispclk low when active (stable-fixes).\n- drm/amd/display: Increase block_sequence array size (stable-fixes).\n- drm/amd/display: Initial psr_version with correct setting (stable-fixes).\n- drm/amd/display: Populate register address for dentist for dcn401 (stable-fixes).\n- drm/amd/display: Read LTTPR ALPM caps during link cap retrieval (stable-fixes).\n- drm/amd/display: Request HW cursor on DCN3.2 with SubVP (stable-fixes).\n- drm/amd/display: Skip checking FRL_MODE bit for PCON BW determination (stable-fixes).\n- drm/amd/display: Support multiple options during psr entry (stable-fixes).\n- drm/amd/display: Update CR AUX RD interval interpretation (stable-fixes).\n- drm/amd/display: Use Nominal vBlank If Provided Instead Of Capping It (stable-fixes).\n- drm/amd/display: calculate the remain segments for all pipes (stable-fixes).\n- drm/amd/display: check stream id dml21 wrapper to get plane_id (stable-fixes).\n- drm/amd/display: fix dcn4x init failed (stable-fixes).\n- drm/amd/display: fix link_set_dpms_off multi-display MST corner case (stable-fixes).\n- drm/amd/display: handle max_downscale_src_width fail check (stable-fixes).\n- drm/amd/display: not abort link train when bw is low (stable-fixes).\n- drm/amd/display: pass calculated dram_speed_mts to dml2 (stable-fixes).\n- drm/amd/display: remove minimum Dispclk and apply oem panel timing (stable-fixes).\n- drm/amd/pm: Fetch current power limit from PMFW (stable-fixes).\n- drm/amd/pm: Skip P2S load for SMU v13.0.12 (stable-fixes).\n- drm/amd/pp: Fix potential NULL pointer dereference in atomctrl_initialize_mc_reg_table (git-fixes).\n- drm/amd: Adjust output for discovery error handling (git-fixes).\n- drm/amdgpu/discovery: check ip_discovery fw file available (stable-fixes).\n- drm/amdgpu/gfx11: do not read registers in mqd init (stable-fixes).\n- drm/amdgpu/gfx12: do not read registers in mqd init (stable-fixes).\n- drm/amdgpu/mes11: fix set_hw_resources_1 calculation (stable-fixes).\n- drm/amdgpu: Allow P2P access through XGMI (stable-fixes).\n- drm/amdgpu: Do not program AGP BAR regs under SRIOV in gfxhub_v1_0.c (stable-fixes).\n- drm/amdgpu: Fix missing drain retry fault the last entry (stable-fixes).\n- drm/amdgpu: Fix the race condition for draining retry fault (stable-fixes).\n- drm/amdgpu: Set snoop bit for SDMA for MI series (stable-fixes).\n- drm/amdgpu: Skip pcie_replay_count sysfs creation for VF (stable-fixes).\n- drm/amdgpu: Update SRIOV video codec caps (stable-fixes).\n- drm/amdgpu: Use active umc info from discovery (stable-fixes).\n- drm/amdgpu: adjust drm_firmware_drivers_only() handling (stable-fixes).\n- drm/amdgpu: enlarge the VBIOS binary size limit (stable-fixes).\n- drm/amdgpu: read back register after written for VCN v4.0.5 (stable-fixes).\n- drm/amdgpu: release xcp_mgr on exit (stable-fixes).\n- drm/amdgpu: remove all KFD fences from the BO on release (stable-fixes).\n- drm/amdgpu: reset psp-\u003ecmd to NULL after releasing the buffer (stable-fixes).\n- drm/amdgpu: switch job hw_fence to amdgpu_fence (git-fixes).\n- drm/amdkfd: Correct F8_MODE for gfx950 (git-fixes).\n- drm/amdkfd: KFD release_work possible circular locking (stable-fixes).\n- drm/amdkfd: Set per-process flags only once cik/vi (stable-fixes).\n- drm/amdkfd: Set per-process flags only once for gfx9/10/11/12 (stable-fixes).\n- drm/amdkfd: fix missing L2 cache info in topology (stable-fixes).\n- drm/amdkfd: set precise mem ops caps to disabled for gfx 11 and 12 (stable-fixes).\n- drm/ast: Find VBIOS mode from regular display size (stable-fixes).\n- drm/ast: Fix comment on modeset lock (git-fixes).\n- drm/atomic: clarify the rules around drm_atomic_state-\u003eallow_modeset (stable-fixes).\n- drm/bridge: cdns-dsi: Check return value when getting default PHY config (git-fixes).\n- drm/bridge: cdns-dsi: Fix connecting to next bridge (git-fixes).\n- drm/bridge: cdns-dsi: Fix phy de-init and flag it so (git-fixes).\n- drm/bridge: cdns-dsi: Fix the clock variable for mode_valid() (git-fixes).\n- drm/bridge: cdns-dsi: Wait for Clk and Data Lanes to be ready (git-fixes).\n- drm/bridge: lt9611uxc: Fix an error handling path in lt9611uxc_probe() (git-fixes).\n- drm/buddy: fix issue that force_merge cannot free all roots (stable-fixes).\n- drm/etnaviv: Protect the scheduler's pending list with its lock (git-fixes).\n- drm/i915/gem: Allow EXEC_CAPTURE on recoverable contexts on DG1 (git-fixes).\n- drm/i915/guc: Check if expecting reply before decrementing outstanding_submission_g2h (git-fixes).\n- drm/i915/guc: Handle race condition where wakeref count drops below 0 (git-fixes).\n- drm/i915/pmu: Fix build error with GCOV and AutoFDO enabled (git-fixes).\n- drm/i915/psr: Fix using wrong mask in REG_FIELD_PREP (git-fixes).\n- drm/i915: fix build error some more (git-fixes).\n- drm/mediatek: Fix kobject put for component sub-drivers (git-fixes).\n- drm/mediatek: mtk_dpi: Add checks for reg_h_fre_con existence (stable-fixes).\n- drm/mediatek: mtk_drm_drv: Fix kobject put for mtk_mutex device ptr (git-fixes).\n- drm/mediatek: mtk_drm_drv: Unbind secondary mmsys components on err (git-fixes).\n- drm/msm/a6xx: Disable rgb565_predicator on Adreno 7c3 (git-fixes).\n- drm/msm/a7xx: Call CP_RESET_CONTEXT_STATE (git-fixes).\n- drm/msm/disp: Correct porch timing for SDM845 (git-fixes).\n- drm/msm/dpu: Clear CTL_FETCH_PIPE_ACTIVE before blend setup (git-fixes).\n- drm/msm/dpu: Clear CTL_FETCH_PIPE_ACTIVE on ctl_path reset (git-fixes).\n- drm/msm/dpu: enable SmartDMA on SC8180X (git-fixes).\n- drm/msm/dpu: enable SmartDMA on SM8150 (git-fixes).\n- drm/msm/dsi/dsi_phy_10nm: Fix missing initial VCO rate (git-fixes).\n- drm/msm/gpu: Fix crash when throttling GPU immediately during boot (git-fixes).\n- drm/msm: Fix CP_RESET_CONTEXT_STATE bitfield names (git-fixes).\n- drm/nouveau/bl: increase buffer size to avoid truncate warning (git-fixes).\n- drm/nouveau: fix the broken marco GSP_MSG_MAX_SIZE (stable-fixes).\n- drm/panel-edp: Add Starry 116KHD024006 (stable-fixes).\n- drm/panel-simple: fix the warnings for the Evervision VGG644804 (git-fixes).\n- drm/panel: samsung-sofef00: Drop s6e3fc2x01 support (git-fixes).\n- drm/panic: add missing space (git-fixes).\n- drm/panthor: Fix GPU_COHERENCY_ACE[_LITE] definitions (git-fixes).\n- drm/panthor: Update panthor_mmu::irq::mask when needed (git-fixes).\n- drm/rockchip: vop2: Add uv swap for cluster window (stable-fixes).\n- drm/rockchip: vop2: Improve display modes handling on RK3588 HDMI0 (stable-fixes).\n- drm/ssd130x: fix ssd132x_clear_screen() columns (git-fixes).\n- drm/tegra: Assign plane type before registration (git-fixes).\n- drm/tegra: Fix a possible null pointer dereference (git-fixes).\n- drm/tegra: rgb: Fix the unbound reference count (git-fixes).\n- drm/udl: Unregister device before cleaning up on disconnect (git-fixes).\n- drm/v3d: Add clock handling (stable-fixes).\n- drm/v3d: Avoid NULL pointer dereference in `v3d_job_update_stats()` (stable-fixes).\n- drm/vc4: tests: Use return instead of assert (git-fixes).\n- drm/vkms: Adjust vkms_state-\u003eactive_planes allocation type (git-fixes).\n- drm/vmwgfx: Add error path for xa_store in vmw_bo_add_detached_resource (git-fixes).\n- drm/vmwgfx: Add seqno waiter for sync_files (git-fixes).\n- drm/vmwgfx: Fix dumb buffer leak (git-fixes).\n- drm/xe/bmg: Update Wa_16023588340 (git-fixes).\n- drm/xe/d3cold: Set power state to D3Cold during s2idle/s3 (git-fixes).\n- drm/xe/debugfs: Add missing xe_pm_runtime_put in wedge_mode_set (stable-fixes).\n- drm/xe/debugfs: fixed the return value of wedged_mode_set (stable-fixes).\n- drm/xe/display: Add check for alloc_ordered_workqueue() (git-fixes).\n- drm/xe/gt: Update handling of xe_force_wake_get return (stable-fixes).\n- drm/xe/oa: Ensure that polled read returns latest data (stable-fixes).\n- drm/xe/pf: Create a link between PF and VF devices (stable-fixes).\n- drm/xe/pf: Reset GuC VF config when unprovisioning critical resource (stable-fixes).\n- drm/xe/relay: Do not use GFP_KERNEL for new transactions (stable-fixes).\n- drm/xe/sa: Always call drm_suballoc_manager_fini() (stable-fixes).\n- drm/xe/sched: stop re-submitting signalled jobs (git-fixes).\n- drm/xe/vf: Retry sending MMIO request to GUC on timeout error (stable-fixes).\n- drm/xe/vm: move rebind_work init earlier (git-fixes).\n- drm/xe/xe2hpg: Add Wa_22021007897 (stable-fixes).\n- drm/xe: Create LRC BO without VM (git-fixes).\n- drm/xe: Do not attempt to bootstrap VF in execlists mode (stable-fixes).\n- drm/xe: Fix memset on iomem (git-fixes).\n- drm/xe: Fix xe_tile_init_noalloc() error propagation (stable-fixes).\n- drm/xe: Make xe_gt_freq part of the Documentation (git-fixes).\n- drm/xe: Move suballocator init to after display init (stable-fixes).\n- drm/xe: Nuke VM's mapping upon close (stable-fixes).\n- drm/xe: Process deferred GGTT node removals on device unwind (git-fixes).\n- drm/xe: Reject BO eviction if BO is bound to current VM (stable-fixes).\n- drm/xe: Retry BO allocation (stable-fixes).\n- drm/xe: Rework eviction rejection of bound external bos (git-fixes).\n- drm/xe: Save the gt pointer in lrc and drop the tile (stable-fixes).\n- drm/xe: Stop ignoring errors from xe_ttm_stolen_mgr_init() (stable-fixes).\n- drm/xe: Wire up device shutdown handler (stable-fixes).\n- drm/xe: remove unmatched xe_vm_unlock() from __xe_exec_queue_init() (git-fixes).\n- drm/xe: xe_gen_wa_oob: replace program_invocation_short_name (stable-fixes).\n- drm: Add valid clones check (stable-fixes).\n- drm: bridge: adv7511: fill stream capabilities (stable-fixes).\n- drm: rcar-du: Fix memory leak in rcar_du_vsps_init() (git-fixes).\n- dummycon: Trigger redraw when switching consoles with deferred takeover (git-fixes).\n- e1000e: set fixed clock frequency indication for Nahum 11 and Nahum 13 (git-fixes).\n- efi/libstub: Describe missing 'out' parameter in efi_load_initrd (git-fixes).\n- fbcon: Make sure modelist not set on unregistered console (stable-fixes).\n- fbcon: Use correct erase colour for clearing in fbcon (stable-fixes).\n- fbdev/efifb: Remove PM for parent device (bsc#1244261).\n- fbdev: Fix do_register_framebuffer to prevent null-ptr-deref in fb_videomode_to_var (git-fixes).\n- fbdev: Fix fb_set_var to prevent null-ptr-deref in fb_videomode_to_var (git-fixes).\n- fbdev: core: fbcvt: avoid division by 0 in fb_cvt_hperiod() (git-fixes).\n- fbdev: core: tileblit: Implement missing margin clearing for tileblit (stable-fixes).\n- fbdev: fsl-diu-fb: add missing device_remove_file() (stable-fixes).\n- fgraph: Still initialize idle shadow stacks when starting (git-fixes).\n- firmware: SDEI: Allow sdei initialization without ACPI_APEI_GHES (git-fixes).\n- firmware: arm_ffa: Reject higher major version as incompatible (stable-fixes).\n- firmware: arm_ffa: Set dma_mask for ffa devices (stable-fixes).\n- firmware: arm_scmi: Relax duplicate name constraint across protocol ids (stable-fixes).\n- firmware: psci: Fix refcount leak in psci_dt_init (git-fixes).\n- fpga: altera-cvp: Increase credit timeout (stable-fixes).\n- fs/nfs/read: fix double-unlock bug in nfs_return_empty_folio() (git-fixes).\n- gpio: mlxbf3: only get IRQ for device instance 0 (git-fixes).\n- gpio: pca953x: Simplify code with cleanup helpers (stable-fixes).\n- gpio: pca953x: Split pca953x_restore_context() and pca953x_save_context() (stable-fixes).\n- gpio: pca953x: fix IRQ storm on system wake up (git-fixes).\n- gpiolib: Revert 'Do not WARN on gpiod_put() for optional GPIO' (stable-fixes).\n- gve: Fix RX_BUFFERS_POSTED stat to report per-queue fill_cnt (git-fixes).\n- gve: add missing NULL check for gve_alloc_pending_packet() in TX DQO (git-fixes).\n- hwmon: (asus-ec-sensors) check sensor index in read_string() (git-fixes).\n- hwmon: (dell-smm) Increment the number of fans (stable-fixes).\n- hwmon: (ftsteutates) Fix TOCTOU race in fts_read() (git-fixes).\n- hwmon: (gpio-fan) Add missing mutex locks (stable-fixes).\n- hwmon: (nct6775): Actually make use of the HWMON_NCT6775 symbol namespace (git-fixes).\n- hwmon: (occ) Rework attribute registration for stack usage (git-fixes).\n- hwmon: (occ) fix unaligned accesses (git-fixes).\n- hwmon: (peci/dimmtemp) Do not provide fake thresholds data (git-fixes).\n- hwmon: (xgene-hwmon) use appropriate type for the latency value (stable-fixes).\n- hwmon: corsair-psu: add USB id of HX1200i Series 2023 psu (git-fixes).\n- i2c: designware: Invoke runtime suspend on quick slave re-registration (stable-fixes).\n- i2c: npcm: Add clock toggle recovery (stable-fixes).\n- i2c: pxa: fix call balance of i2c-\u003eclk handling routines (stable-fixes).\n- i2c: qup: Vote for interconnect bandwidth to DRAM (stable-fixes).\n- i2c: robotfuzz-osif: disable zero-length read messages (git-fixes).\n- i2c: tegra: check msg length in SMBUS block read (bsc#1242086)\n- i2c: tiny-usb: disable zero-length read messages (git-fixes).\n- i3c: master: svc: Fix implicit fallthrough in svc_i3c_master_ibi_work() (git-fixes).\n- i3c: master: svc: Fix missing STOP for master request (stable-fixes).\n- i3c: master: svc: Flush FIFO before sending Dynamic Address Assignment(DAA) (stable-fixes).\n- i40e: retry VFLR handling if there is ongoing VF reset (git-fixes).\n- i40e: return false from i40e_reset_vf if reset is in progress (git-fixes).\n- ice: Fix LACP bonds without SRIOV environment (git-fixes).\n- ice: create new Tx scheduler nodes for new queues only (git-fixes).\n- ice: fix Tx scheduler error handling in XDP callback (git-fixes).\n- ice: fix rebuilding the Tx scheduler tree for large queue counts (git-fixes).\n- ice: fix vf-\u003enum_mac count with port representors (git-fixes).\n- ieee802154: ca8210: Use proper setters and getters for bitwise types (stable-fixes).\n- iio: accel: fxls8962af: Fix temperature scan element sign (git-fixes).\n- iio: adc: ad7124: Fix 3dB filter frequency reading (git-fixes).\n- iio: adc: ad7606_spi: fix reg write value mask (git-fixes).\n- iio: filter: admv8818: Support frequencies \u003e= 2^32 (git-fixes).\n- iio: filter: admv8818: fix band 4, state 15 (git-fixes).\n- iio: filter: admv8818: fix integer overflow (git-fixes).\n- iio: filter: admv8818: fix range calculation (git-fixes).\n- iio: imu: inv_icm42600: Fix temperature calculation (git-fixes).\n- ima: Suspend PCR extends and log appends when rebooting (bsc#1210025 ltc#196650).\n- ima: process_measurement() needlessly takes inode_lock() on MAY_READ (stable-fixes).\n- intel_th: avoid using deprecated page-\u003emapping, index fields (stable-fixes).\n- iommu: Protect against overflow in iommu_pgsize() (git-fixes).\n- iommu: Skip PASID validation for devices without PASID capability (bsc#1244100)\n- iommu: Validate the PASID in iommu_attach_device_pasid() (bsc#1244100)\n- ip6mr: fix tables suspicious RCU usage (git-fixes).\n- ip_tunnel: annotate data-races around t-\u003eparms.link (git-fixes).\n- ipmr: fix incorrect parameter validation in the ip_mroute_getsockopt() function (git-fixes).\n- ipmr: fix tables suspicious RCU usage (git-fixes).\n- ipv4: Convert ip_route_input() to dscp_t (git-fixes).\n- ipv4: Correct/silence an endian warning in __ip_do_redirect (git-fixes).\n- ipv6: save dontfrag in cork (git-fixes).\n- ipvs: Always clear ipvs_property flag in skb_scrub_packet() (git-fixes).\n- isolcpus: fix bug in returning number of allocated cpumask (bsc#1243774).\n- jffs2: check jffs2_prealloc_raw_node_refs() result in few other places (git-fixes).\n- jffs2: check that raw node were preallocated before writing summary (git-fixes).\n- kABI workaround for hda_codec.beep_just_power_on flag (git-fixes).\n- kABI: PCI: endpoint: Retain fixed-size BAR size as well as aligned size (git-fixes).\n- kABI: ipv6: save dontfrag in cork (git-fixes).\n- kABI: serial: mctrl_gpio: split disable_ms into sync and no_sync APIs (git-fixes).\n- kabi: restore layout of struct cgroup_subsys (bsc#1241166).\n- kabi: restore layout of struct mem_control (jsc#PED-12551).\n- kabi: restore layout of struct page_counter (jsc#PED-12551).\n- kernel-source: Do not use multiple -r in sed parameters\n- kernel-source: Remove log.sh from sources\n- leds: pwm-multicolor: Add check for fwnode_property_read_u32 (stable-fixes).\n- loop: Add sanity check for read/write_iter (git-fixes).\n- loop: add file_start_write() and file_end_write() (git-fixes).\n- mailbox: use error ret code of of_parse_phandle_with_args() (stable-fixes).\n- md/raid1,raid10: do not handle IO error for REQ_RAHEAD and REQ_NOWAIT (git-fixes).\n- md/raid1: Add check for missing source disk in process_checks() (git-fixes).\n- media: adv7180: Disable test-pattern control on adv7180 (stable-fixes).\n- media: c8sectpfe: Call of_node_put(i2c_bus) only once in c8sectpfe_probe() (stable-fixes).\n- media: ccs-pll: Check for too high VT PLL multiplier in dual PLL case (git-fixes).\n- media: ccs-pll: Correct the upper limit of maximum op_pre_pll_clk_div (git-fixes).\n- media: ccs-pll: Start OP pre-PLL multiplier search from correct value (git-fixes).\n- media: ccs-pll: Start VT pre-PLL multiplier search from correct value (git-fixes).\n- media: cx231xx: set device_caps for 417 (stable-fixes).\n- media: cxusb: no longer judge rbuf when the write fails (git-fixes).\n- media: davinci: vpif: Fix memory leak in probe error path (git-fixes).\n- media: gspca: Add error handling for stv06xx_read_sensor() (git-fixes).\n- media: i2c: imx219: Correct the minimum vblanking value (stable-fixes).\n- media: imx-jpeg: Cleanup after an allocation error (git-fixes).\n- media: imx-jpeg: Drop the first error frames (git-fixes).\n- media: imx-jpeg: Move mxc_jpeg_free_slot_data() ahead (git-fixes).\n- media: imx-jpeg: Reset slot data pointers when freed (git-fixes).\n- media: intel/ipu6: Fix dma mask for non-secure mode (git-fixes).\n- media: ipu6: Remove workaround for Meteor Lake ES2 (git-fixes).\n- media: nxp: imx8-isi: better handle the m2m usage_count (git-fixes).\n- media: omap3isp: use sgtable-based scatterlist wrappers (git-fixes).\n- media: ov2740: Move pm-runtime cleanup on probe-errors to proper place (git-fixes).\n- media: ov5675: suppress probe deferral errors (git-fixes).\n- media: ov8856: suppress probe deferral errors (git-fixes).\n- media: platform: mtk-mdp3: Remove unused mdp_get_plat_device (git-fixes).\n- media: qcom: camss: csid: Only add TPG v4l2 ctrl if TPG hardware is available (stable-fixes).\n- media: rkvdec: Fix frame size enumeration (git-fixes).\n- media: tc358746: improve calculation of the D-PHY timing registers (stable-fixes).\n- media: test-drivers: vivid: do not call schedule in loop (stable-fixes).\n- media: uvcvideo: Add sanity check to uvc_ioctl_xu_ctrl_map (stable-fixes).\n- media: uvcvideo: Fix deferred probing error (git-fixes).\n- media: uvcvideo: Handle uvc menu translation inside uvc_get_le_value (stable-fixes).\n- media: uvcvideo: Return the number of processed controls (git-fixes).\n- media: v4l2-dev: fix error handling in __video_register_device() (git-fixes).\n- media: v4l: Memset argument to 0 before calling get_mbus_config pad op (stable-fixes).\n- media: venus: Fix probe error handling (git-fixes).\n- media: verisilicon: Free post processor buffers on error (git-fixes).\n- media: videobuf2: use sgtable-based scatterlist wrappers (git-fixes).\n- media: vidtv: Terminating the subsequent process of initialization failure (git-fixes).\n- media: vivid: Change the siize of the composing (git-fixes).\n- mfd: exynos-lpass: Avoid calling exynos_lpass_disable() twice in exynos_lpass_remove() (git-fixes).\n- mfd: stmpe-spi: Correct the name used in MODULE_DEVICE_TABLE (git-fixes).\n- mfd: tps65219: Remove TPS65219_REG_TI_DEV_ID check (stable-fixes).\n- mkspec: Exclude rt flavor from kernel-syms dependencies (bsc#1244337).\n- mm, memcg: cg2 memory{.swap,}.peak write handlers (jsc#PED-12551).\n- mm/hugetlb: fix huge_pmd_unshare() vs GUP-fast race (bsc#1245431).\n- mm/hugetlb: unshare page tables during VMA split, not before (bsc#1245431).\n- mm/memcontrol: export memcg.swap watermark via sysfs for v2 memcg (jsc#PED-12551).\n- mmc: Add quirk to disable DDR50 tuning (stable-fixes).\n- mmc: dw_mmc: add exynos7870 DW MMC support (stable-fixes).\n- mmc: host: Wait for Vdd to settle on card power off (stable-fixes).\n- mmc: sdhci: Disable SD card clock before changing parameters (stable-fixes).\n- mtd: nand: ecc-mxic: Fix use of uninitialized variable ret (git-fixes).\n- mtd: nand: sunxi: Add randomizer configuration before randomizer enable (git-fixes).\n- mtd: rawnand: sunxi: Add randomizer configuration in sunxi_nfc_hw_ecc_write_chunk (git-fixes).\n- neighbour: Do not let neigh_forced_gc() disable preemption for long (git-fixes).\n- net/mdiobus: Fix potential out-of-bounds clause 45 read/write access (git-fixes).\n- net/mdiobus: Fix potential out-of-bounds read/write access (git-fixes).\n- net/mlx4_en: Prevent potential integer overflow calculating Hz (git-fixes).\n- net/mlx5: Add error handling in mlx5_query_nic_vport_node_guid() (git-fixes).\n- net/mlx5: Ensure fw pages are always allocated on same NUMA (git-fixes).\n- net/mlx5: Fix ECVF vports unload on shutdown flow (git-fixes).\n- net/mlx5: Fix return value when searching for existing flow group (git-fixes).\n- net/mlx5_core: Add error handling inmlx5_query_nic_vport_qkey_viol_cntr() (git-fixes).\n- net/mlx5e: Fix leak of Geneve TLV option object (git-fixes).\n- net/neighbor: clear error in case strict check is not set (git-fixes).\n- net/sched: fix use-after-free in taprio_dev_notifier (git-fixes).\n- net: Fix TOCTOU issue in sk_is_readable() (git-fixes).\n- net: Implement missing getsockopt(SO_TIMESTAMPING_NEW) (git-fixes).\n- net: add rcu safety to rtnl_prop_list_size() (git-fixes).\n- net: fix udp gso skb_segment after pull from frag_list (git-fixes).\n- net: give more chances to rcu in netdev_wait_allrefs_any() (git-fixes).\n- net: ice: Perform accurate aRFS flow match (git-fixes).\n- net: ipv4: fix a memleak in ip_setup_cork (git-fixes).\n- net: linkwatch: use system_unbound_wq (git-fixes).\n- net: mana: Add support for Multi Vports on Bare metal (bsc#1244229).\n- net: mana: Record doorbell physical address in PF mode (bsc#1244229).\n- net: page_pool: fix warning code (git-fixes).\n- net: phy: clear phydev-\u003edevlink when the link is deleted (git-fixes).\n- net: phy: fix up const issues in to_mdio_device() and to_phy_device() (git-fixes).\n- net: phy: move phy_link_change() prior to mdio_bus_phy_may_suspend() (bsc#1243538)\n- net: phy: mscc: Fix memory leak when using one step timestamping (git-fixes).\n- net: phy: mscc: Stop clearing the the UDPv4 checksum for L2 frames (git-fixes).\n- net: sched: cls_u32: Fix allocation size in u32_init() (git-fixes).\n- net: sched: consistently use rcu_replace_pointer() in taprio_change() (git-fixes).\n- net: sched: em_text: fix possible memory leak in em_text_destroy() (git-fixes).\n- net: sched: fix erspan_opt settings in cls_flower (git-fixes).\n- net: usb: aqc111: debug info before sanitation (git-fixes).\n- net: usb: aqc111: fix error handling of usbnet read calls (git-fixes).\n- net: wwan: t7xx: Fix napi rx poll issue (git-fixes).\n- net_sched: ets: fix a race in ets_qdisc_change() (git-fixes).\n- net_sched: prio: fix a race in prio_tune() (git-fixes).\n- net_sched: red: fix a race in __red_change() (git-fixes).\n- net_sched: sch_fifo: implement lockless __fifo_dump() (bsc#1237312)\n- net_sched: sch_sfq: reject invalid perturb period (git-fixes).\n- net_sched: sch_sfq: use a temporary work area for validating configuration (bsc#1232504)\n- net_sched: tbf: fix a race in tbf_change() (git-fixes).\n- netdev-genl: Hold rcu_read_lock in napi_get (git-fixes).\n- netlink: fix potential sleeping issue in mqueue_flush_file (git-fixes).\n- netlink: specs: dpll: replace underscores with dashes in names (git-fixes).\n- netpoll: Use rcu_access_pointer() in __netpoll_setup (git-fixes).\n- netpoll: hold rcu read lock in __netpoll_send_skb() (git-fixes).\n- nfsd: Initialize ssc before laundromat_work to prevent NULL dereference (git-fixes).\n- nfsd: nfsd4_spo_must_allow() must check this is a v4 compound request (git-fixes).\n- nfsd: validate the nfsd_serv pointer before calling svc_wake_up (git-fixes).\n- ntp: Clamp maxerror and esterror to operating range (git-fixes)\n- ntp: Remove invalid cast in time offset math (git-fixes)\n- ntp: Safeguard against time_constant overflow (git-fixes)\n- nvme-fc: do not reference lsrsp after failure (bsc#1245193).\n- nvme-pci: add NVME_QUIRK_NO_DEEPEST_PS quirk for SOLIDIGM P44 Pro (git-fixes).\n- nvme-pci: add quirks for WDC Blue SN550 15b7:5009 (git-fixes).\n- nvme-pci: add quirks for device 126f:1001 (git-fixes).\n- nvme: always punt polled uring_cmd end_io work to task_work (git-fixes).\n- nvme: fix command limits status code (git-fixes).\n- nvme: fix implicit bool to flags conversion (git-fixes).\n- nvmet-fc: free pending reqs on tgtport unregister (bsc#1245193).\n- nvmet-fc: take tgtport refs for portentry (bsc#1245193).\n- nvmet-fcloop: access fcpreq only when holding reqlock (bsc#1245193).\n- nvmet-fcloop: add missing fcloop_callback_host_done (bsc#1245193).\n- nvmet-fcloop: allocate/free fcloop_lsreq directly (bsc#1245193).\n- nvmet-fcloop: do not wait for lport cleanup (bsc#1245193).\n- nvmet-fcloop: drop response if targetport is gone (bsc#1245193).\n- nvmet-fcloop: prevent double port deletion (bsc#1245193).\n- nvmet-fcloop: refactor fcloop_delete_local_port (bsc#1245193).\n- nvmet-fcloop: refactor fcloop_nport_alloc and track lport (bsc#1245193).\n- nvmet-fcloop: remove nport from list on last user (bsc#1245193).\n- nvmet-fcloop: track ref counts for nports (bsc#1245193).\n- nvmet-fcloop: update refs on tfcp_req (bsc#1245193).\n- orangefs: Do not truncate file size (git-fixes).\n- pNFS/flexfiles: Report ENETDOWN as a connection error (git-fixes).\n- page_pool: Fix use-after-free in page_pool_recycle_in_ring (git-fixes).\n- phy: core: do not require set_mode() callback for phy_get_mode() to work (stable-fixes).\n- phy: qcom-qmp-usb: Fix an NULL vs IS_ERR() bug (git-fixes).\n- phy: renesas: rcar-gen3-usb2: Add support to initialize the bus (stable-fixes).\n- phy: renesas: rcar-gen3-usb2: Assert PLL reset on PHY power off (git-fixes).\n- phy: renesas: rcar-gen3-usb2: Lock around hardware registers and driver data (git-fixes).\n- phy: renesas: rcar-gen3-usb2: Move IRQ request in probe (stable-fixes).\n- pinctrl-tegra: Restore SFSEL bit when freeing pins (stable-fixes).\n- pinctrl: armada-37xx: propagate error from armada_37xx_gpio_get() (stable-fixes).\n- pinctrl: armada-37xx: propagate error from armada_37xx_gpio_get_direction() (stable-fixes).\n- pinctrl: armada-37xx: propagate error from armada_37xx_pmx_gpio_set_direction() (stable-fixes).\n- pinctrl: armada-37xx: propagate error from armada_37xx_pmx_set_by_name() (stable-fixes).\n- pinctrl: armada-37xx: set GPIO output value before setting direction (git-fixes).\n- pinctrl: armada-37xx: use correct OUTPUT_VAL register for GPIOs \u003e 31 (git-fixes).\n- pinctrl: at91: Fix possible out-of-boundary access (git-fixes).\n- pinctrl: bcm281xx: Use 'unsigned int' instead of bare 'unsigned' (stable-fixes).\n- pinctrl: devicetree: do not goto err when probing hogs in pinctrl_dt_to_map (stable-fixes).\n- pinctrl: mcp23s08: Reset all pins to input at probe (stable-fixes).\n- pinctrl: meson: define the pull up/down resistor value as 60 kOhm (stable-fixes).\n- pinctrl: qcom: pinctrl-qcm2290: Add missing pins (git-fixes).\n- pinctrl: st: Drop unused st_gpio_bank() function (git-fixes).\n- pinctrl: tegra: Fix off by one in tegra_pinctrl_get_group() (git-fixes).\n- platform/x86/amd/hsmp: Add new error code and error logs (jsc#PED-13094).\n- platform/x86/amd/hsmp: Add support for HSMP protocol version 7 messages (jsc#PED-13094).\n- platform/x86/amd/hsmp: Change generic plat_dev name to hsmp_pdev (jsc#PED-13094).\n- platform/x86/amd/hsmp: Change the error type (jsc#PED-13094).\n- platform/x86/amd/hsmp: Convert amd_hsmp_rdwr() to a function pointer (jsc#PED-13094).\n- platform/x86/amd/hsmp: Create hsmp/ directory (jsc#PED-13094).\n- platform/x86/amd/hsmp: Create separate ACPI, plat and common drivers (jsc#PED-13094).\n- platform/x86/amd/hsmp: Create wrapper function init_acpi() (jsc#PED-13094).\n- platform/x86/amd/hsmp: Make amd_hsmp and hsmp_acpi as mutually exclusive drivers (jsc#PED-13094).\n- platform/x86/amd/hsmp: Make hsmp_pdev static instead of global (jsc#PED-13094).\n- platform/x86/amd/hsmp: Move ACPI code to acpi.c (jsc#PED-13094).\n- platform/x86/amd/hsmp: Move platform device specific code to plat.c (jsc#PED-13094).\n- platform/x86/amd/hsmp: Move structure and macros to header file (jsc#PED-13094).\n- platform/x86/amd/hsmp: Report power via hwmon sensor (jsc#PED-13094).\n- platform/x86/amd/hsmp: Use a single DRIVER_VERSION for all hsmp modules (jsc#PED-13094).\n- platform/x86/amd/hsmp: Use dev_groups in the driver structure (jsc#PED-13094).\n- platform/x86/amd/hsmp: Use name space while exporting module symbols (jsc#PED-13094).\n- platform/x86/amd/hsmp: acpi: Add sysfs files to display HSMP telemetry (jsc#PED-13094).\n- platform/x86/amd/hsmp: fix building with CONFIG_HWMON=m (jsc#PED-13094).\n- platform/x86/amd/hsmp: mark hsmp_msg_desc_table as maybe_unused (git-fixes).\n- platform/x86/amd: pmc: Clear metrics table at start of cycle (git-fixes).\n- platform/x86/intel-uncore-freq: Fail module load when plat_info is NULL (git-fixes).\n- platform/x86: amd: Use *-y instead of *-objs in Makefiles (jsc#PED-13094).\n- platform/x86: dell_rbu: Fix list usage (git-fixes).\n- platform/x86: dell_rbu: Stop overwriting data buffer (git-fixes).\n- platform/x86: fujitsu-laptop: Support Lifebook S2110 hotkeys (git-fixes).\n- platform/x86: fujitsu-laptop: Support Lifebook S2110 hotkeys (stable-fixes).\n- platform/x86: hp-bioscfg: Annotate struct bios_args with __counted_by (jsc#PED-13019).\n- platform/x86: hp-bioscfg: Change how enum possible values size is evaluated (jsc#PED-13019).\n- platform/x86: hp-bioscfg: Change how order list size is evaluated (jsc#PED-13019).\n- platform/x86: hp-bioscfg: Change how password encoding size is evaluated (jsc#PED-13019).\n- platform/x86: hp-bioscfg: Change how prerequisites size is evaluated (jsc#PED-13019).\n- platform/x86: hp-bioscfg: Fix error handling in hp_add_other_attributes() (jsc#PED-13019).\n- platform/x86: hp-bioscfg: Fix memory leaks in attribute packages (jsc#PED-13019).\n- platform/x86: hp-bioscfg: Fix reference leak (jsc#PED-13019).\n- platform/x86: hp-bioscfg: Fix uninitialized variable errors (jsc#PED-13019).\n- platform/x86: hp-bioscfg: Makefile (jsc#PED-13019).\n- platform/x86: hp-bioscfg: Remove duplicate use of variable in inner loop (jsc#PED-13019).\n- platform/x86: hp-bioscfg: Remove unused obj in hp_add_other_attributes() (jsc#PED-13019).\n- platform/x86: hp-bioscfg: Removed needless asm-generic (jsc#PED-13019).\n- platform/x86: hp-bioscfg: Replace the word HACK from source code (jsc#PED-13019).\n- platform/x86: hp-bioscfg: Simplify return check in hp_add_other_attributes() (jsc#PED-13019).\n- platform/x86: hp-bioscfg: Update steps order list elements are evaluated (jsc#PED-13019).\n- platform/x86: hp-bioscfg: Use kmemdup() to replace kmalloc + memcpy (jsc#PED-13019).\n- platform/x86: hp-bioscfg: biosattr-interface (jsc#PED-13019).\n- platform/x86: hp-bioscfg: bioscfg (jsc#PED-13019).\n- platform/x86: hp-bioscfg: bioscfg-h (jsc#PED-13019).\n- platform/x86: hp-bioscfg: enum-attributes (jsc#PED-13019).\n- platform/x86: hp-bioscfg: fix a signedness bug in hp_wmi_perform_query() (jsc#PED-13019).\n- platform/x86: hp-bioscfg: fix error reporting in hp_add_other_attributes() (jsc#PED-13019).\n- platform/x86: hp-bioscfg: int-attributes (jsc#PED-13019).\n- platform/x86: hp-bioscfg: move mutex_lock() down in hp_add_other_attributes() (jsc#PED-13019).\n- platform/x86: hp-bioscfg: order-list-attributes (jsc#PED-13019).\n- platform/x86: hp-bioscfg: passwdobj-attributes (jsc#PED-13019).\n- platform/x86: hp-bioscfg: prevent a small buffer overflow (jsc#PED-13019).\n- platform/x86: hp-bioscfg: spmobj-attributes (jsc#PED-13019).\n- platform/x86: hp-bioscfg: string-attributes (jsc#PED-13019).\n- platform/x86: hp-bioscfg: surestart-attributes (jsc#PED-13019).\n- platform/x86: ideapad-laptop: use usleep_range() for EC polling (git-fixes).\n- platform/x86: thinkpad_acpi: Ignore battery threshold change event notification (stable-fixes).\n- platform/x86: thinkpad_acpi: Support also NEC Lavie X1475JAS (git-fixes).\n- platform/x86: thinkpad_acpi: Support also NEC Lavie X1475JAS (stable-fixes).\n- power: reset: at91-reset: Optimize at91_reset() (git-fixes).\n- power: supply: bq27xxx: Retrieve again when busy (stable-fixes).\n- power: supply: collie: Fix wakeup source leaks on device unbind (stable-fixes).\n- powerpc/eeh: Fix missing PE bridge reconfiguration during VFIO EEH recovery (bsc#1215199).\n- powerpc/powernv/memtrace: Fix out of bounds issue in memtrace mmap (bsc#1244309 ltc#213790).\n- powerpc/pseries/msi: Avoid reading PCI device registers in reduced power states (bsc#1215199).\n- powerpc/vas: Return -EINVAL if the offset is non-zero in mmap() (bsc#1244309 ltc#213790).\n- pstore: Change kmsg_bytes storage size to u32 (git-fixes).\n- ptp: ocp: fix start time alignment in ptp_ocp_signal_set (git-fixes).\n- ptp: ocp: reject unsupported periodic output flags (git-fixes).\n- ptp: remove ptp-\u003en_vclocks check logic in ptp_vclock_in_use() (git-fixes).\n- r8152: add vendor/device ID pair for Dell Alienware AW1022z (git-fixes).\n- regulator: ad5398: Add device tree support (stable-fixes).\n- regulator: max14577: Add error check for max14577_read_reg() (git-fixes).\n- regulator: max20086: Change enable gpio to optional (git-fixes).\n- regulator: max20086: Fix MAX200086 chip id (git-fixes).\n- regulator: max20086: Fix refcount leak in max20086_parse_regulators_dt() (git-fixes).\n- rpm/check-for-config-changes: add more to IGNORED_CONFIGS_RE Useful when someone tries (needs) to build the kernel with clang.\n- rpm/kernel-source.changes.old: Drop bogus bugzilla reference (bsc#1244725)\n- rpm: Stop using is_kotd_qa macro This macro is set by bs-upload-kernel, and a conditional in each spec file is used to determine when to build the spec file. This logic should not really be in the spec file. Previously this was done with package links and package meta for the individula links. However, the use of package links is rejected for packages in git based release projects (nothing to do with git actually, new policy). An alternative to package links is multibuild. However, for multibuild packages package meta cannot be used to set which spec file gets built. Use prjcon buildflags instead, and remove this conditional. Depends on bs-upload-kernel adding the build flag.\n- rtc: Fix offset calculation for .start_secs \u0026lt; 0 (git-fixes).\n- rtc: Make rtc_time64_to_tm() support dates before 1970 (stable-fixes).\n- rtc: at91rm9200: drop unused module alias (git-fixes).\n- rtc: cmos: use spin_lock_irqsave in cmos_interrupt (git-fixes).\n- rtc: cpcap: drop unused module alias (git-fixes).\n- rtc: da9063: drop unused module alias (git-fixes).\n- rtc: ds1307: stop disabling alarms on probe (stable-fixes).\n- rtc: jz4740: drop unused module alias (git-fixes).\n- rtc: pm8xxx: drop unused module alias (git-fixes).\n- rtc: rv3032: fix EERD location (stable-fixes).\n- rtc: s3c: drop unused module alias (git-fixes).\n- rtc: sh: assign correct interrupts with DT (git-fixes).\n- rtc: stm32: drop unused module alias (git-fixes).\n- s390/pci: Allow re-add of a reserved but not yet removed device (bsc#1244145).\n- s390/pci: Fix __pcilg_mio_inuser() inline assembly (git-fixes bsc#1245226).\n- s390/pci: Fix duplicate pci_dev_put() in disable_slot() when PF has child VFs (git-fixes bsc#1244145).\n- s390/pci: Fix potential double remove of hotplug slot (bsc#1244145).\n- s390/pci: Prevent self deletion in disable_slot() (bsc#1244145).\n- s390/pci: Remove redundant bus removal and disable from zpci_release_device() (bsc#1244145).\n- s390/pci: Serialize device addition and removal (bsc#1244145).\n- s390/pci: introduce lock to synchronize state of zpci_dev's (jsc#PED-10253 bsc#1244145).\n- s390/pci: remove hotplug slot when releasing the device (bsc#1244145).\n- s390/pci: rename lock member in struct zpci_dev (jsc#PED-10253 bsc#1244145).\n- s390/tty: Fix a potential memory leak bug (git-fixes bsc#1245228).\n- scsi: Improve CDL control (git-fixes).\n- scsi: dc395x: Remove DEBUG conditional compilation (git-fixes).\n- scsi: dc395x: Remove leftover if statement in reselect() (git-fixes).\n- scsi: elx: efct: Fix memory leak in efct_hw_parse_filter() (git-fixes).\n- scsi: hisi_sas: Call I_T_nexus after soft reset for SATA disk (git-fixes).\n- scsi: hisi_sas: Fix I/O errors caused by hardware port ID changes (git-fixes).\n- scsi: iscsi: Fix incorrect error path labels for flashnode operations (git-fixes).\n- scsi: megaraid_sas: Block zero-length ATA VPD inquiry (git-fixes).\n- scsi: mpi3mr: Add level check to control event logging (git-fixes).\n- scsi: mpt3sas: Fix _ctl_get_mpt_mctp_passthru_adapter() to return IOC pointer (git-fixes).\n- scsi: mpt3sas: Send a diag reset if target reset fails (git-fixes).\n- scsi: pm80xx: Set phy_attached to zero when device is gone (git-fixes).\n- scsi: qedf: Use designated initializer for struct qed_fcoe_cb_ops (git-fixes).\n- scsi: sd_zbc: block: Respect bio vector limits for REPORT ZONES buffer (git-fixes).\n- scsi: smartpqi: Fix smp_processor_id() call trace for preemptible kernels (git-fixes).\n- scsi: st: ERASE does not change tape location (git-fixes).\n- scsi: st: Restore some drive settings after reset (git-fixes).\n- scsi: st: Tighten the page format heuristics with MODE SELECT (git-fixes).\n- scsi: storvsc: Do not report the host packet status as the hv status (git-fixes).\n- scsi: storvsc: Increase the timeouts to storvsc_timeout (git-fixes).\n- selftests/bpf: Fix bpf_nf selftest failure (git-fixes).\n- selftests/mm: restore default nr_hugepages value during cleanup in hugetlb_reparenting_test.sh (git-fixes).\n- selftests/net: have `gro.sh -t` return a correct exit code (stable-fixes).\n- selftests/seccomp: fix syscall_restart test for arm compat (git-fixes).\n- serial: Fix potential null-ptr-deref in mlb_usio_probe() (git-fixes).\n- serial: core: restore of_node information in sysfs (git-fixes).\n- serial: imx: Restore original RXTL for console to fix data loss (git-fixes).\n- serial: jsm: fix NPE during jsm_uart_port_init (git-fixes).\n- serial: mctrl_gpio: split disable_ms into sync and no_sync APIs (git-fixes).\n- serial: sh-sci: Move runtime PM enable to sci_probe_single() (stable-fixes).\n- serial: sh-sci: Save and restore more registers (git-fixes).\n- serial: sh-sci: Update the suspend/resume support (stable-fixes).\n- smb3: fix Open files on server counter going negative (git-fixes).\n- smb: client: Use str_yes_no() helper function (git-fixes).\n- smb: client: allow more DFS referrals to be cached (git-fixes).\n- smb: client: avoid unnecessary reconnects when refreshing referrals (git-fixes).\n- smb: client: change return value in open_cached_dir_by_dentry() if !cfids (git-fixes).\n- smb: client: do not retry DFS targets on server shutdown (git-fixes).\n- smb: client: do not trust DFSREF_STORAGE_SERVER bit (git-fixes).\n- smb: client: do not try following DFS links in cifs_tree_connect() (git-fixes).\n- smb: client: fix DFS interlink failover (git-fixes).\n- smb: client: fix DFS mount against old servers with NTLMSSP (git-fixes).\n- smb: client: fix hang in wait_for_response() for negproto (bsc#1242709).\n- smb: client: fix potential race in cifs_put_tcon() (git-fixes).\n- smb: client: fix return value of parse_dfs_referrals() (git-fixes).\n- smb: client: get rid of @nlsc param in cifs_tree_connect() (git-fixes).\n- smb: client: get rid of TCP_Server_Info::refpath_lock (git-fixes).\n- smb: client: get rid of kstrdup() in get_ses_refpath() (git-fixes).\n- smb: client: improve purging of cached referrals (git-fixes).\n- smb: client: introduce av_for_each_entry() helper (git-fixes).\n- smb: client: optimize referral walk on failed link targets (git-fixes).\n- smb: client: parse DNS domain name from domain= option (git-fixes).\n- smb: client: parse av pair type 4 in CHALLENGE_MESSAGE (git-fixes).\n- smb: client: provide dns_resolve_{unc,name} helpers (git-fixes).\n- smb: client: refresh referral without acquiring refpath_lock (git-fixes).\n- smb: client: remove unnecessary checks in open_cached_dir() (git-fixes).\n- soc: aspeed: Add NULL check in aspeed_lpc_enable_snoop() (git-fixes).\n- soc: aspeed: lpc: Fix impossible judgment condition (git-fixes).\n- soc: qcom: smp2p: Fix fallback to qcom,ipc parse (git-fixes).\n- soc: ti: k3-socinfo: Do not use syscon helper to build regmap (stable-fixes).\n- software node: Correct a OOB check in software_node_get_reference_args() (stable-fixes).\n- soundwire: amd: change the soundwire wake enable/disable sequence (stable-fixes).\n- spi-rockchip: Fix register out of bounds access (stable-fixes).\n- spi: bcm63xx-hsspi: fix shared reset (git-fixes).\n- spi: bcm63xx-spi: fix shared reset (git-fixes).\n- spi: sh-msiof: Fix maximum DMA transfer size (git-fixes).\n- spi: spi-sun4i: fix early activation (stable-fixes).\n- spi: tegra210-quad: Fix X1_X2_X4 encoding and support x4 transfers (git-fixes).\n- spi: tegra210-quad: modify chip select (CS) deactivation (git-fixes).\n- spi: tegra210-quad: remove redundant error handling code (git-fixes).\n- spi: zynqmp-gqspi: Always acknowledge interrupts (stable-fixes).\n- staging: iio: ad5933: Correct settling cycles encoding per datasheet (git-fixes).\n- staging: rtl8723bs: Avoid memset() in aes_cipher() and aes_decipher() (git-fixes).\n- struct usci: hide additional member (git-fixes).\n- sunrpc: handle SVC_GARBAGE during svc auth processing as auth error (git-fixes).\n- supported.conf: Add SNP SVSM vTPM driver\n- supported.conf: add it\n- supported.conf: support firmware_attributes_class\n- svsm: Add header with SVSM_VTPM_CMD helpers (bsc#1241191).\n- sysfb: Fix screen_info type check for VGA (git-fixes).\n- tcp/dccp: allow a connection when sk_max_ack_backlog is zero (git-fixes).\n- tcp/dccp: bypass empty buckets in inet_twsk_purge() (git-fixes).\n- tcp/dccp: complete lockless accesses to sk-\u003esk_max_ack_backlog (git-fixes).\n- tcp: bring back NUMA dispersion in inet_ehash_locks_alloc() (git-fixes).\n- tcp_metrics: optimize tcp_metrics_flush_all() (git-fixes).\n- thermal/drivers/mediatek/lvts: Fix debugfs unregister on failure (git-fixes).\n- thermal/drivers/qoriq: Power down TMU on system suspend (stable-fixes).\n- thunderbolt: Do not add non-active NVM if NVM upgrade is disabled for retimer (stable-fixes).\n- thunderbolt: Do not double dequeue a configuration request (stable-fixes).\n- thunderbolt: Fix a logic error in wake on connect (git-fixes).\n- thunderbolt: Improve redrive mode handling (git-fixes).\n- timekeeping: Fix bogus clock_was_set() invocation in (git-fixes)\n- timekeeping: Fix cross-timestamp interpolation corner case (git-fixes)\n- timekeeping: Fix cross-timestamp interpolation for non-x86 (git-fixes)\n- timekeeping: Fix cross-timestamp interpolation on counter (git-fixes)\n- tpm: Add SNP SVSM vTPM driver (bsc#1241191).\n- tpm: Make chip-\u003e{status,cancel,req_canceled} opt (bsc#1241191).\n- trace/trace_event_perf: remove duplicate samples on the first tracepoint event (git-fixes).\n- tracing/eprobe: Fix to release eprobe when failed to add dyn_event (git-fixes).\n- tracing: Add __print_dynamic_array() helper (bsc#1243544).\n- tracing: Add __string_len() example (bsc#1243544).\n- tracing: Fix cmp_entries_dup() to respect sort() comparison rules (git-fixes).\n- tracing: Fix compilation warning on arm32 (bsc#1243551).\n- tracing: Use atomic64_inc_return() in trace_clock_counter() (git-fixes).\n- truct dwc3 hide new member wakeup_pending_funcs (git-fixes).\n- tty: serial: 8250_omap: fix TX with DMA for am33xx (git-fixes).\n- ucsi_debugfs_entry: hide signedness change (git-fixes).\n- udp: annotate data-races around up-\u003epending (git-fixes).\n- udp: fix incorrect parameter validation in the udp_lib_getsockopt() function (git-fixes).\n- udp: fix receiving fraglist GSO packets (git-fixes).\n- udp: preserve the connected status if only UDP cmsg (git-fixes).\n- uprobes: Use kzalloc to allocate xol area (git-fixes).\n- usb: Flush altsetting 0 endpoints before reinitializating them after reset (git-fixes).\n- usb: cdnsp: Fix issue with detecting USB 3.2 speed (git-fixes).\n- usb: cdnsp: Fix issue with detecting command completion event (git-fixes).\n- usb: dwc3: gadget: Make gadget_wakeup asynchronous (git-fixes).\n- usb: misc: onboard_usb_dev: fix support for Cypress HX3 hubs (git-fixes).\n- usb: quirks: Add NO_LPM quirk for SanDisk Extreme 55AE (stable-fixes).\n- usb: renesas_usbhs: Reorder clock handling and power management in probe (git-fixes).\n- usb: storage: Ignore UAS driver for SanDisk 3.2 Gen2 storage device (stable-fixes).\n- usb: typec: tcpm/tcpci_maxim: Fix bounds check in process_rx() (git-fixes).\n- usb: typec: tcpm: move tcpm_queue_vdm_unlocked to asynchronous work (git-fixes).\n- usb: typec: ucsi: Only enable supported notifications (git-fixes).\n- usb: typec: ucsi: allow non-partner GET_PDOS for Qualcomm devices (git-fixes).\n- usb: typec: ucsi: fix Clang -Wsign-conversion warning (git-fixes).\n- usb: typec: ucsi: fix UCSI on buggy Qualcomm devices (git-fixes).\n- usb: typec: ucsi: limit the UCSI_NO_PARTNER_PDOS even further (git-fixes).\n- usb: usbtmc: Fix read_stb function and get_stb ioctl (git-fixes).\n- usb: usbtmc: Fix timeout value in get_stb (git-fixes).\n- usb: xhci: Do not change the status of stalled TDs on failed Stop EP (stable-fixes).\n- usbnet: asix AX88772: leave the carrier control to phylink (stable-fixes).\n- vgacon: Add check for vc_origin address range in vgacon_scroll() (git-fixes).\n- vmxnet3: correctly report gso type for UDP tunnels (bsc#1244626).\n- vmxnet3: support higher link speeds from vmxnet3 v9 (bsc#1244626).\n- vmxnet3: update MTU after device quiesce (bsc#1244626).\n- vt: remove VT_RESIZE and VT_RESIZEX from vt_compat_ioctl() (git-fixes).\n- watchdog: da9052_wdt: respect TWDMIN (stable-fixes).\n- watchdog: exar: Shorten identity name to fit correctly (git-fixes).\n- watchdog: fix watchdog may detect false positive of softlockup (stable-fixes).\n- watchdog: it87_wdt: add PWRGD enable quirk for Qotom QCML04 (git-fixes).\n- watchdog: mediatek: Add support for MT6735 TOPRGU/WDT (git-fixes).\n- wifi: ath11k: Fix QMI memory reuse logic (stable-fixes).\n- wifi: ath11k: avoid burning CPU in ath11k_debugfs_fw_stats_request() (git-fixes).\n- wifi: ath11k: convert timeouts to secs_to_jiffies() (stable-fixes).\n- wifi: ath11k: do not use static variables in ath11k_debugfs_fw_stats_process() (git-fixes).\n- wifi: ath11k: do not wait when there is no vdev started (git-fixes).\n- wifi: ath11k: fix node corruption in ar-\u003earvifs list (git-fixes).\n- wifi: ath11k: fix ring-buffer corruption (git-fixes).\n- wifi: ath11k: fix rx completion meta data corruption (git-fixes).\n- wifi: ath11k: fix soc_dp_stats debugfs file permission (stable-fixes).\n- wifi: ath11k: move some firmware stats related functions outside of debugfs (git-fixes).\n- wifi: ath11k: update channel list in worker when wait flag is set (bsc#1243847).\n- wifi: ath11k: validate ath11k_crypto_mode on top of ath11k_core_qmi_firmware_ready (git-fixes).\n- wifi: ath12k: ACPI CCA threshold support (bsc#1240998).\n- wifi: ath12k: ACPI SAR support (bsc#1240998).\n- wifi: ath12k: ACPI TAS support (bsc#1240998).\n- wifi: ath12k: ACPI band edge channel power support (bsc#1240998).\n- wifi: ath12k: Add MSDU length validation for TKIP MIC error (git-fixes).\n- wifi: ath12k: Add additional checks for vif and sta iterators (bsc#1240998).\n- wifi: ath12k: Add firmware coredump collection support (bsc#1240998).\n- wifi: ath12k: Add htt_stats_dump file ops support (bsc#1240998).\n- wifi: ath12k: Add lock to protect the hardware state (bsc#1240998).\n- wifi: ath12k: Add missing htt_metadata flag in ath12k_dp_tx() (bsc#1240998).\n- wifi: ath12k: Add support to enable debugfs_htt_stats (bsc#1240998).\n- wifi: ath12k: Add support to parse requested stats_type (bsc#1240998).\n- wifi: ath12k: Avoid -Wflex-array-member-not-at-end warnings (bsc#1240998).\n- wifi: ath12k: Avoid napi_sync() before napi_enable() (stable-fixes).\n- wifi: ath12k: Cache vdev configs before vdev create (bsc#1240998).\n- wifi: ath12k: Dump additional Tx PDEV HTT stats (bsc#1240998).\n- wifi: ath12k: Fetch regdb.bin file from board-2.bin (stable-fixes).\n- wifi: ath12k: Fix WARN_ON during firmware crash in split-phy (bsc#1240998).\n- wifi: ath12k: Fix WMI tag for EHT rate in peer assoc (git-fixes).\n- wifi: ath12k: Fix buffer overflow in debugfs (bsc#1240998).\n- wifi: ath12k: Fix devmem address prefix when logging (bsc#1240998).\n- wifi: ath12k: Fix end offset bit definition in monitor ring descriptor (stable-fixes).\n- wifi: ath12k: Fix for out-of bound access error (bsc#1240998).\n- wifi: ath12k: Fix invalid memory access while forming 802.11 header (git-fixes).\n- wifi: ath12k: Fix memory leak during vdev_id mismatch (git-fixes).\n- wifi: ath12k: Fix pdev id sent to firmware for single phy devices (bsc#1240998).\n- wifi: ath12k: Fix the QoS control field offset to build QoS header (git-fixes).\n- wifi: ath12k: Handle error cases during extended skb allocation (git-fixes).\n- wifi: ath12k: Improve BSS discovery with hidden SSID in 6 GHz band (stable-fixes).\n- wifi: ath12k: Introduce device index (bsc#1240998).\n- wifi: ath12k: Modify add and remove chanctx ops for single wiphy support (bsc#1240998).\n- wifi: ath12k: Modify print_array_to_buf() to support arrays with 1-based semantics (bsc#1240998).\n- wifi: ath12k: Modify rts threshold mac op for single wiphy (bsc#1240998).\n- wifi: ath12k: Modify set and get antenna mac ops for single wiphy (bsc#1240998).\n- wifi: ath12k: Optimize the lock contention of used list in Rx data path (bsc#1240998).\n- wifi: ath12k: Pass correct values of center freq1 and center freq2 for 160 MHz (stable-fixes).\n- wifi: ath12k: Prevent sending WMI commands to firmware during firmware crash (bsc#1240998).\n- wifi: ath12k: Refactor Rxdma buffer replinish argument (bsc#1240998).\n- wifi: ath12k: Refactor data path cmem init (bsc#1240998).\n- wifi: ath12k: Refactor error handler of Rxdma replenish (bsc#1240998).\n- wifi: ath12k: Refactor idle ring descriptor setup (bsc#1240998).\n- wifi: ath12k: Refactor the hardware cookie conversion init (bsc#1240998).\n- wifi: ath12k: Refactor the hardware recovery procedure (bsc#1240998).\n- wifi: ath12k: Refactor the hardware state (bsc#1240998).\n- wifi: ath12k: Remove unsupported tx monitor handling (bsc#1240998).\n- wifi: ath12k: Remove unused ath12k_base from ath12k_hw (bsc#1240998).\n- wifi: ath12k: Remove unused tcl_*_ring configuration (bsc#1240998).\n- wifi: ath12k: Replace 'chip' with 'device' in hal Rx return buffer manager (bsc#1240998).\n- wifi: ath12k: Report proper tx completion status to mac80211 (stable-fixes).\n- wifi: ath12k: Resolve multicast packet drop by populating key_cipher in ath12k_install_key() (bsc#1240998).\n- wifi: ath12k: Support BE OFDMA Pdev Rate Stats (bsc#1240998).\n- wifi: ath12k: Support DMAC Reset Stats (bsc#1240998).\n- wifi: ath12k: Support Pdev OBSS Stats (bsc#1240998).\n- wifi: ath12k: Support Pdev Scheduled Algorithm Stats (bsc#1240998).\n- wifi: ath12k: Support Ring and SFM stats (bsc#1240998).\n- wifi: ath12k: Support Self-Generated Transmit stats (bsc#1240998).\n- wifi: ath12k: Support TQM stats (bsc#1240998).\n- wifi: ath12k: Support Transmit DE stats (bsc#1240998).\n- wifi: ath12k: Support Transmit Scheduler stats (bsc#1240998).\n- wifi: ath12k: Support pdev CCA Stats (bsc#1240998).\n- wifi: ath12k: Support pdev Transmit Multi-user stats (bsc#1240998).\n- wifi: ath12k: Support pdev error stats (bsc#1240998).\n- wifi: ath12k: add 6 GHz params in peer assoc command (bsc#1240998).\n- wifi: ath12k: add ATH12K_DBG_WOW log level (bsc#1240998).\n- wifi: ath12k: add EMA beacon support (bsc#1240998).\n- wifi: ath12k: add MBSSID beacon support (bsc#1240998).\n- wifi: ath12k: add WoW net-detect functionality (bsc#1240998).\n- wifi: ath12k: add basic WoW functionalities (bsc#1240998).\n- wifi: ath12k: add channel 2 into 6 GHz channel list (bsc#1240998).\n- wifi: ath12k: add hw_link_id in ath12k_pdev (bsc#1240998).\n- wifi: ath12k: add missing lockdep_assert_wiphy() for ath12k_mac_op_ functions (bsc#1240998).\n- wifi: ath12k: add multi device support for WBM idle ring buffer setup (bsc#1240998).\n- wifi: ath12k: add multiple radio support in a single MAC HW un/register (bsc#1240998).\n- wifi: ath12k: add panic handler (bsc#1240998).\n- wifi: ath12k: add support to handle beacon miss for WCN7850 (bsc#1240998).\n- wifi: ath12k: advertise driver capabilities for MBSSID and EMA (bsc#1240998).\n- wifi: ath12k: allocate dummy net_device dynamically (bsc#1240998).\n- wifi: ath12k: ath12k_mac_op_set_key(): fix uninitialized symbol 'ret' (bsc#1240998).\n- wifi: ath12k: ath12k_mac_op_sta_state(): clean up update_wk cancellation (bsc#1240998).\n- wifi: ath12k: ath12k_mac_set_key(): remove exit label (bsc#1240998).\n- wifi: ath12k: avoid double SW2HW_MACID conversion (bsc#1240998).\n- wifi: ath12k: avoid duplicated vdev down (bsc#1240998).\n- wifi: ath12k: avoid redundant code in Rx cookie conversion init (bsc#1240998).\n- wifi: ath12k: avoid stopping mac80211 queues in ath12k_core_restart() (bsc#1240998).\n- wifi: ath12k: avoid unnecessary MSDU drop in the Rx error process (bsc#1240998).\n- wifi: ath12k: change supports_suspend to true for WCN7850 (bsc#1240998).\n- wifi: ath12k: cleanup unneeded labels (bsc#1240998).\n- wifi: ath12k: configure MBSSID parameters in AP mode (bsc#1240998).\n- wifi: ath12k: configure MBSSID params in vdev create/start (bsc#1240998).\n- wifi: ath12k: convert struct ath12k_sta::update_wk to use struct wiphy_work (bsc#1240998).\n- wifi: ath12k: correct the capital word typo (bsc#1240998).\n- wifi: ath12k: create a structure for WMI vdev up parameters (bsc#1240998).\n- wifi: ath12k: debugfs: radar simulation support (bsc#1240998).\n- wifi: ath12k: decrease MHI channel buffer length to 8KB (bsc#1240998).\n- wifi: ath12k: delete NSS and TX power setting for monitor vdev (bsc#1240998).\n- wifi: ath12k: displace the Tx and Rx descriptor in cookie conversion table (bsc#1240998).\n- wifi: ath12k: do not dump SRNG statistics during resume (bsc#1240998).\n- wifi: ath12k: do not process consecutive RDDM event (bsc#1240998).\n- wifi: ath12k: do not use %pK in dmesg format strings (bsc#1240998).\n- wifi: ath12k: dynamic VLAN support (bsc#1240998).\n- wifi: ath12k: dynamically update peer puncturing bitmap for STA (bsc#1240998).\n- wifi: ath12k: enable WIPHY_FLAG_DISABLE_WEXT (bsc#1240998).\n- wifi: ath12k: enable service flag for survey dump stats (bsc#1240998).\n- wifi: ath12k: extend the link capable flag (bsc#1240998).\n- wifi: ath12k: fetch correct radio based on vdev status (bsc#1240998).\n- wifi: ath12k: fix A-MSDU indication in monitor mode (bsc#1240998).\n- wifi: ath12k: fix ACPI warning when resume (bsc#1240998).\n- wifi: ath12k: fix GCC_GCC_PCIE_HOT_RST definition for WCN7850 (git-fixes).\n- wifi: ath12k: fix NULL pointer access in ath12k_mac_op_get_survey() (bsc#1240998).\n- wifi: ath12k: fix Smatch warnings on ath12k_core_suspend() (bsc#1240998).\n- wifi: ath12k: fix a possible dead lock caused by ab-\u003ebase_lock (stable-fixes).\n- wifi: ath12k: fix ack signal strength calculation (bsc#1240998).\n- wifi: ath12k: fix ath12k_hal_tx_cmd_ext_desc_setup() info1 override (stable-fixes).\n- wifi: ath12k: fix build vs old compiler (bsc#1240998).\n- wifi: ath12k: fix calling correct function for rx monitor mode (bsc#1240998).\n- wifi: ath12k: fix cleanup path after mhi init (git-fixes).\n- wifi: ath12k: fix desc address calculation in wbm tx completion (bsc#1240998).\n- wifi: ath12k: fix driver initialization for WoW unsupported devices (bsc#1240998).\n- wifi: ath12k: fix failed to set mhi state error during reboot with hardware grouping (stable-fixes).\n- wifi: ath12k: fix flush failure in recovery scenarios (bsc#1240998).\n- wifi: ath12k: fix hal_rx_buf_return_buf_manager documentation (bsc#1240998).\n- wifi: ath12k: fix incorrect CE addresses (stable-fixes).\n- wifi: ath12k: fix invalid access to memory (git-fixes).\n- wifi: ath12k: fix key cache handling (bsc#1240998).\n- wifi: ath12k: fix legacy peer association due to missing HT or 6 GHz capabilities (bsc#1240998).\n- wifi: ath12k: fix link capable flags (bsc#1240998).\n- wifi: ath12k: fix link valid field initialization in the monitor Rx (stable-fixes).\n- wifi: ath12k: fix mac id extraction when MSDU spillover in rx error path (bsc#1240998).\n- wifi: ath12k: fix macro definition HAL_RX_MSDU_PKT_LENGTH_GET (stable-fixes).\n- wifi: ath12k: fix mbssid max interface advertisement (bsc#1240998).\n- wifi: ath12k: fix missing endianness conversion in wmi_vdev_create_cmd() (bsc#1240998).\n- wifi: ath12k: fix misspelling of 'dma' in num_rxmda_per_pdev (bsc#1240998).\n- wifi: ath12k: fix node corruption in ar-\u003earvifs list (git-fixes).\n- wifi: ath12k: fix one more memcpy size error (bsc#1240998).\n- wifi: ath12k: fix per pdev debugfs registration (bsc#1240998).\n- wifi: ath12k: fix reusing outside iterator in ath12k_wow_vif_set_wakeups() (bsc#1240998).\n- wifi: ath12k: fix ring-buffer corruption (git-fixes).\n- wifi: ath12k: fix skb_ext_desc leak in ath12k_dp_tx() error path (bsc#1240998).\n- wifi: ath12k: fix struct hal_rx_mpdu_start (bsc#1240998).\n- wifi: ath12k: fix struct hal_rx_phyrx_rssi_legacy_info (bsc#1240998).\n- wifi: ath12k: fix struct hal_rx_ppdu_end_user_stats (bsc#1240998).\n- wifi: ath12k: fix struct hal_rx_ppdu_start (bsc#1240998).\n- wifi: ath12k: fix survey dump collection in 6 GHz (bsc#1240998).\n- wifi: ath12k: fix the ampdu id fetch in the HAL_RX_MPDU_START TLV (stable-fixes).\n- wifi: ath12k: fix the stack frame size warning in ath12k_mac_op_hw_scan (bsc#1240998).\n- wifi: ath12k: fix use-after-free in ath12k_dp_cc_cleanup() (bsc#1240998).\n- wifi: ath12k: fix warning on DMA ring capabilities event (bsc#1240998).\n- wifi: ath12k: flush all packets before suspend (bsc#1240998).\n- wifi: ath12k: handle keepalive during WoWLAN suspend and resume (bsc#1240998).\n- wifi: ath12k: handle symlink cleanup for per pdev debugfs dentry (bsc#1240998).\n- wifi: ath12k: implement WoW enable and wakeup commands (bsc#1240998).\n- wifi: ath12k: implement hardware data filter (bsc#1240998).\n- wifi: ath12k: improve the rx descriptor error information (bsc#1240998).\n- wifi: ath12k: initial debugfs support (bsc#1240998).\n- wifi: ath12k: make read-only array svc_id static const (bsc#1240998).\n- wifi: ath12k: modify ath12k mac start/stop ops for single wiphy (bsc#1240998).\n- wifi: ath12k: modify ath12k_get_arvif_iter() for MLO (bsc#1240998).\n- wifi: ath12k: modify ath12k_mac_op_bss_info_changed() for MLO (bsc#1240998).\n- wifi: ath12k: modify ath12k_mac_op_set_key() for MLO (bsc#1240998).\n- wifi: ath12k: modify ath12k_mac_vif_chan() for MLO (bsc#1240998).\n- wifi: ath12k: modify link arvif creation and removal for MLO (bsc#1240998).\n- wifi: ath12k: modify regulatory support for single wiphy architecture (bsc#1240998).\n- wifi: ath12k: modify remain on channel for single wiphy (bsc#1240998).\n- wifi: ath12k: move txbaddr/rxbaddr into struct ath12k_dp (bsc#1240998).\n- wifi: ath12k: no need to handle pktlog during suspend/resume (bsc#1240998).\n- wifi: ath12k: pass ath12k_link_vif instead of vif/ahvif (bsc#1240998).\n- wifi: ath12k: prepare sta data structure for MLO handling (bsc#1240998).\n- wifi: ath12k: prepare vif config caching for MLO (bsc#1240998).\n- wifi: ath12k: prepare vif data structure for MLO handling (bsc#1240998).\n- wifi: ath12k: read single_chip_mlo_support parameter from QMI PHY capability (bsc#1240998).\n- wifi: ath12k: rearrange IRQ enable/disable in reset path (bsc#1240998).\n- wifi: ath12k: refactor SMPS configuration (bsc#1240998).\n- wifi: ath12k: refactor arvif security parameter configuration (bsc#1240998).\n- wifi: ath12k: refactor ath12k_hw_regs structure (stable-fixes).\n- wifi: ath12k: refactor rx descriptor CMEM configuration (bsc#1240998).\n- wifi: ath12k: remove MHI LOOPBACK channels (bsc#1240998).\n- wifi: ath12k: remove duplicate definition of MAX_RADIOS (bsc#1240998).\n- wifi: ath12k: remove duplicate definitions in wmi.h (bsc#1240998).\n- wifi: ath12k: remove invalid peer create logic (bsc#1240998).\n- wifi: ath12k: remove obsolete struct wmi_start_scan_arg (bsc#1240998).\n- wifi: ath12k: remove redundant peer delete for WCN7850 (bsc#1240998).\n- wifi: ath12k: remove unused variable monitor_flags (bsc#1240998).\n- wifi: ath12k: remove unused variable monitor_present (bsc#1240998).\n- wifi: ath12k: rename MBSSID fields in wmi_vdev_up_cmd (bsc#1240998).\n- wifi: ath12k: restore ASPM for supported hardwares only (bsc#1240998).\n- wifi: ath12k: scan statemachine changes for single wiphy (bsc#1240998).\n- wifi: ath12k: set mlo_capable_flags based on QMI PHY capability (bsc#1240998).\n- wifi: ath12k: skip sending vdev down for channel switch (bsc#1240998).\n- wifi: ath12k: support ARP and NS offload (bsc#1240998).\n- wifi: ath12k: support GTK rekey offload (bsc#1240998).\n- wifi: ath12k: support SMPS configuration for 6 GHz (bsc#1240998).\n- wifi: ath12k: support get_survey mac op for single wiphy (bsc#1240998).\n- wifi: ath12k: support suspend/resume (bsc#1240998).\n- wifi: ath12k: switch to using wiphy_lock() and remove ar-\u003econf_mutex (bsc#1240998).\n- wifi: ath12k: unregister per pdev debugfs (bsc#1240998).\n- wifi: ath12k: update ath12k_mac_op_conf_tx() for MLO (bsc#1240998).\n- wifi: ath12k: update ath12k_mac_op_update_vif_offload() for MLO (bsc#1240998).\n- wifi: ath12k: use 128 bytes aligned iova in transmit path for WCN7850 (bsc#1240998).\n- wifi: ath12k: use correct MAX_RADIOS (bsc#1240998).\n- wifi: ath12k: use tail MSDU to get MSDU information (bsc#1240998).\n- wifi: ath12k: using msdu end descriptor to check for rx multicast packets (stable-fixes).\n- wifi: ath12k: vdev statemachine changes for single wiphy (bsc#1240998).\n- wifi: ath9k: return by of_get_mac_address (stable-fixes).\n- wifi: ath9k_htc: Abort software beacon handling if disabled (git-fixes).\n- wifi: carl9170: do not ping device which has failed to load firmware (git-fixes).\n- wifi: cfg80211: allow IR in 20 MHz configurations (stable-fixes).\n- wifi: iwlfiwi: mvm: Fix the rate reporting (git-fixes).\n- wifi: iwlwifi: Add missing MODULE_FIRMWARE for Qu-c0-jf-b0 (stable-fixes).\n- wifi: iwlwifi: add support for Killer on MTL (stable-fixes).\n- wifi: iwlwifi: do not warn during reprobe (stable-fixes).\n- wifi: iwlwifi: do not warn when if there is a FW error (stable-fixes).\n- wifi: iwlwifi: fix debug actions order (stable-fixes).\n- wifi: iwlwifi: fix the ECKV UEFI variable name (stable-fixes).\n- wifi: iwlwifi: mark Br device not integrated (stable-fixes).\n- wifi: iwlwifi: mvm: fix beacon CCK flag (stable-fixes).\n- wifi: iwlwifi: mvm: fix setting the TK when associated (stable-fixes).\n- wifi: iwlwifi: pcie: make sure to lock rxq-\u003eread (stable-fixes).\n- wifi: iwlwifi: use correct IMR dump variable (stable-fixes).\n- wifi: iwlwifi: w/a FW SMPS mode selection (stable-fixes).\n- wifi: mac80211: VLAN traffic in multicast path (stable-fixes).\n- wifi: mac80211: do not offer a mesh path if forwarding is disabled (stable-fixes).\n- wifi: mac80211: do not unconditionally call drv_mgd_complete_tx() (stable-fixes).\n- wifi: mac80211: fix beacon interval calculation overflow (git-fixes).\n- wifi: mac80211: fix warning on disconnect during failed ML reconf (stable-fixes).\n- wifi: mac80211: remove misplaced drv_mgd_complete_tx() call (stable-fixes).\n- wifi: mac80211: set ieee80211_prep_tx_info::link_id upon Auth Rx (stable-fixes).\n- wifi: mac80211: validate SCAN_FLAG_AP in scan request during MLO (stable-fixes).\n- wifi: mac80211_hwsim: Fix MLD address translation (stable-fixes).\n- wifi: mac80211_hwsim: Prevent tsf from setting if beacon is disabled (stable-fixes).\n- wifi: mt76: mt76x2: Add support for LiteOn WN4516R,WN4519R (stable-fixes).\n- wifi: mt76: mt7915: Fix null-ptr-deref in mt7915_mmio_wed_init() (git-fixes).\n- wifi: mt76: mt7921: add 160 MHz AP for mt7922 device (stable-fixes).\n- wifi: mt76: mt7925: ensure all MCU commands wait for response (git-fixes).\n- wifi: mt76: mt7925: fix fails to enter low power mode in suspend state (stable-fixes).\n- wifi: mt76: mt7925: fix host interrupt register initialization (git-fixes).\n- wifi: mt76: mt7925: introduce thermal protection (stable-fixes).\n- wifi: mt76: mt7925: load the appropriate CLC data based on hardware type (stable-fixes).\n- wifi: mt76: mt7925: prevent multiple scan commands (git-fixes).\n- wifi: mt76: mt7925: refine the sniffer commnad (git-fixes).\n- wifi: mt76: mt7996: drop fragments with multicast or broadcast RA (stable-fixes).\n- wifi: mt76: mt7996: fix RX buffer size of MCU event (git-fixes).\n- wifi: mt76: mt7996: revise TXS size (stable-fixes).\n- wifi: mt76: mt7996: set EHT max ampdu length capability (git-fixes).\n- wifi: mt76: only mark tx-status-failed frames as ACKed on mt76x0/2 (stable-fixes).\n- wifi: mwifiex: Fix HT40 bandwidth issue (stable-fixes).\n- wifi: p54: prevent buffer-overflow in p54_rx_eeprom_readback() (git-fixes).\n- wifi: rtlwifi: disable ASPM for RTL8723BE with subsystem ID 11ad:1723 (git-fixes).\n- wifi: rtw88: Do not use static local variable in rtw8822b_set_tx_power_index_by_rate (stable-fixes).\n- wifi: rtw88: Fix __rtw_download_firmware() for RTL8814AU (stable-fixes).\n- wifi: rtw88: Fix download_firmware_validate() for RTL8814AU (stable-fixes).\n- wifi: rtw88: Fix rtw_desc_to_mcsrate() to handle MCS16-31 (stable-fixes).\n- wifi: rtw88: Fix rtw_init_ht_cap() for RTL8814AU (stable-fixes).\n- wifi: rtw88: Fix rtw_init_vht_cap() for RTL8814AU (stable-fixes).\n- wifi: rtw88: do not ignore hardware read error during DPK (git-fixes).\n- wifi: rtw88: fix the 'para' buffer size to avoid reading out of bounds (git-fixes).\n- wifi: rtw88: sdio: call rtw_sdio_indicate_tx_status unconditionally (git-fixes).\n- wifi: rtw88: sdio: map mgmt frames to queue TX_DESC_QSEL_MGMT (git-fixes).\n- wifi: rtw88: usb: Reduce control message timeout to 500 ms (git-fixes).\n- wifi: rtw89: 8922a: fix TX fail with wrong VCO setting (stable-fixes).\n- wifi: rtw89: 8922a: fix incorrect STA-ID in EHT MU PPDU (stable-fixes).\n- wifi: rtw89: add wiphy_lock() to work that isn't held wiphy_lock() yet (stable-fixes).\n- wifi: rtw89: call power_on ahead before selecting firmware (stable-fixes).\n- wifi: rtw89: fw: get sb_sel_ver via get_unaligned_le32() (stable-fixes).\n- wifi: rtw89: fw: propagate error code from rtw89_h2c_tx() (stable-fixes).\n- wifi: rtw89: leave idle mode when setting WEP encryption for AP mode (stable-fixes).\n- wifi: rtw89: pci: enlarge retry times of RX tag to 1000 (git-fixes).\n- wifi: rtw89: phy: add dummy C2H event handler for report of TAS power (stable-fixes).\n- wireless: purelifi: plfxlc: fix memory leak in plfxlc_usb_wreq_asyn() (stable-fixes).\n- workqueue: Initialize wq_isolated_cpumask in workqueue_init_early() (bsc#1245101 jsc#PED-11934).\n- x86/acpi: Fix LAPIC/x2APIC parsing order (git-fixes).\n- x86/amd_nb, hwmon: (k10temp): Simplify amd_pci_dev_to_node_id() (jsc#PED-13094).\n- x86/amd_nb: Clean up early_is_amd_nb() (jsc#PED-13094).\n- x86/amd_nb: Move SMN access code to a new amd_node driver (jsc#PED-13094).\n- x86/amd_nb: Restrict init function to AMD-based systems (jsc#PED-13094).\n- x86/amd_nb: Simplify function 4 search (jsc#PED-13094).\n- x86/amd_nb: Simplify root device search (jsc#PED-13094).\n- x86/amd_node: Add SMN offsets to exclusive region access (jsc#PED-13094).\n- x86/amd_node: Add support for debugfs access to SMN registers (jsc#PED-13094).\n- x86/amd_node: Remove dependency on AMD_NB (jsc#PED-13094).\n- x86/amd_node: Update __amd_smn_rw() error paths (jsc#PED-13094).\n- x86/amd_node: Use defines for SMN register offsets (jsc#PED-13094).\n- x86/fred/signal: Prevent immediate repeat of single step trap on return from SIGTRAP handler (git-fixes).\n- x86/idle: Remove MFENCEs for X86_BUG_CLFLUSH_MONITOR in mwait_idle_with_hints() and prefer_mwait_c1_over_halt() (git-fixes).\n- x86/kaslr: Reduce KASLR entropy on most x86 systems (git-fixes).\n- x86/mce/amd: Remove shared threshold bank plumbing (jsc#PED-13094).\n- x86/microcode/AMD: Add get_patch_level() (git-fixes).\n- x86/microcode/AMD: Do not return error when microcode update is not necessary (git-fixes).\n- x86/microcode/AMD: Get rid of the _load_microcode_amd() forward declaration (git-fixes).\n- x86/microcode/AMD: Have __apply_microcode_amd() return bool (git-fixes).\n- x86/microcode/AMD: Make __verify_patch_size() return bool (git-fixes).\n- x86/microcode/AMD: Merge early_apply_microcode() into its single callsite (git-fixes).\n- x86/microcode/AMD: Remove ugly linebreak in __verify_patch_section() signature (git-fixes).\n- x86/microcode/AMD: Return bool from find_blobs_in_containers() (git-fixes).\n- x86/microcode: Consolidate the loader enablement checking (git-fixes).\n- x86/mm/init: Handle the special case of device private pages in add_pages(), to not increase max_pfn and trigger dma_addressing_limited() bounce buffers (git-fixes).\n- x86/platform/amd: Move the \u0026lt;asm/amd_hsmp.h\u003e header to \u0026lt;asm/amd/hsmp.h\u003e (jsc#PED-13094).\n- x86/sev: Add SVSM vTPM probe/send_command functions (bsc#1241191).\n- x86/sev: Provide guest VMPL level to userspace (bsc#1241191).\n- x86/sev: Register tpm-svsm platform device (bsc#1241191).\n- x86/xen: fix balloon target initialization for PVH dom0 (git-fixes).\n- x86: Start moving AMD node functionality out of AMD_NB (jsc#PED-13094).\n- xen/arm: call uaccess_ttbr0_enable for dm_op hypercall (git-fixes)\n- xen/x86: fix initial memory balloon target (git-fixes).\n- xhci: dbc: Avoid event polling busyloop if pending rx transfers are inactive (git-fixes).\n- xsk: always clear DMA mapping information when unmapping the pool (git-fixes).\n","status":"published","published":"2025-07-14T12:31:08Z","modified":"2026-03-23T04:46:31.637865Z","updated_at":"2026-11-02T15:53:56.647031Z"},{"id":"SUSE-SU-2025:02333-1","title":"Security update for the Linux Kernel","description":"\nThe SUSE Linux Enterprise 15 SP7 RT kernel was updated to receive various security bugfixes.\n\n\nThe following security bugs were fixed:\n\n- CVE-2023-52888: media: mediatek: vcodec: Only free buffer VA that is not NULL (bsc#1228557).\n- CVE-2024-49568: net/smc: check v2_ext_offset/eid_cnt/ism_gid_cnt when receiving proposal msg (bsc#1235728).\n- CVE-2024-57982: xfrm: state: fix out-of-bounds read during lookup (bsc#1237913).\n- CVE-2024-57995: wifi: ath12k: fix read pointer after free in ath12k_mac_assign_vif_to_vdev() (bsc#1237895).\n- CVE-2024-58053: rxrpc: Fix handling of received connection abort (bsc#1238982).\n- CVE-2025-21720: xfrm: delete intermediate secpath entry in packet offload mode (bsc#1238859).\n- CVE-2025-21868: kABI workaround for adding an header (bsc#1240180).\n- CVE-2025-21898: ftrace: Avoid potential division by zero in function_stat_show() (bsc#1240610).\n- CVE-2025-21899: tracing: Fix bad hist from corrupting named_triggers list (bsc#1240577).\n- CVE-2025-21920: vlan: enforce underlying device type (bsc#1240686).\n- CVE-2025-21938: mptcp: fix 'scheduling while atomic' in mptcp_pm_nl_append_new_local_addr (bsc#1240723).\n- CVE-2025-21959: netfilter: nf_conncount: Fully initialize struct nf_conncount_tuple in insert_tree() (bsc#1240814).\n- CVE-2025-21997: xsk: fix an integer overflow in xp_create_and_assign_umem() (bsc#1240823).\n- CVE-2025-22035: tracing: Fix use-after-free in print_graph_function_flags during tracer switching (bsc#1241544).\n- CVE-2025-22111: kABI fix for net: Remove RTNL dance for SIOCBRADDIF and SIOCBRDELIF (bsc#1241572).\n- CVE-2025-22113: ext4: define ext4_journal_destroy wrapper (bsc#1241617).\n- CVE-2025-23155: net: stmmac: Fix accessing freed irq affinity_hint (bsc#1242573).\n- CVE-2025-37738: ext4: ignore xattrs past end (bsc#1242846).\n- CVE-2025-37743: wifi: ath12k: Avoid memory leak while enabling statistics (bsc#1242163).\n- CVE-2025-37752: net_sched: sch_sfq: move the limit validation (bsc#1242504).\n- CVE-2025-37756: net: tls: explicitly disallow disconnect (bsc#1242515).\n- CVE-2025-37757: tipc: fix memory leak in tipc_link_xmit (bsc#1242521).\n- CVE-2025-37786: net: dsa: free routing table on probe failure (bsc#1242725).\n- CVE-2025-37800: driver core: fix potential NULL pointer dereference in dev_uevent() (bsc#1242849).\n- CVE-2025-37801: spi: spi-imx: Add check for spi_imx_setupxfer() (bsc#1242850).\n- CVE-2025-37811: usb: chipidea: ci_hdrc_imx: fix usbmisc handling (bsc#1242907).\n- CVE-2025-37837: iommu/tegra241-cmdqv: Fix warnings due to dmam_free_coherent() (bsc#1242952).\n- CVE-2025-37844: cifs: avoid NULL pointer dereference in dbg call (bsc#1242946).\n- CVE-2025-37859: page_pool: avoid infinite loop to schedule delayed worker (bsc#1243051).\n- CVE-2025-37862: HID: pidff: Fix null pointer dereference in pidff_find_fields (bsc#1242982).\n- CVE-2025-37865: net: dsa: mv88e6xxx: fix -ENOENT when deleting VLANs and MST is unsupported (bsc#1242954).\n- CVE-2025-37874: net: ngbe: fix memory leak in ngbe_probe() error path (bsc#1242940).\n- CVE-2025-37884: bpf: Fix deadlock between rcu_tasks_trace and event_mutex (bsc#1243060).\n- CVE-2025-37909: net: lan743x: Fix memleak issue when GSO enabled (bsc#1243467).\n- CVE-2025-37917: net: ethernet: mtk-star-emac: fix spinlock recursion issues on rx/tx poll (bsc#1243475).\n- CVE-2025-37921: vxlan: vnifilter: Fix unlocked deletion of default FDB entry (bsc#1243480).\n- CVE-2025-37923: tracing: Fix oob write in trace_seq_to_buffer() (bsc#1243551).\n- CVE-2025-37927: iommu/amd: Fix potential buffer overflow in parse_ivrs_acpihid (bsc#1243620).\n- CVE-2025-37933: octeon_ep: Fix host hang issue during device reboot (bsc#1243628).\n- CVE-2025-37936: perf/x86/intel: KVM: Mask PEBS_ENABLE loaded for guest with vCPU's value (bsc#1243537).\n- CVE-2025-37938: tracing: Verify event formats that have '%*p..' (bsc#1243544).\n- CVE-2025-37945: net: phy: allow MDIO bus PM ops to start/stop state machine for phylink-controlled PHY (bsc#1243538).\n- CVE-2025-37954: smb: client: Avoid race in open_cached_dir with lease breaks (bsc#1243664).\n- CVE-2025-37961: ipvs: fix uninit-value for saddr in do_output_route4 (bsc#1243523).\n- CVE-2025-37967: usb: typec: ucsi: displayport: Fix deadlock (bsc#1243572).\n- CVE-2025-37968: iio: light: opt3001: fix deadlock due to concurrent flag access (bsc#1243571).\n- CVE-2025-37987: pds_core: Prevent possible adminq overflow/stuck condition (bsc#1243542).\n- CVE-2025-37992: net_sched: Flush gso_skb list too during -\u003echange() (bsc#1243698).\n- CVE-2025-37995: module: ensure that kobject_put() is safe for module type kobjects (bsc#1243827).\n- CVE-2025-37997: netfilter: ipset: fix region locking in hash types (bsc#1243832).\n- CVE-2025-37998: openvswitch: Fix unsafe attribute parsing in output_userspace() (bsc#1243836).\n- CVE-2025-38000: sch_hfsc: Fix qlen accounting bug when using peek in hfsc_enqueue() (bsc#1244277).\n- CVE-2025-38001: net_sched: hfsc: Address reentrant enqueue adding class to eltree twice (bsc#1244234).\n- CVE-2025-38011: drm/amdgpu: csa unmap use uninterruptible lock (bsc#1244729).\n- CVE-2025-38018: net/tls: fix kernel panic when alloc_page failed (bsc#1244999).\n- CVE-2025-38053: idpf: fix null-ptr-deref in idpf_features_check (bsc#1244746).\n- CVE-2025-38055: perf/x86/intel: Fix segfault with PEBS-via-PT with sample_freq (bsc#1244747).\n- CVE-2025-38057: espintcp: fix skb leaks (bsc#1244862).\n- CVE-2025-38060: bpf: abort verification if env-\u003ecur_state-\u003eloop_entry != NULL (bsc#1245155).\n- CVE-2025-38072: libnvdimm/labels: Fix divide error in nd_label_data_init() (bsc#1244743).\n\nThe following non-security bugs were fixed:\n\n- ACPI: Add missing prototype for non CONFIG_SUSPEND/CONFIG_X86 case (stable-fixes).\n- ACPI: CPPC: Fix NULL pointer dereference when nosmp is used (git-fixes).\n- ACPI: HED: Always initialize before evged (stable-fixes).\n- ACPI: OSI: Stop advertising support for '3.0 _SCP Extensions' (git-fixes).\n- ACPI: PNP: Add Intel OC Watchdog IDs to non-PNP device list (stable-fixes).\n- ACPI: battery: negate current when discharging (stable-fixes).\n- ACPI: bus: Bail out if acpi_kobj registration fails (stable-fixes).\n- ACPICA: Avoid sequence overread in call to strncmp() (stable-fixes).\n- ACPICA: Utilities: Fix spelling mistake 'Incremement' -\u003e 'Increment' (git-fixes).\n- ACPICA: exserial: do not forget to handle FFixedHW opregions for reading (git-fixes).\n- ACPICA: fix acpi operand cache leak in dswstate.c (stable-fixes).\n- ACPICA: fix acpi parse and parseext cache leaks (stable-fixes).\n- ACPICA: utilities: Fix overflow check in vsnprintf() (stable-fixes).\n- ALSA: hda/intel: Add Thinkpad E15 to PM deny list (stable-fixes).\n- ALSA: hda/realtek: Add quirk for HP Spectre x360 15-df1xxx (stable-fixes).\n- ALSA: hda/realtek: Add quirk for Lenovo Yoga Pro 7 14ASP10 (stable-fixes).\n- ALSA: hda/realtek: Enable PC beep passthrough for HP EliteBook 855 G7 (stable-fixes).\n- ALSA: hda/realtek: Fix built-in mic on ASUS VivoBook X507UAR (git-fixes).\n- ALSA: hda/realtek: Fix built-in mic on ASUS VivoBook X513EA (git-fixes).\n- ALSA: hda/realtek: enable headset mic on Latitude 5420 Rugged (stable-fixes).\n- ALSA: pcm: Fix race of buffer access at PCM OSS layer (stable-fixes).\n- ALSA: seq: Improve data consistency at polling (stable-fixes).\n- ALSA: usb-audio: Accept multiple protocols in GTBs (stable-fixes).\n- ALSA: usb-audio: Add Pioneer DJ DJM-V10 support (stable-fixes).\n- ALSA: usb-audio: Add a quirk for Lenovo Thinkpad Thunderbolt 3 dock (stable-fixes).\n- ALSA: usb-audio: Add implicit feedback quirk for RODE AI-1 (stable-fixes).\n- ALSA: usb-audio: Add name for HP Engage Go dock (stable-fixes).\n- ALSA: usb-audio: Check shutdown at endpoint_set_interface() (stable-fixes).\n- ALSA: usb-audio: Fix NULL pointer deref in snd_usb_power_domain_set() (git-fixes).\n- ALSA: usb-audio: Fix duplicated name in MIDI substream names (stable-fixes).\n- ALSA: usb-audio: Fix out-of-bounds read in snd_usb_get_audioformat_uac3() (git-fixes).\n- ALSA: usb-audio: Rename ALSA kcontrol PCM and PCM1 for the KTMicro sound card (stable-fixes).\n- ALSA: usb-audio: Rename Pioneer mixer channel controls (git-fixes).\n- ALSA: usb-audio: Set MIDI1 flag appropriately for GTB MIDI 1.0 entry (stable-fixes).\n- ALSA: usb-audio: Skip setting clock selector for single connections (stable-fixes).\n- ALSA: usb-audio: Support multiple control interfaces (stable-fixes).\n- ALSA: usb-audio: Support read-only clock selector control (stable-fixes).\n- ALSA: usb-audio: enable support for Presonus Studio 1824c within 1810c file (stable-fixes).\n- ALSA: usb-audio: mixer: Remove temporary string use in parse_clock_source_unit (stable-fixes).\n- ASoC: Intel: avs: Fix deadlock when the failing IPC is SET_D0IX (git-fixes).\n- ASoC: Intel: avs: Verify content returned by parse_int_array() (git-fixes).\n- ASoC: Intel: bytcr_rt5640: Add DMI quirk for Acer Aspire SW3-013 (stable-fixes).\n- ASoC: SOF: Intel: hda-bus: Use PIO mode on ACE2+ platforms (git-fixes).\n- ASoC: SOF: ipc4-pcm: Adjust pipeline_list-\u003epipelines allocation type (git-fixes).\n- ASoC: amd: yc: Add quirk for Lenovo Yoga Pro 7 14ASP9 (stable-fixes).\n- ASoC: apple: mca: Constrain channels according to TDM mask (git-fixes).\n- ASoC: codecs: hda: Fix RPM usage count underflow (git-fixes).\n- ASoC: codecs: pcm3168a: Allow for 24-bit in provider mode (stable-fixes).\n- ASoC: cs42l43: Disable headphone clamps during type detection (stable-fixes).\n- ASoC: imx-card: Adjust over allocation of memory in imx_card_parse_of() (stable-fixes).\n- ASoC: mediatek: mt6359: Add stub for mt6359_accdet_enable_jack_detect (stable-fixes).\n- ASoC: mediatek: mt8188: Add reference for dmic clocks (stable-fixes).\n- ASoC: mediatek: mt8188: Treat DMIC_GAINx_CUR as non-volatile (stable-fixes).\n- ASoC: mediatek: mt8195: Set ETDM1/2 IN/OUT to COMP_DUMMY() (git-fixes).\n- ASoC: meson: meson-card-utils: use of_property_present() for DT parsing (git-fixes).\n- ASoC: ops: Enforce platform maximum on initial value (stable-fixes).\n- ASoC: qcom: sdm845: Add error handling in sdm845_slim_snd_hw_params() (git-fixes).\n- ASoC: qcom: sm8250: explicitly set format in sm8250_be_hw_params_fixup() (stable-fixes).\n- ASoC: rt722-sdca: Add some missing readable registers (stable-fixes).\n- ASoC: soc-dai: check return value at snd_soc_dai_set_tdm_slot() (stable-fixes).\n- ASoC: sun4i-codec: support hp-det-gpios property (stable-fixes).\n- ASoC: tas2764: Add reg defaults for TAS2764_INT_CLK_CFG (stable-fixes).\n- ASoC: tas2764: Enable main IRQs (git-fixes).\n- ASoC: tas2764: Mark SW_RESET as volatile (stable-fixes).\n- ASoC: tas2764: Power up/down amp on mute ops (stable-fixes).\n- ASoC: tas2764: Reinit cache on part reset (git-fixes).\n- ASoC: tas2770: Power cycle amp on ISENSE/VSENSE change (stable-fixes).\n- ASoC: tegra210_ahub: Add check to of_device_get_match_data() (stable-fixes).\n- ASoC: ti: omap-hdmi: Re-add dai_link-\u003eplatform to fix card init (git-fixes).\n- Bluetooth: Fix NULL pointer deference on eir_get_service_data (git-fixes).\n- Bluetooth: L2CAP: Fix not responding with L2CAP_CR_LE_ENCRYPTION (git-fixes).\n- Bluetooth: MGMT: Fix UAF on mgmt_remove_adv_monitor_complete (git-fixes).\n- Bluetooth: MGMT: Fix sparse errors (git-fixes).\n- Bluetooth: MGMT: Remove unused mgmt_pending_find_data (stable-fixes).\n- Bluetooth: MGMT: iterate over mesh commands in mgmt_mesh_foreach() (git-fixes).\n- Bluetooth: Remove pending ACL connection attempts (stable-fixes).\n- Bluetooth: btintel: Check dsbr size from EFI variable (git-fixes).\n- Bluetooth: btintel_pcie: Fix driver not posting maximum rx buffers (git-fixes).\n- Bluetooth: btintel_pcie: Increase the tx and rx descriptor count (git-fixes).\n- Bluetooth: btintel_pcie: Reduce driver buffer posting to prevent race condition (git-fixes).\n- Bluetooth: eir: Fix possible crashes on eir_create_adv_data (git-fixes).\n- Bluetooth: hci_conn: Fix UAF Write in __hci_acl_create_connection_sync (git-fixes).\n- Bluetooth: hci_conn: Only do ACL connections sequentially (stable-fixes).\n- Bluetooth: hci_core: fix list_for_each_entry_rcu usage (git-fixes).\n- Bluetooth: hci_event: Fix not using key encryption size when its known (git-fixes).\n- Bluetooth: hci_qca: move the SoC type check to the right place (git-fixes).\n- Bluetooth: hci_sync: Fix UAF in hci_acl_create_conn_sync (git-fixes).\n- Bluetooth: hci_sync: Fix UAF on hci_abort_conn_sync (git-fixes).\n- Bluetooth: hci_sync: Fix broadcast/PA when using an existing instance (git-fixes).\n- Documentation/rtla: Fix duplicate text about timerlat tracer (git-fixes).\n- Documentation/rtla: Fix typo in common_timerlat_description.rst (git-fixes).\n- Documentation/rtla: Fix typo in rtla-timerlat.rst (git-fixes).\n- Documentation: ACPI: Use all-string data node references (git-fixes).\n- Documentation: fix typo in root= kernel parameter description (git-fixes).\n- Enable livepatching related packages on -RT (jsc#PED-1706)\n- HID: lenovo: Restrict F7/9/11 mode to compact keyboards only (git-fixes).\n- HID: quirks: Add ADATA XPG alpha wireless mouse support (stable-fixes).\n- HID: usbkbd: Fix the bit shift number for LED_KANA (stable-fixes).\n- HID: wacom: fix kobject reference count leak (git-fixes).\n- HID: wacom: fix memory leak on kobject creation failure (git-fixes).\n- HID: wacom: fix memory leak on sysfs attribute creation failure (git-fixes).\n- IB/cm: Drop lockdep assert and WARN when freeing old msg (git-fixes)\n- Input: gpio-keys - fix possible concurrent access in gpio_keys_irq_timer() (git-fixes).\n- Input: ims-pcu - check record size in ims_pcu_flash_firmware() (git-fixes).\n- Input: sparcspkr - avoid unannotated fall-through (stable-fixes).\n- Input: xpad - add more controllers (stable-fixes).\n- KVM: powerpc: Enable commented out BUILD_BUG_ON() assertion (bsc#1215199).\n- KVM: s390: rename PROT_NONE to PROT_TYPE_DUMMY (git-fixes bsc#1245225).\n- Merge branch 'SLE15-SP7' (8ab7501d9efd) into 'SLE15-SP7-RT'\n- MyBS: Correctly generate build flags for non-multibuild package limit (bsc# 1244241) Fixes: 0999112774fc ('MyBS: Use buildflags to set which package to build')\n- MyBS: Do not build kernel-obs-qa with limit_packages Fixes: 58e3f8c34b2b ('bs-upload-kernel: Pass limit_packages also on multibuild')\n- MyBS: Simplify qa_expr generation Start with a 0 which makes the expression valid even if there are no QA repositories (currently does not happen). Then separator is always needed.\n- NFC: nci: uart: Set tty-\u003edisc_data only in success path (git-fixes).\n- NFS: Do not allow waiting for exiting tasks (git-fixes).\n- NFSD: Insulate nfsd4_encode_read_plus() from page boundaries in the encode buffer (git-fixes).\n- NFSv4: Check for delegation validity in nfs_start_delegation_return_locked() (git-fixes).\n- NFSv4: Treat ENETUNREACH errors as fatal for state recovery (git-fixes).\n- PCI/DPC: Initialize aer_err_info before using it (git-fixes).\n- PCI/DPC: Log Error Source ID only when valid (git-fixes).\n- PCI/DPC: Use defines with DPC reason fields (git-fixes).\n- PCI/MSI: Size device MSI domain with the maximum number of vectors (git-fixes).\n- PCI/PM: Set up runtime PM even for devices without PCI PM (git-fixes).\n- PCI: Add ACS quirk for Loongson PCIe (stable-fixes).\n- PCI: Explicitly put devices into D0 when initializing (git-fixes).\n- PCI: Fix lock symmetry in pci_slot_unlock() (git-fixes).\n- PCI: Fix old_size lower bound in calculate_iosize() too (stable-fixes).\n- PCI: apple: Set only available ports up (git-fixes).\n- PCI: apple: Use gpiod_set_value_cansleep in probe flow (git-fixes).\n- PCI: brcmstb: Add a softdep to MIP MSI-X driver (stable-fixes).\n- PCI: brcmstb: Expand inbound window size up to 64GB (stable-fixes).\n- PCI: cadence-ep: Correct PBA offset in .set_msix() callback (git-fixes).\n- PCI: cadence: Fix runtime atomic count underflow (git-fixes).\n- PCI: dw-rockchip: Fix PHY function call sequence in rockchip_pcie_phy_deinit() (git-fixes).\n- PCI: dw-rockchip: Remove PCIE_L0S_ENTRY check from rockchip_pcie_link_up() (git-fixes).\n- PCI: dwc: ep: Correct PBA offset in .set_msix() callback (git-fixes).\n- PCI: dwc: ep: Ensure proper iteration over outbound map windows (stable-fixes).\n- PCI: endpoint: Retain fixed-size BAR size as well as aligned size (git-fixes).\n- PCI: vmd: Disable MSI remapping bypass under Xen (stable-fixes).\n- PM: runtime: fix denying of auto suspend in pm_suspend_timer_fn() (stable-fixes).\n- PM: sleep: Fix power.is_suspended cleanup for direct-complete devices (git-fixes).\n- PM: sleep: Print PM debug messages during hibernation (git-fixes).\n- PM: wakeup: Delete space in the end of string shown by pm_show_wakelocks() (git-fixes).\n- RDMA/core: Fix best page size finding when it can cross SG entries (git-fixes)\n- RDMA/uverbs: Propagate errors from rdma_lookup_get_uobject() (git-fixes)\n- Remove compress-vmlinux.sh /usr/lib/rpm/brp-suse.d/brp-99-compress-vmlinux was added in pesign-obs-integration during SLE12 RC. This workaround can be removed.\n- Remove host-memcpy-hack.h This might have been usefult at some point but we have more things that depend on specific library versions today.\n- Remove try-disable-staging-driver The config for linux-next is autogenerated from master config, and defaults filled for missing options. This is unlikely to enable any staging driver in the first place.\n- Revert 'ALSA: usb-audio: Skip setting clock selector for single connections' (stable-fixes).\n- Revert 'arm64: dts: allwinner: h6: Use RSB for AXP805 PMIC (git-fixes)\n- Revert 'bus: ti-sysc: Probe for l4_wkup and l4_cfg interconnect devices first' (stable-fixes).\n- Revert 'drm/amdgpu: do not allow userspace to create a doorbell BO' (stable-fixes).\n- Revert 'ipv6: save dontfrag in cork (git-fixes).'\n- Revert 'kABI: ipv6: save dontfrag in cork (git-fixes).'\n- Revert 'wifi: mt76: mt7996: fill txd by host driver' (stable-fixes).\n- Revert 'wifi: mwifiex: Fix HT40 bandwidth issue.' (git-fixes).\n- SUNRPC: Do not allow waiting for exiting tasks (git-fixes).\n- SUNRPC: Prevent hang on NFS mount with xprtsec=[m]tls (git-fixes).\n- SUNRPC: rpc_clnt_set_transport() must not change the autobind setting (git-fixes).\n- SUNRPC: rpcbind should never reset the port to the value '0' (git-fixes).\n- USB: serial: pl2303: add new chip PL2303GC-Q20 and PL2303GT-2AB (stable-fixes).\n- VMCI: fix race between vmci_host_setup_notify and vmci_ctx_unset_notify (git-fixes).\n- accel/ivpu: Improve buffer object logging (git-fixes).\n- accel/ivpu: Use dma_resv_lock() instead of a custom mutex (git-fixes).\n- accel/qaic: Mask out SR-IOV PCI resources (stable-fixes).\n- acpi-cpufreq: Fix nominal_freq units to KHz in get_max_boost_ratio() (git-fixes).\n- add bug reference to existing hv_storvsc change (bsc#1245455).\n- arm64: dts: marvell: uDPU: define pinctrl state for alarm LEDs (git-fixes)\n- ata: libata-eh: Do not use ATAPI DMA for a device limited to PIO mode (stable-fixes).\n- ata: pata_via: Force PIO for ATAPI devices on VT6415/VT6330 (stable-fixes).\n- ath10k: snoc: fix unbalanced IRQ enable in crash recovery (git-fixes).\n- backlight: pm8941: Add NULL check in wled_configure() (git-fixes).\n- bnxt: properly flush XDP redirect lists (git-fixes).\n- bpf: Force uprobe bpf program to always return 0 (git-fixes).\n- bs-upload-kernel: Pass limit_packages also on multibuild Fixes: 0999112774fc ('MyBS: Use buildflags to set which package to build') Fixes: 747f601d4156 ('bs-upload-kernel, MyBS, Buildresults: Support multibuild (JSC-SLE#5501, boo#1211226, bsc#1218184)')\n- btrfs: fix fsync of files with no hard links not persisting deletion (git-fixes).\n- btrfs: fix invalid data space release when truncating block in NOCOW mode (git-fixes).\n- btrfs: fix qgroup reservation leak on failure to allocate ordered extent (git-fixes).\n- btrfs: fix wrong start offset for delalloc space release during mmap write (git-fixes).\n- btrfs: remove end_no_trans label from btrfs_log_inode_parent() (git-fixes).\n- btrfs: simplify condition for logging new dentries at btrfs_log_inode_parent() (git-fixes).\n- bus: fsl-mc: do not add a device-link for the UAPI used DPMCP device (git-fixes).\n- bus: fsl-mc: fix GET/SET_TAILDROP command ids (git-fixes).\n- bus: fsl-mc: fix double-free on mc_dev (git-fixes).\n- bus: fsl-mc: increase MC_CMD_COMPLETION_TIMEOUT_MS value (stable-fixes).\n- bus: mhi: host: Fix conflict between power_up and SYSERR (git-fixes).\n- calipso: Fix null-ptr-deref in calipso_req_{set,del}attr() (git-fixes).\n- can: c_can: Use of_property_present() to test existence of DT property (stable-fixes).\n- can: tcan4x5x: fix power regulator retrieval during probe (git-fixes).\n- ceph: Fix incorrect flush end position calculation (git-fixes).\n- ceph: allocate sparse_ext map only for sparse reads (git-fixes).\n- ceph: fix memory leaks in __ceph_sync_read() (git-fixes).\n- cgroup/cpuset: Do not allow creation of local partition over a remote one (bsc#1241166).\n- cgroup/cpuset: Fix race between newly created partition and dying one (bsc#1241166).\n- cifs: change tcon status when need_reconnect is set on it (git-fixes).\n- clocksource: Fix brown-bag boolean thinko in (git-fixes)\n- clocksource: Make watchdog and suspend-timing multiplication (git-fixes)\n- crypto: lrw - Only add ecb if it is not already there (git-fixes).\n- crypto: lzo - Fix compression buffer overrun (stable-fixes).\n- crypto: marvell/cesa - Avoid empty transfer descriptor (git-fixes).\n- crypto: marvell/cesa - Do not chain submitted requests (git-fixes).\n- crypto: marvell/cesa - Handle zero-length skcipher requests (git-fixes).\n- crypto: octeontx2 - suppress auth failure screaming due to negative tests (stable-fixes).\n- crypto: qat - add shutdown handler to qat_420xx (git-fixes).\n- crypto: qat - add shutdown handler to qat_4xxx (git-fixes).\n- crypto: skcipher - Zap type in crypto_alloc_sync_skcipher (stable-fixes).\n- crypto: sun8i-ce - move fallback ahash_request to the end of the struct (git-fixes).\n- crypto: sun8i-ce-cipher - fix error handling in sun8i_ce_cipher_prepare() (git-fixes).\n- crypto: sun8i-ss - do not use sg_dma_len before calling DMA functions (git-fixes).\n- crypto: xts - Only add ecb if it is not already there (git-fixes).\n- devlink: Fix referring to hw_addr attribute during state validation (git-fixes).\n- devlink: fix port dump cmd type (git-fixes).\n- dlm: mask sk_shutdown value (bsc#1228854).\n- dlm: use SHUT_RDWR for SCTP shutdown (bsc#1228854).\n- dmaengine: idxd: cdev: Fix uninitialized use of sva in idxd_cdev_open (stable-fixes).\n- dmaengine: ti: Add NULL check in udma_probe() (git-fixes).\n- drivers/rapidio/rio_cm.c: prevent possible heap overwrite (stable-fixes).\n- drm/amd/display/dm: drop hw_support check in amdgpu_dm_i2c_xfer() (stable-fixes).\n- drm/amd/display: Add debugging message for brightness caps (bsc#1240650).\n- drm/amd/display: Add null pointer check for get_first_active_display() (git-fixes).\n- drm/amd/display: Add support for disconnected eDP streams (stable-fixes).\n- drm/amd/display: Call FP Protect Before Mode Programming/Mode Support (stable-fixes).\n- drm/amd/display: Configure DTBCLK_P with OPTC only for dcn401 (stable-fixes).\n- drm/amd/display: Correct timing_adjust_pending flag setting (stable-fixes).\n- drm/amd/display: Defer BW-optimization-blocked DRR adjustments (git-fixes).\n- drm/amd/display: Do not enable replay when vtotal update is pending (stable-fixes).\n- drm/amd/display: Do not treat wb connector as physical in create_validate_stream_for_sink (stable-fixes).\n- drm/amd/display: Do not try AUX transactions on disconnected link (stable-fixes).\n- drm/amd/display: Ensure DMCUB idle before reset on DCN31/DCN35 (stable-fixes).\n- drm/amd/display: Fix BT2020 YCbCr limited/full range input (stable-fixes).\n- drm/amd/display: Fix DMUB reset sequence for DCN401 (stable-fixes).\n- drm/amd/display: Fix default DC and AC levels (bsc#1240650).\n- drm/amd/display: Fix incorrect DPCD configs while Replay/PSR switch (stable-fixes).\n- drm/amd/display: Fix p-state type when p-state is unsupported (stable-fixes).\n- drm/amd/display: Guard against setting dispclk low for dcn31x (stable-fixes).\n- drm/amd/display: Guard against setting dispclk low when active (stable-fixes).\n- drm/amd/display: Increase block_sequence array size (stable-fixes).\n- drm/amd/display: Initial psr_version with correct setting (stable-fixes).\n- drm/amd/display: Populate register address for dentist for dcn401 (stable-fixes).\n- drm/amd/display: Read LTTPR ALPM caps during link cap retrieval (stable-fixes).\n- drm/amd/display: Request HW cursor on DCN3.2 with SubVP (stable-fixes).\n- drm/amd/display: Skip checking FRL_MODE bit for PCON BW determination (stable-fixes).\n- drm/amd/display: Support multiple options during psr entry (stable-fixes).\n- drm/amd/display: Update CR AUX RD interval interpretation (stable-fixes).\n- drm/amd/display: Use Nominal vBlank If Provided Instead Of Capping It (stable-fixes).\n- drm/amd/display: calculate the remain segments for all pipes (stable-fixes).\n- drm/amd/display: check stream id dml21 wrapper to get plane_id (stable-fixes).\n- drm/amd/display: fix dcn4x init failed (stable-fixes).\n- drm/amd/display: fix link_set_dpms_off multi-display MST corner case (stable-fixes).\n- drm/amd/display: handle max_downscale_src_width fail check (stable-fixes).\n- drm/amd/display: not abort link train when bw is low (stable-fixes).\n- drm/amd/display: pass calculated dram_speed_mts to dml2 (stable-fixes).\n- drm/amd/display: remove minimum Dispclk and apply oem panel timing (stable-fixes).\n- drm/amd/pm: Fetch current power limit from PMFW (stable-fixes).\n- drm/amd/pm: Skip P2S load for SMU v13.0.12 (stable-fixes).\n- drm/amd/pp: Fix potential NULL pointer dereference in atomctrl_initialize_mc_reg_table (git-fixes).\n- drm/amd: Adjust output for discovery error handling (git-fixes).\n- drm/amdgpu/discovery: check ip_discovery fw file available (stable-fixes).\n- drm/amdgpu/gfx11: do not read registers in mqd init (stable-fixes).\n- drm/amdgpu/gfx12: do not read registers in mqd init (stable-fixes).\n- drm/amdgpu/mes11: fix set_hw_resources_1 calculation (stable-fixes).\n- drm/amdgpu: Allow P2P access through XGMI (stable-fixes).\n- drm/amdgpu: Do not program AGP BAR regs under SRIOV in gfxhub_v1_0.c (stable-fixes).\n- drm/amdgpu: Fix missing drain retry fault the last entry (stable-fixes).\n- drm/amdgpu: Fix the race condition for draining retry fault (stable-fixes).\n- drm/amdgpu: Set snoop bit for SDMA for MI series (stable-fixes).\n- drm/amdgpu: Skip pcie_replay_count sysfs creation for VF (stable-fixes).\n- drm/amdgpu: Update SRIOV video codec caps (stable-fixes).\n- drm/amdgpu: Use active umc info from discovery (stable-fixes).\n- drm/amdgpu: adjust drm_firmware_drivers_only() handling (stable-fixes).\n- drm/amdgpu: enlarge the VBIOS binary size limit (stable-fixes).\n- drm/amdgpu: read back register after written for VCN v4.0.5 (stable-fixes).\n- drm/amdgpu: release xcp_mgr on exit (stable-fixes).\n- drm/amdgpu: remove all KFD fences from the BO on release (stable-fixes).\n- drm/amdgpu: reset psp-\u003ecmd to NULL after releasing the buffer (stable-fixes).\n- drm/amdgpu: switch job hw_fence to amdgpu_fence (git-fixes).\n- drm/amdkfd: Correct F8_MODE for gfx950 (git-fixes).\n- drm/amdkfd: KFD release_work possible circular locking (stable-fixes).\n- drm/amdkfd: Set per-process flags only once cik/vi (stable-fixes).\n- drm/amdkfd: Set per-process flags only once for gfx9/10/11/12 (stable-fixes).\n- drm/amdkfd: fix missing L2 cache info in topology (stable-fixes).\n- drm/amdkfd: set precise mem ops caps to disabled for gfx 11 and 12 (stable-fixes).\n- drm/ast: Find VBIOS mode from regular display size (stable-fixes).\n- drm/ast: Fix comment on modeset lock (git-fixes).\n- drm/atomic: clarify the rules around drm_atomic_state-\u003eallow_modeset (stable-fixes).\n- drm/bridge: cdns-dsi: Check return value when getting default PHY config (git-fixes).\n- drm/bridge: cdns-dsi: Fix connecting to next bridge (git-fixes).\n- drm/bridge: cdns-dsi: Fix phy de-init and flag it so (git-fixes).\n- drm/bridge: cdns-dsi: Fix the clock variable for mode_valid() (git-fixes).\n- drm/bridge: cdns-dsi: Wait for Clk and Data Lanes to be ready (git-fixes).\n- drm/bridge: lt9611uxc: Fix an error handling path in lt9611uxc_probe() (git-fixes).\n- drm/buddy: fix issue that force_merge cannot free all roots (stable-fixes).\n- drm/etnaviv: Protect the scheduler's pending list with its lock (git-fixes).\n- drm/i915/gem: Allow EXEC_CAPTURE on recoverable contexts on DG1 (git-fixes).\n- drm/i915/guc: Check if expecting reply before decrementing outstanding_submission_g2h (git-fixes).\n- drm/i915/guc: Handle race condition where wakeref count drops below 0 (git-fixes).\n- drm/i915/pmu: Fix build error with GCOV and AutoFDO enabled (git-fixes).\n- drm/i915/psr: Fix using wrong mask in REG_FIELD_PREP (git-fixes).\n- drm/i915: fix build error some more (git-fixes).\n- drm/mediatek: Fix kobject put for component sub-drivers (git-fixes).\n- drm/mediatek: mtk_dpi: Add checks for reg_h_fre_con existence (stable-fixes).\n- drm/mediatek: mtk_drm_drv: Fix kobject put for mtk_mutex device ptr (git-fixes).\n- drm/mediatek: mtk_drm_drv: Unbind secondary mmsys components on err (git-fixes).\n- drm/msm/a6xx: Disable rgb565_predicator on Adreno 7c3 (git-fixes).\n- drm/msm/a7xx: Call CP_RESET_CONTEXT_STATE (git-fixes).\n- drm/msm/disp: Correct porch timing for SDM845 (git-fixes).\n- drm/msm/dpu: Clear CTL_FETCH_PIPE_ACTIVE before blend setup (git-fixes).\n- drm/msm/dpu: Clear CTL_FETCH_PIPE_ACTIVE on ctl_path reset (git-fixes).\n- drm/msm/dpu: enable SmartDMA on SC8180X (git-fixes).\n- drm/msm/dpu: enable SmartDMA on SM8150 (git-fixes).\n- drm/msm/dsi/dsi_phy_10nm: Fix missing initial VCO rate (git-fixes).\n- drm/msm/gpu: Fix crash when throttling GPU immediately during boot (git-fixes).\n- drm/msm: Fix CP_RESET_CONTEXT_STATE bitfield names (git-fixes).\n- drm/nouveau/bl: increase buffer size to avoid truncate warning (git-fixes).\n- drm/nouveau: fix the broken marco GSP_MSG_MAX_SIZE (stable-fixes).\n- drm/panel-edp: Add Starry 116KHD024006 (stable-fixes).\n- drm/panel-simple: fix the warnings for the Evervision VGG644804 (git-fixes).\n- drm/panel: samsung-sofef00: Drop s6e3fc2x01 support (git-fixes).\n- drm/panic: add missing space (git-fixes).\n- drm/panthor: Fix GPU_COHERENCY_ACE[_LITE] definitions (git-fixes).\n- drm/panthor: Update panthor_mmu::irq::mask when needed (git-fixes).\n- drm/rockchip: vop2: Add uv swap for cluster window (stable-fixes).\n- drm/rockchip: vop2: Improve display modes handling on RK3588 HDMI0 (stable-fixes).\n- drm/ssd130x: fix ssd132x_clear_screen() columns (git-fixes).\n- drm/tegra: Assign plane type before registration (git-fixes).\n- drm/tegra: Fix a possible null pointer dereference (git-fixes).\n- drm/tegra: rgb: Fix the unbound reference count (git-fixes).\n- drm/udl: Unregister device before cleaning up on disconnect (git-fixes).\n- drm/v3d: Add clock handling (stable-fixes).\n- drm/v3d: Avoid NULL pointer dereference in `v3d_job_update_stats()` (stable-fixes).\n- drm/vc4: tests: Use return instead of assert (git-fixes).\n- drm/vkms: Adjust vkms_state-\u003eactive_planes allocation type (git-fixes).\n- drm/vmwgfx: Add error path for xa_store in vmw_bo_add_detached_resource (git-fixes).\n- drm/vmwgfx: Add seqno waiter for sync_files (git-fixes).\n- drm/vmwgfx: Fix dumb buffer leak (git-fixes).\n- drm/xe/bmg: Update Wa_16023588340 (git-fixes).\n- drm/xe/d3cold: Set power state to D3Cold during s2idle/s3 (git-fixes).\n- drm/xe/debugfs: Add missing xe_pm_runtime_put in wedge_mode_set (stable-fixes).\n- drm/xe/debugfs: fixed the return value of wedged_mode_set (stable-fixes).\n- drm/xe/display: Add check for alloc_ordered_workqueue() (git-fixes).\n- drm/xe/gt: Update handling of xe_force_wake_get return (stable-fixes).\n- drm/xe/oa: Ensure that polled read returns latest data (stable-fixes).\n- drm/xe/pf: Create a link between PF and VF devices (stable-fixes).\n- drm/xe/pf: Reset GuC VF config when unprovisioning critical resource (stable-fixes).\n- drm/xe/relay: Do not use GFP_KERNEL for new transactions (stable-fixes).\n- drm/xe/sa: Always call drm_suballoc_manager_fini() (stable-fixes).\n- drm/xe/sched: stop re-submitting signalled jobs (git-fixes).\n- drm/xe/vf: Retry sending MMIO request to GUC on timeout error (stable-fixes).\n- drm/xe/vm: move rebind_work init earlier (git-fixes).\n- drm/xe/xe2hpg: Add Wa_22021007897 (stable-fixes).\n- drm/xe: Create LRC BO without VM (git-fixes).\n- drm/xe: Do not attempt to bootstrap VF in execlists mode (stable-fixes).\n- drm/xe: Fix memset on iomem (git-fixes).\n- drm/xe: Fix xe_tile_init_noalloc() error propagation (stable-fixes).\n- drm/xe: Make xe_gt_freq part of the Documentation (git-fixes).\n- drm/xe: Move suballocator init to after display init (stable-fixes).\n- drm/xe: Nuke VM's mapping upon close (stable-fixes).\n- drm/xe: Process deferred GGTT node removals on device unwind (git-fixes).\n- drm/xe: Reject BO eviction if BO is bound to current VM (stable-fixes).\n- drm/xe: Retry BO allocation (stable-fixes).\n- drm/xe: Rework eviction rejection of bound external bos (git-fixes).\n- drm/xe: Save the gt pointer in lrc and drop the tile (stable-fixes).\n- drm/xe: Stop ignoring errors from xe_ttm_stolen_mgr_init() (stable-fixes).\n- drm/xe: Wire up device shutdown handler (stable-fixes).\n- drm/xe: remove unmatched xe_vm_unlock() from __xe_exec_queue_init() (git-fixes).\n- drm/xe: xe_gen_wa_oob: replace program_invocation_short_name (stable-fixes).\n- drm: Add valid clones check (stable-fixes).\n- drm: bridge: adv7511: fill stream capabilities (stable-fixes).\n- drm: rcar-du: Fix memory leak in rcar_du_vsps_init() (git-fixes).\n- dummycon: Trigger redraw when switching consoles with deferred takeover (git-fixes).\n- e1000e: set fixed clock frequency indication for Nahum 11 and Nahum 13 (git-fixes).\n- efi/libstub: Describe missing 'out' parameter in efi_load_initrd (git-fixes).\n- fbcon: Make sure modelist not set on unregistered console (stable-fixes).\n- fbcon: Use correct erase colour for clearing in fbcon (stable-fixes).\n- fbdev/efifb: Remove PM for parent device (bsc#1244261).\n- fbdev: Fix do_register_framebuffer to prevent null-ptr-deref in fb_videomode_to_var (git-fixes).\n- fbdev: Fix fb_set_var to prevent null-ptr-deref in fb_videomode_to_var (git-fixes).\n- fbdev: core: fbcvt: avoid division by 0 in fb_cvt_hperiod() (git-fixes).\n- fbdev: core: tileblit: Implement missing margin clearing for tileblit (stable-fixes).\n- fbdev: fsl-diu-fb: add missing device_remove_file() (stable-fixes).\n- fgraph: Still initialize idle shadow stacks when starting (git-fixes).\n- firmware: SDEI: Allow sdei initialization without ACPI_APEI_GHES (git-fixes).\n- firmware: arm_ffa: Reject higher major version as incompatible (stable-fixes).\n- firmware: arm_ffa: Set dma_mask for ffa devices (stable-fixes).\n- firmware: arm_scmi: Relax duplicate name constraint across protocol ids (stable-fixes).\n- firmware: psci: Fix refcount leak in psci_dt_init (git-fixes).\n- fpga: altera-cvp: Increase credit timeout (stable-fixes).\n- fs/nfs/read: fix double-unlock bug in nfs_return_empty_folio() (git-fixes).\n- gpio: mlxbf3: only get IRQ for device instance 0 (git-fixes).\n- gpio: pca953x: Simplify code with cleanup helpers (stable-fixes).\n- gpio: pca953x: Split pca953x_restore_context() and pca953x_save_context() (stable-fixes).\n- gpio: pca953x: fix IRQ storm on system wake up (git-fixes).\n- gpiolib: Revert 'Do not WARN on gpiod_put() for optional GPIO' (stable-fixes).\n- gve: Fix RX_BUFFERS_POSTED stat to report per-queue fill_cnt (git-fixes).\n- gve: add missing NULL check for gve_alloc_pending_packet() in TX DQO (git-fixes).\n- hwmon: (asus-ec-sensors) check sensor index in read_string() (git-fixes).\n- hwmon: (dell-smm) Increment the number of fans (stable-fixes).\n- hwmon: (ftsteutates) Fix TOCTOU race in fts_read() (git-fixes).\n- hwmon: (gpio-fan) Add missing mutex locks (stable-fixes).\n- hwmon: (nct6775): Actually make use of the HWMON_NCT6775 symbol namespace (git-fixes).\n- hwmon: (occ) Rework attribute registration for stack usage (git-fixes).\n- hwmon: (occ) fix unaligned accesses (git-fixes).\n- hwmon: (peci/dimmtemp) Do not provide fake thresholds data (git-fixes).\n- hwmon: (xgene-hwmon) use appropriate type for the latency value (stable-fixes).\n- hwmon: corsair-psu: add USB id of HX1200i Series 2023 psu (git-fixes).\n- i2c: designware: Invoke runtime suspend on quick slave re-registration (stable-fixes).\n- i2c: npcm: Add clock toggle recovery (stable-fixes).\n- i2c: pxa: fix call balance of i2c-\u003eclk handling routines (stable-fixes).\n- i2c: qup: Vote for interconnect bandwidth to DRAM (stable-fixes).\n- i2c: robotfuzz-osif: disable zero-length read messages (git-fixes).\n- i2c: tegra: check msg length in SMBUS block read (bsc#1242086)\n- i2c: tiny-usb: disable zero-length read messages (git-fixes).\n- i3c: master: svc: Fix implicit fallthrough in svc_i3c_master_ibi_work() (git-fixes).\n- i3c: master: svc: Fix missing STOP for master request (stable-fixes).\n- i3c: master: svc: Flush FIFO before sending Dynamic Address Assignment(DAA) (stable-fixes).\n- i40e: retry VFLR handling if there is ongoing VF reset (git-fixes).\n- i40e: return false from i40e_reset_vf if reset is in progress (git-fixes).\n- ice: Fix LACP bonds without SRIOV environment (git-fixes).\n- ice: create new Tx scheduler nodes for new queues only (git-fixes).\n- ice: fix Tx scheduler error handling in XDP callback (git-fixes).\n- ice: fix rebuilding the Tx scheduler tree for large queue counts (git-fixes).\n- ice: fix vf-\u003enum_mac count with port representors (git-fixes).\n- ieee802154: ca8210: Use proper setters and getters for bitwise types (stable-fixes).\n- iio: accel: fxls8962af: Fix temperature scan element sign (git-fixes).\n- iio: adc: ad7124: Fix 3dB filter frequency reading (git-fixes).\n- iio: adc: ad7606_spi: fix reg write value mask (git-fixes).\n- iio: filter: admv8818: Support frequencies \u003e= 2^32 (git-fixes).\n- iio: filter: admv8818: fix band 4, state 15 (git-fixes).\n- iio: filter: admv8818: fix integer overflow (git-fixes).\n- iio: filter: admv8818: fix range calculation (git-fixes).\n- iio: imu: inv_icm42600: Fix temperature calculation (git-fixes).\n- ima: Suspend PCR extends and log appends when rebooting (bsc#1210025 ltc#196650).\n- ima: process_measurement() needlessly takes inode_lock() on MAY_READ (stable-fixes).\n- intel_th: avoid using deprecated page-\u003emapping, index fields (stable-fixes).\n- iommu: Protect against overflow in iommu_pgsize() (git-fixes).\n- iommu: Skip PASID validation for devices without PASID capability (bsc#1244100)\n- iommu: Validate the PASID in iommu_attach_device_pasid() (bsc#1244100)\n- ip6mr: fix tables suspicious RCU usage (git-fixes).\n- ip_tunnel: annotate data-races around t-\u003eparms.link (git-fixes).\n- ipmr: fix incorrect parameter validation in the ip_mroute_getsockopt() function (git-fixes).\n- ipmr: fix tables suspicious RCU usage (git-fixes).\n- ipv4: Convert ip_route_input() to dscp_t (git-fixes).\n- ipv4: Correct/silence an endian warning in __ip_do_redirect (git-fixes).\n- ipv6: save dontfrag in cork (git-fixes).\n- ipvs: Always clear ipvs_property flag in skb_scrub_packet() (git-fixes).\n- isolcpus: fix bug in returning number of allocated cpumask (bsc#1243774).\n- jffs2: check jffs2_prealloc_raw_node_refs() result in few other places (git-fixes).\n- jffs2: check that raw node were preallocated before writing summary (git-fixes).\n- kABI workaround for hda_codec.beep_just_power_on flag (git-fixes).\n- kABI: PCI: endpoint: Retain fixed-size BAR size as well as aligned size (git-fixes).\n- kABI: ipv6: save dontfrag in cork (git-fixes).\n- kABI: serial: mctrl_gpio: split disable_ms into sync and no_sync APIs (git-fixes).\n- kabi: restore layout of struct cgroup_subsys (bsc#1241166).\n- kabi: restore layout of struct mem_control (jsc#PED-12551).\n- kabi: restore layout of struct page_counter (jsc#PED-12551).\n- kernel-source: Remove log.sh from sources\n- leds: pwm-multicolor: Add check for fwnode_property_read_u32 (stable-fixes).\n- loop: Add sanity check for read/write_iter (git-fixes).\n- loop: add file_start_write() and file_end_write() (git-fixes).\n- mailbox: use error ret code of of_parse_phandle_with_args() (stable-fixes).\n- md/raid1,raid10: do not handle IO error for REQ_RAHEAD and REQ_NOWAIT (git-fixes).\n- md/raid1: Add check for missing source disk in process_checks() (git-fixes).\n- media: adv7180: Disable test-pattern control on adv7180 (stable-fixes).\n- media: c8sectpfe: Call of_node_put(i2c_bus) only once in c8sectpfe_probe() (stable-fixes).\n- media: ccs-pll: Check for too high VT PLL multiplier in dual PLL case (git-fixes).\n- media: ccs-pll: Correct the upper limit of maximum op_pre_pll_clk_div (git-fixes).\n- media: ccs-pll: Start OP pre-PLL multiplier search from correct value (git-fixes).\n- media: ccs-pll: Start VT pre-PLL multiplier search from correct value (git-fixes).\n- media: cx231xx: set device_caps for 417 (stable-fixes).\n- media: cxusb: no longer judge rbuf when the write fails (git-fixes).\n- media: davinci: vpif: Fix memory leak in probe error path (git-fixes).\n- media: gspca: Add error handling for stv06xx_read_sensor() (git-fixes).\n- media: i2c: imx219: Correct the minimum vblanking value (stable-fixes).\n- media: imx-jpeg: Cleanup after an allocation error (git-fixes).\n- media: imx-jpeg: Drop the first error frames (git-fixes).\n- media: imx-jpeg: Move mxc_jpeg_free_slot_data() ahead (git-fixes).\n- media: imx-jpeg: Reset slot data pointers when freed (git-fixes).\n- media: intel/ipu6: Fix dma mask for non-secure mode (git-fixes).\n- media: ipu6: Remove workaround for Meteor Lake ES2 (git-fixes).\n- media: nxp: imx8-isi: better handle the m2m usage_count (git-fixes).\n- media: omap3isp: use sgtable-based scatterlist wrappers (git-fixes).\n- media: ov2740: Move pm-runtime cleanup on probe-errors to proper place (git-fixes).\n- media: ov5675: suppress probe deferral errors (git-fixes).\n- media: ov8856: suppress probe deferral errors (git-fixes).\n- media: platform: mtk-mdp3: Remove unused mdp_get_plat_device (git-fixes).\n- media: qcom: camss: csid: Only add TPG v4l2 ctrl if TPG hardware is available (stable-fixes).\n- media: rkvdec: Fix frame size enumeration (git-fixes).\n- media: tc358746: improve calculation of the D-PHY timing registers (stable-fixes).\n- media: test-drivers: vivid: do not call schedule in loop (stable-fixes).\n- media: uvcvideo: Add sanity check to uvc_ioctl_xu_ctrl_map (stable-fixes).\n- media: uvcvideo: Fix deferred probing error (git-fixes).\n- media: uvcvideo: Handle uvc menu translation inside uvc_get_le_value (stable-fixes).\n- media: uvcvideo: Return the number of processed controls (git-fixes).\n- media: v4l2-dev: fix error handling in __video_register_device() (git-fixes).\n- media: v4l: Memset argument to 0 before calling get_mbus_config pad op (stable-fixes).\n- media: venus: Fix probe error handling (git-fixes).\n- media: verisilicon: Free post processor buffers on error (git-fixes).\n- media: videobuf2: use sgtable-based scatterlist wrappers (git-fixes).\n- media: vidtv: Terminating the subsequent process of initialization failure (git-fixes).\n- media: vivid: Change the siize of the composing (git-fixes).\n- mfd: exynos-lpass: Avoid calling exynos_lpass_disable() twice in exynos_lpass_remove() (git-fixes).\n- mfd: stmpe-spi: Correct the name used in MODULE_DEVICE_TABLE (git-fixes).\n- mfd: tps65219: Remove TPS65219_REG_TI_DEV_ID check (stable-fixes).\n- mkspec: Exclude rt flavor from kernel-syms dependencies (bsc#1244337).\n- mm, memcg: cg2 memory{.swap,}.peak write handlers (jsc#PED-12551).\n- mm/hugetlb: fix huge_pmd_unshare() vs GUP-fast race (bsc#1245431).\n- mm/hugetlb: unshare page tables during VMA split, not before (bsc#1245431).\n- mm/memcontrol: export memcg.swap watermark via sysfs for v2 memcg (jsc#PED-12551).\n- mmc: Add quirk to disable DDR50 tuning (stable-fixes).\n- mmc: dw_mmc: add exynos7870 DW MMC support (stable-fixes).\n- mmc: host: Wait for Vdd to settle on card power off (stable-fixes).\n- mmc: sdhci: Disable SD card clock before changing parameters (stable-fixes).\n- mtd: nand: ecc-mxic: Fix use of uninitialized variable ret (git-fixes).\n- mtd: nand: sunxi: Add randomizer configuration before randomizer enable (git-fixes).\n- mtd: rawnand: sunxi: Add randomizer configuration in sunxi_nfc_hw_ecc_write_chunk (git-fixes).\n- neighbour: Do not let neigh_forced_gc() disable preemption for long (git-fixes).\n- net/mdiobus: Fix potential out-of-bounds clause 45 read/write access (git-fixes).\n- net/mdiobus: Fix potential out-of-bounds read/write access (git-fixes).\n- net/mlx4_en: Prevent potential integer overflow calculating Hz (git-fixes).\n- net/mlx5: Add error handling in mlx5_query_nic_vport_node_guid() (git-fixes).\n- net/mlx5: Ensure fw pages are always allocated on same NUMA (git-fixes).\n- net/mlx5: Fix ECVF vports unload on shutdown flow (git-fixes).\n- net/mlx5: Fix return value when searching for existing flow group (git-fixes).\n- net/mlx5_core: Add error handling inmlx5_query_nic_vport_qkey_viol_cntr() (git-fixes).\n- net/mlx5e: Fix leak of Geneve TLV option object (git-fixes).\n- net/neighbor: clear error in case strict check is not set (git-fixes).\n- net/sched: fix use-after-free in taprio_dev_notifier (git-fixes).\n- net: Fix TOCTOU issue in sk_is_readable() (git-fixes).\n- net: Implement missing getsockopt(SO_TIMESTAMPING_NEW) (git-fixes).\n- net: add rcu safety to rtnl_prop_list_size() (git-fixes).\n- net: fix udp gso skb_segment after pull from frag_list (git-fixes).\n- net: give more chances to rcu in netdev_wait_allrefs_any() (git-fixes).\n- net: ice: Perform accurate aRFS flow match (git-fixes).\n- net: ipv4: fix a memleak in ip_setup_cork (git-fixes).\n- net: linkwatch: use system_unbound_wq (git-fixes).\n- net: mana: Add support for Multi Vports on Bare metal (bsc#1244229).\n- net: mana: Record doorbell physical address in PF mode (bsc#1244229).\n- net: page_pool: fix warning code (git-fixes).\n- net: phy: clear phydev-\u003edevlink when the link is deleted (git-fixes).\n- net: phy: fix up const issues in to_mdio_device() and to_phy_device() (git-fixes).\n- net: phy: move phy_link_change() prior to mdio_bus_phy_may_suspend() (bsc#1243538)\n- net: phy: mscc: Fix memory leak when using one step timestamping (git-fixes).\n- net: phy: mscc: Stop clearing the the UDPv4 checksum for L2 frames (git-fixes).\n- net: sched: cls_u32: Fix allocation size in u32_init() (git-fixes).\n- net: sched: consistently use rcu_replace_pointer() in taprio_change() (git-fixes).\n- net: sched: em_text: fix possible memory leak in em_text_destroy() (git-fixes).\n- net: sched: fix erspan_opt settings in cls_flower (git-fixes).\n- net: usb: aqc111: debug info before sanitation (git-fixes).\n- net: usb: aqc111: fix error handling of usbnet read calls (git-fixes).\n- net: wwan: t7xx: Fix napi rx poll issue (git-fixes).\n- net_sched: ets: fix a race in ets_qdisc_change() (git-fixes).\n- net_sched: prio: fix a race in prio_tune() (git-fixes).\n- net_sched: red: fix a race in __red_change() (git-fixes).\n- net_sched: sch_fifo: implement lockless __fifo_dump() (bsc#1237312)\n- net_sched: sch_sfq: reject invalid perturb period (git-fixes).\n- net_sched: sch_sfq: use a temporary work area for validating configuration (bsc#1232504)\n- net_sched: tbf: fix a race in tbf_change() (git-fixes).\n- netdev-genl: Hold rcu_read_lock in napi_get (git-fixes).\n- netlink: fix potential sleeping issue in mqueue_flush_file (git-fixes).\n- netlink: specs: dpll: replace underscores with dashes in names (git-fixes).\n- netpoll: Use rcu_access_pointer() in __netpoll_setup (git-fixes).\n- netpoll: hold rcu read lock in __netpoll_send_skb() (git-fixes).\n- nfsd: Initialize ssc before laundromat_work to prevent NULL dereference (git-fixes).\n- nfsd: nfsd4_spo_must_allow() must check this is a v4 compound request (git-fixes).\n- nfsd: validate the nfsd_serv pointer before calling svc_wake_up (git-fixes).\n- ntp: Clamp maxerror and esterror to operating range (git-fixes)\n- ntp: Remove invalid cast in time offset math (git-fixes)\n- ntp: Safeguard against time_constant overflow (git-fixes)\n- nvme-fc: do not reference lsrsp after failure (bsc#1245193).\n- nvme-pci: add NVME_QUIRK_NO_DEEPEST_PS quirk for SOLIDIGM P44 Pro (git-fixes).\n- nvme-pci: add quirks for WDC Blue SN550 15b7:5009 (git-fixes).\n- nvme-pci: add quirks for device 126f:1001 (git-fixes).\n- nvme: always punt polled uring_cmd end_io work to task_work (git-fixes).\n- nvme: fix command limits status code (git-fixes).\n- nvme: fix implicit bool to flags conversion (git-fixes).\n- nvmet-fc: free pending reqs on tgtport unregister (bsc#1245193).\n- nvmet-fc: take tgtport refs for portentry (bsc#1245193).\n- nvmet-fcloop: access fcpreq only when holding reqlock (bsc#1245193).\n- nvmet-fcloop: add missing fcloop_callback_host_done (bsc#1245193).\n- nvmet-fcloop: allocate/free fcloop_lsreq directly (bsc#1245193).\n- nvmet-fcloop: do not wait for lport cleanup (bsc#1245193).\n- nvmet-fcloop: drop response if targetport is gone (bsc#1245193).\n- nvmet-fcloop: prevent double port deletion (bsc#1245193).\n- nvmet-fcloop: refactor fcloop_delete_local_port (bsc#1245193).\n- nvmet-fcloop: refactor fcloop_nport_alloc and track lport (bsc#1245193).\n- nvmet-fcloop: remove nport from list on last user (bsc#1245193).\n- nvmet-fcloop: track ref counts for nports (bsc#1245193).\n- nvmet-fcloop: update refs on tfcp_req (bsc#1245193).\n- orangefs: Do not truncate file size (git-fixes).\n- pNFS/flexfiles: Report ENETDOWN as a connection error (git-fixes).\n- page_pool: Fix use-after-free in page_pool_recycle_in_ring (git-fixes).\n- phy: core: do not require set_mode() callback for phy_get_mode() to work (stable-fixes).\n- phy: qcom-qmp-usb: Fix an NULL vs IS_ERR() bug (git-fixes).\n- phy: renesas: rcar-gen3-usb2: Add support to initialize the bus (stable-fixes).\n- phy: renesas: rcar-gen3-usb2: Assert PLL reset on PHY power off (git-fixes).\n- phy: renesas: rcar-gen3-usb2: Lock around hardware registers and driver data (git-fixes).\n- phy: renesas: rcar-gen3-usb2: Move IRQ request in probe (stable-fixes).\n- pinctrl-tegra: Restore SFSEL bit when freeing pins (stable-fixes).\n- pinctrl: armada-37xx: propagate error from armada_37xx_gpio_get() (stable-fixes).\n- pinctrl: armada-37xx: propagate error from armada_37xx_gpio_get_direction() (stable-fixes).\n- pinctrl: armada-37xx: propagate error from armada_37xx_pmx_gpio_set_direction() (stable-fixes).\n- pinctrl: armada-37xx: propagate error from armada_37xx_pmx_set_by_name() (stable-fixes).\n- pinctrl: armada-37xx: set GPIO output value before setting direction (git-fixes).\n- pinctrl: armada-37xx: use correct OUTPUT_VAL register for GPIOs \u003e 31 (git-fixes).\n- pinctrl: at91: Fix possible out-of-boundary access (git-fixes).\n- pinctrl: bcm281xx: Use 'unsigned int' instead of bare 'unsigned' (stable-fixes).\n- pinctrl: devicetree: do not goto err when probing hogs in pinctrl_dt_to_map (stable-fixes).\n- pinctrl: mcp23s08: Reset all pins to input at probe (stable-fixes).\n- pinctrl: meson: define the pull up/down resistor value as 60 kOhm (stable-fixes).\n- pinctrl: qcom: pinctrl-qcm2290: Add missing pins (git-fixes).\n- pinctrl: st: Drop unused st_gpio_bank() function (git-fixes).\n- pinctrl: tegra: Fix off by one in tegra_pinctrl_get_group() (git-fixes).\n- platform/x86/amd/hsmp: Add new error code and error logs (jsc#PED-13094).\n- platform/x86/amd/hsmp: Add support for HSMP protocol version 7 messages (jsc#PED-13094).\n- platform/x86/amd/hsmp: Change generic plat_dev name to hsmp_pdev (jsc#PED-13094).\n- platform/x86/amd/hsmp: Change the error type (jsc#PED-13094).\n- platform/x86/amd/hsmp: Convert amd_hsmp_rdwr() to a function pointer (jsc#PED-13094).\n- platform/x86/amd/hsmp: Create hsmp/ directory (jsc#PED-13094).\n- platform/x86/amd/hsmp: Create separate ACPI, plat and common drivers (jsc#PED-13094).\n- platform/x86/amd/hsmp: Create wrapper function init_acpi() (jsc#PED-13094).\n- platform/x86/amd/hsmp: Make amd_hsmp and hsmp_acpi as mutually exclusive drivers (jsc#PED-13094).\n- platform/x86/amd/hsmp: Make hsmp_pdev static instead of global (jsc#PED-13094).\n- platform/x86/amd/hsmp: Move ACPI code to acpi.c (jsc#PED-13094).\n- platform/x86/amd/hsmp: Move platform device specific code to plat.c (jsc#PED-13094).\n- platform/x86/amd/hsmp: Move structure and macros to header file (jsc#PED-13094).\n- platform/x86/amd/hsmp: Report power via hwmon sensor (jsc#PED-13094).\n- platform/x86/amd/hsmp: Use a single DRIVER_VERSION for all hsmp modules (jsc#PED-13094).\n- platform/x86/amd/hsmp: Use dev_groups in the driver structure (jsc#PED-13094).\n- platform/x86/amd/hsmp: Use name space while exporting module symbols (jsc#PED-13094).\n- platform/x86/amd/hsmp: acpi: Add sysfs files to display HSMP telemetry (jsc#PED-13094).\n- platform/x86/amd/hsmp: fix building with CONFIG_HWMON=m (jsc#PED-13094).\n- platform/x86/amd/hsmp: mark hsmp_msg_desc_table as maybe_unused (git-fixes).\n- platform/x86/amd: pmc: Clear metrics table at start of cycle (git-fixes).\n- platform/x86/intel-uncore-freq: Fail module load when plat_info is NULL (git-fixes).\n- platform/x86: amd: Use *-y instead of *-objs in Makefiles (jsc#PED-13094).\n- platform/x86: dell_rbu: Fix list usage (git-fixes).\n- platform/x86: dell_rbu: Stop overwriting data buffer (git-fixes).\n- platform/x86: fujitsu-laptop: Support Lifebook S2110 hotkeys (git-fixes).\n- platform/x86: fujitsu-laptop: Support Lifebook S2110 hotkeys (stable-fixes).\n- platform/x86: hp-bioscfg: Annotate struct bios_args with __counted_by (jsc#PED-13019).\n- platform/x86: hp-bioscfg: Change how enum possible values size is evaluated (jsc#PED-13019).\n- platform/x86: hp-bioscfg: Change how order list size is evaluated (jsc#PED-13019).\n- platform/x86: hp-bioscfg: Change how password encoding size is evaluated (jsc#PED-13019).\n- platform/x86: hp-bioscfg: Change how prerequisites size is evaluated (jsc#PED-13019).\n- platform/x86: hp-bioscfg: Fix error handling in hp_add_other_attributes() (jsc#PED-13019).\n- platform/x86: hp-bioscfg: Fix memory leaks in attribute packages (jsc#PED-13019).\n- platform/x86: hp-bioscfg: Fix reference leak (jsc#PED-13019).\n- platform/x86: hp-bioscfg: Fix uninitialized variable errors (jsc#PED-13019).\n- platform/x86: hp-bioscfg: Makefile (jsc#PED-13019).\n- platform/x86: hp-bioscfg: Remove duplicate use of variable in inner loop (jsc#PED-13019).\n- platform/x86: hp-bioscfg: Remove unused obj in hp_add_other_attributes() (jsc#PED-13019).\n- platform/x86: hp-bioscfg: Removed needless asm-generic (jsc#PED-13019).\n- platform/x86: hp-bioscfg: Replace the word HACK from source code (jsc#PED-13019).\n- platform/x86: hp-bioscfg: Simplify return check in hp_add_other_attributes() (jsc#PED-13019).\n- platform/x86: hp-bioscfg: Update steps order list elements are evaluated (jsc#PED-13019).\n- platform/x86: hp-bioscfg: Use kmemdup() to replace kmalloc + memcpy (jsc#PED-13019).\n- platform/x86: hp-bioscfg: biosattr-interface (jsc#PED-13019).\n- platform/x86: hp-bioscfg: bioscfg (jsc#PED-13019).\n- platform/x86: hp-bioscfg: bioscfg-h (jsc#PED-13019).\n- platform/x86: hp-bioscfg: enum-attributes (jsc#PED-13019).\n- platform/x86: hp-bioscfg: fix a signedness bug in hp_wmi_perform_query() (jsc#PED-13019).\n- platform/x86: hp-bioscfg: fix error reporting in hp_add_other_attributes() (jsc#PED-13019).\n- platform/x86: hp-bioscfg: int-attributes (jsc#PED-13019).\n- platform/x86: hp-bioscfg: move mutex_lock() down in hp_add_other_attributes() (jsc#PED-13019).\n- platform/x86: hp-bioscfg: order-list-attributes (jsc#PED-13019).\n- platform/x86: hp-bioscfg: passwdobj-attributes (jsc#PED-13019).\n- platform/x86: hp-bioscfg: prevent a small buffer overflow (jsc#PED-13019).\n- platform/x86: hp-bioscfg: spmobj-attributes (jsc#PED-13019).\n- platform/x86: hp-bioscfg: string-attributes (jsc#PED-13019).\n- platform/x86: hp-bioscfg: surestart-attributes (jsc#PED-13019).\n- platform/x86: ideapad-laptop: use usleep_range() for EC polling (git-fixes).\n- platform/x86: thinkpad_acpi: Ignore battery threshold change event notification (stable-fixes).\n- platform/x86: thinkpad_acpi: Support also NEC Lavie X1475JAS (git-fixes).\n- platform/x86: thinkpad_acpi: Support also NEC Lavie X1475JAS (stable-fixes).\n- power: reset: at91-reset: Optimize at91_reset() (git-fixes).\n- power: supply: bq27xxx: Retrieve again when busy (stable-fixes).\n- power: supply: collie: Fix wakeup source leaks on device unbind (stable-fixes).\n- powerpc/eeh: Fix missing PE bridge reconfiguration during VFIO EEH recovery (bsc#1215199).\n- powerpc/powernv/memtrace: Fix out of bounds issue in memtrace mmap (bsc#1244309 ltc#213790).\n- powerpc/pseries/msi: Avoid reading PCI device registers in reduced power states (bsc#1215199).\n- powerpc/vas: Return -EINVAL if the offset is non-zero in mmap() (bsc#1244309 ltc#213790).\n- pstore: Change kmsg_bytes storage size to u32 (git-fixes).\n- ptp: ocp: fix start time alignment in ptp_ocp_signal_set (git-fixes).\n- ptp: ocp: reject unsupported periodic output flags (git-fixes).\n- ptp: remove ptp-\u003en_vclocks check logic in ptp_vclock_in_use() (git-fixes).\n- r8152: add vendor/device ID pair for Dell Alienware AW1022z (git-fixes).\n- regulator: ad5398: Add device tree support (stable-fixes).\n- regulator: max14577: Add error check for max14577_read_reg() (git-fixes).\n- regulator: max20086: Change enable gpio to optional (git-fixes).\n- regulator: max20086: Fix MAX200086 chip id (git-fixes).\n- regulator: max20086: Fix refcount leak in max20086_parse_regulators_dt() (git-fixes).\n- rpm/check-for-config-changes: add more to IGNORED_CONFIGS_RE Useful when someone tries (needs) to build the kernel with clang.\n- rpm/kernel-source.changes.old: Drop bogus bugzilla reference (bsc#1244725)\n- rpm: Stop using is_kotd_qa macro This macro is set by bs-upload-kernel, and a conditional in each spec file is used to determine when to build the spec file. This logic should not really be in the spec file. Previously this was done with package links and package meta for the individula links. However, the use of package links is rejected for packages in git based release projects (nothing to do with git actually, new policy). An alternative to package links is multibuild. However, for multibuild packages package meta cannot be used to set which spec file gets built. Use prjcon buildflags instead, and remove this conditional. Depends on bs-upload-kernel adding the build flag.\n- rtc: Fix offset calculation for .start_secs \u0026lt; 0 (git-fixes).\n- rtc: Make rtc_time64_to_tm() support dates before 1970 (stable-fixes).\n- rtc: at91rm9200: drop unused module alias (git-fixes).\n- rtc: cmos: use spin_lock_irqsave in cmos_interrupt (git-fixes).\n- rtc: cpcap: drop unused module alias (git-fixes).\n- rtc: da9063: drop unused module alias (git-fixes).\n- rtc: ds1307: stop disabling alarms on probe (stable-fixes).\n- rtc: jz4740: drop unused module alias (git-fixes).\n- rtc: pm8xxx: drop unused module alias (git-fixes).\n- rtc: rv3032: fix EERD location (stable-fixes).\n- rtc: s3c: drop unused module alias (git-fixes).\n- rtc: sh: assign correct interrupts with DT (git-fixes).\n- rtc: stm32: drop unused module alias (git-fixes).\n- s390/pci: Allow re-add of a reserved but not yet removed device (bsc#1244145).\n- s390/pci: Fix __pcilg_mio_inuser() inline assembly (git-fixes bsc#1245226).\n- s390/pci: Fix duplicate pci_dev_put() in disable_slot() when PF has child VFs (git-fixes bsc#1244145).\n- s390/pci: Fix potential double remove of hotplug slot (bsc#1244145).\n- s390/pci: Prevent self deletion in disable_slot() (bsc#1244145).\n- s390/pci: Remove redundant bus removal and disable from zpci_release_device() (bsc#1244145).\n- s390/pci: Serialize device addition and removal (bsc#1244145).\n- s390/pci: introduce lock to synchronize state of zpci_dev's (jsc#PED-10253 bsc#1244145).\n- s390/pci: remove hotplug slot when releasing the device (bsc#1244145).\n- s390/pci: rename lock member in struct zpci_dev (jsc#PED-10253 bsc#1244145).\n- s390/tty: Fix a potential memory leak bug (git-fixes bsc#1245228).\n- scsi: Improve CDL control (git-fixes).\n- scsi: dc395x: Remove DEBUG conditional compilation (git-fixes).\n- scsi: dc395x: Remove leftover if statement in reselect() (git-fixes).\n- scsi: elx: efct: Fix memory leak in efct_hw_parse_filter() (git-fixes).\n- scsi: hisi_sas: Call I_T_nexus after soft reset for SATA disk (git-fixes).\n- scsi: hisi_sas: Fix I/O errors caused by hardware port ID changes (git-fixes).\n- scsi: iscsi: Fix incorrect error path labels for flashnode operations (git-fixes).\n- scsi: megaraid_sas: Block zero-length ATA VPD inquiry (git-fixes).\n- scsi: mpi3mr: Add level check to control event logging (git-fixes).\n- scsi: mpt3sas: Fix _ctl_get_mpt_mctp_passthru_adapter() to return IOC pointer (git-fixes).\n- scsi: mpt3sas: Send a diag reset if target reset fails (git-fixes).\n- scsi: pm80xx: Set phy_attached to zero when device is gone (git-fixes).\n- scsi: qedf: Use designated initializer for struct qed_fcoe_cb_ops (git-fixes).\n- scsi: sd_zbc: block: Respect bio vector limits for REPORT ZONES buffer (git-fixes).\n- scsi: smartpqi: Fix smp_processor_id() call trace for preemptible kernels (git-fixes).\n- scsi: st: ERASE does not change tape location (git-fixes).\n- scsi: st: Restore some drive settings after reset (git-fixes).\n- scsi: st: Tighten the page format heuristics with MODE SELECT (git-fixes).\n- scsi: storvsc: Do not report the host packet status as the hv status (git-fixes).\n- scsi: storvsc: Increase the timeouts to storvsc_timeout (git-fixes).\n- selftests/bpf: Fix bpf_nf selftest failure (git-fixes).\n- selftests/mm: restore default nr_hugepages value during cleanup in hugetlb_reparenting_test.sh (git-fixes).\n- selftests/net: have `gro.sh -t` return a correct exit code (stable-fixes).\n- selftests/seccomp: fix syscall_restart test for arm compat (git-fixes).\n- serial: Fix potential null-ptr-deref in mlb_usio_probe() (git-fixes).\n- serial: core: restore of_node information in sysfs (git-fixes).\n- serial: imx: Restore original RXTL for console to fix data loss (git-fixes).\n- serial: jsm: fix NPE during jsm_uart_port_init (git-fixes).\n- serial: mctrl_gpio: split disable_ms into sync and no_sync APIs (git-fixes).\n- serial: sh-sci: Move runtime PM enable to sci_probe_single() (stable-fixes).\n- serial: sh-sci: Save and restore more registers (git-fixes).\n- serial: sh-sci: Update the suspend/resume support (stable-fixes).\n- smb3: fix Open files on server counter going negative (git-fixes).\n- smb: client: Use str_yes_no() helper function (git-fixes).\n- smb: client: allow more DFS referrals to be cached (git-fixes).\n- smb: client: avoid unnecessary reconnects when refreshing referrals (git-fixes).\n- smb: client: change return value in open_cached_dir_by_dentry() if !cfids (git-fixes).\n- smb: client: do not retry DFS targets on server shutdown (git-fixes).\n- smb: client: do not trust DFSREF_STORAGE_SERVER bit (git-fixes).\n- smb: client: do not try following DFS links in cifs_tree_connect() (git-fixes).\n- smb: client: fix DFS interlink failover (git-fixes).\n- smb: client: fix DFS mount against old servers with NTLMSSP (git-fixes).\n- smb: client: fix hang in wait_for_response() for negproto (bsc#1242709).\n- smb: client: fix potential race in cifs_put_tcon() (git-fixes).\n- smb: client: fix return value of parse_dfs_referrals() (git-fixes).\n- smb: client: get rid of @nlsc param in cifs_tree_connect() (git-fixes).\n- smb: client: get rid of TCP_Server_Info::refpath_lock (git-fixes).\n- smb: client: get rid of kstrdup() in get_ses_refpath() (git-fixes).\n- smb: client: improve purging of cached referrals (git-fixes).\n- smb: client: introduce av_for_each_entry() helper (git-fixes).\n- smb: client: optimize referral walk on failed link targets (git-fixes).\n- smb: client: parse DNS domain name from domain= option (git-fixes).\n- smb: client: parse av pair type 4 in CHALLENGE_MESSAGE (git-fixes).\n- smb: client: provide dns_resolve_{unc,name} helpers (git-fixes).\n- smb: client: refresh referral without acquiring refpath_lock (git-fixes).\n- smb: client: remove unnecessary checks in open_cached_dir() (git-fixes).\n- soc: aspeed: Add NULL check in aspeed_lpc_enable_snoop() (git-fixes).\n- soc: aspeed: lpc: Fix impossible judgment condition (git-fixes).\n- soc: qcom: smp2p: Fix fallback to qcom,ipc parse (git-fixes).\n- soc: ti: k3-socinfo: Do not use syscon helper to build regmap (stable-fixes).\n- software node: Correct a OOB check in software_node_get_reference_args() (stable-fixes).\n- soundwire: amd: change the soundwire wake enable/disable sequence (stable-fixes).\n- spi-rockchip: Fix register out of bounds access (stable-fixes).\n- spi: bcm63xx-hsspi: fix shared reset (git-fixes).\n- spi: bcm63xx-spi: fix shared reset (git-fixes).\n- spi: sh-msiof: Fix maximum DMA transfer size (git-fixes).\n- spi: spi-sun4i: fix early activation (stable-fixes).\n- spi: tegra210-quad: Fix X1_X2_X4 encoding and support x4 transfers (git-fixes).\n- spi: tegra210-quad: modify chip select (CS) deactivation (git-fixes).\n- spi: tegra210-quad: remove redundant error handling code (git-fixes).\n- spi: zynqmp-gqspi: Always acknowledge interrupts (stable-fixes).\n- staging: iio: ad5933: Correct settling cycles encoding per datasheet (git-fixes).\n- staging: rtl8723bs: Avoid memset() in aes_cipher() and aes_decipher() (git-fixes).\n- struct usci: hide additional member (git-fixes).\n- sunrpc: handle SVC_GARBAGE during svc auth processing as auth error (git-fixes).\n- supported.conf: Add SNP SVSM vTPM driver\n- supported.conf: add it\n- supported.conf: support firmware_attributes_class\n- svsm: Add header with SVSM_VTPM_CMD helpers (bsc#1241191).\n- sysfb: Fix screen_info type check for VGA (git-fixes).\n- tcp/dccp: allow a connection when sk_max_ack_backlog is zero (git-fixes).\n- tcp/dccp: bypass empty buckets in inet_twsk_purge() (git-fixes).\n- tcp/dccp: complete lockless accesses to sk-\u003esk_max_ack_backlog (git-fixes).\n- tcp: bring back NUMA dispersion in inet_ehash_locks_alloc() (git-fixes).\n- tcp_metrics: optimize tcp_metrics_flush_all() (git-fixes).\n- thermal/drivers/mediatek/lvts: Fix debugfs unregister on failure (git-fixes).\n- thermal/drivers/qoriq: Power down TMU on system suspend (stable-fixes).\n- thunderbolt: Do not add non-active NVM if NVM upgrade is disabled for retimer (stable-fixes).\n- thunderbolt: Do not double dequeue a configuration request (stable-fixes).\n- thunderbolt: Fix a logic error in wake on connect (git-fixes).\n- thunderbolt: Improve redrive mode handling (git-fixes).\n- timekeeping: Fix bogus clock_was_set() invocation in (git-fixes)\n- timekeeping: Fix cross-timestamp interpolation corner case (git-fixes)\n- timekeeping: Fix cross-timestamp interpolation for non-x86 (git-fixes)\n- timekeeping: Fix cross-timestamp interpolation on counter (git-fixes)\n- tpm: Add SNP SVSM vTPM driver (bsc#1241191).\n- tpm: Make chip-\u003e{status,cancel,req_canceled} opt (bsc#1241191).\n- trace/trace_event_perf: remove duplicate samples on the first tracepoint event (git-fixes).\n- tracing/eprobe: Fix to release eprobe when failed to add dyn_event (git-fixes).\n- tracing: Add __print_dynamic_array() helper (bsc#1243544).\n- tracing: Add __string_len() example (bsc#1243544).\n- tracing: Fix cmp_entries_dup() to respect sort() comparison rules (git-fixes).\n- tracing: Fix compilation warning on arm32 (bsc#1243551).\n- tracing: Use atomic64_inc_return() in trace_clock_counter() (git-fixes).\n- truct dwc3 hide new member wakeup_pending_funcs (git-fixes).\n- tty: serial: 8250_omap: fix TX with DMA for am33xx (git-fixes).\n- ucsi_debugfs_entry: hide signedness change (git-fixes).\n- udp: annotate data-races around up-\u003epending (git-fixes).\n- udp: fix incorrect parameter validation in the udp_lib_getsockopt() function (git-fixes).\n- udp: fix receiving fraglist GSO packets (git-fixes).\n- udp: preserve the connected status if only UDP cmsg (git-fixes).\n- uprobes: Use kzalloc to allocate xol area (git-fixes).\n- usb: Flush altsetting 0 endpoints before reinitializating them after reset (git-fixes).\n- usb: cdnsp: Fix issue with detecting USB 3.2 speed (git-fixes).\n- usb: cdnsp: Fix issue with detecting command completion event (git-fixes).\n- usb: dwc3: gadget: Make gadget_wakeup asynchronous (git-fixes).\n- usb: misc: onboard_usb_dev: fix support for Cypress HX3 hubs (git-fixes).\n- usb: quirks: Add NO_LPM quirk for SanDisk Extreme 55AE (stable-fixes).\n- usb: renesas_usbhs: Reorder clock handling and power management in probe (git-fixes).\n- usb: storage: Ignore UAS driver for SanDisk 3.2 Gen2 storage device (stable-fixes).\n- usb: typec: tcpm/tcpci_maxim: Fix bounds check in process_rx() (git-fixes).\n- usb: typec: tcpm: move tcpm_queue_vdm_unlocked to asynchronous work (git-fixes).\n- usb: typec: ucsi: Only enable supported notifications (git-fixes).\n- usb: typec: ucsi: allow non-partner GET_PDOS for Qualcomm devices (git-fixes).\n- usb: typec: ucsi: fix Clang -Wsign-conversion warning (git-fixes).\n- usb: typec: ucsi: fix UCSI on buggy Qualcomm devices (git-fixes).\n- usb: typec: ucsi: limit the UCSI_NO_PARTNER_PDOS even further (git-fixes).\n- usb: usbtmc: Fix read_stb function and get_stb ioctl (git-fixes).\n- usb: usbtmc: Fix timeout value in get_stb (git-fixes).\n- usb: xhci: Do not change the status of stalled TDs on failed Stop EP (stable-fixes).\n- usbnet: asix AX88772: leave the carrier control to phylink (stable-fixes).\n- vgacon: Add check for vc_origin address range in vgacon_scroll() (git-fixes).\n- vmxnet3: correctly report gso type for UDP tunnels (bsc#1244626).\n- vmxnet3: support higher link speeds from vmxnet3 v9 (bsc#1244626).\n- vmxnet3: update MTU after device quiesce (bsc#1244626).\n- vt: remove VT_RESIZE and VT_RESIZEX from vt_compat_ioctl() (git-fixes).\n- watchdog: da9052_wdt: respect TWDMIN (stable-fixes).\n- watchdog: exar: Shorten identity name to fit correctly (git-fixes).\n- watchdog: fix watchdog may detect false positive of softlockup (stable-fixes).\n- watchdog: it87_wdt: add PWRGD enable quirk for Qotom QCML04 (git-fixes).\n- watchdog: mediatek: Add support for MT6735 TOPRGU/WDT (git-fixes).\n- wifi: ath11k: Fix QMI memory reuse logic (stable-fixes).\n- wifi: ath11k: avoid burning CPU in ath11k_debugfs_fw_stats_request() (git-fixes).\n- wifi: ath11k: convert timeouts to secs_to_jiffies() (stable-fixes).\n- wifi: ath11k: do not use static variables in ath11k_debugfs_fw_stats_process() (git-fixes).\n- wifi: ath11k: do not wait when there is no vdev started (git-fixes).\n- wifi: ath11k: fix node corruption in ar-\u003earvifs list (git-fixes).\n- wifi: ath11k: fix ring-buffer corruption (git-fixes).\n- wifi: ath11k: fix rx completion meta data corruption (git-fixes).\n- wifi: ath11k: fix soc_dp_stats debugfs file permission (stable-fixes).\n- wifi: ath11k: move some firmware stats related functions outside of debugfs (git-fixes).\n- wifi: ath11k: update channel list in worker when wait flag is set (bsc#1243847).\n- wifi: ath11k: validate ath11k_crypto_mode on top of ath11k_core_qmi_firmware_ready (git-fixes).\n- wifi: ath12k: ACPI CCA threshold support (bsc#1240998).\n- wifi: ath12k: ACPI SAR support (bsc#1240998).\n- wifi: ath12k: ACPI TAS support (bsc#1240998).\n- wifi: ath12k: ACPI band edge channel power support (bsc#1240998).\n- wifi: ath12k: Add MSDU length validation for TKIP MIC error (git-fixes).\n- wifi: ath12k: Add additional checks for vif and sta iterators (bsc#1240998).\n- wifi: ath12k: Add firmware coredump collection support (bsc#1240998).\n- wifi: ath12k: Add htt_stats_dump file ops support (bsc#1240998).\n- wifi: ath12k: Add lock to protect the hardware state (bsc#1240998).\n- wifi: ath12k: Add missing htt_metadata flag in ath12k_dp_tx() (bsc#1240998).\n- wifi: ath12k: Add support to enable debugfs_htt_stats (bsc#1240998).\n- wifi: ath12k: Add support to parse requested stats_type (bsc#1240998).\n- wifi: ath12k: Avoid -Wflex-array-member-not-at-end warnings (bsc#1240998).\n- wifi: ath12k: Avoid napi_sync() before napi_enable() (stable-fixes).\n- wifi: ath12k: Cache vdev configs before vdev create (bsc#1240998).\n- wifi: ath12k: Dump additional Tx PDEV HTT stats (bsc#1240998).\n- wifi: ath12k: Fetch regdb.bin file from board-2.bin (stable-fixes).\n- wifi: ath12k: Fix WARN_ON during firmware crash in split-phy (bsc#1240998).\n- wifi: ath12k: Fix WMI tag for EHT rate in peer assoc (git-fixes).\n- wifi: ath12k: Fix buffer overflow in debugfs (bsc#1240998).\n- wifi: ath12k: Fix devmem address prefix when logging (bsc#1240998).\n- wifi: ath12k: Fix end offset bit definition in monitor ring descriptor (stable-fixes).\n- wifi: ath12k: Fix for out-of bound access error (bsc#1240998).\n- wifi: ath12k: Fix invalid memory access while forming 802.11 header (git-fixes).\n- wifi: ath12k: Fix memory leak during vdev_id mismatch (git-fixes).\n- wifi: ath12k: Fix pdev id sent to firmware for single phy devices (bsc#1240998).\n- wifi: ath12k: Fix the QoS control field offset to build QoS header (git-fixes).\n- wifi: ath12k: Handle error cases during extended skb allocation (git-fixes).\n- wifi: ath12k: Improve BSS discovery with hidden SSID in 6 GHz band (stable-fixes).\n- wifi: ath12k: Introduce device index (bsc#1240998).\n- wifi: ath12k: Modify add and remove chanctx ops for single wiphy support (bsc#1240998).\n- wifi: ath12k: Modify print_array_to_buf() to support arrays with 1-based semantics (bsc#1240998).\n- wifi: ath12k: Modify rts threshold mac op for single wiphy (bsc#1240998).\n- wifi: ath12k: Modify set and get antenna mac ops for single wiphy (bsc#1240998).\n- wifi: ath12k: Optimize the lock contention of used list in Rx data path (bsc#1240998).\n- wifi: ath12k: Pass correct values of center freq1 and center freq2 for 160 MHz (stable-fixes).\n- wifi: ath12k: Prevent sending WMI commands to firmware during firmware crash (bsc#1240998).\n- wifi: ath12k: Refactor Rxdma buffer replinish argument (bsc#1240998).\n- wifi: ath12k: Refactor data path cmem init (bsc#1240998).\n- wifi: ath12k: Refactor error handler of Rxdma replenish (bsc#1240998).\n- wifi: ath12k: Refactor idle ring descriptor setup (bsc#1240998).\n- wifi: ath12k: Refactor the hardware cookie conversion init (bsc#1240998).\n- wifi: ath12k: Refactor the hardware recovery procedure (bsc#1240998).\n- wifi: ath12k: Refactor the hardware state (bsc#1240998).\n- wifi: ath12k: Remove unsupported tx monitor handling (bsc#1240998).\n- wifi: ath12k: Remove unused ath12k_base from ath12k_hw (bsc#1240998).\n- wifi: ath12k: Remove unused tcl_*_ring configuration (bsc#1240998).\n- wifi: ath12k: Replace 'chip' with 'device' in hal Rx return buffer manager (bsc#1240998).\n- wifi: ath12k: Report proper tx completion status to mac80211 (stable-fixes).\n- wifi: ath12k: Resolve multicast packet drop by populating key_cipher in ath12k_install_key() (bsc#1240998).\n- wifi: ath12k: Support BE OFDMA Pdev Rate Stats (bsc#1240998).\n- wifi: ath12k: Support DMAC Reset Stats (bsc#1240998).\n- wifi: ath12k: Support Pdev OBSS Stats (bsc#1240998).\n- wifi: ath12k: Support Pdev Scheduled Algorithm Stats (bsc#1240998).\n- wifi: ath12k: Support Ring and SFM stats (bsc#1240998).\n- wifi: ath12k: Support Self-Generated Transmit stats (bsc#1240998).\n- wifi: ath12k: Support TQM stats (bsc#1240998).\n- wifi: ath12k: Support Transmit DE stats (bsc#1240998).\n- wifi: ath12k: Support Transmit Scheduler stats (bsc#1240998).\n- wifi: ath12k: Support pdev CCA Stats (bsc#1240998).\n- wifi: ath12k: Support pdev Transmit Multi-user stats (bsc#1240998).\n- wifi: ath12k: Support pdev error stats (bsc#1240998).\n- wifi: ath12k: add 6 GHz params in peer assoc command (bsc#1240998).\n- wifi: ath12k: add ATH12K_DBG_WOW log level (bsc#1240998).\n- wifi: ath12k: add EMA beacon support (bsc#1240998).\n- wifi: ath12k: add MBSSID beacon support (bsc#1240998).\n- wifi: ath12k: add WoW net-detect functionality (bsc#1240998).\n- wifi: ath12k: add basic WoW functionalities (bsc#1240998).\n- wifi: ath12k: add channel 2 into 6 GHz channel list (bsc#1240998).\n- wifi: ath12k: add hw_link_id in ath12k_pdev (bsc#1240998).\n- wifi: ath12k: add missing lockdep_assert_wiphy() for ath12k_mac_op_ functions (bsc#1240998).\n- wifi: ath12k: add multi device support for WBM idle ring buffer setup (bsc#1240998).\n- wifi: ath12k: add multiple radio support in a single MAC HW un/register (bsc#1240998).\n- wifi: ath12k: add panic handler (bsc#1240998).\n- wifi: ath12k: add support to handle beacon miss for WCN7850 (bsc#1240998).\n- wifi: ath12k: advertise driver capabilities for MBSSID and EMA (bsc#1240998).\n- wifi: ath12k: allocate dummy net_device dynamically (bsc#1240998).\n- wifi: ath12k: ath12k_mac_op_set_key(): fix uninitialized symbol 'ret' (bsc#1240998).\n- wifi: ath12k: ath12k_mac_op_sta_state(): clean up update_wk cancellation (bsc#1240998).\n- wifi: ath12k: ath12k_mac_set_key(): remove exit label (bsc#1240998).\n- wifi: ath12k: avoid double SW2HW_MACID conversion (bsc#1240998).\n- wifi: ath12k: avoid duplicated vdev down (bsc#1240998).\n- wifi: ath12k: avoid redundant code in Rx cookie conversion init (bsc#1240998).\n- wifi: ath12k: avoid stopping mac80211 queues in ath12k_core_restart() (bsc#1240998).\n- wifi: ath12k: avoid unnecessary MSDU drop in the Rx error process (bsc#1240998).\n- wifi: ath12k: change supports_suspend to true for WCN7850 (bsc#1240998).\n- wifi: ath12k: cleanup unneeded labels (bsc#1240998).\n- wifi: ath12k: configure MBSSID parameters in AP mode (bsc#1240998).\n- wifi: ath12k: configure MBSSID params in vdev create/start (bsc#1240998).\n- wifi: ath12k: convert struct ath12k_sta::update_wk to use struct wiphy_work (bsc#1240998).\n- wifi: ath12k: correct the capital word typo (bsc#1240998).\n- wifi: ath12k: create a structure for WMI vdev up parameters (bsc#1240998).\n- wifi: ath12k: debugfs: radar simulation support (bsc#1240998).\n- wifi: ath12k: decrease MHI channel buffer length to 8KB (bsc#1240998).\n- wifi: ath12k: delete NSS and TX power setting for monitor vdev (bsc#1240998).\n- wifi: ath12k: displace the Tx and Rx descriptor in cookie conversion table (bsc#1240998).\n- wifi: ath12k: do not dump SRNG statistics during resume (bsc#1240998).\n- wifi: ath12k: do not process consecutive RDDM event (bsc#1240998).\n- wifi: ath12k: do not use %pK in dmesg format strings (bsc#1240998).\n- wifi: ath12k: dynamic VLAN support (bsc#1240998).\n- wifi: ath12k: dynamically update peer puncturing bitmap for STA (bsc#1240998).\n- wifi: ath12k: enable WIPHY_FLAG_DISABLE_WEXT (bsc#1240998).\n- wifi: ath12k: enable service flag for survey dump stats (bsc#1240998).\n- wifi: ath12k: extend the link capable flag (bsc#1240998).\n- wifi: ath12k: fetch correct radio based on vdev status (bsc#1240998).\n- wifi: ath12k: fix A-MSDU indication in monitor mode (bsc#1240998).\n- wifi: ath12k: fix ACPI warning when resume (bsc#1240998).\n- wifi: ath12k: fix GCC_GCC_PCIE_HOT_RST definition for WCN7850 (git-fixes).\n- wifi: ath12k: fix NULL pointer access in ath12k_mac_op_get_survey() (bsc#1240998).\n- wifi: ath12k: fix Smatch warnings on ath12k_core_suspend() (bsc#1240998).\n- wifi: ath12k: fix a possible dead lock caused by ab-\u003ebase_lock (stable-fixes).\n- wifi: ath12k: fix ack signal strength calculation (bsc#1240998).\n- wifi: ath12k: fix ath12k_hal_tx_cmd_ext_desc_setup() info1 override (stable-fixes).\n- wifi: ath12k: fix build vs old compiler (bsc#1240998).\n- wifi: ath12k: fix calling correct function for rx monitor mode (bsc#1240998).\n- wifi: ath12k: fix cleanup path after mhi init (git-fixes).\n- wifi: ath12k: fix desc address calculation in wbm tx completion (bsc#1240998).\n- wifi: ath12k: fix driver initialization for WoW unsupported devices (bsc#1240998).\n- wifi: ath12k: fix failed to set mhi state error during reboot with hardware grouping (stable-fixes).\n- wifi: ath12k: fix flush failure in recovery scenarios (bsc#1240998).\n- wifi: ath12k: fix hal_rx_buf_return_buf_manager documentation (bsc#1240998).\n- wifi: ath12k: fix incorrect CE addresses (stable-fixes).\n- wifi: ath12k: fix invalid access to memory (git-fixes).\n- wifi: ath12k: fix key cache handling (bsc#1240998).\n- wifi: ath12k: fix legacy peer association due to missing HT or 6 GHz capabilities (bsc#1240998).\n- wifi: ath12k: fix link capable flags (bsc#1240998).\n- wifi: ath12k: fix link valid field initialization in the monitor Rx (stable-fixes).\n- wifi: ath12k: fix mac id extraction when MSDU spillover in rx error path (bsc#1240998).\n- wifi: ath12k: fix macro definition HAL_RX_MSDU_PKT_LENGTH_GET (stable-fixes).\n- wifi: ath12k: fix mbssid max interface advertisement (bsc#1240998).\n- wifi: ath12k: fix missing endianness conversion in wmi_vdev_create_cmd() (bsc#1240998).\n- wifi: ath12k: fix misspelling of 'dma' in num_rxmda_per_pdev (bsc#1240998).\n- wifi: ath12k: fix node corruption in ar-\u003earvifs list (git-fixes).\n- wifi: ath12k: fix one more memcpy size error (bsc#1240998).\n- wifi: ath12k: fix per pdev debugfs registration (bsc#1240998).\n- wifi: ath12k: fix reusing outside iterator in ath12k_wow_vif_set_wakeups() (bsc#1240998).\n- wifi: ath12k: fix ring-buffer corruption (git-fixes).\n- wifi: ath12k: fix skb_ext_desc leak in ath12k_dp_tx() error path (bsc#1240998).\n- wifi: ath12k: fix struct hal_rx_mpdu_start (bsc#1240998).\n- wifi: ath12k: fix struct hal_rx_phyrx_rssi_legacy_info (bsc#1240998).\n- wifi: ath12k: fix struct hal_rx_ppdu_end_user_stats (bsc#1240998).\n- wifi: ath12k: fix struct hal_rx_ppdu_start (bsc#1240998).\n- wifi: ath12k: fix survey dump collection in 6 GHz (bsc#1240998).\n- wifi: ath12k: fix the ampdu id fetch in the HAL_RX_MPDU_START TLV (stable-fixes).\n- wifi: ath12k: fix the stack frame size warning in ath12k_mac_op_hw_scan (bsc#1240998).\n- wifi: ath12k: fix use-after-free in ath12k_dp_cc_cleanup() (bsc#1240998).\n- wifi: ath12k: fix warning on DMA ring capabilities event (bsc#1240998).\n- wifi: ath12k: flush all packets before suspend (bsc#1240998).\n- wifi: ath12k: handle keepalive during WoWLAN suspend and resume (bsc#1240998).\n- wifi: ath12k: handle symlink cleanup for per pdev debugfs dentry (bsc#1240998).\n- wifi: ath12k: implement WoW enable and wakeup commands (bsc#1240998).\n- wifi: ath12k: implement hardware data filter (bsc#1240998).\n- wifi: ath12k: improve the rx descriptor error information (bsc#1240998).\n- wifi: ath12k: initial debugfs support (bsc#1240998).\n- wifi: ath12k: make read-only array svc_id static const (bsc#1240998).\n- wifi: ath12k: modify ath12k mac start/stop ops for single wiphy (bsc#1240998).\n- wifi: ath12k: modify ath12k_get_arvif_iter() for MLO (bsc#1240998).\n- wifi: ath12k: modify ath12k_mac_op_bss_info_changed() for MLO (bsc#1240998).\n- wifi: ath12k: modify ath12k_mac_op_set_key() for MLO (bsc#1240998).\n- wifi: ath12k: modify ath12k_mac_vif_chan() for MLO (bsc#1240998).\n- wifi: ath12k: modify link arvif creation and removal for MLO (bsc#1240998).\n- wifi: ath12k: modify regulatory support for single wiphy architecture (bsc#1240998).\n- wifi: ath12k: modify remain on channel for single wiphy (bsc#1240998).\n- wifi: ath12k: move txbaddr/rxbaddr into struct ath12k_dp (bsc#1240998).\n- wifi: ath12k: no need to handle pktlog during suspend/resume (bsc#1240998).\n- wifi: ath12k: pass ath12k_link_vif instead of vif/ahvif (bsc#1240998).\n- wifi: ath12k: prepare sta data structure for MLO handling (bsc#1240998).\n- wifi: ath12k: prepare vif config caching for MLO (bsc#1240998).\n- wifi: ath12k: prepare vif data structure for MLO handling (bsc#1240998).\n- wifi: ath12k: read single_chip_mlo_support parameter from QMI PHY capability (bsc#1240998).\n- wifi: ath12k: rearrange IRQ enable/disable in reset path (bsc#1240998).\n- wifi: ath12k: refactor SMPS configuration (bsc#1240998).\n- wifi: ath12k: refactor arvif security parameter configuration (bsc#1240998).\n- wifi: ath12k: refactor ath12k_hw_regs structure (stable-fixes).\n- wifi: ath12k: refactor rx descriptor CMEM configuration (bsc#1240998).\n- wifi: ath12k: remove MHI LOOPBACK channels (bsc#1240998).\n- wifi: ath12k: remove duplicate definition of MAX_RADIOS (bsc#1240998).\n- wifi: ath12k: remove duplicate definitions in wmi.h (bsc#1240998).\n- wifi: ath12k: remove invalid peer create logic (bsc#1240998).\n- wifi: ath12k: remove obsolete struct wmi_start_scan_arg (bsc#1240998).\n- wifi: ath12k: remove redundant peer delete for WCN7850 (bsc#1240998).\n- wifi: ath12k: remove unused variable monitor_flags (bsc#1240998).\n- wifi: ath12k: remove unused variable monitor_present (bsc#1240998).\n- wifi: ath12k: rename MBSSID fields in wmi_vdev_up_cmd (bsc#1240998).\n- wifi: ath12k: restore ASPM for supported hardwares only (bsc#1240998).\n- wifi: ath12k: scan statemachine changes for single wiphy (bsc#1240998).\n- wifi: ath12k: set mlo_capable_flags based on QMI PHY capability (bsc#1240998).\n- wifi: ath12k: skip sending vdev down for channel switch (bsc#1240998).\n- wifi: ath12k: support ARP and NS offload (bsc#1240998).\n- wifi: ath12k: support GTK rekey offload (bsc#1240998).\n- wifi: ath12k: support SMPS configuration for 6 GHz (bsc#1240998).\n- wifi: ath12k: support get_survey mac op for single wiphy (bsc#1240998).\n- wifi: ath12k: support suspend/resume (bsc#1240998).\n- wifi: ath12k: switch to using wiphy_lock() and remove ar-\u003econf_mutex (bsc#1240998).\n- wifi: ath12k: unregister per pdev debugfs (bsc#1240998).\n- wifi: ath12k: update ath12k_mac_op_conf_tx() for MLO (bsc#1240998).\n- wifi: ath12k: update ath12k_mac_op_update_vif_offload() for MLO (bsc#1240998).\n- wifi: ath12k: use 128 bytes aligned iova in transmit path for WCN7850 (bsc#1240998).\n- wifi: ath12k: use correct MAX_RADIOS (bsc#1240998).\n- wifi: ath12k: use tail MSDU to get MSDU information (bsc#1240998).\n- wifi: ath12k: using msdu end descriptor to check for rx multicast packets (stable-fixes).\n- wifi: ath12k: vdev statemachine changes for single wiphy (bsc#1240998).\n- wifi: ath9k: return by of_get_mac_address (stable-fixes).\n- wifi: ath9k_htc: Abort software beacon handling if disabled (git-fixes).\n- wifi: carl9170: do not ping device which has failed to load firmware (git-fixes).\n- wifi: cfg80211: allow IR in 20 MHz configurations (stable-fixes).\n- wifi: iwlfiwi: mvm: Fix the rate reporting (git-fixes).\n- wifi: iwlwifi: Add missing MODULE_FIRMWARE for Qu-c0-jf-b0 (stable-fixes).\n- wifi: iwlwifi: add support for Killer on MTL (stable-fixes).\n- wifi: iwlwifi: do not warn during reprobe (stable-fixes).\n- wifi: iwlwifi: do not warn when if there is a FW error (stable-fixes).\n- wifi: iwlwifi: fix debug actions order (stable-fixes).\n- wifi: iwlwifi: fix the ECKV UEFI variable name (stable-fixes).\n- wifi: iwlwifi: mark Br device not integrated (stable-fixes).\n- wifi: iwlwifi: mvm: fix beacon CCK flag (stable-fixes).\n- wifi: iwlwifi: mvm: fix setting the TK when associated (stable-fixes).\n- wifi: iwlwifi: pcie: make sure to lock rxq-\u003eread (stable-fixes).\n- wifi: iwlwifi: use correct IMR dump variable (stable-fixes).\n- wifi: iwlwifi: w/a FW SMPS mode selection (stable-fixes).\n- wifi: mac80211: VLAN traffic in multicast path (stable-fixes).\n- wifi: mac80211: do not offer a mesh path if forwarding is disabled (stable-fixes).\n- wifi: mac80211: do not unconditionally call drv_mgd_complete_tx() (stable-fixes).\n- wifi: mac80211: fix beacon interval calculation overflow (git-fixes).\n- wifi: mac80211: fix warning on disconnect during failed ML reconf (stable-fixes).\n- wifi: mac80211: remove misplaced drv_mgd_complete_tx() call (stable-fixes).\n- wifi: mac80211: set ieee80211_prep_tx_info::link_id upon Auth Rx (stable-fixes).\n- wifi: mac80211: validate SCAN_FLAG_AP in scan request during MLO (stable-fixes).\n- wifi: mac80211_hwsim: Fix MLD address translation (stable-fixes).\n- wifi: mac80211_hwsim: Prevent tsf from setting if beacon is disabled (stable-fixes).\n- wifi: mt76: mt76x2: Add support for LiteOn WN4516R,WN4519R (stable-fixes).\n- wifi: mt76: mt7915: Fix null-ptr-deref in mt7915_mmio_wed_init() (git-fixes).\n- wifi: mt76: mt7921: add 160 MHz AP for mt7922 device (stable-fixes).\n- wifi: mt76: mt7925: ensure all MCU commands wait for response (git-fixes).\n- wifi: mt76: mt7925: fix fails to enter low power mode in suspend state (stable-fixes).\n- wifi: mt76: mt7925: fix host interrupt register initialization (git-fixes).\n- wifi: mt76: mt7925: introduce thermal protection (stable-fixes).\n- wifi: mt76: mt7925: load the appropriate CLC data based on hardware type (stable-fixes).\n- wifi: mt76: mt7925: prevent multiple scan commands (git-fixes).\n- wifi: mt76: mt7925: refine the sniffer commnad (git-fixes).\n- wifi: mt76: mt7996: drop fragments with multicast or broadcast RA (stable-fixes).\n- wifi: mt76: mt7996: fix RX buffer size of MCU event (git-fixes).\n- wifi: mt76: mt7996: revise TXS size (stable-fixes).\n- wifi: mt76: mt7996: set EHT max ampdu length capability (git-fixes).\n- wifi: mt76: only mark tx-status-failed frames as ACKed on mt76x0/2 (stable-fixes).\n- wifi: mwifiex: Fix HT40 bandwidth issue (stable-fixes).\n- wifi: p54: prevent buffer-overflow in p54_rx_eeprom_readback() (git-fixes).\n- wifi: rtlwifi: disable ASPM for RTL8723BE with subsystem ID 11ad:1723 (git-fixes).\n- wifi: rtw88: Do not use static local variable in rtw8822b_set_tx_power_index_by_rate (stable-fixes).\n- wifi: rtw88: Fix __rtw_download_firmware() for RTL8814AU (stable-fixes).\n- wifi: rtw88: Fix download_firmware_validate() for RTL8814AU (stable-fixes).\n- wifi: rtw88: Fix rtw_desc_to_mcsrate() to handle MCS16-31 (stable-fixes).\n- wifi: rtw88: Fix rtw_init_ht_cap() for RTL8814AU (stable-fixes).\n- wifi: rtw88: Fix rtw_init_vht_cap() for RTL8814AU (stable-fixes).\n- wifi: rtw88: do not ignore hardware read error during DPK (git-fixes).\n- wifi: rtw88: fix the 'para' buffer size to avoid reading out of bounds (git-fixes).\n- wifi: rtw88: sdio: call rtw_sdio_indicate_tx_status unconditionally (git-fixes).\n- wifi: rtw88: sdio: map mgmt frames to queue TX_DESC_QSEL_MGMT (git-fixes).\n- wifi: rtw88: usb: Reduce control message timeout to 500 ms (git-fixes).\n- wifi: rtw89: 8922a: fix TX fail with wrong VCO setting (stable-fixes).\n- wifi: rtw89: 8922a: fix incorrect STA-ID in EHT MU PPDU (stable-fixes).\n- wifi: rtw89: add wiphy_lock() to work that isn't held wiphy_lock() yet (stable-fixes).\n- wifi: rtw89: call power_on ahead before selecting firmware (stable-fixes).\n- wifi: rtw89: fw: get sb_sel_ver via get_unaligned_le32() (stable-fixes).\n- wifi: rtw89: fw: propagate error code from rtw89_h2c_tx() (stable-fixes).\n- wifi: rtw89: leave idle mode when setting WEP encryption for AP mode (stable-fixes).\n- wifi: rtw89: pci: enlarge retry times of RX tag to 1000 (git-fixes).\n- wifi: rtw89: phy: add dummy C2H event handler for report of TAS power (stable-fixes).\n- wireless: purelifi: plfxlc: fix memory leak in plfxlc_usb_wreq_asyn() (stable-fixes).\n- workqueue: Initialize wq_isolated_cpumask in workqueue_init_early() (bsc#1245101 jsc#PED-11934).\n- x86/acpi: Fix LAPIC/x2APIC parsing order (git-fixes).\n- x86/amd_nb, hwmon: (k10temp): Simplify amd_pci_dev_to_node_id() (jsc#PED-13094).\n- x86/amd_nb: Clean up early_is_amd_nb() (jsc#PED-13094).\n- x86/amd_nb: Move SMN access code to a new amd_node driver (jsc#PED-13094).\n- x86/amd_nb: Restrict init function to AMD-based systems (jsc#PED-13094).\n- x86/amd_nb: Simplify function 4 search (jsc#PED-13094).\n- x86/amd_nb: Simplify root device search (jsc#PED-13094).\n- x86/amd_node: Add SMN offsets to exclusive region access (jsc#PED-13094).\n- x86/amd_node: Add support for debugfs access to SMN registers (jsc#PED-13094).\n- x86/amd_node: Remove dependency on AMD_NB (jsc#PED-13094).\n- x86/amd_node: Update __amd_smn_rw() error paths (jsc#PED-13094).\n- x86/amd_node: Use defines for SMN register offsets (jsc#PED-13094).\n- x86/fred/signal: Prevent immediate repeat of single step trap on return from SIGTRAP handler (git-fixes).\n- x86/idle: Remove MFENCEs for X86_BUG_CLFLUSH_MONITOR in mwait_idle_with_hints() and prefer_mwait_c1_over_halt() (git-fixes).\n- x86/kaslr: Reduce KASLR entropy on most x86 systems (git-fixes).\n- x86/mce/amd: Remove shared threshold bank plumbing (jsc#PED-13094).\n- x86/microcode/AMD: Add get_patch_level() (git-fixes).\n- x86/microcode/AMD: Do not return error when microcode update is not necessary (git-fixes).\n- x86/microcode/AMD: Get rid of the _load_microcode_amd() forward declaration (git-fixes).\n- x86/microcode/AMD: Have __apply_microcode_amd() return bool (git-fixes).\n- x86/microcode/AMD: Make __verify_patch_size() return bool (git-fixes).\n- x86/microcode/AMD: Merge early_apply_microcode() into its single callsite (git-fixes).\n- x86/microcode/AMD: Remove ugly linebreak in __verify_patch_section() signature (git-fixes).\n- x86/microcode/AMD: Return bool from find_blobs_in_containers() (git-fixes).\n- x86/microcode: Consolidate the loader enablement checking (git-fixes).\n- x86/mm/init: Handle the special case of device private pages in add_pages(), to not increase max_pfn and trigger dma_addressing_limited() bounce buffers (git-fixes).\n- x86/platform/amd: Move the \u0026lt;asm/amd_hsmp.h\u003e header to \u0026lt;asm/amd/hsmp.h\u003e (jsc#PED-13094).\n- x86/sev: Add SVSM vTPM probe/send_command functions (bsc#1241191).\n- x86/sev: Provide guest VMPL level to userspace (bsc#1241191).\n- x86/sev: Register tpm-svsm platform device (bsc#1241191).\n- x86/xen: fix balloon target initialization for PVH dom0 (git-fixes).\n- x86: Start moving AMD node functionality out of AMD_NB (jsc#PED-13094).\n- xen/arm: call uaccess_ttbr0_enable for dm_op hypercall (git-fixes)\n- xen/x86: fix initial memory balloon target (git-fixes).\n- xhci: dbc: Avoid event polling busyloop if pending rx transfers are inactive (git-fixes).\n- xsk: always clear DMA mapping information when unmapping the pool (git-fixes).\n","status":"published","published":"2025-07-16T12:53:19Z","modified":"2026-03-23T04:46:32.394983Z","updated_at":"2026-11-02T15:53:56.647031Z"},{"id":"USN-7089-1","title":"linux, linux-gcp-6.8, linux-hwe-6.8 vulnerabilities","description":"Chenyuan Yang discovered that the USB Gadget subsystem in the Linux kernel\ndid not properly check for the device to be enabled before writing. A local\nattacker could possibly use this to cause a denial of service. (CVE-2024-25741)\n\nSeveral security issues were discovered in the Linux kernel.\nAn attacker could possibly use these to compromise the system.\nThis update corrects flaws in the following subsystems:\n  - ARM32 architecture;\n  - MIPS architecture;\n  - PA-RISC architecture;\n  - PowerPC architecture;\n  - RISC-V architecture;\n  - S390 architecture;\n  - x86 architecture;\n  - Cryptographic API;\n  - Serial ATA and Parallel ATA drivers;\n  - Null block device driver;\n  - Bluetooth drivers;\n  - Cdrom driver;\n  - Clock framework and drivers;\n  - Hardware crypto device drivers;\n  - CXL (Compute Express Link) drivers;\n  - Cirrus firmware drivers;\n  - GPIO subsystem;\n  - GPU drivers;\n  - I2C subsystem;\n  - IIO subsystem;\n  - InfiniBand drivers;\n  - ISDN/mISDN subsystem;\n  - LED subsystem;\n  - Multiple devices driver;\n  - Media drivers;\n  - Fastrpc Driver;\n  - Network drivers;\n  - Microsoft Azure Network Adapter (MANA) driver;\n  - Near Field Communication (NFC) drivers;\n  - NVME drivers;\n  - NVMEM (Non Volatile Memory) drivers;\n  - PCI subsystem;\n  - Pin controllers subsystem;\n  - x86 platform drivers;\n  - S/390 drivers;\n  - SCSI drivers;\n  - Thermal drivers;\n  - TTY drivers;\n  - UFS subsystem;\n  - USB DSL drivers;\n  - USB core drivers;\n  - DesignWare USB3 driver;\n  - USB Gadget drivers;\n  - USB Serial drivers;\n  - VFIO drivers;\n  - VHOST drivers;\n  - File systems infrastructure;\n  - BTRFS file system;\n  - GFS2 file system;\n  - JFFS2 file system;\n  - JFS file system;\n  - Network file systems library;\n  - Network file system client;\n  - NILFS2 file system;\n  - NTFS3 file system;\n  - SMB network file system;\n  - Memory management;\n  - Netfilter;\n  - Tracing infrastructure;\n  - io_uring subsystem;\n  - BPF subsystem;\n  - Core kernel;\n  - Bluetooth subsystem;\n  - CAN network layer;\n  - Ceph Core library;\n  - Networking core;\n  - IPv4 networking;\n  - IPv6 networking;\n  - IUCV driver;\n  - MAC80211 subsystem;\n  - Network traffic control;\n  - Sun RPC protocol;\n  - Wireless networking;\n  - AMD SoC Alsa drivers;\n  - SoC Audio for Freescale CPUs drivers;\n  - MediaTek ASoC drivers;\n  - SoC audio core drivers;\n  - SOF drivers;\n  - Sound sequencer drivers;\n(CVE-2024-42104, CVE-2024-42084, CVE-2024-42252, CVE-2024-41096,\nCVE-2024-42237, CVE-2024-42140, CVE-2024-42150, CVE-2024-41031,\nCVE-2024-41059, CVE-2024-41062, CVE-2024-41051, CVE-2024-41028,\nCVE-2024-41090, CVE-2024-41092, CVE-2024-43855, CVE-2024-41021,\nCVE-2024-42229, CVE-2024-41056, CVE-2024-41048, CVE-2024-41036,\nCVE-2024-42094, CVE-2024-41089, CVE-2024-41068, CVE-2024-41039,\nCVE-2024-41095, CVE-2024-41069, CVE-2024-42234, CVE-2024-42136,\nCVE-2024-41025, CVE-2024-42157, CVE-2024-42248, CVE-2024-42087,\nCVE-2024-41041, CVE-2024-42230, CVE-2024-42151, CVE-2024-42130,\nCVE-2024-42244, CVE-2024-41079, CVE-2024-42253, CVE-2024-42092,\nCVE-2024-41022, CVE-2024-42137, CVE-2024-42132, CVE-2024-42108,\nCVE-2024-42155, CVE-2024-42127, CVE-2024-41060, CVE-2024-42074,\nCVE-2024-41081, CVE-2024-42066, CVE-2024-42098, CVE-2024-42082,\nCVE-2024-42093, CVE-2024-42245, CVE-2024-41072, CVE-2024-41052,\nCVE-2024-42161, CVE-2024-42096, CVE-2024-42115, CVE-2024-41074,\nCVE-2024-42120, CVE-2024-41046, CVE-2024-42239, CVE-2024-41063,\nCVE-2024-42090, CVE-2024-41023, CVE-2024-42069, CVE-2024-41087,\nCVE-2024-42158, CVE-2024-41067, CVE-2024-41084, CVE-2024-41077,\nCVE-2024-42240, CVE-2024-42145, CVE-2024-42102, CVE-2024-41020,\nCVE-2024-42231, CVE-2024-41053, CVE-2024-42131, CVE-2024-42089,\nCVE-2024-41083, CVE-2024-42247, CVE-2024-42105, CVE-2024-41044,\nCVE-2024-42128, CVE-2024-42271, CVE-2024-41037, CVE-2024-42114,\nCVE-2024-42106, CVE-2024-41076, CVE-2024-42088, CVE-2024-41057,\nCVE-2024-41091, CVE-2024-42152, CVE-2024-41070, CVE-2024-41035,\nCVE-2024-41050, CVE-2024-39487, CVE-2024-42113, CVE-2024-42250,\nCVE-2024-41047, CVE-2024-42149, CVE-2024-42079, CVE-2024-42091,\nCVE-2024-42227, CVE-2024-42095, CVE-2024-42109, CVE-2024-41033,\nCVE-2023-52888, CVE-2024-41061, CVE-2024-42223, CVE-2024-42235,\nCVE-2024-41086, CVE-2024-42133, CVE-2024-41082, CVE-2024-41071,\nCVE-2024-41007, CVE-2023-52887, CVE-2024-39486, CVE-2024-41075,\nCVE-2024-42101, CVE-2024-42077, CVE-2024-41042, CVE-2024-42225,\nCVE-2024-42126, CVE-2024-41094, CVE-2024-41085, CVE-2024-41019,\nCVE-2024-41058, CVE-2024-41066, CVE-2024-42156, CVE-2024-42119,\nCVE-2024-41032, CVE-2024-41088, CVE-2024-42100, CVE-2024-42142,\nCVE-2024-41054, CVE-2024-42103, CVE-2024-42124, CVE-2024-41034,\nCVE-2024-42251, CVE-2024-42153, CVE-2024-41045, CVE-2024-42086,\nCVE-2024-42243, CVE-2024-41055, CVE-2024-41078, CVE-2024-42117,\nCVE-2024-41030, CVE-2024-42068, CVE-2024-42110, CVE-2024-42147,\nCVE-2024-42121, CVE-2024-41080, CVE-2024-41027, CVE-2024-43858,\nCVE-2024-42085, CVE-2024-42111, CVE-2024-42238, CVE-2024-41018,\nCVE-2024-42138, CVE-2024-41038, CVE-2024-42070, CVE-2024-42141,\nCVE-2024-41098, CVE-2024-42118, CVE-2024-41073, CVE-2024-42144,\nCVE-2024-42280, CVE-2024-41049, CVE-2024-42076, CVE-2024-41065,\nCVE-2024-42063, CVE-2024-41064, CVE-2024-41017, CVE-2024-42112,\nCVE-2024-42064, CVE-2024-42135, CVE-2024-42146, CVE-2024-41010,\nCVE-2024-41097, CVE-2024-41012, CVE-2024-42097, CVE-2024-42067,\nCVE-2024-42236, CVE-2024-42080, CVE-2024-42241, CVE-2024-42065,\nCVE-2024-42232, CVE-2024-42246, CVE-2024-41093, CVE-2024-41015,\nCVE-2024-42129, CVE-2024-42073, CVE-2024-41029)\n","status":"published","published":"2024-11-01T13:15:22Z","modified":"2026-10-26T22:33:59.398740884Z","updated_at":"2026-11-02T16:58:18.876384Z"},{"id":"USN-7089-2","title":"linux-azure, linux-gcp, linux-ibm vulnerabilities","description":"\nChenyuan Yang discovered that the USB Gadget subsystem in the Linux\nkernel did not properly check for the device to be enabled before\nwriting. A local attacker could possibly use this to cause a denial of\nservice. (CVE-2024-25741)\n\nSeveral security issues were discovered in the Linux kernel.\nAn attacker could possibly use these to compromise the system.\nThis update corrects flaws in the following subsystems:\n  - ARM32 architecture;\n  - MIPS architecture;\n  - PA-RISC architecture;\n  - PowerPC architecture;\n  - RISC-V architecture;\n  - S390 architecture;\n  - x86 architecture;\n  - Cryptographic API;\n  - Serial ATA and Parallel ATA drivers;\n  - Null block device driver;\n  - Bluetooth drivers;\n  - Cdrom driver;\n  - Clock framework and drivers;\n  - Hardware crypto device drivers;\n  - CXL (Compute Express Link) drivers;\n  - Cirrus firmware drivers;\n  - GPIO subsystem;\n  - GPU drivers;\n  - I2C subsystem;\n  - IIO subsystem;\n  - InfiniBand drivers;\n  - ISDN/mISDN subsystem;\n  - LED subsystem;\n  - Multiple devices driver;\n  - Media drivers;\n  - Fastrpc Driver;\n  - Network drivers;\n  - Microsoft Azure Network Adapter (MANA) driver;\n  - Near Field Communication (NFC) drivers;\n  - NVME drivers;\n  - NVMEM (Non Volatile Memory) drivers;\n  - PCI subsystem;\n  - Pin controllers subsystem;\n  - x86 platform drivers;\n  - S/390 drivers;\n  - SCSI drivers;\n  - Thermal drivers;\n  - TTY drivers;\n  - UFS subsystem;\n  - USB DSL drivers;\n  - USB core drivers;\n  - DesignWare USB3 driver;\n  - USB Gadget drivers;\n  - USB Serial drivers;\n  - VFIO drivers;\n  - VHOST drivers;\n  - File systems infrastructure;\n  - BTRFS file system;\n  - GFS2 file system;\n  - JFFS2 file system;\n  - JFS file system;\n  - Network file systems library;\n  - Network file system client;\n  - NILFS2 file system;\n  - NTFS3 file system;\n  - SMB network file system;\n  - Memory management;\n  - Netfilter;\n  - Tracing infrastructure;\n  - io_uring subsystem;\n  - BPF subsystem;\n  - Core kernel;\n  - Bluetooth subsystem;\n  - CAN network layer;\n  - Ceph Core library;\n  - Networking core;\n  - IPv4 networking;\n  - IPv6 networking;\n  - IUCV driver;\n  - MAC80211 subsystem;\n  - Network traffic control;\n  - Sun RPC protocol;\n  - Wireless networking;\n  - AMD SoC Alsa drivers;\n  - SoC Audio for Freescale CPUs drivers;\n  - MediaTek ASoC drivers;\n  - SoC audio core drivers;\n  - SOF drivers;\n  - Sound sequencer drivers;\n(CVE-2024-42104, CVE-2024-42101, CVE-2024-41052, CVE-2024-42157,\nCVE-2024-41020, CVE-2024-41055, CVE-2024-42124, CVE-2023-52888,\nCVE-2024-42079, CVE-2024-43858, CVE-2024-41075, CVE-2024-42073,\nCVE-2024-42113, CVE-2024-42110, CVE-2024-41080, CVE-2024-42097,\nCVE-2024-41046, CVE-2024-42076, CVE-2024-41010, CVE-2024-41018,\nCVE-2024-42115, CVE-2024-41048, CVE-2024-42231, CVE-2024-42241,\nCVE-2024-41034, CVE-2024-42065, CVE-2024-42140, CVE-2024-42094,\nCVE-2024-41029, CVE-2024-42225, CVE-2024-41096, CVE-2024-42088,\nCVE-2024-41087, CVE-2023-52887, CVE-2024-42141, CVE-2024-42135,\nCVE-2024-42247, CVE-2024-39487, CVE-2024-42229, CVE-2024-42147,\nCVE-2024-42252, CVE-2024-41038, CVE-2024-41083, CVE-2024-42091,\nCVE-2024-42156, CVE-2024-42149, CVE-2024-41015, CVE-2024-41047,\nCVE-2024-42129, CVE-2024-42120, CVE-2024-41097, CVE-2024-42243,\nCVE-2024-42084, CVE-2024-42250, CVE-2024-41023, CVE-2024-41028,\nCVE-2024-42108, CVE-2024-41045, CVE-2024-42098, CVE-2024-41064,\nCVE-2024-42087, CVE-2024-42080, CVE-2024-41049, CVE-2024-42271,\nCVE-2024-41037, CVE-2024-42114, CVE-2024-41044, CVE-2024-42126,\nCVE-2024-42119, CVE-2024-42223, CVE-2024-42280, CVE-2024-42112,\nCVE-2024-41019, CVE-2024-42133, CVE-2024-42152, CVE-2024-41074,\nCVE-2024-41042, CVE-2024-41093, CVE-2024-41025, CVE-2024-42253,\nCVE-2024-42136, CVE-2024-42127, CVE-2024-41036, CVE-2024-42237,\nCVE-2024-42111, CVE-2024-41031, CVE-2024-41069, CVE-2024-41084,\nCVE-2024-41076, CVE-2024-41090, CVE-2024-41088, CVE-2024-41070,\nCVE-2024-42118, CVE-2024-42238, CVE-2024-42234, CVE-2024-41089,\nCVE-2024-41095, CVE-2024-41085, CVE-2024-42106, CVE-2024-42155,\nCVE-2024-42146, CVE-2024-42130, CVE-2024-42089, CVE-2024-42132,\nCVE-2024-41091, CVE-2024-42153, CVE-2024-42236, CVE-2024-42085,\nCVE-2024-41065, CVE-2024-41032, CVE-2024-42090, CVE-2024-41030,\nCVE-2024-41017, CVE-2024-42230, CVE-2024-42144, CVE-2024-42137,\nCVE-2024-41082, CVE-2024-41056, CVE-2024-42145, CVE-2024-41041,\nCVE-2024-42240, CVE-2024-41081, CVE-2024-42103, CVE-2024-41053,\nCVE-2024-42070, CVE-2024-42121, CVE-2024-42105, CVE-2024-41022,\nCVE-2024-42151, CVE-2024-42142, CVE-2024-41035, CVE-2024-42232,\nCVE-2024-41058, CVE-2024-42109, CVE-2024-41077, CVE-2024-42095,\nCVE-2024-39486, CVE-2024-42131, CVE-2024-42068, CVE-2024-41073,\nCVE-2024-41079, CVE-2024-42082, CVE-2024-41071, CVE-2024-41066,\nCVE-2024-42102, CVE-2024-43855, CVE-2024-41061, CVE-2024-41072,\nCVE-2024-41059, CVE-2024-41094, CVE-2024-41021, CVE-2024-41098,\nCVE-2024-42158, CVE-2024-41033, CVE-2024-42096, CVE-2024-42251,\nCVE-2024-42077, CVE-2024-42063, CVE-2024-42227, CVE-2024-41007,\nCVE-2024-41057, CVE-2024-41063, CVE-2024-41039, CVE-2024-41067,\nCVE-2024-41062, CVE-2024-42100, CVE-2024-42074, CVE-2024-42064,\nCVE-2024-41092, CVE-2024-42128, CVE-2024-41086, CVE-2024-41054,\nCVE-2024-42239, CVE-2024-41027, CVE-2024-42093, CVE-2024-42244,\nCVE-2024-41050, CVE-2024-41012, CVE-2024-42246, CVE-2024-42117,\nCVE-2024-42069, CVE-2024-42067, CVE-2024-42086, CVE-2024-42066,\nCVE-2024-41060, CVE-2024-42248, CVE-2024-41068, CVE-2024-42161,\nCVE-2024-42092, CVE-2024-42245, CVE-2024-41078, CVE-2024-42235,\nCVE-2024-42150, CVE-2024-41051, CVE-2024-42138)\n","status":"published","published":"2024-11-04T17:30:30Z","modified":"2026-10-26T22:34:00.39355758Z","updated_at":"2026-11-02T16:58:18.876384Z"},{"id":"USN-7089-3","title":"linux-aws, linux-aws-6.8, linux-oracle, linux-oracle-6.8 vulnerabilities","description":"\nChenyuan Yang discovered that the USB Gadget subsystem in the Linux\nkernel did not properly check for the device to be enabled before\nwriting. A local attacker could possibly use this to cause a denial of\nservice. (CVE-2024-25741)\n\nSeveral security issues were discovered in the Linux kernel.\nAn attacker could possibly use these to compromise the system.\nThis update corrects flaws in the following subsystems:\n  - ARM32 architecture;\n  - MIPS architecture;\n  - PA-RISC architecture;\n  - PowerPC architecture;\n  - RISC-V architecture;\n  - S390 architecture;\n  - x86 architecture;\n  - Cryptographic API;\n  - Serial ATA and Parallel ATA drivers;\n  - Null block device driver;\n  - Bluetooth drivers;\n  - Cdrom driver;\n  - Clock framework and drivers;\n  - Hardware crypto device drivers;\n  - CXL (Compute Express Link) drivers;\n  - Cirrus firmware drivers;\n  - GPIO subsystem;\n  - GPU drivers;\n  - I2C subsystem;\n  - IIO subsystem;\n  - InfiniBand drivers;\n  - ISDN/mISDN subsystem;\n  - LED subsystem;\n  - Multiple devices driver;\n  - Media drivers;\n  - Fastrpc Driver;\n  - Network drivers;\n  - Microsoft Azure Network Adapter (MANA) driver;\n  - Near Field Communication (NFC) drivers;\n  - NVME drivers;\n  - NVMEM (Non Volatile Memory) drivers;\n  - PCI subsystem;\n  - Pin controllers subsystem;\n  - x86 platform drivers;\n  - S/390 drivers;\n  - SCSI drivers;\n  - Thermal drivers;\n  - TTY drivers;\n  - UFS subsystem;\n  - USB DSL drivers;\n  - USB core drivers;\n  - DesignWare USB3 driver;\n  - USB Gadget drivers;\n  - USB Serial drivers;\n  - VFIO drivers;\n  - VHOST drivers;\n  - File systems infrastructure;\n  - BTRFS file system;\n  - GFS2 file system;\n  - JFFS2 file system;\n  - JFS file system;\n  - Network file systems library;\n  - Network file system client;\n  - NILFS2 file system;\n  - NTFS3 file system;\n  - SMB network file system;\n  - Memory management;\n  - Netfilter;\n  - Tracing infrastructure;\n  - io_uring subsystem;\n  - BPF subsystem;\n  - Core kernel;\n  - Bluetooth subsystem;\n  - CAN network layer;\n  - Ceph Core library;\n  - Networking core;\n  - IPv4 networking;\n  - IPv6 networking;\n  - IUCV driver;\n  - MAC80211 subsystem;\n  - Network traffic control;\n  - Sun RPC protocol;\n  - Wireless networking;\n  - AMD SoC Alsa drivers;\n  - SoC Audio for Freescale CPUs drivers;\n  - MediaTek ASoC drivers;\n  - SoC audio core drivers;\n  - SOF drivers;\n  - Sound sequencer drivers;\n(CVE-2024-42239, CVE-2024-42079, CVE-2024-41080, CVE-2024-42064,\nCVE-2024-42127, CVE-2024-41049, CVE-2024-41086, CVE-2024-42142,\nCVE-2024-42244, CVE-2024-41060, CVE-2024-42131, CVE-2024-42085,\nCVE-2024-42246, CVE-2024-41062, CVE-2024-42115, CVE-2024-42234,\nCVE-2024-42080, CVE-2024-41095, CVE-2024-41063, CVE-2024-42227,\nCVE-2024-41089, CVE-2024-42133, CVE-2024-43858, CVE-2024-42135,\nCVE-2024-42113, CVE-2024-42120, CVE-2024-42149, CVE-2024-42132,\nCVE-2024-41038, CVE-2024-41069, CVE-2024-41090, CVE-2024-41059,\nCVE-2024-41028, CVE-2024-42126, CVE-2024-42121, CVE-2024-42155,\nCVE-2024-42110, CVE-2024-41021, CVE-2024-41044, CVE-2024-42098,\nCVE-2024-42235, CVE-2024-41083, CVE-2024-41065, CVE-2024-42094,\nCVE-2024-42229, CVE-2024-42240, CVE-2024-42225, CVE-2024-42230,\nCVE-2024-41088, CVE-2024-42073, CVE-2024-42145, CVE-2024-42076,\nCVE-2024-42087, CVE-2024-42241, CVE-2024-41019, CVE-2024-41052,\nCVE-2024-42093, CVE-2024-42063, CVE-2024-41039, CVE-2024-42106,\nCVE-2024-42108, CVE-2024-42237, CVE-2024-41048, CVE-2024-41033,\nCVE-2023-52888, CVE-2024-41096, CVE-2024-41032, CVE-2024-41091,\nCVE-2024-42238, CVE-2024-41056, CVE-2024-42091, CVE-2024-42088,\nCVE-2024-41047, CVE-2024-42271, CVE-2024-41064, CVE-2024-42223,\nCVE-2024-42129, CVE-2024-42102, CVE-2024-42146, CVE-2024-42138,\nCVE-2024-41079, CVE-2024-42232, CVE-2024-42112, CVE-2024-39487,\nCVE-2024-42245, CVE-2024-41093, CVE-2024-41066, CVE-2024-43855,\nCVE-2024-41055, CVE-2024-42100, CVE-2024-41053, CVE-2024-42069,\nCVE-2024-42252, CVE-2024-42243, CVE-2024-42124, CVE-2024-41054,\nCVE-2024-42151, CVE-2024-42118, CVE-2024-42251, CVE-2024-42137,\nCVE-2024-41071, CVE-2024-41010, CVE-2024-41087, CVE-2024-41050,\nCVE-2024-42068, CVE-2024-42158, CVE-2024-41075, CVE-2024-42141,\nCVE-2024-42236, CVE-2024-41068, CVE-2024-42157, CVE-2024-42140,\nCVE-2024-41058, CVE-2024-41076, CVE-2024-42097, CVE-2024-41029,\nCVE-2024-41097, CVE-2024-42109, CVE-2024-41051, CVE-2024-41061,\nCVE-2024-42156, CVE-2024-42101, CVE-2024-41031, CVE-2024-41017,\nCVE-2024-42247, CVE-2024-42128, CVE-2024-41085, CVE-2024-41072,\nCVE-2024-42248, CVE-2024-41045, CVE-2024-42104, CVE-2024-42253,\nCVE-2024-42117, CVE-2024-41078, CVE-2024-42130, CVE-2024-42090,\nCVE-2024-42280, CVE-2024-42250, CVE-2024-42231, CVE-2024-41042,\nCVE-2024-42077, CVE-2024-42153, CVE-2024-41015, CVE-2024-41035,\nCVE-2024-41082, CVE-2024-42114, CVE-2024-41007, CVE-2024-41073,\nCVE-2024-42161, CVE-2024-42082, CVE-2024-42150, CVE-2024-42111,\nCVE-2024-42086, CVE-2024-42095, CVE-2024-41025, CVE-2024-41081,\nCVE-2024-42105, CVE-2024-41027, CVE-2024-42089, CVE-2024-39486,\nCVE-2024-41084, CVE-2024-42092, CVE-2024-42152, CVE-2024-41022,\nCVE-2024-41077, CVE-2024-41098, CVE-2024-41023, CVE-2024-42066,\nCVE-2024-41034, CVE-2024-41037, CVE-2024-41046, CVE-2023-52887,\nCVE-2024-42147, CVE-2024-42065, CVE-2024-42096, CVE-2024-41018,\nCVE-2024-42067, CVE-2024-41041, CVE-2024-42103, CVE-2024-42084,\nCVE-2024-42074, CVE-2024-41094, CVE-2024-42119, CVE-2024-41012,\nCVE-2024-41020, CVE-2024-41074, CVE-2024-42144, CVE-2024-41067,\nCVE-2024-42070, CVE-2024-41057, CVE-2024-41036, CVE-2024-42136,\nCVE-2024-41030, CVE-2024-41070, CVE-2024-41092)\n","status":"published","published":"2024-11-07T09:15:50Z","modified":"2026-10-26T22:34:10.691578849Z","updated_at":"2026-11-02T16:58:18.876384Z"},{"id":"USN-7089-4","title":"linux-oem-6.8 vulnerabilities","description":"\nChenyuan Yang discovered that the USB Gadget subsystem in the Linux\nkernel did not properly check for the device to be enabled before\nwriting. A local attacker could possibly use this to cause a denial of\nservice. (CVE-2024-25741)\n\nSeveral security issues were discovered in the Linux kernel.\nAn attacker could possibly use these to compromise the system.\nThis update corrects flaws in the following subsystems:\n  - ARM32 architecture;\n  - MIPS architecture;\n  - PA-RISC architecture;\n  - PowerPC architecture;\n  - RISC-V architecture;\n  - S390 architecture;\n  - x86 architecture;\n  - Cryptographic API;\n  - Serial ATA and Parallel ATA drivers;\n  - Null block device driver;\n  - Bluetooth drivers;\n  - Cdrom driver;\n  - Clock framework and drivers;\n  - Hardware crypto device drivers;\n  - CXL (Compute Express Link) drivers;\n  - Cirrus firmware drivers;\n  - GPIO subsystem;\n  - GPU drivers;\n  - I2C subsystem;\n  - IIO subsystem;\n  - InfiniBand drivers;\n  - ISDN/mISDN subsystem;\n  - LED subsystem;\n  - Multiple devices driver;\n  - Media drivers;\n  - Fastrpc Driver;\n  - Network drivers;\n  - Microsoft Azure Network Adapter (MANA) driver;\n  - Near Field Communication (NFC) drivers;\n  - NVME drivers;\n  - NVMEM (Non Volatile Memory) drivers;\n  - PCI subsystem;\n  - Pin controllers subsystem;\n  - x86 platform drivers;\n  - S/390 drivers;\n  - SCSI drivers;\n  - Thermal drivers;\n  - TTY drivers;\n  - UFS subsystem;\n  - USB DSL drivers;\n  - USB core drivers;\n  - DesignWare USB3 driver;\n  - USB Gadget drivers;\n  - USB Serial drivers;\n  - VFIO drivers;\n  - VHOST drivers;\n  - File systems infrastructure;\n  - BTRFS file system;\n  - GFS2 file system;\n  - JFFS2 file system;\n  - JFS file system;\n  - Network file systems library;\n  - Network file system client;\n  - NILFS2 file system;\n  - NTFS3 file system;\n  - SMB network file system;\n  - Memory management;\n  - Netfilter;\n  - Tracing infrastructure;\n  - io_uring subsystem;\n  - BPF subsystem;\n  - Core kernel;\n  - Bluetooth subsystem;\n  - CAN network layer;\n  - Ceph Core library;\n  - Networking core;\n  - IPv4 networking;\n  - IPv6 networking;\n  - IUCV driver;\n  - MAC80211 subsystem;\n  - Network traffic control;\n  - Sun RPC protocol;\n  - Wireless networking;\n  - AMD SoC Alsa drivers;\n  - SoC Audio for Freescale CPUs drivers;\n  - MediaTek ASoC drivers;\n  - SoC audio core drivers;\n  - SOF drivers;\n  - Sound sequencer drivers;\n(CVE-2024-41064, CVE-2024-41087, CVE-2023-52888, CVE-2024-42098,\nCVE-2024-42111, CVE-2024-42076, CVE-2024-42088, CVE-2024-42135,\nCVE-2024-42145, CVE-2024-42142, CVE-2024-41036, CVE-2024-41071,\nCVE-2024-41012, CVE-2024-42091, CVE-2024-42253, CVE-2024-42119,\nCVE-2024-42097, CVE-2024-42243, CVE-2024-39487, CVE-2024-42235,\nCVE-2024-42120, CVE-2024-42149, CVE-2024-41015, CVE-2024-41074,\nCVE-2024-42067, CVE-2024-42090, CVE-2024-42128, CVE-2024-41038,\nCVE-2024-42113, CVE-2024-42102, CVE-2024-42231, CVE-2024-42080,\nCVE-2024-42241, CVE-2024-42106, CVE-2024-42130, CVE-2024-42073,\nCVE-2024-42153, CVE-2024-42156, CVE-2024-42118, CVE-2024-41007,\nCVE-2024-41049, CVE-2024-39486, CVE-2024-42240, CVE-2024-41018,\nCVE-2024-42251, CVE-2024-42280, CVE-2024-42096, CVE-2024-42121,\nCVE-2024-42246, CVE-2024-42092, CVE-2024-41090, CVE-2024-42157,\nCVE-2024-43858, CVE-2024-42150, CVE-2024-42110, CVE-2024-41010,\nCVE-2024-41081, CVE-2024-41061, CVE-2024-41078, CVE-2024-41094,\nCVE-2024-41039, CVE-2024-42114, CVE-2024-42109, CVE-2024-41030,\nCVE-2024-42066, CVE-2024-41035, CVE-2024-42146, CVE-2024-42131,\nCVE-2024-41059, CVE-2024-41067, CVE-2024-42138, CVE-2024-41050,\nCVE-2024-41034, CVE-2024-41077, CVE-2024-41076, CVE-2024-41088,\nCVE-2024-41096, CVE-2024-41073, CVE-2024-41037, CVE-2024-42232,\nCVE-2024-41063, CVE-2024-42117, CVE-2024-42155, CVE-2024-41080,\nCVE-2024-42132, CVE-2024-42084, CVE-2024-42136, CVE-2024-42223,\nCVE-2024-41068, CVE-2024-42225, CVE-2024-42065, CVE-2024-41051,\nCVE-2024-43855, CVE-2024-42238, CVE-2024-42250, CVE-2024-42112,\nCVE-2024-41070, CVE-2023-52887, CVE-2024-42094, CVE-2024-42095,\nCVE-2024-41086, CVE-2024-41020, CVE-2024-41082, CVE-2024-42115,\nCVE-2024-42152, CVE-2024-42239, CVE-2024-42093, CVE-2024-42126,\nCVE-2024-41022, CVE-2024-41017, CVE-2024-41092, CVE-2024-41044,\nCVE-2024-42140, CVE-2024-41029, CVE-2024-41054, CVE-2024-42158,\nCVE-2024-41066, CVE-2024-42244, CVE-2024-42070, CVE-2024-41025,\nCVE-2024-42229, CVE-2024-42085, CVE-2024-41084, CVE-2024-41060,\nCVE-2024-41062, CVE-2024-42105, CVE-2024-42124, CVE-2024-41045,\nCVE-2024-42227, CVE-2024-41047, CVE-2024-41042, CVE-2024-42100,\nCVE-2024-42247, CVE-2024-41041, CVE-2024-42087, CVE-2024-42252,\nCVE-2024-41058, CVE-2024-42063, CVE-2024-42271, CVE-2024-41027,\nCVE-2024-42079, CVE-2024-42104, CVE-2024-41098, CVE-2024-41033,\nCVE-2024-41072, CVE-2024-41031, CVE-2024-42089, CVE-2024-41032,\nCVE-2024-42127, CVE-2024-41093, CVE-2024-42082, CVE-2024-41023,\nCVE-2024-41075, CVE-2024-42151, CVE-2024-42141, CVE-2024-42108,\nCVE-2024-42068, CVE-2024-41085, CVE-2024-42103, CVE-2024-41057,\nCVE-2024-42064, CVE-2024-42161, CVE-2024-41052, CVE-2024-41053,\nCVE-2024-42069, CVE-2024-41021, CVE-2024-42147, CVE-2024-41065,\nCVE-2024-41091, CVE-2024-41079, CVE-2024-42086, CVE-2024-42234,\nCVE-2024-41055, CVE-2024-41083, CVE-2024-42101, CVE-2024-42230,\nCVE-2024-41095, CVE-2024-41019, CVE-2024-42245, CVE-2024-42129,\nCVE-2024-42144, CVE-2024-42236, CVE-2024-41028, CVE-2024-42077,\nCVE-2024-42248, CVE-2024-41046, CVE-2024-42133, CVE-2024-42074,\nCVE-2024-41089, CVE-2024-42237, CVE-2024-41056, CVE-2024-41048,\nCVE-2024-42137, CVE-2024-41069, CVE-2024-41097)\n","status":"published","published":"2024-11-13T12:05:57Z","modified":"2026-10-26T22:33:54.911543556Z","updated_at":"2026-11-02T16:58:18.876384Z"},{"id":"USN-7089-5","title":"linux-raspi vulnerabilities","description":"Chenyuan Yang discovered that the USB Gadget subsystem in the Linux\nkernel did not properly check for the device to be enabled before\nwriting. A local attacker could possibly use this to cause a denial of\nservice. (CVE-2024-25741)\n\nSeveral security issues were discovered in the Linux kernel.\nAn attacker could possibly use these to compromise the system.\nThis update corrects flaws in the following subsystems:\n  - ARM32 architecture;\n  - MIPS architecture;\n  - PA-RISC architecture;\n  - PowerPC architecture;\n  - RISC-V architecture;\n  - S390 architecture;\n  - x86 architecture;\n  - Cryptographic API;\n  - Serial ATA and Parallel ATA drivers;\n  - Null block device driver;\n  - Bluetooth drivers;\n  - Cdrom driver;\n  - Clock framework and drivers;\n  - Hardware crypto device drivers;\n  - CXL (Compute Express Link) drivers;\n  - Cirrus firmware drivers;\n  - GPIO subsystem;\n  - GPU drivers;\n  - I2C subsystem;\n  - IIO subsystem;\n  - InfiniBand drivers;\n  - ISDN/mISDN subsystem;\n  - LED subsystem;\n  - Multiple devices driver;\n  - Media drivers;\n  - Fastrpc Driver;\n  - Network drivers;\n  - Microsoft Azure Network Adapter (MANA) driver;\n  - Near Field Communication (NFC) drivers;\n  - NVME drivers;\n  - NVMEM (Non Volatile Memory) drivers;\n  - PCI subsystem;\n  - Pin controllers subsystem;\n  - x86 platform drivers;\n  - S/390 drivers;\n  - SCSI drivers;\n  - Thermal drivers;\n  - TTY drivers;\n  - UFS subsystem;\n  - USB DSL drivers;\n  - USB core drivers;\n  - DesignWare USB3 driver;\n  - USB Gadget drivers;\n  - USB Serial drivers;\n  - VFIO drivers;\n  - VHOST drivers;\n  - File systems infrastructure;\n  - BTRFS file system;\n  - GFS2 file system;\n  - JFFS2 file system;\n  - JFS file system;\n  - Network file systems library;\n  - Network file system client;\n  - NILFS2 file system;\n  - NTFS3 file system;\n  - SMB network file system;\n  - Memory management;\n  - Netfilter;\n  - Tracing infrastructure;\n  - io_uring subsystem;\n  - BPF subsystem;\n  - Core kernel;\n  - Bluetooth subsystem;\n  - CAN network layer;\n  - Ceph Core library;\n  - Networking core;\n  - IPv4 networking;\n  - IPv6 networking;\n  - IUCV driver;\n  - MAC80211 subsystem;\n  - Network traffic control;\n  - Sun RPC protocol;\n  - Wireless networking;\n  - AMD SoC Alsa drivers;\n  - SoC Audio for Freescale CPUs drivers;\n  - MediaTek ASoC drivers;\n  - SoC audio core drivers;\n  - SOF drivers;\n  - Sound sequencer drivers;\n(CVE-2024-42223, CVE-2024-42244, CVE-2024-42105, CVE-2024-42100,\nCVE-2024-42235, CVE-2024-41007, CVE-2024-41047, CVE-2024-42088,\nCVE-2024-42079, CVE-2024-41053, CVE-2024-41094, CVE-2024-42227,\nCVE-2024-42253, CVE-2024-42150, CVE-2024-41049, CVE-2024-42096,\nCVE-2024-42093, CVE-2024-41079, CVE-2024-41037, CVE-2024-42129,\nCVE-2024-41031, CVE-2024-39486, CVE-2024-41065, CVE-2024-42101,\nCVE-2024-41082, CVE-2024-42135, CVE-2024-42236, CVE-2024-41078,\nCVE-2024-42098, CVE-2024-41056, CVE-2024-41096, CVE-2024-41074,\nCVE-2024-42246, CVE-2024-42137, CVE-2024-42232, CVE-2024-42121,\nCVE-2024-41093, CVE-2024-41076, CVE-2024-42157, CVE-2024-41062,\nCVE-2024-42104, CVE-2024-42085, CVE-2024-41092, CVE-2024-41034,\nCVE-2024-41036, CVE-2024-41072, CVE-2024-41012, CVE-2024-39487,\nCVE-2024-42124, CVE-2024-42065, CVE-2024-41061, CVE-2024-41064,\nCVE-2024-41091, CVE-2024-42119, CVE-2024-41088, CVE-2024-42089,\nCVE-2024-41048, CVE-2024-41032, CVE-2024-41020, CVE-2024-42066,\nCVE-2024-42068, CVE-2024-42238, CVE-2024-41069, CVE-2024-41044,\nCVE-2024-41025, CVE-2024-42161, CVE-2023-52887, CVE-2024-42127,\nCVE-2024-42239, CVE-2024-42149, CVE-2024-42091, CVE-2024-42097,\nCVE-2024-41054, CVE-2024-41041, CVE-2024-42131, CVE-2024-41089,\nCVE-2024-41018, CVE-2024-42067, CVE-2024-41039, CVE-2024-42128,\nCVE-2024-42248, CVE-2024-41090, CVE-2024-42073, CVE-2024-43858,\nCVE-2024-42225, CVE-2024-42077, CVE-2024-42247, CVE-2024-42109,\nCVE-2024-41045, CVE-2024-41019, CVE-2024-42231, CVE-2024-41017,\nCVE-2024-42145, CVE-2024-41046, CVE-2024-42063, CVE-2024-41087,\nCVE-2024-41033, CVE-2024-41021, CVE-2024-42241, CVE-2024-42229,\nCVE-2024-41015, CVE-2024-42087, CVE-2024-42133, CVE-2024-41073,\nCVE-2024-42070, CVE-2024-41067, CVE-2024-41077, CVE-2024-42102,\nCVE-2024-42158, CVE-2024-42126, CVE-2024-41042, CVE-2024-41055,\nCVE-2024-42092, CVE-2024-42114, CVE-2024-41059, CVE-2024-41058,\nCVE-2024-41071, CVE-2024-42144, CVE-2024-42146, CVE-2024-41084,\nCVE-2024-42155, CVE-2024-42245, CVE-2024-42156, CVE-2024-41050,\nCVE-2024-42141, CVE-2024-42095, CVE-2024-41097, CVE-2024-42103,\nCVE-2024-42152, CVE-2024-42140, CVE-2024-41023, CVE-2024-41083,\nCVE-2024-42138, CVE-2024-42271, CVE-2024-42252, CVE-2024-42237,\nCVE-2024-42132, CVE-2024-41098, CVE-2024-42086, CVE-2024-41063,\nCVE-2024-42153, CVE-2024-41070, CVE-2024-42115, CVE-2024-42111,\nCVE-2024-42142, CVE-2024-42069, CVE-2024-41027, CVE-2024-42130,\nCVE-2024-42090, CVE-2024-42251, CVE-2024-42118, CVE-2024-41060,\nCVE-2024-41029, CVE-2024-41095, CVE-2024-41038, CVE-2024-42243,\nCVE-2024-42112, CVE-2024-41035, CVE-2024-42240, CVE-2024-41066,\nCVE-2024-41085, CVE-2024-42082, CVE-2024-42117, CVE-2024-42250,\nCVE-2024-41080, CVE-2024-42147, CVE-2024-41081, CVE-2024-42113,\nCVE-2023-52888, CVE-2024-42136, CVE-2024-41057, CVE-2024-41086,\nCVE-2024-42064, CVE-2024-42234, CVE-2024-42076, CVE-2024-42084,\nCVE-2024-42094, CVE-2024-42230, CVE-2024-41068, CVE-2024-43855,\nCVE-2024-42080, CVE-2024-41052, CVE-2024-41051, CVE-2024-42074,\nCVE-2024-41010, CVE-2024-41028, CVE-2024-41030, CVE-2024-41022,\nCVE-2024-42120, CVE-2024-42108, CVE-2024-41075, CVE-2024-42106,\nCVE-2024-42280, CVE-2024-42110, CVE-2024-42151)\n","status":"published","published":"2024-11-14T16:55:06Z","modified":"2026-10-26T22:33:56.031381167Z","updated_at":"2026-11-02T16:58:18.876384Z"},{"id":"USN-7089-6","title":"linux-gke vulnerabilities","description":"\nChenyuan Yang discovered that the USB Gadget subsystem in the Linux\nkernel did not properly check for the device to be enabled before\nwriting. A local attacker could possibly use this to cause a denial of\nservice. (CVE-2024-25741)\n\nSeveral security issues were discovered in the Linux kernel.\nAn attacker could possibly use these to compromise the system.\nThis update corrects flaws in the following subsystems:\n  - ARM32 architecture;\n  - MIPS architecture;\n  - PA-RISC architecture;\n  - PowerPC architecture;\n  - RISC-V architecture;\n  - S390 architecture;\n  - x86 architecture;\n  - Cryptographic API;\n  - Serial ATA and Parallel ATA drivers;\n  - Null block device driver;\n  - Bluetooth drivers;\n  - Cdrom driver;\n  - Clock framework and drivers;\n  - Hardware crypto device drivers;\n  - CXL (Compute Express Link) drivers;\n  - Cirrus firmware drivers;\n  - GPIO subsystem;\n  - GPU drivers;\n  - I2C subsystem;\n  - IIO subsystem;\n  - InfiniBand drivers;\n  - ISDN/mISDN subsystem;\n  - LED subsystem;\n  - Multiple devices driver;\n  - Media drivers;\n  - Fastrpc Driver;\n  - Network drivers;\n  - Microsoft Azure Network Adapter (MANA) driver;\n  - Near Field Communication (NFC) drivers;\n  - NVME drivers;\n  - NVMEM (Non Volatile Memory) drivers;\n  - PCI subsystem;\n  - Pin controllers subsystem;\n  - x86 platform drivers;\n  - S/390 drivers;\n  - SCSI drivers;\n  - Thermal drivers;\n  - TTY drivers;\n  - UFS subsystem;\n  - USB DSL drivers;\n  - USB core drivers;\n  - DesignWare USB3 driver;\n  - USB Gadget drivers;\n  - USB Serial drivers;\n  - VFIO drivers;\n  - VHOST drivers;\n  - File systems infrastructure;\n  - BTRFS file system;\n  - GFS2 file system;\n  - JFFS2 file system;\n  - JFS file system;\n  - Network file systems library;\n  - Network file system client;\n  - NILFS2 file system;\n  - NTFS3 file system;\n  - SMB network file system;\n  - Memory management;\n  - Netfilter;\n  - Tracing infrastructure;\n  - io_uring subsystem;\n  - BPF subsystem;\n  - Core kernel;\n  - Bluetooth subsystem;\n  - CAN network layer;\n  - Ceph Core library;\n  - Networking core;\n  - IPv4 networking;\n  - IPv6 networking;\n  - IUCV driver;\n  - MAC80211 subsystem;\n  - Network traffic control;\n  - Sun RPC protocol;\n  - Wireless networking;\n  - AMD SoC Alsa drivers;\n  - SoC Audio for Freescale CPUs drivers;\n  - MediaTek ASoC drivers;\n  - SoC audio core drivers;\n  - SOF drivers;\n  - Sound sequencer drivers;\n(CVE-2024-41062, CVE-2024-41029, CVE-2024-42142, CVE-2024-41070,\nCVE-2024-41066, CVE-2024-42150, CVE-2024-42120, CVE-2023-52888,\nCVE-2024-42141, CVE-2024-41032, CVE-2024-42245, CVE-2024-41053,\nCVE-2024-42247, CVE-2024-42161, CVE-2024-42094, CVE-2024-41072,\nCVE-2024-42076, CVE-2024-42091, CVE-2024-42103, CVE-2024-41007,\nCVE-2024-42064, CVE-2024-41075, CVE-2024-42157, CVE-2024-42069,\nCVE-2024-41045, CVE-2024-42068, CVE-2024-42090, CVE-2024-41071,\nCVE-2024-42082, CVE-2024-42146, CVE-2024-41018, CVE-2024-42238,\nCVE-2024-41079, CVE-2024-42241, CVE-2024-42067, CVE-2024-42132,\nCVE-2024-42121, CVE-2024-41025, CVE-2024-42231, CVE-2024-42225,\nCVE-2024-41080, CVE-2024-41086, CVE-2024-41012, CVE-2024-42234,\nCVE-2024-41088, CVE-2024-42129, CVE-2024-42158, CVE-2024-41078,\nCVE-2024-41038, CVE-2024-41055, CVE-2024-42106, CVE-2024-42227,\nCVE-2024-42102, CVE-2024-41082, CVE-2024-42108, CVE-2024-41085,\nCVE-2024-41020, CVE-2024-41054, CVE-2024-42085, CVE-2024-42140,\nCVE-2024-42089, CVE-2024-41047, CVE-2024-42092, CVE-2024-41044,\nCVE-2024-42246, CVE-2024-41035, CVE-2024-42250, CVE-2024-42070,\nCVE-2024-41039, CVE-2024-41061, CVE-2024-42147, CVE-2024-42104,\nCVE-2024-41090, CVE-2024-41096, CVE-2024-41063, CVE-2024-41084,\nCVE-2024-41059, CVE-2024-41097, CVE-2024-41089, CVE-2024-42093,\nCVE-2024-42126, CVE-2024-42135, CVE-2024-42128, CVE-2024-42098,\nCVE-2024-42105, CVE-2024-42124, CVE-2024-42101, CVE-2024-41091,\nCVE-2024-42127, CVE-2024-41077, CVE-2024-42111, CVE-2024-41037,\nCVE-2024-42136, CVE-2024-41083, CVE-2024-42243, CVE-2024-41033,\nCVE-2024-41046, CVE-2024-42230, CVE-2024-42080, CVE-2024-42096,\nCVE-2024-42100, CVE-2024-42236, CVE-2024-41022, CVE-2024-42086,\nCVE-2024-42251, CVE-2024-41015, CVE-2024-41027, CVE-2024-42155,\nCVE-2024-42117, CVE-2024-41036, CVE-2024-42133, CVE-2024-41010,\nCVE-2024-42151, CVE-2024-42118, CVE-2024-39486, CVE-2024-42066,\nCVE-2024-42131, CVE-2024-42223, CVE-2024-41081, CVE-2024-42244,\nCVE-2024-41073, CVE-2024-42114, CVE-2024-42252, CVE-2024-42248,\nCVE-2024-42110, CVE-2024-41051, CVE-2023-52887, CVE-2024-42156,\nCVE-2024-41074, CVE-2024-41017, CVE-2024-42079, CVE-2024-41034,\nCVE-2024-41028, CVE-2024-42109, CVE-2024-42235, CVE-2024-41058,\nCVE-2024-42232, CVE-2024-42084, CVE-2024-41076, CVE-2024-41030,\nCVE-2024-41023, CVE-2024-42271, CVE-2024-41050, CVE-2024-41042,\nCVE-2024-41031, CVE-2024-42112, CVE-2024-41092, CVE-2024-42253,\nCVE-2024-42152, CVE-2024-41049, CVE-2024-42237, CVE-2024-41095,\nCVE-2024-42280, CVE-2024-42153, CVE-2024-42115, CVE-2024-42130,\nCVE-2024-41064, CVE-2024-42077, CVE-2024-41067, CVE-2024-42137,\nCVE-2024-41019, CVE-2024-42240, CVE-2024-41093, CVE-2024-41048,\nCVE-2024-42063, CVE-2024-42113, CVE-2024-42145, CVE-2024-42073,\nCVE-2024-43858, CVE-2024-42088, CVE-2024-41069, CVE-2024-41068,\nCVE-2024-42138, CVE-2024-41065, CVE-2024-42087, CVE-2024-42239,\nCVE-2024-42149, CVE-2024-41021, CVE-2024-42065, CVE-2024-39487,\nCVE-2024-41052, CVE-2024-42095, CVE-2024-42074, CVE-2024-42097,\nCVE-2024-41098, CVE-2024-41057, CVE-2024-41060, CVE-2024-42119,\nCVE-2024-42229, CVE-2024-43855, CVE-2024-41056, CVE-2024-41041,\nCVE-2024-42144, CVE-2024-41087, CVE-2024-41094)\n","status":"published","published":"2024-11-15T10:36:16Z","modified":"2026-10-26T22:34:10.328493163Z","updated_at":"2026-11-02T16:58:18.876384Z"},{"id":"USN-7089-7","title":"linux-lowlatency, linux-lowlatency-hwe-6.8 vulnerabilities","description":"Chenyuan Yang discovered that the USB Gadget subsystem in the Linux\nkernel did not properly check for the device to be enabled before\nwriting. A local attacker could possibly use this to cause a denial of\nservice. (CVE-2024-25741)\n\nSeveral security issues were discovered in the Linux kernel.\nAn attacker could possibly use these to compromise the system.\nThis update corrects flaws in the following subsystems:\n  - ARM32 architecture;\n  - MIPS architecture;\n  - PA-RISC architecture;\n  - PowerPC architecture;\n  - RISC-V architecture;\n  - S390 architecture;\n  - x86 architecture;\n  - Cryptographic API;\n  - Serial ATA and Parallel ATA drivers;\n  - Null block device driver;\n  - Bluetooth drivers;\n  - Cdrom driver;\n  - Clock framework and drivers;\n  - Hardware crypto device drivers;\n  - CXL (Compute Express Link) drivers;\n  - Cirrus firmware drivers;\n  - GPIO subsystem;\n  - GPU drivers;\n  - I2C subsystem;\n  - IIO subsystem;\n  - InfiniBand drivers;\n  - ISDN/mISDN subsystem;\n  - LED subsystem;\n  - Multiple devices driver;\n  - Media drivers;\n  - Fastrpc Driver;\n  - Network drivers;\n  - Microsoft Azure Network Adapter (MANA) driver;\n  - Near Field Communication (NFC) drivers;\n  - NVME drivers;\n  - NVMEM (Non Volatile Memory) drivers;\n  - PCI subsystem;\n  - Pin controllers subsystem;\n  - x86 platform drivers;\n  - S/390 drivers;\n  - SCSI drivers;\n  - Thermal drivers;\n  - TTY drivers;\n  - UFS subsystem;\n  - USB DSL drivers;\n  - USB core drivers;\n  - DesignWare USB3 driver;\n  - USB Gadget drivers;\n  - USB Serial drivers;\n  - VFIO drivers;\n  - VHOST drivers;\n  - File systems infrastructure;\n  - BTRFS file system;\n  - GFS2 file system;\n  - JFFS2 file system;\n  - JFS file system;\n  - Network file systems library;\n  - Network file system client;\n  - NILFS2 file system;\n  - NTFS3 file system;\n  - SMB network file system;\n  - Memory management;\n  - Netfilter;\n  - Tracing infrastructure;\n  - io_uring subsystem;\n  - BPF subsystem;\n  - Core kernel;\n  - Bluetooth subsystem;\n  - CAN network layer;\n  - Ceph Core library;\n  - Networking core;\n  - IPv4 networking;\n  - IPv6 networking;\n  - IUCV driver;\n  - MAC80211 subsystem;\n  - Network traffic control;\n  - Sun RPC protocol;\n  - Wireless networking;\n  - AMD SoC Alsa drivers;\n  - SoC Audio for Freescale CPUs drivers;\n  - MediaTek ASoC drivers;\n  - SoC audio core drivers;\n  - SOF drivers;\n  - Sound sequencer drivers;\n(CVE-2024-42104, CVE-2024-42084, CVE-2024-42252, CVE-2024-41096,\nCVE-2024-42237, CVE-2024-42140, CVE-2024-42150, CVE-2024-41031,\nCVE-2024-41059, CVE-2024-41062, CVE-2024-41051, CVE-2024-41028,\nCVE-2024-41090, CVE-2024-41092, CVE-2024-43855, CVE-2024-41021,\nCVE-2024-42229, CVE-2024-41056, CVE-2024-41048, CVE-2024-41036,\nCVE-2024-42094, CVE-2024-41089, CVE-2024-41068, CVE-2024-41039,\nCVE-2024-41095, CVE-2024-41069, CVE-2024-42234, CVE-2024-42136,\nCVE-2024-41025, CVE-2024-42157, CVE-2024-42248, CVE-2024-42087,\nCVE-2024-41041, CVE-2024-42230, CVE-2024-42151, CVE-2024-42130,\nCVE-2024-42244, CVE-2024-41079, CVE-2024-42253, CVE-2024-42092,\nCVE-2024-41022, CVE-2024-42137, CVE-2024-42132, CVE-2024-42108,\nCVE-2024-42155, CVE-2024-42127, CVE-2024-41060, CVE-2024-42074,\nCVE-2024-41081, CVE-2024-42066, CVE-2024-42098, CVE-2024-42082,\nCVE-2024-42093, CVE-2024-42245, CVE-2024-41072, CVE-2024-41052,\nCVE-2024-42161, CVE-2024-42096, CVE-2024-42115, CVE-2024-41074,\nCVE-2024-42120, CVE-2024-41046, CVE-2024-42239, CVE-2024-41063,\nCVE-2024-42090, CVE-2024-41023, CVE-2024-42069, CVE-2024-41087,\nCVE-2024-42158, CVE-2024-41067, CVE-2024-41084, CVE-2024-41077,\nCVE-2024-42240, CVE-2024-42145, CVE-2024-42102, CVE-2024-41020,\nCVE-2024-42231, CVE-2024-41053, CVE-2024-42131, CVE-2024-42089,\nCVE-2024-41083, CVE-2024-42247, CVE-2024-42105, CVE-2024-41044,\nCVE-2024-42128, CVE-2024-42271, CVE-2024-41037, CVE-2024-42114,\nCVE-2024-42106, CVE-2024-41076, CVE-2024-42088, CVE-2024-41057,\nCVE-2024-41091, CVE-2024-42152, CVE-2024-41070, CVE-2024-41035,\nCVE-2024-41050, CVE-2024-39487, CVE-2024-42113, CVE-2024-42250,\nCVE-2024-41047, CVE-2024-42149, CVE-2024-42079, CVE-2024-42091,\nCVE-2024-42227, CVE-2024-42095, CVE-2024-42109, CVE-2024-41033,\nCVE-2023-52888, CVE-2024-41061, CVE-2024-42223, CVE-2024-42235,\nCVE-2024-41086, CVE-2024-42133, CVE-2024-41082, CVE-2024-41071,\nCVE-2024-41007, CVE-2023-52887, CVE-2024-39486, CVE-2024-41075,\nCVE-2024-42101, CVE-2024-42077, CVE-2024-41042, CVE-2024-42225,\nCVE-2024-42126, CVE-2024-41094, CVE-2024-41085, CVE-2024-41019,\nCVE-2024-41058, CVE-2024-41066, CVE-2024-42156, CVE-2024-42119,\nCVE-2024-41032, CVE-2024-41088, CVE-2024-42100, CVE-2024-42142,\nCVE-2024-41054, CVE-2024-42103, CVE-2024-42124, CVE-2024-41034,\nCVE-2024-42251, CVE-2024-42153, CVE-2024-41045, CVE-2024-42086,\nCVE-2024-42243, CVE-2024-41055, CVE-2024-41078, CVE-2024-42117,\nCVE-2024-41030, CVE-2024-42068, CVE-2024-42110, CVE-2024-42147,\nCVE-2024-42121, CVE-2024-41080, CVE-2024-41027, CVE-2024-43858,\nCVE-2024-42085, CVE-2024-42111, CVE-2024-42238, CVE-2024-41018,\nCVE-2024-42138, CVE-2024-41038, CVE-2024-42070, CVE-2024-42141,\nCVE-2024-41098, CVE-2024-42118, CVE-2024-41073, CVE-2024-42144,\nCVE-2024-42280, CVE-2024-41049, CVE-2024-42076, CVE-2024-41065,\nCVE-2024-42063, CVE-2024-41064, CVE-2024-41017, CVE-2024-42112,\nCVE-2024-42064, CVE-2024-42135, CVE-2024-42146, CVE-2024-41010,\nCVE-2024-41097, CVE-2024-41012, CVE-2024-42097, CVE-2024-42067,\nCVE-2024-42236, CVE-2024-42080, CVE-2024-42241, CVE-2024-42065,\nCVE-2024-42232, CVE-2024-42246, CVE-2024-41093, CVE-2024-41015,\nCVE-2024-42129, CVE-2024-42073, CVE-2024-41029)\n","status":"published","published":"2024-11-19T22:35:31Z","modified":"2026-10-26T22:34:04.239512543Z","updated_at":"2026-11-02T16:58:18.876384Z"},{"id":"USN-7090-1","title":"linux-azure-6.8 vulnerabilities","description":"\nChenyuan Yang discovered that the USB Gadget subsystem in the Linux\nkernel did not properly check for the device to be enabled before\nwriting. A local attacker could possibly use this to cause a denial of\nservice. (CVE-2024-25741)\n\nSeveral security issues were discovered in the Linux kernel.\nAn attacker could possibly use these to compromise the system.\nThis update corrects flaws in the following subsystems:\n  - ARM32 architecture;\n  - MIPS architecture;\n  - PA-RISC architecture;\n  - PowerPC architecture;\n  - RISC-V architecture;\n  - S390 architecture;\n  - x86 architecture;\n  - Cryptographic API;\n  - Serial ATA and Parallel ATA drivers;\n  - Null block device driver;\n  - Bluetooth drivers;\n  - Cdrom driver;\n  - Clock framework and drivers;\n  - Hardware crypto device drivers;\n  - CXL (Compute Express Link) drivers;\n  - Cirrus firmware drivers;\n  - GPIO subsystem;\n  - GPU drivers;\n  - I2C subsystem;\n  - IIO subsystem;\n  - InfiniBand drivers;\n  - ISDN/mISDN subsystem;\n  - LED subsystem;\n  - Multiple devices driver;\n  - Media drivers;\n  - Fastrpc Driver;\n  - Network drivers;\n  - Microsoft Azure Network Adapter (MANA) driver;\n  - Near Field Communication (NFC) drivers;\n  - NVME drivers;\n  - NVMEM (Non Volatile Memory) drivers;\n  - PCI subsystem;\n  - Pin controllers subsystem;\n  - x86 platform drivers;\n  - S/390 drivers;\n  - SCSI drivers;\n  - Thermal drivers;\n  - TTY drivers;\n  - UFS subsystem;\n  - USB DSL drivers;\n  - USB core drivers;\n  - DesignWare USB3 driver;\n  - USB Gadget drivers;\n  - USB Serial drivers;\n  - VFIO drivers;\n  - VHOST drivers;\n  - File systems infrastructure;\n  - BTRFS file system;\n  - GFS2 file system;\n  - JFFS2 file system;\n  - JFS file system;\n  - Network file systems library;\n  - Network file system client;\n  - NILFS2 file system;\n  - NTFS3 file system;\n  - SMB network file system;\n  - Memory management;\n  - Netfilter;\n  - Tracing infrastructure;\n  - io_uring subsystem;\n  - BPF subsystem;\n  - Core kernel;\n  - Bluetooth subsystem;\n  - CAN network layer;\n  - Ceph Core library;\n  - Networking core;\n  - IPv4 networking;\n  - IPv6 networking;\n  - IUCV driver;\n  - MAC80211 subsystem;\n  - Network traffic control;\n  - Sun RPC protocol;\n  - Wireless networking;\n  - AMD SoC Alsa drivers;\n  - SoC Audio for Freescale CPUs drivers;\n  - MediaTek ASoC drivers;\n  - SoC audio core drivers;\n  - SOF drivers;\n  - Sound sequencer drivers;\n(CVE-2024-42064, CVE-2024-43858, CVE-2024-42251, CVE-2024-42113,\nCVE-2024-41020, CVE-2024-41093, CVE-2024-45016, CVE-2024-42150,\nCVE-2024-42069, CVE-2024-42157, CVE-2024-42126, CVE-2024-42144,\nCVE-2024-42093, CVE-2024-41035, CVE-2024-41032, CVE-2024-41077,\nCVE-2024-42097, CVE-2024-41071, CVE-2024-42227, CVE-2024-42253,\nCVE-2024-42237, CVE-2024-41060, CVE-2024-42080, CVE-2024-42068,\nCVE-2024-41058, CVE-2024-42140, CVE-2024-42231, CVE-2024-42127,\nCVE-2024-42243, CVE-2023-52887, CVE-2024-39486, CVE-2024-41063,\nCVE-2024-42128, CVE-2024-42074, CVE-2024-41028, CVE-2024-42110,\nCVE-2024-45001, CVE-2024-41090, CVE-2024-41084, CVE-2024-41088,\nCVE-2024-42118, CVE-2024-41094, CVE-2024-41091, CVE-2024-41007,\nCVE-2024-42280, CVE-2024-41044, CVE-2024-41012, CVE-2024-42063,\nCVE-2024-41078, CVE-2024-42082, CVE-2024-41055, CVE-2024-41031,\nCVE-2024-42142, CVE-2024-41083, CVE-2024-42145, CVE-2024-41039,\nCVE-2024-41019, CVE-2024-42149, CVE-2024-42248, CVE-2024-42111,\nCVE-2024-41074, CVE-2024-42096, CVE-2024-42100, CVE-2024-41010,\nCVE-2024-43855, CVE-2024-42136, CVE-2024-41054, CVE-2024-41053,\nCVE-2024-41061, CVE-2024-42104, CVE-2024-41025, CVE-2024-42129,\nCVE-2024-41086, CVE-2024-42133, CVE-2024-42115, CVE-2024-42158,\nCVE-2024-42091, CVE-2024-42088, CVE-2024-42161, CVE-2024-42236,\nCVE-2024-41065, CVE-2024-41062, CVE-2024-42153, CVE-2024-41030,\nCVE-2024-41079, CVE-2023-52888, CVE-2024-42223, CVE-2024-42119,\nCVE-2024-42238, CVE-2024-41052, CVE-2024-41064, CVE-2024-42138,\nCVE-2024-41081, CVE-2024-41034, CVE-2024-42147, CVE-2024-41095,\nCVE-2024-42132, CVE-2024-42137, CVE-2024-42106, CVE-2024-41041,\nCVE-2024-41073, CVE-2024-41033, CVE-2024-41075, CVE-2024-42112,\nCVE-2024-41070, CVE-2024-42234, CVE-2024-41027, CVE-2024-42105,\nCVE-2024-41089, CVE-2024-41098, CVE-2024-42152, CVE-2024-42101,\nCVE-2024-41050, CVE-2024-41069, CVE-2024-42120, CVE-2024-42130,\nCVE-2024-42084, CVE-2024-41066, CVE-2024-42108, CVE-2024-42087,\nCVE-2024-41067, CVE-2024-41023, CVE-2024-41046, CVE-2024-42079,\nCVE-2024-42065, CVE-2024-42098, CVE-2024-42070, CVE-2024-41076,\nCVE-2024-41082, CVE-2024-41096, CVE-2024-42235, CVE-2024-42085,\nCVE-2024-42246, CVE-2024-41049, CVE-2024-42076, CVE-2024-41048,\nCVE-2024-41038, CVE-2024-42241, CVE-2024-41092, CVE-2024-42114,\nCVE-2024-41036, CVE-2024-41047, CVE-2024-41029, CVE-2024-42092,\nCVE-2024-41068, CVE-2024-42067, CVE-2024-42094, CVE-2024-42245,\nCVE-2024-41051, CVE-2024-42250, CVE-2024-42151, CVE-2024-41059,\nCVE-2024-41056, CVE-2024-42095, CVE-2024-42131, CVE-2024-42271,\nCVE-2024-42066, CVE-2024-42240, CVE-2024-41017, CVE-2024-42141,\nCVE-2024-41072, CVE-2024-42229, CVE-2024-42239, CVE-2024-42073,\nCVE-2024-42124, CVE-2024-41080, CVE-2024-42146, CVE-2024-41018,\nCVE-2024-41021, CVE-2024-39487, CVE-2024-42086, CVE-2024-42109,\nCVE-2024-41045, CVE-2024-41037, CVE-2024-41097, CVE-2024-42225,\nCVE-2024-42102, CVE-2024-42117, CVE-2024-42077, CVE-2024-42230,\nCVE-2024-41087, CVE-2024-42089, CVE-2024-42252, CVE-2024-42247,\nCVE-2024-41057, CVE-2024-42121, CVE-2024-42232, CVE-2024-42090,\nCVE-2024-41042, CVE-2024-42244, CVE-2024-42156, CVE-2024-42135,\nCVE-2024-42155, CVE-2024-42103, CVE-2024-41015, CVE-2024-41022,\nCVE-2024-41085)\n","status":"published","published":"2024-11-01T13:48:18Z","modified":"2026-10-29T20:02:33.244524175Z","updated_at":"2026-11-02T16:58:18.876384Z"},{"id":"USN-7095-1","title":"linux-nvidia, linux-nvidia-6.8, linux-nvidia-lowlatency vulnerabilities","description":"\nChenyuan Yang discovered that the USB Gadget subsystem in the Linux\nkernel did not properly check for the device to be enabled before\nwriting. A local attacker could possibly use this to cause a denial of\nservice. (CVE-2024-25741)\n\nSeveral security issues were discovered in the Linux kernel.\nAn attacker could possibly use these to compromise the system.\nThis update corrects flaws in the following subsystems:\n  - ARM32 architecture;\n  - MIPS architecture;\n  - PA-RISC architecture;\n  - PowerPC architecture;\n  - RISC-V architecture;\n  - S390 architecture;\n  - x86 architecture;\n  - Cryptographic API;\n  - Serial ATA and Parallel ATA drivers;\n  - Null block device driver;\n  - Bluetooth drivers;\n  - Cdrom driver;\n  - Clock framework and drivers;\n  - Hardware crypto device drivers;\n  - CXL (Compute Express Link) drivers;\n  - Cirrus firmware drivers;\n  - GPIO subsystem;\n  - GPU drivers;\n  - I2C subsystem;\n  - IIO subsystem;\n  - InfiniBand drivers;\n  - ISDN/mISDN subsystem;\n  - LED subsystem;\n  - Multiple devices driver;\n  - Media drivers;\n  - Fastrpc Driver;\n  - Network drivers;\n  - Microsoft Azure Network Adapter (MANA) driver;\n  - Near Field Communication (NFC) drivers;\n  - NVME drivers;\n  - NVMEM (Non Volatile Memory) drivers;\n  - PCI subsystem;\n  - Pin controllers subsystem;\n  - x86 platform drivers;\n  - S/390 drivers;\n  - SCSI drivers;\n  - Thermal drivers;\n  - TTY drivers;\n  - UFS subsystem;\n  - USB DSL drivers;\n  - USB core drivers;\n  - DesignWare USB3 driver;\n  - USB Gadget drivers;\n  - USB Serial drivers;\n  - VFIO drivers;\n  - VHOST drivers;\n  - File systems infrastructure;\n  - BTRFS file system;\n  - GFS2 file system;\n  - JFFS2 file system;\n  - JFS file system;\n  - Network file systems library;\n  - Network file system client;\n  - NILFS2 file system;\n  - NTFS3 file system;\n  - SMB network file system;\n  - Memory management;\n  - Netfilter;\n  - Tracing infrastructure;\n  - io_uring subsystem;\n  - BPF subsystem;\n  - Core kernel;\n  - Bluetooth subsystem;\n  - CAN network layer;\n  - Ceph Core library;\n  - Networking core;\n  - IPv4 networking;\n  - IPv6 networking;\n  - IUCV driver;\n  - MAC80211 subsystem;\n  - Network traffic control;\n  - Sun RPC protocol;\n  - Wireless networking;\n  - AMD SoC Alsa drivers;\n  - SoC Audio for Freescale CPUs drivers;\n  - MediaTek ASoC drivers;\n  - SoC audio core drivers;\n  - SOF drivers;\n  - Sound sequencer drivers;\n(CVE-2024-42271, CVE-2024-42068, CVE-2024-42086, CVE-2024-42132,\nCVE-2024-42074, CVE-2024-41017, CVE-2024-42090, CVE-2024-42280,\nCVE-2024-41030, CVE-2024-41037, CVE-2024-42248, CVE-2024-42084,\nCVE-2024-41057, CVE-2024-42252, CVE-2024-41055, CVE-2024-42158,\nCVE-2024-42097, CVE-2024-42101, CVE-2024-42095, CVE-2024-41084,\nCVE-2024-41051, CVE-2024-41032, CVE-2024-41046, CVE-2024-42231,\nCVE-2024-42133, CVE-2024-42089, CVE-2024-41062, CVE-2024-41033,\nCVE-2024-41012, CVE-2024-41077, CVE-2024-41064, CVE-2024-41082,\nCVE-2024-41090, CVE-2024-42065, CVE-2024-41096, CVE-2024-42119,\nCVE-2024-41054, CVE-2024-42064, CVE-2024-42253, CVE-2024-42237,\nCVE-2024-42120, CVE-2024-41066, CVE-2024-41083, CVE-2024-42129,\nCVE-2024-41085, CVE-2024-41058, CVE-2024-42146, CVE-2024-42156,\nCVE-2024-42076, CVE-2024-42149, CVE-2024-42069, CVE-2024-41039,\nCVE-2024-42110, CVE-2024-42150, CVE-2024-41015, CVE-2024-39486,\nCVE-2024-42144, CVE-2024-42131, CVE-2024-42087, CVE-2024-42091,\nCVE-2024-42236, CVE-2024-42088, CVE-2024-42112, CVE-2024-42142,\nCVE-2024-42082, CVE-2024-42111, CVE-2024-41028, CVE-2024-45001,\nCVE-2024-42077, CVE-2024-42102, CVE-2024-42239, CVE-2024-42140,\nCVE-2024-41091, CVE-2024-41050, CVE-2024-41034, CVE-2024-43858,\nCVE-2024-42145, CVE-2024-42227, CVE-2024-41029, CVE-2024-42230,\nCVE-2024-42096, CVE-2024-42238, CVE-2024-41027, CVE-2024-42063,\nCVE-2024-41023, CVE-2024-41041, CVE-2024-41038, CVE-2024-41073,\nCVE-2024-41067, CVE-2024-41025, CVE-2024-42152, CVE-2024-42247,\nCVE-2024-41065, CVE-2024-42121, CVE-2024-42157, CVE-2024-42080,\nCVE-2024-41076, CVE-2024-41059, CVE-2024-42108, CVE-2024-42251,\nCVE-2024-42093, CVE-2024-42130, CVE-2024-42126, CVE-2024-42079,\nCVE-2024-42246, CVE-2024-41081, CVE-2024-42092, CVE-2024-43855,\nCVE-2024-42235, CVE-2024-42118, CVE-2024-42067, CVE-2024-41047,\nCVE-2024-42155, CVE-2024-41010, CVE-2024-41061, CVE-2024-41007,\nCVE-2024-42245, CVE-2024-42106, CVE-2024-42066, CVE-2024-41078,\nCVE-2024-42113, CVE-2024-41087, CVE-2024-41092, CVE-2024-42234,\nCVE-2024-42124, CVE-2024-42100, CVE-2024-42128, CVE-2024-41072,\nCVE-2024-41022, CVE-2024-41049, CVE-2024-42229, CVE-2024-42225,\nCVE-2024-41052, CVE-2024-42151, CVE-2024-41094, CVE-2024-41098,\nCVE-2024-41035, CVE-2024-41042, CVE-2024-42114, CVE-2024-42250,\nCVE-2024-41095, CVE-2024-42138, CVE-2024-42241, CVE-2024-42103,\nCVE-2024-42094, CVE-2024-41045, CVE-2024-41075, CVE-2024-42073,\nCVE-2024-42153, CVE-2024-41048, CVE-2024-42085, CVE-2024-41074,\nCVE-2024-42244, CVE-2024-41018, CVE-2024-41079, CVE-2024-42127,\nCVE-2023-52887, CVE-2023-52888, CVE-2024-41071, CVE-2024-41020,\nCVE-2024-41036, CVE-2024-42117, CVE-2024-41068, CVE-2024-41056,\nCVE-2024-39487, CVE-2024-42243, CVE-2024-41019, CVE-2024-41070,\nCVE-2024-41044, CVE-2024-41060, CVE-2024-41088, CVE-2024-41021,\nCVE-2024-41053, CVE-2024-42137, CVE-2024-41086, CVE-2024-42104,\nCVE-2024-42109, CVE-2024-42105, CVE-2024-42136, CVE-2024-41080,\nCVE-2024-42098, CVE-2024-41093, CVE-2024-41063, CVE-2024-42161,\nCVE-2024-42147, CVE-2024-42223, CVE-2024-41097, CVE-2024-41069,\nCVE-2024-42240, CVE-2024-42135, CVE-2024-42070, CVE-2024-41089,\nCVE-2024-42141, CVE-2024-42115, CVE-2024-41031, CVE-2024-42232)\n","status":"published","published":"2024-11-07T09:49:52Z","modified":"2026-10-29T20:02:37.125807872Z","updated_at":"2026-11-02T16:58:18.876384Z"},{"id":"USN-7156-1","title":"linux-gkeop vulnerabilities","description":"\nChenyuan Yang discovered that the USB Gadget subsystem in the Linux kernel\ndid not properly check for the device to be enabled before writing. A local\nattacker could possibly use this to cause a denial of service.\n(CVE-2024-25741)\n\nSeveral security issues were discovered in the Linux kernel.\nAn attacker could possibly use these to compromise the system.\nThis update corrects flaws in the following subsystems:\n  - ARM32 architecture;\n  - ARM64 architecture;\n  - MIPS architecture;\n  - PA-RISC architecture;\n  - PowerPC architecture;\n  - RISC-V architecture;\n  - S390 architecture;\n  - User-Mode Linux (UML);\n  - x86 architecture;\n  - Block layer subsystem;\n  - Cryptographic API;\n  - Android drivers;\n  - Serial ATA and Parallel ATA drivers;\n  - ATM drivers;\n  - Drivers core;\n  - Null block device driver;\n  - Ublk userspace block driver;\n  - Bluetooth drivers;\n  - Cdrom driver;\n  - Character device driver;\n  - Clock framework and drivers;\n  - Hardware crypto device drivers;\n  - CXL (Compute Express Link) drivers;\n  - Buffer Sharing and Synchronization framework;\n  - DMA engine subsystem;\n  - Cirrus firmware drivers;\n  - Qualcomm firmware drivers;\n  - GPIO subsystem;\n  - GPU drivers;\n  - HID subsystem;\n  - Hardware monitoring drivers;\n  - I2C subsystem;\n  - I3C subsystem;\n  - IIO subsystem;\n  - InfiniBand drivers;\n  - Input Device core drivers;\n  - Input Device (Miscellaneous) drivers;\n  - IOMMU subsystem;\n  - IRQ chip drivers;\n  - ISDN/mISDN subsystem;\n  - LED subsystem;\n  - Mailbox framework;\n  - Multiple devices driver;\n  - Media drivers;\n  - Fastrpc Driver;\n  - VMware VMCI Driver;\n  - MMC subsystem;\n  - Ethernet bonding driver;\n  - Network drivers;\n  - Mellanox network drivers;\n  - Microsoft Azure Network Adapter (MANA) driver;\n  - Near Field Communication (NFC) drivers;\n  - NVME drivers;\n  - NVMEM (Non Volatile Memory) drivers;\n  - Device tree and open firmware driver;\n  - Parport drivers;\n  - PCI subsystem;\n  - Pin controllers subsystem;\n  - x86 platform drivers;\n  - Power supply drivers;\n  - Remote Processor subsystem;\n  - S/390 drivers;\n  - SCSI subsystem;\n  - QCOM SoC drivers;\n  - SPI subsystem;\n  - Direct Digital Synthesis drivers;\n  - Thermal drivers;\n  - Thunderbolt and USB4 drivers;\n  - TTY drivers;\n  - UFS subsystem;\n  - Userspace I/O drivers;\n  - USB DSL drivers;\n  - USB core drivers;\n  - DesignWare USB3 driver;\n  - USB Gadget drivers;\n  - USB Host Controller drivers;\n  - USB Serial drivers;\n  - USB Type-C Connector System Software Interface driver;\n  - USB over IP driver;\n  - VFIO drivers;\n  - Virtio Host (VHOST) subsystem;\n  - Framebuffer layer;\n  - Xen hypervisor drivers;\n  - File systems infrastructure;\n  - BTRFS file system;\n  - Ext4 file system;\n  - F2FS file system;\n  - GFS2 file system;\n  - JFFS2 file system;\n  - JFS file system;\n  - Network file systems library;\n  - Network file system (NFS) client;\n  - Network file system (NFS) server daemon;\n  - NILFS2 file system;\n  - File system notification infrastructure;\n  - NTFS3 file system;\n  - Proc file system;\n  - SMB network file system;\n  - Tracing file system;\n  - Bitmap API;\n  - BPF subsystem;\n  - Syscall compatibility layer;\n  - Memory Management;\n  - Memory management;\n  - Objagg library;\n  - Perf events;\n  - Syscall interfaces;\n  - Virtio network driver;\n  - VMware vSockets driver;\n  - KCM (Kernel Connection Multiplexor) sockets driver;\n  - Netfilter;\n  - Tracing infrastructure;\n  - io_uring subsystem;\n  - Control group (cgroup);\n  - DMA mapping infrastructure;\n  - Locking primitives;\n  - Padata parallel execution mechanism;\n  - Scheduler infrastructure;\n  - Closures library;\n  - Radix Tree data structure library;\n  - Kernel userspace event delivery library;\n  - KUnit for arithmetic overflow checks;\n  - Bluetooth subsystem;\n  - Ethernet bridge;\n  - CAN network layer;\n  - Ceph Core library;\n  - Networking core;\n  - Ethtool driver;\n  - IPv4 networking;\n  - IPv6 networking;\n  - IUCV driver;\n  - MAC80211 subsystem;\n  - Multipath TCP;\n  - Network traffic control;\n  - SCTP protocol;\n  - Sun RPC protocol;\n  - TIPC protocol;\n  - Wireless networking;\n  - AppArmor security module;\n  - Landlock security;\n  - SELinux security module;\n  - Simplified Mandatory Access Control Kernel framework;\n  - FireWire sound drivers;\n  - AMD SoC Alsa drivers;\n  - Texas InstrumentS Audio (ASoC/HDA) drivers;\n  - SoC Audio for Freescale CPUs drivers;\n  - Intel ASoC drivers;\n  - MediaTek ASoC drivers;\n  - Amlogic Meson SoC drivers;\n  - SoC audio core drivers;\n  - SOF drivers;\n  - Sound sequencer drivers;\n  - USB sound devices;\n  - Real-Time Linux Analysis tools;\n(CVE-2024-43911, CVE-2024-46762, CVE-2024-46794, CVE-2024-43843,\nCVE-2024-42229, CVE-2024-43888, CVE-2024-44978, CVE-2024-46693,\nCVE-2024-46695, CVE-2024-42290, CVE-2024-42067, CVE-2024-45012,\nCVE-2024-42316, CVE-2024-47665, CVE-2024-41052, CVE-2024-42074,\nCVE-2024-41058, CVE-2024-44975, CVE-2024-46709, CVE-2024-46871,\nCVE-2024-42090, CVE-2024-42296, CVE-2024-42096, CVE-2024-42146,\nCVE-2024-46855, CVE-2024-39487, CVE-2024-43825, CVE-2024-42066,\nCVE-2024-42126, CVE-2024-41022, CVE-2024-41025, CVE-2023-52888,\nCVE-2024-46702, CVE-2024-42269, CVE-2024-41082, CVE-2024-42284,\nCVE-2024-42227, CVE-2024-41017, CVE-2024-42250, CVE-2024-46778,\nCVE-2024-47661, CVE-2024-46727, CVE-2024-46845, CVE-2024-44953,\nCVE-2024-47659, CVE-2024-42137, CVE-2024-42245, CVE-2024-41096,\nCVE-2024-46829, CVE-2024-41053, CVE-2024-46782, CVE-2024-44972,\nCVE-2024-41095, CVE-2024-42239, CVE-2024-42127, CVE-2024-42292,\nCVE-2024-46752, CVE-2024-46679, CVE-2024-41076, CVE-2024-46784,\nCVE-2024-46786, CVE-2024-46678, CVE-2024-44957, CVE-2024-46755,\nCVE-2024-47660, CVE-2024-41067, CVE-2024-46838, CVE-2024-43879,\nCVE-2024-45007, CVE-2024-45025, CVE-2024-45001, CVE-2024-41009,\nCVE-2024-41051, CVE-2024-46836, CVE-2024-49984, CVE-2024-45028,\nCVE-2024-43871, CVE-2024-46783, CVE-2024-42272, CVE-2024-42087,\nCVE-2024-46785, CVE-2024-42276, CVE-2024-47658, CVE-2024-46761,\nCVE-2024-46715, CVE-2024-46676, CVE-2024-43824, CVE-2024-42100,\nCVE-2024-46745, CVE-2024-41084, CVE-2024-41086, CVE-2024-45015,\nCVE-2024-46797, CVE-2024-42160, CVE-2024-46706, CVE-2024-46803,\nCVE-2024-46708, CVE-2024-47669, CVE-2024-45009, CVE-2024-41021,\nCVE-2024-42159, CVE-2024-42321, CVE-2024-46868, CVE-2024-41078,\nCVE-2024-42303, CVE-2024-45027, CVE-2024-42309, CVE-2024-43849,\nCVE-2024-43907, CVE-2024-43899, CVE-2024-43823, CVE-2024-42232,\nCVE-2024-44937, CVE-2024-41046, CVE-2024-42237, CVE-2024-42063,\nCVE-2024-42065, CVE-2024-42154, CVE-2024-42259, CVE-2024-46698,\nCVE-2024-46741, CVE-2024-45020, CVE-2024-42151, CVE-2024-41073,\nCVE-2024-46719, CVE-2024-42295, CVE-2024-46859, CVE-2024-41035,\nCVE-2024-46751, CVE-2024-47667, CVE-2024-46728, CVE-2024-46824,\nCVE-2024-42121, CVE-2024-46776, CVE-2024-46768, CVE-2024-43908,\nCVE-2024-43900, CVE-2024-46707, CVE-2024-44934, CVE-2024-41062,\nCVE-2024-42304, CVE-2024-42312, CVE-2024-42157, CVE-2024-41092,\nCVE-2024-41041, CVE-2024-43832, CVE-2024-41039, CVE-2024-44962,\nCVE-2024-46858, CVE-2024-43856, CVE-2024-41060, CVE-2024-45010,\nCVE-2024-41044, CVE-2024-44942, CVE-2024-42307, CVE-2024-44984,\nCVE-2024-41075, CVE-2024-43817, CVE-2024-46791, CVE-2024-46853,\nCVE-2024-42301, CVE-2024-44993, CVE-2024-41094, CVE-2024-27022,\nCVE-2024-41088, CVE-2024-43883, CVE-2024-41087, CVE-2024-46780,\nCVE-2024-42070, CVE-2024-44965, CVE-2024-46823, CVE-2024-46737,\nCVE-2024-44982, CVE-2024-46697, CVE-2024-45021, CVE-2024-44987,\nCVE-2024-41072, CVE-2024-41063, CVE-2024-46757, CVE-2024-46831,\nCVE-2024-44966, CVE-2024-42322, CVE-2024-42231, CVE-2024-46717,\nCVE-2024-41065, CVE-2024-44969, CVE-2023-52887, CVE-2024-42105,\nCVE-2024-44971, CVE-2024-46798, CVE-2024-42262, CVE-2024-44938,\nCVE-2024-42088, CVE-2024-44970, CVE-2024-43876, CVE-2024-46800,\nCVE-2024-42086, CVE-2024-43826, CVE-2024-46729, CVE-2024-46747,\nCVE-2024-46691, CVE-2024-46723, CVE-2024-41018, CVE-2024-42258,\nCVE-2024-41081, CVE-2024-41049, CVE-2024-43837, CVE-2024-45008,\nCVE-2024-41047, CVE-2024-41019, CVE-2024-42152, CVE-2024-41090,\nCVE-2024-46716, CVE-2024-42104, CVE-2024-46804, CVE-2024-43852,\nCVE-2024-42129, CVE-2024-46870, CVE-2024-41093, CVE-2024-45011,\nCVE-2024-41064, CVE-2024-46722, CVE-2024-42286, CVE-2024-45026,\nCVE-2024-46818, CVE-2024-42281, CVE-2024-43854, CVE-2024-41037,\nCVE-2024-44946, CVE-2024-41012, CVE-2024-41098, CVE-2024-42263,\nCVE-2024-42095, CVE-2024-46756, CVE-2024-43913, CVE-2024-46822,\nCVE-2024-44944, CVE-2024-42156, CVE-2024-42073, CVE-2024-42093,\nCVE-2024-44931, CVE-2024-42223, CVE-2024-42264, CVE-2024-42278,\nCVE-2024-46759, CVE-2024-46826, CVE-2024-43828, CVE-2024-42318,\nCVE-2024-42240, CVE-2024-45000, CVE-2024-43909, CVE-2024-46792,\nCVE-2024-42109, CVE-2024-43867, CVE-2024-42130, CVE-2024-42244,\nCVE-2024-44977, CVE-2024-46774, CVE-2024-41030, CVE-2024-42310,\nCVE-2024-42138, CVE-2024-42317, CVE-2024-42224, CVE-2024-46694,\nCVE-2024-46815, CVE-2024-46677, CVE-2024-46763, CVE-2024-46860,\nCVE-2024-46767, CVE-2024-42111, CVE-2024-41020, CVE-2024-46726,\nCVE-2024-42117, CVE-2024-43831, CVE-2024-42285, CVE-2024-46842,\nCVE-2024-43857, CVE-2024-41031, CVE-2024-43834, CVE-2024-42135,\nCVE-2024-42241, CVE-2024-46846, CVE-2024-44988, CVE-2024-43892,\nCVE-2024-44991, CVE-2024-46806, CVE-2024-41015, CVE-2024-43906,\nCVE-2024-42238, CVE-2024-46779, CVE-2024-41010, CVE-2024-41068,\nCVE-2024-46730, CVE-2024-46827, CVE-2024-42120, CVE-2024-41059,\nCVE-2024-46850, CVE-2023-52889, CVE-2024-45017, CVE-2024-45003,\nCVE-2024-46844, CVE-2024-46816, CVE-2024-46811, CVE-2024-41023,\nCVE-2024-44948, CVE-2024-46753, CVE-2024-45002, CVE-2024-42251,\nCVE-2024-46713, CVE-2024-42273, CVE-2024-46733, CVE-2024-46739,\nCVE-2024-42108, CVE-2024-41085, CVE-2024-41033, CVE-2024-42298,\nCVE-2024-46835, CVE-2024-39472, CVE-2024-47663, CVE-2024-43859,\nCVE-2024-43820, CVE-2024-42118, CVE-2024-41036, CVE-2024-47683,\nCVE-2024-42161, CVE-2024-42235, CVE-2024-43861, CVE-2024-43863,\nCVE-2024-47668, CVE-2024-46685, CVE-2024-43864, CVE-2024-46749,\nCVE-2024-44983, CVE-2024-46841, CVE-2024-42082, CVE-2024-43818,\nCVE-2024-41071, CVE-2024-45006, CVE-2024-42080, CVE-2024-46825,\nCVE-2024-46687, CVE-2024-44959, CVE-2024-43835, CVE-2024-43891,\nCVE-2024-46851, CVE-2024-42248, CVE-2024-42103, CVE-2024-42079,\nCVE-2024-42068, CVE-2024-47664, CVE-2024-46854, CVE-2024-44973,\nCVE-2024-42077, CVE-2024-46821, CVE-2024-43886, CVE-2024-41089,\nCVE-2024-43850, CVE-2024-44995, CVE-2024-46809, CVE-2024-42084,\nCVE-2024-46758, CVE-2024-47662, CVE-2024-43839, CVE-2024-46738,\nCVE-2024-41034, CVE-2024-42228, CVE-2024-42147, CVE-2024-43855,\nCVE-2024-41032, CVE-2024-46819, CVE-2024-44989, CVE-2024-42265,\nCVE-2024-42110, CVE-2024-42155, CVE-2024-45005, CVE-2024-45016,\nCVE-2024-42141, CVE-2024-43821, CVE-2024-42299, CVE-2024-44950,\nCVE-2024-42279, CVE-2024-44943, CVE-2024-43904, CVE-2024-42268,\nCVE-2024-42089, CVE-2024-46807, CVE-2024-44996, CVE-2024-42069,\nCVE-2024-46672, CVE-2024-44940, CVE-2024-42270, CVE-2024-46735,\nCVE-2024-42319, CVE-2024-46754, CVE-2024-46861, CVE-2024-42277,\nCVE-2024-41054, CVE-2024-42131, CVE-2024-41056, CVE-2024-44963,\nCVE-2024-42267, CVE-2024-42283, CVE-2024-42320, CVE-2024-46740,\nCVE-2024-46787, CVE-2024-43895, CVE-2024-43881, CVE-2024-44961,\nCVE-2024-43910, CVE-2024-43875, CVE-2024-42289, CVE-2024-43853,\nCVE-2024-42315, CVE-2024-43884, CVE-2024-46867, CVE-2024-43912,\nCVE-2024-41007, CVE-2024-46743, CVE-2024-46675, CVE-2024-43877,\nCVE-2024-39486, CVE-2024-41050, CVE-2024-43858, CVE-2024-45018,\nCVE-2024-46744, CVE-2024-46750, CVE-2024-46840, CVE-2024-42150,\nCVE-2024-41028, CVE-2024-42091, CVE-2024-43894, CVE-2024-43869,\nCVE-2024-42132, CVE-2024-46777, CVE-2024-42106, CVE-2024-46848,\nCVE-2024-41038, CVE-2024-46711, CVE-2024-43833, CVE-2024-46710,\nCVE-2024-46812, CVE-2024-42311, CVE-2024-46701, CVE-2024-46683,\nCVE-2024-45029, CVE-2024-46830, CVE-2024-46857, CVE-2024-44979,\nCVE-2024-44999, CVE-2024-44985, CVE-2024-46773, CVE-2024-45022,\nCVE-2024-46772, CVE-2024-44960, CVE-2024-42243, CVE-2024-42158,\nCVE-2024-43819, CVE-2024-45030, CVE-2024-42085, CVE-2024-42274,\nCVE-2024-44986, CVE-2024-41048, CVE-2024-42098, CVE-2024-46680,\nCVE-2023-52918, CVE-2024-46673, CVE-2024-46834, CVE-2024-42288,\nCVE-2024-44998, CVE-2024-42113, CVE-2024-42094, CVE-2024-42225,\nCVE-2024-42112, CVE-2024-42153, CVE-2024-43880, CVE-2024-43905,\nCVE-2024-43902, CVE-2024-46681, CVE-2024-42236, CVE-2024-42294,\nCVE-2024-46793, CVE-2024-43882, CVE-2024-44947, CVE-2024-46849,\nCVE-2024-44954, CVE-2024-46852, CVE-2024-41070, CVE-2024-41069,\nCVE-2024-46864, CVE-2024-46703, CVE-2024-43829, CVE-2024-46802,\nCVE-2024-42101, CVE-2024-44990, CVE-2024-43830, CVE-2024-41029,\nCVE-2024-43866, CVE-2024-43889, CVE-2024-42230, CVE-2024-46692,\nCVE-2024-42133, CVE-2024-45013, CVE-2024-42076, CVE-2024-46810,\nCVE-2024-42128, CVE-2024-46718, CVE-2024-46814, CVE-2024-43841,\nCVE-2024-43873, CVE-2024-42092, CVE-2024-41074, CVE-2024-41083,\nCVE-2024-46731, CVE-2024-43842, CVE-2024-41077, CVE-2024-46720,\nCVE-2024-46795, CVE-2024-46813, CVE-2024-46805, CVE-2024-42142,\nCVE-2024-42291, CVE-2024-43846, CVE-2024-41057, CVE-2024-43870,\nCVE-2024-44980, CVE-2024-46866, CVE-2024-43827, CVE-2024-43840,\nCVE-2024-42280, CVE-2024-42261, CVE-2024-42246, CVE-2024-42115,\nCVE-2024-46686, CVE-2024-43860, CVE-2024-46808, CVE-2024-42149,\nCVE-2024-46828, CVE-2024-44935, CVE-2024-43847, CVE-2024-44967,\nCVE-2024-46817, CVE-2024-46721, CVE-2024-42305, CVE-2024-46766,\nCVE-2024-43914, CVE-2024-46760, CVE-2024-41061, CVE-2024-41091,\nCVE-2024-43890, CVE-2024-42314, CVE-2024-42064, CVE-2024-42302,\nCVE-2024-43887, CVE-2024-46832, CVE-2024-46765, CVE-2024-46770,\nCVE-2024-41080, CVE-2024-42253, CVE-2024-44941, CVE-2024-42306,\nCVE-2024-41027, CVE-2024-46689, CVE-2024-46781, CVE-2024-42247,\nCVE-2024-41066, CVE-2024-42287, CVE-2024-41097, CVE-2024-44939,\nCVE-2024-45019, CVE-2024-47674, CVE-2024-46705, CVE-2024-42119,\nCVE-2024-46725, CVE-2024-46746, CVE-2024-46732, CVE-2024-41042,\nCVE-2024-44958, CVE-2024-42114, CVE-2024-43893, CVE-2024-47666,\nCVE-2024-46843, CVE-2024-42252, CVE-2024-42102, CVE-2024-42136,\nCVE-2024-41045, CVE-2024-42260, CVE-2024-46771, CVE-2024-42124,\nCVE-2024-42297, CVE-2024-42271, CVE-2024-43845, CVE-2024-46775,\nCVE-2024-41079, CVE-2024-43868, CVE-2024-42140, CVE-2024-42313,\nCVE-2024-42145, CVE-2024-46724, CVE-2024-46788, CVE-2024-42234,\nCVE-2024-42144, CVE-2024-44974, CVE-2024-42097, CVE-2024-46714,\nCVE-2024-41055, CVE-2024-44956)\n","status":"published","published":"2024-12-12T17:47:44Z","modified":"2026-10-29T20:02:38.448595714Z","updated_at":"2026-11-02T16:58:18.876384Z"}]}}