{"id":"CVE-2024-53232","aliases":["BELL-CVE-2024-53232","DEBIAN-CVE-2024-53232","EUVD-2024-51904","GHSA-c86m-78v8-4hvw","OESA-2026-1759","OESA-2026-1760","OESA-2026-1761","RHBA-2025:6279","RHSA-2025:6966","SUSE-SU-2025:0289-1","SUSE-SU-2025:0428-1","SUSE-SU-2025:0499-1","SUSE-SU-2025:0557-1","SUSE-SU-2025:20165-1","SUSE-SU-2025:20166-1","SUSE-SU-2025:20248-1","SUSE-SU-2025:20249-1","UBUNTU-CVE-2024-53232","USN-7310-1","USN-7449-1","USN-7449-2","USN-7450-1","USN-7451-1","USN-7452-1","USN-7453-1","USN-7468-1","USN-7523-1","USN-7524-1"],"status":"published","title":"iommu/s390: Implement blocking domain","description":"In the Linux kernel, the following vulnerability has been resolved:\n\niommu/s390: Implement blocking domain\n\nThis fixes a crash when surprise hot-unplugging a PCI device. This crash\nhappens because during hot-unplug __iommu_group_set_domain_nofail()\nattaching the default domain fails when the platform no longer\nrecognizes the device as it has already been removed and we end up with\na NULL domain pointer and UAF. This is exactly the case referred to in\nthe second comment in __iommu_device_set_domain() and just as stated\nthere if we can instead attach the blocking domain the UAF is prevented\nas this can handle the already removed device. Implement the blocking\ndomain to use this handling.  With this change, the crash is fixed but\nwe still hit a warning attempting to change DMA ownership on a blocked\ndevice.","severity":{"version":"3.1","score":7.8,"vector":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H","level":"high","assessor":"cna","from":"cve"},"epss":{"day":"2026-11-08","score":0.00232,"percentile":0.14149,"model":"v2026.06.15"},"facts":{"in_kev":false,"known_exploited":false,"public_exploit":false,"fix_available":true},"cwes":["CWE-416","CWE-476"],"published":"2024-12-27T13:50:19Z","modified":"2026-11-03T21:19:53Z","fixes":[{"ecosystem":"Alpaquita:25","package":"linux-lts","fixed_in":["6.12.41-r0"],"sources":["osv"]},{"ecosystem":"Alpaquita:stream","package":"linux-lts","fixed_in":["6.18.35-r1"],"sources":["osv"]},{"ecosystem":"Linux","package":"Kernel","fixed_in":["6.11.11","6.12.2"],"sources":["osv"]},{"ecosystem":"Debian:13","package":"linux","fixed_in":["6.12.3-1"],"sources":["osv"]},{"ecosystem":"Debian:14","package":"linux","fixed_in":["6.12.3-1"],"sources":["osv"]},{"ecosystem":"Ubuntu:22.04:LTS","package":"linux-aws-6.8","fixed_in":["6.8.0-1027.29~22.04.1"],"sources":["osv"]},{"ecosystem":"Ubuntu:22.04:LTS","package":"linux-azure-6.8","fixed_in":["6.8.0-1027.32~22.04.1"],"sources":["osv"]},{"ecosystem":"Ubuntu:22.04:LTS","package":"linux-gcp-6.8","fixed_in":["6.8.0-1028.30~22.04.1"],"sources":["osv"]},{"ecosystem":"Ubuntu:22.04:LTS","package":"linux-hwe-6.8","fixed_in":["6.8.0-58.60~22.04.1"],"sources":["osv"]},{"ecosystem":"Ubuntu:22.04:LTS","package":"linux-ibm-6.8","fixed_in":["6.8.0-1024.24~22.04.1"],"sources":["osv"]},{"ecosystem":"Ubuntu:22.04:LTS","package":"linux-lowlatency-hwe-6.8","fixed_in":["6.8.0-58.60.1~22.04.1"],"sources":["osv"]},{"ecosystem":"Ubuntu:22.04:LTS","package":"linux-nvidia-6.8","fixed_in":["6.8.0-1026.29~22.04.1"],"sources":["osv"]},{"ecosystem":"Ubuntu:22.04:LTS","package":"linux-oracle-6.8","fixed_in":["6.8.0-1024.25~22.04.1"],"sources":["osv"]},{"ecosystem":"Ubuntu:22.04:LTS","package":"linux-riscv-6.8","fixed_in":["6.8.0-58.60.1~22.04.1"],"sources":["osv"]},{"ecosystem":"Ubuntu:Pro:Realtime:22.04:LTS","package":"linux-realtime-6.8","fixed_in":["6.8.1-1020.21~22.04.1"],"sources":["osv"]},{"ecosystem":"Ubuntu:24.04:LTS","package":"linux","fixed_in":["6.8.0-58.60"],"sources":["osv"]},{"ecosystem":"Ubuntu:24.04:LTS","package":"linux-aws","fixed_in":["6.8.0-1027.29"],"sources":["osv"]},{"ecosystem":"Ubuntu:24.04:LTS","package":"linux-azure","fixed_in":["6.8.0-1027.32"],"sources":["osv"]},{"ecosystem":"Ubuntu:24.04:LTS","package":"linux-azure-6.11","fixed_in":["6.11.0-1012.12~24.04.1"],"sources":["osv"]},{"ecosystem":"Ubuntu:24.04:LTS","package":"linux-azure-nvidia","fixed_in":["6.8.0-1014.15"],"sources":["osv"]},{"ecosystem":"Ubuntu:24.04:LTS","package":"linux-gcp","fixed_in":["6.8.0-1028.30"],"sources":["osv"]},{"ecosystem":"Ubuntu:24.04:LTS","package":"linux-gcp-6.11","fixed_in":["6.11.0-1011.11~24.04.1"],"sources":["osv"]},{"ecosystem":"Ubuntu:24.04:LTS","package":"linux-gke","fixed_in":["6.8.0-1023.27"],"sources":["osv"]},{"ecosystem":"Ubuntu:24.04:LTS","package":"linux-gkeop","fixed_in":["6.8.0-1010.12"],"sources":["osv"]},{"ecosystem":"Ubuntu:24.04:LTS","package":"linux-ibm","fixed_in":["6.8.0-1024.24"],"sources":["osv"]},{"ecosystem":"Ubuntu:24.04:LTS","package":"linux-lowlatency","fixed_in":["6.8.0-58.60.1"],"sources":["osv"]},{"ecosystem":"Ubuntu:24.04:LTS","package":"linux-nvidia","fixed_in":["6.8.0-1026.29"],"sources":["osv"]},{"ecosystem":"Ubuntu:24.04:LTS","package":"linux-nvidia-6.11","fixed_in":["6.11.0-1007.7"],"sources":["osv"]},{"ecosystem":"Ubuntu:24.04:LTS","package":"linux-nvidia-lowlatency","fixed_in":["6.8.0-1026.29.1"],"sources":["osv"]},{"ecosystem":"Ubuntu:24.04:LTS","package":"linux-nvidia-tegra","fixed_in":["6.8.0-1008.8"],"sources":["osv"]},{"ecosystem":"Ubuntu:24.04:LTS","package":"linux-oem-6.11","fixed_in":["6.11.0-1015.15"],"sources":["osv"]},{"ecosystem":"Ubuntu:24.04:LTS","package":"linux-oem-6.8","fixed_in":["6.8.0-1026.26"],"sources":["osv"]},{"ecosystem":"Ubuntu:24.04:LTS","package":"linux-oracle","fixed_in":["6.8.0-1024.25"],"sources":["osv"]},{"ecosystem":"Ubuntu:24.04:LTS","package":"linux-raspi","fixed_in":["6.8.0-1028.32"],"sources":["osv"]},{"ecosystem":"Ubuntu:24.04:LTS","package":"linux-riscv","fixed_in":["6.8.0-58.60.1"],"sources":["osv"]},{"ecosystem":"Ubuntu:24.04:LTS","package":"linux-xilinx","fixed_in":["6.8.0-1017.18"],"sources":["osv"]},{"ecosystem":"Ubuntu:Pro:Realtime:24.04:LTS","package":"linux-raspi-realtime","fixed_in":["6.8.0-2023.24"],"sources":["osv"]},{"ecosystem":"Ubuntu:Pro:Realtime:24.04:LTS","package":"linux-realtime","fixed_in":["6.8.1-1020.21"],"sources":["osv"]},{"ecosystem":"Ubuntu:Pro:FIPS-updates:24.04:LTS","package":"linux-fips","fixed_in":["6.8.0-78.78+fips1"],"sources":["osv"]}],"affected":[{"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.12.92-r1"},{"fixed":"6.18.35-r1"}]}]},{"source":"osv","ecosystem":"Linux","package":"Kernel","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"6.7.0"},{"fixed":"6.11.11"}]},{"type":"ECOSYSTEM","events":[{"introduced":"6.12.0"},{"fixed":"6.12.2"}]}]},{"source":"osv","ecosystem":"Debian:13","package":"linux","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.12.3-1"}]}]},{"source":"osv","ecosystem":"Debian:14","package":"linux","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.12.3-1"}]}]},{"source":"osv","ecosystem":"openEuler:24.03-LTS","package":"kernel","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.6.0-144.0.0.127.oe2403"}]}],"bundled":85},{"source":"osv","ecosystem":"openEuler:24.03-LTS-SP1","package":"kernel","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.6.0-144.0.0.139.oe2403sp1"}]}],"bundled":122},{"source":"osv","ecosystem":"openEuler:24.03-LTS-SP2","package":"kernel","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.6.0-144.0.0.140.oe2403sp2"}]}],"bundled":85},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:10.0","package":"kernel-64k-debug-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:6.12.0-55.9.1.el10_0"}]}],"bundled":2},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:10.0","package":"kernel-64k-debug-devel","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:6.12.0-55.9.1.el10_0"}]}],"bundled":2},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:10.0","package":"kernel-64k-debug-devel-matched","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:6.12.0-55.9.1.el10_0"}]}],"bundled":2},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:10.0","package":"kernel-64k-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:6.12.0-55.9.1.el10_0"}]}],"bundled":2},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:10.0","package":"kernel-64k-devel","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:6.12.0-55.9.1.el10_0"}]}],"bundled":2},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:10.0","package":"kernel-64k-devel-matched","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:6.12.0-55.9.1.el10_0"}]}],"bundled":2},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:10.0","package":"kernel-debug-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:6.12.0-55.9.1.el10_0"}]}],"bundled":2},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:10.0","package":"kernel-debug-devel","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:6.12.0-55.9.1.el10_0"}]}],"bundled":2},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:10.0","package":"kernel-debug-devel-matched","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:6.12.0-55.9.1.el10_0"}]}],"bundled":2},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:10.0","package":"kernel-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:6.12.0-55.9.1.el10_0"}]}],"bundled":2},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:10.0","package":"kernel-debuginfo-common-aarch64","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:6.12.0-55.9.1.el10_0"}]}],"bundled":2},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:10.0","package":"kernel-debuginfo-common-ppc64le","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:6.12.0-55.9.1.el10_0"}]}],"bundled":2},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:10.0","package":"kernel-debuginfo-common-s390x","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:6.12.0-55.9.1.el10_0"}]}],"bundled":2},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:10.0","package":"kernel-debuginfo-common-x86_64","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:6.12.0-55.9.1.el10_0"}]}],"bundled":2},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:10.0","package":"kernel-devel","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:6.12.0-55.9.1.el10_0"}]}],"bundled":2},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:10.0","package":"kernel-devel-matched","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:6.12.0-55.9.1.el10_0"}]}],"bundled":2},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:10.0","package":"kernel-doc","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:6.12.0-55.9.1.el10_0"}]}],"bundled":2},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:10.0","package":"kernel-rt-64k-debug-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:6.12.0-55.9.1.el10_0"}]}],"bundled":2},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:10.0","package":"kernel-rt-64k-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:6.12.0-55.9.1.el10_0"}]}],"bundled":2},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:10.0","package":"kernel-rt-debug-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:6.12.0-55.9.1.el10_0"}]}],"bundled":2},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:10.0","package":"kernel-rt-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:6.12.0-55.9.1.el10_0"}]}],"bundled":2},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:10.0","package":"kernel-tools-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:6.12.0-55.9.1.el10_0"}]}],"bundled":2},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:10.0","package":"kernel-zfcpdump-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:6.12.0-55.9.1.el10_0"}]}],"bundled":2},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:10.0","package":"kernel-zfcpdump-devel","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:6.12.0-55.9.1.el10_0"}]}],"bundled":2},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:10.0","package":"kernel-zfcpdump-devel-matched","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:6.12.0-55.9.1.el10_0"}]}],"bundled":2},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:10.0","package":"libperf-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:6.12.0-55.9.1.el10_0"}]}],"bundled":2},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:10.0","package":"perf","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:6.12.0-55.9.1.el10_0"}]}],"bundled":2},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:10.0","package":"perf-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:6.12.0-55.9.1.el10_0"}]}],"bundled":2},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:10.0","package":"python3-perf","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:6.12.0-55.9.1.el10_0"}]}],"bundled":2},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:10.0","package":"python3-perf-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:6.12.0-55.9.1.el10_0"}]}],"bundled":2},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:10.0","package":"rtla","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:6.12.0-55.9.1.el10_0"}]}],"bundled":2},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:10.0","package":"rv","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:6.12.0-55.9.1.el10_0"}]}],"bundled":2},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:10.0","package":"kernel","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:6.12.0-55.9.1.el10_0"}]}],"bundled":2},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:10.0","package":"kernel-64k","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:6.12.0-55.9.1.el10_0"}]}],"bundled":2},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:10.0","package":"kernel-64k-core","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:6.12.0-55.9.1.el10_0"}]}],"bundled":2},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:10.0","package":"kernel-64k-debug","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:6.12.0-55.9.1.el10_0"}]}],"bundled":2},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:10.0","package":"kernel-64k-debug-core","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:6.12.0-55.9.1.el10_0"}]}],"bundled":2},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:10.0","package":"kernel-64k-debug-modules","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:6.12.0-55.9.1.el10_0"}]}],"bundled":2},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:10.0","package":"kernel-64k-debug-modules-core","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:6.12.0-55.9.1.el10_0"}]}],"bundled":2},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:10.0","package":"kernel-64k-debug-modules-extra","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:6.12.0-55.9.1.el10_0"}]}],"bundled":2},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:10.0","package":"kernel-64k-modules","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:6.12.0-55.9.1.el10_0"}]}],"bundled":2},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:10.0","package":"kernel-64k-modules-core","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:6.12.0-55.9.1.el10_0"}]}],"bundled":2},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:10.0","package":"kernel-64k-modules-extra","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:6.12.0-55.9.1.el10_0"}]}],"bundled":2},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:10.0","package":"kernel-abi-stablelists","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:6.12.0-55.9.1.el10_0"}]}],"bundled":2},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:10.0","package":"kernel-core","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:6.12.0-55.9.1.el10_0"}]}],"bundled":2},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:10.0","package":"kernel-debug","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:6.12.0-55.9.1.el10_0"}]}],"bundled":2},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:10.0","package":"kernel-debug-core","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:6.12.0-55.9.1.el10_0"}]}],"bundled":2},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:10.0","package":"kernel-debug-modules","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:6.12.0-55.9.1.el10_0"}]}],"bundled":2},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:10.0","package":"kernel-debug-modules-core","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:6.12.0-55.9.1.el10_0"}]}],"bundled":2},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:10.0","package":"kernel-debug-modules-extra","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:6.12.0-55.9.1.el10_0"}]}],"bundled":2},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:10.0","package":"kernel-debug-uki-virt","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:6.12.0-55.9.1.el10_0"}]}],"bundled":2},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:10.0","package":"kernel-modules","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:6.12.0-55.9.1.el10_0"}]}],"bundled":2},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:10.0","package":"kernel-modules-core","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:6.12.0-55.9.1.el10_0"}]}],"bundled":2},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:10.0","package":"kernel-modules-extra","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:6.12.0-55.9.1.el10_0"}]}],"bundled":2},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:10.0","package":"kernel-tools","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:6.12.0-55.9.1.el10_0"}]}],"bundled":2},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:10.0","package":"kernel-tools-libs","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:6.12.0-55.9.1.el10_0"}]}],"bundled":2},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:10.0","package":"kernel-uki-virt","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:6.12.0-55.9.1.el10_0"}]}],"bundled":2},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:10.0","package":"kernel-uki-virt-addons","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:6.12.0-55.9.1.el10_0"}]}],"bundled":2},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:10.0","package":"kernel-zfcpdump","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:6.12.0-55.9.1.el10_0"}]}],"bundled":2},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:10.0","package":"kernel-zfcpdump-core","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:6.12.0-55.9.1.el10_0"}]}],"bundled":2},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:10.0","package":"kernel-zfcpdump-modules","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:6.12.0-55.9.1.el10_0"}]}],"bundled":2},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:10.0","package":"kernel-zfcpdump-modules-core","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:6.12.0-55.9.1.el10_0"}]}],"bundled":2},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:10.0","package":"kernel-zfcpdump-modules-extra","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:6.12.0-55.9.1.el10_0"}]}],"bundled":2},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:10.0","package":"kernel-tools-libs-devel","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:6.12.0-55.9.1.el10_0"}]}],"bundled":2},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:10.0","package":"libperf","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:6.12.0-55.9.1.el10_0"}]}],"bundled":2},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:10.0","package":"kernel-rt","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:6.12.0-55.9.1.el10_0"}]}],"bundled":2},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:10.0","package":"kernel-rt-core","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:6.12.0-55.9.1.el10_0"}]}],"bundled":2},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:10.0","package":"kernel-rt-debug","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:6.12.0-55.9.1.el10_0"}]}],"bundled":2},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:10.0","package":"kernel-rt-debug-core","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:6.12.0-55.9.1.el10_0"}]}],"bundled":2},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:10.0","package":"kernel-rt-debug-devel","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:6.12.0-55.9.1.el10_0"}]}],"bundled":2},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:10.0","package":"kernel-rt-debug-kvm","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:6.12.0-55.9.1.el10_0"}]}],"bundled":2},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:10.0","package":"kernel-rt-debug-modules","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:6.12.0-55.9.1.el10_0"}]}],"bundled":2},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:10.0","package":"kernel-rt-debug-modules-core","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:6.12.0-55.9.1.el10_0"}]}],"bundled":2},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:10.0","package":"kernel-rt-debug-modules-extra","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:6.12.0-55.9.1.el10_0"}]}],"bundled":2},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:10.0","package":"kernel-rt-devel","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:6.12.0-55.9.1.el10_0"}]}],"bundled":2},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:10.0","package":"kernel-rt-kvm","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:6.12.0-55.9.1.el10_0"}]}],"bundled":2},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:10.0","package":"kernel-rt-modules","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:6.12.0-55.9.1.el10_0"}]}],"bundled":2},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:10.0","package":"kernel-rt-modules-core","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:6.12.0-55.9.1.el10_0"}]}],"bundled":2},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:10.0","package":"kernel-rt-modules-extra","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:6.12.0-55.9.1.el10_0"}]}],"bundled":2},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:10.0","package":"kernel-rt-64k","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:6.12.0-55.9.1.el10_0"}]}],"bundled":2},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:10.0","package":"kernel-rt-64k-core","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:6.12.0-55.9.1.el10_0"}]}],"bundled":2},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:10.0","package":"kernel-rt-64k-debug","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:6.12.0-55.9.1.el10_0"}]}],"bundled":2},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:10.0","package":"kernel-rt-64k-debug-core","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:6.12.0-55.9.1.el10_0"}]}],"bundled":2},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:10.0","package":"kernel-rt-64k-debug-devel","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:6.12.0-55.9.1.el10_0"}]}],"bundled":2},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:10.0","package":"kernel-rt-64k-debug-modules","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:6.12.0-55.9.1.el10_0"}]}],"bundled":2},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:10.0","package":"kernel-rt-64k-debug-modules-core","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:6.12.0-55.9.1.el10_0"}]}],"bundled":2},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:10.0","package":"kernel-rt-64k-debug-modules-extra","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:6.12.0-55.9.1.el10_0"}]}],"bundled":2},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:10.0","package":"kernel-rt-64k-devel","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:6.12.0-55.9.1.el10_0"}]}],"bundled":2},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:10.0","package":"kernel-rt-64k-modules","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:6.12.0-55.9.1.el10_0"}]}],"bundled":2},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:10.0","package":"kernel-rt-64k-modules-core","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:6.12.0-55.9.1.el10_0"}]}],"bundled":2},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:10.0","package":"kernel-rt-64k-modules-extra","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:6.12.0-55.9.1.el10_0"}]}],"bundled":2},{"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-570.12.1.el9_6"}]}],"bundled":406},{"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-570.12.1.el9_6"}]}],"bundled":406},{"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-570.12.1.el9_6"}]}],"bundled":406},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::appstream","package":"kernel-64k-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-570.12.1.el9_6"}]}],"bundled":406},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::appstream","package":"kernel-64k-devel","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-570.12.1.el9_6"}]}],"bundled":406},{"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-570.12.1.el9_6"}]}],"bundled":406},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::appstream","package":"kernel-debug-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-570.12.1.el9_6"}]}],"bundled":406},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::appstream","package":"kernel-debug-devel","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-570.12.1.el9_6"}]}],"bundled":406},{"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-570.12.1.el9_6"}]}],"bundled":406},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::appstream","package":"kernel-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-570.12.1.el9_6"}]}],"bundled":406},{"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-570.12.1.el9_6"}]}],"bundled":406},{"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-570.12.1.el9_6"}]}],"bundled":406},{"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-570.12.1.el9_6"}]}],"bundled":406},{"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-570.12.1.el9_6"}]}],"bundled":406},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::appstream","package":"kernel-devel","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-570.12.1.el9_6"}]}],"bundled":406},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::appstream","package":"kernel-devel-matched","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-570.12.1.el9_6"}]}],"bundled":406},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::appstream","package":"kernel-doc","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-570.12.1.el9_6"}]}],"bundled":406},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::appstream","package":"kernel-rt-64k-debug-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-570.12.1.el9_6"}]}],"bundled":406},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::appstream","package":"kernel-rt-64k-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-570.12.1.el9_6"}]}],"bundled":406},{"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-570.12.1.el9_6"}]}],"bundled":406},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::appstream","package":"kernel-rt-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-570.12.1.el9_6"}]}],"bundled":406},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::appstream","package":"kernel-tools-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-570.12.1.el9_6"}]}],"bundled":406},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::appstream","package":"kernel-zfcpdump-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-570.12.1.el9_6"}]}],"bundled":406},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::appstream","package":"kernel-zfcpdump-devel","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-570.12.1.el9_6"}]}],"bundled":406},{"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-570.12.1.el9_6"}]}],"bundled":406},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::appstream","package":"libperf-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-570.12.1.el9_6"}]}],"bundled":406},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::appstream","package":"perf","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-570.12.1.el9_6"}]}],"bundled":406},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::appstream","package":"perf-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-570.12.1.el9_6"}]}],"bundled":406},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::appstream","package":"python3-perf","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-570.12.1.el9_6"}]}],"bundled":406},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::appstream","package":"python3-perf-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-570.12.1.el9_6"}]}],"bundled":406},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::appstream","package":"rtla","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-570.12.1.el9_6"}]}],"bundled":406},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::appstream","package":"rv","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-570.12.1.el9_6"}]}],"bundled":406},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::baseos","package":"kernel","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-570.12.1.el9_6"}]}],"bundled":406},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::baseos","package":"kernel-64k","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-570.12.1.el9_6"}]}],"bundled":406},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::baseos","package":"kernel-64k-core","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-570.12.1.el9_6"}]}],"bundled":406},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::baseos","package":"kernel-64k-debug","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-570.12.1.el9_6"}]}],"bundled":406},{"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-570.12.1.el9_6"}]}],"bundled":406},{"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-570.12.1.el9_6"}]}],"bundled":406},{"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-570.12.1.el9_6"}]}],"bundled":406},{"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-570.12.1.el9_6"}]}],"bundled":406},{"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-570.12.1.el9_6"}]}],"bundled":406},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::baseos","package":"kernel-64k-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-570.12.1.el9_6"}]}],"bundled":406},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::baseos","package":"kernel-64k-modules","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-570.12.1.el9_6"}]}],"bundled":406},{"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-570.12.1.el9_6"}]}],"bundled":406},{"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-570.12.1.el9_6"}]}],"bundled":406},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::baseos","package":"kernel-abi-stablelists","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-570.12.1.el9_6"}]}],"bundled":406},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::baseos","package":"kernel-core","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-570.12.1.el9_6"}]}],"bundled":406},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::baseos","package":"kernel-debug","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-570.12.1.el9_6"}]}],"bundled":406},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::baseos","package":"kernel-debug-core","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-570.12.1.el9_6"}]}],"bundled":406},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::baseos","package":"kernel-debug-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-570.12.1.el9_6"}]}],"bundled":406},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::baseos","package":"kernel-debug-modules","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-570.12.1.el9_6"}]}],"bundled":406},{"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-570.12.1.el9_6"}]}],"bundled":406},{"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-570.12.1.el9_6"}]}],"bundled":406},{"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-570.12.1.el9_6"}]}],"bundled":406},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::baseos","package":"kernel-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-570.12.1.el9_6"}]}],"bundled":406},{"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-570.12.1.el9_6"}]}],"bundled":406},{"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-570.12.1.el9_6"}]}],"bundled":406},{"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-570.12.1.el9_6"}]}],"bundled":406},{"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-570.12.1.el9_6"}]}],"bundled":406},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::baseos","package":"kernel-modules","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-570.12.1.el9_6"}]}],"bundled":406},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::baseos","package":"kernel-modules-core","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-570.12.1.el9_6"}]}],"bundled":406},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::baseos","package":"kernel-modules-extra","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-570.12.1.el9_6"}]}],"bundled":406},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::baseos","package":"kernel-rt-64k-debug-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-570.12.1.el9_6"}]}],"bundled":406},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::baseos","package":"kernel-rt-64k-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-570.12.1.el9_6"}]}],"bundled":406},{"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-570.12.1.el9_6"}]}],"bundled":406},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::baseos","package":"kernel-rt-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-570.12.1.el9_6"}]}],"bundled":406},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::baseos","package":"kernel-tools","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-570.12.1.el9_6"}]}],"bundled":406},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::baseos","package":"kernel-tools-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-570.12.1.el9_6"}]}],"bundled":406},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::baseos","package":"kernel-tools-libs","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-570.12.1.el9_6"}]}],"bundled":406},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::baseos","package":"kernel-uki-virt","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-570.12.1.el9_6"}]}],"bundled":406},{"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-570.12.1.el9_6"}]}],"bundled":406},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::baseos","package":"kernel-zfcpdump","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-570.12.1.el9_6"}]}],"bundled":406},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::baseos","package":"kernel-zfcpdump-core","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-570.12.1.el9_6"}]}],"bundled":406},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::baseos","package":"kernel-zfcpdump-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-570.12.1.el9_6"}]}],"bundled":406},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::baseos","package":"kernel-zfcpdump-modules","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-570.12.1.el9_6"}]}],"bundled":406},{"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-570.12.1.el9_6"}]}],"bundled":406},{"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-570.12.1.el9_6"}]}],"bundled":406},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::baseos","package":"libperf-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-570.12.1.el9_6"}]}],"bundled":406},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::baseos","package":"perf-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-570.12.1.el9_6"}]}],"bundled":406},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::baseos","package":"python3-perf-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-570.12.1.el9_6"}]}],"bundled":406},{"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-570.12.1.el9_6"}]}],"bundled":406},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::crb","package":"kernel-64k-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-570.12.1.el9_6"}]}],"bundled":406},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::crb","package":"kernel-debug-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-570.12.1.el9_6"}]}],"bundled":406},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::crb","package":"kernel-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-570.12.1.el9_6"}]}],"bundled":406},{"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-570.12.1.el9_6"}]}],"bundled":406},{"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-570.12.1.el9_6"}]}],"bundled":406},{"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-570.12.1.el9_6"}]}],"bundled":406},{"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-570.12.1.el9_6"}]}],"bundled":406},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::crb","package":"kernel-rt-64k-debug-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-570.12.1.el9_6"}]}],"bundled":406},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::crb","package":"kernel-rt-64k-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-570.12.1.el9_6"}]}],"bundled":406},{"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-570.12.1.el9_6"}]}],"bundled":406},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::crb","package":"kernel-rt-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-570.12.1.el9_6"}]}],"bundled":406},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::crb","package":"kernel-tools-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-570.12.1.el9_6"}]}],"bundled":406},{"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-570.12.1.el9_6"}]}],"bundled":406},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::crb","package":"kernel-zfcpdump-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-570.12.1.el9_6"}]}],"bundled":406},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::crb","package":"libperf","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-570.12.1.el9_6"}]}],"bundled":406},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::crb","package":"libperf-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-570.12.1.el9_6"}]}],"bundled":406},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::crb","package":"perf-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-570.12.1.el9_6"}]}],"bundled":406},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::crb","package":"python3-perf-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-570.12.1.el9_6"}]}],"bundled":406},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::nfv","package":"kernel-debug-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-570.12.1.el9_6"}]}],"bundled":406},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::nfv","package":"kernel-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-570.12.1.el9_6"}]}],"bundled":406},{"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-570.12.1.el9_6"}]}],"bundled":406},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::nfv","package":"kernel-rt","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-570.12.1.el9_6"}]}],"bundled":406},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::nfv","package":"kernel-rt-core","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-570.12.1.el9_6"}]}],"bundled":406},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::nfv","package":"kernel-rt-debug","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-570.12.1.el9_6"}]}],"bundled":406},{"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-570.12.1.el9_6"}]}],"bundled":406},{"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-570.12.1.el9_6"}]}],"bundled":406},{"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-570.12.1.el9_6"}]}],"bundled":406},{"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-570.12.1.el9_6"}]}],"bundled":406},{"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-570.12.1.el9_6"}]}],"bundled":406},{"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-570.12.1.el9_6"}]}],"bundled":406},{"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-570.12.1.el9_6"}]}],"bundled":406},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::nfv","package":"kernel-rt-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-570.12.1.el9_6"}]}],"bundled":406},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::nfv","package":"kernel-rt-devel","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-570.12.1.el9_6"}]}],"bundled":406},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::nfv","package":"kernel-rt-kvm","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-570.12.1.el9_6"}]}],"bundled":406},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::nfv","package":"kernel-rt-modules","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-570.12.1.el9_6"}]}],"bundled":406},{"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-570.12.1.el9_6"}]}],"bundled":406},{"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-570.12.1.el9_6"}]}],"bundled":406},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::nfv","package":"kernel-tools-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-570.12.1.el9_6"}]}],"bundled":406},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::nfv","package":"libperf-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-570.12.1.el9_6"}]}],"bundled":406},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::nfv","package":"perf-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-570.12.1.el9_6"}]}],"bundled":406},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::nfv","package":"python3-perf-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-570.12.1.el9_6"}]}],"bundled":406},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::realtime","package":"kernel-64k-debug-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-570.12.1.el9_6"}]}],"bundled":406},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::realtime","package":"kernel-64k-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-570.12.1.el9_6"}]}],"bundled":406},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::realtime","package":"kernel-debug-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-570.12.1.el9_6"}]}],"bundled":406},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::realtime","package":"kernel-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-570.12.1.el9_6"}]}],"bundled":406},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::realtime","package":"kernel-debuginfo-common-aarch64","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-570.12.1.el9_6"}]}],"bundled":406},{"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-570.12.1.el9_6"}]}],"bundled":406},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::realtime","package":"kernel-rt","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-570.12.1.el9_6"}]}],"bundled":406},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::realtime","package":"kernel-rt-64k","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-570.12.1.el9_6"}]}],"bundled":406},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::realtime","package":"kernel-rt-64k-core","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-570.12.1.el9_6"}]}],"bundled":406},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::realtime","package":"kernel-rt-64k-debug","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-570.12.1.el9_6"}]}],"bundled":406},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::realtime","package":"kernel-rt-64k-debug-core","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-570.12.1.el9_6"}]}],"bundled":406},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::realtime","package":"kernel-rt-64k-debug-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-570.12.1.el9_6"}]}],"bundled":406},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::realtime","package":"kernel-rt-64k-debug-devel","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-570.12.1.el9_6"}]}],"bundled":406},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::realtime","package":"kernel-rt-64k-debug-modules","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-570.12.1.el9_6"}]}],"bundled":406},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::realtime","package":"kernel-rt-64k-debug-modules-core","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-570.12.1.el9_6"}]}],"bundled":406},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::realtime","package":"kernel-rt-64k-debug-modules-extra","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-570.12.1.el9_6"}]}],"bundled":406},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::realtime","package":"kernel-rt-64k-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-570.12.1.el9_6"}]}],"bundled":406},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::realtime","package":"kernel-rt-64k-devel","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-570.12.1.el9_6"}]}],"bundled":406},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::realtime","package":"kernel-rt-64k-modules","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-570.12.1.el9_6"}]}],"bundled":406},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::realtime","package":"kernel-rt-64k-modules-core","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-570.12.1.el9_6"}]}],"bundled":406},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::realtime","package":"kernel-rt-64k-modules-extra","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-570.12.1.el9_6"}]}],"bundled":406},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::realtime","package":"kernel-rt-core","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-570.12.1.el9_6"}]}],"bundled":406},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::realtime","package":"kernel-rt-debug","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-570.12.1.el9_6"}]}],"bundled":406},{"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-570.12.1.el9_6"}]}],"bundled":406},{"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-570.12.1.el9_6"}]}],"bundled":406},{"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-570.12.1.el9_6"}]}],"bundled":406},{"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-570.12.1.el9_6"}]}],"bundled":406},{"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-570.12.1.el9_6"}]}],"bundled":406},{"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-570.12.1.el9_6"}]}],"bundled":406},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::realtime","package":"kernel-rt-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-570.12.1.el9_6"}]}],"bundled":406},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::realtime","package":"kernel-rt-devel","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-570.12.1.el9_6"}]}],"bundled":406},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::realtime","package":"kernel-rt-modules","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-570.12.1.el9_6"}]}],"bundled":406},{"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-570.12.1.el9_6"}]}],"bundled":406},{"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-570.12.1.el9_6"}]}],"bundled":406},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::realtime","package":"kernel-tools-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-570.12.1.el9_6"}]}],"bundled":406},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::realtime","package":"libperf-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-570.12.1.el9_6"}]}],"bundled":406},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::realtime","package":"perf-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-570.12.1.el9_6"}]}],"bundled":406},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::realtime","package":"python3-perf-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-570.12.1.el9_6"}]}],"bundled":406},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Module for Confidential Computing Technical Preview 15 SP6","package":"kernel-coco","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.4.0-15061.12.coco15sp6.1"}]}],"bundled":343},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Module for Confidential Computing Technical Preview 15 SP6","package":"kernel-coco_debug","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.4.0-15061.12.coco15sp6.1"}]}],"bundled":343},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Module for Confidential Computing Technical Preview 15 SP6","package":"kernel-source-coco","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.4.0-15061.12.coco15sp6.1"}]}],"bundled":343},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Module for Confidential Computing Technical Preview 15 SP6","package":"kernel-syms-coco","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.4.0-15061.12.coco15sp6.1"}]}],"bundled":343},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Module for Public Cloud 15 SP6","package":"kernel-azure","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.4.0-150600.8.26.1"}]}],"bundled":248},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Module for Public Cloud 15 SP6","package":"kernel-source-azure","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.4.0-150600.8.26.1"}]}],"bundled":248},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Module for Public Cloud 15 SP6","package":"kernel-syms-azure","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.4.0-150600.8.26.1"}]}],"bundled":248},{"source":"osv","ecosystem":"openSUSE:Leap 15.6","package":"kernel-azure","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.4.0-150600.8.26.1"}]}],"bundled":248},{"source":"osv","ecosystem":"openSUSE:Leap 15.6","package":"kernel-source-azure","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.4.0-150600.8.26.1"}]}],"bundled":248},{"source":"osv","ecosystem":"openSUSE:Leap 15.6","package":"kernel-syms-azure","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.4.0-150600.8.26.1"}]}],"bundled":248},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Module for Basesystem 15 SP6","package":"kernel-64kb","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.4.0-150600.23.38.1"}]}],"bundled":257},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Module for Basesystem 15 SP6","package":"kernel-default","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.4.0-150600.23.38.1"}]}],"bundled":257},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Module for Basesystem 15 SP6","package":"kernel-default-base","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.4.0-150600.23.38.1.150600.12.16.2"}]}],"bundled":257},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Module for Basesystem 15 SP6","package":"kernel-source","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.4.0-150600.23.38.1"}]}],"bundled":257},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Module for Basesystem 15 SP6","package":"kernel-zfcpdump","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.4.0-150600.23.38.1"}]}],"bundled":257},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Module for Development Tools 15 SP6","package":"kernel-docs","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.4.0-150600.23.38.1"}]}],"bundled":257},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Module for Development Tools 15 SP6","package":"kernel-obs-build","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.4.0-150600.23.38.1"}]}],"bundled":257},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Module for Development Tools 15 SP6","package":"kernel-source","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.4.0-150600.23.38.1"}]}],"bundled":257},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Module for Development Tools 15 SP6","package":"kernel-syms","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.4.0-150600.23.38.1"}]}],"bundled":257},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Module for Legacy 15 SP6","package":"kernel-default","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.4.0-150600.23.38.1"}]}],"bundled":257},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Live Patching 15 SP6","package":"kernel-default","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.4.0-150600.23.38.1"}]}],"bundled":257},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Live Patching 15 SP6","package":"kernel-livepatch-SLE15-SP6_Update_8","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1-150600.13.3.2"}]}],"bundled":257},{"source":"osv","ecosystem":"SUSE:Linux Enterprise High Availability Extension 15 SP6","package":"kernel-default","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.4.0-150600.23.38.1"}]}],"bundled":257},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Workstation Extension 15 SP6","package":"kernel-default","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.4.0-150600.23.38.1"}]}],"bundled":257},{"source":"osv","ecosystem":"openSUSE:Leap 15.6","package":"dtb-aarch64","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.4.0-150600.23.38.1"}]}],"bundled":257},{"source":"osv","ecosystem":"openSUSE:Leap 15.6","package":"kernel-64kb","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.4.0-150600.23.38.1"}]}],"bundled":257},{"source":"osv","ecosystem":"openSUSE:Leap 15.6","package":"kernel-debug","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.4.0-150600.23.38.1"}]}],"bundled":257},{"source":"osv","ecosystem":"openSUSE:Leap 15.6","package":"kernel-default","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.4.0-150600.23.38.1"}]}],"bundled":257},{"source":"osv","ecosystem":"openSUSE:Leap 15.6","package":"kernel-default-base","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.4.0-150600.23.38.1.150600.12.16.2"}]}],"bundled":257},{"source":"osv","ecosystem":"openSUSE:Leap 15.6","package":"kernel-docs","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.4.0-150600.23.38.1"}]}],"bundled":257},{"source":"osv","ecosystem":"openSUSE:Leap 15.6","package":"kernel-kvmsmall","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.4.0-150600.23.38.1"}]}],"bundled":257},{"source":"osv","ecosystem":"openSUSE:Leap 15.6","package":"kernel-obs-build","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.4.0-150600.23.38.1"}]}],"bundled":257},{"source":"osv","ecosystem":"openSUSE:Leap 15.6","package":"kernel-obs-qa","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.4.0-150600.23.38.1"}]}],"bundled":257},{"source":"osv","ecosystem":"openSUSE:Leap 15.6","package":"kernel-source","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.4.0-150600.23.38.1"}]}],"bundled":257},{"source":"osv","ecosystem":"openSUSE:Leap 15.6","package":"kernel-syms","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.4.0-150600.23.38.1"}]}],"bundled":257},{"source":"osv","ecosystem":"openSUSE:Leap 15.6","package":"kernel-zfcpdump","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.4.0-150600.23.38.1"}]}],"bundled":257},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Live Patching 15 SP6","package":"kernel-livepatch-SLE15-SP6-RT_Update_8","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1-150600.1.3.1"}]}],"bundled":256},{"source":"osv","ecosystem":"SUSE:Real Time Module 15 SP6","package":"kernel-rt","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.4.0-150600.10.26.1"}]}],"bundled":256},{"source":"osv","ecosystem":"SUSE:Real Time Module 15 SP6","package":"kernel-rt_debug","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.4.0-150600.10.26.1"}]}],"bundled":256},{"source":"osv","ecosystem":"SUSE:Real Time Module 15 SP6","package":"kernel-source-rt","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.4.0-150600.10.26.1"}]}],"bundled":256},{"source":"osv","ecosystem":"SUSE:Real Time Module 15 SP6","package":"kernel-syms-rt","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.4.0-150600.10.26.1"}]}],"bundled":256},{"source":"osv","ecosystem":"openSUSE:Leap 15.6","package":"kernel-rt","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.4.0-150600.10.26.1"}]}],"bundled":256},{"source":"osv","ecosystem":"openSUSE:Leap 15.6","package":"kernel-rt_debug","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.4.0-150600.10.26.1"}]}],"bundled":256},{"source":"osv","ecosystem":"openSUSE:Leap 15.6","package":"kernel-source-rt","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.4.0-150600.10.26.1"}]}],"bundled":256},{"source":"osv","ecosystem":"openSUSE:Leap 15.6","package":"kernel-syms-rt","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.4.0-150600.10.26.1"}]}],"bundled":256},{"source":"osv","ecosystem":"SUSE:Linux Micro 6.0","package":"kernel-default","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.4.0-25.1"}]}],"bundled":357},{"source":"osv","ecosystem":"SUSE:Linux Micro 6.0","package":"kernel-default-base","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.4.0-24.1.21.4"}]}],"bundled":357},{"source":"osv","ecosystem":"SUSE:Linux Micro 6.0","package":"kernel-kvmsmall","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.4.0-25.1"}]}],"bundled":357},{"source":"osv","ecosystem":"SUSE:Linux Micro 6.0","package":"kernel-livepatch-MICRO-6-0_Update_5","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1-1.2"}]}],"bundled":357},{"source":"osv","ecosystem":"SUSE:Linux Micro 6.0","package":"kernel-source","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.4.0-25.1"}]}],"bundled":357},{"source":"osv","ecosystem":"SUSE:Linux Micro 6.0","package":"kernel-livepatch-MICRO-6-0-RT_Update_5","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1-1.1"}]}],"bundled":610},{"source":"osv","ecosystem":"SUSE:Linux Micro 6.0","package":"kernel-rt","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.4.0-25.1"}]}],"bundled":610},{"source":"osv","ecosystem":"SUSE:Linux Micro 6.0","package":"kernel-source-rt","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.4.0-25.1"}]}],"bundled":610},{"source":"osv","ecosystem":"SUSE:Linux Micro 6.1","package":"kernel-default","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.4.0-25.1"}]}],"bundled":357},{"source":"osv","ecosystem":"SUSE:Linux Micro 6.1","package":"kernel-default-base","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.4.0-24.1.21.4"}]}],"bundled":357},{"source":"osv","ecosystem":"SUSE:Linux Micro 6.1","package":"kernel-kvmsmall","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.4.0-25.1"}]}],"bundled":357},{"source":"osv","ecosystem":"SUSE:Linux Micro 6.1","package":"kernel-livepatch-MICRO-6-0_Update_5","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1-1.2"}]}],"bundled":357},{"source":"osv","ecosystem":"SUSE:Linux Micro 6.1","package":"kernel-source","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.4.0-25.1"}]}],"bundled":357},{"source":"osv","ecosystem":"SUSE:Linux Micro 6.1","package":"kernel-livepatch-MICRO-6-0-RT_Update_5","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1-1.1"}]}],"bundled":610},{"source":"osv","ecosystem":"SUSE:Linux Micro 6.1","package":"kernel-rt","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.4.0-25.1"}]}],"bundled":610},{"source":"osv","ecosystem":"SUSE:Linux Micro 6.1","package":"kernel-source-rt","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.4.0-25.1"}]}],"bundled":610},{"source":"osv","ecosystem":"Ubuntu:16.04:LTS","package":"linux-hwe-edge","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["4.8.0-28.30~16.04.1","4.8.0-30.32~16.04.1","4.8.0-32.34~16.04.1","4.8.0-34.36~16.04.1","4.10.0-14.16~16.04.1","4.10.0-19.21~16.04.1","4.10.0-20.22~16.04.1","4.10.0-21.23~16.04.1","4.10.0-22.24~16.04.1","4.10.0-24.28~16.04.1","4.10.0-26.30~16.04.1","4.11.0-13.19~16.04.1","4.11.0-14.20~16.04.1","4.13.0-16.19~16.04.3","4.13.0-17.20~16.04.1","4.13.0-19.22~16.04.1","4.13.0-21.24~16.04.1","4.13.0-25.29~16.04.2","4.15.0-13.14~16.04.1","4.15.0-15.16~16.04.1","4.15.0-20.21~16.04.1","4.15.0-22.24~16.04.1","4.15.0-23.25~16.04.1"]},{"source":"osv","ecosystem":"Ubuntu:18.04:LTS","package":"linux-aws-5.0","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.0.0-1021.24~18.04.1","5.0.0-1022.25~18.04.1","5.0.0-1023.26~18.04.1","5.0.0-1024.27~18.04.1","5.0.0-1025.28","5.0.0-1027.30"]},{"source":"osv","ecosystem":"Ubuntu:18.04:LTS","package":"linux-aws-5.3","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.3.0-1016.17~18.04.1","5.3.0-1017.18~18.04.1","5.3.0-1019.21~18.04.1","5.3.0-1023.25~18.04.1","5.3.0-1028.30~18.04.1","5.3.0-1030.32~18.04.1","5.3.0-1032.34~18.04.2","5.3.0-1033.35","5.3.0-1034.36","5.3.0-1035.37"]},{"source":"osv","ecosystem":"Ubuntu:18.04:LTS","package":"linux-azure","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["4.15.0-1002.2","4.15.0-1003.3","4.15.0-1004.4","4.15.0-1008.8","4.15.0-1009.9","4.15.0-1012.12","4.15.0-1013.13","4.15.0-1014.14","4.15.0-1018.18","4.15.0-1019.19","4.15.0-1021.21","4.15.0-1022.23","4.15.0-1023.24","4.15.0-1025.26","4.15.0-1028.29","4.15.0-1030.31","4.15.0-1031.32","4.15.0-1032.33","4.15.0-1035.36","4.15.0-1036.38","4.15.0-1037.39","4.18.0-1011.11~18.04.1","4.18.0-1013.13~18.04.1","4.18.0-1014.14~18.04.1","4.18.0-1018.18~18.04.1","4.18.0-1019.19~18.04.1","4.18.0-1020.20~18.04.1","4.18.0-1023.24~18.04.1","4.18.0-1024.25~18.04.1","4.18.0-1025.27~18.04.1","5.0.0-1014.14~18.04.1","5.0.0-1016.17~18.04.1","5.0.0-1018.19~18.04.1","5.0.0-1020.21~18.04.1","5.0.0-1022.23~18.04.1","5.0.0-1023.24~18.04.1","5.0.0-1025.27~18.04.1","5.0.0-1027.29~18.04.1","5.0.0-1028.30~18.04.1","5.0.0-1029.31~18.04.1","5.0.0-1031.33","5.0.0-1032.34","5.0.0-1035.37","5.0.0-1036.38"]},{"source":"osv","ecosystem":"Ubuntu:18.04:LTS","package":"linux-azure-5.3","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.3.0-1007.8~18.04.1","5.3.0-1008.9~18.04.1","5.3.0-1009.10~18.04.1","5.3.0-1010.11~18.04.1","5.3.0-1012.13~18.04.1","5.3.0-1013.14~18.04.1","5.3.0-1016.17~18.04.1","5.3.0-1018.19~18.04.1","5.3.0-1019.20~18.04.1","5.3.0-1020.21~18.04.1","5.3.0-1022.23~18.04.1","5.3.0-1028.29~18.04.1","5.3.0-1031.32~18.04.1","5.3.0-1032.33~18.04.1","5.3.0-1034.35~18.04.1","5.3.0-1035.36"]},{"source":"osv","ecosystem":"Ubuntu:18.04:LTS","package":"linux-azure-edge","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["4.18.0-1006.6~18.04.1","4.18.0-1007.7~18.04.1","4.18.0-1008.8~18.04.1","5.0.0-1012.12~18.04.2"]},{"source":"osv","ecosystem":"Ubuntu:18.04:LTS","package":"linux-gcp","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["4.15.0-1001.1","4.15.0-1003.3","4.15.0-1005.5","4.15.0-1006.6","4.15.0-1008.8","4.15.0-1009.9","4.15.0-1010.10","4.15.0-1014.14","4.15.0-1015.15","4.15.0-1017.18","4.15.0-1018.19","4.15.0-1019.20","4.15.0-1021.22","4.15.0-1023.24","4.15.0-1024.25","4.15.0-1025.26","4.15.0-1026.27","4.15.0-1027.28","4.15.0-1028.29","4.15.0-1029.31","4.15.0-1030.32","4.15.0-1032.34","4.15.0-1033.35","4.15.0-1034.36","4.15.0-1036.38","4.15.0-1037.39","4.15.0-1040.42","4.15.0-1042.45","4.15.0-1044.70","5.0.0-1020.20~18.04.1","5.0.0-1021.21~18.04.1","5.0.0-1025.26~18.04.1","5.0.0-1026.27~18.04.1","5.0.0-1028.29~18.04.1","5.0.0-1029.30~18.04.1","5.0.0-1031.32","5.0.0-1033.34","5.0.0-1034.35"]},{"source":"osv","ecosystem":"Ubuntu:18.04:LTS","package":"linux-gcp-5.3","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.3.0-1008.9~18.04.1","5.3.0-1009.10~18.04.1","5.3.0-1010.11~18.04.1","5.3.0-1012.13~18.04.1","5.3.0-1014.15~18.04.1","5.3.0-1016.17~18.04.1","5.3.0-1017.18~18.04.1","5.3.0-1018.19~18.04.1","5.3.0-1020.22~18.04.1","5.3.0-1026.28~18.04.1","5.3.0-1029.31~18.04.1","5.3.0-1030.32~18.04.1","5.3.0-1032.34~18.04.1"]},{"source":"osv","ecosystem":"Ubuntu:18.04:LTS","package":"linux-gke-4.15","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["4.15.0-1030.32","4.15.0-1032.34","4.15.0-1033.35","4.15.0-1034.36","4.15.0-1036.38","4.15.0-1037.39","4.15.0-1040.42","4.15.0-1041.43","4.15.0-1042.44","4.15.0-1044.46","4.15.0-1045.48","4.15.0-1046.49","4.15.0-1048.51","4.15.0-1049.52","4.15.0-1050.53","4.15.0-1052.55","4.15.0-1055.58","4.15.0-1057.60","4.15.0-1058.61","4.15.0-1059.62","4.15.0-1063.66","4.15.0-1064.67","4.15.0-1066.69","4.15.0-1067.70","4.15.0-1069.72","4.15.0-1070.73","4.15.0-1072.76","4.15.0-1073.78","4.15.0-1074.79","4.15.0-1076.81","4.15.0-1077.82","4.15.0-1078.83","4.15.0-1079.84"]},{"source":"osv","ecosystem":"Ubuntu:18.04:LTS","package":"linux-gke-5.4","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.4.0-1025.25~18.04.1","5.4.0-1027.28~18.04.1","5.4.0-1029.31~18.04.1","5.4.0-1030.32~18.04.1","5.4.0-1032.34~18.04.1","5.4.0-1033.35~18.04.1","5.4.0-1035.37~18.04.1","5.4.0-1036.38~18.04.1","5.4.0-1037.39~18.04.1","5.4.0-1039.41~18.04.1","5.4.0-1040.42~18.04.1","5.4.0-1042.44~18.04.1","5.4.0-1043.45~18.04.1","5.4.0-1044.46~18.04.1","5.4.0-1046.48~18.04.1","5.4.0-1049.52~18.04.1","5.4.0-1051.54~18.04.1","5.4.0-1052.55~18.04.1","5.4.0-1053.56~18.04.1","5.4.0-1054.57~18.04.1","5.4.0-1055.58~18.04.1","5.4.0-1056.59~18.04.1","5.4.0-1057.60~18.04.1","5.4.0-1059.62~18.04.1","5.4.0-1061.64~18.04.1","5.4.0-1062.65~18.04.1","5.4.0-1063.66~18.04.1","5.4.0-1065.68~18.04.1","5.4.0-1066.69~18.04.1","5.4.0-1067.70~18.04.1","5.4.0-1068.71~18.04.1","5.4.0-1071.76~18.04.3","5.4.0-1072.77~18.04.1","5.4.0-1074.79~18.04.1","5.4.0-1076.82~18.04.1","5.4.0-1078.84~18.04.1","5.4.0-1080.86~18.04.1"]},{"source":"osv","ecosystem":"Ubuntu:18.04:LTS","package":"linux-gkeop-5.4","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.4.0-1001.1","5.4.0-1003.3","5.4.0-1004.5","5.4.0-1005.6","5.4.0-1007.8~18.04.1","5.4.0-1008.9~18.04.1","5.4.0-1009.10~18.04.1","5.4.0-1010.11~18.04.1","5.4.0-1011.12~18.04.2","5.4.0-1012.13~18.04.1","5.4.0-1013.14~18.04.1","5.4.0-1014.15~18.04.1","5.4.0-1015.16~18.04.1","5.4.0-1016.17~18.04.1","5.4.0-1018.19~18.04.1","5.4.0-1021.22~18.04.1","5.4.0-1022.23~18.04.1","5.4.0-1023.24~18.04.1","5.4.0-1024.25~18.04.1","5.4.0-1025.26~18.04.1","5.4.0-1026.27~18.04.1","5.4.0-1027.28~18.04.1","5.4.0-1029.30~18.04.2","5.4.0-1031.32~18.04.1","5.4.0-1032.33~18.04.1","5.4.0-1033.34~18.04.1","5.4.0-1034.35~18.04.1","5.4.0-1036.37~18.04.1","5.4.0-1037.38~18.04.1","5.4.0-1038.39~18.04.1","5.4.0-1039.40~18.04.1","5.4.0-1040.41~18.04.1","5.4.0-1043.44~18.04.1","5.4.0-1046.48~18.04.1","5.4.0-1048.51~18.04.1","5.4.0-1049.52~18.04.1","5.4.0-1051.54~18.04.1"]},{"source":"osv","ecosystem":"Ubuntu:18.04:LTS","package":"linux-hwe","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["4.18.0-13.14~18.04.1","4.18.0-14.15~18.04.1","4.18.0-15.16~18.04.1","4.18.0-16.17~18.04.1","4.18.0-17.18~18.04.1","4.18.0-18.19~18.04.1","4.18.0-20.21~18.04.1","4.18.0-21.22~18.04.1","4.18.0-22.23~18.04.1","4.18.0-24.25~18.04.1","4.18.0-25.26~18.04.1","5.0.0-23.24~18.04.1","5.0.0-25.26~18.04.1","5.0.0-27.28~18.04.1","5.0.0-29.31~18.04.1","5.0.0-31.33~18.04.1","5.0.0-32.34~18.04.2","5.0.0-35.38~18.04.1","5.0.0-36.39~18.04.1","5.0.0-37.40~18.04.1","5.3.0-26.28~18.04.1","5.3.0-28.30~18.04.1","5.3.0-40.32~18.04.1","5.3.0-42.34~18.04.1","5.3.0-45.37~18.04.1","5.3.0-46.38~18.04.1","5.3.0-51.44~18.04.2","5.3.0-53.47~18.04.1","5.3.0-59.53~18.04.1","5.3.0-61.55~18.04.1","5.3.0-62.56~18.04.1","5.3.0-64.58~18.04.1","5.3.0-65.59","5.3.0-66.60","5.3.0-67.61","5.3.0-68.63","5.3.0-69.65","5.3.0-70.66","5.3.0-72.68","5.3.0-73.69","5.3.0-74.70","5.3.0-75.71","5.3.0-76.72"]},{"source":"osv","ecosystem":"Ubuntu:18.04:LTS","package":"linux-hwe-edge","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.0.0-15.16~18.04.1","5.0.0-16.17~18.04.1","5.0.0-17.18~18.04.1","5.0.0-19.20~18.04.1","5.0.0-20.21~18.04.1","5.3.0-19.20~18.04.2","5.3.0-22.24~18.04.1","5.3.0-23.25~18.04.1","5.3.0-23.25~18.04.2","5.3.0-24.26~18.04.2"]},{"source":"osv","ecosystem":"Ubuntu:18.04:LTS","package":"linux-oem","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["4.15.0-1002.3","4.15.0-1004.5","4.15.0-1006.9","4.15.0-1008.11","4.15.0-1009.12","4.15.0-1012.15","4.15.0-1013.16","4.15.0-1015.18","4.15.0-1017.20","4.15.0-1018.21","4.15.0-1021.24","4.15.0-1024.29","4.15.0-1026.31","4.15.0-1028.33","4.15.0-1030.35","4.15.0-1033.38","4.15.0-1034.39","4.15.0-1035.40","4.15.0-1036.41","4.15.0-1038.43","4.15.0-1039.44","4.15.0-1043.48","4.15.0-1045.50","4.15.0-1050.57","4.15.0-1056.65","4.15.0-1057.66","4.15.0-1059.68","4.15.0-1063.72","4.15.0-1064.73","4.15.0-1065.75","4.15.0-1066.76","4.15.0-1067.77","4.15.0-1069.79","4.15.0-1073.83","4.15.0-1076.86","4.15.0-1079.89","4.15.0-1080.90","4.15.0-1081.91","4.15.0-1087.97","4.15.0-1090.100","4.15.0-1091.101","4.15.0-1093.103","4.15.0-1094.104","4.15.0-1096.106","4.15.0-1097.107","4.15.0-1099.109","4.15.0-1100.110","4.15.0-1101.112","4.15.0-1102.113","4.15.0-1103.114"]},{"source":"osv","ecosystem":"Ubuntu:18.04:LTS","package":"linux-oracle-5.0","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.0.0-1007.12~18.04.1","5.0.0-1008.13~18.04.1","5.0.0-1009.14~18.04.1","5.0.0-1010.15~18.04.1","5.0.0-1011.16","5.0.0-1013.18","5.0.0-1014.19"]},{"source":"osv","ecosystem":"Ubuntu:18.04:LTS","package":"linux-oracle-5.3","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.3.0-1011.12~18.04.1","5.3.0-1013.14~18.04.1","5.3.0-1014.15~18.04.1","5.3.0-1016.18~18.04.1","5.3.0-1018.20~18.04.1","5.3.0-1024.26~18.04.1","5.3.0-1027.29~18.04.1","5.3.0-1028.30~18.04.1","5.3.0-1030.32~18.04.1"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-aws-5.11","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.11.0-1009.9~20.04.2","5.11.0-1014.15~20.04.1","5.11.0-1016.17~20.04.1","5.11.0-1017.18~20.04.1","5.11.0-1019.20~20.04.1","5.11.0-1020.21~20.04.2","5.11.0-1021.22~20.04.2","5.11.0-1022.23~20.04.1","5.11.0-1023.24~20.04.1","5.11.0-1025.27~20.04.1","5.11.0-1027.30~20.04.1","5.11.0-1028.31~20.04.1"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-aws-5.13","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.13.0-1008.9~20.04.2","5.13.0-1011.12~20.04.1","5.13.0-1012.13~20.04.1","5.13.0-1014.15~20.04.1","5.13.0-1017.19~20.04.1","5.13.0-1019.21~20.04.1","5.13.0-1021.23~20.04.2","5.13.0-1022.24~20.04.1","5.13.0-1023.25~20.04.1","5.13.0-1025.27~20.04.1","5.13.0-1028.31~20.04.1","5.13.0-1029.32~20.04.1","5.13.0-1031.35~20.04.1"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-aws-5.8","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.8.0-1035.37~20.04.1","5.8.0-1038.40~20.04.1","5.8.0-1041.43~20.04.1","5.8.0-1042.44~20.04.1"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-azure-5.11","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.11.0-1007.7~20.04.2","5.11.0-1012.13~20.04.1","5.11.0-1013.14~20.04.1","5.11.0-1015.16~20.04.1","5.11.0-1017.18~20.04.1","5.11.0-1019.20~20.04.1","5.11.0-1020.21~20.04.1","5.11.0-1021.22~20.04.1","5.11.0-1022.23~20.04.1","5.11.0-1023.24~20.04.1","5.11.0-1025.27~20.04.1","5.11.0-1027.30~20.04.1","5.11.0-1028.31~20.04.2"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-azure-5.13","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.13.0-1009.10~20.04.2","5.13.0-1012.14~20.04.1","5.13.0-1013.15~20.04.1","5.13.0-1014.16~20.04.1","5.13.0-1017.19~20.04.1","5.13.0-1021.24~20.04.1","5.13.0-1022.26~20.04.1","5.13.0-1023.27~20.04.1","5.13.0-1025.29~20.04.1","5.13.0-1028.33~20.04.1","5.13.0-1029.34~20.04.1","5.13.0-1031.37~20.04.1"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-azure-5.8","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.8.0-1033.35~20.04.1","5.8.0-1036.38~20.04.1","5.8.0-1039.42~20.04.1","5.8.0-1040.43~20.04.1","5.8.0-1041.44~20.04.1","5.8.0-1042.45~20.04.1","5.8.0-1043.46~20.04.1"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-azure-fde","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.4.0-1063.66+cvm2.2","5.4.0-1063.66+cvm3.2","5.4.0-1064.67+cvm1.1","5.4.0-1065.68+cvm2.1","5.4.0-1067.70+cvm1.1","5.4.0-1068.71+cvm1.1","5.4.0-1069.72+cvm1.1","5.4.0-1070.73+cvm1.1","5.4.0-1072.75+cvm1.1","5.4.0-1073.76+cvm1.1","5.4.0-1074.77+cvm1.1","5.4.0-1076.79+cvm1.1","5.4.0-1078.81+cvm1.1","5.4.0-1080.83+cvm1.1","5.4.0-1083.87+cvm1.1","5.4.0-1085.90+cvm1.1","5.4.0-1085.90+cvm2.1","5.4.0-1086.91+cvm1.1","5.4.0-1089.94+cvm1.2","5.4.0-1090.95+cvm1.1","5.4.0-1091.96+cvm1.1","5.4.0-1092.97+cvm1.1","5.4.0-1095.101+cvm1.1","5.4.0-1098.104+cvm1.1","5.4.0-1100.106+cvm1.1","5.4.0-1103.109+cvm1.1"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-gcp-5.11","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.11.0-1009.10~20.04.1","5.11.0-1014.16~20.04.1","5.11.0-1017.19~20.04.1","5.11.0-1018.20~20.04.2","5.11.0-1020.22~20.04.1","5.11.0-1021.23~20.04.1","5.11.0-1022.24~20.04.1","5.11.0-1023.25~20.04.1","5.11.0-1024.26~20.04.1","5.11.0-1026.29~20.04.1","5.11.0-1028.32~20.04.1","5.11.0-1029.33~20.04.3"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-gcp-5.13","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.13.0-1008.9~20.04.3","5.13.0-1012.15~20.04.1","5.13.0-1013.16~20.04.1","5.13.0-1015.18~20.04.1","5.13.0-1019.23~20.04.1","5.13.0-1021.25~20.04.1","5.13.0-1023.28~20.04.1","5.13.0-1024.29~20.04.1","5.13.0-1025.30~20.04.1","5.13.0-1027.32~20.04.1","5.13.0-1030.36~20.04.1","5.13.0-1031.37~20.04.1","5.13.0-1033.40~20.04.1"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-gcp-5.8","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.8.0-1032.34~20.04.1","5.8.0-1035.37~20.04.1","5.8.0-1038.40~20.04.1","5.8.0-1039.41"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-gke","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.4.0-1033.35","5.4.0-1035.37","5.4.0-1036.38","5.4.0-1037.39","5.4.0-1039.41","5.4.0-1041.43","5.4.0-1042.44","5.4.0-1043.45","5.4.0-1044.46","5.4.0-1046.48","5.4.0-1049.52","5.4.0-1051.54","5.4.0-1052.55","5.4.0-1053.56","5.4.0-1054.57","5.4.0-1055.58","5.4.0-1056.59","5.4.0-1057.60","5.4.0-1059.62","5.4.0-1061.64","5.4.0-1062.65","5.4.0-1063.66","5.4.0-1065.68","5.4.0-1066.69","5.4.0-1067.70","5.4.0-1068.71","5.4.0-1071.76","5.4.0-1072.77","5.4.0-1074.79","5.4.0-1076.82","5.4.0-1078.84","5.4.0-1080.86","5.4.0-1081.87","5.4.0-1083.89","5.4.0-1084.90","5.4.0-1086.93","5.4.0-1087.94","5.4.0-1090.97","5.4.0-1091.98","5.4.0-1094.101","5.4.0-1095.102","5.4.0-1096.103","5.4.0-1097.104","5.4.0-1098.105","5.4.0-1099.106","5.4.0-1100.107","5.4.0-1101.108","5.4.0-1102.109","5.4.0-1103.110","5.4.0-1104.111","5.4.0-1105.112"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-gke-5.15","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.15.0-1011.14~20.04.1","5.15.0-1014.17~20.04.1","5.15.0-1015.18~20.04.1","5.15.0-1016.19~20.04.1","5.15.0-1019.23~20.04.1","5.15.0-1020.25~20.04.1","5.15.0-1023.28~20.04.2","5.15.0-1027.32~20.04.1","5.15.0-1028.33~20.04.1","5.15.0-1029.34~20.04.1","5.15.0-1031.36~20.04.1","5.15.0-1032.37~20.04.1","5.15.0-1033.38~20.04.1","5.15.0-1034.39~20.04.1","5.15.0-1036.41~20.04.1","5.15.0-1037.42~20.04.1","5.15.0-1038.43~20.04.1","5.15.0-1039.44~20.04.1"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-gkeop","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.4.0-1008.9","5.4.0-1009.10","5.4.0-1010.11","5.4.0-1011.12","5.4.0-1012.13","5.4.0-1013.14","5.4.0-1014.15","5.4.0-1015.16","5.4.0-1016.17","5.4.0-1018.19","5.4.0-1021.22","5.4.0-1022.23","5.4.0-1023.24","5.4.0-1024.25","5.4.0-1025.26","5.4.0-1026.27","5.4.0-1027.28","5.4.0-1029.30","5.4.0-1031.32","5.4.0-1032.33","5.4.0-1033.34","5.4.0-1034.35","5.4.0-1036.37","5.4.0-1037.38","5.4.0-1038.39","5.4.0-1039.40","5.4.0-1040.41","5.4.0-1043.44","5.4.0-1046.48","5.4.0-1048.51","5.4.0-1049.52","5.4.0-1051.54","5.4.0-1052.55","5.4.0-1053.56","5.4.0-1054.57","5.4.0-1056.60","5.4.0-1057.61","5.4.0-1060.64","5.4.0-1061.65","5.4.0-1062.66","5.4.0-1064.68","5.4.0-1065.69","5.4.0-1066.70","5.4.0-1067.71","5.4.0-1068.72","5.4.0-1069.73","5.4.0-1070.74","5.4.0-1071.75","5.4.0-1072.76","5.4.0-1073.77","5.4.0-1074.78","5.4.0-1075.79","5.4.0-1076.80","5.4.0-1077.81","5.4.0-1078.82","5.4.0-1079.83","5.4.0-1080.84","5.4.0-1081.85","5.4.0-1083.87","5.4.0-1084.88","5.4.0-1085.89","5.4.0-1086.90","5.4.0-1087.91","5.4.0-1088.92","5.4.0-1089.93","5.4.0-1090.94","5.4.0-1091.95","5.4.0-1092.96","5.4.0-1093.97","5.4.0-1094.98","5.4.0-1095.99","5.4.0-1096.100","5.4.0-1097.101","5.4.0-1098.102","5.4.0-1099.103","5.4.0-1100.104","5.4.0-1101.105","5.4.0-1102.106"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-gkeop-5.15","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.15.0-1003.5~20.04.2","5.15.0-1005.7~20.04.1","5.15.0-1007.10~20.04.1","5.15.0-1008.12~20.04.1","5.15.0-1011.15~20.04.2","5.15.0-1012.16~20.04.1","5.15.0-1013.17~20.04.1","5.15.0-1015.19~20.04.1","5.15.0-1016.21~20.04.1","5.15.0-1017.22~20.04.1","5.15.0-1018.23~20.04.1","5.15.0-1019.24~20.04.1","5.15.0-1020.25~20.04.1","5.15.0-1021.26~20.04.1","5.15.0-1022.27~20.04.1","5.15.0-1023.28~20.04.1","5.15.0-1024.29~20.04.1","5.15.0-1025.30~20.04.1","5.15.0-1026.31~20.04.1","5.15.0-1027.32~20.04.1","5.15.0-1028.33~20.04.1","5.15.0-1030.35~20.04.1","5.15.0-1031.37~20.04.1","5.15.0-1032.38~20.04.1","5.15.0-1033.39~20.04.1","5.15.0-1034.40~20.04.1","5.15.0-1035.41~20.04.1","5.15.0-1036.42~20.04.1","5.15.0-1037.43~20.04.1","5.15.0-1038.44~20.04.1","5.15.0-1039.45~20.04.1","5.15.0-1040.46~20.04.1","5.15.0-1043.50~20.04.1","5.15.0-1044.51~20.04.1","5.15.0-1045.52~20.04.1","5.15.0-1046.53~20.04.1","5.15.0-1047.54~20.04.1","5.15.0-1048.55~20.04.1","5.15.0-1049.56~20.04.1","5.15.0-1050.57~20.04.1","5.15.0-1051.58~20.04.1","5.15.0-1052.59~20.04.1","5.15.0-1053.60~20.04.1","5.15.0-1054.61~20.04.1","5.15.0-1055.62~20.04.1"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-hwe-5.11","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.11.0-22.23~20.04.1","5.11.0-25.27~20.04.1","5.11.0-27.29~20.04.1","5.11.0-34.36~20.04.1","5.11.0-36.40~20.04.1","5.11.0-37.41~20.04.2","5.11.0-38.42~20.04.1","5.11.0-40.44~20.04.2","5.11.0-41.45~20.04.1","5.11.0-43.47~20.04.2","5.11.0-44.48~20.04.2","5.11.0-46.51~20.04.1"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-hwe-5.13","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.13.0-21.21~20.04.1","5.13.0-22.22~20.04.1","5.13.0-23.23~20.04.2","5.13.0-25.26~20.04.1","5.13.0-27.29~20.04.1","5.13.0-28.31~20.04.1","5.13.0-30.33~20.04.1","5.13.0-35.40~20.04.1","5.13.0-37.42~20.04.1","5.13.0-39.44~20.04.1","5.13.0-40.45~20.04.1","5.13.0-41.46~20.04.1","5.13.0-44.49~20.04.1","5.13.0-48.54~20.04.1","5.13.0-51.58~20.04.1","5.13.0-52.59~20.04.1"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-hwe-5.8","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.8.0-23.24~20.04.1","5.8.0-25.26~20.04.1","5.8.0-28.30~20.04.1","5.8.0-29.31~20.04.1","5.8.0-31.33~20.04.1","5.8.0-33.36~20.04.1","5.8.0-34.37~20.04.2","5.8.0-36.40~20.04.1","5.8.0-38.43~20.04.1","5.8.0-40.45~20.04.1","5.8.0-41.46~20.04.1","5.8.0-43.49~20.04.1","5.8.0-44.50~20.04.1","5.8.0-45.51~20.04.1","5.8.0-48.54~20.04.1","5.8.0-49.55~20.04.1","5.8.0-50.56~20.04.1","5.8.0-53.60~20.04.1","5.8.0-55.62~20.04.1","5.8.0-59.66~20.04.1","5.8.0-63.71~20.04.1"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-intel-5.13","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.13.0-1007.7","5.13.0-1008.8","5.13.0-1009.9","5.13.0-1010.10","5.13.0-1011.11","5.13.0-1014.15","5.13.0-1017.19"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-oem-5.10","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.10.0-1008.9","5.10.0-1011.12","5.10.0-1013.14","5.10.0-1014.15","5.10.0-1016.17","5.10.0-1017.18","5.10.0-1019.20","5.10.0-1021.22","5.10.0-1022.23","5.10.0-1023.24","5.10.0-1025.26","5.10.0-1026.27","5.10.0-1029.30","5.10.0-1032.33","5.10.0-1033.34","5.10.0-1034.35","5.10.0-1038.40","5.10.0-1044.46","5.10.0-1045.47","5.10.0-1049.51","5.10.0-1050.52","5.10.0-1051.53","5.10.0-1052.54","5.10.0-1053.55","5.10.0-1055.58","5.10.0-1057.61"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-oem-5.13","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.13.0-1009.10","5.13.0-1010.11","5.13.0-1012.16","5.13.0-1014.18","5.13.0-1017.21","5.13.0-1019.23","5.13.0-1020.24","5.13.0-1021.25","5.13.0-1022.26","5.13.0-1026.32","5.13.0-1028.35","5.13.0-1029.36"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-oem-5.14","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.14.0-1004.4","5.14.0-1005.5","5.14.0-1007.7","5.14.0-1008.8","5.14.0-1010.10","5.14.0-1011.11","5.14.0-1013.13","5.14.0-1018.19","5.14.0-1020.22","5.14.0-1022.24","5.14.0-1024.26","5.14.0-1027.30","5.14.0-1029.32","5.14.0-1031.34","5.14.0-1032.35","5.14.0-1033.36","5.14.0-1034.37","5.14.0-1036.40","5.14.0-1038.42","5.14.0-1042.47","5.14.0-1044.49","5.14.0-1045.51","5.14.0-1046.53","5.14.0-1047.54","5.14.0-1048.55","5.14.0-1049.56","5.14.0-1050.57","5.14.0-1051.58","5.14.0-1052.59","5.14.0-1054.61","5.14.0-1055.62","5.14.0-1056.63","5.14.0-1057.64","5.14.0-1058.66","5.14.0-1059.67"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-oem-5.6","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.6.0-1007.7","5.6.0-1008.8","5.6.0-1010.10","5.6.0-1011.11","5.6.0-1013.13","5.6.0-1017.17","5.6.0-1018.18","5.6.0-1020.20","5.6.0-1021.21","5.6.0-1023.23","5.6.0-1026.26","5.6.0-1027.27","5.6.0-1028.28","5.6.0-1031.32","5.6.0-1032.33","5.6.0-1033.35","5.6.0-1034.36","5.6.0-1035.37","5.6.0-1036.39","5.6.0-1039.43","5.6.0-1042.46","5.6.0-1047.51","5.6.0-1048.52","5.6.0-1050.54","5.6.0-1052.56","5.6.0-1053.57","5.6.0-1054.58","5.6.0-1055.59","5.6.0-1056.60"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-oracle-5.11","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.11.0-1008.8~20.04.1","5.11.0-1013.14~20.04.1","5.11.0-1016.17~20.04.1","5.11.0-1017.18~20.04.1","5.11.0-1019.20~20.04.1","5.11.0-1020.21~20.04.1","5.11.0-1021.22~20.04.1","5.11.0-1022.23~20.04.1","5.11.0-1023.24~20.04.1","5.11.0-1025.27~20.04.1","5.11.0-1027.30~20.04.1","5.11.0-1028.31~20.04.1"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-oracle-5.13","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.13.0-1011.13~20.04.2","5.13.0-1015.19~20.04.1","5.13.0-1016.20~20.04.1","5.13.0-1018.22~20.04.1","5.13.0-1021.26~20.04.1","5.13.0-1025.30~20.04.1","5.13.0-1027.32~20.04.1","5.13.0-1028.33~20.04.1","5.13.0-1030.35~20.04.1","5.13.0-1033.39~20.04.1","5.13.0-1034.40~20.04.1","5.13.0-1036.43~20.04.1"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-oracle-5.8","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.8.0-1031.32~20.04.2","5.8.0-1033.34~20.04.1","5.8.0-1034.35~20.04.2","5.8.0-1037.38~20.04.1","5.8.0-1038.39~20.04.1"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-raspi2","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.3.0-1007.8","5.3.0-1014.16","5.3.0-1015.17","5.3.0-1017.19","5.4.0-1004.4","5.4.0-1006.6"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-riscv","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.4.0-24.28","5.4.0-26.30","5.4.0-27.31","5.4.0-28.32","5.4.0-30.34","5.4.0-31.35","5.4.0-33.37","5.4.0-34.38","5.4.0-36.41","5.4.0-37.42","5.4.0-39.44","5.4.0-40.45"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-riscv-5.11","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.11.0-1015.16~20.04.1","5.11.0-1017.18~20.04.1","5.11.0-1018.19~20.04.2","5.11.0-1020.21~20.04.1","5.11.0-1021.22~20.04.1","5.11.0-1022.23~20.04.1","5.11.0-1023.24~20.04.1","5.11.0-1024.25~20.04.1","5.11.0-1026.28~20.04.1","5.11.0-1028.31~20.04.1","5.11.0-1029.32~20.04.1","5.11.0-1030.34","5.11.0-1031.35"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-riscv-5.8","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.8.0-14.16~20.04.1","5.8.0-14.16~20.04.3","5.8.0-16.18~20.04.1","5.8.0-17.19~20.04.1","5.8.0-18.20~20.04.1","5.8.0-20.22~20.04.1","5.8.0-22.24~20.04.1","5.8.0-25.27~20.04.1","5.8.0-26.28~20.04.1","5.8.0-29.31~20.04.1"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-allwinner-5.19","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.19.0-1007.7~22.04.1","5.19.0-1009.9~22.04.1","5.19.0-1010.10~22.04.1","5.19.0-1011.11~22.04.1","5.19.0-1012.12~22.04.1","5.19.0-1013.13~22.04.1","5.19.0-1014.14~22.04.1","5.19.0-1015.15~22.04.1"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-aws-5.19","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.19.0-1019.20~22.04.1","5.19.0-1020.21~22.04.1","5.19.0-1022.23~22.04.1","5.19.0-1023.24~22.04.1","5.19.0-1024.25~22.04.1","5.19.0-1025.26~22.04.1","5.19.0-1026.27~22.04.1","5.19.0-1027.28~22.04.1","5.19.0-1028.29~22.04.1","5.19.0-1029.30~22.04.1"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-aws-6.2","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["6.2.0-1005.5~22.04.1","6.2.0-1006.6~22.04.1","6.2.0-1007.7~22.04.1","6.2.0-1008.8~22.04.1","6.2.0-1009.9~22.04.3","6.2.0-1010.10~22.04.1","6.2.0-1011.11~22.04.1","6.2.0-1012.12~22.04.1","6.2.0-1013.13~22.04.1","6.2.0-1014.14~22.04.1","6.2.0-1015.15~22.04.1","6.2.0-1016.16~22.04.1","6.2.0-1017.17~22.04.1","6.2.0-1018.18~22.04.1"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-aws-6.5","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["6.5.0-1008.8~22.04.1","6.5.0-1010.10~22.04.1","6.5.0-1011.11~22.04.1","6.5.0-1012.12~22.04.1","6.5.0-1014.14~22.04.1","6.5.0-1015.15~22.04.1","6.5.0-1016.16~22.04.1","6.5.0-1017.17~22.04.2","6.5.0-1018.18~22.04.1","6.5.0-1020.20~22.04.1","6.5.0-1021.21~22.04.1","6.5.0-1022.22~22.04.1","6.5.0-1023.23~22.04.1","6.5.0-1024.24~22.04.1"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-aws-6.8","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1027.29~22.04.1"}]}],"versions":["6.8.0-1009.9~22.04.2","6.8.0-1010.10~22.04.2","6.8.0-1011.12~22.04.1","6.8.0-1013.14~22.04.1","6.8.0-1014.15~22.04.1","6.8.0-1015.16~22.04.1","6.8.0-1016.17~22.04.2","6.8.0-1017.18~22.04.1","6.8.0-1018.19~22.04.1","6.8.0-1019.21~22.04.1","6.8.0-1020.22~22.04.1","6.8.0-1021.23~22.04.1","6.8.0-1023.25~22.04.1","6.8.0-1024.26~22.04.1"]},{"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-1027.32~22.04.1"}]}],"versions":["6.8.0-1008.8~22.04.1","6.8.0-1009.9~22.04.1","6.8.0-1010.10~22.04.1","6.8.0-1012.14~22.04.1","6.8.0-1013.15~22.04.1","6.8.0-1014.16~22.04.1","6.8.0-1015.17~22.04.2","6.8.0-1017.20~22.04.1","6.8.0-1018.21~22.04.1","6.8.0-1020.23~22.04.1","6.8.0-1021.25~22.04.1","6.8.0-1025.30~22.04.1","6.8.0-1026.31~22.04.1"]},{"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-1028.30~22.04.1"}]}],"versions":["6.8.0-1010.11~22.04.1","6.8.0-1011.12~22.04.1","6.8.0-1012.13~22.04.1","6.8.0-1013.14~22.04.1","6.8.0-1014.16~22.04.1","6.8.0-1015.17~22.04.1","6.8.0-1016.18~22.04.1","6.8.0-1017.19~22.04.1","6.8.0-1018.20~22.04.1","6.8.0-1019.21~22.04.1","6.8.0-1020.22~22.04.1","6.8.0-1021.23~22.04.1","6.8.0-1024.26~22.04.1","6.8.0-1025.27~22.04.1","6.8.0-1026.28~22.04.1","6.8.0-1027.29~22.04.1"]},{"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-58.60~22.04.1"}]}],"versions":["6.8.0-38.38~22.04.1","6.8.0-39.39~22.04.1","6.8.0-40.40~22.04.3","6.8.0-45.45~22.04.1","6.8.0-47.47~22.04.1","6.8.0-48.48~22.04.1","6.8.0-49.49~22.04.1","6.8.0-50.51~22.04.1","6.8.0-51.52~22.04.1","6.8.0-52.53~22.04.1","6.8.0-57.59~22.04.1"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-ibm-6.8","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1024.24~22.04.1"}]}],"versions":["6.8.0-1008.8~22.04.1","6.8.0-1010.10~22.04.1","6.8.0-1011.11~22.04.1","6.8.0-1012.12~22.04.1","6.8.0-1013.13~22.04.1","6.8.0-1014.14~22.04.1","6.8.0-1015.15~22.04.1","6.8.0-1016.16~22.04.1","6.8.0-1017.17~22.04.1","6.8.0-1018.18~22.04.1","6.8.0-1019.19~22.04.1","6.8.0-1023.23~22.04.1"]},{"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-58.60.1~22.04.1"}]}],"versions":["6.8.0-38.38.1~22.04.2","6.8.0-40.40.1~22.04.1","6.8.0-44.44.1~22.04.1","6.8.0-45.45.1~22.04.1","6.8.0-47.47.1~22.04.1","6.8.0-48.48.3~22.04.1","6.8.0-49.49.1~22.04.1","6.8.0-50.51.1~22.04.1","6.8.0-51.52.1~22.04.1","6.8.0-52.53.1~22.04.1","6.8.0-54.56.1~22.04.1","6.8.0-55.57.1~22.04.1","6.8.0-56.58.1~22.04.1","6.8.0-57.59.1~22.04.1"]},{"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-1026.29~22.04.1"}]}],"versions":["6.8.0-1008.8~22.04.1","6.8.0-1009.9~22.04.1","6.8.0-1010.10~22.04.1","6.8.0-1011.11~22.04.1","6.8.0-1012.12~22.04.1","6.8.0-1013.14~22.04.1","6.8.0-1014.15~22.04.1","6.8.0-1015.16~22.04.1","6.8.0-1017.19~22.04.1","6.8.0-1018.20~22.04.1","6.8.0-1019.21~22.04.1","6.8.0-1020.22~22.04.1","6.8.0-1021.23~22.04.1","6.8.0-1022.25~22.04.2","6.8.0-1023.26~22.04.1","6.8.0-1024.27~22.04.1","6.8.0-1025.28~22.04.1"]},{"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-1024.25~22.04.1"}]}],"versions":["6.8.0-1006.6~22.04.3","6.8.0-1008.8~22.04.1","6.8.0-1010.10~22.04.1","6.8.0-1011.11~22.04.1","6.8.0-1012.12~22.04.1","6.8.0-1013.13~22.04.1","6.8.0-1014.14~22.04.1","6.8.0-1015.15~22.04.1","6.8.0-1016.17~22.04.1","6.8.0-1017.18~22.04.1","6.8.0-1018.19~22.04.1","6.8.0-1019.20~22.04.1","6.8.0-1020.21~22.04.1","6.8.0-1021.22~22.04.1","6.8.0-1022.23~22.04.1","6.8.0-1023.24~22.04.1"]},{"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-58.60.1~22.04.1"}]}],"versions":["6.8.0-38.38.1~22.04.1","6.8.0-39.39.1~22.04.1","6.8.0-40.40.1~22.04.1","6.8.0-41.41.1~22.04.1","6.8.0-44.44.1~22.04.1","6.8.0-47.47.1~22.04.1","6.8.0-48.48.1~22.04.2","6.8.0-49.49.1~22.04.1","6.8.0-50.51.1~22.04.1","6.8.0-51.52.1~22.04.1","6.8.0-52.53.1~22.04.1","6.8.0-53.55.1~22.04.1","6.8.0-55.57.1~22.04.1","6.8.0-56.58.1~22.04.1","6.8.0-57.59.1~22.04.1"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-starfive-5.19","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.19.0-1014.16~22.04.1","5.19.0-1015.17~22.04.1","5.19.0-1016.18~22.04.1","5.19.0-1017.19~22.04.1","5.19.0-1018.20~22.04.1","5.19.0-1019.21~22.04.1","5.19.0-1020.22~22.04.1"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-starfive-6.2","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["6.2.0-1006.7~22.04.1","6.2.0-1007.8~22.04.1","6.2.0-1009.10~22.04.1"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-starfive-6.5","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["6.5.0-1007.8~22.04.1","6.5.0-1008.9~22.04.1","6.5.0-1009.10~22.04.1","6.5.0-1010.11~22.04.1","6.5.0-1011.12~22.04.1","6.5.0-1012.13~22.04.1","6.5.0-1014.15~22.04.1","6.5.0-1015.16~22.04.1","6.5.0-1016.17~22.04.1","6.5.0-1017.18~22.04.1","6.5.0-1018.19~22.04.1"]},{"source":"osv","ecosystem":"Ubuntu:Pro:Realtime:22.04:LTS","package":"linux-realtime-6.8","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.1-1020.21~22.04.1"}]}],"versions":["6.8.1-1004.4~22.04.1","6.8.1-1005.5~22.04.2","6.8.1-1006.6~22.04.1","6.8.1-1007.7~22.04.1","6.8.1-1008.8~22.04.1","6.8.1-1009.9~22.04.1","6.8.1-1010.10~22.04.1","6.8.1-1011.11~22.04.1","6.8.1-1012.12~22.04.1","6.8.1-1013.14~22.04.1","6.8.1-1014.15~22.04.1","6.8.1-1015.16~22.04.1","6.8.1-1016.17~22.04.1","6.8.1-1017.18~22.04.1","6.8.1-1018.19~22.04.1","6.8.1-1019.20~22.04.1"]},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-58.60"}]}],"versions":["6.5.0-9.9","6.6.0-14.14","6.8.0-11.11","6.8.0-20.20","6.8.0-22.22","6.8.0-28.28","6.8.0-31.31","6.8.0-35.35","6.8.0-36.36","6.8.0-38.38","6.8.0-39.39","6.8.0-40.40","6.8.0-41.41","6.8.0-44.44","6.8.0-45.45","6.8.0-47.47","6.8.0-48.48","6.8.0-49.49","6.8.0-50.51","6.8.0-51.52","6.8.0-52.53","6.8.0-53.55","6.8.0-54.56","6.8.0-55.57","6.8.0-56.58","6.8.0-57.59"]},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-aws","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1027.29"}]}],"versions":["6.5.0-1008.8","6.6.0-1001.1","6.8.0-1001.1","6.8.0-1006.6","6.8.0-1008.8","6.8.0-1009.9","6.8.0-1010.10","6.8.0-1011.12","6.8.0-1012.13","6.8.0-1013.14","6.8.0-1014.15","6.8.0-1015.16","6.8.0-1016.17","6.8.0-1017.18","6.8.0-1018.20","6.8.0-1019.21","6.8.0-1020.22","6.8.0-1021.23","6.8.0-1023.25","6.8.0-1024.26","6.8.0-1025.27","6.8.0-1026.28"]},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-azure","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1027.32"}]}],"versions":["6.5.0-1007.7","6.6.0-1001.1","6.8.0-1001.1","6.8.0-1005.5","6.8.0-1006.6","6.8.0-1007.7","6.8.0-1008.8","6.8.0-1009.9","6.8.0-1010.10","6.8.0-1012.14","6.8.0-1013.15","6.8.0-1014.16","6.8.0-1015.17","6.8.0-1016.18","6.8.0-1017.20","6.8.0-1018.21","6.8.0-1020.23","6.8.0-1021.25","6.8.0-1025.30","6.8.0-1026.31"]},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-azure-6.11","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.11.0-1012.12~24.04.1"}]}],"versions":["6.11.0-1008.8~24.04.1"]},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-azure-nvidia","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1014.15"}]}],"versions":["6.8.0-1013.14"]},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-gcp","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1028.30"}]}],"versions":["6.5.0-1007.7","6.6.0-1001.1","6.8.0-1002.2","6.8.0-1005.5","6.8.0-1006.6","6.8.0-1007.7","6.8.0-1008.9","6.8.0-1009.10","6.8.0-1010.11","6.8.0-1011.12","6.8.0-1012.13","6.8.0-1013.14","6.8.0-1014.16","6.8.0-1015.17","6.8.0-1016.18","6.8.0-1017.19","6.8.0-1018.20","6.8.0-1019.21","6.8.0-1020.22","6.8.0-1021.23","6.8.0-1024.26","6.8.0-1025.27","6.8.0-1026.28","6.8.0-1027.29"]},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-gcp-6.11","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.11.0-1011.11~24.04.1"}]}],"versions":["6.11.0-1006.6~24.04.2"]},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-gke","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1023.27"}]}],"versions":["6.8.0-1003.5","6.8.0-1004.7","6.8.0-1005.8","6.8.0-1006.9","6.8.0-1007.10","6.8.0-1008.11","6.8.0-1009.12","6.8.0-1010.13","6.8.0-1011.14","6.8.0-1012.15","6.8.0-1013.17","6.8.0-1014.18","6.8.0-1015.19","6.8.0-1016.20","6.8.0-1017.21","6.8.0-1019.23","6.8.0-1020.24","6.8.0-1021.25","6.8.0-1022.26"]},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-gkeop","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1010.12"}]}],"versions":["6.8.0-1001.3","6.8.0-1002.4","6.8.0-1003.5","6.8.0-1004.6","6.8.0-1006.8","6.8.0-1007.9","6.8.0-1008.10","6.8.0-1009.11"]},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-ibm","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1024.24"}]}],"versions":["6.5.0-1009.9","6.8.0-1001.1","6.8.0-1003.3","6.8.0-1004.4","6.8.0-1005.5","6.8.0-1006.6","6.8.0-1007.7","6.8.0-1008.8","6.8.0-1009.9","6.8.0-1010.10","6.8.0-1011.11","6.8.0-1012.12","6.8.0-1013.13","6.8.0-1014.14","6.8.0-1015.15","6.8.0-1016.16","6.8.0-1017.17","6.8.0-1018.18","6.8.0-1019.19","6.8.0-1022.22","6.8.0-1023.23"]},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-lowlatency","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-58.60.1"}]}],"versions":["6.5.0-9.9.1","6.6.0-14.14.1","6.8.0-7.7.1","6.8.0-25.25.3","6.8.0-28.28.1","6.8.0-31.31.1","6.8.0-35.35.1","6.8.0-36.36.1","6.8.0-38.38.1","6.8.0-39.39.1","6.8.0-40.40.1","6.8.0-41.41.1","6.8.0-44.44.1","6.8.0-45.45.1","6.8.0-47.47.1","6.8.0-48.48.3","6.8.0-49.49.1","6.8.0-50.51.1","6.8.0-51.52.1","6.8.0-52.53.1","6.8.0-53.55.2","6.8.0-54.56.1","6.8.0-55.57.1","6.8.0-56.58.1","6.8.0-57.59.1"]},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-nvidia","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1026.29"}]}],"versions":["6.8.0-1007.7","6.8.0-1008.8","6.8.0-1009.9","6.8.0-1010.10","6.8.0-1011.11","6.8.0-1012.12","6.8.0-1013.14","6.8.0-1014.15","6.8.0-1015.16","6.8.0-1017.19","6.8.0-1018.20","6.8.0-1019.21","6.8.0-1020.22","6.8.0-1021.23","6.8.0-1022.25","6.8.0-1023.26","6.8.0-1024.27","6.8.0-1025.28"]},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-nvidia-6.11","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.11.0-1007.7"}]}],"versions":["6.11.0-1002.2","6.11.0-1003.3"]},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-nvidia-lowlatency","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1026.29.1"}]}],"versions":["6.8.0-1009.9.1","6.8.0-1011.11.1","6.8.0-1012.12.1","6.8.0-1013.14.1","6.8.0-1014.15.1","6.8.0-1015.16.1","6.8.0-1017.19.1","6.8.0-1018.20.1","6.8.0-1019.21.1","6.8.0-1020.22.1","6.8.0-1021.23.1","6.8.0-1022.25.2","6.8.0-1023.26.1","6.8.0-1024.27.1","6.8.0-1025.28.1"]},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-nvidia-tegra","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1008.8"}]}],"versions":["6.8.0-1003.3","6.8.0-1004.4"]},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-oem-6.11","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.11.0-1015.15"}]}],"versions":["6.11.0-1007.7","6.11.0-1008.8","6.11.0-1009.9","6.11.0-1010.10","6.11.0-1011.11","6.11.0-1012.12","6.11.0-1013.13"]},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-oem-6.8","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1026.26"}]}],"versions":["6.8.0-1003.3","6.8.0-1004.4","6.8.0-1005.5","6.8.0-1006.6","6.8.0-1007.7","6.8.0-1008.8","6.8.0-1009.9","6.8.0-1010.10","6.8.0-1011.11","6.8.0-1012.12","6.8.0-1013.13","6.8.0-1014.14","6.8.0-1016.16","6.8.0-1017.17","6.8.0-1018.18","6.8.0-1019.19","6.8.0-1020.20","6.8.0-1024.24","6.8.0-1025.25"]},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-oracle","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1024.25"}]}],"versions":["6.5.0-1010.10","6.6.0-1001.1","6.8.0-1001.1","6.8.0-1004.4","6.8.0-1005.5","6.8.0-1006.6","6.8.0-1008.8","6.8.0-1010.10","6.8.0-1011.11","6.8.0-1012.12","6.8.0-1013.13","6.8.0-1014.14","6.8.0-1015.16","6.8.0-1016.17","6.8.0-1017.18","6.8.0-1018.19","6.8.0-1019.20","6.8.0-1020.21","6.8.0-1021.22","6.8.0-1022.23","6.8.0-1023.24"]},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-raspi","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1028.32"}]}],"versions":["6.5.0-1005.7","6.7.0-1001.1","6.8.0-1001.1","6.8.0-1002.2","6.8.0-1003.3","6.8.0-1004.4","6.8.0-1005.5","6.8.0-1006.6","6.8.0-1007.7","6.8.0-1008.8","6.8.0-1009.10","6.8.0-1010.11","6.8.0-1011.12","6.8.0-1012.13","6.8.0-1013.14","6.8.0-1014.16","6.8.0-1015.17","6.8.0-1016.18","6.8.0-1017.19","6.8.0-1018.20","6.8.0-1019.23","6.8.0-1020.24","6.8.0-1024.28"]},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-raspi-realtime","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["6.8.0-2019.20"]},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-realtime","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["6.8.1-1015.16"]},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-riscv","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-58.60.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","6.8.0-48.48.1","6.8.0-49.49.1","6.8.0-50.51.1","6.8.0-51.52.1","6.8.0-52.53.1","6.8.0-53.55.1","6.8.0-55.57.1","6.8.0-56.58.1","6.8.0-57.59.1"]},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-xilinx","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1017.18"}]}],"versions":["6.8.0-1008.9","6.8.0-1009.10","6.8.0-1011.12","6.8.0-1012.13","6.8.0-1013.14","6.8.0-1014.15","6.8.0-1015.16"]},{"source":"osv","ecosystem":"Ubuntu:Pro:Realtime:24.04:LTS","package":"linux-raspi-realtime","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-2023.24"}]}],"versions":["6.7.0-2001.1","6.8.0-2001.1","6.8.0-2002.2","6.8.0-2004.4","6.8.0-2005.5","6.8.0-2006.6","6.8.0-2007.7","6.8.0-2008.8","6.8.0-2009.9","6.8.0-2010.10","6.8.0-2011.11","6.8.0-2012.12","6.8.0-2013.14","6.8.0-2014.15","6.8.0-2015.16","6.8.0-2016.17","6.8.0-2017.18","6.8.0-2018.19","6.8.0-2019.20","6.8.0-2022.23"]},{"source":"osv","ecosystem":"Ubuntu:Pro:Realtime:24.04:LTS","package":"linux-realtime","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.1-1020.21"}]}],"versions":["6.8.0-1008.19","6.8.1-1001.1","6.8.1-1002.2","6.8.1-1003.3","6.8.1-1004.4","6.8.1-1005.5","6.8.1-1006.6","6.8.1-1007.7","6.8.1-1008.8","6.8.1-1009.9","6.8.1-1010.10","6.8.1-1011.11","6.8.1-1012.12","6.8.1-1013.14","6.8.1-1014.15","6.8.1-1015.16","6.8.1-1016.17","6.8.1-1017.18","6.8.1-1018.19","6.8.1-1019.20"]},{"source":"osv","ecosystem":"Ubuntu:Pro:FIPS-updates:24.04:LTS","package":"linux-fips","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-78.78+fips1"}]}],"versions":["6.8.0-38.38+fips4"]},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-oem-6.11","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.11.0-1015.15"}]}],"versions":["6.11.0-1007.7","6.11.0-1008.8","6.11.0-1009.9","6.11.0-1010.10","6.11.0-1011.11","6.11.0-1012.12","6.11.0-1013.13"],"bundled":730},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-azure-6.8","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1027.32~22.04.1"}]}],"versions":["6.8.0-1008.8~22.04.1","6.8.0-1009.9~22.04.1","6.8.0-1010.10~22.04.1","6.8.0-1012.14~22.04.1","6.8.0-1013.15~22.04.1","6.8.0-1014.16~22.04.1","6.8.0-1015.17~22.04.2","6.8.0-1017.20~22.04.1","6.8.0-1018.21~22.04.1","6.8.0-1020.23~22.04.1","6.8.0-1021.25~22.04.1","6.8.0-1025.30~22.04.1","6.8.0-1026.31~22.04.1"],"bundled":461},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-lowlatency-hwe-6.8","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-58.60.1~22.04.1"}]}],"versions":["6.8.0-38.38.1~22.04.2","6.8.0-40.40.1~22.04.1","6.8.0-44.44.1~22.04.1","6.8.0-45.45.1~22.04.1","6.8.0-47.47.1~22.04.1","6.8.0-48.48.3~22.04.1","6.8.0-49.49.1~22.04.1","6.8.0-50.51.1~22.04.1","6.8.0-51.52.1~22.04.1","6.8.0-52.53.1~22.04.1","6.8.0-54.56.1~22.04.1","6.8.0-55.57.1~22.04.1","6.8.0-56.58.1~22.04.1","6.8.0-57.59.1~22.04.1"],"bundled":461},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-nvidia-6.8","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1026.29~22.04.1"}]}],"versions":["6.8.0-1008.8~22.04.1","6.8.0-1009.9~22.04.1","6.8.0-1010.10~22.04.1","6.8.0-1011.11~22.04.1","6.8.0-1012.12~22.04.1","6.8.0-1013.14~22.04.1","6.8.0-1014.15~22.04.1","6.8.0-1015.16~22.04.1","6.8.0-1017.19~22.04.1","6.8.0-1018.20~22.04.1","6.8.0-1019.21~22.04.1","6.8.0-1020.22~22.04.1","6.8.0-1021.23~22.04.1","6.8.0-1022.25~22.04.2","6.8.0-1023.26~22.04.1","6.8.0-1024.27~22.04.1","6.8.0-1025.28~22.04.1"],"bundled":461},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-oracle-6.8","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1024.25~22.04.1"}]}],"versions":["6.8.0-1006.6~22.04.3","6.8.0-1008.8~22.04.1","6.8.0-1010.10~22.04.1","6.8.0-1011.11~22.04.1","6.8.0-1012.12~22.04.1","6.8.0-1013.13~22.04.1","6.8.0-1014.14~22.04.1","6.8.0-1015.15~22.04.1","6.8.0-1016.17~22.04.1","6.8.0-1017.18~22.04.1","6.8.0-1018.19~22.04.1","6.8.0-1019.20~22.04.1","6.8.0-1020.21~22.04.1","6.8.0-1021.22~22.04.1","6.8.0-1022.23~22.04.1","6.8.0-1023.24~22.04.1"],"bundled":461},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-58.60"}]}],"versions":["6.5.0-9.9","6.6.0-14.14","6.8.0-11.11","6.8.0-20.20","6.8.0-22.22","6.8.0-28.28","6.8.0-31.31","6.8.0-35.35","6.8.0-36.36","6.8.0-38.38","6.8.0-39.39","6.8.0-40.40","6.8.0-41.41","6.8.0-44.44","6.8.0-45.45","6.8.0-47.47","6.8.0-48.48","6.8.0-49.49","6.8.0-50.51","6.8.0-51.52","6.8.0-52.53","6.8.0-53.55","6.8.0-54.56","6.8.0-55.57","6.8.0-56.58","6.8.0-57.59"],"bundled":461},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-aws","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1027.29"}]}],"versions":["6.5.0-1008.8","6.6.0-1001.1","6.8.0-1001.1","6.8.0-1006.6","6.8.0-1008.8","6.8.0-1009.9","6.8.0-1010.10","6.8.0-1011.12","6.8.0-1012.13","6.8.0-1013.14","6.8.0-1014.15","6.8.0-1015.16","6.8.0-1016.17","6.8.0-1017.18","6.8.0-1018.20","6.8.0-1019.21","6.8.0-1020.22","6.8.0-1021.23","6.8.0-1023.25","6.8.0-1024.26","6.8.0-1025.27","6.8.0-1026.28"],"bundled":461},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-azure","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1027.32"}]}],"versions":["6.5.0-1007.7","6.6.0-1001.1","6.8.0-1001.1","6.8.0-1005.5","6.8.0-1006.6","6.8.0-1007.7","6.8.0-1008.8","6.8.0-1009.9","6.8.0-1010.10","6.8.0-1012.14","6.8.0-1013.15","6.8.0-1014.16","6.8.0-1015.17","6.8.0-1016.18","6.8.0-1017.20","6.8.0-1018.21","6.8.0-1020.23","6.8.0-1021.25","6.8.0-1025.30","6.8.0-1026.31"],"bundled":461},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-ibm","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1024.24"}]}],"versions":["6.5.0-1009.9","6.8.0-1001.1","6.8.0-1003.3","6.8.0-1004.4","6.8.0-1005.5","6.8.0-1006.6","6.8.0-1007.7","6.8.0-1008.8","6.8.0-1009.9","6.8.0-1010.10","6.8.0-1011.11","6.8.0-1012.12","6.8.0-1013.13","6.8.0-1014.14","6.8.0-1015.15","6.8.0-1016.16","6.8.0-1017.17","6.8.0-1018.18","6.8.0-1019.19","6.8.0-1022.22","6.8.0-1023.23"],"bundled":461},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-lowlatency","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-58.60.1"}]}],"versions":["6.5.0-9.9.1","6.6.0-14.14.1","6.8.0-7.7.1","6.8.0-25.25.3","6.8.0-28.28.1","6.8.0-31.31.1","6.8.0-35.35.1","6.8.0-36.36.1","6.8.0-38.38.1","6.8.0-39.39.1","6.8.0-40.40.1","6.8.0-41.41.1","6.8.0-44.44.1","6.8.0-45.45.1","6.8.0-47.47.1","6.8.0-48.48.3","6.8.0-49.49.1","6.8.0-50.51.1","6.8.0-51.52.1","6.8.0-52.53.1","6.8.0-53.55.2","6.8.0-54.56.1","6.8.0-55.57.1","6.8.0-56.58.1","6.8.0-57.59.1"],"bundled":461},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-nvidia","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1026.29"}]}],"versions":["6.8.0-1007.7","6.8.0-1008.8","6.8.0-1009.9","6.8.0-1010.10","6.8.0-1011.11","6.8.0-1012.12","6.8.0-1013.14","6.8.0-1014.15","6.8.0-1015.16","6.8.0-1017.19","6.8.0-1018.20","6.8.0-1019.21","6.8.0-1020.22","6.8.0-1021.23","6.8.0-1022.25","6.8.0-1023.26","6.8.0-1024.27","6.8.0-1025.28"],"bundled":461},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-nvidia-lowlatency","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1026.29.1"}]}],"versions":["6.8.0-1009.9.1","6.8.0-1011.11.1","6.8.0-1012.12.1","6.8.0-1013.14.1","6.8.0-1014.15.1","6.8.0-1015.16.1","6.8.0-1017.19.1","6.8.0-1018.20.1","6.8.0-1019.21.1","6.8.0-1020.22.1","6.8.0-1021.23.1","6.8.0-1022.25.2","6.8.0-1023.26.1","6.8.0-1024.27.1","6.8.0-1025.28.1"],"bundled":461},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-oem-6.8","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1026.26"}]}],"versions":["6.8.0-1003.3","6.8.0-1004.4","6.8.0-1005.5","6.8.0-1006.6","6.8.0-1007.7","6.8.0-1008.8","6.8.0-1009.9","6.8.0-1010.10","6.8.0-1011.11","6.8.0-1012.12","6.8.0-1013.13","6.8.0-1014.14","6.8.0-1016.16","6.8.0-1017.17","6.8.0-1018.18","6.8.0-1019.19","6.8.0-1020.20","6.8.0-1024.24","6.8.0-1025.25"],"bundled":461},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-oracle","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1024.25"}]}],"versions":["6.5.0-1010.10","6.6.0-1001.1","6.8.0-1001.1","6.8.0-1004.4","6.8.0-1005.5","6.8.0-1006.6","6.8.0-1008.8","6.8.0-1010.10","6.8.0-1011.11","6.8.0-1012.12","6.8.0-1013.13","6.8.0-1014.14","6.8.0-1015.16","6.8.0-1016.17","6.8.0-1017.18","6.8.0-1018.19","6.8.0-1019.20","6.8.0-1020.21","6.8.0-1021.22","6.8.0-1022.23","6.8.0-1023.24"],"bundled":461},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-hwe-6.8","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-58.60~22.04.1"}]}],"versions":["6.8.0-38.38~22.04.1","6.8.0-39.39~22.04.1","6.8.0-40.40~22.04.3","6.8.0-45.45~22.04.1","6.8.0-47.47~22.04.1","6.8.0-48.48~22.04.1","6.8.0-49.49~22.04.1","6.8.0-50.51~22.04.1","6.8.0-51.52~22.04.1","6.8.0-52.53~22.04.1","6.8.0-57.59~22.04.1"],"bundled":461},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-gcp","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1028.30"}]}],"versions":["6.5.0-1007.7","6.6.0-1001.1","6.8.0-1002.2","6.8.0-1005.5","6.8.0-1006.6","6.8.0-1007.7","6.8.0-1008.9","6.8.0-1009.10","6.8.0-1010.11","6.8.0-1011.12","6.8.0-1012.13","6.8.0-1013.14","6.8.0-1014.16","6.8.0-1015.17","6.8.0-1016.18","6.8.0-1017.19","6.8.0-1018.20","6.8.0-1019.21","6.8.0-1020.22","6.8.0-1021.23","6.8.0-1024.26","6.8.0-1025.27","6.8.0-1026.28","6.8.0-1027.29"],"bundled":460},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-gke","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1023.27"}]}],"versions":["6.8.0-1003.5","6.8.0-1004.7","6.8.0-1005.8","6.8.0-1006.9","6.8.0-1007.10","6.8.0-1008.11","6.8.0-1009.12","6.8.0-1010.13","6.8.0-1011.14","6.8.0-1012.15","6.8.0-1013.17","6.8.0-1014.18","6.8.0-1015.19","6.8.0-1016.20","6.8.0-1017.21","6.8.0-1019.23","6.8.0-1020.24","6.8.0-1021.25","6.8.0-1022.26"],"bundled":460},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-gkeop","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1010.12"}]}],"versions":["6.8.0-1001.3","6.8.0-1002.4","6.8.0-1003.5","6.8.0-1004.6","6.8.0-1006.8","6.8.0-1007.9","6.8.0-1008.10","6.8.0-1009.11"],"bundled":460},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-aws-6.8","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1027.29~22.04.1"}]}],"versions":["6.8.0-1009.9~22.04.2","6.8.0-1010.10~22.04.2","6.8.0-1011.12~22.04.1","6.8.0-1013.14~22.04.1","6.8.0-1014.15~22.04.1","6.8.0-1015.16~22.04.1","6.8.0-1016.17~22.04.2","6.8.0-1017.18~22.04.1","6.8.0-1018.19~22.04.1","6.8.0-1019.21~22.04.1","6.8.0-1020.22~22.04.1","6.8.0-1021.23~22.04.1","6.8.0-1023.25~22.04.1","6.8.0-1024.26~22.04.1"],"bundled":577},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-gcp-6.8","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1028.30~22.04.1"}]}],"versions":["6.8.0-1010.11~22.04.1","6.8.0-1011.12~22.04.1","6.8.0-1012.13~22.04.1","6.8.0-1013.14~22.04.1","6.8.0-1014.16~22.04.1","6.8.0-1015.17~22.04.1","6.8.0-1016.18~22.04.1","6.8.0-1017.19~22.04.1","6.8.0-1018.20~22.04.1","6.8.0-1019.21~22.04.1","6.8.0-1020.22~22.04.1","6.8.0-1021.23~22.04.1","6.8.0-1024.26~22.04.1","6.8.0-1025.27~22.04.1","6.8.0-1026.28~22.04.1","6.8.0-1027.29~22.04.1"],"bundled":460},{"source":"osv","ecosystem":"Ubuntu:Pro:Realtime:24.04:LTS","package":"linux-realtime","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.1-1020.21"}]}],"versions":["6.8.0-1008.19","6.8.1-1001.1","6.8.1-1002.2","6.8.1-1003.3","6.8.1-1004.4","6.8.1-1005.5","6.8.1-1006.6","6.8.1-1007.7","6.8.1-1008.8","6.8.1-1009.9","6.8.1-1010.10","6.8.1-1011.11","6.8.1-1012.12","6.8.1-1013.14","6.8.1-1014.15","6.8.1-1015.16","6.8.1-1016.17","6.8.1-1017.18","6.8.1-1018.19","6.8.1-1019.20"],"bundled":461},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-azure-nvidia","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1014.15"}]}],"versions":["6.8.0-1013.14"],"bundled":739},{"source":"osv","ecosystem":"Ubuntu:Pro:Realtime:24.04:LTS","package":"linux-raspi-realtime","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-2023.24"}]}],"versions":["6.7.0-2001.1","6.8.0-2001.1","6.8.0-2002.2","6.8.0-2004.4","6.8.0-2005.5","6.8.0-2006.6","6.8.0-2007.7","6.8.0-2008.8","6.8.0-2009.9","6.8.0-2010.10","6.8.0-2011.11","6.8.0-2012.12","6.8.0-2013.14","6.8.0-2014.15","6.8.0-2015.16","6.8.0-2016.17","6.8.0-2017.18","6.8.0-2018.19","6.8.0-2019.20","6.8.0-2022.23"],"bundled":704},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-raspi","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1028.32"}]}],"versions":["6.5.0-1005.7","6.7.0-1001.1","6.8.0-1001.1","6.8.0-1002.2","6.8.0-1003.3","6.8.0-1004.4","6.8.0-1005.5","6.8.0-1006.6","6.8.0-1007.7","6.8.0-1008.8","6.8.0-1009.10","6.8.0-1010.11","6.8.0-1011.12","6.8.0-1012.13","6.8.0-1013.14","6.8.0-1014.16","6.8.0-1015.17","6.8.0-1016.18","6.8.0-1017.19","6.8.0-1018.20","6.8.0-1019.23","6.8.0-1020.24","6.8.0-1024.28"],"bundled":705}],"products":[{"vendor":"linux","product":"linux"},{"vendor":"linux","product":"linux_kernel"}],"references":[{"url":"https://git.kernel.org/stable/c/3be34fa1cdbf180c1a948cfededfdf2cdc497199","tags":["Patch","web","report"]},{"url":"https://git.kernel.org/stable/c/bd89d94f3ea6fdaee983cbc69226a00b9bde6d59","tags":["Patch","web","report"]},{"url":"https://git.kernel.org/stable/c/ecda483339a5151e3ca30d6b82691ef6f1d17912","tags":["Patch","web","report"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-53232","tags":["advisory"]},{"url":"https://github.com/advisories/GHSA-c86m-78v8-4hvw"},{"url":"https://docs.bell-sw.com/security/cves/CVE-2024-53232","tags":["advisory"]},{"url":"https://github.com/CVEProject/cvelistV5/tree/main/cves/2024/53xxx/CVE-2024-53232.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-53232","tags":["advisory"]},{"url":"https://www.openeuler.org/zh/security/security-bulletins/detail/?id=openEuler-SA-2026-1759","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-37900","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-37954","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-38083","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-38373","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-38556","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-38591","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-38659","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-38730","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-39713","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-39961","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-40030","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-40096","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-40215","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-40220","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-40237","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-40242","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-40251","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-40271","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-40272","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-40277","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-40294","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-40301","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-40308","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-40318","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-40341","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-40342","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-40343","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-40346","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-40351","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-40358","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-40359","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-40361","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-68171","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-68173","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-68174","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-68176","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-68188","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-68200","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-68206","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-68208","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-68214","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-68235","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-68259","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-68261","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-68264","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-68265","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-68297","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-68309","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-68331","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-68337","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-68349","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-68354","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-68356","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-68362","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-68363","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-68376","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-68378","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-68724","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-68725","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-68734","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-68741","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-68744","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-68745","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-68756","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-68780","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-68782","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-68794","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-68803","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-68814","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-68816","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-68818","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-71072","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-71104","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-71116","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-71131","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-71147","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-71149","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-71150","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-22996","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-22998","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-23000","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-23005","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-23035","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-23138","tags":["advisory"]},{"url":"https://www.openeuler.org/zh/security/security-bulletins/detail/?id=openEuler-SA-2026-1760","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-68817","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-71077","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-71134","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-71152","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-71154","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-71238","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-22978","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-22980","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-22990","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-22992","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-23060","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-23069","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-23071","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-23086","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-23099","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-23103","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-23105","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-23111","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-23120","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-23124","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-23126","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-23133","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-23136","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-23137","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-23139","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-23145","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-23154","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-23156","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-23169","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-23173","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-23191","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-23198","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-23204","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-23208","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-23212","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-23221","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-23230","tags":["advisory"]},{"url":"https://www.openeuler.org/zh/security/security-bulletins/detail/?id=openEuler-SA-2026-1761","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-68301","tags":["advisory"]},{"url":"https://access.redhat.com/errata/RHBA-2025:6279","tags":["advisory"]},{"url":"https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/10/html/10.0_release_notes/index","tags":["article"]},{"url":"https://issues.redhat.com/browse/RHEL-65347","tags":["article"]},{"url":"https://issues.redhat.com/browse/RHEL-65818","tags":["article"]},{"url":"https://issues.redhat.com/browse/RHEL-72036","tags":["article"]},{"url":"https://issues.redhat.com/browse/RHEL-73163","tags":["article"]},{"url":"https://security.access.redhat.com/data/csaf/v2/advisories/2025/rhba-2025_6279.json","tags":["advisory"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-53232","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2334410","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-53232","tags":["advisory","report"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024122737-CVE-2024-53232-6919@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2025-71151","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2432362","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2025-71151","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-71151","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2026012328-CVE-2025-71151-1a45@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/errata/RHSA-2025:6966","tags":["advisory"]},{"url":"https://docs.redhat.com/en/documentation/red_hat_enterprise_linux/9/html/9.6_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=2278283","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2280464","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2281340","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2281687","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2281827","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2281829","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2281879","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2281905","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2281907","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2281909","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2281912","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2281914","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2282952","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2282955","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2282959","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2284280","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2292324","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2293458","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2297472","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2297540","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2298411","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2300437","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2301498","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2307840","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2307862","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2307871","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2307883","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2307887","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2307888","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2307889","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2307891","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2309783","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2309789","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2309795","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2309838","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2309850","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2309852","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2309863","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2311706","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2311707","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2311713","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2311719","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2312061","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2312063","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2312108","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2313053","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2313054","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2313055","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2313056","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2313091","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2313093","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2313095","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2313098","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2313102","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2313104","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2313106","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2313107","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2313109","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2313131","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2313134","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2313135","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2313148","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2315156","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2315157","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2315158","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2315171","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2315172","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2315174","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2315180","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2315187","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2315191","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2315205","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2315216","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2317581","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2317584","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2317601","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2320168","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2320169","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2320173","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2320187","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2320200","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2320209","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2320210","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2320212","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2320213","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2320214","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2320220","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2320225","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2320235","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2320238","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2320239","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2320240","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2320242","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2320245","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2320246","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2320248","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2320249","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2320268","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2320274","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2320425","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2320432","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2320443","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2320454","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2320459","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2320462","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2320468","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2320471","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2320475","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2320480","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2320481","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2320484","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2320486","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2320488","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2320489","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2320497","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2320500","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2320501","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2320502","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2320503","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2320506","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2320509","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2320510","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2320515","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2320520","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2320527","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2320529","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2320531","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2320541","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2320543","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2320544","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2320546","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2320547","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2320549","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2320550","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2320552","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2320554","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2320556","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2320557","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2320559","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2320562","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2320563","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2320565","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2320570","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2320571","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2320572","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2320573","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2320574","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2320576","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2320577","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2320586","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2320587","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2320589","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2320590","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2320594","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2320596","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2320598","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2320601","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2320602","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2320610","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2320611","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2320612","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2320615","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2320620","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2320625","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2320629","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2320635","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2320636","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2320658","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2320670","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2320693","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2320707","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2320781","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2322072","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2322303","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2322308","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2322310","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2322312","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2322316","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2322320","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2322323","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2323905","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2323909","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2323918","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2323924","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2323927","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2323929","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2323932","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2323933","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2323938","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2323945","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2323947","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2323950","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2323953","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2324317","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2324320","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2324321","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2324324","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2324325","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2324410","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2324413","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2324419","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2324423","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2324548","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2324566","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2324578","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2324599","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2324610","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2324617","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2324645","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2324650","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2324853","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2324865","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2324869","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2324874","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2324875","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2324889","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2324897","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2324899","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2324901","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2327174","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2327182","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2327189","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2327190","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2327194","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2327332","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2327335","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2327338","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2327343","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2327344","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2327349","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2327358","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2327361","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2327362","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2327365","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2327369","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2327370","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2327373","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2327381","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2327383","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2327888","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2327890","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2327893","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2328791","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2328792","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2329818","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2329919","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2329927","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2329928","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2329929","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2329930","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2329935","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2329936","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2329937","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2330346","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2330357","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2330765","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2333973","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2333974","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2333976","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2333977","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2333982","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2334350","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2334367","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2334373","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2334384","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2334386","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2334388","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2334392","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2334398","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2334399","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2334408","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2334409","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2334419","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2334426","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2334430","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2334432","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2334441","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2334458","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2334461","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2334463","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2334469","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2334472","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2334479","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2334483","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2334486","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2334495","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2334501","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2334503","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2334528","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2334538","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2334539","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2334542","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2334551","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2334561","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2334562","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2334563","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2334573","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2334575","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2334577","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2334667","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2334683","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2334809","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2335899","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2335906","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2336546","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2336550","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2337104","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2337113","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2337117","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2337118","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2337136","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2337148","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2337152","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2337328","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2337333","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2338195","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2338197","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2338199","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2338204","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2338208","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2338214","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2338830","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2338858","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2339126","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2339140","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2339143","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2343169","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2343173","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2343183","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2344683","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2345243","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2345615","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2362882","tags":["report"]},{"url":"https://issues.redhat.com/browse/RHEL-12439","tags":["article"]},{"url":"https://issues.redhat.com/browse/RHEL-28791","tags":["article"]},{"url":"https://issues.redhat.com/browse/RHEL-58641","tags":["article"]},{"url":"https://issues.redhat.com/browse/RHEL-60028","tags":["article"]},{"url":"https://issues.redhat.com/browse/RHEL-61203","tags":["article"]},{"url":"https://issues.redhat.com/browse/RHEL-62339","tags":["article"]},{"url":"https://issues.redhat.com/browse/RHEL-67304","tags":["article"]},{"url":"https://issues.redhat.com/browse/RHEL-71541","tags":["article"]},{"url":"https://issues.redhat.com/browse/RHEL-8810","tags":["article"]},{"url":"https://issues.redhat.com/browse/RHEL-9279","tags":["article"]},{"url":"https://security.access.redhat.com/data/csaf/v2/advisories/2025/rhsa-2025_6966.json","tags":["advisory"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-48969","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-48969","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-48969","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024102144-CVE-2022-48969-8fe7@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-48989","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-48989","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-48989","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024102148-CVE-2022-48989-54c3@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-49006","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-49006","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-49006","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024102151-CVE-2022-49006-83c9@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-49014","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-49014","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-49014","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024102153-CVE-2022-49014-1627@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-49029","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-49029","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-49029","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024102155-CVE-2022-49029-0ffd@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-49747","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2355435","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-49747","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-49747","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025032759-CVE-2022-49747-f361@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-49778","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2363427","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-49778","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-49778","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025050118-CVE-2022-49778-ea15@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-49804","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2363456","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-49804","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-49804","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025050127-CVE-2022-49804-0866@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-49815","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2363358","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-49815","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-49815","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025050131-CVE-2022-49815-ebd2@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-50112","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2373669","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-50112","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-50112","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025061808-CVE-2022-50112-e37e@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-50121","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2373534","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-50121","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-50121","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025061811-CVE-2022-50121-7e33@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-50159","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2373696","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-50159","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-50159","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025061825-CVE-2022-50159-a387@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-50214","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2373513","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-50214","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-50214","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025061844-CVE-2022-50214-6569@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-50319","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2395312","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-50319","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-50319","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025091553-CVE-2022-50319-6747@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-50421","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2400737","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-50421","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-50421","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025100155-CVE-2022-50421-8bdc@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-50491","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2401482","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-50491","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-50491","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025100417-CVE-2022-50491-7a8b@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-50511","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2402295","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-50511","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-50511","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025100701-CVE-2022-50511-5d8d@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-50614","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2419885","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-50614","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-50614","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025120851-CVE-2022-50614-cc88@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-50743","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2425151","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-50743","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-50743","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025122449-CVE-2022-50743-8e63@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-50811","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2426130","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-50811","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-50811","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025123013-CVE-2022-50811-66f4@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-52672","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-52672","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-52672","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024051729-CVE-2023-52672-f30c@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-52917","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-52917","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-52917","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024102100-CVE-2023-52917-f16d@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-53066","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2363718","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-53066","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-53066","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025050211-CVE-2023-53066-cba3@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-53117","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2363694","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-53117","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-53117","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025050229-CVE-2023-53117-09c9@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-53196","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2395317","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-53196","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-53196","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025091559-CVE-2023-53196-c59a@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-53260","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2395374","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-53260","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-53260","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025091504-CVE-2023-53260-2323@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-53261","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2395302","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-53261","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-53261","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025091504-CVE-2023-53261-6a1a@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-53287","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2395698","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-53287","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-53287","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025091625-CVE-2023-53287-d8cd@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-53510","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2400714","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-53510","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-53510","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025100130-CVE-2023-53510-9e6a@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-53519","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2400734","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-53519","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-53519","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025100132-CVE-2023-53519-de9d@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-53555","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2401465","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-53555","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-53555","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025100448-CVE-2023-53555-b949@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-53568","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2401507","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-53568","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-53568","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025100452-CVE-2023-53568-0020@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-53595","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2401509","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-53595","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-53595","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025100428-CVE-2023-53595-91fb@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-53654","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2402189","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-53654","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-53654","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025100720-CVE-2023-53654-dcad@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-53859","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2420340","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-53859","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-53859","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025120904-CVE-2023-53859-1c16@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-53989","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2424933","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-53989","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-53989","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025122423-CVE-2023-53989-1b3b@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-54089","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2425125","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-54089","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-54089","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025122406-CVE-2023-54089-ddc6@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-54117","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2425079","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-54117","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-54117","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025122415-CVE-2023-54117-e980@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-54230","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2426148","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-54230","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-54230","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025123030-CVE-2023-54230-914e@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-54278","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2426072","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-54278","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-54278","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025123003-CVE-2023-54278-d4b2@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-54313","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2426085","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-54313","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-54313","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025123036-CVE-2023-54313-f889@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-54322","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2426163","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-54322","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-54322","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025123022-CVE-2023-54322-34ba@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-27008","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-27008","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-27008","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024050148-CVE-2024-27008-5964@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-27398","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-27398","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-27398","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024051355-CVE-2024-27398-08ef@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-35891","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-35891","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-35891","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024051948-CVE-2024-35891-3a56@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-35933","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-35933","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-35933","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024051917-CVE-2024-35933-cf34@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-35934","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-35934","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-35934","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024051917-CVE-2024-35934-c8af@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-35963","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-35963","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-35963","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024052021-CVE-2024-35963-7934@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-35964","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-35964","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-35964","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024052021-CVE-2024-35964-25e2@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-35965","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-35965","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-35965","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024052021-CVE-2024-35965-19f1@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-35966","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-35966","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-35966","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024052021-CVE-2024-35966-e107@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-35967","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-35967","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-35967","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024052022-CVE-2024-35967-d111@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-35978","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-35978","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-35978","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024052025-CVE-2024-35978-adaa@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-36011","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-36011","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-36011","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024052312-CVE-2024-36011-2a8b@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-36012","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-36012","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-36012","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024052314-CVE-2024-36012-3062@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-36013","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-36013","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-36013","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024052314-CVE-2024-36013-0c90@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-36880","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-36880","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-36880","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024053031-CVE-2024-36880-c961@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-36968","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-36968","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-36968","tags":["advisory"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-38541","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-38541","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-38541","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024061948-CVE-2024-38541-53d0@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-39500","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-39500","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-39500","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024071203-CVE-2024-39500-eba6@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-40956","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-40956","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-40956","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024071224-CVE-2024-40956-b65d@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-41010","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-41010","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-41010","tags":["advisory"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-41062","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-41062","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-41062","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024072906-CVE-2024-41062-cb85@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-42094","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2300709","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-42094","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-42094","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024072911-CVE-2024-42094-135f@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-42133","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-42133","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-42133","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024073028-CVE-2024-42133-07c4@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-42253","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2303634","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-42253","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-42253","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024080835-CVE-2024-42253-0c21@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-42265","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2305410","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-42265","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-42265","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024081737-CVE-2024-42265-a943@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-42278","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2305423","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-42278","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-42278","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024081742-CVE-2024-42278-e639@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-42291","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2305436","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-42291","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-42291","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024081746-CVE-2024-42291-6f31@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-42294","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2305439","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-42294","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-42294","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024081746-CVE-2024-42294-0145@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-42302","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2305447","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-42302","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-42302","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024081749-CVE-2024-42302-c0d9@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-42304","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2305449","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-42304","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-42304","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024081749-CVE-2024-42304-d0e4@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-42305","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2305450","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-42305","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-42305","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024081750-CVE-2024-42305-94ed@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-42312","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2305457","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-42312","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-42312","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024081752-CVE-2024-42312-bddc@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-42315","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2305460","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-42315","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-42315","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024081753-CVE-2024-42315-a707@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-42316","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2305461","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-42316","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-42316","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024081753-CVE-2024-42316-8b49@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-42321","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2305466","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-42321","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-42321","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024081755-CVE-2024-42321-4b46@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-43820","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2305478","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-43820","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-43820","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024081724-CVE-2024-43820-1bd6@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-43821","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2305479","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-43821","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-43821","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024081724-CVE-2024-43821-6ffc@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-43823","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2305481","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-43823","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-43823","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024081725-CVE-2024-43823-4bdd@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-43828","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2305486","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-43828","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-43828","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024081726-CVE-2024-43828-6bcb@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-43834","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2305492","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-43834","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-43834","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024081728-CVE-2024-43834-0140@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-43846","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2305504","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-43846","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-43846","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024081732-CVE-2024-43846-2bd0@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-43853","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2305511","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-43853","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-43853","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024081734-CVE-2024-43853-da5b@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-43871","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2306365","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-43871","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-43871","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024082136-CVE-2024-43871-c2cd@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-43873","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2306367","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-43873","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-43873","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024082136-CVE-2024-43873-c547@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-43882","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2306376","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-43882","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-43882","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024082152-CVE-2024-43882-4fa4@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-43884","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-43884","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-43884","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024082621-CVE-2024-43884-43fa@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-43889","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-43889","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-43889","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024082600-CVE-2024-43889-4d0b@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-43898","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-43898","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-43898","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024082613-CVE-2024-43898-52c2@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-43910","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-43910","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-43910","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024082630-CVE-2024-43910-c6ec@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-43914","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-43914","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-43914","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024082635-CVE-2024-43914-a664@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-44931","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-44931","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-44931","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024082636-CVE-2024-44931-8212@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-44932","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-44932","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-44932","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024082638-CVE-2024-44932-2659@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-44934","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-44934","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-44934","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024082641-CVE-2024-44934-a7fe@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-44952","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-44952","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-44952","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024090411-CVE-2024-44952-6290@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-44958","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-44958","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-44958","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024090413-CVE-2024-44958-80e9@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-44964","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-44964","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-44964","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024090414-CVE-2024-44964-ebb1@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-44975","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-44975","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-44975","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024090442-CVE-2024-44975-7c21@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-44987","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-44987","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-44987","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024090446-CVE-2024-44987-f916@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-44989","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-44989","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-44989","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024090446-CVE-2024-44989-8a2d@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-45000","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-45000","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-45000","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024090449-CVE-2024-45000-fd6f@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-45009","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-45009","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-45009","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024091104-CVE-2024-45009-24ea@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-45010","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-45010","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-45010","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024091107-CVE-2024-45010-33ee@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-45016","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-45016","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-45016","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024091108-CVE-2024-45016-fd5a@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-45022","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-45022","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-45022","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024091109-CVE-2024-45022-08f3@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-46673","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-46673","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-46673","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024091333-CVE-2024-46673-c49c@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-46675","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-46675","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-46675","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024091335-CVE-2024-46675-ba70@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-46711","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-46711","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-46711","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024091348-CVE-2024-46711-ab95@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-46722","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-46722","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-46722","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024091834-CVE-2024-46722-34b3@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-46723","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-46723","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-46723","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024091834-CVE-2024-46723-6726@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-46724","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-46724","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-46724","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024091835-CVE-2024-46724-02f5@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-46725","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-46725","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-46725","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024091835-CVE-2024-46725-af49@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-46743","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-46743","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-46743","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024091835-CVE-2024-46743-f386@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-46745","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-46745","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-46745","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024091836-CVE-2024-46745-7b05@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-46747","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-46747","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-46747","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024091837-CVE-2024-46747-f489@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-46750","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-46750","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-46750","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024091838-CVE-2024-46750-3be1@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-46754","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-46754","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-46754","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024091840-CVE-2024-46754-7f04@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-46756","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-46756","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-46756","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024091840-CVE-2024-46756-2ca6@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-46758","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-46758","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-46758","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024091841-CVE-2024-46758-6154@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-46759","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-46759","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-46759","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024091841-CVE-2024-46759-9b86@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-46761","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-46761","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-46761","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024091842-CVE-2024-46761-289f@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-46783","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-46783","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-46783","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024091850-CVE-2024-46783-edcb@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-46786","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-46786","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-46786","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024091851-CVE-2024-46786-a167@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-46787","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-46787","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-46787","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024091852-CVE-2024-46787-8b6d@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-46800","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-46800","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-46800","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024091857-CVE-2024-46800-0f62@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-46805","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-46805","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-46805","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024092709-CVE-2024-46805-b06a@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-46806","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-46806","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-46806","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024092709-CVE-2024-46806-2cc7@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-46807","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-46807","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-46807","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024092709-CVE-2024-46807-b78e@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-46819","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-46819","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-46819","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024092712-CVE-2024-46819-d958@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-46820","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-46820","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-46820","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024092712-CVE-2024-46820-6405@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-46822","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-46822","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-46822","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024092749-CVE-2024-46822-b901@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-46828","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-46828","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-46828","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024092751-CVE-2024-46828-2184@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-46835","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-46835","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-46835","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024092753-CVE-2024-46835-4f99@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-46839","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-46839","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-46839","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024092754-CVE-2024-46839-cfab@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-46853","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-46853","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-46853","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024092742-CVE-2024-46853-ab04@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-46864","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-46864","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-46864","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024092745-CVE-2024-46864-0343@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-46871","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-46871","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-46871","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024100958-CVE-2024-46871-15f4@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-47141","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-47141","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-47141","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025011119-CVE-2024-47141-13f5@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-47660","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-47660","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-47660","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024100959-CVE-2024-47660-2d61@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-47668","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-47668","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-47668","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024100906-CVE-2024-47668-6b53@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-47678","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-47678","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-47678","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024102106-CVE-2024-47678-0b1b@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-47685","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-47685","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-47685","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024102109-CVE-2024-47685-af1e@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-47687","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-47687","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-47687","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024102109-CVE-2024-47687-9a03@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-47692","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-47692","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-47692","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024102111-CVE-2024-47692-38d2@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-47700","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-47700","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-47700","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024102114-CVE-2024-47700-00ff@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-47703","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-47703","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-47703","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024102115-CVE-2024-47703-36ea@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-47705","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-47705","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-47705","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024102116-CVE-2024-47705-12bc@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-47706","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-47706","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-47706","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024102116-CVE-2024-47706-7312@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-47710","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-47710","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-47710","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024102118-CVE-2024-47710-3882@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-47713","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-47713","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-47713","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024102119-CVE-2024-47713-2624@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-47715","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-47715","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-47715","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024102120-CVE-2024-47715-ff4e@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-47718","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-47718","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-47718","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024102121-CVE-2024-47718-c7cd@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-47719","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-47719","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-47719","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024102121-CVE-2024-47719-09a2@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-47737","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-47737","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-47737","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024102108-CVE-2024-47737-b77e@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-47738","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-47738","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-47738","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024102108-CVE-2024-47738-3f0e@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-47739","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-47739","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-47739","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024102109-CVE-2024-47739-8bc4@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-47745","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-47745","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-47745","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024102111-CVE-2024-47745-42e6@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-47748","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-47748","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-47748","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024102112-CVE-2024-47748-a134@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-48873","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-48873","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-48873","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025011120-CVE-2024-48873-75a9@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-49569","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-49569","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-49569","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025011122-CVE-2024-49569-c532@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-49851","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-49851","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-49851","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024102152-CVE-2024-49851-edd9@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-49856","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-49856","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-49856","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024102154-CVE-2024-49856-f5f7@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-49860","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-49860","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-49860","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024102124-CVE-2024-49860-2a48@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-49861","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2320275","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-49861","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-49861","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024102124-CVE-2024-49861-5288@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-49862","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-49862","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-49862","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024102125-CVE-2024-49862-b995@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-49870","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-49870","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-49870","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024102114-CVE-2024-49870-44f0@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-49875","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-49875","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-49875","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024102115-CVE-2024-49875-02ba@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-49878","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-49878","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-49878","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024102115-CVE-2024-49878-8099@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-49881","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-49881","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-49881","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024102116-CVE-2024-49881-bfd0@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-49882","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-49882","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-49882","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024102116-CVE-2024-49882-4169@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-49883","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-49883","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-49883","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024102116-CVE-2024-49883-ca93@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-49884","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-49884","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-49884","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024102116-CVE-2024-49884-fa56@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-49885","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-49885","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-49885","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024102117-CVE-2024-49885-d5d0@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-49886","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-49886","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-49886","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024102117-CVE-2024-49886-3477@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-49889","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-49889","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-49889","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024102117-CVE-2024-49889-6140@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-49904","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-49904","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-49904","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024102120-CVE-2024-49904-121b@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-49927","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-49927","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-49927","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024102125-CVE-2024-49927-86cf@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-49928","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-49928","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-49928","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024102125-CVE-2024-49928-05d6@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-49929","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-49929","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-49929","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024102125-CVE-2024-49929-1031@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-49930","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-49930","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-49930","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024102125-CVE-2024-49930-34e8@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-49933","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-49933","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-49933","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024102126-CVE-2024-49933-f918@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-49934","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-49934","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-49934","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024102126-CVE-2024-49934-0ac9@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-49935","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-49935","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-49935","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024102126-CVE-2024-49935-004d@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-49937","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-49937","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-49937","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024102127-CVE-2024-49937-74ee@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-49938","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-49938","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-49938","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024102127-CVE-2024-49938-5a61@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-49939","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-49939","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-49939","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024102127-CVE-2024-49939-b39d@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-49946","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-49946","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-49946","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024102129-CVE-2024-49946-762f@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-49948","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-49948","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-49948","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024102129-CVE-2024-49948-ba28@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-49950","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-49950","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-49950","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024102129-CVE-2024-49950-bbf4@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-49951","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-49951","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-49951","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024102130-CVE-2024-49951-a620@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-49954","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-49954","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-49954","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024102130-CVE-2024-49954-cea5@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-49959","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-49959","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-49959","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024102131-CVE-2024-49959-ce09@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-49960","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-49960","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-49960","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024102131-CVE-2024-49960-f9cb@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-49962","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-49962","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-49962","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024102132-CVE-2024-49962-8d16@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-49967","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-49967","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-49967","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024102133-CVE-2024-49967-a58a@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-49968","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-49968","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-49968","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024102133-CVE-2024-49968-ce10@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-49971","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-49971","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-49971","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024102133-CVE-2024-49971-ad07@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-49973","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-49973","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-49973","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024102134-CVE-2024-49973-8824@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-49974","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-49974","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-49974","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024102134-CVE-2024-49974-bda6@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-49975","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-49975","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-49975","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024102134-CVE-2024-49975-4533@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-49977","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-49977","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-49977","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024102135-CVE-2024-49977-b657@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-49983","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-49983","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-49983","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024102136-CVE-2024-49983-275e@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-49991","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-49991","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-49991","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024102137-CVE-2024-49991-59d4@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-49993","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-49993","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-49993","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024102138-CVE-2024-49993-5b57@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-49994","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-49994","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-49994","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024102138-CVE-2024-49994-de99@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-49995","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-49995","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-49995","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024102138-CVE-2024-49995-ec59@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-49999","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-49999","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-49999","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024102139-CVE-2024-49999-e815@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-50002","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-50002","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-50002","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024102139-CVE-2024-50002-bdfd@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-50006","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-50006","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-50006","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024102108-CVE-2024-50006-fe44@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-50008","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-50008","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-50008","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024102109-CVE-2024-50008-0152@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-50009","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-50009","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-50009","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024102109-CVE-2024-50009-1b62@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-50013","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-50013","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-50013","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024102110-CVE-2024-50013-05ef@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-50014","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-50014","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-50014","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024102110-CVE-2024-50014-d684@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-50015","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-50015","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-50015","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024102110-CVE-2024-50015-1eb0@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-50018","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-50018","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-50018","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024102111-CVE-2024-50018-65e9@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-50019","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-50019","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-50019","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024102126-CVE-2024-50019-5896@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-50022","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-50022","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-50022","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024102129-CVE-2024-50022-0531@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-50023","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-50023","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-50023","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024102129-CVE-2024-50023-0e72@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-50024","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-50024","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-50024","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024102129-CVE-2024-50024-a052@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-50027","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-50027","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-50027","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024102130-CVE-2024-50027-91e1@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-50028","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-50028","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-50028","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024102130-CVE-2024-50028-5655@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-50029","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-50029","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-50029","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024102130-CVE-2024-50029-8df2@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-50033","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-50033","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-50033","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024102131-CVE-2024-50033-ce5e@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-50035","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-50035","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-50035","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024102132-CVE-2024-50035-82d8@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-50038","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-50038","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-50038","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024102132-CVE-2024-50038-dc41@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-50039","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-50039","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-50039","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024102132-CVE-2024-50039-41b0@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-50044","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-50044","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-50044","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024102133-CVE-2024-50044-2ee1@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-50046","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-50046","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-50046","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024102134-CVE-2024-50046-a9b4@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-50047","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-50047","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-50047","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024102134-CVE-2024-50047-7a27@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-50055","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-50055","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-50055","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024102134-CVE-2024-50055-7d1f@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-50057","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-50057","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-50057","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024102135-CVE-2024-50057-d046@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-50058","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-50058","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-50058","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024102135-CVE-2024-50058-e827@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-50064","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-50064","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-50064","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024102136-CVE-2024-50064-33d1@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-50067","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-50067","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-50067","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024102859-CVE-2024-50067-f7c0@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-50073","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-50073","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-50073","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024102935-CVE-2024-50073-307b@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-50074","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-50074","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-50074","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024102935-CVE-2024-50074-d44d@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-50075","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-50075","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-50075","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024102935-CVE-2024-50075-81b7@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-50077","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-50077","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-50077","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024102936-CVE-2024-50077-2940@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-50078","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-50078","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-50078","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024102936-CVE-2024-50078-cfe9@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-50081","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-50081","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-50081","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024102937-CVE-2024-50081-f8d6@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-50082","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-50082","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-50082","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024102937-CVE-2024-50082-c5b1@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-50093","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-50093","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-50093","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024110551-CVE-2024-50093-2811@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-50101","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-50101","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-50101","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024110526-CVE-2024-50101-d1bb@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-50102","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-50102","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-50102","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024110553-CVE-2024-50102-3d1e@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-50106","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-50106","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-50106","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024110553-CVE-2024-50106-c095@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-50107","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-50107","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-50107","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024110554-CVE-2024-50107-6bdf@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-50109","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-50109","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-50109","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024110554-CVE-2024-50109-b93c@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-50117","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-50117","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-50117","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024110555-CVE-2024-50117-83b1@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-50120","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-50120","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-50120","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024110556-CVE-2024-50120-07e2@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-50121","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-50121","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-50121","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024110556-CVE-2024-50121-2a0a@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-50126","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-50126","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-50126","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024110557-CVE-2024-50126-733b@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-50127","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-50127","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-50127","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024110557-CVE-2024-50127-c0b5@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-50128","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-50128","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-50128","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024110557-CVE-2024-50128-0fd8@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-50130","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-50130","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-50130","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024110558-CVE-2024-50130-7580@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-50141","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-50141","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-50141","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024110742-CVE-2024-50141-a773@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-50143","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-50143","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-50143","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024110743-CVE-2024-50143-4678@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-50150","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-50150","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-50150","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024110745-CVE-2024-50150-0254@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-50151","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-50151","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-50151","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024110745-CVE-2024-50151-f52b@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-50152","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-50152","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-50152","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024110745-CVE-2024-50152-535e@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-50153","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-50153","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-50153","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024110745-CVE-2024-50153-ecf2@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-50162","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-50162","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-50162","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024110747-CVE-2024-50162-474e@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-50163","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-50163","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-50163","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024110747-CVE-2024-50163-6769@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-50169","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-50169","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-50169","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024110749-CVE-2024-50169-9df5@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-50182","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-50182","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-50182","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024110833-CVE-2024-50182-0fe4@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-50186","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-50186","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-50186","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024110834-CVE-2024-50186-acb0@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-50189","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-50189","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-50189","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024110851-CVE-2024-50189-48c8@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-50191","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-50191","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-50191","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024110851-CVE-2024-50191-f31c@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-50197","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-50197","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-50197","tags":["advisory"]},{"url":"https://git.kernel.org/pub/scm/linux/security/vulns.git/tree/cve/published/2024/CVE-2024-50197.mbox","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-50199","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-50199","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-50199","tags":["advisory"]},{"url":"https://git.kernel.org/pub/scm/linux/security/vulns.git/tree/cve/published/2024/CVE-2024-50199.mbox","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-50200","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-50200","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-50200","tags":["advisory"]},{"url":"https://git.kernel.org/pub/scm/linux/security/vulns.git/tree/cve/published/2024/CVE-2024-50200.mbox","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-50201","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-50201","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-50201","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024110818-CVE-2024-50201-b73d@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-50215","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-50215","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-50215","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024110924-CVE-2024-50215-0155@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-50216","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-50216","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-50216","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024110924-CVE-2024-50216-a031@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-50219","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-50219","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-50219","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024110925-CVE-2024-50219-c970@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-50228","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-50228","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-50228","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024110928-CVE-2024-50228-7a2a@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-50235","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-50235","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-50235","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024110931-CVE-2024-50235-14eb@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-50236","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-50236","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-50236","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024110931-CVE-2024-50236-49dc@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-50237","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-50237","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-50237","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024110932-CVE-2024-50237-7073@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-50256","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-50256","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-50256","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024110938-CVE-2024-50256-5b66@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-50261","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-50261","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-50261","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024110940-CVE-2024-50261-3a20@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-50271","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-50271","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-50271","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024111929-CVE-2024-50271-9089@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-50272","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-50272","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-50272","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024111930-CVE-2024-50272-5691@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-50278","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-50278","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-50278","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024111937-CVE-2024-50278-d6c9@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-50282","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-50282","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-50282","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024111943-CVE-2024-50282-1579@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-50299","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-50299","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-50299","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024111904-CVE-2024-50299-795d@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-50304","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-50304","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-50304","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024111924-CVE-2024-50304-da6d@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-53042","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-53042","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-53042","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024111924-CVE-2024-53042-f7e1@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-53044","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-53044","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-53044","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024111925-CVE-2024-53044-e0d1@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-53047","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-53047","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-53047","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024111926-CVE-2024-53047-8214@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-53050","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-53050","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-53050","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024111927-CVE-2024-53050-b59c@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-53051","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-53051","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-53051","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024111927-CVE-2024-53051-5184@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-53055","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-53055","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-53055","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024111928-CVE-2024-53055-4a64@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-53057","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-53057","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-53057","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024111928-CVE-2024-53057-a3a5@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-53059","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-53059","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-53059","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024111928-CVE-2024-53059-4f81@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-53060","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-53060","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-53060","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024111931-CVE-2024-53060-3b94@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-53070","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-53070","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-53070","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024111933-CVE-2024-53070-6eea@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-53072","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-53072","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-53072","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024111934-CVE-2024-53072-f307@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-53074","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-53074","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-53074","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024111924-CVE-2024-53074-e49b@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-53082","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-53082","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-53082","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024111904-CVE-2024-53082-30c0@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-53085","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-53085","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-53085","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024111905-CVE-2024-53085-9cf3@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-53091","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-53091","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-53091","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024112151-CVE-2024-53091-7f61@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-53093","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-53093","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-53093","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024112152-CVE-2024-53093-f854@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-53095","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-53095","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-53095","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024112152-CVE-2024-53095-7ffd@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-53096","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-53096","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-53096","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024112506-CVE-2024-53096-5bcc@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-53097","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-53097","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-53097","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024112505-CVE-2024-53097-cd93@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-53103","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-53103","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-53103","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024120230-CVE-2024-53103-b5ea@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-53105","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-53105","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-53105","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024120244-CVE-2024-53105-d978@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-53110","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-53110","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-53110","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024120248-CVE-2024-53110-3bff@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-53117","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-53117","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-53117","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024120250-CVE-2024-53117-145b@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-53118","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-53118","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-53118","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024120251-CVE-2024-53118-c6d7@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-53120","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-53120","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-53120","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024120251-CVE-2024-53120-65fd@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-53121","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-53121","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-53121","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024120252-CVE-2024-53121-34da@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-53123","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-53123","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-53123","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024120252-CVE-2024-53123-cd09@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-53124","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-53124","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-53124","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024120253-CVE-2024-53124-91b3@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-53134","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-53134","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-53134","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024120451-CVE-2024-53134-cb0a@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-53136","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-53136","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-53136","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024120452-CVE-2024-53136-f7f8@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-53141","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2330763","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-53141","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-53141","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024120606-CVE-2024-53141-195b@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-53142","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-53142","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-53142","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024120609-CVE-2024-53142-b75e@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-53146","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-53146","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-53146","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024122426-CVE-2024-53146-c503@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-53152","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-53152","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-53152","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024122428-CVE-2024-53152-ada9@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-53156","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-53156","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-53156","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024122429-CVE-2024-53156-732e@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-53160","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-53160","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-53160","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024122431-CVE-2024-53160-692f@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-53161","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-53161","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-53161","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024122431-CVE-2024-53161-50f6@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-53164","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-53164","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-53164","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024122746-CVE-2024-53164-752a@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-53166","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-53166","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-53166","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024122714-CVE-2024-53166-8beb@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-53173","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-53173","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-53173","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024122717-CVE-2024-53173-b3c7@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-53174","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-53174","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-53174","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024122717-CVE-2024-53174-d29a@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-53176","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2334355","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-53176","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-53176","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024122718-CVE-2024-53176-85e0@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-53190","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-53190","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-53190","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024122723-CVE-2024-53190-fdeb@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-53194","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-53194","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-53194","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024122724-CVE-2024-53194-9edf@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-53203","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-53203","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-53203","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024122727-CVE-2024-53203-80fc@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-53208","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-53208","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-53208","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024122729-CVE-2024-53208-dff3@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-53213","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-53213","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-53213","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024122730-CVE-2024-53213-baa6@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-53216","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2334415","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-53216","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-53216","tags":["advisory"]},{"url":"https://git.kernel.org/pub/scm/linux/security/vulns.git/plain/cve/published/2024/CVE-2024-53216.mbox","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-53222","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-53222","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-53222","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024122734-CVE-2024-53222-6c79@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-53224","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-53224","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-53224","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024122734-CVE-2024-53224-2509@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-53237","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-53237","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-53237","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024122739-CVE-2024-53237-2fa6@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-53681","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-53681","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-53681","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025011532-CVE-2024-53681-e199@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-54460","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-54460","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-54460","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025011158-CVE-2024-54460-c8c8@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-54680","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-54680","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-54680","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025011145-CVE-2024-54680-db98@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-56535","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-56535","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-56535","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024122725-CVE-2024-56535-4683@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-56544","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2334428","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-56544","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-56544","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024122728-CVE-2024-56544-42cf@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-56551","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-56551","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-56551","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024122709-CVE-2024-56551-4ad2@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-56558","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-56558","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-56558","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024122712-CVE-2024-56558-9fd9@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-56562","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-56562","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-56562","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024122713-CVE-2024-56562-9fd5@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-56566","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-56566","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-56566","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024122715-CVE-2024-56566-0a7e@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-56570","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-56570","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-56570","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024122716-CVE-2024-56570-7580@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-56590","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-56590","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-56590","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024122759-CVE-2024-56590-d4ba@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-56591","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-56591","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-56591","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024122759-CVE-2024-56591-eaf9@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-56600","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-56600","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-56600","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024122702-CVE-2024-56600-7867@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-56601","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-56601","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-56601","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024122703-CVE-2024-56601-2150@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-56602","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-56602","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-56602","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024122703-CVE-2024-56602-d030@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-56604","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-56604","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-56604","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024122704-CVE-2024-56604-8494@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-56605","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-56605","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-56605","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024122704-CVE-2024-56605-d424@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-56611","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-56611","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-56611","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024122706-CVE-2024-56611-262a@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-56614","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-56614","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-56614","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024122707-CVE-2024-56614-17c4@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-56616","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-56616","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-56616","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024122708-CVE-2024-56616-ae89@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-56623","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-56623","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-56623","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024122710-CVE-2024-56623-e4c7@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-56631","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-56631","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-56631","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024122731-CVE-2024-56631-548f@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-56642","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-56642","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-56642","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024122737-CVE-2024-56642-71ee@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-56644","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-56644","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-56644","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024122737-CVE-2024-56644-83c2@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-56647","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-56647","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-56647","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024122738-CVE-2024-56647-d71f@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-56653","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-56653","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-56653","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024122749-CVE-2024-56653-bb35@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-56654","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-56654","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-56654","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024122749-CVE-2024-56654-66a1@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-56663","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-56663","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-56663","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024122752-CVE-2024-56663-66d7@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-56664","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-56664","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-56664","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024122752-CVE-2024-56664-9dc6@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-56667","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-56667","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-56667","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024122753-CVE-2024-56667-3c3f@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-56688","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-56688","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-56688","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024122834-CVE-2024-56688-4e02@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-56693","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-56693","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-56693","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024122835-CVE-2024-56693-b3c6@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-56729","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-56729","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-56729","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024122924-CVE-2024-56729-8f1c@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-56757","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-56757","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-56757","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025010651-CVE-2024-56757-c26b@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-56760","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-56760","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-56760","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025010654-CVE-2024-56760-af6e@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-56779","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-56779","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-56779","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025010812-CVE-2024-56779-74f5@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-56783","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-56783","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-56783","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025010807-CVE-2024-56783-4ed9@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-57798","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-57798","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-57798","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025011151-CVE-2024-57798-68b5@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-57809","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-57809","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-57809","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025011103-CVE-2024-57809-a6be@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-57843","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-57843","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-57843","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025011103-CVE-2024-57843-1c15@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-57852","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2348530","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-57852","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-57852","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025022603-CVE-2024-57852-f942@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-57879","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-57879","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-57879","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025011131-CVE-2024-57879-7fa8@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-57884","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-57884","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-57884","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025011510-CVE-2024-57884-4cf8@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-57885","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2338198","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-57885","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-57885","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025011510-CVE-2024-57885-ea46@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-57888","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-57888","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-57888","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025011511-CVE-2024-57888-0b38@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-57890","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-57890","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-57890","tags":["advisory"]},{"url":"https://git.kernel.org/stable/c/b92667f755749cf10d9ef1088865c555ae83ffb7","tags":["article"]},{"url":"https://git.kernel.org/stable/c/c2f961c46ea0e5274c5c320d007c2dd949cf627a","tags":["article"]},{"url":"https://git.kernel.org/stable/c/d0257e089d1bbd35c69b6c97ff73e3690ab149a9","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-57894","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-57894","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-57894","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025011513-CVE-2024-57894-fbfe@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-57898","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-57898","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-57898","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025011515-CVE-2024-57898-bfde@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-57903","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2338190","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-57903","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-57903","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025011517-CVE-2024-57903-fd2a@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-57929","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-57929","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-57929","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025011945-CVE-2024-57929-2b82@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-57931","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-57931","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-57931","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025012147-CVE-2024-57931-06fb@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-57940","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-57940","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-57940","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025012128-CVE-2024-57940-e289@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-58009","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2348526","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-58009","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-58009","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025022656-CVE-2024-58009-b2d2@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-58064","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2350354","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-58064","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-58064","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025030609-CVE-2024-58064-6aa6@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-58099","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-58099","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-58099","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025042936-CVE-2024-58099-39c4@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2025-1272","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2025-1272","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-1272","tags":["advisory"]},{"url":"https://access.redhat.com/security/cve/CVE-2025-21646","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2025-21646","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-21646","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025011945-CVE-2025-21646-8f6e@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2025-21663","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2025-21663","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-21663","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025012135-CVE-2025-21663-7420@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2025-21666","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2025-21666","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-21666","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025013157-CVE-2025-21666-465a@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2025-21668","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2025-21668","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-21668","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025013158-CVE-2025-21668-f82f@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2025-21669","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2025-21669","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-21669","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025013158-CVE-2025-21669-b52c@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2025-21689","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2025-21689","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-21689","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025021055-CVE-2025-21689-7ffe@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2025-21694","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2025-21694","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-21694","tags":["advisory"]},{"url":"https://git.kernel.org/stable/c/649b266606bc413407ce315f710c8ce8a88ee30a","tags":["article"]},{"url":"https://git.kernel.org/stable/c/65c367bd9d4f43513c7f837df5753bea9561b836","tags":["article"]},{"url":"https://git.kernel.org/stable/c/80828540dad0757b6337c6561d49c81038f38d87","tags":["article"]},{"url":"https://git.kernel.org/stable/c/80da29deb88a3a907441fc35bb7bac309f31e713","tags":["article"]},{"url":"https://git.kernel.org/stable/c/84c4ed15626574c9ac6c1039ba9c137a77bcc7f2","tags":["article"]},{"url":"https://git.kernel.org/stable/c/a5a2ee8144c3897d37403a69118c3e3dc5713958","tags":["article"]},{"url":"https://git.kernel.org/stable/c/cbc5dde0a461240046e8a41c43d7c3b76d5db952","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2025-21888","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2355410","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2025-21888","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-21888","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025032714-CVE-2025-21888-0f83@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2025-22087","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2360217","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2025-22087","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-22087","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025041616-CVE-2025-22087-d711@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2025-68179","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2422662","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2025-68179","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-68179","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025121631-CVE-2025-68179-6ce9@gregkh/T","tags":["article"]},{"url":"https://www.suse.com/support/update/announcement/2025/suse-su-20250289-1/","tags":["advisory"]},{"url":"https://bugzilla.suse.com/1012628","tags":["report"]},{"url":"https://bugzilla.suse.com/1194869","tags":["report"]},{"url":"https://bugzilla.suse.com/1214954","tags":["report"]},{"url":"https://bugzilla.suse.com/1215199","tags":["report"]},{"url":"https://bugzilla.suse.com/1216813","tags":["report"]},{"url":"https://bugzilla.suse.com/1218470","tags":["report"]},{"url":"https://bugzilla.suse.com/1220355","tags":["report"]},{"url":"https://bugzilla.suse.com/1220711","tags":["report"]},{"url":"https://bugzilla.suse.com/1220773","tags":["report"]},{"url":"https://bugzilla.suse.com/1221326","tags":["report"]},{"url":"https://bugzilla.suse.com/1224095","tags":["report"]},{"url":"https://bugzilla.suse.com/1224726","tags":["report"]},{"url":"https://bugzilla.suse.com/1225743","tags":["report"]},{"url":"https://bugzilla.suse.com/1225758","tags":["report"]},{"url":"https://bugzilla.suse.com/1225820","tags":["report"]},{"url":"https://bugzilla.suse.com/1225897","tags":["report"]},{"url":"https://bugzilla.suse.com/1227445","tags":["report"]},{"url":"https://bugzilla.suse.com/1228526","tags":["report"]},{"url":"https://bugzilla.suse.com/1228592","tags":["report"]},{"url":"https://bugzilla.suse.com/1229809","tags":["report"]},{"url":"https://bugzilla.suse.com/1229833","tags":["report"]},{"url":"https://bugzilla.suse.com/1230205","tags":["report"]},{"url":"https://bugzilla.suse.com/1230413","tags":["report"]},{"url":"https://bugzilla.suse.com/1230557","tags":["report"]},{"url":"https://bugzilla.suse.com/1230697","tags":["report"]},{"url":"https://bugzilla.suse.com/1230807","tags":["report"]},{"url":"https://bugzilla.suse.com/1230827","tags":["report"]},{"url":"https://bugzilla.suse.com/1231016","tags":["report"]},{"url":"https://bugzilla.suse.com/1231854","tags":["report"]},{"url":"https://bugzilla.suse.com/1231909","tags":["report"]},{"url":"https://bugzilla.suse.com/1231963","tags":["report"]},{"url":"https://bugzilla.suse.com/1232087","tags":["report"]},{"url":"https://bugzilla.suse.com/1232157","tags":["report"]},{"url":"https://bugzilla.suse.com/1232158","tags":["report"]},{"url":"https://bugzilla.suse.com/1232166","tags":["report"]},{"url":"https://bugzilla.suse.com/1232193","tags":["report"]},{"url":"https://bugzilla.suse.com/1232198","tags":["report"]},{"url":"https://bugzilla.suse.com/1232201","tags":["report"]},{"url":"https://bugzilla.suse.com/1232418","tags":["report"]},{"url":"https://bugzilla.suse.com/1232419","tags":["report"]},{"url":"https://bugzilla.suse.com/1232420","tags":["report"]},{"url":"https://bugzilla.suse.com/1232421","tags":["report"]},{"url":"https://bugzilla.suse.com/1232436","tags":["report"]},{"url":"https://bugzilla.suse.com/1232882","tags":["report"]},{"url":"https://bugzilla.suse.com/1233038","tags":["report"]},{"url":"https://bugzilla.suse.com/1233055","tags":["report"]},{"url":"https://bugzilla.suse.com/1233070","tags":["report"]},{"url":"https://bugzilla.suse.com/1233096","tags":["report"]},{"url":"https://bugzilla.suse.com/1233112","tags":["report"]},{"url":"https://bugzilla.suse.com/1233200","tags":["report"]},{"url":"https://bugzilla.suse.com/1233201","tags":["report"]},{"url":"https://bugzilla.suse.com/1233204","tags":["report"]},{"url":"https://bugzilla.suse.com/1233239","tags":["report"]},{"url":"https://bugzilla.suse.com/1233259","tags":["report"]},{"url":"https://bugzilla.suse.com/1233260","tags":["report"]},{"url":"https://bugzilla.suse.com/1233324","tags":["report"]},{"url":"https://bugzilla.suse.com/1233328","tags":["report"]},{"url":"https://bugzilla.suse.com/1233461","tags":["report"]},{"url":"https://bugzilla.suse.com/1233467","tags":["report"]},{"url":"https://bugzilla.suse.com/1233468","tags":["report"]},{"url":"https://bugzilla.suse.com/1233469","tags":["report"]},{"url":"https://bugzilla.suse.com/1233485","tags":["report"]},{"url":"https://bugzilla.suse.com/1233488","tags":["report"]},{"url":"https://bugzilla.suse.com/1233523","tags":["report"]},{"url":"https://bugzilla.suse.com/1233546","tags":["report"]},{"url":"https://bugzilla.suse.com/1233547","tags":["report"]},{"url":"https://bugzilla.suse.com/1233550","tags":["report"]},{"url":"https://bugzilla.suse.com/1233558","tags":["report"]},{"url":"https://bugzilla.suse.com/1233568","tags":["report"]},{"url":"https://bugzilla.suse.com/1233637","tags":["report"]},{"url":"https://bugzilla.suse.com/1233638","tags":["report"]},{"url":"https://bugzilla.suse.com/1233642","tags":["report"]},{"url":"https://bugzilla.suse.com/1233772","tags":["report"]},{"url":"https://bugzilla.suse.com/1233837","tags":["report"]},{"url":"https://bugzilla.suse.com/1234024","tags":["report"]},{"url":"https://bugzilla.suse.com/1234069","tags":["report"]},{"url":"https://bugzilla.suse.com/1234071","tags":["report"]},{"url":"https://bugzilla.suse.com/1234073","tags":["report"]},{"url":"https://bugzilla.suse.com/1234075","tags":["report"]},{"url":"https://bugzilla.suse.com/1234076","tags":["report"]},{"url":"https://bugzilla.suse.com/1234077","tags":["report"]},{"url":"https://bugzilla.suse.com/1234078","tags":["report"]},{"url":"https://bugzilla.suse.com/1234079","tags":["report"]},{"url":"https://bugzilla.suse.com/1234085","tags":["report"]},{"url":"https://bugzilla.suse.com/1234086","tags":["report"]},{"url":"https://bugzilla.suse.com/1234139","tags":["report"]},{"url":"https://bugzilla.suse.com/1234140","tags":["report"]},{"url":"https://bugzilla.suse.com/1234141","tags":["report"]},{"url":"https://bugzilla.suse.com/1234142","tags":["report"]},{"url":"https://bugzilla.suse.com/1234143","tags":["report"]},{"url":"https://bugzilla.suse.com/1234144","tags":["report"]},{"url":"https://bugzilla.suse.com/1234145","tags":["report"]},{"url":"https://bugzilla.suse.com/1234146","tags":["report"]},{"url":"https://bugzilla.suse.com/1234147","tags":["report"]},{"url":"https://bugzilla.suse.com/1234148","tags":["report"]},{"url":"https://bugzilla.suse.com/1234149","tags":["report"]},{"url":"https://bugzilla.suse.com/1234150","tags":["report"]},{"url":"https://bugzilla.suse.com/1234153","tags":["report"]},{"url":"https://bugzilla.suse.com/1234155","tags":["report"]},{"url":"https://bugzilla.suse.com/1234156","tags":["report"]},{"url":"https://bugzilla.suse.com/1234158","tags":["report"]},{"url":"https://bugzilla.suse.com/1234159","tags":["report"]},{"url":"https://bugzilla.suse.com/1234160","tags":["report"]},{"url":"https://bugzilla.suse.com/1234161","tags":["report"]},{"url":"https://bugzilla.suse.com/1234162","tags":["report"]},{"url":"https://bugzilla.suse.com/1234163","tags":["report"]},{"url":"https://bugzilla.suse.com/1234164","tags":["report"]},{"url":"https://bugzilla.suse.com/1234165","tags":["report"]},{"url":"https://bugzilla.suse.com/1234166","tags":["report"]},{"url":"https://bugzilla.suse.com/1234167","tags":["report"]},{"url":"https://bugzilla.suse.com/1234168","tags":["report"]},{"url":"https://bugzilla.suse.com/1234169","tags":["report"]},{"url":"https://bugzilla.suse.com/1234170","tags":["report"]},{"url":"https://bugzilla.suse.com/1234171","tags":["report"]},{"url":"https://bugzilla.suse.com/1234172","tags":["report"]},{"url":"https://bugzilla.suse.com/1234173","tags":["report"]},{"url":"https://bugzilla.suse.com/1234174","tags":["report"]},{"url":"https://bugzilla.suse.com/1234175","tags":["report"]},{"url":"https://bugzilla.suse.com/1234176","tags":["report"]},{"url":"https://bugzilla.suse.com/1234177","tags":["report"]},{"url":"https://bugzilla.suse.com/1234178","tags":["report"]},{"url":"https://bugzilla.suse.com/1234179","tags":["report"]},{"url":"https://bugzilla.suse.com/1234180","tags":["report"]},{"url":"https://bugzilla.suse.com/1234181","tags":["report"]},{"url":"https://bugzilla.suse.com/1234182","tags":["report"]},{"url":"https://bugzilla.suse.com/1234183","tags":["report"]},{"url":"https://bugzilla.suse.com/1234184","tags":["report"]},{"url":"https://bugzilla.suse.com/1234185","tags":["report"]},{"url":"https://bugzilla.suse.com/1234186","tags":["report"]},{"url":"https://bugzilla.suse.com/1234187","tags":["report"]},{"url":"https://bugzilla.suse.com/1234188","tags":["report"]},{"url":"https://bugzilla.suse.com/1234189","tags":["report"]},{"url":"https://bugzilla.suse.com/1234190","tags":["report"]},{"url":"https://bugzilla.suse.com/1234191","tags":["report"]},{"url":"https://bugzilla.suse.com/1234192","tags":["report"]},{"url":"https://bugzilla.suse.com/1234193","tags":["report"]},{"url":"https://bugzilla.suse.com/1234194","tags":["report"]},{"url":"https://bugzilla.suse.com/1234195","tags":["report"]},{"url":"https://bugzilla.suse.com/1234196","tags":["report"]},{"url":"https://bugzilla.suse.com/1234197","tags":["report"]},{"url":"https://bugzilla.suse.com/1234198","tags":["report"]},{"url":"https://bugzilla.suse.com/1234199","tags":["report"]},{"url":"https://bugzilla.suse.com/1234200","tags":["report"]},{"url":"https://bugzilla.suse.com/1234201","tags":["report"]},{"url":"https://bugzilla.suse.com/1234203","tags":["report"]},{"url":"https://bugzilla.suse.com/1234204","tags":["report"]},{"url":"https://bugzilla.suse.com/1234205","tags":["report"]},{"url":"https://bugzilla.suse.com/1234207","tags":["report"]},{"url":"https://bugzilla.suse.com/1234208","tags":["report"]},{"url":"https://bugzilla.suse.com/1234209","tags":["report"]},{"url":"https://bugzilla.suse.com/1234219","tags":["report"]},{"url":"https://bugzilla.suse.com/1234220","tags":["report"]},{"url":"https://bugzilla.suse.com/1234221","tags":["report"]},{"url":"https://bugzilla.suse.com/1234223","tags":["report"]},{"url":"https://bugzilla.suse.com/1234237","tags":["report"]},{"url":"https://bugzilla.suse.com/1234238","tags":["report"]},{"url":"https://bugzilla.suse.com/1234239","tags":["report"]},{"url":"https://bugzilla.suse.com/1234240","tags":["report"]},{"url":"https://bugzilla.suse.com/1234241","tags":["report"]},{"url":"https://bugzilla.suse.com/1234242","tags":["report"]},{"url":"https://bugzilla.suse.com/1234243","tags":["report"]},{"url":"https://bugzilla.suse.com/1234278","tags":["report"]},{"url":"https://bugzilla.suse.com/1234279","tags":["report"]},{"url":"https://bugzilla.suse.com/1234280","tags":["report"]},{"url":"https://bugzilla.suse.com/1234281","tags":["report"]},{"url":"https://bugzilla.suse.com/1234282","tags":["report"]},{"url":"https://bugzilla.suse.com/1234294","tags":["report"]},{"url":"https://bugzilla.suse.com/1234338","tags":["report"]},{"url":"https://bugzilla.suse.com/1234357","tags":["report"]},{"url":"https://bugzilla.suse.com/1234381","tags":["report"]},{"url":"https://bugzilla.suse.com/1234454","tags":["report"]},{"url":"https://bugzilla.suse.com/1234464","tags":["report"]},{"url":"https://bugzilla.suse.com/1234605","tags":["report"]},{"url":"https://bugzilla.suse.com/1234619","tags":["report"]},{"url":"https://bugzilla.suse.com/1234635","tags":["report"]},{"url":"https://bugzilla.suse.com/1234651","tags":["report"]},{"url":"https://bugzilla.suse.com/1234652","tags":["report"]},{"url":"https://bugzilla.suse.com/1234654","tags":["report"]},{"url":"https://bugzilla.suse.com/1234655","tags":["report"]},{"url":"https://bugzilla.suse.com/1234657","tags":["report"]},{"url":"https://bugzilla.suse.com/1234658","tags":["report"]},{"url":"https://bugzilla.suse.com/1234659","tags":["report"]},{"url":"https://bugzilla.suse.com/1234668","tags":["report"]},{"url":"https://bugzilla.suse.com/1234690","tags":["report"]},{"url":"https://bugzilla.suse.com/1234725","tags":["report"]},{"url":"https://bugzilla.suse.com/1234726","tags":["report"]},{"url":"https://bugzilla.suse.com/1234810","tags":["report"]},{"url":"https://bugzilla.suse.com/1234811","tags":["report"]},{"url":"https://bugzilla.suse.com/1234825","tags":["report"]},{"url":"https://bugzilla.suse.com/1234826","tags":["report"]},{"url":"https://bugzilla.suse.com/1234827","tags":["report"]},{"url":"https://bugzilla.suse.com/1234829","tags":["report"]},{"url":"https://bugzilla.suse.com/1234832","tags":["report"]},{"url":"https://bugzilla.suse.com/1234834","tags":["report"]},{"url":"https://bugzilla.suse.com/1234843","tags":["report"]},{"url":"https://bugzilla.suse.com/1234846","tags":["report"]},{"url":"https://bugzilla.suse.com/1234848","tags":["report"]},{"url":"https://bugzilla.suse.com/1234853","tags":["report"]},{"url":"https://bugzilla.suse.com/1234855","tags":["report"]},{"url":"https://bugzilla.suse.com/1234856","tags":["report"]},{"url":"https://bugzilla.suse.com/1234863","tags":["report"]},{"url":"https://bugzilla.suse.com/1234884","tags":["report"]},{"url":"https://bugzilla.suse.com/1234887","tags":["report"]},{"url":"https://bugzilla.suse.com/1234888","tags":["report"]},{"url":"https://bugzilla.suse.com/1234889","tags":["report"]},{"url":"https://bugzilla.suse.com/1234891","tags":["report"]},{"url":"https://bugzilla.suse.com/1234893","tags":["report"]},{"url":"https://bugzilla.suse.com/1234898","tags":["report"]},{"url":"https://bugzilla.suse.com/1234899","tags":["report"]},{"url":"https://bugzilla.suse.com/1234900","tags":["report"]},{"url":"https://bugzilla.suse.com/1234901","tags":["report"]},{"url":"https://bugzilla.suse.com/1234905","tags":["report"]},{"url":"https://bugzilla.suse.com/1234906","tags":["report"]},{"url":"https://bugzilla.suse.com/1234907","tags":["report"]},{"url":"https://bugzilla.suse.com/1234909","tags":["report"]},{"url":"https://bugzilla.suse.com/1234911","tags":["report"]},{"url":"https://bugzilla.suse.com/1234912","tags":["report"]},{"url":"https://bugzilla.suse.com/1234916","tags":["report"]},{"url":"https://bugzilla.suse.com/1234918","tags":["report"]},{"url":"https://bugzilla.suse.com/1234920","tags":["report"]},{"url":"https://bugzilla.suse.com/1234921","tags":["report"]},{"url":"https://bugzilla.suse.com/1234922","tags":["report"]},{"url":"https://bugzilla.suse.com/1234923","tags":["report"]},{"url":"https://bugzilla.suse.com/1234929","tags":["report"]},{"url":"https://bugzilla.suse.com/1234930","tags":["report"]},{"url":"https://bugzilla.suse.com/1234931","tags":["report"]},{"url":"https://bugzilla.suse.com/1234934","tags":["report"]},{"url":"https://bugzilla.suse.com/1234937","tags":["report"]},{"url":"https://bugzilla.suse.com/1234948","tags":["report"]},{"url":"https://bugzilla.suse.com/1234950","tags":["report"]},{"url":"https://bugzilla.suse.com/1234952","tags":["report"]},{"url":"https://bugzilla.suse.com/1234957","tags":["report"]},{"url":"https://bugzilla.suse.com/1234960","tags":["report"]},{"url":"https://bugzilla.suse.com/1234962","tags":["report"]},{"url":"https://bugzilla.suse.com/1234963","tags":["report"]},{"url":"https://bugzilla.suse.com/1234968","tags":["report"]},{"url":"https://bugzilla.suse.com/1234969","tags":["report"]},{"url":"https://bugzilla.suse.com/1234970","tags":["report"]},{"url":"https://bugzilla.suse.com/1234971","tags":["report"]},{"url":"https://bugzilla.suse.com/1234973","tags":["report"]},{"url":"https://bugzilla.suse.com/1234974","tags":["report"]},{"url":"https://bugzilla.suse.com/1234989","tags":["report"]},{"url":"https://bugzilla.suse.com/1234999","tags":["report"]},{"url":"https://bugzilla.suse.com/1235000","tags":["report"]},{"url":"https://bugzilla.suse.com/1235002","tags":["report"]},{"url":"https://bugzilla.suse.com/1235003","tags":["report"]},{"url":"https://bugzilla.suse.com/1235004","tags":["report"]},{"url":"https://bugzilla.suse.com/1235007","tags":["report"]},{"url":"https://bugzilla.suse.com/1235009","tags":["report"]},{"url":"https://bugzilla.suse.com/1235011","tags":["report"]},{"url":"https://bugzilla.suse.com/1235016","tags":["report"]},{"url":"https://bugzilla.suse.com/1235019","tags":["report"]},{"url":"https://bugzilla.suse.com/1235031","tags":["report"]},{"url":"https://bugzilla.suse.com/1235032","tags":["report"]},{"url":"https://bugzilla.suse.com/1235033","tags":["report"]},{"url":"https://bugzilla.suse.com/1235035","tags":["report"]},{"url":"https://bugzilla.suse.com/1235037","tags":["report"]},{"url":"https://bugzilla.suse.com/1235038","tags":["report"]},{"url":"https://bugzilla.suse.com/1235039","tags":["report"]},{"url":"https://bugzilla.suse.com/1235040","tags":["report"]},{"url":"https://bugzilla.suse.com/1235042","tags":["report"]},{"url":"https://bugzilla.suse.com/1235043","tags":["report"]},{"url":"https://bugzilla.suse.com/1235045","tags":["report"]},{"url":"https://bugzilla.suse.com/1235046","tags":["report"]},{"url":"https://bugzilla.suse.com/1235050","tags":["report"]},{"url":"https://bugzilla.suse.com/1235051","tags":["report"]},{"url":"https://bugzilla.suse.com/1235053","tags":["report"]},{"url":"https://bugzilla.suse.com/1235054","tags":["report"]},{"url":"https://bugzilla.suse.com/1235056","tags":["report"]},{"url":"https://bugzilla.suse.com/1235057","tags":["report"]},{"url":"https://bugzilla.suse.com/1235059","tags":["report"]},{"url":"https://bugzilla.suse.com/1235061","tags":["report"]},{"url":"https://bugzilla.suse.com/1235065","tags":["report"]},{"url":"https://bugzilla.suse.com/1235070","tags":["report"]},{"url":"https://bugzilla.suse.com/1235073","tags":["report"]},{"url":"https://bugzilla.suse.com/1235075","tags":["report"]},{"url":"https://bugzilla.suse.com/1235100","tags":["report"]},{"url":"https://bugzilla.suse.com/1235108","tags":["report"]},{"url":"https://bugzilla.suse.com/1235112","tags":["report"]},{"url":"https://bugzilla.suse.com/1235115","tags":["report"]},{"url":"https://bugzilla.suse.com/1235117","tags":["report"]},{"url":"https://bugzilla.suse.com/1235122","tags":["report"]},{"url":"https://bugzilla.suse.com/1235123","tags":["report"]},{"url":"https://bugzilla.suse.com/1235125","tags":["report"]},{"url":"https://bugzilla.suse.com/1235128","tags":["report"]},{"url":"https://bugzilla.suse.com/1235132","tags":["report"]},{"url":"https://bugzilla.suse.com/1235133","tags":["report"]},{"url":"https://bugzilla.suse.com/1235134","tags":["report"]},{"url":"https://bugzilla.suse.com/1235138","tags":["report"]},{"url":"https://bugzilla.suse.com/1235155","tags":["report"]},{"url":"https://bugzilla.suse.com/1235160","tags":["report"]},{"url":"https://bugzilla.suse.com/1235219","tags":["report"]},{"url":"https://bugzilla.suse.com/1235220","tags":["report"]},{"url":"https://bugzilla.suse.com/1235222","tags":["report"]},{"url":"https://bugzilla.suse.com/1235223","tags":["report"]},{"url":"https://bugzilla.suse.com/1235224","tags":["report"]},{"url":"https://bugzilla.suse.com/1235227","tags":["report"]},{"url":"https://bugzilla.suse.com/1235241","tags":["report"]},{"url":"https://bugzilla.suse.com/1235246","tags":["report"]},{"url":"https://bugzilla.suse.com/1235249","tags":["report"]},{"url":"https://bugzilla.suse.com/1235251","tags":["report"]},{"url":"https://bugzilla.suse.com/1235252","tags":["report"]},{"url":"https://bugzilla.suse.com/1235389","tags":["report"]},{"url":"https://bugzilla.suse.com/1235391","tags":["report"]},{"url":"https://bugzilla.suse.com/1235406","tags":["report"]},{"url":"https://bugzilla.suse.com/1235409","tags":["report"]},{"url":"https://bugzilla.suse.com/1235410","tags":["report"]},{"url":"https://bugzilla.suse.com/1235412","tags":["report"]},{"url":"https://bugzilla.suse.com/1235413","tags":["report"]},{"url":"https://bugzilla.suse.com/1235415","tags":["report"]},{"url":"https://bugzilla.suse.com/1235416","tags":["report"]},{"url":"https://bugzilla.suse.com/1235417","tags":["report"]},{"url":"https://bugzilla.suse.com/1235423","tags":["report"]},{"url":"https://bugzilla.suse.com/1235424","tags":["report"]},{"url":"https://bugzilla.suse.com/1235425","tags":["report"]},{"url":"https://bugzilla.suse.com/1235426","tags":["report"]},{"url":"https://bugzilla.suse.com/1235427","tags":["report"]},{"url":"https://bugzilla.suse.com/1235428","tags":["report"]},{"url":"https://bugzilla.suse.com/1235429","tags":["report"]},{"url":"https://bugzilla.suse.com/1235433","tags":["report"]},{"url":"https://bugzilla.suse.com/1235437","tags":["report"]},{"url":"https://bugzilla.suse.com/1235439","tags":["report"]},{"url":"https://bugzilla.suse.com/1235444","tags":["report"]},{"url":"https://bugzilla.suse.com/1235445","tags":["report"]},{"url":"https://bugzilla.suse.com/1235449","tags":["report"]},{"url":"https://bugzilla.suse.com/1235451","tags":["report"]},{"url":"https://bugzilla.suse.com/1235454","tags":["report"]},{"url":"https://bugzilla.suse.com/1235458","tags":["report"]},{"url":"https://bugzilla.suse.com/1235459","tags":["report"]},{"url":"https://bugzilla.suse.com/1235464","tags":["report"]},{"url":"https://bugzilla.suse.com/1235466","tags":["report"]},{"url":"https://bugzilla.suse.com/1235473","tags":["report"]},{"url":"https://bugzilla.suse.com/1235479","tags":["report"]},{"url":"https://bugzilla.suse.com/1235480","tags":["report"]},{"url":"https://bugzilla.suse.com/1235483","tags":["report"]},{"url":"https://bugzilla.suse.com/1235486","tags":["report"]},{"url":"https://bugzilla.suse.com/1235488","tags":["report"]},{"url":"https://bugzilla.suse.com/1235491","tags":["report"]},{"url":"https://bugzilla.suse.com/1235494","tags":["report"]},{"url":"https://bugzilla.suse.com/1235495","tags":["report"]},{"url":"https://bugzilla.suse.com/1235496","tags":["report"]},{"url":"https://bugzilla.suse.com/1235497","tags":["report"]},{"url":"https://bugzilla.suse.com/1235500","tags":["report"]},{"url":"https://bugzilla.suse.com/1235502","tags":["report"]},{"url":"https://bugzilla.suse.com/1235503","tags":["report"]},{"url":"https://bugzilla.suse.com/1235507","tags":["report"]},{"url":"https://bugzilla.suse.com/1235519","tags":["report"]},{"url":"https://bugzilla.suse.com/1235520","tags":["report"]},{"url":"https://bugzilla.suse.com/1235521","tags":["report"]},{"url":"https://bugzilla.suse.com/1235523","tags":["report"]},{"url":"https://bugzilla.suse.com/1235526","tags":["report"]},{"url":"https://bugzilla.suse.com/1235528","tags":["report"]},{"url":"https://bugzilla.suse.com/1235532","tags":["report"]},{"url":"https://bugzilla.suse.com/1235533","tags":["report"]},{"url":"https://bugzilla.suse.com/1235534","tags":["report"]},{"url":"https://bugzilla.suse.com/1235537","tags":["report"]},{"url":"https://bugzilla.suse.com/1235538","tags":["report"]},{"url":"https://bugzilla.suse.com/1235550","tags":["report"]},{"url":"https://bugzilla.suse.com/1235552","tags":["report"]},{"url":"https://bugzilla.suse.com/1235555","tags":["report"]},{"url":"https://bugzilla.suse.com/1235557","tags":["report"]},{"url":"https://bugzilla.suse.com/1235563","tags":["report"]},{"url":"https://bugzilla.suse.com/1235564","tags":["report"]},{"url":"https://bugzilla.suse.com/1235565","tags":["report"]},{"url":"https://bugzilla.suse.com/1235568","tags":["report"]},{"url":"https://bugzilla.suse.com/1235570","tags":["report"]},{"url":"https://bugzilla.suse.com/1235571","tags":["report"]},{"url":"https://bugzilla.suse.com/1235577","tags":["report"]},{"url":"https://bugzilla.suse.com/1235584","tags":["report"]},{"url":"https://bugzilla.suse.com/1235587","tags":["report"]},{"url":"https://bugzilla.suse.com/1235611","tags":["report"]},{"url":"https://bugzilla.suse.com/1235616","tags":["report"]},{"url":"https://bugzilla.suse.com/1235622","tags":["report"]},{"url":"https://bugzilla.suse.com/1235627","tags":["report"]},{"url":"https://bugzilla.suse.com/1235632","tags":["report"]},{"url":"https://bugzilla.suse.com/1235635","tags":["report"]},{"url":"https://bugzilla.suse.com/1235641","tags":["report"]},{"url":"https://bugzilla.suse.com/1235643","tags":["report"]},{"url":"https://bugzilla.suse.com/1235645","tags":["report"]},{"url":"https://bugzilla.suse.com/1235646","tags":["report"]},{"url":"https://bugzilla.suse.com/1235647","tags":["report"]},{"url":"https://bugzilla.suse.com/1235650","tags":["report"]},{"url":"https://bugzilla.suse.com/1235653","tags":["report"]},{"url":"https://bugzilla.suse.com/1235657","tags":["report"]},{"url":"https://bugzilla.suse.com/1235663","tags":["report"]},{"url":"https://bugzilla.suse.com/1235700","tags":["report"]},{"url":"https://bugzilla.suse.com/1235705","tags":["report"]},{"url":"https://bugzilla.suse.com/1235707","tags":["report"]},{"url":"https://bugzilla.suse.com/1235708","tags":["report"]},{"url":"https://bugzilla.suse.com/1235710","tags":["report"]},{"url":"https://bugzilla.suse.com/1235714","tags":["report"]},{"url":"https://bugzilla.suse.com/1235716","tags":["report"]},{"url":"https://bugzilla.suse.com/1235720","tags":["report"]},{"url":"https://bugzilla.suse.com/1235723","tags":["report"]},{"url":"https://bugzilla.suse.com/1235727","tags":["report"]},{"url":"https://bugzilla.suse.com/1235730","tags":["report"]},{"url":"https://bugzilla.suse.com/1235737","tags":["report"]},{"url":"https://bugzilla.suse.com/1235739","tags":["report"]},{"url":"https://bugzilla.suse.com/1235745","tags":["report"]},{"url":"https://bugzilla.suse.com/1235747","tags":["report"]},{"url":"https://bugzilla.suse.com/1235750","tags":["report"]},{"url":"https://bugzilla.suse.com/1235753","tags":["report"]},{"url":"https://bugzilla.suse.com/1235759","tags":["report"]},{"url":"https://bugzilla.suse.com/1235764","tags":["report"]},{"url":"https://bugzilla.suse.com/1235768","tags":["report"]},{"url":"https://bugzilla.suse.com/1235776","tags":["report"]},{"url":"https://bugzilla.suse.com/1235777","tags":["report"]},{"url":"https://bugzilla.suse.com/1235778","tags":["report"]},{"url":"https://bugzilla.suse.com/1235779","tags":["report"]},{"url":"https://bugzilla.suse.com/1235793","tags":["report"]},{"url":"https://bugzilla.suse.com/1235798","tags":["report"]},{"url":"https://bugzilla.suse.com/1235806","tags":["report"]},{"url":"https://bugzilla.suse.com/1235808","tags":["report"]},{"url":"https://bugzilla.suse.com/1235812","tags":["report"]},{"url":"https://bugzilla.suse.com/1235814","tags":["report"]},{"url":"https://bugzilla.suse.com/1235818","tags":["report"]},{"url":"https://bugzilla.suse.com/1235842","tags":["report"]},{"url":"https://bugzilla.suse.com/1235894","tags":["report"]},{"url":"https://bugzilla.suse.com/1235902","tags":["report"]},{"url":"https://bugzilla.suse.com/1235903","tags":["report"]},{"url":"https://bugzilla.suse.com/1235906","tags":["report"]},{"url":"https://bugzilla.suse.com/1235918","tags":["report"]},{"url":"https://bugzilla.suse.com/1235919","tags":["report"]},{"url":"https://bugzilla.suse.com/1235920","tags":["report"]},{"url":"https://bugzilla.suse.com/1235924","tags":["report"]},{"url":"https://bugzilla.suse.com/1235940","tags":["report"]},{"url":"https://bugzilla.suse.com/1235946","tags":["report"]},{"url":"https://bugzilla.suse.com/1235952","tags":["report"]},{"url":"https://bugzilla.suse.com/1235964","tags":["report"]},{"url":"https://bugzilla.suse.com/1235965","tags":["report"]},{"url":"https://bugzilla.suse.com/1235967","tags":["report"]},{"url":"https://bugzilla.suse.com/1235969","tags":["report"]},{"url":"https://bugzilla.suse.com/1235976","tags":["report"]},{"url":"https://bugzilla.suse.com/1235977","tags":["report"]},{"url":"https://bugzilla.suse.com/1236078","tags":["report"]},{"url":"https://bugzilla.suse.com/1236080","tags":["report"]},{"url":"https://bugzilla.suse.com/1236082","tags":["report"]},{"url":"https://bugzilla.suse.com/1236088","tags":["report"]},{"url":"https://bugzilla.suse.com/1236090","tags":["report"]},{"url":"https://bugzilla.suse.com/1236091","tags":["report"]},{"url":"https://bugzilla.suse.com/1236096","tags":["report"]},{"url":"https://bugzilla.suse.com/1236097","tags":["report"]},{"url":"https://bugzilla.suse.com/1236098","tags":["report"]},{"url":"https://bugzilla.suse.com/1236101","tags":["report"]},{"url":"https://bugzilla.suse.com/1236102","tags":["report"]},{"url":"https://bugzilla.suse.com/1236104","tags":["report"]},{"url":"https://bugzilla.suse.com/1236106","tags":["report"]},{"url":"https://bugzilla.suse.com/1236120","tags":["report"]},{"url":"https://bugzilla.suse.com/1236125","tags":["report"]},{"url":"https://bugzilla.suse.com/1236131","tags":["report"]},{"url":"https://bugzilla.suse.com/1236138","tags":["report"]},{"url":"https://bugzilla.suse.com/1236143","tags":["report"]},{"url":"https://bugzilla.suse.com/1236144","tags":["report"]},{"url":"https://bugzilla.suse.com/1236145","tags":["report"]},{"url":"https://bugzilla.suse.com/1236168","tags":["report"]},{"url":"https://bugzilla.suse.com/1236178","tags":["report"]},{"url":"https://bugzilla.suse.com/1236180","tags":["report"]},{"url":"https://bugzilla.suse.com/1236181","tags":["report"]},{"url":"https://bugzilla.suse.com/1236190","tags":["report"]},{"url":"https://bugzilla.suse.com/1236198","tags":["report"]},{"url":"https://bugzilla.suse.com/1236227","tags":["report"]},{"url":"https://bugzilla.suse.com/1236248","tags":["report"]},{"url":"https://www.suse.com/security/cve/CVE-2023-52489","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-52923","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-26596","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-26924","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-27397","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-35839","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-36476","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-36908","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-36915","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-39282","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-39480","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-41042","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-43913","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-44934","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-44996","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-45828","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-46680","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-46765","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-46800","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-46896","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-47141","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-47143","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-47678","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-47809","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-48873","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-48881","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-49569","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-49854","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-49884","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-49915","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-49944","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-49951","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-49952","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-49998","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-50016","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-50018","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-50039","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-50047","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-50051","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-50106","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-50143","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-50151","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-50154","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-50199","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-50202","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-50203","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-50211","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-50228","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-50252","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-50256","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-50262","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-50272","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-50278","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-50279","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-50280","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-50296","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-50299","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-52332","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-53043","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-53050","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-53051","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-53055","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-53056","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-53064","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-53090","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-53091","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-53095","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-53099","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-53103","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-53105","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-53110","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-53111","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-53113","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-53117","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-53118","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-53119","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-53120","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-53121","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-53122","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-53125","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-53126","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-53127","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-53129","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-53130","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-53131","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-53133","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-53134","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-53136","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-53138","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-53141","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-53142","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-53144","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-53146","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-53148","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-53150","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-53151","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-53154","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-53155","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-53156","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-53157","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-53158","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-53159","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-53160","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-53161","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-53162","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-53164","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-53166","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-53168","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-53169","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-53170","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-53171","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-53172","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-53173","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-53174","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-53175","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-53179","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-53180","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-53185","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-53188","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-53190","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-53191","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-53194","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-53195","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-53196","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-53197","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-53198","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-53200","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-53201","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-53202","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-53206","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-53207","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-53208","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-53209","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-53210","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-53213","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-53214","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-53215","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-53216","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-53217","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-53222","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-53224","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-53227","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-53229","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-53230","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-53231","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-53232","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-53233","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-53234","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-53236","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-53237","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-53239","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-53240","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-53241","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-53685","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-53690","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-54680","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-55639","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-55881","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-55916","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-56369","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-56372","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-56531","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-56532","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-56533","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-56536","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-56538","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-56539","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-56543","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-56546","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-56548","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-56549","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-56551","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-56557","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-56558","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-56562","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-56566","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-56567","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-56568","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-56569","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-56570","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-56571","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-56572","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-56573","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-56574","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-56575","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-56576","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-56577","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-56578","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-56582","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-56584","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-56587","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-56588","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-56589","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-56590","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-56593","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-56594","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-56595","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-56596","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-56597","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-56598","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-56599","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-5660","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-56602","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-56603","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-56604","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-56605","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-56606","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-56607","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-56609","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-56611","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-56614","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-56615","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-56616","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-56617","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-56619","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-56620","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-56622","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-56623","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-56625","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-56629","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-56630","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-56631","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-56632","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-56634","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-56635","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-56636","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-56637","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-56641","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-56642","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-56643","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-56644","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-56645","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-56648","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-56649","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-56651","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-56654","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-56656","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-56659","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-56660","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-56661","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-56662","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-56663","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-56664","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-56667","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-56670","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-56672","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-56675","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-56677","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-56678","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-56681","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-56683","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-56687","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-56688","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-56690","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-56691","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-56694","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-56698","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-56700","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-56701","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-56704","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-56705","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-56708","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-56709","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-56712","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-56716","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-56722","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-56723","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-56724","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-56729","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-56739","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-56741","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-56745","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-56746","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-56747","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-56748","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-56752","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-56754","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-56755","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-56756","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-56759","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-56760","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-56765","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-56766","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-56767","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-56769","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-56774","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-56775","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-56776","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-56777","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-56778","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-56779","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-56780","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-56787","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-57791","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-57792","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-57793","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-57795","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-57798","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-57801","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-57804","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-57809","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-57838","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-57849","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-57850","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-57857","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-57874","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-57876","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-57887","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-57888","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-57890","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-57892","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-57893","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-57896","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-57897","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-57899","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-57903","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-57904","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-57906","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-57907","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-57908","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-57910","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-57911","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-57912","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-57913","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-57915","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-57916","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-57922","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-57926","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-57929","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-57932","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-57933","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-57935","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-57936","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-57940","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-8805","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-21632","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-21645","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-21646","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-21649","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-21650","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-21651","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-21656","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-21662","tags":["web"]},{"url":"https://www.suse.com/support/update/announcement/2025/suse-su-20250428-1/","tags":["advisory"]},{"url":"https://bugzilla.suse.com/1222803","tags":["report"]},{"url":"https://bugzilla.suse.com/1224049","tags":["report"]},{"url":"https://bugzilla.suse.com/1226980","tags":["report"]},{"url":"https://bugzilla.suse.com/1232101","tags":["report"]},{"url":"https://bugzilla.suse.com/1232161","tags":["report"]},{"url":"https://bugzilla.suse.com/1233221","tags":["report"]},{"url":"https://bugzilla.suse.com/1233248","tags":["report"]},{"url":"https://bugzilla.suse.com/1233522","tags":["report"]},{"url":"https://bugzilla.suse.com/1233778","tags":["report"]},{"url":"https://bugzilla.suse.com/1234683","tags":["report"]},{"url":"https://bugzilla.suse.com/1234693","tags":["report"]},{"url":"https://bugzilla.suse.com/1234947","tags":["report"]},{"url":"https://bugzilla.suse.com/1235001","tags":["report"]},{"url":"https://bugzilla.suse.com/1235217","tags":["report"]},{"url":"https://bugzilla.suse.com/1235230","tags":["report"]},{"url":"https://bugzilla.suse.com/1235390","tags":["report"]},{"url":"https://bugzilla.suse.com/1235418","tags":["report"]},{"url":"https://bugzilla.suse.com/1235430","tags":["report"]},{"url":"https://bugzilla.suse.com/1235487","tags":["report"]},{"url":"https://bugzilla.suse.com/1235489","tags":["report"]},{"url":"https://bugzilla.suse.com/1235498","tags":["report"]},{"url":"https://bugzilla.suse.com/1235545","tags":["report"]},{"url":"https://bugzilla.suse.com/1235578","tags":["report"]},{"url":"https://bugzilla.suse.com/1235582","tags":["report"]},{"url":"https://bugzilla.suse.com/1235583","tags":["report"]},{"url":"https://bugzilla.suse.com/1235612","tags":["report"]},{"url":"https://bugzilla.suse.com/1235638","tags":["report"]},{"url":"https://bugzilla.suse.com/1235656","tags":["report"]},{"url":"https://bugzilla.suse.com/1235686","tags":["report"]},{"url":"https://bugzilla.suse.com/1235865","tags":["report"]},{"url":"https://bugzilla.suse.com/1235874","tags":["report"]},{"url":"https://bugzilla.suse.com/1235941","tags":["report"]},{"url":"https://bugzilla.suse.com/1235948","tags":["report"]},{"url":"https://bugzilla.suse.com/1236127","tags":["report"]},{"url":"https://bugzilla.suse.com/1236160","tags":["report"]},{"url":"https://bugzilla.suse.com/1236161","tags":["report"]},{"url":"https://bugzilla.suse.com/1236163","tags":["report"]},{"url":"https://bugzilla.suse.com/1236182","tags":["report"]},{"url":"https://bugzilla.suse.com/1236192","tags":["report"]},{"url":"https://bugzilla.suse.com/1236245","tags":["report"]},{"url":"https://bugzilla.suse.com/1236247","tags":["report"]},{"url":"https://bugzilla.suse.com/1236260","tags":["report"]},{"url":"https://bugzilla.suse.com/1236262","tags":["report"]},{"url":"https://bugzilla.suse.com/1236628","tags":["report"]},{"url":"https://bugzilla.suse.com/1236688","tags":["report"]},{"url":"https://bugzilla.suse.com/1236696","tags":["report"]},{"url":"https://bugzilla.suse.com/1236698","tags":["report"]},{"url":"https://bugzilla.suse.com/1236703","tags":["report"]},{"url":"https://bugzilla.suse.com/1236732","tags":["report"]},{"url":"https://bugzilla.suse.com/1236733","tags":["report"]},{"url":"https://bugzilla.suse.com/1236757","tags":["report"]},{"url":"https://bugzilla.suse.com/1236758","tags":["report"]},{"url":"https://bugzilla.suse.com/1236760","tags":["report"]},{"url":"https://www.suse.com/security/cve/CVE-2024-49948","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-49978","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-50251","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-50258","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-50304","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-53187","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-53203","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-56600","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-56601","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-56608","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-56610","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-56650","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-56665","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-56679","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-56693","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-56707","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-56715","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-56725","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-56726","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-56727","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-56728","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-56763","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-57802","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-57884","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-57917","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-57931","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-57938","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-57946","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-21652","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-21653","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-21655","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-21663","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-21664","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-21674","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-21676","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-21678","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-21682","tags":["web"]},{"url":"https://www.suse.com/support/update/announcement/2025/suse-su-20250499-1/","tags":["advisory"]},{"url":"https://bugzilla.suse.com/1231088","tags":["report"]},{"url":"https://bugzilla.suse.com/1235244","tags":["report"]},{"url":"https://bugzilla.suse.com/1235441","tags":["report"]},{"url":"https://bugzilla.suse.com/1235914","tags":["report"]},{"url":"https://bugzilla.suse.com/1236680","tags":["report"]},{"url":"https://bugzilla.suse.com/1236683","tags":["report"]},{"url":"https://bugzilla.suse.com/1236685","tags":["report"]},{"url":"https://bugzilla.suse.com/1236694","tags":["report"]},{"url":"https://bugzilla.suse.com/1236761","tags":["report"]},{"url":"https://www.suse.com/security/cve/CVE-2024-26810","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-46858","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-56592","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-56658","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-57882","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-21666","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-21669","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-21670","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-21675","tags":["web"]},{"url":"https://www.suse.com/support/update/announcement/2025/suse-su-20250557-1/","tags":["advisory"]},{"url":"https://www.suse.com/support/update/announcement/2025/suse-su-202520165-1/","tags":["advisory"]},{"url":"https://www.suse.com/support/update/announcement/2025/suse-su-202520166-1/","tags":["advisory"]},{"url":"https://bugzilla.suse.com/1065729","tags":["report"]},{"url":"https://bugzilla.suse.com/1181674","tags":["report"]},{"url":"https://bugzilla.suse.com/1207948","tags":["report"]},{"url":"https://bugzilla.suse.com/1216702","tags":["report"]},{"url":"https://bugzilla.suse.com/1219170","tags":["report"]},{"url":"https://bugzilla.suse.com/1219596","tags":["report"]},{"url":"https://bugzilla.suse.com/1220021","tags":["report"]},{"url":"https://bugzilla.suse.com/1220328","tags":["report"]},{"url":"https://bugzilla.suse.com/1220430","tags":["report"]},{"url":"https://bugzilla.suse.com/1221044","tags":["report"]},{"url":"https://bugzilla.suse.com/1221303","tags":["report"]},{"url":"https://bugzilla.suse.com/1221858","tags":["report"]},{"url":"https://bugzilla.suse.com/1222426","tags":["report"]},{"url":"https://bugzilla.suse.com/1222608","tags":["report"]},{"url":"https://bugzilla.suse.com/1222721","tags":["report"]},{"url":"https://bugzilla.suse.com/1222775","tags":["report"]},{"url":"https://bugzilla.suse.com/1222780","tags":["report"]},{"url":"https://bugzilla.suse.com/1223020","tags":["report"]},{"url":"https://bugzilla.suse.com/1223023","tags":["report"]},{"url":"https://bugzilla.suse.com/1223024","tags":["report"]},{"url":"https://bugzilla.suse.com/1223038","tags":["report"]},{"url":"https://bugzilla.suse.com/1223039","tags":["report"]},{"url":"https://bugzilla.suse.com/1223041","tags":["report"]},{"url":"https://bugzilla.suse.com/1223046","tags":["report"]},{"url":"https://bugzilla.suse.com/1223051","tags":["report"]},{"url":"https://bugzilla.suse.com/1223052","tags":["report"]},{"url":"https://bugzilla.suse.com/1223058","tags":["report"]},{"url":"https://bugzilla.suse.com/1223061","tags":["report"]},{"url":"https://bugzilla.suse.com/1223076","tags":["report"]},{"url":"https://bugzilla.suse.com/1223113","tags":["report"]},{"url":"https://bugzilla.suse.com/1223187","tags":["report"]},{"url":"https://bugzilla.suse.com/1223285","tags":["report"]},{"url":"https://bugzilla.suse.com/1223315","tags":["report"]},{"url":"https://bugzilla.suse.com/1223591","tags":["report"]},{"url":"https://bugzilla.suse.com/1223592","tags":["report"]},{"url":"https://bugzilla.suse.com/1223633","tags":["report"]},{"url":"https://bugzilla.suse.com/1223637","tags":["report"]},{"url":"https://bugzilla.suse.com/1223641","tags":["report"]},{"url":"https://bugzilla.suse.com/1223649","tags":["report"]},{"url":"https://bugzilla.suse.com/1223650","tags":["report"]},{"url":"https://bugzilla.suse.com/1223651","tags":["report"]},{"url":"https://bugzilla.suse.com/1223652","tags":["report"]},{"url":"https://bugzilla.suse.com/1223654","tags":["report"]},{"url":"https://bugzilla.suse.com/1223660","tags":["report"]},{"url":"https://bugzilla.suse.com/1223661","tags":["report"]},{"url":"https://bugzilla.suse.com/1223665","tags":["report"]},{"url":"https://bugzilla.suse.com/1223666","tags":["report"]},{"url":"https://bugzilla.suse.com/1223671","tags":["report"]},{"url":"https://bugzilla.suse.com/1223675","tags":["report"]},{"url":"https://bugzilla.suse.com/1223677","tags":["report"]},{"url":"https://bugzilla.suse.com/1223678","tags":["report"]},{"url":"https://bugzilla.suse.com/1223696","tags":["report"]},{"url":"https://bugzilla.suse.com/1223698","tags":["report"]},{"url":"https://bugzilla.suse.com/1223705","tags":["report"]},{"url":"https://bugzilla.suse.com/1223712","tags":["report"]},{"url":"https://bugzilla.suse.com/1223718","tags":["report"]},{"url":"https://bugzilla.suse.com/1223728","tags":["report"]},{"url":"https://bugzilla.suse.com/1223739","tags":["report"]},{"url":"https://bugzilla.suse.com/1223741","tags":["report"]},{"url":"https://bugzilla.suse.com/1223744","tags":["report"]},{"url":"https://bugzilla.suse.com/1223747","tags":["report"]},{"url":"https://bugzilla.suse.com/1223748","tags":["report"]},{"url":"https://bugzilla.suse.com/1223750","tags":["report"]},{"url":"https://bugzilla.suse.com/1223752","tags":["report"]},{"url":"https://bugzilla.suse.com/1223754","tags":["report"]},{"url":"https://bugzilla.suse.com/1223757","tags":["report"]},{"url":"https://bugzilla.suse.com/1223759","tags":["report"]},{"url":"https://bugzilla.suse.com/1223761","tags":["report"]},{"url":"https://bugzilla.suse.com/1223762","tags":["report"]},{"url":"https://bugzilla.suse.com/1223782","tags":["report"]},{"url":"https://bugzilla.suse.com/1223787","tags":["report"]},{"url":"https://bugzilla.suse.com/1223788","tags":["report"]},{"url":"https://bugzilla.suse.com/1223789","tags":["report"]},{"url":"https://bugzilla.suse.com/1223790","tags":["report"]},{"url":"https://bugzilla.suse.com/1223802","tags":["report"]},{"url":"https://bugzilla.suse.com/1223805","tags":["report"]},{"url":"https://bugzilla.suse.com/1223827","tags":["report"]},{"url":"https://bugzilla.suse.com/1223831","tags":["report"]},{"url":"https://bugzilla.suse.com/1223834","tags":["report"]},{"url":"https://bugzilla.suse.com/1223869","tags":["report"]},{"url":"https://bugzilla.suse.com/1223874","tags":["report"]},{"url":"https://bugzilla.suse.com/1224174","tags":["report"]},{"url":"https://bugzilla.suse.com/1224177","tags":["report"]},{"url":"https://bugzilla.suse.com/1224180","tags":["report"]},{"url":"https://bugzilla.suse.com/1224423","tags":["report"]},{"url":"https://bugzilla.suse.com/1224432","tags":["report"]},{"url":"https://bugzilla.suse.com/1224433","tags":["report"]},{"url":"https://bugzilla.suse.com/1224437","tags":["report"]},{"url":"https://bugzilla.suse.com/1224438","tags":["report"]},{"url":"https://bugzilla.suse.com/1224443","tags":["report"]},{"url":"https://bugzilla.suse.com/1224445","tags":["report"]},{"url":"https://bugzilla.suse.com/1224449","tags":["report"]},{"url":"https://bugzilla.suse.com/1224479","tags":["report"]},{"url":"https://bugzilla.suse.com/1224480","tags":["report"]},{"url":"https://bugzilla.suse.com/1224482","tags":["report"]},{"url":"https://bugzilla.suse.com/1224486","tags":["report"]},{"url":"https://bugzilla.suse.com/1224487","tags":["report"]},{"url":"https://bugzilla.suse.com/1224491","tags":["report"]},{"url":"https://bugzilla.suse.com/1224492","tags":["report"]},{"url":"https://bugzilla.suse.com/1224494","tags":["report"]},{"url":"https://bugzilla.suse.com/1224495","tags":["report"]},{"url":"https://bugzilla.suse.com/1224500","tags":["report"]},{"url":"https://bugzilla.suse.com/1224501","tags":["report"]},{"url":"https://bugzilla.suse.com/1224504","tags":["report"]},{"url":"https://bugzilla.suse.com/1224505","tags":["report"]},{"url":"https://bugzilla.suse.com/1224506","tags":["report"]},{"url":"https://bugzilla.suse.com/1224507","tags":["report"]},{"url":"https://bugzilla.suse.com/1224508","tags":["report"]},{"url":"https://bugzilla.suse.com/1224509","tags":["report"]},{"url":"https://bugzilla.suse.com/1224513","tags":["report"]},{"url":"https://bugzilla.suse.com/1224517","tags":["report"]},{"url":"https://bugzilla.suse.com/1224519","tags":["report"]},{"url":"https://bugzilla.suse.com/1224521","tags":["report"]},{"url":"https://bugzilla.suse.com/1224524","tags":["report"]},{"url":"https://bugzilla.suse.com/1224526","tags":["report"]},{"url":"https://bugzilla.suse.com/1224537","tags":["report"]},{"url":"https://bugzilla.suse.com/1224542","tags":["report"]},{"url":"https://bugzilla.suse.com/1224546","tags":["report"]},{"url":"https://bugzilla.suse.com/1224552","tags":["report"]},{"url":"https://bugzilla.suse.com/1224555","tags":["report"]},{"url":"https://bugzilla.suse.com/1224557","tags":["report"]},{"url":"https://bugzilla.suse.com/1224558","tags":["report"]},{"url":"https://bugzilla.suse.com/1224559","tags":["report"]},{"url":"https://bugzilla.suse.com/1224562","tags":["report"]},{"url":"https://bugzilla.suse.com/1224566","tags":["report"]},{"url":"https://bugzilla.suse.com/1224567","tags":["report"]},{"url":"https://bugzilla.suse.com/1224568","tags":["report"]},{"url":"https://bugzilla.suse.com/1224569","tags":["report"]},{"url":"https://bugzilla.suse.com/1224571","tags":["report"]},{"url":"https://bugzilla.suse.com/1224573","tags":["report"]},{"url":"https://bugzilla.suse.com/1224576","tags":["report"]},{"url":"https://bugzilla.suse.com/1224577","tags":["report"]},{"url":"https://bugzilla.suse.com/1224578","tags":["report"]},{"url":"https://bugzilla.suse.com/1224579","tags":["report"]},{"url":"https://bugzilla.suse.com/1224582","tags":["report"]},{"url":"https://bugzilla.suse.com/1224585","tags":["report"]},{"url":"https://bugzilla.suse.com/1224586","tags":["report"]},{"url":"https://bugzilla.suse.com/1224587","tags":["report"]},{"url":"https://bugzilla.suse.com/1224588","tags":["report"]},{"url":"https://bugzilla.suse.com/1224592","tags":["report"]},{"url":"https://bugzilla.suse.com/1224596","tags":["report"]},{"url":"https://bugzilla.suse.com/1224598","tags":["report"]},{"url":"https://bugzilla.suse.com/1224600","tags":["report"]},{"url":"https://bugzilla.suse.com/1224601","tags":["report"]},{"url":"https://bugzilla.suse.com/1224603","tags":["report"]},{"url":"https://bugzilla.suse.com/1224605","tags":["report"]},{"url":"https://bugzilla.suse.com/1224607","tags":["report"]},{"url":"https://bugzilla.suse.com/1224609","tags":["report"]},{"url":"https://bugzilla.suse.com/1224611","tags":["report"]},{"url":"https://bugzilla.suse.com/1224613","tags":["report"]},{"url":"https://bugzilla.suse.com/1224615","tags":["report"]},{"url":"https://bugzilla.suse.com/1224617","tags":["report"]},{"url":"https://bugzilla.suse.com/1224618","tags":["report"]},{"url":"https://bugzilla.suse.com/1224620","tags":["report"]},{"url":"https://bugzilla.suse.com/1224622","tags":["report"]},{"url":"https://bugzilla.suse.com/1224623","tags":["report"]},{"url":"https://bugzilla.suse.com/1224624","tags":["report"]},{"url":"https://bugzilla.suse.com/1224626","tags":["report"]},{"url":"https://bugzilla.suse.com/1224627","tags":["report"]},{"url":"https://bugzilla.suse.com/1224629","tags":["report"]},{"url":"https://bugzilla.suse.com/1224630","tags":["report"]},{"url":"https://bugzilla.suse.com/1224632","tags":["report"]},{"url":"https://bugzilla.suse.com/1224633","tags":["report"]},{"url":"https://bugzilla.suse.com/1224634","tags":["report"]},{"url":"https://bugzilla.suse.com/1224637","tags":["report"]},{"url":"https://bugzilla.suse.com/1224639","tags":["report"]},{"url":"https://bugzilla.suse.com/1224640","tags":["report"]},{"url":"https://bugzilla.suse.com/1224643","tags":["report"]},{"url":"https://bugzilla.suse.com/1224644","tags":["report"]},{"url":"https://bugzilla.suse.com/1224646","tags":["report"]},{"url":"https://bugzilla.suse.com/1224647","tags":["report"]},{"url":"https://bugzilla.suse.com/1224650","tags":["report"]},{"url":"https://bugzilla.suse.com/1224651","tags":["report"]},{"url":"https://bugzilla.suse.com/1224653","tags":["report"]},{"url":"https://bugzilla.suse.com/1224654","tags":["report"]},{"url":"https://bugzilla.suse.com/1224657","tags":["report"]},{"url":"https://bugzilla.suse.com/1224660","tags":["report"]},{"url":"https://bugzilla.suse.com/1224663","tags":["report"]},{"url":"https://bugzilla.suse.com/1224665","tags":["report"]},{"url":"https://bugzilla.suse.com/1224666","tags":["report"]},{"url":"https://bugzilla.suse.com/1224671","tags":["report"]},{"url":"https://bugzilla.suse.com/1224675","tags":["report"]},{"url":"https://bugzilla.suse.com/1224676","tags":["report"]},{"url":"https://bugzilla.suse.com/1224677","tags":["report"]},{"url":"https://bugzilla.suse.com/1224680","tags":["report"]},{"url":"https://bugzilla.suse.com/1224681","tags":["report"]},{"url":"https://bugzilla.suse.com/1224682","tags":["report"]},{"url":"https://bugzilla.suse.com/1224683","tags":["report"]},{"url":"https://bugzilla.suse.com/1224685","tags":["report"]},{"url":"https://bugzilla.suse.com/1224686","tags":["report"]},{"url":"https://bugzilla.suse.com/1224687","tags":["report"]},{"url":"https://bugzilla.suse.com/1224688","tags":["report"]},{"url":"https://bugzilla.suse.com/1224692","tags":["report"]},{"url":"https://bugzilla.suse.com/1224696","tags":["report"]},{"url":"https://bugzilla.suse.com/1224697","tags":["report"]},{"url":"https://bugzilla.suse.com/1224699","tags":["report"]},{"url":"https://bugzilla.suse.com/1224701","tags":["report"]},{"url":"https://bugzilla.suse.com/1224703","tags":["report"]},{"url":"https://bugzilla.suse.com/1224704","tags":["report"]},{"url":"https://bugzilla.suse.com/1224705","tags":["report"]},{"url":"https://bugzilla.suse.com/1224706","tags":["report"]},{"url":"https://bugzilla.suse.com/1224707","tags":["report"]},{"url":"https://bugzilla.suse.com/1224709","tags":["report"]},{"url":"https://bugzilla.suse.com/1224710","tags":["report"]},{"url":"https://bugzilla.suse.com/1224712","tags":["report"]},{"url":"https://bugzilla.suse.com/1224714","tags":["report"]},{"url":"https://bugzilla.suse.com/1224716","tags":["report"]},{"url":"https://bugzilla.suse.com/1224717","tags":["report"]},{"url":"https://bugzilla.suse.com/1224719","tags":["report"]},{"url":"https://bugzilla.suse.com/1224722","tags":["report"]},{"url":"https://bugzilla.suse.com/1224723","tags":["report"]},{"url":"https://bugzilla.suse.com/1224728","tags":["report"]},{"url":"https://bugzilla.suse.com/1224729","tags":["report"]},{"url":"https://bugzilla.suse.com/1224730","tags":["report"]},{"url":"https://bugzilla.suse.com/1224731","tags":["report"]},{"url":"https://bugzilla.suse.com/1224732","tags":["report"]},{"url":"https://bugzilla.suse.com/1224733","tags":["report"]},{"url":"https://bugzilla.suse.com/1224736","tags":["report"]},{"url":"https://bugzilla.suse.com/1224738","tags":["report"]},{"url":"https://bugzilla.suse.com/1224739","tags":["report"]},{"url":"https://bugzilla.suse.com/1224740","tags":["report"]},{"url":"https://bugzilla.suse.com/1224741","tags":["report"]},{"url":"https://bugzilla.suse.com/1224747","tags":["report"]},{"url":"https://bugzilla.suse.com/1224749","tags":["report"]},{"url":"https://bugzilla.suse.com/1224803","tags":["report"]},{"url":"https://bugzilla.suse.com/1224804","tags":["report"]},{"url":"https://bugzilla.suse.com/1225502","tags":["report"]},{"url":"https://bugzilla.suse.com/1225579","tags":["report"]},{"url":"https://bugzilla.suse.com/1225593","tags":["report"]},{"url":"https://bugzilla.suse.com/1225692","tags":["report"]},{"url":"https://bugzilla.suse.com/1225694","tags":["report"]},{"url":"https://bugzilla.suse.com/1225695","tags":["report"]},{"url":"https://bugzilla.suse.com/1225698","tags":["report"]},{"url":"https://bugzilla.suse.com/1225699","tags":["report"]},{"url":"https://bugzilla.suse.com/1225704","tags":["report"]},{"url":"https://bugzilla.suse.com/1225705","tags":["report"]},{"url":"https://bugzilla.suse.com/1225708","tags":["report"]},{"url":"https://bugzilla.suse.com/1225710","tags":["report"]},{"url":"https://bugzilla.suse.com/1225715","tags":["report"]},{"url":"https://bugzilla.suse.com/1225720","tags":["report"]},{"url":"https://bugzilla.suse.com/1225722","tags":["report"]},{"url":"https://bugzilla.suse.com/1225728","tags":["report"]},{"url":"https://bugzilla.suse.com/1225734","tags":["report"]},{"url":"https://bugzilla.suse.com/1225735","tags":["report"]},{"url":"https://bugzilla.suse.com/1225736","tags":["report"]},{"url":"https://bugzilla.suse.com/1225747","tags":["report"]},{"url":"https://bugzilla.suse.com/1225748","tags":["report"]},{"url":"https://bugzilla.suse.com/1225749","tags":["report"]},{"url":"https://bugzilla.suse.com/1225750","tags":["report"]},{"url":"https://bugzilla.suse.com/1225769","tags":["report"]},{"url":"https://bugzilla.suse.com/1225775","tags":["report"]},{"url":"https://bugzilla.suse.com/1229025","tags":["report"]},{"url":"https://www.suse.com/security/cve/CVE-2023-47233","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-52463","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-52472","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-52591","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-52653","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-52657","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-52658","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-52660","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-52661","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-52662","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-52663","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-52664","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-52667","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-52669","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-52670","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-52671","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-52673","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-52675","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-52676","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-52678","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-52679","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-52681","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-52683","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-52685","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-52686","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-52687","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-52690","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-52691","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-52693","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-52694","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-52695","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-52696","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-52697","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-52882","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-22099","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-26611","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-26742","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-26761","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-26764","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-26786","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-26794","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-26846","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-26853","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-26854","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-26855","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-26856","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-26857","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-26858","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-26861","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-26866","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-26868","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-26870","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-26881","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-26900","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-26903","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-26922","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-26932","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-26934","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-26935","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-26937","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-26938","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-26940","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-26943","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-26949","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-26950","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-26951","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-26957","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-26961","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-26962","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-26963","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-26964","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-26973","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-26983","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-26984","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-26986","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-26988","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-26989","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-26994","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-26995","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-26996","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-26997","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-26999","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-27000","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-27001","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-27002","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-27003","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-27004","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-27008","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-27027","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-27028","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-27029","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-27030","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-27031","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-27046","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-27057","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-27062","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-27067","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-27080","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-27388","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-27389","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-27398","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-27399","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-27400","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-27405","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-27410","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-27411","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-27412","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-27413","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-27416","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-27432","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-27434","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-27435","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-27436","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-35784","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-35786","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-35788","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-35789","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-35790","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-35794","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-35795","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-35796","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-35799","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-35800","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-35801","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-35806","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-35808","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-35809","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-35810","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-35811","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-35812","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-35813","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-35815","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-35817","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-35819","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-35821","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-35822","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-35823","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-35824","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-35825","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-35828","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-35829","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-35830","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-35833","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-35834","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-35835","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-35836","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-35837","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-35838","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-35841","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-35842","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-35845","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-35847","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-35849","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-35850","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-35851","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-35875","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-35878","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-35879","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-35883","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-35885","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-35887","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-35889","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-35891","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-35901","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-35904","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-35907","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-35909","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-35911","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-35912","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-35914","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-35915","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-35916","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-35922","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-35924","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-35927","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-35928","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-35930","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-35932","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-35933","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-35936","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-35937","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-35938","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-35940","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-35945","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-35946","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-35947","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-35950","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-35951","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-35952","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-35953","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-35954","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-35955","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-35958","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-35959","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-35960","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-35961","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-35963","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-35965","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-35966","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-35967","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-35971","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-35972","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-35973","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-35974","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-35975","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-35977","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-35978","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-35982","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-35984","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-35986","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-35989","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-35990","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-35992","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-35995","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-35997","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-36002","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-36009","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-36011","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-36012","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-36014","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-36018","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-36019","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-36020","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-36021","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-36025","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-36026","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-36029","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-36032","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-36880","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-36885","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-36891","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-36893","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-36894","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-36895","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-36896","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-36897","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-36898","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-36906","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-36921","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-36922","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-36928","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-36930","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-36931","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-36940","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-36941","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-36942","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-36944","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-36949","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-36950","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-36951","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-36955","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-36959","tags":["web"]},{"url":"https://www.suse.com/support/update/announcement/2025/suse-su-202520248-1/","tags":["advisory"]},{"url":"https://www.suse.com/support/update/announcement/2025/suse-su-202520249-1/","tags":["advisory"]},{"url":"https://ubuntu.com/security/CVE-2024-53232","tags":["report"]},{"url":"https://git.kernel.org/linus/ecda483339a5151e3ca30d6b82691ef6f1d17912","tags":["report"]},{"url":"https://ubuntu.com/security/notices/USN-7276-1","tags":["advisory"]},{"url":"https://ubuntu.com/security/notices/USN-7277-1","tags":["advisory"]},{"url":"https://ubuntu.com/security/notices/USN-7310-1","tags":["advisory"]},{"url":"https://ubuntu.com/security/notices/USN-7449-1","tags":["advisory"]},{"url":"https://ubuntu.com/security/notices/USN-7450-1","tags":["advisory"]},{"url":"https://ubuntu.com/security/notices/USN-7451-1","tags":["advisory"]},{"url":"https://ubuntu.com/security/notices/USN-7452-1","tags":["advisory"]},{"url":"https://ubuntu.com/security/notices/USN-7453-1","tags":["advisory"]},{"url":"https://ubuntu.com/security/notices/USN-7449-2","tags":["advisory"]},{"url":"https://ubuntu.com/security/notices/USN-7468-1","tags":["advisory"]},{"url":"https://ubuntu.com/security/notices/USN-7523-1","tags":["advisory"]},{"url":"https://ubuntu.com/security/notices/USN-7524-1","tags":["advisory"]},{"url":"https://ubuntu.com/security/CVE-2022-49034","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2023-52917","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-46869","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-47671","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-47675","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-47676","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-47677","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-47678","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-47679","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-47680","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-47681","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-47682","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-47684","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-47685","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-47686","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-47687","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-47688","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-47689","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-47690","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-47691","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-47692","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-47693","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-47694","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-47695","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-47696","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-47697","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-47698","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-47699","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-47700","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-47701","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-47702","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-47703","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-47705","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-47706","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-47707","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-47708","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-47709","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-47710","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-47711","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-47712","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-47713","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-47714","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-47716","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-47717","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-47718","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-47719","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-47720","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-47721","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-47723","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-47724","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-47726","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-47727","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-47728","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-47730","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-47731","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-47732","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-47733","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-47734","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-47735","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-47736","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-47737","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-47738","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-47739","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-47740","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-47741","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-47742","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-47743","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-47744","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-47745","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-47746","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-47747","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-47748","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-47749","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-47750","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-47751","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-47752","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-47753","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-47754","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-47756","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-47757","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-49850","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-49851","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-49852","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-49853","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-49855","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-49856","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-49857","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-49858","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-49859","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-49860","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-49861","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-49862","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-49863","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-49864","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-49865","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-49866","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-49867","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-49868","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-49869","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-49870","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-49871","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-49872","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-49873","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-49874","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-49875","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-49876","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-49877","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-49878","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-49879","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-49880","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-49881","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-49882","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-49883","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-49884","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-49885","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-49886","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-49887","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-49888","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-49889","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-49890","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-49891","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-49892","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-49894","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-49895","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-49900","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-49901","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-49902","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-49903","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-49924","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-49925","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-49926","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-49927","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-49928","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-49929","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-49930","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-49931","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-49932","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-49933","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-49934","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-49935","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-49936","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-49937","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-49938","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-49939","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-49940","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-49941","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-49942","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-49943","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-49944","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-49945","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-49946","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-49947","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-49948","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-49949","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-49950","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-49951","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-49952","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-49953","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-49954","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-49955","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-49956","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-49957","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-49958","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-49959","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-49960","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-49961","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-49962","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-49963","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-49964","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-49965","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-49966","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-49968","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-49969","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-49970","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-49971","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-49972","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-49973","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-49974","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-49975","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-49976","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-49977","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-49978","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-49979","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-49980","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-49981","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-49982","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-49983","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-49985","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-49986","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-49987","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-49988","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-49989","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-49991","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-49992","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-49994","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-49995","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-49996","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-49997","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-49998","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-49999","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50000","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50001","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50002","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50003","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50005","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50006","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50007","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50008","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50009","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50010","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50012","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50013","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50014","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50015","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50016","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50017","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50019","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50020","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50021","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50022","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50023","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50024","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50025","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50026","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50027","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50028","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50029","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50030","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50031","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50033","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50034","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50035","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50036","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50037","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50038","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50039","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50040","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50041","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50042","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50043","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50044","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50045","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50046","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50047","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50048","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50049","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50055","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50056","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50057","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50058","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50059","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50060","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50061","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50062","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50063","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50064","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50065","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50066","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50067","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50068","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50069","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50070","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50071","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50072","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50073","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50074","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50075","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50076","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50077","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50078","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50079","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50080","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50081","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50082","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50083","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50084","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50085","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50086","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50087","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50088","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50090","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50091","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50092","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50093","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50094","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50095","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50096","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50098","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50099","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50100","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50101","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50102","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50103","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50104","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50105","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50106","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50107","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50108","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50109","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50110","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50111","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50112","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50113","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50114","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50115","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50116","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50117","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50118","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50119","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50120","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50121","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50122","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50123","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50124","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50125","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50126","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50127","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50128","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50129","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50130","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50131","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50132","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50133","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50134","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50135","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50136","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50137","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50138","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50139","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50140","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50141","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50142","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50143","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50144","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50145","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50146","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50147","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50148","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50149","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50150","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50151","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50152","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50153","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50154","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50155","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50156","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50157","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50158","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50159","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50160","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50161","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50162","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50163","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50164","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50165","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50166","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50167","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50168","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50169","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50170","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50171","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50172","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50173","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50174","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50176","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50177","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50178","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50179","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50180","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50181","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50182","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50183","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50184","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50185","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50186","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50187","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50188","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50189","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50190","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50191","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50192","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50193","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50194","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50195","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50196","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50197","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50198","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50199","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50200","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50201","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50202","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50203","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50204","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50205","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50206","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50207","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50208","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50209","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50211","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50212","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50213","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50214","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50215","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50216","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50217","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50218","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50220","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50221","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50222","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50223","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50224","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50225","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50226","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50227","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50229","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50230","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50231","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50232","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50233","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50234","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50235","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50236","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50237","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50238","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50239","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50240","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50242","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50243","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50244","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50245","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50246","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50247","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50248","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50250","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50251","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50252","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50253","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50254","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50255","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50256","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50257","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50258","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50259","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50260","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50261","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50262","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50263","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50265","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50266","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50267","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50268","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50269","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50270","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50271","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50272","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50273","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50274","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50275","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50276","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50277","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50278","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50279","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50280","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50281","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50282","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50283","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50284","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50285","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50286","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50287","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50288","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50289","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50290","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50291","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50292","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50293","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50294","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50295","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50296","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50297","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50298","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50299","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50300","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50301","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50302","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50303","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50304","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-53042","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-53043","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-53044","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-53045","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-53046","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-53047","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-53048","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-53049","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-53052","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-53053","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-53055","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-53056","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-53058","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-53059","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-53061","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-53062","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-53063","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-53064","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-53065","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-53066","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-53067","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-53068","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-53069","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-53071","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-53072","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-53074","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-53075","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-53076","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-53077","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-53078","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-53079","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-53080","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-53081","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-53082","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-53083","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-53084","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-53085","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-53086","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-53087","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-53088","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-53089","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-53090","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-53091","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-53092","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-53093","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-53094","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-53095","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-53098","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-53099","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-53100","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-53101","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-53104","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-53105","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-53106","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-53107","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-53108","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-53109","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-53110","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-53111","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-53112","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-53113","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-53114","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-53115","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-53116","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-53117","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-53118","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-53119","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-53120","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-53121","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-53122","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-53123","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-53124","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-53125","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-53126","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-53127","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-53128","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-53129","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-53130","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-53131","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-53132","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-53133","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-53134","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-53135","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-53137","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-53138","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-53139","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-53140","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-53141","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-53142","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-53143","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-53144","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-53145","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-53146","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-53147","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-53148","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-53149","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-53150","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-53151","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-53152","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-53153","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-53154","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-53155","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-53156","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-53157","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-53158","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-53160","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-53161","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-53162","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-53163","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-53165","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-53166","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-53167","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-53168","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-53169","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-53170","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-53171","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-53172","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-53173","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-53174","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-53175","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-53176","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-53177","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-53178","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-53180","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-53181","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-53183","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-53184","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-53187","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-53188","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-53189","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-53190","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-53191","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-53192","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-53193","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-53194","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-53195","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-53196","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-53197","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-53198","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-53199","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-53200","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-53201","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-53202","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-53203","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-53208","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-53209","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-53210","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-53212","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-53213","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-53214","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-53215","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-53216","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-53217","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-53218","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-53219","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-53220","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-53221","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-53223","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-53224","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-53226","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-53227","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-53228","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-53229","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-53230","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-53231","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-53233","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-53234","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-53236","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-53237","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-53239","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56531","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56532","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56533","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56534","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56535","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56536","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56537","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56538","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56539","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56540","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56541","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56542","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56543","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56544","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56545","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56546","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56548","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56549","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56674","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56677","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56678","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56679","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56680","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56681","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56683","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56684","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56685","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56687","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56688","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56689","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56690","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56691","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56692","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56693","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56694","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56696","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56697","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56698","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56699","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56700","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56701","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56702","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56703","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56704","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56705","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56707","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56708","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56720","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56721","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56722","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56723","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56724","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56725","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56726","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56727","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56728","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56729","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56739","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56741","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56742","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56744","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56745","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56746","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56747","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56748","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56749","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56751","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56752","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56754","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56755","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56756","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-0927","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-41014","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-41932","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-41935","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-42122","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-43098","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-44955","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-45828","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-47141","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-47143","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-47794","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-47809","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-48873","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-48875","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-48876","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-48881","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-49569","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-49899","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-49906","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50051","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50210","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50249","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-52332","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-53050","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-53051","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-53060","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-53096","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-53185","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-53222","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-53680","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56550","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56551","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56557","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56558","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56561","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56562","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56565","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56566","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56567","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56568","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56569","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56570","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56572","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56573","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56574","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56575","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56576","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56577","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56578","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56579","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56580","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56581","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56583","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56584","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56586","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56587","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56588","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56589","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56590","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56592","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56593","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56594","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56596","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56597","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56599","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56600","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56601","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56602","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56603","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56604","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56605","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56606","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56607","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56608","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56609","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56610","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56611","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56613","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56615","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56616","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56619","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56620","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56621","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56622","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56623","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56625","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56626","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56627","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56629","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56630","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56631","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56632","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56633","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56634","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56635","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56636","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56637","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56638","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56640","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56641","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56642","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56643","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56644","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56645","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56647","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56648","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56649","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56650","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56651","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56765","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56771","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56772","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56773","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56774","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56775","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56776","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56777","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56778","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56779","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56780","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56781","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56782","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56783","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56785","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56786","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56787","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-57838","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-57843","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-57849","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-57850","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-57872","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-57874","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-57876","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-21700","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-21701","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-21702","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-21756","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-21831","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-21993","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-49893","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-49914","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-49920","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-49921","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50032","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56582","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56595","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56598","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56614","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56658","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56663","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56672","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-57798","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-8805","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-41016","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-47670","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-47672","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-47673","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-47704","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-49896","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-49898","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-49905","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-49907","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-49909","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-49911","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-49912","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-49913","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-49915","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-49917","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-49918","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-49919","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-49922","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-49923","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-53103","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-53164","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-2312","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-36476","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-38608","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-39282","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-41013","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-47408","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-49568","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-49571","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-53179","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-53685","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-53687","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-53690","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-54193","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-54455","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-54460","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-54683","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-55639","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-55881","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-55916","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56369","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56372","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56652","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56653","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56654","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56656","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56657","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56659","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56660","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56662","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56664","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56667","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56670","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56675","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56709","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56710","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56715","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56716","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56717","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56718","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56758","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56759","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56760","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56761","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56763","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56764","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56767","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56769","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56770","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-57791","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-57792","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-57793","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-57801","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-57802","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-57804","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-57806","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-57807","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-57841","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-57879","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-57882","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-57883","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-57884","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-57885","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-57887","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-57888","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-57889","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-57890","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-57892","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-57893","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-57895","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-57896","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-57897","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-57898","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-57899","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-57900","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-57901","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-57902","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-57903","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-57904","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-57906","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-57907","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-57908","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-57910","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-57911","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-57912","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-57913","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-57916","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-57917","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-57925","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-57926","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-57929","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-57931","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-57932","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-57933","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-57938","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-57939","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-57940","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-57945","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-57946","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-58087","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-58099","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-58237","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-21631","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-21632","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-21634","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-21635","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-21636","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-21637","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-21638","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-21639","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-21640","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-21642","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-21643","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-21645","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-21646","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-21647","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-21648","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-21649","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-21650","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-21651","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-21652","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-21653","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-21654","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-21655","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-21656","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-21658","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-21659","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-21660","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-21662","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-21663","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-21664","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-21938","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-21971","tags":["report"]}],"sources":{"cve":[{"id":"CVE-2024-53232","title":"iommu/s390: Implement blocking domain","description":"In the Linux kernel, the following vulnerability has been resolved:\n\niommu/s390: Implement blocking domain\n\nThis fixes a crash when surprise hot-unplugging a PCI device. This crash\nhappens because during hot-unplug __iommu_group_set_domain_nofail()\nattaching the default domain fails when the platform no longer\nrecognizes the device as it has already been removed and we end up with\na NULL domain pointer and UAF. This is exactly the case referred to in\nthe second comment in __iommu_device_set_domain() and just as stated\nthere if we can instead attach the blocking domain the UAF is prevented\nas this can handle the already removed device. Implement the blocking\ndomain to use this handling.  With this change, the crash is fixed but\nwe still hit a warning attempting to change DMA ownership on a blocked\ndevice.","status":"published","published":"2024-12-27T13:50:19.551Z","modified":"2026-08-05T11:44:46.669Z","cvss":[{"version":"3.1","score":7.8,"vector":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H","level":"high","assessor":"cna"},{"version":"3.1","score":7.8,"vector":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H","level":"high","assessor":"adp"}],"cwes":["CWE-416"],"updated_at":"2026-11-02T14:34:17.865042Z"}],"euvd":[{"id":"EUVD-2024-51904","description":"In the Linux kernel, the following vulnerability has been resolved:\n\niommu/s390: Implement blocking domain\n\nThis fixes a crash when surprise hot-unplugging a PCI device. This crash\nhappens because during hot-unplug __iommu_group_set_domain_nofail()\nattaching the default domain fails when the platform no longer\nrecognizes the device as it has already been removed and we end up with\na NULL domain pointer and UAF. This is exactly the case referred to in\nthe second comment in __iommu_device_set_domain() and just as stated\nthere if we can instead attach the blocking domain the UAF is prevented\nas this can handle the already removed device. Implement the blocking\ndomain to use this handling.  With this change, the crash is fixed but\nwe still hit a warning attempting to change DMA ownership on a blocked\ndevice.","status":"published","published":"2024-12-27T13:50:19Z","modified":"2026-08-05T11:44:46Z","cvss":[{"version":"3.1","score":7.8,"vector":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H","level":"high"}],"updated_at":"2026-11-02T18:02:14.928856Z"}],"ghsa":[{"id":"GHSA-c86m-78v8-4hvw","title":"In the Linux kernel, the following vulnerability has been resolved:\n\niommu/s390: Implement...","description":"In the Linux kernel, the following vulnerability has been resolved:\n\niommu/s390: Implement blocking domain\n\nThis fixes a crash when surprise hot-unplugging a PCI device. This crash\nhappens because during hot-unplug __iommu_group_set_domain_nofail()\nattaching the default domain fails when the platform no longer\nrecognizes the device as it has already been removed and we end up with\na NULL domain pointer and UAF. This is exactly the case referred to in\nthe second comment in __iommu_device_set_domain() and just as stated\nthere if we can instead attach the blocking domain the UAF is prevented\nas this can handle the already removed device. Implement the blocking\ndomain to use this handling.  With this change, the crash is fixed but\nwe still hit a warning attempting to change DMA ownership on a blocked\ndevice.","status":"published","published":"2024-12-27T15:31:52Z","modified":"2025-02-03T15:33:02Z","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-416"],"updated_at":"2026-11-02T14:59:45.515027Z"}],"nvd":[{"id":"CVE-2024-53232","description":"In the Linux kernel, the following vulnerability has been resolved:\n\niommu/s390: Implement blocking domain\n\nThis fixes a crash when surprise hot-unplugging a PCI device. This crash\nhappens because during hot-unplug __iommu_group_set_domain_nofail()\nattaching the default domain fails when the platform no longer\nrecognizes the device as it has already been removed and we end up with\na NULL domain pointer and UAF. This is exactly the case referred to in\nthe second comment in __iommu_device_set_domain() and just as stated\nthere if we can instead attach the blocking domain the UAF is prevented\nas this can handle the already removed device. Implement the blocking\ndomain to use this handling.  With this change, the crash is fixed but\nwe still hit a warning attempting to change DMA ownership on a blocked\ndevice.","status":"published","published":"2024-12-27T14:15:31.51Z","modified":"2026-06-17T08:08:39.56Z","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"},{"version":"3.1","score":7.8,"vector":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H","level":"high","assessor":"secondary"}],"cwes":["CWE-416","CWE-476"],"updated_at":"2026-11-02T14:10:41.091507Z"}],"osv":[{"id":"BELL-CVE-2024-53232","status":"published","published":"2025-01-01T05:58:29.502723Z","modified":"2026-06-25T07:16:12.329736477Z","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.963569Z"},{"id":"CVE-2024-53232","title":"iommu/s390: Implement blocking domain","description":"In the Linux kernel, the following vulnerability has been resolved:\n\niommu/s390: Implement blocking domain\n\nThis fixes a crash when surprise hot-unplugging a PCI device. This crash\nhappens because during hot-unplug __iommu_group_set_domain_nofail()\nattaching the default domain fails when the platform no longer\nrecognizes the device as it has already been removed and we end up with\na NULL domain pointer and UAF. This is exactly the case referred to in\nthe second comment in __iommu_device_set_domain() and just as stated\nthere if we can instead attach the blocking domain the UAF is prevented\nas this can handle the already removed device. Implement the blocking\ndomain to use this handling.  With this change, the crash is fixed but\nwe still hit a warning attempting to change DMA ownership on a blocked\ndevice.","status":"published","published":"2024-12-27T13:50:19.551Z","modified":"2026-10-28T02:31:03.178154215Z","cvss":[{"version":"3.1","score":7.8,"vector":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H","level":"high"}],"updated_at":"2026-11-02T15:44:44.451316Z"},{"id":"DEBIAN-CVE-2024-53232","description":"In the Linux kernel, the following vulnerability has been resolved:  iommu/s390: Implement blocking domain  This fixes a crash when surprise hot-unplugging a PCI device. This crash happens because during hot-unplug __iommu_group_set_domain_nofail() attaching the default domain fails when the platform no longer recognizes the device as it has already been removed and we end up with a NULL domain pointer and UAF. This is exactly the case referred to in the second comment in __iommu_device_set_domain() and just as stated there if we can instead attach the blocking domain the UAF is prevented as this can handle the already removed device. Implement the blocking domain to use this handling.  With this change, the crash is fixed but we still hit a warning attempting to change DMA ownership on a blocked device.","status":"published","published":"2024-12-27T14:15:31.51Z","modified":"2026-11-02T12:03:14.982771484Z","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:44.117337Z"},{"id":"OESA-2026-1759","title":"kernel security update","description":"The Linux Kernel, the operating system core itself.\r\n\r\nSecurity Fix(es):\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\niommu/s390: Implement blocking domain\n\nThis fixes a crash when surprise hot-unplugging a PCI device. This crash\nhappens because during hot-unplug __iommu_group_set_domain_nofail()\nattaching the default domain fails when the platform no longer\nrecognizes the device as it has already been removed and we end up with\na NULL domain pointer and UAF. This is exactly the case referred to in\nthe second comment in __iommu_device_set_domain() and just as stated\nthere if we can instead attach the blocking domain the UAF is prevented\nas this can handle the already removed device. Implement the blocking\ndomain to use this handling.  With this change, the crash is fixed but\nwe still hit a warning attempting to change DMA ownership on a blocked\ndevice.(CVE-2024-53232)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\niommu: Fix two issues in iommu_copy_struct_from_user()\n\nIn the review for iommu_copy_struct_to_user() helper, Matt pointed out that\na NULL pointer should be rejected prior to dereferencing it:\nhttps://lore.kernel.org/all/(CVE-2025-37900)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nsmb: client: Avoid race in open_cached_dir with lease breaks\n\nA pre-existing valid cfid returned from find_or_create_cached_dir might\nrace with a lease break, meaning open_cached_dir doesn\u0026apos;t consider it\nvalid, and thinks it\u0026apos;s newly-constructed. This leaks a dentry reference\nif the allocation occurs before the queued lease break work runs.\n\nAvoid the race by extending holding the cfid_list_lock across\nfind_or_create_cached_dir and when the result is checked.(CVE-2025-37954)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnet_sched: prio: fix a race in prio_tune()\n\nGerrard Tai reported a race condition in PRIO, whenever SFQ perturb timer\nfires at the wrong time.\n\nThe race is as follows:\n\nCPU 0                                 CPU 1\n[1]: lock root\n[2]: qdisc_tree_flush_backlog()\n[3]: unlock root\n |\n |                                    [5]: lock root\n |                                    [6]: rehash\n |                                    [7]: qdisc_tree_reduce_backlog()\n |\n[4]: qdisc_put()\n\nThis can be abused to underflow a parent\u0026apos;s qlen.\n\nCalling qdisc_purge_queue() instead of qdisc_tree_flush_backlog()\nshould fix the race, because all packets will be purged from the qdisc\nbefore releasing the lock.(CVE-2025-38083)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nIB/mlx5: Fix potential deadlock in MR deregistration\n\nThe issue arises when kzalloc() is invoked while holding umem_mutex or\nany other lock acquired under umem_mutex. This is problematic because\nkzalloc() can trigger fs_reclaim_aqcuire(), which may, in turn, invoke\nmmu_notifier_invalidate_range_start(). This function can lead to\nmlx5_ib_invalidate_range(), which attempts to acquire umem_mutex again,\nresulting in a deadlock.\n\nThe problematic flow:\n             CPU0                      |              CPU1\n---------------------------------------|------------------------------------------------\nmlx5_ib_dereg_mr()                     |\n → revoke_mr()                         |\n   → mutex_lock(\u0026amp;umem_odp-\u0026gt;umem_mutex) |\n                                       | mlx5_mkey_cache_init()\n                                       |  → mutex_lock(\u0026amp;dev-\u0026gt;cache.rb_lock)\n                                       |  → mlx5r_cache_create_ent_locked()\n                                       |    → kzalloc(GFP_KERNEL)\n                                       |      → fs_reclaim()\n                                       |        → mmu_notifier_invalidate_range_start()\n                                       |          → mlx5_ib_invalidate_range()\n                                       |            → mutex_lock(\u0026amp;umem_odp-\u0026gt;umem_mutex)\n   → cache_ent_find_and_store()        |\n     → mutex_lock(\u0026amp;dev-\u0026gt;cache.rb_lock) |\n\nAdditionally, when kzalloc() is called from within\ncache_ent_find_and_store(), we encounter the same deadlock due to\nre-acquisition of umem_mutex.\n\nSolve by releasing umem_mutex in dereg_mr() after umr_revoke_mr()\nand before acquiring rb_lock. This ensures that we don\u0026apos;t hold\numem_mutex while performing memory allocations that could trigger\nthe reclaim path.\n\nThis change prevents the deadlock by ensuring proper lock ordering and\navoiding holding locks during memory allocation operations that could\ntrigger the reclaim path.\n\nThe following lockdep warning demonstrates the deadlock:\n\n python3/20557 is trying to acquire lock:\n ffff888387542128 (\u0026amp;umem_odp-\u0026gt;umem_mutex){+.+.}-{4:4}, at:\n mlx5_ib_invalidate_range+0x5b/0x550 [mlx5_ib]\n\n but task is already holding lock:\n ffffffff82f6b840 (mmu_notifier_invalidate_range_start){+.+.}-{0:0}, at:\n unmap_vmas+0x7b/0x1a0\n\n which lock already depends on the new lock.\n\n the existing dependency chain (in reverse order) is:\n\n -\u0026gt; #3 (mmu_notifier_invalidate_range_start){+.+.}-{0:0}:\n       fs_reclaim_acquire+0x60/0xd0\n       mem_cgroup_css_alloc+0x6f/0x9b0\n       cgroup_init_subsys+0xa4/0x240\n       cgroup_init+0x1c8/0x510\n       start_kernel+0x747/0x760\n       x86_64_start_reservations+0x25/0x30\n       x86_64_start_kernel+0x73/0x80\n       common_startup_64+0x129/0x138\n\n -\u0026gt; #2 (fs_reclaim){+.+.}-{0:0}:\n       fs_reclaim_acquire+0x91/0xd0\n       __kmalloc_cache_noprof+0x4d/0x4c0\n       mlx5r_cache_create_ent_locked+0x75/0x620 [mlx5_ib]\n       mlx5_mkey_cache_init+0x186/0x360 [mlx5_ib]\n       mlx5_ib_stage_post_ib_reg_umr_init+0x3c/0x60 [mlx5_ib]\n       __mlx5_ib_add+0x4b/0x190 [mlx5_ib]\n       mlx5r_probe+0xd9/0x320 [mlx5_ib]\n       auxiliary_bus_probe+0x42/0x70\n       really_probe+0xdb/0x360\n       __driver_probe_device+0x8f/0x130\n       driver_probe_device+0x1f/0xb0\n       __driver_attach+0xd4/0x1f0\n       bus_for_each_dev+0x79/0xd0\n       bus_add_driver+0xf0/0x200\n       driver_register+0x6e/0xc0\n       __auxiliary_driver_register+0x6a/0xc0\n       do_one_initcall+0x5e/0x390\n       do_init_module+0x88/0x240\n       init_module_from_file+0x85/0xc0\n       idempotent_init_module+0x104/0x300\n       __x64_sys_finit_module+0x68/0xc0\n       do_syscall_64+0x6d/0x140\n       entry_SYSCALL_64_after_hwframe+0x4b/0x53\n\n -\u0026gt; #1 (\u0026amp;dev-\u0026gt;cache.rb_lock){+.+.}-{4:4}:\n       __mutex_lock+0x98/0xf10\n       __mlx5_ib_dereg_mr+0x6f2/0x890 [mlx5_ib]\n       mlx5_ib_dereg_mr+0x21/0x110 [mlx5_ib]\n       ib_dereg_mr_user+0x85/0x1f0 [ib_core]\n  \n---truncated---(CVE-2025-38373)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nHID: core: Harden s32ton() against conversion to 0 bits\n\nTesting by the syzbot fuzzer showed that the HID core gets a\nshift-out-of-bounds exception when it tries to convert a 32-bit\nquantity to a 0-bit quantity.  Ideally this should never occur, but\nthere are buggy devices and some might have a report field with size\nset to zero; we shouldn\u0026apos;t reject the report or the device just because\nof that.\n\nInstead, harden the s32ton() routine so that it returns a reasonable\nresult instead of crashing when it is called with the number of bits\nset to 0 -- the same as what snto32() does.(CVE-2025-38556)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nbpf: Reject narrower access to pointer ctx fields\n\nThe following BPF program, simplified from a syzkaller repro, causes a\nkernel warning:\n\n    r0 = *(u8 *)(r1 + 169);\n    exit;\n\nWith pointer field sk being at offset 168 in __sk_buff. This access is\ndetected as a narrower read in bpf_skb_is_valid_access because it\ndoesn\u0026apos;t match offsetof(struct __sk_buff, sk). It is therefore allowed\nand later proceeds to bpf_convert_ctx_access. Note that for the\n\u0026quot;is_narrower_load\u0026quot; case in the convert_ctx_accesses(), the insn-\u0026gt;off\nis aligned, so the cnt may not be 0 because it matches the\noffsetof(struct __sk_buff, sk) in the bpf_convert_ctx_access. However,\nthe target_size stays 0 and the verifier errors with a kernel warning:\n\n    verifier bug: error during ctx access conversion(1)\n\nThis patch fixes that to return a proper \u0026quot;invalid bpf_context access\noff=X size=Y\u0026quot; error on the load instruction.\n\nThe same issue affects multiple other fields in context structures that\nallow narrow access. Some other non-affected fields (for sk_msg,\nsk_lookup, and sockopt) were also changed to use bpf_ctx_range_ptr for\nconsistency.\n\nNote this syzkaller crash was reported in the \u0026quot;Closes\u0026quot; link below, which\nused to be about a different bug, fixed in\ncommit fce7bd8e385a (\u0026quot;bpf/verifier: Handle BPF_LOAD_ACQ instructions\nin insn_def_regno()\u0026quot;). Because syzbot somehow confused the two bugs,\nthe new crash and repro didn\u0026apos;t get reported to the mailing list.(CVE-2025-38591)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ngfs2: No more self recovery\n\nWhen a node withdraws and it turns out that it is the only node that has\nthe filesystem mounted, gfs2 currently tries to replay the local journal\nto bring the filesystem back into a consistent state.  Not only is that\na very bad idea, it has also never worked because gfs2_recover_func()\nwill refuse to do anything during a withdraw.\n\nHowever, before even getting to this point, gfs2_recover_func()\ndereferences sdp-\u0026gt;sd_jdesc-\u0026gt;jd_inode.  This was a use-after-free before\ncommit 04133b607a78 (\u0026quot;gfs2: Prevent double iput for journal on error\u0026quot;)\nand is a NULL pointer dereference since then.\n\nSimply get rid of self recovery to fix that.(CVE-2025-38659)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nio_uring/net: commit partial buffers on retry\n\nRing provided buffers are potentially only valid within the single\nexecution context in which they were acquired. io_uring deals with this\nand invalidates them on retry. But on the networking side, if\nMSG_WAITALL is set, or if the socket is of the streaming type and too\nlittle was processed, then it will hang on to the buffer rather than\nrecycle or commit it. This is problematic for two reasons:\n\n1) If someone unregisters the provided buffer ring before a later retry,\n   then the req-\u0026gt;buf_list will no longer be valid.\n\n2) If multiple sockers are using the same buffer group, then multiple\n   receives can consume the same memory. This can cause data corruption\n   in the application, as either receive could land in the same\n   userspace buffer.\n\nFix this by disallowing partial retries from pinning a provided buffer\nacross multiple executions, if ring provided buffers are used.(CVE-2025-38730)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nmedia: rainshadow-cec: fix TOCTOU race condition in rain_interrupt()\n\nIn the interrupt handler rain_interrupt(), the buffer full check on\nrain-\u0026gt;buf_len is performed before acquiring rain-\u0026gt;buf_lock. This\ncreates a Time-of-Check to Time-of-Use (TOCTOU) race condition, as\nrain-\u0026gt;buf_len is concurrently accessed and modified in the work\nhandler rain_irq_work_handler() under the same lock.\n\nMultiple interrupt invocations can race, with each reading buf_len\nbefore it becomes full and then proceeding. This can lead to both\ninterrupts attempting to write to the buffer, incrementing buf_len\nbeyond its capacity (DATA_SIZE) and causing a buffer overflow.\n\nFix this bug by moving the spin_lock() to before the buffer full\ncheck. This ensures that the check and the subsequent buffer modification\nare performed atomically, preventing the race condition. An corresponding\nspin_unlock() is added to the overflow path to correctly release the\nlock.\n\nThis possible bug was found by an experimental static analysis tool\ndeveloped by our team.(CVE-2025-39713)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\niommu/amd/pgtbl: Fix possible race while increase page table level\n\nThe AMD IOMMU host page table implementation supports dynamic page table levels\n(up to 6 levels), starting with a 3-level configuration that expands based on\nIOVA address. The kernel maintains a root pointer and current page table level\nto enable proper page table walks in alloc_pte()/fetch_pte() operations.\n\nThe IOMMU IOVA allocator initially starts with 32-bit address and onces its\nexhuasted it switches to 64-bit address (max address is determined based\non IOMMU and device DMA capability). To support larger IOVA, AMD IOMMU\ndriver increases page table level.\n\nBut in unmap path (iommu_v1_unmap_pages()), fetch_pte() reads\npgtable-\u0026gt;[root/mode] without lock. So its possible that in exteme corner case,\nwhen increase_address_space() is updating pgtable-\u0026gt;[root/mode], fetch_pte()\nreads wrong page table level (pgtable-\u0026gt;mode). It does compare the value with\nlevel encoded in page table and returns NULL. This will result is\niommu_unmap ops to fail and upper layer may retry/log WARN_ON.\n\nCPU 0                                         CPU 1\n------                                       ------\nmap pages                                    unmap pages\nalloc_pte() -\u0026gt; increase_address_space()      iommu_v1_unmap_pages() -\u0026gt; fetch_pte()\n  pgtable-\u0026gt;root = pte (new root value)\n                                             READ pgtable-\u0026gt;[mode/root]\n\t\t\t\t\t       Reads new root, old mode\n  Updates mode (pgtable-\u0026gt;mode += 1)\n\nSince Page table level updates are infrequent and already synchronized with a\nspinlock, implement seqcount to enable lock-free read operations on the read path.(CVE-2025-39961)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\npinctrl: check the return value of pinmux_ops::get_function_name()\n\nWhile the API contract in docs doesn\u0026apos;t specify it explicitly, the\ngeneric implementation of the get_function_name() callback from struct\npinmux_ops - pinmux_generic_get_function_name() - can fail and return\nNULL. This is already checked in pinmux_check_ops() so add a similar\ncheck in pinmux_func_name_to_selector() instead of passing the returned\npointer right down to strcmp() where the NULL can get dereferenced. This\nis normal operation when adding new pinfunctions.(CVE-2025-40030)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ndrm/sched: Fix potential double free in drm_sched_job_add_resv_dependencies\n\nWhen adding dependencies with drm_sched_job_add_dependency(), that\nfunction consumes the fence reference both on success and failure, so in\nthe latter case the dma_fence_put() on the error path (xarray failed to\nexpand) is a double free.\n\nInterestingly this bug appears to have been present ever since\ncommit ebd5f74255b9 (\u0026quot;drm/sched: Add dependency tracking\u0026quot;), since the code\nback then looked like this:\n\ndrm_sched_job_add_implicit_dependencies():\n...\n       for (i = 0; i \u0026lt; fence_count; i++) {\n               ret = drm_sched_job_add_dependency(job, fences[i]);\n               if (ret)\n                       break;\n       }\n\n       for (; i \u0026lt; fence_count; i++)\n               dma_fence_put(fences[i]);\n\nWhich means for the failing \u0026apos;i\u0026apos; the dma_fence_put was already a double\nfree. Possibly there were no users at that time, or the test cases were\ninsufficient to hit it.\n\nThe bug was then only noticed and fixed after\ncommit 9c2ba265352a (\u0026quot;drm/scheduler: use new iterator in drm_sched_job_add_implicit_dependencies v2\u0026quot;)\nlanded, with its fixup of\ncommit 4eaf02d6076c (\u0026quot;drm/scheduler: fix drm_sched_job_add_implicit_dependencies\u0026quot;).\n\nAt that point it was a slightly different flavour of a double free, which\ncommit 963d0b356935 (\u0026quot;drm/scheduler: fix drm_sched_job_add_implicit_dependencies harder\u0026quot;)\nnoticed and attempted to fix.\n\nBut it only moved the double free from happening inside the\ndrm_sched_job_add_dependency(), when releasing the reference not yet\nobtained, to the caller, when releasing the reference already released by\nthe former in the failure case.\n\nAs such it is not easy to identify the right target for the fixes tag so\nlets keep it simple and just continue the chain.\n\nWhile fixing we also improve the comment and explain the reason for taking\nthe reference and not dropping it.(CVE-2025-40096)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nxfrm: delete x-\u0026gt;tunnel as we delete x\n\nThe ipcomp fallback tunnels currently get deleted (from the various\nlists and hashtables) as the last user state that needed that fallback\nis destroyed (not deleted). If a reference to that user state still\nexists, the fallback state will remain on the hashtables/lists,\ntriggering the WARN in xfrm_state_fini. Because of those remaining\nreferences, the fix in commit f75a2804da39 (\u0026quot;xfrm: destroy xfrm_state\nsynchronously on net exit path\u0026quot;) is not complete.\n\nWe recently fixed one such situation in TCP due to defered freeing of\nskbs (commit 9b6412e6979f (\u0026quot;tcp: drop secpath at the same time as we\ncurrently drop dst\u0026quot;)). This can also happen due to IP reassembly: skbs\nwith a secpath remain on the reassembly queue until netns\ndestruction. If we can\u0026apos;t guarantee that the queues are flushed by the\ntime xfrm_state_fini runs, there may still be references to a (user)\nxfrm_state, preventing the timely deletion of the corresponding\nfallback state.\n\nInstead of chasing each instance of skbs holding a secpath one by one,\nthis patch fixes the issue directly within xfrm, by deleting the\nfallback state as soon as the last user state depending on it has been\ndeleted. Destruction will still happen when the final reference is\ndropped.\n\nA separate lockdep class for the fallback state is required since\nwe\u0026apos;re going to lock x-\u0026gt;tunnel while x is locked.(CVE-2025-40215)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nfuse: fix livelock in synchronous file put from fuseblk workers\n\nI observed a hang when running generic/323 against a fuseblk server.\nThis test opens a file, initiates a lot of AIO writes to that file\ndescriptor, and closes the file descriptor before the writes complete.\nUnsurprisingly, the AIO exerciser threads are mostly stuck waiting for\nresponses from the fuseblk server:\n\n# cat /proc/372265/task/372313/stack\n[\u0026lt;0\u0026gt;] request_wait_answer+0x1fe/0x2a0 [fuse]\n[\u0026lt;0\u0026gt;] __fuse_simple_request+0xd3/0x2b0 [fuse]\n[\u0026lt;0\u0026gt;] fuse_do_getattr+0xfc/0x1f0 [fuse]\n[\u0026lt;0\u0026gt;] fuse_file_read_iter+0xbe/0x1c0 [fuse]\n[\u0026lt;0\u0026gt;] aio_read+0x130/0x1e0\n[\u0026lt;0\u0026gt;] io_submit_one+0x542/0x860\n[\u0026lt;0\u0026gt;] __x64_sys_io_submit+0x98/0x1a0\n[\u0026lt;0\u0026gt;] do_syscall_64+0x37/0xf0\n[\u0026lt;0\u0026gt;] entry_SYSCALL_64_after_hwframe+0x4b/0x53\n\nBut the /weird/ part is that the fuseblk server threads are waiting for\nresponses from itself:\n\n# cat /proc/372210/task/372232/stack\n[\u0026lt;0\u0026gt;] request_wait_answer+0x1fe/0x2a0 [fuse]\n[\u0026lt;0\u0026gt;] __fuse_simple_request+0xd3/0x2b0 [fuse]\n[\u0026lt;0\u0026gt;] fuse_file_put+0x9a/0xd0 [fuse]\n[\u0026lt;0\u0026gt;] fuse_release+0x36/0x50 [fuse]\n[\u0026lt;0\u0026gt;] __fput+0xec/0x2b0\n[\u0026lt;0\u0026gt;] task_work_run+0x55/0x90\n[\u0026lt;0\u0026gt;] syscall_exit_to_user_mode+0xe9/0x100\n[\u0026lt;0\u0026gt;] do_syscall_64+0x43/0xf0\n[\u0026lt;0\u0026gt;] entry_SYSCALL_64_after_hwframe+0x4b/0x53\n\nThe fuseblk server is fuse2fs so there\u0026apos;s nothing all that exciting in\nthe server itself.  So why is the fuse server calling fuse_file_put?\nThe commit message for the fstest sheds some light on that:\n\n\u0026quot;By closing the file descriptor before calling io_destroy, you pretty\nmuch guarantee that the last put on the ioctx will be done in interrupt\ncontext (during I/O completion).\n\nAha.  AIO fgets a new struct file from the fd when it queues the ioctx.\nThe completion of the FUSE_WRITE command from userspace causes the fuse\nserver to call the AIO completion function.  The completion puts the\nstruct file, queuing a delayed fput to the fuse server task.  When the\nfuse server task returns to userspace, it has to run the delayed fput,\nwhich in the case of a fuseblk server, it does synchronously.\n\nSending the FUSE_RELEASE command sychronously from fuse server threads\nis a bad idea because a client program can initiate enough simultaneous\nAIOs such that all the fuse server threads end up in delayed_fput, and\nnow there aren\u0026apos;t any threads left to handle the queued fuse commands.\n\nFix this by only using asynchronous fputs when closing files, and leave\na comment explaining why.(CVE-2025-40220)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nfs/notify: call exportfs_encode_fid with s_umount\n\nCalling intotify_show_fdinfo() on fd watching an overlayfs inode, while\nthe overlayfs is being unmounted, can lead to dereferencing NULL ptr.\n\nThis issue was found by syzkaller.\n\nRace Condition Diagram:\n\nThread 1                           Thread 2\n--------                           --------\n\ngeneric_shutdown_super()\n shrink_dcache_for_umount\n  sb-\u0026gt;s_root = NULL\n\n                    |\n                    |             vfs_read()\n                    |              inotify_fdinfo()\n                    |               * inode get from mark *\n                    |               show_mark_fhandle(m, inode)\n                    |                exportfs_encode_fid(inode, ..)\n                    |                 ovl_encode_fh(inode, ..)\n                    |                  ovl_check_encode_origin(inode)\n                    |                   * deref i_sb-\u0026gt;s_root *\n                    |\n                    |\n                    v\n fsnotify_sb_delete(sb)\n\nWhich then leads to:\n\n[   32.133461] Oops: general protection fault, probably for non-canonical address 0xdffffc0000000006: 0000 [#1] SMP DEBUG_PAGEALLOC KASAN NOPTI\n[   32.134438] KASAN: null-ptr-deref in range [0x0000000000000030-0x0000000000000037]\n[   32.135032] CPU: 1 UID: 0 PID: 4468 Comm: systemd-coredum Not tainted 6.17.0-rc6 #22 PREEMPT(none)\n\n\u0026lt;snip registers, unreliable trace\u0026gt;\n\n[   32.143353] Call Trace:\n[   32.143732]  ovl_encode_fh+0xd5/0x170\n[   32.144031]  exportfs_encode_inode_fh+0x12f/0x300\n[   32.144425]  show_mark_fhandle+0xbe/0x1f0\n[   32.145805]  inotify_fdinfo+0x226/0x2d0\n[   32.146442]  inotify_show_fdinfo+0x1c5/0x350\n[   32.147168]  seq_show+0x530/0x6f0\n[   32.147449]  seq_read_iter+0x503/0x12a0\n[   32.148419]  seq_read+0x31f/0x410\n[   32.150714]  vfs_read+0x1f0/0x9e0\n[   32.152297]  ksys_read+0x125/0x240\n\nIOW ovl_check_encode_origin derefs inode-\u0026gt;i_sb-\u0026gt;s_root, after it was set\nto NULL in the unmount path.\n\nFix it by protecting calling exportfs_encode_fid() from\nshow_mark_fhandle() with s_umount lock.\n\nThis form of fix was suggested by Amir in [1].\n\n[1]: https://lore.kernel.org/all/CAOQ4uxhbDwhb+2Brs1UdkoF0a3NSdBAOQPNfEHjahrgoKJpLEw@mail.gmail.com/(CVE-2025-40237)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ngfs2: Fix unlikely race in gdlm_put_lock\n\nIn gdlm_put_lock(), there is a small window of time in which the\nDFL_UNMOUNT flag has been set but the lockspace hasn\u0026apos;t been released,\nyet.  In that window, dlm may still call gdlm_ast() and gdlm_bast().\nTo prevent it from dereferencing freed glock objects, only free the\nglock if the lockspace has actually been released.(CVE-2025-40242)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ndevlink: rate: Unset parent pointer in devl_rate_nodes_destroy\n\nThe function devl_rate_nodes_destroy is documented to \u0026quot;Unset parent for\nall rate objects\u0026quot;. However, it was only calling the driver-specific\n`rate_leaf_parent_set` or `rate_node_parent_set` ops and decrementing\nthe parent\u0026apos;s refcount, without actually setting the\n`devlink_rate-\u0026gt;parent` pointer to NULL.\n\nThis leaves a dangling pointer in the `devlink_rate` struct, which cause\nrefcount error in netdevsim[1] and mlx5[2]. In addition, this is\ninconsistent with the behavior of `devlink_nl_rate_parent_node_set`,\nwhere the parent pointer is correctly cleared.\n\nThis patch fixes the issue by explicitly setting `devlink_rate-\u0026gt;parent`\nto NULL after notifying the driver, thus fulfilling the function\u0026apos;s\ndocumented behavior for all rate objects.\n\n[1]\nrepro steps:\necho 1 \u0026gt; /sys/bus/netdevsim/new_device\ndevlink dev eswitch set netdevsim/netdevsim1 mode switchdev\necho 1 \u0026gt; /sys/bus/netdevsim/devices/netdevsim1/sriov_numvfs\ndevlink port function rate add netdevsim/netdevsim1/test_node\ndevlink port function rate set netdevsim/netdevsim1/128 parent test_node\necho 1 \u0026gt; /sys/bus/netdevsim/del_device\n\ndmesg:\nrefcount_t: decrement hit 0; leaking memory.\nWARNING: CPU: 8 PID: 1530 at lib/refcount.c:31 refcount_warn_saturate+0x42/0xe0\nCPU: 8 UID: 0 PID: 1530 Comm: bash Not tainted 6.18.0-rc4+ #1 NONE\nHardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS rel-1.16.0-0-gd239552ce722-prebuilt.qemu.org 04/01/2014\nRIP: 0010:refcount_warn_saturate+0x42/0xe0\nCall Trace:\n \u0026lt;TASK\u0026gt;\n devl_rate_leaf_destroy+0x8d/0x90\n __nsim_dev_port_del+0x6c/0x70 [netdevsim]\n nsim_dev_reload_destroy+0x11c/0x140 [netdevsim]\n nsim_drv_remove+0x2b/0xb0 [netdevsim]\n device_release_driver_internal+0x194/0x1f0\n bus_remove_device+0xc6/0x130\n device_del+0x159/0x3c0\n device_unregister+0x1a/0x60\n del_device_store+0x111/0x170 [netdevsim]\n kernfs_fop_write_iter+0x12e/0x1e0\n vfs_write+0x215/0x3d0\n ksys_write+0x5f/0xd0\n do_syscall_64+0x55/0x10f0\n entry_SYSCALL_64_after_hwframe+0x4b/0x53\n\n[2]\ndevlink dev eswitch set pci/0000:08:00.0 mode switchdev\ndevlink port add pci/0000:08:00.0 flavour pcisf pfnum 0 sfnum 1000\ndevlink port function rate add pci/0000:08:00.0/group1\ndevlink port function rate set pci/0000:08:00.0/32768 parent group1\nmodprobe -r mlx5_ib mlx5_fwctl mlx5_core\n\ndmesg:\nrefcount_t: decrement hit 0; leaking memory.\nWARNING: CPU: 7 PID: 16151 at lib/refcount.c:31 refcount_warn_saturate+0x42/0xe0\nCPU: 7 UID: 0 PID: 16151 Comm: bash Not tainted 6.17.0-rc7_for_upstream_min_debug_2025_10_02_12_44 #1 NONE\nHardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS rel-1.16.3-0-ga6ed6b701f0a-prebuilt.qemu.org 04/01/2014\nRIP: 0010:refcount_warn_saturate+0x42/0xe0\nCall Trace:\n \u0026lt;TASK\u0026gt;\n devl_rate_leaf_destroy+0x8d/0x90\n mlx5_esw_offloads_devlink_port_unregister+0x33/0x60 [mlx5_core]\n mlx5_esw_offloads_unload_rep+0x3f/0x50 [mlx5_core]\n mlx5_eswitch_unload_sf_vport+0x40/0x90 [mlx5_core]\n mlx5_sf_esw_event+0xc4/0x120 [mlx5_core]\n notifier_call_chain+0x33/0xa0\n blocking_notifier_call_chain+0x3b/0x50\n mlx5_eswitch_disable_locked+0x50/0x110 [mlx5_core]\n mlx5_eswitch_disable+0x63/0x90 [mlx5_core]\n mlx5_unload+0x1d/0x170 [mlx5_core]\n mlx5_uninit_one+0xa2/0x130 [mlx5_core]\n remove_one+0x78/0xd0 [mlx5_core]\n pci_device_remove+0x39/0xa0\n device_release_driver_internal+0x194/0x1f0\n unbind_store+0x99/0xa0\n kernfs_fop_write_iter+0x12e/0x1e0\n vfs_write+0x215/0x3d0\n ksys_write+0x5f/0xd0\n do_syscall_64+0x53/0x1f0\n entry_SYSCALL_64_after_hwframe+0x4b/0x53(CVE-2025-40251)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nfs/proc: fix uaf in proc_readdir_de()\n\nPde is erased from subdir rbtree through rb_erase(), but not set the node\nto EMPTY, which may result in uaf access.  We should use RB_CLEAR_NODE()\nset the erased node to EMPTY, then pde_subdir_next() will return NULL to\navoid uaf access.\n\nWe found an uaf issue while using stress-ng testing, need to run testcase\ngetdent and tun in the same time.  The steps of the issue is as follows:\n\n1) use getdent to traverse dir /proc/pid/net/dev_snmp6/, and current\n   pde is tun3;\n\n2) in the [time windows] unregister netdevice tun3 and tun2, and erase\n   them from rbtree.  erase tun3 first, and then erase tun2.  the\n   pde(tun2) will be released to slab;\n\n3) continue to getdent process, then pde_subdir_next() will return\n   pde(tun2) which is released, it will case uaf access.\n\nCPU 0                                      |    CPU 1\n-------------------------------------------------------------------------\ntraverse dir /proc/pid/net/dev_snmp6/      |   unregister_netdevice(tun-\u0026gt;dev)   //tun3 tun2\nsys_getdents64()                           |\n  iterate_dir()                            |\n    proc_readdir()                         |\n      proc_readdir_de()                    |     snmp6_unregister_dev()\n        pde_get(de);                       |       proc_remove()\n        read_unlock(\u0026amp;proc_subdir_lock);    |         remove_proc_subtree()\n                                           |           write_lock(\u0026amp;proc_subdir_lock);\n        [time window]                      |           rb_erase(\u0026amp;root-\u0026gt;subdir_node, \u0026amp;parent-\u0026gt;subdir);\n                                           |           write_unlock(\u0026amp;proc_subdir_lock);\n        read_lock(\u0026amp;proc_subdir_lock);      |\n        next = pde_subdir_next(de);        |\n        pde_put(de);                       |\n        de = next;    //UAF                |\n\nrbtree of dev_snmp6\n                        |\n                    pde(tun3)\n                     /    \\\n                  NULL  pde(tun2)(CVE-2025-40271)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nmm/secretmem: fix use-after-free race in fault handler\n\nWhen a page fault occurs in a secret memory file created with\n`memfd_secret(2)`, the kernel will allocate a new folio for it, mark the\nunderlying page as not-present in the direct map, and add it to the file\nmapping.\n\nIf two tasks cause a fault in the same page concurrently, both could end\nup allocating a folio and removing the page from the direct map, but only\none would succeed in adding the folio to the file mapping.  The task that\nfailed undoes the effects of its attempt by (a) freeing the folio again\nand (b) putting the page back into the direct map.  However, by doing\nthese two operations in this order, the page becomes available to the\nallocator again before it is placed back in the direct mapping.\n\nIf another task attempts to allocate the page between (a) and (b), and the\nkernel tries to access it via the direct map, it would result in a\nsupervisor not-present page fault.\n\nFix the ordering to restore the direct map before the folio is freed.(CVE-2025-40272)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ndrm/vmwgfx: Validate command header size against SVGA_CMD_MAX_DATASIZE\n\nThis data originates from userspace and is used in buffer offset\ncalculations which could potentially overflow causing an out-of-bounds\naccess.(CVE-2025-40277)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nBluetooth: MGMT: Fix OOB access in parse_adv_monitor_pattern()\n\nIn the parse_adv_monitor_pattern() function, the value of\nthe \u0026apos;length\u0026apos; variable is currently limited to HCI_MAX_EXT_AD_LENGTH(251).\nThe size of the \u0026apos;value\u0026apos; array in the mgmt_adv_pattern structure is 31.\nIf the value of \u0026apos;pattern[i].length\u0026apos; is set in the user space\nand exceeds 31, the \u0026apos;patterns[i].value\u0026apos; array can be accessed\nout of bound when copied.\n\nIncreasing the size of the \u0026apos;value\u0026apos; array in\nthe \u0026apos;mgmt_adv_pattern\u0026apos; structure will break the userspace.\nConsidering this, and to avoid OOB access revert the limits for \u0026apos;offset\u0026apos;\nand \u0026apos;length\u0026apos; back to the value of HCI_MAX_AD_LENGTH.\n\nFound by InfoTeCS on behalf of Linux Verification Center\n(linuxtesting.org) with SVACE.(CVE-2025-40294)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nBluetooth: hci_event: validate skb length for unknown CC opcode\n\nIn hci_cmd_complete_evt(), if the command complete event has an unknown\nopcode, we assume the first byte of the remaining skb-\u0026gt;data contains the\nreturn status. However, parameter data has previously been pulled in\nhci_event_func(), which may leave the skb empty. If so, using skb-\u0026gt;data[0]\nfor the return status uses un-init memory.\n\nThe fix is to check skb-\u0026gt;len before using skb-\u0026gt;data.(CVE-2025-40301)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nBluetooth: bcsp: receive data only if registered\n\nCurrently, bcsp_recv() can be called even when the BCSP protocol has not\nbeen registered. This leads to a NULL pointer dereference, as shown in\nthe following stack trace:\n\n    KASAN: null-ptr-deref in range [0x0000000000000108-0x000000000000010f]\n    RIP: 0010:bcsp_recv+0x13d/0x1740 drivers/bluetooth/hci_bcsp.c:590\n    Call Trace:\n     \u0026lt;TASK\u0026gt;\n     hci_uart_tty_receive+0x194/0x220 drivers/bluetooth/hci_ldisc.c:627\n     tiocsti+0x23c/0x2c0 drivers/tty/tty_io.c:2290\n     tty_ioctl+0x626/0xde0 drivers/tty/tty_io.c:2706\n     vfs_ioctl fs/ioctl.c:51 [inline]\n     __do_sys_ioctl fs/ioctl.c:907 [inline]\n     __se_sys_ioctl+0xfc/0x170 fs/ioctl.c:893\n     do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline]\n     do_syscall_64+0xfa/0x3b0 arch/x86/entry/syscall_64.c:94\n     entry_SYSCALL_64_after_hwframe+0x77/0x7f\n\nTo prevent this, ensure that the HCI_UART_REGISTERED flag is set before\nprocessing received data. If the protocol is not registered, return\n-EUNATCH.(CVE-2025-40308)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nBluetooth: hci_sync: fix race in hci_cmd_sync_dequeue_once\n\nhci_cmd_sync_dequeue_once() does lookup and then cancel\nthe entry under two separate lock sections. Meanwhile,\nhci_cmd_sync_work() can also delete the same entry,\nleading to double list_del() and \u0026quot;UAF\u0026quot;.\n\nFix this by holding cmd_sync_work_lock across both\nlookup and cancel, so that the entry cannot be removed\nconcurrently.(CVE-2025-40318)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nfutex: Don\u0026apos;t leak robust_list pointer on exec race\n\nsys_get_robust_list() and compat_get_robust_list() use ptrace_may_access()\nto check if the calling task is allowed to access another task\u0026apos;s\nrobust_list pointer. This check is racy against a concurrent exec() in the\ntarget process.\n\nDuring exec(), a task may transition from a non-privileged binary to a\nprivileged one (e.g., setuid binary) and its credentials/memory mappings\nmay change. If get_robust_list() performs ptrace_may_access() before\nthis transition, it may erroneously allow access to sensitive information\nafter the target becomes privileged.\n\nA racy access allows an attacker to exploit a window during which\nptrace_may_access() passes before a target process transitions to a\nprivileged state via exec().\n\nFor example, consider a non-privileged task T that is about to execute a\nsetuid-root binary. An attacker task A calls get_robust_list(T) while T\nis still unprivileged. Since ptrace_may_access() checks permissions\nbased on current credentials, it succeeds. However, if T begins exec\nimmediately afterwards, it becomes privileged and may change its memory\nmappings. Because get_robust_list() proceeds to access T-\u0026gt;robust_list\nwithout synchronizing with exec() it may read user-space pointers from a\nnow-privileged process.\n\nThis violates the intended post-exec access restrictions and could\nexpose sensitive memory addresses or be used as a primitive in a larger\nexploit chain. Consequently, the race can lead to unauthorized\ndisclosure of information across privilege boundaries and poses a\npotential security risk.\n\nTake a read lock on signal-\u0026gt;exec_update_lock prior to invoking\nptrace_may_access() and accessing the robust_list/compat_robust_list.\nThis ensures that the target task\u0026apos;s exec state remains stable during the\ncheck, allowing for consistent and synchronized validation of\ncredentials.(CVE-2025-40341)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnvme-fc: use lock accessing port_state and rport state\n\nnvme_fc_unregister_remote removes the remote port on a lport object at\nany point in time when there is no active association. This races with\nwith the reconnect logic, because nvme_fc_create_association is not\ntaking a lock to check the port_state and atomically increase the\nactive count on the rport.(CVE-2025-40342)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnvmet-fc: avoid scheduling association deletion twice\n\nWhen forcefully shutting down a port via the configfs interface,\nnvmet_port_subsys_drop_link() first calls nvmet_port_del_ctrls() and\nthen nvmet_disable_port(). Both functions will eventually schedule all\nremaining associations for deletion.\n\nThe current implementation checks whether an association is about to be\nremoved, but only after the work item has already been scheduled. As a\nresult, it is possible for the first scheduled work item to free all\nresources, and then for the same work item to be scheduled again for\ndeletion.\n\nBecause the association list is an RCU list, it is not possible to take\na lock and remove the list entry directly, so it cannot be looked up\nagain. Instead, a flag (terminating) must be used to determine whether\nthe association is already in the process of being deleted.(CVE-2025-40343)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\narch_topology: Fix incorrect error check in topology_parse_cpu_capacity()\n\nFix incorrect use of PTR_ERR_OR_ZERO() in topology_parse_cpu_capacity()\nwhich causes the code to proceed with NULL clock pointers. The current\nlogic uses !PTR_ERR_OR_ZERO(cpu_clk) which evaluates to true for both\nvalid pointers and NULL, leading to potential NULL pointer dereference\nin clk_get_rate().\n\nPer include/linux/err.h documentation, PTR_ERR_OR_ZERO(ptr) returns:\n\u0026quot;The error code within @ptr if it is an error pointer; 0 otherwise.\u0026quot;\n\nThis means PTR_ERR_OR_ZERO() returns 0 for both valid pointers AND NULL\npointers. Therefore !PTR_ERR_OR_ZERO(cpu_clk) evaluates to true (proceed)\nwhen cpu_clk is either valid or NULL, causing clk_get_rate(NULL) to be\ncalled when of_clk_get() returns NULL.\n\nReplace with !IS_ERR_OR_NULL(cpu_clk) which only proceeds for valid\npointers, preventing potential NULL pointer dereference in clk_get_rate().(CVE-2025-40346)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nhfsplus: fix KMSAN uninit-value issue in hfsplus_delete_cat()\n\nThe syzbot reported issue in hfsplus_delete_cat():\n\n[   70.682285][ T9333] =====================================================\n[   70.682943][ T9333] BUG: KMSAN: uninit-value in hfsplus_subfolders_dec+0x1d7/0x220\n[   70.683640][ T9333]  hfsplus_subfolders_dec+0x1d7/0x220\n[   70.684141][ T9333]  hfsplus_delete_cat+0x105d/0x12b0\n[   70.684621][ T9333]  hfsplus_rmdir+0x13d/0x310\n[   70.685048][ T9333]  vfs_rmdir+0x5ba/0x810\n[   70.685447][ T9333]  do_rmdir+0x964/0xea0\n[   70.685833][ T9333]  __x64_sys_rmdir+0x71/0xb0\n[   70.686260][ T9333]  x64_sys_call+0xcd8/0x3cf0\n[   70.686695][ T9333]  do_syscall_64+0xd9/0x1d0\n[   70.687119][ T9333]  entry_SYSCALL_64_after_hwframe+0x77/0x7f\n[   70.687646][ T9333]\n[   70.687856][ T9333] Uninit was stored to memory at:\n[   70.688311][ T9333]  hfsplus_subfolders_inc+0x1c2/0x1d0\n[   70.688779][ T9333]  hfsplus_create_cat+0x148e/0x1800\n[   70.689231][ T9333]  hfsplus_mknod+0x27f/0x600\n[   70.689730][ T9333]  hfsplus_mkdir+0x5a/0x70\n[   70.690146][ T9333]  vfs_mkdir+0x483/0x7a0\n[   70.690545][ T9333]  do_mkdirat+0x3f2/0xd30\n[   70.690944][ T9333]  __x64_sys_mkdir+0x9a/0xf0\n[   70.691380][ T9333]  x64_sys_call+0x2f89/0x3cf0\n[   70.691816][ T9333]  do_syscall_64+0xd9/0x1d0\n[   70.692229][ T9333]  entry_SYSCALL_64_after_hwframe+0x77/0x7f\n[   70.692773][ T9333]\n[   70.692990][ T9333] Uninit was stored to memory at:\n[   70.693469][ T9333]  hfsplus_subfolders_inc+0x1c2/0x1d0\n[   70.693960][ T9333]  hfsplus_create_cat+0x148e/0x1800\n[   70.694438][ T9333]  hfsplus_fill_super+0x21c1/0x2700\n[   70.694911][ T9333]  mount_bdev+0x37b/0x530\n[   70.695320][ T9333]  hfsplus_mount+0x4d/0x60\n[   70.695729][ T9333]  legacy_get_tree+0x113/0x2c0\n[   70.696167][ T9333]  vfs_get_tree+0xb3/0x5c0\n[   70.696588][ T9333]  do_new_mount+0x73e/0x1630\n[   70.697013][ T9333]  path_mount+0x6e3/0x1eb0\n[   70.697425][ T9333]  __se_sys_mount+0x733/0x830\n[   70.697857][ T9333]  __x64_sys_mount+0xe4/0x150\n[   70.698269][ T9333]  x64_sys_call+0x2691/0x3cf0\n[   70.698704][ T9333]  do_syscall_64+0xd9/0x1d0\n[   70.699117][ T9333]  entry_SYSCALL_64_after_hwframe+0x77/0x7f\n[   70.699730][ T9333]\n[   70.699946][ T9333] Uninit was created at:\n[   70.700378][ T9333]  __alloc_pages_noprof+0x714/0xe60\n[   70.700843][ T9333]  alloc_pages_mpol_noprof+0x2a2/0x9b0\n[   70.701331][ T9333]  alloc_pages_noprof+0xf8/0x1f0\n[   70.701774][ T9333]  allocate_slab+0x30e/0x1390\n[   70.702194][ T9333]  ___slab_alloc+0x1049/0x33a0\n[   70.702635][ T9333]  kmem_cache_alloc_lru_noprof+0x5ce/0xb20\n[   70.703153][ T9333]  hfsplus_alloc_inode+0x5a/0xd0\n[   70.703598][ T9333]  alloc_inode+0x82/0x490\n[   70.703984][ T9333]  iget_locked+0x22e/0x1320\n[   70.704428][ T9333]  hfsplus_iget+0x5c/0xba0\n[   70.704827][ T9333]  hfsplus_btree_open+0x135/0x1dd0\n[   70.705291][ T9333]  hfsplus_fill_super+0x1132/0x2700\n[   70.705776][ T9333]  mount_bdev+0x37b/0x530\n[   70.706171][ T9333]  hfsplus_mount+0x4d/0x60\n[   70.706579][ T9333]  legacy_get_tree+0x113/0x2c0\n[   70.707019][ T9333]  vfs_get_tree+0xb3/0x5c0\n[   70.707444][ T9333]  do_new_mount+0x73e/0x1630\n[   70.707865][ T9333]  path_mount+0x6e3/0x1eb0\n[   70.708270][ T9333]  __se_sys_mount+0x733/0x830\n[   70.708711][ T9333]  __x64_sys_mount+0xe4/0x150\n[   70.709158][ T9333]  x64_sys_call+0x2691/0x3cf0\n[   70.709630][ T9333]  do_syscall_64+0xd9/0x1d0\n[   70.710053][ T9333]  entry_SYSCALL_64_after_hwframe+0x77/0x7f\n[   70.710611][ T9333]\n[   70.710842][ T9333] CPU: 3 UID: 0 PID: 9333 Comm: repro Not tainted 6.12.0-rc6-dirty #17\n[   70.711568][ T9333] Hardware name: QEMU Ubuntu 24.04 PC (i440FX + PIIX, 1996), BIOS 1.16.3-debian-1.16.3-2 04/01/2014\n[   70.712490][ T9333] =====================================================\n[   70.713085][ T9333] Disabling lock debugging due to kernel taint\n[   70.713618][ T9333] Kernel panic - not syncing: kmsan.panic set ...\n[   70.714159][ T9333] \n---truncated---(CVE-2025-40351)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nriscv: stacktrace: Disable KASAN checks for non-current tasks\n\nUnwinding the stack of a task other than current, KASAN would report\n\u0026quot;BUG: KASAN: out-of-bounds in walk_stackframe+0x41c/0x460\u0026quot;\n\nThere is a same issue on x86 and has been resolved by the commit\n84936118bdf3 (\u0026quot;x86/unwind: Disable KASAN checks for non-current tasks\u0026quot;)\nThe solution could be applied to RISC-V too.\n\nThis patch also can solve the issue:\nhttps://seclists.org/oss-sec/2025/q4/23\n\n[(CVE-2025-40358)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nperf/x86/intel: Fix KASAN global-out-of-bounds warning\n\nWhen running \u0026quot;perf mem record\u0026quot; command on CWF, the below KASAN\nglobal-out-of-bounds warning is seen.\n\n  ==================================================================\n  BUG: KASAN: global-out-of-bounds in cmt_latency_data+0x176/0x1b0\n  Read of size 4 at addr ffffffffb721d000 by task dtlb/9850\n\n  Call Trace:\n\n   kasan_report+0xb8/0xf0\n   cmt_latency_data+0x176/0x1b0\n   setup_arch_pebs_sample_data+0xf49/0x2560\n   intel_pmu_drain_arch_pebs+0x577/0xb00\n   handle_pmi_common+0x6c4/0xc80\n\nThe issue is caused by below code in __grt_latency_data(). The code\ntries to access x86_hybrid_pmu structure which doesn\u0026apos;t exist on\nnon-hybrid platform like CWF.\n\n        WARN_ON_ONCE(hybrid_pmu(event-\u0026gt;pmu)-\u0026gt;pmu_type == hybrid_big)\n\nSo add is_hybrid() check before calling this WARN_ON_ONCE to fix the\nglobal-out-of-bounds access issue.(CVE-2025-40359)\n\nRejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority.(CVE-2025-40361)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nx86/fpu: Ensure XFD state on signal delivery\n\nSean reported [1] the following splat when running KVM tests:\n\n   WARNING: CPU: 232 PID: 15391 at xfd_validate_state+0x65/0x70\n   Call Trace:\n    \u0026lt;TASK\u0026gt;\n    fpu__clear_user_states+0x9c/0x100\n    arch_do_signal_or_restart+0x142/0x210\n    exit_to_user_mode_loop+0x55/0x100\n    do_syscall_64+0x205/0x2c0\n    entry_SYSCALL_64_after_hwframe+0x4b/0x53\n\nChao further identified [2] a reproducible scenario involving signal\ndelivery: a non-AMX task is preempted by an AMX-enabled task which\nmodifies the XFD MSR.\n\nWhen the non-AMX task resumes and reloads XSTATE with init values,\na warning is triggered due to a mismatch between fpstate::xfd and the\nCPU\u0026apos;s current XFD state. fpu__clear_user_states() does not currently\nre-synchronize the XFD state after such preemption.\n\nInvoke xfd_update_state() which detects and corrects the mismatch if\nthere is a dynamic feature.\n\nThis also benefits the sigreturn path, as fpu__restore_sig() may call\nfpu__clear_user_states() when the sigframe is inaccessible.\n\n[ dhansen: minor changelog munging ](CVE-2025-68171)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nftrace: Fix softlockup in ftrace_module_enable\n\nA soft lockup was observed when loading amdgpu module.\nIf a module has a lot of tracable functions, multiple calls\nto kallsyms_lookup can spend too much time in RCU critical\nsection and with disabled preemption, causing kernel panic.\nThis is the same issue that was fixed in\ncommit d0b24b4e91fc (\u0026quot;ftrace: Prevent RCU stall on PREEMPT_VOLUNTARY\nkernels\u0026quot;) and commit 42ea22e754ba (\u0026quot;ftrace: Add cond_resched() to\nftrace_graph_set_hash()\u0026quot;).\n\nFix it the same way by adding cond_resched() in ftrace_module_enable.(CVE-2025-68173)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\namd/amdkfd: enhance kfd process check in switch partition\n\ncurrent switch partition only check if kfd_processes_table is empty.\nkfd_prcesses_table entry is deleted in kfd_process_notifier_release, but\nkfd_process tear down is in kfd_process_wq_release.\n\nconsider two processes:\n\nProcess A (workqueue) -\u0026gt; kfd_process_wq_release -\u0026gt; Access kfd_node member\nProcess B switch partition -\u0026gt; amdgpu_xcp_pre_partition_switch -\u0026gt; amdgpu_amdkfd_device_fini_sw\n-\u0026gt; kfd_node tear down.\n\nProcess A and B may trigger a race as shown in dmesg log.\n\nThis patch is to resolve the race by adding an atomic kfd_process counter\nkfd_processes_count, it increment as create kfd process, decrement as\nfinish kfd_process_wq_release.\n\nv2: Put kfd_processes_count per kfd_dev, move decrement to kfd_process_destroy_pdds\nand bug fix. (Philip Yang)\n\n[3966658.307702] divide error: 0000 [#1] SMP NOPTI\n[3966658.350818]  i10nm_edac\n[3966658.356318] CPU: 124 PID: 38435 Comm: kworker/124:0 Kdump: loaded Tainted\n[3966658.356890] Workqueue: kfd_process_wq kfd_process_wq_release [amdgpu]\n[3966658.362839]  nfit\n[3966658.366457] RIP: 0010:kfd_get_num_sdma_engines+0x17/0x40 [amdgpu]\n[3966658.366460] Code: 00 00 e9 ac 81 02 00 66 66 2e 0f 1f 84 00 00 00 00 00 90 0f 1f 44 00 00 48 8b 4f 08 48 8b b7 00 01 00 00 8b 81 58 26 03 00 99 \u0026lt;f7\u0026gt; be b8 01 00 00 80 b9 70 2e 00 00 00 74 0b 83 f8 02 ba 02 00 00\n[3966658.380967]  x86_pkg_temp_thermal\n[3966658.391529] RSP: 0018:ffffc900a0edfdd8 EFLAGS: 00010246\n[3966658.391531] RAX: 0000000000000008 RBX: ffff8974e593b800 RCX: ffff888645900000\n[3966658.391531] RDX: 0000000000000000 RSI: ffff888129154400 RDI: ffff888129151c00\n[3966658.391532] RBP: ffff8883ad79d400 R08: 0000000000000000 R09: ffff8890d2750af4\n[3966658.391532] R10: 0000000000000018 R11: 0000000000000018 R12: 0000000000000000\n[3966658.391533] R13: ffff8883ad79d400 R14: ffffe87ff662ba00 R15: ffff8974e593b800\n[3966658.391533] FS:  0000000000000000(0000) GS:ffff88fe7f600000(0000) knlGS:0000000000000000\n[3966658.391534] CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033\n[3966658.391534] CR2: 0000000000d71000 CR3: 000000dd0e970004 CR4: 0000000002770ee0\n[3966658.391535] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000\n[3966658.391535] DR3: 0000000000000000 DR6: 00000000fffe07f0 DR7: 0000000000000400\n[3966658.391536] PKRU: 55555554\n[3966658.391536] Call Trace:\n[3966658.391674]  deallocate_sdma_queue+0x38/0xa0 [amdgpu]\n[3966658.391762]  process_termination_cpsch+0x1ed/0x480 [amdgpu]\n[3966658.399754]  intel_powerclamp\n[3966658.402831]  kfd_process_dequeue_from_all_devices+0x5b/0xc0 [amdgpu]\n[3966658.402908]  kfd_process_wq_release+0x1a/0x1a0 [amdgpu]\n[3966658.410516]  coretemp\n[3966658.434016]  process_one_work+0x1ad/0x380\n[3966658.434021]  worker_thread+0x49/0x310\n[3966658.438963]  kvm_intel\n[3966658.446041]  ? process_one_work+0x380/0x380\n[3966658.446045]  kthread+0x118/0x140\n[3966658.446047]  ? __kthread_bind_mask+0x60/0x60\n[3966658.446050]  ret_from_fork+0x1f/0x30\n[3966658.446053] Modules linked in: kpatch_20765354(OEK)\n[3966658.455310]  kvm\n[3966658.464534]  mptcp_diag xsk_diag raw_diag unix_diag af_packet_diag netlink_diag udp_diag act_pedit act_mirred act_vlan cls_flower kpatch_21951273(OEK) kpatch_18424469(OEK) kpatch_19749756(OEK)\n[3966658.473462]  idxd_mdev\n[3966658.482306]  kpatch_17971294(OEK) sch_ingress xt_conntrack amdgpu(OE) amdxcp(OE) amddrm_buddy(OE) amd_sched(OE) amdttm(OE) amdkcl(OE) intel_ifs iptable_mangle tcm_loop target_core_pscsi tcp_diag target_core_file inet_diag target_core_iblock target_core_user target_core_mod coldpgs kpatch_18383292(OEK) ip6table_nat ip6table_filter ip6_tables ip_set_hash_ipportip ip_set_hash_ipportnet ip_set_hash_ipport ip_set_bitmap_port xt_comment iptable_nat nf_nat iptable_filter ip_tables ip_set ip_vs_sh ip_vs_wrr ip_vs_rr ip_vs nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 sn_core_odd(OE) i40e overlay binfmt_misc tun bonding(OE) aisqos(OE) aisqo\n---truncated---(CVE-2025-68174)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nPCI: cadence: Check for the existence of cdns_pcie::ops before using it\n\ncdns_pcie::ops might not be populated by all the Cadence glue drivers. This\nis going to be true for the upcoming Sophgo platform which doesn\u0026apos;t set the\nops.\n\nHence, add a check to prevent NULL pointer dereference.\n\n[mani: reworded subject and description](CVE-2025-68176)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ntcp: use dst_dev_rcu() in tcp_fastopen_active_disable_ofo_check()\n\nUse RCU to avoid a pair of atomic operations and a potential\nUAF on dst_dev()-\u0026gt;flags.(CVE-2025-68188)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nbpf: Add bpf_prog_run_data_pointers()\n\nsyzbot found that cls_bpf_classify() is able to change\ntc_skb_cb(skb)-\u0026gt;drop_reason triggering a warning in sk_skb_reason_drop().\n\nWARNING: CPU: 0 PID: 5965 at net/core/skbuff.c:1192 __sk_skb_reason_drop net/core/skbuff.c:1189 [inline]\nWARNING: CPU: 0 PID: 5965 at net/core/skbuff.c:1192 sk_skb_reason_drop+0x76/0x170 net/core/skbuff.c:1214\n\nstruct tc_skb_cb has been added in commit ec624fe740b4 (\u0026quot;net/sched:\nExtend qdisc control block with tc control block\u0026quot;), which added a wrong\ninteraction with db58ba459202 (\u0026quot;bpf: wire in data and data_end for\ncls_act_bpf\u0026quot;).\n\ndrop_reason was added later.\n\nAdd bpf_prog_run_data_pointers() helper to save/restore the net_sched\nstorage colliding with BPF data_meta/data_end.(CVE-2025-68200)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnetfilter: nft_ct: add seqadj extension for natted connections\n\nSequence adjustment may be required for FTP traffic with PASV/EPSV modes.\ndue to need to re-write packet payload (IP, port) on the ftp control\nconnection. This can require changes to the TCP length and expected\nseq / ack_seq.\n\nThe easiest way to reproduce this issue is with PASV mode.\nExample ruleset:\ntable inet ftp_nat {\n        ct helper ftp_helper {\n                type \u0026quot;ftp\u0026quot; protocol tcp\n                l3proto inet\n        }\n\n        chain prerouting {\n                type filter hook prerouting priority 0; policy accept;\n                tcp dport 21 ct state new ct helper set \u0026quot;ftp_helper\u0026quot;\n        }\n}\ntable ip nat {\n        chain prerouting {\n                type nat hook prerouting priority -100; policy accept;\n                tcp dport 21 dnat ip prefix to ip daddr map {\n\t\t\t192.168.100.1 : 192.168.13.2/32 }\n        }\n\n        chain postrouting {\n                type nat hook postrouting priority 100 ; policy accept;\n                tcp sport 21 snat ip prefix to ip saddr map {\n\t\t\t192.168.13.2 : 192.168.100.1/32 }\n        }\n}\n\nNote that the ftp helper gets assigned *after* the dnat setup.\n\nThe inverse (nat after helper assign) is handled by an existing\ncheck in nf_nat_setup_info() and will not show the problem.\n\nTopoloy:\n\n +-------------------+     +----------------------------------+\n | FTP: 192.168.13.2 | \u0026lt;-\u0026gt; | NAT: 192.168.13.3, 192.168.100.1 |\n +-------------------+     +----------------------------------+\n                                      |\n                         +-----------------------+\n                         | Client: 192.168.100.2 |\n                         +-----------------------+\n\nftp nat changes do not work as expected in this case:\nConnected to 192.168.100.1.\n[..]\nftp\u0026gt; epsv\nEPSV/EPRT on IPv4 off.\nftp\u0026gt; ls\n227 Entering passive mode (192,168,100,1,209,129).\n421 Service not available, remote server has closed connection.\n\nKernel logs:\nMissing nfct_seqadj_ext_add() setup call\nWARNING: CPU: 1 PID: 0 at net/netfilter/nf_conntrack_seqadj.c:41\n[..]\n __nf_nat_mangle_tcp_packet+0x100/0x160 [nf_nat]\n nf_nat_ftp+0x142/0x280 [nf_nat_ftp]\n help+0x4d1/0x880 [nf_conntrack_ftp]\n nf_confirm+0x122/0x2e0 [nf_conntrack]\n nf_hook_slow+0x3c/0xb0\n ..\n\nFix this by adding the required extension when a conntrack helper is assigned\nto a connection that has a nat binding.(CVE-2025-68206)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nbpf: account for current allocated stack depth in widen_imprecise_scalars()\n\nThe usage pattern for widen_imprecise_scalars() looks as follows:\n\n    prev_st = find_prev_entry(env, ...);\n    queued_st = push_stack(...);\n    widen_imprecise_scalars(env, prev_st, queued_st);\n\nWhere prev_st is an ancestor of the queued_st in the explored states\ntree. This ancestor is not guaranteed to have same allocated stack\ndepth as queued_st. E.g. in the following case:\n\n    def main():\n      for i in 1..2:\n        foo(i)        // same callsite, differnt param\n\n    def foo(i):\n      if i == 1:\n        use 128 bytes of stack\n      iterator based loop\n\nHere, for a second \u0026apos;foo\u0026apos; call prev_st-\u0026gt;allocated_stack is 128,\nwhile queued_st-\u0026gt;allocated_stack is much smaller.\nwiden_imprecise_scalars() needs to take this into account and avoid\naccessing bpf_verifier_state-\u0026gt;frame[*]-\u0026gt;stack out of bounds.(CVE-2025-68208)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ntimers: Fix NULL function pointer race in timer_shutdown_sync()\n\nThere is a race condition between timer_shutdown_sync() and timer\nexpiration that can lead to hitting a WARN_ON in expire_timers().\n\nThe issue occurs when timer_shutdown_sync() clears the timer function\nto NULL while the timer is still running on another CPU. The race\nscenario looks like this:\n\nCPU0\t\t\t\t\tCPU1\n\t\t\t\t\t\u0026lt;SOFTIRQ\u0026gt;\n\t\t\t\t\tlock_timer_base()\n\t\t\t\t\texpire_timers()\n\t\t\t\t\tbase-\u0026gt;running_timer = timer;\n\t\t\t\t\tunlock_timer_base()\n\t\t\t\t\t[call_timer_fn enter]\n\t\t\t\t\tmod_timer()\n\t\t\t\t\t...\ntimer_shutdown_sync()\nlock_timer_base()\n// For now, will not detach the timer but only clear its function to NULL\nif (base-\u0026gt;running_timer != timer)\n\tret = detach_if_pending(timer, base, true);\nif (shutdown)\n\ttimer-\u0026gt;function = NULL;\nunlock_timer_base()\n\t\t\t\t\t[call_timer_fn exit]\n\t\t\t\t\tlock_timer_base()\n\t\t\t\t\tbase-\u0026gt;running_timer = NULL;\n\t\t\t\t\tunlock_timer_base()\n\t\t\t\t\t...\n\t\t\t\t\t// Now timer is pending while its function set to NULL.\n\t\t\t\t\t// next timer trigger\n\t\t\t\t\t\u0026lt;SOFTIRQ\u0026gt;\n\t\t\t\t\texpire_timers()\n\t\t\t\t\tWARN_ON_ONCE(!fn) // hit\n\t\t\t\t\t...\nlock_timer_base()\n// Now timer will detach\nif (base-\u0026gt;running_timer != timer)\n\tret = detach_if_pending(timer, base, true);\nif (shutdown)\n\ttimer-\u0026gt;function = NULL;\nunlock_timer_base()\n\nThe problem is that timer_shutdown_sync() clears the timer function\nregardless of whether the timer is currently running. This can leave a\npending timer with a NULL function pointer, which triggers the\nWARN_ON_ONCE(!fn) check in expire_timers().\n\nFix this by only clearing the timer function when actually detaching the\ntimer. If the timer is running, leave the function pointer intact, which is\nsafe because the timer will be properly detached when it finishes running.(CVE-2025-68214)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnouveau/firmware: Add missing kfree() of nvkm_falcon_fw::boot\n\nnvkm_falcon_fw::boot is allocated, but no one frees it. This causes a\nkmemleak warning.\n\nMake sure this data is deallocated.(CVE-2025-68235)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nKVM: SVM: Don\u0026apos;t skip unrelated instruction if INT3/INTO is replaced\n\nWhen re-injecting a soft interrupt from an INT3, INT0, or (select) INTn\ninstruction, discard the exception and retry the instruction if the code\nstream is changed (e.g. by a different vCPU) between when the CPU\nexecutes the instruction and when KVM decodes the instruction to get the\nnext RIP.\n\nAs effectively predicted by commit 6ef88d6e36c2 (\u0026quot;KVM: SVM: Re-inject\nINT3/INTO instead of retrying the instruction\u0026quot;), failure to verify that\nthe correct INTn instruction was decoded can effectively clobber guest\nstate due to decoding the wrong instruction and thus specifying the\nwrong next RIP.\n\nThe bug most often manifests as \u0026quot;Oops: int3\u0026quot; panics on static branch\nchecks in Linux guests.  Enabling or disabling a static branch in Linux\nuses the kernel\u0026apos;s \u0026quot;text poke\u0026quot; code patching mechanism.  To modify code\nwhile other CPUs may be executing that code, Linux (temporarily)\nreplaces the first byte of the original instruction with an int3 (opcode\n0xcc), then patches in the new code stream except for the first byte,\nand finally replaces the int3 with the first byte of the new code\nstream.  If a CPU hits the int3, i.e. executes the code while it\u0026apos;s being\nmodified, then the guest kernel must look up the RIP to determine how to\nhandle the #BP, e.g. by emulating the new instruction.  If the RIP is\nincorrect, then this lookup fails and the guest kernel panics.\n\nThe bug reproduces almost instantly by hacking the guest kernel to\nrepeatedly check a static branch[1] while running a drgn script[2] on\nthe host to constantly swap out the memory containing the guest\u0026apos;s TSS.\n\n[1]: https://gist.github.com/osandov/44d17c51c28c0ac998ea0334edf90b5a\n[2]: https://gist.github.com/osandov/10e45e45afa29b11e0c7209247afc00b(CVE-2025-68259)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\next4: add i_data_sem protection in ext4_destroy_inline_data_nolock()\n\nFix a race between inline data destruction and block mapping.\n\nThe function ext4_destroy_inline_data_nolock() changes the inode data\nlayout by clearing EXT4_INODE_INLINE_DATA and setting EXT4_INODE_EXTENTS.\nAt the same time, another thread may execute ext4_map_blocks(), which\ntests EXT4_INODE_EXTENTS to decide whether to call ext4_ext_map_blocks()\nor ext4_ind_map_blocks().\n\nWithout i_data_sem protection, ext4_ind_map_blocks() may receive inode\nwith EXT4_INODE_EXTENTS flag and triggering assert.\n\nkernel BUG at fs/ext4/indirect.c:546!\nEXT4-fs (loop2): unmounting filesystem.\ninvalid opcode: 0000 [#1] PREEMPT SMP KASAN NOPTI\nHardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.12.0-1 04/01/2014\nRIP: 0010:ext4_ind_map_blocks.cold+0x2b/0x5a fs/ext4/indirect.c:546\n\nCall Trace:\n \u0026lt;TASK\u0026gt;\n ext4_map_blocks+0xb9b/0x16f0 fs/ext4/inode.c:681\n _ext4_get_block+0x242/0x590 fs/ext4/inode.c:822\n ext4_block_write_begin+0x48b/0x12c0 fs/ext4/inode.c:1124\n ext4_write_begin+0x598/0xef0 fs/ext4/inode.c:1255\n ext4_da_write_begin+0x21e/0x9c0 fs/ext4/inode.c:3000\n generic_perform_write+0x259/0x5d0 mm/filemap.c:3846\n ext4_buffered_write_iter+0x15b/0x470 fs/ext4/file.c:285\n ext4_file_write_iter+0x8e0/0x17f0 fs/ext4/file.c:679\n call_write_iter include/linux/fs.h:2271 [inline]\n do_iter_readv_writev+0x212/0x3c0 fs/read_write.c:735\n do_iter_write+0x186/0x710 fs/read_write.c:861\n vfs_iter_write+0x70/0xa0 fs/read_write.c:902\n iter_file_splice_write+0x73b/0xc90 fs/splice.c:685\n do_splice_from fs/splice.c:763 [inline]\n direct_splice_actor+0x10f/0x170 fs/splice.c:950\n splice_direct_to_actor+0x33a/0xa10 fs/splice.c:896\n do_splice_direct+0x1a9/0x280 fs/splice.c:1002\n do_sendfile+0xb13/0x12c0 fs/read_write.c:1255\n __do_sys_sendfile64 fs/read_write.c:1323 [inline]\n __se_sys_sendfile64 fs/read_write.c:1309 [inline]\n __x64_sys_sendfile64+0x1cf/0x210 fs/read_write.c:1309\n do_syscall_x64 arch/x86/entry/common.c:51 [inline]\n do_syscall_64+0x35/0x80 arch/x86/entry/common.c:81\n entry_SYSCALL_64_after_hwframe+0x6e/0xd8(CVE-2025-68261)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\next4: refresh inline data size before write operations\n\nThe cached ei-\u0026gt;i_inline_size can become stale between the initial size\ncheck and when ext4_update_inline_data()/ext4_create_inline_data() use\nit. Although ext4_get_max_inline_size() reads the correct value at the\ntime of the check, concurrent xattr operations can modify i_inline_size\nbefore ext4_write_lock_xattr() is acquired.\n\nThis causes ext4_update_inline_data() and ext4_create_inline_data() to\nwork with stale capacity values, leading to a BUG_ON() crash in\next4_write_inline_data():\n\n  kernel BUG at fs/ext4/inline.c:1331!\n  BUG_ON(pos + len \u0026gt; EXT4_I(inode)-\u0026gt;i_inline_size);\n\nThe race window:\n1. ext4_get_max_inline_size() reads i_inline_size = 60 (correct)\n2. Size check passes for 50-byte write\n3. [Another thread adds xattr, i_inline_size changes to 40]\n4. ext4_write_lock_xattr() acquires lock\n5. ext4_update_inline_data() uses stale i_inline_size = 60\n6. Attempts to write 50 bytes but only 40 bytes actually available\n7. BUG_ON() triggers\n\nFix this by recalculating i_inline_size via ext4_find_inline_data_nolock()\nimmediately after acquiring xattr_sem. This ensures ext4_update_inline_data()\nand ext4_create_inline_data() work with current values that are protected\nfrom concurrent modifications.\n\nThis is similar to commit a54c4613dac1 (\u0026quot;ext4: fix race writing to an\ninline_data file while its xattrs are changing\u0026quot;) which fixed i_inline_off\nstaleness. This patch addresses the related i_inline_size staleness issue.(CVE-2025-68264)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnvme: fix admin request_queue lifetime\n\nThe namespaces can access the controller\u0026apos;s admin request_queue, and\nstale references on the namespaces may exist after tearing down the\ncontroller. Ensure the admin request_queue is active by moving the\ncontroller\u0026apos;s \u0026apos;put\u0026apos; to after all controller references have been released\nto ensure no one is can access the request_queue. This fixes a reported\nuse-after-free bug:\n\n  BUG: KASAN: slab-use-after-free in blk_queue_enter+0x41c/0x4a0\n  Read of size 8 at addr ffff88c0a53819f8 by task nvme/3287\n  CPU: 67 UID: 0 PID: 3287 Comm: nvme Tainted: G            E       6.13.2-ga1582f1a031e #15\n  Tainted: [E]=UNSIGNED_MODULE\n  Hardware name: Jabil /EGS 2S MB1, BIOS 1.00 06/18/2025\n  Call Trace:\n   \u0026lt;TASK\u0026gt;\n   dump_stack_lvl+0x4f/0x60\n   print_report+0xc4/0x620\n   ? _raw_spin_lock_irqsave+0x70/0xb0\n   ? _raw_read_unlock_irqrestore+0x30/0x30\n   ? blk_queue_enter+0x41c/0x4a0\n   kasan_report+0xab/0xe0\n   ? blk_queue_enter+0x41c/0x4a0\n   blk_queue_enter+0x41c/0x4a0\n   ? __irq_work_queue_local+0x75/0x1d0\n   ? blk_queue_start_drain+0x70/0x70\n   ? irq_work_queue+0x18/0x20\n   ? vprintk_emit.part.0+0x1cc/0x350\n   ? wake_up_klogd_work_func+0x60/0x60\n   blk_mq_alloc_request+0x2b7/0x6b0\n   ? __blk_mq_alloc_requests+0x1060/0x1060\n   ? __switch_to+0x5b7/0x1060\n   nvme_submit_user_cmd+0xa9/0x330\n   nvme_user_cmd.isra.0+0x240/0x3f0\n   ? force_sigsegv+0xe0/0xe0\n   ? nvme_user_cmd64+0x400/0x400\n   ? vfs_fileattr_set+0x9b0/0x9b0\n   ? cgroup_update_frozen_flag+0x24/0x1c0\n   ? cgroup_leave_frozen+0x204/0x330\n   ? nvme_ioctl+0x7c/0x2c0\n   blkdev_ioctl+0x1a8/0x4d0\n   ? blkdev_common_ioctl+0x1930/0x1930\n   ? fdget+0x54/0x380\n   __x64_sys_ioctl+0x129/0x190\n   do_syscall_64+0x5b/0x160\n   entry_SYSCALL_64_after_hwframe+0x4b/0x53\n  RIP: 0033:0x7f765f703b0b\n  Code: ff ff ff 85 c0 79 9b 49 c7 c4 ff ff ff ff 5b 5d 4c 89 e0 41 5c c3 66 0f 1f 84 00 00 00 00 00 f3 0f 1e fa b8 10 00 00 00 0f 05 \u0026lt;48\u0026gt; 3d 01 f0 ff ff 73 01 c3 48 8b 0d dd 52 0f 00 f7 d8 64 89 01 48\n  RSP: 002b:00007ffe2cefe808 EFLAGS: 00000202 ORIG_RAX: 0000000000000010\n  RAX: ffffffffffffffda RBX: 00007ffe2cefe860 RCX: 00007f765f703b0b\n  RDX: 00007ffe2cefe860 RSI: 00000000c0484e41 RDI: 0000000000000003\n  RBP: 0000000000000000 R08: 0000000000000003 R09: 0000000000000000\n  R10: 00007f765f611d50 R11: 0000000000000202 R12: 0000000000000003\n  R13: 00000000c0484e41 R14: 0000000000000001 R15: 00007ffe2cefea60\n   \u0026lt;/TASK\u0026gt;(CVE-2025-68265)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nceph: fix crash in process_v2_sparse_read() for encrypted directories\n\nThe crash in process_v2_sparse_read() for fscrypt-encrypted directories\nhas been reported. Issue takes place for Ceph msgr2 protocol in secure\nmode. It can be reproduced by the steps:\n\nsudo mount -t ceph :/ /mnt/cephfs/ -o name=admin,fs=cephfs,ms_mode=secure\n\n(1) mkdir /mnt/cephfs/fscrypt-test-3\n(2) cp area_decrypted.tar /mnt/cephfs/fscrypt-test-3\n(3) fscrypt encrypt --source=raw_key --key=./my.key /mnt/cephfs/fscrypt-test-3\n(4) fscrypt lock /mnt/cephfs/fscrypt-test-3\n(5) fscrypt unlock --key=my.key /mnt/cephfs/fscrypt-test-3\n(6) cat /mnt/cephfs/fscrypt-test-3/area_decrypted.tar\n(7) Issue has been triggered\n\n[  408.072247] ------------[ cut here ]------------\n[  408.072251] WARNING: CPU: 1 PID: 392 at net/ceph/messenger_v2.c:865\nceph_con_v2_try_read+0x4b39/0x72f0\n[  408.072267] Modules linked in: intel_rapl_msr intel_rapl_common\nintel_uncore_frequency_common intel_pmc_core pmt_telemetry pmt_discovery\npmt_class intel_pmc_ssram_telemetry intel_vsec kvm_intel joydev kvm irqbypass\npolyval_clmulni ghash_clmulni_intel aesni_intel rapl input_leds psmouse\nserio_raw i2c_piix4 vga16fb bochs vgastate i2c_smbus floppy mac_hid qemu_fw_cfg\npata_acpi sch_fq_codel rbd msr parport_pc ppdev lp parport efi_pstore\n[  408.072304] CPU: 1 UID: 0 PID: 392 Comm: kworker/1:3 Not tainted 6.17.0-rc7+\n[  408.072307] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS\n1.17.0-5.fc42 04/01/2014\n[  408.072310] Workqueue: ceph-msgr ceph_con_workfn\n[  408.072314] RIP: 0010:ceph_con_v2_try_read+0x4b39/0x72f0\n[  408.072317] Code: c7 c1 20 f0 d4 ae 50 31 d2 48 c7 c6 60 27 d5 ae 48 c7 c7 f8\n8e 6f b0 68 60 38 d5 ae e8 00 47 61 fe 48 83 c4 18 e9 ac fc ff ff \u0026lt;0f\u0026gt; 0b e9 06\nfe ff ff 4c 8b 9d 98 fd ff ff 0f 84 64 e7 ff ff 89 85\n[  408.072319] RSP: 0018:ffff88811c3e7a30 EFLAGS: 00010246\n[  408.072322] RAX: ffffed1024874c6f RBX: ffffea00042c2b40 RCX: 0000000000000f38\n[  408.072324] RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000000000000\n[  408.072325] RBP: ffff88811c3e7ca8 R08: 0000000000000000 R09: 00000000000000c8\n[  408.072326] R10: 00000000000000c8 R11: 0000000000000000 R12: 00000000000000c8\n[  408.072327] R13: dffffc0000000000 R14: ffff8881243a6030 R15: 0000000000003000\n[  408.072329] FS:  0000000000000000(0000) GS:ffff88823eadf000(0000)\nknlGS:0000000000000000\n[  408.072331] CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033\n[  408.072332] CR2: 000000c0003c6000 CR3: 000000010c106005 CR4: 0000000000772ef0\n[  408.072336] PKRU: 55555554\n[  408.072337] Call Trace:\n[  408.072338]  \u0026lt;TASK\u0026gt;\n[  408.072340]  ? sched_clock_noinstr+0x9/0x10\n[  408.072344]  ? __pfx_ceph_con_v2_try_read+0x10/0x10\n[  408.072347]  ? _raw_spin_unlock+0xe/0x40\n[  408.072349]  ? finish_task_switch.isra.0+0x15d/0x830\n[  408.072353]  ? __kasan_check_write+0x14/0x30\n[  408.072357]  ? mutex_lock+0x84/0xe0\n[  408.072359]  ? __pfx_mutex_lock+0x10/0x10\n[  408.072361]  ceph_con_workfn+0x27e/0x10e0\n[  408.072364]  ? metric_delayed_work+0x311/0x2c50\n[  408.072367]  process_one_work+0x611/0xe20\n[  408.072371]  ? __kasan_check_write+0x14/0x30\n[  408.072373]  worker_thread+0x7e3/0x1580\n[  408.072375]  ? __pfx__raw_spin_lock_irqsave+0x10/0x10\n[  408.072378]  ? __pfx_worker_thread+0x10/0x10\n[  408.072381]  kthread+0x381/0x7a0\n[  408.072383]  ? __pfx__raw_spin_lock_irq+0x10/0x10\n[  408.072385]  ? __pfx_kthread+0x10/0x10\n[  408.072387]  ? __kasan_check_write+0x14/0x30\n[  408.072389]  ? recalc_sigpending+0x160/0x220\n[  408.072392]  ? _raw_spin_unlock_irq+0xe/0x50\n[  408.072394]  ? calculate_sigpending+0x78/0xb0\n[  408.072395]  ? __pfx_kthread+0x10/0x10\n[  408.072397]  ret_from_fork+0x2b6/0x380\n[  408.072400]  ? __pfx_kthread+0x10/0x10\n[  408.072402]  ret_from_fork_asm+0x1a/0x30\n[  408.072406]  \u0026lt;/TASK\u0026gt;\n[  408.072407] ---[ end trace 0000000000000000 ]---\n[  408.072418] Oops: general protection fault, probably for non-canonical\naddress 0xdffffc00000000\n---truncated---(CVE-2025-68297)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nPCI/AER: Fix NULL pointer access by aer_info\n\nThe kzalloc(GFP_KERNEL) may return NULL, so all accesses to aer_info-\u0026gt;xxx\nwill result in kernel panic. Fix it.(CVE-2025-68309)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nusb: uas: fix urb unmapping issue when the uas device is remove during ongoing data transfer\n\nWhen a UAS device is unplugged during data transfer, there is\na probability of a system panic occurring. The root cause is\nan access to an invalid memory address during URB callback handling.\nSpecifically, this happens when the dma_direct_unmap_sg() function\nis called within the usb_hcd_unmap_urb_for_dma() interface, but the\nsg-\u0026gt;dma_address field is 0 and the sg data structure has already been\nfreed.\n\nThe SCSI driver sends transfer commands by invoking uas_queuecommand_lck()\nin uas.c, using the uas_submit_urbs() function to submit requests to USB.\nWithin the uas_submit_urbs() implementation, three URBs (sense_urb,\ndata_urb, and cmd_urb) are sequentially submitted. Device removal may\noccur at any point during uas_submit_urbs execution, which may result\nin URB submission failure. However, some URBs might have been successfully\nsubmitted before the failure, and uas_submit_urbs will return the -ENODEV\nerror code in this case. The current error handling directly calls\nscsi_done(). In the SCSI driver, this eventually triggers scsi_complete()\nto invoke scsi_end_request() for releasing the sgtable. The successfully\nsubmitted URBs, when being unlinked to giveback, call\nusb_hcd_unmap_urb_for_dma() in hcd.c, leading to exceptions during sg\nunmapping operations since the sg data structure has already been freed.\n\nThis patch modifies the error condition check in the uas_submit_urbs()\nfunction. When a UAS device is removed but one or more URBs have already\nbeen successfully submitted to USB, it avoids immediately invoking\nscsi_done() and save the cmnd to devinfo-\u0026gt;cmnd array. If the successfully\nsubmitted URBs is completed before devinfo-\u0026gt;resetting being set, then\nthe scsi_done() function will be called within uas_try_complete() after\nall pending URB operations are finalized. Otherwise, the scsi_done()\nfunction will be called within uas_zap_pending(), which is executed after\nusb_kill_anchored_urbs().\n\nThe error handling only takes effect when uas_queuecommand_lck() calls\nuas_submit_urbs() and returns the error value -ENODEV . In this case,\nthe device is disconnected, and the flow proceeds to uas_disconnect(),\nwhere uas_zap_pending() is invoked to call uas_try_complete().(CVE-2025-68331)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\njbd2: avoid bug_on in jbd2_journal_get_create_access() when file system corrupted\n\nThere\u0026apos;s issue when file system corrupted:\n------------[ cut here ]------------\nkernel BUG at fs/jbd2/transaction.c:1289!\nOops: invalid opcode: 0000 [#1] SMP KASAN PTI\nCPU: 5 UID: 0 PID: 2031 Comm: mkdir Not tainted 6.18.0-rc1-next\nRIP: 0010:jbd2_journal_get_create_access+0x3b6/0x4d0\nRSP: 0018:ffff888117aafa30 EFLAGS: 00010202\nRAX: 0000000000000000 RBX: ffff88811a86b000 RCX: ffffffff89a63534\nRDX: 1ffff110200ec602 RSI: 0000000000000004 RDI: ffff888100763010\nRBP: ffff888100763000 R08: 0000000000000001 R09: ffff888100763028\nR10: 0000000000000003 R11: 0000000000000000 R12: 0000000000000000\nR13: ffff88812c432000 R14: ffff88812c608000 R15: ffff888120bfc000\nCS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033\nCR2: 00007f91d6970c99 CR3: 00000001159c4000 CR4: 00000000000006f0\nCall Trace:\n \u0026lt;TASK\u0026gt;\n __ext4_journal_get_create_access+0x42/0x170\n ext4_getblk+0x319/0x6f0\n ext4_bread+0x11/0x100\n ext4_append+0x1e6/0x4a0\n ext4_init_new_dir+0x145/0x1d0\n ext4_mkdir+0x326/0x920\n vfs_mkdir+0x45c/0x740\n do_mkdirat+0x234/0x2f0\n __x64_sys_mkdir+0xd6/0x120\n do_syscall_64+0x5f/0xfa0\n entry_SYSCALL_64_after_hwframe+0x76/0x7e\n\nThe above issue occurs with us in errors=continue mode when accompanied by\nstorage failures. There have been many inconsistencies in the file system\ndata.\nIn the case of file system data inconsistency, for example, if the block\nbitmap of a referenced block is not set, it can lead to the situation where\na block being committed is allocated and used again. As a result, the\nfollowing condition will not be satisfied then trigger BUG_ON. Of course,\nit is entirely possible to construct a problematic image that can trigger\nthis BUG_ON through specific operations. In fact, I have constructed such\nan image and easily reproduced this issue.\nTherefore, J_ASSERT() holds true only under ideal conditions, but it may\nnot necessarily be satisfied in exceptional scenarios. Using J_ASSERT()\ndirectly in abnormal situations would cause the system to crash, which is\nclearly not what we want. So here we directly trigger a JBD abort instead\nof immediately invoking BUG_ON.(CVE-2025-68337)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nNFSv4/pNFS: Clear NFS_INO_LAYOUTCOMMIT in pnfs_mark_layout_stateid_invalid\n\nFixes a crash when layout is null during this call stack:\n\nwrite_inode\n    -\u0026gt; nfs4_write_inode\n        -\u0026gt; pnfs_layoutcommit_inode\n\npnfs_set_layoutcommit relies on the lseg refcount to keep the layout\naround. Need to clear NFS_INO_LAYOUTCOMMIT otherwise we might attempt\nto reference a null layout.(CVE-2025-68349)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nregulator: core: Protect regulator_supply_alias_list with regulator_list_mutex\n\nregulator_supply_alias_list was accessed without any locking in\nregulator_supply_alias(), regulator_register_supply_alias(), and\nregulator_unregister_supply_alias(). Concurrent registration,\nunregistration and lookups can race, leading to:\n\n1 use-after-free if an alias entry is removed while being read,\n2 duplicate entries when two threads register the same alias,\n3 inconsistent alias mappings observed by consumers.\n\nProtect all traversals, insertions and deletions on\nregulator_supply_alias_list with the existing regulator_list_mutex.(CVE-2025-68354)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ngfs2: Prevent recursive memory reclaim\n\nFunction new_inode() returns a new inode with inode-\u0026gt;i_mapping-\u0026gt;gfp_mask\nset to GFP_HIGHUSER_MOVABLE.  This value includes the __GFP_FS flag, so\nallocations in that address space can recurse into filesystem memory\nreclaim.  We don\u0026apos;t want that to happen because it can consume a\nsignificant amount of stack memory.\n\nWorse than that is that it can also deadlock: for example, in several\nplaces, gfs2_unstuff_dinode() is called inside filesystem transactions.\nThis calls filemap_grab_folio(), which can allocate a new folio, which\ncan trigger memory reclaim.  If memory reclaim recurses into the\nfilesystem and starts another transaction, a deadlock will ensue.\n\nTo fix these kinds of problems, prevent memory reclaim from recursing\ninto filesystem code by making sure that the gfp_mask of inode address\nspaces doesn\u0026apos;t include __GFP_FS.\n\nThe \u0026quot;meta\u0026quot; and resource group address spaces were already using GFP_NOFS\nas their gfp_mask (which doesn\u0026apos;t include __GFP_FS).  The default value\nof GFP_HIGHUSER_MOVABLE is less restrictive than GFP_NOFS, though.  To\navoid being overly limiting, use the default value and only knock off\nthe __GFP_FS flag.  I\u0026apos;m not sure if this will actually make a\ndifference, but it also shouldn\u0026apos;t hurt.\n\nThis patch is loosely based on commit ad22c7a043c2 (\u0026quot;xfs: prevent stack\noverflows from page cache allocation\u0026quot;).\n\nFixes xfstest generic/273.(CVE-2025-68356)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nwifi: rtl818x: rtl8187: Fix potential buffer underflow in rtl8187_rx_cb()\n\nThe rtl8187_rx_cb() calculates the rx descriptor header address\nby subtracting its size from the skb tail pointer.\nHowever, it does not validate if the received packet\n(skb-\u0026gt;len from urb-\u0026gt;actual_length) is large enough to contain this\nheader.\n\nIf a truncated packet is received, this will lead to a buffer\nunderflow, reading memory before the start of the skb data area,\nand causing a kernel panic.\n\nAdd length checks for both rtl8187 and rtl8187b descriptor headers\nbefore attempting to access them, dropping the packet cleanly if the\ncheck fails.(CVE-2025-68362)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nbpf: Check skb-\u0026gt;transport_header is set in bpf_skb_check_mtu\n\nThe bpf_skb_check_mtu helper needs to use skb-\u0026gt;transport_header when\nthe BPF_MTU_CHK_SEGS flag is used:\n\n\tbpf_skb_check_mtu(skb, ifindex, \u0026amp;mtu_len, 0, BPF_MTU_CHK_SEGS)\n\nThe transport_header is not always set. There is a WARN_ON_ONCE\nreport when CONFIG_DEBUG_NET is enabled + skb-\u0026gt;gso_size is set +\nbpf_prog_test_run is used:\n\nWARNING: CPU: 1 PID: 2216 at ./include/linux/skbuff.h:3071\n skb_gso_validate_network_len\n bpf_skb_check_mtu\n bpf_prog_3920e25740a41171_tc_chk_segs_flag # A test in the next patch\n bpf_test_run\n bpf_prog_test_run_skb\n\nFor a normal ingress skb (not test_run), skb_reset_transport_header\nis performed but there is plan to avoid setting it as described in\ncommit 2170a1f09148 (\u0026quot;net: no longer reset transport_header in __netif_receive_skb_core()\u0026quot;).\n\nThis patch fixes the bpf helper by checking\nskb_transport_header_was_set(). The check is done just before\nskb-\u0026gt;transport_header is used, to avoid breaking the existing bpf prog.\nThe WARN_ON_ONCE is limited to bpf_prog_test_run, so targeting bpf-next.(CVE-2025-68363)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ncoresight: ETR: Fix ETR buffer use-after-free issue\n\nWhen ETR is enabled as CS_MODE_SYSFS, if the buffer size is changed\nand enabled again, currently sysfs_buf will point to the newly\nallocated memory(buf_new) and free the old memory(buf_old). But the\netr_buf that is being used by the ETR remains pointed to buf_old, not\nupdated to buf_new. In this case, it will result in a memory\nuse-after-free issue.\n\nFix this by checking ETR\u0026apos;s mode before updating and releasing buf_old,\nif the mode is CS_MODE_SYSFS, then skip updating and releasing it.(CVE-2025-68376)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nbpf: Fix stackmap overflow check in __bpf_get_stackid()\n\nSyzkaller reported a KASAN slab-out-of-bounds write in __bpf_get_stackid()\nwhen copying stack trace data. The issue occurs when the perf trace\n contains more stack entries than the stack map bucket can hold,\n leading to an out-of-bounds write in the bucket\u0026apos;s data array.(CVE-2025-68378)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ncrypto: asymmetric_keys - prevent overflow in asymmetric_key_generate_id\n\nUse check_add_overflow() to guard against potential integer overflows\nwhen adding the binary blob lengths and the size of an asymmetric_key_id\nstructure and return ERR_PTR(-EOVERFLOW) accordingly. This prevents a\npossible buffer overflow when copying data from potentially malicious\nX.509 certificate fields that can be arbitrarily large, such as ASN.1\nINTEGER serial numbers, issuer names, etc.(CVE-2025-68724)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nbpf: Do not let BPF test infra emit invalid GSO types to stack\n\nYinhao et al. reported that their fuzzer tool was able to trigger a\nskb_warn_bad_offload() from netif_skb_features() -\u0026gt; gso_features_check().\nWhen a BPF program - triggered via BPF test infra - pushes the packet\nto the loopback device via bpf_clone_redirect() then mentioned offload\nwarning can be seen. GSO-related features are then rightfully disabled.\n\nWe get into this situation due to convert___skb_to_skb() setting\ngso_segs and gso_size but not gso_type. Technically, it makes sense\nthat this warning triggers since the GSO properties are malformed due\nto the gso_type. Potentially, the gso_type could be marked non-trustworthy\nthrough setting it at least to SKB_GSO_DODGY without any other specific\nassumptions, but that also feels wrong given we should not go further\ninto the GSO engine in the first place.\n\nThe checks were added in 121d57af308d (\u0026quot;gso: validate gso_type in GSO\nhandlers\u0026quot;) because there were malicious (syzbot) senders that combine\na protocol with a non-matching gso_type. If we would want to drop such\npackets, gso_features_check() currently only returns feature flags via\nnetif_skb_features(), so one location for potentially dropping such skbs\ncould be validate_xmit_unreadable_skb(), but then otoh it would be\nan additional check in the fast-path for a very corner case. Given\nbpf_clone_redirect() is the only place where BPF test infra could emit\nsuch packets, lets reject them right there.(CVE-2025-68725)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nisdn: mISDN: hfcsusb: fix memory leak in hfcsusb_probe()\n\nIn hfcsusb_probe(), the memory allocated for ctrl_urb gets leaked when\nsetup_instance() fails with an error code. Fix that by freeing the urb\nbefore freeing the hw structure. Also change the error paths to use the\ngoto ladder style.\n\nCompile tested only. Issue found using a prototype static analysis tool.(CVE-2025-68734)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nscsi: qla2xxx: Fix improper freeing of purex item\n\nIn qla2xxx_process_purls_iocb(), an item is allocated via\nqla27xx_copy_multiple_pkt(), which internally calls\nqla24xx_alloc_purex_item().\n\nThe qla24xx_alloc_purex_item() function may return a pre-allocated item\nfrom a per-adapter pool for small allocations, instead of dynamically\nallocating memory with kzalloc().\n\nAn error handling path in qla2xxx_process_purls_iocb() incorrectly uses\nkfree() to release the item. If the item was from the pre-allocated\npool, calling kfree() on it is a bug that can lead to memory corruption.\n\nFix this by using the correct deallocation function,\nqla24xx_free_purex_item(), which properly handles both dynamically\nallocated and pre-allocated items.(CVE-2025-68741)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nbpf: Free special fields when update [lru_,]percpu_hash maps\n\nAs [lru_,]percpu_hash maps support BPF_KPTR_{REF,PERCPU}, missing\ncalls to \u0026apos;bpf_obj_free_fields()\u0026apos; in \u0026apos;pcpu_copy_value()\u0026apos; could cause the\nmemory referenced by BPF_KPTR_{REF,PERCPU} fields to be held until the\nmap gets freed.\n\nFix this by calling \u0026apos;bpf_obj_free_fields()\u0026apos; after\n\u0026apos;copy_map_value[,_long]()\u0026apos; in \u0026apos;pcpu_copy_value()\u0026apos;.(CVE-2025-68744)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nscsi: qla2xxx: Clear cmds after chip reset\n\nCommit aefed3e5548f (\u0026quot;scsi: qla2xxx: target: Fix offline port handling\nand host reset handling\u0026quot;) caused two problems:\n\n1. Commands sent to FW, after chip reset got stuck and never freed as FW\n   is not going to respond to them anymore.\n\n2. BUG_ON(cmd-\u0026gt;sg_mapped) in qlt_free_cmd().  Commit 26f9ce53817a\n   (\u0026quot;scsi: qla2xxx: Fix missed DMA unmap for aborted commands\u0026quot;)\n   attempted to fix this, but introduced another bug under different\n   circumstances when two different CPUs were racing to call\n   qlt_unmap_sg() at the same time: BUG_ON(!valid_dma_direction(dir)) in\n   dma_unmap_sg_attrs().\n\nSo revert \u0026quot;scsi: qla2xxx: Fix missed DMA unmap for aborted commands\u0026quot; and\npartially revert \u0026quot;scsi: qla2xxx: target: Fix offline port handling and\nhost reset handling\u0026quot; at __qla2x00_abort_all_cmds.(CVE-2025-68745)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nblock: Use RCU in blk_mq_[un]quiesce_tagset() instead of set-\u0026gt;tag_list_lock\n\nblk_mq_{add,del}_queue_tag_set() functions add and remove queues from\ntagset, the functions make sure that tagset and queues are marked as\nshared when two or more queues are attached to the same tagset.\nInitially a tagset starts as unshared and when the number of added\nqueues reaches two, blk_mq_add_queue_tag_set() marks it as shared along\nwith all the queues attached to it. When the number of attached queues\ndrops to 1 blk_mq_del_queue_tag_set() need to mark both the tagset and\nthe remaining queues as unshared.\n\nBoth functions need to freeze current queues in tagset before setting on\nunsetting BLK_MQ_F_TAG_QUEUE_SHARED flag. While doing so, both functions\nhold set-\u0026gt;tag_list_lock mutex, which makes sense as we do not want\nqueues to be added or deleted in the process. This used to work fine\nuntil commit 98d81f0df70c (\u0026quot;nvme: use blk_mq_[un]quiesce_tagset\u0026quot;)\nmade the nvme driver quiesce tagset instead of quiscing individual\nqueues. blk_mq_quiesce_tagset() does the job and quiesce the queues in\nset-\u0026gt;tag_list while holding set-\u0026gt;tag_list_lock also.\n\nThis results in deadlock between two threads with these stacktraces:\n\n  __schedule+0x47c/0xbb0\n  ? timerqueue_add+0x66/0xb0\n  schedule+0x1c/0xa0\n  schedule_preempt_disabled+0xa/0x10\n  __mutex_lock.constprop.0+0x271/0x600\n  blk_mq_quiesce_tagset+0x25/0xc0\n  nvme_dev_disable+0x9c/0x250\n  nvme_timeout+0x1fc/0x520\n  blk_mq_handle_expired+0x5c/0x90\n  bt_iter+0x7e/0x90\n  blk_mq_queue_tag_busy_iter+0x27e/0x550\n  ? __blk_mq_complete_request_remote+0x10/0x10\n  ? __blk_mq_complete_request_remote+0x10/0x10\n  ? __call_rcu_common.constprop.0+0x1c0/0x210\n  blk_mq_timeout_work+0x12d/0x170\n  process_one_work+0x12e/0x2d0\n  worker_thread+0x288/0x3a0\n  ? rescuer_thread+0x480/0x480\n  kthread+0xb8/0xe0\n  ? kthread_park+0x80/0x80\n  ret_from_fork+0x2d/0x50\n  ? kthread_park+0x80/0x80\n  ret_from_fork_asm+0x11/0x20\n\n  __schedule+0x47c/0xbb0\n  ? xas_find+0x161/0x1a0\n  schedule+0x1c/0xa0\n  blk_mq_freeze_queue_wait+0x3d/0x70\n  ? destroy_sched_domains_rcu+0x30/0x30\n  blk_mq_update_tag_set_shared+0x44/0x80\n  blk_mq_exit_queue+0x141/0x150\n  del_gendisk+0x25a/0x2d0\n  nvme_ns_remove+0xc9/0x170\n  nvme_remove_namespaces+0xc7/0x100\n  nvme_remove+0x62/0x150\n  pci_device_remove+0x23/0x60\n  device_release_driver_internal+0x159/0x200\n  unbind_store+0x99/0xa0\n  kernfs_fop_write_iter+0x112/0x1e0\n  vfs_write+0x2b1/0x3d0\n  ksys_write+0x4e/0xb0\n  do_syscall_64+0x5b/0x160\n  entry_SYSCALL_64_after_hwframe+0x4b/0x53\n\nThe top stacktrace is showing nvme_timeout() called to handle nvme\ncommand timeout. timeout handler is trying to disable the controller and\nas a first step, it needs to blk_mq_quiesce_tagset() to tell blk-mq not\nto call queue callback handlers. The thread is stuck waiting for\nset-\u0026gt;tag_list_lock as it tries to walk the queues in set-\u0026gt;tag_list.\n\nThe lock is held by the second thread in the bottom stack which is\nwaiting for one of queues to be frozen. The queue usage counter will\ndrop to zero after nvme_timeout() finishes, and this will not happen\nbecause the thread will wait for this mutex forever.\n\nGiven that [un]quiescing queue is an operation that does not need to\nsleep, update blk_mq_[un]quiesce_tagset() to use RCU instead of taking\nset-\u0026gt;tag_list_lock, update blk_mq_{add,del}_queue_tag_set() to use RCU\nsafe list operations. Also, delete INIT_LIST_HEAD(\u0026amp;q-\u0026gt;tag_set_list)\nin blk_mq_del_queue_tag_set() because we can not re-initialize it while\nthe list is being traversed under RCU. The deleted queue will not be\nadded/deleted to/from a tagset and it will be freed in blk_free_queue()\nafter the end of RCU grace period.(CVE-2025-68756)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nsched/deadline: only set free_cpus for online runqueues\n\nCommit 16b269436b72 (\u0026quot;sched/deadline: Modify cpudl::free_cpus\nto reflect rd-\u0026gt;online\u0026quot;) introduced the cpudl_set/clear_freecpu\nfunctions to allow the cpu_dl::free_cpus mask to be manipulated\nby the deadline scheduler class rq_on/offline callbacks so the\nmask would also reflect this state.\n\nCommit 9659e1eeee28 (\u0026quot;sched/deadline: Remove cpu_active_mask\nfrom cpudl_find()\u0026quot;) removed the check of the cpu_active_mask to\nsave some processing on the premise that the cpudl::free_cpus\nmask already reflected the runqueue online state.\n\nUnfortunately, there are cases where it is possible for the\ncpudl_clear function to set the free_cpus bit for a CPU when the\ndeadline runqueue is offline. When this occurs while a CPU is\nconnected to the default root domain the flag may retain the bad\nstate after the CPU has been unplugged. Later, a different CPU\nthat is transitioning through the default root domain may push a\ndeadline task to the powered down CPU when cpudl_find sees its\nfree_cpus bit is set. If this happens the task will not have the\nopportunity to run.\n\nOne example is outlined here:\nhttps://lore.kernel.org/lkml/(CVE-2025-68780)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nscsi: target: Reset t_task_cdb pointer in error case\n\nIf allocation of cmd-\u0026gt;t_task_cdb fails, it remains NULL but is later\ndereferenced in the \u0026apos;err\u0026apos; path.\n\nIn case of error, reset NULL t_task_cdb value to point at the default\nfixed-size buffer.\n\nFound by Linux Verification Center (linuxtesting.org) with SVACE.(CVE-2025-68782)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\niomap: adjust read range correctly for non-block-aligned positions\n\niomap_adjust_read_range() assumes that the position and length passed in\nare block-aligned. This is not always the case however, as shown in the\nsyzbot generated case for erofs. This causes too many bytes to be\nskipped for uptodate blocks, which results in returning the incorrect\nposition and length to read in. If all the blocks are uptodate, this\nunderflows length and returns a position beyond the folio.\n\nFix the calculation to also take into account the block offset when\ncalculating how many bytes can be skipped for uptodate blocks.(CVE-2025-68794)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nNFSD: NFSv4 file creation neglects setting ACL\n\nAn NFSv4 client that sets an ACL with a named principal during file\ncreation retrieves the ACL afterwards, and finds that it is only a\ndefault ACL (based on the mode bits) and not the ACL that was\nrequested during file creation. This violates RFC 8881 section\n6.4.1.3: \u0026quot;the ACL attribute is set as given\u0026quot;.\n\nThe issue occurs in nfsd_create_setattr(), which calls\nnfsd_attrs_valid() to determine whether to call nfsd_setattr().\nHowever, nfsd_attrs_valid() checks only for iattr changes and\nsecurity labels, but not POSIX ACLs. When only an ACL is present,\nthe function returns false, nfsd_setattr() is skipped, and the\nPOSIX ACL is never applied to the inode.\n\nSubsequently, when the client retrieves the ACL, the server finds\nno POSIX ACL on the inode and returns one generated from the file\u0026apos;s\nmode bits rather than returning the originally-specified ACL.(CVE-2025-68803)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nio_uring: fix filename leak in __io_openat_prep()\n\n __io_openat_prep() allocates a struct filename using getname(). However,\nfor the condition of the file being installed in the fixed file table as\nwell as having O_CLOEXEC flag set, the function returns early. At that\npoint, the request doesn\u0026apos;t have REQ_F_NEED_CLEANUP flag set. Due to this,\nthe memory for the newly allocated struct filename is not cleaned up,\ncausing a memory leak.\n\nFix this by setting the REQ_F_NEED_CLEANUP for the request just after the\nsuccessful getname() call, so that when the request is torn down, the\nfilename will be cleaned up, along with other resources needing cleanup.(CVE-2025-68814)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnet/mlx5: fw_tracer, Validate format string parameters\n\nAdd validation for format string parameters in the firmware tracer to\nprevent potential security vulnerabilities and crashes from malformed\nformat strings received from firmware.\n\nThe firmware tracer receives format strings from the device firmware and\nuses them to format trace messages. Without proper validation, bad\nfirmware could provide format strings with invalid format specifiers\n(e.g., %s, %p, %n) that could lead to crashes, or other undefined\nbehavior.\n\nAdd mlx5_tracer_validate_params() to validate that all format specifiers\nin trace strings are limited to safe integer/hex formats (%x, %d, %i,\n%u, %llx, %lx, etc.). Reject strings containing other format types that\ncould be used to access arbitrary memory or cause crashes.\nInvalid format strings are added to the trace output for visibility with\n\u0026quot;BAD_FORMAT: \u0026quot; prefix.(CVE-2025-68816)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nscsi: Revert \u0026quot;scsi: qla2xxx: Perform lockless command completion in abort path\u0026quot;\n\nThis reverts commit 0367076b0817d5c75dfb83001ce7ce5c64d803a9.\n\nThe commit being reverted added code to __qla2x00_abort_all_cmds() to\ncall sp-\u0026gt;done() without holding a spinlock.  But unlike the older code\nbelow it, this new code failed to check sp-\u0026gt;cmd_type and just assumed\nTYPE_SRB, which results in a jump to an invalid pointer in target-mode\nwith TYPE_TGT_CMD:\n\nqla2xxx [0000:65:00.0]-d034:8: qla24xx_do_nack_work create sess success\n  0000000009f7a79b\nqla2xxx [0000:65:00.0]-5003:8: ISP System Error - mbx1=1ff5h mbx2=10h\n  mbx3=0h mbx4=0h mbx5=191h mbx6=0h mbx7=0h.\nqla2xxx [0000:65:00.0]-d01e:8: -\u0026gt; fwdump no buffer\nqla2xxx [0000:65:00.0]-f03a:8: qla_target(0): System error async event\n  0x8002 occurred\nqla2xxx [0000:65:00.0]-00af:8: Performing ISP error recovery -\n  ha=0000000058183fda.\nBUG: kernel NULL pointer dereference, address: 0000000000000000\nPF: supervisor instruction fetch in kernel mode\nPF: error_code(0x0010) - not-present page\nPGD 0 P4D 0\nOops: 0010 [#1] SMP\nCPU: 2 PID: 9446 Comm: qla2xxx_8_dpc Tainted: G           O       6.1.133 #1\nHardware name: Supermicro Super Server/X11SPL-F, BIOS 4.2 12/15/2023\nRIP: 0010:0x0\nCode: Unable to access opcode bytes at 0xffffffffffffffd6.\nRSP: 0018:ffffc90001f93dc8 EFLAGS: 00010206\nRAX: 0000000000000282 RBX: 0000000000000355 RCX: ffff88810d16a000\nRDX: ffff88810dbadaa8 RSI: 0000000000080000 RDI: ffff888169dc38c0\nRBP: ffff888169dc38c0 R08: 0000000000000001 R09: 0000000000000045\nR10: ffffffffa034bdf0 R11: 0000000000000000 R12: ffff88810800bb40\nR13: 0000000000001aa8 R14: ffff888100136610 R15: ffff8881070f7400\nFS:  0000000000000000(0000) GS:ffff88bf80080000(0000) knlGS:0000000000000000\nCS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033\nCR2: ffffffffffffffd6 CR3: 000000010c8ff006 CR4: 00000000003706e0\nDR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000\nDR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400\nCall Trace:\n \u0026lt;TASK\u0026gt;\n ? __die+0x4d/0x8b\n ? page_fault_oops+0x91/0x180\n ? trace_buffer_unlock_commit_regs+0x38/0x1a0\n ? exc_page_fault+0x391/0x5e0\n ? asm_exc_page_fault+0x22/0x30\n __qla2x00_abort_all_cmds+0xcb/0x3e0 [qla2xxx_scst]\n qla2x00_abort_all_cmds+0x50/0x70 [qla2xxx_scst]\n qla2x00_abort_isp_cleanup+0x3b7/0x4b0 [qla2xxx_scst]\n qla2x00_abort_isp+0xfd/0x860 [qla2xxx_scst]\n qla2x00_do_dpc+0x581/0xa40 [qla2xxx_scst]\n kthread+0xa8/0xd0\n \u0026lt;/TASK\u0026gt;\n\nThen commit 4475afa2646d (\u0026quot;scsi: qla2xxx: Complete command early within\nlock\u0026quot;) added the spinlock back, because not having the lock caused a\nrace and a crash.  But qla2x00_abort_srb() in the switch below already\nchecks for qla2x00_chip_is_down() and handles it the same way, so the\ncode above the switch is now redundant and still buggy in target-mode.\nRemove it.(CVE-2025-68818)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nshmem: fix recovery on rename failures\n\nmaple_tree insertions can fail if we are seriously short on memory;\nsimple_offset_rename() does not recover well if it runs into that.\nThe same goes for simple_offset_rename_exchange().\n\nMoreover, shmem_whiteout() expects that if it succeeds, the caller will\nprogress to d_move(), i.e. that shmem_rename2() won\u0026apos;t fail past the\nsuccessful call of shmem_whiteout().\n\nNot hard to fix, fortunately - mtree_store() can\u0026apos;t fail if the index we\nare trying to store into is already present in the tree as a singleton.\n\nFor simple_offset_rename_exchange() that\u0026apos;s enough - we just need to be\ncareful about the order of operations.\n\nFor simple_offset_rename() solution is to preinsert the target into the\ntree for new_dir; the rest can be done without any potentially failing\noperations.\n\nThat preinsertion has to be done in shmem_rename2() rather than in\nsimple_offset_rename() itself - otherwise we\u0026apos;d need to deal with the\npossibility of failure after successful shmem_whiteout().(CVE-2025-71072)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nKVM: x86: Fix VM hard lockup after prolonged inactivity with periodic HV timer\n\nWhen advancing the target expiration for the guest\u0026apos;s APIC timer in periodic\nmode, set the expiration to \u0026quot;now\u0026quot; if the target expiration is in the past\n(similar to what is done in update_target_expiration()).  Blindly adding\nthe period to the previous target expiration can result in KVM generating\na practically unbounded number of hrtimer IRQs due to programming an\nexpired timer over and over.  In extreme scenarios, e.g. if userspace\npauses/suspends a VM for an extended duration, this can even cause hard\nlockups in the host.\n\nCurrently, the bug only affects Intel CPUs when using the hypervisor timer\n(HV timer), a.k.a. the VMX preemption timer.  Unlike the software timer,\na.k.a. hrtimer, which KVM keeps running even on exits to userspace, the\nHV timer only runs while the guest is active.  As a result, if the vCPU\ndoes not run for an extended duration, there will be a huge gap between\nthe target expiration and the current time the vCPU resumes running.\nBecause the target expiration is incremented by only one period on each\ntimer expiration, this leads to a series of timer expirations occurring\nrapidly after the vCPU/VM resumes.\n\nMore critically, when the vCPU first triggers a periodic HV timer\nexpiration after resuming, advancing the expiration by only one period\nwill result in a target expiration in the past.  As a result, the delta\nmay be calculated as a negative value.  When the delta is converted into\nan absolute value (tscdeadline is an unsigned u64), the resulting value\ncan overflow what the HV timer is capable of programming.  I.e. the large\nvalue will exceed the VMX Preemption Timer\u0026apos;s maximum bit width of\ncpu_preemption_timer_multi + 32, and thus cause KVM to switch from the\nHV timer to the software timer (hrtimers).\n\nAfter switching to the software timer, periodic timer expiration callbacks\nmay be executed consecutively within a single clock interrupt handler,\nbecause hrtimers honors KVM\u0026apos;s request for an expiration in the past and\nimmediately re-invokes KVM\u0026apos;s callback after reprogramming.  And because\nthe interrupt handler runs with IRQs disabled, restarting KVM\u0026apos;s hrtimer\nover and over until the target expiration is advanced to \u0026quot;now\u0026quot; can result\nin a hard lockup.\n\nE.g. the following hard lockup was triggered in the host when running a\nWindows VM (only relevant because it used the APIC timer in periodic mode)\nafter resuming the VM from a long suspend (in the host).\n\n  NMI watchdog: Watchdog detected hard LOCKUP on cpu 45\n  ...\n  RIP: 0010:advance_periodic_target_expiration+0x4d/0x80 [kvm]\n  ...\n  RSP: 0018:ff4f88f5d98d8ef0 EFLAGS: 00000046\n  RAX: fff0103f91be678e RBX: fff0103f91be678e RCX: 00843a7d9e127bcc\n  RDX: 0000000000000002 RSI: 0052ca4003697505 RDI: ff440d5bfbdbd500\n  RBP: ff440d5956f99200 R08: ff2ff2a42deb6a84 R09: 000000000002a6c0\n  R10: 0122d794016332b3 R11: 0000000000000000 R12: ff440db1af39cfc0\n  R13: ff440db1af39cfc0 R14: ffffffffc0d4a560 R15: ff440db1af39d0f8\n  FS:  00007f04a6ffd700(0000) GS:ff440db1af380000(0000) knlGS:000000e38a3b8000\n  CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033\n  CR2: 000000d5651feff8 CR3: 000000684e038002 CR4: 0000000000773ee0\n  PKRU: 55555554\n  Call Trace:\n   \u0026lt;IRQ\u0026gt;\n   apic_timer_fn+0x31/0x50 [kvm]\n   __hrtimer_run_queues+0x100/0x280\n   hrtimer_interrupt+0x100/0x210\n   ? ttwu_do_wakeup+0x19/0x160\n   smp_apic_timer_interrupt+0x6a/0x130\n   apic_timer_interrupt+0xf/0x20\n   \u0026lt;/IRQ\u0026gt;\n\nMoreover, if the suspend duration of the virtual machine is not long enough\nto trigger a hard lockup in this scenario, since commit 98c25ead5eda\n(\u0026quot;KVM: VMX: Move preemption timer \u0026lt;=\u0026gt; hrtimer dance to common x86\u0026quot;), KVM\nwill continue using the software timer until the guest reprograms the APIC\ntimer in some way.  Since the periodic timer does not require frequent APIC\ntimer register programming, the guest may continue to use the software\ntimer in \n---truncated---(CVE-2025-71104)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nlibceph: make decode_pool() more resilient against corrupted osdmaps\n\nIf the osdmap is (maliciously) corrupted such that the encoded length\nof ceph_pg_pool envelope is less than what is expected for a particular\nencoding version, out-of-bounds reads may ensue because the only bounds\ncheck that is there is based on that length value.\n\nThis patch adds explicit bounds checks for each field that is decoded\nor skipped.(CVE-2025-71116)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ncrypto: seqiv - Do not use req-\u0026gt;iv after crypto_aead_encrypt\n\nAs soon as crypto_aead_encrypt is called, the underlying request\nmay be freed by an asynchronous completion.  Thus dereferencing\nreq-\u0026gt;iv after it returns is invalid.\n\nInstead of checking req-\u0026gt;iv against info, create a new variable\nunaligned_info and use it for that purpose instead.(CVE-2025-71131)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nKEYS: trusted: Fix a memory leak in tpm2_load_cmd\n\n\u0026apos;tpm2_load_cmd\u0026apos; allocates a tempoary blob indirectly via \u0026apos;tpm2_key_decode\u0026apos;\nbut it is not freed in the failure paths. Address this by wrapping the blob\ninto with a cleanup helper.(CVE-2025-71147)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nio_uring/poll: correctly handle io_poll_add() return value on update\n\nWhen the core of io_uring was updated to handle completions\nconsistently and with fixed return codes, the POLL_REMOVE opcode\nwith updates got slightly broken. If a POLL_ADD is pending and\nthen POLL_REMOVE is used to update the events of that request, if that\nupdate causes the POLL_ADD to now trigger, then that completion is lost\nand a CQE is never posted.\n\nAdditionally, ensure that if an update does cause an existing POLL_ADD\nto complete, that the completion value isn\u0026apos;t always overwritten with\n-ECANCELED. For that case, whatever io_poll_add() set the value to\nshould just be retained.(CVE-2025-71149)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nksmbd: Fix refcount leak when invalid session is found on session lookup\n\nWhen a session is found but its state is not SMB2_SESSION_VALID, It\nindicates that no valid session was found, but it is missing to decrement\nthe reference count acquired by the session lookup, which results in\na reference count leak. This patch fixes the issue by explicitly calling\nksmbd_user_session_put to release the reference to the session.(CVE-2025-71150)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnet/mlx5e: Don\u0026apos;t store mlx5e_priv in mlx5e_dev devlink priv\n\nmlx5e_priv is an unstable structure that can be memset(0) if profile\nattaching fails, mlx5e_priv in mlx5e_dev devlink private is used to\nreference the netdev and mdev associated with that struct. Instead,\nstore netdev directly into mlx5e_dev and get mdev from the containing\nmlx5_adev aux device structure.\n\nThis fixes a kernel oops in mlx5e_remove when switchdev mode fails due\nto change profile failure.\n\n$ devlink dev eswitch set pci/0000:00:03.0 mode switchdev\nError: mlx5_core: Failed setting eswitch to offloads.\ndmesg:\nworkqueue: Failed to create a rescuer kthread for wq \u0026quot;mlx5e\u0026quot;: -EINTR\nmlx5_core 0012:03:00.1: mlx5e_netdev_init_profile:6214:(pid 37199): mlx5e_priv_init failed, err=-12\nmlx5_core 0012:03:00.1 gpu3rdma1: mlx5e_netdev_change_profile: new profile init failed, -12\nworkqueue: Failed to create a rescuer kthread for wq \u0026quot;mlx5e\u0026quot;: -EINTR\nmlx5_core 0012:03:00.1: mlx5e_netdev_init_profile:6214:(pid 37199): mlx5e_priv_init failed, err=-12\nmlx5_core 0012:03:00.1 gpu3rdma1: mlx5e_netdev_change_profile: failed to rollback to orig profile, -12\n\n$ devlink dev reload pci/0000:00:03.0 ==\u0026gt; oops\n\nBUG: kernel NULL pointer dereference, address: 0000000000000520\n #PF: supervisor read access in kernel mode\n #PF: error_code(0x0000) - not-present page\nPGD 0 P4D 0\nOops: Oops: 0000 [#1] SMP NOPTI\nCPU: 3 UID: 0 PID: 521 Comm: devlink Not tainted 6.18.0-rc5+ #117 PREEMPT(voluntary)\nHardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.16.3-2.fc40 04/01/2014\nRIP: 0010:mlx5e_remove+0x68/0x130\nRSP: 0018:ffffc900034838f0 EFLAGS: 00010246\nRAX: ffff88810283c380 RBX: ffff888101874400 RCX: ffffffff826ffc45\nRDX: 0000000000000000 RSI: 0000000000000001 RDI: 0000000000000000\nRBP: ffff888102d789c0 R08: ffff8881007137f0 R09: ffff888100264e10\nR10: ffffc90003483898 R11: ffffc900034838a0 R12: ffff888100d261a0\nR13: ffff888100d261a0 R14: ffff8881018749a0 R15: ffff888101874400\nFS:  00007f8565fea740(0000) GS:ffff88856a759000(0000) knlGS:0000000000000000\nCS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033\nCR2: 0000000000000520 CR3: 000000010b11a004 CR4: 0000000000370ef0\nCall Trace:\n \u0026lt;TASK\u0026gt;\n device_release_driver_internal+0x19c/0x200\n bus_remove_device+0xc6/0x130\n device_del+0x160/0x3d0\n ? devl_param_driverinit_value_get+0x2d/0x90\n mlx5_detach_device+0x89/0xe0\n mlx5_unload_one_devl_locked+0x3a/0x70\n mlx5_devlink_reload_down+0xc8/0x220\n devlink_reload+0x7d/0x260\n devlink_nl_reload_doit+0x45b/0x5a0\n genl_family_rcv_msg_doit+0xe8/0x140(CVE-2026-22996)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnvme-tcp: fix NULL pointer dereferences in nvmet_tcp_build_pdu_iovec\n\nCommit efa56305908b (\u0026quot;nvmet-tcp: Fix a kernel panic when host sends an invalid H2C PDU length\u0026quot;)\nadded ttag bounds checking and data_offset\nvalidation in nvmet_tcp_handle_h2c_data_pdu(), but it did not validate\nwhether the command\u0026apos;s data structures (cmd-\u0026gt;req.sg and cmd-\u0026gt;iov) have\nbeen properly initialized before processing H2C_DATA PDUs.\n\nThe nvmet_tcp_build_pdu_iovec() function dereferences these pointers\nwithout NULL checks. This can be triggered by sending H2C_DATA PDU\nimmediately after the ICREQ/ICRESP handshake, before\nsending a CONNECT command or NVMe write command.\n\nAttack vectors that trigger NULL pointer dereferences:\n1. H2C_DATA PDU sent before CONNECT → both pointers NULL\n2. H2C_DATA PDU for READ command → cmd-\u0026gt;req.sg allocated, cmd-\u0026gt;iov NULL\n3. H2C_DATA PDU for uninitialized command slot → both pointers NULL\n\nThe fix validates both cmd-\u0026gt;req.sg and cmd-\u0026gt;iov before calling\nnvmet_tcp_build_pdu_iovec(). Both checks are required because:\n- Uninitialized commands: both NULL\n- READ commands: cmd-\u0026gt;req.sg allocated, cmd-\u0026gt;iov NULL\n- WRITE commands: both allocated(CVE-2026-22998)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnet/mlx5e: Fix crash on profile change rollback failure\n\nmlx5e_netdev_change_profile can fail to attach a new profile and can\nfail to rollback to old profile, in such case, we could end up with a\ndangling netdev with a fully reset netdev_priv. A retry to change\nprofile, e.g. another attempt to call mlx5e_netdev_change_profile via\nswitchdev mode change, will crash trying to access the now NULL\npriv-\u0026gt;mdev.\n\nThis fix allows mlx5e_netdev_change_profile() to handle previous\nfailures and an empty priv, by not assuming priv is valid.\n\nPass netdev and mdev to all flows requiring\nmlx5e_netdev_change_profile() and avoid passing priv.\nIn mlx5e_netdev_change_profile() check if current priv is valid, and if\nnot, just attach the new profile without trying to access the old one.\n\nThis fixes the following oops, when enabling switchdev mode for the 2nd\ntime after first time failure:\n\n ## Enabling switchdev mode first time:\n\nmlx5_core 0012:03:00.1: E-Switch: Supported tc chains and prios offload\nworkqueue: Failed to create a rescuer kthread for wq \u0026quot;mlx5e\u0026quot;: -EINTR\nmlx5_core 0012:03:00.1: mlx5e_netdev_init_profile:6214:(pid 37199): mlx5e_priv_init failed, err=-12\nmlx5_core 0012:03:00.1 gpu3rdma1: mlx5e_netdev_change_profile: new profile init failed, -12\nworkqueue: Failed to create a rescuer kthread for wq \u0026quot;mlx5e\u0026quot;: -EINTR\nmlx5_core 0012:03:00.1: mlx5e_netdev_init_profile:6214:(pid 37199): mlx5e_priv_init failed, err=-12\nmlx5_core 0012:03:00.1 gpu3rdma1: mlx5e_netdev_change_profile: failed to rollback to orig profile, -12\n                                                                         ^^^^^^^^\nmlx5_core 0000:00:03.0: E-Switch: Disable: mode(LEGACY), nvfs(0), necvfs(0), active vports(0)\n\n ## retry: Enabling switchdev mode 2nd time:\n\nmlx5_core 0000:00:03.0: E-Switch: Supported tc chains and prios offload\nBUG: kernel NULL pointer dereference, address: 0000000000000038\n #PF: supervisor read access in kernel mode\n #PF: error_code(0x0000) - not-present page\nPGD 0 P4D 0\nOops: Oops: 0000 [#1] SMP NOPTI\nCPU: 13 UID: 0 PID: 520 Comm: devlink Not tainted 6.18.0-rc4+ #91 PREEMPT(voluntary)\nHardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.16.3-2.fc40 04/01/2014\nRIP: 0010:mlx5e_detach_netdev+0x3c/0x90\nCode: 50 00 00 f0 80 4f 78 02 48 8b bf e8 07 00 00 48 85 ff 74 16 48 8b 73 78 48 d1 ee 83 e6 01 83 f6 01 40 0f b6 f6 e8 c4 42 00 00 \u0026lt;48\u0026gt; 8b 45 38 48 85 c0 74 08 48 89 df e8 cc 47 40 1e 48 8b bb f0 07\nRSP: 0018:ffffc90000673890 EFLAGS: 00010246\nRAX: 0000000000000000 RBX: ffff8881036a89c0 RCX: 0000000000000000\nRDX: ffff888113f63800 RSI: ffffffff822fe720 RDI: 0000000000000000\nRBP: 0000000000000000 R08: 0000000000002dcd R09: 0000000000000000\nR10: ffffc900006738e8 R11: 00000000ffffffff R12: 0000000000000000\nR13: 0000000000000000 R14: ffff8881036a89c0 R15: 0000000000000000\nFS:  00007fdfb8384740(0000) GS:ffff88856a9d6000(0000) knlGS:0000000000000000\nCS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033\nCR2: 0000000000000038 CR3: 0000000112ae0005 CR4: 0000000000370ef0\nCall Trace:\n \u0026lt;TASK\u0026gt;\n mlx5e_netdev_change_profile+0x45/0xb0\n mlx5e_vport_rep_load+0x27b/0x2d0\n mlx5_esw_offloads_rep_load+0x72/0xf0\n esw_offloads_enable+0x5d0/0x970\n mlx5_eswitch_enable_locked+0x349/0x430\n ? is_mp_supported+0x57/0xb0\n mlx5_devlink_eswitch_mode_set+0x26b/0x430\n devlink_nl_eswitch_set_doit+0x6f/0xf0\n genl_family_rcv_msg_doit+0xe8/0x140\n genl_rcv_msg+0x18b/0x290\n ? __pfx_devlink_nl_pre_doit+0x10/0x10\n ? __pfx_devlink_nl_eswitch_set_doit+0x10/0x10\n ? __pfx_devlink_nl_post_doit+0x10/0x10\n ? __pfx_genl_rcv_msg+0x10/0x10\n netlink_rcv_skb+0x52/0x100\n genl_rcv+0x28/0x40\n netlink_unicast+0x282/0x3e0\n ? __alloc_skb+0xd6/0x190\n netlink_sendmsg+0x1f7/0x430\n __sys_sendto+0x213/0x220\n ? __sys_recvmsg+0x6a/0xd0\n __x64_sys_sendto+0x24/0x30\n do_syscall_64+0x50/0x1f0\n entry_SYSCALL_64_after_hwframe+0x76/0x7e\nRIP: 0033:0x7fdfb8495047(CVE-2026-23000)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nx86/fpu: Clear XSTATE_BV[i] in guest XSAVE state whenever XFD[i]=1\n\nWhen loading guest XSAVE state via KVM_SET_XSAVE, and when updating XFD in\nresponse to a guest WRMSR, clear XFD-disabled features in the saved (or to\nbe restored) XSTATE_BV to ensure KVM doesn\u0026apos;t attempt to load state for\nfeatures that are disabled via the guest\u0026apos;s XFD.  Because the kernel\nexecutes XRSTOR with the guest\u0026apos;s XFD, saving XSTATE_BV[i]=1 with XFD[i]=1\nwill cause XRSTOR to #NM and panic the kernel.\n\nE.g. if fpu_update_guest_xfd() sets XFD without clearing XSTATE_BV:\n\n  ------------[ cut here ]------------\n  WARNING: arch/x86/kernel/traps.c:1524 at exc_device_not_available+0x101/0x110, CPU#29: amx_test/848\n  Modules linked in: kvm_intel kvm irqbypass\n  CPU: 29 UID: 1000 PID: 848 Comm: amx_test Not tainted 6.19.0-rc2-ffa07f7fd437-x86_amx_nm_xfd_non_init-vm #171 NONE\n  Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 0.0.0 02/06/2015\n  RIP: 0010:exc_device_not_available+0x101/0x110\n  Call Trace:\n   \u0026lt;TASK\u0026gt;\n   asm_exc_device_not_available+0x1a/0x20\n  RIP: 0010:restore_fpregs_from_fpstate+0x36/0x90\n   switch_fpu_return+0x4a/0xb0\n   kvm_arch_vcpu_ioctl_run+0x1245/0x1e40 [kvm]\n   kvm_vcpu_ioctl+0x2c3/0x8f0 [kvm]\n   __x64_sys_ioctl+0x8f/0xd0\n   do_syscall_64+0x62/0x940\n   entry_SYSCALL_64_after_hwframe+0x4b/0x53\n   \u0026lt;/TASK\u0026gt;\n  ---[ end trace 0000000000000000 ]---\n\nThis can happen if the guest executes WRMSR(MSR_IA32_XFD) to set XFD[18] = 1,\nand a host IRQ triggers kernel_fpu_begin() prior to the vmexit handler\u0026apos;s\ncall to fpu_update_guest_xfd().\n\nand if userspace stuffs XSTATE_BV[i]=1 via KVM_SET_XSAVE:\n\n  ------------[ cut here ]------------\n  WARNING: arch/x86/kernel/traps.c:1524 at exc_device_not_available+0x101/0x110, CPU#14: amx_test/867\n  Modules linked in: kvm_intel kvm irqbypass\n  CPU: 14 UID: 1000 PID: 867 Comm: amx_test Not tainted 6.19.0-rc2-2dace9faccd6-x86_amx_nm_xfd_non_init-vm #168 NONE\n  Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 0.0.0 02/06/2015\n  RIP: 0010:exc_device_not_available+0x101/0x110\n  Call Trace:\n   \u0026lt;TASK\u0026gt;\n   asm_exc_device_not_available+0x1a/0x20\n  RIP: 0010:restore_fpregs_from_fpstate+0x36/0x90\n   fpu_swap_kvm_fpstate+0x6b/0x120\n   kvm_load_guest_fpu+0x30/0x80 [kvm]\n   kvm_arch_vcpu_ioctl_run+0x85/0x1e40 [kvm]\n   kvm_vcpu_ioctl+0x2c3/0x8f0 [kvm]\n   __x64_sys_ioctl+0x8f/0xd0\n   do_syscall_64+0x62/0x940\n   entry_SYSCALL_64_after_hwframe+0x4b/0x53\n   \u0026lt;/TASK\u0026gt;\n  ---[ end trace 0000000000000000 ]---\n\nThe new behavior is consistent with the AMX architecture.  Per Intel\u0026apos;s SDM,\nXSAVE saves XSTATE_BV as \u0026apos;0\u0026apos; for components that are disabled via XFD\n(and non-compacted XSAVE saves the initial configuration of the state\ncomponent):\n\n  If XSAVE, XSAVEC, XSAVEOPT, or XSAVES is saving the state component i,\n  the instruction does not generate #NM when XCR0[i] = IA32_XFD[i] = 1;\n  instead, it operates as if XINUSE[i] = 0 (and the state component was\n  in its initial state): it saves bit i of XSTATE_BV field of the XSAVE\n  header as 0; in addition, XSAVE saves the initial configuration of the\n  state component (the other instructions do not save state component i).\n\nAlternatively, KVM could always do XRSTOR with XFD=0, e.g. by using\na constant XFD based on the set of enabled features when XSAVEing for\na struct fpu_guest.  However, having XSTATE_BV[i]=1 for XFD-disabled\nfeatures can only happen in the above interrupt case, or in similar\nscenarios involving preemption on preemptible kernels, because\nfpu_swap_kvm_fpstate()\u0026apos;s call to save_fpregs_to_fpstate() saves the\noutgoing FPU state with the current XFD; and that is (on all but the\nfirst WRMSR to XFD) the guest XFD.\n\nTherefore, XFD can only go out of sync with XSTATE_BV in the above\ninterrupt case, or in similar scenarios involving preemption on\npreemptible kernels, and it we can consider it (de facto) part of KVM\nABI that KVM_GET_XSAVE returns XSTATE_BV[i]=0 for XFD-disabled features.\n\n[Move clea\n---truncated---(CVE-2026-23005)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnet/mlx5e: Pass netdev to mlx5e_destroy_netdev instead of priv\n\nmlx5e_priv is an unstable structure that can be memset(0) if profile\nattaching fails.\n\nPass netdev to mlx5e_destroy_netdev() to guarantee it will work on a\nvalid netdev.\n\nOn mlx5e_remove: Check validity of priv-\u0026gt;profile, before attempting\nto cleanup any resources that might be not there.\n\nThis fixes a kernel oops in mlx5e_remove when switchdev mode fails due\nto change profile failure.\n\n$ devlink dev eswitch set pci/0000:00:03.0 mode switchdev\nError: mlx5_core: Failed setting eswitch to offloads.\ndmesg:\nworkqueue: Failed to create a rescuer kthread for wq \u0026quot;mlx5e\u0026quot;: -EINTR\nmlx5_core 0012:03:00.1: mlx5e_netdev_init_profile:6214:(pid 37199): mlx5e_priv_init failed, err=-12\nmlx5_core 0012:03:00.1 gpu3rdma1: mlx5e_netdev_change_profile: new profile init failed, -12\nworkqueue: Failed to create a rescuer kthread for wq \u0026quot;mlx5e\u0026quot;: -EINTR\nmlx5_core 0012:03:00.1: mlx5e_netdev_init_profile:6214:(pid 37199): mlx5e_priv_init failed, err=-12\nmlx5_core 0012:03:00.1 gpu3rdma1: mlx5e_netdev_change_profile: failed to rollback to orig profile, -12\n\n$ devlink dev reload pci/0000:00:03.0 ==\u0026gt; oops\n\nBUG: kernel NULL pointer dereference, address: 0000000000000370\nPGD 0 P4D 0\nOops: Oops: 0000 [#1] SMP NOPTI\nCPU: 15 UID: 0 PID: 520 Comm: devlink Not tainted 6.18.0-rc5+ #115 PREEMPT(voluntary)\nHardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.16.3-2.fc40 04/01/2014\nRIP: 0010:mlx5e_dcbnl_dscp_app+0x23/0x100\nRSP: 0018:ffffc9000083f8b8 EFLAGS: 00010286\nRAX: ffff8881126fc380 RBX: ffff8881015ac400 RCX: ffffffff826ffc45\nRDX: 0000000000000000 RSI: 0000000000000001 RDI: ffff8881035109c0\nRBP: ffff8881035109c0 R08: ffff888101e3e838 R09: ffff888100264e10\nR10: ffffc9000083f898 R11: ffffc9000083f8a0 R12: ffff888101b921a0\nR13: ffff888101b921a0 R14: ffff8881015ac9a0 R15: ffff8881015ac400\nFS:  00007f789a3c8740(0000) GS:ffff88856aa59000(0000) knlGS:0000000000000000\nCS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033\nCR2: 0000000000000370 CR3: 000000010b6c0001 CR4: 0000000000370ef0\nCall Trace:\n \u0026lt;TASK\u0026gt;\n mlx5e_remove+0x57/0x110\n device_release_driver_internal+0x19c/0x200\n bus_remove_device+0xc6/0x130\n device_del+0x160/0x3d0\n ? devl_param_driverinit_value_get+0x2d/0x90\n mlx5_detach_device+0x89/0xe0\n mlx5_unload_one_devl_locked+0x3a/0x70\n mlx5_devlink_reload_down+0xc8/0x220\n devlink_reload+0x7d/0x260\n devlink_nl_reload_doit+0x45b/0x5a0\n genl_family_rcv_msg_doit+0xe8/0x140(CVE-2026-23035)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ntracing: Add recursion protection in kernel stack trace recording\n\nA bug was reported about an infinite recursion caused by tracing the rcu\nevents with the kernel stack trace trigger enabled. The stack trace code\ncalled back into RCU which then called the stack trace again.\n\nExpand the ftrace recursion protection to add a set of bits to protect\nevents from recursion. Each bit represents the context that the event is\nin (normal, softirq, interrupt and NMI).\n\nHave the stack trace code use the interrupt context to protect against\nrecursion.\n\nNote, the bug showed an issue in both the RCU code as well as the tracing\nstacktrace code. This only handles the tracing stack trace side of the\nbug. The RCU fix will be handled separately.(CVE-2026-23138)","status":"published","published":"2026-03-27T11:10:47Z","modified":"2026-08-18T01:19:44.306450654Z","cvss":[{"version":"3.1","score":7.8,"vector":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H","level":"high"}],"updated_at":"2026-11-02T15:52:45.721983Z"},{"id":"OESA-2026-1760","title":"kernel security update","description":"The Linux Kernel, the operating system core itself.\r\n\r\nSecurity Fix(es):\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\niommu/s390: Implement blocking domain\n\nThis fixes a crash when surprise hot-unplugging a PCI device. This crash\nhappens because during hot-unplug __iommu_group_set_domain_nofail()\nattaching the default domain fails when the platform no longer\nrecognizes the device as it has already been removed and we end up with\na NULL domain pointer and UAF. This is exactly the case referred to in\nthe second comment in __iommu_device_set_domain() and just as stated\nthere if we can instead attach the blocking domain the UAF is prevented\nas this can handle the already removed device. Implement the blocking\ndomain to use this handling.  With this change, the crash is fixed but\nwe still hit a warning attempting to change DMA ownership on a blocked\ndevice.(CVE-2024-53232)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\niommu: Fix two issues in iommu_copy_struct_from_user()\n\nIn the review for iommu_copy_struct_to_user() helper, Matt pointed out that\na NULL pointer should be rejected prior to dereferencing it:\nhttps://lore.kernel.org/all/(CVE-2025-37900)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nsmb: client: Avoid race in open_cached_dir with lease breaks\n\nA pre-existing valid cfid returned from find_or_create_cached_dir might\nrace with a lease break, meaning open_cached_dir doesn\u0026apos;t consider it\nvalid, and thinks it\u0026apos;s newly-constructed. This leaks a dentry reference\nif the allocation occurs before the queued lease break work runs.\n\nAvoid the race by extending holding the cfid_list_lock across\nfind_or_create_cached_dir and when the result is checked.(CVE-2025-37954)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnet_sched: prio: fix a race in prio_tune()\n\nGerrard Tai reported a race condition in PRIO, whenever SFQ perturb timer\nfires at the wrong time.\n\nThe race is as follows:\n\nCPU 0                                 CPU 1\n[1]: lock root\n[2]: qdisc_tree_flush_backlog()\n[3]: unlock root\n |\n |                                    [5]: lock root\n |                                    [6]: rehash\n |                                    [7]: qdisc_tree_reduce_backlog()\n |\n[4]: qdisc_put()\n\nThis can be abused to underflow a parent\u0026apos;s qlen.\n\nCalling qdisc_purge_queue() instead of qdisc_tree_flush_backlog()\nshould fix the race, because all packets will be purged from the qdisc\nbefore releasing the lock.(CVE-2025-38083)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nIB/mlx5: Fix potential deadlock in MR deregistration\n\nThe issue arises when kzalloc() is invoked while holding umem_mutex or\nany other lock acquired under umem_mutex. This is problematic because\nkzalloc() can trigger fs_reclaim_aqcuire(), which may, in turn, invoke\nmmu_notifier_invalidate_range_start(). This function can lead to\nmlx5_ib_invalidate_range(), which attempts to acquire umem_mutex again,\nresulting in a deadlock.\n\nThe problematic flow:\n             CPU0                      |              CPU1\n---------------------------------------|------------------------------------------------\nmlx5_ib_dereg_mr()                     |\n → revoke_mr()                         |\n   → mutex_lock(\u0026amp;umem_odp-\u0026gt;umem_mutex) |\n                                       | mlx5_mkey_cache_init()\n                                       |  → mutex_lock(\u0026amp;dev-\u0026gt;cache.rb_lock)\n                                       |  → mlx5r_cache_create_ent_locked()\n                                       |    → kzalloc(GFP_KERNEL)\n                                       |      → fs_reclaim()\n                                       |        → mmu_notifier_invalidate_range_start()\n                                       |          → mlx5_ib_invalidate_range()\n                                       |            → mutex_lock(\u0026amp;umem_odp-\u0026gt;umem_mutex)\n   → cache_ent_find_and_store()        |\n     → mutex_lock(\u0026amp;dev-\u0026gt;cache.rb_lock) |\n\nAdditionally, when kzalloc() is called from within\ncache_ent_find_and_store(), we encounter the same deadlock due to\nre-acquisition of umem_mutex.\n\nSolve by releasing umem_mutex in dereg_mr() after umr_revoke_mr()\nand before acquiring rb_lock. This ensures that we don\u0026apos;t hold\numem_mutex while performing memory allocations that could trigger\nthe reclaim path.\n\nThis change prevents the deadlock by ensuring proper lock ordering and\navoiding holding locks during memory allocation operations that could\ntrigger the reclaim path.\n\nThe following lockdep warning demonstrates the deadlock:\n\n python3/20557 is trying to acquire lock:\n ffff888387542128 (\u0026amp;umem_odp-\u0026gt;umem_mutex){+.+.}-{4:4}, at:\n mlx5_ib_invalidate_range+0x5b/0x550 [mlx5_ib]\n\n but task is already holding lock:\n ffffffff82f6b840 (mmu_notifier_invalidate_range_start){+.+.}-{0:0}, at:\n unmap_vmas+0x7b/0x1a0\n\n which lock already depends on the new lock.\n\n the existing dependency chain (in reverse order) is:\n\n -\u0026gt; #3 (mmu_notifier_invalidate_range_start){+.+.}-{0:0}:\n       fs_reclaim_acquire+0x60/0xd0\n       mem_cgroup_css_alloc+0x6f/0x9b0\n       cgroup_init_subsys+0xa4/0x240\n       cgroup_init+0x1c8/0x510\n       start_kernel+0x747/0x760\n       x86_64_start_reservations+0x25/0x30\n       x86_64_start_kernel+0x73/0x80\n       common_startup_64+0x129/0x138\n\n -\u0026gt; #2 (fs_reclaim){+.+.}-{0:0}:\n       fs_reclaim_acquire+0x91/0xd0\n       __kmalloc_cache_noprof+0x4d/0x4c0\n       mlx5r_cache_create_ent_locked+0x75/0x620 [mlx5_ib]\n       mlx5_mkey_cache_init+0x186/0x360 [mlx5_ib]\n       mlx5_ib_stage_post_ib_reg_umr_init+0x3c/0x60 [mlx5_ib]\n       __mlx5_ib_add+0x4b/0x190 [mlx5_ib]\n       mlx5r_probe+0xd9/0x320 [mlx5_ib]\n       auxiliary_bus_probe+0x42/0x70\n       really_probe+0xdb/0x360\n       __driver_probe_device+0x8f/0x130\n       driver_probe_device+0x1f/0xb0\n       __driver_attach+0xd4/0x1f0\n       bus_for_each_dev+0x79/0xd0\n       bus_add_driver+0xf0/0x200\n       driver_register+0x6e/0xc0\n       __auxiliary_driver_register+0x6a/0xc0\n       do_one_initcall+0x5e/0x390\n       do_init_module+0x88/0x240\n       init_module_from_file+0x85/0xc0\n       idempotent_init_module+0x104/0x300\n       __x64_sys_finit_module+0x68/0xc0\n       do_syscall_64+0x6d/0x140\n       entry_SYSCALL_64_after_hwframe+0x4b/0x53\n\n -\u0026gt; #1 (\u0026amp;dev-\u0026gt;cache.rb_lock){+.+.}-{4:4}:\n       __mutex_lock+0x98/0xf10\n       __mlx5_ib_dereg_mr+0x6f2/0x890 [mlx5_ib]\n       mlx5_ib_dereg_mr+0x21/0x110 [mlx5_ib]\n       ib_dereg_mr_user+0x85/0x1f0 [ib_core]\n  \n---truncated---(CVE-2025-38373)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nHID: core: Harden s32ton() against conversion to 0 bits\n\nTesting by the syzbot fuzzer showed that the HID core gets a\nshift-out-of-bounds exception when it tries to convert a 32-bit\nquantity to a 0-bit quantity.  Ideally this should never occur, but\nthere are buggy devices and some might have a report field with size\nset to zero; we shouldn\u0026apos;t reject the report or the device just because\nof that.\n\nInstead, harden the s32ton() routine so that it returns a reasonable\nresult instead of crashing when it is called with the number of bits\nset to 0 -- the same as what snto32() does.(CVE-2025-38556)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nbpf: Reject narrower access to pointer ctx fields\n\nThe following BPF program, simplified from a syzkaller repro, causes a\nkernel warning:\n\n    r0 = *(u8 *)(r1 + 169);\n    exit;\n\nWith pointer field sk being at offset 168 in __sk_buff. This access is\ndetected as a narrower read in bpf_skb_is_valid_access because it\ndoesn\u0026apos;t match offsetof(struct __sk_buff, sk). It is therefore allowed\nand later proceeds to bpf_convert_ctx_access. Note that for the\n\u0026quot;is_narrower_load\u0026quot; case in the convert_ctx_accesses(), the insn-\u0026gt;off\nis aligned, so the cnt may not be 0 because it matches the\noffsetof(struct __sk_buff, sk) in the bpf_convert_ctx_access. However,\nthe target_size stays 0 and the verifier errors with a kernel warning:\n\n    verifier bug: error during ctx access conversion(1)\n\nThis patch fixes that to return a proper \u0026quot;invalid bpf_context access\noff=X size=Y\u0026quot; error on the load instruction.\n\nThe same issue affects multiple other fields in context structures that\nallow narrow access. Some other non-affected fields (for sk_msg,\nsk_lookup, and sockopt) were also changed to use bpf_ctx_range_ptr for\nconsistency.\n\nNote this syzkaller crash was reported in the \u0026quot;Closes\u0026quot; link below, which\nused to be about a different bug, fixed in\ncommit fce7bd8e385a (\u0026quot;bpf/verifier: Handle BPF_LOAD_ACQ instructions\nin insn_def_regno()\u0026quot;). Because syzbot somehow confused the two bugs,\nthe new crash and repro didn\u0026apos;t get reported to the mailing list.(CVE-2025-38591)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ngfs2: No more self recovery\n\nWhen a node withdraws and it turns out that it is the only node that has\nthe filesystem mounted, gfs2 currently tries to replay the local journal\nto bring the filesystem back into a consistent state.  Not only is that\na very bad idea, it has also never worked because gfs2_recover_func()\nwill refuse to do anything during a withdraw.\n\nHowever, before even getting to this point, gfs2_recover_func()\ndereferences sdp-\u0026gt;sd_jdesc-\u0026gt;jd_inode.  This was a use-after-free before\ncommit 04133b607a78 (\u0026quot;gfs2: Prevent double iput for journal on error\u0026quot;)\nand is a NULL pointer dereference since then.\n\nSimply get rid of self recovery to fix that.(CVE-2025-38659)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nio_uring/net: commit partial buffers on retry\n\nRing provided buffers are potentially only valid within the single\nexecution context in which they were acquired. io_uring deals with this\nand invalidates them on retry. But on the networking side, if\nMSG_WAITALL is set, or if the socket is of the streaming type and too\nlittle was processed, then it will hang on to the buffer rather than\nrecycle or commit it. This is problematic for two reasons:\n\n1) If someone unregisters the provided buffer ring before a later retry,\n   then the req-\u0026gt;buf_list will no longer be valid.\n\n2) If multiple sockers are using the same buffer group, then multiple\n   receives can consume the same memory. This can cause data corruption\n   in the application, as either receive could land in the same\n   userspace buffer.\n\nFix this by disallowing partial retries from pinning a provided buffer\nacross multiple executions, if ring provided buffers are used.(CVE-2025-38730)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nmedia: rainshadow-cec: fix TOCTOU race condition in rain_interrupt()\n\nIn the interrupt handler rain_interrupt(), the buffer full check on\nrain-\u0026gt;buf_len is performed before acquiring rain-\u0026gt;buf_lock. This\ncreates a Time-of-Check to Time-of-Use (TOCTOU) race condition, as\nrain-\u0026gt;buf_len is concurrently accessed and modified in the work\nhandler rain_irq_work_handler() under the same lock.\n\nMultiple interrupt invocations can race, with each reading buf_len\nbefore it becomes full and then proceeding. This can lead to both\ninterrupts attempting to write to the buffer, incrementing buf_len\nbeyond its capacity (DATA_SIZE) and causing a buffer overflow.\n\nFix this bug by moving the spin_lock() to before the buffer full\ncheck. This ensures that the check and the subsequent buffer modification\nare performed atomically, preventing the race condition. An corresponding\nspin_unlock() is added to the overflow path to correctly release the\nlock.\n\nThis possible bug was found by an experimental static analysis tool\ndeveloped by our team.(CVE-2025-39713)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\niommu/amd/pgtbl: Fix possible race while increase page table level\n\nThe AMD IOMMU host page table implementation supports dynamic page table levels\n(up to 6 levels), starting with a 3-level configuration that expands based on\nIOVA address. The kernel maintains a root pointer and current page table level\nto enable proper page table walks in alloc_pte()/fetch_pte() operations.\n\nThe IOMMU IOVA allocator initially starts with 32-bit address and onces its\nexhuasted it switches to 64-bit address (max address is determined based\non IOMMU and device DMA capability). To support larger IOVA, AMD IOMMU\ndriver increases page table level.\n\nBut in unmap path (iommu_v1_unmap_pages()), fetch_pte() reads\npgtable-\u0026gt;[root/mode] without lock. So its possible that in exteme corner case,\nwhen increase_address_space() is updating pgtable-\u0026gt;[root/mode], fetch_pte()\nreads wrong page table level (pgtable-\u0026gt;mode). It does compare the value with\nlevel encoded in page table and returns NULL. This will result is\niommu_unmap ops to fail and upper layer may retry/log WARN_ON.\n\nCPU 0                                         CPU 1\n------                                       ------\nmap pages                                    unmap pages\nalloc_pte() -\u0026gt; increase_address_space()      iommu_v1_unmap_pages() -\u0026gt; fetch_pte()\n  pgtable-\u0026gt;root = pte (new root value)\n                                             READ pgtable-\u0026gt;[mode/root]\n\t\t\t\t\t       Reads new root, old mode\n  Updates mode (pgtable-\u0026gt;mode += 1)\n\nSince Page table level updates are infrequent and already synchronized with a\nspinlock, implement seqcount to enable lock-free read operations on the read path.(CVE-2025-39961)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\npinctrl: check the return value of pinmux_ops::get_function_name()\n\nWhile the API contract in docs doesn\u0026apos;t specify it explicitly, the\ngeneric implementation of the get_function_name() callback from struct\npinmux_ops - pinmux_generic_get_function_name() - can fail and return\nNULL. This is already checked in pinmux_check_ops() so add a similar\ncheck in pinmux_func_name_to_selector() instead of passing the returned\npointer right down to strcmp() where the NULL can get dereferenced. This\nis normal operation when adding new pinfunctions.(CVE-2025-40030)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ndrm/sched: Fix potential double free in drm_sched_job_add_resv_dependencies\n\nWhen adding dependencies with drm_sched_job_add_dependency(), that\nfunction consumes the fence reference both on success and failure, so in\nthe latter case the dma_fence_put() on the error path (xarray failed to\nexpand) is a double free.\n\nInterestingly this bug appears to have been present ever since\ncommit ebd5f74255b9 (\u0026quot;drm/sched: Add dependency tracking\u0026quot;), since the code\nback then looked like this:\n\ndrm_sched_job_add_implicit_dependencies():\n...\n       for (i = 0; i \u0026lt; fence_count; i++) {\n               ret = drm_sched_job_add_dependency(job, fences[i]);\n               if (ret)\n                       break;\n       }\n\n       for (; i \u0026lt; fence_count; i++)\n               dma_fence_put(fences[i]);\n\nWhich means for the failing \u0026apos;i\u0026apos; the dma_fence_put was already a double\nfree. Possibly there were no users at that time, or the test cases were\ninsufficient to hit it.\n\nThe bug was then only noticed and fixed after\ncommit 9c2ba265352a (\u0026quot;drm/scheduler: use new iterator in drm_sched_job_add_implicit_dependencies v2\u0026quot;)\nlanded, with its fixup of\ncommit 4eaf02d6076c (\u0026quot;drm/scheduler: fix drm_sched_job_add_implicit_dependencies\u0026quot;).\n\nAt that point it was a slightly different flavour of a double free, which\ncommit 963d0b356935 (\u0026quot;drm/scheduler: fix drm_sched_job_add_implicit_dependencies harder\u0026quot;)\nnoticed and attempted to fix.\n\nBut it only moved the double free from happening inside the\ndrm_sched_job_add_dependency(), when releasing the reference not yet\nobtained, to the caller, when releasing the reference already released by\nthe former in the failure case.\n\nAs such it is not easy to identify the right target for the fixes tag so\nlets keep it simple and just continue the chain.\n\nWhile fixing we also improve the comment and explain the reason for taking\nthe reference and not dropping it.(CVE-2025-40096)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nxfrm: delete x-\u0026gt;tunnel as we delete x\n\nThe ipcomp fallback tunnels currently get deleted (from the various\nlists and hashtables) as the last user state that needed that fallback\nis destroyed (not deleted). If a reference to that user state still\nexists, the fallback state will remain on the hashtables/lists,\ntriggering the WARN in xfrm_state_fini. Because of those remaining\nreferences, the fix in commit f75a2804da39 (\u0026quot;xfrm: destroy xfrm_state\nsynchronously on net exit path\u0026quot;) is not complete.\n\nWe recently fixed one such situation in TCP due to defered freeing of\nskbs (commit 9b6412e6979f (\u0026quot;tcp: drop secpath at the same time as we\ncurrently drop dst\u0026quot;)). This can also happen due to IP reassembly: skbs\nwith a secpath remain on the reassembly queue until netns\ndestruction. If we can\u0026apos;t guarantee that the queues are flushed by the\ntime xfrm_state_fini runs, there may still be references to a (user)\nxfrm_state, preventing the timely deletion of the corresponding\nfallback state.\n\nInstead of chasing each instance of skbs holding a secpath one by one,\nthis patch fixes the issue directly within xfrm, by deleting the\nfallback state as soon as the last user state depending on it has been\ndeleted. Destruction will still happen when the final reference is\ndropped.\n\nA separate lockdep class for the fallback state is required since\nwe\u0026apos;re going to lock x-\u0026gt;tunnel while x is locked.(CVE-2025-40215)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nfuse: fix livelock in synchronous file put from fuseblk workers\n\nI observed a hang when running generic/323 against a fuseblk server.\nThis test opens a file, initiates a lot of AIO writes to that file\ndescriptor, and closes the file descriptor before the writes complete.\nUnsurprisingly, the AIO exerciser threads are mostly stuck waiting for\nresponses from the fuseblk server:\n\n# cat /proc/372265/task/372313/stack\n[\u0026lt;0\u0026gt;] request_wait_answer+0x1fe/0x2a0 [fuse]\n[\u0026lt;0\u0026gt;] __fuse_simple_request+0xd3/0x2b0 [fuse]\n[\u0026lt;0\u0026gt;] fuse_do_getattr+0xfc/0x1f0 [fuse]\n[\u0026lt;0\u0026gt;] fuse_file_read_iter+0xbe/0x1c0 [fuse]\n[\u0026lt;0\u0026gt;] aio_read+0x130/0x1e0\n[\u0026lt;0\u0026gt;] io_submit_one+0x542/0x860\n[\u0026lt;0\u0026gt;] __x64_sys_io_submit+0x98/0x1a0\n[\u0026lt;0\u0026gt;] do_syscall_64+0x37/0xf0\n[\u0026lt;0\u0026gt;] entry_SYSCALL_64_after_hwframe+0x4b/0x53\n\nBut the /weird/ part is that the fuseblk server threads are waiting for\nresponses from itself:\n\n# cat /proc/372210/task/372232/stack\n[\u0026lt;0\u0026gt;] request_wait_answer+0x1fe/0x2a0 [fuse]\n[\u0026lt;0\u0026gt;] __fuse_simple_request+0xd3/0x2b0 [fuse]\n[\u0026lt;0\u0026gt;] fuse_file_put+0x9a/0xd0 [fuse]\n[\u0026lt;0\u0026gt;] fuse_release+0x36/0x50 [fuse]\n[\u0026lt;0\u0026gt;] __fput+0xec/0x2b0\n[\u0026lt;0\u0026gt;] task_work_run+0x55/0x90\n[\u0026lt;0\u0026gt;] syscall_exit_to_user_mode+0xe9/0x100\n[\u0026lt;0\u0026gt;] do_syscall_64+0x43/0xf0\n[\u0026lt;0\u0026gt;] entry_SYSCALL_64_after_hwframe+0x4b/0x53\n\nThe fuseblk server is fuse2fs so there\u0026apos;s nothing all that exciting in\nthe server itself.  So why is the fuse server calling fuse_file_put?\nThe commit message for the fstest sheds some light on that:\n\n\u0026quot;By closing the file descriptor before calling io_destroy, you pretty\nmuch guarantee that the last put on the ioctx will be done in interrupt\ncontext (during I/O completion).\n\nAha.  AIO fgets a new struct file from the fd when it queues the ioctx.\nThe completion of the FUSE_WRITE command from userspace causes the fuse\nserver to call the AIO completion function.  The completion puts the\nstruct file, queuing a delayed fput to the fuse server task.  When the\nfuse server task returns to userspace, it has to run the delayed fput,\nwhich in the case of a fuseblk server, it does synchronously.\n\nSending the FUSE_RELEASE command sychronously from fuse server threads\nis a bad idea because a client program can initiate enough simultaneous\nAIOs such that all the fuse server threads end up in delayed_fput, and\nnow there aren\u0026apos;t any threads left to handle the queued fuse commands.\n\nFix this by only using asynchronous fputs when closing files, and leave\na comment explaining why.(CVE-2025-40220)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nfs/notify: call exportfs_encode_fid with s_umount\n\nCalling intotify_show_fdinfo() on fd watching an overlayfs inode, while\nthe overlayfs is being unmounted, can lead to dereferencing NULL ptr.\n\nThis issue was found by syzkaller.\n\nRace Condition Diagram:\n\nThread 1                           Thread 2\n--------                           --------\n\ngeneric_shutdown_super()\n shrink_dcache_for_umount\n  sb-\u0026gt;s_root = NULL\n\n                    |\n                    |             vfs_read()\n                    |              inotify_fdinfo()\n                    |               * inode get from mark *\n                    |               show_mark_fhandle(m, inode)\n                    |                exportfs_encode_fid(inode, ..)\n                    |                 ovl_encode_fh(inode, ..)\n                    |                  ovl_check_encode_origin(inode)\n                    |                   * deref i_sb-\u0026gt;s_root *\n                    |\n                    |\n                    v\n fsnotify_sb_delete(sb)\n\nWhich then leads to:\n\n[   32.133461] Oops: general protection fault, probably for non-canonical address 0xdffffc0000000006: 0000 [#1] SMP DEBUG_PAGEALLOC KASAN NOPTI\n[   32.134438] KASAN: null-ptr-deref in range [0x0000000000000030-0x0000000000000037]\n[   32.135032] CPU: 1 UID: 0 PID: 4468 Comm: systemd-coredum Not tainted 6.17.0-rc6 #22 PREEMPT(none)\n\n\u0026lt;snip registers, unreliable trace\u0026gt;\n\n[   32.143353] Call Trace:\n[   32.143732]  ovl_encode_fh+0xd5/0x170\n[   32.144031]  exportfs_encode_inode_fh+0x12f/0x300\n[   32.144425]  show_mark_fhandle+0xbe/0x1f0\n[   32.145805]  inotify_fdinfo+0x226/0x2d0\n[   32.146442]  inotify_show_fdinfo+0x1c5/0x350\n[   32.147168]  seq_show+0x530/0x6f0\n[   32.147449]  seq_read_iter+0x503/0x12a0\n[   32.148419]  seq_read+0x31f/0x410\n[   32.150714]  vfs_read+0x1f0/0x9e0\n[   32.152297]  ksys_read+0x125/0x240\n\nIOW ovl_check_encode_origin derefs inode-\u0026gt;i_sb-\u0026gt;s_root, after it was set\nto NULL in the unmount path.\n\nFix it by protecting calling exportfs_encode_fid() from\nshow_mark_fhandle() with s_umount lock.\n\nThis form of fix was suggested by Amir in [1].\n\n[1]: https://lore.kernel.org/all/CAOQ4uxhbDwhb+2Brs1UdkoF0a3NSdBAOQPNfEHjahrgoKJpLEw@mail.gmail.com/(CVE-2025-40237)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ngfs2: Fix unlikely race in gdlm_put_lock\n\nIn gdlm_put_lock(), there is a small window of time in which the\nDFL_UNMOUNT flag has been set but the lockspace hasn\u0026apos;t been released,\nyet.  In that window, dlm may still call gdlm_ast() and gdlm_bast().\nTo prevent it from dereferencing freed glock objects, only free the\nglock if the lockspace has actually been released.(CVE-2025-40242)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ndevlink: rate: Unset parent pointer in devl_rate_nodes_destroy\n\nThe function devl_rate_nodes_destroy is documented to \u0026quot;Unset parent for\nall rate objects\u0026quot;. However, it was only calling the driver-specific\n`rate_leaf_parent_set` or `rate_node_parent_set` ops and decrementing\nthe parent\u0026apos;s refcount, without actually setting the\n`devlink_rate-\u0026gt;parent` pointer to NULL.\n\nThis leaves a dangling pointer in the `devlink_rate` struct, which cause\nrefcount error in netdevsim[1] and mlx5[2]. In addition, this is\ninconsistent with the behavior of `devlink_nl_rate_parent_node_set`,\nwhere the parent pointer is correctly cleared.\n\nThis patch fixes the issue by explicitly setting `devlink_rate-\u0026gt;parent`\nto NULL after notifying the driver, thus fulfilling the function\u0026apos;s\ndocumented behavior for all rate objects.\n\n[1]\nrepro steps:\necho 1 \u0026gt; /sys/bus/netdevsim/new_device\ndevlink dev eswitch set netdevsim/netdevsim1 mode switchdev\necho 1 \u0026gt; /sys/bus/netdevsim/devices/netdevsim1/sriov_numvfs\ndevlink port function rate add netdevsim/netdevsim1/test_node\ndevlink port function rate set netdevsim/netdevsim1/128 parent test_node\necho 1 \u0026gt; /sys/bus/netdevsim/del_device\n\ndmesg:\nrefcount_t: decrement hit 0; leaking memory.\nWARNING: CPU: 8 PID: 1530 at lib/refcount.c:31 refcount_warn_saturate+0x42/0xe0\nCPU: 8 UID: 0 PID: 1530 Comm: bash Not tainted 6.18.0-rc4+ #1 NONE\nHardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS rel-1.16.0-0-gd239552ce722-prebuilt.qemu.org 04/01/2014\nRIP: 0010:refcount_warn_saturate+0x42/0xe0\nCall Trace:\n \u0026lt;TASK\u0026gt;\n devl_rate_leaf_destroy+0x8d/0x90\n __nsim_dev_port_del+0x6c/0x70 [netdevsim]\n nsim_dev_reload_destroy+0x11c/0x140 [netdevsim]\n nsim_drv_remove+0x2b/0xb0 [netdevsim]\n device_release_driver_internal+0x194/0x1f0\n bus_remove_device+0xc6/0x130\n device_del+0x159/0x3c0\n device_unregister+0x1a/0x60\n del_device_store+0x111/0x170 [netdevsim]\n kernfs_fop_write_iter+0x12e/0x1e0\n vfs_write+0x215/0x3d0\n ksys_write+0x5f/0xd0\n do_syscall_64+0x55/0x10f0\n entry_SYSCALL_64_after_hwframe+0x4b/0x53\n\n[2]\ndevlink dev eswitch set pci/0000:08:00.0 mode switchdev\ndevlink port add pci/0000:08:00.0 flavour pcisf pfnum 0 sfnum 1000\ndevlink port function rate add pci/0000:08:00.0/group1\ndevlink port function rate set pci/0000:08:00.0/32768 parent group1\nmodprobe -r mlx5_ib mlx5_fwctl mlx5_core\n\ndmesg:\nrefcount_t: decrement hit 0; leaking memory.\nWARNING: CPU: 7 PID: 16151 at lib/refcount.c:31 refcount_warn_saturate+0x42/0xe0\nCPU: 7 UID: 0 PID: 16151 Comm: bash Not tainted 6.17.0-rc7_for_upstream_min_debug_2025_10_02_12_44 #1 NONE\nHardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS rel-1.16.3-0-ga6ed6b701f0a-prebuilt.qemu.org 04/01/2014\nRIP: 0010:refcount_warn_saturate+0x42/0xe0\nCall Trace:\n \u0026lt;TASK\u0026gt;\n devl_rate_leaf_destroy+0x8d/0x90\n mlx5_esw_offloads_devlink_port_unregister+0x33/0x60 [mlx5_core]\n mlx5_esw_offloads_unload_rep+0x3f/0x50 [mlx5_core]\n mlx5_eswitch_unload_sf_vport+0x40/0x90 [mlx5_core]\n mlx5_sf_esw_event+0xc4/0x120 [mlx5_core]\n notifier_call_chain+0x33/0xa0\n blocking_notifier_call_chain+0x3b/0x50\n mlx5_eswitch_disable_locked+0x50/0x110 [mlx5_core]\n mlx5_eswitch_disable+0x63/0x90 [mlx5_core]\n mlx5_unload+0x1d/0x170 [mlx5_core]\n mlx5_uninit_one+0xa2/0x130 [mlx5_core]\n remove_one+0x78/0xd0 [mlx5_core]\n pci_device_remove+0x39/0xa0\n device_release_driver_internal+0x194/0x1f0\n unbind_store+0x99/0xa0\n kernfs_fop_write_iter+0x12e/0x1e0\n vfs_write+0x215/0x3d0\n ksys_write+0x5f/0xd0\n do_syscall_64+0x53/0x1f0\n entry_SYSCALL_64_after_hwframe+0x4b/0x53(CVE-2025-40251)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nfs/proc: fix uaf in proc_readdir_de()\n\nPde is erased from subdir rbtree through rb_erase(), but not set the node\nto EMPTY, which may result in uaf access.  We should use RB_CLEAR_NODE()\nset the erased node to EMPTY, then pde_subdir_next() will return NULL to\navoid uaf access.\n\nWe found an uaf issue while using stress-ng testing, need to run testcase\ngetdent and tun in the same time.  The steps of the issue is as follows:\n\n1) use getdent to traverse dir /proc/pid/net/dev_snmp6/, and current\n   pde is tun3;\n\n2) in the [time windows] unregister netdevice tun3 and tun2, and erase\n   them from rbtree.  erase tun3 first, and then erase tun2.  the\n   pde(tun2) will be released to slab;\n\n3) continue to getdent process, then pde_subdir_next() will return\n   pde(tun2) which is released, it will case uaf access.\n\nCPU 0                                      |    CPU 1\n-------------------------------------------------------------------------\ntraverse dir /proc/pid/net/dev_snmp6/      |   unregister_netdevice(tun-\u0026gt;dev)   //tun3 tun2\nsys_getdents64()                           |\n  iterate_dir()                            |\n    proc_readdir()                         |\n      proc_readdir_de()                    |     snmp6_unregister_dev()\n        pde_get(de);                       |       proc_remove()\n        read_unlock(\u0026amp;proc_subdir_lock);    |         remove_proc_subtree()\n                                           |           write_lock(\u0026amp;proc_subdir_lock);\n        [time window]                      |           rb_erase(\u0026amp;root-\u0026gt;subdir_node, \u0026amp;parent-\u0026gt;subdir);\n                                           |           write_unlock(\u0026amp;proc_subdir_lock);\n        read_lock(\u0026amp;proc_subdir_lock);      |\n        next = pde_subdir_next(de);        |\n        pde_put(de);                       |\n        de = next;    //UAF                |\n\nrbtree of dev_snmp6\n                        |\n                    pde(tun3)\n                     /    \\\n                  NULL  pde(tun2)(CVE-2025-40271)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nmm/secretmem: fix use-after-free race in fault handler\n\nWhen a page fault occurs in a secret memory file created with\n`memfd_secret(2)`, the kernel will allocate a new folio for it, mark the\nunderlying page as not-present in the direct map, and add it to the file\nmapping.\n\nIf two tasks cause a fault in the same page concurrently, both could end\nup allocating a folio and removing the page from the direct map, but only\none would succeed in adding the folio to the file mapping.  The task that\nfailed undoes the effects of its attempt by (a) freeing the folio again\nand (b) putting the page back into the direct map.  However, by doing\nthese two operations in this order, the page becomes available to the\nallocator again before it is placed back in the direct mapping.\n\nIf another task attempts to allocate the page between (a) and (b), and the\nkernel tries to access it via the direct map, it would result in a\nsupervisor not-present page fault.\n\nFix the ordering to restore the direct map before the folio is freed.(CVE-2025-40272)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ndrm/vmwgfx: Validate command header size against SVGA_CMD_MAX_DATASIZE\n\nThis data originates from userspace and is used in buffer offset\ncalculations which could potentially overflow causing an out-of-bounds\naccess.(CVE-2025-40277)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nBluetooth: MGMT: Fix OOB access in parse_adv_monitor_pattern()\n\nIn the parse_adv_monitor_pattern() function, the value of\nthe \u0026apos;length\u0026apos; variable is currently limited to HCI_MAX_EXT_AD_LENGTH(251).\nThe size of the \u0026apos;value\u0026apos; array in the mgmt_adv_pattern structure is 31.\nIf the value of \u0026apos;pattern[i].length\u0026apos; is set in the user space\nand exceeds 31, the \u0026apos;patterns[i].value\u0026apos; array can be accessed\nout of bound when copied.\n\nIncreasing the size of the \u0026apos;value\u0026apos; array in\nthe \u0026apos;mgmt_adv_pattern\u0026apos; structure will break the userspace.\nConsidering this, and to avoid OOB access revert the limits for \u0026apos;offset\u0026apos;\nand \u0026apos;length\u0026apos; back to the value of HCI_MAX_AD_LENGTH.\n\nFound by InfoTeCS on behalf of Linux Verification Center\n(linuxtesting.org) with SVACE.(CVE-2025-40294)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nBluetooth: hci_event: validate skb length for unknown CC opcode\n\nIn hci_cmd_complete_evt(), if the command complete event has an unknown\nopcode, we assume the first byte of the remaining skb-\u0026gt;data contains the\nreturn status. However, parameter data has previously been pulled in\nhci_event_func(), which may leave the skb empty. If so, using skb-\u0026gt;data[0]\nfor the return status uses un-init memory.\n\nThe fix is to check skb-\u0026gt;len before using skb-\u0026gt;data.(CVE-2025-40301)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nBluetooth: bcsp: receive data only if registered\n\nCurrently, bcsp_recv() can be called even when the BCSP protocol has not\nbeen registered. This leads to a NULL pointer dereference, as shown in\nthe following stack trace:\n\n    KASAN: null-ptr-deref in range [0x0000000000000108-0x000000000000010f]\n    RIP: 0010:bcsp_recv+0x13d/0x1740 drivers/bluetooth/hci_bcsp.c:590\n    Call Trace:\n     \u0026lt;TASK\u0026gt;\n     hci_uart_tty_receive+0x194/0x220 drivers/bluetooth/hci_ldisc.c:627\n     tiocsti+0x23c/0x2c0 drivers/tty/tty_io.c:2290\n     tty_ioctl+0x626/0xde0 drivers/tty/tty_io.c:2706\n     vfs_ioctl fs/ioctl.c:51 [inline]\n     __do_sys_ioctl fs/ioctl.c:907 [inline]\n     __se_sys_ioctl+0xfc/0x170 fs/ioctl.c:893\n     do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline]\n     do_syscall_64+0xfa/0x3b0 arch/x86/entry/syscall_64.c:94\n     entry_SYSCALL_64_after_hwframe+0x77/0x7f\n\nTo prevent this, ensure that the HCI_UART_REGISTERED flag is set before\nprocessing received data. If the protocol is not registered, return\n-EUNATCH.(CVE-2025-40308)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nBluetooth: hci_sync: fix race in hci_cmd_sync_dequeue_once\n\nhci_cmd_sync_dequeue_once() does lookup and then cancel\nthe entry under two separate lock sections. Meanwhile,\nhci_cmd_sync_work() can also delete the same entry,\nleading to double list_del() and \u0026quot;UAF\u0026quot;.\n\nFix this by holding cmd_sync_work_lock across both\nlookup and cancel, so that the entry cannot be removed\nconcurrently.(CVE-2025-40318)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nfutex: Don\u0026apos;t leak robust_list pointer on exec race\n\nsys_get_robust_list() and compat_get_robust_list() use ptrace_may_access()\nto check if the calling task is allowed to access another task\u0026apos;s\nrobust_list pointer. This check is racy against a concurrent exec() in the\ntarget process.\n\nDuring exec(), a task may transition from a non-privileged binary to a\nprivileged one (e.g., setuid binary) and its credentials/memory mappings\nmay change. If get_robust_list() performs ptrace_may_access() before\nthis transition, it may erroneously allow access to sensitive information\nafter the target becomes privileged.\n\nA racy access allows an attacker to exploit a window during which\nptrace_may_access() passes before a target process transitions to a\nprivileged state via exec().\n\nFor example, consider a non-privileged task T that is about to execute a\nsetuid-root binary. An attacker task A calls get_robust_list(T) while T\nis still unprivileged. Since ptrace_may_access() checks permissions\nbased on current credentials, it succeeds. However, if T begins exec\nimmediately afterwards, it becomes privileged and may change its memory\nmappings. Because get_robust_list() proceeds to access T-\u0026gt;robust_list\nwithout synchronizing with exec() it may read user-space pointers from a\nnow-privileged process.\n\nThis violates the intended post-exec access restrictions and could\nexpose sensitive memory addresses or be used as a primitive in a larger\nexploit chain. Consequently, the race can lead to unauthorized\ndisclosure of information across privilege boundaries and poses a\npotential security risk.\n\nTake a read lock on signal-\u0026gt;exec_update_lock prior to invoking\nptrace_may_access() and accessing the robust_list/compat_robust_list.\nThis ensures that the target task\u0026apos;s exec state remains stable during the\ncheck, allowing for consistent and synchronized validation of\ncredentials.(CVE-2025-40341)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnvme-fc: use lock accessing port_state and rport state\n\nnvme_fc_unregister_remote removes the remote port on a lport object at\nany point in time when there is no active association. This races with\nwith the reconnect logic, because nvme_fc_create_association is not\ntaking a lock to check the port_state and atomically increase the\nactive count on the rport.(CVE-2025-40342)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnvmet-fc: avoid scheduling association deletion twice\n\nWhen forcefully shutting down a port via the configfs interface,\nnvmet_port_subsys_drop_link() first calls nvmet_port_del_ctrls() and\nthen nvmet_disable_port(). Both functions will eventually schedule all\nremaining associations for deletion.\n\nThe current implementation checks whether an association is about to be\nremoved, but only after the work item has already been scheduled. As a\nresult, it is possible for the first scheduled work item to free all\nresources, and then for the same work item to be scheduled again for\ndeletion.\n\nBecause the association list is an RCU list, it is not possible to take\na lock and remove the list entry directly, so it cannot be looked up\nagain. Instead, a flag (terminating) must be used to determine whether\nthe association is already in the process of being deleted.(CVE-2025-40343)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\narch_topology: Fix incorrect error check in topology_parse_cpu_capacity()\n\nFix incorrect use of PTR_ERR_OR_ZERO() in topology_parse_cpu_capacity()\nwhich causes the code to proceed with NULL clock pointers. The current\nlogic uses !PTR_ERR_OR_ZERO(cpu_clk) which evaluates to true for both\nvalid pointers and NULL, leading to potential NULL pointer dereference\nin clk_get_rate().\n\nPer include/linux/err.h documentation, PTR_ERR_OR_ZERO(ptr) returns:\n\u0026quot;The error code within @ptr if it is an error pointer; 0 otherwise.\u0026quot;\n\nThis means PTR_ERR_OR_ZERO() returns 0 for both valid pointers AND NULL\npointers. Therefore !PTR_ERR_OR_ZERO(cpu_clk) evaluates to true (proceed)\nwhen cpu_clk is either valid or NULL, causing clk_get_rate(NULL) to be\ncalled when of_clk_get() returns NULL.\n\nReplace with !IS_ERR_OR_NULL(cpu_clk) which only proceeds for valid\npointers, preventing potential NULL pointer dereference in clk_get_rate().(CVE-2025-40346)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nhfsplus: fix KMSAN uninit-value issue in hfsplus_delete_cat()\n\nThe syzbot reported issue in hfsplus_delete_cat():\n\n[   70.682285][ T9333] =====================================================\n[   70.682943][ T9333] BUG: KMSAN: uninit-value in hfsplus_subfolders_dec+0x1d7/0x220\n[   70.683640][ T9333]  hfsplus_subfolders_dec+0x1d7/0x220\n[   70.684141][ T9333]  hfsplus_delete_cat+0x105d/0x12b0\n[   70.684621][ T9333]  hfsplus_rmdir+0x13d/0x310\n[   70.685048][ T9333]  vfs_rmdir+0x5ba/0x810\n[   70.685447][ T9333]  do_rmdir+0x964/0xea0\n[   70.685833][ T9333]  __x64_sys_rmdir+0x71/0xb0\n[   70.686260][ T9333]  x64_sys_call+0xcd8/0x3cf0\n[   70.686695][ T9333]  do_syscall_64+0xd9/0x1d0\n[   70.687119][ T9333]  entry_SYSCALL_64_after_hwframe+0x77/0x7f\n[   70.687646][ T9333]\n[   70.687856][ T9333] Uninit was stored to memory at:\n[   70.688311][ T9333]  hfsplus_subfolders_inc+0x1c2/0x1d0\n[   70.688779][ T9333]  hfsplus_create_cat+0x148e/0x1800\n[   70.689231][ T9333]  hfsplus_mknod+0x27f/0x600\n[   70.689730][ T9333]  hfsplus_mkdir+0x5a/0x70\n[   70.690146][ T9333]  vfs_mkdir+0x483/0x7a0\n[   70.690545][ T9333]  do_mkdirat+0x3f2/0xd30\n[   70.690944][ T9333]  __x64_sys_mkdir+0x9a/0xf0\n[   70.691380][ T9333]  x64_sys_call+0x2f89/0x3cf0\n[   70.691816][ T9333]  do_syscall_64+0xd9/0x1d0\n[   70.692229][ T9333]  entry_SYSCALL_64_after_hwframe+0x77/0x7f\n[   70.692773][ T9333]\n[   70.692990][ T9333] Uninit was stored to memory at:\n[   70.693469][ T9333]  hfsplus_subfolders_inc+0x1c2/0x1d0\n[   70.693960][ T9333]  hfsplus_create_cat+0x148e/0x1800\n[   70.694438][ T9333]  hfsplus_fill_super+0x21c1/0x2700\n[   70.694911][ T9333]  mount_bdev+0x37b/0x530\n[   70.695320][ T9333]  hfsplus_mount+0x4d/0x60\n[   70.695729][ T9333]  legacy_get_tree+0x113/0x2c0\n[   70.696167][ T9333]  vfs_get_tree+0xb3/0x5c0\n[   70.696588][ T9333]  do_new_mount+0x73e/0x1630\n[   70.697013][ T9333]  path_mount+0x6e3/0x1eb0\n[   70.697425][ T9333]  __se_sys_mount+0x733/0x830\n[   70.697857][ T9333]  __x64_sys_mount+0xe4/0x150\n[   70.698269][ T9333]  x64_sys_call+0x2691/0x3cf0\n[   70.698704][ T9333]  do_syscall_64+0xd9/0x1d0\n[   70.699117][ T9333]  entry_SYSCALL_64_after_hwframe+0x77/0x7f\n[   70.699730][ T9333]\n[   70.699946][ T9333] Uninit was created at:\n[   70.700378][ T9333]  __alloc_pages_noprof+0x714/0xe60\n[   70.700843][ T9333]  alloc_pages_mpol_noprof+0x2a2/0x9b0\n[   70.701331][ T9333]  alloc_pages_noprof+0xf8/0x1f0\n[   70.701774][ T9333]  allocate_slab+0x30e/0x1390\n[   70.702194][ T9333]  ___slab_alloc+0x1049/0x33a0\n[   70.702635][ T9333]  kmem_cache_alloc_lru_noprof+0x5ce/0xb20\n[   70.703153][ T9333]  hfsplus_alloc_inode+0x5a/0xd0\n[   70.703598][ T9333]  alloc_inode+0x82/0x490\n[   70.703984][ T9333]  iget_locked+0x22e/0x1320\n[   70.704428][ T9333]  hfsplus_iget+0x5c/0xba0\n[   70.704827][ T9333]  hfsplus_btree_open+0x135/0x1dd0\n[   70.705291][ T9333]  hfsplus_fill_super+0x1132/0x2700\n[   70.705776][ T9333]  mount_bdev+0x37b/0x530\n[   70.706171][ T9333]  hfsplus_mount+0x4d/0x60\n[   70.706579][ T9333]  legacy_get_tree+0x113/0x2c0\n[   70.707019][ T9333]  vfs_get_tree+0xb3/0x5c0\n[   70.707444][ T9333]  do_new_mount+0x73e/0x1630\n[   70.707865][ T9333]  path_mount+0x6e3/0x1eb0\n[   70.708270][ T9333]  __se_sys_mount+0x733/0x830\n[   70.708711][ T9333]  __x64_sys_mount+0xe4/0x150\n[   70.709158][ T9333]  x64_sys_call+0x2691/0x3cf0\n[   70.709630][ T9333]  do_syscall_64+0xd9/0x1d0\n[   70.710053][ T9333]  entry_SYSCALL_64_after_hwframe+0x77/0x7f\n[   70.710611][ T9333]\n[   70.710842][ T9333] CPU: 3 UID: 0 PID: 9333 Comm: repro Not tainted 6.12.0-rc6-dirty #17\n[   70.711568][ T9333] Hardware name: QEMU Ubuntu 24.04 PC (i440FX + PIIX, 1996), BIOS 1.16.3-debian-1.16.3-2 04/01/2014\n[   70.712490][ T9333] =====================================================\n[   70.713085][ T9333] Disabling lock debugging due to kernel taint\n[   70.713618][ T9333] Kernel panic - not syncing: kmsan.panic set ...\n[   70.714159][ T9333] \n---truncated---(CVE-2025-40351)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nriscv: stacktrace: Disable KASAN checks for non-current tasks\n\nUnwinding the stack of a task other than current, KASAN would report\n\u0026quot;BUG: KASAN: out-of-bounds in walk_stackframe+0x41c/0x460\u0026quot;\n\nThere is a same issue on x86 and has been resolved by the commit\n84936118bdf3 (\u0026quot;x86/unwind: Disable KASAN checks for non-current tasks\u0026quot;)\nThe solution could be applied to RISC-V too.\n\nThis patch also can solve the issue:\nhttps://seclists.org/oss-sec/2025/q4/23\n\n[(CVE-2025-40358)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nperf/x86/intel: Fix KASAN global-out-of-bounds warning\n\nWhen running \u0026quot;perf mem record\u0026quot; command on CWF, the below KASAN\nglobal-out-of-bounds warning is seen.\n\n  ==================================================================\n  BUG: KASAN: global-out-of-bounds in cmt_latency_data+0x176/0x1b0\n  Read of size 4 at addr ffffffffb721d000 by task dtlb/9850\n\n  Call Trace:\n\n   kasan_report+0xb8/0xf0\n   cmt_latency_data+0x176/0x1b0\n   setup_arch_pebs_sample_data+0xf49/0x2560\n   intel_pmu_drain_arch_pebs+0x577/0xb00\n   handle_pmi_common+0x6c4/0xc80\n\nThe issue is caused by below code in __grt_latency_data(). The code\ntries to access x86_hybrid_pmu structure which doesn\u0026apos;t exist on\nnon-hybrid platform like CWF.\n\n        WARN_ON_ONCE(hybrid_pmu(event-\u0026gt;pmu)-\u0026gt;pmu_type == hybrid_big)\n\nSo add is_hybrid() check before calling this WARN_ON_ONCE to fix the\nglobal-out-of-bounds access issue.(CVE-2025-40359)\n\nRejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority.(CVE-2025-40361)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nx86/fpu: Ensure XFD state on signal delivery\n\nSean reported [1] the following splat when running KVM tests:\n\n   WARNING: CPU: 232 PID: 15391 at xfd_validate_state+0x65/0x70\n   Call Trace:\n    \u0026lt;TASK\u0026gt;\n    fpu__clear_user_states+0x9c/0x100\n    arch_do_signal_or_restart+0x142/0x210\n    exit_to_user_mode_loop+0x55/0x100\n    do_syscall_64+0x205/0x2c0\n    entry_SYSCALL_64_after_hwframe+0x4b/0x53\n\nChao further identified [2] a reproducible scenario involving signal\ndelivery: a non-AMX task is preempted by an AMX-enabled task which\nmodifies the XFD MSR.\n\nWhen the non-AMX task resumes and reloads XSTATE with init values,\na warning is triggered due to a mismatch between fpstate::xfd and the\nCPU\u0026apos;s current XFD state. fpu__clear_user_states() does not currently\nre-synchronize the XFD state after such preemption.\n\nInvoke xfd_update_state() which detects and corrects the mismatch if\nthere is a dynamic feature.\n\nThis also benefits the sigreturn path, as fpu__restore_sig() may call\nfpu__clear_user_states() when the sigframe is inaccessible.\n\n[ dhansen: minor changelog munging ](CVE-2025-68171)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nftrace: Fix softlockup in ftrace_module_enable\n\nA soft lockup was observed when loading amdgpu module.\nIf a module has a lot of tracable functions, multiple calls\nto kallsyms_lookup can spend too much time in RCU critical\nsection and with disabled preemption, causing kernel panic.\nThis is the same issue that was fixed in\ncommit d0b24b4e91fc (\u0026quot;ftrace: Prevent RCU stall on PREEMPT_VOLUNTARY\nkernels\u0026quot;) and commit 42ea22e754ba (\u0026quot;ftrace: Add cond_resched() to\nftrace_graph_set_hash()\u0026quot;).\n\nFix it the same way by adding cond_resched() in ftrace_module_enable.(CVE-2025-68173)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\namd/amdkfd: enhance kfd process check in switch partition\n\ncurrent switch partition only check if kfd_processes_table is empty.\nkfd_prcesses_table entry is deleted in kfd_process_notifier_release, but\nkfd_process tear down is in kfd_process_wq_release.\n\nconsider two processes:\n\nProcess A (workqueue) -\u0026gt; kfd_process_wq_release -\u0026gt; Access kfd_node member\nProcess B switch partition -\u0026gt; amdgpu_xcp_pre_partition_switch -\u0026gt; amdgpu_amdkfd_device_fini_sw\n-\u0026gt; kfd_node tear down.\n\nProcess A and B may trigger a race as shown in dmesg log.\n\nThis patch is to resolve the race by adding an atomic kfd_process counter\nkfd_processes_count, it increment as create kfd process, decrement as\nfinish kfd_process_wq_release.\n\nv2: Put kfd_processes_count per kfd_dev, move decrement to kfd_process_destroy_pdds\nand bug fix. (Philip Yang)\n\n[3966658.307702] divide error: 0000 [#1] SMP NOPTI\n[3966658.350818]  i10nm_edac\n[3966658.356318] CPU: 124 PID: 38435 Comm: kworker/124:0 Kdump: loaded Tainted\n[3966658.356890] Workqueue: kfd_process_wq kfd_process_wq_release [amdgpu]\n[3966658.362839]  nfit\n[3966658.366457] RIP: 0010:kfd_get_num_sdma_engines+0x17/0x40 [amdgpu]\n[3966658.366460] Code: 00 00 e9 ac 81 02 00 66 66 2e 0f 1f 84 00 00 00 00 00 90 0f 1f 44 00 00 48 8b 4f 08 48 8b b7 00 01 00 00 8b 81 58 26 03 00 99 \u0026lt;f7\u0026gt; be b8 01 00 00 80 b9 70 2e 00 00 00 74 0b 83 f8 02 ba 02 00 00\n[3966658.380967]  x86_pkg_temp_thermal\n[3966658.391529] RSP: 0018:ffffc900a0edfdd8 EFLAGS: 00010246\n[3966658.391531] RAX: 0000000000000008 RBX: ffff8974e593b800 RCX: ffff888645900000\n[3966658.391531] RDX: 0000000000000000 RSI: ffff888129154400 RDI: ffff888129151c00\n[3966658.391532] RBP: ffff8883ad79d400 R08: 0000000000000000 R09: ffff8890d2750af4\n[3966658.391532] R10: 0000000000000018 R11: 0000000000000018 R12: 0000000000000000\n[3966658.391533] R13: ffff8883ad79d400 R14: ffffe87ff662ba00 R15: ffff8974e593b800\n[3966658.391533] FS:  0000000000000000(0000) GS:ffff88fe7f600000(0000) knlGS:0000000000000000\n[3966658.391534] CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033\n[3966658.391534] CR2: 0000000000d71000 CR3: 000000dd0e970004 CR4: 0000000002770ee0\n[3966658.391535] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000\n[3966658.391535] DR3: 0000000000000000 DR6: 00000000fffe07f0 DR7: 0000000000000400\n[3966658.391536] PKRU: 55555554\n[3966658.391536] Call Trace:\n[3966658.391674]  deallocate_sdma_queue+0x38/0xa0 [amdgpu]\n[3966658.391762]  process_termination_cpsch+0x1ed/0x480 [amdgpu]\n[3966658.399754]  intel_powerclamp\n[3966658.402831]  kfd_process_dequeue_from_all_devices+0x5b/0xc0 [amdgpu]\n[3966658.402908]  kfd_process_wq_release+0x1a/0x1a0 [amdgpu]\n[3966658.410516]  coretemp\n[3966658.434016]  process_one_work+0x1ad/0x380\n[3966658.434021]  worker_thread+0x49/0x310\n[3966658.438963]  kvm_intel\n[3966658.446041]  ? process_one_work+0x380/0x380\n[3966658.446045]  kthread+0x118/0x140\n[3966658.446047]  ? __kthread_bind_mask+0x60/0x60\n[3966658.446050]  ret_from_fork+0x1f/0x30\n[3966658.446053] Modules linked in: kpatch_20765354(OEK)\n[3966658.455310]  kvm\n[3966658.464534]  mptcp_diag xsk_diag raw_diag unix_diag af_packet_diag netlink_diag udp_diag act_pedit act_mirred act_vlan cls_flower kpatch_21951273(OEK) kpatch_18424469(OEK) kpatch_19749756(OEK)\n[3966658.473462]  idxd_mdev\n[3966658.482306]  kpatch_17971294(OEK) sch_ingress xt_conntrack amdgpu(OE) amdxcp(OE) amddrm_buddy(OE) amd_sched(OE) amdttm(OE) amdkcl(OE) intel_ifs iptable_mangle tcm_loop target_core_pscsi tcp_diag target_core_file inet_diag target_core_iblock target_core_user target_core_mod coldpgs kpatch_18383292(OEK) ip6table_nat ip6table_filter ip6_tables ip_set_hash_ipportip ip_set_hash_ipportnet ip_set_hash_ipport ip_set_bitmap_port xt_comment iptable_nat nf_nat iptable_filter ip_tables ip_set ip_vs_sh ip_vs_wrr ip_vs_rr ip_vs nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 sn_core_odd(OE) i40e overlay binfmt_misc tun bonding(OE) aisqos(OE) aisqo\n---truncated---(CVE-2025-68174)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nPCI: cadence: Check for the existence of cdns_pcie::ops before using it\n\ncdns_pcie::ops might not be populated by all the Cadence glue drivers. This\nis going to be true for the upcoming Sophgo platform which doesn\u0026apos;t set the\nops.\n\nHence, add a check to prevent NULL pointer dereference.\n\n[mani: reworded subject and description](CVE-2025-68176)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ntcp: use dst_dev_rcu() in tcp_fastopen_active_disable_ofo_check()\n\nUse RCU to avoid a pair of atomic operations and a potential\nUAF on dst_dev()-\u0026gt;flags.(CVE-2025-68188)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nbpf: Add bpf_prog_run_data_pointers()\n\nsyzbot found that cls_bpf_classify() is able to change\ntc_skb_cb(skb)-\u0026gt;drop_reason triggering a warning in sk_skb_reason_drop().\n\nWARNING: CPU: 0 PID: 5965 at net/core/skbuff.c:1192 __sk_skb_reason_drop net/core/skbuff.c:1189 [inline]\nWARNING: CPU: 0 PID: 5965 at net/core/skbuff.c:1192 sk_skb_reason_drop+0x76/0x170 net/core/skbuff.c:1214\n\nstruct tc_skb_cb has been added in commit ec624fe740b4 (\u0026quot;net/sched:\nExtend qdisc control block with tc control block\u0026quot;), which added a wrong\ninteraction with db58ba459202 (\u0026quot;bpf: wire in data and data_end for\ncls_act_bpf\u0026quot;).\n\ndrop_reason was added later.\n\nAdd bpf_prog_run_data_pointers() helper to save/restore the net_sched\nstorage colliding with BPF data_meta/data_end.(CVE-2025-68200)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnetfilter: nft_ct: add seqadj extension for natted connections\n\nSequence adjustment may be required for FTP traffic with PASV/EPSV modes.\ndue to need to re-write packet payload (IP, port) on the ftp control\nconnection. This can require changes to the TCP length and expected\nseq / ack_seq.\n\nThe easiest way to reproduce this issue is with PASV mode.\nExample ruleset:\ntable inet ftp_nat {\n        ct helper ftp_helper {\n                type \u0026quot;ftp\u0026quot; protocol tcp\n                l3proto inet\n        }\n\n        chain prerouting {\n                type filter hook prerouting priority 0; policy accept;\n                tcp dport 21 ct state new ct helper set \u0026quot;ftp_helper\u0026quot;\n        }\n}\ntable ip nat {\n        chain prerouting {\n                type nat hook prerouting priority -100; policy accept;\n                tcp dport 21 dnat ip prefix to ip daddr map {\n\t\t\t192.168.100.1 : 192.168.13.2/32 }\n        }\n\n        chain postrouting {\n                type nat hook postrouting priority 100 ; policy accept;\n                tcp sport 21 snat ip prefix to ip saddr map {\n\t\t\t192.168.13.2 : 192.168.100.1/32 }\n        }\n}\n\nNote that the ftp helper gets assigned *after* the dnat setup.\n\nThe inverse (nat after helper assign) is handled by an existing\ncheck in nf_nat_setup_info() and will not show the problem.\n\nTopoloy:\n\n +-------------------+     +----------------------------------+\n | FTP: 192.168.13.2 | \u0026lt;-\u0026gt; | NAT: 192.168.13.3, 192.168.100.1 |\n +-------------------+     +----------------------------------+\n                                      |\n                         +-----------------------+\n                         | Client: 192.168.100.2 |\n                         +-----------------------+\n\nftp nat changes do not work as expected in this case:\nConnected to 192.168.100.1.\n[..]\nftp\u0026gt; epsv\nEPSV/EPRT on IPv4 off.\nftp\u0026gt; ls\n227 Entering passive mode (192,168,100,1,209,129).\n421 Service not available, remote server has closed connection.\n\nKernel logs:\nMissing nfct_seqadj_ext_add() setup call\nWARNING: CPU: 1 PID: 0 at net/netfilter/nf_conntrack_seqadj.c:41\n[..]\n __nf_nat_mangle_tcp_packet+0x100/0x160 [nf_nat]\n nf_nat_ftp+0x142/0x280 [nf_nat_ftp]\n help+0x4d1/0x880 [nf_conntrack_ftp]\n nf_confirm+0x122/0x2e0 [nf_conntrack]\n nf_hook_slow+0x3c/0xb0\n ..\n\nFix this by adding the required extension when a conntrack helper is assigned\nto a connection that has a nat binding.(CVE-2025-68206)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nbpf: account for current allocated stack depth in widen_imprecise_scalars()\n\nThe usage pattern for widen_imprecise_scalars() looks as follows:\n\n    prev_st = find_prev_entry(env, ...);\n    queued_st = push_stack(...);\n    widen_imprecise_scalars(env, prev_st, queued_st);\n\nWhere prev_st is an ancestor of the queued_st in the explored states\ntree. This ancestor is not guaranteed to have same allocated stack\ndepth as queued_st. E.g. in the following case:\n\n    def main():\n      for i in 1..2:\n        foo(i)        // same callsite, differnt param\n\n    def foo(i):\n      if i == 1:\n        use 128 bytes of stack\n      iterator based loop\n\nHere, for a second \u0026apos;foo\u0026apos; call prev_st-\u0026gt;allocated_stack is 128,\nwhile queued_st-\u0026gt;allocated_stack is much smaller.\nwiden_imprecise_scalars() needs to take this into account and avoid\naccessing bpf_verifier_state-\u0026gt;frame[*]-\u0026gt;stack out of bounds.(CVE-2025-68208)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ntimers: Fix NULL function pointer race in timer_shutdown_sync()\n\nThere is a race condition between timer_shutdown_sync() and timer\nexpiration that can lead to hitting a WARN_ON in expire_timers().\n\nThe issue occurs when timer_shutdown_sync() clears the timer function\nto NULL while the timer is still running on another CPU. The race\nscenario looks like this:\n\nCPU0\t\t\t\t\tCPU1\n\t\t\t\t\t\u0026lt;SOFTIRQ\u0026gt;\n\t\t\t\t\tlock_timer_base()\n\t\t\t\t\texpire_timers()\n\t\t\t\t\tbase-\u0026gt;running_timer = timer;\n\t\t\t\t\tunlock_timer_base()\n\t\t\t\t\t[call_timer_fn enter]\n\t\t\t\t\tmod_timer()\n\t\t\t\t\t...\ntimer_shutdown_sync()\nlock_timer_base()\n// For now, will not detach the timer but only clear its function to NULL\nif (base-\u0026gt;running_timer != timer)\n\tret = detach_if_pending(timer, base, true);\nif (shutdown)\n\ttimer-\u0026gt;function = NULL;\nunlock_timer_base()\n\t\t\t\t\t[call_timer_fn exit]\n\t\t\t\t\tlock_timer_base()\n\t\t\t\t\tbase-\u0026gt;running_timer = NULL;\n\t\t\t\t\tunlock_timer_base()\n\t\t\t\t\t...\n\t\t\t\t\t// Now timer is pending while its function set to NULL.\n\t\t\t\t\t// next timer trigger\n\t\t\t\t\t\u0026lt;SOFTIRQ\u0026gt;\n\t\t\t\t\texpire_timers()\n\t\t\t\t\tWARN_ON_ONCE(!fn) // hit\n\t\t\t\t\t...\nlock_timer_base()\n// Now timer will detach\nif (base-\u0026gt;running_timer != timer)\n\tret = detach_if_pending(timer, base, true);\nif (shutdown)\n\ttimer-\u0026gt;function = NULL;\nunlock_timer_base()\n\nThe problem is that timer_shutdown_sync() clears the timer function\nregardless of whether the timer is currently running. This can leave a\npending timer with a NULL function pointer, which triggers the\nWARN_ON_ONCE(!fn) check in expire_timers().\n\nFix this by only clearing the timer function when actually detaching the\ntimer. If the timer is running, leave the function pointer intact, which is\nsafe because the timer will be properly detached when it finishes running.(CVE-2025-68214)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnouveau/firmware: Add missing kfree() of nvkm_falcon_fw::boot\n\nnvkm_falcon_fw::boot is allocated, but no one frees it. This causes a\nkmemleak warning.\n\nMake sure this data is deallocated.(CVE-2025-68235)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nKVM: SVM: Don\u0026apos;t skip unrelated instruction if INT3/INTO is replaced\n\nWhen re-injecting a soft interrupt from an INT3, INT0, or (select) INTn\ninstruction, discard the exception and retry the instruction if the code\nstream is changed (e.g. by a different vCPU) between when the CPU\nexecutes the instruction and when KVM decodes the instruction to get the\nnext RIP.\n\nAs effectively predicted by commit 6ef88d6e36c2 (\u0026quot;KVM: SVM: Re-inject\nINT3/INTO instead of retrying the instruction\u0026quot;), failure to verify that\nthe correct INTn instruction was decoded can effectively clobber guest\nstate due to decoding the wrong instruction and thus specifying the\nwrong next RIP.\n\nThe bug most often manifests as \u0026quot;Oops: int3\u0026quot; panics on static branch\nchecks in Linux guests.  Enabling or disabling a static branch in Linux\nuses the kernel\u0026apos;s \u0026quot;text poke\u0026quot; code patching mechanism.  To modify code\nwhile other CPUs may be executing that code, Linux (temporarily)\nreplaces the first byte of the original instruction with an int3 (opcode\n0xcc), then patches in the new code stream except for the first byte,\nand finally replaces the int3 with the first byte of the new code\nstream.  If a CPU hits the int3, i.e. executes the code while it\u0026apos;s being\nmodified, then the guest kernel must look up the RIP to determine how to\nhandle the #BP, e.g. by emulating the new instruction.  If the RIP is\nincorrect, then this lookup fails and the guest kernel panics.\n\nThe bug reproduces almost instantly by hacking the guest kernel to\nrepeatedly check a static branch[1] while running a drgn script[2] on\nthe host to constantly swap out the memory containing the guest\u0026apos;s TSS.\n\n[1]: https://gist.github.com/osandov/44d17c51c28c0ac998ea0334edf90b5a\n[2]: https://gist.github.com/osandov/10e45e45afa29b11e0c7209247afc00b(CVE-2025-68259)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\next4: add i_data_sem protection in ext4_destroy_inline_data_nolock()\n\nFix a race between inline data destruction and block mapping.\n\nThe function ext4_destroy_inline_data_nolock() changes the inode data\nlayout by clearing EXT4_INODE_INLINE_DATA and setting EXT4_INODE_EXTENTS.\nAt the same time, another thread may execute ext4_map_blocks(), which\ntests EXT4_INODE_EXTENTS to decide whether to call ext4_ext_map_blocks()\nor ext4_ind_map_blocks().\n\nWithout i_data_sem protection, ext4_ind_map_blocks() may receive inode\nwith EXT4_INODE_EXTENTS flag and triggering assert.\n\nkernel BUG at fs/ext4/indirect.c:546!\nEXT4-fs (loop2): unmounting filesystem.\ninvalid opcode: 0000 [#1] PREEMPT SMP KASAN NOPTI\nHardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.12.0-1 04/01/2014\nRIP: 0010:ext4_ind_map_blocks.cold+0x2b/0x5a fs/ext4/indirect.c:546\n\nCall Trace:\n \u0026lt;TASK\u0026gt;\n ext4_map_blocks+0xb9b/0x16f0 fs/ext4/inode.c:681\n _ext4_get_block+0x242/0x590 fs/ext4/inode.c:822\n ext4_block_write_begin+0x48b/0x12c0 fs/ext4/inode.c:1124\n ext4_write_begin+0x598/0xef0 fs/ext4/inode.c:1255\n ext4_da_write_begin+0x21e/0x9c0 fs/ext4/inode.c:3000\n generic_perform_write+0x259/0x5d0 mm/filemap.c:3846\n ext4_buffered_write_iter+0x15b/0x470 fs/ext4/file.c:285\n ext4_file_write_iter+0x8e0/0x17f0 fs/ext4/file.c:679\n call_write_iter include/linux/fs.h:2271 [inline]\n do_iter_readv_writev+0x212/0x3c0 fs/read_write.c:735\n do_iter_write+0x186/0x710 fs/read_write.c:861\n vfs_iter_write+0x70/0xa0 fs/read_write.c:902\n iter_file_splice_write+0x73b/0xc90 fs/splice.c:685\n do_splice_from fs/splice.c:763 [inline]\n direct_splice_actor+0x10f/0x170 fs/splice.c:950\n splice_direct_to_actor+0x33a/0xa10 fs/splice.c:896\n do_splice_direct+0x1a9/0x280 fs/splice.c:1002\n do_sendfile+0xb13/0x12c0 fs/read_write.c:1255\n __do_sys_sendfile64 fs/read_write.c:1323 [inline]\n __se_sys_sendfile64 fs/read_write.c:1309 [inline]\n __x64_sys_sendfile64+0x1cf/0x210 fs/read_write.c:1309\n do_syscall_x64 arch/x86/entry/common.c:51 [inline]\n do_syscall_64+0x35/0x80 arch/x86/entry/common.c:81\n entry_SYSCALL_64_after_hwframe+0x6e/0xd8(CVE-2025-68261)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\next4: refresh inline data size before write operations\n\nThe cached ei-\u0026gt;i_inline_size can become stale between the initial size\ncheck and when ext4_update_inline_data()/ext4_create_inline_data() use\nit. Although ext4_get_max_inline_size() reads the correct value at the\ntime of the check, concurrent xattr operations can modify i_inline_size\nbefore ext4_write_lock_xattr() is acquired.\n\nThis causes ext4_update_inline_data() and ext4_create_inline_data() to\nwork with stale capacity values, leading to a BUG_ON() crash in\next4_write_inline_data():\n\n  kernel BUG at fs/ext4/inline.c:1331!\n  BUG_ON(pos + len \u0026gt; EXT4_I(inode)-\u0026gt;i_inline_size);\n\nThe race window:\n1. ext4_get_max_inline_size() reads i_inline_size = 60 (correct)\n2. Size check passes for 50-byte write\n3. [Another thread adds xattr, i_inline_size changes to 40]\n4. ext4_write_lock_xattr() acquires lock\n5. ext4_update_inline_data() uses stale i_inline_size = 60\n6. Attempts to write 50 bytes but only 40 bytes actually available\n7. BUG_ON() triggers\n\nFix this by recalculating i_inline_size via ext4_find_inline_data_nolock()\nimmediately after acquiring xattr_sem. This ensures ext4_update_inline_data()\nand ext4_create_inline_data() work with current values that are protected\nfrom concurrent modifications.\n\nThis is similar to commit a54c4613dac1 (\u0026quot;ext4: fix race writing to an\ninline_data file while its xattrs are changing\u0026quot;) which fixed i_inline_off\nstaleness. This patch addresses the related i_inline_size staleness issue.(CVE-2025-68264)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnvme: fix admin request_queue lifetime\n\nThe namespaces can access the controller\u0026apos;s admin request_queue, and\nstale references on the namespaces may exist after tearing down the\ncontroller. Ensure the admin request_queue is active by moving the\ncontroller\u0026apos;s \u0026apos;put\u0026apos; to after all controller references have been released\nto ensure no one is can access the request_queue. This fixes a reported\nuse-after-free bug:\n\n  BUG: KASAN: slab-use-after-free in blk_queue_enter+0x41c/0x4a0\n  Read of size 8 at addr ffff88c0a53819f8 by task nvme/3287\n  CPU: 67 UID: 0 PID: 3287 Comm: nvme Tainted: G            E       6.13.2-ga1582f1a031e #15\n  Tainted: [E]=UNSIGNED_MODULE\n  Hardware name: Jabil /EGS 2S MB1, BIOS 1.00 06/18/2025\n  Call Trace:\n   \u0026lt;TASK\u0026gt;\n   dump_stack_lvl+0x4f/0x60\n   print_report+0xc4/0x620\n   ? _raw_spin_lock_irqsave+0x70/0xb0\n   ? _raw_read_unlock_irqrestore+0x30/0x30\n   ? blk_queue_enter+0x41c/0x4a0\n   kasan_report+0xab/0xe0\n   ? blk_queue_enter+0x41c/0x4a0\n   blk_queue_enter+0x41c/0x4a0\n   ? __irq_work_queue_local+0x75/0x1d0\n   ? blk_queue_start_drain+0x70/0x70\n   ? irq_work_queue+0x18/0x20\n   ? vprintk_emit.part.0+0x1cc/0x350\n   ? wake_up_klogd_work_func+0x60/0x60\n   blk_mq_alloc_request+0x2b7/0x6b0\n   ? __blk_mq_alloc_requests+0x1060/0x1060\n   ? __switch_to+0x5b7/0x1060\n   nvme_submit_user_cmd+0xa9/0x330\n   nvme_user_cmd.isra.0+0x240/0x3f0\n   ? force_sigsegv+0xe0/0xe0\n   ? nvme_user_cmd64+0x400/0x400\n   ? vfs_fileattr_set+0x9b0/0x9b0\n   ? cgroup_update_frozen_flag+0x24/0x1c0\n   ? cgroup_leave_frozen+0x204/0x330\n   ? nvme_ioctl+0x7c/0x2c0\n   blkdev_ioctl+0x1a8/0x4d0\n   ? blkdev_common_ioctl+0x1930/0x1930\n   ? fdget+0x54/0x380\n   __x64_sys_ioctl+0x129/0x190\n   do_syscall_64+0x5b/0x160\n   entry_SYSCALL_64_after_hwframe+0x4b/0x53\n  RIP: 0033:0x7f765f703b0b\n  Code: ff ff ff 85 c0 79 9b 49 c7 c4 ff ff ff ff 5b 5d 4c 89 e0 41 5c c3 66 0f 1f 84 00 00 00 00 00 f3 0f 1e fa b8 10 00 00 00 0f 05 \u0026lt;48\u0026gt; 3d 01 f0 ff ff 73 01 c3 48 8b 0d dd 52 0f 00 f7 d8 64 89 01 48\n  RSP: 002b:00007ffe2cefe808 EFLAGS: 00000202 ORIG_RAX: 0000000000000010\n  RAX: ffffffffffffffda RBX: 00007ffe2cefe860 RCX: 00007f765f703b0b\n  RDX: 00007ffe2cefe860 RSI: 00000000c0484e41 RDI: 0000000000000003\n  RBP: 0000000000000000 R08: 0000000000000003 R09: 0000000000000000\n  R10: 00007f765f611d50 R11: 0000000000000202 R12: 0000000000000003\n  R13: 00000000c0484e41 R14: 0000000000000001 R15: 00007ffe2cefea60\n   \u0026lt;/TASK\u0026gt;(CVE-2025-68265)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nceph: fix crash in process_v2_sparse_read() for encrypted directories\n\nThe crash in process_v2_sparse_read() for fscrypt-encrypted directories\nhas been reported. Issue takes place for Ceph msgr2 protocol in secure\nmode. It can be reproduced by the steps:\n\nsudo mount -t ceph :/ /mnt/cephfs/ -o name=admin,fs=cephfs,ms_mode=secure\n\n(1) mkdir /mnt/cephfs/fscrypt-test-3\n(2) cp area_decrypted.tar /mnt/cephfs/fscrypt-test-3\n(3) fscrypt encrypt --source=raw_key --key=./my.key /mnt/cephfs/fscrypt-test-3\n(4) fscrypt lock /mnt/cephfs/fscrypt-test-3\n(5) fscrypt unlock --key=my.key /mnt/cephfs/fscrypt-test-3\n(6) cat /mnt/cephfs/fscrypt-test-3/area_decrypted.tar\n(7) Issue has been triggered\n\n[  408.072247] ------------[ cut here ]------------\n[  408.072251] WARNING: CPU: 1 PID: 392 at net/ceph/messenger_v2.c:865\nceph_con_v2_try_read+0x4b39/0x72f0\n[  408.072267] Modules linked in: intel_rapl_msr intel_rapl_common\nintel_uncore_frequency_common intel_pmc_core pmt_telemetry pmt_discovery\npmt_class intel_pmc_ssram_telemetry intel_vsec kvm_intel joydev kvm irqbypass\npolyval_clmulni ghash_clmulni_intel aesni_intel rapl input_leds psmouse\nserio_raw i2c_piix4 vga16fb bochs vgastate i2c_smbus floppy mac_hid qemu_fw_cfg\npata_acpi sch_fq_codel rbd msr parport_pc ppdev lp parport efi_pstore\n[  408.072304] CPU: 1 UID: 0 PID: 392 Comm: kworker/1:3 Not tainted 6.17.0-rc7+\n[  408.072307] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS\n1.17.0-5.fc42 04/01/2014\n[  408.072310] Workqueue: ceph-msgr ceph_con_workfn\n[  408.072314] RIP: 0010:ceph_con_v2_try_read+0x4b39/0x72f0\n[  408.072317] Code: c7 c1 20 f0 d4 ae 50 31 d2 48 c7 c6 60 27 d5 ae 48 c7 c7 f8\n8e 6f b0 68 60 38 d5 ae e8 00 47 61 fe 48 83 c4 18 e9 ac fc ff ff \u0026lt;0f\u0026gt; 0b e9 06\nfe ff ff 4c 8b 9d 98 fd ff ff 0f 84 64 e7 ff ff 89 85\n[  408.072319] RSP: 0018:ffff88811c3e7a30 EFLAGS: 00010246\n[  408.072322] RAX: ffffed1024874c6f RBX: ffffea00042c2b40 RCX: 0000000000000f38\n[  408.072324] RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000000000000\n[  408.072325] RBP: ffff88811c3e7ca8 R08: 0000000000000000 R09: 00000000000000c8\n[  408.072326] R10: 00000000000000c8 R11: 0000000000000000 R12: 00000000000000c8\n[  408.072327] R13: dffffc0000000000 R14: ffff8881243a6030 R15: 0000000000003000\n[  408.072329] FS:  0000000000000000(0000) GS:ffff88823eadf000(0000)\nknlGS:0000000000000000\n[  408.072331] CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033\n[  408.072332] CR2: 000000c0003c6000 CR3: 000000010c106005 CR4: 0000000000772ef0\n[  408.072336] PKRU: 55555554\n[  408.072337] Call Trace:\n[  408.072338]  \u0026lt;TASK\u0026gt;\n[  408.072340]  ? sched_clock_noinstr+0x9/0x10\n[  408.072344]  ? __pfx_ceph_con_v2_try_read+0x10/0x10\n[  408.072347]  ? _raw_spin_unlock+0xe/0x40\n[  408.072349]  ? finish_task_switch.isra.0+0x15d/0x830\n[  408.072353]  ? __kasan_check_write+0x14/0x30\n[  408.072357]  ? mutex_lock+0x84/0xe0\n[  408.072359]  ? __pfx_mutex_lock+0x10/0x10\n[  408.072361]  ceph_con_workfn+0x27e/0x10e0\n[  408.072364]  ? metric_delayed_work+0x311/0x2c50\n[  408.072367]  process_one_work+0x611/0xe20\n[  408.072371]  ? __kasan_check_write+0x14/0x30\n[  408.072373]  worker_thread+0x7e3/0x1580\n[  408.072375]  ? __pfx__raw_spin_lock_irqsave+0x10/0x10\n[  408.072378]  ? __pfx_worker_thread+0x10/0x10\n[  408.072381]  kthread+0x381/0x7a0\n[  408.072383]  ? __pfx__raw_spin_lock_irq+0x10/0x10\n[  408.072385]  ? __pfx_kthread+0x10/0x10\n[  408.072387]  ? __kasan_check_write+0x14/0x30\n[  408.072389]  ? recalc_sigpending+0x160/0x220\n[  408.072392]  ? _raw_spin_unlock_irq+0xe/0x50\n[  408.072394]  ? calculate_sigpending+0x78/0xb0\n[  408.072395]  ? __pfx_kthread+0x10/0x10\n[  408.072397]  ret_from_fork+0x2b6/0x380\n[  408.072400]  ? __pfx_kthread+0x10/0x10\n[  408.072402]  ret_from_fork_asm+0x1a/0x30\n[  408.072406]  \u0026lt;/TASK\u0026gt;\n[  408.072407] ---[ end trace 0000000000000000 ]---\n[  408.072418] Oops: general protection fault, probably for non-canonical\naddress 0xdffffc00000000\n---truncated---(CVE-2025-68297)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nPCI/AER: Fix NULL pointer access by aer_info\n\nThe kzalloc(GFP_KERNEL) may return NULL, so all accesses to aer_info-\u0026gt;xxx\nwill result in kernel panic. Fix it.(CVE-2025-68309)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nusb: uas: fix urb unmapping issue when the uas device is remove during ongoing data transfer\n\nWhen a UAS device is unplugged during data transfer, there is\na probability of a system panic occurring. The root cause is\nan access to an invalid memory address during URB callback handling.\nSpecifically, this happens when the dma_direct_unmap_sg() function\nis called within the usb_hcd_unmap_urb_for_dma() interface, but the\nsg-\u0026gt;dma_address field is 0 and the sg data structure has already been\nfreed.\n\nThe SCSI driver sends transfer commands by invoking uas_queuecommand_lck()\nin uas.c, using the uas_submit_urbs() function to submit requests to USB.\nWithin the uas_submit_urbs() implementation, three URBs (sense_urb,\ndata_urb, and cmd_urb) are sequentially submitted. Device removal may\noccur at any point during uas_submit_urbs execution, which may result\nin URB submission failure. However, some URBs might have been successfully\nsubmitted before the failure, and uas_submit_urbs will return the -ENODEV\nerror code in this case. The current error handling directly calls\nscsi_done(). In the SCSI driver, this eventually triggers scsi_complete()\nto invoke scsi_end_request() for releasing the sgtable. The successfully\nsubmitted URBs, when being unlinked to giveback, call\nusb_hcd_unmap_urb_for_dma() in hcd.c, leading to exceptions during sg\nunmapping operations since the sg data structure has already been freed.\n\nThis patch modifies the error condition check in the uas_submit_urbs()\nfunction. When a UAS device is removed but one or more URBs have already\nbeen successfully submitted to USB, it avoids immediately invoking\nscsi_done() and save the cmnd to devinfo-\u0026gt;cmnd array. If the successfully\nsubmitted URBs is completed before devinfo-\u0026gt;resetting being set, then\nthe scsi_done() function will be called within uas_try_complete() after\nall pending URB operations are finalized. Otherwise, the scsi_done()\nfunction will be called within uas_zap_pending(), which is executed after\nusb_kill_anchored_urbs().\n\nThe error handling only takes effect when uas_queuecommand_lck() calls\nuas_submit_urbs() and returns the error value -ENODEV . In this case,\nthe device is disconnected, and the flow proceeds to uas_disconnect(),\nwhere uas_zap_pending() is invoked to call uas_try_complete().(CVE-2025-68331)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\njbd2: avoid bug_on in jbd2_journal_get_create_access() when file system corrupted\n\nThere\u0026apos;s issue when file system corrupted:\n------------[ cut here ]------------\nkernel BUG at fs/jbd2/transaction.c:1289!\nOops: invalid opcode: 0000 [#1] SMP KASAN PTI\nCPU: 5 UID: 0 PID: 2031 Comm: mkdir Not tainted 6.18.0-rc1-next\nRIP: 0010:jbd2_journal_get_create_access+0x3b6/0x4d0\nRSP: 0018:ffff888117aafa30 EFLAGS: 00010202\nRAX: 0000000000000000 RBX: ffff88811a86b000 RCX: ffffffff89a63534\nRDX: 1ffff110200ec602 RSI: 0000000000000004 RDI: ffff888100763010\nRBP: ffff888100763000 R08: 0000000000000001 R09: ffff888100763028\nR10: 0000000000000003 R11: 0000000000000000 R12: 0000000000000000\nR13: ffff88812c432000 R14: ffff88812c608000 R15: ffff888120bfc000\nCS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033\nCR2: 00007f91d6970c99 CR3: 00000001159c4000 CR4: 00000000000006f0\nCall Trace:\n \u0026lt;TASK\u0026gt;\n __ext4_journal_get_create_access+0x42/0x170\n ext4_getblk+0x319/0x6f0\n ext4_bread+0x11/0x100\n ext4_append+0x1e6/0x4a0\n ext4_init_new_dir+0x145/0x1d0\n ext4_mkdir+0x326/0x920\n vfs_mkdir+0x45c/0x740\n do_mkdirat+0x234/0x2f0\n __x64_sys_mkdir+0xd6/0x120\n do_syscall_64+0x5f/0xfa0\n entry_SYSCALL_64_after_hwframe+0x76/0x7e\n\nThe above issue occurs with us in errors=continue mode when accompanied by\nstorage failures. There have been many inconsistencies in the file system\ndata.\nIn the case of file system data inconsistency, for example, if the block\nbitmap of a referenced block is not set, it can lead to the situation where\na block being committed is allocated and used again. As a result, the\nfollowing condition will not be satisfied then trigger BUG_ON. Of course,\nit is entirely possible to construct a problematic image that can trigger\nthis BUG_ON through specific operations. In fact, I have constructed such\nan image and easily reproduced this issue.\nTherefore, J_ASSERT() holds true only under ideal conditions, but it may\nnot necessarily be satisfied in exceptional scenarios. Using J_ASSERT()\ndirectly in abnormal situations would cause the system to crash, which is\nclearly not what we want. So here we directly trigger a JBD abort instead\nof immediately invoking BUG_ON.(CVE-2025-68337)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nNFSv4/pNFS: Clear NFS_INO_LAYOUTCOMMIT in pnfs_mark_layout_stateid_invalid\n\nFixes a crash when layout is null during this call stack:\n\nwrite_inode\n    -\u0026gt; nfs4_write_inode\n        -\u0026gt; pnfs_layoutcommit_inode\n\npnfs_set_layoutcommit relies on the lseg refcount to keep the layout\naround. Need to clear NFS_INO_LAYOUTCOMMIT otherwise we might attempt\nto reference a null layout.(CVE-2025-68349)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nregulator: core: Protect regulator_supply_alias_list with regulator_list_mutex\n\nregulator_supply_alias_list was accessed without any locking in\nregulator_supply_alias(), regulator_register_supply_alias(), and\nregulator_unregister_supply_alias(). Concurrent registration,\nunregistration and lookups can race, leading to:\n\n1 use-after-free if an alias entry is removed while being read,\n2 duplicate entries when two threads register the same alias,\n3 inconsistent alias mappings observed by consumers.\n\nProtect all traversals, insertions and deletions on\nregulator_supply_alias_list with the existing regulator_list_mutex.(CVE-2025-68354)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ngfs2: Prevent recursive memory reclaim\n\nFunction new_inode() returns a new inode with inode-\u0026gt;i_mapping-\u0026gt;gfp_mask\nset to GFP_HIGHUSER_MOVABLE.  This value includes the __GFP_FS flag, so\nallocations in that address space can recurse into filesystem memory\nreclaim.  We don\u0026apos;t want that to happen because it can consume a\nsignificant amount of stack memory.\n\nWorse than that is that it can also deadlock: for example, in several\nplaces, gfs2_unstuff_dinode() is called inside filesystem transactions.\nThis calls filemap_grab_folio(), which can allocate a new folio, which\ncan trigger memory reclaim.  If memory reclaim recurses into the\nfilesystem and starts another transaction, a deadlock will ensue.\n\nTo fix these kinds of problems, prevent memory reclaim from recursing\ninto filesystem code by making sure that the gfp_mask of inode address\nspaces doesn\u0026apos;t include __GFP_FS.\n\nThe \u0026quot;meta\u0026quot; and resource group address spaces were already using GFP_NOFS\nas their gfp_mask (which doesn\u0026apos;t include __GFP_FS).  The default value\nof GFP_HIGHUSER_MOVABLE is less restrictive than GFP_NOFS, though.  To\navoid being overly limiting, use the default value and only knock off\nthe __GFP_FS flag.  I\u0026apos;m not sure if this will actually make a\ndifference, but it also shouldn\u0026apos;t hurt.\n\nThis patch is loosely based on commit ad22c7a043c2 (\u0026quot;xfs: prevent stack\noverflows from page cache allocation\u0026quot;).\n\nFixes xfstest generic/273.(CVE-2025-68356)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nwifi: rtl818x: rtl8187: Fix potential buffer underflow in rtl8187_rx_cb()\n\nThe rtl8187_rx_cb() calculates the rx descriptor header address\nby subtracting its size from the skb tail pointer.\nHowever, it does not validate if the received packet\n(skb-\u0026gt;len from urb-\u0026gt;actual_length) is large enough to contain this\nheader.\n\nIf a truncated packet is received, this will lead to a buffer\nunderflow, reading memory before the start of the skb data area,\nand causing a kernel panic.\n\nAdd length checks for both rtl8187 and rtl8187b descriptor headers\nbefore attempting to access them, dropping the packet cleanly if the\ncheck fails.(CVE-2025-68362)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nbpf: Check skb-\u0026gt;transport_header is set in bpf_skb_check_mtu\n\nThe bpf_skb_check_mtu helper needs to use skb-\u0026gt;transport_header when\nthe BPF_MTU_CHK_SEGS flag is used:\n\n\tbpf_skb_check_mtu(skb, ifindex, \u0026amp;mtu_len, 0, BPF_MTU_CHK_SEGS)\n\nThe transport_header is not always set. There is a WARN_ON_ONCE\nreport when CONFIG_DEBUG_NET is enabled + skb-\u0026gt;gso_size is set +\nbpf_prog_test_run is used:\n\nWARNING: CPU: 1 PID: 2216 at ./include/linux/skbuff.h:3071\n skb_gso_validate_network_len\n bpf_skb_check_mtu\n bpf_prog_3920e25740a41171_tc_chk_segs_flag # A test in the next patch\n bpf_test_run\n bpf_prog_test_run_skb\n\nFor a normal ingress skb (not test_run), skb_reset_transport_header\nis performed but there is plan to avoid setting it as described in\ncommit 2170a1f09148 (\u0026quot;net: no longer reset transport_header in __netif_receive_skb_core()\u0026quot;).\n\nThis patch fixes the bpf helper by checking\nskb_transport_header_was_set(). The check is done just before\nskb-\u0026gt;transport_header is used, to avoid breaking the existing bpf prog.\nThe WARN_ON_ONCE is limited to bpf_prog_test_run, so targeting bpf-next.(CVE-2025-68363)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ncoresight: ETR: Fix ETR buffer use-after-free issue\n\nWhen ETR is enabled as CS_MODE_SYSFS, if the buffer size is changed\nand enabled again, currently sysfs_buf will point to the newly\nallocated memory(buf_new) and free the old memory(buf_old). But the\netr_buf that is being used by the ETR remains pointed to buf_old, not\nupdated to buf_new. In this case, it will result in a memory\nuse-after-free issue.\n\nFix this by checking ETR\u0026apos;s mode before updating and releasing buf_old,\nif the mode is CS_MODE_SYSFS, then skip updating and releasing it.(CVE-2025-68376)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nbpf: Fix stackmap overflow check in __bpf_get_stackid()\n\nSyzkaller reported a KASAN slab-out-of-bounds write in __bpf_get_stackid()\nwhen copying stack trace data. The issue occurs when the perf trace\n contains more stack entries than the stack map bucket can hold,\n leading to an out-of-bounds write in the bucket\u0026apos;s data array.(CVE-2025-68378)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ncrypto: asymmetric_keys - prevent overflow in asymmetric_key_generate_id\n\nUse check_add_overflow() to guard against potential integer overflows\nwhen adding the binary blob lengths and the size of an asymmetric_key_id\nstructure and return ERR_PTR(-EOVERFLOW) accordingly. This prevents a\npossible buffer overflow when copying data from potentially malicious\nX.509 certificate fields that can be arbitrarily large, such as ASN.1\nINTEGER serial numbers, issuer names, etc.(CVE-2025-68724)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nbpf: Do not let BPF test infra emit invalid GSO types to stack\n\nYinhao et al. reported that their fuzzer tool was able to trigger a\nskb_warn_bad_offload() from netif_skb_features() -\u0026gt; gso_features_check().\nWhen a BPF program - triggered via BPF test infra - pushes the packet\nto the loopback device via bpf_clone_redirect() then mentioned offload\nwarning can be seen. GSO-related features are then rightfully disabled.\n\nWe get into this situation due to convert___skb_to_skb() setting\ngso_segs and gso_size but not gso_type. Technically, it makes sense\nthat this warning triggers since the GSO properties are malformed due\nto the gso_type. Potentially, the gso_type could be marked non-trustworthy\nthrough setting it at least to SKB_GSO_DODGY without any other specific\nassumptions, but that also feels wrong given we should not go further\ninto the GSO engine in the first place.\n\nThe checks were added in 121d57af308d (\u0026quot;gso: validate gso_type in GSO\nhandlers\u0026quot;) because there were malicious (syzbot) senders that combine\na protocol with a non-matching gso_type. If we would want to drop such\npackets, gso_features_check() currently only returns feature flags via\nnetif_skb_features(), so one location for potentially dropping such skbs\ncould be validate_xmit_unreadable_skb(), but then otoh it would be\nan additional check in the fast-path for a very corner case. Given\nbpf_clone_redirect() is the only place where BPF test infra could emit\nsuch packets, lets reject them right there.(CVE-2025-68725)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nisdn: mISDN: hfcsusb: fix memory leak in hfcsusb_probe()\n\nIn hfcsusb_probe(), the memory allocated for ctrl_urb gets leaked when\nsetup_instance() fails with an error code. Fix that by freeing the urb\nbefore freeing the hw structure. Also change the error paths to use the\ngoto ladder style.\n\nCompile tested only. Issue found using a prototype static analysis tool.(CVE-2025-68734)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nscsi: qla2xxx: Fix improper freeing of purex item\n\nIn qla2xxx_process_purls_iocb(), an item is allocated via\nqla27xx_copy_multiple_pkt(), which internally calls\nqla24xx_alloc_purex_item().\n\nThe qla24xx_alloc_purex_item() function may return a pre-allocated item\nfrom a per-adapter pool for small allocations, instead of dynamically\nallocating memory with kzalloc().\n\nAn error handling path in qla2xxx_process_purls_iocb() incorrectly uses\nkfree() to release the item. If the item was from the pre-allocated\npool, calling kfree() on it is a bug that can lead to memory corruption.\n\nFix this by using the correct deallocation function,\nqla24xx_free_purex_item(), which properly handles both dynamically\nallocated and pre-allocated items.(CVE-2025-68741)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nbpf: Free special fields when update [lru_,]percpu_hash maps\n\nAs [lru_,]percpu_hash maps support BPF_KPTR_{REF,PERCPU}, missing\ncalls to \u0026apos;bpf_obj_free_fields()\u0026apos; in \u0026apos;pcpu_copy_value()\u0026apos; could cause the\nmemory referenced by BPF_KPTR_{REF,PERCPU} fields to be held until the\nmap gets freed.\n\nFix this by calling \u0026apos;bpf_obj_free_fields()\u0026apos; after\n\u0026apos;copy_map_value[,_long]()\u0026apos; in \u0026apos;pcpu_copy_value()\u0026apos;.(CVE-2025-68744)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nscsi: qla2xxx: Clear cmds after chip reset\n\nCommit aefed3e5548f (\u0026quot;scsi: qla2xxx: target: Fix offline port handling\nand host reset handling\u0026quot;) caused two problems:\n\n1. Commands sent to FW, after chip reset got stuck and never freed as FW\n   is not going to respond to them anymore.\n\n2. BUG_ON(cmd-\u0026gt;sg_mapped) in qlt_free_cmd().  Commit 26f9ce53817a\n   (\u0026quot;scsi: qla2xxx: Fix missed DMA unmap for aborted commands\u0026quot;)\n   attempted to fix this, but introduced another bug under different\n   circumstances when two different CPUs were racing to call\n   qlt_unmap_sg() at the same time: BUG_ON(!valid_dma_direction(dir)) in\n   dma_unmap_sg_attrs().\n\nSo revert \u0026quot;scsi: qla2xxx: Fix missed DMA unmap for aborted commands\u0026quot; and\npartially revert \u0026quot;scsi: qla2xxx: target: Fix offline port handling and\nhost reset handling\u0026quot; at __qla2x00_abort_all_cmds.(CVE-2025-68745)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nblock: Use RCU in blk_mq_[un]quiesce_tagset() instead of set-\u0026gt;tag_list_lock\n\nblk_mq_{add,del}_queue_tag_set() functions add and remove queues from\ntagset, the functions make sure that tagset and queues are marked as\nshared when two or more queues are attached to the same tagset.\nInitially a tagset starts as unshared and when the number of added\nqueues reaches two, blk_mq_add_queue_tag_set() marks it as shared along\nwith all the queues attached to it. When the number of attached queues\ndrops to 1 blk_mq_del_queue_tag_set() need to mark both the tagset and\nthe remaining queues as unshared.\n\nBoth functions need to freeze current queues in tagset before setting on\nunsetting BLK_MQ_F_TAG_QUEUE_SHARED flag. While doing so, both functions\nhold set-\u0026gt;tag_list_lock mutex, which makes sense as we do not want\nqueues to be added or deleted in the process. This used to work fine\nuntil commit 98d81f0df70c (\u0026quot;nvme: use blk_mq_[un]quiesce_tagset\u0026quot;)\nmade the nvme driver quiesce tagset instead of quiscing individual\nqueues. blk_mq_quiesce_tagset() does the job and quiesce the queues in\nset-\u0026gt;tag_list while holding set-\u0026gt;tag_list_lock also.\n\nThis results in deadlock between two threads with these stacktraces:\n\n  __schedule+0x47c/0xbb0\n  ? timerqueue_add+0x66/0xb0\n  schedule+0x1c/0xa0\n  schedule_preempt_disabled+0xa/0x10\n  __mutex_lock.constprop.0+0x271/0x600\n  blk_mq_quiesce_tagset+0x25/0xc0\n  nvme_dev_disable+0x9c/0x250\n  nvme_timeout+0x1fc/0x520\n  blk_mq_handle_expired+0x5c/0x90\n  bt_iter+0x7e/0x90\n  blk_mq_queue_tag_busy_iter+0x27e/0x550\n  ? __blk_mq_complete_request_remote+0x10/0x10\n  ? __blk_mq_complete_request_remote+0x10/0x10\n  ? __call_rcu_common.constprop.0+0x1c0/0x210\n  blk_mq_timeout_work+0x12d/0x170\n  process_one_work+0x12e/0x2d0\n  worker_thread+0x288/0x3a0\n  ? rescuer_thread+0x480/0x480\n  kthread+0xb8/0xe0\n  ? kthread_park+0x80/0x80\n  ret_from_fork+0x2d/0x50\n  ? kthread_park+0x80/0x80\n  ret_from_fork_asm+0x11/0x20\n\n  __schedule+0x47c/0xbb0\n  ? xas_find+0x161/0x1a0\n  schedule+0x1c/0xa0\n  blk_mq_freeze_queue_wait+0x3d/0x70\n  ? destroy_sched_domains_rcu+0x30/0x30\n  blk_mq_update_tag_set_shared+0x44/0x80\n  blk_mq_exit_queue+0x141/0x150\n  del_gendisk+0x25a/0x2d0\n  nvme_ns_remove+0xc9/0x170\n  nvme_remove_namespaces+0xc7/0x100\n  nvme_remove+0x62/0x150\n  pci_device_remove+0x23/0x60\n  device_release_driver_internal+0x159/0x200\n  unbind_store+0x99/0xa0\n  kernfs_fop_write_iter+0x112/0x1e0\n  vfs_write+0x2b1/0x3d0\n  ksys_write+0x4e/0xb0\n  do_syscall_64+0x5b/0x160\n  entry_SYSCALL_64_after_hwframe+0x4b/0x53\n\nThe top stacktrace is showing nvme_timeout() called to handle nvme\ncommand timeout. timeout handler is trying to disable the controller and\nas a first step, it needs to blk_mq_quiesce_tagset() to tell blk-mq not\nto call queue callback handlers. The thread is stuck waiting for\nset-\u0026gt;tag_list_lock as it tries to walk the queues in set-\u0026gt;tag_list.\n\nThe lock is held by the second thread in the bottom stack which is\nwaiting for one of queues to be frozen. The queue usage counter will\ndrop to zero after nvme_timeout() finishes, and this will not happen\nbecause the thread will wait for this mutex forever.\n\nGiven that [un]quiescing queue is an operation that does not need to\nsleep, update blk_mq_[un]quiesce_tagset() to use RCU instead of taking\nset-\u0026gt;tag_list_lock, update blk_mq_{add,del}_queue_tag_set() to use RCU\nsafe list operations. Also, delete INIT_LIST_HEAD(\u0026amp;q-\u0026gt;tag_set_list)\nin blk_mq_del_queue_tag_set() because we can not re-initialize it while\nthe list is being traversed under RCU. The deleted queue will not be\nadded/deleted to/from a tagset and it will be freed in blk_free_queue()\nafter the end of RCU grace period.(CVE-2025-68756)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nsched/deadline: only set free_cpus for online runqueues\n\nCommit 16b269436b72 (\u0026quot;sched/deadline: Modify cpudl::free_cpus\nto reflect rd-\u0026gt;online\u0026quot;) introduced the cpudl_set/clear_freecpu\nfunctions to allow the cpu_dl::free_cpus mask to be manipulated\nby the deadline scheduler class rq_on/offline callbacks so the\nmask would also reflect this state.\n\nCommit 9659e1eeee28 (\u0026quot;sched/deadline: Remove cpu_active_mask\nfrom cpudl_find()\u0026quot;) removed the check of the cpu_active_mask to\nsave some processing on the premise that the cpudl::free_cpus\nmask already reflected the runqueue online state.\n\nUnfortunately, there are cases where it is possible for the\ncpudl_clear function to set the free_cpus bit for a CPU when the\ndeadline runqueue is offline. When this occurs while a CPU is\nconnected to the default root domain the flag may retain the bad\nstate after the CPU has been unplugged. Later, a different CPU\nthat is transitioning through the default root domain may push a\ndeadline task to the powered down CPU when cpudl_find sees its\nfree_cpus bit is set. If this happens the task will not have the\nopportunity to run.\n\nOne example is outlined here:\nhttps://lore.kernel.org/lkml/(CVE-2025-68780)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nscsi: target: Reset t_task_cdb pointer in error case\n\nIf allocation of cmd-\u0026gt;t_task_cdb fails, it remains NULL but is later\ndereferenced in the \u0026apos;err\u0026apos; path.\n\nIn case of error, reset NULL t_task_cdb value to point at the default\nfixed-size buffer.\n\nFound by Linux Verification Center (linuxtesting.org) with SVACE.(CVE-2025-68782)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\niomap: adjust read range correctly for non-block-aligned positions\n\niomap_adjust_read_range() assumes that the position and length passed in\nare block-aligned. This is not always the case however, as shown in the\nsyzbot generated case for erofs. This causes too many bytes to be\nskipped for uptodate blocks, which results in returning the incorrect\nposition and length to read in. If all the blocks are uptodate, this\nunderflows length and returns a position beyond the folio.\n\nFix the calculation to also take into account the block offset when\ncalculating how many bytes can be skipped for uptodate blocks.(CVE-2025-68794)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nNFSD: NFSv4 file creation neglects setting ACL\n\nAn NFSv4 client that sets an ACL with a named principal during file\ncreation retrieves the ACL afterwards, and finds that it is only a\ndefault ACL (based on the mode bits) and not the ACL that was\nrequested during file creation. This violates RFC 8881 section\n6.4.1.3: \u0026quot;the ACL attribute is set as given\u0026quot;.\n\nThe issue occurs in nfsd_create_setattr(), which calls\nnfsd_attrs_valid() to determine whether to call nfsd_setattr().\nHowever, nfsd_attrs_valid() checks only for iattr changes and\nsecurity labels, but not POSIX ACLs. When only an ACL is present,\nthe function returns false, nfsd_setattr() is skipped, and the\nPOSIX ACL is never applied to the inode.\n\nSubsequently, when the client retrieves the ACL, the server finds\nno POSIX ACL on the inode and returns one generated from the file\u0026apos;s\nmode bits rather than returning the originally-specified ACL.(CVE-2025-68803)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nio_uring: fix filename leak in __io_openat_prep()\n\n __io_openat_prep() allocates a struct filename using getname(). However,\nfor the condition of the file being installed in the fixed file table as\nwell as having O_CLOEXEC flag set, the function returns early. At that\npoint, the request doesn\u0026apos;t have REQ_F_NEED_CLEANUP flag set. Due to this,\nthe memory for the newly allocated struct filename is not cleaned up,\ncausing a memory leak.\n\nFix this by setting the REQ_F_NEED_CLEANUP for the request just after the\nsuccessful getname() call, so that when the request is torn down, the\nfilename will be cleaned up, along with other resources needing cleanup.(CVE-2025-68814)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnet/mlx5: fw_tracer, Validate format string parameters\n\nAdd validation for format string parameters in the firmware tracer to\nprevent potential security vulnerabilities and crashes from malformed\nformat strings received from firmware.\n\nThe firmware tracer receives format strings from the device firmware and\nuses them to format trace messages. Without proper validation, bad\nfirmware could provide format strings with invalid format specifiers\n(e.g., %s, %p, %n) that could lead to crashes, or other undefined\nbehavior.\n\nAdd mlx5_tracer_validate_params() to validate that all format specifiers\nin trace strings are limited to safe integer/hex formats (%x, %d, %i,\n%u, %llx, %lx, etc.). Reject strings containing other format types that\ncould be used to access arbitrary memory or cause crashes.\nInvalid format strings are added to the trace output for visibility with\n\u0026quot;BAD_FORMAT: \u0026quot; prefix.(CVE-2025-68816)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nksmbd: fix use-after-free in ksmbd_tree_connect_put under concurrency\n\nUnder high concurrency, A tree-connection object (tcon) is freed on\na disconnect path while another path still holds a reference and later\nexecutes *_put()/write on it.(CVE-2025-68817)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nscsi: Revert \u0026quot;scsi: qla2xxx: Perform lockless command completion in abort path\u0026quot;\n\nThis reverts commit 0367076b0817d5c75dfb83001ce7ce5c64d803a9.\n\nThe commit being reverted added code to __qla2x00_abort_all_cmds() to\ncall sp-\u0026gt;done() without holding a spinlock.  But unlike the older code\nbelow it, this new code failed to check sp-\u0026gt;cmd_type and just assumed\nTYPE_SRB, which results in a jump to an invalid pointer in target-mode\nwith TYPE_TGT_CMD:\n\nqla2xxx [0000:65:00.0]-d034:8: qla24xx_do_nack_work create sess success\n  0000000009f7a79b\nqla2xxx [0000:65:00.0]-5003:8: ISP System Error - mbx1=1ff5h mbx2=10h\n  mbx3=0h mbx4=0h mbx5=191h mbx6=0h mbx7=0h.\nqla2xxx [0000:65:00.0]-d01e:8: -\u0026gt; fwdump no buffer\nqla2xxx [0000:65:00.0]-f03a:8: qla_target(0): System error async event\n  0x8002 occurred\nqla2xxx [0000:65:00.0]-00af:8: Performing ISP error recovery -\n  ha=0000000058183fda.\nBUG: kernel NULL pointer dereference, address: 0000000000000000\nPF: supervisor instruction fetch in kernel mode\nPF: error_code(0x0010) - not-present page\nPGD 0 P4D 0\nOops: 0010 [#1] SMP\nCPU: 2 PID: 9446 Comm: qla2xxx_8_dpc Tainted: G           O       6.1.133 #1\nHardware name: Supermicro Super Server/X11SPL-F, BIOS 4.2 12/15/2023\nRIP: 0010:0x0\nCode: Unable to access opcode bytes at 0xffffffffffffffd6.\nRSP: 0018:ffffc90001f93dc8 EFLAGS: 00010206\nRAX: 0000000000000282 RBX: 0000000000000355 RCX: ffff88810d16a000\nRDX: ffff88810dbadaa8 RSI: 0000000000080000 RDI: ffff888169dc38c0\nRBP: ffff888169dc38c0 R08: 0000000000000001 R09: 0000000000000045\nR10: ffffffffa034bdf0 R11: 0000000000000000 R12: ffff88810800bb40\nR13: 0000000000001aa8 R14: ffff888100136610 R15: ffff8881070f7400\nFS:  0000000000000000(0000) GS:ffff88bf80080000(0000) knlGS:0000000000000000\nCS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033\nCR2: ffffffffffffffd6 CR3: 000000010c8ff006 CR4: 00000000003706e0\nDR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000\nDR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400\nCall Trace:\n \u0026lt;TASK\u0026gt;\n ? __die+0x4d/0x8b\n ? page_fault_oops+0x91/0x180\n ? trace_buffer_unlock_commit_regs+0x38/0x1a0\n ? exc_page_fault+0x391/0x5e0\n ? asm_exc_page_fault+0x22/0x30\n __qla2x00_abort_all_cmds+0xcb/0x3e0 [qla2xxx_scst]\n qla2x00_abort_all_cmds+0x50/0x70 [qla2xxx_scst]\n qla2x00_abort_isp_cleanup+0x3b7/0x4b0 [qla2xxx_scst]\n qla2x00_abort_isp+0xfd/0x860 [qla2xxx_scst]\n qla2x00_do_dpc+0x581/0xa40 [qla2xxx_scst]\n kthread+0xa8/0xd0\n \u0026lt;/TASK\u0026gt;\n\nThen commit 4475afa2646d (\u0026quot;scsi: qla2xxx: Complete command early within\nlock\u0026quot;) added the spinlock back, because not having the lock caused a\nrace and a crash.  But qla2x00_abort_srb() in the switch below already\nchecks for qla2x00_chip_is_down() and handles it the same way, so the\ncode above the switch is now redundant and still buggy in target-mode.\nRemove it.(CVE-2025-68818)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nshmem: fix recovery on rename failures\n\nmaple_tree insertions can fail if we are seriously short on memory;\nsimple_offset_rename() does not recover well if it runs into that.\nThe same goes for simple_offset_rename_exchange().\n\nMoreover, shmem_whiteout() expects that if it succeeds, the caller will\nprogress to d_move(), i.e. that shmem_rename2() won\u0026apos;t fail past the\nsuccessful call of shmem_whiteout().\n\nNot hard to fix, fortunately - mtree_store() can\u0026apos;t fail if the index we\nare trying to store into is already present in the tree as a singleton.\n\nFor simple_offset_rename_exchange() that\u0026apos;s enough - we just need to be\ncareful about the order of operations.\n\nFor simple_offset_rename() solution is to preinsert the target into the\ntree for new_dir; the rest can be done without any potentially failing\noperations.\n\nThat preinsertion has to be done in shmem_rename2() rather than in\nsimple_offset_rename() itself - otherwise we\u0026apos;d need to deal with the\npossibility of failure after successful shmem_whiteout().(CVE-2025-71072)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ntpm: Cap the number of PCR banks\n\ntpm2_get_pcr_allocation() does not cap any upper limit for the number of\nbanks. Cap the limit to eight banks so that out of bounds values coming\nfrom external I/O cause on only limited harm.(CVE-2025-71077)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nKVM: x86: Fix VM hard lockup after prolonged inactivity with periodic HV timer\n\nWhen advancing the target expiration for the guest\u0026apos;s APIC timer in periodic\nmode, set the expiration to \u0026quot;now\u0026quot; if the target expiration is in the past\n(similar to what is done in update_target_expiration()).  Blindly adding\nthe period to the previous target expiration can result in KVM generating\na practically unbounded number of hrtimer IRQs due to programming an\nexpired timer over and over.  In extreme scenarios, e.g. if userspace\npauses/suspends a VM for an extended duration, this can even cause hard\nlockups in the host.\n\nCurrently, the bug only affects Intel CPUs when using the hypervisor timer\n(HV timer), a.k.a. the VMX preemption timer.  Unlike the software timer,\na.k.a. hrtimer, which KVM keeps running even on exits to userspace, the\nHV timer only runs while the guest is active.  As a result, if the vCPU\ndoes not run for an extended duration, there will be a huge gap between\nthe target expiration and the current time the vCPU resumes running.\nBecause the target expiration is incremented by only one period on each\ntimer expiration, this leads to a series of timer expirations occurring\nrapidly after the vCPU/VM resumes.\n\nMore critically, when the vCPU first triggers a periodic HV timer\nexpiration after resuming, advancing the expiration by only one period\nwill result in a target expiration in the past.  As a result, the delta\nmay be calculated as a negative value.  When the delta is converted into\nan absolute value (tscdeadline is an unsigned u64), the resulting value\ncan overflow what the HV timer is capable of programming.  I.e. the large\nvalue will exceed the VMX Preemption Timer\u0026apos;s maximum bit width of\ncpu_preemption_timer_multi + 32, and thus cause KVM to switch from the\nHV timer to the software timer (hrtimers).\n\nAfter switching to the software timer, periodic timer expiration callbacks\nmay be executed consecutively within a single clock interrupt handler,\nbecause hrtimers honors KVM\u0026apos;s request for an expiration in the past and\nimmediately re-invokes KVM\u0026apos;s callback after reprogramming.  And because\nthe interrupt handler runs with IRQs disabled, restarting KVM\u0026apos;s hrtimer\nover and over until the target expiration is advanced to \u0026quot;now\u0026quot; can result\nin a hard lockup.\n\nE.g. the following hard lockup was triggered in the host when running a\nWindows VM (only relevant because it used the APIC timer in periodic mode)\nafter resuming the VM from a long suspend (in the host).\n\n  NMI watchdog: Watchdog detected hard LOCKUP on cpu 45\n  ...\n  RIP: 0010:advance_periodic_target_expiration+0x4d/0x80 [kvm]\n  ...\n  RSP: 0018:ff4f88f5d98d8ef0 EFLAGS: 00000046\n  RAX: fff0103f91be678e RBX: fff0103f91be678e RCX: 00843a7d9e127bcc\n  RDX: 0000000000000002 RSI: 0052ca4003697505 RDI: ff440d5bfbdbd500\n  RBP: ff440d5956f99200 R08: ff2ff2a42deb6a84 R09: 000000000002a6c0\n  R10: 0122d794016332b3 R11: 0000000000000000 R12: ff440db1af39cfc0\n  R13: ff440db1af39cfc0 R14: ffffffffc0d4a560 R15: ff440db1af39d0f8\n  FS:  00007f04a6ffd700(0000) GS:ff440db1af380000(0000) knlGS:000000e38a3b8000\n  CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033\n  CR2: 000000d5651feff8 CR3: 000000684e038002 CR4: 0000000000773ee0\n  PKRU: 55555554\n  Call Trace:\n   \u0026lt;IRQ\u0026gt;\n   apic_timer_fn+0x31/0x50 [kvm]\n   __hrtimer_run_queues+0x100/0x280\n   hrtimer_interrupt+0x100/0x210\n   ? ttwu_do_wakeup+0x19/0x160\n   smp_apic_timer_interrupt+0x6a/0x130\n   apic_timer_interrupt+0xf/0x20\n   \u0026lt;/IRQ\u0026gt;\n\nMoreover, if the suspend duration of the virtual machine is not long enough\nto trigger a hard lockup in this scenario, since commit 98c25ead5eda\n(\u0026quot;KVM: VMX: Move preemption timer \u0026lt;=\u0026gt; hrtimer dance to common x86\u0026quot;), KVM\nwill continue using the software timer until the guest reprograms the APIC\ntimer in some way.  Since the periodic timer does not require frequent APIC\ntimer register programming, the guest may continue to use the software\ntimer in \n---truncated---(CVE-2025-71104)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nlibceph: make decode_pool() more resilient against corrupted osdmaps\n\nIf the osdmap is (maliciously) corrupted such that the encoded length\nof ceph_pg_pool envelope is less than what is expected for a particular\nencoding version, out-of-bounds reads may ensue because the only bounds\ncheck that is there is based on that length value.\n\nThis patch adds explicit bounds checks for each field that is decoded\nor skipped.(CVE-2025-71116)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ncrypto: seqiv - Do not use req-\u0026gt;iv after crypto_aead_encrypt\n\nAs soon as crypto_aead_encrypt is called, the underlying request\nmay be freed by an asynchronous completion.  Thus dereferencing\nreq-\u0026gt;iv after it returns is invalid.\n\nInstead of checking req-\u0026gt;iv against info, create a new variable\nunaligned_info and use it for that purpose instead.(CVE-2025-71131)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nmm/page_alloc: change all pageblocks migrate type on coalescing\n\nWhen a page is freed it coalesces with a buddy into a higher order page\nwhile possible.  When the buddy page migrate type differs, it is expected\nto be updated to match the one of the page being freed.\n\nHowever, only the first pageblock of the buddy page is updated, while the\nrest of the pageblocks are left unchanged.\n\nThat causes warnings in later expand() and other code paths (like below),\nsince an inconsistency between migration type of the list containing the\npage and the page-owned pageblocks migration types is introduced.\n\n[  308.986589] ------------[ cut here ]------------\n[  308.987227] page type is 0, passed migratetype is 1 (nr=256)\n[  308.987275] WARNING: CPU: 1 PID: 5224 at mm/page_alloc.c:812 expand+0x23c/0x270\n[  308.987293] Modules linked in: algif_hash(E) af_alg(E) nft_fib_inet(E) nft_fib_ipv4(E) nft_fib_ipv6(E) nft_fib(E) nft_reject_inet(E) nf_reject_ipv4(E) nf_reject_ipv6(E) nft_reject(E) nft_ct(E) nft_chain_nat(E) nf_nat(E) nf_conntrack(E) nf_defrag_ipv6(E) nf_defrag_ipv4(E) nf_tables(E) s390_trng(E) vfio_ccw(E) mdev(E) vfio_iommu_type1(E) vfio(E) sch_fq_codel(E) drm(E) i2c_core(E) drm_panel_orientation_quirks(E) loop(E) nfnetlink(E) vsock_loopback(E) vmw_vsock_virtio_transport_common(E) vsock(E) ctcm(E) fsm(E) diag288_wdt(E) watchdog(E) zfcp(E) scsi_transport_fc(E) ghash_s390(E) prng(E) aes_s390(E) des_generic(E) des_s390(E) libdes(E) sha3_512_s390(E) sha3_256_s390(E) sha_common(E) paes_s390(E) crypto_engine(E) pkey_cca(E) pkey_ep11(E) zcrypt(E) rng_core(E) pkey_pckmo(E) pkey(E) autofs4(E)\n[  308.987439] Unloaded tainted modules: hmac_s390(E):2\n[  308.987650] CPU: 1 UID: 0 PID: 5224 Comm: mempig_verify Kdump: loaded Tainted: G            E       6.18.0-gcc-bpf-debug #431 PREEMPT\n[  308.987657] Tainted: [E]=UNSIGNED_MODULE\n[  308.987661] Hardware name: IBM 3906 M04 704 (z/VM 7.3.0)\n[  308.987666] Krnl PSW : 0404f00180000000 00000349976fa600 (expand+0x240/0x270)\n[  308.987676]            R:0 T:1 IO:0 EX:0 Key:0 M:1 W:0 P:0 AS:3 CC:3 PM:0 RI:0 EA:3\n[  308.987682] Krnl GPRS: 0000034980000004 0000000000000005 0000000000000030 000003499a0e6d88\n[  308.987688]            0000000000000005 0000034980000005 000002be803ac000 0000023efe6c8300\n[  308.987692]            0000000000000008 0000034998d57290 000002be00000100 0000023e00000008\n[  308.987696]            0000000000000000 0000000000000000 00000349976fa5fc 000002c99b1eb6f0\n[  308.987708] Krnl Code: 00000349976fa5f0: c020008a02f2\tlarl\t%r2,000003499883abd4\n                          00000349976fa5f6: c0e5ffe3f4b5\tbrasl\t%r14,0000034997378f60\n                         #00000349976fa5fc: af000000\t\tmc\t0,0\n                         \u0026gt;00000349976fa600: a7f4ff4c\t\tbrc\t15,00000349976fa498\n                          00000349976fa604: b9040026\t\tlgr\t%r2,%r6\n                          00000349976fa608: c0300088317f\tlarl\t%r3,0000034998800906\n                          00000349976fa60e: c0e5fffdb6e1\tbrasl\t%r14,00000349976b13d0\n                          00000349976fa614: af000000\t\tmc\t0,0\n[  308.987734] Call Trace:\n[  308.987738]  [\u0026lt;00000349976fa600\u0026gt;] expand+0x240/0x270\n[  308.987744] ([\u0026lt;00000349976fa5fc\u0026gt;] expand+0x23c/0x270)\n[  308.987749]  [\u0026lt;00000349976ff95e\u0026gt;] rmqueue_bulk+0x71e/0x940\n[  308.987754]  [\u0026lt;00000349976ffd7e\u0026gt;] __rmqueue_pcplist+0x1fe/0x2a0\n[  308.987759]  [\u0026lt;0000034997700966\u0026gt;] rmqueue.isra.0+0xb46/0xf40\n[  308.987763]  [\u0026lt;0000034997703ec8\u0026gt;] get_page_from_freelist+0x198/0x8d0\n[  308.987768]  [\u0026lt;0000034997706fa8\u0026gt;] __alloc_frozen_pages_noprof+0x198/0x400\n[  308.987774]  [\u0026lt;00000349977536f8\u0026gt;] alloc_pages_mpol+0xb8/0x220\n[  308.987781]  [\u0026lt;0000034997753bf6\u0026gt;] folio_alloc_mpol_noprof+0x26/0xc0\n[  308.987786]  [\u0026lt;0000034997753e4c\u0026gt;] vma_alloc_folio_noprof+0x6c/0xa0\n[  308.987791]  [\u0026lt;0000034997775b22\u0026gt;] vma_alloc_anon_folio_pmd+0x42/0x240\n[  308.987799]  [\u0026lt;000003499777bfea\u0026gt;] __do_huge_pmd_anonymous_page+0x3a/0x210\n[  308.987804]  [\u0026lt;00000349976cb0\n---truncated---(CVE-2025-71134)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nKEYS: trusted: Fix a memory leak in tpm2_load_cmd\n\n\u0026apos;tpm2_load_cmd\u0026apos; allocates a tempoary blob indirectly via \u0026apos;tpm2_key_decode\u0026apos;\nbut it is not freed in the failure paths. Address this by wrapping the blob\ninto with a cleanup helper.(CVE-2025-71147)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nio_uring/poll: correctly handle io_poll_add() return value on update\n\nWhen the core of io_uring was updated to handle completions\nconsistently and with fixed return codes, the POLL_REMOVE opcode\nwith updates got slightly broken. If a POLL_ADD is pending and\nthen POLL_REMOVE is used to update the events of that request, if that\nupdate causes the POLL_ADD to now trigger, then that completion is lost\nand a CQE is never posted.\n\nAdditionally, ensure that if an update does cause an existing POLL_ADD\nto complete, that the completion value isn\u0026apos;t always overwritten with\n-ECANCELED. For that case, whatever io_poll_add() set the value to\nshould just be retained.(CVE-2025-71149)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nksmbd: Fix refcount leak when invalid session is found on session lookup\n\nWhen a session is found but its state is not SMB2_SESSION_VALID, It\nindicates that no valid session was found, but it is missing to decrement\nthe reference count acquired by the session lookup, which results in\na reference count leak. This patch fixes the issue by explicitly calling\nksmbd_user_session_put to release the reference to the session.(CVE-2025-71150)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnet: dsa: properly keep track of conduit reference\n\nProblem description\n-------------------\n\nDSA has a mumbo-jumbo of reference handling of the conduit net device\nand its kobject which, sadly, is just wrong and doesn\u0026apos;t make sense.\n\nThere are two distinct problems.\n\n1. The OF path, which uses of_find_net_device_by_node(), never releases\n   the elevated refcount on the conduit\u0026apos;s kobject. Nominally, the OF and\n   non-OF paths should result in objects having identical reference\n   counts taken, and it is already suspicious that\n   dsa_dev_to_net_device() has a put_device() call which is missing in\n   dsa_port_parse_of(), but we can actually even verify that an issue\n   exists. With CONFIG_DEBUG_KOBJECT_RELEASE=y, if we run this command\n   \u0026quot;before\u0026quot; and \u0026quot;after\u0026quot; applying this patch:\n\n(unbind the conduit driver for net device eno2)\necho 0000:00:00.2 \u0026gt; /sys/bus/pci/drivers/fsl_enetc/unbind\n\nwe see these lines in the output diff which appear only with the patch\napplied:\n\nkobject: \u0026apos;eno2\u0026apos; (ffff002009a3a6b8): kobject_release, parent 0000000000000000 (delayed 1000)\nkobject: \u0026apos;109\u0026apos; (ffff0020099d59a0): kobject_release, parent 0000000000000000 (delayed 1000)\n\n2. After we find the conduit interface one way (OF) or another (non-OF),\n   it can get unregistered at any time, and DSA remains with a long-lived,\n   but in this case stale, cpu_dp-\u0026gt;conduit pointer. Holding the net\n   device\u0026apos;s underlying kobject isn\u0026apos;t actually of much help, it just\n   prevents it from being freed (but we never need that kobject\n   directly). What helps us to prevent the net device from being\n   unregistered is the parallel netdev reference mechanism (dev_hold()\n   and dev_put()).\n\nActually we actually use that netdev tracker mechanism implicitly on\nuser ports since commit 2f1e8ea726e9 (\u0026quot;net: dsa: link interfaces with\nthe DSA master to get rid of lockdep warnings\u0026quot;), via netdev_upper_dev_link().\nBut time still passes at DSA switch probe time between the initial\nof_find_net_device_by_node() code and the user port creation time, time\nduring which the conduit could unregister itself and DSA wouldn\u0026apos;t know\nabout it.\n\nSo we have to run of_find_net_device_by_node() under rtnl_lock() to\nprevent that from happening, and release the lock only with the netdev\ntracker having acquired the reference.\n\nDo we need to keep the reference until dsa_unregister_switch() /\ndsa_switch_shutdown()?\n1: Maybe yes. A switch device will still be registered even if all user\n   ports failed to probe, see commit 86f8b1c01a0a (\u0026quot;net: dsa: Do not\n   make user port errors fatal\u0026quot;), and the cpu_dp-\u0026gt;conduit pointers\n   remain valid.  I haven\u0026apos;t audited all call paths to see whether they\n   will actually use the conduit in lack of any user port, but if they\n   do, it seems safer to not rely on user ports for that reference.\n2. Definitely yes. We support changing the conduit which a user port is\n   associated to, and we can get into a situation where we\u0026apos;ve moved all\n   user ports away from a conduit, thus no longer hold any reference to\n   it via the net device tracker. But we shouldn\u0026apos;t let it go nonetheless\n   - see the next change in relation to dsa_tree_find_first_conduit()\n   and LAG conduits which disappear.\n   We have to be prepared to return to the physical conduit, so the CPU\n   port must explicitly keep another reference to it. This is also to\n   say: the user ports and their CPU ports may not always keep a\n   reference to the same conduit net device, and both are needed.\n\nAs for the conduit\u0026apos;s kobject for the /sys/class/net/ entry, we don\u0026apos;t\ncare about it, we can release it as soon as we hold the net device\nobject itself.\n\nHistory and blame attribution\n-----------------------------\n\nThe code has been refactored so many times, it is very difficult to\nfollow and properly attribute a blame, but I\u0026apos;ll try to make a short\nhistory which I hope to be correct.\n\nWe have two distinct probing paths:\n- one for OF, introduced in 2016 i\n---truncated---(CVE-2025-71152)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnet: usb: rtl8150: fix memory leak on usb_submit_urb() failure\n\nIn async_set_registers(), when usb_submit_urb() fails, the allocated\n  async_req structure and URB are not freed, causing a memory leak.\n\n  The completion callback async_set_reg_cb() is responsible for freeing\n  these allocations, but it is only called after the URB is successfully\n  submitted and completes (successfully or with error). If submission\n  fails, the callback never runs and the memory is leaked.\n\n  Fix this by freeing both the URB and the request structure in the error\n  path when usb_submit_urb() fails.(CVE-2025-71154)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nscsi: qla2xxx: Fix bsg_done() causing double free\n\nKernel panic observed on system,\n\n[5353358.825191] BUG: unable to handle page fault for address: ff5f5e897b024000\n[5353358.825194] #PF: supervisor write access in kernel mode\n[5353358.825195] #PF: error_code(0x0002) - not-present page\n[5353358.825196] PGD 100006067 P4D 0\n[5353358.825198] Oops: 0002 [#1] PREEMPT SMP NOPTI\n[5353358.825200] CPU: 5 PID: 2132085 Comm: qlafwupdate.sub Kdump: loaded Tainted: G        W    L    -------  ---  5.14.0-503.34.1.el9_5.x86_64 #1\n[5353358.825203] Hardware name: HPE ProLiant DL360 Gen11/ProLiant DL360 Gen11, BIOS 2.44 01/17/2025\n[5353358.825204] RIP: 0010:memcpy_erms+0x6/0x10\n[5353358.825211] RSP: 0018:ff591da8f4f6b710 EFLAGS: 00010246\n[5353358.825212] RAX: ff5f5e897b024000 RBX: 0000000000007090 RCX: 0000000000001000\n[5353358.825213] RDX: 0000000000001000 RSI: ff591da8f4fed090 RDI: ff5f5e897b024000\n[5353358.825214] RBP: 0000000000010000 R08: ff5f5e897b024000 R09: 0000000000000000\n[5353358.825215] R10: ff46cf8c40517000 R11: 0000000000000001 R12: 0000000000008090\n[5353358.825216] R13: ff591da8f4f6b720 R14: 0000000000001000 R15: 0000000000000000\n[5353358.825218] FS:  00007f1e88d47740(0000) GS:ff46cf935f940000(0000) knlGS:0000000000000000\n[5353358.825219] CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033\n[5353358.825220] CR2: ff5f5e897b024000 CR3: 0000000231532004 CR4: 0000000000771ef0\n[5353358.825221] PKRU: 55555554\n[5353358.825222] Call Trace:\n[5353358.825223]  \u0026lt;TASK\u0026gt;\n[5353358.825224]  ? show_trace_log_lvl+0x1c4/0x2df\n[5353358.825229]  ? show_trace_log_lvl+0x1c4/0x2df\n[5353358.825232]  ? sg_copy_buffer+0xc8/0x110\n[5353358.825236]  ? __die_body.cold+0x8/0xd\n[5353358.825238]  ? page_fault_oops+0x134/0x170\n[5353358.825242]  ? kernelmode_fixup_or_oops+0x84/0x110\n[5353358.825244]  ? exc_page_fault+0xa8/0x150\n[5353358.825247]  ? asm_exc_page_fault+0x22/0x30\n[5353358.825252]  ? memcpy_erms+0x6/0x10\n[5353358.825253]  sg_copy_buffer+0xc8/0x110\n[5353358.825259]  qla2x00_process_vendor_specific+0x652/0x1320 [qla2xxx]\n[5353358.825317]  qla24xx_bsg_request+0x1b2/0x2d0 [qla2xxx]\n\nMost routines in qla_bsg.c call bsg_done() only for success cases.\nHowever a few invoke it for failure case as well leading to a double\nfree. Validate before calling bsg_done().(CVE-2025-71238)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nwifi: avoid kernel-infoleak from struct iw_point\n\nstruct iw_point has a 32bit hole on 64bit arches.\n\nstruct iw_point {\n  void __user   *pointer;       /* Pointer to the data  (in user space) */\n  __u16         length;         /* number of fields or size in bytes */\n  __u16         flags;          /* Optional params */\n};\n\nMake sure to zero the structure to avoid disclosing 32bits of kernel data\nto user space.(CVE-2026-22978)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnfsd: provide locking for v4_end_grace\n\nWriting to v4_end_grace can race with server shutdown and result in\nmemory being accessed after it was freed - reclaim_str_hashtbl in\nparticularly.\n\nWe cannot hold nfsd_mutex across the nfsd4_end_grace() call as that is\nheld while client_tracking_op-\u0026gt;init() is called and that can wait for\nan upcall to nfsdcltrack which can write to v4_end_grace, resulting in a\ndeadlock.\n\nnfsd4_end_grace() is also called by the landromat work queue and this\ndoesn\u0026apos;t require locking as server shutdown will stop the work and wait\nfor it before freeing anything that nfsd4_end_grace() might access.\n\nHowever, we must be sure that writing to v4_end_grace doesn\u0026apos;t restart\nthe work item after shutdown has already waited for it.  For this we\nadd a new flag protected with nn-\u0026gt;client_lock.  It is set only while it\nis safe to make client tracking calls, and v4_end_grace only schedules\nwork while the flag is set with the spinlock held.\n\nSo this patch adds a nfsd_net field \u0026quot;client_tracking_active\u0026quot; which is\nset as described.  Another field \u0026quot;grace_end_forced\u0026quot;, is set when\nv4_end_grace is written.  After this is set, and providing\nclient_tracking_active is set, the laundromat is scheduled.\nThis \u0026quot;grace_end_forced\u0026quot; field bypasses other checks for whether the\ngrace period has finished.\n\nThis resolves a race which can result in use-after-free.(CVE-2026-22980)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nlibceph: replace overzealous BUG_ON in osdmap_apply_incremental()\n\nIf the osdmap is (maliciously) corrupted such that the incremental\nosdmap epoch is different from what is expected, there is no need to\nBUG.  Instead, just declare the incremental osdmap to be invalid.(CVE-2026-22990)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nlibceph: return the handler error from mon_handle_auth_done()\n\nCurrently any error from ceph_auth_handle_reply_done() is propagated\nvia finish_auth() but isn\u0026apos;t returned from mon_handle_auth_done().  This\nresults in higher layers learning that (despite the monitor considering\nus to be successfully authenticated) something went wrong in the\nauthentication phase and reacting accordingly, but msgr2 still trying\nto proceed with establishing the session in the background.  In the\ncase of secure mode this can trigger a WARN in setup_crypto() and later\nlead to a NULL pointer dereference inside of prepare_auth_signature().(CVE-2026-22992)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnet/mlx5e: Don\u0026apos;t store mlx5e_priv in mlx5e_dev devlink priv\n\nmlx5e_priv is an unstable structure that can be memset(0) if profile\nattaching fails, mlx5e_priv in mlx5e_dev devlink private is used to\nreference the netdev and mdev associated with that struct. Instead,\nstore netdev directly into mlx5e_dev and get mdev from the containing\nmlx5_adev aux device structure.\n\nThis fixes a kernel oops in mlx5e_remove when switchdev mode fails due\nto change profile failure.\n\n$ devlink dev eswitch set pci/0000:00:03.0 mode switchdev\nError: mlx5_core: Failed setting eswitch to offloads.\ndmesg:\nworkqueue: Failed to create a rescuer kthread for wq \u0026quot;mlx5e\u0026quot;: -EINTR\nmlx5_core 0012:03:00.1: mlx5e_netdev_init_profile:6214:(pid 37199): mlx5e_priv_init failed, err=-12\nmlx5_core 0012:03:00.1 gpu3rdma1: mlx5e_netdev_change_profile: new profile init failed, -12\nworkqueue: Failed to create a rescuer kthread for wq \u0026quot;mlx5e\u0026quot;: -EINTR\nmlx5_core 0012:03:00.1: mlx5e_netdev_init_profile:6214:(pid 37199): mlx5e_priv_init failed, err=-12\nmlx5_core 0012:03:00.1 gpu3rdma1: mlx5e_netdev_change_profile: failed to rollback to orig profile, -12\n\n$ devlink dev reload pci/0000:00:03.0 ==\u0026gt; oops\n\nBUG: kernel NULL pointer dereference, address: 0000000000000520\n #PF: supervisor read access in kernel mode\n #PF: error_code(0x0000) - not-present page\nPGD 0 P4D 0\nOops: Oops: 0000 [#1] SMP NOPTI\nCPU: 3 UID: 0 PID: 521 Comm: devlink Not tainted 6.18.0-rc5+ #117 PREEMPT(voluntary)\nHardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.16.3-2.fc40 04/01/2014\nRIP: 0010:mlx5e_remove+0x68/0x130\nRSP: 0018:ffffc900034838f0 EFLAGS: 00010246\nRAX: ffff88810283c380 RBX: ffff888101874400 RCX: ffffffff826ffc45\nRDX: 0000000000000000 RSI: 0000000000000001 RDI: 0000000000000000\nRBP: ffff888102d789c0 R08: ffff8881007137f0 R09: ffff888100264e10\nR10: ffffc90003483898 R11: ffffc900034838a0 R12: ffff888100d261a0\nR13: ffff888100d261a0 R14: ffff8881018749a0 R15: ffff888101874400\nFS:  00007f8565fea740(0000) GS:ffff88856a759000(0000) knlGS:0000000000000000\nCS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033\nCR2: 0000000000000520 CR3: 000000010b11a004 CR4: 0000000000370ef0\nCall Trace:\n \u0026lt;TASK\u0026gt;\n device_release_driver_internal+0x19c/0x200\n bus_remove_device+0xc6/0x130\n device_del+0x160/0x3d0\n ? devl_param_driverinit_value_get+0x2d/0x90\n mlx5_detach_device+0x89/0xe0\n mlx5_unload_one_devl_locked+0x3a/0x70\n mlx5_devlink_reload_down+0xc8/0x220\n devlink_reload+0x7d/0x260\n devlink_nl_reload_doit+0x45b/0x5a0\n genl_family_rcv_msg_doit+0xe8/0x140(CVE-2026-22996)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnvme-tcp: fix NULL pointer dereferences in nvmet_tcp_build_pdu_iovec\n\nCommit efa56305908b (\u0026quot;nvmet-tcp: Fix a kernel panic when host sends an invalid H2C PDU length\u0026quot;)\nadded ttag bounds checking and data_offset\nvalidation in nvmet_tcp_handle_h2c_data_pdu(), but it did not validate\nwhether the command\u0026apos;s data structures (cmd-\u0026gt;req.sg and cmd-\u0026gt;iov) have\nbeen properly initialized before processing H2C_DATA PDUs.\n\nThe nvmet_tcp_build_pdu_iovec() function dereferences these pointers\nwithout NULL checks. This can be triggered by sending H2C_DATA PDU\nimmediately after the ICREQ/ICRESP handshake, before\nsending a CONNECT command or NVMe write command.\n\nAttack vectors that trigger NULL pointer dereferences:\n1. H2C_DATA PDU sent before CONNECT → both pointers NULL\n2. H2C_DATA PDU for READ command → cmd-\u0026gt;req.sg allocated, cmd-\u0026gt;iov NULL\n3. H2C_DATA PDU for uninitialized command slot → both pointers NULL\n\nThe fix validates both cmd-\u0026gt;req.sg and cmd-\u0026gt;iov before calling\nnvmet_tcp_build_pdu_iovec(). Both checks are required because:\n- Uninitialized commands: both NULL\n- READ commands: cmd-\u0026gt;req.sg allocated, cmd-\u0026gt;iov NULL\n- WRITE commands: both allocated(CVE-2026-22998)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnet/mlx5e: Fix crash on profile change rollback failure\n\nmlx5e_netdev_change_profile can fail to attach a new profile and can\nfail to rollback to old profile, in such case, we could end up with a\ndangling netdev with a fully reset netdev_priv. A retry to change\nprofile, e.g. another attempt to call mlx5e_netdev_change_profile via\nswitchdev mode change, will crash trying to access the now NULL\npriv-\u0026gt;mdev.\n\nThis fix allows mlx5e_netdev_change_profile() to handle previous\nfailures and an empty priv, by not assuming priv is valid.\n\nPass netdev and mdev to all flows requiring\nmlx5e_netdev_change_profile() and avoid passing priv.\nIn mlx5e_netdev_change_profile() check if current priv is valid, and if\nnot, just attach the new profile without trying to access the old one.\n\nThis fixes the following oops, when enabling switchdev mode for the 2nd\ntime after first time failure:\n\n ## Enabling switchdev mode first time:\n\nmlx5_core 0012:03:00.1: E-Switch: Supported tc chains and prios offload\nworkqueue: Failed to create a rescuer kthread for wq \u0026quot;mlx5e\u0026quot;: -EINTR\nmlx5_core 0012:03:00.1: mlx5e_netdev_init_profile:6214:(pid 37199): mlx5e_priv_init failed, err=-12\nmlx5_core 0012:03:00.1 gpu3rdma1: mlx5e_netdev_change_profile: new profile init failed, -12\nworkqueue: Failed to create a rescuer kthread for wq \u0026quot;mlx5e\u0026quot;: -EINTR\nmlx5_core 0012:03:00.1: mlx5e_netdev_init_profile:6214:(pid 37199): mlx5e_priv_init failed, err=-12\nmlx5_core 0012:03:00.1 gpu3rdma1: mlx5e_netdev_change_profile: failed to rollback to orig profile, -12\n                                                                         ^^^^^^^^\nmlx5_core 0000:00:03.0: E-Switch: Disable: mode(LEGACY), nvfs(0), necvfs(0), active vports(0)\n\n ## retry: Enabling switchdev mode 2nd time:\n\nmlx5_core 0000:00:03.0: E-Switch: Supported tc chains and prios offload\nBUG: kernel NULL pointer dereference, address: 0000000000000038\n #PF: supervisor read access in kernel mode\n #PF: error_code(0x0000) - not-present page\nPGD 0 P4D 0\nOops: Oops: 0000 [#1] SMP NOPTI\nCPU: 13 UID: 0 PID: 520 Comm: devlink Not tainted 6.18.0-rc4+ #91 PREEMPT(voluntary)\nHardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.16.3-2.fc40 04/01/2014\nRIP: 0010:mlx5e_detach_netdev+0x3c/0x90\nCode: 50 00 00 f0 80 4f 78 02 48 8b bf e8 07 00 00 48 85 ff 74 16 48 8b 73 78 48 d1 ee 83 e6 01 83 f6 01 40 0f b6 f6 e8 c4 42 00 00 \u0026lt;48\u0026gt; 8b 45 38 48 85 c0 74 08 48 89 df e8 cc 47 40 1e 48 8b bb f0 07\nRSP: 0018:ffffc90000673890 EFLAGS: 00010246\nRAX: 0000000000000000 RBX: ffff8881036a89c0 RCX: 0000000000000000\nRDX: ffff888113f63800 RSI: ffffffff822fe720 RDI: 0000000000000000\nRBP: 0000000000000000 R08: 0000000000002dcd R09: 0000000000000000\nR10: ffffc900006738e8 R11: 00000000ffffffff R12: 0000000000000000\nR13: 0000000000000000 R14: ffff8881036a89c0 R15: 0000000000000000\nFS:  00007fdfb8384740(0000) GS:ffff88856a9d6000(0000) knlGS:0000000000000000\nCS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033\nCR2: 0000000000000038 CR3: 0000000112ae0005 CR4: 0000000000370ef0\nCall Trace:\n \u0026lt;TASK\u0026gt;\n mlx5e_netdev_change_profile+0x45/0xb0\n mlx5e_vport_rep_load+0x27b/0x2d0\n mlx5_esw_offloads_rep_load+0x72/0xf0\n esw_offloads_enable+0x5d0/0x970\n mlx5_eswitch_enable_locked+0x349/0x430\n ? is_mp_supported+0x57/0xb0\n mlx5_devlink_eswitch_mode_set+0x26b/0x430\n devlink_nl_eswitch_set_doit+0x6f/0xf0\n genl_family_rcv_msg_doit+0xe8/0x140\n genl_rcv_msg+0x18b/0x290\n ? __pfx_devlink_nl_pre_doit+0x10/0x10\n ? __pfx_devlink_nl_eswitch_set_doit+0x10/0x10\n ? __pfx_devlink_nl_post_doit+0x10/0x10\n ? __pfx_genl_rcv_msg+0x10/0x10\n netlink_rcv_skb+0x52/0x100\n genl_rcv+0x28/0x40\n netlink_unicast+0x282/0x3e0\n ? __alloc_skb+0xd6/0x190\n netlink_sendmsg+0x1f7/0x430\n __sys_sendto+0x213/0x220\n ? __sys_recvmsg+0x6a/0xd0\n __x64_sys_sendto+0x24/0x30\n do_syscall_64+0x50/0x1f0\n entry_SYSCALL_64_after_hwframe+0x76/0x7e\nRIP: 0033:0x7fdfb8495047(CVE-2026-23000)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nx86/fpu: Clear XSTATE_BV[i] in guest XSAVE state whenever XFD[i]=1\n\nWhen loading guest XSAVE state via KVM_SET_XSAVE, and when updating XFD in\nresponse to a guest WRMSR, clear XFD-disabled features in the saved (or to\nbe restored) XSTATE_BV to ensure KVM doesn\u0026apos;t attempt to load state for\nfeatures that are disabled via the guest\u0026apos;s XFD.  Because the kernel\nexecutes XRSTOR with the guest\u0026apos;s XFD, saving XSTATE_BV[i]=1 with XFD[i]=1\nwill cause XRSTOR to #NM and panic the kernel.\n\nE.g. if fpu_update_guest_xfd() sets XFD without clearing XSTATE_BV:\n\n  ------------[ cut here ]------------\n  WARNING: arch/x86/kernel/traps.c:1524 at exc_device_not_available+0x101/0x110, CPU#29: amx_test/848\n  Modules linked in: kvm_intel kvm irqbypass\n  CPU: 29 UID: 1000 PID: 848 Comm: amx_test Not tainted 6.19.0-rc2-ffa07f7fd437-x86_amx_nm_xfd_non_init-vm #171 NONE\n  Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 0.0.0 02/06/2015\n  RIP: 0010:exc_device_not_available+0x101/0x110\n  Call Trace:\n   \u0026lt;TASK\u0026gt;\n   asm_exc_device_not_available+0x1a/0x20\n  RIP: 0010:restore_fpregs_from_fpstate+0x36/0x90\n   switch_fpu_return+0x4a/0xb0\n   kvm_arch_vcpu_ioctl_run+0x1245/0x1e40 [kvm]\n   kvm_vcpu_ioctl+0x2c3/0x8f0 [kvm]\n   __x64_sys_ioctl+0x8f/0xd0\n   do_syscall_64+0x62/0x940\n   entry_SYSCALL_64_after_hwframe+0x4b/0x53\n   \u0026lt;/TASK\u0026gt;\n  ---[ end trace 0000000000000000 ]---\n\nThis can happen if the guest executes WRMSR(MSR_IA32_XFD) to set XFD[18] = 1,\nand a host IRQ triggers kernel_fpu_begin() prior to the vmexit handler\u0026apos;s\ncall to fpu_update_guest_xfd().\n\nand if userspace stuffs XSTATE_BV[i]=1 via KVM_SET_XSAVE:\n\n  ------------[ cut here ]------------\n  WARNING: arch/x86/kernel/traps.c:1524 at exc_device_not_available+0x101/0x110, CPU#14: amx_test/867\n  Modules linked in: kvm_intel kvm irqbypass\n  CPU: 14 UID: 1000 PID: 867 Comm: amx_test Not tainted 6.19.0-rc2-2dace9faccd6-x86_amx_nm_xfd_non_init-vm #168 NONE\n  Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 0.0.0 02/06/2015\n  RIP: 0010:exc_device_not_available+0x101/0x110\n  Call Trace:\n   \u0026lt;TASK\u0026gt;\n   asm_exc_device_not_available+0x1a/0x20\n  RIP: 0010:restore_fpregs_from_fpstate+0x36/0x90\n   fpu_swap_kvm_fpstate+0x6b/0x120\n   kvm_load_guest_fpu+0x30/0x80 [kvm]\n   kvm_arch_vcpu_ioctl_run+0x85/0x1e40 [kvm]\n   kvm_vcpu_ioctl+0x2c3/0x8f0 [kvm]\n   __x64_sys_ioctl+0x8f/0xd0\n   do_syscall_64+0x62/0x940\n   entry_SYSCALL_64_after_hwframe+0x4b/0x53\n   \u0026lt;/TASK\u0026gt;\n  ---[ end trace 0000000000000000 ]---\n\nThe new behavior is consistent with the AMX architecture.  Per Intel\u0026apos;s SDM,\nXSAVE saves XSTATE_BV as \u0026apos;0\u0026apos; for components that are disabled via XFD\n(and non-compacted XSAVE saves the initial configuration of the state\ncomponent):\n\n  If XSAVE, XSAVEC, XSAVEOPT, or XSAVES is saving the state component i,\n  the instruction does not generate #NM when XCR0[i] = IA32_XFD[i] = 1;\n  instead, it operates as if XINUSE[i] = 0 (and the state component was\n  in its initial state): it saves bit i of XSTATE_BV field of the XSAVE\n  header as 0; in addition, XSAVE saves the initial configuration of the\n  state component (the other instructions do not save state component i).\n\nAlternatively, KVM could always do XRSTOR with XFD=0, e.g. by using\na constant XFD based on the set of enabled features when XSAVEing for\na struct fpu_guest.  However, having XSTATE_BV[i]=1 for XFD-disabled\nfeatures can only happen in the above interrupt case, or in similar\nscenarios involving preemption on preemptible kernels, because\nfpu_swap_kvm_fpstate()\u0026apos;s call to save_fpregs_to_fpstate() saves the\noutgoing FPU state with the current XFD; and that is (on all but the\nfirst WRMSR to XFD) the guest XFD.\n\nTherefore, XFD can only go out of sync with XSTATE_BV in the above\ninterrupt case, or in similar scenarios involving preemption on\npreemptible kernels, and it we can consider it (de facto) part of KVM\nABI that KVM_GET_XSAVE returns XSTATE_BV[i]=0 for XFD-disabled features.\n\n[Move clea\n---truncated---(CVE-2026-23005)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnet/mlx5e: Pass netdev to mlx5e_destroy_netdev instead of priv\n\nmlx5e_priv is an unstable structure that can be memset(0) if profile\nattaching fails.\n\nPass netdev to mlx5e_destroy_netdev() to guarantee it will work on a\nvalid netdev.\n\nOn mlx5e_remove: Check validity of priv-\u0026gt;profile, before attempting\nto cleanup any resources that might be not there.\n\nThis fixes a kernel oops in mlx5e_remove when switchdev mode fails due\nto change profile failure.\n\n$ devlink dev eswitch set pci/0000:00:03.0 mode switchdev\nError: mlx5_core: Failed setting eswitch to offloads.\ndmesg:\nworkqueue: Failed to create a rescuer kthread for wq \u0026quot;mlx5e\u0026quot;: -EINTR\nmlx5_core 0012:03:00.1: mlx5e_netdev_init_profile:6214:(pid 37199): mlx5e_priv_init failed, err=-12\nmlx5_core 0012:03:00.1 gpu3rdma1: mlx5e_netdev_change_profile: new profile init failed, -12\nworkqueue: Failed to create a rescuer kthread for wq \u0026quot;mlx5e\u0026quot;: -EINTR\nmlx5_core 0012:03:00.1: mlx5e_netdev_init_profile:6214:(pid 37199): mlx5e_priv_init failed, err=-12\nmlx5_core 0012:03:00.1 gpu3rdma1: mlx5e_netdev_change_profile: failed to rollback to orig profile, -12\n\n$ devlink dev reload pci/0000:00:03.0 ==\u0026gt; oops\n\nBUG: kernel NULL pointer dereference, address: 0000000000000370\nPGD 0 P4D 0\nOops: Oops: 0000 [#1] SMP NOPTI\nCPU: 15 UID: 0 PID: 520 Comm: devlink Not tainted 6.18.0-rc5+ #115 PREEMPT(voluntary)\nHardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.16.3-2.fc40 04/01/2014\nRIP: 0010:mlx5e_dcbnl_dscp_app+0x23/0x100\nRSP: 0018:ffffc9000083f8b8 EFLAGS: 00010286\nRAX: ffff8881126fc380 RBX: ffff8881015ac400 RCX: ffffffff826ffc45\nRDX: 0000000000000000 RSI: 0000000000000001 RDI: ffff8881035109c0\nRBP: ffff8881035109c0 R08: ffff888101e3e838 R09: ffff888100264e10\nR10: ffffc9000083f898 R11: ffffc9000083f8a0 R12: ffff888101b921a0\nR13: ffff888101b921a0 R14: ffff8881015ac9a0 R15: ffff8881015ac400\nFS:  00007f789a3c8740(0000) GS:ffff88856aa59000(0000) knlGS:0000000000000000\nCS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033\nCR2: 0000000000000370 CR3: 000000010b6c0001 CR4: 0000000000370ef0\nCall Trace:\n \u0026lt;TASK\u0026gt;\n mlx5e_remove+0x57/0x110\n device_release_driver_internal+0x19c/0x200\n bus_remove_device+0xc6/0x130\n device_del+0x160/0x3d0\n ? devl_param_driverinit_value_get+0x2d/0x90\n mlx5_detach_device+0x89/0xe0\n mlx5_unload_one_devl_locked+0x3a/0x70\n mlx5_devlink_reload_down+0xc8/0x220\n devlink_reload+0x7d/0x260\n devlink_nl_reload_doit+0x45b/0x5a0\n genl_family_rcv_msg_doit+0xe8/0x140(CVE-2026-23035)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ncrypto: authencesn - reject too-short AAD (assoclen\u0026lt;8) to match ESP/ESN spec\n\nauthencesn assumes an ESP/ESN-formatted AAD. When assoclen is shorter than\nthe minimum expected length, crypto_authenc_esn_decrypt() can advance past\nthe end of the destination scatterlist and trigger a NULL pointer dereference\nin scatterwalk_map_and_copy(), leading to a kernel panic (DoS).\n\nAdd a minimum AAD length check to fail fast on invalid inputs.(CVE-2026-23060)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nvsock/virtio: fix potential underflow in virtio_transport_get_credit()\n\nThe credit calculation in virtio_transport_get_credit() uses unsigned\narithmetic:\n\n  ret = vvs-\u0026gt;peer_buf_alloc - (vvs-\u0026gt;tx_cnt - vvs-\u0026gt;peer_fwd_cnt);\n\nIf the peer shrinks its advertised buffer (peer_buf_alloc) while bytes\nare in flight, the subtraction can underflow and produce a large\npositive value, potentially allowing more data to be queued than the\npeer can handle.\n\nReuse virtio_transport_has_space() which already handles this case and\nadd a comment to make it clear why we are doing that.\n\n[Stefano: use virtio_transport_has_space() instead of duplicating the code]\n[Stefano: tweak the commit message](CVE-2026-23069)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nregmap: Fix race condition in hwspinlock irqsave routine\n\nPreviously, the address of the shared member \u0026apos;\u0026amp;map-\u0026gt;spinlock_flags\u0026apos; was\npassed directly to \u0026apos;hwspin_lock_timeout_irqsave\u0026apos;. This creates a race\ncondition where multiple contexts contending for the lock could overwrite\nthe shared flags variable, potentially corrupting the state for the\ncurrent lock owner.\n\nFix this by using a local stack variable \u0026apos;flags\u0026apos; to store the IRQ state\ntemporarily.(CVE-2026-23071)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nvsock/virtio: cap TX credit to local buffer size\n\nThe virtio transports derives its TX credit directly from peer_buf_alloc,\nwhich is set from the remote endpoint\u0026apos;s SO_VM_SOCKETS_BUFFER_SIZE value.\n\nOn the host side this means that the amount of data we are willing to\nqueue for a connection is scaled by a guest-chosen buffer size, rather\nthan the host\u0026apos;s own vsock configuration. A malicious guest can advertise\na large buffer and read slowly, causing the host to allocate a\ncorrespondingly large amount of sk_buff memory.\nThe same thing would happen in the guest with a malicious host, since\nvirtio transports share the same code base.\n\nIntroduce a small helper, virtio_transport_tx_buf_size(), that\nreturns min(peer_buf_alloc, buf_alloc), and use it wherever we consume\npeer_buf_alloc.\n\nThis ensures the effective TX window is bounded by both the peer\u0026apos;s\nadvertised buffer and our own buf_alloc (already clamped to\nbuffer_max_size via SO_VM_SOCKETS_BUFFER_MAX_SIZE), so a remote peer\ncannot force the other to queue more data than allowed by its own\nvsock settings.\n\nOn an unpatched Ubuntu 22.04 host (~64 GiB RAM), running a PoC with\n32 guest vsock connections advertising 2 GiB each and reading slowly\ndrove Slab/SUnreclaim from ~0.5 GiB to ~57 GiB; the system only\nrecovered after killing the QEMU process. That said, if QEMU memory is\nlimited with cgroups, the maximum memory used will be limited.\n\nWith this patch applied:\n\n  Before:\n    MemFree:        ~61.6 GiB\n    Slab:           ~142 MiB\n    SUnreclaim:     ~117 MiB\n\n  After 32 high-credit connections:\n    MemFree:        ~61.5 GiB\n    Slab:           ~178 MiB\n    SUnreclaim:     ~152 MiB\n\nOnly ~35 MiB increase in Slab/SUnreclaim, no host OOM, and the guest\nremains responsive.\n\nCompatibility with non-virtio transports:\n\n  - VMCI uses the AF_VSOCK buffer knobs to size its queue pairs per\n    socket based on the local vsk-\u0026gt;buffer_* values; the remote side\n    cannot enlarge those queues beyond what the local endpoint\n    configured.\n\n  - Hyper-V\u0026apos;s vsock transport uses fixed-size VMBus ring buffers and\n    an MTU bound; there is no peer-controlled credit field comparable\n    to peer_buf_alloc, and the remote endpoint cannot drive in-flight\n    kernel memory above those ring sizes.\n\n  - The loopback path reuses virtio_transport_common.c, so it\n    naturally follows the same semantics as the virtio transport.\n\nThis change is limited to virtio_transport_common.c and thus affects\nvirtio-vsock, vhost-vsock, and loopback, bringing them in line with the\n\u0026quot;remote window intersected with local policy\u0026quot; behaviour that VMCI and\nHyper-V already effectively have.\n\n[Stefano: small adjustments after changing the previous patch]\n[Stefano: tweak the commit message](CVE-2026-23086)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nbonding: limit BOND_MODE_8023AD to Ethernet devices\n\nBOND_MODE_8023AD makes sense for ARPHRD_ETHER only.\n\nsyzbot reported:\n\n BUG: KASAN: global-out-of-bounds in __hw_addr_create net/core/dev_addr_lists.c:63 [inline]\n BUG: KASAN: global-out-of-bounds in __hw_addr_add_ex+0x25d/0x760 net/core/dev_addr_lists.c:118\nRead of size 16 at addr ffffffff8bf94040 by task syz.1.3580/19497\n\nCPU: 1 UID: 0 PID: 19497 Comm: syz.1.3580 Tainted: G             L      syzkaller #0 PREEMPT(full)\nTainted: [L]=SOFTLOCKUP\nHardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 10/25/2025\nCall Trace:\n \u0026lt;TASK\u0026gt;\n  dump_stack_lvl+0xe8/0x150 lib/dump_stack.c:120\n  print_address_description mm/kasan/report.c:378 [inline]\n  print_report+0xca/0x240 mm/kasan/report.c:482\n  kasan_report+0x118/0x150 mm/kasan/report.c:595\n check_region_inline mm/kasan/generic.c:-1 [inline]\n  kasan_check_range+0x2b0/0x2c0 mm/kasan/generic.c:200\n  __asan_memcpy+0x29/0x70 mm/kasan/shadow.c:105\n  __hw_addr_create net/core/dev_addr_lists.c:63 [inline]\n  __hw_addr_add_ex+0x25d/0x760 net/core/dev_addr_lists.c:118\n  __dev_mc_add net/core/dev_addr_lists.c:868 [inline]\n  dev_mc_add+0xa1/0x120 net/core/dev_addr_lists.c:886\n  bond_enslave+0x2b8b/0x3ac0 drivers/net/bonding/bond_main.c:2180\n  do_set_master+0x533/0x6d0 net/core/rtnetlink.c:2963\n  do_setlink+0xcf0/0x41c0 net/core/rtnetlink.c:3165\n  rtnl_changelink net/core/rtnetlink.c:3776 [inline]\n  __rtnl_newlink net/core/rtnetlink.c:3935 [inline]\n  rtnl_newlink+0x161c/0x1c90 net/core/rtnetlink.c:4072\n  rtnetlink_rcv_msg+0x7cf/0xb70 net/core/rtnetlink.c:6958\n  netlink_rcv_skb+0x208/0x470 net/netlink/af_netlink.c:2550\n  netlink_unicast_kernel net/netlink/af_netlink.c:1318 [inline]\n  netlink_unicast+0x82f/0x9e0 net/netlink/af_netlink.c:1344\n  netlink_sendmsg+0x805/0xb30 net/netlink/af_netlink.c:1894\n  sock_sendmsg_nosec net/socket.c:727 [inline]\n  __sock_sendmsg+0x21c/0x270 net/socket.c:742\n  ____sys_sendmsg+0x505/0x820 net/socket.c:2592\n  ___sys_sendmsg+0x21f/0x2a0 net/socket.c:2646\n  __sys_sendmsg+0x164/0x220 net/socket.c:2678\n  do_syscall_32_irqs_on arch/x86/entry/syscall_32.c:83 [inline]\n  __do_fast_syscall_32+0x1dc/0x560 arch/x86/entry/syscall_32.c:307\n  do_fast_syscall_32+0x34/0x80 arch/x86/entry/syscall_32.c:332\n entry_SYSENTER_compat_after_hwframe+0x84/0x8e\n \u0026lt;/TASK\u0026gt;\n\nThe buggy address belongs to the variable:\n lacpdu_mcast_addr+0x0/0x40(CVE-2026-23099)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nipvlan: Make the addrs_lock be per port\n\nMake the addrs_lock be per port, not per ipvlan dev.\n\nInitial code seems to be written in the assumption,\nthat any address change must occur under RTNL.\nBut it is not so for the case of IPv6. So\n\n1) Introduce per-port addrs_lock.\n\n2) It was needed to fix places where it was forgotten\nto take lock (ipvlan_open/ipvlan_close)\n\nThis appears to be a very minor problem though.\nSince it\u0026apos;s highly unlikely that ipvlan_add_addr() will\nbe called on 2 CPU simultaneously. But nevertheless,\nthis could cause:\n\n1) False-negative of ipvlan_addr_busy(): one interface\niterated through all port-\u0026gt;ipvlans + ipvlan-\u0026gt;addrs\nunder some ipvlan spinlock, and another added IP\nunder its own lock. Though this is only possible\nfor IPv6, since looks like only ipvlan_addr6_event() can be\ncalled without rtnl_lock.\n\n2) Race since ipvlan_ht_addr_add(port) is called under\ndifferent ipvlan-\u0026gt;addrs_lock locks\n\nThis should not affect performance, since add/remove IP\nis a rare situation and spinlock is not taken on fast\npaths.(CVE-2026-23103)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnet/sched: qfq: Use cl_is_active to determine whether class is active in qfq_rm_from_ag\n\nThis is more of a preventive patch to make the code more consistent and\nto prevent possible exploits that employ child qlen manipulations on qfq.\nuse cl_is_active instead of relying on the child qdisc\u0026apos;s qlen to determine\nclass activation.(CVE-2026-23105)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnetfilter: nf_tables: fix inverted genmask check in nft_map_catchall_activate()\n\nnft_map_catchall_activate() has an inverted element activity check\ncompared to its non-catchall counterpart nft_mapelem_activate() and\ncompared to what is logically required.\n\nnft_map_catchall_activate() is called from the abort path to re-activate\ncatchall map elements that were deactivated during a failed transaction.\nIt should skip elements that are already active (they don\u0026apos;t need\nre-activation) and process elements that are inactive (they need to be\nrestored). Instead, the current code does the opposite: it skips inactive\nelements and processes active ones.\n\nCompare the non-catchall activate callback, which is correct:\n\n  nft_mapelem_activate():\n    if (nft_set_elem_active(ext, iter-\u0026gt;genmask))\n        return 0;   /* skip active, process inactive */\n\nWith the buggy catchall version:\n\n  nft_map_catchall_activate():\n    if (!nft_set_elem_active(ext, genmask))\n        continue;   /* skip inactive, process active */\n\nThe consequence is that when a DELSET operation is aborted,\nnft_setelem_data_activate() is never called for the catchall element.\nFor NFT_GOTO verdict elements, this means nft_data_hold() is never\ncalled to restore the chain-\u0026gt;use reference count. Each abort cycle\npermanently decrements chain-\u0026gt;use. Once chain-\u0026gt;use reaches zero,\nDELCHAIN succeeds and frees the chain while catchall verdict elements\nstill reference it, resulting in a use-after-free.\n\nThis is exploitable for local privilege escalation from an unprivileged\nuser via user namespaces + nftables on distributions that enable\nCONFIG_USER_NS and CONFIG_NF_TABLES.\n\nFix by removing the negation so the check matches nft_mapelem_activate():\nskip active elements, process inactive ones.(CVE-2026-23111)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nl2tp: avoid one data-race in l2tp_tunnel_del_work()\n\nWe should read sk-\u0026gt;sk_socket only when dealing with kernel sockets.\n\nsyzbot reported the following data-race:\n\nBUG: KCSAN: data-race in l2tp_tunnel_del_work / sk_common_release\n\nwrite to 0xffff88811c182b20 of 8 bytes by task 5365 on cpu 0:\n  sk_set_socket include/net/sock.h:2092 [inline]\n  sock_orphan include/net/sock.h:2118 [inline]\n  sk_common_release+0xae/0x230 net/core/sock.c:4003\n  udp_lib_close+0x15/0x20 include/net/udp.h:325\n  inet_release+0xce/0xf0 net/ipv4/af_inet.c:437\n  __sock_release net/socket.c:662 [inline]\n  sock_close+0x6b/0x150 net/socket.c:1455\n  __fput+0x29b/0x650 fs/file_table.c:468\n  ____fput+0x1c/0x30 fs/file_table.c:496\n  task_work_run+0x131/0x1a0 kernel/task_work.c:233\n  resume_user_mode_work include/linux/resume_user_mode.h:50 [inline]\n  __exit_to_user_mode_loop kernel/entry/common.c:44 [inline]\n  exit_to_user_mode_loop+0x1fe/0x740 kernel/entry/common.c:75\n  __exit_to_user_mode_prepare include/linux/irq-entry-common.h:226 [inline]\n  syscall_exit_to_user_mode_prepare include/linux/irq-entry-common.h:256 [inline]\n  syscall_exit_to_user_mode_work include/linux/entry-common.h:159 [inline]\n  syscall_exit_to_user_mode include/linux/entry-common.h:194 [inline]\n  do_syscall_64+0x1e1/0x2b0 arch/x86/entry/syscall_64.c:100\n entry_SYSCALL_64_after_hwframe+0x77/0x7f\n\nread to 0xffff88811c182b20 of 8 bytes by task 827 on cpu 1:\n  l2tp_tunnel_del_work+0x2f/0x1a0 net/l2tp/l2tp_core.c:1418\n  process_one_work kernel/workqueue.c:3257 [inline]\n  process_scheduled_works+0x4ce/0x9d0 kernel/workqueue.c:3340\n  worker_thread+0x582/0x770 kernel/workqueue.c:3421\n  kthread+0x489/0x510 kernel/kthread.c:463\n  ret_from_fork+0x149/0x290 arch/x86/kernel/process.c:158\n  ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:246\n\nvalue changed: 0xffff88811b818000 -\u0026gt; 0x0000000000000000(CVE-2026-23120)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nipv6: annotate data-race in ndisc_router_discovery()\n\nsyzbot found that ndisc_router_discovery() could read and write\nin6_dev-\u0026gt;ra_mtu without holding a lock [1]\n\nThis looks fine, IFLA_INET6_RA_MTU is best effort.\n\nAdd READ_ONCE()/WRITE_ONCE() to document the race.\n\nNote that we might also reject illegal MTU values\n(mtu \u0026lt; IPV6_MIN_MTU || mtu \u0026gt; skb-\u0026gt;dev-\u0026gt;mtu) in a future patch.\n\n[1]\nBUG: KCSAN: data-race in ndisc_router_discovery / ndisc_router_discovery\n\nread to 0xffff888119809c20 of 4 bytes by task 25817 on cpu 1:\n  ndisc_router_discovery+0x151d/0x1c90 net/ipv6/ndisc.c:1558\n  ndisc_rcv+0x2ad/0x3d0 net/ipv6/ndisc.c:1841\n  icmpv6_rcv+0xe5a/0x12f0 net/ipv6/icmp.c:989\n  ip6_protocol_deliver_rcu+0xb2a/0x10d0 net/ipv6/ip6_input.c:438\n  ip6_input_finish+0xf0/0x1d0 net/ipv6/ip6_input.c:489\n  NF_HOOK include/linux/netfilter.h:318 [inline]\n  ip6_input+0x5e/0x140 net/ipv6/ip6_input.c:500\n  ip6_mc_input+0x27c/0x470 net/ipv6/ip6_input.c:590\n  dst_input include/net/dst.h:474 [inline]\n  ip6_rcv_finish+0x336/0x340 net/ipv6/ip6_input.c:79\n...\n\nwrite to 0xffff888119809c20 of 4 bytes by task 25816 on cpu 0:\n  ndisc_router_discovery+0x155a/0x1c90 net/ipv6/ndisc.c:1559\n  ndisc_rcv+0x2ad/0x3d0 net/ipv6/ndisc.c:1841\n  icmpv6_rcv+0xe5a/0x12f0 net/ipv6/icmp.c:989\n  ip6_protocol_deliver_rcu+0xb2a/0x10d0 net/ipv6/ip6_input.c:438\n  ip6_input_finish+0xf0/0x1d0 net/ipv6/ip6_input.c:489\n  NF_HOOK include/linux/netfilter.h:318 [inline]\n  ip6_input+0x5e/0x140 net/ipv6/ip6_input.c:500\n  ip6_mc_input+0x27c/0x470 net/ipv6/ip6_input.c:590\n  dst_input include/net/dst.h:474 [inline]\n  ip6_rcv_finish+0x336/0x340 net/ipv6/ip6_input.c:79\n...\n\nvalue changed: 0x00000000 -\u0026gt; 0xe5400659(CVE-2026-23124)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnetdevsim: fix a race issue related to the operation on bpf_bound_progs list\n\nThe netdevsim driver lacks a protection mechanism for operations on the\nbpf_bound_progs list. When the nsim_bpf_create_prog() performs\nlist_add_tail, it is possible that nsim_bpf_destroy_prog() is\nsimultaneously performs list_del. Concurrent operations on the list may\nlead to list corruption and trigger a kernel crash as follows:\n\n[  417.290971] kernel BUG at lib/list_debug.c:62!\n[  417.290983] invalid opcode: 0000 [#1] PREEMPT SMP NOPTI\n[  417.290992] CPU: 10 PID: 168 Comm: kworker/10:1 Kdump: loaded Not tainted 6.19.0-rc5 #1\n[  417.291003] Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.16.3-debian-1.16.3-2 04/01/2014\n[  417.291007] Workqueue: events bpf_prog_free_deferred\n[  417.291021] RIP: 0010:__list_del_entry_valid_or_report+0xa7/0xc0\n[  417.291034] Code: a8 ff 0f 0b 48 89 fe 48 89 ca 48 c7 c7 48 a1 eb ae e8 ed fb a8 ff 0f 0b 48 89 fe 48 89 c2 48 c7 c7 80 a1 eb ae e8 d9 fb a8 ff \u0026lt;0f\u0026gt; 0b 48 89 d1 48 c7 c7 d0 a1 eb ae 48 89 f2 48 89 c6 e8 c2 fb a8\n[  417.291040] RSP: 0018:ffffb16a40807df8 EFLAGS: 00010246\n[  417.291046] RAX: 000000000000006d RBX: ffff8e589866f500 RCX: 0000000000000000\n[  417.291051] RDX: 0000000000000000 RSI: ffff8e59f7b23180 RDI: ffff8e59f7b23180\n[  417.291055] RBP: ffffb16a412c9000 R08: 0000000000000000 R09: 0000000000000003\n[  417.291059] R10: ffffb16a40807c80 R11: ffffffffaf9edce8 R12: ffff8e594427ac20\n[  417.291063] R13: ffff8e59f7b44780 R14: ffff8e58800b7a05 R15: 0000000000000000\n[  417.291074] FS:  0000000000000000(0000) GS:ffff8e59f7b00000(0000) knlGS:0000000000000000\n[  417.291079] CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033\n[  417.291083] CR2: 00007fc4083efe08 CR3: 00000001c3626006 CR4: 0000000000770ee0\n[  417.291088] PKRU: 55555554\n[  417.291091] Call Trace:\n[  417.291096]  \u0026lt;TASK\u0026gt;\n[  417.291103]  nsim_bpf_destroy_prog+0x31/0x80 [netdevsim]\n[  417.291154]  __bpf_prog_offload_destroy+0x2a/0x80\n[  417.291163]  bpf_prog_dev_bound_destroy+0x6f/0xb0\n[  417.291171]  bpf_prog_free_deferred+0x18e/0x1a0\n[  417.291178]  process_one_work+0x18a/0x3a0\n[  417.291188]  worker_thread+0x27b/0x3a0\n[  417.291197]  ? __pfx_worker_thread+0x10/0x10\n[  417.291207]  kthread+0xe5/0x120\n[  417.291214]  ? __pfx_kthread+0x10/0x10\n[  417.291221]  ret_from_fork+0x31/0x50\n[  417.291230]  ? __pfx_kthread+0x10/0x10\n[  417.291236]  ret_from_fork_asm+0x1a/0x30\n[  417.291246]  \u0026lt;/TASK\u0026gt;\n\nAdd a mutex lock, to prevent simultaneous addition and deletion operations\non the list.(CVE-2026-23126)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nwifi: ath10k: fix dma_free_coherent() pointer\n\ndma_alloc_coherent() allocates a DMA mapped buffer and stores the\naddresses in XXX_unaligned fields.  Those should be reused when freeing\nthe buffer rather than the aligned addresses.(CVE-2026-23133)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nlibceph: reset sparse-read state in osd_fault()\n\nWhen a fault occurs, the connection is abandoned, reestablished, and any\npending operations are retried. The OSD client tracks the progress of a\nsparse-read reply using a separate state machine, largely independent of\nthe messenger\u0026apos;s state.\n\nIf a connection is lost mid-payload or the sparse-read state machine\nreturns an error, the sparse-read state is not reset. The OSD client\nwill then interpret the beginning of a new reply as the continuation of\nthe old one. If this makes the sparse-read machinery enter a failure\nstate, it may never recover, producing loops like:\n\n  libceph:  [0] got 0 extents\n  libceph: data len 142248331 != extent len 0\n  libceph: osd0 (1)...:6801 socket error on read\n  libceph: data len 142248331 != extent len 0\n  libceph: osd0 (1)...:6801 socket error on read\n\nTherefore, reset the sparse-read state in osd_fault(), ensuring retries\nstart from a clean state.(CVE-2026-23136)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nof: unittest: Fix memory leak in unittest_data_add()\n\nIn unittest_data_add(), if of_resolve_phandles() fails, the allocated\nunittest_data is not freed, leading to a memory leak.\n\nFix this by using scope-based cleanup helper __free(kfree) for automatic\nresource cleanup. This ensures unittest_data is automatically freed when\nit goes out of scope in error paths.\n\nFor the success path, use retain_and_null_ptr() to transfer ownership\nof the memory to the device tree and prevent double freeing.(CVE-2026-23137)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ntracing: Add recursion protection in kernel stack trace recording\n\nA bug was reported about an infinite recursion caused by tracing the rcu\nevents with the kernel stack trace trigger enabled. The stack trace code\ncalled back into RCU which then called the stack trace again.\n\nExpand the ftrace recursion protection to add a set of bits to protect\nevents from recursion. Each bit represents the context that the event is\nin (normal, softirq, interrupt and NMI).\n\nHave the stack trace code use the interrupt context to protect against\nrecursion.\n\nNote, the bug showed an issue in both the RCU code as well as the tracing\nstacktrace code. This only handles the tracing stack trace side of the\nbug. The RCU fix will be handled separately.(CVE-2026-23138)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnetfilter: nf_conncount: update last_gc only when GC has been performed\n\nCurrently last_gc is being updated everytime a new connection is\ntracked, that means that it is updated even if a GC wasn\u0026apos;t performed.\nWith a sufficiently high packet rate, it is possible to always bypass\nthe GC, causing the list to grow infinitely.\n\nUpdate the last_gc value only when a GC has been actually performed.(CVE-2026-23139)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\next4: fix iloc.bh leak in ext4_xattr_inode_update_ref\n\nThe error branch for ext4_xattr_inode_update_ref forget to release the\nrefcount for iloc.bh. Find this when review code.(CVE-2026-23145)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnet: fix segmentation of forwarding fraglist GRO\n\nThis patch enhances GSO segment handling by properly checking\nthe SKB_GSO_DODGY flag for frag_list GSO packets, addressing\nlow throughput issues observed when a station accesses IPv4\nservers via hotspots with an IPv6-only upstream interface.\n\nSpecifically, it fixes a bug in GSO segmentation when forwarding\nGRO packets containing a frag_list. The function skb_segment_list\ncannot correctly process GRO skbs that have been converted by XLAT,\nsince XLAT only translates the header of the head skb. Consequently,\nskbs in the frag_list may remain untranslated, resulting in protocol\ninconsistencies and reduced throughput.\n\nTo address this, the patch explicitly sets the SKB_GSO_DODGY flag\nfor GSO packets in XLAT\u0026apos;s IPv4/IPv6 protocol translation helpers\n(bpf_skb_proto_4_to_6 and bpf_skb_proto_6_to_4). This marks GSO\npackets as potentially modified after protocol translation. As a\nresult, GSO segmentation will avoid using skb_segment_list and\ninstead falls back to skb_segment for packets with the SKB_GSO_DODGY\nflag. This ensures that only safe and fully translated frag_list\npackets are processed by skb_segment_list, resolving protocol\ninconsistencies and improving throughput when forwarding GRO packets\nconverted by XLAT.(CVE-2026-23154)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nefivarfs: fix error propagation in efivar_entry_get()\n\nefivar_entry_get() always returns success even if the underlying\n__efivar_entry_get() fails, masking errors.\n\nThis may result in uninitialized heap memory being copied to userspace\nin the efivarfs_file_read() path.\n\nFix it by returning the error from __efivar_entry_get().(CVE-2026-23156)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nmptcp: fix race in mptcp_pm_nl_flush_addrs_doit()\n\nsyzbot and Eulgyu Kim reported crashes in mptcp_pm_nl_get_local_id()\nand/or mptcp_pm_nl_is_backup()\n\nRoot cause is list_splice_init() in mptcp_pm_nl_flush_addrs_doit()\nwhich is not RCU ready.\n\nlist_splice_init_rcu() can not be called here while holding pernet-\u0026gt;lock\nspinlock.\n\nMany thanks to Eulgyu Kim for providing a repro and testing our patches.(CVE-2026-23169)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnet/mlx5e: TC, delete flows only for existing peers\n\nWhen deleting TC steering flows, iterate only over actual devcom\npeers instead of assuming all possible ports exist. This avoids\ntouching non-existent peers and ensures cleanup is limited to\ndevices the driver is currently connected to.\n\n BUG: kernel NULL pointer dereference, address: 0000000000000008\n #PF: supervisor write access in kernel mode\n #PF: error_code(0x0002) - not-present page\n PGD 133c8a067 P4D 0\n Oops: Oops: 0002 [#1] SMP\n CPU: 19 UID: 0 PID: 2169 Comm: tc Not tainted 6.18.0+ #156 NONE\n Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS rel-1.16.0-0-gd239552ce722-prebuilt.qemu.org 04/01/2014\n RIP: 0010:mlx5e_tc_del_fdb_peers_flow+0xbe/0x200 [mlx5_core]\n Code: 00 00 a8 08 74 a8 49 8b 46 18 f6 c4 02 74 9f 4c 8d bf a0 12 00 00 4c 89 ff e8 0e e7 96 e1 49 8b 44 24 08 49 8b 0c 24 4c 89 ff \u0026lt;48\u0026gt; 89 41 08 48 89 08 49 89 2c 24 49 89 5c 24 08 e8 7d ce 96 e1 49\n RSP: 0018:ff11000143867528 EFLAGS: 00010246\n RAX: 0000000000000000 RBX: dead000000000122 RCX: 0000000000000000\n RDX: ff11000143691580 RSI: ff110001026e5000 RDI: ff11000106f3d2a0\n RBP: dead000000000100 R08: 00000000000003fd R09: 0000000000000002\n R10: ff11000101c75690 R11: ff1100085faea178 R12: ff11000115f0ae78\n R13: 0000000000000000 R14: ff11000115f0a800 R15: ff11000106f3d2a0\n FS:  00007f35236bf740(0000) GS:ff110008dc809000(0000) knlGS:0000000000000000\n CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033\n CR2: 0000000000000008 CR3: 0000000157a01001 CR4: 0000000000373eb0\n Call Trace:\n  \u0026lt;TASK\u0026gt;\n  mlx5e_tc_del_flow+0x46/0x270 [mlx5_core]\n  mlx5e_flow_put+0x25/0x50 [mlx5_core]\n  mlx5e_delete_flower+0x2a6/0x3e0 [mlx5_core]\n  tc_setup_cb_reoffload+0x20/0x80\n  fl_reoffload+0x26f/0x2f0 [cls_flower]\n  ? mlx5e_tc_reoffload_flows_work+0xc0/0xc0 [mlx5_core]\n  ? mlx5e_tc_reoffload_flows_work+0xc0/0xc0 [mlx5_core]\n  tcf_block_playback_offloads+0x9e/0x1c0\n  tcf_block_unbind+0x7b/0xd0\n  tcf_block_setup+0x186/0x1d0\n  tcf_block_offload_cmd.isra.0+0xef/0x130\n  tcf_block_offload_unbind+0x43/0x70\n  __tcf_block_put+0x85/0x160\n  ingress_destroy+0x32/0x110 [sch_ingress]\n  __qdisc_destroy+0x44/0x100\n  qdisc_graft+0x22b/0x610\n  tc_get_qdisc+0x183/0x4d0\n  rtnetlink_rcv_msg+0x2d7/0x3d0\n  ? rtnl_calcit.isra.0+0x100/0x100\n  netlink_rcv_skb+0x53/0x100\n  netlink_unicast+0x249/0x320\n  ? __alloc_skb+0x102/0x1f0\n  netlink_sendmsg+0x1e3/0x420\n  __sock_sendmsg+0x38/0x60\n  ____sys_sendmsg+0x1ef/0x230\n  ? copy_msghdr_from_user+0x6c/0xa0\n  ___sys_sendmsg+0x7f/0xc0\n  ? ___sys_recvmsg+0x8a/0xc0\n  ? __sys_sendto+0x119/0x180\n  __sys_sendmsg+0x61/0xb0\n  do_syscall_64+0x55/0x640\n  entry_SYSCALL_64_after_hwframe+0x4b/0x53\n RIP: 0033:0x7f35238bb764\n Code: 15 b9 86 0c 00 f7 d8 64 89 02 b8 ff ff ff ff eb bf 0f 1f 44 00 00 f3 0f 1e fa 80 3d e5 08 0d 00 00 74 13 b8 2e 00 00 00 0f 05 \u0026lt;48\u0026gt; 3d 00 f0 ff ff 77 4c c3 0f 1f 00 55 48 89 e5 48 83 ec 20 89 55\n RSP: 002b:00007ffed4c35638 EFLAGS: 00000202 ORIG_RAX: 000000000000002e\n RAX: ffffffffffffffda RBX: 000055a2efcc75e0 RCX: 00007f35238bb764\n RDX: 0000000000000000 RSI: 00007ffed4c356a0 RDI: 0000000000000003\n RBP: 00007ffed4c35710 R08: 0000000000000010 R09: 00007f3523984b20\n R10: 0000000000000004 R11: 0000000000000202 R12: 00007ffed4c35790\n R13: 000000006947df8f R14: 000055a2efcc75e0 R15: 00007ffed4c35780(CVE-2026-23173)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nALSA: aloop: Fix racy access at PCM trigger\n\nThe PCM trigger callback of aloop driver tries to check the PCM state\nand stop the stream of the tied substream in the corresponding cable.\nSince both check and stop operations are performed outside the cable\nlock, this may result in UAF when a program attempts to trigger\nfrequently while opening/closing the tied stream, as spotted by\nfuzzers.\n\nFor addressing the UAF, this patch changes two things:\n- It covers the most of code in loopback_check_format() with\n  cable-\u0026gt;lock spinlock, and add the proper NULL checks.  This avoids\n  already some racy accesses.\n- In addition, now we try to check the state of the capture PCM stream\n  that may be stopped in this function, which was the major pain point\n  leading to UAF.(CVE-2026-23191)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nKVM: Don\u0026apos;t clobber irqfd routing type when deassigning irqfd\n\nWhen deassigning a KVM_IRQFD, don\u0026apos;t clobber the irqfd\u0026apos;s copy of the IRQ\u0026apos;s\nrouting entry as doing so breaks kvm_arch_irq_bypass_del_producer() on x86\nand arm64, which explicitly look for KVM_IRQ_ROUTING_MSI.  Instead, to\nhandle a concurrent routing update, verify that the irqfd is still active\nbefore consuming the routing information.  As evidenced by the x86 and\narm64 bugs, and another bug in kvm_arch_update_irqfd_routing() (see below),\nclobbering the entry type without notifying arch code is surprising and\nerror prone.\n\nAs a bonus, checking that the irqfd is active provides a convenient\nlocation for documenting _why_ KVM must not consume the routing entry for\nan irqfd that is in the process of being deassigned: once the irqfd is\ndeleted from the list (which happens *before* the eventfd is detached), it\nwill no longer receive updates via kvm_irq_routing_update(), and so KVM\ncould deliver an event using stale routing information (relative to\nKVM_SET_GSI_ROUTING returning to userspace).\n\nAs an even better bonus, explicitly checking for the irqfd being active\nfixes a similar bug to the one the clobbering is trying to prevent: if an\nirqfd is deactivated, and then its routing is changed,\nkvm_irq_routing_update() won\u0026apos;t invoke kvm_arch_update_irqfd_routing()\n(because the irqfd isn\u0026apos;t in the list).  And so if the irqfd is in bypass\nmode, IRQs will continue to be posted using the old routing information.\n\nAs for kvm_arch_irq_bypass_del_producer(), clobbering the routing type\nresults in KVM incorrectly keeping the IRQ in bypass mode, which is\nespecially problematic on AMD as KVM tracks IRQs that are being posted to\na vCPU in a list whose lifetime is tied to the irqfd.\n\nWithout the help of KASAN to detect use-after-free, the most common\nsympton on AMD is a NULL pointer deref in amd_iommu_update_ga() due to\nthe memory for irqfd structure being re-allocated and zeroed, resulting\nin irqfd-\u0026gt;irq_bypass_data being NULL when read by\navic_update_iommu_vcpu_affinity():\n\n  BUG: kernel NULL pointer dereference, address: 0000000000000018\n  #PF: supervisor read access in kernel mode\n  #PF: error_code(0x0000) - not-present page\n  PGD 40cf2b9067 P4D 40cf2b9067 PUD 408362a067 PMD 0\n  Oops: Oops: 0000 [#1] SMP\n  CPU: 6 UID: 0 PID: 40383 Comm: vfio_irq_test\n  Tainted: G     U  W  O        6.19.0-smp--5dddc257e6b2-irqfd #31 NONE\n  Tainted: [U]=USER, [W]=WARN, [O]=OOT_MODULE\n  Hardware name: Google, Inc. Arcadia_IT_80/Arcadia_IT_80, BIOS 34.78.2-0 09/05/2025\n  RIP: 0010:amd_iommu_update_ga+0x19/0xe0\n  Call Trace:\n   \u0026lt;TASK\u0026gt;\n   avic_update_iommu_vcpu_affinity+0x3d/0x90 [kvm_amd]\n   __avic_vcpu_load+0xf4/0x130 [kvm_amd]\n   kvm_arch_vcpu_load+0x89/0x210 [kvm]\n   vcpu_load+0x30/0x40 [kvm]\n   kvm_arch_vcpu_ioctl_run+0x45/0x620 [kvm]\n   kvm_vcpu_ioctl+0x571/0x6a0 [kvm]\n   __se_sys_ioctl+0x6d/0xb0\n   do_syscall_64+0x6f/0x9d0\n   entry_SYSCALL_64_after_hwframe+0x4b/0x53\n  RIP: 0033:0x46893b\n    \u0026lt;/TASK\u0026gt;\n  ---[ end trace 0000000000000000 ]---\n\nIf AVIC is inhibited when the irfd is deassigned, the bug will manifest as\nlist corruption, e.g. on the next irqfd assignment.\n\n  list_add corruption. next-\u0026gt;prev should be prev (ffff8d474d5cd588),\n                       but was 0000000000000000. (next=ffff8d8658f86530).\n  ------------[ cut here ]------------\n  kernel BUG at lib/list_debug.c:31!\n  Oops: invalid opcode: 0000 [#1] SMP\n  CPU: 128 UID: 0 PID: 80818 Comm: vfio_irq_test\n  Tainted: G     U  W  O        6.19.0-smp--f19dc4d680ba-irqfd #28 NONE\n  Tainted: [U]=USER, [W]=WARN, [O]=OOT_MODULE\n  Hardware name: Google, Inc. Arcadia_IT_80/Arcadia_IT_80, BIOS 34.78.2-0 09/05/2025\n  RIP: 0010:__list_add_valid_or_report+0x97/0xc0\n  Call Trace:\n   \u0026lt;TASK\u0026gt;\n   avic_pi_update_irte+0x28e/0x2b0 [kvm_amd]\n   kvm_pi_update_irte+0xbf/0x190 [kvm]\n   kvm_arch_irq_bypass_add_producer+0x72/0x90 [kvm]\n   irq_bypass_register_consumer+0xcd/0x170 [irqbypa\n---truncated---(CVE-2026-23198)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnet/sched: cls_u32: use skb_header_pointer_careful()\n\nskb_header_pointer() does not fully validate negative @offset values.\n\nUse skb_header_pointer_careful() instead.\n\nGangMin Kim provided a report and a repro fooling u32_classify():\n\nBUG: KASAN: slab-out-of-bounds in u32_classify+0x1180/0x11b0\nnet/sched/cls_u32.c:221(CVE-2026-23204)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nALSA: usb-audio: Prevent excessive number of frames\n\nIn this case, the user constructed the parameters with maxpacksize 40\nfor rate 22050 / pps 1000, and packsize[0] 22 packsize[1] 23. The buffer\nsize for each data URB is maxpacksize * packets, which in this example\nis 40 * 6 = 240; When the user performs a write operation to send audio\ndata into the ALSA PCM playback stream, the calculated number of frames\nis packsize[0] * packets = 264, which exceeds the allocated URB buffer\nsize, triggering the out-of-bounds (OOB) issue reported by syzbot [1].\n\nAdded a check for the number of single data URB frames when calculating\nthe number of frames to prevent [1].\n\n[1]\nBUG: KASAN: slab-out-of-bounds in copy_to_urb+0x261/0x460 sound/usb/pcm.c:1487\nWrite of size 264 at addr ffff88804337e800 by task syz.0.17/5506\nCall Trace:\n copy_to_urb+0x261/0x460 sound/usb/pcm.c:1487\n prepare_playback_urb+0x953/0x13d0 sound/usb/pcm.c:1611\n prepare_outbound_urb+0x377/0xc50 sound/usb/endpoint.c:333(CVE-2026-23208)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nbonding: annotate data-races around slave-\u0026gt;last_rx\n\nslave-\u0026gt;last_rx and slave-\u0026gt;target_last_arp_rx[...] can be read and written\nlocklessly. Add READ_ONCE() and WRITE_ONCE() annotations.\n\nsyzbot reported:\n\nBUG: KCSAN: data-race in bond_rcv_validate / bond_rcv_validate\n\nwrite to 0xffff888149f0d428 of 8 bytes by interrupt on cpu 1:\n  bond_rcv_validate+0x202/0x7a0 drivers/net/bonding/bond_main.c:3335\n  bond_handle_frame+0xde/0x5e0 drivers/net/bonding/bond_main.c:1533\n  __netif_receive_skb_core+0x5b1/0x1950 net/core/dev.c:6039\n  __netif_receive_skb_one_core net/core/dev.c:6150 [inline]\n  __netif_receive_skb+0x59/0x270 net/core/dev.c:6265\n  netif_receive_skb_internal net/core/dev.c:6351 [inline]\n  netif_receive_skb+0x4b/0x2d0 net/core/dev.c:6410\n...\n\nwrite to 0xffff888149f0d428 of 8 bytes by interrupt on cpu 0:\n  bond_rcv_validate+0x202/0x7a0 drivers/net/bonding/bond_main.c:3335\n  bond_handle_frame+0xde/0x5e0 drivers/net/bonding/bond_main.c:1533\n  __netif_receive_skb_core+0x5b1/0x1950 net/core/dev.c:6039\n  __netif_receive_skb_one_core net/core/dev.c:6150 [inline]\n  __netif_receive_skb+0x59/0x270 net/core/dev.c:6265\n  netif_receive_skb_internal net/core/dev.c:6351 [inline]\n  netif_receive_skb+0x4b/0x2d0 net/core/dev.c:6410\n  br_netif_receive_skb net/bridge/br_input.c:30 [inline]\n  NF_HOOK include/linux/netfilter.h:318 [inline]\n...\n\nvalue changed: 0x0000000100005365 -\u0026gt; 0x0000000100005366(CVE-2026-23212)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nbus: fsl-mc: fix use-after-free in driver_override_show()\n\nThe driver_override_show() function reads the driver_override string\nwithout holding the device_lock. However, driver_override_store() uses\ndriver_set_override(), which modifies and frees the string while holding\nthe device_lock.\n\nThis can result in a concurrent use-after-free if the string is freed\nby the store function while being read by the show function.\n\nFix this by holding the device_lock around the read operation.(CVE-2026-23221)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nsmb: client: split cached_fid bitfields to avoid shared-byte RMW races\n\nis_open, has_lease and on_list are stored in the same bitfield byte in\nstruct cached_fid but are updated in different code paths that may run\nconcurrently. Bitfield assignments generate byte read–modify–write\noperations (e.g. `orb $mask, addr` on x86_64), so updating one flag can\nrestore stale values of the others.\n\nA possible interleaving is:\n    CPU1: load old byte (has_lease=1, on_list=1)\n    CPU2: clear both flags (store 0)\n    CPU1: RMW store (old | IS_OPEN) -\u0026gt; reintroduces cleared bits\n\nTo avoid this class of races, convert these flags to separate bool\nfields.(CVE-2026-23230)","status":"published","published":"2026-03-27T11:10:47Z","modified":"2026-08-18T01:19:55.317925454Z","cvss":[{"version":"3.1","score":7.8,"vector":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H","level":"high"}],"updated_at":"2026-11-02T15:52:45.721983Z"},{"id":"OESA-2026-1761","title":"kernel security update","description":"The Linux Kernel, the operating system core itself.\r\n\r\nSecurity Fix(es):\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\niommu/s390: Implement blocking domain\n\nThis fixes a crash when surprise hot-unplugging a PCI device. This crash\nhappens because during hot-unplug __iommu_group_set_domain_nofail()\nattaching the default domain fails when the platform no longer\nrecognizes the device as it has already been removed and we end up with\na NULL domain pointer and UAF. This is exactly the case referred to in\nthe second comment in __iommu_device_set_domain() and just as stated\nthere if we can instead attach the blocking domain the UAF is prevented\nas this can handle the already removed device. Implement the blocking\ndomain to use this handling.  With this change, the crash is fixed but\nwe still hit a warning attempting to change DMA ownership on a blocked\ndevice.(CVE-2024-53232)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\niommu: Fix two issues in iommu_copy_struct_from_user()\n\nIn the review for iommu_copy_struct_to_user() helper, Matt pointed out that\na NULL pointer should be rejected prior to dereferencing it:\nhttps://lore.kernel.org/all/(CVE-2025-37900)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nsmb: client: Avoid race in open_cached_dir with lease breaks\n\nA pre-existing valid cfid returned from find_or_create_cached_dir might\nrace with a lease break, meaning open_cached_dir doesn\u0026apos;t consider it\nvalid, and thinks it\u0026apos;s newly-constructed. This leaks a dentry reference\nif the allocation occurs before the queued lease break work runs.\n\nAvoid the race by extending holding the cfid_list_lock across\nfind_or_create_cached_dir and when the result is checked.(CVE-2025-37954)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnet_sched: prio: fix a race in prio_tune()\n\nGerrard Tai reported a race condition in PRIO, whenever SFQ perturb timer\nfires at the wrong time.\n\nThe race is as follows:\n\nCPU 0                                 CPU 1\n[1]: lock root\n[2]: qdisc_tree_flush_backlog()\n[3]: unlock root\n |\n |                                    [5]: lock root\n |                                    [6]: rehash\n |                                    [7]: qdisc_tree_reduce_backlog()\n |\n[4]: qdisc_put()\n\nThis can be abused to underflow a parent\u0026apos;s qlen.\n\nCalling qdisc_purge_queue() instead of qdisc_tree_flush_backlog()\nshould fix the race, because all packets will be purged from the qdisc\nbefore releasing the lock.(CVE-2025-38083)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nIB/mlx5: Fix potential deadlock in MR deregistration\n\nThe issue arises when kzalloc() is invoked while holding umem_mutex or\nany other lock acquired under umem_mutex. This is problematic because\nkzalloc() can trigger fs_reclaim_aqcuire(), which may, in turn, invoke\nmmu_notifier_invalidate_range_start(). This function can lead to\nmlx5_ib_invalidate_range(), which attempts to acquire umem_mutex again,\nresulting in a deadlock.\n\nThe problematic flow:\n             CPU0                      |              CPU1\n---------------------------------------|------------------------------------------------\nmlx5_ib_dereg_mr()                     |\n → revoke_mr()                         |\n   → mutex_lock(\u0026amp;umem_odp-\u0026gt;umem_mutex) |\n                                       | mlx5_mkey_cache_init()\n                                       |  → mutex_lock(\u0026amp;dev-\u0026gt;cache.rb_lock)\n                                       |  → mlx5r_cache_create_ent_locked()\n                                       |    → kzalloc(GFP_KERNEL)\n                                       |      → fs_reclaim()\n                                       |        → mmu_notifier_invalidate_range_start()\n                                       |          → mlx5_ib_invalidate_range()\n                                       |            → mutex_lock(\u0026amp;umem_odp-\u0026gt;umem_mutex)\n   → cache_ent_find_and_store()        |\n     → mutex_lock(\u0026amp;dev-\u0026gt;cache.rb_lock) |\n\nAdditionally, when kzalloc() is called from within\ncache_ent_find_and_store(), we encounter the same deadlock due to\nre-acquisition of umem_mutex.\n\nSolve by releasing umem_mutex in dereg_mr() after umr_revoke_mr()\nand before acquiring rb_lock. This ensures that we don\u0026apos;t hold\numem_mutex while performing memory allocations that could trigger\nthe reclaim path.\n\nThis change prevents the deadlock by ensuring proper lock ordering and\navoiding holding locks during memory allocation operations that could\ntrigger the reclaim path.\n\nThe following lockdep warning demonstrates the deadlock:\n\n python3/20557 is trying to acquire lock:\n ffff888387542128 (\u0026amp;umem_odp-\u0026gt;umem_mutex){+.+.}-{4:4}, at:\n mlx5_ib_invalidate_range+0x5b/0x550 [mlx5_ib]\n\n but task is already holding lock:\n ffffffff82f6b840 (mmu_notifier_invalidate_range_start){+.+.}-{0:0}, at:\n unmap_vmas+0x7b/0x1a0\n\n which lock already depends on the new lock.\n\n the existing dependency chain (in reverse order) is:\n\n -\u0026gt; #3 (mmu_notifier_invalidate_range_start){+.+.}-{0:0}:\n       fs_reclaim_acquire+0x60/0xd0\n       mem_cgroup_css_alloc+0x6f/0x9b0\n       cgroup_init_subsys+0xa4/0x240\n       cgroup_init+0x1c8/0x510\n       start_kernel+0x747/0x760\n       x86_64_start_reservations+0x25/0x30\n       x86_64_start_kernel+0x73/0x80\n       common_startup_64+0x129/0x138\n\n -\u0026gt; #2 (fs_reclaim){+.+.}-{0:0}:\n       fs_reclaim_acquire+0x91/0xd0\n       __kmalloc_cache_noprof+0x4d/0x4c0\n       mlx5r_cache_create_ent_locked+0x75/0x620 [mlx5_ib]\n       mlx5_mkey_cache_init+0x186/0x360 [mlx5_ib]\n       mlx5_ib_stage_post_ib_reg_umr_init+0x3c/0x60 [mlx5_ib]\n       __mlx5_ib_add+0x4b/0x190 [mlx5_ib]\n       mlx5r_probe+0xd9/0x320 [mlx5_ib]\n       auxiliary_bus_probe+0x42/0x70\n       really_probe+0xdb/0x360\n       __driver_probe_device+0x8f/0x130\n       driver_probe_device+0x1f/0xb0\n       __driver_attach+0xd4/0x1f0\n       bus_for_each_dev+0x79/0xd0\n       bus_add_driver+0xf0/0x200\n       driver_register+0x6e/0xc0\n       __auxiliary_driver_register+0x6a/0xc0\n       do_one_initcall+0x5e/0x390\n       do_init_module+0x88/0x240\n       init_module_from_file+0x85/0xc0\n       idempotent_init_module+0x104/0x300\n       __x64_sys_finit_module+0x68/0xc0\n       do_syscall_64+0x6d/0x140\n       entry_SYSCALL_64_after_hwframe+0x4b/0x53\n\n -\u0026gt; #1 (\u0026amp;dev-\u0026gt;cache.rb_lock){+.+.}-{4:4}:\n       __mutex_lock+0x98/0xf10\n       __mlx5_ib_dereg_mr+0x6f2/0x890 [mlx5_ib]\n       mlx5_ib_dereg_mr+0x21/0x110 [mlx5_ib]\n       ib_dereg_mr_user+0x85/0x1f0 [ib_core]\n  \n---truncated---(CVE-2025-38373)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nHID: core: Harden s32ton() against conversion to 0 bits\n\nTesting by the syzbot fuzzer showed that the HID core gets a\nshift-out-of-bounds exception when it tries to convert a 32-bit\nquantity to a 0-bit quantity.  Ideally this should never occur, but\nthere are buggy devices and some might have a report field with size\nset to zero; we shouldn\u0026apos;t reject the report or the device just because\nof that.\n\nInstead, harden the s32ton() routine so that it returns a reasonable\nresult instead of crashing when it is called with the number of bits\nset to 0 -- the same as what snto32() does.(CVE-2025-38556)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nbpf: Reject narrower access to pointer ctx fields\n\nThe following BPF program, simplified from a syzkaller repro, causes a\nkernel warning:\n\n    r0 = *(u8 *)(r1 + 169);\n    exit;\n\nWith pointer field sk being at offset 168 in __sk_buff. This access is\ndetected as a narrower read in bpf_skb_is_valid_access because it\ndoesn\u0026apos;t match offsetof(struct __sk_buff, sk). It is therefore allowed\nand later proceeds to bpf_convert_ctx_access. Note that for the\n\u0026quot;is_narrower_load\u0026quot; case in the convert_ctx_accesses(), the insn-\u0026gt;off\nis aligned, so the cnt may not be 0 because it matches the\noffsetof(struct __sk_buff, sk) in the bpf_convert_ctx_access. However,\nthe target_size stays 0 and the verifier errors with a kernel warning:\n\n    verifier bug: error during ctx access conversion(1)\n\nThis patch fixes that to return a proper \u0026quot;invalid bpf_context access\noff=X size=Y\u0026quot; error on the load instruction.\n\nThe same issue affects multiple other fields in context structures that\nallow narrow access. Some other non-affected fields (for sk_msg,\nsk_lookup, and sockopt) were also changed to use bpf_ctx_range_ptr for\nconsistency.\n\nNote this syzkaller crash was reported in the \u0026quot;Closes\u0026quot; link below, which\nused to be about a different bug, fixed in\ncommit fce7bd8e385a (\u0026quot;bpf/verifier: Handle BPF_LOAD_ACQ instructions\nin insn_def_regno()\u0026quot;). Because syzbot somehow confused the two bugs,\nthe new crash and repro didn\u0026apos;t get reported to the mailing list.(CVE-2025-38591)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ngfs2: No more self recovery\n\nWhen a node withdraws and it turns out that it is the only node that has\nthe filesystem mounted, gfs2 currently tries to replay the local journal\nto bring the filesystem back into a consistent state.  Not only is that\na very bad idea, it has also never worked because gfs2_recover_func()\nwill refuse to do anything during a withdraw.\n\nHowever, before even getting to this point, gfs2_recover_func()\ndereferences sdp-\u0026gt;sd_jdesc-\u0026gt;jd_inode.  This was a use-after-free before\ncommit 04133b607a78 (\u0026quot;gfs2: Prevent double iput for journal on error\u0026quot;)\nand is a NULL pointer dereference since then.\n\nSimply get rid of self recovery to fix that.(CVE-2025-38659)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nio_uring/net: commit partial buffers on retry\n\nRing provided buffers are potentially only valid within the single\nexecution context in which they were acquired. io_uring deals with this\nand invalidates them on retry. But on the networking side, if\nMSG_WAITALL is set, or if the socket is of the streaming type and too\nlittle was processed, then it will hang on to the buffer rather than\nrecycle or commit it. This is problematic for two reasons:\n\n1) If someone unregisters the provided buffer ring before a later retry,\n   then the req-\u0026gt;buf_list will no longer be valid.\n\n2) If multiple sockers are using the same buffer group, then multiple\n   receives can consume the same memory. This can cause data corruption\n   in the application, as either receive could land in the same\n   userspace buffer.\n\nFix this by disallowing partial retries from pinning a provided buffer\nacross multiple executions, if ring provided buffers are used.(CVE-2025-38730)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nmedia: rainshadow-cec: fix TOCTOU race condition in rain_interrupt()\n\nIn the interrupt handler rain_interrupt(), the buffer full check on\nrain-\u0026gt;buf_len is performed before acquiring rain-\u0026gt;buf_lock. This\ncreates a Time-of-Check to Time-of-Use (TOCTOU) race condition, as\nrain-\u0026gt;buf_len is concurrently accessed and modified in the work\nhandler rain_irq_work_handler() under the same lock.\n\nMultiple interrupt invocations can race, with each reading buf_len\nbefore it becomes full and then proceeding. This can lead to both\ninterrupts attempting to write to the buffer, incrementing buf_len\nbeyond its capacity (DATA_SIZE) and causing a buffer overflow.\n\nFix this bug by moving the spin_lock() to before the buffer full\ncheck. This ensures that the check and the subsequent buffer modification\nare performed atomically, preventing the race condition. An corresponding\nspin_unlock() is added to the overflow path to correctly release the\nlock.\n\nThis possible bug was found by an experimental static analysis tool\ndeveloped by our team.(CVE-2025-39713)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\niommu/amd/pgtbl: Fix possible race while increase page table level\n\nThe AMD IOMMU host page table implementation supports dynamic page table levels\n(up to 6 levels), starting with a 3-level configuration that expands based on\nIOVA address. The kernel maintains a root pointer and current page table level\nto enable proper page table walks in alloc_pte()/fetch_pte() operations.\n\nThe IOMMU IOVA allocator initially starts with 32-bit address and onces its\nexhuasted it switches to 64-bit address (max address is determined based\non IOMMU and device DMA capability). To support larger IOVA, AMD IOMMU\ndriver increases page table level.\n\nBut in unmap path (iommu_v1_unmap_pages()), fetch_pte() reads\npgtable-\u0026gt;[root/mode] without lock. So its possible that in exteme corner case,\nwhen increase_address_space() is updating pgtable-\u0026gt;[root/mode], fetch_pte()\nreads wrong page table level (pgtable-\u0026gt;mode). It does compare the value with\nlevel encoded in page table and returns NULL. This will result is\niommu_unmap ops to fail and upper layer may retry/log WARN_ON.\n\nCPU 0                                         CPU 1\n------                                       ------\nmap pages                                    unmap pages\nalloc_pte() -\u0026gt; increase_address_space()      iommu_v1_unmap_pages() -\u0026gt; fetch_pte()\n  pgtable-\u0026gt;root = pte (new root value)\n                                             READ pgtable-\u0026gt;[mode/root]\n\t\t\t\t\t       Reads new root, old mode\n  Updates mode (pgtable-\u0026gt;mode += 1)\n\nSince Page table level updates are infrequent and already synchronized with a\nspinlock, implement seqcount to enable lock-free read operations on the read path.(CVE-2025-39961)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\npinctrl: check the return value of pinmux_ops::get_function_name()\n\nWhile the API contract in docs doesn\u0026apos;t specify it explicitly, the\ngeneric implementation of the get_function_name() callback from struct\npinmux_ops - pinmux_generic_get_function_name() - can fail and return\nNULL. This is already checked in pinmux_check_ops() so add a similar\ncheck in pinmux_func_name_to_selector() instead of passing the returned\npointer right down to strcmp() where the NULL can get dereferenced. This\nis normal operation when adding new pinfunctions.(CVE-2025-40030)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ndrm/sched: Fix potential double free in drm_sched_job_add_resv_dependencies\n\nWhen adding dependencies with drm_sched_job_add_dependency(), that\nfunction consumes the fence reference both on success and failure, so in\nthe latter case the dma_fence_put() on the error path (xarray failed to\nexpand) is a double free.\n\nInterestingly this bug appears to have been present ever since\ncommit ebd5f74255b9 (\u0026quot;drm/sched: Add dependency tracking\u0026quot;), since the code\nback then looked like this:\n\ndrm_sched_job_add_implicit_dependencies():\n...\n       for (i = 0; i \u0026lt; fence_count; i++) {\n               ret = drm_sched_job_add_dependency(job, fences[i]);\n               if (ret)\n                       break;\n       }\n\n       for (; i \u0026lt; fence_count; i++)\n               dma_fence_put(fences[i]);\n\nWhich means for the failing \u0026apos;i\u0026apos; the dma_fence_put was already a double\nfree. Possibly there were no users at that time, or the test cases were\ninsufficient to hit it.\n\nThe bug was then only noticed and fixed after\ncommit 9c2ba265352a (\u0026quot;drm/scheduler: use new iterator in drm_sched_job_add_implicit_dependencies v2\u0026quot;)\nlanded, with its fixup of\ncommit 4eaf02d6076c (\u0026quot;drm/scheduler: fix drm_sched_job_add_implicit_dependencies\u0026quot;).\n\nAt that point it was a slightly different flavour of a double free, which\ncommit 963d0b356935 (\u0026quot;drm/scheduler: fix drm_sched_job_add_implicit_dependencies harder\u0026quot;)\nnoticed and attempted to fix.\n\nBut it only moved the double free from happening inside the\ndrm_sched_job_add_dependency(), when releasing the reference not yet\nobtained, to the caller, when releasing the reference already released by\nthe former in the failure case.\n\nAs such it is not easy to identify the right target for the fixes tag so\nlets keep it simple and just continue the chain.\n\nWhile fixing we also improve the comment and explain the reason for taking\nthe reference and not dropping it.(CVE-2025-40096)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nxfrm: delete x-\u0026gt;tunnel as we delete x\n\nThe ipcomp fallback tunnels currently get deleted (from the various\nlists and hashtables) as the last user state that needed that fallback\nis destroyed (not deleted). If a reference to that user state still\nexists, the fallback state will remain on the hashtables/lists,\ntriggering the WARN in xfrm_state_fini. Because of those remaining\nreferences, the fix in commit f75a2804da39 (\u0026quot;xfrm: destroy xfrm_state\nsynchronously on net exit path\u0026quot;) is not complete.\n\nWe recently fixed one such situation in TCP due to defered freeing of\nskbs (commit 9b6412e6979f (\u0026quot;tcp: drop secpath at the same time as we\ncurrently drop dst\u0026quot;)). This can also happen due to IP reassembly: skbs\nwith a secpath remain on the reassembly queue until netns\ndestruction. If we can\u0026apos;t guarantee that the queues are flushed by the\ntime xfrm_state_fini runs, there may still be references to a (user)\nxfrm_state, preventing the timely deletion of the corresponding\nfallback state.\n\nInstead of chasing each instance of skbs holding a secpath one by one,\nthis patch fixes the issue directly within xfrm, by deleting the\nfallback state as soon as the last user state depending on it has been\ndeleted. Destruction will still happen when the final reference is\ndropped.\n\nA separate lockdep class for the fallback state is required since\nwe\u0026apos;re going to lock x-\u0026gt;tunnel while x is locked.(CVE-2025-40215)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nfuse: fix livelock in synchronous file put from fuseblk workers\n\nI observed a hang when running generic/323 against a fuseblk server.\nThis test opens a file, initiates a lot of AIO writes to that file\ndescriptor, and closes the file descriptor before the writes complete.\nUnsurprisingly, the AIO exerciser threads are mostly stuck waiting for\nresponses from the fuseblk server:\n\n# cat /proc/372265/task/372313/stack\n[\u0026lt;0\u0026gt;] request_wait_answer+0x1fe/0x2a0 [fuse]\n[\u0026lt;0\u0026gt;] __fuse_simple_request+0xd3/0x2b0 [fuse]\n[\u0026lt;0\u0026gt;] fuse_do_getattr+0xfc/0x1f0 [fuse]\n[\u0026lt;0\u0026gt;] fuse_file_read_iter+0xbe/0x1c0 [fuse]\n[\u0026lt;0\u0026gt;] aio_read+0x130/0x1e0\n[\u0026lt;0\u0026gt;] io_submit_one+0x542/0x860\n[\u0026lt;0\u0026gt;] __x64_sys_io_submit+0x98/0x1a0\n[\u0026lt;0\u0026gt;] do_syscall_64+0x37/0xf0\n[\u0026lt;0\u0026gt;] entry_SYSCALL_64_after_hwframe+0x4b/0x53\n\nBut the /weird/ part is that the fuseblk server threads are waiting for\nresponses from itself:\n\n# cat /proc/372210/task/372232/stack\n[\u0026lt;0\u0026gt;] request_wait_answer+0x1fe/0x2a0 [fuse]\n[\u0026lt;0\u0026gt;] __fuse_simple_request+0xd3/0x2b0 [fuse]\n[\u0026lt;0\u0026gt;] fuse_file_put+0x9a/0xd0 [fuse]\n[\u0026lt;0\u0026gt;] fuse_release+0x36/0x50 [fuse]\n[\u0026lt;0\u0026gt;] __fput+0xec/0x2b0\n[\u0026lt;0\u0026gt;] task_work_run+0x55/0x90\n[\u0026lt;0\u0026gt;] syscall_exit_to_user_mode+0xe9/0x100\n[\u0026lt;0\u0026gt;] do_syscall_64+0x43/0xf0\n[\u0026lt;0\u0026gt;] entry_SYSCALL_64_after_hwframe+0x4b/0x53\n\nThe fuseblk server is fuse2fs so there\u0026apos;s nothing all that exciting in\nthe server itself.  So why is the fuse server calling fuse_file_put?\nThe commit message for the fstest sheds some light on that:\n\n\u0026quot;By closing the file descriptor before calling io_destroy, you pretty\nmuch guarantee that the last put on the ioctx will be done in interrupt\ncontext (during I/O completion).\n\nAha.  AIO fgets a new struct file from the fd when it queues the ioctx.\nThe completion of the FUSE_WRITE command from userspace causes the fuse\nserver to call the AIO completion function.  The completion puts the\nstruct file, queuing a delayed fput to the fuse server task.  When the\nfuse server task returns to userspace, it has to run the delayed fput,\nwhich in the case of a fuseblk server, it does synchronously.\n\nSending the FUSE_RELEASE command sychronously from fuse server threads\nis a bad idea because a client program can initiate enough simultaneous\nAIOs such that all the fuse server threads end up in delayed_fput, and\nnow there aren\u0026apos;t any threads left to handle the queued fuse commands.\n\nFix this by only using asynchronous fputs when closing files, and leave\na comment explaining why.(CVE-2025-40220)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nfs/notify: call exportfs_encode_fid with s_umount\n\nCalling intotify_show_fdinfo() on fd watching an overlayfs inode, while\nthe overlayfs is being unmounted, can lead to dereferencing NULL ptr.\n\nThis issue was found by syzkaller.\n\nRace Condition Diagram:\n\nThread 1                           Thread 2\n--------                           --------\n\ngeneric_shutdown_super()\n shrink_dcache_for_umount\n  sb-\u0026gt;s_root = NULL\n\n                    |\n                    |             vfs_read()\n                    |              inotify_fdinfo()\n                    |               * inode get from mark *\n                    |               show_mark_fhandle(m, inode)\n                    |                exportfs_encode_fid(inode, ..)\n                    |                 ovl_encode_fh(inode, ..)\n                    |                  ovl_check_encode_origin(inode)\n                    |                   * deref i_sb-\u0026gt;s_root *\n                    |\n                    |\n                    v\n fsnotify_sb_delete(sb)\n\nWhich then leads to:\n\n[   32.133461] Oops: general protection fault, probably for non-canonical address 0xdffffc0000000006: 0000 [#1] SMP DEBUG_PAGEALLOC KASAN NOPTI\n[   32.134438] KASAN: null-ptr-deref in range [0x0000000000000030-0x0000000000000037]\n[   32.135032] CPU: 1 UID: 0 PID: 4468 Comm: systemd-coredum Not tainted 6.17.0-rc6 #22 PREEMPT(none)\n\n\u0026lt;snip registers, unreliable trace\u0026gt;\n\n[   32.143353] Call Trace:\n[   32.143732]  ovl_encode_fh+0xd5/0x170\n[   32.144031]  exportfs_encode_inode_fh+0x12f/0x300\n[   32.144425]  show_mark_fhandle+0xbe/0x1f0\n[   32.145805]  inotify_fdinfo+0x226/0x2d0\n[   32.146442]  inotify_show_fdinfo+0x1c5/0x350\n[   32.147168]  seq_show+0x530/0x6f0\n[   32.147449]  seq_read_iter+0x503/0x12a0\n[   32.148419]  seq_read+0x31f/0x410\n[   32.150714]  vfs_read+0x1f0/0x9e0\n[   32.152297]  ksys_read+0x125/0x240\n\nIOW ovl_check_encode_origin derefs inode-\u0026gt;i_sb-\u0026gt;s_root, after it was set\nto NULL in the unmount path.\n\nFix it by protecting calling exportfs_encode_fid() from\nshow_mark_fhandle() with s_umount lock.\n\nThis form of fix was suggested by Amir in [1].\n\n[1]: https://lore.kernel.org/all/CAOQ4uxhbDwhb+2Brs1UdkoF0a3NSdBAOQPNfEHjahrgoKJpLEw@mail.gmail.com/(CVE-2025-40237)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ngfs2: Fix unlikely race in gdlm_put_lock\n\nIn gdlm_put_lock(), there is a small window of time in which the\nDFL_UNMOUNT flag has been set but the lockspace hasn\u0026apos;t been released,\nyet.  In that window, dlm may still call gdlm_ast() and gdlm_bast().\nTo prevent it from dereferencing freed glock objects, only free the\nglock if the lockspace has actually been released.(CVE-2025-40242)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ndevlink: rate: Unset parent pointer in devl_rate_nodes_destroy\n\nThe function devl_rate_nodes_destroy is documented to \u0026quot;Unset parent for\nall rate objects\u0026quot;. However, it was only calling the driver-specific\n`rate_leaf_parent_set` or `rate_node_parent_set` ops and decrementing\nthe parent\u0026apos;s refcount, without actually setting the\n`devlink_rate-\u0026gt;parent` pointer to NULL.\n\nThis leaves a dangling pointer in the `devlink_rate` struct, which cause\nrefcount error in netdevsim[1] and mlx5[2]. In addition, this is\ninconsistent with the behavior of `devlink_nl_rate_parent_node_set`,\nwhere the parent pointer is correctly cleared.\n\nThis patch fixes the issue by explicitly setting `devlink_rate-\u0026gt;parent`\nto NULL after notifying the driver, thus fulfilling the function\u0026apos;s\ndocumented behavior for all rate objects.\n\n[1]\nrepro steps:\necho 1 \u0026gt; /sys/bus/netdevsim/new_device\ndevlink dev eswitch set netdevsim/netdevsim1 mode switchdev\necho 1 \u0026gt; /sys/bus/netdevsim/devices/netdevsim1/sriov_numvfs\ndevlink port function rate add netdevsim/netdevsim1/test_node\ndevlink port function rate set netdevsim/netdevsim1/128 parent test_node\necho 1 \u0026gt; /sys/bus/netdevsim/del_device\n\ndmesg:\nrefcount_t: decrement hit 0; leaking memory.\nWARNING: CPU: 8 PID: 1530 at lib/refcount.c:31 refcount_warn_saturate+0x42/0xe0\nCPU: 8 UID: 0 PID: 1530 Comm: bash Not tainted 6.18.0-rc4+ #1 NONE\nHardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS rel-1.16.0-0-gd239552ce722-prebuilt.qemu.org 04/01/2014\nRIP: 0010:refcount_warn_saturate+0x42/0xe0\nCall Trace:\n \u0026lt;TASK\u0026gt;\n devl_rate_leaf_destroy+0x8d/0x90\n __nsim_dev_port_del+0x6c/0x70 [netdevsim]\n nsim_dev_reload_destroy+0x11c/0x140 [netdevsim]\n nsim_drv_remove+0x2b/0xb0 [netdevsim]\n device_release_driver_internal+0x194/0x1f0\n bus_remove_device+0xc6/0x130\n device_del+0x159/0x3c0\n device_unregister+0x1a/0x60\n del_device_store+0x111/0x170 [netdevsim]\n kernfs_fop_write_iter+0x12e/0x1e0\n vfs_write+0x215/0x3d0\n ksys_write+0x5f/0xd0\n do_syscall_64+0x55/0x10f0\n entry_SYSCALL_64_after_hwframe+0x4b/0x53\n\n[2]\ndevlink dev eswitch set pci/0000:08:00.0 mode switchdev\ndevlink port add pci/0000:08:00.0 flavour pcisf pfnum 0 sfnum 1000\ndevlink port function rate add pci/0000:08:00.0/group1\ndevlink port function rate set pci/0000:08:00.0/32768 parent group1\nmodprobe -r mlx5_ib mlx5_fwctl mlx5_core\n\ndmesg:\nrefcount_t: decrement hit 0; leaking memory.\nWARNING: CPU: 7 PID: 16151 at lib/refcount.c:31 refcount_warn_saturate+0x42/0xe0\nCPU: 7 UID: 0 PID: 16151 Comm: bash Not tainted 6.17.0-rc7_for_upstream_min_debug_2025_10_02_12_44 #1 NONE\nHardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS rel-1.16.3-0-ga6ed6b701f0a-prebuilt.qemu.org 04/01/2014\nRIP: 0010:refcount_warn_saturate+0x42/0xe0\nCall Trace:\n \u0026lt;TASK\u0026gt;\n devl_rate_leaf_destroy+0x8d/0x90\n mlx5_esw_offloads_devlink_port_unregister+0x33/0x60 [mlx5_core]\n mlx5_esw_offloads_unload_rep+0x3f/0x50 [mlx5_core]\n mlx5_eswitch_unload_sf_vport+0x40/0x90 [mlx5_core]\n mlx5_sf_esw_event+0xc4/0x120 [mlx5_core]\n notifier_call_chain+0x33/0xa0\n blocking_notifier_call_chain+0x3b/0x50\n mlx5_eswitch_disable_locked+0x50/0x110 [mlx5_core]\n mlx5_eswitch_disable+0x63/0x90 [mlx5_core]\n mlx5_unload+0x1d/0x170 [mlx5_core]\n mlx5_uninit_one+0xa2/0x130 [mlx5_core]\n remove_one+0x78/0xd0 [mlx5_core]\n pci_device_remove+0x39/0xa0\n device_release_driver_internal+0x194/0x1f0\n unbind_store+0x99/0xa0\n kernfs_fop_write_iter+0x12e/0x1e0\n vfs_write+0x215/0x3d0\n ksys_write+0x5f/0xd0\n do_syscall_64+0x53/0x1f0\n entry_SYSCALL_64_after_hwframe+0x4b/0x53(CVE-2025-40251)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nfs/proc: fix uaf in proc_readdir_de()\n\nPde is erased from subdir rbtree through rb_erase(), but not set the node\nto EMPTY, which may result in uaf access.  We should use RB_CLEAR_NODE()\nset the erased node to EMPTY, then pde_subdir_next() will return NULL to\navoid uaf access.\n\nWe found an uaf issue while using stress-ng testing, need to run testcase\ngetdent and tun in the same time.  The steps of the issue is as follows:\n\n1) use getdent to traverse dir /proc/pid/net/dev_snmp6/, and current\n   pde is tun3;\n\n2) in the [time windows] unregister netdevice tun3 and tun2, and erase\n   them from rbtree.  erase tun3 first, and then erase tun2.  the\n   pde(tun2) will be released to slab;\n\n3) continue to getdent process, then pde_subdir_next() will return\n   pde(tun2) which is released, it will case uaf access.\n\nCPU 0                                      |    CPU 1\n-------------------------------------------------------------------------\ntraverse dir /proc/pid/net/dev_snmp6/      |   unregister_netdevice(tun-\u0026gt;dev)   //tun3 tun2\nsys_getdents64()                           |\n  iterate_dir()                            |\n    proc_readdir()                         |\n      proc_readdir_de()                    |     snmp6_unregister_dev()\n        pde_get(de);                       |       proc_remove()\n        read_unlock(\u0026amp;proc_subdir_lock);    |         remove_proc_subtree()\n                                           |           write_lock(\u0026amp;proc_subdir_lock);\n        [time window]                      |           rb_erase(\u0026amp;root-\u0026gt;subdir_node, \u0026amp;parent-\u0026gt;subdir);\n                                           |           write_unlock(\u0026amp;proc_subdir_lock);\n        read_lock(\u0026amp;proc_subdir_lock);      |\n        next = pde_subdir_next(de);        |\n        pde_put(de);                       |\n        de = next;    //UAF                |\n\nrbtree of dev_snmp6\n                        |\n                    pde(tun3)\n                     /    \\\n                  NULL  pde(tun2)(CVE-2025-40271)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nmm/secretmem: fix use-after-free race in fault handler\n\nWhen a page fault occurs in a secret memory file created with\n`memfd_secret(2)`, the kernel will allocate a new folio for it, mark the\nunderlying page as not-present in the direct map, and add it to the file\nmapping.\n\nIf two tasks cause a fault in the same page concurrently, both could end\nup allocating a folio and removing the page from the direct map, but only\none would succeed in adding the folio to the file mapping.  The task that\nfailed undoes the effects of its attempt by (a) freeing the folio again\nand (b) putting the page back into the direct map.  However, by doing\nthese two operations in this order, the page becomes available to the\nallocator again before it is placed back in the direct mapping.\n\nIf another task attempts to allocate the page between (a) and (b), and the\nkernel tries to access it via the direct map, it would result in a\nsupervisor not-present page fault.\n\nFix the ordering to restore the direct map before the folio is freed.(CVE-2025-40272)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ndrm/vmwgfx: Validate command header size against SVGA_CMD_MAX_DATASIZE\n\nThis data originates from userspace and is used in buffer offset\ncalculations which could potentially overflow causing an out-of-bounds\naccess.(CVE-2025-40277)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nBluetooth: MGMT: Fix OOB access in parse_adv_monitor_pattern()\n\nIn the parse_adv_monitor_pattern() function, the value of\nthe \u0026apos;length\u0026apos; variable is currently limited to HCI_MAX_EXT_AD_LENGTH(251).\nThe size of the \u0026apos;value\u0026apos; array in the mgmt_adv_pattern structure is 31.\nIf the value of \u0026apos;pattern[i].length\u0026apos; is set in the user space\nand exceeds 31, the \u0026apos;patterns[i].value\u0026apos; array can be accessed\nout of bound when copied.\n\nIncreasing the size of the \u0026apos;value\u0026apos; array in\nthe \u0026apos;mgmt_adv_pattern\u0026apos; structure will break the userspace.\nConsidering this, and to avoid OOB access revert the limits for \u0026apos;offset\u0026apos;\nand \u0026apos;length\u0026apos; back to the value of HCI_MAX_AD_LENGTH.\n\nFound by InfoTeCS on behalf of Linux Verification Center\n(linuxtesting.org) with SVACE.(CVE-2025-40294)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nBluetooth: hci_event: validate skb length for unknown CC opcode\n\nIn hci_cmd_complete_evt(), if the command complete event has an unknown\nopcode, we assume the first byte of the remaining skb-\u0026gt;data contains the\nreturn status. However, parameter data has previously been pulled in\nhci_event_func(), which may leave the skb empty. If so, using skb-\u0026gt;data[0]\nfor the return status uses un-init memory.\n\nThe fix is to check skb-\u0026gt;len before using skb-\u0026gt;data.(CVE-2025-40301)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nBluetooth: bcsp: receive data only if registered\n\nCurrently, bcsp_recv() can be called even when the BCSP protocol has not\nbeen registered. This leads to a NULL pointer dereference, as shown in\nthe following stack trace:\n\n    KASAN: null-ptr-deref in range [0x0000000000000108-0x000000000000010f]\n    RIP: 0010:bcsp_recv+0x13d/0x1740 drivers/bluetooth/hci_bcsp.c:590\n    Call Trace:\n     \u0026lt;TASK\u0026gt;\n     hci_uart_tty_receive+0x194/0x220 drivers/bluetooth/hci_ldisc.c:627\n     tiocsti+0x23c/0x2c0 drivers/tty/tty_io.c:2290\n     tty_ioctl+0x626/0xde0 drivers/tty/tty_io.c:2706\n     vfs_ioctl fs/ioctl.c:51 [inline]\n     __do_sys_ioctl fs/ioctl.c:907 [inline]\n     __se_sys_ioctl+0xfc/0x170 fs/ioctl.c:893\n     do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline]\n     do_syscall_64+0xfa/0x3b0 arch/x86/entry/syscall_64.c:94\n     entry_SYSCALL_64_after_hwframe+0x77/0x7f\n\nTo prevent this, ensure that the HCI_UART_REGISTERED flag is set before\nprocessing received data. If the protocol is not registered, return\n-EUNATCH.(CVE-2025-40308)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nBluetooth: hci_sync: fix race in hci_cmd_sync_dequeue_once\n\nhci_cmd_sync_dequeue_once() does lookup and then cancel\nthe entry under two separate lock sections. Meanwhile,\nhci_cmd_sync_work() can also delete the same entry,\nleading to double list_del() and \u0026quot;UAF\u0026quot;.\n\nFix this by holding cmd_sync_work_lock across both\nlookup and cancel, so that the entry cannot be removed\nconcurrently.(CVE-2025-40318)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nfutex: Don\u0026apos;t leak robust_list pointer on exec race\n\nsys_get_robust_list() and compat_get_robust_list() use ptrace_may_access()\nto check if the calling task is allowed to access another task\u0026apos;s\nrobust_list pointer. This check is racy against a concurrent exec() in the\ntarget process.\n\nDuring exec(), a task may transition from a non-privileged binary to a\nprivileged one (e.g., setuid binary) and its credentials/memory mappings\nmay change. If get_robust_list() performs ptrace_may_access() before\nthis transition, it may erroneously allow access to sensitive information\nafter the target becomes privileged.\n\nA racy access allows an attacker to exploit a window during which\nptrace_may_access() passes before a target process transitions to a\nprivileged state via exec().\n\nFor example, consider a non-privileged task T that is about to execute a\nsetuid-root binary. An attacker task A calls get_robust_list(T) while T\nis still unprivileged. Since ptrace_may_access() checks permissions\nbased on current credentials, it succeeds. However, if T begins exec\nimmediately afterwards, it becomes privileged and may change its memory\nmappings. Because get_robust_list() proceeds to access T-\u0026gt;robust_list\nwithout synchronizing with exec() it may read user-space pointers from a\nnow-privileged process.\n\nThis violates the intended post-exec access restrictions and could\nexpose sensitive memory addresses or be used as a primitive in a larger\nexploit chain. Consequently, the race can lead to unauthorized\ndisclosure of information across privilege boundaries and poses a\npotential security risk.\n\nTake a read lock on signal-\u0026gt;exec_update_lock prior to invoking\nptrace_may_access() and accessing the robust_list/compat_robust_list.\nThis ensures that the target task\u0026apos;s exec state remains stable during the\ncheck, allowing for consistent and synchronized validation of\ncredentials.(CVE-2025-40341)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnvme-fc: use lock accessing port_state and rport state\n\nnvme_fc_unregister_remote removes the remote port on a lport object at\nany point in time when there is no active association. This races with\nwith the reconnect logic, because nvme_fc_create_association is not\ntaking a lock to check the port_state and atomically increase the\nactive count on the rport.(CVE-2025-40342)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnvmet-fc: avoid scheduling association deletion twice\n\nWhen forcefully shutting down a port via the configfs interface,\nnvmet_port_subsys_drop_link() first calls nvmet_port_del_ctrls() and\nthen nvmet_disable_port(). Both functions will eventually schedule all\nremaining associations for deletion.\n\nThe current implementation checks whether an association is about to be\nremoved, but only after the work item has already been scheduled. As a\nresult, it is possible for the first scheduled work item to free all\nresources, and then for the same work item to be scheduled again for\ndeletion.\n\nBecause the association list is an RCU list, it is not possible to take\na lock and remove the list entry directly, so it cannot be looked up\nagain. Instead, a flag (terminating) must be used to determine whether\nthe association is already in the process of being deleted.(CVE-2025-40343)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\narch_topology: Fix incorrect error check in topology_parse_cpu_capacity()\n\nFix incorrect use of PTR_ERR_OR_ZERO() in topology_parse_cpu_capacity()\nwhich causes the code to proceed with NULL clock pointers. The current\nlogic uses !PTR_ERR_OR_ZERO(cpu_clk) which evaluates to true for both\nvalid pointers and NULL, leading to potential NULL pointer dereference\nin clk_get_rate().\n\nPer include/linux/err.h documentation, PTR_ERR_OR_ZERO(ptr) returns:\n\u0026quot;The error code within @ptr if it is an error pointer; 0 otherwise.\u0026quot;\n\nThis means PTR_ERR_OR_ZERO() returns 0 for both valid pointers AND NULL\npointers. Therefore !PTR_ERR_OR_ZERO(cpu_clk) evaluates to true (proceed)\nwhen cpu_clk is either valid or NULL, causing clk_get_rate(NULL) to be\ncalled when of_clk_get() returns NULL.\n\nReplace with !IS_ERR_OR_NULL(cpu_clk) which only proceeds for valid\npointers, preventing potential NULL pointer dereference in clk_get_rate().(CVE-2025-40346)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nhfsplus: fix KMSAN uninit-value issue in hfsplus_delete_cat()\n\nThe syzbot reported issue in hfsplus_delete_cat():\n\n[   70.682285][ T9333] =====================================================\n[   70.682943][ T9333] BUG: KMSAN: uninit-value in hfsplus_subfolders_dec+0x1d7/0x220\n[   70.683640][ T9333]  hfsplus_subfolders_dec+0x1d7/0x220\n[   70.684141][ T9333]  hfsplus_delete_cat+0x105d/0x12b0\n[   70.684621][ T9333]  hfsplus_rmdir+0x13d/0x310\n[   70.685048][ T9333]  vfs_rmdir+0x5ba/0x810\n[   70.685447][ T9333]  do_rmdir+0x964/0xea0\n[   70.685833][ T9333]  __x64_sys_rmdir+0x71/0xb0\n[   70.686260][ T9333]  x64_sys_call+0xcd8/0x3cf0\n[   70.686695][ T9333]  do_syscall_64+0xd9/0x1d0\n[   70.687119][ T9333]  entry_SYSCALL_64_after_hwframe+0x77/0x7f\n[   70.687646][ T9333]\n[   70.687856][ T9333] Uninit was stored to memory at:\n[   70.688311][ T9333]  hfsplus_subfolders_inc+0x1c2/0x1d0\n[   70.688779][ T9333]  hfsplus_create_cat+0x148e/0x1800\n[   70.689231][ T9333]  hfsplus_mknod+0x27f/0x600\n[   70.689730][ T9333]  hfsplus_mkdir+0x5a/0x70\n[   70.690146][ T9333]  vfs_mkdir+0x483/0x7a0\n[   70.690545][ T9333]  do_mkdirat+0x3f2/0xd30\n[   70.690944][ T9333]  __x64_sys_mkdir+0x9a/0xf0\n[   70.691380][ T9333]  x64_sys_call+0x2f89/0x3cf0\n[   70.691816][ T9333]  do_syscall_64+0xd9/0x1d0\n[   70.692229][ T9333]  entry_SYSCALL_64_after_hwframe+0x77/0x7f\n[   70.692773][ T9333]\n[   70.692990][ T9333] Uninit was stored to memory at:\n[   70.693469][ T9333]  hfsplus_subfolders_inc+0x1c2/0x1d0\n[   70.693960][ T9333]  hfsplus_create_cat+0x148e/0x1800\n[   70.694438][ T9333]  hfsplus_fill_super+0x21c1/0x2700\n[   70.694911][ T9333]  mount_bdev+0x37b/0x530\n[   70.695320][ T9333]  hfsplus_mount+0x4d/0x60\n[   70.695729][ T9333]  legacy_get_tree+0x113/0x2c0\n[   70.696167][ T9333]  vfs_get_tree+0xb3/0x5c0\n[   70.696588][ T9333]  do_new_mount+0x73e/0x1630\n[   70.697013][ T9333]  path_mount+0x6e3/0x1eb0\n[   70.697425][ T9333]  __se_sys_mount+0x733/0x830\n[   70.697857][ T9333]  __x64_sys_mount+0xe4/0x150\n[   70.698269][ T9333]  x64_sys_call+0x2691/0x3cf0\n[   70.698704][ T9333]  do_syscall_64+0xd9/0x1d0\n[   70.699117][ T9333]  entry_SYSCALL_64_after_hwframe+0x77/0x7f\n[   70.699730][ T9333]\n[   70.699946][ T9333] Uninit was created at:\n[   70.700378][ T9333]  __alloc_pages_noprof+0x714/0xe60\n[   70.700843][ T9333]  alloc_pages_mpol_noprof+0x2a2/0x9b0\n[   70.701331][ T9333]  alloc_pages_noprof+0xf8/0x1f0\n[   70.701774][ T9333]  allocate_slab+0x30e/0x1390\n[   70.702194][ T9333]  ___slab_alloc+0x1049/0x33a0\n[   70.702635][ T9333]  kmem_cache_alloc_lru_noprof+0x5ce/0xb20\n[   70.703153][ T9333]  hfsplus_alloc_inode+0x5a/0xd0\n[   70.703598][ T9333]  alloc_inode+0x82/0x490\n[   70.703984][ T9333]  iget_locked+0x22e/0x1320\n[   70.704428][ T9333]  hfsplus_iget+0x5c/0xba0\n[   70.704827][ T9333]  hfsplus_btree_open+0x135/0x1dd0\n[   70.705291][ T9333]  hfsplus_fill_super+0x1132/0x2700\n[   70.705776][ T9333]  mount_bdev+0x37b/0x530\n[   70.706171][ T9333]  hfsplus_mount+0x4d/0x60\n[   70.706579][ T9333]  legacy_get_tree+0x113/0x2c0\n[   70.707019][ T9333]  vfs_get_tree+0xb3/0x5c0\n[   70.707444][ T9333]  do_new_mount+0x73e/0x1630\n[   70.707865][ T9333]  path_mount+0x6e3/0x1eb0\n[   70.708270][ T9333]  __se_sys_mount+0x733/0x830\n[   70.708711][ T9333]  __x64_sys_mount+0xe4/0x150\n[   70.709158][ T9333]  x64_sys_call+0x2691/0x3cf0\n[   70.709630][ T9333]  do_syscall_64+0xd9/0x1d0\n[   70.710053][ T9333]  entry_SYSCALL_64_after_hwframe+0x77/0x7f\n[   70.710611][ T9333]\n[   70.710842][ T9333] CPU: 3 UID: 0 PID: 9333 Comm: repro Not tainted 6.12.0-rc6-dirty #17\n[   70.711568][ T9333] Hardware name: QEMU Ubuntu 24.04 PC (i440FX + PIIX, 1996), BIOS 1.16.3-debian-1.16.3-2 04/01/2014\n[   70.712490][ T9333] =====================================================\n[   70.713085][ T9333] Disabling lock debugging due to kernel taint\n[   70.713618][ T9333] Kernel panic - not syncing: kmsan.panic set ...\n[   70.714159][ T9333] \n---truncated---(CVE-2025-40351)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nriscv: stacktrace: Disable KASAN checks for non-current tasks\n\nUnwinding the stack of a task other than current, KASAN would report\n\u0026quot;BUG: KASAN: out-of-bounds in walk_stackframe+0x41c/0x460\u0026quot;\n\nThere is a same issue on x86 and has been resolved by the commit\n84936118bdf3 (\u0026quot;x86/unwind: Disable KASAN checks for non-current tasks\u0026quot;)\nThe solution could be applied to RISC-V too.\n\nThis patch also can solve the issue:\nhttps://seclists.org/oss-sec/2025/q4/23\n\n[(CVE-2025-40358)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nperf/x86/intel: Fix KASAN global-out-of-bounds warning\n\nWhen running \u0026quot;perf mem record\u0026quot; command on CWF, the below KASAN\nglobal-out-of-bounds warning is seen.\n\n  ==================================================================\n  BUG: KASAN: global-out-of-bounds in cmt_latency_data+0x176/0x1b0\n  Read of size 4 at addr ffffffffb721d000 by task dtlb/9850\n\n  Call Trace:\n\n   kasan_report+0xb8/0xf0\n   cmt_latency_data+0x176/0x1b0\n   setup_arch_pebs_sample_data+0xf49/0x2560\n   intel_pmu_drain_arch_pebs+0x577/0xb00\n   handle_pmi_common+0x6c4/0xc80\n\nThe issue is caused by below code in __grt_latency_data(). The code\ntries to access x86_hybrid_pmu structure which doesn\u0026apos;t exist on\nnon-hybrid platform like CWF.\n\n        WARN_ON_ONCE(hybrid_pmu(event-\u0026gt;pmu)-\u0026gt;pmu_type == hybrid_big)\n\nSo add is_hybrid() check before calling this WARN_ON_ONCE to fix the\nglobal-out-of-bounds access issue.(CVE-2025-40359)\n\nRejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority.(CVE-2025-40361)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nx86/fpu: Ensure XFD state on signal delivery\n\nSean reported [1] the following splat when running KVM tests:\n\n   WARNING: CPU: 232 PID: 15391 at xfd_validate_state+0x65/0x70\n   Call Trace:\n    \u0026lt;TASK\u0026gt;\n    fpu__clear_user_states+0x9c/0x100\n    arch_do_signal_or_restart+0x142/0x210\n    exit_to_user_mode_loop+0x55/0x100\n    do_syscall_64+0x205/0x2c0\n    entry_SYSCALL_64_after_hwframe+0x4b/0x53\n\nChao further identified [2] a reproducible scenario involving signal\ndelivery: a non-AMX task is preempted by an AMX-enabled task which\nmodifies the XFD MSR.\n\nWhen the non-AMX task resumes and reloads XSTATE with init values,\na warning is triggered due to a mismatch between fpstate::xfd and the\nCPU\u0026apos;s current XFD state. fpu__clear_user_states() does not currently\nre-synchronize the XFD state after such preemption.\n\nInvoke xfd_update_state() which detects and corrects the mismatch if\nthere is a dynamic feature.\n\nThis also benefits the sigreturn path, as fpu__restore_sig() may call\nfpu__clear_user_states() when the sigframe is inaccessible.\n\n[ dhansen: minor changelog munging ](CVE-2025-68171)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nftrace: Fix softlockup in ftrace_module_enable\n\nA soft lockup was observed when loading amdgpu module.\nIf a module has a lot of tracable functions, multiple calls\nto kallsyms_lookup can spend too much time in RCU critical\nsection and with disabled preemption, causing kernel panic.\nThis is the same issue that was fixed in\ncommit d0b24b4e91fc (\u0026quot;ftrace: Prevent RCU stall on PREEMPT_VOLUNTARY\nkernels\u0026quot;) and commit 42ea22e754ba (\u0026quot;ftrace: Add cond_resched() to\nftrace_graph_set_hash()\u0026quot;).\n\nFix it the same way by adding cond_resched() in ftrace_module_enable.(CVE-2025-68173)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\namd/amdkfd: enhance kfd process check in switch partition\n\ncurrent switch partition only check if kfd_processes_table is empty.\nkfd_prcesses_table entry is deleted in kfd_process_notifier_release, but\nkfd_process tear down is in kfd_process_wq_release.\n\nconsider two processes:\n\nProcess A (workqueue) -\u0026gt; kfd_process_wq_release -\u0026gt; Access kfd_node member\nProcess B switch partition -\u0026gt; amdgpu_xcp_pre_partition_switch -\u0026gt; amdgpu_amdkfd_device_fini_sw\n-\u0026gt; kfd_node tear down.\n\nProcess A and B may trigger a race as shown in dmesg log.\n\nThis patch is to resolve the race by adding an atomic kfd_process counter\nkfd_processes_count, it increment as create kfd process, decrement as\nfinish kfd_process_wq_release.\n\nv2: Put kfd_processes_count per kfd_dev, move decrement to kfd_process_destroy_pdds\nand bug fix. (Philip Yang)\n\n[3966658.307702] divide error: 0000 [#1] SMP NOPTI\n[3966658.350818]  i10nm_edac\n[3966658.356318] CPU: 124 PID: 38435 Comm: kworker/124:0 Kdump: loaded Tainted\n[3966658.356890] Workqueue: kfd_process_wq kfd_process_wq_release [amdgpu]\n[3966658.362839]  nfit\n[3966658.366457] RIP: 0010:kfd_get_num_sdma_engines+0x17/0x40 [amdgpu]\n[3966658.366460] Code: 00 00 e9 ac 81 02 00 66 66 2e 0f 1f 84 00 00 00 00 00 90 0f 1f 44 00 00 48 8b 4f 08 48 8b b7 00 01 00 00 8b 81 58 26 03 00 99 \u0026lt;f7\u0026gt; be b8 01 00 00 80 b9 70 2e 00 00 00 74 0b 83 f8 02 ba 02 00 00\n[3966658.380967]  x86_pkg_temp_thermal\n[3966658.391529] RSP: 0018:ffffc900a0edfdd8 EFLAGS: 00010246\n[3966658.391531] RAX: 0000000000000008 RBX: ffff8974e593b800 RCX: ffff888645900000\n[3966658.391531] RDX: 0000000000000000 RSI: ffff888129154400 RDI: ffff888129151c00\n[3966658.391532] RBP: ffff8883ad79d400 R08: 0000000000000000 R09: ffff8890d2750af4\n[3966658.391532] R10: 0000000000000018 R11: 0000000000000018 R12: 0000000000000000\n[3966658.391533] R13: ffff8883ad79d400 R14: ffffe87ff662ba00 R15: ffff8974e593b800\n[3966658.391533] FS:  0000000000000000(0000) GS:ffff88fe7f600000(0000) knlGS:0000000000000000\n[3966658.391534] CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033\n[3966658.391534] CR2: 0000000000d71000 CR3: 000000dd0e970004 CR4: 0000000002770ee0\n[3966658.391535] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000\n[3966658.391535] DR3: 0000000000000000 DR6: 00000000fffe07f0 DR7: 0000000000000400\n[3966658.391536] PKRU: 55555554\n[3966658.391536] Call Trace:\n[3966658.391674]  deallocate_sdma_queue+0x38/0xa0 [amdgpu]\n[3966658.391762]  process_termination_cpsch+0x1ed/0x480 [amdgpu]\n[3966658.399754]  intel_powerclamp\n[3966658.402831]  kfd_process_dequeue_from_all_devices+0x5b/0xc0 [amdgpu]\n[3966658.402908]  kfd_process_wq_release+0x1a/0x1a0 [amdgpu]\n[3966658.410516]  coretemp\n[3966658.434016]  process_one_work+0x1ad/0x380\n[3966658.434021]  worker_thread+0x49/0x310\n[3966658.438963]  kvm_intel\n[3966658.446041]  ? process_one_work+0x380/0x380\n[3966658.446045]  kthread+0x118/0x140\n[3966658.446047]  ? __kthread_bind_mask+0x60/0x60\n[3966658.446050]  ret_from_fork+0x1f/0x30\n[3966658.446053] Modules linked in: kpatch_20765354(OEK)\n[3966658.455310]  kvm\n[3966658.464534]  mptcp_diag xsk_diag raw_diag unix_diag af_packet_diag netlink_diag udp_diag act_pedit act_mirred act_vlan cls_flower kpatch_21951273(OEK) kpatch_18424469(OEK) kpatch_19749756(OEK)\n[3966658.473462]  idxd_mdev\n[3966658.482306]  kpatch_17971294(OEK) sch_ingress xt_conntrack amdgpu(OE) amdxcp(OE) amddrm_buddy(OE) amd_sched(OE) amdttm(OE) amdkcl(OE) intel_ifs iptable_mangle tcm_loop target_core_pscsi tcp_diag target_core_file inet_diag target_core_iblock target_core_user target_core_mod coldpgs kpatch_18383292(OEK) ip6table_nat ip6table_filter ip6_tables ip_set_hash_ipportip ip_set_hash_ipportnet ip_set_hash_ipport ip_set_bitmap_port xt_comment iptable_nat nf_nat iptable_filter ip_tables ip_set ip_vs_sh ip_vs_wrr ip_vs_rr ip_vs nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 sn_core_odd(OE) i40e overlay binfmt_misc tun bonding(OE) aisqos(OE) aisqo\n---truncated---(CVE-2025-68174)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nPCI: cadence: Check for the existence of cdns_pcie::ops before using it\n\ncdns_pcie::ops might not be populated by all the Cadence glue drivers. This\nis going to be true for the upcoming Sophgo platform which doesn\u0026apos;t set the\nops.\n\nHence, add a check to prevent NULL pointer dereference.\n\n[mani: reworded subject and description](CVE-2025-68176)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ntcp: use dst_dev_rcu() in tcp_fastopen_active_disable_ofo_check()\n\nUse RCU to avoid a pair of atomic operations and a potential\nUAF on dst_dev()-\u0026gt;flags.(CVE-2025-68188)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nbpf: Add bpf_prog_run_data_pointers()\n\nsyzbot found that cls_bpf_classify() is able to change\ntc_skb_cb(skb)-\u0026gt;drop_reason triggering a warning in sk_skb_reason_drop().\n\nWARNING: CPU: 0 PID: 5965 at net/core/skbuff.c:1192 __sk_skb_reason_drop net/core/skbuff.c:1189 [inline]\nWARNING: CPU: 0 PID: 5965 at net/core/skbuff.c:1192 sk_skb_reason_drop+0x76/0x170 net/core/skbuff.c:1214\n\nstruct tc_skb_cb has been added in commit ec624fe740b4 (\u0026quot;net/sched:\nExtend qdisc control block with tc control block\u0026quot;), which added a wrong\ninteraction with db58ba459202 (\u0026quot;bpf: wire in data and data_end for\ncls_act_bpf\u0026quot;).\n\ndrop_reason was added later.\n\nAdd bpf_prog_run_data_pointers() helper to save/restore the net_sched\nstorage colliding with BPF data_meta/data_end.(CVE-2025-68200)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnetfilter: nft_ct: add seqadj extension for natted connections\n\nSequence adjustment may be required for FTP traffic with PASV/EPSV modes.\ndue to need to re-write packet payload (IP, port) on the ftp control\nconnection. This can require changes to the TCP length and expected\nseq / ack_seq.\n\nThe easiest way to reproduce this issue is with PASV mode.\nExample ruleset:\ntable inet ftp_nat {\n        ct helper ftp_helper {\n                type \u0026quot;ftp\u0026quot; protocol tcp\n                l3proto inet\n        }\n\n        chain prerouting {\n                type filter hook prerouting priority 0; policy accept;\n                tcp dport 21 ct state new ct helper set \u0026quot;ftp_helper\u0026quot;\n        }\n}\ntable ip nat {\n        chain prerouting {\n                type nat hook prerouting priority -100; policy accept;\n                tcp dport 21 dnat ip prefix to ip daddr map {\n\t\t\t192.168.100.1 : 192.168.13.2/32 }\n        }\n\n        chain postrouting {\n                type nat hook postrouting priority 100 ; policy accept;\n                tcp sport 21 snat ip prefix to ip saddr map {\n\t\t\t192.168.13.2 : 192.168.100.1/32 }\n        }\n}\n\nNote that the ftp helper gets assigned *after* the dnat setup.\n\nThe inverse (nat after helper assign) is handled by an existing\ncheck in nf_nat_setup_info() and will not show the problem.\n\nTopoloy:\n\n +-------------------+     +----------------------------------+\n | FTP: 192.168.13.2 | \u0026lt;-\u0026gt; | NAT: 192.168.13.3, 192.168.100.1 |\n +-------------------+     +----------------------------------+\n                                      |\n                         +-----------------------+\n                         | Client: 192.168.100.2 |\n                         +-----------------------+\n\nftp nat changes do not work as expected in this case:\nConnected to 192.168.100.1.\n[..]\nftp\u0026gt; epsv\nEPSV/EPRT on IPv4 off.\nftp\u0026gt; ls\n227 Entering passive mode (192,168,100,1,209,129).\n421 Service not available, remote server has closed connection.\n\nKernel logs:\nMissing nfct_seqadj_ext_add() setup call\nWARNING: CPU: 1 PID: 0 at net/netfilter/nf_conntrack_seqadj.c:41\n[..]\n __nf_nat_mangle_tcp_packet+0x100/0x160 [nf_nat]\n nf_nat_ftp+0x142/0x280 [nf_nat_ftp]\n help+0x4d1/0x880 [nf_conntrack_ftp]\n nf_confirm+0x122/0x2e0 [nf_conntrack]\n nf_hook_slow+0x3c/0xb0\n ..\n\nFix this by adding the required extension when a conntrack helper is assigned\nto a connection that has a nat binding.(CVE-2025-68206)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nbpf: account for current allocated stack depth in widen_imprecise_scalars()\n\nThe usage pattern for widen_imprecise_scalars() looks as follows:\n\n    prev_st = find_prev_entry(env, ...);\n    queued_st = push_stack(...);\n    widen_imprecise_scalars(env, prev_st, queued_st);\n\nWhere prev_st is an ancestor of the queued_st in the explored states\ntree. This ancestor is not guaranteed to have same allocated stack\ndepth as queued_st. E.g. in the following case:\n\n    def main():\n      for i in 1..2:\n        foo(i)        // same callsite, differnt param\n\n    def foo(i):\n      if i == 1:\n        use 128 bytes of stack\n      iterator based loop\n\nHere, for a second \u0026apos;foo\u0026apos; call prev_st-\u0026gt;allocated_stack is 128,\nwhile queued_st-\u0026gt;allocated_stack is much smaller.\nwiden_imprecise_scalars() needs to take this into account and avoid\naccessing bpf_verifier_state-\u0026gt;frame[*]-\u0026gt;stack out of bounds.(CVE-2025-68208)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnouveau/firmware: Add missing kfree() of nvkm_falcon_fw::boot\n\nnvkm_falcon_fw::boot is allocated, but no one frees it. This causes a\nkmemleak warning.\n\nMake sure this data is deallocated.(CVE-2025-68235)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nKVM: SVM: Don\u0026apos;t skip unrelated instruction if INT3/INTO is replaced\n\nWhen re-injecting a soft interrupt from an INT3, INT0, or (select) INTn\ninstruction, discard the exception and retry the instruction if the code\nstream is changed (e.g. by a different vCPU) between when the CPU\nexecutes the instruction and when KVM decodes the instruction to get the\nnext RIP.\n\nAs effectively predicted by commit 6ef88d6e36c2 (\u0026quot;KVM: SVM: Re-inject\nINT3/INTO instead of retrying the instruction\u0026quot;), failure to verify that\nthe correct INTn instruction was decoded can effectively clobber guest\nstate due to decoding the wrong instruction and thus specifying the\nwrong next RIP.\n\nThe bug most often manifests as \u0026quot;Oops: int3\u0026quot; panics on static branch\nchecks in Linux guests.  Enabling or disabling a static branch in Linux\nuses the kernel\u0026apos;s \u0026quot;text poke\u0026quot; code patching mechanism.  To modify code\nwhile other CPUs may be executing that code, Linux (temporarily)\nreplaces the first byte of the original instruction with an int3 (opcode\n0xcc), then patches in the new code stream except for the first byte,\nand finally replaces the int3 with the first byte of the new code\nstream.  If a CPU hits the int3, i.e. executes the code while it\u0026apos;s being\nmodified, then the guest kernel must look up the RIP to determine how to\nhandle the #BP, e.g. by emulating the new instruction.  If the RIP is\nincorrect, then this lookup fails and the guest kernel panics.\n\nThe bug reproduces almost instantly by hacking the guest kernel to\nrepeatedly check a static branch[1] while running a drgn script[2] on\nthe host to constantly swap out the memory containing the guest\u0026apos;s TSS.\n\n[1]: https://gist.github.com/osandov/44d17c51c28c0ac998ea0334edf90b5a\n[2]: https://gist.github.com/osandov/10e45e45afa29b11e0c7209247afc00b(CVE-2025-68259)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\next4: add i_data_sem protection in ext4_destroy_inline_data_nolock()\n\nFix a race between inline data destruction and block mapping.\n\nThe function ext4_destroy_inline_data_nolock() changes the inode data\nlayout by clearing EXT4_INODE_INLINE_DATA and setting EXT4_INODE_EXTENTS.\nAt the same time, another thread may execute ext4_map_blocks(), which\ntests EXT4_INODE_EXTENTS to decide whether to call ext4_ext_map_blocks()\nor ext4_ind_map_blocks().\n\nWithout i_data_sem protection, ext4_ind_map_blocks() may receive inode\nwith EXT4_INODE_EXTENTS flag and triggering assert.\n\nkernel BUG at fs/ext4/indirect.c:546!\nEXT4-fs (loop2): unmounting filesystem.\ninvalid opcode: 0000 [#1] PREEMPT SMP KASAN NOPTI\nHardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.12.0-1 04/01/2014\nRIP: 0010:ext4_ind_map_blocks.cold+0x2b/0x5a fs/ext4/indirect.c:546\n\nCall Trace:\n \u0026lt;TASK\u0026gt;\n ext4_map_blocks+0xb9b/0x16f0 fs/ext4/inode.c:681\n _ext4_get_block+0x242/0x590 fs/ext4/inode.c:822\n ext4_block_write_begin+0x48b/0x12c0 fs/ext4/inode.c:1124\n ext4_write_begin+0x598/0xef0 fs/ext4/inode.c:1255\n ext4_da_write_begin+0x21e/0x9c0 fs/ext4/inode.c:3000\n generic_perform_write+0x259/0x5d0 mm/filemap.c:3846\n ext4_buffered_write_iter+0x15b/0x470 fs/ext4/file.c:285\n ext4_file_write_iter+0x8e0/0x17f0 fs/ext4/file.c:679\n call_write_iter include/linux/fs.h:2271 [inline]\n do_iter_readv_writev+0x212/0x3c0 fs/read_write.c:735\n do_iter_write+0x186/0x710 fs/read_write.c:861\n vfs_iter_write+0x70/0xa0 fs/read_write.c:902\n iter_file_splice_write+0x73b/0xc90 fs/splice.c:685\n do_splice_from fs/splice.c:763 [inline]\n direct_splice_actor+0x10f/0x170 fs/splice.c:950\n splice_direct_to_actor+0x33a/0xa10 fs/splice.c:896\n do_splice_direct+0x1a9/0x280 fs/splice.c:1002\n do_sendfile+0xb13/0x12c0 fs/read_write.c:1255\n __do_sys_sendfile64 fs/read_write.c:1323 [inline]\n __se_sys_sendfile64 fs/read_write.c:1309 [inline]\n __x64_sys_sendfile64+0x1cf/0x210 fs/read_write.c:1309\n do_syscall_x64 arch/x86/entry/common.c:51 [inline]\n do_syscall_64+0x35/0x80 arch/x86/entry/common.c:81\n entry_SYSCALL_64_after_hwframe+0x6e/0xd8(CVE-2025-68261)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\next4: refresh inline data size before write operations\n\nThe cached ei-\u0026gt;i_inline_size can become stale between the initial size\ncheck and when ext4_update_inline_data()/ext4_create_inline_data() use\nit. Although ext4_get_max_inline_size() reads the correct value at the\ntime of the check, concurrent xattr operations can modify i_inline_size\nbefore ext4_write_lock_xattr() is acquired.\n\nThis causes ext4_update_inline_data() and ext4_create_inline_data() to\nwork with stale capacity values, leading to a BUG_ON() crash in\next4_write_inline_data():\n\n  kernel BUG at fs/ext4/inline.c:1331!\n  BUG_ON(pos + len \u0026gt; EXT4_I(inode)-\u0026gt;i_inline_size);\n\nThe race window:\n1. ext4_get_max_inline_size() reads i_inline_size = 60 (correct)\n2. Size check passes for 50-byte write\n3. [Another thread adds xattr, i_inline_size changes to 40]\n4. ext4_write_lock_xattr() acquires lock\n5. ext4_update_inline_data() uses stale i_inline_size = 60\n6. Attempts to write 50 bytes but only 40 bytes actually available\n7. BUG_ON() triggers\n\nFix this by recalculating i_inline_size via ext4_find_inline_data_nolock()\nimmediately after acquiring xattr_sem. This ensures ext4_update_inline_data()\nand ext4_create_inline_data() work with current values that are protected\nfrom concurrent modifications.\n\nThis is similar to commit a54c4613dac1 (\u0026quot;ext4: fix race writing to an\ninline_data file while its xattrs are changing\u0026quot;) which fixed i_inline_off\nstaleness. This patch addresses the related i_inline_size staleness issue.(CVE-2025-68264)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnvme: fix admin request_queue lifetime\n\nThe namespaces can access the controller\u0026apos;s admin request_queue, and\nstale references on the namespaces may exist after tearing down the\ncontroller. Ensure the admin request_queue is active by moving the\ncontroller\u0026apos;s \u0026apos;put\u0026apos; to after all controller references have been released\nto ensure no one is can access the request_queue. This fixes a reported\nuse-after-free bug:\n\n  BUG: KASAN: slab-use-after-free in blk_queue_enter+0x41c/0x4a0\n  Read of size 8 at addr ffff88c0a53819f8 by task nvme/3287\n  CPU: 67 UID: 0 PID: 3287 Comm: nvme Tainted: G            E       6.13.2-ga1582f1a031e #15\n  Tainted: [E]=UNSIGNED_MODULE\n  Hardware name: Jabil /EGS 2S MB1, BIOS 1.00 06/18/2025\n  Call Trace:\n   \u0026lt;TASK\u0026gt;\n   dump_stack_lvl+0x4f/0x60\n   print_report+0xc4/0x620\n   ? _raw_spin_lock_irqsave+0x70/0xb0\n   ? _raw_read_unlock_irqrestore+0x30/0x30\n   ? blk_queue_enter+0x41c/0x4a0\n   kasan_report+0xab/0xe0\n   ? blk_queue_enter+0x41c/0x4a0\n   blk_queue_enter+0x41c/0x4a0\n   ? __irq_work_queue_local+0x75/0x1d0\n   ? blk_queue_start_drain+0x70/0x70\n   ? irq_work_queue+0x18/0x20\n   ? vprintk_emit.part.0+0x1cc/0x350\n   ? wake_up_klogd_work_func+0x60/0x60\n   blk_mq_alloc_request+0x2b7/0x6b0\n   ? __blk_mq_alloc_requests+0x1060/0x1060\n   ? __switch_to+0x5b7/0x1060\n   nvme_submit_user_cmd+0xa9/0x330\n   nvme_user_cmd.isra.0+0x240/0x3f0\n   ? force_sigsegv+0xe0/0xe0\n   ? nvme_user_cmd64+0x400/0x400\n   ? vfs_fileattr_set+0x9b0/0x9b0\n   ? cgroup_update_frozen_flag+0x24/0x1c0\n   ? cgroup_leave_frozen+0x204/0x330\n   ? nvme_ioctl+0x7c/0x2c0\n   blkdev_ioctl+0x1a8/0x4d0\n   ? blkdev_common_ioctl+0x1930/0x1930\n   ? fdget+0x54/0x380\n   __x64_sys_ioctl+0x129/0x190\n   do_syscall_64+0x5b/0x160\n   entry_SYSCALL_64_after_hwframe+0x4b/0x53\n  RIP: 0033:0x7f765f703b0b\n  Code: ff ff ff 85 c0 79 9b 49 c7 c4 ff ff ff ff 5b 5d 4c 89 e0 41 5c c3 66 0f 1f 84 00 00 00 00 00 f3 0f 1e fa b8 10 00 00 00 0f 05 \u0026lt;48\u0026gt; 3d 01 f0 ff ff 73 01 c3 48 8b 0d dd 52 0f 00 f7 d8 64 89 01 48\n  RSP: 002b:00007ffe2cefe808 EFLAGS: 00000202 ORIG_RAX: 0000000000000010\n  RAX: ffffffffffffffda RBX: 00007ffe2cefe860 RCX: 00007f765f703b0b\n  RDX: 00007ffe2cefe860 RSI: 00000000c0484e41 RDI: 0000000000000003\n  RBP: 0000000000000000 R08: 0000000000000003 R09: 0000000000000000\n  R10: 00007f765f611d50 R11: 0000000000000202 R12: 0000000000000003\n  R13: 00000000c0484e41 R14: 0000000000000001 R15: 00007ffe2cefea60\n   \u0026lt;/TASK\u0026gt;(CVE-2025-68265)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nceph: fix crash in process_v2_sparse_read() for encrypted directories\n\nThe crash in process_v2_sparse_read() for fscrypt-encrypted directories\nhas been reported. Issue takes place for Ceph msgr2 protocol in secure\nmode. It can be reproduced by the steps:\n\nsudo mount -t ceph :/ /mnt/cephfs/ -o name=admin,fs=cephfs,ms_mode=secure\n\n(1) mkdir /mnt/cephfs/fscrypt-test-3\n(2) cp area_decrypted.tar /mnt/cephfs/fscrypt-test-3\n(3) fscrypt encrypt --source=raw_key --key=./my.key /mnt/cephfs/fscrypt-test-3\n(4) fscrypt lock /mnt/cephfs/fscrypt-test-3\n(5) fscrypt unlock --key=my.key /mnt/cephfs/fscrypt-test-3\n(6) cat /mnt/cephfs/fscrypt-test-3/area_decrypted.tar\n(7) Issue has been triggered\n\n[  408.072247] ------------[ cut here ]------------\n[  408.072251] WARNING: CPU: 1 PID: 392 at net/ceph/messenger_v2.c:865\nceph_con_v2_try_read+0x4b39/0x72f0\n[  408.072267] Modules linked in: intel_rapl_msr intel_rapl_common\nintel_uncore_frequency_common intel_pmc_core pmt_telemetry pmt_discovery\npmt_class intel_pmc_ssram_telemetry intel_vsec kvm_intel joydev kvm irqbypass\npolyval_clmulni ghash_clmulni_intel aesni_intel rapl input_leds psmouse\nserio_raw i2c_piix4 vga16fb bochs vgastate i2c_smbus floppy mac_hid qemu_fw_cfg\npata_acpi sch_fq_codel rbd msr parport_pc ppdev lp parport efi_pstore\n[  408.072304] CPU: 1 UID: 0 PID: 392 Comm: kworker/1:3 Not tainted 6.17.0-rc7+\n[  408.072307] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS\n1.17.0-5.fc42 04/01/2014\n[  408.072310] Workqueue: ceph-msgr ceph_con_workfn\n[  408.072314] RIP: 0010:ceph_con_v2_try_read+0x4b39/0x72f0\n[  408.072317] Code: c7 c1 20 f0 d4 ae 50 31 d2 48 c7 c6 60 27 d5 ae 48 c7 c7 f8\n8e 6f b0 68 60 38 d5 ae e8 00 47 61 fe 48 83 c4 18 e9 ac fc ff ff \u0026lt;0f\u0026gt; 0b e9 06\nfe ff ff 4c 8b 9d 98 fd ff ff 0f 84 64 e7 ff ff 89 85\n[  408.072319] RSP: 0018:ffff88811c3e7a30 EFLAGS: 00010246\n[  408.072322] RAX: ffffed1024874c6f RBX: ffffea00042c2b40 RCX: 0000000000000f38\n[  408.072324] RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000000000000\n[  408.072325] RBP: ffff88811c3e7ca8 R08: 0000000000000000 R09: 00000000000000c8\n[  408.072326] R10: 00000000000000c8 R11: 0000000000000000 R12: 00000000000000c8\n[  408.072327] R13: dffffc0000000000 R14: ffff8881243a6030 R15: 0000000000003000\n[  408.072329] FS:  0000000000000000(0000) GS:ffff88823eadf000(0000)\nknlGS:0000000000000000\n[  408.072331] CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033\n[  408.072332] CR2: 000000c0003c6000 CR3: 000000010c106005 CR4: 0000000000772ef0\n[  408.072336] PKRU: 55555554\n[  408.072337] Call Trace:\n[  408.072338]  \u0026lt;TASK\u0026gt;\n[  408.072340]  ? sched_clock_noinstr+0x9/0x10\n[  408.072344]  ? __pfx_ceph_con_v2_try_read+0x10/0x10\n[  408.072347]  ? _raw_spin_unlock+0xe/0x40\n[  408.072349]  ? finish_task_switch.isra.0+0x15d/0x830\n[  408.072353]  ? __kasan_check_write+0x14/0x30\n[  408.072357]  ? mutex_lock+0x84/0xe0\n[  408.072359]  ? __pfx_mutex_lock+0x10/0x10\n[  408.072361]  ceph_con_workfn+0x27e/0x10e0\n[  408.072364]  ? metric_delayed_work+0x311/0x2c50\n[  408.072367]  process_one_work+0x611/0xe20\n[  408.072371]  ? __kasan_check_write+0x14/0x30\n[  408.072373]  worker_thread+0x7e3/0x1580\n[  408.072375]  ? __pfx__raw_spin_lock_irqsave+0x10/0x10\n[  408.072378]  ? __pfx_worker_thread+0x10/0x10\n[  408.072381]  kthread+0x381/0x7a0\n[  408.072383]  ? __pfx__raw_spin_lock_irq+0x10/0x10\n[  408.072385]  ? __pfx_kthread+0x10/0x10\n[  408.072387]  ? __kasan_check_write+0x14/0x30\n[  408.072389]  ? recalc_sigpending+0x160/0x220\n[  408.072392]  ? _raw_spin_unlock_irq+0xe/0x50\n[  408.072394]  ? calculate_sigpending+0x78/0xb0\n[  408.072395]  ? __pfx_kthread+0x10/0x10\n[  408.072397]  ret_from_fork+0x2b6/0x380\n[  408.072400]  ? __pfx_kthread+0x10/0x10\n[  408.072402]  ret_from_fork_asm+0x1a/0x30\n[  408.072406]  \u0026lt;/TASK\u0026gt;\n[  408.072407] ---[ end trace 0000000000000000 ]---\n[  408.072418] Oops: general protection fault, probably for non-canonical\naddress 0xdffffc00000000\n---truncated---(CVE-2025-68297)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnet: atlantic: fix fragment overflow handling in RX path\n\nThe atlantic driver can receive packets with more than MAX_SKB_FRAGS (17)\nfragments when handling large multi-descriptor packets. This causes an\nout-of-bounds write in skb_add_rx_frag_netmem() leading to kernel panic.\n\nThe issue occurs because the driver doesn\u0026apos;t check the total number of\nfragments before calling skb_add_rx_frag(). When a packet requires more\nthan MAX_SKB_FRAGS fragments, the fragment index exceeds the array bounds.\n\nFix by assuming there will be an extra frag if buff-\u0026gt;len \u0026gt; AQ_CFG_RX_HDR_SIZE,\nthen all fragments are accounted for. And reusing the existing check to\nprevent the overflow earlier in the code path.\n\nThis crash occurred in production with an Aquantia AQC113 10G NIC.\n\nStack trace from production environment:\n```\nRIP: 0010:skb_add_rx_frag_netmem+0x29/0xd0\nCode: 90 f3 0f 1e fa 0f 1f 44 00 00 48 89 f8 41 89\nca 48 89 d7 48 63 ce 8b 90 c0 00 00 00 48 c1 e1 04 48 01 ca 48 03 90\nc8 00 00 00 \u0026lt;48\u0026gt; 89 7a 30 44 89 52 3c 44 89 42 38 40 f6 c7 01 75 74 48\n89 fa 83\nRSP: 0018:ffffa9bec02a8d50 EFLAGS: 00010287\nRAX: ffff925b22e80a00 RBX: ffff925ad38d2700 RCX:\nfffffffe0a0c8000\nRDX: ffff9258ea95bac0 RSI: ffff925ae0a0c800 RDI:\n0000000000037a40\nRBP: 0000000000000024 R08: 0000000000000000 R09:\n0000000000000021\nR10: 0000000000000848 R11: 0000000000000000 R12:\nffffa9bec02a8e24\nR13: ffff925ad8615570 R14: 0000000000000000 R15:\nffff925b22e80a00\nFS: 0000000000000000(0000)\nGS:ffff925e47880000(0000) knlGS:0000000000000000\nCS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033\nCR2: ffff9258ea95baf0 CR3: 0000000166022004 CR4:\n0000000000f72ef0\nPKRU: 55555554\nCall Trace:\n\u0026lt;IRQ\u0026gt;\naq_ring_rx_clean+0x175/0xe60 [atlantic]\n? aq_ring_rx_clean+0x14d/0xe60 [atlantic]\n? aq_ring_tx_clean+0xdf/0x190 [atlantic]\n? kmem_cache_free+0x348/0x450\n? aq_vec_poll+0x81/0x1d0 [atlantic]\n? __napi_poll+0x28/0x1c0\n? net_rx_action+0x337/0x420\n```\n\nChanges in v4:\n- Add Fixes: tag to satisfy patch validation requirements.\n\nChanges in v3:\n- Fix by assuming there will be an extra frag if buff-\u0026gt;len \u0026gt; AQ_CFG_RX_HDR_SIZE,\n  then all fragments are accounted for.(CVE-2025-68301)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nPCI/AER: Fix NULL pointer access by aer_info\n\nThe kzalloc(GFP_KERNEL) may return NULL, so all accesses to aer_info-\u0026gt;xxx\nwill result in kernel panic. Fix it.(CVE-2025-68309)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nusb: uas: fix urb unmapping issue when the uas device is remove during ongoing data transfer\n\nWhen a UAS device is unplugged during data transfer, there is\na probability of a system panic occurring. The root cause is\nan access to an invalid memory address during URB callback handling.\nSpecifically, this happens when the dma_direct_unmap_sg() function\nis called within the usb_hcd_unmap_urb_for_dma() interface, but the\nsg-\u0026gt;dma_address field is 0 and the sg data structure has already been\nfreed.\n\nThe SCSI driver sends transfer commands by invoking uas_queuecommand_lck()\nin uas.c, using the uas_submit_urbs() function to submit requests to USB.\nWithin the uas_submit_urbs() implementation, three URBs (sense_urb,\ndata_urb, and cmd_urb) are sequentially submitted. Device removal may\noccur at any point during uas_submit_urbs execution, which may result\nin URB submission failure. However, some URBs might have been successfully\nsubmitted before the failure, and uas_submit_urbs will return the -ENODEV\nerror code in this case. The current error handling directly calls\nscsi_done(). In the SCSI driver, this eventually triggers scsi_complete()\nto invoke scsi_end_request() for releasing the sgtable. The successfully\nsubmitted URBs, when being unlinked to giveback, call\nusb_hcd_unmap_urb_for_dma() in hcd.c, leading to exceptions during sg\nunmapping operations since the sg data structure has already been freed.\n\nThis patch modifies the error condition check in the uas_submit_urbs()\nfunction. When a UAS device is removed but one or more URBs have already\nbeen successfully submitted to USB, it avoids immediately invoking\nscsi_done() and save the cmnd to devinfo-\u0026gt;cmnd array. If the successfully\nsubmitted URBs is completed before devinfo-\u0026gt;resetting being set, then\nthe scsi_done() function will be called within uas_try_complete() after\nall pending URB operations are finalized. Otherwise, the scsi_done()\nfunction will be called within uas_zap_pending(), which is executed after\nusb_kill_anchored_urbs().\n\nThe error handling only takes effect when uas_queuecommand_lck() calls\nuas_submit_urbs() and returns the error value -ENODEV . In this case,\nthe device is disconnected, and the flow proceeds to uas_disconnect(),\nwhere uas_zap_pending() is invoked to call uas_try_complete().(CVE-2025-68331)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\njbd2: avoid bug_on in jbd2_journal_get_create_access() when file system corrupted\n\nThere\u0026apos;s issue when file system corrupted:\n------------[ cut here ]------------\nkernel BUG at fs/jbd2/transaction.c:1289!\nOops: invalid opcode: 0000 [#1] SMP KASAN PTI\nCPU: 5 UID: 0 PID: 2031 Comm: mkdir Not tainted 6.18.0-rc1-next\nRIP: 0010:jbd2_journal_get_create_access+0x3b6/0x4d0\nRSP: 0018:ffff888117aafa30 EFLAGS: 00010202\nRAX: 0000000000000000 RBX: ffff88811a86b000 RCX: ffffffff89a63534\nRDX: 1ffff110200ec602 RSI: 0000000000000004 RDI: ffff888100763010\nRBP: ffff888100763000 R08: 0000000000000001 R09: ffff888100763028\nR10: 0000000000000003 R11: 0000000000000000 R12: 0000000000000000\nR13: ffff88812c432000 R14: ffff88812c608000 R15: ffff888120bfc000\nCS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033\nCR2: 00007f91d6970c99 CR3: 00000001159c4000 CR4: 00000000000006f0\nCall Trace:\n \u0026lt;TASK\u0026gt;\n __ext4_journal_get_create_access+0x42/0x170\n ext4_getblk+0x319/0x6f0\n ext4_bread+0x11/0x100\n ext4_append+0x1e6/0x4a0\n ext4_init_new_dir+0x145/0x1d0\n ext4_mkdir+0x326/0x920\n vfs_mkdir+0x45c/0x740\n do_mkdirat+0x234/0x2f0\n __x64_sys_mkdir+0xd6/0x120\n do_syscall_64+0x5f/0xfa0\n entry_SYSCALL_64_after_hwframe+0x76/0x7e\n\nThe above issue occurs with us in errors=continue mode when accompanied by\nstorage failures. There have been many inconsistencies in the file system\ndata.\nIn the case of file system data inconsistency, for example, if the block\nbitmap of a referenced block is not set, it can lead to the situation where\na block being committed is allocated and used again. As a result, the\nfollowing condition will not be satisfied then trigger BUG_ON. Of course,\nit is entirely possible to construct a problematic image that can trigger\nthis BUG_ON through specific operations. In fact, I have constructed such\nan image and easily reproduced this issue.\nTherefore, J_ASSERT() holds true only under ideal conditions, but it may\nnot necessarily be satisfied in exceptional scenarios. Using J_ASSERT()\ndirectly in abnormal situations would cause the system to crash, which is\nclearly not what we want. So here we directly trigger a JBD abort instead\nof immediately invoking BUG_ON.(CVE-2025-68337)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nNFSv4/pNFS: Clear NFS_INO_LAYOUTCOMMIT in pnfs_mark_layout_stateid_invalid\n\nFixes a crash when layout is null during this call stack:\n\nwrite_inode\n    -\u0026gt; nfs4_write_inode\n        -\u0026gt; pnfs_layoutcommit_inode\n\npnfs_set_layoutcommit relies on the lseg refcount to keep the layout\naround. Need to clear NFS_INO_LAYOUTCOMMIT otherwise we might attempt\nto reference a null layout.(CVE-2025-68349)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nregulator: core: Protect regulator_supply_alias_list with regulator_list_mutex\n\nregulator_supply_alias_list was accessed without any locking in\nregulator_supply_alias(), regulator_register_supply_alias(), and\nregulator_unregister_supply_alias(). Concurrent registration,\nunregistration and lookups can race, leading to:\n\n1 use-after-free if an alias entry is removed while being read,\n2 duplicate entries when two threads register the same alias,\n3 inconsistent alias mappings observed by consumers.\n\nProtect all traversals, insertions and deletions on\nregulator_supply_alias_list with the existing regulator_list_mutex.(CVE-2025-68354)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ngfs2: Prevent recursive memory reclaim\n\nFunction new_inode() returns a new inode with inode-\u0026gt;i_mapping-\u0026gt;gfp_mask\nset to GFP_HIGHUSER_MOVABLE.  This value includes the __GFP_FS flag, so\nallocations in that address space can recurse into filesystem memory\nreclaim.  We don\u0026apos;t want that to happen because it can consume a\nsignificant amount of stack memory.\n\nWorse than that is that it can also deadlock: for example, in several\nplaces, gfs2_unstuff_dinode() is called inside filesystem transactions.\nThis calls filemap_grab_folio(), which can allocate a new folio, which\ncan trigger memory reclaim.  If memory reclaim recurses into the\nfilesystem and starts another transaction, a deadlock will ensue.\n\nTo fix these kinds of problems, prevent memory reclaim from recursing\ninto filesystem code by making sure that the gfp_mask of inode address\nspaces doesn\u0026apos;t include __GFP_FS.\n\nThe \u0026quot;meta\u0026quot; and resource group address spaces were already using GFP_NOFS\nas their gfp_mask (which doesn\u0026apos;t include __GFP_FS).  The default value\nof GFP_HIGHUSER_MOVABLE is less restrictive than GFP_NOFS, though.  To\navoid being overly limiting, use the default value and only knock off\nthe __GFP_FS flag.  I\u0026apos;m not sure if this will actually make a\ndifference, but it also shouldn\u0026apos;t hurt.\n\nThis patch is loosely based on commit ad22c7a043c2 (\u0026quot;xfs: prevent stack\noverflows from page cache allocation\u0026quot;).\n\nFixes xfstest generic/273.(CVE-2025-68356)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nwifi: rtl818x: rtl8187: Fix potential buffer underflow in rtl8187_rx_cb()\n\nThe rtl8187_rx_cb() calculates the rx descriptor header address\nby subtracting its size from the skb tail pointer.\nHowever, it does not validate if the received packet\n(skb-\u0026gt;len from urb-\u0026gt;actual_length) is large enough to contain this\nheader.\n\nIf a truncated packet is received, this will lead to a buffer\nunderflow, reading memory before the start of the skb data area,\nand causing a kernel panic.\n\nAdd length checks for both rtl8187 and rtl8187b descriptor headers\nbefore attempting to access them, dropping the packet cleanly if the\ncheck fails.(CVE-2025-68362)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nbpf: Check skb-\u0026gt;transport_header is set in bpf_skb_check_mtu\n\nThe bpf_skb_check_mtu helper needs to use skb-\u0026gt;transport_header when\nthe BPF_MTU_CHK_SEGS flag is used:\n\n\tbpf_skb_check_mtu(skb, ifindex, \u0026amp;mtu_len, 0, BPF_MTU_CHK_SEGS)\n\nThe transport_header is not always set. There is a WARN_ON_ONCE\nreport when CONFIG_DEBUG_NET is enabled + skb-\u0026gt;gso_size is set +\nbpf_prog_test_run is used:\n\nWARNING: CPU: 1 PID: 2216 at ./include/linux/skbuff.h:3071\n skb_gso_validate_network_len\n bpf_skb_check_mtu\n bpf_prog_3920e25740a41171_tc_chk_segs_flag # A test in the next patch\n bpf_test_run\n bpf_prog_test_run_skb\n\nFor a normal ingress skb (not test_run), skb_reset_transport_header\nis performed but there is plan to avoid setting it as described in\ncommit 2170a1f09148 (\u0026quot;net: no longer reset transport_header in __netif_receive_skb_core()\u0026quot;).\n\nThis patch fixes the bpf helper by checking\nskb_transport_header_was_set(). The check is done just before\nskb-\u0026gt;transport_header is used, to avoid breaking the existing bpf prog.\nThe WARN_ON_ONCE is limited to bpf_prog_test_run, so targeting bpf-next.(CVE-2025-68363)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ncoresight: ETR: Fix ETR buffer use-after-free issue\n\nWhen ETR is enabled as CS_MODE_SYSFS, if the buffer size is changed\nand enabled again, currently sysfs_buf will point to the newly\nallocated memory(buf_new) and free the old memory(buf_old). But the\netr_buf that is being used by the ETR remains pointed to buf_old, not\nupdated to buf_new. In this case, it will result in a memory\nuse-after-free issue.\n\nFix this by checking ETR\u0026apos;s mode before updating and releasing buf_old,\nif the mode is CS_MODE_SYSFS, then skip updating and releasing it.(CVE-2025-68376)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nbpf: Fix stackmap overflow check in __bpf_get_stackid()\n\nSyzkaller reported a KASAN slab-out-of-bounds write in __bpf_get_stackid()\nwhen copying stack trace data. The issue occurs when the perf trace\n contains more stack entries than the stack map bucket can hold,\n leading to an out-of-bounds write in the bucket\u0026apos;s data array.(CVE-2025-68378)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ncrypto: asymmetric_keys - prevent overflow in asymmetric_key_generate_id\n\nUse check_add_overflow() to guard against potential integer overflows\nwhen adding the binary blob lengths and the size of an asymmetric_key_id\nstructure and return ERR_PTR(-EOVERFLOW) accordingly. This prevents a\npossible buffer overflow when copying data from potentially malicious\nX.509 certificate fields that can be arbitrarily large, such as ASN.1\nINTEGER serial numbers, issuer names, etc.(CVE-2025-68724)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nbpf: Do not let BPF test infra emit invalid GSO types to stack\n\nYinhao et al. reported that their fuzzer tool was able to trigger a\nskb_warn_bad_offload() from netif_skb_features() -\u0026gt; gso_features_check().\nWhen a BPF program - triggered via BPF test infra - pushes the packet\nto the loopback device via bpf_clone_redirect() then mentioned offload\nwarning can be seen. GSO-related features are then rightfully disabled.\n\nWe get into this situation due to convert___skb_to_skb() setting\ngso_segs and gso_size but not gso_type. Technically, it makes sense\nthat this warning triggers since the GSO properties are malformed due\nto the gso_type. Potentially, the gso_type could be marked non-trustworthy\nthrough setting it at least to SKB_GSO_DODGY without any other specific\nassumptions, but that also feels wrong given we should not go further\ninto the GSO engine in the first place.\n\nThe checks were added in 121d57af308d (\u0026quot;gso: validate gso_type in GSO\nhandlers\u0026quot;) because there were malicious (syzbot) senders that combine\na protocol with a non-matching gso_type. If we would want to drop such\npackets, gso_features_check() currently only returns feature flags via\nnetif_skb_features(), so one location for potentially dropping such skbs\ncould be validate_xmit_unreadable_skb(), but then otoh it would be\nan additional check in the fast-path for a very corner case. Given\nbpf_clone_redirect() is the only place where BPF test infra could emit\nsuch packets, lets reject them right there.(CVE-2025-68725)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nisdn: mISDN: hfcsusb: fix memory leak in hfcsusb_probe()\n\nIn hfcsusb_probe(), the memory allocated for ctrl_urb gets leaked when\nsetup_instance() fails with an error code. Fix that by freeing the urb\nbefore freeing the hw structure. Also change the error paths to use the\ngoto ladder style.\n\nCompile tested only. Issue found using a prototype static analysis tool.(CVE-2025-68734)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nscsi: qla2xxx: Fix improper freeing of purex item\n\nIn qla2xxx_process_purls_iocb(), an item is allocated via\nqla27xx_copy_multiple_pkt(), which internally calls\nqla24xx_alloc_purex_item().\n\nThe qla24xx_alloc_purex_item() function may return a pre-allocated item\nfrom a per-adapter pool for small allocations, instead of dynamically\nallocating memory with kzalloc().\n\nAn error handling path in qla2xxx_process_purls_iocb() incorrectly uses\nkfree() to release the item. If the item was from the pre-allocated\npool, calling kfree() on it is a bug that can lead to memory corruption.\n\nFix this by using the correct deallocation function,\nqla24xx_free_purex_item(), which properly handles both dynamically\nallocated and pre-allocated items.(CVE-2025-68741)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nbpf: Free special fields when update [lru_,]percpu_hash maps\n\nAs [lru_,]percpu_hash maps support BPF_KPTR_{REF,PERCPU}, missing\ncalls to \u0026apos;bpf_obj_free_fields()\u0026apos; in \u0026apos;pcpu_copy_value()\u0026apos; could cause the\nmemory referenced by BPF_KPTR_{REF,PERCPU} fields to be held until the\nmap gets freed.\n\nFix this by calling \u0026apos;bpf_obj_free_fields()\u0026apos; after\n\u0026apos;copy_map_value[,_long]()\u0026apos; in \u0026apos;pcpu_copy_value()\u0026apos;.(CVE-2025-68744)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nscsi: qla2xxx: Clear cmds after chip reset\n\nCommit aefed3e5548f (\u0026quot;scsi: qla2xxx: target: Fix offline port handling\nand host reset handling\u0026quot;) caused two problems:\n\n1. Commands sent to FW, after chip reset got stuck and never freed as FW\n   is not going to respond to them anymore.\n\n2. BUG_ON(cmd-\u0026gt;sg_mapped) in qlt_free_cmd().  Commit 26f9ce53817a\n   (\u0026quot;scsi: qla2xxx: Fix missed DMA unmap for aborted commands\u0026quot;)\n   attempted to fix this, but introduced another bug under different\n   circumstances when two different CPUs were racing to call\n   qlt_unmap_sg() at the same time: BUG_ON(!valid_dma_direction(dir)) in\n   dma_unmap_sg_attrs().\n\nSo revert \u0026quot;scsi: qla2xxx: Fix missed DMA unmap for aborted commands\u0026quot; and\npartially revert \u0026quot;scsi: qla2xxx: target: Fix offline port handling and\nhost reset handling\u0026quot; at __qla2x00_abort_all_cmds.(CVE-2025-68745)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nblock: Use RCU in blk_mq_[un]quiesce_tagset() instead of set-\u0026gt;tag_list_lock\n\nblk_mq_{add,del}_queue_tag_set() functions add and remove queues from\ntagset, the functions make sure that tagset and queues are marked as\nshared when two or more queues are attached to the same tagset.\nInitially a tagset starts as unshared and when the number of added\nqueues reaches two, blk_mq_add_queue_tag_set() marks it as shared along\nwith all the queues attached to it. When the number of attached queues\ndrops to 1 blk_mq_del_queue_tag_set() need to mark both the tagset and\nthe remaining queues as unshared.\n\nBoth functions need to freeze current queues in tagset before setting on\nunsetting BLK_MQ_F_TAG_QUEUE_SHARED flag. While doing so, both functions\nhold set-\u0026gt;tag_list_lock mutex, which makes sense as we do not want\nqueues to be added or deleted in the process. This used to work fine\nuntil commit 98d81f0df70c (\u0026quot;nvme: use blk_mq_[un]quiesce_tagset\u0026quot;)\nmade the nvme driver quiesce tagset instead of quiscing individual\nqueues. blk_mq_quiesce_tagset() does the job and quiesce the queues in\nset-\u0026gt;tag_list while holding set-\u0026gt;tag_list_lock also.\n\nThis results in deadlock between two threads with these stacktraces:\n\n  __schedule+0x47c/0xbb0\n  ? timerqueue_add+0x66/0xb0\n  schedule+0x1c/0xa0\n  schedule_preempt_disabled+0xa/0x10\n  __mutex_lock.constprop.0+0x271/0x600\n  blk_mq_quiesce_tagset+0x25/0xc0\n  nvme_dev_disable+0x9c/0x250\n  nvme_timeout+0x1fc/0x520\n  blk_mq_handle_expired+0x5c/0x90\n  bt_iter+0x7e/0x90\n  blk_mq_queue_tag_busy_iter+0x27e/0x550\n  ? __blk_mq_complete_request_remote+0x10/0x10\n  ? __blk_mq_complete_request_remote+0x10/0x10\n  ? __call_rcu_common.constprop.0+0x1c0/0x210\n  blk_mq_timeout_work+0x12d/0x170\n  process_one_work+0x12e/0x2d0\n  worker_thread+0x288/0x3a0\n  ? rescuer_thread+0x480/0x480\n  kthread+0xb8/0xe0\n  ? kthread_park+0x80/0x80\n  ret_from_fork+0x2d/0x50\n  ? kthread_park+0x80/0x80\n  ret_from_fork_asm+0x11/0x20\n\n  __schedule+0x47c/0xbb0\n  ? xas_find+0x161/0x1a0\n  schedule+0x1c/0xa0\n  blk_mq_freeze_queue_wait+0x3d/0x70\n  ? destroy_sched_domains_rcu+0x30/0x30\n  blk_mq_update_tag_set_shared+0x44/0x80\n  blk_mq_exit_queue+0x141/0x150\n  del_gendisk+0x25a/0x2d0\n  nvme_ns_remove+0xc9/0x170\n  nvme_remove_namespaces+0xc7/0x100\n  nvme_remove+0x62/0x150\n  pci_device_remove+0x23/0x60\n  device_release_driver_internal+0x159/0x200\n  unbind_store+0x99/0xa0\n  kernfs_fop_write_iter+0x112/0x1e0\n  vfs_write+0x2b1/0x3d0\n  ksys_write+0x4e/0xb0\n  do_syscall_64+0x5b/0x160\n  entry_SYSCALL_64_after_hwframe+0x4b/0x53\n\nThe top stacktrace is showing nvme_timeout() called to handle nvme\ncommand timeout. timeout handler is trying to disable the controller and\nas a first step, it needs to blk_mq_quiesce_tagset() to tell blk-mq not\nto call queue callback handlers. The thread is stuck waiting for\nset-\u0026gt;tag_list_lock as it tries to walk the queues in set-\u0026gt;tag_list.\n\nThe lock is held by the second thread in the bottom stack which is\nwaiting for one of queues to be frozen. The queue usage counter will\ndrop to zero after nvme_timeout() finishes, and this will not happen\nbecause the thread will wait for this mutex forever.\n\nGiven that [un]quiescing queue is an operation that does not need to\nsleep, update blk_mq_[un]quiesce_tagset() to use RCU instead of taking\nset-\u0026gt;tag_list_lock, update blk_mq_{add,del}_queue_tag_set() to use RCU\nsafe list operations. Also, delete INIT_LIST_HEAD(\u0026amp;q-\u0026gt;tag_set_list)\nin blk_mq_del_queue_tag_set() because we can not re-initialize it while\nthe list is being traversed under RCU. The deleted queue will not be\nadded/deleted to/from a tagset and it will be freed in blk_free_queue()\nafter the end of RCU grace period.(CVE-2025-68756)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nsched/deadline: only set free_cpus for online runqueues\n\nCommit 16b269436b72 (\u0026quot;sched/deadline: Modify cpudl::free_cpus\nto reflect rd-\u0026gt;online\u0026quot;) introduced the cpudl_set/clear_freecpu\nfunctions to allow the cpu_dl::free_cpus mask to be manipulated\nby the deadline scheduler class rq_on/offline callbacks so the\nmask would also reflect this state.\n\nCommit 9659e1eeee28 (\u0026quot;sched/deadline: Remove cpu_active_mask\nfrom cpudl_find()\u0026quot;) removed the check of the cpu_active_mask to\nsave some processing on the premise that the cpudl::free_cpus\nmask already reflected the runqueue online state.\n\nUnfortunately, there are cases where it is possible for the\ncpudl_clear function to set the free_cpus bit for a CPU when the\ndeadline runqueue is offline. When this occurs while a CPU is\nconnected to the default root domain the flag may retain the bad\nstate after the CPU has been unplugged. Later, a different CPU\nthat is transitioning through the default root domain may push a\ndeadline task to the powered down CPU when cpudl_find sees its\nfree_cpus bit is set. If this happens the task will not have the\nopportunity to run.\n\nOne example is outlined here:\nhttps://lore.kernel.org/lkml/(CVE-2025-68780)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nscsi: target: Reset t_task_cdb pointer in error case\n\nIf allocation of cmd-\u0026gt;t_task_cdb fails, it remains NULL but is later\ndereferenced in the \u0026apos;err\u0026apos; path.\n\nIn case of error, reset NULL t_task_cdb value to point at the default\nfixed-size buffer.\n\nFound by Linux Verification Center (linuxtesting.org) with SVACE.(CVE-2025-68782)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\niomap: adjust read range correctly for non-block-aligned positions\n\niomap_adjust_read_range() assumes that the position and length passed in\nare block-aligned. This is not always the case however, as shown in the\nsyzbot generated case for erofs. This causes too many bytes to be\nskipped for uptodate blocks, which results in returning the incorrect\nposition and length to read in. If all the blocks are uptodate, this\nunderflows length and returns a position beyond the folio.\n\nFix the calculation to also take into account the block offset when\ncalculating how many bytes can be skipped for uptodate blocks.(CVE-2025-68794)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nNFSD: NFSv4 file creation neglects setting ACL\n\nAn NFSv4 client that sets an ACL with a named principal during file\ncreation retrieves the ACL afterwards, and finds that it is only a\ndefault ACL (based on the mode bits) and not the ACL that was\nrequested during file creation. This violates RFC 8881 section\n6.4.1.3: \u0026quot;the ACL attribute is set as given\u0026quot;.\n\nThe issue occurs in nfsd_create_setattr(), which calls\nnfsd_attrs_valid() to determine whether to call nfsd_setattr().\nHowever, nfsd_attrs_valid() checks only for iattr changes and\nsecurity labels, but not POSIX ACLs. When only an ACL is present,\nthe function returns false, nfsd_setattr() is skipped, and the\nPOSIX ACL is never applied to the inode.\n\nSubsequently, when the client retrieves the ACL, the server finds\nno POSIX ACL on the inode and returns one generated from the file\u0026apos;s\nmode bits rather than returning the originally-specified ACL.(CVE-2025-68803)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nio_uring: fix filename leak in __io_openat_prep()\n\n __io_openat_prep() allocates a struct filename using getname(). However,\nfor the condition of the file being installed in the fixed file table as\nwell as having O_CLOEXEC flag set, the function returns early. At that\npoint, the request doesn\u0026apos;t have REQ_F_NEED_CLEANUP flag set. Due to this,\nthe memory for the newly allocated struct filename is not cleaned up,\ncausing a memory leak.\n\nFix this by setting the REQ_F_NEED_CLEANUP for the request just after the\nsuccessful getname() call, so that when the request is torn down, the\nfilename will be cleaned up, along with other resources needing cleanup.(CVE-2025-68814)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnet/mlx5: fw_tracer, Validate format string parameters\n\nAdd validation for format string parameters in the firmware tracer to\nprevent potential security vulnerabilities and crashes from malformed\nformat strings received from firmware.\n\nThe firmware tracer receives format strings from the device firmware and\nuses them to format trace messages. Without proper validation, bad\nfirmware could provide format strings with invalid format specifiers\n(e.g., %s, %p, %n) that could lead to crashes, or other undefined\nbehavior.\n\nAdd mlx5_tracer_validate_params() to validate that all format specifiers\nin trace strings are limited to safe integer/hex formats (%x, %d, %i,\n%u, %llx, %lx, etc.). Reject strings containing other format types that\ncould be used to access arbitrary memory or cause crashes.\nInvalid format strings are added to the trace output for visibility with\n\u0026quot;BAD_FORMAT: \u0026quot; prefix.(CVE-2025-68816)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nscsi: Revert \u0026quot;scsi: qla2xxx: Perform lockless command completion in abort path\u0026quot;\n\nThis reverts commit 0367076b0817d5c75dfb83001ce7ce5c64d803a9.\n\nThe commit being reverted added code to __qla2x00_abort_all_cmds() to\ncall sp-\u0026gt;done() without holding a spinlock.  But unlike the older code\nbelow it, this new code failed to check sp-\u0026gt;cmd_type and just assumed\nTYPE_SRB, which results in a jump to an invalid pointer in target-mode\nwith TYPE_TGT_CMD:\n\nqla2xxx [0000:65:00.0]-d034:8: qla24xx_do_nack_work create sess success\n  0000000009f7a79b\nqla2xxx [0000:65:00.0]-5003:8: ISP System Error - mbx1=1ff5h mbx2=10h\n  mbx3=0h mbx4=0h mbx5=191h mbx6=0h mbx7=0h.\nqla2xxx [0000:65:00.0]-d01e:8: -\u0026gt; fwdump no buffer\nqla2xxx [0000:65:00.0]-f03a:8: qla_target(0): System error async event\n  0x8002 occurred\nqla2xxx [0000:65:00.0]-00af:8: Performing ISP error recovery -\n  ha=0000000058183fda.\nBUG: kernel NULL pointer dereference, address: 0000000000000000\nPF: supervisor instruction fetch in kernel mode\nPF: error_code(0x0010) - not-present page\nPGD 0 P4D 0\nOops: 0010 [#1] SMP\nCPU: 2 PID: 9446 Comm: qla2xxx_8_dpc Tainted: G           O       6.1.133 #1\nHardware name: Supermicro Super Server/X11SPL-F, BIOS 4.2 12/15/2023\nRIP: 0010:0x0\nCode: Unable to access opcode bytes at 0xffffffffffffffd6.\nRSP: 0018:ffffc90001f93dc8 EFLAGS: 00010206\nRAX: 0000000000000282 RBX: 0000000000000355 RCX: ffff88810d16a000\nRDX: ffff88810dbadaa8 RSI: 0000000000080000 RDI: ffff888169dc38c0\nRBP: ffff888169dc38c0 R08: 0000000000000001 R09: 0000000000000045\nR10: ffffffffa034bdf0 R11: 0000000000000000 R12: ffff88810800bb40\nR13: 0000000000001aa8 R14: ffff888100136610 R15: ffff8881070f7400\nFS:  0000000000000000(0000) GS:ffff88bf80080000(0000) knlGS:0000000000000000\nCS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033\nCR2: ffffffffffffffd6 CR3: 000000010c8ff006 CR4: 00000000003706e0\nDR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000\nDR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400\nCall Trace:\n \u0026lt;TASK\u0026gt;\n ? __die+0x4d/0x8b\n ? page_fault_oops+0x91/0x180\n ? trace_buffer_unlock_commit_regs+0x38/0x1a0\n ? exc_page_fault+0x391/0x5e0\n ? asm_exc_page_fault+0x22/0x30\n __qla2x00_abort_all_cmds+0xcb/0x3e0 [qla2xxx_scst]\n qla2x00_abort_all_cmds+0x50/0x70 [qla2xxx_scst]\n qla2x00_abort_isp_cleanup+0x3b7/0x4b0 [qla2xxx_scst]\n qla2x00_abort_isp+0xfd/0x860 [qla2xxx_scst]\n qla2x00_do_dpc+0x581/0xa40 [qla2xxx_scst]\n kthread+0xa8/0xd0\n \u0026lt;/TASK\u0026gt;\n\nThen commit 4475afa2646d (\u0026quot;scsi: qla2xxx: Complete command early within\nlock\u0026quot;) added the spinlock back, because not having the lock caused a\nrace and a crash.  But qla2x00_abort_srb() in the switch below already\nchecks for qla2x00_chip_is_down() and handles it the same way, so the\ncode above the switch is now redundant and still buggy in target-mode.\nRemove it.(CVE-2025-68818)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nshmem: fix recovery on rename failures\n\nmaple_tree insertions can fail if we are seriously short on memory;\nsimple_offset_rename() does not recover well if it runs into that.\nThe same goes for simple_offset_rename_exchange().\n\nMoreover, shmem_whiteout() expects that if it succeeds, the caller will\nprogress to d_move(), i.e. that shmem_rename2() won\u0026apos;t fail past the\nsuccessful call of shmem_whiteout().\n\nNot hard to fix, fortunately - mtree_store() can\u0026apos;t fail if the index we\nare trying to store into is already present in the tree as a singleton.\n\nFor simple_offset_rename_exchange() that\u0026apos;s enough - we just need to be\ncareful about the order of operations.\n\nFor simple_offset_rename() solution is to preinsert the target into the\ntree for new_dir; the rest can be done without any potentially failing\noperations.\n\nThat preinsertion has to be done in shmem_rename2() rather than in\nsimple_offset_rename() itself - otherwise we\u0026apos;d need to deal with the\npossibility of failure after successful shmem_whiteout().(CVE-2025-71072)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nKVM: x86: Fix VM hard lockup after prolonged inactivity with periodic HV timer\n\nWhen advancing the target expiration for the guest\u0026apos;s APIC timer in periodic\nmode, set the expiration to \u0026quot;now\u0026quot; if the target expiration is in the past\n(similar to what is done in update_target_expiration()).  Blindly adding\nthe period to the previous target expiration can result in KVM generating\na practically unbounded number of hrtimer IRQs due to programming an\nexpired timer over and over.  In extreme scenarios, e.g. if userspace\npauses/suspends a VM for an extended duration, this can even cause hard\nlockups in the host.\n\nCurrently, the bug only affects Intel CPUs when using the hypervisor timer\n(HV timer), a.k.a. the VMX preemption timer.  Unlike the software timer,\na.k.a. hrtimer, which KVM keeps running even on exits to userspace, the\nHV timer only runs while the guest is active.  As a result, if the vCPU\ndoes not run for an extended duration, there will be a huge gap between\nthe target expiration and the current time the vCPU resumes running.\nBecause the target expiration is incremented by only one period on each\ntimer expiration, this leads to a series of timer expirations occurring\nrapidly after the vCPU/VM resumes.\n\nMore critically, when the vCPU first triggers a periodic HV timer\nexpiration after resuming, advancing the expiration by only one period\nwill result in a target expiration in the past.  As a result, the delta\nmay be calculated as a negative value.  When the delta is converted into\nan absolute value (tscdeadline is an unsigned u64), the resulting value\ncan overflow what the HV timer is capable of programming.  I.e. the large\nvalue will exceed the VMX Preemption Timer\u0026apos;s maximum bit width of\ncpu_preemption_timer_multi + 32, and thus cause KVM to switch from the\nHV timer to the software timer (hrtimers).\n\nAfter switching to the software timer, periodic timer expiration callbacks\nmay be executed consecutively within a single clock interrupt handler,\nbecause hrtimers honors KVM\u0026apos;s request for an expiration in the past and\nimmediately re-invokes KVM\u0026apos;s callback after reprogramming.  And because\nthe interrupt handler runs with IRQs disabled, restarting KVM\u0026apos;s hrtimer\nover and over until the target expiration is advanced to \u0026quot;now\u0026quot; can result\nin a hard lockup.\n\nE.g. the following hard lockup was triggered in the host when running a\nWindows VM (only relevant because it used the APIC timer in periodic mode)\nafter resuming the VM from a long suspend (in the host).\n\n  NMI watchdog: Watchdog detected hard LOCKUP on cpu 45\n  ...\n  RIP: 0010:advance_periodic_target_expiration+0x4d/0x80 [kvm]\n  ...\n  RSP: 0018:ff4f88f5d98d8ef0 EFLAGS: 00000046\n  RAX: fff0103f91be678e RBX: fff0103f91be678e RCX: 00843a7d9e127bcc\n  RDX: 0000000000000002 RSI: 0052ca4003697505 RDI: ff440d5bfbdbd500\n  RBP: ff440d5956f99200 R08: ff2ff2a42deb6a84 R09: 000000000002a6c0\n  R10: 0122d794016332b3 R11: 0000000000000000 R12: ff440db1af39cfc0\n  R13: ff440db1af39cfc0 R14: ffffffffc0d4a560 R15: ff440db1af39d0f8\n  FS:  00007f04a6ffd700(0000) GS:ff440db1af380000(0000) knlGS:000000e38a3b8000\n  CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033\n  CR2: 000000d5651feff8 CR3: 000000684e038002 CR4: 0000000000773ee0\n  PKRU: 55555554\n  Call Trace:\n   \u0026lt;IRQ\u0026gt;\n   apic_timer_fn+0x31/0x50 [kvm]\n   __hrtimer_run_queues+0x100/0x280\n   hrtimer_interrupt+0x100/0x210\n   ? ttwu_do_wakeup+0x19/0x160\n   smp_apic_timer_interrupt+0x6a/0x130\n   apic_timer_interrupt+0xf/0x20\n   \u0026lt;/IRQ\u0026gt;\n\nMoreover, if the suspend duration of the virtual machine is not long enough\nto trigger a hard lockup in this scenario, since commit 98c25ead5eda\n(\u0026quot;KVM: VMX: Move preemption timer \u0026lt;=\u0026gt; hrtimer dance to common x86\u0026quot;), KVM\nwill continue using the software timer until the guest reprograms the APIC\ntimer in some way.  Since the periodic timer does not require frequent APIC\ntimer register programming, the guest may continue to use the software\ntimer in \n---truncated---(CVE-2025-71104)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nlibceph: make decode_pool() more resilient against corrupted osdmaps\n\nIf the osdmap is (maliciously) corrupted such that the encoded length\nof ceph_pg_pool envelope is less than what is expected for a particular\nencoding version, out-of-bounds reads may ensue because the only bounds\ncheck that is there is based on that length value.\n\nThis patch adds explicit bounds checks for each field that is decoded\nor skipped.(CVE-2025-71116)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ncrypto: seqiv - Do not use req-\u0026gt;iv after crypto_aead_encrypt\n\nAs soon as crypto_aead_encrypt is called, the underlying request\nmay be freed by an asynchronous completion.  Thus dereferencing\nreq-\u0026gt;iv after it returns is invalid.\n\nInstead of checking req-\u0026gt;iv against info, create a new variable\nunaligned_info and use it for that purpose instead.(CVE-2025-71131)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nKEYS: trusted: Fix a memory leak in tpm2_load_cmd\n\n\u0026apos;tpm2_load_cmd\u0026apos; allocates a tempoary blob indirectly via \u0026apos;tpm2_key_decode\u0026apos;\nbut it is not freed in the failure paths. Address this by wrapping the blob\ninto with a cleanup helper.(CVE-2025-71147)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nio_uring/poll: correctly handle io_poll_add() return value on update\n\nWhen the core of io_uring was updated to handle completions\nconsistently and with fixed return codes, the POLL_REMOVE opcode\nwith updates got slightly broken. If a POLL_ADD is pending and\nthen POLL_REMOVE is used to update the events of that request, if that\nupdate causes the POLL_ADD to now trigger, then that completion is lost\nand a CQE is never posted.\n\nAdditionally, ensure that if an update does cause an existing POLL_ADD\nto complete, that the completion value isn\u0026apos;t always overwritten with\n-ECANCELED. For that case, whatever io_poll_add() set the value to\nshould just be retained.(CVE-2025-71149)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nksmbd: Fix refcount leak when invalid session is found on session lookup\n\nWhen a session is found but its state is not SMB2_SESSION_VALID, It\nindicates that no valid session was found, but it is missing to decrement\nthe reference count acquired by the session lookup, which results in\na reference count leak. This patch fixes the issue by explicitly calling\nksmbd_user_session_put to release the reference to the session.(CVE-2025-71150)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnet/mlx5e: Don\u0026apos;t store mlx5e_priv in mlx5e_dev devlink priv\n\nmlx5e_priv is an unstable structure that can be memset(0) if profile\nattaching fails, mlx5e_priv in mlx5e_dev devlink private is used to\nreference the netdev and mdev associated with that struct. Instead,\nstore netdev directly into mlx5e_dev and get mdev from the containing\nmlx5_adev aux device structure.\n\nThis fixes a kernel oops in mlx5e_remove when switchdev mode fails due\nto change profile failure.\n\n$ devlink dev eswitch set pci/0000:00:03.0 mode switchdev\nError: mlx5_core: Failed setting eswitch to offloads.\ndmesg:\nworkqueue: Failed to create a rescuer kthread for wq \u0026quot;mlx5e\u0026quot;: -EINTR\nmlx5_core 0012:03:00.1: mlx5e_netdev_init_profile:6214:(pid 37199): mlx5e_priv_init failed, err=-12\nmlx5_core 0012:03:00.1 gpu3rdma1: mlx5e_netdev_change_profile: new profile init failed, -12\nworkqueue: Failed to create a rescuer kthread for wq \u0026quot;mlx5e\u0026quot;: -EINTR\nmlx5_core 0012:03:00.1: mlx5e_netdev_init_profile:6214:(pid 37199): mlx5e_priv_init failed, err=-12\nmlx5_core 0012:03:00.1 gpu3rdma1: mlx5e_netdev_change_profile: failed to rollback to orig profile, -12\n\n$ devlink dev reload pci/0000:00:03.0 ==\u0026gt; oops\n\nBUG: kernel NULL pointer dereference, address: 0000000000000520\n #PF: supervisor read access in kernel mode\n #PF: error_code(0x0000) - not-present page\nPGD 0 P4D 0\nOops: Oops: 0000 [#1] SMP NOPTI\nCPU: 3 UID: 0 PID: 521 Comm: devlink Not tainted 6.18.0-rc5+ #117 PREEMPT(voluntary)\nHardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.16.3-2.fc40 04/01/2014\nRIP: 0010:mlx5e_remove+0x68/0x130\nRSP: 0018:ffffc900034838f0 EFLAGS: 00010246\nRAX: ffff88810283c380 RBX: ffff888101874400 RCX: ffffffff826ffc45\nRDX: 0000000000000000 RSI: 0000000000000001 RDI: 0000000000000000\nRBP: ffff888102d789c0 R08: ffff8881007137f0 R09: ffff888100264e10\nR10: ffffc90003483898 R11: ffffc900034838a0 R12: ffff888100d261a0\nR13: ffff888100d261a0 R14: ffff8881018749a0 R15: ffff888101874400\nFS:  00007f8565fea740(0000) GS:ffff88856a759000(0000) knlGS:0000000000000000\nCS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033\nCR2: 0000000000000520 CR3: 000000010b11a004 CR4: 0000000000370ef0\nCall Trace:\n \u0026lt;TASK\u0026gt;\n device_release_driver_internal+0x19c/0x200\n bus_remove_device+0xc6/0x130\n device_del+0x160/0x3d0\n ? devl_param_driverinit_value_get+0x2d/0x90\n mlx5_detach_device+0x89/0xe0\n mlx5_unload_one_devl_locked+0x3a/0x70\n mlx5_devlink_reload_down+0xc8/0x220\n devlink_reload+0x7d/0x260\n devlink_nl_reload_doit+0x45b/0x5a0\n genl_family_rcv_msg_doit+0xe8/0x140(CVE-2026-22996)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnvme-tcp: fix NULL pointer dereferences in nvmet_tcp_build_pdu_iovec\n\nCommit efa56305908b (\u0026quot;nvmet-tcp: Fix a kernel panic when host sends an invalid H2C PDU length\u0026quot;)\nadded ttag bounds checking and data_offset\nvalidation in nvmet_tcp_handle_h2c_data_pdu(), but it did not validate\nwhether the command\u0026apos;s data structures (cmd-\u0026gt;req.sg and cmd-\u0026gt;iov) have\nbeen properly initialized before processing H2C_DATA PDUs.\n\nThe nvmet_tcp_build_pdu_iovec() function dereferences these pointers\nwithout NULL checks. This can be triggered by sending H2C_DATA PDU\nimmediately after the ICREQ/ICRESP handshake, before\nsending a CONNECT command or NVMe write command.\n\nAttack vectors that trigger NULL pointer dereferences:\n1. H2C_DATA PDU sent before CONNECT → both pointers NULL\n2. H2C_DATA PDU for READ command → cmd-\u0026gt;req.sg allocated, cmd-\u0026gt;iov NULL\n3. H2C_DATA PDU for uninitialized command slot → both pointers NULL\n\nThe fix validates both cmd-\u0026gt;req.sg and cmd-\u0026gt;iov before calling\nnvmet_tcp_build_pdu_iovec(). Both checks are required because:\n- Uninitialized commands: both NULL\n- READ commands: cmd-\u0026gt;req.sg allocated, cmd-\u0026gt;iov NULL\n- WRITE commands: both allocated(CVE-2026-22998)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnet/mlx5e: Fix crash on profile change rollback failure\n\nmlx5e_netdev_change_profile can fail to attach a new profile and can\nfail to rollback to old profile, in such case, we could end up with a\ndangling netdev with a fully reset netdev_priv. A retry to change\nprofile, e.g. another attempt to call mlx5e_netdev_change_profile via\nswitchdev mode change, will crash trying to access the now NULL\npriv-\u0026gt;mdev.\n\nThis fix allows mlx5e_netdev_change_profile() to handle previous\nfailures and an empty priv, by not assuming priv is valid.\n\nPass netdev and mdev to all flows requiring\nmlx5e_netdev_change_profile() and avoid passing priv.\nIn mlx5e_netdev_change_profile() check if current priv is valid, and if\nnot, just attach the new profile without trying to access the old one.\n\nThis fixes the following oops, when enabling switchdev mode for the 2nd\ntime after first time failure:\n\n ## Enabling switchdev mode first time:\n\nmlx5_core 0012:03:00.1: E-Switch: Supported tc chains and prios offload\nworkqueue: Failed to create a rescuer kthread for wq \u0026quot;mlx5e\u0026quot;: -EINTR\nmlx5_core 0012:03:00.1: mlx5e_netdev_init_profile:6214:(pid 37199): mlx5e_priv_init failed, err=-12\nmlx5_core 0012:03:00.1 gpu3rdma1: mlx5e_netdev_change_profile: new profile init failed, -12\nworkqueue: Failed to create a rescuer kthread for wq \u0026quot;mlx5e\u0026quot;: -EINTR\nmlx5_core 0012:03:00.1: mlx5e_netdev_init_profile:6214:(pid 37199): mlx5e_priv_init failed, err=-12\nmlx5_core 0012:03:00.1 gpu3rdma1: mlx5e_netdev_change_profile: failed to rollback to orig profile, -12\n                                                                         ^^^^^^^^\nmlx5_core 0000:00:03.0: E-Switch: Disable: mode(LEGACY), nvfs(0), necvfs(0), active vports(0)\n\n ## retry: Enabling switchdev mode 2nd time:\n\nmlx5_core 0000:00:03.0: E-Switch: Supported tc chains and prios offload\nBUG: kernel NULL pointer dereference, address: 0000000000000038\n #PF: supervisor read access in kernel mode\n #PF: error_code(0x0000) - not-present page\nPGD 0 P4D 0\nOops: Oops: 0000 [#1] SMP NOPTI\nCPU: 13 UID: 0 PID: 520 Comm: devlink Not tainted 6.18.0-rc4+ #91 PREEMPT(voluntary)\nHardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.16.3-2.fc40 04/01/2014\nRIP: 0010:mlx5e_detach_netdev+0x3c/0x90\nCode: 50 00 00 f0 80 4f 78 02 48 8b bf e8 07 00 00 48 85 ff 74 16 48 8b 73 78 48 d1 ee 83 e6 01 83 f6 01 40 0f b6 f6 e8 c4 42 00 00 \u0026lt;48\u0026gt; 8b 45 38 48 85 c0 74 08 48 89 df e8 cc 47 40 1e 48 8b bb f0 07\nRSP: 0018:ffffc90000673890 EFLAGS: 00010246\nRAX: 0000000000000000 RBX: ffff8881036a89c0 RCX: 0000000000000000\nRDX: ffff888113f63800 RSI: ffffffff822fe720 RDI: 0000000000000000\nRBP: 0000000000000000 R08: 0000000000002dcd R09: 0000000000000000\nR10: ffffc900006738e8 R11: 00000000ffffffff R12: 0000000000000000\nR13: 0000000000000000 R14: ffff8881036a89c0 R15: 0000000000000000\nFS:  00007fdfb8384740(0000) GS:ffff88856a9d6000(0000) knlGS:0000000000000000\nCS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033\nCR2: 0000000000000038 CR3: 0000000112ae0005 CR4: 0000000000370ef0\nCall Trace:\n \u0026lt;TASK\u0026gt;\n mlx5e_netdev_change_profile+0x45/0xb0\n mlx5e_vport_rep_load+0x27b/0x2d0\n mlx5_esw_offloads_rep_load+0x72/0xf0\n esw_offloads_enable+0x5d0/0x970\n mlx5_eswitch_enable_locked+0x349/0x430\n ? is_mp_supported+0x57/0xb0\n mlx5_devlink_eswitch_mode_set+0x26b/0x430\n devlink_nl_eswitch_set_doit+0x6f/0xf0\n genl_family_rcv_msg_doit+0xe8/0x140\n genl_rcv_msg+0x18b/0x290\n ? __pfx_devlink_nl_pre_doit+0x10/0x10\n ? __pfx_devlink_nl_eswitch_set_doit+0x10/0x10\n ? __pfx_devlink_nl_post_doit+0x10/0x10\n ? __pfx_genl_rcv_msg+0x10/0x10\n netlink_rcv_skb+0x52/0x100\n genl_rcv+0x28/0x40\n netlink_unicast+0x282/0x3e0\n ? __alloc_skb+0xd6/0x190\n netlink_sendmsg+0x1f7/0x430\n __sys_sendto+0x213/0x220\n ? __sys_recvmsg+0x6a/0xd0\n __x64_sys_sendto+0x24/0x30\n do_syscall_64+0x50/0x1f0\n entry_SYSCALL_64_after_hwframe+0x76/0x7e\nRIP: 0033:0x7fdfb8495047(CVE-2026-23000)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nx86/fpu: Clear XSTATE_BV[i] in guest XSAVE state whenever XFD[i]=1\n\nWhen loading guest XSAVE state via KVM_SET_XSAVE, and when updating XFD in\nresponse to a guest WRMSR, clear XFD-disabled features in the saved (or to\nbe restored) XSTATE_BV to ensure KVM doesn\u0026apos;t attempt to load state for\nfeatures that are disabled via the guest\u0026apos;s XFD.  Because the kernel\nexecutes XRSTOR with the guest\u0026apos;s XFD, saving XSTATE_BV[i]=1 with XFD[i]=1\nwill cause XRSTOR to #NM and panic the kernel.\n\nE.g. if fpu_update_guest_xfd() sets XFD without clearing XSTATE_BV:\n\n  ------------[ cut here ]------------\n  WARNING: arch/x86/kernel/traps.c:1524 at exc_device_not_available+0x101/0x110, CPU#29: amx_test/848\n  Modules linked in: kvm_intel kvm irqbypass\n  CPU: 29 UID: 1000 PID: 848 Comm: amx_test Not tainted 6.19.0-rc2-ffa07f7fd437-x86_amx_nm_xfd_non_init-vm #171 NONE\n  Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 0.0.0 02/06/2015\n  RIP: 0010:exc_device_not_available+0x101/0x110\n  Call Trace:\n   \u0026lt;TASK\u0026gt;\n   asm_exc_device_not_available+0x1a/0x20\n  RIP: 0010:restore_fpregs_from_fpstate+0x36/0x90\n   switch_fpu_return+0x4a/0xb0\n   kvm_arch_vcpu_ioctl_run+0x1245/0x1e40 [kvm]\n   kvm_vcpu_ioctl+0x2c3/0x8f0 [kvm]\n   __x64_sys_ioctl+0x8f/0xd0\n   do_syscall_64+0x62/0x940\n   entry_SYSCALL_64_after_hwframe+0x4b/0x53\n   \u0026lt;/TASK\u0026gt;\n  ---[ end trace 0000000000000000 ]---\n\nThis can happen if the guest executes WRMSR(MSR_IA32_XFD) to set XFD[18] = 1,\nand a host IRQ triggers kernel_fpu_begin() prior to the vmexit handler\u0026apos;s\ncall to fpu_update_guest_xfd().\n\nand if userspace stuffs XSTATE_BV[i]=1 via KVM_SET_XSAVE:\n\n  ------------[ cut here ]------------\n  WARNING: arch/x86/kernel/traps.c:1524 at exc_device_not_available+0x101/0x110, CPU#14: amx_test/867\n  Modules linked in: kvm_intel kvm irqbypass\n  CPU: 14 UID: 1000 PID: 867 Comm: amx_test Not tainted 6.19.0-rc2-2dace9faccd6-x86_amx_nm_xfd_non_init-vm #168 NONE\n  Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 0.0.0 02/06/2015\n  RIP: 0010:exc_device_not_available+0x101/0x110\n  Call Trace:\n   \u0026lt;TASK\u0026gt;\n   asm_exc_device_not_available+0x1a/0x20\n  RIP: 0010:restore_fpregs_from_fpstate+0x36/0x90\n   fpu_swap_kvm_fpstate+0x6b/0x120\n   kvm_load_guest_fpu+0x30/0x80 [kvm]\n   kvm_arch_vcpu_ioctl_run+0x85/0x1e40 [kvm]\n   kvm_vcpu_ioctl+0x2c3/0x8f0 [kvm]\n   __x64_sys_ioctl+0x8f/0xd0\n   do_syscall_64+0x62/0x940\n   entry_SYSCALL_64_after_hwframe+0x4b/0x53\n   \u0026lt;/TASK\u0026gt;\n  ---[ end trace 0000000000000000 ]---\n\nThe new behavior is consistent with the AMX architecture.  Per Intel\u0026apos;s SDM,\nXSAVE saves XSTATE_BV as \u0026apos;0\u0026apos; for components that are disabled via XFD\n(and non-compacted XSAVE saves the initial configuration of the state\ncomponent):\n\n  If XSAVE, XSAVEC, XSAVEOPT, or XSAVES is saving the state component i,\n  the instruction does not generate #NM when XCR0[i] = IA32_XFD[i] = 1;\n  instead, it operates as if XINUSE[i] = 0 (and the state component was\n  in its initial state): it saves bit i of XSTATE_BV field of the XSAVE\n  header as 0; in addition, XSAVE saves the initial configuration of the\n  state component (the other instructions do not save state component i).\n\nAlternatively, KVM could always do XRSTOR with XFD=0, e.g. by using\na constant XFD based on the set of enabled features when XSAVEing for\na struct fpu_guest.  However, having XSTATE_BV[i]=1 for XFD-disabled\nfeatures can only happen in the above interrupt case, or in similar\nscenarios involving preemption on preemptible kernels, because\nfpu_swap_kvm_fpstate()\u0026apos;s call to save_fpregs_to_fpstate() saves the\noutgoing FPU state with the current XFD; and that is (on all but the\nfirst WRMSR to XFD) the guest XFD.\n\nTherefore, XFD can only go out of sync with XSTATE_BV in the above\ninterrupt case, or in similar scenarios involving preemption on\npreemptible kernels, and it we can consider it (de facto) part of KVM\nABI that KVM_GET_XSAVE returns XSTATE_BV[i]=0 for XFD-disabled features.\n\n[Move clea\n---truncated---(CVE-2026-23005)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnet/mlx5e: Pass netdev to mlx5e_destroy_netdev instead of priv\n\nmlx5e_priv is an unstable structure that can be memset(0) if profile\nattaching fails.\n\nPass netdev to mlx5e_destroy_netdev() to guarantee it will work on a\nvalid netdev.\n\nOn mlx5e_remove: Check validity of priv-\u0026gt;profile, before attempting\nto cleanup any resources that might be not there.\n\nThis fixes a kernel oops in mlx5e_remove when switchdev mode fails due\nto change profile failure.\n\n$ devlink dev eswitch set pci/0000:00:03.0 mode switchdev\nError: mlx5_core: Failed setting eswitch to offloads.\ndmesg:\nworkqueue: Failed to create a rescuer kthread for wq \u0026quot;mlx5e\u0026quot;: -EINTR\nmlx5_core 0012:03:00.1: mlx5e_netdev_init_profile:6214:(pid 37199): mlx5e_priv_init failed, err=-12\nmlx5_core 0012:03:00.1 gpu3rdma1: mlx5e_netdev_change_profile: new profile init failed, -12\nworkqueue: Failed to create a rescuer kthread for wq \u0026quot;mlx5e\u0026quot;: -EINTR\nmlx5_core 0012:03:00.1: mlx5e_netdev_init_profile:6214:(pid 37199): mlx5e_priv_init failed, err=-12\nmlx5_core 0012:03:00.1 gpu3rdma1: mlx5e_netdev_change_profile: failed to rollback to orig profile, -12\n\n$ devlink dev reload pci/0000:00:03.0 ==\u0026gt; oops\n\nBUG: kernel NULL pointer dereference, address: 0000000000000370\nPGD 0 P4D 0\nOops: Oops: 0000 [#1] SMP NOPTI\nCPU: 15 UID: 0 PID: 520 Comm: devlink Not tainted 6.18.0-rc5+ #115 PREEMPT(voluntary)\nHardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.16.3-2.fc40 04/01/2014\nRIP: 0010:mlx5e_dcbnl_dscp_app+0x23/0x100\nRSP: 0018:ffffc9000083f8b8 EFLAGS: 00010286\nRAX: ffff8881126fc380 RBX: ffff8881015ac400 RCX: ffffffff826ffc45\nRDX: 0000000000000000 RSI: 0000000000000001 RDI: ffff8881035109c0\nRBP: ffff8881035109c0 R08: ffff888101e3e838 R09: ffff888100264e10\nR10: ffffc9000083f898 R11: ffffc9000083f8a0 R12: ffff888101b921a0\nR13: ffff888101b921a0 R14: ffff8881015ac9a0 R15: ffff8881015ac400\nFS:  00007f789a3c8740(0000) GS:ffff88856aa59000(0000) knlGS:0000000000000000\nCS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033\nCR2: 0000000000000370 CR3: 000000010b6c0001 CR4: 0000000000370ef0\nCall Trace:\n \u0026lt;TASK\u0026gt;\n mlx5e_remove+0x57/0x110\n device_release_driver_internal+0x19c/0x200\n bus_remove_device+0xc6/0x130\n device_del+0x160/0x3d0\n ? devl_param_driverinit_value_get+0x2d/0x90\n mlx5_detach_device+0x89/0xe0\n mlx5_unload_one_devl_locked+0x3a/0x70\n mlx5_devlink_reload_down+0xc8/0x220\n devlink_reload+0x7d/0x260\n devlink_nl_reload_doit+0x45b/0x5a0\n genl_family_rcv_msg_doit+0xe8/0x140(CVE-2026-23035)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ntracing: Add recursion protection in kernel stack trace recording\n\nA bug was reported about an infinite recursion caused by tracing the rcu\nevents with the kernel stack trace trigger enabled. The stack trace code\ncalled back into RCU which then called the stack trace again.\n\nExpand the ftrace recursion protection to add a set of bits to protect\nevents from recursion. Each bit represents the context that the event is\nin (normal, softirq, interrupt and NMI).\n\nHave the stack trace code use the interrupt context to protect against\nrecursion.\n\nNote, the bug showed an issue in both the RCU code as well as the tracing\nstacktrace code. This only handles the tracing stack trace side of the\nbug. The RCU fix will be handled separately.(CVE-2026-23138)","status":"published","published":"2026-03-27T11:10:47Z","modified":"2026-08-18T01:19:45.881631165Z","cvss":[{"version":"3.1","score":7.8,"vector":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H","level":"high"}],"updated_at":"2026-11-02T15:52:45.721983Z"},{"id":"RHBA-2025:6279","title":"Red Hat Bug Fix Advisory: kernel bug fix and enhancement update","status":"published","published":"2026-02-11T10:02:59Z","modified":"2026-09-28T10:03:28Z","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:52:58.636919Z"},{"id":"RHSA-2025:6966","title":"Red Hat Security Advisory: kernel security update","status":"published","published":"2025-05-14T10:05:42Z","modified":"2026-10-17T10:06:54Z","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:17.133041Z"},{"id":"UBUNTU-CVE-2024-53232","description":"In the Linux kernel, the following vulnerability has been resolved: iommu/s390: Implement blocking domain This fixes a crash when surprise hot-unplugging a PCI device. This crash happens because during hot-unplug __iommu_group_set_domain_nofail() attaching the default domain fails when the platform no longer recognizes the device as it has already been removed and we end up with a NULL domain pointer and UAF. This is exactly the case referred to in the second comment in __iommu_device_set_domain() and just as stated there if we can instead attach the blocking domain the UAF is prevented as this can handle the already removed device. Implement the blocking domain to use this handling.  With this change, the crash is fixed but we still hit a warning attempting to change DMA ownership on a blocked device.","status":"published","published":"2024-12-27T14:15:00Z","modified":"2026-10-08T12:52:51.020881388Z","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"},{"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:55:11.182485Z"},{"id":"SUSE-SU-2025:0289-1","title":"Security update for the Linux Kernel","description":"\nThe SUSE Linux Enterprise 15 SP6 Confidential Computing kernel was updated to receive various security bugfixes.\n\n\nThe following security bugs were fixed:\n\n- CVE-2023-52489: mm/sparsemem: fix race in accessing memory_section-\u003eusage (bsc#1221326).\n- CVE-2024-26596: net: dsa: fix netdev_priv() dereference before check on non-DSA netdevice events (bsc#1220355).\n- CVE-2024-26924: scsi: lpfc: Release hbalock before calling lpfc_worker_wake_up() (bsc#1225820).\n- CVE-2024-27397: netfilter: nf_tables: use timestamp to check for set element timeout (bsc#1224095).\n- CVE-2024-35839: kABI fix for netfilter: bridge: replace physindev with physinif in nf_bridge_info (bsc#1224726).\n- CVE-2024-36915: nfc: llcp: fix nfc_llcp_setsockopt() unsafe copies (bsc#1225758).\n- CVE-2024-41042: Prefer nft_chain_validate (bsc#1228526).\n- CVE-2024-44934: net: bridge: mcast: wait for previous gc cycles when removing port (bsc#1229809).\n- CVE-2024-44996: vsock: fix recursive -\u003erecvmsg calls (bsc#1230205).\n- CVE-2024-45828: i3c: mipi-i3c-hci: Mask ring interrupts before ring stop request (bsc#1235705).\n- CVE-2024-46680: Bluetooth: btnxpuart: Fix random crash seen while removing driver (bsc#1230557).\n- CVE-2024-46765: ice: protect XDP configuration with a mutex (bsc#1230807).\n- CVE-2024-46800: sch/netem: fix use after free in netem_dequeue (bsc#1230827).\n- CVE-2024-47678: icmp: change the order of rate limits (bsc#1231854).\n- CVE-2024-48881: bcache: revert replacing IS_ERR_OR_NULL with IS_ERR again (bsc#1235727).\n- CVE-2024-49944: sctp: set sk_state back to CLOSED if autobind fails in sctp_listen_start (bsc#1232166).\n- CVE-2024-49951: Bluetooth: MGMT: Fix possible crash on mgmt_index_removed (bsc#1232158).\n- CVE-2024-49952: netfilter: nf_tables: prevent nf_skb_duplicated corruption (bsc#1232157).\n- CVE-2024-49998: net: dsa: improve shutdown sequence (bsc#1232087).\n- CVE-2024-50018: net: napi: Prevent overflow of napi_defer_hard_irqs (bsc#1232419).\n- CVE-2024-50039: kABI: Restore deleted EXPORT_SYMBOL(__qdisc_calculate_pkt_len) (bsc#1231909).\n- CVE-2024-50143: udf: fix uninit-value use in udf_get_fileshortad (bsc#1233038).\n- CVE-2024-50151: smb: client: fix OOBs when building SMB2_IOCTL request (bsc#1233055).\n- CVE-2024-50199: mm/swapfile: skip HugeTLB pages for unuse_vma (bsc#1233112).\n- CVE-2024-50202: nilfs2: propagate directory read errors from nilfs_find_entry() (bsc#1233324).\n- CVE-2024-50252: mlxsw: spectrum_ipip: Fix memory leak when changing remote IPv6 address (bsc#1233201).\n- CVE-2024-50256: netfilter: nf_reject_ipv6: fix potential crash in nf_send_reset6() (bsc#1233200).\n- CVE-2024-50262: bpf: Fix out-of-bounds write in trie_get_next_key() (bsc#1233239).\n- CVE-2024-50278, CVE-2024-50280: dm cache: fix flushing uninitialized delayed_work on cache_ctr error (bsc#1233467 bsc#1233469).\n- CVE-2024-50278: dm cache: fix potential out-of-bounds access on the first resume (bsc#1233467).\n- CVE-2024-50279: dm cache: fix out-of-bounds access to the dirty bitset when resizing (bsc#1233468).\n- CVE-2024-50296: net: hns3: fix kernel crash when uninstalling driver (bsc#1233485).\n- CVE-2024-50299: sctp: properly validate chunk size in sctp_sf_ootb() (bsc#1233488).\n- CVE-2024-53043: mctp i2c: handle NULL header address (bsc#1233523).\n- CVE-2024-53050: drm/i915/hdcp: Add encoder check in hdcp2_get_capability (bsc#1233546).\n- CVE-2024-53051: drm/i915/hdcp: Add encoder check in intel_hdcp_get_capability (bsc#1233547).\n- CVE-2024-53055: wifi: iwlwifi: mvm: fix 6 GHz scan construction (bsc#1233550).\n- CVE-2024-53056: drm/mediatek: Fix potential NULL dereference in mtk_crtc_destroy() (bsc#1233568).\n- CVE-2024-53064: idpf: fix idpf_vc_core_init error path (bsc#1233558 bsc#1234464).\n- CVE-2024-53090: afs: Fix lock recursion (bsc#1233637).\n- CVE-2024-53091: bpf: Add sk_is_inet and IS_ICSK check in tls_sw_has_ctx_tx/rx (bsc#1233638).\n- CVE-2024-53099: bpf: Check validity of link-\u003etype in bpf_link_show_fdinfo() (bsc#1233772).\n- CVE-2024-53105: mm: page_alloc: move mlocked flag clearance into free_pages_prepare() (bsc#1234069).\n- CVE-2024-53110: vp_vdpa: fix id_table array not null terminated error (bsc#1234085).\n- CVE-2024-53111: mm/mremap: fix address wraparound in move_page_tables() (bsc#1234086).\n- CVE-2024-53113: mm: fix NULL pointer dereference in alloc_pages_bulk_noprof (bsc#1234077).\n- CVE-2024-53117: virtio/vsock: Improve MSG_ZEROCOPY error handling (bsc#1234079).\n- CVE-2024-53118: vsock: Fix sk_error_queue memory leak (bsc#1234071).\n- CVE-2024-53119: virtio/vsock: Fix accept_queue memory leak (bsc#1234073).\n- CVE-2024-53121: net/mlx5: fs, lock FTE when checking if active (bsc#1234078).\n- CVE-2024-53122: mptcp: cope racing subflow creation in mptcp_rcv_space_adjust (bsc#1234076).\n- CVE-2024-53125: bpf: sync_linked_regs() must preserve subreg_def (bsc#1234156).\n- CVE-2024-53130: nilfs2: fix null-ptr-deref in block_dirty_buffer tracepoint (bsc#1234219).\n- CVE-2024-53131: nilfs2: fix null-ptr-deref in block_touch_buffer tracepoint (bsc#1234220).\n- CVE-2024-53133: drm/amd/display: Handle dml allocation failure to avoid crash (bsc#1234221)\n- CVE-2024-53134: pmdomain: imx93-blk-ctrl: correct remove path (bsc#1234159).\n- CVE-2024-53138: net/mlx5e: kTLS, Fix incorrect page refcounting (bsc#1234223).\n- CVE-2024-53141: netfilter: ipset: add missing range check in bitmap_ip_uadt (bsc#1234381).\n- CVE-2024-53160: rcu/kvfree: Fix data-race in __mod_timer / kvfree_call_rcu (bsc#1234810).\n- CVE-2024-53161: EDAC/bluefield: Fix potential integer overflow (bsc#1234856).\n- CVE-2024-53164: net: sched: fix ordering of qlen adjustment (bsc#1234863).\n- CVE-2024-53170: block: fix uaf for flush rq while iterating tags (bsc#1234888).\n- CVE-2024-53172: ubi: fastmap: Fix duplicate slab cache names while attaching (bsc#1234898).\n- CVE-2024-53175: ipc: fix memleak if msg_init_ns failed in create_ipc_ns (bsc#1234893).\n- CVE-2024-53179: smb: client: fix use-after-free of signing key (bsc#1234921).\n- CVE-2024-53185: smb: client: fix NULL ptr deref in crypto_aead_setkey() (bsc#1234901).\n- CVE-2024-53195: KVM: arm64: Get rid of userspace_irqchip_in_use (bsc#1234957).\n- CVE-2024-53196: KVM: arm64: Do not retire aborted MMIO instruction (bsc#1234906).\n- CVE-2024-53198: xen: Fix the issue of resource not being properly released in xenbus_dev_probe() (bsc#1234923).\n- CVE-2024-53214: vfio/pci: Properly hide first-in-list PCIe extended capability (bsc#1235004).\n- CVE-2024-53216: nfsd: fix UAF when access ex_uuid or ex_stats (bsc#1235003).\n- CVE-2024-53222: zram: fix NULL pointer in comp_algorithm_show() (bsc#1234974).\n- CVE-2024-53227: scsi: bfa: Fix use-after-free in bfad_im_module_exit() (bsc#1235011).\n- CVE-2024-53232: iommu/s390: Implement blocking domain (bsc#1235050).\n- CVE-2024-53234: erofs: handle NONHEAD !delta[1] lclusters gracefully (bsc#1235045).\n- CVE-2024-53236: xsk: Free skb when TX metadata options are invalid (bsc#1235000).\n- CVE-2024-53240: xen/netfront: fix crash when removing device (bsc#1234281).\n- CVE-2024-53241: x86/xen: use new hypercall functions instead of hypercall page (XSA-466 bsc#1234282).\n- CVE-2024-53685: ceph: give up on paths longer than PATH_MAX (bsc#1235720).\n- CVE-2024-55639: net: renesas: rswitch: avoid use-after-put for a device tree node (bsc#1235737).\n- CVE-2024-55881: KVM: x86: Play nice with protected guests in complete_hypercall_exit() (bsc#1235745).\n- CVE-2024-56372: net: tun: fix tun_napi_alloc_frags() (bsc#1235753).\n- CVE-2024-56549: cachefiles: Fix NULL pointer dereference in object-\u003efile (bsc#1234912).\n- CVE-2024-56566: mm/slub: Avoid list corruption when removing a slab from the full list (bsc#1235033).\n- CVE-2024-56568: iommu/arm-smmu: Defer probe of clients after smmu device bound (bsc#1235032).\n- CVE-2024-56569: ftrace: Fix regression with module command in stack_trace_filter (bsc#1235031).\n- CVE-2024-56570: ovl: Filter invalid inodes with missing lookup function (bsc#1235035).\n- CVE-2024-56582: btrfs: fix use-after-free in btrfs_encoded_read_endio() (bsc#1235128).\n- CVE-2024-56588: scsi: hisi_sas: Create all dump files during debugfs initialization (bsc#1235123).\n- CVE-2024-56589: scsi: hisi_sas: Add cond_resched() for no forced preemption model (bsc#1235241).\n- CVE-2024-56599: wifi: ath10k: avoid NULL pointer error during sdio remove (bsc#1235138).\n- CVE-2024-56602: net: ieee802154: do not leave a dangling sk pointer in ieee802154_create() (bsc#1235521).\n- CVE-2024-56603: net: af_can: do not leave a dangling sk pointer in can_create() (bsc#1235415).\n- CVE-2024-56604: Bluetooth: RFCOMM: avoid leaving dangling sk pointer in rfcomm_sock_alloc() (bsc#1235056).\n- CVE-2024-56605: Bluetooth: L2CAP: do not leave dangling sk pointer on error in l2cap_sock_create() (bsc#1235061).\n- CVE-2024-56611: mm/mempolicy: fix migrate_to_node() assuming there is at least one VMA in a MM (bsc#1235391).\n- CVE-2024-56614: xsk: fix OOB map writes when deleting elements (bsc#1235424).\n- CVE-2024-56615: bpf: fix OOB devmap writes when deleting elements (bsc#1235426).\n- CVE-2024-56617: cacheinfo: Allocate memory during CPU hotplug if not done from the primary CPU (bsc#1235429).\n- CVE-2024-56620: scsi: ufs: qcom: Only free platform MSIs when ESI is enabled (bsc#1235227).\n- CVE-2024-56622: scsi: ufs: core: sysfs: Prevent div by zero (bsc#1235251).\n- CVE-2024-56631: scsi: sg: Fix slab-use-after-free read in sg_release() (bsc#1235480).\n- CVE-2024-56635: net: avoid potential UAF in default_operstate() (bsc#1235519).\n- CVE-2024-56636: geneve: do not assume mac header is set in geneve_xmit_skb() (bsc#1235520).\n- CVE-2024-56637: netfilter: ipset: Hold module reference while requesting a module (bsc#1235523).\n- CVE-2024-56641: net/smc: initialize close_work early to avoid warning (bsc#1235526).\n- CVE-2024-56643: dccp: Fix memory leak in dccp_feat_change_recv (bsc#1235132).\n- CVE-2024-56648: net: hsr: avoid potential out-of-bound access in fill_frame_info() (bsc#1235451).\n- CVE-2024-56649: net: enetc: Do not configure preemptible TCs if SIs do not support (bsc#1235449).\n- CVE-2024-56656: bnxt_en: Fix aggregation ID mask to prevent oops on 5760X chips (bsc#1235444).\n- CVE-2024-56659: net: lapb: increase LAPB_HEADER_LEN (bsc#1235439).\n- CVE-2024-56660: net/mlx5: DR, prevent potential error pointer dereference (bsc#1235437).\n- CVE-2024-56664: bpf, sockmap: Fix race between element replace and close() (bsc#1235249).\n- CVE-2024-56675: bpf: Fix UAF via mismatching bpf_prog/attachment RCU flavors (bsc#1235555).\n- CVE-2024-56694: bpf: fix recursive lock when verdict program return SK_PASS (bsc#1235412).\n- CVE-2024-56704: 9p/xen: fix release of IRQ (bsc#1235584).\n- CVE-2024-56708: EDAC/igen6: Avoid segmentation fault on module unload (bsc#1235564).\n- CVE-2024-56712: udmabuf: fix memory leak on last export_udmabuf() error path (bsc#1235565).\n- CVE-2024-56716: netdevsim: prevent bad user input in nsim_dev_health_break_write() (bsc#1235587).\n- CVE-2024-56729: smb: Initialize cfid-\u003etcon before performing network ops (bsc#1235503).\n- CVE-2024-56747: scsi: qedi: Fix a possible memory leak in qedi_alloc_and_init_sb() (bsc#1234934).\n- CVE-2024-56748: scsi: qedf: Fix a possible memory leak in qedf_alloc_and_init_sb() (bsc#1235627).\n- CVE-2024-56755: netfs/fscache: Add a memory barrier for FSCACHE_VOLUME_CREATING (bsc#1234920).\n- CVE-2024-56759: btrfs: fix use-after-free when COWing tree bock and tracing is enabled (bsc#1235645).\n- CVE-2024-56774: btrfs: add a sanity check for btrfs root in btrfs_search_slot() (bsc#1235653).\n- CVE-2024-56775: drm/amd/display: Fix handling of plane refcount (bsc#1235657).\n- CVE-2024-57791: net/smc: check return value of sock_recvmsg when draining clc data (bsc#1235759).\n- CVE-2024-57793: virt: tdx-guest: Just leak decrypted memory on unrecoverable errors (bsc#1235768).\n- CVE-2024-57795: RDMA/rxe: Remove the direct link to net_device (bsc#1235906).\n- CVE-2024-57801: net/mlx5e: Skip restore TC rules for vport rep without loaded flag (bsc#1235940).\n- CVE-2024-57804: scsi: mpi3mr: Fix corrupt config pages PHY state is switched in sysfs (bsc#1235779).\n- CVE-2024-57809: PCI: imx6: Fix suspend/resume support on i.MX6QDL (bsc#1235793).\n- CVE-2024-57838: s390/entry: Mark IRQ entries to fix stack depot warnings (bsc#1235798).\n- CVE-2024-57857: RDMA/siw: Remove direct link to net_device (bsc#1235946).\n- CVE-2024-57892: ocfs2: fix slab-use-after-free due to dangling pointer dqi_priv (bsc#1235964).\n- CVE-2024-57896: btrfs: flush delalloc workers queue before stopping cleaner kthread during unmount (bsc#1235965).\n- CVE-2024-57903: net: restrict SO_REUSEPORT to inet sockets (bsc#1235967).\n- CVE-2024-57929: dm array: fix releasing a faulty array block twice in dm_array_cursor_end (bsc#1236096).\n- CVE-2024-57932: gve: guard XDP xmit NDO on existence of xdp queues (bsc#1236190).\n- CVE-2024-57933: gve: guard XSK operations on the existence of queues (bsc#1236178).\n- CVE-2025-21632: x86/fpu: Ensure shadow stack is active before 'getting' registers (bsc#1236106).\n- CVE-2025-21649: net: hns3: fix kernel crash when 1588 is sent on HIP08 devices (bsc#1236143).\n- CVE-2025-21650: net: hns3: fixed hclge_fetch_pf_reg accesses bar space out of bounds issue (bsc#1236144).\n- CVE-2025-21651: net: hns3: do not auto enable misc vector (bsc#1236145).\n- CVE-2025-21662: net/mlx5: Fix variable not being completed when function returns (bsc#1236198).\n\nThe following non-security bugs were fixed:\n\n- 9p: v9fs_fid_find: also lookup by inode if not found dentry (git-fixes).\n- ACPI/HMAT: Move HMAT messages to pr_debug() (bsc#1234294)\n- ACPI/IORT: Add PMCG platform information for HiSilicon HIP09A (stable-fixes).\n- ACPI/IORT: Add PMCG platform information for HiSilicon HIP10/11 (stable-fixes).\n- ACPI: PCC: Add PCC shared memory region command and status bitfields (stable-fixes).\n- ACPI: PRM: Add PRM handler direct call support (jsc#PED-10467).\n- ACPI: resource: Add Asus Vivobook X1504VAP to irq1_level_low_skip_override[] (stable-fixes).\n- ACPI: resource: Add TongFang GM5HG0A to irq1_edge_low_force_override[] (stable-fixes).\n- ACPI: resource: Fix memory resource type union access (git-fixes).\n- ACPI: x86: Add skip i2c clients quirk for Acer Iconia One 8 A1-840 (stable-fixes).\n- ACPI: x86: Clean up Asus entries in acpi_quirk_skip_dmi_ids[] (stable-fixes).\n- ACPI: x86: Make UART skip quirks work on PCI UARTs without an UID (stable-fixes).\n- ACPICA: events/evxfregn: do not release the ContextMutex that was never acquired (git-fixes).\n- ALSA hda/realtek: Add quirk for Framework F111:000C (stable-fixes).\n- ALSA: hda/conexant: fix Z60MR100 startup pop issue (stable-fixes).\n- ALSA: hda/hdmi: Yet more pin fix for HP EliteDesk 800 G4 (stable-fixes).\n- ALSA: hda/realtek - Add support for ASUS Zen AIO 27 Z272SD_A272SD audio (stable-fixes).\n- ALSA: hda/realtek: Add Framework Laptop 13 (Intel Core Ultra) to quirks (stable-fixes).\n- ALSA: hda/realtek: Add new alc2xx-fixup-headset-mic model (stable-fixes).\n- ALSA: hda/realtek: Add support for Ayaneo System using CS35L41 HDA (stable-fixes).\n- ALSA: hda/realtek: Add support for Galaxy Book2 Pro (NP950XEE) (stable-fixes).\n- ALSA: hda/realtek: Add support for Samsung Galaxy Book3 360 (NP730QFG) (stable-fixes).\n- ALSA: hda/realtek: Enable mute and micmute LED on HP ProBook 430 G8 (stable-fixes).\n- ALSA: hda/realtek: Fix headset mic on Acer Nitro 5 (stable-fixes).\n- ALSA: hda: Add HP MP9 G4 Retail System AMS to force connect list (stable-fixes).\n- ALSA: line6: Fix racy access to midibuf (stable-fixes).\n- ALSA: seq: Check UMP support for midi_version change (git-fixes).\n- ALSA: seq: oss: Fix races at processing SysEx messages (stable-fixes).\n- ALSA: seq: ump: Fix seq port updates per FB info notify (git-fixes).\n- ALSA: seq: ump: Use automatic cleanup of kfree() (stable-fixes).\n- ALSA: seq: ump: Use guard() for locking (stable-fixes).\n- ALSA: ump: Use guard() for locking (stable-fixes).\n- ALSA: usb-audio: Add implicit feedback quirk for Yamaha THR5 (stable-fixes).\n- ALSA: usb-audio: Fix a DMA to stack memory bug (git-fixes).\n- ALSA: usb-audio: Notify xrun for low-latency mode (git-fixes).\n- ALSA: usb-audio: Re-add ScratchAmp quirk entries (git-fixes).\n- ALSA: usb-audio: US16x08: Initialize array before use (git-fixes).\n- ALSA: usb-audio: add mixer mapping for Corsair HS80 (stable-fixes).\n- ASoC: Intel: avs: da7219: Remove suspend_pre() and resume_post() (stable-fixes).\n- ASoC: Intel: sof_sdw: add quirk for Dell SKU 0B8C (stable-fixes).\n- ASoC: Intel: sof_sdw: fix jack detection on ADL-N variant RVP (stable-fixes).\n- ASoC: SOF: Remove libraries from topology lookups (git-fixes).\n- ASoC: SOF: ipc3-topology: fix resource leaks in sof_ipc3_widget_setup_comp_dai() (git-fixes).\n- ASoC: amd: yc: Add a quirk for microfone on Lenovo ThinkPad P14s Gen 5 21MES00B00 (stable-fixes).\n- ASoC: amd: yc: Add quirk for microphone on Lenovo Thinkpad T14s Gen 6 21M1CTO1WW (stable-fixes).\n- ASoC: amd: yc: Fix the wrong return value (git-fixes).\n- ASoC: amd: yc: Support mic on HP 14-em0002la (stable-fixes).\n- ASoC: amd: yc: Support mic on Lenovo Thinkpad E14 Gen 6 (stable-fixes).\n- ASoC: amd: yc: fix internal mic on Redmi G 2022 (stable-fixes).\n- ASoC: codecs: wcd938x-sdw: Correct Soundwire ports mask (git-fixes).\n- ASoC: codecs: wsa881x: Correct Soundwire ports mask (git-fixes).\n- ASoC: codecs: wsa883x: Correct Soundwire ports mask (git-fixes).\n- ASoC: codecs: wsa884x: Correct Soundwire ports mask (git-fixes).\n- ASoC: cs35l56: Handle OTP read latency over SoundWire (stable-fixes).\n- ASoC: cs35l56: Patch CS35L56_IRQ1_MASK_18 to the default value (stable-fixes).\n- ASoC: fsl_micfil: Expand the range of FIFO watermark mask (stable-fixes).\n- ASoC: hdmi-codec: reorder channel allocation list (stable-fixes).\n- ASoC: mediatek: disable buffer pre-allocation (stable-fixes).\n- ASoC: mediatek: mt8188-mt6359: Remove hardcoded dmic codec (git-fixes).\n- ASoC: meson: axg-fifo: fix irq scheduling issue with PREEMPT_RT (git-fixes).\n- ASoC: nau8822: Lower debug print priority (stable-fixes).\n- ASoC: rt722: add delay time to wait for the calibration procedure (stable-fixes).\n- Bluetooth: Add support ITTIM PE50-M75C (stable-fixes).\n- Bluetooth: Fix type of len in rfcomm_sock_getsockopt{,_old}() (stable-fixes).\n- Bluetooth: ISO: Reassociate a socket with an active BIS (stable-fixes).\n- Bluetooth: L2CAP: do not leave dangling sk pointer on error in l2cap_sock_create() (stable-fixes).\n- Bluetooth: MGMT: Fix Add Device to responding before completing (git-fixes).\n- Bluetooth: MGMT: Fix possible deadlocks (git-fixes).\n- Bluetooth: SCO: Add support for 16 bits transparent voice setting (git-fixes).\n- Bluetooth: btnxpuart: Fix driver sending truncated data (git-fixes).\n- Bluetooth: btnxpuart: Resolve TX timeout error in power save stress test (bsc#1230557)\n- Bluetooth: btusb: Add RTL8852BE device 0489:e123 to device tables (stable-fixes).\n- Bluetooth: btusb: Add USB HW IDs for MT7921/MT7922/MT7925 (stable-fixes).\n- Bluetooth: btusb: Add new VID/PID 0489/e111 for MT7925 (stable-fixes).\n- Bluetooth: btusb: Add new VID/PID 13d3/3602 for MT7925 (stable-fixes).\n- Bluetooth: btusb: add callback function in btusb suspend/resume (stable-fixes).\n- Bluetooth: btusb: mediatek: add callback function in btusb_disconnect (stable-fixes).\n- Bluetooth: hci_core: Fix not checking skb length on hci_acldata_packet (stable-fixes).\n- Bluetooth: hci_event: Fix using rcu_read_(un)lock while iterating (git-fixes).\n- Bluetooth: hci_sync: Fix not setting Random Address when required (git-fixes).\n- Bluetooth: iso: Fix recursive locking warning (git-fixes).\n- Disable ceph (jsc#PED-7242)\n- Documentation/virt/kvm: Document on Trust Domain Extensions(TDX) (jsc#PED-6143).\n- Documentation: PM: Clarify pm_runtime_resume_and_get() return value (git-fixes).\n- Drivers: hv: util: Avoid accessing a ringbuffer not initialized yet (git-fixes).\n- Drop uvcvideo fix due to regression (bsc#1235894)\n- HID: magicmouse: Apple Magic Trackpad 2 USB-C driver support (stable-fixes).\n- HID: wacom: fix when get product name maybe null pointer (git-fixes).\n- Input: bbnsm_pwrkey - fix missed key press after suspend (git-fixes).\n- KVM: Fix conflict of IOCTL definition of KVM_MEMORY_MAPPING (jsc#PED-6143).\n- KVM: SVM: Allow guest writes to set MSR_AMD64_DE_CFG bits (bsc#1234635).\n- KVM: TDX: Add KVM Exit for TDX TDG.VP.VMCALL (jsc#PED-6143).\n- KVM: TDX: Add TSX_CTRL msr into uret_msrs list (jsc#PED-6143).\n- KVM: TDX: Add a method to ignore dirty logging (jsc#PED-6143).\n- KVM: TDX: Add a method to ignore for TDX to ignore hypercall patch (jsc#PED-6143).\n- KVM: TDX: Add a place holder for handler of TDX hypercalls (TDG.VP.VMCALL) (jsc#PED-6143).\n- KVM: TDX: Add a place holder to handle TDX VM exit (jsc#PED-6143).\n- KVM: TDX: Add accessors VMX VMCS helpers (jsc#PED-6143).\n- KVM: TDX: Add helper function to read TDX metadata in array (jsc#PED-6143).\n- KVM: TDX: Add helper functions to allocate/free TDX private host key id (jsc#PED-6143).\n- KVM: TDX: Add is_private check for mmu_alloc_root (jsc#PED-6143).\n- KVM: TDX: Add load_mmu_pgd method for TDX (jsc#PED-6143).\n- KVM: TDX: Add methods to ignore VMX preemption timer (jsc#PED-6143).\n- KVM: TDX: Add methods to ignore accesses to TSC (jsc#PED-6143).\n- KVM: TDX: Add methods to ignore guest instruction emulation (jsc#PED-6143).\n- KVM: TDX: Add methods to ignore virtual apic related operation (jsc#PED-6143).\n- KVM: TDX: Add support for find pending IRQ in a protected local APIC (jsc#PED-6143).\n- KVM: TDX: Complete interrupts after tdexit (jsc#PED-6143).\n- KVM: TDX: Create initial guest memory (jsc#PED-6143).\n- KVM: TDX: Do TDX specific vcpu initialization (jsc#PED-6143).\n- KVM: TDX: Do not use NO_RBP_MOD for backward compatibility (jsc#PED-6143).\n- KVM: TDX: Emulate Xen MTRR disablement (jsc#PED-6143).\n- KVM: TDX: Extend memory measurement with initial guest memory (jsc#PED-6143).\n- KVM: TDX: Finalize VM initialization (jsc#PED-6143).\n- KVM: TDX: Fix incompatibility with QEMU definition (jsc#PED-6143).\n- KVM: TDX: Fix is_private for page fault handler (jsc#PED-6143).\n- KVM: TDX: Get system-wide info about TDX module on initialization (jsc#PED-6143).\n- KVM: TDX: Handle EXIT_REASON_OTHER_SMI with MSMI (jsc#PED-6143).\n- KVM: TDX: Handle MSR IA32_FEAT_CTL MSR and IA32_MCG_EXT_CTL (jsc#PED-6143).\n- KVM: TDX: Handle MSR MTRRCap and MTRRDefType access (jsc#PED-6143).\n- KVM: TDX: Handle TDG.VP.VMCALL\u0026lt;GetTdVmCallInfo\u003e hypercall (jsc#PED-6143).\n- KVM: TDX: Handle TDX PV CPUID hypercall (jsc#PED-6143).\n- KVM: TDX: Handle TDX PV HLT hypercall (jsc#PED-6143).\n- KVM: TDX: Handle TDX PV MMIO hypercall (jsc#PED-6143).\n- KVM: TDX: Handle TDX PV port io hypercall (jsc#PED-6143).\n- KVM: TDX: Handle TDX PV rdmsr/wrmsr hypercall (jsc#PED-6143).\n- KVM: TDX: Handle vmentry failure for INTEL TD guest (jsc#PED-6143).\n- KVM: TDX: Ignore setting up mce (jsc#PED-6143).\n- KVM: TDX: Implement TDX vcpu enter/exit path (jsc#PED-6143).\n- KVM: TDX: Implement callbacks for MSR operations for TDX (jsc#PED-6143).\n- KVM: TDX: Implement interrupt injection (jsc#PED-6143).\n- KVM: TDX: Implement methods to inject NMI (jsc#PED-6143).\n- KVM: TDX: Inhibit APICv for TDX guest (jsc#PED-6143).\n- KVM: TDX: MTRR: implement get_mt_mask() for TDX (jsc#PED-6143).\n- KVM: TDX: Make KVM_CAP_MAX_VCPUS backend specific (jsc#PED-6143).\n- KVM: TDX: Make pmu_intel.c ignore guest TD case (jsc#PED-6143).\n- KVM: TDX: Refuse to unplug the last cpu on the package (jsc#PED-6143).\n- KVM: TDX: Require TDP MMU and mmio caching for TDX (jsc#PED-6143).\n- KVM: TDX: Retry seamcall when TDX_OPERAND_BUSY with operand SEPT (jsc#PED-6143).\n- KVM: TDX: Return -EINTR for KVM_MEMORY_MAPPING when signal pending (jsc#PED-6143).\n- KVM: TDX: Silently discard SMI request (jsc#PED-6143).\n- KVM: TDX: Silently ignore INIT/SIPI (jsc#PED-6143).\n- KVM: TDX: TDP MMU TDX support (jsc#PED-6143).\n- KVM: TDX: create/destroy VM structure (jsc#PED-6143).\n- KVM: TDX: create/free TDX vcpu structure (jsc#PED-6143).\n- KVM: TDX: handle EXCEPTION_NMI and EXTERNAL_INTERRUPT (jsc#PED-6143).\n- KVM: TDX: handle EXIT_REASON_OTHER_SMI (jsc#PED-6143).\n- KVM: TDX: handle KVM hypercall with TDG.VP.VMCALL (jsc#PED-6143).\n- KVM: TDX: handle ept violation/misconfig exit (jsc#PED-6143).\n- KVM: TDX: handle vcpu migration over logical processor (jsc#PED-6143).\n- KVM: TDX: initialize VM with TDX specific parameters (jsc#PED-6143).\n- KVM: TDX: remove use of struct vcpu_vmx from posted_interrupt.c (jsc#PED-6143).\n- KVM: TDX: restore debug store when TD exit (jsc#PED-6143).\n- KVM: TDX: restore host xsave state when exit from the guest TD (jsc#PED-6143).\n- KVM: TDX: restore user ret MSRs (jsc#PED-6143).\n- KVM: TDX: vcpu_run: save/restore host state(host kernel gs) (jsc#PED-6143).\n- KVM: TDX: x86: Add ioctl to get TDX systemwide parameters (jsc#PED-6143).\n- KVM: VMX: Move NMI/exception handler to common helper (jsc#PED-6143).\n- KVM: VMX: Split out guts of EPT violation to common/exposed function (jsc#PED-6143).\n- KVM: s390: Reject KVM_SET_GSI_ROUTING on ucontrol VMs (git-fixes bsc#1235776).\n- KVM: s390: Reject setting flic pfault attributes on ucontrol VMs (git-fixes bsc#1235777).\n- KVM: s390: vsie: fix virtual/physical address in unpin_scb() (git-fixes bsc#1235778).\n- KVM: x86/mmu: Add a new is_private member for union kvm_mmu_page_role (jsc#PED-6143).\n- KVM: x86/mmu: Add a private pointer to struct kvm_mmu_page (jsc#PED-6143).\n- KVM: x86/mmu: Add address conversion functions for TDX shared bit of GPA (jsc#PED-6143).\n- KVM: x86/mmu: Alloc TDP MMU roots while holding mmu_lock for read (jsc#PED-6143).\n- KVM: x86/mmu: Allow passing '-1' for 'all' as_id for TDP MMU iterators (jsc#PED-6143).\n- KVM: x86/mmu: Check for usable TDP MMU root while holding mmu_lock for read (jsc#PED-6143).\n- KVM: x86/mmu: Disallow fast page fault on private GPA (jsc#PED-6143).\n- KVM: x86/mmu: Do not do TLB flush when zappings SPTEs in invalid roots (jsc#PED-6143).\n- KVM: x86/mmu: Do not enable page track for TD guest (jsc#PED-6143).\n- KVM: x86/mmu: Free TDP MMU roots while holding mmy_lock for read (jsc#PED-6143).\n- KVM: x86/mmu: Precisely invalidate MMU root_role during CPUID update (git-fixes).\n- KVM: x86/mmu: Skip invalid TDP MMU roots when write-protecting SPTEs (jsc#PED-6143).\n- KVM: x86/mmu: Skip invalid roots when zapping leaf SPTEs for GFN range (jsc#PED-6143).\n- KVM: x86/mmu: Zap invalidated TDP MMU roots at 4KiB granularity (jsc#PED-6143).\n- KVM: x86/tdp_mmu: Apply mmu notifier callback to only shared GPA (jsc#PED-6143).\n- KVM: x86/tdp_mmu: Do not zap private pages for unsupported cases (jsc#PED-6143).\n- KVM: x86/tdp_mmu: Fix to return original flush on unsupported cases (jsc#PED-6143).\n- KVM: x86/tdp_mmu: Init role member of struct kvm_mmu_page at allocation (jsc#PED-6143).\n- KVM: x86/tdp_mmu: Support TDX private mapping for TDP MMU (jsc#PED-6143).\n- KVM: x86: Add a switch_db_regs flag to handle TDX's auto-switched behavior (jsc#PED-6143).\n- KVM: x86: Add hooks in kvm_arch_vcpu_memory_mapping() (jsc#PED-6143).\n- KVM: x86: Allow to update cached values in kvm_user_return_msrs w/o wrmsr (jsc#PED-6143).\n- KVM: x86: Assume timer IRQ was injected if APIC state is proteced (jsc#PED-6143).\n- KVM: x86: Split core of hypercall emulation to helper function (jsc#PED-6143).\n- KVM: x86: design documentation on TDX support of x86 KVM TDP MMU (jsc#PED-6143).\n- NFS/pnfs: Fix a live lock between recalled layouts and layoutget (git-fixes).\n- NFSD: Async COPY result needs to return a write verifier (git-fixes).\n- NFSD: Cap the number of bytes copied by nfs4_reset_recoverydir() (git-fixes).\n- NFSD: Fix nfsd4_shutdown_copy() (git-fixes).\n- NFSD: Prevent NULL dereference in nfsd4_process_cb_update() (git-fixes).\n- NFSD: Prevent a potential integer overflow (git-fixes).\n- NFSD: Remove a never-true comparison (git-fixes).\n- NFSD: initialize copy-\u003ecp_clp early in nfsd4_copy for use by trace point (git-fixes).\n- NFSv4.0: Fix a use-after-free problem in the asynchronous open() (git-fixes).\n- Octeontx2-pf: Free send queue buffers incase of leaf to inner (git-fixes).\n- PCI/AER: Disable AER service on suspend (stable-fixes).\n- PCI/MSI: Handle lack of irqdomain gracefully (git-fixes).\n- PCI: Add 'reset_subordinate' to reset hierarchy below bridge (stable-fixes).\n- PCI: Add ACS quirk for Broadcom BCM5760X NIC (stable-fixes).\n- PCI: Add ACS quirk for Wangxun FF5xxx NICs (stable-fixes).\n- PCI: Add T_PERST_CLK_US macro (git-fixes).\n- PCI: Detect and trust built-in Thunderbolt chips (stable-fixes).\n- PCI: Fix use-after-free of slot-\u003ebus on hot remove (stable-fixes).\n- PCI: Use preserve_config in place of pci_flags (stable-fixes).\n- PCI: cadence: Extract link setup sequence from cdns_pcie_host_setup() (stable-fixes).\n- PCI: cadence: Set cdns_pcie_host_init() global (stable-fixes).\n- PCI: cpqphp: Use PCI_POSSIBLE_ERROR() to check config reads (stable-fixes).\n- PCI: j721e: Add PCIe 4x lane selection support (stable-fixes).\n- PCI: j721e: Add per platform maximum lane settings (stable-fixes).\n- PCI: j721e: Add reset GPIO to struct j721e_pcie (stable-fixes).\n- PCI: j721e: Add suspend and resume support (git-fixes).\n- PCI: j721e: Use T_PERST_CLK_US macro (git-fixes).\n- PCI: qcom: Add support for IPQ9574 (stable-fixes).\n- PCI: vmd: Add DID 8086:B06F and 8086:B60B for Intel client SKUs (stable-fixes).\n- PCI: vmd: Set devices to D0 before enabling PM L1 Substates (stable-fixes).\n- RAS/AMD/ATL: Translate normalized to system physical addresses using PRM (jsc#PED-10467).\n- RDMA/bnxt_re: Add check for path mtu in modify_qp (git-fixes)\n- RDMA/bnxt_re: Add send queue size check for variable wqe (git-fixes)\n- RDMA/bnxt_re: Avoid initializing the software queue for user queues (git-fixes)\n- RDMA/bnxt_re: Avoid sending the modify QP workaround for latest adapters (git-fixes)\n- RDMA/bnxt_re: Disable use of reserved wqes (git-fixes)\n- RDMA/bnxt_re: Fix MSN table size for variable wqe mode (git-fixes)\n- RDMA/bnxt_re: Fix max SGEs for the Work Request (git-fixes)\n- RDMA/bnxt_re: Fix max_qp_wrs reported (git-fixes)\n- RDMA/bnxt_re: Fix reporting hw_ver in query_device (git-fixes)\n- RDMA/bnxt_re: Fix the check for 9060 condition (git-fixes)\n- RDMA/bnxt_re: Fix the locking while accessing the QP table (git-fixes)\n- RDMA/bnxt_re: Fix the max WQE size for static WQE support (git-fixes)\n- RDMA/bnxt_re: Fix the max WQEs used in Static WQE mode (git-fixes)\n- RDMA/bnxt_re: Remove always true dattr validity check (git-fixes)\n- RDMA/core: Fix ENODEV error for iWARP test over vlan (git-fixes)\n- RDMA/hns: Fix accessing invalid dip_ctx during destroying QP (git-fixes)\n- RDMA/hns: Fix mapping error of zero-hop WQE buffer (git-fixes)\n- RDMA/hns: Fix missing flush CQE for DWQE (git-fixes)\n- RDMA/hns: Fix warning storm caused by invalid input in IO path (git-fixes)\n- RDMA/mlx5: Enforce same type port association for multiport RoCE (git-fixes)\n- RDMA/rtrs: Ensure 'ib_sge list' is accessible (git-fixes)\n- RDMA/uverbs: Prevent integer overflow issue (git-fixes)\n- RFC: KVM: x86, TDX: Add check for KVM_SET_CPUID2 (jsc#PED-6143).\n- RFC: KVM: x86: Add x86 callback to check cpuid (jsc#PED-6143).\n- Revert 'block/mq-deadline: use correct way to throttling write requests' (bsc#1234146).\n- Revert 'btrfs: fix use-after-free waiting for encoded read endios (bsc#1235128)'\n- Revert 'igb: Disable threaded IRQ for igb_msix_other' (git-fixes).\n- Revert 'mm, kmsan: fix infinite recursion due to RCU critical section' (bsc#1230413)\n- Revert 'mm/sparsemem: fix race in accessing memory_section-\u003eusage' (bsc#1230413)\n- Revert 'mm: prevent derefencing NULL ptr in pfn_section_valid()' (bsc#1230413)\n- Revert 'mtd: spi-nor: core: replace dummy buswidth from addr to data' (git-fixes).\n- Revert 'unicode: Do not special case ignorable code points' (stable-fixes).\n- Revert 'arm64: Kconfig: Make SME depend on BROKEN for now'\n- SUNRPC: make sure cache entry active before cache_show (git-fixes).\n- SUNRPC: timeout and cancel TLS handshake with -ETIMEDOUT (git-fixes).\n- USB: core: Disable LPM only for non-suspended ports (git-fixes).\n- USB: serial: cp210x: add Phoenix Contact UPS Device (stable-fixes).\n- USB: serial: option: add MediaTek T7XX compositions (stable-fixes).\n- USB: serial: option: add MeiG Smart SLM770A (stable-fixes).\n- USB: serial: option: add MeiG Smart SRM815 (stable-fixes).\n- USB: serial: option: add Neoway N723-EA support (stable-fixes).\n- USB: serial: option: add Netprisma LCUK54 modules for WWAN Ready (stable-fixes).\n- USB: serial: option: add TCL IK512 MBIM \u0026 ECM (stable-fixes).\n- USB: serial: option: add Telit FE910C04 rmnet compositions (stable-fixes).\n- USB: usblp: return error when setting unsupported protocol (git-fixes).\n- VM: TDX: Add place holder for TDX VM specific mem_enc_op ioctl (jsc#PED-6143).\n- accel/habanalabs/gaudi2: unsecure tpc count registers (stable-fixes).\n- accel/habanalabs: export dma-buf only if size/offset multiples of PAGE_SIZE (stable-fixes).\n- accel/habanalabs: fix debugfs files permissions (stable-fixes).\n- accel/habanalabs: increase HL_MAX_STR to 64 bytes to avoid warnings (stable-fixes).\n- acpi: nfit: vmalloc-out-of-bounds Read in acpi_nfit_ctl (git-fixes).\n- af_unix: Call manage_oob() for every skb in unix_stream_read_generic() (bsc#1234725).\n- afs: Automatically generate trace tag enums (git-fixes).\n- afs: Fix missing subdir edit when renamed between parent dirs (git-fixes).\n- afs: Fix the maximum cell name length (git-fixes).\n- amdgpu/uvd: get ring reference from rq scheduler (git-fixes).\n- arch: Introduce arch_{,try_}_cmpxchg128{,_local}() (bsc#1220773).\n- arch: Remove cmpxchg_double (bsc#1220773).\n- arch: consolidate arch_irq_work_raise prototypes (git-fixes).\n- arm64: Ensure bits ASID[15:8] are masked out when the kernel uses (bsc#1234605)\n- arm64: Force position-independent veneers (git-fixes).\n- arm64: Kconfig: Make SME depend on BROKEN for now (git-fixes).\n- arm64: dts: allwinner: pinephone: Add mount matrix to accelerometer (git-fixes)\n- arm64: dts: freescale: imx8mm-verdin: Fix SD regulator startup delay (git-fixes)\n- arm64: dts: freescale: imx8mp-verdin: Fix SD regulator startup delay (git-fixes)\n- arm64: dts: imx8-ss-vpu: Fix imx8qm VPU IRQs (git-fixes)\n- arm64: dts: imx8mp: correct sdhc ipg clk (git-fixes).\n- arm64: dts: imx8qxp: Add VPU subsystem file (git-fixes)\n- arm64: dts: imx93: add nvmem property for eqos (git-fixes)\n- arm64: dts: imx93: add nvmem property for fec1 (git-fixes)\n- arm64: dts: imx93: add ocotp node (git-fixes)\n- arm64: dts: rockchip: Add DTS for FriendlyARM NanoPi R2S Plus (git-fixes)\n- arm64: dts: rockchip: Correct GPIO polarity on brcm BT nodes (git-fixes)\n- arm64: dts: rockchip: Fix LED triggers on rk3308-roc-cc (git-fixes)\n- arm64: dts: rockchip: Fix bluetooth properties on Rock960 boards (git-fixes)\n- arm64: dts: rockchip: Fix bluetooth properties on rk3566 box demo (git-fixes)\n- arm64: dts: rockchip: Fix reset-gpios property on brcm BT nodes (git-fixes)\n- arm64: dts: rockchip: Fix rt5651 compatible value on (git-fixes)\n- arm64: dts: rockchip: Fix rt5651 compatible value on rk3399-eaidk-610 (git-fixes)\n- arm64: dts: rockchip: Fix wakeup prop names on PineNote BT node (git-fixes)\n- arm64: dts: rockchip: Remove #cooling-cells from fan on Theobroma (git-fixes)\n- arm64: dts: rockchip: Remove hdmi's 2nd interrupt on rk3328 (git-fixes)\n- arm64: dts: rockchip: Remove undocumented supports-emmc property (git-fixes)\n- arm64: dts: rockchip: add hevc power domain clock to rk3328 (git-fixes).\n- arm64: dts: rockchip: fix i2c2 pinctrl-names property on (git-fixes)\n- arm64: dts: rockchip: remove num-slots property from (git-fixes)\n- arm64: dts: rockchip: remove orphaned pinctrl-names from pinephone (git-fixes)\n- arm64: fix .data.rel.ro size assertion when CONFIG_LTO_CLANG (git-fixes)\n- arm64: ptrace: fix partial SETREGSET for NT_ARM_TAGGED_ADDR_CTRL (git-fixes).\n- arm64: smccc: Remove broken support for SMCCCv1.3 SVE discard hint (git-fixes)\n- arm64: smccc: replace custom COUNT_ARGS() \u0026 CONCATENATE() (git-fixes)\n- arm64: tegra: Move AGX Orin nodes to correct location (git-fixes)\n- arm64: tls: Fix context-switching of tpidrro_el0 when kpti is enabled (git-fixes)\n- autofs: fix memory leak of waitqueues in autofs_catatonic_mode (git-fixes).\n- batman-adv: Do not let TT changes list grows indefinitely (git-fixes).\n- batman-adv: Do not send uninitialized TT changes (git-fixes).\n- batman-adv: Remove uninitialized data in full table TT response (git-fixes).\n- blk-cgroup: Fix UAF in blkcg_unpin_online() (bsc#1234726).\n- blk-core: use pr_warn_ratelimited() in bio_check_ro() (bsc#1234139).\n- blk-iocost: Fix an UBSAN shift-out-of-bounds warning (bsc#1234144).\n- blk-iocost: do not WARN if iocg was already offlined (bsc#1234147).\n- blk-throttle: fix lockdep warning of 'cgroup_mutex or RCU read lock required!' (bsc#1234140).\n- blk-wbt-Fix-detection-of-dirty-throttled-tasks.patch: Update tags\n- block, bfq: choose the last bfqq from merge chain in bfq_setup_cooperator() (bsc#1234149).\n- block, bfq: do not break merge chain in bfq_split_bfqq() (bsc#1234150).\n- block, bfq: fix bfqq uaf in bfq_limit_depth() (bsc#1234160).\n- block, bfq: fix procress reference leakage for bfqq in merge chain (bsc#1234280).\n- block, bfq: fix uaf for accessing waker_bfqq after splitting (bsc#1234279).\n- block/mq-deadline: Fix the tag reservation code (bsc#1234148).\n- block: Call .limit_depth() after .hctx has been set (bsc#1234148).\n- block: Fix where bio IO priority gets set (bsc#1234145).\n- block: prevent an integer overflow in bvec_try_merge_hw_page (bsc#1234142).\n- block: update the stable_writes flag in bdev_add (bsc#1234141).\n- bnxt_en: Fix GSO type for HW GRO packets on 5750X chips (git-fixes)\n- bnxt_en: Fix receive ring space parameters when XDP is active (git-fixes).\n- bnxt_en: Reserve rings after PCIe AER recovery if NIC interface is down (git-fixes).\n- bnxt_en: Set backplane link modes correctly for ethtool (git-fixes).\n- bpf, arm64: Fix address emission with tag-based KASAN enabled (git-fixes)\n- bpf, arm64: Remove garbage frame for struct_ops trampoline (git-fixes)\n- bpf, x86: Fix PROBE_MEM runtime load check (git-fixes).\n- bpf: verifier: prevent userspace memory access (git-fixes).\n- btrfs: fix use-after-free in btrfs_encoded_read_endio() (bsc#1235445).\n- btrfs: fix use-after-free waiting for encoded read endios (bsc#1235128)\n- btrfs: fix use-after-free waiting for encoded read endios (bsc#1235445).\n- can: c_can: c_can_handle_bus_err(): update statistics if skb allocation fails (git-fixes).\n- can: dev: can_set_termination(): allow sleeping GPIOs (git-fixes).\n- can: ems_usb: ems_usb_rx_err(): fix {rx,tx}_errors statistics (git-fixes).\n- can: gs_usb: add VID/PID for Xylanta SAINT3 product family (stable-fixes).\n- can: hi311x: hi3110_can_ist(): fix potential use-after-free (git-fixes).\n- can: hi311x: hi3110_can_ist(): fix {rx,tx}_errors statistics (git-fixes).\n- can: ifi_canfd: ifi_canfd_handle_lec_err(): fix {rx,tx}_errors statistics (git-fixes).\n- can: j1939: fix error in J1939 documentation (stable-fixes).\n- can: j1939: j1939_session_new(): fix skb reference counting (git-fixes).\n- can: m_can: m_can_handle_lec_err(): fix {rx,tx}_errors statistics (git-fixes).\n- can: mcp251xfd: mcp251xfd_get_tef_len(): work around erratum DS80000789E 6 (git-fixes).\n- can: sja1000: sja1000_err(): fix {rx,tx}_errors statistics (git-fixes).\n- can: sun4i_can: sun4i_can_err(): call can_change_state() even if cf is NULL (git-fixes).\n- can: sun4i_can: sun4i_can_err(): fix {rx,tx}_errors statistics (git-fixes).\n- ceph: improve error handling and short/overflow-read logic in __ceph_sync_read() (bsc#1228592).\n- cleanup: Add conditional guard support (stable-fixes).\n- cleanup: Adjust scoped_guard() macros to avoid potential warning (stable-fixes).\n- cleanup: Remove address space of returned pointer (git-fixes).\n- clocksource/drivers/timer-ti-dm: Fix child node refcount handling (git-fixes).\n- clocksource/drivers:sp804: Make user selectable (git-fixes).\n- counter: stm32-timer-cnt: Add check for clk_enable() (git-fixes).\n- counter: ti-ecap-capture: Add check for clk_enable() (git-fixes).\n- cpufreq: intel_pstate: Check turbo_is_disabled() in store_no_turbo() (bsc#1234619).\n- cpufreq: intel_pstate: Do not update global.turbo_disabled after initialization (bsc#1234619).\n- cpufreq: intel_pstate: Drop redundant locking from intel_pstate_driver_cleanup() (bsc#1234619).\n- cpufreq: intel_pstate: Fix unchecked HWP MSR access (bsc#1234619).\n- cpufreq: intel_pstate: Fold intel_pstate_max_within_limits() into caller (bsc#1234619).\n- cpufreq: intel_pstate: Get rid of unnecessary READ_ONCE() annotations (bsc#1234619).\n- cpufreq: intel_pstate: Read global.no_turbo under READ_ONCE() (bsc#1234619).\n- cpufreq: intel_pstate: Rearrange show_no_turbo() and store_no_turbo() (bsc#1234619).\n- cpufreq: intel_pstate: Refine computation of P-state for given frequency (bsc#1234619).\n- cpufreq: intel_pstate: Replace three global.turbo_disabled checks (bsc#1234619).\n- cpufreq: intel_pstate: Revise global turbo disable check (bsc#1234619).\n- cpufreq: intel_pstate: Simplify spinlock locking (bsc#1234619).\n- cpufreq: intel_pstate: Update the maximum CPU frequency consistently (bsc#1234619).\n- cpufreq: intel_pstate: Use __ro_after_init for three variables (bsc#1234619).\n- cpufreq: intel_pstate: Wait for canceled delayed work to complete (bsc#1234619).\n- crypto: ecc - Prevent ecc_digits_from_bytes from reading too many bytes (git-fixes).\n- crypto: ecdsa - Avoid signed integer overflow on signature decoding (stable-fixes).\n- crypto: ecdsa - Convert byte arrays with key coordinates to digits (stable-fixes).\n- crypto: ecdsa - Rename keylen to bufsize where necessary (stable-fixes).\n- crypto: ecdsa - Use ecc_digits_from_bytes to convert signature (stable-fixes).\n- crypto: qat - disable IOV in adf_dev_stop() (git-fixes).\n- crypto: x86/sha256 - Add parentheses around macros' single arguments (stable-fixes).\n- cyrpto/b128ops: Remove struct u128 (bsc#1220773).\n- devlink: Fix length of eswitch inline-mode (git-fixes).\n- dlm: fix possible lkb_resource null dereference (git-fixes).\n- dma-buf: fix dma_fence_array_signaled v4 (stable-fixes).\n- dma-debug: fix a possible deadlock on radix_lock (stable-fixes).\n- dma-fence: Fix reference leak on fence merge failure path (git-fixes).\n- dma-fence: Use kernel's sort for merging fences (git-fixes).\n- dmaengine: apple-admac: Avoid accessing registers in probe (git-fixes).\n- dmaengine: at_xdmac: avoid null_prt_deref in at_xdmac_prep_dma_memset (git-fixes).\n- dmaengine: dw: Select only supported masters for ACPI devices (git-fixes).\n- dmaengine: idxd: Check for driver name match before sva user feature (bsc#1234357).\n- dmaengine: mv_xor: fix child node refcount handling in early exit (git-fixes).\n- dmaengine: tegra: Return correct DMA status when paused (git-fixes).\n- driver core: Add FWLINK_FLAG_IGNORE to completely ignore a fwnode link (stable-fixes).\n- driver core: fw_devlink: Improve logs for cycle detection (stable-fixes).\n- driver core: fw_devlink: Stop trying to optimize cycle detection logic (git-fixes).\n- drivers: net: ionic: add missed debugfs cleanup to ionic_probe() error path (git-fixes).\n- drm/amd/display: Add HDR workaround for specific eDP (stable-fixes).\n- drm/amd/display: Add NULL check for clk_mgr in dcn32_init_hw (stable-fixes).\n- drm/amd/display: Add check for granularity in dml ceil/floor helpers (stable-fixes).\n- drm/amd/display: Allow backlight to go below `AMDGPU_DM_DEFAULT_MIN_BACKLIGHT` (stable-fixes).\n- drm/amd/display: Avoid overflow assignment in link_dp_cts (stable-fixes).\n- drm/amd/display: Fix DSC-re-computing (stable-fixes).\n- drm/amd/display: Fix Synaptics Cascaded Panamera DSC Determination (stable-fixes).\n- drm/amd/display: Fix incorrect DSC recompute trigger (stable-fixes).\n- drm/amd/display: Revert Avoid overflow assignment (stable-fixes).\n- drm/amd/display: Use gpuvm_min_page_size_kbytes for DML2 surfaces (stable-fixes).\n- drm/amd/display: increase MAX_SURFACES to the value supported by hw (stable-fixes).\n- drm/amd/pm: fix the high voltage issue after unload (stable-fixes).\n- drm/amd/pm: update current_socclk and current_uclk in gpu_metrics on smu v13.0.7 (stable-fixes).\n- drm/amdgpu/gfx10: use rlc safe mode for soft recovery (stable-fixes).\n- drm/amdgpu/gfx11: use rlc safe mode for soft recovery (stable-fixes).\n- drm/amdgpu/gfx9: properly handle error ints on all pipes (stable-fixes).\n- drm/amdgpu/gfx9: use rlc safe mode for soft recovery (stable-fixes).\n- drm/amdgpu/hdp5.2: do a posting read when flushing HDP (stable-fixes).\n- drm/amdgpu/pm: Remove gpu_od if it's an empty directory (stable-fixes).\n- drm/amdgpu/umsch: do not execute umsch test when GPU is in reset/suspend (stable-fixes).\n- drm/amdgpu/umsch: reinitialize write pointer in hw init (stable-fixes).\n- drm/amdgpu/vcn: reset fw_shared when VCPU buffers corrupted on vcn v4.0.3 (stable-fixes).\n- drm/amdgpu: Block MMR_READ IOCTL in reset (stable-fixes).\n- drm/amdgpu: Dereference the ATCS ACPI buffer (stable-fixes).\n- drm/amdgpu: add raven1 gfxoff quirk (stable-fixes).\n- drm/amdgpu: add smu 14.0.1 discovery support (stable-fixes).\n- drm/amdgpu: clear RB_OVERFLOW bit when enabling interrupts for vega20_ih (stable-fixes).\n- drm/amdgpu: differentiate external rev id for gfx 11.5.0 (stable-fixes).\n- drm/amdgpu: disallow multiple BO_HANDLES chunks in one submit (stable-fixes).\n- drm/amdgpu: do not access invalid sched (git-fixes).\n- drm/amdgpu: enable gfxoff quirk on HP 705G4 (stable-fixes).\n- drm/amdgpu: fix unchecked return value warning for amdgpu_gfx (stable-fixes).\n- drm/amdgpu: fix usage slab after free (stable-fixes).\n- drm/amdgpu: prevent BO_HANDLES error from being overwritten (git-fixes).\n- drm/amdgpu: refine error handling in amdgpu_ttm_tt_pin_userptr (stable-fixes).\n- drm/amdgpu: set the right AMDGPU sg segment limitation (stable-fixes).\n- drm/amdgpu: skip amdgpu_device_cache_pci_state under sriov (stable-fixes).\n- drm/amdkfd: Correct the migration DMA map direction (stable-fixes).\n- drm/amdkfd: Fix resource leak in criu restore queue (stable-fixes).\n- drm/amdkfd: Use device based logging for errors (stable-fixes).\n- drm/amdkfd: Use the correct wptr size (stable-fixes).\n- drm/amdkfd: fixed page fault when enable MES shader debugger (git-fixes).\n- drm/amdkfd: pause autosuspend when creating pdd (stable-fixes).\n- drm/bridge: adv7511_audio: Update Audio InfoFrame properly (git-fixes).\n- drm/bridge: it6505: Enable module autoloading (stable-fixes).\n- drm/bridge: it6505: Fix inverted reset polarity (git-fixes).\n- drm/bridge: it6505: update usleep_range for RC circuit charge time (stable-fixes).\n- drm/display: Fix building with GCC 15 (stable-fixes).\n- drm/dp_mst: Ensure mst_primary pointer is valid in drm_dp_mst_handle_up_req() (stable-fixes).\n- drm/dp_mst: Fix MST sideband message body length check (stable-fixes).\n- drm/dp_mst: Fix resetting msg rx state after topology removal (git-fixes).\n- drm/dp_mst: Verify request type in the corresponding down message reply (stable-fixes).\n- drm/etnaviv: flush shader L1 cache after user commandstream (stable-fixes).\n- drm/i915/dg1: Fix power gate sequence (git-fixes).\n- drm/i915: Fix NULL pointer dereference in capture_engine (git-fixes).\n- drm/i915: Fix memory leak by correcting cache object name in error handler (git-fixes).\n- drm/mcde: Enable module autoloading (stable-fixes).\n- drm/mediatek: Add return value check when reading DPCD (git-fixes).\n- drm/mediatek: Add support for 180-degree rotation in the display driver (git-fixes).\n- drm/mediatek: Fix YCbCr422 color format issue for DP (git-fixes).\n- drm/mediatek: Fix mode valid issue for dp (git-fixes).\n- drm/mediatek: Set private-\u003eall_drm_private[i]-\u003edrm to NULL if mtk_drm_bind returns err (git-fixes).\n- drm/mediatek: mtk_dsi: Add registers to pdata to fix MT8186/MT8188 (git-fixes).\n- drm/mediatek: stop selecting foreign drivers (git-fixes).\n- drm/modes: Avoid divide by zero harder in drm_mode_vrefresh() (stable-fixes).\n- drm/nouveau/gsp: Use the sg allocator for level 2 of radix3 (stable-fixes).\n- drm/panel: novatek-nt35950: fix return value check in nt35950_probe() (git-fixes).\n- drm/panel: simple: Add Microchip AC69T88A LVDS Display panel (stable-fixes).\n- drm/printer: Allow NULL data in devcoredump printer (stable-fixes).\n- drm/radeon/r100: Handle unknown family in r100_cp_init_microcode() (stable-fixes).\n- drm/radeon/r600_cs: Fix possible int overflow in r600_packet3_check() (stable-fixes).\n- drm/radeon: Fix spurious unplug event on radeon HDMI (git-fixes).\n- drm/radeon: add helper rdev_to_drm(rdev) (stable-fixes).\n- drm/radeon: change rdev-\u003eddev to rdev_to_drm(rdev) (stable-fixes).\n- drm/sched: memset() 'job' in drm_sched_job_init() (stable-fixes).\n- drm/sti: Add __iomem for mixer_dbg_mxn's parameter (git-fixes).\n- drm/v3d: Enable Performance Counters before clearing them (git-fixes).\n- drm/v3d: Ensure job pointer is set to NULL after job completion (git-fixes).\n- drm/vc4: hdmi: Avoid log spam for audio start failure (stable-fixes).\n- drm/vc4: hvs: Set AXI panic modes for the HVS (stable-fixes).\n- drm/vmwgfx: Add new keep_resv BO param (git-fixes).\n- drm: adv7511: Drop dsi single lane support (git-fixes).\n- drm: adv7511: Fix use-after-free in adv7533_attach_dsi() (git-fixes).\n- drm: panel-orientation-quirks: Add quirk for AYA NEO 2 model (stable-fixes).\n- drm: panel-orientation-quirks: Add quirk for AYA NEO Founder edition (stable-fixes).\n- drm: panel-orientation-quirks: Add quirk for AYA NEO GEEK (stable-fixes).\n- drm: panel-orientation-quirks: Make Lenovo Yoga Tab 3 X90F DMI match less strict (stable-fixes).\n- erofs: avoid debugging output for (de)compressed data (git-fixes).\n- exfat: ensure that ctime is updated whenever the mtime is (git-fixes).\n- exfat: fix the infinite loop in __exfat_free_cluster() (git-fixes).\n- exfat: fix the infinite loop in exfat_readdir() (git-fixes).\n- exfat: fix uninit-value in __exfat_get_dentry_set (git-fixes).\n- ext4: add a new helper to check if es must be kept (bsc#1234170).\n- ext4: add correct group descriptors and reserved GDT blocks to system zone (bsc#1234164).\n- ext4: add missed brelse in update_backups (bsc#1234171).\n- ext4: allow for the last group to be marked as trimmed (bsc#1234278).\n- ext4: avoid buffer_head leak in ext4_mark_inode_used() (bsc#1234191).\n- ext4: avoid excessive credit estimate in ext4_tmpfile() (bsc#1234180).\n- ext4: avoid negative min_clusters in find_group_orlov() (bsc#1234193).\n- ext4: avoid overlapping preallocations due to overflow (bsc#1234162).\n- ext4: avoid potential buffer_head leak in __ext4_new_inode() (bsc#1234192).\n- ext4: avoid writing unitialized memory to disk in EA inodes (bsc#1234187).\n- ext4: check the extent status again before inserting delalloc block (bsc#1234186).\n- ext4: clear EXT4_GROUP_INFO_WAS_TRIMMED_BIT even mount with discard (bsc#1234190).\n- ext4: convert to exclusive lock while inserting delalloc extents (bsc#1234178).\n- ext4: correct best extent lstart adjustment logic (bsc#1234179).\n- ext4: correct grp validation in ext4_mb_good_group (bsc#1234163).\n- ext4: correct return value of ext4_convert_meta_bg (bsc#1234172).\n- ext4: correct the hole length returned by ext4_map_blocks() (bsc#1234178).\n- ext4: correct the start block of counting reserved clusters (bsc#1234169).\n- ext4: do not let fstrim block system suspend (https://bugzilla.kernel.org/show_bug.cgi?id=216322 bsc#1234166).\n- ext4: do not trim the group with corrupted block bitmap (bsc#1234177).\n- ext4: factor out __es_alloc_extent() and __es_free_extent() (bsc#1234170).\n- ext4: factor out a common helper to query extent map (bsc#1234186).\n- ext4: fix inconsistent between segment fstrim and full fstrim (bsc#1234176).\n- ext4: fix incorrect tid assumption in __jbd2_log_wait_for_space() (bsc#1234188).\n- ext4: fix incorrect tid assumption in ext4_wait_for_tail_page_commit() (bsc#1234188).\n- ext4: fix incorrect tid assumption in jbd2_journal_shrink_checkpoint_list() (bsc#1234188).\n- ext4: fix memory leaks in ext4_fname_{setup_filename,prepare_lookup} (bsc#1214954).\n- ext4: fix potential unnitialized variable (bsc#1234183).\n- ext4: fix race between writepages and remount (bsc#1234168).\n- ext4: fix rec_len verify error (bsc#1234167).\n- ext4: fix slab-use-after-free in ext4_es_insert_extent() (bsc#1234170).\n- ext4: fix uninitialized variable in ext4_inlinedir_to_tree (bsc#1234185).\n- ext4: forbid commit inconsistent quota data when errors=remount-ro (bsc#1234178).\n- ext4: make ext4_es_insert_delayed_block() return void (bsc#1234170).\n- ext4: make ext4_es_insert_extent() return void (bsc#1234170).\n- ext4: make ext4_es_remove_extent() return void (bsc#1234170).\n- ext4: make ext4_zeroout_es() return void (bsc#1234170).\n- ext4: make sure allocate pending entry not fail (bsc#1234170).\n- ext4: mark buffer new if it is unwritten to avoid stale data exposure (bsc#1234175).\n- ext4: move 'ix' sanity check to corrent position (bsc#1234174).\n- ext4: move setting of trimmed bit into ext4_try_to_trim_range() (bsc#1234165).\n- ext4: nested locking for xattr inode (bsc#1234189).\n- ext4: propagate errors from ext4_find_extent() in ext4_insert_range() (bsc#1234194).\n- ext4: refactor ext4_da_map_blocks() (bsc#1234178).\n- ext4: remove gdb backup copy for meta bg in setup_new_flex_group_blocks (bsc#1234173).\n- ext4: remove the redundant folio_wait_stable() (bsc#1234184).\n- ext4: set the type of max_zeroout to unsigned int to avoid overflow (bsc#1234182).\n- ext4: set type of ac_groups_linear_remaining to __u32 to avoid overflow (bsc#1234181).\n- ext4: use pre-allocated es in __es_insert_extent() (bsc#1234170).\n- ext4: use pre-allocated es in __es_remove_extent() (bsc#1234170).\n- ext4: using nofail preallocation in ext4_es_insert_delayed_block() (bsc#1234170).\n- ext4: using nofail preallocation in ext4_es_insert_extent() (bsc#1234170).\n- ext4: using nofail preallocation in ext4_es_remove_extent() (bsc#1234170).\n- filemap: Fix bounds checking in filemap_read() (bsc#1234209).\n- filemap: add a per-mapping stable writes flag (bsc#1234141).\n- firmware: arm_scmi: Reject clear channel request on A2P (stable-fixes).\n- fs-writeback: do not requeue a clean inode having skipped pages (bsc#1234200).\n- fs/writeback: bail out if there is no more inodes for IO and queued once (bsc#1234207).\n- fsnotify: fix sending inotify event with unexpected filename (bsc#1234198).\n- genirq/cpuhotplug: Retry with cpu_online_mask when migration fails (git-fixes).\n- genirq/cpuhotplug: Skip suspended interrupts when restoring affinity (git-fixes).\n- genirq/irqdesc: Honor caller provided affinity in alloc_desc() (git-fixes).\n- gpio: grgpio: Add NULL check in grgpio_probe (git-fixes).\n- gpio: grgpio: use a helper variable to store the address of ofdev-\u003edev (stable-fixes).\n- gpio: xilinx: Convert gpio_lock to raw spinlock (git-fixes).\n- hfsplus: do not query the device logical block size multiple times (git-fixes).\n- hvc/xen: fix console unplug (git-fixes).\n- hvc/xen: fix error path in xen_hvc_init() to always register frontend driver (git-fixes).\n- hvc/xen: fix event channel handling for secondary consoles (git-fixes).\n- hwmon: (drivetemp) Fix driver producing garbage data when SCSI errors occur (git-fixes).\n- hwmon: (nct6775) Add 665-ACE/600M-CL to ASUS WMI monitoring list (stable-fixes).\n- hwmon: (pmbus/core) clear faults after setting smbalert mask (git-fixes).\n- hwmon: (pmbus_core) Allow to hook PMBUS_SMBALERT_MASK (stable-fixes).\n- hwmon: (tmp513) Do not use 'proxy' headers (stable-fixes).\n- hwmon: (tmp513) Fix Current Register value interpretation (git-fixes).\n- hwmon: (tmp513) Fix division of negative numbers (git-fixes).\n- hwmon: (tmp513) Fix interpretation of values of Shunt Voltage and Limit Registers (git-fixes).\n- hwmon: (tmp513) Fix interpretation of values of Temperature Result and Limit Registers (git-fixes).\n- hwmon: (tmp513) Simplify with dev_err_probe() (stable-fixes).\n- hwmon: (tmp513) Use SI constants from units.h (stable-fixes).\n- i2c: core: fix reference leak in i2c_register_adapter() (git-fixes).\n- i2c: i801: Add support for Intel Arrow Lake-H (stable-fixes).\n- i2c: i801: Add support for Intel Panther Lake (stable-fixes).\n- i2c: imx: add imx7d compatible string for applying erratum ERR007805 (git-fixes).\n- i2c: microchip-core: actually use repeated sends (git-fixes).\n- i2c: microchip-core: fix 'ghost' detections (git-fixes).\n- i2c: mux: demux-pinctrl: check initial mux selection, too (git-fixes).\n- i2c: pnx: Fix timeout in wait functions (git-fixes).\n- i2c: rcar: fix NACK handling when being a target (git-fixes).\n- i2c: riic: Always round-up when calculating bus period (git-fixes).\n- i2c: xgene-slimpro: Migrate to use generic PCC shmem related macros (stable-fixes).\n- i40e: Fix handling changed priv flags (git-fixes).\n- i915/guc: Accumulate active runtime on gt reset (git-fixes).\n- i915/guc: Ensure busyness counter increases motonically (git-fixes).\n- i915/guc: Reset engine utilization buffer before registration (git-fixes).\n- iTCO_wdt: mask NMI_NOW bit for update_no_reboot_bit() call (git-fixes).\n- ice: Unbind the workqueue (bsc#1234989)\n- ice: change q_index variable type to s16 to store -1 value (git-fixes).\n- ice: consistently use q_idx in ice_vc_cfg_qs_msg() (git-fixes).\n- ice: fix PHY Clock Recovery availability check (git-fixes).\n- idpf: add support for SW triggered interrupts (bsc#1235507).\n- idpf: enable WB_ON_ITR (bsc#1235507).\n- idpf: trigger SW interrupt when exiting wb_on_itr mode (bsc#1235507).\n- ieee802154: ca8210: Add missing check for kfifo_alloc() in ca8210_probe() (git-fixes).\n- igb: Fix potential invalid memory access in igb_init_module() (git-fixes).\n- iio: adc: ad7124: Disable all channels at probe time (git-fixes).\n- iio: adc: at91: call input_free_device() on allocated iio_dev (git-fixes).\n- iio: adc: rockchip_saradc: fix information leak in triggered buffer (git-fixes).\n- iio: adc: ti-ads124s08: Use gpiod_set_value_cansleep() (git-fixes).\n- iio: adc: ti-ads8688: fix information leak in triggered buffer (git-fixes).\n- iio: dummy: iio_simply_dummy_buffer: fix information leak in triggered buffer (git-fixes).\n- iio: gyro: fxas21002c: Fix missing data update in trigger handler (git-fixes).\n- iio: imu: kmx61: fix information leak in triggered buffer (git-fixes).\n- iio: inkern: call iio_device_put() only on mapped devices (git-fixes).\n- iio: light: vcnl4035: fix information leak in triggered buffer (git-fixes).\n- iio: magnetometer: yas530: use signed integer type for clamp limits (git-fixes).\n- iio: pressure: zpa2326: fix information leak in triggered buffer (git-fixes).\n- iio: test : check null return of kunit_kmalloc in iio_rescale_test_scale (git-fixes).\n- instrumentation: Wire up cmpxchg128() (bsc#1220773).\n- io_uring/rw: avoid punting to io-wq directly (git-fixes).\n- io_uring/tctx: work around xa_store() allocation error issue (git-fixes).\n- io_uring: Fix registered ring file refcount leak (git-fixes).\n- io_uring: always lock __io_cqring_overflow_flush (git-fixes).\n- io_uring: check if iowq is killed before queuing (git-fixes).\n- iommu/io-pgtable-arm: Fix stage-2 map/unmap for concatenated tables (git-fixes).\n- irqchip/gic-v3: Force propagation of the active state with a read-back (stable-fixes).\n- irqchip/gic: Correct declaration of *percpu_base pointer in union gic_base (stable-fixes).\n- irqflags: Explicitly ignore lockdep_hrtimer_exit() argument (git-fixes).\n- isofs: handle CDs with bad root inode but good Joliet root directory (bsc#1234199).\n- ixgbe: downgrade logging of unsupported VF API version to debug (git-fixes).\n- ixgbevf: stop attempting IPSEC offload on Mailbox API 1.5 (git-fixes).\n- jffs2: Fix rtime decompressor (git-fixes).\n- jffs2: Prevent rtime decompress memory corruption (git-fixes).\n- jffs2: fix use of uninitialized variable (git-fixes).\n- jfs: add a check to prevent array-index-out-of-bounds in dbAdjTree (git-fixes).\n- jfs: array-index-out-of-bounds fix in dtReadFirst (git-fixes).\n- jfs: fix array-index-out-of-bounds in jfs_readdir (git-fixes).\n- jfs: fix shift-out-of-bounds in dbSplit (git-fixes).\n- jfs: xattr: check invalid xattr size more strictly (git-fixes).\n- kABI workaround for struct drm_dp_mst_topology_mgr (git-fixes).\n- kABI: Fix kABI after TDX KVM backports (jsc#PED-6143).\n- kABI: Restore exported __arm_smccc_sve_check (git-fixes)\n- kabi/severities: make vcap_find_actionfield PASS (bsc#1220773)\n- kasan: make report_lock a raw spinlock (git-fixes).\n- kdb: Fix buffer overflow during tab-complete (bsc#1234652).\n- kdb: Fix console handling when editing and tab-completing commands (bsc#1234655).\n- kdb: Merge identical case statements in kdb_read() (bsc#1234657).\n- kdb: Use format-specifiers rather than memset() for padding in kdb_read() (bsc#1234658).\n- kdb: Use format-strings rather than '\\0' injection in kdb_read() (bsc#1234654).\n- kdb: Use the passed prompt in kdb_position_cursor() (bsc#1234654).\n- kdb: address -Wformat-security warnings (bsc#1234659).\n- kgdb: Flush console before entering kgdb on panic (bsc#1234651).\n- leds: class: Protect brightness_show() with led_cdev-\u003eled_access mutex (stable-fixes).\n- lib/stackdepot: print disabled message only if truly disabled (git-fixes).\n- linux/dmaengine.h: fix a few kernel-doc warnings (git-fixes).\n- locking/atomic/x86: Correct the definition of __arch_try_cmpxchg128() (bsc#1220773 git-fix).\n- loop: fix the the direct I/O support check when used on top of block devices (bsc#1234143).\n- mac80211: fix user-power when emulating chanctx (stable-fixes).\n- mailbox: pcc: Add support for platform notification handling (stable-fixes).\n- mailbox: pcc: Support shared interrupt for multiple subspaces (stable-fixes).\n- media: cx231xx: Add support for Dexatek USB Video Grabber 1d19:6108 (stable-fixes).\n- media: dvb-frontends: dib3000mb: fix uninit-value in dib3000_write_reg (git-fixes).\n- media: uvcvideo: Add a quirk for the Kaiweets KTI-W02 infrared camera (stable-fixes).\n- media: uvcvideo: Force UVC version to 1.0a for 0408:4035 (stable-fixes).\n- media: uvcvideo: RealSense D421 Depth module metadata (stable-fixes).\n- memory tiering: count PGPROMOTE_SUCCESS when mem tiering is enabled (git-fixes).\n- memory-failure: use a folio in me_huge_page() (git-fixes).\n- mfd: da9052-spi: Change read-mask to write-mask (git-fixes).\n- mfd: intel_soc_pmic_bxtwc: Use IRQ domain for PMIC devices (git-fixes).\n- mfd: intel_soc_pmic_bxtwc: Use IRQ domain for TMU device (git-fixes).\n- mfd: intel_soc_pmic_bxtwc: Use IRQ domain for USB Type-C device (git-fixes).\n- misc: microchip: pci1xxxx: Resolve kernel panic during GPIO IRQ handling (git-fixes).\n- misc: microchip: pci1xxxx: Resolve return code mismatch during GPIO set config (git-fixes).\n- mm, kmsan: fix infinite recursion due to RCU critical section (git-fixes).\n- mm,page_owner: do not remove __GFP_NOLOCKDEP in add_stack_record_to_list (git-fixes).\n- mm/filemap: avoid buffered read/write race to read inconsistent data (bsc#1234204).\n- mm/memory-failure: cast index to loff_t before shifting it (git-fixes).\n- mm/memory-failure: check the mapcount of the precise page (git-fixes).\n- mm/memory-failure: fix crash in split_huge_page_to_list from soft_offline_page (git-fixes).\n- mm/memory-failure: pass the folio and the page to collect_procs() (git-fixes).\n- mm/memory-failure: use raw_spinlock_t in struct memory_failure_cpu (git-fixes).\n- mm/memory_hotplug: add missing mem_hotplug_lock (git-fixes).\n- mm/memory_hotplug: fix error handling in add_memory_resource() (git-fixes).\n- mm/memory_hotplug: prevent accessing by index=-1 (git-fixes).\n- mm/memory_hotplug: use pfn math in place of direct struct page manipulation (git-fixes).\n- mm/migrate: correct nr_failed in migrate_pages_sync() (git-fixes).\n- mm/migrate: fix deadlock in migrate_pages_batch() on large folios (git-fixes).\n- mm/migrate: putback split folios when numa hint migration fails (git-fixes).\n- mm/migrate: split source folio if it is on deferred split list (git-fixes).\n- mm/page_owner: remove free_ts from page_owner output (git-fixes).\n- mm/readahead: do not allow order-1 folio (bsc#1234205).\n- mm/readahead: limit page cache size in page_cache_ra_order() (bsc#1234208).\n- mm: convert DAX lock/unlock page to lock/unlock folio (git-fixes).\n- mm: memory-failure: ensure moving HWPoison flag to the raw error pages (git-fixes).\n- mm: memory-failure: fetch compound head after extra page refcnt is held (git-fixes).\n- mm: memory-failure: fix potential page refcnt leak in memory_failure() (git-fixes).\n- mm: memory-failure: fix race window when trying to get hugetlb folio (git-fixes).\n- mm: memory-failure: remove unneeded PageHuge() check (git-fixes).\n- mm: prevent derefencing NULL ptr in pfn_section_valid() (git-fixes).\n- mmc: core: Add SD card quirk for broken poweroff notification (stable-fixes).\n- mmc: core: Further prevent card detect during shutdown (git-fixes).\n- mmc: mtk-sd: Fix MMC_CAP2_CRYPTO flag setting (git-fixes).\n- mmc: mtk-sd: fix devm_clk_get_optional usage (stable-fixes).\n- mmc: sdhci-esdhc-imx: enable quirks SDHCI_QUIRK_NO_LED (stable-fixes).\n- mmc: sdhci-pci: Add DMI quirk for missing CD GPIO on Vexia Edu Atla 10 tablet (stable-fixes).\n- mmc: sdhci-tegra: Remove SDHCI_QUIRK_BROKEN_ADMA_ZEROLEN_DESC quirk (git-fixes).\n- modpost: fix the missed iteration for the max bit in do_input() (git-fixes).\n- mtd: diskonchip: Cast an operand to prevent potential overflow (git-fixes).\n- mtd: hyperbus: rpc-if: Add missing MODULE_DEVICE_TABLE (git-fixes).\n- mtd: hyperbus: rpc-if: Convert to platform remove callback returning void (stable-fixes).\n- mtd: rawnand: arasan: Fix double assertion of chip-select (git-fixes).\n- mtd: rawnand: arasan: Fix missing de-registration of NAND (git-fixes).\n- mtd: rawnand: fix double free in atmel_pmecc_create_user() (git-fixes).\n- net :mana :Request a V2 response version for MANA_QUERY_GF_STAT (git-fixes).\n- net/ipv6: release expired exception dst cached in socket (bsc#1216813).\n- net/mlx5e: CT: Fix null-ptr-deref in add rule err flow (git-fixes).\n- net/mlx5e: Remove workaround to avoid syndrome for internal port (git-fixes).\n- net/mlx5e: clear xdp features on non-uplink representors (git-fixes).\n- net/qed: allow old cards not supporting 'num_images' to work (git-fixes).\n- net: Return error from sk_stream_wait_connect() if sk_wait_event() fails (git-fixes).\n- net: mana: Increase the DEF_RX_BUFFERS_PER_QUEUE to 1024 (bsc#1235246).\n- net: usb: qmi_wwan: add Quectel RG650V (stable-fixes).\n- net: usb: qmi_wwan: add Telit FE910C04 compositions (stable-fixes).\n- net: wwan: iosm: Properly check for valid exec stage in ipc_mmio_init() (git-fixes).\n- net: wwan: t7xx: Fix FSM command timeout issue (git-fixes).\n- netdevsim: copy addresses for both in and out paths (git-fixes).\n- nfs: ignore SB_RDONLY when mounting nfs (git-fixes).\n- nfsd: fix nfs4_openowner leak when concurrent nfsd4_open occur (git-fixes).\n- nfsd: make sure exp active before svc_export_show (git-fixes).\n- nfsd: release svc_expkey/svc_export with rcu_work (git-fixes).\n- nfsd: restore callback functionality for NFSv4.0 (git-fixes).\n- nilfs2: fix buffer head leaks in calls to truncate_inode_pages() (git-fixes).\n- nilfs2: fix potential out-of-bounds memory access in nilfs_find_entry() (git-fixes).\n- nilfs2: prevent use of deleted inode (git-fixes).\n- nvme-pci: 512 byte aligned dma pool segment quirk (git-fixes).\n- nvme-rdma: unquiesce admin_q before destroy it (git-fixes).\n- nvme-tcp: fix the memleak while create new ctrl failed (git-fixes).\n- nvme/multipath: Fix RCU list traversal to use SRCU primitive (git-fixes).\n- nvme: apple: fix device reference counting (git-fixes).\n- nvme: fix metadata handling in nvme-passthrough (git-fixes).\n- nvmet-loop: avoid using mutex in IO hotpath (git-fixes).\n- ocfs2: fix uninitialized value in ocfs2_file_read_iter() (git-fixes).\n- ocfs2: free inode when ocfs2_get_init_inode() fails (git-fixes).\n- of/irq: Fix using uninitialized variable @addr_len in API of_irq_parse_one() (git-fixes).\n- of: Fix error path in of_parse_phandle_with_args_map() (git-fixes).\n- of: Fix refcount leakage for OF node returned by __of_get_dma_parent() (git-fixes).\n- of: address: Report error on resource bounds overflow (stable-fixes).\n- parisc: Raise minimal GCC version (bsc#1220773).\n- parisc: Raise minimal GCC version to 12.0.0 (bsc#1220773 git-fix).\n- percpu: Add {raw,this}_cpu_try_cmpxchg() (bsc#1220773).\n- percpu: Fix self-assignment of __old in raw_cpu_generic_try_cmpxchg() (bsc#1220773 git-fix).\n- percpu: Wire up cmpxchg128 (bsc#1220773).\n- phy: core: Fix an OF node refcount leakage in _of_phy_get() (git-fixes).\n- phy: core: Fix an OF node refcount leakage in of_phy_provider_lookup() (git-fixes).\n- phy: core: Fix that API devm_of_phy_provider_unregister() fails to unregister the phy provider (git-fixes).\n- phy: core: Fix that API devm_phy_destroy() fails to destroy the phy (git-fixes).\n- phy: core: Fix that API devm_phy_put() fails to release the phy (git-fixes).\n- phy: qcom-qmp: Fix register name in RX Lane config of SC8280XP (git-fixes).\n- phy: rockchip: naneng-combphy: fix phy reset (git-fixes).\n- phy: usb: Toggle the PHY power during init (git-fixes).\n- pinctrl: mcp23s08: Fix sleeping in atomic context due to regmap locking (git-fixes).\n- pinctrl: qcom-pmic-gpio: add support for PM8937 (stable-fixes).\n- pinctrl: qcom: spmi-mpp: Add PM8937 compatible (stable-fixes).\n- pinmux: Use sequential access to access desc-\u003epinmux data (stable-fixes).\n- platform/chrome: cros_ec_proto: Lock device when updating MKBP version (git-fixes).\n- platform/x86/amd/pmc: Only disable IRQ1 wakeup where i8042 actually enabled it (git-fixes).\n- platform/x86/intel-uncore-freq: Ignore minor version change (bsc#1225897).\n- platform/x86/intel/tpmi: Add defines to get version information (bsc#1225897).\n- platform/x86: asus-nb-wmi: Ignore unknown event 0xCF (stable-fixes).\n- platform/x86: dell-smbios-base: Extends support to Alienware products (stable-fixes).\n- platform/x86: dell-wmi-base: Handle META key Lock/Unlock events (stable-fixes).\n- platform/x86: thinkpad_acpi: Fix for ThinkPad's with ECFW showing incorrect fan speed (stable-fixes).\n- power: supply: gpio-charger: Fix set charge current limits (git-fixes).\n- powerpc/64s: Fix unnecessary copy to 0 when kernel is booted at address 0 (bsc#1215199).\n- powerpc/atomic: Use YZ constraints for DS-form instructions (bsc#1194869).\n- powerpc/book3s64/hugetlb: Fix disabling hugetlb when fadump is active (bsc#1235108).\n- powerpc/fadump: Move fadump_cma_init to setup_arch() after initmem_init() (bsc#1215199).\n- powerpc/fadump: Refactor and prepare fadump_cma_init for late init (bsc#1215199).\n- powerpc/iommu: Move pSeries specific functions to pseries/iommu.c (bsc#1220711 ltc#205755).\n- powerpc/iommu: Only build sPAPR access functions on pSeries (bsc#1220711 ltc#205755).\n- powerpc/kexec: Fix return of uninitialized variable (bsc#1194869).\n- powerpc/mm/fault: Fix kfence page fault reporting (bsc#1194869).\n- powerpc/mm: Fix boot crash with FLATMEM (bsc#1194869).\n- powerpc/mm: Fix boot warning with hugepages and CONFIG_DEBUG_VIRTUAL (bsc#1194869).\n- powerpc/powernv/pci: Remove MVE code (bsc#1220711 ltc#205755).\n- powerpc/powernv/pci: Remove ioda1 support (bsc#1220711 ltc#205755).\n- powerpc/powernv/pci: Remove last IODA1 defines (bsc#1220711 ltc#205755).\n- powerpc/powernv: Free name on error in opal_event_init() (bsc#1194869).\n- powerpc/pseries/iommu: IOMMU incorrectly marks MMIO range in DDW (bsc#1218470 ltc#204531).\n- powerpc/pseries/vas: Add close() callback in vas_vm_ops struct (bsc#1234825).\n- powerpc/pseries: Fix KVM guest detection for disabling hardlockup detector (bsc#1194869).\n- powerpc/pseries: Fix dtl_access_lock to be a rw_semaphore (bsc#1194869).\n- powerpc/pseries: Use correct data types from pseries_hp_errorlog struct (bsc#1215199).\n- powerpc/vdso: Inconditionally use CFUNC macro (bsc#1215199).\n- proc/softirqs: replace seq_printf with seq_put_decimal_ull_width (git-fixes).\n- quota: Fix rcu annotations of inode dquot pointers (bsc#1234197).\n- quota: explicitly forbid quota files from being encrypted (bsc#1234196).\n- quota: flush quota_release_work upon quota writeback (bsc#1234195).\n- quota: simplify drop_dquot_ref() (bsc#1234197).\n- readahead: use ilog2 instead of a while loop in page_cache_ra_order() (bsc#1234208).\n- regmap: Use correct format specifier for logging range errors (stable-fixes).\n- regmap: detach regmap from dev on regmap_exit (git-fixes).\n- regulator: rk808: Add apply_bit for BUCK3 on RK809 (stable-fixes).\n- rtc: cmos: avoid taking rtc_lock for extended period of time (stable-fixes).\n- s390/cio: Do not unregister the subchannel based on DNV (git-fixes).\n- s390/cpum_sf: Convert to cmpxchg128() (bsc#1220773).\n- s390/cpum_sf: Handle CPU hotplug remove during sampling (git-fixes).\n- s390/cpum_sf: Remove WARN_ON_ONCE statements (git-fixes).\n- s390/facility: Disable compile time optimization for decompressor code (git-fixes).\n- s390/iucv: MSG_PEEK causes memory leak in iucv_sock_destruct() (git-fixes).\n- s390/pageattr: Implement missing kernel_page_present() (git-fixes).\n- s390x config: IOMMU_DEFAULT_DMA_LAZY=y (bsc#1235646)\n- scatterlist: fix incorrect func name in kernel-doc (git-fixes).\n- sched/numa: fix memory leak due to the overwritten vma-\u003enumab_state (git fixes (sched/numa)).\n- scsi: lpfc: Add handling for LS_RJT reason explanation authentication required (bsc#1235409).\n- scsi: lpfc: Add support for large fw object application layer reads (bsc#1235409).\n- scsi: lpfc: Change lpfc_nodelist save_flags member into a bitmask (bsc#1235409).\n- scsi: lpfc: Copyright updates for 14.4.0.7 patches (bsc#1235409).\n- scsi: lpfc: Delete NLP_TARGET_REMOVE flag due to obsolete usage (bsc#1235409).\n- scsi: lpfc: Modify handling of ADISC based on ndlp state and RPI registration (bsc#1235409).\n- scsi: lpfc: Redefine incorrect type in lpfc_create_device_data() (bsc#1235409).\n- scsi: lpfc: Restrict the REG_FCFI MAM field to FCoE adapters only (bsc#1235409).\n- scsi: lpfc: Update definition of firmware configuration mbox cmds (bsc#1235409).\n- scsi: lpfc: Update lpfc version to 14.4.0.7 (bsc#1235409).\n- scsi: qla2xxx: Fix NVMe and NPIV connect issue (bsc#1235406).\n- scsi: qla2xxx: Fix abort in bsg timeout (bsc#1235406).\n- scsi: qla2xxx: Fix use after free on unload (bsc#1235406).\n- scsi: qla2xxx: Remove check req_sg_cnt should be equal to rsp_sg_cnt (bsc#1235406).\n- scsi: qla2xxx: Remove the unused 'del_list_entry' field in struct fc_port (bsc#1235406).\n- scsi: qla2xxx: Supported speed displayed incorrectly for VPorts (bsc#1235406).\n- scsi: qla2xxx: Update version to 10.02.09.400-k (bsc#1235406).\n- scsi: storvsc: Do not flag MAINTENANCE_IN return of SRB_STATUS_DATA_OVERRUN as an error (git-fixes).\n- selftests/bpf: Test PROBE_MEM of VSYSCALL_ADDR on x86-64 (git-fixes).\n- selftests: mptcp: avoid spurious errors on disconnect (git-fixes).\n- serial: 8250_dw: Add Sophgo SG2044 quirk (stable-fixes).\n- serial: 8250_dw: Do not use struct dw8250_data outside of 8250_dw (git-fixes).\n- serial: 8250_dw: Replace ACPI device check by a quirk (git-fixes).\n- serial: 8250_fintek: Add support for F81216E (stable-fixes).\n- serial: Do not hold the port lock when setting rx-during-tx GPIO (git-fixes).\n- serial: amba-pl011: Fix RX stall when DMA is used (git-fixes).\n- serial: amba-pl011: Use port lock wrappers (stable-fixes).\n- serial: amba-pl011: fix build regression (git-fixes).\n- serial: do not use uninitialized value in uart_poll_init() (git-fixes).\n- serial: imx: only set receiver level if it is zero (git-fixes).\n- serial: imx: set receiver level before starting uart (git-fixes).\n- serial: qcom-geni: Do not cancel/abort if we can't get the port lock (git-fixes).\n- serial: qcom-geni: disable interrupts during console writes (git-fixes).\n- serial: qcom-geni: fix arg types for qcom_geni_serial_poll_bit() (git-fixes).\n- serial: qcom-geni: fix console corruption (git-fixes).\n- serial: qcom-geni: fix dma rx cancellation (git-fixes).\n- serial: qcom-geni: fix false console tx restart (git-fixes).\n- serial: qcom-geni: fix fifo polling timeout (git-fixes).\n- serial: qcom-geni: fix hard lockup on buffer flush (git-fixes).\n- serial: qcom-geni: fix polled console corruption (git-fixes).\n- serial: qcom-geni: fix polled console initialisation (git-fixes).\n- serial: qcom-geni: fix receiver enable (git-fixes).\n- serial: qcom-geni: fix shutdown race (git-fixes).\n- serial: qcom-geni: fix soft lockup on sw flow control and suspend (git-fixes).\n- serial: qcom-geni: introduce qcom_geni_serial_poll_bitfield() (git-fixes).\n- serial: qcom-geni: revert broken hibernation support (git-fixes).\n- serial: stm32: Return IRQ_NONE in the ISR if no handling happend (git-fixes).\n- serial: stm32: do not always set SER_RS485_RX_DURING_TX if RS485 is enabled (git-fixes).\n- slub: Replace cmpxchg_double() (bsc#1220773).\n- slub: Replace cmpxchg_double() - KABI fix (bsc#1220773).\n- smb: client: fix TCP timers deadlock after rmmod (git-fixes) [hcarvalho: fix issue described in bsc#1233642]\n- soc/fsl: cpm: qmc: Convert to platform remove callback returning void (stable-fixes).\n- soc: fsl: cpm1: qmc: Fix blank line and spaces (stable-fixes).\n- soc: fsl: cpm1: qmc: Introduce qmc_init_resource() and its CPM1 version (stable-fixes).\n- soc: fsl: cpm1: qmc: Introduce qmc_{init,exit}_xcc() and their CPM1 version (stable-fixes).\n- soc: fsl: cpm1: qmc: Re-order probe() operations (stable-fixes).\n- soc: fsl: cpm1: qmc: Set the ret error code on platform_get_irq() failure (git-fixes).\n- soc: imx8m: Probe the SoC driver as platform driver (stable-fixes).\n- soc: qcom: Add check devm_kasprintf() returned value (stable-fixes).\n- soc: qcom: geni-se: Add M_TX_FIFO_NOT_EMPTY bit definition (git-fixes).\n- soc: qcom: geni-se: add GP_LENGTH/IRQ_EN_SET/IRQ_EN_CLEAR registers (git-fixes).\n- soc: qcom: socinfo: fix revision check in qcom_socinfo_probe() (git-fixes).\n- sound: usb: enable DSD output for ddHiFi TC44C (stable-fixes).\n- sound: usb: format: do not warn that raw DSD is unsupported (stable-fixes).\n- spi: aspeed: Fix an error handling path in aspeed_spi_[read|write]_user() (git-fixes).\n- spi: mpc52xx: Add cancel_work_sync before module remove (git-fixes).\n- stackdepot: rename pool_index to pool_index_plus_1 (git-fixes).\n- stackdepot: respect __GFP_NOLOCKDEP allocation flag (git-fixes).\n- staging: iio: ad9832: Correct phase range check (git-fixes).\n- staging: iio: ad9834: Correct phase range check (git-fixes).\n- sunrpc: clear XPRT_SOCK_UPD_TIMEOUT when reset transport (git-fixes).\n- sunrpc: fix one UAF issue caused by sunrpc kernel tcp socket (git-fixes).\n- sunrpc: handle -ENOTCONN in xs_tcp_setup_socket() (git-fixes).\n- svcrdma: Address an integer overflow (git-fixes).\n- svcrdma: fix miss destroy percpu_counter in svc_rdma_proc_init() (git-fixes).\n- swiotlb: Enforce page alignment in swiotlb_alloc() (git-fixes).\n- swiotlb: Reinstate page-alignment for mappings \u003e= PAGE_SIZE (git-fixes).\n- tdx: following fixup for mapping_level porting conflict (jsc#PED-6143).\n- tdx: init has_private_mem during tdx init (jsc#PED-6143).\n- the end of (the first phase of) TDX KVM patch series (jsc#PED-6143).\n- thermal/drivers/qcom/tsens-v1: Add support for MSM8937 tsens (stable-fixes).\n- thermal: of: fix OF node leak in of_thermal_zone_find() (git-fixes).\n- thunderbolt: Add support for Intel Lunar Lake (stable-fixes).\n- thunderbolt: Add support for Intel Panther Lake-M/P (stable-fixes).\n- tipc: fix NULL deref in cleanup_bearer() (bsc#1235433).\n- tools: hv: change permissions of NetworkManager configuration file (git-fixes).\n- tpm/eventlog: Limit memory allocations for event logs with excessive size (bsc#1233260 bsc#1233259 bsc#1232421).\n- tpm: Map the ACPI provided event log (bsc#1233260 bsc#1233259 bsc#1232421).\n- tpm_tis_spi: Release chip select when flow control fails (bsc#1234338)\n- tty: serial: 8250: Fix another runtime PM usage counter underflow (git-fixes).\n- tty: serial: kgdboc: Fix 8250_* kgdb over serial (git-fixes).\n- types: Introduce [us]128 (bsc#1220773).\n- ubifs: Correct the total block count by deducting journal reservation (git-fixes).\n- ubifs: authentication: Fix use-after-free in ubifs_tnc_end_commit (git-fixes).\n- udf: Fix lock ordering in udf_evict_inode() (bsc#1234238).\n- udf: fix uninit-value use in udf_get_fileshortad (bsc#1234243).\n- udf: prevent integer overflow in udf_bitmap_free_blocks() (bsc#1234239).\n- udf: refactor inode_bmap() to handle error (bsc#1234242).\n- udf: refactor udf_current_aext() to handle error (bsc#1234240).\n- udf: refactor udf_next_aext() to handle error (bsc#1234241).\n- udf: udftime: prevent overflow in udf_disk_stamp_to_time() (bsc#1234237).\n- usb-storage: Add max sectors quirk for Nokia 208 (stable-fixes).\n- usb: add support for new USB device ID 0x17EF:0x3098 for the r8152 driver (stable-fixes).\n- usb: cdns3-ti: Add workaround for Errata i2409 (stable-fixes).\n- usb: cdns3: Add quirk flag to enable suspend residency (stable-fixes).\n- usb: chipidea: add CI_HDRC_FORCE_VBUS_ACTIVE_ALWAYS flag (stable-fixes).\n- usb: chipidea: udc: handle USB Error Interrupt if IOC not set (stable-fixes).\n- usb: dwc2: Fix HCD port connection race (git-fixes).\n- usb: dwc2: Fix HCD resume (git-fixes).\n- usb: dwc2: gadget: Do not write invalid mapped sg entries into dma_desc with iommu enabled (stable-fixes).\n- usb: dwc2: hcd: Fix GetPortStatus \u0026 SetPortFeature (git-fixes).\n- usb: dwc3-am62: Disable autosuspend during remove (git-fixes).\n- usb: dwc3: ep0: Do not clear ep0 DWC3_EP_TRANSFER_STARTED (git-fixes).\n- usb: dwc3: ep0: Do not reset resource alloc flag (git-fixes).\n- usb: dwc3: ep0: Do not reset resource alloc flag (including ep0) (git-fixes).\n- usb: dwc3: gadget: Rewrite endpoint allocation flow (stable-fixes).\n- usb: dwc3: gadget: fix writing NYET threshold (git-fixes).\n- usb: dwc3: xilinx: make sure pipe clock is deselected in usb2 only mode (git-fixes).\n- usb: ehci-hcd: fix call balance of clocks handling routines (git-fixes).\n- usb: fix reference leak in usb_new_device() (git-fixes).\n- usb: gadget: configfs: Ignore trailing LF for user strings to cdev (git-fixes).\n- usb: gadget: f_fs: Remove WARN_ON in functionfs_bind (git-fixes).\n- usb: gadget: f_uac2: Fix incorrect setting of bNumEndpoints (git-fixes).\n- usb: gadget: u_serial: Disable ep before setting port to null to fix the crash caused by port being null (git-fixes).\n- usb: gadget: u_serial: Fix the issue that gs_start_io crashed due to accessing null pointer (git-fixes).\n- usb: host: max3421-hcd: Correctly abort a USB request (git-fixes).\n- usb: typec: anx7411: fix OF node reference leaks in anx7411_typec_switch_probe() (git-fixes).\n- usb: typec: anx7411: fix fwnode_handle reference leak (git-fixes).\n- usb: typec: tcpm/tcpci_maxim: fix error code in max_contaminant_read_resistance_kohm() (git-fixes).\n- usb: typec: use cleanup facility for 'altmodes_node' (stable-fixes).\n- vDPA/ifcvf: Fix pci_read_config_byte() return code handling (git-fixes).\n- vdpa/mlx5: Fix PA offset with unaligned starting iotlb map (git-fixes).\n- vdpa/mlx5: Fix suboptimal range on iotlb iteration (git-fixes).\n- vdpa: solidrun: Fix UB bug with devres (git-fixes).\n- vfs: fix readahead(2) on block devices (bsc#1234201).\n- vmscan,migrate: fix page count imbalance on node stats when demoting pages (git-fixes).\n- watchdog: apple: Actually flush writes after requesting watchdog restart (git-fixes).\n- watchdog: mediatek: Make sure system reset gets asserted in mtk_wdt_restart() (git-fixes).\n- watchdog: rti: of: honor timeout-sec property (git-fixes).\n- watchdog: rzg2l_wdt: Power on the watchdog domain in the restart handler (stable-fixes).\n- watchdog: rzg2l_wdt: Rely on the reset driver for doing proper reset (stable-fixes).\n- watchdog: rzg2l_wdt: Remove reset de-assert from probe (stable-fixes).\n- wifi: ath12k: fix atomic calls in ath12k_mac_op_set_bitrate_mask() (stable-fixes).\n- wifi: ath5k: add PCI ID for Arcadyan devices (git-fixes).\n- wifi: ath5k: add PCI ID for SX76X (git-fixes).\n- wifi: brcmfmac: Fix oops due to NULL pointer dereference in brcmf_sdiod_sglist_rw() (stable-fixes).\n- wifi: cfg80211: sme: init n_channels before channels[] access (git-fixes).\n- wifi: cw1200: Fix potential NULL dereference (git-fixes).\n- wifi: ipw2x00: libipw_rx_any(): fix bad alignment (stable-fixes).\n- wifi: iwlwifi: mvm: Use the sync timepoint API in suspend (stable-fixes).\n- wifi: mac80211: Add non-atomic station iterator (stable-fixes).\n- wifi: mac80211: clean up 'ret' in sta_link_apply_parameters() (stable-fixes).\n- wifi: mac80211: export ieee80211_purge_tx_queue() for drivers (stable-fixes).\n- wifi: mac80211: fix mbss changed flags corruption on 32 bit systems (stable-fixes).\n- wifi: mac80211: fix station NSS capability initialization order (git-fixes).\n- wifi: mac80211: init cnt before accessing elem in ieee80211_copy_mbssid_beacon (git-fixes).\n- wifi: mac80211: wake the queues in case of failure in resume (stable-fixes).\n- wifi: nl80211: fix NL80211_ATTR_MLO_LINK_ID off-by-one (git-fixes).\n- wifi: rtlwifi: Drastically reduce the attempts to read efuse in case of failures (stable-fixes).\n- wifi: rtw88: use ieee80211_purge_tx_queue() to purge TX skb (stable-fixes).\n- wifi: rtw89: check return value of ieee80211_probereq_get() for RNR (stable-fixes).\n- workqueue: Do not warn when cancelling WQ_MEM_RECLAIM work from !WQ_MEM_RECLAIM worker (bsc#1235416).\n- writeback, cgroup: switch inodes with dirty timestamps to release dying cgwbs (bsc#1234203).\n- x86,amd_iommu: Replace cmpxchg_double() (bsc#1220773).\n- x86,intel_iommu: Replace cmpxchg_double() (bsc#1220773).\n- x86/hyperv: Fix hv tsc page based sched_clock for hibernation (git-fixes).\n- x86/kexec: Reset TDX private memory on platforms with TDX erratum (jsc#PED-6143).\n- x86/kexec: do unconditional WBINVD for bare-metal in relocate_kernel() (jsc#PED-6143).\n- x86/kexec: do unconditional WBINVD for bare-metal in stop_this_cpu() (jsc#PED-6143).\n- x86/static-call: Remove early_boot_irqs_disabled check to fix Xen PVH dom0 (git-fixes).\n- x86/virt/tdx: Add TDX memory reset notifier to reset other private pages (jsc#PED-6143).\n- x86/virt/tdx: Exclude memory region hole within CMR as TDMR's reserved area (jsc#PED-6143).\n- x86/virt/tdx: Explicitly save/restore RBP for seamcall_saved_ret() (jsc#PED-6143).\n- x86/virt/tdx: Get information about TDX module and TDX-capable memory (jsc#PED-6143).\n- xfs: do not allocate COW extents when unsharing a hole (git-fixes).\n- xfs: fix sb_spino_align checks for large fsblock sizes (git-fixes).\n- xfs: remove unknown compat feature check in superblock write validation (git-fixes).\n- xfs: return from xfs_symlink_verify early on V4 filesystems (git-fixes).\n- xfs: sb_spino_align is not verified (git-fixes).\n- xhci: Add usb cold attach (CAS) as a reason to resume root hub (git-fixes).\n- xhci: Allow RPM on the USB controller (1022:43f7) by default (stable-fixes).\n- xhci: fix possible null pointer deref during xhci urb enqueue (git-fixes).\n","status":"published","published":"2025-01-29T16:11:29Z","modified":"2026-02-04T02:27:31.070473Z","updated_at":"2026-11-02T15:53:57.111474Z"},{"id":"SUSE-SU-2025:0428-1","title":"Security update for the Linux Kernel","description":"\nThe SUSE Linux Enterprise 15 SP6 Azure kernel was updated to receive various security bugfixes.\n\n\nThe following security bugs were fixed:\n\n- CVE-2023-52489: mm/sparsemem: fix race in accessing memory_section-\u003eusage (bsc#1221326).\n- CVE-2024-45828: i3c: mipi-i3c-hci: Mask ring interrupts before ring stop request (bsc#1235705).\n- CVE-2024-48881: bcache: revert replacing IS_ERR_OR_NULL with IS_ERR again (bsc#1235727).\n- CVE-2024-49948: net: add more sanity checks to qdisc_pkt_len_init() (bsc#1232161).\n- CVE-2024-49951: Bluetooth: MGMT: Fix possible crash on mgmt_index_removed (bsc#1232158).\n- CVE-2024-49978: gso: fix udp gso fraglist segmentation after pull from frag_list (bsc#1232101).\n- CVE-2024-49998: net: dsa: improve shutdown sequence (bsc#1232087).\n- CVE-2024-50151: smb: client: fix OOBs when building SMB2_IOCTL request (bsc#1233055).\n- CVE-2024-50199: mm/swapfile: skip HugeTLB pages for unuse_vma (bsc#1233112).\n- CVE-2024-50251: netfilter: nft_payload: sanitize offset and length before calling skb_checksum() (bsc#1233248).\n- CVE-2024-50258: net: fix crash when config small gso_max_size/gso_ipv4_max_size (bsc#1233221).\n- CVE-2024-50299: sctp: properly validate chunk size in sctp_sf_ootb() (bsc#1233488).\n- CVE-2024-50304: ipv4: ip_tunnel: Fix suspicious RCU usage warning in ip_tunnel_find() (bsc#1233522).\n- CVE-2024-53091: bpf: Add sk_is_inet and IS_ICSK check in tls_sw_has_ctx_tx/rx (bsc#1233638).\n- CVE-2024-53164: net: sched: fix ordering of qlen adjustment (bsc#1234863).\n- CVE-2024-53170: block: fix uaf for flush rq while iterating tags (bsc#1234888).\n- CVE-2024-53172: ubi: fastmap: Fix duplicate slab cache names while attaching (bsc#1234898).\n- CVE-2024-53175: ipc: fix memleak if msg_init_ns failed in create_ipc_ns (bsc#1234893).\n- CVE-2024-53185: smb: client: fix NULL ptr deref in crypto_aead_setkey() (bsc#1234901).\n- CVE-2024-53187: io_uring: check for overflows in io_pin_pages (bsc#1234947).\n- CVE-2024-53195: KVM: arm64: Get rid of userspace_irqchip_in_use (bsc#1234957).\n- CVE-2024-53196: KVM: arm64: Do not retire aborted MMIO instruction (bsc#1234906).\n- CVE-2024-53198: xen: Fix the issue of resource not being properly released in xenbus_dev_probe() (bsc#1234923).\n- CVE-2024-53203: usb: typec: fix potential array underflow in ucsi_ccg_sync_control() (bsc#1235001).\n- CVE-2024-53227: scsi: bfa: Fix use-after-free in bfad_im_module_exit() (bsc#1235011).\n- CVE-2024-53232: iommu/s390: Implement blocking domain (bsc#1235050).\n- CVE-2024-53236: xsk: Free skb when TX metadata options are invalid (bsc#1235000).\n- CVE-2024-53685: ceph: give up on paths longer than PATH_MAX (bsc#1235720).\n- CVE-2024-55639: net: renesas: rswitch: avoid use-after-put for a device tree node (bsc#1235737).\n- CVE-2024-55881: KVM: x86: Play nice with protected guests in complete_hypercall_exit() (bsc#1235745).\n- CVE-2024-56372: net: tun: fix tun_napi_alloc_frags() (bsc#1235753).\n- CVE-2024-56568: iommu/arm-smmu: Defer probe of clients after smmu device bound (bsc#1235032).\n- CVE-2024-56569: ftrace: Fix regression with module command in stack_trace_filter (bsc#1235031).\n- CVE-2024-56570: ovl: Filter invalid inodes with missing lookup function (bsc#1235035).\n- CVE-2024-56588: scsi: hisi_sas: Create all dump files during debugfs initialization (bsc#1235123).\n- CVE-2024-56589: scsi: hisi_sas: Add cond_resched() for no forced preemption model (bsc#1235241).\n- CVE-2024-56600: net: inet6: do not leave a dangling sk pointer in inet6_create() (bsc#1235217).\n- CVE-2024-56601: net: inet: do not leave a dangling sk pointer in inet_create() (bsc#1235230).\n- CVE-2024-56602: net: ieee802154: do not leave a dangling sk pointer in ieee802154_create() (bsc#1235521).\n- CVE-2024-56603: net: af_can: do not leave a dangling sk pointer in can_create() (bsc#1235415).\n- CVE-2024-56605: Bluetooth: L2CAP: do not leave dangling sk pointer on error in l2cap_sock_create() (bsc#1235061).\n- CVE-2024-56608: drm/amd/display: Fix out-of-bounds access in 'dcn21_link_encoder_create' (bsc#1235487).\n- CVE-2024-56610: kcsan: Turn report_filterlist_lock into a raw_spinlock (bsc#1235390).\n- CVE-2024-56611: mm/mempolicy: fix migrate_to_node() assuming there is at least one VMA in a MM (bsc#1235391).\n- CVE-2024-56614: xsk: fix OOB map writes when deleting elements (bsc#1235424).\n- CVE-2024-56615: bpf: fix OOB devmap writes when deleting elements (bsc#1235426).\n- CVE-2024-56617: cacheinfo: Allocate memory during CPU hotplug if not done from the primary CPU (bsc#1235429).\n- CVE-2024-56620: scsi: ufs: qcom: Only free platform MSIs when ESI is enabled (bsc#1235227).\n- CVE-2024-56622: scsi: ufs: core: sysfs: Prevent div by zero (bsc#1235251).\n- CVE-2024-56631: scsi: sg: Fix slab-use-after-free read in sg_release() (bsc#1235480).\n- CVE-2024-56635: net: avoid potential UAF in default_operstate() (bsc#1235519).\n- CVE-2024-56636: geneve: do not assume mac header is set in geneve_xmit_skb() (bsc#1235520).\n- CVE-2024-56637: netfilter: ipset: Hold module reference while requesting a module (bsc#1235523).\n- CVE-2024-56641: net/smc: initialize close_work early to avoid warning (bsc#1235526).\n- CVE-2024-56643: dccp: Fix memory leak in dccp_feat_change_recv (bsc#1235132).\n- CVE-2024-56648: net: hsr: avoid potential out-of-bound access in fill_frame_info() (bsc#1235451).\n- CVE-2024-56649: net: enetc: Do not configure preemptible TCs if SIs do not support (bsc#1235449).\n- CVE-2024-56650: netfilter: x_tables: fix LED ID check in led_tg_check() (bsc#1235430).\n- CVE-2024-56656: bnxt_en: Fix aggregation ID mask to prevent oops on 5760X chips (bsc#1235444).\n- CVE-2024-56659: net: lapb: increase LAPB_HEADER_LEN (bsc#1235439).\n- CVE-2024-56660: net/mlx5: DR, prevent potential error pointer dereference (bsc#1235437).\n- CVE-2024-56664: bpf, sockmap: Fix race between element replace and close() (bsc#1235249).\n- CVE-2024-56665: bpf,perf: Fix invalid prog_array access in perf_event_detach_bpf_prog (bsc#1235489).\n- CVE-2024-56675: bpf: Fix UAF via mismatching bpf_prog/attachment RCU flavors (bsc#1235555).\n- CVE-2024-56679: octeontx2-pf: handle otx2_mbox_get_rsp errors in otx2_common.c (bsc#1235498).\n- CVE-2024-56693: brd: defer automatic disk creation until module initialization succeeds (bsc#1235418).\n- CVE-2024-56694: bpf: fix recursive lock when verdict program return SK_PASS (bsc#1235412).\n- CVE-2024-56704: 9p/xen: fix release of IRQ (bsc#1235584).\n- CVE-2024-56707: octeontx2-pf: handle otx2_mbox_get_rsp errors in otx2_dmac_flt.c (bsc#1235545).\n- CVE-2024-56708: EDAC/igen6: Avoid segmentation fault on module unload (bsc#1235564).\n- CVE-2024-56712: udmabuf: fix memory leak on last export_udmabuf() error path (bsc#1235565).\n- CVE-2024-56715: ionic: Fix netdev notifier unregister on failure (bsc#1235612).\n- CVE-2024-56716: netdevsim: prevent bad user input in nsim_dev_health_break_write() (bsc#1235587).\n- CVE-2024-56725: octeontx2-pf: handle otx2_mbox_get_rsp errors in otx2_dcbnl.c (bsc#1235578).\n- CVE-2024-56726: octeontx2-pf: handle otx2_mbox_get_rsp errors in cn10k.c (bsc#1235582).\n- CVE-2024-56727: octeontx2-pf: handle otx2_mbox_get_rsp errors in otx2_flows.c (bsc#1235583).\n- CVE-2024-56728: octeontx2-pf: handle otx2_mbox_get_rsp errors in otx2_ethtool.c (bsc#1235656).\n- CVE-2024-56729: smb: Initialize cfid-\u003etcon before performing network ops (bsc#1235503).\n- CVE-2024-56747: scsi: qedi: Fix a possible memory leak in qedi_alloc_and_init_sb() (bsc#1234934).\n- CVE-2024-56748: scsi: qedf: Fix a possible memory leak in qedf_alloc_and_init_sb() (bsc#1235627).\n- CVE-2024-56759: btrfs: fix use-after-free when COWing tree bock and tracing is enabled (bsc#1235645).\n- CVE-2024-56763: tracing: Prevent bad count for tracing_cpumask_write (bsc#1235638).\n- CVE-2024-56774: btrfs: add a sanity check for btrfs root in btrfs_search_slot() (bsc#1235653).\n- CVE-2024-56775: drm/amd/display: Fix handling of plane refcount (bsc#1235657).\n- CVE-2024-57791: net/smc: check return value of sock_recvmsg when draining clc data (bsc#1235759).\n- CVE-2024-57793: virt: tdx-guest: Just leak decrypted memory on unrecoverable errors (bsc#1235768).\n- CVE-2024-57795: RDMA/rxe: Remove the direct link to net_device (bsc#1235906).\n- CVE-2024-57801: net/mlx5e: Skip restore TC rules for vport rep without loaded flag (bsc#1235940).\n- CVE-2024-57802: netrom: check buffer length before accessing it (bsc#1235941).\n- CVE-2024-57804: scsi: mpi3mr: Fix corrupt config pages PHY state is switched in sysfs (bsc#1235779).\n- CVE-2024-57809: PCI: imx6: Fix suspend/resume support on i.MX6QDL (bsc#1235793).\n- CVE-2024-57838: s390/entry: Mark IRQ entries to fix stack depot warnings (bsc#1235798).\n- CVE-2024-57857: RDMA/siw: Remove direct link to net_device (bsc#1235946).\n- CVE-2024-57884: mm: vmscan: account for free pages to prevent infinite Loop in throttle_direct_reclaim() (bsc#1235948).\n- CVE-2024-57892: ocfs2: fix slab-use-after-free due to dangling pointer dqi_priv (bsc#1235964).\n- CVE-2024-57896: btrfs: flush delalloc workers queue before stopping cleaner kthread during unmount (bsc#1235965).\n- CVE-2024-57903: net: restrict SO_REUSEPORT to inet sockets (bsc#1235967).\n- CVE-2024-57917: topology: Keep the cpumask unchanged when printing cpumap (bsc#1236127).\n- CVE-2024-57929: dm array: fix releasing a faulty array block twice in dm_array_cursor_end (bsc#1236096).\n- CVE-2024-57931: selinux: ignore unknown extended permissions (bsc#1236192).\n- CVE-2024-57932: gve: guard XDP xmit NDO on existence of xdp queues (bsc#1236190).\n- CVE-2024-57933: gve: guard XSK operations on the existence of queues (bsc#1236178).\n- CVE-2024-57938: net/sctp: Prevent autoclose integer overflow in sctp_association_init() (bsc#1236182).\n- CVE-2024-57946: virtio-blk: do not keep queue frozen during system suspend (bsc#1236247).\n- CVE-2025-21632: x86/fpu: Ensure shadow stack is active before 'getting' registers (bsc#1236106).\n- CVE-2025-21649: net: hns3: fix kernel crash when 1588 is sent on HIP08 devices (bsc#1236143).\n- CVE-2025-21650: net: hns3: fixed hclge_fetch_pf_reg accesses bar space out of bounds issue (bsc#1236144).\n- CVE-2025-21651: net: hns3: do not auto enable misc vector (bsc#1236145).\n- CVE-2025-21652: ipvlan: Fix use-after-free in ipvlan_get_iflink() (bsc#1236160).\n- CVE-2025-21653: net_sched: cls_flow: validate TCA_FLOW_RSHIFT attribute (bsc#1236161).\n- CVE-2025-21655: io_uring/eventfd: ensure io_eventfd_signal() defers another RCU period (bsc#1236163).\n- CVE-2025-21662: net/mlx5: Fix variable not being completed when function returns (bsc#1236198).\n- CVE-2025-21663: net: stmmac: dwmac-tegra: Read iommu stream id from device tree (bsc#1236260).\n- CVE-2025-21664: dm thin: make get_first_thin use rcu-safe list first function (bsc#1236262).\n- CVE-2025-21674: net/mlx5e: Fix inversion dependency warning while enabling IPsec tunnel (bsc#1236688).\n- CVE-2025-21676: net: fec: handle page_pool_dev_alloc_pages error (bsc#1236696).\n- CVE-2025-21678: gtp: Destroy device along with udp socket's netns dismantle (bsc#1236698).\n- CVE-2025-21682: eth: bnxt: always recalculate features after XDP clearing, fix null-deref (bsc#1236703).\n\nThe following non-security bugs were fixed:\n\n- ACPI/IORT: Add PMCG platform information for HiSilicon HIP09A (stable-fixes).\n- ACPI/IORT: Add PMCG platform information for HiSilicon HIP10/11 (stable-fixes).\n- ACPI: PCC: Add PCC shared memory region command and status bitfields (stable-fixes).\n- ACPI: fan: cleanup resources in the error path of .probe() (git-fixes).\n- ACPI: resource: Add Asus Vivobook X1504VAP to irq1_level_low_skip_override[] (stable-fixes).\n- ACPI: resource: Add TongFang GM5HG0A to irq1_edge_low_force_override[] (stable-fixes).\n- ACPI: resource: acpi_dev_irq_override(): Check DMI match last (stable-fixes).\n- ALSA: hda/realtek - Add support for ASUS Zen AIO 27 Z272SD_A272SD audio (stable-fixes).\n- ALSA: hda/realtek - Fixed headphone distorted sound on Acer Aspire A115-31 laptop (git-fixes).\n- ALSA: hda/realtek: Add new alc2xx-fixup-headset-mic model (stable-fixes).\n- ALSA: hda/realtek: Add support for Ayaneo System using CS35L41 HDA (stable-fixes).\n- ALSA: hda/realtek: Add support for Galaxy Book2 Pro (NP950XEE) (stable-fixes).\n- ALSA: hda/realtek: Enable Mute LED on HP Laptop 14s-fq1xxx (stable-fixes).\n- ALSA: hda/realtek: Enable headset mic on Positivo C6400 (stable-fixes).\n- ALSA: hda/realtek: Workaround for resume on Dell Venue 11 Pro 7130 (bsc#1235686).\n- ALSA: hda: Fix headset detection failure due to unstable sort (git-fixes).\n- ALSA: ump: Use guard() for locking (stable-fixes).\n- ALSA: usb-audio: Add delay quirk for USB Audio Device (stable-fixes).\n- ALSA: usb-audio: Add delay quirk for iBasso DC07 Pro (stable-fixes).\n- ASoC: Intel: avs: Fix theoretical infinite loop (git-fixes).\n- ASoC: acp: Support microphone from Lenovo Go S (stable-fixes).\n- ASoC: mediatek: disable buffer pre-allocation (stable-fixes).\n- ASoC: rockchip: i2s_tdm: Re-add the set_sysclk callback (git-fixes).\n- ASoC: rt722: add delay time to wait for the calibration procedure (stable-fixes).\n- ASoC: samsung: Add missing depends on I2C (git-fixes).\n- ASoC: samsung: Add missing selects for MFD_WM8994 (stable-fixes).\n- ASoC: sun4i-spdif: Add clock multiplier settings (git-fixes).\n- ASoC: wm8994: Add depends on MFD core (stable-fixes).\n- Bluetooth: Add support ITTIM PE50-M75C (stable-fixes).\n- Bluetooth: L2CAP: accept zero as a special value for MTU auto-selection (git-fixes).\n- Bluetooth: L2CAP: handle NULL sock pointer in l2cap_sock_alloc (git-fixes).\n- Bluetooth: MGMT: Fix Add Device to responding before completing (git-fixes).\n- Bluetooth: btnxpuart: Fix driver sending truncated data (git-fixes).\n- Bluetooth: btnxpuart: Fix glitches seen in dual A2DP streaming (git-fixes).\n- Bluetooth: btusb: Add USB HW IDs for MT7921/MT7922/MT7925 (stable-fixes).\n- Bluetooth: btusb: Add new VID/PID 0489/e111 for MT7925 (stable-fixes).\n- Bluetooth: btusb: Add new VID/PID 13d3/3602 for MT7925 (stable-fixes).\n- Bluetooth: btusb: add callback function in btusb suspend/resume (stable-fixes).\n- Bluetooth: btusb: mediatek: add callback function in btusb_disconnect (stable-fixes).\n- Bluetooth: hci_sync: Fix not setting Random Address when required (git-fixes).\n- EDAC/{i10nm,skx,skx_common}: Support UV systems (bsc#1234693).\n- HID: core: Fix assumption that Resolution Multipliers must be in Logical Collections (git-fixes).\n- HID: fix generic desktop D-Pad controls (git-fixes).\n- HID: hid-sensor-hub: do not use stale platform-data on remove (git-fixes).\n- HID: hid-thrustmaster: Fix warning in thrustmaster_probe by adding endpoint check (git-fixes).\n- HID: multitouch: fix support for Goodix PID 0x01e9 (git-fixes).\n- Input: atkbd - map F23 key to support default copilot shortcut (stable-fixes).\n- Input: bbnsm_pwrkey - add remove hook (git-fixes).\n- Input: bbnsm_pwrkey - fix missed key press after suspend (git-fixes).\n- Input: davinci-keyscan - remove leftover header (git-fixes).\n- Input: xpad - add QH Electronics VID/PID (stable-fixes).\n- Input: xpad - add support for Nacon Evol-X Xbox One Controller (stable-fixes).\n- Input: xpad - add support for Nacon Pro Compact (stable-fixes).\n- Input: xpad - add support for wooting two he (arm) (stable-fixes).\n- Input: xpad - add unofficial Xbox 360 wireless receiver clone (stable-fixes).\n- Input: xpad - improve name of 8BitDo controller 2dc8:3106 (stable-fixes).\n- KVM: SVM: Allow guest writes to set MSR_AMD64_DE_CFG bits (bsc#1234635).\n- KVM: s390: Reject KVM_SET_GSI_ROUTING on ucontrol VMs (git-fixes bsc#1235776).\n- KVM: s390: Reject setting flic pfault attributes on ucontrol VMs (git-fixes bsc#1235777).\n- KVM: s390: vsie: fix virtual/physical address in unpin_scb() (git-fixes bsc#1235778).\n- NFC: nci: Add bounds checking in nci_hci_create_pipe() (git-fixes).\n- NFSv4.2: fix COPY_NOTIFY xdr buf size calculation (git-fixes).\n- NFSv4.2: mark OFFLOAD_CANCEL MOVEABLE (git-fixes).\n- PCI: Avoid putting some root ports into D3 on TUXEDO Sirius Gen1 (git-fixes).\n- PCI: dwc: Always stop link in the dw_pcie_suspend_noirq (git-fixes).\n- PCI: dwc: ep: Prevent changing BAR size/flags in pci_epc_set_bar() (git-fixes).\n- PCI: dwc: ep: Write BAR_MASK before iATU registers in pci_epc_set_bar() (git-fixes).\n- PCI: endpoint: Destroy the EPC device in devm_pci_epc_destroy() (git-fixes).\n- PCI: endpoint: Finish virtual EP removal in pci_epf_remove_vepf() (git-fixes).\n- PCI: endpoint: pci-epf-test: Fix check for DMA MEMCPY test (git-fixes).\n- PCI: endpoint: pci-epf-test: Set dma_chan_rx pointer to NULL on error (git-fixes).\n- PCI: imx6: Deassert apps_reset in imx_pcie_deassert_core_reset() (git-fixes).\n- PCI: imx6: Skip controller_id generation logic for i.MX7D (git-fixes).\n- PCI: microchip: Set inbound address translation for coherent or non-coherent mode (git-fixes).\n- PCI: rcar-ep: Fix incorrect variable used when calling devm_request_mem_region() (git-fixes).\n- PM: hibernate: Add error handling for syscore_suspend() (git-fixes).\n- RDMA/bnxt_re: Add send queue size check for variable wqe (git-fixes)\n- RDMA/bnxt_re: Fix MSN table size for variable wqe mode (git-fixes)\n- RDMA/bnxt_re: Fix max SGEs for the Work Request (git-fixes)\n- RDMA/bnxt_re: Fix the max WQE size for static WQE support (git-fixes)\n- RDMA/bnxt_re: Fix the max WQEs used in Static WQE mode (git-fixes)\n- RDMA/bnxt_re: Fix to drop reference to the mmap entry in case of error (git-fixes)\n- RDMA/bnxt_re: Fix to export port num to ib_query_qp (git-fixes)\n- RDMA/mlx4: Avoid false error about access to uninitialized gids array (git-fixes)\n- RDMA/mlx5: Fix a race for an ODP MR which leads to CQE with error (git-fixes)\n- RDMA/mlx5: Fix implicit ODP use after free (git-fixes)\n- RDMA/mlx5: Fix indirect mkey ODP page count (git-fixes)\n- RDMA/rxe: Fix mismatched max_msg_sz (git-fixes)\n- RDMA/rxe: Fix the warning '__rxe_cleanup+0x12c/0x170 [rdma_rxe]' (git-fixes)\n- RDMA/srp: Fix error handling in srp_add_port (git-fixes)\n- Disable 'ocfs2: fix UBSAN warning in ocfs2_verify_volume()' (bsc#1236138).\n- Remove 'idpf: fix memory leaks and crashes while performing a soft reset' fix (bsc#1236628).\n- Remove 'media: uvcvideo: Require entities to have a non-zero unique ID' fix (bsc#1235894).\n- Revert 'HID: multitouch: Add support for lenovo Y9000P Touchpad' (stable-fixes).\n- Revert 'drm/i915/dpt: Make DPT object unshrinkable' (stable-fixes).\n- Revert 'mtd: spi-nor: core: replace dummy buswidth from addr to data' (git-fixes).\n- Revert 'usb: gadget: u_serial: Disable ep before setting port to null to fix the crash caused by port being null' (stable-fixes).\n- USB: core: Disable LPM only for non-suspended ports (git-fixes).\n- USB: serial: cp210x: add Phoenix Contact UPS Device (stable-fixes).\n- USB: serial: option: add MeiG Smart SRM815 (stable-fixes).\n- USB: serial: option: add Neoway N723-EA support (stable-fixes).\n- USB: serial: quatech2: fix null-ptr-deref in qt2_process_read_urb() (git-fixes).\n- USB: usblp: return error when setting unsupported protocol (git-fixes).\n- VFS: use system_unbound_wq for delayed_mntput (bsc#1234683).\n- VMCI: fix reference to ioctl-number.rst (git-fixes).\n- afs: Fix EEXIST error returned from afs_rmdir() to be ENOTEMPTY (git-fixes).\n- afs: Fix cleanup of immediately failed async calls (git-fixes).\n- afs: Fix directory format encoding struct (git-fixes).\n- afs: Fix the fallback handling for the YFS.RemoveFile2 RPC call (git-fixes).\n- afs: Fix the maximum cell name length (git-fixes).\n- arm64/sme: Move storage of reg_smidr to __cpuinfo_store_cpu() (git-fixes)\n- arm64: Filter out SVE hwcaps when FEAT_SVE isn't implemented (git-fixes)\n- arm64: Kconfig: Make SME depend on BROKEN for now (git-fixes bsc#1236245).\n- arm64: dts: rockchip: Add sdmmc/sdio/emmc reset controls for RK3328 (git-fixes)\n- arm64: dts: rockchip: add hevc power domain clock to rk3328 (git-fixes).\n- arm64: dts: rockchip: increase gmac rx_delay on rk3399-puma (git-fixes)\n- arm64: ptrace: fix partial SETREGSET for NT_ARM_TAGGED_ADDR_CTRL (git-fixes).\n- arm64: tegra: Disable Tegra234 sce-fabric node (git-fixes)\n- arm64: tegra: Fix Tegra234 PCIe interrupt-map (git-fixes)\n- arm64: tegra: Fix typo in Tegra234 dce-fabric compatible (git-fixes)\n- ata: libata-core: Set ATA_QCFLAG_RTF_FILLED in fill_result_tf() (stable-fixes).\n- bnxt_en: Fix GSO type for HW GRO packets on 5750X chips (git-fixes)\n- btrfs: fix use-after-free in btrfs_encoded_read_endio() (bsc#1235445).\n- btrfs: fix use-after-free waiting for encoded read endios (bsc#1235445).\n- bus: mhi: host: Free mhi_buf vector inside mhi_alloc_bhie_table() (git-fixes).\n- ceph: improve error handling and short/overflow-read logic in __ceph_sync_read() (bsc#1228592).\n- cleanup: Add conditional guard support (stable-fixes).\n- cleanup: Adjust scoped_guard() macros to avoid potential warning (stable-fixes).\n- cleanup: Remove address space of returned pointer (git-fixes).\n- cpufreq: ACPI: Fix max-frequency computation (git-fixes).\n- cpufreq: Do not unregister cpufreq cooling on CPU hotplug (git-fixes).\n- cpufreq: amd-pstate: remove global header file (git-fixes).\n- cpufreq: intel_pstate: Check turbo_is_disabled() in store_no_turbo() (bsc#1234619).\n- cpufreq: intel_pstate: Do not update global.turbo_disabled after initialization (bsc#1234619).\n- cpufreq: intel_pstate: Drop redundant locking from intel_pstate_driver_cleanup() (bsc#1234619).\n- cpufreq: intel_pstate: Fix unchecked HWP MSR access (bsc#1234619).\n- cpufreq: intel_pstate: Fold intel_pstate_max_within_limits() into caller (bsc#1234619).\n- cpufreq: intel_pstate: Get rid of unnecessary READ_ONCE() annotations (bsc#1234619).\n- cpufreq: intel_pstate: Make hwp_notify_lock a raw spinlock (git-fixes).\n- cpufreq: intel_pstate: Read global.no_turbo under READ_ONCE() (bsc#1234619).\n- cpufreq: intel_pstate: Rearrange show_no_turbo() and store_no_turbo() (bsc#1234619).\n- cpufreq: intel_pstate: Refine computation of P-state for given frequency (bsc#1234619).\n- cpufreq: intel_pstate: Replace three global.turbo_disabled checks (bsc#1234619).\n- cpufreq: intel_pstate: Revise global turbo disable check (bsc#1234619).\n- cpufreq: intel_pstate: Simplify spinlock locking (bsc#1234619).\n- cpufreq: intel_pstate: Update the maximum CPU frequency consistently (bsc#1234619).\n- cpufreq: intel_pstate: Use HWP to initialize ITMT if CPPC is missing (git-fixes).\n- cpufreq: intel_pstate: Use __ro_after_init for three variables (bsc#1234619).\n- cpufreq: intel_pstate: Wait for canceled delayed work to complete (bsc#1234619).\n- cpufreq: intel_pstate: fix pstate limits enforcement for adjust_perf call back (git-fixes).\n- cpuidle: Avoid potential overflow in integer multiplication (git-fixes).\n- cpupower: fix TSC MHz calculation (git-fixes).\n- crypto: caam - use JobR's space to access page 0 regs (git-fixes).\n- crypto: ecc - Prevent ecc_digits_from_bytes from reading too many bytes (git-fixes).\n- crypto: ecdsa - Avoid signed integer overflow on signature decoding (stable-fixes).\n- crypto: ecdsa - Convert byte arrays with key coordinates to digits (stable-fixes).\n- crypto: ecdsa - Rename keylen to bufsize where necessary (stable-fixes).\n- crypto: ecdsa - Use ecc_digits_from_bytes to convert signature (stable-fixes).\n- crypto: iaa - Fix IAA disabling that occurs when sync_mode is set to 'async' (git-fixes).\n- crypto: ixp4xx - fix OF node reference leaks in init_ixp_crypto() (git-fixes).\n- crypto: qce - fix goto jump in error path (git-fixes).\n- crypto: qce - fix priority to be less than ARMv8 CE (git-fixes).\n- crypto: qce - unregister previously registered algos in error path (git-fixes).\n- devcoredump: cleanup some comments (git-fixes).\n- dlm: fix possible lkb_resource null dereference (git-fixes).\n- dmaengine: ti: edma: fix OF node reference leaks in edma_driver (git-fixes).\n- docs: media: update location of the media patches (stable-fixes).\n- docs: power: Fix footnote reference for Toshiba Satellite P10-554 (git-fixes).\n- driver core: class: Fix wild pointer dereferences in API class_dev_iter_next() (git-fixes).\n- drivers/card_reader/rtsx_usb: Restore interrupt based detection (git-fixes).\n- drm/amd/display: Add check for granularity in dml ceil/floor helpers (stable-fixes).\n- drm/amd/display: Fix DSC-re-computing (stable-fixes).\n- drm/amd/display: Fix incorrect DSC recompute trigger (stable-fixes).\n- drm/amd/display: Use HW lock mgr for PSR1 (stable-fixes).\n- drm/amd/display: increase MAX_SURFACES to the value supported by hw (stable-fixes).\n- drm/amd/pm: Fix an error handling path in vega10_enable_se_edc_force_stall_config() (git-fixes).\n- drm/amdgpu/vcn: reset fw_shared under SRIOV (git-fixes).\n- drm/amdgpu: Fix potential NULL pointer dereference in atomctrl_get_smc_sclk_range_table (git-fixes).\n- drm/amdgpu: always sync the GFX pipe on ctx switch (stable-fixes).\n- drm/amdgpu: simplify return statement in amdgpu_ras_eeprom_init (git-fixes).\n- drm/amdgpu: tear down ttm range manager for doorbell in amdgpu_ttm_fini() (git-fixes).\n- drm/amdkfd: Correct the migration DMA map direction (stable-fixes).\n- drm/amdkfd: fixed page fault when enable MES shader debugger (git-fixes).\n- drm/bridge: it6505: Change definition of AUX_FIFO_MAX_SIZE (git-fixes).\n- drm/etnaviv: Fix page property being used for non writecombine buffers (git-fixes).\n- drm/i915/fb: Relax clear color alignment to 64 bytes (stable-fixes).\n- drm/mediatek: Add return value check when reading DPCD (git-fixes).\n- drm/mediatek: Add support for 180-degree rotation in the display driver (git-fixes).\n- drm/mediatek: Fix YCbCr422 color format issue for DP (git-fixes).\n- drm/mediatek: Fix mode valid issue for dp (git-fixes).\n- drm/mediatek: Set private-\u003eall_drm_private[i]-\u003edrm to NULL if mtk_drm_bind returns err (git-fixes).\n- drm/mediatek: mtk_dsi: Add registers to pdata to fix MT8186/MT8188 (git-fixes).\n- drm/mediatek: stop selecting foreign drivers (git-fixes).\n- drm/msm/dp: set safe_to_exit_level before printing it (git-fixes).\n- drm/msm/dpu: link DSPP_2/_3 blocks on SC8180X (git-fixes).\n- drm/msm/dpu: link DSPP_2/_3 blocks on SM8150 (git-fixes).\n- drm/msm/dpu: link DSPP_2/_3 blocks on SM8250 (git-fixes).\n- drm/msm/dpu: link DSPP_2/_3 blocks on SM8350 (git-fixes).\n- drm/msm/dpu: link DSPP_2/_3 blocks on SM8550 (git-fixes).\n- drm/msm: Check return value of of_dma_configure() (git-fixes).\n- drm/msm: do not clean up priv-\u003ekms prematurely (git-fixes).\n- drm/rcar-du: dsi: Fix PHY lock bit check (git-fixes).\n- drm/rockchip: cdn-dp: Use drm_connector_helper_hpd_irq_event() (git-fixes).\n- drm/rockchip: vop2: Check linear format for Cluster windows on rk3566/8 (git-fixes).\n- drm/rockchip: vop2: Fix cluster windows alpha ctrl regsiters offset (git-fixes).\n- drm/rockchip: vop2: Fix the mixer alpha setup for layer 0 (git-fixes).\n- drm/tidss: Clear the interrupt status for interrupts being disabled (git-fixes).\n- drm/tidss: Fix issue in irq handling causing irq-flood issue (git-fixes).\n- drm/v3d: Assign job pointer to NULL before signaling the fence (git-fixes).\n- drm/v3d: Ensure job pointer is set to NULL after job completion (git-fixes).\n- drm/v3d: Stop active perfmon if it is being destroyed (git-fixes).\n- drm/vmwgfx: Add new keep_resv BO param (git-fixes).\n- exfat: ensure that ctime is updated whenever the mtime is (git-fixes).\n- exfat: fix the infinite loop in __exfat_free_cluster() (git-fixes).\n- exfat: fix the infinite loop in exfat_readdir() (git-fixes).\n- fbdev: omapfb: Fix an OF node leak in dss_of_port_get_parent_device() (git-fixes).\n- genirq: Make handle_enforce_irqctx() unconditionally available (git-fixes).\n- genksyms: fix memory leak when the same symbol is added from source (git-fixes).\n- genksyms: fix memory leak when the same symbol is read from *.symref file (git-fixes).\n- gfs2: Truncate address space when flipping GFS2_DIF_JDATA flag (git-fixes).\n- gpio: mxc: remove dead code after switch to DT-only (git-fixes).\n- gpio: xilinx: Convert gpio_lock to raw spinlock (git-fixes).\n- gtp: Use for_each_netdev_rcu() in gtp_genl_dump_pdp() (git-fixes).\n- hwmon: (drivetemp) Fix driver producing garbage data when SCSI errors occur (git-fixes).\n- hwmon: (drivetemp) Set scsi command timeout to 10s (stable-fixes).\n- hwmon: (tmp513) Fix division of negative numbers (git-fixes).\n- hyperv: Do not overlap the hvcall IO areas in get_vtl() (git-fixes).\n- i2c: core: fix reference leak in i2c_register_adapter() (git-fixes).\n- i2c: i801: Add support for Intel Arrow Lake-H (stable-fixes).\n- i2c: i801: Add support for Intel Panther Lake (stable-fixes).\n- i2c: mux: demux-pinctrl: check initial mux selection, too (git-fixes).\n- i2c: rcar: fix NACK handling when being a target (git-fixes).\n- i2c: xgene-slimpro: Migrate to use generic PCC shmem related macros (stable-fixes).\n- ibmvnic: Free any outstanding tx skbs during scrq reset (bsc#1226980).\n- ieee802154: ca8210: Add missing check for kfifo_alloc() in ca8210_probe() (git-fixes).\n- iio: adc: ad7124: Disable all channels at probe time (git-fixes).\n- iio: adc: ad_sigma_delta: Handle CS assertion as intended in ad_sd_read_reg_raw() (git-fixes).\n- iio: adc: at91: call input_free_device() on allocated iio_dev (git-fixes).\n- iio: adc: rockchip_saradc: fix information leak in triggered buffer (git-fixes).\n- iio: adc: ti-ads124s08: Use gpiod_set_value_cansleep() (git-fixes).\n- iio: adc: ti-ads8688: fix information leak in triggered buffer (git-fixes).\n- iio: dummy: iio_simply_dummy_buffer: fix information leak in triggered buffer (git-fixes).\n- iio: gyro: fxas21002c: Fix missing data update in trigger handler (git-fixes).\n- iio: iio-mux: kzalloc instead of devm_kzalloc to ensure page alignment (git-fixes).\n- iio: imu: kmx61: fix information leak in triggered buffer (git-fixes).\n- iio: inkern: call iio_device_put() only on mapped devices (git-fixes).\n- iio: light: as73211: fix channel handling in only-color triggered buffer (git-fixes).\n- iio: light: vcnl4035: fix information leak in triggered buffer (git-fixes).\n- iio: pressure: zpa2326: fix information leak in triggered buffer (git-fixes).\n- iio: test : check null return of kunit_kmalloc in iio_rescale_test_scale (git-fixes).\n- intel_th: core: fix kernel-doc warnings (git-fixes).\n- ipmi: ipmb: Add check devm_kasprintf() returned value (git-fixes).\n- ipmi: ssif_bmc: Fix new request loss when bmc ready for a response (git-fixes).\n- irqchip/gic-v3: Force propagation of the active state with a read-back (stable-fixes).\n- irqchip/gic: Correct declaration of *percpu_base pointer in union gic_base (stable-fixes).\n- kconfig: fix file name in warnings when loading KCONFIG_DEFCONFIG_LIST (git-fixes).\n- kheaders: Ignore silly-rename files (stable-fixes).\n- ktest.pl: Avoid false positives with grub2 skip regex (stable-fixes).\n- ktest.pl: Check kernelrelease return in get_version (git-fixes).\n- ktest.pl: Fix typo 'accesing' (git-fixes).\n- ktest.pl: Fix typo in comment (git-fixes).\n- ktest.pl: Remove unused declarations in run_bisect_test function (git-fixes).\n- ktest: force $buildonly = 1 for 'make_warnings_file' test type (stable-fixes).\n- landlock: Handle weird files (git-fixes).\n- latencytop: use correct kernel-doc format for func params (git-fixes).\n- leds: lp8860: Write full EEPROM, not only half of it (git-fixes).\n- leds: netxbig: Fix an OF node reference leak in netxbig_leds_get_of_pdata() (git-fixes).\n- lib/inflate.c: remove dead code (git-fixes).\n- lib/stackdepot: print disabled message only if truly disabled (git-fixes).\n- mac802154: check local interfaces before deleting sdata list (stable-fixes).\n- mailbox: pcc: Add support for platform notification handling (stable-fixes).\n- mailbox: pcc: Support shared interrupt for multiple subspaces (stable-fixes).\n- mailbox: tegra-hsp: Clear mailbox before using message (git-fixes).\n- maple_tree: simplify split calculation (git-fixes).\n- media: camif-core: Add check for clk_enable() (git-fixes).\n- media: ccs: Clean up parsed CCS static data on parse failure (git-fixes).\n- media: ccs: Fix CCS static data parsing for large block sizes (git-fixes).\n- media: ccs: Fix cleanup order in ccs_probe() (git-fixes).\n- media: dvb-usb-v2: af9035: fix ISO C90 compilation error on af9035_i2c_master_xfer (git-fixes).\n- media: i2c: imx412: Add missing newline to prints (git-fixes).\n- media: i2c: ov9282: Correct the exposure offset (git-fixes).\n- media: imx-jpeg: Fix potential error pointer dereference in detach_pm() (git-fixes).\n- media: imx296: Add standby delay during probe (git-fixes).\n- media: lmedm04: Handle errors for lme2510_int_read (git-fixes).\n- media: marvell: Add check for clk_enable() (git-fixes).\n- media: mc: fix endpoint iteration (git-fixes).\n- media: mipi-csis: Add check for clk_enable() (git-fixes).\n- media: nxp: imx8-isi: fix v4l2-compliance test errors (git-fixes).\n- media: ov5640: fix get_light_freq on auto (git-fixes).\n- media: rc: iguanair: handle timeouts (git-fixes).\n- media: rkisp1: Fix unused value issue (git-fixes).\n- media: uvcvideo: Fix crash during unbind if gpio unit is in use (git-fixes).\n- media: uvcvideo: Fix double free in error path (git-fixes).\n- media: uvcvideo: Fix event flags in uvc_ctrl_send_events (git-fixes).\n- media: uvcvideo: Force UVC version to 1.0a for 0408:4035 (stable-fixes).\n- media: uvcvideo: Only save async fh if success (git-fixes).\n- media: uvcvideo: Propagate buf-\u003eerror to userspace (git-fixes).\n- media: uvcvideo: Remove dangling pointers (git-fixes).\n- media: uvcvideo: Remove redundant NULL assignment (git-fixes).\n- media: uvcvideo: Support partial control reads (git-fixes).\n- memory tiering: count PGPROMOTE_SUCCESS when mem tiering is enabled (git-fixes).\n- memory-failure: use a folio in me_huge_page() (git-fixes).\n- memory: tegra20-emc: fix an OF node reference bug in tegra_emc_find_node_by_ram_code() (git-fixes).\n- misc: fastrpc: Deregister device nodes properly in error scenarios (git-fixes).\n- misc: fastrpc: Fix copy buffer page size (git-fixes).\n- misc: fastrpc: Fix registered buffer page address (git-fixes).\n- misc: microchip: pci1xxxx: Resolve kernel panic during GPIO IRQ handling (git-fixes).\n- misc: microchip: pci1xxxx: Resolve return code mismatch during GPIO set config (git-fixes).\n- misc: misc_minor_alloc to use ida for all dynamic/misc dynamic minors (git-fixes).\n- mm, kmsan: fix infinite recursion due to RCU critical section (git-fixes).\n- mm,page_owner: do not remove __GFP_NOLOCKDEP in add_stack_record_to_list (git-fixes).\n- mm/memory-failure: cast index to loff_t before shifting it (git-fixes).\n- mm/memory-failure: check the mapcount of the precise page (git-fixes).\n- mm/memory-failure: fix crash in split_huge_page_to_list from soft_offline_page (git-fixes).\n- mm/memory-failure: pass the folio and the page to collect_procs() (git-fixes).\n- mm/memory-failure: use raw_spinlock_t in struct memory_failure_cpu (git-fixes).\n- mm/memory_hotplug: add missing mem_hotplug_lock (git-fixes).\n- mm/memory_hotplug: fix error handling in add_memory_resource() (git-fixes).\n- mm/memory_hotplug: prevent accessing by index=-1 (git-fixes).\n- mm/memory_hotplug: use pfn math in place of direct struct page manipulation (git-fixes).\n- mm/migrate: correct nr_failed in migrate_pages_sync() (git-fixes).\n- mm/migrate: fix deadlock in migrate_pages_batch() on large folios (git-fixes).\n- mm/migrate: putback split folios when numa hint migration fails (git-fixes).\n- mm/migrate: split source folio if it is on deferred split list (git-fixes).\n- mm/page_owner: remove free_ts from page_owner output (git-fixes).\n- mm/rodata_test: use READ_ONCE() to read const variable (git-fixes).\n- mm: convert DAX lock/unlock page to lock/unlock folio (git-fixes).\n- mm: memory-failure: ensure moving HWPoison flag to the raw error pages (git-fixes).\n- mm: memory-failure: fetch compound head after extra page refcnt is held (git-fixes).\n- mm: memory-failure: fix potential page refcnt leak in memory_failure() (git-fixes).\n- mm: memory-failure: fix race window when trying to get hugetlb folio (git-fixes).\n- mm: memory-failure: remove unneeded PageHuge() check (git-fixes).\n- mm: prevent derefencing NULL ptr in pfn_section_valid() (git-fixes).\n- modpost: fix the missed iteration for the max bit in do_input() (git-fixes).\n- mtd: onenand: Fix uninitialized retlen in do_otp_read() (git-fixes).\n- mtd: spinand: Remove write_enable_op() in markbad() (git-fixes).\n- net/rose: prevent integer overflows in rose_setsockopt() (git-fixes).\n- net: mana: Cleanup 'mana' debugfs dir after cleanup of all children (bsc#1236760).\n- net: mana: Enable debugfs files for MANA device (bsc#1236758).\n- net: netvsc: Update default VMBus channels (bsc#1236757).\n- net: phy: c45-tjaxx: add delay between MDIO write and read in soft_reset (git-fixes).\n- net: rose: fix timer races against user threads (git-fixes).\n- net: usb: qmi_wwan: add Telit FE910C04 compositions (stable-fixes).\n- net: usb: rtl8150: enable basic endpoint checking (git-fixes).\n- net: wwan: iosm: Properly check for valid exec stage in ipc_mmio_init() (git-fixes).\n- net: wwan: t7xx: Fix FSM command timeout issue (git-fixes).\n- netfilter: nf_tables: validate family when identifying table via handle (bsc#1233778 ZDI-24-1454).\n- nilfs2: fix possible int overflows in nilfs_fiemap() (git-fixes).\n- nvme-tcp: Fix I/O queue cpu spreading for multiple controllers (git-fixes).\n- nvme: Add error check for xa_store in nvme_get_effects_log (git-fixes).\n- nvme: Add error path for xa_store in nvme_init_effects (git-fixes).\n- nvme: fix bogus kzalloc() return check in nvme_init_effects_log() (git-fixes).\n- nvmet: propagate npwg topology (git-fixes).\n- padata: add pd get/put refcnt helper (git-fixes).\n- padata: avoid UAF for reorder_work (git-fixes).\n- padata: fix UAF in padata_reorder (git-fixes).\n- pinctrl: amd: Take suspend type into consideration which pins are non-wake (git-fixes).\n- pinctrl: samsung: fix fwnode refcount cleanup if platform_get_irq_optional() fails (git-fixes).\n- platform/x86/amd/pmc: Only disable IRQ1 wakeup where i8042 actually enabled it (git-fixes).\n- platform/x86/intel-uncore-freq: Ignore minor version change (bsc#1225897).\n- platform/x86/intel/tpmi: Add defines to get version information (bsc#1225897).\n- pm:cpupower: Add missing powercap_set_enabled() stub function (git-fixes).\n- power: ip5xxx_power: Fix return value on ADC read errors (git-fixes).\n- powerpc/iommu: Move pSeries specific functions to pseries/iommu.c (bsc#1220711 ltc#205755).\n- powerpc/iommu: Only build sPAPR access functions on pSeries (bsc#1220711 ltc#205755).\n- powerpc/powernv/pci: Remove MVE code (bsc#1220711 ltc#205755).\n- powerpc/powernv/pci: Remove ioda1 support (bsc#1220711 ltc#205755).\n- powerpc/powernv/pci: Remove last IODA1 defines (bsc#1220711 ltc#205755).\n- powerpc/pseries/eeh: Fix get PE state translation (bsc#1215199).\n- powerpc/pseries/iommu: IOMMU incorrectly marks MMIO range in DDW (bsc#1218470 ltc#204531).\n- powerpc/pseries/vas: Add close() callback in vas_vm_ops struct (bsc#1234825).\n- pps: add an error check in parport_attach (git-fixes).\n- pps: remove usage of the deprecated ida_simple_xx() API (stable-fixes).\n- printk: Add is_printk_legacy_deferred() (bsc#1236733).\n- printk: Defer legacy printing when holding printk_cpu_sync (bsc#1236733).\n- pwm: stm32-lp: Add check for clk_enable() (git-fixes).\n- pwm: stm32: Add check for clk_enable() (git-fixes).\n- r8169: enable SG/TSO on selected chip versions per default (bsc#1235874).\n- rcu-tasks: Pull sampling of -\u003epercpu_dequeue_lim out of loop (git-fixes)\n- rcu/tree: Defer setting of jiffies during stall reset (git-fixes)\n- rcu: Dump memory object info if callback function is invalid (git-fixes)\n- rcu: Eliminate rcu_gp_slow_unregister() false positive (git-fixes)\n- rcuscale: Move rcu_scale_writer() (git-fixes)\n- rdma/cxgb4: Prevent potential integer overflow on 32bit (git-fixes)\n- regulator: core: Add missing newline character (git-fixes).\n- regulator: of: Implement the unwind path of of_regulator_match() (git-fixes).\n- remoteproc: core: Fix ida_free call while not allocated (git-fixes).\n- rtc: pcf85063: fix potential OOB write in PCF85063 NVMEM read (git-fixes).\n- rtc: zynqmp: Fix optional clock name property (git-fixes).\n- s390x config: IOMMU_DEFAULT_DMA_LAZY=y (bsc#1235646)\n- samples/landlock: Fix possible NULL dereference in parse_path() (git-fixes).\n- sched/fair: Fix value reported by hot tasks pulled in /proc/schedstat (bsc#1235865).\n- sched/fair: Fix value reported by hot tasks pulled in /proc/schedstat -kabi (bsc#1235865).\n- scsi: storvsc: Ratelimit warning logs to prevent VM denial of service (git-fixes).\n- seccomp: Stub for !CONFIG_SECCOMP (stable-fixes).\n- selftest: media_tests: fix trivial UAF typo (git-fixes).\n- selftests/alsa: Fix circular dependency involving global-timer (stable-fixes).\n- selftests/landlock: Fix error message (git-fixes).\n- selftests/mm/cow: modify the incorrect checking parameters (git-fixes).\n- selftests/powerpc: Fix argument order to timer_sub() (git-fixes).\n- selftests: harness: fix printing of mismatch values in __EXPECT() (git-fixes).\n- selftests: mptcp: avoid spurious errors on disconnect (git-fixes).\n- selftests: tc-testing: reduce rshift value (stable-fixes).\n- selftests: timers: clocksource-switch: Adapt progress to kselftest framework (git-fixes).\n- selinux: Fix SCTP error inconsistency in selinux_socket_bind() (git-fixes).\n- serial: 8250: Adjust the timeout for FIFO mode (git-fixes).\n- serial: sh-sci: Do not probe the serial port if its slot in sci_ports[] is in use (git-fixes).\n- serial: sh-sci: Drop __initdata macro for port_cfg (git-fixes).\n- soc: atmel: fix device_node release in atmel_soc_device_init() (git-fixes).\n- soc: mediatek: mtk-devapc: Fix leaking IO map on error paths (git-fixes).\n- soc: qcom: smem_state: fix missing of_node_put in error path (git-fixes).\n- soc: qcom: socinfo: Avoid out of bounds read of serial number (git-fixes).\n- sound: usb: enable DSD output for ddHiFi TC44C (stable-fixes).\n- sound: usb: format: do not warn that raw DSD is unsupported (stable-fixes).\n- spi: zynq-qspi: Add check for clk_enable() (git-fixes).\n- srcu: Fix srcu_struct node grpmask overflow on 64-bit systems (git-fixes)\n- srcu: Only accelerate on enqueue time (git-fixes)\n- stackdepot: rename pool_index to pool_index_plus_1 (git-fixes).\n- stackdepot: respect __GFP_NOLOCKDEP allocation flag (git-fixes).\n- staging: iio: ad9832: Correct phase range check (git-fixes).\n- staging: iio: ad9834: Correct phase range check (git-fixes).\n- staging: media: imx: fix OF node leak in imx_media_add_of_subdevs() (git-fixes).\n- staging: media: max96712: fix kernel oops when removing module (git-fixes).\n- thermal: of: fix OF node leak in of_thermal_zone_find() (git-fixes).\n- thunderbolt: Add support for Intel Lunar Lake (stable-fixes).\n- thunderbolt: Add support for Intel Panther Lake-M/P (stable-fixes).\n- tipc: fix NULL deref in cleanup_bearer() (bsc#1235433).\n- tools: Sync if_xdp.h uapi tooling header (git-fixes).\n- tpm: Map the ACPI provided event log (bsc#1233260 bsc#1233259 bsc#1232421).\n- tty: serial: 8250: Fix another runtime PM usage counter underflow (git-fixes).\n- ubifs: skip dumping tnc tree when zroot is null (git-fixes).\n- uio: Fix return value of poll (git-fixes).\n- uio: uio_dmem_genirq: check the return value of devm_kasprintf() (git-fixes).\n- usb-storage: Add max sectors quirk for Nokia 208 (stable-fixes).\n- usb: chipidea: add CI_HDRC_FORCE_VBUS_ACTIVE_ALWAYS flag (stable-fixes).\n- usb: dwc3-am62: Disable autosuspend during remove (git-fixes).\n- usb: dwc3-am62: Fix an OF node leak in phy_syscon_pll_refclk() (git-fixes).\n- usb: dwc3: gadget: fix writing NYET threshold (git-fixes).\n- usb: fix reference leak in usb_new_device() (git-fixes).\n- usb: gadget: configfs: Ignore trailing LF for user strings to cdev (git-fixes).\n- usb: gadget: f_fs: Remove WARN_ON in functionfs_bind (git-fixes).\n- usb: gadget: f_tcm: Decrement command ref count on cleanup (git-fixes).\n- usb: gadget: f_tcm: Do not free command immediately (git-fixes).\n- usb: gadget: f_tcm: Do not prepare BOT write request twice (git-fixes).\n- usb: gadget: f_tcm: Fix Get/SetInterface return value (git-fixes).\n- usb: gadget: f_tcm: Translate error to sense (git-fixes).\n- usb: gadget: f_tcm: ep_autoconfig with fullspeed endpoint (git-fixes).\n- usb: gadget: f_uac2: Fix incorrect setting of bNumEndpoints (git-fixes).\n- usb: gadget: u_serial: Disable ep before setting port to null to fix the crash caused by port being null (git-fixes).\n- usb: host: xhci-plat: Assign shared_hcd-\u003ersrc_start (git-fixes).\n- usb: typec: fix pm usage counter imbalance in ucsi_ccg_sync_control() (bsc#1235001)\n- usb: typec: tcpm/tcpci_maxim: fix error code in max_contaminant_read_resistance_kohm() (git-fixes).\n- usb: typec: tcpm: set SRC_SEND_CAPABILITIES timeout to PD_T_SENDER_RESPONSE (git-fixes).\n- usbnet: ipheth: break up NCM header size computation (git-fixes).\n- usbnet: ipheth: check that DPE points past NCM header (git-fixes).\n- usbnet: ipheth: fix DPE OoB read (git-fixes).\n- usbnet: ipheth: fix possible overflow in DPE length check (git-fixes).\n- usbnet: ipheth: refactor NCM datagram loop (git-fixes).\n- usbnet: ipheth: use static NDP16 location in URB (git-fixes).\n- vfio/pci: Lock external INTx masking ops (bsc#1222803).\n- vmscan,migrate: fix page count imbalance on node stats when demoting pages (git-fixes).\n- watchdog: rzg2l_wdt: Power on the watchdog domain in the restart handler (stable-fixes).\n- watchdog: rzg2l_wdt: Rely on the reset driver for doing proper reset (stable-fixes).\n- watchdog: rzg2l_wdt: Remove reset de-assert from probe (stable-fixes).\n- wifi: ath11k: Fix unexpected return buffer manager error for WCN6750/WCN6855 (git-fixes).\n- wifi: ath11k: cleanup struct ath11k_mon_data (git-fixes).\n- wifi: ath12k: fix atomic calls in ath12k_mac_op_set_bitrate_mask() (stable-fixes).\n- wifi: ath12k: fix tx power, max reg power update to firmware (git-fixes).\n- wifi: brcmfmac: add missing header include for brcmf_dbg (git-fixes).\n- wifi: cfg80211: adjust allocation of colocated AP data (git-fixes).\n- wifi: iwlwifi: fw: read STEP table from correct UEFI var (git-fixes).\n- wifi: mac80211: Add non-atomic station iterator (stable-fixes).\n- wifi: mac80211: Fix common size calculation for ML element (git-fixes).\n- wifi: mac80211: do not flush non-uploaded STAs (git-fixes).\n- wifi: mac80211: export ieee80211_purge_tx_queue() for drivers (stable-fixes).\n- wifi: mac80211: fix mbss changed flags corruption on 32 bit systems (stable-fixes).\n- wifi: mac80211: fix tid removal during mesh forwarding (git-fixes).\n- wifi: mac80211: prohibit deactivating all links (git-fixes).\n- wifi: mac80211: wake the queues in case of failure in resume (stable-fixes).\n- wifi: mt76: mt76u_vendor_request: Do not print error messages when -EPROTO (git-fixes).\n- wifi: mt76: mt7915: Fix mesh scan on MT7916 DBDC (git-fixes).\n- wifi: mt76: mt7915: add module param to select 5 GHz or 6 GHz on MT7916 (git-fixes).\n- wifi: mt76: mt7915: firmware restart on devices with a second pcie link (git-fixes).\n- wifi: mt76: mt7915: fix overflows seen when writing limit attributes (git-fixes).\n- wifi: mt76: mt7915: fix register mapping (git-fixes).\n- wifi: mt76: mt7921: fix using incorrect group cipher after disconnection (git-fixes).\n- wifi: mt76: mt7925: fix off by one in mt7925_load_clc() (git-fixes).\n- wifi: mt76: mt7996: add max mpdu len capability (git-fixes).\n- wifi: mt76: mt7996: fix HE Phy capability (git-fixes).\n- wifi: mt76: mt7996: fix definition of tx descriptor (git-fixes).\n- wifi: mt76: mt7996: fix incorrect indexing of MIB FW event (git-fixes).\n- wifi: mt76: mt7996: fix ldpc setting (git-fixes).\n- wifi: mt76: mt7996: fix overflows seen when writing limit attributes (git-fixes).\n- wifi: mt76: mt7996: fix register mapping (git-fixes).\n- wifi: mt76: mt7996: fix rx filter setting for bfee functionality (git-fixes).\n- wifi: mt76: mt7996: fix the capability of reception of EHT MU PPDU (git-fixes).\n- wifi: rtlwifi: destroy workqueue at rtl_deinit_core (git-fixes).\n- wifi: rtlwifi: do not complete firmware loading needlessly (git-fixes).\n- wifi: rtlwifi: fix init_sw_vars leak when probe fails (git-fixes).\n- wifi: rtlwifi: fix memory leaks and invalid access at probe error path (git-fixes).\n- wifi: rtlwifi: pci: wait for firmware loading before releasing memory (git-fixes).\n- wifi: rtlwifi: remove unused check_buddy_priv (git-fixes).\n- wifi: rtlwifi: rtl8192se: rise completion of firmware loading as last step (git-fixes).\n- wifi: rtlwifi: rtl8821ae: Fix media status report (git-fixes).\n- wifi: rtlwifi: rtl8821ae: phy: restore removed code to fix infinite loop (git-fixes).\n- wifi: rtlwifi: usb: fix workqueue leak when probe fails (git-fixes).\n- wifi: rtlwifi: wait for firmware loading before releasing memory (git-fixes).\n- wifi: rtw88: use ieee80211_purge_tx_queue() to purge TX skb (stable-fixes).\n- wifi: rtw89: mcc: consider time limits not divisible by 1024 (git-fixes).\n- wifi: wcn36xx: fix channel survey memory allocation size (git-fixes).\n- wifi: wlcore: fix unbalanced pm_runtime calls (git-fixes).\n- workqueue: Add rcu lock check at the end of work item execution (bsc#1236732).\n- x86/static-call: Remove early_boot_irqs_disabled check to fix Xen PVH dom0 (git-fixes).\n- xfs: Add error handling for xfs_reflink_cancel_cow_range (git-fixes).\n- xfs: Propagate errors from xfs_reflink_cancel_cow_range in xfs_dax_write_iomap_end (git-fixes).\n","status":"published","published":"2025-02-11T10:40:10Z","modified":"2026-02-04T03:19:22.226497Z","updated_at":"2026-11-02T15:53:58.883365Z"},{"id":"SUSE-SU-2025:0499-1","title":"Security update for the Linux Kernel","description":"\nThe SUSE Linux Enterprise 15 SP6 kernel was updated to receive various security bugfixes.\n\n\nThe following security bugs were fixed:\n\n- CVE-2025-21682: eth: bnxt: always recalculate features after XDP clearing, fix null-deref (bsc#1236703).\n- CVE-2025-21678: gtp: Destroy device along with udp socket's netns dismantle (bsc#1236698).\n- CVE-2025-21676: net: fec: handle page_pool_dev_alloc_pages error (bsc#1236696).\n- CVE-2025-21675: net/mlx5: Clear port select structure when fail to create (bsc#1236694).\n- CVE-2025-21674: net/mlx5e: Fix inversion dependency warning while enabling IPsec tunnel (bsc#1236688).\n- CVE-2025-21670: vsock/bpf: return early if transport is not assigned (bsc#1236685).\n- CVE-2025-21669: vsock/virtio: discard packets if the transport changes (bsc#1236683).\n- CVE-2025-21666: vsock: prevent null-ptr-deref in vsock_*[has_data|has_space] (bsc#1236680).\n- CVE-2025-21664: dm thin: make get_first_thin use rcu-safe list first function (bsc#1236262).\n- CVE-2025-21663: net: stmmac: dwmac-tegra: Read iommu stream id from device tree (bsc#1236260).\n- CVE-2025-21662: net/mlx5: Fix variable not being completed when function returns (bsc#1236198).\n- CVE-2025-21655: io_uring/eventfd: ensure io_eventfd_signal() defers another RCU period (bsc#1236163).\n- CVE-2025-21653: net_sched: cls_flow: validate TCA_FLOW_RSHIFT attribute (bsc#1236161).\n- CVE-2025-21652: ipvlan: Fix use-after-free in ipvlan_get_iflink() (bsc#1236160).\n- CVE-2025-21651: net: hns3: do not auto enable misc vector (bsc#1236145).\n- CVE-2025-21650: net: hns3: fixed hclge_fetch_pf_reg accesses bar space out of bounds issue (bsc#1236144).\n- CVE-2025-21649: net: hns3: fix kernel crash when 1588 is sent on HIP08 devices (bsc#1236143).\n- CVE-2025-21632: x86/fpu: Ensure shadow stack is active before 'getting' registers (bsc#1236106).\n- CVE-2024-57946: virtio-blk: do not keep queue frozen during system suspend (bsc#1236247).\n- CVE-2024-57938: net/sctp: Prevent autoclose integer overflow in sctp_association_init() (bsc#1236182).\n- CVE-2024-57933: gve: guard XSK operations on the existence of queues (bsc#1236178).\n- CVE-2024-57932: gve: guard XDP xmit NDO on existence of xdp queues (bsc#1236190).\n- CVE-2024-57931: selinux: ignore unknown extended permissions (bsc#1236192).\n- CVE-2024-57929: dm array: fix releasing a faulty array block twice in dm_array_cursor_end (bsc#1236096).\n- CVE-2024-57917: topology: Keep the cpumask unchanged when printing cpumap (bsc#1236127).\n- CVE-2024-57903: net: restrict SO_REUSEPORT to inet sockets (bsc#1235967).\n- CVE-2024-57896: btrfs: flush delalloc workers queue before stopping cleaner kthread during unmount (bsc#1235965).\n- CVE-2024-57892: ocfs2: fix slab-use-after-free due to dangling pointer dqi_priv (bsc#1235964).\n- CVE-2024-57884: mm: vmscan: account for free pages to prevent infinite Loop in throttle_direct_reclaim() (bsc#1235948).\n- CVE-2024-57882: mptcp: fix TCP options overflow. (bsc#1235914).\n- CVE-2024-57857: RDMA/siw: Remove direct link to net_device (bsc#1235946).\n- CVE-2024-57838: s390/entry: Mark IRQ entries to fix stack depot warnings (bsc#1235798).\n- CVE-2024-57809: PCI: imx6: Fix suspend/resume support on i.MX6QDL (bsc#1235793).\n- CVE-2024-57804: scsi: mpi3mr: Fix corrupt config pages PHY state is switched in sysfs (bsc#1235779).\n- CVE-2024-57802: netrom: check buffer length before accessing it (bsc#1235941).\n- CVE-2024-57801: net/mlx5e: Skip restore TC rules for vport rep without loaded flag (bsc#1235940).\n- CVE-2024-57795: RDMA/rxe: Remove the direct link to net_device (bsc#1235906).\n- CVE-2024-57793: virt: tdx-guest: Just leak decrypted memory on unrecoverable errors (bsc#1235768).\n- CVE-2024-57791: net/smc: check return value of sock_recvmsg when draining clc data (bsc#1235759).\n- CVE-2024-56775: drm/amd/display: Fix handling of plane refcount (bsc#1235657).\n- CVE-2024-56774: btrfs: add a sanity check for btrfs root in btrfs_search_slot() (bsc#1235653).\n- CVE-2024-56763: tracing: Prevent bad count for tracing_cpumask_write (bsc#1235638).\n- CVE-2024-56759: btrfs: fix use-after-free when COWing tree bock and tracing is enabled (bsc#1235645).\n- CVE-2024-56748: scsi: qedf: Fix a possible memory leak in qedf_alloc_and_init_sb() (bsc#1235627).\n- CVE-2024-56747: scsi: qedi: Fix a possible memory leak in qedi_alloc_and_init_sb() (bsc#1234934).\n- CVE-2024-56729: smb: Initialize cfid-\u003etcon before performing network ops (bsc#1235503).\n- CVE-2024-56728: octeontx2-pf: handle otx2_mbox_get_rsp errors in otx2_ethtool.c (bsc#1235656).\n- CVE-2024-56727: octeontx2-pf: handle otx2_mbox_get_rsp errors in otx2_flows.c (bsc#1235583).\n- CVE-2024-56726: octeontx2-pf: handle otx2_mbox_get_rsp errors in cn10k.c (bsc#1235582).\n- CVE-2024-56725: octeontx2-pf: handle otx2_mbox_get_rsp errors in otx2_dcbnl.c (bsc#1235578).\n- CVE-2024-56716: netdevsim: prevent bad user input in nsim_dev_health_break_write() (bsc#1235587).\n- CVE-2024-56715: ionic: Fix netdev notifier unregister on failure (bsc#1235612).\n- CVE-2024-56712: udmabuf: fix memory leak on last export_udmabuf() error path (bsc#1235565).\n- CVE-2024-56708: EDAC/igen6: Avoid segmentation fault on module unload (bsc#1235564).\n- CVE-2024-56707: octeontx2-pf: handle otx2_mbox_get_rsp errors in otx2_dmac_flt.c (bsc#1235545).\n- CVE-2024-56704: 9p/xen: fix release of IRQ (bsc#1235584).\n- CVE-2024-56694: bpf: fix recursive lock when verdict program return SK_PASS (bsc#1235412).\n- CVE-2024-56693: brd: defer automatic disk creation until module initialization succeeds (bsc#1235418).\n- CVE-2024-56679: octeontx2-pf: handle otx2_mbox_get_rsp errors in otx2_common.c (bsc#1235498).\n- CVE-2024-56675: bpf: Fix UAF via mismatching bpf_prog/attachment RCU flavors (bsc#1235555).\n- CVE-2024-56665: bpf,perf: Fix invalid prog_array access in perf_event_detach_bpf_prog (bsc#1235489).\n- CVE-2024-56664: bpf, sockmap: Fix race between element replace and close() (bsc#1235249).\n- CVE-2024-56660: net/mlx5: DR, prevent potential error pointer dereference (bsc#1235437).\n- CVE-2024-56659: net: lapb: increase LAPB_HEADER_LEN (bsc#1235439).\n- CVE-2024-56658: net: defer final 'struct net' free in netns dismantle (bsc#1235441).\n- CVE-2024-56656: bnxt_en: Fix aggregation ID mask to prevent oops on 5760X chips (bsc#1235444).\n- CVE-2024-56650: netfilter: x_tables: fix LED ID check in led_tg_check() (bsc#1235430).\n- CVE-2024-56649: net: enetc: Do not configure preemptible TCs if SIs do not support (bsc#1235449).\n- CVE-2024-56648: net: hsr: avoid potential out-of-bound access in fill_frame_info() (bsc#1235451).\n- CVE-2024-56643: dccp: Fix memory leak in dccp_feat_change_recv (bsc#1235132).\n- CVE-2024-56641: net/smc: initialize close_work early to avoid warning (bsc#1235526).\n- CVE-2024-56637: netfilter: ipset: Hold module reference while requesting a module (bsc#1235523).\n- CVE-2024-56636: geneve: do not assume mac header is set in geneve_xmit_skb() (bsc#1235520).\n- CVE-2024-56635: net: avoid potential UAF in default_operstate() (bsc#1235519).\n- CVE-2024-56631: scsi: sg: Fix slab-use-after-free read in sg_release() (bsc#1235480).\n- CVE-2024-56622: scsi: ufs: core: sysfs: Prevent div by zero (bsc#1235251).\n- CVE-2024-56620: scsi: ufs: qcom: Only free platform MSIs when ESI is enabled (bsc#1235227).\n- CVE-2024-56617: cacheinfo: Allocate memory during CPU hotplug if not done from the primary CPU (bsc#1235429).\n- CVE-2024-56615: bpf: fix OOB devmap writes when deleting elements (bsc#1235426).\n- CVE-2024-56614: xsk: fix OOB map writes when deleting elements (bsc#1235424).\n- CVE-2024-56611: mm/mempolicy: fix migrate_to_node() assuming there is at least one VMA in a MM (bsc#1235391).\n- CVE-2024-56610: kcsan: Turn report_filterlist_lock into a raw_spinlock (bsc#1235390).\n- CVE-2024-56608: drm/amd/display: Fix out-of-bounds access in 'dcn21_link_encoder_create' (bsc#1235487).\n- CVE-2024-56603: net: af_can: do not leave a dangling sk pointer in can_create() (bsc#1235415).\n- CVE-2024-56602: net: ieee802154: do not leave a dangling sk pointer in ieee802154_create() (bsc#1235521).\n- CVE-2024-56601: net: inet: do not leave a dangling sk pointer in inet_create() (bsc#1235230).\n- CVE-2024-56600: net: inet6: do not leave a dangling sk pointer in inet6_create() (bsc#1235217).\n- CVE-2024-56592: bpf: Call free_htab_elem() after htab_unlock_bucket() (bsc#1235244).\n- CVE-2024-56589: scsi: hisi_sas: Add cond_resched() for no forced preemption model (bsc#1235241).\n- CVE-2024-56588: scsi: hisi_sas: Create all dump files during debugfs initialization (bsc#1235123).\n- CVE-2024-56570: ovl: Filter invalid inodes with missing lookup function (bsc#1235035).\n- CVE-2024-56569: ftrace: Fix regression with module command in stack_trace_filter (bsc#1235031).\n- CVE-2024-56568: iommu/arm-smmu: Defer probe of clients after smmu device bound (bsc#1235032).\n- CVE-2024-56372: net: tun: fix tun_napi_alloc_frags() (bsc#1235753).\n- CVE-2024-55881: KVM: x86: Play nice with protected guests in complete_hypercall_exit() (bsc#1235745).\n- CVE-2024-55639: net: renesas: rswitch: avoid use-after-put for a device tree node (bsc#1235737).\n- CVE-2024-53685: ceph: give up on paths longer than PATH_MAX (bsc#1235720).\n- CVE-2024-53236: xsk: Free skb when TX metadata options are invalid (bsc#1235000).\n- CVE-2024-53232: iommu/s390: Implement blocking domain (bsc#1235050).\n- CVE-2024-53227: scsi: bfa: Fix use-after-free in bfad_im_module_exit() (bsc#1235011).\n- CVE-2024-53203: usb: typec: fix potential array underflow in ucsi_ccg_sync_control() (bsc#1235001).\n- CVE-2024-53198: xen: Fix the issue of resource not being properly released in xenbus_dev_probe() (bsc#1234923).\n- CVE-2024-53196: KVM: arm64: Do not retire aborted MMIO instruction (bsc#1234906).\n- CVE-2024-53195: KVM: arm64: Get rid of userspace_irqchip_in_use (bsc#1234957).\n- CVE-2024-53187: io_uring: check for overflows in io_pin_pages (bsc#1234947).\n- CVE-2024-53185: smb: client: fix NULL ptr deref in crypto_aead_setkey() (bsc#1234901).\n- CVE-2024-53175: ipc: fix memleak if msg_init_ns failed in create_ipc_ns (bsc#1234893).\n- CVE-2024-53172: ubi: fastmap: Fix duplicate slab cache names while attaching (bsc#1234898).\n- CVE-2024-53170: block: fix uaf for flush rq while iterating tags (bsc#1234888).\n- CVE-2024-53164: net: sched: fix ordering of qlen adjustment (bsc#1234863).\n- CVE-2024-53091: bpf: Add sk_is_inet and IS_ICSK check in tls_sw_has_ctx_tx/rx (bsc#1233638).\n- CVE-2024-50304: ipv4: ip_tunnel: Fix suspicious RCU usage warning in ip_tunnel_find() (bsc#1233522).\n- CVE-2024-50299: sctp: properly validate chunk size in sctp_sf_ootb() (bsc#1233488).\n- CVE-2024-50258: net: fix crash when config small gso_max_size/gso_ipv4_max_size (bsc#1233221).\n- CVE-2024-50251: netfilter: nft_payload: sanitize offset and length before calling skb_checksum() (bsc#1233248).\n- CVE-2024-50199: mm/swapfile: skip HugeTLB pages for unuse_vma (bsc#1233112).\n- CVE-2024-50151: smb: client: fix OOBs when building SMB2_IOCTL request (bsc#1233055).\n- CVE-2024-49998: net: dsa: improve shutdown sequence (bsc#1232087).\n- CVE-2024-49978: gso: fix udp gso fraglist segmentation after pull from frag_list (bsc#1232101).\n- CVE-2024-49951: Bluetooth: MGMT: Fix possible crash on mgmt_index_removed (bsc#1232158).\n- CVE-2024-49948: net: add more sanity checks to qdisc_pkt_len_init() (bsc#1232161).\n- CVE-2024-48881: bcache: revert replacing IS_ERR_OR_NULL with IS_ERR again (bsc#1235727).\n- CVE-2024-46858: mptcp: pm: Fix uaf in __timer_delete_sync (bsc#1231088).\n- CVE-2024-45828: i3c: mipi-i3c-hci: Mask ring interrupts before ring stop request (bsc#1235705).\n- CVE-2024-26810: vfio/pci: Lock external INTx masking ops (bsc#1222803).\n- CVE-2023-52489: mm/sparsemem: fix race in accessing memory_section-\u003eusage (bsc#1221326).\n\nThe following non-security bugs were fixed:\n\n- ACPI/IORT: Add PMCG platform information for HiSilicon HIP09A (stable-fixes).\n- ACPI/IORT: Add PMCG platform information for HiSilicon HIP10/11 (stable-fixes).\n- ACPI: PCC: Add PCC shared memory region command and status bitfields (stable-fixes).\n- ACPI: fan: cleanup resources in the error path of .probe() (git-fixes).\n- ACPI: resource: Add Asus Vivobook X1504VAP to irq1_level_low_skip_override[] (stable-fixes).\n- ACPI: resource: Add TongFang GM5HG0A to irq1_edge_low_force_override[] (stable-fixes).\n- ACPI: resource: acpi_dev_irq_override(): Check DMI match last (stable-fixes).\n- ALSA: hda/realtek - Add support for ASUS Zen AIO 27 Z272SD_A272SD audio (stable-fixes).\n- ALSA: hda/realtek - Fixed headphone distorted sound on Acer Aspire A115-31 laptop (git-fixes).\n- ALSA: hda/realtek: Add new alc2xx-fixup-headset-mic model (stable-fixes).\n- ALSA: hda/realtek: Add support for Ayaneo System using CS35L41 HDA (stable-fixes).\n- ALSA: hda/realtek: Add support for Galaxy Book2 Pro (NP950XEE) (stable-fixes).\n- ALSA: hda/realtek: Enable Mute LED on HP Laptop 14s-fq1xxx (stable-fixes).\n- ALSA: hda/realtek: Enable headset mic on Positivo C6400 (stable-fixes).\n- ALSA: hda/realtek: Workaround for resume on Dell Venue 11 Pro 7130 (bsc#1235686).\n- ALSA: hda: Fix headset detection failure due to unstable sort (git-fixes).\n- ALSA: ump: Use guard() for locking (stable-fixes).\n- ALSA: usb-audio: Add delay quirk for USB Audio Device (stable-fixes).\n- ALSA: usb-audio: Add delay quirk for iBasso DC07 Pro (stable-fixes).\n- ASoC: Intel: avs: Fix theoretical infinite loop (git-fixes).\n- ASoC: acp: Support microphone from Lenovo Go S (stable-fixes).\n- ASoC: mediatek: disable buffer pre-allocation (stable-fixes).\n- ASoC: rockchip: i2s_tdm: Re-add the set_sysclk callback (git-fixes).\n- ASoC: rt722: add delay time to wait for the calibration procedure (stable-fixes).\n- ASoC: samsung: Add missing depends on I2C (git-fixes).\n- ASoC: samsung: Add missing selects for MFD_WM8994 (stable-fixes).\n- ASoC: sun4i-spdif: Add clock multiplier settings (git-fixes).\n- ASoC: wm8994: Add depends on MFD core (stable-fixes).\n- Align git commit ID abbreviation guidelines and checks (git-fixes).\n- Bluetooth: Add support ITTIM PE50-M75C (stable-fixes).\n- Bluetooth: L2CAP: accept zero as a special value for MTU auto-selection (git-fixes).\n- Bluetooth: L2CAP: handle NULL sock pointer in l2cap_sock_alloc (git-fixes).\n- Bluetooth: MGMT: Fix Add Device to responding before completing (git-fixes).\n- Bluetooth: btnxpuart: Fix driver sending truncated data (git-fixes).\n- Bluetooth: btnxpuart: Fix glitches seen in dual A2DP streaming (git-fixes).\n- Bluetooth: btusb: Add USB HW IDs for MT7921/MT7922/MT7925 (stable-fixes).\n- Bluetooth: btusb: Add new VID/PID 0489/e111 for MT7925 (stable-fixes).\n- Bluetooth: btusb: Add new VID/PID 13d3/3602 for MT7925 (stable-fixes).\n- Bluetooth: btusb: add callback function in btusb suspend/resume (stable-fixes).\n- Bluetooth: btusb: mediatek: add callback function in btusb_disconnect (stable-fixes).\n- Bluetooth: hci_sync: Fix not setting Random Address when required (git-fixes).\n- EDAC/{i10nm,skx,skx_common}: Support UV systems (bsc#1234693).\n- HID: core: Fix assumption that Resolution Multipliers must be in Logical Collections (git-fixes).\n- HID: fix generic desktop D-Pad controls (git-fixes).\n- HID: hid-sensor-hub: do not use stale platform-data on remove (git-fixes).\n- HID: hid-thrustmaster: Fix warning in thrustmaster_probe by adding endpoint check (git-fixes).\n- HID: multitouch: fix support for Goodix PID 0x01e9 (git-fixes).\n- Input: atkbd - map F23 key to support default copilot shortcut (stable-fixes).\n- Input: bbnsm_pwrkey - add remove hook (git-fixes).\n- Input: bbnsm_pwrkey - fix missed key press after suspend (git-fixes).\n- Input: davinci-keyscan - remove leftover header (git-fixes).\n- Input: xpad - add QH Electronics VID/PID (stable-fixes).\n- Input: xpad - add support for Nacon Evol-X Xbox One Controller (stable-fixes).\n- Input: xpad - add support for Nacon Pro Compact (stable-fixes).\n- Input: xpad - add support for wooting two he (arm) (stable-fixes).\n- Input: xpad - add unofficial Xbox 360 wireless receiver clone (stable-fixes).\n- Input: xpad - improve name of 8BitDo controller 2dc8:3106 (stable-fixes).\n- KVM: SVM: Allow guest writes to set MSR_AMD64_DE_CFG bits (bsc#1234635).\n- KVM: s390: Reject KVM_SET_GSI_ROUTING on ucontrol VMs (git-fixes bsc#1235776).\n- KVM: s390: Reject setting flic pfault attributes on ucontrol VMs (git-fixes bsc#1235777).\n- KVM: s390: vsie: fix virtual/physical address in unpin_scb() (git-fixes bsc#1235778).\n- NFC: nci: Add bounds checking in nci_hci_create_pipe() (git-fixes).\n- NFSv4.2: fix COPY_NOTIFY xdr buf size calculation (git-fixes).\n- NFSv4.2: mark OFFLOAD_CANCEL MOVEABLE (git-fixes).\n- PCI: Avoid putting some root ports into D3 on TUXEDO Sirius Gen1 (git-fixes).\n- PCI: dwc: Always stop link in the dw_pcie_suspend_noirq (git-fixes).\n- PCI: dwc: ep: Prevent changing BAR size/flags in pci_epc_set_bar() (git-fixes).\n- PCI: dwc: ep: Write BAR_MASK before iATU registers in pci_epc_set_bar() (git-fixes).\n- PCI: endpoint: Destroy the EPC device in devm_pci_epc_destroy() (git-fixes).\n- PCI: endpoint: Finish virtual EP removal in pci_epf_remove_vepf() (git-fixes).\n- PCI: endpoint: pci-epf-test: Fix check for DMA MEMCPY test (git-fixes).\n- PCI: endpoint: pci-epf-test: Set dma_chan_rx pointer to NULL on error (git-fixes).\n- PCI: imx6: Deassert apps_reset in imx_pcie_deassert_core_reset() (git-fixes).\n- PCI: imx6: Skip controller_id generation logic for i.MX7D (git-fixes).\n- PCI: microchip: Set inbound address translation for coherent or non-coherent mode (git-fixes).\n- PCI: rcar-ep: Fix incorrect variable used when calling devm_request_mem_region() (git-fixes).\n- PM: hibernate: Add error handling for syscore_suspend() (git-fixes).\n- RDMA/bnxt_re: Add send queue size check for variable wqe (git-fixes)\n- RDMA/bnxt_re: Fix MSN table size for variable wqe mode (git-fixes)\n- RDMA/bnxt_re: Fix max SGEs for the Work Request (git-fixes)\n- RDMA/bnxt_re: Fix the max WQE size for static WQE support (git-fixes)\n- RDMA/bnxt_re: Fix the max WQEs used in Static WQE mode (git-fixes)\n- RDMA/bnxt_re: Fix to drop reference to the mmap entry in case of error (git-fixes)\n- RDMA/bnxt_re: Fix to export port num to ib_query_qp (git-fixes)\n- RDMA/mlx4: Avoid false error about access to uninitialized gids array (git-fixes)\n- RDMA/mlx5: Fix a race for an ODP MR which leads to CQE with error (git-fixes)\n- RDMA/mlx5: Fix implicit ODP use after free (git-fixes)\n- RDMA/mlx5: Fix indirect mkey ODP page count (git-fixes)\n- RDMA/rxe: Fix mismatched max_msg_sz (git-fixes)\n- RDMA/rxe: Fix the warning '__rxe_cleanup+0x12c/0x170 [rdma_rxe]' (git-fixes)\n- RDMA/srp: Fix error handling in srp_add_port (git-fixes)\n- Revert 'HID: multitouch: Add support for lenovo Y9000P Touchpad' (stable-fixes).\n- Revert 'drm/i915/dpt: Make DPT object unshrinkable' (stable-fixes).\n- Revert 'mtd: spi-nor: core: replace dummy buswidth from addr to data' (git-fixes).\n- Revert 'usb: gadget: u_serial: Disable ep before setting port to null to fix the crash caused by port being null' (stable-fixes).\n- USB: core: Disable LPM only for non-suspended ports (git-fixes).\n- USB: serial: cp210x: add Phoenix Contact UPS Device (stable-fixes).\n- USB: serial: option: add MeiG Smart SRM815 (stable-fixes).\n- USB: serial: option: add Neoway N723-EA support (stable-fixes).\n- USB: serial: quatech2: fix null-ptr-deref in qt2_process_read_urb() (git-fixes).\n- USB: usblp: return error when setting unsupported protocol (git-fixes).\n- VFS: use system_unbound_wq for delayed_mntput (bsc#1234683).\n- VMCI: fix reference to ioctl-number.rst (git-fixes).\n- afs: Fix EEXIST error returned from afs_rmdir() to be ENOTEMPTY (git-fixes).\n- afs: Fix cleanup of immediately failed async calls (git-fixes).\n- afs: Fix directory format encoding struct (git-fixes).\n- afs: Fix the fallback handling for the YFS.RemoveFile2 RPC call (git-fixes).\n- afs: Fix the maximum cell name length (git-fixes).\n- arm64/sme: Move storage of reg_smidr to __cpuinfo_store_cpu() (git-fixes)\n- arm64: Filter out SVE hwcaps when FEAT_SVE isn't implemented (git-fixes)\n- arm64: Kconfig: Make SME depend on BROKEN for now (git-fixes bsc#1236245).\n- arm64: dts: rockchip: Add sdmmc/sdio/emmc reset controls for RK3328 (git-fixes)\n- arm64: dts: rockchip: add hevc power domain clock to rk3328 (git-fixes).\n- arm64: dts: rockchip: increase gmac rx_delay on rk3399-puma (git-fixes)\n- arm64: ptrace: fix partial SETREGSET for NT_ARM_TAGGED_ADDR_CTRL (git-fixes).\n- arm64: tegra: Disable Tegra234 sce-fabric node (git-fixes)\n- arm64: tegra: Fix Tegra234 PCIe interrupt-map (git-fixes)\n- arm64: tegra: Fix typo in Tegra234 dce-fabric compatible (git-fixes)\n- ata: libata-core: Set ATA_QCFLAG_RTF_FILLED in fill_result_tf() (stable-fixes).\n- bnxt_en: Fix GSO type for HW GRO packets on 5750X chips (git-fixes)\n- btrfs: fix use-after-free in btrfs_encoded_read_endio() (bsc#1235445).\n- btrfs: fix use-after-free waiting for encoded read endios (bsc#1235445).\n- bus: mhi: host: Free mhi_buf vector inside mhi_alloc_bhie_table() (git-fixes).\n- ceph: improve error handling and short/overflow-read logic in __ceph_sync_read() (bsc#1228592).\n- cleanup: Add conditional guard support (stable-fixes).\n- cleanup: Adjust scoped_guard() macros to avoid potential warning (stable-fixes).\n- cleanup: Remove address space of returned pointer (git-fixes).\n- cpufreq: ACPI: Fix max-frequency computation (git-fixes).\n- cpufreq: Do not unregister cpufreq cooling on CPU hotplug (git-fixes).\n- cpufreq: amd-pstate: remove global header file (git-fixes).\n- cpufreq: intel_pstate: Check turbo_is_disabled() in store_no_turbo() (bsc#1234619).\n- cpufreq: intel_pstate: Do not update global.turbo_disabled after initialization (bsc#1234619).\n- cpufreq: intel_pstate: Drop redundant locking from intel_pstate_driver_cleanup() (bsc#1234619).\n- cpufreq: intel_pstate: Fix unchecked HWP MSR access (bsc#1234619).\n- cpufreq: intel_pstate: Fold intel_pstate_max_within_limits() into caller (bsc#1234619).\n- cpufreq: intel_pstate: Get rid of unnecessary READ_ONCE() annotations (bsc#1234619).\n- cpufreq: intel_pstate: Make hwp_notify_lock a raw spinlock (git-fixes).\n- cpufreq: intel_pstate: Read global.no_turbo under READ_ONCE() (bsc#1234619).\n- cpufreq: intel_pstate: Rearrange show_no_turbo() and store_no_turbo() (bsc#1234619).\n- cpufreq: intel_pstate: Refine computation of P-state for given frequency (bsc#1234619).\n- cpufreq: intel_pstate: Replace three global.turbo_disabled checks (bsc#1234619).\n- cpufreq: intel_pstate: Revise global turbo disable check (bsc#1234619).\n- cpufreq: intel_pstate: Simplify spinlock locking (bsc#1234619).\n- cpufreq: intel_pstate: Update the maximum CPU frequency consistently (bsc#1234619).\n- cpufreq: intel_pstate: Use HWP to initialize ITMT if CPPC is missing (git-fixes).\n- cpufreq: intel_pstate: Use __ro_after_init for three variables (bsc#1234619).\n- cpufreq: intel_pstate: Wait for canceled delayed work to complete (bsc#1234619).\n- cpufreq: intel_pstate: fix pstate limits enforcement for adjust_perf call back (git-fixes).\n- cpuidle: Avoid potential overflow in integer multiplication (git-fixes).\n- cpupower: fix TSC MHz calculation (git-fixes).\n- crypto: caam - use JobR's space to access page 0 regs (git-fixes).\n- crypto: ecc - Prevent ecc_digits_from_bytes from reading too many bytes (git-fixes).\n- crypto: ecdsa - Avoid signed integer overflow on signature decoding (stable-fixes).\n- crypto: ecdsa - Convert byte arrays with key coordinates to digits (stable-fixes).\n- crypto: ecdsa - Rename keylen to bufsize where necessary (stable-fixes).\n- crypto: ecdsa - Use ecc_digits_from_bytes to convert signature (stable-fixes).\n- crypto: iaa - Fix IAA disabling that occurs when sync_mode is set to 'async' (git-fixes).\n- crypto: ixp4xx - fix OF node reference leaks in init_ixp_crypto() (git-fixes).\n- crypto: qce - fix goto jump in error path (git-fixes).\n- crypto: qce - fix priority to be less than ARMv8 CE (git-fixes).\n- crypto: qce - unregister previously registered algos in error path (git-fixes).\n- devcoredump: cleanup some comments (git-fixes).\n- dlm: fix possible lkb_resource null dereference (git-fixes).\n- dmaengine: ti: edma: fix OF node reference leaks in edma_driver (git-fixes).\n- docs: media: update location of the media patches (stable-fixes).\n- docs: power: Fix footnote reference for Toshiba Satellite P10-554 (git-fixes).\n- driver core: class: Fix wild pointer dereferences in API class_dev_iter_next() (git-fixes).\n- drivers/card_reader/rtsx_usb: Restore interrupt based detection (git-fixes).\n- drm/amd/display: Add check for granularity in dml ceil/floor helpers (stable-fixes).\n- drm/amd/display: Fix DSC-re-computing (stable-fixes).\n- drm/amd/display: Fix incorrect DSC recompute trigger (stable-fixes).\n- drm/amd/display: Use HW lock mgr for PSR1 (stable-fixes).\n- drm/amd/display: increase MAX_SURFACES to the value supported by hw (stable-fixes).\n- drm/amd/pm: Fix an error handling path in vega10_enable_se_edc_force_stall_config() (git-fixes).\n- drm/amdgpu/vcn: reset fw_shared under SRIOV (git-fixes).\n- drm/amdgpu: Fix potential NULL pointer dereference in atomctrl_get_smc_sclk_range_table (git-fixes).\n- drm/amdgpu: always sync the GFX pipe on ctx switch (stable-fixes).\n- drm/amdgpu: simplify return statement in amdgpu_ras_eeprom_init (git-fixes).\n- drm/amdgpu: tear down ttm range manager for doorbell in amdgpu_ttm_fini() (git-fixes).\n- drm/amdkfd: Correct the migration DMA map direction (stable-fixes).\n- drm/amdkfd: fixed page fault when enable MES shader debugger (git-fixes).\n- drm/bridge: it6505: Change definition of AUX_FIFO_MAX_SIZE (git-fixes).\n- drm/etnaviv: Fix page property being used for non writecombine buffers (git-fixes).\n- drm/i915/fb: Relax clear color alignment to 64 bytes (stable-fixes).\n- drm/mediatek: Add return value check when reading DPCD (git-fixes).\n- drm/mediatek: Add support for 180-degree rotation in the display driver (git-fixes).\n- drm/mediatek: Fix YCbCr422 color format issue for DP (git-fixes).\n- drm/mediatek: Fix mode valid issue for dp (git-fixes).\n- drm/mediatek: Set private-\u003eall_drm_private[i]-\u003edrm to NULL if mtk_drm_bind returns err (git-fixes).\n- drm/mediatek: mtk_dsi: Add registers to pdata to fix MT8186/MT8188 (git-fixes).\n- drm/mediatek: stop selecting foreign drivers (git-fixes).\n- drm/msm/dp: set safe_to_exit_level before printing it (git-fixes).\n- drm/msm/dpu: link DSPP_2/_3 blocks on SC8180X (git-fixes).\n- drm/msm/dpu: link DSPP_2/_3 blocks on SM8150 (git-fixes).\n- drm/msm/dpu: link DSPP_2/_3 blocks on SM8250 (git-fixes).\n- drm/msm/dpu: link DSPP_2/_3 blocks on SM8350 (git-fixes).\n- drm/msm/dpu: link DSPP_2/_3 blocks on SM8550 (git-fixes).\n- drm/msm: Check return value of of_dma_configure() (git-fixes).\n- drm/msm: do not clean up priv-\u003ekms prematurely (git-fixes).\n- drm/rcar-du: dsi: Fix PHY lock bit check (git-fixes).\n- drm/rockchip: cdn-dp: Use drm_connector_helper_hpd_irq_event() (git-fixes).\n- drm/rockchip: vop2: Check linear format for Cluster windows on rk3566/8 (git-fixes).\n- drm/rockchip: vop2: Fix cluster windows alpha ctrl regsiters offset (git-fixes).\n- drm/rockchip: vop2: Fix the mixer alpha setup for layer 0 (git-fixes).\n- drm/tidss: Clear the interrupt status for interrupts being disabled (git-fixes).\n- drm/tidss: Fix issue in irq handling causing irq-flood issue (git-fixes).\n- drm/v3d: Assign job pointer to NULL before signaling the fence (git-fixes).\n- drm/v3d: Ensure job pointer is set to NULL after job completion (git-fixes).\n- drm/v3d: Stop active perfmon if it is being destroyed (git-fixes).\n- drm/vmwgfx: Add new keep_resv BO param (git-fixes).\n- exfat: ensure that ctime is updated whenever the mtime is (git-fixes).\n- exfat: fix the infinite loop in __exfat_free_cluster() (git-fixes).\n- exfat: fix the infinite loop in exfat_readdir() (git-fixes).\n- fbdev: omapfb: Fix an OF node leak in dss_of_port_get_parent_device() (git-fixes).\n- genirq: Make handle_enforce_irqctx() unconditionally available (git-fixes).\n- genksyms: fix memory leak when the same symbol is added from source (git-fixes).\n- genksyms: fix memory leak when the same symbol is read from *.symref file (git-fixes).\n- gfs2: Truncate address space when flipping GFS2_DIF_JDATA flag (git-fixes).\n- gpio: mxc: remove dead code after switch to DT-only (git-fixes).\n- gpio: xilinx: Convert gpio_lock to raw spinlock (git-fixes).\n- gtp: Use for_each_netdev_rcu() in gtp_genl_dump_pdp() (git-fixes).\n- hwmon: (drivetemp) Fix driver producing garbage data when SCSI errors occur (git-fixes).\n- hwmon: (drivetemp) Set scsi command timeout to 10s (stable-fixes).\n- hwmon: (tmp513) Fix division of negative numbers (git-fixes).\n- hyperv: Do not overlap the hvcall IO areas in get_vtl() (git-fixes).\n- i2c: core: fix reference leak in i2c_register_adapter() (git-fixes).\n- i2c: i801: Add support for Intel Arrow Lake-H (stable-fixes).\n- i2c: i801: Add support for Intel Panther Lake (stable-fixes).\n- i2c: mux: demux-pinctrl: check initial mux selection, too (git-fixes).\n- i2c: rcar: fix NACK handling when being a target (git-fixes).\n- i2c: xgene-slimpro: Migrate to use generic PCC shmem related macros (stable-fixes).\n- ibmvnic: Free any outstanding tx skbs during scrq reset (bsc#1226980).\n- ieee802154: ca8210: Add missing check for kfifo_alloc() in ca8210_probe() (git-fixes).\n- iio: adc: ad7124: Disable all channels at probe time (git-fixes).\n- iio: adc: ad_sigma_delta: Handle CS assertion as intended in ad_sd_read_reg_raw() (git-fixes).\n- iio: adc: at91: call input_free_device() on allocated iio_dev (git-fixes).\n- iio: adc: rockchip_saradc: fix information leak in triggered buffer (git-fixes).\n- iio: adc: ti-ads124s08: Use gpiod_set_value_cansleep() (git-fixes).\n- iio: adc: ti-ads8688: fix information leak in triggered buffer (git-fixes).\n- iio: dummy: iio_simply_dummy_buffer: fix information leak in triggered buffer (git-fixes).\n- iio: gyro: fxas21002c: Fix missing data update in trigger handler (git-fixes).\n- iio: iio-mux: kzalloc instead of devm_kzalloc to ensure page alignment (git-fixes).\n- iio: imu: kmx61: fix information leak in triggered buffer (git-fixes).\n- iio: inkern: call iio_device_put() only on mapped devices (git-fixes).\n- iio: light: as73211: fix channel handling in only-color triggered buffer (git-fixes).\n- iio: light: vcnl4035: fix information leak in triggered buffer (git-fixes).\n- iio: pressure: zpa2326: fix information leak in triggered buffer (git-fixes).\n- iio: test : check null return of kunit_kmalloc in iio_rescale_test_scale (git-fixes).\n- intel_th: core: fix kernel-doc warnings (git-fixes).\n- ipmi: ipmb: Add check devm_kasprintf() returned value (git-fixes).\n- ipmi: ssif_bmc: Fix new request loss when bmc ready for a response (git-fixes).\n- irqchip/gic-v3: Force propagation of the active state with a read-back (stable-fixes).\n- irqchip/gic: Correct declaration of *percpu_base pointer in union gic_base (stable-fixes).\n- kABI workaround for struct auto_pin_cfg_item change (git-fixes).\n- kconfig: fix file name in warnings when loading KCONFIG_DEFCONFIG_LIST (git-fixes).\n- kheaders: Ignore silly-rename files (stable-fixes).\n- ktest.pl: Avoid false positives with grub2 skip regex (stable-fixes).\n- ktest.pl: Check kernelrelease return in get_version (git-fixes).\n- ktest.pl: Fix typo 'accesing' (git-fixes).\n- ktest.pl: Fix typo in comment (git-fixes).\n- ktest.pl: Remove unused declarations in run_bisect_test function (git-fixes).\n- ktest: force $buildonly = 1 for 'make_warnings_file' test type (stable-fixes).\n- landlock: Handle weird files (git-fixes).\n- latencytop: use correct kernel-doc format for func params (git-fixes).\n- leds: lp8860: Write full EEPROM, not only half of it (git-fixes).\n- leds: netxbig: Fix an OF node reference leak in netxbig_leds_get_of_pdata() (git-fixes).\n- lib/inflate.c: remove dead code (git-fixes).\n- lib/stackdepot: print disabled message only if truly disabled (git-fixes).\n- mac802154: check local interfaces before deleting sdata list (stable-fixes).\n- mailbox: pcc: Add support for platform notification handling (stable-fixes).\n- mailbox: pcc: Support shared interrupt for multiple subspaces (stable-fixes).\n- mailbox: tegra-hsp: Clear mailbox before using message (git-fixes).\n- maple_tree: simplify split calculation (git-fixes).\n- media: camif-core: Add check for clk_enable() (git-fixes).\n- media: ccs: Clean up parsed CCS static data on parse failure (git-fixes).\n- media: ccs: Fix CCS static data parsing for large block sizes (git-fixes).\n- media: ccs: Fix cleanup order in ccs_probe() (git-fixes).\n- media: dvb-usb-v2: af9035: fix ISO C90 compilation error on af9035_i2c_master_xfer (git-fixes).\n- media: dvb: mb86a16: check the return value of mb86a16_read() (git-fixes).\n- media: firewire: firedtv-avc.c: replace BUG with proper, error return (git-fixes).\n- media: i2c: imx412: Add missing newline to prints (git-fixes).\n- media: i2c: ov9282: Correct the exposure offset (git-fixes).\n- media: imx-jpeg: Fix potential error pointer dereference in detach_pm() (git-fixes).\n- media: imx296: Add standby delay during probe (git-fixes).\n- media: lmedm04: Handle errors for lme2510_int_read (git-fixes).\n- media: marvell: Add check for clk_enable() (git-fixes).\n- media: mc: fix endpoint iteration (git-fixes).\n- media: mipi-csis: Add check for clk_enable() (git-fixes).\n- media: nxp: imx8-isi: fix v4l2-compliance test errors (git-fixes).\n- media: ov08x40: Fix hblank out of range issue (git-fixes).\n- media: ov5640: fix get_light_freq on auto (git-fixes).\n- media: rc: iguanair: handle timeouts (git-fixes).\n- media: rkisp1: Fix unused value issue (git-fixes).\n- media: uvcvideo: Drop uvcvideo fix due to regression (bsc#1235894)\n- media: uvcvideo: Fix crash during unbind if gpio unit is in use (git-fixes).\n- media: uvcvideo: Fix double free in error path (git-fixes).\n- media: uvcvideo: Fix event flags in uvc_ctrl_send_events (git-fixes).\n- media: uvcvideo: Force UVC version to 1.0a for 0408:4035 (stable-fixes).\n- media: uvcvideo: Only save async fh if success (git-fixes).\n- media: uvcvideo: Propagate buf-\u003eerror to userspace (git-fixes).\n- media: uvcvideo: Remove dangling pointers (git-fixes).\n- media: uvcvideo: Remove redundant NULL assignment (git-fixes).\n- media: uvcvideo: Support partial control reads (git-fixes).\n- memory tiering: count PGPROMOTE_SUCCESS when mem tiering is enabled (git-fixes).\n- memory-failure: use a folio in me_huge_page() (git-fixes).\n- memory: tegra20-emc: fix an OF node reference bug in tegra_emc_find_node_by_ram_code() (git-fixes).\n- misc: fastrpc: Deregister device nodes properly in error scenarios (git-fixes).\n- misc: fastrpc: Fix copy buffer page size (git-fixes).\n- misc: fastrpc: Fix registered buffer page address (git-fixes).\n- misc: microchip: pci1xxxx: Resolve kernel panic during GPIO IRQ handling (git-fixes).\n- misc: microchip: pci1xxxx: Resolve return code mismatch during GPIO set config (git-fixes).\n- misc: misc_minor_alloc to use ida for all dynamic/misc dynamic minors (git-fixes).\n- mm, kmsan: fix infinite recursion due to RCU critical section (git-fixes).\n- mm,page_owner: do not remove __GFP_NOLOCKDEP in add_stack_record_to_list (git-fixes).\n- mm/compaction: fix UBSAN shift-out-of-bounds warning (git fixes (mm/compaction)).\n- mm/memory-failure: cast index to loff_t before shifting it (git-fixes).\n- mm/memory-failure: check the mapcount of the precise page (git-fixes).\n- mm/memory-failure: fix crash in split_huge_page_to_list from soft_offline_page (git-fixes).\n- mm/memory-failure: pass the folio and the page to collect_procs() (git-fixes).\n- mm/memory-failure: use raw_spinlock_t in struct memory_failure_cpu (git-fixes).\n- mm/memory_hotplug: add missing mem_hotplug_lock (git-fixes).\n- mm/memory_hotplug: fix error handling in add_memory_resource() (git-fixes).\n- mm/memory_hotplug: prevent accessing by index=-1 (git-fixes).\n- mm/memory_hotplug: use pfn math in place of direct struct page manipulation (git-fixes).\n- mm/migrate: correct nr_failed in migrate_pages_sync() (git-fixes).\n- mm/migrate: fix deadlock in migrate_pages_batch() on large folios (git-fixes).\n- mm/migrate: putback split folios when numa hint migration fails (git-fixes).\n- mm/migrate: split source folio if it is on deferred split list (git-fixes).\n- mm/page_owner: remove free_ts from page_owner output (git-fixes).\n- mm/rodata_test: use READ_ONCE() to read const variable (git-fixes).\n- mm: convert DAX lock/unlock page to lock/unlock folio (git-fixes).\n- mm: memory-failure: ensure moving HWPoison flag to the raw error pages (git-fixes).\n- mm: memory-failure: fetch compound head after extra page refcnt is held (git-fixes).\n- mm: memory-failure: fix potential page refcnt leak in memory_failure() (git-fixes).\n- mm: memory-failure: fix race window when trying to get hugetlb folio (git-fixes).\n- mm: memory-failure: remove unneeded PageHuge() check (git-fixes).\n- mm: prevent derefencing NULL ptr in pfn_section_valid() (git-fixes).\n- modpost: fix the missed iteration for the max bit in do_input() (git-fixes).\n- mtd: onenand: Fix uninitialized retlen in do_otp_read() (git-fixes).\n- mtd: spinand: Remove write_enable_op() in markbad() (git-fixes).\n- net/rose: prevent integer overflows in rose_setsockopt() (git-fixes).\n- net: mana: Add get_link and get_link_ksettings in ethtool (bsc#1236761).\n- net: mana: Cleanup 'mana' debugfs dir after cleanup of all children (bsc#1236760).\n- net: mana: Enable debugfs files for MANA device (bsc#1236758).\n- net: netvsc: Update default VMBus channels (bsc#1236757).\n- net: phy: c45-tjaxx: add delay between MDIO write and read in soft_reset (git-fixes).\n- net: rose: fix timer races against user threads (git-fixes).\n- net: usb: qmi_wwan: add Telit FE910C04 compositions (stable-fixes).\n- net: usb: rtl8150: enable basic endpoint checking (git-fixes).\n- net: wwan: iosm: Properly check for valid exec stage in ipc_mmio_init() (git-fixes).\n- net: wwan: t7xx: Fix FSM command timeout issue (git-fixes).\n- netfilter: nf_tables: validate family when identifying table via handle (bsc#1233778 ZDI-24-1454).\n- nilfs2: fix possible int overflows in nilfs_fiemap() (git-fixes).\n- nvme-tcp: Fix I/O queue cpu spreading for multiple controllers (git-fixes).\n- nvme: Add error check for xa_store in nvme_get_effects_log (git-fixes).\n- nvme: Add error path for xa_store in nvme_init_effects (git-fixes).\n- nvme: fix bogus kzalloc() return check in nvme_init_effects_log() (git-fixes).\n- nvmet: propagate npwg topology (git-fixes).\n- ocfs2: temporarily disable upstream patch (bsc#1236138)\n- padata: add pd get/put refcnt helper (git-fixes).\n- padata: avoid UAF for reorder_work (git-fixes).\n- padata: fix UAF in padata_reorder (git-fixes).\n- pinctrl: amd: Take suspend type into consideration which pins are non-wake (git-fixes).\n- pinctrl: samsung: fix fwnode refcount cleanup if platform_get_irq_optional() fails (git-fixes).\n- platform/x86/amd/pmc: Only disable IRQ1 wakeup where i8042 actually enabled it (git-fixes).\n- platform/x86/intel-uncore-freq: Ignore minor version change (bsc#1225897).\n- platform/x86/intel/tpmi: Add defines to get version information (bsc#1225897).\n- pm:cpupower: Add missing powercap_set_enabled() stub function (git-fixes).\n- power: ip5xxx_power: Fix return value on ADC read errors (git-fixes).\n- powerpc/iommu: Move pSeries specific functions to pseries/iommu.c (bsc#1220711 ltc#205755).\n- powerpc/iommu: Only build sPAPR access functions on pSeries (bsc#1220711 ltc#205755).\n- powerpc/powernv/pci: Remove MVE code (bsc#1220711 ltc#205755).\n- powerpc/powernv/pci: Remove ioda1 support (bsc#1220711 ltc#205755).\n- powerpc/powernv/pci: Remove last IODA1 defines (bsc#1220711 ltc#205755).\n- powerpc/pseries/eeh: Fix get PE state translation (bsc#1215199).\n- powerpc/pseries/iommu: IOMMU incorrectly marks MMIO range in DDW (bsc#1218470 ltc#204531).\n- powerpc/pseries/vas: Add close() callback in vas_vm_ops struct (bsc#1234825).\n- pps: add an error check in parport_attach (git-fixes).\n- pps: remove usage of the deprecated ida_simple_xx() API (stable-fixes).\n- printk: Add is_printk_legacy_deferred() (bsc#1236733).\n- printk: Defer legacy printing when holding printk_cpu_sync (bsc#1236733).\n- pwm: stm32-lp: Add check for clk_enable() (git-fixes).\n- pwm: stm32: Add check for clk_enable() (git-fixes).\n- r8169: enable SG/TSO on selected chip versions per default (bsc#1235874).\n- rcu-tasks: Pull sampling of -\u003epercpu_dequeue_lim out of loop (git-fixes)\n- rcu/tree: Defer setting of jiffies during stall reset (git-fixes)\n- rcu: Dump memory object info if callback function is invalid (git-fixes)\n- rcu: Eliminate rcu_gp_slow_unregister() false positive (git-fixes)\n- rcuscale: Move rcu_scale_writer() (git-fixes)\n- rdma/cxgb4: Prevent potential integer overflow on 32bit (git-fixes)\n- regulator: core: Add missing newline character (git-fixes).\n- regulator: of: Implement the unwind path of of_regulator_match() (git-fixes).\n- remoteproc: core: Fix ida_free call while not allocated (git-fixes).\n- rtc: pcf85063: fix potential OOB write in PCF85063 NVMEM read (git-fixes).\n- rtc: zynqmp: Fix optional clock name property (git-fixes).\n- s390x config: IOMMU_DEFAULT_DMA_LAZY=y (bsc#1235646)\n- samples/landlock: Fix possible NULL dereference in parse_path() (git-fixes).\n- sched/fair: Fix value reported by hot tasks pulled in /proc/schedstat (bsc#1235865).\n- sched/fair: Fix value reported by hot tasks pulled in /proc/schedstat -kabi (bsc#1235865).\n- scsi: storvsc: Ratelimit warning logs to prevent VM denial of service (git-fixes).\n- seccomp: Stub for !CONFIG_SECCOMP (stable-fixes).\n- selftest: media_tests: fix trivial UAF typo (git-fixes).\n- selftests/alsa: Fix circular dependency involving global-timer (stable-fixes).\n- selftests/landlock: Fix error message (git-fixes).\n- selftests/mm/cow: modify the incorrect checking parameters (git-fixes).\n- selftests/powerpc: Fix argument order to timer_sub() (git-fixes).\n- selftests: harness: fix printing of mismatch values in __EXPECT() (git-fixes).\n- selftests: mptcp: avoid spurious errors on disconnect (git-fixes).\n- selftests: tc-testing: reduce rshift value (stable-fixes).\n- selftests: timers: clocksource-switch: Adapt progress to kselftest framework (git-fixes).\n- selinux: Fix SCTP error inconsistency in selinux_socket_bind() (git-fixes).\n- serial: 8250: Adjust the timeout for FIFO mode (git-fixes).\n- serial: sh-sci: Do not probe the serial port if its slot in sci_ports[] is in use (git-fixes).\n- serial: sh-sci: Drop __initdata macro for port_cfg (git-fixes).\n- soc: atmel: fix device_node release in atmel_soc_device_init() (git-fixes).\n- soc: mediatek: mtk-devapc: Fix leaking IO map on error paths (git-fixes).\n- soc: qcom: smem_state: fix missing of_node_put in error path (git-fixes).\n- soc: qcom: socinfo: Avoid out of bounds read of serial number (git-fixes).\n- sound: usb: enable DSD output for ddHiFi TC44C (stable-fixes).\n- sound: usb: format: do not warn that raw DSD is unsupported (stable-fixes).\n- spi: zynq-qspi: Add check for clk_enable() (git-fixes).\n- srcu: Fix srcu_struct node grpmask overflow on 64-bit systems (git-fixes)\n- srcu: Only accelerate on enqueue time (git-fixes)\n- stackdepot: rename pool_index to pool_index_plus_1 (git-fixes).\n- stackdepot: respect __GFP_NOLOCKDEP allocation flag (git-fixes).\n- staging: iio: ad9832: Correct phase range check (git-fixes).\n- staging: iio: ad9834: Correct phase range check (git-fixes).\n- staging: media: imx: fix OF node leak in imx_media_add_of_subdevs() (git-fixes).\n- staging: media: max96712: fix kernel oops when removing module (git-fixes).\n- thermal: of: fix OF node leak in of_thermal_zone_find() (git-fixes).\n- thunderbolt: Add support for Intel Lunar Lake (stable-fixes).\n- thunderbolt: Add support for Intel Panther Lake-M/P (stable-fixes).\n- tipc: fix NULL deref in cleanup_bearer() (bsc#1235433).\n- tools: Sync if_xdp.h uapi tooling header (git-fixes).\n- tpm: Map the ACPI provided event log (bsc#1233260 bsc#1233259 bsc#1232421).\n- tty: serial: 8250: Fix another runtime PM usage counter underflow (git-fixes).\n- tty: xilinx_uartps: split sysrq handling (git-fixes).\n- ubifs: skip dumping tnc tree when zroot is null (git-fixes).\n- uio: Fix return value of poll (git-fixes).\n- uio: uio_dmem_genirq: check the return value of devm_kasprintf() (git-fixes).\n- usb-storage: Add max sectors quirk for Nokia 208 (stable-fixes).\n- usb: chipidea: add CI_HDRC_FORCE_VBUS_ACTIVE_ALWAYS flag (stable-fixes).\n- usb: chipidea: ci_hdrc_imx: decrement device's refcount in .remove() and in the error path of .probe() (git-fixes).\n- usb: dwc3-am62: Disable autosuspend during remove (git-fixes).\n- usb: dwc3-am62: Fix an OF node leak in phy_syscon_pll_refclk() (git-fixes).\n- usb: dwc3: gadget: fix writing NYET threshold (git-fixes).\n- usb: fix reference leak in usb_new_device() (git-fixes).\n- usb: gadget: configfs: Ignore trailing LF for user strings to cdev (git-fixes).\n- usb: gadget: f_fs: Remove WARN_ON in functionfs_bind (git-fixes).\n- usb: gadget: f_tcm: Decrement command ref count on cleanup (git-fixes).\n- usb: gadget: f_tcm: Do not free command immediately (git-fixes).\n- usb: gadget: f_tcm: Do not prepare BOT write request twice (git-fixes).\n- usb: gadget: f_tcm: Fix Get/SetInterface return value (git-fixes).\n- usb: gadget: f_tcm: Translate error to sense (git-fixes).\n- usb: gadget: f_tcm: ep_autoconfig with fullspeed endpoint (git-fixes).\n- usb: gadget: f_uac2: Fix incorrect setting of bNumEndpoints (git-fixes).\n- usb: gadget: u_serial: Disable ep before setting port to null to fix the crash caused by port being null (git-fixes).\n- usb: host: xhci-plat: Assign shared_hcd-\u003ersrc_start (git-fixes).\n- usb: typec: fix pm usage counter imbalance in ucsi_ccg_sync_control() (bsc#1235001)\n- usb: typec: tcpm/tcpci_maxim: fix error code in max_contaminant_read_resistance_kohm() (git-fixes).\n- usb: typec: tcpm: set SRC_SEND_CAPABILITIES timeout to PD_T_SENDER_RESPONSE (git-fixes).\n- usbnet: ipheth: break up NCM header size computation (git-fixes).\n- usbnet: ipheth: check that DPE points past NCM header (git-fixes).\n- usbnet: ipheth: fix DPE OoB read (git-fixes).\n- usbnet: ipheth: fix possible overflow in DPE length check (git-fixes).\n- usbnet: ipheth: refactor NCM datagram loop (git-fixes).\n- usbnet: ipheth: use static NDP16 location in URB (git-fixes).\n- virtio-mem: check if the config changed before fake offlining memory (git-fixes).\n- virtio-mem: convert most offline_and_remove_memory() errors to -EBUSY (git-fixes).\n- virtio-mem: keep retrying on offline_and_remove_memory() errors in Sub Block Mode (SBM) (git-fixes).\n- virtio-mem: remove unsafe unplug in Big Block Mode (BBM) (git-fixes).\n- vmscan,migrate: fix page count imbalance on node stats when demoting pages (git-fixes).\n- vsock/virtio: cancel close work in the destructor (git-fixes)\n- vsock: Keep the binding until socket destruction (git-fixes)\n- vsock: reset socket state when de-assigning the transport (git-fixes)\n- watchdog: rzg2l_wdt: Power on the watchdog domain in the restart handler (stable-fixes).\n- watchdog: rzg2l_wdt: Rely on the reset driver for doing proper reset (stable-fixes).\n- watchdog: rzg2l_wdt: Remove reset de-assert from probe (stable-fixes).\n- wifi: ath11k: Fix unexpected return buffer manager error for WCN6750/WCN6855 (git-fixes).\n- wifi: ath11k: cleanup struct ath11k_mon_data (git-fixes).\n- wifi: ath12k: fix atomic calls in ath12k_mac_op_set_bitrate_mask() (stable-fixes).\n- wifi: ath12k: fix tx power, max reg power update to firmware (git-fixes).\n- wifi: brcmfmac: add missing header include for brcmf_dbg (git-fixes).\n- wifi: cfg80211: adjust allocation of colocated AP data (git-fixes).\n- wifi: iwlwifi: fw: read STEP table from correct UEFI var (git-fixes).\n- wifi: mac80211: Add non-atomic station iterator (stable-fixes).\n- wifi: mac80211: Fix common size calculation for ML element (git-fixes).\n- wifi: mac80211: do not flush non-uploaded STAs (git-fixes).\n- wifi: mac80211: export ieee80211_purge_tx_queue() for drivers (stable-fixes).\n- wifi: mac80211: fix mbss changed flags corruption on 32 bit systems (stable-fixes).\n- wifi: mac80211: fix tid removal during mesh forwarding (git-fixes).\n- wifi: mac80211: prohibit deactivating all links (git-fixes).\n- wifi: mac80211: wake the queues in case of failure in resume (stable-fixes).\n- wifi: mt76: mt76u_vendor_request: Do not print error messages when -EPROTO (git-fixes).\n- wifi: mt76: mt7915: Fix mesh scan on MT7916 DBDC (git-fixes).\n- wifi: mt76: mt7915: add module param to select 5 GHz or 6 GHz on MT7916 (git-fixes).\n- wifi: mt76: mt7915: firmware restart on devices with a second pcie link (git-fixes).\n- wifi: mt76: mt7915: fix overflows seen when writing limit attributes (git-fixes).\n- wifi: mt76: mt7915: fix register mapping (git-fixes).\n- wifi: mt76: mt7921: fix using incorrect group cipher after disconnection (git-fixes).\n- wifi: mt76: mt7925: fix off by one in mt7925_load_clc() (git-fixes).\n- wifi: mt76: mt7996: add max mpdu len capability (git-fixes).\n- wifi: mt76: mt7996: fix HE Phy capability (git-fixes).\n- wifi: mt76: mt7996: fix definition of tx descriptor (git-fixes).\n- wifi: mt76: mt7996: fix incorrect indexing of MIB FW event (git-fixes).\n- wifi: mt76: mt7996: fix ldpc setting (git-fixes).\n- wifi: mt76: mt7996: fix overflows seen when writing limit attributes (git-fixes).\n- wifi: mt76: mt7996: fix register mapping (git-fixes).\n- wifi: mt76: mt7996: fix rx filter setting for bfee functionality (git-fixes).\n- wifi: mt76: mt7996: fix the capability of reception of EHT MU PPDU (git-fixes).\n- wifi: rtlwifi: destroy workqueue at rtl_deinit_core (git-fixes).\n- wifi: rtlwifi: do not complete firmware loading needlessly (git-fixes).\n- wifi: rtlwifi: fix init_sw_vars leak when probe fails (git-fixes).\n- wifi: rtlwifi: fix memory leaks and invalid access at probe error path (git-fixes).\n- wifi: rtlwifi: pci: wait for firmware loading before releasing memory (git-fixes).\n- wifi: rtlwifi: remove unused check_buddy_priv (git-fixes).\n- wifi: rtlwifi: rtl8192se: rise completion of firmware loading as last step (git-fixes).\n- wifi: rtlwifi: rtl8821ae: Fix media status report (git-fixes).\n- wifi: rtlwifi: rtl8821ae: phy: restore removed code to fix infinite loop (git-fixes).\n- wifi: rtlwifi: usb: fix workqueue leak when probe fails (git-fixes).\n- wifi: rtlwifi: wait for firmware loading before releasing memory (git-fixes).\n- wifi: rtw88: use ieee80211_purge_tx_queue() to purge TX skb (stable-fixes).\n- wifi: rtw89: mcc: consider time limits not divisible by 1024 (git-fixes).\n- wifi: wcn36xx: fix channel survey memory allocation size (git-fixes).\n- wifi: wlcore: fix unbalanced pm_runtime calls (git-fixes).\n- workqueue: Add rcu lock check at the end of work item execution (bsc#1236732).\n- x86/static-call: Remove early_boot_irqs_disabled check to fix Xen PVH dom0 (git-fixes).\n- xfs: Add error handling for xfs_reflink_cancel_cow_range (git-fixes).\n- xfs: Propagate errors from xfs_reflink_cancel_cow_range in xfs_dax_write_iomap_end (git-fixes).\n","status":"published","published":"2025-02-13T08:14:44Z","modified":"2026-02-04T03:46:09.495439Z","updated_at":"2026-11-02T15:53:58.883365Z"},{"id":"SUSE-SU-2025:0557-1","title":"Security update for the Linux Kernel","description":"\nThe SUSE Linux Enterprise 15 SP6 RT kernel was updated to receive various security bugfixes.\n\n\nThe following security bugs were fixed:\n\n- CVE-2024-45828: i3c: mipi-i3c-hci: Mask ring interrupts before ring stop request (bsc#1235705).\n- CVE-2024-46858: mptcp: pm: Fix uaf in __timer_delete_sync (bsc#1231088).\n- CVE-2024-48881: bcache: revert replacing IS_ERR_OR_NULL with IS_ERR again (bsc#1235727).\n- CVE-2024-49948: net: add more sanity checks to qdisc_pkt_len_init() (bsc#1232161).\n- CVE-2024-49951: Bluetooth: MGMT: Fix possible crash on mgmt_index_removed (bsc#1232158).\n- CVE-2024-49978: gso: fix udp gso fraglist segmentation after pull from frag_list (bsc#1232101).\n- CVE-2024-49998: net: dsa: improve shutdown sequence (bsc#1232087).\n- CVE-2024-50151: smb: client: fix OOBs when building SMB2_IOCTL request (bsc#1233055).\n- CVE-2024-50199: mm/swapfile: skip HugeTLB pages for unuse_vma (bsc#1233112).\n- CVE-2024-50251: netfilter: nft_payload: sanitize offset and length before calling skb_checksum() (bsc#1233248).\n- CVE-2024-50258: net: fix crash when config small gso_max_size/gso_ipv4_max_size (bsc#1233221).\n- CVE-2024-50299: sctp: properly validate chunk size in sctp_sf_ootb() (bsc#1233488).\n- CVE-2024-50304: ipv4: ip_tunnel: Fix suspicious RCU usage warning in ip_tunnel_find() (bsc#1233522).\n- CVE-2024-53091: bpf: Add sk_is_inet and IS_ICSK check in tls_sw_has_ctx_tx/rx (bsc#1233638).\n- CVE-2024-53164: net: sched: fix ordering of qlen adjustment (bsc#1234863).\n- CVE-2024-53170: block: fix uaf for flush rq while iterating tags (bsc#1234888).\n- CVE-2024-53172: ubi: fastmap: Fix duplicate slab cache names while attaching (bsc#1234898).\n- CVE-2024-53175: ipc: fix memleak if msg_init_ns failed in create_ipc_ns (bsc#1234893).\n- CVE-2024-53185: smb: client: fix NULL ptr deref in crypto_aead_setkey() (bsc#1234901).\n- CVE-2024-53187: io_uring: check for overflows in io_pin_pages (bsc#1234947).\n- CVE-2024-53195: KVM: arm64: Get rid of userspace_irqchip_in_use (bsc#1234957).\n- CVE-2024-53196: KVM: arm64: Do not retire aborted MMIO instruction (bsc#1234906).\n- CVE-2024-53198: xen: Fix the issue of resource not being properly released in xenbus_dev_probe() (bsc#1234923).\n- CVE-2024-53203: usb: typec: fix potential array underflow in ucsi_ccg_sync_control() (bsc#1235001).\n- CVE-2024-53227: scsi: bfa: Fix use-after-free in bfad_im_module_exit() (bsc#1235011).\n- CVE-2024-53232: iommu/s390: Implement blocking domain (bsc#1235050).\n- CVE-2024-53236: xsk: Free skb when TX metadata options are invalid (bsc#1235000).\n- CVE-2024-53685: ceph: give up on paths longer than PATH_MAX (bsc#1235720).\n- CVE-2024-55639: net: renesas: rswitch: avoid use-after-put for a device tree node (bsc#1235737).\n- CVE-2024-55881: KVM: x86: Play nice with protected guests in complete_hypercall_exit() (bsc#1235745).\n- CVE-2024-56372: net: tun: fix tun_napi_alloc_frags() (bsc#1235753).\n- CVE-2024-56568: iommu/arm-smmu: Defer probe of clients after smmu device bound (bsc#1235032).\n- CVE-2024-56569: ftrace: Fix regression with module command in stack_trace_filter (bsc#1235031).\n- CVE-2024-56570: ovl: Filter invalid inodes with missing lookup function (bsc#1235035).\n- CVE-2024-56588: scsi: hisi_sas: Create all dump files during debugfs initialization (bsc#1235123).\n- CVE-2024-56589: scsi: hisi_sas: Add cond_resched() for no forced preemption model (bsc#1235241).\n- CVE-2024-56592: bpf: Call free_htab_elem() after htab_unlock_bucket() (bsc#1235244).\n- CVE-2024-56600: net: inet6: do not leave a dangling sk pointer in inet6_create() (bsc#1235217).\n- CVE-2024-56601: net: inet: do not leave a dangling sk pointer in inet_create() (bsc#1235230).\n- CVE-2024-56602: net: ieee802154: do not leave a dangling sk pointer in ieee802154_create() (bsc#1235521).\n- CVE-2024-56603: net: af_can: do not leave a dangling sk pointer in can_create() (bsc#1235415).\n- CVE-2024-56608: drm/amd/display: Fix out-of-bounds access in 'dcn21_link_encoder_create' (bsc#1235487).\n- CVE-2024-56610: kcsan: Turn report_filterlist_lock into a raw_spinlock (bsc#1235390).\n- CVE-2024-56611: mm/mempolicy: fix migrate_to_node() assuming there is at least one VMA in a MM (bsc#1235391).\n- CVE-2024-56614: xsk: fix OOB map writes when deleting elements (bsc#1235424).\n- CVE-2024-56615: bpf: fix OOB devmap writes when deleting elements (bsc#1235426).\n- CVE-2024-56617: cacheinfo: Allocate memory during CPU hotplug if not done from the primary CPU (bsc#1235429).\n- CVE-2024-56620: scsi: ufs: qcom: Only free platform MSIs when ESI is enabled (bsc#1235227).\n- CVE-2024-56622: scsi: ufs: core: sysfs: Prevent div by zero (bsc#1235251).\n- CVE-2024-56631: scsi: sg: Fix slab-use-after-free read in sg_release() (bsc#1235480).\n- CVE-2024-56635: net: avoid potential UAF in default_operstate() (bsc#1235519).\n- CVE-2024-56636: geneve: do not assume mac header is set in geneve_xmit_skb() (bsc#1235520).\n- CVE-2024-56637: netfilter: ipset: Hold module reference while requesting a module (bsc#1235523).\n- CVE-2024-56641: net/smc: initialize close_work early to avoid warning (bsc#1235526).\n- CVE-2024-56643: dccp: Fix memory leak in dccp_feat_change_recv (bsc#1235132).\n- CVE-2024-56648: net: hsr: avoid potential out-of-bound access in fill_frame_info() (bsc#1235451).\n- CVE-2024-56649: net: enetc: Do not configure preemptible TCs if SIs do not support (bsc#1235449).\n- CVE-2024-56650: netfilter: x_tables: fix LED ID check in led_tg_check() (bsc#1235430).\n- CVE-2024-56656: bnxt_en: Fix aggregation ID mask to prevent oops on 5760X chips (bsc#1235444).\n- CVE-2024-56658: net: defer final 'struct net' free in netns dismantle (bsc#1235441).\n- CVE-2024-56659: net: lapb: increase LAPB_HEADER_LEN (bsc#1235439).\n- CVE-2024-56660: net/mlx5: DR, prevent potential error pointer dereference (bsc#1235437).\n- CVE-2024-56664: bpf, sockmap: Fix race between element replace and close() (bsc#1235249).\n- CVE-2024-56665: bpf,perf: Fix invalid prog_array access in perf_event_detach_bpf_prog (bsc#1235489).\n- CVE-2024-56675: bpf: Fix UAF via mismatching bpf_prog/attachment RCU flavors (bsc#1235555).\n- CVE-2024-56679: octeontx2-pf: handle otx2_mbox_get_rsp errors in otx2_common.c (bsc#1235498).\n- CVE-2024-56693: brd: defer automatic disk creation until module initialization succeeds (bsc#1235418).\n- CVE-2024-56694: bpf: fix recursive lock when verdict program return SK_PASS (bsc#1235412).\n- CVE-2024-56704: 9p/xen: fix release of IRQ (bsc#1235584).\n- CVE-2024-56707: octeontx2-pf: handle otx2_mbox_get_rsp errors in otx2_dmac_flt.c (bsc#1235545).\n- CVE-2024-56708: EDAC/igen6: Avoid segmentation fault on module unload (bsc#1235564).\n- CVE-2024-56712: udmabuf: fix memory leak on last export_udmabuf() error path (bsc#1235565).\n- CVE-2024-56715: ionic: Fix netdev notifier unregister on failure (bsc#1235612).\n- CVE-2024-56716: netdevsim: prevent bad user input in nsim_dev_health_break_write() (bsc#1235587).\n- CVE-2024-56725: octeontx2-pf: handle otx2_mbox_get_rsp errors in otx2_dcbnl.c (bsc#1235578).\n- CVE-2024-56726: octeontx2-pf: handle otx2_mbox_get_rsp errors in cn10k.c (bsc#1235582).\n- CVE-2024-56727: octeontx2-pf: handle otx2_mbox_get_rsp errors in otx2_flows.c (bsc#1235583).\n- CVE-2024-56728: octeontx2-pf: handle otx2_mbox_get_rsp errors in otx2_ethtool.c (bsc#1235656).\n- CVE-2024-56729: smb: Initialize cfid-\u003etcon before performing network ops (bsc#1235503).\n- CVE-2024-56747: scsi: qedi: Fix a possible memory leak in qedi_alloc_and_init_sb() (bsc#1234934).\n- CVE-2024-56748: scsi: qedf: Fix a possible memory leak in qedf_alloc_and_init_sb() (bsc#1235627).\n- CVE-2024-56759: btrfs: fix use-after-free when COWing tree bock and tracing is enabled (bsc#1235645).\n- CVE-2024-56763: tracing: Prevent bad count for tracing_cpumask_write (bsc#1235638).\n- CVE-2024-56774: btrfs: add a sanity check for btrfs root in btrfs_search_slot() (bsc#1235653).\n- CVE-2024-56775: drm/amd/display: Fix handling of plane refcount (bsc#1235657).\n- CVE-2024-57791: net/smc: check return value of sock_recvmsg when draining clc data (bsc#1235759).\n- CVE-2024-57793: virt: tdx-guest: Just leak decrypted memory on unrecoverable errors (bsc#1235768).\n- CVE-2024-57795: RDMA/rxe: Remove the direct link to net_device (bsc#1235906).\n- CVE-2024-57801: net/mlx5e: Skip restore TC rules for vport rep without loaded flag (bsc#1235940).\n- CVE-2024-57802: netrom: check buffer length before accessing it (bsc#1235941).\n- CVE-2024-57804: scsi: mpi3mr: Fix corrupt config pages PHY state is switched in sysfs (bsc#1235779).\n- CVE-2024-57809: PCI: imx6: Fix suspend/resume support on i.MX6QDL (bsc#1235793).\n- CVE-2024-57838: s390/entry: Mark IRQ entries to fix stack depot warnings (bsc#1235798).\n- CVE-2024-57857: RDMA/siw: Remove direct link to net_device (bsc#1235946).\n- CVE-2024-57882: mptcp: fix TCP options overflow. (bsc#1235914).\n- CVE-2024-57884: mm: vmscan: account for free pages to prevent infinite Loop in throttle_direct_reclaim() (bsc#1235948).\n- CVE-2024-57892: ocfs2: fix slab-use-after-free due to dangling pointer dqi_priv (bsc#1235964).\n- CVE-2024-57896: btrfs: flush delalloc workers queue before stopping cleaner kthread during unmount (bsc#1235965).\n- CVE-2024-57903: net: restrict SO_REUSEPORT to inet sockets (bsc#1235967).\n- CVE-2024-57917: topology: Keep the cpumask unchanged when printing cpumap (bsc#1236127).\n- CVE-2024-57929: dm array: fix releasing a faulty array block twice in dm_array_cursor_end (bsc#1236096).\n- CVE-2024-57931: selinux: ignore unknown extended permissions (bsc#1236192).\n- CVE-2024-57932: gve: guard XDP xmit NDO on existence of xdp queues (bsc#1236190).\n- CVE-2024-57933: gve: guard XSK operations on the existence of queues (bsc#1236178).\n- CVE-2024-57938: net/sctp: Prevent autoclose integer overflow in sctp_association_init() (bsc#1236182).\n- CVE-2024-57946: virtio-blk: do not keep queue frozen during system suspend (bsc#1236247).\n- CVE-2025-21632: x86/fpu: Ensure shadow stack is active before 'getting' registers (bsc#1236106).\n- CVE-2025-21649: net: hns3: fix kernel crash when 1588 is sent on HIP08 devices (bsc#1236143).\n- CVE-2025-21650: net: hns3: fixed hclge_fetch_pf_reg accesses bar space out of bounds issue (bsc#1236144).\n- CVE-2025-21651: net: hns3: do not auto enable misc vector (bsc#1236145).\n- CVE-2025-21652: ipvlan: Fix use-after-free in ipvlan_get_iflink() (bsc#1236160).\n- CVE-2025-21653: net_sched: cls_flow: validate TCA_FLOW_RSHIFT attribute (bsc#1236161).\n- CVE-2025-21655: io_uring/eventfd: ensure io_eventfd_signal() defers another RCU period (bsc#1236163).\n- CVE-2025-21662: net/mlx5: Fix variable not being completed when function returns (bsc#1236198).\n- CVE-2025-21663: net: stmmac: dwmac-tegra: Read iommu stream id from device tree (bsc#1236260).\n- CVE-2025-21664: dm thin: make get_first_thin use rcu-safe list first function (bsc#1236262).\n- CVE-2025-21666: vsock: prevent null-ptr-deref in vsock_*[has_data|has_space] (bsc#1236680).\n- CVE-2025-21669: vsock/virtio: discard packets if the transport changes (bsc#1236683).\n- CVE-2025-21670: vsock/bpf: return early if transport is not assigned (bsc#1236685).\n- CVE-2025-21674: net/mlx5e: Fix inversion dependency warning while enabling IPsec tunnel (bsc#1236688).\n- CVE-2025-21675: net/mlx5: Clear port select structure when fail to create (bsc#1236694).\n- CVE-2025-21676: net: fec: handle page_pool_dev_alloc_pages error (bsc#1236696).\n- CVE-2025-21678: gtp: Destroy device along with udp socket's netns dismantle (bsc#1236698).\n- CVE-2025-21682: eth: bnxt: always recalculate features after XDP clearing, fix null-deref (bsc#1236703).\n\nThe following non-security bugs were fixed:\n\n- ACPI/IORT: Add PMCG platform information for HiSilicon HIP09A (stable-fixes).\n- ACPI/IORT: Add PMCG platform information for HiSilicon HIP10/11 (stable-fixes).\n- ACPI: PCC: Add PCC shared memory region command and status bitfields (stable-fixes).\n- ACPI: fan: cleanup resources in the error path of .probe() (git-fixes).\n- ACPI: resource: Add Asus Vivobook X1504VAP to irq1_level_low_skip_override[] (stable-fixes).\n- ACPI: resource: Add TongFang GM5HG0A to irq1_edge_low_force_override[] (stable-fixes).\n- ACPI: resource: acpi_dev_irq_override(): Check DMI match last (stable-fixes).\n- ALSA: hda/realtek - Add support for ASUS Zen AIO 27 Z272SD_A272SD audio (stable-fixes).\n- ALSA: hda/realtek - Fixed headphone distorted sound on Acer Aspire A115-31 laptop (git-fixes).\n- ALSA: hda/realtek: Add new alc2xx-fixup-headset-mic model (stable-fixes).\n- ALSA: hda/realtek: Add support for Ayaneo System using CS35L41 HDA (stable-fixes).\n- ALSA: hda/realtek: Add support for Galaxy Book2 Pro (NP950XEE) (stable-fixes).\n- ALSA: hda/realtek: Enable Mute LED on HP Laptop 14s-fq1xxx (stable-fixes).\n- ALSA: hda/realtek: Enable headset mic on Positivo C6400 (stable-fixes).\n- ALSA: hda/realtek: Workaround for resume on Dell Venue 11 Pro 7130 (bsc#1235686).\n- ALSA: hda: Fix headset detection failure due to unstable sort (git-fixes).\n- ALSA: ump: Use guard() for locking (stable-fixes).\n- ALSA: usb-audio: Add delay quirk for USB Audio Device (stable-fixes).\n- ALSA: usb-audio: Add delay quirk for iBasso DC07 Pro (stable-fixes).\n- ASoC: Intel: avs: Fix theoretical infinite loop (git-fixes).\n- ASoC: acp: Support microphone from Lenovo Go S (stable-fixes).\n- ASoC: mediatek: disable buffer pre-allocation (stable-fixes).\n- ASoC: rockchip: i2s_tdm: Re-add the set_sysclk callback (git-fixes).\n- ASoC: rt722: add delay time to wait for the calibration procedure (stable-fixes).\n- ASoC: samsung: Add missing depends on I2C (git-fixes).\n- ASoC: samsung: Add missing selects for MFD_WM8994 (stable-fixes).\n- ASoC: sun4i-spdif: Add clock multiplier settings (git-fixes).\n- ASoC: wm8994: Add depends on MFD core (stable-fixes).\n- Align git commit ID abbreviation guidelines and checks (git-fixes).\n- Bluetooth: Add support ITTIM PE50-M75C (stable-fixes).\n- Bluetooth: L2CAP: accept zero as a special value for MTU auto-selection (git-fixes).\n- Bluetooth: L2CAP: handle NULL sock pointer in l2cap_sock_alloc (git-fixes).\n- Bluetooth: MGMT: Fix Add Device to responding before completing (git-fixes).\n- Bluetooth: btnxpuart: Fix driver sending truncated data (git-fixes).\n- Bluetooth: btnxpuart: Fix glitches seen in dual A2DP streaming (git-fixes).\n- Bluetooth: btusb: Add USB HW IDs for MT7921/MT7922/MT7925 (stable-fixes).\n- Bluetooth: btusb: Add new VID/PID 0489/e111 for MT7925 (stable-fixes).\n- Bluetooth: btusb: Add new VID/PID 13d3/3602 for MT7925 (stable-fixes).\n- Bluetooth: btusb: add callback function in btusb suspend/resume (stable-fixes).\n- Bluetooth: btusb: mediatek: add callback function in btusb_disconnect (stable-fixes).\n- Bluetooth: hci_sync: Fix not setting Random Address when required (git-fixes).\n- uvcvideo: drop fix due to regression (bsc#1235894)\n- EDAC/{i10nm,skx,skx_common}: Support UV systems (bsc#1234693).\n- HID: core: Fix assumption that Resolution Multipliers must be in Logical Collections (git-fixes).\n- HID: fix generic desktop D-Pad controls (git-fixes).\n- HID: hid-sensor-hub: do not use stale platform-data on remove (git-fixes).\n- HID: hid-thrustmaster: Fix warning in thrustmaster_probe by adding endpoint check (git-fixes).\n- HID: multitouch: fix support for Goodix PID 0x01e9 (git-fixes).\n- Input: atkbd - map F23 key to support default copilot shortcut (stable-fixes).\n- Input: bbnsm_pwrkey - add remove hook (git-fixes).\n- Input: bbnsm_pwrkey - fix missed key press after suspend (git-fixes).\n- Input: davinci-keyscan - remove leftover header (git-fixes).\n- Input: xpad - add QH Electronics VID/PID (stable-fixes).\n- Input: xpad - add support for Nacon Evol-X Xbox One Controller (stable-fixes).\n- Input: xpad - add support for Nacon Pro Compact (stable-fixes).\n- Input: xpad - add support for wooting two he (arm) (stable-fixes).\n- Input: xpad - add unofficial Xbox 360 wireless receiver clone (stable-fixes).\n- Input: xpad - improve name of 8BitDo controller 2dc8:3106 (stable-fixes).\n- KVM: SVM: Allow guest writes to set MSR_AMD64_DE_CFG bits (bsc#1234635).\n- KVM: s390: Reject KVM_SET_GSI_ROUTING on ucontrol VMs (git-fixes bsc#1235776).\n- KVM: s390: Reject setting flic pfault attributes on ucontrol VMs (git-fixes bsc#1235777).\n- KVM: s390: vsie: fix virtual/physical address in unpin_scb() (git-fixes bsc#1235778).\n- Move upstreamed DRM patch into sorted section\n- Move upstreamed NFS patch into sorted section\n- Move upstreamed TPM patch into sorted section\n- Move upstreamed lpfc patches into sorted section\n- Move upstreamed ppc patch into sorted section\n- Move upstreamed sound patch into sorted section\n- NFC: nci: Add bounds checking in nci_hci_create_pipe() (git-fixes).\n- NFSv4.2: fix COPY_NOTIFY xdr buf size calculation (git-fixes).\n- NFSv4.2: mark OFFLOAD_CANCEL MOVEABLE (git-fixes).\n- PCI: Avoid putting some root ports into D3 on TUXEDO Sirius Gen1 (git-fixes).\n- PCI: dwc: Always stop link in the dw_pcie_suspend_noirq (git-fixes).\n- PCI: dwc: ep: Prevent changing BAR size/flags in pci_epc_set_bar() (git-fixes).\n- PCI: dwc: ep: Write BAR_MASK before iATU registers in pci_epc_set_bar() (git-fixes).\n- PCI: endpoint: Destroy the EPC device in devm_pci_epc_destroy() (git-fixes).\n- PCI: endpoint: Finish virtual EP removal in pci_epf_remove_vepf() (git-fixes).\n- PCI: endpoint: pci-epf-test: Fix check for DMA MEMCPY test (git-fixes).\n- PCI: endpoint: pci-epf-test: Set dma_chan_rx pointer to NULL on error (git-fixes).\n- PCI: imx6: Deassert apps_reset in imx_pcie_deassert_core_reset() (git-fixes).\n- PCI: imx6: Skip controller_id generation logic for i.MX7D (git-fixes).\n- PCI: microchip: Set inbound address translation for coherent or non-coherent mode (git-fixes).\n- PCI: rcar-ep: Fix incorrect variable used when calling devm_request_mem_region() (git-fixes).\n- PM: hibernate: Add error handling for syscore_suspend() (git-fixes).\n- RDMA/bnxt_re: Add send queue size check for variable wqe (git-fixes)\n- RDMA/bnxt_re: Fix MSN table size for variable wqe mode (git-fixes)\n- RDMA/bnxt_re: Fix max SGEs for the Work Request (git-fixes)\n- RDMA/bnxt_re: Fix the max WQE size for static WQE support (git-fixes)\n- RDMA/bnxt_re: Fix the max WQEs used in Static WQE mode (git-fixes)\n- RDMA/bnxt_re: Fix to drop reference to the mmap entry in case of error (git-fixes)\n- RDMA/bnxt_re: Fix to export port num to ib_query_qp (git-fixes)\n- RDMA/mlx4: Avoid false error about access to uninitialized gids array (git-fixes)\n- RDMA/mlx5: Fix a race for an ODP MR which leads to CQE with error (git-fixes)\n- RDMA/mlx5: Fix implicit ODP use after free (git-fixes)\n- RDMA/mlx5: Fix indirect mkey ODP page count (git-fixes)\n- RDMA/rxe: Fix mismatched max_msg_sz (git-fixes)\n- RDMA/rxe: Fix the warning '__rxe_cleanup+0x12c/0x170 [rdma_rxe]' (git-fixes)\n- RDMA/srp: Fix error handling in srp_add_port (git-fixes)\n- USB: core: Disable LPM only for non-suspended ports (git-fixes).\n- USB: serial: cp210x: add Phoenix Contact UPS Device (stable-fixes).\n- USB: serial: option: add MeiG Smart SRM815 (stable-fixes).\n- USB: serial: option: add Neoway N723-EA support (stable-fixes).\n- USB: serial: quatech2: fix null-ptr-deref in qt2_process_read_urb() (git-fixes).\n- USB: usblp: return error when setting unsupported protocol (git-fixes).\n- Update patches.suse/nvme-tcp-Fix-I-O-queue-cpu-spreading-for-multiple-co.patch (git-fixes bsc#1224049).\n- VFS: use system_unbound_wq for delayed_mntput (bsc#1234683).\n- VMCI: fix reference to ioctl-number.rst (git-fixes).\n- afs: Fix EEXIST error returned from afs_rmdir() to be ENOTEMPTY (git-fixes).\n- afs: Fix cleanup of immediately failed async calls (git-fixes).\n- afs: Fix directory format encoding struct (git-fixes).\n- afs: Fix the fallback handling for the YFS.RemoveFile2 RPC call (git-fixes).\n- afs: Fix the maximum cell name length (git-fixes).\n- arm64/sme: Move storage of reg_smidr to __cpuinfo_store_cpu() (git-fixes)\n- arm64: Filter out SVE hwcaps when FEAT_SVE isn't implemented (git-fixes)\n- arm64: Kconfig: Make SME depend on BROKEN for now (git-fixes bsc#1236245).\n- arm64: dts: rockchip: Add sdmmc/sdio/emmc reset controls for RK3328 (git-fixes)\n- arm64: dts: rockchip: add hevc power domain clock to rk3328 (git-fixes).\n- arm64: dts: rockchip: increase gmac rx_delay on rk3399-puma (git-fixes)\n- arm64: ptrace: fix partial SETREGSET for NT_ARM_TAGGED_ADDR_CTRL (git-fixes).\n- arm64: tegra: Disable Tegra234 sce-fabric node (git-fixes)\n- arm64: tegra: Fix Tegra234 PCIe interrupt-map (git-fixes)\n- arm64: tegra: Fix typo in Tegra234 dce-fabric compatible (git-fixes)\n- ata: libata-core: Set ATA_QCFLAG_RTF_FILLED in fill_result_tf() (stable-fixes).\n- bnxt_en: Fix GSO type for HW GRO packets on 5750X chips (git-fixes)\n- btrfs: fix use-after-free in btrfs_encoded_read_endio() (bsc#1235445).\n- btrfs: fix use-after-free waiting for encoded read endios (bsc#1235445).\n- bus: mhi: host: Free mhi_buf vector inside mhi_alloc_bhie_table() (git-fixes).\n- ceph: improve error handling and short/overflow-read logic in __ceph_sync_read() (bsc#1228592).\n- cleanup: Add conditional guard support (stable-fixes).\n- cleanup: Adjust scoped_guard() macros to avoid potential warning (stable-fixes).\n- cleanup: Remove address space of returned pointer (git-fixes).\n- cpufreq: ACPI: Fix max-frequency computation (git-fixes).\n- cpufreq: Do not unregister cpufreq cooling on CPU hotplug (git-fixes).\n- cpufreq: amd-pstate: remove global header file (git-fixes).\n- cpufreq: intel_pstate: Check turbo_is_disabled() in store_no_turbo() (bsc#1234619).\n- cpufreq: intel_pstate: Do not update global.turbo_disabled after initialization (bsc#1234619).\n- cpufreq: intel_pstate: Drop redundant locking from intel_pstate_driver_cleanup() (bsc#1234619).\n- cpufreq: intel_pstate: Fix unchecked HWP MSR access (bsc#1234619).\n- cpufreq: intel_pstate: Fold intel_pstate_max_within_limits() into caller (bsc#1234619).\n- cpufreq: intel_pstate: Get rid of unnecessary READ_ONCE() annotations (bsc#1234619).\n- cpufreq: intel_pstate: Make hwp_notify_lock a raw spinlock (git-fixes).\n- cpufreq: intel_pstate: Read global.no_turbo under READ_ONCE() (bsc#1234619).\n- cpufreq: intel_pstate: Rearrange show_no_turbo() and store_no_turbo() (bsc#1234619).\n- cpufreq: intel_pstate: Refine computation of P-state for given frequency (bsc#1234619).\n- cpufreq: intel_pstate: Replace three global.turbo_disabled checks (bsc#1234619).\n- cpufreq: intel_pstate: Revise global turbo disable check (bsc#1234619).\n- cpufreq: intel_pstate: Simplify spinlock locking (bsc#1234619).\n- cpufreq: intel_pstate: Update the maximum CPU frequency consistently (bsc#1234619).\n- cpufreq: intel_pstate: Use HWP to initialize ITMT if CPPC is missing (git-fixes).\n- cpufreq: intel_pstate: Use __ro_after_init for three variables (bsc#1234619).\n- cpufreq: intel_pstate: Wait for canceled delayed work to complete (bsc#1234619).\n- cpufreq: intel_pstate: fix pstate limits enforcement for adjust_perf call back (git-fixes).\n- cpuidle: Avoid potential overflow in integer multiplication (git-fixes).\n- cpupower: fix TSC MHz calculation (git-fixes).\n- crypto: caam - use JobR's space to access page 0 regs (git-fixes).\n- crypto: ecc - Prevent ecc_digits_from_bytes from reading too many bytes (git-fixes).\n- crypto: ecdsa - Avoid signed integer overflow on signature decoding (stable-fixes).\n- crypto: ecdsa - Convert byte arrays with key coordinates to digits (stable-fixes).\n- crypto: ecdsa - Rename keylen to bufsize where necessary (stable-fixes).\n- crypto: ecdsa - Use ecc_digits_from_bytes to convert signature (stable-fixes).\n- crypto: iaa - Fix IAA disabling that occurs when sync_mode is set to 'async' (git-fixes).\n- crypto: ixp4xx - fix OF node reference leaks in init_ixp_crypto() (git-fixes).\n- crypto: qce - fix goto jump in error path (git-fixes).\n- crypto: qce - fix priority to be less than ARMv8 CE (git-fixes).\n- crypto: qce - unregister previously registered algos in error path (git-fixes).\n- devcoredump: cleanup some comments (git-fixes).\n- dlm: fix possible lkb_resource null dereference (git-fixes).\n- dmaengine: ti: edma: fix OF node reference leaks in edma_driver (git-fixes).\n- doc/README.SUSE: Point to the updated version of LKMPG\n- docs: media: update location of the media patches (stable-fixes).\n- docs: power: Fix footnote reference for Toshiba Satellite P10-554 (git-fixes).\n- driver core: class: Fix wild pointer dereferences in API class_dev_iter_next() (git-fixes).\n- drivers/card_reader/rtsx_usb: Restore interrupt based detection (git-fixes).\n- drm/amd/display: Add check for granularity in dml ceil/floor helpers (stable-fixes).\n- drm/amd/display: Fix DSC-re-computing (stable-fixes).\n- drm/amd/display: Fix incorrect DSC recompute trigger (stable-fixes).\n- drm/amd/display: Use HW lock mgr for PSR1 (stable-fixes).\n- drm/amd/display: increase MAX_SURFACES to the value supported by hw (stable-fixes).\n- drm/amd/pm: Fix an error handling path in vega10_enable_se_edc_force_stall_config() (git-fixes).\n- drm/amdgpu/vcn: reset fw_shared under SRIOV (git-fixes).\n- drm/amdgpu: Fix potential NULL pointer dereference in atomctrl_get_smc_sclk_range_table (git-fixes).\n- drm/amdgpu: always sync the GFX pipe on ctx switch (stable-fixes).\n- drm/amdgpu: simplify return statement in amdgpu_ras_eeprom_init (git-fixes).\n- drm/amdgpu: tear down ttm range manager for doorbell in amdgpu_ttm_fini() (git-fixes).\n- drm/amdkfd: Correct the migration DMA map direction (stable-fixes).\n- drm/amdkfd: fixed page fault when enable MES shader debugger (git-fixes).\n- drm/bridge: it6505: Change definition of AUX_FIFO_MAX_SIZE (git-fixes).\n- drm/etnaviv: Fix page property being used for non writecombine buffers (git-fixes).\n- drm/i915/fb: Relax clear color alignment to 64 bytes (stable-fixes).\n- drm/mediatek: Add return value check when reading DPCD (git-fixes).\n- drm/mediatek: Add support for 180-degree rotation in the display driver (git-fixes).\n- drm/mediatek: Fix YCbCr422 color format issue for DP (git-fixes).\n- drm/mediatek: Fix mode valid issue for dp (git-fixes).\n- drm/mediatek: Set private-\u003eall_drm_private[i]-\u003edrm to NULL if mtk_drm_bind returns err (git-fixes).\n- drm/mediatek: mtk_dsi: Add registers to pdata to fix MT8186/MT8188 (git-fixes).\n- drm/mediatek: stop selecting foreign drivers (git-fixes).\n- drm/msm/dp: set safe_to_exit_level before printing it (git-fixes).\n- drm/msm/dpu: link DSPP_2/_3 blocks on SC8180X (git-fixes).\n- drm/msm/dpu: link DSPP_2/_3 blocks on SM8150 (git-fixes).\n- drm/msm/dpu: link DSPP_2/_3 blocks on SM8250 (git-fixes).\n- drm/msm/dpu: link DSPP_2/_3 blocks on SM8350 (git-fixes).\n- drm/msm/dpu: link DSPP_2/_3 blocks on SM8550 (git-fixes).\n- drm/msm: Check return value of of_dma_configure() (git-fixes).\n- drm/msm: do not clean up priv-\u003ekms prematurely (git-fixes).\n- drm/rcar-du: dsi: Fix PHY lock bit check (git-fixes).\n- drm/rockchip: cdn-dp: Use drm_connector_helper_hpd_irq_event() (git-fixes).\n- drm/rockchip: vop2: Check linear format for Cluster windows on rk3566/8 (git-fixes).\n- drm/rockchip: vop2: Fix cluster windows alpha ctrl regsiters offset (git-fixes).\n- drm/rockchip: vop2: Fix the mixer alpha setup for layer 0 (git-fixes).\n- drm/tidss: Clear the interrupt status for interrupts being disabled (git-fixes).\n- drm/tidss: Fix issue in irq handling causing irq-flood issue (git-fixes).\n- drm/v3d: Assign job pointer to NULL before signaling the fence (git-fixes).\n- drm/v3d: Ensure job pointer is set to NULL after job completion (git-fixes).\n- drm/v3d: Stop active perfmon if it is being destroyed (git-fixes).\n- drm/vmwgfx: Add new keep_resv BO param (git-fixes).\n- exfat: ensure that ctime is updated whenever the mtime is (git-fixes).\n- exfat: fix the infinite loop in __exfat_free_cluster() (git-fixes).\n- exfat: fix the infinite loop in exfat_readdir() (git-fixes).\n- fbdev: omapfb: Fix an OF node leak in dss_of_port_get_parent_device() (git-fixes).\n- genirq: Make handle_enforce_irqctx() unconditionally available (git-fixes).\n- genksyms: fix memory leak when the same symbol is added from source (git-fixes).\n- genksyms: fix memory leak when the same symbol is read from *.symref file (git-fixes).\n- gfs2: Truncate address space when flipping GFS2_DIF_JDATA flag (git-fixes).\n- gpio: mxc: remove dead code after switch to DT-only (git-fixes).\n- gpio: xilinx: Convert gpio_lock to raw spinlock (git-fixes).\n- gtp: Use for_each_netdev_rcu() in gtp_genl_dump_pdp() (git-fixes).\n- hwmon: (drivetemp) Fix driver producing garbage data when SCSI errors occur (git-fixes).\n- hwmon: (drivetemp) Set scsi command timeout to 10s (stable-fixes).\n- hwmon: (tmp513) Fix division of negative numbers (git-fixes).\n- hyperv: Do not overlap the hvcall IO areas in get_vtl() (git-fixes).\n- i2c: core: fix reference leak in i2c_register_adapter() (git-fixes).\n- i2c: i801: Add support for Intel Arrow Lake-H (stable-fixes).\n- i2c: i801: Add support for Intel Panther Lake (stable-fixes).\n- i2c: mux: demux-pinctrl: check initial mux selection, too (git-fixes).\n- i2c: rcar: fix NACK handling when being a target (git-fixes).\n- i2c: xgene-slimpro: Migrate to use generic PCC shmem related macros (stable-fixes).\n- ibmvnic: Free any outstanding tx skbs during scrq reset (bsc#1226980).\n- ieee802154: ca8210: Add missing check for kfifo_alloc() in ca8210_probe() (git-fixes).\n- iio: adc: ad7124: Disable all channels at probe time (git-fixes).\n- iio: adc: ad_sigma_delta: Handle CS assertion as intended in ad_sd_read_reg_raw() (git-fixes).\n- iio: adc: at91: call input_free_device() on allocated iio_dev (git-fixes).\n- iio: adc: rockchip_saradc: fix information leak in triggered buffer (git-fixes).\n- iio: adc: ti-ads124s08: Use gpiod_set_value_cansleep() (git-fixes).\n- iio: adc: ti-ads8688: fix information leak in triggered buffer (git-fixes).\n- iio: dummy: iio_simply_dummy_buffer: fix information leak in triggered buffer (git-fixes).\n- iio: gyro: fxas21002c: Fix missing data update in trigger handler (git-fixes).\n- iio: iio-mux: kzalloc instead of devm_kzalloc to ensure page alignment (git-fixes).\n- iio: imu: kmx61: fix information leak in triggered buffer (git-fixes).\n- iio: inkern: call iio_device_put() only on mapped devices (git-fixes).\n- iio: light: as73211: fix channel handling in only-color triggered buffer (git-fixes).\n- iio: light: vcnl4035: fix information leak in triggered buffer (git-fixes).\n- iio: pressure: zpa2326: fix information leak in triggered buffer (git-fixes).\n- iio: test : check null return of kunit_kmalloc in iio_rescale_test_scale (git-fixes).\n- intel_th: core: fix kernel-doc warnings (git-fixes).\n- ipmi: ipmb: Add check devm_kasprintf() returned value (git-fixes).\n- ipmi: ssif_bmc: Fix new request loss when bmc ready for a response (git-fixes).\n- irqchip/gic-v3: Force propagation of the active state with a read-back (stable-fixes).\n- irqchip/gic: Correct declaration of *percpu_base pointer in union gic_base (stable-fixes).\n- kABI workaround for struct auto_pin_cfg_item change (git-fixes).\n- kconfig: fix file name in warnings when loading KCONFIG_DEFCONFIG_LIST (git-fixes).\n- kheaders: Ignore silly-rename files (stable-fixes).\n- ktest.pl: Avoid false positives with grub2 skip regex (stable-fixes).\n- ktest.pl: Check kernelrelease return in get_version (git-fixes).\n- ktest.pl: Fix typo 'accesing' (git-fixes).\n- ktest.pl: Fix typo in comment (git-fixes).\n- ktest.pl: Remove unused declarations in run_bisect_test function (git-fixes).\n- ktest: force $buildonly = 1 for 'make_warnings_file' test type (stable-fixes).\n- landlock: Handle weird files (git-fixes).\n- latencytop: use correct kernel-doc format for func params (git-fixes).\n- leds: lp8860: Write full EEPROM, not only half of it (git-fixes).\n- leds: netxbig: Fix an OF node reference leak in netxbig_leds_get_of_pdata() (git-fixes).\n- lib/inflate.c: remove dead code (git-fixes).\n- lib/stackdepot: print disabled message only if truly disabled (git-fixes).\n- mac802154: check local interfaces before deleting sdata list (stable-fixes).\n- mailbox: pcc: Add support for platform notification handling (stable-fixes).\n- mailbox: pcc: Support shared interrupt for multiple subspaces (stable-fixes).\n- mailbox: tegra-hsp: Clear mailbox before using message (git-fixes).\n- maple_tree: simplify split calculation (git-fixes).\n- media: camif-core: Add check for clk_enable() (git-fixes).\n- media: ccs: Clean up parsed CCS static data on parse failure (git-fixes).\n- media: ccs: Fix CCS static data parsing for large block sizes (git-fixes).\n- media: ccs: Fix cleanup order in ccs_probe() (git-fixes).\n- media: dvb-usb-v2: af9035: fix ISO C90 compilation error on af9035_i2c_master_xfer (git-fixes).\n- media: dvb: mb86a16: check the return value of mb86a16_read() (git-fixes).\n- media: firewire: firedtv-avc.c: replace BUG with proper, error return (git-fixes).\n- media: i2c: imx412: Add missing newline to prints (git-fixes).\n- media: i2c: ov9282: Correct the exposure offset (git-fixes).\n- media: imx-jpeg: Fix potential error pointer dereference in detach_pm() (git-fixes).\n- media: imx296: Add standby delay during probe (git-fixes).\n- media: lmedm04: Handle errors for lme2510_int_read (git-fixes).\n- media: marvell: Add check for clk_enable() (git-fixes).\n- media: mc: fix endpoint iteration (git-fixes).\n- media: mipi-csis: Add check for clk_enable() (git-fixes).\n- media: nxp: imx8-isi: fix v4l2-compliance test errors (git-fixes).\n- media: ov08x40: Fix hblank out of range issue (git-fixes).\n- media: ov5640: fix get_light_freq on auto (git-fixes).\n- media: rc: iguanair: handle timeouts (git-fixes).\n- media: rkisp1: Fix unused value issue (git-fixes).\n- media: uvcvideo: Fix crash during unbind if gpio unit is in use (git-fixes).\n- media: uvcvideo: Fix double free in error path (git-fixes).\n- media: uvcvideo: Fix event flags in uvc_ctrl_send_events (git-fixes).\n- media: uvcvideo: Force UVC version to 1.0a for 0408:4035 (stable-fixes).\n- media: uvcvideo: Only save async fh if success (git-fixes).\n- media: uvcvideo: Propagate buf-\u003eerror to userspace (git-fixes).\n- media: uvcvideo: Remove dangling pointers (git-fixes).\n- media: uvcvideo: Remove redundant NULL assignment (git-fixes).\n- media: uvcvideo: Support partial control reads (git-fixes).\n- memory tiering: count PGPROMOTE_SUCCESS when mem tiering is enabled (git-fixes).\n- memory-failure: use a folio in me_huge_page() (git-fixes).\n- memory: tegra20-emc: fix an OF node reference bug in tegra_emc_find_node_by_ram_code() (git-fixes).\n- misc: fastrpc: Deregister device nodes properly in error scenarios (git-fixes).\n- misc: fastrpc: Fix copy buffer page size (git-fixes).\n- misc: fastrpc: Fix registered buffer page address (git-fixes).\n- misc: microchip: pci1xxxx: Resolve kernel panic during GPIO IRQ handling (git-fixes).\n- misc: microchip: pci1xxxx: Resolve return code mismatch during GPIO set config (git-fixes).\n- misc: misc_minor_alloc to use ida for all dynamic/misc dynamic minors (git-fixes).\n- mm, kmsan: fix infinite recursion due to RCU critical section (git-fixes).\n- mm,page_owner: do not remove __GFP_NOLOCKDEP in add_stack_record_to_list (git-fixes).\n- mm/compaction: fix UBSAN shift-out-of-bounds warning (git fixes (mm/compaction)).\n- mm/memory-failure: cast index to loff_t before shifting it (git-fixes).\n- mm/memory-failure: check the mapcount of the precise page (git-fixes).\n- mm/memory-failure: fix crash in split_huge_page_to_list from soft_offline_page (git-fixes).\n- mm/memory-failure: pass the folio and the page to collect_procs() (git-fixes).\n- mm/memory-failure: use raw_spinlock_t in struct memory_failure_cpu (git-fixes).\n- mm/memory_hotplug: add missing mem_hotplug_lock (git-fixes).\n- mm/memory_hotplug: fix error handling in add_memory_resource() (git-fixes).\n- mm/memory_hotplug: prevent accessing by index=-1 (git-fixes).\n- mm/memory_hotplug: use pfn math in place of direct struct page manipulation (git-fixes).\n- mm/migrate: correct nr_failed in migrate_pages_sync() (git-fixes).\n- mm/migrate: fix deadlock in migrate_pages_batch() on large folios (git-fixes).\n- mm/migrate: putback split folios when numa hint migration fails (git-fixes).\n- mm/migrate: split source folio if it is on deferred split list (git-fixes).\n- mm/page_owner: remove free_ts from page_owner output (git-fixes).\n- mm/rodata_test: use READ_ONCE() to read const variable (git-fixes).\n- mm: convert DAX lock/unlock page to lock/unlock folio (git-fixes).\n- mm: memory-failure: ensure moving HWPoison flag to the raw error pages (git-fixes).\n- mm: memory-failure: fetch compound head after extra page refcnt is held (git-fixes).\n- mm: memory-failure: fix potential page refcnt leak in memory_failure() (git-fixes).\n- mm: memory-failure: fix race window when trying to get hugetlb folio (git-fixes).\n- mm: memory-failure: remove unneeded PageHuge() check (git-fixes).\n- mm: prevent derefencing NULL ptr in pfn_section_valid() (git-fixes).\n- modpost: fix the missed iteration for the max bit in do_input() (git-fixes).\n- mtd: onenand: Fix uninitialized retlen in do_otp_read() (git-fixes).\n- mtd: spinand: Remove write_enable_op() in markbad() (git-fixes).\n- net/rose: prevent integer overflows in rose_setsockopt() (git-fixes).\n- net: mana: Add get_link and get_link_ksettings in ethtool (bsc#1236761).\n- net: mana: Cleanup 'mana' debugfs dir after cleanup of all children (bsc#1236760).\n- net: mana: Enable debugfs files for MANA device (bsc#1236758).\n- net: netvsc: Update default VMBus channels (bsc#1236757).\n- net: phy: c45-tjaxx: add delay between MDIO write and read in soft_reset (git-fixes).\n- net: rose: fix timer races against user threads (git-fixes).\n- net: usb: qmi_wwan: add Telit FE910C04 compositions (stable-fixes).\n- net: usb: rtl8150: enable basic endpoint checking (git-fixes).\n- net: wwan: iosm: Properly check for valid exec stage in ipc_mmio_init() (git-fixes).\n- net: wwan: t7xx: Fix FSM command timeout issue (git-fixes).\n- netfilter: nf_tables: validate family when identifying table via handle (bsc#1233778 ZDI-24-1454).\n- nilfs2: fix possible int overflows in nilfs_fiemap() (git-fixes).\n- nvme-tcp: Fix I/O queue cpu spreading for multiple controllers (git-fixes).\n- nvme: Add error check for xa_store in nvme_get_effects_log (git-fixes).\n- nvme: Add error path for xa_store in nvme_init_effects (git-fixes).\n- nvme: fix bogus kzalloc() return check in nvme_init_effects_log() (git-fixes).\n- nvmet: propagate npwg topology (git-fixes).\n- padata: add pd get/put refcnt helper (git-fixes).\n- padata: avoid UAF for reorder_work (git-fixes).\n- padata: fix UAF in padata_reorder (git-fixes).\n- pinctrl: amd: Take suspend type into consideration which pins are non-wake (git-fixes).\n- pinctrl: samsung: fix fwnode refcount cleanup if platform_get_irq_optional() fails (git-fixes).\n- platform/x86/amd/pmc: Only disable IRQ1 wakeup where i8042 actually enabled it (git-fixes).\n- platform/x86/intel-uncore-freq: Ignore minor version change (bsc#1225897).\n- platform/x86/intel/tpmi: Add defines to get version information (bsc#1225897).\n- pm:cpupower: Add missing powercap_set_enabled() stub function (git-fixes).\n- power: ip5xxx_power: Fix return value on ADC read errors (git-fixes).\n- powerpc/iommu: Move pSeries specific functions to pseries/iommu.c (bsc#1220711 ltc#205755).\n- powerpc/iommu: Only build sPAPR access functions on pSeries (bsc#1220711 ltc#205755).\n- powerpc/powernv/pci: Remove MVE code (bsc#1220711 ltc#205755).\n- powerpc/powernv/pci: Remove ioda1 support (bsc#1220711 ltc#205755).\n- powerpc/powernv/pci: Remove last IODA1 defines (bsc#1220711 ltc#205755).\n- powerpc/pseries/eeh: Fix get PE state translation (bsc#1215199).\n- powerpc/pseries/iommu: IOMMU incorrectly marks MMIO range in DDW (bsc#1218470 ltc#204531).\n- powerpc/pseries/vas: Add close() callback in vas_vm_ops struct (bsc#1234825).\n- pps: add an error check in parport_attach (git-fixes).\n- pps: remove usage of the deprecated ida_simple_xx() API (stable-fixes).\n- printk: Add is_printk_legacy_deferred() (bsc#1236733).\n- printk: Defer legacy printing when holding printk_cpu_sync (bsc#1236733).\n- pwm: stm32-lp: Add check for clk_enable() (git-fixes).\n- pwm: stm32: Add check for clk_enable() (git-fixes).\n- r8169: enable SG/TSO on selected chip versions per default (bsc#1235874).\n- rcu-tasks: Pull sampling of -\u003epercpu_dequeue_lim out of loop (git-fixes)\n- rcu/tree: Defer setting of jiffies during stall reset (git-fixes)\n- rcu: Dump memory object info if callback function is invalid (git-fixes)\n- rcu: Eliminate rcu_gp_slow_unregister() false positive (git-fixes)\n- rcuscale: Move rcu_scale_writer() (git-fixes)\n- rdma/cxgb4: Prevent potential integer overflow on 32bit (git-fixes)\n- regulator: core: Add missing newline character (git-fixes).\n- regulator: of: Implement the unwind path of of_regulator_match() (git-fixes).\n- remoteproc: core: Fix ida_free call while not allocated (git-fixes).\n- rtc: pcf85063: fix potential OOB write in PCF85063 NVMEM read (git-fixes).\n- rtc: zynqmp: Fix optional clock name property (git-fixes).\n- s390x config: IOMMU_DEFAULT_DMA_LAZY=y (bsc#1235646)\n- samples/landlock: Fix possible NULL dereference in parse_path() (git-fixes).\n- sched/fair: Fix value reported by hot tasks pulled in /proc/schedstat (bsc#1235865).\n- sched/fair: Fix value reported by hot tasks pulled in /proc/schedstat -kabi (bsc#1235865).\n- scsi: storvsc: Ratelimit warning logs to prevent VM denial of service (git-fixes).\n- seccomp: Stub for !CONFIG_SECCOMP (stable-fixes).\n- selftest: media_tests: fix trivial UAF typo (git-fixes).\n- selftests/alsa: Fix circular dependency involving global-timer (stable-fixes).\n- selftests/landlock: Fix error message (git-fixes).\n- selftests/mm/cow: modify the incorrect checking parameters (git-fixes).\n- selftests/powerpc: Fix argument order to timer_sub() (git-fixes).\n- selftests: harness: fix printing of mismatch values in __EXPECT() (git-fixes).\n- selftests: mptcp: avoid spurious errors on disconnect (git-fixes).\n- selftests: tc-testing: reduce rshift value (stable-fixes).\n- selftests: timers: clocksource-switch: Adapt progress to kselftest framework (git-fixes).\n- selinux: Fix SCTP error inconsistency in selinux_socket_bind() (git-fixes).\n- serial: 8250: Adjust the timeout for FIFO mode (git-fixes).\n- serial: sh-sci: Do not probe the serial port if its slot in sci_ports[] is in use (git-fixes).\n- serial: sh-sci: Drop __initdata macro for port_cfg (git-fixes).\n- ocfs2: temporarily disable upstream patch (bsc#1236138).\n- soc: atmel: fix device_node release in atmel_soc_device_init() (git-fixes).\n- soc: mediatek: mtk-devapc: Fix leaking IO map on error paths (git-fixes).\n- soc: qcom: smem_state: fix missing of_node_put in error path (git-fixes).\n- soc: qcom: socinfo: Avoid out of bounds read of serial number (git-fixes).\n- sound: usb: enable DSD output for ddHiFi TC44C (stable-fixes).\n- sound: usb: format: do not warn that raw DSD is unsupported (stable-fixes).\n- spi: zynq-qspi: Add check for clk_enable() (git-fixes).\n- srcu: Fix srcu_struct node grpmask overflow on 64-bit systems (git-fixes)\n- srcu: Only accelerate on enqueue time (git-fixes)\n- stackdepot: rename pool_index to pool_index_plus_1 (git-fixes).\n- stackdepot: respect __GFP_NOLOCKDEP allocation flag (git-fixes).\n- staging: iio: ad9832: Correct phase range check (git-fixes).\n- staging: iio: ad9834: Correct phase range check (git-fixes).\n- staging: media: imx: fix OF node leak in imx_media_add_of_subdevs() (git-fixes).\n- staging: media: max96712: fix kernel oops when removing module (git-fixes).\n- thermal: of: fix OF node leak in of_thermal_zone_find() (git-fixes).\n- thunderbolt: Add support for Intel Lunar Lake (stable-fixes).\n- thunderbolt: Add support for Intel Panther Lake-M/P (stable-fixes).\n- tipc: fix NULL deref in cleanup_bearer() (bsc#1235433).\n- tools: Sync if_xdp.h uapi tooling header (git-fixes).\n- tpm: Map the ACPI provided event log (bsc#1233260 bsc#1233259 bsc#1232421).\n- tty: serial: 8250: Fix another runtime PM usage counter underflow (git-fixes).\n- tty: xilinx_uartps: split sysrq handling (git-fixes).\n- ubifs: skip dumping tnc tree when zroot is null (git-fixes).\n- uio: Fix return value of poll (git-fixes).\n- uio: uio_dmem_genirq: check the return value of devm_kasprintf() (git-fixes).\n- usb-storage: Add max sectors quirk for Nokia 208 (stable-fixes).\n- usb: chipidea: add CI_HDRC_FORCE_VBUS_ACTIVE_ALWAYS flag (stable-fixes).\n- usb: chipidea: ci_hdrc_imx: decrement device's refcount in .remove() and in the error path of .probe() (git-fixes).\n- usb: dwc3-am62: Disable autosuspend during remove (git-fixes).\n- usb: dwc3-am62: Fix an OF node leak in phy_syscon_pll_refclk() (git-fixes).\n- usb: dwc3: gadget: fix writing NYET threshold (git-fixes).\n- usb: fix reference leak in usb_new_device() (git-fixes).\n- usb: gadget: configfs: Ignore trailing LF for user strings to cdev (git-fixes).\n- usb: gadget: f_fs: Remove WARN_ON in functionfs_bind (git-fixes).\n- usb: gadget: f_tcm: Decrement command ref count on cleanup (git-fixes).\n- usb: gadget: f_tcm: Do not free command immediately (git-fixes).\n- usb: gadget: f_tcm: Do not prepare BOT write request twice (git-fixes).\n- usb: gadget: f_tcm: Fix Get/SetInterface return value (git-fixes).\n- usb: gadget: f_tcm: Translate error to sense (git-fixes).\n- usb: gadget: f_tcm: ep_autoconfig with fullspeed endpoint (git-fixes).\n- usb: gadget: f_uac2: Fix incorrect setting of bNumEndpoints (git-fixes).\n- usb: gadget: u_serial: Disable ep before setting port to null to fix the crash caused by port being null (git-fixes).\n- usb: host: xhci-plat: Assign shared_hcd-\u003ersrc_start (git-fixes).\n- usb: typec: fix pm usage counter imbalance in ucsi_ccg_sync_control() (bsc#1235001)\n- usb: typec: tcpm/tcpci_maxim: fix error code in max_contaminant_read_resistance_kohm() (git-fixes).\n- usb: typec: tcpm: set SRC_SEND_CAPABILITIES timeout to PD_T_SENDER_RESPONSE (git-fixes).\n- usbnet: ipheth: break up NCM header size computation (git-fixes).\n- usbnet: ipheth: check that DPE points past NCM header (git-fixes).\n- usbnet: ipheth: fix DPE OoB read (git-fixes).\n- usbnet: ipheth: fix possible overflow in DPE length check (git-fixes).\n- usbnet: ipheth: refactor NCM datagram loop (git-fixes).\n- usbnet: ipheth: use static NDP16 location in URB (git-fixes).\n- vfio/pci: Lock external INTx masking ops (bsc#1222803).\n- virtio-mem: check if the config changed before fake offlining memory (git-fixes).\n- virtio-mem: convert most offline_and_remove_memory() errors to -EBUSY (git-fixes).\n- virtio-mem: keep retrying on offline_and_remove_memory() errors in Sub Block Mode (SBM) (git-fixes).\n- virtio-mem: remove unsafe unplug in Big Block Mode (BBM) (git-fixes).\n- vmscan,migrate: fix page count imbalance on node stats when demoting pages (git-fixes).\n- vsock/virtio: cancel close work in the destructor (git-fixes)\n- vsock: Keep the binding until socket destruction (git-fixes)\n- vsock: reset socket state when de-assigning the transport (git-fixes)\n- watchdog: rzg2l_wdt: Power on the watchdog domain in the restart handler (stable-fixes).\n- watchdog: rzg2l_wdt: Rely on the reset driver for doing proper reset (stable-fixes).\n- watchdog: rzg2l_wdt: Remove reset de-assert from probe (stable-fixes).\n- wifi: ath11k: Fix unexpected return buffer manager error for WCN6750/WCN6855 (git-fixes).\n- wifi: ath11k: cleanup struct ath11k_mon_data (git-fixes).\n- wifi: ath12k: fix atomic calls in ath12k_mac_op_set_bitrate_mask() (stable-fixes).\n- wifi: ath12k: fix tx power, max reg power update to firmware (git-fixes).\n- wifi: brcmfmac: add missing header include for brcmf_dbg (git-fixes).\n- wifi: cfg80211: adjust allocation of colocated AP data (git-fixes).\n- wifi: iwlwifi: fw: read STEP table from correct UEFI var (git-fixes).\n- wifi: mac80211: Add non-atomic station iterator (stable-fixes).\n- wifi: mac80211: Fix common size calculation for ML element (git-fixes).\n- wifi: mac80211: do not flush non-uploaded STAs (git-fixes).\n- wifi: mac80211: export ieee80211_purge_tx_queue() for drivers (stable-fixes).\n- wifi: mac80211: fix mbss changed flags corruption on 32 bit systems (stable-fixes).\n- wifi: mac80211: fix tid removal during mesh forwarding (git-fixes).\n- wifi: mac80211: prohibit deactivating all links (git-fixes).\n- wifi: mac80211: wake the queues in case of failure in resume (stable-fixes).\n- wifi: mt76: mt76u_vendor_request: Do not print error messages when -EPROTO (git-fixes).\n- wifi: mt76: mt7915: Fix mesh scan on MT7916 DBDC (git-fixes).\n- wifi: mt76: mt7915: add module param to select 5 GHz or 6 GHz on MT7916 (git-fixes).\n- wifi: mt76: mt7915: firmware restart on devices with a second pcie link (git-fixes).\n- wifi: mt76: mt7915: fix overflows seen when writing limit attributes (git-fixes).\n- wifi: mt76: mt7915: fix register mapping (git-fixes).\n- wifi: mt76: mt7921: fix using incorrect group cipher after disconnection (git-fixes).\n- wifi: mt76: mt7925: fix off by one in mt7925_load_clc() (git-fixes).\n- wifi: mt76: mt7996: add max mpdu len capability (git-fixes).\n- wifi: mt76: mt7996: fix HE Phy capability (git-fixes).\n- wifi: mt76: mt7996: fix definition of tx descriptor (git-fixes).\n- wifi: mt76: mt7996: fix incorrect indexing of MIB FW event (git-fixes).\n- wifi: mt76: mt7996: fix ldpc setting (git-fixes).\n- wifi: mt76: mt7996: fix overflows seen when writing limit attributes (git-fixes).\n- wifi: mt76: mt7996: fix register mapping (git-fixes).\n- wifi: mt76: mt7996: fix rx filter setting for bfee functionality (git-fixes).\n- wifi: mt76: mt7996: fix the capability of reception of EHT MU PPDU (git-fixes).\n- wifi: rtlwifi: destroy workqueue at rtl_deinit_core (git-fixes).\n- wifi: rtlwifi: do not complete firmware loading needlessly (git-fixes).\n- wifi: rtlwifi: fix init_sw_vars leak when probe fails (git-fixes).\n- wifi: rtlwifi: fix memory leaks and invalid access at probe error path (git-fixes).\n- wifi: rtlwifi: pci: wait for firmware loading before releasing memory (git-fixes).\n- wifi: rtlwifi: remove unused check_buddy_priv (git-fixes).\n- wifi: rtlwifi: rtl8192se: rise completion of firmware loading as last step (git-fixes).\n- wifi: rtlwifi: rtl8821ae: Fix media status report (git-fixes).\n- wifi: rtlwifi: rtl8821ae: phy: restore removed code to fix infinite loop (git-fixes).\n- wifi: rtlwifi: usb: fix workqueue leak when probe fails (git-fixes).\n- wifi: rtlwifi: wait for firmware loading before releasing memory (git-fixes).\n- wifi: rtw88: use ieee80211_purge_tx_queue() to purge TX skb (stable-fixes).\n- wifi: rtw89: mcc: consider time limits not divisible by 1024 (git-fixes).\n- wifi: wcn36xx: fix channel survey memory allocation size (git-fixes).\n- wifi: wlcore: fix unbalanced pm_runtime calls (git-fixes).\n- workqueue: Add rcu lock check at the end of work item execution (bsc#1236732).\n- x86/static-call: Remove early_boot_irqs_disabled check to fix Xen PVH dom0 (git-fixes).\n- xfs: Add error handling for xfs_reflink_cancel_cow_range (git-fixes).\n- xfs: Propagate errors from xfs_reflink_cancel_cow_range in xfs_dax_write_iomap_end (git-fixes).\n","status":"published","published":"2025-02-14T15:26:53Z","modified":"2026-02-04T03:50:43.941456Z","updated_at":"2026-11-02T15:53:58.883365Z"},{"id":"SUSE-SU-2025:20165-1","title":"Security update for the Linux Kernel","description":"\n\nThe SUSE Linux Enterprise Micro 6.0 and 6.1 kernel was updated to receive various security bugfixes.\n\nThe following security bugs were fixed:\n\n- CVE-2024-26924: scsi: lpfc: Release hbalock before calling lpfc_worker_wake_up() (bsc#1225820).\n- CVE-2024-27397: netfilter: nf_tables: use timestamp to check for set element timeout (bsc#1224095).\n- CVE-2024-35839: kABI fix for netfilter: bridge: replace physindev with physinif in nf_bridge_info (bsc#1224726).\n- CVE-2024-41042: Prefer nft_chain_validate (bsc#1228526).\n- CVE-2024-44934: net: bridge: mcast: wait for previous gc cycles when removing port (bsc#1229809).\n- CVE-2024-44996: vsock: fix recursive -\u003erecvmsg calls (bsc#1230205).\n- CVE-2024-45828: i3c: mipi-i3c-hci: Mask ring interrupts before ring stop request (bsc#1235705).\n- CVE-2024-47678: icmp: change the order of rate limits (bsc#1231854).\n- CVE-2024-48881: bcache: revert replacing IS_ERR_OR_NULL with IS_ERR again (bsc#1235727).\n- CVE-2024-49948: net: add more sanity checks to qdisc_pkt_len_init() (bsc#1232161).\n- CVE-2024-49951: Bluetooth: MGMT: Fix possible crash on mgmt_index_removed (bsc#1232158).\n- CVE-2024-49978: gso: fix udp gso fraglist segmentation after pull from frag_list (bsc#1232101).\n- CVE-2024-49998: net: dsa: improve shutdown sequence (bsc#1232087).\n- CVE-2024-50018: net: napi: Prevent overflow of napi_defer_hard_irqs (bsc#1232419).\n- CVE-2024-50039: kABI: Restore deleted EXPORT_SYMBOL(__qdisc_calculate_pkt_len) (bsc#1231909).\n- CVE-2024-50143: udf: fix uninit-value use in udf_get_fileshortad (bsc#1233038).\n- CVE-2024-50151: smb: client: fix OOBs when building SMB2_IOCTL request (bsc#1233055).\n- CVE-2024-50199: mm/swapfile: skip HugeTLB pages for unuse_vma (bsc#1233112).\n- CVE-2024-50202: nilfs2: propagate directory read errors from nilfs_find_entry() (bsc#1233324).\n- CVE-2024-50256: netfilter: nf_reject_ipv6: fix potential crash in nf_send_reset6() (bsc#1233200).\n- CVE-2024-50262: bpf: Fix out-of-bounds write in trie_get_next_key() (bsc#1233239).\n- CVE-2024-50278, CVE-2024-50280: dm cache: fix flushing uninitialized\n  delayed_work on cache_ctr error (bsc#1233467 bsc#1233469).\n- CVE-2024-50278: dm cache: fix potential out-of-bounds access on the first resume (bsc#1233467).\n- CVE-2024-50299: sctp: properly validate chunk size in sctp_sf_ootb() (bsc#1233488).\n- CVE-2024-53050: drm/i915/hdcp: Add encoder check in hdcp2_get_capability (bsc#1233546).\n- CVE-2024-53064: idpf: fix idpf_vc_core_init error path (bsc#1233558 bsc#1234464).\n- CVE-2024-53090: afs: Fix lock recursion (bsc#1233637).\n- CVE-2024-53091: bpf: Add sk_is_inet and IS_ICSK check in tls_sw_has_ctx_tx/rx (bsc#1233638).\n- CVE-2024-53099: bpf: Check validity of link-\u003etype in bpf_link_show_fdinfo() (bsc#1233772).\n- CVE-2024-53105: mm: page_alloc: move mlocked flag clearance into free_pages_prepare() (bsc#1234069).\n- CVE-2024-53111: mm/mremap: fix address wraparound in move_page_tables() (bsc#1234086).\n- CVE-2024-53113: mm: fix NULL pointer dereference in alloc_pages_bulk_noprof (bsc#1234077).\n- CVE-2024-53117: virtio/vsock: Improve MSG_ZEROCOPY error handling (bsc#1234079).\n- CVE-2024-53118: vsock: Fix sk_error_queue memory leak (bsc#1234071).\n- CVE-2024-53119: virtio/vsock: Fix accept_queue memory leak (bsc#1234073).\n- CVE-2024-53122: mptcp: cope racing subflow creation in mptcp_rcv_space_adjust (bsc#1234076).\n- CVE-2024-53125: bpf: sync_linked_regs() must preserve subreg_def (bsc#1234156).\n- CVE-2024-53130: nilfs2: fix null-ptr-deref in block_dirty_buffer tracepoint (bsc#1234219).\n- CVE-2024-53131: nilfs2: fix null-ptr-deref in block_touch_buffer tracepoint (bsc#1234220).\n- CVE-2024-53133: drm/amd/display: Handle dml allocation failure to avoid crash (bsc#1234221)\n- CVE-2024-53134: pmdomain: imx93-blk-ctrl: correct remove path (bsc#1234159).\n- CVE-2024-53141: netfilter: ipset: add missing range check in bitmap_ip_uadt (bsc#1234381).\n- CVE-2024-53160: rcu/kvfree: Fix data-race in __mod_timer / kvfree_call_rcu (bsc#1234810).\n- CVE-2024-53161: EDAC/bluefield: Fix potential integer overflow (bsc#1234856).\n- CVE-2024-53164: net: sched: fix ordering of qlen adjustment (bsc#1234863).\n- CVE-2024-53170: block: fix uaf for flush rq while iterating tags (bsc#1234888).\n- CVE-2024-53172: ubi: fastmap: Fix duplicate slab cache names while attaching (bsc#1234898).\n- CVE-2024-53175: ipc: fix memleak if msg_init_ns failed in create_ipc_ns (bsc#1234893).\n- CVE-2024-53179: smb: client: fix use-after-free of signing key (bsc#1234921).\n- CVE-2024-53185: smb: client: fix NULL ptr deref in crypto_aead_setkey() (bsc#1234901).\n- CVE-2024-53187: io_uring: check for overflows in io_pin_pages (bsc#1234947).\n- CVE-2024-53195: KVM: arm64: Get rid of userspace_irqchip_in_use (bsc#1234957).\n- CVE-2024-53196: KVM: arm64: Do not retire aborted MMIO instruction (bsc#1234906).\n- CVE-2024-53198: xen: Fix the issue of resource not being properly released in xenbus_dev_probe() (bsc#1234923).\n- CVE-2024-53203: usb: typec: fix potential array underflow in ucsi_ccg_sync_control() (bsc#1235001).\n- CVE-2024-53214: vfio/pci: Properly hide first-in-list PCIe extended capability (bsc#1235004).\n- CVE-2024-53216: nfsd: fix UAF when access ex_uuid or ex_stats (bsc#1235003).\n- CVE-2024-53222: zram: fix NULL pointer in comp_algorithm_show() (bsc#1234974).\n- CVE-2024-53227: scsi: bfa: Fix use-after-free in bfad_im_module_exit() (bsc#1235011).\n- CVE-2024-53232: iommu/s390: Implement blocking domain (bsc#1235050).\n- CVE-2024-53234: erofs: handle NONHEAD !delta[1] lclusters gracefully (bsc#1235045).\n- CVE-2024-53236: xsk: Free skb when TX metadata options are invalid (bsc#1235000).\n- CVE-2024-53240: xen/netfront: fix crash when removing device (bsc#1234281).\n- CVE-2024-53241: x86/xen: use new hypercall functions instead of hypercall page (XSA-466 bsc#1234282).\n- CVE-2024-53685: ceph: give up on paths longer than PATH_MAX (bsc#1235720).\n- CVE-2024-55639: net: renesas: rswitch: avoid use-after-put for a device tree node (bsc#1235737).\n- CVE-2024-55881: KVM: x86: Play nice with protected guests in complete_hypercall_exit() (bsc#1235745).\n- CVE-2024-56372: net: tun: fix tun_napi_alloc_frags() (bsc#1235753).\n- CVE-2024-56549: cachefiles: Fix NULL pointer dereference in object-\u003efile (bsc#1234912).\n- CVE-2024-56566: mm/slub: Avoid list corruption when removing a slab from the full list (bsc#1235033).\n- CVE-2024-56568: iommu/arm-smmu: Defer probe of clients after smmu device bound (bsc#1235032).\n- CVE-2024-56569: ftrace: Fix regression with module command in stack_trace_filter (bsc#1235031).\n- CVE-2024-56570: ovl: Filter invalid inodes with missing lookup function (bsc#1235035).\n- CVE-2024-56582: btrfs: fix use-after-free in btrfs_encoded_read_endio() (bsc#1235128).\n- CVE-2024-56588: scsi: hisi_sas: Create all dump files during debugfs initialization (bsc#1235123).\n- CVE-2024-56589: scsi: hisi_sas: Add cond_resched() for no forced preemption model (bsc#1235241).\n- CVE-2024-56599: wifi: ath10k: avoid NULL pointer error during sdio remove (bsc#1235138).\n- CVE-2024-56600: net: inet6: do not leave a dangling sk pointer in inet6_create() (bsc#1235217).\n- CVE-2024-56601: net: inet: do not leave a dangling sk pointer in inet_create() (bsc#1235230).\n- CVE-2024-56602: net: ieee802154: do not leave a dangling sk pointer in ieee802154_create() (bsc#1235521).\n- CVE-2024-56603: net: af_can: do not leave a dangling sk pointer in can_create() (bsc#1235415).\n- CVE-2024-56604: Bluetooth: RFCOMM: avoid leaving dangling sk pointer in rfcomm_sock_alloc() (bsc#1235056).\n- CVE-2024-56608: drm/amd/display: Fix out-of-bounds access in 'dcn21_link_encoder_create' (bsc#1235487).\n- CVE-2024-56610: kcsan: Turn report_filterlist_lock into a raw_spinlock (bsc#1235390).\n- CVE-2024-56611: mm/mempolicy: fix migrate_to_node() assuming there is at least one VMA in a MM (bsc#1235391).\n- CVE-2024-56614: xsk: fix OOB map writes when deleting elements (bsc#1235424).\n- CVE-2024-56615: bpf: fix OOB devmap writes when deleting elements (bsc#1235426).\n- CVE-2024-56617: cacheinfo: Allocate memory during CPU hotplug if not done from the primary CPU (bsc#1235429).\n- CVE-2024-56620: scsi: ufs: qcom: Only free platform MSIs when ESI is enabled (bsc#1235227).\n- CVE-2024-56622: scsi: ufs: core: sysfs: Prevent div by zero (bsc#1235251).\n- CVE-2024-56631: scsi: sg: Fix slab-use-after-free read in sg_release() (bsc#1235480).\n- CVE-2024-56635: net: avoid potential UAF in default_operstate() (bsc#1235519).\n- CVE-2024-56636: geneve: do not assume mac header is set in geneve_xmit_skb() (bsc#1235520).\n- CVE-2024-56637: netfilter: ipset: Hold module reference while requesting a module (bsc#1235523).\n- CVE-2024-56641: net/smc: initialize close_work early to avoid warning (bsc#1235526).\n- CVE-2024-56643: dccp: Fix memory leak in dccp_feat_change_recv (bsc#1235132).\n- CVE-2024-56648: net: hsr: avoid potential out-of-bound access in fill_frame_info() (bsc#1235451).\n- CVE-2024-56649: net: enetc: Do not configure preemptible TCs if SIs do not support (bsc#1235449).\n- CVE-2024-56650: netfilter: x_tables: fix LED ID check in led_tg_check() (bsc#1235430).\n- CVE-2024-56656: bnxt_en: Fix aggregation ID mask to prevent oops on 5760X chips (bsc#1235444).\n- CVE-2024-56659: net: lapb: increase LAPB_HEADER_LEN (bsc#1235439).\n- CVE-2024-56660: net/mlx5: DR, prevent potential error pointer dereference (bsc#1235437).\n- CVE-2024-56664: bpf, sockmap: Fix race between element replace and close() (bsc#1235249).\n- CVE-2024-56665: bpf,perf: Fix invalid prog_array access in perf_event_detach_bpf_prog (bsc#1235489).\n- CVE-2024-56675: bpf: Fix UAF via mismatching bpf_prog/attachment RCU flavors (bsc#1235555).\n- CVE-2024-56679: octeontx2-pf: handle otx2_mbox_get_rsp errors in otx2_common.c (bsc#1235498).\n- CVE-2024-56693: brd: defer automatic disk creation until module initialization succeeds (bsc#1235418).\n- CVE-2024-56694: bpf: fix recursive lock when verdict program return SK_PASS (bsc#1235412).\n- CVE-2024-56704: 9p/xen: fix release of IRQ (bsc#1235584).\n- CVE-2024-56707: octeontx2-pf: handle otx2_mbox_get_rsp errors in otx2_dmac_flt.c (bsc#1235545).\n- CVE-2024-56708: EDAC/igen6: Avoid segmentation fault on module unload (bsc#1235564).\n- CVE-2024-56712: udmabuf: fix memory leak on last export_udmabuf() error path (bsc#1235565).\n- CVE-2024-56715: ionic: Fix netdev notifier unregister on failure (bsc#1235612).\n- CVE-2024-56716: netdevsim: prevent bad user input in nsim_dev_health_break_write() (bsc#1235587).\n- CVE-2024-56725: octeontx2-pf: handle otx2_mbox_get_rsp errors in otx2_dcbnl.c (bsc#1235578).\n- CVE-2024-56726: octeontx2-pf: handle otx2_mbox_get_rsp errors in cn10k.c (bsc#1235582).\n- CVE-2024-56727: octeontx2-pf: handle otx2_mbox_get_rsp errors in otx2_flows.c (bsc#1235583).\n- CVE-2024-56728: octeontx2-pf: handle otx2_mbox_get_rsp errors in otx2_ethtool.c (bsc#1235656).\n- CVE-2024-56729: smb: Initialize cfid-\u003etcon before performing network ops (bsc#1235503).\n- CVE-2024-56747: scsi: qedi: Fix a possible memory leak in qedi_alloc_and_init_sb() (bsc#1234934).\n- CVE-2024-56748: scsi: qedf: Fix a possible memory leak in qedf_alloc_and_init_sb() (bsc#1235627).\n- CVE-2024-56755: netfs/fscache: Add a memory barrier for FSCACHE_VOLUME_CREATING (bsc#1234920).\n- CVE-2024-56759: btrfs: fix use-after-free when COWing tree bock and tracing is enabled (bsc#1235645).\n- CVE-2024-56763: tracing: Prevent bad count for tracing_cpumask_write (bsc#1235638).\n- CVE-2024-56774: btrfs: add a sanity check for btrfs root in btrfs_search_slot() (bsc#1235653).\n- CVE-2024-56775: drm/amd/display: Fix handling of plane refcount (bsc#1235657).\n- CVE-2024-57791: net/smc: check return value of sock_recvmsg when draining clc data (bsc#1235759).\n- CVE-2024-57793: virt: tdx-guest: Just leak decrypted memory on unrecoverable errors (bsc#1235768).\n- CVE-2024-57795: RDMA/rxe: Remove the direct link to net_device (bsc#1235906).\n- CVE-2024-57801: net/mlx5e: Skip restore TC rules for vport rep without loaded flag (bsc#1235940).\n- CVE-2024-57802: netrom: check buffer length before accessing it (bsc#1235941).\n- CVE-2024-57804: scsi: mpi3mr: Fix corrupt config pages PHY state is switched in sysfs (bsc#1235779).\n- CVE-2024-57809: PCI: imx6: Fix suspend/resume support on i.MX6QDL (bsc#1235793).\n- CVE-2024-57838: s390/entry: Mark IRQ entries to fix stack depot warnings (bsc#1235798).\n- CVE-2024-57857: RDMA/siw: Remove direct link to net_device (bsc#1235946).\n- CVE-2024-57884: mm: vmscan: account for free pages to prevent infinite Loop in throttle_direct_reclaim() (bsc#1235948).\n- CVE-2024-57892: ocfs2: fix slab-use-after-free due to dangling pointer dqi_priv (bsc#1235964).\n- CVE-2024-57896: btrfs: flush delalloc workers queue before stopping cleaner kthread during unmount (bsc#1235965).\n- CVE-2024-57903: net: restrict SO_REUSEPORT to inet sockets (bsc#1235967).\n- CVE-2024-57917: topology: Keep the cpumask unchanged when printing cpumap (bsc#1236127).\n- CVE-2024-57929: dm array: fix releasing a faulty array block twice in dm_array_cursor_end (bsc#1236096).\n- CVE-2024-57931: selinux: ignore unknown extended permissions (bsc#1236192).\n- CVE-2024-57932: gve: guard XDP xmit NDO on existence of xdp queues (bsc#1236190).\n- CVE-2024-57933: gve: guard XSK operations on the existence of queues (bsc#1236178).\n- CVE-2024-57938: net/sctp: Prevent autoclose integer overflow in sctp_association_init() (bsc#1236182).\n- CVE-2024-57946: virtio-blk: do not keep queue frozen during system suspend (bsc#1236247).\n- CVE-2025-21632: x86/fpu: Ensure shadow stack is active before \"getting\" registers (bsc#1236106).\n- CVE-2025-21649: net: hns3: fix kernel crash when 1588 is sent on HIP08 devices (bsc#1236143).\n- CVE-2025-21650: net: hns3: fixed hclge_fetch_pf_reg accesses bar space out of bounds issue (bsc#1236144).\n- CVE-2025-21651: net: hns3: do not auto enable misc vector (bsc#1236145).\n- CVE-2025-21652: ipvlan: Fix use-after-free in ipvlan_get_iflink() (bsc#1236160).\n- CVE-2025-21653: net_sched: cls_flow: validate TCA_FLOW_RSHIFT attribute (bsc#1236161).\n- CVE-2025-21655: io_uring/eventfd: ensure io_eventfd_signal() defers another RCU period (bsc#1236163).\n- CVE-2025-21662: net/mlx5: Fix variable not being completed when function returns (bsc#1236198).\n- CVE-2025-21663: net: stmmac: dwmac-tegra: Read iommu stream id from device tree (bsc#1236260).\n- CVE-2025-21664: dm thin: make get_first_thin use rcu-safe list first function (bsc#1236262).\n- CVE-2025-21674: net/mlx5e: Fix inversion dependency warning while enabling IPsec tunnel (bsc#1236688).\n- CVE-2025-21676: net: fec: handle page_pool_dev_alloc_pages error (bsc#1236696).\n- CVE-2025-21682: eth: bnxt: always recalculate features after XDP clearing, fix null-deref (bsc#1236703).\n\nThe following non-security bugs were fixed:\n\n- 9p: v9fs_fid_find: also lookup by inode if not found dentry (git-fixes).\n- ACPI/HMAT: Move HMAT messages to pr_debug() (bsc#1234294)\n- ACPI/IORT: Add PMCG platform information for HiSilicon HIP09A (stable-fixes).\n- ACPI/IORT: Add PMCG platform information for HiSilicon HIP10/11 (stable-fixes).\n- ACPI: PCC: Add PCC shared memory region command and status bitfields (stable-fixes).\n- ACPI: PRM: Add PRM handler direct call support (jsc#PED-10467).\n- ACPI: fan: cleanup resources in the error path of .probe() (git-fixes).\n- ACPI: resource: Add Asus Vivobook X1504VAP to irq1_level_low_skip_override[] (stable-fixes).\n- ACPI: resource: Add TongFang GM5HG0A to irq1_edge_low_force_override[] (stable-fixes).\n- ACPI: resource: Fix memory resource type union access (git-fixes).\n- ACPI: resource: acpi_dev_irq_override(): Check DMI match last (stable-fixes).\n- ACPI: x86: Add skip i2c clients quirk for Acer Iconia One 8 A1-840 (stable-fixes).\n- ACPI: x86: Clean up Asus entries in acpi_quirk_skip_dmi_ids[] (stable-fixes).\n- ACPI: x86: Make UART skip quirks work on PCI UARTs without an UID (stable-fixes).\n- ACPICA: events/evxfregn: do not release the ContextMutex that was never acquired (git-fixes).\n- ALSA hda/realtek: Add quirk for Framework F111:000C (stable-fixes).\n- ALSA: hda/hdmi: Yet more pin fix for HP EliteDesk 800 G4 (stable-fixes).\n- ALSA: hda/realtek - Add support for ASUS Zen AIO 27 Z272SD_A272SD audio (stable-fixes).\n- ALSA: hda/realtek - Fixed headphone distorted sound on Acer Aspire A115-31 laptop (git-fixes).\n- ALSA: hda/realtek: Add Framework Laptop 13 (Intel Core Ultra) to quirks (stable-fixes).\n- ALSA: hda/realtek: Add new alc2xx-fixup-headset-mic model (stable-fixes).\n- ALSA: hda/realtek: Add support for Ayaneo System using CS35L41 HDA (stable-fixes).\n- ALSA: hda/realtek: Add support for Galaxy Book2 Pro (NP950XEE) (stable-fixes).\n- ALSA: hda/realtek: Enable Mute LED on HP Laptop 14s-fq1xxx (stable-fixes).\n- ALSA: hda/realtek: Enable headset mic on Positivo C6400 (stable-fixes).\n- ALSA: hda/realtek: Fix headset mic on Acer Nitro 5 (stable-fixes).\n- ALSA: hda/realtek: Workaround for resume on Dell Venue 11 Pro 7130 (bsc#1235686).\n- ALSA: hda: Add HP MP9 G4 Retail System AMS to force connect list (stable-fixes).\n- ALSA: hda: Fix headset detection failure due to unstable sort (git-fixes).\n- ALSA: line6: Fix racy access to midibuf (stable-fixes).\n- ALSA: seq: Check UMP support for midi_version change (git-fixes).\n- ALSA: seq: oss: Fix races at processing SysEx messages (stable-fixes).\n- ALSA: seq: ump: Fix seq port updates per FB info notify (git-fixes).\n- ALSA: seq: ump: Use automatic cleanup of kfree() (stable-fixes).\n- ALSA: seq: ump: Use guard() for locking (stable-fixes).\n- ALSA: ump: Use guard() for locking (stable-fixes).\n- ALSA: usb-audio: Add delay quirk for USB Audio Device (stable-fixes).\n- ALSA: usb-audio: Add delay quirk for iBasso DC07 Pro (stable-fixes).\n- ALSA: usb-audio: Add implicit feedback quirk for Yamaha THR5 (stable-fixes).\n- ALSA: usb-audio: Notify xrun for low-latency mode (git-fixes).\n- ALSA: usb-audio: Re-add ScratchAmp quirk entries (git-fixes).\n- ALSA: usb-audio: US16x08: Initialize array before use (git-fixes).\n- ASoC: Intel: avs: Fix theoretical infinite loop (git-fixes).\n- ASoC: Intel: sof_sdw: add quirk for Dell SKU 0B8C (stable-fixes).\n- ASoC: Intel: sof_sdw: fix jack detection on ADL-N variant RVP (stable-fixes).\n- ASoC: SOF: Remove libraries from topology lookups (git-fixes).\n- ASoC: acp: Support microphone from Lenovo Go S (stable-fixes).\n- ASoC: amd: yc: Add a quirk for microfone on Lenovo ThinkPad P14s Gen 5 21MES00B00 (stable-fixes).\n- ASoC: amd: yc: Add quirk for microphone on Lenovo Thinkpad T14s Gen 6 21M1CTO1WW (stable-fixes).\n- ASoC: amd: yc: Fix the wrong return value (git-fixes).\n- ASoC: amd: yc: Support mic on HP 14-em0002la (stable-fixes).\n- ASoC: amd: yc: Support mic on Lenovo Thinkpad E14 Gen 6 (stable-fixes).\n- ASoC: amd: yc: fix internal mic on Redmi G 2022 (stable-fixes).\n- ASoC: codecs: wcd938x-sdw: Correct Soundwire ports mask (git-fixes).\n- ASoC: codecs: wsa881x: Correct Soundwire ports mask (git-fixes).\n- ASoC: codecs: wsa883x: Correct Soundwire ports mask (git-fixes).\n- ASoC: codecs: wsa884x: Correct Soundwire ports mask (git-fixes).\n- ASoC: cs35l56: Handle OTP read latency over SoundWire (stable-fixes).\n- ASoC: cs35l56: Patch CS35L56_IRQ1_MASK_18 to the default value (stable-fixes).\n- ASoC: fsl_micfil: Expand the range of FIFO watermark mask (stable-fixes).\n- ASoC: hdmi-codec: reorder channel allocation list (stable-fixes).\n- ASoC: mediatek: disable buffer pre-allocation (stable-fixes).\n- ASoC: meson: axg-fifo: fix irq scheduling issue with PREEMPT_RT (git-fixes).\n- ASoC: nau8822: Lower debug print priority (stable-fixes).\n- ASoC: rockchip: i2s_tdm: Re-add the set_sysclk callback (git-fixes).\n- ASoC: rt722: add delay time to wait for the calibration procedure (stable-fixes).\n- ASoC: samsung: Add missing depends on I2C (git-fixes).\n- ASoC: samsung: Add missing selects for MFD_WM8994 (stable-fixes).\n- ASoC: sun4i-spdif: Add clock multiplier settings (git-fixes).\n- ASoC: wm8994: Add depends on MFD core (stable-fixes).\n- Bluetooth: Add support ITTIM PE50-M75C (stable-fixes).\n- Bluetooth: Fix type of len in rfcomm_sock_getsockopt{,_old}() (stable-fixes).\n- Bluetooth: ISO: Reassociate a socket with an active BIS (stable-fixes).\n- Bluetooth: L2CAP: accept zero as a special value for MTU auto-selection (git-fixes).\n- Bluetooth: L2CAP: do not leave dangling sk pointer on error in l2cap_sock_create() (stable-fixes).\n- Bluetooth: L2CAP: handle NULL sock pointer in l2cap_sock_alloc (git-fixes).\n- Bluetooth: MGMT: Fix Add Device to responding before completing (git-fixes).\n- Bluetooth: MGMT: Fix possible deadlocks (git-fixes).\n- Bluetooth: SCO: Add support for 16 bits transparent voice setting (git-fixes).\n- Bluetooth: btnxpuart: Fix driver sending truncated data (git-fixes).\n- Bluetooth: btnxpuart: Fix glitches seen in dual A2DP streaming (git-fixes).\n- Bluetooth: btusb: Add RTL8852BE device 0489:e123 to device tables (stable-fixes).\n- Bluetooth: btusb: Add USB HW IDs for MT7921/MT7922/MT7925 (stable-fixes).\n- Bluetooth: btusb: Add new VID/PID 0489/e111 for MT7925 (stable-fixes).\n- Bluetooth: btusb: Add new VID/PID 13d3/3602 for MT7925 (stable-fixes).\n- Bluetooth: btusb: add callback function in btusb suspend/resume (stable-fixes).\n- Bluetooth: btusb: mediatek: add callback function in btusb_disconnect (stable-fixes).\n- Bluetooth: hci_core: Fix not checking skb length on hci_acldata_packet (stable-fixes).\n- Bluetooth: hci_event: Fix using rcu_read_(un)lock while iterating (git-fixes).\n- Bluetooth: hci_sync: Fix not setting Random Address when required (git-fixes).\n- Bluetooth: iso: Fix recursive locking warning (git-fixes).\n- Delete XHCI patch for regression (bsc#1235550)\n- Disable ceph (jsc#PED-7242)\n- Documentation: PM: Clarify pm_runtime_resume_and_get() return value (git-fixes).\n- Drivers: hv: util: Avoid accessing a ringbuffer not initialized yet (git-fixes).\n- Drop downstream TPM fix patch (bsc#1233260 bsc#1233259 bsc#1232421)\n- Drop uvcvideo fix due to regression (bsc#1235894)\n- EDAC/{i10nm,skx,skx_common}: Support UV systems (bsc#1234693).\n- HID: core: Fix assumption that Resolution Multipliers must be in Logical Collections (git-fixes).\n- HID: fix generic desktop D-Pad controls (git-fixes).\n- HID: hid-sensor-hub: do not use stale platform-data on remove (git-fixes).\n- HID: hid-thrustmaster: Fix warning in thrustmaster_probe by adding endpoint check (git-fixes).\n- HID: magicmouse: Apple Magic Trackpad 2 USB-C driver support (stable-fixes).\n- HID: multitouch: fix support for Goodix PID 0x01e9 (git-fixes).\n- Input: atkbd - map F23 key to support default copilot shortcut (stable-fixes).\n- Input: bbnsm_pwrkey - add remove hook (git-fixes).\n- Input: bbnsm_pwrkey - fix missed key press after suspend (git-fixes).\n- Input: davinci-keyscan - remove leftover header (git-fixes).\n- Input: xpad - add QH Electronics VID/PID (stable-fixes).\n- Input: xpad - add support for Nacon Evol-X Xbox One Controller (stable-fixes).\n- Input: xpad - add support for Nacon Pro Compact (stable-fixes).\n- Input: xpad - add support for wooting two he (arm) (stable-fixes).\n- Input: xpad - add unofficial Xbox 360 wireless receiver clone (stable-fixes).\n- Input: xpad - improve name of 8BitDo controller 2dc8:3106 (stable-fixes).\n- KVM: SVM: Allow guest writes to set MSR_AMD64_DE_CFG bits (bsc#1234635).\n- KVM: s390: Reject KVM_SET_GSI_ROUTING on ucontrol VMs (git-fixes bsc#1235776).\n- KVM: s390: Reject setting flic pfault attributes on ucontrol VMs (git-fixes bsc#1235777).\n- KVM: s390: vsie: fix virtual/physical address in unpin_scb() (git-fixes bsc#1235778).\n- NFC: nci: Add bounds checking in nci_hci_create_pipe() (git-fixes).\n- NFS/pnfs: Fix a live lock between recalled layouts and layoutget (git-fixes).\n- NFSD: Async COPY result needs to return a write verifier (git-fixes).\n- NFSD: Cap the number of bytes copied by nfs4_reset_recoverydir() (git-fixes).\n- NFSD: Fix nfsd4_shutdown_copy() (git-fixes).\n- NFSD: Prevent NULL dereference in nfsd4_process_cb_update() (git-fixes).\n- NFSD: Prevent a potential integer overflow (git-fixes).\n- NFSD: Remove a never-true comparison (git-fixes).\n- NFSD: initialize copy-\u003ecp_clp early in nfsd4_copy for use by trace point (git-fixes).\n- NFSv4.0: Fix a use-after-free problem in the asynchronous open() (git-fixes).\n- NFSv4.2: fix COPY_NOTIFY xdr buf size calculation (git-fixes).\n- NFSv4.2: mark OFFLOAD_CANCEL MOVEABLE (git-fixes).\n- Octeontx2-pf: Free send queue buffers incase of leaf to inner (git-fixes).\n- PCI/AER: Disable AER service on suspend (stable-fixes).\n- PCI/MSI: Handle lack of irqdomain gracefully (git-fixes).\n- PCI: Add 'reset_subordinate' to reset hierarchy below bridge (stable-fixes).\n- PCI: Add ACS quirk for Broadcom BCM5760X NIC (stable-fixes).\n- PCI: Add ACS quirk for Wangxun FF5xxx NICs (stable-fixes).\n- PCI: Add T_PERST_CLK_US macro (git-fixes).\n- PCI: Avoid putting some root ports into D3 on TUXEDO Sirius Gen1 (git-fixes).\n- PCI: Detect and trust built-in Thunderbolt chips (stable-fixes).\n- PCI: Fix use-after-free of slot-\u003ebus on hot remove (stable-fixes).\n- PCI: Use preserve_config in place of pci_flags (stable-fixes).\n- PCI: cadence: Extract link setup sequence from cdns_pcie_host_setup() (stable-fixes).\n- PCI: cadence: Set cdns_pcie_host_init() global (stable-fixes).\n- PCI: cpqphp: Use PCI_POSSIBLE_ERROR() to check config reads (stable-fixes).\n- PCI: dwc: Always stop link in the dw_pcie_suspend_noirq (git-fixes).\n- PCI: dwc: ep: Prevent changing BAR size/flags in pci_epc_set_bar() (git-fixes).\n- PCI: dwc: ep: Write BAR_MASK before iATU registers in pci_epc_set_bar() (git-fixes).\n- PCI: endpoint: Destroy the EPC device in devm_pci_epc_destroy() (git-fixes).\n- PCI: endpoint: Finish virtual EP removal in pci_epf_remove_vepf() (git-fixes).\n- PCI: endpoint: pci-epf-test: Fix check for DMA MEMCPY test (git-fixes).\n- PCI: endpoint: pci-epf-test: Set dma_chan_rx pointer to NULL on error (git-fixes).\n- PCI: imx6: Deassert apps_reset in imx_pcie_deassert_core_reset() (git-fixes).\n- PCI: imx6: Skip controller_id generation logic for i.MX7D (git-fixes).\n- PCI: j721e: Add PCIe 4x lane selection support (stable-fixes).\n- PCI: j721e: Add per platform maximum lane settings (stable-fixes).\n- PCI: j721e: Add reset GPIO to struct j721e_pcie (stable-fixes).\n- PCI: j721e: Add suspend and resume support (git-fixes).\n- PCI: j721e: Use T_PERST_CLK_US macro (git-fixes).\n- PCI: microchip: Set inbound address translation for coherent or non-coherent mode (git-fixes).\n- PCI: qcom: Add support for IPQ9574 (stable-fixes).\n- PCI: rcar-ep: Fix incorrect variable used when calling devm_request_mem_region() (git-fixes).\n- PCI: vmd: Add DID 8086:B06F and 8086:B60B for Intel client SKUs (stable-fixes).\n- PCI: vmd: Set devices to D0 before enabling PM L1 Substates (stable-fixes).\n- PM: hibernate: Add error handling for syscore_suspend() (git-fixes).\n- RAS/AMD/ATL: Translate normalized to system physical addresses using PRM (jsc#PED-10467).\n- RDMA/bnxt_re: Add check for path mtu in modify_qp (git-fixes)\n- RDMA/bnxt_re: Add send queue size check for variable wqe (git-fixes)\n- RDMA/bnxt_re: Avoid initializing the software queue for user queues (git-fixes)\n- RDMA/bnxt_re: Avoid sending the modify QP workaround for latest adapters (git-fixes)\n- RDMA/bnxt_re: Disable use of reserved wqes (git-fixes)\n- RDMA/bnxt_re: Fix MSN table size for variable wqe mode (git-fixes)\n- RDMA/bnxt_re: Fix max SGEs for the Work Request (git-fixes)\n- RDMA/bnxt_re: Fix max_qp_wrs reported (git-fixes)\n- RDMA/bnxt_re: Fix reporting hw_ver in query_device (git-fixes)\n- RDMA/bnxt_re: Fix the check for 9060 condition (git-fixes)\n- RDMA/bnxt_re: Fix the locking while accessing the QP table (git-fixes)\n- RDMA/bnxt_re: Fix the max WQE size for static WQE support (git-fixes)\n- RDMA/bnxt_re: Fix the max WQEs used in Static WQE mode (git-fixes)\n- RDMA/bnxt_re: Fix to drop reference to the mmap entry in case of error (git-fixes)\n- RDMA/bnxt_re: Fix to export port num to ib_query_qp (git-fixes)\n- RDMA/bnxt_re: Remove always true dattr validity check (git-fixes)\n- RDMA/core: Fix ENODEV error for iWARP test over vlan (git-fixes)\n- RDMA/hns: Fix accessing invalid dip_ctx during destroying QP (git-fixes)\n- RDMA/hns: Fix mapping error of zero-hop WQE buffer (git-fixes)\n- RDMA/hns: Fix missing flush CQE for DWQE (git-fixes)\n- RDMA/hns: Fix warning storm caused by invalid input in IO path (git-fixes)\n- RDMA/mlx4: Avoid false error about access to uninitialized gids array (git-fixes)\n- RDMA/mlx5: Enforce same type port association for multiport RoCE (git-fixes)\n- RDMA/mlx5: Fix a race for an ODP MR which leads to CQE with error (git-fixes)\n- RDMA/mlx5: Fix implicit ODP use after free (git-fixes)\n- RDMA/mlx5: Fix indirect mkey ODP page count (git-fixes)\n- RDMA/rtrs: Ensure 'ib_sge list' is accessible (git-fixes)\n- RDMA/rxe: Fix mismatched max_msg_sz (git-fixes)\n- RDMA/rxe: Fix the warning \"__rxe_cleanup+0x12c/0x170 [rdma_rxe]\" (git-fixes)\n- RDMA/srp: Fix error handling in srp_add_port (git-fixes)\n- RDMA/uverbs: Prevent integer overflow issue (git-fixes)\n- Revert \"HID: multitouch: Add support for lenovo Y9000P Touchpad\" (stable-fixes).\n- Revert \"block/mq-deadline: use correct way to throttling write requests\" (bsc#1234146).\n- Revert \"btrfs: fix use-after-free waiting for encoded read endios (bsc#1235128)\"\n- Revert \"drm/i915/dpt: Make DPT object unshrinkable\" (stable-fixes).\n- Revert \"igb: Disable threaded IRQ for igb_msix_other\" (git-fixes).\n- Revert \"mm, kmsan: fix infinite recursion due to RCU critical section\" (bsc#1230413)\n- Revert \"mm/sparsemem: fix race in accessing memory_section-\u003eusage\" (bsc#1230413)\n- Revert \"mm: prevent derefencing NULL ptr in pfn_section_valid()\" (bsc#1230413)\n- Revert \"mtd: spi-nor: core: replace dummy buswidth from addr to data\" (git-fixes).\n- Revert \"unicode: Do not special case ignorable code points\" (stable-fixes).\n- Revert \"usb: gadget: u_serial: Disable ep before setting port to null\n  to fix the crash caused by port being null\" (stable-fixes).\n- Revert 'arm64: Kconfig: Make SME depend on BROKEN for now' \n- Revert 0dd78566990 (\"Disable ceph (jsc#PED-7242)\") \n- SUNRPC: make sure cache entry active before cache_show (git-fixes).\n- SUNRPC: timeout and cancel TLS handshake with -ETIMEDOUT (git-fixes).\n- USB: core: Disable LPM only for non-suspended ports (git-fixes).\n- USB: serial: cp210x: add Phoenix Contact UPS Device (stable-fixes).\n- USB: serial: option: add MediaTek T7XX compositions (stable-fixes).\n- USB: serial: option: add MeiG Smart SLM770A (stable-fixes).\n- USB: serial: option: add MeiG Smart SRM815 (stable-fixes).\n- USB: serial: option: add Neoway N723-EA support (stable-fixes).\n- USB: serial: option: add Netprisma LCUK54 modules for WWAN Ready (stable-fixes).\n- USB: serial: option: add TCL IK512 MBIM \u0026 ECM (stable-fixes).\n- USB: serial: option: add Telit FE910C04 rmnet compositions (stable-fixes).\n- USB: serial: quatech2: fix null-ptr-deref in qt2_process_read_urb() (git-fixes).\n- USB: usblp: return error when setting unsupported protocol (git-fixes).\n- VFS: use system_unbound_wq for delayed_mntput (bsc#1234683).\n- VMCI: fix reference to ioctl-number.rst (git-fixes).\n- accel/habanalabs/gaudi2: unsecure tpc count registers (stable-fixes).\n- accel/habanalabs: export dma-buf only if size/offset multiples of PAGE_SIZE (stable-fixes).\n- accel/habanalabs: fix debugfs files permissions (stable-fixes).\n- accel/habanalabs: increase HL_MAX_STR to 64 bytes to avoid warnings (stable-fixes).\n- acpi: nfit: vmalloc-out-of-bounds Read in acpi_nfit_ctl (git-fixes).\n- af_unix: Call manage_oob() for every skb in unix_stream_read_generic() (bsc#1234725).\n- afs: Automatically generate trace tag enums (git-fixes).\n- afs: Fix EEXIST error returned from afs_rmdir() to be ENOTEMPTY (git-fixes).\n- afs: Fix cleanup of immediately failed async calls (git-fixes).\n- afs: Fix directory format encoding struct (git-fixes).\n- afs: Fix missing subdir edit when renamed between parent dirs (git-fixes).\n- afs: Fix the fallback handling for the YFS.RemoveFile2 RPC call (git-fixes).\n- afs: Fix the maximum cell name length (git-fixes).\n- amdgpu/uvd: get ring reference from rq scheduler (git-fixes).\n- arch: Introduce arch_{,try_}_cmpxchg128{,_local}() (bsc#1220773).\n- arch: Remove cmpxchg_double (bsc#1220773).\n- arch: consolidate arch_irq_work_raise prototypes (git-fixes).\n- arm64/sme: Move storage of reg_smidr to __cpuinfo_store_cpu() (git-fixes)\n- arm64: Ensure bits ASID[15:8] are masked out when the kernel uses (bsc#1234605)\n- arm64: Filter out SVE hwcaps when FEAT_SVE isn't implemented (git-fixes)\n- arm64: Force position-independent veneers (git-fixes).\n- arm64: Kconfig: Make SME depend on BROKEN for now (git-fixes bsc#1236245)\n- arm64: dts: imx8mp: correct sdhc ipg clk (git-fixes).\n- arm64: dts: rockchip: Add sdmmc/sdio/emmc reset controls for RK3328 (git-fixes)\n- arm64: dts: rockchip: add hevc power domain clock to rk3328 (git-fixes).\n- arm64: dts: rockchip: increase gmac rx_delay on rk3399-puma (git-fixes)\n- arm64: ptrace: fix partial SETREGSET for NT_ARM_TAGGED_ADDR_CTRL (git-fixes).\n- arm64: tegra: Disable Tegra234 sce-fabric node (git-fixes)\n- arm64: tegra: Fix Tegra234 PCIe interrupt-map (git-fixes)\n- arm64: tegra: Fix typo in Tegra234 dce-fabric compatible (git-fixes)\n- ata: libata-core: Set ATA_QCFLAG_RTF_FILLED in fill_result_tf() (stable-fixes).\n- autofs: fix memory leak of waitqueues in autofs_catatonic_mode (git-fixes).\n- batman-adv: Do not let TT changes list grows indefinitely (git-fixes).\n- batman-adv: Do not send uninitialized TT changes (git-fixes).\n- batman-adv: Remove uninitialized data in full table TT response (git-fixes).\n- blk-cgroup: Fix UAF in blkcg_unpin_online() (bsc#1234726).\n- blk-core: use pr_warn_ratelimited() in bio_check_ro() (bsc#1234139).\n- blk-iocost: Fix an UBSAN shift-out-of-bounds warning (bsc#1234144).\n- blk-iocost: do not WARN if iocg was already offlined (bsc#1234147).\n- blk-throttle: fix lockdep warning of \"cgroup_mutex or RCU read lock required!\" (bsc#1234140).\n- block, bfq: choose the last bfqq from merge chain in bfq_setup_cooperator() (bsc#1234149).\n- block, bfq: do not break merge chain in bfq_split_bfqq() (bsc#1234150).\n- block, bfq: fix bfqq uaf in bfq_limit_depth() (bsc#1234160).\n- block, bfq: fix procress reference leakage for bfqq in merge chain (bsc#1234280).\n- block, bfq: fix uaf for accessing waker_bfqq after splitting (bsc#1234279).\n- block/mq-deadline: Fix the tag reservation code (bsc#1234148).\n- block: Call .limit_depth() after .hctx has been set (bsc#1234148).\n- block: Fix where bio IO priority gets set (bsc#1234145).\n- block: prevent an integer overflow in bvec_try_merge_hw_page (bsc#1234142).\n- block: update the stable_writes flag in bdev_add (bsc#1234141).\n- bnxt_en: Fix GSO type for HW GRO packets on 5750X chips (git-fixes)\n- bnxt_en: Fix receive ring space parameters when XDP is active (git-fixes).\n- bnxt_en: Reserve rings after PCIe AER recovery if NIC interface is down (git-fixes).\n- bnxt_en: Set backplane link modes correctly for ethtool (git-fixes).\n- bpf, x86: Fix PROBE_MEM runtime load check (git-fixes).\n- bpf: verifier: prevent userspace memory access (git-fixes).\n- btrfs: fix use-after-free in btrfs_encoded_read_endio() (bsc#1235445).\n- btrfs: fix use-after-free waiting for encoded read endios (bsc#1235128)\n- btrfs: fix use-after-free waiting for encoded read endios (bsc#1235445).\n- bus: mhi: host: Free mhi_buf vector inside mhi_alloc_bhie_table() (git-fixes).\n- can: gs_usb: add VID/PID for Xylanta SAINT3 product family (stable-fixes).\n- can: j1939: fix error in J1939 documentation (stable-fixes).\n- ceph: improve error handling and short/overflow-read logic in __ceph_sync_read() (bsc#1228592).\n- checkpatch: always parse orig_commit in fixes tag (git-fixes).\n- checkpatch: check for missing Fixes tags (stable-fixes).\n- cleanup: Add conditional guard support (stable-fixes).\n- cleanup: Adjust scoped_guard() macros to avoid potential warning (stable-fixes).\n- cleanup: Remove address space of returned pointer (git-fixes).\n- clocksource/drivers/timer-ti-dm: Fix child node refcount handling (git-fixes).\n- clocksource/drivers:sp804: Make user selectable (git-fixes).\n- counter: stm32-timer-cnt: Add check for clk_enable() (git-fixes).\n- counter: ti-ecap-capture: Add check for clk_enable() (git-fixes).\n- cpufreq: ACPI: Fix max-frequency computation (git-fixes).\n- cpufreq: Do not unregister cpufreq cooling on CPU hotplug (git-fixes).\n- cpufreq: amd-pstate: remove global header file (git-fixes).\n- cpufreq: intel_pstate: Check turbo_is_disabled() in store_no_turbo() (bsc#1234619).\n- cpufreq: intel_pstate: Do not update global.turbo_disabled after initialization (bsc#1234619).\n- cpufreq: intel_pstate: Drop redundant locking from intel_pstate_driver_cleanup() (bsc#1234619).\n- cpufreq: intel_pstate: Fix unchecked HWP MSR access (bsc#1234619).\n- cpufreq: intel_pstate: Fold intel_pstate_max_within_limits() into caller (bsc#1234619).\n- cpufreq: intel_pstate: Get rid of unnecessary READ_ONCE() annotations (bsc#1234619).\n- cpufreq: intel_pstate: Make hwp_notify_lock a raw spinlock (git-fixes).\n- cpufreq: intel_pstate: Read global.no_turbo under READ_ONCE() (bsc#1234619).\n- cpufreq: intel_pstate: Rearrange show_no_turbo() and store_no_turbo() (bsc#1234619).\n- cpufreq: intel_pstate: Refine computation of P-state for given frequency (bsc#1234619).\n- cpufreq: intel_pstate: Replace three global.turbo_disabled checks (bsc#1234619).\n- cpufreq: intel_pstate: Revise global turbo disable check (bsc#1234619).\n- cpufreq: intel_pstate: Simplify spinlock locking (bsc#1234619).\n- cpufreq: intel_pstate: Update the maximum CPU frequency consistently (bsc#1234619).\n- cpufreq: intel_pstate: Use HWP to initialize ITMT if CPPC is missing (git-fixes).\n- cpufreq: intel_pstate: Use __ro_after_init for three variables (bsc#1234619).\n- cpufreq: intel_pstate: Wait for canceled delayed work to complete (bsc#1234619).\n- cpufreq: intel_pstate: fix pstate limits enforcement for adjust_perf call back (git-fixes).\n- cpuidle: Avoid potential overflow in integer multiplication (git-fixes).\n- cpupower: fix TSC MHz calculation (git-fixes).\n- crypto: caam - use JobR's space to access page 0 regs (git-fixes).\n- crypto: ecc - Prevent ecc_digits_from_bytes from reading too many bytes (git-fixes).\n- crypto: ecdsa - Avoid signed integer overflow on signature decoding (stable-fixes).\n- crypto: ecdsa - Convert byte arrays with key coordinates to digits (stable-fixes).\n- crypto: ecdsa - Rename keylen to bufsize where necessary (stable-fixes).\n- crypto: ecdsa - Use ecc_digits_from_bytes to convert signature (stable-fixes).\n- crypto: iaa - Fix IAA disabling that occurs when sync_mode is set to 'async' (git-fixes).\n- crypto: ixp4xx - fix OF node reference leaks in init_ixp_crypto() (git-fixes).\n- crypto: qat - disable IOV in adf_dev_stop() (git-fixes).\n- crypto: qce - fix goto jump in error path (git-fixes).\n- crypto: qce - fix priority to be less than ARMv8 CE (git-fixes).\n- crypto: qce - unregister previously registered algos in error path (git-fixes).\n- crypto: x86/sha256 - Add parentheses around macros' single arguments (stable-fixes).\n- cyrpto/b128ops: Remove struct u128 (bsc#1220773).\n- devcoredump: cleanup some comments (git-fixes).\n- devlink: Fix length of eswitch inline-mode (git-fixes).\n- dlm: fix possible lkb_resource null dereference (git-fixes).\n- dma-buf: fix dma_fence_array_signaled v4 (stable-fixes).\n- dma-debug: fix a possible deadlock on radix_lock (stable-fixes).\n- dmaengine: apple-admac: Avoid accessing registers in probe (git-fixes).\n- dmaengine: at_xdmac: avoid null_prt_deref in at_xdmac_prep_dma_memset (git-fixes).\n- dmaengine: dw: Select only supported masters for ACPI devices (git-fixes).\n- dmaengine: idxd: Check for driver name match before sva user feature (bsc#1234357).\n- dmaengine: mv_xor: fix child node refcount handling in early exit (git-fixes).\n- dmaengine: tegra: Return correct DMA status when paused (git-fixes).\n- dmaengine: ti: edma: fix OF node reference leaks in edma_driver (git-fixes).\n- docs: media: update location of the media patches (stable-fixes).\n- docs: power: Fix footnote reference for Toshiba Satellite P10-554 (git-fixes).\n- driver core: Add FWLINK_FLAG_IGNORE to completely ignore a fwnode link (stable-fixes).\n- driver core: class: Fix wild pointer dereferences in API class_dev_iter_next() (git-fixes).\n- driver core: fw_devlink: Improve logs for cycle detection (stable-fixes).\n- driver core: fw_devlink: Stop trying to optimize cycle detection logic (git-fixes).\n- drivers/card_reader/rtsx_usb: Restore interrupt based detection (git-fixes).\n- drivers: net: ionic: add missed debugfs cleanup to ionic_probe() error path (git-fixes).\n- drm/amd/display: Add HDR workaround for specific eDP (stable-fixes).\n- drm/amd/display: Add NULL check for clk_mgr in dcn32_init_hw (stable-fixes).\n- drm/amd/display: Add check for granularity in dml ceil/floor helpers (stable-fixes).\n- drm/amd/display: Allow backlight to go below `AMDGPU_DM_DEFAULT_MIN_BACKLIGHT` (stable-fixes).\n- drm/amd/display: Avoid overflow assignment in link_dp_cts (stable-fixes).\n- drm/amd/display: Fix DSC-re-computing (stable-fixes).\n- drm/amd/display: Fix Synaptics Cascaded Panamera DSC Determination (stable-fixes).\n- drm/amd/display: Fix incorrect DSC recompute trigger (stable-fixes).\n- drm/amd/display: Revert Avoid overflow assignment (stable-fixes).\n- drm/amd/display: Use HW lock mgr for PSR1 (stable-fixes).\n- drm/amd/display: Use gpuvm_min_page_size_kbytes for DML2 surfaces (stable-fixes).\n- drm/amd/display: increase MAX_SURFACES to the value supported by hw (stable-fixes).\n- drm/amd/pm: Fix an error handling path in vega10_enable_se_edc_force_stall_config() (git-fixes).\n- drm/amd/pm: fix the high voltage issue after unload (stable-fixes).\n- drm/amd/pm: update current_socclk and current_uclk in gpu_metrics on smu v13.0.7 (stable-fixes).\n- drm/amdgpu/gfx10: use rlc safe mode for soft recovery (stable-fixes).\n- drm/amdgpu/gfx11: use rlc safe mode for soft recovery (stable-fixes).\n- drm/amdgpu/gfx9: properly handle error ints on all pipes (stable-fixes).\n- drm/amdgpu/gfx9: use rlc safe mode for soft recovery (stable-fixes).\n- drm/amdgpu/hdp5.2: do a posting read when flushing HDP (stable-fixes).\n- drm/amdgpu/pm: Remove gpu_od if it's an empty directory (stable-fixes).\n- drm/amdgpu/umsch: do not execute umsch test when GPU is in reset/suspend (stable-fixes).\n- drm/amdgpu/umsch: reinitialize write pointer in hw init (stable-fixes).\n- drm/amdgpu/vcn: reset fw_shared under SRIOV (git-fixes).\n- drm/amdgpu/vcn: reset fw_shared when VCPU buffers corrupted on vcn v4.0.3 (stable-fixes).\n- drm/amdgpu: Block MMR_READ IOCTL in reset (stable-fixes).\n- drm/amdgpu: Dereference the ATCS ACPI buffer (stable-fixes).\n- drm/amdgpu: Fix potential NULL pointer dereference in atomctrl_get_smc_sclk_range_table (git-fixes).\n- drm/amdgpu: add raven1 gfxoff quirk (stable-fixes).\n- drm/amdgpu: add smu 14.0.1 discovery support (stable-fixes).\n- drm/amdgpu: always sync the GFX pipe on ctx switch (stable-fixes).\n- drm/amdgpu: clear RB_OVERFLOW bit when enabling interrupts for vega20_ih (stable-fixes).\n- drm/amdgpu: differentiate external rev id for gfx 11.5.0 (stable-fixes).\n- drm/amdgpu: disallow multiple BO_HANDLES chunks in one submit (stable-fixes).\n- drm/amdgpu: do not access invalid sched (git-fixes).\n- drm/amdgpu: enable gfxoff quirk on HP 705G4 (stable-fixes).\n- drm/amdgpu: fix unchecked return value warning for amdgpu_gfx (stable-fixes).\n- drm/amdgpu: fix usage slab after free (stable-fixes).\n- drm/amdgpu: prevent BO_HANDLES error from being overwritten (git-fixes).\n- drm/amdgpu: refine error handling in amdgpu_ttm_tt_pin_userptr (stable-fixes).\n- drm/amdgpu: set the right AMDGPU sg segment limitation (stable-fixes).\n- drm/amdgpu: simplify return statement in amdgpu_ras_eeprom_init (git-fixes).\n- drm/amdgpu: skip amdgpu_device_cache_pci_state under sriov (stable-fixes).\n- drm/amdgpu: tear down ttm range manager for doorbell in amdgpu_ttm_fini() (git-fixes).\n- drm/amdkfd: Correct the migration DMA map direction (stable-fixes).\n- drm/amdkfd: Fix resource leak in criu restore queue (stable-fixes).\n- drm/amdkfd: Use device based logging for errors (stable-fixes).\n- drm/amdkfd: Use the correct wptr size (stable-fixes).\n- drm/amdkfd: fixed page fault when enable MES shader debugger (git-fixes).\n- drm/amdkfd: pause autosuspend when creating pdd (stable-fixes).\n- drm/bridge: adv7511_audio: Update Audio InfoFrame properly (git-fixes).\n- drm/bridge: it6505: Change definition of AUX_FIFO_MAX_SIZE (git-fixes).\n- drm/bridge: it6505: Enable module autoloading (stable-fixes).\n- drm/bridge: it6505: Fix inverted reset polarity (git-fixes).\n- drm/bridge: it6505: update usleep_range for RC circuit charge time (stable-fixes).\n- drm/display: Fix building with GCC 15 (stable-fixes).\n- drm/dp_mst: Ensure mst_primary pointer is valid in drm_dp_mst_handle_up_req() (stable-fixes).\n- drm/dp_mst: Fix MST sideband message body length check (stable-fixes).\n- drm/dp_mst: Fix resetting msg rx state after topology removal (git-fixes).\n- drm/dp_mst: Verify request type in the corresponding down message reply (stable-fixes).\n- drm/etnaviv: Fix page property being used for non writecombine buffers (git-fixes).\n- drm/etnaviv: flush shader L1 cache after user commandstream (stable-fixes).\n- drm/i915/dg1: Fix power gate sequence (git-fixes).\n- drm/i915/fb: Relax clear color alignment to 64 bytes (stable-fixes).\n- drm/i915: Fix NULL pointer dereference in capture_engine (git-fixes).\n- drm/i915: Fix memory leak by correcting cache object name in error handler (git-fixes).\n- drm/mcde: Enable module autoloading (stable-fixes).\n- drm/mediatek: Add return value check when reading DPCD (git-fixes).\n- drm/mediatek: Add support for 180-degree rotation in the display driver (git-fixes).\n- drm/mediatek: Fix YCbCr422 color format issue for DP (git-fixes).\n- drm/mediatek: Fix mode valid issue for dp (git-fixes).\n- drm/mediatek: Set private-\u003eall_drm_private[i]-\u003edrm to NULL if mtk_drm_bind returns err (git-fixes).\n- drm/mediatek: mtk_dsi: Add registers to pdata to fix MT8186/MT8188 (git-fixes).\n- drm/mediatek: stop selecting foreign drivers (git-fixes).\n- drm/modes: Avoid divide by zero harder in drm_mode_vrefresh() (stable-fixes).\n- drm/msm/dp: set safe_to_exit_level before printing it (git-fixes).\n- drm/msm/dpu: link DSPP_2/_3 blocks on SC8180X (git-fixes).\n- drm/msm/dpu: link DSPP_2/_3 blocks on SM8150 (git-fixes).\n- drm/msm/dpu: link DSPP_2/_3 blocks on SM8250 (git-fixes).\n- drm/msm/dpu: link DSPP_2/_3 blocks on SM8350 (git-fixes).\n- drm/msm/dpu: link DSPP_2/_3 blocks on SM8550 (git-fixes).\n- drm/msm: Check return value of of_dma_configure() (git-fixes).\n- drm/msm: do not clean up priv-\u003ekms prematurely (git-fixes).\n- drm/nouveau/gsp: Use the sg allocator for level 2 of radix3 (stable-fixes).\n- drm/panel: novatek-nt35950: fix return value check in nt35950_probe() (git-fixes).\n- drm/panel: simple: Add Microchip AC69T88A LVDS Display panel (stable-fixes).\n- drm/printer: Allow NULL data in devcoredump printer (stable-fixes).\n- drm/radeon/r100: Handle unknown family in r100_cp_init_microcode() (stable-fixes).\n- drm/radeon/r600_cs: Fix possible int overflow in r600_packet3_check() (stable-fixes).\n- drm/radeon: Fix spurious unplug event on radeon HDMI (git-fixes).\n- drm/radeon: add helper rdev_to_drm(rdev) (stable-fixes).\n- drm/radeon: change rdev-\u003eddev to rdev_to_drm(rdev) (stable-fixes).\n- drm/rcar-du: dsi: Fix PHY lock bit check (git-fixes).\n- drm/rockchip: cdn-dp: Use drm_connector_helper_hpd_irq_event() (git-fixes).\n- drm/rockchip: vop2: Check linear format for Cluster windows on rk3566/8 (git-fixes).\n- drm/rockchip: vop2: Fix cluster windows alpha ctrl regsiters offset (git-fixes).\n- drm/rockchip: vop2: Fix the mixer alpha setup for layer 0 (git-fixes).\n- drm/sched: memset() 'job' in drm_sched_job_init() (stable-fixes).\n- drm/tidss: Clear the interrupt status for interrupts being disabled (git-fixes).\n- drm/tidss: Fix issue in irq handling causing irq-flood issue (git-fixes).\n- drm/v3d: Assign job pointer to NULL before signaling the fence (git-fixes).\n- drm/v3d: Ensure job pointer is set to NULL after job completion (git-fixes).\n- drm/v3d: Stop active perfmon if it is being destroyed (git-fixes).\n- drm/vc4: hdmi: Avoid log spam for audio start failure (stable-fixes).\n- drm/vc4: hvs: Set AXI panic modes for the HVS (stable-fixes).\n- drm/vmwgfx: Add new keep_resv BO param (git-fixes).\n- drm: adv7511: Drop dsi single lane support (git-fixes).\n- drm: adv7511: Fix use-after-free in adv7533_attach_dsi() (git-fixes).\n- drm: panel-orientation-quirks: Add quirk for AYA NEO 2 model (stable-fixes).\n- drm: panel-orientation-quirks: Add quirk for AYA NEO Founder edition (stable-fixes).\n- drm: panel-orientation-quirks: Add quirk for AYA NEO GEEK (stable-fixes).\n- drm: panel-orientation-quirks: Make Lenovo Yoga Tab 3 X90F DMI match less strict (stable-fixes).\n- erofs: avoid debugging output for (de)compressed data (git-fixes).\n- exfat: ensure that ctime is updated whenever the mtime is (git-fixes).\n- exfat: fix the infinite loop in __exfat_free_cluster() (git-fixes).\n- exfat: fix the infinite loop in exfat_readdir() (git-fixes).\n- exfat: fix uninit-value in __exfat_get_dentry_set (git-fixes).\n- ext4: add a new helper to check if es must be kept (bsc#1234170).\n- ext4: add correct group descriptors and reserved GDT blocks to system zone (bsc#1234164).\n- ext4: add missed brelse in update_backups (bsc#1234171).\n- ext4: allow for the last group to be marked as trimmed (bsc#1234278).\n- ext4: avoid buffer_head leak in ext4_mark_inode_used() (bsc#1234191).\n- ext4: avoid excessive credit estimate in ext4_tmpfile() (bsc#1234180).\n- ext4: avoid negative min_clusters in find_group_orlov() (bsc#1234193).\n- ext4: avoid overlapping preallocations due to overflow (bsc#1234162).\n- ext4: avoid potential buffer_head leak in __ext4_new_inode() (bsc#1234192).\n- ext4: avoid writing unitialized memory to disk in EA inodes (bsc#1234187).\n- ext4: check the extent status again before inserting delalloc block (bsc#1234186).\n- ext4: clear EXT4_GROUP_INFO_WAS_TRIMMED_BIT even mount with discard (bsc#1234190).\n- ext4: convert to exclusive lock while inserting delalloc extents (bsc#1234178).\n- ext4: correct best extent lstart adjustment logic (bsc#1234179).\n- ext4: correct grp validation in ext4_mb_good_group (bsc#1234163).\n- ext4: correct return value of ext4_convert_meta_bg (bsc#1234172).\n- ext4: correct the hole length returned by ext4_map_blocks() (bsc#1234178).\n- ext4: correct the start block of counting reserved clusters (bsc#1234169).\n- ext4: do not let fstrim block system suspend (bsc#1234166).\n- ext4: do not trim the group with corrupted block bitmap (bsc#1234177).\n- ext4: factor out __es_alloc_extent() and __es_free_extent() (bsc#1234170).\n- ext4: factor out a common helper to query extent map (bsc#1234186).\n- ext4: fix inconsistent between segment fstrim and full fstrim (bsc#1234176).\n- ext4: fix incorrect tid assumption in __jbd2_log_wait_for_space() (bsc#1234188).\n- ext4: fix incorrect tid assumption in ext4_wait_for_tail_page_commit() (bsc#1234188).\n- ext4: fix incorrect tid assumption in jbd2_journal_shrink_checkpoint_list() (bsc#1234188).\n- ext4: fix memory leaks in ext4_fname_{setup_filename,prepare_lookup} (bsc#1214954).\n- ext4: fix potential unnitialized variable (bsc#1234183).\n- ext4: fix race between writepages and remount (bsc#1234168).\n- ext4: fix rec_len verify error (bsc#1234167).\n- ext4: fix slab-use-after-free in ext4_es_insert_extent() (bsc#1234170).\n- ext4: fix uninitialized variable in ext4_inlinedir_to_tree (bsc#1234185).\n- ext4: forbid commit inconsistent quota data when errors=remount-ro (bsc#1234178).\n- ext4: make ext4_es_insert_delayed_block() return void (bsc#1234170).\n- ext4: make ext4_es_insert_extent() return void (bsc#1234170).\n- ext4: make ext4_es_remove_extent() return void (bsc#1234170).\n- ext4: make ext4_zeroout_es() return void (bsc#1234170).\n- ext4: make sure allocate pending entry not fail (bsc#1234170).\n- ext4: mark buffer new if it is unwritten to avoid stale data exposure (bsc#1234175).\n- ext4: move 'ix' sanity check to corrent position (bsc#1234174).\n- ext4: move setting of trimmed bit into ext4_try_to_trim_range() (bsc#1234165).\n- ext4: nested locking for xattr inode (bsc#1234189).\n- ext4: propagate errors from ext4_find_extent() in ext4_insert_range() (bsc#1234194).\n- ext4: refactor ext4_da_map_blocks() (bsc#1234178).\n- ext4: remove gdb backup copy for meta bg in setup_new_flex_group_blocks (bsc#1234173).\n- ext4: remove the redundant folio_wait_stable() (bsc#1234184).\n- ext4: set the type of max_zeroout to unsigned int to avoid overflow (bsc#1234182).\n- ext4: set type of ac_groups_linear_remaining to __u32 to avoid overflow (bsc#1234181).\n- ext4: use pre-allocated es in __es_insert_extent() (bsc#1234170).\n- ext4: use pre-allocated es in __es_remove_extent() (bsc#1234170).\n- ext4: using nofail preallocation in ext4_es_insert_delayed_block() (bsc#1234170).\n- ext4: using nofail preallocation in ext4_es_insert_extent() (bsc#1234170).\n- ext4: using nofail preallocation in ext4_es_remove_extent() (bsc#1234170).\n- fbdev: omapfb: Fix an OF node leak in dss_of_port_get_parent_device() (git-fixes).\n- filemap: Fix bounds checking in filemap_read() (bsc#1234209).\n- filemap: add a per-mapping stable writes flag (bsc#1234141).\n- firmware: arm_scmi: Reject clear channel request on A2P (stable-fixes).\n- fs-writeback: do not requeue a clean inode having skipped pages (bsc#1234200).\n- fs/writeback: bail out if there is no more inodes for IO and queued once (bsc#1234207).\n- fsnotify: fix sending inotify event with unexpected filename (bsc#1234198).\n- genirq/cpuhotplug: Retry with cpu_online_mask when migration fails (git-fixes).\n- genirq/cpuhotplug: Skip suspended interrupts when restoring affinity (git-fixes).\n- genirq/irqdesc: Honor caller provided affinity in alloc_desc() (git-fixes).\n- genirq: Make handle_enforce_irqctx() unconditionally available (git-fixes).\n- genksyms: fix memory leak when the same symbol is added from source (git-fixes).\n- genksyms: fix memory leak when the same symbol is read from *.symref file (git-fixes).\n- gfs2: Truncate address space when flipping GFS2_DIF_JDATA flag (git-fixes).\n- gpio: grgpio: Add NULL check in grgpio_probe (git-fixes).\n- gpio: grgpio: use a helper variable to store the address of ofdev-\u003edev (stable-fixes).\n- gpio: mxc: remove dead code after switch to DT-only (git-fixes).\n- gpio: xilinx: Convert gpio_lock to raw spinlock (git-fixes).\n- hfsplus: do not query the device logical block size multiple times (git-fixes).\n- hvc/xen: fix console unplug (git-fixes).\n- hvc/xen: fix error path in xen_hvc_init() to always register frontend driver (git-fixes).\n- hvc/xen: fix event channel handling for secondary consoles (git-fixes).\n- hwmon: (drivetemp) Fix driver producing garbage data when SCSI errors occur (git-fixes).\n- hwmon: (drivetemp) Set scsi command timeout to 10s (stable-fixes).\n- hwmon: (nct6775) Add 665-ACE/600M-CL to ASUS WMI monitoring list (stable-fixes).\n- hwmon: (pmbus/core) clear faults after setting smbalert mask (git-fixes).\n- hwmon: (pmbus_core) Allow to hook PMBUS_SMBALERT_MASK (stable-fixes).\n- hwmon: (tmp513) Do not use \"proxy\" headers (stable-fixes).\n- hwmon: (tmp513) Fix Current Register value interpretation (git-fixes).\n- hwmon: (tmp513) Fix division of negative numbers (git-fixes).\n- hwmon: (tmp513) Fix interpretation of values of Shunt Voltage and Limit Registers (git-fixes).\n- hwmon: (tmp513) Fix interpretation of values of Temperature Result and Limit Registers (git-fixes).\n- hwmon: (tmp513) Simplify with dev_err_probe() (stable-fixes).\n- hwmon: (tmp513) Use SI constants from units.h (stable-fixes).\n- hyperv: Do not overlap the hvcall IO areas in get_vtl() (git-fixes).\n- i2c: core: fix reference leak in i2c_register_adapter() (git-fixes).\n- i2c: i801: Add support for Intel Arrow Lake-H (stable-fixes).\n- i2c: i801: Add support for Intel Panther Lake (stable-fixes).\n- i2c: imx: add imx7d compatible string for applying erratum ERR007805 (git-fixes).\n- i2c: microchip-core: actually use repeated sends (git-fixes).\n- i2c: microchip-core: fix \"ghost\" detections (git-fixes).\n- i2c: mux: demux-pinctrl: check initial mux selection, too (git-fixes).\n- i2c: pnx: Fix timeout in wait functions (git-fixes).\n- i2c: rcar: fix NACK handling when being a target (git-fixes).\n- i2c: riic: Always round-up when calculating bus period (git-fixes).\n- i2c: xgene-slimpro: Migrate to use generic PCC shmem related macros (stable-fixes).\n- i40e: Fix handling changed priv flags (git-fixes).\n- i915/guc: Accumulate active runtime on gt reset (git-fixes).\n- i915/guc: Ensure busyness counter increases motonically (git-fixes).\n- i915/guc: Reset engine utilization buffer before registration (git-fixes).\n- ibmvnic: Free any outstanding tx skbs during scrq reset (bsc#1226980).\n- ice: Unbind the workqueue (bsc#1234989)\n- ice: change q_index variable type to s16 to store -1 value (git-fixes).\n- ice: consistently use q_idx in ice_vc_cfg_qs_msg() (git-fixes).\n- ice: fix PHY Clock Recovery availability check (git-fixes).\n- idpf: add support for SW triggered interrupts (bsc#1235507).\n- idpf: enable WB_ON_ITR (bsc#1235507).\n- idpf: trigger SW interrupt when exiting wb_on_itr mode (bsc#1235507).\n- ieee802154: ca8210: Add missing check for kfifo_alloc() in ca8210_probe() (git-fixes).\n- igb: Fix potential invalid memory access in igb_init_module() (git-fixes).\n- iio: adc: ad7124: Disable all channels at probe time (git-fixes).\n- iio: adc: ad_sigma_delta: Handle CS assertion as intended in ad_sd_read_reg_raw() (git-fixes).\n- iio: adc: at91: call input_free_device() on allocated iio_dev (git-fixes).\n- iio: adc: rockchip_saradc: fix information leak in triggered buffer (git-fixes).\n- iio: adc: ti-ads124s08: Use gpiod_set_value_cansleep() (git-fixes).\n- iio: adc: ti-ads8688: fix information leak in triggered buffer (git-fixes).\n- iio: dummy: iio_simply_dummy_buffer: fix information leak in triggered buffer (git-fixes).\n- iio: gyro: fxas21002c: Fix missing data update in trigger handler (git-fixes).\n- iio: iio-mux: kzalloc instead of devm_kzalloc to ensure page alignment (git-fixes).\n- iio: imu: kmx61: fix information leak in triggered buffer (git-fixes).\n- iio: inkern: call iio_device_put() only on mapped devices (git-fixes).\n- iio: light: as73211: fix channel handling in only-color triggered buffer (git-fixes).\n- iio: light: vcnl4035: fix information leak in triggered buffer (git-fixes).\n- iio: magnetometer: yas530: use signed integer type for clamp limits (git-fixes).\n- iio: pressure: zpa2326: fix information leak in triggered buffer (git-fixes).\n- iio: test : check null return of kunit_kmalloc in iio_rescale_test_scale (git-fixes).\n- instrumentation: Wire up cmpxchg128() (bsc#1220773).\n- intel_th: core: fix kernel-doc warnings (git-fixes).\n- io_uring/rw: avoid punting to io-wq directly (git-fixes).\n- io_uring/tctx: work around xa_store() allocation error issue (git-fixes).\n- io_uring: Fix registered ring file refcount leak (git-fixes).\n- io_uring: always lock __io_cqring_overflow_flush (git-fixes).\n- io_uring: check if iowq is killed before queuing (git-fixes).\n- iommu/io-pgtable-arm: Fix stage-2 map/unmap for concatenated tables (git-fixes).\n- ipmi: ipmb: Add check devm_kasprintf() returned value (git-fixes).\n- ipmi: ssif_bmc: Fix new request loss when bmc ready for a response (git-fixes).\n- irqchip/gic-v3: Force propagation of the active state with a read-back (stable-fixes).\n- irqchip/gic: Correct declaration of *percpu_base pointer in union gic_base (stable-fixes).\n- irqflags: Explicitly ignore lockdep_hrtimer_exit() argument (git-fixes).\n- isofs: handle CDs with bad root inode but good Joliet root directory (bsc#1234199).\n- ixgbe: downgrade logging of unsupported VF API version to debug (git-fixes).\n- ixgbevf: stop attempting IPSEC offload on Mailbox API 1.5 (git-fixes).\n- jffs2: Fix rtime decompressor (git-fixes).\n- jffs2: Prevent rtime decompress memory corruption (git-fixes).\n- jffs2: fix use of uninitialized variable (git-fixes).\n- jfs: add a check to prevent array-index-out-of-bounds in dbAdjTree (git-fixes).\n- jfs: array-index-out-of-bounds fix in dtReadFirst (git-fixes).\n- jfs: fix array-index-out-of-bounds in jfs_readdir (git-fixes).\n- jfs: fix shift-out-of-bounds in dbSplit (git-fixes).\n- jfs: xattr: check invalid xattr size more strictly (git-fixes).\n- kABI workaround for struct auto_pin_cfg_item change (git-fixes).\n- kABI workaround for struct drm_dp_mst_topology_mgr (git-fixes).\n- kabi/severities: make vcap_find_actionfield PASS (bsc#1220773)\n- kasan: make report_lock a raw spinlock (git-fixes).\n- kconfig: fix file name in warnings when loading KCONFIG_DEFCONFIG_LIST (git-fixes).\n- kdb: Fix buffer overflow during tab-complete (bsc#1234652).\n- kdb: Fix console handling when editing and tab-completing commands (bsc#1234655).\n- kdb: Merge identical case statements in kdb_read() (bsc#1234657).\n- kdb: Use format-specifiers rather than memset() for padding in kdb_read() (bsc#1234658).\n- kdb: Use format-strings rather than '\\0' injection in kdb_read() (bsc#1234654).\n- kdb: Use the passed prompt in kdb_position_cursor() (bsc#1234654).\n- kdb: address -Wformat-security warnings (bsc#1234659).\n- kgdb: Flush console before entering kgdb on panic (bsc#1234651).\n- kheaders: Ignore silly-rename files (stable-fixes).\n- ktest.pl: Avoid false positives with grub2 skip regex (stable-fixes).\n- ktest.pl: Check kernelrelease return in get_version (git-fixes).\n- ktest.pl: Fix typo \"accesing\" (git-fixes).\n- ktest.pl: Fix typo in comment (git-fixes).\n- ktest.pl: Remove unused declarations in run_bisect_test function (git-fixes).\n- ktest: force $buildonly = 1 for 'make_warnings_file' test type (stable-fixes).\n- landlock: Handle weird files (git-fixes).\n- latencytop: use correct kernel-doc format for func params (git-fixes).\n- leds: class: Protect brightness_show() with led_cdev-\u003eled_access mutex (stable-fixes).\n- leds: lp8860: Write full EEPROM, not only half of it (git-fixes).\n- leds: netxbig: Fix an OF node reference leak in netxbig_leds_get_of_pdata() (git-fixes).\n- lib/inflate.c: remove dead code (git-fixes).\n- lib/stackdepot: print disabled message only if truly disabled (git-fixes).\n- linux/dmaengine.h: fix a few kernel-doc warnings (git-fixes).\n- locking/atomic/x86: Correct the definition of __arch_try_cmpxchg128() (bsc#1220773 git-fix).\n- loop: fix the the direct I/O support check when used on top of block devices (bsc#1234143).\n- mac80211: fix user-power when emulating chanctx (stable-fixes).\n- mac802154: check local interfaces before deleting sdata list (stable-fixes).\n- mailbox: pcc: Add support for platform notification handling (stable-fixes).\n- mailbox: pcc: Support shared interrupt for multiple subspaces (stable-fixes).\n- mailbox: tegra-hsp: Clear mailbox before using message (git-fixes).\n- maple_tree: simplify split calculation (git-fixes).\n- media: camif-core: Add check for clk_enable() (git-fixes).\n- media: ccs: Clean up parsed CCS static data on parse failure (git-fixes).\n- media: ccs: Fix CCS static data parsing for large block sizes (git-fixes).\n- media: ccs: Fix cleanup order in ccs_probe() (git-fixes).\n- media: cx231xx: Add support for Dexatek USB Video Grabber 1d19:6108 (stable-fixes).\n- media: dvb-frontends: dib3000mb: fix uninit-value in dib3000_write_reg (git-fixes).\n- media: dvb-usb-v2: af9035: fix ISO C90 compilation error on af9035_i2c_master_xfer (git-fixes).\n- media: i2c: imx412: Add missing newline to prints (git-fixes).\n- media: i2c: ov9282: Correct the exposure offset (git-fixes).\n- media: imx-jpeg: Fix potential error pointer dereference in detach_pm() (git-fixes).\n- media: imx296: Add standby delay during probe (git-fixes).\n- media: lmedm04: Handle errors for lme2510_int_read (git-fixes).\n- media: marvell: Add check for clk_enable() (git-fixes).\n- media: mc: fix endpoint iteration (git-fixes).\n- media: mipi-csis: Add check for clk_enable() (git-fixes).\n- media: nxp: imx8-isi: fix v4l2-compliance test errors (git-fixes).\n- media: ov5640: fix get_light_freq on auto (git-fixes).\n- media: rc: iguanair: handle timeouts (git-fixes).\n- media: rkisp1: Fix unused value issue (git-fixes).\n- media: uvcvideo: Add a quirk for the Kaiweets KTI-W02 infrared camera (stable-fixes).\n- media: uvcvideo: Fix crash during unbind if gpio unit is in use (git-fixes).\n- media: uvcvideo: Fix double free in error path (git-fixes).\n- media: uvcvideo: Fix event flags in uvc_ctrl_send_events (git-fixes).\n- media: uvcvideo: Force UVC version to 1.0a for 0408:4035 (stable-fixes).\n- media: uvcvideo: Only save async fh if success (git-fixes).\n- media: uvcvideo: Propagate buf-\u003eerror to userspace (git-fixes).\n- media: uvcvideo: RealSense D421 Depth module metadata (stable-fixes).\n- media: uvcvideo: Remove dangling pointers (git-fixes).\n- media: uvcvideo: Remove redundant NULL assignment (git-fixes).\n- media: uvcvideo: Support partial control reads (git-fixes).\n- memory tiering: count PGPROMOTE_SUCCESS when mem tiering is enabled (git-fixes).\n- memory-failure: use a folio in me_huge_page() (git-fixes).\n- memory: tegra20-emc: fix an OF node reference bug in tegra_emc_find_node_by_ram_code() (git-fixes).\n- mfd: da9052-spi: Change read-mask to write-mask (git-fixes).\n- mfd: intel_soc_pmic_bxtwc: Use IRQ domain for PMIC devices (git-fixes).\n- mfd: intel_soc_pmic_bxtwc: Use IRQ domain for TMU device (git-fixes).\n- mfd: intel_soc_pmic_bxtwc: Use IRQ domain for USB Type-C device (git-fixes).\n- misc: fastrpc: Deregister device nodes properly in error scenarios (git-fixes).\n- misc: fastrpc: Fix copy buffer page size (git-fixes).\n- misc: fastrpc: Fix registered buffer page address (git-fixes).\n- misc: microchip: pci1xxxx: Resolve kernel panic during GPIO IRQ handling (git-fixes).\n- misc: microchip: pci1xxxx: Resolve return code mismatch during GPIO set config (git-fixes).\n- misc: misc_minor_alloc to use ida for all dynamic/misc dynamic minors (git-fixes).\n- mm, kmsan: fix infinite recursion due to RCU critical section (git-fixes).\n- mm,page_owner: do not remove __GFP_NOLOCKDEP in add_stack_record_to_list (git-fixes).\n- mm/filemap: avoid buffered read/write race to read inconsistent data (bsc#1234204).\n- mm/memory-failure: cast index to loff_t before shifting it (git-fixes).\n- mm/memory-failure: check the mapcount of the precise page (git-fixes).\n- mm/memory-failure: fix crash in split_huge_page_to_list from soft_offline_page (git-fixes).\n- mm/memory-failure: pass the folio and the page to collect_procs() (git-fixes).\n- mm/memory-failure: use raw_spinlock_t in struct memory_failure_cpu (git-fixes).\n- mm/memory_hotplug: add missing mem_hotplug_lock (git-fixes).\n- mm/memory_hotplug: fix error handling in add_memory_resource() (git-fixes).\n- mm/memory_hotplug: prevent accessing by index=-1 (git-fixes).\n- mm/memory_hotplug: use pfn math in place of direct struct page manipulation (git-fixes).\n- mm/migrate: correct nr_failed in migrate_pages_sync() (git-fixes).\n- mm/migrate: fix deadlock in migrate_pages_batch() on large folios (git-fixes).\n- mm/migrate: putback split folios when numa hint migration fails (git-fixes).\n- mm/migrate: split source folio if it is on deferred split list (git-fixes).\n- mm/page_owner: remove free_ts from page_owner output (git-fixes).\n- mm/readahead: do not allow order-1 folio (bsc#1234205).\n- mm/readahead: limit page cache size in page_cache_ra_order() (bsc#1234208).\n- mm/rodata_test: use READ_ONCE() to read const variable (git-fixes).\n- mm: convert DAX lock/unlock page to lock/unlock folio (git-fixes).\n- mm: memory-failure: ensure moving HWPoison flag to the raw error pages (git-fixes).\n- mm: memory-failure: fetch compound head after extra page refcnt is held (git-fixes).\n- mm: memory-failure: fix potential page refcnt leak in memory_failure() (git-fixes).\n- mm: memory-failure: fix race window when trying to get hugetlb folio (git-fixes).\n- mm: memory-failure: remove unneeded PageHuge() check (git-fixes).\n- mm: prevent derefencing NULL ptr in pfn_section_valid() (git-fixes).\n- mmc: core: Add SD card quirk for broken poweroff notification (stable-fixes).\n- mmc: mtk-sd: Fix MMC_CAP2_CRYPTO flag setting (git-fixes).\n- mmc: mtk-sd: fix devm_clk_get_optional usage (stable-fixes).\n- mmc: sdhci-esdhc-imx: enable quirks SDHCI_QUIRK_NO_LED (stable-fixes).\n- mmc: sdhci-pci: Add DMI quirk for missing CD GPIO on Vexia Edu Atla 10 tablet (stable-fixes).\n- mmc: sdhci-tegra: Remove SDHCI_QUIRK_BROKEN_ADMA_ZEROLEN_DESC quirk (git-fixes).\n- modpost: fix the missed iteration for the max bit in do_input() (git-fixes).\n- mtd: diskonchip: Cast an operand to prevent potential overflow (git-fixes).\n- mtd: hyperbus: rpc-if: Add missing MODULE_DEVICE_TABLE (git-fixes).\n- mtd: hyperbus: rpc-if: Convert to platform remove callback returning void (stable-fixes).\n- mtd: onenand: Fix uninitialized retlen in do_otp_read() (git-fixes).\n- mtd: rawnand: arasan: Fix double assertion of chip-select (git-fixes).\n- mtd: rawnand: arasan: Fix missing de-registration of NAND (git-fixes).\n- mtd: rawnand: fix double free in atmel_pmecc_create_user() (git-fixes).\n- mtd: spinand: Remove write_enable_op() in markbad() (git-fixes).\n- net :mana :Request a V2 response version for MANA_QUERY_GF_STAT (git-fixes).\n- net/ipv6: release expired exception dst cached in socket (bsc#1216813).\n- net/mlx5e: CT: Fix null-ptr-deref in add rule err flow (git-fixes).\n- net/mlx5e: Remove workaround to avoid syndrome for internal port (git-fixes).\n- net/mlx5e: clear xdp features on non-uplink representors (git-fixes).\n- net/qed: allow old cards not supporting \"num_images\" to work (git-fixes).\n- net/rose: prevent integer overflows in rose_setsockopt() (git-fixes).\n- net: Return error from sk_stream_wait_connect() if sk_wait_event() fails (git-fixes).\n- net: mana: Increase the DEF_RX_BUFFERS_PER_QUEUE to 1024 (bsc#1235246).\n- net: phy: c45-tjaxx: add delay between MDIO write and read in soft_reset (git-fixes).\n- net: rose: fix timer races against user threads (git-fixes).\n- net: usb: qmi_wwan: add Quectel RG650V (stable-fixes).\n- net: usb: qmi_wwan: add Telit FE910C04 compositions (stable-fixes).\n- net: usb: rtl8150: enable basic endpoint checking (git-fixes).\n- net: wwan: iosm: Properly check for valid exec stage in ipc_mmio_init() (git-fixes).\n- net: wwan: t7xx: Fix FSM command timeout issue (git-fixes).\n- netfilter: nf_tables: validate family when identifying table via handle (bsc#1233778 ZDI-24-1454).\n- nfs: ignore SB_RDONLY when mounting nfs (git-fixes).\n- nfsd: fix nfs4_openowner leak when concurrent nfsd4_open occur (git-fixes).\n- nfsd: make sure exp active before svc_export_show (git-fixes).\n- nfsd: release svc_expkey/svc_export with rcu_work (git-fixes).\n- nfsd: restore callback functionality for NFSv4.0 (git-fixes).\n- nilfs2: fix buffer head leaks in calls to truncate_inode_pages() (git-fixes).\n- nilfs2: fix possible int overflows in nilfs_fiemap() (git-fixes).\n- nilfs2: fix potential out-of-bounds memory access in nilfs_find_entry() (git-fixes).\n- nilfs2: prevent use of deleted inode (git-fixes).\n- nvme-pci: 512 byte aligned dma pool segment quirk (git-fixes).\n- nvme-rdma: unquiesce admin_q before destroy it (git-fixes).\n- nvme-tcp: Fix I/O queue cpu spreading for multiple controllers (git-fixes).\n- nvme-tcp: fix the memleak while create new ctrl failed (git-fixes).\n- nvme/multipath: Fix RCU list traversal to use SRCU primitive (git-fixes).\n- nvme: Add error check for xa_store in nvme_get_effects_log (git-fixes).\n- nvme: Add error path for xa_store in nvme_init_effects (git-fixes).\n- nvme: apple: fix device reference counting (git-fixes).\n- nvme: fix bogus kzalloc() return check in nvme_init_effects_log() (git-fixes).\n- nvme: fix metadata handling in nvme-passthrough (git-fixes).\n- nvmet-loop: avoid using mutex in IO hotpath (git-fixes).\n- nvmet: propagate npwg topology (git-fixes).\n- ocfs2: fix uninitialized value in ocfs2_file_read_iter() (git-fixes).\n- ocfs2: free inode when ocfs2_get_init_inode() fails (git-fixes).\n- of/irq: Fix using uninitialized variable @addr_len in API of_irq_parse_one() (git-fixes).\n- of: Fix error path in of_parse_phandle_with_args_map() (git-fixes).\n- of: Fix refcount leakage for OF node returned by __of_get_dma_parent() (git-fixes).\n- of: address: Report error on resource bounds overflow (stable-fixes).\n- padata: add pd get/put refcnt helper (git-fixes).\n- padata: avoid UAF for reorder_work (git-fixes).\n- padata: fix UAF in padata_reorder (git-fixes).\n- parisc: Raise minimal GCC version (bsc#1220773).\n- parisc: Raise minimal GCC version to 12.0.0 (bsc#1220773 git-fix).\n- percpu: Add {raw,this}_cpu_try_cmpxchg() (bsc#1220773).\n- percpu: Fix self-assignment of __old in raw_cpu_generic_try_cmpxchg() (bsc#1220773 git-fix).\n- percpu: Wire up cmpxchg128 (bsc#1220773).\n- phy: core: Fix an OF node refcount leakage in _of_phy_get() (git-fixes).\n- phy: core: Fix an OF node refcount leakage in of_phy_provider_lookup() (git-fixes).\n- phy: core: Fix that API devm_of_phy_provider_unregister() fails to unregister the phy provider (git-fixes).\n- phy: core: Fix that API devm_phy_destroy() fails to destroy the phy (git-fixes).\n- phy: core: Fix that API devm_phy_put() fails to release the phy (git-fixes).\n- phy: qcom-qmp: Fix register name in RX Lane config of SC8280XP (git-fixes).\n- phy: rockchip: naneng-combphy: fix phy reset (git-fixes).\n- phy: usb: Toggle the PHY power during init (git-fixes).\n- pinctrl: amd: Take suspend type into consideration which pins are non-wake (git-fixes).\n- pinctrl: mcp23s08: Fix sleeping in atomic context due to regmap locking (git-fixes).\n- pinctrl: qcom-pmic-gpio: add support for PM8937 (stable-fixes).\n- pinctrl: qcom: spmi-mpp: Add PM8937 compatible (stable-fixes).\n- pinctrl: samsung: fix fwnode refcount cleanup if platform_get_irq_optional() fails (git-fixes).\n- pinmux: Use sequential access to access desc-\u003epinmux data (stable-fixes).\n- platform/chrome: cros_ec_proto: Lock device when updating MKBP version (git-fixes).\n- platform/x86/amd/pmc: Only disable IRQ1 wakeup where i8042 actually enabled it (git-fixes).\n- platform/x86/intel-uncore-freq: Ignore minor version change (bsc#1225897).\n- platform/x86/intel/tpmi: Add defines to get version information (bsc#1225897).\n- platform/x86: asus-nb-wmi: Ignore unknown event 0xCF (stable-fixes).\n- platform/x86: dell-smbios-base: Extends support to Alienware products (stable-fixes).\n- platform/x86: dell-wmi-base: Handle META key Lock/Unlock events (stable-fixes).\n- platform/x86: thinkpad_acpi: Fix for ThinkPad's with ECFW showing incorrect fan speed (stable-fixes).\n- pm:cpupower: Add missing powercap_set_enabled() stub function (git-fixes).\n- power: ip5xxx_power: Fix return value on ADC read errors (git-fixes).\n- power: supply: gpio-charger: Fix set charge current limits (git-fixes).\n- powerpc/book3s64/hugetlb: Fix disabling hugetlb when fadump is active (bsc#1235108).\n- powerpc/iommu: Move pSeries specific functions to pseries/iommu.c (bsc#1220711 ltc#205755).\n- powerpc/iommu: Only build sPAPR access functions on pSeries (bsc#1220711 ltc#205755).\n- powerpc/powernv/pci: Remove MVE code (bsc#1220711 ltc#205755).\n- powerpc/powernv/pci: Remove ioda1 support (bsc#1220711 ltc#205755).\n- powerpc/powernv/pci: Remove last IODA1 defines (bsc#1220711 ltc#205755).\n- powerpc/pseries/eeh: Fix get PE state translation (bsc#1215199).\n- powerpc/pseries/iommu: IOMMU incorrectly marks MMIO range in DDW (bsc#1218470 ltc#204531).\n- powerpc/pseries/vas: Add close() callback in vas_vm_ops struct (bsc#1234825).\n- pps: add an error check in parport_attach (git-fixes).\n- pps: remove usage of the deprecated ida_simple_xx() API (stable-fixes).\n- printk: Add is_printk_legacy_deferred() (bsc#1236733).\n- printk: Defer legacy printing when holding printk_cpu_sync (bsc#1236733).\n- proc/softirqs: replace seq_printf with seq_put_decimal_ull_width (git-fixes).\n- pwm: stm32-lp: Add check for clk_enable() (git-fixes).\n- pwm: stm32: Add check for clk_enable() (git-fixes).\n- quota: Fix rcu annotations of inode dquot pointers (bsc#1234197).\n- quota: explicitly forbid quota files from being encrypted (bsc#1234196).\n- quota: flush quota_release_work upon quota writeback (bsc#1234195).\n- quota: simplify drop_dquot_ref() (bsc#1234197).\n- rcu-tasks: Pull sampling of -\u003epercpu_dequeue_lim out of loop (git-fixes)\n- rcu/tree: Defer setting of jiffies during stall reset (git-fixes)\n- rcu: Dump memory object info if callback function is invalid (git-fixes)\n- rcu: Eliminate rcu_gp_slow_unregister() false positive (git-fixes)\n- rcuscale: Move rcu_scale_writer() (git-fixes)\n- rdma/cxgb4: Prevent potential integer overflow on 32bit (git-fixes)\n- readahead: use ilog2 instead of a while loop in page_cache_ra_order() (bsc#1234208).\n- regmap: Use correct format specifier for logging range errors (stable-fixes).\n- regulator: core: Add missing newline character (git-fixes).\n- regulator: of: Implement the unwind path of of_regulator_match() (git-fixes).\n- regulator: rk808: Add apply_bit for BUCK3 on RK809 (stable-fixes).\n- remoteproc: core: Fix ida_free call while not allocated (git-fixes).\n- rtc: cmos: avoid taking rtc_lock for extended period of time (stable-fixes).\n- rtc: pcf85063: fix potential OOB write in PCF85063 NVMEM read (git-fixes).\n- rtc: zynqmp: Fix optional clock name property (git-fixes).\n- s390/cio: Do not unregister the subchannel based on DNV (git-fixes).\n- s390/cpum_sf: Convert to cmpxchg128() (bsc#1220773).\n- s390/cpum_sf: Handle CPU hotplug remove during sampling (git-fixes).\n- s390/cpum_sf: Remove WARN_ON_ONCE statements (git-fixes).\n- s390/facility: Disable compile time optimization for decompressor code (git-fixes).\n- s390/iucv: MSG_PEEK causes memory leak in iucv_sock_destruct() (git-fixes).\n- s390/pageattr: Implement missing kernel_page_present() (git-fixes).\n- s390x config: IOMMU_DEFAULT_DMA_LAZY=y (bsc#1235646)\n- samples/landlock: Fix possible NULL dereference in parse_path() (git-fixes).\n- scatterlist: fix incorrect func name in kernel-doc (git-fixes).\n- sched/fair: Fix value reported by hot tasks pulled in /proc/schedstat (bsc#1235865).\n- sched/fair: Fix value reported by hot tasks pulled in /proc/schedstat -kabi (bsc#1235865).\n- sched/numa: fix memory leak due to the overwritten vma-\u003enumab_state (git fixes (sched/numa)).\n- scsi: lpfc: Add handling for LS_RJT reason explanation authentication required (bsc#1235409).\n- scsi: lpfc: Add support for large fw object application layer reads (bsc#1235409).\n- scsi: lpfc: Change lpfc_nodelist save_flags member into a bitmask (bsc#1235409).\n- scsi: lpfc: Copyright updates for 14.4.0.7 patches (bsc#1235409).\n- scsi: lpfc: Delete NLP_TARGET_REMOVE flag due to obsolete usage (bsc#1235409).\n- scsi: lpfc: Modify handling of ADISC based on ndlp state and RPI registration (bsc#1235409).\n- scsi: lpfc: Redefine incorrect type in lpfc_create_device_data() (bsc#1235409).\n- scsi: lpfc: Restrict the REG_FCFI MAM field to FCoE adapters only (bsc#1235409).\n- scsi: lpfc: Update definition of firmware configuration mbox cmds (bsc#1235409).\n- scsi: lpfc: Update lpfc version to 14.4.0.7 (bsc#1235409).\n- scsi: qla2xxx: Fix NVMe and NPIV connect issue (bsc#1235406).\n- scsi: qla2xxx: Fix abort in bsg timeout (bsc#1235406).\n- scsi: qla2xxx: Fix use after free on unload (bsc#1235406).\n- scsi: qla2xxx: Remove check req_sg_cnt should be equal to rsp_sg_cnt (bsc#1235406).\n- scsi: qla2xxx: Remove the unused 'del_list_entry' field in struct fc_port (bsc#1235406).\n- scsi: qla2xxx: Supported speed displayed incorrectly for VPorts (bsc#1235406).\n- scsi: qla2xxx: Update version to 10.02.09.400-k (bsc#1235406).\n- scsi: storvsc: Do not flag MAINTENANCE_IN return of SRB_STATUS_DATA_OVERRUN as an error (git-fixes).\n- scsi: storvsc: Ratelimit warning logs to prevent VM denial of service (git-fixes).\n- seccomp: Stub for !CONFIG_SECCOMP (stable-fixes).\n- selftest: media_tests: fix trivial UAF typo (git-fixes).\n- selftests/alsa: Fix circular dependency involving global-timer (stable-fixes).\n- selftests/bpf: Test PROBE_MEM of VSYSCALL_ADDR on x86-64 (git-fixes).\n- selftests/landlock: Fix error message (git-fixes).\n- selftests/mm/cow: modify the incorrect checking parameters (git-fixes).\n- selftests/powerpc: Fix argument order to timer_sub() (git-fixes).\n- selftests: harness: fix printing of mismatch values in __EXPECT() (git-fixes).\n- selftests: mptcp: avoid spurious errors on disconnect (git-fixes).\n- selftests: tc-testing: reduce rshift value (stable-fixes).\n- selftests: timers: clocksource-switch: Adapt progress to kselftest framework (git-fixes).\n- selinux: Fix SCTP error inconsistency in selinux_socket_bind() (git-fixes).\n- serial: 8250: Adjust the timeout for FIFO mode (git-fixes).\n- serial: 8250_dw: Add Sophgo SG2044 quirk (stable-fixes).\n- serial: 8250_dw: Do not use struct dw8250_data outside of 8250_dw (git-fixes).\n- serial: 8250_dw: Replace ACPI device check by a quirk (git-fixes).\n- serial: 8250_fintek: Add support for F81216E (stable-fixes).\n- serial: Do not hold the port lock when setting rx-during-tx GPIO (git-fixes).\n- serial: amba-pl011: Fix RX stall when DMA is used (git-fixes).\n- serial: amba-pl011: Use port lock wrappers (stable-fixes).\n- serial: amba-pl011: fix build regression (git-fixes).\n- serial: do not use uninitialized value in uart_poll_init() (git-fixes).\n- serial: imx: only set receiver level if it is zero (git-fixes).\n- serial: imx: set receiver level before starting uart (git-fixes).\n- serial: qcom-geni: Do not cancel/abort if we can't get the port lock (git-fixes).\n- serial: qcom-geni: disable interrupts during console writes (git-fixes).\n- serial: qcom-geni: fix arg types for qcom_geni_serial_poll_bit() (git-fixes).\n- serial: qcom-geni: fix console corruption (git-fixes).\n- serial: qcom-geni: fix dma rx cancellation (git-fixes).\n- serial: qcom-geni: fix false console tx restart (git-fixes).\n- serial: qcom-geni: fix fifo polling timeout (git-fixes).\n- serial: qcom-geni: fix hard lockup on buffer flush (git-fixes).\n- serial: qcom-geni: fix polled console corruption (git-fixes).\n- serial: qcom-geni: fix polled console initialisation (git-fixes).\n- serial: qcom-geni: fix receiver enable (git-fixes).\n- serial: qcom-geni: fix shutdown race (git-fixes).\n- serial: qcom-geni: fix soft lockup on sw flow control and suspend (git-fixes).\n- serial: qcom-geni: introduce qcom_geni_serial_poll_bitfield() (git-fixes).\n- serial: qcom-geni: revert broken hibernation support (git-fixes).\n- serial: sh-sci: Do not probe the serial port if its slot in sci_ports[] is in use (git-fixes).\n- serial: sh-sci: Drop __initdata macro for port_cfg (git-fixes).\n- serial: stm32: Return IRQ_NONE in the ISR if no handling happend (git-fixes).\n- serial: stm32: do not always set SER_RS485_RX_DURING_TX if RS485 is enabled (git-fixes).\n- slub: Replace cmpxchg_double() (bsc#1220773).\n- slub: Replace cmpxchg_double() - KABI fix (bsc#1220773).\n- smb: client: fix TCP timers deadlock after rmmod (git-fixes) [hcarvalho: fix issue described in bsc#1233642]\n- soc/fsl: cpm: qmc: Convert to platform remove callback returning void (stable-fixes).\n- soc: atmel: fix device_node release in atmel_soc_device_init() (git-fixes).\n- soc: fsl: cpm1: qmc: Fix blank line and spaces (stable-fixes).\n- soc: fsl: cpm1: qmc: Introduce qmc_init_resource() and its CPM1 version (stable-fixes).\n- soc: fsl: cpm1: qmc: Introduce qmc_{init,exit}_xcc() and their CPM1 version (stable-fixes).\n- soc: fsl: cpm1: qmc: Re-order probe() operations (stable-fixes).\n- soc: fsl: cpm1: qmc: Set the ret error code on platform_get_irq() failure (git-fixes).\n- soc: imx8m: Probe the SoC driver as platform driver (stable-fixes).\n- soc: mediatek: mtk-devapc: Fix leaking IO map on error paths (git-fixes).\n- soc: qcom: Add check devm_kasprintf() returned value (stable-fixes).\n- soc: qcom: geni-se: Add M_TX_FIFO_NOT_EMPTY bit definition (git-fixes).\n- soc: qcom: geni-se: add GP_LENGTH/IRQ_EN_SET/IRQ_EN_CLEAR registers (git-fixes).\n- soc: qcom: smem_state: fix missing of_node_put in error path (git-fixes).\n- soc: qcom: socinfo: Avoid out of bounds read of serial number (git-fixes).\n- soc: qcom: socinfo: fix revision check in qcom_socinfo_probe() (git-fixes).\n- sound: usb: enable DSD output for ddHiFi TC44C (stable-fixes).\n- sound: usb: format: do not warn that raw DSD is unsupported (stable-fixes).\n- spi: aspeed: Fix an error handling path in aspeed_spi_[read|write]_user() (git-fixes).\n- spi: zynq-qspi: Add check for clk_enable() (git-fixes).\n- srcu: Fix srcu_struct node grpmask overflow on 64-bit systems (git-fixes)\n- srcu: Only accelerate on enqueue time (git-fixes)\n- stackdepot: rename pool_index to pool_index_plus_1 (git-fixes).\n- stackdepot: respect __GFP_NOLOCKDEP allocation flag (git-fixes).\n- staging: iio: ad9832: Correct phase range check (git-fixes).\n- staging: iio: ad9834: Correct phase range check (git-fixes).\n- staging: media: imx: fix OF node leak in imx_media_add_of_subdevs() (git-fixes).\n- staging: media: max96712: fix kernel oops when removing module (git-fixes).\n- sunrpc: clear XPRT_SOCK_UPD_TIMEOUT when reset transport (git-fixes).\n- sunrpc: fix one UAF issue caused by sunrpc kernel tcp socket (git-fixes).\n- sunrpc: handle -ENOTCONN in xs_tcp_setup_socket() (git-fixes).\n- supported.conf: Add support for v4l2-dv-timings (jsc#PED-8645)\n- svcrdma: Address an integer overflow (git-fixes).\n- svcrdma: fix miss destroy percpu_counter in svc_rdma_proc_init() (git-fixes).\n- swiotlb: Enforce page alignment in swiotlb_alloc() (git-fixes).\n- swiotlb: Reinstate page-alignment for mappings \u003e= PAGE_SIZE (git-fixes).\n- thermal/drivers/qcom/tsens-v1: Add support for MSM8937 tsens (stable-fixes).\n- thermal: of: fix OF node leak in of_thermal_zone_find() (git-fixes).\n- thunderbolt: Add support for Intel Lunar Lake (stable-fixes).\n- thunderbolt: Add support for Intel Panther Lake-M/P (stable-fixes).\n- tipc: fix NULL deref in cleanup_bearer() (bsc#1235433).\n- tools: Sync if_xdp.h uapi tooling header (git-fixes).\n- tools: hv: change permissions of NetworkManager configuration file (git-fixes).\n- tpm/eventlog: Limit memory allocations for event logs with excessive size (bsc#1233260 bsc#1233259 bsc#1232421).\n- tpm: Map the ACPI provided event log (bsc#1233260 bsc#1233259 bsc#1232421).\n- tpm_tis_spi: Release chip select when flow control fails (bsc#1234338)\n- tty: serial: 8250: Fix another runtime PM usage counter underflow (git-fixes).\n- tty: serial: kgdboc: Fix 8250_* kgdb over serial (git-fixes).\n- types: Introduce [us]128 (bsc#1220773).\n- ubifs: Correct the total block count by deducting journal reservation (git-fixes).\n- ubifs: authentication: Fix use-after-free in ubifs_tnc_end_commit (git-fixes).\n- ubifs: skip dumping tnc tree when zroot is null (git-fixes).\n- udf: Fix lock ordering in udf_evict_inode() (bsc#1234238).\n- udf: fix uninit-value use in udf_get_fileshortad (bsc#1234243).\n- udf: prevent integer overflow in udf_bitmap_free_blocks() (bsc#1234239).\n- udf: refactor inode_bmap() to handle error (bsc#1234242).\n- udf: refactor udf_current_aext() to handle error (bsc#1234240).\n- udf: refactor udf_next_aext() to handle error (bsc#1234241).\n- udf: udftime: prevent overflow in udf_disk_stamp_to_time() (bsc#1234237).\n- uio: Fix return value of poll (git-fixes).\n- uio: uio_dmem_genirq: check the return value of devm_kasprintf() (git-fixes).\n- usb-storage: Add max sectors quirk for Nokia 208 (stable-fixes).\n- usb: add support for new USB device ID 0x17EF:0x3098 for the r8152 driver (stable-fixes).\n- usb: cdns3-ti: Add workaround for Errata i2409 (stable-fixes).\n- usb: cdns3: Add quirk flag to enable suspend residency (stable-fixes).\n- usb: chipidea: add CI_HDRC_FORCE_VBUS_ACTIVE_ALWAYS flag (stable-fixes).\n- usb: chipidea: udc: handle USB Error Interrupt if IOC not set (stable-fixes).\n- usb: dwc2: Fix HCD port connection race (git-fixes).\n- usb: dwc2: Fix HCD resume (git-fixes).\n- usb: dwc2: gadget: Do not write invalid mapped sg entries into dma_desc with iommu enabled (stable-fixes).\n- usb: dwc2: hcd: Fix GetPortStatus \u0026 SetPortFeature (git-fixes).\n- usb: dwc3-am62: Disable autosuspend during remove (git-fixes).\n- usb: dwc3-am62: Fix an OF node leak in phy_syscon_pll_refclk() (git-fixes).\n- usb: dwc3: ep0: Do not clear ep0 DWC3_EP_TRANSFER_STARTED (git-fixes).\n- usb: dwc3: ep0: Do not reset resource alloc flag (git-fixes).\n- usb: dwc3: ep0: Do not reset resource alloc flag (including ep0) (git-fixes).\n- usb: dwc3: gadget: Rewrite endpoint allocation flow (stable-fixes).\n- usb: dwc3: gadget: fix writing NYET threshold (git-fixes).\n- usb: dwc3: xilinx: make sure pipe clock is deselected in usb2 only mode (git-fixes).\n- usb: ehci-hcd: fix call balance of clocks handling routines (git-fixes).\n- usb: fix reference leak in usb_new_device() (git-fixes).\n- usb: gadget: configfs: Ignore trailing LF for user strings to cdev (git-fixes).\n- usb: gadget: f_fs: Remove WARN_ON in functionfs_bind (git-fixes).\n- usb: gadget: f_tcm: Decrement command ref count on cleanup (git-fixes).\n- usb: gadget: f_tcm: Do not free command immediately (git-fixes).\n- usb: gadget: f_tcm: Do not prepare BOT write request twice (git-fixes).\n- usb: gadget: f_tcm: Fix Get/SetInterface return value (git-fixes).\n- usb: gadget: f_tcm: Translate error to sense (git-fixes).\n- usb: gadget: f_tcm: ep_autoconfig with fullspeed endpoint (git-fixes).\n- usb: gadget: f_uac2: Fix incorrect setting of bNumEndpoints (git-fixes).\n- usb: gadget: u_serial: Disable ep before setting port to null to fix the crash caused by port being null (git-fixes).\n- usb: gadget: u_serial: Fix the issue that gs_start_io crashed due to accessing null pointer (git-fixes).\n- usb: host: max3421-hcd: Correctly abort a USB request (git-fixes).\n- usb: host: xhci-plat: Assign shared_hcd-\u003ersrc_start (git-fixes).\n- usb: typec: anx7411: fix OF node reference leaks in anx7411_typec_switch_probe() (git-fixes).\n- usb: typec: anx7411: fix fwnode_handle reference leak (git-fixes).\n- usb: typec: fix pm usage counter imbalance in ucsi_ccg_sync_control() (bsc#1235001)\n- usb: typec: tcpm/tcpci_maxim: fix error code in max_contaminant_read_resistance_kohm() (git-fixes).\n- usb: typec: tcpm: set SRC_SEND_CAPABILITIES timeout to PD_T_SENDER_RESPONSE (git-fixes).\n- usb: typec: use cleanup facility for 'altmodes_node' (stable-fixes).\n- usbnet: ipheth: break up NCM header size computation (git-fixes).\n- usbnet: ipheth: check that DPE points past NCM header (git-fixes).\n- usbnet: ipheth: fix DPE OoB read (git-fixes).\n- usbnet: ipheth: fix possible overflow in DPE length check (git-fixes).\n- usbnet: ipheth: refactor NCM datagram loop (git-fixes).\n- usbnet: ipheth: use static NDP16 location in URB (git-fixes).\n- vDPA/ifcvf: Fix pci_read_config_byte() return code handling (git-fixes).\n- vdpa/mlx5: Fix PA offset with unaligned starting iotlb map (git-fixes).\n- vdpa/mlx5: Fix suboptimal range on iotlb iteration (git-fixes).\n- vdpa: solidrun: Fix UB bug with devres (git-fixes).\n- vfs: fix readahead(2) on block devices (bsc#1234201).\n- vmscan,migrate: fix page count imbalance on node stats when demoting pages (git-fixes).\n- watchdog: rzg2l_wdt: Power on the watchdog domain in the restart handler (stable-fixes).\n- watchdog: rzg2l_wdt: Rely on the reset driver for doing proper reset (stable-fixes).\n- watchdog: rzg2l_wdt: Remove reset de-assert from probe (stable-fixes).\n- wifi: ath11k: Fix unexpected return buffer manager error for WCN6750/WCN6855 (git-fixes).\n- wifi: ath11k: cleanup struct ath11k_mon_data (git-fixes).\n- wifi: ath12k: fix atomic calls in ath12k_mac_op_set_bitrate_mask() (stable-fixes).\n- wifi: ath12k: fix tx power, max reg power update to firmware (git-fixes).\n- wifi: ath5k: add PCI ID for Arcadyan devices (git-fixes).\n- wifi: ath5k: add PCI ID for SX76X (git-fixes).\n- wifi: brcmfmac: Fix oops due to NULL pointer dereference in brcmf_sdiod_sglist_rw() (stable-fixes).\n- wifi: brcmfmac: add missing header include for brcmf_dbg (git-fixes).\n- wifi: cfg80211: adjust allocation of colocated AP data (git-fixes).\n- wifi: cfg80211: sme: init n_channels before channels[] access (git-fixes).\n- wifi: cw1200: Fix potential NULL dereference (git-fixes).\n- wifi: ipw2x00: libipw_rx_any(): fix bad alignment (stable-fixes).\n- wifi: iwlwifi: fw: read STEP table from correct UEFI var (git-fixes).\n- wifi: iwlwifi: mvm: Use the sync timepoint API in suspend (stable-fixes).\n- wifi: mac80211: Add non-atomic station iterator (stable-fixes).\n- wifi: mac80211: Fix common size calculation for ML element (git-fixes).\n- wifi: mac80211: clean up 'ret' in sta_link_apply_parameters() (stable-fixes).\n- wifi: mac80211: do not flush non-uploaded STAs (git-fixes).\n- wifi: mac80211: export ieee80211_purge_tx_queue() for drivers (stable-fixes).\n- wifi: mac80211: fix mbss changed flags corruption on 32 bit systems (stable-fixes).\n- wifi: mac80211: fix station NSS capability initialization order (git-fixes).\n- wifi: mac80211: fix tid removal during mesh forwarding (git-fixes).\n- wifi: mac80211: init cnt before accessing elem in ieee80211_copy_mbssid_beacon (git-fixes).\n- wifi: mac80211: prohibit deactivating all links (git-fixes).\n- wifi: mac80211: wake the queues in case of failure in resume (stable-fixes).\n- wifi: mt76: mt76u_vendor_request: Do not print error messages when -EPROTO (git-fixes).\n- wifi: mt76: mt7915: Fix mesh scan on MT7916 DBDC (git-fixes).\n- wifi: mt76: mt7915: add module param to select 5 GHz or 6 GHz on MT7916 (git-fixes).\n- wifi: mt76: mt7915: firmware restart on devices with a second pcie link (git-fixes).\n- wifi: mt76: mt7915: fix overflows seen when writing limit attributes (git-fixes).\n- wifi: mt76: mt7915: fix register mapping (git-fixes).\n- wifi: mt76: mt7921: fix using incorrect group cipher after disconnection (git-fixes).\n- wifi: mt76: mt7925: fix off by one in mt7925_load_clc() (git-fixes).\n- wifi: mt76: mt7996: add max mpdu len capability (git-fixes).\n- wifi: mt76: mt7996: fix HE Phy capability (git-fixes).\n- wifi: mt76: mt7996: fix definition of tx descriptor (git-fixes).\n- wifi: mt76: mt7996: fix incorrect indexing of MIB FW event (git-fixes).\n- wifi: mt76: mt7996: fix ldpc setting (git-fixes).\n- wifi: mt76: mt7996: fix overflows seen when writing limit attributes (git-fixes).\n- wifi: mt76: mt7996: fix register mapping (git-fixes).\n- wifi: mt76: mt7996: fix rx filter setting for bfee functionality (git-fixes).\n- wifi: mt76: mt7996: fix the capability of reception of EHT MU PPDU (git-fixes).\n- wifi: nl80211: fix NL80211_ATTR_MLO_LINK_ID off-by-one (git-fixes).\n- wifi: rtlwifi: Drastically reduce the attempts to read efuse in case of failures (stable-fixes).\n- wifi: rtlwifi: destroy workqueue at rtl_deinit_core (git-fixes).\n- wifi: rtlwifi: do not complete firmware loading needlessly (git-fixes).\n- wifi: rtlwifi: fix init_sw_vars leak when probe fails (git-fixes).\n- wifi: rtlwifi: fix memory leaks and invalid access at probe error path (git-fixes).\n- wifi: rtlwifi: pci: wait for firmware loading before releasing memory (git-fixes).\n- wifi: rtlwifi: remove unused check_buddy_priv (git-fixes).\n- wifi: rtlwifi: rtl8192se: rise completion of firmware loading as last step (git-fixes).\n- wifi: rtlwifi: rtl8821ae: Fix media status report (git-fixes).\n- wifi: rtlwifi: rtl8821ae: phy: restore removed code to fix infinite loop (git-fixes).\n- wifi: rtlwifi: usb: fix workqueue leak when probe fails (git-fixes).\n- wifi: rtlwifi: wait for firmware loading before releasing memory (git-fixes).\n- wifi: rtw88: use ieee80211_purge_tx_queue() to purge TX skb (stable-fixes).\n- wifi: rtw89: check return value of ieee80211_probereq_get() for RNR (stable-fixes).\n- wifi: rtw89: mcc: consider time limits not divisible by 1024 (git-fixes).\n- wifi: wcn36xx: fix channel survey memory allocation size (git-fixes).\n- wifi: wlcore: fix unbalanced pm_runtime calls (git-fixes).\n- workqueue: Add rcu lock check at the end of work item execution (bsc#1236732).\n- workqueue: Do not warn when cancelling WQ_MEM_RECLAIM work from !WQ_MEM_RECLAIM worker (bsc#1235416).\n- writeback, cgroup: switch inodes with dirty timestamps to release dying cgwbs (bsc#1234203).\n- x86,amd_iommu: Replace cmpxchg_double() (bsc#1220773).\n- x86,intel_iommu: Replace cmpxchg_double() (bsc#1220773).\n- x86/hyperv: Fix hv tsc page based sched_clock for hibernation (git-fixes).\n- x86/static-call: Remove early_boot_irqs_disabled check to fix Xen PVH dom0 (git-fixes).\n- xfs: Add error handling for xfs_reflink_cancel_cow_range (git-fixes).\n- xfs: Propagate errors from xfs_reflink_cancel_cow_range in xfs_dax_write_iomap_end (git-fixes).\n- xfs: do not allocate COW extents when unsharing a hole (git-fixes).\n- xfs: fix sb_spino_align checks for large fsblock sizes (git-fixes).\n- xfs: remove unknown compat feature check in superblock write validation (git-fixes).\n- xfs: return from xfs_symlink_verify early on V4 filesystems (git-fixes).\n- xfs: sb_spino_align is not verified (git-fixes).\n- xhci: Add usb cold attach (CAS) as a reason to resume root hub (git-fixes).\n- xhci: Allow RPM on the USB controller (1022:43f7) by default (stable-fixes).\n- xhci: fix possible null pointer deref during xhci urb enqueue (git-fixes).\n","status":"published","published":"2025-03-27T15:23:42Z","modified":"2026-03-23T04:50:43.221938Z","updated_at":"2026-11-02T15:53:59.381172Z"},{"id":"SUSE-SU-2025:20166-1","title":"Security update for the Linux Kernel","description":"\n\nThe SUSE Linux Enterprise Micro 6.0 and 6.1 RT kernel was updated to receive various security bugfixes.\n\nThe following security bugs were fixed:\n\n- CVE-2024-26924: scsi: lpfc: Release hbalock before calling lpfc_worker_wake_up() (bsc#1225820).\n- CVE-2024-27397: netfilter: nf_tables: use timestamp to check for set element timeout (bsc#1224095).\n- CVE-2024-35839: kABI fix for netfilter: bridge: replace physindev with physinif in nf_bridge_info (bsc#1224726).\n- CVE-2024-41042: Prefer nft_chain_validate (bsc#1228526).\n- CVE-2024-44934: net: bridge: mcast: wait for previous gc cycles when removing port (bsc#1229809).\n- CVE-2024-44996: vsock: fix recursive -\u003erecvmsg calls (bsc#1230205).\n- CVE-2024-45828: i3c: mipi-i3c-hci: Mask ring interrupts before ring stop request (bsc#1235705).\n- CVE-2024-47678: icmp: change the order of rate limits (bsc#1231854).\n- CVE-2024-48881: bcache: revert replacing IS_ERR_OR_NULL with IS_ERR again (bsc#1235727).\n- CVE-2024-49948: net: add more sanity checks to qdisc_pkt_len_init() (bsc#1232161).\n- CVE-2024-49951: Bluetooth: MGMT: Fix possible crash on mgmt_index_removed (bsc#1232158).\n- CVE-2024-49978: gso: fix udp gso fraglist segmentation after pull from frag_list (bsc#1232101).\n- CVE-2024-49998: net: dsa: improve shutdown sequence (bsc#1232087).\n- CVE-2024-50018: net: napi: Prevent overflow of napi_defer_hard_irqs (bsc#1232419).\n- CVE-2024-50039: kABI: Restore deleted EXPORT_SYMBOL(__qdisc_calculate_pkt_len) (bsc#1231909).\n- CVE-2024-50143: udf: fix uninit-value use in udf_get_fileshortad (bsc#1233038).\n- CVE-2024-50151: smb: client: fix OOBs when building SMB2_IOCTL request (bsc#1233055).\n- CVE-2024-50199: mm/swapfile: skip HugeTLB pages for unuse_vma (bsc#1233112).\n- CVE-2024-50202: nilfs2: propagate directory read errors from nilfs_find_entry() (bsc#1233324).\n- CVE-2024-50256: netfilter: nf_reject_ipv6: fix potential crash in nf_send_reset6() (bsc#1233200).\n- CVE-2024-50262: bpf: Fix out-of-bounds write in trie_get_next_key() (bsc#1233239).\n- CVE-2024-50278, CVE-2024-50280: dm cache: fix flushing uninitialized delayed_work on cache_ctr error (bsc#1233467 bsc#1233469).\n- CVE-2024-50278: dm cache: fix potential out-of-bounds access on the first resume (bsc#1233467).\n- CVE-2024-50299: sctp: properly validate chunk size in sctp_sf_ootb() (bsc#1233488).\n- CVE-2024-53050: drm/i915/hdcp: Add encoder check in hdcp2_get_capability (bsc#1233546).\n- CVE-2024-53064: idpf: fix idpf_vc_core_init error path (bsc#1233558 bsc#1234464).\n- CVE-2024-53090: afs: Fix lock recursion (bsc#1233637).\n- CVE-2024-53091: bpf: Add sk_is_inet and IS_ICSK check in tls_sw_has_ctx_tx/rx (bsc#1233638).\n- CVE-2024-53099: bpf: Check validity of link-\u003etype in bpf_link_show_fdinfo() (bsc#1233772).\n- CVE-2024-53105: mm: page_alloc: move mlocked flag clearance into free_pages_prepare() (bsc#1234069).\n- CVE-2024-53111: mm/mremap: fix address wraparound in move_page_tables() (bsc#1234086).\n- CVE-2024-53113: mm: fix NULL pointer dereference in alloc_pages_bulk_noprof (bsc#1234077).\n- CVE-2024-53117: virtio/vsock: Improve MSG_ZEROCOPY error handling (bsc#1234079).\n- CVE-2024-53118: vsock: Fix sk_error_queue memory leak (bsc#1234071).\n- CVE-2024-53119: virtio/vsock: Fix accept_queue memory leak (bsc#1234073).\n- CVE-2024-53122: mptcp: cope racing subflow creation in mptcp_rcv_space_adjust (bsc#1234076).\n- CVE-2024-53125: bpf: sync_linked_regs() must preserve subreg_def (bsc#1234156).\n- CVE-2024-53130: nilfs2: fix null-ptr-deref in block_dirty_buffer tracepoint (bsc#1234219).\n- CVE-2024-53131: nilfs2: fix null-ptr-deref in block_touch_buffer tracepoint (bsc#1234220).\n- CVE-2024-53133: drm/amd/display: Handle dml allocation failure to avoid crash (bsc#1234221)\n- CVE-2024-53134: pmdomain: imx93-blk-ctrl: correct remove path (bsc#1234159).\n- CVE-2024-53141: netfilter: ipset: add missing range check in bitmap_ip_uadt (bsc#1234381).\n- CVE-2024-53160: rcu/kvfree: Fix data-race in __mod_timer / kvfree_call_rcu (bsc#1234810).\n- CVE-2024-53161: EDAC/bluefield: Fix potential integer overflow (bsc#1234856).\n- CVE-2024-53164: net: sched: fix ordering of qlen adjustment (bsc#1234863).\n- CVE-2024-53170: block: fix uaf for flush rq while iterating tags (bsc#1234888).\n- CVE-2024-53172: ubi: fastmap: Fix duplicate slab cache names while attaching (bsc#1234898).\n- CVE-2024-53175: ipc: fix memleak if msg_init_ns failed in create_ipc_ns (bsc#1234893).\n- CVE-2024-53179: smb: client: fix use-after-free of signing key (bsc#1234921).\n- CVE-2024-53185: smb: client: fix NULL ptr deref in crypto_aead_setkey() (bsc#1234901).\n- CVE-2024-53187: io_uring: check for overflows in io_pin_pages (bsc#1234947).\n- CVE-2024-53195: KVM: arm64: Get rid of userspace_irqchip_in_use (bsc#1234957).\n- CVE-2024-53196: KVM: arm64: Do not retire aborted MMIO instruction (bsc#1234906).\n- CVE-2024-53198: xen: Fix the issue of resource not being properly released in xenbus_dev_probe() (bsc#1234923).\n- CVE-2024-53203: usb: typec: fix potential array underflow in ucsi_ccg_sync_control() (bsc#1235001).\n- CVE-2024-53214: vfio/pci: Properly hide first-in-list PCIe extended capability (bsc#1235004).\n- CVE-2024-53216: nfsd: fix UAF when access ex_uuid or ex_stats (bsc#1235003).\n- CVE-2024-53222: zram: fix NULL pointer in comp_algorithm_show() (bsc#1234974).\n- CVE-2024-53227: scsi: bfa: Fix use-after-free in bfad_im_module_exit() (bsc#1235011).\n- CVE-2024-53232: iommu/s390: Implement blocking domain (bsc#1235050).\n- CVE-2024-53234: erofs: handle NONHEAD !delta[1] lclusters gracefully (bsc#1235045).\n- CVE-2024-53236: xsk: Free skb when TX metadata options are invalid (bsc#1235000).\n- CVE-2024-53240: xen/netfront: fix crash when removing device (bsc#1234281).\n- CVE-2024-53241: x86/xen: use new hypercall functions instead of hypercall page (XSA-466 bsc#1234282).\n- CVE-2024-53685: ceph: give up on paths longer than PATH_MAX (bsc#1235720).\n- CVE-2024-55639: net: renesas: rswitch: avoid use-after-put for a device tree node (bsc#1235737).\n- CVE-2024-55881: KVM: x86: Play nice with protected guests in complete_hypercall_exit() (bsc#1235745).\n- CVE-2024-56372: net: tun: fix tun_napi_alloc_frags() (bsc#1235753).\n- CVE-2024-56549: cachefiles: Fix NULL pointer dereference in object-\u003efile (bsc#1234912).\n- CVE-2024-56566: mm/slub: Avoid list corruption when removing a slab from the full list (bsc#1235033).\n- CVE-2024-56568: iommu/arm-smmu: Defer probe of clients after smmu device bound (bsc#1235032).\n- CVE-2024-56569: ftrace: Fix regression with module command in stack_trace_filter (bsc#1235031).\n- CVE-2024-56570: ovl: Filter invalid inodes with missing lookup function (bsc#1235035).\n- CVE-2024-56582: btrfs: fix use-after-free in btrfs_encoded_read_endio() (bsc#1235128).\n- CVE-2024-56588: scsi: hisi_sas: Create all dump files during debugfs initialization (bsc#1235123).\n- CVE-2024-56589: scsi: hisi_sas: Add cond_resched() for no forced preemption model (bsc#1235241).\n- CVE-2024-56599: wifi: ath10k: avoid NULL pointer error during sdio remove (bsc#1235138).\n- CVE-2024-56600: net: inet6: do not leave a dangling sk pointer in inet6_create() (bsc#1235217).\n- CVE-2024-56601: net: inet: do not leave a dangling sk pointer in inet_create() (bsc#1235230).\n- CVE-2024-56602: net: ieee802154: do not leave a dangling sk pointer in ieee802154_create() (bsc#1235521).\n- CVE-2024-56603: net: af_can: do not leave a dangling sk pointer in can_create() (bsc#1235415).\n- CVE-2024-56604: Bluetooth: RFCOMM: avoid leaving dangling sk pointer in rfcomm_sock_alloc() (bsc#1235056).\n- CVE-2024-56608: drm/amd/display: Fix out-of-bounds access in 'dcn21_link_encoder_create' (bsc#1235487).\n- CVE-2024-56610: kcsan: Turn report_filterlist_lock into a raw_spinlock (bsc#1235390).\n- CVE-2024-56611: mm/mempolicy: fix migrate_to_node() assuming there is at least one VMA in a MM (bsc#1235391).\n- CVE-2024-56614: xsk: fix OOB map writes when deleting elements (bsc#1235424).\n- CVE-2024-56615: bpf: fix OOB devmap writes when deleting elements (bsc#1235426).\n- CVE-2024-56617: cacheinfo: Allocate memory during CPU hotplug if not done from the primary CPU (bsc#1235429).\n- CVE-2024-56620: scsi: ufs: qcom: Only free platform MSIs when ESI is enabled (bsc#1235227).\n- CVE-2024-56622: scsi: ufs: core: sysfs: Prevent div by zero (bsc#1235251).\n- CVE-2024-56631: scsi: sg: Fix slab-use-after-free read in sg_release() (bsc#1235480).\n- CVE-2024-56635: net: avoid potential UAF in default_operstate() (bsc#1235519).\n- CVE-2024-56636: geneve: do not assume mac header is set in geneve_xmit_skb() (bsc#1235520).\n- CVE-2024-56637: netfilter: ipset: Hold module reference while requesting a module (bsc#1235523).\n- CVE-2024-56641: net/smc: initialize close_work early to avoid warning (bsc#1235526).\n- CVE-2024-56643: dccp: Fix memory leak in dccp_feat_change_recv (bsc#1235132).\n- CVE-2024-56648: net: hsr: avoid potential out-of-bound access in fill_frame_info() (bsc#1235451).\n- CVE-2024-56649: net: enetc: Do not configure preemptible TCs if SIs do not support (bsc#1235449).\n- CVE-2024-56650: netfilter: x_tables: fix LED ID check in led_tg_check() (bsc#1235430).\n- CVE-2024-56656: bnxt_en: Fix aggregation ID mask to prevent oops on 5760X chips (bsc#1235444).\n- CVE-2024-56659: net: lapb: increase LAPB_HEADER_LEN (bsc#1235439).\n- CVE-2024-56660: net/mlx5: DR, prevent potential error pointer dereference (bsc#1235437).\n- CVE-2024-56664: bpf, sockmap: Fix race between element replace and close() (bsc#1235249).\n- CVE-2024-56665: bpf,perf: Fix invalid prog_array access in perf_event_detach_bpf_prog (bsc#1235489).\n- CVE-2024-56675: bpf: Fix UAF via mismatching bpf_prog/attachment RCU flavors (bsc#1235555).\n- CVE-2024-56679: octeontx2-pf: handle otx2_mbox_get_rsp errors in otx2_common.c (bsc#1235498).\n- CVE-2024-56693: brd: defer automatic disk creation until module initialization succeeds (bsc#1235418).\n- CVE-2024-56694: bpf: fix recursive lock when verdict program return SK_PASS (bsc#1235412).\n- CVE-2024-56704: 9p/xen: fix release of IRQ (bsc#1235584).\n- CVE-2024-56707: octeontx2-pf: handle otx2_mbox_get_rsp errors in otx2_dmac_flt.c (bsc#1235545).\n- CVE-2024-56708: EDAC/igen6: Avoid segmentation fault on module unload (bsc#1235564).\n- CVE-2024-56712: udmabuf: fix memory leak on last export_udmabuf() error path (bsc#1235565).\n- CVE-2024-56715: ionic: Fix netdev notifier unregister on failure (bsc#1235612).\n- CVE-2024-56716: netdevsim: prevent bad user input in nsim_dev_health_break_write() (bsc#1235587).\n- CVE-2024-56725: octeontx2-pf: handle otx2_mbox_get_rsp errors in otx2_dcbnl.c (bsc#1235578).\n- CVE-2024-56726: octeontx2-pf: handle otx2_mbox_get_rsp errors in cn10k.c (bsc#1235582).\n- CVE-2024-56727: octeontx2-pf: handle otx2_mbox_get_rsp errors in otx2_flows.c (bsc#1235583).\n- CVE-2024-56728: octeontx2-pf: handle otx2_mbox_get_rsp errors in otx2_ethtool.c (bsc#1235656).\n- CVE-2024-56729: smb: Initialize cfid-\u003etcon before performing network ops (bsc#1235503).\n- CVE-2024-56747: scsi: qedi: Fix a possible memory leak in qedi_alloc_and_init_sb() (bsc#1234934).\n- CVE-2024-56748: scsi: qedf: Fix a possible memory leak in qedf_alloc_and_init_sb() (bsc#1235627).\n- CVE-2024-56755: netfs/fscache: Add a memory barrier for FSCACHE_VOLUME_CREATING (bsc#1234920).\n- CVE-2024-56759: btrfs: fix use-after-free when COWing tree bock and tracing is enabled (bsc#1235645).\n- CVE-2024-56763: tracing: Prevent bad count for tracing_cpumask_write (bsc#1235638).\n- CVE-2024-56774: btrfs: add a sanity check for btrfs root in btrfs_search_slot() (bsc#1235653).\n- CVE-2024-56775: drm/amd/display: Fix handling of plane refcount (bsc#1235657).\n- CVE-2024-57791: net/smc: check return value of sock_recvmsg when draining clc data (bsc#1235759).\n- CVE-2024-57793: virt: tdx-guest: Just leak decrypted memory on unrecoverable errors (bsc#1235768).\n- CVE-2024-57795: RDMA/rxe: Remove the direct link to net_device (bsc#1235906).\n- CVE-2024-57801: net/mlx5e: Skip restore TC rules for vport rep without loaded flag (bsc#1235940).\n- CVE-2024-57802: netrom: check buffer length before accessing it (bsc#1235941).\n- CVE-2024-57804: scsi: mpi3mr: Fix corrupt config pages PHY state is switched in sysfs (bsc#1235779).\n- CVE-2024-57809: PCI: imx6: Fix suspend/resume support on i.MX6QDL (bsc#1235793).\n- CVE-2024-57838: s390/entry: Mark IRQ entries to fix stack depot warnings (bsc#1235798).\n- CVE-2024-57857: RDMA/siw: Remove direct link to net_device (bsc#1235946).\n- CVE-2024-57884: mm: vmscan: account for free pages to prevent infinite Loop in throttle_direct_reclaim() (bsc#1235948).\n- CVE-2024-57892: ocfs2: fix slab-use-after-free due to dangling pointer dqi_priv (bsc#1235964).\n- CVE-2024-57896: btrfs: flush delalloc workers queue before stopping cleaner kthread during unmount (bsc#1235965).\n- CVE-2024-57903: net: restrict SO_REUSEPORT to inet sockets (bsc#1235967).\n- CVE-2024-57917: topology: Keep the cpumask unchanged when printing cpumap (bsc#1236127).\n- CVE-2024-57929: dm array: fix releasing a faulty array block twice in dm_array_cursor_end (bsc#1236096).\n- CVE-2024-57931: selinux: ignore unknown extended permissions (bsc#1236192).\n- CVE-2024-57932: gve: guard XDP xmit NDO on existence of xdp queues (bsc#1236190).\n- CVE-2024-57933: gve: guard XSK operations on the existence of queues (bsc#1236178).\n- CVE-2024-57938: net/sctp: Prevent autoclose integer overflow in sctp_association_init() (bsc#1236182).\n- CVE-2024-57946: virtio-blk: do not keep queue frozen during system suspend (bsc#1236247).\n- CVE-2025-21632: x86/fpu: Ensure shadow stack is active before \"getting\" registers (bsc#1236106).\n- CVE-2025-21649: net: hns3: fix kernel crash when 1588 is sent on HIP08 devices (bsc#1236143).\n- CVE-2025-21650: net: hns3: fixed hclge_fetch_pf_reg accesses bar space out of bounds issue (bsc#1236144).\n- CVE-2025-21651: net: hns3: do not auto enable misc vector (bsc#1236145).\n- CVE-2025-21652: ipvlan: Fix use-after-free in ipvlan_get_iflink() (bsc#1236160).\n- CVE-2025-21653: net_sched: cls_flow: validate TCA_FLOW_RSHIFT attribute (bsc#1236161).\n- CVE-2025-21655: io_uring/eventfd: ensure io_eventfd_signal() defers another RCU period (bsc#1236163).\n- CVE-2025-21662: net/mlx5: Fix variable not being completed when function returns (bsc#1236198).\n- CVE-2025-21663: net: stmmac: dwmac-tegra: Read iommu stream id from device tree (bsc#1236260).\n- CVE-2025-21664: dm thin: make get_first_thin use rcu-safe list first function (bsc#1236262).\n- CVE-2025-21674: net/mlx5e: Fix inversion dependency warning while enabling IPsec tunnel (bsc#1236688).\n- CVE-2025-21676: net: fec: handle page_pool_dev_alloc_pages error (bsc#1236696).\n- CVE-2025-21682: eth: bnxt: always recalculate features after XDP clearing, fix null-deref (bsc#1236703).\n\nFeatures added:\n\n  * - Disable ceph (jsc#PED-7242)\n  * - RAS/AMD/ATL: Translate normalized to system physical addresses using PRM (jsc#PED-10467).\n  * - ACPI: PRM: Add PRM handler direct call support (jsc#PED-10467).\n  * - supported.conf: Add support for v4l2-dv-timings  (jsc#PED-8645)\n\n\nThe following non-security bugs were fixed:\n\n- 9p: v9fs_fid_find: also lookup by inode if not found dentry (git-fixes).\n- ACPI/HMAT: Move HMAT messages to pr_debug() (bsc#1234294)\n- ACPI/IORT: Add PMCG platform information for HiSilicon HIP09A (stable-fixes).\n- ACPI/IORT: Add PMCG platform information for HiSilicon HIP10/11 (stable-fixes).\n- ACPI: PCC: Add PCC shared memory region command and status bitfields (stable-fixes).\n- ACPI: PRM: Add PRM handler direct call support (jsc#PED-10467).\n- ACPI: fan: cleanup resources in the error path of .probe() (git-fixes).\n- ACPI: resource: Add Asus Vivobook X1504VAP to irq1_level_low_skip_override[] (stable-fixes).\n- ACPI: resource: Add TongFang GM5HG0A to irq1_edge_low_force_override[] (stable-fixes).\n- ACPI: resource: Fix memory resource type union access (git-fixes).\n- ACPI: resource: acpi_dev_irq_override(): Check DMI match last (stable-fixes).\n- ACPI: x86: Add skip i2c clients quirk for Acer Iconia One 8 A1-840 (stable-fixes).\n- ACPI: x86: Clean up Asus entries in acpi_quirk_skip_dmi_ids[] (stable-fixes).\n- ACPI: x86: Make UART skip quirks work on PCI UARTs without an UID (stable-fixes).\n- ACPICA: events/evxfregn: do not release the ContextMutex that was never acquired (git-fixes).\n- ALSA hda/realtek: Add quirk for Framework F111:000C (stable-fixes).\n- ALSA: hda/hdmi: Yet more pin fix for HP EliteDesk 800 G4 (stable-fixes).\n- ALSA: hda/realtek - Add support for ASUS Zen AIO 27 Z272SD_A272SD audio (stable-fixes).\n- ALSA: hda/realtek - Fixed headphone distorted sound on Acer Aspire A115-31 laptop (git-fixes).\n- ALSA: hda/realtek: Add Framework Laptop 13 (Intel Core Ultra) to quirks (stable-fixes).\n- ALSA: hda/realtek: Add new alc2xx-fixup-headset-mic model (stable-fixes).\n- ALSA: hda/realtek: Add support for Ayaneo System using CS35L41 HDA (stable-fixes).\n- ALSA: hda/realtek: Add support for Galaxy Book2 Pro (NP950XEE) (stable-fixes).\n- ALSA: hda/realtek: Enable Mute LED on HP Laptop 14s-fq1xxx (stable-fixes).\n- ALSA: hda/realtek: Enable headset mic on Positivo C6400 (stable-fixes).\n- ALSA: hda/realtek: Fix headset mic on Acer Nitro 5 (stable-fixes).\n- ALSA: hda/realtek: Workaround for resume on Dell Venue 11 Pro 7130 (bsc#1235686).\n- ALSA: hda: Add HP MP9 G4 Retail System AMS to force connect list (stable-fixes).\n- ALSA: hda: Fix headset detection failure due to unstable sort (git-fixes).\n- ALSA: line6: Fix racy access to midibuf (stable-fixes).\n- ALSA: seq: Check UMP support for midi_version change (git-fixes).\n- ALSA: seq: oss: Fix races at processing SysEx messages (stable-fixes).\n- ALSA: seq: ump: Fix seq port updates per FB info notify (git-fixes).\n- ALSA: seq: ump: Use automatic cleanup of kfree() (stable-fixes).\n- ALSA: seq: ump: Use guard() for locking (stable-fixes).\n- ALSA: ump: Use guard() for locking (stable-fixes).\n- ALSA: usb-audio: Add delay quirk for USB Audio Device (stable-fixes).\n- ALSA: usb-audio: Add delay quirk for iBasso DC07 Pro (stable-fixes).\n- ALSA: usb-audio: Add implicit feedback quirk for Yamaha THR5 (stable-fixes).\n- ALSA: usb-audio: Notify xrun for low-latency mode (git-fixes).\n- ALSA: usb-audio: Re-add ScratchAmp quirk entries (git-fixes).\n- ALSA: usb-audio: US16x08: Initialize array before use (git-fixes).\n- ASoC: Intel: avs: Fix theoretical infinite loop (git-fixes).\n- ASoC: Intel: sof_sdw: add quirk for Dell SKU 0B8C (stable-fixes).\n- ASoC: Intel: sof_sdw: fix jack detection on ADL-N variant RVP (stable-fixes).\n- ASoC: SOF: Remove libraries from topology lookups (git-fixes).\n- ASoC: acp: Support microphone from Lenovo Go S (stable-fixes).\n- ASoC: amd: yc: Add a quirk for microfone on Lenovo ThinkPad P14s Gen 5 21MES00B00 (stable-fixes).\n- ASoC: amd: yc: Add quirk for microphone on Lenovo Thinkpad T14s Gen 6 21M1CTO1WW (stable-fixes).\n- ASoC: amd: yc: Fix the wrong return value (git-fixes).\n- ASoC: amd: yc: Support mic on HP 14-em0002la (stable-fixes).\n- ASoC: amd: yc: Support mic on Lenovo Thinkpad E14 Gen 6 (stable-fixes).\n- ASoC: amd: yc: fix internal mic on Redmi G 2022 (stable-fixes).\n- ASoC: codecs: wcd938x-sdw: Correct Soundwire ports mask (git-fixes).\n- ASoC: codecs: wsa881x: Correct Soundwire ports mask (git-fixes).\n- ASoC: codecs: wsa883x: Correct Soundwire ports mask (git-fixes).\n- ASoC: codecs: wsa884x: Correct Soundwire ports mask (git-fixes).\n- ASoC: cs35l56: Handle OTP read latency over SoundWire (stable-fixes).\n- ASoC: cs35l56: Patch CS35L56_IRQ1_MASK_18 to the default value (stable-fixes).\n- ASoC: fsl_micfil: Expand the range of FIFO watermark mask (stable-fixes).\n- ASoC: hdmi-codec: reorder channel allocation list (stable-fixes).\n- ASoC: mediatek: disable buffer pre-allocation (stable-fixes).\n- ASoC: meson: axg-fifo: fix irq scheduling issue with PREEMPT_RT (git-fixes).\n- ASoC: nau8822: Lower debug print priority (stable-fixes).\n- ASoC: rockchip: i2s_tdm: Re-add the set_sysclk callback (git-fixes).\n- ASoC: rt722: add delay time to wait for the calibration procedure (stable-fixes).\n- ASoC: samsung: Add missing depends on I2C (git-fixes).\n- ASoC: samsung: Add missing selects for MFD_WM8994 (stable-fixes).\n- ASoC: sun4i-spdif: Add clock multiplier settings (git-fixes).\n- ASoC: wm8994: Add depends on MFD core (stable-fixes).\n- Add already cherry-picked ids to AMDGPU patch\n- Align git commit ID abbreviation guidelines and checks (git-fixes).\n- Bluetooth: Add support ITTIM PE50-M75C (stable-fixes).\n- Bluetooth: Fix type of len in rfcomm_sock_getsockopt{,_old}() (stable-fixes).\n- Bluetooth: ISO: Reassociate a socket with an active BIS (stable-fixes).\n- Bluetooth: L2CAP: accept zero as a special value for MTU auto-selection (git-fixes).\n- Bluetooth: L2CAP: do not leave dangling sk pointer on error in l2cap_sock_create() (stable-fixes).\n- Bluetooth: L2CAP: handle NULL sock pointer in l2cap_sock_alloc (git-fixes).\n- Bluetooth: MGMT: Fix Add Device to responding before completing (git-fixes).\n- Bluetooth: MGMT: Fix possible deadlocks (git-fixes).\n- Bluetooth: SCO: Add support for 16 bits transparent voice setting (git-fixes).\n- Bluetooth: btnxpuart: Fix driver sending truncated data (git-fixes).\n- Bluetooth: btnxpuart: Fix glitches seen in dual A2DP streaming (git-fixes).\n- Bluetooth: btusb: Add RTL8852BE device 0489:e123 to device tables (stable-fixes).\n- Bluetooth: btusb: Add USB HW IDs for MT7921/MT7922/MT7925 (stable-fixes).\n- Bluetooth: btusb: Add new VID/PID 0489/e111 for MT7925 (stable-fixes).\n- Bluetooth: btusb: Add new VID/PID 13d3/3602 for MT7925 (stable-fixes).\n- Bluetooth: btusb: add callback function in btusb suspend/resume (stable-fixes).\n- Bluetooth: btusb: mediatek: add callback function in btusb_disconnect (stable-fixes).\n- Bluetooth: hci_core: Fix not checking skb length on hci_acldata_packet (stable-fixes).\n- Bluetooth: hci_event: Fix using rcu_read_(un)lock while iterating (git-fixes).\n- Bluetooth: hci_sync: Fix not setting Random Address when required (git-fixes).\n- Bluetooth: iso: Fix recursive locking warning (git-fixes).\n- Delete XHCI patch for regression (bsc#1235550)\n- Disable ceph (jsc#PED-7242)\n- Documentation: PM: Clarify pm_runtime_resume_and_get() return value (git-fixes).\n- Drivers: hv: util: Avoid accessing a ringbuffer not initialized yet (git-fixes).\n- Drop downstream TPM fix patch (bsc#1233260 bsc#1233259 bsc#1232421)\n- Drop uvcvideo fix due to regression (bsc#1235894)\n- EDAC/{i10nm,skx,skx_common}: Support UV systems (bsc#1234693).\n- HID: core: Fix assumption that Resolution Multipliers must be in Logical Collections (git-fixes).\n- HID: fix generic desktop D-Pad controls (git-fixes).\n- HID: hid-sensor-hub: do not use stale platform-data on remove (git-fixes).\n- HID: hid-thrustmaster: Fix warning in thrustmaster_probe by adding endpoint check (git-fixes).\n- HID: magicmouse: Apple Magic Trackpad 2 USB-C driver support (stable-fixes).\n- HID: multitouch: fix support for Goodix PID 0x01e9 (git-fixes).\n- Input: atkbd - map F23 key to support default copilot shortcut (stable-fixes).\n- Input: bbnsm_pwrkey - add remove hook (git-fixes).\n- Input: bbnsm_pwrkey - fix missed key press after suspend (git-fixes).\n- Input: davinci-keyscan - remove leftover header (git-fixes).\n- Input: xpad - add QH Electronics VID/PID (stable-fixes).\n- Input: xpad - add support for Nacon Evol-X Xbox One Controller (stable-fixes).\n- Input: xpad - add support for Nacon Pro Compact (stable-fixes).\n- Input: xpad - add support for wooting two he (arm) (stable-fixes).\n- Input: xpad - add unofficial Xbox 360 wireless receiver clone (stable-fixes).\n- Input: xpad - improve name of 8BitDo controller 2dc8:3106 (stable-fixes).\n- KVM: SVM: Allow guest writes to set MSR_AMD64_DE_CFG bits (bsc#1234635).\n- KVM: s390: Reject KVM_SET_GSI_ROUTING on ucontrol VMs (git-fixes bsc#1235776).\n- KVM: s390: Reject setting flic pfault attributes on ucontrol VMs (git-fixes bsc#1235777).\n- KVM: s390: vsie: fix virtual/physical address in unpin_scb() (git-fixes bsc#1235778).\n- Move kABI workaround patch to correct folder\n- Move upstreamed DRM patch into sorted section\n- Move upstreamed NFS patch into sorted section\n- Move upstreamed TPM patch into sorted section\n- Move upstreamed lpfc patches into sorted section\n- Move upstreamed ppc patch into sorted section\n- Move upstreamed sound patch into sorted section\n- Move upstreamed sound patches into sorted section\n- NFC: nci: Add bounds checking in nci_hci_create_pipe() (git-fixes).\n- NFS/pnfs: Fix a live lock between recalled layouts and layoutget (git-fixes).\n- NFSD: Async COPY result needs to return a write verifier (git-fixes).\n- NFSD: Cap the number of bytes copied by nfs4_reset_recoverydir() (git-fixes).\n- NFSD: Fix nfsd4_shutdown_copy() (git-fixes).\n- NFSD: Prevent NULL dereference in nfsd4_process_cb_update() (git-fixes).\n- NFSD: Prevent a potential integer overflow (git-fixes).\n- NFSD: Remove a never-true comparison (git-fixes).\n- NFSD: initialize copy-\u003ecp_clp early in nfsd4_copy for use by trace point (git-fixes).\n- NFSv4.0: Fix a use-after-free problem in the asynchronous open() (git-fixes).\n- NFSv4.2: fix COPY_NOTIFY xdr buf size calculation (git-fixes).\n- NFSv4.2: mark OFFLOAD_CANCEL MOVEABLE (git-fixes).\n- Octeontx2-pf: Free send queue buffers incase of leaf to inner (git-fixes).\n- PCI/AER: Disable AER service on suspend (stable-fixes).\n- PCI/MSI: Handle lack of irqdomain gracefully (git-fixes).\n- PCI: Add 'reset_subordinate' to reset hierarchy below bridge (stable-fixes).\n- PCI: Add ACS quirk for Broadcom BCM5760X NIC (stable-fixes).\n- PCI: Add ACS quirk for Wangxun FF5xxx NICs (stable-fixes).\n- PCI: Add T_PERST_CLK_US macro (git-fixes).\n- PCI: Avoid putting some root ports into D3 on TUXEDO Sirius Gen1 (git-fixes).\n- PCI: Detect and trust built-in Thunderbolt chips (stable-fixes).\n- PCI: Fix use-after-free of slot-\u003ebus on hot remove (stable-fixes).\n- PCI: Use preserve_config in place of pci_flags (stable-fixes).\n- PCI: cadence: Extract link setup sequence from cdns_pcie_host_setup() (stable-fixes).\n- PCI: cadence: Set cdns_pcie_host_init() global (stable-fixes).\n- PCI: cpqphp: Use PCI_POSSIBLE_ERROR() to check config reads (stable-fixes).\n- PCI: dwc: Always stop link in the dw_pcie_suspend_noirq (git-fixes).\n- PCI: dwc: ep: Prevent changing BAR size/flags in pci_epc_set_bar() (git-fixes).\n- PCI: dwc: ep: Write BAR_MASK before iATU registers in pci_epc_set_bar() (git-fixes).\n- PCI: endpoint: Destroy the EPC device in devm_pci_epc_destroy() (git-fixes).\n- PCI: endpoint: Finish virtual EP removal in pci_epf_remove_vepf() (git-fixes).\n- PCI: endpoint: pci-epf-test: Fix check for DMA MEMCPY test (git-fixes).\n- PCI: endpoint: pci-epf-test: Set dma_chan_rx pointer to NULL on error (git-fixes).\n- PCI: imx6: Deassert apps_reset in imx_pcie_deassert_core_reset() (git-fixes).\n- PCI: imx6: Skip controller_id generation logic for i.MX7D (git-fixes).\n- PCI: j721e: Add PCIe 4x lane selection support (stable-fixes).\n- PCI: j721e: Add per platform maximum lane settings (stable-fixes).\n- PCI: j721e: Add reset GPIO to struct j721e_pcie (stable-fixes).\n- PCI: j721e: Add suspend and resume support (git-fixes).\n- PCI: j721e: Use T_PERST_CLK_US macro (git-fixes).\n- PCI: microchip: Set inbound address translation for coherent or non-coherent mode (git-fixes).\n- PCI: qcom: Add support for IPQ9574 (stable-fixes).\n- PCI: rcar-ep: Fix incorrect variable used when calling devm_request_mem_region() (git-fixes).\n- PCI: vmd: Add DID 8086:B06F and 8086:B60B for Intel client SKUs (stable-fixes).\n- PCI: vmd: Set devices to D0 before enabling PM L1 Substates (stable-fixes).\n- PM: hibernate: Add error handling for syscore_suspend() (git-fixes).\n- RAS/AMD/ATL: Translate normalized to system physical addresses using PRM (jsc#PED-10467).\n- RDMA/bnxt_re: Add check for path mtu in modify_qp (git-fixes)\n- RDMA/bnxt_re: Add send queue size check for variable wqe (git-fixes)\n- RDMA/bnxt_re: Avoid initializing the software queue for user queues (git-fixes)\n- RDMA/bnxt_re: Avoid sending the modify QP workaround for latest adapters (git-fixes)\n- RDMA/bnxt_re: Disable use of reserved wqes (git-fixes)\n- RDMA/bnxt_re: Fix MSN table size for variable wqe mode (git-fixes)\n- RDMA/bnxt_re: Fix max SGEs for the Work Request (git-fixes)\n- RDMA/bnxt_re: Fix max_qp_wrs reported (git-fixes)\n- RDMA/bnxt_re: Fix reporting hw_ver in query_device (git-fixes)\n- RDMA/bnxt_re: Fix the check for 9060 condition (git-fixes)\n- RDMA/bnxt_re: Fix the locking while accessing the QP table (git-fixes)\n- RDMA/bnxt_re: Fix the max WQE size for static WQE support (git-fixes)\n- RDMA/bnxt_re: Fix the max WQEs used in Static WQE mode (git-fixes)\n- RDMA/bnxt_re: Fix to drop reference to the mmap entry in case of error (git-fixes)\n- RDMA/bnxt_re: Fix to export port num to ib_query_qp (git-fixes)\n- RDMA/bnxt_re: Remove always true dattr validity check (git-fixes)\n- RDMA/core: Fix ENODEV error for iWARP test over vlan (git-fixes)\n- RDMA/hns: Fix accessing invalid dip_ctx during destroying QP (git-fixes)\n- RDMA/hns: Fix mapping error of zero-hop WQE buffer (git-fixes)\n- RDMA/hns: Fix missing flush CQE for DWQE (git-fixes)\n- RDMA/hns: Fix warning storm caused by invalid input in IO path (git-fixes)\n- RDMA/mlx4: Avoid false error about access to uninitialized gids array (git-fixes)\n- RDMA/mlx5: Enforce same type port association for multiport RoCE (git-fixes)\n- RDMA/mlx5: Fix a race for an ODP MR which leads to CQE with error (git-fixes)\n- RDMA/mlx5: Fix implicit ODP use after free (git-fixes)\n- RDMA/mlx5: Fix indirect mkey ODP page count (git-fixes)\n- RDMA/rtrs: Ensure 'ib_sge list' is accessible (git-fixes)\n- RDMA/rxe: Fix mismatched max_msg_sz (git-fixes)\n- RDMA/rxe: Fix the warning \"__rxe_cleanup+0x12c/0x170 [rdma_rxe]\" (git-fixes)\n- RDMA/srp: Fix error handling in srp_add_port (git-fixes)\n- RDMA/uverbs: Prevent integer overflow issue (git-fixes)\n- README.BRANCH: Remove copy of branch name\n- Refresh patches.suse/ALSA-hda-realtek-Add-support-for-Samsung-Galaxy-Book.patch.\n- Refresh patches.suse/cpufreq-intel_pstate-Temporarily-boost-P-state-when-.patch.\n- Revert \"HID: multitouch: Add support for lenovo Y9000P Touchpad\" (stable-fixes).\n- Revert \"block/mq-deadline: use correct way to throttling write requests\" (bsc#1234146).\n- Revert \"btrfs: fix use-after-free waiting for encoded read endios (bsc#1235128)\"\n- Revert \"drm/i915/dpt: Make DPT object unshrinkable\" (stable-fixes).\n- Revert \"igb: Disable threaded IRQ for igb_msix_other\" (git-fixes).\n- Revert \"mtd: spi-nor: core: replace dummy buswidth from addr to data\" (git-fixes).\n- Revert \"unicode: Do not special case ignorable code points\" (stable-fixes).\n- Revert \"usb: gadget: u_serial: Disable ep before setting port to null to fix the crash caused by port being null\" (stable-fixes).\n- Revert 'arm64: Kconfig: Make SME depend on BROKEN for now' This reverts commit 2ccfee6be929dd4ea49ef59a7ae686473aae40b6 CONFIG_ARM64_SME is enabled by default so some customers may rely on SME. We need further analysis to evaluate to what extent we are impacted and in case we'll disable SME support later.\n- Revert 0dd78566990 (\"Disable ceph (jsc#PED-7242)\") Apparently, jsc#PED-7242 is only deprecate ceph for 15-SP6 and disable for 15-SP7. Revert the disabling.\n- SUNRPC: make sure cache entry active before cache_show (git-fixes).\n- SUNRPC: timeout and cancel TLS handshake with -ETIMEDOUT (git-fixes).\n- USB: core: Disable LPM only for non-suspended ports (git-fixes).\n- USB: serial: cp210x: add Phoenix Contact UPS Device (stable-fixes).\n- USB: serial: option: add MediaTek T7XX compositions (stable-fixes).\n- USB: serial: option: add MeiG Smart SLM770A (stable-fixes).\n- USB: serial: option: add MeiG Smart SRM815 (stable-fixes).\n- USB: serial: option: add Neoway N723-EA support (stable-fixes).\n- USB: serial: option: add Netprisma LCUK54 modules for WWAN Ready (stable-fixes).\n- USB: serial: option: add TCL IK512 MBIM \u0026 ECM (stable-fixes).\n- USB: serial: option: add Telit FE910C04 rmnet compositions (stable-fixes).\n- USB: serial: quatech2: fix null-ptr-deref in qt2_process_read_urb() (git-fixes).\n- USB: usblp: return error when setting unsupported protocol (git-fixes).\n- VFS: use system_unbound_wq for delayed_mntput (bsc#1234683).\n- VMCI: fix reference to ioctl-number.rst (git-fixes).\n- accel/habanalabs/gaudi2: unsecure tpc count registers (stable-fixes).\n- accel/habanalabs: export dma-buf only if size/offset multiples of PAGE_SIZE (stable-fixes).\n- accel/habanalabs: fix debugfs files permissions (stable-fixes).\n- accel/habanalabs: increase HL_MAX_STR to 64 bytes to avoid warnings (stable-fixes).\n- acpi: nfit: vmalloc-out-of-bounds Read in acpi_nfit_ctl (git-fixes).\n- af_unix: Call manage_oob() for every skb in unix_stream_read_generic() (bsc#1234725).\n- afs: Automatically generate trace tag enums (git-fixes).\n- afs: Fix EEXIST error returned from afs_rmdir() to be ENOTEMPTY (git-fixes).\n- afs: Fix cleanup of immediately failed async calls (git-fixes).\n- afs: Fix directory format encoding struct (git-fixes).\n- afs: Fix missing subdir edit when renamed between parent dirs (git-fixes).\n- afs: Fix the fallback handling for the YFS.RemoveFile2 RPC call (git-fixes).\n- afs: Fix the maximum cell name length (git-fixes).\n- amdgpu/uvd: get ring reference from rq scheduler (git-fixes).\n- arch: Introduce arch_{,try_}_cmpxchg128{,_local}() (bsc#1220773).\n- arch: Remove cmpxchg_double (bsc#1220773).\n- arch: consolidate arch_irq_work_raise prototypes (git-fixes).\n- arm64/sme: Move storage of reg_smidr to __cpuinfo_store_cpu() (git-fixes)\n- arm64: Ensure bits ASID[15:8] are masked out when the kernel uses (bsc#1234605)\n- arm64: Filter out SVE hwcaps when FEAT_SVE isn't implemented (git-fixes)\n- arm64: Force position-independent veneers (git-fixes).\n- arm64: Kconfig: Make SME depend on BROKEN for now (git-fixes bsc#1236245) Update arm64 default configuration file\n- arm64: Kconfig: Make SME depend on BROKEN for now (git-fixes).\n- arm64: dts: imx8mp: correct sdhc ipg clk (git-fixes).\n- arm64: dts: rockchip: Add sdmmc/sdio/emmc reset controls for RK3328 (git-fixes)\n- arm64: dts: rockchip: add hevc power domain clock to rk3328 (git-fixes).\n- arm64: dts: rockchip: increase gmac rx_delay on rk3399-puma (git-fixes)\n- arm64: ptrace: fix partial SETREGSET for NT_ARM_TAGGED_ADDR_CTRL (git-fixes).\n- arm64: tegra: Disable Tegra234 sce-fabric node (git-fixes)\n- arm64: tegra: Fix Tegra234 PCIe interrupt-map (git-fixes)\n- arm64: tegra: Fix typo in Tegra234 dce-fabric compatible (git-fixes)\n- ata: libata-core: Set ATA_QCFLAG_RTF_FILLED in fill_result_tf() (stable-fixes).\n- autofs: fix memory leak of waitqueues in autofs_catatonic_mode (git-fixes).\n- batman-adv: Do not let TT changes list grows indefinitely (git-fixes).\n- batman-adv: Do not send uninitialized TT changes (git-fixes).\n- batman-adv: Remove uninitialized data in full table TT response (git-fixes).\n- blacklist.conf: printk/sysctl: breaks kernel without pre-requisite patches (bsc#1229025)\n- blk-cgroup: Fix UAF in blkcg_unpin_online() (bsc#1234726).\n- blk-core: use pr_warn_ratelimited() in bio_check_ro() (bsc#1234139).\n- blk-iocost: Fix an UBSAN shift-out-of-bounds warning (bsc#1234144).\n- blk-iocost: do not WARN if iocg was already offlined (bsc#1234147).\n- blk-throttle: fix lockdep warning of \"cgroup_mutex or RCU read lock required!\" (bsc#1234140).\n- block, bfq: choose the last bfqq from merge chain in bfq_setup_cooperator() (bsc#1234149).\n- block, bfq: do not break merge chain in bfq_split_bfqq() (bsc#1234150).\n- block, bfq: fix bfqq uaf in bfq_limit_depth() (bsc#1234160).\n- block, bfq: fix procress reference leakage for bfqq in merge chain (bsc#1234280).\n- block, bfq: fix uaf for accessing waker_bfqq after splitting (bsc#1234279).\n- block/mq-deadline: Fix the tag reservation code (bsc#1234148).\n- block: Call .limit_depth() after .hctx has been set (bsc#1234148).\n- block: Fix where bio IO priority gets set (bsc#1234145).\n- block: prevent an integer overflow in bvec_try_merge_hw_page (bsc#1234142).\n- block: update the stable_writes flag in bdev_add (bsc#1234141).\n- bnxt_en: Fix GSO type for HW GRO packets on 5750X chips (git-fixes)\n- bnxt_en: Fix receive ring space parameters when XDP is active (git-fixes).\n- bnxt_en: Reserve rings after PCIe AER recovery if NIC interface is down (git-fixes).\n- bnxt_en: Set backplane link modes correctly for ethtool (git-fixes).\n- bpf, x86: Fix PROBE_MEM runtime load check (git-fixes).\n- bpf: verifier: prevent userspace memory access (git-fixes).\n- btrfs: fix use-after-free in btrfs_encoded_read_endio() (bsc#1235445).\n- btrfs: fix use-after-free waiting for encoded read endios (bsc#1235128)\n- btrfs: fix use-after-free waiting for encoded read endios (bsc#1235445).\n- bus: mhi: host: Free mhi_buf vector inside mhi_alloc_bhie_table() (git-fixes).\n- can: gs_usb: add VID/PID for Xylanta SAINT3 product family (stable-fixes).\n- can: j1939: fix error in J1939 documentation (stable-fixes).\n- ceph: improve error handling and short/overflow-read logic in __ceph_sync_read() (bsc#1228592).\n- checkpatch: always parse orig_commit in fixes tag (git-fixes).\n- checkpatch: check for missing Fixes tags (stable-fixes).\n- cleanup: Add conditional guard support (stable-fixes).\n- cleanup: Adjust scoped_guard() macros to avoid potential warning (stable-fixes).\n- cleanup: Remove address space of returned pointer (git-fixes).\n- clocksource/drivers/timer-ti-dm: Fix child node refcount handling (git-fixes).\n- clocksource/drivers:sp804: Make user selectable (git-fixes).\n- counter: stm32-timer-cnt: Add check for clk_enable() (git-fixes).\n- counter: ti-ecap-capture: Add check for clk_enable() (git-fixes).\n- cpufreq: ACPI: Fix max-frequency computation (git-fixes).\n- cpufreq: Do not unregister cpufreq cooling on CPU hotplug (git-fixes).\n- cpufreq: amd-pstate: remove global header file (git-fixes).\n- cpufreq: intel_pstate: Check turbo_is_disabled() in store_no_turbo() (bsc#1234619).\n- cpufreq: intel_pstate: Do not update global.turbo_disabled after initialization (bsc#1234619).\n- cpufreq: intel_pstate: Drop redundant locking from intel_pstate_driver_cleanup() (bsc#1234619).\n- cpufreq: intel_pstate: Fix unchecked HWP MSR access (bsc#1234619).\n- cpufreq: intel_pstate: Fold intel_pstate_max_within_limits() into caller (bsc#1234619).\n- cpufreq: intel_pstate: Get rid of unnecessary READ_ONCE() annotations (bsc#1234619).\n- cpufreq: intel_pstate: Make hwp_notify_lock a raw spinlock (git-fixes).\n- cpufreq: intel_pstate: Read global.no_turbo under READ_ONCE() (bsc#1234619).\n- cpufreq: intel_pstate: Rearrange show_no_turbo() and store_no_turbo() (bsc#1234619).\n- cpufreq: intel_pstate: Refine computation of P-state for given frequency (bsc#1234619).\n- cpufreq: intel_pstate: Replace three global.turbo_disabled checks (bsc#1234619).\n- cpufreq: intel_pstate: Revise global turbo disable check (bsc#1234619).\n- cpufreq: intel_pstate: Simplify spinlock locking (bsc#1234619).\n- cpufreq: intel_pstate: Update the maximum CPU frequency consistently (bsc#1234619).\n- cpufreq: intel_pstate: Use HWP to initialize ITMT if CPPC is missing (git-fixes).\n- cpufreq: intel_pstate: Use __ro_after_init for three variables (bsc#1234619).\n- cpufreq: intel_pstate: Wait for canceled delayed work to complete (bsc#1234619).\n- cpufreq: intel_pstate: fix pstate limits enforcement for adjust_perf call back (git-fixes).\n- cpuidle: Avoid potential overflow in integer multiplication (git-fixes).\n- cpupower: fix TSC MHz calculation (git-fixes).\n- crypto: caam - use JobR's space to access page 0 regs (git-fixes).\n- crypto: ecc - Prevent ecc_digits_from_bytes from reading too many bytes (git-fixes).\n- crypto: ecdsa - Avoid signed integer overflow on signature decoding (stable-fixes).\n- crypto: ecdsa - Convert byte arrays with key coordinates to digits (stable-fixes).\n- crypto: ecdsa - Rename keylen to bufsize where necessary (stable-fixes).\n- crypto: ecdsa - Use ecc_digits_from_bytes to convert signature (stable-fixes).\n- crypto: iaa - Fix IAA disabling that occurs when sync_mode is set to 'async' (git-fixes).\n- crypto: ixp4xx - fix OF node reference leaks in init_ixp_crypto() (git-fixes).\n- crypto: qat - disable IOV in adf_dev_stop() (git-fixes).\n- crypto: qce - fix goto jump in error path (git-fixes).\n- crypto: qce - fix priority to be less than ARMv8 CE (git-fixes).\n- crypto: qce - unregister previously registered algos in error path (git-fixes).\n- crypto: x86/sha256 - Add parentheses around macros' single arguments (stable-fixes).\n- cyrpto/b128ops: Remove struct u128 (bsc#1220773).\n- devcoredump: cleanup some comments (git-fixes).\n- devlink: Fix length of eswitch inline-mode (git-fixes).\n- dlm: fix possible lkb_resource null dereference (git-fixes).\n- dma-buf: fix dma_fence_array_signaled v4 (stable-fixes).\n- dma-debug: fix a possible deadlock on radix_lock (stable-fixes).\n- dmaengine: apple-admac: Avoid accessing registers in probe (git-fixes).\n- dmaengine: at_xdmac: avoid null_prt_deref in at_xdmac_prep_dma_memset (git-fixes).\n- dmaengine: dw: Select only supported masters for ACPI devices (git-fixes).\n- dmaengine: idxd: Check for driver name match before sva user feature (bsc#1234357).\n- dmaengine: mv_xor: fix child node refcount handling in early exit (git-fixes).\n- dmaengine: tegra: Return correct DMA status when paused (git-fixes).\n- dmaengine: ti: edma: fix OF node reference leaks in edma_driver (git-fixes).\n- docs: media: update location of the media patches (stable-fixes).\n- docs: power: Fix footnote reference for Toshiba Satellite P10-554 (git-fixes).\n- driver core: Add FWLINK_FLAG_IGNORE to completely ignore a fwnode link (stable-fixes).\n- driver core: class: Fix wild pointer dereferences in API class_dev_iter_next() (git-fixes).\n- driver core: fw_devlink: Improve logs for cycle detection (stable-fixes).\n- driver core: fw_devlink: Stop trying to optimize cycle detection logic (git-fixes).\n- drivers/card_reader/rtsx_usb: Restore interrupt based detection (git-fixes).\n- drivers: net: ionic: add missed debugfs cleanup to ionic_probe() error path (git-fixes).\n- drm/amd/display: Add HDR workaround for specific eDP (stable-fixes).\n- drm/amd/display: Add NULL check for clk_mgr in dcn32_init_hw (stable-fixes).\n- drm/amd/display: Add check for granularity in dml ceil/floor helpers (stable-fixes).\n- drm/amd/display: Allow backlight to go below `AMDGPU_DM_DEFAULT_MIN_BACKLIGHT` (stable-fixes).\n- drm/amd/display: Avoid overflow assignment in link_dp_cts (stable-fixes).\n- drm/amd/display: Fix DSC-re-computing (stable-fixes).\n- drm/amd/display: Fix Synaptics Cascaded Panamera DSC Determination (stable-fixes).\n- drm/amd/display: Fix incorrect DSC recompute trigger (stable-fixes).\n- drm/amd/display: Revert Avoid overflow assignment (stable-fixes).\n- drm/amd/display: Use HW lock mgr for PSR1 (stable-fixes).\n- drm/amd/display: Use gpuvm_min_page_size_kbytes for DML2 surfaces (stable-fixes).\n- drm/amd/display: increase MAX_SURFACES to the value supported by hw (stable-fixes).\n- drm/amd/pm: Fix an error handling path in vega10_enable_se_edc_force_stall_config() (git-fixes).\n- drm/amd/pm: fix the high voltage issue after unload (stable-fixes).\n- drm/amd/pm: update current_socclk and current_uclk in gpu_metrics on smu v13.0.7 (stable-fixes).\n- drm/amdgpu/gfx10: use rlc safe mode for soft recovery (stable-fixes).\n- drm/amdgpu/gfx11: use rlc safe mode for soft recovery (stable-fixes).\n- drm/amdgpu/gfx9: properly handle error ints on all pipes (stable-fixes).\n- drm/amdgpu/gfx9: use rlc safe mode for soft recovery (stable-fixes).\n- drm/amdgpu/hdp5.2: do a posting read when flushing HDP (stable-fixes).\n- drm/amdgpu/pm: Remove gpu_od if it's an empty directory (stable-fixes).\n- drm/amdgpu/umsch: do not execute umsch test when GPU is in reset/suspend (stable-fixes).\n- drm/amdgpu/umsch: reinitialize write pointer in hw init (stable-fixes).\n- drm/amdgpu/vcn: reset fw_shared under SRIOV (git-fixes).\n- drm/amdgpu/vcn: reset fw_shared when VCPU buffers corrupted on vcn v4.0.3 (stable-fixes).\n- drm/amdgpu: Block MMR_READ IOCTL in reset (stable-fixes).\n- drm/amdgpu: Dereference the ATCS ACPI buffer (stable-fixes).\n- drm/amdgpu: Fix potential NULL pointer dereference in atomctrl_get_smc_sclk_range_table (git-fixes).\n- drm/amdgpu: add raven1 gfxoff quirk (stable-fixes).\n- drm/amdgpu: add smu 14.0.1 discovery support (stable-fixes).\n- drm/amdgpu: always sync the GFX pipe on ctx switch (stable-fixes).\n- drm/amdgpu: clear RB_OVERFLOW bit when enabling interrupts for vega20_ih (stable-fixes).\n- drm/amdgpu: differentiate external rev id for gfx 11.5.0 (stable-fixes).\n- drm/amdgpu: disallow multiple BO_HANDLES chunks in one submit (stable-fixes).\n- drm/amdgpu: do not access invalid sched (git-fixes).\n- drm/amdgpu: enable gfxoff quirk on HP 705G4 (stable-fixes).\n- drm/amdgpu: fix unchecked return value warning for amdgpu_gfx (stable-fixes).\n- drm/amdgpu: fix usage slab after free (stable-fixes).\n- drm/amdgpu: prevent BO_HANDLES error from being overwritten (git-fixes).\n- drm/amdgpu: refine error handling in amdgpu_ttm_tt_pin_userptr (stable-fixes).\n- drm/amdgpu: set the right AMDGPU sg segment limitation (stable-fixes).\n- drm/amdgpu: simplify return statement in amdgpu_ras_eeprom_init (git-fixes).\n- drm/amdgpu: skip amdgpu_device_cache_pci_state under sriov (stable-fixes).\n- drm/amdgpu: tear down ttm range manager for doorbell in amdgpu_ttm_fini() (git-fixes).\n- drm/amdkfd: Correct the migration DMA map direction (stable-fixes).\n- drm/amdkfd: Fix resource leak in criu restore queue (stable-fixes).\n- drm/amdkfd: Use device based logging for errors (stable-fixes).\n- drm/amdkfd: Use the correct wptr size (stable-fixes).\n- drm/amdkfd: fixed page fault when enable MES shader debugger (git-fixes).\n- drm/amdkfd: pause autosuspend when creating pdd (stable-fixes).\n- drm/bridge: adv7511_audio: Update Audio InfoFrame properly (git-fixes).\n- drm/bridge: it6505: Change definition of AUX_FIFO_MAX_SIZE (git-fixes).\n- drm/bridge: it6505: Enable module autoloading (stable-fixes).\n- drm/bridge: it6505: Fix inverted reset polarity (git-fixes).\n- drm/bridge: it6505: update usleep_range for RC circuit charge time (stable-fixes).\n- drm/display: Fix building with GCC 15 (stable-fixes).\n- drm/dp_mst: Ensure mst_primary pointer is valid in drm_dp_mst_handle_up_req() (stable-fixes).\n- drm/dp_mst: Fix MST sideband message body length check (stable-fixes).\n- drm/dp_mst: Fix resetting msg rx state after topology removal (git-fixes).\n- drm/dp_mst: Verify request type in the corresponding down message reply (stable-fixes).\n- drm/etnaviv: Fix page property being used for non writecombine buffers (git-fixes).\n- drm/etnaviv: flush shader L1 cache after user commandstream (stable-fixes).\n- drm/i915/dg1: Fix power gate sequence (git-fixes).\n- drm/i915/fb: Relax clear color alignment to 64 bytes (stable-fixes).\n- drm/i915: Fix NULL pointer dereference in capture_engine (git-fixes).\n- drm/i915: Fix memory leak by correcting cache object name in error handler (git-fixes).\n- drm/mcde: Enable module autoloading (stable-fixes).\n- drm/mediatek: Add return value check when reading DPCD (git-fixes).\n- drm/mediatek: Add support for 180-degree rotation in the display driver (git-fixes).\n- drm/mediatek: Fix YCbCr422 color format issue for DP (git-fixes).\n- drm/mediatek: Fix mode valid issue for dp (git-fixes).\n- drm/mediatek: Set private-\u003eall_drm_private[i]-\u003edrm to NULL if mtk_drm_bind returns err (git-fixes).\n- drm/mediatek: mtk_dsi: Add registers to pdata to fix MT8186/MT8188 (git-fixes).\n- drm/mediatek: stop selecting foreign drivers (git-fixes).\n- drm/modes: Avoid divide by zero harder in drm_mode_vrefresh() (stable-fixes).\n- drm/msm/dp: set safe_to_exit_level before printing it (git-fixes).\n- drm/msm/dpu: link DSPP_2/_3 blocks on SC8180X (git-fixes).\n- drm/msm/dpu: link DSPP_2/_3 blocks on SM8150 (git-fixes).\n- drm/msm/dpu: link DSPP_2/_3 blocks on SM8250 (git-fixes).\n- drm/msm/dpu: link DSPP_2/_3 blocks on SM8350 (git-fixes).\n- drm/msm/dpu: link DSPP_2/_3 blocks on SM8550 (git-fixes).\n- drm/msm: Check return value of of_dma_configure() (git-fixes).\n- drm/msm: do not clean up priv-\u003ekms prematurely (git-fixes).\n- drm/nouveau/gsp: Use the sg allocator for level 2 of radix3 (stable-fixes).\n- drm/panel: novatek-nt35950: fix return value check in nt35950_probe() (git-fixes).\n- drm/panel: simple: Add Microchip AC69T88A LVDS Display panel (stable-fixes).\n- drm/printer: Allow NULL data in devcoredump printer (stable-fixes).\n- drm/radeon/r100: Handle unknown family in r100_cp_init_microcode() (stable-fixes).\n- drm/radeon/r600_cs: Fix possible int overflow in r600_packet3_check() (stable-fixes).\n- drm/radeon: Fix spurious unplug event on radeon HDMI (git-fixes).\n- drm/radeon: add helper rdev_to_drm(rdev) (stable-fixes).\n- drm/radeon: change rdev-\u003eddev to rdev_to_drm(rdev) (stable-fixes).\n- drm/rcar-du: dsi: Fix PHY lock bit check (git-fixes).\n- drm/rockchip: cdn-dp: Use drm_connector_helper_hpd_irq_event() (git-fixes).\n- drm/rockchip: vop2: Check linear format for Cluster windows on rk3566/8 (git-fixes).\n- drm/rockchip: vop2: Fix cluster windows alpha ctrl regsiters offset (git-fixes).\n- drm/rockchip: vop2: Fix the mixer alpha setup for layer 0 (git-fixes).\n- drm/sched: memset() 'job' in drm_sched_job_init() (stable-fixes).\n- drm/tidss: Clear the interrupt status for interrupts being disabled (git-fixes).\n- drm/tidss: Fix issue in irq handling causing irq-flood issue (git-fixes).\n- drm/v3d: Assign job pointer to NULL before signaling the fence (git-fixes).\n- drm/v3d: Ensure job pointer is set to NULL after job completion (git-fixes).\n- drm/v3d: Stop active perfmon if it is being destroyed (git-fixes).\n- drm/vc4: hdmi: Avoid log spam for audio start failure (stable-fixes).\n- drm/vc4: hvs: Set AXI panic modes for the HVS (stable-fixes).\n- drm/vmwgfx: Add new keep_resv BO param (git-fixes).\n- drm: adv7511: Drop dsi single lane support (git-fixes).\n- drm: adv7511: Fix use-after-free in adv7533_attach_dsi() (git-fixes).\n- drm: panel-orientation-quirks: Add quirk for AYA NEO 2 model (stable-fixes).\n- drm: panel-orientation-quirks: Add quirk for AYA NEO Founder edition (stable-fixes).\n- drm: panel-orientation-quirks: Add quirk for AYA NEO GEEK (stable-fixes).\n- drm: panel-orientation-quirks: Make Lenovo Yoga Tab 3 X90F DMI match less strict (stable-fixes).\n- erofs: avoid debugging output for (de)compressed data (git-fixes).\n- exfat: ensure that ctime is updated whenever the mtime is (git-fixes).\n- exfat: fix the infinite loop in __exfat_free_cluster() (git-fixes).\n- exfat: fix the infinite loop in exfat_readdir() (git-fixes).\n- exfat: fix uninit-value in __exfat_get_dentry_set (git-fixes).\n- ext4: add a new helper to check if es must be kept (bsc#1234170).\n- ext4: add correct group descriptors and reserved GDT blocks to system zone (bsc#1234164).\n- ext4: add missed brelse in update_backups (bsc#1234171).\n- ext4: allow for the last group to be marked as trimmed (bsc#1234278).\n- ext4: avoid buffer_head leak in ext4_mark_inode_used() (bsc#1234191).\n- ext4: avoid excessive credit estimate in ext4_tmpfile() (bsc#1234180).\n- ext4: avoid negative min_clusters in find_group_orlov() (bsc#1234193).\n- ext4: avoid overlapping preallocations due to overflow (bsc#1234162).\n- ext4: avoid potential buffer_head leak in __ext4_new_inode() (bsc#1234192).\n- ext4: avoid writing unitialized memory to disk in EA inodes (bsc#1234187).\n- ext4: check the extent status again before inserting delalloc block (bsc#1234186).\n- ext4: clear EXT4_GROUP_INFO_WAS_TRIMMED_BIT even mount with discard (bsc#1234190).\n- ext4: convert to exclusive lock while inserting delalloc extents (bsc#1234178).\n- ext4: correct best extent lstart adjustment logic (bsc#1234179).\n- ext4: correct grp validation in ext4_mb_good_group (bsc#1234163).\n- ext4: correct return value of ext4_convert_meta_bg (bsc#1234172).\n- ext4: correct the hole length returned by ext4_map_blocks() (bsc#1234178).\n- ext4: correct the start block of counting reserved clusters (bsc#1234169).\n- ext4: do not let fstrim block system suspend (https://bugzilla.kernel.org/show_bug.cgi?id=216322 bsc#1234166).\n- ext4: do not trim the group with corrupted block bitmap (bsc#1234177).\n- ext4: factor out __es_alloc_extent() and __es_free_extent() (bsc#1234170).\n- ext4: factor out a common helper to query extent map (bsc#1234186).\n- ext4: fix inconsistent between segment fstrim and full fstrim (bsc#1234176).\n- ext4: fix incorrect tid assumption in __jbd2_log_wait_for_space() (bsc#1234188).\n- ext4: fix incorrect tid assumption in ext4_wait_for_tail_page_commit() (bsc#1234188).\n- ext4: fix incorrect tid assumption in jbd2_journal_shrink_checkpoint_list() (bsc#1234188).\n- ext4: fix memory leaks in ext4_fname_{setup_filename,prepare_lookup} (bsc#1214954).\n- ext4: fix potential unnitialized variable (bsc#1234183).\n- ext4: fix race between writepages and remount (bsc#1234168).\n- ext4: fix rec_len verify error (bsc#1234167).\n- ext4: fix slab-use-after-free in ext4_es_insert_extent() (bsc#1234170).\n- ext4: fix uninitialized variable in ext4_inlinedir_to_tree (bsc#1234185).\n- ext4: forbid commit inconsistent quota data when errors=remount-ro (bsc#1234178).\n- ext4: make ext4_es_insert_delayed_block() return void (bsc#1234170).\n- ext4: make ext4_es_insert_extent() return void (bsc#1234170).\n- ext4: make ext4_es_remove_extent() return void (bsc#1234170).\n- ext4: make ext4_zeroout_es() return void (bsc#1234170).\n- ext4: make sure allocate pending entry not fail (bsc#1234170).\n- ext4: mark buffer new if it is unwritten to avoid stale data exposure (bsc#1234175).\n- ext4: move 'ix' sanity check to corrent position (bsc#1234174).\n- ext4: move setting of trimmed bit into ext4_try_to_trim_range() (bsc#1234165).\n- ext4: nested locking for xattr inode (bsc#1234189).\n- ext4: propagate errors from ext4_find_extent() in ext4_insert_range() (bsc#1234194).\n- ext4: refactor ext4_da_map_blocks() (bsc#1234178).\n- ext4: remove gdb backup copy for meta bg in setup_new_flex_group_blocks (bsc#1234173).\n- ext4: remove the redundant folio_wait_stable() (bsc#1234184).\n- ext4: set the type of max_zeroout to unsigned int to avoid overflow (bsc#1234182).\n- ext4: set type of ac_groups_linear_remaining to __u32 to avoid overflow (bsc#1234181).\n- ext4: use pre-allocated es in __es_insert_extent() (bsc#1234170).\n- ext4: use pre-allocated es in __es_remove_extent() (bsc#1234170).\n- ext4: using nofail preallocation in ext4_es_insert_delayed_block() (bsc#1234170).\n- ext4: using nofail preallocation in ext4_es_insert_extent() (bsc#1234170).\n- ext4: using nofail preallocation in ext4_es_remove_extent() (bsc#1234170).\n- fbdev: omapfb: Fix an OF node leak in dss_of_port_get_parent_device() (git-fixes).\n- filemap: Fix bounds checking in filemap_read() (bsc#1234209).\n- filemap: add a per-mapping stable writes flag (bsc#1234141).\n- firmware: arm_scmi: Reject clear channel request on A2P (stable-fixes).\n- fs-writeback: do not requeue a clean inode having skipped pages (bsc#1234200).\n- fs/writeback: bail out if there is no more inodes for IO and queued once (bsc#1234207).\n- fsnotify: fix sending inotify event with unexpected filename (bsc#1234198).\n- genirq/cpuhotplug: Retry with cpu_online_mask when migration fails (git-fixes).\n- genirq/cpuhotplug: Skip suspended interrupts when restoring affinity (git-fixes).\n- genirq/irqdesc: Honor caller provided affinity in alloc_desc() (git-fixes).\n- genirq: Make handle_enforce_irqctx() unconditionally available (git-fixes).\n- genksyms: fix memory leak when the same symbol is added from source (git-fixes).\n- genksyms: fix memory leak when the same symbol is read from *.symref file (git-fixes).\n- gfs2: Truncate address space when flipping GFS2_DIF_JDATA flag (git-fixes).\n- gpio: grgpio: Add NULL check in grgpio_probe (git-fixes).\n- gpio: grgpio: use a helper variable to store the address of ofdev-\u003edev (stable-fixes).\n- gpio: mxc: remove dead code after switch to DT-only (git-fixes).\n- gpio: xilinx: Convert gpio_lock to raw spinlock (git-fixes).\n- hfsplus: do not query the device logical block size multiple times (git-fixes).\n- hvc/xen: fix console unplug (git-fixes).\n- hvc/xen: fix error path in xen_hvc_init() to always register frontend driver (git-fixes).\n- hvc/xen: fix event channel handling for secondary consoles (git-fixes).\n- hwmon: (drivetemp) Fix driver producing garbage data when SCSI errors occur (git-fixes).\n- hwmon: (drivetemp) Set scsi command timeout to 10s (stable-fixes).\n- hwmon: (nct6775) Add 665-ACE/600M-CL to ASUS WMI monitoring list (stable-fixes).\n- hwmon: (pmbus/core) clear faults after setting smbalert mask (git-fixes).\n- hwmon: (pmbus_core) Allow to hook PMBUS_SMBALERT_MASK (stable-fixes).\n- hwmon: (tmp513) Do not use \"proxy\" headers (stable-fixes).\n- hwmon: (tmp513) Fix Current Register value interpretation (git-fixes).\n- hwmon: (tmp513) Fix division of negative numbers (git-fixes).\n- hwmon: (tmp513) Fix interpretation of values of Shunt Voltage and Limit Registers (git-fixes).\n- hwmon: (tmp513) Fix interpretation of values of Temperature Result and Limit Registers (git-fixes).\n- hwmon: (tmp513) Simplify with dev_err_probe() (stable-fixes).\n- hwmon: (tmp513) Use SI constants from units.h (stable-fixes).\n- hyperv: Do not overlap the hvcall IO areas in get_vtl() (git-fixes).\n- i2c: core: fix reference leak in i2c_register_adapter() (git-fixes).\n- i2c: i801: Add support for Intel Arrow Lake-H (stable-fixes).\n- i2c: i801: Add support for Intel Panther Lake (stable-fixes).\n- i2c: imx: add imx7d compatible string for applying erratum ERR007805 (git-fixes).\n- i2c: microchip-core: actually use repeated sends (git-fixes).\n- i2c: microchip-core: fix \"ghost\" detections (git-fixes).\n- i2c: mux: demux-pinctrl: check initial mux selection, too (git-fixes).\n- i2c: pnx: Fix timeout in wait functions (git-fixes).\n- i2c: rcar: fix NACK handling when being a target (git-fixes).\n- i2c: riic: Always round-up when calculating bus period (git-fixes).\n- i2c: xgene-slimpro: Migrate to use generic PCC shmem related macros (stable-fixes).\n- i40e: Fix handling changed priv flags (git-fixes).\n- i915/guc: Accumulate active runtime on gt reset (git-fixes).\n- i915/guc: Ensure busyness counter increases motonically (git-fixes).\n- i915/guc: Reset engine utilization buffer before registration (git-fixes).\n- ibmvnic: Free any outstanding tx skbs during scrq reset (bsc#1226980).\n- ice: Unbind the workqueue (bsc#1234989)\n- ice: change q_index variable type to s16 to store -1 value (git-fixes).\n- ice: consistently use q_idx in ice_vc_cfg_qs_msg() (git-fixes).\n- ice: fix PHY Clock Recovery availability check (git-fixes).\n- idpf: add support for SW triggered interrupts (bsc#1235507).\n- idpf: enable WB_ON_ITR (bsc#1235507).\n- idpf: trigger SW interrupt when exiting wb_on_itr mode (bsc#1235507).\n- ieee802154: ca8210: Add missing check for kfifo_alloc() in ca8210_probe() (git-fixes).\n- igb: Fix potential invalid memory access in igb_init_module() (git-fixes).\n- iio: adc: ad7124: Disable all channels at probe time (git-fixes).\n- iio: adc: ad_sigma_delta: Handle CS assertion as intended in ad_sd_read_reg_raw() (git-fixes).\n- iio: adc: at91: call input_free_device() on allocated iio_dev (git-fixes).\n- iio: adc: rockchip_saradc: fix information leak in triggered buffer (git-fixes).\n- iio: adc: ti-ads124s08: Use gpiod_set_value_cansleep() (git-fixes).\n- iio: adc: ti-ads8688: fix information leak in triggered buffer (git-fixes).\n- iio: dummy: iio_simply_dummy_buffer: fix information leak in triggered buffer (git-fixes).\n- iio: gyro: fxas21002c: Fix missing data update in trigger handler (git-fixes).\n- iio: iio-mux: kzalloc instead of devm_kzalloc to ensure page alignment (git-fixes).\n- iio: imu: kmx61: fix information leak in triggered buffer (git-fixes).\n- iio: inkern: call iio_device_put() only on mapped devices (git-fixes).\n- iio: light: as73211: fix channel handling in only-color triggered buffer (git-fixes).\n- iio: light: vcnl4035: fix information leak in triggered buffer (git-fixes).\n- iio: magnetometer: yas530: use signed integer type for clamp limits (git-fixes).\n- iio: pressure: zpa2326: fix information leak in triggered buffer (git-fixes).\n- iio: test : check null return of kunit_kmalloc in iio_rescale_test_scale (git-fixes).\n- instrumentation: Wire up cmpxchg128() (bsc#1220773).\n- intel_th: core: fix kernel-doc warnings (git-fixes).\n- io_uring/rw: avoid punting to io-wq directly (git-fixes).\n- io_uring/tctx: work around xa_store() allocation error issue (git-fixes).\n- io_uring: Fix registered ring file refcount leak (git-fixes).\n- io_uring: always lock __io_cqring_overflow_flush (git-fixes).\n- io_uring: check if iowq is killed before queuing (git-fixes).\n- iommu/io-pgtable-arm: Fix stage-2 map/unmap for concatenated tables (git-fixes).\n- ipmi: ipmb: Add check devm_kasprintf() returned value (git-fixes).\n- ipmi: ssif_bmc: Fix new request loss when bmc ready for a response (git-fixes).\n- irqchip/gic-v3: Force propagation of the active state with a read-back (stable-fixes).\n- irqchip/gic: Correct declaration of *percpu_base pointer in union gic_base (stable-fixes).\n- irqflags: Explicitly ignore lockdep_hrtimer_exit() argument (git-fixes).\n- isofs: handle CDs with bad root inode but good Joliet root directory (bsc#1234199).\n- ixgbe: downgrade logging of unsupported VF API version to debug (git-fixes).\n- ixgbevf: stop attempting IPSEC offload on Mailbox API 1.5 (git-fixes).\n- jffs2: Fix rtime decompressor (git-fixes).\n- jffs2: Prevent rtime decompress memory corruption (git-fixes).\n- jffs2: fix use of uninitialized variable (git-fixes).\n- jfs: add a check to prevent array-index-out-of-bounds in dbAdjTree (git-fixes).\n- jfs: array-index-out-of-bounds fix in dtReadFirst (git-fixes).\n- jfs: fix array-index-out-of-bounds in jfs_readdir (git-fixes).\n- jfs: fix shift-out-of-bounds in dbSplit (git-fixes).\n- jfs: xattr: check invalid xattr size more strictly (git-fixes).\n- kABI workaround for struct auto_pin_cfg_item change (git-fixes).\n- kABI workaround for struct drm_dp_mst_topology_mgr (git-fixes).\n- kabi/severities: make vcap_find_actionfield PASS (bsc#1220773)\n- kasan: make report_lock a raw spinlock (git-fixes).\n- kconfig: fix file name in warnings when loading KCONFIG_DEFCONFIG_LIST (git-fixes).\n- kdb: Fix buffer overflow during tab-complete (bsc#1234652).\n- kdb: Fix console handling when editing and tab-completing commands (bsc#1234655).\n- kdb: Merge identical case statements in kdb_read() (bsc#1234657).\n- kdb: Use format-specifiers rather than memset() for padding in kdb_read() (bsc#1234658).\n- kdb: Use format-strings rather than '\\0' injection in kdb_read() (bsc#1234654).\n- kdb: Use the passed prompt in kdb_position_cursor() (bsc#1234654).\n- kdb: address -Wformat-security warnings (bsc#1234659).\n- kgdb: Flush console before entering kgdb on panic (bsc#1234651).\n- kheaders: Ignore silly-rename files (stable-fixes).\n- ktest.pl: Avoid false positives with grub2 skip regex (stable-fixes).\n- ktest.pl: Check kernelrelease return in get_version (git-fixes).\n- ktest.pl: Fix typo \"accesing\" (git-fixes).\n- ktest.pl: Fix typo in comment (git-fixes).\n- ktest.pl: Remove unused declarations in run_bisect_test function (git-fixes).\n- ktest: force $buildonly = 1 for 'make_warnings_file' test type (stable-fixes).\n- landlock: Handle weird files (git-fixes).\n- latencytop: use correct kernel-doc format for func params (git-fixes).\n- leds: class: Protect brightness_show() with led_cdev-\u003eled_access mutex (stable-fixes).\n- leds: lp8860: Write full EEPROM, not only half of it (git-fixes).\n- leds: netxbig: Fix an OF node reference leak in netxbig_leds_get_of_pdata() (git-fixes).\n- lib/inflate.c: remove dead code (git-fixes).\n- lib/stackdepot: print disabled message only if truly disabled (git-fixes).\n- linux/dmaengine.h: fix a few kernel-doc warnings (git-fixes).\n- locking/atomic/x86: Correct the definition of __arch_try_cmpxchg128() (bsc#1220773 git-fix).\n- loop: fix the the direct I/O support check when used on top of block devices (bsc#1234143).\n- mac80211: fix user-power when emulating chanctx (stable-fixes).\n- mac802154: check local interfaces before deleting sdata list (stable-fixes).\n- mailbox: pcc: Add support for platform notification handling (stable-fixes).\n- mailbox: pcc: Support shared interrupt for multiple subspaces (stable-fixes).\n- mailbox: tegra-hsp: Clear mailbox before using message (git-fixes).\n- maple_tree: simplify split calculation (git-fixes).\n- media: camif-core: Add check for clk_enable() (git-fixes).\n- media: ccs: Clean up parsed CCS static data on parse failure (git-fixes).\n- media: ccs: Fix CCS static data parsing for large block sizes (git-fixes).\n- media: ccs: Fix cleanup order in ccs_probe() (git-fixes).\n- media: cx231xx: Add support for Dexatek USB Video Grabber 1d19:6108 (stable-fixes).\n- media: dvb-frontends: dib3000mb: fix uninit-value in dib3000_write_reg (git-fixes).\n- media: dvb-usb-v2: af9035: fix ISO C90 compilation error on af9035_i2c_master_xfer (git-fixes).\n- media: i2c: imx412: Add missing newline to prints (git-fixes).\n- media: i2c: ov9282: Correct the exposure offset (git-fixes).\n- media: imx-jpeg: Fix potential error pointer dereference in detach_pm() (git-fixes).\n- media: imx296: Add standby delay during probe (git-fixes).\n- media: lmedm04: Handle errors for lme2510_int_read (git-fixes).\n- media: marvell: Add check for clk_enable() (git-fixes).\n- media: mc: fix endpoint iteration (git-fixes).\n- media: mipi-csis: Add check for clk_enable() (git-fixes).\n- media: nxp: imx8-isi: fix v4l2-compliance test errors (git-fixes).\n- media: ov5640: fix get_light_freq on auto (git-fixes).\n- media: rc: iguanair: handle timeouts (git-fixes).\n- media: rkisp1: Fix unused value issue (git-fixes).\n- media: uvcvideo: Add a quirk for the Kaiweets KTI-W02 infrared camera (stable-fixes).\n- media: uvcvideo: Fix crash during unbind if gpio unit is in use (git-fixes).\n- media: uvcvideo: Fix double free in error path (git-fixes).\n- media: uvcvideo: Fix event flags in uvc_ctrl_send_events (git-fixes).\n- media: uvcvideo: Force UVC version to 1.0a for 0408:4035 (stable-fixes).\n- media: uvcvideo: Only save async fh if success (git-fixes).\n- media: uvcvideo: Propagate buf-\u003eerror to userspace (git-fixes).\n- media: uvcvideo: RealSense D421 Depth module metadata (stable-fixes).\n- media: uvcvideo: Remove dangling pointers (git-fixes).\n- media: uvcvideo: Remove redundant NULL assignment (git-fixes).\n- media: uvcvideo: Support partial control reads (git-fixes).\n- memory tiering: count PGPROMOTE_SUCCESS when mem tiering is enabled (git-fixes).\n- memory-failure: use a folio in me_huge_page() (git-fixes).\n- memory: tegra20-emc: fix an OF node reference bug in tegra_emc_find_node_by_ram_code() (git-fixes).\n- mfd: da9052-spi: Change read-mask to write-mask (git-fixes).\n- mfd: intel_soc_pmic_bxtwc: Use IRQ domain for PMIC devices (git-fixes).\n- mfd: intel_soc_pmic_bxtwc: Use IRQ domain for TMU device (git-fixes).\n- mfd: intel_soc_pmic_bxtwc: Use IRQ domain for USB Type-C device (git-fixes).\n- misc: fastrpc: Deregister device nodes properly in error scenarios (git-fixes).\n- misc: fastrpc: Fix copy buffer page size (git-fixes).\n- misc: fastrpc: Fix registered buffer page address (git-fixes).\n- misc: microchip: pci1xxxx: Resolve kernel panic during GPIO IRQ handling (git-fixes).\n- misc: microchip: pci1xxxx: Resolve return code mismatch during GPIO set config (git-fixes).\n- misc: misc_minor_alloc to use ida for all dynamic/misc dynamic minors (git-fixes).\n- mm, kmsan: fix infinite recursion due to RCU critical section (git-fixes).\n- mm,page_owner: do not remove __GFP_NOLOCKDEP in add_stack_record_to_list (git-fixes).\n- mm/filemap: avoid buffered read/write race to read inconsistent data (bsc#1234204).\n- mm/memory-failure: cast index to loff_t before shifting it (git-fixes).\n- mm/memory-failure: check the mapcount of the precise page (git-fixes).\n- mm/memory-failure: fix crash in split_huge_page_to_list from soft_offline_page (git-fixes).\n- mm/memory-failure: pass the folio and the page to collect_procs() (git-fixes).\n- mm/memory-failure: use raw_spinlock_t in struct memory_failure_cpu (git-fixes).\n- mm/memory_hotplug: add missing mem_hotplug_lock (git-fixes).\n- mm/memory_hotplug: fix error handling in add_memory_resource() (git-fixes).\n- mm/memory_hotplug: prevent accessing by index=-1 (git-fixes).\n- mm/memory_hotplug: use pfn math in place of direct struct page manipulation (git-fixes).\n- mm/migrate: correct nr_failed in migrate_pages_sync() (git-fixes).\n- mm/migrate: fix deadlock in migrate_pages_batch() on large folios (git-fixes).\n- mm/migrate: putback split folios when numa hint migration fails (git-fixes).\n- mm/migrate: split source folio if it is on deferred split list (git-fixes).\n- mm/page_owner: remove free_ts from page_owner output (git-fixes).\n- mm/readahead: do not allow order-1 folio (bsc#1234205).\n- mm/readahead: limit page cache size in page_cache_ra_order() (bsc#1234208).\n- mm/rodata_test: use READ_ONCE() to read const variable (git-fixes).\n- mm: convert DAX lock/unlock page to lock/unlock folio (git-fixes).\n- mm: memory-failure: ensure moving HWPoison flag to the raw error pages (git-fixes).\n- mm: memory-failure: fetch compound head after extra page refcnt is held (git-fixes).\n- mm: memory-failure: fix potential page refcnt leak in memory_failure() (git-fixes).\n- mm: memory-failure: fix race window when trying to get hugetlb folio (git-fixes).\n- mm: memory-failure: remove unneeded PageHuge() check (git-fixes).\n- mm: prevent derefencing NULL ptr in pfn_section_valid() (git-fixes).\n- mmc: core: Add SD card quirk for broken poweroff notification (stable-fixes).\n- mmc: mtk-sd: Fix MMC_CAP2_CRYPTO flag setting (git-fixes).\n- mmc: mtk-sd: fix devm_clk_get_optional usage (stable-fixes).\n- mmc: sdhci-esdhc-imx: enable quirks SDHCI_QUIRK_NO_LED (stable-fixes).\n- mmc: sdhci-pci: Add DMI quirk for missing CD GPIO on Vexia Edu Atla 10 tablet (stable-fixes).\n- mmc: sdhci-tegra: Remove SDHCI_QUIRK_BROKEN_ADMA_ZEROLEN_DESC quirk (git-fixes).\n- modpost: fix the missed iteration for the max bit in do_input() (git-fixes).\n- mtd: diskonchip: Cast an operand to prevent potential overflow (git-fixes).\n- mtd: hyperbus: rpc-if: Add missing MODULE_DEVICE_TABLE (git-fixes).\n- mtd: hyperbus: rpc-if: Convert to platform remove callback returning void (stable-fixes).\n- mtd: onenand: Fix uninitialized retlen in do_otp_read() (git-fixes).\n- mtd: rawnand: arasan: Fix double assertion of chip-select (git-fixes).\n- mtd: rawnand: arasan: Fix missing de-registration of NAND (git-fixes).\n- mtd: rawnand: fix double free in atmel_pmecc_create_user() (git-fixes).\n- mtd: spinand: Remove write_enable_op() in markbad() (git-fixes).\n- net :mana :Request a V2 response version for MANA_QUERY_GF_STAT (git-fixes).\n- net/ipv6: release expired exception dst cached in socket (bsc#1216813).\n- net/mlx5e: CT: Fix null-ptr-deref in add rule err flow (git-fixes).\n- net/mlx5e: Remove workaround to avoid syndrome for internal port (git-fixes).\n- net/mlx5e: clear xdp features on non-uplink representors (git-fixes).\n- net/qed: allow old cards not supporting \"num_images\" to work (git-fixes).\n- net/rose: prevent integer overflows in rose_setsockopt() (git-fixes).\n- net: Return error from sk_stream_wait_connect() if sk_wait_event() fails (git-fixes).\n- net: mana: Increase the DEF_RX_BUFFERS_PER_QUEUE to 1024 (bsc#1235246).\n- net: phy: c45-tjaxx: add delay between MDIO write and read in soft_reset (git-fixes).\n- net: rose: fix timer races against user threads (git-fixes).\n- net: usb: qmi_wwan: add Quectel RG650V (stable-fixes).\n- net: usb: qmi_wwan: add Telit FE910C04 compositions (stable-fixes).\n- net: usb: rtl8150: enable basic endpoint checking (git-fixes).\n- net: wwan: iosm: Properly check for valid exec stage in ipc_mmio_init() (git-fixes).\n- net: wwan: t7xx: Fix FSM command timeout issue (git-fixes).\n- netfilter: nf_tables: validate family when identifying table via handle (bsc#1233778 ZDI-24-1454).\n- nfs: ignore SB_RDONLY when mounting nfs (git-fixes).\n- nfsd: fix nfs4_openowner leak when concurrent nfsd4_open occur (git-fixes).\n- nfsd: make sure exp active before svc_export_show (git-fixes).\n- nfsd: release svc_expkey/svc_export with rcu_work (git-fixes).\n- nfsd: restore callback functionality for NFSv4.0 (git-fixes).\n- nilfs2: fix buffer head leaks in calls to truncate_inode_pages() (git-fixes).\n- nilfs2: fix possible int overflows in nilfs_fiemap() (git-fixes).\n- nilfs2: fix potential out-of-bounds memory access in nilfs_find_entry() (git-fixes).\n- nilfs2: prevent use of deleted inode (git-fixes).\n- nvme-pci: 512 byte aligned dma pool segment quirk (git-fixes).\n- nvme-rdma: unquiesce admin_q before destroy it (git-fixes).\n- nvme-tcp: Fix I/O queue cpu spreading for multiple controllers (git-fixes).\n- nvme-tcp: fix the memleak while create new ctrl failed (git-fixes).\n- nvme/multipath: Fix RCU list traversal to use SRCU primitive (git-fixes).\n- nvme: Add error check for xa_store in nvme_get_effects_log (git-fixes).\n- nvme: Add error path for xa_store in nvme_init_effects (git-fixes).\n- nvme: apple: fix device reference counting (git-fixes).\n- nvme: fix bogus kzalloc() return check in nvme_init_effects_log() (git-fixes).\n- nvme: fix metadata handling in nvme-passthrough (git-fixes).\n- nvmet-loop: avoid using mutex in IO hotpath (git-fixes).\n- nvmet: propagate npwg topology (git-fixes).\n- ocfs2: fix uninitialized value in ocfs2_file_read_iter() (git-fixes).\n- ocfs2: free inode when ocfs2_get_init_inode() fails (git-fixes).\n- of/irq: Fix using uninitialized variable @addr_len in API of_irq_parse_one() (git-fixes).\n- of: Fix error path in of_parse_phandle_with_args_map() (git-fixes).\n- of: Fix refcount leakage for OF node returned by __of_get_dma_parent() (git-fixes).\n- of: address: Report error on resource bounds overflow (stable-fixes).\n- padata: add pd get/put refcnt helper (git-fixes).\n- padata: avoid UAF for reorder_work (git-fixes).\n- padata: fix UAF in padata_reorder (git-fixes).\n- parisc: Raise minimal GCC version (bsc#1220773).\n- parisc: Raise minimal GCC version to 12.0.0 (bsc#1220773 git-fix).\n- percpu: Add {raw,this}_cpu_try_cmpxchg() (bsc#1220773).\n- percpu: Fix self-assignment of __old in raw_cpu_generic_try_cmpxchg() (bsc#1220773 git-fix).\n- percpu: Wire up cmpxchg128 (bsc#1220773).\n- phy: core: Fix an OF node refcount leakage in _of_phy_get() (git-fixes).\n- phy: core: Fix an OF node refcount leakage in of_phy_provider_lookup() (git-fixes).\n- phy: core: Fix that API devm_of_phy_provider_unregister() fails to unregister the phy provider (git-fixes).\n- phy: core: Fix that API devm_phy_destroy() fails to destroy the phy (git-fixes).\n- phy: core: Fix that API devm_phy_put() fails to release the phy (git-fixes).\n- phy: qcom-qmp: Fix register name in RX Lane config of SC8280XP (git-fixes).\n- phy: rockchip: naneng-combphy: fix phy reset (git-fixes).\n- phy: usb: Toggle the PHY power during init (git-fixes).\n- pinctrl: amd: Take suspend type into consideration which pins are non-wake (git-fixes).\n- pinctrl: mcp23s08: Fix sleeping in atomic context due to regmap locking (git-fixes).\n- pinctrl: qcom-pmic-gpio: add support for PM8937 (stable-fixes).\n- pinctrl: qcom: spmi-mpp: Add PM8937 compatible (stable-fixes).\n- pinctrl: samsung: fix fwnode refcount cleanup if platform_get_irq_optional() fails (git-fixes).\n- pinmux: Use sequential access to access desc-\u003epinmux data (stable-fixes).\n- platform/chrome: cros_ec_proto: Lock device when updating MKBP version (git-fixes).\n- platform/x86/amd/pmc: Only disable IRQ1 wakeup where i8042 actually enabled it (git-fixes).\n- platform/x86/intel-uncore-freq: Ignore minor version change (bsc#1225897).\n- platform/x86/intel/tpmi: Add defines to get version information (bsc#1225897).\n- platform/x86: asus-nb-wmi: Ignore unknown event 0xCF (stable-fixes).\n- platform/x86: dell-smbios-base: Extends support to Alienware products (stable-fixes).\n- platform/x86: dell-wmi-base: Handle META key Lock/Unlock events (stable-fixes).\n- platform/x86: thinkpad_acpi: Fix for ThinkPad's with ECFW showing incorrect fan speed (stable-fixes).\n- pm:cpupower: Add missing powercap_set_enabled() stub function (git-fixes).\n- power: ip5xxx_power: Fix return value on ADC read errors (git-fixes).\n- power: supply: gpio-charger: Fix set charge current limits (git-fixes).\n- powerpc/book3s64/hugetlb: Fix disabling hugetlb when fadump is active (bsc#1235108).\n- powerpc/iommu: Move pSeries specific functions to pseries/iommu.c (bsc#1220711 ltc#205755).\n- powerpc/iommu: Only build sPAPR access functions on pSeries (bsc#1220711 ltc#205755).\n- powerpc/powernv/pci: Remove MVE code (bsc#1220711 ltc#205755).\n- powerpc/powernv/pci: Remove ioda1 support (bsc#1220711 ltc#205755).\n- powerpc/powernv/pci: Remove last IODA1 defines (bsc#1220711 ltc#205755).\n- powerpc/pseries/eeh: Fix get PE state translation (bsc#1215199).\n- powerpc/pseries/iommu: IOMMU incorrectly marks MMIO range in DDW (bsc#1218470 ltc#204531).\n- powerpc/pseries/vas: Add close() callback in vas_vm_ops struct (bsc#1234825).\n- pps: add an error check in parport_attach (git-fixes).\n- pps: remove usage of the deprecated ida_simple_xx() API (stable-fixes).\n- printk: Add is_printk_legacy_deferred() (bsc#1236733).\n- printk: Defer legacy printing when holding printk_cpu_sync (bsc#1236733).\n- proc/softirqs: replace seq_printf with seq_put_decimal_ull_width (git-fixes).\n- pwm: stm32-lp: Add check for clk_enable() (git-fixes).\n- pwm: stm32: Add check for clk_enable() (git-fixes).\n- quota: Fix rcu annotations of inode dquot pointers (bsc#1234197).\n- quota: explicitly forbid quota files from being encrypted (bsc#1234196).\n- quota: flush quota_release_work upon quota writeback (bsc#1234195).\n- quota: simplify drop_dquot_ref() (bsc#1234197).\n- rcu-tasks: Pull sampling of -\u003epercpu_dequeue_lim out of loop (git-fixes)\n- rcu/tree: Defer setting of jiffies during stall reset (git-fixes)\n- rcu: Dump memory object info if callback function is invalid (git-fixes)\n- rcu: Eliminate rcu_gp_slow_unregister() false positive (git-fixes)\n- rcuscale: Move rcu_scale_writer() (git-fixes)\n- rdma/cxgb4: Prevent potential integer overflow on 32bit (git-fixes)\n- readahead: use ilog2 instead of a while loop in page_cache_ra_order() (bsc#1234208).\n- regmap: Use correct format specifier for logging range errors (stable-fixes).\n- regulator: core: Add missing newline character (git-fixes).\n- regulator: of: Implement the unwind path of of_regulator_match() (git-fixes).\n- regulator: rk808: Add apply_bit for BUCK3 on RK809 (stable-fixes).\n- remoteproc: core: Fix ida_free call while not allocated (git-fixes).\n- rtc: cmos: avoid taking rtc_lock for extended period of time (stable-fixes).\n- rtc: pcf85063: fix potential OOB write in PCF85063 NVMEM read (git-fixes).\n- rtc: zynqmp: Fix optional clock name property (git-fixes).\n- s390/cio: Do not unregister the subchannel based on DNV (git-fixes).\n- s390/cpum_sf: Convert to cmpxchg128() (bsc#1220773).\n- s390/cpum_sf: Handle CPU hotplug remove during sampling (git-fixes).\n- s390/cpum_sf: Remove WARN_ON_ONCE statements (git-fixes).\n- s390/facility: Disable compile time optimization for decompressor code (git-fixes).\n- s390/iucv: MSG_PEEK causes memory leak in iucv_sock_destruct() (git-fixes).\n- s390/pageattr: Implement missing kernel_page_present() (git-fixes).\n- s390x config: IOMMU_DEFAULT_DMA_LAZY=y (bsc#1235646)\n- samples/landlock: Fix possible NULL dereference in parse_path() (git-fixes).\n- scatterlist: fix incorrect func name in kernel-doc (git-fixes).\n- sched/fair: Fix value reported by hot tasks pulled in /proc/schedstat (bsc#1235865).\n- sched/fair: Fix value reported by hot tasks pulled in /proc/schedstat -kabi (bsc#1235865).\n- sched/numa: fix memory leak due to the overwritten vma-\u003enumab_state (git fixes (sched/numa)).\n- scsi: lpfc: Add handling for LS_RJT reason explanation authentication required (bsc#1235409).\n- scsi: lpfc: Add support for large fw object application layer reads (bsc#1235409).\n- scsi: lpfc: Change lpfc_nodelist save_flags member into a bitmask (bsc#1235409).\n- scsi: lpfc: Copyright updates for 14.4.0.7 patches (bsc#1235409).\n- scsi: lpfc: Delete NLP_TARGET_REMOVE flag due to obsolete usage (bsc#1235409).\n- scsi: lpfc: Modify handling of ADISC based on ndlp state and RPI registration (bsc#1235409).\n- scsi: lpfc: Redefine incorrect type in lpfc_create_device_data() (bsc#1235409).\n- scsi: lpfc: Restrict the REG_FCFI MAM field to FCoE adapters only (bsc#1235409).\n- scsi: lpfc: Update definition of firmware configuration mbox cmds (bsc#1235409).\n- scsi: lpfc: Update lpfc version to 14.4.0.7 (bsc#1235409).\n- scsi: qla2xxx: Fix NVMe and NPIV connect issue (bsc#1235406).\n- scsi: qla2xxx: Fix abort in bsg timeout (bsc#1235406).\n- scsi: qla2xxx: Fix use after free on unload (bsc#1235406).\n- scsi: qla2xxx: Remove check req_sg_cnt should be equal to rsp_sg_cnt (bsc#1235406).\n- scsi: qla2xxx: Remove the unused 'del_list_entry' field in struct fc_port (bsc#1235406).\n- scsi: qla2xxx: Supported speed displayed incorrectly for VPorts (bsc#1235406).\n- scsi: qla2xxx: Update version to 10.02.09.400-k (bsc#1235406).\n- scsi: storvsc: Do not flag MAINTENANCE_IN return of SRB_STATUS_DATA_OVERRUN as an error (git-fixes).\n- scsi: storvsc: Ratelimit warning logs to prevent VM denial of service (git-fixes).\n- seccomp: Stub for !CONFIG_SECCOMP (stable-fixes).\n- selftest: media_tests: fix trivial UAF typo (git-fixes).\n- selftests/alsa: Fix circular dependency involving global-timer (stable-fixes).\n- selftests/bpf: Test PROBE_MEM of VSYSCALL_ADDR on x86-64 (git-fixes).\n- selftests/landlock: Fix error message (git-fixes).\n- selftests/mm/cow: modify the incorrect checking parameters (git-fixes).\n- selftests/powerpc: Fix argument order to timer_sub() (git-fixes).\n- selftests: harness: fix printing of mismatch values in __EXPECT() (git-fixes).\n- selftests: mptcp: avoid spurious errors on disconnect (git-fixes).\n- selftests: tc-testing: reduce rshift value (stable-fixes).\n- selftests: timers: clocksource-switch: Adapt progress to kselftest framework (git-fixes).\n- selinux: Fix SCTP error inconsistency in selinux_socket_bind() (git-fixes).\n- serial: 8250: Adjust the timeout for FIFO mode (git-fixes).\n- serial: 8250_dw: Add Sophgo SG2044 quirk (stable-fixes).\n- serial: 8250_dw: Do not use struct dw8250_data outside of 8250_dw (git-fixes).\n- serial: 8250_dw: Replace ACPI device check by a quirk (git-fixes).\n- serial: 8250_fintek: Add support for F81216E (stable-fixes).\n- serial: Do not hold the port lock when setting rx-during-tx GPIO (git-fixes).\n- serial: amba-pl011: Fix RX stall when DMA is used (git-fixes).\n- serial: amba-pl011: Use port lock wrappers (stable-fixes).\n- serial: amba-pl011: fix build regression (git-fixes).\n- serial: do not use uninitialized value in uart_poll_init() (git-fixes).\n- serial: imx: only set receiver level if it is zero (git-fixes).\n- serial: imx: set receiver level before starting uart (git-fixes).\n- serial: qcom-geni: Do not cancel/abort if we can't get the port lock (git-fixes).\n- serial: qcom-geni: disable interrupts during console writes (git-fixes).\n- serial: qcom-geni: fix arg types for qcom_geni_serial_poll_bit() (git-fixes).\n- serial: qcom-geni: fix console corruption (git-fixes).\n- serial: qcom-geni: fix dma rx cancellation (git-fixes).\n- serial: qcom-geni: fix false console tx restart (git-fixes).\n- serial: qcom-geni: fix fifo polling timeout (git-fixes).\n- serial: qcom-geni: fix hard lockup on buffer flush (git-fixes).\n- serial: qcom-geni: fix polled console corruption (git-fixes).\n- serial: qcom-geni: fix polled console initialisation (git-fixes).\n- serial: qcom-geni: fix receiver enable (git-fixes).\n- serial: qcom-geni: fix shutdown race (git-fixes).\n- serial: qcom-geni: fix soft lockup on sw flow control and suspend (git-fixes).\n- serial: qcom-geni: introduce qcom_geni_serial_poll_bitfield() (git-fixes).\n- serial: qcom-geni: revert broken hibernation support (git-fixes).\n- serial: sh-sci: Do not probe the serial port if its slot in sci_ports[] is in use (git-fixes).\n- serial: sh-sci: Drop __initdata macro for port_cfg (git-fixes).\n- serial: stm32: Return IRQ_NONE in the ISR if no handling happend (git-fixes).\n- serial: stm32: do not always set SER_RS485_RX_DURING_TX if RS485 is enabled (git-fixes).\n- series.conf: temporarily disable upstream patch patches.suse/ocfs2-fix-UBSAN-warning-in-ocfs2_verify_volume.patch (bsc#1236138)\n- slub: Replace cmpxchg_double() (bsc#1220773).\n- slub: Replace cmpxchg_double() - KABI fix (bsc#1220773).\n- smb: client: fix TCP timers deadlock after rmmod (git-fixes) [hcarvalho: fix issue described in bsc#1233642]\n- soc/fsl: cpm: qmc: Convert to platform remove callback returning void (stable-fixes).\n- soc: atmel: fix device_node release in atmel_soc_device_init() (git-fixes).\n- soc: fsl: cpm1: qmc: Fix blank line and spaces (stable-fixes).\n- soc: fsl: cpm1: qmc: Introduce qmc_init_resource() and its CPM1 version (stable-fixes).\n- soc: fsl: cpm1: qmc: Introduce qmc_{init,exit}_xcc() and their CPM1 version (stable-fixes).\n- soc: fsl: cpm1: qmc: Re-order probe() operations (stable-fixes).\n- soc: fsl: cpm1: qmc: Set the ret error code on platform_get_irq() failure (git-fixes).\n- soc: imx8m: Probe the SoC driver as platform driver (stable-fixes).\n- soc: mediatek: mtk-devapc: Fix leaking IO map on error paths (git-fixes).\n- soc: qcom: Add check devm_kasprintf() returned value (stable-fixes).\n- soc: qcom: geni-se: Add M_TX_FIFO_NOT_EMPTY bit definition (git-fixes).\n- soc: qcom: geni-se: add GP_LENGTH/IRQ_EN_SET/IRQ_EN_CLEAR registers (git-fixes).\n- soc: qcom: smem_state: fix missing of_node_put in error path (git-fixes).\n- soc: qcom: socinfo: Avoid out of bounds read of serial number (git-fixes).\n- soc: qcom: socinfo: fix revision check in qcom_socinfo_probe() (git-fixes).\n- sound: usb: enable DSD output for ddHiFi TC44C (stable-fixes).\n- sound: usb: format: do not warn that raw DSD is unsupported (stable-fixes).\n- spi: aspeed: Fix an error handling path in aspeed_spi_[read|write]_user() (git-fixes).\n- spi: zynq-qspi: Add check for clk_enable() (git-fixes).\n- srcu: Fix srcu_struct node grpmask overflow on 64-bit systems (git-fixes)\n- srcu: Only accelerate on enqueue time (git-fixes)\n- stackdepot: rename pool_index to pool_index_plus_1 (git-fixes).\n- stackdepot: respect __GFP_NOLOCKDEP allocation flag (git-fixes).\n- staging: iio: ad9832: Correct phase range check (git-fixes).\n- staging: iio: ad9834: Correct phase range check (git-fixes).\n- staging: media: imx: fix OF node leak in imx_media_add_of_subdevs() (git-fixes).\n- staging: media: max96712: fix kernel oops when removing module (git-fixes).\n- sunrpc: clear XPRT_SOCK_UPD_TIMEOUT when reset transport (git-fixes).\n- sunrpc: fix one UAF issue caused by sunrpc kernel tcp socket (git-fixes).\n- sunrpc: handle -ENOTCONN in xs_tcp_setup_socket() (git-fixes).\n- supported.conf: Add support for v4l2-dv-timings (jsc#PED-8645)\n- svcrdma: Address an integer overflow (git-fixes).\n- svcrdma: fix miss destroy percpu_counter in svc_rdma_proc_init() (git-fixes).\n- swiotlb: Enforce page alignment in swiotlb_alloc() (git-fixes).\n- swiotlb: Reinstate page-alignment for mappings \u003e= PAGE_SIZE (git-fixes).\n- thermal/drivers/qcom/tsens-v1: Add support for MSM8937 tsens (stable-fixes).\n- thermal: of: fix OF node leak in of_thermal_zone_find() (git-fixes).\n- thunderbolt: Add support for Intel Lunar Lake (stable-fixes).\n- thunderbolt: Add support for Intel Panther Lake-M/P (stable-fixes).\n- tipc: fix NULL deref in cleanup_bearer() (bsc#1235433).\n- tools: Sync if_xdp.h uapi tooling header (git-fixes).\n- tools: hv: change permissions of NetworkManager configuration file (git-fixes).\n- tpm/eventlog: Limit memory allocations for event logs with excessive size (bsc#1233260 bsc#1233259 bsc#1232421).\n- tpm: Map the ACPI provided event log (bsc#1233260 bsc#1233259 bsc#1232421).\n- tpm_tis_spi: Release chip select when flow control fails (bsc#1234338)\n- tty: serial: 8250: Fix another runtime PM usage counter underflow (git-fixes).\n- tty: serial: kgdboc: Fix 8250_* kgdb over serial (git-fixes).\n- types: Introduce [us]128 (bsc#1220773).\n- ubifs: Correct the total block count by deducting journal reservation (git-fixes).\n- ubifs: authentication: Fix use-after-free in ubifs_tnc_end_commit (git-fixes).\n- ubifs: skip dumping tnc tree when zroot is null (git-fixes).\n- udf: Fix lock ordering in udf_evict_inode() (bsc#1234238).\n- udf: fix uninit-value use in udf_get_fileshortad (bsc#1234243).\n- udf: prevent integer overflow in udf_bitmap_free_blocks() (bsc#1234239).\n- udf: refactor inode_bmap() to handle error (bsc#1234242).\n- udf: refactor udf_current_aext() to handle error (bsc#1234240).\n- udf: refactor udf_next_aext() to handle error (bsc#1234241).\n- udf: udftime: prevent overflow in udf_disk_stamp_to_time() (bsc#1234237).\n- uio: Fix return value of poll (git-fixes).\n- uio: uio_dmem_genirq: check the return value of devm_kasprintf() (git-fixes).\n- usb-storage: Add max sectors quirk for Nokia 208 (stable-fixes).\n- usb: add support for new USB device ID 0x17EF:0x3098 for the r8152 driver (stable-fixes).\n- usb: cdns3-ti: Add workaround for Errata i2409 (stable-fixes).\n- usb: cdns3: Add quirk flag to enable suspend residency (stable-fixes).\n- usb: chipidea: add CI_HDRC_FORCE_VBUS_ACTIVE_ALWAYS flag (stable-fixes).\n- usb: chipidea: udc: handle USB Error Interrupt if IOC not set (stable-fixes).\n- usb: dwc2: Fix HCD port connection race (git-fixes).\n- usb: dwc2: Fix HCD resume (git-fixes).\n- usb: dwc2: gadget: Do not write invalid mapped sg entries into dma_desc with iommu enabled (stable-fixes).\n- usb: dwc2: hcd: Fix GetPortStatus \u0026 SetPortFeature (git-fixes).\n- usb: dwc3-am62: Disable autosuspend during remove (git-fixes).\n- usb: dwc3-am62: Fix an OF node leak in phy_syscon_pll_refclk() (git-fixes).\n- usb: dwc3: ep0: Do not clear ep0 DWC3_EP_TRANSFER_STARTED (git-fixes).\n- usb: dwc3: ep0: Do not reset resource alloc flag (git-fixes).\n- usb: dwc3: ep0: Do not reset resource alloc flag (including ep0) (git-fixes).\n- usb: dwc3: gadget: Rewrite endpoint allocation flow (stable-fixes).\n- usb: dwc3: gadget: fix writing NYET threshold (git-fixes).\n- usb: dwc3: xilinx: make sure pipe clock is deselected in usb2 only mode (git-fixes).\n- usb: ehci-hcd: fix call balance of clocks handling routines (git-fixes).\n- usb: fix reference leak in usb_new_device() (git-fixes).\n- usb: gadget: configfs: Ignore trailing LF for user strings to cdev (git-fixes).\n- usb: gadget: f_fs: Remove WARN_ON in functionfs_bind (git-fixes).\n- usb: gadget: f_tcm: Decrement command ref count on cleanup (git-fixes).\n- usb: gadget: f_tcm: Do not free command immediately (git-fixes).\n- usb: gadget: f_tcm: Do not prepare BOT write request twice (git-fixes).\n- usb: gadget: f_tcm: Fix Get/SetInterface return value (git-fixes).\n- usb: gadget: f_tcm: Translate error to sense (git-fixes).\n- usb: gadget: f_tcm: ep_autoconfig with fullspeed endpoint (git-fixes).\n- usb: gadget: f_uac2: Fix incorrect setting of bNumEndpoints (git-fixes).\n- usb: gadget: u_serial: Disable ep before setting port to null to fix the crash caused by port being null (git-fixes).\n- usb: gadget: u_serial: Fix the issue that gs_start_io crashed due to accessing null pointer (git-fixes).\n- usb: host: max3421-hcd: Correctly abort a USB request (git-fixes).\n- usb: host: xhci-plat: Assign shared_hcd-\u003ersrc_start (git-fixes).\n- usb: typec: anx7411: fix OF node reference leaks in anx7411_typec_switch_probe() (git-fixes).\n- usb: typec: anx7411: fix fwnode_handle reference leak (git-fixes).\n- usb: typec: fix pm usage counter imbalance in ucsi_ccg_sync_control() (bsc#1235001)\n- usb: typec: tcpm/tcpci_maxim: fix error code in max_contaminant_read_resistance_kohm() (git-fixes).\n- usb: typec: tcpm: set SRC_SEND_CAPABILITIES timeout to PD_T_SENDER_RESPONSE (git-fixes).\n- usb: typec: use cleanup facility for 'altmodes_node' (stable-fixes).\n- usbnet: ipheth: break up NCM header size computation (git-fixes).\n- usbnet: ipheth: check that DPE points past NCM header (git-fixes).\n- usbnet: ipheth: fix DPE OoB read (git-fixes).\n- usbnet: ipheth: fix possible overflow in DPE length check (git-fixes).\n- usbnet: ipheth: refactor NCM datagram loop (git-fixes).\n- usbnet: ipheth: use static NDP16 location in URB (git-fixes).\n- vDPA/ifcvf: Fix pci_read_config_byte() return code handling (git-fixes).\n- vdpa/mlx5: Fix PA offset with unaligned starting iotlb map (git-fixes).\n- vdpa/mlx5: Fix suboptimal range on iotlb iteration (git-fixes).\n- vdpa: solidrun: Fix UB bug with devres (git-fixes).\n- vfs: fix readahead(2) on block devices (bsc#1234201).\n- vmscan,migrate: fix page count imbalance on node stats when demoting pages (git-fixes).\n- watchdog: rzg2l_wdt: Power on the watchdog domain in the restart handler (stable-fixes).\n- watchdog: rzg2l_wdt: Rely on the reset driver for doing proper reset (stable-fixes).\n- watchdog: rzg2l_wdt: Remove reset de-assert from probe (stable-fixes).\n- wifi: ath11k: Fix unexpected return buffer manager error for WCN6750/WCN6855 (git-fixes).\n- wifi: ath11k: cleanup struct ath11k_mon_data (git-fixes).\n- wifi: ath12k: fix atomic calls in ath12k_mac_op_set_bitrate_mask() (stable-fixes).\n- wifi: ath12k: fix tx power, max reg power update to firmware (git-fixes).\n- wifi: ath5k: add PCI ID for Arcadyan devices (git-fixes).\n- wifi: ath5k: add PCI ID for SX76X (git-fixes).\n- wifi: brcmfmac: Fix oops due to NULL pointer dereference in brcmf_sdiod_sglist_rw() (stable-fixes).\n- wifi: brcmfmac: add missing header include for brcmf_dbg (git-fixes).\n- wifi: cfg80211: adjust allocation of colocated AP data (git-fixes).\n- wifi: cfg80211: sme: init n_channels before channels[] access (git-fixes).\n- wifi: cw1200: Fix potential NULL dereference (git-fixes).\n- wifi: ipw2x00: libipw_rx_any(): fix bad alignment (stable-fixes).\n- wifi: iwlwifi: fw: read STEP table from correct UEFI var (git-fixes).\n- wifi: iwlwifi: mvm: Use the sync timepoint API in suspend (stable-fixes).\n- wifi: mac80211: Add non-atomic station iterator (stable-fixes).\n- wifi: mac80211: Fix common size calculation for ML element (git-fixes).\n- wifi: mac80211: clean up 'ret' in sta_link_apply_parameters() (stable-fixes).\n- wifi: mac80211: do not flush non-uploaded STAs (git-fixes).\n- wifi: mac80211: export ieee80211_purge_tx_queue() for drivers (stable-fixes).\n- wifi: mac80211: fix mbss changed flags corruption on 32 bit systems (stable-fixes).\n- wifi: mac80211: fix station NSS capability initialization order (git-fixes).\n- wifi: mac80211: fix tid removal during mesh forwarding (git-fixes).\n- wifi: mac80211: init cnt before accessing elem in ieee80211_copy_mbssid_beacon (git-fixes).\n- wifi: mac80211: prohibit deactivating all links (git-fixes).\n- wifi: mac80211: wake the queues in case of failure in resume (stable-fixes).\n- wifi: mt76: mt76u_vendor_request: Do not print error messages when -EPROTO (git-fixes).\n- wifi: mt76: mt7915: Fix mesh scan on MT7916 DBDC (git-fixes).\n- wifi: mt76: mt7915: add module param to select 5 GHz or 6 GHz on MT7916 (git-fixes).\n- wifi: mt76: mt7915: firmware restart on devices with a second pcie link (git-fixes).\n- wifi: mt76: mt7915: fix overflows seen when writing limit attributes (git-fixes).\n- wifi: mt76: mt7915: fix register mapping (git-fixes).\n- wifi: mt76: mt7921: fix using incorrect group cipher after disconnection (git-fixes).\n- wifi: mt76: mt7925: fix off by one in mt7925_load_clc() (git-fixes).\n- wifi: mt76: mt7996: add max mpdu len capability (git-fixes).\n- wifi: mt76: mt7996: fix HE Phy capability (git-fixes).\n- wifi: mt76: mt7996: fix definition of tx descriptor (git-fixes).\n- wifi: mt76: mt7996: fix incorrect indexing of MIB FW event (git-fixes).\n- wifi: mt76: mt7996: fix ldpc setting (git-fixes).\n- wifi: mt76: mt7996: fix overflows seen when writing limit attributes (git-fixes).\n- wifi: mt76: mt7996: fix register mapping (git-fixes).\n- wifi: mt76: mt7996: fix rx filter setting for bfee functionality (git-fixes).\n- wifi: mt76: mt7996: fix the capability of reception of EHT MU PPDU (git-fixes).\n- wifi: nl80211: fix NL80211_ATTR_MLO_LINK_ID off-by-one (git-fixes).\n- wifi: rtlwifi: Drastically reduce the attempts to read efuse in case of failures (stable-fixes).\n- wifi: rtlwifi: destroy workqueue at rtl_deinit_core (git-fixes).\n- wifi: rtlwifi: do not complete firmware loading needlessly (git-fixes).\n- wifi: rtlwifi: fix init_sw_vars leak when probe fails (git-fixes).\n- wifi: rtlwifi: fix memory leaks and invalid access at probe error path (git-fixes).\n- wifi: rtlwifi: pci: wait for firmware loading before releasing memory (git-fixes).\n- wifi: rtlwifi: remove unused check_buddy_priv (git-fixes).\n- wifi: rtlwifi: rtl8192se: rise completion of firmware loading as last step (git-fixes).\n- wifi: rtlwifi: rtl8821ae: Fix media status report (git-fixes).\n- wifi: rtlwifi: rtl8821ae: phy: restore removed code to fix infinite loop (git-fixes).\n- wifi: rtlwifi: usb: fix workqueue leak when probe fails (git-fixes).\n- wifi: rtlwifi: wait for firmware loading before releasing memory (git-fixes).\n- wifi: rtw88: use ieee80211_purge_tx_queue() to purge TX skb (stable-fixes).\n- wifi: rtw89: check return value of ieee80211_probereq_get() for RNR (stable-fixes).\n- wifi: rtw89: mcc: consider time limits not divisible by 1024 (git-fixes).\n- wifi: wcn36xx: fix channel survey memory allocation size (git-fixes).\n- wifi: wlcore: fix unbalanced pm_runtime calls (git-fixes).\n- workqueue: Add rcu lock check at the end of work item execution (bsc#1236732).\n- workqueue: Do not warn when cancelling WQ_MEM_RECLAIM work from !WQ_MEM_RECLAIM worker (bsc#1235416).\n- writeback, cgroup: switch inodes with dirty timestamps to release dying cgwbs (bsc#1234203).\n- x86,amd_iommu: Replace cmpxchg_double() (bsc#1220773).\n- x86,intel_iommu: Replace cmpxchg_double() (bsc#1220773).\n- x86/hyperv: Fix hv tsc page based sched_clock for hibernation (git-fixes).\n- x86/static-call: Remove early_boot_irqs_disabled check to fix Xen PVH dom0 (git-fixes).\n- xfs: Add error handling for xfs_reflink_cancel_cow_range (git-fixes).\n- xfs: Propagate errors from xfs_reflink_cancel_cow_range in xfs_dax_write_iomap_end (git-fixes).\n- xfs: do not allocate COW extents when unsharing a hole (git-fixes).\n- xfs: fix sb_spino_align checks for large fsblock sizes (git-fixes).\n- xfs: remove unknown compat feature check in superblock write validation (git-fixes).\n- xfs: return from xfs_symlink_verify early on V4 filesystems (git-fixes).\n- xfs: sb_spino_align is not verified (git-fixes).\n- xhci: Add usb cold attach (CAS) as a reason to resume root hub (git-fixes).\n- xhci: Allow RPM on the USB controller (1022:43f7) by default (stable-fixes).\n- xhci: fix possible null pointer deref during xhci urb enqueue (git-fixes).\n","status":"published","published":"2025-03-28T07:51:47Z","modified":"2026-03-23T04:50:04.890383Z","updated_at":"2026-11-02T15:53:59.381172Z"},{"id":"SUSE-SU-2025:20248-1","title":"Security update for the Linux Kernel","description":"\n\nThe SUSE Linux Enterprise Micro 6.0 and 6.1 kernel was updated to receive various security bugfixes.\n\nThe following security bugs were fixed:\n\n- CVE-2024-26924: scsi: lpfc: Release hbalock before calling lpfc_worker_wake_up() (bsc#1225820).\n- CVE-2024-27397: netfilter: nf_tables: use timestamp to check for set element timeout (bsc#1224095).\n- CVE-2024-35839: kABI fix for netfilter: bridge: replace physindev with physinif in nf_bridge_info (bsc#1224726).\n- CVE-2024-41042: Prefer nft_chain_validate (bsc#1228526).\n- CVE-2024-44934: net: bridge: mcast: wait for previous gc cycles when removing port (bsc#1229809).\n- CVE-2024-44996: vsock: fix recursive -\u003erecvmsg calls (bsc#1230205).\n- CVE-2024-45828: i3c: mipi-i3c-hci: Mask ring interrupts before ring stop request (bsc#1235705).\n- CVE-2024-47678: icmp: change the order of rate limits (bsc#1231854).\n- CVE-2024-48881: bcache: revert replacing IS_ERR_OR_NULL with IS_ERR again (bsc#1235727).\n- CVE-2024-49948: net: add more sanity checks to qdisc_pkt_len_init() (bsc#1232161).\n- CVE-2024-49951: Bluetooth: MGMT: Fix possible crash on mgmt_index_removed (bsc#1232158).\n- CVE-2024-49978: gso: fix udp gso fraglist segmentation after pull from frag_list (bsc#1232101).\n- CVE-2024-49998: net: dsa: improve shutdown sequence (bsc#1232087).\n- CVE-2024-50018: net: napi: Prevent overflow of napi_defer_hard_irqs (bsc#1232419).\n- CVE-2024-50039: kABI: Restore deleted EXPORT_SYMBOL(__qdisc_calculate_pkt_len) (bsc#1231909).\n- CVE-2024-50143: udf: fix uninit-value use in udf_get_fileshortad (bsc#1233038).\n- CVE-2024-50151: smb: client: fix OOBs when building SMB2_IOCTL request (bsc#1233055).\n- CVE-2024-50199: mm/swapfile: skip HugeTLB pages for unuse_vma (bsc#1233112).\n- CVE-2024-50202: nilfs2: propagate directory read errors from nilfs_find_entry() (bsc#1233324).\n- CVE-2024-50256: netfilter: nf_reject_ipv6: fix potential crash in nf_send_reset6() (bsc#1233200).\n- CVE-2024-50262: bpf: Fix out-of-bounds write in trie_get_next_key() (bsc#1233239).\n- CVE-2024-50278, CVE-2024-50280: dm cache: fix flushing uninitialized\n  delayed_work on cache_ctr error (bsc#1233467 bsc#1233469).\n- CVE-2024-50278: dm cache: fix potential out-of-bounds access on the first resume (bsc#1233467).\n- CVE-2024-50299: sctp: properly validate chunk size in sctp_sf_ootb() (bsc#1233488).\n- CVE-2024-53050: drm/i915/hdcp: Add encoder check in hdcp2_get_capability (bsc#1233546).\n- CVE-2024-53064: idpf: fix idpf_vc_core_init error path (bsc#1233558 bsc#1234464).\n- CVE-2024-53090: afs: Fix lock recursion (bsc#1233637).\n- CVE-2024-53091: bpf: Add sk_is_inet and IS_ICSK check in tls_sw_has_ctx_tx/rx (bsc#1233638).\n- CVE-2024-53099: bpf: Check validity of link-\u003etype in bpf_link_show_fdinfo() (bsc#1233772).\n- CVE-2024-53105: mm: page_alloc: move mlocked flag clearance into free_pages_prepare() (bsc#1234069).\n- CVE-2024-53111: mm/mremap: fix address wraparound in move_page_tables() (bsc#1234086).\n- CVE-2024-53113: mm: fix NULL pointer dereference in alloc_pages_bulk_noprof (bsc#1234077).\n- CVE-2024-53117: virtio/vsock: Improve MSG_ZEROCOPY error handling (bsc#1234079).\n- CVE-2024-53118: vsock: Fix sk_error_queue memory leak (bsc#1234071).\n- CVE-2024-53119: virtio/vsock: Fix accept_queue memory leak (bsc#1234073).\n- CVE-2024-53122: mptcp: cope racing subflow creation in mptcp_rcv_space_adjust (bsc#1234076).\n- CVE-2024-53125: bpf: sync_linked_regs() must preserve subreg_def (bsc#1234156).\n- CVE-2024-53130: nilfs2: fix null-ptr-deref in block_dirty_buffer tracepoint (bsc#1234219).\n- CVE-2024-53131: nilfs2: fix null-ptr-deref in block_touch_buffer tracepoint (bsc#1234220).\n- CVE-2024-53133: drm/amd/display: Handle dml allocation failure to avoid crash (bsc#1234221)\n- CVE-2024-53134: pmdomain: imx93-blk-ctrl: correct remove path (bsc#1234159).\n- CVE-2024-53141: netfilter: ipset: add missing range check in bitmap_ip_uadt (bsc#1234381).\n- CVE-2024-53160: rcu/kvfree: Fix data-race in __mod_timer / kvfree_call_rcu (bsc#1234810).\n- CVE-2024-53161: EDAC/bluefield: Fix potential integer overflow (bsc#1234856).\n- CVE-2024-53164: net: sched: fix ordering of qlen adjustment (bsc#1234863).\n- CVE-2024-53170: block: fix uaf for flush rq while iterating tags (bsc#1234888).\n- CVE-2024-53172: ubi: fastmap: Fix duplicate slab cache names while attaching (bsc#1234898).\n- CVE-2024-53175: ipc: fix memleak if msg_init_ns failed in create_ipc_ns (bsc#1234893).\n- CVE-2024-53179: smb: client: fix use-after-free of signing key (bsc#1234921).\n- CVE-2024-53185: smb: client: fix NULL ptr deref in crypto_aead_setkey() (bsc#1234901).\n- CVE-2024-53187: io_uring: check for overflows in io_pin_pages (bsc#1234947).\n- CVE-2024-53195: KVM: arm64: Get rid of userspace_irqchip_in_use (bsc#1234957).\n- CVE-2024-53196: KVM: arm64: Do not retire aborted MMIO instruction (bsc#1234906).\n- CVE-2024-53198: xen: Fix the issue of resource not being properly released in xenbus_dev_probe() (bsc#1234923).\n- CVE-2024-53203: usb: typec: fix potential array underflow in ucsi_ccg_sync_control() (bsc#1235001).\n- CVE-2024-53214: vfio/pci: Properly hide first-in-list PCIe extended capability (bsc#1235004).\n- CVE-2024-53216: nfsd: fix UAF when access ex_uuid or ex_stats (bsc#1235003).\n- CVE-2024-53222: zram: fix NULL pointer in comp_algorithm_show() (bsc#1234974).\n- CVE-2024-53227: scsi: bfa: Fix use-after-free in bfad_im_module_exit() (bsc#1235011).\n- CVE-2024-53232: iommu/s390: Implement blocking domain (bsc#1235050).\n- CVE-2024-53234: erofs: handle NONHEAD !delta[1] lclusters gracefully (bsc#1235045).\n- CVE-2024-53236: xsk: Free skb when TX metadata options are invalid (bsc#1235000).\n- CVE-2024-53240: xen/netfront: fix crash when removing device (bsc#1234281).\n- CVE-2024-53241: x86/xen: use new hypercall functions instead of hypercall page (XSA-466 bsc#1234282).\n- CVE-2024-53685: ceph: give up on paths longer than PATH_MAX (bsc#1235720).\n- CVE-2024-55639: net: renesas: rswitch: avoid use-after-put for a device tree node (bsc#1235737).\n- CVE-2024-55881: KVM: x86: Play nice with protected guests in complete_hypercall_exit() (bsc#1235745).\n- CVE-2024-56372: net: tun: fix tun_napi_alloc_frags() (bsc#1235753).\n- CVE-2024-56549: cachefiles: Fix NULL pointer dereference in object-\u003efile (bsc#1234912).\n- CVE-2024-56566: mm/slub: Avoid list corruption when removing a slab from the full list (bsc#1235033).\n- CVE-2024-56568: iommu/arm-smmu: Defer probe of clients after smmu device bound (bsc#1235032).\n- CVE-2024-56569: ftrace: Fix regression with module command in stack_trace_filter (bsc#1235031).\n- CVE-2024-56570: ovl: Filter invalid inodes with missing lookup function (bsc#1235035).\n- CVE-2024-56582: btrfs: fix use-after-free in btrfs_encoded_read_endio() (bsc#1235128).\n- CVE-2024-56588: scsi: hisi_sas: Create all dump files during debugfs initialization (bsc#1235123).\n- CVE-2024-56589: scsi: hisi_sas: Add cond_resched() for no forced preemption model (bsc#1235241).\n- CVE-2024-56599: wifi: ath10k: avoid NULL pointer error during sdio remove (bsc#1235138).\n- CVE-2024-56600: net: inet6: do not leave a dangling sk pointer in inet6_create() (bsc#1235217).\n- CVE-2024-56601: net: inet: do not leave a dangling sk pointer in inet_create() (bsc#1235230).\n- CVE-2024-56602: net: ieee802154: do not leave a dangling sk pointer in ieee802154_create() (bsc#1235521).\n- CVE-2024-56603: net: af_can: do not leave a dangling sk pointer in can_create() (bsc#1235415).\n- CVE-2024-56604: Bluetooth: RFCOMM: avoid leaving dangling sk pointer in rfcomm_sock_alloc() (bsc#1235056).\n- CVE-2024-56608: drm/amd/display: Fix out-of-bounds access in 'dcn21_link_encoder_create' (bsc#1235487).\n- CVE-2024-56610: kcsan: Turn report_filterlist_lock into a raw_spinlock (bsc#1235390).\n- CVE-2024-56611: mm/mempolicy: fix migrate_to_node() assuming there is at least one VMA in a MM (bsc#1235391).\n- CVE-2024-56614: xsk: fix OOB map writes when deleting elements (bsc#1235424).\n- CVE-2024-56615: bpf: fix OOB devmap writes when deleting elements (bsc#1235426).\n- CVE-2024-56617: cacheinfo: Allocate memory during CPU hotplug if not done from the primary CPU (bsc#1235429).\n- CVE-2024-56620: scsi: ufs: qcom: Only free platform MSIs when ESI is enabled (bsc#1235227).\n- CVE-2024-56622: scsi: ufs: core: sysfs: Prevent div by zero (bsc#1235251).\n- CVE-2024-56631: scsi: sg: Fix slab-use-after-free read in sg_release() (bsc#1235480).\n- CVE-2024-56635: net: avoid potential UAF in default_operstate() (bsc#1235519).\n- CVE-2024-56636: geneve: do not assume mac header is set in geneve_xmit_skb() (bsc#1235520).\n- CVE-2024-56637: netfilter: ipset: Hold module reference while requesting a module (bsc#1235523).\n- CVE-2024-56641: net/smc: initialize close_work early to avoid warning (bsc#1235526).\n- CVE-2024-56643: dccp: Fix memory leak in dccp_feat_change_recv (bsc#1235132).\n- CVE-2024-56648: net: hsr: avoid potential out-of-bound access in fill_frame_info() (bsc#1235451).\n- CVE-2024-56649: net: enetc: Do not configure preemptible TCs if SIs do not support (bsc#1235449).\n- CVE-2024-56650: netfilter: x_tables: fix LED ID check in led_tg_check() (bsc#1235430).\n- CVE-2024-56656: bnxt_en: Fix aggregation ID mask to prevent oops on 5760X chips (bsc#1235444).\n- CVE-2024-56659: net: lapb: increase LAPB_HEADER_LEN (bsc#1235439).\n- CVE-2024-56660: net/mlx5: DR, prevent potential error pointer dereference (bsc#1235437).\n- CVE-2024-56664: bpf, sockmap: Fix race between element replace and close() (bsc#1235249).\n- CVE-2024-56665: bpf,perf: Fix invalid prog_array access in perf_event_detach_bpf_prog (bsc#1235489).\n- CVE-2024-56675: bpf: Fix UAF via mismatching bpf_prog/attachment RCU flavors (bsc#1235555).\n- CVE-2024-56679: octeontx2-pf: handle otx2_mbox_get_rsp errors in otx2_common.c (bsc#1235498).\n- CVE-2024-56693: brd: defer automatic disk creation until module initialization succeeds (bsc#1235418).\n- CVE-2024-56694: bpf: fix recursive lock when verdict program return SK_PASS (bsc#1235412).\n- CVE-2024-56704: 9p/xen: fix release of IRQ (bsc#1235584).\n- CVE-2024-56707: octeontx2-pf: handle otx2_mbox_get_rsp errors in otx2_dmac_flt.c (bsc#1235545).\n- CVE-2024-56708: EDAC/igen6: Avoid segmentation fault on module unload (bsc#1235564).\n- CVE-2024-56712: udmabuf: fix memory leak on last export_udmabuf() error path (bsc#1235565).\n- CVE-2024-56715: ionic: Fix netdev notifier unregister on failure (bsc#1235612).\n- CVE-2024-56716: netdevsim: prevent bad user input in nsim_dev_health_break_write() (bsc#1235587).\n- CVE-2024-56725: octeontx2-pf: handle otx2_mbox_get_rsp errors in otx2_dcbnl.c (bsc#1235578).\n- CVE-2024-56726: octeontx2-pf: handle otx2_mbox_get_rsp errors in cn10k.c (bsc#1235582).\n- CVE-2024-56727: octeontx2-pf: handle otx2_mbox_get_rsp errors in otx2_flows.c (bsc#1235583).\n- CVE-2024-56728: octeontx2-pf: handle otx2_mbox_get_rsp errors in otx2_ethtool.c (bsc#1235656).\n- CVE-2024-56729: smb: Initialize cfid-\u003etcon before performing network ops (bsc#1235503).\n- CVE-2024-56747: scsi: qedi: Fix a possible memory leak in qedi_alloc_and_init_sb() (bsc#1234934).\n- CVE-2024-56748: scsi: qedf: Fix a possible memory leak in qedf_alloc_and_init_sb() (bsc#1235627).\n- CVE-2024-56755: netfs/fscache: Add a memory barrier for FSCACHE_VOLUME_CREATING (bsc#1234920).\n- CVE-2024-56759: btrfs: fix use-after-free when COWing tree bock and tracing is enabled (bsc#1235645).\n- CVE-2024-56763: tracing: Prevent bad count for tracing_cpumask_write (bsc#1235638).\n- CVE-2024-56774: btrfs: add a sanity check for btrfs root in btrfs_search_slot() (bsc#1235653).\n- CVE-2024-56775: drm/amd/display: Fix handling of plane refcount (bsc#1235657).\n- CVE-2024-57791: net/smc: check return value of sock_recvmsg when draining clc data (bsc#1235759).\n- CVE-2024-57793: virt: tdx-guest: Just leak decrypted memory on unrecoverable errors (bsc#1235768).\n- CVE-2024-57795: RDMA/rxe: Remove the direct link to net_device (bsc#1235906).\n- CVE-2024-57801: net/mlx5e: Skip restore TC rules for vport rep without loaded flag (bsc#1235940).\n- CVE-2024-57802: netrom: check buffer length before accessing it (bsc#1235941).\n- CVE-2024-57804: scsi: mpi3mr: Fix corrupt config pages PHY state is switched in sysfs (bsc#1235779).\n- CVE-2024-57809: PCI: imx6: Fix suspend/resume support on i.MX6QDL (bsc#1235793).\n- CVE-2024-57838: s390/entry: Mark IRQ entries to fix stack depot warnings (bsc#1235798).\n- CVE-2024-57857: RDMA/siw: Remove direct link to net_device (bsc#1235946).\n- CVE-2024-57884: mm: vmscan: account for free pages to prevent infinite Loop in throttle_direct_reclaim() (bsc#1235948).\n- CVE-2024-57892: ocfs2: fix slab-use-after-free due to dangling pointer dqi_priv (bsc#1235964).\n- CVE-2024-57896: btrfs: flush delalloc workers queue before stopping cleaner kthread during unmount (bsc#1235965).\n- CVE-2024-57903: net: restrict SO_REUSEPORT to inet sockets (bsc#1235967).\n- CVE-2024-57917: topology: Keep the cpumask unchanged when printing cpumap (bsc#1236127).\n- CVE-2024-57929: dm array: fix releasing a faulty array block twice in dm_array_cursor_end (bsc#1236096).\n- CVE-2024-57931: selinux: ignore unknown extended permissions (bsc#1236192).\n- CVE-2024-57932: gve: guard XDP xmit NDO on existence of xdp queues (bsc#1236190).\n- CVE-2024-57933: gve: guard XSK operations on the existence of queues (bsc#1236178).\n- CVE-2024-57938: net/sctp: Prevent autoclose integer overflow in sctp_association_init() (bsc#1236182).\n- CVE-2024-57946: virtio-blk: do not keep queue frozen during system suspend (bsc#1236247).\n- CVE-2025-21632: x86/fpu: Ensure shadow stack is active before \"getting\" registers (bsc#1236106).\n- CVE-2025-21649: net: hns3: fix kernel crash when 1588 is sent on HIP08 devices (bsc#1236143).\n- CVE-2025-21650: net: hns3: fixed hclge_fetch_pf_reg accesses bar space out of bounds issue (bsc#1236144).\n- CVE-2025-21651: net: hns3: do not auto enable misc vector (bsc#1236145).\n- CVE-2025-21652: ipvlan: Fix use-after-free in ipvlan_get_iflink() (bsc#1236160).\n- CVE-2025-21653: net_sched: cls_flow: validate TCA_FLOW_RSHIFT attribute (bsc#1236161).\n- CVE-2025-21655: io_uring/eventfd: ensure io_eventfd_signal() defers another RCU period (bsc#1236163).\n- CVE-2025-21662: net/mlx5: Fix variable not being completed when function returns (bsc#1236198).\n- CVE-2025-21663: net: stmmac: dwmac-tegra: Read iommu stream id from device tree (bsc#1236260).\n- CVE-2025-21664: dm thin: make get_first_thin use rcu-safe list first function (bsc#1236262).\n- CVE-2025-21674: net/mlx5e: Fix inversion dependency warning while enabling IPsec tunnel (bsc#1236688).\n- CVE-2025-21676: net: fec: handle page_pool_dev_alloc_pages error (bsc#1236696).\n- CVE-2025-21682: eth: bnxt: always recalculate features after XDP clearing, fix null-deref (bsc#1236703).\n\nThe following non-security bugs were fixed:\n\n- 9p: v9fs_fid_find: also lookup by inode if not found dentry (git-fixes).\n- ACPI/HMAT: Move HMAT messages to pr_debug() (bsc#1234294)\n- ACPI/IORT: Add PMCG platform information for HiSilicon HIP09A (stable-fixes).\n- ACPI/IORT: Add PMCG platform information for HiSilicon HIP10/11 (stable-fixes).\n- ACPI: PCC: Add PCC shared memory region command and status bitfields (stable-fixes).\n- ACPI: PRM: Add PRM handler direct call support (jsc#PED-10467).\n- ACPI: fan: cleanup resources in the error path of .probe() (git-fixes).\n- ACPI: resource: Add Asus Vivobook X1504VAP to irq1_level_low_skip_override[] (stable-fixes).\n- ACPI: resource: Add TongFang GM5HG0A to irq1_edge_low_force_override[] (stable-fixes).\n- ACPI: resource: Fix memory resource type union access (git-fixes).\n- ACPI: resource: acpi_dev_irq_override(): Check DMI match last (stable-fixes).\n- ACPI: x86: Add skip i2c clients quirk for Acer Iconia One 8 A1-840 (stable-fixes).\n- ACPI: x86: Clean up Asus entries in acpi_quirk_skip_dmi_ids[] (stable-fixes).\n- ACPI: x86: Make UART skip quirks work on PCI UARTs without an UID (stable-fixes).\n- ACPICA: events/evxfregn: do not release the ContextMutex that was never acquired (git-fixes).\n- ALSA hda/realtek: Add quirk for Framework F111:000C (stable-fixes).\n- ALSA: hda/hdmi: Yet more pin fix for HP EliteDesk 800 G4 (stable-fixes).\n- ALSA: hda/realtek - Add support for ASUS Zen AIO 27 Z272SD_A272SD audio (stable-fixes).\n- ALSA: hda/realtek - Fixed headphone distorted sound on Acer Aspire A115-31 laptop (git-fixes).\n- ALSA: hda/realtek: Add Framework Laptop 13 (Intel Core Ultra) to quirks (stable-fixes).\n- ALSA: hda/realtek: Add new alc2xx-fixup-headset-mic model (stable-fixes).\n- ALSA: hda/realtek: Add support for Ayaneo System using CS35L41 HDA (stable-fixes).\n- ALSA: hda/realtek: Add support for Galaxy Book2 Pro (NP950XEE) (stable-fixes).\n- ALSA: hda/realtek: Enable Mute LED on HP Laptop 14s-fq1xxx (stable-fixes).\n- ALSA: hda/realtek: Enable headset mic on Positivo C6400 (stable-fixes).\n- ALSA: hda/realtek: Fix headset mic on Acer Nitro 5 (stable-fixes).\n- ALSA: hda/realtek: Workaround for resume on Dell Venue 11 Pro 7130 (bsc#1235686).\n- ALSA: hda: Add HP MP9 G4 Retail System AMS to force connect list (stable-fixes).\n- ALSA: hda: Fix headset detection failure due to unstable sort (git-fixes).\n- ALSA: line6: Fix racy access to midibuf (stable-fixes).\n- ALSA: seq: Check UMP support for midi_version change (git-fixes).\n- ALSA: seq: oss: Fix races at processing SysEx messages (stable-fixes).\n- ALSA: seq: ump: Fix seq port updates per FB info notify (git-fixes).\n- ALSA: seq: ump: Use automatic cleanup of kfree() (stable-fixes).\n- ALSA: seq: ump: Use guard() for locking (stable-fixes).\n- ALSA: ump: Use guard() for locking (stable-fixes).\n- ALSA: usb-audio: Add delay quirk for USB Audio Device (stable-fixes).\n- ALSA: usb-audio: Add delay quirk for iBasso DC07 Pro (stable-fixes).\n- ALSA: usb-audio: Add implicit feedback quirk for Yamaha THR5 (stable-fixes).\n- ALSA: usb-audio: Notify xrun for low-latency mode (git-fixes).\n- ALSA: usb-audio: Re-add ScratchAmp quirk entries (git-fixes).\n- ALSA: usb-audio: US16x08: Initialize array before use (git-fixes).\n- ASoC: Intel: avs: Fix theoretical infinite loop (git-fixes).\n- ASoC: Intel: sof_sdw: add quirk for Dell SKU 0B8C (stable-fixes).\n- ASoC: Intel: sof_sdw: fix jack detection on ADL-N variant RVP (stable-fixes).\n- ASoC: SOF: Remove libraries from topology lookups (git-fixes).\n- ASoC: acp: Support microphone from Lenovo Go S (stable-fixes).\n- ASoC: amd: yc: Add a quirk for microfone on Lenovo ThinkPad P14s Gen 5 21MES00B00 (stable-fixes).\n- ASoC: amd: yc: Add quirk for microphone on Lenovo Thinkpad T14s Gen 6 21M1CTO1WW (stable-fixes).\n- ASoC: amd: yc: Fix the wrong return value (git-fixes).\n- ASoC: amd: yc: Support mic on HP 14-em0002la (stable-fixes).\n- ASoC: amd: yc: Support mic on Lenovo Thinkpad E14 Gen 6 (stable-fixes).\n- ASoC: amd: yc: fix internal mic on Redmi G 2022 (stable-fixes).\n- ASoC: codecs: wcd938x-sdw: Correct Soundwire ports mask (git-fixes).\n- ASoC: codecs: wsa881x: Correct Soundwire ports mask (git-fixes).\n- ASoC: codecs: wsa883x: Correct Soundwire ports mask (git-fixes).\n- ASoC: codecs: wsa884x: Correct Soundwire ports mask (git-fixes).\n- ASoC: cs35l56: Handle OTP read latency over SoundWire (stable-fixes).\n- ASoC: cs35l56: Patch CS35L56_IRQ1_MASK_18 to the default value (stable-fixes).\n- ASoC: fsl_micfil: Expand the range of FIFO watermark mask (stable-fixes).\n- ASoC: hdmi-codec: reorder channel allocation list (stable-fixes).\n- ASoC: mediatek: disable buffer pre-allocation (stable-fixes).\n- ASoC: meson: axg-fifo: fix irq scheduling issue with PREEMPT_RT (git-fixes).\n- ASoC: nau8822: Lower debug print priority (stable-fixes).\n- ASoC: rockchip: i2s_tdm: Re-add the set_sysclk callback (git-fixes).\n- ASoC: rt722: add delay time to wait for the calibration procedure (stable-fixes).\n- ASoC: samsung: Add missing depends on I2C (git-fixes).\n- ASoC: samsung: Add missing selects for MFD_WM8994 (stable-fixes).\n- ASoC: sun4i-spdif: Add clock multiplier settings (git-fixes).\n- ASoC: wm8994: Add depends on MFD core (stable-fixes).\n- Bluetooth: Add support ITTIM PE50-M75C (stable-fixes).\n- Bluetooth: Fix type of len in rfcomm_sock_getsockopt{,_old}() (stable-fixes).\n- Bluetooth: ISO: Reassociate a socket with an active BIS (stable-fixes).\n- Bluetooth: L2CAP: accept zero as a special value for MTU auto-selection (git-fixes).\n- Bluetooth: L2CAP: do not leave dangling sk pointer on error in l2cap_sock_create() (stable-fixes).\n- Bluetooth: L2CAP: handle NULL sock pointer in l2cap_sock_alloc (git-fixes).\n- Bluetooth: MGMT: Fix Add Device to responding before completing (git-fixes).\n- Bluetooth: MGMT: Fix possible deadlocks (git-fixes).\n- Bluetooth: SCO: Add support for 16 bits transparent voice setting (git-fixes).\n- Bluetooth: btnxpuart: Fix driver sending truncated data (git-fixes).\n- Bluetooth: btnxpuart: Fix glitches seen in dual A2DP streaming (git-fixes).\n- Bluetooth: btusb: Add RTL8852BE device 0489:e123 to device tables (stable-fixes).\n- Bluetooth: btusb: Add USB HW IDs for MT7921/MT7922/MT7925 (stable-fixes).\n- Bluetooth: btusb: Add new VID/PID 0489/e111 for MT7925 (stable-fixes).\n- Bluetooth: btusb: Add new VID/PID 13d3/3602 for MT7925 (stable-fixes).\n- Bluetooth: btusb: add callback function in btusb suspend/resume (stable-fixes).\n- Bluetooth: btusb: mediatek: add callback function in btusb_disconnect (stable-fixes).\n- Bluetooth: hci_core: Fix not checking skb length on hci_acldata_packet (stable-fixes).\n- Bluetooth: hci_event: Fix using rcu_read_(un)lock while iterating (git-fixes).\n- Bluetooth: hci_sync: Fix not setting Random Address when required (git-fixes).\n- Bluetooth: iso: Fix recursive locking warning (git-fixes).\n- Delete XHCI patch for regression (bsc#1235550)\n- Disable ceph (jsc#PED-7242)\n- Documentation: PM: Clarify pm_runtime_resume_and_get() return value (git-fixes).\n- Drivers: hv: util: Avoid accessing a ringbuffer not initialized yet (git-fixes).\n- Drop downstream TPM fix patch (bsc#1233260 bsc#1233259 bsc#1232421)\n- Drop uvcvideo fix due to regression (bsc#1235894)\n- EDAC/{i10nm,skx,skx_common}: Support UV systems (bsc#1234693).\n- HID: core: Fix assumption that Resolution Multipliers must be in Logical Collections (git-fixes).\n- HID: fix generic desktop D-Pad controls (git-fixes).\n- HID: hid-sensor-hub: do not use stale platform-data on remove (git-fixes).\n- HID: hid-thrustmaster: Fix warning in thrustmaster_probe by adding endpoint check (git-fixes).\n- HID: magicmouse: Apple Magic Trackpad 2 USB-C driver support (stable-fixes).\n- HID: multitouch: fix support for Goodix PID 0x01e9 (git-fixes).\n- Input: atkbd - map F23 key to support default copilot shortcut (stable-fixes).\n- Input: bbnsm_pwrkey - add remove hook (git-fixes).\n- Input: bbnsm_pwrkey - fix missed key press after suspend (git-fixes).\n- Input: davinci-keyscan - remove leftover header (git-fixes).\n- Input: xpad - add QH Electronics VID/PID (stable-fixes).\n- Input: xpad - add support for Nacon Evol-X Xbox One Controller (stable-fixes).\n- Input: xpad - add support for Nacon Pro Compact (stable-fixes).\n- Input: xpad - add support for wooting two he (arm) (stable-fixes).\n- Input: xpad - add unofficial Xbox 360 wireless receiver clone (stable-fixes).\n- Input: xpad - improve name of 8BitDo controller 2dc8:3106 (stable-fixes).\n- KVM: SVM: Allow guest writes to set MSR_AMD64_DE_CFG bits (bsc#1234635).\n- KVM: s390: Reject KVM_SET_GSI_ROUTING on ucontrol VMs (git-fixes bsc#1235776).\n- KVM: s390: Reject setting flic pfault attributes on ucontrol VMs (git-fixes bsc#1235777).\n- KVM: s390: vsie: fix virtual/physical address in unpin_scb() (git-fixes bsc#1235778).\n- NFC: nci: Add bounds checking in nci_hci_create_pipe() (git-fixes).\n- NFS/pnfs: Fix a live lock between recalled layouts and layoutget (git-fixes).\n- NFSD: Async COPY result needs to return a write verifier (git-fixes).\n- NFSD: Cap the number of bytes copied by nfs4_reset_recoverydir() (git-fixes).\n- NFSD: Fix nfsd4_shutdown_copy() (git-fixes).\n- NFSD: Prevent NULL dereference in nfsd4_process_cb_update() (git-fixes).\n- NFSD: Prevent a potential integer overflow (git-fixes).\n- NFSD: Remove a never-true comparison (git-fixes).\n- NFSD: initialize copy-\u003ecp_clp early in nfsd4_copy for use by trace point (git-fixes).\n- NFSv4.0: Fix a use-after-free problem in the asynchronous open() (git-fixes).\n- NFSv4.2: fix COPY_NOTIFY xdr buf size calculation (git-fixes).\n- NFSv4.2: mark OFFLOAD_CANCEL MOVEABLE (git-fixes).\n- Octeontx2-pf: Free send queue buffers incase of leaf to inner (git-fixes).\n- PCI/AER: Disable AER service on suspend (stable-fixes).\n- PCI/MSI: Handle lack of irqdomain gracefully (git-fixes).\n- PCI: Add 'reset_subordinate' to reset hierarchy below bridge (stable-fixes).\n- PCI: Add ACS quirk for Broadcom BCM5760X NIC (stable-fixes).\n- PCI: Add ACS quirk for Wangxun FF5xxx NICs (stable-fixes).\n- PCI: Add T_PERST_CLK_US macro (git-fixes).\n- PCI: Avoid putting some root ports into D3 on TUXEDO Sirius Gen1 (git-fixes).\n- PCI: Detect and trust built-in Thunderbolt chips (stable-fixes).\n- PCI: Fix use-after-free of slot-\u003ebus on hot remove (stable-fixes).\n- PCI: Use preserve_config in place of pci_flags (stable-fixes).\n- PCI: cadence: Extract link setup sequence from cdns_pcie_host_setup() (stable-fixes).\n- PCI: cadence: Set cdns_pcie_host_init() global (stable-fixes).\n- PCI: cpqphp: Use PCI_POSSIBLE_ERROR() to check config reads (stable-fixes).\n- PCI: dwc: Always stop link in the dw_pcie_suspend_noirq (git-fixes).\n- PCI: dwc: ep: Prevent changing BAR size/flags in pci_epc_set_bar() (git-fixes).\n- PCI: dwc: ep: Write BAR_MASK before iATU registers in pci_epc_set_bar() (git-fixes).\n- PCI: endpoint: Destroy the EPC device in devm_pci_epc_destroy() (git-fixes).\n- PCI: endpoint: Finish virtual EP removal in pci_epf_remove_vepf() (git-fixes).\n- PCI: endpoint: pci-epf-test: Fix check for DMA MEMCPY test (git-fixes).\n- PCI: endpoint: pci-epf-test: Set dma_chan_rx pointer to NULL on error (git-fixes).\n- PCI: imx6: Deassert apps_reset in imx_pcie_deassert_core_reset() (git-fixes).\n- PCI: imx6: Skip controller_id generation logic for i.MX7D (git-fixes).\n- PCI: j721e: Add PCIe 4x lane selection support (stable-fixes).\n- PCI: j721e: Add per platform maximum lane settings (stable-fixes).\n- PCI: j721e: Add reset GPIO to struct j721e_pcie (stable-fixes).\n- PCI: j721e: Add suspend and resume support (git-fixes).\n- PCI: j721e: Use T_PERST_CLK_US macro (git-fixes).\n- PCI: microchip: Set inbound address translation for coherent or non-coherent mode (git-fixes).\n- PCI: qcom: Add support for IPQ9574 (stable-fixes).\n- PCI: rcar-ep: Fix incorrect variable used when calling devm_request_mem_region() (git-fixes).\n- PCI: vmd: Add DID 8086:B06F and 8086:B60B for Intel client SKUs (stable-fixes).\n- PCI: vmd: Set devices to D0 before enabling PM L1 Substates (stable-fixes).\n- PM: hibernate: Add error handling for syscore_suspend() (git-fixes).\n- RAS/AMD/ATL: Translate normalized to system physical addresses using PRM (jsc#PED-10467).\n- RDMA/bnxt_re: Add check for path mtu in modify_qp (git-fixes)\n- RDMA/bnxt_re: Add send queue size check for variable wqe (git-fixes)\n- RDMA/bnxt_re: Avoid initializing the software queue for user queues (git-fixes)\n- RDMA/bnxt_re: Avoid sending the modify QP workaround for latest adapters (git-fixes)\n- RDMA/bnxt_re: Disable use of reserved wqes (git-fixes)\n- RDMA/bnxt_re: Fix MSN table size for variable wqe mode (git-fixes)\n- RDMA/bnxt_re: Fix max SGEs for the Work Request (git-fixes)\n- RDMA/bnxt_re: Fix max_qp_wrs reported (git-fixes)\n- RDMA/bnxt_re: Fix reporting hw_ver in query_device (git-fixes)\n- RDMA/bnxt_re: Fix the check for 9060 condition (git-fixes)\n- RDMA/bnxt_re: Fix the locking while accessing the QP table (git-fixes)\n- RDMA/bnxt_re: Fix the max WQE size for static WQE support (git-fixes)\n- RDMA/bnxt_re: Fix the max WQEs used in Static WQE mode (git-fixes)\n- RDMA/bnxt_re: Fix to drop reference to the mmap entry in case of error (git-fixes)\n- RDMA/bnxt_re: Fix to export port num to ib_query_qp (git-fixes)\n- RDMA/bnxt_re: Remove always true dattr validity check (git-fixes)\n- RDMA/core: Fix ENODEV error for iWARP test over vlan (git-fixes)\n- RDMA/hns: Fix accessing invalid dip_ctx during destroying QP (git-fixes)\n- RDMA/hns: Fix mapping error of zero-hop WQE buffer (git-fixes)\n- RDMA/hns: Fix missing flush CQE for DWQE (git-fixes)\n- RDMA/hns: Fix warning storm caused by invalid input in IO path (git-fixes)\n- RDMA/mlx4: Avoid false error about access to uninitialized gids array (git-fixes)\n- RDMA/mlx5: Enforce same type port association for multiport RoCE (git-fixes)\n- RDMA/mlx5: Fix a race for an ODP MR which leads to CQE with error (git-fixes)\n- RDMA/mlx5: Fix implicit ODP use after free (git-fixes)\n- RDMA/mlx5: Fix indirect mkey ODP page count (git-fixes)\n- RDMA/rtrs: Ensure 'ib_sge list' is accessible (git-fixes)\n- RDMA/rxe: Fix mismatched max_msg_sz (git-fixes)\n- RDMA/rxe: Fix the warning \"__rxe_cleanup+0x12c/0x170 [rdma_rxe]\" (git-fixes)\n- RDMA/srp: Fix error handling in srp_add_port (git-fixes)\n- RDMA/uverbs: Prevent integer overflow issue (git-fixes)\n- Revert \"HID: multitouch: Add support for lenovo Y9000P Touchpad\" (stable-fixes).\n- Revert \"block/mq-deadline: use correct way to throttling write requests\" (bsc#1234146).\n- Revert \"btrfs: fix use-after-free waiting for encoded read endios (bsc#1235128)\"\n- Revert \"drm/i915/dpt: Make DPT object unshrinkable\" (stable-fixes).\n- Revert \"igb: Disable threaded IRQ for igb_msix_other\" (git-fixes).\n- Revert \"mm, kmsan: fix infinite recursion due to RCU critical section\" (bsc#1230413)\n- Revert \"mm/sparsemem: fix race in accessing memory_section-\u003eusage\" (bsc#1230413)\n- Revert \"mm: prevent derefencing NULL ptr in pfn_section_valid()\" (bsc#1230413)\n- Revert \"mtd: spi-nor: core: replace dummy buswidth from addr to data\" (git-fixes).\n- Revert \"unicode: Do not special case ignorable code points\" (stable-fixes).\n- Revert \"usb: gadget: u_serial: Disable ep before setting port to null\n  to fix the crash caused by port being null\" (stable-fixes).\n- Revert 'arm64: Kconfig: Make SME depend on BROKEN for now' \n- Revert 0dd78566990 (\"Disable ceph (jsc#PED-7242)\") \n- SUNRPC: make sure cache entry active before cache_show (git-fixes).\n- SUNRPC: timeout and cancel TLS handshake with -ETIMEDOUT (git-fixes).\n- USB: core: Disable LPM only for non-suspended ports (git-fixes).\n- USB: serial: cp210x: add Phoenix Contact UPS Device (stable-fixes).\n- USB: serial: option: add MediaTek T7XX compositions (stable-fixes).\n- USB: serial: option: add MeiG Smart SLM770A (stable-fixes).\n- USB: serial: option: add MeiG Smart SRM815 (stable-fixes).\n- USB: serial: option: add Neoway N723-EA support (stable-fixes).\n- USB: serial: option: add Netprisma LCUK54 modules for WWAN Ready (stable-fixes).\n- USB: serial: option: add TCL IK512 MBIM \u0026 ECM (stable-fixes).\n- USB: serial: option: add Telit FE910C04 rmnet compositions (stable-fixes).\n- USB: serial: quatech2: fix null-ptr-deref in qt2_process_read_urb() (git-fixes).\n- USB: usblp: return error when setting unsupported protocol (git-fixes).\n- VFS: use system_unbound_wq for delayed_mntput (bsc#1234683).\n- VMCI: fix reference to ioctl-number.rst (git-fixes).\n- accel/habanalabs/gaudi2: unsecure tpc count registers (stable-fixes).\n- accel/habanalabs: export dma-buf only if size/offset multiples of PAGE_SIZE (stable-fixes).\n- accel/habanalabs: fix debugfs files permissions (stable-fixes).\n- accel/habanalabs: increase HL_MAX_STR to 64 bytes to avoid warnings (stable-fixes).\n- acpi: nfit: vmalloc-out-of-bounds Read in acpi_nfit_ctl (git-fixes).\n- af_unix: Call manage_oob() for every skb in unix_stream_read_generic() (bsc#1234725).\n- afs: Automatically generate trace tag enums (git-fixes).\n- afs: Fix EEXIST error returned from afs_rmdir() to be ENOTEMPTY (git-fixes).\n- afs: Fix cleanup of immediately failed async calls (git-fixes).\n- afs: Fix directory format encoding struct (git-fixes).\n- afs: Fix missing subdir edit when renamed between parent dirs (git-fixes).\n- afs: Fix the fallback handling for the YFS.RemoveFile2 RPC call (git-fixes).\n- afs: Fix the maximum cell name length (git-fixes).\n- amdgpu/uvd: get ring reference from rq scheduler (git-fixes).\n- arch: Introduce arch_{,try_}_cmpxchg128{,_local}() (bsc#1220773).\n- arch: Remove cmpxchg_double (bsc#1220773).\n- arch: consolidate arch_irq_work_raise prototypes (git-fixes).\n- arm64/sme: Move storage of reg_smidr to __cpuinfo_store_cpu() (git-fixes)\n- arm64: Ensure bits ASID[15:8] are masked out when the kernel uses (bsc#1234605)\n- arm64: Filter out SVE hwcaps when FEAT_SVE isn't implemented (git-fixes)\n- arm64: Force position-independent veneers (git-fixes).\n- arm64: Kconfig: Make SME depend on BROKEN for now (git-fixes bsc#1236245)\n- arm64: dts: imx8mp: correct sdhc ipg clk (git-fixes).\n- arm64: dts: rockchip: Add sdmmc/sdio/emmc reset controls for RK3328 (git-fixes)\n- arm64: dts: rockchip: add hevc power domain clock to rk3328 (git-fixes).\n- arm64: dts: rockchip: increase gmac rx_delay on rk3399-puma (git-fixes)\n- arm64: ptrace: fix partial SETREGSET for NT_ARM_TAGGED_ADDR_CTRL (git-fixes).\n- arm64: tegra: Disable Tegra234 sce-fabric node (git-fixes)\n- arm64: tegra: Fix Tegra234 PCIe interrupt-map (git-fixes)\n- arm64: tegra: Fix typo in Tegra234 dce-fabric compatible (git-fixes)\n- ata: libata-core: Set ATA_QCFLAG_RTF_FILLED in fill_result_tf() (stable-fixes).\n- autofs: fix memory leak of waitqueues in autofs_catatonic_mode (git-fixes).\n- batman-adv: Do not let TT changes list grows indefinitely (git-fixes).\n- batman-adv: Do not send uninitialized TT changes (git-fixes).\n- batman-adv: Remove uninitialized data in full table TT response (git-fixes).\n- blk-cgroup: Fix UAF in blkcg_unpin_online() (bsc#1234726).\n- blk-core: use pr_warn_ratelimited() in bio_check_ro() (bsc#1234139).\n- blk-iocost: Fix an UBSAN shift-out-of-bounds warning (bsc#1234144).\n- blk-iocost: do not WARN if iocg was already offlined (bsc#1234147).\n- blk-throttle: fix lockdep warning of \"cgroup_mutex or RCU read lock required!\" (bsc#1234140).\n- block, bfq: choose the last bfqq from merge chain in bfq_setup_cooperator() (bsc#1234149).\n- block, bfq: do not break merge chain in bfq_split_bfqq() (bsc#1234150).\n- block, bfq: fix bfqq uaf in bfq_limit_depth() (bsc#1234160).\n- block, bfq: fix procress reference leakage for bfqq in merge chain (bsc#1234280).\n- block, bfq: fix uaf for accessing waker_bfqq after splitting (bsc#1234279).\n- block/mq-deadline: Fix the tag reservation code (bsc#1234148).\n- block: Call .limit_depth() after .hctx has been set (bsc#1234148).\n- block: Fix where bio IO priority gets set (bsc#1234145).\n- block: prevent an integer overflow in bvec_try_merge_hw_page (bsc#1234142).\n- block: update the stable_writes flag in bdev_add (bsc#1234141).\n- bnxt_en: Fix GSO type for HW GRO packets on 5750X chips (git-fixes)\n- bnxt_en: Fix receive ring space parameters when XDP is active (git-fixes).\n- bnxt_en: Reserve rings after PCIe AER recovery if NIC interface is down (git-fixes).\n- bnxt_en: Set backplane link modes correctly for ethtool (git-fixes).\n- bpf, x86: Fix PROBE_MEM runtime load check (git-fixes).\n- bpf: verifier: prevent userspace memory access (git-fixes).\n- btrfs: fix use-after-free in btrfs_encoded_read_endio() (bsc#1235445).\n- btrfs: fix use-after-free waiting for encoded read endios (bsc#1235128)\n- btrfs: fix use-after-free waiting for encoded read endios (bsc#1235445).\n- bus: mhi: host: Free mhi_buf vector inside mhi_alloc_bhie_table() (git-fixes).\n- can: gs_usb: add VID/PID for Xylanta SAINT3 product family (stable-fixes).\n- can: j1939: fix error in J1939 documentation (stable-fixes).\n- ceph: improve error handling and short/overflow-read logic in __ceph_sync_read() (bsc#1228592).\n- checkpatch: always parse orig_commit in fixes tag (git-fixes).\n- checkpatch: check for missing Fixes tags (stable-fixes).\n- cleanup: Add conditional guard support (stable-fixes).\n- cleanup: Adjust scoped_guard() macros to avoid potential warning (stable-fixes).\n- cleanup: Remove address space of returned pointer (git-fixes).\n- clocksource/drivers/timer-ti-dm: Fix child node refcount handling (git-fixes).\n- clocksource/drivers:sp804: Make user selectable (git-fixes).\n- counter: stm32-timer-cnt: Add check for clk_enable() (git-fixes).\n- counter: ti-ecap-capture: Add check for clk_enable() (git-fixes).\n- cpufreq: ACPI: Fix max-frequency computation (git-fixes).\n- cpufreq: Do not unregister cpufreq cooling on CPU hotplug (git-fixes).\n- cpufreq: amd-pstate: remove global header file (git-fixes).\n- cpufreq: intel_pstate: Check turbo_is_disabled() in store_no_turbo() (bsc#1234619).\n- cpufreq: intel_pstate: Do not update global.turbo_disabled after initialization (bsc#1234619).\n- cpufreq: intel_pstate: Drop redundant locking from intel_pstate_driver_cleanup() (bsc#1234619).\n- cpufreq: intel_pstate: Fix unchecked HWP MSR access (bsc#1234619).\n- cpufreq: intel_pstate: Fold intel_pstate_max_within_limits() into caller (bsc#1234619).\n- cpufreq: intel_pstate: Get rid of unnecessary READ_ONCE() annotations (bsc#1234619).\n- cpufreq: intel_pstate: Make hwp_notify_lock a raw spinlock (git-fixes).\n- cpufreq: intel_pstate: Read global.no_turbo under READ_ONCE() (bsc#1234619).\n- cpufreq: intel_pstate: Rearrange show_no_turbo() and store_no_turbo() (bsc#1234619).\n- cpufreq: intel_pstate: Refine computation of P-state for given frequency (bsc#1234619).\n- cpufreq: intel_pstate: Replace three global.turbo_disabled checks (bsc#1234619).\n- cpufreq: intel_pstate: Revise global turbo disable check (bsc#1234619).\n- cpufreq: intel_pstate: Simplify spinlock locking (bsc#1234619).\n- cpufreq: intel_pstate: Update the maximum CPU frequency consistently (bsc#1234619).\n- cpufreq: intel_pstate: Use HWP to initialize ITMT if CPPC is missing (git-fixes).\n- cpufreq: intel_pstate: Use __ro_after_init for three variables (bsc#1234619).\n- cpufreq: intel_pstate: Wait for canceled delayed work to complete (bsc#1234619).\n- cpufreq: intel_pstate: fix pstate limits enforcement for adjust_perf call back (git-fixes).\n- cpuidle: Avoid potential overflow in integer multiplication (git-fixes).\n- cpupower: fix TSC MHz calculation (git-fixes).\n- crypto: caam - use JobR's space to access page 0 regs (git-fixes).\n- crypto: ecc - Prevent ecc_digits_from_bytes from reading too many bytes (git-fixes).\n- crypto: ecdsa - Avoid signed integer overflow on signature decoding (stable-fixes).\n- crypto: ecdsa - Convert byte arrays with key coordinates to digits (stable-fixes).\n- crypto: ecdsa - Rename keylen to bufsize where necessary (stable-fixes).\n- crypto: ecdsa - Use ecc_digits_from_bytes to convert signature (stable-fixes).\n- crypto: iaa - Fix IAA disabling that occurs when sync_mode is set to 'async' (git-fixes).\n- crypto: ixp4xx - fix OF node reference leaks in init_ixp_crypto() (git-fixes).\n- crypto: qat - disable IOV in adf_dev_stop() (git-fixes).\n- crypto: qce - fix goto jump in error path (git-fixes).\n- crypto: qce - fix priority to be less than ARMv8 CE (git-fixes).\n- crypto: qce - unregister previously registered algos in error path (git-fixes).\n- crypto: x86/sha256 - Add parentheses around macros' single arguments (stable-fixes).\n- cyrpto/b128ops: Remove struct u128 (bsc#1220773).\n- devcoredump: cleanup some comments (git-fixes).\n- devlink: Fix length of eswitch inline-mode (git-fixes).\n- dlm: fix possible lkb_resource null dereference (git-fixes).\n- dma-buf: fix dma_fence_array_signaled v4 (stable-fixes).\n- dma-debug: fix a possible deadlock on radix_lock (stable-fixes).\n- dmaengine: apple-admac: Avoid accessing registers in probe (git-fixes).\n- dmaengine: at_xdmac: avoid null_prt_deref in at_xdmac_prep_dma_memset (git-fixes).\n- dmaengine: dw: Select only supported masters for ACPI devices (git-fixes).\n- dmaengine: idxd: Check for driver name match before sva user feature (bsc#1234357).\n- dmaengine: mv_xor: fix child node refcount handling in early exit (git-fixes).\n- dmaengine: tegra: Return correct DMA status when paused (git-fixes).\n- dmaengine: ti: edma: fix OF node reference leaks in edma_driver (git-fixes).\n- docs: media: update location of the media patches (stable-fixes).\n- docs: power: Fix footnote reference for Toshiba Satellite P10-554 (git-fixes).\n- driver core: Add FWLINK_FLAG_IGNORE to completely ignore a fwnode link (stable-fixes).\n- driver core: class: Fix wild pointer dereferences in API class_dev_iter_next() (git-fixes).\n- driver core: fw_devlink: Improve logs for cycle detection (stable-fixes).\n- driver core: fw_devlink: Stop trying to optimize cycle detection logic (git-fixes).\n- drivers/card_reader/rtsx_usb: Restore interrupt based detection (git-fixes).\n- drivers: net: ionic: add missed debugfs cleanup to ionic_probe() error path (git-fixes).\n- drm/amd/display: Add HDR workaround for specific eDP (stable-fixes).\n- drm/amd/display: Add NULL check for clk_mgr in dcn32_init_hw (stable-fixes).\n- drm/amd/display: Add check for granularity in dml ceil/floor helpers (stable-fixes).\n- drm/amd/display: Allow backlight to go below `AMDGPU_DM_DEFAULT_MIN_BACKLIGHT` (stable-fixes).\n- drm/amd/display: Avoid overflow assignment in link_dp_cts (stable-fixes).\n- drm/amd/display: Fix DSC-re-computing (stable-fixes).\n- drm/amd/display: Fix Synaptics Cascaded Panamera DSC Determination (stable-fixes).\n- drm/amd/display: Fix incorrect DSC recompute trigger (stable-fixes).\n- drm/amd/display: Revert Avoid overflow assignment (stable-fixes).\n- drm/amd/display: Use HW lock mgr for PSR1 (stable-fixes).\n- drm/amd/display: Use gpuvm_min_page_size_kbytes for DML2 surfaces (stable-fixes).\n- drm/amd/display: increase MAX_SURFACES to the value supported by hw (stable-fixes).\n- drm/amd/pm: Fix an error handling path in vega10_enable_se_edc_force_stall_config() (git-fixes).\n- drm/amd/pm: fix the high voltage issue after unload (stable-fixes).\n- drm/amd/pm: update current_socclk and current_uclk in gpu_metrics on smu v13.0.7 (stable-fixes).\n- drm/amdgpu/gfx10: use rlc safe mode for soft recovery (stable-fixes).\n- drm/amdgpu/gfx11: use rlc safe mode for soft recovery (stable-fixes).\n- drm/amdgpu/gfx9: properly handle error ints on all pipes (stable-fixes).\n- drm/amdgpu/gfx9: use rlc safe mode for soft recovery (stable-fixes).\n- drm/amdgpu/hdp5.2: do a posting read when flushing HDP (stable-fixes).\n- drm/amdgpu/pm: Remove gpu_od if it's an empty directory (stable-fixes).\n- drm/amdgpu/umsch: do not execute umsch test when GPU is in reset/suspend (stable-fixes).\n- drm/amdgpu/umsch: reinitialize write pointer in hw init (stable-fixes).\n- drm/amdgpu/vcn: reset fw_shared under SRIOV (git-fixes).\n- drm/amdgpu/vcn: reset fw_shared when VCPU buffers corrupted on vcn v4.0.3 (stable-fixes).\n- drm/amdgpu: Block MMR_READ IOCTL in reset (stable-fixes).\n- drm/amdgpu: Dereference the ATCS ACPI buffer (stable-fixes).\n- drm/amdgpu: Fix potential NULL pointer dereference in atomctrl_get_smc_sclk_range_table (git-fixes).\n- drm/amdgpu: add raven1 gfxoff quirk (stable-fixes).\n- drm/amdgpu: add smu 14.0.1 discovery support (stable-fixes).\n- drm/amdgpu: always sync the GFX pipe on ctx switch (stable-fixes).\n- drm/amdgpu: clear RB_OVERFLOW bit when enabling interrupts for vega20_ih (stable-fixes).\n- drm/amdgpu: differentiate external rev id for gfx 11.5.0 (stable-fixes).\n- drm/amdgpu: disallow multiple BO_HANDLES chunks in one submit (stable-fixes).\n- drm/amdgpu: do not access invalid sched (git-fixes).\n- drm/amdgpu: enable gfxoff quirk on HP 705G4 (stable-fixes).\n- drm/amdgpu: fix unchecked return value warning for amdgpu_gfx (stable-fixes).\n- drm/amdgpu: fix usage slab after free (stable-fixes).\n- drm/amdgpu: prevent BO_HANDLES error from being overwritten (git-fixes).\n- drm/amdgpu: refine error handling in amdgpu_ttm_tt_pin_userptr (stable-fixes).\n- drm/amdgpu: set the right AMDGPU sg segment limitation (stable-fixes).\n- drm/amdgpu: simplify return statement in amdgpu_ras_eeprom_init (git-fixes).\n- drm/amdgpu: skip amdgpu_device_cache_pci_state under sriov (stable-fixes).\n- drm/amdgpu: tear down ttm range manager for doorbell in amdgpu_ttm_fini() (git-fixes).\n- drm/amdkfd: Correct the migration DMA map direction (stable-fixes).\n- drm/amdkfd: Fix resource leak in criu restore queue (stable-fixes).\n- drm/amdkfd: Use device based logging for errors (stable-fixes).\n- drm/amdkfd: Use the correct wptr size (stable-fixes).\n- drm/amdkfd: fixed page fault when enable MES shader debugger (git-fixes).\n- drm/amdkfd: pause autosuspend when creating pdd (stable-fixes).\n- drm/bridge: adv7511_audio: Update Audio InfoFrame properly (git-fixes).\n- drm/bridge: it6505: Change definition of AUX_FIFO_MAX_SIZE (git-fixes).\n- drm/bridge: it6505: Enable module autoloading (stable-fixes).\n- drm/bridge: it6505: Fix inverted reset polarity (git-fixes).\n- drm/bridge: it6505: update usleep_range for RC circuit charge time (stable-fixes).\n- drm/display: Fix building with GCC 15 (stable-fixes).\n- drm/dp_mst: Ensure mst_primary pointer is valid in drm_dp_mst_handle_up_req() (stable-fixes).\n- drm/dp_mst: Fix MST sideband message body length check (stable-fixes).\n- drm/dp_mst: Fix resetting msg rx state after topology removal (git-fixes).\n- drm/dp_mst: Verify request type in the corresponding down message reply (stable-fixes).\n- drm/etnaviv: Fix page property being used for non writecombine buffers (git-fixes).\n- drm/etnaviv: flush shader L1 cache after user commandstream (stable-fixes).\n- drm/i915/dg1: Fix power gate sequence (git-fixes).\n- drm/i915/fb: Relax clear color alignment to 64 bytes (stable-fixes).\n- drm/i915: Fix NULL pointer dereference in capture_engine (git-fixes).\n- drm/i915: Fix memory leak by correcting cache object name in error handler (git-fixes).\n- drm/mcde: Enable module autoloading (stable-fixes).\n- drm/mediatek: Add return value check when reading DPCD (git-fixes).\n- drm/mediatek: Add support for 180-degree rotation in the display driver (git-fixes).\n- drm/mediatek: Fix YCbCr422 color format issue for DP (git-fixes).\n- drm/mediatek: Fix mode valid issue for dp (git-fixes).\n- drm/mediatek: Set private-\u003eall_drm_private[i]-\u003edrm to NULL if mtk_drm_bind returns err (git-fixes).\n- drm/mediatek: mtk_dsi: Add registers to pdata to fix MT8186/MT8188 (git-fixes).\n- drm/mediatek: stop selecting foreign drivers (git-fixes).\n- drm/modes: Avoid divide by zero harder in drm_mode_vrefresh() (stable-fixes).\n- drm/msm/dp: set safe_to_exit_level before printing it (git-fixes).\n- drm/msm/dpu: link DSPP_2/_3 blocks on SC8180X (git-fixes).\n- drm/msm/dpu: link DSPP_2/_3 blocks on SM8150 (git-fixes).\n- drm/msm/dpu: link DSPP_2/_3 blocks on SM8250 (git-fixes).\n- drm/msm/dpu: link DSPP_2/_3 blocks on SM8350 (git-fixes).\n- drm/msm/dpu: link DSPP_2/_3 blocks on SM8550 (git-fixes).\n- drm/msm: Check return value of of_dma_configure() (git-fixes).\n- drm/msm: do not clean up priv-\u003ekms prematurely (git-fixes).\n- drm/nouveau/gsp: Use the sg allocator for level 2 of radix3 (stable-fixes).\n- drm/panel: novatek-nt35950: fix return value check in nt35950_probe() (git-fixes).\n- drm/panel: simple: Add Microchip AC69T88A LVDS Display panel (stable-fixes).\n- drm/printer: Allow NULL data in devcoredump printer (stable-fixes).\n- drm/radeon/r100: Handle unknown family in r100_cp_init_microcode() (stable-fixes).\n- drm/radeon/r600_cs: Fix possible int overflow in r600_packet3_check() (stable-fixes).\n- drm/radeon: Fix spurious unplug event on radeon HDMI (git-fixes).\n- drm/radeon: add helper rdev_to_drm(rdev) (stable-fixes).\n- drm/radeon: change rdev-\u003eddev to rdev_to_drm(rdev) (stable-fixes).\n- drm/rcar-du: dsi: Fix PHY lock bit check (git-fixes).\n- drm/rockchip: cdn-dp: Use drm_connector_helper_hpd_irq_event() (git-fixes).\n- drm/rockchip: vop2: Check linear format for Cluster windows on rk3566/8 (git-fixes).\n- drm/rockchip: vop2: Fix cluster windows alpha ctrl regsiters offset (git-fixes).\n- drm/rockchip: vop2: Fix the mixer alpha setup for layer 0 (git-fixes).\n- drm/sched: memset() 'job' in drm_sched_job_init() (stable-fixes).\n- drm/tidss: Clear the interrupt status for interrupts being disabled (git-fixes).\n- drm/tidss: Fix issue in irq handling causing irq-flood issue (git-fixes).\n- drm/v3d: Assign job pointer to NULL before signaling the fence (git-fixes).\n- drm/v3d: Ensure job pointer is set to NULL after job completion (git-fixes).\n- drm/v3d: Stop active perfmon if it is being destroyed (git-fixes).\n- drm/vc4: hdmi: Avoid log spam for audio start failure (stable-fixes).\n- drm/vc4: hvs: Set AXI panic modes for the HVS (stable-fixes).\n- drm/vmwgfx: Add new keep_resv BO param (git-fixes).\n- drm: adv7511: Drop dsi single lane support (git-fixes).\n- drm: adv7511: Fix use-after-free in adv7533_attach_dsi() (git-fixes).\n- drm: panel-orientation-quirks: Add quirk for AYA NEO 2 model (stable-fixes).\n- drm: panel-orientation-quirks: Add quirk for AYA NEO Founder edition (stable-fixes).\n- drm: panel-orientation-quirks: Add quirk for AYA NEO GEEK (stable-fixes).\n- drm: panel-orientation-quirks: Make Lenovo Yoga Tab 3 X90F DMI match less strict (stable-fixes).\n- erofs: avoid debugging output for (de)compressed data (git-fixes).\n- exfat: ensure that ctime is updated whenever the mtime is (git-fixes).\n- exfat: fix the infinite loop in __exfat_free_cluster() (git-fixes).\n- exfat: fix the infinite loop in exfat_readdir() (git-fixes).\n- exfat: fix uninit-value in __exfat_get_dentry_set (git-fixes).\n- ext4: add a new helper to check if es must be kept (bsc#1234170).\n- ext4: add correct group descriptors and reserved GDT blocks to system zone (bsc#1234164).\n- ext4: add missed brelse in update_backups (bsc#1234171).\n- ext4: allow for the last group to be marked as trimmed (bsc#1234278).\n- ext4: avoid buffer_head leak in ext4_mark_inode_used() (bsc#1234191).\n- ext4: avoid excessive credit estimate in ext4_tmpfile() (bsc#1234180).\n- ext4: avoid negative min_clusters in find_group_orlov() (bsc#1234193).\n- ext4: avoid overlapping preallocations due to overflow (bsc#1234162).\n- ext4: avoid potential buffer_head leak in __ext4_new_inode() (bsc#1234192).\n- ext4: avoid writing unitialized memory to disk in EA inodes (bsc#1234187).\n- ext4: check the extent status again before inserting delalloc block (bsc#1234186).\n- ext4: clear EXT4_GROUP_INFO_WAS_TRIMMED_BIT even mount with discard (bsc#1234190).\n- ext4: convert to exclusive lock while inserting delalloc extents (bsc#1234178).\n- ext4: correct best extent lstart adjustment logic (bsc#1234179).\n- ext4: correct grp validation in ext4_mb_good_group (bsc#1234163).\n- ext4: correct return value of ext4_convert_meta_bg (bsc#1234172).\n- ext4: correct the hole length returned by ext4_map_blocks() (bsc#1234178).\n- ext4: correct the start block of counting reserved clusters (bsc#1234169).\n- ext4: do not let fstrim block system suspend (bsc#1234166).\n- ext4: do not trim the group with corrupted block bitmap (bsc#1234177).\n- ext4: factor out __es_alloc_extent() and __es_free_extent() (bsc#1234170).\n- ext4: factor out a common helper to query extent map (bsc#1234186).\n- ext4: fix inconsistent between segment fstrim and full fstrim (bsc#1234176).\n- ext4: fix incorrect tid assumption in __jbd2_log_wait_for_space() (bsc#1234188).\n- ext4: fix incorrect tid assumption in ext4_wait_for_tail_page_commit() (bsc#1234188).\n- ext4: fix incorrect tid assumption in jbd2_journal_shrink_checkpoint_list() (bsc#1234188).\n- ext4: fix memory leaks in ext4_fname_{setup_filename,prepare_lookup} (bsc#1214954).\n- ext4: fix potential unnitialized variable (bsc#1234183).\n- ext4: fix race between writepages and remount (bsc#1234168).\n- ext4: fix rec_len verify error (bsc#1234167).\n- ext4: fix slab-use-after-free in ext4_es_insert_extent() (bsc#1234170).\n- ext4: fix uninitialized variable in ext4_inlinedir_to_tree (bsc#1234185).\n- ext4: forbid commit inconsistent quota data when errors=remount-ro (bsc#1234178).\n- ext4: make ext4_es_insert_delayed_block() return void (bsc#1234170).\n- ext4: make ext4_es_insert_extent() return void (bsc#1234170).\n- ext4: make ext4_es_remove_extent() return void (bsc#1234170).\n- ext4: make ext4_zeroout_es() return void (bsc#1234170).\n- ext4: make sure allocate pending entry not fail (bsc#1234170).\n- ext4: mark buffer new if it is unwritten to avoid stale data exposure (bsc#1234175).\n- ext4: move 'ix' sanity check to corrent position (bsc#1234174).\n- ext4: move setting of trimmed bit into ext4_try_to_trim_range() (bsc#1234165).\n- ext4: nested locking for xattr inode (bsc#1234189).\n- ext4: propagate errors from ext4_find_extent() in ext4_insert_range() (bsc#1234194).\n- ext4: refactor ext4_da_map_blocks() (bsc#1234178).\n- ext4: remove gdb backup copy for meta bg in setup_new_flex_group_blocks (bsc#1234173).\n- ext4: remove the redundant folio_wait_stable() (bsc#1234184).\n- ext4: set the type of max_zeroout to unsigned int to avoid overflow (bsc#1234182).\n- ext4: set type of ac_groups_linear_remaining to __u32 to avoid overflow (bsc#1234181).\n- ext4: use pre-allocated es in __es_insert_extent() (bsc#1234170).\n- ext4: use pre-allocated es in __es_remove_extent() (bsc#1234170).\n- ext4: using nofail preallocation in ext4_es_insert_delayed_block() (bsc#1234170).\n- ext4: using nofail preallocation in ext4_es_insert_extent() (bsc#1234170).\n- ext4: using nofail preallocation in ext4_es_remove_extent() (bsc#1234170).\n- fbdev: omapfb: Fix an OF node leak in dss_of_port_get_parent_device() (git-fixes).\n- filemap: Fix bounds checking in filemap_read() (bsc#1234209).\n- filemap: add a per-mapping stable writes flag (bsc#1234141).\n- firmware: arm_scmi: Reject clear channel request on A2P (stable-fixes).\n- fs-writeback: do not requeue a clean inode having skipped pages (bsc#1234200).\n- fs/writeback: bail out if there is no more inodes for IO and queued once (bsc#1234207).\n- fsnotify: fix sending inotify event with unexpected filename (bsc#1234198).\n- genirq/cpuhotplug: Retry with cpu_online_mask when migration fails (git-fixes).\n- genirq/cpuhotplug: Skip suspended interrupts when restoring affinity (git-fixes).\n- genirq/irqdesc: Honor caller provided affinity in alloc_desc() (git-fixes).\n- genirq: Make handle_enforce_irqctx() unconditionally available (git-fixes).\n- genksyms: fix memory leak when the same symbol is added from source (git-fixes).\n- genksyms: fix memory leak when the same symbol is read from *.symref file (git-fixes).\n- gfs2: Truncate address space when flipping GFS2_DIF_JDATA flag (git-fixes).\n- gpio: grgpio: Add NULL check in grgpio_probe (git-fixes).\n- gpio: grgpio: use a helper variable to store the address of ofdev-\u003edev (stable-fixes).\n- gpio: mxc: remove dead code after switch to DT-only (git-fixes).\n- gpio: xilinx: Convert gpio_lock to raw spinlock (git-fixes).\n- hfsplus: do not query the device logical block size multiple times (git-fixes).\n- hvc/xen: fix console unplug (git-fixes).\n- hvc/xen: fix error path in xen_hvc_init() to always register frontend driver (git-fixes).\n- hvc/xen: fix event channel handling for secondary consoles (git-fixes).\n- hwmon: (drivetemp) Fix driver producing garbage data when SCSI errors occur (git-fixes).\n- hwmon: (drivetemp) Set scsi command timeout to 10s (stable-fixes).\n- hwmon: (nct6775) Add 665-ACE/600M-CL to ASUS WMI monitoring list (stable-fixes).\n- hwmon: (pmbus/core) clear faults after setting smbalert mask (git-fixes).\n- hwmon: (pmbus_core) Allow to hook PMBUS_SMBALERT_MASK (stable-fixes).\n- hwmon: (tmp513) Do not use \"proxy\" headers (stable-fixes).\n- hwmon: (tmp513) Fix Current Register value interpretation (git-fixes).\n- hwmon: (tmp513) Fix division of negative numbers (git-fixes).\n- hwmon: (tmp513) Fix interpretation of values of Shunt Voltage and Limit Registers (git-fixes).\n- hwmon: (tmp513) Fix interpretation of values of Temperature Result and Limit Registers (git-fixes).\n- hwmon: (tmp513) Simplify with dev_err_probe() (stable-fixes).\n- hwmon: (tmp513) Use SI constants from units.h (stable-fixes).\n- hyperv: Do not overlap the hvcall IO areas in get_vtl() (git-fixes).\n- i2c: core: fix reference leak in i2c_register_adapter() (git-fixes).\n- i2c: i801: Add support for Intel Arrow Lake-H (stable-fixes).\n- i2c: i801: Add support for Intel Panther Lake (stable-fixes).\n- i2c: imx: add imx7d compatible string for applying erratum ERR007805 (git-fixes).\n- i2c: microchip-core: actually use repeated sends (git-fixes).\n- i2c: microchip-core: fix \"ghost\" detections (git-fixes).\n- i2c: mux: demux-pinctrl: check initial mux selection, too (git-fixes).\n- i2c: pnx: Fix timeout in wait functions (git-fixes).\n- i2c: rcar: fix NACK handling when being a target (git-fixes).\n- i2c: riic: Always round-up when calculating bus period (git-fixes).\n- i2c: xgene-slimpro: Migrate to use generic PCC shmem related macros (stable-fixes).\n- i40e: Fix handling changed priv flags (git-fixes).\n- i915/guc: Accumulate active runtime on gt reset (git-fixes).\n- i915/guc: Ensure busyness counter increases motonically (git-fixes).\n- i915/guc: Reset engine utilization buffer before registration (git-fixes).\n- ibmvnic: Free any outstanding tx skbs during scrq reset (bsc#1226980).\n- ice: Unbind the workqueue (bsc#1234989)\n- ice: change q_index variable type to s16 to store -1 value (git-fixes).\n- ice: consistently use q_idx in ice_vc_cfg_qs_msg() (git-fixes).\n- ice: fix PHY Clock Recovery availability check (git-fixes).\n- idpf: add support for SW triggered interrupts (bsc#1235507).\n- idpf: enable WB_ON_ITR (bsc#1235507).\n- idpf: trigger SW interrupt when exiting wb_on_itr mode (bsc#1235507).\n- ieee802154: ca8210: Add missing check for kfifo_alloc() in ca8210_probe() (git-fixes).\n- igb: Fix potential invalid memory access in igb_init_module() (git-fixes).\n- iio: adc: ad7124: Disable all channels at probe time (git-fixes).\n- iio: adc: ad_sigma_delta: Handle CS assertion as intended in ad_sd_read_reg_raw() (git-fixes).\n- iio: adc: at91: call input_free_device() on allocated iio_dev (git-fixes).\n- iio: adc: rockchip_saradc: fix information leak in triggered buffer (git-fixes).\n- iio: adc: ti-ads124s08: Use gpiod_set_value_cansleep() (git-fixes).\n- iio: adc: ti-ads8688: fix information leak in triggered buffer (git-fixes).\n- iio: dummy: iio_simply_dummy_buffer: fix information leak in triggered buffer (git-fixes).\n- iio: gyro: fxas21002c: Fix missing data update in trigger handler (git-fixes).\n- iio: iio-mux: kzalloc instead of devm_kzalloc to ensure page alignment (git-fixes).\n- iio: imu: kmx61: fix information leak in triggered buffer (git-fixes).\n- iio: inkern: call iio_device_put() only on mapped devices (git-fixes).\n- iio: light: as73211: fix channel handling in only-color triggered buffer (git-fixes).\n- iio: light: vcnl4035: fix information leak in triggered buffer (git-fixes).\n- iio: magnetometer: yas530: use signed integer type for clamp limits (git-fixes).\n- iio: pressure: zpa2326: fix information leak in triggered buffer (git-fixes).\n- iio: test : check null return of kunit_kmalloc in iio_rescale_test_scale (git-fixes).\n- instrumentation: Wire up cmpxchg128() (bsc#1220773).\n- intel_th: core: fix kernel-doc warnings (git-fixes).\n- io_uring/rw: avoid punting to io-wq directly (git-fixes).\n- io_uring/tctx: work around xa_store() allocation error issue (git-fixes).\n- io_uring: Fix registered ring file refcount leak (git-fixes).\n- io_uring: always lock __io_cqring_overflow_flush (git-fixes).\n- io_uring: check if iowq is killed before queuing (git-fixes).\n- iommu/io-pgtable-arm: Fix stage-2 map/unmap for concatenated tables (git-fixes).\n- ipmi: ipmb: Add check devm_kasprintf() returned value (git-fixes).\n- ipmi: ssif_bmc: Fix new request loss when bmc ready for a response (git-fixes).\n- irqchip/gic-v3: Force propagation of the active state with a read-back (stable-fixes).\n- irqchip/gic: Correct declaration of *percpu_base pointer in union gic_base (stable-fixes).\n- irqflags: Explicitly ignore lockdep_hrtimer_exit() argument (git-fixes).\n- isofs: handle CDs with bad root inode but good Joliet root directory (bsc#1234199).\n- ixgbe: downgrade logging of unsupported VF API version to debug (git-fixes).\n- ixgbevf: stop attempting IPSEC offload on Mailbox API 1.5 (git-fixes).\n- jffs2: Fix rtime decompressor (git-fixes).\n- jffs2: Prevent rtime decompress memory corruption (git-fixes).\n- jffs2: fix use of uninitialized variable (git-fixes).\n- jfs: add a check to prevent array-index-out-of-bounds in dbAdjTree (git-fixes).\n- jfs: array-index-out-of-bounds fix in dtReadFirst (git-fixes).\n- jfs: fix array-index-out-of-bounds in jfs_readdir (git-fixes).\n- jfs: fix shift-out-of-bounds in dbSplit (git-fixes).\n- jfs: xattr: check invalid xattr size more strictly (git-fixes).\n- kABI workaround for struct auto_pin_cfg_item change (git-fixes).\n- kABI workaround for struct drm_dp_mst_topology_mgr (git-fixes).\n- kabi/severities: make vcap_find_actionfield PASS (bsc#1220773)\n- kasan: make report_lock a raw spinlock (git-fixes).\n- kconfig: fix file name in warnings when loading KCONFIG_DEFCONFIG_LIST (git-fixes).\n- kdb: Fix buffer overflow during tab-complete (bsc#1234652).\n- kdb: Fix console handling when editing and tab-completing commands (bsc#1234655).\n- kdb: Merge identical case statements in kdb_read() (bsc#1234657).\n- kdb: Use format-specifiers rather than memset() for padding in kdb_read() (bsc#1234658).\n- kdb: Use format-strings rather than '\\0' injection in kdb_read() (bsc#1234654).\n- kdb: Use the passed prompt in kdb_position_cursor() (bsc#1234654).\n- kdb: address -Wformat-security warnings (bsc#1234659).\n- kgdb: Flush console before entering kgdb on panic (bsc#1234651).\n- kheaders: Ignore silly-rename files (stable-fixes).\n- ktest.pl: Avoid false positives with grub2 skip regex (stable-fixes).\n- ktest.pl: Check kernelrelease return in get_version (git-fixes).\n- ktest.pl: Fix typo \"accesing\" (git-fixes).\n- ktest.pl: Fix typo in comment (git-fixes).\n- ktest.pl: Remove unused declarations in run_bisect_test function (git-fixes).\n- ktest: force $buildonly = 1 for 'make_warnings_file' test type (stable-fixes).\n- landlock: Handle weird files (git-fixes).\n- latencytop: use correct kernel-doc format for func params (git-fixes).\n- leds: class: Protect brightness_show() with led_cdev-\u003eled_access mutex (stable-fixes).\n- leds: lp8860: Write full EEPROM, not only half of it (git-fixes).\n- leds: netxbig: Fix an OF node reference leak in netxbig_leds_get_of_pdata() (git-fixes).\n- lib/inflate.c: remove dead code (git-fixes).\n- lib/stackdepot: print disabled message only if truly disabled (git-fixes).\n- linux/dmaengine.h: fix a few kernel-doc warnings (git-fixes).\n- locking/atomic/x86: Correct the definition of __arch_try_cmpxchg128() (bsc#1220773 git-fix).\n- loop: fix the the direct I/O support check when used on top of block devices (bsc#1234143).\n- mac80211: fix user-power when emulating chanctx (stable-fixes).\n- mac802154: check local interfaces before deleting sdata list (stable-fixes).\n- mailbox: pcc: Add support for platform notification handling (stable-fixes).\n- mailbox: pcc: Support shared interrupt for multiple subspaces (stable-fixes).\n- mailbox: tegra-hsp: Clear mailbox before using message (git-fixes).\n- maple_tree: simplify split calculation (git-fixes).\n- media: camif-core: Add check for clk_enable() (git-fixes).\n- media: ccs: Clean up parsed CCS static data on parse failure (git-fixes).\n- media: ccs: Fix CCS static data parsing for large block sizes (git-fixes).\n- media: ccs: Fix cleanup order in ccs_probe() (git-fixes).\n- media: cx231xx: Add support for Dexatek USB Video Grabber 1d19:6108 (stable-fixes).\n- media: dvb-frontends: dib3000mb: fix uninit-value in dib3000_write_reg (git-fixes).\n- media: dvb-usb-v2: af9035: fix ISO C90 compilation error on af9035_i2c_master_xfer (git-fixes).\n- media: i2c: imx412: Add missing newline to prints (git-fixes).\n- media: i2c: ov9282: Correct the exposure offset (git-fixes).\n- media: imx-jpeg: Fix potential error pointer dereference in detach_pm() (git-fixes).\n- media: imx296: Add standby delay during probe (git-fixes).\n- media: lmedm04: Handle errors for lme2510_int_read (git-fixes).\n- media: marvell: Add check for clk_enable() (git-fixes).\n- media: mc: fix endpoint iteration (git-fixes).\n- media: mipi-csis: Add check for clk_enable() (git-fixes).\n- media: nxp: imx8-isi: fix v4l2-compliance test errors (git-fixes).\n- media: ov5640: fix get_light_freq on auto (git-fixes).\n- media: rc: iguanair: handle timeouts (git-fixes).\n- media: rkisp1: Fix unused value issue (git-fixes).\n- media: uvcvideo: Add a quirk for the Kaiweets KTI-W02 infrared camera (stable-fixes).\n- media: uvcvideo: Fix crash during unbind if gpio unit is in use (git-fixes).\n- media: uvcvideo: Fix double free in error path (git-fixes).\n- media: uvcvideo: Fix event flags in uvc_ctrl_send_events (git-fixes).\n- media: uvcvideo: Force UVC version to 1.0a for 0408:4035 (stable-fixes).\n- media: uvcvideo: Only save async fh if success (git-fixes).\n- media: uvcvideo: Propagate buf-\u003eerror to userspace (git-fixes).\n- media: uvcvideo: RealSense D421 Depth module metadata (stable-fixes).\n- media: uvcvideo: Remove dangling pointers (git-fixes).\n- media: uvcvideo: Remove redundant NULL assignment (git-fixes).\n- media: uvcvideo: Support partial control reads (git-fixes).\n- memory tiering: count PGPROMOTE_SUCCESS when mem tiering is enabled (git-fixes).\n- memory-failure: use a folio in me_huge_page() (git-fixes).\n- memory: tegra20-emc: fix an OF node reference bug in tegra_emc_find_node_by_ram_code() (git-fixes).\n- mfd: da9052-spi: Change read-mask to write-mask (git-fixes).\n- mfd: intel_soc_pmic_bxtwc: Use IRQ domain for PMIC devices (git-fixes).\n- mfd: intel_soc_pmic_bxtwc: Use IRQ domain for TMU device (git-fixes).\n- mfd: intel_soc_pmic_bxtwc: Use IRQ domain for USB Type-C device (git-fixes).\n- misc: fastrpc: Deregister device nodes properly in error scenarios (git-fixes).\n- misc: fastrpc: Fix copy buffer page size (git-fixes).\n- misc: fastrpc: Fix registered buffer page address (git-fixes).\n- misc: microchip: pci1xxxx: Resolve kernel panic during GPIO IRQ handling (git-fixes).\n- misc: microchip: pci1xxxx: Resolve return code mismatch during GPIO set config (git-fixes).\n- misc: misc_minor_alloc to use ida for all dynamic/misc dynamic minors (git-fixes).\n- mm, kmsan: fix infinite recursion due to RCU critical section (git-fixes).\n- mm,page_owner: do not remove __GFP_NOLOCKDEP in add_stack_record_to_list (git-fixes).\n- mm/filemap: avoid buffered read/write race to read inconsistent data (bsc#1234204).\n- mm/memory-failure: cast index to loff_t before shifting it (git-fixes).\n- mm/memory-failure: check the mapcount of the precise page (git-fixes).\n- mm/memory-failure: fix crash in split_huge_page_to_list from soft_offline_page (git-fixes).\n- mm/memory-failure: pass the folio and the page to collect_procs() (git-fixes).\n- mm/memory-failure: use raw_spinlock_t in struct memory_failure_cpu (git-fixes).\n- mm/memory_hotplug: add missing mem_hotplug_lock (git-fixes).\n- mm/memory_hotplug: fix error handling in add_memory_resource() (git-fixes).\n- mm/memory_hotplug: prevent accessing by index=-1 (git-fixes).\n- mm/memory_hotplug: use pfn math in place of direct struct page manipulation (git-fixes).\n- mm/migrate: correct nr_failed in migrate_pages_sync() (git-fixes).\n- mm/migrate: fix deadlock in migrate_pages_batch() on large folios (git-fixes).\n- mm/migrate: putback split folios when numa hint migration fails (git-fixes).\n- mm/migrate: split source folio if it is on deferred split list (git-fixes).\n- mm/page_owner: remove free_ts from page_owner output (git-fixes).\n- mm/readahead: do not allow order-1 folio (bsc#1234205).\n- mm/readahead: limit page cache size in page_cache_ra_order() (bsc#1234208).\n- mm/rodata_test: use READ_ONCE() to read const variable (git-fixes).\n- mm: convert DAX lock/unlock page to lock/unlock folio (git-fixes).\n- mm: memory-failure: ensure moving HWPoison flag to the raw error pages (git-fixes).\n- mm: memory-failure: fetch compound head after extra page refcnt is held (git-fixes).\n- mm: memory-failure: fix potential page refcnt leak in memory_failure() (git-fixes).\n- mm: memory-failure: fix race window when trying to get hugetlb folio (git-fixes).\n- mm: memory-failure: remove unneeded PageHuge() check (git-fixes).\n- mm: prevent derefencing NULL ptr in pfn_section_valid() (git-fixes).\n- mmc: core: Add SD card quirk for broken poweroff notification (stable-fixes).\n- mmc: mtk-sd: Fix MMC_CAP2_CRYPTO flag setting (git-fixes).\n- mmc: mtk-sd: fix devm_clk_get_optional usage (stable-fixes).\n- mmc: sdhci-esdhc-imx: enable quirks SDHCI_QUIRK_NO_LED (stable-fixes).\n- mmc: sdhci-pci: Add DMI quirk for missing CD GPIO on Vexia Edu Atla 10 tablet (stable-fixes).\n- mmc: sdhci-tegra: Remove SDHCI_QUIRK_BROKEN_ADMA_ZEROLEN_DESC quirk (git-fixes).\n- modpost: fix the missed iteration for the max bit in do_input() (git-fixes).\n- mtd: diskonchip: Cast an operand to prevent potential overflow (git-fixes).\n- mtd: hyperbus: rpc-if: Add missing MODULE_DEVICE_TABLE (git-fixes).\n- mtd: hyperbus: rpc-if: Convert to platform remove callback returning void (stable-fixes).\n- mtd: onenand: Fix uninitialized retlen in do_otp_read() (git-fixes).\n- mtd: rawnand: arasan: Fix double assertion of chip-select (git-fixes).\n- mtd: rawnand: arasan: Fix missing de-registration of NAND (git-fixes).\n- mtd: rawnand: fix double free in atmel_pmecc_create_user() (git-fixes).\n- mtd: spinand: Remove write_enable_op() in markbad() (git-fixes).\n- net :mana :Request a V2 response version for MANA_QUERY_GF_STAT (git-fixes).\n- net/ipv6: release expired exception dst cached in socket (bsc#1216813).\n- net/mlx5e: CT: Fix null-ptr-deref in add rule err flow (git-fixes).\n- net/mlx5e: Remove workaround to avoid syndrome for internal port (git-fixes).\n- net/mlx5e: clear xdp features on non-uplink representors (git-fixes).\n- net/qed: allow old cards not supporting \"num_images\" to work (git-fixes).\n- net/rose: prevent integer overflows in rose_setsockopt() (git-fixes).\n- net: Return error from sk_stream_wait_connect() if sk_wait_event() fails (git-fixes).\n- net: mana: Increase the DEF_RX_BUFFERS_PER_QUEUE to 1024 (bsc#1235246).\n- net: phy: c45-tjaxx: add delay between MDIO write and read in soft_reset (git-fixes).\n- net: rose: fix timer races against user threads (git-fixes).\n- net: usb: qmi_wwan: add Quectel RG650V (stable-fixes).\n- net: usb: qmi_wwan: add Telit FE910C04 compositions (stable-fixes).\n- net: usb: rtl8150: enable basic endpoint checking (git-fixes).\n- net: wwan: iosm: Properly check for valid exec stage in ipc_mmio_init() (git-fixes).\n- net: wwan: t7xx: Fix FSM command timeout issue (git-fixes).\n- netfilter: nf_tables: validate family when identifying table via handle (bsc#1233778 ZDI-24-1454).\n- nfs: ignore SB_RDONLY when mounting nfs (git-fixes).\n- nfsd: fix nfs4_openowner leak when concurrent nfsd4_open occur (git-fixes).\n- nfsd: make sure exp active before svc_export_show (git-fixes).\n- nfsd: release svc_expkey/svc_export with rcu_work (git-fixes).\n- nfsd: restore callback functionality for NFSv4.0 (git-fixes).\n- nilfs2: fix buffer head leaks in calls to truncate_inode_pages() (git-fixes).\n- nilfs2: fix possible int overflows in nilfs_fiemap() (git-fixes).\n- nilfs2: fix potential out-of-bounds memory access in nilfs_find_entry() (git-fixes).\n- nilfs2: prevent use of deleted inode (git-fixes).\n- nvme-pci: 512 byte aligned dma pool segment quirk (git-fixes).\n- nvme-rdma: unquiesce admin_q before destroy it (git-fixes).\n- nvme-tcp: Fix I/O queue cpu spreading for multiple controllers (git-fixes).\n- nvme-tcp: fix the memleak while create new ctrl failed (git-fixes).\n- nvme/multipath: Fix RCU list traversal to use SRCU primitive (git-fixes).\n- nvme: Add error check for xa_store in nvme_get_effects_log (git-fixes).\n- nvme: Add error path for xa_store in nvme_init_effects (git-fixes).\n- nvme: apple: fix device reference counting (git-fixes).\n- nvme: fix bogus kzalloc() return check in nvme_init_effects_log() (git-fixes).\n- nvme: fix metadata handling in nvme-passthrough (git-fixes).\n- nvmet-loop: avoid using mutex in IO hotpath (git-fixes).\n- nvmet: propagate npwg topology (git-fixes).\n- ocfs2: fix uninitialized value in ocfs2_file_read_iter() (git-fixes).\n- ocfs2: free inode when ocfs2_get_init_inode() fails (git-fixes).\n- of/irq: Fix using uninitialized variable @addr_len in API of_irq_parse_one() (git-fixes).\n- of: Fix error path in of_parse_phandle_with_args_map() (git-fixes).\n- of: Fix refcount leakage for OF node returned by __of_get_dma_parent() (git-fixes).\n- of: address: Report error on resource bounds overflow (stable-fixes).\n- padata: add pd get/put refcnt helper (git-fixes).\n- padata: avoid UAF for reorder_work (git-fixes).\n- padata: fix UAF in padata_reorder (git-fixes).\n- parisc: Raise minimal GCC version (bsc#1220773).\n- parisc: Raise minimal GCC version to 12.0.0 (bsc#1220773 git-fix).\n- percpu: Add {raw,this}_cpu_try_cmpxchg() (bsc#1220773).\n- percpu: Fix self-assignment of __old in raw_cpu_generic_try_cmpxchg() (bsc#1220773 git-fix).\n- percpu: Wire up cmpxchg128 (bsc#1220773).\n- phy: core: Fix an OF node refcount leakage in _of_phy_get() (git-fixes).\n- phy: core: Fix an OF node refcount leakage in of_phy_provider_lookup() (git-fixes).\n- phy: core: Fix that API devm_of_phy_provider_unregister() fails to unregister the phy provider (git-fixes).\n- phy: core: Fix that API devm_phy_destroy() fails to destroy the phy (git-fixes).\n- phy: core: Fix that API devm_phy_put() fails to release the phy (git-fixes).\n- phy: qcom-qmp: Fix register name in RX Lane config of SC8280XP (git-fixes).\n- phy: rockchip: naneng-combphy: fix phy reset (git-fixes).\n- phy: usb: Toggle the PHY power during init (git-fixes).\n- pinctrl: amd: Take suspend type into consideration which pins are non-wake (git-fixes).\n- pinctrl: mcp23s08: Fix sleeping in atomic context due to regmap locking (git-fixes).\n- pinctrl: qcom-pmic-gpio: add support for PM8937 (stable-fixes).\n- pinctrl: qcom: spmi-mpp: Add PM8937 compatible (stable-fixes).\n- pinctrl: samsung: fix fwnode refcount cleanup if platform_get_irq_optional() fails (git-fixes).\n- pinmux: Use sequential access to access desc-\u003epinmux data (stable-fixes).\n- platform/chrome: cros_ec_proto: Lock device when updating MKBP version (git-fixes).\n- platform/x86/amd/pmc: Only disable IRQ1 wakeup where i8042 actually enabled it (git-fixes).\n- platform/x86/intel-uncore-freq: Ignore minor version change (bsc#1225897).\n- platform/x86/intel/tpmi: Add defines to get version information (bsc#1225897).\n- platform/x86: asus-nb-wmi: Ignore unknown event 0xCF (stable-fixes).\n- platform/x86: dell-smbios-base: Extends support to Alienware products (stable-fixes).\n- platform/x86: dell-wmi-base: Handle META key Lock/Unlock events (stable-fixes).\n- platform/x86: thinkpad_acpi: Fix for ThinkPad's with ECFW showing incorrect fan speed (stable-fixes).\n- pm:cpupower: Add missing powercap_set_enabled() stub function (git-fixes).\n- power: ip5xxx_power: Fix return value on ADC read errors (git-fixes).\n- power: supply: gpio-charger: Fix set charge current limits (git-fixes).\n- powerpc/book3s64/hugetlb: Fix disabling hugetlb when fadump is active (bsc#1235108).\n- powerpc/iommu: Move pSeries specific functions to pseries/iommu.c (bsc#1220711 ltc#205755).\n- powerpc/iommu: Only build sPAPR access functions on pSeries (bsc#1220711 ltc#205755).\n- powerpc/powernv/pci: Remove MVE code (bsc#1220711 ltc#205755).\n- powerpc/powernv/pci: Remove ioda1 support (bsc#1220711 ltc#205755).\n- powerpc/powernv/pci: Remove last IODA1 defines (bsc#1220711 ltc#205755).\n- powerpc/pseries/eeh: Fix get PE state translation (bsc#1215199).\n- powerpc/pseries/iommu: IOMMU incorrectly marks MMIO range in DDW (bsc#1218470 ltc#204531).\n- powerpc/pseries/vas: Add close() callback in vas_vm_ops struct (bsc#1234825).\n- pps: add an error check in parport_attach (git-fixes).\n- pps: remove usage of the deprecated ida_simple_xx() API (stable-fixes).\n- printk: Add is_printk_legacy_deferred() (bsc#1236733).\n- printk: Defer legacy printing when holding printk_cpu_sync (bsc#1236733).\n- proc/softirqs: replace seq_printf with seq_put_decimal_ull_width (git-fixes).\n- pwm: stm32-lp: Add check for clk_enable() (git-fixes).\n- pwm: stm32: Add check for clk_enable() (git-fixes).\n- quota: Fix rcu annotations of inode dquot pointers (bsc#1234197).\n- quota: explicitly forbid quota files from being encrypted (bsc#1234196).\n- quota: flush quota_release_work upon quota writeback (bsc#1234195).\n- quota: simplify drop_dquot_ref() (bsc#1234197).\n- rcu-tasks: Pull sampling of -\u003epercpu_dequeue_lim out of loop (git-fixes)\n- rcu/tree: Defer setting of jiffies during stall reset (git-fixes)\n- rcu: Dump memory object info if callback function is invalid (git-fixes)\n- rcu: Eliminate rcu_gp_slow_unregister() false positive (git-fixes)\n- rcuscale: Move rcu_scale_writer() (git-fixes)\n- rdma/cxgb4: Prevent potential integer overflow on 32bit (git-fixes)\n- readahead: use ilog2 instead of a while loop in page_cache_ra_order() (bsc#1234208).\n- regmap: Use correct format specifier for logging range errors (stable-fixes).\n- regulator: core: Add missing newline character (git-fixes).\n- regulator: of: Implement the unwind path of of_regulator_match() (git-fixes).\n- regulator: rk808: Add apply_bit for BUCK3 on RK809 (stable-fixes).\n- remoteproc: core: Fix ida_free call while not allocated (git-fixes).\n- rtc: cmos: avoid taking rtc_lock for extended period of time (stable-fixes).\n- rtc: pcf85063: fix potential OOB write in PCF85063 NVMEM read (git-fixes).\n- rtc: zynqmp: Fix optional clock name property (git-fixes).\n- s390/cio: Do not unregister the subchannel based on DNV (git-fixes).\n- s390/cpum_sf: Convert to cmpxchg128() (bsc#1220773).\n- s390/cpum_sf: Handle CPU hotplug remove during sampling (git-fixes).\n- s390/cpum_sf: Remove WARN_ON_ONCE statements (git-fixes).\n- s390/facility: Disable compile time optimization for decompressor code (git-fixes).\n- s390/iucv: MSG_PEEK causes memory leak in iucv_sock_destruct() (git-fixes).\n- s390/pageattr: Implement missing kernel_page_present() (git-fixes).\n- s390x config: IOMMU_DEFAULT_DMA_LAZY=y (bsc#1235646)\n- samples/landlock: Fix possible NULL dereference in parse_path() (git-fixes).\n- scatterlist: fix incorrect func name in kernel-doc (git-fixes).\n- sched/fair: Fix value reported by hot tasks pulled in /proc/schedstat (bsc#1235865).\n- sched/fair: Fix value reported by hot tasks pulled in /proc/schedstat -kabi (bsc#1235865).\n- sched/numa: fix memory leak due to the overwritten vma-\u003enumab_state (git fixes (sched/numa)).\n- scsi: lpfc: Add handling for LS_RJT reason explanation authentication required (bsc#1235409).\n- scsi: lpfc: Add support for large fw object application layer reads (bsc#1235409).\n- scsi: lpfc: Change lpfc_nodelist save_flags member into a bitmask (bsc#1235409).\n- scsi: lpfc: Copyright updates for 14.4.0.7 patches (bsc#1235409).\n- scsi: lpfc: Delete NLP_TARGET_REMOVE flag due to obsolete usage (bsc#1235409).\n- scsi: lpfc: Modify handling of ADISC based on ndlp state and RPI registration (bsc#1235409).\n- scsi: lpfc: Redefine incorrect type in lpfc_create_device_data() (bsc#1235409).\n- scsi: lpfc: Restrict the REG_FCFI MAM field to FCoE adapters only (bsc#1235409).\n- scsi: lpfc: Update definition of firmware configuration mbox cmds (bsc#1235409).\n- scsi: lpfc: Update lpfc version to 14.4.0.7 (bsc#1235409).\n- scsi: qla2xxx: Fix NVMe and NPIV connect issue (bsc#1235406).\n- scsi: qla2xxx: Fix abort in bsg timeout (bsc#1235406).\n- scsi: qla2xxx: Fix use after free on unload (bsc#1235406).\n- scsi: qla2xxx: Remove check req_sg_cnt should be equal to rsp_sg_cnt (bsc#1235406).\n- scsi: qla2xxx: Remove the unused 'del_list_entry' field in struct fc_port (bsc#1235406).\n- scsi: qla2xxx: Supported speed displayed incorrectly for VPorts (bsc#1235406).\n- scsi: qla2xxx: Update version to 10.02.09.400-k (bsc#1235406).\n- scsi: storvsc: Do not flag MAINTENANCE_IN return of SRB_STATUS_DATA_OVERRUN as an error (git-fixes).\n- scsi: storvsc: Ratelimit warning logs to prevent VM denial of service (git-fixes).\n- seccomp: Stub for !CONFIG_SECCOMP (stable-fixes).\n- selftest: media_tests: fix trivial UAF typo (git-fixes).\n- selftests/alsa: Fix circular dependency involving global-timer (stable-fixes).\n- selftests/bpf: Test PROBE_MEM of VSYSCALL_ADDR on x86-64 (git-fixes).\n- selftests/landlock: Fix error message (git-fixes).\n- selftests/mm/cow: modify the incorrect checking parameters (git-fixes).\n- selftests/powerpc: Fix argument order to timer_sub() (git-fixes).\n- selftests: harness: fix printing of mismatch values in __EXPECT() (git-fixes).\n- selftests: mptcp: avoid spurious errors on disconnect (git-fixes).\n- selftests: tc-testing: reduce rshift value (stable-fixes).\n- selftests: timers: clocksource-switch: Adapt progress to kselftest framework (git-fixes).\n- selinux: Fix SCTP error inconsistency in selinux_socket_bind() (git-fixes).\n- serial: 8250: Adjust the timeout for FIFO mode (git-fixes).\n- serial: 8250_dw: Add Sophgo SG2044 quirk (stable-fixes).\n- serial: 8250_dw: Do not use struct dw8250_data outside of 8250_dw (git-fixes).\n- serial: 8250_dw: Replace ACPI device check by a quirk (git-fixes).\n- serial: 8250_fintek: Add support for F81216E (stable-fixes).\n- serial: Do not hold the port lock when setting rx-during-tx GPIO (git-fixes).\n- serial: amba-pl011: Fix RX stall when DMA is used (git-fixes).\n- serial: amba-pl011: Use port lock wrappers (stable-fixes).\n- serial: amba-pl011: fix build regression (git-fixes).\n- serial: do not use uninitialized value in uart_poll_init() (git-fixes).\n- serial: imx: only set receiver level if it is zero (git-fixes).\n- serial: imx: set receiver level before starting uart (git-fixes).\n- serial: qcom-geni: Do not cancel/abort if we can't get the port lock (git-fixes).\n- serial: qcom-geni: disable interrupts during console writes (git-fixes).\n- serial: qcom-geni: fix arg types for qcom_geni_serial_poll_bit() (git-fixes).\n- serial: qcom-geni: fix console corruption (git-fixes).\n- serial: qcom-geni: fix dma rx cancellation (git-fixes).\n- serial: qcom-geni: fix false console tx restart (git-fixes).\n- serial: qcom-geni: fix fifo polling timeout (git-fixes).\n- serial: qcom-geni: fix hard lockup on buffer flush (git-fixes).\n- serial: qcom-geni: fix polled console corruption (git-fixes).\n- serial: qcom-geni: fix polled console initialisation (git-fixes).\n- serial: qcom-geni: fix receiver enable (git-fixes).\n- serial: qcom-geni: fix shutdown race (git-fixes).\n- serial: qcom-geni: fix soft lockup on sw flow control and suspend (git-fixes).\n- serial: qcom-geni: introduce qcom_geni_serial_poll_bitfield() (git-fixes).\n- serial: qcom-geni: revert broken hibernation support (git-fixes).\n- serial: sh-sci: Do not probe the serial port if its slot in sci_ports[] is in use (git-fixes).\n- serial: sh-sci: Drop __initdata macro for port_cfg (git-fixes).\n- serial: stm32: Return IRQ_NONE in the ISR if no handling happend (git-fixes).\n- serial: stm32: do not always set SER_RS485_RX_DURING_TX if RS485 is enabled (git-fixes).\n- slub: Replace cmpxchg_double() (bsc#1220773).\n- slub: Replace cmpxchg_double() - KABI fix (bsc#1220773).\n- smb: client: fix TCP timers deadlock after rmmod (git-fixes) [hcarvalho: fix issue described in bsc#1233642]\n- soc/fsl: cpm: qmc: Convert to platform remove callback returning void (stable-fixes).\n- soc: atmel: fix device_node release in atmel_soc_device_init() (git-fixes).\n- soc: fsl: cpm1: qmc: Fix blank line and spaces (stable-fixes).\n- soc: fsl: cpm1: qmc: Introduce qmc_init_resource() and its CPM1 version (stable-fixes).\n- soc: fsl: cpm1: qmc: Introduce qmc_{init,exit}_xcc() and their CPM1 version (stable-fixes).\n- soc: fsl: cpm1: qmc: Re-order probe() operations (stable-fixes).\n- soc: fsl: cpm1: qmc: Set the ret error code on platform_get_irq() failure (git-fixes).\n- soc: imx8m: Probe the SoC driver as platform driver (stable-fixes).\n- soc: mediatek: mtk-devapc: Fix leaking IO map on error paths (git-fixes).\n- soc: qcom: Add check devm_kasprintf() returned value (stable-fixes).\n- soc: qcom: geni-se: Add M_TX_FIFO_NOT_EMPTY bit definition (git-fixes).\n- soc: qcom: geni-se: add GP_LENGTH/IRQ_EN_SET/IRQ_EN_CLEAR registers (git-fixes).\n- soc: qcom: smem_state: fix missing of_node_put in error path (git-fixes).\n- soc: qcom: socinfo: Avoid out of bounds read of serial number (git-fixes).\n- soc: qcom: socinfo: fix revision check in qcom_socinfo_probe() (git-fixes).\n- sound: usb: enable DSD output for ddHiFi TC44C (stable-fixes).\n- sound: usb: format: do not warn that raw DSD is unsupported (stable-fixes).\n- spi: aspeed: Fix an error handling path in aspeed_spi_[read|write]_user() (git-fixes).\n- spi: zynq-qspi: Add check for clk_enable() (git-fixes).\n- srcu: Fix srcu_struct node grpmask overflow on 64-bit systems (git-fixes)\n- srcu: Only accelerate on enqueue time (git-fixes)\n- stackdepot: rename pool_index to pool_index_plus_1 (git-fixes).\n- stackdepot: respect __GFP_NOLOCKDEP allocation flag (git-fixes).\n- staging: iio: ad9832: Correct phase range check (git-fixes).\n- staging: iio: ad9834: Correct phase range check (git-fixes).\n- staging: media: imx: fix OF node leak in imx_media_add_of_subdevs() (git-fixes).\n- staging: media: max96712: fix kernel oops when removing module (git-fixes).\n- sunrpc: clear XPRT_SOCK_UPD_TIMEOUT when reset transport (git-fixes).\n- sunrpc: fix one UAF issue caused by sunrpc kernel tcp socket (git-fixes).\n- sunrpc: handle -ENOTCONN in xs_tcp_setup_socket() (git-fixes).\n- supported.conf: Add support for v4l2-dv-timings (jsc#PED-8645)\n- svcrdma: Address an integer overflow (git-fixes).\n- svcrdma: fix miss destroy percpu_counter in svc_rdma_proc_init() (git-fixes).\n- swiotlb: Enforce page alignment in swiotlb_alloc() (git-fixes).\n- swiotlb: Reinstate page-alignment for mappings \u003e= PAGE_SIZE (git-fixes).\n- thermal/drivers/qcom/tsens-v1: Add support for MSM8937 tsens (stable-fixes).\n- thermal: of: fix OF node leak in of_thermal_zone_find() (git-fixes).\n- thunderbolt: Add support for Intel Lunar Lake (stable-fixes).\n- thunderbolt: Add support for Intel Panther Lake-M/P (stable-fixes).\n- tipc: fix NULL deref in cleanup_bearer() (bsc#1235433).\n- tools: Sync if_xdp.h uapi tooling header (git-fixes).\n- tools: hv: change permissions of NetworkManager configuration file (git-fixes).\n- tpm/eventlog: Limit memory allocations for event logs with excessive size (bsc#1233260 bsc#1233259 bsc#1232421).\n- tpm: Map the ACPI provided event log (bsc#1233260 bsc#1233259 bsc#1232421).\n- tpm_tis_spi: Release chip select when flow control fails (bsc#1234338)\n- tty: serial: 8250: Fix another runtime PM usage counter underflow (git-fixes).\n- tty: serial: kgdboc: Fix 8250_* kgdb over serial (git-fixes).\n- types: Introduce [us]128 (bsc#1220773).\n- ubifs: Correct the total block count by deducting journal reservation (git-fixes).\n- ubifs: authentication: Fix use-after-free in ubifs_tnc_end_commit (git-fixes).\n- ubifs: skip dumping tnc tree when zroot is null (git-fixes).\n- udf: Fix lock ordering in udf_evict_inode() (bsc#1234238).\n- udf: fix uninit-value use in udf_get_fileshortad (bsc#1234243).\n- udf: prevent integer overflow in udf_bitmap_free_blocks() (bsc#1234239).\n- udf: refactor inode_bmap() to handle error (bsc#1234242).\n- udf: refactor udf_current_aext() to handle error (bsc#1234240).\n- udf: refactor udf_next_aext() to handle error (bsc#1234241).\n- udf: udftime: prevent overflow in udf_disk_stamp_to_time() (bsc#1234237).\n- uio: Fix return value of poll (git-fixes).\n- uio: uio_dmem_genirq: check the return value of devm_kasprintf() (git-fixes).\n- usb-storage: Add max sectors quirk for Nokia 208 (stable-fixes).\n- usb: add support for new USB device ID 0x17EF:0x3098 for the r8152 driver (stable-fixes).\n- usb: cdns3-ti: Add workaround for Errata i2409 (stable-fixes).\n- usb: cdns3: Add quirk flag to enable suspend residency (stable-fixes).\n- usb: chipidea: add CI_HDRC_FORCE_VBUS_ACTIVE_ALWAYS flag (stable-fixes).\n- usb: chipidea: udc: handle USB Error Interrupt if IOC not set (stable-fixes).\n- usb: dwc2: Fix HCD port connection race (git-fixes).\n- usb: dwc2: Fix HCD resume (git-fixes).\n- usb: dwc2: gadget: Do not write invalid mapped sg entries into dma_desc with iommu enabled (stable-fixes).\n- usb: dwc2: hcd: Fix GetPortStatus \u0026 SetPortFeature (git-fixes).\n- usb: dwc3-am62: Disable autosuspend during remove (git-fixes).\n- usb: dwc3-am62: Fix an OF node leak in phy_syscon_pll_refclk() (git-fixes).\n- usb: dwc3: ep0: Do not clear ep0 DWC3_EP_TRANSFER_STARTED (git-fixes).\n- usb: dwc3: ep0: Do not reset resource alloc flag (git-fixes).\n- usb: dwc3: ep0: Do not reset resource alloc flag (including ep0) (git-fixes).\n- usb: dwc3: gadget: Rewrite endpoint allocation flow (stable-fixes).\n- usb: dwc3: gadget: fix writing NYET threshold (git-fixes).\n- usb: dwc3: xilinx: make sure pipe clock is deselected in usb2 only mode (git-fixes).\n- usb: ehci-hcd: fix call balance of clocks handling routines (git-fixes).\n- usb: fix reference leak in usb_new_device() (git-fixes).\n- usb: gadget: configfs: Ignore trailing LF for user strings to cdev (git-fixes).\n- usb: gadget: f_fs: Remove WARN_ON in functionfs_bind (git-fixes).\n- usb: gadget: f_tcm: Decrement command ref count on cleanup (git-fixes).\n- usb: gadget: f_tcm: Do not free command immediately (git-fixes).\n- usb: gadget: f_tcm: Do not prepare BOT write request twice (git-fixes).\n- usb: gadget: f_tcm: Fix Get/SetInterface return value (git-fixes).\n- usb: gadget: f_tcm: Translate error to sense (git-fixes).\n- usb: gadget: f_tcm: ep_autoconfig with fullspeed endpoint (git-fixes).\n- usb: gadget: f_uac2: Fix incorrect setting of bNumEndpoints (git-fixes).\n- usb: gadget: u_serial: Disable ep before setting port to null to fix the crash caused by port being null (git-fixes).\n- usb: gadget: u_serial: Fix the issue that gs_start_io crashed due to accessing null pointer (git-fixes).\n- usb: host: max3421-hcd: Correctly abort a USB request (git-fixes).\n- usb: host: xhci-plat: Assign shared_hcd-\u003ersrc_start (git-fixes).\n- usb: typec: anx7411: fix OF node reference leaks in anx7411_typec_switch_probe() (git-fixes).\n- usb: typec: anx7411: fix fwnode_handle reference leak (git-fixes).\n- usb: typec: fix pm usage counter imbalance in ucsi_ccg_sync_control() (bsc#1235001)\n- usb: typec: tcpm/tcpci_maxim: fix error code in max_contaminant_read_resistance_kohm() (git-fixes).\n- usb: typec: tcpm: set SRC_SEND_CAPABILITIES timeout to PD_T_SENDER_RESPONSE (git-fixes).\n- usb: typec: use cleanup facility for 'altmodes_node' (stable-fixes).\n- usbnet: ipheth: break up NCM header size computation (git-fixes).\n- usbnet: ipheth: check that DPE points past NCM header (git-fixes).\n- usbnet: ipheth: fix DPE OoB read (git-fixes).\n- usbnet: ipheth: fix possible overflow in DPE length check (git-fixes).\n- usbnet: ipheth: refactor NCM datagram loop (git-fixes).\n- usbnet: ipheth: use static NDP16 location in URB (git-fixes).\n- vDPA/ifcvf: Fix pci_read_config_byte() return code handling (git-fixes).\n- vdpa/mlx5: Fix PA offset with unaligned starting iotlb map (git-fixes).\n- vdpa/mlx5: Fix suboptimal range on iotlb iteration (git-fixes).\n- vdpa: solidrun: Fix UB bug with devres (git-fixes).\n- vfs: fix readahead(2) on block devices (bsc#1234201).\n- vmscan,migrate: fix page count imbalance on node stats when demoting pages (git-fixes).\n- watchdog: rzg2l_wdt: Power on the watchdog domain in the restart handler (stable-fixes).\n- watchdog: rzg2l_wdt: Rely on the reset driver for doing proper reset (stable-fixes).\n- watchdog: rzg2l_wdt: Remove reset de-assert from probe (stable-fixes).\n- wifi: ath11k: Fix unexpected return buffer manager error for WCN6750/WCN6855 (git-fixes).\n- wifi: ath11k: cleanup struct ath11k_mon_data (git-fixes).\n- wifi: ath12k: fix atomic calls in ath12k_mac_op_set_bitrate_mask() (stable-fixes).\n- wifi: ath12k: fix tx power, max reg power update to firmware (git-fixes).\n- wifi: ath5k: add PCI ID for Arcadyan devices (git-fixes).\n- wifi: ath5k: add PCI ID for SX76X (git-fixes).\n- wifi: brcmfmac: Fix oops due to NULL pointer dereference in brcmf_sdiod_sglist_rw() (stable-fixes).\n- wifi: brcmfmac: add missing header include for brcmf_dbg (git-fixes).\n- wifi: cfg80211: adjust allocation of colocated AP data (git-fixes).\n- wifi: cfg80211: sme: init n_channels before channels[] access (git-fixes).\n- wifi: cw1200: Fix potential NULL dereference (git-fixes).\n- wifi: ipw2x00: libipw_rx_any(): fix bad alignment (stable-fixes).\n- wifi: iwlwifi: fw: read STEP table from correct UEFI var (git-fixes).\n- wifi: iwlwifi: mvm: Use the sync timepoint API in suspend (stable-fixes).\n- wifi: mac80211: Add non-atomic station iterator (stable-fixes).\n- wifi: mac80211: Fix common size calculation for ML element (git-fixes).\n- wifi: mac80211: clean up 'ret' in sta_link_apply_parameters() (stable-fixes).\n- wifi: mac80211: do not flush non-uploaded STAs (git-fixes).\n- wifi: mac80211: export ieee80211_purge_tx_queue() for drivers (stable-fixes).\n- wifi: mac80211: fix mbss changed flags corruption on 32 bit systems (stable-fixes).\n- wifi: mac80211: fix station NSS capability initialization order (git-fixes).\n- wifi: mac80211: fix tid removal during mesh forwarding (git-fixes).\n- wifi: mac80211: init cnt before accessing elem in ieee80211_copy_mbssid_beacon (git-fixes).\n- wifi: mac80211: prohibit deactivating all links (git-fixes).\n- wifi: mac80211: wake the queues in case of failure in resume (stable-fixes).\n- wifi: mt76: mt76u_vendor_request: Do not print error messages when -EPROTO (git-fixes).\n- wifi: mt76: mt7915: Fix mesh scan on MT7916 DBDC (git-fixes).\n- wifi: mt76: mt7915: add module param to select 5 GHz or 6 GHz on MT7916 (git-fixes).\n- wifi: mt76: mt7915: firmware restart on devices with a second pcie link (git-fixes).\n- wifi: mt76: mt7915: fix overflows seen when writing limit attributes (git-fixes).\n- wifi: mt76: mt7915: fix register mapping (git-fixes).\n- wifi: mt76: mt7921: fix using incorrect group cipher after disconnection (git-fixes).\n- wifi: mt76: mt7925: fix off by one in mt7925_load_clc() (git-fixes).\n- wifi: mt76: mt7996: add max mpdu len capability (git-fixes).\n- wifi: mt76: mt7996: fix HE Phy capability (git-fixes).\n- wifi: mt76: mt7996: fix definition of tx descriptor (git-fixes).\n- wifi: mt76: mt7996: fix incorrect indexing of MIB FW event (git-fixes).\n- wifi: mt76: mt7996: fix ldpc setting (git-fixes).\n- wifi: mt76: mt7996: fix overflows seen when writing limit attributes (git-fixes).\n- wifi: mt76: mt7996: fix register mapping (git-fixes).\n- wifi: mt76: mt7996: fix rx filter setting for bfee functionality (git-fixes).\n- wifi: mt76: mt7996: fix the capability of reception of EHT MU PPDU (git-fixes).\n- wifi: nl80211: fix NL80211_ATTR_MLO_LINK_ID off-by-one (git-fixes).\n- wifi: rtlwifi: Drastically reduce the attempts to read efuse in case of failures (stable-fixes).\n- wifi: rtlwifi: destroy workqueue at rtl_deinit_core (git-fixes).\n- wifi: rtlwifi: do not complete firmware loading needlessly (git-fixes).\n- wifi: rtlwifi: fix init_sw_vars leak when probe fails (git-fixes).\n- wifi: rtlwifi: fix memory leaks and invalid access at probe error path (git-fixes).\n- wifi: rtlwifi: pci: wait for firmware loading before releasing memory (git-fixes).\n- wifi: rtlwifi: remove unused check_buddy_priv (git-fixes).\n- wifi: rtlwifi: rtl8192se: rise completion of firmware loading as last step (git-fixes).\n- wifi: rtlwifi: rtl8821ae: Fix media status report (git-fixes).\n- wifi: rtlwifi: rtl8821ae: phy: restore removed code to fix infinite loop (git-fixes).\n- wifi: rtlwifi: usb: fix workqueue leak when probe fails (git-fixes).\n- wifi: rtlwifi: wait for firmware loading before releasing memory (git-fixes).\n- wifi: rtw88: use ieee80211_purge_tx_queue() to purge TX skb (stable-fixes).\n- wifi: rtw89: check return value of ieee80211_probereq_get() for RNR (stable-fixes).\n- wifi: rtw89: mcc: consider time limits not divisible by 1024 (git-fixes).\n- wifi: wcn36xx: fix channel survey memory allocation size (git-fixes).\n- wifi: wlcore: fix unbalanced pm_runtime calls (git-fixes).\n- workqueue: Add rcu lock check at the end of work item execution (bsc#1236732).\n- workqueue: Do not warn when cancelling WQ_MEM_RECLAIM work from !WQ_MEM_RECLAIM worker (bsc#1235416).\n- writeback, cgroup: switch inodes with dirty timestamps to release dying cgwbs (bsc#1234203).\n- x86,amd_iommu: Replace cmpxchg_double() (bsc#1220773).\n- x86,intel_iommu: Replace cmpxchg_double() (bsc#1220773).\n- x86/hyperv: Fix hv tsc page based sched_clock for hibernation (git-fixes).\n- x86/static-call: Remove early_boot_irqs_disabled check to fix Xen PVH dom0 (git-fixes).\n- xfs: Add error handling for xfs_reflink_cancel_cow_range (git-fixes).\n- xfs: Propagate errors from xfs_reflink_cancel_cow_range in xfs_dax_write_iomap_end (git-fixes).\n- xfs: do not allocate COW extents when unsharing a hole (git-fixes).\n- xfs: fix sb_spino_align checks for large fsblock sizes (git-fixes).\n- xfs: remove unknown compat feature check in superblock write validation (git-fixes).\n- xfs: return from xfs_symlink_verify early on V4 filesystems (git-fixes).\n- xfs: sb_spino_align is not verified (git-fixes).\n- xhci: Add usb cold attach (CAS) as a reason to resume root hub (git-fixes).\n- xhci: Allow RPM on the USB controller (1022:43f7) by default (stable-fixes).\n- xhci: fix possible null pointer deref during xhci urb enqueue (git-fixes).\n","status":"published","published":"2025-03-27T14:32:55Z","modified":"2026-03-23T04:48:13.571275Z","updated_at":"2026-11-02T15:53:59.381172Z"},{"id":"SUSE-SU-2025:20249-1","title":"Security update for the Linux Kernel","description":"\n\nThe SUSE Linux Enterprise Micro 6.0 and 6.1 RT kernel was updated to receive various security bugfixes.\n\nThe following security bugs were fixed:\n\n- CVE-2024-26924: scsi: lpfc: Release hbalock before calling lpfc_worker_wake_up() (bsc#1225820).\n- CVE-2024-27397: netfilter: nf_tables: use timestamp to check for set element timeout (bsc#1224095).\n- CVE-2024-35839: kABI fix for netfilter: bridge: replace physindev with physinif in nf_bridge_info (bsc#1224726).\n- CVE-2024-41042: Prefer nft_chain_validate (bsc#1228526).\n- CVE-2024-44934: net: bridge: mcast: wait for previous gc cycles when removing port (bsc#1229809).\n- CVE-2024-44996: vsock: fix recursive -\u003erecvmsg calls (bsc#1230205).\n- CVE-2024-45828: i3c: mipi-i3c-hci: Mask ring interrupts before ring stop request (bsc#1235705).\n- CVE-2024-47678: icmp: change the order of rate limits (bsc#1231854).\n- CVE-2024-48881: bcache: revert replacing IS_ERR_OR_NULL with IS_ERR again (bsc#1235727).\n- CVE-2024-49948: net: add more sanity checks to qdisc_pkt_len_init() (bsc#1232161).\n- CVE-2024-49951: Bluetooth: MGMT: Fix possible crash on mgmt_index_removed (bsc#1232158).\n- CVE-2024-49978: gso: fix udp gso fraglist segmentation after pull from frag_list (bsc#1232101).\n- CVE-2024-49998: net: dsa: improve shutdown sequence (bsc#1232087).\n- CVE-2024-50018: net: napi: Prevent overflow of napi_defer_hard_irqs (bsc#1232419).\n- CVE-2024-50039: kABI: Restore deleted EXPORT_SYMBOL(__qdisc_calculate_pkt_len) (bsc#1231909).\n- CVE-2024-50143: udf: fix uninit-value use in udf_get_fileshortad (bsc#1233038).\n- CVE-2024-50151: smb: client: fix OOBs when building SMB2_IOCTL request (bsc#1233055).\n- CVE-2024-50199: mm/swapfile: skip HugeTLB pages for unuse_vma (bsc#1233112).\n- CVE-2024-50202: nilfs2: propagate directory read errors from nilfs_find_entry() (bsc#1233324).\n- CVE-2024-50256: netfilter: nf_reject_ipv6: fix potential crash in nf_send_reset6() (bsc#1233200).\n- CVE-2024-50262: bpf: Fix out-of-bounds write in trie_get_next_key() (bsc#1233239).\n- CVE-2024-50278, CVE-2024-50280: dm cache: fix flushing uninitialized delayed_work on cache_ctr error (bsc#1233467 bsc#1233469).\n- CVE-2024-50278: dm cache: fix potential out-of-bounds access on the first resume (bsc#1233467).\n- CVE-2024-50299: sctp: properly validate chunk size in sctp_sf_ootb() (bsc#1233488).\n- CVE-2024-53050: drm/i915/hdcp: Add encoder check in hdcp2_get_capability (bsc#1233546).\n- CVE-2024-53064: idpf: fix idpf_vc_core_init error path (bsc#1233558 bsc#1234464).\n- CVE-2024-53090: afs: Fix lock recursion (bsc#1233637).\n- CVE-2024-53091: bpf: Add sk_is_inet and IS_ICSK check in tls_sw_has_ctx_tx/rx (bsc#1233638).\n- CVE-2024-53099: bpf: Check validity of link-\u003etype in bpf_link_show_fdinfo() (bsc#1233772).\n- CVE-2024-53105: mm: page_alloc: move mlocked flag clearance into free_pages_prepare() (bsc#1234069).\n- CVE-2024-53111: mm/mremap: fix address wraparound in move_page_tables() (bsc#1234086).\n- CVE-2024-53113: mm: fix NULL pointer dereference in alloc_pages_bulk_noprof (bsc#1234077).\n- CVE-2024-53117: virtio/vsock: Improve MSG_ZEROCOPY error handling (bsc#1234079).\n- CVE-2024-53118: vsock: Fix sk_error_queue memory leak (bsc#1234071).\n- CVE-2024-53119: virtio/vsock: Fix accept_queue memory leak (bsc#1234073).\n- CVE-2024-53122: mptcp: cope racing subflow creation in mptcp_rcv_space_adjust (bsc#1234076).\n- CVE-2024-53125: bpf: sync_linked_regs() must preserve subreg_def (bsc#1234156).\n- CVE-2024-53130: nilfs2: fix null-ptr-deref in block_dirty_buffer tracepoint (bsc#1234219).\n- CVE-2024-53131: nilfs2: fix null-ptr-deref in block_touch_buffer tracepoint (bsc#1234220).\n- CVE-2024-53133: drm/amd/display: Handle dml allocation failure to avoid crash (bsc#1234221)\n- CVE-2024-53134: pmdomain: imx93-blk-ctrl: correct remove path (bsc#1234159).\n- CVE-2024-53141: netfilter: ipset: add missing range check in bitmap_ip_uadt (bsc#1234381).\n- CVE-2024-53160: rcu/kvfree: Fix data-race in __mod_timer / kvfree_call_rcu (bsc#1234810).\n- CVE-2024-53161: EDAC/bluefield: Fix potential integer overflow (bsc#1234856).\n- CVE-2024-53164: net: sched: fix ordering of qlen adjustment (bsc#1234863).\n- CVE-2024-53170: block: fix uaf for flush rq while iterating tags (bsc#1234888).\n- CVE-2024-53172: ubi: fastmap: Fix duplicate slab cache names while attaching (bsc#1234898).\n- CVE-2024-53175: ipc: fix memleak if msg_init_ns failed in create_ipc_ns (bsc#1234893).\n- CVE-2024-53179: smb: client: fix use-after-free of signing key (bsc#1234921).\n- CVE-2024-53185: smb: client: fix NULL ptr deref in crypto_aead_setkey() (bsc#1234901).\n- CVE-2024-53187: io_uring: check for overflows in io_pin_pages (bsc#1234947).\n- CVE-2024-53195: KVM: arm64: Get rid of userspace_irqchip_in_use (bsc#1234957).\n- CVE-2024-53196: KVM: arm64: Do not retire aborted MMIO instruction (bsc#1234906).\n- CVE-2024-53198: xen: Fix the issue of resource not being properly released in xenbus_dev_probe() (bsc#1234923).\n- CVE-2024-53203: usb: typec: fix potential array underflow in ucsi_ccg_sync_control() (bsc#1235001).\n- CVE-2024-53214: vfio/pci: Properly hide first-in-list PCIe extended capability (bsc#1235004).\n- CVE-2024-53216: nfsd: fix UAF when access ex_uuid or ex_stats (bsc#1235003).\n- CVE-2024-53222: zram: fix NULL pointer in comp_algorithm_show() (bsc#1234974).\n- CVE-2024-53227: scsi: bfa: Fix use-after-free in bfad_im_module_exit() (bsc#1235011).\n- CVE-2024-53232: iommu/s390: Implement blocking domain (bsc#1235050).\n- CVE-2024-53234: erofs: handle NONHEAD !delta[1] lclusters gracefully (bsc#1235045).\n- CVE-2024-53236: xsk: Free skb when TX metadata options are invalid (bsc#1235000).\n- CVE-2024-53240: xen/netfront: fix crash when removing device (bsc#1234281).\n- CVE-2024-53241: x86/xen: use new hypercall functions instead of hypercall page (XSA-466 bsc#1234282).\n- CVE-2024-53685: ceph: give up on paths longer than PATH_MAX (bsc#1235720).\n- CVE-2024-55639: net: renesas: rswitch: avoid use-after-put for a device tree node (bsc#1235737).\n- CVE-2024-55881: KVM: x86: Play nice with protected guests in complete_hypercall_exit() (bsc#1235745).\n- CVE-2024-56372: net: tun: fix tun_napi_alloc_frags() (bsc#1235753).\n- CVE-2024-56549: cachefiles: Fix NULL pointer dereference in object-\u003efile (bsc#1234912).\n- CVE-2024-56566: mm/slub: Avoid list corruption when removing a slab from the full list (bsc#1235033).\n- CVE-2024-56568: iommu/arm-smmu: Defer probe of clients after smmu device bound (bsc#1235032).\n- CVE-2024-56569: ftrace: Fix regression with module command in stack_trace_filter (bsc#1235031).\n- CVE-2024-56570: ovl: Filter invalid inodes with missing lookup function (bsc#1235035).\n- CVE-2024-56582: btrfs: fix use-after-free in btrfs_encoded_read_endio() (bsc#1235128).\n- CVE-2024-56588: scsi: hisi_sas: Create all dump files during debugfs initialization (bsc#1235123).\n- CVE-2024-56589: scsi: hisi_sas: Add cond_resched() for no forced preemption model (bsc#1235241).\n- CVE-2024-56599: wifi: ath10k: avoid NULL pointer error during sdio remove (bsc#1235138).\n- CVE-2024-56600: net: inet6: do not leave a dangling sk pointer in inet6_create() (bsc#1235217).\n- CVE-2024-56601: net: inet: do not leave a dangling sk pointer in inet_create() (bsc#1235230).\n- CVE-2024-56602: net: ieee802154: do not leave a dangling sk pointer in ieee802154_create() (bsc#1235521).\n- CVE-2024-56603: net: af_can: do not leave a dangling sk pointer in can_create() (bsc#1235415).\n- CVE-2024-56604: Bluetooth: RFCOMM: avoid leaving dangling sk pointer in rfcomm_sock_alloc() (bsc#1235056).\n- CVE-2024-56608: drm/amd/display: Fix out-of-bounds access in 'dcn21_link_encoder_create' (bsc#1235487).\n- CVE-2024-56610: kcsan: Turn report_filterlist_lock into a raw_spinlock (bsc#1235390).\n- CVE-2024-56611: mm/mempolicy: fix migrate_to_node() assuming there is at least one VMA in a MM (bsc#1235391).\n- CVE-2024-56614: xsk: fix OOB map writes when deleting elements (bsc#1235424).\n- CVE-2024-56615: bpf: fix OOB devmap writes when deleting elements (bsc#1235426).\n- CVE-2024-56617: cacheinfo: Allocate memory during CPU hotplug if not done from the primary CPU (bsc#1235429).\n- CVE-2024-56620: scsi: ufs: qcom: Only free platform MSIs when ESI is enabled (bsc#1235227).\n- CVE-2024-56622: scsi: ufs: core: sysfs: Prevent div by zero (bsc#1235251).\n- CVE-2024-56631: scsi: sg: Fix slab-use-after-free read in sg_release() (bsc#1235480).\n- CVE-2024-56635: net: avoid potential UAF in default_operstate() (bsc#1235519).\n- CVE-2024-56636: geneve: do not assume mac header is set in geneve_xmit_skb() (bsc#1235520).\n- CVE-2024-56637: netfilter: ipset: Hold module reference while requesting a module (bsc#1235523).\n- CVE-2024-56641: net/smc: initialize close_work early to avoid warning (bsc#1235526).\n- CVE-2024-56643: dccp: Fix memory leak in dccp_feat_change_recv (bsc#1235132).\n- CVE-2024-56648: net: hsr: avoid potential out-of-bound access in fill_frame_info() (bsc#1235451).\n- CVE-2024-56649: net: enetc: Do not configure preemptible TCs if SIs do not support (bsc#1235449).\n- CVE-2024-56650: netfilter: x_tables: fix LED ID check in led_tg_check() (bsc#1235430).\n- CVE-2024-56656: bnxt_en: Fix aggregation ID mask to prevent oops on 5760X chips (bsc#1235444).\n- CVE-2024-56659: net: lapb: increase LAPB_HEADER_LEN (bsc#1235439).\n- CVE-2024-56660: net/mlx5: DR, prevent potential error pointer dereference (bsc#1235437).\n- CVE-2024-56664: bpf, sockmap: Fix race between element replace and close() (bsc#1235249).\n- CVE-2024-56665: bpf,perf: Fix invalid prog_array access in perf_event_detach_bpf_prog (bsc#1235489).\n- CVE-2024-56675: bpf: Fix UAF via mismatching bpf_prog/attachment RCU flavors (bsc#1235555).\n- CVE-2024-56679: octeontx2-pf: handle otx2_mbox_get_rsp errors in otx2_common.c (bsc#1235498).\n- CVE-2024-56693: brd: defer automatic disk creation until module initialization succeeds (bsc#1235418).\n- CVE-2024-56694: bpf: fix recursive lock when verdict program return SK_PASS (bsc#1235412).\n- CVE-2024-56704: 9p/xen: fix release of IRQ (bsc#1235584).\n- CVE-2024-56707: octeontx2-pf: handle otx2_mbox_get_rsp errors in otx2_dmac_flt.c (bsc#1235545).\n- CVE-2024-56708: EDAC/igen6: Avoid segmentation fault on module unload (bsc#1235564).\n- CVE-2024-56712: udmabuf: fix memory leak on last export_udmabuf() error path (bsc#1235565).\n- CVE-2024-56715: ionic: Fix netdev notifier unregister on failure (bsc#1235612).\n- CVE-2024-56716: netdevsim: prevent bad user input in nsim_dev_health_break_write() (bsc#1235587).\n- CVE-2024-56725: octeontx2-pf: handle otx2_mbox_get_rsp errors in otx2_dcbnl.c (bsc#1235578).\n- CVE-2024-56726: octeontx2-pf: handle otx2_mbox_get_rsp errors in cn10k.c (bsc#1235582).\n- CVE-2024-56727: octeontx2-pf: handle otx2_mbox_get_rsp errors in otx2_flows.c (bsc#1235583).\n- CVE-2024-56728: octeontx2-pf: handle otx2_mbox_get_rsp errors in otx2_ethtool.c (bsc#1235656).\n- CVE-2024-56729: smb: Initialize cfid-\u003etcon before performing network ops (bsc#1235503).\n- CVE-2024-56747: scsi: qedi: Fix a possible memory leak in qedi_alloc_and_init_sb() (bsc#1234934).\n- CVE-2024-56748: scsi: qedf: Fix a possible memory leak in qedf_alloc_and_init_sb() (bsc#1235627).\n- CVE-2024-56755: netfs/fscache: Add a memory barrier for FSCACHE_VOLUME_CREATING (bsc#1234920).\n- CVE-2024-56759: btrfs: fix use-after-free when COWing tree bock and tracing is enabled (bsc#1235645).\n- CVE-2024-56763: tracing: Prevent bad count for tracing_cpumask_write (bsc#1235638).\n- CVE-2024-56774: btrfs: add a sanity check for btrfs root in btrfs_search_slot() (bsc#1235653).\n- CVE-2024-56775: drm/amd/display: Fix handling of plane refcount (bsc#1235657).\n- CVE-2024-57791: net/smc: check return value of sock_recvmsg when draining clc data (bsc#1235759).\n- CVE-2024-57793: virt: tdx-guest: Just leak decrypted memory on unrecoverable errors (bsc#1235768).\n- CVE-2024-57795: RDMA/rxe: Remove the direct link to net_device (bsc#1235906).\n- CVE-2024-57801: net/mlx5e: Skip restore TC rules for vport rep without loaded flag (bsc#1235940).\n- CVE-2024-57802: netrom: check buffer length before accessing it (bsc#1235941).\n- CVE-2024-57804: scsi: mpi3mr: Fix corrupt config pages PHY state is switched in sysfs (bsc#1235779).\n- CVE-2024-57809: PCI: imx6: Fix suspend/resume support on i.MX6QDL (bsc#1235793).\n- CVE-2024-57838: s390/entry: Mark IRQ entries to fix stack depot warnings (bsc#1235798).\n- CVE-2024-57857: RDMA/siw: Remove direct link to net_device (bsc#1235946).\n- CVE-2024-57884: mm: vmscan: account for free pages to prevent infinite Loop in throttle_direct_reclaim() (bsc#1235948).\n- CVE-2024-57892: ocfs2: fix slab-use-after-free due to dangling pointer dqi_priv (bsc#1235964).\n- CVE-2024-57896: btrfs: flush delalloc workers queue before stopping cleaner kthread during unmount (bsc#1235965).\n- CVE-2024-57903: net: restrict SO_REUSEPORT to inet sockets (bsc#1235967).\n- CVE-2024-57917: topology: Keep the cpumask unchanged when printing cpumap (bsc#1236127).\n- CVE-2024-57929: dm array: fix releasing a faulty array block twice in dm_array_cursor_end (bsc#1236096).\n- CVE-2024-57931: selinux: ignore unknown extended permissions (bsc#1236192).\n- CVE-2024-57932: gve: guard XDP xmit NDO on existence of xdp queues (bsc#1236190).\n- CVE-2024-57933: gve: guard XSK operations on the existence of queues (bsc#1236178).\n- CVE-2024-57938: net/sctp: Prevent autoclose integer overflow in sctp_association_init() (bsc#1236182).\n- CVE-2024-57946: virtio-blk: do not keep queue frozen during system suspend (bsc#1236247).\n- CVE-2025-21632: x86/fpu: Ensure shadow stack is active before \"getting\" registers (bsc#1236106).\n- CVE-2025-21649: net: hns3: fix kernel crash when 1588 is sent on HIP08 devices (bsc#1236143).\n- CVE-2025-21650: net: hns3: fixed hclge_fetch_pf_reg accesses bar space out of bounds issue (bsc#1236144).\n- CVE-2025-21651: net: hns3: do not auto enable misc vector (bsc#1236145).\n- CVE-2025-21652: ipvlan: Fix use-after-free in ipvlan_get_iflink() (bsc#1236160).\n- CVE-2025-21653: net_sched: cls_flow: validate TCA_FLOW_RSHIFT attribute (bsc#1236161).\n- CVE-2025-21655: io_uring/eventfd: ensure io_eventfd_signal() defers another RCU period (bsc#1236163).\n- CVE-2025-21662: net/mlx5: Fix variable not being completed when function returns (bsc#1236198).\n- CVE-2025-21663: net: stmmac: dwmac-tegra: Read iommu stream id from device tree (bsc#1236260).\n- CVE-2025-21664: dm thin: make get_first_thin use rcu-safe list first function (bsc#1236262).\n- CVE-2025-21674: net/mlx5e: Fix inversion dependency warning while enabling IPsec tunnel (bsc#1236688).\n- CVE-2025-21676: net: fec: handle page_pool_dev_alloc_pages error (bsc#1236696).\n- CVE-2025-21682: eth: bnxt: always recalculate features after XDP clearing, fix null-deref (bsc#1236703).\n\nFeatures added:\n\n  * - Disable ceph (jsc#PED-7242)\n  * - RAS/AMD/ATL: Translate normalized to system physical addresses using PRM (jsc#PED-10467).\n  * - ACPI: PRM: Add PRM handler direct call support (jsc#PED-10467).\n  * - supported.conf: Add support for v4l2-dv-timings  (jsc#PED-8645)\n\n\nThe following non-security bugs were fixed:\n\n- 9p: v9fs_fid_find: also lookup by inode if not found dentry (git-fixes).\n- ACPI/HMAT: Move HMAT messages to pr_debug() (bsc#1234294)\n- ACPI/IORT: Add PMCG platform information for HiSilicon HIP09A (stable-fixes).\n- ACPI/IORT: Add PMCG platform information for HiSilicon HIP10/11 (stable-fixes).\n- ACPI: PCC: Add PCC shared memory region command and status bitfields (stable-fixes).\n- ACPI: PRM: Add PRM handler direct call support (jsc#PED-10467).\n- ACPI: fan: cleanup resources in the error path of .probe() (git-fixes).\n- ACPI: resource: Add Asus Vivobook X1504VAP to irq1_level_low_skip_override[] (stable-fixes).\n- ACPI: resource: Add TongFang GM5HG0A to irq1_edge_low_force_override[] (stable-fixes).\n- ACPI: resource: Fix memory resource type union access (git-fixes).\n- ACPI: resource: acpi_dev_irq_override(): Check DMI match last (stable-fixes).\n- ACPI: x86: Add skip i2c clients quirk for Acer Iconia One 8 A1-840 (stable-fixes).\n- ACPI: x86: Clean up Asus entries in acpi_quirk_skip_dmi_ids[] (stable-fixes).\n- ACPI: x86: Make UART skip quirks work on PCI UARTs without an UID (stable-fixes).\n- ACPICA: events/evxfregn: do not release the ContextMutex that was never acquired (git-fixes).\n- ALSA hda/realtek: Add quirk for Framework F111:000C (stable-fixes).\n- ALSA: hda/hdmi: Yet more pin fix for HP EliteDesk 800 G4 (stable-fixes).\n- ALSA: hda/realtek - Add support for ASUS Zen AIO 27 Z272SD_A272SD audio (stable-fixes).\n- ALSA: hda/realtek - Fixed headphone distorted sound on Acer Aspire A115-31 laptop (git-fixes).\n- ALSA: hda/realtek: Add Framework Laptop 13 (Intel Core Ultra) to quirks (stable-fixes).\n- ALSA: hda/realtek: Add new alc2xx-fixup-headset-mic model (stable-fixes).\n- ALSA: hda/realtek: Add support for Ayaneo System using CS35L41 HDA (stable-fixes).\n- ALSA: hda/realtek: Add support for Galaxy Book2 Pro (NP950XEE) (stable-fixes).\n- ALSA: hda/realtek: Enable Mute LED on HP Laptop 14s-fq1xxx (stable-fixes).\n- ALSA: hda/realtek: Enable headset mic on Positivo C6400 (stable-fixes).\n- ALSA: hda/realtek: Fix headset mic on Acer Nitro 5 (stable-fixes).\n- ALSA: hda/realtek: Workaround for resume on Dell Venue 11 Pro 7130 (bsc#1235686).\n- ALSA: hda: Add HP MP9 G4 Retail System AMS to force connect list (stable-fixes).\n- ALSA: hda: Fix headset detection failure due to unstable sort (git-fixes).\n- ALSA: line6: Fix racy access to midibuf (stable-fixes).\n- ALSA: seq: Check UMP support for midi_version change (git-fixes).\n- ALSA: seq: oss: Fix races at processing SysEx messages (stable-fixes).\n- ALSA: seq: ump: Fix seq port updates per FB info notify (git-fixes).\n- ALSA: seq: ump: Use automatic cleanup of kfree() (stable-fixes).\n- ALSA: seq: ump: Use guard() for locking (stable-fixes).\n- ALSA: ump: Use guard() for locking (stable-fixes).\n- ALSA: usb-audio: Add delay quirk for USB Audio Device (stable-fixes).\n- ALSA: usb-audio: Add delay quirk for iBasso DC07 Pro (stable-fixes).\n- ALSA: usb-audio: Add implicit feedback quirk for Yamaha THR5 (stable-fixes).\n- ALSA: usb-audio: Notify xrun for low-latency mode (git-fixes).\n- ALSA: usb-audio: Re-add ScratchAmp quirk entries (git-fixes).\n- ALSA: usb-audio: US16x08: Initialize array before use (git-fixes).\n- ASoC: Intel: avs: Fix theoretical infinite loop (git-fixes).\n- ASoC: Intel: sof_sdw: add quirk for Dell SKU 0B8C (stable-fixes).\n- ASoC: Intel: sof_sdw: fix jack detection on ADL-N variant RVP (stable-fixes).\n- ASoC: SOF: Remove libraries from topology lookups (git-fixes).\n- ASoC: acp: Support microphone from Lenovo Go S (stable-fixes).\n- ASoC: amd: yc: Add a quirk for microfone on Lenovo ThinkPad P14s Gen 5 21MES00B00 (stable-fixes).\n- ASoC: amd: yc: Add quirk for microphone on Lenovo Thinkpad T14s Gen 6 21M1CTO1WW (stable-fixes).\n- ASoC: amd: yc: Fix the wrong return value (git-fixes).\n- ASoC: amd: yc: Support mic on HP 14-em0002la (stable-fixes).\n- ASoC: amd: yc: Support mic on Lenovo Thinkpad E14 Gen 6 (stable-fixes).\n- ASoC: amd: yc: fix internal mic on Redmi G 2022 (stable-fixes).\n- ASoC: codecs: wcd938x-sdw: Correct Soundwire ports mask (git-fixes).\n- ASoC: codecs: wsa881x: Correct Soundwire ports mask (git-fixes).\n- ASoC: codecs: wsa883x: Correct Soundwire ports mask (git-fixes).\n- ASoC: codecs: wsa884x: Correct Soundwire ports mask (git-fixes).\n- ASoC: cs35l56: Handle OTP read latency over SoundWire (stable-fixes).\n- ASoC: cs35l56: Patch CS35L56_IRQ1_MASK_18 to the default value (stable-fixes).\n- ASoC: fsl_micfil: Expand the range of FIFO watermark mask (stable-fixes).\n- ASoC: hdmi-codec: reorder channel allocation list (stable-fixes).\n- ASoC: mediatek: disable buffer pre-allocation (stable-fixes).\n- ASoC: meson: axg-fifo: fix irq scheduling issue with PREEMPT_RT (git-fixes).\n- ASoC: nau8822: Lower debug print priority (stable-fixes).\n- ASoC: rockchip: i2s_tdm: Re-add the set_sysclk callback (git-fixes).\n- ASoC: rt722: add delay time to wait for the calibration procedure (stable-fixes).\n- ASoC: samsung: Add missing depends on I2C (git-fixes).\n- ASoC: samsung: Add missing selects for MFD_WM8994 (stable-fixes).\n- ASoC: sun4i-spdif: Add clock multiplier settings (git-fixes).\n- ASoC: wm8994: Add depends on MFD core (stable-fixes).\n- Add already cherry-picked ids to AMDGPU patch\n- Align git commit ID abbreviation guidelines and checks (git-fixes).\n- Bluetooth: Add support ITTIM PE50-M75C (stable-fixes).\n- Bluetooth: Fix type of len in rfcomm_sock_getsockopt{,_old}() (stable-fixes).\n- Bluetooth: ISO: Reassociate a socket with an active BIS (stable-fixes).\n- Bluetooth: L2CAP: accept zero as a special value for MTU auto-selection (git-fixes).\n- Bluetooth: L2CAP: do not leave dangling sk pointer on error in l2cap_sock_create() (stable-fixes).\n- Bluetooth: L2CAP: handle NULL sock pointer in l2cap_sock_alloc (git-fixes).\n- Bluetooth: MGMT: Fix Add Device to responding before completing (git-fixes).\n- Bluetooth: MGMT: Fix possible deadlocks (git-fixes).\n- Bluetooth: SCO: Add support for 16 bits transparent voice setting (git-fixes).\n- Bluetooth: btnxpuart: Fix driver sending truncated data (git-fixes).\n- Bluetooth: btnxpuart: Fix glitches seen in dual A2DP streaming (git-fixes).\n- Bluetooth: btusb: Add RTL8852BE device 0489:e123 to device tables (stable-fixes).\n- Bluetooth: btusb: Add USB HW IDs for MT7921/MT7922/MT7925 (stable-fixes).\n- Bluetooth: btusb: Add new VID/PID 0489/e111 for MT7925 (stable-fixes).\n- Bluetooth: btusb: Add new VID/PID 13d3/3602 for MT7925 (stable-fixes).\n- Bluetooth: btusb: add callback function in btusb suspend/resume (stable-fixes).\n- Bluetooth: btusb: mediatek: add callback function in btusb_disconnect (stable-fixes).\n- Bluetooth: hci_core: Fix not checking skb length on hci_acldata_packet (stable-fixes).\n- Bluetooth: hci_event: Fix using rcu_read_(un)lock while iterating (git-fixes).\n- Bluetooth: hci_sync: Fix not setting Random Address when required (git-fixes).\n- Bluetooth: iso: Fix recursive locking warning (git-fixes).\n- Delete XHCI patch for regression (bsc#1235550)\n- Disable ceph (jsc#PED-7242)\n- Documentation: PM: Clarify pm_runtime_resume_and_get() return value (git-fixes).\n- Drivers: hv: util: Avoid accessing a ringbuffer not initialized yet (git-fixes).\n- Drop downstream TPM fix patch (bsc#1233260 bsc#1233259 bsc#1232421)\n- Drop uvcvideo fix due to regression (bsc#1235894)\n- EDAC/{i10nm,skx,skx_common}: Support UV systems (bsc#1234693).\n- HID: core: Fix assumption that Resolution Multipliers must be in Logical Collections (git-fixes).\n- HID: fix generic desktop D-Pad controls (git-fixes).\n- HID: hid-sensor-hub: do not use stale platform-data on remove (git-fixes).\n- HID: hid-thrustmaster: Fix warning in thrustmaster_probe by adding endpoint check (git-fixes).\n- HID: magicmouse: Apple Magic Trackpad 2 USB-C driver support (stable-fixes).\n- HID: multitouch: fix support for Goodix PID 0x01e9 (git-fixes).\n- Input: atkbd - map F23 key to support default copilot shortcut (stable-fixes).\n- Input: bbnsm_pwrkey - add remove hook (git-fixes).\n- Input: bbnsm_pwrkey - fix missed key press after suspend (git-fixes).\n- Input: davinci-keyscan - remove leftover header (git-fixes).\n- Input: xpad - add QH Electronics VID/PID (stable-fixes).\n- Input: xpad - add support for Nacon Evol-X Xbox One Controller (stable-fixes).\n- Input: xpad - add support for Nacon Pro Compact (stable-fixes).\n- Input: xpad - add support for wooting two he (arm) (stable-fixes).\n- Input: xpad - add unofficial Xbox 360 wireless receiver clone (stable-fixes).\n- Input: xpad - improve name of 8BitDo controller 2dc8:3106 (stable-fixes).\n- KVM: SVM: Allow guest writes to set MSR_AMD64_DE_CFG bits (bsc#1234635).\n- KVM: s390: Reject KVM_SET_GSI_ROUTING on ucontrol VMs (git-fixes bsc#1235776).\n- KVM: s390: Reject setting flic pfault attributes on ucontrol VMs (git-fixes bsc#1235777).\n- KVM: s390: vsie: fix virtual/physical address in unpin_scb() (git-fixes bsc#1235778).\n- Move kABI workaround patch to correct folder\n- Move upstreamed DRM patch into sorted section\n- Move upstreamed NFS patch into sorted section\n- Move upstreamed TPM patch into sorted section\n- Move upstreamed lpfc patches into sorted section\n- Move upstreamed ppc patch into sorted section\n- Move upstreamed sound patch into sorted section\n- Move upstreamed sound patches into sorted section\n- NFC: nci: Add bounds checking in nci_hci_create_pipe() (git-fixes).\n- NFS/pnfs: Fix a live lock between recalled layouts and layoutget (git-fixes).\n- NFSD: Async COPY result needs to return a write verifier (git-fixes).\n- NFSD: Cap the number of bytes copied by nfs4_reset_recoverydir() (git-fixes).\n- NFSD: Fix nfsd4_shutdown_copy() (git-fixes).\n- NFSD: Prevent NULL dereference in nfsd4_process_cb_update() (git-fixes).\n- NFSD: Prevent a potential integer overflow (git-fixes).\n- NFSD: Remove a never-true comparison (git-fixes).\n- NFSD: initialize copy-\u003ecp_clp early in nfsd4_copy for use by trace point (git-fixes).\n- NFSv4.0: Fix a use-after-free problem in the asynchronous open() (git-fixes).\n- NFSv4.2: fix COPY_NOTIFY xdr buf size calculation (git-fixes).\n- NFSv4.2: mark OFFLOAD_CANCEL MOVEABLE (git-fixes).\n- Octeontx2-pf: Free send queue buffers incase of leaf to inner (git-fixes).\n- PCI/AER: Disable AER service on suspend (stable-fixes).\n- PCI/MSI: Handle lack of irqdomain gracefully (git-fixes).\n- PCI: Add 'reset_subordinate' to reset hierarchy below bridge (stable-fixes).\n- PCI: Add ACS quirk for Broadcom BCM5760X NIC (stable-fixes).\n- PCI: Add ACS quirk for Wangxun FF5xxx NICs (stable-fixes).\n- PCI: Add T_PERST_CLK_US macro (git-fixes).\n- PCI: Avoid putting some root ports into D3 on TUXEDO Sirius Gen1 (git-fixes).\n- PCI: Detect and trust built-in Thunderbolt chips (stable-fixes).\n- PCI: Fix use-after-free of slot-\u003ebus on hot remove (stable-fixes).\n- PCI: Use preserve_config in place of pci_flags (stable-fixes).\n- PCI: cadence: Extract link setup sequence from cdns_pcie_host_setup() (stable-fixes).\n- PCI: cadence: Set cdns_pcie_host_init() global (stable-fixes).\n- PCI: cpqphp: Use PCI_POSSIBLE_ERROR() to check config reads (stable-fixes).\n- PCI: dwc: Always stop link in the dw_pcie_suspend_noirq (git-fixes).\n- PCI: dwc: ep: Prevent changing BAR size/flags in pci_epc_set_bar() (git-fixes).\n- PCI: dwc: ep: Write BAR_MASK before iATU registers in pci_epc_set_bar() (git-fixes).\n- PCI: endpoint: Destroy the EPC device in devm_pci_epc_destroy() (git-fixes).\n- PCI: endpoint: Finish virtual EP removal in pci_epf_remove_vepf() (git-fixes).\n- PCI: endpoint: pci-epf-test: Fix check for DMA MEMCPY test (git-fixes).\n- PCI: endpoint: pci-epf-test: Set dma_chan_rx pointer to NULL on error (git-fixes).\n- PCI: imx6: Deassert apps_reset in imx_pcie_deassert_core_reset() (git-fixes).\n- PCI: imx6: Skip controller_id generation logic for i.MX7D (git-fixes).\n- PCI: j721e: Add PCIe 4x lane selection support (stable-fixes).\n- PCI: j721e: Add per platform maximum lane settings (stable-fixes).\n- PCI: j721e: Add reset GPIO to struct j721e_pcie (stable-fixes).\n- PCI: j721e: Add suspend and resume support (git-fixes).\n- PCI: j721e: Use T_PERST_CLK_US macro (git-fixes).\n- PCI: microchip: Set inbound address translation for coherent or non-coherent mode (git-fixes).\n- PCI: qcom: Add support for IPQ9574 (stable-fixes).\n- PCI: rcar-ep: Fix incorrect variable used when calling devm_request_mem_region() (git-fixes).\n- PCI: vmd: Add DID 8086:B06F and 8086:B60B for Intel client SKUs (stable-fixes).\n- PCI: vmd: Set devices to D0 before enabling PM L1 Substates (stable-fixes).\n- PM: hibernate: Add error handling for syscore_suspend() (git-fixes).\n- RAS/AMD/ATL: Translate normalized to system physical addresses using PRM (jsc#PED-10467).\n- RDMA/bnxt_re: Add check for path mtu in modify_qp (git-fixes)\n- RDMA/bnxt_re: Add send queue size check for variable wqe (git-fixes)\n- RDMA/bnxt_re: Avoid initializing the software queue for user queues (git-fixes)\n- RDMA/bnxt_re: Avoid sending the modify QP workaround for latest adapters (git-fixes)\n- RDMA/bnxt_re: Disable use of reserved wqes (git-fixes)\n- RDMA/bnxt_re: Fix MSN table size for variable wqe mode (git-fixes)\n- RDMA/bnxt_re: Fix max SGEs for the Work Request (git-fixes)\n- RDMA/bnxt_re: Fix max_qp_wrs reported (git-fixes)\n- RDMA/bnxt_re: Fix reporting hw_ver in query_device (git-fixes)\n- RDMA/bnxt_re: Fix the check for 9060 condition (git-fixes)\n- RDMA/bnxt_re: Fix the locking while accessing the QP table (git-fixes)\n- RDMA/bnxt_re: Fix the max WQE size for static WQE support (git-fixes)\n- RDMA/bnxt_re: Fix the max WQEs used in Static WQE mode (git-fixes)\n- RDMA/bnxt_re: Fix to drop reference to the mmap entry in case of error (git-fixes)\n- RDMA/bnxt_re: Fix to export port num to ib_query_qp (git-fixes)\n- RDMA/bnxt_re: Remove always true dattr validity check (git-fixes)\n- RDMA/core: Fix ENODEV error for iWARP test over vlan (git-fixes)\n- RDMA/hns: Fix accessing invalid dip_ctx during destroying QP (git-fixes)\n- RDMA/hns: Fix mapping error of zero-hop WQE buffer (git-fixes)\n- RDMA/hns: Fix missing flush CQE for DWQE (git-fixes)\n- RDMA/hns: Fix warning storm caused by invalid input in IO path (git-fixes)\n- RDMA/mlx4: Avoid false error about access to uninitialized gids array (git-fixes)\n- RDMA/mlx5: Enforce same type port association for multiport RoCE (git-fixes)\n- RDMA/mlx5: Fix a race for an ODP MR which leads to CQE with error (git-fixes)\n- RDMA/mlx5: Fix implicit ODP use after free (git-fixes)\n- RDMA/mlx5: Fix indirect mkey ODP page count (git-fixes)\n- RDMA/rtrs: Ensure 'ib_sge list' is accessible (git-fixes)\n- RDMA/rxe: Fix mismatched max_msg_sz (git-fixes)\n- RDMA/rxe: Fix the warning \"__rxe_cleanup+0x12c/0x170 [rdma_rxe]\" (git-fixes)\n- RDMA/srp: Fix error handling in srp_add_port (git-fixes)\n- RDMA/uverbs: Prevent integer overflow issue (git-fixes)\n- README.BRANCH: Remove copy of branch name\n- Refresh patches.suse/ALSA-hda-realtek-Add-support-for-Samsung-Galaxy-Book.patch.\n- Refresh patches.suse/cpufreq-intel_pstate-Temporarily-boost-P-state-when-.patch.\n- Revert \"HID: multitouch: Add support for lenovo Y9000P Touchpad\" (stable-fixes).\n- Revert \"block/mq-deadline: use correct way to throttling write requests\" (bsc#1234146).\n- Revert \"btrfs: fix use-after-free waiting for encoded read endios (bsc#1235128)\"\n- Revert \"drm/i915/dpt: Make DPT object unshrinkable\" (stable-fixes).\n- Revert \"igb: Disable threaded IRQ for igb_msix_other\" (git-fixes).\n- Revert \"mtd: spi-nor: core: replace dummy buswidth from addr to data\" (git-fixes).\n- Revert \"unicode: Do not special case ignorable code points\" (stable-fixes).\n- Revert \"usb: gadget: u_serial: Disable ep before setting port to null to fix the crash caused by port being null\" (stable-fixes).\n- Revert 'arm64: Kconfig: Make SME depend on BROKEN for now' This reverts commit 2ccfee6be929dd4ea49ef59a7ae686473aae40b6 CONFIG_ARM64_SME is enabled by default so some customers may rely on SME. We need further analysis to evaluate to what extent we are impacted and in case we'll disable SME support later.\n- Revert 0dd78566990 (\"Disable ceph (jsc#PED-7242)\") Apparently, jsc#PED-7242 is only deprecate ceph for 15-SP6 and disable for 15-SP7. Revert the disabling.\n- SUNRPC: make sure cache entry active before cache_show (git-fixes).\n- SUNRPC: timeout and cancel TLS handshake with -ETIMEDOUT (git-fixes).\n- USB: core: Disable LPM only for non-suspended ports (git-fixes).\n- USB: serial: cp210x: add Phoenix Contact UPS Device (stable-fixes).\n- USB: serial: option: add MediaTek T7XX compositions (stable-fixes).\n- USB: serial: option: add MeiG Smart SLM770A (stable-fixes).\n- USB: serial: option: add MeiG Smart SRM815 (stable-fixes).\n- USB: serial: option: add Neoway N723-EA support (stable-fixes).\n- USB: serial: option: add Netprisma LCUK54 modules for WWAN Ready (stable-fixes).\n- USB: serial: option: add TCL IK512 MBIM \u0026 ECM (stable-fixes).\n- USB: serial: option: add Telit FE910C04 rmnet compositions (stable-fixes).\n- USB: serial: quatech2: fix null-ptr-deref in qt2_process_read_urb() (git-fixes).\n- USB: usblp: return error when setting unsupported protocol (git-fixes).\n- VFS: use system_unbound_wq for delayed_mntput (bsc#1234683).\n- VMCI: fix reference to ioctl-number.rst (git-fixes).\n- accel/habanalabs/gaudi2: unsecure tpc count registers (stable-fixes).\n- accel/habanalabs: export dma-buf only if size/offset multiples of PAGE_SIZE (stable-fixes).\n- accel/habanalabs: fix debugfs files permissions (stable-fixes).\n- accel/habanalabs: increase HL_MAX_STR to 64 bytes to avoid warnings (stable-fixes).\n- acpi: nfit: vmalloc-out-of-bounds Read in acpi_nfit_ctl (git-fixes).\n- af_unix: Call manage_oob() for every skb in unix_stream_read_generic() (bsc#1234725).\n- afs: Automatically generate trace tag enums (git-fixes).\n- afs: Fix EEXIST error returned from afs_rmdir() to be ENOTEMPTY (git-fixes).\n- afs: Fix cleanup of immediately failed async calls (git-fixes).\n- afs: Fix directory format encoding struct (git-fixes).\n- afs: Fix missing subdir edit when renamed between parent dirs (git-fixes).\n- afs: Fix the fallback handling for the YFS.RemoveFile2 RPC call (git-fixes).\n- afs: Fix the maximum cell name length (git-fixes).\n- amdgpu/uvd: get ring reference from rq scheduler (git-fixes).\n- arch: Introduce arch_{,try_}_cmpxchg128{,_local}() (bsc#1220773).\n- arch: Remove cmpxchg_double (bsc#1220773).\n- arch: consolidate arch_irq_work_raise prototypes (git-fixes).\n- arm64/sme: Move storage of reg_smidr to __cpuinfo_store_cpu() (git-fixes)\n- arm64: Ensure bits ASID[15:8] are masked out when the kernel uses (bsc#1234605)\n- arm64: Filter out SVE hwcaps when FEAT_SVE isn't implemented (git-fixes)\n- arm64: Force position-independent veneers (git-fixes).\n- arm64: Kconfig: Make SME depend on BROKEN for now (git-fixes bsc#1236245) Update arm64 default configuration file\n- arm64: Kconfig: Make SME depend on BROKEN for now (git-fixes).\n- arm64: dts: imx8mp: correct sdhc ipg clk (git-fixes).\n- arm64: dts: rockchip: Add sdmmc/sdio/emmc reset controls for RK3328 (git-fixes)\n- arm64: dts: rockchip: add hevc power domain clock to rk3328 (git-fixes).\n- arm64: dts: rockchip: increase gmac rx_delay on rk3399-puma (git-fixes)\n- arm64: ptrace: fix partial SETREGSET for NT_ARM_TAGGED_ADDR_CTRL (git-fixes).\n- arm64: tegra: Disable Tegra234 sce-fabric node (git-fixes)\n- arm64: tegra: Fix Tegra234 PCIe interrupt-map (git-fixes)\n- arm64: tegra: Fix typo in Tegra234 dce-fabric compatible (git-fixes)\n- ata: libata-core: Set ATA_QCFLAG_RTF_FILLED in fill_result_tf() (stable-fixes).\n- autofs: fix memory leak of waitqueues in autofs_catatonic_mode (git-fixes).\n- batman-adv: Do not let TT changes list grows indefinitely (git-fixes).\n- batman-adv: Do not send uninitialized TT changes (git-fixes).\n- batman-adv: Remove uninitialized data in full table TT response (git-fixes).\n- blacklist.conf: printk/sysctl: breaks kernel without pre-requisite patches (bsc#1229025)\n- blk-cgroup: Fix UAF in blkcg_unpin_online() (bsc#1234726).\n- blk-core: use pr_warn_ratelimited() in bio_check_ro() (bsc#1234139).\n- blk-iocost: Fix an UBSAN shift-out-of-bounds warning (bsc#1234144).\n- blk-iocost: do not WARN if iocg was already offlined (bsc#1234147).\n- blk-throttle: fix lockdep warning of \"cgroup_mutex or RCU read lock required!\" (bsc#1234140).\n- block, bfq: choose the last bfqq from merge chain in bfq_setup_cooperator() (bsc#1234149).\n- block, bfq: do not break merge chain in bfq_split_bfqq() (bsc#1234150).\n- block, bfq: fix bfqq uaf in bfq_limit_depth() (bsc#1234160).\n- block, bfq: fix procress reference leakage for bfqq in merge chain (bsc#1234280).\n- block, bfq: fix uaf for accessing waker_bfqq after splitting (bsc#1234279).\n- block/mq-deadline: Fix the tag reservation code (bsc#1234148).\n- block: Call .limit_depth() after .hctx has been set (bsc#1234148).\n- block: Fix where bio IO priority gets set (bsc#1234145).\n- block: prevent an integer overflow in bvec_try_merge_hw_page (bsc#1234142).\n- block: update the stable_writes flag in bdev_add (bsc#1234141).\n- bnxt_en: Fix GSO type for HW GRO packets on 5750X chips (git-fixes)\n- bnxt_en: Fix receive ring space parameters when XDP is active (git-fixes).\n- bnxt_en: Reserve rings after PCIe AER recovery if NIC interface is down (git-fixes).\n- bnxt_en: Set backplane link modes correctly for ethtool (git-fixes).\n- bpf, x86: Fix PROBE_MEM runtime load check (git-fixes).\n- bpf: verifier: prevent userspace memory access (git-fixes).\n- btrfs: fix use-after-free in btrfs_encoded_read_endio() (bsc#1235445).\n- btrfs: fix use-after-free waiting for encoded read endios (bsc#1235128)\n- btrfs: fix use-after-free waiting for encoded read endios (bsc#1235445).\n- bus: mhi: host: Free mhi_buf vector inside mhi_alloc_bhie_table() (git-fixes).\n- can: gs_usb: add VID/PID for Xylanta SAINT3 product family (stable-fixes).\n- can: j1939: fix error in J1939 documentation (stable-fixes).\n- ceph: improve error handling and short/overflow-read logic in __ceph_sync_read() (bsc#1228592).\n- checkpatch: always parse orig_commit in fixes tag (git-fixes).\n- checkpatch: check for missing Fixes tags (stable-fixes).\n- cleanup: Add conditional guard support (stable-fixes).\n- cleanup: Adjust scoped_guard() macros to avoid potential warning (stable-fixes).\n- cleanup: Remove address space of returned pointer (git-fixes).\n- clocksource/drivers/timer-ti-dm: Fix child node refcount handling (git-fixes).\n- clocksource/drivers:sp804: Make user selectable (git-fixes).\n- counter: stm32-timer-cnt: Add check for clk_enable() (git-fixes).\n- counter: ti-ecap-capture: Add check for clk_enable() (git-fixes).\n- cpufreq: ACPI: Fix max-frequency computation (git-fixes).\n- cpufreq: Do not unregister cpufreq cooling on CPU hotplug (git-fixes).\n- cpufreq: amd-pstate: remove global header file (git-fixes).\n- cpufreq: intel_pstate: Check turbo_is_disabled() in store_no_turbo() (bsc#1234619).\n- cpufreq: intel_pstate: Do not update global.turbo_disabled after initialization (bsc#1234619).\n- cpufreq: intel_pstate: Drop redundant locking from intel_pstate_driver_cleanup() (bsc#1234619).\n- cpufreq: intel_pstate: Fix unchecked HWP MSR access (bsc#1234619).\n- cpufreq: intel_pstate: Fold intel_pstate_max_within_limits() into caller (bsc#1234619).\n- cpufreq: intel_pstate: Get rid of unnecessary READ_ONCE() annotations (bsc#1234619).\n- cpufreq: intel_pstate: Make hwp_notify_lock a raw spinlock (git-fixes).\n- cpufreq: intel_pstate: Read global.no_turbo under READ_ONCE() (bsc#1234619).\n- cpufreq: intel_pstate: Rearrange show_no_turbo() and store_no_turbo() (bsc#1234619).\n- cpufreq: intel_pstate: Refine computation of P-state for given frequency (bsc#1234619).\n- cpufreq: intel_pstate: Replace three global.turbo_disabled checks (bsc#1234619).\n- cpufreq: intel_pstate: Revise global turbo disable check (bsc#1234619).\n- cpufreq: intel_pstate: Simplify spinlock locking (bsc#1234619).\n- cpufreq: intel_pstate: Update the maximum CPU frequency consistently (bsc#1234619).\n- cpufreq: intel_pstate: Use HWP to initialize ITMT if CPPC is missing (git-fixes).\n- cpufreq: intel_pstate: Use __ro_after_init for three variables (bsc#1234619).\n- cpufreq: intel_pstate: Wait for canceled delayed work to complete (bsc#1234619).\n- cpufreq: intel_pstate: fix pstate limits enforcement for adjust_perf call back (git-fixes).\n- cpuidle: Avoid potential overflow in integer multiplication (git-fixes).\n- cpupower: fix TSC MHz calculation (git-fixes).\n- crypto: caam - use JobR's space to access page 0 regs (git-fixes).\n- crypto: ecc - Prevent ecc_digits_from_bytes from reading too many bytes (git-fixes).\n- crypto: ecdsa - Avoid signed integer overflow on signature decoding (stable-fixes).\n- crypto: ecdsa - Convert byte arrays with key coordinates to digits (stable-fixes).\n- crypto: ecdsa - Rename keylen to bufsize where necessary (stable-fixes).\n- crypto: ecdsa - Use ecc_digits_from_bytes to convert signature (stable-fixes).\n- crypto: iaa - Fix IAA disabling that occurs when sync_mode is set to 'async' (git-fixes).\n- crypto: ixp4xx - fix OF node reference leaks in init_ixp_crypto() (git-fixes).\n- crypto: qat - disable IOV in adf_dev_stop() (git-fixes).\n- crypto: qce - fix goto jump in error path (git-fixes).\n- crypto: qce - fix priority to be less than ARMv8 CE (git-fixes).\n- crypto: qce - unregister previously registered algos in error path (git-fixes).\n- crypto: x86/sha256 - Add parentheses around macros' single arguments (stable-fixes).\n- cyrpto/b128ops: Remove struct u128 (bsc#1220773).\n- devcoredump: cleanup some comments (git-fixes).\n- devlink: Fix length of eswitch inline-mode (git-fixes).\n- dlm: fix possible lkb_resource null dereference (git-fixes).\n- dma-buf: fix dma_fence_array_signaled v4 (stable-fixes).\n- dma-debug: fix a possible deadlock on radix_lock (stable-fixes).\n- dmaengine: apple-admac: Avoid accessing registers in probe (git-fixes).\n- dmaengine: at_xdmac: avoid null_prt_deref in at_xdmac_prep_dma_memset (git-fixes).\n- dmaengine: dw: Select only supported masters for ACPI devices (git-fixes).\n- dmaengine: idxd: Check for driver name match before sva user feature (bsc#1234357).\n- dmaengine: mv_xor: fix child node refcount handling in early exit (git-fixes).\n- dmaengine: tegra: Return correct DMA status when paused (git-fixes).\n- dmaengine: ti: edma: fix OF node reference leaks in edma_driver (git-fixes).\n- docs: media: update location of the media patches (stable-fixes).\n- docs: power: Fix footnote reference for Toshiba Satellite P10-554 (git-fixes).\n- driver core: Add FWLINK_FLAG_IGNORE to completely ignore a fwnode link (stable-fixes).\n- driver core: class: Fix wild pointer dereferences in API class_dev_iter_next() (git-fixes).\n- driver core: fw_devlink: Improve logs for cycle detection (stable-fixes).\n- driver core: fw_devlink: Stop trying to optimize cycle detection logic (git-fixes).\n- drivers/card_reader/rtsx_usb: Restore interrupt based detection (git-fixes).\n- drivers: net: ionic: add missed debugfs cleanup to ionic_probe() error path (git-fixes).\n- drm/amd/display: Add HDR workaround for specific eDP (stable-fixes).\n- drm/amd/display: Add NULL check for clk_mgr in dcn32_init_hw (stable-fixes).\n- drm/amd/display: Add check for granularity in dml ceil/floor helpers (stable-fixes).\n- drm/amd/display: Allow backlight to go below `AMDGPU_DM_DEFAULT_MIN_BACKLIGHT` (stable-fixes).\n- drm/amd/display: Avoid overflow assignment in link_dp_cts (stable-fixes).\n- drm/amd/display: Fix DSC-re-computing (stable-fixes).\n- drm/amd/display: Fix Synaptics Cascaded Panamera DSC Determination (stable-fixes).\n- drm/amd/display: Fix incorrect DSC recompute trigger (stable-fixes).\n- drm/amd/display: Revert Avoid overflow assignment (stable-fixes).\n- drm/amd/display: Use HW lock mgr for PSR1 (stable-fixes).\n- drm/amd/display: Use gpuvm_min_page_size_kbytes for DML2 surfaces (stable-fixes).\n- drm/amd/display: increase MAX_SURFACES to the value supported by hw (stable-fixes).\n- drm/amd/pm: Fix an error handling path in vega10_enable_se_edc_force_stall_config() (git-fixes).\n- drm/amd/pm: fix the high voltage issue after unload (stable-fixes).\n- drm/amd/pm: update current_socclk and current_uclk in gpu_metrics on smu v13.0.7 (stable-fixes).\n- drm/amdgpu/gfx10: use rlc safe mode for soft recovery (stable-fixes).\n- drm/amdgpu/gfx11: use rlc safe mode for soft recovery (stable-fixes).\n- drm/amdgpu/gfx9: properly handle error ints on all pipes (stable-fixes).\n- drm/amdgpu/gfx9: use rlc safe mode for soft recovery (stable-fixes).\n- drm/amdgpu/hdp5.2: do a posting read when flushing HDP (stable-fixes).\n- drm/amdgpu/pm: Remove gpu_od if it's an empty directory (stable-fixes).\n- drm/amdgpu/umsch: do not execute umsch test when GPU is in reset/suspend (stable-fixes).\n- drm/amdgpu/umsch: reinitialize write pointer in hw init (stable-fixes).\n- drm/amdgpu/vcn: reset fw_shared under SRIOV (git-fixes).\n- drm/amdgpu/vcn: reset fw_shared when VCPU buffers corrupted on vcn v4.0.3 (stable-fixes).\n- drm/amdgpu: Block MMR_READ IOCTL in reset (stable-fixes).\n- drm/amdgpu: Dereference the ATCS ACPI buffer (stable-fixes).\n- drm/amdgpu: Fix potential NULL pointer dereference in atomctrl_get_smc_sclk_range_table (git-fixes).\n- drm/amdgpu: add raven1 gfxoff quirk (stable-fixes).\n- drm/amdgpu: add smu 14.0.1 discovery support (stable-fixes).\n- drm/amdgpu: always sync the GFX pipe on ctx switch (stable-fixes).\n- drm/amdgpu: clear RB_OVERFLOW bit when enabling interrupts for vega20_ih (stable-fixes).\n- drm/amdgpu: differentiate external rev id for gfx 11.5.0 (stable-fixes).\n- drm/amdgpu: disallow multiple BO_HANDLES chunks in one submit (stable-fixes).\n- drm/amdgpu: do not access invalid sched (git-fixes).\n- drm/amdgpu: enable gfxoff quirk on HP 705G4 (stable-fixes).\n- drm/amdgpu: fix unchecked return value warning for amdgpu_gfx (stable-fixes).\n- drm/amdgpu: fix usage slab after free (stable-fixes).\n- drm/amdgpu: prevent BO_HANDLES error from being overwritten (git-fixes).\n- drm/amdgpu: refine error handling in amdgpu_ttm_tt_pin_userptr (stable-fixes).\n- drm/amdgpu: set the right AMDGPU sg segment limitation (stable-fixes).\n- drm/amdgpu: simplify return statement in amdgpu_ras_eeprom_init (git-fixes).\n- drm/amdgpu: skip amdgpu_device_cache_pci_state under sriov (stable-fixes).\n- drm/amdgpu: tear down ttm range manager for doorbell in amdgpu_ttm_fini() (git-fixes).\n- drm/amdkfd: Correct the migration DMA map direction (stable-fixes).\n- drm/amdkfd: Fix resource leak in criu restore queue (stable-fixes).\n- drm/amdkfd: Use device based logging for errors (stable-fixes).\n- drm/amdkfd: Use the correct wptr size (stable-fixes).\n- drm/amdkfd: fixed page fault when enable MES shader debugger (git-fixes).\n- drm/amdkfd: pause autosuspend when creating pdd (stable-fixes).\n- drm/bridge: adv7511_audio: Update Audio InfoFrame properly (git-fixes).\n- drm/bridge: it6505: Change definition of AUX_FIFO_MAX_SIZE (git-fixes).\n- drm/bridge: it6505: Enable module autoloading (stable-fixes).\n- drm/bridge: it6505: Fix inverted reset polarity (git-fixes).\n- drm/bridge: it6505: update usleep_range for RC circuit charge time (stable-fixes).\n- drm/display: Fix building with GCC 15 (stable-fixes).\n- drm/dp_mst: Ensure mst_primary pointer is valid in drm_dp_mst_handle_up_req() (stable-fixes).\n- drm/dp_mst: Fix MST sideband message body length check (stable-fixes).\n- drm/dp_mst: Fix resetting msg rx state after topology removal (git-fixes).\n- drm/dp_mst: Verify request type in the corresponding down message reply (stable-fixes).\n- drm/etnaviv: Fix page property being used for non writecombine buffers (git-fixes).\n- drm/etnaviv: flush shader L1 cache after user commandstream (stable-fixes).\n- drm/i915/dg1: Fix power gate sequence (git-fixes).\n- drm/i915/fb: Relax clear color alignment to 64 bytes (stable-fixes).\n- drm/i915: Fix NULL pointer dereference in capture_engine (git-fixes).\n- drm/i915: Fix memory leak by correcting cache object name in error handler (git-fixes).\n- drm/mcde: Enable module autoloading (stable-fixes).\n- drm/mediatek: Add return value check when reading DPCD (git-fixes).\n- drm/mediatek: Add support for 180-degree rotation in the display driver (git-fixes).\n- drm/mediatek: Fix YCbCr422 color format issue for DP (git-fixes).\n- drm/mediatek: Fix mode valid issue for dp (git-fixes).\n- drm/mediatek: Set private-\u003eall_drm_private[i]-\u003edrm to NULL if mtk_drm_bind returns err (git-fixes).\n- drm/mediatek: mtk_dsi: Add registers to pdata to fix MT8186/MT8188 (git-fixes).\n- drm/mediatek: stop selecting foreign drivers (git-fixes).\n- drm/modes: Avoid divide by zero harder in drm_mode_vrefresh() (stable-fixes).\n- drm/msm/dp: set safe_to_exit_level before printing it (git-fixes).\n- drm/msm/dpu: link DSPP_2/_3 blocks on SC8180X (git-fixes).\n- drm/msm/dpu: link DSPP_2/_3 blocks on SM8150 (git-fixes).\n- drm/msm/dpu: link DSPP_2/_3 blocks on SM8250 (git-fixes).\n- drm/msm/dpu: link DSPP_2/_3 blocks on SM8350 (git-fixes).\n- drm/msm/dpu: link DSPP_2/_3 blocks on SM8550 (git-fixes).\n- drm/msm: Check return value of of_dma_configure() (git-fixes).\n- drm/msm: do not clean up priv-\u003ekms prematurely (git-fixes).\n- drm/nouveau/gsp: Use the sg allocator for level 2 of radix3 (stable-fixes).\n- drm/panel: novatek-nt35950: fix return value check in nt35950_probe() (git-fixes).\n- drm/panel: simple: Add Microchip AC69T88A LVDS Display panel (stable-fixes).\n- drm/printer: Allow NULL data in devcoredump printer (stable-fixes).\n- drm/radeon/r100: Handle unknown family in r100_cp_init_microcode() (stable-fixes).\n- drm/radeon/r600_cs: Fix possible int overflow in r600_packet3_check() (stable-fixes).\n- drm/radeon: Fix spurious unplug event on radeon HDMI (git-fixes).\n- drm/radeon: add helper rdev_to_drm(rdev) (stable-fixes).\n- drm/radeon: change rdev-\u003eddev to rdev_to_drm(rdev) (stable-fixes).\n- drm/rcar-du: dsi: Fix PHY lock bit check (git-fixes).\n- drm/rockchip: cdn-dp: Use drm_connector_helper_hpd_irq_event() (git-fixes).\n- drm/rockchip: vop2: Check linear format for Cluster windows on rk3566/8 (git-fixes).\n- drm/rockchip: vop2: Fix cluster windows alpha ctrl regsiters offset (git-fixes).\n- drm/rockchip: vop2: Fix the mixer alpha setup for layer 0 (git-fixes).\n- drm/sched: memset() 'job' in drm_sched_job_init() (stable-fixes).\n- drm/tidss: Clear the interrupt status for interrupts being disabled (git-fixes).\n- drm/tidss: Fix issue in irq handling causing irq-flood issue (git-fixes).\n- drm/v3d: Assign job pointer to NULL before signaling the fence (git-fixes).\n- drm/v3d: Ensure job pointer is set to NULL after job completion (git-fixes).\n- drm/v3d: Stop active perfmon if it is being destroyed (git-fixes).\n- drm/vc4: hdmi: Avoid log spam for audio start failure (stable-fixes).\n- drm/vc4: hvs: Set AXI panic modes for the HVS (stable-fixes).\n- drm/vmwgfx: Add new keep_resv BO param (git-fixes).\n- drm: adv7511: Drop dsi single lane support (git-fixes).\n- drm: adv7511: Fix use-after-free in adv7533_attach_dsi() (git-fixes).\n- drm: panel-orientation-quirks: Add quirk for AYA NEO 2 model (stable-fixes).\n- drm: panel-orientation-quirks: Add quirk for AYA NEO Founder edition (stable-fixes).\n- drm: panel-orientation-quirks: Add quirk for AYA NEO GEEK (stable-fixes).\n- drm: panel-orientation-quirks: Make Lenovo Yoga Tab 3 X90F DMI match less strict (stable-fixes).\n- erofs: avoid debugging output for (de)compressed data (git-fixes).\n- exfat: ensure that ctime is updated whenever the mtime is (git-fixes).\n- exfat: fix the infinite loop in __exfat_free_cluster() (git-fixes).\n- exfat: fix the infinite loop in exfat_readdir() (git-fixes).\n- exfat: fix uninit-value in __exfat_get_dentry_set (git-fixes).\n- ext4: add a new helper to check if es must be kept (bsc#1234170).\n- ext4: add correct group descriptors and reserved GDT blocks to system zone (bsc#1234164).\n- ext4: add missed brelse in update_backups (bsc#1234171).\n- ext4: allow for the last group to be marked as trimmed (bsc#1234278).\n- ext4: avoid buffer_head leak in ext4_mark_inode_used() (bsc#1234191).\n- ext4: avoid excessive credit estimate in ext4_tmpfile() (bsc#1234180).\n- ext4: avoid negative min_clusters in find_group_orlov() (bsc#1234193).\n- ext4: avoid overlapping preallocations due to overflow (bsc#1234162).\n- ext4: avoid potential buffer_head leak in __ext4_new_inode() (bsc#1234192).\n- ext4: avoid writing unitialized memory to disk in EA inodes (bsc#1234187).\n- ext4: check the extent status again before inserting delalloc block (bsc#1234186).\n- ext4: clear EXT4_GROUP_INFO_WAS_TRIMMED_BIT even mount with discard (bsc#1234190).\n- ext4: convert to exclusive lock while inserting delalloc extents (bsc#1234178).\n- ext4: correct best extent lstart adjustment logic (bsc#1234179).\n- ext4: correct grp validation in ext4_mb_good_group (bsc#1234163).\n- ext4: correct return value of ext4_convert_meta_bg (bsc#1234172).\n- ext4: correct the hole length returned by ext4_map_blocks() (bsc#1234178).\n- ext4: correct the start block of counting reserved clusters (bsc#1234169).\n- ext4: do not let fstrim block system suspend (https://bugzilla.kernel.org/show_bug.cgi?id=216322 bsc#1234166).\n- ext4: do not trim the group with corrupted block bitmap (bsc#1234177).\n- ext4: factor out __es_alloc_extent() and __es_free_extent() (bsc#1234170).\n- ext4: factor out a common helper to query extent map (bsc#1234186).\n- ext4: fix inconsistent between segment fstrim and full fstrim (bsc#1234176).\n- ext4: fix incorrect tid assumption in __jbd2_log_wait_for_space() (bsc#1234188).\n- ext4: fix incorrect tid assumption in ext4_wait_for_tail_page_commit() (bsc#1234188).\n- ext4: fix incorrect tid assumption in jbd2_journal_shrink_checkpoint_list() (bsc#1234188).\n- ext4: fix memory leaks in ext4_fname_{setup_filename,prepare_lookup} (bsc#1214954).\n- ext4: fix potential unnitialized variable (bsc#1234183).\n- ext4: fix race between writepages and remount (bsc#1234168).\n- ext4: fix rec_len verify error (bsc#1234167).\n- ext4: fix slab-use-after-free in ext4_es_insert_extent() (bsc#1234170).\n- ext4: fix uninitialized variable in ext4_inlinedir_to_tree (bsc#1234185).\n- ext4: forbid commit inconsistent quota data when errors=remount-ro (bsc#1234178).\n- ext4: make ext4_es_insert_delayed_block() return void (bsc#1234170).\n- ext4: make ext4_es_insert_extent() return void (bsc#1234170).\n- ext4: make ext4_es_remove_extent() return void (bsc#1234170).\n- ext4: make ext4_zeroout_es() return void (bsc#1234170).\n- ext4: make sure allocate pending entry not fail (bsc#1234170).\n- ext4: mark buffer new if it is unwritten to avoid stale data exposure (bsc#1234175).\n- ext4: move 'ix' sanity check to corrent position (bsc#1234174).\n- ext4: move setting of trimmed bit into ext4_try_to_trim_range() (bsc#1234165).\n- ext4: nested locking for xattr inode (bsc#1234189).\n- ext4: propagate errors from ext4_find_extent() in ext4_insert_range() (bsc#1234194).\n- ext4: refactor ext4_da_map_blocks() (bsc#1234178).\n- ext4: remove gdb backup copy for meta bg in setup_new_flex_group_blocks (bsc#1234173).\n- ext4: remove the redundant folio_wait_stable() (bsc#1234184).\n- ext4: set the type of max_zeroout to unsigned int to avoid overflow (bsc#1234182).\n- ext4: set type of ac_groups_linear_remaining to __u32 to avoid overflow (bsc#1234181).\n- ext4: use pre-allocated es in __es_insert_extent() (bsc#1234170).\n- ext4: use pre-allocated es in __es_remove_extent() (bsc#1234170).\n- ext4: using nofail preallocation in ext4_es_insert_delayed_block() (bsc#1234170).\n- ext4: using nofail preallocation in ext4_es_insert_extent() (bsc#1234170).\n- ext4: using nofail preallocation in ext4_es_remove_extent() (bsc#1234170).\n- fbdev: omapfb: Fix an OF node leak in dss_of_port_get_parent_device() (git-fixes).\n- filemap: Fix bounds checking in filemap_read() (bsc#1234209).\n- filemap: add a per-mapping stable writes flag (bsc#1234141).\n- firmware: arm_scmi: Reject clear channel request on A2P (stable-fixes).\n- fs-writeback: do not requeue a clean inode having skipped pages (bsc#1234200).\n- fs/writeback: bail out if there is no more inodes for IO and queued once (bsc#1234207).\n- fsnotify: fix sending inotify event with unexpected filename (bsc#1234198).\n- genirq/cpuhotplug: Retry with cpu_online_mask when migration fails (git-fixes).\n- genirq/cpuhotplug: Skip suspended interrupts when restoring affinity (git-fixes).\n- genirq/irqdesc: Honor caller provided affinity in alloc_desc() (git-fixes).\n- genirq: Make handle_enforce_irqctx() unconditionally available (git-fixes).\n- genksyms: fix memory leak when the same symbol is added from source (git-fixes).\n- genksyms: fix memory leak when the same symbol is read from *.symref file (git-fixes).\n- gfs2: Truncate address space when flipping GFS2_DIF_JDATA flag (git-fixes).\n- gpio: grgpio: Add NULL check in grgpio_probe (git-fixes).\n- gpio: grgpio: use a helper variable to store the address of ofdev-\u003edev (stable-fixes).\n- gpio: mxc: remove dead code after switch to DT-only (git-fixes).\n- gpio: xilinx: Convert gpio_lock to raw spinlock (git-fixes).\n- hfsplus: do not query the device logical block size multiple times (git-fixes).\n- hvc/xen: fix console unplug (git-fixes).\n- hvc/xen: fix error path in xen_hvc_init() to always register frontend driver (git-fixes).\n- hvc/xen: fix event channel handling for secondary consoles (git-fixes).\n- hwmon: (drivetemp) Fix driver producing garbage data when SCSI errors occur (git-fixes).\n- hwmon: (drivetemp) Set scsi command timeout to 10s (stable-fixes).\n- hwmon: (nct6775) Add 665-ACE/600M-CL to ASUS WMI monitoring list (stable-fixes).\n- hwmon: (pmbus/core) clear faults after setting smbalert mask (git-fixes).\n- hwmon: (pmbus_core) Allow to hook PMBUS_SMBALERT_MASK (stable-fixes).\n- hwmon: (tmp513) Do not use \"proxy\" headers (stable-fixes).\n- hwmon: (tmp513) Fix Current Register value interpretation (git-fixes).\n- hwmon: (tmp513) Fix division of negative numbers (git-fixes).\n- hwmon: (tmp513) Fix interpretation of values of Shunt Voltage and Limit Registers (git-fixes).\n- hwmon: (tmp513) Fix interpretation of values of Temperature Result and Limit Registers (git-fixes).\n- hwmon: (tmp513) Simplify with dev_err_probe() (stable-fixes).\n- hwmon: (tmp513) Use SI constants from units.h (stable-fixes).\n- hyperv: Do not overlap the hvcall IO areas in get_vtl() (git-fixes).\n- i2c: core: fix reference leak in i2c_register_adapter() (git-fixes).\n- i2c: i801: Add support for Intel Arrow Lake-H (stable-fixes).\n- i2c: i801: Add support for Intel Panther Lake (stable-fixes).\n- i2c: imx: add imx7d compatible string for applying erratum ERR007805 (git-fixes).\n- i2c: microchip-core: actually use repeated sends (git-fixes).\n- i2c: microchip-core: fix \"ghost\" detections (git-fixes).\n- i2c: mux: demux-pinctrl: check initial mux selection, too (git-fixes).\n- i2c: pnx: Fix timeout in wait functions (git-fixes).\n- i2c: rcar: fix NACK handling when being a target (git-fixes).\n- i2c: riic: Always round-up when calculating bus period (git-fixes).\n- i2c: xgene-slimpro: Migrate to use generic PCC shmem related macros (stable-fixes).\n- i40e: Fix handling changed priv flags (git-fixes).\n- i915/guc: Accumulate active runtime on gt reset (git-fixes).\n- i915/guc: Ensure busyness counter increases motonically (git-fixes).\n- i915/guc: Reset engine utilization buffer before registration (git-fixes).\n- ibmvnic: Free any outstanding tx skbs during scrq reset (bsc#1226980).\n- ice: Unbind the workqueue (bsc#1234989)\n- ice: change q_index variable type to s16 to store -1 value (git-fixes).\n- ice: consistently use q_idx in ice_vc_cfg_qs_msg() (git-fixes).\n- ice: fix PHY Clock Recovery availability check (git-fixes).\n- idpf: add support for SW triggered interrupts (bsc#1235507).\n- idpf: enable WB_ON_ITR (bsc#1235507).\n- idpf: trigger SW interrupt when exiting wb_on_itr mode (bsc#1235507).\n- ieee802154: ca8210: Add missing check for kfifo_alloc() in ca8210_probe() (git-fixes).\n- igb: Fix potential invalid memory access in igb_init_module() (git-fixes).\n- iio: adc: ad7124: Disable all channels at probe time (git-fixes).\n- iio: adc: ad_sigma_delta: Handle CS assertion as intended in ad_sd_read_reg_raw() (git-fixes).\n- iio: adc: at91: call input_free_device() on allocated iio_dev (git-fixes).\n- iio: adc: rockchip_saradc: fix information leak in triggered buffer (git-fixes).\n- iio: adc: ti-ads124s08: Use gpiod_set_value_cansleep() (git-fixes).\n- iio: adc: ti-ads8688: fix information leak in triggered buffer (git-fixes).\n- iio: dummy: iio_simply_dummy_buffer: fix information leak in triggered buffer (git-fixes).\n- iio: gyro: fxas21002c: Fix missing data update in trigger handler (git-fixes).\n- iio: iio-mux: kzalloc instead of devm_kzalloc to ensure page alignment (git-fixes).\n- iio: imu: kmx61: fix information leak in triggered buffer (git-fixes).\n- iio: inkern: call iio_device_put() only on mapped devices (git-fixes).\n- iio: light: as73211: fix channel handling in only-color triggered buffer (git-fixes).\n- iio: light: vcnl4035: fix information leak in triggered buffer (git-fixes).\n- iio: magnetometer: yas530: use signed integer type for clamp limits (git-fixes).\n- iio: pressure: zpa2326: fix information leak in triggered buffer (git-fixes).\n- iio: test : check null return of kunit_kmalloc in iio_rescale_test_scale (git-fixes).\n- instrumentation: Wire up cmpxchg128() (bsc#1220773).\n- intel_th: core: fix kernel-doc warnings (git-fixes).\n- io_uring/rw: avoid punting to io-wq directly (git-fixes).\n- io_uring/tctx: work around xa_store() allocation error issue (git-fixes).\n- io_uring: Fix registered ring file refcount leak (git-fixes).\n- io_uring: always lock __io_cqring_overflow_flush (git-fixes).\n- io_uring: check if iowq is killed before queuing (git-fixes).\n- iommu/io-pgtable-arm: Fix stage-2 map/unmap for concatenated tables (git-fixes).\n- ipmi: ipmb: Add check devm_kasprintf() returned value (git-fixes).\n- ipmi: ssif_bmc: Fix new request loss when bmc ready for a response (git-fixes).\n- irqchip/gic-v3: Force propagation of the active state with a read-back (stable-fixes).\n- irqchip/gic: Correct declaration of *percpu_base pointer in union gic_base (stable-fixes).\n- irqflags: Explicitly ignore lockdep_hrtimer_exit() argument (git-fixes).\n- isofs: handle CDs with bad root inode but good Joliet root directory (bsc#1234199).\n- ixgbe: downgrade logging of unsupported VF API version to debug (git-fixes).\n- ixgbevf: stop attempting IPSEC offload on Mailbox API 1.5 (git-fixes).\n- jffs2: Fix rtime decompressor (git-fixes).\n- jffs2: Prevent rtime decompress memory corruption (git-fixes).\n- jffs2: fix use of uninitialized variable (git-fixes).\n- jfs: add a check to prevent array-index-out-of-bounds in dbAdjTree (git-fixes).\n- jfs: array-index-out-of-bounds fix in dtReadFirst (git-fixes).\n- jfs: fix array-index-out-of-bounds in jfs_readdir (git-fixes).\n- jfs: fix shift-out-of-bounds in dbSplit (git-fixes).\n- jfs: xattr: check invalid xattr size more strictly (git-fixes).\n- kABI workaround for struct auto_pin_cfg_item change (git-fixes).\n- kABI workaround for struct drm_dp_mst_topology_mgr (git-fixes).\n- kabi/severities: make vcap_find_actionfield PASS (bsc#1220773)\n- kasan: make report_lock a raw spinlock (git-fixes).\n- kconfig: fix file name in warnings when loading KCONFIG_DEFCONFIG_LIST (git-fixes).\n- kdb: Fix buffer overflow during tab-complete (bsc#1234652).\n- kdb: Fix console handling when editing and tab-completing commands (bsc#1234655).\n- kdb: Merge identical case statements in kdb_read() (bsc#1234657).\n- kdb: Use format-specifiers rather than memset() for padding in kdb_read() (bsc#1234658).\n- kdb: Use format-strings rather than '\\0' injection in kdb_read() (bsc#1234654).\n- kdb: Use the passed prompt in kdb_position_cursor() (bsc#1234654).\n- kdb: address -Wformat-security warnings (bsc#1234659).\n- kgdb: Flush console before entering kgdb on panic (bsc#1234651).\n- kheaders: Ignore silly-rename files (stable-fixes).\n- ktest.pl: Avoid false positives with grub2 skip regex (stable-fixes).\n- ktest.pl: Check kernelrelease return in get_version (git-fixes).\n- ktest.pl: Fix typo \"accesing\" (git-fixes).\n- ktest.pl: Fix typo in comment (git-fixes).\n- ktest.pl: Remove unused declarations in run_bisect_test function (git-fixes).\n- ktest: force $buildonly = 1 for 'make_warnings_file' test type (stable-fixes).\n- landlock: Handle weird files (git-fixes).\n- latencytop: use correct kernel-doc format for func params (git-fixes).\n- leds: class: Protect brightness_show() with led_cdev-\u003eled_access mutex (stable-fixes).\n- leds: lp8860: Write full EEPROM, not only half of it (git-fixes).\n- leds: netxbig: Fix an OF node reference leak in netxbig_leds_get_of_pdata() (git-fixes).\n- lib/inflate.c: remove dead code (git-fixes).\n- lib/stackdepot: print disabled message only if truly disabled (git-fixes).\n- linux/dmaengine.h: fix a few kernel-doc warnings (git-fixes).\n- locking/atomic/x86: Correct the definition of __arch_try_cmpxchg128() (bsc#1220773 git-fix).\n- loop: fix the the direct I/O support check when used on top of block devices (bsc#1234143).\n- mac80211: fix user-power when emulating chanctx (stable-fixes).\n- mac802154: check local interfaces before deleting sdata list (stable-fixes).\n- mailbox: pcc: Add support for platform notification handling (stable-fixes).\n- mailbox: pcc: Support shared interrupt for multiple subspaces (stable-fixes).\n- mailbox: tegra-hsp: Clear mailbox before using message (git-fixes).\n- maple_tree: simplify split calculation (git-fixes).\n- media: camif-core: Add check for clk_enable() (git-fixes).\n- media: ccs: Clean up parsed CCS static data on parse failure (git-fixes).\n- media: ccs: Fix CCS static data parsing for large block sizes (git-fixes).\n- media: ccs: Fix cleanup order in ccs_probe() (git-fixes).\n- media: cx231xx: Add support for Dexatek USB Video Grabber 1d19:6108 (stable-fixes).\n- media: dvb-frontends: dib3000mb: fix uninit-value in dib3000_write_reg (git-fixes).\n- media: dvb-usb-v2: af9035: fix ISO C90 compilation error on af9035_i2c_master_xfer (git-fixes).\n- media: i2c: imx412: Add missing newline to prints (git-fixes).\n- media: i2c: ov9282: Correct the exposure offset (git-fixes).\n- media: imx-jpeg: Fix potential error pointer dereference in detach_pm() (git-fixes).\n- media: imx296: Add standby delay during probe (git-fixes).\n- media: lmedm04: Handle errors for lme2510_int_read (git-fixes).\n- media: marvell: Add check for clk_enable() (git-fixes).\n- media: mc: fix endpoint iteration (git-fixes).\n- media: mipi-csis: Add check for clk_enable() (git-fixes).\n- media: nxp: imx8-isi: fix v4l2-compliance test errors (git-fixes).\n- media: ov5640: fix get_light_freq on auto (git-fixes).\n- media: rc: iguanair: handle timeouts (git-fixes).\n- media: rkisp1: Fix unused value issue (git-fixes).\n- media: uvcvideo: Add a quirk for the Kaiweets KTI-W02 infrared camera (stable-fixes).\n- media: uvcvideo: Fix crash during unbind if gpio unit is in use (git-fixes).\n- media: uvcvideo: Fix double free in error path (git-fixes).\n- media: uvcvideo: Fix event flags in uvc_ctrl_send_events (git-fixes).\n- media: uvcvideo: Force UVC version to 1.0a for 0408:4035 (stable-fixes).\n- media: uvcvideo: Only save async fh if success (git-fixes).\n- media: uvcvideo: Propagate buf-\u003eerror to userspace (git-fixes).\n- media: uvcvideo: RealSense D421 Depth module metadata (stable-fixes).\n- media: uvcvideo: Remove dangling pointers (git-fixes).\n- media: uvcvideo: Remove redundant NULL assignment (git-fixes).\n- media: uvcvideo: Support partial control reads (git-fixes).\n- memory tiering: count PGPROMOTE_SUCCESS when mem tiering is enabled (git-fixes).\n- memory-failure: use a folio in me_huge_page() (git-fixes).\n- memory: tegra20-emc: fix an OF node reference bug in tegra_emc_find_node_by_ram_code() (git-fixes).\n- mfd: da9052-spi: Change read-mask to write-mask (git-fixes).\n- mfd: intel_soc_pmic_bxtwc: Use IRQ domain for PMIC devices (git-fixes).\n- mfd: intel_soc_pmic_bxtwc: Use IRQ domain for TMU device (git-fixes).\n- mfd: intel_soc_pmic_bxtwc: Use IRQ domain for USB Type-C device (git-fixes).\n- misc: fastrpc: Deregister device nodes properly in error scenarios (git-fixes).\n- misc: fastrpc: Fix copy buffer page size (git-fixes).\n- misc: fastrpc: Fix registered buffer page address (git-fixes).\n- misc: microchip: pci1xxxx: Resolve kernel panic during GPIO IRQ handling (git-fixes).\n- misc: microchip: pci1xxxx: Resolve return code mismatch during GPIO set config (git-fixes).\n- misc: misc_minor_alloc to use ida for all dynamic/misc dynamic minors (git-fixes).\n- mm, kmsan: fix infinite recursion due to RCU critical section (git-fixes).\n- mm,page_owner: do not remove __GFP_NOLOCKDEP in add_stack_record_to_list (git-fixes).\n- mm/filemap: avoid buffered read/write race to read inconsistent data (bsc#1234204).\n- mm/memory-failure: cast index to loff_t before shifting it (git-fixes).\n- mm/memory-failure: check the mapcount of the precise page (git-fixes).\n- mm/memory-failure: fix crash in split_huge_page_to_list from soft_offline_page (git-fixes).\n- mm/memory-failure: pass the folio and the page to collect_procs() (git-fixes).\n- mm/memory-failure: use raw_spinlock_t in struct memory_failure_cpu (git-fixes).\n- mm/memory_hotplug: add missing mem_hotplug_lock (git-fixes).\n- mm/memory_hotplug: fix error handling in add_memory_resource() (git-fixes).\n- mm/memory_hotplug: prevent accessing by index=-1 (git-fixes).\n- mm/memory_hotplug: use pfn math in place of direct struct page manipulation (git-fixes).\n- mm/migrate: correct nr_failed in migrate_pages_sync() (git-fixes).\n- mm/migrate: fix deadlock in migrate_pages_batch() on large folios (git-fixes).\n- mm/migrate: putback split folios when numa hint migration fails (git-fixes).\n- mm/migrate: split source folio if it is on deferred split list (git-fixes).\n- mm/page_owner: remove free_ts from page_owner output (git-fixes).\n- mm/readahead: do not allow order-1 folio (bsc#1234205).\n- mm/readahead: limit page cache size in page_cache_ra_order() (bsc#1234208).\n- mm/rodata_test: use READ_ONCE() to read const variable (git-fixes).\n- mm: convert DAX lock/unlock page to lock/unlock folio (git-fixes).\n- mm: memory-failure: ensure moving HWPoison flag to the raw error pages (git-fixes).\n- mm: memory-failure: fetch compound head after extra page refcnt is held (git-fixes).\n- mm: memory-failure: fix potential page refcnt leak in memory_failure() (git-fixes).\n- mm: memory-failure: fix race window when trying to get hugetlb folio (git-fixes).\n- mm: memory-failure: remove unneeded PageHuge() check (git-fixes).\n- mm: prevent derefencing NULL ptr in pfn_section_valid() (git-fixes).\n- mmc: core: Add SD card quirk for broken poweroff notification (stable-fixes).\n- mmc: mtk-sd: Fix MMC_CAP2_CRYPTO flag setting (git-fixes).\n- mmc: mtk-sd: fix devm_clk_get_optional usage (stable-fixes).\n- mmc: sdhci-esdhc-imx: enable quirks SDHCI_QUIRK_NO_LED (stable-fixes).\n- mmc: sdhci-pci: Add DMI quirk for missing CD GPIO on Vexia Edu Atla 10 tablet (stable-fixes).\n- mmc: sdhci-tegra: Remove SDHCI_QUIRK_BROKEN_ADMA_ZEROLEN_DESC quirk (git-fixes).\n- modpost: fix the missed iteration for the max bit in do_input() (git-fixes).\n- mtd: diskonchip: Cast an operand to prevent potential overflow (git-fixes).\n- mtd: hyperbus: rpc-if: Add missing MODULE_DEVICE_TABLE (git-fixes).\n- mtd: hyperbus: rpc-if: Convert to platform remove callback returning void (stable-fixes).\n- mtd: onenand: Fix uninitialized retlen in do_otp_read() (git-fixes).\n- mtd: rawnand: arasan: Fix double assertion of chip-select (git-fixes).\n- mtd: rawnand: arasan: Fix missing de-registration of NAND (git-fixes).\n- mtd: rawnand: fix double free in atmel_pmecc_create_user() (git-fixes).\n- mtd: spinand: Remove write_enable_op() in markbad() (git-fixes).\n- net :mana :Request a V2 response version for MANA_QUERY_GF_STAT (git-fixes).\n- net/ipv6: release expired exception dst cached in socket (bsc#1216813).\n- net/mlx5e: CT: Fix null-ptr-deref in add rule err flow (git-fixes).\n- net/mlx5e: Remove workaround to avoid syndrome for internal port (git-fixes).\n- net/mlx5e: clear xdp features on non-uplink representors (git-fixes).\n- net/qed: allow old cards not supporting \"num_images\" to work (git-fixes).\n- net/rose: prevent integer overflows in rose_setsockopt() (git-fixes).\n- net: Return error from sk_stream_wait_connect() if sk_wait_event() fails (git-fixes).\n- net: mana: Increase the DEF_RX_BUFFERS_PER_QUEUE to 1024 (bsc#1235246).\n- net: phy: c45-tjaxx: add delay between MDIO write and read in soft_reset (git-fixes).\n- net: rose: fix timer races against user threads (git-fixes).\n- net: usb: qmi_wwan: add Quectel RG650V (stable-fixes).\n- net: usb: qmi_wwan: add Telit FE910C04 compositions (stable-fixes).\n- net: usb: rtl8150: enable basic endpoint checking (git-fixes).\n- net: wwan: iosm: Properly check for valid exec stage in ipc_mmio_init() (git-fixes).\n- net: wwan: t7xx: Fix FSM command timeout issue (git-fixes).\n- netfilter: nf_tables: validate family when identifying table via handle (bsc#1233778 ZDI-24-1454).\n- nfs: ignore SB_RDONLY when mounting nfs (git-fixes).\n- nfsd: fix nfs4_openowner leak when concurrent nfsd4_open occur (git-fixes).\n- nfsd: make sure exp active before svc_export_show (git-fixes).\n- nfsd: release svc_expkey/svc_export with rcu_work (git-fixes).\n- nfsd: restore callback functionality for NFSv4.0 (git-fixes).\n- nilfs2: fix buffer head leaks in calls to truncate_inode_pages() (git-fixes).\n- nilfs2: fix possible int overflows in nilfs_fiemap() (git-fixes).\n- nilfs2: fix potential out-of-bounds memory access in nilfs_find_entry() (git-fixes).\n- nilfs2: prevent use of deleted inode (git-fixes).\n- nvme-pci: 512 byte aligned dma pool segment quirk (git-fixes).\n- nvme-rdma: unquiesce admin_q before destroy it (git-fixes).\n- nvme-tcp: Fix I/O queue cpu spreading for multiple controllers (git-fixes).\n- nvme-tcp: fix the memleak while create new ctrl failed (git-fixes).\n- nvme/multipath: Fix RCU list traversal to use SRCU primitive (git-fixes).\n- nvme: Add error check for xa_store in nvme_get_effects_log (git-fixes).\n- nvme: Add error path for xa_store in nvme_init_effects (git-fixes).\n- nvme: apple: fix device reference counting (git-fixes).\n- nvme: fix bogus kzalloc() return check in nvme_init_effects_log() (git-fixes).\n- nvme: fix metadata handling in nvme-passthrough (git-fixes).\n- nvmet-loop: avoid using mutex in IO hotpath (git-fixes).\n- nvmet: propagate npwg topology (git-fixes).\n- ocfs2: fix uninitialized value in ocfs2_file_read_iter() (git-fixes).\n- ocfs2: free inode when ocfs2_get_init_inode() fails (git-fixes).\n- of/irq: Fix using uninitialized variable @addr_len in API of_irq_parse_one() (git-fixes).\n- of: Fix error path in of_parse_phandle_with_args_map() (git-fixes).\n- of: Fix refcount leakage for OF node returned by __of_get_dma_parent() (git-fixes).\n- of: address: Report error on resource bounds overflow (stable-fixes).\n- padata: add pd get/put refcnt helper (git-fixes).\n- padata: avoid UAF for reorder_work (git-fixes).\n- padata: fix UAF in padata_reorder (git-fixes).\n- parisc: Raise minimal GCC version (bsc#1220773).\n- parisc: Raise minimal GCC version to 12.0.0 (bsc#1220773 git-fix).\n- percpu: Add {raw,this}_cpu_try_cmpxchg() (bsc#1220773).\n- percpu: Fix self-assignment of __old in raw_cpu_generic_try_cmpxchg() (bsc#1220773 git-fix).\n- percpu: Wire up cmpxchg128 (bsc#1220773).\n- phy: core: Fix an OF node refcount leakage in _of_phy_get() (git-fixes).\n- phy: core: Fix an OF node refcount leakage in of_phy_provider_lookup() (git-fixes).\n- phy: core: Fix that API devm_of_phy_provider_unregister() fails to unregister the phy provider (git-fixes).\n- phy: core: Fix that API devm_phy_destroy() fails to destroy the phy (git-fixes).\n- phy: core: Fix that API devm_phy_put() fails to release the phy (git-fixes).\n- phy: qcom-qmp: Fix register name in RX Lane config of SC8280XP (git-fixes).\n- phy: rockchip: naneng-combphy: fix phy reset (git-fixes).\n- phy: usb: Toggle the PHY power during init (git-fixes).\n- pinctrl: amd: Take suspend type into consideration which pins are non-wake (git-fixes).\n- pinctrl: mcp23s08: Fix sleeping in atomic context due to regmap locking (git-fixes).\n- pinctrl: qcom-pmic-gpio: add support for PM8937 (stable-fixes).\n- pinctrl: qcom: spmi-mpp: Add PM8937 compatible (stable-fixes).\n- pinctrl: samsung: fix fwnode refcount cleanup if platform_get_irq_optional() fails (git-fixes).\n- pinmux: Use sequential access to access desc-\u003epinmux data (stable-fixes).\n- platform/chrome: cros_ec_proto: Lock device when updating MKBP version (git-fixes).\n- platform/x86/amd/pmc: Only disable IRQ1 wakeup where i8042 actually enabled it (git-fixes).\n- platform/x86/intel-uncore-freq: Ignore minor version change (bsc#1225897).\n- platform/x86/intel/tpmi: Add defines to get version information (bsc#1225897).\n- platform/x86: asus-nb-wmi: Ignore unknown event 0xCF (stable-fixes).\n- platform/x86: dell-smbios-base: Extends support to Alienware products (stable-fixes).\n- platform/x86: dell-wmi-base: Handle META key Lock/Unlock events (stable-fixes).\n- platform/x86: thinkpad_acpi: Fix for ThinkPad's with ECFW showing incorrect fan speed (stable-fixes).\n- pm:cpupower: Add missing powercap_set_enabled() stub function (git-fixes).\n- power: ip5xxx_power: Fix return value on ADC read errors (git-fixes).\n- power: supply: gpio-charger: Fix set charge current limits (git-fixes).\n- powerpc/book3s64/hugetlb: Fix disabling hugetlb when fadump is active (bsc#1235108).\n- powerpc/iommu: Move pSeries specific functions to pseries/iommu.c (bsc#1220711 ltc#205755).\n- powerpc/iommu: Only build sPAPR access functions on pSeries (bsc#1220711 ltc#205755).\n- powerpc/powernv/pci: Remove MVE code (bsc#1220711 ltc#205755).\n- powerpc/powernv/pci: Remove ioda1 support (bsc#1220711 ltc#205755).\n- powerpc/powernv/pci: Remove last IODA1 defines (bsc#1220711 ltc#205755).\n- powerpc/pseries/eeh: Fix get PE state translation (bsc#1215199).\n- powerpc/pseries/iommu: IOMMU incorrectly marks MMIO range in DDW (bsc#1218470 ltc#204531).\n- powerpc/pseries/vas: Add close() callback in vas_vm_ops struct (bsc#1234825).\n- pps: add an error check in parport_attach (git-fixes).\n- pps: remove usage of the deprecated ida_simple_xx() API (stable-fixes).\n- printk: Add is_printk_legacy_deferred() (bsc#1236733).\n- printk: Defer legacy printing when holding printk_cpu_sync (bsc#1236733).\n- proc/softirqs: replace seq_printf with seq_put_decimal_ull_width (git-fixes).\n- pwm: stm32-lp: Add check for clk_enable() (git-fixes).\n- pwm: stm32: Add check for clk_enable() (git-fixes).\n- quota: Fix rcu annotations of inode dquot pointers (bsc#1234197).\n- quota: explicitly forbid quota files from being encrypted (bsc#1234196).\n- quota: flush quota_release_work upon quota writeback (bsc#1234195).\n- quota: simplify drop_dquot_ref() (bsc#1234197).\n- rcu-tasks: Pull sampling of -\u003epercpu_dequeue_lim out of loop (git-fixes)\n- rcu/tree: Defer setting of jiffies during stall reset (git-fixes)\n- rcu: Dump memory object info if callback function is invalid (git-fixes)\n- rcu: Eliminate rcu_gp_slow_unregister() false positive (git-fixes)\n- rcuscale: Move rcu_scale_writer() (git-fixes)\n- rdma/cxgb4: Prevent potential integer overflow on 32bit (git-fixes)\n- readahead: use ilog2 instead of a while loop in page_cache_ra_order() (bsc#1234208).\n- regmap: Use correct format specifier for logging range errors (stable-fixes).\n- regulator: core: Add missing newline character (git-fixes).\n- regulator: of: Implement the unwind path of of_regulator_match() (git-fixes).\n- regulator: rk808: Add apply_bit for BUCK3 on RK809 (stable-fixes).\n- remoteproc: core: Fix ida_free call while not allocated (git-fixes).\n- rtc: cmos: avoid taking rtc_lock for extended period of time (stable-fixes).\n- rtc: pcf85063: fix potential OOB write in PCF85063 NVMEM read (git-fixes).\n- rtc: zynqmp: Fix optional clock name property (git-fixes).\n- s390/cio: Do not unregister the subchannel based on DNV (git-fixes).\n- s390/cpum_sf: Convert to cmpxchg128() (bsc#1220773).\n- s390/cpum_sf: Handle CPU hotplug remove during sampling (git-fixes).\n- s390/cpum_sf: Remove WARN_ON_ONCE statements (git-fixes).\n- s390/facility: Disable compile time optimization for decompressor code (git-fixes).\n- s390/iucv: MSG_PEEK causes memory leak in iucv_sock_destruct() (git-fixes).\n- s390/pageattr: Implement missing kernel_page_present() (git-fixes).\n- s390x config: IOMMU_DEFAULT_DMA_LAZY=y (bsc#1235646)\n- samples/landlock: Fix possible NULL dereference in parse_path() (git-fixes).\n- scatterlist: fix incorrect func name in kernel-doc (git-fixes).\n- sched/fair: Fix value reported by hot tasks pulled in /proc/schedstat (bsc#1235865).\n- sched/fair: Fix value reported by hot tasks pulled in /proc/schedstat -kabi (bsc#1235865).\n- sched/numa: fix memory leak due to the overwritten vma-\u003enumab_state (git fixes (sched/numa)).\n- scsi: lpfc: Add handling for LS_RJT reason explanation authentication required (bsc#1235409).\n- scsi: lpfc: Add support for large fw object application layer reads (bsc#1235409).\n- scsi: lpfc: Change lpfc_nodelist save_flags member into a bitmask (bsc#1235409).\n- scsi: lpfc: Copyright updates for 14.4.0.7 patches (bsc#1235409).\n- scsi: lpfc: Delete NLP_TARGET_REMOVE flag due to obsolete usage (bsc#1235409).\n- scsi: lpfc: Modify handling of ADISC based on ndlp state and RPI registration (bsc#1235409).\n- scsi: lpfc: Redefine incorrect type in lpfc_create_device_data() (bsc#1235409).\n- scsi: lpfc: Restrict the REG_FCFI MAM field to FCoE adapters only (bsc#1235409).\n- scsi: lpfc: Update definition of firmware configuration mbox cmds (bsc#1235409).\n- scsi: lpfc: Update lpfc version to 14.4.0.7 (bsc#1235409).\n- scsi: qla2xxx: Fix NVMe and NPIV connect issue (bsc#1235406).\n- scsi: qla2xxx: Fix abort in bsg timeout (bsc#1235406).\n- scsi: qla2xxx: Fix use after free on unload (bsc#1235406).\n- scsi: qla2xxx: Remove check req_sg_cnt should be equal to rsp_sg_cnt (bsc#1235406).\n- scsi: qla2xxx: Remove the unused 'del_list_entry' field in struct fc_port (bsc#1235406).\n- scsi: qla2xxx: Supported speed displayed incorrectly for VPorts (bsc#1235406).\n- scsi: qla2xxx: Update version to 10.02.09.400-k (bsc#1235406).\n- scsi: storvsc: Do not flag MAINTENANCE_IN return of SRB_STATUS_DATA_OVERRUN as an error (git-fixes).\n- scsi: storvsc: Ratelimit warning logs to prevent VM denial of service (git-fixes).\n- seccomp: Stub for !CONFIG_SECCOMP (stable-fixes).\n- selftest: media_tests: fix trivial UAF typo (git-fixes).\n- selftests/alsa: Fix circular dependency involving global-timer (stable-fixes).\n- selftests/bpf: Test PROBE_MEM of VSYSCALL_ADDR on x86-64 (git-fixes).\n- selftests/landlock: Fix error message (git-fixes).\n- selftests/mm/cow: modify the incorrect checking parameters (git-fixes).\n- selftests/powerpc: Fix argument order to timer_sub() (git-fixes).\n- selftests: harness: fix printing of mismatch values in __EXPECT() (git-fixes).\n- selftests: mptcp: avoid spurious errors on disconnect (git-fixes).\n- selftests: tc-testing: reduce rshift value (stable-fixes).\n- selftests: timers: clocksource-switch: Adapt progress to kselftest framework (git-fixes).\n- selinux: Fix SCTP error inconsistency in selinux_socket_bind() (git-fixes).\n- serial: 8250: Adjust the timeout for FIFO mode (git-fixes).\n- serial: 8250_dw: Add Sophgo SG2044 quirk (stable-fixes).\n- serial: 8250_dw: Do not use struct dw8250_data outside of 8250_dw (git-fixes).\n- serial: 8250_dw: Replace ACPI device check by a quirk (git-fixes).\n- serial: 8250_fintek: Add support for F81216E (stable-fixes).\n- serial: Do not hold the port lock when setting rx-during-tx GPIO (git-fixes).\n- serial: amba-pl011: Fix RX stall when DMA is used (git-fixes).\n- serial: amba-pl011: Use port lock wrappers (stable-fixes).\n- serial: amba-pl011: fix build regression (git-fixes).\n- serial: do not use uninitialized value in uart_poll_init() (git-fixes).\n- serial: imx: only set receiver level if it is zero (git-fixes).\n- serial: imx: set receiver level before starting uart (git-fixes).\n- serial: qcom-geni: Do not cancel/abort if we can't get the port lock (git-fixes).\n- serial: qcom-geni: disable interrupts during console writes (git-fixes).\n- serial: qcom-geni: fix arg types for qcom_geni_serial_poll_bit() (git-fixes).\n- serial: qcom-geni: fix console corruption (git-fixes).\n- serial: qcom-geni: fix dma rx cancellation (git-fixes).\n- serial: qcom-geni: fix false console tx restart (git-fixes).\n- serial: qcom-geni: fix fifo polling timeout (git-fixes).\n- serial: qcom-geni: fix hard lockup on buffer flush (git-fixes).\n- serial: qcom-geni: fix polled console corruption (git-fixes).\n- serial: qcom-geni: fix polled console initialisation (git-fixes).\n- serial: qcom-geni: fix receiver enable (git-fixes).\n- serial: qcom-geni: fix shutdown race (git-fixes).\n- serial: qcom-geni: fix soft lockup on sw flow control and suspend (git-fixes).\n- serial: qcom-geni: introduce qcom_geni_serial_poll_bitfield() (git-fixes).\n- serial: qcom-geni: revert broken hibernation support (git-fixes).\n- serial: sh-sci: Do not probe the serial port if its slot in sci_ports[] is in use (git-fixes).\n- serial: sh-sci: Drop __initdata macro for port_cfg (git-fixes).\n- serial: stm32: Return IRQ_NONE in the ISR if no handling happend (git-fixes).\n- serial: stm32: do not always set SER_RS485_RX_DURING_TX if RS485 is enabled (git-fixes).\n- series.conf: temporarily disable upstream patch patches.suse/ocfs2-fix-UBSAN-warning-in-ocfs2_verify_volume.patch (bsc#1236138)\n- slub: Replace cmpxchg_double() (bsc#1220773).\n- slub: Replace cmpxchg_double() - KABI fix (bsc#1220773).\n- smb: client: fix TCP timers deadlock after rmmod (git-fixes) [hcarvalho: fix issue described in bsc#1233642]\n- soc/fsl: cpm: qmc: Convert to platform remove callback returning void (stable-fixes).\n- soc: atmel: fix device_node release in atmel_soc_device_init() (git-fixes).\n- soc: fsl: cpm1: qmc: Fix blank line and spaces (stable-fixes).\n- soc: fsl: cpm1: qmc: Introduce qmc_init_resource() and its CPM1 version (stable-fixes).\n- soc: fsl: cpm1: qmc: Introduce qmc_{init,exit}_xcc() and their CPM1 version (stable-fixes).\n- soc: fsl: cpm1: qmc: Re-order probe() operations (stable-fixes).\n- soc: fsl: cpm1: qmc: Set the ret error code on platform_get_irq() failure (git-fixes).\n- soc: imx8m: Probe the SoC driver as platform driver (stable-fixes).\n- soc: mediatek: mtk-devapc: Fix leaking IO map on error paths (git-fixes).\n- soc: qcom: Add check devm_kasprintf() returned value (stable-fixes).\n- soc: qcom: geni-se: Add M_TX_FIFO_NOT_EMPTY bit definition (git-fixes).\n- soc: qcom: geni-se: add GP_LENGTH/IRQ_EN_SET/IRQ_EN_CLEAR registers (git-fixes).\n- soc: qcom: smem_state: fix missing of_node_put in error path (git-fixes).\n- soc: qcom: socinfo: Avoid out of bounds read of serial number (git-fixes).\n- soc: qcom: socinfo: fix revision check in qcom_socinfo_probe() (git-fixes).\n- sound: usb: enable DSD output for ddHiFi TC44C (stable-fixes).\n- sound: usb: format: do not warn that raw DSD is unsupported (stable-fixes).\n- spi: aspeed: Fix an error handling path in aspeed_spi_[read|write]_user() (git-fixes).\n- spi: zynq-qspi: Add check for clk_enable() (git-fixes).\n- srcu: Fix srcu_struct node grpmask overflow on 64-bit systems (git-fixes)\n- srcu: Only accelerate on enqueue time (git-fixes)\n- stackdepot: rename pool_index to pool_index_plus_1 (git-fixes).\n- stackdepot: respect __GFP_NOLOCKDEP allocation flag (git-fixes).\n- staging: iio: ad9832: Correct phase range check (git-fixes).\n- staging: iio: ad9834: Correct phase range check (git-fixes).\n- staging: media: imx: fix OF node leak in imx_media_add_of_subdevs() (git-fixes).\n- staging: media: max96712: fix kernel oops when removing module (git-fixes).\n- sunrpc: clear XPRT_SOCK_UPD_TIMEOUT when reset transport (git-fixes).\n- sunrpc: fix one UAF issue caused by sunrpc kernel tcp socket (git-fixes).\n- sunrpc: handle -ENOTCONN in xs_tcp_setup_socket() (git-fixes).\n- supported.conf: Add support for v4l2-dv-timings (jsc#PED-8645)\n- svcrdma: Address an integer overflow (git-fixes).\n- svcrdma: fix miss destroy percpu_counter in svc_rdma_proc_init() (git-fixes).\n- swiotlb: Enforce page alignment in swiotlb_alloc() (git-fixes).\n- swiotlb: Reinstate page-alignment for mappings \u003e= PAGE_SIZE (git-fixes).\n- thermal/drivers/qcom/tsens-v1: Add support for MSM8937 tsens (stable-fixes).\n- thermal: of: fix OF node leak in of_thermal_zone_find() (git-fixes).\n- thunderbolt: Add support for Intel Lunar Lake (stable-fixes).\n- thunderbolt: Add support for Intel Panther Lake-M/P (stable-fixes).\n- tipc: fix NULL deref in cleanup_bearer() (bsc#1235433).\n- tools: Sync if_xdp.h uapi tooling header (git-fixes).\n- tools: hv: change permissions of NetworkManager configuration file (git-fixes).\n- tpm/eventlog: Limit memory allocations for event logs with excessive size (bsc#1233260 bsc#1233259 bsc#1232421).\n- tpm: Map the ACPI provided event log (bsc#1233260 bsc#1233259 bsc#1232421).\n- tpm_tis_spi: Release chip select when flow control fails (bsc#1234338)\n- tty: serial: 8250: Fix another runtime PM usage counter underflow (git-fixes).\n- tty: serial: kgdboc: Fix 8250_* kgdb over serial (git-fixes).\n- types: Introduce [us]128 (bsc#1220773).\n- ubifs: Correct the total block count by deducting journal reservation (git-fixes).\n- ubifs: authentication: Fix use-after-free in ubifs_tnc_end_commit (git-fixes).\n- ubifs: skip dumping tnc tree when zroot is null (git-fixes).\n- udf: Fix lock ordering in udf_evict_inode() (bsc#1234238).\n- udf: fix uninit-value use in udf_get_fileshortad (bsc#1234243).\n- udf: prevent integer overflow in udf_bitmap_free_blocks() (bsc#1234239).\n- udf: refactor inode_bmap() to handle error (bsc#1234242).\n- udf: refactor udf_current_aext() to handle error (bsc#1234240).\n- udf: refactor udf_next_aext() to handle error (bsc#1234241).\n- udf: udftime: prevent overflow in udf_disk_stamp_to_time() (bsc#1234237).\n- uio: Fix return value of poll (git-fixes).\n- uio: uio_dmem_genirq: check the return value of devm_kasprintf() (git-fixes).\n- usb-storage: Add max sectors quirk for Nokia 208 (stable-fixes).\n- usb: add support for new USB device ID 0x17EF:0x3098 for the r8152 driver (stable-fixes).\n- usb: cdns3-ti: Add workaround for Errata i2409 (stable-fixes).\n- usb: cdns3: Add quirk flag to enable suspend residency (stable-fixes).\n- usb: chipidea: add CI_HDRC_FORCE_VBUS_ACTIVE_ALWAYS flag (stable-fixes).\n- usb: chipidea: udc: handle USB Error Interrupt if IOC not set (stable-fixes).\n- usb: dwc2: Fix HCD port connection race (git-fixes).\n- usb: dwc2: Fix HCD resume (git-fixes).\n- usb: dwc2: gadget: Do not write invalid mapped sg entries into dma_desc with iommu enabled (stable-fixes).\n- usb: dwc2: hcd: Fix GetPortStatus \u0026 SetPortFeature (git-fixes).\n- usb: dwc3-am62: Disable autosuspend during remove (git-fixes).\n- usb: dwc3-am62: Fix an OF node leak in phy_syscon_pll_refclk() (git-fixes).\n- usb: dwc3: ep0: Do not clear ep0 DWC3_EP_TRANSFER_STARTED (git-fixes).\n- usb: dwc3: ep0: Do not reset resource alloc flag (git-fixes).\n- usb: dwc3: ep0: Do not reset resource alloc flag (including ep0) (git-fixes).\n- usb: dwc3: gadget: Rewrite endpoint allocation flow (stable-fixes).\n- usb: dwc3: gadget: fix writing NYET threshold (git-fixes).\n- usb: dwc3: xilinx: make sure pipe clock is deselected in usb2 only mode (git-fixes).\n- usb: ehci-hcd: fix call balance of clocks handling routines (git-fixes).\n- usb: fix reference leak in usb_new_device() (git-fixes).\n- usb: gadget: configfs: Ignore trailing LF for user strings to cdev (git-fixes).\n- usb: gadget: f_fs: Remove WARN_ON in functionfs_bind (git-fixes).\n- usb: gadget: f_tcm: Decrement command ref count on cleanup (git-fixes).\n- usb: gadget: f_tcm: Do not free command immediately (git-fixes).\n- usb: gadget: f_tcm: Do not prepare BOT write request twice (git-fixes).\n- usb: gadget: f_tcm: Fix Get/SetInterface return value (git-fixes).\n- usb: gadget: f_tcm: Translate error to sense (git-fixes).\n- usb: gadget: f_tcm: ep_autoconfig with fullspeed endpoint (git-fixes).\n- usb: gadget: f_uac2: Fix incorrect setting of bNumEndpoints (git-fixes).\n- usb: gadget: u_serial: Disable ep before setting port to null to fix the crash caused by port being null (git-fixes).\n- usb: gadget: u_serial: Fix the issue that gs_start_io crashed due to accessing null pointer (git-fixes).\n- usb: host: max3421-hcd: Correctly abort a USB request (git-fixes).\n- usb: host: xhci-plat: Assign shared_hcd-\u003ersrc_start (git-fixes).\n- usb: typec: anx7411: fix OF node reference leaks in anx7411_typec_switch_probe() (git-fixes).\n- usb: typec: anx7411: fix fwnode_handle reference leak (git-fixes).\n- usb: typec: fix pm usage counter imbalance in ucsi_ccg_sync_control() (bsc#1235001)\n- usb: typec: tcpm/tcpci_maxim: fix error code in max_contaminant_read_resistance_kohm() (git-fixes).\n- usb: typec: tcpm: set SRC_SEND_CAPABILITIES timeout to PD_T_SENDER_RESPONSE (git-fixes).\n- usb: typec: use cleanup facility for 'altmodes_node' (stable-fixes).\n- usbnet: ipheth: break up NCM header size computation (git-fixes).\n- usbnet: ipheth: check that DPE points past NCM header (git-fixes).\n- usbnet: ipheth: fix DPE OoB read (git-fixes).\n- usbnet: ipheth: fix possible overflow in DPE length check (git-fixes).\n- usbnet: ipheth: refactor NCM datagram loop (git-fixes).\n- usbnet: ipheth: use static NDP16 location in URB (git-fixes).\n- vDPA/ifcvf: Fix pci_read_config_byte() return code handling (git-fixes).\n- vdpa/mlx5: Fix PA offset with unaligned starting iotlb map (git-fixes).\n- vdpa/mlx5: Fix suboptimal range on iotlb iteration (git-fixes).\n- vdpa: solidrun: Fix UB bug with devres (git-fixes).\n- vfs: fix readahead(2) on block devices (bsc#1234201).\n- vmscan,migrate: fix page count imbalance on node stats when demoting pages (git-fixes).\n- watchdog: rzg2l_wdt: Power on the watchdog domain in the restart handler (stable-fixes).\n- watchdog: rzg2l_wdt: Rely on the reset driver for doing proper reset (stable-fixes).\n- watchdog: rzg2l_wdt: Remove reset de-assert from probe (stable-fixes).\n- wifi: ath11k: Fix unexpected return buffer manager error for WCN6750/WCN6855 (git-fixes).\n- wifi: ath11k: cleanup struct ath11k_mon_data (git-fixes).\n- wifi: ath12k: fix atomic calls in ath12k_mac_op_set_bitrate_mask() (stable-fixes).\n- wifi: ath12k: fix tx power, max reg power update to firmware (git-fixes).\n- wifi: ath5k: add PCI ID for Arcadyan devices (git-fixes).\n- wifi: ath5k: add PCI ID for SX76X (git-fixes).\n- wifi: brcmfmac: Fix oops due to NULL pointer dereference in brcmf_sdiod_sglist_rw() (stable-fixes).\n- wifi: brcmfmac: add missing header include for brcmf_dbg (git-fixes).\n- wifi: cfg80211: adjust allocation of colocated AP data (git-fixes).\n- wifi: cfg80211: sme: init n_channels before channels[] access (git-fixes).\n- wifi: cw1200: Fix potential NULL dereference (git-fixes).\n- wifi: ipw2x00: libipw_rx_any(): fix bad alignment (stable-fixes).\n- wifi: iwlwifi: fw: read STEP table from correct UEFI var (git-fixes).\n- wifi: iwlwifi: mvm: Use the sync timepoint API in suspend (stable-fixes).\n- wifi: mac80211: Add non-atomic station iterator (stable-fixes).\n- wifi: mac80211: Fix common size calculation for ML element (git-fixes).\n- wifi: mac80211: clean up 'ret' in sta_link_apply_parameters() (stable-fixes).\n- wifi: mac80211: do not flush non-uploaded STAs (git-fixes).\n- wifi: mac80211: export ieee80211_purge_tx_queue() for drivers (stable-fixes).\n- wifi: mac80211: fix mbss changed flags corruption on 32 bit systems (stable-fixes).\n- wifi: mac80211: fix station NSS capability initialization order (git-fixes).\n- wifi: mac80211: fix tid removal during mesh forwarding (git-fixes).\n- wifi: mac80211: init cnt before accessing elem in ieee80211_copy_mbssid_beacon (git-fixes).\n- wifi: mac80211: prohibit deactivating all links (git-fixes).\n- wifi: mac80211: wake the queues in case of failure in resume (stable-fixes).\n- wifi: mt76: mt76u_vendor_request: Do not print error messages when -EPROTO (git-fixes).\n- wifi: mt76: mt7915: Fix mesh scan on MT7916 DBDC (git-fixes).\n- wifi: mt76: mt7915: add module param to select 5 GHz or 6 GHz on MT7916 (git-fixes).\n- wifi: mt76: mt7915: firmware restart on devices with a second pcie link (git-fixes).\n- wifi: mt76: mt7915: fix overflows seen when writing limit attributes (git-fixes).\n- wifi: mt76: mt7915: fix register mapping (git-fixes).\n- wifi: mt76: mt7921: fix using incorrect group cipher after disconnection (git-fixes).\n- wifi: mt76: mt7925: fix off by one in mt7925_load_clc() (git-fixes).\n- wifi: mt76: mt7996: add max mpdu len capability (git-fixes).\n- wifi: mt76: mt7996: fix HE Phy capability (git-fixes).\n- wifi: mt76: mt7996: fix definition of tx descriptor (git-fixes).\n- wifi: mt76: mt7996: fix incorrect indexing of MIB FW event (git-fixes).\n- wifi: mt76: mt7996: fix ldpc setting (git-fixes).\n- wifi: mt76: mt7996: fix overflows seen when writing limit attributes (git-fixes).\n- wifi: mt76: mt7996: fix register mapping (git-fixes).\n- wifi: mt76: mt7996: fix rx filter setting for bfee functionality (git-fixes).\n- wifi: mt76: mt7996: fix the capability of reception of EHT MU PPDU (git-fixes).\n- wifi: nl80211: fix NL80211_ATTR_MLO_LINK_ID off-by-one (git-fixes).\n- wifi: rtlwifi: Drastically reduce the attempts to read efuse in case of failures (stable-fixes).\n- wifi: rtlwifi: destroy workqueue at rtl_deinit_core (git-fixes).\n- wifi: rtlwifi: do not complete firmware loading needlessly (git-fixes).\n- wifi: rtlwifi: fix init_sw_vars leak when probe fails (git-fixes).\n- wifi: rtlwifi: fix memory leaks and invalid access at probe error path (git-fixes).\n- wifi: rtlwifi: pci: wait for firmware loading before releasing memory (git-fixes).\n- wifi: rtlwifi: remove unused check_buddy_priv (git-fixes).\n- wifi: rtlwifi: rtl8192se: rise completion of firmware loading as last step (git-fixes).\n- wifi: rtlwifi: rtl8821ae: Fix media status report (git-fixes).\n- wifi: rtlwifi: rtl8821ae: phy: restore removed code to fix infinite loop (git-fixes).\n- wifi: rtlwifi: usb: fix workqueue leak when probe fails (git-fixes).\n- wifi: rtlwifi: wait for firmware loading before releasing memory (git-fixes).\n- wifi: rtw88: use ieee80211_purge_tx_queue() to purge TX skb (stable-fixes).\n- wifi: rtw89: check return value of ieee80211_probereq_get() for RNR (stable-fixes).\n- wifi: rtw89: mcc: consider time limits not divisible by 1024 (git-fixes).\n- wifi: wcn36xx: fix channel survey memory allocation size (git-fixes).\n- wifi: wlcore: fix unbalanced pm_runtime calls (git-fixes).\n- workqueue: Add rcu lock check at the end of work item execution (bsc#1236732).\n- workqueue: Do not warn when cancelling WQ_MEM_RECLAIM work from !WQ_MEM_RECLAIM worker (bsc#1235416).\n- writeback, cgroup: switch inodes with dirty timestamps to release dying cgwbs (bsc#1234203).\n- x86,amd_iommu: Replace cmpxchg_double() (bsc#1220773).\n- x86,intel_iommu: Replace cmpxchg_double() (bsc#1220773).\n- x86/hyperv: Fix hv tsc page based sched_clock for hibernation (git-fixes).\n- x86/static-call: Remove early_boot_irqs_disabled check to fix Xen PVH dom0 (git-fixes).\n- xfs: Add error handling for xfs_reflink_cancel_cow_range (git-fixes).\n- xfs: Propagate errors from xfs_reflink_cancel_cow_range in xfs_dax_write_iomap_end (git-fixes).\n- xfs: do not allocate COW extents when unsharing a hole (git-fixes).\n- xfs: fix sb_spino_align checks for large fsblock sizes (git-fixes).\n- xfs: remove unknown compat feature check in superblock write validation (git-fixes).\n- xfs: return from xfs_symlink_verify early on V4 filesystems (git-fixes).\n- xfs: sb_spino_align is not verified (git-fixes).\n- xhci: Add usb cold attach (CAS) as a reason to resume root hub (git-fixes).\n- xhci: Allow RPM on the USB controller (1022:43f7) by default (stable-fixes).\n- xhci: fix possible null pointer deref during xhci urb enqueue (git-fixes).\n","status":"published","published":"2025-03-28T07:51:47Z","modified":"2026-03-23T04:48:13.92582Z","updated_at":"2026-11-02T15:53:59.381172Z"},{"id":"USN-7310-1","title":"linux-oem-6.11 vulnerabilities","description":"Attila Szász discovered that the HFS+ file system implementation in the\nLinux Kernel contained a heap overflow vulnerability. An attacker could use\na specially crafted file system image that, when mounted, could cause a\ndenial of service (system crash) or possibly execute arbitrary code.\n(CVE-2025-0927)\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  - PowerPC architecture;\n  - RISC-V architecture;\n  - S390 architecture;\n  - SuperH RISC architecture;\n  - User-Mode Linux (UML);\n  - x86 architecture;\n  - Block layer subsystem;\n  - Cryptographic API;\n  - Compute Acceleration Framework;\n  - ACPI drivers;\n  - Drivers core;\n  - ATA over ethernet (AOE) driver;\n  - RAM backed block device driver;\n  - Network block device driver;\n  - Ublk userspace block driver;\n  - Compressed RAM block device driver;\n  - Bluetooth drivers;\n  - TPM device driver;\n  - Clock framework and drivers;\n  - Data acquisition framework and drivers;\n  - CPU frequency scaling framework;\n  - Hardware crypto device drivers;\n  - CXL (Compute Express Link) drivers;\n  - DAX dirext access to differentiated memory framework;\n  - Buffer Sharing and Synchronization framework;\n  - EDAC drivers;\n  - FireWire subsystem;\n  - ARM SCMI message protocol;\n  - ARM SCPI message protocol;\n  - EFI core;\n  - Qualcomm firmware drivers;\n  - GPIO subsystem;\n  - GPU drivers;\n  - HID subsystem;\n  - I2C subsystem;\n  - I3C subsystem;\n  - IIO ADC drivers;\n  - IIO subsystem;\n  - InfiniBand drivers;\n  - Input Device core drivers;\n  - IOMMU subsystem;\n  - IRQ chip drivers;\n  - Mailbox framework;\n  - Multiple devices driver;\n  - Media drivers;\n  - Multifunction device drivers;\n  - MMC subsystem;\n  - MTD block device drivers;\n  - Ethernet bonding driver;\n  - Network drivers;\n  - Mellanox network drivers;\n  - STMicroelectronics network drivers;\n  - NTB driver;\n  - Virtio pmem driver;\n  - NVME drivers;\n  - Parport drivers;\n  - PCI subsystem;\n  - Alibaba DDR Sub-System Driveway PMU driver;\n  - PHY drivers;\n  - Pin controllers subsystem;\n  - x86 platform drivers;\n  - i.MX PM domains;\n  - Powercap sysfs driver;\n  - Voltage and Current Regulator drivers;\n  - Remote Processor subsystem;\n  - StarFive reset controller drivers;\n  - Real Time Clock drivers;\n  - SCSI subsystem;\n  - SuperH / SH-Mobile drivers;\n  - QCOM SoC drivers;\n  - Xilinx SoC drivers;\n  - SPI subsystem;\n  - Direct Digital Synthesis drivers;\n  - Media staging drivers;\n  - TCM subsystem;\n  - Thermal drivers;\n  - Thunderbolt and USB4 drivers;\n  - TTY drivers;\n  - UFS subsystem;\n  - USB Device Class drivers;\n  - DesignWare USB3 driver;\n  - USB Gadget drivers;\n  - USB Host Controller drivers;\n  - USB Dual Role (OTG-ready) Controller drivers;\n  - USB Serial drivers;\n  - USB Type-C support driver;\n  - USB Type-C Port Controller Manager driver;\n  - TI TPS6598x USB Power Delivery controller driver;\n  - USB Type-C Connector System Software Interface driver;\n  - vDPA drivers;\n  - VFIO drivers;\n  - Virtio Host (VHOST) subsystem;\n  - Framebuffer layer;\n  - Virtio drivers;\n  - Xen hypervisor drivers;\n  - AFS file system;\n  - BTRFS file system;\n  - File systems infrastructure;\n  - Ceph distributed file system;\n  - EROFS file system;\n  - Ext4 file system;\n  - F2FS file system;\n  - GFS2 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  - UBI file system;\n  - BPF subsystem;\n  - Network file system (NFS) superblock;\n  - Virtio network driver;\n  - Bluetooth subsystem;\n  - Network traffic control;\n  - Network sockets;\n  - TCP network protocol;\n  - Tracing infrastructure;\n  - User-space API (UAPI);\n  - Kernel init infrastructure;\n  - io_uring subsystem;\n  - IPC subsystem;\n  - Perf events;\n  - Kernel fork() syscall;\n  - Kernel thread helper (kthread);\n  - Padata parallel execution mechanism;\n  - RCU subsystem;\n  - Arbitrary resource management;\n  - Scheduler infrastructure;\n  - Signal handling mechanism;\n  - Static call mechanism;\n  - Task handling mechanism;\n  - Timer substystem drivers;\n  - Maple Tree data structure library;\n  - Memory management;\n  - 9P file system network protocol;\n  - Ethernet bridge;\n  - CAN network layer;\n  - Networking core;\n  - DCCP (Datagram Congestion Control Protocol);\n  - Distributed Switch Architecture;\n  - IPv4 networking;\n  - IPv6 networking;\n  - IUCV driver;\n  - L2TP protocol;\n  - MAC80211 subsystem;\n  - IEEE 802.15.4 subsystem;\n  - Multipath TCP;\n  - NCSI (Network Controller Sideband Interface) driver;\n  - Netfilter;\n  - Netlink;\n  - RxRPC session sockets;\n  - SCTP protocol;\n  - SMC sockets;\n  - Sun RPC protocol;\n  - TIPC protocol;\n  - Unix domain sockets;\n  - VMware vSockets driver;\n  - Wireless networking;\n  - eXpress Data Path;\n  - XFRM subsystem;\n  - AppArmor security module;\n  - Integrity Measurement Architecture(IMA) framework;\n  - Key management;\n  - ALSA framework;\n  - FireWire sound drivers;\n  - AudioScience HPI driver;\n  - HD-audio driver;\n  - SoC Audio for Freescale CPUs drivers;\n  - MediaTek ASoC drivers;\n  - QCOM ASoC drivers;\n  - SoC audio core drivers;\n  - STMicroelectronics SoC drivers;\n  - USB sound devices;\n  - KVM core;\n(CVE-2024-50244, CVE-2024-56754, CVE-2024-50082, CVE-2024-47737,\nCVE-2024-50300, CVE-2024-49872, CVE-2024-50180, CVE-2024-50218,\nCVE-2024-49956, CVE-2024-53189, CVE-2024-56705, CVE-2024-50119,\nCVE-2024-53192, CVE-2024-49950, CVE-2024-56722, CVE-2024-49943,\nCVE-2024-50031, CVE-2024-47685, CVE-2024-50296, CVE-2024-49939,\nCVE-2024-47696, CVE-2024-47752, CVE-2024-49937, CVE-2024-53140,\nCVE-2024-50236, CVE-2024-50151, CVE-2024-50069, CVE-2024-50170,\nCVE-2024-50246, CVE-2024-50217, CVE-2024-53125, CVE-2024-50084,\nCVE-2024-50005, CVE-2024-53137, CVE-2024-50233, CVE-2024-49991,\nCVE-2024-50067, CVE-2024-50290, CVE-2024-47735, CVE-2024-53133,\nCVE-2024-50289, CVE-2024-49855, CVE-2024-49868, CVE-2024-56728,\nCVE-2024-56726, CVE-2024-50012, CVE-2024-53078, CVE-2024-50223,\nCVE-2024-50143, CVE-2024-50287, CVE-2024-49971, CVE-2024-49900,\nCVE-2024-50263, CVE-2024-50206, CVE-2024-47707, CVE-2024-47751,\nCVE-2024-56747, CVE-2024-50260, CVE-2024-50173, CVE-2024-47680,\nCVE-2024-50009, CVE-2024-53219, CVE-2024-53144, CVE-2024-50008,\nCVE-2024-53208, CVE-2024-49966, CVE-2024-50104, CVE-2024-50030,\nCVE-2024-53049, CVE-2024-53201, CVE-2024-50130, CVE-2024-49856,\nCVE-2024-53095, CVE-2024-50033, CVE-2024-47730, CVE-2024-53216,\nCVE-2024-50286, CVE-2024-50284, CVE-2024-47744, CVE-2023-52917,\nCVE-2024-50275, CVE-2024-53114, CVE-2024-49968, CVE-2024-50111,\nCVE-2024-50000, CVE-2024-53081, CVE-2024-49857, CVE-2024-50262,\nCVE-2024-50281, CVE-2024-53156, CVE-2024-50225, CVE-2024-53239,\nCVE-2024-50036, CVE-2024-50187, CVE-2024-53165, CVE-2024-49931,\nCVE-2024-53111, CVE-2024-49862, CVE-2024-47701, CVE-2024-53091,\nCVE-2024-50103, CVE-2024-53046, CVE-2024-56678, CVE-2024-56749,\nCVE-2024-53175, CVE-2024-49970, CVE-2024-50035, CVE-2024-50088,\nCVE-2024-50297, CVE-2024-47721, CVE-2024-50240, CVE-2024-50076,\nCVE-2024-56683, CVE-2024-53120, CVE-2024-50074, CVE-2024-50095,\nCVE-2024-49963, CVE-2024-50158, CVE-2024-50020, CVE-2024-53083,\nCVE-2024-50029, CVE-2024-56755, CVE-2024-49969, CVE-2024-50022,\nCVE-2024-50278, CVE-2024-50125, CVE-2024-47706, CVE-2024-50204,\nCVE-2024-56543, CVE-2024-53108, CVE-2024-49885, CVE-2024-50128,\nCVE-2024-50062, CVE-2024-50139, CVE-2024-50183, CVE-2024-50288,\nCVE-2024-56729, CVE-2024-49945, CVE-2024-47695, CVE-2024-56533,\nCVE-2024-53234, CVE-2024-50002, CVE-2024-50040, CVE-2024-49903,\nCVE-2024-47702, CVE-2024-47728, CVE-2024-49874, CVE-2024-47718,\nCVE-2024-53142, CVE-2024-49983, CVE-2024-50211, CVE-2024-50294,\nCVE-2024-50132, CVE-2024-53236, CVE-2024-50042, CVE-2024-49999,\nCVE-2024-50001, CVE-2024-50046, CVE-2024-50133, CVE-2024-50256,\nCVE-2024-49869, CVE-2024-49852, CVE-2024-47717, CVE-2024-56704,\nCVE-2024-50102, CVE-2024-50150, CVE-2024-49880, CVE-2024-50235,\nCVE-2024-49892, CVE-2024-53194, CVE-2024-53104, CVE-2024-50232,\nCVE-2024-50226, CVE-2024-56684, CVE-2024-47713, CVE-2024-50191,\nCVE-2024-49850, CVE-2024-50277, CVE-2024-53113, CVE-2024-50013,\nCVE-2024-53221, CVE-2024-50220, CVE-2024-49960, CVE-2024-53228,\nCVE-2024-50152, CVE-2024-56689, CVE-2024-53220, CVE-2024-50209,\nCVE-2024-50285, CVE-2024-50197, CVE-2024-53072, CVE-2024-50273,\nCVE-2024-49928, CVE-2024-53132, CVE-2024-56720, CVE-2024-50194,\nCVE-2024-50112, CVE-2024-53079, CVE-2024-56696, CVE-2024-47750,\nCVE-2024-53212, CVE-2024-56541, CVE-2024-50024, CVE-2024-53168,\nCVE-2024-50247, CVE-2024-50193, CVE-2024-47754, CVE-2024-56540,\nCVE-2024-50026, CVE-2024-53047, CVE-2024-53151, CVE-2024-50176,\nCVE-2024-49975, CVE-2024-50034, CVE-2024-50126, CVE-2024-49863,\nCVE-2024-47693, CVE-2024-49954, CVE-2024-49938, CVE-2024-50171,\nCVE-2024-50185, CVE-2024-50200, CVE-2024-50201, CVE-2024-53184,\nCVE-2024-47709, CVE-2024-50138, CVE-2024-49935, CVE-2024-50049,\nCVE-2024-56537, CVE-2024-50057, CVE-2024-56677, CVE-2024-47743,\nCVE-2024-50293, CVE-2024-50099, CVE-2024-47720, CVE-2024-50021,\nCVE-2024-50059, CVE-2024-49871, CVE-2024-49884, CVE-2024-47694,\nCVE-2024-56723, CVE-2024-47724, CVE-2024-50038, CVE-2024-53123,\nCVE-2024-53177, CVE-2024-49932, CVE-2024-50196, CVE-2024-50234,\nCVE-2024-50078, CVE-2024-53043, CVE-2024-49926, CVE-2024-49988,\nCVE-2024-53187, CVE-2024-53056, CVE-2024-53217, CVE-2024-56745,\nCVE-2024-47726, CVE-2024-50063, CVE-2024-49987, CVE-2024-49955,\nCVE-2024-50179, CVE-2024-49866, CVE-2024-50283, CVE-2024-49997,\nCVE-2024-47742, CVE-2024-56691, CVE-2024-50253, CVE-2024-56690,\nCVE-2024-47710, CVE-2024-53129, CVE-2024-50190, CVE-2024-50090,\nCVE-2024-56702, CVE-2024-50148, CVE-2024-53183, CVE-2024-50070,\nCVE-2024-50154, CVE-2024-50243, CVE-2024-50003, CVE-2024-50117,\nCVE-2024-56751, CVE-2024-56697, CVE-2024-53166, CVE-2024-53196,\nCVE-2024-47677, CVE-2024-56679, CVE-2024-49996, CVE-2024-47681,\nCVE-2024-53181, CVE-2024-47700, CVE-2024-53071, CVE-2024-50015,\nCVE-2024-53126, CVE-2024-50165, CVE-2024-50172, CVE-2024-53063,\nCVE-2024-53200, CVE-2024-53135, CVE-2024-49974, CVE-2024-53088,\nCVE-2024-49936, CVE-2024-53121, CVE-2024-50166, CVE-2024-50087,\nCVE-2024-53065, CVE-2024-53214, CVE-2024-53076, CVE-2024-53059,\nCVE-2024-50230, CVE-2024-49985, CVE-2024-50092, CVE-2024-53233,\nCVE-2024-50047, CVE-2024-56685, CVE-2024-47682, CVE-2024-47705,\nCVE-2024-50077, CVE-2024-53224, CVE-2024-49887, CVE-2024-49940,\nCVE-2024-47741, CVE-2024-49858, CVE-2024-56536, CVE-2024-53055,\nCVE-2024-56687, CVE-2024-50100, CVE-2024-53075, CVE-2024-47699,\nCVE-2024-53213, CVE-2024-49977, CVE-2024-50268, CVE-2024-53146,\nCVE-2024-50304, CVE-2024-50096, CVE-2024-53162, CVE-2024-56725,\nCVE-2024-49953, CVE-2024-53077, CVE-2024-50107, CVE-2024-53226,\nCVE-2024-53134, CVE-2024-49873, CVE-2024-56548, CVE-2024-53145,\nCVE-2024-53141, CVE-2024-56741, CVE-2024-53067, CVE-2024-53152,\nCVE-2024-50072, CVE-2024-50282, CVE-2024-53232, CVE-2024-50140,\nCVE-2024-53198, CVE-2024-53150, CVE-2024-49876, CVE-2024-50302,\nCVE-2024-53115, CVE-2024-47692, CVE-2024-50301, CVE-2024-50202,\nCVE-2024-50155, CVE-2024-56693, CVE-2024-53082, CVE-2024-53167,\nCVE-2024-56748, CVE-2024-53064, CVE-2024-50227, CVE-2024-56539,\nCVE-2024-50215, CVE-2024-50043, CVE-2024-50146, CVE-2024-50147,\nCVE-2024-56699, CVE-2024-50122, CVE-2024-53044, CVE-2024-47712,\nCVE-2024-53230, CVE-2024-50121, CVE-2024-50216, CVE-2024-53084,\nCVE-2024-56703, CVE-2024-50178, CVE-2024-49934, CVE-2024-47678,\nCVE-2024-50271, CVE-2024-50144, CVE-2024-50252, CVE-2024-47734,\nCVE-2024-47711, CVE-2024-50214, CVE-2024-53100, CVE-2024-56680,\nCVE-2024-50198, CVE-2024-50025, CVE-2024-50044, CVE-2024-50098,\nCVE-2024-47745, CVE-2024-49860, CVE-2024-49881, CVE-2024-53048,\nCVE-2024-56721, CVE-2024-56756, CVE-2024-53171, CVE-2024-49901,\nCVE-2024-53109, CVE-2024-53061, CVE-2024-49929, CVE-2024-47691,\nCVE-2024-50045, CVE-2024-47723, CVE-2024-56546, CVE-2024-50157,\nCVE-2024-53169, CVE-2024-47716, CVE-2024-53093, CVE-2024-50224,\nCVE-2024-53193, CVE-2024-49895, CVE-2024-47698, CVE-2024-49942,\nCVE-2024-50167, CVE-2024-53202, CVE-2024-49870, CVE-2024-50291,\nCVE-2024-50156, CVE-2024-53153, CVE-2024-50272, CVE-2024-50145,\nCVE-2024-50298, CVE-2024-50274, CVE-2024-56694, CVE-2024-50108,\nCVE-2024-50222, CVE-2024-53163, CVE-2024-50164, CVE-2024-53062,\nCVE-2024-50212, CVE-2024-53127, CVE-2024-47688, CVE-2024-49959,\nCVE-2024-50203, CVE-2024-49927, CVE-2024-50083, CVE-2024-53227,\nCVE-2024-47697, CVE-2024-53053, CVE-2024-53172, CVE-2024-56752,\nCVE-2024-50207, CVE-2024-50169, CVE-2024-53176, CVE-2024-53089,\nCVE-2024-56707, CVE-2024-53195, CVE-2024-49851, CVE-2024-53209,\nCVE-2024-49972, CVE-2024-53130, CVE-2024-53157, CVE-2024-53094,\nCVE-2024-50182, CVE-2024-49879, CVE-2024-53191, CVE-2024-49925,\nCVE-2024-49949, CVE-2024-56534, CVE-2024-47714, CVE-2024-53161,\nCVE-2024-49992, CVE-2024-47732, CVE-2024-53143, CVE-2024-53119,\nCVE-2024-50064, CVE-2024-50039, CVE-2024-53087, CVE-2024-49886,\nCVE-2024-49979, CVE-2024-50041, CVE-2024-50184, CVE-2024-49958,\nCVE-2024-50221, CVE-2024-56688, CVE-2024-49941, CVE-2024-50245,\nCVE-2024-50017, CVE-2024-53180, CVE-2024-56535, CVE-2024-50142,\nCVE-2024-50295, CVE-2024-56708, CVE-2024-50016, CVE-2024-49902,\nCVE-2024-50120, CVE-2024-47748, CVE-2024-49982, CVE-2024-50257,\nCVE-2024-50086, CVE-2024-50261, CVE-2024-53188, CVE-2024-49888,\nCVE-2024-53106, CVE-2024-50073, CVE-2024-50186, CVE-2024-56544,\nCVE-2024-47739, CVE-2024-50238, CVE-2024-56739, CVE-2024-49964,\nCVE-2024-47686, CVE-2024-46869, CVE-2024-53116, CVE-2024-50014,\nCVE-2024-53231, CVE-2024-53138, CVE-2024-50213, CVE-2024-50265,\nCVE-2024-49998, CVE-2024-50292, CVE-2024-50137, CVE-2024-50114,\nCVE-2024-53237, CVE-2024-49952, CVE-2024-53074, CVE-2024-49981,\nCVE-2024-47733, CVE-2024-50019, CVE-2024-47719, CVE-2024-53068,\nCVE-2024-49944, CVE-2024-50066, CVE-2024-50007, CVE-2024-53155,\nCVE-2024-47756, CVE-2024-49947, CVE-2024-49951, CVE-2024-50065,\nCVE-2024-49957, CVE-2024-50116, CVE-2024-50188, CVE-2024-50255,\nCVE-2024-53197, CVE-2024-50267, CVE-2024-50124, CVE-2024-53069,\nCVE-2024-53139, CVE-2024-47676, CVE-2024-56545, CVE-2024-53085,\nCVE-2024-50163, CVE-2024-53092, CVE-2024-53099, CVE-2024-49889,\nCVE-2024-53052, CVE-2024-49995, CVE-2024-49976, CVE-2024-50110,\nCVE-2024-50192, CVE-2024-50208, CVE-2024-50276, CVE-2024-53170,\nCVE-2024-50259, CVE-2024-47731, CVE-2024-49924, CVE-2024-56532,\nCVE-2024-50048, CVE-2024-49965, CVE-2024-53147, CVE-2024-50205,\nCVE-2024-49859, CVE-2024-53066, CVE-2024-47687, CVE-2024-50149,\nCVE-2024-49864, CVE-2024-49867, CVE-2024-50160, CVE-2024-53058,\nCVE-2024-47753, CVE-2024-49883, CVE-2024-53199, CVE-2024-56746,\nCVE-2024-50094, CVE-2024-49946, CVE-2024-50006, CVE-2024-53101,\nCVE-2024-49891, CVE-2024-50075, CVE-2024-47747, CVE-2024-47740,\nCVE-2024-50248, CVE-2024-50162, CVE-2024-53090, CVE-2024-53203,\nCVE-2024-50242, CVE-2024-49961, CVE-2024-50085, CVE-2024-50299,\nCVE-2024-49980, CVE-2024-50280, CVE-2024-53107, CVE-2024-50199,\nCVE-2024-53122, CVE-2024-56674, CVE-2024-50079, CVE-2024-50060,\nCVE-2024-53210, CVE-2024-50177, CVE-2024-53223, CVE-2024-50127,\nCVE-2024-53190, CVE-2022-49034, CVE-2024-56744, CVE-2024-50136,\nCVE-2024-47675, CVE-2024-50303, CVE-2024-50123, CVE-2024-47738,\nCVE-2024-50239, CVE-2024-50135, CVE-2024-53218, CVE-2024-50109,\nCVE-2024-56724, CVE-2024-56681, CVE-2024-50027, CVE-2024-50081,\nCVE-2024-50068, CVE-2024-50101, CVE-2024-50071, CVE-2024-50129,\nCVE-2024-50091, CVE-2024-53112, CVE-2024-50181, CVE-2024-50080,\nCVE-2024-47703, CVE-2024-47727, CVE-2024-53215, CVE-2024-53105,\nCVE-2024-50174, CVE-2024-50105, CVE-2024-56700, CVE-2024-53173,\nCVE-2024-49865, CVE-2024-49973, CVE-2024-56538, CVE-2024-50251,\nCVE-2024-56692, CVE-2024-47671, CVE-2024-50189, CVE-2024-49853,\nCVE-2024-50153, CVE-2024-53124, CVE-2024-56549, CVE-2024-53160,\nCVE-2024-53174, CVE-2024-53117, CVE-2024-50279, CVE-2024-50118,\nCVE-2024-47757, CVE-2024-50055, CVE-2024-49875, CVE-2024-50141,\nCVE-2024-49890, CVE-2024-49878, CVE-2024-50134, CVE-2024-53042,\nCVE-2024-56727, CVE-2024-49861, CVE-2024-49948, CVE-2024-50010,\nCVE-2024-49930, CVE-2024-49877, CVE-2024-47690, CVE-2024-50115,\nCVE-2024-50254, CVE-2024-50250, CVE-2024-47679, CVE-2024-50258,\nCVE-2024-53128, CVE-2024-49994, CVE-2024-53154, CVE-2024-50037,\nCVE-2024-53149, CVE-2024-50266, CVE-2024-50061, CVE-2024-56698,\nCVE-2024-53118, CVE-2024-47689, CVE-2024-47708, CVE-2024-50131,\nCVE-2024-50168, CVE-2024-53158, CVE-2024-49894, CVE-2024-50056,\nCVE-2024-50231, CVE-2024-50270, CVE-2024-50269, CVE-2024-50237,\nCVE-2024-56742, CVE-2024-49882, CVE-2024-47749, CVE-2024-49962,\nCVE-2024-49933, CVE-2024-53045, CVE-2024-50028, CVE-2024-53178,\nCVE-2024-50229, CVE-2024-50023, CVE-2024-50161, CVE-2024-56701,\nCVE-2024-49978, CVE-2024-50093, CVE-2024-50195, CVE-2024-49986,\nCVE-2024-53098, CVE-2024-53131, CVE-2024-47684, CVE-2024-53148,\nCVE-2024-50058, CVE-2024-53086, CVE-2024-50113, CVE-2024-49989,\nCVE-2024-50106, CVE-2024-53080, CVE-2024-53229, CVE-2024-50159,\nCVE-2024-56531, CVE-2024-53110, CVE-2024-47736, CVE-2024-56542,\nCVE-2024-47746)\n","status":"published","published":"2025-02-28T11:33:16Z","modified":"2026-11-03T21:17:33.180491814Z","updated_at":"2026-11-03T21:43:54.166508Z"},{"id":"USN-7449-1","title":"linux, linux-aws, linux-azure, linux-azure-6.8, linux-ibm, linux-lowlatency, linux-lowlatency-hwe-6.8, linux-nvidia, linux-nvidia-6.8, linux-nvidia-lowlatency, linux-oem-6.8, linux-oracle, linux-oracle-6.8 vulnerabilities","description":"Several security issues were discovered in the Linux kernel.\nAn attacker could possibly use these to compromise the system.\nThis update corrects flaws in the following subsystems:\n  - ARM64 architecture;\n  - MIPS architecture;\n  - PowerPC architecture;\n  - RISC-V architecture;\n  - S390 architecture;\n  - SuperH RISC architecture;\n  - User-Mode Linux (UML);\n  - x86 architecture;\n  - Block layer subsystem;\n  - Cryptographic API;\n  - Compute Acceleration Framework;\n  - ACPI drivers;\n  - Drivers core;\n  - RAM backed block device driver;\n  - Compressed RAM block device driver;\n  - TPM device driver;\n  - Clock framework and drivers;\n  - Data acquisition framework and drivers;\n  - CPU frequency scaling framework;\n  - Hardware crypto device drivers;\n  - CXL (Compute Express Link) drivers;\n  - EDAC drivers;\n  - ARM SCMI message protocol;\n  - ARM SCPI message protocol;\n  - EFI core;\n  - GPIO subsystem;\n  - GPU drivers;\n  - HID subsystem;\n  - I3C subsystem;\n  - IIO ADC drivers;\n  - IIO subsystem;\n  - InfiniBand drivers;\n  - IOMMU subsystem;\n  - LED subsystem;\n  - Multiple devices driver;\n  - Media drivers;\n  - Multifunction device drivers;\n  - MMC subsystem;\n  - MTD block device drivers;\n  - Network drivers;\n  - Mellanox network drivers;\n  - STMicroelectronics network drivers;\n  - NVME drivers;\n  - PCI subsystem;\n  - PHY drivers;\n  - Pin controllers subsystem;\n  - x86 platform drivers;\n  - i.MX PM domains;\n  - Voltage and Current Regulator drivers;\n  - StarFive reset controller drivers;\n  - Real Time Clock drivers;\n  - SCSI subsystem;\n  - i.MX SoC drivers;\n  - QCOM SoC drivers;\n  - Xilinx SoC drivers;\n  - SPI subsystem;\n  - Media staging drivers;\n  - TCM subsystem;\n  - UFS subsystem;\n  - DesignWare USB3 driver;\n  - USB Dual Role (OTG-ready) Controller drivers;\n  - USB Serial drivers;\n  - USB Type-C support driver;\n  - USB Type-C Port Controller Manager driver;\n  - USB Type-C Connector System Software Interface driver;\n  - vDPA drivers;\n  - VFIO drivers;\n  - Framebuffer layer;\n  - Xen hypervisor drivers;\n  - AFS file system;\n  - BTRFS file system;\n  - File systems infrastructure;\n  - EROFS file system;\n  - F2FS 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  - NTFS3 file system;\n  - Overlay file system;\n  - Proc file system;\n  - Diskquota system;\n  - SMB network file system;\n  - UBI file system;\n  - DRM display driver;\n  - BPF subsystem;\n  - StackDepot library;\n  - Bluetooth subsystem;\n  - IP tunnels definitions;\n  - Netfilter;\n  - Tracing infrastructure;\n  - User-space API (UAPI);\n  - Kernel init infrastructure;\n  - io_uring subsystem;\n  - IPC subsystem;\n  - DMA mapping infrastructure;\n  - Kernel fork() syscall;\n  - KCSAN framework;\n  - RCU subsystem;\n  - Arbitrary resource management;\n  - Scheduler infrastructure;\n  - Signal handling mechanism;\n  - Task handling mechanism;\n  - Timer subsystem;\n  - KUnit library;\n  - Memory management;\n  - 9P file system network protocol;\n  - CAN network layer;\n  - Networking core;\n  - DCCP (Datagram Congestion Control Protocol);\n  - Ethtool driver;\n  - HSR network protocol;\n  - IEEE802154.4 network protocol;\n  - IPv4 networking;\n  - IPv6 networking;\n  - IUCV driver;\n  - MAC80211 subsystem;\n  - Multipath TCP;\n  - Packet sockets;\n  - RxRPC session sockets;\n  - Network traffic control;\n  - SCTP protocol;\n  - SMC sockets;\n  - Sun RPC protocol;\n  - TIPC protocol;\n  - VMware vSockets driver;\n  - Wireless networking;\n  - eXpress Data Path;\n  - XFRM subsystem;\n  - Integrity Measurement Architecture(IMA) framework;\n  - Key management;\n  - ALSA framework;\n  - FireWire sound drivers;\n  - HD-audio driver;\n  - MediaTek ASoC drivers;\n  - QCOM ASoC drivers;\n  - SoC audio core drivers;\n  - STMicroelectronics SoC drivers;\n  - USB sound devices;\n(CVE-2024-50288, CVE-2024-56568, CVE-2024-50280, CVE-2024-56677,\nCVE-2024-56620, CVE-2024-53108, CVE-2024-53115, CVE-2024-53061,\nCVE-2024-53215, CVE-2024-50275, CVE-2024-53133, CVE-2024-50279,\nCVE-2025-21831, CVE-2025-21756, CVE-2024-56727, CVE-2024-50208,\nCVE-2024-50142, CVE-2024-53148, CVE-2024-56781, CVE-2024-53171,\nCVE-2024-56608, CVE-2024-53177, CVE-2024-56708, CVE-2024-50207,\nCVE-2024-50278, CVE-2024-50166, CVE-2024-56629, CVE-2024-56723,\nCVE-2024-50172, CVE-2024-56707, CVE-2024-50051, CVE-2024-56606,\nCVE-2024-56700, CVE-2024-56599, CVE-2024-53051, CVE-2024-56632,\nCVE-2024-47143, CVE-2024-53135, CVE-2024-53111, CVE-2024-56634,\nCVE-2024-50262, CVE-2024-56587, CVE-2024-50125, CVE-2024-53145,\nCVE-2024-53185, CVE-2024-56575, CVE-2024-53231, CVE-2024-53072,\nCVE-2024-50110, CVE-2024-53172, CVE-2024-50258, CVE-2024-53226,\nCVE-2024-50211, CVE-2024-43098, CVE-2024-50224, CVE-2024-56642,\nCVE-2024-53082, CVE-2024-50108, CVE-2024-53094, CVE-2024-53184,\nCVE-2024-56648, CVE-2024-50140, CVE-2024-53166, CVE-2024-53090,\nCVE-2024-50301, CVE-2024-56625, CVE-2024-50230, CVE-2024-56586,\nCVE-2024-53052, CVE-2024-56574, CVE-2024-53168, CVE-2024-53209,\nCVE-2024-56640, CVE-2024-49899, CVE-2024-50247, CVE-2024-50150,\nCVE-2024-53058, CVE-2024-50153, CVE-2024-56689, CVE-2024-50283,\nCVE-2024-50251, CVE-2024-56578, CVE-2024-50303, CVE-2024-56569,\nCVE-2024-53134, CVE-2024-50158, CVE-2024-56592, CVE-2024-50300,\nCVE-2024-57838, CVE-2024-50205, CVE-2024-56562, CVE-2024-57843,\nCVE-2024-53084, CVE-2024-56532, CVE-2024-50127, CVE-2024-56584,\nCVE-2024-53196, CVE-2024-56722, CVE-2024-50215, CVE-2022-49034,\nCVE-2024-47809, CVE-2024-56744, CVE-2024-50121, CVE-2024-53083,\nCVE-2024-56540, CVE-2024-50209, CVE-2024-56787, CVE-2024-48873,\nCVE-2024-53221, CVE-2024-56746, CVE-2024-50238, CVE-2024-50226,\nCVE-2024-52332, CVE-2024-56649, CVE-2024-56546, CVE-2024-53223,\nCVE-2024-50259, CVE-2024-50287, CVE-2024-56701, CVE-2024-56692,\nCVE-2024-50243, CVE-2024-53160, CVE-2024-56619, CVE-2024-50128,\nCVE-2024-53173, CVE-2024-53127, CVE-2024-56720, CVE-2024-56633,\nCVE-2024-48875, CVE-2024-56775, CVE-2024-50155, CVE-2024-56611,\nCVE-2024-56539, CVE-2024-50282, CVE-2024-56600, CVE-2024-53110,\nCVE-2024-50111, CVE-2024-56773, CVE-2024-53161, CVE-2024-56615,\nCVE-2024-56786, CVE-2024-56783, CVE-2024-56645, CVE-2024-50216,\nCVE-2024-56605, CVE-2024-56622, CVE-2024-56613, CVE-2024-50245,\nCVE-2024-50240, CVE-2024-53222, CVE-2024-53203, CVE-2024-53042,\nCVE-2024-56724, CVE-2024-57876, CVE-2024-49906, CVE-2024-56596,\nCVE-2024-50234, CVE-2024-41014, CVE-2024-53053, CVE-2024-48881,\nCVE-2024-56601, CVE-2024-56581, CVE-2024-56609, CVE-2024-56576,\nCVE-2024-53044, CVE-2024-53680, CVE-2024-50170, CVE-2024-50116,\nCVE-2024-56705, CVE-2024-53138, CVE-2024-53162, CVE-2024-50136,\nCVE-2024-53210, CVE-2024-50167, CVE-2024-50292, CVE-2024-53067,\nCVE-2024-53101, CVE-2024-56691, CVE-2024-53200, CVE-2024-50255,\nCVE-2024-53142, CVE-2025-21700, CVE-2024-50104, CVE-2024-56687,\nCVE-2024-50163, CVE-2024-56756, CVE-2024-50218, CVE-2024-56550,\nCVE-2024-53202, CVE-2024-50137, CVE-2024-50270, CVE-2024-56641,\nCVE-2024-53154, CVE-2024-53224, CVE-2024-53155, CVE-2024-50124,\nCVE-2024-41935, CVE-2024-50265, CVE-2024-53190, CVE-2024-50256,\nCVE-2024-53234, CVE-2024-56693, CVE-2024-50143, CVE-2024-53181,\nCVE-2024-50154, CVE-2024-53233, CVE-2024-56771, CVE-2024-53236,\nCVE-2024-53227, CVE-2024-56572, CVE-2024-53126, CVE-2024-56551,\nCVE-2024-50299, CVE-2024-53218, CVE-2024-50135, CVE-2024-53188,\nCVE-2024-56635, CVE-2024-53055, CVE-2024-56751, CVE-2024-56577,\nCVE-2024-50289, CVE-2024-56590, CVE-2024-56745, CVE-2024-53176,\nCVE-2024-56681, CVE-2024-50160, CVE-2024-56557, CVE-2024-53213,\nCVE-2024-50267, CVE-2024-50146, CVE-2024-56627, CVE-2024-50290,\nCVE-2024-56565, CVE-2024-56752, CVE-2024-56603, CVE-2024-50246,\nCVE-2024-56690, CVE-2024-50222, CVE-2024-53087, CVE-2024-53091,\nCVE-2024-50115, CVE-2024-53106, CVE-2024-50250, CVE-2024-50242,\nCVE-2024-50248, CVE-2024-53229, CVE-2024-56588, CVE-2024-56785,\nCVE-2024-53195, CVE-2025-21702, CVE-2024-53059, CVE-2024-50107,\nCVE-2024-50139, CVE-2024-50276, CVE-2024-56543, CVE-2024-53228,\nCVE-2024-50232, CVE-2024-53128, CVE-2024-56651, CVE-2024-53047,\nCVE-2024-56726, CVE-2024-50159, CVE-2024-50231, CVE-2024-56545,\nCVE-2024-56778, CVE-2024-56602, CVE-2024-50221, CVE-2024-56754,\nCVE-2024-56704, CVE-2024-56650, CVE-2024-57850, CVE-2024-50206,\nCVE-2024-56573, CVE-2024-56703, CVE-2024-53208, CVE-2024-53158,\nCVE-2024-50274, CVE-2024-56638, CVE-2024-50151, CVE-2024-53239,\nCVE-2024-56742, CVE-2024-50237, CVE-2024-53066, CVE-2024-56580,\nCVE-2024-56688, CVE-2024-53089, CVE-2024-56777, CVE-2024-50138,\nCVE-2024-53198, CVE-2024-56589, CVE-2024-56694, CVE-2024-50261,\nCVE-2024-53147, CVE-2024-50263, CVE-2024-56644, CVE-2024-56597,\nCVE-2024-53197, CVE-2024-50164, CVE-2024-53191, CVE-2024-56549,\nCVE-2024-50284, CVE-2024-57849, CVE-2024-56594, CVE-2024-56782,\nCVE-2024-50235, CVE-2024-49569, CVE-2024-53237, CVE-2024-56643,\nCVE-2024-53109, CVE-2024-53157, CVE-2024-56637, CVE-2024-56623,\nCVE-2024-56683, CVE-2024-50257, CVE-2024-56765, CVE-2024-53201,\nCVE-2024-53050, CVE-2024-53120, CVE-2024-53121, CVE-2024-50126,\nCVE-2024-56774, CVE-2024-53219, CVE-2024-56616, CVE-2024-50223,\nCVE-2024-41932, CVE-2024-50271, CVE-2024-56593, CVE-2024-50285,\nCVE-2024-53113, CVE-2025-21993, CVE-2024-56607, CVE-2024-50252,\nCVE-2024-56610, CVE-2024-53043, CVE-2024-50120, CVE-2024-44955,\nCVE-2024-50118, CVE-2024-53130, CVE-2024-56566, CVE-2024-53146,\nCVE-2024-56721, CVE-2024-53079, CVE-2024-56685, CVE-2024-50145,\nCVE-2024-56755, CVE-2024-50268, CVE-2024-53046, CVE-2024-50010,\nCVE-2024-56531, CVE-2024-53129, CVE-2024-47794, CVE-2024-53119,\nCVE-2024-50297, CVE-2024-56728, CVE-2025-21701, CVE-2024-53163,\nCVE-2024-56739, CVE-2024-56538, CVE-2024-50294, CVE-2024-53183,\nCVE-2024-53131, CVE-2024-56626, CVE-2024-50133, CVE-2024-53151,\nCVE-2024-56679, CVE-2024-50225, CVE-2024-50152, CVE-2024-53174,\nCVE-2024-56698, CVE-2024-53105, CVE-2024-53085, CVE-2024-53220,\nCVE-2024-53180, CVE-2024-53060, CVE-2024-53139, CVE-2024-56631,\nCVE-2024-53175, CVE-2024-57872, CVE-2024-56779, CVE-2024-50220,\nCVE-2024-50169, CVE-2024-56772, CVE-2024-53230, CVE-2024-53122,\nCVE-2024-50067, CVE-2024-56558, CVE-2024-45828, CVE-2024-57874,\nCVE-2024-50239, CVE-2024-53214, CVE-2024-56621, CVE-2024-50156,\nCVE-2024-56583, CVE-2024-56776, CVE-2024-50298, CVE-2024-56533,\nCVE-2024-56748, CVE-2024-53114, CVE-2024-53187, CVE-2024-50269,\nCVE-2024-50286, CVE-2024-56579, CVE-2024-56548, CVE-2024-50210,\nCVE-2024-50244, CVE-2024-50291, CVE-2024-56567, CVE-2024-56780,\nCVE-2024-53150, CVE-2024-56636, CVE-2024-56561, CVE-2024-53194,\nCVE-2024-53093, CVE-2024-53117, CVE-2024-53062, CVE-2024-53123,\nCVE-2024-50236, CVE-2024-56630, CVE-2024-56678, CVE-2024-48876,\nCVE-2024-50249, CVE-2024-53099, CVE-2024-53048, CVE-2024-50296,\nCVE-2024-50131, CVE-2024-50105, CVE-2024-50141, CVE-2024-56729,\nCVE-2024-53217, CVE-2024-50295, CVE-2024-50130, CVE-2024-56725,\nCVE-2024-42122, CVE-2024-56570, CVE-2024-53118, CVE-2024-50112,\nCVE-2024-50203, CVE-2024-53178, CVE-2024-53068, CVE-2024-50272,\nCVE-2024-53232, CVE-2024-53088, CVE-2024-56647, CVE-2024-53076,\nCVE-2024-53100, CVE-2024-53096, CVE-2024-56747, CVE-2024-53045,\nCVE-2024-53086, CVE-2024-50147, CVE-2024-53081, CVE-2024-50273,\nCVE-2024-50103, CVE-2024-53107, CVE-2024-53095, CVE-2024-47141,\nCVE-2024-56604, CVE-2024-50304, CVE-2024-53169, CVE-2024-50162,\nCVE-2024-53112)\n","status":"published","published":"2025-04-23T14:20:38Z","modified":"2026-11-03T21:19:53.332188631Z","updated_at":"2026-11-03T21:42:57.147559Z"},{"id":"USN-7449-2","title":"linux-hwe-6.8 vulnerabilities","description":"Several security issues were discovered in the Linux kernel.\nAn attacker could possibly use these to compromise the system.\nThis update corrects flaws in the following subsystems:\n  - ARM64 architecture;\n  - MIPS architecture;\n  - PowerPC architecture;\n  - RISC-V architecture;\n  - S390 architecture;\n  - SuperH RISC architecture;\n  - User-Mode Linux (UML);\n  - x86 architecture;\n  - Block layer subsystem;\n  - Cryptographic API;\n  - Compute Acceleration Framework;\n  - ACPI drivers;\n  - Drivers core;\n  - RAM backed block device driver;\n  - Compressed RAM block device driver;\n  - TPM device driver;\n  - Clock framework and drivers;\n  - Data acquisition framework and drivers;\n  - CPU frequency scaling framework;\n  - Hardware crypto device drivers;\n  - CXL (Compute Express Link) drivers;\n  - EDAC drivers;\n  - ARM SCMI message protocol;\n  - ARM SCPI message protocol;\n  - EFI core;\n  - GPIO subsystem;\n  - GPU drivers;\n  - HID subsystem;\n  - I3C subsystem;\n  - IIO ADC drivers;\n  - IIO subsystem;\n  - InfiniBand drivers;\n  - IOMMU subsystem;\n  - LED subsystem;\n  - Multiple devices driver;\n  - Media drivers;\n  - Multifunction device drivers;\n  - MMC subsystem;\n  - MTD block device drivers;\n  - Network drivers;\n  - Mellanox network drivers;\n  - STMicroelectronics network drivers;\n  - NVME drivers;\n  - PCI subsystem;\n  - PHY drivers;\n  - Pin controllers subsystem;\n  - x86 platform drivers;\n  - i.MX PM domains;\n  - Voltage and Current Regulator drivers;\n  - StarFive reset controller drivers;\n  - Real Time Clock drivers;\n  - SCSI subsystem;\n  - i.MX SoC drivers;\n  - QCOM SoC drivers;\n  - Xilinx SoC drivers;\n  - SPI subsystem;\n  - Media staging drivers;\n  - TCM subsystem;\n  - UFS subsystem;\n  - DesignWare USB3 driver;\n  - USB Dual Role (OTG-ready) Controller drivers;\n  - USB Serial drivers;\n  - USB Type-C support driver;\n  - USB Type-C Port Controller Manager driver;\n  - USB Type-C Connector System Software Interface driver;\n  - vDPA drivers;\n  - VFIO drivers;\n  - Framebuffer layer;\n  - Xen hypervisor drivers;\n  - AFS file system;\n  - BTRFS file system;\n  - File systems infrastructure;\n  - EROFS file system;\n  - F2FS 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  - NTFS3 file system;\n  - Overlay file system;\n  - Proc file system;\n  - Diskquota system;\n  - SMB network file system;\n  - UBI file system;\n  - DRM display driver;\n  - BPF subsystem;\n  - StackDepot library;\n  - Bluetooth subsystem;\n  - IP tunnels definitions;\n  - Netfilter;\n  - Tracing infrastructure;\n  - User-space API (UAPI);\n  - Kernel init infrastructure;\n  - io_uring subsystem;\n  - IPC subsystem;\n  - DMA mapping infrastructure;\n  - Kernel fork() syscall;\n  - KCSAN framework;\n  - RCU subsystem;\n  - Arbitrary resource management;\n  - Scheduler infrastructure;\n  - Signal handling mechanism;\n  - Task handling mechanism;\n  - Timer subsystem;\n  - KUnit library;\n  - Memory management;\n  - 9P file system network protocol;\n  - CAN network layer;\n  - Networking core;\n  - DCCP (Datagram Congestion Control Protocol);\n  - Ethtool driver;\n  - HSR network protocol;\n  - IEEE802154.4 network protocol;\n  - IPv4 networking;\n  - IPv6 networking;\n  - IUCV driver;\n  - MAC80211 subsystem;\n  - Multipath TCP;\n  - Packet sockets;\n  - RxRPC session sockets;\n  - Network traffic control;\n  - SCTP protocol;\n  - SMC sockets;\n  - Sun RPC protocol;\n  - TIPC protocol;\n  - VMware vSockets driver;\n  - Wireless networking;\n  - eXpress Data Path;\n  - XFRM subsystem;\n  - Integrity Measurement Architecture(IMA) framework;\n  - Key management;\n  - ALSA framework;\n  - FireWire sound drivers;\n  - HD-audio driver;\n  - MediaTek ASoC drivers;\n  - QCOM ASoC drivers;\n  - SoC audio core drivers;\n  - STMicroelectronics SoC drivers;\n  - USB sound devices;\n(CVE-2022-49034, CVE-2024-56632, CVE-2024-53177, CVE-2024-56679,\nCVE-2024-48881, CVE-2024-56690, CVE-2024-50216, CVE-2024-50269,\nCVE-2024-53079, CVE-2024-50111, CVE-2024-50103, CVE-2024-50147,\nCVE-2024-53089, CVE-2024-56579, CVE-2024-53110, CVE-2024-50203,\nCVE-2024-50243, CVE-2024-57872, CVE-2024-53181, CVE-2024-50155,\nCVE-2024-53196, CVE-2024-50154, CVE-2024-53084, CVE-2024-50128,\nCVE-2024-53146, CVE-2024-53047, CVE-2024-56619, CVE-2024-50259,\nCVE-2024-56724, CVE-2024-50270, CVE-2024-44955, CVE-2024-53166,\nCVE-2024-56771, CVE-2024-53081, CVE-2024-50172, CVE-2024-56636,\nCVE-2024-56543, CVE-2024-49906, CVE-2024-45828, CVE-2024-50236,\nCVE-2024-50284, CVE-2024-56694, CVE-2024-56777, CVE-2024-50296,\nCVE-2024-53083, CVE-2024-50299, CVE-2024-53117, CVE-2024-53202,\nCVE-2024-53052, CVE-2024-53145, CVE-2024-53106, CVE-2024-50121,\nCVE-2024-53113, CVE-2024-50300, CVE-2024-50211, CVE-2024-50226,\nCVE-2024-50230, CVE-2024-56698, CVE-2024-53184, CVE-2024-50142,\nCVE-2024-56638, CVE-2024-53043, CVE-2024-56651, CVE-2024-50105,\nCVE-2024-56549, CVE-2024-56644, CVE-2024-50303, CVE-2024-53108,\nCVE-2024-53221, CVE-2024-56576, CVE-2024-50248, CVE-2024-50222,\nCVE-2024-53150, CVE-2024-50287, CVE-2024-53045, CVE-2024-53213,\nCVE-2024-50127, CVE-2024-53129, CVE-2024-53217, CVE-2024-53130,\nCVE-2024-56640, CVE-2024-56634, CVE-2024-53169, CVE-2024-53200,\nCVE-2024-53151, CVE-2024-53087, CVE-2024-53050, CVE-2024-53237,\nCVE-2024-50159, CVE-2024-43098, CVE-2025-21831, CVE-2024-52332,\nCVE-2024-53220, CVE-2024-50138, CVE-2024-53115, CVE-2024-50152,\nCVE-2024-56703, CVE-2024-53168, CVE-2024-53123, CVE-2024-50271,\nCVE-2024-50210, CVE-2024-50275, CVE-2024-50153, CVE-2024-50301,\nCVE-2024-56601, CVE-2024-47141, CVE-2024-56649, CVE-2024-50133,\nCVE-2024-56772, CVE-2024-50249, CVE-2024-50118, CVE-2024-56562,\nCVE-2024-53197, CVE-2024-56566, CVE-2024-56725, CVE-2024-56603,\nCVE-2024-56621, CVE-2024-50292, CVE-2024-56561, CVE-2024-53139,\nCVE-2024-56575, CVE-2024-53155, CVE-2024-53048, CVE-2024-50272,\nCVE-2024-53119, CVE-2024-53215, CVE-2024-53172, CVE-2024-50279,\nCVE-2024-56739, CVE-2024-56700, CVE-2024-53135, CVE-2024-50252,\nCVE-2024-56688, CVE-2024-41014, CVE-2024-56604, CVE-2024-53099,\nCVE-2024-56701, CVE-2024-56532, CVE-2024-53222, CVE-2024-56533,\nCVE-2024-56787, CVE-2024-53121, CVE-2024-53053, CVE-2024-50206,\nCVE-2024-53091, CVE-2024-50208, CVE-2024-53134, CVE-2024-56568,\nCVE-2024-53183, CVE-2024-56780, CVE-2024-53194, CVE-2024-56586,\nCVE-2024-53127, CVE-2024-50263, CVE-2024-56776, CVE-2024-53208,\nCVE-2024-50273, CVE-2024-53178, CVE-2024-53214, CVE-2024-50282,\nCVE-2024-50245, CVE-2024-56616, CVE-2024-50145, CVE-2024-50235,\nCVE-2024-50276, CVE-2024-50110, CVE-2024-56748, CVE-2024-56558,\nCVE-2024-53122, CVE-2024-50162, CVE-2024-53131, CVE-2024-50120,\nCVE-2024-56627, CVE-2024-53076, CVE-2024-53228, CVE-2024-53058,\nCVE-2024-53201, CVE-2024-50267, CVE-2024-50104, CVE-2024-53109,\nCVE-2024-56565, CVE-2024-56574, CVE-2024-53231, CVE-2024-56631,\nCVE-2024-56625, CVE-2024-53093, CVE-2024-53051, CVE-2024-50151,\nCVE-2024-53198, CVE-2024-50156, CVE-2024-50244, CVE-2024-53062,\nCVE-2024-56588, CVE-2024-53095, CVE-2024-53142, CVE-2024-53210,\nCVE-2024-53120, CVE-2024-50265, CVE-2024-53185, CVE-2024-56590,\nCVE-2024-50108, CVE-2024-50220, CVE-2024-56756, CVE-2024-56635,\nCVE-2024-50304, CVE-2024-56545, CVE-2024-57849, CVE-2024-56708,\nCVE-2024-53157, CVE-2024-50250, CVE-2024-56678, CVE-2024-57874,\nCVE-2024-53114, CVE-2024-53160, CVE-2024-56723, CVE-2024-56683,\nCVE-2024-56570, CVE-2024-53209, CVE-2024-53126, CVE-2024-56581,\nCVE-2024-53161, CVE-2024-56605, CVE-2024-50115, CVE-2024-50135,\nCVE-2024-53061, CVE-2024-50126, CVE-2024-56573, CVE-2024-56567,\nCVE-2024-56546, CVE-2024-53180, CVE-2024-50283, CVE-2024-50207,\nCVE-2024-50242, CVE-2024-50240, CVE-2024-50130, CVE-2024-47794,\nCVE-2024-56611, CVE-2024-56751, CVE-2024-53138, CVE-2024-53195,\nCVE-2024-47143, CVE-2024-56691, CVE-2025-21702, CVE-2024-56742,\nCVE-2024-53223, CVE-2024-53227, CVE-2024-50150, CVE-2024-56594,\nCVE-2024-50140, CVE-2024-56721, CVE-2024-53059, CVE-2024-41932,\nCVE-2024-41935, CVE-2024-56607, CVE-2024-53191, CVE-2024-53055,\nCVE-2024-50218, CVE-2024-56746, CVE-2024-53096, CVE-2024-56531,\nCVE-2024-57876, CVE-2024-56592, CVE-2024-56722, CVE-2024-56728,\nCVE-2025-21700, CVE-2024-53232, CVE-2024-56608, CVE-2024-53190,\nCVE-2024-56752, CVE-2024-50234, CVE-2024-56572, CVE-2024-53044,\nCVE-2024-50107, CVE-2024-56677, CVE-2024-53111, CVE-2024-50205,\nCVE-2024-56650, CVE-2024-48875, CVE-2024-56609, CVE-2024-53680,\nCVE-2024-56687, CVE-2024-53175, CVE-2024-50231, CVE-2024-56578,\nCVE-2024-50112, CVE-2024-56647, CVE-2024-50294, CVE-2024-50160,\nCVE-2024-50209, CVE-2024-53147, CVE-2024-56707, CVE-2024-53088,\nCVE-2024-50167, CVE-2024-50232, CVE-2024-56642, CVE-2024-56596,\nCVE-2024-50224, CVE-2024-53100, CVE-2024-50137, CVE-2024-56633,\nCVE-2024-56580, CVE-2024-53118, CVE-2024-53082, CVE-2024-56569,\nCVE-2024-56775, CVE-2024-53173, CVE-2024-56727, CVE-2024-56597,\nCVE-2024-56593, CVE-2024-56744, CVE-2024-53105, CVE-2024-56786,\nCVE-2024-53224, CVE-2024-53162, CVE-2024-57838, CVE-2024-50223,\nCVE-2024-50139, CVE-2024-56557, CVE-2024-50221, CVE-2024-50124,\nCVE-2024-50251, CVE-2024-50170, CVE-2024-53230, CVE-2024-53148,\nCVE-2024-56623, CVE-2024-50125, CVE-2024-53094, CVE-2024-50136,\nCVE-2024-50288, CVE-2024-50131, CVE-2024-56689, CVE-2024-56610,\nCVE-2024-53066, CVE-2024-56641, CVE-2024-50067, CVE-2024-53174,\nCVE-2024-53236, CVE-2024-56785, CVE-2024-56637, CVE-2024-56765,\nCVE-2024-50255, CVE-2024-53187, CVE-2024-56643, CVE-2024-56540,\nCVE-2024-50261, CVE-2024-56630, CVE-2024-50169, CVE-2024-50010,\nCVE-2024-53128, CVE-2024-56551, CVE-2024-53090, CVE-2024-56773,\nCVE-2025-21701, CVE-2024-50262, CVE-2024-56648, CVE-2024-56779,\nCVE-2024-50278, CVE-2024-53086, CVE-2024-48873, CVE-2024-56745,\nCVE-2024-50247, CVE-2024-56602, CVE-2024-53085, CVE-2024-50238,\nCVE-2024-56726, CVE-2024-50256, CVE-2024-49899, CVE-2024-50239,\nCVE-2024-50166, CVE-2024-56629, CVE-2024-50225, CVE-2024-53060,\nCVE-2024-53046, CVE-2025-21756, CVE-2024-50051, CVE-2024-50258,\nCVE-2024-50297, CVE-2024-53203, CVE-2024-50257, CVE-2024-56577,\nCVE-2024-50116, CVE-2024-53226, CVE-2024-47809, CVE-2024-50280,\nCVE-2024-53229, CVE-2024-50290, CVE-2024-56600, CVE-2024-50143,\nCVE-2024-53171, CVE-2024-53163, CVE-2024-56704, CVE-2024-50274,\nCVE-2024-53072, CVE-2024-50141, CVE-2024-48876, CVE-2024-56681,\nCVE-2024-56599, CVE-2024-56774, CVE-2024-56583, CVE-2024-50146,\nCVE-2024-56729, CVE-2024-50295, CVE-2024-56693, CVE-2024-53158,\nCVE-2024-56548, CVE-2024-53154, CVE-2024-53188, CVE-2024-50237,\nCVE-2024-56550, CVE-2024-53233, CVE-2024-53068, CVE-2024-56783,\nCVE-2024-50164, CVE-2024-53067, CVE-2024-50298, CVE-2024-50285,\nCVE-2024-50246, CVE-2024-42122, CVE-2024-56754, CVE-2024-56606,\nCVE-2024-53101, CVE-2024-56626, CVE-2024-56589, CVE-2024-56692,\nCVE-2024-53234, CVE-2024-56613, CVE-2024-53133, CVE-2024-56747,\nCVE-2024-57843, CVE-2024-50215, CVE-2024-56705, CVE-2024-56620,\nCVE-2024-56615, CVE-2024-56539, CVE-2024-57850, CVE-2024-56755,\nCVE-2024-56584, CVE-2024-50291, CVE-2024-53218, CVE-2024-56685,\nCVE-2024-50158, CVE-2024-56782, CVE-2024-53176, CVE-2024-53042,\nCVE-2024-50268, CVE-2024-53239, CVE-2024-50286, CVE-2024-53107,\nCVE-2024-56645, CVE-2024-56538, CVE-2024-56622, CVE-2024-56720,\nCVE-2024-50163, CVE-2025-21993, CVE-2024-53219, CVE-2024-56587,\nCVE-2024-56781, CVE-2024-49569, CVE-2024-50289, CVE-2024-53112,\nCVE-2024-56778)\n","status":"published","published":"2025-04-24T17:43:48Z","modified":"2026-11-03T21:17:31.484740669Z","updated_at":"2026-11-03T21:43:54.166508Z"},{"id":"USN-7450-1","title":"linux-gcp, linux-gke, linux-gkeop vulnerabilities","description":"Several security issues were discovered in the Linux kernel.\nAn attacker could possibly use these to compromise the system.\nThis update corrects flaws in the following subsystems:\n  - ARM64 architecture;\n  - MIPS architecture;\n  - PowerPC architecture;\n  - RISC-V architecture;\n  - S390 architecture;\n  - SuperH RISC architecture;\n  - User-Mode Linux (UML);\n  - x86 architecture;\n  - Block layer subsystem;\n  - Cryptographic API;\n  - Compute Acceleration Framework;\n  - ACPI drivers;\n  - Drivers core;\n  - RAM backed block device driver;\n  - Compressed RAM block device driver;\n  - TPM device driver;\n  - Clock framework and drivers;\n  - Data acquisition framework and drivers;\n  - CPU frequency scaling framework;\n  - Hardware crypto device drivers;\n  - CXL (Compute Express Link) drivers;\n  - EDAC drivers;\n  - ARM SCMI message protocol;\n  - ARM SCPI message protocol;\n  - EFI core;\n  - GPIO subsystem;\n  - GPU drivers;\n  - HID subsystem;\n  - I3C subsystem;\n  - IIO ADC drivers;\n  - IIO subsystem;\n  - InfiniBand drivers;\n  - IOMMU subsystem;\n  - LED subsystem;\n  - Multiple devices driver;\n  - Media drivers;\n  - Multifunction device drivers;\n  - MMC subsystem;\n  - MTD block device drivers;\n  - Network drivers;\n  - Mellanox network drivers;\n  - STMicroelectronics network drivers;\n  - NVME drivers;\n  - PCI subsystem;\n  - PHY drivers;\n  - Pin controllers subsystem;\n  - x86 platform drivers;\n  - i.MX PM domains;\n  - Voltage and Current Regulator drivers;\n  - StarFive reset controller drivers;\n  - Real Time Clock drivers;\n  - SCSI subsystem;\n  - i.MX SoC drivers;\n  - QCOM SoC drivers;\n  - Xilinx SoC drivers;\n  - SPI subsystem;\n  - Media staging drivers;\n  - TCM subsystem;\n  - UFS subsystem;\n  - DesignWare USB3 driver;\n  - USB Dual Role (OTG-ready) Controller drivers;\n  - USB Serial drivers;\n  - USB Type-C support driver;\n  - USB Type-C Port Controller Manager driver;\n  - USB Type-C Connector System Software Interface driver;\n  - vDPA drivers;\n  - VFIO drivers;\n  - Framebuffer layer;\n  - Xen hypervisor drivers;\n  - AFS file system;\n  - BTRFS file system;\n  - File systems infrastructure;\n  - EROFS file system;\n  - F2FS 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  - NTFS3 file system;\n  - Overlay file system;\n  - Proc file system;\n  - Diskquota system;\n  - SMB network file system;\n  - UBI file system;\n  - DRM display driver;\n  - BPF subsystem;\n  - StackDepot library;\n  - Bluetooth subsystem;\n  - IP tunnels definitions;\n  - Netfilter;\n  - Tracing infrastructure;\n  - User-space API (UAPI);\n  - Kernel init infrastructure;\n  - io_uring subsystem;\n  - IPC subsystem;\n  - DMA mapping infrastructure;\n  - Kernel fork() syscall;\n  - KCSAN framework;\n  - RCU subsystem;\n  - Arbitrary resource management;\n  - Scheduler infrastructure;\n  - Signal handling mechanism;\n  - Task handling mechanism;\n  - Timer subsystem;\n  - KUnit library;\n  - Memory management;\n  - 9P file system network protocol;\n  - CAN network layer;\n  - Networking core;\n  - DCCP (Datagram Congestion Control Protocol);\n  - Ethtool driver;\n  - HSR network protocol;\n  - IEEE802154.4 network protocol;\n  - IPv4 networking;\n  - IPv6 networking;\n  - IUCV driver;\n  - MAC80211 subsystem;\n  - Multipath TCP;\n  - Packet sockets;\n  - RxRPC session sockets;\n  - Network traffic control;\n  - SCTP protocol;\n  - SMC sockets;\n  - Sun RPC protocol;\n  - TIPC protocol;\n  - VMware vSockets driver;\n  - Wireless networking;\n  - eXpress Data Path;\n  - XFRM subsystem;\n  - Integrity Measurement Architecture(IMA) framework;\n  - Key management;\n  - ALSA framework;\n  - FireWire sound drivers;\n  - HD-audio driver;\n  - MediaTek ASoC drivers;\n  - QCOM ASoC drivers;\n  - SoC audio core drivers;\n  - STMicroelectronics SoC drivers;\n  - USB sound devices;\n(CVE-2024-50051, CVE-2024-56546, CVE-2024-56551, CVE-2024-53236,\nCVE-2024-50244, CVE-2024-53043, CVE-2024-56694, CVE-2025-21700,\nCVE-2024-56700, CVE-2025-21993, CVE-2024-53224, CVE-2024-50105,\nCVE-2024-53100, CVE-2024-56690, CVE-2024-50150, CVE-2024-53223,\nCVE-2024-50285, CVE-2024-50269, CVE-2024-53089, CVE-2024-53044,\nCVE-2024-53175, CVE-2024-57849, CVE-2024-50296, CVE-2024-50120,\nCVE-2024-50147, CVE-2024-56540, CVE-2024-56602, CVE-2024-50289,\nCVE-2024-53127, CVE-2024-56786, CVE-2024-50108, CVE-2024-53045,\nCVE-2024-53067, CVE-2024-50138, CVE-2024-53173, CVE-2024-50143,\nCVE-2024-56678, CVE-2024-53130, CVE-2024-53157, CVE-2024-56723,\nCVE-2024-56623, CVE-2024-53234, CVE-2024-53088, CVE-2024-53068,\nCVE-2024-53195, CVE-2024-53188, CVE-2024-56613, CVE-2024-56561,\nCVE-2024-53218, CVE-2024-50215, CVE-2024-53227, CVE-2024-50139,\nCVE-2024-50170, CVE-2024-56640, CVE-2024-56720, CVE-2024-56780,\nCVE-2024-56705, CVE-2024-53131, CVE-2024-56597, CVE-2024-50224,\nCVE-2024-57843, CVE-2024-50251, CVE-2024-50243, CVE-2024-53200,\nCVE-2024-50280, CVE-2024-50303, CVE-2024-50107, CVE-2024-56606,\nCVE-2024-53237, CVE-2024-53161, CVE-2024-56685, CVE-2024-53185,\nCVE-2024-56785, CVE-2024-53150, CVE-2024-53166, CVE-2024-50141,\nCVE-2024-50158, CVE-2024-47143, CVE-2024-56773, CVE-2024-53090,\nCVE-2024-56778, CVE-2024-50142, CVE-2025-21701, CVE-2024-50301,\nCVE-2024-53050, CVE-2024-50211, CVE-2024-50246, CVE-2024-50252,\nCVE-2024-53122, CVE-2024-53085, CVE-2024-50104, CVE-2024-50288,\nCVE-2024-53151, CVE-2024-56728, CVE-2024-53086, CVE-2024-56568,\nCVE-2024-53133, CVE-2024-50290, CVE-2024-56774, CVE-2024-50278,\nCVE-2024-56565, CVE-2024-53147, CVE-2024-56775, CVE-2024-53239,\nCVE-2024-56533, CVE-2024-50225, CVE-2024-50124, CVE-2024-47794,\nCVE-2024-50163, CVE-2024-53680, CVE-2024-56574, CVE-2024-56605,\nCVE-2024-50112, CVE-2024-53221, CVE-2024-56751, CVE-2024-56538,\nCVE-2024-53123, CVE-2024-56688, CVE-2024-50239, CVE-2024-56742,\nCVE-2024-56752, CVE-2024-53059, CVE-2024-50282, CVE-2024-50238,\nCVE-2024-53108, CVE-2024-50152, CVE-2024-53214, CVE-2024-53226,\nCVE-2024-50292, CVE-2024-56580, CVE-2024-56621, CVE-2024-56593,\nCVE-2024-56689, CVE-2024-56649, CVE-2024-56650, CVE-2024-53203,\nCVE-2024-56626, CVE-2025-21831, CVE-2024-53053, CVE-2024-50257,\nCVE-2024-50203, CVE-2024-56643, CVE-2024-50231, CVE-2024-53066,\nCVE-2024-53105, CVE-2024-53233, CVE-2024-56703, CVE-2024-56725,\nCVE-2024-50172, CVE-2024-53160, CVE-2024-50131, CVE-2024-53196,\nCVE-2024-56645, CVE-2024-50304, CVE-2024-56746, CVE-2024-53232,\nCVE-2024-49906, CVE-2024-53129, CVE-2024-53135, CVE-2024-56545,\nCVE-2024-56600, CVE-2024-56642, CVE-2024-43098, CVE-2024-50291,\nCVE-2024-53219, CVE-2024-53197, CVE-2024-53084, CVE-2024-53155,\nCVE-2024-53094, CVE-2024-56581, CVE-2024-56531, CVE-2024-50300,\nCVE-2024-50232, CVE-2024-56590, CVE-2024-48881, CVE-2024-56708,\nCVE-2024-56632, CVE-2024-53051, CVE-2024-53177, CVE-2024-56698,\nCVE-2024-56707, CVE-2024-56693, CVE-2024-53213, CVE-2024-53121,\nCVE-2024-56681, CVE-2024-56607, CVE-2024-53120, CVE-2024-56615,\nCVE-2024-53109, CVE-2024-50209, CVE-2024-56592, CVE-2024-50103,\nCVE-2024-56722, CVE-2024-53046, CVE-2024-50155, CVE-2024-56765,\nCVE-2024-56572, CVE-2024-56611, CVE-2024-56679, CVE-2024-50259,\nCVE-2024-50111, CVE-2024-53217, CVE-2024-53113, CVE-2024-53101,\nCVE-2024-50208, CVE-2024-53115, CVE-2024-56691, CVE-2024-50137,\nCVE-2024-53194, CVE-2024-41935, CVE-2024-56584, CVE-2022-49034,\nCVE-2024-53072, CVE-2024-41932, CVE-2024-56729, CVE-2024-53095,\nCVE-2024-56755, CVE-2024-50268, CVE-2024-56631, CVE-2024-48875,\nCVE-2025-21756, CVE-2024-50127, CVE-2024-50136, CVE-2024-56562,\nCVE-2024-56683, CVE-2024-50250, CVE-2024-53184, CVE-2024-50205,\nCVE-2024-56543, CVE-2024-56787, CVE-2024-50116, CVE-2024-53096,\nCVE-2024-53169, CVE-2024-50154, CVE-2024-53230, CVE-2024-50247,\nCVE-2024-56570, CVE-2024-56583, CVE-2025-21702, CVE-2024-50126,\nCVE-2024-50151, CVE-2024-53208, CVE-2024-50153, CVE-2024-56619,\nCVE-2024-56532, CVE-2024-56776, CVE-2024-53093, CVE-2024-53139,\nCVE-2024-50263, CVE-2024-41014, CVE-2024-53126, CVE-2024-53052,\nCVE-2024-56636, CVE-2024-50299, CVE-2024-56601, CVE-2024-56569,\nCVE-2024-53168, CVE-2024-53112, CVE-2024-56576, CVE-2024-50230,\nCVE-2024-56630, CVE-2024-50010, CVE-2024-56599, CVE-2024-50156,\nCVE-2024-50286, CVE-2024-53174, CVE-2024-50216, CVE-2024-56744,\nCVE-2024-50265, CVE-2024-50255, CVE-2024-56567, CVE-2024-50118,\nCVE-2024-50276, CVE-2024-53099, CVE-2024-50234, CVE-2024-56745,\nCVE-2024-53114, CVE-2024-50273, CVE-2024-49899, CVE-2024-56608,\nCVE-2024-56625, CVE-2024-56577, CVE-2024-56596, CVE-2024-56634,\nCVE-2024-56777, CVE-2024-47141, CVE-2024-53180, CVE-2024-56701,\nCVE-2024-53158, CVE-2024-56566, CVE-2024-56616, CVE-2024-53117,\nCVE-2024-53181, CVE-2024-50115, CVE-2024-56772, CVE-2024-53163,\nCVE-2024-50140, CVE-2024-56633, CVE-2024-50262, CVE-2024-56677,\nCVE-2024-53201, CVE-2024-57850, CVE-2024-50271, CVE-2024-50279,\nCVE-2024-50226, CVE-2024-53191, CVE-2024-45828, CVE-2024-53106,\nCVE-2024-50275, CVE-2024-50245, CVE-2024-56783, CVE-2024-50261,\nCVE-2024-50283, CVE-2024-53062, CVE-2024-50240, CVE-2024-53183,\nCVE-2024-53222, CVE-2024-53119, CVE-2024-53138, CVE-2024-52332,\nCVE-2024-50167, CVE-2024-53042, CVE-2024-50169, CVE-2024-50162,\nCVE-2024-53087, CVE-2024-50298, CVE-2024-56610, CVE-2024-53060,\nCVE-2024-56578, CVE-2024-50272, CVE-2024-56604, CVE-2024-50287,\nCVE-2024-47809, CVE-2024-56603, CVE-2024-50237, CVE-2024-56647,\nCVE-2024-56747, CVE-2024-50221, CVE-2024-53215, CVE-2024-56550,\nCVE-2024-56748, CVE-2024-56557, CVE-2024-48873, CVE-2024-49569,\nCVE-2024-50206, CVE-2024-56781, CVE-2024-56638, CVE-2024-50218,\nCVE-2024-53055, CVE-2024-57838, CVE-2024-50267, CVE-2024-56575,\nCVE-2024-53202, CVE-2024-53154, CVE-2024-53176, CVE-2024-56779,\nCVE-2024-50210, CVE-2024-56589, CVE-2024-50130, CVE-2024-53190,\nCVE-2024-53082, CVE-2024-56549, CVE-2024-56594, CVE-2024-50294,\nCVE-2024-56754, CVE-2024-53142, CVE-2024-50295, CVE-2024-57872,\nCVE-2024-53081, CVE-2024-56629, CVE-2024-53209, CVE-2024-56558,\nCVE-2024-50164, CVE-2024-53162, CVE-2024-56539, CVE-2024-56721,\nCVE-2024-50121, CVE-2024-56651, CVE-2024-56609, CVE-2024-50207,\nCVE-2024-50220, CVE-2024-53228, CVE-2024-53171, CVE-2024-53110,\nCVE-2024-53146, CVE-2024-53148, CVE-2024-50284, CVE-2024-56739,\nCVE-2024-48876, CVE-2024-50222, CVE-2024-53079, CVE-2024-53048,\nCVE-2024-50135, CVE-2024-56726, CVE-2024-50110, CVE-2024-53145,\nCVE-2024-53198, CVE-2024-50249, CVE-2024-44955, CVE-2024-56573,\nCVE-2024-53047, CVE-2024-50133, CVE-2024-53091, CVE-2024-53134,\nCVE-2024-50128, CVE-2024-56648, CVE-2024-53111, CVE-2024-50258,\nCVE-2024-56587, CVE-2024-56644, CVE-2024-53229, CVE-2024-56727,\nCVE-2024-50159, CVE-2024-57874, CVE-2024-50166, CVE-2024-53210,\nCVE-2024-53172, CVE-2024-53107, CVE-2024-56620, CVE-2024-53076,\nCVE-2024-50236, CVE-2024-56627, CVE-2024-56771, CVE-2024-56724,\nCVE-2024-50235, CVE-2024-50270, CVE-2024-50160, CVE-2024-50067,\nCVE-2024-56641, CVE-2024-50297, CVE-2024-53178, CVE-2024-53231,\nCVE-2024-56692, CVE-2024-53128, CVE-2024-56635, CVE-2024-42122,\nCVE-2024-50223, CVE-2024-56586, CVE-2024-50242, CVE-2024-50256,\nCVE-2024-56756, CVE-2024-56782, CVE-2024-50145, CVE-2024-56704,\nCVE-2024-50146, CVE-2024-53058, CVE-2024-56588, CVE-2024-53187,\nCVE-2024-56548, CVE-2024-56579, CVE-2024-50248, CVE-2024-50125,\nCVE-2024-57876, CVE-2024-56687, CVE-2024-53061, CVE-2024-53118,\nCVE-2024-56622, CVE-2024-53083, CVE-2024-53220, CVE-2024-56637)\n","status":"published","published":"2025-04-23T14:50:25Z","modified":"2026-11-03T21:18:00.636291983Z","updated_at":"2026-11-03T21:43:48.662011Z"},{"id":"USN-7451-1","title":"linux-aws-6.8 vulnerabilities","description":"Several security issues were discovered in the Linux kernel.\nAn attacker could possibly use these to compromise the system.\nThis update corrects flaws in the following subsystems:\n  - ARM64 architecture;\n  - MIPS architecture;\n  - PowerPC architecture;\n  - RISC-V architecture;\n  - S390 architecture;\n  - SuperH RISC architecture;\n  - User-Mode Linux (UML);\n  - x86 architecture;\n  - Block layer subsystem;\n  - Cryptographic API;\n  - Compute Acceleration Framework;\n  - ACPI drivers;\n  - Drivers core;\n  - RAM backed block device driver;\n  - Ublk userspace block driver;\n  - Compressed RAM block device driver;\n  - TPM device driver;\n  - Clock framework and drivers;\n  - Data acquisition framework and drivers;\n  - CPU frequency scaling framework;\n  - Hardware crypto device drivers;\n  - CXL (Compute Express Link) drivers;\n  - DAX dirext access to differentiated memory framework;\n  - EDAC drivers;\n  - ARM SCMI message protocol;\n  - ARM SCPI message protocol;\n  - EFI core;\n  - GPIO subsystem;\n  - GPU drivers;\n  - HID subsystem;\n  - I3C subsystem;\n  - IIO ADC drivers;\n  - IIO subsystem;\n  - InfiniBand drivers;\n  - IOMMU subsystem;\n  - IRQ chip drivers;\n  - LED subsystem;\n  - Multiple devices driver;\n  - Media drivers;\n  - Multifunction device drivers;\n  - MMC subsystem;\n  - MTD block device drivers;\n  - Network drivers;\n  - Mellanox network drivers;\n  - STMicroelectronics network drivers;\n  - NTB driver;\n  - Virtio pmem driver;\n  - NVME drivers;\n  - Parport drivers;\n  - PCI subsystem;\n  - PHY drivers;\n  - Pin controllers subsystem;\n  - x86 platform drivers;\n  - i.MX PM domains;\n  - Voltage and Current Regulator drivers;\n  - StarFive reset controller drivers;\n  - Real Time Clock drivers;\n  - SCSI subsystem;\n  - SuperH / SH-Mobile drivers;\n  - i.MX SoC drivers;\n  - QCOM SoC drivers;\n  - Xilinx SoC drivers;\n  - SPI subsystem;\n  - Direct Digital Synthesis drivers;\n  - Media staging drivers;\n  - TCM subsystem;\n  - Thermal drivers;\n  - TTY drivers;\n  - UFS subsystem;\n  - DesignWare USB3 driver;\n  - USB Gadget drivers;\n  - USB Host Controller drivers;\n  - USB Dual Role (OTG-ready) Controller drivers;\n  - USB Serial drivers;\n  - USB Type-C support driver;\n  - USB Type-C Port Controller Manager driver;\n  - TI TPS6598x USB Power Delivery controller driver;\n  - USB Type-C Connector System Software Interface driver;\n  - vDPA drivers;\n  - VFIO drivers;\n  - Framebuffer layer;\n  - Xen hypervisor drivers;\n  - AFS file system;\n  - BTRFS file system;\n  - File systems infrastructure;\n  - EROFS file system;\n  - Ext4 file system;\n  - F2FS 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  - NTFS3 file system;\n  - Overlay file system;\n  - Proc file system;\n  - Diskquota system;\n  - SMB network file system;\n  - UBI file system;\n  - DRM display driver;\n  - BPF subsystem;\n  - Network file system (NFS) superblock;\n  - StackDepot library;\n  - Bluetooth subsystem;\n  - IP tunnels definitions;\n  - Network namespace;\n  - Netfilter;\n  - Network traffic control;\n  - Network sockets;\n  - Tracing infrastructure;\n  - User-space API (UAPI);\n  - Kernel init infrastructure;\n  - io_uring subsystem;\n  - IPC subsystem;\n  - DMA mapping infrastructure;\n  - Kernel fork() syscall;\n  - KCSAN framework;\n  - Kernel thread helper (kthread);\n  - RCU subsystem;\n  - Arbitrary resource management;\n  - Scheduler infrastructure;\n  - Signal handling mechanism;\n  - Task handling mechanism;\n  - Timer subsystem;\n  - KUnit library;\n  - Maple Tree data structure library;\n  - Memory management;\n  - 9P file system network protocol;\n  - Ethernet bridge;\n  - CAN network layer;\n  - Networking core;\n  - DCCP (Datagram Congestion Control Protocol);\n  - Ethtool driver;\n  - HSR network protocol;\n  - IEEE802154.4 network protocol;\n  - IPv4 networking;\n  - IPv6 networking;\n  - IUCV driver;\n  - MAC80211 subsystem;\n  - Multipath TCP;\n  - Netlink;\n  - Packet sockets;\n  - RxRPC session sockets;\n  - SCTP protocol;\n  - SMC sockets;\n  - Sun RPC protocol;\n  - TIPC protocol;\n  - Unix domain sockets;\n  - VMware vSockets driver;\n  - Wireless networking;\n  - eXpress Data Path;\n  - XFRM subsystem;\n  - Integrity Measurement Architecture(IMA) framework;\n  - Key management;\n  - ALSA framework;\n  - FireWire sound drivers;\n  - HD-audio driver;\n  - MediaTek ASoC drivers;\n  - QCOM ASoC drivers;\n  - SoC audio core drivers;\n  - STMicroelectronics SoC drivers;\n  - USB sound devices;\n(CVE-2024-49914, CVE-2024-53158, CVE-2024-50225, CVE-2024-50224,\nCVE-2024-53139, CVE-2024-56720, CVE-2024-53680, CVE-2024-56650,\nCVE-2024-53113, CVE-2024-53138, CVE-2024-53131, CVE-2024-56614,\nCVE-2024-56586, CVE-2024-50095, CVE-2024-56578, CVE-2024-50131,\nCVE-2024-56748, CVE-2024-50280, CVE-2024-56637, CVE-2024-57850,\nCVE-2024-56651, CVE-2024-52332, CVE-2024-56707, CVE-2024-53166,\nCVE-2024-47794, CVE-2024-53118, CVE-2024-50099, CVE-2024-53089,\nCVE-2024-50216, CVE-2024-50292, CVE-2024-53047, CVE-2024-56627,\nCVE-2024-50108, CVE-2024-50289, CVE-2024-56672, CVE-2024-50291,\nCVE-2024-56785, CVE-2024-53119, CVE-2024-50152, CVE-2024-56589,\nCVE-2024-50229, CVE-2024-53221, CVE-2024-53157, CVE-2024-50201,\nCVE-2024-56679, CVE-2024-50125, CVE-2024-56701, CVE-2024-50128,\nCVE-2024-53230, CVE-2024-56576, CVE-2024-50215, CVE-2024-56606,\nCVE-2024-50146, CVE-2024-50272, CVE-2024-53233, CVE-2024-56782,\nCVE-2024-50009, CVE-2024-56604, CVE-2024-50258, CVE-2024-50140,\nCVE-2024-50232, CVE-2024-53107, CVE-2024-50218, CVE-2024-50221,\nCVE-2024-50143, CVE-2024-56739, CVE-2024-53201, CVE-2024-50130,\nCVE-2024-50141, CVE-2024-53134, CVE-2024-53173, CVE-2024-50063,\nCVE-2024-53060, CVE-2024-53093, CVE-2024-50162, CVE-2024-50111,\nCVE-2024-50153, CVE-2024-53198, CVE-2024-50039, CVE-2024-50180,\nCVE-2024-56568, CVE-2024-56746, CVE-2024-50263, CVE-2024-56575,\nCVE-2024-50040, CVE-2024-56681, CVE-2024-50210, CVE-2024-56566,\nCVE-2024-56611, CVE-2024-53188, CVE-2024-56641, CVE-2024-50240,\nCVE-2024-50252, CVE-2024-56603, CVE-2024-56539, CVE-2024-53187,\nCVE-2024-50223, CVE-2024-53117, CVE-2024-50268, CVE-2024-49921,\nCVE-2024-57876, CVE-2024-56579, CVE-2024-49972, CVE-2024-50239,\nCVE-2024-50148, CVE-2024-50078, CVE-2024-50061, CVE-2024-56626,\nCVE-2024-50286, CVE-2024-56543, CVE-2024-50088, CVE-2024-50069,\nCVE-2024-41935, CVE-2024-57843, CVE-2024-53059, CVE-2024-56605,\nCVE-2024-53234, CVE-2024-53121, CVE-2024-56772, CVE-2024-53120,\nCVE-2024-50171, CVE-2024-56780, CVE-2024-47143, CVE-2024-50065,\nCVE-2024-50124, CVE-2024-56691, CVE-2024-50056, CVE-2024-56645,\nCVE-2024-53200, CVE-2024-50295, CVE-2024-56551, CVE-2024-56565,\nCVE-2024-50118, CVE-2024-50206, CVE-2024-50116, CVE-2024-56545,\nCVE-2024-50211, CVE-2024-50025, CVE-2024-53129, CVE-2024-49569,\nCVE-2024-56781, CVE-2024-56574, CVE-2024-50244, CVE-2024-50103,\nCVE-2024-50112, CVE-2024-47726, CVE-2024-53154, CVE-2024-53090,\nCVE-2024-50064, CVE-2024-50231, CVE-2024-56572, CVE-2024-56649,\nCVE-2024-50195, CVE-2024-49899, CVE-2024-53050, CVE-2024-53063,\nCVE-2025-21702, CVE-2024-50233, CVE-2024-49920, CVE-2024-44955,\nCVE-2024-50049, CVE-2024-50087, CVE-2024-56631, CVE-2024-50196,\nCVE-2024-50183, CVE-2024-50115, CVE-2024-53148, CVE-2024-53083,\nCVE-2024-50220, CVE-2024-53076, CVE-2024-50075, CVE-2024-53171,\nCVE-2024-50237, CVE-2024-50251, CVE-2024-50245, CVE-2024-56581,\nCVE-2024-50032, CVE-2024-56642, CVE-2024-50051, CVE-2024-56635,\nCVE-2024-56596, CVE-2024-56726, CVE-2024-57798, CVE-2024-50235,\nCVE-2024-50248, CVE-2024-53237, CVE-2024-50120, CVE-2024-56629,\nCVE-2024-56776, CVE-2024-47809, CVE-2024-50024, CVE-2024-50189,\nCVE-2024-50283, CVE-2024-53160, CVE-2024-50304, CVE-2024-53178,\nCVE-2024-56698, CVE-2024-50090, CVE-2024-50070, CVE-2025-21701,\nCVE-2024-53126, CVE-2024-53087, CVE-2024-56773, CVE-2024-50194,\nCVE-2024-56561, CVE-2024-50154, CVE-2024-50158, CVE-2024-50147,\nCVE-2024-53133, CVE-2024-50187, CVE-2024-53180, CVE-2024-50279,\nCVE-2024-49893, CVE-2024-50138, CVE-2024-53066, CVE-2024-50242,\nCVE-2024-47141, CVE-2024-53115, CVE-2024-50059, CVE-2024-56540,\nCVE-2024-53220, CVE-2024-50288, CVE-2024-57874, CVE-2024-50026,\nCVE-2024-56689, CVE-2024-50042, CVE-2024-49865, CVE-2024-50047,\nCVE-2024-50164, CVE-2024-56549, CVE-2024-56765, CVE-2024-56587,\nCVE-2024-56567, CVE-2024-48875, CVE-2024-56570, CVE-2024-50126,\nCVE-2024-53140, CVE-2024-50167, CVE-2024-57872, CVE-2024-53055,\nCVE-2024-56745, CVE-2024-56633, CVE-2024-53108, CVE-2024-53150,\nCVE-2024-53174, CVE-2024-50077, CVE-2024-56747, CVE-2024-50294,\nCVE-2024-53091, CVE-2024-56742, CVE-2024-56573, CVE-2024-50270,\nCVE-2024-50028, CVE-2024-50285, CVE-2024-56694, CVE-2024-50274,\nCVE-2024-50222, CVE-2024-56634, CVE-2024-50027, CVE-2024-56562,\nCVE-2024-50066, CVE-2024-50301, CVE-2024-53231, CVE-2024-56538,\nCVE-2024-53044, CVE-2024-53106, CVE-2024-41014, CVE-2024-50202,\nCVE-2024-56583, CVE-2024-50267, CVE-2024-53219, CVE-2024-50298,\nCVE-2024-47711, CVE-2024-53048, CVE-2024-56602, CVE-2024-50048,\nCVE-2024-56598, CVE-2024-53105, CVE-2024-53072, CVE-2024-53094,\nCVE-2024-50137, CVE-2024-50269, CVE-2024-53109, CVE-2024-56755,\nCVE-2024-53208, CVE-2024-53165, CVE-2024-56724, CVE-2024-56774,\nCVE-2024-53202, CVE-2024-56752, CVE-2024-53228, CVE-2024-56532,\nCVE-2024-53147, CVE-2024-56582, CVE-2024-56723, CVE-2024-56778,\nCVE-2024-50096, CVE-2024-56599, CVE-2024-56632, CVE-2024-53191,\nCVE-2024-56616, CVE-2024-50080, CVE-2025-21993, CVE-2024-56647,\nCVE-2024-56648, CVE-2024-56722, CVE-2024-53176, CVE-2024-50234,\nCVE-2024-50256, CVE-2024-53145, CVE-2024-50182, CVE-2024-50160,\nCVE-2024-53123, CVE-2024-53227, CVE-2024-50020, CVE-2024-56644,\nCVE-2024-50045, CVE-2024-50036, CVE-2024-56783, CVE-2024-53184,\nCVE-2024-53142, CVE-2024-56725, CVE-2024-49906, CVE-2024-56751,\nCVE-2024-56584, CVE-2024-56663, CVE-2024-53042, CVE-2024-50188,\nCVE-2024-53169, CVE-2024-53085, CVE-2024-56690, CVE-2024-50186,\nCVE-2024-53156, CVE-2024-50250, CVE-2024-56787, CVE-2024-50076,\nCVE-2024-53122, CVE-2024-56643, CVE-2024-50084, CVE-2024-50271,\nCVE-2024-53045, CVE-2024-53058, CVE-2024-50238, CVE-2024-50300,\nCVE-2024-56621, CVE-2024-56729, CVE-2024-50284, CVE-2024-53135,\nCVE-2024-50287, CVE-2024-53161, CVE-2024-56727, CVE-2024-50044,\nCVE-2024-56601, CVE-2024-53194, CVE-2024-50209, CVE-2024-50145,\nCVE-2024-53067, CVE-2024-53215, CVE-2024-56608, CVE-2024-56557,\nCVE-2025-21756, CVE-2024-53229, CVE-2024-53112, CVE-2024-50133,\nCVE-2024-50169, CVE-2025-21700, CVE-2024-50191, CVE-2024-57838,\nCVE-2024-56693, CVE-2024-53183, CVE-2024-50278, CVE-2024-53111,\nCVE-2024-50151, CVE-2024-53053, CVE-2024-56630, CVE-2024-50060,\nCVE-2024-56580, CVE-2024-50230, CVE-2024-53099, CVE-2024-56533,\nCVE-2024-56640, CVE-2024-50282, CVE-2024-50159, CVE-2024-56658,\nCVE-2024-50021, CVE-2024-50275, CVE-2024-50192, CVE-2024-50302,\nCVE-2024-50139, CVE-2024-53096, CVE-2024-50290, CVE-2024-50246,\nCVE-2024-50127, CVE-2024-56569, CVE-2024-50029, CVE-2024-53168,\nCVE-2025-21831, CVE-2024-53052, CVE-2024-56704, CVE-2024-57849,\nCVE-2024-50022, CVE-2024-50208, CVE-2024-53177, CVE-2024-56771,\nCVE-2024-50134, CVE-2024-53151, CVE-2024-50098, CVE-2024-53214,\nCVE-2024-56754, CVE-2024-43098, CVE-2024-50299, CVE-2024-50255,\nCVE-2024-56687, CVE-2024-53196, CVE-2024-53217, CVE-2024-48873,\nCVE-2024-53062, CVE-2024-53101, CVE-2024-56592, CVE-2024-53086,\nCVE-2024-50207, CVE-2024-50035, CVE-2024-50067, CVE-2024-50072,\nCVE-2024-56619, CVE-2024-53088, CVE-2024-53210, CVE-2024-56721,\nCVE-2024-56531, CVE-2024-56705, CVE-2024-50085, CVE-2024-53222,\nCVE-2024-50262, CVE-2024-50156, CVE-2024-45828, CVE-2024-53181,\nCVE-2024-50083, CVE-2024-53068, CVE-2024-53081, CVE-2024-50107,\nCVE-2022-49034, CVE-2024-50276, CVE-2024-50249, CVE-2024-50030,\nCVE-2024-53203, CVE-2024-50185, CVE-2024-50163, CVE-2024-50184,\nCVE-2024-53162, CVE-2024-56703, CVE-2024-56685, CVE-2024-56548,\nCVE-2024-53100, CVE-2024-56597, CVE-2024-53110, CVE-2024-50086,\nCVE-2024-56636, CVE-2024-56677, CVE-2024-50166, CVE-2024-50247,\nCVE-2024-53061, CVE-2024-56577, CVE-2024-50062, CVE-2024-56786,\nCVE-2024-50019, CVE-2024-56609, CVE-2024-48881, CVE-2024-53239,\nCVE-2024-53128, CVE-2024-56692, CVE-2024-50068, CVE-2024-56683,\nCVE-2024-56594, CVE-2024-53209, CVE-2024-50142, CVE-2024-56590,\nCVE-2024-56613, CVE-2024-53163, CVE-2024-50261, CVE-2024-53224,\nCVE-2024-56595, CVE-2024-50150, CVE-2024-53079, CVE-2024-56775,\nCVE-2024-53095, CVE-2024-50105, CVE-2024-50193, CVE-2024-53043,\nCVE-2024-53213, CVE-2024-56638, CVE-2024-50023, CVE-2024-50057,\nCVE-2024-50038, CVE-2024-56550, CVE-2024-53232, CVE-2024-50155,\nCVE-2024-53155, CVE-2024-53197, CVE-2024-50046, CVE-2024-50236,\nCVE-2024-50243, CVE-2024-53172, CVE-2024-53226, CVE-2024-53146,\nCVE-2024-42122, CVE-2024-50199, CVE-2024-50205, CVE-2024-50170,\nCVE-2024-50200, CVE-2024-56620, CVE-2024-50104, CVE-2024-56593,\nCVE-2024-53223, CVE-2024-53082, CVE-2024-50058, CVE-2024-56688,\nCVE-2024-56607, CVE-2024-53195, CVE-2024-41932, CVE-2024-56756,\nCVE-2024-53236, CVE-2024-56622, CVE-2024-50093, CVE-2024-53114,\nCVE-2024-56600, CVE-2024-53190, CVE-2024-53130, CVE-2024-53084,\nCVE-2024-56610, CVE-2024-53170, CVE-2024-53127, CVE-2024-49968,\nCVE-2024-50203, CVE-2024-50259, CVE-2024-50031, CVE-2024-53051,\nCVE-2024-50226, CVE-2024-56779, CVE-2024-56588, CVE-2024-56777,\nCVE-2024-50121, CVE-2024-50055, CVE-2024-50033, CVE-2024-50010,\nCVE-2024-53218, CVE-2024-56744, CVE-2024-50297, CVE-2024-50257,\nCVE-2024-56558, CVE-2024-50073, CVE-2024-56623, CVE-2024-50135,\nCVE-2024-50197, CVE-2024-56625, CVE-2024-56546, CVE-2024-53175,\nCVE-2024-50273, CVE-2024-50082, CVE-2024-56615, CVE-2024-53185,\nCVE-2024-50172, CVE-2024-50265, CVE-2024-56678, CVE-2024-48876,\nCVE-2024-50110, CVE-2024-50101, CVE-2024-50041, CVE-2024-53046,\nCVE-2024-50198, CVE-2024-50303, CVE-2024-56708, CVE-2024-56728,\nCVE-2024-50136, CVE-2024-56700, CVE-2024-50074, CVE-2024-50117,\nCVE-2024-50296)\n","status":"published","published":"2025-04-23T15:11:40Z","modified":"2026-11-03T21:17:42.731974836Z","updated_at":"2026-11-03T21:43:54.166508Z"},{"id":"USN-7452-1","title":"linux-gcp-6.8 vulnerabilities","description":"Several security issues were discovered in the Linux kernel.\nAn attacker could possibly use these to compromise the system.\nThis update corrects flaws in the following subsystems:\n  - ARM64 architecture;\n  - MIPS architecture;\n  - PowerPC architecture;\n  - RISC-V architecture;\n  - S390 architecture;\n  - SuperH RISC architecture;\n  - User-Mode Linux (UML);\n  - x86 architecture;\n  - Block layer subsystem;\n  - Cryptographic API;\n  - Compute Acceleration Framework;\n  - ACPI drivers;\n  - Drivers core;\n  - RAM backed block device driver;\n  - Compressed RAM block device driver;\n  - TPM device driver;\n  - Clock framework and drivers;\n  - Data acquisition framework and drivers;\n  - CPU frequency scaling framework;\n  - Hardware crypto device drivers;\n  - CXL (Compute Express Link) drivers;\n  - EDAC drivers;\n  - ARM SCMI message protocol;\n  - ARM SCPI message protocol;\n  - EFI core;\n  - GPIO subsystem;\n  - GPU drivers;\n  - HID subsystem;\n  - I3C subsystem;\n  - IIO ADC drivers;\n  - IIO subsystem;\n  - InfiniBand drivers;\n  - IOMMU subsystem;\n  - LED subsystem;\n  - Multiple devices driver;\n  - Media drivers;\n  - Multifunction device drivers;\n  - MMC subsystem;\n  - MTD block device drivers;\n  - Network drivers;\n  - Mellanox network drivers;\n  - STMicroelectronics network drivers;\n  - NVME drivers;\n  - PCI subsystem;\n  - PHY drivers;\n  - Pin controllers subsystem;\n  - x86 platform drivers;\n  - i.MX PM domains;\n  - Voltage and Current Regulator drivers;\n  - StarFive reset controller drivers;\n  - Real Time Clock drivers;\n  - SCSI subsystem;\n  - i.MX SoC drivers;\n  - QCOM SoC drivers;\n  - Xilinx SoC drivers;\n  - SPI subsystem;\n  - Media staging drivers;\n  - TCM subsystem;\n  - UFS subsystem;\n  - DesignWare USB3 driver;\n  - USB Dual Role (OTG-ready) Controller drivers;\n  - USB Serial drivers;\n  - USB Type-C support driver;\n  - USB Type-C Port Controller Manager driver;\n  - USB Type-C Connector System Software Interface driver;\n  - vDPA drivers;\n  - VFIO drivers;\n  - Framebuffer layer;\n  - Xen hypervisor drivers;\n  - AFS file system;\n  - BTRFS file system;\n  - File systems infrastructure;\n  - EROFS file system;\n  - F2FS 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  - NTFS3 file system;\n  - Overlay file system;\n  - Proc file system;\n  - Diskquota system;\n  - SMB network file system;\n  - UBI file system;\n  - DRM display driver;\n  - BPF subsystem;\n  - StackDepot library;\n  - Bluetooth subsystem;\n  - IP tunnels definitions;\n  - Netfilter;\n  - Tracing infrastructure;\n  - User-space API (UAPI);\n  - Kernel init infrastructure;\n  - io_uring subsystem;\n  - IPC subsystem;\n  - DMA mapping infrastructure;\n  - Kernel fork() syscall;\n  - KCSAN framework;\n  - RCU subsystem;\n  - Arbitrary resource management;\n  - Scheduler infrastructure;\n  - Signal handling mechanism;\n  - Task handling mechanism;\n  - Timer subsystem;\n  - KUnit library;\n  - Memory management;\n  - 9P file system network protocol;\n  - CAN network layer;\n  - Networking core;\n  - DCCP (Datagram Congestion Control Protocol);\n  - Ethtool driver;\n  - HSR network protocol;\n  - IEEE802154.4 network protocol;\n  - IPv4 networking;\n  - IPv6 networking;\n  - IUCV driver;\n  - MAC80211 subsystem;\n  - Multipath TCP;\n  - Packet sockets;\n  - RxRPC session sockets;\n  - Network traffic control;\n  - SCTP protocol;\n  - SMC sockets;\n  - Sun RPC protocol;\n  - TIPC protocol;\n  - VMware vSockets driver;\n  - Wireless networking;\n  - eXpress Data Path;\n  - XFRM subsystem;\n  - Integrity Measurement Architecture(IMA) framework;\n  - Key management;\n  - ALSA framework;\n  - FireWire sound drivers;\n  - HD-audio driver;\n  - MediaTek ASoC drivers;\n  - QCOM ASoC drivers;\n  - SoC audio core drivers;\n  - STMicroelectronics SoC drivers;\n  - USB sound devices;\n(CVE-2024-56724, CVE-2024-50108, CVE-2024-56631, CVE-2024-50236,\nCVE-2022-49034, CVE-2024-50133, CVE-2024-53108, CVE-2024-56605,\nCVE-2024-56599, CVE-2024-56721, CVE-2024-53110, CVE-2024-56751,\nCVE-2024-53120, CVE-2024-53198, CVE-2024-57876, CVE-2024-50285,\nCVE-2024-53133, CVE-2024-56681, CVE-2024-56581, CVE-2025-21701,\nCVE-2024-53086, CVE-2024-53201, CVE-2024-56630, CVE-2024-53222,\nCVE-2024-50139, CVE-2024-53084, CVE-2024-53214, CVE-2024-53183,\nCVE-2024-56600, CVE-2024-50286, CVE-2024-53232, CVE-2024-56777,\nCVE-2024-56540, CVE-2024-50121, CVE-2024-50284, CVE-2024-56621,\nCVE-2024-53195, CVE-2024-50279, CVE-2024-53203, CVE-2024-50104,\nCVE-2024-50238, CVE-2024-53177, CVE-2024-53053, CVE-2024-50297,\nCVE-2024-56569, CVE-2024-53131, CVE-2024-56642, CVE-2024-56752,\nCVE-2024-53079, CVE-2024-56705, CVE-2024-56679, CVE-2024-50272,\nCVE-2024-53231, CVE-2024-53228, CVE-2024-50128, CVE-2024-53229,\nCVE-2024-53055, CVE-2024-53050, CVE-2024-50265, CVE-2024-56703,\nCVE-2024-53114, CVE-2024-50278, CVE-2024-56771, CVE-2024-56708,\nCVE-2024-53082, CVE-2024-50051, CVE-2024-50125, CVE-2024-53109,\nCVE-2024-50257, CVE-2024-50107, CVE-2024-50290, CVE-2024-50211,\nCVE-2024-56609, CVE-2024-53190, CVE-2024-50232, CVE-2024-53134,\nCVE-2024-50142, CVE-2024-50166, CVE-2024-53051, CVE-2024-53224,\nCVE-2024-57872, CVE-2024-53200, CVE-2024-56685, CVE-2025-21700,\nCVE-2024-43098, CVE-2024-56604, CVE-2024-50218, CVE-2024-53113,\nCVE-2024-50242, CVE-2024-50223, CVE-2024-53099, CVE-2024-50162,\nCVE-2024-56587, CVE-2025-21756, CVE-2024-50126, CVE-2024-50067,\nCVE-2024-56539, CVE-2024-50153, CVE-2024-50251, CVE-2024-56726,\nCVE-2024-56780, CVE-2024-56700, CVE-2024-53059, CVE-2024-50252,\nCVE-2024-50269, CVE-2024-50163, CVE-2024-50248, CVE-2024-56578,\nCVE-2024-50240, CVE-2024-53155, CVE-2024-56613, CVE-2024-50118,\nCVE-2024-53091, CVE-2024-57838, CVE-2024-53094, CVE-2024-56638,\nCVE-2024-53175, CVE-2024-53062, CVE-2024-57843, CVE-2024-50210,\nCVE-2024-53237, CVE-2024-50115, CVE-2024-50164, CVE-2024-50208,\nCVE-2024-53068, CVE-2024-41932, CVE-2024-45828, CVE-2024-56635,\nCVE-2024-50112, CVE-2024-50289, CVE-2024-53197, CVE-2024-49906,\nCVE-2024-50304, CVE-2024-56625, CVE-2024-56785, CVE-2024-49899,\nCVE-2024-48876, CVE-2024-53236, CVE-2024-50216, CVE-2024-56756,\nCVE-2024-53178, CVE-2024-53095, CVE-2024-56786, CVE-2024-50111,\nCVE-2024-56643, CVE-2024-56584, CVE-2024-50298, CVE-2024-53089,\nCVE-2024-56550, CVE-2024-50221, CVE-2024-50160, CVE-2024-53188,\nCVE-2024-53066, CVE-2024-53047, CVE-2024-56765, CVE-2024-56601,\nCVE-2024-53146, CVE-2024-56597, CVE-2024-56622, CVE-2024-50205,\nCVE-2024-56647, CVE-2024-56651, CVE-2024-56572, CVE-2024-56568,\nCVE-2024-53087, CVE-2024-50152, CVE-2024-53230, CVE-2024-50276,\nCVE-2024-56562, CVE-2024-56565, CVE-2024-56596, CVE-2024-50237,\nCVE-2024-53194, CVE-2024-53176, CVE-2024-56754, CVE-2024-56593,\nCVE-2024-50225, CVE-2024-47143, CVE-2024-50301, CVE-2025-21831,\nCVE-2024-53151, CVE-2024-50259, CVE-2024-50150, CVE-2024-53145,\nCVE-2024-56590, CVE-2024-50222, CVE-2024-53058, CVE-2024-56687,\nCVE-2024-56690, CVE-2024-56538, CVE-2024-53044, CVE-2024-50292,\nCVE-2024-56577, CVE-2024-50235, CVE-2024-50172, CVE-2024-53127,\nCVE-2024-56615, CVE-2024-53088, CVE-2024-50141, CVE-2024-53223,\nCVE-2024-50135, CVE-2024-50262, CVE-2024-53174, CVE-2024-56545,\nCVE-2024-53093, CVE-2024-56586, CVE-2024-53118, CVE-2024-56727,\nCVE-2024-57874, CVE-2024-50267, CVE-2024-53048, CVE-2024-50250,\nCVE-2024-56533, CVE-2024-53196, CVE-2024-57849, CVE-2024-50010,\nCVE-2024-53129, CVE-2024-53119, CVE-2024-56742, CVE-2024-53045,\nCVE-2024-50226, CVE-2024-53173, CVE-2024-53220, CVE-2024-53185,\nCVE-2024-50294, CVE-2024-53181, CVE-2024-53150, CVE-2024-47809,\nCVE-2024-56746, CVE-2024-53233, CVE-2024-56620, CVE-2024-53213,\nCVE-2024-53163, CVE-2024-56648, CVE-2024-56640, CVE-2024-48873,\nCVE-2024-53209, CVE-2024-50246, CVE-2024-50258, CVE-2024-57850,\nCVE-2024-56549, CVE-2024-56627, CVE-2024-56778, CVE-2024-56720,\nCVE-2024-50256, CVE-2024-56725, CVE-2024-56729, CVE-2024-53046,\nCVE-2024-56573, CVE-2024-53112, CVE-2024-53115, CVE-2024-50234,\nCVE-2024-53172, CVE-2024-56558, CVE-2024-56787, CVE-2024-53184,\nCVE-2024-50131, CVE-2024-50255, CVE-2024-50155, CVE-2024-53187,\nCVE-2024-49569, CVE-2024-56616, CVE-2024-53147, CVE-2024-53123,\nCVE-2024-53162, CVE-2024-53126, CVE-2024-53061, CVE-2024-53210,\nCVE-2024-50138, CVE-2024-53105, CVE-2024-56644, CVE-2024-50105,\nCVE-2024-50207, CVE-2024-53158, CVE-2024-50261, CVE-2024-56693,\nCVE-2024-41935, CVE-2024-53128, CVE-2024-50116, CVE-2024-50143,\nCVE-2025-21702, CVE-2024-53072, CVE-2024-53100, CVE-2024-42122,\nCVE-2024-50303, CVE-2024-50124, CVE-2024-56606, CVE-2024-56557,\nCVE-2024-53083, CVE-2024-50299, CVE-2024-56589, CVE-2024-50296,\nCVE-2024-50275, CVE-2024-56698, CVE-2024-50245, CVE-2024-50263,\nCVE-2024-56633, CVE-2024-50230, CVE-2024-56579, CVE-2024-50231,\nCVE-2024-50295, CVE-2024-56611, CVE-2024-56689, CVE-2024-50159,\nCVE-2024-53680, CVE-2024-56551, CVE-2024-56748, CVE-2024-50249,\nCVE-2024-53168, CVE-2024-56632, CVE-2024-53060, CVE-2024-41014,\nCVE-2024-53121, CVE-2024-50145, CVE-2024-53081, CVE-2024-50151,\nCVE-2024-56781, CVE-2024-50110, CVE-2024-53148, CVE-2024-56567,\nCVE-2024-56641, CVE-2024-53208, CVE-2024-56619, CVE-2024-52332,\nCVE-2024-56775, CVE-2024-56626, CVE-2024-56688, CVE-2024-53215,\nCVE-2024-56783, CVE-2024-50103, CVE-2024-53226, CVE-2024-50282,\nCVE-2024-56755, CVE-2024-50268, CVE-2024-50271, CVE-2024-53076,\nCVE-2024-56610, CVE-2024-56636, CVE-2024-44955, CVE-2024-56623,\nCVE-2024-56694, CVE-2024-56608, CVE-2024-56576, CVE-2024-56692,\nCVE-2024-56723, CVE-2024-53191, CVE-2024-56677, CVE-2024-48875,\nCVE-2024-53106, CVE-2024-56678, CVE-2024-50273, CVE-2024-50206,\nCVE-2024-50170, CVE-2024-56594, CVE-2024-56707, CVE-2024-56649,\nCVE-2024-50167, CVE-2024-56691, CVE-2024-56683, CVE-2024-53052,\nCVE-2024-56747, CVE-2024-47141, CVE-2024-56543, CVE-2024-56574,\nCVE-2024-53085, CVE-2024-50136, CVE-2024-56779, CVE-2024-53111,\nCVE-2024-53139, CVE-2024-56704, CVE-2024-56745, CVE-2024-53234,\nCVE-2024-53138, CVE-2024-50130, CVE-2024-48881, CVE-2024-53107,\nCVE-2024-53218, CVE-2024-56602, CVE-2024-56531, CVE-2024-53154,\nCVE-2024-56532, CVE-2024-53130, CVE-2024-50215, CVE-2024-50147,\nCVE-2024-56607, CVE-2024-50137, CVE-2024-47794, CVE-2024-50158,\nCVE-2024-50239, CVE-2024-56645, CVE-2024-53171, CVE-2024-56592,\nCVE-2024-56772, CVE-2024-50288, CVE-2024-50156, CVE-2024-53180,\nCVE-2024-53169, CVE-2024-56634, CVE-2024-56728, CVE-2024-56722,\nCVE-2024-50209, CVE-2024-56588, CVE-2024-53096, CVE-2024-56548,\nCVE-2024-53166, CVE-2024-56773, CVE-2024-56575, CVE-2024-56650,\nCVE-2024-50127, CVE-2024-56744, CVE-2024-56546, CVE-2024-50154,\nCVE-2024-53202, CVE-2024-56782, CVE-2024-50270, CVE-2024-53157,\nCVE-2024-50243, CVE-2024-56583, CVE-2024-53239, CVE-2025-21993,\nCVE-2024-56603, CVE-2024-56629, CVE-2024-53135, CVE-2024-56739,\nCVE-2024-50283, CVE-2024-56580, CVE-2024-50169, CVE-2024-56774,\nCVE-2024-53042, CVE-2024-53227, CVE-2024-53067, CVE-2024-50224,\nCVE-2024-50247, CVE-2024-53122, CVE-2024-53090, CVE-2024-53221,\nCVE-2024-50146, CVE-2024-53219, CVE-2024-53142, CVE-2024-56570,\nCVE-2024-56566, CVE-2024-50140, CVE-2024-56776, CVE-2024-50287,\nCVE-2024-53161, CVE-2024-50300, CVE-2024-53160, CVE-2024-50203,\nCVE-2024-53217, CVE-2024-50244, CVE-2024-53043, CVE-2024-50280,\nCVE-2024-56637, CVE-2024-53117, CVE-2024-56701, CVE-2024-50291,\nCVE-2024-50120, CVE-2024-53101, CVE-2024-50220, CVE-2024-56561)\n","status":"published","published":"2025-04-23T15:29:33Z","modified":"2026-11-03T21:17:31.85697949Z","updated_at":"2026-11-03T21:43:54.166508Z"},{"id":"USN-7453-1","title":"linux-realtime vulnerabilities","description":"Several security issues were discovered in the Linux kernel.\nAn attacker could possibly use these to compromise the system.\nThis update corrects flaws in the following subsystems:\n  - ARM64 architecture;\n  - MIPS architecture;\n  - PowerPC architecture;\n  - RISC-V architecture;\n  - S390 architecture;\n  - SuperH RISC architecture;\n  - User-Mode Linux (UML);\n  - x86 architecture;\n  - Block layer subsystem;\n  - Cryptographic API;\n  - Compute Acceleration Framework;\n  - ACPI drivers;\n  - Drivers core;\n  - RAM backed block device driver;\n  - Compressed RAM block device driver;\n  - TPM device driver;\n  - Clock framework and drivers;\n  - Data acquisition framework and drivers;\n  - CPU frequency scaling framework;\n  - Hardware crypto device drivers;\n  - CXL (Compute Express Link) drivers;\n  - EDAC drivers;\n  - ARM SCMI message protocol;\n  - ARM SCPI message protocol;\n  - EFI core;\n  - GPIO subsystem;\n  - GPU drivers;\n  - HID subsystem;\n  - I3C subsystem;\n  - IIO ADC drivers;\n  - IIO subsystem;\n  - InfiniBand drivers;\n  - IOMMU subsystem;\n  - LED subsystem;\n  - Multiple devices driver;\n  - Media drivers;\n  - Multifunction device drivers;\n  - MMC subsystem;\n  - MTD block device drivers;\n  - Network drivers;\n  - Mellanox network drivers;\n  - STMicroelectronics network drivers;\n  - NVME drivers;\n  - PCI subsystem;\n  - PHY drivers;\n  - Pin controllers subsystem;\n  - x86 platform drivers;\n  - i.MX PM domains;\n  - Voltage and Current Regulator drivers;\n  - StarFive reset controller drivers;\n  - Real Time Clock drivers;\n  - SCSI subsystem;\n  - i.MX SoC drivers;\n  - QCOM SoC drivers;\n  - Xilinx SoC drivers;\n  - SPI subsystem;\n  - Media staging drivers;\n  - TCM subsystem;\n  - UFS subsystem;\n  - DesignWare USB3 driver;\n  - USB Dual Role (OTG-ready) Controller drivers;\n  - USB Serial drivers;\n  - USB Type-C support driver;\n  - USB Type-C Port Controller Manager driver;\n  - USB Type-C Connector System Software Interface driver;\n  - vDPA drivers;\n  - VFIO drivers;\n  - Framebuffer layer;\n  - Xen hypervisor drivers;\n  - AFS file system;\n  - BTRFS file system;\n  - File systems infrastructure;\n  - EROFS file system;\n  - F2FS 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  - NTFS3 file system;\n  - Overlay file system;\n  - Proc file system;\n  - Diskquota system;\n  - SMB network file system;\n  - UBI file system;\n  - DRM display driver;\n  - BPF subsystem;\n  - StackDepot library;\n  - Bluetooth subsystem;\n  - IP tunnels definitions;\n  - Netfilter;\n  - Tracing infrastructure;\n  - User-space API (UAPI);\n  - Kernel init infrastructure;\n  - io_uring subsystem;\n  - IPC subsystem;\n  - DMA mapping infrastructure;\n  - Kernel fork() syscall;\n  - KCSAN framework;\n  - RCU subsystem;\n  - Arbitrary resource management;\n  - Scheduler infrastructure;\n  - Signal handling mechanism;\n  - Task handling mechanism;\n  - Timer subsystem;\n  - KUnit library;\n  - Memory management;\n  - 9P file system network protocol;\n  - CAN network layer;\n  - Networking core;\n  - DCCP (Datagram Congestion Control Protocol);\n  - Ethtool driver;\n  - HSR network protocol;\n  - IEEE802154.4 network protocol;\n  - IPv4 networking;\n  - IPv6 networking;\n  - IUCV driver;\n  - MAC80211 subsystem;\n  - Multipath TCP;\n  - Packet sockets;\n  - RxRPC session sockets;\n  - Network traffic control;\n  - SCTP protocol;\n  - SMC sockets;\n  - Sun RPC protocol;\n  - TIPC protocol;\n  - VMware vSockets driver;\n  - Wireless networking;\n  - eXpress Data Path;\n  - XFRM subsystem;\n  - Integrity Measurement Architecture(IMA) framework;\n  - Key management;\n  - ALSA framework;\n  - FireWire sound drivers;\n  - HD-audio driver;\n  - MediaTek ASoC drivers;\n  - QCOM ASoC drivers;\n  - SoC audio core drivers;\n  - STMicroelectronics SoC drivers;\n  - USB sound devices;\n(CVE-2024-53187, CVE-2024-50268, CVE-2024-53161, CVE-2024-56721,\nCVE-2024-53059, CVE-2024-53217, CVE-2022-49034, CVE-2024-53061,\nCVE-2024-50284, CVE-2024-50167, CVE-2024-53221, CVE-2024-56773,\nCVE-2024-53051, CVE-2024-50263, CVE-2024-56631, CVE-2024-53106,\nCVE-2024-50051, CVE-2024-50164, CVE-2024-56533, CVE-2024-53218,\nCVE-2024-56678, CVE-2024-56692, CVE-2024-50155, CVE-2025-21702,\nCVE-2024-53100, CVE-2024-50208, CVE-2024-56707, CVE-2024-56781,\nCVE-2024-48873, CVE-2024-50159, CVE-2024-50138, CVE-2024-50291,\nCVE-2024-53091, CVE-2024-56708, CVE-2024-50142, CVE-2024-50105,\nCVE-2024-50299, CVE-2024-50203, CVE-2024-53210, CVE-2024-56625,\nCVE-2024-53147, CVE-2024-50226, CVE-2024-50294, CVE-2024-50128,\nCVE-2024-53060, CVE-2024-56776, CVE-2024-56586, CVE-2024-56569,\nCVE-2024-53214, CVE-2024-53172, CVE-2024-48881, CVE-2024-53119,\nCVE-2024-50121, CVE-2024-53195, CVE-2024-56703, CVE-2024-56572,\nCVE-2024-50225, CVE-2024-50133, CVE-2024-50280, CVE-2024-53190,\nCVE-2024-56685, CVE-2024-53067, CVE-2024-56538, CVE-2024-53200,\nCVE-2024-56694, CVE-2024-53173, CVE-2024-53118, CVE-2024-53047,\nCVE-2024-50103, CVE-2024-56638, CVE-2024-50257, CVE-2024-53171,\nCVE-2024-57874, CVE-2024-56626, CVE-2024-56611, CVE-2024-56642,\nCVE-2024-56636, CVE-2025-21756, CVE-2024-53188, CVE-2024-56633,\nCVE-2024-53181, CVE-2024-50218, CVE-2024-56771, CVE-2024-56778,\nCVE-2024-56568, CVE-2024-56720, CVE-2024-50249, CVE-2024-53175,\nCVE-2024-53160, CVE-2024-53093, CVE-2024-56754, CVE-2024-53084,\nCVE-2024-53215, CVE-2024-47794, CVE-2024-50287, CVE-2024-49899,\nCVE-2024-56651, CVE-2024-53191, CVE-2024-56744, CVE-2024-50158,\nCVE-2024-56619, CVE-2024-53162, CVE-2024-53208, CVE-2024-56729,\nCVE-2024-56545, CVE-2024-56605, CVE-2024-48876, CVE-2024-50290,\nCVE-2024-53154, CVE-2024-56620, CVE-2025-21700, CVE-2024-53148,\nCVE-2024-50156, CVE-2024-53138, CVE-2024-50269, CVE-2024-50141,\nCVE-2024-56551, CVE-2024-50221, CVE-2024-50288, CVE-2024-56546,\nCVE-2024-50209, CVE-2024-53234, CVE-2024-50232, CVE-2024-53086,\nCVE-2024-53232, CVE-2024-50112, CVE-2024-57838, CVE-2024-53220,\nCVE-2024-53121, CVE-2024-53142, CVE-2024-56610, CVE-2024-57872,\nCVE-2024-50160, CVE-2024-50010, CVE-2024-56690, CVE-2024-53128,\nCVE-2024-56650, CVE-2024-53158, CVE-2024-57850, CVE-2024-53088,\nCVE-2024-56629, CVE-2024-50239, CVE-2024-50145, CVE-2024-56724,\nCVE-2024-56566, CVE-2024-50303, CVE-2024-53053, CVE-2024-56539,\nCVE-2024-50153, CVE-2024-50242, CVE-2024-53055, CVE-2024-53127,\nCVE-2024-56751, CVE-2024-56588, CVE-2024-56691, CVE-2024-53180,\nCVE-2024-53076, CVE-2024-53072, CVE-2024-53196, CVE-2024-56679,\nCVE-2024-53042, CVE-2024-56777, CVE-2024-42122, CVE-2024-50244,\nCVE-2024-50169, CVE-2024-50205, CVE-2024-53110, CVE-2024-53157,\nCVE-2024-50295, CVE-2024-53680, CVE-2024-56613, CVE-2024-53194,\nCVE-2024-56779, CVE-2024-56597, CVE-2024-50130, CVE-2024-53083,\nCVE-2024-50246, CVE-2024-53131, CVE-2024-53107, CVE-2024-56756,\nCVE-2024-56727, CVE-2024-50162, CVE-2024-50273, CVE-2024-56726,\nCVE-2024-50255, CVE-2024-53185, CVE-2024-50137, CVE-2024-41932,\nCVE-2024-56787, CVE-2024-56765, CVE-2024-56601, CVE-2024-56698,\nCVE-2024-56558, CVE-2024-57876, CVE-2024-56581, CVE-2024-53202,\nCVE-2024-50236, CVE-2024-56681, CVE-2024-50297, CVE-2024-53203,\nCVE-2024-53081, CVE-2024-53155, CVE-2024-50275, CVE-2024-56630,\nCVE-2024-50166, CVE-2024-57843, CVE-2024-56677, CVE-2024-53094,\nCVE-2024-53048, CVE-2024-50125, CVE-2024-50216, CVE-2024-56774,\nCVE-2024-44955, CVE-2024-56748, CVE-2024-50223, CVE-2024-53087,\nCVE-2024-56775, CVE-2024-50298, CVE-2024-56627, CVE-2024-50139,\nCVE-2024-53134, CVE-2024-53224, CVE-2024-53150, CVE-2024-56704,\nCVE-2024-53198, CVE-2024-53111, CVE-2024-50251, CVE-2024-53082,\nCVE-2024-56785, CVE-2024-56647, CVE-2024-50282, CVE-2024-53058,\nCVE-2024-56637, CVE-2024-50283, CVE-2024-50135, CVE-2024-56622,\nCVE-2024-50301, CVE-2024-50147, CVE-2024-50252, CVE-2024-56567,\nCVE-2024-50230, CVE-2024-53105, CVE-2024-56574, CVE-2024-56589,\nCVE-2024-56543, CVE-2024-50267, CVE-2024-53163, CVE-2024-53123,\nCVE-2024-50248, CVE-2024-53219, CVE-2024-50238, CVE-2024-50296,\nCVE-2024-56593, CVE-2024-56645, CVE-2024-50270, CVE-2024-56780,\nCVE-2024-56576, CVE-2024-53114, CVE-2024-53089, CVE-2024-56644,\nCVE-2024-56739, CVE-2024-53184, CVE-2024-56700, CVE-2024-56786,\nCVE-2024-43098, CVE-2024-50115, CVE-2024-53201, CVE-2024-50220,\nCVE-2024-53226, CVE-2024-53222, CVE-2024-53133, CVE-2024-50222,\nCVE-2024-56640, CVE-2024-50206, CVE-2024-53229, CVE-2024-41014,\nCVE-2024-50272, CVE-2024-56641, CVE-2024-53237, CVE-2024-50207,\nCVE-2024-53168, CVE-2024-56592, CVE-2024-53090, CVE-2024-56782,\nCVE-2024-53043, CVE-2024-50289, CVE-2024-56687, CVE-2024-56755,\nCVE-2024-50111, CVE-2024-57849, CVE-2024-53231, CVE-2024-56550,\nCVE-2024-50247, CVE-2024-53085, CVE-2024-56745, CVE-2024-56600,\nCVE-2024-56596, CVE-2024-50150, CVE-2024-56623, CVE-2024-53108,\nCVE-2024-56579, CVE-2024-50151, CVE-2024-56548, CVE-2024-56565,\nCVE-2024-50110, CVE-2024-47141, CVE-2024-41935, CVE-2024-50274,\nCVE-2024-56603, CVE-2024-53197, CVE-2024-56688, CVE-2024-56577,\nCVE-2024-53174, CVE-2024-56723, CVE-2024-56616, CVE-2024-56573,\nCVE-2024-53044, CVE-2024-53109, CVE-2024-52332, CVE-2024-53079,\nCVE-2024-50131, CVE-2024-53068, CVE-2024-50163, CVE-2024-56772,\nCVE-2024-56634, CVE-2024-53095, CVE-2024-50215, CVE-2024-50243,\nCVE-2024-50265, CVE-2024-56540, CVE-2024-53045, CVE-2024-56562,\nCVE-2024-53135, CVE-2024-56689, CVE-2024-56570, CVE-2024-53066,\nCVE-2024-53145, CVE-2024-56580, CVE-2024-53101, CVE-2024-53177,\nCVE-2024-53183, CVE-2024-53115, CVE-2024-56722, CVE-2025-21993,\nCVE-2024-49569, CVE-2025-21831, CVE-2024-50279, CVE-2024-53052,\nCVE-2024-53113, CVE-2024-50292, CVE-2024-50224, CVE-2024-50259,\nCVE-2024-56615, CVE-2024-56649, CVE-2024-53169, CVE-2024-56635,\nCVE-2024-50261, CVE-2024-50172, CVE-2024-53228, CVE-2024-53166,\nCVE-2024-50140, CVE-2024-50170, CVE-2024-56587, CVE-2024-56607,\nCVE-2024-56575, CVE-2024-53099, CVE-2024-49906, CVE-2024-50234,\nCVE-2024-56531, CVE-2024-50127, CVE-2024-56608, CVE-2024-56583,\nCVE-2024-56648, CVE-2024-48875, CVE-2024-50152, CVE-2024-53062,\nCVE-2024-53176, CVE-2024-50250, CVE-2024-53233, CVE-2024-56578,\nCVE-2024-53112, CVE-2024-53146, CVE-2024-56590, CVE-2024-56584,\nCVE-2024-50211, CVE-2024-50116, CVE-2024-50124, CVE-2024-50067,\nCVE-2024-53050, CVE-2024-45828, CVE-2024-47809, CVE-2024-50276,\nCVE-2024-56557, CVE-2024-50304, CVE-2024-56742, CVE-2024-50108,\nCVE-2024-53122, CVE-2024-56602, CVE-2024-50235, CVE-2024-50278,\nCVE-2024-56561, CVE-2024-56632, CVE-2025-21701, CVE-2024-56752,\nCVE-2024-50262, CVE-2024-56621, CVE-2024-53129, CVE-2024-50285,\nCVE-2024-56643, CVE-2024-53227, CVE-2024-50258, CVE-2024-53139,\nCVE-2024-53209, CVE-2024-56701, CVE-2024-56594, CVE-2024-53223,\nCVE-2024-50136, CVE-2024-50256, CVE-2024-53178, CVE-2024-53236,\nCVE-2024-56549, CVE-2024-56683, CVE-2024-53126, CVE-2024-53120,\nCVE-2024-53117, CVE-2024-50104, CVE-2024-50146, CVE-2024-53239,\nCVE-2024-56599, CVE-2024-50210, CVE-2024-56609, CVE-2024-50245,\nCVE-2024-56705, CVE-2024-56604, CVE-2024-50118, CVE-2024-56783,\nCVE-2024-50271, CVE-2024-53151, CVE-2024-56728, CVE-2024-56746,\nCVE-2024-53213, CVE-2024-50231, CVE-2024-56532, CVE-2024-53130,\nCVE-2024-50143, CVE-2024-50286, CVE-2024-53230, CVE-2024-53096,\nCVE-2024-50154, CVE-2024-50237, CVE-2024-50240, CVE-2024-56725,\nCVE-2024-56693, CVE-2024-56606, CVE-2024-50126, CVE-2024-56747,\nCVE-2024-50107, CVE-2024-50300, CVE-2024-47143, CVE-2024-53046,\nCVE-2024-50120)\n","status":"published","published":"2025-04-23T16:18:00Z","modified":"2026-11-03T21:17:47.102596108Z","updated_at":"2026-11-03T21:43:54.166508Z"},{"id":"USN-7468-1","title":"linux-azure-nvidia vulnerabilities","description":"Michael Randrianantenaina discovered that the Bluetooth driver in the Linux\nKernel contained an improper access control vulnerability. A nearby\nattacker could use this to connect a rougue device and possibly execute\narbitrary code. (CVE-2024-8805)\n\nAttila Szász discovered that the HFS+ file system implementation in the\nLinux Kernel contained a heap overflow vulnerability. An attacker could use\na specially crafted file system image that, when mounted, could cause a\ndenial of service (system crash) or possibly execute arbitrary code.\n(CVE-2025-0927)\n\nIt was discovered that the CIFS network file system implementation in the\nLinux kernel did not properly verify the target namespace when handling\nupcalls. An attacker could use this to expose sensitive information.\n(CVE-2025-2312)\n\nSeveral security issues were discovered in the Linux kernel.\nAn attacker could possibly use these to compromise the system.\nThis update corrects flaws in the following subsystems:\n  - ARM64 architecture;\n  - MIPS architecture;\n  - PowerPC architecture;\n  - RISC-V architecture;\n  - S390 architecture;\n  - SuperH RISC architecture;\n  - User-Mode Linux (UML);\n  - x86 architecture;\n  - Block layer subsystem;\n  - Cryptographic API;\n  - Compute Acceleration Framework;\n  - ACPI drivers;\n  - Drivers core;\n  - ATA over ethernet (AOE) driver;\n  - RAM backed block device driver;\n  - Network block device driver;\n  - Ublk userspace block driver;\n  - Compressed RAM block device driver;\n  - TPM device driver;\n  - Clock framework and drivers;\n  - Data acquisition framework and drivers;\n  - CPU frequency scaling framework;\n  - Hardware crypto device drivers;\n  - CXL (Compute Express Link) drivers;\n  - DAX dirext access to differentiated memory framework;\n  - EDAC drivers;\n  - ARM SCMI message protocol;\n  - ARM SCPI message protocol;\n  - EFI core;\n  - iSCSI Boot Firmware Table Attributes driver;\n  - GPIO subsystem;\n  - GPU drivers;\n  - HID subsystem;\n  - I2C subsystem;\n  - I3C subsystem;\n  - IIO ADC drivers;\n  - IIO subsystem;\n  - InfiniBand drivers;\n  - Input Device core drivers;\n  - IOMMU subsystem;\n  - IRQ chip drivers;\n  - LED subsystem;\n  - Mailbox framework;\n  - Multiple devices driver;\n  - Media drivers;\n  - Multifunction device drivers;\n  - MMC subsystem;\n  - MTD block device drivers;\n  - Ethernet bonding driver;\n  - Network drivers;\n  - Mellanox network drivers;\n  - STMicroelectronics network drivers;\n  - NTB driver;\n  - Virtio pmem driver;\n  - NVME drivers;\n  - Parport drivers;\n  - PCI subsystem;\n  - PHY drivers;\n  - Pin controllers subsystem;\n  - x86 platform drivers;\n  - i.MX PM domains;\n  - Voltage and Current Regulator drivers;\n  - StarFive reset controller drivers;\n  - Real Time Clock drivers;\n  - SCSI subsystem;\n  - SuperH / SH-Mobile drivers;\n  - i.MX SoC drivers;\n  - QCOM SoC drivers;\n  - Xilinx SoC drivers;\n  - SPI subsystem;\n  - Direct Digital Synthesis drivers;\n  - Media staging drivers;\n  - TCM subsystem;\n  - Thermal drivers;\n  - TTY drivers;\n  - UFS subsystem;\n  - USB Device Class drivers;\n  - DesignWare USB3 driver;\n  - USB Gadget drivers;\n  - USB Host Controller drivers;\n  - USB Dual Role (OTG-ready) Controller drivers;\n  - USB Serial drivers;\n  - USB Type-C support driver;\n  - USB Type-C Port Controller Manager driver;\n  - TI TPS6598x USB Power Delivery controller driver;\n  - USB Type-C Connector System Software Interface driver;\n  - vDPA drivers;\n  - VFIO drivers;\n  - Virtio Host (VHOST) subsystem;\n  - Framebuffer layer;\n  - Xen hypervisor drivers;\n  - AFS file system;\n  - BTRFS file system;\n  - File systems infrastructure;\n  - Ceph distributed file system;\n  - EROFS file system;\n  - Ext4 file system;\n  - F2FS 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  - NTFS3 file system;\n  - Overlay file system;\n  - Proc file system;\n  - Diskquota system;\n  - SMB network file system;\n  - UBI file system;\n  - DRM display driver;\n  - BPF subsystem;\n  - Kernel Samepage Merging mechanism;\n  - Network file system (NFS) superblock;\n  - Kernel stack handling interfaces;\n  - StackDepot library;\n  - Task handling mechanism;\n  - userfaultfd() syscall;\n  - Bluetooth subsystem;\n  - IP tunnels definitions;\n  - Network namespace;\n  - Netfilter;\n  - Network traffic control;\n  - Network sockets;\n  - TCP network protocol;\n  - Tracing infrastructure;\n  - User-space API (UAPI);\n  - Kernel init infrastructure;\n  - io_uring subsystem;\n  - IPC subsystem;\n  - DMA mapping infrastructure;\n  - Perf events;\n  - Kernel fork() syscall;\n  - KCSAN framework;\n  - Kernel thread helper (kthread);\n  - Padata parallel execution mechanism;\n  - RCU subsystem;\n  - Arbitrary resource management;\n  - Scheduler infrastructure;\n  - Signal handling mechanism;\n  - Static call mechanism;\n  - Timer subsystem;\n  - Vector I/O iterator library;\n  - KUnit library;\n  - Maple Tree data structure library;\n  - Memory management;\n  - 9P file system network protocol;\n  - Ethernet bridge;\n  - CAN network layer;\n  - Networking core;\n  - DCCP (Datagram Congestion Control Protocol);\n  - Distributed Switch Architecture;\n  - Ethtool driver;\n  - HSR network protocol;\n  - IEEE802154.4 network protocol;\n  - IPv4 networking;\n  - IPv6 networking;\n  - IUCV driver;\n  - MAC80211 subsystem;\n  - Multipath TCP;\n  - NCSI (Network Controller Sideband Interface) driver;\n  - Netlink;\n  - Packet sockets;\n  - RxRPC session sockets;\n  - SCTP protocol;\n  - SMC sockets;\n  - Sun RPC protocol;\n  - TIPC protocol;\n  - Unix domain sockets;\n  - VMware vSockets driver;\n  - Wireless networking;\n  - eXpress Data Path;\n  - XFRM subsystem;\n  - Integrity Measurement Architecture(IMA) framework;\n  - Key management;\n  - ALSA framework;\n  - FireWire sound drivers;\n  - AudioScience HPI driver;\n  - HD-audio driver;\n  - MediaTek ASoC drivers;\n  - QCOM ASoC drivers;\n  - SoC audio core drivers;\n  - STMicroelectronics SoC drivers;\n  - USB sound devices;\n(CVE-2024-49996, CVE-2024-56693, CVE-2024-49928, CVE-2024-47728,\nCVE-2024-50218, CVE-2024-50197, CVE-2024-50084, CVE-2024-56698,\nCVE-2024-56623, CVE-2024-50203, CVE-2024-56786, CVE-2024-53198,\nCVE-2024-49939, CVE-2024-49852, CVE-2024-49920, CVE-2024-53117,\nCVE-2024-50023, CVE-2024-56581, CVE-2024-49954, CVE-2024-56658,\nCVE-2024-56688, CVE-2024-56574, CVE-2024-56690, CVE-2024-53158,\nCVE-2024-56777, CVE-2024-56582, CVE-2024-56629, CVE-2024-49997,\nCVE-2024-50041, CVE-2024-53052, CVE-2024-50126, CVE-2024-56726,\nCVE-2024-50007, CVE-2024-47712, CVE-2024-50225, CVE-2024-50269,\nCVE-2024-50200, CVE-2024-53099, CVE-2024-50083, CVE-2024-53162,\nCVE-2024-57876, CVE-2024-50180, CVE-2024-56678, CVE-2024-50179,\nCVE-2024-56776, CVE-2024-53151, CVE-2024-56631, CVE-2024-50160,\nCVE-2024-50302, CVE-2024-53126, CVE-2024-50151, CVE-2024-49917,\nCVE-2024-49899, CVE-2024-49927, CVE-2024-48875, CVE-2024-50298,\nCVE-2024-53148, CVE-2024-53160, CVE-2024-50187, CVE-2024-50072,\nCVE-2024-56756, CVE-2024-56625, CVE-2024-44955, CVE-2024-47671,\nCVE-2024-47141, CVE-2024-50047, CVE-2024-50048, CVE-2024-50245,\nCVE-2024-50096, CVE-2024-56602, CVE-2024-53232, CVE-2024-50284,\nCVE-2024-53129, CVE-2024-56724, CVE-2024-56632, CVE-2024-49924,\nCVE-2024-47756, CVE-2024-53226, CVE-2024-50189, CVE-2024-56573,\nCVE-2024-50257, CVE-2024-50300, CVE-2024-47673, CVE-2024-50152,\nCVE-2024-53215, CVE-2024-50295, CVE-2024-50111, CVE-2024-49865,\nCVE-2024-47691, CVE-2024-56649, CVE-2024-56567, CVE-2024-53061,\nCVE-2024-50153, CVE-2024-53091, CVE-2024-56692, CVE-2024-41932,\nCVE-2024-56650, CVE-2024-56645, CVE-2024-47670, CVE-2024-53130,\nCVE-2024-50066, CVE-2024-50020, CVE-2024-50154, CVE-2024-49998,\nCVE-2024-50290, CVE-2024-56594, CVE-2024-56627, CVE-2024-49882,\nCVE-2024-50220, CVE-2024-49914, CVE-2024-50019, CVE-2024-53213,\nCVE-2024-50015, CVE-2024-53172, CVE-2024-50198, CVE-2024-53051,\nCVE-2024-50280, CVE-2024-53187, CVE-2024-50136, CVE-2024-47672,\nCVE-2024-56606, CVE-2024-47699, CVE-2024-56780, CVE-2024-56672,\nCVE-2024-56637, CVE-2024-49946, CVE-2024-56752, CVE-2024-50199,\nCVE-2024-53119, CVE-2024-53084, CVE-2024-50076, CVE-2024-49938,\nCVE-2024-50237, CVE-2024-56779, CVE-2024-50108, CVE-2024-50162,\nCVE-2024-49936, CVE-2024-41935, CVE-2024-53046, CVE-2024-56572,\nCVE-2024-53107, CVE-2024-53150, CVE-2024-56539, CVE-2024-49949,\nCVE-2024-41014, CVE-2024-53217, CVE-2024-49977, CVE-2025-21702,\nCVE-2024-50267, CVE-2024-50138, CVE-2024-50229, CVE-2024-56586,\nCVE-2024-50057, CVE-2024-50070, CVE-2024-49898, CVE-2024-50085,\nCVE-2024-56746, CVE-2024-53106, CVE-2024-47695, CVE-2024-50009,\nCVE-2024-50103, CVE-2024-47693, CVE-2024-53135, CVE-2024-53127,\nCVE-2024-50067, CVE-2024-57850, CVE-2024-56615, CVE-2024-50167,\nCVE-2024-50042, CVE-2024-56546, CVE-2024-47749, CVE-2024-47705,\nCVE-2024-47747, CVE-2024-56570, CVE-2024-56604, CVE-2024-53112,\nCVE-2024-49988, CVE-2024-56597, CVE-2024-50268, CVE-2024-53121,\nCVE-2024-56635, CVE-2024-50002, CVE-2024-50127, CVE-2024-56603,\nCVE-2024-56531, CVE-2024-49890, CVE-2024-53157, CVE-2024-50246,\nCVE-2024-56562, CVE-2024-56722, CVE-2024-49912, CVE-2024-56774,\nCVE-2024-49893, CVE-2024-56593, CVE-2024-53131, CVE-2024-57798,\nCVE-2024-50275, CVE-2024-50075, CVE-2024-53174, CVE-2024-53087,\nCVE-2024-50155, CVE-2024-47696, CVE-2024-53155, CVE-2024-50201,\nCVE-2024-53134, CVE-2024-49922, CVE-2024-53138, CVE-2024-47711,\nCVE-2024-47742, CVE-2024-53043, CVE-2024-48881, CVE-2024-53203,\nCVE-2024-53053, CVE-2024-56589, CVE-2024-56679, CVE-2024-49892,\nCVE-2024-56677, CVE-2024-53144, CVE-2024-50107, CVE-2024-56583,\nCVE-2025-21701, CVE-2024-49911, CVE-2024-50244, CVE-2024-49969,\nCVE-2024-50098, CVE-2024-50166, CVE-2024-47809, CVE-2024-56781,\nCVE-2024-49894, CVE-2025-21700, CVE-2024-49930, CVE-2024-56548,\nCVE-2024-50134, CVE-2024-53194, CVE-2024-50285, CVE-2024-42122,\nCVE-2024-53171, CVE-2024-53120, CVE-2024-50279, CVE-2024-57838,\nCVE-2024-50082, CVE-2024-50168, CVE-2024-53175, CVE-2024-47710,\nCVE-2024-49972, CVE-2024-56727, CVE-2024-49919, CVE-2024-53066,\nCVE-2024-56708, CVE-2024-53142, CVE-2024-49896, CVE-2024-49950,\nCVE-2024-53114, CVE-2024-47737, CVE-2024-56721, CVE-2024-50030,\nCVE-2024-50063, CVE-2024-56704, CVE-2024-56694, CVE-2024-49937,\nCVE-2024-56596, CVE-2024-49855, CVE-2024-53231, CVE-2024-50259,\nCVE-2024-50163, CVE-2024-50263, CVE-2024-56579, CVE-2024-50148,\nCVE-2024-50252, CVE-2024-56775, CVE-2024-53195, CVE-2024-56771,\nCVE-2024-56765, CVE-2024-50192, CVE-2024-56705, CVE-2024-56566,\nCVE-2024-49851, CVE-2024-56575, CVE-2024-53222, CVE-2024-50014,\nCVE-2024-49891, CVE-2024-53128, CVE-2024-49921, CVE-2024-50024,\nCVE-2024-56703, CVE-2024-56787, CVE-2024-56723, CVE-2024-56687,\nCVE-2024-47718, CVE-2024-49902, CVE-2024-49963, CVE-2024-56691,\nCVE-2024-53173, CVE-2024-56599, CVE-2024-50080, CVE-2024-47704,\nCVE-2024-49934, CVE-2024-56707, CVE-2024-49958, CVE-2024-49888,\nCVE-2024-53095, CVE-2024-53089, CVE-2024-49935, CVE-2024-50022,\nCVE-2024-47748, CVE-2024-56634, CVE-2024-53090, CVE-2024-50242,\nCVE-2024-53085, CVE-2024-50073, CVE-2024-50068, CVE-2024-49877,\nCVE-2024-56642, CVE-2024-53067, CVE-2024-50118, CVE-2024-50061,\nCVE-2024-49948, CVE-2024-53100, CVE-2024-50194, CVE-2024-50116,\nCVE-2024-48873, CVE-2024-53180, CVE-2024-56663, CVE-2024-50303,\nCVE-2024-50250, CVE-2024-50045, CVE-2024-50296, CVE-2024-49961,\nCVE-2024-56549, CVE-2024-50027, CVE-2024-53227, CVE-2024-50292,\nCVE-2024-49900, CVE-2024-50074, CVE-2024-53115, CVE-2024-56747,\nCVE-2024-50078, CVE-2024-56772, CVE-2024-53141, CVE-2024-50301,\nCVE-2024-53079, CVE-2024-50255, CVE-2024-56565, CVE-2024-53165,\nCVE-2024-52332, CVE-2024-53140, CVE-2024-50286, CVE-2024-53088,\nCVE-2024-53139, CVE-2024-49881, CVE-2024-49859, CVE-2024-50247,\nCVE-2024-50278, CVE-2024-50124, CVE-2024-47709, CVE-2024-50128,\nCVE-2024-49962, CVE-2024-50258, CVE-2024-56532, CVE-2024-47684,\nCVE-2024-56633, CVE-2024-53210, CVE-2024-49867, CVE-2024-50056,\nCVE-2024-50137, CVE-2024-47730, CVE-2024-49960, CVE-2024-50060,\nCVE-2024-49925, CVE-2024-50195, CVE-2024-50031, CVE-2024-50099,\nCVE-2024-49863, CVE-2024-49992, CVE-2024-53083, CVE-2024-56751,\nCVE-2024-50141, CVE-2024-47701, CVE-2024-53122, CVE-2024-56576,\nCVE-2024-47689, CVE-2024-50121, CVE-2024-50147, CVE-2024-50226,\nCVE-2024-50239, CVE-2024-56578, CVE-2024-50062, CVE-2024-50033,\nCVE-2024-49982, CVE-2024-56545, CVE-2024-53118, CVE-2024-50231,\nCVE-2024-50125, CVE-2024-50191, CVE-2024-49875, CVE-2024-47794,\nCVE-2024-49983, CVE-2024-56595, CVE-2024-50224, CVE-2024-47690,\nCVE-2024-50272, CVE-2024-49901, CVE-2024-56538, CVE-2024-50010,\nCVE-2024-49959, CVE-2024-53154, CVE-2024-53221, CVE-2024-49886,\nCVE-2024-50145, CVE-2024-49884, CVE-2024-50028, CVE-2024-50232,\nCVE-2024-53208, CVE-2024-50000, CVE-2024-56728, CVE-2024-50304,\nCVE-2024-49989, CVE-2024-47739, CVE-2024-56550, CVE-2024-50055,\nCVE-2024-56590, CVE-2024-53055, CVE-2024-50270, CVE-2024-53164,\nCVE-2024-49856, CVE-2024-57849, CVE-2024-47697, CVE-2024-43098,\nCVE-2024-50170, CVE-2024-53196, CVE-2024-50251, CVE-2024-56533,\nCVE-2024-41016, CVE-2024-53105, CVE-2024-53230, CVE-2024-50164,\nCVE-2024-50101, CVE-2024-56607, CVE-2024-50186, CVE-2024-50105,\nCVE-2024-47679, CVE-2024-48876, CVE-2024-50243, CVE-2024-47720,\nCVE-2024-53239, CVE-2024-53062, CVE-2024-50021, CVE-2024-56614,\nCVE-2024-53224, CVE-2024-56619, CVE-2024-53072, CVE-2024-53223,\nCVE-2024-50039, CVE-2024-49981, CVE-2024-50230, CVE-2024-47143,\nCVE-2024-53082, CVE-2024-50216, CVE-2024-47713, CVE-2024-56720,\nCVE-2024-56543, CVE-2024-53094, CVE-2024-53111, CVE-2024-50036,\nCVE-2024-50065, CVE-2024-57874, CVE-2024-56689, CVE-2024-53183,\nCVE-2024-53108, CVE-2024-56643, CVE-2024-49868, CVE-2024-56611,\nCVE-2024-50185, CVE-2024-50223, CVE-2024-50193, CVE-2024-56616,\nCVE-2024-50265, CVE-2024-56701, CVE-2024-50112, CVE-2024-50297,\nCVE-2024-50207, CVE-2024-56558, CVE-2024-56782, CVE-2024-53081,\nCVE-2024-50044, CVE-2024-50040, CVE-2024-49991, CVE-2024-50013,\nCVE-2024-53170, CVE-2024-56540, CVE-2024-47723, CVE-2024-49913,\nCVE-2024-53169, CVE-2024-49974, CVE-2024-50256, CVE-2024-49858,\nCVE-2024-56609, CVE-2024-50282, CVE-2024-53168, CVE-2024-50182,\nCVE-2024-49973, CVE-2024-56638, CVE-2024-56683, CVE-2024-50059,\nCVE-2024-56648, CVE-2024-45828, CVE-2024-56610, CVE-2024-47740,\nCVE-2024-47692, CVE-2024-50026, CVE-2024-50117, CVE-2024-50221,\nCVE-2024-49931, CVE-2024-49994, CVE-2024-50184, CVE-2024-50171,\nCVE-2024-50261, CVE-2024-50283, CVE-2024-50233, CVE-2024-53184,\nCVE-2024-53220, CVE-2024-53191, CVE-2024-53190, CVE-2024-56592,\nCVE-2024-47703, CVE-2024-53048, CVE-2024-49955, CVE-2024-50150,\nCVE-2024-50208, CVE-2024-56577, CVE-2024-50159, CVE-2024-50131,\nCVE-2024-56755, CVE-2024-50172, CVE-2024-53146, CVE-2024-53161,\nCVE-2024-50222, CVE-2024-49879, CVE-2024-50146, CVE-2024-53063,\nCVE-2024-49889, CVE-2024-50287, CVE-2024-56647, CVE-2024-56613,\nCVE-2024-50017, CVE-2024-56551, CVE-2024-53145, CVE-2024-53166,\nCVE-2024-56622, CVE-2025-21993, CVE-2024-50133, CVE-2024-53234,\nCVE-2024-53133, CVE-2024-47735, CVE-2024-49861, CVE-2024-50143,\nCVE-2024-50169, CVE-2024-50046, CVE-2024-50069, CVE-2024-56742,\nCVE-2024-50104, CVE-2024-56636, CVE-2024-56745, CVE-2024-56630,\nCVE-2024-50276, CVE-2024-53228, CVE-2024-49945, CVE-2025-21756,\nCVE-2024-50142, CVE-2024-56729, CVE-2024-49569, CVE-2024-49952,\nCVE-2024-50006, CVE-2024-50273, CVE-2024-49906, CVE-2024-53058,\nCVE-2024-49895, CVE-2024-50240, CVE-2024-49987, CVE-2024-53233,\nCVE-2024-53086, CVE-2024-50110, CVE-2024-50064, CVE-2024-49878,\nCVE-2024-56644, CVE-2024-56605, CVE-2024-47698, CVE-2024-53147,\nCVE-2024-47745, CVE-2024-56685, CVE-2024-50016, CVE-2024-49871,\nCVE-2024-47757, CVE-2024-53103, CVE-2024-56580, CVE-2024-49883,\nCVE-2024-53163, CVE-2024-53110, CVE-2024-50058, CVE-2024-56640,\nCVE-2024-53101, CVE-2024-53156, CVE-2022-49034, CVE-2024-53109,\nCVE-2024-49978, CVE-2024-50235, CVE-2024-53680, CVE-2024-50299,\nCVE-2024-53177, CVE-2024-50008, CVE-2024-56744, CVE-2025-21831,\nCVE-2024-50038, CVE-2024-50271, CVE-2024-53178, CVE-2024-50012,\nCVE-2024-53188, CVE-2024-49860, CVE-2024-53237, CVE-2024-50188,\nCVE-2024-49880, CVE-2024-50077, CVE-2024-49968, CVE-2024-50236,\nCVE-2024-50206, CVE-2024-53197, CVE-2024-56587, CVE-2024-53236,\nCVE-2024-50139, CVE-2024-50120, CVE-2024-56681, CVE-2024-53059,\nCVE-2024-53113, CVE-2024-50209, CVE-2024-49957, CVE-2024-49944,\nCVE-2024-50087, CVE-2024-56754, CVE-2024-49903, CVE-2024-56600,\nCVE-2024-47706, CVE-2024-49907, CVE-2024-53202, CVE-2024-50215,\nCVE-2024-47734, CVE-2024-56785, CVE-2024-53229, CVE-2024-53050,\nCVE-2024-50051, CVE-2024-53209, CVE-2024-56739, CVE-2024-50262,\nCVE-2024-50088, CVE-2024-56621, CVE-2024-49929, CVE-2024-57843,\nCVE-2024-56569, CVE-2024-50140, CVE-2024-50135, CVE-2024-57872,\nCVE-2024-49866, CVE-2024-53214, CVE-2024-50090, CVE-2024-49985,\nCVE-2024-56608, CVE-2024-56598, CVE-2024-49915, CVE-2024-53104,\nCVE-2024-50035, CVE-2024-53047, CVE-2024-53176, CVE-2024-56700,\nCVE-2024-49975, CVE-2024-53200, CVE-2024-50274, CVE-2024-56748,\nCVE-2024-56601, CVE-2024-50289, CVE-2024-50086, CVE-2024-53044,\nCVE-2024-50029, CVE-2024-49909, CVE-2024-47738, CVE-2024-47726,\nCVE-2024-56568, CVE-2024-53181, CVE-2024-53218, CVE-2024-56725,\nCVE-2024-56778, CVE-2024-50115, CVE-2024-50288, CVE-2024-50291,\nCVE-2024-50049, CVE-2024-56773, CVE-2024-50001, CVE-2024-49933,\nCVE-2024-50211, CVE-2024-50095, CVE-2024-56651, CVE-2024-50238,\nCVE-2024-47707, CVE-2024-50205, CVE-2024-50093, CVE-2024-50183,\nCVE-2024-56588, CVE-2024-49965, CVE-2024-56584, CVE-2024-53096,\nCVE-2024-50248, CVE-2024-50234, CVE-2024-49926, CVE-2024-49923,\nCVE-2024-49918, CVE-2024-50130, CVE-2024-53093, CVE-2024-56626,\nCVE-2024-50156, CVE-2024-56557, CVE-2024-50196, CVE-2024-56620,\nCVE-2024-49870, CVE-2024-50294, CVE-2024-53042, CVE-2024-53076,\nCVE-2024-49905, CVE-2024-53045, CVE-2024-50202, CVE-2024-56641,\nCVE-2024-53219, CVE-2024-50158, CVE-2024-50025, CVE-2024-47685,\nCVE-2024-49966, CVE-2024-53123, CVE-2024-53068, CVE-2024-47678)\n","status":"published","published":"2025-04-28T15:04:12Z","modified":"2026-11-03T21:17:55.939905598Z","updated_at":"2026-11-03T21:43:54.166508Z"},{"id":"USN-7523-1","title":"linux-raspi-realtime vulnerabilities","description":"Several security issues were discovered in the Linux kernel.\nAn attacker could possibly use these to compromise the system.\nThis update corrects flaws in the following subsystems:\n  - ARM64 architecture;\n  - MIPS architecture;\n  - PowerPC architecture;\n  - RISC-V architecture;\n  - S390 architecture;\n  - SuperH RISC architecture;\n  - User-Mode Linux (UML);\n  - x86 architecture;\n  - Block layer subsystem;\n  - Cryptographic API;\n  - Compute Acceleration Framework;\n  - ACPI drivers;\n  - Drivers core;\n  - RAM backed block device driver;\n  - Ublk userspace block driver;\n  - Virtio block driver;\n  - Compressed RAM block device driver;\n  - Bluetooth drivers;\n  - TPM device driver;\n  - Clock framework and drivers;\n  - Data acquisition framework and drivers;\n  - CPU frequency scaling framework;\n  - Hardware crypto device drivers;\n  - CXL (Compute Express Link) drivers;\n  - DAX dirext access to differentiated memory framework;\n  - DMA engine subsystem;\n  - EDAC drivers;\n  - ARM SCMI message protocol;\n  - ARM SCPI message protocol;\n  - EFI core;\n  - iSCSI Boot Firmware Table Attributes driver;\n  - GPIO subsystem;\n  - GPU drivers;\n  - HID subsystem;\n  - Microsoft Hyper-V drivers;\n  - Hardware monitoring drivers;\n  - I3C subsystem;\n  - IIO ADC drivers;\n  - IIO subsystem;\n  - InfiniBand drivers;\n  - IOMMU subsystem;\n  - IRQ chip drivers;\n  - LED subsystem;\n  - Multiple devices driver;\n  - Media drivers;\n  - Multifunction device drivers;\n  - Microchip PCI driver;\n  - MMC subsystem;\n  - MTD block device drivers;\n  - Network drivers;\n  - Mellanox network drivers;\n  - STMicroelectronics network drivers;\n  - NTB driver;\n  - Virtio pmem driver;\n  - NVME drivers;\n  - Parport drivers;\n  - PCI subsystem;\n  - PHY drivers;\n  - Pin controllers subsystem;\n  - x86 platform drivers;\n  - i.MX PM domains;\n  - Power supply drivers;\n  - Voltage and Current Regulator drivers;\n  - StarFive reset controller drivers;\n  - Real Time Clock drivers;\n  - SCSI subsystem;\n  - SuperH / SH-Mobile drivers;\n  - i.MX SoC drivers;\n  - QCOM SoC drivers;\n  - Xilinx SoC drivers;\n  - SPI subsystem;\n  - Direct Digital Synthesis drivers;\n  - Media staging drivers;\n  - TCM subsystem;\n  - Thermal drivers;\n  - TTY drivers;\n  - UFS subsystem;\n  - DesignWare USB3 driver;\n  - USB Gadget drivers;\n  - USB Host Controller drivers;\n  - USB Dual Role (OTG-ready) Controller drivers;\n  - USB Serial drivers;\n  - USB Type-C support driver;\n  - USB Type-C Port Controller Manager driver;\n  - TI TPS6598x USB Power Delivery controller driver;\n  - USB Type-C Connector System Software Interface driver;\n  - vDPA drivers;\n  - VFIO drivers;\n  - Framebuffer layer;\n  - TDX Guest driver;\n  - Xen hypervisor drivers;\n  - AFS file system;\n  - BTRFS file system;\n  - File systems infrastructure;\n  - Ceph distributed file system;\n  - EROFS file system;\n  - Ext4 file system;\n  - F2FS 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  - NTFS3 file system;\n  - Overlay file system;\n  - Proc file system;\n  - Diskquota system;\n  - SMB network file system;\n  - UBI file system;\n  - DRM display driver;\n  - BPF subsystem;\n  - VLANs driver;\n  - Kernel Samepage Merging mechanism;\n  - Memory management;\n  - Network file system (NFS) superblock;\n  - Kernel stack handling interfaces;\n  - StackDepot library;\n  - Task handling mechanism;\n  - userfaultfd() syscall;\n  - Bluetooth subsystem;\n  - IP tunnels definitions;\n  - LAPB network protocol;\n  - Network namespace;\n  - Netfilter;\n  - Network traffic control;\n  - Network sockets;\n  - Tracing infrastructure;\n  - User-space API (UAPI);\n  - Kernel init infrastructure;\n  - io_uring subsystem;\n  - IPC subsystem;\n  - Control group (cgroup);\n  - DMA mapping infrastructure;\n  - Kernel fork() syscall;\n  - KCSAN framework;\n  - Kernel thread helper (kthread);\n  - RCU subsystem;\n  - Arbitrary resource management;\n  - Scheduler infrastructure;\n  - Signal handling mechanism;\n  - Timer subsystem;\n  - Workqueue subsystem;\n  - Vector I/O iterator library;\n  - KUnit library;\n  - Maple Tree data structure library;\n  - 9P file system network protocol;\n  - Ethernet bridge;\n  - CAN network layer;\n  - Networking core;\n  - DCCP (Datagram Congestion Control Protocol);\n  - Ethtool driver;\n  - HSR network protocol;\n  - IEEE802154.4 network protocol;\n  - IPv4 networking;\n  - IPv6 networking;\n  - IUCV driver;\n  - MAC80211 subsystem;\n  - Multipath TCP;\n  - Netlink;\n  - NET/ROM layer;\n  - Packet sockets;\n  - RDS protocol;\n  - RxRPC session sockets;\n  - SCTP protocol;\n  - SMC sockets;\n  - Sun RPC protocol;\n  - TIPC protocol;\n  - Unix domain sockets;\n  - VMware vSockets driver;\n  - Wireless networking;\n  - eXpress Data Path;\n  - XFRM subsystem;\n  - Integrity Measurement Architecture(IMA) framework;\n  - Key management;\n  - SELinux security module;\n  - ALSA framework;\n  - FireWire sound drivers;\n  - HD-audio driver;\n  - MediaTek ASoC drivers;\n  - QCOM ASoC drivers;\n  - SoC audio core drivers;\n  - STMicroelectronics SoC drivers;\n  - USB sound devices;\n(CVE-2024-56566, CVE-2024-56631, CVE-2025-21756, CVE-2024-57841,\nCVE-2024-50270, CVE-2024-50104, CVE-2024-50143, CVE-2024-56756,\nCVE-2024-50295, CVE-2024-48873, CVE-2024-53229, CVE-2024-50051,\nCVE-2024-50125, CVE-2024-56761, CVE-2024-50223, CVE-2024-53687,\nCVE-2024-53094, CVE-2024-53131, CVE-2024-57933, CVE-2024-57884,\nCVE-2024-57917, CVE-2024-53210, CVE-2024-50245, CVE-2024-56679,\nCVE-2024-50258, CVE-2024-57902, CVE-2024-50236, CVE-2024-56607,\nCVE-2024-50209, CVE-2024-50184, CVE-2024-50127, CVE-2024-50010,\nCVE-2024-50185, CVE-2024-57900, CVE-2024-56739, CVE-2024-56643,\nCVE-2024-56675, CVE-2024-56689, CVE-2024-50135, CVE-2024-56688,\nCVE-2024-50153, CVE-2025-21635, CVE-2025-21632, CVE-2024-50072,\nCVE-2025-21646, CVE-2024-56727, CVE-2024-53058, CVE-2024-53107,\nCVE-2024-53166, CVE-2024-50019, CVE-2024-50242, CVE-2024-56755,\nCVE-2024-50301, CVE-2024-57801, CVE-2024-56716, CVE-2024-50023,\nCVE-2024-50288, CVE-2024-50078, CVE-2024-56572, CVE-2024-53158,\nCVE-2024-50075, CVE-2024-57912, CVE-2024-56759, CVE-2024-53155,\nCVE-2024-56584, CVE-2024-56672, CVE-2024-56590, CVE-2024-56658,\nCVE-2024-50235, CVE-2024-53160, CVE-2024-56622, CVE-2024-50130,\nCVE-2024-50265, CVE-2024-56579, CVE-2024-50292, CVE-2024-56728,\nCVE-2024-56543, CVE-2024-56722, CVE-2024-53197, CVE-2025-21645,\nCVE-2024-50138, CVE-2024-45828, CVE-2024-50208, CVE-2024-56724,\nCVE-2024-50304, CVE-2024-50195, CVE-2024-49571, CVE-2024-50263,\nCVE-2024-55881, CVE-2024-50220, CVE-2024-50044, CVE-2024-53237,\nCVE-2024-50278, CVE-2024-56557, CVE-2024-50068, CVE-2024-56574,\nCVE-2024-50180, CVE-2024-50065, CVE-2025-21642, CVE-2024-56565,\nCVE-2024-50189, CVE-2024-53228, CVE-2024-56752, CVE-2024-50169,\nCVE-2024-53198, CVE-2024-56532, CVE-2025-21659, CVE-2024-53223,\nCVE-2024-50084, CVE-2024-56582, CVE-2024-56632, CVE-2024-56709,\nCVE-2024-50134, CVE-2024-57945, CVE-2024-56546, CVE-2024-50056,\nCVE-2024-53059, CVE-2024-53171, CVE-2024-50080, CVE-2024-49899,\nCVE-2024-50090, CVE-2024-53184, CVE-2024-50131, CVE-2024-57926,\nCVE-2024-50225, CVE-2024-47809, CVE-2024-53180, CVE-2024-56372,\nCVE-2024-50137, CVE-2024-50192, CVE-2024-56642, CVE-2025-21637,\nCVE-2024-53219, CVE-2024-56650, CVE-2024-53090, CVE-2024-53148,\nCVE-2024-56785, CVE-2024-50230, CVE-2024-50275, CVE-2024-47141,\nCVE-2024-50022, CVE-2024-53142, CVE-2024-50059, CVE-2024-56765,\nCVE-2024-53046, CVE-2024-58087, CVE-2025-21664, CVE-2025-21658,\nCVE-2024-56569, CVE-2024-50110, CVE-2024-53161, CVE-2024-53150,\nCVE-2024-53140, CVE-2024-50069, CVE-2024-56594, CVE-2024-53181,\nCVE-2024-53178, CVE-2024-56652, CVE-2024-56708, CVE-2024-53174,\nCVE-2024-53072, CVE-2024-50290, CVE-2024-53162, CVE-2024-50029,\nCVE-2024-53179, CVE-2024-53079, CVE-2024-57906, CVE-2024-50035,\nCVE-2024-50224, CVE-2025-21649, CVE-2024-50163, CVE-2024-57882,\nCVE-2024-50024, CVE-2024-56550, CVE-2024-53690, CVE-2024-50203,\nCVE-2024-53195, CVE-2024-50118, CVE-2024-53175, CVE-2024-57908,\nCVE-2025-21701, CVE-2024-47736, CVE-2024-53067, CVE-2024-53200,\nCVE-2024-50032, CVE-2024-50282, CVE-2024-50162, CVE-2024-53118,\nCVE-2024-56636, CVE-2024-56629, CVE-2024-50030, CVE-2024-56595,\nCVE-2024-56601, CVE-2024-57904, CVE-2024-53115, CVE-2024-50077,\nCVE-2024-56654, CVE-2024-50199, CVE-2024-56782, CVE-2024-50151,\nCVE-2024-50182, CVE-2024-53052, CVE-2024-53151, CVE-2024-57938,\nCVE-2024-53084, CVE-2024-50296, CVE-2024-53217, CVE-2024-57892,\nCVE-2024-50287, CVE-2024-53110, CVE-2024-56763, CVE-2024-50027,\nCVE-2024-50261, CVE-2024-50112, CVE-2024-56533, CVE-2024-56704,\nCVE-2024-47726, CVE-2024-50238, CVE-2024-57876, CVE-2024-50207,\nCVE-2024-50116, CVE-2024-50155, CVE-2024-53086, CVE-2024-50291,\nCVE-2025-21631, CVE-2024-56538, CVE-2024-56720, CVE-2024-53123,\nCVE-2024-58099, CVE-2024-56597, CVE-2024-53168, CVE-2024-57879,\nCVE-2022-49034, CVE-2024-56549, CVE-2024-41014, CVE-2024-53091,\nCVE-2024-56677, CVE-2024-53156, CVE-2024-50158, CVE-2024-50251,\nCVE-2024-56641, CVE-2024-56718, CVE-2024-57901, CVE-2024-56606,\nCVE-2024-50268, CVE-2024-48875, CVE-2024-50167, CVE-2024-50028,\nCVE-2024-50256, CVE-2024-50283, CVE-2024-53133, CVE-2024-50302,\nCVE-2024-56721, CVE-2024-53177, CVE-2024-57798, CVE-2024-53126,\nCVE-2024-56638, CVE-2024-50285, CVE-2024-53076, CVE-2024-53146,\nCVE-2024-56698, CVE-2025-21700, CVE-2024-56619, CVE-2024-50115,\nCVE-2024-53190, CVE-2024-54460, CVE-2024-50073, CVE-2024-56771,\nCVE-2024-56637, CVE-2024-50061, CVE-2024-55639, CVE-2024-56651,\nCVE-2024-50064, CVE-2024-53044, CVE-2024-53096, CVE-2024-56613,\nCVE-2024-56769, CVE-2024-57910, CVE-2024-41013, CVE-2024-50186,\nCVE-2024-50159, CVE-2024-56600, CVE-2024-56787, CVE-2024-57929,\nCVE-2024-56640, CVE-2025-21662, CVE-2024-53099, CVE-2024-56570,\nCVE-2024-53100, CVE-2024-50101, CVE-2024-50160, CVE-2024-50273,\nCVE-2024-47711, CVE-2024-50191, CVE-2024-56786, CVE-2024-50107,\nCVE-2024-53236, CVE-2024-56548, CVE-2024-56562, CVE-2024-50229,\nCVE-2024-56647, CVE-2024-53139, CVE-2024-48876, CVE-2024-57872,\nCVE-2024-53063, CVE-2024-53226, CVE-2024-56758, CVE-2024-50086,\nCVE-2024-53209, CVE-2024-50096, CVE-2024-56660, CVE-2024-57893,\nCVE-2024-53083, CVE-2024-57916, CVE-2024-50205, CVE-2024-50200,\nCVE-2024-53108, CVE-2024-50033, CVE-2024-50276, CVE-2024-56621,\nCVE-2024-56725, CVE-2024-56558, CVE-2024-57931, CVE-2024-50145,\nCVE-2024-56616, CVE-2024-53685, CVE-2024-53129, CVE-2025-21650,\nCVE-2025-21654, CVE-2024-50171, CVE-2024-56599, CVE-2024-50046,\nCVE-2024-56701, CVE-2024-47408, CVE-2025-21636, CVE-2024-50231,\nCVE-2024-50152, CVE-2024-50206, CVE-2024-50009, CVE-2024-53130,\nCVE-2024-57793, CVE-2024-57791, CVE-2024-50262, CVE-2024-56586,\nCVE-2024-57895, CVE-2024-57899, CVE-2024-56608, CVE-2024-50197,\nCVE-2024-56774, CVE-2024-53224, CVE-2024-53231, CVE-2024-50237,\nCVE-2024-50139, CVE-2024-50222, CVE-2024-50039, CVE-2024-53101,\nCVE-2024-56776, CVE-2024-56625, CVE-2024-53188, CVE-2024-50269,\nCVE-2024-50055, CVE-2024-50216, CVE-2024-56615, CVE-2024-56648,\nCVE-2024-50048, CVE-2024-57925, CVE-2024-50193, CVE-2024-56754,\nCVE-2025-21647, CVE-2024-50105, CVE-2024-49893, CVE-2024-53128,\nCVE-2024-49568, CVE-2024-56539, CVE-2024-50117, CVE-2024-53081,\nCVE-2024-50148, CVE-2024-56685, CVE-2024-50226, CVE-2024-56576,\nCVE-2024-56627, CVE-2024-50289, CVE-2025-21653, CVE-2024-53082,\nCVE-2024-56581, CVE-2024-53227, CVE-2024-56691, CVE-2024-56780,\nCVE-2024-50095, CVE-2024-50136, CVE-2024-50201, CVE-2024-55916,\nCVE-2024-56583, CVE-2024-53135, CVE-2024-53106, CVE-2024-57887,\nCVE-2024-57792, CVE-2024-48881, CVE-2024-56645, CVE-2024-53157,\nCVE-2024-53045, CVE-2024-53170, CVE-2024-50082, CVE-2024-56531,\nCVE-2024-53183, CVE-2024-53191, CVE-2024-53163, CVE-2025-21656,\nCVE-2024-50274, CVE-2025-21639, CVE-2025-21663, CVE-2024-50183,\nCVE-2024-50020, CVE-2024-56568, CVE-2024-56781, CVE-2024-50057,\nCVE-2024-56681, CVE-2024-50299, CVE-2024-53233, CVE-2024-53121,\nCVE-2024-53214, CVE-2024-56700, CVE-2024-50247, CVE-2024-56778,\nCVE-2024-50067, CVE-2024-56662, CVE-2024-56635, CVE-2024-53112,\nCVE-2024-56729, CVE-2024-56589, CVE-2024-53093, CVE-2024-50248,\nCVE-2024-53220, CVE-2025-21971, CVE-2024-52332, CVE-2024-38608,\nCVE-2024-50062, CVE-2024-53218, CVE-2024-56630, CVE-2024-49569,\nCVE-2024-56745, CVE-2024-56715, CVE-2024-56633, CVE-2024-53208,\nCVE-2024-56770, CVE-2024-50154, CVE-2024-56705, CVE-2024-50120,\nCVE-2024-57939, CVE-2024-57843, CVE-2024-56609, CVE-2024-56772,\nCVE-2024-50211, CVE-2024-57804, CVE-2024-57889, CVE-2024-56603,\nCVE-2024-53087, CVE-2024-53125, CVE-2024-53061, CVE-2025-21652,\nCVE-2024-50255, CVE-2024-56690, CVE-2025-21702, CVE-2024-53169,\nCVE-2024-50240, CVE-2024-56683, CVE-2024-49972, CVE-2025-21655,\nCVE-2024-57874, CVE-2024-53120, CVE-2024-57907, CVE-2024-56626,\nCVE-2024-56726, CVE-2024-56773, CVE-2024-49914, CVE-2024-42122,\nCVE-2024-53194, CVE-2024-49920, CVE-2024-56545, CVE-2024-56575,\nCVE-2024-56775, CVE-2024-53134, CVE-2024-56717, CVE-2024-53105,\nCVE-2024-57897, CVE-2024-50124, CVE-2024-50239, CVE-2024-50036,\nCVE-2024-50234, CVE-2025-21651, CVE-2024-56767, CVE-2024-53165,\nCVE-2024-53680, CVE-2024-41935, CVE-2024-50150, CVE-2024-53043,\nCVE-2024-56659, CVE-2024-50243, CVE-2024-56567, CVE-2024-50141,\nCVE-2024-50049, CVE-2024-53222, CVE-2024-53122, CVE-2024-50257,\nCVE-2024-50147, CVE-2024-53176, CVE-2024-53234, CVE-2024-53187,\nCVE-2024-50280, CVE-2024-50140, CVE-2024-57911, CVE-2024-50060,\nCVE-2024-56598, CVE-2024-50246, CVE-2024-53047, CVE-2024-56577,\nCVE-2024-57802, CVE-2024-53050, CVE-2024-50088, CVE-2024-56751,\nCVE-2024-56611, CVE-2024-53068, CVE-2025-21643, CVE-2024-50038,\nCVE-2024-36476, CVE-2024-56707, CVE-2024-50040, CVE-2024-53088,\nCVE-2024-50284, CVE-2024-53127, CVE-2024-50298, CVE-2024-56593,\nCVE-2024-57898, CVE-2024-57903, CVE-2024-56703, CVE-2024-56746,\nCVE-2024-56663, CVE-2024-53138, CVE-2024-56744, CVE-2024-50042,\nCVE-2024-57940, CVE-2024-56747, CVE-2024-56623, CVE-2024-56777,\nCVE-2024-41932, CVE-2024-47143, CVE-2024-50098, CVE-2024-53147,\nCVE-2024-53173, CVE-2024-50249, CVE-2024-49921, CVE-2024-56783,\nCVE-2024-50294, CVE-2024-53062, CVE-2024-57946, CVE-2024-56710,\nCVE-2025-21640, CVE-2024-53042, CVE-2024-56649, CVE-2024-50233,\nCVE-2024-50121, CVE-2024-53051, CVE-2024-57932, CVE-2025-21634,\nCVE-2024-56580, CVE-2024-56687, CVE-2024-53239, CVE-2024-56634,\nCVE-2024-56653, CVE-2024-53196, CVE-2024-56596, CVE-2024-50133,\nCVE-2024-50142, CVE-2024-50045, CVE-2024-53119, CVE-2024-56694,\nCVE-2024-50188, CVE-2024-50218, CVE-2024-50259, CVE-2024-56605,\nCVE-2024-53232, CVE-2024-57885, CVE-2024-50198, CVE-2024-56764,\nCVE-2025-21648, CVE-2024-50108, CVE-2024-56644, CVE-2024-50156,\nCVE-2024-53215, CVE-2024-50221, CVE-2024-56678, CVE-2024-50103,\nCVE-2024-53230, CVE-2024-50047, CVE-2024-50202, CVE-2024-56588,\nCVE-2024-53117, CVE-2024-53048, CVE-2025-21660, CVE-2024-53154,\nCVE-2024-50187, CVE-2024-50066, CVE-2024-50170, CVE-2024-56667,\nCVE-2024-56540, CVE-2024-53113, CVE-2024-44955, CVE-2024-53172,\nCVE-2024-49865, CVE-2024-56604, CVE-2025-21638, CVE-2024-50093,\nCVE-2024-50128, CVE-2024-50279, CVE-2024-50286, CVE-2024-50083,\nCVE-2024-56657, CVE-2024-53085, CVE-2024-50303, CVE-2024-57838,\nCVE-2024-56551, CVE-2024-54193, CVE-2024-57888, CVE-2024-50070,\nCVE-2024-50172, CVE-2024-57890, CVE-2024-56578, CVE-2025-21938,\nCVE-2024-53066, CVE-2024-54683, CVE-2024-50196, CVE-2024-49968,\nCVE-2024-56692, CVE-2024-50074, CVE-2024-53053, CVE-2024-50031,\nCVE-2024-54455, CVE-2024-57807, CVE-2024-56742, CVE-2024-57883,\nCVE-2024-50099, CVE-2024-50025, CVE-2024-57850, CVE-2024-57896,\nCVE-2024-56587, CVE-2024-50087, CVE-2024-57806, CVE-2024-53203,\nCVE-2024-50272, CVE-2024-50300, CVE-2024-50058, CVE-2024-50232,\nCVE-2024-50111, CVE-2024-50063, CVE-2024-50297, CVE-2024-50252,\nCVE-2024-53221, CVE-2024-50250, CVE-2024-50146, CVE-2024-53114,\nCVE-2024-50215, CVE-2024-50244, CVE-2024-56369, CVE-2024-53055,\nCVE-2024-49906, CVE-2024-43098, CVE-2024-58237, CVE-2024-57913,\nCVE-2024-50085, CVE-2024-53109, CVE-2024-56693, CVE-2025-21993,\nCVE-2024-53213, CVE-2024-50026, CVE-2024-53095, CVE-2024-56664,\nCVE-2024-53111, CVE-2024-50041, CVE-2024-50021, CVE-2024-39282,\nCVE-2024-56592, CVE-2024-56748, CVE-2024-47794, CVE-2024-50271,\nCVE-2024-56614, CVE-2024-50166, CVE-2024-57849, CVE-2024-56573,\nCVE-2024-56620, CVE-2024-50194, CVE-2024-56723, CVE-2024-50267,\nCVE-2024-56779, CVE-2024-56656, CVE-2024-50164, CVE-2024-50076,\nCVE-2024-50126, CVE-2025-21831, CVE-2024-56610, CVE-2024-56670,\nCVE-2024-53145, CVE-2024-56760, CVE-2024-56602, CVE-2024-53202)\n","status":"published","published":"2025-05-20T15:09:47Z","modified":"2026-11-03T21:17:40.131927753Z","updated_at":"2026-11-03T21:43:54.166508Z"},{"id":"USN-7524-1","title":"linux-raspi vulnerabilities","description":"Several security issues were discovered in the Linux kernel.\nAn attacker could possibly use these to compromise the system.\nThis update corrects flaws in the following subsystems:\n  - ARM64 architecture;\n  - MIPS architecture;\n  - PowerPC architecture;\n  - RISC-V architecture;\n  - S390 architecture;\n  - SuperH RISC architecture;\n  - User-Mode Linux (UML);\n  - x86 architecture;\n  - Block layer subsystem;\n  - Cryptographic API;\n  - Compute Acceleration Framework;\n  - ACPI drivers;\n  - Drivers core;\n  - RAM backed block device driver;\n  - Ublk userspace block driver;\n  - Virtio block driver;\n  - Compressed RAM block device driver;\n  - Bluetooth drivers;\n  - TPM device driver;\n  - Clock framework and drivers;\n  - Data acquisition framework and drivers;\n  - CPU frequency scaling framework;\n  - Hardware crypto device drivers;\n  - CXL (Compute Express Link) drivers;\n  - DAX dirext access to differentiated memory framework;\n  - DMA engine subsystem;\n  - EDAC drivers;\n  - ARM SCMI message protocol;\n  - ARM SCPI message protocol;\n  - EFI core;\n  - iSCSI Boot Firmware Table Attributes driver;\n  - GPIO subsystem;\n  - GPU drivers;\n  - HID subsystem;\n  - Microsoft Hyper-V drivers;\n  - Hardware monitoring drivers;\n  - I3C subsystem;\n  - IIO ADC drivers;\n  - IIO subsystem;\n  - InfiniBand drivers;\n  - IOMMU subsystem;\n  - IRQ chip drivers;\n  - LED subsystem;\n  - Multiple devices driver;\n  - Media drivers;\n  - Multifunction device drivers;\n  - Microchip PCI driver;\n  - MMC subsystem;\n  - MTD block device drivers;\n  - Network drivers;\n  - Mellanox network drivers;\n  - STMicroelectronics network drivers;\n  - NTB driver;\n  - Virtio pmem driver;\n  - NVME drivers;\n  - Parport drivers;\n  - PCI subsystem;\n  - PHY drivers;\n  - Pin controllers subsystem;\n  - x86 platform drivers;\n  - i.MX PM domains;\n  - Power supply drivers;\n  - Voltage and Current Regulator drivers;\n  - StarFive reset controller drivers;\n  - Real Time Clock drivers;\n  - SCSI subsystem;\n  - SuperH / SH-Mobile drivers;\n  - i.MX SoC drivers;\n  - QCOM SoC drivers;\n  - Xilinx SoC drivers;\n  - SPI subsystem;\n  - Direct Digital Synthesis drivers;\n  - Media staging drivers;\n  - TCM subsystem;\n  - Thermal drivers;\n  - TTY drivers;\n  - UFS subsystem;\n  - DesignWare USB3 driver;\n  - USB Gadget drivers;\n  - USB Host Controller drivers;\n  - USB Dual Role (OTG-ready) Controller drivers;\n  - USB Serial drivers;\n  - USB Type-C support driver;\n  - USB Type-C Port Controller Manager driver;\n  - TI TPS6598x USB Power Delivery controller driver;\n  - USB Type-C Connector System Software Interface driver;\n  - vDPA drivers;\n  - VFIO drivers;\n  - Framebuffer layer;\n  - TDX Guest driver;\n  - Xen hypervisor drivers;\n  - AFS file system;\n  - BTRFS file system;\n  - File systems infrastructure;\n  - Ceph distributed file system;\n  - EROFS file system;\n  - Ext4 file system;\n  - F2FS 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  - NTFS3 file system;\n  - Overlay file system;\n  - Proc file system;\n  - Diskquota system;\n  - SMB network file system;\n  - UBI file system;\n  - DRM display driver;\n  - BPF subsystem;\n  - VLANs driver;\n  - Kernel Samepage Merging mechanism;\n  - Memory management;\n  - Network file system (NFS) superblock;\n  - Kernel stack handling interfaces;\n  - StackDepot library;\n  - Task handling mechanism;\n  - userfaultfd() syscall;\n  - Bluetooth subsystem;\n  - IP tunnels definitions;\n  - LAPB network protocol;\n  - Network namespace;\n  - Netfilter;\n  - Network traffic control;\n  - Network sockets;\n  - Tracing infrastructure;\n  - User-space API (UAPI);\n  - Kernel init infrastructure;\n  - io_uring subsystem;\n  - IPC subsystem;\n  - Control group (cgroup);\n  - DMA mapping infrastructure;\n  - Kernel fork() syscall;\n  - KCSAN framework;\n  - Kernel thread helper (kthread);\n  - RCU subsystem;\n  - Arbitrary resource management;\n  - Scheduler infrastructure;\n  - Signal handling mechanism;\n  - Timer subsystem;\n  - Workqueue subsystem;\n  - Vector I/O iterator library;\n  - KUnit library;\n  - Maple Tree data structure library;\n  - 9P file system network protocol;\n  - Ethernet bridge;\n  - CAN network layer;\n  - Networking core;\n  - DCCP (Datagram Congestion Control Protocol);\n  - Ethtool driver;\n  - HSR network protocol;\n  - IEEE802154.4 network protocol;\n  - IPv4 networking;\n  - IPv6 networking;\n  - IUCV driver;\n  - MAC80211 subsystem;\n  - Multipath TCP;\n  - Netlink;\n  - NET/ROM layer;\n  - Packet sockets;\n  - RDS protocol;\n  - RxRPC session sockets;\n  - SCTP protocol;\n  - SMC sockets;\n  - Sun RPC protocol;\n  - TIPC protocol;\n  - Unix domain sockets;\n  - VMware vSockets driver;\n  - Wireless networking;\n  - eXpress Data Path;\n  - XFRM subsystem;\n  - Integrity Measurement Architecture(IMA) framework;\n  - Key management;\n  - SELinux security module;\n  - ALSA framework;\n  - FireWire sound drivers;\n  - HD-audio driver;\n  - MediaTek ASoC drivers;\n  - QCOM ASoC drivers;\n  - SoC audio core drivers;\n  - STMicroelectronics SoC drivers;\n  - USB sound devices;\n(CVE-2025-21651, CVE-2024-55881, CVE-2024-50223, CVE-2024-50033,\nCVE-2024-57907, CVE-2024-53233, CVE-2024-57798, CVE-2024-50262,\nCVE-2024-50265, CVE-2024-50197, CVE-2024-50066, CVE-2024-50271,\nCVE-2024-57892, CVE-2024-56767, CVE-2024-50237, CVE-2024-56638,\nCVE-2024-50084, CVE-2025-21638, CVE-2024-56630, CVE-2024-50193,\nCVE-2024-50093, CVE-2024-49914, CVE-2024-50221, CVE-2024-50202,\nCVE-2025-21659, CVE-2024-50009, CVE-2024-53059, CVE-2024-50206,\nCVE-2024-53239, CVE-2024-53219, CVE-2024-53139, CVE-2024-56752,\nCVE-2024-50125, CVE-2024-53226, CVE-2024-57940, CVE-2024-57925,\nCVE-2024-53081, CVE-2024-53053, CVE-2024-56627, CVE-2024-57882,\nCVE-2025-21645, CVE-2025-21642, CVE-2024-50120, CVE-2024-50240,\nCVE-2024-53168, CVE-2024-53178, CVE-2024-53166, CVE-2024-50030,\nCVE-2024-50299, CVE-2024-57926, CVE-2024-55916, CVE-2024-56593,\nCVE-2024-53083, CVE-2024-56641, CVE-2024-50049, CVE-2024-56761,\nCVE-2024-56664, CVE-2024-50242, CVE-2024-56589, CVE-2024-50248,\nCVE-2024-41013, CVE-2024-50291, CVE-2024-53061, CVE-2024-50105,\nCVE-2024-53171, CVE-2024-56568, CVE-2024-50133, CVE-2024-56594,\nCVE-2024-56582, CVE-2024-53100, CVE-2024-50021, CVE-2024-56603,\nCVE-2024-50055, CVE-2024-56637, CVE-2024-50273, CVE-2025-21660,\nCVE-2024-50083, CVE-2024-53063, CVE-2024-56599, CVE-2024-56783,\nCVE-2025-21993, CVE-2024-50019, CVE-2024-53177, CVE-2024-50038,\nCVE-2024-53113, CVE-2024-50215, CVE-2024-50036, CVE-2024-44955,\nCVE-2024-56602, CVE-2024-54193, CVE-2024-56685, CVE-2024-50137,\nCVE-2025-21640, CVE-2024-57838, CVE-2024-50024, CVE-2024-57849,\nCVE-2024-50304, CVE-2024-50263, CVE-2024-50048, CVE-2024-53176,\nCVE-2024-50191, CVE-2024-56781, CVE-2024-56548, CVE-2024-50278,\nCVE-2024-57906, CVE-2024-53114, CVE-2025-21646, CVE-2024-53196,\nCVE-2024-50135, CVE-2024-50286, CVE-2025-21831, CVE-2024-50163,\nCVE-2024-56694, CVE-2024-50023, CVE-2024-50031, CVE-2024-56709,\nCVE-2024-50107, CVE-2024-56672, CVE-2024-57887, CVE-2024-50162,\nCVE-2024-50207, CVE-2024-53155, CVE-2024-50095, CVE-2024-56703,\nCVE-2024-50268, CVE-2024-56607, CVE-2024-53115, CVE-2024-56739,\nCVE-2024-53091, CVE-2024-50086, CVE-2024-56580, CVE-2024-56572,\nCVE-2024-56693, CVE-2024-57904, CVE-2025-21938, CVE-2024-56698,\nCVE-2024-50039, CVE-2024-50233, CVE-2024-50282, CVE-2024-50251,\nCVE-2024-53184, CVE-2025-21700, CVE-2024-56565, CVE-2024-53117,\nCVE-2024-50288, CVE-2024-50171, CVE-2024-56583, CVE-2024-50115,\nCVE-2024-53687, CVE-2024-49568, CVE-2024-53047, CVE-2024-53150,\nCVE-2024-56549, CVE-2024-50148, CVE-2024-56679, CVE-2024-57888,\nCVE-2024-53680, CVE-2024-50155, CVE-2024-56751, CVE-2024-56610,\nCVE-2024-50272, CVE-2024-50182, CVE-2024-57916, CVE-2024-53237,\nCVE-2024-50211, CVE-2024-56605, CVE-2024-56601, CVE-2024-48873,\nCVE-2024-50166, CVE-2024-50085, CVE-2024-50108, CVE-2024-57792,\nCVE-2024-50224, CVE-2024-56779, CVE-2024-50068, CVE-2024-53151,\nCVE-2024-56657, CVE-2024-50026, CVE-2024-53138, CVE-2024-57896,\nCVE-2024-53222, CVE-2024-50164, CVE-2024-53230, CVE-2024-56614,\nCVE-2024-53089, CVE-2024-57895, CVE-2024-56755, CVE-2024-50096,\nCVE-2024-56645, CVE-2024-53162, CVE-2024-56566, CVE-2024-53086,\nCVE-2024-56718, CVE-2024-50062, CVE-2024-50065, CVE-2024-56763,\nCVE-2024-56538, CVE-2024-53127, CVE-2024-49893, CVE-2024-53087,\nCVE-2024-53058, CVE-2024-57945, CVE-2024-53174, CVE-2024-53096,\nCVE-2024-56546, CVE-2024-56754, CVE-2024-49865, CVE-2024-56635,\nCVE-2024-56539, CVE-2024-56551, CVE-2024-53044, CVE-2024-56700,\nCVE-2024-56787, CVE-2024-56586, CVE-2024-56687, CVE-2024-53236,\nCVE-2024-50058, CVE-2024-53146, CVE-2024-50269, CVE-2024-50056,\nCVE-2024-56608, CVE-2024-49899, CVE-2024-53099, CVE-2024-57902,\nCVE-2024-56656, CVE-2024-50126, CVE-2024-50274, CVE-2025-21654,\nCVE-2025-21971, CVE-2024-53130, CVE-2024-49571, CVE-2024-56742,\nCVE-2024-56613, CVE-2024-56575, CVE-2024-56540, CVE-2024-53194,\nCVE-2024-50044, CVE-2024-49906, CVE-2024-53163, CVE-2024-56774,\nCVE-2024-50143, CVE-2024-49968, CVE-2024-53202, CVE-2024-57876,\nCVE-2024-56650, CVE-2024-53685, CVE-2025-21656, CVE-2024-56648,\nCVE-2025-21636, CVE-2024-56782, CVE-2024-50198, CVE-2024-50110,\nCVE-2024-56775, CVE-2024-50239, CVE-2024-53156, CVE-2024-50045,\nCVE-2024-53045, CVE-2024-58237, CVE-2024-50167, CVE-2024-50060,\nCVE-2024-56372, CVE-2024-56756, CVE-2024-54455, CVE-2024-56543,\nCVE-2024-56772, CVE-2024-50131, CVE-2024-56616, CVE-2024-50185,\nCVE-2024-53154, CVE-2024-50138, CVE-2024-53111, CVE-2024-50025,\nCVE-2024-50156, CVE-2024-39282, CVE-2024-53140, CVE-2024-57872,\nCVE-2024-50077, CVE-2025-21652, CVE-2025-21655, CVE-2024-57901,\nCVE-2024-57791, CVE-2024-50259, CVE-2024-57890, CVE-2024-56770,\nCVE-2024-53170, CVE-2024-56705, CVE-2024-56597, CVE-2024-50047,\nCVE-2024-53101, CVE-2024-50128, CVE-2024-50287, CVE-2024-50186,\nCVE-2024-56745, CVE-2024-56720, CVE-2024-57889, CVE-2024-56590,\nCVE-2024-57807, CVE-2024-50158, CVE-2024-53198, CVE-2024-57843,\nCVE-2024-53095, CVE-2024-56678, CVE-2024-56758, CVE-2024-53120,\nCVE-2024-50087, CVE-2024-50147, CVE-2024-56652, CVE-2024-56692,\nCVE-2024-56724, CVE-2024-50226, CVE-2024-56609, CVE-2024-56769,\nCVE-2024-47408, CVE-2024-53187, CVE-2024-56596, CVE-2024-48875,\nCVE-2024-50236, CVE-2024-50284, CVE-2024-49921, CVE-2024-53229,\nCVE-2024-50256, CVE-2024-57946, CVE-2024-53175, CVE-2024-56619,\nCVE-2024-50257, CVE-2024-53210, CVE-2024-53203, CVE-2025-21658,\nCVE-2024-56683, CVE-2024-50302, CVE-2024-56570, CVE-2024-50187,\nCVE-2025-21650, CVE-2024-50082, CVE-2024-50194, CVE-2024-53072,\nCVE-2024-50118, CVE-2024-53043, CVE-2024-50160, CVE-2025-21635,\nCVE-2024-57900, CVE-2024-57879, CVE-2024-50294, CVE-2024-48876,\nCVE-2024-50250, CVE-2024-50220, CVE-2025-21648, CVE-2024-50032,\nCVE-2024-56765, CVE-2024-56369, CVE-2024-53109, CVE-2024-47143,\nCVE-2025-21643, CVE-2024-50261, CVE-2024-56558, CVE-2024-49920,\nCVE-2024-56689, CVE-2024-56647, CVE-2024-50290, CVE-2024-57908,\nCVE-2024-53209, CVE-2024-53220, CVE-2024-50073, CVE-2024-47711,\nCVE-2024-50183, CVE-2024-56690, CVE-2024-50067, CVE-2024-56778,\nCVE-2024-56622, CVE-2024-56729, CVE-2024-53157, CVE-2024-53213,\nCVE-2024-50130, CVE-2024-56629, CVE-2024-57885, CVE-2025-21637,\nCVE-2024-50078, CVE-2024-53224, CVE-2024-50116, CVE-2024-53068,\nCVE-2024-50300, CVE-2024-53084, CVE-2024-50099, CVE-2024-56723,\nCVE-2024-50230, CVE-2024-56636, CVE-2024-50252, CVE-2024-56587,\nCVE-2024-53131, CVE-2024-50046, CVE-2024-50200, CVE-2024-56588,\nCVE-2024-47726, CVE-2024-56615, CVE-2024-57917, CVE-2024-50063,\nCVE-2024-50246, CVE-2024-53055, CVE-2024-53133, CVE-2024-50205,\nCVE-2024-53076, CVE-2024-50283, CVE-2024-56660, CVE-2024-56707,\nCVE-2024-50180, CVE-2024-56746, CVE-2025-21756, CVE-2024-50127,\nCVE-2024-50145, CVE-2024-56625, CVE-2024-56760, CVE-2024-53121,\nCVE-2024-53122, CVE-2024-53062, CVE-2024-53046, CVE-2024-56764,\nCVE-2024-57801, CVE-2024-56728, CVE-2022-49034, CVE-2024-53094,\nCVE-2024-53147, CVE-2024-56776, CVE-2024-57898, CVE-2024-53148,\nCVE-2024-56704, CVE-2024-50035, CVE-2024-50152, CVE-2024-50169,\nCVE-2024-56600, CVE-2024-56681, CVE-2024-45828, CVE-2024-53052,\nCVE-2024-56574, CVE-2024-56531, CVE-2024-50303, CVE-2024-57897,\nCVE-2024-53123, CVE-2024-57874, CVE-2024-57939, CVE-2024-47141,\nCVE-2024-56659, CVE-2024-50069, CVE-2024-50141, CVE-2024-50201,\nCVE-2024-50270, CVE-2024-56621, CVE-2024-56606, CVE-2024-53129,\nCVE-2024-57938, CVE-2024-50203, CVE-2024-56708, CVE-2024-53197,\nCVE-2024-53208, CVE-2024-50028, CVE-2024-56677, CVE-2025-21664,\nCVE-2024-50121, CVE-2024-56644, CVE-2024-57804, CVE-2024-53145,\nCVE-2024-56780, CVE-2024-50112, CVE-2024-56759, CVE-2024-50192,\nCVE-2024-53181, CVE-2024-50170, CVE-2024-50080, CVE-2024-50238,\nCVE-2024-57912, CVE-2024-50222, CVE-2024-36476, CVE-2024-53107,\nCVE-2024-53119, CVE-2024-43098, CVE-2024-56604, CVE-2024-56567,\nCVE-2024-47736, CVE-2024-53180, CVE-2024-38608, CVE-2024-53227,\nCVE-2024-50136, CVE-2024-53105, CVE-2024-50225, CVE-2024-56649,\nCVE-2024-57899, CVE-2024-41014, CVE-2024-50188, CVE-2024-53160,\nCVE-2024-53183, CVE-2024-54460, CVE-2024-56725, CVE-2024-56642,\nCVE-2024-53223, CVE-2024-56631, CVE-2024-50134, CVE-2024-53135,\nCVE-2024-56573, CVE-2024-50104, CVE-2024-53126, CVE-2024-56667,\nCVE-2025-21662, CVE-2024-53221, CVE-2024-56786, CVE-2024-50040,\nCVE-2024-53085, CVE-2024-50051, CVE-2024-56721, CVE-2024-52332,\nCVE-2024-50075, CVE-2024-50208, CVE-2024-50209, CVE-2024-56710,\nCVE-2024-50296, CVE-2024-53066, CVE-2025-21701, CVE-2024-56584,\nCVE-2024-41932, CVE-2024-50059, CVE-2024-57911, CVE-2024-56785,\nCVE-2024-50216, CVE-2024-50249, CVE-2024-49569, CVE-2024-50098,\nCVE-2024-56777, CVE-2024-53093, CVE-2024-53067, CVE-2025-21634,\nCVE-2024-53190, CVE-2024-50199, CVE-2024-56577, CVE-2024-56653,\nCVE-2024-50027, CVE-2024-50285, CVE-2025-21632, CVE-2025-21702,\nCVE-2024-57893, CVE-2024-50235, CVE-2024-56658, CVE-2024-57802,\nCVE-2024-58087, CVE-2024-53112, CVE-2024-47809, CVE-2024-50111,\nCVE-2024-57910, CVE-2024-53142, CVE-2024-50196, CVE-2024-56578,\nCVE-2024-53200, CVE-2024-50276, CVE-2024-53188, CVE-2024-53048,\nCVE-2024-56771, CVE-2024-53228, CVE-2024-57850, CVE-2024-49972,\nCVE-2025-21647, CVE-2024-50072, CVE-2024-56701, CVE-2024-53232,\nCVE-2024-50088, CVE-2024-56557, CVE-2024-56632, CVE-2024-50142,\nCVE-2024-57806, CVE-2024-53051, CVE-2024-57931, CVE-2024-50103,\nCVE-2024-50258, CVE-2024-53172, CVE-2024-53106, CVE-2024-53158,\nCVE-2024-56595, CVE-2024-53108, CVE-2024-56626, CVE-2024-56691,\nCVE-2024-50289, CVE-2024-53217, CVE-2024-50234, CVE-2024-54683,\nCVE-2024-53042, CVE-2024-56675, CVE-2024-50195, CVE-2024-53195,\nCVE-2024-56654, CVE-2024-56715, CVE-2025-21639, CVE-2024-57913,\nCVE-2024-56717, CVE-2024-56651, CVE-2024-56688, CVE-2024-53128,\nCVE-2024-53169, CVE-2024-56620, CVE-2024-50189, CVE-2024-56550,\nCVE-2024-50244, CVE-2024-50279, CVE-2024-42122, CVE-2024-58099,\nCVE-2024-53179, CVE-2024-56532, CVE-2024-53215, CVE-2024-50232,\nCVE-2024-50029, CVE-2024-57933, CVE-2024-56662, CVE-2024-53690,\nCVE-2024-53134, CVE-2024-48881, CVE-2024-56727, CVE-2024-56576,\nCVE-2024-56670, CVE-2024-56598, CVE-2024-53161, CVE-2024-50061,\nCVE-2024-50117, CVE-2025-21653, CVE-2024-50101, CVE-2024-55639,\nCVE-2025-21649, CVE-2024-53231, CVE-2024-50041, CVE-2024-50231,\nCVE-2024-57932, CVE-2024-50076, CVE-2024-53165, CVE-2024-57793,\nCVE-2024-53082, CVE-2024-50020, CVE-2024-50267, CVE-2024-57883,\nCVE-2024-50298, CVE-2024-56643, CVE-2024-56640, CVE-2024-50074,\nCVE-2024-53125, CVE-2024-56748, CVE-2024-56634, CVE-2024-50064,\nCVE-2024-50172, CVE-2024-50255, CVE-2024-50042, CVE-2024-57929,\nCVE-2024-56773, CVE-2024-53214, CVE-2024-53110, CVE-2024-56569,\nCVE-2024-56581, CVE-2024-56716, CVE-2024-50090, CVE-2024-53218,\nCVE-2024-57884, CVE-2024-56611, CVE-2024-50243, CVE-2024-56545,\nCVE-2024-56623, CVE-2024-53173, CVE-2024-53090, CVE-2025-21631,\nCVE-2024-56744, CVE-2024-56722, CVE-2024-50297, CVE-2024-56726,\nCVE-2024-56592, CVE-2024-50275, CVE-2025-21663, CVE-2024-57841,\nCVE-2024-50150, CVE-2024-50301, CVE-2024-56579, CVE-2024-53088,\nCVE-2024-50153, CVE-2024-50280, CVE-2024-50124, CVE-2024-50229,\nCVE-2024-50146, CVE-2024-50057, CVE-2024-56562, CVE-2024-50070,\nCVE-2024-50218, CVE-2024-53118, CVE-2024-47794, CVE-2024-50295,\nCVE-2024-56747, CVE-2024-56663, CVE-2024-50292, CVE-2024-50140,\nCVE-2024-50154, CVE-2024-53050, CVE-2024-41935, CVE-2024-56533,\nCVE-2024-50139, CVE-2024-56633, CVE-2024-50184, CVE-2024-53191,\nCVE-2024-50022, CVE-2024-50010, CVE-2024-50245, CVE-2024-53079,\nCVE-2024-50151, CVE-2024-53234, CVE-2024-50247, CVE-2024-50159,\nCVE-2024-57903)\n","status":"published","published":"2025-05-26T12:39:02Z","modified":"2026-11-03T21:17:41.40645054Z","updated_at":"2026-11-03T21:43:54.166508Z"}]}}