{"id":"CVE-2024-56760","aliases":["AZL-55044","BELL-CVE-2024-56760","DEBIAN-CVE-2024-56760","EUVD-2024-53403","GHSA-7vgm-4f6w-wj5f","MGASA-2025-0030","MGASA-2025-0032","OESA-2026-2417","OESA-2026-2418","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-56760","USN-7379-1","USN-7381-1","USN-7382-1","USN-7513-1","USN-7513-2","USN-7513-3","USN-7513-4","USN-7513-5","USN-7514-1","USN-7515-1","USN-7515-2","USN-7522-1","USN-7523-1","USN-7524-1"],"status":"published","title":"PCI/MSI: Handle lack of irqdomain gracefully","description":"In the Linux kernel, the following vulnerability has been resolved:\n\nPCI/MSI: Handle lack of irqdomain gracefully\n\nAlexandre observed a warning emitted from pci_msi_setup_msi_irqs() on a\nRISCV platform which does not provide PCI/MSI support:\n\n WARNING: CPU: 1 PID: 1 at drivers/pci/msi/msi.h:121 pci_msi_setup_msi_irqs+0x2c/0x32\n __pci_enable_msix_range+0x30c/0x596\n pci_msi_setup_msi_irqs+0x2c/0x32\n pci_alloc_irq_vectors_affinity+0xb8/0xe2\n\nRISCV uses hierarchical interrupt domains and correctly does not implement\nthe legacy fallback. The warning triggers from the legacy fallback stub.\n\nThat warning is bogus as the PCI/MSI layer knows whether a PCI/MSI parent\ndomain is associated with the device or not. There is a check for MSI-X,\nwhich has a legacy assumption. But that legacy fallback assumption is only\nvalid when legacy support is enabled, but otherwise the check should simply\nreturn -ENOTSUPP.\n\nLoongarch tripped over the same problem and blindly enabled legacy support\nwithout implementing the legacy fallbacks. There are weak implementations\nwhich return an error, so the problem was papered over.\n\nCorrect pci_msi_domain_supports() to evaluate the legacy mode and add\nthe missing supported check into the MSI enable path to complete it.","severity":{"version":"3.1","score":5.5,"vector":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H","level":"medium","assessor":"primary","from":"nvd"},"epss":{"day":"2026-11-10","score":0.00206,"percentile":0.10723,"model":"v2026.06.15"},"facts":{"in_kev":false,"known_exploited":false,"public_exploit":false,"fix_available":true},"published":"2025-01-06T16:20:40Z","modified":"2026-11-03T21:17:41Z","fixes":[{"ecosystem":"Azure Linux:3","package":"kernel","fixed_in":["6.6.76.1-1"],"sources":["osv"]},{"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.6.69","6.12.8"],"sources":["osv"]},{"ecosystem":"Debian:13","package":"linux","fixed_in":["6.12.8-1"],"sources":["osv"]},{"ecosystem":"Debian:14","package":"linux","fixed_in":["6.12.8-1"],"sources":["osv"]},{"ecosystem":"Ubuntu:22.04:LTS","package":"linux-aws-6.8","fixed_in":["6.8.0-1029.31~22.04.1"],"sources":["osv"]},{"ecosystem":"Ubuntu:22.04:LTS","package":"linux-azure-6.8","fixed_in":["6.8.0-1029.34~22.04.1"],"sources":["osv"]},{"ecosystem":"Ubuntu:22.04:LTS","package":"linux-gcp-6.8","fixed_in":["6.8.0-1030.32~22.04.1"],"sources":["osv"]},{"ecosystem":"Ubuntu:22.04:LTS","package":"linux-hwe-6.8","fixed_in":["6.8.0-60.63~22.04.1"],"sources":["osv"]},{"ecosystem":"Ubuntu:22.04:LTS","package":"linux-ibm-6.8","fixed_in":["6.8.0-1026.26~22.04.1"],"sources":["osv"]},{"ecosystem":"Ubuntu:22.04:LTS","package":"linux-lowlatency-hwe-6.8","fixed_in":["6.8.0-60.63.1~22.04.1"],"sources":["osv"]},{"ecosystem":"Ubuntu:22.04:LTS","package":"linux-nvidia-6.8","fixed_in":["6.8.0-1028.31~22.04.1"],"sources":["osv"]},{"ecosystem":"Ubuntu:22.04:LTS","package":"linux-oracle-6.8","fixed_in":["6.8.0-1026.27~22.04.1"],"sources":["osv"]},{"ecosystem":"Ubuntu:22.04:LTS","package":"linux-riscv-6.8","fixed_in":["6.8.0-62.65~22.04.1"],"sources":["osv"]},{"ecosystem":"Ubuntu:Pro:Realtime:22.04:LTS","package":"linux-realtime-6.8","fixed_in":["6.8.1-1022.23~22.04.1"],"sources":["osv"]},{"ecosystem":"Ubuntu:24.04:LTS","package":"linux","fixed_in":["6.8.0-60.63"],"sources":["osv"]},{"ecosystem":"Ubuntu:24.04:LTS","package":"linux-aws","fixed_in":["6.8.0-1029.31"],"sources":["osv"]},{"ecosystem":"Ubuntu:24.04:LTS","package":"linux-azure","fixed_in":["6.8.0-1029.34"],"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-1016.17"],"sources":["osv"]},{"ecosystem":"Ubuntu:24.04:LTS","package":"linux-gcp","fixed_in":["6.8.0-1030.32"],"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-1025.29"],"sources":["osv"]},{"ecosystem":"Ubuntu:24.04:LTS","package":"linux-gkeop","fixed_in":["6.8.0-1012.14"],"sources":["osv"]},{"ecosystem":"Ubuntu:24.04:LTS","package":"linux-hwe-6.11","fixed_in":["6.11.0-21.21~24.04.1"],"sources":["osv"]},{"ecosystem":"Ubuntu:24.04:LTS","package":"linux-ibm","fixed_in":["6.8.0-1026.26"],"sources":["osv"]},{"ecosystem":"Ubuntu:24.04:LTS","package":"linux-lowlatency","fixed_in":["6.8.0-60.63.1"],"sources":["osv"]},{"ecosystem":"Ubuntu:24.04:LTS","package":"linux-nvidia","fixed_in":["6.8.0-1028.31"],"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-1028.31.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-1017.17"],"sources":["osv"]},{"ecosystem":"Ubuntu:24.04:LTS","package":"linux-oem-6.8","fixed_in":["6.8.0-1028.28"],"sources":["osv"]},{"ecosystem":"Ubuntu:24.04:LTS","package":"linux-oracle","fixed_in":["6.8.0-1026.27"],"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-60.63.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-1022.23"],"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":"Azure Linux:3","package":"kernel","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.6.76.1-1"}]}]},{"source":"osv","ecosystem":"Alpaquita:25","package":"linux-lts","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"6.6.89-r0"},{"fixed":"6.12.41-r0"}]}]},{"source":"osv","ecosystem":"Alpaquita:stream","package":"linux-lts","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"6.12.92-r1"},{"fixed":"6.18.35-r1"}]}]},{"source":"osv","ecosystem":"Linux","package":"Kernel","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"6.2.0"},{"fixed":"6.6.69"}]},{"type":"ECOSYSTEM","events":[{"introduced":"6.7.0"},{"fixed":"6.12.8"}]}]},{"source":"osv","ecosystem":"Debian:13","package":"linux","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.12.8-1"}]}]},{"source":"osv","ecosystem":"Debian:14","package":"linux","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.12.8-1"}]}]},{"source":"osv","ecosystem":"Mageia:9","package":"kernel","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.6.74-1.mga9"}]}],"bundled":202},{"source":"osv","ecosystem":"Mageia:9","package":"kmod-virtualbox","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"7.0.24-64.mga9"}]}],"bundled":202},{"source":"osv","ecosystem":"Mageia:9","package":"kmod-xtables-addons","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"3.24-70.mga9"}]}],"bundled":202},{"source":"osv","ecosystem":"Mageia:9","package":"dwarves","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1.29-1.mga9"}]}],"bundled":202},{"source":"osv","ecosystem":"Mageia:9","package":"kernel-linus","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.6.74-1.mga9"}]}],"bundled":202},{"source":"osv","ecosystem":"openEuler:24.03-LTS","package":"kernel","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.6.0-145.0.12.138.oe2403"}]}],"bundled":108},{"source":"osv","ecosystem":"openEuler:24.03-LTS-SP1","package":"kernel","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.6.0-145.1.12.150.oe2403sp1"}]}],"bundled":122},{"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-1029.31~22.04.1"}]}],"versions":["6.8.0-1009.9~22.04.2","6.8.0-1010.10~22.04.2","6.8.0-1011.12~22.04.1","6.8.0-1013.14~22.04.1","6.8.0-1014.15~22.04.1","6.8.0-1015.16~22.04.1","6.8.0-1016.17~22.04.2","6.8.0-1017.18~22.04.1","6.8.0-1018.19~22.04.1","6.8.0-1019.21~22.04.1","6.8.0-1020.22~22.04.1","6.8.0-1021.23~22.04.1","6.8.0-1023.25~22.04.1","6.8.0-1024.26~22.04.1","6.8.0-1027.29~22.04.1","6.8.0-1028.30~22.04.1"]},{"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-1029.34~22.04.1"}]}],"versions":["6.8.0-1008.8~22.04.1","6.8.0-1009.9~22.04.1","6.8.0-1010.10~22.04.1","6.8.0-1012.14~22.04.1","6.8.0-1013.15~22.04.1","6.8.0-1014.16~22.04.1","6.8.0-1015.17~22.04.2","6.8.0-1017.20~22.04.1","6.8.0-1018.21~22.04.1","6.8.0-1020.23~22.04.1","6.8.0-1021.25~22.04.1","6.8.0-1025.30~22.04.1","6.8.0-1026.31~22.04.1","6.8.0-1027.32~22.04.1","6.8.0-1028.33~22.04.1"]},{"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-1030.32~22.04.1"}]}],"versions":["6.8.0-1010.11~22.04.1","6.8.0-1011.12~22.04.1","6.8.0-1012.13~22.04.1","6.8.0-1013.14~22.04.1","6.8.0-1014.16~22.04.1","6.8.0-1015.17~22.04.1","6.8.0-1016.18~22.04.1","6.8.0-1017.19~22.04.1","6.8.0-1018.20~22.04.1","6.8.0-1019.21~22.04.1","6.8.0-1020.22~22.04.1","6.8.0-1021.23~22.04.1","6.8.0-1024.26~22.04.1","6.8.0-1025.27~22.04.1","6.8.0-1026.28~22.04.1","6.8.0-1027.29~22.04.1","6.8.0-1028.30~22.04.1","6.8.0-1029.31~22.04.1"]},{"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-60.63~22.04.1"}]}],"versions":["6.8.0-38.38~22.04.1","6.8.0-39.39~22.04.1","6.8.0-40.40~22.04.3","6.8.0-45.45~22.04.1","6.8.0-47.47~22.04.1","6.8.0-48.48~22.04.1","6.8.0-49.49~22.04.1","6.8.0-50.51~22.04.1","6.8.0-51.52~22.04.1","6.8.0-52.53~22.04.1","6.8.0-57.59~22.04.1","6.8.0-58.60~22.04.1","6.8.0-59.61~22.04.1"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-ibm-6.8","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1026.26~22.04.1"}]}],"versions":["6.8.0-1008.8~22.04.1","6.8.0-1010.10~22.04.1","6.8.0-1011.11~22.04.1","6.8.0-1012.12~22.04.1","6.8.0-1013.13~22.04.1","6.8.0-1014.14~22.04.1","6.8.0-1015.15~22.04.1","6.8.0-1016.16~22.04.1","6.8.0-1017.17~22.04.1","6.8.0-1018.18~22.04.1","6.8.0-1019.19~22.04.1","6.8.0-1023.23~22.04.1","6.8.0-1024.24~22.04.1","6.8.0-1025.25~22.04.1"]},{"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-60.63.1~22.04.1"}]}],"versions":["6.8.0-38.38.1~22.04.2","6.8.0-40.40.1~22.04.1","6.8.0-44.44.1~22.04.1","6.8.0-45.45.1~22.04.1","6.8.0-47.47.1~22.04.1","6.8.0-48.48.3~22.04.1","6.8.0-49.49.1~22.04.1","6.8.0-50.51.1~22.04.1","6.8.0-51.52.1~22.04.1","6.8.0-52.53.1~22.04.1","6.8.0-54.56.1~22.04.1","6.8.0-55.57.1~22.04.1","6.8.0-56.58.1~22.04.1","6.8.0-57.59.1~22.04.1","6.8.0-58.60.1~22.04.1","6.8.0-59.61.1~22.04.1"]},{"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-1028.31~22.04.1"}]}],"versions":["6.8.0-1008.8~22.04.1","6.8.0-1009.9~22.04.1","6.8.0-1010.10~22.04.1","6.8.0-1011.11~22.04.1","6.8.0-1012.12~22.04.1","6.8.0-1013.14~22.04.1","6.8.0-1014.15~22.04.1","6.8.0-1015.16~22.04.1","6.8.0-1017.19~22.04.1","6.8.0-1018.20~22.04.1","6.8.0-1019.21~22.04.1","6.8.0-1020.22~22.04.1","6.8.0-1021.23~22.04.1","6.8.0-1022.25~22.04.2","6.8.0-1023.26~22.04.1","6.8.0-1024.27~22.04.1","6.8.0-1025.28~22.04.1","6.8.0-1026.29~22.04.1","6.8.0-1027.30~22.04.1"]},{"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-1026.27~22.04.1"}]}],"versions":["6.8.0-1006.6~22.04.3","6.8.0-1008.8~22.04.1","6.8.0-1010.10~22.04.1","6.8.0-1011.11~22.04.1","6.8.0-1012.12~22.04.1","6.8.0-1013.13~22.04.1","6.8.0-1014.14~22.04.1","6.8.0-1015.15~22.04.1","6.8.0-1016.17~22.04.1","6.8.0-1017.18~22.04.1","6.8.0-1018.19~22.04.1","6.8.0-1019.20~22.04.1","6.8.0-1020.21~22.04.1","6.8.0-1021.22~22.04.1","6.8.0-1022.23~22.04.1","6.8.0-1023.24~22.04.1","6.8.0-1024.25~22.04.1","6.8.0-1025.26~22.04.1"]},{"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-62.65~22.04.1"}]}],"versions":["6.8.0-38.38.1~22.04.1","6.8.0-39.39.1~22.04.1","6.8.0-40.40.1~22.04.1","6.8.0-41.41.1~22.04.1","6.8.0-44.44.1~22.04.1","6.8.0-47.47.1~22.04.1","6.8.0-48.48.1~22.04.2","6.8.0-49.49.1~22.04.1","6.8.0-50.51.1~22.04.1","6.8.0-51.52.1~22.04.1","6.8.0-52.53.1~22.04.1","6.8.0-53.55.1~22.04.1","6.8.0-55.57.1~22.04.1","6.8.0-56.58.1~22.04.1","6.8.0-57.59.1~22.04.1","6.8.0-58.60.1~22.04.1","6.8.0-59.61.1~22.04.1"]},{"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-1022.23~22.04.1"}]}],"versions":["6.8.1-1004.4~22.04.1","6.8.1-1005.5~22.04.2","6.8.1-1006.6~22.04.1","6.8.1-1007.7~22.04.1","6.8.1-1008.8~22.04.1","6.8.1-1009.9~22.04.1","6.8.1-1010.10~22.04.1","6.8.1-1011.11~22.04.1","6.8.1-1012.12~22.04.1","6.8.1-1013.14~22.04.1","6.8.1-1014.15~22.04.1","6.8.1-1015.16~22.04.1","6.8.1-1016.17~22.04.1","6.8.1-1017.18~22.04.1","6.8.1-1018.19~22.04.1","6.8.1-1019.20~22.04.1","6.8.1-1020.21~22.04.1","6.8.1-1021.22~22.04.1"]},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-60.63"}]}],"versions":["6.5.0-9.9","6.6.0-14.14","6.8.0-11.11","6.8.0-20.20","6.8.0-22.22","6.8.0-28.28","6.8.0-31.31","6.8.0-35.35","6.8.0-36.36","6.8.0-38.38","6.8.0-39.39","6.8.0-40.40","6.8.0-41.41","6.8.0-44.44","6.8.0-45.45","6.8.0-47.47","6.8.0-48.48","6.8.0-49.49","6.8.0-50.51","6.8.0-51.52","6.8.0-52.53","6.8.0-53.55","6.8.0-54.56","6.8.0-55.57","6.8.0-56.58","6.8.0-57.59","6.8.0-58.60","6.8.0-59.61"]},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-aws","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1029.31"}]}],"versions":["6.5.0-1008.8","6.6.0-1001.1","6.8.0-1001.1","6.8.0-1006.6","6.8.0-1008.8","6.8.0-1009.9","6.8.0-1010.10","6.8.0-1011.12","6.8.0-1012.13","6.8.0-1013.14","6.8.0-1014.15","6.8.0-1015.16","6.8.0-1016.17","6.8.0-1017.18","6.8.0-1018.20","6.8.0-1019.21","6.8.0-1020.22","6.8.0-1021.23","6.8.0-1023.25","6.8.0-1024.26","6.8.0-1025.27","6.8.0-1026.28","6.8.0-1027.29","6.8.0-1028.30"]},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-azure","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1029.34"}]}],"versions":["6.5.0-1007.7","6.6.0-1001.1","6.8.0-1001.1","6.8.0-1005.5","6.8.0-1006.6","6.8.0-1007.7","6.8.0-1008.8","6.8.0-1009.9","6.8.0-1010.10","6.8.0-1012.14","6.8.0-1013.15","6.8.0-1014.16","6.8.0-1015.17","6.8.0-1016.18","6.8.0-1017.20","6.8.0-1018.21","6.8.0-1020.23","6.8.0-1021.25","6.8.0-1025.30","6.8.0-1026.31","6.8.0-1027.32","6.8.0-1028.33"]},{"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-1016.17"}]}],"versions":["6.8.0-1013.14","6.8.0-1014.15"]},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-gcp","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1030.32"}]}],"versions":["6.5.0-1007.7","6.6.0-1001.1","6.8.0-1002.2","6.8.0-1005.5","6.8.0-1006.6","6.8.0-1007.7","6.8.0-1008.9","6.8.0-1009.10","6.8.0-1010.11","6.8.0-1011.12","6.8.0-1012.13","6.8.0-1013.14","6.8.0-1014.16","6.8.0-1015.17","6.8.0-1016.18","6.8.0-1017.19","6.8.0-1018.20","6.8.0-1019.21","6.8.0-1020.22","6.8.0-1021.23","6.8.0-1024.26","6.8.0-1025.27","6.8.0-1026.28","6.8.0-1027.29","6.8.0-1028.30","6.8.0-1029.31"]},{"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-1025.29"}]}],"versions":["6.8.0-1003.5","6.8.0-1004.7","6.8.0-1005.8","6.8.0-1006.9","6.8.0-1007.10","6.8.0-1008.11","6.8.0-1009.12","6.8.0-1010.13","6.8.0-1011.14","6.8.0-1012.15","6.8.0-1013.17","6.8.0-1014.18","6.8.0-1015.19","6.8.0-1016.20","6.8.0-1017.21","6.8.0-1019.23","6.8.0-1020.24","6.8.0-1021.25","6.8.0-1022.26","6.8.0-1023.27","6.8.0-1024.28"]},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-gkeop","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1012.14"}]}],"versions":["6.8.0-1001.3","6.8.0-1002.4","6.8.0-1003.5","6.8.0-1004.6","6.8.0-1006.8","6.8.0-1007.9","6.8.0-1008.10","6.8.0-1009.11","6.8.0-1010.12","6.8.0-1011.13"]},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-hwe-6.11","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.11.0-21.21~24.04.1"}]}],"versions":["6.11.0-17.17~24.04.2","6.11.0-19.19~24.04.1"]},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-ibm","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1026.26"}]}],"versions":["6.5.0-1009.9","6.8.0-1001.1","6.8.0-1003.3","6.8.0-1004.4","6.8.0-1005.5","6.8.0-1006.6","6.8.0-1007.7","6.8.0-1008.8","6.8.0-1009.9","6.8.0-1010.10","6.8.0-1011.11","6.8.0-1012.12","6.8.0-1013.13","6.8.0-1014.14","6.8.0-1015.15","6.8.0-1016.16","6.8.0-1017.17","6.8.0-1018.18","6.8.0-1019.19","6.8.0-1022.22","6.8.0-1023.23","6.8.0-1024.24","6.8.0-1025.25"]},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-lowlatency","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-60.63.1"}]}],"versions":["6.5.0-9.9.1","6.6.0-14.14.1","6.8.0-7.7.1","6.8.0-25.25.3","6.8.0-28.28.1","6.8.0-31.31.1","6.8.0-35.35.1","6.8.0-36.36.1","6.8.0-38.38.1","6.8.0-39.39.1","6.8.0-40.40.1","6.8.0-41.41.1","6.8.0-44.44.1","6.8.0-45.45.1","6.8.0-47.47.1","6.8.0-48.48.3","6.8.0-49.49.1","6.8.0-50.51.1","6.8.0-51.52.1","6.8.0-52.53.1","6.8.0-53.55.2","6.8.0-54.56.1","6.8.0-55.57.1","6.8.0-56.58.1","6.8.0-57.59.1","6.8.0-58.60.1","6.8.0-59.61.1"]},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-nvidia","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1028.31"}]}],"versions":["6.8.0-1007.7","6.8.0-1008.8","6.8.0-1009.9","6.8.0-1010.10","6.8.0-1011.11","6.8.0-1012.12","6.8.0-1013.14","6.8.0-1014.15","6.8.0-1015.16","6.8.0-1017.19","6.8.0-1018.20","6.8.0-1019.21","6.8.0-1020.22","6.8.0-1021.23","6.8.0-1022.25","6.8.0-1023.26","6.8.0-1024.27","6.8.0-1025.28","6.8.0-1026.29","6.8.0-1027.30"]},{"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-1028.31.1"}]}],"versions":["6.8.0-1009.9.1","6.8.0-1011.11.1","6.8.0-1012.12.1","6.8.0-1013.14.1","6.8.0-1014.15.1","6.8.0-1015.16.1","6.8.0-1017.19.1","6.8.0-1018.20.1","6.8.0-1019.21.1","6.8.0-1020.22.1","6.8.0-1021.23.1","6.8.0-1022.25.2","6.8.0-1023.26.1","6.8.0-1024.27.1","6.8.0-1025.28.1","6.8.0-1026.29.1","6.8.0-1027.30.1"]},{"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-1017.17"}]}],"versions":["6.11.0-1007.7","6.11.0-1008.8","6.11.0-1009.9","6.11.0-1010.10","6.11.0-1011.11","6.11.0-1012.12","6.11.0-1013.13","6.11.0-1015.15","6.11.0-1016.16"]},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-oem-6.8","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1028.28"}]}],"versions":["6.8.0-1003.3","6.8.0-1004.4","6.8.0-1005.5","6.8.0-1006.6","6.8.0-1007.7","6.8.0-1008.8","6.8.0-1009.9","6.8.0-1010.10","6.8.0-1011.11","6.8.0-1012.12","6.8.0-1013.13","6.8.0-1014.14","6.8.0-1016.16","6.8.0-1017.17","6.8.0-1018.18","6.8.0-1019.19","6.8.0-1020.20","6.8.0-1024.24","6.8.0-1025.25","6.8.0-1026.26","6.8.0-1027.27"]},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-oracle","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1026.27"}]}],"versions":["6.5.0-1010.10","6.6.0-1001.1","6.8.0-1001.1","6.8.0-1004.4","6.8.0-1005.5","6.8.0-1006.6","6.8.0-1008.8","6.8.0-1010.10","6.8.0-1011.11","6.8.0-1012.12","6.8.0-1013.13","6.8.0-1014.14","6.8.0-1015.16","6.8.0-1016.17","6.8.0-1017.18","6.8.0-1018.19","6.8.0-1019.20","6.8.0-1020.21","6.8.0-1021.22","6.8.0-1022.23","6.8.0-1023.24","6.8.0-1024.25","6.8.0-1025.26"]},{"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-60.63.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","6.8.0-58.60.1","6.8.0-59.61.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-1022.23"}]}],"versions":["6.8.0-1008.19","6.8.1-1001.1","6.8.1-1002.2","6.8.1-1003.3","6.8.1-1004.4","6.8.1-1005.5","6.8.1-1006.6","6.8.1-1007.7","6.8.1-1008.8","6.8.1-1009.9","6.8.1-1010.10","6.8.1-1011.11","6.8.1-1012.12","6.8.1-1013.14","6.8.1-1014.15","6.8.1-1015.16","6.8.1-1016.17","6.8.1-1017.18","6.8.1-1018.19","6.8.1-1019.20","6.8.1-1020.21","6.8.1-1021.22"]},{"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-hwe-6.11","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.11.0-21.21~24.04.1"}]}],"versions":["6.11.0-17.17~24.04.2","6.11.0-19.19~24.04.1"],"bundled":308},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-lowlatency-hwe-6.11","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.11.0-1011.12~24.04.1"}]}],"versions":["6.11.0-1009.10~24.04.1"],"bundled":311},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-oem-6.11","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.11.0-1017.17"}]}],"versions":["6.11.0-1007.7","6.11.0-1008.8","6.11.0-1009.9","6.11.0-1010.10","6.11.0-1011.11","6.11.0-1012.12","6.11.0-1013.13","6.11.0-1015.15","6.11.0-1016.16"],"bundled":307},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-aws-6.8","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1029.31~22.04.1"}]}],"versions":["6.8.0-1009.9~22.04.2","6.8.0-1010.10~22.04.2","6.8.0-1011.12~22.04.1","6.8.0-1013.14~22.04.1","6.8.0-1014.15~22.04.1","6.8.0-1015.16~22.04.1","6.8.0-1016.17~22.04.2","6.8.0-1017.18~22.04.1","6.8.0-1018.19~22.04.1","6.8.0-1019.21~22.04.1","6.8.0-1020.22~22.04.1","6.8.0-1021.23~22.04.1","6.8.0-1023.25~22.04.1","6.8.0-1024.26~22.04.1","6.8.0-1027.29~22.04.1","6.8.0-1028.30~22.04.1"],"bundled":133},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-lowlatency-hwe-6.8","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-60.63.1~22.04.1"}]}],"versions":["6.8.0-38.38.1~22.04.2","6.8.0-40.40.1~22.04.1","6.8.0-44.44.1~22.04.1","6.8.0-45.45.1~22.04.1","6.8.0-47.47.1~22.04.1","6.8.0-48.48.3~22.04.1","6.8.0-49.49.1~22.04.1","6.8.0-50.51.1~22.04.1","6.8.0-51.52.1~22.04.1","6.8.0-52.53.1~22.04.1","6.8.0-54.56.1~22.04.1","6.8.0-55.57.1~22.04.1","6.8.0-56.58.1~22.04.1","6.8.0-57.59.1~22.04.1","6.8.0-58.60.1~22.04.1","6.8.0-59.61.1~22.04.1"],"bundled":133},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-60.63"}]}],"versions":["6.5.0-9.9","6.6.0-14.14","6.8.0-11.11","6.8.0-20.20","6.8.0-22.22","6.8.0-28.28","6.8.0-31.31","6.8.0-35.35","6.8.0-36.36","6.8.0-38.38","6.8.0-39.39","6.8.0-40.40","6.8.0-41.41","6.8.0-44.44","6.8.0-45.45","6.8.0-47.47","6.8.0-48.48","6.8.0-49.49","6.8.0-50.51","6.8.0-51.52","6.8.0-52.53","6.8.0-53.55","6.8.0-54.56","6.8.0-55.57","6.8.0-56.58","6.8.0-57.59","6.8.0-58.60","6.8.0-59.61"],"bundled":133},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-aws","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1029.31"}]}],"versions":["6.5.0-1008.8","6.6.0-1001.1","6.8.0-1001.1","6.8.0-1006.6","6.8.0-1008.8","6.8.0-1009.9","6.8.0-1010.10","6.8.0-1011.12","6.8.0-1012.13","6.8.0-1013.14","6.8.0-1014.15","6.8.0-1015.16","6.8.0-1016.17","6.8.0-1017.18","6.8.0-1018.20","6.8.0-1019.21","6.8.0-1020.22","6.8.0-1021.23","6.8.0-1023.25","6.8.0-1024.26","6.8.0-1025.27","6.8.0-1026.28","6.8.0-1027.29","6.8.0-1028.30"],"bundled":133},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-ibm","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1026.26"}]}],"versions":["6.5.0-1009.9","6.8.0-1001.1","6.8.0-1003.3","6.8.0-1004.4","6.8.0-1005.5","6.8.0-1006.6","6.8.0-1007.7","6.8.0-1008.8","6.8.0-1009.9","6.8.0-1010.10","6.8.0-1011.11","6.8.0-1012.12","6.8.0-1013.13","6.8.0-1014.14","6.8.0-1015.15","6.8.0-1016.16","6.8.0-1017.17","6.8.0-1018.18","6.8.0-1019.19","6.8.0-1022.22","6.8.0-1023.23","6.8.0-1024.24","6.8.0-1025.25"],"bundled":133},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-lowlatency","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-60.63.1"}]}],"versions":["6.5.0-9.9.1","6.6.0-14.14.1","6.8.0-7.7.1","6.8.0-25.25.3","6.8.0-28.28.1","6.8.0-31.31.1","6.8.0-35.35.1","6.8.0-36.36.1","6.8.0-38.38.1","6.8.0-39.39.1","6.8.0-40.40.1","6.8.0-41.41.1","6.8.0-44.44.1","6.8.0-45.45.1","6.8.0-47.47.1","6.8.0-48.48.3","6.8.0-49.49.1","6.8.0-50.51.1","6.8.0-51.52.1","6.8.0-52.53.1","6.8.0-53.55.2","6.8.0-54.56.1","6.8.0-55.57.1","6.8.0-56.58.1","6.8.0-57.59.1","6.8.0-58.60.1","6.8.0-59.61.1"],"bundled":133},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-oracle","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1026.27"}]}],"versions":["6.5.0-1010.10","6.6.0-1001.1","6.8.0-1001.1","6.8.0-1004.4","6.8.0-1005.5","6.8.0-1006.6","6.8.0-1008.8","6.8.0-1010.10","6.8.0-1011.11","6.8.0-1012.12","6.8.0-1013.13","6.8.0-1014.14","6.8.0-1015.16","6.8.0-1016.17","6.8.0-1017.18","6.8.0-1018.19","6.8.0-1019.20","6.8.0-1020.21","6.8.0-1021.22","6.8.0-1022.23","6.8.0-1023.24","6.8.0-1024.25","6.8.0-1025.26"],"bundled":133},{"source":"osv","ecosystem":"Ubuntu:Pro:Realtime:24.04:LTS","package":"linux-realtime","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.1-1022.23"}]}],"versions":["6.8.0-1008.19","6.8.1-1001.1","6.8.1-1002.2","6.8.1-1003.3","6.8.1-1004.4","6.8.1-1005.5","6.8.1-1006.6","6.8.1-1007.7","6.8.1-1008.8","6.8.1-1009.9","6.8.1-1010.10","6.8.1-1011.11","6.8.1-1012.12","6.8.1-1013.14","6.8.1-1014.15","6.8.1-1015.16","6.8.1-1016.17","6.8.1-1017.18","6.8.1-1018.19","6.8.1-1019.20","6.8.1-1020.21","6.8.1-1021.22"],"bundled":133},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-azure-6.8","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1029.34~22.04.1"}]}],"versions":["6.8.0-1008.8~22.04.1","6.8.0-1009.9~22.04.1","6.8.0-1010.10~22.04.1","6.8.0-1012.14~22.04.1","6.8.0-1013.15~22.04.1","6.8.0-1014.16~22.04.1","6.8.0-1015.17~22.04.2","6.8.0-1017.20~22.04.1","6.8.0-1018.21~22.04.1","6.8.0-1020.23~22.04.1","6.8.0-1021.25~22.04.1","6.8.0-1025.30~22.04.1","6.8.0-1026.31~22.04.1","6.8.0-1027.32~22.04.1","6.8.0-1028.33~22.04.1"],"bundled":133},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-azure","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1029.34"}]}],"versions":["6.5.0-1007.7","6.6.0-1001.1","6.8.0-1001.1","6.8.0-1005.5","6.8.0-1006.6","6.8.0-1007.7","6.8.0-1008.8","6.8.0-1009.9","6.8.0-1010.10","6.8.0-1012.14","6.8.0-1013.15","6.8.0-1014.16","6.8.0-1015.17","6.8.0-1016.18","6.8.0-1017.20","6.8.0-1018.21","6.8.0-1020.23","6.8.0-1021.25","6.8.0-1025.30","6.8.0-1026.31","6.8.0-1027.32","6.8.0-1028.33"],"bundled":133},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-oem-6.8","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1028.28"}]}],"versions":["6.8.0-1003.3","6.8.0-1004.4","6.8.0-1005.5","6.8.0-1006.6","6.8.0-1007.7","6.8.0-1008.8","6.8.0-1009.9","6.8.0-1010.10","6.8.0-1011.11","6.8.0-1012.12","6.8.0-1013.13","6.8.0-1014.14","6.8.0-1016.16","6.8.0-1017.17","6.8.0-1018.18","6.8.0-1019.19","6.8.0-1020.20","6.8.0-1024.24","6.8.0-1025.25","6.8.0-1026.26","6.8.0-1027.27"],"bundled":133},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-hwe-6.8","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-60.63~22.04.1"}]}],"versions":["6.8.0-38.38~22.04.1","6.8.0-39.39~22.04.1","6.8.0-40.40~22.04.3","6.8.0-45.45~22.04.1","6.8.0-47.47~22.04.1","6.8.0-48.48~22.04.1","6.8.0-49.49~22.04.1","6.8.0-50.51~22.04.1","6.8.0-51.52~22.04.1","6.8.0-52.53~22.04.1","6.8.0-57.59~22.04.1","6.8.0-58.60~22.04.1","6.8.0-59.61~22.04.1"],"bundled":133},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-oracle-6.8","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1026.27~22.04.1"}]}],"versions":["6.8.0-1006.6~22.04.3","6.8.0-1008.8~22.04.1","6.8.0-1010.10~22.04.1","6.8.0-1011.11~22.04.1","6.8.0-1012.12~22.04.1","6.8.0-1013.13~22.04.1","6.8.0-1014.14~22.04.1","6.8.0-1015.15~22.04.1","6.8.0-1016.17~22.04.1","6.8.0-1017.18~22.04.1","6.8.0-1018.19~22.04.1","6.8.0-1019.20~22.04.1","6.8.0-1020.21~22.04.1","6.8.0-1021.22~22.04.1","6.8.0-1022.23~22.04.1","6.8.0-1023.24~22.04.1","6.8.0-1024.25~22.04.1","6.8.0-1025.26~22.04.1"],"bundled":133},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-nvidia-6.8","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1028.31~22.04.1"}]}],"versions":["6.8.0-1008.8~22.04.1","6.8.0-1009.9~22.04.1","6.8.0-1010.10~22.04.1","6.8.0-1011.11~22.04.1","6.8.0-1012.12~22.04.1","6.8.0-1013.14~22.04.1","6.8.0-1014.15~22.04.1","6.8.0-1015.16~22.04.1","6.8.0-1017.19~22.04.1","6.8.0-1018.20~22.04.1","6.8.0-1019.21~22.04.1","6.8.0-1020.22~22.04.1","6.8.0-1021.23~22.04.1","6.8.0-1022.25~22.04.2","6.8.0-1023.26~22.04.1","6.8.0-1024.27~22.04.1","6.8.0-1025.28~22.04.1","6.8.0-1026.29~22.04.1","6.8.0-1027.30~22.04.1"],"bundled":134},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-nvidia","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1028.31"}]}],"versions":["6.8.0-1007.7","6.8.0-1008.8","6.8.0-1009.9","6.8.0-1010.10","6.8.0-1011.11","6.8.0-1012.12","6.8.0-1013.14","6.8.0-1014.15","6.8.0-1015.16","6.8.0-1017.19","6.8.0-1018.20","6.8.0-1019.21","6.8.0-1020.22","6.8.0-1021.23","6.8.0-1022.25","6.8.0-1023.26","6.8.0-1024.27","6.8.0-1025.28","6.8.0-1026.29","6.8.0-1027.30"],"bundled":134},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-nvidia-lowlatency","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1028.31.1"}]}],"versions":["6.8.0-1009.9.1","6.8.0-1011.11.1","6.8.0-1012.12.1","6.8.0-1013.14.1","6.8.0-1014.15.1","6.8.0-1015.16.1","6.8.0-1017.19.1","6.8.0-1018.20.1","6.8.0-1019.21.1","6.8.0-1020.22.1","6.8.0-1021.23.1","6.8.0-1022.25.2","6.8.0-1023.26.1","6.8.0-1024.27.1","6.8.0-1025.28.1","6.8.0-1026.29.1","6.8.0-1027.30.1"],"bundled":134},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-gke","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1025.29"}]}],"versions":["6.8.0-1003.5","6.8.0-1004.7","6.8.0-1005.8","6.8.0-1006.9","6.8.0-1007.10","6.8.0-1008.11","6.8.0-1009.12","6.8.0-1010.13","6.8.0-1011.14","6.8.0-1012.15","6.8.0-1013.17","6.8.0-1014.18","6.8.0-1015.19","6.8.0-1016.20","6.8.0-1017.21","6.8.0-1019.23","6.8.0-1020.24","6.8.0-1021.25","6.8.0-1022.26","6.8.0-1023.27","6.8.0-1024.28"],"bundled":134},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-gcp-6.8","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1030.32~22.04.1"}]}],"versions":["6.8.0-1010.11~22.04.1","6.8.0-1011.12~22.04.1","6.8.0-1012.13~22.04.1","6.8.0-1013.14~22.04.1","6.8.0-1014.16~22.04.1","6.8.0-1015.17~22.04.1","6.8.0-1016.18~22.04.1","6.8.0-1017.19~22.04.1","6.8.0-1018.20~22.04.1","6.8.0-1019.21~22.04.1","6.8.0-1020.22~22.04.1","6.8.0-1021.23~22.04.1","6.8.0-1024.26~22.04.1","6.8.0-1025.27~22.04.1","6.8.0-1026.28~22.04.1","6.8.0-1027.29~22.04.1","6.8.0-1028.30~22.04.1","6.8.0-1029.31~22.04.1"],"bundled":134},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-gcp","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1030.32"}]}],"versions":["6.5.0-1007.7","6.6.0-1001.1","6.8.0-1002.2","6.8.0-1005.5","6.8.0-1006.6","6.8.0-1007.7","6.8.0-1008.9","6.8.0-1009.10","6.8.0-1010.11","6.8.0-1011.12","6.8.0-1012.13","6.8.0-1013.14","6.8.0-1014.16","6.8.0-1015.17","6.8.0-1016.18","6.8.0-1017.19","6.8.0-1018.20","6.8.0-1019.21","6.8.0-1020.22","6.8.0-1021.23","6.8.0-1024.26","6.8.0-1025.27","6.8.0-1026.28","6.8.0-1027.29","6.8.0-1028.30","6.8.0-1029.31"],"bundled":134},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-gkeop","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1012.14"}]}],"versions":["6.8.0-1001.3","6.8.0-1002.4","6.8.0-1003.5","6.8.0-1004.6","6.8.0-1006.8","6.8.0-1007.9","6.8.0-1008.10","6.8.0-1009.11","6.8.0-1010.12","6.8.0-1011.13"],"bundled":134},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-azure-nvidia","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1016.17"}]}],"versions":["6.8.0-1013.14","6.8.0-1014.15"],"bundled":136},{"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/b1f7476e07b93d65a1a3643dcb4a7bed80d4328d","tags":["Patch","web","report"]},{"url":"https://git.kernel.org/stable/c/aed157301c659a48f5564cc4568cf0e5c8831af0","tags":["Patch","web","report"]},{"url":"https://git.kernel.org/stable/c/a60b990798eb17433d0283788280422b1bd94b18","tags":["Patch","web","report"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-56760","tags":["web","advisory"]},{"url":"https://github.com/advisories/GHSA-7vgm-4f6w-wj5f"},{"url":"https://docs.bell-sw.com/security/cves/CVE-2024-56760","tags":["advisory"]},{"url":"https://github.com/CVEProject/cvelistV5/tree/main/cves/2024/56xxx/CVE-2024-56760.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-56760","tags":["advisory"]},{"url":"https://advisories.mageia.org/MGASA-2025-0030.html","tags":["advisory"]},{"url":"https://bugs.mageia.org/show_bug.cgi?id=33961","tags":["report"]},{"url":"https://cdn.kernel.org/pub/linux/kernel/v6.x/ChangeLog-6.6.66","tags":["web"]},{"url":"https://cdn.kernel.org/pub/linux/kernel/v6.x/ChangeLog-6.6.67","tags":["web"]},{"url":"https://cdn.kernel.org/pub/linux/kernel/v6.x/ChangeLog-6.6.68","tags":["web"]},{"url":"https://cdn.kernel.org/pub/linux/kernel/v6.x/ChangeLog-6.6.69","tags":["web"]},{"url":"https://cdn.kernel.org/pub/linux/kernel/v6.x/ChangeLog-6.6.70","tags":["web"]},{"url":"https://cdn.kernel.org/pub/linux/kernel/v6.x/ChangeLog-6.6.71","tags":["web"]},{"url":"https://cdn.kernel.org/pub/linux/kernel/v6.x/ChangeLog-6.6.72","tags":["web"]},{"url":"https://cdn.kernel.org/pub/linux/kernel/v6.x/ChangeLog-6.6.73","tags":["web"]},{"url":"https://cdn.kernel.org/pub/linux/kernel/v6.x/ChangeLog-6.6.74","tags":["web"]},{"url":"https://advisories.mageia.org/MGASA-2025-0032.html","tags":["advisory"]},{"url":"https://bugs.mageia.org/show_bug.cgi?id=33968","tags":["report"]},{"url":"https://www.openeuler.org/zh/security/security-bulletins/detail/?id=openEuler-SA-2026-2417","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-56611","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-21908","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-21931","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-21970","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-21971","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-21980","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-21981","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-21986","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-21995","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-22001","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-22009","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-22071","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-22077","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-23138","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-23157","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-37740","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-37748","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-37766","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-37768","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-37770","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-37771","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-37778","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-37793","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-37805","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-37815","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-37831","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-37844","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-37853","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-37881","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-37889","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-37905","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-37918","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-37947","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-37967","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-38014","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-38037","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-38043","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-38051","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-38064","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-38113","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-38122","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-38123","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-38131","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-38148","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-38161","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-38183","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-38193","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-38194","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-38241","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-38255","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-38304","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-38307","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-38321","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-38344","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-38364","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-38461","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-38462","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-38488","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-38499","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-38552","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-38575","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-38609","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-38721","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-39676","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-39682","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-39702","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-39728","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-39756","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-39770","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-39812","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-39841","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-39894","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-39937","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-39955","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-39980","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-40018","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-40062","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-40078","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-40136","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-40240","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-40254","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-40280","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-40281","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-40331","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-68283","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-68284","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-68285","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-68304","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-68740","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-68742","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-68795","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-68820","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-71064","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-22976","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-22994","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-23053","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-23056","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-23063","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-23253","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-23260","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-23268","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-23271","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-23273","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-31447","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-43047","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-43048","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-43407","tags":["advisory"]},{"url":"https://www.openeuler.org/zh/security/security-bulletins/detail/?id=openEuler-SA-2026-2418","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-23292","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-23296","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-23313","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-23317","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-23319","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-23352","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-23359","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-23360","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-23374","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-23383","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-23388","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-43053","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-43147","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-43261","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-43289","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-43470","tags":["advisory"]},{"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-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"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-53232","tags":["advisory"]},{"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-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://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","report"]},{"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://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://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-56760","tags":["report"]},{"url":"https://git.kernel.org/linus/a60b990798eb17433d0283788280422b1bd94b18","tags":["report"]},{"url":"https://ubuntu.com/security/notices/USN-7379-1","tags":["advisory"]},{"url":"https://ubuntu.com/security/notices/USN-7380-1","tags":["advisory"]},{"url":"https://ubuntu.com/security/notices/USN-7381-1","tags":["advisory"]},{"url":"https://ubuntu.com/security/notices/USN-7382-1","tags":["advisory"]},{"url":"https://ubuntu.com/security/notices/USN-7379-2","tags":["advisory"]},{"url":"https://ubuntu.com/security/notices/USN-7513-1","tags":["advisory"]},{"url":"https://ubuntu.com/security/notices/USN-7513-2","tags":["advisory"]},{"url":"https://ubuntu.com/security/notices/USN-7514-1","tags":["advisory"]},{"url":"https://ubuntu.com/security/notices/USN-7515-1","tags":["advisory"]},{"url":"https://ubuntu.com/security/notices/USN-7513-3","tags":["advisory"]},{"url":"https://ubuntu.com/security/notices/USN-7522-1","tags":["advisory"]},{"url":"https://ubuntu.com/security/notices/USN-7515-2","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/notices/USN-7513-4","tags":["advisory"]},{"url":"https://ubuntu.com/security/notices/USN-7513-5","tags":["advisory"]},{"url":"https://ubuntu.com/security/CVE-2024-36476","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-39282","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-43098","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-47408","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-49568","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-49569","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-49571","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50051","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-51729","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-52319","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-52332","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-53179","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-53680","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-53681","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-53682","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-54191","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-54680","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-55641","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-55642","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-56368","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-56550","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56551","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56552","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-56559","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-56563","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56564","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-56582","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-56591","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-56595","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-56598","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-56614","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-56617","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56618","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-56624","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-56639","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-56646","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-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-56655","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-56663","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56664","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56665","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56667","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56669","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56670","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56671","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56673","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-56711","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56712","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56713","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56714","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-56719","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56757","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-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-56765","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56766","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56767","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56768","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-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-56784","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-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-57795","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-57798","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-57799","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-57805","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-57809","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-57838","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-57839","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-57841","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-57857","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-57875","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-57876","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-57878","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-57879","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-57880","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-57881","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-57886","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-57894","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-57905","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-57918","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-57919","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-57921","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-57924","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-57934","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-57935","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-57944","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-2025-21629","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-21633","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-21644","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-21661","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-21834","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56658","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56672","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-0927","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-38608","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-41013","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-47736","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-53125","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-58237","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-21938","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-21971","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-21888","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-44964","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-21953","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2022-49034","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-41014","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-42122","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-44955","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-47711","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-47726","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-49865","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-49893","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-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-49968","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-49972","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-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-50032","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50033","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-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-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-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-50080","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-50093","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-50101","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-50107","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50108","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-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-50120","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50121","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-50130","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50131","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-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-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-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-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-50166","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50167","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-50180","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-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-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-50215","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50216","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-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-50249","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-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-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-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-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-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-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-53050","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-53051","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-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-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-53072","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-53076","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-53079","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-53090","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-53091","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-53096","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-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-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-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-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-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-53142","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-53150","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-53151","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-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-53190","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-53191","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-53200","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-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-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-53222","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-53232","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-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-56543","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-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-56681","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56683","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-56698","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-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-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-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-2024-58099","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-53089","tags":["report"]}],"sources":{"cve":[{"id":"CVE-2024-56760","title":"PCI/MSI: Handle lack of irqdomain gracefully","description":"In the Linux kernel, the following vulnerability has been resolved:\n\nPCI/MSI: Handle lack of irqdomain gracefully\n\nAlexandre observed a warning emitted from pci_msi_setup_msi_irqs() on a\nRISCV platform which does not provide PCI/MSI support:\n\n WARNING: CPU: 1 PID: 1 at drivers/pci/msi/msi.h:121 pci_msi_setup_msi_irqs+0x2c/0x32\n __pci_enable_msix_range+0x30c/0x596\n pci_msi_setup_msi_irqs+0x2c/0x32\n pci_alloc_irq_vectors_affinity+0xb8/0xe2\n\nRISCV uses hierarchical interrupt domains and correctly does not implement\nthe legacy fallback. The warning triggers from the legacy fallback stub.\n\nThat warning is bogus as the PCI/MSI layer knows whether a PCI/MSI parent\ndomain is associated with the device or not. There is a check for MSI-X,\nwhich has a legacy assumption. But that legacy fallback assumption is only\nvalid when legacy support is enabled, but otherwise the check should simply\nreturn -ENOTSUPP.\n\nLoongarch tripped over the same problem and blindly enabled legacy support\nwithout implementing the legacy fallbacks. There are weak implementations\nwhich return an error, so the problem was papered over.\n\nCorrect pci_msi_domain_supports() to evaluate the legacy mode and add\nthe missing supported check into the MSI enable path to complete it.","status":"published","published":"2025-01-06T16:20:40.369Z","modified":"2026-05-11T20:58:33.614Z","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":"adp"}],"updated_at":"2026-11-02T14:33:57.983942Z"}],"euvd":[{"id":"EUVD-2024-53403","description":"In the Linux kernel, the following vulnerability has been resolved:\n\nPCI/MSI: Handle lack of irqdomain gracefully\n\nAlexandre observed a warning emitted from pci_msi_setup_msi_irqs() on a\nRISCV platform which does not provide PCI/MSI support:\n\n WARNING: CPU: 1 PID: 1 at drivers/pci/msi/msi.h:121 pci_msi_setup_msi_irqs+0x2c/0x32\n __pci_enable_msix_range+0x30c/0x596\n pci_msi_setup_msi_irqs+0x2c/0x32\n pci_alloc_irq_vectors_affinity+0xb8/0xe2\n\nRISCV uses hierarchical interrupt domains and correctly does not implement\nthe legacy fallback. The warning triggers from the legacy fallback stub.\n\nThat warning is bogus as the PCI/MSI layer knows whether a PCI/MSI parent\ndomain is associated with the device or not. There is a check for MSI-X,\nwhich has a legacy assumption. But that legacy fallback assumption is only\nvalid when legacy support is enabled, but otherwise the check should simply\nreturn -ENOTSUPP.\n\nLoongarch tripped over the same problem and blindly enabled legacy support\nwithout implementing the legacy fallbacks. There are weak implementations\nwhich return an error, so the problem was papered over.\n\nCorrect pci_msi_domain_supports() to evaluate the legacy mode and add\nthe missing supported check into the MSI enable path to complete it.","status":"published","published":"2025-01-06T16:20:40Z","modified":"2026-05-11T20:58:33Z","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-02T19:04:52.383818Z"}],"ghsa":[{"id":"GHSA-7vgm-4f6w-wj5f","title":"In the Linux kernel, the following vulnerability has been resolved:\n\nPCI/MSI: Handle lack of...","description":"In the Linux kernel, the following vulnerability has been resolved:\n\nPCI/MSI: Handle lack of irqdomain gracefully\n\nAlexandre observed a warning emitted from pci_msi_setup_msi_irqs() on a\nRISCV platform which does not provide PCI/MSI support:\n\n WARNING: CPU: 1 PID: 1 at drivers/pci/msi/msi.h:121 pci_msi_setup_msi_irqs+0x2c/0x32\n __pci_enable_msix_range+0x30c/0x596\n pci_msi_setup_msi_irqs+0x2c/0x32\n pci_alloc_irq_vectors_affinity+0xb8/0xe2\n\nRISCV uses hierarchical interrupt domains and correctly does not implement\nthe legacy fallback. The warning triggers from the legacy fallback stub.\n\nThat warning is bogus as the PCI/MSI layer knows whether a PCI/MSI parent\ndomain is associated with the device or not. There is a check for MSI-X,\nwhich has a legacy assumption. But that legacy fallback assumption is only\nvalid when legacy support is enabled, but otherwise the check should simply\nreturn -ENOTSUPP.\n\nLoongarch tripped over the same problem and blindly enabled legacy support\nwithout implementing the legacy fallbacks. There are weak implementations\nwhich return an error, so the problem was papered over.\n\nCorrect pci_msi_domain_supports() to evaluate the legacy mode and add\nthe missing supported check into the MSI enable path to complete it.","status":"published","published":"2025-01-06T18:31:03Z","modified":"2025-01-08T00:30:49Z","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-02T14:59:25.155575Z"}],"nvd":[{"id":"CVE-2024-56760","description":"In the Linux kernel, the following vulnerability has been resolved:\n\nPCI/MSI: Handle lack of irqdomain gracefully\n\nAlexandre observed a warning emitted from pci_msi_setup_msi_irqs() on a\nRISCV platform which does not provide PCI/MSI support:\n\n WARNING: CPU: 1 PID: 1 at drivers/pci/msi/msi.h:121 pci_msi_setup_msi_irqs+0x2c/0x32\n __pci_enable_msix_range+0x30c/0x596\n pci_msi_setup_msi_irqs+0x2c/0x32\n pci_alloc_irq_vectors_affinity+0xb8/0xe2\n\nRISCV uses hierarchical interrupt domains and correctly does not implement\nthe legacy fallback. The warning triggers from the legacy fallback stub.\n\nThat warning is bogus as the PCI/MSI layer knows whether a PCI/MSI parent\ndomain is associated with the device or not. There is a check for MSI-X,\nwhich has a legacy assumption. But that legacy fallback assumption is only\nvalid when legacy support is enabled, but otherwise the check should simply\nreturn -ENOTSUPP.\n\nLoongarch tripped over the same problem and blindly enabled legacy support\nwithout implementing the legacy fallbacks. There are weak implementations\nwhich return an error, so the problem was papered over.\n\nCorrect pci_msi_domain_supports() to evaluate the legacy mode and add\nthe missing supported check into the MSI enable path to complete it.","status":"published","published":"2025-01-06T17:15:41.173Z","modified":"2026-06-17T08:12:55.74Z","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":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":"secondary"}],"updated_at":"2026-11-02T14:10:41.489236Z"}],"osv":[{"id":"AZL-55044","title":"CVE-2024-56760 affecting package kernel for versions less than 6.6.76.1-1","description":"In the Linux kernel, the following vulnerability has been resolved:\n\nPCI/MSI: Handle lack of irqdomain gracefully\n\nAlexandre observed a warning emitted from pci_msi_setup_msi_irqs() on a\nRISCV platform which does not provide PCI/MSI support:\n\n WARNING: CPU: 1 PID: 1 at drivers/pci/msi/msi.h:121 pci_msi_setup_msi_irqs+0x2c/0x32\n __pci_enable_msix_range+0x30c/0x596\n pci_msi_setup_msi_irqs+0x2c/0x32\n pci_alloc_irq_vectors_affinity+0xb8/0xe2\n\nRISCV uses hierarchical interrupt domains and correctly does not implement\nthe legacy fallback. The warning triggers from the legacy fallback stub.\n\nThat warning is bogus as the PCI/MSI layer knows whether a PCI/MSI parent\ndomain is associated with the device or not. There is a check for MSI-X,\nwhich has a legacy assumption. But that legacy fallback assumption is only\nvalid when legacy support is enabled, but otherwise the check should simply\nreturn -ENOTSUPP.\n\nLoongarch tripped over the same problem and blindly enabled legacy support\nwithout implementing the legacy fallbacks. There are weak implementations\nwhich return an error, so the problem was papered over.\n\nCorrect pci_msi_domain_supports() to evaluate the legacy mode and add\nthe missing supported check into the MSI enable path to complete it.","status":"published","published":"2025-01-06T17:15:41Z","modified":"2026-04-21T04:47:43.14332Z","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:06.879785Z"},{"id":"BELL-CVE-2024-56760","status":"published","published":"2025-01-13T17:59:23.517997Z","modified":"2026-06-25T07:17:19.87694525Z","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:21.227396Z"},{"id":"CVE-2024-56760","title":"PCI/MSI: Handle lack of irqdomain gracefully","description":"In the Linux kernel, the following vulnerability has been resolved:\n\nPCI/MSI: Handle lack of irqdomain gracefully\n\nAlexandre observed a warning emitted from pci_msi_setup_msi_irqs() on a\nRISCV platform which does not provide PCI/MSI support:\n\n WARNING: CPU: 1 PID: 1 at drivers/pci/msi/msi.h:121 pci_msi_setup_msi_irqs+0x2c/0x32\n __pci_enable_msix_range+0x30c/0x596\n pci_msi_setup_msi_irqs+0x2c/0x32\n pci_alloc_irq_vectors_affinity+0xb8/0xe2\n\nRISCV uses hierarchical interrupt domains and correctly does not implement\nthe legacy fallback. The warning triggers from the legacy fallback stub.\n\nThat warning is bogus as the PCI/MSI layer knows whether a PCI/MSI parent\ndomain is associated with the device or not. There is a check for MSI-X,\nwhich has a legacy assumption. But that legacy fallback assumption is only\nvalid when legacy support is enabled, but otherwise the check should simply\nreturn -ENOTSUPP.\n\nLoongarch tripped over the same problem and blindly enabled legacy support\nwithout implementing the legacy fallbacks. There are weak implementations\nwhich return an error, so the problem was papered over.\n\nCorrect pci_msi_domain_supports() to evaluate the legacy mode and add\nthe missing supported check into the MSI enable path to complete it.","status":"published","published":"2025-01-06T16:20:40.369Z","modified":"2026-10-28T02:30:36.669459547Z","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:44:44.777182Z"},{"id":"DEBIAN-CVE-2024-56760","description":"In the Linux kernel, the following vulnerability has been resolved:  PCI/MSI: Handle lack of irqdomain gracefully  Alexandre observed a warning emitted from pci_msi_setup_msi_irqs() on a RISCV platform which does not provide PCI/MSI support:   WARNING: CPU: 1 PID: 1 at drivers/pci/msi/msi.h:121 pci_msi_setup_msi_irqs+0x2c/0x32  __pci_enable_msix_range+0x30c/0x596  pci_msi_setup_msi_irqs+0x2c/0x32  pci_alloc_irq_vectors_affinity+0xb8/0xe2  RISCV uses hierarchical interrupt domains and correctly does not implement the legacy fallback. The warning triggers from the legacy fallback stub.  That warning is bogus as the PCI/MSI layer knows whether a PCI/MSI parent domain is associated with the device or not. There is a check for MSI-X, which has a legacy assumption. But that legacy fallback assumption is only valid when legacy support is enabled, but otherwise the check should simply return -ENOTSUPP.  Loongarch tripped over the same problem and blindly enabled legacy support without implementing the legacy fallbacks. There are weak implementations which return an error, so the problem was papered over.  Correct pci_msi_domain_supports() to evaluate the legacy mode and add the missing supported check into the MSI enable path to complete it.","status":"published","published":"2025-01-06T17:15:41.173Z","modified":"2026-11-02T12:03:10.414998716Z","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.429177Z"},{"id":"OESA-2026-2417","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:mm/mempolicy: fix migrate_to_node() assuming there is at least one VMA in a MMWe currently assume that there is at least one VMA in a MM, which isn ttrue.So we might end up having find_vma() return NULL, to then de-referenceNULL.  So properly handle find_vma() returning NULL.This fixes the report:Oops: general protection fault, probably for non-canonical address 0xdffffc0000000000: 0000 [#1] PREEMPT SMP KASAN PTIKASAN: null-ptr-deref in range [0x0000000000000000-0x0000000000000007]CPU: 1 UID: 0 PID: 6021 Comm: syz-executor284 Not tainted 6.12.0-rc7-syzkaller-00187-gf868cd251776 #0Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 10/30/2024RIP: 0010:migrate_to_node mm/mempolicy.c:1090 [inline]RIP: 0010:do_migrate_pages+0x403/0x6f0 mm/mempolicy.c:1194Code: ...RSP: 0018:ffffc9000375fd08 EFLAGS: 00010246RAX: 0000000000000000 RBX: ffffc9000375fd78 RCX: 0000000000000000RDX: ffff88807e171300 RSI: dffffc0000000000 RDI: ffff88803390c044RBP: ffff88807e171428 R08: 0000000000000014 R09: fffffbfff2039ef1R10: ffffffff901cf78f R11: 0000000000000000 R12: 0000000000000003R13: ffffc9000375fe90 R14: ffffc9000375fe98 R15: ffffc9000375fdf8FS:  00005555919e1380(0000) GS:ffff8880b8700000(0000) knlGS:0000000000000000CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033CR2: 00005555919e1ca8 CR3: 000000007f12a000 CR4: 00000000003526f0DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400Call Trace: \u0026lt;TASK\u0026gt; kernel_migrate_pages+0x5b2/0x750 mm/mempolicy.c:1709 __do_sys_migrate_pages mm/mempolicy.c:1727 [inline] __se_sys_migrate_pages mm/mempolicy.c:1723 [inline] __x64_sys_migrate_pages+0x96/0x100 mm/mempolicy.c:1723 do_syscall_x64 arch/x86/entry/common.c:52 [inline] do_syscall_64+0xcd/0x250 arch/x86/entry/common.c:83 entry_SYSCALL_64_after_hwframe+0x77/0x7f[akpm@linux-foundation.org: add unlikely()](CVE-2024-56611)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nPCI/MSI: Handle lack of irqdomain gracefully\n\nAlexandre observed a warning emitted from pci_msi_setup_msi_irqs() on a\nRISCV platform which does not provide PCI/MSI support:\n\n WARNING: CPU: 1 PID: 1 at drivers/pci/msi/msi.h:121 pci_msi_setup_msi_irqs+0x2c/0x32\n __pci_enable_msix_range+0x30c/0x596\n pci_msi_setup_msi_irqs+0x2c/0x32\n pci_alloc_irq_vectors_affinity+0xb8/0xe2\n\nRISCV uses hierarchical interrupt domains and correctly does not implement\nthe legacy fallback. The warning triggers from the legacy fallback stub.\n\nThat warning is bogus as the PCI/MSI layer knows whether a PCI/MSI parent\ndomain is associated with the device or not. There is a check for MSI-X,\nwhich has a legacy assumption. But that legacy fallback assumption is only\nvalid when legacy support is enabled, but otherwise the check should simply\nreturn -ENOTSUPP.\n\nLoongarch tripped over the same problem and blindly enabled legacy support\nwithout implementing the legacy fallbacks. There are weak implementations\nwhich return an error, so the problem was papered over.\n\nCorrect pci_msi_domain_supports() to evaluate the legacy mode and add\nthe missing supported check into the MSI enable path to complete it.(CVE-2024-56760)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nNFS: fix nfs_release_folio() to not deadlock via kcompactd writeback\n\nAdd PF_KCOMPACTD flag and current_is_kcompactd() helper to check for it so\nnfs_release_folio() can skip calling nfs_wb_folio() from kcompactd.\n\nOtherwise NFS can deadlock waiting for kcompactd enduced writeback which\nrecurses back to NFS (which triggers writeback to NFSD via NFS loopback\nmount on the same host, NFSD blocks waiting for XFS\u0026apos;s call to\n__filemap_get_folio):\n\n6070.550357] INFO: task kcompactd0:58 blocked for more than 4435 seconds.\n\n{---\n[58] \u0026quot;kcompactd0\u0026quot;\n[\u0026lt;0\u0026gt;] folio_wait_bit+0xe8/0x200\n[\u0026lt;0\u0026gt;] folio_wait_writeback+0x2b/0x80\n[\u0026lt;0\u0026gt;] nfs_wb_folio+0x80/0x1b0 [nfs]\n[\u0026lt;0\u0026gt;] nfs_release_folio+0x68/0x130 [nfs]\n[\u0026lt;0\u0026gt;] split_huge_page_to_list_to_order+0x362/0x840\n[\u0026lt;0\u0026gt;] migrate_pages_batch+0x43d/0xb90\n[\u0026lt;0\u0026gt;] migrate_pages_sync+0x9a/0x240\n[\u0026lt;0\u0026gt;] migrate_pages+0x93c/0x9f0\n[\u0026lt;0\u0026gt;] compact_zone+0x8e2/0x1030\n[\u0026lt;0\u0026gt;] compact_node+0xdb/0x120\n[\u0026lt;0\u0026gt;] kcompactd+0x121/0x2e0\n[\u0026lt;0\u0026gt;] kthread+0xcf/0x100\n[\u0026lt;0\u0026gt;] ret_from_fork+0x31/0x40\n[\u0026lt;0\u0026gt;] ret_from_fork_asm+0x1a/0x30\n---}\n\n[(CVE-2025-21908)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nhwpoison, memory_hotplug: lock folio before unmap hwpoisoned folio\n\nCommit b15c87263a69 (\u0026quot;hwpoison, memory_hotplug: allow hwpoisoned pages to\nbe offlined) add page poison checks in do_migrate_range in order to make\noffline hwpoisoned page possible by introducing isolate_lru_page and\ntry_to_unmap for hwpoisoned page.  However folio lock must be held before\ncalling try_to_unmap.  Add it to fix this problem.\n\nWarning will be produced if folio is not locked during unmap:\n\n  ------------[ cut here ]------------\n  kernel BUG at ./include/linux/swapops.h:400!\n  Internal error: Oops - BUG: 00000000f2000800 [#1] PREEMPT SMP\n  Modules linked in:\n  CPU: 4 UID: 0 PID: 411 Comm: bash Tainted: G        W          6.13.0-rc1-00016-g3c434c7ee82a-dirty #41\n  Tainted: [W]=WARN\n  Hardware name: QEMU QEMU Virtual Machine, BIOS 0.0.0 02/06/2015\n  pstate: 40400005 (nZcv daif +PAN -UAO -TCO -DIT -SSBS BTYPE=--)\n  pc : try_to_unmap_one+0xb08/0xd3c\n  lr : try_to_unmap_one+0x3dc/0xd3c\n  Call trace:\n   try_to_unmap_one+0xb08/0xd3c (P)\n   try_to_unmap_one+0x3dc/0xd3c (L)\n   rmap_walk_anon+0xdc/0x1f8\n   rmap_walk+0x3c/0x58\n   try_to_unmap+0x88/0x90\n   unmap_poisoned_folio+0x30/0xa8\n   do_migrate_range+0x4a0/0x568\n   offline_pages+0x5a4/0x670\n   memory_block_action+0x17c/0x374\n   memory_subsys_offline+0x3c/0x78\n   device_offline+0xa4/0xd0\n   state_store+0x8c/0xf0\n   dev_attr_store+0x18/0x2c\n   sysfs_kf_write+0x44/0x54\n   kernfs_fop_write_iter+0x118/0x1a8\n   vfs_write+0x3a8/0x4bc\n   ksys_write+0x6c/0xf8\n   __arm64_sys_write+0x1c/0x28\n   invoke_syscall+0x44/0x100\n   el0_svc_common.constprop.0+0x40/0xe0\n   do_el0_svc+0x1c/0x28\n   el0_svc+0x30/0xd0\n   el0t_64_sync_handler+0xc8/0xcc\n   el0t_64_sync+0x198/0x19c\n  Code: f9407be0 b5fff320 d4210000 17ffff97 (d4210000)\n  ---[ end trace 0000000000000000 ]---(CVE-2025-21931)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnet/mlx5: Bridge, fix the crash caused by LAG state check\n\nWhen removing LAG device from bridge, NETDEV_CHANGEUPPER event is\ntriggered. Driver finds the lower devices (PFs) to flush all the\noffloaded entries. And mlx5_lag_is_shared_fdb is checked, it returns\nfalse if one of PF is unloaded. In such case,\nmlx5_esw_bridge_lag_rep_get() and its caller return NULL, instead of\nthe alive PF, and the flush is skipped.\n\nBesides, the bridge fdb entry\u0026apos;s lastuse is updated in mlx5 bridge\nevent handler. But this SWITCHDEV_FDB_ADD_TO_BRIDGE event can be\nignored in this case because the upper interface for bond is deleted,\nand the entry will never be aged because lastuse is never updated.\n\nTo make things worse, as the entry is alive, mlx5 bridge workqueue\nkeeps sending that event, which is then handled by kernel bridge\nnotifier. It causes the following crash when accessing the passed bond\nnetdev which is already destroyed.\n\nTo fix this issue, remove such checks. LAG state is already checked in\ncommit 15f8f168952f (\u0026quot;net/mlx5: Bridge, verify LAG state when adding\nbond to bridge\u0026quot;), driver still need to skip offload if LAG becomes\ninvalid state after initialization.\n\n Oops: stack segment: 0000 [#1] SMP\n CPU: 3 UID: 0 PID: 23695 Comm: kworker/u40:3 Tainted: G           OE      6.11.0_mlnx #1\n Tainted: [O]=OOT_MODULE, [E]=UNSIGNED_MODULE\n Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS rel-1.13.0-0-gf21b5a4aeb02-prebuilt.qemu.org 04/01/2014\n Workqueue: mlx5_bridge_wq mlx5_esw_bridge_update_work [mlx5_core]\n RIP: 0010:br_switchdev_event+0x2c/0x110 [bridge]\n Code: 44 00 00 48 8b 02 48 f7 00 00 02 00 00 74 69 41 54 55 53 48 83 ec 08 48 8b a8 08 01 00 00 48 85 ed 74 4a 48 83 fe 02 48 89 d3 \u0026lt;4c\u0026gt; 8b 65 00 74 23 76 49 48 83 fe 05 74 7e 48 83 fe 06 75 2f 0f b7\n RSP: 0018:ffffc900092cfda0 EFLAGS: 00010297\n RAX: ffff888123bfe000 RBX: ffffc900092cfe08 RCX: 00000000ffffffff\n RDX: ffffc900092cfe08 RSI: 0000000000000001 RDI: ffffffffa0c585f0\n RBP: 6669746f6e690a30 R08: 0000000000000000 R09: ffff888123ae92c8\n R10: 0000000000000000 R11: fefefefefefefeff R12: ffff888123ae9c60\n R13: 0000000000000001 R14: ffffc900092cfe08 R15: 0000000000000000\n FS:  0000000000000000(0000) GS:ffff88852c980000(0000) knlGS:0000000000000000\n CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033\n CR2: 00007f15914c8734 CR3: 0000000002830005 CR4: 0000000000770ef0\n DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000\n DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400\n PKRU: 55555554\n Call Trace:\n  \u0026lt;TASK\u0026gt;\n  ? __die_body+0x1a/0x60\n  ? die+0x38/0x60\n  ? do_trap+0x10b/0x120\n  ? do_error_trap+0x64/0xa0\n  ? exc_stack_segment+0x33/0x50\n  ? asm_exc_stack_segment+0x22/0x30\n  ? br_switchdev_event+0x2c/0x110 [bridge]\n  ? sched_balance_newidle.isra.149+0x248/0x390\n  notifier_call_chain+0x4b/0xa0\n  atomic_notifier_call_chain+0x16/0x20\n  mlx5_esw_bridge_update+0xec/0x170 [mlx5_core]\n  mlx5_esw_bridge_update_work+0x19/0x40 [mlx5_core]\n  process_scheduled_works+0x81/0x390\n  worker_thread+0x106/0x250\n  ? bh_worker+0x110/0x110\n  kthread+0xb7/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  \u0026lt;/TASK\u0026gt;(CVE-2025-21970)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnet_sched: Prevent creation of classes with TC_H_ROOT\n\nThe function qdisc_tree_reduce_backlog() uses TC_H_ROOT as a termination\ncondition when traversing up the qdisc tree to update parent backlog\ncounters. However, if a class is created with classid TC_H_ROOT, the\ntraversal terminates prematurely at this class instead of reaching the\nactual root qdisc, causing parent statistics to be incorrectly maintained.\nIn case of DRR, this could lead to a crash as reported by Mingi Cho.\n\nPrevent the creation of any Qdisc class with classid TC_H_ROOT\n(0xFFFFFFFF) across all qdisc types, as suggested by Jamal.(CVE-2025-21971)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nsched: address a potential NULL pointer dereference in the GRED scheduler.\n\nIf kzalloc in gred_init returns a NULL pointer, the code follows the\nerror handling path, invoking gred_destroy. This, in turn, calls\ngred_offload, where memset could receive a NULL pointer as input,\npotentially leading to a kernel crash.\n\nWhen table-\u0026gt;opt is NULL in gred_init(), gred_change_table_def()\nis not called yet, so it is not necessary to call -\u0026gt;ndo_setup_tc()\nin gred_offload().(CVE-2025-21980)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nice: fix memory leak in aRFS after reset\n\nFix aRFS (accelerated Receive Flow Steering) structures memory leak by\nadding a checker to verify if aRFS memory is already allocated while\nconfiguring VSI. aRFS objects are allocated in two cases:\n- as part of VSI initialization (at probe), and\n- as part of reset handling\n\nHowever, VSI reconfiguration executed during reset involves memory\nallocation one more time, without prior releasing already allocated\nresources. This led to the memory leak with the following signature:\n\n[root@os-delivery ~]# cat /sys/kernel/debug/kmemleak\nunreferenced object 0xff3c1ca7252e6000 (size 8192):\n  comm \u0026quot;kworker/0:0\u0026quot;, pid 8, jiffies 4296833052\n  hex dump (first 32 bytes):\n    00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................\n    00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................\n  backtrace (crc 0):\n    [\u0026lt;ffffffff991ec485\u0026gt;] __kmalloc_cache_noprof+0x275/0x340\n    [\u0026lt;ffffffffc0a6e06a\u0026gt;] ice_init_arfs+0x3a/0xe0 [ice]\n    [\u0026lt;ffffffffc09f1027\u0026gt;] ice_vsi_cfg_def+0x607/0x850 [ice]\n    [\u0026lt;ffffffffc09f244b\u0026gt;] ice_vsi_setup+0x5b/0x130 [ice]\n    [\u0026lt;ffffffffc09c2131\u0026gt;] ice_init+0x1c1/0x460 [ice]\n    [\u0026lt;ffffffffc09c64af\u0026gt;] ice_probe+0x2af/0x520 [ice]\n    [\u0026lt;ffffffff994fbcd3\u0026gt;] local_pci_probe+0x43/0xa0\n    [\u0026lt;ffffffff98f07103\u0026gt;] work_for_cpu_fn+0x13/0x20\n    [\u0026lt;ffffffff98f0b6d9\u0026gt;] process_one_work+0x179/0x390\n    [\u0026lt;ffffffff98f0c1e9\u0026gt;] worker_thread+0x239/0x340\n    [\u0026lt;ffffffff98f14abc\u0026gt;] kthread+0xcc/0x100\n    [\u0026lt;ffffffff98e45a6d\u0026gt;] ret_from_fork+0x2d/0x50\n    [\u0026lt;ffffffff98e083ba\u0026gt;] ret_from_fork_asm+0x1a/0x30\n    ...(CVE-2025-21981)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnet: switchdev: Convert blocking notification chain to a raw one\n\nA blocking notification chain uses a read-write semaphore to protect the\nintegrity of the chain. The semaphore is acquired for writing when\nadding / removing notifiers to / from the chain and acquired for reading\nwhen traversing the chain and informing notifiers about an event.\n\nIn case of the blocking switchdev notification chain, recursive\nnotifications are possible which leads to the semaphore being acquired\ntwice for reading and to lockdep warnings being generated [1].\n\nSpecifically, this can happen when the bridge driver processes a\nSWITCHDEV_BRPORT_UNOFFLOADED event which causes it to emit notifications\nabout deferred events when calling switchdev_deferred_process().\n\nFix this by converting the notification chain to a raw notification\nchain in a similar fashion to the netdev notification chain. Protect\nthe chain using the RTNL mutex by acquiring it when modifying the chain.\nEvents are always informed under the RTNL mutex, but add an assertion in\ncall_switchdev_blocking_notifiers() to make sure this is not violated in\nthe future.\n\nMaintain the \u0026quot;blocking\u0026quot; prefix as events are always emitted from process\ncontext and listeners are allowed to block.\n\n[1]:\nWARNING: possible recursive locking detected\n6.14.0-rc4-custom-g079270089484 #1 Not tainted\n--------------------------------------------\nip/52731 is trying to acquire lock:\nffffffff850918d8 ((switchdev_blocking_notif_chain).rwsem){++++}-{4:4}, at: blocking_notifier_call_chain+0x58/0xa0\n\nbut task is already holding lock:\nffffffff850918d8 ((switchdev_blocking_notif_chain).rwsem){++++}-{4:4}, at: blocking_notifier_call_chain+0x58/0xa0\n\nother info that might help us debug this:\nPossible unsafe locking scenario:\nCPU0\n----\nlock((switchdev_blocking_notif_chain).rwsem);\nlock((switchdev_blocking_notif_chain).rwsem);\n\n*** DEADLOCK ***\nMay be due to missing lock nesting notation\n3 locks held by ip/52731:\n #0: ffffffff84f795b0 (rtnl_mutex){+.+.}-{4:4}, at: rtnl_newlink+0x727/0x1dc0\n #1: ffffffff8731f628 (\u0026amp;net-\u0026gt;rtnl_mutex){+.+.}-{4:4}, at: rtnl_newlink+0x790/0x1dc0\n #2: ffffffff850918d8 ((switchdev_blocking_notif_chain).rwsem){++++}-{4:4}, at: blocking_notifier_call_chain+0x58/0xa0\n\nstack backtrace:\n...\n? __pfx_down_read+0x10/0x10\n? __pfx_mark_lock+0x10/0x10\n? __pfx_switchdev_port_attr_set_deferred+0x10/0x10\nblocking_notifier_call_chain+0x58/0xa0\nswitchdev_port_attr_notify.constprop.0+0xb3/0x1b0\n? __pfx_switchdev_port_attr_notify.constprop.0+0x10/0x10\n? mark_held_locks+0x94/0xe0\n? switchdev_deferred_process+0x11a/0x340\nswitchdev_port_attr_set_deferred+0x27/0xd0\nswitchdev_deferred_process+0x164/0x340\nbr_switchdev_port_unoffload+0xc8/0x100 [bridge]\nbr_switchdev_blocking_event+0x29f/0x580 [bridge]\nnotifier_call_chain+0xa2/0x440\nblocking_notifier_call_chain+0x6e/0xa0\nswitchdev_bridge_port_unoffload+0xde/0x1a0\n...(CVE-2025-21986)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ndrm/sched: Fix fence reference count leak\n\nThe last_scheduled fence leaks when an entity is being killed and adding\nthe cleanup callback fails.\n\nDecrement the reference count of prev when dma_fence_add_callback()\nfails, ensuring proper balance.\n\n[phasta: add git tag info for stable kernel](CVE-2025-21995)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\naccel/qaic: Fix integer overflow in qaic_validate_req()\n\nThese are u64 variables that come from the user via\nqaic_attach_slice_bo_ioctl().  Use check_add_overflow() to ensure that\nthe math doesn\u0026apos;t have an integer wrapping bug.(CVE-2025-22001)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nregulator: dummy: force synchronous probing\n\nSometimes I get a NULL pointer dereference at boot time in kobject_get()\nwith the following call stack:\n\nanatop_regulator_probe()\n devm_regulator_register()\n  regulator_register()\n   regulator_resolve_supply()\n    kobject_get()\n\nBy placing some extra BUG_ON() statements I could verify that this is\nraised because probing of the \u0026apos;dummy\u0026apos; regulator driver is not completed\n(\u0026apos;dummy_regulator_rdev\u0026apos; is still NULL).\n\nIn the JTAG debugger I can see that dummy_regulator_probe() and\nanatop_regulator_probe() can be run by different kernel threads\n(kworker/u4:*).  I haven\u0026apos;t further investigated whether this can be\nchanged or if there are other possibilities to force synchronization\nbetween these two probe routines.  On the other hand I don\u0026apos;t expect much\nboot time penalty by probing the \u0026apos;dummy\u0026apos; regulator synchronously.(CVE-2025-22009)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nspufs: fix a leak in spufs_create_context()\n\nLeak fixes back in 2008 missed one case - if we are trying to set affinity\nand spufs_mkdir() fails, we need to drop the reference to neighbor.(CVE-2025-22071)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nRevert \u0026quot;smb: client: fix TCP timers deadlock after rmmod\u0026quot;\n\nThis reverts commit e9f2517a3e18a54a3943c098d2226b245d488801.\n\nCommit e9f2517a3e18 (\u0026quot;smb: client: fix TCP timers deadlock after\nrmmod\u0026quot;) is intended to fix a null-ptr-deref in LOCKDEP, which is\nmentioned as CVE-2024-54680, but is actually did not fix anything;\nThe issue can be reproduced on top of it. [0]\n\nAlso, it reverted the change by commit ef7134c7fc48 (\u0026quot;smb: client:\nFix use-after-free of network namespace.\u0026quot;) and introduced a real\nissue by reviving the kernel TCP socket.\n\nWhen a reconnect happens for a CIFS connection, the socket state\ntransitions to FIN_WAIT_1.  Then, inet_csk_clear_xmit_timers_sync()\nin tcp_close() stops all timers for the socket.\n\nIf an incoming FIN packet is lost, the socket will stay at FIN_WAIT_1\nforever, and such sockets could be leaked up to net.ipv4.tcp_max_orphans.\n\nUsually, FIN can be retransmitted by the peer, but if the peer aborts\nthe connection, the issue comes into reality.\n\nI warned about this privately by pointing out the exact report [1],\nbut the bogus fix was finally merged.\n\nSo, we should not stop the timers to finally kill the connection on\nour side in that case, meaning we must not use a kernel socket for\nTCP whose sk-\u0026gt;sk_net_refcnt is 0.\n\nThe kernel socket does not have a reference to its netns to make it\npossible to tear down netns without cleaning up every resource in it.\n\nFor example, tunnel devices use a UDP socket internally, but we can\ndestroy netns without removing such devices and let it complete\nduring exit.  Otherwise, netns would be leaked when the last application\ndied.\n\nHowever, this is problematic for TCP sockets because TCP has timers to\nclose the connection gracefully even after the socket is close()d.  The\nlifetime of the socket and its netns is different from the lifetime of\nthe underlying connection.\n\nIf the socket user does not maintain the netns lifetime, the timer could\nbe fired after the socket is close()d and its netns is freed up, resulting\nin use-after-free.\n\nActually, we have seen so many similar issues and converted such sockets\nto have a reference to netns.\n\nThat\u0026apos;s why I converted the CIFS client socket to have a reference to\nnetns (sk-\u0026gt;sk_net_refcnt == 1), which is somehow mentioned as out-of-scope\nof CIFS and technically wrong in e9f2517a3e18, but **is in-scope and right\nfix**.\n\nRegarding the LOCKDEP issue, we can prevent the module unload by\nbumping the module refcount when switching the LOCKDDEP key in\nsock_lock_init_class_and_name(). [2]\n\nFor a while, let\u0026apos;s revert the bogus fix.\n\nNote that now we can use sk_net_refcnt_upgrade() for the socket\nconversion, but I\u0026apos;ll do so later separately to make backport easy.(CVE-2025-22077)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nwatch_queue: fix pipe accounting mismatch\n\nCurrently, watch_queue_set_size() modifies the pipe buffers charged to\nuser-\u0026gt;pipe_bufs without updating the pipe-\u0026gt;nr_accounted on the pipe\nitself, due to the if (!pipe_has_watch_queue()) test in\npipe_resize_ring(). This means that when the pipe is ultimately freed,\nwe decrement user-\u0026gt;pipe_bufs by something other than what than we had\ncharged to it, potentially leading to an underflow. This in turn can\ncause subsequent too_many_pipe_buffers_soft() tests to fail with -EPERM.\n\nTo remedy this, explicitly account for the pipe usage in\nwatch_queue_set_size() to match the number set via account_pipe_buffers()\n\n(It\u0026apos;s unclear why watch_queue_set_size() does not update nr_accounted;\nit may be due to intentional overprovisioning in watch_queue_set_size()?)(CVE-2025-23138)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nmedia: venus: hfi_parser: add check to avoid out of bound access\n\nThere is a possibility that init_codecs is invoked multiple times during\nmanipulated payload from video firmware. In such case, if codecs_count\ncan get incremented to value more than MAX_CODEC_NUM, there can be OOB\naccess. Reset the count so that it always starts from beginning.(CVE-2025-23157)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\njfs: add sanity check for agwidth in dbMount\n\nThe width in dmapctl of the AG is zero, it trigger a divide error when\ncalculating the control page level in dbAllocAG.\n\nTo avoid this issue, add a check for agwidth in dbAllocAG.(CVE-2025-37740)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\niommu/mediatek: Fix NULL pointer deference in mtk_iommu_device_group\n\nCurrently, mtk_iommu calls during probe iommu_device_register before\nthe hw_list from driver data is initialized. Since iommu probing issue\nfix, it leads to NULL pointer dereference in mtk_iommu_device_group when\nhw_list is accessed with list_first_entry (not null safe).\n\nSo, change the call order to ensure iommu_device_register is called\nafter the driver data are initialized.(CVE-2025-37748)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ndrm/amd/pm: Prevent division by zero\n\nThe user can set any speed value.\nIf speed is greater than UINT_MAX/8, division by zero is possible.\n\nFound by Linux Verification Center (linuxtesting.org) with SVACE.(CVE-2025-37766)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ndrm/amd/pm: Prevent division by zero\n\nThe user can set any speed value.\nIf speed is greater than UINT_MAX/8, division by zero is possible.\n\nFound by Linux Verification Center (linuxtesting.org) with SVACE.(CVE-2025-37768)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ndrm/amd/pm: Prevent division by zero\n\nThe user can set any speed value.\nIf speed is greater than UINT_MAX/8, division by zero is possible.\n\nFound by Linux Verification Center (linuxtesting.org) with SVACE.(CVE-2025-37770)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ndrm/amd/pm: Prevent division by zero\n\nThe user can set any speed value.\nIf speed is greater than UINT_MAX/8, division by zero is possible.\n\nFound by Linux Verification Center (linuxtesting.org) with SVACE.(CVE-2025-37771)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nksmbd: Fix dangling pointer in krb_authenticate\n\nkrb_authenticate frees sess-\u0026gt;user and does not set the pointer\nto NULL. It calls ksmbd_krb5_authenticate to reinitialise\nsess-\u0026gt;user but that function may return without doing so. If\nthat happens then smb2_sess_setup, which calls krb_authenticate,\nwill be accessing free\u0026apos;d memory when it later uses sess-\u0026gt;user.(CVE-2025-37778)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nASoC: Intel: avs: Fix null-ptr-deref in avs_component_probe()\n\ndevm_kasprintf() returns NULL when memory allocation fails. Currently,\navs_component_probe() does not check for this case, which results in a\nNULL pointer dereference.(CVE-2025-37793)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nsound/virtio: Fix cancel_sync warnings on uninitialized work_structs\n\nBetty reported hitting the following warning:\n\n[    8.709131][  T221] WARNING: CPU: 2 PID: 221 at kernel/workqueue.c:4182\n...\n[    8.713282][  T221] Call trace:\n[    8.713365][  T221]  __flush_work+0x8d0/0x914\n[    8.713468][  T221]  __cancel_work_sync+0xac/0xfc\n[    8.713570][  T221]  cancel_work_sync+0x24/0x34\n[    8.713667][  T221]  virtsnd_remove+0xa8/0xf8 [virtio_snd ab15f34d0dd772f6d11327e08a81d46dc9c36276]\n[    8.713868][  T221]  virtsnd_probe+0x48c/0x664 [virtio_snd ab15f34d0dd772f6d11327e08a81d46dc9c36276]\n[    8.714035][  T221]  virtio_dev_probe+0x28c/0x390\n[    8.714139][  T221]  really_probe+0x1bc/0x4c8\n...\n\nIt seems we\u0026apos;re hitting the error path in virtsnd_probe(), which\ntriggers a virtsnd_remove() which iterates over the substreams\ncalling cancel_work_sync() on the elapsed_period work_struct.\n\nLooking at the code, from earlier in:\nvirtsnd_probe()-\u0026gt;virtsnd_build_devs()-\u0026gt;virtsnd_pcm_parse_cfg()\n\nWe set snd-\u0026gt;nsubstreams, allocate the snd-\u0026gt;substreams, and if\nwe then hit an error on the info allocation or something in\nvirtsnd_ctl_query_info() fails, we will exit without having\ninitialized the elapsed_period work_struct.\n\nWhen that error path unwinds we then call virtsnd_remove()\nwhich as long as the substreams array is allocated, will iterate\nthrough calling cancel_work_sync() on the uninitialized work\nstruct hitting this warning.\n\nTakashi Iwai suggested this fix, which initializes the substreams\nstructure right after allocation, so that if we hit the error\npaths we avoid trying to cleanup uninitialized data.\n\nNote: I have not yet managed to reproduce the issue myself, so\nthis patch has had limited testing.\n\nFeedback or thoughts would be appreciated!(CVE-2025-37805)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nmisc: microchip: pci1xxxx: Fix Kernel panic during IRQ handler registration\n\nResolve kernel panic while accessing IRQ handler associated with the\ngenerated IRQ. This is done by acquiring the spinlock and storing the\ncurrent interrupt state before handling the interrupt request using\ngeneric_handle_irq.\n\nA previous fix patch was submitted where \u0026apos;generic_handle_irq\u0026apos; was\nreplaced with \u0026apos;handle_nested_irq\u0026apos;. However, this change also causes\nthe kernel panic where after determining which GPIO triggered the\ninterrupt and attempting to call handle_nested_irq with the mapped\nIRQ number, leads to a failure in locating the registered handler.(CVE-2025-37815)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ncpufreq: apple-soc: Fix null-ptr-deref in apple_soc_cpufreq_get_rate()\n\ncpufreq_cpu_get_raw() can return NULL when the target CPU is not present\nin the policy-\u0026gt;cpus mask. apple_soc_cpufreq_get_rate() does not check\nfor this case, which results in a NULL pointer dereference.(CVE-2025-37831)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ncifs: avoid NULL pointer dereference in dbg call\n\ncifs_server_dbg() implies server to be non-NULL so\nmove call under condition to avoid NULL pointer dereference.\n\nFound by Linux Verification Center (linuxtesting.org) with SVACE.(CVE-2025-37844)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ndrm/amdkfd: debugfs hang_hws skip GPU with MES\n\ndebugfs hang_hws is used by GPU reset test with HWS, for MES this crash\nthe kernel with NULL pointer access because dqm-\u0026gt;packet_mgr is not setup\nfor MES path.\n\nSkip GPU with MES for now, MES hang_hws debugfs interface will be\nsupported later.(CVE-2025-37853)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nusb: gadget: aspeed: Add NULL pointer check in ast_vhub_init_dev()\n\nThe variable d-\u0026gt;name, returned by devm_kasprintf(), could be NULL.\nA pointer check is added to prevent potential NULL pointer dereference.\nThis is similar to the fix in commit 3027e7b15b02\n(\u0026quot;ice: Fix some null pointer dereference issues in ice_ptp.c\u0026quot;).\n\nThis issue is found by our static analysis tool(CVE-2025-37881)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nASoC: ops: Consistently treat platform_max as control value\n\nThis reverts commit 9bdd10d57a88 (\u0026quot;ASoC: ops: Shift tested values in\nsnd_soc_put_volsw() by +min\u0026quot;), and makes some additional related\nupdates.\n\nThere are two ways the platform_max could be interpreted; the maximum\nregister value, or the maximum value the control can be set to. The\npatch moved from treating the value as a control value to a register\none. When the patch was applied it was technically correct as\nsnd_soc_limit_volume() also used the register interpretation. However,\neven then most of the other usages treated platform_max as a\ncontrol value, and snd_soc_limit_volume() has since been updated to\nalso do so in commit fb9ad24485087 (\u0026quot;ASoC: ops: add correct range\ncheck for limiting volume\u0026quot;). That patch however, missed updating\nsnd_soc_put_volsw() back to the control interpretation, and fixing\nsnd_soc_info_volsw_range(). The control interpretation makes more\nsense as limiting is typically done from the machine driver, so it is\nappropriate to use the customer facing representation rather than the\ninternal codec representation. Update all the code to consistently use\nthis interpretation of platform_max.\n\nFinally, also add some comments to the soc_mixer_control struct to\nhopefully avoid further patches switching between the two approaches.(CVE-2025-37889)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nfirmware: arm_scmi: Balance device refcount when destroying devices\n\nUsing device_find_child() to lookup the proper SCMI device to destroy\ncauses an unbalance in device refcount, since device_find_child() calls an\nimplicit get_device(): this, in turns, inhibits the call of the provided\nrelease methods upon devices destruction.\n\nAs a consequence, one of the structures that is not freed properly upon\ndestruction is the internal struct device_private dev-\u0026gt;p populated by the\ndrivers subsystem core.\n\nKMemleak detects this situation since loading/unloding some SCMI driver\ncauses related devices to be created/destroyed without calling any\ndevice_release method.\n\nunreferenced object 0xffff00000f583800 (size 512):\n  comm \u0026quot;insmod\u0026quot;, pid 227, jiffies 4294912190\n  hex dump (first 32 bytes):\n    00 00 00 00 ad 4e ad de ff ff ff ff 00 00 00 00  .....N..........\n    ff ff ff ff ff ff ff ff 60 36 1d 8a 00 80 ff ff  ........`6......\n  backtrace (crc 114e2eed):\n    kmemleak_alloc+0xbc/0xd8\n    __kmalloc_cache_noprof+0x2dc/0x398\n    device_add+0x954/0x12d0\n    device_register+0x28/0x40\n    __scmi_device_create.part.0+0x1bc/0x380\n    scmi_device_create+0x2d0/0x390\n    scmi_create_protocol_devices+0x74/0xf8\n    scmi_device_request_notifier+0x1f8/0x2a8\n    notifier_call_chain+0x110/0x3b0\n    blocking_notifier_call_chain+0x70/0xb0\n    scmi_driver_register+0x350/0x7f0\n    0xffff80000a3b3038\n    do_one_initcall+0x12c/0x730\n    do_init_module+0x1dc/0x640\n    load_module+0x4b20/0x5b70\n    init_module_from_file+0xec/0x158\n\n$ ./scripts/faddr2line ./vmlinux device_add+0x954/0x12d0\ndevice_add+0x954/0x12d0:\nkmalloc_noprof at include/linux/slab.h:901\n(inlined by) kzalloc_noprof at include/linux/slab.h:1037\n(inlined by) device_private_init at drivers/base/core.c:3510\n(inlined by) device_add at drivers/base/core.c:3561\n\nBalance device refcount by issuing a put_device() on devices found via\ndevice_find_child().(CVE-2025-37905)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nBluetooth: btusb: avoid NULL pointer dereference in skb_dequeue()\n\nA NULL pointer dereference can occur in skb_dequeue() when processing a\nQCA firmware crash dump on WCN7851 (0489:e0f3).\n\n[ 93.672166] Bluetooth: hci0: ACL memdump size(589824)\n\n[ 93.672475] BUG: kernel NULL pointer dereference, address: 0000000000000008\n[ 93.672517] Workqueue: hci0 hci_devcd_rx [bluetooth]\n[ 93.672598] RIP: 0010:skb_dequeue+0x50/0x80\n\nThe issue stems from handle_dump_pkt_qca() returning 0 even when a dump\npacket is successfully processed. This is because it incorrectly\nforwards the return value of hci_devcd_init() (which returns 0 on\nsuccess). As a result, the caller (btusb_recv_acl_qca() or\nbtusb_recv_evt_qca()) assumes the packet was not handled and passes it\nto hci_recv_frame(), leading to premature kfree() of the skb.\n\nLater, hci_devcd_rx() attempts to dequeue the same skb from the dump\nqueue, resulting in a NULL pointer dereference.\n\nFix this by:\n1. Making handle_dump_pkt_qca() return 0 on success and negative errno\n   on failure, consistent with kernel conventions.\n2. Splitting dump packet detection into separate functions for ACL\n   and event packets for better structure and readability.\n\nThis ensures dump packets are properly identified and consumed, avoiding\ndouble handling and preventing NULL pointer access.(CVE-2025-37918)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nksmbd: prevent out-of-bounds stream writes by validating *pos\n\nksmbd_vfs_stream_write() did not validate whether the write offset\n(*pos) was within the bounds of the existing stream data length (v_len).\nIf *pos was greater than or equal to v_len, this could lead to an\nout-of-bounds memory write.\n\nThis patch adds a check to ensure *pos is less than v_len before\nproceeding. If the condition fails, -EINVAL is returned.(CVE-2025-37947)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nusb: typec: ucsi: displayport: Fix deadlock\n\nThis patch introduces the ucsi_con_mutex_lock / ucsi_con_mutex_unlock\nfunctions to the UCSI driver. ucsi_con_mutex_lock ensures the connector\nmutex is only locked if a connection is established and the partner pointer\nis valid. This resolves a deadlock scenario where\nucsi_displayport_remove_partner holds con-\u0026gt;mutex waiting for\ndp_altmode_work to complete while dp_altmode_work attempts to acquire it.(CVE-2025-37967)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ndmaengine: idxd: Refactor remove call with idxd_cleanup() helper\n\nThe idxd_cleanup() helper cleans up perfmon, interrupts, internals and\nso on. Refactor remove call with the idxd_cleanup() helper to avoid code\nduplication. Note, this also fixes the missing put_device() for idxd\ngroups, enginces and wqs.(CVE-2025-38014)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nvxlan: Annotate FDB data races\n\nThe \u0026apos;used\u0026apos; and \u0026apos;updated\u0026apos; fields in the FDB entry structure can be\naccessed concurrently by multiple threads, leading to reports such as\n[1]. Can be reproduced using [2].\n\nSuppress these reports by annotating these accesses using\nREAD_ONCE() / WRITE_ONCE().\n\n[1]\nBUG: KCSAN: data-race in vxlan_xmit / vxlan_xmit\n\nwrite to 0xffff942604d263a8 of 8 bytes by task 286 on cpu 0:\n vxlan_xmit+0xb29/0x2380\n dev_hard_start_xmit+0x84/0x2f0\n __dev_queue_xmit+0x45a/0x1650\n packet_xmit+0x100/0x150\n packet_sendmsg+0x2114/0x2ac0\n __sys_sendto+0x318/0x330\n __x64_sys_sendto+0x76/0x90\n x64_sys_call+0x14e8/0x1c00\n do_syscall_64+0x9e/0x1a0\n entry_SYSCALL_64_after_hwframe+0x77/0x7f\n\nread to 0xffff942604d263a8 of 8 bytes by task 287 on cpu 2:\n vxlan_xmit+0xadf/0x2380\n dev_hard_start_xmit+0x84/0x2f0\n __dev_queue_xmit+0x45a/0x1650\n packet_xmit+0x100/0x150\n packet_sendmsg+0x2114/0x2ac0\n __sys_sendto+0x318/0x330\n __x64_sys_sendto+0x76/0x90\n x64_sys_call+0x14e8/0x1c00\n do_syscall_64+0x9e/0x1a0\n entry_SYSCALL_64_after_hwframe+0x77/0x7f\n\nvalue changed: 0x00000000fffbac6e -\u0026gt; 0x00000000fffbac6f\n\nReported by Kernel Concurrency Sanitizer on:\nCPU: 2 UID: 0 PID: 287 Comm: mausezahn Not tainted 6.13.0-rc7-01544-gb4b270f11a02 #5\nHardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.16.3-3.fc41 04/01/2014\n\n[2]\n #!/bin/bash\n\n set +H\n echo whitelist \u0026gt; /sys/kernel/debug/kcsan\n echo !vxlan_xmit \u0026gt; /sys/kernel/debug/kcsan\n\n ip link add name vx0 up type vxlan id 10010 dstport 4789 local 192.0.2.1\n bridge fdb add 00:11:22:33:44:55 dev vx0 self static dst 198.51.100.1\n taskset -c 0 mausezahn vx0 -a own -b 00:11:22:33:44:55 -c 0 -q \u0026amp;\n taskset -c 2 mausezahn vx0 -a own -b 00:11:22:33:44:55 -c 0 -q \u0026amp;(CVE-2025-38037)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nfirmware: arm_ffa: Set dma_mask for ffa devices\n\nSet dma_mask for FFA devices, otherwise DMA allocation using the device pointer\nlead to following warning:\n\nWARNING: CPU: 1 PID: 1 at kernel/dma/mapping.c:597 dma_alloc_attrs+0xe0/0x124(CVE-2025-38043)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nsmb: client: Fix use-after-free in cifs_fill_dirent\n\nThere is a race condition in the readdir concurrency process, which may\naccess the rsp buffer after it has been released, triggering the\nfollowing KASAN warning.\n\n ==================================================================\n BUG: KASAN: slab-use-after-free in cifs_fill_dirent+0xb03/0xb60 [cifs]\n Read of size 4 at addr ffff8880099b819c by task a.out/342975\n\n CPU: 2 UID: 0 PID: 342975 Comm: a.out Not tainted 6.15.0-rc6+ #240 PREEMPT(full)\n Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.16.1-2.fc37 04/01/2014\n Call Trace:\n  \u0026lt;TASK\u0026gt;\n  dump_stack_lvl+0x53/0x70\n  print_report+0xce/0x640\n  kasan_report+0xb8/0xf0\n  cifs_fill_dirent+0xb03/0xb60 [cifs]\n  cifs_readdir+0x12cb/0x3190 [cifs]\n  iterate_dir+0x1a1/0x520\n  __x64_sys_getdents+0x134/0x220\n  do_syscall_64+0x4b/0x110\n  entry_SYSCALL_64_after_hwframe+0x76/0x7e\n RIP: 0033:0x7f996f64b9f9\n Code: ff c3 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 44 00 00 48 89 f8 48 89\n f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 \u0026lt;48\u0026gt; 3d 01\n f0 ff ff  0d f7 c3 0c 00 f7 d8 64 89 8\n RSP: 002b:00007f996f53de78 EFLAGS: 00000207 ORIG_RAX: 000000000000004e\n RAX: ffffffffffffffda RBX: 00007f996f53ecdc RCX: 00007f996f64b9f9\n RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000000000003\n RBP: 00007f996f53dea0 R08: 0000000000000000 R09: 0000000000000000\n R10: 0000000000000000 R11: 0000000000000207 R12: ffffffffffffff88\n R13: 0000000000000000 R14: 00007ffc8cd9a500 R15: 00007f996f51e000\n  \u0026lt;/TASK\u0026gt;\n\n Allocated by task 408:\n  kasan_save_stack+0x20/0x40\n  kasan_save_track+0x14/0x30\n  __kasan_slab_alloc+0x6e/0x70\n  kmem_cache_alloc_noprof+0x117/0x3d0\n  mempool_alloc_noprof+0xf2/0x2c0\n  cifs_buf_get+0x36/0x80 [cifs]\n  allocate_buffers+0x1d2/0x330 [cifs]\n  cifs_demultiplex_thread+0x22b/0x2690 [cifs]\n  kthread+0x394/0x720\n  ret_from_fork+0x34/0x70\n  ret_from_fork_asm+0x1a/0x30\n\n Freed by task 342979:\n  kasan_save_stack+0x20/0x40\n  kasan_save_track+0x14/0x30\n  kasan_save_free_info+0x3b/0x60\n  __kasan_slab_free+0x37/0x50\n  kmem_cache_free+0x2b8/0x500\n  cifs_buf_release+0x3c/0x70 [cifs]\n  cifs_readdir+0x1c97/0x3190 [cifs]\n  iterate_dir+0x1a1/0x520\n  __x64_sys_getdents64+0x134/0x220\n  do_syscall_64+0x4b/0x110\n  entry_SYSCALL_64_after_hwframe+0x76/0x7e\n\n The buggy address belongs to the object at ffff8880099b8000\n  which belongs to the cache cifs_request of size 16588\n The buggy address is located 412 bytes inside of\n  freed 16588-byte region [ffff8880099b8000, ffff8880099bc0cc)\n\n The buggy address belongs to the physical page:\n page: refcount:0 mapcount:0 mapping:0000000000000000 index:0x0 pfn:0x99b8\n head: order:3 mapcount:0 entire_mapcount:0 nr_pages_mapped:0 pincount:0\n anon flags: 0x80000000000040(head|node=0|zone=1)\n page_type: f5(slab)\n raw: 0080000000000040 ffff888001e03400 0000000000000000 dead000000000001\n raw: 0000000000000000 0000000000010001 00000000f5000000 0000000000000000\n head: 0080000000000040 ffff888001e03400 0000000000000000 dead000000000001\n head: 0000000000000000 0000000000010001 00000000f5000000 0000000000000000\n head: 0080000000000003 ffffea0000266e01 00000000ffffffff 00000000ffffffff\n head: ffffffffffffffff 0000000000000000 00000000ffffffff 0000000000000008\n page dumped because: kasan: bad access detected\n\n Memory state around the buggy address:\n  ffff8880099b8080: fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb\n  ffff8880099b8100: fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb\n \u0026gt;ffff8880099b8180: fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb\n                             ^\n  ffff8880099b8200: fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb\n  ffff8880099b8280: fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb\n ==================================================================\n\nPOC is available in the link [1].\n\nThe problem triggering process is as follows:\n\nProcess 1                       Process 2\n-----------------------------------\n---truncated---(CVE-2025-38051)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nvirtio: break and reset virtio devices on device_shutdown()\n\nHongyu reported a hang on kexec in a VM. QEMU reported invalid memory\naccesses during the hang.\n\n\tInvalid read at addr 0x102877002, size 2, region \u0026apos;(null)\u0026apos;, reason: rejected\n\tInvalid write at addr 0x102877A44, size 2, region \u0026apos;(null)\u0026apos;, reason: rejected\n\t...\n\nIt was traced down to virtio-console. Kexec works fine if virtio-console\nis not in use.\n\nThe issue is that virtio-console continues to write to the MMIO even after\nunderlying virtio-pci device is reset.\n\nAdditionally, Eric noticed that IOMMUs are reset before devices, if\ndevices are not reset on shutdown they continue to poke at guest memory\nand get errors from the IOMMU. Some devices get wedged then.\n\nThe problem can be solved by breaking all virtio devices on virtio\nbus shutdown, then resetting them.(CVE-2025-38064)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nACPI: CPPC: Fix NULL pointer dereference when nosmp is used\n\nWith nosmp in cmdline, other CPUs are not brought up, leaving\ntheir cpc_desc_ptr NULL. CPU0\u0026apos;s iteration via for_each_possible_cpu()\ndereferences these NULL pointers, causing panic.\n\nPanic backtrace:\n\n[    0.401123] Unable to handle kernel NULL pointer dereference at virtual address 00000000000000b8\n...\n[    0.403255] [\u0026lt;ffffffff809a5818\u0026gt;] cppc_allow_fast_switch+0x6a/0xd4\n...\nKernel panic - not syncing: Attempted to kill init!\n\n[ rjw: New subject ](CVE-2025-38113)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ngve: add missing NULL check for gve_alloc_pending_packet() in TX DQO\n\ngve_alloc_pending_packet() can return NULL, but gve_tx_add_skb_dqo()\ndid not check for this case before dereferencing the returned pointer.\n\nAdd a missing NULL check to prevent a potential NULL pointer\ndereference when allocation fails.\n\nThis improves robustness in low-memory scenarios.(CVE-2025-38122)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnet: wwan: t7xx: Fix napi rx poll issue\n\nWhen driver handles the napi rx polling requests, the netdev might\nhave been released by the dellink logic triggered by the disconnect\noperation on user plane. However, in the logic of processing skb in\npolling, an invalid netdev is still being used, which causes a panic.\n\nBUG: kernel NULL pointer dereference, address: 00000000000000f1\nOops: 0000 [#1] PREEMPT SMP NOPTI\nRIP: 0010:dev_gro_receive+0x3a/0x620\n[...]\nCall Trace:\n \u0026lt;IRQ\u0026gt;\n ? __die_body+0x68/0xb0\n ? page_fault_oops+0x379/0x3e0\n ? exc_page_fault+0x4f/0xa0\n ? asm_exc_page_fault+0x22/0x30\n ? __pfx_t7xx_ccmni_recv_skb+0x10/0x10 [mtk_t7xx (HASH:1400 7)]\n ? dev_gro_receive+0x3a/0x620\n napi_gro_receive+0xad/0x170\n t7xx_ccmni_recv_skb+0x48/0x70 [mtk_t7xx (HASH:1400 7)]\n t7xx_dpmaif_napi_rx_poll+0x590/0x800 [mtk_t7xx (HASH:1400 7)]\n net_rx_action+0x103/0x470\n irq_exit_rcu+0x13a/0x310\n sysvec_apic_timer_interrupt+0x56/0x90\n \u0026lt;/IRQ\u0026gt;(CVE-2025-38123)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ncoresight: prevent deactivate active config while enabling the config\n\nWhile enable active config via cscfg_csdev_enable_active_config(),\nactive config could be deactivated via configfs\u0026apos; sysfs interface.\nThis could make UAF issue in below scenario:\n\nCPU0                                          CPU1\n(sysfs enable)                                load module\n                                              cscfg_load_config_sets()\n                                              activate config. // sysfs\n                                              (sys_active_cnt == 1)\n...\ncscfg_csdev_enable_active_config()\nlock(csdev-\u0026gt;cscfg_csdev_lock)\n// here load config activate by CPU1\nunlock(csdev-\u0026gt;cscfg_csdev_lock)\n\n                                              deactivate config // sysfs\n                                              (sys_activec_cnt == 0)\n                                              cscfg_unload_config_sets()\n                                              unload module\n\n// access to config_desc which freed\n// while unloading module.\ncscfg_csdev_enable_config\n\nTo address this, use cscfg_config_desc\u0026apos;s active_cnt as a reference count\n which will be holded when\n    - activate the config.\n    - enable the activated config.\nand put the module reference when config_active_cnt == 0.(CVE-2025-38131)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnet: phy: mscc: Fix memory leak when using one step timestamping\n\nFix memory leak when running one-step timestamping. When running\none-step sync timestamping, the HW is configured to insert the TX time\ninto the frame, so there is no reason to keep the skb anymore. As in\nthis case the HW will never generate an interrupt to say that the frame\nwas timestamped, then the frame will never released.\nFix this by freeing the frame in case of one-step timestamping.(CVE-2025-38148)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nRDMA/mlx5: Fix error flow upon firmware failure for RQ destruction\n\nUpon RQ destruction if the firmware command fails which is the\nlast resource to be destroyed some SW resources were already cleaned\nregardless of the failure.\n\nNow properly rollback the object to its original state upon such failure.\n\nIn order to avoid a use-after free in case someone tries to destroy the\nobject again, which results in the following kernel trace:\nrefcount_t: underflow; use-after-free.\nWARNING: CPU: 0 PID: 37589 at lib/refcount.c:28 refcount_warn_saturate+0xf4/0x148\nModules linked in: rdma_ucm(OE) rdma_cm(OE) iw_cm(OE) ib_ipoib(OE) ib_cm(OE) ib_umad(OE) mlx5_ib(OE) rfkill mlx5_core(OE) mlxdevm(OE) ib_uverbs(OE) ib_core(OE) psample mlxfw(OE) mlx_compat(OE) macsec tls pci_hyperv_intf sunrpc vfat fat virtio_net net_failover failover fuse loop nfnetlink vsock_loopback vmw_vsock_virtio_transport_common vmw_vsock_vmci_transport vmw_vmci vsock xfs crct10dif_ce ghash_ce sha2_ce sha256_arm64 sha1_ce virtio_console virtio_gpu virtio_blk virtio_dma_buf virtio_mmio dm_mirror dm_region_hash dm_log dm_mod xpmem(OE)\nCPU: 0 UID: 0 PID: 37589 Comm: python3 Kdump: loaded Tainted: G           OE     -------  ---  6.12.0-54.el10.aarch64 #1\nTainted: [O]=OOT_MODULE, [E]=UNSIGNED_MODULE\nHardware name: QEMU KVM Virtual Machine, BIOS 0.0.0 02/06/2015\npstate: 60400005 (nZCv daif +PAN -UAO -TCO -DIT -SSBS BTYPE=--)\npc : refcount_warn_saturate+0xf4/0x148\nlr : refcount_warn_saturate+0xf4/0x148\nsp : ffff80008b81b7e0\nx29: ffff80008b81b7e0 x28: ffff000133d51600 x27: 0000000000000001\nx26: 0000000000000000 x25: 00000000ffffffea x24: ffff00010ae80f00\nx23: ffff00010ae80f80 x22: ffff0000c66e5d08 x21: 0000000000000000\nx20: ffff0000c66e0000 x19: ffff00010ae80340 x18: 0000000000000006\nx17: 0000000000000000 x16: 0000000000000020 x15: ffff80008b81b37f\nx14: 0000000000000000 x13: 2e656572662d7265 x12: ffff80008283ef78\nx11: ffff80008257efd0 x10: ffff80008283efd0 x9 : ffff80008021ed90\nx8 : 0000000000000001 x7 : 00000000000bffe8 x6 : c0000000ffff7fff\nx5 : ffff0001fb8e3408 x4 : 0000000000000000 x3 : ffff800179993000\nx2 : 0000000000000000 x1 : 0000000000000000 x0 : ffff000133d51600\nCall trace:\n refcount_warn_saturate+0xf4/0x148\n mlx5_core_put_rsc+0x88/0xa0 [mlx5_ib]\n mlx5_core_destroy_rq_tracked+0x64/0x98 [mlx5_ib]\n mlx5_ib_destroy_wq+0x34/0x80 [mlx5_ib]\n ib_destroy_wq_user+0x30/0xc0 [ib_core]\n uverbs_free_wq+0x28/0x58 [ib_uverbs]\n destroy_hw_idr_uobject+0x34/0x78 [ib_uverbs]\n uverbs_destroy_uobject+0x48/0x240 [ib_uverbs]\n __uverbs_cleanup_ufile+0xd4/0x1a8 [ib_uverbs]\n uverbs_destroy_ufile_hw+0x48/0x120 [ib_uverbs]\n ib_uverbs_close+0x2c/0x100 [ib_uverbs]\n __fput+0xd8/0x2f0\n __fput_sync+0x50/0x70\n __arm64_sys_close+0x40/0x90\n invoke_syscall.constprop.0+0x74/0xd0\n do_el0_svc+0x48/0xe8\n el0_svc+0x44/0x1d0\n el0t_64_sync_handler+0x120/0x130\n el0t_64_sync+0x1a4/0x1a8(CVE-2025-38161)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnet: lan743x: fix potential out-of-bounds write in lan743x_ptp_io_event_clock_get()\n\nBefore calling lan743x_ptp_io_event_clock_get(), the \u0026apos;channel\u0026apos; value\nis checked against the maximum value of PCI11X1X_PTP_IO_MAX_CHANNELS(8).\nThis seems correct and aligns with the PTP interrupt status register\n(PTP_INT_STS) specifications.\n\nHowever, lan743x_ptp_io_event_clock_get() writes to ptp-\u0026gt;extts[] with\nonly LAN743X_PTP_N_EXTTS(4) elements, using channel as an index:\n\n    lan743x_ptp_io_event_clock_get(..., u8 channel,...)\n    {\n        ...\n        /* Update Local timestamp */\n        extts = \u0026amp;ptp-\u0026gt;extts[channel];\n        extts-\u0026gt;ts.tv_sec = sec;\n        ...\n    }\n\nTo avoid an out-of-bounds write and utilize all the supported GPIO\ninputs, set LAN743X_PTP_N_EXTTS to 8.\n\nDetected using the static analysis tool - Svace.(CVE-2025-38183)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnet_sched: sch_sfq: reject invalid perturb period\n\nGerrard Tai reported that SFQ perturb_period has no range check yet,\nand this can be used to trigger a race condition fixed in a separate patch.\n\nWe want to make sure ctl-\u0026gt;perturb_period * HZ will not overflow\nand is positive.\n\n\ntc qd add dev lo root sfq perturb -10   # negative value : error\nError: sch_sfq: invalid perturb period.\n\ntc qd add dev lo root sfq perturb 1000000000 # too big : error\nError: sch_sfq: invalid perturb period.\n\ntc qd add dev lo root sfq perturb 2000000 # acceptable value\ntc -s -d qd sh dev lo\nqdisc sfq 8005: root refcnt 2 limit 127p quantum 64Kb depth 127 flows 128 divisor 1024 perturb 2000000sec\n Sent 0 bytes 0 pkt (dropped 0, overlimits 0 requeues 0)\n backlog 0b 0p requeues 0(CVE-2025-38193)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\njffs2: check that raw node were preallocated before writing summary\n\nSyzkaller detected a kernel bug in jffs2_link_node_ref, caused by fault\ninjection in jffs2_prealloc_raw_node_refs. jffs2_sum_write_sumnode doesn\u0026apos;t\ncheck return value of jffs2_prealloc_raw_node_refs and simply lets any\nerror propagate into jffs2_sum_write_data, which eventually calls\njffs2_link_node_ref in order to link the summary to an expectedly allocated\nnode.\n\nkernel BUG at fs/jffs2/nodelist.c:592!\ninvalid opcode: 0000 [#1] PREEMPT SMP KASAN NOPTI\nCPU: 1 PID: 31277 Comm: syz-executor.7 Not tainted 6.1.128-syzkaller-00139-ge10f83ca10a1 #0\nHardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.12.0-1 04/01/2014\nRIP: 0010:jffs2_link_node_ref+0x570/0x690 fs/jffs2/nodelist.c:592\nCall Trace:\n \u0026lt;TASK\u0026gt;\n jffs2_sum_write_data fs/jffs2/summary.c:841 [inline]\n jffs2_sum_write_sumnode+0xd1a/0x1da0 fs/jffs2/summary.c:874\n jffs2_do_reserve_space+0xa18/0xd60 fs/jffs2/nodemgmt.c:388\n jffs2_reserve_space+0x55f/0xaa0 fs/jffs2/nodemgmt.c:197\n jffs2_write_inode_range+0x246/0xb50 fs/jffs2/write.c:362\n jffs2_write_end+0x726/0x15d0 fs/jffs2/file.c:301\n generic_perform_write+0x314/0x5d0 mm/filemap.c:3856\n __generic_file_write_iter+0x2ae/0x4d0 mm/filemap.c:3973\n generic_file_write_iter+0xe3/0x350 mm/filemap.c:4005\n call_write_iter include/linux/fs.h:2265 [inline]\n do_iter_readv_writev+0x20f/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+0x10c/0x170 fs/splice.c:950\n splice_direct_to_actor+0x337/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\n\nFix this issue by checking return value of jffs2_prealloc_raw_node_refs\nbefore calling jffs2_sum_write_data.\n\nFound by Linux Verification Center (linuxtesting.org) with Syzkaller.(CVE-2025-38194)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nmm/shmem, swap: fix softlockup with mTHP swapin\n\nFollowing softlockup can be easily reproduced on my test machine with:\n\necho always \u0026gt; /sys/kernel/mm/transparent_hugepage/hugepages-64kB/enabled\nswapon /dev/zram0 # zram0 is a 48G swap device\nmkdir -p /sys/fs/cgroup/memory/test\necho 1G \u0026gt; /sys/fs/cgroup/test/memory.max\necho $BASHPID \u0026gt; /sys/fs/cgroup/test/cgroup.procs\nwhile true; do\n    dd if=/dev/zero of=/tmp/test.img bs=1M count=5120\n    cat /tmp/test.img \u0026gt; /dev/null\n    rm /tmp/test.img\ndone\n\nThen after a while:\nwatchdog: BUG: soft lockup - CPU#0 stuck for 763s! [cat:5787]\nModules linked in: zram virtiofs\nCPU: 0 UID: 0 PID: 5787 Comm: cat Kdump: loaded Tainted: G             L      6.15.0.orig-gf3021d9246bc-dirty #118 PREEMPT(voluntary)·\nTainted: [L]=SOFTLOCKUP\nHardware name: Red Hat KVM/RHEL-AV, BIOS 0.0.0 02/06/2015\nRIP: 0010:mpol_shared_policy_lookup+0xd/0x70\nCode: e9 b8 b4 ff ff 31 c0 c3 cc cc cc cc 90 90 90 90 90 90 90 90 90 90 90 90 90 90 90 90 90 66 0f 1f 00 0f 1f 44 00 00 41 54 55 53 \u0026lt;48\u0026gt; 8b 1f 48 85 db 74 41 4c 8d 67 08 48 89 fb 48 89 f5 4c 89 e7 e8\nRSP: 0018:ffffc90002b1fc28 EFLAGS: 00000202\nRAX: 00000000001c20ca RBX: 0000000000724e1e RCX: 0000000000000001\nRDX: ffff888118e214c8 RSI: 0000000000057d42 RDI: ffff888118e21518\nRBP: 000000000002bec8 R08: 0000000000000001 R09: 0000000000000000\nR10: 0000000000000bf4 R11: 0000000000000000 R12: 0000000000000001\nR13: 00000000001c20ca R14: 00000000001c20ca R15: 0000000000000000\nFS:  00007f03f995c740(0000) GS:ffff88a07ad9a000(0000) knlGS:0000000000000000\nCS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033\nCR2: 00007f03f98f1000 CR3: 0000000144626004 CR4: 0000000000770eb0\nDR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000\nDR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400\nPKRU: 55555554\nCall Trace:\n \u0026lt;TASK\u0026gt;\n shmem_alloc_folio+0x31/0xc0\n shmem_swapin_folio+0x309/0xcf0\n ? filemap_get_entry+0x117/0x1e0\n ? xas_load+0xd/0xb0\n ? filemap_get_entry+0x101/0x1e0\n shmem_get_folio_gfp+0x2ed/0x5b0\n shmem_file_read_iter+0x7f/0x2e0\n vfs_read+0x252/0x330\n ksys_read+0x68/0xf0\n do_syscall_64+0x4c/0x1c0\n entry_SYSCALL_64_after_hwframe+0x76/0x7e\nRIP: 0033:0x7f03f9a46991\nCode: 00 48 8b 15 81 14 10 00 f7 d8 64 89 02 b8 ff ff ff ff eb bd e8 20 ad 01 00 f3 0f 1e fa 80 3d 35 97 10 00 00 74 13 31 c0 0f 05 \u0026lt;48\u0026gt; 3d 00 f0 ff ff 77 4f c3 66 0f 1f 44 00 00 55 48 89 e5 48 83 ec\nRSP: 002b:00007fff3c52bd28 EFLAGS: 00000246 ORIG_RAX: 0000000000000000\nRAX: ffffffffffffffda RBX: 0000000000040000 RCX: 00007f03f9a46991\nRDX: 0000000000040000 RSI: 00007f03f98ba000 RDI: 0000000000000003\nRBP: 00007fff3c52bd50 R08: 0000000000000000 R09: 00007f03f9b9a380\nR10: 0000000000000022 R11: 0000000000000246 R12: 0000000000040000\nR13: 00007f03f98ba000 R14: 0000000000000003 R15: 0000000000000000\n \u0026lt;/TASK\u0026gt;\n\nThe reason is simple, readahead brought some order 0 folio in swap cache,\nand the swapin mTHP folio being allocated is in conflict with it, so\nswapcache_prepare fails and causes shmem_swap_alloc_folio to return\n-EEXIST, and shmem simply retries again and again causing this loop.\n\nFix it by applying a similar fix for anon mTHP swapin.\n\nThe performance change is very slight, time of swapin 10g zero folios\nwith shmem (test for 12 times):\nBefore:  2.47s\nAfter:   2.48s\n\n[(CVE-2025-38241)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nlib/group_cpus: fix NULL pointer dereference from group_cpus_evenly()\n\nWhile testing null_blk with configfs, echo 0 \u0026gt; poll_queues will trigger\nfollowing panic:\n\nBUG: kernel NULL pointer dereference, address: 0000000000000010\nOops: Oops: 0000 [#1] SMP NOPTI\nCPU: 27 UID: 0 PID: 920 Comm: bash Not tainted 6.15.0-02023-gadbdb95c8696-dirty #1238 PREEMPT(undef)\nHardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.16.1-2.fc37 04/01/2014\nRIP: 0010:__bitmap_or+0x48/0x70\nCall Trace:\n \u0026lt;TASK\u0026gt;\n __group_cpus_evenly+0x822/0x8c0\n group_cpus_evenly+0x2d9/0x490\n blk_mq_map_queues+0x1e/0x110\n null_map_queues+0xc9/0x170 [null_blk]\n blk_mq_update_queue_map+0xdb/0x160\n blk_mq_update_nr_hw_queues+0x22b/0x560\n nullb_update_nr_hw_queues+0x71/0xf0 [null_blk]\n nullb_device_poll_queues_store+0xa4/0x130 [null_blk]\n configfs_write_iter+0x109/0x1d0\n vfs_write+0x26e/0x6f0\n ksys_write+0x79/0x180\n __x64_sys_write+0x1d/0x30\n x64_sys_call+0x45c4/0x45f0\n do_syscall_64+0xa5/0x240\n entry_SYSCALL_64_after_hwframe+0x76/0x7e\n\nRoot cause is that numgrps is set to 0, and ZERO_SIZE_PTR is returned from\nkcalloc(), and later ZERO_SIZE_PTR will be deferenced.\n\nFix the problem by checking numgrps first in group_cpus_evenly(), and\nreturn NULL directly if numgrps is zero.\n\n[(CVE-2025-38255)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nBluetooth: Fix NULL pointer deference on eir_get_service_data\n\nThe len parameter is considered optional so it can be NULL so it cannot\nbe used for skipping to next entry of EIR_SERVICE_DATA.(CVE-2025-38304)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nASoC: Intel: avs: Verify content returned by parse_int_array()\n\nThe first element of the returned array stores its length. If it is 0,\nany manipulation beyond the element at index 0 ends with null-ptr-deref.(CVE-2025-38307)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nsmb: Log an error when close_all_cached_dirs fails\n\nUnder low-memory conditions, close_all_cached_dirs() can\u0026apos;t move the\ndentries to a separate list to dput() them once the locks are dropped.\nThis will result in a \u0026quot;Dentry still in use\u0026quot; error, so add an error\nmessage that makes it clear this is what happened:\n\n[  495.281119] CIFS: VFS: \\\\otters.example.com\\share Out of memory while dropping dentries\n[  495.281595] ------------[ cut here ]------------\n[  495.281887] BUG: Dentry ffff888115531138{i=78,n=/}  still in use (2) [unmount of cifs cifs]\n[  495.282391] WARNING: CPU: 1 PID: 2329 at fs/dcache.c:1536 umount_check+0xc8/0xf0\n\nAlso, bail out of looping through all tcons as soon as a single\nallocation fails, since we\u0026apos;re already in trouble, and kmalloc() attempts\nfor subseqeuent tcons are likely to fail just like the first one did.(CVE-2025-38321)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nACPICA: fix acpi parse and parseext cache leaks\n\nACPICA commit 8829e70e1360c81e7a5a901b5d4f48330e021ea5\n\nI\u0026apos;m Seunghun Han, and I work for National Security Research Institute of\nSouth Korea.\n\nI have been doing a research on ACPI and found an ACPI cache leak in ACPI\nearly abort cases.\n\nBoot log of ACPI cache leak is as follows:\n[    0.352414] ACPI: Added _OSI(Module Device)\n[    0.353182] ACPI: Added _OSI(Processor Device)\n[    0.353182] ACPI: Added _OSI(3.0 _SCP Extensions)\n[    0.353182] ACPI: Added _OSI(Processor Aggregator Device)\n[    0.356028] ACPI: Unable to start the ACPI Interpreter\n[    0.356799] ACPI Error: Could not remove SCI handler (20170303/evmisc-281)\n[    0.360215] kmem_cache_destroy Acpi-State: Slab cache still has objects\n[    0.360648] CPU: 0 PID: 1 Comm: swapper/0 Tainted: G        W\n4.12.0-rc4-next-20170608+ #10\n[    0.361273] Hardware name: innotek gmb_h virtual_box/virtual_box, BIOS\nvirtual_box 12/01/2006\n[    0.361873] Call Trace:\n[    0.362243]  ? dump_stack+0x5c/0x81\n[    0.362591]  ? kmem_cache_destroy+0x1aa/0x1c0\n[    0.362944]  ? acpi_sleep_proc_init+0x27/0x27\n[    0.363296]  ? acpi_os_delete_cache+0xa/0x10\n[    0.363646]  ? acpi_ut_delete_caches+0x6d/0x7b\n[    0.364000]  ? acpi_terminate+0xa/0x14\n[    0.364000]  ? acpi_init+0x2af/0x34f\n[    0.364000]  ? __class_create+0x4c/0x80\n[    0.364000]  ? video_setup+0x7f/0x7f\n[    0.364000]  ? acpi_sleep_proc_init+0x27/0x27\n[    0.364000]  ? do_one_initcall+0x4e/0x1a0\n[    0.364000]  ? kernel_init_freeable+0x189/0x20a\n[    0.364000]  ? rest_init+0xc0/0xc0\n[    0.364000]  ? kernel_init+0xa/0x100\n[    0.364000]  ? ret_from_fork+0x25/0x30\n\nI analyzed this memory leak in detail. I found that “Acpi-State” cache and\n“Acpi-Parse” cache were merged because the size of cache objects was same\nslab cache size.\n\nI finally found “Acpi-Parse” cache and “Acpi-parse_ext” cache were leaked\nusing SLAB_NEVER_MERGE flag in kmem_cache_create() function.\n\nReal ACPI cache leak point is as follows:\n[    0.360101] ACPI: Added _OSI(Module Device)\n[    0.360101] ACPI: Added _OSI(Processor Device)\n[    0.360101] ACPI: Added _OSI(3.0 _SCP Extensions)\n[    0.361043] ACPI: Added _OSI(Processor Aggregator Device)\n[    0.364016] ACPI: Unable to start the ACPI Interpreter\n[    0.365061] ACPI Error: Could not remove SCI handler (20170303/evmisc-281)\n[    0.368174] kmem_cache_destroy Acpi-Parse: Slab cache still has objects\n[    0.369332] CPU: 1 PID: 1 Comm: swapper/0 Tainted: G        W\n4.12.0-rc4-next-20170608+ #8\n[    0.371256] Hardware name: innotek gmb_h virtual_box/virtual_box, BIOS\nvirtual_box 12/01/2006\n[    0.372000] Call Trace:\n[    0.372000]  ? dump_stack+0x5c/0x81\n[    0.372000]  ? kmem_cache_destroy+0x1aa/0x1c0\n[    0.372000]  ? acpi_sleep_proc_init+0x27/0x27\n[    0.372000]  ? acpi_os_delete_cache+0xa/0x10\n[    0.372000]  ? acpi_ut_delete_caches+0x56/0x7b\n[    0.372000]  ? acpi_terminate+0xa/0x14\n[    0.372000]  ? acpi_init+0x2af/0x34f\n[    0.372000]  ? __class_create+0x4c/0x80\n[    0.372000]  ? video_setup+0x7f/0x7f\n[    0.372000]  ? acpi_sleep_proc_init+0x27/0x27\n[    0.372000]  ? do_one_initcall+0x4e/0x1a0\n[    0.372000]  ? kernel_init_freeable+0x189/0x20a\n[    0.372000]  ? rest_init+0xc0/0xc0\n[    0.372000]  ? kernel_init+0xa/0x100\n[    0.372000]  ? ret_from_fork+0x25/0x30\n[    0.388039] kmem_cache_destroy Acpi-parse_ext: Slab cache still has objects\n[    0.389063] CPU: 1 PID: 1 Comm: swapper/0 Tainted: G        W\n4.12.0-rc4-next-20170608+ #8\n[    0.390557] Hardware name: innotek gmb_h virtual_box/virtual_box, BIOS\nvirtual_box 12/01/2006\n[    0.392000] Call Trace:\n[    0.392000]  ? dump_stack+0x5c/0x81\n[    0.392000]  ? kmem_cache_destroy+0x1aa/0x1c0\n[    0.392000]  ? acpi_sleep_proc_init+0x27/0x27\n[    0.392000]  ? acpi_os_delete_cache+0xa/0x10\n[    0.392000]  ? acpi_ut_delete_caches+0x6d/0x7b\n[    0.392000]  ? acpi_terminate+0xa/0x14\n[    0.392000]  ? acpi_init+0x2af/0x3\n---truncated---(CVE-2025-38344)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nmaple_tree: fix MA_STATE_PREALLOC flag in mas_preallocate()\n\nTemporarily clear the preallocation flag when explicitly requesting\nallocations.  Pre-existing allocations are already counted against the\nrequest through mas_node_count_gfp(), but the allocations will not happen\nif the MA_STATE_PREALLOC flag is set.  This flag is meant to avoid\nre-allocating in bulk allocation mode, and to detect issues with\npreallocation calculations.\n\nThe MA_STATE_PREALLOC flag should also always be set on zero allocations\nso that detection of underflow allocations will print a WARN_ON() during\nconsumption.\n\nUser visible effect of this flaw is a WARN_ON() followed by a null pointer\ndereference when subsequent requests for larger number of nodes is\nignored, such as the vma merge retry in mmap_region() caused by drivers\naltering the vma flags (which happens in v6.6, at least)(CVE-2025-38364)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nvsock: Fix transport_* TOCTOU\n\nTransport assignment may race with module unload. Protect new_transport\nfrom becoming a stale pointer.\n\nThis also takes care of an insecure call in vsock_use_local_transport();\nadd a lockdep assert.\n\nBUG: unable to handle page fault for address: fffffbfff8056000\nOops: Oops: 0000 [#1] SMP KASAN\nRIP: 0010:vsock_assign_transport+0x366/0x600\nCall Trace:\n vsock_connect+0x59c/0xc40\n __sys_connect+0xe8/0x100\n __x64_sys_connect+0x6e/0xc0\n do_syscall_64+0x92/0x1c0\n entry_SYSCALL_64_after_hwframe+0x4b/0x53(CVE-2025-38461)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nvsock: Fix transport_{g2h,h2g} TOCTOU\n\nvsock_find_cid() and vsock_dev_do_ioctl() may race with module unload.\ntransport_{g2h,h2g} may become NULL after the NULL check.\n\nIntroduce vsock_transport_local_cid() to protect from a potential\nnull-ptr-deref.\n\nKASAN: null-ptr-deref in range [0x0000000000000118-0x000000000000011f]\nRIP: 0010:vsock_find_cid+0x47/0x90\nCall Trace:\n __vsock_bind+0x4b2/0x720\n vsock_bind+0x90/0xe0\n __sys_bind+0x14d/0x1e0\n __x64_sys_bind+0x6e/0xc0\n do_syscall_64+0x92/0x1c0\n entry_SYSCALL_64_after_hwframe+0x4b/0x53\n\nKASAN: null-ptr-deref in range [0x0000000000000118-0x000000000000011f]\nRIP: 0010:vsock_dev_do_ioctl.isra.0+0x58/0xf0\nCall Trace:\n __x64_sys_ioctl+0x12d/0x190\n do_syscall_64+0x92/0x1c0\n entry_SYSCALL_64_after_hwframe+0x4b/0x53(CVE-2025-38462)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nsmb: client: fix use-after-free in crypt_message when using async crypto\n\nThe CVE-2024-50047 fix removed asynchronous crypto handling from\ncrypt_message(), assuming all crypto operations are synchronous.\nHowever, when hardware crypto accelerators are used, this can cause\nuse-after-free crashes:\n\n  crypt_message()\n    // Allocate the creq buffer containing the req\n    creq = smb2_get_aead_req(..., \u0026amp;req);\n\n    // Async encryption returns -EINPROGRESS immediately\n    rc = enc ? crypto_aead_encrypt(req) : crypto_aead_decrypt(req);\n\n    // Free creq while async operation is still in progress\n    kvfree_sensitive(creq, ...);\n\nHardware crypto modules often implement async AEAD operations for\nperformance. When crypto_aead_encrypt/decrypt() returns -EINPROGRESS,\nthe operation completes asynchronously. Without crypto_wait_req(),\nthe function immediately frees the request buffer, leading to crashes\nwhen the driver later accesses the freed memory.\n\nThis results in a use-after-free condition when the hardware crypto\ndriver later accesses the freed request structure, leading to kernel\ncrashes with NULL pointer dereferences.\n\nThe issue occurs because crypto_alloc_aead() with mask=0 doesn\u0026apos;t\nguarantee synchronous operation. Even without CRYPTO_ALG_ASYNC in\nthe mask, async implementations can be selected.\n\nFix by restoring the async crypto handling:\n- DECLARE_CRYPTO_WAIT(wait) for completion tracking\n- aead_request_set_callback() for async completion notification\n- crypto_wait_req() to wait for operation completion\n\nThis ensures the request buffer isn\u0026apos;t freed until the crypto operation\ncompletes, whether synchronous or asynchronous, while preserving the\nCVE-2024-50047 fix.(CVE-2025-38488)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nclone_private_mnt(): make sure that caller has CAP_SYS_ADMIN in the right userns\n\nWhat we want is to verify there is that clone won\u0026apos;t expose something\nhidden by a mount we wouldn\u0026apos;t be able to undo.  \u0026quot;Wouldn\u0026apos;t be able to undo\u0026quot;\nmay be a result of MNT_LOCKED on a child, but it may also come from\nlacking admin rights in the userns of the namespace mount belongs to.\n\nclone_private_mnt() checks the former, but not the latter.\n\nThere\u0026apos;s a number of rather confusing CAP_SYS_ADMIN checks in various\nuserns during the mount, especially with the new mount API; they serve\ndifferent purposes and in case of clone_private_mnt() they usually,\nbut not always end up covering the missing check mentioned above.(CVE-2025-38499)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nmptcp: plug races between subflow fail and subflow creation\n\nWe have races similar to the one addressed by the previous patch between\nsubflow failing and additional subflow creation. They are just harder to\ntrigger.\n\nThe solution is similar. Use a separate flag to track the condition\n\u0026apos;socket state prevent any additional subflow creation\u0026apos; protected by the\nfallback lock.\n\nThe socket fallback makes such flag true, and also receiving or sending\nan MP_FAIL option.\n\nThe field \u0026apos;allow_infinite_fallback\u0026apos; is now always touched under the\nrelevant lock, we can drop the ONCE annotation on write.(CVE-2025-38552)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nksmbd: use aead_request_free to match aead_request_alloc\n\nUse aead_request_free() instead of kfree() to properly free memory\nallocated by aead_request_alloc(). This ensures sensitive crypto data\nis zeroed before being freed.(CVE-2025-38575)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nPM / devfreq: Check governor before using governor-\u0026gt;name\n\nCommit 96ffcdf239de (\u0026quot;PM / devfreq: Remove redundant governor_name from\nstruct devfreq\u0026quot;) removes governor_name and uses governor-\u0026gt;name to replace\nit. But devfreq-\u0026gt;governor may be NULL and directly using\ndevfreq-\u0026gt;governor-\u0026gt;name may cause null pointer exception. Move the check of\ngovernor to before using governor-\u0026gt;name.(CVE-2025-38609)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnetfilter: ctnetlink: fix refcount leak on table dump\n\nThere is a reference count leak in ctnetlink_dump_table():\n      if (res \u0026lt; 0) {\n                nf_conntrack_get(\u0026amp;ct-\u0026gt;ct_general); // HERE\n                cb-\u0026gt;args[1] = (unsigned long)ct;\n                ...\n\nWhile its very unlikely, its possible that ct == last.\nIf this happens, then the refcount of ct was already incremented.\nThis 2nd increment is never undone.\n\nThis prevents the conntrack object from being released, which in turn\nkeeps prevents cnet-\u0026gt;count from dropping back to 0.\n\nThis will then block the netns dismantle (or conntrack rmmod) as\nnf_conntrack_cleanup_net_list() will wait forever.\n\nThis can be reproduced by running conntrack_resize.sh selftest in a loop.\nIt takes ~20 minutes for me on a preemptible kernel on average before\nI see a runaway kworker spinning in nf_conntrack_cleanup_net_list.\n\nOne fix would to change this to:\n        if (res \u0026lt; 0) {\n\t\tif (ct != last)\n\t                nf_conntrack_get(\u0026amp;ct-\u0026gt;ct_general);\n\nBut this reference counting isn\u0026apos;t needed in the first place.\nWe can just store a cookie value instead.\n\nA followup patch will do the same for ctnetlink_exp_dump_table,\nit looks to me as if this has the same problem and like\nctnetlink_dump_table, we only need a \u0026apos;skip hint\u0026apos;, not the actual\nobject so we can apply the same cookie strategy there as well.(CVE-2025-38721)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nscsi: qla4xxx: Prevent a potential error pointer dereference\n\nThe qla4xxx_get_ep_fwdb() function is supposed to return NULL on error,\nbut qla4xxx_ep_connect() returns error pointers.  Propagating the error\npointers will lead to an Oops in the caller, so change the error pointers\nto NULL.(CVE-2025-39676)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ntls: fix handling of zero-length records on the rx_list\n\nEach recvmsg() call must process either\n - only contiguous DATA records (any number of them)\n - one non-DATA record\n\nIf the next record has different type than what has already been\nprocessed we break out of the main processing loop. If the record\nhas already been decrypted (which may be the case for TLS 1.3 where\nwe don\u0026apos;t know type until decryption) we queue the pending record\nto the rx_list. Next recvmsg() will pick it up from there.\n\nQueuing the skb to rx_list after zero-copy decrypt is not possible,\nsince in that case we decrypted directly to the user space buffer,\nand we don\u0026apos;t have an skb to queue (darg.skb points to the ciphertext\nskb for access to metadata like length).\n\nOnly data records are allowed zero-copy, and we break the processing\nloop after each non-data record. So we should never zero-copy and\nthen find out that the record type has changed. The corner case\nwe missed is when the initial record comes from rx_list, and it\u0026apos;s\nzero length.(CVE-2025-39682)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nipv6: sr: Fix MAC comparison to be constant-time\n\nTo prevent timing attacks, MACs need to be compared in constant time.\nUse the appropriate helper function for this.(CVE-2025-39702)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nclk: samsung: Fix UBSAN panic in samsung_clk_init()\n\nWith UBSAN_ARRAY_BOUNDS=y, I\u0026apos;m hitting the below panic due to\ndereferencing `ctx-\u0026gt;clk_data.hws` before setting\n`ctx-\u0026gt;clk_data.num = nr_clks`. Move that up to fix the crash.\n\n  UBSAN: array index out of bounds: 00000000f2005512 [#1] PREEMPT SMP\n  \u0026lt;snip\u0026gt;\n  Call trace:\n   samsung_clk_init+0x110/0x124 (P)\n   samsung_clk_init+0x48/0x124 (L)\n   samsung_cmu_register_one+0x3c/0xa0\n   exynos_arm64_register_cmu+0x54/0x64\n   __gs101_cmu_top_of_clk_init_declare+0x28/0x60\n   ...(CVE-2025-39728)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nfs: Prevent file descriptor table allocations exceeding INT_MAX\n\nWhen sysctl_nr_open is set to a very high value (for example, 1073741816\nas set by systemd), processes attempting to use file descriptors near\nthe limit can trigger massive memory allocation attempts that exceed\nINT_MAX, resulting in a WARNING in mm/slub.c:\n\n  WARNING: CPU: 0 PID: 44 at mm/slub.c:5027 __kvmalloc_node_noprof+0x21a/0x288\n\nThis happens because kvmalloc_array() and kvmalloc() check if the\nrequested size exceeds INT_MAX and emit a warning when the allocation is\nnot flagged with __GFP_NOWARN.\n\nSpecifically, when nr_open is set to 1073741816 (0x3ffffff8) and a\nprocess calls dup2(oldfd, 1073741880), the kernel attempts to allocate:\n- File descriptor array: 1073741880 * 8 bytes = 8,589,935,040 bytes\n- Multiple bitmaps: ~400MB\n- Total allocation size: \u0026gt; 8GB (exceeding INT_MAX = 2,147,483,647)\n\nReproducer:\n1. Set /proc/sys/fs/nr_open to 1073741816:\n   # echo 1073741816 \u0026gt; /proc/sys/fs/nr_open\n\n2. Run a program that uses a high file descriptor:\n   #include \u0026lt;unistd.h\u0026gt;\n   #include \u0026lt;sys/resource.h\u0026gt;\n\n   int main() {\n       struct rlimit rlim = {1073741824, 1073741824};\n       setrlimit(RLIMIT_NOFILE, \u0026amp;rlim);\n       dup2(2, 1073741880);  // Triggers the warning\n       return 0;\n   }\n\n3. Observe WARNING in dmesg at mm/slub.c:5027\n\nsystemd commit a8b627a introduced automatic bumping of fs.nr_open to the\nmaximum possible value. The rationale was that systems with memory\ncontrol groups (memcg) no longer need separate file descriptor limits\nsince memory is properly accounted. However, this change overlooked\nthat:\n\n1. The kernel\u0026apos;s allocation functions still enforce INT_MAX as a maximum\n   size regardless of memcg accounting\n2. Programs and tests that legitimately test file descriptor limits can\n   inadvertently trigger massive allocations\n3. The resulting allocations (\u0026gt;8GB) are impractical and will always fail\n\nsystemd\u0026apos;s algorithm starts with INT_MAX and keeps halving the value\nuntil the kernel accepts it. On most systems, this results in nr_open\nbeing set to 1073741816 (0x3ffffff8), which is just under 1GB of file\ndescriptors.\n\nWhile processes rarely use file descriptors near this limit in normal\noperation, certain selftests (like\ntools/testing/selftests/core/unshare_test.c) and programs that test file\ndescriptor limits can trigger this issue.\n\nFix this by adding a check in alloc_fdtable() to ensure the requested\nallocation size does not exceed INT_MAX. This causes the operation to\nfail with -EMFILE instead of triggering a kernel warning and avoids the\nimpractical \u0026gt;8GB memory allocation request.(CVE-2025-39756)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnet: gso: Forbid IPv6 TSO with extensions on devices with only IPV6_CSUM\n\nWhen performing Generic Segmentation Offload (GSO) on an IPv6 packet that\ncontains extension headers, the kernel incorrectly requests checksum offload\nif the egress device only advertises NETIF_F_IPV6_CSUM feature, which has\na strict contract: it supports checksum offload only for plain TCP or UDP\nover IPv6 and explicitly does not support packets with extension headers.\nThe current GSO logic violates this contract by failing to disable the feature\nfor packets with extension headers, such as those used in GREoIPv6 tunnels.\n\nThis violation results in the device being asked to perform an operation\nit cannot support, leading to a `skb_warn_bad_offload` warning and a collapse\nof network throughput. While device TSO/USO is correctly bypassed in favor\nof software GSO for these packets, the GSO stack must be explicitly told not\nto request checksum offload.\n\nMask NETIF_F_IPV6_CSUM, NETIF_F_TSO6 and NETIF_F_GSO_UDP_L4\nin gso_features_check if the IPv6 header contains extension headers to compute\nchecksum in software.\n\nThe exception is a BIG TCP extension, which, as stated in commit\n68e068cabd2c6c53 (\u0026quot;net: reenable NETIF_F_IPV6_CSUM offload for BIG TCP packets\u0026quot;):\n\u0026quot;The feature is only enabled on devices that support BIG TCP TSO.\nThe header is only present for PF_PACKET taps like tcpdump,\nand not transmitted by physical devices.\u0026quot;\n\nkernel log output (truncated):\nWARNING: CPU: 1 PID: 5273 at net/core/dev.c:3535 skb_warn_bad_offload+0x81/0x140\n...\nCall Trace:\n \u0026lt;TASK\u0026gt;\n skb_checksum_help+0x12a/0x1f0\n validate_xmit_skb+0x1a3/0x2d0\n validate_xmit_skb_list+0x4f/0x80\n sch_direct_xmit+0x1a2/0x380\n __dev_xmit_skb+0x242/0x670\n __dev_queue_xmit+0x3fc/0x7f0\n ip6_finish_output2+0x25e/0x5d0\n ip6_finish_output+0x1fc/0x3f0\n ip6_tnl_xmit+0x608/0xc00 [ip6_tunnel]\n ip6gre_tunnel_xmit+0x1c0/0x390 [ip6_gre]\n dev_hard_start_xmit+0x63/0x1c0\n __dev_queue_xmit+0x6d0/0x7f0\n ip6_finish_output2+0x214/0x5d0\n ip6_finish_output+0x1fc/0x3f0\n ip6_xmit+0x2ca/0x6f0\n ip6_finish_output+0x1fc/0x3f0\n ip6_xmit+0x2ca/0x6f0\n inet6_csk_xmit+0xeb/0x150\n __tcp_transmit_skb+0x555/0xa80\n tcp_write_xmit+0x32a/0xe90\n tcp_sendmsg_locked+0x437/0x1110\n tcp_sendmsg+0x2f/0x50\n...\nskb linear:   00000000: e4 3d 1a 7d ec 30 e4 3d 1a 7e 5d 90 86 dd 60 0e\nskb linear:   00000010: 00 0a 1b 34 3c 40 20 11 00 00 00 00 00 00 00 00\nskb linear:   00000020: 00 00 00 00 00 12 20 11 00 00 00 00 00 00 00 00\nskb linear:   00000030: 00 00 00 00 00 11 2f 00 04 01 04 01 01 00 00 00\nskb linear:   00000040: 86 dd 60 0e 00 0a 1b 00 06 40 20 23 00 00 00 00\nskb linear:   00000050: 00 00 00 00 00 00 00 00 00 12 20 23 00 00 00 00\nskb linear:   00000060: 00 00 00 00 00 00 00 00 00 11 bf 96 14 51 13 f9\nskb linear:   00000070: ae 27 a0 a8 2b e3 80 18 00 40 5b 6f 00 00 01 01\nskb linear:   00000080: 08 0a 42 d4 50 d5 4b 70 f8 1a(CVE-2025-39770)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nsctp: initialize more fields in sctp_v6_from_sk()\n\nsyzbot found that sin6_scope_id was not properly initialized,\nleading to undefined behavior.\n\nClear sin6_scope_id and sin6_flowinfo.\n\nBUG: KMSAN: uninit-value in __sctp_v6_cmp_addr+0x887/0x8c0 net/sctp/ipv6.c:649\n  __sctp_v6_cmp_addr+0x887/0x8c0 net/sctp/ipv6.c:649\n  sctp_inet6_cmp_addr+0x4f2/0x510 net/sctp/ipv6.c:983\n  sctp_bind_addr_conflict+0x22a/0x3b0 net/sctp/bind_addr.c:390\n  sctp_get_port_local+0x21eb/0x2440 net/sctp/socket.c:8452\n  sctp_get_port net/sctp/socket.c:8523 [inline]\n  sctp_listen_start net/sctp/socket.c:8567 [inline]\n  sctp_inet_listen+0x710/0xfd0 net/sctp/socket.c:8636\n  __sys_listen_socket net/socket.c:1912 [inline]\n  __sys_listen net/socket.c:1927 [inline]\n  __do_sys_listen net/socket.c:1932 [inline]\n  __se_sys_listen net/socket.c:1930 [inline]\n  __x64_sys_listen+0x343/0x4c0 net/socket.c:1930\n  x64_sys_call+0x271d/0x3e20 arch/x86/include/generated/asm/syscalls_64.h:51\n  do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline]\n  do_syscall_64+0xd9/0x210 arch/x86/entry/syscall_64.c:94\n entry_SYSCALL_64_after_hwframe+0x77/0x7f\n\nLocal variable addr.i.i created at:\n  sctp_get_port net/sctp/socket.c:8515 [inline]\n  sctp_listen_start net/sctp/socket.c:8567 [inline]\n  sctp_inet_listen+0x650/0xfd0 net/sctp/socket.c:8636\n  __sys_listen_socket net/socket.c:1912 [inline]\n  __sys_listen net/socket.c:1927 [inline]\n  __do_sys_listen net/socket.c:1932 [inline]\n  __se_sys_listen net/socket.c:1930 [inline]\n  __x64_sys_listen+0x343/0x4c0 net/socket.c:1930(CVE-2025-39812)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nscsi: lpfc: Fix buffer free/clear order in deferred receive path\n\nFix a use-after-free window by correcting the buffer release sequence in\nthe deferred receive path. The code freed the RQ buffer first and only\nthen cleared the context pointer under the lock. Concurrent paths (e.g.,\nABTS and the repost path) also inspect and release the same pointer under\nthe lock, so the old order could lead to double-free/UAF.\n\nNote that the repost path already uses the correct pattern: detach the\npointer under the lock, then free it after dropping the lock. The\ndeferred path should do the same.(CVE-2025-39841)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnetfilter: br_netfilter: do not check confirmed bit in br_nf_local_in() after confirm\n\nWhen send a broadcast packet to a tap device, which was added to a bridge,\nbr_nf_local_in() is called to confirm the conntrack. If another conntrack\nwith the same hash value is added to the hash table, which can be\ntriggered by a normal packet to a non-bridge device, the below warning\nmay happen.\n\n  ------------[ cut here ]------------\n  WARNING: CPU: 1 PID: 96 at net/bridge/br_netfilter_hooks.c:632 br_nf_local_in+0x168/0x200\n  CPU: 1 UID: 0 PID: 96 Comm: tap_send Not tainted 6.17.0-rc2-dirty #44 PREEMPT(voluntary)\n  RIP: 0010:br_nf_local_in+0x168/0x200\n  Call Trace:\n   \u0026lt;TASK\u0026gt;\n   nf_hook_slow+0x3e/0xf0\n   br_pass_frame_up+0x103/0x180\n   br_handle_frame_finish+0x2de/0x5b0\n   br_nf_hook_thresh+0xc0/0x120\n   br_nf_pre_routing_finish+0x168/0x3a0\n   br_nf_pre_routing+0x237/0x5e0\n   br_handle_frame+0x1ec/0x3c0\n   __netif_receive_skb_core+0x225/0x1210\n   __netif_receive_skb_one_core+0x37/0xa0\n   netif_receive_skb+0x36/0x160\n   tun_get_user+0xa54/0x10c0\n   tun_chr_write_iter+0x65/0xb0\n   vfs_write+0x305/0x410\n   ksys_write+0x60/0xd0\n   do_syscall_64+0xa4/0x260\n   entry_SYSCALL_64_after_hwframe+0x77/0x7f\n   \u0026lt;/TASK\u0026gt;\n  ---[ end trace 0000000000000000 ]---\n\nTo solve the hash conflict, nf_ct_resolve_clash() try to merge the\nconntracks, and update skb-\u0026gt;_nfct. However, br_nf_local_in() still use the\nold ct from local variable \u0026apos;nfct\u0026apos; after confirm(), which leads to this\nwarning.\n\nIf confirm() does not insert the conntrack entry and return NF_DROP, the\nwarning may also occur. There is no need to reserve the WARN_ON_ONCE, just\nremove it.(CVE-2025-39894)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnet: rfkill: gpio: Fix crash due to dereferencering uninitialized pointer\n\nSince commit 7d5e9737efda (\u0026quot;net: rfkill: gpio: get the name and type from\ndevice property\u0026quot;) rfkill_find_type() gets called with the possibly\nuninitialized \u0026quot;const char *type_name;\u0026quot; local variable.\n\nOn x86 systems when rfkill-gpio binds to a \u0026quot;BCM4752\u0026quot; or \u0026quot;LNV4752\u0026quot;\nacpi_device, the rfkill-\u0026gt;type is set based on the ACPI acpi_device_id:\n\n        rfkill-\u0026gt;type = (unsigned)id-\u0026gt;driver_data;\n\nand there is no \u0026quot;type\u0026quot; property so device_property_read_string() will fail\nand leave type_name uninitialized, leading to a potential crash.\n\nrfkill_find_type() does accept a NULL pointer, fix the potential crash\nby initializing type_name to NULL.\n\nNote likely sofar this has not been caught because:\n\n1. Not many x86 machines actually have a \u0026quot;BCM4752\u0026quot;/\u0026quot;LNV4752\u0026quot; acpi_device\n2. The stack happened to contain NULL where type_name is stored(CVE-2025-39937)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ntcp: Clear tcp_sk(sk)-\u0026gt;fastopen_rsk in tcp_disconnect().\n\nsyzbot reported the splat below where a socket had tcp_sk(sk)-\u0026gt;fastopen_rsk\nin the TCP_ESTABLISHED state. [0]\n\nsyzbot reused the server-side TCP Fast Open socket as a new client before\nthe TFO socket completes 3WHS:\n\n  1. accept()\n  2. connect(AF_UNSPEC)\n  3. connect() to another destination\n\nAs of accept(), sk-\u0026gt;sk_state is TCP_SYN_RECV, and tcp_disconnect() changes\nit to TCP_CLOSE and makes connect() possible, which restarts timers.\n\nSince tcp_disconnect() forgot to clear tcp_sk(sk)-\u0026gt;fastopen_rsk, the\nretransmit timer triggered the warning and the intended packet was not\nretransmitted.\n\nLet\u0026apos;s call reqsk_fastopen_remove() in tcp_disconnect().\n\n[0]:\nWARNING: CPU: 2 PID: 0 at net/ipv4/tcp_timer.c:542 tcp_retransmit_timer (net/ipv4/tcp_timer.c:542 (discriminator 7))\nModules linked in:\nCPU: 2 UID: 0 PID: 0 Comm: swapper/2 Not tainted 6.17.0-rc5-g201825fb4278 #62 PREEMPT(voluntary)\nHardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.16.3-debian-1.16.3-2 04/01/2014\nRIP: 0010:tcp_retransmit_timer (net/ipv4/tcp_timer.c:542 (discriminator 7))\nCode: 41 55 41 54 55 53 48 8b af b8 08 00 00 48 89 fb 48 85 ed 0f 84 55 01 00 00 0f b6 47 12 3c 03 74 0c 0f b6 47 12 3c 04 74 04 90 \u0026lt;0f\u0026gt; 0b 90 48 8b 85 c0 00 00 00 48 89 ef 48 8b 40 30 e8 6a 4f 06 3e\nRSP: 0018:ffffc900002f8d40 EFLAGS: 00010293\nRAX: 0000000000000002 RBX: ffff888106911400 RCX: 0000000000000017\nRDX: 0000000002517619 RSI: ffffffff83764080 RDI: ffff888106911400\nRBP: ffff888106d5c000 R08: 0000000000000001 R09: ffffc900002f8de8\nR10: 00000000000000c2 R11: ffffc900002f8ff8 R12: ffff888106911540\nR13: ffff888106911480 R14: ffff888106911840 R15: ffffc900002f8de0\nFS:  0000000000000000(0000) GS:ffff88907b768000(0000) knlGS:0000000000000000\nCS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033\nCR2: 00007f8044d69d90 CR3: 0000000002c30003 CR4: 0000000000370ef0\nCall Trace:\n \u0026lt;IRQ\u0026gt;\n tcp_write_timer (net/ipv4/tcp_timer.c:738)\n call_timer_fn (kernel/time/timer.c:1747)\n __run_timers (kernel/time/timer.c:1799 kernel/time/timer.c:2372)\n timer_expire_remote (kernel/time/timer.c:2385 kernel/time/timer.c:2376 kernel/time/timer.c:2135)\n tmigr_handle_remote_up (kernel/time/timer_migration.c:944 kernel/time/timer_migration.c:1035)\n __walk_groups.isra.0 (kernel/time/timer_migration.c:533 (discriminator 1))\n tmigr_handle_remote (kernel/time/timer_migration.c:1096)\n handle_softirqs (./arch/x86/include/asm/jump_label.h:36 ./include/trace/events/irq.h:142 kernel/softirq.c:580)\n irq_exit_rcu (kernel/softirq.c:614 kernel/softirq.c:453 kernel/softirq.c:680 kernel/softirq.c:696)\n sysvec_apic_timer_interrupt (arch/x86/kernel/apic/apic.c:1050 (discriminator 35) arch/x86/kernel/apic/apic.c:1050 (discriminator 35))\n \u0026lt;/IRQ\u0026gt;(CVE-2025-39955)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnexthop: Forbid FDB status change while nexthop is in a group\n\nThe kernel forbids the creation of non-FDB nexthop groups with FDB\nnexthops:\n\n # ip nexthop add id 1 via 192.0.2.1 fdb\n # ip nexthop add id 2 group 1\n Error: Non FDB nexthop group cannot have fdb nexthops.\n\nAnd vice versa:\n\n # ip nexthop add id 3 via 192.0.2.2 dev dummy1\n # ip nexthop add id 4 group 3 fdb\n Error: FDB nexthop group can only have fdb nexthops.\n\nHowever, as long as no routes are pointing to a non-FDB nexthop group,\nthe kernel allows changing the type of a nexthop from FDB to non-FDB and\nvice versa:\n\n # ip nexthop add id 5 via 192.0.2.2 dev dummy1\n # ip nexthop add id 6 group 5\n # ip nexthop replace id 5 via 192.0.2.2 fdb\n # echo $?\n 0\n\nThis configuration is invalid and can result in a NPD [1] since FDB\nnexthops are not associated with a nexthop device:\n\n # ip route add 198.51.100.1/32 nhid 6\n # ping 198.51.100.1\n\nFix by preventing nexthop FDB status change while the nexthop is in a\ngroup:\n\n # ip nexthop add id 7 via 192.0.2.2 dev dummy1\n # ip nexthop add id 8 group 7\n # ip nexthop replace id 7 via 192.0.2.2 fdb\n Error: Cannot change nexthop FDB status while in a group.\n\n[1]\nBUG: kernel NULL pointer dereference, address: 00000000000003c0\n[...]\nOops: Oops: 0000 [#1] SMP\nCPU: 6 UID: 0 PID: 367 Comm: ping Not tainted 6.17.0-rc6-virtme-gb65678cacc03 #1 PREEMPT(voluntary)\nHardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.17.0-4.fc41 04/01/2014\nRIP: 0010:fib_lookup_good_nhc+0x1e/0x80\n[...]\nCall Trace:\n \u0026lt;TASK\u0026gt;\n fib_table_lookup+0x541/0x650\n ip_route_output_key_hash_rcu+0x2ea/0x970\n ip_route_output_key_hash+0x55/0x80\n __ip4_datagram_connect+0x250/0x330\n udp_connect+0x2b/0x60\n __sys_connect+0x9c/0xd0\n __x64_sys_connect+0x18/0x20\n do_syscall_64+0xa4/0x2a0\n entry_SYSCALL_64_after_hwframe+0x4b/0x53(CVE-2025-39980)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nipvs: Defer ip_vs_ftp unregister during netns cleanup\n\nOn the netns cleanup path, __ip_vs_ftp_exit() may unregister ip_vs_ftp\nbefore connections with valid cp-\u0026gt;app pointers are flushed, leading to a\nuse-after-free.\n\nFix this by introducing a global `exiting_module` flag, set to true in\nip_vs_ftp_exit() before unregistering the pernet subsystem. In\n__ip_vs_ftp_exit(), skip ip_vs_ftp unregister if called during netns\ncleanup (when exiting_module is false) and defer it to\n__ip_vs_cleanup_batch(), which unregisters all apps after all connections\nare flushed. If called during module exit, unregister ip_vs_ftp\nimmediately.(CVE-2025-40018)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ncrypto: hisilicon/qm - set NULL to qm-\u0026gt;debug.qm_diff_regs\n\nWhen the initialization of qm-\u0026gt;debug.acc_diff_reg fails,\nthe probe process does not exit. However, after qm-\u0026gt;debug.qm_diff_regs is\nfreed, it is not set to NULL. This can lead to a double free when the\nremove process attempts to free it again. Therefore, qm-\u0026gt;debug.qm_diff_regs\nshould be set to NULL after it is freed.(CVE-2025-40062)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nbpf: Explicitly check accesses to bpf_sock_addr\n\nSyzkaller found a kernel warning on the following sock_addr program:\n\n    0: r0 = 0\n    1: r2 = *(u32 *)(r1 +60)\n    2: exit\n\nwhich triggers:\n\n    verifier bug: error during ctx access conversion (0)\n\nThis is happening because offset 60 in bpf_sock_addr corresponds to an\nimplicit padding of 4 bytes, right after msg_src_ip4. Access to this\npadding isn\u0026apos;t rejected in sock_addr_is_valid_access and it thus later\nfails to convert the access.\n\nThis patch fixes it by explicitly checking the various fields of\nbpf_sock_addr in sock_addr_is_valid_access.\n\nI checked the other ctx structures and is_valid_access functions and\ndidn\u0026apos;t find any other similar cases. Other cases of (properly handled)\npadding are covered in new tests in a subsequent patch.(CVE-2025-40078)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ncrypto: hisilicon/qm - request reserved interrupt for virtual function\n\nThe device interrupt vector 3 is an error interrupt for\nphysical function and a reserved interrupt for virtual function.\nHowever, the driver has not registered the reserved interrupt for\nvirtual function. When allocating interrupts, the number of interrupts\nis allocated based on powers of two, which includes this interrupt.\nWhen the system enables GICv4 and the virtual function passthrough\nto the virtual machine, releasing the interrupt in the driver\ntriggers a warning.\n\nThe WARNING report is:\nWARNING: CPU: 62 PID: 14889 at arch/arm64/kvm/vgic/vgic-its.c:852 its_free_ite+0x94/0xb4\n\nTherefore, register a reserved interrupt for VF and set the\nIRQF_NO_AUTOEN flag to avoid that warning.(CVE-2025-40136)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nsctp: avoid NULL dereference when chunk data buffer is missing\n\nchunk-\u0026gt;skb pointer is dereferenced in the if-block where it\u0026apos;s supposed\nto be NULL only.\n\nchunk-\u0026gt;skb can only be NULL if chunk-\u0026gt;head_skb is not. Check for frag_list\ninstead and do it just before replacing chunk-\u0026gt;skb. We\u0026apos;re sure that\notherwise chunk-\u0026gt;skb is non-NULL because of outer if() condition.(CVE-2025-40240)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnet: openvswitch: remove never-working support for setting nsh fields\n\nThe validation of the set(nsh(...)) action is completely wrong.\nIt runs through the nsh_key_put_from_nlattr() function that is the\nsame function that validates NSH keys for the flow match and the\npush_nsh() action.  However, the set(nsh(...)) has a very different\nmemory layout.  Nested attributes in there are doubled in size in\ncase of the masked set().  That makes proper validation impossible.\n\nThere is also confusion in the code between the \u0026apos;masked\u0026apos; flag, that\nsays that the nested attributes are doubled in size containing both\nthe value and the mask, and the \u0026apos;is_mask\u0026apos; that says that the value\nwe\u0026apos;re parsing is the mask.  This is causing kernel crash on trying to\nwrite into mask part of the match with SW_FLOW_KEY_PUT() during\nvalidation, while validate_nsh() doesn\u0026apos;t allocate any memory for it:\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 1c2383067 P4D 1c2383067 PUD 20b703067 PMD 0\n  Oops: Oops: 0000 [#1] SMP NOPTI\n  CPU: 8 UID: 0 Kdump: loaded Not tainted 6.17.0-rc4+ #107 PREEMPT(voluntary)\n  RIP: 0010:nsh_key_put_from_nlattr+0x19d/0x610 [openvswitch]\n  Call Trace:\n   \u0026lt;TASK\u0026gt;\n   validate_nsh+0x60/0x90 [openvswitch]\n   validate_set.constprop.0+0x270/0x3c0 [openvswitch]\n   __ovs_nla_copy_actions+0x477/0x860 [openvswitch]\n   ovs_nla_copy_actions+0x8d/0x100 [openvswitch]\n   ovs_packet_cmd_execute+0x1cc/0x310 [openvswitch]\n   genl_family_rcv_msg_doit+0xdb/0x130\n   genl_family_rcv_msg+0x14b/0x220\n   genl_rcv_msg+0x47/0xa0\n   netlink_rcv_skb+0x53/0x100\n   genl_rcv+0x24/0x40\n   netlink_unicast+0x280/0x3b0\n   netlink_sendmsg+0x1f7/0x430\n   ____sys_sendmsg+0x36b/0x3a0\n   ___sys_sendmsg+0x87/0xd0\n   __sys_sendmsg+0x6d/0xd0\n   do_syscall_64+0x7b/0x2c0\n   entry_SYSCALL_64_after_hwframe+0x76/0x7e\n\nThe third issue with this process is that while trying to convert\nthe non-masked set into masked one, validate_set() copies and doubles\nthe size of the OVS_KEY_ATTR_NSH as if it didn\u0026apos;t have any nested\nattributes.  It should be copying each nested attribute and doubling\nthem in size independently.  And the process must be properly reversed\nduring the conversion back from masked to a non-masked variant during\nthe flow dump.\n\nIn the end, the only two outcomes of trying to use this action are\neither validation failure or a kernel crash.  And if somehow someone\nmanages to install a flow with such an action, it will most definitely\nnot do what it is supposed to, since all the keys and the masks are\nmixed up.\n\nFixing all the issues is a complex task as it requires re-writing\nmost of the validation code.\n\nGiven that and the fact that this functionality never worked since\nintroduction, let\u0026apos;s just remove it altogether.  It\u0026apos;s better to\nre-introduce it later with a proper implementation instead of trying\nto fix it in stable releases.(CVE-2025-40254)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ntipc: Fix use-after-free in tipc_mon_reinit_self().\n\nsyzbot reported use-after-free of tipc_net(net)-\u0026gt;monitors[]\nin tipc_mon_reinit_self(). [0]\n\nThe array is protected by RTNL, but tipc_mon_reinit_self()\niterates over it without RTNL.\n\ntipc_mon_reinit_self() is called from tipc_net_finalize(),\nwhich is always under RTNL except for tipc_net_finalize_work().\n\nLet\u0026apos;s hold RTNL in tipc_net_finalize_work().\n\n[0]:\nBUG: KASAN: slab-use-after-free in __raw_spin_lock_irqsave include/linux/spinlock_api_smp.h:110 [inline]\nBUG: KASAN: slab-use-after-free in _raw_spin_lock_irqsave+0xa7/0xf0 kernel/locking/spinlock.c:162\nRead of size 1 at addr ffff88805eae1030 by task kworker/0:7/5989\n\nCPU: 0 UID: 0 PID: 5989 Comm: kworker/0:7 Not tainted syzkaller #0 PREEMPT_{RT,(full)}\nHardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 08/18/2025\nWorkqueue: events tipc_net_finalize_work\nCall Trace:\n \u0026lt;TASK\u0026gt;\n dump_stack_lvl+0x189/0x250 lib/dump_stack.c:120\n print_address_description mm/kasan/report.c:378 [inline]\n print_report+0xca/0x240 mm/kasan/report.c:482\n kasan_report+0x118/0x150 mm/kasan/report.c:595\n __kasan_check_byte+0x2a/0x40 mm/kasan/common.c:568\n kasan_check_byte include/linux/kasan.h:399 [inline]\n lock_acquire+0x8d/0x360 kernel/locking/lockdep.c:5842\n __raw_spin_lock_irqsave include/linux/spinlock_api_smp.h:110 [inline]\n _raw_spin_lock_irqsave+0xa7/0xf0 kernel/locking/spinlock.c:162\n rtlock_slowlock kernel/locking/rtmutex.c:1894 [inline]\n rwbase_rtmutex_lock_state kernel/locking/spinlock_rt.c:160 [inline]\n rwbase_write_lock+0xd3/0x7e0 kernel/locking/rwbase_rt.c:244\n rt_write_lock+0x76/0x110 kernel/locking/spinlock_rt.c:243\n write_lock_bh include/linux/rwlock_rt.h:99 [inline]\n tipc_mon_reinit_self+0x79/0x430 net/tipc/monitor.c:718\n tipc_net_finalize+0x115/0x190 net/tipc/net.c:140\n process_one_work kernel/workqueue.c:3236 [inline]\n process_scheduled_works+0xade/0x17b0 kernel/workqueue.c:3319\n worker_thread+0x8a0/0xda0 kernel/workqueue.c:3400\n kthread+0x70e/0x8a0 kernel/kthread.c:463\n ret_from_fork+0x439/0x7d0 arch/x86/kernel/process.c:148\n ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:245\n \u0026lt;/TASK\u0026gt;\n\nAllocated by task 6089:\n kasan_save_stack mm/kasan/common.c:47 [inline]\n kasan_save_track+0x3e/0x80 mm/kasan/common.c:68\n poison_kmalloc_redzone mm/kasan/common.c:388 [inline]\n __kasan_kmalloc+0x93/0xb0 mm/kasan/common.c:405\n kasan_kmalloc include/linux/kasan.h:260 [inline]\n __kmalloc_cache_noprof+0x1a8/0x320 mm/slub.c:4407\n kmalloc_noprof include/linux/slab.h:905 [inline]\n kzalloc_noprof include/linux/slab.h:1039 [inline]\n tipc_mon_create+0xc3/0x4d0 net/tipc/monitor.c:657\n tipc_enable_bearer net/tipc/bearer.c:357 [inline]\n __tipc_nl_bearer_enable+0xe16/0x13f0 net/tipc/bearer.c:1047\n __tipc_nl_compat_doit net/tipc/netlink_compat.c:371 [inline]\n tipc_nl_compat_doit+0x3bc/0x5f0 net/tipc/netlink_compat.c:393\n tipc_nl_compat_handle net/tipc/netlink_compat.c:-1 [inline]\n tipc_nl_compat_recv+0x83c/0xbe0 net/tipc/netlink_compat.c:1321\n genl_family_rcv_msg_doit+0x215/0x300 net/netlink/genetlink.c:1115\n genl_family_rcv_msg net/netlink/genetlink.c:1195 [inline]\n genl_rcv_msg+0x60e/0x790 net/netlink/genetlink.c:1210\n netlink_rcv_skb+0x208/0x470 net/netlink/af_netlink.c:2552\n genl_rcv+0x28/0x40 net/netlink/genetlink.c:1219\n netlink_unicast_kernel net/netlink/af_netlink.c:1320 [inline]\n netlink_unicast+0x846/0xa10 net/netlink/af_netlink.c:1346\n netlink_sendmsg+0x805/0xb30 net/netlink/af_netlink.c:1896\n sock_sendmsg_nosec net/socket.c:714 [inline]\n __sock_sendmsg+0x21c/0x270 net/socket.c:729\n ____sys_sendmsg+0x508/0x820 net/socket.c:2614\n ___sys_sendmsg+0x21f/0x2a0 net/socket.c:2668\n __sys_sendmsg net/socket.c:2700 [inline]\n __do_sys_sendmsg net/socket.c:2705 [inline]\n __se_sys_sendmsg net/socket.c:2703 [inline]\n __x64_sys_sendmsg+0x1a1/0x260 net/socket.c:2703\n do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline]\n do_syscall_64+0xfa/0x3b0 arch/\n---truncated---(CVE-2025-40280)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nsctp: prevent possible shift-out-of-bounds in sctp_transport_update_rto\n\nsyzbot reported a possible shift-out-of-bounds [1]\n\nBlamed commit added rto_alpha_max and rto_beta_max set to 1000.\n\nIt is unclear if some sctp users are setting very large rto_alpha\nand/or rto_beta.\n\nIn order to prevent user regression, perform the test at run time.\n\nAlso add READ_ONCE() annotations as sysctl values can change under us.\n\n[1]\n\nUBSAN: shift-out-of-bounds in net/sctp/transport.c:509:41\nshift exponent 64 is too large for 32-bit type \u0026apos;unsigned int\u0026apos;\nCPU: 0 UID: 0 PID: 16704 Comm: syz.2.2320 Not tainted syzkaller #0 PREEMPT(full)\nHardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 10/02/2025\nCall Trace:\n \u0026lt;TASK\u0026gt;\n  __dump_stack lib/dump_stack.c:94 [inline]\n  dump_stack_lvl+0x16c/0x1f0 lib/dump_stack.c:120\n  ubsan_epilogue lib/ubsan.c:233 [inline]\n  __ubsan_handle_shift_out_of_bounds+0x27f/0x420 lib/ubsan.c:494\n  sctp_transport_update_rto.cold+0x1c/0x34b net/sctp/transport.c:509\n  sctp_check_transmitted+0x11c4/0x1c30 net/sctp/outqueue.c:1502\n  sctp_outq_sack+0x4ef/0x1b20 net/sctp/outqueue.c:1338\n  sctp_cmd_process_sack net/sctp/sm_sideeffect.c:840 [inline]\n  sctp_cmd_interpreter net/sctp/sm_sideeffect.c:1372 [inline](CVE-2025-40281)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nsctp: Prevent TOCTOU out-of-bounds write\n\nFor the following path not holding the sock lock,\n\n  sctp_diag_dump() -\u0026gt; sctp_for_each_endpoint() -\u0026gt; sctp_ep_dump()\n\nmake sure not to exceed bounds in case the address list has grown\nbetween buffer allocation (time-of-check) and write (time-of-use).(CVE-2025-40331)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nlibceph: replace BUG_ON with bounds check for map-\u0026gt;max_osd\n\nOSD indexes come from untrusted network packets. Boundary checks are\nadded to validate these against map-\u0026gt;max_osd.\n\n[ idryomov: drop BUG_ON in ceph_get_primary_affinity(), minor cosmetic\n  edits ](CVE-2025-68283)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nlibceph: prevent potential out-of-bounds writes in handle_auth_session_key()\n\nThe len field originates from untrusted network packets. Boundary\nchecks have been added to prevent potential out-of-bounds writes when\ndecrypting the connection secret or processing service tickets.\n\n[ idryomov: changelog ](CVE-2025-68284)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nlibceph: fix potential use-after-free in have_mon_and_osd_map()\n\nThe wait loop in __ceph_open_session() can race with the client\nreceiving a new monmap or osdmap shortly after the initial map is\nreceived.  Both ceph_monc_handle_map() and handle_one_map() install\na new map immediately after freeing the old one\n\n    kfree(monc-\u0026gt;monmap);\n    monc-\u0026gt;monmap = monmap;\n\n    ceph_osdmap_destroy(osdc-\u0026gt;osdmap);\n    osdc-\u0026gt;osdmap = newmap;\n\nunder client-\u0026gt;monc.mutex and client-\u0026gt;osdc.lock respectively, but\nbecause neither is taken in have_mon_and_osd_map() it\u0026apos;s possible for\nclient-\u0026gt;monc.monmap-\u0026gt;epoch and client-\u0026gt;osdc.osdmap-\u0026gt;epoch arms in\n\n    client-\u0026gt;monc.monmap \u0026amp;\u0026amp; client-\u0026gt;monc.monmap-\u0026gt;epoch \u0026amp;\u0026amp;\n        client-\u0026gt;osdc.osdmap \u0026amp;\u0026amp; client-\u0026gt;osdc.osdmap-\u0026gt;epoch;\n\ncondition to dereference an already freed map.  This happens to be\nreproducible with generic/395 and generic/397 with KASAN enabled:\n\n    BUG: KASAN: slab-use-after-free in have_mon_and_osd_map+0x56/0x70\n    Read of size 4 at addr ffff88811012d810 by task mount.ceph/13305\n    CPU: 2 UID: 0 PID: 13305 Comm: mount.ceph Not tainted 6.14.0-rc2-build2+ #1266\n    ...\n    Call Trace:\n    \u0026lt;TASK\u0026gt;\n    have_mon_and_osd_map+0x56/0x70\n    ceph_open_session+0x182/0x290\n    ceph_get_tree+0x333/0x680\n    vfs_get_tree+0x49/0x180\n    do_new_mount+0x1a3/0x2d0\n    path_mount+0x6dd/0x730\n    do_mount+0x99/0xe0\n    __do_sys_mount+0x141/0x180\n    do_syscall_64+0x9f/0x100\n    entry_SYSCALL_64_after_hwframe+0x76/0x7e\n    \u0026lt;/TASK\u0026gt;\n\n    Allocated by task 13305:\n    ceph_osdmap_alloc+0x16/0x130\n    ceph_osdc_init+0x27a/0x4c0\n    ceph_create_client+0x153/0x190\n    create_fs_client+0x50/0x2a0\n    ceph_get_tree+0xff/0x680\n    vfs_get_tree+0x49/0x180\n    do_new_mount+0x1a3/0x2d0\n    path_mount+0x6dd/0x730\n    do_mount+0x99/0xe0\n    __do_sys_mount+0x141/0x180\n    do_syscall_64+0x9f/0x100\n    entry_SYSCALL_64_after_hwframe+0x76/0x7e\n\n    Freed by task 9475:\n    kfree+0x212/0x290\n    handle_one_map+0x23c/0x3b0\n    ceph_osdc_handle_map+0x3c9/0x590\n    mon_dispatch+0x655/0x6f0\n    ceph_con_process_message+0xc3/0xe0\n    ceph_con_v1_try_read+0x614/0x760\n    ceph_con_workfn+0x2de/0x650\n    process_one_work+0x486/0x7c0\n    process_scheduled_works+0x73/0x90\n    worker_thread+0x1c8/0x2a0\n    kthread+0x2ec/0x300\n    ret_from_fork+0x24/0x40\n    ret_from_fork_asm+0x1a/0x30\n\nRewrite the wait loop to check the above condition directly with\nclient-\u0026gt;monc.mutex and client-\u0026gt;osdc.lock taken as appropriate.  While\nat it, improve the timeout handling (previously mount_timeout could be\nexceeded in case wait_event_interruptible_timeout() slept more than\nonce) and access client-\u0026gt;auth_err under client-\u0026gt;monc.mutex to match\nhow it\u0026apos;s set in finish_auth().\n\nmonmap_show() and osdmap_show() now take the respective lock before\naccessing the map as well.(CVE-2025-68285)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nBluetooth: hci_core: lookup hci_conn on RX path on protocol side\n\nThe hdev lock/lookup/unlock/use pattern in the packet RX path doesn\u0026apos;t\nensure hci_conn* is not concurrently modified/deleted. This locking\nappears to be leftover from before conn_hash started using RCU\ncommit bf4c63252490b (\u0026quot;Bluetooth: convert conn hash to RCU\u0026quot;)\nand not clear if it had purpose since then.\n\nCurrently, there are code paths that delete hci_conn* from elsewhere\nthan the ordered hdev-\u0026gt;workqueue where the RX work runs in. E.g.\ncommit 5af1f84ed13a (\u0026quot;Bluetooth: hci_sync: Fix UAF on hci_abort_conn_sync\u0026quot;)\nintroduced some of these, and there probably were a few others before\nit.  It\u0026apos;s better to do the locking so that even if these run\nconcurrently no UAF is possible.\n\nMove the lookup of hci_conn and associated socket-specific conn to\nprotocol recv handlers, and do them within a single critical section\nto cover hci_conn* usage and lookup.\n\nsyzkaller has reported a crash that appears to be this issue:\n\n    [Task hdev-\u0026gt;workqueue]          [Task 2]\n                                    hci_disconnect_all_sync\n    l2cap_recv_acldata(hcon)\n                                      hci_conn_get(hcon)\n                                      hci_abort_conn_sync(hcon)\n                                        hci_dev_lock\n      hci_dev_lock\n                                        hci_conn_del(hcon)\n      v-------------------------------- hci_dev_unlock\n                                      hci_conn_put(hcon)\n      conn = hcon-\u0026gt;l2cap_data (UAF)(CVE-2025-68304)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nima: Handle error code returned by ima_filter_rule_match()\n\nIn ima_match_rules(), if ima_filter_rule_match() returns -ENOENT due to\nthe rule being NULL, the function incorrectly skips the \u0026apos;if (!rc)\u0026apos; check\nand sets \u0026apos;result = true\u0026apos;. The LSM rule is considered a match, causing\nextra files to be measured by IMA.\n\nThis issue can be reproduced in the following scenario:\nAfter unloading the SELinux policy module via \u0026apos;semodule -d\u0026apos;, if an IMA\nmeasurement is triggered before ima_lsm_rules is updated,\nin ima_match_rules(), the first call to ima_filter_rule_match() returns\n-ESTALE. This causes the code to enter the \u0026apos;if (rc == -ESTALE \u0026amp;\u0026amp;\n!rule_reinitialized)\u0026apos; block, perform ima_lsm_copy_rule() and retry. In\nima_lsm_copy_rule(), since the SELinux module has been removed, the rule\nbecomes NULL, and the second call to ima_filter_rule_match() returns\n-ENOENT. This bypasses the \u0026apos;if (!rc)\u0026apos; check and results in a false match.\n\nCall trace:\n  selinux_audit_rule_match+0x310/0x3b8\n  security_audit_rule_match+0x60/0xa0\n  ima_match_rules+0x2e4/0x4a0\n  ima_match_policy+0x9c/0x1e8\n  ima_get_action+0x48/0x60\n  process_measurement+0xf8/0xa98\n  ima_bprm_check+0x98/0xd8\n  security_bprm_check+0x5c/0x78\n  search_binary_handler+0x6c/0x318\n  exec_binprm+0x58/0x1b8\n  bprm_execve+0xb8/0x130\n  do_execveat_common.isra.0+0x1a8/0x258\n  __arm64_sys_execve+0x48/0x68\n  invoke_syscall+0x50/0x128\n  el0_svc_common.constprop.0+0xc8/0xf0\n  do_el0_svc+0x24/0x38\n  el0_svc+0x44/0x200\n  el0t_64_sync_handler+0x100/0x130\n  el0t_64_sync+0x3c8/0x3d0\n\nFix this by changing \u0026apos;if (!rc)\u0026apos; to \u0026apos;if (rc \u0026lt;= 0)\u0026apos; to ensure that error\ncodes like -ENOENT do not bypass the check and accidentally result in a\nsuccessful match.(CVE-2025-68740)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nbpf: Fix invalid prog-\u0026gt;stats access when update_effective_progs fails\n\nSyzkaller triggers an invalid memory access issue following fault\ninjection in update_effective_progs. The issue can be described as\nfollows:\n\n__cgroup_bpf_detach\n  update_effective_progs\n    compute_effective_progs\n      bpf_prog_array_alloc \u0026lt;-- fault inject\n  purge_effective_progs\n    /* change to dummy_bpf_prog */\n    array-\u0026gt;items[index] = \u0026amp;dummy_bpf_prog.prog\n\n---softirq start---\n__do_softirq\n  ...\n    __cgroup_bpf_run_filter_skb\n      __bpf_prog_run_save_cb\n        bpf_prog_run\n          stats = this_cpu_ptr(prog-\u0026gt;stats)\n          /* invalid memory access */\n          flags = u64_stats_update_begin_irqsave(\u0026amp;stats-\u0026gt;syncp)\n---softirq end---\n\n  static_branch_dec(\u0026amp;cgroup_bpf_enabled_key[atype])\n\nThe reason is that fault injection caused update_effective_progs to fail\nand then changed the original prog into dummy_bpf_prog.prog in\npurge_effective_progs. Then a softirq came, and accessing the members of\ndummy_bpf_prog.prog in the softirq triggers invalid mem access.\n\nTo fix it, skip updating stats when stats is NULL.(CVE-2025-68742)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nethtool: Avoid overflowing userspace buffer on stats query\n\nThe ethtool -S command operates across three ioctl calls:\nETHTOOL_GSSET_INFO for the size, ETHTOOL_GSTRINGS for the names, and\nETHTOOL_GSTATS for the values.\n\nIf the number of stats changes between these calls (e.g., due to device\nreconfiguration), userspace\u0026apos;s buffer allocation will be incorrect,\npotentially leading to buffer overflow.\n\nDrivers are generally expected to maintain stable stat counts, but some\ndrivers (e.g., mlx5, bnx2x, bna, ksz884x) use dynamic counters, making\nthis scenario possible.\n\nSome drivers try to handle this internally:\n- bnad_get_ethtool_stats() returns early in case stats.n_stats is not\n  equal to the driver\u0026apos;s stats count.\n- micrel/ksz884x also makes sure not to write anything beyond\n  stats.n_stats and overflow the buffer.\n\nHowever, both use stats.n_stats which is already assigned with the value\nreturned from get_sset_count(), hence won\u0026apos;t solve the issue described\nhere.\n\nChange ethtool_get_strings(), ethtool_get_stats(),\nethtool_get_phy_stats() to not return anything in case of a mismatch\nbetween userspace\u0026apos;s size and get_sset_size(), to prevent buffer\noverflow.\nThe returned n_stats value will be equal to zero, to reflect that\nnothing has been returned.\n\nThis could result in one of two cases when using upstream ethtool,\ndepending on when the size change is detected:\n1. When detected in ethtool_get_strings():\n    # ethtool -S eth2\n    no stats available\n\n2. When detected in get stats, all stats will be reported as zero.\n\nBoth cases are presumably transient, and a subsequent ethtool call\nshould succeed.\n\nOther than the overflow avoidance, these two cases are very evident (no\noutput/cleared stats), which is arguably better than presenting\nincorrect/shifted stats.\nI also considered returning an error instead of a \u0026quot;silent\u0026quot; response, but\nthat seems more destructive towards userspace apps.\n\nNotes:\n- This patch does not claim to fix the inherent race, it only makes sure\n  that we do not overflow the userspace buffer, and makes for a more\n  predictable behavior.\n\n- RTNL lock is held during each ioctl, the race window exists between\n  the separate ioctl calls when the lock is released.\n\n- Userspace ethtool always fills stats.n_stats, but it is likely that\n  these stats ioctls are implemented in other userspace applications\n  which might not fill it. The added code checks that it\u0026apos;s not zero,\n  to prevent any regressions.(CVE-2025-68795)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\next4: xattr: fix null pointer deref in ext4_raw_inode()\n\nIf ext4_get_inode_loc() fails (e.g. if it returns -EFSCORRUPTED),\niloc.bh will remain set to NULL. Since ext4_xattr_inode_dec_ref_all()\nlacks error checking, this will lead to a null pointer dereference\nin ext4_raw_inode(), called right after ext4_get_inode_loc().\n\nFound by Linux Verification Center (linuxtesting.org) with SVACE.(CVE-2025-68820)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnet: hns3: using the num_tqps in the vf driver to apply for resources\n\nCurrently, hdev-\u0026gt;htqp is allocated using hdev-\u0026gt;num_tqps, and kinfo-\u0026gt;tqp\nis allocated using kinfo-\u0026gt;num_tqps. However, kinfo-\u0026gt;num_tqps is set to\nmin(new_tqps, hdev-\u0026gt;num_tqps);  Therefore, kinfo-\u0026gt;num_tqps may be smaller\nthan hdev-\u0026gt;num_tqps, which causes some hdev-\u0026gt;htqp[i] to remain\nuninitialized in hclgevf_knic_setup().\n\nThus, this patch allocates hdev-\u0026gt;htqp and kinfo-\u0026gt;tqp using hdev-\u0026gt;num_tqps,\nensuring that the lengths of hdev-\u0026gt;htqp and kinfo-\u0026gt;tqp are consistent\nand that all elements are properly initialized.(CVE-2025-71064)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnet/sched: sch_qfq: Fix NULL deref when deactivating inactive aggregate in qfq_reset\n\n`qfq_class-\u0026gt;leaf_qdisc-\u0026gt;q.qlen \u0026gt; 0` does not imply that the class\nitself is active.\n\nTwo qfq_class objects may point to the same leaf_qdisc. This happens\nwhen:\n\n1. one QFQ qdisc is attached to the dev as the root qdisc, and\n\n2. another QFQ qdisc is temporarily referenced (e.g., via qdisc_get()\n/ qdisc_put()) and is pending to be destroyed, as in function\ntc_new_tfilter.\n\nWhen packets are enqueued through the root QFQ qdisc, the shared\nleaf_qdisc-\u0026gt;q.qlen increases. At the same time, the second QFQ\nqdisc triggers qdisc_put and qdisc_destroy: the qdisc enters\nqfq_reset() with its own q-\u0026gt;q.qlen == 0, but its class\u0026apos;s leaf\nqdisc-\u0026gt;q.qlen \u0026gt; 0. Therefore, the qfq_reset would wrongly deactivate\nan inactive aggregate and trigger a null-deref in qfq_deactivate_agg:\n\n[    0.903172] BUG: kernel NULL pointer dereference, address: 0000000000000000\n[    0.903571] #PF: supervisor write access in kernel mode\n[    0.903860] #PF: error_code(0x0002) - not-present page\n[    0.904177] PGD 10299b067 P4D 10299b067 PUD 10299c067 PMD 0\n[    0.904502] Oops: Oops: 0002 [#1] SMP NOPTI\n[    0.904737] CPU: 0 UID: 0 PID: 135 Comm: exploit Not tainted 6.19.0-rc3+ #2 NONE\n[    0.905157] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS rel-1.17.0-0-gb52ca86e094d-prebuilt.qemu.org 04/01/2014\n[    0.905754] RIP: 0010:qfq_deactivate_agg (include/linux/list.h:992 (discriminator 2) include/linux/list.h:1006 (discriminator 2) net/sched/sch_qfq.c:1367 (discriminator 2) net/sched/sch_qfq.c:1393 (discriminator 2))\n[    0.906046] Code: 0f 84 4d 01 00 00 48 89 70 18 8b 4b 10 48 c7 c2 ff ff ff ff 48 8b 78 08 48 d3 e2 48 21 f2 48 2b 13 48 8b 30 48 d3 ea 8b 4b 18 0\n\nCode starting with the faulting instruction\n===========================================\n   0:\t0f 84 4d 01 00 00    \tje     0x153\n   6:\t48 89 70 18          \tmov    %rsi,0x18(%rax)\n   a:\t8b 4b 10             \tmov    0x10(%rbx),%ecx\n   d:\t48 c7 c2 ff ff ff ff \tmov    $0xffffffffffffffff,%rdx\n  14:\t48 8b 78 08          \tmov    0x8(%rax),%rdi\n  18:\t48 d3 e2             \tshl    %cl,%rdx\n  1b:\t48 21 f2             \tand    %rsi,%rdx\n  1e:\t48 2b 13             \tsub    (%rbx),%rdx\n  21:\t48 8b 30             \tmov    (%rax),%rsi\n  24:\t48 d3 ea             \tshr    %cl,%rdx\n  27:\t8b 4b 18             \tmov    0x18(%rbx),%ecx\n\t...\n[    0.907095] RSP: 0018:ffffc900004a39a0 EFLAGS: 00010246\n[    0.907368] RAX: ffff8881043a0880 RBX: ffff888102953340 RCX: 0000000000000000\n[    0.907723] RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000000000000\n[    0.908100] RBP: ffff888102952180 R08: 0000000000000000 R09: 0000000000000000\n[    0.908451] R10: ffff8881043a0000 R11: 0000000000000000 R12: ffff888102952000\n[    0.908804] R13: ffff888102952180 R14: ffff8881043a0ad8 R15: ffff8881043a0880\n[    0.909179] FS:  000000002a1a0380(0000) GS:ffff888196d8d000(0000) knlGS:0000000000000000\n[    0.909572] CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033\n[    0.909857] CR2: 0000000000000000 CR3: 0000000102993002 CR4: 0000000000772ef0\n[    0.910247] PKRU: 55555554\n[    0.910391] Call Trace:\n[    0.910527]  \u0026lt;TASK\u0026gt;\n[    0.910638]  qfq_reset_qdisc (net/sched/sch_qfq.c:357 net/sched/sch_qfq.c:1485)\n[    0.910826]  qdisc_reset (include/linux/skbuff.h:2195 include/linux/skbuff.h:2501 include/linux/skbuff.h:3424 include/linux/skbuff.h:3430 net/sched/sch_generic.c:1036)\n[    0.911040]  __qdisc_destroy (net/sched/sch_generic.c:1076)\n[    0.911236]  tc_new_tfilter (net/sched/cls_api.c:2447)\n[    0.911447]  rtnetlink_rcv_msg (net/core/rtnetlink.c:6958)\n[    0.911663]  ? __pfx_rtnetlink_rcv_msg (net/core/rtnetlink.c:6861)\n[    0.911894]  netlink_rcv_skb (net/netlink/af_netlink.c:2550)\n[    0.912100]  netlink_unicast (net/netlink/af_netlink.c:1319 net/netlink/af_netlink.c:1344)\n[    0.912296]  ? __alloc_skb (net/core/skbuff.c:706)\n[    0.912484]  netlink_sendmsg (net/netlink/af\n---truncated---(CVE-2026-22976)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nbpf: Fix reference count leak in bpf_prog_test_run_xdp()\n\nsyzbot is reporting\n\n  unregister_netdevice: waiting for sit0 to become free. Usage count = 2\n\nproblem. A debug printk() patch found that a refcount is obtained at\nxdp_convert_md_to_buff() from bpf_prog_test_run_xdp().\n\nAccording to commit ec94670fcb3b (\u0026quot;bpf: Support specifying ingress via\nxdp_md context in BPF_PROG_TEST_RUN\u0026quot;), the refcount obtained by\nxdp_convert_md_to_buff() will be released by xdp_convert_buff_to_md().\n\nTherefore, we can consider that the error handling path introduced by\ncommit 1c1949982524 (\u0026quot;bpf: introduce frags support to\nbpf_prog_test_run_xdp()\u0026quot;) forgot to call xdp_convert_buff_to_md().(CVE-2026-22994)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nNFS: Fix a deadlock involving nfs_release_folio()\n\nWang Zhaolong reports a deadlock involving NFSv4.1 state recovery\nwaiting on kthreadd, which is attempting to reclaim memory by calling\nnfs_release_folio(). The latter cannot make progress due to state\nrecovery being needed.\n\nIt seems that the only safe thing to do here is to kick off a writeback\nof the folio, without waiting for completion, or else kicking off an\nasynchronous commit.(CVE-2026-23053)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nuacce: implement mremap in uacce_vm_ops to return -EPERM\n\nThe current uacce_vm_ops does not support the mremap operation of\nvm_operations_struct. Implement .mremap to return -EPERM to remind\nusers.\n\nThe reason we need to explicitly disable mremap is that when the\ndriver does not implement .mremap, it uses the default mremap\nmethod. This could lead to a risk scenario:\n\nAn application might first mmap address p1, then mremap to p2,\nfollowed by munmap(p1), and finally munmap(p2). Since the default\nmremap copies the original vma\u0026apos;s vm_private_data (i.e., q) to the\nnew vma, both munmap operations would trigger vma_close, causing\nq-\u0026gt;qfr to be freed twice(qfr will be set to null here, so repeated\nrelease is ok).(CVE-2026-23056)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nuacce: ensure safe queue release with state management\n\nDirectly calling `put_queue` carries risks since it cannot\nguarantee that resources of `uacce_queue` have been fully released\nbeforehand. So adding a `stop_queue` operation for the\nUACCE_CMD_PUT_Q command and leaving the `put_queue` operation to\nthe final resource release ensures safety.\n\nQueue states are defined as follows:\n- UACCE_Q_ZOMBIE: Initial state\n- UACCE_Q_INIT: After opening `uacce`\n- UACCE_Q_STARTED: After `start` is issued via `ioctl`\n\nWhen executing `poweroff -f` in virt while accelerator are still\nworking, `uacce_fops_release` and `uacce_remove` may execute\nconcurrently. This can cause `uacce_put_queue` within\n`uacce_fops_release` to access a NULL `ops` pointer. Therefore, add\nstate checks to prevent accessing freed pointers.(CVE-2026-23063)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nmedia: dvb-core: fix wrong reinitialization of ringbuffer on reopen\n\ndvb_dvr_open() calls dvb_ringbuffer_init() when a new reader opens the\nDVR device.  dvb_ringbuffer_init() calls init_waitqueue_head(), which\nreinitializes the waitqueue list head to empty.\n\nSince dmxdev-\u0026gt;dvr_buffer.queue is a shared waitqueue (all opens of the\nsame DVR device share it), this orphans any existing waitqueue entries\nfrom io_uring poll or epoll, leaving them with stale prev/next pointers\nwhile the list head is reset to {self, self}.\n\nThe waitqueue and spinlock in dvr_buffer are already properly\ninitialized once in dvb_dmxdev_init().  The open path only needs to\nreset the buffer data pointer, size, and read/write positions.\n\nReplace the dvb_ringbuffer_init() call in dvb_dvr_open() with direct\nassignment of data/size and a call to dvb_ringbuffer_reset(), which\nproperly resets pread, pwrite, and error with correct memory ordering\nwithout touching the waitqueue or spinlock.(CVE-2026-23253)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nregmap: maple: free entry on mas_store_gfp() failure\n\nregcache_maple_write() allocates a new block (\u0026apos;entry\u0026apos;) to merge\nadjacent ranges and then stores it with mas_store_gfp().\nWhen mas_store_gfp() fails, the new \u0026apos;entry\u0026apos; remains allocated and\nis never freed, leaking memory.\n\nFree \u0026apos;entry\u0026apos; on the failure path; on success continue freeing the\nreplaced neighbor blocks (\u0026apos;lower\u0026apos;, \u0026apos;upper\u0026apos;).(CVE-2026-23260)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\napparmor: fix unprivileged local user can do privileged policy management\n\nAn unprivileged local user can load, replace, and remove profiles by\nopening the apparmorfs interfaces, via a confused deputy attack, by\npassing the opened fd to a privileged process, and getting the\nprivileged process to write to the interface.\n\nThis does require a privileged target that can be manipulated to do\nthe write for the unprivileged process, but once such access is\nachieved full policy management is possible and all the possible\nimplications that implies: removing confinement, DoS of system or\ntarget applications by denying all execution, by-passing the\nunprivileged user namespace restriction, to exploiting kernel bugs for\na local privilege escalation.\n\nThe policy management interface can not have its permissions simply\nchanged from 0666 to 0600 because non-root processes need to be able\nto load policy to different policy namespaces.\n\nInstead ensure the task writing the interface has privileges that\nare a subset of the task that opened the interface. This is already\ndone via policy for confined processes, but unconfined can delegate\naccess to the opened fd, by-passing the usual policy check.(CVE-2026-23268)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nperf: Fix __perf_event_overflow() vs perf_remove_from_context() race\n\nMake sure that __perf_event_overflow() runs with IRQs disabled for all\npossible callchains. Specifically the software events can end up running\nit with only preemption disabled.\n\nThis opens up a race vs perf_event_exit_event() and friends that will go\nand free various things the overflow path expects to be present, like\nthe BPF program.(CVE-2026-23271)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nmacvlan: observe an RCU grace period in macvlan_common_newlink() error path\n\nvalis reported that a race condition still happens after my prior patch.\n\nmacvlan_common_newlink() might have made @dev visible before\ndetecting an error, and its caller will directly call free_netdev(dev).\n\nWe must respect an RCU period, either in macvlan or the core networking\nstack.\n\nAfter adding a temporary mdelay(1000) in macvlan_forward_source_one()\nto open the race window, valis repro was:\n\nip link add p1 type veth peer p2\nip link set address 00:00:00:00:00:20 dev p1\nip link set up dev p1\nip link set up dev p2\nip link add mv0 link p2 type macvlan mode source\n\n(ip link add invalid% link p2 type macvlan mode source macaddr add\n00:00:00:00:00:20 \u0026amp;) ; sleep 0.5 ; ping -c1 -I p1 1.2.3.4\nPING 1.2.3.4 (1.2.3.4): 56 data bytes\nRTNETLINK answers: Invalid argument\n\nBUG: KASAN: slab-use-after-free in macvlan_forward_source\n(drivers/net/macvlan.c:408 drivers/net/macvlan.c:444)\nRead of size 8 at addr ffff888016bb89c0 by task e/175\n\nCPU: 1 UID: 1000 PID: 175 Comm: e Not tainted 6.19.0-rc8+ #33 NONE\nHardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.14.0-2 04/01/2014\nCall Trace:\n\u0026lt;IRQ\u0026gt;\ndump_stack_lvl (lib/dump_stack.c:123)\nprint_report (mm/kasan/report.c:379 mm/kasan/report.c:482)\n? macvlan_forward_source (drivers/net/macvlan.c:408 drivers/net/macvlan.c:444)\nkasan_report (mm/kasan/report.c:597)\n? macvlan_forward_source (drivers/net/macvlan.c:408 drivers/net/macvlan.c:444)\nmacvlan_forward_source (drivers/net/macvlan.c:408 drivers/net/macvlan.c:444)\n? tasklet_init (kernel/softirq.c:983)\nmacvlan_handle_frame (drivers/net/macvlan.c:501)\n\nAllocated by task 169:\nkasan_save_stack (mm/kasan/common.c:58)\nkasan_save_track (./arch/x86/include/asm/current.h:25\nmm/kasan/common.c:70 mm/kasan/common.c:79)\n__kasan_kmalloc (mm/kasan/common.c:419)\n__kvmalloc_node_noprof (./include/linux/kasan.h:263 mm/slub.c:5657\nmm/slub.c:7140)\nalloc_netdev_mqs (net/core/dev.c:12012)\nrtnl_create_link (net/core/rtnetlink.c:3648)\nrtnl_newlink (net/core/rtnetlink.c:3830 net/core/rtnetlink.c:3957\nnet/core/rtnetlink.c:4072)\nrtnetlink_rcv_msg (net/core/rtnetlink.c:6958)\nnetlink_rcv_skb (net/netlink/af_netlink.c:2550)\nnetlink_unicast (net/netlink/af_netlink.c:1319 net/netlink/af_netlink.c:1344)\nnetlink_sendmsg (net/netlink/af_netlink.c:1894)\n__sys_sendto (net/socket.c:727 net/socket.c:742 net/socket.c:2206)\n__x64_sys_sendto (net/socket.c:2209)\ndo_syscall_64 (arch/x86/entry/syscall_64.c:63 arch/x86/entry/syscall_64.c:94)\nentry_SYSCALL_64_after_hwframe (arch/x86/entry/entry_64.S:131)\n\nFreed by task 169:\nkasan_save_stack (mm/kasan/common.c:58)\nkasan_save_track (./arch/x86/include/asm/current.h:25\nmm/kasan/common.c:70 mm/kasan/common.c:79)\nkasan_save_free_info (mm/kasan/generic.c:587)\n__kasan_slab_free (mm/kasan/common.c:287)\nkfree (mm/slub.c:6674 mm/slub.c:6882)\nrtnl_newlink (net/core/rtnetlink.c:3845 net/core/rtnetlink.c:3957\nnet/core/rtnetlink.c:4072)\nrtnetlink_rcv_msg (net/core/rtnetlink.c:6958)\nnetlink_rcv_skb (net/netlink/af_netlink.c:2550)\nnetlink_unicast (net/netlink/af_netlink.c:1319 net/netlink/af_netlink.c:1344)\nnetlink_sendmsg (net/netlink/af_netlink.c:1894)\n__sys_sendto (net/socket.c:727 net/socket.c:742 net/socket.c:2206)\n__x64_sys_sendto (net/socket.c:2209)\ndo_syscall_64 (arch/x86/entry/syscall_64.c:63 arch/x86/entry/syscall_64.c:94)\nentry_SYSCALL_64_after_hwframe (arch/x86/entry/entry_64.S:131)(CVE-2026-23273)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\next4: reject mount if bigalloc with s_first_data_block != 0\n\nbigalloc with s_first_data_block != 0 is not supported, reject mounting\nit.(CVE-2026-31447)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nHID: multitouch: Check to ensure report responses match the request\n\nIt is possible for a malicious (or clumsy) device to respond to a\nspecific report\u0026apos;s feature request using a completely different report\nID.  This can cause confusion in the HID core resulting in nasty\nside-effects such as OOB writes.\n\nAdd a check to ensure that the report ID in the response, matches the\none that was requested.  If it doesn\u0026apos;t, omit reporting the raw event and\nreturn early.(CVE-2026-43047)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nHID: core: Mitigate potential OOB by removing bogus memset()\n\nThe memset() in hid_report_raw_event() has the good intention of\nclearing out bogus data by zeroing the area from the end of the incoming\ndata string to the assumed end of the buffer.  However, as we have\npreviously seen, doing so can easily result in OOB reads and writes in\nthe subsequent thread of execution.\n\nThe current suggestion from one of the HID maintainers is to remove the\nmemset() and simply return if the incoming event buffer size is not\nlarge enough to fill the associated report.\n\nSuggested-by Benjamin Tissoires \u0026lt;(CVE-2026-43048)\n\nIn the Linux kernel, there is a potential out-of-bounds access vulnerability in the ceph_handle_auth_reply() function of the libceph component. When processing messages of type CEPH_MSG_AUTH_REPLY, the value of the payload_len field is stored in a variable of type int. A value greater than INT_MAX leads to integer overflow and is interpreted as a negative value, which causes the pointer address to be decremented and subsequently accessed because ceph_decode_need() only checks that the memory access does not exceed the end address of the allocation. The vulnerability is fixed by changing the data type of payload_len to u32 and introducing additional sanity checks.(CVE-2026-43407)","status":"published","published":"2026-05-22T11:11:22Z","modified":"2026-08-18T01:20:03.128754584Z","cvss":[{"version":"3.1","score":9.1,"vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:H","level":"critical"}],"updated_at":"2026-11-02T15:52:46.449097Z"},{"id":"OESA-2026-2418","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:mm/mempolicy: fix migrate_to_node() assuming there is at least one VMA in a MMWe currently assume that there is at least one VMA in a MM, which isn ttrue.So we might end up having find_vma() return NULL, to then de-referenceNULL.  So properly handle find_vma() returning NULL.This fixes the report:Oops: general protection fault, probably for non-canonical address 0xdffffc0000000000: 0000 [#1] PREEMPT SMP KASAN PTIKASAN: null-ptr-deref in range [0x0000000000000000-0x0000000000000007]CPU: 1 UID: 0 PID: 6021 Comm: syz-executor284 Not tainted 6.12.0-rc7-syzkaller-00187-gf868cd251776 #0Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 10/30/2024RIP: 0010:migrate_to_node mm/mempolicy.c:1090 [inline]RIP: 0010:do_migrate_pages+0x403/0x6f0 mm/mempolicy.c:1194Code: ...RSP: 0018:ffffc9000375fd08 EFLAGS: 00010246RAX: 0000000000000000 RBX: ffffc9000375fd78 RCX: 0000000000000000RDX: ffff88807e171300 RSI: dffffc0000000000 RDI: ffff88803390c044RBP: ffff88807e171428 R08: 0000000000000014 R09: fffffbfff2039ef1R10: ffffffff901cf78f R11: 0000000000000000 R12: 0000000000000003R13: ffffc9000375fe90 R14: ffffc9000375fe98 R15: ffffc9000375fdf8FS:  00005555919e1380(0000) GS:ffff8880b8700000(0000) knlGS:0000000000000000CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033CR2: 00005555919e1ca8 CR3: 000000007f12a000 CR4: 00000000003526f0DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400Call Trace: \u0026lt;TASK\u0026gt; kernel_migrate_pages+0x5b2/0x750 mm/mempolicy.c:1709 __do_sys_migrate_pages mm/mempolicy.c:1727 [inline] __se_sys_migrate_pages mm/mempolicy.c:1723 [inline] __x64_sys_migrate_pages+0x96/0x100 mm/mempolicy.c:1723 do_syscall_x64 arch/x86/entry/common.c:52 [inline] do_syscall_64+0xcd/0x250 arch/x86/entry/common.c:83 entry_SYSCALL_64_after_hwframe+0x77/0x7f[akpm@linux-foundation.org: add unlikely()](CVE-2024-56611)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nPCI/MSI: Handle lack of irqdomain gracefully\n\nAlexandre observed a warning emitted from pci_msi_setup_msi_irqs() on a\nRISCV platform which does not provide PCI/MSI support:\n\n WARNING: CPU: 1 PID: 1 at drivers/pci/msi/msi.h:121 pci_msi_setup_msi_irqs+0x2c/0x32\n __pci_enable_msix_range+0x30c/0x596\n pci_msi_setup_msi_irqs+0x2c/0x32\n pci_alloc_irq_vectors_affinity+0xb8/0xe2\n\nRISCV uses hierarchical interrupt domains and correctly does not implement\nthe legacy fallback. The warning triggers from the legacy fallback stub.\n\nThat warning is bogus as the PCI/MSI layer knows whether a PCI/MSI parent\ndomain is associated with the device or not. There is a check for MSI-X,\nwhich has a legacy assumption. But that legacy fallback assumption is only\nvalid when legacy support is enabled, but otherwise the check should simply\nreturn -ENOTSUPP.\n\nLoongarch tripped over the same problem and blindly enabled legacy support\nwithout implementing the legacy fallbacks. There are weak implementations\nwhich return an error, so the problem was papered over.\n\nCorrect pci_msi_domain_supports() to evaluate the legacy mode and add\nthe missing supported check into the MSI enable path to complete it.(CVE-2024-56760)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nNFS: fix nfs_release_folio() to not deadlock via kcompactd writeback\n\nAdd PF_KCOMPACTD flag and current_is_kcompactd() helper to check for it so\nnfs_release_folio() can skip calling nfs_wb_folio() from kcompactd.\n\nOtherwise NFS can deadlock waiting for kcompactd enduced writeback which\nrecurses back to NFS (which triggers writeback to NFSD via NFS loopback\nmount on the same host, NFSD blocks waiting for XFS\u0026apos;s call to\n__filemap_get_folio):\n\n6070.550357] INFO: task kcompactd0:58 blocked for more than 4435 seconds.\n\n{---\n[58] \u0026quot;kcompactd0\u0026quot;\n[\u0026lt;0\u0026gt;] folio_wait_bit+0xe8/0x200\n[\u0026lt;0\u0026gt;] folio_wait_writeback+0x2b/0x80\n[\u0026lt;0\u0026gt;] nfs_wb_folio+0x80/0x1b0 [nfs]\n[\u0026lt;0\u0026gt;] nfs_release_folio+0x68/0x130 [nfs]\n[\u0026lt;0\u0026gt;] split_huge_page_to_list_to_order+0x362/0x840\n[\u0026lt;0\u0026gt;] migrate_pages_batch+0x43d/0xb90\n[\u0026lt;0\u0026gt;] migrate_pages_sync+0x9a/0x240\n[\u0026lt;0\u0026gt;] migrate_pages+0x93c/0x9f0\n[\u0026lt;0\u0026gt;] compact_zone+0x8e2/0x1030\n[\u0026lt;0\u0026gt;] compact_node+0xdb/0x120\n[\u0026lt;0\u0026gt;] kcompactd+0x121/0x2e0\n[\u0026lt;0\u0026gt;] kthread+0xcf/0x100\n[\u0026lt;0\u0026gt;] ret_from_fork+0x31/0x40\n[\u0026lt;0\u0026gt;] ret_from_fork_asm+0x1a/0x30\n---}\n\n[(CVE-2025-21908)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nhwpoison, memory_hotplug: lock folio before unmap hwpoisoned folio\n\nCommit b15c87263a69 (\u0026quot;hwpoison, memory_hotplug: allow hwpoisoned pages to\nbe offlined) add page poison checks in do_migrate_range in order to make\noffline hwpoisoned page possible by introducing isolate_lru_page and\ntry_to_unmap for hwpoisoned page.  However folio lock must be held before\ncalling try_to_unmap.  Add it to fix this problem.\n\nWarning will be produced if folio is not locked during unmap:\n\n  ------------[ cut here ]------------\n  kernel BUG at ./include/linux/swapops.h:400!\n  Internal error: Oops - BUG: 00000000f2000800 [#1] PREEMPT SMP\n  Modules linked in:\n  CPU: 4 UID: 0 PID: 411 Comm: bash Tainted: G        W          6.13.0-rc1-00016-g3c434c7ee82a-dirty #41\n  Tainted: [W]=WARN\n  Hardware name: QEMU QEMU Virtual Machine, BIOS 0.0.0 02/06/2015\n  pstate: 40400005 (nZcv daif +PAN -UAO -TCO -DIT -SSBS BTYPE=--)\n  pc : try_to_unmap_one+0xb08/0xd3c\n  lr : try_to_unmap_one+0x3dc/0xd3c\n  Call trace:\n   try_to_unmap_one+0xb08/0xd3c (P)\n   try_to_unmap_one+0x3dc/0xd3c (L)\n   rmap_walk_anon+0xdc/0x1f8\n   rmap_walk+0x3c/0x58\n   try_to_unmap+0x88/0x90\n   unmap_poisoned_folio+0x30/0xa8\n   do_migrate_range+0x4a0/0x568\n   offline_pages+0x5a4/0x670\n   memory_block_action+0x17c/0x374\n   memory_subsys_offline+0x3c/0x78\n   device_offline+0xa4/0xd0\n   state_store+0x8c/0xf0\n   dev_attr_store+0x18/0x2c\n   sysfs_kf_write+0x44/0x54\n   kernfs_fop_write_iter+0x118/0x1a8\n   vfs_write+0x3a8/0x4bc\n   ksys_write+0x6c/0xf8\n   __arm64_sys_write+0x1c/0x28\n   invoke_syscall+0x44/0x100\n   el0_svc_common.constprop.0+0x40/0xe0\n   do_el0_svc+0x1c/0x28\n   el0_svc+0x30/0xd0\n   el0t_64_sync_handler+0xc8/0xcc\n   el0t_64_sync+0x198/0x19c\n  Code: f9407be0 b5fff320 d4210000 17ffff97 (d4210000)\n  ---[ end trace 0000000000000000 ]---(CVE-2025-21931)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnet/mlx5: Bridge, fix the crash caused by LAG state check\n\nWhen removing LAG device from bridge, NETDEV_CHANGEUPPER event is\ntriggered. Driver finds the lower devices (PFs) to flush all the\noffloaded entries. And mlx5_lag_is_shared_fdb is checked, it returns\nfalse if one of PF is unloaded. In such case,\nmlx5_esw_bridge_lag_rep_get() and its caller return NULL, instead of\nthe alive PF, and the flush is skipped.\n\nBesides, the bridge fdb entry\u0026apos;s lastuse is updated in mlx5 bridge\nevent handler. But this SWITCHDEV_FDB_ADD_TO_BRIDGE event can be\nignored in this case because the upper interface for bond is deleted,\nand the entry will never be aged because lastuse is never updated.\n\nTo make things worse, as the entry is alive, mlx5 bridge workqueue\nkeeps sending that event, which is then handled by kernel bridge\nnotifier. It causes the following crash when accessing the passed bond\nnetdev which is already destroyed.\n\nTo fix this issue, remove such checks. LAG state is already checked in\ncommit 15f8f168952f (\u0026quot;net/mlx5: Bridge, verify LAG state when adding\nbond to bridge\u0026quot;), driver still need to skip offload if LAG becomes\ninvalid state after initialization.\n\n Oops: stack segment: 0000 [#1] SMP\n CPU: 3 UID: 0 PID: 23695 Comm: kworker/u40:3 Tainted: G           OE      6.11.0_mlnx #1\n Tainted: [O]=OOT_MODULE, [E]=UNSIGNED_MODULE\n Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS rel-1.13.0-0-gf21b5a4aeb02-prebuilt.qemu.org 04/01/2014\n Workqueue: mlx5_bridge_wq mlx5_esw_bridge_update_work [mlx5_core]\n RIP: 0010:br_switchdev_event+0x2c/0x110 [bridge]\n Code: 44 00 00 48 8b 02 48 f7 00 00 02 00 00 74 69 41 54 55 53 48 83 ec 08 48 8b a8 08 01 00 00 48 85 ed 74 4a 48 83 fe 02 48 89 d3 \u0026lt;4c\u0026gt; 8b 65 00 74 23 76 49 48 83 fe 05 74 7e 48 83 fe 06 75 2f 0f b7\n RSP: 0018:ffffc900092cfda0 EFLAGS: 00010297\n RAX: ffff888123bfe000 RBX: ffffc900092cfe08 RCX: 00000000ffffffff\n RDX: ffffc900092cfe08 RSI: 0000000000000001 RDI: ffffffffa0c585f0\n RBP: 6669746f6e690a30 R08: 0000000000000000 R09: ffff888123ae92c8\n R10: 0000000000000000 R11: fefefefefefefeff R12: ffff888123ae9c60\n R13: 0000000000000001 R14: ffffc900092cfe08 R15: 0000000000000000\n FS:  0000000000000000(0000) GS:ffff88852c980000(0000) knlGS:0000000000000000\n CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033\n CR2: 00007f15914c8734 CR3: 0000000002830005 CR4: 0000000000770ef0\n DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000\n DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400\n PKRU: 55555554\n Call Trace:\n  \u0026lt;TASK\u0026gt;\n  ? __die_body+0x1a/0x60\n  ? die+0x38/0x60\n  ? do_trap+0x10b/0x120\n  ? do_error_trap+0x64/0xa0\n  ? exc_stack_segment+0x33/0x50\n  ? asm_exc_stack_segment+0x22/0x30\n  ? br_switchdev_event+0x2c/0x110 [bridge]\n  ? sched_balance_newidle.isra.149+0x248/0x390\n  notifier_call_chain+0x4b/0xa0\n  atomic_notifier_call_chain+0x16/0x20\n  mlx5_esw_bridge_update+0xec/0x170 [mlx5_core]\n  mlx5_esw_bridge_update_work+0x19/0x40 [mlx5_core]\n  process_scheduled_works+0x81/0x390\n  worker_thread+0x106/0x250\n  ? bh_worker+0x110/0x110\n  kthread+0xb7/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  \u0026lt;/TASK\u0026gt;(CVE-2025-21970)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnet_sched: Prevent creation of classes with TC_H_ROOT\n\nThe function qdisc_tree_reduce_backlog() uses TC_H_ROOT as a termination\ncondition when traversing up the qdisc tree to update parent backlog\ncounters. However, if a class is created with classid TC_H_ROOT, the\ntraversal terminates prematurely at this class instead of reaching the\nactual root qdisc, causing parent statistics to be incorrectly maintained.\nIn case of DRR, this could lead to a crash as reported by Mingi Cho.\n\nPrevent the creation of any Qdisc class with classid TC_H_ROOT\n(0xFFFFFFFF) across all qdisc types, as suggested by Jamal.(CVE-2025-21971)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nsched: address a potential NULL pointer dereference in the GRED scheduler.\n\nIf kzalloc in gred_init returns a NULL pointer, the code follows the\nerror handling path, invoking gred_destroy. This, in turn, calls\ngred_offload, where memset could receive a NULL pointer as input,\npotentially leading to a kernel crash.\n\nWhen table-\u0026gt;opt is NULL in gred_init(), gred_change_table_def()\nis not called yet, so it is not necessary to call -\u0026gt;ndo_setup_tc()\nin gred_offload().(CVE-2025-21980)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nice: fix memory leak in aRFS after reset\n\nFix aRFS (accelerated Receive Flow Steering) structures memory leak by\nadding a checker to verify if aRFS memory is already allocated while\nconfiguring VSI. aRFS objects are allocated in two cases:\n- as part of VSI initialization (at probe), and\n- as part of reset handling\n\nHowever, VSI reconfiguration executed during reset involves memory\nallocation one more time, without prior releasing already allocated\nresources. This led to the memory leak with the following signature:\n\n[root@os-delivery ~]# cat /sys/kernel/debug/kmemleak\nunreferenced object 0xff3c1ca7252e6000 (size 8192):\n  comm \u0026quot;kworker/0:0\u0026quot;, pid 8, jiffies 4296833052\n  hex dump (first 32 bytes):\n    00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................\n    00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................\n  backtrace (crc 0):\n    [\u0026lt;ffffffff991ec485\u0026gt;] __kmalloc_cache_noprof+0x275/0x340\n    [\u0026lt;ffffffffc0a6e06a\u0026gt;] ice_init_arfs+0x3a/0xe0 [ice]\n    [\u0026lt;ffffffffc09f1027\u0026gt;] ice_vsi_cfg_def+0x607/0x850 [ice]\n    [\u0026lt;ffffffffc09f244b\u0026gt;] ice_vsi_setup+0x5b/0x130 [ice]\n    [\u0026lt;ffffffffc09c2131\u0026gt;] ice_init+0x1c1/0x460 [ice]\n    [\u0026lt;ffffffffc09c64af\u0026gt;] ice_probe+0x2af/0x520 [ice]\n    [\u0026lt;ffffffff994fbcd3\u0026gt;] local_pci_probe+0x43/0xa0\n    [\u0026lt;ffffffff98f07103\u0026gt;] work_for_cpu_fn+0x13/0x20\n    [\u0026lt;ffffffff98f0b6d9\u0026gt;] process_one_work+0x179/0x390\n    [\u0026lt;ffffffff98f0c1e9\u0026gt;] worker_thread+0x239/0x340\n    [\u0026lt;ffffffff98f14abc\u0026gt;] kthread+0xcc/0x100\n    [\u0026lt;ffffffff98e45a6d\u0026gt;] ret_from_fork+0x2d/0x50\n    [\u0026lt;ffffffff98e083ba\u0026gt;] ret_from_fork_asm+0x1a/0x30\n    ...(CVE-2025-21981)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnet: switchdev: Convert blocking notification chain to a raw one\n\nA blocking notification chain uses a read-write semaphore to protect the\nintegrity of the chain. The semaphore is acquired for writing when\nadding / removing notifiers to / from the chain and acquired for reading\nwhen traversing the chain and informing notifiers about an event.\n\nIn case of the blocking switchdev notification chain, recursive\nnotifications are possible which leads to the semaphore being acquired\ntwice for reading and to lockdep warnings being generated [1].\n\nSpecifically, this can happen when the bridge driver processes a\nSWITCHDEV_BRPORT_UNOFFLOADED event which causes it to emit notifications\nabout deferred events when calling switchdev_deferred_process().\n\nFix this by converting the notification chain to a raw notification\nchain in a similar fashion to the netdev notification chain. Protect\nthe chain using the RTNL mutex by acquiring it when modifying the chain.\nEvents are always informed under the RTNL mutex, but add an assertion in\ncall_switchdev_blocking_notifiers() to make sure this is not violated in\nthe future.\n\nMaintain the \u0026quot;blocking\u0026quot; prefix as events are always emitted from process\ncontext and listeners are allowed to block.\n\n[1]:\nWARNING: possible recursive locking detected\n6.14.0-rc4-custom-g079270089484 #1 Not tainted\n--------------------------------------------\nip/52731 is trying to acquire lock:\nffffffff850918d8 ((switchdev_blocking_notif_chain).rwsem){++++}-{4:4}, at: blocking_notifier_call_chain+0x58/0xa0\n\nbut task is already holding lock:\nffffffff850918d8 ((switchdev_blocking_notif_chain).rwsem){++++}-{4:4}, at: blocking_notifier_call_chain+0x58/0xa0\n\nother info that might help us debug this:\nPossible unsafe locking scenario:\nCPU0\n----\nlock((switchdev_blocking_notif_chain).rwsem);\nlock((switchdev_blocking_notif_chain).rwsem);\n\n*** DEADLOCK ***\nMay be due to missing lock nesting notation\n3 locks held by ip/52731:\n #0: ffffffff84f795b0 (rtnl_mutex){+.+.}-{4:4}, at: rtnl_newlink+0x727/0x1dc0\n #1: ffffffff8731f628 (\u0026amp;net-\u0026gt;rtnl_mutex){+.+.}-{4:4}, at: rtnl_newlink+0x790/0x1dc0\n #2: ffffffff850918d8 ((switchdev_blocking_notif_chain).rwsem){++++}-{4:4}, at: blocking_notifier_call_chain+0x58/0xa0\n\nstack backtrace:\n...\n? __pfx_down_read+0x10/0x10\n? __pfx_mark_lock+0x10/0x10\n? __pfx_switchdev_port_attr_set_deferred+0x10/0x10\nblocking_notifier_call_chain+0x58/0xa0\nswitchdev_port_attr_notify.constprop.0+0xb3/0x1b0\n? __pfx_switchdev_port_attr_notify.constprop.0+0x10/0x10\n? mark_held_locks+0x94/0xe0\n? switchdev_deferred_process+0x11a/0x340\nswitchdev_port_attr_set_deferred+0x27/0xd0\nswitchdev_deferred_process+0x164/0x340\nbr_switchdev_port_unoffload+0xc8/0x100 [bridge]\nbr_switchdev_blocking_event+0x29f/0x580 [bridge]\nnotifier_call_chain+0xa2/0x440\nblocking_notifier_call_chain+0x6e/0xa0\nswitchdev_bridge_port_unoffload+0xde/0x1a0\n...(CVE-2025-21986)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ndrm/sched: Fix fence reference count leak\n\nThe last_scheduled fence leaks when an entity is being killed and adding\nthe cleanup callback fails.\n\nDecrement the reference count of prev when dma_fence_add_callback()\nfails, ensuring proper balance.\n\n[phasta: add git tag info for stable kernel](CVE-2025-21995)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\naccel/qaic: Fix integer overflow in qaic_validate_req()\n\nThese are u64 variables that come from the user via\nqaic_attach_slice_bo_ioctl().  Use check_add_overflow() to ensure that\nthe math doesn\u0026apos;t have an integer wrapping bug.(CVE-2025-22001)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nregulator: dummy: force synchronous probing\n\nSometimes I get a NULL pointer dereference at boot time in kobject_get()\nwith the following call stack:\n\nanatop_regulator_probe()\n devm_regulator_register()\n  regulator_register()\n   regulator_resolve_supply()\n    kobject_get()\n\nBy placing some extra BUG_ON() statements I could verify that this is\nraised because probing of the \u0026apos;dummy\u0026apos; regulator driver is not completed\n(\u0026apos;dummy_regulator_rdev\u0026apos; is still NULL).\n\nIn the JTAG debugger I can see that dummy_regulator_probe() and\nanatop_regulator_probe() can be run by different kernel threads\n(kworker/u4:*).  I haven\u0026apos;t further investigated whether this can be\nchanged or if there are other possibilities to force synchronization\nbetween these two probe routines.  On the other hand I don\u0026apos;t expect much\nboot time penalty by probing the \u0026apos;dummy\u0026apos; regulator synchronously.(CVE-2025-22009)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nspufs: fix a leak in spufs_create_context()\n\nLeak fixes back in 2008 missed one case - if we are trying to set affinity\nand spufs_mkdir() fails, we need to drop the reference to neighbor.(CVE-2025-22071)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nRevert \u0026quot;smb: client: fix TCP timers deadlock after rmmod\u0026quot;\n\nThis reverts commit e9f2517a3e18a54a3943c098d2226b245d488801.\n\nCommit e9f2517a3e18 (\u0026quot;smb: client: fix TCP timers deadlock after\nrmmod\u0026quot;) is intended to fix a null-ptr-deref in LOCKDEP, which is\nmentioned as CVE-2024-54680, but is actually did not fix anything;\nThe issue can be reproduced on top of it. [0]\n\nAlso, it reverted the change by commit ef7134c7fc48 (\u0026quot;smb: client:\nFix use-after-free of network namespace.\u0026quot;) and introduced a real\nissue by reviving the kernel TCP socket.\n\nWhen a reconnect happens for a CIFS connection, the socket state\ntransitions to FIN_WAIT_1.  Then, inet_csk_clear_xmit_timers_sync()\nin tcp_close() stops all timers for the socket.\n\nIf an incoming FIN packet is lost, the socket will stay at FIN_WAIT_1\nforever, and such sockets could be leaked up to net.ipv4.tcp_max_orphans.\n\nUsually, FIN can be retransmitted by the peer, but if the peer aborts\nthe connection, the issue comes into reality.\n\nI warned about this privately by pointing out the exact report [1],\nbut the bogus fix was finally merged.\n\nSo, we should not stop the timers to finally kill the connection on\nour side in that case, meaning we must not use a kernel socket for\nTCP whose sk-\u0026gt;sk_net_refcnt is 0.\n\nThe kernel socket does not have a reference to its netns to make it\npossible to tear down netns without cleaning up every resource in it.\n\nFor example, tunnel devices use a UDP socket internally, but we can\ndestroy netns without removing such devices and let it complete\nduring exit.  Otherwise, netns would be leaked when the last application\ndied.\n\nHowever, this is problematic for TCP sockets because TCP has timers to\nclose the connection gracefully even after the socket is close()d.  The\nlifetime of the socket and its netns is different from the lifetime of\nthe underlying connection.\n\nIf the socket user does not maintain the netns lifetime, the timer could\nbe fired after the socket is close()d and its netns is freed up, resulting\nin use-after-free.\n\nActually, we have seen so many similar issues and converted such sockets\nto have a reference to netns.\n\nThat\u0026apos;s why I converted the CIFS client socket to have a reference to\nnetns (sk-\u0026gt;sk_net_refcnt == 1), which is somehow mentioned as out-of-scope\nof CIFS and technically wrong in e9f2517a3e18, but **is in-scope and right\nfix**.\n\nRegarding the LOCKDEP issue, we can prevent the module unload by\nbumping the module refcount when switching the LOCKDDEP key in\nsock_lock_init_class_and_name(). [2]\n\nFor a while, let\u0026apos;s revert the bogus fix.\n\nNote that now we can use sk_net_refcnt_upgrade() for the socket\nconversion, but I\u0026apos;ll do so later separately to make backport easy.(CVE-2025-22077)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nwatch_queue: fix pipe accounting mismatch\n\nCurrently, watch_queue_set_size() modifies the pipe buffers charged to\nuser-\u0026gt;pipe_bufs without updating the pipe-\u0026gt;nr_accounted on the pipe\nitself, due to the if (!pipe_has_watch_queue()) test in\npipe_resize_ring(). This means that when the pipe is ultimately freed,\nwe decrement user-\u0026gt;pipe_bufs by something other than what than we had\ncharged to it, potentially leading to an underflow. This in turn can\ncause subsequent too_many_pipe_buffers_soft() tests to fail with -EPERM.\n\nTo remedy this, explicitly account for the pipe usage in\nwatch_queue_set_size() to match the number set via account_pipe_buffers()\n\n(It\u0026apos;s unclear why watch_queue_set_size() does not update nr_accounted;\nit may be due to intentional overprovisioning in watch_queue_set_size()?)(CVE-2025-23138)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nmedia: venus: hfi_parser: add check to avoid out of bound access\n\nThere is a possibility that init_codecs is invoked multiple times during\nmanipulated payload from video firmware. In such case, if codecs_count\ncan get incremented to value more than MAX_CODEC_NUM, there can be OOB\naccess. Reset the count so that it always starts from beginning.(CVE-2025-23157)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\njfs: add sanity check for agwidth in dbMount\n\nThe width in dmapctl of the AG is zero, it trigger a divide error when\ncalculating the control page level in dbAllocAG.\n\nTo avoid this issue, add a check for agwidth in dbAllocAG.(CVE-2025-37740)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\niommu/mediatek: Fix NULL pointer deference in mtk_iommu_device_group\n\nCurrently, mtk_iommu calls during probe iommu_device_register before\nthe hw_list from driver data is initialized. Since iommu probing issue\nfix, it leads to NULL pointer dereference in mtk_iommu_device_group when\nhw_list is accessed with list_first_entry (not null safe).\n\nSo, change the call order to ensure iommu_device_register is called\nafter the driver data are initialized.(CVE-2025-37748)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ndrm/amd/pm: Prevent division by zero\n\nThe user can set any speed value.\nIf speed is greater than UINT_MAX/8, division by zero is possible.\n\nFound by Linux Verification Center (linuxtesting.org) with SVACE.(CVE-2025-37766)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ndrm/amd/pm: Prevent division by zero\n\nThe user can set any speed value.\nIf speed is greater than UINT_MAX/8, division by zero is possible.\n\nFound by Linux Verification Center (linuxtesting.org) with SVACE.(CVE-2025-37768)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ndrm/amd/pm: Prevent division by zero\n\nThe user can set any speed value.\nIf speed is greater than UINT_MAX/8, division by zero is possible.\n\nFound by Linux Verification Center (linuxtesting.org) with SVACE.(CVE-2025-37770)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ndrm/amd/pm: Prevent division by zero\n\nThe user can set any speed value.\nIf speed is greater than UINT_MAX/8, division by zero is possible.\n\nFound by Linux Verification Center (linuxtesting.org) with SVACE.(CVE-2025-37771)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nksmbd: Fix dangling pointer in krb_authenticate\n\nkrb_authenticate frees sess-\u0026gt;user and does not set the pointer\nto NULL. It calls ksmbd_krb5_authenticate to reinitialise\nsess-\u0026gt;user but that function may return without doing so. If\nthat happens then smb2_sess_setup, which calls krb_authenticate,\nwill be accessing free\u0026apos;d memory when it later uses sess-\u0026gt;user.(CVE-2025-37778)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nASoC: Intel: avs: Fix null-ptr-deref in avs_component_probe()\n\ndevm_kasprintf() returns NULL when memory allocation fails. Currently,\navs_component_probe() does not check for this case, which results in a\nNULL pointer dereference.(CVE-2025-37793)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nsound/virtio: Fix cancel_sync warnings on uninitialized work_structs\n\nBetty reported hitting the following warning:\n\n[    8.709131][  T221] WARNING: CPU: 2 PID: 221 at kernel/workqueue.c:4182\n...\n[    8.713282][  T221] Call trace:\n[    8.713365][  T221]  __flush_work+0x8d0/0x914\n[    8.713468][  T221]  __cancel_work_sync+0xac/0xfc\n[    8.713570][  T221]  cancel_work_sync+0x24/0x34\n[    8.713667][  T221]  virtsnd_remove+0xa8/0xf8 [virtio_snd ab15f34d0dd772f6d11327e08a81d46dc9c36276]\n[    8.713868][  T221]  virtsnd_probe+0x48c/0x664 [virtio_snd ab15f34d0dd772f6d11327e08a81d46dc9c36276]\n[    8.714035][  T221]  virtio_dev_probe+0x28c/0x390\n[    8.714139][  T221]  really_probe+0x1bc/0x4c8\n...\n\nIt seems we\u0026apos;re hitting the error path in virtsnd_probe(), which\ntriggers a virtsnd_remove() which iterates over the substreams\ncalling cancel_work_sync() on the elapsed_period work_struct.\n\nLooking at the code, from earlier in:\nvirtsnd_probe()-\u0026gt;virtsnd_build_devs()-\u0026gt;virtsnd_pcm_parse_cfg()\n\nWe set snd-\u0026gt;nsubstreams, allocate the snd-\u0026gt;substreams, and if\nwe then hit an error on the info allocation or something in\nvirtsnd_ctl_query_info() fails, we will exit without having\ninitialized the elapsed_period work_struct.\n\nWhen that error path unwinds we then call virtsnd_remove()\nwhich as long as the substreams array is allocated, will iterate\nthrough calling cancel_work_sync() on the uninitialized work\nstruct hitting this warning.\n\nTakashi Iwai suggested this fix, which initializes the substreams\nstructure right after allocation, so that if we hit the error\npaths we avoid trying to cleanup uninitialized data.\n\nNote: I have not yet managed to reproduce the issue myself, so\nthis patch has had limited testing.\n\nFeedback or thoughts would be appreciated!(CVE-2025-37805)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nmisc: microchip: pci1xxxx: Fix Kernel panic during IRQ handler registration\n\nResolve kernel panic while accessing IRQ handler associated with the\ngenerated IRQ. This is done by acquiring the spinlock and storing the\ncurrent interrupt state before handling the interrupt request using\ngeneric_handle_irq.\n\nA previous fix patch was submitted where \u0026apos;generic_handle_irq\u0026apos; was\nreplaced with \u0026apos;handle_nested_irq\u0026apos;. However, this change also causes\nthe kernel panic where after determining which GPIO triggered the\ninterrupt and attempting to call handle_nested_irq with the mapped\nIRQ number, leads to a failure in locating the registered handler.(CVE-2025-37815)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ncpufreq: apple-soc: Fix null-ptr-deref in apple_soc_cpufreq_get_rate()\n\ncpufreq_cpu_get_raw() can return NULL when the target CPU is not present\nin the policy-\u0026gt;cpus mask. apple_soc_cpufreq_get_rate() does not check\nfor this case, which results in a NULL pointer dereference.(CVE-2025-37831)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ncifs: avoid NULL pointer dereference in dbg call\n\ncifs_server_dbg() implies server to be non-NULL so\nmove call under condition to avoid NULL pointer dereference.\n\nFound by Linux Verification Center (linuxtesting.org) with SVACE.(CVE-2025-37844)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ndrm/amdkfd: debugfs hang_hws skip GPU with MES\n\ndebugfs hang_hws is used by GPU reset test with HWS, for MES this crash\nthe kernel with NULL pointer access because dqm-\u0026gt;packet_mgr is not setup\nfor MES path.\n\nSkip GPU with MES for now, MES hang_hws debugfs interface will be\nsupported later.(CVE-2025-37853)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nusb: gadget: aspeed: Add NULL pointer check in ast_vhub_init_dev()\n\nThe variable d-\u0026gt;name, returned by devm_kasprintf(), could be NULL.\nA pointer check is added to prevent potential NULL pointer dereference.\nThis is similar to the fix in commit 3027e7b15b02\n(\u0026quot;ice: Fix some null pointer dereference issues in ice_ptp.c\u0026quot;).\n\nThis issue is found by our static analysis tool(CVE-2025-37881)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nASoC: ops: Consistently treat platform_max as control value\n\nThis reverts commit 9bdd10d57a88 (\u0026quot;ASoC: ops: Shift tested values in\nsnd_soc_put_volsw() by +min\u0026quot;), and makes some additional related\nupdates.\n\nThere are two ways the platform_max could be interpreted; the maximum\nregister value, or the maximum value the control can be set to. The\npatch moved from treating the value as a control value to a register\none. When the patch was applied it was technically correct as\nsnd_soc_limit_volume() also used the register interpretation. However,\neven then most of the other usages treated platform_max as a\ncontrol value, and snd_soc_limit_volume() has since been updated to\nalso do so in commit fb9ad24485087 (\u0026quot;ASoC: ops: add correct range\ncheck for limiting volume\u0026quot;). That patch however, missed updating\nsnd_soc_put_volsw() back to the control interpretation, and fixing\nsnd_soc_info_volsw_range(). The control interpretation makes more\nsense as limiting is typically done from the machine driver, so it is\nappropriate to use the customer facing representation rather than the\ninternal codec representation. Update all the code to consistently use\nthis interpretation of platform_max.\n\nFinally, also add some comments to the soc_mixer_control struct to\nhopefully avoid further patches switching between the two approaches.(CVE-2025-37889)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nfirmware: arm_scmi: Balance device refcount when destroying devices\n\nUsing device_find_child() to lookup the proper SCMI device to destroy\ncauses an unbalance in device refcount, since device_find_child() calls an\nimplicit get_device(): this, in turns, inhibits the call of the provided\nrelease methods upon devices destruction.\n\nAs a consequence, one of the structures that is not freed properly upon\ndestruction is the internal struct device_private dev-\u0026gt;p populated by the\ndrivers subsystem core.\n\nKMemleak detects this situation since loading/unloding some SCMI driver\ncauses related devices to be created/destroyed without calling any\ndevice_release method.\n\nunreferenced object 0xffff00000f583800 (size 512):\n  comm \u0026quot;insmod\u0026quot;, pid 227, jiffies 4294912190\n  hex dump (first 32 bytes):\n    00 00 00 00 ad 4e ad de ff ff ff ff 00 00 00 00  .....N..........\n    ff ff ff ff ff ff ff ff 60 36 1d 8a 00 80 ff ff  ........`6......\n  backtrace (crc 114e2eed):\n    kmemleak_alloc+0xbc/0xd8\n    __kmalloc_cache_noprof+0x2dc/0x398\n    device_add+0x954/0x12d0\n    device_register+0x28/0x40\n    __scmi_device_create.part.0+0x1bc/0x380\n    scmi_device_create+0x2d0/0x390\n    scmi_create_protocol_devices+0x74/0xf8\n    scmi_device_request_notifier+0x1f8/0x2a8\n    notifier_call_chain+0x110/0x3b0\n    blocking_notifier_call_chain+0x70/0xb0\n    scmi_driver_register+0x350/0x7f0\n    0xffff80000a3b3038\n    do_one_initcall+0x12c/0x730\n    do_init_module+0x1dc/0x640\n    load_module+0x4b20/0x5b70\n    init_module_from_file+0xec/0x158\n\n$ ./scripts/faddr2line ./vmlinux device_add+0x954/0x12d0\ndevice_add+0x954/0x12d0:\nkmalloc_noprof at include/linux/slab.h:901\n(inlined by) kzalloc_noprof at include/linux/slab.h:1037\n(inlined by) device_private_init at drivers/base/core.c:3510\n(inlined by) device_add at drivers/base/core.c:3561\n\nBalance device refcount by issuing a put_device() on devices found via\ndevice_find_child().(CVE-2025-37905)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nBluetooth: btusb: avoid NULL pointer dereference in skb_dequeue()\n\nA NULL pointer dereference can occur in skb_dequeue() when processing a\nQCA firmware crash dump on WCN7851 (0489:e0f3).\n\n[ 93.672166] Bluetooth: hci0: ACL memdump size(589824)\n\n[ 93.672475] BUG: kernel NULL pointer dereference, address: 0000000000000008\n[ 93.672517] Workqueue: hci0 hci_devcd_rx [bluetooth]\n[ 93.672598] RIP: 0010:skb_dequeue+0x50/0x80\n\nThe issue stems from handle_dump_pkt_qca() returning 0 even when a dump\npacket is successfully processed. This is because it incorrectly\nforwards the return value of hci_devcd_init() (which returns 0 on\nsuccess). As a result, the caller (btusb_recv_acl_qca() or\nbtusb_recv_evt_qca()) assumes the packet was not handled and passes it\nto hci_recv_frame(), leading to premature kfree() of the skb.\n\nLater, hci_devcd_rx() attempts to dequeue the same skb from the dump\nqueue, resulting in a NULL pointer dereference.\n\nFix this by:\n1. Making handle_dump_pkt_qca() return 0 on success and negative errno\n   on failure, consistent with kernel conventions.\n2. Splitting dump packet detection into separate functions for ACL\n   and event packets for better structure and readability.\n\nThis ensures dump packets are properly identified and consumed, avoiding\ndouble handling and preventing NULL pointer access.(CVE-2025-37918)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nksmbd: prevent out-of-bounds stream writes by validating *pos\n\nksmbd_vfs_stream_write() did not validate whether the write offset\n(*pos) was within the bounds of the existing stream data length (v_len).\nIf *pos was greater than or equal to v_len, this could lead to an\nout-of-bounds memory write.\n\nThis patch adds a check to ensure *pos is less than v_len before\nproceeding. If the condition fails, -EINVAL is returned.(CVE-2025-37947)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nusb: typec: ucsi: displayport: Fix deadlock\n\nThis patch introduces the ucsi_con_mutex_lock / ucsi_con_mutex_unlock\nfunctions to the UCSI driver. ucsi_con_mutex_lock ensures the connector\nmutex is only locked if a connection is established and the partner pointer\nis valid. This resolves a deadlock scenario where\nucsi_displayport_remove_partner holds con-\u0026gt;mutex waiting for\ndp_altmode_work to complete while dp_altmode_work attempts to acquire it.(CVE-2025-37967)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ndmaengine: idxd: Refactor remove call with idxd_cleanup() helper\n\nThe idxd_cleanup() helper cleans up perfmon, interrupts, internals and\nso on. Refactor remove call with the idxd_cleanup() helper to avoid code\nduplication. Note, this also fixes the missing put_device() for idxd\ngroups, enginces and wqs.(CVE-2025-38014)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nvxlan: Annotate FDB data races\n\nThe \u0026apos;used\u0026apos; and \u0026apos;updated\u0026apos; fields in the FDB entry structure can be\naccessed concurrently by multiple threads, leading to reports such as\n[1]. Can be reproduced using [2].\n\nSuppress these reports by annotating these accesses using\nREAD_ONCE() / WRITE_ONCE().\n\n[1]\nBUG: KCSAN: data-race in vxlan_xmit / vxlan_xmit\n\nwrite to 0xffff942604d263a8 of 8 bytes by task 286 on cpu 0:\n vxlan_xmit+0xb29/0x2380\n dev_hard_start_xmit+0x84/0x2f0\n __dev_queue_xmit+0x45a/0x1650\n packet_xmit+0x100/0x150\n packet_sendmsg+0x2114/0x2ac0\n __sys_sendto+0x318/0x330\n __x64_sys_sendto+0x76/0x90\n x64_sys_call+0x14e8/0x1c00\n do_syscall_64+0x9e/0x1a0\n entry_SYSCALL_64_after_hwframe+0x77/0x7f\n\nread to 0xffff942604d263a8 of 8 bytes by task 287 on cpu 2:\n vxlan_xmit+0xadf/0x2380\n dev_hard_start_xmit+0x84/0x2f0\n __dev_queue_xmit+0x45a/0x1650\n packet_xmit+0x100/0x150\n packet_sendmsg+0x2114/0x2ac0\n __sys_sendto+0x318/0x330\n __x64_sys_sendto+0x76/0x90\n x64_sys_call+0x14e8/0x1c00\n do_syscall_64+0x9e/0x1a0\n entry_SYSCALL_64_after_hwframe+0x77/0x7f\n\nvalue changed: 0x00000000fffbac6e -\u0026gt; 0x00000000fffbac6f\n\nReported by Kernel Concurrency Sanitizer on:\nCPU: 2 UID: 0 PID: 287 Comm: mausezahn Not tainted 6.13.0-rc7-01544-gb4b270f11a02 #5\nHardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.16.3-3.fc41 04/01/2014\n\n[2]\n #!/bin/bash\n\n set +H\n echo whitelist \u0026gt; /sys/kernel/debug/kcsan\n echo !vxlan_xmit \u0026gt; /sys/kernel/debug/kcsan\n\n ip link add name vx0 up type vxlan id 10010 dstport 4789 local 192.0.2.1\n bridge fdb add 00:11:22:33:44:55 dev vx0 self static dst 198.51.100.1\n taskset -c 0 mausezahn vx0 -a own -b 00:11:22:33:44:55 -c 0 -q \u0026amp;\n taskset -c 2 mausezahn vx0 -a own -b 00:11:22:33:44:55 -c 0 -q \u0026amp;(CVE-2025-38037)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nfirmware: arm_ffa: Set dma_mask for ffa devices\n\nSet dma_mask for FFA devices, otherwise DMA allocation using the device pointer\nlead to following warning:\n\nWARNING: CPU: 1 PID: 1 at kernel/dma/mapping.c:597 dma_alloc_attrs+0xe0/0x124(CVE-2025-38043)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nsmb: client: Fix use-after-free in cifs_fill_dirent\n\nThere is a race condition in the readdir concurrency process, which may\naccess the rsp buffer after it has been released, triggering the\nfollowing KASAN warning.\n\n ==================================================================\n BUG: KASAN: slab-use-after-free in cifs_fill_dirent+0xb03/0xb60 [cifs]\n Read of size 4 at addr ffff8880099b819c by task a.out/342975\n\n CPU: 2 UID: 0 PID: 342975 Comm: a.out Not tainted 6.15.0-rc6+ #240 PREEMPT(full)\n Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.16.1-2.fc37 04/01/2014\n Call Trace:\n  \u0026lt;TASK\u0026gt;\n  dump_stack_lvl+0x53/0x70\n  print_report+0xce/0x640\n  kasan_report+0xb8/0xf0\n  cifs_fill_dirent+0xb03/0xb60 [cifs]\n  cifs_readdir+0x12cb/0x3190 [cifs]\n  iterate_dir+0x1a1/0x520\n  __x64_sys_getdents+0x134/0x220\n  do_syscall_64+0x4b/0x110\n  entry_SYSCALL_64_after_hwframe+0x76/0x7e\n RIP: 0033:0x7f996f64b9f9\n Code: ff c3 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 44 00 00 48 89 f8 48 89\n f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 \u0026lt;48\u0026gt; 3d 01\n f0 ff ff  0d f7 c3 0c 00 f7 d8 64 89 8\n RSP: 002b:00007f996f53de78 EFLAGS: 00000207 ORIG_RAX: 000000000000004e\n RAX: ffffffffffffffda RBX: 00007f996f53ecdc RCX: 00007f996f64b9f9\n RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000000000003\n RBP: 00007f996f53dea0 R08: 0000000000000000 R09: 0000000000000000\n R10: 0000000000000000 R11: 0000000000000207 R12: ffffffffffffff88\n R13: 0000000000000000 R14: 00007ffc8cd9a500 R15: 00007f996f51e000\n  \u0026lt;/TASK\u0026gt;\n\n Allocated by task 408:\n  kasan_save_stack+0x20/0x40\n  kasan_save_track+0x14/0x30\n  __kasan_slab_alloc+0x6e/0x70\n  kmem_cache_alloc_noprof+0x117/0x3d0\n  mempool_alloc_noprof+0xf2/0x2c0\n  cifs_buf_get+0x36/0x80 [cifs]\n  allocate_buffers+0x1d2/0x330 [cifs]\n  cifs_demultiplex_thread+0x22b/0x2690 [cifs]\n  kthread+0x394/0x720\n  ret_from_fork+0x34/0x70\n  ret_from_fork_asm+0x1a/0x30\n\n Freed by task 342979:\n  kasan_save_stack+0x20/0x40\n  kasan_save_track+0x14/0x30\n  kasan_save_free_info+0x3b/0x60\n  __kasan_slab_free+0x37/0x50\n  kmem_cache_free+0x2b8/0x500\n  cifs_buf_release+0x3c/0x70 [cifs]\n  cifs_readdir+0x1c97/0x3190 [cifs]\n  iterate_dir+0x1a1/0x520\n  __x64_sys_getdents64+0x134/0x220\n  do_syscall_64+0x4b/0x110\n  entry_SYSCALL_64_after_hwframe+0x76/0x7e\n\n The buggy address belongs to the object at ffff8880099b8000\n  which belongs to the cache cifs_request of size 16588\n The buggy address is located 412 bytes inside of\n  freed 16588-byte region [ffff8880099b8000, ffff8880099bc0cc)\n\n The buggy address belongs to the physical page:\n page: refcount:0 mapcount:0 mapping:0000000000000000 index:0x0 pfn:0x99b8\n head: order:3 mapcount:0 entire_mapcount:0 nr_pages_mapped:0 pincount:0\n anon flags: 0x80000000000040(head|node=0|zone=1)\n page_type: f5(slab)\n raw: 0080000000000040 ffff888001e03400 0000000000000000 dead000000000001\n raw: 0000000000000000 0000000000010001 00000000f5000000 0000000000000000\n head: 0080000000000040 ffff888001e03400 0000000000000000 dead000000000001\n head: 0000000000000000 0000000000010001 00000000f5000000 0000000000000000\n head: 0080000000000003 ffffea0000266e01 00000000ffffffff 00000000ffffffff\n head: ffffffffffffffff 0000000000000000 00000000ffffffff 0000000000000008\n page dumped because: kasan: bad access detected\n\n Memory state around the buggy address:\n  ffff8880099b8080: fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb\n  ffff8880099b8100: fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb\n \u0026gt;ffff8880099b8180: fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb\n                             ^\n  ffff8880099b8200: fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb\n  ffff8880099b8280: fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb\n ==================================================================\n\nPOC is available in the link [1].\n\nThe problem triggering process is as follows:\n\nProcess 1                       Process 2\n-----------------------------------\n---truncated---(CVE-2025-38051)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nvirtio: break and reset virtio devices on device_shutdown()\n\nHongyu reported a hang on kexec in a VM. QEMU reported invalid memory\naccesses during the hang.\n\n\tInvalid read at addr 0x102877002, size 2, region \u0026apos;(null)\u0026apos;, reason: rejected\n\tInvalid write at addr 0x102877A44, size 2, region \u0026apos;(null)\u0026apos;, reason: rejected\n\t...\n\nIt was traced down to virtio-console. Kexec works fine if virtio-console\nis not in use.\n\nThe issue is that virtio-console continues to write to the MMIO even after\nunderlying virtio-pci device is reset.\n\nAdditionally, Eric noticed that IOMMUs are reset before devices, if\ndevices are not reset on shutdown they continue to poke at guest memory\nand get errors from the IOMMU. Some devices get wedged then.\n\nThe problem can be solved by breaking all virtio devices on virtio\nbus shutdown, then resetting them.(CVE-2025-38064)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nACPI: CPPC: Fix NULL pointer dereference when nosmp is used\n\nWith nosmp in cmdline, other CPUs are not brought up, leaving\ntheir cpc_desc_ptr NULL. CPU0\u0026apos;s iteration via for_each_possible_cpu()\ndereferences these NULL pointers, causing panic.\n\nPanic backtrace:\n\n[    0.401123] Unable to handle kernel NULL pointer dereference at virtual address 00000000000000b8\n...\n[    0.403255] [\u0026lt;ffffffff809a5818\u0026gt;] cppc_allow_fast_switch+0x6a/0xd4\n...\nKernel panic - not syncing: Attempted to kill init!\n\n[ rjw: New subject ](CVE-2025-38113)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ngve: add missing NULL check for gve_alloc_pending_packet() in TX DQO\n\ngve_alloc_pending_packet() can return NULL, but gve_tx_add_skb_dqo()\ndid not check for this case before dereferencing the returned pointer.\n\nAdd a missing NULL check to prevent a potential NULL pointer\ndereference when allocation fails.\n\nThis improves robustness in low-memory scenarios.(CVE-2025-38122)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnet: wwan: t7xx: Fix napi rx poll issue\n\nWhen driver handles the napi rx polling requests, the netdev might\nhave been released by the dellink logic triggered by the disconnect\noperation on user plane. However, in the logic of processing skb in\npolling, an invalid netdev is still being used, which causes a panic.\n\nBUG: kernel NULL pointer dereference, address: 00000000000000f1\nOops: 0000 [#1] PREEMPT SMP NOPTI\nRIP: 0010:dev_gro_receive+0x3a/0x620\n[...]\nCall Trace:\n \u0026lt;IRQ\u0026gt;\n ? __die_body+0x68/0xb0\n ? page_fault_oops+0x379/0x3e0\n ? exc_page_fault+0x4f/0xa0\n ? asm_exc_page_fault+0x22/0x30\n ? __pfx_t7xx_ccmni_recv_skb+0x10/0x10 [mtk_t7xx (HASH:1400 7)]\n ? dev_gro_receive+0x3a/0x620\n napi_gro_receive+0xad/0x170\n t7xx_ccmni_recv_skb+0x48/0x70 [mtk_t7xx (HASH:1400 7)]\n t7xx_dpmaif_napi_rx_poll+0x590/0x800 [mtk_t7xx (HASH:1400 7)]\n net_rx_action+0x103/0x470\n irq_exit_rcu+0x13a/0x310\n sysvec_apic_timer_interrupt+0x56/0x90\n \u0026lt;/IRQ\u0026gt;(CVE-2025-38123)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ncoresight: prevent deactivate active config while enabling the config\n\nWhile enable active config via cscfg_csdev_enable_active_config(),\nactive config could be deactivated via configfs\u0026apos; sysfs interface.\nThis could make UAF issue in below scenario:\n\nCPU0                                          CPU1\n(sysfs enable)                                load module\n                                              cscfg_load_config_sets()\n                                              activate config. // sysfs\n                                              (sys_active_cnt == 1)\n...\ncscfg_csdev_enable_active_config()\nlock(csdev-\u0026gt;cscfg_csdev_lock)\n// here load config activate by CPU1\nunlock(csdev-\u0026gt;cscfg_csdev_lock)\n\n                                              deactivate config // sysfs\n                                              (sys_activec_cnt == 0)\n                                              cscfg_unload_config_sets()\n                                              unload module\n\n// access to config_desc which freed\n// while unloading module.\ncscfg_csdev_enable_config\n\nTo address this, use cscfg_config_desc\u0026apos;s active_cnt as a reference count\n which will be holded when\n    - activate the config.\n    - enable the activated config.\nand put the module reference when config_active_cnt == 0.(CVE-2025-38131)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnet: phy: mscc: Fix memory leak when using one step timestamping\n\nFix memory leak when running one-step timestamping. When running\none-step sync timestamping, the HW is configured to insert the TX time\ninto the frame, so there is no reason to keep the skb anymore. As in\nthis case the HW will never generate an interrupt to say that the frame\nwas timestamped, then the frame will never released.\nFix this by freeing the frame in case of one-step timestamping.(CVE-2025-38148)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nRDMA/mlx5: Fix error flow upon firmware failure for RQ destruction\n\nUpon RQ destruction if the firmware command fails which is the\nlast resource to be destroyed some SW resources were already cleaned\nregardless of the failure.\n\nNow properly rollback the object to its original state upon such failure.\n\nIn order to avoid a use-after free in case someone tries to destroy the\nobject again, which results in the following kernel trace:\nrefcount_t: underflow; use-after-free.\nWARNING: CPU: 0 PID: 37589 at lib/refcount.c:28 refcount_warn_saturate+0xf4/0x148\nModules linked in: rdma_ucm(OE) rdma_cm(OE) iw_cm(OE) ib_ipoib(OE) ib_cm(OE) ib_umad(OE) mlx5_ib(OE) rfkill mlx5_core(OE) mlxdevm(OE) ib_uverbs(OE) ib_core(OE) psample mlxfw(OE) mlx_compat(OE) macsec tls pci_hyperv_intf sunrpc vfat fat virtio_net net_failover failover fuse loop nfnetlink vsock_loopback vmw_vsock_virtio_transport_common vmw_vsock_vmci_transport vmw_vmci vsock xfs crct10dif_ce ghash_ce sha2_ce sha256_arm64 sha1_ce virtio_console virtio_gpu virtio_blk virtio_dma_buf virtio_mmio dm_mirror dm_region_hash dm_log dm_mod xpmem(OE)\nCPU: 0 UID: 0 PID: 37589 Comm: python3 Kdump: loaded Tainted: G           OE     -------  ---  6.12.0-54.el10.aarch64 #1\nTainted: [O]=OOT_MODULE, [E]=UNSIGNED_MODULE\nHardware name: QEMU KVM Virtual Machine, BIOS 0.0.0 02/06/2015\npstate: 60400005 (nZCv daif +PAN -UAO -TCO -DIT -SSBS BTYPE=--)\npc : refcount_warn_saturate+0xf4/0x148\nlr : refcount_warn_saturate+0xf4/0x148\nsp : ffff80008b81b7e0\nx29: ffff80008b81b7e0 x28: ffff000133d51600 x27: 0000000000000001\nx26: 0000000000000000 x25: 00000000ffffffea x24: ffff00010ae80f00\nx23: ffff00010ae80f80 x22: ffff0000c66e5d08 x21: 0000000000000000\nx20: ffff0000c66e0000 x19: ffff00010ae80340 x18: 0000000000000006\nx17: 0000000000000000 x16: 0000000000000020 x15: ffff80008b81b37f\nx14: 0000000000000000 x13: 2e656572662d7265 x12: ffff80008283ef78\nx11: ffff80008257efd0 x10: ffff80008283efd0 x9 : ffff80008021ed90\nx8 : 0000000000000001 x7 : 00000000000bffe8 x6 : c0000000ffff7fff\nx5 : ffff0001fb8e3408 x4 : 0000000000000000 x3 : ffff800179993000\nx2 : 0000000000000000 x1 : 0000000000000000 x0 : ffff000133d51600\nCall trace:\n refcount_warn_saturate+0xf4/0x148\n mlx5_core_put_rsc+0x88/0xa0 [mlx5_ib]\n mlx5_core_destroy_rq_tracked+0x64/0x98 [mlx5_ib]\n mlx5_ib_destroy_wq+0x34/0x80 [mlx5_ib]\n ib_destroy_wq_user+0x30/0xc0 [ib_core]\n uverbs_free_wq+0x28/0x58 [ib_uverbs]\n destroy_hw_idr_uobject+0x34/0x78 [ib_uverbs]\n uverbs_destroy_uobject+0x48/0x240 [ib_uverbs]\n __uverbs_cleanup_ufile+0xd4/0x1a8 [ib_uverbs]\n uverbs_destroy_ufile_hw+0x48/0x120 [ib_uverbs]\n ib_uverbs_close+0x2c/0x100 [ib_uverbs]\n __fput+0xd8/0x2f0\n __fput_sync+0x50/0x70\n __arm64_sys_close+0x40/0x90\n invoke_syscall.constprop.0+0x74/0xd0\n do_el0_svc+0x48/0xe8\n el0_svc+0x44/0x1d0\n el0t_64_sync_handler+0x120/0x130\n el0t_64_sync+0x1a4/0x1a8(CVE-2025-38161)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnet: lan743x: fix potential out-of-bounds write in lan743x_ptp_io_event_clock_get()\n\nBefore calling lan743x_ptp_io_event_clock_get(), the \u0026apos;channel\u0026apos; value\nis checked against the maximum value of PCI11X1X_PTP_IO_MAX_CHANNELS(8).\nThis seems correct and aligns with the PTP interrupt status register\n(PTP_INT_STS) specifications.\n\nHowever, lan743x_ptp_io_event_clock_get() writes to ptp-\u0026gt;extts[] with\nonly LAN743X_PTP_N_EXTTS(4) elements, using channel as an index:\n\n    lan743x_ptp_io_event_clock_get(..., u8 channel,...)\n    {\n        ...\n        /* Update Local timestamp */\n        extts = \u0026amp;ptp-\u0026gt;extts[channel];\n        extts-\u0026gt;ts.tv_sec = sec;\n        ...\n    }\n\nTo avoid an out-of-bounds write and utilize all the supported GPIO\ninputs, set LAN743X_PTP_N_EXTTS to 8.\n\nDetected using the static analysis tool - Svace.(CVE-2025-38183)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnet_sched: sch_sfq: reject invalid perturb period\n\nGerrard Tai reported that SFQ perturb_period has no range check yet,\nand this can be used to trigger a race condition fixed in a separate patch.\n\nWe want to make sure ctl-\u0026gt;perturb_period * HZ will not overflow\nand is positive.\n\n\ntc qd add dev lo root sfq perturb -10   # negative value : error\nError: sch_sfq: invalid perturb period.\n\ntc qd add dev lo root sfq perturb 1000000000 # too big : error\nError: sch_sfq: invalid perturb period.\n\ntc qd add dev lo root sfq perturb 2000000 # acceptable value\ntc -s -d qd sh dev lo\nqdisc sfq 8005: root refcnt 2 limit 127p quantum 64Kb depth 127 flows 128 divisor 1024 perturb 2000000sec\n Sent 0 bytes 0 pkt (dropped 0, overlimits 0 requeues 0)\n backlog 0b 0p requeues 0(CVE-2025-38193)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\njffs2: check that raw node were preallocated before writing summary\n\nSyzkaller detected a kernel bug in jffs2_link_node_ref, caused by fault\ninjection in jffs2_prealloc_raw_node_refs. jffs2_sum_write_sumnode doesn\u0026apos;t\ncheck return value of jffs2_prealloc_raw_node_refs and simply lets any\nerror propagate into jffs2_sum_write_data, which eventually calls\njffs2_link_node_ref in order to link the summary to an expectedly allocated\nnode.\n\nkernel BUG at fs/jffs2/nodelist.c:592!\ninvalid opcode: 0000 [#1] PREEMPT SMP KASAN NOPTI\nCPU: 1 PID: 31277 Comm: syz-executor.7 Not tainted 6.1.128-syzkaller-00139-ge10f83ca10a1 #0\nHardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.12.0-1 04/01/2014\nRIP: 0010:jffs2_link_node_ref+0x570/0x690 fs/jffs2/nodelist.c:592\nCall Trace:\n \u0026lt;TASK\u0026gt;\n jffs2_sum_write_data fs/jffs2/summary.c:841 [inline]\n jffs2_sum_write_sumnode+0xd1a/0x1da0 fs/jffs2/summary.c:874\n jffs2_do_reserve_space+0xa18/0xd60 fs/jffs2/nodemgmt.c:388\n jffs2_reserve_space+0x55f/0xaa0 fs/jffs2/nodemgmt.c:197\n jffs2_write_inode_range+0x246/0xb50 fs/jffs2/write.c:362\n jffs2_write_end+0x726/0x15d0 fs/jffs2/file.c:301\n generic_perform_write+0x314/0x5d0 mm/filemap.c:3856\n __generic_file_write_iter+0x2ae/0x4d0 mm/filemap.c:3973\n generic_file_write_iter+0xe3/0x350 mm/filemap.c:4005\n call_write_iter include/linux/fs.h:2265 [inline]\n do_iter_readv_writev+0x20f/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+0x10c/0x170 fs/splice.c:950\n splice_direct_to_actor+0x337/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\n\nFix this issue by checking return value of jffs2_prealloc_raw_node_refs\nbefore calling jffs2_sum_write_data.\n\nFound by Linux Verification Center (linuxtesting.org) with Syzkaller.(CVE-2025-38194)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nmm/shmem, swap: fix softlockup with mTHP swapin\n\nFollowing softlockup can be easily reproduced on my test machine with:\n\necho always \u0026gt; /sys/kernel/mm/transparent_hugepage/hugepages-64kB/enabled\nswapon /dev/zram0 # zram0 is a 48G swap device\nmkdir -p /sys/fs/cgroup/memory/test\necho 1G \u0026gt; /sys/fs/cgroup/test/memory.max\necho $BASHPID \u0026gt; /sys/fs/cgroup/test/cgroup.procs\nwhile true; do\n    dd if=/dev/zero of=/tmp/test.img bs=1M count=5120\n    cat /tmp/test.img \u0026gt; /dev/null\n    rm /tmp/test.img\ndone\n\nThen after a while:\nwatchdog: BUG: soft lockup - CPU#0 stuck for 763s! [cat:5787]\nModules linked in: zram virtiofs\nCPU: 0 UID: 0 PID: 5787 Comm: cat Kdump: loaded Tainted: G             L      6.15.0.orig-gf3021d9246bc-dirty #118 PREEMPT(voluntary)·\nTainted: [L]=SOFTLOCKUP\nHardware name: Red Hat KVM/RHEL-AV, BIOS 0.0.0 02/06/2015\nRIP: 0010:mpol_shared_policy_lookup+0xd/0x70\nCode: e9 b8 b4 ff ff 31 c0 c3 cc cc cc cc 90 90 90 90 90 90 90 90 90 90 90 90 90 90 90 90 90 66 0f 1f 00 0f 1f 44 00 00 41 54 55 53 \u0026lt;48\u0026gt; 8b 1f 48 85 db 74 41 4c 8d 67 08 48 89 fb 48 89 f5 4c 89 e7 e8\nRSP: 0018:ffffc90002b1fc28 EFLAGS: 00000202\nRAX: 00000000001c20ca RBX: 0000000000724e1e RCX: 0000000000000001\nRDX: ffff888118e214c8 RSI: 0000000000057d42 RDI: ffff888118e21518\nRBP: 000000000002bec8 R08: 0000000000000001 R09: 0000000000000000\nR10: 0000000000000bf4 R11: 0000000000000000 R12: 0000000000000001\nR13: 00000000001c20ca R14: 00000000001c20ca R15: 0000000000000000\nFS:  00007f03f995c740(0000) GS:ffff88a07ad9a000(0000) knlGS:0000000000000000\nCS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033\nCR2: 00007f03f98f1000 CR3: 0000000144626004 CR4: 0000000000770eb0\nDR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000\nDR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400\nPKRU: 55555554\nCall Trace:\n \u0026lt;TASK\u0026gt;\n shmem_alloc_folio+0x31/0xc0\n shmem_swapin_folio+0x309/0xcf0\n ? filemap_get_entry+0x117/0x1e0\n ? xas_load+0xd/0xb0\n ? filemap_get_entry+0x101/0x1e0\n shmem_get_folio_gfp+0x2ed/0x5b0\n shmem_file_read_iter+0x7f/0x2e0\n vfs_read+0x252/0x330\n ksys_read+0x68/0xf0\n do_syscall_64+0x4c/0x1c0\n entry_SYSCALL_64_after_hwframe+0x76/0x7e\nRIP: 0033:0x7f03f9a46991\nCode: 00 48 8b 15 81 14 10 00 f7 d8 64 89 02 b8 ff ff ff ff eb bd e8 20 ad 01 00 f3 0f 1e fa 80 3d 35 97 10 00 00 74 13 31 c0 0f 05 \u0026lt;48\u0026gt; 3d 00 f0 ff ff 77 4f c3 66 0f 1f 44 00 00 55 48 89 e5 48 83 ec\nRSP: 002b:00007fff3c52bd28 EFLAGS: 00000246 ORIG_RAX: 0000000000000000\nRAX: ffffffffffffffda RBX: 0000000000040000 RCX: 00007f03f9a46991\nRDX: 0000000000040000 RSI: 00007f03f98ba000 RDI: 0000000000000003\nRBP: 00007fff3c52bd50 R08: 0000000000000000 R09: 00007f03f9b9a380\nR10: 0000000000000022 R11: 0000000000000246 R12: 0000000000040000\nR13: 00007f03f98ba000 R14: 0000000000000003 R15: 0000000000000000\n \u0026lt;/TASK\u0026gt;\n\nThe reason is simple, readahead brought some order 0 folio in swap cache,\nand the swapin mTHP folio being allocated is in conflict with it, so\nswapcache_prepare fails and causes shmem_swap_alloc_folio to return\n-EEXIST, and shmem simply retries again and again causing this loop.\n\nFix it by applying a similar fix for anon mTHP swapin.\n\nThe performance change is very slight, time of swapin 10g zero folios\nwith shmem (test for 12 times):\nBefore:  2.47s\nAfter:   2.48s\n\n[(CVE-2025-38241)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nlib/group_cpus: fix NULL pointer dereference from group_cpus_evenly()\n\nWhile testing null_blk with configfs, echo 0 \u0026gt; poll_queues will trigger\nfollowing panic:\n\nBUG: kernel NULL pointer dereference, address: 0000000000000010\nOops: Oops: 0000 [#1] SMP NOPTI\nCPU: 27 UID: 0 PID: 920 Comm: bash Not tainted 6.15.0-02023-gadbdb95c8696-dirty #1238 PREEMPT(undef)\nHardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.16.1-2.fc37 04/01/2014\nRIP: 0010:__bitmap_or+0x48/0x70\nCall Trace:\n \u0026lt;TASK\u0026gt;\n __group_cpus_evenly+0x822/0x8c0\n group_cpus_evenly+0x2d9/0x490\n blk_mq_map_queues+0x1e/0x110\n null_map_queues+0xc9/0x170 [null_blk]\n blk_mq_update_queue_map+0xdb/0x160\n blk_mq_update_nr_hw_queues+0x22b/0x560\n nullb_update_nr_hw_queues+0x71/0xf0 [null_blk]\n nullb_device_poll_queues_store+0xa4/0x130 [null_blk]\n configfs_write_iter+0x109/0x1d0\n vfs_write+0x26e/0x6f0\n ksys_write+0x79/0x180\n __x64_sys_write+0x1d/0x30\n x64_sys_call+0x45c4/0x45f0\n do_syscall_64+0xa5/0x240\n entry_SYSCALL_64_after_hwframe+0x76/0x7e\n\nRoot cause is that numgrps is set to 0, and ZERO_SIZE_PTR is returned from\nkcalloc(), and later ZERO_SIZE_PTR will be deferenced.\n\nFix the problem by checking numgrps first in group_cpus_evenly(), and\nreturn NULL directly if numgrps is zero.\n\n[(CVE-2025-38255)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nBluetooth: Fix NULL pointer deference on eir_get_service_data\n\nThe len parameter is considered optional so it can be NULL so it cannot\nbe used for skipping to next entry of EIR_SERVICE_DATA.(CVE-2025-38304)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nASoC: Intel: avs: Verify content returned by parse_int_array()\n\nThe first element of the returned array stores its length. If it is 0,\nany manipulation beyond the element at index 0 ends with null-ptr-deref.(CVE-2025-38307)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nsmb: Log an error when close_all_cached_dirs fails\n\nUnder low-memory conditions, close_all_cached_dirs() can\u0026apos;t move the\ndentries to a separate list to dput() them once the locks are dropped.\nThis will result in a \u0026quot;Dentry still in use\u0026quot; error, so add an error\nmessage that makes it clear this is what happened:\n\n[  495.281119] CIFS: VFS: \\\\otters.example.com\\share Out of memory while dropping dentries\n[  495.281595] ------------[ cut here ]------------\n[  495.281887] BUG: Dentry ffff888115531138{i=78,n=/}  still in use (2) [unmount of cifs cifs]\n[  495.282391] WARNING: CPU: 1 PID: 2329 at fs/dcache.c:1536 umount_check+0xc8/0xf0\n\nAlso, bail out of looping through all tcons as soon as a single\nallocation fails, since we\u0026apos;re already in trouble, and kmalloc() attempts\nfor subseqeuent tcons are likely to fail just like the first one did.(CVE-2025-38321)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nACPICA: fix acpi parse and parseext cache leaks\n\nACPICA commit 8829e70e1360c81e7a5a901b5d4f48330e021ea5\n\nI\u0026apos;m Seunghun Han, and I work for National Security Research Institute of\nSouth Korea.\n\nI have been doing a research on ACPI and found an ACPI cache leak in ACPI\nearly abort cases.\n\nBoot log of ACPI cache leak is as follows:\n[    0.352414] ACPI: Added _OSI(Module Device)\n[    0.353182] ACPI: Added _OSI(Processor Device)\n[    0.353182] ACPI: Added _OSI(3.0 _SCP Extensions)\n[    0.353182] ACPI: Added _OSI(Processor Aggregator Device)\n[    0.356028] ACPI: Unable to start the ACPI Interpreter\n[    0.356799] ACPI Error: Could not remove SCI handler (20170303/evmisc-281)\n[    0.360215] kmem_cache_destroy Acpi-State: Slab cache still has objects\n[    0.360648] CPU: 0 PID: 1 Comm: swapper/0 Tainted: G        W\n4.12.0-rc4-next-20170608+ #10\n[    0.361273] Hardware name: innotek gmb_h virtual_box/virtual_box, BIOS\nvirtual_box 12/01/2006\n[    0.361873] Call Trace:\n[    0.362243]  ? dump_stack+0x5c/0x81\n[    0.362591]  ? kmem_cache_destroy+0x1aa/0x1c0\n[    0.362944]  ? acpi_sleep_proc_init+0x27/0x27\n[    0.363296]  ? acpi_os_delete_cache+0xa/0x10\n[    0.363646]  ? acpi_ut_delete_caches+0x6d/0x7b\n[    0.364000]  ? acpi_terminate+0xa/0x14\n[    0.364000]  ? acpi_init+0x2af/0x34f\n[    0.364000]  ? __class_create+0x4c/0x80\n[    0.364000]  ? video_setup+0x7f/0x7f\n[    0.364000]  ? acpi_sleep_proc_init+0x27/0x27\n[    0.364000]  ? do_one_initcall+0x4e/0x1a0\n[    0.364000]  ? kernel_init_freeable+0x189/0x20a\n[    0.364000]  ? rest_init+0xc0/0xc0\n[    0.364000]  ? kernel_init+0xa/0x100\n[    0.364000]  ? ret_from_fork+0x25/0x30\n\nI analyzed this memory leak in detail. I found that “Acpi-State” cache and\n“Acpi-Parse” cache were merged because the size of cache objects was same\nslab cache size.\n\nI finally found “Acpi-Parse” cache and “Acpi-parse_ext” cache were leaked\nusing SLAB_NEVER_MERGE flag in kmem_cache_create() function.\n\nReal ACPI cache leak point is as follows:\n[    0.360101] ACPI: Added _OSI(Module Device)\n[    0.360101] ACPI: Added _OSI(Processor Device)\n[    0.360101] ACPI: Added _OSI(3.0 _SCP Extensions)\n[    0.361043] ACPI: Added _OSI(Processor Aggregator Device)\n[    0.364016] ACPI: Unable to start the ACPI Interpreter\n[    0.365061] ACPI Error: Could not remove SCI handler (20170303/evmisc-281)\n[    0.368174] kmem_cache_destroy Acpi-Parse: Slab cache still has objects\n[    0.369332] CPU: 1 PID: 1 Comm: swapper/0 Tainted: G        W\n4.12.0-rc4-next-20170608+ #8\n[    0.371256] Hardware name: innotek gmb_h virtual_box/virtual_box, BIOS\nvirtual_box 12/01/2006\n[    0.372000] Call Trace:\n[    0.372000]  ? dump_stack+0x5c/0x81\n[    0.372000]  ? kmem_cache_destroy+0x1aa/0x1c0\n[    0.372000]  ? acpi_sleep_proc_init+0x27/0x27\n[    0.372000]  ? acpi_os_delete_cache+0xa/0x10\n[    0.372000]  ? acpi_ut_delete_caches+0x56/0x7b\n[    0.372000]  ? acpi_terminate+0xa/0x14\n[    0.372000]  ? acpi_init+0x2af/0x34f\n[    0.372000]  ? __class_create+0x4c/0x80\n[    0.372000]  ? video_setup+0x7f/0x7f\n[    0.372000]  ? acpi_sleep_proc_init+0x27/0x27\n[    0.372000]  ? do_one_initcall+0x4e/0x1a0\n[    0.372000]  ? kernel_init_freeable+0x189/0x20a\n[    0.372000]  ? rest_init+0xc0/0xc0\n[    0.372000]  ? kernel_init+0xa/0x100\n[    0.372000]  ? ret_from_fork+0x25/0x30\n[    0.388039] kmem_cache_destroy Acpi-parse_ext: Slab cache still has objects\n[    0.389063] CPU: 1 PID: 1 Comm: swapper/0 Tainted: G        W\n4.12.0-rc4-next-20170608+ #8\n[    0.390557] Hardware name: innotek gmb_h virtual_box/virtual_box, BIOS\nvirtual_box 12/01/2006\n[    0.392000] Call Trace:\n[    0.392000]  ? dump_stack+0x5c/0x81\n[    0.392000]  ? kmem_cache_destroy+0x1aa/0x1c0\n[    0.392000]  ? acpi_sleep_proc_init+0x27/0x27\n[    0.392000]  ? acpi_os_delete_cache+0xa/0x10\n[    0.392000]  ? acpi_ut_delete_caches+0x6d/0x7b\n[    0.392000]  ? acpi_terminate+0xa/0x14\n[    0.392000]  ? acpi_init+0x2af/0x3\n---truncated---(CVE-2025-38344)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nmaple_tree: fix MA_STATE_PREALLOC flag in mas_preallocate()\n\nTemporarily clear the preallocation flag when explicitly requesting\nallocations.  Pre-existing allocations are already counted against the\nrequest through mas_node_count_gfp(), but the allocations will not happen\nif the MA_STATE_PREALLOC flag is set.  This flag is meant to avoid\nre-allocating in bulk allocation mode, and to detect issues with\npreallocation calculations.\n\nThe MA_STATE_PREALLOC flag should also always be set on zero allocations\nso that detection of underflow allocations will print a WARN_ON() during\nconsumption.\n\nUser visible effect of this flaw is a WARN_ON() followed by a null pointer\ndereference when subsequent requests for larger number of nodes is\nignored, such as the vma merge retry in mmap_region() caused by drivers\naltering the vma flags (which happens in v6.6, at least)(CVE-2025-38364)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nvsock: Fix transport_* TOCTOU\n\nTransport assignment may race with module unload. Protect new_transport\nfrom becoming a stale pointer.\n\nThis also takes care of an insecure call in vsock_use_local_transport();\nadd a lockdep assert.\n\nBUG: unable to handle page fault for address: fffffbfff8056000\nOops: Oops: 0000 [#1] SMP KASAN\nRIP: 0010:vsock_assign_transport+0x366/0x600\nCall Trace:\n vsock_connect+0x59c/0xc40\n __sys_connect+0xe8/0x100\n __x64_sys_connect+0x6e/0xc0\n do_syscall_64+0x92/0x1c0\n entry_SYSCALL_64_after_hwframe+0x4b/0x53(CVE-2025-38461)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nvsock: Fix transport_{g2h,h2g} TOCTOU\n\nvsock_find_cid() and vsock_dev_do_ioctl() may race with module unload.\ntransport_{g2h,h2g} may become NULL after the NULL check.\n\nIntroduce vsock_transport_local_cid() to protect from a potential\nnull-ptr-deref.\n\nKASAN: null-ptr-deref in range [0x0000000000000118-0x000000000000011f]\nRIP: 0010:vsock_find_cid+0x47/0x90\nCall Trace:\n __vsock_bind+0x4b2/0x720\n vsock_bind+0x90/0xe0\n __sys_bind+0x14d/0x1e0\n __x64_sys_bind+0x6e/0xc0\n do_syscall_64+0x92/0x1c0\n entry_SYSCALL_64_after_hwframe+0x4b/0x53\n\nKASAN: null-ptr-deref in range [0x0000000000000118-0x000000000000011f]\nRIP: 0010:vsock_dev_do_ioctl.isra.0+0x58/0xf0\nCall Trace:\n __x64_sys_ioctl+0x12d/0x190\n do_syscall_64+0x92/0x1c0\n entry_SYSCALL_64_after_hwframe+0x4b/0x53(CVE-2025-38462)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nsmb: client: fix use-after-free in crypt_message when using async crypto\n\nThe CVE-2024-50047 fix removed asynchronous crypto handling from\ncrypt_message(), assuming all crypto operations are synchronous.\nHowever, when hardware crypto accelerators are used, this can cause\nuse-after-free crashes:\n\n  crypt_message()\n    // Allocate the creq buffer containing the req\n    creq = smb2_get_aead_req(..., \u0026amp;req);\n\n    // Async encryption returns -EINPROGRESS immediately\n    rc = enc ? crypto_aead_encrypt(req) : crypto_aead_decrypt(req);\n\n    // Free creq while async operation is still in progress\n    kvfree_sensitive(creq, ...);\n\nHardware crypto modules often implement async AEAD operations for\nperformance. When crypto_aead_encrypt/decrypt() returns -EINPROGRESS,\nthe operation completes asynchronously. Without crypto_wait_req(),\nthe function immediately frees the request buffer, leading to crashes\nwhen the driver later accesses the freed memory.\n\nThis results in a use-after-free condition when the hardware crypto\ndriver later accesses the freed request structure, leading to kernel\ncrashes with NULL pointer dereferences.\n\nThe issue occurs because crypto_alloc_aead() with mask=0 doesn\u0026apos;t\nguarantee synchronous operation. Even without CRYPTO_ALG_ASYNC in\nthe mask, async implementations can be selected.\n\nFix by restoring the async crypto handling:\n- DECLARE_CRYPTO_WAIT(wait) for completion tracking\n- aead_request_set_callback() for async completion notification\n- crypto_wait_req() to wait for operation completion\n\nThis ensures the request buffer isn\u0026apos;t freed until the crypto operation\ncompletes, whether synchronous or asynchronous, while preserving the\nCVE-2024-50047 fix.(CVE-2025-38488)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nclone_private_mnt(): make sure that caller has CAP_SYS_ADMIN in the right userns\n\nWhat we want is to verify there is that clone won\u0026apos;t expose something\nhidden by a mount we wouldn\u0026apos;t be able to undo.  \u0026quot;Wouldn\u0026apos;t be able to undo\u0026quot;\nmay be a result of MNT_LOCKED on a child, but it may also come from\nlacking admin rights in the userns of the namespace mount belongs to.\n\nclone_private_mnt() checks the former, but not the latter.\n\nThere\u0026apos;s a number of rather confusing CAP_SYS_ADMIN checks in various\nuserns during the mount, especially with the new mount API; they serve\ndifferent purposes and in case of clone_private_mnt() they usually,\nbut not always end up covering the missing check mentioned above.(CVE-2025-38499)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nmptcp: plug races between subflow fail and subflow creation\n\nWe have races similar to the one addressed by the previous patch between\nsubflow failing and additional subflow creation. They are just harder to\ntrigger.\n\nThe solution is similar. Use a separate flag to track the condition\n\u0026apos;socket state prevent any additional subflow creation\u0026apos; protected by the\nfallback lock.\n\nThe socket fallback makes such flag true, and also receiving or sending\nan MP_FAIL option.\n\nThe field \u0026apos;allow_infinite_fallback\u0026apos; is now always touched under the\nrelevant lock, we can drop the ONCE annotation on write.(CVE-2025-38552)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nksmbd: use aead_request_free to match aead_request_alloc\n\nUse aead_request_free() instead of kfree() to properly free memory\nallocated by aead_request_alloc(). This ensures sensitive crypto data\nis zeroed before being freed.(CVE-2025-38575)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nPM / devfreq: Check governor before using governor-\u0026gt;name\n\nCommit 96ffcdf239de (\u0026quot;PM / devfreq: Remove redundant governor_name from\nstruct devfreq\u0026quot;) removes governor_name and uses governor-\u0026gt;name to replace\nit. But devfreq-\u0026gt;governor may be NULL and directly using\ndevfreq-\u0026gt;governor-\u0026gt;name may cause null pointer exception. Move the check of\ngovernor to before using governor-\u0026gt;name.(CVE-2025-38609)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnetfilter: ctnetlink: fix refcount leak on table dump\n\nThere is a reference count leak in ctnetlink_dump_table():\n      if (res \u0026lt; 0) {\n                nf_conntrack_get(\u0026amp;ct-\u0026gt;ct_general); // HERE\n                cb-\u0026gt;args[1] = (unsigned long)ct;\n                ...\n\nWhile its very unlikely, its possible that ct == last.\nIf this happens, then the refcount of ct was already incremented.\nThis 2nd increment is never undone.\n\nThis prevents the conntrack object from being released, which in turn\nkeeps prevents cnet-\u0026gt;count from dropping back to 0.\n\nThis will then block the netns dismantle (or conntrack rmmod) as\nnf_conntrack_cleanup_net_list() will wait forever.\n\nThis can be reproduced by running conntrack_resize.sh selftest in a loop.\nIt takes ~20 minutes for me on a preemptible kernel on average before\nI see a runaway kworker spinning in nf_conntrack_cleanup_net_list.\n\nOne fix would to change this to:\n        if (res \u0026lt; 0) {\n\t\tif (ct != last)\n\t                nf_conntrack_get(\u0026amp;ct-\u0026gt;ct_general);\n\nBut this reference counting isn\u0026apos;t needed in the first place.\nWe can just store a cookie value instead.\n\nA followup patch will do the same for ctnetlink_exp_dump_table,\nit looks to me as if this has the same problem and like\nctnetlink_dump_table, we only need a \u0026apos;skip hint\u0026apos;, not the actual\nobject so we can apply the same cookie strategy there as well.(CVE-2025-38721)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nscsi: qla4xxx: Prevent a potential error pointer dereference\n\nThe qla4xxx_get_ep_fwdb() function is supposed to return NULL on error,\nbut qla4xxx_ep_connect() returns error pointers.  Propagating the error\npointers will lead to an Oops in the caller, so change the error pointers\nto NULL.(CVE-2025-39676)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ntls: fix handling of zero-length records on the rx_list\n\nEach recvmsg() call must process either\n - only contiguous DATA records (any number of them)\n - one non-DATA record\n\nIf the next record has different type than what has already been\nprocessed we break out of the main processing loop. If the record\nhas already been decrypted (which may be the case for TLS 1.3 where\nwe don\u0026apos;t know type until decryption) we queue the pending record\nto the rx_list. Next recvmsg() will pick it up from there.\n\nQueuing the skb to rx_list after zero-copy decrypt is not possible,\nsince in that case we decrypted directly to the user space buffer,\nand we don\u0026apos;t have an skb to queue (darg.skb points to the ciphertext\nskb for access to metadata like length).\n\nOnly data records are allowed zero-copy, and we break the processing\nloop after each non-data record. So we should never zero-copy and\nthen find out that the record type has changed. The corner case\nwe missed is when the initial record comes from rx_list, and it\u0026apos;s\nzero length.(CVE-2025-39682)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nipv6: sr: Fix MAC comparison to be constant-time\n\nTo prevent timing attacks, MACs need to be compared in constant time.\nUse the appropriate helper function for this.(CVE-2025-39702)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nclk: samsung: Fix UBSAN panic in samsung_clk_init()\n\nWith UBSAN_ARRAY_BOUNDS=y, I\u0026apos;m hitting the below panic due to\ndereferencing `ctx-\u0026gt;clk_data.hws` before setting\n`ctx-\u0026gt;clk_data.num = nr_clks`. Move that up to fix the crash.\n\n  UBSAN: array index out of bounds: 00000000f2005512 [#1] PREEMPT SMP\n  \u0026lt;snip\u0026gt;\n  Call trace:\n   samsung_clk_init+0x110/0x124 (P)\n   samsung_clk_init+0x48/0x124 (L)\n   samsung_cmu_register_one+0x3c/0xa0\n   exynos_arm64_register_cmu+0x54/0x64\n   __gs101_cmu_top_of_clk_init_declare+0x28/0x60\n   ...(CVE-2025-39728)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nfs: Prevent file descriptor table allocations exceeding INT_MAX\n\nWhen sysctl_nr_open is set to a very high value (for example, 1073741816\nas set by systemd), processes attempting to use file descriptors near\nthe limit can trigger massive memory allocation attempts that exceed\nINT_MAX, resulting in a WARNING in mm/slub.c:\n\n  WARNING: CPU: 0 PID: 44 at mm/slub.c:5027 __kvmalloc_node_noprof+0x21a/0x288\n\nThis happens because kvmalloc_array() and kvmalloc() check if the\nrequested size exceeds INT_MAX and emit a warning when the allocation is\nnot flagged with __GFP_NOWARN.\n\nSpecifically, when nr_open is set to 1073741816 (0x3ffffff8) and a\nprocess calls dup2(oldfd, 1073741880), the kernel attempts to allocate:\n- File descriptor array: 1073741880 * 8 bytes = 8,589,935,040 bytes\n- Multiple bitmaps: ~400MB\n- Total allocation size: \u0026gt; 8GB (exceeding INT_MAX = 2,147,483,647)\n\nReproducer:\n1. Set /proc/sys/fs/nr_open to 1073741816:\n   # echo 1073741816 \u0026gt; /proc/sys/fs/nr_open\n\n2. Run a program that uses a high file descriptor:\n   #include \u0026lt;unistd.h\u0026gt;\n   #include \u0026lt;sys/resource.h\u0026gt;\n\n   int main() {\n       struct rlimit rlim = {1073741824, 1073741824};\n       setrlimit(RLIMIT_NOFILE, \u0026amp;rlim);\n       dup2(2, 1073741880);  // Triggers the warning\n       return 0;\n   }\n\n3. Observe WARNING in dmesg at mm/slub.c:5027\n\nsystemd commit a8b627a introduced automatic bumping of fs.nr_open to the\nmaximum possible value. The rationale was that systems with memory\ncontrol groups (memcg) no longer need separate file descriptor limits\nsince memory is properly accounted. However, this change overlooked\nthat:\n\n1. The kernel\u0026apos;s allocation functions still enforce INT_MAX as a maximum\n   size regardless of memcg accounting\n2. Programs and tests that legitimately test file descriptor limits can\n   inadvertently trigger massive allocations\n3. The resulting allocations (\u0026gt;8GB) are impractical and will always fail\n\nsystemd\u0026apos;s algorithm starts with INT_MAX and keeps halving the value\nuntil the kernel accepts it. On most systems, this results in nr_open\nbeing set to 1073741816 (0x3ffffff8), which is just under 1GB of file\ndescriptors.\n\nWhile processes rarely use file descriptors near this limit in normal\noperation, certain selftests (like\ntools/testing/selftests/core/unshare_test.c) and programs that test file\ndescriptor limits can trigger this issue.\n\nFix this by adding a check in alloc_fdtable() to ensure the requested\nallocation size does not exceed INT_MAX. This causes the operation to\nfail with -EMFILE instead of triggering a kernel warning and avoids the\nimpractical \u0026gt;8GB memory allocation request.(CVE-2025-39756)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnet: gso: Forbid IPv6 TSO with extensions on devices with only IPV6_CSUM\n\nWhen performing Generic Segmentation Offload (GSO) on an IPv6 packet that\ncontains extension headers, the kernel incorrectly requests checksum offload\nif the egress device only advertises NETIF_F_IPV6_CSUM feature, which has\na strict contract: it supports checksum offload only for plain TCP or UDP\nover IPv6 and explicitly does not support packets with extension headers.\nThe current GSO logic violates this contract by failing to disable the feature\nfor packets with extension headers, such as those used in GREoIPv6 tunnels.\n\nThis violation results in the device being asked to perform an operation\nit cannot support, leading to a `skb_warn_bad_offload` warning and a collapse\nof network throughput. While device TSO/USO is correctly bypassed in favor\nof software GSO for these packets, the GSO stack must be explicitly told not\nto request checksum offload.\n\nMask NETIF_F_IPV6_CSUM, NETIF_F_TSO6 and NETIF_F_GSO_UDP_L4\nin gso_features_check if the IPv6 header contains extension headers to compute\nchecksum in software.\n\nThe exception is a BIG TCP extension, which, as stated in commit\n68e068cabd2c6c53 (\u0026quot;net: reenable NETIF_F_IPV6_CSUM offload for BIG TCP packets\u0026quot;):\n\u0026quot;The feature is only enabled on devices that support BIG TCP TSO.\nThe header is only present for PF_PACKET taps like tcpdump,\nand not transmitted by physical devices.\u0026quot;\n\nkernel log output (truncated):\nWARNING: CPU: 1 PID: 5273 at net/core/dev.c:3535 skb_warn_bad_offload+0x81/0x140\n...\nCall Trace:\n \u0026lt;TASK\u0026gt;\n skb_checksum_help+0x12a/0x1f0\n validate_xmit_skb+0x1a3/0x2d0\n validate_xmit_skb_list+0x4f/0x80\n sch_direct_xmit+0x1a2/0x380\n __dev_xmit_skb+0x242/0x670\n __dev_queue_xmit+0x3fc/0x7f0\n ip6_finish_output2+0x25e/0x5d0\n ip6_finish_output+0x1fc/0x3f0\n ip6_tnl_xmit+0x608/0xc00 [ip6_tunnel]\n ip6gre_tunnel_xmit+0x1c0/0x390 [ip6_gre]\n dev_hard_start_xmit+0x63/0x1c0\n __dev_queue_xmit+0x6d0/0x7f0\n ip6_finish_output2+0x214/0x5d0\n ip6_finish_output+0x1fc/0x3f0\n ip6_xmit+0x2ca/0x6f0\n ip6_finish_output+0x1fc/0x3f0\n ip6_xmit+0x2ca/0x6f0\n inet6_csk_xmit+0xeb/0x150\n __tcp_transmit_skb+0x555/0xa80\n tcp_write_xmit+0x32a/0xe90\n tcp_sendmsg_locked+0x437/0x1110\n tcp_sendmsg+0x2f/0x50\n...\nskb linear:   00000000: e4 3d 1a 7d ec 30 e4 3d 1a 7e 5d 90 86 dd 60 0e\nskb linear:   00000010: 00 0a 1b 34 3c 40 20 11 00 00 00 00 00 00 00 00\nskb linear:   00000020: 00 00 00 00 00 12 20 11 00 00 00 00 00 00 00 00\nskb linear:   00000030: 00 00 00 00 00 11 2f 00 04 01 04 01 01 00 00 00\nskb linear:   00000040: 86 dd 60 0e 00 0a 1b 00 06 40 20 23 00 00 00 00\nskb linear:   00000050: 00 00 00 00 00 00 00 00 00 12 20 23 00 00 00 00\nskb linear:   00000060: 00 00 00 00 00 00 00 00 00 11 bf 96 14 51 13 f9\nskb linear:   00000070: ae 27 a0 a8 2b e3 80 18 00 40 5b 6f 00 00 01 01\nskb linear:   00000080: 08 0a 42 d4 50 d5 4b 70 f8 1a(CVE-2025-39770)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nsctp: initialize more fields in sctp_v6_from_sk()\n\nsyzbot found that sin6_scope_id was not properly initialized,\nleading to undefined behavior.\n\nClear sin6_scope_id and sin6_flowinfo.\n\nBUG: KMSAN: uninit-value in __sctp_v6_cmp_addr+0x887/0x8c0 net/sctp/ipv6.c:649\n  __sctp_v6_cmp_addr+0x887/0x8c0 net/sctp/ipv6.c:649\n  sctp_inet6_cmp_addr+0x4f2/0x510 net/sctp/ipv6.c:983\n  sctp_bind_addr_conflict+0x22a/0x3b0 net/sctp/bind_addr.c:390\n  sctp_get_port_local+0x21eb/0x2440 net/sctp/socket.c:8452\n  sctp_get_port net/sctp/socket.c:8523 [inline]\n  sctp_listen_start net/sctp/socket.c:8567 [inline]\n  sctp_inet_listen+0x710/0xfd0 net/sctp/socket.c:8636\n  __sys_listen_socket net/socket.c:1912 [inline]\n  __sys_listen net/socket.c:1927 [inline]\n  __do_sys_listen net/socket.c:1932 [inline]\n  __se_sys_listen net/socket.c:1930 [inline]\n  __x64_sys_listen+0x343/0x4c0 net/socket.c:1930\n  x64_sys_call+0x271d/0x3e20 arch/x86/include/generated/asm/syscalls_64.h:51\n  do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline]\n  do_syscall_64+0xd9/0x210 arch/x86/entry/syscall_64.c:94\n entry_SYSCALL_64_after_hwframe+0x77/0x7f\n\nLocal variable addr.i.i created at:\n  sctp_get_port net/sctp/socket.c:8515 [inline]\n  sctp_listen_start net/sctp/socket.c:8567 [inline]\n  sctp_inet_listen+0x650/0xfd0 net/sctp/socket.c:8636\n  __sys_listen_socket net/socket.c:1912 [inline]\n  __sys_listen net/socket.c:1927 [inline]\n  __do_sys_listen net/socket.c:1932 [inline]\n  __se_sys_listen net/socket.c:1930 [inline]\n  __x64_sys_listen+0x343/0x4c0 net/socket.c:1930(CVE-2025-39812)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nscsi: lpfc: Fix buffer free/clear order in deferred receive path\n\nFix a use-after-free window by correcting the buffer release sequence in\nthe deferred receive path. The code freed the RQ buffer first and only\nthen cleared the context pointer under the lock. Concurrent paths (e.g.,\nABTS and the repost path) also inspect and release the same pointer under\nthe lock, so the old order could lead to double-free/UAF.\n\nNote that the repost path already uses the correct pattern: detach the\npointer under the lock, then free it after dropping the lock. The\ndeferred path should do the same.(CVE-2025-39841)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnetfilter: br_netfilter: do not check confirmed bit in br_nf_local_in() after confirm\n\nWhen send a broadcast packet to a tap device, which was added to a bridge,\nbr_nf_local_in() is called to confirm the conntrack. If another conntrack\nwith the same hash value is added to the hash table, which can be\ntriggered by a normal packet to a non-bridge device, the below warning\nmay happen.\n\n  ------------[ cut here ]------------\n  WARNING: CPU: 1 PID: 96 at net/bridge/br_netfilter_hooks.c:632 br_nf_local_in+0x168/0x200\n  CPU: 1 UID: 0 PID: 96 Comm: tap_send Not tainted 6.17.0-rc2-dirty #44 PREEMPT(voluntary)\n  RIP: 0010:br_nf_local_in+0x168/0x200\n  Call Trace:\n   \u0026lt;TASK\u0026gt;\n   nf_hook_slow+0x3e/0xf0\n   br_pass_frame_up+0x103/0x180\n   br_handle_frame_finish+0x2de/0x5b0\n   br_nf_hook_thresh+0xc0/0x120\n   br_nf_pre_routing_finish+0x168/0x3a0\n   br_nf_pre_routing+0x237/0x5e0\n   br_handle_frame+0x1ec/0x3c0\n   __netif_receive_skb_core+0x225/0x1210\n   __netif_receive_skb_one_core+0x37/0xa0\n   netif_receive_skb+0x36/0x160\n   tun_get_user+0xa54/0x10c0\n   tun_chr_write_iter+0x65/0xb0\n   vfs_write+0x305/0x410\n   ksys_write+0x60/0xd0\n   do_syscall_64+0xa4/0x260\n   entry_SYSCALL_64_after_hwframe+0x77/0x7f\n   \u0026lt;/TASK\u0026gt;\n  ---[ end trace 0000000000000000 ]---\n\nTo solve the hash conflict, nf_ct_resolve_clash() try to merge the\nconntracks, and update skb-\u0026gt;_nfct. However, br_nf_local_in() still use the\nold ct from local variable \u0026apos;nfct\u0026apos; after confirm(), which leads to this\nwarning.\n\nIf confirm() does not insert the conntrack entry and return NF_DROP, the\nwarning may also occur. There is no need to reserve the WARN_ON_ONCE, just\nremove it.(CVE-2025-39894)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnet: rfkill: gpio: Fix crash due to dereferencering uninitialized pointer\n\nSince commit 7d5e9737efda (\u0026quot;net: rfkill: gpio: get the name and type from\ndevice property\u0026quot;) rfkill_find_type() gets called with the possibly\nuninitialized \u0026quot;const char *type_name;\u0026quot; local variable.\n\nOn x86 systems when rfkill-gpio binds to a \u0026quot;BCM4752\u0026quot; or \u0026quot;LNV4752\u0026quot;\nacpi_device, the rfkill-\u0026gt;type is set based on the ACPI acpi_device_id:\n\n        rfkill-\u0026gt;type = (unsigned)id-\u0026gt;driver_data;\n\nand there is no \u0026quot;type\u0026quot; property so device_property_read_string() will fail\nand leave type_name uninitialized, leading to a potential crash.\n\nrfkill_find_type() does accept a NULL pointer, fix the potential crash\nby initializing type_name to NULL.\n\nNote likely sofar this has not been caught because:\n\n1. Not many x86 machines actually have a \u0026quot;BCM4752\u0026quot;/\u0026quot;LNV4752\u0026quot; acpi_device\n2. The stack happened to contain NULL where type_name is stored(CVE-2025-39937)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ntcp: Clear tcp_sk(sk)-\u0026gt;fastopen_rsk in tcp_disconnect().\n\nsyzbot reported the splat below where a socket had tcp_sk(sk)-\u0026gt;fastopen_rsk\nin the TCP_ESTABLISHED state. [0]\n\nsyzbot reused the server-side TCP Fast Open socket as a new client before\nthe TFO socket completes 3WHS:\n\n  1. accept()\n  2. connect(AF_UNSPEC)\n  3. connect() to another destination\n\nAs of accept(), sk-\u0026gt;sk_state is TCP_SYN_RECV, and tcp_disconnect() changes\nit to TCP_CLOSE and makes connect() possible, which restarts timers.\n\nSince tcp_disconnect() forgot to clear tcp_sk(sk)-\u0026gt;fastopen_rsk, the\nretransmit timer triggered the warning and the intended packet was not\nretransmitted.\n\nLet\u0026apos;s call reqsk_fastopen_remove() in tcp_disconnect().\n\n[0]:\nWARNING: CPU: 2 PID: 0 at net/ipv4/tcp_timer.c:542 tcp_retransmit_timer (net/ipv4/tcp_timer.c:542 (discriminator 7))\nModules linked in:\nCPU: 2 UID: 0 PID: 0 Comm: swapper/2 Not tainted 6.17.0-rc5-g201825fb4278 #62 PREEMPT(voluntary)\nHardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.16.3-debian-1.16.3-2 04/01/2014\nRIP: 0010:tcp_retransmit_timer (net/ipv4/tcp_timer.c:542 (discriminator 7))\nCode: 41 55 41 54 55 53 48 8b af b8 08 00 00 48 89 fb 48 85 ed 0f 84 55 01 00 00 0f b6 47 12 3c 03 74 0c 0f b6 47 12 3c 04 74 04 90 \u0026lt;0f\u0026gt; 0b 90 48 8b 85 c0 00 00 00 48 89 ef 48 8b 40 30 e8 6a 4f 06 3e\nRSP: 0018:ffffc900002f8d40 EFLAGS: 00010293\nRAX: 0000000000000002 RBX: ffff888106911400 RCX: 0000000000000017\nRDX: 0000000002517619 RSI: ffffffff83764080 RDI: ffff888106911400\nRBP: ffff888106d5c000 R08: 0000000000000001 R09: ffffc900002f8de8\nR10: 00000000000000c2 R11: ffffc900002f8ff8 R12: ffff888106911540\nR13: ffff888106911480 R14: ffff888106911840 R15: ffffc900002f8de0\nFS:  0000000000000000(0000) GS:ffff88907b768000(0000) knlGS:0000000000000000\nCS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033\nCR2: 00007f8044d69d90 CR3: 0000000002c30003 CR4: 0000000000370ef0\nCall Trace:\n \u0026lt;IRQ\u0026gt;\n tcp_write_timer (net/ipv4/tcp_timer.c:738)\n call_timer_fn (kernel/time/timer.c:1747)\n __run_timers (kernel/time/timer.c:1799 kernel/time/timer.c:2372)\n timer_expire_remote (kernel/time/timer.c:2385 kernel/time/timer.c:2376 kernel/time/timer.c:2135)\n tmigr_handle_remote_up (kernel/time/timer_migration.c:944 kernel/time/timer_migration.c:1035)\n __walk_groups.isra.0 (kernel/time/timer_migration.c:533 (discriminator 1))\n tmigr_handle_remote (kernel/time/timer_migration.c:1096)\n handle_softirqs (./arch/x86/include/asm/jump_label.h:36 ./include/trace/events/irq.h:142 kernel/softirq.c:580)\n irq_exit_rcu (kernel/softirq.c:614 kernel/softirq.c:453 kernel/softirq.c:680 kernel/softirq.c:696)\n sysvec_apic_timer_interrupt (arch/x86/kernel/apic/apic.c:1050 (discriminator 35) arch/x86/kernel/apic/apic.c:1050 (discriminator 35))\n \u0026lt;/IRQ\u0026gt;(CVE-2025-39955)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnexthop: Forbid FDB status change while nexthop is in a group\n\nThe kernel forbids the creation of non-FDB nexthop groups with FDB\nnexthops:\n\n # ip nexthop add id 1 via 192.0.2.1 fdb\n # ip nexthop add id 2 group 1\n Error: Non FDB nexthop group cannot have fdb nexthops.\n\nAnd vice versa:\n\n # ip nexthop add id 3 via 192.0.2.2 dev dummy1\n # ip nexthop add id 4 group 3 fdb\n Error: FDB nexthop group can only have fdb nexthops.\n\nHowever, as long as no routes are pointing to a non-FDB nexthop group,\nthe kernel allows changing the type of a nexthop from FDB to non-FDB and\nvice versa:\n\n # ip nexthop add id 5 via 192.0.2.2 dev dummy1\n # ip nexthop add id 6 group 5\n # ip nexthop replace id 5 via 192.0.2.2 fdb\n # echo $?\n 0\n\nThis configuration is invalid and can result in a NPD [1] since FDB\nnexthops are not associated with a nexthop device:\n\n # ip route add 198.51.100.1/32 nhid 6\n # ping 198.51.100.1\n\nFix by preventing nexthop FDB status change while the nexthop is in a\ngroup:\n\n # ip nexthop add id 7 via 192.0.2.2 dev dummy1\n # ip nexthop add id 8 group 7\n # ip nexthop replace id 7 via 192.0.2.2 fdb\n Error: Cannot change nexthop FDB status while in a group.\n\n[1]\nBUG: kernel NULL pointer dereference, address: 00000000000003c0\n[...]\nOops: Oops: 0000 [#1] SMP\nCPU: 6 UID: 0 PID: 367 Comm: ping Not tainted 6.17.0-rc6-virtme-gb65678cacc03 #1 PREEMPT(voluntary)\nHardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.17.0-4.fc41 04/01/2014\nRIP: 0010:fib_lookup_good_nhc+0x1e/0x80\n[...]\nCall Trace:\n \u0026lt;TASK\u0026gt;\n fib_table_lookup+0x541/0x650\n ip_route_output_key_hash_rcu+0x2ea/0x970\n ip_route_output_key_hash+0x55/0x80\n __ip4_datagram_connect+0x250/0x330\n udp_connect+0x2b/0x60\n __sys_connect+0x9c/0xd0\n __x64_sys_connect+0x18/0x20\n do_syscall_64+0xa4/0x2a0\n entry_SYSCALL_64_after_hwframe+0x4b/0x53(CVE-2025-39980)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nipvs: Defer ip_vs_ftp unregister during netns cleanup\n\nOn the netns cleanup path, __ip_vs_ftp_exit() may unregister ip_vs_ftp\nbefore connections with valid cp-\u0026gt;app pointers are flushed, leading to a\nuse-after-free.\n\nFix this by introducing a global `exiting_module` flag, set to true in\nip_vs_ftp_exit() before unregistering the pernet subsystem. In\n__ip_vs_ftp_exit(), skip ip_vs_ftp unregister if called during netns\ncleanup (when exiting_module is false) and defer it to\n__ip_vs_cleanup_batch(), which unregisters all apps after all connections\nare flushed. If called during module exit, unregister ip_vs_ftp\nimmediately.(CVE-2025-40018)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ncrypto: hisilicon/qm - set NULL to qm-\u0026gt;debug.qm_diff_regs\n\nWhen the initialization of qm-\u0026gt;debug.acc_diff_reg fails,\nthe probe process does not exit. However, after qm-\u0026gt;debug.qm_diff_regs is\nfreed, it is not set to NULL. This can lead to a double free when the\nremove process attempts to free it again. Therefore, qm-\u0026gt;debug.qm_diff_regs\nshould be set to NULL after it is freed.(CVE-2025-40062)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nbpf: Explicitly check accesses to bpf_sock_addr\n\nSyzkaller found a kernel warning on the following sock_addr program:\n\n    0: r0 = 0\n    1: r2 = *(u32 *)(r1 +60)\n    2: exit\n\nwhich triggers:\n\n    verifier bug: error during ctx access conversion (0)\n\nThis is happening because offset 60 in bpf_sock_addr corresponds to an\nimplicit padding of 4 bytes, right after msg_src_ip4. Access to this\npadding isn\u0026apos;t rejected in sock_addr_is_valid_access and it thus later\nfails to convert the access.\n\nThis patch fixes it by explicitly checking the various fields of\nbpf_sock_addr in sock_addr_is_valid_access.\n\nI checked the other ctx structures and is_valid_access functions and\ndidn\u0026apos;t find any other similar cases. Other cases of (properly handled)\npadding are covered in new tests in a subsequent patch.(CVE-2025-40078)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ncrypto: hisilicon/qm - request reserved interrupt for virtual function\n\nThe device interrupt vector 3 is an error interrupt for\nphysical function and a reserved interrupt for virtual function.\nHowever, the driver has not registered the reserved interrupt for\nvirtual function. When allocating interrupts, the number of interrupts\nis allocated based on powers of two, which includes this interrupt.\nWhen the system enables GICv4 and the virtual function passthrough\nto the virtual machine, releasing the interrupt in the driver\ntriggers a warning.\n\nThe WARNING report is:\nWARNING: CPU: 62 PID: 14889 at arch/arm64/kvm/vgic/vgic-its.c:852 its_free_ite+0x94/0xb4\n\nTherefore, register a reserved interrupt for VF and set the\nIRQF_NO_AUTOEN flag to avoid that warning.(CVE-2025-40136)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nsctp: avoid NULL dereference when chunk data buffer is missing\n\nchunk-\u0026gt;skb pointer is dereferenced in the if-block where it\u0026apos;s supposed\nto be NULL only.\n\nchunk-\u0026gt;skb can only be NULL if chunk-\u0026gt;head_skb is not. Check for frag_list\ninstead and do it just before replacing chunk-\u0026gt;skb. We\u0026apos;re sure that\notherwise chunk-\u0026gt;skb is non-NULL because of outer if() condition.(CVE-2025-40240)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnet: openvswitch: remove never-working support for setting nsh fields\n\nThe validation of the set(nsh(...)) action is completely wrong.\nIt runs through the nsh_key_put_from_nlattr() function that is the\nsame function that validates NSH keys for the flow match and the\npush_nsh() action.  However, the set(nsh(...)) has a very different\nmemory layout.  Nested attributes in there are doubled in size in\ncase of the masked set().  That makes proper validation impossible.\n\nThere is also confusion in the code between the \u0026apos;masked\u0026apos; flag, that\nsays that the nested attributes are doubled in size containing both\nthe value and the mask, and the \u0026apos;is_mask\u0026apos; that says that the value\nwe\u0026apos;re parsing is the mask.  This is causing kernel crash on trying to\nwrite into mask part of the match with SW_FLOW_KEY_PUT() during\nvalidation, while validate_nsh() doesn\u0026apos;t allocate any memory for it:\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 1c2383067 P4D 1c2383067 PUD 20b703067 PMD 0\n  Oops: Oops: 0000 [#1] SMP NOPTI\n  CPU: 8 UID: 0 Kdump: loaded Not tainted 6.17.0-rc4+ #107 PREEMPT(voluntary)\n  RIP: 0010:nsh_key_put_from_nlattr+0x19d/0x610 [openvswitch]\n  Call Trace:\n   \u0026lt;TASK\u0026gt;\n   validate_nsh+0x60/0x90 [openvswitch]\n   validate_set.constprop.0+0x270/0x3c0 [openvswitch]\n   __ovs_nla_copy_actions+0x477/0x860 [openvswitch]\n   ovs_nla_copy_actions+0x8d/0x100 [openvswitch]\n   ovs_packet_cmd_execute+0x1cc/0x310 [openvswitch]\n   genl_family_rcv_msg_doit+0xdb/0x130\n   genl_family_rcv_msg+0x14b/0x220\n   genl_rcv_msg+0x47/0xa0\n   netlink_rcv_skb+0x53/0x100\n   genl_rcv+0x24/0x40\n   netlink_unicast+0x280/0x3b0\n   netlink_sendmsg+0x1f7/0x430\n   ____sys_sendmsg+0x36b/0x3a0\n   ___sys_sendmsg+0x87/0xd0\n   __sys_sendmsg+0x6d/0xd0\n   do_syscall_64+0x7b/0x2c0\n   entry_SYSCALL_64_after_hwframe+0x76/0x7e\n\nThe third issue with this process is that while trying to convert\nthe non-masked set into masked one, validate_set() copies and doubles\nthe size of the OVS_KEY_ATTR_NSH as if it didn\u0026apos;t have any nested\nattributes.  It should be copying each nested attribute and doubling\nthem in size independently.  And the process must be properly reversed\nduring the conversion back from masked to a non-masked variant during\nthe flow dump.\n\nIn the end, the only two outcomes of trying to use this action are\neither validation failure or a kernel crash.  And if somehow someone\nmanages to install a flow with such an action, it will most definitely\nnot do what it is supposed to, since all the keys and the masks are\nmixed up.\n\nFixing all the issues is a complex task as it requires re-writing\nmost of the validation code.\n\nGiven that and the fact that this functionality never worked since\nintroduction, let\u0026apos;s just remove it altogether.  It\u0026apos;s better to\nre-introduce it later with a proper implementation instead of trying\nto fix it in stable releases.(CVE-2025-40254)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ntipc: Fix use-after-free in tipc_mon_reinit_self().\n\nsyzbot reported use-after-free of tipc_net(net)-\u0026gt;monitors[]\nin tipc_mon_reinit_self(). [0]\n\nThe array is protected by RTNL, but tipc_mon_reinit_self()\niterates over it without RTNL.\n\ntipc_mon_reinit_self() is called from tipc_net_finalize(),\nwhich is always under RTNL except for tipc_net_finalize_work().\n\nLet\u0026apos;s hold RTNL in tipc_net_finalize_work().\n\n[0]:\nBUG: KASAN: slab-use-after-free in __raw_spin_lock_irqsave include/linux/spinlock_api_smp.h:110 [inline]\nBUG: KASAN: slab-use-after-free in _raw_spin_lock_irqsave+0xa7/0xf0 kernel/locking/spinlock.c:162\nRead of size 1 at addr ffff88805eae1030 by task kworker/0:7/5989\n\nCPU: 0 UID: 0 PID: 5989 Comm: kworker/0:7 Not tainted syzkaller #0 PREEMPT_{RT,(full)}\nHardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 08/18/2025\nWorkqueue: events tipc_net_finalize_work\nCall Trace:\n \u0026lt;TASK\u0026gt;\n dump_stack_lvl+0x189/0x250 lib/dump_stack.c:120\n print_address_description mm/kasan/report.c:378 [inline]\n print_report+0xca/0x240 mm/kasan/report.c:482\n kasan_report+0x118/0x150 mm/kasan/report.c:595\n __kasan_check_byte+0x2a/0x40 mm/kasan/common.c:568\n kasan_check_byte include/linux/kasan.h:399 [inline]\n lock_acquire+0x8d/0x360 kernel/locking/lockdep.c:5842\n __raw_spin_lock_irqsave include/linux/spinlock_api_smp.h:110 [inline]\n _raw_spin_lock_irqsave+0xa7/0xf0 kernel/locking/spinlock.c:162\n rtlock_slowlock kernel/locking/rtmutex.c:1894 [inline]\n rwbase_rtmutex_lock_state kernel/locking/spinlock_rt.c:160 [inline]\n rwbase_write_lock+0xd3/0x7e0 kernel/locking/rwbase_rt.c:244\n rt_write_lock+0x76/0x110 kernel/locking/spinlock_rt.c:243\n write_lock_bh include/linux/rwlock_rt.h:99 [inline]\n tipc_mon_reinit_self+0x79/0x430 net/tipc/monitor.c:718\n tipc_net_finalize+0x115/0x190 net/tipc/net.c:140\n process_one_work kernel/workqueue.c:3236 [inline]\n process_scheduled_works+0xade/0x17b0 kernel/workqueue.c:3319\n worker_thread+0x8a0/0xda0 kernel/workqueue.c:3400\n kthread+0x70e/0x8a0 kernel/kthread.c:463\n ret_from_fork+0x439/0x7d0 arch/x86/kernel/process.c:148\n ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:245\n \u0026lt;/TASK\u0026gt;\n\nAllocated by task 6089:\n kasan_save_stack mm/kasan/common.c:47 [inline]\n kasan_save_track+0x3e/0x80 mm/kasan/common.c:68\n poison_kmalloc_redzone mm/kasan/common.c:388 [inline]\n __kasan_kmalloc+0x93/0xb0 mm/kasan/common.c:405\n kasan_kmalloc include/linux/kasan.h:260 [inline]\n __kmalloc_cache_noprof+0x1a8/0x320 mm/slub.c:4407\n kmalloc_noprof include/linux/slab.h:905 [inline]\n kzalloc_noprof include/linux/slab.h:1039 [inline]\n tipc_mon_create+0xc3/0x4d0 net/tipc/monitor.c:657\n tipc_enable_bearer net/tipc/bearer.c:357 [inline]\n __tipc_nl_bearer_enable+0xe16/0x13f0 net/tipc/bearer.c:1047\n __tipc_nl_compat_doit net/tipc/netlink_compat.c:371 [inline]\n tipc_nl_compat_doit+0x3bc/0x5f0 net/tipc/netlink_compat.c:393\n tipc_nl_compat_handle net/tipc/netlink_compat.c:-1 [inline]\n tipc_nl_compat_recv+0x83c/0xbe0 net/tipc/netlink_compat.c:1321\n genl_family_rcv_msg_doit+0x215/0x300 net/netlink/genetlink.c:1115\n genl_family_rcv_msg net/netlink/genetlink.c:1195 [inline]\n genl_rcv_msg+0x60e/0x790 net/netlink/genetlink.c:1210\n netlink_rcv_skb+0x208/0x470 net/netlink/af_netlink.c:2552\n genl_rcv+0x28/0x40 net/netlink/genetlink.c:1219\n netlink_unicast_kernel net/netlink/af_netlink.c:1320 [inline]\n netlink_unicast+0x846/0xa10 net/netlink/af_netlink.c:1346\n netlink_sendmsg+0x805/0xb30 net/netlink/af_netlink.c:1896\n sock_sendmsg_nosec net/socket.c:714 [inline]\n __sock_sendmsg+0x21c/0x270 net/socket.c:729\n ____sys_sendmsg+0x508/0x820 net/socket.c:2614\n ___sys_sendmsg+0x21f/0x2a0 net/socket.c:2668\n __sys_sendmsg net/socket.c:2700 [inline]\n __do_sys_sendmsg net/socket.c:2705 [inline]\n __se_sys_sendmsg net/socket.c:2703 [inline]\n __x64_sys_sendmsg+0x1a1/0x260 net/socket.c:2703\n do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline]\n do_syscall_64+0xfa/0x3b0 arch/\n---truncated---(CVE-2025-40280)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nsctp: prevent possible shift-out-of-bounds in sctp_transport_update_rto\n\nsyzbot reported a possible shift-out-of-bounds [1]\n\nBlamed commit added rto_alpha_max and rto_beta_max set to 1000.\n\nIt is unclear if some sctp users are setting very large rto_alpha\nand/or rto_beta.\n\nIn order to prevent user regression, perform the test at run time.\n\nAlso add READ_ONCE() annotations as sysctl values can change under us.\n\n[1]\n\nUBSAN: shift-out-of-bounds in net/sctp/transport.c:509:41\nshift exponent 64 is too large for 32-bit type \u0026apos;unsigned int\u0026apos;\nCPU: 0 UID: 0 PID: 16704 Comm: syz.2.2320 Not tainted syzkaller #0 PREEMPT(full)\nHardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 10/02/2025\nCall Trace:\n \u0026lt;TASK\u0026gt;\n  __dump_stack lib/dump_stack.c:94 [inline]\n  dump_stack_lvl+0x16c/0x1f0 lib/dump_stack.c:120\n  ubsan_epilogue lib/ubsan.c:233 [inline]\n  __ubsan_handle_shift_out_of_bounds+0x27f/0x420 lib/ubsan.c:494\n  sctp_transport_update_rto.cold+0x1c/0x34b net/sctp/transport.c:509\n  sctp_check_transmitted+0x11c4/0x1c30 net/sctp/outqueue.c:1502\n  sctp_outq_sack+0x4ef/0x1b20 net/sctp/outqueue.c:1338\n  sctp_cmd_process_sack net/sctp/sm_sideeffect.c:840 [inline]\n  sctp_cmd_interpreter net/sctp/sm_sideeffect.c:1372 [inline](CVE-2025-40281)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nsctp: Prevent TOCTOU out-of-bounds write\n\nFor the following path not holding the sock lock,\n\n  sctp_diag_dump() -\u0026gt; sctp_for_each_endpoint() -\u0026gt; sctp_ep_dump()\n\nmake sure not to exceed bounds in case the address list has grown\nbetween buffer allocation (time-of-check) and write (time-of-use).(CVE-2025-40331)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nlibceph: replace BUG_ON with bounds check for map-\u0026gt;max_osd\n\nOSD indexes come from untrusted network packets. Boundary checks are\nadded to validate these against map-\u0026gt;max_osd.\n\n[ idryomov: drop BUG_ON in ceph_get_primary_affinity(), minor cosmetic\n  edits ](CVE-2025-68283)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nlibceph: prevent potential out-of-bounds writes in handle_auth_session_key()\n\nThe len field originates from untrusted network packets. Boundary\nchecks have been added to prevent potential out-of-bounds writes when\ndecrypting the connection secret or processing service tickets.\n\n[ idryomov: changelog ](CVE-2025-68284)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nlibceph: fix potential use-after-free in have_mon_and_osd_map()\n\nThe wait loop in __ceph_open_session() can race with the client\nreceiving a new monmap or osdmap shortly after the initial map is\nreceived.  Both ceph_monc_handle_map() and handle_one_map() install\na new map immediately after freeing the old one\n\n    kfree(monc-\u0026gt;monmap);\n    monc-\u0026gt;monmap = monmap;\n\n    ceph_osdmap_destroy(osdc-\u0026gt;osdmap);\n    osdc-\u0026gt;osdmap = newmap;\n\nunder client-\u0026gt;monc.mutex and client-\u0026gt;osdc.lock respectively, but\nbecause neither is taken in have_mon_and_osd_map() it\u0026apos;s possible for\nclient-\u0026gt;monc.monmap-\u0026gt;epoch and client-\u0026gt;osdc.osdmap-\u0026gt;epoch arms in\n\n    client-\u0026gt;monc.monmap \u0026amp;\u0026amp; client-\u0026gt;monc.monmap-\u0026gt;epoch \u0026amp;\u0026amp;\n        client-\u0026gt;osdc.osdmap \u0026amp;\u0026amp; client-\u0026gt;osdc.osdmap-\u0026gt;epoch;\n\ncondition to dereference an already freed map.  This happens to be\nreproducible with generic/395 and generic/397 with KASAN enabled:\n\n    BUG: KASAN: slab-use-after-free in have_mon_and_osd_map+0x56/0x70\n    Read of size 4 at addr ffff88811012d810 by task mount.ceph/13305\n    CPU: 2 UID: 0 PID: 13305 Comm: mount.ceph Not tainted 6.14.0-rc2-build2+ #1266\n    ...\n    Call Trace:\n    \u0026lt;TASK\u0026gt;\n    have_mon_and_osd_map+0x56/0x70\n    ceph_open_session+0x182/0x290\n    ceph_get_tree+0x333/0x680\n    vfs_get_tree+0x49/0x180\n    do_new_mount+0x1a3/0x2d0\n    path_mount+0x6dd/0x730\n    do_mount+0x99/0xe0\n    __do_sys_mount+0x141/0x180\n    do_syscall_64+0x9f/0x100\n    entry_SYSCALL_64_after_hwframe+0x76/0x7e\n    \u0026lt;/TASK\u0026gt;\n\n    Allocated by task 13305:\n    ceph_osdmap_alloc+0x16/0x130\n    ceph_osdc_init+0x27a/0x4c0\n    ceph_create_client+0x153/0x190\n    create_fs_client+0x50/0x2a0\n    ceph_get_tree+0xff/0x680\n    vfs_get_tree+0x49/0x180\n    do_new_mount+0x1a3/0x2d0\n    path_mount+0x6dd/0x730\n    do_mount+0x99/0xe0\n    __do_sys_mount+0x141/0x180\n    do_syscall_64+0x9f/0x100\n    entry_SYSCALL_64_after_hwframe+0x76/0x7e\n\n    Freed by task 9475:\n    kfree+0x212/0x290\n    handle_one_map+0x23c/0x3b0\n    ceph_osdc_handle_map+0x3c9/0x590\n    mon_dispatch+0x655/0x6f0\n    ceph_con_process_message+0xc3/0xe0\n    ceph_con_v1_try_read+0x614/0x760\n    ceph_con_workfn+0x2de/0x650\n    process_one_work+0x486/0x7c0\n    process_scheduled_works+0x73/0x90\n    worker_thread+0x1c8/0x2a0\n    kthread+0x2ec/0x300\n    ret_from_fork+0x24/0x40\n    ret_from_fork_asm+0x1a/0x30\n\nRewrite the wait loop to check the above condition directly with\nclient-\u0026gt;monc.mutex and client-\u0026gt;osdc.lock taken as appropriate.  While\nat it, improve the timeout handling (previously mount_timeout could be\nexceeded in case wait_event_interruptible_timeout() slept more than\nonce) and access client-\u0026gt;auth_err under client-\u0026gt;monc.mutex to match\nhow it\u0026apos;s set in finish_auth().\n\nmonmap_show() and osdmap_show() now take the respective lock before\naccessing the map as well.(CVE-2025-68285)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nBluetooth: hci_core: lookup hci_conn on RX path on protocol side\n\nThe hdev lock/lookup/unlock/use pattern in the packet RX path doesn\u0026apos;t\nensure hci_conn* is not concurrently modified/deleted. This locking\nappears to be leftover from before conn_hash started using RCU\ncommit bf4c63252490b (\u0026quot;Bluetooth: convert conn hash to RCU\u0026quot;)\nand not clear if it had purpose since then.\n\nCurrently, there are code paths that delete hci_conn* from elsewhere\nthan the ordered hdev-\u0026gt;workqueue where the RX work runs in. E.g.\ncommit 5af1f84ed13a (\u0026quot;Bluetooth: hci_sync: Fix UAF on hci_abort_conn_sync\u0026quot;)\nintroduced some of these, and there probably were a few others before\nit.  It\u0026apos;s better to do the locking so that even if these run\nconcurrently no UAF is possible.\n\nMove the lookup of hci_conn and associated socket-specific conn to\nprotocol recv handlers, and do them within a single critical section\nto cover hci_conn* usage and lookup.\n\nsyzkaller has reported a crash that appears to be this issue:\n\n    [Task hdev-\u0026gt;workqueue]          [Task 2]\n                                    hci_disconnect_all_sync\n    l2cap_recv_acldata(hcon)\n                                      hci_conn_get(hcon)\n                                      hci_abort_conn_sync(hcon)\n                                        hci_dev_lock\n      hci_dev_lock\n                                        hci_conn_del(hcon)\n      v-------------------------------- hci_dev_unlock\n                                      hci_conn_put(hcon)\n      conn = hcon-\u0026gt;l2cap_data (UAF)(CVE-2025-68304)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nima: Handle error code returned by ima_filter_rule_match()\n\nIn ima_match_rules(), if ima_filter_rule_match() returns -ENOENT due to\nthe rule being NULL, the function incorrectly skips the \u0026apos;if (!rc)\u0026apos; check\nand sets \u0026apos;result = true\u0026apos;. The LSM rule is considered a match, causing\nextra files to be measured by IMA.\n\nThis issue can be reproduced in the following scenario:\nAfter unloading the SELinux policy module via \u0026apos;semodule -d\u0026apos;, if an IMA\nmeasurement is triggered before ima_lsm_rules is updated,\nin ima_match_rules(), the first call to ima_filter_rule_match() returns\n-ESTALE. This causes the code to enter the \u0026apos;if (rc == -ESTALE \u0026amp;\u0026amp;\n!rule_reinitialized)\u0026apos; block, perform ima_lsm_copy_rule() and retry. In\nima_lsm_copy_rule(), since the SELinux module has been removed, the rule\nbecomes NULL, and the second call to ima_filter_rule_match() returns\n-ENOENT. This bypasses the \u0026apos;if (!rc)\u0026apos; check and results in a false match.\n\nCall trace:\n  selinux_audit_rule_match+0x310/0x3b8\n  security_audit_rule_match+0x60/0xa0\n  ima_match_rules+0x2e4/0x4a0\n  ima_match_policy+0x9c/0x1e8\n  ima_get_action+0x48/0x60\n  process_measurement+0xf8/0xa98\n  ima_bprm_check+0x98/0xd8\n  security_bprm_check+0x5c/0x78\n  search_binary_handler+0x6c/0x318\n  exec_binprm+0x58/0x1b8\n  bprm_execve+0xb8/0x130\n  do_execveat_common.isra.0+0x1a8/0x258\n  __arm64_sys_execve+0x48/0x68\n  invoke_syscall+0x50/0x128\n  el0_svc_common.constprop.0+0xc8/0xf0\n  do_el0_svc+0x24/0x38\n  el0_svc+0x44/0x200\n  el0t_64_sync_handler+0x100/0x130\n  el0t_64_sync+0x3c8/0x3d0\n\nFix this by changing \u0026apos;if (!rc)\u0026apos; to \u0026apos;if (rc \u0026lt;= 0)\u0026apos; to ensure that error\ncodes like -ENOENT do not bypass the check and accidentally result in a\nsuccessful match.(CVE-2025-68740)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nbpf: Fix invalid prog-\u0026gt;stats access when update_effective_progs fails\n\nSyzkaller triggers an invalid memory access issue following fault\ninjection in update_effective_progs. The issue can be described as\nfollows:\n\n__cgroup_bpf_detach\n  update_effective_progs\n    compute_effective_progs\n      bpf_prog_array_alloc \u0026lt;-- fault inject\n  purge_effective_progs\n    /* change to dummy_bpf_prog */\n    array-\u0026gt;items[index] = \u0026amp;dummy_bpf_prog.prog\n\n---softirq start---\n__do_softirq\n  ...\n    __cgroup_bpf_run_filter_skb\n      __bpf_prog_run_save_cb\n        bpf_prog_run\n          stats = this_cpu_ptr(prog-\u0026gt;stats)\n          /* invalid memory access */\n          flags = u64_stats_update_begin_irqsave(\u0026amp;stats-\u0026gt;syncp)\n---softirq end---\n\n  static_branch_dec(\u0026amp;cgroup_bpf_enabled_key[atype])\n\nThe reason is that fault injection caused update_effective_progs to fail\nand then changed the original prog into dummy_bpf_prog.prog in\npurge_effective_progs. Then a softirq came, and accessing the members of\ndummy_bpf_prog.prog in the softirq triggers invalid mem access.\n\nTo fix it, skip updating stats when stats is NULL.(CVE-2025-68742)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nethtool: Avoid overflowing userspace buffer on stats query\n\nThe ethtool -S command operates across three ioctl calls:\nETHTOOL_GSSET_INFO for the size, ETHTOOL_GSTRINGS for the names, and\nETHTOOL_GSTATS for the values.\n\nIf the number of stats changes between these calls (e.g., due to device\nreconfiguration), userspace\u0026apos;s buffer allocation will be incorrect,\npotentially leading to buffer overflow.\n\nDrivers are generally expected to maintain stable stat counts, but some\ndrivers (e.g., mlx5, bnx2x, bna, ksz884x) use dynamic counters, making\nthis scenario possible.\n\nSome drivers try to handle this internally:\n- bnad_get_ethtool_stats() returns early in case stats.n_stats is not\n  equal to the driver\u0026apos;s stats count.\n- micrel/ksz884x also makes sure not to write anything beyond\n  stats.n_stats and overflow the buffer.\n\nHowever, both use stats.n_stats which is already assigned with the value\nreturned from get_sset_count(), hence won\u0026apos;t solve the issue described\nhere.\n\nChange ethtool_get_strings(), ethtool_get_stats(),\nethtool_get_phy_stats() to not return anything in case of a mismatch\nbetween userspace\u0026apos;s size and get_sset_size(), to prevent buffer\noverflow.\nThe returned n_stats value will be equal to zero, to reflect that\nnothing has been returned.\n\nThis could result in one of two cases when using upstream ethtool,\ndepending on when the size change is detected:\n1. When detected in ethtool_get_strings():\n    # ethtool -S eth2\n    no stats available\n\n2. When detected in get stats, all stats will be reported as zero.\n\nBoth cases are presumably transient, and a subsequent ethtool call\nshould succeed.\n\nOther than the overflow avoidance, these two cases are very evident (no\noutput/cleared stats), which is arguably better than presenting\nincorrect/shifted stats.\nI also considered returning an error instead of a \u0026quot;silent\u0026quot; response, but\nthat seems more destructive towards userspace apps.\n\nNotes:\n- This patch does not claim to fix the inherent race, it only makes sure\n  that we do not overflow the userspace buffer, and makes for a more\n  predictable behavior.\n\n- RTNL lock is held during each ioctl, the race window exists between\n  the separate ioctl calls when the lock is released.\n\n- Userspace ethtool always fills stats.n_stats, but it is likely that\n  these stats ioctls are implemented in other userspace applications\n  which might not fill it. The added code checks that it\u0026apos;s not zero,\n  to prevent any regressions.(CVE-2025-68795)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\next4: xattr: fix null pointer deref in ext4_raw_inode()\n\nIf ext4_get_inode_loc() fails (e.g. if it returns -EFSCORRUPTED),\niloc.bh will remain set to NULL. Since ext4_xattr_inode_dec_ref_all()\nlacks error checking, this will lead to a null pointer dereference\nin ext4_raw_inode(), called right after ext4_get_inode_loc().\n\nFound by Linux Verification Center (linuxtesting.org) with SVACE.(CVE-2025-68820)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnet: hns3: using the num_tqps in the vf driver to apply for resources\n\nCurrently, hdev-\u0026gt;htqp is allocated using hdev-\u0026gt;num_tqps, and kinfo-\u0026gt;tqp\nis allocated using kinfo-\u0026gt;num_tqps. However, kinfo-\u0026gt;num_tqps is set to\nmin(new_tqps, hdev-\u0026gt;num_tqps);  Therefore, kinfo-\u0026gt;num_tqps may be smaller\nthan hdev-\u0026gt;num_tqps, which causes some hdev-\u0026gt;htqp[i] to remain\nuninitialized in hclgevf_knic_setup().\n\nThus, this patch allocates hdev-\u0026gt;htqp and kinfo-\u0026gt;tqp using hdev-\u0026gt;num_tqps,\nensuring that the lengths of hdev-\u0026gt;htqp and kinfo-\u0026gt;tqp are consistent\nand that all elements are properly initialized.(CVE-2025-71064)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnet/sched: sch_qfq: Fix NULL deref when deactivating inactive aggregate in qfq_reset\n\n`qfq_class-\u0026gt;leaf_qdisc-\u0026gt;q.qlen \u0026gt; 0` does not imply that the class\nitself is active.\n\nTwo qfq_class objects may point to the same leaf_qdisc. This happens\nwhen:\n\n1. one QFQ qdisc is attached to the dev as the root qdisc, and\n\n2. another QFQ qdisc is temporarily referenced (e.g., via qdisc_get()\n/ qdisc_put()) and is pending to be destroyed, as in function\ntc_new_tfilter.\n\nWhen packets are enqueued through the root QFQ qdisc, the shared\nleaf_qdisc-\u0026gt;q.qlen increases. At the same time, the second QFQ\nqdisc triggers qdisc_put and qdisc_destroy: the qdisc enters\nqfq_reset() with its own q-\u0026gt;q.qlen == 0, but its class\u0026apos;s leaf\nqdisc-\u0026gt;q.qlen \u0026gt; 0. Therefore, the qfq_reset would wrongly deactivate\nan inactive aggregate and trigger a null-deref in qfq_deactivate_agg:\n\n[    0.903172] BUG: kernel NULL pointer dereference, address: 0000000000000000\n[    0.903571] #PF: supervisor write access in kernel mode\n[    0.903860] #PF: error_code(0x0002) - not-present page\n[    0.904177] PGD 10299b067 P4D 10299b067 PUD 10299c067 PMD 0\n[    0.904502] Oops: Oops: 0002 [#1] SMP NOPTI\n[    0.904737] CPU: 0 UID: 0 PID: 135 Comm: exploit Not tainted 6.19.0-rc3+ #2 NONE\n[    0.905157] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS rel-1.17.0-0-gb52ca86e094d-prebuilt.qemu.org 04/01/2014\n[    0.905754] RIP: 0010:qfq_deactivate_agg (include/linux/list.h:992 (discriminator 2) include/linux/list.h:1006 (discriminator 2) net/sched/sch_qfq.c:1367 (discriminator 2) net/sched/sch_qfq.c:1393 (discriminator 2))\n[    0.906046] Code: 0f 84 4d 01 00 00 48 89 70 18 8b 4b 10 48 c7 c2 ff ff ff ff 48 8b 78 08 48 d3 e2 48 21 f2 48 2b 13 48 8b 30 48 d3 ea 8b 4b 18 0\n\nCode starting with the faulting instruction\n===========================================\n   0:\t0f 84 4d 01 00 00    \tje     0x153\n   6:\t48 89 70 18          \tmov    %rsi,0x18(%rax)\n   a:\t8b 4b 10             \tmov    0x10(%rbx),%ecx\n   d:\t48 c7 c2 ff ff ff ff \tmov    $0xffffffffffffffff,%rdx\n  14:\t48 8b 78 08          \tmov    0x8(%rax),%rdi\n  18:\t48 d3 e2             \tshl    %cl,%rdx\n  1b:\t48 21 f2             \tand    %rsi,%rdx\n  1e:\t48 2b 13             \tsub    (%rbx),%rdx\n  21:\t48 8b 30             \tmov    (%rax),%rsi\n  24:\t48 d3 ea             \tshr    %cl,%rdx\n  27:\t8b 4b 18             \tmov    0x18(%rbx),%ecx\n\t...\n[    0.907095] RSP: 0018:ffffc900004a39a0 EFLAGS: 00010246\n[    0.907368] RAX: ffff8881043a0880 RBX: ffff888102953340 RCX: 0000000000000000\n[    0.907723] RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000000000000\n[    0.908100] RBP: ffff888102952180 R08: 0000000000000000 R09: 0000000000000000\n[    0.908451] R10: ffff8881043a0000 R11: 0000000000000000 R12: ffff888102952000\n[    0.908804] R13: ffff888102952180 R14: ffff8881043a0ad8 R15: ffff8881043a0880\n[    0.909179] FS:  000000002a1a0380(0000) GS:ffff888196d8d000(0000) knlGS:0000000000000000\n[    0.909572] CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033\n[    0.909857] CR2: 0000000000000000 CR3: 0000000102993002 CR4: 0000000000772ef0\n[    0.910247] PKRU: 55555554\n[    0.910391] Call Trace:\n[    0.910527]  \u0026lt;TASK\u0026gt;\n[    0.910638]  qfq_reset_qdisc (net/sched/sch_qfq.c:357 net/sched/sch_qfq.c:1485)\n[    0.910826]  qdisc_reset (include/linux/skbuff.h:2195 include/linux/skbuff.h:2501 include/linux/skbuff.h:3424 include/linux/skbuff.h:3430 net/sched/sch_generic.c:1036)\n[    0.911040]  __qdisc_destroy (net/sched/sch_generic.c:1076)\n[    0.911236]  tc_new_tfilter (net/sched/cls_api.c:2447)\n[    0.911447]  rtnetlink_rcv_msg (net/core/rtnetlink.c:6958)\n[    0.911663]  ? __pfx_rtnetlink_rcv_msg (net/core/rtnetlink.c:6861)\n[    0.911894]  netlink_rcv_skb (net/netlink/af_netlink.c:2550)\n[    0.912100]  netlink_unicast (net/netlink/af_netlink.c:1319 net/netlink/af_netlink.c:1344)\n[    0.912296]  ? __alloc_skb (net/core/skbuff.c:706)\n[    0.912484]  netlink_sendmsg (net/netlink/af\n---truncated---(CVE-2026-22976)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nbpf: Fix reference count leak in bpf_prog_test_run_xdp()\n\nsyzbot is reporting\n\n  unregister_netdevice: waiting for sit0 to become free. Usage count = 2\n\nproblem. A debug printk() patch found that a refcount is obtained at\nxdp_convert_md_to_buff() from bpf_prog_test_run_xdp().\n\nAccording to commit ec94670fcb3b (\u0026quot;bpf: Support specifying ingress via\nxdp_md context in BPF_PROG_TEST_RUN\u0026quot;), the refcount obtained by\nxdp_convert_md_to_buff() will be released by xdp_convert_buff_to_md().\n\nTherefore, we can consider that the error handling path introduced by\ncommit 1c1949982524 (\u0026quot;bpf: introduce frags support to\nbpf_prog_test_run_xdp()\u0026quot;) forgot to call xdp_convert_buff_to_md().(CVE-2026-22994)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nNFS: Fix a deadlock involving nfs_release_folio()\n\nWang Zhaolong reports a deadlock involving NFSv4.1 state recovery\nwaiting on kthreadd, which is attempting to reclaim memory by calling\nnfs_release_folio(). The latter cannot make progress due to state\nrecovery being needed.\n\nIt seems that the only safe thing to do here is to kick off a writeback\nof the folio, without waiting for completion, or else kicking off an\nasynchronous commit.(CVE-2026-23053)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nmedia: dvb-core: fix wrong reinitialization of ringbuffer on reopen\n\ndvb_dvr_open() calls dvb_ringbuffer_init() when a new reader opens the\nDVR device.  dvb_ringbuffer_init() calls init_waitqueue_head(), which\nreinitializes the waitqueue list head to empty.\n\nSince dmxdev-\u0026gt;dvr_buffer.queue is a shared waitqueue (all opens of the\nsame DVR device share it), this orphans any existing waitqueue entries\nfrom io_uring poll or epoll, leaving them with stale prev/next pointers\nwhile the list head is reset to {self, self}.\n\nThe waitqueue and spinlock in dvr_buffer are already properly\ninitialized once in dvb_dmxdev_init().  The open path only needs to\nreset the buffer data pointer, size, and read/write positions.\n\nReplace the dvb_ringbuffer_init() call in dvb_dvr_open() with direct\nassignment of data/size and a call to dvb_ringbuffer_reset(), which\nproperly resets pread, pwrite, and error with correct memory ordering\nwithout touching the waitqueue or spinlock.(CVE-2026-23253)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nregmap: maple: free entry on mas_store_gfp() failure\n\nregcache_maple_write() allocates a new block (\u0026apos;entry\u0026apos;) to merge\nadjacent ranges and then stores it with mas_store_gfp().\nWhen mas_store_gfp() fails, the new \u0026apos;entry\u0026apos; remains allocated and\nis never freed, leaking memory.\n\nFree \u0026apos;entry\u0026apos; on the failure path; on success continue freeing the\nreplaced neighbor blocks (\u0026apos;lower\u0026apos;, \u0026apos;upper\u0026apos;).(CVE-2026-23260)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\napparmor: fix unprivileged local user can do privileged policy management\n\nAn unprivileged local user can load, replace, and remove profiles by\nopening the apparmorfs interfaces, via a confused deputy attack, by\npassing the opened fd to a privileged process, and getting the\nprivileged process to write to the interface.\n\nThis does require a privileged target that can be manipulated to do\nthe write for the unprivileged process, but once such access is\nachieved full policy management is possible and all the possible\nimplications that implies: removing confinement, DoS of system or\ntarget applications by denying all execution, by-passing the\nunprivileged user namespace restriction, to exploiting kernel bugs for\na local privilege escalation.\n\nThe policy management interface can not have its permissions simply\nchanged from 0666 to 0600 because non-root processes need to be able\nto load policy to different policy namespaces.\n\nInstead ensure the task writing the interface has privileges that\nare a subset of the task that opened the interface. This is already\ndone via policy for confined processes, but unconfined can delegate\naccess to the opened fd, by-passing the usual policy check.(CVE-2026-23268)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nperf: Fix __perf_event_overflow() vs perf_remove_from_context() race\n\nMake sure that __perf_event_overflow() runs with IRQs disabled for all\npossible callchains. Specifically the software events can end up running\nit with only preemption disabled.\n\nThis opens up a race vs perf_event_exit_event() and friends that will go\nand free various things the overflow path expects to be present, like\nthe BPF program.(CVE-2026-23271)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nmacvlan: observe an RCU grace period in macvlan_common_newlink() error path\n\nvalis reported that a race condition still happens after my prior patch.\n\nmacvlan_common_newlink() might have made @dev visible before\ndetecting an error, and its caller will directly call free_netdev(dev).\n\nWe must respect an RCU period, either in macvlan or the core networking\nstack.\n\nAfter adding a temporary mdelay(1000) in macvlan_forward_source_one()\nto open the race window, valis repro was:\n\nip link add p1 type veth peer p2\nip link set address 00:00:00:00:00:20 dev p1\nip link set up dev p1\nip link set up dev p2\nip link add mv0 link p2 type macvlan mode source\n\n(ip link add invalid% link p2 type macvlan mode source macaddr add\n00:00:00:00:00:20 \u0026amp;) ; sleep 0.5 ; ping -c1 -I p1 1.2.3.4\nPING 1.2.3.4 (1.2.3.4): 56 data bytes\nRTNETLINK answers: Invalid argument\n\nBUG: KASAN: slab-use-after-free in macvlan_forward_source\n(drivers/net/macvlan.c:408 drivers/net/macvlan.c:444)\nRead of size 8 at addr ffff888016bb89c0 by task e/175\n\nCPU: 1 UID: 1000 PID: 175 Comm: e Not tainted 6.19.0-rc8+ #33 NONE\nHardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.14.0-2 04/01/2014\nCall Trace:\n\u0026lt;IRQ\u0026gt;\ndump_stack_lvl (lib/dump_stack.c:123)\nprint_report (mm/kasan/report.c:379 mm/kasan/report.c:482)\n? macvlan_forward_source (drivers/net/macvlan.c:408 drivers/net/macvlan.c:444)\nkasan_report (mm/kasan/report.c:597)\n? macvlan_forward_source (drivers/net/macvlan.c:408 drivers/net/macvlan.c:444)\nmacvlan_forward_source (drivers/net/macvlan.c:408 drivers/net/macvlan.c:444)\n? tasklet_init (kernel/softirq.c:983)\nmacvlan_handle_frame (drivers/net/macvlan.c:501)\n\nAllocated by task 169:\nkasan_save_stack (mm/kasan/common.c:58)\nkasan_save_track (./arch/x86/include/asm/current.h:25\nmm/kasan/common.c:70 mm/kasan/common.c:79)\n__kasan_kmalloc (mm/kasan/common.c:419)\n__kvmalloc_node_noprof (./include/linux/kasan.h:263 mm/slub.c:5657\nmm/slub.c:7140)\nalloc_netdev_mqs (net/core/dev.c:12012)\nrtnl_create_link (net/core/rtnetlink.c:3648)\nrtnl_newlink (net/core/rtnetlink.c:3830 net/core/rtnetlink.c:3957\nnet/core/rtnetlink.c:4072)\nrtnetlink_rcv_msg (net/core/rtnetlink.c:6958)\nnetlink_rcv_skb (net/netlink/af_netlink.c:2550)\nnetlink_unicast (net/netlink/af_netlink.c:1319 net/netlink/af_netlink.c:1344)\nnetlink_sendmsg (net/netlink/af_netlink.c:1894)\n__sys_sendto (net/socket.c:727 net/socket.c:742 net/socket.c:2206)\n__x64_sys_sendto (net/socket.c:2209)\ndo_syscall_64 (arch/x86/entry/syscall_64.c:63 arch/x86/entry/syscall_64.c:94)\nentry_SYSCALL_64_after_hwframe (arch/x86/entry/entry_64.S:131)\n\nFreed by task 169:\nkasan_save_stack (mm/kasan/common.c:58)\nkasan_save_track (./arch/x86/include/asm/current.h:25\nmm/kasan/common.c:70 mm/kasan/common.c:79)\nkasan_save_free_info (mm/kasan/generic.c:587)\n__kasan_slab_free (mm/kasan/common.c:287)\nkfree (mm/slub.c:6674 mm/slub.c:6882)\nrtnl_newlink (net/core/rtnetlink.c:3845 net/core/rtnetlink.c:3957\nnet/core/rtnetlink.c:4072)\nrtnetlink_rcv_msg (net/core/rtnetlink.c:6958)\nnetlink_rcv_skb (net/netlink/af_netlink.c:2550)\nnetlink_unicast (net/netlink/af_netlink.c:1319 net/netlink/af_netlink.c:1344)\nnetlink_sendmsg (net/netlink/af_netlink.c:1894)\n__sys_sendto (net/socket.c:727 net/socket.c:742 net/socket.c:2206)\n__x64_sys_sendto (net/socket.c:2209)\ndo_syscall_64 (arch/x86/entry/syscall_64.c:63 arch/x86/entry/syscall_64.c:94)\nentry_SYSCALL_64_after_hwframe (arch/x86/entry/entry_64.S:131)(CVE-2026-23273)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nscsi: target: Fix recursive locking in __configfs_open_file()\n\nIn flush_write_buffer, \u0026amp;p-\u0026gt;frag_sem is acquired and then the loaded store\nfunction is called, which, here, is target_core_item_dbroot_store().  This\nfunction called filp_open(), following which these functions were called\n(in reverse order), according to the call trace:\n\n  down_read\n  __configfs_open_file\n  do_dentry_open\n  vfs_open\n  do_open\n  path_openat\n  do_filp_open\n  file_open_name\n  filp_open\n  target_core_item_dbroot_store\n  flush_write_buffer\n  configfs_write_iter\n\ntarget_core_item_dbroot_store() tries to validate the new file path by\ntrying to open the file path provided to it; however, in this case, the bug\nreport shows:\n\ndb_root: not a directory: /sys/kernel/config/target/dbroot\n\nindicating that the same configfs file was tried to be opened, on which it\nis currently working on. Thus, it is trying to acquire frag_sem semaphore\nof the same file of which it already holds the semaphore obtained in\nflush_write_buffer(), leading to acquiring the semaphore in a nested manner\nand a possibility of recursive locking.\n\nFix this by modifying target_core_item_dbroot_store() to use kern_path()\ninstead of filp_open() to avoid opening the file using filesystem-specific\nfunction __configfs_open_file(), and further modifying it to make this fix\ncompatible.(CVE-2026-23292)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nscsi: core: Fix refcount leak for tagset_refcnt\n\nThis leak will cause a hang when tearing down the SCSI host. For example,\niscsid hangs with the following call trace:\n\n[130120.652718] scsi_alloc_sdev: Allocation failure during SCSI scanning, some SCSI devices might not be configured\n\nPID: 2528     TASK: ffff9d0408974e00  CPU: 3    COMMAND: \u0026quot;iscsid\u0026quot;\n #0 [ffffb5b9c134b9e0] __schedule at ffffffff860657d4\n #1 [ffffb5b9c134ba28] schedule at ffffffff86065c6f\n #2 [ffffb5b9c134ba40] schedule_timeout at ffffffff86069fb0\n #3 [ffffb5b9c134bab0] __wait_for_common at ffffffff8606674f\n #4 [ffffb5b9c134bb10] scsi_remove_host at ffffffff85bfe84b\n #5 [ffffb5b9c134bb30] iscsi_sw_tcp_session_destroy at ffffffffc03031c4 [iscsi_tcp]\n #6 [ffffb5b9c134bb48] iscsi_if_recv_msg at ffffffffc0292692 [scsi_transport_iscsi]\n #7 [ffffb5b9c134bb98] iscsi_if_rx at ffffffffc02929c2 [scsi_transport_iscsi]\n #8 [ffffb5b9c134bbf0] netlink_unicast at ffffffff85e551d6\n #9 [ffffb5b9c134bc38] netlink_sendmsg at ffffffff85e554ef(CVE-2026-23296)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ni40e: Fix preempt count leak in napi poll tracepoint\n\nUsing get_cpu() in the tracepoint assignment causes an obvious preempt\ncount leak because nothing invokes put_cpu() to undo it:\n\n  softirq: huh, entered softirq 3 NET_RX with preempt_count 00000100, exited with 00000101?\n\nThis clearly has seen a lot of testing in the last 3+ years...\n\nUse smp_processor_id() instead.(CVE-2026-23313)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ndrm/vmwgfx: Return the correct value in vmw_translate_ptr functions\n\nBefore the referenced fixes these functions used a lookup function that\nreturned a pointer. This was changed to another lookup function that\nreturned an error code with the pointer becoming an out parameter.\n\nThe error path when the lookup failed was not changed to reflect this\nchange and the code continued to return the PTR_ERR of the now\nuninitialized pointer. This could cause the vmw_translate_ptr functions\nto return success when they actually failed causing further uninitialized\nand OOB accesses.(CVE-2026-23317)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nbpf: Fix a UAF issue in bpf_trampoline_link_cgroup_shim\n\nThe root cause of this bug is that when \u0026apos;bpf_link_put\u0026apos; reduces the\nrefcount of \u0026apos;shim_link-\u0026gt;link.link\u0026apos; to zero, the resource is considered\nreleased but may still be referenced via \u0026apos;tr-\u0026gt;progs_hlist\u0026apos; in\n\u0026apos;cgroup_shim_find\u0026apos;. The actual cleanup of \u0026apos;tr-\u0026gt;progs_hlist\u0026apos; in\n\u0026apos;bpf_shim_tramp_link_release\u0026apos; is deferred. During this window, another\nprocess can cause a use-after-free via \u0026apos;bpf_trampoline_link_cgroup_shim\u0026apos;.\n\nBased on Martin KaFai Lau\u0026apos;s suggestions, I have created a simple patch.\n\nTo fix this:\n   Add an atomic non-zero check in \u0026apos;bpf_trampoline_link_cgroup_shim\u0026apos;.\n   Only increment the refcount if it is not already zero.\n\nTesting:\n   I verified the fix by adding a delay in\n   \u0026apos;bpf_shim_tramp_link_release\u0026apos; to make the bug easier to trigger:\n\nstatic void bpf_shim_tramp_link_release(struct bpf_link *link)\n{\n\t/* ... */\n\tif (!shim_link-\u0026gt;trampoline)\n\t\treturn;\n\n+\tmsleep(100);\n\tWARN_ON_ONCE(bpf_trampoline_unlink_prog(\u0026amp;shim_link-\u0026gt;link,\n\t\tshim_link-\u0026gt;trampoline, NULL));\n\tbpf_trampoline_put(shim_link-\u0026gt;trampoline);\n}\n\nBefore the patch, running a PoC easily reproduced the crash(almost 100%)\nwith a call trace similar to KaiyanM\u0026apos;s report.\nAfter the patch, the bug no longer occurs even after millions of\niterations.(CVE-2026-23319)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nx86/efi: defer freeing of boot services memory\n\nefi_free_boot_services() frees memory occupied by EFI_BOOT_SERVICES_CODE\nand EFI_BOOT_SERVICES_DATA using memblock_free_late().\n\nThere are two issue with that: memblock_free_late() should be used for\nmemory allocated with memblock_alloc() while the memory reserved with\nmemblock_reserve() should be freed with free_reserved_area().\n\nMore acutely, with CONFIG_DEFERRED_STRUCT_PAGE_INIT=y\nefi_free_boot_services() is called before deferred initialization of the\nmemory map is complete.\n\nBenjamin Herrenschmidt reports that this causes a leak of ~140MB of\nRAM on EC2 t3a.nano instances which only have 512MB or RAM.\n\nIf the freed memory resides in the areas that memory map for them is\nstill uninitialized, they won\u0026apos;t be actually freed because\nmemblock_free_late() calls memblock_free_pages() and the latter skips\nuninitialized pages.\n\nUsing free_reserved_area() at this point is also problematic because\n__free_page() accesses the buddy of the freed page and that again might\nend up in uninitialized part of the memory map.\n\nDelaying the entire efi_free_boot_services() could be problematic\nbecause in addition to freeing boot services memory it updates\nefi.memmap without any synchronization and that\u0026apos;s undesirable late in\nboot when there is concurrency.\n\nMore robust approach is to only defer freeing of the EFI boot services\nmemory.\n\nSplit efi_free_boot_services() in two. First efi_unmap_boot_services()\ncollects ranges that should be freed into an array then\nefi_free_boot_services() later frees them after deferred init is complete.(CVE-2026-23352)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nbpf: Fix stack-out-of-bounds write in devmap\n\nget_upper_ifindexes() iterates over all upper devices and writes their\nindices into an array without checking bounds.\n\nAlso the callers assume that the max number of upper devices is\nMAX_NEST_DEV and allocate excluded_devices[1+MAX_NEST_DEV] on the stack,\nbut that assumption is not correct and the number of upper devices could\nbe larger than MAX_NEST_DEV (e.g., many macvlans), causing a\nstack-out-of-bounds write.\n\nAdd a max parameter to get_upper_ifindexes() to avoid the issue.\nWhen there are too many upper devices, return -EOVERFLOW and abort the\nredirect.\n\nTo reproduce, create more than MAX_NEST_DEV(8) macvlans on a device with\nan XDP program attached using BPF_F_BROADCAST | BPF_F_EXCLUDE_INGRESS.\nThen send a packet to the device to trigger the XDP redirect path.(CVE-2026-23359)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnvme: fix admin queue leak on controller reset\n\nWhen nvme_alloc_admin_tag_set() is called during a controller reset,\na previous admin queue may still exist. Release it properly before\nallocating a new one to avoid orphaning the old queue.\n\nThis fixes a regression introduced by commit 03b3bcd319b3 (\u0026quot;nvme: fix\nadmin request_queue lifetime\u0026quot;).(CVE-2026-23360)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nblktrace: fix __this_cpu_read/write in preemptible context\n\ntracing_record_cmdline() internally uses __this_cpu_read() and\n__this_cpu_write() on the per-CPU variable trace_cmdline_save, and\ntrace_save_cmdline() explicitly asserts preemption is disabled via\nlockdep_assert_preemption_disabled(). These operations are only safe\nwhen preemption is off, as they were designed to be called from the\nscheduler context (probe_wakeup_sched_switch() / probe_wakeup()).\n\n__blk_add_trace() was calling tracing_record_cmdline(current) early in\nthe blk_tracer path, before ring buffer reservation, from process\ncontext where preemption is fully enabled. This triggers the following\nusing blktests/blktrace/002:\n\nblktrace/002 (blktrace ftrace corruption with sysfs trace)   [failed]\n    runtime  0.367s  ...  0.437s\n    something found in dmesg:\n    [   81.211018] run blktests blktrace/002 at 2026-02-25 22:24:33\n    [   81.239580] null_blk: disk nullb1 created\n    [   81.357294] BUG: using __this_cpu_read() in preemptible [00000000] code: dd/2516\n    [   81.362842] caller is tracing_record_cmdline+0x10/0x40\n    [   81.362872] CPU: 16 UID: 0 PID: 2516 Comm: dd Tainted: G                 N  7.0.0-rc1lblk+ #84 PREEMPT(full)\n    [   81.362877] Tainted: [N]=TEST\n    [   81.362878] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS rel-1.17.0-0-gb52ca86e094d-prebuilt.qemu.org 04/01/2014\n    [   81.362881] Call Trace:\n    [   81.362884]  \u0026lt;TASK\u0026gt;\n    [   81.362886]  dump_stack_lvl+0x8d/0xb0\n    ...\n    (See \u0026apos;/mnt/sda/blktests/results/nodev/blktrace/002.dmesg\u0026apos; for the entire message)\n\n[   81.211018] run blktests blktrace/002 at 2026-02-25 22:24:33\n[   81.239580] null_blk: disk nullb1 created\n[   81.357294] BUG: using __this_cpu_read() in preemptible [00000000] code: dd/2516\n[   81.362842] caller is tracing_record_cmdline+0x10/0x40\n[   81.362872] CPU: 16 UID: 0 PID: 2516 Comm: dd Tainted: G                 N  7.0.0-rc1lblk+ #84 PREEMPT(full)\n[   81.362877] Tainted: [N]=TEST\n[   81.362878] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS rel-1.17.0-0-gb52ca86e094d-prebuilt.qemu.org 04/01/2014\n[   81.362881] Call Trace:\n[   81.362884]  \u0026lt;TASK\u0026gt;\n[   81.362886]  dump_stack_lvl+0x8d/0xb0\n[   81.362895]  check_preemption_disabled+0xce/0xe0\n[   81.362902]  tracing_record_cmdline+0x10/0x40\n[   81.362923]  __blk_add_trace+0x307/0x5d0\n[   81.362934]  ? lock_acquire+0xe0/0x300\n[   81.362940]  ? iov_iter_extract_pages+0x101/0xa30\n[   81.362959]  blk_add_trace_bio+0x106/0x1e0\n[   81.362968]  submit_bio_noacct_nocheck+0x24b/0x3a0\n[   81.362979]  ? lockdep_init_map_type+0x58/0x260\n[   81.362988]  submit_bio_wait+0x56/0x90\n[   81.363009]  __blkdev_direct_IO_simple+0x16c/0x250\n[   81.363026]  ? __pfx_submit_bio_wait_endio+0x10/0x10\n[   81.363038]  ? rcu_read_lock_any_held+0x73/0xa0\n[   81.363051]  blkdev_read_iter+0xc1/0x140\n[   81.363059]  vfs_read+0x20b/0x330\n[   81.363083]  ksys_read+0x67/0xe0\n[   81.363090]  do_syscall_64+0xbf/0xf00\n[   81.363102]  entry_SYSCALL_64_after_hwframe+0x76/0x7e\n[   81.363106] RIP: 0033:0x7f281906029d\n[   81.363111] Code: 31 c0 e9 c6 fe ff ff 50 48 8d 3d 66 63 0a 00 e8 59 ff 01 00 66 0f 1f 84 00 00 00 00 00 80 3d 41 33 0e 00 00 74 17 31 c0 0f 05 \u0026lt;48\u0026gt; 3d 00 f0 ff ff 77 5b c3 66 2e 0f 1f 84 00 00 00 00 00 48 83 ec\n[   81.363113] RSP: 002b:00007ffca127dd48 EFLAGS: 00000246 ORIG_RAX: 0000000000000000\n[   81.363120] RAX: ffffffffffffffda RBX: 0000000000000000 RCX: 00007f281906029d\n[   81.363122] RDX: 0000000000001000 RSI: 0000559f8bfae000 RDI: 0000000000000000\n[   81.363123] RBP: 0000000000001000 R08: 0000002863a10a81 R09: 00007f281915f000\n[   81.363124] R10: 00007f2818f77b60 R11: 0000000000000246 R12: 0000559f8bfae000\n[   81.363126] R13: 0000000000000000 R14: 0000000000000000 R15: 000000000000000a\n[   81.363142]  \u0026lt;/TASK\u0026gt;\n\nThe same BUG fires from blk_add_trace_plug(), blk_add_trace_unplug(),\nand blk_add_trace_rq() paths as well.\n\nThe purpose of tracin\n---truncated---(CVE-2026-23374)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nbpf, arm64: Force 8-byte alignment for JIT buffer to prevent atomic tearing\n\nstruct bpf_plt contains a u64 target field. Currently, the BPF JIT\nallocator requests an alignment of 4 bytes (sizeof(u32)) for the JIT\nbuffer.\n\nBecause the base address of the JIT buffer can be 4-byte aligned (e.g.,\nending in 0x4 or 0xc), the relative padding logic in build_plt() fails\nto ensure that target lands on an 8-byte boundary.\n\nThis leads to two issues:\n1. UBSAN reports misaligned-access warnings when dereferencing the\n   structure.\n2. More critically, target is updated concurrently via WRITE_ONCE() in\n   bpf_arch_text_poke() while the JIT\u0026apos;d code executes ldr. On arm64,\n   64-bit loads/stores are only guaranteed to be single-copy atomic if\n   they are 64-bit aligned. A misaligned target risks a torn read,\n   causing the JIT to jump to a corrupted address.\n\nFix this by increasing the allocation alignment requirement to 8 bytes\n(sizeof(u64)) in bpf_jit_binary_pack_alloc(). This anchors the base of\nthe JIT buffer to an 8-byte boundary, allowing the relative padding math\nin build_plt() to correctly align the target field.(CVE-2026-23383)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nSquashfs: check metadata block offset is within range\n\nSyzkaller reports a \u0026quot;general protection fault in squashfs_copy_data\u0026quot;\n\nThis is ultimately caused by a corrupted index look-up table, which\nproduces a negative metadata block offset.\n\nThis is subsequently passed to squashfs_copy_data (via\nsquashfs_read_metadata) where the negative offset causes an out of bounds\naccess.\n\nThe fix is to check that the offset is within range in\nsquashfs_read_metadata.  This will trap this and other cases.(CVE-2026-23388)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\next4: reject mount if bigalloc with s_first_data_block != 0\n\nbigalloc with s_first_data_block != 0 is not supported, reject mounting\nit.(CVE-2026-31447)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nHID: multitouch: Check to ensure report responses match the request\n\nIt is possible for a malicious (or clumsy) device to respond to a\nspecific report\u0026apos;s feature request using a completely different report\nID.  This can cause confusion in the HID core resulting in nasty\nside-effects such as OOB writes.\n\nAdd a check to ensure that the report ID in the response, matches the\none that was requested.  If it doesn\u0026apos;t, omit reporting the raw event and\nreturn early.(CVE-2026-43047)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nHID: core: Mitigate potential OOB by removing bogus memset()\n\nThe memset() in hid_report_raw_event() has the good intention of\nclearing out bogus data by zeroing the area from the end of the incoming\ndata string to the assumed end of the buffer.  However, as we have\npreviously seen, doing so can easily result in OOB reads and writes in\nthe subsequent thread of execution.\n\nThe current suggestion from one of the HID maintainers is to remove the\nmemset() and simply return if the incoming event buffer size is not\nlarge enough to fill the associated report.\n\nSuggested-by Benjamin Tissoires \u0026lt;(CVE-2026-43048)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nxfs: close crash window in attr dabtree inactivation\n\nWhen inactivating an inode with node-format extended attributes,\nxfs_attr3_node_inactive() invalidates all child leaf/node blocks via\nxfs_trans_binval(), but intentionally does not remove the corresponding\nentries from their parent node blocks.  The implicit assumption is that\nxfs_attr_inactive() will truncate the entire attr fork to zero extents\nafterwards, so log recovery will never reach the root node and follow\nthose stale pointers.\n\nHowever, if a log shutdown occurs after the leaf/node block cancellations\ncommit but before the attr bmap truncation commits, this assumption\nbreaks.  Recovery replays the attr bmap intact (the inode still has\nattr fork extents), but suppresses replay of all cancelled leaf/node\nblocks, maybe leaving them as stale data on disk.  On the next mount,\nxlog_recover_process_iunlinks() retries inactivation and attempts to\nread the root node via the attr bmap. If the root node was not replayed,\nreading the unreplayed root block triggers a metadata verification\nfailure immediately; if it was replayed, following its child pointers\nto unreplayed child blocks triggers the same failure:\n\n XFS (pmem0): Metadata corruption detected at\n xfs_da3_node_read_verify+0x53/0x220, xfs_da3_node block 0x78\n XFS (pmem0): Unmount and run xfs_repair\n XFS (pmem0): First 128 bytes of corrupted metadata buffer:\n 00000000: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................\n 00000010: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................\n 00000020: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................\n 00000030: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................\n 00000040: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................\n 00000050: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................\n 00000060: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................\n 00000070: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................\n XFS (pmem0): metadata I/O error in \u0026quot;xfs_da_read_buf+0x104/0x190\u0026quot; at daddr 0x78 len 8 error 117\n\nFix this in two places:\n\nIn xfs_attr3_node_inactive(), after calling xfs_trans_binval() on a\nchild block, immediately remove the entry that references it from the\nparent node in the same transaction.  This eliminates the window where\nthe parent holds a pointer to a cancelled block.  Once all children are\nremoved, the now-empty root node is converted to a leaf block within the\nsame transaction. This node-to-leaf conversion is necessary for crash\nsafety. If the system shutdown after the empty node is written to the\nlog but before the second-phase bmap truncation commits, log recovery\nwill attempt to verify the root block on disk. xfs_da3_node_verify()\ndoes not permit a node block with count == 0; such a block will fail\nverification and trigger a metadata corruption shutdown. on the other\nhand, leaf blocks are allowed to have this transient state.\n\nIn xfs_attr_inactive(), split the attr fork truncation into two explicit\nphases.  First, truncate all extents beyond the root block (the child\nextents whose parent references have already been removed above).\nSecond, invalidate the root block and truncate the attr bmap to zero in\na single transaction.  The two operations in the second phase must be\natomic: as long as the attr bmap has any non-zero length, recovery can\nfollow it to the root block, so the root block invalidation must commit\ntogether with the bmap-to-zero truncation.(CVE-2026-43053)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nRevert \u0026quot;PCI/IOV: Add PCI rescan-remove locking when enabling/disabling SR-IOV\u0026quot;\n\nThis reverts commit 05703271c3cd (\u0026quot;PCI/IOV: Add PCI rescan-remove locking\nwhen enabling/disabling SR-IOV\u0026quot;), which causes a deadlock by recursively\ntaking pci_rescan_remove_lock when sriov_del_vfs() is called as part of\npci_stop_and_remove_bus_device(). For example with the following sequence\nof commands:\n\n  $ echo \u0026lt;NUM\u0026gt; \u0026gt; /sys/bus/pci/devices/\u0026lt;pf\u0026gt;/sriov_numvfs\n  $ echo 1 \u0026gt; /sys/bus/pci/devices/\u0026lt;pf\u0026gt;/remove\n\nA trimmed trace of the deadlock on a mlx5 device is as below:\n\n  zsh/5715 is trying to acquire lock:\n  000002597926ef50 (pci_rescan_remove_lock){+.+.}-{3:3}, at: sriov_disable+0x34/0x140\n\n  but task is already holding lock:\n  000002597926ef50 (pci_rescan_remove_lock){+.+.}-{3:3}, at: pci_stop_and_remove_bus_device_locked+0x24/0x80\n  ...\n  Call Trace:\n   [\u0026lt;00000259778c4f90\u0026gt;] dump_stack_lvl+0xc0/0x110\n   [\u0026lt;00000259779c844e\u0026gt;] print_deadlock_bug+0x31e/0x330\n   [\u0026lt;00000259779c1908\u0026gt;] __lock_acquire+0x16c8/0x32f0\n   [\u0026lt;00000259779bffac\u0026gt;] lock_acquire+0x14c/0x350\n   [\u0026lt;00000259789643a6\u0026gt;] __mutex_lock_common+0xe6/0x1520\n   [\u0026lt;000002597896413c\u0026gt;] mutex_lock_nested+0x3c/0x50\n   [\u0026lt;00000259784a07e4\u0026gt;] sriov_disable+0x34/0x140\n   [\u0026lt;00000258f7d6dd80\u0026gt;] mlx5_sriov_disable+0x50/0x80 [mlx5_core]\n   [\u0026lt;00000258f7d5745e\u0026gt;] remove_one+0x5e/0xf0 [mlx5_core]\n   [\u0026lt;00000259784857fc\u0026gt;] pci_device_remove+0x3c/0xa0\n   [\u0026lt;000002597851012e\u0026gt;] device_release_driver_internal+0x18e/0x280\n   [\u0026lt;000002597847ae22\u0026gt;] pci_stop_bus_device+0x82/0xa0\n   [\u0026lt;000002597847afce\u0026gt;] pci_stop_and_remove_bus_device_locked+0x5e/0x80\n   [\u0026lt;00000259784972c2\u0026gt;] remove_store+0x72/0x90\n   [\u0026lt;0000025977e6661a\u0026gt;] kernfs_fop_write_iter+0x15a/0x200\n   [\u0026lt;0000025977d7241c\u0026gt;] vfs_write+0x24c/0x300\n   [\u0026lt;0000025977d72696\u0026gt;] ksys_write+0x86/0x110\n   [\u0026lt;000002597895b61c\u0026gt;] __do_syscall+0x14c/0x400\n   [\u0026lt;000002597896e0ee\u0026gt;] system_call+0x6e/0x90\n\nThis alone is not a complete fix as it restores the issue the cited commit\ntried to solve. A new fix will be provided as a follow on.(CVE-2026-43147)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\narm64: Add support for TSV110 Spectre-BHB mitigation\n\nThe TSV110 processor is vulnerable to the Spectre-BHB (Branch History\nBuffer) attack, which can be exploited to leak information through\nbranch prediction side channels. This commit adds the MIDR of TSV110\nto the list for software mitigation.(CVE-2026-43261)\n\nIn the Linux kernel, the kexec_load_purgatory() function derives image-\u0026gt;start by locating e_entry inside an SHF_EXECINSTR section. If the purgatory object contains multiple executable sections with overlapping sh_addr, the entrypoint check can match more than once and trigger a WARN. Derive the entry section from the purgatory_start symbol when present and compute image-\u0026gt;start from its final placement. Keep the existing e_entry fallback for purgatories that do not expose the symbol.(CVE-2026-43289)\n\nIn the Linux kernel, there is a potential out-of-bounds access vulnerability in the ceph_handle_auth_reply() function of the libceph component. When processing messages of type CEPH_MSG_AUTH_REPLY, the value of the payload_len field is stored in a variable of type int. A value greater than INT_MAX leads to integer overflow and is interpreted as a negative value, which causes the pointer address to be decremented and subsequently accessed because ceph_decode_need() only checks that the memory access does not exceed the end address of the allocation. The vulnerability is fixed by changing the data type of payload_len to u32 and introducing additional sanity checks.(CVE-2026-43407)\n\nIn the Linux kernel, when an alias is found through d_splice_alias in the nfs3_proc_create function, if the alias happens to be a directory dentry, the system does not return any error but simply forgets about this alias, leaving the original dentry to be added as negative. This later causes a system crash in nfs_atomic_open_v23/finish_open since a negative dentry is supplied to do_dentry_open. This issue was observed running lustre-racer, where directories and files are created/removed concurrently with the same name and O_EXCL is not used to open files.(CVE-2026-43470)","status":"published","published":"2026-05-22T11:11:22Z","modified":"2026-08-18T01:20:02.121651445Z","cvss":[{"version":"3.1","score":9.1,"vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:H","level":"critical"}],"updated_at":"2026-11-02T15:52:46.449097Z"},{"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-56760","description":"In the Linux kernel, the following vulnerability has been resolved: PCI/MSI: Handle lack of irqdomain gracefully Alexandre observed a warning emitted from pci_msi_setup_msi_irqs() on a RISCV platform which does not provide PCI/MSI support:  WARNING: CPU: 1 PID: 1 at drivers/pci/msi/msi.h:121 pci_msi_setup_msi_irqs+0x2c/0x32  __pci_enable_msix_range+0x30c/0x596  pci_msi_setup_msi_irqs+0x2c/0x32  pci_alloc_irq_vectors_affinity+0xb8/0xe2 RISCV uses hierarchical interrupt domains and correctly does not implement the legacy fallback. The warning triggers from the legacy fallback stub. That warning is bogus as the PCI/MSI layer knows whether a PCI/MSI parent domain is associated with the device or not. There is a check for MSI-X, which has a legacy assumption. But that legacy fallback assumption is only valid when legacy support is enabled, but otherwise the check should simply return -ENOTSUPP. Loongarch tripped over the same problem and blindly enabled legacy support without implementing the legacy fallbacks. There are weak implementations which return an error, so the problem was papered over. Correct pci_msi_domain_supports() to evaluate the legacy mode and add the missing supported check into the MSI enable path to complete it.","status":"published","published":"2025-01-06T17:15:00Z","modified":"2026-10-08T12:52:54.560229581Z","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"},{"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:15.331356Z"},{"id":"MGASA-2025-0030","title":"Updated kernel, kmod-virtualbox, kmod-xtables-addons \u0026 dwarves packages fix security vulnerabilities","description":"Upstream kernel version 6.6.74 fixes bugs and vulnerabilities.\nThe kmod-virtualbox and kmod-xtables-addons packages have been\nupdated to work with this new kernel.\nFor information about the vulnerabilities see the links.\n","status":"published","published":"2025-01-31T20:54:03Z","modified":"2026-04-16T04:41:37.04829169Z","updated_at":"2026-11-02T15:49:42.684501Z"},{"id":"MGASA-2025-0032","title":"Updated kernel-linus packages fix security vulnerabilities","description":"Vanilla upstream kernel version 6.6.74 fixes bugs and vulnerabilities.\nFor information about the vulnerabilities see the links.\n","status":"published","published":"2025-01-31T20:54:03Z","modified":"2026-04-16T04:44:17.127966836Z","updated_at":"2026-11-02T15:49:42.684501Z"},{"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-7379-1","title":"linux, linux-aws, linux-azure, linux-gcp, linux-hwe-6.11, linux-oracle, 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  - x86 architecture;\n  - Block layer subsystem;\n  - Compute Acceleration Framework;\n  - ACPI drivers;\n  - Drivers core;\n  - Ublk userspace block driver;\n  - Virtio block driver;\n  - Bluetooth drivers;\n  - Buffer Sharing and Synchronization framework;\n  - DMA engine subsystem;\n  - EFI core;\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  - LED subsystem;\n  - Multiple devices driver;\n  - Media drivers;\n  - Microchip PCI driver;\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  - Power supply drivers;\n  - Voltage and Current Regulator drivers;\n  - SCSI subsystem;\n  - i.MX SoC drivers;\n  - SPI subsystem;\n  - UFS subsystem;\n  - USB Gadget drivers;\n  - TDX Guest driver;\n  - AFS file system;\n  - BTRFS file system;\n  - Ceph distributed file system;\n  - File systems infrastructure;\n  - F2FS file system;\n  - JFFS2 file system;\n  - JFS file system;\n  - Network file systems library;\n  - Network file system (NFS) server daemon;\n  - NILFS2 file system;\n  - File system notification infrastructure;\n  - Overlay file system;\n  - Diskquota system;\n  - SMB network file system;\n  - DRM display driver;\n  - BPF subsystem;\n  - VLANs driver;\n  - KASAN memory debugging framework;\n  - Memory management;\n  - StackDepot library;\n  - Bluetooth subsystem;\n  - LAPB network protocol;\n  - Netfilter;\n  - io_uring subsystem;\n  - Control group (cgroup);\n  - DMA mapping infrastructure;\n  - KCSAN framework;\n  - Scheduler infrastructure;\n  - Seccomp subsystem;\n  - Tracing infrastructure;\n  - Workqueue subsystem;\n  - KUnit library;\n  - CAN network layer;\n  - Networking core;\n  - DCCP (Datagram Congestion Control Protocol);\n  - HSR network protocol;\n  - IEEE802154.4 network protocol;\n  - IPv4 networking;\n  - IPv6 networking;\n  - MAC80211 subsystem;\n  - Multipath TCP;\n  - NET/ROM layer;\n  - Packet sockets;\n  - RDS protocol;\n  - Network traffic control;\n  - SCTP protocol;\n  - SMC sockets;\n  - TIPC protocol;\n  - Wireless networking;\n  - eXpress Data Path;\n  - SELinux security module;\n  - ALSA framework;\n  - Intel ASoC drivers;\n  - SOF drivers;\n(CVE-2024-57921, CVE-2024-56614, CVE-2024-56558, CVE-2024-56589,\nCVE-2024-56662, CVE-2024-56610, CVE-2024-56717, CVE-2024-57890,\nCVE-2024-55639, CVE-2024-56562, CVE-2025-21633, CVE-2024-56598,\nCVE-2024-47794, CVE-2024-41935, CVE-2024-57901, CVE-2024-56587,\nCVE-2024-56581, CVE-2024-56783, CVE-2024-57888, CVE-2024-57809,\nCVE-2024-57926, CVE-2025-21650, CVE-2024-56634, CVE-2025-21639,\nCVE-2025-21656, CVE-2024-56578, CVE-2025-21632, CVE-2024-56784,\nCVE-2025-21644, CVE-2024-56776, CVE-2024-56764, CVE-2024-56652,\nCVE-2024-56550, CVE-2024-56569, CVE-2024-57904, CVE-2024-49569,\nCVE-2024-56770, CVE-2024-56606, CVE-2024-57806, CVE-2024-56646,\nCVE-2024-57895, CVE-2024-57880, CVE-2024-56650, CVE-2024-56591,\nCVE-2024-56590, CVE-2024-56642, CVE-2024-56713, CVE-2025-21663,\nCVE-2024-57938, CVE-2024-56760, CVE-2024-56583, CVE-2025-21662,\nCVE-2024-56629, CVE-2024-47408, CVE-2024-57850, CVE-2024-56777,\nCVE-2024-56626, CVE-2024-56773, CVE-2024-56647, CVE-2025-21664,\nCVE-2024-56564, CVE-2024-56597, CVE-2024-56623, CVE-2024-57897,\nCVE-2024-56670, CVE-2024-56567, CVE-2024-57931, CVE-2024-56761,\nCVE-2024-57935, CVE-2024-53690, CVE-2025-21640, CVE-2024-56608,\nCVE-2024-57878, CVE-2025-21648, CVE-2024-57898, CVE-2024-57889,\nCVE-2024-56644, CVE-2024-56763, CVE-2024-57900, CVE-2024-56575,\nCVE-2024-56786, CVE-2025-21635, CVE-2024-56559, CVE-2024-56659,\nCVE-2024-56621, CVE-2024-57908, CVE-2024-52319, CVE-2024-43098,\nCVE-2024-57838, CVE-2024-56782, CVE-2025-21631, CVE-2024-36476,\nCVE-2025-21649, CVE-2024-56667, CVE-2024-49571, CVE-2024-55916,\nCVE-2024-57887, CVE-2024-56640, CVE-2024-57801, CVE-2024-57886,\nCVE-2024-56582, CVE-2024-56561, CVE-2024-56665, CVE-2024-57805,\nCVE-2024-51729, CVE-2024-57857, CVE-2024-57876, CVE-2024-57896,\nCVE-2024-57799, CVE-2024-57925, CVE-2024-57917, CVE-2024-56664,\nCVE-2024-57913, CVE-2025-21660, CVE-2024-56596, CVE-2024-56671,\nCVE-2024-56595, CVE-2024-56781, CVE-2024-57912, CVE-2024-56638,\nCVE-2024-56636, CVE-2024-56669, CVE-2024-57945, CVE-2024-56633,\nCVE-2024-56605, CVE-2024-57882, CVE-2025-21652, CVE-2024-53179,\nCVE-2024-56599, CVE-2024-57892, CVE-2025-21647, CVE-2024-57910,\nCVE-2024-57792, CVE-2024-56768, CVE-2024-56711, CVE-2024-47143,\nCVE-2024-56577, CVE-2024-56574, CVE-2024-56765, CVE-2024-58087,\nCVE-2024-53685, CVE-2024-56787, CVE-2024-56592, CVE-2024-56368,\nCVE-2024-56615, CVE-2024-56712, CVE-2024-56648, CVE-2024-57874,\nCVE-2024-56653, CVE-2024-56656, CVE-2024-56641, CVE-2024-56719,\nCVE-2025-21658, CVE-2024-56637, CVE-2024-56709, CVE-2024-57843,\nCVE-2024-56588, CVE-2024-57807, CVE-2024-57939, CVE-2024-56594,\nCVE-2024-55642, CVE-2024-57841, CVE-2024-50051, CVE-2024-56663,\nCVE-2024-56654, CVE-2024-56369, CVE-2024-57885, CVE-2024-56779,\nCVE-2024-56772, CVE-2024-56617, CVE-2024-56624, CVE-2024-56570,\nCVE-2024-56639, CVE-2025-21642, CVE-2024-56603, CVE-2024-56604,\nCVE-2024-57875, CVE-2025-21653, CVE-2025-21654, CVE-2024-56645,\nCVE-2024-56775, CVE-2024-52332, CVE-2024-48875, CVE-2024-41932,\nCVE-2024-57804, CVE-2025-21661, CVE-2024-57932, CVE-2024-53681,\nCVE-2024-56563, CVE-2024-56609, CVE-2024-57798, CVE-2025-21637,\nCVE-2024-57940, CVE-2024-56675, CVE-2024-56630, CVE-2024-56565,\nCVE-2024-54460, CVE-2024-56573, CVE-2025-21645, CVE-2024-56715,\nCVE-2024-56632, CVE-2024-56622, CVE-2024-56673, CVE-2024-48881,\nCVE-2024-56593, CVE-2024-56620, CVE-2024-48876, CVE-2025-21643,\nCVE-2024-56657, CVE-2024-57905, CVE-2024-57802, CVE-2024-56766,\nCVE-2024-57893, CVE-2024-57894, CVE-2024-57903, CVE-2024-57902,\nCVE-2024-57934, CVE-2024-57881, CVE-2024-56602, CVE-2024-47809,\nCVE-2024-56580, CVE-2024-57899, CVE-2024-56759, CVE-2024-56586,\nCVE-2024-57839, CVE-2024-49568, CVE-2024-56660, CVE-2024-53687,\nCVE-2024-57907, CVE-2024-56601, CVE-2024-56767, CVE-2024-57916,\nCVE-2024-56616, CVE-2024-56557, CVE-2024-56566, CVE-2024-56643,\nCVE-2025-21638, CVE-2024-57879, CVE-2025-21655, CVE-2024-56618,\nCVE-2024-56758, CVE-2024-56576, CVE-2024-57849, CVE-2024-56372,\nCVE-2024-45828, CVE-2024-57795, CVE-2024-56710, CVE-2024-56568,\nCVE-2024-56769, CVE-2025-21834, CVE-2024-56716, CVE-2024-56613,\nCVE-2024-56584, CVE-2024-56552, CVE-2025-21659, CVE-2024-57929,\nCVE-2024-57946, CVE-2025-21646, CVE-2024-56572, CVE-2024-55881,\nCVE-2025-21651, CVE-2024-57924, CVE-2025-21634, CVE-2024-53682,\nCVE-2024-57872, CVE-2024-53680, CVE-2024-54680, CVE-2024-57918,\nCVE-2024-56780, CVE-2025-21636, CVE-2024-57906, CVE-2024-55641,\nCVE-2024-54455, CVE-2024-57919, CVE-2024-54683, CVE-2024-54193,\nCVE-2024-56635, CVE-2024-57933, CVE-2024-56611, CVE-2024-56551,\nCVE-2024-57883, CVE-2024-57793, CVE-2024-56631, CVE-2024-56600,\nCVE-2024-56651, CVE-2024-56714, CVE-2024-39282, CVE-2024-56627,\nCVE-2024-56649, CVE-2024-56579, CVE-2024-57791, CVE-2024-56774,\nCVE-2024-57944, CVE-2024-57911, CVE-2024-48873, CVE-2024-57884,\nCVE-2025-21629, CVE-2024-56778, CVE-2024-56619, CVE-2024-54191,\nCVE-2024-56771, CVE-2024-47141, CVE-2024-56757, CVE-2024-56718,\nCVE-2024-56655, CVE-2024-56607, CVE-2024-56785, CVE-2024-56625)\n","status":"published","published":"2025-03-27T16:18:31Z","modified":"2026-10-29T20:02:56.402454662Z","updated_at":"2026-11-02T16:58:19.988474Z"},{"id":"USN-7381-1","title":"linux-lowlatency-hwe-6.11 vulnerabilities","description":"\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\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  - x86 architecture;\n  - Block layer subsystem;\n  - Compute Acceleration Framework;\n  - ACPI drivers;\n  - Drivers core;\n  - Ublk userspace block driver;\n  - Virtio block driver;\n  - Bluetooth drivers;\n  - Buffer Sharing and Synchronization framework;\n  - DMA engine subsystem;\n  - EFI core;\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  - LED subsystem;\n  - Multiple devices driver;\n  - Media drivers;\n  - Microchip PCI driver;\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  - Power supply drivers;\n  - Voltage and Current Regulator drivers;\n  - SCSI subsystem;\n  - i.MX SoC drivers;\n  - SPI subsystem;\n  - UFS subsystem;\n  - USB Gadget drivers;\n  - TDX Guest driver;\n  - AFS file system;\n  - BTRFS file system;\n  - Ceph distributed file system;\n  - File systems infrastructure;\n  - F2FS file system;\n  - JFFS2 file system;\n  - JFS file system;\n  - Network file systems library;\n  - Network file system (NFS) server daemon;\n  - NILFS2 file system;\n  - File system notification infrastructure;\n  - Overlay file system;\n  - Diskquota system;\n  - SMB network file system;\n  - DRM display driver;\n  - BPF subsystem;\n  - VLANs driver;\n  - KASAN memory debugging framework;\n  - Memory management;\n  - StackDepot library;\n  - Bluetooth subsystem;\n  - LAPB network protocol;\n  - Network namespace;\n  - Netfilter;\n  - io_uring subsystem;\n  - Control group (cgroup);\n  - DMA mapping infrastructure;\n  - KCSAN framework;\n  - Scheduler infrastructure;\n  - Seccomp subsystem;\n  - Tracing infrastructure;\n  - Workqueue subsystem;\n  - KUnit library;\n  - CAN network layer;\n  - Networking core;\n  - DCCP (Datagram Congestion Control Protocol);\n  - HSR network protocol;\n  - IEEE802154.4 network protocol;\n  - IPv4 networking;\n  - IPv6 networking;\n  - MAC80211 subsystem;\n  - Multipath TCP;\n  - NET/ROM layer;\n  - Packet sockets;\n  - RDS protocol;\n  - Network traffic control;\n  - SCTP protocol;\n  - SMC sockets;\n  - TIPC protocol;\n  - Wireless networking;\n  - eXpress Data Path;\n  - SELinux security module;\n  - ALSA framework;\n  - Intel ASoC drivers;\n  - SOF drivers;\n(CVE-2024-56712, CVE-2024-56761, CVE-2025-21661, CVE-2024-56565,\nCVE-2024-57804, CVE-2024-57887, CVE-2025-21642, CVE-2024-56779,\nCVE-2025-21656, CVE-2024-57890, CVE-2024-36476, CVE-2024-57843,\nCVE-2024-56594, CVE-2024-41932, CVE-2025-21653, CVE-2024-56567,\nCVE-2024-56665, CVE-2024-54191, CVE-2024-57893, CVE-2024-57932,\nCVE-2024-56656, CVE-2024-57945, CVE-2024-57931, CVE-2024-56599,\nCVE-2024-57897, CVE-2024-57903, CVE-2024-57918, CVE-2024-57795,\nCVE-2024-56662, CVE-2025-21639, CVE-2024-55881, CVE-2024-57889,\nCVE-2024-57884, CVE-2024-57934, CVE-2024-39282, CVE-2024-56718,\nCVE-2024-56644, CVE-2024-56760, CVE-2024-43098, CVE-2024-47143,\nCVE-2024-55642, CVE-2024-56634, CVE-2024-56564, CVE-2024-56768,\nCVE-2024-56649, CVE-2024-57919, CVE-2024-56620, CVE-2024-56625,\nCVE-2024-56655, CVE-2024-56772, CVE-2025-21637, CVE-2024-56617,\nCVE-2024-57879, CVE-2024-56715, CVE-2024-56550, CVE-2024-50051,\nCVE-2024-56673, CVE-2024-51729, CVE-2025-21664, CVE-2025-21649,\nCVE-2024-56605, CVE-2024-56622, CVE-2024-56591, CVE-2024-56782,\nCVE-2024-57801, CVE-2024-56664, CVE-2024-57916, CVE-2024-53680,\nCVE-2024-57926, CVE-2024-56637, CVE-2024-56769, CVE-2024-57924,\nCVE-2024-56648, CVE-2024-57872, CVE-2024-56593, CVE-2024-57913,\nCVE-2024-53682, CVE-2024-56670, CVE-2024-56767, CVE-2024-56778,\nCVE-2024-56777, CVE-2025-21658, CVE-2025-21646, CVE-2024-48875,\nCVE-2024-56758, CVE-2024-56604, CVE-2024-56787, CVE-2024-56581,\nCVE-2025-21635, CVE-2024-56641, CVE-2024-56608, CVE-2024-57885,\nCVE-2024-56716, CVE-2024-56671, CVE-2024-56559, CVE-2025-21633,\nCVE-2024-56372, CVE-2024-57888, CVE-2024-56623, CVE-2025-21638,\nCVE-2024-56600, CVE-2024-56647, CVE-2025-21659, CVE-2024-41935,\nCVE-2024-56624, CVE-2024-56574, CVE-2025-21648, CVE-2024-56621,\nCVE-2024-54460, CVE-2024-56659, CVE-2024-47141, CVE-2024-57805,\nCVE-2024-57792, CVE-2024-45828, CVE-2024-53681, CVE-2024-56568,\nCVE-2024-56764, CVE-2025-21650, CVE-2024-56601, CVE-2024-56663,\nCVE-2025-21660, CVE-2025-21629, CVE-2024-56595, CVE-2024-57917,\nCVE-2024-53685, CVE-2024-57882, CVE-2024-57894, CVE-2024-56651,\nCVE-2024-56657, CVE-2024-57876, CVE-2024-56717, CVE-2024-57935,\nCVE-2024-56667, CVE-2024-57910, CVE-2024-57793, CVE-2024-56631,\nCVE-2024-56638, CVE-2025-21640, CVE-2024-56710, CVE-2024-56583,\nCVE-2024-56557, CVE-2024-56658, CVE-2025-21632, CVE-2024-56645,\nCVE-2024-56646, CVE-2024-56640, CVE-2024-57944, CVE-2024-56598,\nCVE-2024-57857, CVE-2024-56709, CVE-2024-56654, CVE-2024-57809,\nCVE-2024-57895, CVE-2025-21834, CVE-2024-56763, CVE-2024-48881,\nCVE-2024-57841, CVE-2024-57878, CVE-2024-56774, CVE-2024-57791,\nCVE-2024-56575, CVE-2024-56619, CVE-2024-56570, CVE-2024-56616,\nCVE-2024-56569, CVE-2025-21636, CVE-2024-56572, CVE-2024-56552,\nCVE-2024-56596, CVE-2025-21654, CVE-2024-56573, CVE-2024-56784,\nCVE-2024-56626, CVE-2024-56642, CVE-2024-56643, CVE-2024-56719,\nCVE-2024-56632, CVE-2024-57839, CVE-2024-56578, CVE-2024-53690,\nCVE-2024-56609, CVE-2024-56562, CVE-2024-56589, CVE-2024-56781,\nCVE-2024-56672, CVE-2024-56775, CVE-2024-56713, CVE-2024-56580,\nCVE-2024-57874, CVE-2024-56369, CVE-2024-56711, CVE-2025-21651,\nCVE-2024-56584, CVE-2024-57904, CVE-2024-54680, CVE-2024-56577,\nCVE-2024-56558, CVE-2024-56780, CVE-2024-58087, CVE-2024-57892,\nCVE-2025-21644, CVE-2024-57911, CVE-2024-56579, CVE-2025-21663,\nCVE-2024-56618, CVE-2024-56766, CVE-2024-56653, CVE-2025-21655,\nCVE-2024-56669, CVE-2024-56759, CVE-2024-48876, CVE-2025-21631,\nCVE-2024-56765, CVE-2024-56770, CVE-2024-57838, CVE-2025-21634,\nCVE-2024-56650, CVE-2024-57939, CVE-2024-56606, CVE-2024-56610,\nCVE-2025-21662, CVE-2024-56785, CVE-2024-55916, CVE-2025-21643,\nCVE-2024-56586, CVE-2024-56582, CVE-2024-56614, CVE-2024-49571,\nCVE-2024-49569, CVE-2024-57798, CVE-2024-56633, CVE-2024-55641,\nCVE-2025-21647, CVE-2025-21652, CVE-2024-56757, CVE-2024-56597,\nCVE-2024-47794, CVE-2024-57902, CVE-2024-57925, CVE-2024-54683,\nCVE-2024-57938, CVE-2024-56615, CVE-2024-57906, CVE-2024-53687,\nCVE-2024-57899, CVE-2024-56783, CVE-2024-56786, CVE-2024-56635,\nCVE-2024-56551, CVE-2024-53179, CVE-2024-56588, CVE-2024-47408,\nCVE-2024-57849, CVE-2024-52319, CVE-2024-56576, CVE-2024-57905,\nCVE-2024-57946, CVE-2024-56607, CVE-2024-57806, CVE-2024-57933,\nCVE-2024-55639, CVE-2024-56561, CVE-2024-48873, CVE-2024-52332,\nCVE-2025-21645, CVE-2024-56602, CVE-2024-56590, CVE-2024-57799,\nCVE-2024-57929, CVE-2024-56639, CVE-2024-56613, CVE-2024-56675,\nCVE-2024-57912, CVE-2024-57883, CVE-2024-56636, CVE-2024-56592,\nCVE-2024-57802, CVE-2024-54455, CVE-2024-57908, CVE-2024-56603,\nCVE-2024-57875, CVE-2024-56773, CVE-2024-47809, CVE-2024-56630,\nCVE-2024-56587, CVE-2024-56627, CVE-2024-57921, CVE-2024-56660,\nCVE-2024-56771, CVE-2024-57886, CVE-2024-57896, CVE-2024-57807,\nCVE-2024-57907, CVE-2024-49568, CVE-2024-54193, CVE-2024-56652,\nCVE-2024-57940, CVE-2024-57898, CVE-2024-57901, CVE-2024-56714,\nCVE-2024-56566, CVE-2024-56563, CVE-2024-56368, CVE-2024-56611,\nCVE-2024-56776, CVE-2024-57850, CVE-2024-56629, CVE-2024-57881,\nCVE-2024-57880, CVE-2024-57900)\n","status":"published","published":"2025-03-27T17:07:06Z","modified":"2026-06-03T14:03:54.171720088Z","updated_at":"2026-11-02T16:58:19.988474Z"},{"id":"USN-7382-1","title":"linux-oem-6.11 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  - x86 architecture;\n  - Block layer subsystem;\n  - Compute Acceleration Framework;\n  - ACPI drivers;\n  - Drivers core;\n  - Ublk userspace block driver;\n  - Virtio block driver;\n  - Bluetooth drivers;\n  - Buffer Sharing and Synchronization framework;\n  - DMA engine subsystem;\n  - EFI core;\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  - LED subsystem;\n  - Multiple devices driver;\n  - Media drivers;\n  - Microchip PCI driver;\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  - Power supply drivers;\n  - Voltage and Current Regulator drivers;\n  - SCSI subsystem;\n  - i.MX SoC drivers;\n  - SPI subsystem;\n  - UFS subsystem;\n  - USB Gadget drivers;\n  - TDX Guest driver;\n  - AFS file system;\n  - BTRFS file system;\n  - Ceph distributed file system;\n  - File systems infrastructure;\n  - F2FS file system;\n  - JFFS2 file system;\n  - JFS file system;\n  - Network file systems library;\n  - Network file system (NFS) server daemon;\n  - NILFS2 file system;\n  - File system notification infrastructure;\n  - Overlay file system;\n  - Diskquota system;\n  - SMB network file system;\n  - DRM display driver;\n  - BPF subsystem;\n  - VLANs driver;\n  - KASAN memory debugging framework;\n  - Memory management;\n  - StackDepot library;\n  - Bluetooth subsystem;\n  - LAPB network protocol;\n  - Netfilter;\n  - io_uring subsystem;\n  - Control group (cgroup);\n  - DMA mapping infrastructure;\n  - KCSAN framework;\n  - Scheduler infrastructure;\n  - Seccomp subsystem;\n  - Tracing infrastructure;\n  - Workqueue subsystem;\n  - KUnit library;\n  - CAN network layer;\n  - Networking core;\n  - DCCP (Datagram Congestion Control Protocol);\n  - HSR network protocol;\n  - IEEE802154.4 network protocol;\n  - IPv4 networking;\n  - IPv6 networking;\n  - MAC80211 subsystem;\n  - Multipath TCP;\n  - NET/ROM layer;\n  - Packet sockets;\n  - RDS protocol;\n  - Network traffic control;\n  - SCTP protocol;\n  - SMC sockets;\n  - TIPC protocol;\n  - Wireless networking;\n  - eXpress Data Path;\n  - SELinux security module;\n  - ALSA framework;\n  - Intel ASoC drivers;\n  - SOF drivers;\n(CVE-2024-47794, CVE-2025-21653, CVE-2024-55642, CVE-2024-56580,\nCVE-2024-36476, CVE-2024-56623, CVE-2024-56773, CVE-2024-48873,\nCVE-2024-47141, CVE-2024-57910, CVE-2024-56759, CVE-2024-54460,\nCVE-2024-57839, CVE-2024-56625, CVE-2024-55916, CVE-2025-21664,\nCVE-2025-21652, CVE-2024-56624, CVE-2024-56574, CVE-2024-50051,\nCVE-2025-21655, CVE-2024-56578, CVE-2024-56782, CVE-2024-57939,\nCVE-2024-57935, CVE-2024-56647, CVE-2024-57905, CVE-2024-57921,\nCVE-2024-56660, CVE-2025-21650, CVE-2025-21631, CVE-2024-56642,\nCVE-2024-56552, CVE-2024-57934, CVE-2024-56621, CVE-2024-57881,\nCVE-2024-41932, CVE-2024-56770, CVE-2024-57897, CVE-2024-56785,\nCVE-2024-56664, CVE-2024-57945, CVE-2024-57938, CVE-2024-56636,\nCVE-2024-56572, CVE-2024-43098, CVE-2024-56760, CVE-2024-57916,\nCVE-2024-56714, CVE-2025-21660, CVE-2024-57906, CVE-2025-21638,\nCVE-2024-53687, CVE-2024-56652, CVE-2024-51729, CVE-2024-49571,\nCVE-2024-57883, CVE-2024-54191, CVE-2024-56712, CVE-2024-49568,\nCVE-2024-57932, CVE-2024-57893, CVE-2024-56645, CVE-2024-56719,\nCVE-2024-56641, CVE-2024-57802, CVE-2024-56775, CVE-2024-56627,\nCVE-2024-56638, CVE-2024-57929, CVE-2024-56615, CVE-2024-56566,\nCVE-2024-56620, CVE-2024-56577, CVE-2025-21656, CVE-2024-57887,\nCVE-2024-52319, CVE-2024-56657, CVE-2024-57872, CVE-2024-56607,\nCVE-2024-56562, CVE-2025-21645, CVE-2025-21634, CVE-2024-56567,\nCVE-2024-56637, CVE-2025-21646, CVE-2024-57918, CVE-2024-56646,\nCVE-2024-57849, CVE-2025-21633, CVE-2025-21639, CVE-2024-56644,\nCVE-2024-56618, CVE-2024-56564, CVE-2024-56369, CVE-2024-56766,\nCVE-2024-56635, CVE-2024-57907, CVE-2024-56778, CVE-2024-57880,\nCVE-2024-57885, CVE-2024-56591, CVE-2024-56780, CVE-2024-57913,\nCVE-2024-54680, CVE-2025-21632, CVE-2024-54683, CVE-2025-21654,\nCVE-2024-58087, CVE-2024-56772, CVE-2024-56758, CVE-2024-57795,\nCVE-2025-21644, CVE-2024-56586, CVE-2024-56663, CVE-2024-56558,\nCVE-2024-57882, CVE-2024-56651, CVE-2024-56783, CVE-2024-53681,\nCVE-2024-57911, CVE-2024-57879, CVE-2024-56649, CVE-2024-56563,\nCVE-2024-56639, CVE-2024-56605, CVE-2024-57888, CVE-2024-56640,\nCVE-2024-57841, CVE-2024-56656, CVE-2024-48875, CVE-2024-48876,\nCVE-2024-57919, CVE-2024-57940, CVE-2024-56630, CVE-2024-53685,\nCVE-2024-56604, CVE-2024-47809, CVE-2024-57889, CVE-2024-56619,\nCVE-2024-57806, CVE-2024-56583, CVE-2024-56715, CVE-2025-21640,\nCVE-2025-21662, CVE-2024-56662, CVE-2024-55639, CVE-2024-56711,\nCVE-2024-56372, CVE-2024-54455, CVE-2024-56771, CVE-2024-56368,\nCVE-2024-57892, CVE-2024-57843, CVE-2025-21636, CVE-2024-56650,\nCVE-2024-56613, CVE-2024-56716, CVE-2024-57793, CVE-2024-56634,\nCVE-2024-56595, CVE-2024-57878, CVE-2024-56598, CVE-2024-39282,\nCVE-2024-57908, CVE-2024-57917, CVE-2024-56763, CVE-2024-56629,\nCVE-2024-56710, CVE-2024-56671, CVE-2024-56667, CVE-2024-57924,\nCVE-2024-57926, CVE-2025-21658, CVE-2024-56594, CVE-2024-56584,\nCVE-2024-53179, CVE-2024-56587, CVE-2024-57946, CVE-2024-56717,\nCVE-2025-21635, CVE-2024-56779, CVE-2024-57944, CVE-2024-56767,\nCVE-2024-56781, CVE-2024-56765, CVE-2024-56609, CVE-2024-54193,\nCVE-2024-57804, CVE-2024-56599, CVE-2024-56602, CVE-2024-57901,\nCVE-2024-53680, CVE-2024-57801, CVE-2024-57912, CVE-2024-56606,\nCVE-2024-56579, CVE-2024-56588, CVE-2024-57895, CVE-2024-56601,\nCVE-2024-55641, CVE-2024-56559, CVE-2024-56557, CVE-2025-21661,\nCVE-2024-57799, CVE-2024-57850, CVE-2024-57876, CVE-2024-47408,\nCVE-2024-57899, CVE-2024-56597, CVE-2024-57890, CVE-2024-56670,\nCVE-2024-56603, CVE-2024-56654, CVE-2025-21834, CVE-2024-56590,\nCVE-2024-49569, CVE-2024-56616, CVE-2024-56659, CVE-2024-56596,\nCVE-2025-21642, CVE-2025-21663, CVE-2025-21648, CVE-2024-56614,\nCVE-2024-56673, CVE-2024-56787, CVE-2024-56713, CVE-2024-56573,\nCVE-2024-56589, CVE-2024-56764, CVE-2024-56655, CVE-2024-56617,\nCVE-2024-56669, CVE-2024-56576, CVE-2024-57792, CVE-2024-57904,\nCVE-2024-52332, CVE-2024-57900, CVE-2024-57933, CVE-2024-55881,\nCVE-2024-56626, CVE-2024-57894, CVE-2024-56582, CVE-2024-57838,\nCVE-2025-21629, CVE-2025-21659, CVE-2024-57809, CVE-2024-47143,\nCVE-2024-57925, CVE-2024-41935, CVE-2025-21649, CVE-2024-57884,\nCVE-2024-57875, CVE-2025-21647, CVE-2024-56581, CVE-2024-57886,\nCVE-2024-57896, CVE-2025-21651, CVE-2024-56611, CVE-2024-56575,\nCVE-2024-57807, CVE-2024-56561, CVE-2024-53690, CVE-2024-56761,\nCVE-2024-57902, CVE-2024-56600, CVE-2024-56593, CVE-2024-57805,\nCVE-2024-56568, CVE-2024-56632, CVE-2024-56622, CVE-2025-21637,\nCVE-2024-45828, CVE-2024-56709, CVE-2024-56631, CVE-2025-21643,\nCVE-2024-56786, CVE-2024-56565, CVE-2024-57903, CVE-2024-56592,\nCVE-2024-56569, CVE-2024-56718, CVE-2024-57791, CVE-2024-56665,\nCVE-2024-56774, CVE-2024-56608, CVE-2024-56643, CVE-2024-57931,\nCVE-2024-57857, CVE-2024-56777, CVE-2024-53682, CVE-2024-56648,\nCVE-2024-56769, CVE-2024-48881, CVE-2024-56776, CVE-2024-57798,\nCVE-2024-57874, CVE-2024-56633, CVE-2024-56768, CVE-2024-56653,\nCVE-2024-56784, CVE-2024-56550, CVE-2024-56610, CVE-2024-56570,\nCVE-2024-56675, CVE-2024-57898, CVE-2024-56551)\n","status":"published","published":"2025-03-27T17:21:41Z","modified":"2026-10-29T20:02:40.007032312Z","updated_at":"2026-11-02T16:58:19.988474Z"},{"id":"USN-7513-1","title":"linux, linux-aws, linux-aws-6.8, linux-ibm, linux-lowlatency, linux-lowlatency-hwe-6.8, linux-oracle 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  - RISC-V architecture;\n  - x86 architecture;\n  - Block layer subsystem;\n  - Compute Acceleration Framework;\n  - ACPI drivers;\n  - Drivers core;\n  - Ublk userspace block driver;\n  - Virtio block driver;\n  - DMA engine subsystem;\n  - GPU drivers;\n  - Microsoft Hyper-V drivers;\n  - Hardware monitoring drivers;\n  - IIO ADC drivers;\n  - IIO subsystem;\n  - InfiniBand drivers;\n  - Multiple devices driver;\n  - Media drivers;\n  - Microchip PCI driver;\n  - Network drivers;\n  - Mellanox network drivers;\n  - STMicroelectronics network drivers;\n  - PCI subsystem;\n  - Pin controllers subsystem;\n  - x86 platform drivers;\n  - Power supply drivers;\n  - SCSI subsystem;\n  - USB Gadget drivers;\n  - TDX Guest driver;\n  - AFS file system;\n  - BTRFS file system;\n  - Ceph distributed file system;\n  - EROFS file system;\n  - File systems infrastructure;\n  - Network file systems library;\n  - NILFS2 file system;\n  - Overlay file system;\n  - SMB network file system;\n  - VLANs driver;\n  - Memory management;\n  - LAPB network protocol;\n  - io_uring subsystem;\n  - BPF subsystem;\n  - Control group (cgroup);\n  - Tracing infrastructure;\n  - Workqueue subsystem;\n  - Bluetooth subsystem;\n  - Networking core;\n  - IPv4 networking;\n  - IPv6 networking;\n  - MAC80211 subsystem;\n  - Multipath TCP;\n  - Netfilter;\n  - NET/ROM layer;\n  - Packet sockets;\n  - RDS protocol;\n  - Network traffic control;\n  - SCTP protocol;\n  - SMC sockets;\n  - Wireless networking;\n  - SELinux security module;\n  - ALSA framework;\n  - SOF drivers;\n(CVE-2024-56372, CVE-2025-21639, CVE-2024-57897, CVE-2024-56770,\nCVE-2024-57898, CVE-2025-21655, CVE-2024-56667, CVE-2024-41013,\nCVE-2024-57888, CVE-2025-21658, CVE-2024-57911, CVE-2024-56654,\nCVE-2024-57904, CVE-2024-56664, CVE-2024-57806, CVE-2024-56758,\nCVE-2024-57912, CVE-2025-21649, CVE-2024-56369, CVE-2025-21656,\nCVE-2025-21643, CVE-2024-57884, CVE-2025-21640, CVE-2024-56769,\nCVE-2024-57939, CVE-2025-21635, CVE-2024-57902, CVE-2024-36476,\nCVE-2025-21646, CVE-2024-57887, CVE-2024-57882, CVE-2024-57792,\nCVE-2024-56759, CVE-2024-57901, CVE-2024-56764, CVE-2025-21654,\nCVE-2024-57899, CVE-2025-21664, CVE-2024-56715, CVE-2024-56760,\nCVE-2024-57926, CVE-2024-57938, CVE-2025-21637, CVE-2024-55881,\nCVE-2024-57916, CVE-2024-57908, CVE-2024-57910, CVE-2024-57892,\nCVE-2024-57890, CVE-2024-56662, CVE-2024-57793, CVE-2024-47408,\nCVE-2024-49568, CVE-2024-57946, CVE-2024-53690, CVE-2024-56716,\nCVE-2024-57801, CVE-2024-56670, CVE-2024-56709, CVE-2024-57885,\nCVE-2024-57791, CVE-2024-38608, CVE-2024-56763, CVE-2024-57906,\nCVE-2024-47736, CVE-2024-56761, CVE-2024-56659, CVE-2025-21636,\nCVE-2024-57913, CVE-2024-56710, CVE-2025-21660, CVE-2024-57945,\nCVE-2024-39282, CVE-2024-53687, CVE-2024-57907, CVE-2024-53179,\nCVE-2025-21659, CVE-2024-57805, CVE-2024-57889, CVE-2024-57940,\nCVE-2025-21645, CVE-2024-56660, CVE-2024-56718, CVE-2024-57802,\nCVE-2024-56767, CVE-2024-56717, CVE-2024-58087, CVE-2025-21647,\nCVE-2025-21650, CVE-2024-57895, CVE-2025-21632, CVE-2024-54193,\nCVE-2024-57893, CVE-2025-21652, CVE-2025-21634, CVE-2024-56652,\nCVE-2024-57929, CVE-2024-57804, CVE-2024-57925, CVE-2024-57932,\nCVE-2024-54683, CVE-2025-21663, CVE-2024-56665, CVE-2024-54455,\nCVE-2025-21642, CVE-2024-57931, CVE-2025-21971, CVE-2024-56656,\nCVE-2025-21651, CVE-2024-49571, CVE-2025-21631, CVE-2024-56675,\nCVE-2024-53125, CVE-2025-21938, CVE-2024-57879, CVE-2024-56657,\nCVE-2024-57807, CVE-2024-57841, CVE-2024-57903, CVE-2024-53685,\nCVE-2024-57896, CVE-2024-57900, CVE-2024-57883, CVE-2024-58237,\nCVE-2025-21638, CVE-2024-55639, CVE-2025-21653, CVE-2025-21648,\nCVE-2024-54460, CVE-2024-57933, CVE-2024-55916, CVE-2024-57917,\nCVE-2025-21662)\n","status":"published","published":"2025-05-16T16:23:28Z","modified":"2026-10-30T21:54:59.435739623Z","updated_at":"2026-11-02T16:58:19.988474Z"},{"id":"USN-7513-2","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  - RISC-V architecture;\n  - x86 architecture;\n  - Block layer subsystem;\n  - Compute Acceleration Framework;\n  - ACPI drivers;\n  - Drivers core;\n  - Ublk userspace block driver;\n  - Virtio block driver;\n  - DMA engine subsystem;\n  - GPU drivers;\n  - Microsoft Hyper-V drivers;\n  - Hardware monitoring drivers;\n  - IIO ADC drivers;\n  - IIO subsystem;\n  - InfiniBand drivers;\n  - Multiple devices driver;\n  - Media drivers;\n  - Microchip PCI driver;\n  - Network drivers;\n  - Mellanox network drivers;\n  - STMicroelectronics network drivers;\n  - PCI subsystem;\n  - Pin controllers subsystem;\n  - x86 platform drivers;\n  - Power supply drivers;\n  - SCSI subsystem;\n  - USB Gadget drivers;\n  - TDX Guest driver;\n  - AFS file system;\n  - BTRFS file system;\n  - Ceph distributed file system;\n  - EROFS file system;\n  - File systems infrastructure;\n  - Network file systems library;\n  - NILFS2 file system;\n  - Overlay file system;\n  - SMB network file system;\n  - VLANs driver;\n  - Memory management;\n  - LAPB network protocol;\n  - io_uring subsystem;\n  - BPF subsystem;\n  - Control group (cgroup);\n  - Tracing infrastructure;\n  - Workqueue subsystem;\n  - Bluetooth subsystem;\n  - Networking core;\n  - IPv4 networking;\n  - IPv6 networking;\n  - MAC80211 subsystem;\n  - Multipath TCP;\n  - Netfilter;\n  - NET/ROM layer;\n  - Packet sockets;\n  - RDS protocol;\n  - Network traffic control;\n  - SCTP protocol;\n  - SMC sockets;\n  - Wireless networking;\n  - SELinux security module;\n  - ALSA framework;\n  - SOF drivers;\n(CVE-2024-56372, CVE-2025-21639, CVE-2024-57897, CVE-2024-56770,\nCVE-2024-57898, CVE-2025-21655, CVE-2024-56667, CVE-2024-41013,\nCVE-2024-57888, CVE-2025-21658, CVE-2024-57911, CVE-2024-56654,\nCVE-2024-57904, CVE-2024-56664, CVE-2024-57806, CVE-2024-56758,\nCVE-2024-57912, CVE-2025-21649, CVE-2024-56369, CVE-2025-21656,\nCVE-2025-21643, CVE-2024-57884, CVE-2025-21640, CVE-2024-56769,\nCVE-2024-57939, CVE-2025-21635, CVE-2024-57902, CVE-2024-36476,\nCVE-2025-21646, CVE-2024-57887, CVE-2024-57882, CVE-2024-57792,\nCVE-2024-56759, CVE-2024-57901, CVE-2024-56764, CVE-2025-21654,\nCVE-2024-57899, CVE-2025-21664, CVE-2024-56715, CVE-2024-56760,\nCVE-2024-57926, CVE-2024-57938, CVE-2025-21637, CVE-2024-55881,\nCVE-2024-57916, CVE-2024-57908, CVE-2024-57910, CVE-2024-57892,\nCVE-2024-57890, CVE-2024-56662, CVE-2024-57793, CVE-2024-47408,\nCVE-2024-49568, CVE-2024-57946, CVE-2024-53690, CVE-2024-56716,\nCVE-2024-57801, CVE-2024-56670, CVE-2024-56709, CVE-2024-57885,\nCVE-2024-57791, CVE-2024-38608, CVE-2024-56763, CVE-2024-57906,\nCVE-2024-47736, CVE-2024-56761, CVE-2024-56659, CVE-2025-21636,\nCVE-2024-57913, CVE-2024-56710, CVE-2025-21660, CVE-2024-57945,\nCVE-2024-39282, CVE-2024-53687, CVE-2024-57907, CVE-2024-53179,\nCVE-2025-21659, CVE-2024-57805, CVE-2024-57889, CVE-2024-57940,\nCVE-2025-21645, CVE-2024-56660, CVE-2024-56718, CVE-2024-57802,\nCVE-2024-56767, CVE-2024-56717, CVE-2024-58087, CVE-2025-21647,\nCVE-2025-21650, CVE-2024-57895, CVE-2025-21632, CVE-2024-54193,\nCVE-2024-57893, CVE-2025-21652, CVE-2025-21634, CVE-2024-56652,\nCVE-2024-57929, CVE-2024-57804, CVE-2024-57925, CVE-2024-57932,\nCVE-2024-54683, CVE-2025-21663, CVE-2024-56665, CVE-2024-54455,\nCVE-2025-21642, CVE-2024-57931, CVE-2025-21971, CVE-2024-56656,\nCVE-2025-21651, CVE-2024-49571, CVE-2025-21631, CVE-2024-56675,\nCVE-2024-53125, CVE-2025-21938, CVE-2024-57879, CVE-2024-56657,\nCVE-2024-57807, CVE-2024-57841, CVE-2024-57903, CVE-2024-53685,\nCVE-2024-57896, CVE-2024-57900, CVE-2024-57883, CVE-2024-58237,\nCVE-2025-21638, CVE-2024-55639, CVE-2025-21653, CVE-2025-21648,\nCVE-2024-54460, CVE-2024-57933, CVE-2024-55916, CVE-2024-57917,\nCVE-2025-21662)\n","status":"published","published":"2025-05-16T16:30:47Z","modified":"2026-10-30T21:54:49.280890094Z","updated_at":"2026-11-02T16:58:19.988474Z"},{"id":"USN-7513-3","title":"linux-azure, linux-azure-6.8, linux-oem-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  - RISC-V architecture;\n  - x86 architecture;\n  - Block layer subsystem;\n  - Compute Acceleration Framework;\n  - ACPI drivers;\n  - Drivers core;\n  - Ublk userspace block driver;\n  - Virtio block driver;\n  - DMA engine subsystem;\n  - GPU drivers;\n  - Microsoft Hyper-V drivers;\n  - Hardware monitoring drivers;\n  - IIO ADC drivers;\n  - IIO subsystem;\n  - InfiniBand drivers;\n  - Multiple devices driver;\n  - Media drivers;\n  - Microchip PCI driver;\n  - Network drivers;\n  - Mellanox network drivers;\n  - STMicroelectronics network drivers;\n  - PCI subsystem;\n  - Pin controllers subsystem;\n  - x86 platform drivers;\n  - Power supply drivers;\n  - SCSI subsystem;\n  - USB Gadget drivers;\n  - TDX Guest driver;\n  - AFS file system;\n  - BTRFS file system;\n  - Ceph distributed file system;\n  - EROFS file system;\n  - File systems infrastructure;\n  - Network file systems library;\n  - NILFS2 file system;\n  - Overlay file system;\n  - SMB network file system;\n  - VLANs driver;\n  - Memory management;\n  - LAPB network protocol;\n  - io_uring subsystem;\n  - BPF subsystem;\n  - Control group (cgroup);\n  - Tracing infrastructure;\n  - Workqueue subsystem;\n  - Bluetooth subsystem;\n  - Networking core;\n  - IPv4 networking;\n  - IPv6 networking;\n  - MAC80211 subsystem;\n  - Multipath TCP;\n  - Netfilter;\n  - NET/ROM layer;\n  - Packet sockets;\n  - RDS protocol;\n  - Network traffic control;\n  - SCTP protocol;\n  - SMC sockets;\n  - Wireless networking;\n  - SELinux security module;\n  - ALSA framework;\n  - SOF drivers;\n(CVE-2025-21648, CVE-2025-21645, CVE-2024-56767, CVE-2025-21664,\nCVE-2025-21636, CVE-2024-57898, CVE-2024-56667, CVE-2024-57912,\nCVE-2024-47408, CVE-2024-56761, CVE-2024-56665, CVE-2024-57887,\nCVE-2024-54683, CVE-2024-56662, CVE-2024-57910, CVE-2024-38608,\nCVE-2024-56710, CVE-2025-21656, CVE-2024-57885, CVE-2024-53125,\nCVE-2024-56675, CVE-2024-57895, CVE-2024-56660, CVE-2025-21638,\nCVE-2024-57932, CVE-2024-57807, CVE-2024-56759, CVE-2024-57883,\nCVE-2025-21643, CVE-2024-54193, CVE-2024-57879, CVE-2024-54460,\nCVE-2024-41013, CVE-2024-56654, CVE-2024-55916, CVE-2024-57897,\nCVE-2024-58087, CVE-2024-57904, CVE-2024-57893, CVE-2025-21652,\nCVE-2024-57925, CVE-2024-47736, CVE-2024-57802, CVE-2024-49571,\nCVE-2024-57916, CVE-2024-57801, CVE-2025-21647, CVE-2024-56763,\nCVE-2024-57903, CVE-2024-57899, CVE-2024-57908, CVE-2024-57900,\nCVE-2024-57911, CVE-2024-57902, CVE-2024-57938, CVE-2024-56760,\nCVE-2025-21642, CVE-2025-21971, CVE-2024-57933, CVE-2024-57917,\nCVE-2024-53179, CVE-2024-57896, CVE-2024-57906, CVE-2024-56716,\nCVE-2024-39282, CVE-2024-57806, CVE-2025-21938, CVE-2024-55881,\nCVE-2024-57931, CVE-2024-56717, CVE-2024-56369, CVE-2025-21640,\nCVE-2024-57888, CVE-2024-57804, CVE-2024-57907, CVE-2024-53687,\nCVE-2024-57940, CVE-2024-57929, CVE-2025-21637, CVE-2024-57805,\nCVE-2024-56372, CVE-2025-21646, CVE-2024-57913, CVE-2024-57901,\nCVE-2024-57889, CVE-2024-56770, CVE-2024-57945, CVE-2024-56659,\nCVE-2024-57946, CVE-2024-57890, CVE-2024-36476, CVE-2024-57882,\nCVE-2024-53685, CVE-2024-57791, CVE-2024-55639, CVE-2024-56718,\nCVE-2024-57792, CVE-2025-21662, CVE-2024-57793, CVE-2024-54455,\nCVE-2025-21632, CVE-2024-56715, CVE-2024-56652, CVE-2024-57939,\nCVE-2024-56657, CVE-2025-21658, CVE-2025-21655, CVE-2025-21635,\nCVE-2024-56656, CVE-2025-21660, CVE-2025-21634, CVE-2025-21631,\nCVE-2024-57892, CVE-2024-57884, CVE-2024-58237, CVE-2025-21659,\nCVE-2024-57926, CVE-2024-53690, CVE-2025-21654, CVE-2024-57841,\nCVE-2025-21639, CVE-2025-21663, CVE-2024-56670, CVE-2024-56758,\nCVE-2024-56764, CVE-2024-56709, CVE-2024-49568, CVE-2024-56769,\nCVE-2025-21653, CVE-2025-21651, CVE-2025-21650, CVE-2024-56664,\nCVE-2025-21649)\n","status":"published","published":"2025-05-20T14:20:56Z","modified":"2026-10-30T21:54:43.047326931Z","updated_at":"2026-11-02T16:58:19.988474Z"},{"id":"USN-7513-4","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  - RISC-V architecture;\n  - x86 architecture;\n  - Block layer subsystem;\n  - Compute Acceleration Framework;\n  - ACPI drivers;\n  - Drivers core;\n  - Ublk userspace block driver;\n  - Virtio block driver;\n  - DMA engine subsystem;\n  - GPU drivers;\n  - Microsoft Hyper-V drivers;\n  - Hardware monitoring drivers;\n  - IIO ADC drivers;\n  - IIO subsystem;\n  - InfiniBand drivers;\n  - Multiple devices driver;\n  - Media drivers;\n  - Microchip PCI driver;\n  - Network drivers;\n  - Mellanox network drivers;\n  - STMicroelectronics network drivers;\n  - PCI subsystem;\n  - Pin controllers subsystem;\n  - x86 platform drivers;\n  - Power supply drivers;\n  - SCSI subsystem;\n  - USB Gadget drivers;\n  - TDX Guest driver;\n  - AFS file system;\n  - BTRFS file system;\n  - Ceph distributed file system;\n  - EROFS file system;\n  - File systems infrastructure;\n  - Network file systems library;\n  - NILFS2 file system;\n  - Overlay file system;\n  - SMB network file system;\n  - VLANs driver;\n  - Memory management;\n  - LAPB network protocol;\n  - io_uring subsystem;\n  - BPF subsystem;\n  - Control group (cgroup);\n  - Tracing infrastructure;\n  - Workqueue subsystem;\n  - Bluetooth subsystem;\n  - Networking core;\n  - IPv4 networking;\n  - IPv6 networking;\n  - MAC80211 subsystem;\n  - Multipath TCP;\n  - Netfilter;\n  - NET/ROM layer;\n  - Packet sockets;\n  - RDS protocol;\n  - Network traffic control;\n  - SCTP protocol;\n  - SMC sockets;\n  - Wireless networking;\n  - SELinux security module;\n  - ALSA framework;\n  - SOF drivers;\n(CVE-2024-57895, CVE-2024-57801, CVE-2025-21653, CVE-2025-21664,\nCVE-2024-57911, CVE-2024-57890, CVE-2024-56372, CVE-2024-57931,\nCVE-2024-57841, CVE-2024-56758, CVE-2024-57946, CVE-2024-54460,\nCVE-2024-55639, CVE-2025-21636, CVE-2025-21656, CVE-2024-57917,\nCVE-2024-53685, CVE-2024-55881, CVE-2024-57910, CVE-2024-56369,\nCVE-2024-57929, CVE-2024-57940, CVE-2024-54455, CVE-2025-21631,\nCVE-2024-56656, CVE-2025-21643, CVE-2024-57807, CVE-2024-47736,\nCVE-2024-56670, CVE-2025-21660, CVE-2024-56667, CVE-2024-41013,\nCVE-2024-56710, CVE-2025-21659, CVE-2024-57792, CVE-2024-57893,\nCVE-2024-57913, CVE-2024-57897, CVE-2024-57907, CVE-2024-57916,\nCVE-2025-21647, CVE-2024-56665, CVE-2025-21649, CVE-2024-57938,\nCVE-2024-56709, CVE-2024-57945, CVE-2025-21654, CVE-2024-56657,\nCVE-2024-49571, CVE-2024-54683, CVE-2024-56664, CVE-2024-58087,\nCVE-2024-54193, CVE-2024-57802, CVE-2025-21637, CVE-2024-56761,\nCVE-2024-57892, CVE-2024-56675, CVE-2025-21645, CVE-2024-57908,\nCVE-2024-58237, CVE-2024-57887, CVE-2024-53687, CVE-2025-21650,\nCVE-2024-57888, CVE-2024-57902, CVE-2024-57906, CVE-2024-56764,\nCVE-2024-57882, CVE-2024-56652, CVE-2025-21652, CVE-2025-21662,\nCVE-2024-57879, CVE-2024-56662, CVE-2024-56660, CVE-2025-21632,\nCVE-2024-47408, CVE-2025-21642, CVE-2025-21655, CVE-2025-21640,\nCVE-2025-21663, CVE-2024-57933, CVE-2024-57899, CVE-2024-57884,\nCVE-2024-56654, CVE-2024-57806, CVE-2024-57901, CVE-2024-57926,\nCVE-2024-39282, CVE-2024-56770, CVE-2024-57889, CVE-2024-56769,\nCVE-2024-53690, CVE-2024-57904, CVE-2025-21971, CVE-2024-57885,\nCVE-2024-56718, CVE-2024-56767, CVE-2024-38608, CVE-2024-56760,\nCVE-2024-56763, CVE-2024-57912, CVE-2024-36476, CVE-2024-57793,\nCVE-2025-21638, CVE-2024-56716, CVE-2024-57804, CVE-2024-57932,\nCVE-2024-57900, CVE-2025-21651, CVE-2024-57925, CVE-2024-53125,\nCVE-2024-56717, CVE-2025-21938, CVE-2025-21639, CVE-2024-57883,\nCVE-2024-56715, CVE-2024-57805, CVE-2024-55916, CVE-2024-53179,\nCVE-2024-56759, CVE-2024-57939, CVE-2025-21646, CVE-2024-57898,\nCVE-2024-57791, CVE-2025-21634, CVE-2025-21635, CVE-2024-56659,\nCVE-2024-57903, CVE-2025-21648, CVE-2024-57896, CVE-2024-49568,\nCVE-2025-21658)\n","status":"published","published":"2025-05-28T08:07:10Z","modified":"2026-10-30T21:54:38.693985869Z","updated_at":"2026-11-02T16:58:19.988474Z"},{"id":"USN-7513-5","title":"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  - RISC-V architecture;\n  - x86 architecture;\n  - Block layer subsystem;\n  - Compute Acceleration Framework;\n  - ACPI drivers;\n  - Drivers core;\n  - Ublk userspace block driver;\n  - Virtio block driver;\n  - DMA engine subsystem;\n  - GPU drivers;\n  - Microsoft Hyper-V drivers;\n  - Hardware monitoring drivers;\n  - IIO ADC drivers;\n  - IIO subsystem;\n  - InfiniBand drivers;\n  - Multiple devices driver;\n  - Media drivers;\n  - Microchip PCI driver;\n  - Network drivers;\n  - Mellanox network drivers;\n  - STMicroelectronics network drivers;\n  - PCI subsystem;\n  - Pin controllers subsystem;\n  - x86 platform drivers;\n  - Power supply drivers;\n  - SCSI subsystem;\n  - USB Gadget drivers;\n  - TDX Guest driver;\n  - AFS file system;\n  - BTRFS file system;\n  - Ceph distributed file system;\n  - EROFS file system;\n  - File systems infrastructure;\n  - Network file systems library;\n  - NILFS2 file system;\n  - Overlay file system;\n  - SMB network file system;\n  - VLANs driver;\n  - Memory management;\n  - LAPB network protocol;\n  - io_uring subsystem;\n  - BPF subsystem;\n  - Control group (cgroup);\n  - Tracing infrastructure;\n  - Workqueue subsystem;\n  - Bluetooth subsystem;\n  - Networking core;\n  - IPv4 networking;\n  - IPv6 networking;\n  - MAC80211 subsystem;\n  - Multipath TCP;\n  - Netfilter;\n  - NET/ROM layer;\n  - Packet sockets;\n  - RDS protocol;\n  - Network traffic control;\n  - SCTP protocol;\n  - SMC sockets;\n  - Wireless networking;\n  - SELinux security module;\n  - ALSA framework;\n  - SOF drivers;\n(CVE-2024-57913, CVE-2024-47408, CVE-2024-57884, CVE-2024-57801,\nCVE-2025-21664, CVE-2024-57912, CVE-2025-21634, CVE-2024-53125,\nCVE-2024-57900, CVE-2024-57911, CVE-2024-56716, CVE-2024-56715,\nCVE-2024-57892, CVE-2025-21640, CVE-2025-21646, CVE-2024-57889,\nCVE-2024-56758, CVE-2024-56767, CVE-2024-57926, CVE-2024-56670,\nCVE-2024-57940, CVE-2024-56717, CVE-2024-56759, CVE-2024-57887,\nCVE-2025-21654, CVE-2024-57938, CVE-2024-57841, CVE-2024-39282,\nCVE-2024-56761, CVE-2025-21649, CVE-2024-56652, CVE-2024-56665,\nCVE-2024-57896, CVE-2024-56667, CVE-2024-57902, CVE-2024-54455,\nCVE-2025-21656, CVE-2024-56709, CVE-2025-21635, CVE-2024-57792,\nCVE-2025-21642, CVE-2025-21660, CVE-2024-53690, CVE-2024-57904,\nCVE-2024-53685, CVE-2025-21938, CVE-2024-55881, CVE-2024-57793,\nCVE-2024-56659, CVE-2025-21632, CVE-2024-56656, CVE-2025-21636,\nCVE-2024-47736, CVE-2024-57899, CVE-2024-57916, CVE-2024-56664,\nCVE-2025-21971, CVE-2025-21659, CVE-2024-57910, CVE-2024-57802,\nCVE-2024-57806, CVE-2025-21655, CVE-2024-54193, CVE-2024-57885,\nCVE-2025-21658, CVE-2024-57945, CVE-2025-21650, CVE-2024-58237,\nCVE-2024-57804, CVE-2024-57888, CVE-2025-21637, CVE-2024-57882,\nCVE-2024-57883, CVE-2024-56675, CVE-2025-21663, CVE-2024-49568,\nCVE-2024-58087, CVE-2024-56764, CVE-2024-57903, CVE-2024-57917,\nCVE-2024-57893, CVE-2025-21648, CVE-2025-21631, CVE-2024-57890,\nCVE-2024-56718, CVE-2025-21638, CVE-2024-56372, CVE-2024-49571,\nCVE-2025-21662, CVE-2024-56770, CVE-2024-57807, CVE-2024-57925,\nCVE-2024-57898, CVE-2025-21653, CVE-2024-57895, CVE-2024-56657,\nCVE-2024-54683, CVE-2024-56769, CVE-2024-38608, CVE-2024-57931,\nCVE-2025-21652, CVE-2024-57908, CVE-2024-56760, CVE-2024-57929,\nCVE-2024-36476, CVE-2024-55639, CVE-2025-21645, CVE-2024-57907,\nCVE-2024-54460, CVE-2025-21643, CVE-2024-56660, CVE-2024-53687,\nCVE-2025-21639, CVE-2024-57932, CVE-2024-56654, CVE-2024-57805,\nCVE-2024-56662, CVE-2025-21647, CVE-2024-56710, CVE-2024-57901,\nCVE-2024-56369, CVE-2024-57897, CVE-2024-57939, CVE-2024-57791,\nCVE-2024-57879, CVE-2024-57946, CVE-2024-55916, CVE-2024-41013,\nCVE-2025-21651, CVE-2024-53179, CVE-2024-57933, CVE-2024-56763,\nCVE-2024-57906)\n","status":"published","published":"2025-05-29T11:51:43Z","modified":"2026-10-30T21:54:36.504088674Z","updated_at":"2026-11-02T16:58:19.988474Z"},{"id":"USN-7514-1","title":"linux-nvidia, linux-nvidia-6.8, linux-nvidia-lowlatency 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  - RISC-V architecture;\n  - x86 architecture;\n  - Block layer subsystem;\n  - Compute Acceleration Framework;\n  - ACPI drivers;\n  - Drivers core;\n  - Ublk userspace block driver;\n  - Virtio block driver;\n  - DMA engine subsystem;\n  - GPU drivers;\n  - Microsoft Hyper-V drivers;\n  - Hardware monitoring drivers;\n  - IIO ADC drivers;\n  - IIO subsystem;\n  - InfiniBand drivers;\n  - Multiple devices driver;\n  - Media drivers;\n  - Microchip PCI driver;\n  - Network drivers;\n  - Mellanox network drivers;\n  - STMicroelectronics network drivers;\n  - PCI subsystem;\n  - Pin controllers subsystem;\n  - x86 platform drivers;\n  - Power supply drivers;\n  - SCSI subsystem;\n  - USB Gadget drivers;\n  - TDX Guest driver;\n  - AFS file system;\n  - BTRFS file system;\n  - Ceph distributed file system;\n  - EROFS file system;\n  - File systems infrastructure;\n  - Network file systems library;\n  - NILFS2 file system;\n  - Overlay file system;\n  - SMB network file system;\n  - VLANs driver;\n  - Memory management;\n  - LAPB network protocol;\n  - io_uring subsystem;\n  - BPF subsystem;\n  - Control group (cgroup);\n  - Tracing infrastructure;\n  - Workqueue subsystem;\n  - Bluetooth subsystem;\n  - Networking core;\n  - IPv4 networking;\n  - IPv6 networking;\n  - MAC80211 subsystem;\n  - Multipath TCP;\n  - Netfilter;\n  - NET/ROM layer;\n  - Packet sockets;\n  - RDS protocol;\n  - Network traffic control;\n  - SCTP protocol;\n  - SMC sockets;\n  - Wireless networking;\n  - SELinux security module;\n  - ALSA framework;\n  - SOF drivers;\n(CVE-2024-57901, CVE-2024-57889, CVE-2024-53687, CVE-2024-57804,\nCVE-2024-56709, CVE-2025-21631, CVE-2024-57908, CVE-2025-21645,\nCVE-2024-47736, CVE-2024-57896, CVE-2024-38608, CVE-2025-21637,\nCVE-2024-57898, CVE-2024-53179, CVE-2024-56710, CVE-2024-57802,\nCVE-2025-21659, CVE-2024-57903, CVE-2024-56764, CVE-2024-57892,\nCVE-2024-56717, CVE-2024-57938, CVE-2024-55881, CVE-2024-56718,\nCVE-2025-21647, CVE-2024-39282, CVE-2024-57879, CVE-2025-21643,\nCVE-2024-57792, CVE-2024-56657, CVE-2024-53685, CVE-2024-54455,\nCVE-2024-56656, CVE-2025-21638, CVE-2024-57907, CVE-2024-54193,\nCVE-2024-57806, CVE-2025-21655, CVE-2024-56670, CVE-2024-57904,\nCVE-2024-56369, CVE-2024-57945, CVE-2024-56759, CVE-2024-56716,\nCVE-2025-21651, CVE-2024-57911, CVE-2024-56372, CVE-2024-36476,\nCVE-2024-57888, CVE-2024-41013, CVE-2024-57882, CVE-2025-21636,\nCVE-2025-21971, CVE-2024-57841, CVE-2024-56760, CVE-2024-57805,\nCVE-2024-56758, CVE-2025-21648, CVE-2024-57917, CVE-2024-57913,\nCVE-2025-21658, CVE-2024-57926, CVE-2024-57939, CVE-2024-57791,\nCVE-2024-57883, CVE-2024-58087, CVE-2024-56665, CVE-2024-57887,\nCVE-2025-21635, CVE-2024-56662, CVE-2024-57893, CVE-2024-57916,\nCVE-2024-56675, CVE-2024-56763, CVE-2024-56664, CVE-2024-53690,\nCVE-2025-21663, CVE-2024-56761, CVE-2024-57910, CVE-2025-21660,\nCVE-2024-57885, CVE-2024-57899, CVE-2025-21650, CVE-2025-21888,\nCVE-2024-57801, CVE-2024-58237, CVE-2024-56767, CVE-2024-57895,\nCVE-2024-57912, CVE-2024-56654, CVE-2025-21646, CVE-2024-54683,\nCVE-2024-57931, CVE-2024-49568, CVE-2025-21639, CVE-2025-21632,\nCVE-2024-56769, CVE-2024-57807, CVE-2025-21656, CVE-2024-55639,\nCVE-2024-56652, CVE-2024-57933, CVE-2024-57793, CVE-2025-21662,\nCVE-2024-57940, CVE-2024-56715, CVE-2024-57906, CVE-2024-57900,\nCVE-2024-56660, CVE-2024-57897, CVE-2024-49571, CVE-2024-57890,\nCVE-2025-21642, CVE-2025-21634, CVE-2025-21938, CVE-2024-57929,\nCVE-2025-21664, CVE-2024-53125, CVE-2024-54460, CVE-2024-57925,\nCVE-2025-21652, CVE-2025-21653, CVE-2024-55916, CVE-2024-47408,\nCVE-2024-57902, CVE-2025-21654, CVE-2025-21649, CVE-2024-56770,\nCVE-2024-57932, CVE-2024-57946, CVE-2025-21640, CVE-2024-57884,\nCVE-2024-56667, CVE-2024-56659)\n","status":"published","published":"2025-05-16T17:05:40Z","modified":"2026-10-30T21:54:41.657690837Z","updated_at":"2026-11-02T16:58:19.988474Z"},{"id":"USN-7515-1","title":"linux-gke 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  - RISC-V architecture;\n  - x86 architecture;\n  - Block layer subsystem;\n  - Compute Acceleration Framework;\n  - ACPI drivers;\n  - Drivers core;\n  - Ublk userspace block driver;\n  - Virtio block driver;\n  - DMA engine subsystem;\n  - GPU drivers;\n  - Microsoft Hyper-V drivers;\n  - Hardware monitoring drivers;\n  - IIO ADC drivers;\n  - IIO subsystem;\n  - InfiniBand drivers;\n  - Multiple devices driver;\n  - Media drivers;\n  - Microchip PCI driver;\n  - Network drivers;\n  - Mellanox network drivers;\n  - STMicroelectronics network drivers;\n  - PCI subsystem;\n  - Pin controllers subsystem;\n  - x86 platform drivers;\n  - Power supply drivers;\n  - SCSI subsystem;\n  - USB Gadget drivers;\n  - TDX Guest driver;\n  - AFS file system;\n  - BTRFS file system;\n  - Ceph distributed file system;\n  - EROFS file system;\n  - File systems infrastructure;\n  - Network file systems library;\n  - NILFS2 file system;\n  - Overlay file system;\n  - SMB network file system;\n  - VLANs driver;\n  - Memory management;\n  - LAPB network protocol;\n  - io_uring subsystem;\n  - BPF subsystem;\n  - Control group (cgroup);\n  - Tracing infrastructure;\n  - Workqueue subsystem;\n  - Bluetooth subsystem;\n  - Networking core;\n  - IPv4 networking;\n  - IPv6 networking;\n  - MAC80211 subsystem;\n  - Multipath TCP;\n  - Netfilter;\n  - NET/ROM layer;\n  - Packet sockets;\n  - RDS protocol;\n  - Network traffic control;\n  - SCTP protocol;\n  - SMC sockets;\n  - Wireless networking;\n  - SELinux security module;\n  - ALSA framework;\n  - SOF drivers;\n(CVE-2025-21660, CVE-2025-21659, CVE-2024-56718, CVE-2024-56675,\nCVE-2025-21631, CVE-2025-21664, CVE-2025-21655, CVE-2025-21662,\nCVE-2024-57804, CVE-2025-21656, CVE-2024-57910, CVE-2025-21647,\nCVE-2025-21634, CVE-2024-56716, CVE-2024-56709, CVE-2024-56770,\nCVE-2024-57888, CVE-2024-57793, CVE-2024-56670, CVE-2024-57931,\nCVE-2025-21640, CVE-2025-21648, CVE-2024-57913, CVE-2024-56710,\nCVE-2024-44964, CVE-2024-57911, CVE-2025-21654, CVE-2024-57890,\nCVE-2024-56654, CVE-2024-56767, CVE-2025-21650, CVE-2024-54460,\nCVE-2025-21635, CVE-2024-57791, CVE-2024-49568, CVE-2024-57879,\nCVE-2024-57929, CVE-2024-56715, CVE-2024-57899, CVE-2024-53687,\nCVE-2024-57900, CVE-2024-57903, CVE-2024-54455, CVE-2024-56763,\nCVE-2024-58087, CVE-2025-21638, CVE-2024-57892, CVE-2024-57884,\nCVE-2024-57792, CVE-2024-57904, CVE-2024-56759, CVE-2024-56659,\nCVE-2024-57885, CVE-2024-57889, CVE-2024-56657, CVE-2024-56667,\nCVE-2024-47408, CVE-2024-57805, CVE-2025-21637, CVE-2024-57893,\nCVE-2024-57946, CVE-2024-57806, CVE-2024-36476, CVE-2025-21646,\nCVE-2024-56369, CVE-2024-57917, CVE-2025-21649, CVE-2024-54193,\nCVE-2024-56717, CVE-2024-41013, CVE-2024-55916, CVE-2024-57933,\nCVE-2024-57907, CVE-2024-54683, CVE-2024-57887, CVE-2024-56760,\nCVE-2024-56652, CVE-2024-57940, CVE-2024-57906, CVE-2024-57939,\nCVE-2024-56372, CVE-2024-56665, CVE-2024-57925, CVE-2025-21938,\nCVE-2024-57895, CVE-2024-58237, CVE-2024-56664, CVE-2024-56660,\nCVE-2024-55639, CVE-2025-21632, CVE-2024-57841, CVE-2024-39282,\nCVE-2025-21651, CVE-2024-53125, CVE-2024-57807, CVE-2025-21643,\nCVE-2024-57883, CVE-2024-57898, CVE-2024-57897, CVE-2024-53179,\nCVE-2024-57932, CVE-2024-57916, CVE-2024-53685, CVE-2024-57908,\nCVE-2025-21652, CVE-2025-21658, CVE-2024-57926, CVE-2024-57801,\nCVE-2024-55881, CVE-2024-57901, CVE-2025-21653, CVE-2025-21642,\nCVE-2024-57882, CVE-2024-57912, CVE-2024-56662, CVE-2025-21639,\nCVE-2025-21971, CVE-2024-47736, CVE-2024-56761, CVE-2024-57945,\nCVE-2025-21663, CVE-2024-49571, CVE-2024-56758, CVE-2024-53690,\nCVE-2024-38608, CVE-2024-56656, CVE-2025-21645, CVE-2024-56764,\nCVE-2024-57896, CVE-2024-57938, CVE-2024-57902, CVE-2025-21636,\nCVE-2024-56769, CVE-2024-57802)\n","status":"published","published":"2025-05-16T16:43:48Z","modified":"2026-10-30T21:54:36.703094006Z","updated_at":"2026-11-02T16:58:19.988474Z"},{"id":"USN-7515-2","title":"linux-gcp, linux-gcp-6.8, 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  - RISC-V architecture;\n  - x86 architecture;\n  - Block layer subsystem;\n  - Compute Acceleration Framework;\n  - ACPI drivers;\n  - Drivers core;\n  - Ublk userspace block driver;\n  - Virtio block driver;\n  - DMA engine subsystem;\n  - GPU drivers;\n  - Microsoft Hyper-V drivers;\n  - Hardware monitoring drivers;\n  - IIO ADC drivers;\n  - IIO subsystem;\n  - InfiniBand drivers;\n  - Multiple devices driver;\n  - Media drivers;\n  - Microchip PCI driver;\n  - Network drivers;\n  - Mellanox network drivers;\n  - STMicroelectronics network drivers;\n  - PCI subsystem;\n  - Pin controllers subsystem;\n  - x86 platform drivers;\n  - Power supply drivers;\n  - SCSI subsystem;\n  - USB Gadget drivers;\n  - TDX Guest driver;\n  - AFS file system;\n  - BTRFS file system;\n  - Ceph distributed file system;\n  - EROFS file system;\n  - File systems infrastructure;\n  - Network file systems library;\n  - NILFS2 file system;\n  - Overlay file system;\n  - SMB network file system;\n  - VLANs driver;\n  - Memory management;\n  - LAPB network protocol;\n  - io_uring subsystem;\n  - BPF subsystem;\n  - Control group (cgroup);\n  - Tracing infrastructure;\n  - Workqueue subsystem;\n  - Bluetooth subsystem;\n  - Networking core;\n  - IPv4 networking;\n  - IPv6 networking;\n  - MAC80211 subsystem;\n  - Multipath TCP;\n  - Netfilter;\n  - NET/ROM layer;\n  - Packet sockets;\n  - RDS protocol;\n  - Network traffic control;\n  - SCTP protocol;\n  - SMC sockets;\n  - Wireless networking;\n  - SELinux security module;\n  - ALSA framework;\n  - SOF drivers;\n(CVE-2024-57945, CVE-2024-56717, CVE-2024-57806, CVE-2025-21659,\nCVE-2024-57899, CVE-2024-57933, CVE-2024-56675, CVE-2025-21653,\nCVE-2024-44964, CVE-2024-57892, CVE-2024-56760, CVE-2024-57906,\nCVE-2024-57792, CVE-2024-54455, CVE-2025-21656, CVE-2024-56656,\nCVE-2024-57884, CVE-2025-21638, CVE-2024-56758, CVE-2025-21663,\nCVE-2024-54460, CVE-2024-57911, CVE-2024-55639, CVE-2024-57890,\nCVE-2025-21632, CVE-2024-57896, CVE-2024-56657, CVE-2024-54683,\nCVE-2025-21640, CVE-2025-21655, CVE-2025-21651, CVE-2024-57940,\nCVE-2024-56709, CVE-2024-57904, CVE-2024-47408, CVE-2024-53687,\nCVE-2025-21639, CVE-2024-57897, CVE-2025-21647, CVE-2024-57907,\nCVE-2025-21652, CVE-2024-56662, CVE-2024-57882, CVE-2024-56763,\nCVE-2025-21938, CVE-2024-57802, CVE-2024-36476, CVE-2024-57938,\nCVE-2024-57883, CVE-2024-57879, CVE-2024-57908, CVE-2024-57939,\nCVE-2024-57805, CVE-2024-56664, CVE-2024-56761, CVE-2024-56659,\nCVE-2025-21631, CVE-2024-56715, CVE-2025-21664, CVE-2024-56710,\nCVE-2024-56372, CVE-2024-57932, CVE-2024-57898, CVE-2025-21971,\nCVE-2024-47736, CVE-2024-41013, CVE-2024-57931, CVE-2024-56759,\nCVE-2024-57893, CVE-2025-21635, CVE-2024-53690, CVE-2024-57807,\nCVE-2024-56652, CVE-2024-57926, CVE-2024-57901, CVE-2024-57793,\nCVE-2024-39282, CVE-2024-49568, CVE-2024-57903, CVE-2024-57913,\nCVE-2024-53685, CVE-2024-57912, CVE-2024-56667, CVE-2024-54193,\nCVE-2024-55881, CVE-2024-56369, CVE-2024-58237, CVE-2024-57929,\nCVE-2024-53179, CVE-2024-56718, CVE-2025-21650, CVE-2025-21642,\nCVE-2025-21636, CVE-2025-21649, CVE-2025-21643, CVE-2024-58087,\nCVE-2025-21662, CVE-2025-21634, CVE-2024-57791, CVE-2025-21660,\nCVE-2024-49571, CVE-2024-56716, CVE-2024-57804, CVE-2024-57801,\nCVE-2025-21648, CVE-2024-56769, CVE-2025-21637, CVE-2024-57895,\nCVE-2024-57910, CVE-2024-57885, CVE-2024-56665, CVE-2024-55916,\nCVE-2024-57917, CVE-2024-57900, CVE-2024-57841, CVE-2025-21654,\nCVE-2024-56660, CVE-2025-21646, CVE-2024-57925, CVE-2024-57888,\nCVE-2025-21645, CVE-2025-21658, CVE-2024-57887, CVE-2024-56767,\nCVE-2024-57902, CVE-2024-56764, CVE-2024-57916, CVE-2024-56654,\nCVE-2024-57946, CVE-2024-56670, CVE-2024-56770, CVE-2024-57889,\nCVE-2024-38608, CVE-2024-53125)\n","status":"published","published":"2025-05-20T14:47:35Z","modified":"2026-10-30T21:54:42.787842787Z","updated_at":"2026-11-02T16:58:19.988474Z"},{"id":"USN-7522-1","title":"linux-azure-nvidia 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  - RISC-V architecture;\n  - x86 architecture;\n  - Block layer subsystem;\n  - Compute Acceleration Framework;\n  - ACPI drivers;\n  - Drivers core;\n  - Ublk userspace block driver;\n  - Virtio block driver;\n  - Bluetooth drivers;\n  - DMA engine subsystem;\n  - GPU drivers;\n  - Microsoft Hyper-V drivers;\n  - Hardware monitoring drivers;\n  - IIO ADC drivers;\n  - IIO subsystem;\n  - InfiniBand drivers;\n  - Multiple devices driver;\n  - Media drivers;\n  - Microchip PCI driver;\n  - Network drivers;\n  - Mellanox network drivers;\n  - Microsoft Azure Network Adapter (MANA) driver;\n  - STMicroelectronics network drivers;\n  - PCI subsystem;\n  - Pin controllers subsystem;\n  - x86 platform drivers;\n  - Power supply drivers;\n  - SCSI subsystem;\n  - USB Gadget drivers;\n  - TDX Guest driver;\n  - AFS file system;\n  - BTRFS file system;\n  - Ceph distributed file system;\n  - EROFS file system;\n  - File systems infrastructure;\n  - Network file systems library;\n  - NILFS2 file system;\n  - Overlay file system;\n  - SMB network file system;\n  - VLANs driver;\n  - Memory management;\n  - LAPB network protocol;\n  - io_uring subsystem;\n  - BPF subsystem;\n  - Control group (cgroup);\n  - Tracing infrastructure;\n  - Workqueue subsystem;\n  - Bluetooth subsystem;\n  - Networking core;\n  - IPv4 networking;\n  - IPv6 networking;\n  - MAC80211 subsystem;\n  - Multipath TCP;\n  - Netfilter;\n  - NET/ROM layer;\n  - Packet sockets;\n  - RDS protocol;\n  - Network traffic control;\n  - SCTP protocol;\n  - SMC sockets;\n  - Wireless networking;\n  - SELinux security module;\n  - ALSA framework;\n  - SOF drivers;\n(CVE-2024-56653, CVE-2024-57932, CVE-2024-54455, CVE-2024-57938,\nCVE-2024-57896, CVE-2024-53179, CVE-2024-57903, CVE-2025-21640,\nCVE-2024-56654, CVE-2024-57906, CVE-2024-53690, CVE-2025-21648,\nCVE-2024-57913, CVE-2025-21655, CVE-2024-57907, CVE-2025-21634,\nCVE-2024-57926, CVE-2025-21659, CVE-2024-54460, CVE-2024-57898,\nCVE-2024-56769, CVE-2024-36476, CVE-2025-21938, CVE-2025-21637,\nCVE-2024-57888, CVE-2024-57901, CVE-2024-57887, CVE-2024-57940,\nCVE-2024-49571, CVE-2024-57889, CVE-2024-55639, CVE-2024-57899,\nCVE-2024-56759, CVE-2024-41013, CVE-2024-57895, CVE-2024-57933,\nCVE-2024-56662, CVE-2024-56767, CVE-2025-21639, CVE-2024-56715,\nCVE-2024-57883, CVE-2025-21636, CVE-2024-57931, CVE-2025-21642,\nCVE-2024-53685, CVE-2024-56659, CVE-2025-21971, CVE-2024-56716,\nCVE-2025-21652, CVE-2024-57792, CVE-2025-21638, CVE-2024-56764,\nCVE-2024-55916, CVE-2024-57916, CVE-2024-56718, CVE-2024-57929,\nCVE-2024-57900, CVE-2025-21660, CVE-2024-57879, CVE-2024-56758,\nCVE-2024-57908, CVE-2025-21664, CVE-2024-56652, CVE-2024-57882,\nCVE-2024-39282, CVE-2025-21663, CVE-2024-47736, CVE-2024-54193,\nCVE-2025-21650, CVE-2024-56665, CVE-2024-57793, CVE-2024-58087,\nCVE-2025-21658, CVE-2025-21643, CVE-2024-54683, CVE-2024-56667,\nCVE-2024-56664, CVE-2024-56770, CVE-2024-57946, CVE-2024-57904,\nCVE-2024-56709, CVE-2024-56369, CVE-2024-58237, CVE-2024-57885,\nCVE-2024-56763, CVE-2024-56657, CVE-2025-21645, CVE-2024-57893,\nCVE-2025-21631, CVE-2024-57791, CVE-2024-57910, CVE-2024-57902,\nCVE-2024-57806, CVE-2025-21656, CVE-2024-53125, CVE-2024-56761,\nCVE-2024-56717, CVE-2024-47408, CVE-2025-21654, CVE-2025-21649,\nCVE-2024-57807, CVE-2024-56675, CVE-2025-21653, CVE-2024-57897,\nCVE-2024-53687, CVE-2024-56760, CVE-2025-21635, CVE-2025-21632,\nCVE-2024-57890, CVE-2025-21647, CVE-2024-57917, CVE-2024-56372,\nCVE-2024-56656, CVE-2024-57912, CVE-2024-57841, CVE-2025-21953,\nCVE-2024-56710, CVE-2024-57884, CVE-2024-57804, CVE-2025-21888,\nCVE-2024-56660, CVE-2024-57805, CVE-2024-57801, CVE-2024-38608,\nCVE-2024-57945, CVE-2024-55881, CVE-2024-57802, CVE-2024-57892,\nCVE-2025-21646, CVE-2024-56670, CVE-2025-21651, CVE-2024-57939,\nCVE-2024-57925, CVE-2024-57911, CVE-2025-21662, CVE-2024-49568)\n","status":"published","published":"2025-05-20T14:33:46Z","modified":"2026-10-30T21:55:10.51909878Z","updated_at":"2026-11-02T16:58:19.988474Z"},{"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"}]}}