{"id":"CVE-2024-49978","aliases":["AZL-51829","BELL-CVE-2024-49978","DEBIAN-CVE-2024-49978","DLA-4008-1","EUVD-2024-43656","GHSA-rf58-pp6r-5653","MGASA-2024-0344","MGASA-2024-0345","OESA-2024-2367","OESA-2024-2368","OESA-2024-2369","OESA-2024-2371","ROOT-OS-DEBIAN-11-CVE-2024-49978","ROOT-OS-UBUNTU-2204-CVE-2024-49978","SUSE-SU-2025:0428-1","SUSE-SU-2025:0499-1","SUSE-SU-2025:0557-1","SUSE-SU-2025:0564-1","SUSE-SU-2025:20165-1","SUSE-SU-2025:20166-1","SUSE-SU-2025:20248-1","SUSE-SU-2025:20249-1","UBUNTU-CVE-2024-49978","USN-7301-1","USN-7303-1","USN-7303-2","USN-7303-3","USN-7304-1","USN-7310-1","USN-7311-1","USN-7384-1","USN-7384-2","USN-7385-1","USN-7386-1","USN-7403-1","USN-7468-1","openSUSE-SU-2024:14500-1","openSUSE-SU-2025:14705-1"],"status":"published","title":"gso: fix udp gso fraglist segmentation after pull from frag_list","description":"In the Linux kernel, the following vulnerability has been resolved:\n\ngso: fix udp gso fraglist segmentation after pull from frag_list\n\nDetect gso fraglist skbs with corrupted geometry (see below) and\npass these to skb_segment instead of skb_segment_list, as the first\ncan segment them correctly.\n\nValid SKB_GSO_FRAGLIST skbs\n- consist of two or more segments\n- the head_skb holds the protocol headers plus first gso_size\n- one or more frag_list skbs hold exactly one segment\n- all but the last must be gso_size\n\nOptional datapath hooks such as NAT and BPF (bpf_skb_pull_data) can\nmodify these skbs, breaking these invariants.\n\nIn extreme cases they pull all data into skb linear. For UDP, this\ncauses a NULL ptr deref in __udpv4_gso_segment_list_csum at\nudp_hdr(seg-\u003enext)-\u003edest.\n\nDetect invalid geometry due to pull, by checking head_skb size.\nDon't just drop, as this may blackhole a destination. Convert to be\nable to pass to regular skb_segment.","severity":{"version":"3.1","score":7.5,"vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H","level":"high","assessor":"cna","from":"cve"},"epss":{"day":"2026-11-11","score":0.00659,"percentile":0.51997,"model":"v2026.06.15"},"facts":{"in_kev":false,"known_exploited":false,"public_exploit":false,"fix_available":true},"cwes":["CWE-476"],"published":"2024-10-21T18:02:25Z","modified":"2026-11-11T09:38:34Z","fixes":[{"ecosystem":"Alpaquita:23","package":"linux-lts","fixed_in":["6.1.114-r0"],"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.12.41-r0"],"sources":["osv"]},{"ecosystem":"Linux","package":"Kernel","fixed_in":["6.1.113","6.6.55","6.10.14","6.11.3"],"sources":["osv"]},{"ecosystem":"Debian:12","package":"linux","fixed_in":["6.1.115-1"],"sources":["osv"]},{"ecosystem":"Debian:13","package":"linux","fixed_in":["6.11.4-1"],"sources":["osv"]},{"ecosystem":"Debian:14","package":"linux","fixed_in":["6.11.4-1"],"sources":["osv"]},{"ecosystem":"Root:Debian:11","package":"linux","fixed_in":["5.10.262-1.aikido.113","5.10.262-1.aikido.114"],"sources":["osv"]},{"ecosystem":"Root:Debian:11","package":"rootio-linux","fixed_in":["5.10.262-1.aikido.113","5.10.262-1.aikido.114"],"sources":["osv"]},{"ecosystem":"Root:Ubuntu:22.04","package":"linux","fixed_in":["5.15.0-203.213.aikido.119"],"sources":["osv"]},{"ecosystem":"Root:Ubuntu:22.04","package":"rootio-linux","fixed_in":["5.15.0-203.213.aikido.119"],"sources":["osv"]},{"ecosystem":"Ubuntu:22.04:LTS","package":"linux-aws-6.8","fixed_in":["6.8.0-1023.25~22.04.1"],"sources":["osv"]},{"ecosystem":"Ubuntu:22.04:LTS","package":"linux-azure-6.8","fixed_in":["6.8.0-1025.30~22.04.1"],"sources":["osv"]},{"ecosystem":"Ubuntu:22.04:LTS","package":"linux-gcp-6.8","fixed_in":["6.8.0-1024.26~22.04.1"],"sources":["osv"]},{"ecosystem":"Ubuntu:22.04:LTS","package":"linux-hwe-6.8","fixed_in":["6.8.0-57.59~22.04.1"],"sources":["osv"]},{"ecosystem":"Ubuntu:22.04:LTS","package":"linux-ibm-6.8","fixed_in":["6.8.0-1023.23~22.04.1"],"sources":["osv"]},{"ecosystem":"Ubuntu:22.04:LTS","package":"linux-lowlatency-hwe-6.8","fixed_in":["6.8.0-54.56.1~22.04.1"],"sources":["osv"]},{"ecosystem":"Ubuntu:22.04:LTS","package":"linux-nvidia-6.8","fixed_in":["6.8.0-1022.25~22.04.2"],"sources":["osv"]},{"ecosystem":"Ubuntu:22.04:LTS","package":"linux-oracle-6.8","fixed_in":["6.8.0-1020.21~22.04.1"],"sources":["osv"]},{"ecosystem":"Ubuntu:22.04:LTS","package":"linux-riscv-6.8","fixed_in":["6.8.0-53.55.1~22.04.1"],"sources":["osv"]},{"ecosystem":"Ubuntu:Pro:Realtime:22.04:LTS","package":"linux-realtime-6.8","fixed_in":["6.8.1-1016.17~22.04.1"],"sources":["osv"]},{"ecosystem":"Ubuntu:24.04:LTS","package":"linux","fixed_in":["6.8.0-54.56"],"sources":["osv"]},{"ecosystem":"Ubuntu:24.04:LTS","package":"linux-aws","fixed_in":["6.8.0-1023.25"],"sources":["osv"]},{"ecosystem":"Ubuntu:24.04:LTS","package":"linux-azure","fixed_in":["6.8.0-1025.30"],"sources":["osv"]},{"ecosystem":"Ubuntu:24.04:LTS","package":"linux-azure-6.11","fixed_in":["6.11.0-1012.12~24.04.1"],"sources":["osv"]},{"ecosystem":"Ubuntu:24.04:LTS","package":"linux-azure-nvidia","fixed_in":["6.8.0-1014.15"],"sources":["osv"]},{"ecosystem":"Ubuntu:24.04:LTS","package":"linux-gcp","fixed_in":["6.8.0-1024.26"],"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-1019.23"],"sources":["osv"]},{"ecosystem":"Ubuntu:24.04:LTS","package":"linux-gkeop","fixed_in":["6.8.0-1006.8"],"sources":["osv"]},{"ecosystem":"Ubuntu:24.04:LTS","package":"linux-ibm","fixed_in":["6.8.0-1022.22"],"sources":["osv"]},{"ecosystem":"Ubuntu:24.04:LTS","package":"linux-lowlatency","fixed_in":["6.8.0-54.56.1"],"sources":["osv"]},{"ecosystem":"Ubuntu:24.04:LTS","package":"linux-nvidia","fixed_in":["6.8.0-1022.25"],"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-1022.25.2"],"sources":["osv"]},{"ecosystem":"Ubuntu:24.04:LTS","package":"linux-oem-6.11","fixed_in":["6.11.0-1015.15"],"sources":["osv"]},{"ecosystem":"Ubuntu:24.04:LTS","package":"linux-oem-6.8","fixed_in":["6.8.0-1024.24"],"sources":["osv"]},{"ecosystem":"Ubuntu:24.04:LTS","package":"linux-oracle","fixed_in":["6.8.0-1020.21"],"sources":["osv"]},{"ecosystem":"Ubuntu:24.04:LTS","package":"linux-raspi","fixed_in":["6.8.0-1019.23"],"sources":["osv"]},{"ecosystem":"Ubuntu:24.04:LTS","package":"linux-riscv","fixed_in":["6.8.0-53.55.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-2018.19"],"sources":["osv"]},{"ecosystem":"Ubuntu:Pro:Realtime:24.04:LTS","package":"linux-realtime","fixed_in":["6.8.1-1016.17"],"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:2","package":"kernel","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"last_affected":"5.15.200.1-1"}]}]},{"source":"osv","ecosystem":"Alpaquita:23","package":"linux-lts","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"6.1.112-r0"},{"fixed":"6.1.114-r0"}]}]},{"source":"osv","ecosystem":"Alpaquita:25","package":"linux-lts","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"6.6.89-r0"},{"fixed":"6.12.41-r0"}]}]},{"source":"osv","ecosystem":"Alpaquita:stream","package":"linux-lts","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"6.6.100-r0"},{"fixed":"6.12.41-r0"}]}]},{"source":"osv","ecosystem":"Linux","package":"Kernel","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"5.6.0"},{"fixed":"6.1.113"}]},{"type":"ECOSYSTEM","events":[{"introduced":"6.2.0"},{"fixed":"6.6.55"}]},{"type":"ECOSYSTEM","events":[{"introduced":"6.7.0"},{"fixed":"6.10.14"}]},{"type":"ECOSYSTEM","events":[{"introduced":"6.11.0"},{"fixed":"6.11.3"}]}]},{"source":"osv","ecosystem":"Debian:12","package":"linux","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.1.115-1"}]}],"versions":["6.1.106-1","6.1.106-2","6.1.106-3","6.1.112-1","6.1.27-1","6.1.37-1","6.1.38-1","6.1.38-2","6.1.38-2~bpo11+1","6.1.38-3","6.1.38-4","6.1.38-4~bpo11+1","6.1.52-1","6.1.55-1","6.1.55-1~bpo11+1","6.1.64-1","6.1.66-1","6.1.67-1","6.1.69-1","6.1.69-1~bpo11+1","6.1.76-1","6.1.76-1~bpo11+1","6.1.82-1","6.1.85-1","6.1.90-1","6.1.90-1~bpo11+1","6.1.94-1","6.1.94-1~bpo11+1","6.1.98-1","6.1.99-1"]},{"source":"osv","ecosystem":"Debian:13","package":"linux","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.11.4-1"}]}]},{"source":"osv","ecosystem":"Debian:14","package":"linux","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.11.4-1"}]}]},{"source":"osv","ecosystem":"Debian:11","package":"linux-6.1","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.1.119-1~deb11u1"}]}],"versions":["6.1.106-3~deb11u1","6.1.106-3~deb11u2","6.1.106-3~deb11u3","6.1.112-1~deb11u1"],"bundled":838},{"source":"osv","ecosystem":"Mageia:9","package":"kernel-linus","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.6.58-2.mga9"}]}],"bundled":210},{"source":"osv","ecosystem":"Mageia:9","package":"kernel","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.6.58-2.mga9"}]}],"bundled":210},{"source":"osv","ecosystem":"Mageia:9","package":"kmod-xtables-addons","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"3.24-65.mga9"}]}],"bundled":210},{"source":"osv","ecosystem":"Mageia:9","package":"kmod-virtualbox","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"7.0.20-57.mga9"}]}],"bundled":210},{"source":"osv","ecosystem":"Mageia:9","package":"kernel-firmware","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"20240909-1.mga9"}]}],"bundled":210},{"source":"osv","ecosystem":"Mageia:9","package":"kernel-firmware-nonfree","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"20240909-1.mga9.nonfree"}]}],"bundled":210},{"source":"osv","ecosystem":"Mageia:9","package":"radeon-firmware","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"20240909-1.mga9.nonfree"}]}],"bundled":210},{"source":"osv","ecosystem":"openEuler:24.03-LTS","package":"kernel","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.6.0-50.0.0.55.oe2403"}]}],"bundled":121},{"source":"osv","ecosystem":"openEuler:22.03-LTS-SP4","package":"kernel","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.10.0-235.0.0.134.oe2203sp4"}]}],"bundled":75},{"source":"osv","ecosystem":"openEuler:22.03-LTS-SP3","package":"kernel","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.10.0-235.0.0.137.oe2203sp3"}]}],"bundled":75},{"source":"osv","ecosystem":"openEuler:22.03-LTS-SP1","package":"kernel","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.10.0-136.100.0.181.oe2203sp1"}]}],"bundled":89},{"source":"osv","ecosystem":"Root:Debian:11","package":"linux","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.10.262-1.aikido.113"},{"fixed":"5.10.262-1.aikido.114"}]}]},{"source":"osv","ecosystem":"Root:Debian:11","package":"rootio-linux","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.10.262-1.aikido.113"},{"fixed":"5.10.262-1.aikido.114"}]}]},{"source":"osv","ecosystem":"Root:Ubuntu:22.04","package":"linux","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-203.213.aikido.119"}]}]},{"source":"osv","ecosystem":"Root:Ubuntu:22.04","package":"rootio-linux","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-203.213.aikido.119"}]}]},{"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 Enterprise Module for Confidential Computing Technical Preview 15 SP6","package":"kernel-coco","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.4.0-15061.15.coco15sp6.1"}]}],"bundled":54},{"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.15.coco15sp6.1"}]}],"bundled":54},{"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.15.coco15sp6.1"}]}],"bundled":54},{"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.15.coco15sp6.1"}]}],"bundled":54},{"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-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:Pro:20.04:LTS","package":"linux-aws-5.15","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.15.0-1014.18~20.04.1","5.15.0-1015.19~20.04.1","5.15.0-1017.21~20.04.1","5.15.0-1019.23~20.04.1","5.15.0-1020.24~20.04.1","5.15.0-1021.25~20.04.1","5.15.0-1022.26~20.04.1","5.15.0-1023.27~20.04.1","5.15.0-1026.30~20.04.2","5.15.0-1027.31~20.04.1","5.15.0-1028.32~20.04.1","5.15.0-1030.34~20.04.1","5.15.0-1031.35~20.04.1","5.15.0-1033.37~20.04.1","5.15.0-1034.38~20.04.1","5.15.0-1035.39~20.04.1","5.15.0-1036.40~20.04.1","5.15.0-1037.41~20.04.1","5.15.0-1038.43~20.04.1","5.15.0-1039.44~20.04.1","5.15.0-1040.45~20.04.1","5.15.0-1041.46~20.04.1","5.15.0-1043.48~20.04.1","5.15.0-1044.49~20.04.1","5.15.0-1045.50~20.04.1","5.15.0-1047.52~20.04.1","5.15.0-1048.53~20.04.1","5.15.0-1049.54~20.04.1","5.15.0-1050.55~20.04.1","5.15.0-1051.56~20.04.1","5.15.0-1052.57~20.04.1","5.15.0-1053.58~20.04.1","5.15.0-1055.60~20.04.1","5.15.0-1056.61~20.04.1","5.15.0-1057.63~20.04.1","5.15.0-1058.64~20.04.1","5.15.0-1061.67~20.04.1","5.15.0-1062.68~20.04.1","5.15.0-1063.69~20.04.1","5.15.0-1064.70~20.04.1","5.15.0-1065.71~20.04.1","5.15.0-1066.72~20.04.1","5.15.0-1067.73~20.04.1","5.15.0-1068.74~20.04.1","5.15.0-1069.75~20.04.1","5.15.0-1070.76~20.04.1","5.15.0-1071.77~20.04.1","5.15.0-1072.78~20.04.1","5.15.0-1073.79~20.04.1","5.15.0-1075.82~20.04.1","5.15.0-1077.84~20.04.1","5.15.0-1080.87~20.04.1","5.15.0-1081.88~20.04.1","5.15.0-1082.89~20.04.1","5.15.0-1083.90~20.04.1","5.15.0-1084.91~20.04.1","5.15.0-1086.93~20.04.1","5.15.0-1087.94~20.04.1","5.15.0-1088.95~20.04.1","5.15.0-1089.96~20.04.1","5.15.0-1090.97~20.04.1","5.15.0-1091.98~20.04.1","5.15.0-1092.99~20.04.1","5.15.0-1093.100~20.04.1","5.15.0-1095.102~20.04.1","5.15.0-1096.103~20.04.1","5.15.0-1097.104~20.04.1","5.15.0-1098.105~20.04.1","5.15.0-1099.106~20.04.1","5.15.0-1100.107~20.04.2","5.15.0-1101.108~20.04.1","5.15.0-1103.110~20.04.1","5.15.0-1104.111~20.04.1","5.15.0-1105.112~20.04.1","5.15.0-1106.113~20.04.1","5.15.0-1108.115~20.04.1","5.15.0-1109.116~20.04.1","5.15.0-1111.118~20.04.1","5.15.0-1112.119~20.04.1","5.15.0-1114.121~20.04.1","5.15.0-1115.122~20.04.1","5.15.0-1116.123~20.04.1","5.15.0-1117.124~20.04.1","5.15.0-1119.126~20.04.1","5.15.0-1120.127~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:Pro:20.04:LTS","package":"linux-azure-5.15","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.15.0-1007.8~20.04.1","5.15.0-1008.9~20.04.1","5.15.0-1013.16~20.04.1","5.15.0-1014.17~20.04.1","5.15.0-1017.20~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.29~20.04.1","5.15.0-1029.36~20.04.1","5.15.0-1030.37~20.04.1","5.15.0-1031.38~20.04.1","5.15.0-1033.40~20.04.1","5.15.0-1034.41~20.04.1","5.15.0-1035.42~20.04.1","5.15.0-1036.43~20.04.1","5.15.0-1037.44~20.04.1","5.15.0-1038.45~20.04.1","5.15.0-1039.46~20.04.1","5.15.0-1040.47~20.04.1","5.15.0-1041.48~20.04.1","5.15.0-1042.49~20.04.1","5.15.0-1043.50~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-1049.56~20.04.1","5.15.0-1050.57~20.04.1","5.15.0-1051.59~20.04.1","5.15.0-1052.60~20.04.1","5.15.0-1053.61~20.04.1","5.15.0-1054.62~20.04.1","5.15.0-1056.64~20.04.1","5.15.0-1057.65~20.04.1","5.15.0-1058.66~20.04.2","5.15.0-1059.67~20.04.1","5.15.0-1060.69~20.04.1","5.15.0-1061.70~20.04.1","5.15.0-1063.72~20.04.1","5.15.0-1064.73~20.04.1","5.15.0-1065.74~20.04.1","5.15.0-1067.76~20.04.1","5.15.0-1068.77~20.04.1","5.15.0-1070.79~20.04.1","5.15.0-1071.80~20.04.1","5.15.0-1072.81~20.04.1","5.15.0-1073.82~20.04.1","5.15.0-1074.83~20.04.1","5.15.0-1075.84~20.04.1","5.15.0-1078.87~20.04.1","5.15.0-1079.88~20.04.1","5.15.0-1081.90~20.04.1","5.15.0-1082.91~20.04.1","5.15.0-1086.95~20.04.1","5.15.0-1087.96~20.04.1","5.15.0-1088.97~20.04.1","5.15.0-1089.98~20.04.1","5.15.0-1091.100~20.04.1","5.15.0-1094.103~20.04.1","5.15.0-1095.104~20.04.1","5.15.0-1096.105~20.04.1","5.15.0-1097.106~20.04.1","5.15.0-1098.107~20.04.1","5.15.0-1102.111~20.04.1","5.15.0-1103.112~20.04.1","5.15.0-1110.119~20.04.1","5.15.0-1111.120~20.04.1","5.15.0-1114.123~20.04.1","5.15.0-1116.125~20.04.1","5.15.0-1117.126~20.04.1","5.15.0-1119.128~20.04.1","5.15.0-1121.130~20.04.1","5.15.0-1122.131~20.04.1","5.15.0-1123.132~20.04.1","5.15.0-1125.134~20.04.1","5.15.0-1126.135~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:Pro:20.04:LTS","package":"linux-azure-fde-5.15","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.15.0-1019.24~20.04.1.1","5.15.0-1020.25~20.04.1.1","5.15.0-1021.26~20.04.1.1","5.15.0-1029.36~20.04.1.1","5.15.0-1030.37~20.04.1.1","5.15.0-1031.38~20.04.1.1","5.15.0-1033.40~20.04.1.1","5.15.0-1034.41~20.04.1.2","5.15.0-1035.42~20.04.1.1","5.15.0-1036.43~20.04.1.1","5.15.0-1037.44~20.04.1.1","5.15.0-1038.45~20.04.1.1","5.15.0-1039.46~20.04.1.1","5.15.0-1040.47~20.04.1.1","5.15.0-1041.48~20.04.1.1","5.15.0-1042.49~20.04.1.1","5.15.0-1043.50~20.04.1.1","5.15.0-1046.53~20.04.1.1","5.15.0-1047.54~20.04.1.1","5.15.0-1049.56~20.04.1.1","5.15.0-1050.57~20.04.1.1","5.15.0-1051.59~20.04.1.1","5.15.0-1052.60~20.04.1.1","5.15.0-1053.61~20.04.1.1","5.15.0-1054.62~20.04.1.1","5.15.0-1056.64~20.04.1.1","5.15.0-1057.65~20.04.1.1","5.15.0-1058.66~20.04.2.1","5.15.0-1059.67~20.04.1.1","5.15.0-1060.69~20.04.1.1","5.15.0-1061.70~20.04.1.1","5.15.0-1063.72~20.04.1.1","5.15.0-1064.73~20.04.1.1","5.15.0-1065.74~20.04.1.1","5.15.0-1067.76~20.04.1.1","5.15.0-1068.77~20.04.1.1","5.15.0-1070.79~20.04.1.1","5.15.0-1071.80~20.04.1.1","5.15.0-1072.81~20.04.1.1","5.15.0-1073.82~20.04.1.1","5.15.0-1074.83~20.04.1.1","5.15.0-1076.85~20.04.1.1","5.15.0-1078.87~20.04.1.1","5.15.0-1081.90~20.04.1.1","5.15.0-1082.91~20.04.1.1","5.15.0-1086.95~20.04.1.1","5.15.0-1087.96~20.04.1.1","5.15.0-1088.97~20.04.1.1","5.15.0-1089.98~20.04.1.1","5.15.0-1091.100~20.04.1.1","5.15.0-1094.103~20.04.1.1","5.15.0-1096.105~20.04.1.1","5.15.0-1097.106~20.04.1.1","5.15.0-1098.107~20.04.1.1","5.15.0-1102.111~20.04.1.1","5.15.0-1103.112~20.04.1.1","5.15.0-1111.120~20.04.1.1","5.15.0-1114.123~20.04.1","5.15.0-1116.125~20.04.1","5.15.0-1117.126~20.04.2","5.15.0-1118.127~20.04.1","5.15.0-1119.128~20.04.1","5.15.0-1120.129~20.04.1","5.15.0-1121.130~20.04.1","5.15.0-1122.131~20.04.1","5.15.0-1124.133~20.04.1","5.15.0-1125.134~20.04.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:Pro:20.04:LTS","package":"linux-gcp-5.15","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.15.0-1006.9~20.04.1","5.15.0-1012.17~20.04.1","5.15.0-1013.18~20.04.1","5.15.0-1016.21~20.04.1","5.15.0-1017.23~20.04.2","5.15.0-1018.24~20.04.1","5.15.0-1021.28~20.04.1","5.15.0-1022.29~20.04.1","5.15.0-1025.32~20.04.2","5.15.0-1026.33~20.04.1","5.15.0-1027.34~20.04.1","5.15.0-1029.36~20.04.1","5.15.0-1030.37~20.04.1","5.15.0-1031.38~20.04.1","5.15.0-1032.40~20.04.1","5.15.0-1033.41~20.04.1","5.15.0-1034.42~20.04.1","5.15.0-1035.43~20.04.1","5.15.0-1036.44~20.04.1","5.15.0-1037.45~20.04.1","5.15.0-1038.46~20.04.1","5.15.0-1039.47~20.04.1","5.15.0-1040.48~20.04.1","5.15.0-1041.49~20.04.1","5.15.0-1042.50~20.04.1","5.15.0-1044.52~20.04.1","5.15.0-1045.53~20.04.2","5.15.0-1046.54~20.04.1","5.15.0-1047.55~20.04.1","5.15.0-1048.56~20.04.1","5.15.0-1049.57~20.04.1","5.15.0-1051.59~20.04.1","5.15.0-1052.60~20.04.1","5.15.0-1053.61~20.04.1","5.15.0-1054.62~20.04.1","5.15.0-1055.63~20.04.1","5.15.0-1058.66~20.04.1","5.15.0-1059.67~20.04.1","5.15.0-1060.68~20.04.1","5.15.0-1062.70~20.04.1","5.15.0-1065.73~20.04.1","5.15.0-1066.74~20.04.1","5.15.0-1067.75~20.04.1","5.15.0-1068.76~20.04.1","5.15.0-1069.77~20.04.1","5.15.0-1070.78~20.04.1","5.15.0-1071.79~20.04.1","5.15.0-1072.80~20.04.1","5.15.0-1073.81~20.04.1","5.15.0-1074.83~20.04.1","5.15.0-1075.84~20.04.1","5.15.0-1077.86~20.04.1","5.15.0-1078.87~20.04.1","5.15.0-1081.90~20.04.1","5.15.0-1083.92~20.04.1","5.15.0-1085.94~20.04.1","5.15.0-1086.95~20.04.1","5.15.0-1087.96~20.04.2","5.15.0-1088.97~20.04.1","5.15.0-1090.99~20.04.1","5.15.0-1091.100~20.04.1","5.15.0-1092.101~20.04.1","5.15.0-1093.102~20.04.1","5.15.0-1095.104~20.04.1","5.15.0-1096.105~20.04.1","5.15.0-1097.106~20.04.1","5.15.0-1098.107~20.04.1","5.15.0-1099.108~20.04.1","5.15.0-1100.109~20.04.1","5.15.0-1101.110~20.04.1","5.15.0-1103.112~20.04.1","5.15.0-1104.113~20.04.1","5.15.0-1106.115~20.04.1","5.15.0-1108.117~20.04.1","5.15.0-1109.118~20.04.1","5.15.0-1111.121~20.04.1","5.15.0-1112.122~20.04.1","5.15.0-1114.124~20.04.1","5.15.0-1118.128~20.04.1","5.15.0-1120.130~20.04.1","5.15.0-1121.131~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-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:Pro:20.04:LTS","package":"linux-hwe-5.15","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.15.0-33.34~20.04.1","5.15.0-41.44~20.04.1","5.15.0-43.46~20.04.1","5.15.0-46.49~20.04.1","5.15.0-48.54~20.04.1","5.15.0-50.56~20.04.1","5.15.0-52.58~20.04.1","5.15.0-53.59~20.04.1","5.15.0-56.62~20.04.1","5.15.0-57.63~20.04.1","5.15.0-58.64~20.04.1","5.15.0-60.66~20.04.1","5.15.0-67.74~20.04.1","5.15.0-69.76~20.04.1","5.15.0-70.77~20.04.1","5.15.0-71.78~20.04.1","5.15.0-72.79~20.04.1","5.15.0-73.80~20.04.1","5.15.0-75.82~20.04.1","5.15.0-76.83~20.04.1","5.15.0-78.85~20.04.1","5.15.0-79.86~20.04.2","5.15.0-82.91~20.04.1","5.15.0-83.92~20.04.1","5.15.0-84.93~20.04.1","5.15.0-86.96~20.04.1","5.15.0-87.97~20.04.1","5.15.0-88.98~20.04.1","5.15.0-89.99~20.04.1","5.15.0-91.101~20.04.1","5.15.0-92.102~20.04.1","5.15.0-94.104~20.04.1","5.15.0-97.107~20.04.1","5.15.0-100.110~20.04.1","5.15.0-101.111~20.04.1","5.15.0-102.112~20.04.1","5.15.0-105.115~20.04.1","5.15.0-106.116~20.04.1","5.15.0-107.117~20.04.1","5.15.0-113.123~20.04.1","5.15.0-116.126~20.04.1","5.15.0-117.127~20.04.1","5.15.0-118.128~20.04.1","5.15.0-119.129~20.04.1","5.15.0-121.131~20.04.1","5.15.0-122.132~20.04.1","5.15.0-124.134~20.04.1","5.15.0-125.135~20.04.1","5.15.0-126.136~20.04.1","5.15.0-127.137~20.04.1","5.15.0-130.140~20.04.1","5.15.0-131.141~20.04.1","5.15.0-134.145~20.04.1","5.15.0-136.147~20.04.1","5.15.0-138.148~20.04.1","5.15.0-139.149~20.04.1","5.15.0-142.152~20.04.1","5.15.0-143.153~20.04.1","5.15.0-144.157~20.04.1","5.15.0-145.158~20.04.1","5.15.0-151.161~20.04.1","5.15.0-152.162~20.04.1","5.15.0-153.163~20.04.1","5.15.0-156.166~20.04.1","5.15.0-157.167~20.04.1","5.15.0-160.170~20.04.1","5.15.0-161.171~20.04.1","5.15.0-163.173~20.04.1","5.15.0-164.174~20.04.1","5.15.0-168.178~20.04.1","5.15.0-170.180~20.04.3","5.15.0-171.181~20.04.1","5.15.0-173.183~20.04.1","5.15.0-176.186~20.04.1","5.15.0-177.187~20.04.1","5.15.0-179.189~20.04.1","5.15.0-181.191~20.04.1","5.15.0-185.195~20.04.1","5.15.0-186.196~20.04.1","5.15.0-190.200~20.04.1","5.15.0-191.201~20.04.1","5.15.0-194.204~20.04.1","5.15.0-198.208~20.04.1","5.15.0-202.212~20.04.1","5.15.0-203.213~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:Pro:20.04:LTS","package":"linux-ibm-5.15","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.15.0-1033.36~20.04.1","5.15.0-1034.37~20.04.1","5.15.0-1035.38~20.04.1","5.15.0-1036.39~20.04.1","5.15.0-1037.40~20.04.1","5.15.0-1038.41~20.04.1","5.15.0-1040.43~20.04.1","5.15.0-1041.44~20.04.1","5.15.0-1042.45~20.04.1","5.15.0-1043.46~20.04.1","5.15.0-1044.47~20.04.1","5.15.0-1045.48~20.04.1","5.15.0-1046.49~20.04.1","5.15.0-1047.50~20.04.1","5.15.0-1048.51~20.04.1","5.15.0-1049.52~20.04.1","5.15.0-1050.53~20.04.1","5.15.0-1053.56~20.04.1","5.15.0-1054.57~20.04.1","5.15.0-1055.58~20.04.1","5.15.0-1057.60~20.04.1","5.15.0-1058.61~20.04.1","5.15.0-1059.62~20.04.1","5.15.0-1060.63~20.04.1","5.15.0-1061.64~20.04.1","5.15.0-1062.65~20.04.1","5.15.0-1063.66~20.04.1","5.15.0-1064.67~20.04.1","5.15.0-1065.68~20.04.1","5.15.0-1066.69~20.04.1","5.15.0-1067.70~20.04.1","5.15.0-1068.71~20.04.1","5.15.0-1069.72~20.04.1","5.15.0-1074.77~20.04.1","5.15.0-1075.78~20.04.1","5.15.0-1076.79~20.04.1","5.15.0-1078.81~20.04.1","5.15.0-1079.82~20.04.1","5.15.0-1080.83~20.04.1","5.15.0-1081.84~20.04.1","5.15.0-1083.86~20.04.1","5.15.0-1085.88~20.04.1","5.15.0-1086.89~20.04.1","5.15.0-1087.90~20.04.1","5.15.0-1089.92~20.04.1","5.15.0-1090.93~20.04.1","5.15.0-1091.94~20.04.1","5.15.0-1092.95~20.04.1","5.15.0-1093.96~20.04.1","5.15.0-1094.97~20.04.1","5.15.0-1095.98~20.04.1","5.15.0-1097.100~20.04.1","5.15.0-1098.101~20.04.1","5.15.0-1099.102~20.04.1","5.15.0-1100.103~20.04.1","5.15.0-1102.105~20.04.1","5.15.0-1103.106~20.04.1","5.15.0-1105.109~20.04.1","5.15.0-1106.110~20.04.1","5.15.0-1107.111~20.04.1","5.15.0-1108.112~20.04.1","5.15.0-1109.113~20.04.1","5.15.0-1110.114~20.04.1","5.15.0-1111.115~20.04.1","5.15.0-1113.117~20.04.1","5.15.0-1114.118~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:Pro:20.04:LTS","package":"linux-intel-iotg-5.15","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.15.0-1003.5~20.04.1","5.15.0-1008.11~20.04.1","5.15.0-1010.14~20.04.1","5.15.0-1015.20~20.04.2","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-1021.26~20.04.1","5.15.0-1023.28~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-1030.35~20.04.1","5.15.0-1031.36~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-1040.46~20.04.1","5.15.0-1043.49~20.04.1","5.15.0-1045.51~20.04.1","5.15.0-1046.52~20.04.1","5.15.0-1048.54~20.04.1","5.15.0-1049.55~20.04.1","5.15.0-1050.56~20.04.1","5.15.0-1051.57~20.04.1","5.15.0-1052.58~20.04.1","5.15.0-1055.61~20.04.1","5.15.0-1058.64~20.04.1","5.15.0-1059.65~20.04.1","5.15.0-1060.66~20.04.1","5.15.0-1061.67~20.04.1","5.15.0-1062.68~20.04.1","5.15.0-1063.69~20.04.1","5.15.0-1064.70~20.04.1","5.15.0-1065.71~20.04.1","5.15.0-1066.72~20.04.1","5.15.0-1067.73~20.04.1","5.15.0-1071.77~20.04.1","5.15.0-1072.78~20.04.1","5.15.0-1073.79~20.04.2","5.15.0-1074.80~20.04.1","5.15.0-1077.83~20.04.1","5.15.0-1078.84~20.04.1","5.15.0-1079.85~20.04.1","5.15.0-1083.89~20.04.1","5.15.0-1084.90~20.04.1","5.15.0-1085.91~20.04.1","5.15.0-1086.92~20.04.1","5.15.0-1087.93~20.04.1","5.15.0-1088.94~20.04.1","5.15.0-1090.96~20.04.1","5.15.0-1091.97~20.04.1","5.15.0-1092.98~20.04.1","5.15.0-1093.99~20.04.1","5.15.0-1094.100~20.04.1","5.15.0-1095.101~20.04.1","5.15.0-1096.102~20.04.1","5.15.0-1098.104~20.04.1","5.15.0-1099.105~20.04.1","5.15.0-1100.106~20.04.1","5.15.0-1101.107~20.04.1","5.15.0-1103.109~20.04.1","5.15.0-1104.110~20.04.1","5.15.0-1106.112~20.04.1","5.15.0-1107.113~20.04.1","5.15.0-1108.114~20.04.1","5.15.0-1109.115~20.04.1","5.15.0-1110.116~20.04.1","5.15.0-1111.117~20.04.1","5.15.0-1112.118~20.04.1","5.15.0-1114.120~20.04.1","5.15.0-1115.121~20.04.1"]},{"source":"osv","ecosystem":"Ubuntu:Pro:20.04:LTS","package":"linux-lowlatency-hwe-5.15","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.15.0-33.34~20.04.1","5.15.0-42.45~20.04.1","5.15.0-43.46~20.04.1","5.15.0-46.49~20.04.1","5.15.0-48.54~20.04.1","5.15.0-50.56~20.04.1","5.15.0-52.58~20.04.1","5.15.0-53.59~20.04.1","5.15.0-56.62~20.04.1","5.15.0-58.64~20.04.1","5.15.0-60.66~20.04.1","5.15.0-67.74~20.04.1","5.15.0-69.76~20.04.1","5.15.0-70.77~20.04.1","5.15.0-71.78~20.04.1","5.15.0-72.79~20.04.1","5.15.0-73.80~20.04.1","5.15.0-75.82~20.04.1","5.15.0-76.83~20.04.1","5.15.0-78.85~20.04.1","5.15.0-79.88~20.04.1","5.15.0-82.91~20.04.1","5.15.0-83.92~20.04.1","5.15.0-84.93~20.04.1","5.15.0-86.95~20.04.1","5.15.0-87.96~20.04.1","5.15.0-88.98~20.04.1","5.15.0-89.99~20.04.1","5.15.0-91.101~20.04.1","5.15.0-92.102~20.04.1","5.15.0-94.104~20.04.1","5.15.0-97.107~20.04.1","5.15.0-100.110~20.04.1","5.15.0-101.111~20.04.1","5.15.0-102.112~20.04.1","5.15.0-105.115~20.04.1","5.15.0-106.116~20.04.1","5.15.0-107.117~20.04.1","5.15.0-110.120~20.04.1","5.15.0-113.123~20.04.1","5.15.0-116.126~20.04.1","5.15.0-117.127~20.04.1","5.15.0-118.128~20.04.1","5.15.0-119.129~20.04.1","5.15.0-121.131~20.04.1","5.15.0-122.132~20.04.1","5.15.0-124.134~20.04.1","5.15.0-125.135~20.04.1","5.15.0-126.136~20.04.1","5.15.0-127.137~20.04.1","5.15.0-128.138~20.04.1","5.15.0-129.139~20.04.1","5.15.0-131.141~20.04.1","5.15.0-133.143~20.04.1","5.15.0-134.145~20.04.1","5.15.0-135.146~20.04.1","5.15.0-136.147~20.04.1","5.15.0-138.148~20.04.1","5.15.0-139.149~20.04.1","5.15.0-140.150~20.04.1","5.15.0-142.152~20.04.1","5.15.0-143.153~20.04.1","5.15.0-144.157~20.04.1","5.15.0-145.158~20.04.1","5.15.0-152.162~20.04.1","5.15.0-153.163~20.04.1","5.15.0-156.166~20.04.1","5.15.0-157.167~20.04.1","5.15.0-160.170~20.04.1","5.15.0-161.171~20.04.1","5.15.0-163.173~20.04.1","5.15.0-164.174~20.04.1","5.15.0-168.178~20.04.1","5.15.0-170.180~20.04.1","5.15.0-171.181~20.04.1","5.15.0-173.183~20.04.1","5.15.0-174.184~20.04.1","5.15.0-175.185~20.04.1","5.15.0-177.187~20.04.1","5.15.0-178.188~20.04.1","5.15.0-179.189~20.04.1","5.15.0-181.191~20.04.1","5.15.0-183.193~20.04.1","5.15.0-184.194~20.04.1","5.15.0-190.200~20.04.1","5.15.0-191.201~20.04.1","5.15.0-194.204~20.04.1","5.15.0-195.205~20.04.1","5.15.0-197.207~20.04.1","5.15.0-198.208~20.04.1"]},{"source":"osv","ecosystem":"Ubuntu:Pro:20.04:LTS","package":"linux-nvidia-tegra-5.15","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.15.0-1009.9~20.04.1","5.15.0-1010.10~20.04.1","5.15.0-1012.12~20.04.1","5.15.0-1014.14~20.04.1","5.15.0-1015.15~20.04.1","5.15.0-1016.16~20.04.1","5.15.0-1017.17~20.04.1","5.15.0-1018.18~20.04.1","5.15.0-1019.19~20.04.1","5.15.0-1020.20~20.04.1","5.15.0-1022.22~20.04.1","5.15.0-1025.25~20.04.1","5.15.0-1027.27~20.04.1","5.15.0-1030.30~20.04.1","5.15.0-1032.32~20.04.1","5.15.0-1039.39~20.04.1","5.15.0-1040.40~20.04.1","5.15.0-1041.41~20.04.1","5.15.0-1042.42~20.04.1","5.15.0-1043.43~20.04.1","5.15.0-1044.44~20.04.1","5.15.0-1045.45~20.04.1","5.15.0-1046.46~20.04.1","5.15.0-1047.47~20.04.1","5.15.0-1048.48~20.04.1","5.15.0-1049.49~20.04.1","5.15.0-1050.50~20.04.1","5.15.0-1051.51~20.04.1","5.15.0-1052.52~20.04.2","5.15.0-1053.53~20.04.1","5.15.0-1055.55~20.04.1","5.15.0-1057.57~20.04.1","5.15.0-1058.58~20.04.1","5.15.0-1060.60~20.04.1","5.15.0-1061.61~20.04.1","5.15.0-1063.63~20.04.1","5.15.0-1064.66~20.04.1","5.15.0-1065.67~20.04.1","5.15.0-1066.68~20.04.1","5.15.0-1067.69~20.04.1","5.15.0-1068.70~20.04.1","5.15.0-1070.72~20.04.1","5.15.0-1071.73~20.04.1"]},{"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:Pro:20.04:LTS","package":"linux-oracle-5.15","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.15.0-1007.9~20.04.1","5.15.0-1013.17~20.04.1","5.15.0-1016.20~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-1021.27~20.04.1","5.15.0-1022.28~20.04.1","5.15.0-1025.31~20.04.2","5.15.0-1027.33~20.04.1","5.15.0-1029.35~20.04.1","5.15.0-1030.36~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-1041.47~20.04.1","5.15.0-1042.48~20.04.1","5.15.0-1044.50~20.04.1","5.15.0-1045.51~20.04.1","5.15.0-1046.52~20.04.1","5.15.0-1047.53~20.04.1","5.15.0-1048.54~20.04.1","5.15.0-1049.55~20.04.1","5.15.0-1050.56~20.04.1","5.15.0-1051.57~20.04.1","5.15.0-1052.58~20.04.1","5.15.0-1053.59~20.04.1","5.15.0-1054.60~20.04.1","5.15.0-1055.61~20.04.1","5.15.0-1058.64~20.04.1","5.15.0-1059.65~20.04.1","5.15.0-1061.67~20.04.1","5.15.0-1062.68~20.04.1","5.15.0-1063.69~20.04.1","5.15.0-1065.71~20.04.1","5.15.0-1066.72~20.04.1","5.15.0-1067.73~20.04.1","5.15.0-1068.74~20.04.1","5.15.0-1069.75~20.04.1","5.15.0-1070.76~20.04.1","5.15.0-1071.77~20.04.1","5.15.0-1072.78~20.04.1","5.15.0-1073.79~20.04.1","5.15.0-1074.80~20.04.1","5.15.0-1075.81~20.04.1","5.15.0-1076.82~20.04.1","5.15.0-1077.83~20.04.1","5.15.0-1078.84~20.04.1","5.15.0-1079.85~20.04.1","5.15.0-1080.86~20.04.1","5.15.0-1081.87~20.04.1","5.15.0-1083.89~20.04.1","5.15.0-1084.90~20.04.1","5.15.0-1085.91~20.04.3","5.15.0-1086.92~20.04.1","5.15.0-1088.94~20.04.1","5.15.0-1090.96~20.04.1","5.15.0-1091.97~20.04.1","5.15.0-1092.98~20.04.1","5.15.0-1093.99~20.04.1","5.15.0-1094.100~20.04.1","5.15.0-1095.101~20.04.1","5.15.0-1096.102~20.04.1","5.15.0-1097.103~20.04.1","5.15.0-1098.104~20.04.1","5.15.0-1100.106~20.04.1","5.15.0-1101.107~20.04.1","5.15.0-1102.108~20.04.1","5.15.0-1104.110~20.04.1","5.15.0-1106.112~20.04.1","5.15.0-1108.114~20.04.1","5.15.0-1109.115~20.04.1","5.15.0-1110.116~20.04.1","5.15.0-1111.117~20.04.1","5.15.0-1114.120~20.04.1","5.15.0-1116.122~20.04.1","5.15.0-1117.123~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:Pro:20.04:LTS","package":"linux-riscv-5.15","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.15.0-1015.17~20.04.1","5.15.0-1017.19~20.04.1","5.15.0-1018.21~20.04.1","5.15.0-1019.22~20.04.1","5.15.0-1022.26~20.04.1","5.15.0-1023.27~20.04.1","5.15.0-1026.30~20.04.2","5.15.0-1027.31~20.04.1","5.15.0-1028.32~20.04.1","5.15.0-1029.33~20.04.1","5.15.0-1030.34~20.04.1","5.15.0-1031.35~20.04.1","5.15.0-1032.36~20.04.1","5.15.0-1033.37~20.04.1","5.15.0-1034.38~20.04.1","5.15.0-1035.39~20.04.1","5.15.0-1036.40~20.04.2","5.15.0-1037.41~20.04.2","5.15.0-1038.42~20.04.2","5.15.0-1039.43~20.04.2","5.15.0-1040.44~20.04.3","5.15.0-1041.45~20.04.1","5.15.0-1043.47~20.04.1","5.15.0-1044.48~20.04.1","5.15.0-1045.49~20.04.1","5.15.0-1046.50~20.04.1","5.15.0-1047.51~20.04.1","5.15.0-1048.52~20.04.1","5.15.0-1049.53~20.04.2","5.15.0-1050.54~20.04.1","5.15.0-1051.55~20.04.1","5.15.0-1052.56~20.04.1","5.15.0-1053.57~20.04.1","5.15.0-1056.60~20.04.1","5.15.0-1057.61~20.04.1","5.15.0-1058.62~20.04.1","5.15.0-1059.63~20.04.1","5.15.0-1060.64~20.04.1","5.15.0-1061.65~20.04.1","5.15.0-1062.66~20.04.1","5.15.0-1063.67~20.04.1","5.15.0-1064.68~20.04.1","5.15.0-1065.69~20.04.1","5.15.0-1066.70~20.04.1","5.15.0-1067.71~20.04.1","5.15.0-1068.72~20.04.1","5.15.0-1069.73~20.04.1","5.15.0-1070.74~20.04.1","5.15.0-1071.75~20.04.1","5.15.0-1072.76~20.04.1","5.15.0-1073.77~20.04.1","5.15.0-1074.78~20.04.1","5.15.0-1075.79~20.04.1","5.15.0-1076.80~20.04.1","5.15.0-1077.81~20.04.1","5.15.0-1078.82~20.04.1","5.15.0-1079.83~20.04.1","5.15.0-1081.85~20.04.1","5.15.0-1082.86~20.04.1","5.15.0-1083.87~20.04.1","5.15.0-1084.88~20.04.1","5.15.0-1085.89~20.04.1","5.15.0-1086.90~20.04.1","5.15.0-1087.91~20.04.1","5.15.0-1088.92~20.04.1","5.15.0-1090.94~20.04.1","5.15.0-1091.95~20.04.1","5.15.0-1092.96~20.04.1","5.15.0-1093.97~20.04.2","5.15.0-1094.98~20.04.1","5.15.0-1095.99~20.04.1","5.15.0-1096.100~20.04.1","5.15.0-1097.101~20.04.1","5.15.0-1098.102~20.04.1","5.15.0-1099.103~20.04.1","5.15.0-1100.104~20.04.1","5.15.0-1102.106~20.04.1","5.15.0-1103.107~20.04.1","5.15.0-1105.109~20.04.1","5.15.0-1106.110~20.04.1","5.15.0-1107.111~20.04.1","5.15.0-1108.112~20.04.1","5.15.0-1109.113~20.04.1","5.15.0-1110.114~20.04.1","5.15.0-1111.115~20.04.1","5.15.0-1113.117~20.04.2","5.15.0-1114.118~20.04.1"]},{"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","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.13.0-19.19","5.15.0-17.17","5.15.0-18.18","5.15.0-22.22","5.15.0-23.23","5.15.0-25.25","5.15.0-27.28","5.15.0-30.31","5.15.0-33.34","5.15.0-35.36","5.15.0-37.39","5.15.0-39.42","5.15.0-40.43","5.15.0-41.44","5.15.0-43.46","5.15.0-46.49","5.15.0-47.51","5.15.0-48.54","5.15.0-50.56","5.15.0-52.58","5.15.0-53.59","5.15.0-56.62","5.15.0-57.63","5.15.0-58.64","5.15.0-60.66","5.15.0-67.74","5.15.0-69.76","5.15.0-70.77","5.15.0-71.78","5.15.0-72.79","5.15.0-73.80","5.15.0-75.82","5.15.0-76.83","5.15.0-78.85","5.15.0-79.86","5.15.0-82.91","5.15.0-83.92","5.15.0-84.93","5.15.0-86.96","5.15.0-87.97","5.15.0-88.98","5.15.0-89.99","5.15.0-91.101","5.15.0-92.102","5.15.0-94.104","5.15.0-97.107","5.15.0-100.110","5.15.0-101.111","5.15.0-102.112","5.15.0-105.115","5.15.0-106.116","5.15.0-107.117","5.15.0-112.122","5.15.0-113.123","5.15.0-116.126","5.15.0-117.127","5.15.0-118.128","5.15.0-119.129","5.15.0-121.131","5.15.0-122.132","5.15.0-124.134","5.15.0-125.135","5.15.0-126.136","5.15.0-127.137","5.15.0-128.138","5.15.0-130.140","5.15.0-131.141","5.15.0-133.144","5.15.0-134.145","5.15.0-135.146","5.15.0-136.147","5.15.0-138.148","5.15.0-139.149","5.15.0-140.150","5.15.0-141.151","5.15.0-142.152","5.15.0-143.153","5.15.0-144.157","5.15.0-151.161","5.15.0-152.162","5.15.0-153.163","5.15.0-156.166","5.15.0-157.167","5.15.0-160.170","5.15.0-161.171","5.15.0-163.173","5.15.0-164.174","5.15.0-168.178","5.15.0-170.180","5.15.0-171.181","5.15.0-173.183","5.15.0-174.184","5.15.0-176.186","5.15.0-177.187","5.15.0-179.189","5.15.0-181.191","5.15.0-185.195","5.15.0-186.196","5.15.0-187.197","5.15.0-190.200","5.15.0-191.201","5.15.0-194.204","5.15.0-198.208","5.15.0-202.212","5.15.0-203.213"]},{"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","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.13.0-1005.6","5.15.0-1002.4","5.15.0-1003.5","5.15.0-1004.6","5.15.0-1005.7","5.15.0-1008.10","5.15.0-1009.11","5.15.0-1011.14","5.15.0-1013.17","5.15.0-1014.18","5.15.0-1015.19","5.15.0-1017.21","5.15.0-1019.23","5.15.0-1020.24","5.15.0-1021.25","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","5.15.0-1030.34","5.15.0-1031.35","5.15.0-1033.37","5.15.0-1034.38","5.15.0-1035.39","5.15.0-1036.40","5.15.0-1037.41","5.15.0-1038.43","5.15.0-1039.44","5.15.0-1040.45","5.15.0-1042.47","5.15.0-1043.48","5.15.0-1044.49","5.15.0-1045.50","5.15.0-1047.52","5.15.0-1048.53","5.15.0-1049.54","5.15.0-1050.55","5.15.0-1051.56","5.15.0-1052.57","5.15.0-1053.58","5.15.0-1055.60","5.15.0-1056.61","5.15.0-1057.63","5.15.0-1060.66","5.15.0-1061.67","5.15.0-1062.68","5.15.0-1063.69","5.15.0-1064.70","5.15.0-1065.71","5.15.0-1066.72","5.15.0-1067.73","5.15.0-1068.74","5.15.0-1069.75","5.15.0-1070.76","5.15.0-1071.77","5.15.0-1072.78","5.15.0-1073.79","5.15.0-1076.83","5.15.0-1078.85","5.15.0-1079.86","5.15.0-1080.87","5.15.0-1081.88","5.15.0-1082.89","5.15.0-1083.90","5.15.0-1084.91","5.15.0-1085.92","5.15.0-1086.93","5.15.0-1087.94","5.15.0-1088.95","5.15.0-1089.96","5.15.0-1090.97","5.15.0-1091.98","5.15.0-1092.99","5.15.0-1093.100","5.15.0-1095.102","5.15.0-1096.103","5.15.0-1097.104","5.15.0-1098.105","5.15.0-1099.106","5.15.0-1100.107","5.15.0-1101.108","5.15.0-1103.110","5.15.0-1104.111","5.15.0-1105.112","5.15.0-1106.113","5.15.0-1108.115","5.15.0-1109.116","5.15.0-1111.118","5.15.0-1112.119","5.15.0-1113.120","5.15.0-1114.121","5.15.0-1115.122","5.15.0-1116.123","5.15.0-1117.124","5.15.0-1119.126","5.15.0-1120.127"]},{"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-1023.25~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"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-azure","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.13.0-1006.7","5.15.0-1001.2","5.15.0-1002.3","5.15.0-1003.4","5.15.0-1005.6","5.15.0-1007.8","5.15.0-1008.9","5.15.0-1010.12","5.15.0-1012.15","5.15.0-1013.16","5.15.0-1014.17","5.15.0-1017.20","5.15.0-1019.24","5.15.0-1020.25","5.15.0-1021.26","5.15.0-1022.27","5.15.0-1023.29","5.15.0-1024.30","5.15.0-1029.36","5.15.0-1030.37","5.15.0-1031.38","5.15.0-1033.40","5.15.0-1034.41","5.15.0-1035.42","5.15.0-1036.43","5.15.0-1037.44","5.15.0-1038.45","5.15.0-1039.46","5.15.0-1040.47","5.15.0-1041.48","5.15.0-1042.49","5.15.0-1044.51","5.15.0-1045.52","5.15.0-1046.53","5.15.0-1047.54","5.15.0-1049.56","5.15.0-1050.57","5.15.0-1051.59","5.15.0-1052.60","5.15.0-1053.61","5.15.0-1054.62","5.15.0-1056.64","5.15.0-1057.65","5.15.0-1058.66","5.15.0-1059.67","5.15.0-1060.69","5.15.0-1061.70","5.15.0-1063.72","5.15.0-1064.73","5.15.0-1066.75","5.15.0-1067.76","5.15.0-1068.77","5.15.0-1070.79","5.15.0-1071.80","5.15.0-1072.81","5.15.0-1073.82","5.15.0-1074.83","5.15.0-1075.84","5.15.0-1078.87","5.15.0-1079.88","5.15.0-1081.90","5.15.0-1082.91","5.15.0-1084.93","5.15.0-1086.95","5.15.0-1087.96","5.15.0-1088.97","5.15.0-1089.98","5.15.0-1090.99","5.15.0-1091.100","5.15.0-1092.101","5.15.0-1094.103","5.15.0-1095.104","5.15.0-1096.105","5.15.0-1097.106","5.15.0-1098.107","5.15.0-1099.108","5.15.0-1101.110","5.15.0-1102.111","5.15.0-1103.112","5.15.0-1109.118","5.15.0-1110.119","5.15.0-1111.120","5.15.0-1114.123","5.15.0-1116.125","5.15.0-1117.126","5.15.0-1118.127","5.15.0-1119.128","5.15.0-1121.130","5.15.0-1122.131","5.15.0-1123.132","5.15.0-1125.134","5.15.0-1126.135"]},{"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-1025.30~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"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-azure-fde","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.15.0-1019.24.1","5.15.0-1024.30.1","5.15.0-1029.36.1","5.15.0-1030.37.1","5.15.0-1031.38.1","5.15.0-1033.40.1","5.15.0-1034.41.1","5.15.0-1035.42.1","5.15.0-1036.43.1","5.15.0-1037.44.1","5.15.0-1038.45.1","5.15.0-1039.46.1","5.15.0-1041.48.1","5.15.0-1042.49.1","5.15.0-1044.51.1","5.15.0-1045.52.1","5.15.0-1046.53.1","5.15.0-1047.54.1","5.15.0-1049.56.1","5.15.0-1050.57.1","5.15.0-1051.59.1","5.15.0-1052.60.1","5.15.0-1053.61.1","5.15.0-1054.62.1","5.15.0-1056.64.1","5.15.0-1057.65.1","5.15.0-1058.66.1","5.15.0-1059.67.1","5.15.0-1060.69.1","5.15.0-1061.70.1","5.15.0-1063.72.1","5.15.0-1064.73.1","5.15.0-1065.74.1","5.15.0-1067.76.1","5.15.0-1068.77.1","5.15.0-1070.79.1","5.15.0-1071.80.1","5.15.0-1072.81.1","5.15.0-1073.82.1","5.15.0-1076.85.1","5.15.0-1078.87.1","5.15.0-1081.90.1","5.15.0-1082.91.1","5.15.0-1084.93.1","5.15.0-1086.95.1","5.15.0-1087.96.1","5.15.0-1088.97.1","5.15.0-1089.98.1","5.15.0-1090.99.1","5.15.0-1091.100.1","5.15.0-1092.101.1","5.15.0-1094.103.1","5.15.0-1095.104.1","5.15.0-1096.105.1","5.15.0-1097.106.1","5.15.0-1098.107.1","5.15.0-1102.111.1","5.15.0-1109.118.1","5.15.0-1110.119.1","5.15.0-1111.120.1","5.15.0-1114.123","5.15.0-1116.125","5.15.0-1117.126","5.15.0-1118.127","5.15.0-1119.128","5.15.0-1120.129","5.15.0-1121.130","5.15.0-1122.131","5.15.0-1124.133","5.15.0-1125.134"]},{"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","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.13.0-1005.6","5.15.0-1001.3","5.15.0-1002.5","5.15.0-1003.6","5.15.0-1004.7","5.15.0-1005.8","5.15.0-1006.9","5.15.0-1008.12","5.15.0-1010.15","5.15.0-1013.18","5.15.0-1016.21","5.15.0-1017.23","5.15.0-1018.24","5.15.0-1019.25","5.15.0-1021.28","5.15.0-1022.29","5.15.0-1025.32","5.15.0-1026.33","5.15.0-1027.34","5.15.0-1029.36","5.15.0-1030.37","5.15.0-1031.38","5.15.0-1032.40","5.15.0-1034.42","5.15.0-1035.43","5.15.0-1036.44","5.15.0-1037.45","5.15.0-1038.46","5.15.0-1039.47","5.15.0-1040.48","5.15.0-1041.49","5.15.0-1042.50","5.15.0-1044.52","5.15.0-1045.53","5.15.0-1046.54","5.15.0-1047.55","5.15.0-1048.56","5.15.0-1049.57","5.15.0-1051.59","5.15.0-1052.60","5.15.0-1053.61","5.15.0-1054.62","5.15.0-1055.63","5.15.0-1058.66","5.15.0-1059.67","5.15.0-1060.68","5.15.0-1062.70","5.15.0-1063.71","5.15.0-1064.72","5.15.0-1065.73","5.15.0-1066.74","5.15.0-1067.75","5.15.0-1068.76","5.15.0-1069.77","5.15.0-1070.78","5.15.0-1071.79","5.15.0-1072.80","5.15.0-1073.81","5.15.0-1074.83","5.15.0-1075.84","5.15.0-1077.86","5.15.0-1078.87","5.15.0-1079.88","5.15.0-1080.89","5.15.0-1081.90","5.15.0-1082.91","5.15.0-1083.92","5.15.0-1084.93","5.15.0-1085.94","5.15.0-1086.95","5.15.0-1087.96","5.15.0-1088.97","5.15.0-1090.99","5.15.0-1091.100","5.15.0-1092.101","5.15.0-1093.102","5.15.0-1095.104","5.15.0-1096.105","5.15.0-1097.106","5.15.0-1098.107","5.15.0-1099.108","5.15.0-1100.109","5.15.0-1101.110","5.15.0-1103.112","5.15.0-1104.113","5.15.0-1105.114","5.15.0-1106.115","5.15.0-1108.117","5.15.0-1109.118","5.15.0-1111.121","5.15.0-1112.122","5.15.0-1114.124","5.15.0-1115.125","5.15.0-1117.127","5.15.0-1118.128","5.15.0-1120.130","5.15.0-1121.131"]},{"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-1024.26~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"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-gke","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.15.0-1002.2","5.15.0-1003.3","5.15.0-1004.5","5.15.0-1005.6","5.15.0-1006.7","5.15.0-1008.10","5.15.0-1010.13","5.15.0-1011.14","5.15.0-1014.17","5.15.0-1015.18","5.15.0-1016.19","5.15.0-1017.20","5.15.0-1019.23","5.15.0-1020.25","5.15.0-1023.28","5.15.0-1024.29","5.15.0-1027.32","5.15.0-1028.33","5.15.0-1030.35","5.15.0-1031.36","5.15.0-1032.37","5.15.0-1033.38","5.15.0-1034.39","5.15.0-1035.40","5.15.0-1036.41","5.15.0-1037.42","5.15.0-1038.43","5.15.0-1039.44","5.15.0-1040.45","5.15.0-1041.46","5.15.0-1042.47","5.15.0-1044.49","5.15.0-1045.50","5.15.0-1046.51","5.15.0-1047.52","5.15.0-1048.53","5.15.0-1049.54","5.15.0-1050.55","5.15.0-1051.56","5.15.0-1052.57","5.15.0-1053.58","5.15.0-1054.59","5.15.0-1057.62","5.15.0-1058.63","5.15.0-1059.64","5.15.0-1060.66","5.15.0-1061.67","5.15.0-1062.68","5.15.0-1063.69","5.15.0-1064.70","5.15.0-1065.71","5.15.0-1066.72","5.15.0-1067.73","5.15.0-1068.74","5.15.0-1069.75","5.15.0-1070.76","5.15.0-1071.77","5.15.0-1072.78","5.15.0-1073.79","5.15.0-1075.81","5.15.0-1076.82","5.15.0-1077.83","5.15.0-1078.84","5.15.0-1079.85","5.15.0-1080.86","5.15.0-1081.87","5.15.0-1082.88","5.15.0-1083.89","5.15.0-1084.90","5.15.0-1085.91","5.15.0-1086.92","5.15.0-1087.93","5.15.0-1088.94","5.15.0-1089.95","5.15.0-1090.96","5.15.0-1091.97","5.15.0-1092.98","5.15.0-1093.99","5.15.0-1094.100","5.15.0-1095.101","5.15.0-1096.102","5.15.0-1097.103","5.15.0-1099.105","5.15.0-1100.106","5.15.0-1101.107","5.15.0-1102.108","5.15.0-1104.110","5.15.0-1105.111","5.15.0-1107.113","5.15.0-1108.114","5.15.0-1110.116","5.15.0-1111.117","5.15.0-1112.118","5.15.0-1113.119","5.15.0-1115.121","5.15.0-1116.122"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-gkeop","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.15.0-1001.2","5.15.0-1002.4","5.15.0-1003.5","5.15.0-1004.6","5.15.0-1005.7","5.15.0-1007.10","5.15.0-1008.12","5.15.0-1011.15","5.15.0-1012.16","5.15.0-1013.17","5.15.0-1015.19","5.15.0-1016.21","5.15.0-1017.22","5.15.0-1018.23","5.15.0-1019.24","5.15.0-1020.25","5.15.0-1021.26","5.15.0-1022.27","5.15.0-1023.28","5.15.0-1024.29","5.15.0-1025.30","5.15.0-1026.31","5.15.0-1027.32","5.15.0-1028.33","5.15.0-1030.35","5.15.0-1031.37","5.15.0-1032.38","5.15.0-1033.39","5.15.0-1034.40","5.15.0-1035.41","5.15.0-1036.42","5.15.0-1037.43","5.15.0-1038.44","5.15.0-1039.45","5.15.0-1040.46","5.15.0-1043.50","5.15.0-1044.51","5.15.0-1045.52","5.15.0-1046.53","5.15.0-1047.54","5.15.0-1048.55","5.15.0-1049.56","5.15.0-1050.57","5.15.0-1051.58","5.15.0-1052.59","5.15.0-1053.60","5.15.0-1054.61","5.15.0-1055.62","5.15.0-1056.63","5.15.0-1057.64","5.15.0-1058.66","5.15.0-1059.67","5.15.0-1060.68","5.15.0-1061.69","5.15.0-1062.70","5.15.0-1063.71","5.15.0-1064.72","5.15.0-1065.73","5.15.0-1066.74","5.15.0-1067.75","5.15.0-1068.76","5.15.0-1069.77","5.15.0-1070.78","5.15.0-1071.79","5.15.0-1073.81","5.15.0-1074.82","5.15.0-1075.83","5.15.0-1076.84","5.15.0-1078.86","5.15.0-1079.87","5.15.0-1080.88","5.15.0-1081.89","5.15.0-1082.90","5.15.0-1083.91","5.15.0-1084.92","5.15.0-1086.94","5.15.0-1087.95","5.15.0-1088.96","5.15.0-1089.97","5.15.0-1091.99","5.15.0-1092.100","5.15.0-1094.102","5.15.0-1095.103","5.15.0-1096.104","5.15.0-1097.105","5.15.0-1098.106","5.15.0-1099.107","5.15.0-1100.108","5.15.0-1102.110","5.15.0-1103.111"]},{"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-57.59~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"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-ibm","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.15.0-1002.2","5.15.0-1003.3","5.15.0-1004.4","5.15.0-1005.5","5.15.0-1007.8","5.15.0-1009.11","5.15.0-1010.12","5.15.0-1012.14","5.15.0-1013.15","5.15.0-1015.17","5.15.0-1017.20","5.15.0-1018.21","5.15.0-1021.24","5.15.0-1022.25","5.15.0-1023.26","5.15.0-1025.28","5.15.0-1026.29","5.15.0-1027.30","5.15.0-1028.31","5.15.0-1029.32","5.15.0-1030.33","5.15.0-1031.34","5.15.0-1032.35","5.15.0-1033.36","5.15.0-1034.37","5.15.0-1035.38","5.15.0-1036.39","5.15.0-1037.40","5.15.0-1038.41","5.15.0-1040.43","5.15.0-1041.44","5.15.0-1042.45","5.15.0-1043.46","5.15.0-1044.47","5.15.0-1045.48","5.15.0-1046.49","5.15.0-1047.50","5.15.0-1048.51","5.15.0-1049.52","5.15.0-1050.53","5.15.0-1053.56","5.15.0-1054.57","5.15.0-1055.58","5.15.0-1056.59","5.15.0-1057.60","5.15.0-1058.61","5.15.0-1059.62","5.15.0-1060.63","5.15.0-1061.64","5.15.0-1062.65","5.15.0-1063.66","5.15.0-1064.67","5.15.0-1065.68","5.15.0-1066.69","5.15.0-1067.70","5.15.0-1068.71","5.15.0-1069.72","5.15.0-1070.73","5.15.0-1071.74","5.15.0-1072.75","5.15.0-1073.76","5.15.0-1074.77","5.15.0-1075.78","5.15.0-1076.79","5.15.0-1077.80","5.15.0-1078.81","5.15.0-1079.82","5.15.0-1080.83","5.15.0-1081.84","5.15.0-1084.87","5.15.0-1085.88","5.15.0-1086.89","5.15.0-1087.90","5.15.0-1089.92","5.15.0-1090.93","5.15.0-1091.94","5.15.0-1092.95","5.15.0-1093.96","5.15.0-1094.97","5.15.0-1095.98","5.15.0-1097.100","5.15.0-1098.101","5.15.0-1099.102","5.15.0-1100.103","5.15.0-1102.105","5.15.0-1103.106","5.15.0-1105.109","5.15.0-1106.110","5.15.0-1107.111","5.15.0-1108.112","5.15.0-1109.113","5.15.0-1110.114","5.15.0-1111.115","5.15.0-1113.117","5.15.0-1114.118"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-ibm-6.8","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1023.23~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"]},{"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-intel-iotg","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.15.0-1004.6","5.15.0-1008.11","5.15.0-1010.14","5.15.0-1013.17","5.15.0-1015.20","5.15.0-1016.21","5.15.0-1017.22","5.15.0-1018.23","5.15.0-1021.26","5.15.0-1023.28","5.15.0-1025.30","5.15.0-1026.31","5.15.0-1027.32","5.15.0-1028.33","5.15.0-1030.35","5.15.0-1031.36","5.15.0-1033.38","5.15.0-1034.39","5.15.0-1035.40","5.15.0-1036.41","5.15.0-1037.42","5.15.0-1038.43","5.15.0-1039.45","5.15.0-1040.46","5.15.0-1043.49","5.15.0-1045.51","5.15.0-1046.52","5.15.0-1047.53","5.15.0-1048.54","5.15.0-1049.55","5.15.0-1050.56","5.15.0-1051.57","5.15.0-1052.58","5.15.0-1055.61","5.15.0-1057.63","5.15.0-1058.64","5.15.0-1059.65","5.15.0-1060.66","5.15.0-1061.67","5.15.0-1062.68","5.15.0-1063.69","5.15.0-1064.70","5.15.0-1065.71","5.15.0-1066.72","5.15.0-1067.73","5.15.0-1071.77","5.15.0-1072.78","5.15.0-1073.79","5.15.0-1074.80","5.15.0-1075.81","5.15.0-1076.82","5.15.0-1077.83","5.15.0-1078.84","5.15.0-1079.85","5.15.0-1080.86","5.15.0-1081.87","5.15.0-1082.88","5.15.0-1083.89","5.15.0-1084.90","5.15.0-1085.91","5.15.0-1086.92","5.15.0-1087.93","5.15.0-1088.94","5.15.0-1090.96","5.15.0-1091.97","5.15.0-1092.98","5.15.0-1093.99","5.15.0-1094.100","5.15.0-1095.101","5.15.0-1096.102","5.15.0-1098.104","5.15.0-1099.105","5.15.0-1100.106","5.15.0-1101.107","5.15.0-1103.109","5.15.0-1104.110","5.15.0-1106.112","5.15.0-1107.113","5.15.0-1108.114","5.15.0-1109.115","5.15.0-1110.116","5.15.0-1111.117","5.15.0-1112.118","5.15.0-1114.120","5.15.0-1115.121"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-kvm","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-1002.2","5.15.0-1004.4","5.15.0-1005.5","5.15.0-1007.7","5.15.0-1008.8","5.15.0-1010.11","5.15.0-1012.14","5.15.0-1013.16","5.15.0-1016.19","5.15.0-1017.21","5.15.0-1018.22","5.15.0-1019.23","5.15.0-1020.24","5.15.0-1021.26","5.15.0-1024.29","5.15.0-1025.30","5.15.0-1026.31","5.15.0-1028.33","5.15.0-1029.34","5.15.0-1030.35","5.15.0-1031.36","5.15.0-1032.37","5.15.0-1033.38","5.15.0-1034.39","5.15.0-1035.40","5.15.0-1037.42","5.15.0-1038.43","5.15.0-1039.44","5.15.0-1040.45","5.15.0-1041.46","5.15.0-1042.47","5.15.0-1044.49","5.15.0-1045.50","5.15.0-1046.51","5.15.0-1047.52","5.15.0-1048.53","5.15.0-1049.54","5.15.0-1050.55","5.15.0-1051.56","5.15.0-1052.57","5.15.0-1053.58","5.15.0-1054.59","5.15.0-1057.62","5.15.0-1058.63","5.15.0-1059.64","5.15.0-1060.65","5.15.0-1061.66","5.15.0-1062.67","5.15.0-1063.68","5.15.0-1064.69","5.15.0-1065.70","5.15.0-1066.71","5.15.0-1067.72","5.15.0-1068.73","5.15.0-1069.74","5.15.0-1070.75","5.15.0-1071.76","5.15.0-1072.77","5.15.0-1073.78","5.15.0-1076.81","5.15.0-1077.82","5.15.0-1078.83","5.15.0-1079.84","5.15.0-1080.85","5.15.0-1081.86","5.15.0-1082.87","5.15.0-1083.88","5.15.0-1084.89","5.15.0-1085.90","5.15.0-1086.91","5.15.0-1087.92","5.15.0-1088.93","5.15.0-1089.94","5.15.0-1090.95","5.15.0-1091.96","5.15.0-1092.97","5.15.0-1093.98","5.15.0-1095.100","5.15.0-1096.101","5.15.0-1097.102","5.15.0-1098.103","5.15.0-1100.105","5.15.0-1101.106","5.15.0-1103.108","5.15.0-1104.109","5.15.0-1105.110","5.15.0-1106.111","5.15.0-1107.112","5.15.0-1108.113","5.15.0-1109.114","5.15.0-1111.116","5.15.0-1112.117"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-lowlatency","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.15.0-22.22","5.15.0-23.23","5.15.0-24.24","5.15.0-27.28","5.15.0-30.31","5.15.0-33.34","5.15.0-35.36","5.15.0-37.39","5.15.0-39.42","5.15.0-40.43","5.15.0-41.44","5.15.0-43.46","5.15.0-46.49","5.15.0-47.53","5.15.0-48.54","5.15.0-50.56","5.15.0-52.58","5.15.0-53.59","5.15.0-56.62","5.15.0-57.63","5.15.0-58.64","5.15.0-60.66","5.15.0-67.74","5.15.0-69.76","5.15.0-70.77","5.15.0-71.78","5.15.0-72.79","5.15.0-73.80","5.15.0-75.82","5.15.0-76.83","5.15.0-78.85","5.15.0-79.88","5.15.0-82.91","5.15.0-83.92","5.15.0-84.93","5.15.0-86.95","5.15.0-87.96","5.15.0-88.98","5.15.0-89.99","5.15.0-91.101","5.15.0-92.102","5.15.0-94.104","5.15.0-97.107","5.15.0-100.110","5.15.0-101.111","5.15.0-102.112","5.15.0-105.115","5.15.0-106.116","5.15.0-107.117","5.15.0-110.120","5.15.0-113.123","5.15.0-116.126","5.15.0-117.127","5.15.0-118.128","5.15.0-119.129","5.15.0-121.131","5.15.0-122.132","5.15.0-124.134","5.15.0-125.135","5.15.0-126.136","5.15.0-127.137","5.15.0-128.138","5.15.0-129.139","5.15.0-131.141","5.15.0-133.143","5.15.0-134.145","5.15.0-135.146","5.15.0-136.147","5.15.0-138.148","5.15.0-139.149","5.15.0-140.150","5.15.0-141.151","5.15.0-142.152","5.15.0-143.153","5.15.0-144.157","5.15.0-145.158","5.15.0-152.162","5.15.0-153.163","5.15.0-156.166","5.15.0-157.167","5.15.0-160.170","5.15.0-161.171","5.15.0-163.173","5.15.0-164.174","5.15.0-168.178","5.15.0-170.180","5.15.0-171.181","5.15.0-173.183","5.15.0-174.184","5.15.0-175.185","5.15.0-177.187","5.15.0-178.188","5.15.0-179.189","5.15.0-181.191","5.15.0-183.193","5.15.0-184.194","5.15.0-190.200","5.15.0-191.201","5.15.0-194.204","5.15.0-195.205","5.15.0-197.207","5.15.0-198.208"]},{"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-54.56.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"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-nvidia","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.15.0-1005.5","5.15.0-1007.7","5.15.0-1010.10","5.15.0-1015.15","5.15.0-1017.17","5.15.0-1018.18","5.15.0-1023.23","5.15.0-1025.25","5.15.0-1026.26","5.15.0-1027.27","5.15.0-1028.28","5.15.0-1029.29","5.15.0-1030.30","5.15.0-1031.31","5.15.0-1032.32","5.15.0-1033.33","5.15.0-1037.37","5.15.0-1039.39","5.15.0-1040.40","5.15.0-1041.41","5.15.0-1042.42","5.15.0-1043.43","5.15.0-1044.44","5.15.0-1045.45","5.15.0-1046.46","5.15.0-1047.47","5.15.0-1048.48","5.15.0-1053.54","5.15.0-1054.55","5.15.0-1055.56","5.15.0-1058.59","5.15.0-1059.60","5.15.0-1060.61","5.15.0-1061.62","5.15.0-1062.63","5.15.0-1063.64","5.15.0-1064.65","5.15.0-1065.66","5.15.0-1066.67","5.15.0-1067.68","5.15.0-1068.69","5.15.0-1069.70","5.15.0-1070.71","5.15.0-1071.72","5.15.0-1072.73","5.15.0-1073.74","5.15.0-1074.75","5.15.0-1075.76","5.15.0-1076.77","5.15.0-1077.78","5.15.0-1078.79","5.15.0-1079.80","5.15.0-1080.81","5.15.0-1081.82","5.15.0-1082.83","5.15.0-1083.84","5.15.0-1085.86","5.15.0-1086.87","5.15.0-1087.88","5.15.0-1088.89","5.15.0-1090.91","5.15.0-1091.92","5.15.0-1092.93","5.15.0-1093.94","5.15.0-1094.95","5.15.0-1095.96","5.15.0-1096.97","5.15.0-1098.99","5.15.0-1099.100","5.15.0-1100.101","5.15.0-1101.102","5.15.0-1103.104","5.15.0-1104.105","5.15.0-1106.107","5.15.0-1107.108","5.15.0-1108.109","5.15.0-1109.110","5.15.0-1110.111","5.15.0-1111.112","5.15.0-1112.113","5.15.0-1114.115","5.15.0-1115.116"]},{"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-1022.25~22.04.2"}]}],"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"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-nvidia-tegra","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.15.0-1009.9","5.15.0-1010.10","5.15.0-1012.12","5.15.0-1013.13","5.15.0-1014.14","5.15.0-1015.15","5.15.0-1016.16","5.15.0-1017.17","5.15.0-1018.18","5.15.0-1019.19","5.15.0-1020.20","5.15.0-1021.21","5.15.0-1022.22","5.15.0-1025.25","5.15.0-1026.26","5.15.0-1027.27","5.15.0-1028.28","5.15.0-1030.30","5.15.0-1032.32","5.15.0-1033.33","5.15.0-1034.34","5.15.0-1035.35","5.15.0-1036.36","5.15.0-1037.37","5.15.0-1038.38","5.15.0-1039.39","5.15.0-1040.40","5.15.0-1041.41","5.15.0-1042.42","5.15.0-1043.43","5.15.0-1044.44","5.15.0-1045.45","5.15.0-1046.46","5.15.0-1047.47","5.15.0-1048.48","5.15.0-1049.49","5.15.0-1050.50","5.15.0-1051.51","5.15.0-1052.52","5.15.0-1053.53","5.15.0-1055.55","5.15.0-1056.56","5.15.0-1057.57","5.15.0-1058.58","5.15.0-1060.60","5.15.0-1061.61","5.15.0-1063.63","5.15.0-1064.66","5.15.0-1065.67","5.15.0-1066.68","5.15.0-1067.69","5.15.0-1068.70","5.15.0-1070.72","5.15.0-1071.73"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-nvidia-tegra-igx","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.15.0-1001.1","5.15.0-1002.2","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-1009.9","5.15.0-1012.12","5.15.0-1013.13","5.15.0-1015.15","5.15.0-1016.16","5.15.0-1018.18","5.15.0-1019.19","5.15.0-1020.20","5.15.0-1021.21","5.15.0-1022.22","5.15.0-1023.23","5.15.0-1024.24","5.15.0-1026.26","5.15.0-1027.27","5.15.0-1028.28","5.15.0-1029.29","5.15.0-1030.30","5.15.0-1031.31","5.15.0-1032.32","5.15.0-1033.33","5.15.0-1034.34","5.15.0-1035.35","5.15.0-1036.36","5.15.0-1037.37","5.15.0-1038.38","5.15.0-1039.39","5.15.0-1040.40","5.15.0-1041.41","5.15.0-1042.42","5.15.0-1044.44","5.15.0-1045.45","5.15.0-1046.46","5.15.0-1047.47","5.15.0-1049.49","5.15.0-1050.50","5.15.0-1052.52","5.15.0-1053.53","5.15.0-1054.54","5.15.0-1055.55","5.15.0-1056.56","5.15.0-1057.57","5.15.0-1059.59"]},{"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","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.13.0-1008.10","5.15.0-1001.3","5.15.0-1002.4","5.15.0-1003.5","5.15.0-1006.8","5.15.0-1007.9","5.15.0-1009.12","5.15.0-1011.15","5.15.0-1013.17","5.15.0-1016.20","5.15.0-1017.22","5.15.0-1018.23","5.15.0-1019.24","5.15.0-1021.27","5.15.0-1022.28","5.15.0-1025.31","5.15.0-1026.32","5.15.0-1027.33","5.15.0-1029.35","5.15.0-1030.36","5.15.0-1032.38","5.15.0-1033.39","5.15.0-1034.40","5.15.0-1035.41","5.15.0-1036.42","5.15.0-1037.43","5.15.0-1038.44","5.15.0-1039.45","5.15.0-1040.46","5.15.0-1041.47","5.15.0-1042.48","5.15.0-1044.50","5.15.0-1045.51","5.15.0-1046.52","5.15.0-1047.53","5.15.0-1048.54","5.15.0-1049.55","5.15.0-1050.56","5.15.0-1051.57","5.15.0-1052.58","5.15.0-1053.59","5.15.0-1054.60","5.15.0-1055.61","5.15.0-1058.64","5.15.0-1059.65","5.15.0-1060.66","5.15.0-1061.67","5.15.0-1062.68","5.15.0-1063.69","5.15.0-1064.70","5.15.0-1065.71","5.15.0-1066.72","5.15.0-1067.73","5.15.0-1068.74","5.15.0-1069.75","5.15.0-1070.76","5.15.0-1071.77","5.15.0-1072.78","5.15.0-1073.79","5.15.0-1074.80","5.15.0-1075.81","5.15.0-1076.82","5.15.0-1077.83","5.15.0-1078.84","5.15.0-1079.85","5.15.0-1080.86","5.15.0-1081.87","5.15.0-1082.88","5.15.0-1083.89","5.15.0-1084.90","5.15.0-1085.91","5.15.0-1086.92","5.15.0-1088.94","5.15.0-1089.95","5.15.0-1090.96","5.15.0-1091.97","5.15.0-1092.98","5.15.0-1093.99","5.15.0-1094.100","5.15.0-1095.101","5.15.0-1096.102","5.15.0-1097.103","5.15.0-1098.104","5.15.0-1100.106","5.15.0-1101.107","5.15.0-1102.108","5.15.0-1103.109","5.15.0-1105.111","5.15.0-1106.112","5.15.0-1108.114","5.15.0-1109.115","5.15.0-1110.116","5.15.0-1111.117","5.15.0-1112.118","5.15.0-1113.119","5.15.0-1114.120","5.15.0-1116.122","5.15.0-1117.123"]},{"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-1020.21~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"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-raspi","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.13.0-1008.9","5.15.0-1002.2","5.15.0-1003.3","5.15.0-1004.4","5.15.0-1005.5","5.15.0-1006.6","5.15.0-1008.8","5.15.0-1011.13","5.15.0-1012.14","5.15.0-1013.15","5.15.0-1014.16","5.15.0-1015.17","5.15.0-1016.18","5.15.0-1017.19","5.15.0-1018.20","5.15.0-1021.23","5.15.0-1022.24","5.15.0-1023.25","5.15.0-1024.26","5.15.0-1025.27","5.15.0-1026.28","5.15.0-1027.29","5.15.0-1028.30","5.15.0-1029.31","5.15.0-1030.32","5.15.0-1032.35","5.15.0-1033.36","5.15.0-1034.37","5.15.0-1035.38","5.15.0-1036.39","5.15.0-1037.40","5.15.0-1038.41","5.15.0-1040.43","5.15.0-1041.44","5.15.0-1042.45","5.15.0-1043.46","5.15.0-1044.47","5.15.0-1045.48","5.15.0-1046.49","5.15.0-1047.50","5.15.0-1048.51","5.15.0-1049.52","5.15.0-1050.53","5.15.0-1053.56","5.15.0-1054.57","5.15.0-1055.58","5.15.0-1058.61","5.15.0-1059.62","5.15.0-1060.63","5.15.0-1061.64","5.15.0-1062.65","5.15.0-1063.66","5.15.0-1064.67","5.15.0-1065.68","5.15.0-1066.69","5.15.0-1067.70","5.15.0-1070.73","5.15.0-1071.74","5.15.0-1072.75","5.15.0-1073.76","5.15.0-1074.77","5.15.0-1075.78","5.15.0-1076.79","5.15.0-1077.80","5.15.0-1078.81","5.15.0-1079.82","5.15.0-1080.83","5.15.0-1083.86","5.15.0-1084.87","5.15.0-1085.88","5.15.0-1086.89","5.15.0-1087.90","5.15.0-1089.92","5.15.0-1090.93","5.15.0-1091.94","5.15.0-1092.95","5.15.0-1093.96","5.15.0-1097.100","5.15.0-1098.101","5.15.0-1099.102","5.15.0-1100.103","5.15.0-1102.105","5.15.0-1103.106","5.15.0-1105.108","5.15.0-1106.109","5.15.0-1108.111","5.15.0-1110.113","5.15.0-1113.116"]},{"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-53.55.1~22.04.1"}]}],"versions":["6.8.0-38.38.1~22.04.1","6.8.0-39.39.1~22.04.1","6.8.0-40.40.1~22.04.1","6.8.0-41.41.1~22.04.1","6.8.0-44.44.1~22.04.1","6.8.0-47.47.1~22.04.1","6.8.0-48.48.1~22.04.2","6.8.0-49.49.1~22.04.1","6.8.0-50.51.1~22.04.1","6.8.0-51.52.1~22.04.1","6.8.0-52.53.1~22.04.1"]},{"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:22.04:LTS","package":"linux-xilinx-zynqmp","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.15.0-1022.26","5.15.0-1023.27","5.15.0-1025.29","5.15.0-1027.31","5.15.0-1030.34","5.15.0-1031.35","5.15.0-1035.39","5.15.0-1036.40","5.15.0-1037.41","5.15.0-1038.42","5.15.0-1039.43","5.15.0-1041.45","5.15.0-1044.48","5.15.0-1046.50","5.15.0-1050.54","5.15.0-1051.55","5.15.0-1052.56","5.15.0-1053.57","5.15.0-1054.58","5.15.0-1055.59","5.15.0-1056.60","5.15.0-1057.61","5.15.0-1059.63","5.15.0-1060.64","5.15.0-1061.65","5.15.0-1062.66","5.15.0-1063.67","5.15.0-1064.68","5.15.0-1065.69","5.15.0-1067.71","5.15.0-1068.72","5.15.0-1069.73","5.15.0-1070.74","5.15.0-1074.78","5.15.0-1075.79","5.15.0-1076.80","5.15.0-1077.81","5.15.0-1078.82","5.15.0-1079.83","5.15.0-1080.84"]},{"source":"osv","ecosystem":"Ubuntu:Nvidia-BlueField:22.04:LTS","package":"linux-bluefield","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.15.0-1011.13","5.15.0-1014.16","5.15.0-1015.17","5.15.0-1017.19","5.15.0-1019.21","5.15.0-1021.23","5.15.0-1022.24","5.15.0-1023.25","5.15.0-1024.26","5.15.0-1027.29","5.15.0-1028.30","5.15.0-1031.33","5.15.0-1032.34","5.15.0-1033.35","5.15.0-1035.37","5.15.0-1036.38","5.15.0-1037.39","5.15.0-1038.40","5.15.0-1040.42","5.15.0-1042.44","5.15.0-1043.45","5.15.0-1044.46","5.15.0-1045.47","5.15.0-1047.49","5.15.0-1048.50","5.15.0-1050.52","5.15.0-1051.53","5.15.0-1052.54","5.15.0-1053.55","5.15.0-1054.56","5.15.0-1056.58","5.15.0-1057.59","5.15.0-1058.60","5.15.0-1059.61","5.15.0-1060.62","5.15.0-1061.63","5.15.0-1062.64","5.15.0-1063.65","5.15.0-1064.66","5.15.0-1065.67","5.15.0-1066.68","5.15.0-1067.69","5.15.0-1069.71","5.15.0-1070.72","5.15.0-1072.74","5.15.0-1074.76","5.15.0-1075.77","5.15.0-1076.78","5.15.0-1077.79","5.15.0-1079.81","5.15.0-1080.82","5.15.0-1081.83","5.15.0-1082.84","5.15.0-1083.85","5.15.0-1084.86","5.15.0-1085.87","5.15.0-1086.88","5.15.0-1087.89","5.15.0-1089.91","5.15.0-1090.92","5.15.0-1092.94","5.15.0-1093.95","5.15.0-1095.97","5.15.0-1096.98","5.15.0-1097.99","5.15.0-1098.100","5.15.0-1099.101","5.15.0-1100.102","5.15.0-1101.103","5.15.0-1103.105","5.15.0-1104.106"]},{"source":"osv","ecosystem":"Ubuntu:Pro:Realtime:22.04:LTS","package":"linux-intel-iot-realtime","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.15.0-1021.26","5.15.0-1022.27","5.15.0-1023.28","5.15.0-1024.29","5.15.0-1028.33","5.15.0-1033.35","5.15.0-1034.36","5.15.0-1035.37","5.15.0-1036.38","5.15.0-1037.39","5.15.0-1038.40","5.15.0-1039.41","5.15.0-1040.42","5.15.0-1041.43","5.15.0-1042.44","5.15.0-1043.45","5.15.0-1044.46","5.15.0-1046.48","5.15.0-1047.49","5.15.0-1048.50","5.15.0-1049.51","5.15.0-1050.52","5.15.0-1053.55","5.15.0-1054.56","5.15.0-1055.57","5.15.0-1056.58","5.15.0-1057.59","5.15.0-1058.60","5.15.0-1059.61","5.15.0-1060.62","5.15.0-1061.63","5.15.0-1063.65","5.15.0-1064.66","5.15.0-1066.68","5.15.0-1071.73","5.15.0-1072.74","5.15.0-1073.75","5.15.0-1074.76","5.15.0-1075.77","5.15.0-1076.78","5.15.0-1077.79","5.15.0-1078.80","5.15.0-1079.81","5.15.0-1080.82","5.15.0-1081.83","5.15.0-1082.84","5.15.0-1083.85","5.15.0-1084.86","5.15.0-1085.87","5.15.0-1086.88","5.15.0-1087.89","5.15.0-1088.90","5.15.0-1089.91","5.15.0-1090.92","5.15.0-1091.93","5.15.0-1092.94","5.15.0-1093.95","5.15.0-1094.96","5.15.0-1096.98","5.15.0-1097.99","5.15.0-1098.100","5.15.0-1099.101","5.15.0-1100.102","5.15.0-1101.103","5.15.0-1103.105","5.15.0-1104.106","5.15.0-1105.107","5.15.0-1106.108","5.15.0-1107.109","5.15.0-1108.110","5.15.0-1109.111","5.15.0-1111.115","5.15.0-1112.116"]},{"source":"osv","ecosystem":"Ubuntu:Pro:Realtime:22.04:LTS","package":"linux-realtime","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.15.0-1006.6","5.15.0-1007.7","5.15.0-1009.9","5.15.0-1011.11","5.15.0-1014.14","5.15.0-1015.15","5.15.0-1016.16","5.15.0-1019.19","5.15.0-1020.20","5.15.0-1021.21","5.15.0-1022.22","5.15.0-1024.25","5.15.0-1025.28","5.15.0-1028.31","5.15.0-1029.32","5.15.0-1030.33","5.15.0-1032.35","5.15.0-1033.36","5.15.0-1034.37","5.15.0-1036.39","5.15.0-1037.40","5.15.0-1038.41","5.15.0-1039.42","5.15.0-1040.45","5.15.0-1041.46","5.15.0-1042.47","5.15.0-1043.48","5.15.0-1044.49","5.15.0-1045.50","5.15.0-1046.52","5.15.0-1048.54","5.15.0-1049.55","5.15.0-1050.56","5.15.0-1051.57","5.15.0-1052.58","5.15.0-1053.59","5.15.0-1054.60","5.15.0-1055.62","5.15.0-1056.63","5.15.0-1057.64","5.15.0-1058.66","5.15.0-1061.69","5.15.0-1062.70","5.15.0-1063.71","5.15.0-1064.72","5.15.0-1065.73","5.15.0-1066.74","5.15.0-1067.75","5.15.0-1068.76","5.15.0-1069.77","5.15.0-1070.78","5.15.0-1071.79","5.15.0-1072.80","5.15.0-1073.81","5.15.0-1074.82","5.15.0-1075.83","5.15.0-1076.84","5.15.0-1077.85","5.15.0-1078.86","5.15.0-1079.87","5.15.0-1080.88","5.15.0-1081.89","5.15.0-1082.91","5.15.0-1083.92","5.15.0-1084.93","5.15.0-1085.94","5.15.0-1086.95","5.15.0-1087.96","5.15.0-1088.97","5.15.0-1089.98","5.15.0-1090.99","5.15.0-1091.100","5.15.0-1092.101","5.15.0-1093.102","5.15.0-1094.103","5.15.0-1095.104","5.15.0-1096.105","5.15.0-1097.106","5.15.0-1098.107","5.15.0-1099.108","5.15.0-1100.109","5.15.0-1102.111","5.15.0-1103.112","5.15.0-1104.113","5.15.0-1105.114","5.15.0-1107.116","5.15.0-1108.117","5.15.0-1110.119","5.15.0-1111.120","5.15.0-1112.121","5.15.0-1113.122","5.15.0-1114.123","5.15.0-1115.124","5.15.0-1116.125","5.15.0-1118.127","5.15.0-1119.128"]},{"source":"osv","ecosystem":"Ubuntu:Pro:Realtime:22.04:LTS","package":"linux-realtime-6.8","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.1-1016.17~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"]},{"source":"osv","ecosystem":"Ubuntu:Pro:FIPS-preview:22.04:LTS","package":"linux-aws-fips","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.15.0-1042.47+fips1","5.15.0-1051.56+fips1"]},{"source":"osv","ecosystem":"Ubuntu:Pro:FIPS-preview:22.04:LTS","package":"linux-azure-fips","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.15.0-1053.61+fips1"]},{"source":"osv","ecosystem":"Ubuntu:Pro:FIPS-preview:22.04:LTS","package":"linux-fips","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.15.0-73.80+fips1"]},{"source":"osv","ecosystem":"Ubuntu:Pro:FIPS-preview:22.04:LTS","package":"linux-gcp-fips","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.15.0-1048.56+fips1"]},{"source":"osv","ecosystem":"Ubuntu:Pro:FIPS-updates:22.04:LTS","package":"linux-aws-fips","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.15.0-1051.56+fips1","5.15.0-1052.57+fips1","5.15.0-1053.58+fips1","5.15.0-1055.60+fips1","5.15.0-1056.61+fips1","5.15.0-1057.63+fips1","5.15.0-1060.66+fips1","5.15.0-1061.67+fips1","5.15.0-1062.68+fips1","5.15.0-1063.69+fips1","5.15.0-1064.70+fips1","5.15.0-1065.71+fips1","5.15.0-1066.72+fips1","5.15.0-1067.73+fips1","5.15.0-1068.74+fips1","5.15.0-1069.75+fips1","5.15.0-1070.76+fips1","5.15.0-1071.77+fips1","5.15.0-1072.78+fips1","5.15.0-1073.79+fips1","5.15.0-1076.83+fips1","5.15.0-1077.84+fips1","5.15.0-1078.85+fips1","5.15.0-1079.86+fips1","5.15.0-1080.87+fips1","5.15.0-1081.88+fips1","5.15.0-1082.89+fips1","5.15.0-1083.90+fips1","5.15.0-1084.91+fips1","5.15.0-1085.92+fips1","5.15.0-1086.93+fips1","5.15.0-1087.94+fips1","5.15.0-1088.95+fips1","5.15.0-1089.96+fips1","5.15.0-1090.97+fips1","5.15.0-1091.98+fips1","5.15.0-1092.99+fips1","5.15.0-1093.100+fips1","5.15.0-1095.102+fips1","5.15.0-1096.103+fips1","5.15.0-1097.104+fips1","5.15.0-1098.105+fips1","5.15.0-1099.106+fips1","5.15.0-1100.107+fips1","5.15.0-1101.108+fips1","5.15.0-1103.110+fips1","5.15.0-1104.111+fips1","5.15.0-1105.112+fips1","5.15.0-1106.113+fips1","5.15.0-1108.115+fips1","5.15.0-1109.116+fips1","5.15.0-1111.118+fips1","5.15.0-1112.119+fips1","5.15.0-1113.120+fips1","5.15.0-1114.121+fips1","5.15.0-1115.122+fips1","5.15.0-1116.123+fips1","5.15.0-1117.124+fips1","5.15.0-1119.126+fips1","5.15.0-1120.127+fips1"]},{"source":"osv","ecosystem":"Ubuntu:Pro:FIPS-updates:22.04:LTS","package":"linux-azure-fips","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.15.0-1053.61+fips1","5.15.0-1058.66+fips1","5.15.0-1059.67+fips1","5.15.0-1060.69+fips1","5.15.0-1061.70+fips1","5.15.0-1063.72+fips1","5.15.0-1064.73+fips1","5.15.0-1065.74+fips1","5.15.0-1067.76+fips1","5.15.0-1068.77+fips1","5.15.0-1070.79+fips1","5.15.0-1071.80+fips1","5.15.0-1072.81+fips1","5.15.0-1073.82+fips1","5.15.0-1074.83+fips1","5.15.0-1075.84+fips1","5.15.0-1078.87+fips1","5.15.0-1079.88+fips1","5.15.0-1080.89+fips1","5.15.0-1082.91+fips1","5.15.0-1083.92+fips1","5.15.0-1085.94+fips1","5.15.0-1087.96+fips1","5.15.0-1088.97+fips1","5.15.0-1089.98+fips1","5.15.0-1090.99+fips1","5.15.0-1091.100+fips1","5.15.0-1094.103+fips1","5.15.0-1095.104+fips1","5.15.0-1096.105+fips1","5.15.0-1097.106+fips1","5.15.0-1098.107+fips1","5.15.0-1101.110+fips1","5.15.0-1102.111+fips1","5.15.0-1103.112+fips1","5.15.0-1109.118+fips1","5.15.0-1110.119+fips1","5.15.0-1111.120+fips1","5.15.0-1114.123+fips1","5.15.0-1116.125+fips1","5.15.0-1117.126+fips1","5.15.0-1118.127+fips1","5.15.0-1119.128+fips1","5.15.0-1121.130+fips1","5.15.0-1122.131+fips1","5.15.0-1123.132+fips1","5.15.0-1125.134+fips1","5.15.0-1126.135+fips1"]},{"source":"osv","ecosystem":"Ubuntu:Pro:FIPS-updates:22.04:LTS","package":"linux-fips","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.15.0-73.80+fips1","5.15.0-92.102+fips1","5.15.0-94.104+fips1","5.15.0-97.107+fips1","5.15.0-100.110+fips1","5.15.0-101.111+fips1","5.15.0-102.112+fips1","5.15.0-105.115+fips1","5.15.0-106.116+fips1","5.15.0-107.117+fips1","5.15.0-111.121+fips1","5.15.0-113.123+fips1","5.15.0-115.125+fips1","5.15.0-117.127+fips1","5.15.0-118.128+fips1","5.15.0-119.129+fips1","5.15.0-121.131+fips1","5.15.0-122.132+fips1","5.15.0-124.134+fips1","5.15.0-125.135+fips1","5.15.0-127.137+fips1","5.15.0-128.138+fips1","5.15.0-130.140+fips1","5.15.0-131.141+fips1","5.15.0-133.144+fips1","5.15.0-134.145+fips1","5.15.0-135.146+fips1","5.15.0-136.147+fips1","5.15.0-138.148+fips1","5.15.0-139.149+fips1","5.15.0-140.150+fips1","5.15.0-141.151+fips1","5.15.0-142.152+fips1","5.15.0-143.153+fips1","5.15.0-144.157+fips1","5.15.0-145.158+fips1","5.15.0-152.162+fips1","5.15.0-153.163+fips1","5.15.0-156.166+fips1","5.15.0-157.167+fips1","5.15.0-160.170+fips1","5.15.0-161.171+fips1","5.15.0-163.173+fips1","5.15.0-164.174+fips1","5.15.0-168.178+fips1","5.15.0-170.180+fips1","5.15.0-171.181+fips1","5.15.0-173.183+fips1","5.15.0-174.184+fips1","5.15.0-176.186+fips1","5.15.0-177.187+fips1","5.15.0-179.189+fips1","5.15.0-181.191+fips1","5.15.0-185.195+fips1","5.15.0-186.196+fips1","5.15.0-190.200+fips1","5.15.0-191.201+fips1","5.15.0-194.204+fips1","5.15.0-198.208+fips1","5.15.0-202.212+fips1"]},{"source":"osv","ecosystem":"Ubuntu:Pro:FIPS-updates:22.04:LTS","package":"linux-gcp-fips","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.15.0-1048.56+fips1","5.15.0-1055.63+fips2","5.15.0-1058.66+fips1","5.15.0-1059.67+fips1","5.15.0-1060.68+fips1","5.15.0-1062.70+fips1","5.15.0-1063.71+fips1","5.15.0-1064.72+fips1","5.15.0-1065.73+fips1","5.15.0-1066.74+fips1","5.15.0-1067.75+fips1","5.15.0-1068.76+fips1","5.15.0-1069.77+fips1","5.15.0-1070.78+fips1","5.15.0-1071.79+fips1","5.15.0-1072.80+fips1","5.15.0-1073.81+fips1","5.15.0-1074.83+fips1","5.15.0-1075.84+fips1","5.15.0-1077.86+fips1","5.15.0-1078.87+fips1","5.15.0-1079.88+fips1","5.15.0-1080.89+fips1","5.15.0-1081.90+fips1","5.15.0-1082.91+fips1","5.15.0-1083.92+fips1","5.15.0-1084.93+fips1","5.15.0-1085.94+fips1","5.15.0-1086.95+fips1","5.15.0-1087.96+fips1","5.15.0-1088.97+fips1","5.15.0-1090.99+fips1","5.15.0-1091.100+fips1","5.15.0-1092.101+fips1","5.15.0-1093.102+fips1","5.15.0-1095.104+fips1","5.15.0-1096.105+fips1","5.15.0-1097.106+fips1","5.15.0-1098.107+fips1","5.15.0-1099.108+fips1","5.15.0-1100.109+fips1","5.15.0-1101.110+fips1","5.15.0-1103.112+fips1","5.15.0-1104.113+fips1","5.15.0-1105.114+fips1","5.15.0-1106.115+fips1","5.15.0-1108.117+fips1","5.15.0-1109.118+fips1","5.15.0-1111.121+fips1","5.15.0-1112.122+fips1","5.15.0-1114.124+fips1","5.15.0-1115.125+fips1","5.15.0-1116.126+fips1","5.15.0-1118.128+fips1","5.15.0-1120.130+fips1","5.15.0-1121.131+fips1"]},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-54.56"}]}],"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"]},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-aws","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1023.25"}]}],"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"]},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-azure","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1025.30"}]}],"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"]},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-azure-6.11","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.11.0-1012.12~24.04.1"}]}],"versions":["6.11.0-1008.8~24.04.1"]},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-azure-nvidia","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1014.15"}]}],"versions":["6.8.0-1013.14"]},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-gcp","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1024.26"}]}],"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"]},{"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-1019.23"}]}],"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"]},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-gkeop","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1006.8"}]}],"versions":["6.8.0-1001.3","6.8.0-1002.4","6.8.0-1003.5","6.8.0-1004.6"]},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-ibm","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1022.22"}]}],"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"]},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-lowlatency","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-54.56.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"]},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-nvidia","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1022.25"}]}],"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"]},{"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-1022.25.2"}]}],"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"]},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-oem-6.11","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.11.0-1015.15"}]}],"versions":["6.11.0-1007.7","6.11.0-1008.8","6.11.0-1009.9","6.11.0-1010.10","6.11.0-1011.11","6.11.0-1012.12","6.11.0-1013.13"]},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-oem-6.8","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1024.24"}]}],"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"]},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-oracle","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1020.21"}]}],"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"]},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-raspi","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1019.23"}]}],"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"]},{"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-53.55.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"]},{"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-2018.19"}]}],"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"]},{"source":"osv","ecosystem":"Ubuntu:Pro:Realtime:24.04:LTS","package":"linux-realtime","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.1-1016.17"}]}],"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"]},{"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:26.04:LTS","package":"linux-vmware","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["7.0.0-1006.6"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-lowlatency-hwe-6.8","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-54.56.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"],"bundled":209},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-54.56"}]}],"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"],"bundled":209},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-lowlatency","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-54.56.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"],"bundled":209},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-nvidia-6.8","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1022.25~22.04.2"}]}],"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"],"bundled":208},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-nvidia","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1022.25"}]}],"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"],"bundled":208},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-nvidia-lowlatency","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1022.25.2"}]}],"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"],"bundled":208},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-oracle-6.8","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1020.21~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"],"bundled":208},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-oracle","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1020.21"}]}],"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"],"bundled":208},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-gcp-6.8","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1024.26~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"],"bundled":208},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-raspi","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1019.23"}]}],"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"],"bundled":208},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-gcp","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1024.26"}]}],"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"],"bundled":210},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-gke","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1019.23"}]}],"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"],"bundled":210},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-gkeop","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1006.8"}]}],"versions":["6.8.0-1001.3","6.8.0-1002.4","6.8.0-1003.5","6.8.0-1004.6"],"bundled":210},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-oem-6.11","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.11.0-1015.15"}]}],"versions":["6.11.0-1007.7","6.11.0-1008.8","6.11.0-1009.9","6.11.0-1010.10","6.11.0-1011.11","6.11.0-1012.12","6.11.0-1013.13"],"bundled":730},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-aws-6.8","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1023.25~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"],"bundled":211},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-aws","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1023.25"}]}],"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"],"bundled":211},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-azure","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1025.30"}]}],"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"],"bundled":318},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-azure-6.8","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1025.30~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"],"bundled":318},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-ibm","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1022.22"}]}],"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"],"bundled":317},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-oem-6.8","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1024.24"}]}],"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"],"bundled":317},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-hwe-6.8","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-57.59~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"],"bundled":325},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-azure-nvidia","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1014.15"}]}],"versions":["6.8.0-1013.14"],"bundled":739},{"source":"osv","ecosystem":"openSUSE:Tumbleweed","package":"kernel-source","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.11.8-1.1"}]}],"bundled":486},{"source":"osv","ecosystem":"openSUSE:Tumbleweed","package":"kernel-source-longterm","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.12.11-1.1"}]}],"bundled":504}],"products":[{"vendor":"linux","product":"linux"},{"vendor":"linux","product":"linux_kernel"}],"references":[{"url":"https://git.kernel.org/stable/c/080e6c9a3908de193a48f646c5ce1bfb15676ffc","tags":["Patch","web","report"]},{"url":"https://git.kernel.org/stable/c/af3122f5fdc0d00581d6e598a668df6bf54c9daa","tags":["Patch","web","report"]},{"url":"https://git.kernel.org/stable/c/33e28acf42ee863f332a958bfc2f1a284a3659df","tags":["Patch","web","report"]},{"url":"https://git.kernel.org/stable/c/3cd00d2e3655fad3bda96dc1ebf17b6495f86fea","tags":["Patch","web","report"]},{"url":"https://git.kernel.org/stable/c/a1e40ac5b5e9077fe1f7ae0eb88034db0f9ae1ab","tags":["Patch","web","report"]},{"url":"https://lists.debian.org/debian-lts-announce/2025/01/msg00001.html","tags":["web"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-49978","tags":["web","advisory"]},{"url":"https://github.com/advisories/GHSA-rf58-pp6r-5653"},{"url":"https://docs.bell-sw.com/security/cves/CVE-2024-49978","tags":["advisory"]},{"url":"https://github.com/CVEProject/cvelistV5/tree/main/cves/2024/49xxx/CVE-2024-49978.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-49978","tags":["advisory"]},{"url":"https://advisories.mageia.org/MGASA-2024-0344.html","tags":["advisory"]},{"url":"https://bugs.mageia.org/show_bug.cgi?id=33669","tags":["report"]},{"url":"https://cdn.kernel.org/pub/linux/kernel/v6.x/ChangeLog-6.6.53","tags":["web"]},{"url":"https://cdn.kernel.org/pub/linux/kernel/v6.x/ChangeLog-6.6.54","tags":["web"]},{"url":"https://cdn.kernel.org/pub/linux/kernel/v6.x/ChangeLog-6.6.55","tags":["web"]},{"url":"https://cdn.kernel.org/pub/linux/kernel/v6.x/ChangeLog-6.6.56","tags":["web"]},{"url":"https://cdn.kernel.org/pub/linux/kernel/v6.x/ChangeLog-6.6.57","tags":["web"]},{"url":"https://cdn.kernel.org/pub/linux/kernel/v6.x/ChangeLog-6.6.58","tags":["web"]},{"url":"https://advisories.mageia.org/MGASA-2024-0345.html","tags":["advisory"]},{"url":"https://bugs.mageia.org/show_bug.cgi?id=33667","tags":["report"]},{"url":"https://www.openeuler.org/zh/security/security-bulletins/detail/?id=openEuler-SA-2024-2367","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-42122","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-44943","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-44951","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-45021","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-46685","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-46702","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-46735","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-46743","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-46809","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-46815","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-46824","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-46831","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-47679","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-47686","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-47688","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-47690","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-47691","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-47696","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-47699","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-47700","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-47701","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-47703","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-47704","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-47705","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-47719","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-47727","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-47739","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-47742","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-47744","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-47748","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-47751","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-47752","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-47753","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-47756","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-49850","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-49852","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-49858","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-49859","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-49860","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-49862","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-49870","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-49871","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-49874","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-49877","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-49879","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-49881","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-49882","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-49883","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-49884","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-49886","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-49889","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-49892","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-49896","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-49898","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-49901","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-49909","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-49912","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-49913","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-49917","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-49922","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-49924","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-49931","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-49933","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-49934","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-49936","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-49937","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-49940","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-49954","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-49955","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-49958","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-49960","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-49961","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-49966","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-49967","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-49968","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-49973","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-49975","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-49981","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-49983","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-49989","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-49992","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-49994","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-49995","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-49996","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-50000","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-50003","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-50006","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-50008","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-50009","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-50013","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-50014","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-50015","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-50016","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-50019","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-50022","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-50025","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-50026","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-50028","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-50029","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-50033","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-50036","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-50040","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-50041","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-50047","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-50055","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-50058","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-50059","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-50060","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-50063","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-50064","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-50066","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-50067","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-50070","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-50072","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-50074","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-50076","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-50083","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-50084","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-50087","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-50088","tags":["advisory"]},{"url":"https://www.openeuler.org/zh/security/security-bulletins/detail/?id=openEuler-SA-2024-2368","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-48961","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-48975","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-49004","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-46677","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-47659","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-47660","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-47668","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-47673","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-47693","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-47723","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-47726","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-49855","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-49950","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-50002","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-50007","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-50035","tags":["advisory"]},{"url":"https://www.openeuler.org/zh/security/security-bulletins/detail/?id=openEuler-SA-2024-2369","tags":["advisory"]},{"url":"https://www.openeuler.org/zh/security/security-bulletins/detail/?id=openEuler-SA-2024-2371","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-48956","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-48958","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-48960","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-48962","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-48966","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-48972","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-48981","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-48982","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-48992","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-48995","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-49005","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-49011","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-49017","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-49020","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-49021","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-49023","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-49031","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-49032","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-47692","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-49863","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-49965","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-50046","tags":["advisory"]},{"url":"https://www.suse.com/support/update/announcement/2025/suse-su-20250428-1/","tags":["advisory"]},{"url":"https://bugzilla.suse.com/1012628","tags":["report"]},{"url":"https://bugzilla.suse.com/1194869","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/1220711","tags":["report"]},{"url":"https://bugzilla.suse.com/1221326","tags":["report"]},{"url":"https://bugzilla.suse.com/1222803","tags":["report"]},{"url":"https://bugzilla.suse.com/1224049","tags":["report"]},{"url":"https://bugzilla.suse.com/1225897","tags":["report"]},{"url":"https://bugzilla.suse.com/1226980","tags":["report"]},{"url":"https://bugzilla.suse.com/1228592","tags":["report"]},{"url":"https://bugzilla.suse.com/1229833","tags":["report"]},{"url":"https://bugzilla.suse.com/1231016","tags":["report"]},{"url":"https://bugzilla.suse.com/1232087","tags":["report"]},{"url":"https://bugzilla.suse.com/1232101","tags":["report"]},{"url":"https://bugzilla.suse.com/1232158","tags":["report"]},{"url":"https://bugzilla.suse.com/1232161","tags":["report"]},{"url":"https://bugzilla.suse.com/1232421","tags":["report"]},{"url":"https://bugzilla.suse.com/1232882","tags":["report"]},{"url":"https://bugzilla.suse.com/1233055","tags":["report"]},{"url":"https://bugzilla.suse.com/1233112","tags":["report"]},{"url":"https://bugzilla.suse.com/1233221","tags":["report"]},{"url":"https://bugzilla.suse.com/1233248","tags":["report"]},{"url":"https://bugzilla.suse.com/1233259","tags":["report"]},{"url":"https://bugzilla.suse.com/1233260","tags":["report"]},{"url":"https://bugzilla.suse.com/1233488","tags":["report"]},{"url":"https://bugzilla.suse.com/1233522","tags":["report"]},{"url":"https://bugzilla.suse.com/1233638","tags":["report"]},{"url":"https://bugzilla.suse.com/1233642","tags":["report"]},{"url":"https://bugzilla.suse.com/1233778","tags":["report"]},{"url":"https://bugzilla.suse.com/1234195","tags":["report"]},{"url":"https://bugzilla.suse.com/1234619","tags":["report"]},{"url":"https://bugzilla.suse.com/1234635","tags":["report"]},{"url":"https://bugzilla.suse.com/1234683","tags":["report"]},{"url":"https://bugzilla.suse.com/1234693","tags":["report"]},{"url":"https://bugzilla.suse.com/1234726","tags":["report"]},{"url":"https://bugzilla.suse.com/1234825","tags":["report"]},{"url":"https://bugzilla.suse.com/1234863","tags":["report"]},{"url":"https://bugzilla.suse.com/1234887","tags":["report"]},{"url":"https://bugzilla.suse.com/1234888","tags":["report"]},{"url":"https://bugzilla.suse.com/1234893","tags":["report"]},{"url":"https://bugzilla.suse.com/1234898","tags":["report"]},{"url":"https://bugzilla.suse.com/1234901","tags":["report"]},{"url":"https://bugzilla.suse.com/1234906","tags":["report"]},{"url":"https://bugzilla.suse.com/1234923","tags":["report"]},{"url":"https://bugzilla.suse.com/1234931","tags":["report"]},{"url":"https://bugzilla.suse.com/1234934","tags":["report"]},{"url":"https://bugzilla.suse.com/1234947","tags":["report"]},{"url":"https://bugzilla.suse.com/1234957","tags":["report"]},{"url":"https://bugzilla.suse.com/1235000","tags":["report"]},{"url":"https://bugzilla.suse.com/1235001","tags":["report"]},{"url":"https://bugzilla.suse.com/1235011","tags":["report"]},{"url":"https://bugzilla.suse.com/1235031","tags":["report"]},{"url":"https://bugzilla.suse.com/1235032","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/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/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/1235100","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/1235132","tags":["report"]},{"url":"https://bugzilla.suse.com/1235133","tags":["report"]},{"url":"https://bugzilla.suse.com/1235155","tags":["report"]},{"url":"https://bugzilla.suse.com/1235160","tags":["report"]},{"url":"https://bugzilla.suse.com/1235217","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/1235230","tags":["report"]},{"url":"https://bugzilla.suse.com/1235241","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/1235390","tags":["report"]},{"url":"https://bugzilla.suse.com/1235391","tags":["report"]},{"url":"https://bugzilla.suse.com/1235406","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/1235418","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/1235430","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/1235487","tags":["report"]},{"url":"https://bugzilla.suse.com/1235488","tags":["report"]},{"url":"https://bugzilla.suse.com/1235489","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/1235498","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/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/1235545","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/1235578","tags":["report"]},{"url":"https://bugzilla.suse.com/1235582","tags":["report"]},{"url":"https://bugzilla.suse.com/1235583","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/1235612","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/1235638","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/1235656","tags":["report"]},{"url":"https://bugzilla.suse.com/1235657","tags":["report"]},{"url":"https://bugzilla.suse.com/1235663","tags":["report"]},{"url":"https://bugzilla.suse.com/1235686","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/1235865","tags":["report"]},{"url":"https://bugzilla.suse.com/1235874","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/1235941","tags":["report"]},{"url":"https://bugzilla.suse.com/1235946","tags":["report"]},{"url":"https://bugzilla.suse.com/1235948","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/1236127","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/1236160","tags":["report"]},{"url":"https://bugzilla.suse.com/1236161","tags":["report"]},{"url":"https://bugzilla.suse.com/1236163","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/1236182","tags":["report"]},{"url":"https://bugzilla.suse.com/1236190","tags":["report"]},{"url":"https://bugzilla.suse.com/1236192","tags":["report"]},{"url":"https://bugzilla.suse.com/1236198","tags":["report"]},{"url":"https://bugzilla.suse.com/1236227","tags":["report"]},{"url":"https://bugzilla.suse.com/1236245","tags":["report"]},{"url":"https://bugzilla.suse.com/1236247","tags":["report"]},{"url":"https://bugzilla.suse.com/1236248","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-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-36476","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-39282","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-43913","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-45828","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-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-49948","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-49951","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-49978","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-49998","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-50151","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-50199","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-50299","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-50304","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-52332","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-53164","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-53168","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-53170","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-53172","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-53175","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-53185","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-53187","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-53203","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-53227","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-53236","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-53239","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-56538","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-56557","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-56558","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-56577","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-56578","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-56600","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-56601","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-56606","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-56607","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-56608","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-56609","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-56610","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-56648","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-56649","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-56650","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-56665","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-56679","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-56693","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-56707","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-56715","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-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-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-56759","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-56760","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-56763","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-57802","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-57884","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-57917","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-57931","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-57938","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-57940","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-57946","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-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-21656","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-21662","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/security/cve/CVE-2024-5660","tags":["web"]},{"url":"https://www.suse.com/support/update/announcement/2025/suse-su-20250564-1/","tags":["advisory"]},{"url":"https://bugzilla.suse.com/1227937","tags":["report"]},{"url":"https://bugzilla.suse.com/1233028","tags":["report"]},{"url":"https://bugzilla.suse.com/1234070","tags":["report"]},{"url":"https://bugzilla.suse.com/1235485","tags":["report"]},{"url":"https://bugzilla.suse.com/1236681","tags":["report"]},{"url":"https://bugzilla.suse.com/1236682","tags":["report"]},{"url":"https://bugzilla.suse.com/1236684","tags":["report"]},{"url":"https://bugzilla.suse.com/1236689","tags":["report"]},{"url":"https://bugzilla.suse.com/1236702","tags":["report"]},{"url":"https://bugzilla.suse.com/1236759","tags":["report"]},{"url":"https://www.suse.com/security/cve/CVE-2024-40980","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-50142","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-53123","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-56633","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-21665","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-21667","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-21668","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-21673","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-21681","tags":["web"]},{"url":"https://www.suse.com/support/update/announcement/2025/suse-su-202520165-1/","tags":["advisory"]},{"url":"https://bugzilla.suse.com/1214954","tags":["report"]},{"url":"https://bugzilla.suse.com/1220773","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/1225820","tags":["report"]},{"url":"https://bugzilla.suse.com/1227445","tags":["report"]},{"url":"https://bugzilla.suse.com/1228526","tags":["report"]},{"url":"https://bugzilla.suse.com/1229809","tags":["report"]},{"url":"https://bugzilla.suse.com/1230205","tags":["report"]},{"url":"https://bugzilla.suse.com/1230413","tags":["report"]},{"url":"https://bugzilla.suse.com/1230697","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/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/1232436","tags":["report"]},{"url":"https://bugzilla.suse.com/1233038","tags":["report"]},{"url":"https://bugzilla.suse.com/1233070","tags":["report"]},{"url":"https://bugzilla.suse.com/1233096","tags":["report"]},{"url":"https://bugzilla.suse.com/1233200","tags":["report"]},{"url":"https://bugzilla.suse.com/1233204","tags":["report"]},{"url":"https://bugzilla.suse.com/1233239","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/1233469","tags":["report"]},{"url":"https://bugzilla.suse.com/1233546","tags":["report"]},{"url":"https://bugzilla.suse.com/1233558","tags":["report"]},{"url":"https://bugzilla.suse.com/1233637","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/1234079","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/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/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/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/1234810","tags":["report"]},{"url":"https://bugzilla.suse.com/1234811","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/1234884","tags":["report"]},{"url":"https://bugzilla.suse.com/1234889","tags":["report"]},{"url":"https://bugzilla.suse.com/1234891","tags":["report"]},{"url":"https://bugzilla.suse.com/1234899","tags":["report"]},{"url":"https://bugzilla.suse.com/1234900","tags":["report"]},{"url":"https://bugzilla.suse.com/1234905","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/1234929","tags":["report"]},{"url":"https://bugzilla.suse.com/1234930","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/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/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/1235016","tags":["report"]},{"url":"https://bugzilla.suse.com/1235019","tags":["report"]},{"url":"https://bugzilla.suse.com/1235033","tags":["report"]},{"url":"https://bugzilla.suse.com/1235045","tags":["report"]},{"url":"https://bugzilla.suse.com/1235056","tags":["report"]},{"url":"https://bugzilla.suse.com/1235075","tags":["report"]},{"url":"https://bugzilla.suse.com/1235108","tags":["report"]},{"url":"https://bugzilla.suse.com/1235128","tags":["report"]},{"url":"https://bugzilla.suse.com/1235134","tags":["report"]},{"url":"https://bugzilla.suse.com/1235138","tags":["report"]},{"url":"https://bugzilla.suse.com/1235246","tags":["report"]},{"url":"https://bugzilla.suse.com/1235409","tags":["report"]},{"url":"https://bugzilla.suse.com/1235507","tags":["report"]},{"url":"https://bugzilla.suse.com/1235550","tags":["report"]},{"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-36908","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-44934","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-44996","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-47678","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-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-50143","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-50154","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-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-50280","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-53050","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-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-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-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-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-53166","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-53169","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-53171","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-53179","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-53180","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-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-53229","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-53234","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-53237","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-56536","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-56539","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-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-56576","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-56582","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-56599","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-56645","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-56667","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-8805","tags":["web"]},{"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-49978","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-49978","tags":["report"]},{"url":"https://git.kernel.org/linus/a1e40ac5b5e9077fe1f7ae0eb88034db0f9ae1ab","tags":["report"]},{"url":"https://ubuntu.com/security/notices/USN-7276-1","tags":["advisory"]},{"url":"https://ubuntu.com/security/notices/USN-7277-1","tags":["advisory"]},{"url":"https://ubuntu.com/security/notices/USN-7301-1","tags":["advisory"]},{"url":"https://ubuntu.com/security/notices/USN-7303-1","tags":["advisory"]},{"url":"https://ubuntu.com/security/notices/USN-7304-1","tags":["advisory"]},{"url":"https://ubuntu.com/security/notices/USN-7303-2","tags":["advisory"]},{"url":"https://ubuntu.com/security/notices/USN-7310-1","tags":["advisory"]},{"url":"https://ubuntu.com/security/notices/USN-7311-1","tags":["advisory"]},{"url":"https://ubuntu.com/security/notices/USN-7303-3","tags":["advisory"]},{"url":"https://ubuntu.com/security/notices/USN-7384-1","tags":["advisory"]},{"url":"https://ubuntu.com/security/notices/USN-7385-1","tags":["advisory"]},{"url":"https://ubuntu.com/security/notices/USN-7386-1","tags":["advisory"]},{"url":"https://ubuntu.com/security/notices/USN-7384-2","tags":["advisory"]},{"url":"https://ubuntu.com/security/notices/USN-7403-1","tags":["advisory"]},{"url":"https://ubuntu.com/security/notices/USN-7468-1","tags":["advisory"]},{"url":"https://ubuntu.com/security/CVE-2023-52917","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-41016","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-47670","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-47671","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-47672","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-47673","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-47675","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-47677","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-47678","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-47679","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-47681","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-47682","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-47684","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-47685","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-47686","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-47687","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-47688","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-47689","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-47690","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-47691","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-47692","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-47693","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-47695","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-47696","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-47697","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-47698","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-47699","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-47700","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-47701","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-47702","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-47703","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-47704","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-47705","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-47706","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-47707","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-47709","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-47710","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-47712","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-47713","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-47714","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-47715","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-47716","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-47718","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-47719","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-47720","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-47723","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-47727","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-47728","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-47730","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-47731","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-47732","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-47733","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-47734","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-47735","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-47737","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-47738","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-47739","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-47740","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-47741","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-47742","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-47743","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-47744","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-47745","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-47747","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-47748","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-47749","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-47750","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-47751","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-47752","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-47753","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-47754","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-47756","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-47757","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-49850","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-49851","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-49852","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-49853","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-49855","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-49856","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-49858","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-49859","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-49860","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-49861","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-49862","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-49863","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-49864","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-49866","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-49867","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-49868","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-49870","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-49871","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-49874","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-49875","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-49876","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-49877","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-49878","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-49879","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-49880","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-49881","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-49882","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-49883","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-49884","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-49885","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-49886","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-49888","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-49889","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-49890","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-49891","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-49892","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-49894","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-49895","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-49896","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-49897","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-49898","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-49900","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-49901","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-49902","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-49903","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-49905","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-49907","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-49909","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-49911","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-49912","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-49913","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-49915","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-49917","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-49918","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-49919","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-49922","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-49923","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-49924","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-49925","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-49926","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-49927","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-49928","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-49929","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-49930","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-49931","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-49933","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-49934","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-49935","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-49936","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-49937","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-49938","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-49939","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-49942","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-49944","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-49945","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-49946","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-49947","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-49948","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-49949","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-49950","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-49951","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-49952","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-49953","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-49954","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-49955","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-49957","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-49958","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-49959","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-49960","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-49961","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-49962","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-49963","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-49965","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-49966","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-49969","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-49973","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-49974","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-49975","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-49976","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-49977","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-49980","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-49981","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-49982","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-49983","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-49985","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-49986","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-49987","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-49988","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-49989","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-49991","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-49992","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-49994","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-49995","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-49996","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-49997","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-49998","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-49999","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50000","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50001","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50002","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50005","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50006","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50007","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50008","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50012","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50013","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50014","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50015","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50016","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50017","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50175","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50176","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50179","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-53144","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-0927","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50274","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-53064","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2022-49034","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-46869","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-47676","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-47680","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-47694","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-47708","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-47711","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-47717","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-47721","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-47724","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-47726","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-47736","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-47746","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-49857","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-49865","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-49869","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-49872","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-49873","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-49887","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-49932","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-49940","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-49941","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-49943","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-49956","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-49964","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-49968","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-49970","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-49971","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-49972","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-49979","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50003","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-50033","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50034","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50035","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50036","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50037","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50038","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50039","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50040","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50041","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50042","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50043","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50044","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50045","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50046","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50047","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50048","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50049","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50055","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50056","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50057","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50058","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50059","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50060","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50061","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50062","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50063","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50064","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50065","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50066","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50067","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50068","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50069","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50070","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50071","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50072","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50073","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50074","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50075","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50076","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50077","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50078","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50079","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50080","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50081","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50082","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50083","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50084","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50085","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50086","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50087","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50088","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50090","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50091","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50092","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50093","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50094","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50095","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50096","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50098","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50099","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50100","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50101","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50102","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50103","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50104","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50105","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50106","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50107","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50108","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50109","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50110","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50111","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50112","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50113","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50114","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50115","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50116","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50117","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50118","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50119","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50120","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50121","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50122","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50123","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50124","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50125","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50126","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50127","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50128","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50129","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50130","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50131","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50132","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50133","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50134","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50135","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50136","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50137","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50138","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50139","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50140","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50141","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50142","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50143","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50144","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50145","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50146","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50147","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50148","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50149","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50150","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50151","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50152","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50153","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50154","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50155","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50156","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50157","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50158","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50159","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50160","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50161","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50162","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50163","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50164","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50165","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50166","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50167","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50168","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50169","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50170","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50171","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50172","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50173","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50174","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50177","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50178","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50180","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50181","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50182","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50183","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50184","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50185","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50186","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50187","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50188","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50189","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50190","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50191","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50192","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50193","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50194","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50195","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50196","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50197","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50198","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50199","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50200","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50201","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50202","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50203","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50204","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50205","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50206","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50207","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50208","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50209","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50211","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50212","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50213","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50214","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50215","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50216","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50217","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50218","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50220","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50221","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50222","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50223","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50224","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50225","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50226","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50227","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50229","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50230","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50231","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50232","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50233","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50234","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50235","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50236","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50237","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50238","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50239","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50240","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50242","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50243","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50244","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50245","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50246","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50247","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50248","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50250","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50251","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50252","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50253","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50254","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50255","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50256","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50257","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50258","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50259","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50260","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50261","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50262","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50263","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50265","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50266","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50267","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50268","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50269","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50270","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50271","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50272","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50273","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50275","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50276","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50277","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50278","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50279","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50280","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50281","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50282","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50283","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50284","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50285","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50286","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50287","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50288","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50289","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50290","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50291","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50292","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50293","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50294","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50295","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50296","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50297","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50298","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50299","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50300","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50301","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50302","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50303","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50304","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-53042","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-53043","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-53044","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-53045","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-53046","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-53047","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-53048","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-53049","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-53052","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-53053","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-53055","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-53056","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-53058","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-53059","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-53061","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-53062","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-53063","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-53065","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-53066","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-53067","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-53068","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-53069","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-53071","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-53072","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-53074","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-53075","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-53076","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-53077","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-53078","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-53079","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-53080","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-53081","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-53082","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-53083","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-53084","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-53085","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-53086","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-53087","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-53088","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-53089","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-53090","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-53091","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-53092","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-53093","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-53094","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-53095","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-53098","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-53099","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-53100","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-53101","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-53104","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-53105","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-53106","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-53107","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-53108","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-53109","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-53110","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-53111","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-53112","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-53113","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-53114","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-53115","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-53116","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-53117","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-53118","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-53119","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-53120","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-53121","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-53122","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-53123","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-53124","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-53125","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-53126","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-53127","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-53128","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-53129","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-53130","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-53131","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-53132","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-53133","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-53134","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-53135","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-53137","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-53138","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-53139","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-53140","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-53141","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-53142","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-53143","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-53145","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-53146","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-53147","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-53148","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-53149","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-53150","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-53151","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-53152","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-53153","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-53154","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-53155","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-53156","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-53157","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-53158","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-53160","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-53161","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-53162","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-53163","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-53165","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-53166","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-53167","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-53168","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-53169","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-53170","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-53171","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-53172","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-53173","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-53174","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-53175","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-53176","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-53177","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-53178","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-53180","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-53181","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-53183","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-53184","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-53187","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-53188","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-53189","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-53190","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-53191","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-53192","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-53193","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-53194","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-53195","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-53196","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-53197","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-53198","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-53199","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-53200","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-53201","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-53202","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-53203","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-53208","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-53209","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-53210","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-53212","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-53213","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-53214","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-53215","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-53216","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-53217","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-53218","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-53219","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-53220","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-53221","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-53223","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-53224","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-53226","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-53227","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-53228","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-53229","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-53230","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-53231","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-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-56534","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56535","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56536","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56537","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56538","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56539","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56540","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56541","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56542","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56543","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56544","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56545","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56546","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56548","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56549","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56674","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56677","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56678","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56679","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56680","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56681","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56683","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56684","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56685","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56687","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56688","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56689","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56690","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56691","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56692","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56693","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56694","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56696","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56697","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56698","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56699","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56700","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56701","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56702","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56703","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56704","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56705","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56707","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56708","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56720","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56721","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56722","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56723","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56724","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56725","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56726","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56727","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56728","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56729","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56739","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56741","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56742","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56744","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56745","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56746","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56747","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56748","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56749","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56751","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56752","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56754","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56755","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56756","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-53103","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-53164","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-8805","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-49893","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-49914","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-49920","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-49921","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56582","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56614","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56663","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-2312","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50032","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56595","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56598","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56658","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56672","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-57798","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-41014","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-41932","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-41935","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-42122","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-43098","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-44955","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-45828","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-47141","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-47143","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-47794","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-47809","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-48873","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-48875","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-48876","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-48881","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-49569","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-49899","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-49906","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50051","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-52332","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-53050","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-53051","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-53096","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-53222","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-53680","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56550","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56551","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56557","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56558","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56562","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56565","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56566","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56567","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56568","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56569","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56570","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56572","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56573","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56574","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56575","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56576","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56577","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56578","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56579","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56580","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56581","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56583","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56584","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56586","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56587","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56588","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56589","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56590","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56592","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56593","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56594","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56596","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56597","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56599","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56600","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56601","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56602","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56603","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56604","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56605","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56606","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56607","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56608","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56609","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56610","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56611","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56613","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56615","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56616","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56619","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56620","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56621","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56622","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56623","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56625","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56626","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56627","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56629","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56630","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56631","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56632","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56633","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56634","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56635","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56636","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56637","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56638","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56640","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56641","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56642","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56643","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56644","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56645","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56647","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56648","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56649","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56650","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56651","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56765","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56771","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56772","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56773","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56774","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56775","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56776","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56777","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56778","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56779","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56780","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56781","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56782","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56785","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56786","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56787","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-57838","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-57843","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-57849","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-57850","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-57872","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-57874","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-57876","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-21700","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-21701","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-21702","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-21756","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-21831","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-21993","tags":["report"]},{"url":"https://lists.opensuse.org/archives/list/security-announce@lists.opensuse.org/thread/2NO44GTYBSPPWKFDREFWHITK4XKTNVLP/","tags":["advisory"]},{"url":"https://www.suse.com/security/cve/CVE-2023-52917","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-46869","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-47671","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-47675","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-47676","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-47677","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-47679","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-47680","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-47681","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-47682","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-47683","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-47684","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-47685","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-47686","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-47687","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-47688","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-47689","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-47690","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-47691","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-47692","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-47693","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-47694","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-47695","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-47696","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-47697","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-47698","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-47699","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-47700","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-47701","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-47702","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-47703","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-47704","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-47705","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-47706","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-47707","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-47708","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-47709","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-47710","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-47711","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-47712","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-47713","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-47714","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-47715","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-47716","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-47717","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-47718","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-47719","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-47720","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-47721","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-47723","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-47724","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-47726","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-47727","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-47728","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-47729","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-47730","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-47731","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-47732","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-47733","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-47734","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-47735","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-47736","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-47737","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-47738","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-47739","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-47740","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-47741","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-47742","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-47743","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-47744","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-47745","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-47746","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-47747","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-47748","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-47749","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-47750","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-47751","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-47752","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-47753","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-47754","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-47756","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-47757","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-49850","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-49851","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-49852","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-49853","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-49855","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-49856","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-49857","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-49858","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-49859","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-49860","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-49861","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-49862","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-49863","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-49864","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-49865","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-49866","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-49867","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-49868","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-49869","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-49870","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-49871","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-49872","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-49873","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-49874","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-49875","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-49876","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-49877","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-49878","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-49879","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-49880","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-49881","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-49882","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-49883","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-49885","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-49886","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-49887","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-49888","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-49889","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-49890","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-49891","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-49892","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-49893","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-49894","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-49895","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-49896","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-49897","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-49898","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-49899","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-49900","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-49901","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-49902","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-49903","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-49904","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-49905","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-49906","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-49907","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-49908","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-49909","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-49910","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-49911","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-49912","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-49913","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-49914","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-49916","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-49917","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-49918","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-49919","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-49920","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-49921","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-49922","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-49923","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-49924","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-49925","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-49926","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-49927","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-49928","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-49929","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-49930","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-49931","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-49932","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-49933","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-49934","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-49935","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-49936","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-49937","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-49938","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-49939","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-49940","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-49941","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-49942","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-49943","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-49944","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-49945","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-49946","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-49947","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-49949","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-49950","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-49952","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-49953","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-49954","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-49955","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-49956","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-49957","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-49958","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-49959","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-49960","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-49961","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-49962","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-49963","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-49964","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-49965","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-49966","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-49967","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-49968","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-49969","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-49970","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-49971","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-49972","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-49973","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-49974","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-49975","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-49976","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-49977","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-49979","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-49980","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-49981","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-49982","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-49983","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-49984","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-49985","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-49986","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-49987","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-49988","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-49989","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-49990","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-49991","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-49992","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-49994","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-49995","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-49996","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-49997","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-49999","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-50000","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-50001","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-50002","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-50003","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-50004","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-50005","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-50006","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-50007","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-50008","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-50009","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-50010","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-50011","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-50012","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-50013","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-50014","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-50015","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-50017","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-50019","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-50020","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-50021","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-50022","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-50023","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-50024","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-50025","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-50026","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-50027","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-50028","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-50029","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-50030","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-50031","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-50032","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-50033","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-50034","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-50035","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-50036","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-50037","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-50038","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-50040","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-50041","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-50042","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-50043","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-50044","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-50045","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-50046","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-50048","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-50049","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-50055","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-50056","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-50057","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-50058","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-50059","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-50060","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-50061","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-50062","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-50063","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-50064","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-50065","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-50066","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-50067","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-50068","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-50069","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-50070","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-50071","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-50072","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-50073","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-50074","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-50075","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-50076","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-50077","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-50078","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-50079","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-50080","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-50081","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-50082","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-50083","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-50084","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-50085","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-50086","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-50087","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-50088","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-50089","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-50090","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-50091","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-50092","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-50093","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-50094","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-50095","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-50096","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-50097","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-50098","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-50099","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-50100","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-50101","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-50102","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-50103","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-50104","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-50105","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-50107","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-50108","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-50109","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-50110","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-50111","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-50112","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-50113","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-50114","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-50115","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-50116","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-50117","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-50118","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-50119","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-50120","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-50121","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-50122","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-50123","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-50124","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-50125","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-50126","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-50127","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-50128","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-50129","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-50130","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-50131","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-50132","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-50133","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-50134","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-50135","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-50136","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-50137","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-50138","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-50139","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-50140","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-50141","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-50144","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-50145","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-50146","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-50147","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-50148","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-50149","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-50150","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-50152","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-50153","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-50155","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-50156","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-50157","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-50158","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-50159","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-50160","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-50161","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-50162","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-50163","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-50164","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-50165","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-50166","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-50167","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-50168","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-50170","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-50171","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-50172","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-50173","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-50174","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-50175","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-50176","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-50177","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-50178","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-50179","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-50180","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-50181","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-50182","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-50183","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-50184","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-50185","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-50186","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-50187","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-50188","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-50189","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-50190","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-50191","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-50192","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-50193","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-50194","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-50195","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-50196","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-50197","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-50198","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-50200","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-50201","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-50205","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-50206","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-50207","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-50208","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-50209","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-50210","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-50212","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-50213","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-50214","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-50215","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-50216","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-50217","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-50218","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-50220","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-50221","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-50222","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-50223","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-50224","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-50225","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-50226","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-50227","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-50229","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-50230","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-50231","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-50232","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-50233","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-50234","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-50235","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-50236","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-50237","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-50238","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-50239","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-50240","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-50241","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-50242","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-50243","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-50244","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-50245","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-50246","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-50247","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-50248","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-50249","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-50250","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-50252","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-50253","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-50254","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-50255","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-50257","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-50259","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-50260","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-50261","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-50263","tags":["web"]},{"url":"https://lists.opensuse.org/archives/list/security-announce@lists.opensuse.org/thread/T7LN2FDZYBYZRLX5LOA3REDAXV7VKGW4/","tags":["advisory"]},{"url":"https://www.suse.com/security/cve/CVE-2023-28746","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-52429","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-52456","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-52457","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-52459","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-52461","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-6270","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-6535","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-6536","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-7042","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-2201","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-23307","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-23851","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-24860","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-26605","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-26862","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-26865","tags":["web"]}],"sources":{"cve":[{"id":"CVE-2024-49978","title":"gso: fix udp gso fraglist segmentation after pull from frag_list","description":"In the Linux kernel, the following vulnerability has been resolved:\n\ngso: fix udp gso fraglist segmentation after pull from frag_list\n\nDetect gso fraglist skbs with corrupted geometry (see below) and\npass these to skb_segment instead of skb_segment_list, as the first\ncan segment them correctly.\n\nValid SKB_GSO_FRAGLIST skbs\n- consist of two or more segments\n- the head_skb holds the protocol headers plus first gso_size\n- one or more frag_list skbs hold exactly one segment\n- all but the last must be gso_size\n\nOptional datapath hooks such as NAT and BPF (bpf_skb_pull_data) can\nmodify these skbs, breaking these invariants.\n\nIn extreme cases they pull all data into skb linear. For UDP, this\ncauses a NULL ptr deref in __udpv4_gso_segment_list_csum at\nudp_hdr(seg-\u003enext)-\u003edest.\n\nDetect invalid geometry due to pull, by checking head_skb size.\nDon't just drop, as this may blackhole a destination. Convert to be\nable to pass to regular skb_segment.","status":"published","published":"2024-10-21T18:02:25.151Z","modified":"2026-08-05T11:40:48.306Z","cvss":[{"version":"3.1","score":7.5,"vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H","level":"high","assessor":"cna"}],"updated_at":"2026-11-02T14:33:55.977982Z"}],"euvd":[{"id":"EUVD-2024-43656","description":"In the Linux kernel, the following vulnerability has been resolved:\n\ngso: fix udp gso fraglist segmentation after pull from frag_list\n\nDetect gso fraglist skbs with corrupted geometry (see below) and\npass these to skb_segment instead of skb_segment_list, as the first\ncan segment them correctly.\n\nValid SKB_GSO_FRAGLIST skbs\n- consist of two or more segments\n- the head_skb holds the protocol headers plus first gso_size\n- one or more frag_list skbs hold exactly one segment\n- all but the last must be gso_size\n\nOptional datapath hooks such as NAT and BPF (bpf_skb_pull_data) can\nmodify these skbs, breaking these invariants.\n\nIn extreme cases they pull all data into skb linear. For UDP, this\ncauses a NULL ptr deref in __udpv4_gso_segment_list_csum at\nudp_hdr(seg-\u003enext)-\u003edest.\n\nDetect invalid geometry due to pull, by checking head_skb size.\nDon't just drop, as this may blackhole a destination. Convert to be\nable to pass to regular skb_segment.","status":"published","published":"2024-10-21T18:02:25Z","modified":"2026-08-05T11:40:48Z","cvss":[{"version":"3.1","score":7.5,"vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H","level":"high"}],"updated_at":"2026-11-02T18:02:15.837662Z"}],"ghsa":[{"id":"GHSA-rf58-pp6r-5653","title":"In the Linux kernel, the following vulnerability has been resolved:\n\ngso: fix udp gso fraglist...","description":"In the Linux kernel, the following vulnerability has been resolved:\n\ngso: fix udp gso fraglist segmentation after pull from frag_list\n\nDetect gso fraglist skbs with corrupted geometry (see below) and\npass these to skb_segment instead of skb_segment_list, as the first\ncan segment them correctly.\n\nValid SKB_GSO_FRAGLIST skbs\n- consist of two or more segments\n- the head_skb holds the protocol headers plus first gso_size\n- one or more frag_list skbs hold exactly one segment\n- all but the last must be gso_size\n\nOptional datapath hooks such as NAT and BPF (bpf_skb_pull_data) can\nmodify these skbs, breaking these invariants.\n\nIn extreme cases they pull all data into skb linear. For UDP, this\ncauses a NULL ptr deref in __udpv4_gso_segment_list_csum at\nudp_hdr(seg-\u003enext)-\u003edest.\n\nDetect invalid geometry due to pull, by checking head_skb size.\nDon't just drop, as this may blackhole a destination. Convert to be\nable to pass to regular skb_segment.","status":"published","published":"2024-10-21T18:30:59Z","modified":"2025-11-04T00:32: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"}],"cwes":["CWE-476"],"updated_at":"2026-11-02T15:04:31.727217Z"}],"nvd":[{"id":"CVE-2024-49978","description":"In the Linux kernel, the following vulnerability has been resolved:\n\ngso: fix udp gso fraglist segmentation after pull from frag_list\n\nDetect gso fraglist skbs with corrupted geometry (see below) and\npass these to skb_segment instead of skb_segment_list, as the first\ncan segment them correctly.\n\nValid SKB_GSO_FRAGLIST skbs\n- consist of two or more segments\n- the head_skb holds the protocol headers plus first gso_size\n- one or more frag_list skbs hold exactly one segment\n- all but the last must be gso_size\n\nOptional datapath hooks such as NAT and BPF (bpf_skb_pull_data) can\nmodify these skbs, breaking these invariants.\n\nIn extreme cases they pull all data into skb linear. For UDP, this\ncauses a NULL ptr deref in __udpv4_gso_segment_list_csum at\nudp_hdr(seg-\u003enext)-\u003edest.\n\nDetect invalid geometry due to pull, by checking head_skb size.\nDon't just drop, as this may blackhole a destination. Convert to be\nable to pass to regular skb_segment.","status":"published","published":"2024-10-21T18:15:18.483Z","modified":"2026-08-04T11:21:04.2Z","cvss":[{"version":"3.1","score":7.5,"vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H","level":"high","assessor":"secondary"},{"version":"3.1","score":5.5,"vector":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H","level":"medium","assessor":"primary"}],"cwes":["CWE-476"],"updated_at":"2026-11-02T14:10:33.928543Z"}],"osv":[{"id":"AZL-51829","title":"CVE-2024-49978 affecting package kernel 5.15.200.1-1","description":"In the Linux kernel, the following vulnerability has been resolved:\n\ngso: fix udp gso fraglist segmentation after pull from frag_list\n\nDetect gso fraglist skbs with corrupted geometry (see below) and\npass these to skb_segment instead of skb_segment_list, as the first\ncan segment them correctly.\n\nValid SKB_GSO_FRAGLIST skbs\n- consist of two or more segments\n- the head_skb holds the protocol headers plus first gso_size\n- one or more frag_list skbs hold exactly one segment\n- all but the last must be gso_size\n\nOptional datapath hooks such as NAT and BPF (bpf_skb_pull_data) can\nmodify these skbs, breaking these invariants.\n\nIn extreme cases they pull all data into skb linear. For UDP, this\ncauses a NULL ptr deref in __udpv4_gso_segment_list_csum at\nudp_hdr(seg-\u003enext)-\u003edest.\n\nDetect invalid geometry due to pull, by checking head_skb size.\nDon't just drop, as this may blackhole a destination. Convert to be\nable to pass to regular skb_segment.","status":"published","published":"2024-10-21T18:15:18Z","modified":"2026-04-21T04:33:15.986886Z","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.3228Z"},{"id":"BELL-CVE-2024-49978","status":"published","published":"2024-10-23T05:57:12.861499Z","modified":"2026-01-26T09:39:33.093913Z","cvss":[{"version":"3.1","score":5.5,"vector":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H","level":"medium"}],"updated_at":"2026-11-02T15:28:20.711507Z"},{"id":"CVE-2024-49978","title":"gso: fix udp gso fraglist segmentation after pull from frag_list","description":"In the Linux kernel, the following vulnerability has been resolved:\n\ngso: fix udp gso fraglist segmentation after pull from frag_list\n\nDetect gso fraglist skbs with corrupted geometry (see below) and\npass these to skb_segment instead of skb_segment_list, as the first\ncan segment them correctly.\n\nValid SKB_GSO_FRAGLIST skbs\n- consist of two or more segments\n- the head_skb holds the protocol headers plus first gso_size\n- one or more frag_list skbs hold exactly one segment\n- all but the last must be gso_size\n\nOptional datapath hooks such as NAT and BPF (bpf_skb_pull_data) can\nmodify these skbs, breaking these invariants.\n\nIn extreme cases they pull all data into skb linear. For UDP, this\ncauses a NULL ptr deref in __udpv4_gso_segment_list_csum at\nudp_hdr(seg-\u003enext)-\u003edest.\n\nDetect invalid geometry due to pull, by checking head_skb size.\nDon't just drop, as this may blackhole a destination. Convert to be\nable to pass to regular skb_segment.","status":"published","published":"2024-10-21T18:02:25.151Z","modified":"2026-10-28T02:31:07.264589061Z","cvss":[{"version":"3.1","score":7.5,"vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H","level":"high"}],"updated_at":"2026-11-02T15:44:43.597758Z"},{"id":"DEBIAN-CVE-2024-49978","description":"In the Linux kernel, the following vulnerability has been resolved:  gso: fix udp gso fraglist segmentation after pull from frag_list  Detect gso fraglist skbs with corrupted geometry (see below) and pass these to skb_segment instead of skb_segment_list, as the first can segment them correctly.  Valid SKB_GSO_FRAGLIST skbs - consist of two or more segments - the head_skb holds the protocol headers plus first gso_size - one or more frag_list skbs hold exactly one segment - all but the last must be gso_size  Optional datapath hooks such as NAT and BPF (bpf_skb_pull_data) can modify these skbs, breaking these invariants.  In extreme cases they pull all data into skb linear. For UDP, this causes a NULL ptr deref in __udpv4_gso_segment_list_csum at udp_hdr(seg-\u003enext)-\u003edest.  Detect invalid geometry due to pull, by checking head_skb size. Don't just drop, as this may blackhole a destination. Convert to be able to pass to regular skb_segment.","status":"published","published":"2024-10-21T18:15:18.483Z","modified":"2026-11-02T12:02:53.854010588Z","cvss":[{"version":"3.1","score":5.5,"vector":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H","level":"medium"}],"updated_at":"2026-11-02T15:45:43.798789Z"},{"id":"OESA-2024-2367","title":"kernel security update","description":"The Linux Kernel, the operating system core itself.\r\n\r\nSecurity Fix(es):\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\ndrm/amd/display: Add NULL pointer check for kzalloc\r\n\r\n[Why \u0026amp; How]\nCheck return pointer of kzalloc before using it.(CVE-2024-42122)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nmm: gup: stop abusing try_grab_folio\r\n\r\nA kernel warning was reported when pinning folio in CMA memory when\nlaunching SEV virtual machine.  The splat looks like:\r\n\r\n[  464.325306] WARNING: CPU: 13 PID: 6734 at mm/gup.c:1313 __get_user_pages+0x423/0x520\n[  464.325464] CPU: 13 PID: 6734 Comm: qemu-kvm Kdump: loaded Not tainted 6.6.33+ #6\n[  464.325477] RIP: 0010:__get_user_pages+0x423/0x520\n[  464.325515] Call Trace:\n[  464.325520]  \u0026lt;TASK\u0026gt;\n[  464.325523]  ? __get_user_pages+0x423/0x520\n[  464.325528]  ? __warn+0x81/0x130\n[  464.325536]  ? __get_user_pages+0x423/0x520\n[  464.325541]  ? report_bug+0x171/0x1a0\n[  464.325549]  ? handle_bug+0x3c/0x70\n[  464.325554]  ? exc_invalid_op+0x17/0x70\n[  464.325558]  ? asm_exc_invalid_op+0x1a/0x20\n[  464.325567]  ? __get_user_pages+0x423/0x520\n[  464.325575]  __gup_longterm_locked+0x212/0x7a0\n[  464.325583]  internal_get_user_pages_fast+0xfb/0x190\n[  464.325590]  pin_user_pages_fast+0x47/0x60\n[  464.325598]  sev_pin_memory+0xca/0x170 [kvm_amd]\n[  464.325616]  sev_mem_enc_register_region+0x81/0x130 [kvm_amd]\r\n\r\nPer the analysis done by yangge, when starting the SEV virtual machine, it\nwill call pin_user_pages_fast(..., FOLL_LONGTERM, ...) to pin the memory. \nBut the page is in CMA area, so fast GUP will fail then fallback to the\nslow path due to the longterm pinnalbe check in try_grab_folio().\r\n\r\nThe slow path will try to pin the pages then migrate them out of CMA area.\nBut the slow path also uses try_grab_folio() to pin the page, it will\nalso fail due to the same check then the above warning is triggered.\r\n\r\nIn addition, the try_grab_folio() is supposed to be used in fast path and\nit elevates folio refcount by using add ref unless zero.  We are guaranteed\nto have at least one stable reference in slow path, so the simple atomic add\ncould be used.  The performance difference should be trivial, but the\nmisuse may be confusing and misleading.\r\n\r\nRedefined try_grab_folio() to try_grab_folio_fast(), and try_grab_page()\nto try_grab_folio(), and use them in the proper paths.  This solves both\nthe abuse and the kernel warning.\r\n\r\nThe proper naming makes their usecase more clear and should prevent from\nabusing in the future.\r\n\r\npeterx said:\r\n\r\n: The user will see the pin fails, for gpu-slow it further triggers the WARN\n: right below that failure (as in the original report):\n: \n:         folio = try_grab_folio(page, page_increm - 1,\n:                                 foll_flags);\n:         if (WARN_ON_ONCE(!folio)) { \u0026lt;------------------------ here\n:                 /*\n:                         * Release the 1st page ref if the\n:                         * folio is problematic, fail hard.\n:                         */\n:                 gup_put_folio(page_folio(page), 1,\n:                                 foll_flags);\n:                 ret = -EFAULT;\n:                 goto out;\n:         }\r\n\r\n[1] https://lore.kernel.org/linux-mm/1719478388-31917-1-git-send-email-yangge1116@126.com/\r\n\r\n[shy828301@gmail.com: fix implicit declaration of function try_grab_folio_fast]\n  Link: https://lkml.kernel.org/r/CAHbLzkowMSso-4Nufc9hcMehQsK9PNz3OSu-+eniU-2Mm-xjhA@mail.gmail.com(CVE-2024-44943)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nserial: sc16is7xx: fix TX fifo corruption\r\n\r\nSometimes, when a packet is received on channel A at almost the same time\nas a packet is about to be transmitted on channel B, we observe with a\nlogic analyzer that the received packet on channel A is transmitted on\nchannel B. In other words, the Tx buffer data on channel B is corrupted\nwith data from channel A.\r\n\r\nThe problem appeared since commit 4409df5866b7 (\u0026quot;serial: sc16is7xx: change\nEFR lock to operate on each channels\u0026quot;), which changed the EFR locking to\noperate on each channel instead of chip-wise.\r\n\r\nThis commit has introduced a regression, because the EFR lock is used not\nonly to protect the EFR registers access, but also, in a very obscure and\nundocumented way, to protect access to the data buffer, which is shared by\nthe Tx and Rx handlers, but also by each channel of the IC.\r\n\r\nFix this regression first by switching to kfifo_out_linear_ptr() in\nsc16is7xx_handle_tx() to eliminate the need for a shared Rx/Tx buffer.\r\n\r\nSecondly, replace the chip-wise Rx buffer with a separate Rx buffer for\neach channel.(CVE-2024-44951)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nmemcg_write_event_control(): fix a user-triggerable oops\r\n\r\nwe are *not* guaranteed that anything past the terminating NUL\nis mapped (let alone initialized with anything sane).(CVE-2024-45021)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\npinctrl: single: fix potential NULL dereference in pcs_get_function()\r\n\r\npinmux_generic_get_function() can return NULL and the pointer \u0026apos;function\u0026apos;\nwas dereferenced without checking against NULL. Add checking of pointer\n\u0026apos;function\u0026apos; in pcs_get_function().\r\n\r\nFound by code review.(CVE-2024-46685)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nthunderbolt: Mark XDomain as unplugged when router is removed\r\n\r\nI noticed that when we do discrete host router NVM upgrade and it gets\nhot-removed from the PCIe side as a result of NVM firmware authentication,\nif there is another host connected with enabled paths we hang in tearing\nthem down. This is due to fact that the Thunderbolt networking driver\nalso tries to cleanup the paths and ends up blocking in\ntb_disconnect_xdomain_paths() waiting for the domain lock.\r\n\r\nHowever, at this point we already cleaned the paths in tb_stop() so\nthere is really no need for tb_disconnect_xdomain_paths() to do that\nanymore. Furthermore it already checks if the XDomain is unplugged and\nbails out early so take advantage of that and mark the XDomain as\nunplugged when we remove the parent router.(CVE-2024-46702)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nublk_drv: fix NULL pointer dereference in ublk_ctrl_start_recovery()\r\n\r\nWhen two UBLK_CMD_START_USER_RECOVERY commands are submitted, the\nfirst one sets \u0026apos;ubq-\u0026gt;ubq_daemon\u0026apos; to NULL, and the second one triggers\nWARN in ublk_queue_reinit() and subsequently a NULL pointer dereference\nissue.\r\n\r\nFix it by adding the check in ublk_ctrl_start_recovery() and return\nimmediately in case of zero \u0026apos;ub-\u0026gt;nr_queues_ready\u0026apos;.\r\n\r\n  BUG: kernel NULL pointer dereference, address: 0000000000000028\n  RIP: 0010:ublk_ctrl_start_recovery.constprop.0+0x82/0x180\n  Call Trace:\n   \u0026lt;TASK\u0026gt;\n   ? __die+0x20/0x70\n   ? page_fault_oops+0x75/0x170\n   ? exc_page_fault+0x64/0x140\n   ? asm_exc_page_fault+0x22/0x30\n   ? ublk_ctrl_start_recovery.constprop.0+0x82/0x180\n   ublk_ctrl_uring_cmd+0x4f7/0x6c0\n   ? pick_next_task_idle+0x26/0x40\n   io_uring_cmd+0x9a/0x1b0\n   io_issue_sqe+0x193/0x3f0\n   io_wq_submit_work+0x9b/0x390\n   io_worker_handle_work+0x165/0x360\n   io_wq_worker+0xcb/0x2f0\n   ? finish_task_switch.isra.0+0x203/0x290\n   ? finish_task_switch.isra.0+0x203/0x290\n   ? __pfx_io_wq_worker+0x10/0x10\n   ret_from_fork+0x2d/0x50\n   ? __pfx_io_wq_worker+0x10/0x10\n   ret_from_fork_asm+0x1a/0x30\n   \u0026lt;/TASK\u0026gt;(CVE-2024-46735)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nof/irq: Prevent device address out-of-bounds read in interrupt map walk\r\n\r\nWhen of_irq_parse_raw() is invoked with a device address smaller than\nthe interrupt parent node (from #address-cells property), KASAN detects\nthe following out-of-bounds read when populating the initial match table\n(dyndbg=\u0026quot;func of_irq_parse_* +p\u0026quot;):\r\n\r\n  OF: of_irq_parse_one: dev=/soc@0/picasso/watchdog, index=0\n  OF:  parent=/soc@0/pci@878000000000/gpio0@17,0, intsize=2\n  OF:  intspec=4\n  OF: of_irq_parse_raw: ipar=/soc@0/pci@878000000000/gpio0@17,0, size=2\n  OF:  -\u0026gt; addrsize=3\n  ==================================================================\n  BUG: KASAN: slab-out-of-bounds in of_irq_parse_raw+0x2b8/0x8d0\n  Read of size 4 at addr ffffff81beca5608 by task bash/764\r\n\r\n  CPU: 1 PID: 764 Comm: bash Tainted: G           O       6.1.67-484c613561-nokia_sm_arm64 #1\n  Hardware name: Unknown Unknown Product/Unknown Product, BIOS 2023.01-12.24.03-dirty 01/01/2023\n  Call trace:\n   dump_backtrace+0xdc/0x130\n   show_stack+0x1c/0x30\n   dump_stack_lvl+0x6c/0x84\n   print_report+0x150/0x448\n   kasan_report+0x98/0x140\n   __asan_load4+0x78/0xa0\n   of_irq_parse_raw+0x2b8/0x8d0\n   of_irq_parse_one+0x24c/0x270\n   parse_interrupts+0xc0/0x120\n   of_fwnode_add_links+0x100/0x2d0\n   fw_devlink_parse_fwtree+0x64/0xc0\n   device_add+0xb38/0xc30\n   of_device_add+0x64/0x90\n   of_platform_device_create_pdata+0xd0/0x170\n   of_platform_bus_create+0x244/0x600\n   of_platform_notify+0x1b0/0x254\n   blocking_notifier_call_chain+0x9c/0xd0\n   __of_changeset_entry_notify+0x1b8/0x230\n   __of_changeset_apply_notify+0x54/0xe4\n   of_overlay_fdt_apply+0xc04/0xd94\n   ...\r\n\r\n  The buggy address belongs to the object at ffffff81beca5600\n   which belongs to the cache kmalloc-128 of size 128\n  The buggy address is located 8 bytes inside of\n   128-byte region [ffffff81beca5600, ffffff81beca5680)\r\n\r\n  The buggy address belongs to the physical page:\n  page:00000000230d3d03 refcount:1 mapcount:0 mapping:0000000000000000 index:0x0 pfn:0x1beca4\n  head:00000000230d3d03 order:1 compound_mapcount:0 compound_pincount:0\n  flags: 0x8000000000010200(slab|head|zone=2)\n  raw: 8000000000010200 0000000000000000 dead000000000122 ffffff810000c300\n  raw: 0000000000000000 0000000000200020 00000001ffffffff 0000000000000000\n  page dumped because: kasan: bad access detected\r\n\r\n  Memory state around the buggy address:\n   ffffff81beca5500: 04 fc fc fc fc fc fc fc fc fc fc fc fc fc fc fc\n   ffffff81beca5580: fc fc fc fc fc fc fc fc fc fc fc fc fc fc fc fc\n  \u0026gt;ffffff81beca5600: 00 fc fc fc fc fc fc fc fc fc fc fc fc fc fc fc\n                        ^\n   ffffff81beca5680: fc fc fc fc fc fc fc fc fc fc fc fc fc fc fc fc\n   ffffff81beca5700: 00 00 00 00 00 00 fc fc fc fc fc fc fc fc fc fc\n  ==================================================================\n  OF:  -\u0026gt; got it !\r\n\r\nPrevent the out-of-bounds read by copying the device address into a\nbuffer of sufficient size.(CVE-2024-46743)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\ndrm/amd/display: Check BIOS images before it is used\r\n\r\nBIOS images may fail to load and null checks are added before they are\nused.\r\n\r\nThis fixes 6 NULL_RETURNS issues reported by Coverity.(CVE-2024-46809)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\ndrm/amd/display: Check num_valid_sets before accessing reader_wm_sets[]\r\n\r\n[WHY \u0026amp; HOW]\nnum_valid_sets needs to be checked to avoid a negative index when\naccessing reader_wm_sets[num_valid_sets - 1].\r\n\r\nThis fixes an OVERRUN issue reported by Coverity.(CVE-2024-46815)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\niommufd: Require drivers to supply the cache_invalidate_user ops\r\n\r\nIf drivers don\u0026apos;t do this then iommufd will oops invalidation ioctls with\nsomething like:\r\n\r\n  Unable to handle kernel NULL pointer dereference at virtual address 0000000000000000\n  Mem abort info:\n    ESR = 0x0000000086000004\n    EC = 0x21: IABT (current EL), IL = 32 bits\n    SET = 0, FnV = 0\n    EA = 0, S1PTW = 0\n    FSC = 0x04: level 0 translation fault\n  user pgtable: 4k pages, 48-bit VAs, pgdp=0000000101059000\n  [0000000000000000] pgd=0000000000000000, p4d=0000000000000000\n  Internal error: Oops: 0000000086000004 [#1] PREEMPT SMP\n  Modules linked in:\n  CPU: 2 PID: 371 Comm: qemu-system-aar Not tainted 6.8.0-rc7-gde77230ac23a #9\n  Hardware name: linux,dummy-virt (DT)\n  pstate: 81400809 (Nzcv daif +PAN -UAO -TCO +DIT -SSBS BTYPE=-c)\n  pc : 0x0\n  lr : iommufd_hwpt_invalidate+0xa4/0x204\n  sp : ffff800080f3bcc0\n  x29: ffff800080f3bcf0 x28: ffff0000c369b300 x27: 0000000000000000\n  x26: 0000000000000000 x25: 0000000000000000 x24: 0000000000000000\n  x23: 0000000000000000 x22: 00000000c1e334a0 x21: ffff0000c1e334a0\n  x20: ffff800080f3bd38 x19: ffff800080f3bd58 x18: 0000000000000000\n  x17: 0000000000000000 x16: 0000000000000000 x15: 0000ffff8240d6d8\n  x14: 0000000000000000 x13: 0000000000000000 x12: 0000000000000000\n  x11: 0000000000000000 x10: 0000000000000000 x9 : 0000000000000000\n  x8 : 0000001000000002 x7 : 0000fffeac1ec950 x6 : 0000000000000000\n  x5 : ffff800080f3bd78 x4 : 0000000000000003 x3 : 0000000000000002\n  x2 : 0000000000000000 x1 : ffff800080f3bcc8 x0 : ffff0000c6034d80\n  Call trace:\n   0x0\n   iommufd_fops_ioctl+0x154/0x274\n   __arm64_sys_ioctl+0xac/0xf0\n   invoke_syscall+0x48/0x110\n   el0_svc_common.constprop.0+0x40/0xe0\n   do_el0_svc+0x1c/0x28\n   el0_svc+0x34/0xb4\n   el0t_64_sync_handler+0x120/0x12c\n   el0t_64_sync+0x190/0x194\r\n\r\nAll existing drivers implement this op for nesting, this is mostly a\nbisection aid.(CVE-2024-46824)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nnet: microchip: vcap: Fix use-after-free error in kunit test\r\n\r\nThis is a clear use-after-free error. We remove it, and rely on checking\nthe return code of vcap_del_rule.(CVE-2024-46831)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  vfs: fix race between evice_inodes() and find_inode()\u0026amp;iput()  Hi, all  Recently I noticed a bug[1] in btrfs, after digged it into and I believe it\u0026apos;a race in vfs.  Let\u0026apos;s assume there\u0026apos;s a inode (ie ino 261) with i_count 1 is called by iput(), and there\u0026apos;s a concurrent thread calling generic_shutdown_super().  cpu0:                              cpu1: iput() // i_count is 1   -\u0026gt;spin_lock(inode)   -\u0026gt;dec i_count to 0   -\u0026gt;iput_final()                    generic_shutdown_super()     -\u0026gt;__inode_add_lru()               -\u0026gt;evict_inodes()       // cause some reason[2]           -\u0026gt;if (atomic_read(inode-\u0026gt;i_count)) continue;       // return before                  // inode 261 passed the above check       // list_lru_add_obj()             // and then schedule out    -\u0026gt;spin_unlock() // note here: the inode 261 // was still at sb list and hash list, // and I_FREEING|I_WILL_FREE was not been set  btrfs_iget()   // after some function calls   -\u0026gt;find_inode()     // found the above inode 261     -\u0026gt;spin_lock(inode)    // check I_FREEING|I_WILL_FREE    // and passed       -\u0026gt;__iget()     -\u0026gt;spin_unlock(inode)                // schedule back                                         -\u0026gt;spin_lock(inode)                                         // check (I_NEW|I_FREEING|I_WILL_FREE) flags,                                         // passed and set I_FREEING iput()                                  -\u0026gt;spin_unlock(inode)   -\u0026gt;spin_lock(inode)     -\u0026gt;evict()   // dec i_count to 0   -\u0026gt;iput_final()     -\u0026gt;spin_unlock()     -\u0026gt;evict()  Now, we have two threads simultaneously evicting the same inode, which may trigger the BUG(inode-\u0026gt;i_state \u0026amp; I_CLEAR) statement both within clear_inode() and iput().  To fix the bug, recheck the inode-\u0026gt;i_count after holding i_lock. Because in the most scenarios, the first check is valid, and the overhead of spin_lock() can be reduced.  If there is any misunderstanding, please let me know, thanks.  [1]: https://lore.kernel.org/linux-btrfs/000000000000eabe1d0619c48986@google.com/ [2]: The reason might be 1. SB_ACTIVE was removed or 2. mapping_shrinkable() return false when I reproduced the bug.(CVE-2024-47679)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  ep93xx: clock: Fix off by one in ep93xx_div_recalc_rate()  The psc-\u0026gt;div[] array has psc-\u0026gt;num_div elements.  These values come from when we call clk_hw_register_div().  It\u0026apos;s adc_divisors and ARRAY_SIZE(adc_divisors)) and so on.  So this condition needs to be \u0026gt;= instead of \u0026gt; to prevent an out of bounds read.(CVE-2024-47686)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  driver core: Fix a potential null-ptr-deref in module_add_driver()  Inject fault while probing of-fpga-region, if kasprintf() fails in module_add_driver(), the second sysfs_remove_link() in exit path will cause null-ptr-deref as below because kernfs_name_hash() will call strlen() with NULL driver_name.  Fix it by releasing resources based on the exit path sequence.    KASAN: null-ptr-deref in range [0x0000000000000000-0x0000000000000007]   Mem abort info:     ESR = 0x0000000096000005     EC = 0x25: DABT (current EL), IL = 32 bits     SET = 0, FnV = 0     EA = 0, S1PTW = 0     FSC = 0x05: level 1 translation fault   Data abort info:     ISV = 0, ISS = 0x00000005, ISS2 = 0x00000000     CM = 0, WnR = 0, TnD = 0, TagAccess = 0     GCS = 0, Overlay = 0, DirtyBit = 0, Xs = 0   [dfffffc000000000] address between user and kernel address ranges   Internal error: Oops: 0000000096000005 [#1] PREEMPT SMP   Dumping ftrace buffer:      (ftrace buffer empty)   Modules linked in: of_fpga_region(+) fpga_region fpga_bridge cfg80211 rfkill 8021q garp mrp stp llc ipv6 [last unloaded: of_fpga_region]   CPU: 2 UID: 0 PID: 2036 Comm: modprobe Not tainted 6.11.0-rc2-g6a0e38264012 #295   Hardware name: linux,dummy-virt (DT)   pstate: 60000005 (nZCv daif -PAN -UAO -TCO -DIT -SSBS BTYPE=--)   pc : strlen+0x24/0xb0   lr : kernfs_name_hash+0x1c/0xc4   sp : ffffffc081f97380   x29: ffffffc081f97380 x28: ffffffc081f97b90 x27: ffffff80c821c2a0   x26: ffffffedac0be418 x25: 0000000000000000 x24: ffffff80c09d2000   x23: 0000000000000000 x22: 0000000000000000 x21: 0000000000000000   x20: 0000000000000000 x19: 0000000000000000 x18: 0000000000001840   x17: 0000000000000000 x16: 0000000000000000 x15: 1ffffff8103f2e42   x14: 00000000f1f1f1f1 x13: 0000000000000004 x12: ffffffb01812d61d   x11: 1ffffff01812d61c x10: ffffffb01812d61c x9 : dfffffc000000000   x8 : 0000004fe7ed29e4 x7 : ffffff80c096b0e7 x6 : 0000000000000001   x5 : ffffff80c096b0e0 x4 : 1ffffffdb990efa2 x3 : 0000000000000000   x2 : 0000000000000000 x1 : dfffffc000000000 x0 : 0000000000000000   Call trace:    strlen+0x24/0xb0    kernfs_name_hash+0x1c/0xc4    kernfs_find_ns+0x118/0x2e8    kernfs_remove_by_name_ns+0x80/0x100    sysfs_remove_link+0x74/0xa8    module_add_driver+0x278/0x394    bus_add_driver+0x1f0/0x43c    driver_register+0xf4/0x3c0    __platform_driver_register+0x60/0x88    of_fpga_region_init+0x20/0x1000 [of_fpga_region]    do_one_initcall+0x110/0x788    do_init_module+0x1dc/0x5c8    load_module+0x3c38/0x4cac    init_module_from_file+0xd4/0x128    idempotent_init_module+0x2cc/0x528    __arm64_sys_finit_module+0xac/0x100    invoke_syscall+0x6c/0x258    el0_svc_common.constprop.0+0x160/0x22c    do_el0_svc+0x44/0x5c    el0_svc+0x48/0xb8    el0t_64_sync_handler+0x13c/0x158    el0t_64_sync+0x190/0x194   Code: f2fbffe1 a90157f4 12000802 aa0003f5 (38e16861)   ---[ end trace 0000000000000000 ]---   Kernel panic - not syncing: Oops: Fatal exception(CVE-2024-47688)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  f2fs: get rid of online repaire on corrupted directory  syzbot reports a f2fs bug as below:  kernel BUG at fs/f2fs/inode.c:896! RIP: 0010:f2fs_evict_inode+0x1598/0x15c0 fs/f2fs/inode.c:896 Call Trace:  evict+0x532/0x950 fs/inode.c:704  dispose_list fs/inode.c:747 [inline]  evict_inodes+0x5f9/0x690 fs/inode.c:797  generic_shutdown_super+0x9d/0x2d0 fs/super.c:627  kill_block_super+0x44/0x90 fs/super.c:1696  kill_f2fs_super+0x344/0x690 fs/f2fs/super.c:4898  deactivate_locked_super+0xc4/0x130 fs/super.c:473  cleanup_mnt+0x41f/0x4b0 fs/namespace.c:1373  task_work_run+0x24f/0x310 kernel/task_work.c:228  ptrace_notify+0x2d2/0x380 kernel/signal.c:2402  ptrace_report_syscall include/linux/ptrace.h:415 [inline]  ptrace_report_syscall_exit include/linux/ptrace.h:477 [inline]  syscall_exit_work+0xc6/0x190 kernel/entry/common.c:173  syscall_exit_to_user_mode_prepare kernel/entry/common.c:200 [inline]  __syscall_exit_to_user_mode_work kernel/entry/common.c:205 [inline]  syscall_exit_to_user_mode+0x279/0x370 kernel/entry/common.c:218  do_syscall_64+0x100/0x230 arch/x86/entry/common.c:89  entry_SYSCALL_64_after_hwframe+0x77/0x7f RIP: 0010:f2fs_evict_inode+0x1598/0x15c0 fs/f2fs/inode.c:896  Online repaire on corrupted directory in f2fs_lookup() can generate dirty data/meta while racing w/ readonly remount, it may leave dirty inode after filesystem becomes readonly, however, checkpoint() will skips flushing dirty inode in a state of readonly mode, result in above panic.  Let\u0026apos;s get rid of online repaire in f2fs_lookup(), and leave the work to fsck.f2fs.(CVE-2024-47690)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  f2fs: fix to avoid use-after-free in f2fs_stop_gc_thread()  syzbot reports a f2fs bug as below:   __dump_stack lib/dump_stack.c:88 [inline]  dump_stack_lvl+0x241/0x360 lib/dump_stack.c:114  print_report+0xe8/0x550 mm/kasan/report.c:491  kasan_report+0x143/0x180 mm/kasan/report.c:601  kasan_check_range+0x282/0x290 mm/kasan/generic.c:189  instrument_atomic_read_write include/linux/instrumented.h:96 [inline]  atomic_fetch_add_relaxed include/linux/atomic/atomic-instrumented.h:252 [inline]  __refcount_add include/linux/refcount.h:184 [inline]  __refcount_inc include/linux/refcount.h:241 [inline]  refcount_inc include/linux/refcount.h:258 [inline]  get_task_struct include/linux/sched/task.h:118 [inline]  kthread_stop+0xca/0x630 kernel/kthread.c:704  f2fs_stop_gc_thread+0x65/0xb0 fs/f2fs/gc.c:210  f2fs_do_shutdown+0x192/0x540 fs/f2fs/file.c:2283  f2fs_ioc_shutdown fs/f2fs/file.c:2325 [inline]  __f2fs_ioctl+0x443a/0xbe60 fs/f2fs/file.c:4325  vfs_ioctl fs/ioctl.c:51 [inline]  __do_sys_ioctl fs/ioctl.c:907 [inline]  __se_sys_ioctl+0xfc/0x170 fs/ioctl.c:893  do_syscall_x64 arch/x86/entry/common.c:52 [inline]  do_syscall_64+0xf3/0x230 arch/x86/entry/common.c:83  entry_SYSCALL_64_after_hwframe+0x77/0x7f  The root cause is below race condition, it may cause use-after-free issue in sbi-\u0026gt;gc_th pointer.  - remount  - f2fs_remount   - f2fs_stop_gc_thread    - kfree(gc_th)     - f2fs_ioc_shutdown      - f2fs_do_shutdown       - f2fs_stop_gc_thread        - kthread_stop(gc_th-\u0026gt;f2fs_gc_task)    : sbi-\u0026gt;gc_thread = NULL;  We will call f2fs_do_shutdown() in two paths: - for f2fs_ioc_shutdown() path, we should grab sb-\u0026gt;s_umount semaphore for fixing. - for f2fs_shutdown() path, it\u0026apos;s safe since caller has already grabbed sb-\u0026gt;s_umount semaphore.(CVE-2024-47691)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  RDMA/iwcm: Fix WARNING:at_kernel/workqueue.c:#check_flush_dependency  In the commit aee2424246f9 (\u0026quot;RDMA/iwcm: Fix a use-after-free related to destroying CM IDs\u0026quot;), the function flush_workqueue is invoked to flush the work queue iwcm_wq.  But at that time, the work queue iwcm_wq was created via the function alloc_ordered_workqueue without the flag WQ_MEM_RECLAIM.  Because the current process is trying to flush the whole iwcm_wq, if iwcm_wq doesn\u0026apos;t have the flag WQ_MEM_RECLAIM, verify that the current process is not reclaiming memory or running on a workqueue which doesn\u0026apos;t have the flag WQ_MEM_RECLAIM as that can break forward-progress guarantee leading to a deadlock.  The call trace is as below:  [  125.350876][ T1430] Call Trace: [  125.356281][ T1430]  \u0026lt;TASK\u0026gt; [ 125.361285][ T1430] ? __warn (kernel/panic.c:693) [ 125.367640][ T1430] ? check_flush_dependency (kernel/workqueue.c:3706 (discriminator 9)) [ 125.375689][ T1430] ? report_bug (lib/bug.c:180 lib/bug.c:219) [ 125.382505][ T1430] ? handle_bug (arch/x86/kernel/traps.c:239) [ 125.388987][ T1430] ? exc_invalid_op (arch/x86/kernel/traps.c:260 (discriminator 1)) [ 125.395831][ T1430] ? asm_exc_invalid_op (arch/x86/include/asm/idtentry.h:621) [ 125.403125][ T1430] ? check_flush_dependency (kernel/workqueue.c:3706 (discriminator 9)) [ 125.410984][ T1430] ? check_flush_dependency (kernel/workqueue.c:3706 (discriminator 9)) [ 125.418764][ T1430] __flush_workqueue (kernel/workqueue.c:3970) [ 125.426021][ T1430] ? __pfx___might_resched (kernel/sched/core.c:10151) [ 125.433431][ T1430] ? destroy_cm_id (drivers/infiniband/core/iwcm.c:375) iw_cm [ 125.441209][ T1430] ? __pfx___flush_workqueue (kernel/workqueue.c:3910) [ 125.473900][ T1430] ? _raw_spin_lock_irqsave (arch/x86/include/asm/atomic.h:107 include/linux/atomic/atomic-arch-fallback.h:2170 include/linux/atomic/atomic-instrumented.h:1302 include/asm-generic/qspinlock.h:111 include/linux/spinlock.h:187 include/linux/spinlock_api_smp.h:111 kernel/locking/spinlock.c:162) [ 125.473909][ T1430] ? __pfx__raw_spin_lock_irqsave (kernel/locking/spinlock.c:161) [ 125.482537][ T1430] _destroy_id (drivers/infiniband/core/cma.c:2044) rdma_cm [ 125.495072][ T1430] nvme_rdma_free_queue (drivers/nvme/host/rdma.c:656 drivers/nvme/host/rdma.c:650) nvme_rdma [ 125.505827][ T1430] nvme_rdma_reset_ctrl_work (drivers/nvme/host/rdma.c:2180) nvme_rdma [ 125.505831][ T1430] process_one_work (kernel/workqueue.c:3231) [ 125.515122][ T1430] worker_thread (kernel/workqueue.c:3306 kernel/workqueue.c:3393) [ 125.515127][ T1430] ? __pfx_worker_thread (kernel/workqueue.c:3339) [ 125.531837][ T1430] kthread (kernel/kthread.c:389) [ 125.539864][ T1430] ? __pfx_kthread (kernel/kthread.c:342) [ 125.550628][ T1430] ret_from_fork (arch/x86/kernel/process.c:147) [ 125.558840][ T1430] ? __pfx_kthread (kernel/kthread.c:342) [ 125.558844][ T1430] ret_from_fork_asm (arch/x86/entry/entry_64.S:257) [  125.566487][ T1430]  \u0026lt;/TASK\u0026gt; [  125.566488][ T1430] ---[ end trace 0000000000000000 ]---(CVE-2024-47696)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  nilfs2: fix potential null-ptr-deref in nilfs_btree_insert()  Patch series \u0026quot;nilfs2: fix potential issues with empty b-tree nodes\u0026quot;.  This series addresses three potential issues with empty b-tree nodes that can occur with corrupted filesystem images, including one recently discovered by syzbot.   This patch (of 3):  If a b-tree is broken on the device, and the b-tree height is greater than 2 (the level of the root node is greater than 1) even if the number of child nodes of the b-tree root is 0, a NULL pointer dereference occurs in nilfs_btree_prepare_insert(), which is called from nilfs_btree_insert().  This is because, when the number of child nodes of the b-tree root is 0, nilfs_btree_do_lookup() does not set the block buffer head in any of path[x].bp_bh, leaving it as the initial value of NULL, but if the level of the b-tree root node is greater than 1, nilfs_btree_get_nonroot_node(), which accesses the buffer memory of path[x].bp_bh, is called.  Fix this issue by adding a check to nilfs_btree_root_broken(), which performs sanity checks when reading the root node from the device, to detect this inconsistency.  Thanks to Lizhi Xu for trying to solve the bug and clarifying the cause early on.(CVE-2024-47699)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  ext4: check stripe size compatibility on remount as well  We disable stripe size in __ext4_fill_super if it is not a multiple of the cluster ratio however this check is missed when trying to remount. This can leave us with cases where stripe \u0026lt; cluster_ratio after remount:set making EXT4_B2C(sbi-\u0026gt;s_stripe) become 0 that can cause some unforeseen bugs like divide by 0.  Fix that by adding the check in remount path as well.(CVE-2024-47700)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  ext4: avoid OOB when system.data xattr changes underneath the filesystem  When looking up for an entry in an inlined directory, if e_value_offs is changed underneath the filesystem by some change in the block device, it will lead to an out-of-bounds access that KASAN detects as an UAF.  EXT4-fs (loop0): mounted filesystem 00000000-0000-0000-0000-000000000000 r/w without journal. Quota mode: none. loop0: detected capacity change from 2048 to 2047 ================================================================== BUG: KASAN: use-after-free in ext4_search_dir+0xf2/0x1c0 fs/ext4/namei.c:1500 Read of size 1 at addr ffff88803e91130f by task syz-executor269/5103  CPU: 0 UID: 0 PID: 5103 Comm: syz-executor269 Not tainted 6.11.0-rc4-syzkaller #0 Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.16.3-debian-1.16.3-2~bpo12+1 04/01/2014 Call Trace:  \u0026lt;TASK\u0026gt;  __dump_stack lib/dump_stack.c:93 [inline]  dump_stack_lvl+0x241/0x360 lib/dump_stack.c:119  print_address_description mm/kasan/report.c:377 [inline]  print_report+0x169/0x550 mm/kasan/report.c:488  kasan_report+0x143/0x180 mm/kasan/report.c:601  ext4_search_dir+0xf2/0x1c0 fs/ext4/namei.c:1500  ext4_find_inline_entry+0x4be/0x5e0 fs/ext4/inline.c:1697  __ext4_find_entry+0x2b4/0x1b30 fs/ext4/namei.c:1573  ext4_lookup_entry fs/ext4/namei.c:1727 [inline]  ext4_lookup+0x15f/0x750 fs/ext4/namei.c:1795  lookup_one_qstr_excl+0x11f/0x260 fs/namei.c:1633  filename_create+0x297/0x540 fs/namei.c:3980  do_symlinkat+0xf9/0x3a0 fs/namei.c:4587  __do_sys_symlinkat fs/namei.c:4610 [inline]  __se_sys_symlinkat fs/namei.c:4607 [inline]  __x64_sys_symlinkat+0x95/0xb0 fs/namei.c:4607  do_syscall_x64 arch/x86/entry/common.c:52 [inline]  do_syscall_64+0xf3/0x230 arch/x86/entry/common.c:83  entry_SYSCALL_64_after_hwframe+0x77/0x7f RIP: 0033:0x7f3e73ced469 Code: 28 00 00 00 75 05 48 83 c4 28 c3 e8 21 18 00 00 90 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 \u0026lt;48\u0026gt; 3d 01 f0 ff ff 73 01 c3 48 c7 c1 b8 ff ff ff f7 d8 64 89 01 48 RSP: 002b:00007fff4d40c258 EFLAGS: 00000246 ORIG_RAX: 000000000000010a RAX: ffffffffffffffda RBX: 0032656c69662f2e RCX: 00007f3e73ced469 RDX: 0000000020000200 RSI: 00000000ffffff9c RDI: 00000000200001c0 RBP: 0000000000000000 R08: 00007fff4d40c290 R09: 00007fff4d40c290 R10: 0023706f6f6c2f76 R11: 0000000000000246 R12: 00007fff4d40c27c R13: 0000000000000003 R14: 431bde82d7b634db R15: 00007fff4d40c2b0  \u0026lt;/TASK\u0026gt;  Calling ext4_xattr_ibody_find right after reading the inode with ext4_get_inode_loc will lead to a check of the validity of the xattrs, avoiding this problem.(CVE-2024-47701)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  bpf, lsm: Add check for BPF LSM return value  A bpf prog returning a positive number attached to file_alloc_security hook makes kernel panic.  This happens because file system can not filter out the positive number returned by the LSM prog using IS_ERR, and misinterprets this positive number as a file pointer.  Given that hook file_alloc_security never returned positive number before the introduction of BPF LSM, and other BPF LSM hooks may encounter similar issues, this patch adds LSM return value check in verifier, to ensure no unexpected value is returned.(CVE-2024-47703)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  drm/amd/display: Check link_res-\u0026gt;hpo_dp_link_enc before using it  [WHAT \u0026amp; HOW] Functions dp_enable_link_phy and dp_disable_link_phy can pass link_res without initializing hpo_dp_link_enc and it is necessary to check for null before dereferencing.  This fixes 2 FORWARD_NULL issues reported by Coverity.(CVE-2024-47704)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  block: fix potential invalid pointer dereference in blk_add_partition  The blk_add_partition() function initially used a single if-condition (IS_ERR(part)) to check for errors when adding a partition. This was modified to handle the specific case of -ENXIO separately, allowing the function to proceed without logging the error in this case. However, this change unintentionally left a path where md_autodetect_dev() could be called without confirming that part is a valid pointer.  This commit separates the error handling logic by splitting the initial if-condition, improving code readability and handling specific error scenarios explicitly. The function now distinguishes the general error case from -ENXIO without altering the existing behavior of md_autodetect_dev() calls.(CVE-2024-47705)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  iommufd: Protect against overflow of ALIGN() during iova allocation  Userspace can supply an iova and uptr such that the target iova alignment becomes really big and ALIGN() overflows which corrupts the selected area range during allocation. CONFIG_IOMMUFD_TEST can detect this:     WARNING: CPU: 1 PID: 5092 at drivers/iommu/iommufd/io_pagetable.c:268 iopt_alloc_area_pages drivers/iommu/iommufd/io_pagetable.c:268 [inline]    WARNING: CPU: 1 PID: 5092 at drivers/iommu/iommufd/io_pagetable.c:268 iopt_map_pages+0xf95/0x1050 drivers/iommu/iommufd/io_pagetable.c:352    Modules linked in:    CPU: 1 PID: 5092 Comm: syz-executor294 Not tainted 6.10.0-rc5-syzkaller-00294-g3ffea9a7a6f7 #0    Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 06/07/2024    RIP: 0010:iopt_alloc_area_pages drivers/iommu/iommufd/io_pagetable.c:268 [inline]    RIP: 0010:iopt_map_pages+0xf95/0x1050 drivers/iommu/iommufd/io_pagetable.c:352    Code: fc e9 a4 f3 ff ff e8 1a 8b 4c fc 41 be e4 ff ff ff e9 8a f3 ff ff e8 0a 8b 4c fc 90 0f 0b 90 e9 37 f5 ff ff e8 fc 8a 4c fc 90 \u0026lt;0f\u0026gt; 0b 90 e9 68 f3 ff ff 48 c7 c1 ec 82 ad 8f 80 e1 07 80 c1 03 38    RSP: 0018:ffffc90003ebf9e0 EFLAGS: 00010293    RAX: ffffffff85499fa4 RBX: 00000000ffffffef RCX: ffff888079b49e00    RDX: 0000000000000000 RSI: 00000000ffffffef RDI: 0000000000000000    RBP: ffffc90003ebfc50 R08: ffffffff85499b30 R09: ffffffff85499942    R10: 0000000000000002 R11: ffff888079b49e00 R12: ffff8880228e0010    R13: 0000000000000000 R14: 1ffff920007d7f68 R15: ffffc90003ebfd00    FS:  000055557d760380(0000) GS:ffff8880b9500000(0000) knlGS:0000000000000000    CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033    CR2: 00000000005fdeb8 CR3: 000000007404a000 CR4: 00000000003506f0    DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000    DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400    Call Trace:     \u0026lt;TASK\u0026gt;     iommufd_ioas_copy+0x610/0x7b0 drivers/iommu/iommufd/ioas.c:274     iommufd_fops_ioctl+0x4d9/0x5a0 drivers/iommu/iommufd/main.c:421     vfs_ioctl fs/ioctl.c:51 [inline]     __do_sys_ioctl fs/ioctl.c:907 [inline]     __se_sys_ioctl+0xfc/0x170 fs/ioctl.c:893     do_syscall_x64 arch/x86/entry/common.c:52 [inline]     do_syscall_64+0xf3/0x230 arch/x86/entry/common.c:83     entry_SYSCALL_64_after_hwframe+0x77/0x7f  Cap the automatic alignment to the huge page size, which is probably a better idea overall. Huge automatic alignments can fragment and chew up the available IOVA space without any reason.(CVE-2024-47719)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  x86/tdx: Fix \u0026quot;in-kernel MMIO\u0026quot; check  TDX only supports kernel-initiated MMIO operations. The handle_mmio() function checks if the #VE exception occurred in the kernel and rejects the operation if it did not.  However, userspace can deceive the kernel into performing MMIO on its behalf. For example, if userspace can point a syscall to an MMIO address, syscall does get_user() or put_user() on it, triggering MMIO #VE. The kernel will treat the #VE as in-kernel MMIO.  Ensure that the target MMIO address is within the kernel before decoding instruction.(CVE-2024-47727)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  padata: use integer wrap around to prevent deadlock on seq_nr overflow  When submitting more than 2^32 padata objects to padata_do_serial, the current sorting implementation incorrectly sorts padata objects with overflowed seq_nr, causing them to be placed before existing objects in the reorder list. This leads to a deadlock in the serialization process as padata_find_next cannot match padata-\u0026gt;seq_nr and pd-\u0026gt;processed because the padata instance with overflowed seq_nr will be selected next.  To fix this, we use an unsigned integer wrap around to correctly sort padata objects in scenarios with integer overflow.(CVE-2024-47739)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  firmware_loader: Block path traversal  Most firmware names are hardcoded strings, or are constructed from fairly constrained format strings where the dynamic parts are just some hex numbers or such.  However, there are a couple codepaths in the kernel where firmware file names contain string components that are passed through from a device or semi-privileged userspace; the ones I could find (not counting interfaces that require root privileges) are:   - lpfc_sli4_request_firmware_update() seems to construct the firmware    filename from \u0026quot;ModelName\u0026quot;, a string that was previously parsed out of    some descriptor (\u0026quot;Vital Product Data\u0026quot;) in lpfc_fill_vpd()  - nfp_net_fw_find() seems to construct a firmware filename from a model    name coming from nfp_hwinfo_lookup(pf-\u0026gt;hwinfo, \u0026quot;nffw.partno\u0026quot;), which I    think parses some descriptor that was read from the device.    (But this case likely isn\u0026apos;t exploitable because the format string looks    like \u0026quot;netronome/nic_%s\u0026quot;, and there shouldn\u0026apos;t be any *folders* starting    with \u0026quot;netronome/nic_\u0026quot;. The previous case was different because there,    the \u0026quot;%s\u0026quot; is *at the start* of the format string.)  - module_flash_fw_schedule() is reachable from the    ETHTOOL_MSG_MODULE_FW_FLASH_ACT netlink command, which is marked as    GENL_UNS_ADMIN_PERM (meaning CAP_NET_ADMIN inside a user namespace is    enough to pass the privilege check), and takes a userspace-provided    firmware name.    (But I think to reach this case, you need to have CAP_NET_ADMIN over a    network namespace that a special kind of ethernet device is mapped into,    so I think this is not a viable attack path in practice.)  Fix it by rejecting any firmware names containing \u0026quot;..\u0026quot; path components.  For what it\u0026apos;s worth, I went looking and haven\u0026apos;t found any USB device drivers that use the firmware loader dangerously.(CVE-2024-47742)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  KVM: Use dedicated mutex to protect kvm_usage_count to avoid deadlock  Use a dedicated mutex to guard kvm_usage_count to fix a potential deadlock on x86 due to a chain of locks and SRCU synchronizations.  Translating the below lockdep splat, CPU1 #6 will wait on CPU0 #1, CPU0 #8 will wait on CPU2 #3, and CPU2 #7 will wait on CPU1 #4 (if there\u0026apos;s a writer, due to the fairness of r/w semaphores).      CPU0                     CPU1                     CPU2 1   lock(\u0026amp;kvm-\u0026gt;slots_lock); 2                                                     lock(\u0026amp;vcpu-\u0026gt;mutex); 3                                                     lock(\u0026amp;kvm-\u0026gt;srcu); 4                            lock(cpu_hotplug_lock); 5                            lock(kvm_lock); 6                            lock(\u0026amp;kvm-\u0026gt;slots_lock); 7                                                     lock(cpu_hotplug_lock); 8   sync(\u0026amp;kvm-\u0026gt;srcu);  Note, there are likely more potential deadlocks in KVM x86, e.g. the same pattern of taking cpu_hotplug_lock outside of kvm_lock likely exists with __kvmclock_cpufreq_notifier():    cpuhp_cpufreq_online()   |   -\u0026gt; cpufreq_online()      |      -\u0026gt; cpufreq_gov_performance_limits()         |         -\u0026gt; __cpufreq_driver_target()            |            -\u0026gt; __target_index()               |               -\u0026gt; cpufreq_freq_transition_begin()                  |                  -\u0026gt; cpufreq_notify_transition()                     |                     -\u0026gt; ... __kvmclock_cpufreq_notifier()  But, actually triggering such deadlocks is beyond rare due to the combination of dependencies and timings involved.  E.g. the cpufreq notifier is only used on older CPUs without a constant TSC, mucking with the NX hugepage mitigation while VMs are running is very uncommon, and doing so while also onlining/offlining a CPU (necessary to generate contention on cpu_hotplug_lock) would be even more unusual.  The most robust solution to the general cpu_hotplug_lock issue is likely to switch vm_list to be an RCU-protected list, e.g. so that x86\u0026apos;s cpufreq notifier doesn\u0026apos;t to take kvm_lock.  For now, settle for fixing the most blatant deadlock, as switching to an RCU-protected list is a much more involved change, but add a comment in locking.rst to call out that care needs to be taken when walking holding kvm_lock and walking vm_list.    ======================================================   WARNING: possible circular locking dependency detected   6.10.0-smp--c257535a0c9d-pip #330 Tainted: G S         O   ------------------------------------------------------   tee/35048 is trying to acquire lock:   ff6a80eced71e0a8 (\u0026amp;kvm-\u0026gt;slots_lock){+.+.}-{3:3}, at: set_nx_huge_pages+0x179/0x1e0 [kvm]    but task is already holding lock:   ffffffffc07abb08 (kvm_lock){+.+.}-{3:3}, at: set_nx_huge_pages+0x14a/0x1e0 [kvm]    which lock already depends on the new lock.     the existing dependency chain (in reverse order) is:    -\u0026gt; #3 (kvm_lock){+.+.}-{3:3}:          __mutex_lock+0x6a/0xb40          mutex_lock_nested+0x1f/0x30          kvm_dev_ioctl+0x4fb/0xe50 [kvm]          __se_sys_ioctl+0x7b/0xd0          __x64_sys_ioctl+0x21/0x30          x64_sys_call+0x15d0/0x2e60          do_syscall_64+0x83/0x160          entry_SYSCALL_64_after_hwframe+0x76/0x7e    -\u0026gt; #2 (cpu_hotplug_lock){++++}-{0:0}:          cpus_read_lock+0x2e/0xb0          static_key_slow_inc+0x16/0x30          kvm_lapic_set_base+0x6a/0x1c0 [kvm]          kvm_set_apic_base+0x8f/0xe0 [kvm]          kvm_set_msr_common+0x9ae/0xf80 [kvm]          vmx_set_msr+0xa54/0xbe0 [kvm_intel]          __kvm_set_msr+0xb6/0x1a0 [kvm]          kvm_arch_vcpu_ioctl+0xeca/0x10c0 [kvm]          kvm_vcpu_ioctl+0x485/0x5b0 [kvm]          __se_sys_ioctl+0x7b/0xd0          __x64_sys_ioctl+0x21/0x30          x64_sys_call+0x15d0/0x2e60          do_syscall_64+0x83/0x160          entry_SYSCALL_64_after_hwframe+0x76/0x7e    -\u0026gt; #1 (\u0026amp;kvm-\u0026gt;srcu){.+.+}-{0:0}:          __synchronize_srcu+0x44/0x1a0        ---truncated---(CVE-2024-47744)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  vhost_vdpa: assign irq bypass producer token correctly  We used to call irq_bypass_unregister_producer() in vhost_vdpa_setup_vq_irq() which is problematic as we don\u0026apos;t know if the token pointer is still valid or not.  Actually, we use the eventfd_ctx as the token so the life cycle of the token should be bound to the VHOST_SET_VRING_CALL instead of vhost_vdpa_setup_vq_irq() which could be called by set_status().  Fixing this by setting up irq bypass producer\u0026apos;s token when handling VHOST_SET_VRING_CALL and un-registering the producer before calling vhost_vring_ioctl() to prevent a possible use after free as eventfd could have been released in vhost_vring_ioctl(). And such registering and unregistering will only be done if DRIVER_OK is set.(CVE-2024-47748)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  PCI: kirin: Fix buffer overflow in kirin_pcie_parse_port()  Within kirin_pcie_parse_port(), the pcie-\u0026gt;num_slots is compared to pcie-\u0026gt;gpio_id_reset size (MAX_PCI_SLOTS) which is correct and would lead to an overflow.  Thus, fix condition to pcie-\u0026gt;num_slots + 1 \u0026gt;= MAX_PCI_SLOTS and move pcie-\u0026gt;num_slots increment below the if-statement to avoid out-of-bounds array access.  Found by Linux Verification Center (linuxtesting.org) with SVACE.  [kwilczynski: commit log](CVE-2024-47751)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  media: mediatek: vcodec: Fix H264 stateless decoder smatch warning  Fix a smatch static checker warning on vdec_h264_req_if.c. Which leads to a kernel crash when fb is NULL.(CVE-2024-47752)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  media: mediatek: vcodec: Fix VP8 stateless decoder smatch warning  Fix a smatch static checker warning on vdec_vp8_req_if.c. Which leads to a kernel crash when fb is NULL.(CVE-2024-47753)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  PCI: keystone: Fix if-statement expression in ks_pcie_quirk()  This code accidentally uses \u0026amp;\u0026amp; where || was intended.  It potentially results in a NULL dereference.  Thus, fix the if-statement expression to use the correct condition.  [kwilczynski: commit log](CVE-2024-47756)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  bpf: correctly handle malformed BPF_CORE_TYPE_ID_LOCAL relos  In case of malformed relocation record of kind BPF_CORE_TYPE_ID_LOCAL referencing a non-existing BTF type, function bpf_core_calc_relo_insn would cause a null pointer deference.  Fix this by adding a proper check upper in call stack, as malformed relocation records could be passed from user space.  Simplest reproducer is a program:      r0 = 0     exit  With a single relocation record:      .insn_off = 0,          /* patch first instruction */     .type_id = 100500,      /* this type id does not exist */     .access_str_off = 6,    /* offset of string \u0026quot;0\u0026quot; */     .kind = BPF_CORE_TYPE_ID_LOCAL,  See the link for original reproducer or next commit for a test case.(CVE-2024-49850)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  scsi: elx: libefc: Fix potential use after free in efc_nport_vport_del()  The kref_put() function will call nport-\u0026gt;release if the refcount drops to zero.  The nport-\u0026gt;release release function is _efc_nport_free() which frees \u0026quot;nport\u0026quot;.  But then we dereference \u0026quot;nport\u0026quot; on the next line which is a use after free.  Re-order these lines to avoid the use after free.(CVE-2024-49852)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  efistub/tpm: Use ACPI reclaim memory for event log to avoid corruption  The TPM event log table is a Linux specific construct, where the data produced by the GetEventLog() boot service is cached in memory, and passed on to the OS using an EFI configuration table.  The use of EFI_LOADER_DATA here results in the region being left unreserved in the E820 memory map constructed by the EFI stub, and this is the memory description that is passed on to the incoming kernel by kexec, which is therefore unaware that the region should be reserved.  Even though the utility of the TPM2 event log after a kexec is questionable, any corruption might send the parsing code off into the weeds and crash the kernel. So let\u0026apos;s use EFI_ACPI_RECLAIM_MEMORY instead, which is always treated as reserved by the E820 conversion logic.(CVE-2024-49858)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  f2fs: fix to check atomic_file in f2fs ioctl interfaces  Some f2fs ioctl interfaces like f2fs_ioc_set_pin_file(), f2fs_move_file_range(), and f2fs_defragment_range() missed to check atomic_write status, which may cause potential race issue, fix it.(CVE-2024-49859)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  ACPI: sysfs: validate return type of _STR method  Only buffer objects are valid return values of _STR.  If something else is returned description_show() will access invalid memory.(CVE-2024-49860)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  powercap: intel_rapl: Fix off by one in get_rpi()  The rp-\u0026gt;priv-\u0026gt;rpi array is either rpi_msr or rpi_tpmi which have NR_RAPL_PRIMITIVES number of elements.  Thus the \u0026gt; needs to be \u0026gt;= to prevent an off by one access.(CVE-2024-49862)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  cachefiles: fix dentry leak in cachefiles_open_file()  A dentry leak may be caused when a lookup cookie and a cull are concurrent:              P1             |             P2 ----------------------------------------------------------- cachefiles_lookup_cookie   cachefiles_look_up_object     lookup_one_positive_unlocked      // get dentry                             cachefiles_cull                               inode-\u0026gt;i_flags |= S_KERNEL_FILE;     cachefiles_open_file       cachefiles_mark_inode_in_use         __cachefiles_mark_inode_in_use           can_use = false           if (!(inode-\u0026gt;i_flags \u0026amp; S_KERNEL_FILE))             can_use = true    return false         return false         // Returns an error but doesn\u0026apos;t put dentry  After that the following WARNING will be triggered when the backend folder is umounted:  ================================================================== BUG: Dentry 000000008ad87947{i=7a,n=Dx_1_1.img}  still in use (1) [unmount of ext4 sda] WARNING: CPU: 4 PID: 359261 at fs/dcache.c:1767 umount_check+0x5d/0x70 CPU: 4 PID: 359261 Comm: umount Not tainted 6.6.0-dirty #25 RIP: 0010:umount_check+0x5d/0x70 Call Trace:  \u0026lt;TASK\u0026gt;  d_walk+0xda/0x2b0  do_one_tree+0x20/0x40  shrink_dcache_for_umount+0x2c/0x90  generic_shutdown_super+0x20/0x160  kill_block_super+0x1a/0x40  ext4_kill_sb+0x22/0x40  deactivate_locked_super+0x35/0x80  cleanup_mnt+0x104/0x160 ==================================================================  Whether cachefiles_open_file() returns true or false, the reference count obtained by lookup_positive_unlocked() in cachefiles_look_up_object() should be released.  Therefore release that reference count in cachefiles_look_up_object() to fix the above issue and simplify the code.(CVE-2024-49870)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  Input: adp5589-keys - fix NULL pointer dereference  We register a devm action to call adp5589_clear_config() and then pass the i2c client as argument so that we can call i2c_get_clientdata() in order to get our device object. However, i2c_set_clientdata() is only being set at the end of the probe function which means that we\u0026apos;ll get a NULL pointer dereference in case the probe function fails early.(CVE-2024-49871)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  i3c: master: svc: Fix use after free vulnerability in svc_i3c_master Driver Due to Race Condition  In the svc_i3c_master_probe function, \u0026amp;master-\u0026gt;hj_work is bound with svc_i3c_master_hj_work, \u0026amp;master-\u0026gt;ibi_work is bound with svc_i3c_master_ibi_work. And svc_i3c_master_ibi_work  can start the hj_work, svc_i3c_master_irq_handler can start the ibi_work.  If we remove the module which will call svc_i3c_master_remove to make cleanup, it will free master-\u0026gt;base through i3c_master_unregister while the work mentioned above will be used. The sequence of operations that may lead to a UAF bug is as follows:  CPU0                                         CPU1                                      | svc_i3c_master_hj_work svc_i3c_master_remove               | i3c_master_unregister(\u0026amp;master-\u0026gt;base)| device_unregister(\u0026amp;master-\u0026gt;dev)     | device_release                      | //free master-\u0026gt;base                 |                                     | i3c_master_do_daa(\u0026amp;master-\u0026gt;base)                                     | //use master-\u0026gt;base  Fix it by ensuring that the work is canceled before proceeding with the cleanup in svc_i3c_master_remove.(CVE-2024-49874)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  ocfs2: fix possible null-ptr-deref in ocfs2_set_buffer_uptodate  When doing cleanup, if flags without OCFS2_BH_READAHEAD, it may trigger NULL pointer dereference in the following ocfs2_set_buffer_uptodate() if bh is NULL.(CVE-2024-49877)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  drm: omapdrm: Add missing check for alloc_ordered_workqueue  As it may return NULL pointer and cause NULL pointer dereference. Add check for the return value of alloc_ordered_workqueue.(CVE-2024-49879)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  ext4: update orig_path in ext4_find_extent()  In ext4_find_extent(), if the path is not big enough, we free it and set *orig_path to NULL. But after reallocating and successfully initializing the path, we don\u0026apos;t update *orig_path, in which case the caller gets a valid path but a NULL ppath, and this may cause a NULL pointer dereference or a path memory leak. For example:  ext4_split_extent   path = *ppath = 2000   ext4_find_extent     if (depth \u0026gt; path[0].p_maxdepth)       kfree(path = 2000);       *orig_path = path = NULL;       path = kcalloc() = 3000   ext4_split_extent_at(*ppath = NULL)     path = *ppath;     ex = path[depth].p_ext;     // NULL pointer dereference!  ================================================================== BUG: kernel NULL pointer dereference, address: 0000000000000010 CPU: 6 UID: 0 PID: 576 Comm: fsstress Not tainted 6.11.0-rc2-dirty #847 RIP: 0010:ext4_split_extent_at+0x6d/0x560 Call Trace:  \u0026lt;TASK\u0026gt;  ext4_split_extent.isra.0+0xcb/0x1b0  ext4_ext_convert_to_initialized+0x168/0x6c0  ext4_ext_handle_unwritten_extents+0x325/0x4d0  ext4_ext_map_blocks+0x520/0xdb0  ext4_map_blocks+0x2b0/0x690  ext4_iomap_begin+0x20e/0x2c0 [...] ==================================================================  Therefore, *orig_path is updated when the extent lookup succeeds, so that the caller can safely use path or *ppath.(CVE-2024-49881)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  ext4: fix double brelse() the buffer of the extents path  In ext4_ext_try_to_merge_up(), set path[1].p_bh to NULL after it has been released, otherwise it may be released twice. An example of what triggers this is as follows:    split2    map    split1 |--------|-------|--------|  ext4_ext_map_blocks  ext4_ext_handle_unwritten_extents   ext4_split_convert_extents    // path-\u0026gt;p_depth == 0    ext4_split_extent      // 1. do split1      ext4_split_extent_at        |ext4_ext_insert_extent        |  ext4_ext_create_new_leaf        |    ext4_ext_grow_indepth        |      le16_add_cpu(\u0026amp;neh-\u0026gt;eh_depth, 1)        |    ext4_find_extent        |      // return -ENOMEM        |// get error and try zeroout        |path = ext4_find_extent        |  path-\u0026gt;p_depth = 1        |ext4_ext_try_to_merge        |  ext4_ext_try_to_merge_up        |    path-\u0026gt;p_depth = 0        |    brelse(path[1].p_bh)  ---\u0026gt; not set to NULL here        |// zeroout success      // 2. update path      ext4_find_extent      // 3. do split2      ext4_split_extent_at        ext4_ext_insert_extent          ext4_ext_create_new_leaf            ext4_ext_grow_indepth              le16_add_cpu(\u0026amp;neh-\u0026gt;eh_depth, 1)            ext4_find_extent              path[0].p_bh = NULL;              path-\u0026gt;p_depth = 1              read_extent_tree_block  ---\u0026gt; return err              // path[1].p_bh is still the old value              ext4_free_ext_path                ext4_ext_drop_refs                  // path-\u0026gt;p_depth == 1                  brelse(path[1].p_bh)  ---\u0026gt; brelse a buffer twice  Finally got the following WARRNING when removing the buffer from lru:  ============================================ VFS: brelse: Trying to free free buffer WARNING: CPU: 2 PID: 72 at fs/buffer.c:1241 __brelse+0x58/0x90 CPU: 2 PID: 72 Comm: kworker/u19:1 Not tainted 6.9.0-dirty #716 RIP: 0010:__brelse+0x58/0x90 Call Trace:  \u0026lt;TASK\u0026gt;  __find_get_block+0x6e7/0x810  bdev_getblk+0x2b/0x480  __ext4_get_inode_loc+0x48a/0x1240  ext4_get_inode_loc+0xb2/0x150  ext4_reserve_inode_write+0xb7/0x230  __ext4_mark_inode_dirty+0x144/0x6a0  ext4_ext_insert_extent+0x9c8/0x3230  ext4_ext_map_blocks+0xf45/0x2dc0  ext4_map_blocks+0x724/0x1700  ext4_do_writepages+0x12d6/0x2a70 [...] ============================================(CVE-2024-49882)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  ext4: aovid use-after-free in ext4_ext_insert_extent()  As Ojaswin mentioned in Link, in ext4_ext_insert_extent(), if the path is reallocated in ext4_ext_create_new_leaf(), we\u0026apos;ll use the stale path and cause UAF. Below is a sample trace with dummy values:  ext4_ext_insert_extent   path = *ppath = 2000   ext4_ext_create_new_leaf(ppath)     ext4_find_extent(ppath)       path = *ppath = 2000       if (depth \u0026gt; path[0].p_maxdepth)             kfree(path = 2000);             *ppath = path = NULL;       path = kcalloc() = 3000       *ppath = 3000;       return path;   /* here path is still 2000, UAF! */   eh = path[depth].p_hdr  ================================================================== BUG: KASAN: slab-use-after-free in ext4_ext_insert_extent+0x26d4/0x3330 Read of size 8 at addr ffff8881027bf7d0 by task kworker/u36:1/179 CPU: 3 UID: 0 PID: 179 Comm: kworker/u6:1 Not tainted 6.11.0-rc2-dirty #866 Call Trace:  \u0026lt;TASK\u0026gt;  ext4_ext_insert_extent+0x26d4/0x3330  ext4_ext_map_blocks+0xe22/0x2d40  ext4_map_blocks+0x71e/0x1700  ext4_do_writepages+0x1290/0x2800 [...]  Allocated by task 179:  ext4_find_extent+0x81c/0x1f70  ext4_ext_map_blocks+0x146/0x2d40  ext4_map_blocks+0x71e/0x1700  ext4_do_writepages+0x1290/0x2800  ext4_writepages+0x26d/0x4e0  do_writepages+0x175/0x700 [...]  Freed by task 179:  kfree+0xcb/0x240  ext4_find_extent+0x7c0/0x1f70  ext4_ext_insert_extent+0xa26/0x3330  ext4_ext_map_blocks+0xe22/0x2d40  ext4_map_blocks+0x71e/0x1700  ext4_do_writepages+0x1290/0x2800  ext4_writepages+0x26d/0x4e0  do_writepages+0x175/0x700 [...] ==================================================================  So use *ppath to update the path to avoid the above problem.(CVE-2024-49883)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  ext4: fix slab-use-after-free in ext4_split_extent_at()  We hit the following use-after-free:  ================================================================== BUG: KASAN: slab-use-after-free in ext4_split_extent_at+0xba8/0xcc0 Read of size 2 at addr ffff88810548ed08 by task kworker/u20:0/40 CPU: 0 PID: 40 Comm: kworker/u20:0 Not tainted 6.9.0-dirty #724 Call Trace:  \u0026lt;TASK\u0026gt;  kasan_report+0x93/0xc0  ext4_split_extent_at+0xba8/0xcc0  ext4_split_extent.isra.0+0x18f/0x500  ext4_split_convert_extents+0x275/0x750  ext4_ext_handle_unwritten_extents+0x73e/0x1580  ext4_ext_map_blocks+0xe20/0x2dc0  ext4_map_blocks+0x724/0x1700  ext4_do_writepages+0x12d6/0x2a70 [...]  Allocated by task 40:  __kmalloc_noprof+0x1ac/0x480  ext4_find_extent+0xf3b/0x1e70  ext4_ext_map_blocks+0x188/0x2dc0  ext4_map_blocks+0x724/0x1700  ext4_do_writepages+0x12d6/0x2a70 [...]  Freed by task 40:  kfree+0xf1/0x2b0  ext4_find_extent+0xa71/0x1e70  ext4_ext_insert_extent+0xa22/0x3260  ext4_split_extent_at+0x3ef/0xcc0  ext4_split_extent.isra.0+0x18f/0x500  ext4_split_convert_extents+0x275/0x750  ext4_ext_handle_unwritten_extents+0x73e/0x1580  ext4_ext_map_blocks+0xe20/0x2dc0  ext4_map_blocks+0x724/0x1700  ext4_do_writepages+0x12d6/0x2a70 [...] ==================================================================  The flow of issue triggering is as follows:  ext4_split_extent_at   path = *ppath   ext4_ext_insert_extent(ppath)     ext4_ext_create_new_leaf(ppath)       ext4_find_extent(orig_path)         path = *orig_path         read_extent_tree_block           // return -ENOMEM or -EIO         ext4_free_ext_path(path)           kfree(path)         *orig_path = NULL   a. If err is -ENOMEM:   ext4_ext_dirty(path + path-\u0026gt;p_depth)   // path use-after-free !!!   b. If err is -EIO and we have EXT_DEBUG defined:   ext4_ext_show_leaf(path)     eh = path[depth].p_hdr     // path also use-after-free !!!  So when trying to zeroout or fix the extent length, call ext4_find_extent() to update the path.  In addition we use *ppath directly as an ext4_ext_show_leaf() input to avoid possible use-after-free when EXT_DEBUG is defined, and to avoid unnecessary path updates.(CVE-2024-49884)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  platform/x86: ISST: Fix the KASAN report slab-out-of-bounds bug  Attaching SST PCI device to VM causes \u0026quot;BUG: KASAN: slab-out-of-bounds\u0026quot;. kasan report: [   19.411889] ================================================================== [   19.413702] BUG: KASAN: slab-out-of-bounds in _isst_if_get_pci_dev+0x3d5/0x400 [isst_if_common] [   19.415634] Read of size 8 at addr ffff888829e65200 by task cpuhp/16/113 [   19.417368] [   19.418627] CPU: 16 PID: 113 Comm: cpuhp/16 Tainted: G            E      6.9.0 #10 [   19.420435] Hardware name: VMware, Inc. VMware20,1/440BX Desktop Reference Platform, BIOS VMW201.00V.20192059.B64.2207280713 07/28/2022 [   19.422687] Call Trace: [   19.424091]  \u0026lt;TASK\u0026gt; [   19.425448]  dump_stack_lvl+0x5d/0x80 [   19.426963]  ? _isst_if_get_pci_dev+0x3d5/0x400 [isst_if_common] [   19.428694]  print_report+0x19d/0x52e [   19.430206]  ? __pfx__raw_spin_lock_irqsave+0x10/0x10 [   19.431837]  ? _isst_if_get_pci_dev+0x3d5/0x400 [isst_if_common] [   19.433539]  kasan_report+0xf0/0x170 [   19.435019]  ? _isst_if_get_pci_dev+0x3d5/0x400 [isst_if_common] [   19.436709]  _isst_if_get_pci_dev+0x3d5/0x400 [isst_if_common] [   19.438379]  ? __pfx_sched_clock_cpu+0x10/0x10 [   19.439910]  isst_if_cpu_online+0x406/0x58f [isst_if_common] [   19.441573]  ? __pfx_isst_if_cpu_online+0x10/0x10 [isst_if_common] [   19.443263]  ? ttwu_queue_wakelist+0x2c1/0x360 [   19.444797]  cpuhp_invoke_callback+0x221/0xec0 [   19.446337]  cpuhp_thread_fun+0x21b/0x610 [   19.447814]  ? __pfx_cpuhp_thread_fun+0x10/0x10 [   19.449354]  smpboot_thread_fn+0x2e7/0x6e0 [   19.450859]  ? __pfx_smpboot_thread_fn+0x10/0x10 [   19.452405]  kthread+0x29c/0x350 [   19.453817]  ? __pfx_kthread+0x10/0x10 [   19.455253]  ret_from_fork+0x31/0x70 [   19.456685]  ? __pfx_kthread+0x10/0x10 [   19.458114]  ret_from_fork_asm+0x1a/0x30 [   19.459573]  \u0026lt;/TASK\u0026gt; [   19.460853] [   19.462055] Allocated by task 1198: [   19.463410]  kasan_save_stack+0x30/0x50 [   19.464788]  kasan_save_track+0x14/0x30 [   19.466139]  __kasan_kmalloc+0xaa/0xb0 [   19.467465]  __kmalloc+0x1cd/0x470 [   19.468748]  isst_if_cdev_register+0x1da/0x350 [isst_if_common] [   19.470233]  isst_if_mbox_init+0x108/0xff0 [isst_if_mbox_msr] [   19.471670]  do_one_initcall+0xa4/0x380 [   19.472903]  do_init_module+0x238/0x760 [   19.474105]  load_module+0x5239/0x6f00 [   19.475285]  init_module_from_file+0xd1/0x130 [   19.476506]  idempotent_init_module+0x23b/0x650 [   19.477725]  __x64_sys_finit_module+0xbe/0x130 [   19.476506]  idempotent_init_module+0x23b/0x650 [   19.477725]  __x64_sys_finit_module+0xbe/0x130 [   19.478920]  do_syscall_64+0x82/0x160 [   19.480036]  entry_SYSCALL_64_after_hwframe+0x76/0x7e [   19.481292] [   19.482205] The buggy address belongs to the object at ffff888829e65000  which belongs to the cache kmalloc-512 of size 512 [   19.484818] The buggy address is located 0 bytes to the right of  allocated 512-byte region [ffff888829e65000, ffff888829e65200) [   19.487447] [   19.488328] The buggy address belongs to the physical page: [   19.489569] page: refcount:1 mapcount:0 mapping:0000000000000000 index:0xffff888829e60c00 pfn:0x829e60 [   19.491140] head: order:3 entire_mapcount:0 nr_pages_mapped:0 pincount:0 [   19.492466] anon flags: 0x57ffffc0000840(slab|head|node=1|zone=2|lastcpupid=0x1fffff) [   19.493914] page_type: 0xffffffff() [   19.494988] raw: 0057ffffc0000840 ffff88810004cc80 0000000000000000 0000000000000001 [   19.496451] raw: ffff888829e60c00 0000000080200018 00000001ffffffff 0000000000000000 [   19.497906] head: 0057ffffc0000840 ffff88810004cc80 0000000000000000 0000000000000001 [   19.499379] head: ffff888829e60c00 0000000080200018 00000001ffffffff 0000000000000000 [   19.500844] head: 0057ffffc0000003 ffffea0020a79801 ffffea0020a79848 00000000ffffffff [   19.502316] head: 0000000800000000 0000000000000000 00000000ffffffff 0000000000000000 [   19.503784] page dumped because: k ---truncated---(CVE-2024-49886)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  ext4: avoid use-after-free in ext4_ext_show_leaf()  In ext4_find_extent(), path may be freed by error or be reallocated, so using a previously saved *ppath may have been freed and thus may trigger use-after-free, as follows:  ext4_split_extent   path = *ppath;   ext4_split_extent_at(ppath)   path = ext4_find_extent(ppath)   ext4_split_extent_at(ppath)     // ext4_find_extent fails to free path     // but zeroout succeeds   ext4_ext_show_leaf(inode, path)     eh = path[depth].p_hdr     // path use-after-free !!!  Similar to ext4_split_extent_at(), we use *ppath directly as an input to ext4_ext_show_leaf(). Fix a spelling error by the way.  Same problem in ext4_ext_handle_unwritten_extents(). Since \u0026apos;path\u0026apos; is only used in ext4_ext_show_leaf(), remove \u0026apos;path\u0026apos; and use *ppath directly.  This issue is triggered only when EXT_DEBUG is defined and therefore does not affect functionality.(CVE-2024-49889)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  drm/amd/display: Initialize get_bytes_per_element\u0026apos;s default to 1  Variables, used as denominators and maybe not assigned to other values, should not be 0. bytes_per_element_y \u0026amp; bytes_per_element_c are initialized by get_bytes_per_element() which should never return 0.  This fixes 10 DIVIDE_BY_ZERO issues reported by Coverity.(CVE-2024-49892)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  drm/amd/display: Check stream before comparing them  [WHAT \u0026amp; HOW] amdgpu_dm can pass a null stream to dc_is_stream_unchanged. It is necessary to check for null before dereferencing them.  This fixes 1 FORWARD_NULL issue reported by Coverity.(CVE-2024-49896)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  drm/amd/display: Check null-initialized variables  [WHAT \u0026amp; HOW] drr_timing and subvp_pipe are initialized to null and they are not always assigned new values. It is necessary to check for null before dereferencing.  This fixes 2 FORWARD_NULL issues reported by Coverity.(CVE-2024-49898)\r\n\r\n(CVE-2024-49901)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  drm/amd/display: Add NULL check for function pointer in dcn32_set_output_transfer_func  This commit adds a null check for the set_output_gamma function pointer in the dcn32_set_output_transfer_func function. Previously, set_output_gamma was being checked for null, but then it was being dereferenced without any null check. This could lead to a null pointer dereference if set_output_gamma is null.  To fix this, we now ensure that set_output_gamma is not null before dereferencing it. We do this by adding a null check for set_output_gamma before the call to set_output_gamma.(CVE-2024-49909)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  drm/amd/display: Handle null \u0026apos;stream_status\u0026apos; in \u0026apos;planes_changed_for_existing_stream\u0026apos;  This commit adds a null check for \u0026apos;stream_status\u0026apos; in the function \u0026apos;planes_changed_for_existing_stream\u0026apos;. Previously, the code assumed \u0026apos;stream_status\u0026apos; could be null, but did not handle the case where it was actually null. This could lead to a null pointer dereference.  Reported by smatch: drivers/gpu/drm/amd/amdgpu/../display/dc/core/dc_resource.c:3784 planes_changed_for_existing_stream() error: we previously assumed \u0026apos;stream_status\u0026apos; could be null (see line 3774)(CVE-2024-49912)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  drm/amd/display: Add null check for top_pipe_to_program in commit_planes_for_stream  This commit addresses a null pointer dereference issue in the `commit_planes_for_stream` function at line 4140. The issue could occur when `top_pipe_to_program` is null.  The fix adds a check to ensure `top_pipe_to_program` is not null before accessing its stream_res. This prevents a null pointer dereference.  Reported by smatch: drivers/gpu/drm/amd/amdgpu/../display/dc/core/dc.c:4140 commit_planes_for_stream() error: we previously assumed \u0026apos;top_pipe_to_program\u0026apos; could be null (see line 3906)(CVE-2024-49913)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  drm/amd/display: Add NULL check for clk_mgr and clk_mgr-\u0026gt;funcs in dcn30_init_hw  This commit addresses a potential null pointer dereference issue in the `dcn30_init_hw` function. The issue could occur when `dc-\u0026gt;clk_mgr` or `dc-\u0026gt;clk_mgr-\u0026gt;funcs` is null.  The fix adds a check to ensure `dc-\u0026gt;clk_mgr` and `dc-\u0026gt;clk_mgr-\u0026gt;funcs` is not null before accessing its functions. This prevents a potential null pointer dereference.  Reported by smatch: drivers/gpu/drm/amd/amdgpu/../display/dc/hwss/dcn30/dcn30_hwseq.c:789 dcn30_init_hw() error: we previously assumed \u0026apos;dc-\u0026gt;clk_mgr\u0026apos; could be null (see line 628)(CVE-2024-49917)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  drm/amd/display: Check null pointers before using them  [WHAT \u0026amp; HOW] These pointers are null checked previously in the same function, indicating they might be null as reported by Coverity. As a result, they need to be checked when used again.  This fixes 3 FORWARD_NULL issue reported by Coverity.(CVE-2024-49922)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  fbdev: pxafb: Fix possible use after free in pxafb_task()  In the pxafb_probe function, it calls the pxafb_init_fbinfo function, after which \u0026amp;fbi-\u0026gt;task is associated with pxafb_task. Moreover, within this pxafb_init_fbinfo function, the pxafb_blank function within the \u0026amp;pxafb_ops struct is capable of scheduling work.  If we remove the module which will call pxafb_remove to make cleanup, it will call unregister_framebuffer function which can call do_unregister_framebuffer to free fbi-\u0026gt;fb through put_fb_info(fb_info), while the work mentioned above will be used. The sequence of operations that may lead to a UAF bug is as follows:  CPU0                                                CPU1                                     | pxafb_task pxafb_remove                       | unregister_framebuffer(info)       | do_unregister_framebuffer(fb_info) | put_fb_info(fb_info)               | // free fbi-\u0026gt;fb                    | set_ctrlr_state(fbi, state)                                    | __pxafb_lcd_power(fbi, 0)                                    | fbi-\u0026gt;lcd_power(on, \u0026amp;fbi-\u0026gt;fb.var)                                    | //use fbi-\u0026gt;fb  Fix it by ensuring that the work is canceled before proceeding with the cleanup in pxafb_remove.  Note that only root user can remove the driver at runtime.(CVE-2024-49924)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  wifi: ath12k: fix array out-of-bound access in SoC stats  Currently, the ath12k_soc_dp_stats::hal_reo_error array is defined with a maximum size of DP_REO_DST_RING_MAX. However, the ath12k_dp_rx_process() function access ath12k_soc_dp_stats::hal_reo_error using the REO destination SRNG ring ID, which is incorrect. SRNG ring ID differ from normal ring ID, and this usage leads to out-of-bounds array access. To fix this issue, modify ath12k_dp_rx_process() to use the normal ring ID directly instead of the SRNG ring ID to avoid out-of-bounds array access.  Tested-on: QCN9274 hw2.0 PCI WLAN.WBE.1.0.1-00029-QCAHKSWPL_SILICONZ-1(CVE-2024-49931)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  blk_iocost: fix more out of bound shifts  Recently running UBSAN caught few out of bound shifts in the ioc_forgive_debts() function:  UBSAN: shift-out-of-bounds in block/blk-iocost.c:2142:38 shift exponent 80 is too large for 64-bit type \u0026apos;u64\u0026apos; (aka \u0026apos;unsigned long long\u0026apos;) ... UBSAN: shift-out-of-bounds in block/blk-iocost.c:2144:30 shift exponent 80 is too large for 64-bit type \u0026apos;u64\u0026apos; (aka \u0026apos;unsigned long long\u0026apos;) ... Call Trace: \u0026lt;IRQ\u0026gt; dump_stack_lvl+0xca/0x130 __ubsan_handle_shift_out_of_bounds+0x22c/0x280 ? __lock_acquire+0x6441/0x7c10 ioc_timer_fn+0x6cec/0x7750 ? blk_iocost_init+0x720/0x720 ? call_timer_fn+0x5d/0x470 call_timer_fn+0xfa/0x470 ? blk_iocost_init+0x720/0x720 __run_timer_base+0x519/0x700 ...  Actual impact of this issue was not identified but I propose to fix the undefined behaviour. The proposed fix to prevent those out of bound shifts consist of precalculating exponent before using it the shift operations by taking min value from the actual exponent and maximum possible number of bits.(CVE-2024-49933)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  fs/inode: Prevent dump_mapping() accessing invalid dentry.d_name.name  It\u0026apos;s observed that a crash occurs during hot-remove a memory device, in which user is accessing the hugetlb. See calltrace as following:  ------------[ cut here ]------------ WARNING: CPU: 1 PID: 14045 at arch/x86/mm/fault.c:1278 do_user_addr_fault+0x2a0/0x790 Modules linked in: kmem device_dax cxl_mem cxl_pmem cxl_port cxl_pci dax_hmem dax_pmem nd_pmem cxl_acpi nd_btt cxl_core crc32c_intel nvme virtiofs fuse nvme_core nfit libnvdimm dm_multipath scsi_dh_rdac scsi_dh_emc s mirror dm_region_hash dm_log dm_mod CPU: 1 PID: 14045 Comm: daxctl Not tainted 6.10.0-rc2-lizhijian+ #492 Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS rel-1.16.3-0-ga6ed6b701f0a-prebuilt.qemu.org 04/01/2014 RIP: 0010:do_user_addr_fault+0x2a0/0x790 Code: 48 8b 00 a8 04 0f 84 b5 fe ff ff e9 1c ff ff ff 4c 89 e9 4c 89 e2 be 01 00 00 00 bf 02 00 00 00 e8 b5 ef 24 00 e9 42 fe ff ff \u0026lt;0f\u0026gt; 0b 48 83 c4 08 4c 89 ea 48 89 ee 4c 89 e7 5b 5d 41 5c 41 5d 41 RSP: 0000:ffffc90000a575f0 EFLAGS: 00010046 RAX: ffff88800c303600 RBX: 0000000000000000 RCX: 0000000000000000 RDX: 0000000000001000 RSI: ffffffff82504162 RDI: ffffffff824b2c36 RBP: 0000000000000000 R08: 0000000000000000 R09: 0000000000000000 R10: 0000000000000000 R11: 0000000000000000 R12: ffffc90000a57658 R13: 0000000000001000 R14: ffff88800bc2e040 R15: 0000000000000000 FS:  00007f51cb57d880(0000) GS:ffff88807fd00000(0000) knlGS:0000000000000000 CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 0000000000001000 CR3: 00000000072e2004 CR4: 00000000001706f0 DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400 Call Trace:  \u0026lt;TASK\u0026gt;  ? __warn+0x8d/0x190  ? do_user_addr_fault+0x2a0/0x790  ? report_bug+0x1c3/0x1d0  ? handle_bug+0x3c/0x70  ? exc_invalid_op+0x14/0x70  ? asm_exc_invalid_op+0x16/0x20  ? do_user_addr_fault+0x2a0/0x790  ? exc_page_fault+0x31/0x200  exc_page_fault+0x68/0x200 \u0026lt;...snip...\u0026gt; BUG: unable to handle page fault for address: 0000000000001000  #PF: supervisor read access in kernel mode  #PF: error_code(0x0000) - not-present page  PGD 800000000ad92067 P4D 800000000ad92067 PUD 7677067 PMD 0  Oops: Oops: 0000 [#1] PREEMPT SMP PTI  ---[ end trace 0000000000000000 ]---  BUG: unable to handle page fault for address: 0000000000001000  #PF: supervisor read access in kernel mode  #PF: error_code(0x0000) - not-present page  PGD 800000000ad92067 P4D 800000000ad92067 PUD 7677067 PMD 0  Oops: Oops: 0000 [#1] PREEMPT SMP PTI  CPU: 1 PID: 14045 Comm: daxctl Kdump: loaded Tainted: G        W          6.10.0-rc2-lizhijian+ #492  Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS rel-1.16.3-0-ga6ed6b701f0a-prebuilt.qemu.org 04/01/2014  RIP: 0010:dentry_name+0x1f4/0x440 \u0026lt;...snip...\u0026gt; ? dentry_name+0x2fa/0x440 vsnprintf+0x1f3/0x4f0 vprintk_store+0x23a/0x540 vprintk_emit+0x6d/0x330 _printk+0x58/0x80 dump_mapping+0x10b/0x1a0 ? __pfx_free_object_rcu+0x10/0x10 __dump_page+0x26b/0x3e0 ? vprintk_emit+0xe0/0x330 ? _printk+0x58/0x80 ? dump_page+0x17/0x50 dump_page+0x17/0x50 do_migrate_range+0x2f7/0x7f0 ? do_migrate_range+0x42/0x7f0 ? offline_pages+0x2f4/0x8c0 offline_pages+0x60a/0x8c0 memory_subsys_offline+0x9f/0x1c0 ? lockdep_hardirqs_on+0x77/0x100 ? _raw_spin_unlock_irqrestore+0x38/0x60 device_offline+0xe3/0x110 state_store+0x6e/0xc0 kernfs_fop_write_iter+0x143/0x200 vfs_write+0x39f/0x560 ksys_write+0x65/0xf0 do_syscall_64+0x62/0x130  Previously, some sanity check have been done in dump_mapping() before the print facility parsing \u0026apos;%pd\u0026apos; though, it\u0026apos;s still possible to run into an invalid dentry.d_name.name.  Since dump_mapping() only needs to dump the filename only, retrieve it by itself in a safer way to prevent an unnecessary crash.  Note that either retrieving the filename with \u0026apos;%pd\u0026apos; or strncpy_from_kernel_nofault(), the filename could be unreliable.(CVE-2024-49934)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  net/xen-netback: prevent UAF in xenvif_flush_hash()  During the list_for_each_entry_rcu iteration call of xenvif_flush_hash, kfree_rcu does not exist inside the rcu read critical section, so if kfree_rcu is called when the rcu grace period ends during the iteration, UAF occurs when accessing head-\u0026gt;next after the entry becomes free.  Therefore, to solve this, you need to change it to list_for_each_entry_safe.(CVE-2024-49936)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  wifi: cfg80211: Set correct chandef when starting CAC  When starting CAC in a mode other than AP mode, it return a \u0026quot;WARNING: CPU: 0 PID: 63 at cfg80211_chandef_dfs_usable+0x20/0xaf [cfg80211]\u0026quot; caused by the chandef.chan being null at the end of CAC.  Solution: Ensure the channel definition is set for the different modes when starting CAC to avoid getting a NULL \u0026apos;chan\u0026apos; at the end of CAC.   Call Trace:   ? show_regs.part.0+0x14/0x16   ? __warn+0x67/0xc0   ? cfg80211_chandef_dfs_usable+0x20/0xaf [cfg80211]   ? report_bug+0xa7/0x130   ? exc_overflow+0x30/0x30   ? handle_bug+0x27/0x50   ? exc_invalid_op+0x18/0x60   ? handle_exception+0xf6/0xf6   ? exc_overflow+0x30/0x30   ? cfg80211_chandef_dfs_usable+0x20/0xaf [cfg80211]   ? exc_overflow+0x30/0x30   ? cfg80211_chandef_dfs_usable+0x20/0xaf [cfg80211]   ? regulatory_propagate_dfs_state.cold+0x1b/0x4c [cfg80211]   ? cfg80211_propagate_cac_done_wk+0x1a/0x30 [cfg80211]   ? process_one_work+0x165/0x280   ? worker_thread+0x120/0x3f0   ? kthread+0xc2/0xf0   ? process_one_work+0x280/0x280   ? kthread_complete_and_exit+0x20/0x20   ? ret_from_fork+0x19/0x24  [shorten subject, remove OCB, reorder cases to match previous list](CVE-2024-49937)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  l2tp: prevent possible tunnel refcount underflow  When a session is created, it sets a backpointer to its tunnel. When the session refcount drops to 0, l2tp_session_free drops the tunnel refcount if session-\u0026gt;tunnel is non-NULL. However, session-\u0026gt;tunnel is set in l2tp_session_create, before the tunnel refcount is incremented by l2tp_session_register, which leaves a small window where session-\u0026gt;tunnel is non-NULL when the tunnel refcount hasn\u0026apos;t been bumped.  Moving the assignment to l2tp_session_register is trivial but l2tp_session_create calls l2tp_session_set_header_len which uses session-\u0026gt;tunnel to get the tunnel\u0026apos;s encap. Add an encap arg to l2tp_session_set_header_len to avoid using session-\u0026gt;tunnel.  If l2tpv3 sessions have colliding IDs, it is possible for l2tp_v3_session_get to race with l2tp_session_register and fetch a session which doesn\u0026apos;t yet have session-\u0026gt;tunnel set. Add a check for this case.(CVE-2024-49940)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  static_call: Replace pointless WARN_ON() in static_call_module_notify()  static_call_module_notify() triggers a WARN_ON(), when memory allocation fails in __static_call_add_module().  That\u0026apos;s not really justified, because the failure case must be correctly handled by the well known call chain and the error code is passed through to the initiating userspace application.  A memory allocation fail is not a fatal problem, but the WARN_ON() takes the machine out when panic_on_warn is set.  Replace it with a pr_warn().(CVE-2024-49954)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  ACPI: battery: Fix possible crash when unregistering a battery hook  When a battery hook returns an error when adding a new battery, then the battery hook is automatically unregistered. However the battery hook provider cannot know that, so it will later call battery_hook_unregister() on the already unregistered battery hook, resulting in a crash.  Fix this by using the list head to mark already unregistered battery hooks as already being unregistered so that they can be ignored by battery_hook_unregister().(CVE-2024-49955)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  ocfs2: reserve space for inline xattr before attaching reflink tree  One of our customers reported a crash and a corrupted ocfs2 filesystem.  The crash was due to the detection of corruption.  Upon troubleshooting, the fsck -fn output showed the below corruption  [EXTENT_LIST_FREE] Extent list in owner 33080590 claims 230 as the next free chain record, but fsck believes the largest valid value is 227.  Clamp the next record value? n  The stat output from the debugfs.ocfs2 showed the following corruption where the \u0026quot;Next Free Rec:\u0026quot; had overshot the \u0026quot;Count:\u0026quot; in the root metadata block.          Inode: 33080590   Mode: 0640   Generation: 2619713622 (0x9c25a856)         FS Generation: 904309833 (0x35e6ac49)         CRC32: 00000000   ECC: 0000         Type: Regular   Attr: 0x0   Flags: Valid         Dynamic Features: (0x16) HasXattr InlineXattr Refcounted         Extended Attributes Block: 0  Extended Attributes Inline Size: 256         User: 0 (root)   Group: 0 (root)   Size: 281320357888         Links: 1   Clusters: 141738         ctime: 0x66911b56 0x316edcb8 -- Fri Jul 12 06:02:30.829349048 2024         atime: 0x66911d6b 0x7f7a28d -- Fri Jul 12 06:11:23.133669517 2024         mtime: 0x66911b56 0x12ed75d7 -- Fri Jul 12 06:02:30.317552087 2024         dtime: 0x0 -- Wed Dec 31 17:00:00 1969         Refcount Block: 2777346         Last Extblk: 2886943   Orphan Slot: 0         Sub Alloc Slot: 0   Sub Alloc Bit: 14         Tree Depth: 1   Count: 227   Next Free Rec: 230         ## Offset        Clusters       Block#         0  0             2310           2776351         1  2310          2139           2777375         2  4449          1221           2778399         3  5670          731            2779423         4  6401          566            2780447         .......          ....           .......         .......          ....           .......  The issue was in the reflink workfow while reserving space for inline xattr.  The problematic function is ocfs2_reflink_xattr_inline().  By the time this function is called the reflink tree is already recreated at the destination inode from the source inode.  At this point, this function reserves space for inline xattrs at the destination inode without even checking if there is space at the root metadata block.  It simply reduces the l_count from 243 to 227 thereby making space of 256 bytes for inline xattr whereas the inode already has extents beyond this index (in this case up to 230), thereby causing corruption.  The fix for this is to reserve space for inline metadata at the destination inode before the reflink tree gets recreated. The customer has verified the fix.(CVE-2024-49958)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  ext4: fix timer use-after-free on failed mount  Syzbot has found an ODEBUG bug in ext4_fill_super  The del_timer_sync function cancels the s_err_report timer, which reminds about filesystem errors daily. We should guarantee the timer is no longer active before kfree(sbi).  When filesystem mounting fails, the flow goes to failed_mount3, where an error occurs when ext4_stop_mmpd is called, causing a read I/O failure. This triggers the ext4_handle_error function that ultimately re-arms the timer, leaving the s_err_report timer active before kfree(sbi) is called.  Fix the issue by canceling the s_err_report timer after calling ext4_stop_mmpd.(CVE-2024-49960)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  media: i2c: ar0521: Use cansleep version of gpiod_set_value()  If we use GPIO reset from I2C port expander, we must use *_cansleep() variant of GPIO functions. This was not done in ar0521_power_on()/ar0521_power_off() functions. Let\u0026apos;s fix that.  ------------[ cut here ]------------ WARNING: CPU: 0 PID: 11 at drivers/gpio/gpiolib.c:3496 gpiod_set_value+0x74/0x7c Modules linked in: CPU: 0 PID: 11 Comm: kworker/u16:0 Not tainted 6.10.0 #53 Hardware name: Diasom DS-RK3568-SOM-EVB (DT) Workqueue: events_unbound deferred_probe_work_func pstate: 80400009 (Nzcv daif +PAN -UAO -TCO -DIT -SSBS BTYPE=--) pc : gpiod_set_value+0x74/0x7c lr : ar0521_power_on+0xcc/0x290 sp : ffffff8001d7ab70 x29: ffffff8001d7ab70 x28: ffffff80027dcc90 x27: ffffff8003c82000 x26: ffffff8003ca9250 x25: ffffffc080a39c60 x24: ffffff8003ca9088 x23: ffffff8002402720 x22: ffffff8003ca9080 x21: ffffff8003ca9088 x20: 0000000000000000 x19: ffffff8001eb2a00 x18: ffffff80efeeac80 x17: 756d2d6332692f30 x16: 0000000000000000 x15: 0000000000000000 x14: ffffff8001d91d40 x13: 0000000000000016 x12: ffffffc080e98930 x11: ffffff8001eb2880 x10: 0000000000000890 x9 : ffffff8001d7a9f0 x8 : ffffff8001d92570 x7 : ffffff80efeeac80 x6 : 000000003fc6e780 x5 : ffffff8001d91c80 x4 : 0000000000000002 x3 : 0000000000000000 x2 : 0000000000000000 x1 : 0000000000000000 x0 : 0000000000000001 Call trace:  gpiod_set_value+0x74/0x7c  ar0521_power_on+0xcc/0x290 ...(CVE-2024-49961)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  ocfs2: cancel dqi_sync_work before freeing oinfo  ocfs2_global_read_info() will initialize and schedule dqi_sync_work at the end, if error occurs after successfully reading global quota, it will trigger the following warning with CONFIG_DEBUG_OBJECTS_* enabled:  ODEBUG: free active (active state 0) object: 00000000d8b0ce28 object type: timer_list hint: qsync_work_fn+0x0/0x16c  This reports that there is an active delayed work when freeing oinfo in error handling, so cancel dqi_sync_work first.  BTW, return status instead of -1 when .read_file_info fails.(CVE-2024-49966)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  ext4: no need to continue when the number of entries is 1(CVE-2024-49967)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  ext4: filesystems without casefold feature cannot be mounted with siphash  When mounting the ext4 filesystem, if the default hash version is set to DX_HASH_SIPHASH but the casefold feature is not set, exit the mounting.(CVE-2024-49968)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  r8169: add tally counter fields added with RTL8125  RTL8125 added fields to the tally counter, what may result in the chip dma\u0026apos;ing these new fields to unallocated memory. Therefore make sure that the allocated memory area is big enough to hold all of the tally counter values, even if we use only parts of it.(CVE-2024-49973)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  uprobes: fix kernel info leak via \u0026quot;[uprobes]\u0026quot; vma  xol_add_vma() maps the uninitialized page allocated by __create_xol_area() into userspace. On some architectures (x86) this memory is readable even without VM_READ, VM_EXEC results in the same pgprot_t as VM_EXEC|VM_READ, although this doesn\u0026apos;t really matter, debugger can read this memory anyway.(CVE-2024-49975)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  gso: fix udp gso fraglist segmentation after pull from frag_list  Detect gso fraglist skbs with corrupted geometry (see below) and pass these to skb_segment instead of skb_segment_list, as the first can segment them correctly.  Valid SKB_GSO_FRAGLIST skbs - consist of two or more segments - the head_skb holds the protocol headers plus first gso_size - one or more frag_list skbs hold exactly one segment - all but the last must be gso_size  Optional datapath hooks such as NAT and BPF (bpf_skb_pull_data) can modify these skbs, breaking these invariants.  In extreme cases they pull all data into skb linear. For UDP, this causes a NULL ptr deref in __udpv4_gso_segment_list_csum at udp_hdr(seg-\u0026gt;next)-\u0026gt;dest.  Detect invalid geometry due to pull, by checking head_skb size. Don\u0026apos;t just drop, as this may blackhole a destination. Convert to be able to pass to regular skb_segment.(CVE-2024-49978)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  media: venus: fix use after free bug in venus_remove due to race condition  in venus_probe, core-\u0026gt;work is bound with venus_sys_error_handler, which is used to handle error. The code use core-\u0026gt;sys_err_done to make sync work. The core-\u0026gt;work is started in venus_event_notify.  If we call venus_remove, there might be an unfished work. The possible sequence is as follows:  CPU0                  CPU1                       |venus_sys_error_handler venus_remove         | hfi_destroy     | venus_hfi_destroy  | kfree(hdev);      |                      |hfi_reinit       |venus_hfi_queues_reinit                      |//use hdev  Fix it by canceling the work in venus_remove.(CVE-2024-49981)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  ext4: drop ppath from ext4_ext_replay_update_ex() to avoid double-free  When calling ext4_force_split_extent_at() in ext4_ext_replay_update_ex(), the \u0026apos;ppath\u0026apos; is updated but it is the \u0026apos;path\u0026apos; that is freed, thus potentially triggering a double-free in the following process:  ext4_ext_replay_update_ex   ppath = path   ext4_force_split_extent_at(\u0026amp;ppath)     ext4_split_extent_at       ext4_ext_insert_extent         ext4_ext_create_new_leaf           ext4_ext_grow_indepth             ext4_find_extent               if (depth \u0026gt; path[0].p_maxdepth)                 kfree(path)                 ---\u0026gt; path First freed                 *orig_path = path = NULL    ---\u0026gt; null ppath   kfree(path)                               ---\u0026gt; path double-free !!!  So drop the unnecessary ppath and use path directly to avoid this problem. And use ext4_find_extent() directly to update path, avoiding unnecessary memory allocation and freeing. Also, propagate the error returned by ext4_find_extent() instead of using strange error codes.(CVE-2024-49983)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  drm/amd/display: fix double free issue during amdgpu module unload  Flexible endpoints use DIGs from available inflexible endpoints, so only the encoders of inflexible links need to be freed. Otherwise, a double free issue may occur when unloading the amdgpu module.  [  279.190523] RIP: 0010:__slab_free+0x152/0x2f0 [  279.190577] Call Trace: [  279.190580]  \u0026lt;TASK\u0026gt; [  279.190582]  ? show_regs+0x69/0x80 [  279.190590]  ? die+0x3b/0x90 [  279.190595]  ? do_trap+0xc8/0xe0 [  279.190601]  ? do_error_trap+0x73/0xa0 [  279.190605]  ? __slab_free+0x152/0x2f0 [  279.190609]  ? exc_invalid_op+0x56/0x70 [  279.190616]  ? __slab_free+0x152/0x2f0 [  279.190642]  ? asm_exc_invalid_op+0x1f/0x30 [  279.190648]  ? dcn10_link_encoder_destroy+0x19/0x30 [amdgpu] [  279.191096]  ? __slab_free+0x152/0x2f0 [  279.191102]  ? dcn10_link_encoder_destroy+0x19/0x30 [amdgpu] [  279.191469]  kfree+0x260/0x2b0 [  279.191474]  dcn10_link_encoder_destroy+0x19/0x30 [amdgpu] [  279.191821]  link_destroy+0xd7/0x130 [amdgpu] [  279.192248]  dc_destruct+0x90/0x270 [amdgpu] [  279.192666]  dc_destroy+0x19/0x40 [amdgpu] [  279.193020]  amdgpu_dm_fini+0x16e/0x200 [amdgpu] [  279.193432]  dm_hw_fini+0x26/0x40 [amdgpu] [  279.193795]  amdgpu_device_fini_hw+0x24c/0x400 [amdgpu] [  279.194108]  amdgpu_driver_unload_kms+0x4f/0x70 [amdgpu] [  279.194436]  amdgpu_pci_remove+0x40/0x80 [amdgpu] [  279.194632]  pci_device_remove+0x3a/0xa0 [  279.194638]  device_remove+0x40/0x70 [  279.194642]  device_release_driver_internal+0x1ad/0x210 [  279.194647]  driver_detach+0x4e/0xa0 [  279.194650]  bus_remove_driver+0x6f/0xf0 [  279.194653]  driver_unregister+0x33/0x60 [  279.194657]  pci_unregister_driver+0x44/0x90 [  279.194662]  amdgpu_exit+0x19/0x1f0 [amdgpu] [  279.194939]  __do_sys_delete_module.isra.0+0x198/0x2f0 [  279.194946]  __x64_sys_delete_module+0x16/0x20 [  279.194950]  do_syscall_64+0x58/0x120 [  279.194954]  entry_SYSCALL_64_after_hwframe+0x6e/0x76 [  279.194980]  \u0026lt;/TASK\u0026gt;(CVE-2024-49989)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  drm/stm: Avoid use-after-free issues with crtc and plane  ltdc_load() calls functions drm_crtc_init_with_planes(), drm_universal_plane_init() and drm_encoder_init(). These functions should not be called with parameters allocated with devm_kzalloc() to avoid use-after-free issues [1].  Use allocations managed by the DRM framework.  Found by Linux Verification Center (linuxtesting.org).  [1] https://lore.kernel.org/lkml/u366i76e3qhh3ra5oxrtngjtm2u5lterkekcz6y2jkndhuxzli@diujon4h7qwb/(CVE-2024-49992)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  block: fix integer overflow in BLKSECDISCARD  I independently rediscovered   commit 22d24a544b0d49bbcbd61c8c0eaf77d3c9297155  block: fix overflow in blk_ioctl_discard()  but for secure erase.  Same problem:   uint64_t r[2] = {512, 18446744073709551104ULL};  ioctl(fd, BLKSECDISCARD, r);  will enter near infinite loop inside blkdev_issue_secure_erase():   a.out: attempt to access beyond end of device  loop0: rw=5, sector=3399043073, nr_sectors = 1024 limit=2048  bio_check_eod: 3286214 callbacks suppressed(CVE-2024-49994)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  tipc: guard against string buffer overrun  Smatch reports that copying media_name and if_name to name_parts may overwrite the destination.   .../bearer.c:166 bearer_name_validate() error: strcpy() \u0026apos;media_name\u0026apos; too large for \u0026apos;name_parts-\u0026gt;media_name\u0026apos; (32 vs 16)  .../bearer.c:167 bearer_name_validate() error: strcpy() \u0026apos;if_name\u0026apos; too large for \u0026apos;name_parts-\u0026gt;if_name\u0026apos; (1010102 vs 16)  This does seem to be the case so guard against this possibility by using strscpy() and failing if truncation occurs.  Introduced by commit b97bf3fd8f6a (\u0026quot;[TIPC] Initial merge\u0026quot;)  Compile tested only.(CVE-2024-49995)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  cifs: Fix buffer overflow when parsing NFS reparse points  ReparseDataLength is sum of the InodeType size and DataBuffer size. So to get DataBuffer size it is needed to subtract InodeType\u0026apos;s size from ReparseDataLength.  Function cifs_strndup_from_utf16() is currentlly accessing buf-\u0026gt;DataBuffer at position after the end of the buffer because it does not subtract InodeType size from the length. Fix this problem and correctly subtract variable len.  Member InodeType is present only when reparse buffer is large enough. Check for ReparseDataLength before accessing InodeType to prevent another invalid memory access.  Major and minor rdev values are present also only when reparse buffer is large enough. Check for reparse buffer size before calling reparse_mkdev().(CVE-2024-49996)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  net/mlx5e: Fix NULL deref in mlx5e_tir_builder_alloc()  In mlx5e_tir_builder_alloc() kvzalloc() may return NULL which is dereferenced on the next line in a reference to the modify field.  Found by Linux Verification Center (linuxtesting.org) with SVACE.(CVE-2024-50000)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  drm/amd/display: Fix system hang while resume with TBT monitor  [Why] Connected with a Thunderbolt monitor and do the suspend and the system may hang while resume.  The TBT monitor HPD will be triggered during the resume procedure and call the drm_client_modeset_probe() while struct drm_connector connector-\u0026gt;dev-\u0026gt;master is NULL.  It will mess up the pipe topology after resume.  [How] Skip the TBT monitor HPD during the resume procedure because we currently will probe the connectors after resume by default.  (cherry picked from commit 453f86a26945207a16b8f66aaed5962dc2b95b85)(CVE-2024-50003)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  ext4: fix i_data_sem unlock order in ext4_ind_migrate()  Fuzzing reports a possible deadlock in jbd2_log_wait_commit.  This issue is triggered when an EXT4_IOC_MIGRATE ioctl is set to require synchronous updates because the file descriptor is opened with O_SYNC. This can lead to the jbd2_journal_stop() function calling jbd2_might_wait_for_commit(), potentially causing a deadlock if the EXT4_IOC_MIGRATE call races with a write(2) system call.  This problem only arises when CONFIG_PROVE_LOCKING is enabled. In this case, the jbd2_might_wait_for_commit macro locks jbd2_handle in the jbd2_journal_stop function while i_data_sem is locked. This triggers lockdep because the jbd2_journal_start function might also lock the same jbd2_handle simultaneously.  Found by Linux Verification Center (linuxtesting.org) with syzkaller.  Rule: add(CVE-2024-50006)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  wifi: mwifiex: Fix memcpy() field-spanning write warning in mwifiex_cmd_802_11_scan_ext()  Replace one-element array with a flexible-array member in `struct host_cmd_ds_802_11_scan_ext`.  With this, fix the following warning:  elo 16 17:51:58 surfacebook kernel: ------------[ cut here ]------------ elo 16 17:51:58 surfacebook kernel: memcpy: detected field-spanning write (size 243) of single field \u0026quot;ext_scan-\u0026gt;tlv_buffer\u0026quot; at drivers/net/wireless/marvell/mwifiex/scan.c:2239 (size 1) elo 16 17:51:58 surfacebook kernel: WARNING: CPU: 0 PID: 498 at drivers/net/wireless/marvell/mwifiex/scan.c:2239 mwifiex_cmd_802_11_scan_ext+0x83/0x90 [mwifiex](CVE-2024-50008)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  cpufreq: amd-pstate: add check for cpufreq_cpu_get\u0026apos;s return value  cpufreq_cpu_get may return NULL. To avoid NULL-dereference check it and return in case of error.  Found by Linux Verification Center (linuxtesting.org) with SVACE.(CVE-2024-50009)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  exfat: fix memory leak in exfat_load_bitmap()  If the first directory entry in the root directory is not a bitmap directory entry, \u0026apos;bh\u0026apos; will not be released and reassigned, which will cause a memory leak.(CVE-2024-50013)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  ext4: fix access to uninitialised lock in fc replay path  The following kernel trace can be triggered with fstest generic/629 when executed against a filesystem with fast-commit feature enabled:  INFO: trying to register non-static key. The code is fine but needs lockdep annotation, or maybe you didn\u0026apos;t initialize this object before use? turning off the locking correctness validator. CPU: 0 PID: 866 Comm: mount Not tainted 6.10.0+ #11 Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS rel-1.16.2-3-gd478f380-prebuilt.qemu.org 04/01/2014 Call Trace:  \u0026lt;TASK\u0026gt;  dump_stack_lvl+0x66/0x90  register_lock_class+0x759/0x7d0  __lock_acquire+0x85/0x2630  ? __find_get_block+0xb4/0x380  lock_acquire+0xd1/0x2d0  ? __ext4_journal_get_write_access+0xd5/0x160  _raw_spin_lock+0x33/0x40  ? __ext4_journal_get_write_access+0xd5/0x160  __ext4_journal_get_write_access+0xd5/0x160  ext4_reserve_inode_write+0x61/0xb0  __ext4_mark_inode_dirty+0x79/0x270  ? ext4_ext_replay_set_iblocks+0x2f8/0x450  ext4_ext_replay_set_iblocks+0x330/0x450  ext4_fc_replay+0x14c8/0x1540  ? jread+0x88/0x2e0  ? rcu_is_watching+0x11/0x40  do_one_pass+0x447/0xd00  jbd2_journal_recover+0x139/0x1b0  jbd2_journal_load+0x96/0x390  ext4_load_and_init_journal+0x253/0xd40  ext4_fill_super+0x2cc6/0x3180 ...  In the replay path there\u0026apos;s an attempt to lock sbi-\u0026gt;s_bdev_wb_lock in function ext4_check_bdev_write_error().  Unfortunately, at this point this spinlock has not been initialized yet.  Moving it\u0026apos;s initialization to an earlier point in __ext4_fill_super() fixes this splat.(CVE-2024-50014)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  ext4: dax: fix overflowing extents beyond inode size when partially writing  The dax_iomap_rw() does two things in each iteration: map written blocks and copy user data to blocks. If the process is killed by user(See signal handling in dax_iomap_iter()), the copied data will be returned and added on inode size, which means that the length of written extents may exceed the inode size, then fsck will fail. An example is given as:  dd if=/dev/urandom of=file bs=4M count=1  dax_iomap_rw   iomap_iter // round 1    ext4_iomap_begin     ext4_iomap_alloc // allocate 0~2M extents(written flag)   dax_iomap_iter // copy 2M data   iomap_iter // round 2    iomap_iter_advance     iter-\u0026gt;pos += iter-\u0026gt;processed // iter-\u0026gt;pos = 2M    ext4_iomap_begin     ext4_iomap_alloc // allocate 2~4M extents(written flag)   dax_iomap_iter    fatal_signal_pending   done = iter-\u0026gt;pos - iocb-\u0026gt;ki_pos // done = 2M  ext4_handle_inode_extension   ext4_update_inode_size // inode size = 2M  fsck reports: Inode 13, i_size is 2097152, should be 4194304.  Fix?  Fix the problem by truncating extents if the written length is smaller than expected.(CVE-2024-50015)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  drm/amd/display: Avoid overflow assignment in link_dp_cts  sampling_rate is an uint8_t but is assigned an unsigned int, and thus it can overflow. As a result, sampling_rate is changed to uint32_t.  Similarly, LINK_QUAL_PATTERN_SET has a size of 2 bits, and it should only be assigned to a value less or equal than 4.  This fixes 2 INTEGER_OVERFLOW issues reported by Coverity.(CVE-2024-50016)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  kthread: unpark only parked kthread  Calling into kthread unparking unconditionally is mostly harmless when the kthread is already unparked. The wake up is then simply ignored because the target is not in TASK_PARKED state.  However if the kthread is per CPU, the wake up is preceded by a call to kthread_bind() which expects the task to be inactive and in TASK_PARKED state, which obviously isn\u0026apos;t the case if it is unparked.  As a result, calling kthread_stop() on an unparked per-cpu kthread triggers such a warning:   WARNING: CPU: 0 PID: 11 at kernel/kthread.c:525 __kthread_bind_mask kernel/kthread.c:525   \u0026lt;TASK\u0026gt;   kthread_stop+0x17a/0x630 kernel/kthread.c:707   destroy_workqueue+0x136/0xc40 kernel/workqueue.c:5810   wg_destruct+0x1e2/0x2e0 drivers/net/wireguard/device.c:257   netdev_run_todo+0xe1a/0x1000 net/core/dev.c:10693   default_device_exit_batch+0xa14/0xa90 net/core/dev.c:11769   ops_exit_list net/core/net_namespace.c:178 [inline]   cleanup_net+0x89d/0xcc0 net/core/net_namespace.c:640   process_one_work kernel/workqueue.c:3231 [inline]   process_scheduled_works+0xa2c/0x1830 kernel/workqueue.c:3312   worker_thread+0x86d/0xd70 kernel/workqueue.c:3393   kthread+0x2f0/0x390 kernel/kthread.c:389   ret_from_fork+0x4b/0x80 arch/x86/kernel/process.c:147   ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:244   \u0026lt;/TASK\u0026gt;  Fix this with skipping unecessary unparking while stopping a kthread.(CVE-2024-50019)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  device-dax: correct pgoff align in dax_set_mapping()  pgoff should be aligned using ALIGN_DOWN() instead of ALIGN().  Otherwise, vmf-\u0026gt;address not aligned to fault_size will be aligned to the next alignment, that can result in memory failure getting the wrong address.  It\u0026apos;s a subtle situation that only can be observed in page_mapped_in_vma() after the page is page fault handled by dev_dax_huge_fault.  Generally, there is little chance to perform page_mapped_in_vma in dev-dax\u0026apos;s page unless in specific error injection to the dax device to trigger an MCE - memory-failure.  In that case, page_mapped_in_vma() will be triggered to determine which task is accessing the failure address and kill that task in the end.   We used self-developed dax device (which is 2M aligned mapping) , to perform error injection to random address.  It turned out that error injected to non-2M-aligned address was causing endless MCE until panic. Because page_mapped_in_vma() kept resulting wrong address and the task accessing the failure address was never killed properly:   [ 3783.719419] Memory failure: 0x200c9742: recovery action for dax page:  Recovered [ 3784.049006] mce: Uncorrected hardware memory error in user-access at  200c9742380 [ 3784.049190] Memory failure: 0x200c9742: recovery action for dax page:  Recovered [ 3784.448042] mce: Uncorrected hardware memory error in user-access at  200c9742380 [ 3784.448186] Memory failure: 0x200c9742: recovery action for dax page:  Recovered [ 3784.792026] mce: Uncorrected hardware memory error in user-access at  200c9742380 [ 3784.792179] Memory failure: 0x200c9742: recovery action for dax page:  Recovered [ 3785.162502] mce: Uncorrected hardware memory error in user-access at  200c9742380 [ 3785.162633] Memory failure: 0x200c9742: recovery action for dax page:  Recovered [ 3785.461116] mce: Uncorrected hardware memory error in user-access at  200c9742380 [ 3785.461247] Memory failure: 0x200c9742: recovery action for dax page:  Recovered [ 3785.764730] mce: Uncorrected hardware memory error in user-access at  200c9742380 [ 3785.764859] Memory failure: 0x200c9742: recovery action for dax page:  Recovered [ 3786.042128] mce: Uncorrected hardware memory error in user-access at  200c9742380 [ 3786.042259] Memory failure: 0x200c9742: recovery action for dax page:  Recovered [ 3786.464293] mce: Uncorrected hardware memory error in user-access at  200c9742380 [ 3786.464423] Memory failure: 0x200c9742: recovery action for dax page:  Recovered [ 3786.818090] mce: Uncorrected hardware memory error in user-access at  200c9742380 [ 3786.818217] Memory failure: 0x200c9742: recovery action for dax page:  Recovered [ 3787.085297] mce: Uncorrected hardware memory error in user-access at  200c9742380 [ 3787.085424] Memory failure: 0x200c9742: recovery action for dax page:  Recovered  It took us several weeks to pinpoint this problem,  but we eventually used bpftrace to trace the page fault and mce address and successfully identified the issue.   Joao added:  ; Likely we never reproduce in production because we always pin : device-dax regions in the region align they provide (Qemu does : similarly with prealloc in hugetlb/file backed memory).  I think this : bug requires that we touch *unpinned* device-dax regions unaligned to : the device-dax selected alignment (page size i.e.  4K/2M/1G)(CVE-2024-50022)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  scsi: fnic: Move flush_work initialization out of if block  After commit 379a58caa199 (\u0026quot;scsi: fnic: Move fnic_fnic_flush_tx() to a work queue\u0026quot;), it can happen that a work item is sent to an uninitialized work queue.  This may has the effect that the item being queued is never actually queued, and any further actions depending on it will not proceed.  The following warning is observed while the fnic driver is loaded:  kernel: WARNING: CPU: 11 PID: 0 at ../kernel/workqueue.c:1524 __queue_work+0x373/0x410 kernel:  \u0026lt;IRQ\u0026gt; kernel:  queue_work_on+0x3a/0x50 kernel:  fnic_wq_copy_cmpl_handler+0x54a/0x730 [fnic 62fbff0c42e7fb825c60a55cde2fb91facb2ed24] kernel:  fnic_isr_msix_wq_copy+0x2d/0x60 [fnic 62fbff0c42e7fb825c60a55cde2fb91facb2ed24] kernel:  __handle_irq_event_percpu+0x36/0x1a0 kernel:  handle_irq_event_percpu+0x30/0x70 kernel:  handle_irq_event+0x34/0x60 kernel:  handle_edge_irq+0x7e/0x1a0 kernel:  __common_interrupt+0x3b/0xb0 kernel:  common_interrupt+0x58/0xa0 kernel:  \u0026lt;/IRQ\u0026gt;  It has been observed that this may break the rediscovery of Fibre Channel devices after a temporary fabric failure.  This patch fixes it by moving the work queue initialization out of an if block in fnic_probe().(CVE-2024-50025)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  scsi: wd33c93: Don\u0026apos;t use stale scsi_pointer value  A regression was introduced with commit dbb2da557a6a (\u0026quot;scsi: wd33c93: Move the SCSI pointer to private command data\u0026quot;) which results in an oops in wd33c93_intr(). That commit added the scsi_pointer variable and initialized it from hostdata-\u0026gt;connected. However, during selection, hostdata-\u0026gt;connected is not yet valid. Fix this by getting the current scsi_pointer from hostdata-\u0026gt;selecting.(CVE-2024-50026)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  thermal: core: Reference count the zone in thermal_zone_get_by_id()  There are places in the thermal netlink code where nothing prevents the thermal zone object from going away while being accessed after it has been returned by thermal_zone_get_by_id().  To address this, make thermal_zone_get_by_id() get a reference on the thermal zone device object to be returned with the help of get_device(), under thermal_list_lock, and adjust all of its callers to this change with the help of the cleanup.h infrastructure.(CVE-2024-50028)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  Bluetooth: hci_conn: Fix UAF in hci_enhanced_setup_sync  This checks if the ACL connection remains valid as it could be destroyed while hci_enhanced_setup_sync is pending on cmd_sync leading to the following trace:  BUG: KASAN: slab-use-after-free in hci_enhanced_setup_sync+0x91b/0xa60 Read of size 1 at addr ffff888002328ffd by task kworker/u5:2/37  CPU: 0 UID: 0 PID: 37 Comm: kworker/u5:2 Not tainted 6.11.0-rc6-01300-g810be445d8d6 #7099 Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.16.3-2.fc40 04/01/2014 Workqueue: hci0 hci_cmd_sync_work Call Trace:  \u0026lt;TASK\u0026gt;  dump_stack_lvl+0x5d/0x80  ? hci_enhanced_setup_sync+0x91b/0xa60  print_report+0x152/0x4c0  ? hci_enhanced_setup_sync+0x91b/0xa60  ? __virt_addr_valid+0x1fa/0x420  ? hci_enhanced_setup_sync+0x91b/0xa60  kasan_report+0xda/0x1b0  ? hci_enhanced_setup_sync+0x91b/0xa60  hci_enhanced_setup_sync+0x91b/0xa60  ? __pfx_hci_enhanced_setup_sync+0x10/0x10  ? __pfx___mutex_lock+0x10/0x10  hci_cmd_sync_work+0x1c2/0x330  process_one_work+0x7d9/0x1360  ? __pfx_lock_acquire+0x10/0x10  ? __pfx_process_one_work+0x10/0x10  ? assign_work+0x167/0x240  worker_thread+0x5b7/0xf60  ? __kthread_parkme+0xac/0x1c0  ? __pfx_worker_thread+0x10/0x10  ? __pfx_worker_thread+0x10/0x10  kthread+0x293/0x360  ? __pfx_kthread+0x10/0x10  ret_from_fork+0x2f/0x70  ? __pfx_kthread+0x10/0x10  ret_from_fork_asm+0x1a/0x30  \u0026lt;/TASK\u0026gt;  Allocated by task 34:  kasan_save_stack+0x30/0x50  kasan_save_track+0x14/0x30  __kasan_kmalloc+0x8f/0xa0  __hci_conn_add+0x187/0x17d0  hci_connect_sco+0x2e1/0xb90  sco_sock_connect+0x2a2/0xb80  __sys_connect+0x227/0x2a0  __x64_sys_connect+0x6d/0xb0  do_syscall_64+0x71/0x140  entry_SYSCALL_64_after_hwframe+0x76/0x7e  Freed by task 37:  kasan_save_stack+0x30/0x50  kasan_save_track+0x14/0x30  kasan_save_free_info+0x3b/0x60  __kasan_slab_free+0x101/0x160  kfree+0xd0/0x250  device_release+0x9a/0x210  kobject_put+0x151/0x280  hci_conn_del+0x448/0xbf0  hci_abort_conn_sync+0x46f/0x980  hci_cmd_sync_work+0x1c2/0x330  process_one_work+0x7d9/0x1360  worker_thread+0x5b7/0xf60  kthread+0x293/0x360  ret_from_fork+0x2f/0x70  ret_from_fork_asm+0x1a/0x30(CVE-2024-50029)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  slip: make slhc_remember() more robust against malicious packets  syzbot found that slhc_remember() was missing checks against malicious packets [1].  slhc_remember() only checked the size of the packet was at least 20, which is not good enough.  We need to make sure the packet includes the IPv4 and TCP header that are supposed to be carried.  Add iph and th pointers to make the code more readable.  [1]  BUG: KMSAN: uninit-value in slhc_remember+0x2e8/0x7b0 drivers/net/slip/slhc.c:666   slhc_remember+0x2e8/0x7b0 drivers/net/slip/slhc.c:666   ppp_receive_nonmp_frame+0xe45/0x35e0 drivers/net/ppp/ppp_generic.c:2455   ppp_receive_frame drivers/net/ppp/ppp_generic.c:2372 [inline]   ppp_do_recv+0x65f/0x40d0 drivers/net/ppp/ppp_generic.c:2212   ppp_input+0x7dc/0xe60 drivers/net/ppp/ppp_generic.c:2327   pppoe_rcv_core+0x1d3/0x720 drivers/net/ppp/pppoe.c:379   sk_backlog_rcv+0x13b/0x420 include/net/sock.h:1113   __release_sock+0x1da/0x330 net/core/sock.c:3072   release_sock+0x6b/0x250 net/core/sock.c:3626   pppoe_sendmsg+0x2b8/0xb90 drivers/net/ppp/pppoe.c:903   sock_sendmsg_nosec net/socket.c:729 [inline]   __sock_sendmsg+0x30f/0x380 net/socket.c:744   ____sys_sendmsg+0x903/0xb60 net/socket.c:2602   ___sys_sendmsg+0x28d/0x3c0 net/socket.c:2656   __sys_sendmmsg+0x3c1/0x960 net/socket.c:2742   __do_sys_sendmmsg net/socket.c:2771 [inline]   __se_sys_sendmmsg net/socket.c:2768 [inline]   __x64_sys_sendmmsg+0xbc/0x120 net/socket.c:2768   x64_sys_call+0xb6e/0x3ba0 arch/x86/include/generated/asm/syscalls_64.h:308   do_syscall_x64 arch/x86/entry/common.c:52 [inline]   do_syscall_64+0xcd/0x1e0 arch/x86/entry/common.c:83  entry_SYSCALL_64_after_hwframe+0x77/0x7f  Uninit was created at:   slab_post_alloc_hook mm/slub.c:4091 [inline]   slab_alloc_node mm/slub.c:4134 [inline]   kmem_cache_alloc_node_noprof+0x6bf/0xb80 mm/slub.c:4186   kmalloc_reserve+0x13d/0x4a0 net/core/skbuff.c:587   __alloc_skb+0x363/0x7b0 net/core/skbuff.c:678   alloc_skb include/linux/skbuff.h:1322 [inline]   sock_wmalloc+0xfe/0x1a0 net/core/sock.c:2732   pppoe_sendmsg+0x3a7/0xb90 drivers/net/ppp/pppoe.c:867   sock_sendmsg_nosec net/socket.c:729 [inline]   __sock_sendmsg+0x30f/0x380 net/socket.c:744   ____sys_sendmsg+0x903/0xb60 net/socket.c:2602   ___sys_sendmsg+0x28d/0x3c0 net/socket.c:2656   __sys_sendmmsg+0x3c1/0x960 net/socket.c:2742   __do_sys_sendmmsg net/socket.c:2771 [inline]   __se_sys_sendmmsg net/socket.c:2768 [inline]   __x64_sys_sendmmsg+0xbc/0x120 net/socket.c:2768   x64_sys_call+0xb6e/0x3ba0 arch/x86/include/generated/asm/syscalls_64.h:308   do_syscall_x64 arch/x86/entry/common.c:52 [inline]   do_syscall_64+0xcd/0x1e0 arch/x86/entry/common.c:83  entry_SYSCALL_64_after_hwframe+0x77/0x7f  CPU: 0 UID: 0 PID: 5460 Comm: syz.2.33 Not tainted 6.12.0-rc2-syzkaller-00006-g87d6aab2389e #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 09/13/2024(CVE-2024-50033)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  net: do not delay dst_entries_add() in dst_release()  dst_entries_add() uses per-cpu data that might be freed at netns dismantle from ip6_route_net_exit() calling dst_entries_destroy()  Before ip6_route_net_exit() can be called, we release all the dsts associated with this netns, via calls to dst_release(), which waits an rcu grace period before calling dst_destroy()  dst_entries_add() use in dst_destroy() is racy, because dst_entries_destroy() could have been called already.  Decrementing the number of dsts must happen sooner.  Notes:  1) in CONFIG_XFRM case, dst_destroy() can call    dst_release_immediate(child), this might also cause UAF    if the child does not have DST_NOCOUNT set.    IPSEC maintainers might take a look and see how to address this.  2) There is also discussion about removing this count of dst,    which might happen in future kernels.(CVE-2024-50036)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  igb: Do not bring the device up after non-fatal error  Commit 004d25060c78 (\u0026quot;igb: Fix igb_down hung on surprise removal\u0026quot;) changed igb_io_error_detected() to ignore non-fatal pcie errors in order to avoid hung task that can happen when igb_down() is called multiple times. This caused an issue when processing transient non-fatal errors. igb_io_resume(), which is called after igb_io_error_detected(), assumes that device is brought down by igb_io_error_detected() if the interface is up. This resulted in panic with stacktrace below.  [ T3256] igb 0000:09:00.0 haeth0: igb: haeth0 NIC Link is Down [  T292] pcieport 0000:00:1c.5: AER: Uncorrected (Non-Fatal) error received: 0000:09:00.0 [  T292] igb 0000:09:00.0: PCIe Bus Error: severity=Uncorrected (Non-Fatal), type=Transaction Layer, (Requester ID) [  T292] igb 0000:09:00.0:   device [8086:1537] error status/mask=00004000/00000000 [  T292] igb 0000:09:00.0:    [14] CmpltTO [  200.105524,009][  T292] igb 0000:09:00.0: AER:   TLP Header: 00000000 00000000 00000000 00000000 [  T292] pcieport 0000:00:1c.5: AER: broadcast error_detected message [  T292] igb 0000:09:00.0: Non-correctable non-fatal error reported. [  T292] pcieport 0000:00:1c.5: AER: broadcast mmio_enabled message [  T292] pcieport 0000:00:1c.5: AER: broadcast resume message [  T292] ------------[ cut here ]------------ [  T292] kernel BUG at net/core/dev.c:6539! [  T292] invalid opcode: 0000 [#1] PREEMPT SMP [  T292] RIP: 0010:napi_enable+0x37/0x40 [  T292] Call Trace: [  T292]  \u0026lt;TASK\u0026gt; [  T292]  ? die+0x33/0x90 [  T292]  ? do_trap+0xdc/0x110 [  T292]  ? napi_enable+0x37/0x40 [  T292]  ? do_error_trap+0x70/0xb0 [  T292]  ? napi_enable+0x37/0x40 [  T292]  ? napi_enable+0x37/0x40 [  T292]  ? exc_invalid_op+0x4e/0x70 [  T292]  ? napi_enable+0x37/0x40 [  T292]  ? asm_exc_invalid_op+0x16/0x20 [  T292]  ? napi_enable+0x37/0x40 [  T292]  igb_up+0x41/0x150 [  T292]  igb_io_resume+0x25/0x70 [  T292]  report_resume+0x54/0x70 [  T292]  ? report_frozen_detected+0x20/0x20 [  T292]  pci_walk_bus+0x6c/0x90 [  T292]  ? aer_print_port_info+0xa0/0xa0 [  T292]  pcie_do_recovery+0x22f/0x380 [  T292]  aer_process_err_devices+0x110/0x160 [  T292]  aer_isr+0x1c1/0x1e0 [  T292]  ? disable_irq_nosync+0x10/0x10 [  T292]  irq_thread_fn+0x1a/0x60 [  T292]  irq_thread+0xe3/0x1a0 [  T292]  ? irq_set_affinity_notifier+0x120/0x120 [  T292]  ? irq_affinity_notify+0x100/0x100 [  T292]  kthread+0xe2/0x110 [  T292]  ? kthread_complete_and_exit+0x20/0x20 [  T292]  ret_from_fork+0x2d/0x50 [  T292]  ? kthread_complete_and_exit+0x20/0x20 [  T292]  ret_from_fork_asm+0x11/0x20 [  T292]  \u0026lt;/TASK\u0026gt;  To fix this issue igb_io_resume() checks if the interface is running and the device is not down this means igb_io_error_detected() did not bring the device down and there is no need to bring it up.(CVE-2024-50040)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  i40e: Fix macvlan leak by synchronizing access to mac_filter_hash  This patch addresses a macvlan leak issue in the i40e driver caused by concurrent access to vsi-\u0026gt;mac_filter_hash. The leak occurs when multiple threads attempt to modify the mac_filter_hash simultaneously, leading to inconsistent state and potential memory leaks.  To fix this, we now wrap the calls to i40e_del_mac_filter() and zeroing vf-\u0026gt;default_lan_addr.addr with spin_lock/unlock_bh(\u0026amp;vsi-\u0026gt;mac_filter_hash_lock), ensuring atomic operations and preventing concurrent access.  Additionally, we add lockdep_assert_held(\u0026amp;vsi-\u0026gt;mac_filter_hash_lock) in i40e_add_mac_filter() to help catch similar issues in the future.  Reproduction steps: 1. Spawn VFs and configure port vlan on them. 2. Trigger concurrent macvlan operations (e.g., adding and deleting  portvlan and/or mac filters). 3. Observe the potential memory leak and inconsistent state in the  mac_filter_hash.  This synchronization ensures the integrity of the mac_filter_hash and prevents the described leak.(CVE-2024-50041)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  smb: client: fix UAF in async decryption  Doing an async decryption (large read) crashes with a slab-use-after-free way down in the crypto API.  Reproducer:     # mount.cifs -o ...,seal,esize=1 //srv/share /mnt     # dd if=/mnt/largefile of=/dev/null     ...     [  194.196391] ==================================================================     [  194.196844] BUG: KASAN: slab-use-after-free in gf128mul_4k_lle+0xc1/0x110     [  194.197269] Read of size 8 at addr ffff888112bd0448 by task kworker/u77:2/899     [  194.197707]     [  194.197818] CPU: 12 UID: 0 PID: 899 Comm: kworker/u77:2 Not tainted 6.11.0-lku-00028-gfca3ca14a17a-dirty #43     [  194.198400] Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS rel-1.16.2-3-gd478f380-prebuilt.qemu.org 04/01/2014     [  194.199046] Workqueue: smb3decryptd smb2_decrypt_offload [cifs]     [  194.200032] Call Trace:     [  194.200191]  \u0026lt;TASK\u0026gt;     [  194.200327]  dump_stack_lvl+0x4e/0x70     [  194.200558]  ? gf128mul_4k_lle+0xc1/0x110     [  194.200809]  print_report+0x174/0x505     [  194.201040]  ? __pfx__raw_spin_lock_irqsave+0x10/0x10     [  194.201352]  ? srso_return_thunk+0x5/0x5f     [  194.201604]  ? __virt_addr_valid+0xdf/0x1c0     [  194.201868]  ? gf128mul_4k_lle+0xc1/0x110     [  194.202128]  kasan_report+0xc8/0x150     [  194.202361]  ? gf128mul_4k_lle+0xc1/0x110     [  194.202616]  gf128mul_4k_lle+0xc1/0x110     [  194.202863]  ghash_update+0x184/0x210     [  194.203103]  shash_ahash_update+0x184/0x2a0     [  194.203377]  ? __pfx_shash_ahash_update+0x10/0x10     [  194.203651]  ? srso_return_thunk+0x5/0x5f     [  194.203877]  ? crypto_gcm_init_common+0x1ba/0x340     [  194.204142]  gcm_hash_assoc_remain_continue+0x10a/0x140     [  194.204434]  crypt_message+0xec1/0x10a0 [cifs]     [  194.206489]  ? __pfx_crypt_message+0x10/0x10 [cifs]     [  194.208507]  ? srso_return_thunk+0x5/0x5f     [  194.209205]  ? srso_return_thunk+0x5/0x5f     [  194.209925]  ? srso_return_thunk+0x5/0x5f     [  194.210443]  ? srso_return_thunk+0x5/0x5f     [  194.211037]  decrypt_raw_data+0x15f/0x250 [cifs]     [  194.212906]  ? __pfx_decrypt_raw_data+0x10/0x10 [cifs]     [  194.214670]  ? srso_return_thunk+0x5/0x5f     [  194.215193]  smb2_decrypt_offload+0x12a/0x6c0 [cifs]  This is because TFM is being used in parallel.  Fix this by allocating a new AEAD TFM for async decryption, but keep the existing one for synchronous READ cases (similar to what is done in smb3_calc_signature()).  Also remove the calls to aead_request_set_callback() and crypto_wait_req() since it\u0026apos;s always going to be a synchronous operation.(CVE-2024-50047)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  driver core: bus: Fix double free in driver API bus_register()  For bus_register(), any error which happens after kset_register() will cause that @priv are freed twice, fixed by setting @priv with NULL after the first free.(CVE-2024-50055)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  serial: protect uart_port_dtr_rts() in uart_shutdown() too  Commit af224ca2df29 (serial: core: Prevent unsafe uart port access, part 3) added few uport == NULL checks. It added one to uart_shutdown(), so the commit assumes, uport can be NULL in there. But right after that protection, there is an unprotected \u0026quot;uart_port_dtr_rts(uport, false);\u0026quot; call. That is invoked only if HUPCL is set, so I assume that is the reason why we do not see lots of these reports.  Or it cannot be NULL at this point at all for some reason :P.  Until the above is investigated, stay on the safe side and move this dereference to the if too.  I got this inconsistency from Coverity under CID 1585130. Thanks.(CVE-2024-50058)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  ntb: ntb_hw_switchtec: Fix use after free vulnerability in switchtec_ntb_remove due to race condition  In the switchtec_ntb_add function, it can call switchtec_ntb_init_sndev function, then \u0026amp;sndev-\u0026gt;check_link_status_work is bound with check_link_status_work. switchtec_ntb_link_notification may be called to start the work.  If we remove the module which will call switchtec_ntb_remove to make cleanup, it will free sndev through kfree(sndev), while the work mentioned above will be used. The sequence of operations that may lead to a UAF bug is as follows:  CPU0                                 CPU1                          | check_link_status_work switchtec_ntb_remove    | kfree(sndev);           |                         | if (sndev-\u0026gt;link_force_down)                         | // use sndev  Fix it by ensuring that the work is canceled before proceeding with the cleanup in switchtec_ntb_remove.(CVE-2024-50059)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  io_uring: check if we need to reschedule during overflow flush  In terms of normal application usage, this list will always be empty. And if an application does overflow a bit, it\u0026apos;ll have a few entries. However, nothing obviously prevents syzbot from running a test case that generates a ton of overflow entries, and then flushing them can take quite a while.  Check for needing to reschedule while flushing, and drop our locks and do so if necessary. There\u0026apos;s no state to maintain here as overflows always prune from head-of-list, hence it\u0026apos;s fine to drop and reacquire the locks at the end of the loop.(CVE-2024-50060)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  bpf: Prevent tail call between progs attached to different hooks  bpf progs can be attached to kernel functions, and the attached functions can take different parameters or return different return values. If prog attached to one kernel function tail calls prog attached to another kernel function, the ctx access or return value verification could be bypassed.  For example, if prog1 is attached to func1 which takes only 1 parameter and prog2 is attached to func2 which takes two parameters. Since verifier assumes the bpf ctx passed to prog2 is constructed based on func2\u0026apos;s prototype, verifier allows prog2 to access the second parameter from the bpf ctx passed to it. The problem is that verifier does not prevent prog1 from passing its bpf ctx to prog2 via tail call. In this case, the bpf ctx passed to prog2 is constructed from func1 instead of func2, that is, the assumption for ctx access verification is bypassed.  Another example, if BPF LSM prog1 is attached to hook file_alloc_security, and BPF LSM prog2 is attached to hook bpf_lsm_audit_rule_known. Verifier knows the return value rules for these two hooks, e.g. it is legal for bpf_lsm_audit_rule_known to return positive number 1, and it is illegal for file_alloc_security to return positive number. So verifier allows prog2 to return positive number 1, but does not allow prog1 to return positive number. The problem is that verifier does not prevent prog1 from calling prog2 via tail call. In this case, prog2\u0026apos;s return value 1 will be used as the return value for prog1\u0026apos;s hook file_alloc_security. That is, the return value rule is bypassed.  This patch adds restriction for tail call to prevent such bypasses.(CVE-2024-50063)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  zram: free secondary algorithms names  We need to kfree() secondary algorithms names when reset zram device that had multi-streams, otherwise we leak memory.  [senozhatsky@chromium.org: kfree(NULL) is legal]   Link: https://lkml.kernel.org/r/20240917013021.868769-1-senozhatsky@chromium.org(CVE-2024-50064)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  mm/mremap: fix move_normal_pmd/retract_page_tables race  In mremap(), move_page_tables() looks at the type of the PMD entry and the specified address range to figure out by which method the next chunk of page table entries should be moved.  At that point, the mmap_lock is held in write mode, but no rmap locks are held yet.  For PMD entries that point to page tables and are fully covered by the source address range, move_pgt_entry(NORMAL_PMD, ...) is called, which first takes rmap locks, then does move_normal_pmd().  move_normal_pmd() takes the necessary page table locks at source and destination, then moves an entire page table from the source to the destination.  The problem is: The rmap locks, which protect against concurrent page table removal by retract_page_tables() in the THP code, are only taken after the PMD entry has been read and it has been decided how to move it.  So we can race as follows (with two processes that have mappings of the same tmpfs file that is stored on a tmpfs mount with huge=advise); note that process A accesses page tables through the MM while process B does it through the file rmap:  process A                      process B =========                      ========= mremap   mremap_to     move_vma       move_page_tables         get_old_pmd         alloc_new_pmd                       *** PREEMPT ***                                madvise(MADV_COLLAPSE)                                  do_madvise                                    madvise_walk_vmas                                      madvise_vma_behavior                                        madvise_collapse                                          hpage_collapse_scan_file                                            collapse_file                                              retract_page_tables                                                i_mmap_lock_read(mapping)                                                pmdp_collapse_flush                                                i_mmap_unlock_read(mapping)         move_pgt_entry(NORMAL_PMD, ...)           take_rmap_locks           move_normal_pmd           drop_rmap_locks  When this happens, move_normal_pmd() can end up creating bogus PMD entries in the line `pmd_populate(mm, new_pmd, pmd_pgtable(pmd))`.  The effect depends on arch-specific and machine-specific details; on x86, you can end up with physical page 0 mapped as a page table, which is likely exploitable for user-\u0026gt;kernel privilege escalation.  Fix the race by letting process B recheck that the PMD still points to a page table after the rmap locks have been taken.  Otherwise, we bail and let the caller fall back to the PTE-level copying path, which will then bail immediately at the pmd_none() check.  Bug reachability: Reaching this bug requires that you can create shmem/file THP mappings - anonymous THP uses different code that doesn\u0026apos;t zap stuff under rmap locks.  File THP is gated on an experimental config flag (CONFIG_READ_ONLY_THP_FOR_FS), so on normal distro kernels you need shmem THP to hit this bug.  As far as I know, getting shmem THP normally requires that you can mount your own tmpfs with the right mount flags, which would require creating your own user+mount namespace; though I don\u0026apos;t know if some distros maybe enable shmem THP by default or something like that.  Bug impact: This issue can likely be used for user-\u0026gt;kernel privilege escalation when it is reachable.(CVE-2024-50066)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  uprobe: avoid out-of-bounds memory access of fetching args  Uprobe needs to fetch args into a percpu buffer, and then copy to ring buffer to avoid non-atomic context problem.  Sometimes user-space strings, arrays can be very large, but the size of percpu buffer is only page size. And store_trace_args() won\u0026apos;t check whether these data exceeds a single page or not, caused out-of-bounds memory access.  It could be reproduced by following steps: 1. build kernel with CONFIG_KASAN enabled 2. save follow program as test.c  ``` \\#include \u0026lt;stdio.h\u0026gt; \\#include \u0026lt;stdlib.h\u0026gt; \\#include \u0026lt;string.h\u0026gt;  // If string length large than MAX_STRING_SIZE, the fetch_store_strlen() // will return 0, cause __get_data_size() return shorter size, and // store_trace_args() will not trigger out-of-bounds access. // So make string length less than 4096. \\#define STRLEN 4093  void generate_string(char *str, int n) {     int i;     for (i = 0; i \u0026lt; n; ++i)     {         char c = i % 26 + \u0026apos;a\u0026apos;;         str[i] = c;     }     str[n-1] = \u0026apos;\\0\u0026apos;; }  void print_string(char *str) {     printf(\u0026quot;%s\\n\u0026quot;, str); }  int main() {     char tmp[STRLEN];      generate_string(tmp, STRLEN);     print_string(tmp);      return 0; } ``` 3. compile program `gcc -o test test.c`  4. get the offset of `print_string()` ``` objdump -t test | grep -w print_string 0000000000401199 g     F .text  000000000000001b              print_string ```  5. configure uprobe with offset 0x1199 ``` off=0x1199  cd /sys/kernel/debug/tracing/ echo \u0026quot;p /root/test:${off} arg1=+0(%di):ustring arg2=\\$comm arg3=+0(%di):ustring\u0026quot;  \u0026gt; uprobe_events echo 1 \u0026gt; events/uprobes/enable echo 1 \u0026gt; tracing_on ```  6. run `test`, and kasan will report error. ================================================================== BUG: KASAN: use-after-free in strncpy_from_user+0x1d6/0x1f0 Write of size 8 at addr ffff88812311c004 by task test/499CPU: 0 UID: 0 PID: 499 Comm: test Not tainted 6.12.0-rc3+ #18 Hardware name: Red Hat KVM, BIOS 1.16.0-4.al8 04/01/2014 Call Trace:  \u0026lt;TASK\u0026gt;  dump_stack_lvl+0x55/0x70  print_address_description.constprop.0+0x27/0x310  kasan_report+0x10f/0x120  ? strncpy_from_user+0x1d6/0x1f0  strncpy_from_user+0x1d6/0x1f0  ? rmqueue.constprop.0+0x70d/0x2ad0  process_fetch_insn+0xb26/0x1470  ? __pfx_process_fetch_insn+0x10/0x10  ? _raw_spin_lock+0x85/0xe0  ? __pfx__raw_spin_lock+0x10/0x10  ? __pte_offset_map+0x1f/0x2d0  ? unwind_next_frame+0xc5f/0x1f80  ? arch_stack_walk+0x68/0xf0  ? is_bpf_text_address+0x23/0x30  ? kernel_text_address.part.0+0xbb/0xd0  ? __kernel_text_address+0x66/0xb0  ? unwind_get_return_address+0x5e/0xa0  ? __pfx_stack_trace_consume_entry+0x10/0x10  ? arch_stack_walk+0xa2/0xf0  ? _raw_spin_lock_irqsave+0x8b/0xf0  ? __pfx__raw_spin_lock_irqsave+0x10/0x10  ? depot_alloc_stack+0x4c/0x1f0  ? _raw_spin_unlock_irqrestore+0xe/0x30  ? stack_depot_save_flags+0x35d/0x4f0  ? kasan_save_stack+0x34/0x50  ? kasan_save_stack+0x24/0x50  ? mutex_lock+0x91/0xe0  ? __pfx_mutex_lock+0x10/0x10  prepare_uprobe_buffer.part.0+0x2cd/0x500  uprobe_dispatcher+0x2c3/0x6a0  ? __pfx_uprobe_dispatcher+0x10/0x10  ? __kasan_slab_alloc+0x4d/0x90  handler_chain+0xdd/0x3e0  handle_swbp+0x26e/0x3d0  ? __pfx_handle_swbp+0x10/0x10  ? uprobe_pre_sstep_notifier+0x151/0x1b0  irqentry_exit_to_user_mode+0xe2/0x1b0  asm_exc_int3+0x39/0x40 RIP: 0033:0x401199 Code: 01 c2 0f b6 45 fb 88 02 83 45 fc 01 8b 45 fc 3b 45 e4 7c b7 8b 45 e4 48 98 48 8d 50 ff 48 8b 45 e8 48 01 d0 ce RSP: 002b:00007ffdf00576a8 EFLAGS: 00000206 RAX: 00007ffdf00576b0 RBX: 0000000000000000 RCX: 0000000000000ff2 RDX: 0000000000000ffc RSI: 0000000000000ffd RDI: 00007ffdf00576b0 RBP: 00007ffdf00586b0 R08: 00007feb2f9c0d20 R09: 00007feb2f9c0d20 R10: 0000000000000001 R11: 0000000000000202 R12: 0000000000401040 R13: 00007ffdf0058780 R14: 0000000000000000 R15: 0000000000000000  \u0026lt;/TASK\u0026gt;  This commit enforces the buffer\u0026apos;s maxlen less than a page-size to avoid store_trace_args() out-of-memory access.(CVE-2024-50067)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  pinctrl: stm32: check devm_kasprintf() returned value  devm_kasprintf() can return a NULL pointer on failure but this returned value is not checked. Fix this lack and check the returned value.  Found by code review.(CVE-2024-50070)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  x86/bugs: Use code segment selector for VERW operand  Robert Gill reported below #GP in 32-bit mode when dosemu software was executing vm86() system call:    general protection fault: 0000 [#1] PREEMPT SMP   CPU: 4 PID: 4610 Comm: dosemu.bin Not tainted 6.6.21-gentoo-x86 #1   Hardware name: Dell Inc. PowerEdge 1950/0H723K, BIOS 2.7.0 10/30/2010   EIP: restore_all_switch_stack+0xbe/0xcf   EAX: 00000000 EBX: 00000000 ECX: 00000000 EDX: 00000000   ESI: 00000000 EDI: 00000000 EBP: 00000000 ESP: ff8affdc   DS: 0000 ES: 0000 FS: 0000 GS: 0033 SS: 0068 EFLAGS: 00010046   CR0: 80050033 CR2: 00c2101c CR3: 04b6d000 CR4: 000406d0   Call Trace:    show_regs+0x70/0x78    die_addr+0x29/0x70    exc_general_protection+0x13c/0x348    exc_bounds+0x98/0x98    handle_exception+0x14d/0x14d    exc_bounds+0x98/0x98    restore_all_switch_stack+0xbe/0xcf    exc_bounds+0x98/0x98    restore_all_switch_stack+0xbe/0xcf  This only happens in 32-bit mode when VERW based mitigations like MDS/RFDS are enabled. This is because segment registers with an arbitrary user value can result in #GP when executing VERW. Intel SDM vol. 2C documents the following behavior for VERW instruction:    #GP(0) - If a memory operand effective address is outside the CS, DS, ES,     FS, or GS segment limit.  CLEAR_CPU_BUFFERS macro executes VERW instruction before returning to user space. Use %cs selector to reference VERW operand. This ensures VERW will not #GP for an arbitrary user %ds.  [ mingo: Fixed the SOB chain. ](CVE-2024-50072)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  parport: Proper fix for array out-of-bounds access  The recent fix for array out-of-bounds accesses replaced sprintf() calls blindly with snprintf().  However, since snprintf() returns the would-be-printed size, not the actually output size, the length calculation can still go over the given limit.  Use scnprintf() instead of snprintf(), which returns the actually output letters, for addressing the potential out-of-bounds access properly.(CVE-2024-50074)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  vt: prevent kernel-infoleak in con_font_get()  font.data may not initialize all memory spaces depending on the implementation of vc-\u0026gt;vc_sw-\u0026gt;con_font_get. This may cause info-leak, so to prevent this, it is safest to modify it to initialize the allocated memory space to 0, and it generally does not affect the overall performance of the system.(CVE-2024-50076)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  tcp: fix mptcp DSS corruption due to large pmtu xmit  Syzkaller was able to trigger a DSS corruption:    TCP: request_sock_subflow_v4: Possible SYN flooding on port [::]:20002. Sending cookies.   ------------[ cut here ]------------   WARNING: CPU: 0 PID: 5227 at net/mptcp/protocol.c:695 __mptcp_move_skbs_from_subflow+0x20a9/0x21f0 net/mptcp/protocol.c:695   Modules linked in:   CPU: 0 UID: 0 PID: 5227 Comm: syz-executor350 Not tainted 6.11.0-syzkaller-08829-gaf9c191ac2a0 #0   Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 08/06/2024   RIP: 0010:__mptcp_move_skbs_from_subflow+0x20a9/0x21f0 net/mptcp/protocol.c:695   Code: 0f b6 dc 31 ff 89 de e8 b5 dd ea f5 89 d8 48 81 c4 50 01 00 00 5b 41 5c 41 5d 41 5e 41 5f 5d c3 cc cc cc cc e8 98 da ea f5 90 \u0026lt;0f\u0026gt; 0b 90 e9 47 ff ff ff e8 8a da ea f5 90 0f 0b 90 e9 99 e0 ff ff   RSP: 0018:ffffc90000006db8 EFLAGS: 00010246   RAX: ffffffff8ba9df18 RBX: 00000000000055f0 RCX: ffff888030023c00   RDX: 0000000000000100 RSI: 00000000000081e5 RDI: 00000000000055f0   RBP: 1ffff110062bf1ae R08: ffffffff8ba9cf12 R09: 1ffff110062bf1b8   R10: dffffc0000000000 R11: ffffed10062bf1b9 R12: 0000000000000000   R13: dffffc0000000000 R14: 00000000700cec61 R15: 00000000000081e5   FS:  000055556679c380(0000) GS:ffff8880b8600000(0000) knlGS:0000000000000000   CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033   CR2: 0000000020287000 CR3: 0000000077892000 CR4: 00000000003506f0   DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000   DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400   Call Trace:    \u0026lt;IRQ\u0026gt;    move_skbs_to_msk net/mptcp/protocol.c:811 [inline]    mptcp_data_ready+0x29c/0xa90 net/mptcp/protocol.c:854    subflow_data_ready+0x34a/0x920 net/mptcp/subflow.c:1490    tcp_data_queue+0x20fd/0x76c0 net/ipv4/tcp_input.c:5283    tcp_rcv_established+0xfba/0x2020 net/ipv4/tcp_input.c:6237    tcp_v4_do_rcv+0x96d/0xc70 net/ipv4/tcp_ipv4.c:1915    tcp_v4_rcv+0x2dc0/0x37f0 net/ipv4/tcp_ipv4.c:2350    ip_protocol_deliver_rcu+0x22e/0x440 net/ipv4/ip_input.c:205    ip_local_deliver_finish+0x341/0x5f0 net/ipv4/ip_input.c:233    NF_HOOK+0x3a4/0x450 include/linux/netfilter.h:314    NF_HOOK+0x3a4/0x450 include/linux/netfilter.h:314    __netif_receive_skb_one_core net/core/dev.c:5662 [inline]    __netif_receive_skb+0x2bf/0x650 net/core/dev.c:5775    process_backlog+0x662/0x15b0 net/core/dev.c:6107    __napi_poll+0xcb/0x490 net/core/dev.c:6771    napi_poll net/core/dev.c:6840 [inline]    net_rx_action+0x89b/0x1240 net/core/dev.c:6962    handle_softirqs+0x2c5/0x980 kernel/softirq.c:554    do_softirq+0x11b/0x1e0 kernel/softirq.c:455    \u0026lt;/IRQ\u0026gt;    \u0026lt;TASK\u0026gt;    __local_bh_enable_ip+0x1bb/0x200 kernel/softirq.c:382    local_bh_enable include/linux/bottom_half.h:33 [inline]    rcu_read_unlock_bh include/linux/rcupdate.h:919 [inline]    __dev_queue_xmit+0x1764/0x3e80 net/core/dev.c:4451    dev_queue_xmit include/linux/netdevice.h:3094 [inline]    neigh_hh_output include/net/neighbour.h:526 [inline]    neigh_output include/net/neighbour.h:540 [inline]    ip_finish_output2+0xd41/0x1390 net/ipv4/ip_output.c:236    ip_local_out net/ipv4/ip_output.c:130 [inline]    __ip_queue_xmit+0x118c/0x1b80 net/ipv4/ip_output.c:536    __tcp_transmit_skb+0x2544/0x3b30 net/ipv4/tcp_output.c:1466    tcp_transmit_skb net/ipv4/tcp_output.c:1484 [inline]    tcp_mtu_probe net/ipv4/tcp_output.c:2547 [inline]    tcp_write_xmit+0x641d/0x6bf0 net/ipv4/tcp_output.c:2752    __tcp_push_pending_frames+0x9b/0x360 net/ipv4/tcp_output.c:3015    tcp_push_pending_frames include/net/tcp.h:2107 [inline]    tcp_data_snd_check net/ipv4/tcp_input.c:5714 [inline]    tcp_rcv_established+0x1026/0x2020 net/ipv4/tcp_input.c:6239    tcp_v4_do_rcv+0x96d/0xc70 net/ipv4/tcp_ipv4.c:1915    sk_backlog_rcv include/net/sock.h:1113 [inline]    __release_sock+0x214/0x350 net/core/sock.c:3072    release_sock+0x61/0x1f0 net/core/sock.c:3626    mptcp_push_ ---truncated---(CVE-2024-50083)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  net: microchip: vcap api: Fix memory leaks in vcap_api_encode_rule_test()  Commit a3c1e45156ad (\u0026quot;net: microchip: vcap: Fix use-after-free error in kunit test\u0026quot;) fixed the use-after-free error, but introduced below memory leaks by removing necessary vcap_free_rule(), add it to fix it.   unreferenced object 0xffffff80ca58b700 (size 192):    comm \u0026quot;kunit_try_catch\u0026quot;, pid 1215, jiffies 4294898264    hex dump (first 32 bytes):      00 12 7a 00 05 00 00 00 0a 00 00 00 64 00 00 00  ..z.........d...      00 00 00 00 00 00 00 00 00 04 0b cc 80 ff ff ff  ................    backtrace (crc 9c09c3fe):      [\u0026lt;0000000052a0be73\u0026gt;] kmemleak_alloc+0x34/0x40      [\u0026lt;0000000043605459\u0026gt;] __kmalloc_cache_noprof+0x26c/0x2f4      [\u0026lt;0000000040a01b8d\u0026gt;] vcap_alloc_rule+0x3cc/0x9c4      [\u0026lt;000000003fe86110\u0026gt;] vcap_api_encode_rule_test+0x1ac/0x16b0      [\u0026lt;00000000b3595fc4\u0026gt;] kunit_try_run_case+0x13c/0x3ac      [\u0026lt;0000000010f5d2bf\u0026gt;] kunit_generic_run_threadfn_adapter+0x80/0xec      [\u0026lt;00000000c5d82c9a\u0026gt;] kthread+0x2e8/0x374      [\u0026lt;00000000f4287308\u0026gt;] ret_from_fork+0x10/0x20  unreferenced object 0xffffff80cc0b0400 (size 64):    comm \u0026quot;kunit_try_catch\u0026quot;, pid 1215, jiffies 4294898265    hex dump (first 32 bytes):      80 04 0b cc 80 ff ff ff 18 b7 58 ca 80 ff ff ff  ..........X.....      39 00 00 00 02 00 00 00 06 05 04 03 02 01 ff ff  9...............    backtrace (crc daf014e9):      [\u0026lt;0000000052a0be73\u0026gt;] kmemleak_alloc+0x34/0x40      [\u0026lt;0000000043605459\u0026gt;] __kmalloc_cache_noprof+0x26c/0x2f4      [\u0026lt;000000000ff63fd4\u0026gt;] vcap_rule_add_key+0x2cc/0x528      [\u0026lt;00000000dfdb1e81\u0026gt;] vcap_api_encode_rule_test+0x224/0x16b0      [\u0026lt;00000000b3595fc4\u0026gt;] kunit_try_run_case+0x13c/0x3ac      [\u0026lt;0000000010f5d2bf\u0026gt;] kunit_generic_run_threadfn_adapter+0x80/0xec      [\u0026lt;00000000c5d82c9a\u0026gt;] kthread+0x2e8/0x374      [\u0026lt;00000000f4287308\u0026gt;] ret_from_fork+0x10/0x20  unreferenced object 0xffffff80cc0b0700 (size 64):    comm \u0026quot;kunit_try_catch\u0026quot;, pid 1215, jiffies 4294898265    hex dump (first 32 bytes):      80 07 0b cc 80 ff ff ff 28 b7 58 ca 80 ff ff ff  ........(.X.....      3c 00 00 00 00 00 00 00 01 2f 03 b3 ec ff ff ff  \u0026lt;......../......    backtrace (crc 8d877792):      [\u0026lt;0000000052a0be73\u0026gt;] kmemleak_alloc+0x34/0x40      [\u0026lt;0000000043605459\u0026gt;] __kmalloc_cache_noprof+0x26c/0x2f4      [\u0026lt;000000006eadfab7\u0026gt;] vcap_rule_add_action+0x2d0/0x52c      [\u0026lt;00000000323475d1\u0026gt;] vcap_api_encode_rule_test+0x4d4/0x16b0      [\u0026lt;00000000b3595fc4\u0026gt;] kunit_try_run_case+0x13c/0x3ac      [\u0026lt;0000000010f5d2bf\u0026gt;] kunit_generic_run_threadfn_adapter+0x80/0xec      [\u0026lt;00000000c5d82c9a\u0026gt;] kthread+0x2e8/0x374      [\u0026lt;00000000f4287308\u0026gt;] ret_from_fork+0x10/0x20  unreferenced object 0xffffff80cc0b0900 (size 64):    comm \u0026quot;kunit_try_catch\u0026quot;, pid 1215, jiffies 4294898266    hex dump (first 32 bytes):      80 09 0b cc 80 ff ff ff 80 06 0b cc 80 ff ff ff  ................      7d 00 00 00 01 00 00 00 00 00 00 00 ff 00 00 00  }...............    backtrace (crc 34181e56):      [\u0026lt;0000000052a0be73\u0026gt;] kmemleak_alloc+0x34/0x40      [\u0026lt;0000000043605459\u0026gt;] __kmalloc_cache_noprof+0x26c/0x2f4      [\u0026lt;000000000ff63fd4\u0026gt;] vcap_rule_add_key+0x2cc/0x528      [\u0026lt;00000000991e3564\u0026gt;] vcap_val_rule+0xcf0/0x13e8      [\u0026lt;00000000fc9868e5\u0026gt;] vcap_api_encode_rule_test+0x678/0x16b0      [\u0026lt;00000000b3595fc4\u0026gt;] kunit_try_run_case+0x13c/0x3ac      [\u0026lt;0000000010f5d2bf\u0026gt;] kunit_generic_run_threadfn_adapter+0x80/0xec      [\u0026lt;00000000c5d82c9a\u0026gt;] kthread+0x2e8/0x374      [\u0026lt;00000000f4287308\u0026gt;] ret_from_fork+0x10/0x20  unreferenced object 0xffffff80cc0b0980 (size 64):    comm \u0026quot;kunit_try_catch\u0026quot;, pid 1215, jiffies 4294898266    hex dump (first 32 bytes):      18 b7 58 ca 80 ff ff ff 00 09 0b cc 80 ff ff ff  ..X.............      67 00 00 00 00 00 00 00 01 01 74 88 c0 ff ff ff  g.........t.....    backtrace (crc 275fd9be):      [\u0026lt;0000000052a0be73\u0026gt;] kmemleak_alloc+0x34/0x40      [\u0026lt;0000000043605459\u0026gt;] __kmalloc_cache_noprof+0x26c/0x2f4      [\u0026lt;000000000ff63fd4\u0026gt;] vcap_rule_add_key+0x2cc/0x528      [\u0026lt;000000001396a1a2\u0026gt;] test_add_de ---truncated---(CVE-2024-50084)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  btrfs: fix uninitialized pointer free on read_alloc_one_name() error  The function read_alloc_one_name() does not initialize the name field of the passed fscrypt_str struct if kmalloc fails to allocate the corresponding buffer.  Thus, it is not guaranteed that fscrypt_str.name is initialized when freeing it.  This is a follow-up to the linked patch that fixes the remaining instances of the bug introduced by commit e43eec81c516 (\u0026quot;btrfs: use struct qstr instead of name and namelen pairs\u0026quot;).(CVE-2024-50087)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  btrfs: fix uninitialized pointer free in add_inode_ref()  The add_inode_ref() function does not initialize the \u0026quot;name\u0026quot; struct when it is declared.  If any of the following calls to \u0026quot;read_one_inode() returns NULL,   dir = read_one_inode(root, parent_objectid);  if (!dir) {   ret = -ENOENT;   goto out;  }   inode = read_one_inode(root, inode_objectid);  if (!inode) {   ret = -EIO;   goto out;  }  then \u0026quot;name.name\u0026quot; would be freed on \u0026quot;out\u0026quot; before being initialized.  out:  ...  kfree(name.name);  This issue was reported by Coverity with CID 1526744.(CVE-2024-50088)","status":"published","published":"2024-11-08T11:07:50Z","modified":"2026-08-18T01:18:38.656170144Z","cvss":[{"version":"3.1","score":7.8,"vector":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H","level":"high"}],"updated_at":"2026-11-02T15:52:42.253598Z"},{"id":"OESA-2024-2368","title":"kernel security update","description":"The Linux Kernel, the operating system core itself.\r\n\r\nSecurity Fix(es):\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  net: mdio: fix unbalanced fwnode reference count in mdio_device_release()  There is warning report about of_node refcount leak while probing mdio device:  OF: ERROR: memory leak, expected refcount 1 instead of 2, of_node_get()/of_node_put() unbalanced - destroy cset entry: attach overlay node /spi/soc@0/mdio@710700c0/ethernet@4  In of_mdiobus_register_device(), we increase fwnode refcount by fwnode_handle_get() before associating the of_node with mdio device, but it has never been decreased in normal path. Since that, in mdio_device_release(), it needs to call fwnode_handle_put() in addition instead of calling kfree() directly.  After above, just calling mdio_device_free() in the error handle path of of_mdiobus_register_device() is enough to keep the refcount balanced.(CVE-2022-48961)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  gpiolib: fix memory leak in gpiochip_setup_dev()  Here is a backtrace report about memory leak detected in gpiochip_setup_dev():  unreferenced object 0xffff88810b406400 (size 512):   comm \u0026quot;python3\u0026quot;, pid 1682, jiffies 4295346908 (age 24.090s)   backtrace:     kmalloc_trace     device_add  device_private_init at drivers/base/core.c:3361    (inlined by) device_add at drivers/base/core.c:3411     cdev_device_add     gpiolib_cdev_register     gpiochip_setup_dev     gpiochip_add_data_with_key  gcdev_register() \u0026amp; gcdev_unregister() would call device_add() \u0026amp; device_del() (no matter CONFIG_GPIO_CDEV is enabled or not) to register/unregister device.  However, if device_add() succeeds, some resource (like struct device_private allocated by device_private_init()) is not released by device_del().  Therefore, after device_add() succeeds by gcdev_register(), it needs to call put_device() to release resource in the error handle path.  Here we move forward the register of release function, and let it release every piece of resource by put_device() instead of kfree().  While at it, fix another subtle issue, i.e. when gc-\u0026gt;ngpio is equal to 0, we still call kcalloc() and, in case of further error, kfree() on the ZERO_PTR pointer, which is not NULL. It\u0026apos;s not a bug per se, but rather waste of the resources and potentially wrong expectation about contents of the gdev-\u0026gt;descs variable.(CVE-2022-48975)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  riscv: Sync efi page table\u0026apos;s kernel mappings before switching  The EFI page table is initially created as a copy of the kernel page table. With VMAP_STACK enabled, kernel stacks are allocated in the vmalloc area: if the stack is allocated in a new PGD (one that was not present at the moment of the efi page table creation or not synced in a previous vmalloc fault), the kernel will take a trap when switching to the efi page table when the vmalloc kernel stack is accessed, resulting in a kernel panic.  Fix that by updating the efi kernel mappings before switching to the efi page table.(CVE-2022-49004)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nmemcg_write_event_control(): fix a user-triggerable oops\r\n\r\nwe are *not* guaranteed that anything past the terminating NUL\nis mapped (let alone initialized with anything sane).(CVE-2024-45021)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\ngtp: fix a potential NULL pointer dereference\r\n\r\nWhen sockfd_lookup() fails, gtp_encap_enable_socket() returns a\nNULL pointer, but its callers only check for error pointers thus miss\nthe NULL pointer case.\r\n\r\nFix it by returning an error pointer with the error code carried from\nsockfd_lookup().\r\n\r\n(I found this bug during code inspection.)(CVE-2024-46677)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\ndrm/amd/display: Check BIOS images before it is used\r\n\r\nBIOS images may fail to load and null checks are added before they are\nused.\r\n\r\nThis fixes 6 NULL_RETURNS issues reported by Coverity.(CVE-2024-46809)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nsmack: tcp: ipv4, fix incorrect labeling\r\n\r\nCurrently, Smack mirrors the label of incoming tcp/ipv4 connections:\nwhen a label \u0026apos;foo\u0026apos; connects to a label \u0026apos;bar\u0026apos; with tcp/ipv4,\n\u0026apos;foo\u0026apos; always gets \u0026apos;foo\u0026apos; in returned ipv4 packets. So,\n1) returned packets are incorrectly labeled (\u0026apos;foo\u0026apos; instead of \u0026apos;bar\u0026apos;)\n2) \u0026apos;bar\u0026apos; can write to \u0026apos;foo\u0026apos; without being authorized to write.\r\n\r\nHere is a scenario how to see this:\r\n\r\n* Take two machines, let\u0026apos;s call them C and S,\n   with active Smack in the default state\n   (no settings, no rules, no labeled hosts, only builtin labels)\r\n\r\n* At S, add Smack rule \u0026apos;foo bar w\u0026apos;\n   (labels \u0026apos;foo\u0026apos; and \u0026apos;bar\u0026apos; are instantiated at S at this moment)\r\n\r\n* At S, at label \u0026apos;bar\u0026apos;, launch a program\n   that listens for incoming tcp/ipv4 connections\r\n\r\n* From C, at label \u0026apos;foo\u0026apos;, connect to the listener at S.\n   (label \u0026apos;foo\u0026apos; is instantiated at C at this moment)\n   Connection succeedes and works.\r\n\r\n* Send some data in both directions.\n* Collect network traffic of this connection.\r\n\r\nAll packets in both directions are labeled with the CIPSO\nof the label \u0026apos;foo\u0026apos;. Hence, label \u0026apos;bar\u0026apos; writes to \u0026apos;foo\u0026apos; without\nbeing authorized, and even without ever being known at C.\r\n\r\nIf anybody cares: exactly the same happens with DCCP.\r\n\r\nThis behavior 1st manifested in release 2.6.29.4 (see Fixes below)\nand it looks unintentional. At least, no explanation was provided.\r\n\r\nI changed returned packes label into the \u0026apos;bar\u0026apos;,\nto bring it into line with the Smack documentation claims.(CVE-2024-47659)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nfsnotify: clear PARENT_WATCHED flags lazily\r\n\r\nIn some setups directories can have many (usually negative) dentries.\nHence __fsnotify_update_child_dentry_flags() function can take a\nsignificant amount of time. Since the bulk of this function happens\nunder inode-\u0026gt;i_lock this causes a significant contention on the lock\nwhen we remove the watch from the directory as the\n__fsnotify_update_child_dentry_flags() call from fsnotify_recalc_mask()\nraces with __fsnotify_update_child_dentry_flags() calls from\n__fsnotify_parent() happening on children. This can lead upto softlockup\nreports reported by users.\r\n\r\nFix the problem by calling fsnotify_update_children_dentry_flags() to\nset PARENT_WATCHED flags only when parent starts watching children.\r\n\r\nWhen parent stops watching children, clear false positive PARENT_WATCHED\nflags lazily in __fsnotify_parent() for each accessed child.(CVE-2024-47660)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nlib/generic-radix-tree.c: Fix rare race in __genradix_ptr_alloc()\r\n\r\nIf we need to increase the tree depth, allocate a new node, and then\nrace with another thread that increased the tree depth before us, we\u0026apos;ll\nstill have a preallocated node that might be used later.\r\n\r\nIf we then use that node for a new non-root node, it\u0026apos;ll still have a\npointer to the old root instead of being zeroed - fix this by zeroing it\nin the cmpxchg failure path.(CVE-2024-47668)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nwifi: iwlwifi: mvm: pause TCM when the firmware is stopped\r\n\r\nNot doing so will make us send a host command to the transport while the\nfirmware is not alive, which will trigger a WARNING.\r\n\r\nbad state = 0\nWARNING: CPU: 2 PID: 17434 at drivers/net/wireless/intel/iwlwifi/iwl-trans.c:115 iwl_trans_send_cmd+0x1cb/0x1e0 [iwlwifi]\nRIP: 0010:iwl_trans_send_cmd+0x1cb/0x1e0 [iwlwifi]\nCall Trace:\n \u0026lt;TASK\u0026gt;\n iwl_mvm_send_cmd+0x40/0xc0 [iwlmvm]\n iwl_mvm_config_scan+0x198/0x260 [iwlmvm]\n iwl_mvm_recalc_tcm+0x730/0x11d0 [iwlmvm]\n iwl_mvm_tcm_work+0x1d/0x30 [iwlmvm]\n process_one_work+0x29e/0x640\n worker_thread+0x2df/0x690\n ? rescuer_thread+0x540/0x540\n kthread+0x192/0x1e0\n ? set_kthread_struct+0x90/0x90\n ret_from_fork+0x22/0x30(CVE-2024-47673)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  f2fs: get rid of online repaire on corrupted directory  syzbot reports a f2fs bug as below:  kernel BUG at fs/f2fs/inode.c:896! RIP: 0010:f2fs_evict_inode+0x1598/0x15c0 fs/f2fs/inode.c:896 Call Trace:  evict+0x532/0x950 fs/inode.c:704  dispose_list fs/inode.c:747 [inline]  evict_inodes+0x5f9/0x690 fs/inode.c:797  generic_shutdown_super+0x9d/0x2d0 fs/super.c:627  kill_block_super+0x44/0x90 fs/super.c:1696  kill_f2fs_super+0x344/0x690 fs/f2fs/super.c:4898  deactivate_locked_super+0xc4/0x130 fs/super.c:473  cleanup_mnt+0x41f/0x4b0 fs/namespace.c:1373  task_work_run+0x24f/0x310 kernel/task_work.c:228  ptrace_notify+0x2d2/0x380 kernel/signal.c:2402  ptrace_report_syscall include/linux/ptrace.h:415 [inline]  ptrace_report_syscall_exit include/linux/ptrace.h:477 [inline]  syscall_exit_work+0xc6/0x190 kernel/entry/common.c:173  syscall_exit_to_user_mode_prepare kernel/entry/common.c:200 [inline]  __syscall_exit_to_user_mode_work kernel/entry/common.c:205 [inline]  syscall_exit_to_user_mode+0x279/0x370 kernel/entry/common.c:218  do_syscall_64+0x100/0x230 arch/x86/entry/common.c:89  entry_SYSCALL_64_after_hwframe+0x77/0x7f RIP: 0010:f2fs_evict_inode+0x1598/0x15c0 fs/f2fs/inode.c:896  Online repaire on corrupted directory in f2fs_lookup() can generate dirty data/meta while racing w/ readonly remount, it may leave dirty inode after filesystem becomes readonly, however, checkpoint() will skips flushing dirty inode in a state of readonly mode, result in above panic.  Let\u0026apos;s get rid of online repaire in f2fs_lookup(), and leave the work to fsck.f2fs.(CVE-2024-47690)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  f2fs: fix to avoid use-after-free in f2fs_stop_gc_thread()  syzbot reports a f2fs bug as below:   __dump_stack lib/dump_stack.c:88 [inline]  dump_stack_lvl+0x241/0x360 lib/dump_stack.c:114  print_report+0xe8/0x550 mm/kasan/report.c:491  kasan_report+0x143/0x180 mm/kasan/report.c:601  kasan_check_range+0x282/0x290 mm/kasan/generic.c:189  instrument_atomic_read_write include/linux/instrumented.h:96 [inline]  atomic_fetch_add_relaxed include/linux/atomic/atomic-instrumented.h:252 [inline]  __refcount_add include/linux/refcount.h:184 [inline]  __refcount_inc include/linux/refcount.h:241 [inline]  refcount_inc include/linux/refcount.h:258 [inline]  get_task_struct include/linux/sched/task.h:118 [inline]  kthread_stop+0xca/0x630 kernel/kthread.c:704  f2fs_stop_gc_thread+0x65/0xb0 fs/f2fs/gc.c:210  f2fs_do_shutdown+0x192/0x540 fs/f2fs/file.c:2283  f2fs_ioc_shutdown fs/f2fs/file.c:2325 [inline]  __f2fs_ioctl+0x443a/0xbe60 fs/f2fs/file.c:4325  vfs_ioctl fs/ioctl.c:51 [inline]  __do_sys_ioctl fs/ioctl.c:907 [inline]  __se_sys_ioctl+0xfc/0x170 fs/ioctl.c:893  do_syscall_x64 arch/x86/entry/common.c:52 [inline]  do_syscall_64+0xf3/0x230 arch/x86/entry/common.c:83  entry_SYSCALL_64_after_hwframe+0x77/0x7f  The root cause is below race condition, it may cause use-after-free issue in sbi-\u0026gt;gc_th pointer.  - remount  - f2fs_remount   - f2fs_stop_gc_thread    - kfree(gc_th)     - f2fs_ioc_shutdown      - f2fs_do_shutdown       - f2fs_stop_gc_thread        - kthread_stop(gc_th-\u0026gt;f2fs_gc_task)    : sbi-\u0026gt;gc_thread = NULL;  We will call f2fs_do_shutdown() in two paths: - for f2fs_ioc_shutdown() path, we should grab sb-\u0026gt;s_umount semaphore for fixing. - for f2fs_shutdown() path, it\u0026apos;s safe since caller has already grabbed sb-\u0026gt;s_umount semaphore.(CVE-2024-47691)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  IB/core: Fix ib_cache_setup_one error flow cleanup  When ib_cache_update return an error, we exit ib_cache_setup_one instantly with no proper cleanup, even though before this we had already successfully done gid_table_setup_one, that results in the kernel WARN below.  Do proper cleanup using gid_table_cleanup_one before returning the err in order to fix the issue.  WARNING: CPU: 4 PID: 922 at drivers/infiniband/core/cache.c:806 gid_table_release_one+0x181/0x1a0 Modules linked in: CPU: 4 UID: 0 PID: 922 Comm: c_repro Not tainted 6.11.0-rc1+ #3 Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS rel-1.13.0-0-gf21b5a4aeb02-prebuilt.qemu.org 04/01/2014 RIP: 0010:gid_table_release_one+0x181/0x1a0 Code: 44 8b 38 75 0c e8 2f cb 34 ff 4d 8b b5 28 05 00 00 e8 23 cb 34 ff 44 89 f9 89 da 4c 89 f6 48 c7 c7 d0 58 14 83 e8 4f de 21 ff \u0026lt;0f\u0026gt; 0b 4c 8b 75 30 e9 54 ff ff ff 48 8    3 c4 10 5b 5d 41 5c 41 5d 41 RSP: 0018:ffffc90002b835b0 EFLAGS: 00010286 RAX: 0000000000000000 RBX: 0000000000000000 RCX: ffffffff811c8527 RDX: 0000000000000000 RSI: ffffffff811c8534 RDI: 0000000000000001 RBP: ffff8881011b3d00 R08: ffff88810b3abe00 R09: 205d303839303631 R10: 666572207972746e R11: 72746e6520444947 R12: 0000000000000001 R13: ffff888106390000 R14: ffff8881011f2110 R15: 0000000000000001 FS:  00007fecc3b70800(0000) GS:ffff88813bd00000(0000) knlGS:0000000000000000 CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 0000000020000340 CR3: 000000010435a001 CR4: 00000000003706b0 DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400 Call Trace:  \u0026lt;TASK\u0026gt;  ? show_regs+0x94/0xa0  ? __warn+0x9e/0x1c0  ? gid_table_release_one+0x181/0x1a0  ? report_bug+0x1f9/0x340  ? gid_table_release_one+0x181/0x1a0  ? handle_bug+0xa2/0x110  ? exc_invalid_op+0x31/0xa0  ? asm_exc_invalid_op+0x16/0x20  ? __warn_printk+0xc7/0x180  ? __warn_printk+0xd4/0x180  ? gid_table_release_one+0x181/0x1a0  ib_device_release+0x71/0xe0  ? __pfx_ib_device_release+0x10/0x10  device_release+0x44/0xd0  kobject_put+0x135/0x3d0  put_device+0x20/0x30  rxe_net_add+0x7d/0xa0  rxe_newlink+0xd7/0x190  nldev_newlink+0x1b0/0x2a0  ? __pfx_nldev_newlink+0x10/0x10  rdma_nl_rcv_msg+0x1ad/0x2e0  rdma_nl_rcv_skb.constprop.0+0x176/0x210  netlink_unicast+0x2de/0x400  netlink_sendmsg+0x306/0x660  __sock_sendmsg+0x110/0x120  ____sys_sendmsg+0x30e/0x390  ___sys_sendmsg+0x9b/0xf0  ? kstrtouint+0x6e/0xa0  ? kstrtouint_from_user+0x7c/0xb0  ? get_pid_task+0xb0/0xd0  ? proc_fail_nth_write+0x5b/0x140  ? __fget_light+0x9a/0x200  ? preempt_count_add+0x47/0xa0  __sys_sendmsg+0x61/0xd0  do_syscall_64+0x50/0x110  entry_SYSCALL_64_after_hwframe+0x76/0x7e(CVE-2024-47693)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  RDMA/iwcm: Fix WARNING:at_kernel/workqueue.c:#check_flush_dependency  In the commit aee2424246f9 (\u0026quot;RDMA/iwcm: Fix a use-after-free related to destroying CM IDs\u0026quot;), the function flush_workqueue is invoked to flush the work queue iwcm_wq.  But at that time, the work queue iwcm_wq was created via the function alloc_ordered_workqueue without the flag WQ_MEM_RECLAIM.  Because the current process is trying to flush the whole iwcm_wq, if iwcm_wq doesn\u0026apos;t have the flag WQ_MEM_RECLAIM, verify that the current process is not reclaiming memory or running on a workqueue which doesn\u0026apos;t have the flag WQ_MEM_RECLAIM as that can break forward-progress guarantee leading to a deadlock.  The call trace is as below:  [  125.350876][ T1430] Call Trace: [  125.356281][ T1430]  \u0026lt;TASK\u0026gt; [ 125.361285][ T1430] ? __warn (kernel/panic.c:693) [ 125.367640][ T1430] ? check_flush_dependency (kernel/workqueue.c:3706 (discriminator 9)) [ 125.375689][ T1430] ? report_bug (lib/bug.c:180 lib/bug.c:219) [ 125.382505][ T1430] ? handle_bug (arch/x86/kernel/traps.c:239) [ 125.388987][ T1430] ? exc_invalid_op (arch/x86/kernel/traps.c:260 (discriminator 1)) [ 125.395831][ T1430] ? asm_exc_invalid_op (arch/x86/include/asm/idtentry.h:621) [ 125.403125][ T1430] ? check_flush_dependency (kernel/workqueue.c:3706 (discriminator 9)) [ 125.410984][ T1430] ? check_flush_dependency (kernel/workqueue.c:3706 (discriminator 9)) [ 125.418764][ T1430] __flush_workqueue (kernel/workqueue.c:3970) [ 125.426021][ T1430] ? __pfx___might_resched (kernel/sched/core.c:10151) [ 125.433431][ T1430] ? destroy_cm_id (drivers/infiniband/core/iwcm.c:375) iw_cm [ 125.441209][ T1430] ? __pfx___flush_workqueue (kernel/workqueue.c:3910) [ 125.473900][ T1430] ? _raw_spin_lock_irqsave (arch/x86/include/asm/atomic.h:107 include/linux/atomic/atomic-arch-fallback.h:2170 include/linux/atomic/atomic-instrumented.h:1302 include/asm-generic/qspinlock.h:111 include/linux/spinlock.h:187 include/linux/spinlock_api_smp.h:111 kernel/locking/spinlock.c:162) [ 125.473909][ T1430] ? __pfx__raw_spin_lock_irqsave (kernel/locking/spinlock.c:161) [ 125.482537][ T1430] _destroy_id (drivers/infiniband/core/cma.c:2044) rdma_cm [ 125.495072][ T1430] nvme_rdma_free_queue (drivers/nvme/host/rdma.c:656 drivers/nvme/host/rdma.c:650) nvme_rdma [ 125.505827][ T1430] nvme_rdma_reset_ctrl_work (drivers/nvme/host/rdma.c:2180) nvme_rdma [ 125.505831][ T1430] process_one_work (kernel/workqueue.c:3231) [ 125.515122][ T1430] worker_thread (kernel/workqueue.c:3306 kernel/workqueue.c:3393) [ 125.515127][ T1430] ? __pfx_worker_thread (kernel/workqueue.c:3339) [ 125.531837][ T1430] kthread (kernel/kthread.c:389) [ 125.539864][ T1430] ? __pfx_kthread (kernel/kthread.c:342) [ 125.550628][ T1430] ret_from_fork (arch/x86/kernel/process.c:147) [ 125.558840][ T1430] ? __pfx_kthread (kernel/kthread.c:342) [ 125.558844][ T1430] ret_from_fork_asm (arch/x86/entry/entry_64.S:257) [  125.566487][ T1430]  \u0026lt;/TASK\u0026gt; [  125.566488][ T1430] ---[ end trace 0000000000000000 ]---(CVE-2024-47696)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  nilfs2: fix potential null-ptr-deref in nilfs_btree_insert()  Patch series \u0026quot;nilfs2: fix potential issues with empty b-tree nodes\u0026quot;.  This series addresses three potential issues with empty b-tree nodes that can occur with corrupted filesystem images, including one recently discovered by syzbot.   This patch (of 3):  If a b-tree is broken on the device, and the b-tree height is greater than 2 (the level of the root node is greater than 1) even if the number of child nodes of the b-tree root is 0, a NULL pointer dereference occurs in nilfs_btree_prepare_insert(), which is called from nilfs_btree_insert().  This is because, when the number of child nodes of the b-tree root is 0, nilfs_btree_do_lookup() does not set the block buffer head in any of path[x].bp_bh, leaving it as the initial value of NULL, but if the level of the b-tree root node is greater than 1, nilfs_btree_get_nonroot_node(), which accesses the buffer memory of path[x].bp_bh, is called.  Fix this issue by adding a check to nilfs_btree_root_broken(), which performs sanity checks when reading the root node from the device, to detect this inconsistency.  Thanks to Lizhi Xu for trying to solve the bug and clarifying the cause early on.(CVE-2024-47699)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  ext4: avoid OOB when system.data xattr changes underneath the filesystem  When looking up for an entry in an inlined directory, if e_value_offs is changed underneath the filesystem by some change in the block device, it will lead to an out-of-bounds access that KASAN detects as an UAF.  EXT4-fs (loop0): mounted filesystem 00000000-0000-0000-0000-000000000000 r/w without journal. Quota mode: none. loop0: detected capacity change from 2048 to 2047 ================================================================== BUG: KASAN: use-after-free in ext4_search_dir+0xf2/0x1c0 fs/ext4/namei.c:1500 Read of size 1 at addr ffff88803e91130f by task syz-executor269/5103  CPU: 0 UID: 0 PID: 5103 Comm: syz-executor269 Not tainted 6.11.0-rc4-syzkaller #0 Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.16.3-debian-1.16.3-2~bpo12+1 04/01/2014 Call Trace:  \u0026lt;TASK\u0026gt;  __dump_stack lib/dump_stack.c:93 [inline]  dump_stack_lvl+0x241/0x360 lib/dump_stack.c:119  print_address_description mm/kasan/report.c:377 [inline]  print_report+0x169/0x550 mm/kasan/report.c:488  kasan_report+0x143/0x180 mm/kasan/report.c:601  ext4_search_dir+0xf2/0x1c0 fs/ext4/namei.c:1500  ext4_find_inline_entry+0x4be/0x5e0 fs/ext4/inline.c:1697  __ext4_find_entry+0x2b4/0x1b30 fs/ext4/namei.c:1573  ext4_lookup_entry fs/ext4/namei.c:1727 [inline]  ext4_lookup+0x15f/0x750 fs/ext4/namei.c:1795  lookup_one_qstr_excl+0x11f/0x260 fs/namei.c:1633  filename_create+0x297/0x540 fs/namei.c:3980  do_symlinkat+0xf9/0x3a0 fs/namei.c:4587  __do_sys_symlinkat fs/namei.c:4610 [inline]  __se_sys_symlinkat fs/namei.c:4607 [inline]  __x64_sys_symlinkat+0x95/0xb0 fs/namei.c:4607  do_syscall_x64 arch/x86/entry/common.c:52 [inline]  do_syscall_64+0xf3/0x230 arch/x86/entry/common.c:83  entry_SYSCALL_64_after_hwframe+0x77/0x7f RIP: 0033:0x7f3e73ced469 Code: 28 00 00 00 75 05 48 83 c4 28 c3 e8 21 18 00 00 90 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 \u0026lt;48\u0026gt; 3d 01 f0 ff ff 73 01 c3 48 c7 c1 b8 ff ff ff f7 d8 64 89 01 48 RSP: 002b:00007fff4d40c258 EFLAGS: 00000246 ORIG_RAX: 000000000000010a RAX: ffffffffffffffda RBX: 0032656c69662f2e RCX: 00007f3e73ced469 RDX: 0000000020000200 RSI: 00000000ffffff9c RDI: 00000000200001c0 RBP: 0000000000000000 R08: 00007fff4d40c290 R09: 00007fff4d40c290 R10: 0023706f6f6c2f76 R11: 0000000000000246 R12: 00007fff4d40c27c R13: 0000000000000003 R14: 431bde82d7b634db R15: 00007fff4d40c2b0  \u0026lt;/TASK\u0026gt;  Calling ext4_xattr_ibody_find right after reading the inode with ext4_get_inode_loc will lead to a check of the validity of the xattrs, avoiding this problem.(CVE-2024-47701)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  bpf, lsm: Add check for BPF LSM return value  A bpf prog returning a positive number attached to file_alloc_security hook makes kernel panic.  This happens because file system can not filter out the positive number returned by the LSM prog using IS_ERR, and misinterprets this positive number as a file pointer.  Given that hook file_alloc_security never returned positive number before the introduction of BPF LSM, and other BPF LSM hooks may encounter similar issues, this patch adds LSM return value check in verifier, to ensure no unexpected value is returned.(CVE-2024-47703)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  block: fix potential invalid pointer dereference in blk_add_partition  The blk_add_partition() function initially used a single if-condition (IS_ERR(part)) to check for errors when adding a partition. This was modified to handle the specific case of -ENXIO separately, allowing the function to proceed without logging the error in this case. However, this change unintentionally left a path where md_autodetect_dev() could be called without confirming that part is a valid pointer.  This commit separates the error handling logic by splitting the initial if-condition, improving code readability and handling specific error scenarios explicitly. The function now distinguishes the general error case from -ENXIO without altering the existing behavior of md_autodetect_dev() calls.(CVE-2024-47705)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  jfs: fix out-of-bounds in dbNextAG() and diAlloc()  In dbNextAG() , there is no check for the case where bmp-\u0026gt;db_numag is greater or same than MAXAG due to a polluted image, which causes an out-of-bounds. Therefore, a bounds check should be added in dbMount().  And in dbNextAG(), a check for the case where agpref is greater than bmp-\u0026gt;db_numag should be added, so an out-of-bounds exception should be prevented.  Additionally, a check for the case where agno is greater or same than MAXAG should be added in diAlloc() to prevent out-of-bounds.(CVE-2024-47723)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  f2fs: fix to wait dio completion  It should wait all existing dio write IOs before block removal, otherwise, previous direct write IO may overwrite data in the block which may be reused by other inode.(CVE-2024-47726)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  padata: use integer wrap around to prevent deadlock on seq_nr overflow  When submitting more than 2^32 padata objects to padata_do_serial, the current sorting implementation incorrectly sorts padata objects with overflowed seq_nr, causing them to be placed before existing objects in the reorder list. This leads to a deadlock in the serialization process as padata_find_next cannot match padata-\u0026gt;seq_nr and pd-\u0026gt;processed because the padata instance with overflowed seq_nr will be selected next.  To fix this, we use an unsigned integer wrap around to correctly sort padata objects in scenarios with integer overflow.(CVE-2024-47739)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  firmware_loader: Block path traversal  Most firmware names are hardcoded strings, or are constructed from fairly constrained format strings where the dynamic parts are just some hex numbers or such.  However, there are a couple codepaths in the kernel where firmware file names contain string components that are passed through from a device or semi-privileged userspace; the ones I could find (not counting interfaces that require root privileges) are:   - lpfc_sli4_request_firmware_update() seems to construct the firmware    filename from \u0026quot;ModelName\u0026quot;, a string that was previously parsed out of    some descriptor (\u0026quot;Vital Product Data\u0026quot;) in lpfc_fill_vpd()  - nfp_net_fw_find() seems to construct a firmware filename from a model    name coming from nfp_hwinfo_lookup(pf-\u0026gt;hwinfo, \u0026quot;nffw.partno\u0026quot;), which I    think parses some descriptor that was read from the device.    (But this case likely isn\u0026apos;t exploitable because the format string looks    like \u0026quot;netronome/nic_%s\u0026quot;, and there shouldn\u0026apos;t be any *folders* starting    with \u0026quot;netronome/nic_\u0026quot;. The previous case was different because there,    the \u0026quot;%s\u0026quot; is *at the start* of the format string.)  - module_flash_fw_schedule() is reachable from the    ETHTOOL_MSG_MODULE_FW_FLASH_ACT netlink command, which is marked as    GENL_UNS_ADMIN_PERM (meaning CAP_NET_ADMIN inside a user namespace is    enough to pass the privilege check), and takes a userspace-provided    firmware name.    (But I think to reach this case, you need to have CAP_NET_ADMIN over a    network namespace that a special kind of ethernet device is mapped into,    so I think this is not a viable attack path in practice.)  Fix it by rejecting any firmware names containing \u0026quot;..\u0026quot; path components.  For what it\u0026apos;s worth, I went looking and haven\u0026apos;t found any USB device drivers that use the firmware loader dangerously.(CVE-2024-47742)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  vhost_vdpa: assign irq bypass producer token correctly  We used to call irq_bypass_unregister_producer() in vhost_vdpa_setup_vq_irq() which is problematic as we don\u0026apos;t know if the token pointer is still valid or not.  Actually, we use the eventfd_ctx as the token so the life cycle of the token should be bound to the VHOST_SET_VRING_CALL instead of vhost_vdpa_setup_vq_irq() which could be called by set_status().  Fixing this by setting up irq bypass producer\u0026apos;s token when handling VHOST_SET_VRING_CALL and un-registering the producer before calling vhost_vring_ioctl() to prevent a possible use after free as eventfd could have been released in vhost_vring_ioctl(). And such registering and unregistering will only be done if DRIVER_OK is set.(CVE-2024-47748)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  PCI: keystone: Fix if-statement expression in ks_pcie_quirk()  This code accidentally uses \u0026amp;\u0026amp; where || was intended.  It potentially results in a NULL dereference.  Thus, fix the if-statement expression to use the correct condition.  [kwilczynski: commit log](CVE-2024-47756)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  nbd: fix race between timeout and normal completion  If request timetout is handled by nbd_requeue_cmd(), normal completion has to be stopped for avoiding to complete this requeued request, other use-after-free can be triggered.  Fix the race by clearing NBD_CMD_INFLIGHT in nbd_requeue_cmd(), meantime make sure that cmd-\u0026gt;lock is grabbed for clearing the flag and the requeue.(CVE-2024-49855)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  efistub/tpm: Use ACPI reclaim memory for event log to avoid corruption  The TPM event log table is a Linux specific construct, where the data produced by the GetEventLog() boot service is cached in memory, and passed on to the OS using an EFI configuration table.  The use of EFI_LOADER_DATA here results in the region being left unreserved in the E820 memory map constructed by the EFI stub, and this is the memory description that is passed on to the incoming kernel by kexec, which is therefore unaware that the region should be reserved.  Even though the utility of the TPM2 event log after a kexec is questionable, any corruption might send the parsing code off into the weeds and crash the kernel. So let\u0026apos;s use EFI_ACPI_RECLAIM_MEMORY instead, which is always treated as reserved by the E820 conversion logic.(CVE-2024-49858)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  f2fs: fix to check atomic_file in f2fs ioctl interfaces  Some f2fs ioctl interfaces like f2fs_ioc_set_pin_file(), f2fs_move_file_range(), and f2fs_defragment_range() missed to check atomic_write status, which may cause potential race issue, fix it.(CVE-2024-49859)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  ACPI: sysfs: validate return type of _STR method  Only buffer objects are valid return values of _STR.  If something else is returned description_show() will access invalid memory.(CVE-2024-49860)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  powercap: intel_rapl: Fix off by one in get_rpi()  The rp-\u0026gt;priv-\u0026gt;rpi array is either rpi_msr or rpi_tpmi which have NR_RAPL_PRIMITIVES number of elements.  Thus the \u0026gt; needs to be \u0026gt;= to prevent an off by one access.(CVE-2024-49862)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  ocfs2: fix possible null-ptr-deref in ocfs2_set_buffer_uptodate  When doing cleanup, if flags without OCFS2_BH_READAHEAD, it may trigger NULL pointer dereference in the following ocfs2_set_buffer_uptodate() if bh is NULL.(CVE-2024-49877)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  drm: omapdrm: Add missing check for alloc_ordered_workqueue  As it may return NULL pointer and cause NULL pointer dereference. Add check for the return value of alloc_ordered_workqueue.(CVE-2024-49879)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  ext4: update orig_path in ext4_find_extent()  In ext4_find_extent(), if the path is not big enough, we free it and set *orig_path to NULL. But after reallocating and successfully initializing the path, we don\u0026apos;t update *orig_path, in which case the caller gets a valid path but a NULL ppath, and this may cause a NULL pointer dereference or a path memory leak. For example:  ext4_split_extent   path = *ppath = 2000   ext4_find_extent     if (depth \u0026gt; path[0].p_maxdepth)       kfree(path = 2000);       *orig_path = path = NULL;       path = kcalloc() = 3000   ext4_split_extent_at(*ppath = NULL)     path = *ppath;     ex = path[depth].p_ext;     // NULL pointer dereference!  ================================================================== BUG: kernel NULL pointer dereference, address: 0000000000000010 CPU: 6 UID: 0 PID: 576 Comm: fsstress Not tainted 6.11.0-rc2-dirty #847 RIP: 0010:ext4_split_extent_at+0x6d/0x560 Call Trace:  \u0026lt;TASK\u0026gt;  ext4_split_extent.isra.0+0xcb/0x1b0  ext4_ext_convert_to_initialized+0x168/0x6c0  ext4_ext_handle_unwritten_extents+0x325/0x4d0  ext4_ext_map_blocks+0x520/0xdb0  ext4_map_blocks+0x2b0/0x690  ext4_iomap_begin+0x20e/0x2c0 [...] ==================================================================  Therefore, *orig_path is updated when the extent lookup succeeds, so that the caller can safely use path or *ppath.(CVE-2024-49881)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  ext4: fix double brelse() the buffer of the extents path  In ext4_ext_try_to_merge_up(), set path[1].p_bh to NULL after it has been released, otherwise it may be released twice. An example of what triggers this is as follows:    split2    map    split1 |--------|-------|--------|  ext4_ext_map_blocks  ext4_ext_handle_unwritten_extents   ext4_split_convert_extents    // path-\u0026gt;p_depth == 0    ext4_split_extent      // 1. do split1      ext4_split_extent_at        |ext4_ext_insert_extent        |  ext4_ext_create_new_leaf        |    ext4_ext_grow_indepth        |      le16_add_cpu(\u0026amp;neh-\u0026gt;eh_depth, 1)        |    ext4_find_extent        |      // return -ENOMEM        |// get error and try zeroout        |path = ext4_find_extent        |  path-\u0026gt;p_depth = 1        |ext4_ext_try_to_merge        |  ext4_ext_try_to_merge_up        |    path-\u0026gt;p_depth = 0        |    brelse(path[1].p_bh)  ---\u0026gt; not set to NULL here        |// zeroout success      // 2. update path      ext4_find_extent      // 3. do split2      ext4_split_extent_at        ext4_ext_insert_extent          ext4_ext_create_new_leaf            ext4_ext_grow_indepth              le16_add_cpu(\u0026amp;neh-\u0026gt;eh_depth, 1)            ext4_find_extent              path[0].p_bh = NULL;              path-\u0026gt;p_depth = 1              read_extent_tree_block  ---\u0026gt; return err              // path[1].p_bh is still the old value              ext4_free_ext_path                ext4_ext_drop_refs                  // path-\u0026gt;p_depth == 1                  brelse(path[1].p_bh)  ---\u0026gt; brelse a buffer twice  Finally got the following WARRNING when removing the buffer from lru:  ============================================ VFS: brelse: Trying to free free buffer WARNING: CPU: 2 PID: 72 at fs/buffer.c:1241 __brelse+0x58/0x90 CPU: 2 PID: 72 Comm: kworker/u19:1 Not tainted 6.9.0-dirty #716 RIP: 0010:__brelse+0x58/0x90 Call Trace:  \u0026lt;TASK\u0026gt;  __find_get_block+0x6e7/0x810  bdev_getblk+0x2b/0x480  __ext4_get_inode_loc+0x48a/0x1240  ext4_get_inode_loc+0xb2/0x150  ext4_reserve_inode_write+0xb7/0x230  __ext4_mark_inode_dirty+0x144/0x6a0  ext4_ext_insert_extent+0x9c8/0x3230  ext4_ext_map_blocks+0xf45/0x2dc0  ext4_map_blocks+0x724/0x1700  ext4_do_writepages+0x12d6/0x2a70 [...] ============================================(CVE-2024-49882)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  ext4: aovid use-after-free in ext4_ext_insert_extent()  As Ojaswin mentioned in Link, in ext4_ext_insert_extent(), if the path is reallocated in ext4_ext_create_new_leaf(), we\u0026apos;ll use the stale path and cause UAF. Below is a sample trace with dummy values:  ext4_ext_insert_extent   path = *ppath = 2000   ext4_ext_create_new_leaf(ppath)     ext4_find_extent(ppath)       path = *ppath = 2000       if (depth \u0026gt; path[0].p_maxdepth)             kfree(path = 2000);             *ppath = path = NULL;       path = kcalloc() = 3000       *ppath = 3000;       return path;   /* here path is still 2000, UAF! */   eh = path[depth].p_hdr  ================================================================== BUG: KASAN: slab-use-after-free in ext4_ext_insert_extent+0x26d4/0x3330 Read of size 8 at addr ffff8881027bf7d0 by task kworker/u36:1/179 CPU: 3 UID: 0 PID: 179 Comm: kworker/u6:1 Not tainted 6.11.0-rc2-dirty #866 Call Trace:  \u0026lt;TASK\u0026gt;  ext4_ext_insert_extent+0x26d4/0x3330  ext4_ext_map_blocks+0xe22/0x2d40  ext4_map_blocks+0x71e/0x1700  ext4_do_writepages+0x1290/0x2800 [...]  Allocated by task 179:  ext4_find_extent+0x81c/0x1f70  ext4_ext_map_blocks+0x146/0x2d40  ext4_map_blocks+0x71e/0x1700  ext4_do_writepages+0x1290/0x2800  ext4_writepages+0x26d/0x4e0  do_writepages+0x175/0x700 [...]  Freed by task 179:  kfree+0xcb/0x240  ext4_find_extent+0x7c0/0x1f70  ext4_ext_insert_extent+0xa26/0x3330  ext4_ext_map_blocks+0xe22/0x2d40  ext4_map_blocks+0x71e/0x1700  ext4_do_writepages+0x1290/0x2800  ext4_writepages+0x26d/0x4e0  do_writepages+0x175/0x700 [...] ==================================================================  So use *ppath to update the path to avoid the above problem.(CVE-2024-49883)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  ext4: fix slab-use-after-free in ext4_split_extent_at()  We hit the following use-after-free:  ================================================================== BUG: KASAN: slab-use-after-free in ext4_split_extent_at+0xba8/0xcc0 Read of size 2 at addr ffff88810548ed08 by task kworker/u20:0/40 CPU: 0 PID: 40 Comm: kworker/u20:0 Not tainted 6.9.0-dirty #724 Call Trace:  \u0026lt;TASK\u0026gt;  kasan_report+0x93/0xc0  ext4_split_extent_at+0xba8/0xcc0  ext4_split_extent.isra.0+0x18f/0x500  ext4_split_convert_extents+0x275/0x750  ext4_ext_handle_unwritten_extents+0x73e/0x1580  ext4_ext_map_blocks+0xe20/0x2dc0  ext4_map_blocks+0x724/0x1700  ext4_do_writepages+0x12d6/0x2a70 [...]  Allocated by task 40:  __kmalloc_noprof+0x1ac/0x480  ext4_find_extent+0xf3b/0x1e70  ext4_ext_map_blocks+0x188/0x2dc0  ext4_map_blocks+0x724/0x1700  ext4_do_writepages+0x12d6/0x2a70 [...]  Freed by task 40:  kfree+0xf1/0x2b0  ext4_find_extent+0xa71/0x1e70  ext4_ext_insert_extent+0xa22/0x3260  ext4_split_extent_at+0x3ef/0xcc0  ext4_split_extent.isra.0+0x18f/0x500  ext4_split_convert_extents+0x275/0x750  ext4_ext_handle_unwritten_extents+0x73e/0x1580  ext4_ext_map_blocks+0xe20/0x2dc0  ext4_map_blocks+0x724/0x1700  ext4_do_writepages+0x12d6/0x2a70 [...] ==================================================================  The flow of issue triggering is as follows:  ext4_split_extent_at   path = *ppath   ext4_ext_insert_extent(ppath)     ext4_ext_create_new_leaf(ppath)       ext4_find_extent(orig_path)         path = *orig_path         read_extent_tree_block           // return -ENOMEM or -EIO         ext4_free_ext_path(path)           kfree(path)         *orig_path = NULL   a. If err is -ENOMEM:   ext4_ext_dirty(path + path-\u0026gt;p_depth)   // path use-after-free !!!   b. If err is -EIO and we have EXT_DEBUG defined:   ext4_ext_show_leaf(path)     eh = path[depth].p_hdr     // path also use-after-free !!!  So when trying to zeroout or fix the extent length, call ext4_find_extent() to update the path.  In addition we use *ppath directly as an ext4_ext_show_leaf() input to avoid possible use-after-free when EXT_DEBUG is defined, and to avoid unnecessary path updates.(CVE-2024-49884)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  platform/x86: ISST: Fix the KASAN report slab-out-of-bounds bug  Attaching SST PCI device to VM causes \u0026quot;BUG: KASAN: slab-out-of-bounds\u0026quot;. kasan report: [   19.411889] ================================================================== [   19.413702] BUG: KASAN: slab-out-of-bounds in _isst_if_get_pci_dev+0x3d5/0x400 [isst_if_common] [   19.415634] Read of size 8 at addr ffff888829e65200 by task cpuhp/16/113 [   19.417368] [   19.418627] CPU: 16 PID: 113 Comm: cpuhp/16 Tainted: G            E      6.9.0 #10 [   19.420435] Hardware name: VMware, Inc. VMware20,1/440BX Desktop Reference Platform, BIOS VMW201.00V.20192059.B64.2207280713 07/28/2022 [   19.422687] Call Trace: [   19.424091]  \u0026lt;TASK\u0026gt; [   19.425448]  dump_stack_lvl+0x5d/0x80 [   19.426963]  ? _isst_if_get_pci_dev+0x3d5/0x400 [isst_if_common] [   19.428694]  print_report+0x19d/0x52e [   19.430206]  ? __pfx__raw_spin_lock_irqsave+0x10/0x10 [   19.431837]  ? _isst_if_get_pci_dev+0x3d5/0x400 [isst_if_common] [   19.433539]  kasan_report+0xf0/0x170 [   19.435019]  ? _isst_if_get_pci_dev+0x3d5/0x400 [isst_if_common] [   19.436709]  _isst_if_get_pci_dev+0x3d5/0x400 [isst_if_common] [   19.438379]  ? __pfx_sched_clock_cpu+0x10/0x10 [   19.439910]  isst_if_cpu_online+0x406/0x58f [isst_if_common] [   19.441573]  ? __pfx_isst_if_cpu_online+0x10/0x10 [isst_if_common] [   19.443263]  ? ttwu_queue_wakelist+0x2c1/0x360 [   19.444797]  cpuhp_invoke_callback+0x221/0xec0 [   19.446337]  cpuhp_thread_fun+0x21b/0x610 [   19.447814]  ? __pfx_cpuhp_thread_fun+0x10/0x10 [   19.449354]  smpboot_thread_fn+0x2e7/0x6e0 [   19.450859]  ? __pfx_smpboot_thread_fn+0x10/0x10 [   19.452405]  kthread+0x29c/0x350 [   19.453817]  ? __pfx_kthread+0x10/0x10 [   19.455253]  ret_from_fork+0x31/0x70 [   19.456685]  ? __pfx_kthread+0x10/0x10 [   19.458114]  ret_from_fork_asm+0x1a/0x30 [   19.459573]  \u0026lt;/TASK\u0026gt; [   19.460853] [   19.462055] Allocated by task 1198: [   19.463410]  kasan_save_stack+0x30/0x50 [   19.464788]  kasan_save_track+0x14/0x30 [   19.466139]  __kasan_kmalloc+0xaa/0xb0 [   19.467465]  __kmalloc+0x1cd/0x470 [   19.468748]  isst_if_cdev_register+0x1da/0x350 [isst_if_common] [   19.470233]  isst_if_mbox_init+0x108/0xff0 [isst_if_mbox_msr] [   19.471670]  do_one_initcall+0xa4/0x380 [   19.472903]  do_init_module+0x238/0x760 [   19.474105]  load_module+0x5239/0x6f00 [   19.475285]  init_module_from_file+0xd1/0x130 [   19.476506]  idempotent_init_module+0x23b/0x650 [   19.477725]  __x64_sys_finit_module+0xbe/0x130 [   19.476506]  idempotent_init_module+0x23b/0x650 [   19.477725]  __x64_sys_finit_module+0xbe/0x130 [   19.478920]  do_syscall_64+0x82/0x160 [   19.480036]  entry_SYSCALL_64_after_hwframe+0x76/0x7e [   19.481292] [   19.482205] The buggy address belongs to the object at ffff888829e65000  which belongs to the cache kmalloc-512 of size 512 [   19.484818] The buggy address is located 0 bytes to the right of  allocated 512-byte region [ffff888829e65000, ffff888829e65200) [   19.487447] [   19.488328] The buggy address belongs to the physical page: [   19.489569] page: refcount:1 mapcount:0 mapping:0000000000000000 index:0xffff888829e60c00 pfn:0x829e60 [   19.491140] head: order:3 entire_mapcount:0 nr_pages_mapped:0 pincount:0 [   19.492466] anon flags: 0x57ffffc0000840(slab|head|node=1|zone=2|lastcpupid=0x1fffff) [   19.493914] page_type: 0xffffffff() [   19.494988] raw: 0057ffffc0000840 ffff88810004cc80 0000000000000000 0000000000000001 [   19.496451] raw: ffff888829e60c00 0000000080200018 00000001ffffffff 0000000000000000 [   19.497906] head: 0057ffffc0000840 ffff88810004cc80 0000000000000000 0000000000000001 [   19.499379] head: ffff888829e60c00 0000000080200018 00000001ffffffff 0000000000000000 [   19.500844] head: 0057ffffc0000003 ffffea0020a79801 ffffea0020a79848 00000000ffffffff [   19.502316] head: 0000000800000000 0000000000000000 00000000ffffffff 0000000000000000 [   19.503784] page dumped because: k ---truncated---(CVE-2024-49886)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  ext4: avoid use-after-free in ext4_ext_show_leaf()  In ext4_find_extent(), path may be freed by error or be reallocated, so using a previously saved *ppath may have been freed and thus may trigger use-after-free, as follows:  ext4_split_extent   path = *ppath;   ext4_split_extent_at(ppath)   path = ext4_find_extent(ppath)   ext4_split_extent_at(ppath)     // ext4_find_extent fails to free path     // but zeroout succeeds   ext4_ext_show_leaf(inode, path)     eh = path[depth].p_hdr     // path use-after-free !!!  Similar to ext4_split_extent_at(), we use *ppath directly as an input to ext4_ext_show_leaf(). Fix a spelling error by the way.  Same problem in ext4_ext_handle_unwritten_extents(). Since \u0026apos;path\u0026apos; is only used in ext4_ext_show_leaf(), remove \u0026apos;path\u0026apos; and use *ppath directly.  This issue is triggered only when EXT_DEBUG is defined and therefore does not affect functionality.(CVE-2024-49889)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  drm/amd/display: Check stream before comparing them  [WHAT \u0026amp; HOW] amdgpu_dm can pass a null stream to dc_is_stream_unchanged. It is necessary to check for null before dereferencing them.  This fixes 1 FORWARD_NULL issue reported by Coverity.(CVE-2024-49896)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  drm/amd/display: Add null check for top_pipe_to_program in commit_planes_for_stream  This commit addresses a null pointer dereference issue in the `commit_planes_for_stream` function at line 4140. The issue could occur when `top_pipe_to_program` is null.  The fix adds a check to ensure `top_pipe_to_program` is not null before accessing its stream_res. This prevents a null pointer dereference.  Reported by smatch: drivers/gpu/drm/amd/amdgpu/../display/dc/core/dc.c:4140 commit_planes_for_stream() error: we previously assumed \u0026apos;top_pipe_to_program\u0026apos; could be null (see line 3906)(CVE-2024-49913)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  drm/amd/display: Add NULL check for clk_mgr and clk_mgr-\u0026gt;funcs in dcn30_init_hw  This commit addresses a potential null pointer dereference issue in the `dcn30_init_hw` function. The issue could occur when `dc-\u0026gt;clk_mgr` or `dc-\u0026gt;clk_mgr-\u0026gt;funcs` is null.  The fix adds a check to ensure `dc-\u0026gt;clk_mgr` and `dc-\u0026gt;clk_mgr-\u0026gt;funcs` is not null before accessing its functions. This prevents a potential null pointer dereference.  Reported by smatch: drivers/gpu/drm/amd/amdgpu/../display/dc/hwss/dcn30/dcn30_hwseq.c:789 dcn30_init_hw() error: we previously assumed \u0026apos;dc-\u0026gt;clk_mgr\u0026apos; could be null (see line 628)(CVE-2024-49917)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  drm/amd/display: Check null pointers before using them  [WHAT \u0026amp; HOW] These pointers are null checked previously in the same function, indicating they might be null as reported by Coverity. As a result, they need to be checked when used again.  This fixes 3 FORWARD_NULL issue reported by Coverity.(CVE-2024-49922)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  fbdev: pxafb: Fix possible use after free in pxafb_task()  In the pxafb_probe function, it calls the pxafb_init_fbinfo function, after which \u0026amp;fbi-\u0026gt;task is associated with pxafb_task. Moreover, within this pxafb_init_fbinfo function, the pxafb_blank function within the \u0026amp;pxafb_ops struct is capable of scheduling work.  If we remove the module which will call pxafb_remove to make cleanup, it will call unregister_framebuffer function which can call do_unregister_framebuffer to free fbi-\u0026gt;fb through put_fb_info(fb_info), while the work mentioned above will be used. The sequence of operations that may lead to a UAF bug is as follows:  CPU0                                                CPU1                                     | pxafb_task pxafb_remove                       | unregister_framebuffer(info)       | do_unregister_framebuffer(fb_info) | put_fb_info(fb_info)               | // free fbi-\u0026gt;fb                    | set_ctrlr_state(fbi, state)                                    | __pxafb_lcd_power(fbi, 0)                                    | fbi-\u0026gt;lcd_power(on, \u0026amp;fbi-\u0026gt;fb.var)                                    | //use fbi-\u0026gt;fb  Fix it by ensuring that the work is canceled before proceeding with the cleanup in pxafb_remove.  Note that only root user can remove the driver at runtime.(CVE-2024-49924)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  blk_iocost: fix more out of bound shifts  Recently running UBSAN caught few out of bound shifts in the ioc_forgive_debts() function:  UBSAN: shift-out-of-bounds in block/blk-iocost.c:2142:38 shift exponent 80 is too large for 64-bit type \u0026apos;u64\u0026apos; (aka \u0026apos;unsigned long long\u0026apos;) ... UBSAN: shift-out-of-bounds in block/blk-iocost.c:2144:30 shift exponent 80 is too large for 64-bit type \u0026apos;u64\u0026apos; (aka \u0026apos;unsigned long long\u0026apos;) ... Call Trace: \u0026lt;IRQ\u0026gt; dump_stack_lvl+0xca/0x130 __ubsan_handle_shift_out_of_bounds+0x22c/0x280 ? __lock_acquire+0x6441/0x7c10 ioc_timer_fn+0x6cec/0x7750 ? blk_iocost_init+0x720/0x720 ? call_timer_fn+0x5d/0x470 call_timer_fn+0xfa/0x470 ? blk_iocost_init+0x720/0x720 __run_timer_base+0x519/0x700 ...  Actual impact of this issue was not identified but I propose to fix the undefined behaviour. The proposed fix to prevent those out of bound shifts consist of precalculating exponent before using it the shift operations by taking min value from the actual exponent and maximum possible number of bits.(CVE-2024-49933)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  fs/inode: Prevent dump_mapping() accessing invalid dentry.d_name.name  It\u0026apos;s observed that a crash occurs during hot-remove a memory device, in which user is accessing the hugetlb. See calltrace as following:  ------------[ cut here ]------------ WARNING: CPU: 1 PID: 14045 at arch/x86/mm/fault.c:1278 do_user_addr_fault+0x2a0/0x790 Modules linked in: kmem device_dax cxl_mem cxl_pmem cxl_port cxl_pci dax_hmem dax_pmem nd_pmem cxl_acpi nd_btt cxl_core crc32c_intel nvme virtiofs fuse nvme_core nfit libnvdimm dm_multipath scsi_dh_rdac scsi_dh_emc s mirror dm_region_hash dm_log dm_mod CPU: 1 PID: 14045 Comm: daxctl Not tainted 6.10.0-rc2-lizhijian+ #492 Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS rel-1.16.3-0-ga6ed6b701f0a-prebuilt.qemu.org 04/01/2014 RIP: 0010:do_user_addr_fault+0x2a0/0x790 Code: 48 8b 00 a8 04 0f 84 b5 fe ff ff e9 1c ff ff ff 4c 89 e9 4c 89 e2 be 01 00 00 00 bf 02 00 00 00 e8 b5 ef 24 00 e9 42 fe ff ff \u0026lt;0f\u0026gt; 0b 48 83 c4 08 4c 89 ea 48 89 ee 4c 89 e7 5b 5d 41 5c 41 5d 41 RSP: 0000:ffffc90000a575f0 EFLAGS: 00010046 RAX: ffff88800c303600 RBX: 0000000000000000 RCX: 0000000000000000 RDX: 0000000000001000 RSI: ffffffff82504162 RDI: ffffffff824b2c36 RBP: 0000000000000000 R08: 0000000000000000 R09: 0000000000000000 R10: 0000000000000000 R11: 0000000000000000 R12: ffffc90000a57658 R13: 0000000000001000 R14: ffff88800bc2e040 R15: 0000000000000000 FS:  00007f51cb57d880(0000) GS:ffff88807fd00000(0000) knlGS:0000000000000000 CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 0000000000001000 CR3: 00000000072e2004 CR4: 00000000001706f0 DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400 Call Trace:  \u0026lt;TASK\u0026gt;  ? __warn+0x8d/0x190  ? do_user_addr_fault+0x2a0/0x790  ? report_bug+0x1c3/0x1d0  ? handle_bug+0x3c/0x70  ? exc_invalid_op+0x14/0x70  ? asm_exc_invalid_op+0x16/0x20  ? do_user_addr_fault+0x2a0/0x790  ? exc_page_fault+0x31/0x200  exc_page_fault+0x68/0x200 \u0026lt;...snip...\u0026gt; BUG: unable to handle page fault for address: 0000000000001000  #PF: supervisor read access in kernel mode  #PF: error_code(0x0000) - not-present page  PGD 800000000ad92067 P4D 800000000ad92067 PUD 7677067 PMD 0  Oops: Oops: 0000 [#1] PREEMPT SMP PTI  ---[ end trace 0000000000000000 ]---  BUG: unable to handle page fault for address: 0000000000001000  #PF: supervisor read access in kernel mode  #PF: error_code(0x0000) - not-present page  PGD 800000000ad92067 P4D 800000000ad92067 PUD 7677067 PMD 0  Oops: Oops: 0000 [#1] PREEMPT SMP PTI  CPU: 1 PID: 14045 Comm: daxctl Kdump: loaded Tainted: G        W          6.10.0-rc2-lizhijian+ #492  Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS rel-1.16.3-0-ga6ed6b701f0a-prebuilt.qemu.org 04/01/2014  RIP: 0010:dentry_name+0x1f4/0x440 \u0026lt;...snip...\u0026gt; ? dentry_name+0x2fa/0x440 vsnprintf+0x1f3/0x4f0 vprintk_store+0x23a/0x540 vprintk_emit+0x6d/0x330 _printk+0x58/0x80 dump_mapping+0x10b/0x1a0 ? __pfx_free_object_rcu+0x10/0x10 __dump_page+0x26b/0x3e0 ? vprintk_emit+0xe0/0x330 ? _printk+0x58/0x80 ? dump_page+0x17/0x50 dump_page+0x17/0x50 do_migrate_range+0x2f7/0x7f0 ? do_migrate_range+0x42/0x7f0 ? offline_pages+0x2f4/0x8c0 offline_pages+0x60a/0x8c0 memory_subsys_offline+0x9f/0x1c0 ? lockdep_hardirqs_on+0x77/0x100 ? _raw_spin_unlock_irqrestore+0x38/0x60 device_offline+0xe3/0x110 state_store+0x6e/0xc0 kernfs_fop_write_iter+0x143/0x200 vfs_write+0x39f/0x560 ksys_write+0x65/0xf0 do_syscall_64+0x62/0x130  Previously, some sanity check have been done in dump_mapping() before the print facility parsing \u0026apos;%pd\u0026apos; though, it\u0026apos;s still possible to run into an invalid dentry.d_name.name.  Since dump_mapping() only needs to dump the filename only, retrieve it by itself in a safer way to prevent an unnecessary crash.  Note that either retrieving the filename with \u0026apos;%pd\u0026apos; or strncpy_from_kernel_nofault(), the filename could be unreliable.(CVE-2024-49934)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  net/xen-netback: prevent UAF in xenvif_flush_hash()  During the list_for_each_entry_rcu iteration call of xenvif_flush_hash, kfree_rcu does not exist inside the rcu read critical section, so if kfree_rcu is called when the rcu grace period ends during the iteration, UAF occurs when accessing head-\u0026gt;next after the entry becomes free.  Therefore, to solve this, you need to change it to list_for_each_entry_safe.(CVE-2024-49936)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  l2tp: prevent possible tunnel refcount underflow  When a session is created, it sets a backpointer to its tunnel. When the session refcount drops to 0, l2tp_session_free drops the tunnel refcount if session-\u0026gt;tunnel is non-NULL. However, session-\u0026gt;tunnel is set in l2tp_session_create, before the tunnel refcount is incremented by l2tp_session_register, which leaves a small window where session-\u0026gt;tunnel is non-NULL when the tunnel refcount hasn\u0026apos;t been bumped.  Moving the assignment to l2tp_session_register is trivial but l2tp_session_create calls l2tp_session_set_header_len which uses session-\u0026gt;tunnel to get the tunnel\u0026apos;s encap. Add an encap arg to l2tp_session_set_header_len to avoid using session-\u0026gt;tunnel.  If l2tpv3 sessions have colliding IDs, it is possible for l2tp_v3_session_get to race with l2tp_session_register and fetch a session which doesn\u0026apos;t yet have session-\u0026gt;tunnel set. Add a check for this case.(CVE-2024-49940)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  Bluetooth: L2CAP: Fix uaf in l2cap_connect  [Syzbot reported] BUG: KASAN: slab-use-after-free in l2cap_connect.constprop.0+0x10d8/0x1270 net/bluetooth/l2cap_core.c:3949 Read of size 8 at addr ffff8880241e9800 by task kworker/u9:0/54  CPU: 0 UID: 0 PID: 54 Comm: kworker/u9:0 Not tainted 6.11.0-rc6-syzkaller-00268-g788220eee30d #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 08/06/2024 Workqueue: hci2 hci_rx_work Call Trace:  \u0026lt;TASK\u0026gt;  __dump_stack lib/dump_stack.c:93 [inline]  dump_stack_lvl+0x116/0x1f0 lib/dump_stack.c:119  print_address_description mm/kasan/report.c:377 [inline]  print_report+0xc3/0x620 mm/kasan/report.c:488  kasan_report+0xd9/0x110 mm/kasan/report.c:601  l2cap_connect.constprop.0+0x10d8/0x1270 net/bluetooth/l2cap_core.c:3949  l2cap_connect_req net/bluetooth/l2cap_core.c:4080 [inline]  l2cap_bredr_sig_cmd net/bluetooth/l2cap_core.c:4772 [inline]  l2cap_sig_channel net/bluetooth/l2cap_core.c:5543 [inline]  l2cap_recv_frame+0xf0b/0x8eb0 net/bluetooth/l2cap_core.c:6825  l2cap_recv_acldata+0x9b4/0xb70 net/bluetooth/l2cap_core.c:7514  hci_acldata_packet net/bluetooth/hci_core.c:3791 [inline]  hci_rx_work+0xaab/0x1610 net/bluetooth/hci_core.c:4028  process_one_work+0x9c5/0x1b40 kernel/workqueue.c:3231  process_scheduled_works kernel/workqueue.c:3312 [inline]  worker_thread+0x6c8/0xed0 kernel/workqueue.c:3389  kthread+0x2c1/0x3a0 kernel/kthread.c:389  ret_from_fork+0x45/0x80 arch/x86/kernel/process.c:147  ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:244 ...  Freed by task 5245:  kasan_save_stack+0x33/0x60 mm/kasan/common.c:47  kasan_save_track+0x14/0x30 mm/kasan/common.c:68  kasan_save_free_info+0x3b/0x60 mm/kasan/generic.c:579  poison_slab_object+0xf7/0x160 mm/kasan/common.c:240  __kasan_slab_free+0x32/0x50 mm/kasan/common.c:256  kasan_slab_free include/linux/kasan.h:184 [inline]  slab_free_hook mm/slub.c:2256 [inline]  slab_free mm/slub.c:4477 [inline]  kfree+0x12a/0x3b0 mm/slub.c:4598  l2cap_conn_free net/bluetooth/l2cap_core.c:1810 [inline]  kref_put include/linux/kref.h:65 [inline]  l2cap_conn_put net/bluetooth/l2cap_core.c:1822 [inline]  l2cap_conn_del+0x59d/0x730 net/bluetooth/l2cap_core.c:1802  l2cap_connect_cfm+0x9e6/0xf80 net/bluetooth/l2cap_core.c:7241  hci_connect_cfm include/net/bluetooth/hci_core.h:1960 [inline]  hci_conn_failed+0x1c3/0x370 net/bluetooth/hci_conn.c:1265  hci_abort_conn_sync+0x75a/0xb50 net/bluetooth/hci_sync.c:5583  abort_conn_sync+0x197/0x360 net/bluetooth/hci_conn.c:2917  hci_cmd_sync_work+0x1a4/0x410 net/bluetooth/hci_sync.c:328  process_one_work+0x9c5/0x1b40 kernel/workqueue.c:3231  process_scheduled_works kernel/workqueue.c:3312 [inline]  worker_thread+0x6c8/0xed0 kernel/workqueue.c:3389  kthread+0x2c1/0x3a0 kernel/kthread.c:389  ret_from_fork+0x45/0x80 arch/x86/kernel/process.c:147  ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:244(CVE-2024-49950)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  static_call: Replace pointless WARN_ON() in static_call_module_notify()  static_call_module_notify() triggers a WARN_ON(), when memory allocation fails in __static_call_add_module().  That\u0026apos;s not really justified, because the failure case must be correctly handled by the well known call chain and the error code is passed through to the initiating userspace application.  A memory allocation fail is not a fatal problem, but the WARN_ON() takes the machine out when panic_on_warn is set.  Replace it with a pr_warn().(CVE-2024-49954)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  ACPI: battery: Fix possible crash when unregistering a battery hook  When a battery hook returns an error when adding a new battery, then the battery hook is automatically unregistered. However the battery hook provider cannot know that, so it will later call battery_hook_unregister() on the already unregistered battery hook, resulting in a crash.  Fix this by using the list head to mark already unregistered battery hooks as already being unregistered so that they can be ignored by battery_hook_unregister().(CVE-2024-49955)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  ocfs2: reserve space for inline xattr before attaching reflink tree  One of our customers reported a crash and a corrupted ocfs2 filesystem.  The crash was due to the detection of corruption.  Upon troubleshooting, the fsck -fn output showed the below corruption  [EXTENT_LIST_FREE] Extent list in owner 33080590 claims 230 as the next free chain record, but fsck believes the largest valid value is 227.  Clamp the next record value? n  The stat output from the debugfs.ocfs2 showed the following corruption where the \u0026quot;Next Free Rec:\u0026quot; had overshot the \u0026quot;Count:\u0026quot; in the root metadata block.          Inode: 33080590   Mode: 0640   Generation: 2619713622 (0x9c25a856)         FS Generation: 904309833 (0x35e6ac49)         CRC32: 00000000   ECC: 0000         Type: Regular   Attr: 0x0   Flags: Valid         Dynamic Features: (0x16) HasXattr InlineXattr Refcounted         Extended Attributes Block: 0  Extended Attributes Inline Size: 256         User: 0 (root)   Group: 0 (root)   Size: 281320357888         Links: 1   Clusters: 141738         ctime: 0x66911b56 0x316edcb8 -- Fri Jul 12 06:02:30.829349048 2024         atime: 0x66911d6b 0x7f7a28d -- Fri Jul 12 06:11:23.133669517 2024         mtime: 0x66911b56 0x12ed75d7 -- Fri Jul 12 06:02:30.317552087 2024         dtime: 0x0 -- Wed Dec 31 17:00:00 1969         Refcount Block: 2777346         Last Extblk: 2886943   Orphan Slot: 0         Sub Alloc Slot: 0   Sub Alloc Bit: 14         Tree Depth: 1   Count: 227   Next Free Rec: 230         ## Offset        Clusters       Block#         0  0             2310           2776351         1  2310          2139           2777375         2  4449          1221           2778399         3  5670          731            2779423         4  6401          566            2780447         .......          ....           .......         .......          ....           .......  The issue was in the reflink workfow while reserving space for inline xattr.  The problematic function is ocfs2_reflink_xattr_inline().  By the time this function is called the reflink tree is already recreated at the destination inode from the source inode.  At this point, this function reserves space for inline xattrs at the destination inode without even checking if there is space at the root metadata block.  It simply reduces the l_count from 243 to 227 thereby making space of 256 bytes for inline xattr whereas the inode already has extents beyond this index (in this case up to 230), thereby causing corruption.  The fix for this is to reserve space for inline metadata at the destination inode before the reflink tree gets recreated. The customer has verified the fix.(CVE-2024-49958)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  r8169: add tally counter fields added with RTL8125  RTL8125 added fields to the tally counter, what may result in the chip dma\u0026apos;ing these new fields to unallocated memory. Therefore make sure that the allocated memory area is big enough to hold all of the tally counter values, even if we use only parts of it.(CVE-2024-49973)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  uprobes: fix kernel info leak via \u0026quot;[uprobes]\u0026quot; vma  xol_add_vma() maps the uninitialized page allocated by __create_xol_area() into userspace. On some architectures (x86) this memory is readable even without VM_READ, VM_EXEC results in the same pgprot_t as VM_EXEC|VM_READ, although this doesn\u0026apos;t really matter, debugger can read this memory anyway.(CVE-2024-49975)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  gso: fix udp gso fraglist segmentation after pull from frag_list  Detect gso fraglist skbs with corrupted geometry (see below) and pass these to skb_segment instead of skb_segment_list, as the first can segment them correctly.  Valid SKB_GSO_FRAGLIST skbs - consist of two or more segments - the head_skb holds the protocol headers plus first gso_size - one or more frag_list skbs hold exactly one segment - all but the last must be gso_size  Optional datapath hooks such as NAT and BPF (bpf_skb_pull_data) can modify these skbs, breaking these invariants.  In extreme cases they pull all data into skb linear. For UDP, this causes a NULL ptr deref in __udpv4_gso_segment_list_csum at udp_hdr(seg-\u0026gt;next)-\u0026gt;dest.  Detect invalid geometry due to pull, by checking head_skb size. Don\u0026apos;t just drop, as this may blackhole a destination. Convert to be able to pass to regular skb_segment.(CVE-2024-49978)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  media: venus: fix use after free bug in venus_remove due to race condition  in venus_probe, core-\u0026gt;work is bound with venus_sys_error_handler, which is used to handle error. The code use core-\u0026gt;sys_err_done to make sync work. The core-\u0026gt;work is started in venus_event_notify.  If we call venus_remove, there might be an unfished work. The possible sequence is as follows:  CPU0                  CPU1                       |venus_sys_error_handler venus_remove         | hfi_destroy     | venus_hfi_destroy  | kfree(hdev);      |                      |hfi_reinit       |venus_hfi_queues_reinit                      |//use hdev  Fix it by canceling the work in venus_remove.(CVE-2024-49981)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  drm/stm: Avoid use-after-free issues with crtc and plane  ltdc_load() calls functions drm_crtc_init_with_planes(), drm_universal_plane_init() and drm_encoder_init(). These functions should not be called with parameters allocated with devm_kzalloc() to avoid use-after-free issues [1].  Use allocations managed by the DRM framework.  Found by Linux Verification Center (linuxtesting.org).  [1] https://lore.kernel.org/lkml/u366i76e3qhh3ra5oxrtngjtm2u5lterkekcz6y2jkndhuxzli@diujon4h7qwb/(CVE-2024-49992)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  tipc: guard against string buffer overrun  Smatch reports that copying media_name and if_name to name_parts may overwrite the destination.   .../bearer.c:166 bearer_name_validate() error: strcpy() \u0026apos;media_name\u0026apos; too large for \u0026apos;name_parts-\u0026gt;media_name\u0026apos; (32 vs 16)  .../bearer.c:167 bearer_name_validate() error: strcpy() \u0026apos;if_name\u0026apos; too large for \u0026apos;name_parts-\u0026gt;if_name\u0026apos; (1010102 vs 16)  This does seem to be the case so guard against this possibility by using strscpy() and failing if truncation occurs.  Introduced by commit b97bf3fd8f6a (\u0026quot;[TIPC] Initial merge\u0026quot;)  Compile tested only.(CVE-2024-49995)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  cifs: Fix buffer overflow when parsing NFS reparse points  ReparseDataLength is sum of the InodeType size and DataBuffer size. So to get DataBuffer size it is needed to subtract InodeType\u0026apos;s size from ReparseDataLength.  Function cifs_strndup_from_utf16() is currentlly accessing buf-\u0026gt;DataBuffer at position after the end of the buffer because it does not subtract InodeType size from the length. Fix this problem and correctly subtract variable len.  Member InodeType is present only when reparse buffer is large enough. Check for ReparseDataLength before accessing InodeType to prevent another invalid memory access.  Major and minor rdev values are present also only when reparse buffer is large enough. Check for reparse buffer size before calling reparse_mkdev().(CVE-2024-49996)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  static_call: Handle module init failure correctly in static_call_del_module()  Module insertion invokes static_call_add_module() to initialize the static calls in a module. static_call_add_module() invokes __static_call_init(), which allocates a struct static_call_mod to either encapsulate the built-in static call sites of the associated key into it so further modules can be added or to append the module to the module chain.  If that allocation fails the function returns with an error code and the module core invokes static_call_del_module() to clean up eventually added static_call_mod entries.  This works correctly, when all keys used by the module were converted over to a module chain before the failure. If not then static_call_del_module() causes a #GP as it blindly assumes that key::mods points to a valid struct static_call_mod.  The problem is that key::mods is not a individual struct member of struct static_call_key, it\u0026apos;s part of a union to save space:          union {                 /* bit 0: 0 = mods, 1 = sites */                 unsigned long type;                 struct static_call_mod *mods;                 struct static_call_site *sites;  };  key::sites is a pointer to the list of built-in usage sites of the static call. The type of the pointer is differentiated by bit 0. A mods pointer has the bit clear, the sites pointer has the bit set.  As static_call_del_module() blidly assumes that the pointer is a valid static_call_mod type, it fails to check for this failure case and dereferences the pointer to the list of built-in call sites, which is obviously bogus.  Cure it by checking whether the key has a sites or a mods pointer.  If it\u0026apos;s a sites pointer then the key is not to be touched. As the sites are walked in the same order as in __static_call_init() the site walk can be terminated because all subsequent sites have not been touched by the init code due to the error exit.  If it was converted before the allocation fail, then the inner loop which searches for a module match will find nothing.  A fail in the second allocation in __static_call_init() is harmless and does not require special treatment. The first allocation succeeded and converted the key to a module chain. That first entry has mod::mod == NULL and mod::next == NULL, so the inner loop of static_call_del_module() will neither find a module match nor a module chain. The next site in the walk was either already converted, but can\u0026apos;t match the module, or it will exit the outer loop because it has a static_call_site pointer and not a static_call_mod pointer.(CVE-2024-50002)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  ALSA: asihpi: Fix potential OOB array access  ASIHPI driver stores some values in the static array upon a response from the driver, and its index depends on the firmware.  We shouldn\u0026apos;t trust it blindly.  This patch adds a sanity check of the array index to fit in the array size.(CVE-2024-50007)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  wifi: mwifiex: Fix memcpy() field-spanning write warning in mwifiex_cmd_802_11_scan_ext()  Replace one-element array with a flexible-array member in `struct host_cmd_ds_802_11_scan_ext`.  With this, fix the following warning:  elo 16 17:51:58 surfacebook kernel: ------------[ cut here ]------------ elo 16 17:51:58 surfacebook kernel: memcpy: detected field-spanning write (size 243) of single field \u0026quot;ext_scan-\u0026gt;tlv_buffer\u0026quot; at drivers/net/wireless/marvell/mwifiex/scan.c:2239 (size 1) elo 16 17:51:58 surfacebook kernel: WARNING: CPU: 0 PID: 498 at drivers/net/wireless/marvell/mwifiex/scan.c:2239 mwifiex_cmd_802_11_scan_ext+0x83/0x90 [mwifiex](CVE-2024-50008)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  ext4: dax: fix overflowing extents beyond inode size when partially writing  The dax_iomap_rw() does two things in each iteration: map written blocks and copy user data to blocks. If the process is killed by user(See signal handling in dax_iomap_iter()), the copied data will be returned and added on inode size, which means that the length of written extents may exceed the inode size, then fsck will fail. An example is given as:  dd if=/dev/urandom of=file bs=4M count=1  dax_iomap_rw   iomap_iter // round 1    ext4_iomap_begin     ext4_iomap_alloc // allocate 0~2M extents(written flag)   dax_iomap_iter // copy 2M data   iomap_iter // round 2    iomap_iter_advance     iter-\u0026gt;pos += iter-\u0026gt;processed // iter-\u0026gt;pos = 2M    ext4_iomap_begin     ext4_iomap_alloc // allocate 2~4M extents(written flag)   dax_iomap_iter    fatal_signal_pending   done = iter-\u0026gt;pos - iocb-\u0026gt;ki_pos // done = 2M  ext4_handle_inode_extension   ext4_update_inode_size // inode size = 2M  fsck reports: Inode 13, i_size is 2097152, should be 4194304.  Fix?  Fix the problem by truncating extents if the written length is smaller than expected.(CVE-2024-50015)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  drm/amd/display: Avoid overflow assignment in link_dp_cts  sampling_rate is an uint8_t but is assigned an unsigned int, and thus it can overflow. As a result, sampling_rate is changed to uint32_t.  Similarly, LINK_QUAL_PATTERN_SET has a size of 2 bits, and it should only be assigned to a value less or equal than 4.  This fixes 2 INTEGER_OVERFLOW issues reported by Coverity.(CVE-2024-50016)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  thermal: core: Reference count the zone in thermal_zone_get_by_id()  There are places in the thermal netlink code where nothing prevents the thermal zone object from going away while being accessed after it has been returned by thermal_zone_get_by_id().  To address this, make thermal_zone_get_by_id() get a reference on the thermal zone device object to be returned with the help of get_device(), under thermal_list_lock, and adjust all of its callers to this change with the help of the cleanup.h infrastructure.(CVE-2024-50028)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  slip: make slhc_remember() more robust against malicious packets  syzbot found that slhc_remember() was missing checks against malicious packets [1].  slhc_remember() only checked the size of the packet was at least 20, which is not good enough.  We need to make sure the packet includes the IPv4 and TCP header that are supposed to be carried.  Add iph and th pointers to make the code more readable.  [1]  BUG: KMSAN: uninit-value in slhc_remember+0x2e8/0x7b0 drivers/net/slip/slhc.c:666   slhc_remember+0x2e8/0x7b0 drivers/net/slip/slhc.c:666   ppp_receive_nonmp_frame+0xe45/0x35e0 drivers/net/ppp/ppp_generic.c:2455   ppp_receive_frame drivers/net/ppp/ppp_generic.c:2372 [inline]   ppp_do_recv+0x65f/0x40d0 drivers/net/ppp/ppp_generic.c:2212   ppp_input+0x7dc/0xe60 drivers/net/ppp/ppp_generic.c:2327   pppoe_rcv_core+0x1d3/0x720 drivers/net/ppp/pppoe.c:379   sk_backlog_rcv+0x13b/0x420 include/net/sock.h:1113   __release_sock+0x1da/0x330 net/core/sock.c:3072   release_sock+0x6b/0x250 net/core/sock.c:3626   pppoe_sendmsg+0x2b8/0xb90 drivers/net/ppp/pppoe.c:903   sock_sendmsg_nosec net/socket.c:729 [inline]   __sock_sendmsg+0x30f/0x380 net/socket.c:744   ____sys_sendmsg+0x903/0xb60 net/socket.c:2602   ___sys_sendmsg+0x28d/0x3c0 net/socket.c:2656   __sys_sendmmsg+0x3c1/0x960 net/socket.c:2742   __do_sys_sendmmsg net/socket.c:2771 [inline]   __se_sys_sendmmsg net/socket.c:2768 [inline]   __x64_sys_sendmmsg+0xbc/0x120 net/socket.c:2768   x64_sys_call+0xb6e/0x3ba0 arch/x86/include/generated/asm/syscalls_64.h:308   do_syscall_x64 arch/x86/entry/common.c:52 [inline]   do_syscall_64+0xcd/0x1e0 arch/x86/entry/common.c:83  entry_SYSCALL_64_after_hwframe+0x77/0x7f  Uninit was created at:   slab_post_alloc_hook mm/slub.c:4091 [inline]   slab_alloc_node mm/slub.c:4134 [inline]   kmem_cache_alloc_node_noprof+0x6bf/0xb80 mm/slub.c:4186   kmalloc_reserve+0x13d/0x4a0 net/core/skbuff.c:587   __alloc_skb+0x363/0x7b0 net/core/skbuff.c:678   alloc_skb include/linux/skbuff.h:1322 [inline]   sock_wmalloc+0xfe/0x1a0 net/core/sock.c:2732   pppoe_sendmsg+0x3a7/0xb90 drivers/net/ppp/pppoe.c:867   sock_sendmsg_nosec net/socket.c:729 [inline]   __sock_sendmsg+0x30f/0x380 net/socket.c:744   ____sys_sendmsg+0x903/0xb60 net/socket.c:2602   ___sys_sendmsg+0x28d/0x3c0 net/socket.c:2656   __sys_sendmmsg+0x3c1/0x960 net/socket.c:2742   __do_sys_sendmmsg net/socket.c:2771 [inline]   __se_sys_sendmmsg net/socket.c:2768 [inline]   __x64_sys_sendmmsg+0xbc/0x120 net/socket.c:2768   x64_sys_call+0xb6e/0x3ba0 arch/x86/include/generated/asm/syscalls_64.h:308   do_syscall_x64 arch/x86/entry/common.c:52 [inline]   do_syscall_64+0xcd/0x1e0 arch/x86/entry/common.c:83  entry_SYSCALL_64_after_hwframe+0x77/0x7f  CPU: 0 UID: 0 PID: 5460 Comm: syz.2.33 Not tainted 6.12.0-rc2-syzkaller-00006-g87d6aab2389e #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 09/13/2024(CVE-2024-50033)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  ppp: fix ppp_async_encode() illegal access  syzbot reported an issue in ppp_async_encode() [1]  In this case, pppoe_sendmsg() is called with a zero size. Then ppp_async_encode() is called with an empty skb.  BUG: KMSAN: uninit-value in ppp_async_encode drivers/net/ppp/ppp_async.c:545 [inline]  BUG: KMSAN: uninit-value in ppp_async_push+0xb4f/0x2660 drivers/net/ppp/ppp_async.c:675   ppp_async_encode drivers/net/ppp/ppp_async.c:545 [inline]   ppp_async_push+0xb4f/0x2660 drivers/net/ppp/ppp_async.c:675   ppp_async_send+0x130/0x1b0 drivers/net/ppp/ppp_async.c:634   ppp_channel_bridge_input drivers/net/ppp/ppp_generic.c:2280 [inline]   ppp_input+0x1f1/0xe60 drivers/net/ppp/ppp_generic.c:2304   pppoe_rcv_core+0x1d3/0x720 drivers/net/ppp/pppoe.c:379   sk_backlog_rcv+0x13b/0x420 include/net/sock.h:1113   __release_sock+0x1da/0x330 net/core/sock.c:3072   release_sock+0x6b/0x250 net/core/sock.c:3626   pppoe_sendmsg+0x2b8/0xb90 drivers/net/ppp/pppoe.c:903   sock_sendmsg_nosec net/socket.c:729 [inline]   __sock_sendmsg+0x30f/0x380 net/socket.c:744   ____sys_sendmsg+0x903/0xb60 net/socket.c:2602   ___sys_sendmsg+0x28d/0x3c0 net/socket.c:2656   __sys_sendmmsg+0x3c1/0x960 net/socket.c:2742   __do_sys_sendmmsg net/socket.c:2771 [inline]   __se_sys_sendmmsg net/socket.c:2768 [inline]   __x64_sys_sendmmsg+0xbc/0x120 net/socket.c:2768   x64_sys_call+0xb6e/0x3ba0 arch/x86/include/generated/asm/syscalls_64.h:308   do_syscall_x64 arch/x86/entry/common.c:52 [inline]   do_syscall_64+0xcd/0x1e0 arch/x86/entry/common.c:83  entry_SYSCALL_64_after_hwframe+0x77/0x7f  Uninit was created at:   slab_post_alloc_hook mm/slub.c:4092 [inline]   slab_alloc_node mm/slub.c:4135 [inline]   kmem_cache_alloc_node_noprof+0x6bf/0xb80 mm/slub.c:4187   kmalloc_reserve+0x13d/0x4a0 net/core/skbuff.c:587   __alloc_skb+0x363/0x7b0 net/core/skbuff.c:678   alloc_skb include/linux/skbuff.h:1322 [inline]   sock_wmalloc+0xfe/0x1a0 net/core/sock.c:2732   pppoe_sendmsg+0x3a7/0xb90 drivers/net/ppp/pppoe.c:867   sock_sendmsg_nosec net/socket.c:729 [inline]   __sock_sendmsg+0x30f/0x380 net/socket.c:744   ____sys_sendmsg+0x903/0xb60 net/socket.c:2602   ___sys_sendmsg+0x28d/0x3c0 net/socket.c:2656   __sys_sendmmsg+0x3c1/0x960 net/socket.c:2742   __do_sys_sendmmsg net/socket.c:2771 [inline]   __se_sys_sendmmsg net/socket.c:2768 [inline]   __x64_sys_sendmmsg+0xbc/0x120 net/socket.c:2768   x64_sys_call+0xb6e/0x3ba0 arch/x86/include/generated/asm/syscalls_64.h:308   do_syscall_x64 arch/x86/entry/common.c:52 [inline]   do_syscall_64+0xcd/0x1e0 arch/x86/entry/common.c:83  entry_SYSCALL_64_after_hwframe+0x77/0x7f  CPU: 1 UID: 0 PID: 5411 Comm: syz.1.14 Not tainted 6.12.0-rc1-syzkaller-00165-g360c1f1f24c6 #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 09/13/2024(CVE-2024-50035)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  igb: Do not bring the device up after non-fatal error  Commit 004d25060c78 (\u0026quot;igb: Fix igb_down hung on surprise removal\u0026quot;) changed igb_io_error_detected() to ignore non-fatal pcie errors in order to avoid hung task that can happen when igb_down() is called multiple times. This caused an issue when processing transient non-fatal errors. igb_io_resume(), which is called after igb_io_error_detected(), assumes that device is brought down by igb_io_error_detected() if the interface is up. This resulted in panic with stacktrace below.  [ T3256] igb 0000:09:00.0 haeth0: igb: haeth0 NIC Link is Down [  T292] pcieport 0000:00:1c.5: AER: Uncorrected (Non-Fatal) error received: 0000:09:00.0 [  T292] igb 0000:09:00.0: PCIe Bus Error: severity=Uncorrected (Non-Fatal), type=Transaction Layer, (Requester ID) [  T292] igb 0000:09:00.0:   device [8086:1537] error status/mask=00004000/00000000 [  T292] igb 0000:09:00.0:    [14] CmpltTO [  200.105524,009][  T292] igb 0000:09:00.0: AER:   TLP Header: 00000000 00000000 00000000 00000000 [  T292] pcieport 0000:00:1c.5: AER: broadcast error_detected message [  T292] igb 0000:09:00.0: Non-correctable non-fatal error reported. [  T292] pcieport 0000:00:1c.5: AER: broadcast mmio_enabled message [  T292] pcieport 0000:00:1c.5: AER: broadcast resume message [  T292] ------------[ cut here ]------------ [  T292] kernel BUG at net/core/dev.c:6539! [  T292] invalid opcode: 0000 [#1] PREEMPT SMP [  T292] RIP: 0010:napi_enable+0x37/0x40 [  T292] Call Trace: [  T292]  \u0026lt;TASK\u0026gt; [  T292]  ? die+0x33/0x90 [  T292]  ? do_trap+0xdc/0x110 [  T292]  ? napi_enable+0x37/0x40 [  T292]  ? do_error_trap+0x70/0xb0 [  T292]  ? napi_enable+0x37/0x40 [  T292]  ? napi_enable+0x37/0x40 [  T292]  ? exc_invalid_op+0x4e/0x70 [  T292]  ? napi_enable+0x37/0x40 [  T292]  ? asm_exc_invalid_op+0x16/0x20 [  T292]  ? napi_enable+0x37/0x40 [  T292]  igb_up+0x41/0x150 [  T292]  igb_io_resume+0x25/0x70 [  T292]  report_resume+0x54/0x70 [  T292]  ? report_frozen_detected+0x20/0x20 [  T292]  pci_walk_bus+0x6c/0x90 [  T292]  ? aer_print_port_info+0xa0/0xa0 [  T292]  pcie_do_recovery+0x22f/0x380 [  T292]  aer_process_err_devices+0x110/0x160 [  T292]  aer_isr+0x1c1/0x1e0 [  T292]  ? disable_irq_nosync+0x10/0x10 [  T292]  irq_thread_fn+0x1a/0x60 [  T292]  irq_thread+0xe3/0x1a0 [  T292]  ? irq_set_affinity_notifier+0x120/0x120 [  T292]  ? irq_affinity_notify+0x100/0x100 [  T292]  kthread+0xe2/0x110 [  T292]  ? kthread_complete_and_exit+0x20/0x20 [  T292]  ret_from_fork+0x2d/0x50 [  T292]  ? kthread_complete_and_exit+0x20/0x20 [  T292]  ret_from_fork_asm+0x11/0x20 [  T292]  \u0026lt;/TASK\u0026gt;  To fix this issue igb_io_resume() checks if the interface is running and the device is not down this means igb_io_error_detected() did not bring the device down and there is no need to bring it up.(CVE-2024-50040)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  smb: client: fix UAF in async decryption  Doing an async decryption (large read) crashes with a slab-use-after-free way down in the crypto API.  Reproducer:     # mount.cifs -o ...,seal,esize=1 //srv/share /mnt     # dd if=/mnt/largefile of=/dev/null     ...     [  194.196391] ==================================================================     [  194.196844] BUG: KASAN: slab-use-after-free in gf128mul_4k_lle+0xc1/0x110     [  194.197269] Read of size 8 at addr ffff888112bd0448 by task kworker/u77:2/899     [  194.197707]     [  194.197818] CPU: 12 UID: 0 PID: 899 Comm: kworker/u77:2 Not tainted 6.11.0-lku-00028-gfca3ca14a17a-dirty #43     [  194.198400] Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS rel-1.16.2-3-gd478f380-prebuilt.qemu.org 04/01/2014     [  194.199046] Workqueue: smb3decryptd smb2_decrypt_offload [cifs]     [  194.200032] Call Trace:     [  194.200191]  \u0026lt;TASK\u0026gt;     [  194.200327]  dump_stack_lvl+0x4e/0x70     [  194.200558]  ? gf128mul_4k_lle+0xc1/0x110     [  194.200809]  print_report+0x174/0x505     [  194.201040]  ? __pfx__raw_spin_lock_irqsave+0x10/0x10     [  194.201352]  ? srso_return_thunk+0x5/0x5f     [  194.201604]  ? __virt_addr_valid+0xdf/0x1c0     [  194.201868]  ? gf128mul_4k_lle+0xc1/0x110     [  194.202128]  kasan_report+0xc8/0x150     [  194.202361]  ? gf128mul_4k_lle+0xc1/0x110     [  194.202616]  gf128mul_4k_lle+0xc1/0x110     [  194.202863]  ghash_update+0x184/0x210     [  194.203103]  shash_ahash_update+0x184/0x2a0     [  194.203377]  ? __pfx_shash_ahash_update+0x10/0x10     [  194.203651]  ? srso_return_thunk+0x5/0x5f     [  194.203877]  ? crypto_gcm_init_common+0x1ba/0x340     [  194.204142]  gcm_hash_assoc_remain_continue+0x10a/0x140     [  194.204434]  crypt_message+0xec1/0x10a0 [cifs]     [  194.206489]  ? __pfx_crypt_message+0x10/0x10 [cifs]     [  194.208507]  ? srso_return_thunk+0x5/0x5f     [  194.209205]  ? srso_return_thunk+0x5/0x5f     [  194.209925]  ? srso_return_thunk+0x5/0x5f     [  194.210443]  ? srso_return_thunk+0x5/0x5f     [  194.211037]  decrypt_raw_data+0x15f/0x250 [cifs]     [  194.212906]  ? __pfx_decrypt_raw_data+0x10/0x10 [cifs]     [  194.214670]  ? srso_return_thunk+0x5/0x5f     [  194.215193]  smb2_decrypt_offload+0x12a/0x6c0 [cifs]  This is because TFM is being used in parallel.  Fix this by allocating a new AEAD TFM for async decryption, but keep the existing one for synchronous READ cases (similar to what is done in smb3_calc_signature()).  Also remove the calls to aead_request_set_callback() and crypto_wait_req() since it\u0026apos;s always going to be a synchronous operation.(CVE-2024-50047)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  serial: protect uart_port_dtr_rts() in uart_shutdown() too  Commit af224ca2df29 (serial: core: Prevent unsafe uart port access, part 3) added few uport == NULL checks. It added one to uart_shutdown(), so the commit assumes, uport can be NULL in there. But right after that protection, there is an unprotected \u0026quot;uart_port_dtr_rts(uport, false);\u0026quot; call. That is invoked only if HUPCL is set, so I assume that is the reason why we do not see lots of these reports.  Or it cannot be NULL at this point at all for some reason :P.  Until the above is investigated, stay on the safe side and move this dereference to the if too.  I got this inconsistency from Coverity under CID 1585130. Thanks.(CVE-2024-50058)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  ntb: ntb_hw_switchtec: Fix use after free vulnerability in switchtec_ntb_remove due to race condition  In the switchtec_ntb_add function, it can call switchtec_ntb_init_sndev function, then \u0026amp;sndev-\u0026gt;check_link_status_work is bound with check_link_status_work. switchtec_ntb_link_notification may be called to start the work.  If we remove the module which will call switchtec_ntb_remove to make cleanup, it will free sndev through kfree(sndev), while the work mentioned above will be used. The sequence of operations that may lead to a UAF bug is as follows:  CPU0                                 CPU1                          | check_link_status_work switchtec_ntb_remove    | kfree(sndev);           |                         | if (sndev-\u0026gt;link_force_down)                         | // use sndev  Fix it by ensuring that the work is canceled before proceeding with the cleanup in switchtec_ntb_remove.(CVE-2024-50059)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  io_uring: check if we need to reschedule during overflow flush  In terms of normal application usage, this list will always be empty. And if an application does overflow a bit, it\u0026apos;ll have a few entries. However, nothing obviously prevents syzbot from running a test case that generates a ton of overflow entries, and then flushing them can take quite a while.  Check for needing to reschedule while flushing, and drop our locks and do so if necessary. There\u0026apos;s no state to maintain here as overflows always prune from head-of-list, hence it\u0026apos;s fine to drop and reacquire the locks at the end of the loop.(CVE-2024-50060)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  bpf: Prevent tail call between progs attached to different hooks  bpf progs can be attached to kernel functions, and the attached functions can take different parameters or return different return values. If prog attached to one kernel function tail calls prog attached to another kernel function, the ctx access or return value verification could be bypassed.  For example, if prog1 is attached to func1 which takes only 1 parameter and prog2 is attached to func2 which takes two parameters. Since verifier assumes the bpf ctx passed to prog2 is constructed based on func2\u0026apos;s prototype, verifier allows prog2 to access the second parameter from the bpf ctx passed to it. The problem is that verifier does not prevent prog1 from passing its bpf ctx to prog2 via tail call. In this case, the bpf ctx passed to prog2 is constructed from func1 instead of func2, that is, the assumption for ctx access verification is bypassed.  Another example, if BPF LSM prog1 is attached to hook file_alloc_security, and BPF LSM prog2 is attached to hook bpf_lsm_audit_rule_known. Verifier knows the return value rules for these two hooks, e.g. it is legal for bpf_lsm_audit_rule_known to return positive number 1, and it is illegal for file_alloc_security to return positive number. So verifier allows prog2 to return positive number 1, but does not allow prog1 to return positive number. The problem is that verifier does not prevent prog1 from calling prog2 via tail call. In this case, prog2\u0026apos;s return value 1 will be used as the return value for prog1\u0026apos;s hook file_alloc_security. That is, the return value rule is bypassed.  This patch adds restriction for tail call to prevent such bypasses.(CVE-2024-50063)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  zram: free secondary algorithms names  We need to kfree() secondary algorithms names when reset zram device that had multi-streams, otherwise we leak memory.  [senozhatsky@chromium.org: kfree(NULL) is legal]   Link: https://lkml.kernel.org/r/20240917013021.868769-1-senozhatsky@chromium.org(CVE-2024-50064)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  uprobe: avoid out-of-bounds memory access of fetching args  Uprobe needs to fetch args into a percpu buffer, and then copy to ring buffer to avoid non-atomic context problem.  Sometimes user-space strings, arrays can be very large, but the size of percpu buffer is only page size. And store_trace_args() won\u0026apos;t check whether these data exceeds a single page or not, caused out-of-bounds memory access.  It could be reproduced by following steps: 1. build kernel with CONFIG_KASAN enabled 2. save follow program as test.c  ``` \\#include \u0026lt;stdio.h\u0026gt; \\#include \u0026lt;stdlib.h\u0026gt; \\#include \u0026lt;string.h\u0026gt;  // If string length large than MAX_STRING_SIZE, the fetch_store_strlen() // will return 0, cause __get_data_size() return shorter size, and // store_trace_args() will not trigger out-of-bounds access. // So make string length less than 4096. \\#define STRLEN 4093  void generate_string(char *str, int n) {     int i;     for (i = 0; i \u0026lt; n; ++i)     {         char c = i % 26 + \u0026apos;a\u0026apos;;         str[i] = c;     }     str[n-1] = \u0026apos;\\0\u0026apos;; }  void print_string(char *str) {     printf(\u0026quot;%s\\n\u0026quot;, str); }  int main() {     char tmp[STRLEN];      generate_string(tmp, STRLEN);     print_string(tmp);      return 0; } ``` 3. compile program `gcc -o test test.c`  4. get the offset of `print_string()` ``` objdump -t test | grep -w print_string 0000000000401199 g     F .text  000000000000001b              print_string ```  5. configure uprobe with offset 0x1199 ``` off=0x1199  cd /sys/kernel/debug/tracing/ echo \u0026quot;p /root/test:${off} arg1=+0(%di):ustring arg2=\\$comm arg3=+0(%di):ustring\u0026quot;  \u0026gt; uprobe_events echo 1 \u0026gt; events/uprobes/enable echo 1 \u0026gt; tracing_on ```  6. run `test`, and kasan will report error. ================================================================== BUG: KASAN: use-after-free in strncpy_from_user+0x1d6/0x1f0 Write of size 8 at addr ffff88812311c004 by task test/499CPU: 0 UID: 0 PID: 499 Comm: test Not tainted 6.12.0-rc3+ #18 Hardware name: Red Hat KVM, BIOS 1.16.0-4.al8 04/01/2014 Call Trace:  \u0026lt;TASK\u0026gt;  dump_stack_lvl+0x55/0x70  print_address_description.constprop.0+0x27/0x310  kasan_report+0x10f/0x120  ? strncpy_from_user+0x1d6/0x1f0  strncpy_from_user+0x1d6/0x1f0  ? rmqueue.constprop.0+0x70d/0x2ad0  process_fetch_insn+0xb26/0x1470  ? __pfx_process_fetch_insn+0x10/0x10  ? _raw_spin_lock+0x85/0xe0  ? __pfx__raw_spin_lock+0x10/0x10  ? __pte_offset_map+0x1f/0x2d0  ? unwind_next_frame+0xc5f/0x1f80  ? arch_stack_walk+0x68/0xf0  ? is_bpf_text_address+0x23/0x30  ? kernel_text_address.part.0+0xbb/0xd0  ? __kernel_text_address+0x66/0xb0  ? unwind_get_return_address+0x5e/0xa0  ? __pfx_stack_trace_consume_entry+0x10/0x10  ? arch_stack_walk+0xa2/0xf0  ? _raw_spin_lock_irqsave+0x8b/0xf0  ? __pfx__raw_spin_lock_irqsave+0x10/0x10  ? depot_alloc_stack+0x4c/0x1f0  ? _raw_spin_unlock_irqrestore+0xe/0x30  ? stack_depot_save_flags+0x35d/0x4f0  ? kasan_save_stack+0x34/0x50  ? kasan_save_stack+0x24/0x50  ? mutex_lock+0x91/0xe0  ? __pfx_mutex_lock+0x10/0x10  prepare_uprobe_buffer.part.0+0x2cd/0x500  uprobe_dispatcher+0x2c3/0x6a0  ? __pfx_uprobe_dispatcher+0x10/0x10  ? __kasan_slab_alloc+0x4d/0x90  handler_chain+0xdd/0x3e0  handle_swbp+0x26e/0x3d0  ? __pfx_handle_swbp+0x10/0x10  ? uprobe_pre_sstep_notifier+0x151/0x1b0  irqentry_exit_to_user_mode+0xe2/0x1b0  asm_exc_int3+0x39/0x40 RIP: 0033:0x401199 Code: 01 c2 0f b6 45 fb 88 02 83 45 fc 01 8b 45 fc 3b 45 e4 7c b7 8b 45 e4 48 98 48 8d 50 ff 48 8b 45 e8 48 01 d0 ce RSP: 002b:00007ffdf00576a8 EFLAGS: 00000206 RAX: 00007ffdf00576b0 RBX: 0000000000000000 RCX: 0000000000000ff2 RDX: 0000000000000ffc RSI: 0000000000000ffd RDI: 00007ffdf00576b0 RBP: 00007ffdf00586b0 R08: 00007feb2f9c0d20 R09: 00007feb2f9c0d20 R10: 0000000000000001 R11: 0000000000000202 R12: 0000000000401040 R13: 00007ffdf0058780 R14: 0000000000000000 R15: 0000000000000000  \u0026lt;/TASK\u0026gt;  This commit enforces the buffer\u0026apos;s maxlen less than a page-size to avoid store_trace_args() out-of-memory access.(CVE-2024-50067)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  parport: Proper fix for array out-of-bounds access  The recent fix for array out-of-bounds accesses replaced sprintf() calls blindly with snprintf().  However, since snprintf() returns the would-be-printed size, not the actually output size, the length calculation can still go over the given limit.  Use scnprintf() instead of snprintf(), which returns the actually output letters, for addressing the potential out-of-bounds access properly.(CVE-2024-50074)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  tcp: fix mptcp DSS corruption due to large pmtu xmit  Syzkaller was able to trigger a DSS corruption:    TCP: request_sock_subflow_v4: Possible SYN flooding on port [::]:20002. Sending cookies.   ------------[ cut here ]------------   WARNING: CPU: 0 PID: 5227 at net/mptcp/protocol.c:695 __mptcp_move_skbs_from_subflow+0x20a9/0x21f0 net/mptcp/protocol.c:695   Modules linked in:   CPU: 0 UID: 0 PID: 5227 Comm: syz-executor350 Not tainted 6.11.0-syzkaller-08829-gaf9c191ac2a0 #0   Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 08/06/2024   RIP: 0010:__mptcp_move_skbs_from_subflow+0x20a9/0x21f0 net/mptcp/protocol.c:695   Code: 0f b6 dc 31 ff 89 de e8 b5 dd ea f5 89 d8 48 81 c4 50 01 00 00 5b 41 5c 41 5d 41 5e 41 5f 5d c3 cc cc cc cc e8 98 da ea f5 90 \u0026lt;0f\u0026gt; 0b 90 e9 47 ff ff ff e8 8a da ea f5 90 0f 0b 90 e9 99 e0 ff ff   RSP: 0018:ffffc90000006db8 EFLAGS: 00010246   RAX: ffffffff8ba9df18 RBX: 00000000000055f0 RCX: ffff888030023c00   RDX: 0000000000000100 RSI: 00000000000081e5 RDI: 00000000000055f0   RBP: 1ffff110062bf1ae R08: ffffffff8ba9cf12 R09: 1ffff110062bf1b8   R10: dffffc0000000000 R11: ffffed10062bf1b9 R12: 0000000000000000   R13: dffffc0000000000 R14: 00000000700cec61 R15: 00000000000081e5   FS:  000055556679c380(0000) GS:ffff8880b8600000(0000) knlGS:0000000000000000   CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033   CR2: 0000000020287000 CR3: 0000000077892000 CR4: 00000000003506f0   DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000   DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400   Call Trace:    \u0026lt;IRQ\u0026gt;    move_skbs_to_msk net/mptcp/protocol.c:811 [inline]    mptcp_data_ready+0x29c/0xa90 net/mptcp/protocol.c:854    subflow_data_ready+0x34a/0x920 net/mptcp/subflow.c:1490    tcp_data_queue+0x20fd/0x76c0 net/ipv4/tcp_input.c:5283    tcp_rcv_established+0xfba/0x2020 net/ipv4/tcp_input.c:6237    tcp_v4_do_rcv+0x96d/0xc70 net/ipv4/tcp_ipv4.c:1915    tcp_v4_rcv+0x2dc0/0x37f0 net/ipv4/tcp_ipv4.c:2350    ip_protocol_deliver_rcu+0x22e/0x440 net/ipv4/ip_input.c:205    ip_local_deliver_finish+0x341/0x5f0 net/ipv4/ip_input.c:233    NF_HOOK+0x3a4/0x450 include/linux/netfilter.h:314    NF_HOOK+0x3a4/0x450 include/linux/netfilter.h:314    __netif_receive_skb_one_core net/core/dev.c:5662 [inline]    __netif_receive_skb+0x2bf/0x650 net/core/dev.c:5775    process_backlog+0x662/0x15b0 net/core/dev.c:6107    __napi_poll+0xcb/0x490 net/core/dev.c:6771    napi_poll net/core/dev.c:6840 [inline]    net_rx_action+0x89b/0x1240 net/core/dev.c:6962    handle_softirqs+0x2c5/0x980 kernel/softirq.c:554    do_softirq+0x11b/0x1e0 kernel/softirq.c:455    \u0026lt;/IRQ\u0026gt;    \u0026lt;TASK\u0026gt;    __local_bh_enable_ip+0x1bb/0x200 kernel/softirq.c:382    local_bh_enable include/linux/bottom_half.h:33 [inline]    rcu_read_unlock_bh include/linux/rcupdate.h:919 [inline]    __dev_queue_xmit+0x1764/0x3e80 net/core/dev.c:4451    dev_queue_xmit include/linux/netdevice.h:3094 [inline]    neigh_hh_output include/net/neighbour.h:526 [inline]    neigh_output include/net/neighbour.h:540 [inline]    ip_finish_output2+0xd41/0x1390 net/ipv4/ip_output.c:236    ip_local_out net/ipv4/ip_output.c:130 [inline]    __ip_queue_xmit+0x118c/0x1b80 net/ipv4/ip_output.c:536    __tcp_transmit_skb+0x2544/0x3b30 net/ipv4/tcp_output.c:1466    tcp_transmit_skb net/ipv4/tcp_output.c:1484 [inline]    tcp_mtu_probe net/ipv4/tcp_output.c:2547 [inline]    tcp_write_xmit+0x641d/0x6bf0 net/ipv4/tcp_output.c:2752    __tcp_push_pending_frames+0x9b/0x360 net/ipv4/tcp_output.c:3015    tcp_push_pending_frames include/net/tcp.h:2107 [inline]    tcp_data_snd_check net/ipv4/tcp_input.c:5714 [inline]    tcp_rcv_established+0x1026/0x2020 net/ipv4/tcp_input.c:6239    tcp_v4_do_rcv+0x96d/0xc70 net/ipv4/tcp_ipv4.c:1915    sk_backlog_rcv include/net/sock.h:1113 [inline]    __release_sock+0x214/0x350 net/core/sock.c:3072    release_sock+0x61/0x1f0 net/core/sock.c:3626    mptcp_push_ ---truncated---(CVE-2024-50083)","status":"published","published":"2024-11-08T11:07:50Z","modified":"2026-08-18T01:18:38.692115173Z","cvss":[{"version":"3.1","score":8.8,"vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H","level":"high"}],"updated_at":"2026-11-02T15:52:42.253598Z"},{"id":"OESA-2024-2369","title":"kernel security update","description":"The Linux Kernel, the operating system core itself.\r\n\r\nSecurity Fix(es):\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  net: mdio: fix unbalanced fwnode reference count in mdio_device_release()  There is warning report about of_node refcount leak while probing mdio device:  OF: ERROR: memory leak, expected refcount 1 instead of 2, of_node_get()/of_node_put() unbalanced - destroy cset entry: attach overlay node /spi/soc@0/mdio@710700c0/ethernet@4  In of_mdiobus_register_device(), we increase fwnode refcount by fwnode_handle_get() before associating the of_node with mdio device, but it has never been decreased in normal path. Since that, in mdio_device_release(), it needs to call fwnode_handle_put() in addition instead of calling kfree() directly.  After above, just calling mdio_device_free() in the error handle path of of_mdiobus_register_device() is enough to keep the refcount balanced.(CVE-2022-48961)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  gpiolib: fix memory leak in gpiochip_setup_dev()  Here is a backtrace report about memory leak detected in gpiochip_setup_dev():  unreferenced object 0xffff88810b406400 (size 512):   comm \u0026quot;python3\u0026quot;, pid 1682, jiffies 4295346908 (age 24.090s)   backtrace:     kmalloc_trace     device_add  device_private_init at drivers/base/core.c:3361    (inlined by) device_add at drivers/base/core.c:3411     cdev_device_add     gpiolib_cdev_register     gpiochip_setup_dev     gpiochip_add_data_with_key  gcdev_register() \u0026amp; gcdev_unregister() would call device_add() \u0026amp; device_del() (no matter CONFIG_GPIO_CDEV is enabled or not) to register/unregister device.  However, if device_add() succeeds, some resource (like struct device_private allocated by device_private_init()) is not released by device_del().  Therefore, after device_add() succeeds by gcdev_register(), it needs to call put_device() to release resource in the error handle path.  Here we move forward the register of release function, and let it release every piece of resource by put_device() instead of kfree().  While at it, fix another subtle issue, i.e. when gc-\u0026gt;ngpio is equal to 0, we still call kcalloc() and, in case of further error, kfree() on the ZERO_PTR pointer, which is not NULL. It\u0026apos;s not a bug per se, but rather waste of the resources and potentially wrong expectation about contents of the gdev-\u0026gt;descs variable.(CVE-2022-48975)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  riscv: Sync efi page table\u0026apos;s kernel mappings before switching  The EFI page table is initially created as a copy of the kernel page table. With VMAP_STACK enabled, kernel stacks are allocated in the vmalloc area: if the stack is allocated in a new PGD (one that was not present at the moment of the efi page table creation or not synced in a previous vmalloc fault), the kernel will take a trap when switching to the efi page table when the vmalloc kernel stack is accessed, resulting in a kernel panic.  Fix that by updating the efi kernel mappings before switching to the efi page table.(CVE-2022-49004)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nmemcg_write_event_control(): fix a user-triggerable oops\r\n\r\nwe are *not* guaranteed that anything past the terminating NUL\nis mapped (let alone initialized with anything sane).(CVE-2024-45021)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\ngtp: fix a potential NULL pointer dereference\r\n\r\nWhen sockfd_lookup() fails, gtp_encap_enable_socket() returns a\nNULL pointer, but its callers only check for error pointers thus miss\nthe NULL pointer case.\r\n\r\nFix it by returning an error pointer with the error code carried from\nsockfd_lookup().\r\n\r\n(I found this bug during code inspection.)(CVE-2024-46677)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\ndrm/amd/display: Check BIOS images before it is used\r\n\r\nBIOS images may fail to load and null checks are added before they are\nused.\r\n\r\nThis fixes 6 NULL_RETURNS issues reported by Coverity.(CVE-2024-46809)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nsmack: tcp: ipv4, fix incorrect labeling\r\n\r\nCurrently, Smack mirrors the label of incoming tcp/ipv4 connections:\nwhen a label \u0026apos;foo\u0026apos; connects to a label \u0026apos;bar\u0026apos; with tcp/ipv4,\n\u0026apos;foo\u0026apos; always gets \u0026apos;foo\u0026apos; in returned ipv4 packets. So,\n1) returned packets are incorrectly labeled (\u0026apos;foo\u0026apos; instead of \u0026apos;bar\u0026apos;)\n2) \u0026apos;bar\u0026apos; can write to \u0026apos;foo\u0026apos; without being authorized to write.\r\n\r\nHere is a scenario how to see this:\r\n\r\n* Take two machines, let\u0026apos;s call them C and S,\n   with active Smack in the default state\n   (no settings, no rules, no labeled hosts, only builtin labels)\r\n\r\n* At S, add Smack rule \u0026apos;foo bar w\u0026apos;\n   (labels \u0026apos;foo\u0026apos; and \u0026apos;bar\u0026apos; are instantiated at S at this moment)\r\n\r\n* At S, at label \u0026apos;bar\u0026apos;, launch a program\n   that listens for incoming tcp/ipv4 connections\r\n\r\n* From C, at label \u0026apos;foo\u0026apos;, connect to the listener at S.\n   (label \u0026apos;foo\u0026apos; is instantiated at C at this moment)\n   Connection succeedes and works.\r\n\r\n* Send some data in both directions.\n* Collect network traffic of this connection.\r\n\r\nAll packets in both directions are labeled with the CIPSO\nof the label \u0026apos;foo\u0026apos;. Hence, label \u0026apos;bar\u0026apos; writes to \u0026apos;foo\u0026apos; without\nbeing authorized, and even without ever being known at C.\r\n\r\nIf anybody cares: exactly the same happens with DCCP.\r\n\r\nThis behavior 1st manifested in release 2.6.29.4 (see Fixes below)\nand it looks unintentional. At least, no explanation was provided.\r\n\r\nI changed returned packes label into the \u0026apos;bar\u0026apos;,\nto bring it into line with the Smack documentation claims.(CVE-2024-47659)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nfsnotify: clear PARENT_WATCHED flags lazily\r\n\r\nIn some setups directories can have many (usually negative) dentries.\nHence __fsnotify_update_child_dentry_flags() function can take a\nsignificant amount of time. Since the bulk of this function happens\nunder inode-\u0026gt;i_lock this causes a significant contention on the lock\nwhen we remove the watch from the directory as the\n__fsnotify_update_child_dentry_flags() call from fsnotify_recalc_mask()\nraces with __fsnotify_update_child_dentry_flags() calls from\n__fsnotify_parent() happening on children. This can lead upto softlockup\nreports reported by users.\r\n\r\nFix the problem by calling fsnotify_update_children_dentry_flags() to\nset PARENT_WATCHED flags only when parent starts watching children.\r\n\r\nWhen parent stops watching children, clear false positive PARENT_WATCHED\nflags lazily in __fsnotify_parent() for each accessed child.(CVE-2024-47660)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nlib/generic-radix-tree.c: Fix rare race in __genradix_ptr_alloc()\r\n\r\nIf we need to increase the tree depth, allocate a new node, and then\nrace with another thread that increased the tree depth before us, we\u0026apos;ll\nstill have a preallocated node that might be used later.\r\n\r\nIf we then use that node for a new non-root node, it\u0026apos;ll still have a\npointer to the old root instead of being zeroed - fix this by zeroing it\nin the cmpxchg failure path.(CVE-2024-47668)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nwifi: iwlwifi: mvm: pause TCM when the firmware is stopped\r\n\r\nNot doing so will make us send a host command to the transport while the\nfirmware is not alive, which will trigger a WARNING.\r\n\r\nbad state = 0\nWARNING: CPU: 2 PID: 17434 at drivers/net/wireless/intel/iwlwifi/iwl-trans.c:115 iwl_trans_send_cmd+0x1cb/0x1e0 [iwlwifi]\nRIP: 0010:iwl_trans_send_cmd+0x1cb/0x1e0 [iwlwifi]\nCall Trace:\n \u0026lt;TASK\u0026gt;\n iwl_mvm_send_cmd+0x40/0xc0 [iwlmvm]\n iwl_mvm_config_scan+0x198/0x260 [iwlmvm]\n iwl_mvm_recalc_tcm+0x730/0x11d0 [iwlmvm]\n iwl_mvm_tcm_work+0x1d/0x30 [iwlmvm]\n process_one_work+0x29e/0x640\n worker_thread+0x2df/0x690\n ? rescuer_thread+0x540/0x540\n kthread+0x192/0x1e0\n ? set_kthread_struct+0x90/0x90\n ret_from_fork+0x22/0x30(CVE-2024-47673)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  f2fs: get rid of online repaire on corrupted directory  syzbot reports a f2fs bug as below:  kernel BUG at fs/f2fs/inode.c:896! RIP: 0010:f2fs_evict_inode+0x1598/0x15c0 fs/f2fs/inode.c:896 Call Trace:  evict+0x532/0x950 fs/inode.c:704  dispose_list fs/inode.c:747 [inline]  evict_inodes+0x5f9/0x690 fs/inode.c:797  generic_shutdown_super+0x9d/0x2d0 fs/super.c:627  kill_block_super+0x44/0x90 fs/super.c:1696  kill_f2fs_super+0x344/0x690 fs/f2fs/super.c:4898  deactivate_locked_super+0xc4/0x130 fs/super.c:473  cleanup_mnt+0x41f/0x4b0 fs/namespace.c:1373  task_work_run+0x24f/0x310 kernel/task_work.c:228  ptrace_notify+0x2d2/0x380 kernel/signal.c:2402  ptrace_report_syscall include/linux/ptrace.h:415 [inline]  ptrace_report_syscall_exit include/linux/ptrace.h:477 [inline]  syscall_exit_work+0xc6/0x190 kernel/entry/common.c:173  syscall_exit_to_user_mode_prepare kernel/entry/common.c:200 [inline]  __syscall_exit_to_user_mode_work kernel/entry/common.c:205 [inline]  syscall_exit_to_user_mode+0x279/0x370 kernel/entry/common.c:218  do_syscall_64+0x100/0x230 arch/x86/entry/common.c:89  entry_SYSCALL_64_after_hwframe+0x77/0x7f RIP: 0010:f2fs_evict_inode+0x1598/0x15c0 fs/f2fs/inode.c:896  Online repaire on corrupted directory in f2fs_lookup() can generate dirty data/meta while racing w/ readonly remount, it may leave dirty inode after filesystem becomes readonly, however, checkpoint() will skips flushing dirty inode in a state of readonly mode, result in above panic.  Let\u0026apos;s get rid of online repaire in f2fs_lookup(), and leave the work to fsck.f2fs.(CVE-2024-47690)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  f2fs: fix to avoid use-after-free in f2fs_stop_gc_thread()  syzbot reports a f2fs bug as below:   __dump_stack lib/dump_stack.c:88 [inline]  dump_stack_lvl+0x241/0x360 lib/dump_stack.c:114  print_report+0xe8/0x550 mm/kasan/report.c:491  kasan_report+0x143/0x180 mm/kasan/report.c:601  kasan_check_range+0x282/0x290 mm/kasan/generic.c:189  instrument_atomic_read_write include/linux/instrumented.h:96 [inline]  atomic_fetch_add_relaxed include/linux/atomic/atomic-instrumented.h:252 [inline]  __refcount_add include/linux/refcount.h:184 [inline]  __refcount_inc include/linux/refcount.h:241 [inline]  refcount_inc include/linux/refcount.h:258 [inline]  get_task_struct include/linux/sched/task.h:118 [inline]  kthread_stop+0xca/0x630 kernel/kthread.c:704  f2fs_stop_gc_thread+0x65/0xb0 fs/f2fs/gc.c:210  f2fs_do_shutdown+0x192/0x540 fs/f2fs/file.c:2283  f2fs_ioc_shutdown fs/f2fs/file.c:2325 [inline]  __f2fs_ioctl+0x443a/0xbe60 fs/f2fs/file.c:4325  vfs_ioctl fs/ioctl.c:51 [inline]  __do_sys_ioctl fs/ioctl.c:907 [inline]  __se_sys_ioctl+0xfc/0x170 fs/ioctl.c:893  do_syscall_x64 arch/x86/entry/common.c:52 [inline]  do_syscall_64+0xf3/0x230 arch/x86/entry/common.c:83  entry_SYSCALL_64_after_hwframe+0x77/0x7f  The root cause is below race condition, it may cause use-after-free issue in sbi-\u0026gt;gc_th pointer.  - remount  - f2fs_remount   - f2fs_stop_gc_thread    - kfree(gc_th)     - f2fs_ioc_shutdown      - f2fs_do_shutdown       - f2fs_stop_gc_thread        - kthread_stop(gc_th-\u0026gt;f2fs_gc_task)    : sbi-\u0026gt;gc_thread = NULL;  We will call f2fs_do_shutdown() in two paths: - for f2fs_ioc_shutdown() path, we should grab sb-\u0026gt;s_umount semaphore for fixing. - for f2fs_shutdown() path, it\u0026apos;s safe since caller has already grabbed sb-\u0026gt;s_umount semaphore.(CVE-2024-47691)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  IB/core: Fix ib_cache_setup_one error flow cleanup  When ib_cache_update return an error, we exit ib_cache_setup_one instantly with no proper cleanup, even though before this we had already successfully done gid_table_setup_one, that results in the kernel WARN below.  Do proper cleanup using gid_table_cleanup_one before returning the err in order to fix the issue.  WARNING: CPU: 4 PID: 922 at drivers/infiniband/core/cache.c:806 gid_table_release_one+0x181/0x1a0 Modules linked in: CPU: 4 UID: 0 PID: 922 Comm: c_repro Not tainted 6.11.0-rc1+ #3 Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS rel-1.13.0-0-gf21b5a4aeb02-prebuilt.qemu.org 04/01/2014 RIP: 0010:gid_table_release_one+0x181/0x1a0 Code: 44 8b 38 75 0c e8 2f cb 34 ff 4d 8b b5 28 05 00 00 e8 23 cb 34 ff 44 89 f9 89 da 4c 89 f6 48 c7 c7 d0 58 14 83 e8 4f de 21 ff \u0026lt;0f\u0026gt; 0b 4c 8b 75 30 e9 54 ff ff ff 48 8    3 c4 10 5b 5d 41 5c 41 5d 41 RSP: 0018:ffffc90002b835b0 EFLAGS: 00010286 RAX: 0000000000000000 RBX: 0000000000000000 RCX: ffffffff811c8527 RDX: 0000000000000000 RSI: ffffffff811c8534 RDI: 0000000000000001 RBP: ffff8881011b3d00 R08: ffff88810b3abe00 R09: 205d303839303631 R10: 666572207972746e R11: 72746e6520444947 R12: 0000000000000001 R13: ffff888106390000 R14: ffff8881011f2110 R15: 0000000000000001 FS:  00007fecc3b70800(0000) GS:ffff88813bd00000(0000) knlGS:0000000000000000 CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 0000000020000340 CR3: 000000010435a001 CR4: 00000000003706b0 DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400 Call Trace:  \u0026lt;TASK\u0026gt;  ? show_regs+0x94/0xa0  ? __warn+0x9e/0x1c0  ? gid_table_release_one+0x181/0x1a0  ? report_bug+0x1f9/0x340  ? gid_table_release_one+0x181/0x1a0  ? handle_bug+0xa2/0x110  ? exc_invalid_op+0x31/0xa0  ? asm_exc_invalid_op+0x16/0x20  ? __warn_printk+0xc7/0x180  ? __warn_printk+0xd4/0x180  ? gid_table_release_one+0x181/0x1a0  ib_device_release+0x71/0xe0  ? __pfx_ib_device_release+0x10/0x10  device_release+0x44/0xd0  kobject_put+0x135/0x3d0  put_device+0x20/0x30  rxe_net_add+0x7d/0xa0  rxe_newlink+0xd7/0x190  nldev_newlink+0x1b0/0x2a0  ? __pfx_nldev_newlink+0x10/0x10  rdma_nl_rcv_msg+0x1ad/0x2e0  rdma_nl_rcv_skb.constprop.0+0x176/0x210  netlink_unicast+0x2de/0x400  netlink_sendmsg+0x306/0x660  __sock_sendmsg+0x110/0x120  ____sys_sendmsg+0x30e/0x390  ___sys_sendmsg+0x9b/0xf0  ? kstrtouint+0x6e/0xa0  ? kstrtouint_from_user+0x7c/0xb0  ? get_pid_task+0xb0/0xd0  ? proc_fail_nth_write+0x5b/0x140  ? __fget_light+0x9a/0x200  ? preempt_count_add+0x47/0xa0  __sys_sendmsg+0x61/0xd0  do_syscall_64+0x50/0x110  entry_SYSCALL_64_after_hwframe+0x76/0x7e(CVE-2024-47693)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  RDMA/iwcm: Fix WARNING:at_kernel/workqueue.c:#check_flush_dependency  In the commit aee2424246f9 (\u0026quot;RDMA/iwcm: Fix a use-after-free related to destroying CM IDs\u0026quot;), the function flush_workqueue is invoked to flush the work queue iwcm_wq.  But at that time, the work queue iwcm_wq was created via the function alloc_ordered_workqueue without the flag WQ_MEM_RECLAIM.  Because the current process is trying to flush the whole iwcm_wq, if iwcm_wq doesn\u0026apos;t have the flag WQ_MEM_RECLAIM, verify that the current process is not reclaiming memory or running on a workqueue which doesn\u0026apos;t have the flag WQ_MEM_RECLAIM as that can break forward-progress guarantee leading to a deadlock.  The call trace is as below:  [  125.350876][ T1430] Call Trace: [  125.356281][ T1430]  \u0026lt;TASK\u0026gt; [ 125.361285][ T1430] ? __warn (kernel/panic.c:693) [ 125.367640][ T1430] ? check_flush_dependency (kernel/workqueue.c:3706 (discriminator 9)) [ 125.375689][ T1430] ? report_bug (lib/bug.c:180 lib/bug.c:219) [ 125.382505][ T1430] ? handle_bug (arch/x86/kernel/traps.c:239) [ 125.388987][ T1430] ? exc_invalid_op (arch/x86/kernel/traps.c:260 (discriminator 1)) [ 125.395831][ T1430] ? asm_exc_invalid_op (arch/x86/include/asm/idtentry.h:621) [ 125.403125][ T1430] ? check_flush_dependency (kernel/workqueue.c:3706 (discriminator 9)) [ 125.410984][ T1430] ? check_flush_dependency (kernel/workqueue.c:3706 (discriminator 9)) [ 125.418764][ T1430] __flush_workqueue (kernel/workqueue.c:3970) [ 125.426021][ T1430] ? __pfx___might_resched (kernel/sched/core.c:10151) [ 125.433431][ T1430] ? destroy_cm_id (drivers/infiniband/core/iwcm.c:375) iw_cm [ 125.441209][ T1430] ? __pfx___flush_workqueue (kernel/workqueue.c:3910) [ 125.473900][ T1430] ? _raw_spin_lock_irqsave (arch/x86/include/asm/atomic.h:107 include/linux/atomic/atomic-arch-fallback.h:2170 include/linux/atomic/atomic-instrumented.h:1302 include/asm-generic/qspinlock.h:111 include/linux/spinlock.h:187 include/linux/spinlock_api_smp.h:111 kernel/locking/spinlock.c:162) [ 125.473909][ T1430] ? __pfx__raw_spin_lock_irqsave (kernel/locking/spinlock.c:161) [ 125.482537][ T1430] _destroy_id (drivers/infiniband/core/cma.c:2044) rdma_cm [ 125.495072][ T1430] nvme_rdma_free_queue (drivers/nvme/host/rdma.c:656 drivers/nvme/host/rdma.c:650) nvme_rdma [ 125.505827][ T1430] nvme_rdma_reset_ctrl_work (drivers/nvme/host/rdma.c:2180) nvme_rdma [ 125.505831][ T1430] process_one_work (kernel/workqueue.c:3231) [ 125.515122][ T1430] worker_thread (kernel/workqueue.c:3306 kernel/workqueue.c:3393) [ 125.515127][ T1430] ? __pfx_worker_thread (kernel/workqueue.c:3339) [ 125.531837][ T1430] kthread (kernel/kthread.c:389) [ 125.539864][ T1430] ? __pfx_kthread (kernel/kthread.c:342) [ 125.550628][ T1430] ret_from_fork (arch/x86/kernel/process.c:147) [ 125.558840][ T1430] ? __pfx_kthread (kernel/kthread.c:342) [ 125.558844][ T1430] ret_from_fork_asm (arch/x86/entry/entry_64.S:257) [  125.566487][ T1430]  \u0026lt;/TASK\u0026gt; [  125.566488][ T1430] ---[ end trace 0000000000000000 ]---(CVE-2024-47696)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  nilfs2: fix potential null-ptr-deref in nilfs_btree_insert()  Patch series \u0026quot;nilfs2: fix potential issues with empty b-tree nodes\u0026quot;.  This series addresses three potential issues with empty b-tree nodes that can occur with corrupted filesystem images, including one recently discovered by syzbot.   This patch (of 3):  If a b-tree is broken on the device, and the b-tree height is greater than 2 (the level of the root node is greater than 1) even if the number of child nodes of the b-tree root is 0, a NULL pointer dereference occurs in nilfs_btree_prepare_insert(), which is called from nilfs_btree_insert().  This is because, when the number of child nodes of the b-tree root is 0, nilfs_btree_do_lookup() does not set the block buffer head in any of path[x].bp_bh, leaving it as the initial value of NULL, but if the level of the b-tree root node is greater than 1, nilfs_btree_get_nonroot_node(), which accesses the buffer memory of path[x].bp_bh, is called.  Fix this issue by adding a check to nilfs_btree_root_broken(), which performs sanity checks when reading the root node from the device, to detect this inconsistency.  Thanks to Lizhi Xu for trying to solve the bug and clarifying the cause early on.(CVE-2024-47699)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  ext4: avoid OOB when system.data xattr changes underneath the filesystem  When looking up for an entry in an inlined directory, if e_value_offs is changed underneath the filesystem by some change in the block device, it will lead to an out-of-bounds access that KASAN detects as an UAF.  EXT4-fs (loop0): mounted filesystem 00000000-0000-0000-0000-000000000000 r/w without journal. Quota mode: none. loop0: detected capacity change from 2048 to 2047 ================================================================== BUG: KASAN: use-after-free in ext4_search_dir+0xf2/0x1c0 fs/ext4/namei.c:1500 Read of size 1 at addr ffff88803e91130f by task syz-executor269/5103  CPU: 0 UID: 0 PID: 5103 Comm: syz-executor269 Not tainted 6.11.0-rc4-syzkaller #0 Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.16.3-debian-1.16.3-2~bpo12+1 04/01/2014 Call Trace:  \u0026lt;TASK\u0026gt;  __dump_stack lib/dump_stack.c:93 [inline]  dump_stack_lvl+0x241/0x360 lib/dump_stack.c:119  print_address_description mm/kasan/report.c:377 [inline]  print_report+0x169/0x550 mm/kasan/report.c:488  kasan_report+0x143/0x180 mm/kasan/report.c:601  ext4_search_dir+0xf2/0x1c0 fs/ext4/namei.c:1500  ext4_find_inline_entry+0x4be/0x5e0 fs/ext4/inline.c:1697  __ext4_find_entry+0x2b4/0x1b30 fs/ext4/namei.c:1573  ext4_lookup_entry fs/ext4/namei.c:1727 [inline]  ext4_lookup+0x15f/0x750 fs/ext4/namei.c:1795  lookup_one_qstr_excl+0x11f/0x260 fs/namei.c:1633  filename_create+0x297/0x540 fs/namei.c:3980  do_symlinkat+0xf9/0x3a0 fs/namei.c:4587  __do_sys_symlinkat fs/namei.c:4610 [inline]  __se_sys_symlinkat fs/namei.c:4607 [inline]  __x64_sys_symlinkat+0x95/0xb0 fs/namei.c:4607  do_syscall_x64 arch/x86/entry/common.c:52 [inline]  do_syscall_64+0xf3/0x230 arch/x86/entry/common.c:83  entry_SYSCALL_64_after_hwframe+0x77/0x7f RIP: 0033:0x7f3e73ced469 Code: 28 00 00 00 75 05 48 83 c4 28 c3 e8 21 18 00 00 90 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 \u0026lt;48\u0026gt; 3d 01 f0 ff ff 73 01 c3 48 c7 c1 b8 ff ff ff f7 d8 64 89 01 48 RSP: 002b:00007fff4d40c258 EFLAGS: 00000246 ORIG_RAX: 000000000000010a RAX: ffffffffffffffda RBX: 0032656c69662f2e RCX: 00007f3e73ced469 RDX: 0000000020000200 RSI: 00000000ffffff9c RDI: 00000000200001c0 RBP: 0000000000000000 R08: 00007fff4d40c290 R09: 00007fff4d40c290 R10: 0023706f6f6c2f76 R11: 0000000000000246 R12: 00007fff4d40c27c R13: 0000000000000003 R14: 431bde82d7b634db R15: 00007fff4d40c2b0  \u0026lt;/TASK\u0026gt;  Calling ext4_xattr_ibody_find right after reading the inode with ext4_get_inode_loc will lead to a check of the validity of the xattrs, avoiding this problem.(CVE-2024-47701)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  bpf, lsm: Add check for BPF LSM return value  A bpf prog returning a positive number attached to file_alloc_security hook makes kernel panic.  This happens because file system can not filter out the positive number returned by the LSM prog using IS_ERR, and misinterprets this positive number as a file pointer.  Given that hook file_alloc_security never returned positive number before the introduction of BPF LSM, and other BPF LSM hooks may encounter similar issues, this patch adds LSM return value check in verifier, to ensure no unexpected value is returned.(CVE-2024-47703)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  block: fix potential invalid pointer dereference in blk_add_partition  The blk_add_partition() function initially used a single if-condition (IS_ERR(part)) to check for errors when adding a partition. This was modified to handle the specific case of -ENXIO separately, allowing the function to proceed without logging the error in this case. However, this change unintentionally left a path where md_autodetect_dev() could be called without confirming that part is a valid pointer.  This commit separates the error handling logic by splitting the initial if-condition, improving code readability and handling specific error scenarios explicitly. The function now distinguishes the general error case from -ENXIO without altering the existing behavior of md_autodetect_dev() calls.(CVE-2024-47705)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  jfs: fix out-of-bounds in dbNextAG() and diAlloc()  In dbNextAG() , there is no check for the case where bmp-\u0026gt;db_numag is greater or same than MAXAG due to a polluted image, which causes an out-of-bounds. Therefore, a bounds check should be added in dbMount().  And in dbNextAG(), a check for the case where agpref is greater than bmp-\u0026gt;db_numag should be added, so an out-of-bounds exception should be prevented.  Additionally, a check for the case where agno is greater or same than MAXAG should be added in diAlloc() to prevent out-of-bounds.(CVE-2024-47723)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  f2fs: fix to wait dio completion  It should wait all existing dio write IOs before block removal, otherwise, previous direct write IO may overwrite data in the block which may be reused by other inode.(CVE-2024-47726)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  padata: use integer wrap around to prevent deadlock on seq_nr overflow  When submitting more than 2^32 padata objects to padata_do_serial, the current sorting implementation incorrectly sorts padata objects with overflowed seq_nr, causing them to be placed before existing objects in the reorder list. This leads to a deadlock in the serialization process as padata_find_next cannot match padata-\u0026gt;seq_nr and pd-\u0026gt;processed because the padata instance with overflowed seq_nr will be selected next.  To fix this, we use an unsigned integer wrap around to correctly sort padata objects in scenarios with integer overflow.(CVE-2024-47739)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  firmware_loader: Block path traversal  Most firmware names are hardcoded strings, or are constructed from fairly constrained format strings where the dynamic parts are just some hex numbers or such.  However, there are a couple codepaths in the kernel where firmware file names contain string components that are passed through from a device or semi-privileged userspace; the ones I could find (not counting interfaces that require root privileges) are:   - lpfc_sli4_request_firmware_update() seems to construct the firmware    filename from \u0026quot;ModelName\u0026quot;, a string that was previously parsed out of    some descriptor (\u0026quot;Vital Product Data\u0026quot;) in lpfc_fill_vpd()  - nfp_net_fw_find() seems to construct a firmware filename from a model    name coming from nfp_hwinfo_lookup(pf-\u0026gt;hwinfo, \u0026quot;nffw.partno\u0026quot;), which I    think parses some descriptor that was read from the device.    (But this case likely isn\u0026apos;t exploitable because the format string looks    like \u0026quot;netronome/nic_%s\u0026quot;, and there shouldn\u0026apos;t be any *folders* starting    with \u0026quot;netronome/nic_\u0026quot;. The previous case was different because there,    the \u0026quot;%s\u0026quot; is *at the start* of the format string.)  - module_flash_fw_schedule() is reachable from the    ETHTOOL_MSG_MODULE_FW_FLASH_ACT netlink command, which is marked as    GENL_UNS_ADMIN_PERM (meaning CAP_NET_ADMIN inside a user namespace is    enough to pass the privilege check), and takes a userspace-provided    firmware name.    (But I think to reach this case, you need to have CAP_NET_ADMIN over a    network namespace that a special kind of ethernet device is mapped into,    so I think this is not a viable attack path in practice.)  Fix it by rejecting any firmware names containing \u0026quot;..\u0026quot; path components.  For what it\u0026apos;s worth, I went looking and haven\u0026apos;t found any USB device drivers that use the firmware loader dangerously.(CVE-2024-47742)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  vhost_vdpa: assign irq bypass producer token correctly  We used to call irq_bypass_unregister_producer() in vhost_vdpa_setup_vq_irq() which is problematic as we don\u0026apos;t know if the token pointer is still valid or not.  Actually, we use the eventfd_ctx as the token so the life cycle of the token should be bound to the VHOST_SET_VRING_CALL instead of vhost_vdpa_setup_vq_irq() which could be called by set_status().  Fixing this by setting up irq bypass producer\u0026apos;s token when handling VHOST_SET_VRING_CALL and un-registering the producer before calling vhost_vring_ioctl() to prevent a possible use after free as eventfd could have been released in vhost_vring_ioctl(). And such registering and unregistering will only be done if DRIVER_OK is set.(CVE-2024-47748)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  PCI: keystone: Fix if-statement expression in ks_pcie_quirk()  This code accidentally uses \u0026amp;\u0026amp; where || was intended.  It potentially results in a NULL dereference.  Thus, fix the if-statement expression to use the correct condition.  [kwilczynski: commit log](CVE-2024-47756)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  nbd: fix race between timeout and normal completion  If request timetout is handled by nbd_requeue_cmd(), normal completion has to be stopped for avoiding to complete this requeued request, other use-after-free can be triggered.  Fix the race by clearing NBD_CMD_INFLIGHT in nbd_requeue_cmd(), meantime make sure that cmd-\u0026gt;lock is grabbed for clearing the flag and the requeue.(CVE-2024-49855)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  efistub/tpm: Use ACPI reclaim memory for event log to avoid corruption  The TPM event log table is a Linux specific construct, where the data produced by the GetEventLog() boot service is cached in memory, and passed on to the OS using an EFI configuration table.  The use of EFI_LOADER_DATA here results in the region being left unreserved in the E820 memory map constructed by the EFI stub, and this is the memory description that is passed on to the incoming kernel by kexec, which is therefore unaware that the region should be reserved.  Even though the utility of the TPM2 event log after a kexec is questionable, any corruption might send the parsing code off into the weeds and crash the kernel. So let\u0026apos;s use EFI_ACPI_RECLAIM_MEMORY instead, which is always treated as reserved by the E820 conversion logic.(CVE-2024-49858)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  f2fs: fix to check atomic_file in f2fs ioctl interfaces  Some f2fs ioctl interfaces like f2fs_ioc_set_pin_file(), f2fs_move_file_range(), and f2fs_defragment_range() missed to check atomic_write status, which may cause potential race issue, fix it.(CVE-2024-49859)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  ACPI: sysfs: validate return type of _STR method  Only buffer objects are valid return values of _STR.  If something else is returned description_show() will access invalid memory.(CVE-2024-49860)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  powercap: intel_rapl: Fix off by one in get_rpi()  The rp-\u0026gt;priv-\u0026gt;rpi array is either rpi_msr or rpi_tpmi which have NR_RAPL_PRIMITIVES number of elements.  Thus the \u0026gt; needs to be \u0026gt;= to prevent an off by one access.(CVE-2024-49862)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  ocfs2: fix possible null-ptr-deref in ocfs2_set_buffer_uptodate  When doing cleanup, if flags without OCFS2_BH_READAHEAD, it may trigger NULL pointer dereference in the following ocfs2_set_buffer_uptodate() if bh is NULL.(CVE-2024-49877)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  drm: omapdrm: Add missing check for alloc_ordered_workqueue  As it may return NULL pointer and cause NULL pointer dereference. Add check for the return value of alloc_ordered_workqueue.(CVE-2024-49879)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  ext4: update orig_path in ext4_find_extent()  In ext4_find_extent(), if the path is not big enough, we free it and set *orig_path to NULL. But after reallocating and successfully initializing the path, we don\u0026apos;t update *orig_path, in which case the caller gets a valid path but a NULL ppath, and this may cause a NULL pointer dereference or a path memory leak. For example:  ext4_split_extent   path = *ppath = 2000   ext4_find_extent     if (depth \u0026gt; path[0].p_maxdepth)       kfree(path = 2000);       *orig_path = path = NULL;       path = kcalloc() = 3000   ext4_split_extent_at(*ppath = NULL)     path = *ppath;     ex = path[depth].p_ext;     // NULL pointer dereference!  ================================================================== BUG: kernel NULL pointer dereference, address: 0000000000000010 CPU: 6 UID: 0 PID: 576 Comm: fsstress Not tainted 6.11.0-rc2-dirty #847 RIP: 0010:ext4_split_extent_at+0x6d/0x560 Call Trace:  \u0026lt;TASK\u0026gt;  ext4_split_extent.isra.0+0xcb/0x1b0  ext4_ext_convert_to_initialized+0x168/0x6c0  ext4_ext_handle_unwritten_extents+0x325/0x4d0  ext4_ext_map_blocks+0x520/0xdb0  ext4_map_blocks+0x2b0/0x690  ext4_iomap_begin+0x20e/0x2c0 [...] ==================================================================  Therefore, *orig_path is updated when the extent lookup succeeds, so that the caller can safely use path or *ppath.(CVE-2024-49881)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  ext4: fix double brelse() the buffer of the extents path  In ext4_ext_try_to_merge_up(), set path[1].p_bh to NULL after it has been released, otherwise it may be released twice. An example of what triggers this is as follows:    split2    map    split1 |--------|-------|--------|  ext4_ext_map_blocks  ext4_ext_handle_unwritten_extents   ext4_split_convert_extents    // path-\u0026gt;p_depth == 0    ext4_split_extent      // 1. do split1      ext4_split_extent_at        |ext4_ext_insert_extent        |  ext4_ext_create_new_leaf        |    ext4_ext_grow_indepth        |      le16_add_cpu(\u0026amp;neh-\u0026gt;eh_depth, 1)        |    ext4_find_extent        |      // return -ENOMEM        |// get error and try zeroout        |path = ext4_find_extent        |  path-\u0026gt;p_depth = 1        |ext4_ext_try_to_merge        |  ext4_ext_try_to_merge_up        |    path-\u0026gt;p_depth = 0        |    brelse(path[1].p_bh)  ---\u0026gt; not set to NULL here        |// zeroout success      // 2. update path      ext4_find_extent      // 3. do split2      ext4_split_extent_at        ext4_ext_insert_extent          ext4_ext_create_new_leaf            ext4_ext_grow_indepth              le16_add_cpu(\u0026amp;neh-\u0026gt;eh_depth, 1)            ext4_find_extent              path[0].p_bh = NULL;              path-\u0026gt;p_depth = 1              read_extent_tree_block  ---\u0026gt; return err              // path[1].p_bh is still the old value              ext4_free_ext_path                ext4_ext_drop_refs                  // path-\u0026gt;p_depth == 1                  brelse(path[1].p_bh)  ---\u0026gt; brelse a buffer twice  Finally got the following WARRNING when removing the buffer from lru:  ============================================ VFS: brelse: Trying to free free buffer WARNING: CPU: 2 PID: 72 at fs/buffer.c:1241 __brelse+0x58/0x90 CPU: 2 PID: 72 Comm: kworker/u19:1 Not tainted 6.9.0-dirty #716 RIP: 0010:__brelse+0x58/0x90 Call Trace:  \u0026lt;TASK\u0026gt;  __find_get_block+0x6e7/0x810  bdev_getblk+0x2b/0x480  __ext4_get_inode_loc+0x48a/0x1240  ext4_get_inode_loc+0xb2/0x150  ext4_reserve_inode_write+0xb7/0x230  __ext4_mark_inode_dirty+0x144/0x6a0  ext4_ext_insert_extent+0x9c8/0x3230  ext4_ext_map_blocks+0xf45/0x2dc0  ext4_map_blocks+0x724/0x1700  ext4_do_writepages+0x12d6/0x2a70 [...] ============================================(CVE-2024-49882)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  ext4: aovid use-after-free in ext4_ext_insert_extent()  As Ojaswin mentioned in Link, in ext4_ext_insert_extent(), if the path is reallocated in ext4_ext_create_new_leaf(), we\u0026apos;ll use the stale path and cause UAF. Below is a sample trace with dummy values:  ext4_ext_insert_extent   path = *ppath = 2000   ext4_ext_create_new_leaf(ppath)     ext4_find_extent(ppath)       path = *ppath = 2000       if (depth \u0026gt; path[0].p_maxdepth)             kfree(path = 2000);             *ppath = path = NULL;       path = kcalloc() = 3000       *ppath = 3000;       return path;   /* here path is still 2000, UAF! */   eh = path[depth].p_hdr  ================================================================== BUG: KASAN: slab-use-after-free in ext4_ext_insert_extent+0x26d4/0x3330 Read of size 8 at addr ffff8881027bf7d0 by task kworker/u36:1/179 CPU: 3 UID: 0 PID: 179 Comm: kworker/u6:1 Not tainted 6.11.0-rc2-dirty #866 Call Trace:  \u0026lt;TASK\u0026gt;  ext4_ext_insert_extent+0x26d4/0x3330  ext4_ext_map_blocks+0xe22/0x2d40  ext4_map_blocks+0x71e/0x1700  ext4_do_writepages+0x1290/0x2800 [...]  Allocated by task 179:  ext4_find_extent+0x81c/0x1f70  ext4_ext_map_blocks+0x146/0x2d40  ext4_map_blocks+0x71e/0x1700  ext4_do_writepages+0x1290/0x2800  ext4_writepages+0x26d/0x4e0  do_writepages+0x175/0x700 [...]  Freed by task 179:  kfree+0xcb/0x240  ext4_find_extent+0x7c0/0x1f70  ext4_ext_insert_extent+0xa26/0x3330  ext4_ext_map_blocks+0xe22/0x2d40  ext4_map_blocks+0x71e/0x1700  ext4_do_writepages+0x1290/0x2800  ext4_writepages+0x26d/0x4e0  do_writepages+0x175/0x700 [...] ==================================================================  So use *ppath to update the path to avoid the above problem.(CVE-2024-49883)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  ext4: fix slab-use-after-free in ext4_split_extent_at()  We hit the following use-after-free:  ================================================================== BUG: KASAN: slab-use-after-free in ext4_split_extent_at+0xba8/0xcc0 Read of size 2 at addr ffff88810548ed08 by task kworker/u20:0/40 CPU: 0 PID: 40 Comm: kworker/u20:0 Not tainted 6.9.0-dirty #724 Call Trace:  \u0026lt;TASK\u0026gt;  kasan_report+0x93/0xc0  ext4_split_extent_at+0xba8/0xcc0  ext4_split_extent.isra.0+0x18f/0x500  ext4_split_convert_extents+0x275/0x750  ext4_ext_handle_unwritten_extents+0x73e/0x1580  ext4_ext_map_blocks+0xe20/0x2dc0  ext4_map_blocks+0x724/0x1700  ext4_do_writepages+0x12d6/0x2a70 [...]  Allocated by task 40:  __kmalloc_noprof+0x1ac/0x480  ext4_find_extent+0xf3b/0x1e70  ext4_ext_map_blocks+0x188/0x2dc0  ext4_map_blocks+0x724/0x1700  ext4_do_writepages+0x12d6/0x2a70 [...]  Freed by task 40:  kfree+0xf1/0x2b0  ext4_find_extent+0xa71/0x1e70  ext4_ext_insert_extent+0xa22/0x3260  ext4_split_extent_at+0x3ef/0xcc0  ext4_split_extent.isra.0+0x18f/0x500  ext4_split_convert_extents+0x275/0x750  ext4_ext_handle_unwritten_extents+0x73e/0x1580  ext4_ext_map_blocks+0xe20/0x2dc0  ext4_map_blocks+0x724/0x1700  ext4_do_writepages+0x12d6/0x2a70 [...] ==================================================================  The flow of issue triggering is as follows:  ext4_split_extent_at   path = *ppath   ext4_ext_insert_extent(ppath)     ext4_ext_create_new_leaf(ppath)       ext4_find_extent(orig_path)         path = *orig_path         read_extent_tree_block           // return -ENOMEM or -EIO         ext4_free_ext_path(path)           kfree(path)         *orig_path = NULL   a. If err is -ENOMEM:   ext4_ext_dirty(path + path-\u0026gt;p_depth)   // path use-after-free !!!   b. If err is -EIO and we have EXT_DEBUG defined:   ext4_ext_show_leaf(path)     eh = path[depth].p_hdr     // path also use-after-free !!!  So when trying to zeroout or fix the extent length, call ext4_find_extent() to update the path.  In addition we use *ppath directly as an ext4_ext_show_leaf() input to avoid possible use-after-free when EXT_DEBUG is defined, and to avoid unnecessary path updates.(CVE-2024-49884)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  platform/x86: ISST: Fix the KASAN report slab-out-of-bounds bug  Attaching SST PCI device to VM causes \u0026quot;BUG: KASAN: slab-out-of-bounds\u0026quot;. kasan report: [   19.411889] ================================================================== [   19.413702] BUG: KASAN: slab-out-of-bounds in _isst_if_get_pci_dev+0x3d5/0x400 [isst_if_common] [   19.415634] Read of size 8 at addr ffff888829e65200 by task cpuhp/16/113 [   19.417368] [   19.418627] CPU: 16 PID: 113 Comm: cpuhp/16 Tainted: G            E      6.9.0 #10 [   19.420435] Hardware name: VMware, Inc. VMware20,1/440BX Desktop Reference Platform, BIOS VMW201.00V.20192059.B64.2207280713 07/28/2022 [   19.422687] Call Trace: [   19.424091]  \u0026lt;TASK\u0026gt; [   19.425448]  dump_stack_lvl+0x5d/0x80 [   19.426963]  ? _isst_if_get_pci_dev+0x3d5/0x400 [isst_if_common] [   19.428694]  print_report+0x19d/0x52e [   19.430206]  ? __pfx__raw_spin_lock_irqsave+0x10/0x10 [   19.431837]  ? _isst_if_get_pci_dev+0x3d5/0x400 [isst_if_common] [   19.433539]  kasan_report+0xf0/0x170 [   19.435019]  ? _isst_if_get_pci_dev+0x3d5/0x400 [isst_if_common] [   19.436709]  _isst_if_get_pci_dev+0x3d5/0x400 [isst_if_common] [   19.438379]  ? __pfx_sched_clock_cpu+0x10/0x10 [   19.439910]  isst_if_cpu_online+0x406/0x58f [isst_if_common] [   19.441573]  ? __pfx_isst_if_cpu_online+0x10/0x10 [isst_if_common] [   19.443263]  ? ttwu_queue_wakelist+0x2c1/0x360 [   19.444797]  cpuhp_invoke_callback+0x221/0xec0 [   19.446337]  cpuhp_thread_fun+0x21b/0x610 [   19.447814]  ? __pfx_cpuhp_thread_fun+0x10/0x10 [   19.449354]  smpboot_thread_fn+0x2e7/0x6e0 [   19.450859]  ? __pfx_smpboot_thread_fn+0x10/0x10 [   19.452405]  kthread+0x29c/0x350 [   19.453817]  ? __pfx_kthread+0x10/0x10 [   19.455253]  ret_from_fork+0x31/0x70 [   19.456685]  ? __pfx_kthread+0x10/0x10 [   19.458114]  ret_from_fork_asm+0x1a/0x30 [   19.459573]  \u0026lt;/TASK\u0026gt; [   19.460853] [   19.462055] Allocated by task 1198: [   19.463410]  kasan_save_stack+0x30/0x50 [   19.464788]  kasan_save_track+0x14/0x30 [   19.466139]  __kasan_kmalloc+0xaa/0xb0 [   19.467465]  __kmalloc+0x1cd/0x470 [   19.468748]  isst_if_cdev_register+0x1da/0x350 [isst_if_common] [   19.470233]  isst_if_mbox_init+0x108/0xff0 [isst_if_mbox_msr] [   19.471670]  do_one_initcall+0xa4/0x380 [   19.472903]  do_init_module+0x238/0x760 [   19.474105]  load_module+0x5239/0x6f00 [   19.475285]  init_module_from_file+0xd1/0x130 [   19.476506]  idempotent_init_module+0x23b/0x650 [   19.477725]  __x64_sys_finit_module+0xbe/0x130 [   19.476506]  idempotent_init_module+0x23b/0x650 [   19.477725]  __x64_sys_finit_module+0xbe/0x130 [   19.478920]  do_syscall_64+0x82/0x160 [   19.480036]  entry_SYSCALL_64_after_hwframe+0x76/0x7e [   19.481292] [   19.482205] The buggy address belongs to the object at ffff888829e65000  which belongs to the cache kmalloc-512 of size 512 [   19.484818] The buggy address is located 0 bytes to the right of  allocated 512-byte region [ffff888829e65000, ffff888829e65200) [   19.487447] [   19.488328] The buggy address belongs to the physical page: [   19.489569] page: refcount:1 mapcount:0 mapping:0000000000000000 index:0xffff888829e60c00 pfn:0x829e60 [   19.491140] head: order:3 entire_mapcount:0 nr_pages_mapped:0 pincount:0 [   19.492466] anon flags: 0x57ffffc0000840(slab|head|node=1|zone=2|lastcpupid=0x1fffff) [   19.493914] page_type: 0xffffffff() [   19.494988] raw: 0057ffffc0000840 ffff88810004cc80 0000000000000000 0000000000000001 [   19.496451] raw: ffff888829e60c00 0000000080200018 00000001ffffffff 0000000000000000 [   19.497906] head: 0057ffffc0000840 ffff88810004cc80 0000000000000000 0000000000000001 [   19.499379] head: ffff888829e60c00 0000000080200018 00000001ffffffff 0000000000000000 [   19.500844] head: 0057ffffc0000003 ffffea0020a79801 ffffea0020a79848 00000000ffffffff [   19.502316] head: 0000000800000000 0000000000000000 00000000ffffffff 0000000000000000 [   19.503784] page dumped because: k ---truncated---(CVE-2024-49886)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  ext4: avoid use-after-free in ext4_ext_show_leaf()  In ext4_find_extent(), path may be freed by error or be reallocated, so using a previously saved *ppath may have been freed and thus may trigger use-after-free, as follows:  ext4_split_extent   path = *ppath;   ext4_split_extent_at(ppath)   path = ext4_find_extent(ppath)   ext4_split_extent_at(ppath)     // ext4_find_extent fails to free path     // but zeroout succeeds   ext4_ext_show_leaf(inode, path)     eh = path[depth].p_hdr     // path use-after-free !!!  Similar to ext4_split_extent_at(), we use *ppath directly as an input to ext4_ext_show_leaf(). Fix a spelling error by the way.  Same problem in ext4_ext_handle_unwritten_extents(). Since \u0026apos;path\u0026apos; is only used in ext4_ext_show_leaf(), remove \u0026apos;path\u0026apos; and use *ppath directly.  This issue is triggered only when EXT_DEBUG is defined and therefore does not affect functionality.(CVE-2024-49889)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  drm/amd/display: Check stream before comparing them  [WHAT \u0026amp; HOW] amdgpu_dm can pass a null stream to dc_is_stream_unchanged. It is necessary to check for null before dereferencing them.  This fixes 1 FORWARD_NULL issue reported by Coverity.(CVE-2024-49896)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  drm/amd/display: Add null check for top_pipe_to_program in commit_planes_for_stream  This commit addresses a null pointer dereference issue in the `commit_planes_for_stream` function at line 4140. The issue could occur when `top_pipe_to_program` is null.  The fix adds a check to ensure `top_pipe_to_program` is not null before accessing its stream_res. This prevents a null pointer dereference.  Reported by smatch: drivers/gpu/drm/amd/amdgpu/../display/dc/core/dc.c:4140 commit_planes_for_stream() error: we previously assumed \u0026apos;top_pipe_to_program\u0026apos; could be null (see line 3906)(CVE-2024-49913)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  drm/amd/display: Add NULL check for clk_mgr and clk_mgr-\u0026gt;funcs in dcn30_init_hw  This commit addresses a potential null pointer dereference issue in the `dcn30_init_hw` function. The issue could occur when `dc-\u0026gt;clk_mgr` or `dc-\u0026gt;clk_mgr-\u0026gt;funcs` is null.  The fix adds a check to ensure `dc-\u0026gt;clk_mgr` and `dc-\u0026gt;clk_mgr-\u0026gt;funcs` is not null before accessing its functions. This prevents a potential null pointer dereference.  Reported by smatch: drivers/gpu/drm/amd/amdgpu/../display/dc/hwss/dcn30/dcn30_hwseq.c:789 dcn30_init_hw() error: we previously assumed \u0026apos;dc-\u0026gt;clk_mgr\u0026apos; could be null (see line 628)(CVE-2024-49917)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  drm/amd/display: Check null pointers before using them  [WHAT \u0026amp; HOW] These pointers are null checked previously in the same function, indicating they might be null as reported by Coverity. As a result, they need to be checked when used again.  This fixes 3 FORWARD_NULL issue reported by Coverity.(CVE-2024-49922)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  fbdev: pxafb: Fix possible use after free in pxafb_task()  In the pxafb_probe function, it calls the pxafb_init_fbinfo function, after which \u0026amp;fbi-\u0026gt;task is associated with pxafb_task. Moreover, within this pxafb_init_fbinfo function, the pxafb_blank function within the \u0026amp;pxafb_ops struct is capable of scheduling work.  If we remove the module which will call pxafb_remove to make cleanup, it will call unregister_framebuffer function which can call do_unregister_framebuffer to free fbi-\u0026gt;fb through put_fb_info(fb_info), while the work mentioned above will be used. The sequence of operations that may lead to a UAF bug is as follows:  CPU0                                                CPU1                                     | pxafb_task pxafb_remove                       | unregister_framebuffer(info)       | do_unregister_framebuffer(fb_info) | put_fb_info(fb_info)               | // free fbi-\u0026gt;fb                    | set_ctrlr_state(fbi, state)                                    | __pxafb_lcd_power(fbi, 0)                                    | fbi-\u0026gt;lcd_power(on, \u0026amp;fbi-\u0026gt;fb.var)                                    | //use fbi-\u0026gt;fb  Fix it by ensuring that the work is canceled before proceeding with the cleanup in pxafb_remove.  Note that only root user can remove the driver at runtime.(CVE-2024-49924)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  blk_iocost: fix more out of bound shifts  Recently running UBSAN caught few out of bound shifts in the ioc_forgive_debts() function:  UBSAN: shift-out-of-bounds in block/blk-iocost.c:2142:38 shift exponent 80 is too large for 64-bit type \u0026apos;u64\u0026apos; (aka \u0026apos;unsigned long long\u0026apos;) ... UBSAN: shift-out-of-bounds in block/blk-iocost.c:2144:30 shift exponent 80 is too large for 64-bit type \u0026apos;u64\u0026apos; (aka \u0026apos;unsigned long long\u0026apos;) ... Call Trace: \u0026lt;IRQ\u0026gt; dump_stack_lvl+0xca/0x130 __ubsan_handle_shift_out_of_bounds+0x22c/0x280 ? __lock_acquire+0x6441/0x7c10 ioc_timer_fn+0x6cec/0x7750 ? blk_iocost_init+0x720/0x720 ? call_timer_fn+0x5d/0x470 call_timer_fn+0xfa/0x470 ? blk_iocost_init+0x720/0x720 __run_timer_base+0x519/0x700 ...  Actual impact of this issue was not identified but I propose to fix the undefined behaviour. The proposed fix to prevent those out of bound shifts consist of precalculating exponent before using it the shift operations by taking min value from the actual exponent and maximum possible number of bits.(CVE-2024-49933)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  fs/inode: Prevent dump_mapping() accessing invalid dentry.d_name.name  It\u0026apos;s observed that a crash occurs during hot-remove a memory device, in which user is accessing the hugetlb. See calltrace as following:  ------------[ cut here ]------------ WARNING: CPU: 1 PID: 14045 at arch/x86/mm/fault.c:1278 do_user_addr_fault+0x2a0/0x790 Modules linked in: kmem device_dax cxl_mem cxl_pmem cxl_port cxl_pci dax_hmem dax_pmem nd_pmem cxl_acpi nd_btt cxl_core crc32c_intel nvme virtiofs fuse nvme_core nfit libnvdimm dm_multipath scsi_dh_rdac scsi_dh_emc s mirror dm_region_hash dm_log dm_mod CPU: 1 PID: 14045 Comm: daxctl Not tainted 6.10.0-rc2-lizhijian+ #492 Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS rel-1.16.3-0-ga6ed6b701f0a-prebuilt.qemu.org 04/01/2014 RIP: 0010:do_user_addr_fault+0x2a0/0x790 Code: 48 8b 00 a8 04 0f 84 b5 fe ff ff e9 1c ff ff ff 4c 89 e9 4c 89 e2 be 01 00 00 00 bf 02 00 00 00 e8 b5 ef 24 00 e9 42 fe ff ff \u0026lt;0f\u0026gt; 0b 48 83 c4 08 4c 89 ea 48 89 ee 4c 89 e7 5b 5d 41 5c 41 5d 41 RSP: 0000:ffffc90000a575f0 EFLAGS: 00010046 RAX: ffff88800c303600 RBX: 0000000000000000 RCX: 0000000000000000 RDX: 0000000000001000 RSI: ffffffff82504162 RDI: ffffffff824b2c36 RBP: 0000000000000000 R08: 0000000000000000 R09: 0000000000000000 R10: 0000000000000000 R11: 0000000000000000 R12: ffffc90000a57658 R13: 0000000000001000 R14: ffff88800bc2e040 R15: 0000000000000000 FS:  00007f51cb57d880(0000) GS:ffff88807fd00000(0000) knlGS:0000000000000000 CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 0000000000001000 CR3: 00000000072e2004 CR4: 00000000001706f0 DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400 Call Trace:  \u0026lt;TASK\u0026gt;  ? __warn+0x8d/0x190  ? do_user_addr_fault+0x2a0/0x790  ? report_bug+0x1c3/0x1d0  ? handle_bug+0x3c/0x70  ? exc_invalid_op+0x14/0x70  ? asm_exc_invalid_op+0x16/0x20  ? do_user_addr_fault+0x2a0/0x790  ? exc_page_fault+0x31/0x200  exc_page_fault+0x68/0x200 \u0026lt;...snip...\u0026gt; BUG: unable to handle page fault for address: 0000000000001000  #PF: supervisor read access in kernel mode  #PF: error_code(0x0000) - not-present page  PGD 800000000ad92067 P4D 800000000ad92067 PUD 7677067 PMD 0  Oops: Oops: 0000 [#1] PREEMPT SMP PTI  ---[ end trace 0000000000000000 ]---  BUG: unable to handle page fault for address: 0000000000001000  #PF: supervisor read access in kernel mode  #PF: error_code(0x0000) - not-present page  PGD 800000000ad92067 P4D 800000000ad92067 PUD 7677067 PMD 0  Oops: Oops: 0000 [#1] PREEMPT SMP PTI  CPU: 1 PID: 14045 Comm: daxctl Kdump: loaded Tainted: G        W          6.10.0-rc2-lizhijian+ #492  Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS rel-1.16.3-0-ga6ed6b701f0a-prebuilt.qemu.org 04/01/2014  RIP: 0010:dentry_name+0x1f4/0x440 \u0026lt;...snip...\u0026gt; ? dentry_name+0x2fa/0x440 vsnprintf+0x1f3/0x4f0 vprintk_store+0x23a/0x540 vprintk_emit+0x6d/0x330 _printk+0x58/0x80 dump_mapping+0x10b/0x1a0 ? __pfx_free_object_rcu+0x10/0x10 __dump_page+0x26b/0x3e0 ? vprintk_emit+0xe0/0x330 ? _printk+0x58/0x80 ? dump_page+0x17/0x50 dump_page+0x17/0x50 do_migrate_range+0x2f7/0x7f0 ? do_migrate_range+0x42/0x7f0 ? offline_pages+0x2f4/0x8c0 offline_pages+0x60a/0x8c0 memory_subsys_offline+0x9f/0x1c0 ? lockdep_hardirqs_on+0x77/0x100 ? _raw_spin_unlock_irqrestore+0x38/0x60 device_offline+0xe3/0x110 state_store+0x6e/0xc0 kernfs_fop_write_iter+0x143/0x200 vfs_write+0x39f/0x560 ksys_write+0x65/0xf0 do_syscall_64+0x62/0x130  Previously, some sanity check have been done in dump_mapping() before the print facility parsing \u0026apos;%pd\u0026apos; though, it\u0026apos;s still possible to run into an invalid dentry.d_name.name.  Since dump_mapping() only needs to dump the filename only, retrieve it by itself in a safer way to prevent an unnecessary crash.  Note that either retrieving the filename with \u0026apos;%pd\u0026apos; or strncpy_from_kernel_nofault(), the filename could be unreliable.(CVE-2024-49934)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  net/xen-netback: prevent UAF in xenvif_flush_hash()  During the list_for_each_entry_rcu iteration call of xenvif_flush_hash, kfree_rcu does not exist inside the rcu read critical section, so if kfree_rcu is called when the rcu grace period ends during the iteration, UAF occurs when accessing head-\u0026gt;next after the entry becomes free.  Therefore, to solve this, you need to change it to list_for_each_entry_safe.(CVE-2024-49936)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  l2tp: prevent possible tunnel refcount underflow  When a session is created, it sets a backpointer to its tunnel. When the session refcount drops to 0, l2tp_session_free drops the tunnel refcount if session-\u0026gt;tunnel is non-NULL. However, session-\u0026gt;tunnel is set in l2tp_session_create, before the tunnel refcount is incremented by l2tp_session_register, which leaves a small window where session-\u0026gt;tunnel is non-NULL when the tunnel refcount hasn\u0026apos;t been bumped.  Moving the assignment to l2tp_session_register is trivial but l2tp_session_create calls l2tp_session_set_header_len which uses session-\u0026gt;tunnel to get the tunnel\u0026apos;s encap. Add an encap arg to l2tp_session_set_header_len to avoid using session-\u0026gt;tunnel.  If l2tpv3 sessions have colliding IDs, it is possible for l2tp_v3_session_get to race with l2tp_session_register and fetch a session which doesn\u0026apos;t yet have session-\u0026gt;tunnel set. Add a check for this case.(CVE-2024-49940)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  Bluetooth: L2CAP: Fix uaf in l2cap_connect  [Syzbot reported] BUG: KASAN: slab-use-after-free in l2cap_connect.constprop.0+0x10d8/0x1270 net/bluetooth/l2cap_core.c:3949 Read of size 8 at addr ffff8880241e9800 by task kworker/u9:0/54  CPU: 0 UID: 0 PID: 54 Comm: kworker/u9:0 Not tainted 6.11.0-rc6-syzkaller-00268-g788220eee30d #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 08/06/2024 Workqueue: hci2 hci_rx_work Call Trace:  \u0026lt;TASK\u0026gt;  __dump_stack lib/dump_stack.c:93 [inline]  dump_stack_lvl+0x116/0x1f0 lib/dump_stack.c:119  print_address_description mm/kasan/report.c:377 [inline]  print_report+0xc3/0x620 mm/kasan/report.c:488  kasan_report+0xd9/0x110 mm/kasan/report.c:601  l2cap_connect.constprop.0+0x10d8/0x1270 net/bluetooth/l2cap_core.c:3949  l2cap_connect_req net/bluetooth/l2cap_core.c:4080 [inline]  l2cap_bredr_sig_cmd net/bluetooth/l2cap_core.c:4772 [inline]  l2cap_sig_channel net/bluetooth/l2cap_core.c:5543 [inline]  l2cap_recv_frame+0xf0b/0x8eb0 net/bluetooth/l2cap_core.c:6825  l2cap_recv_acldata+0x9b4/0xb70 net/bluetooth/l2cap_core.c:7514  hci_acldata_packet net/bluetooth/hci_core.c:3791 [inline]  hci_rx_work+0xaab/0x1610 net/bluetooth/hci_core.c:4028  process_one_work+0x9c5/0x1b40 kernel/workqueue.c:3231  process_scheduled_works kernel/workqueue.c:3312 [inline]  worker_thread+0x6c8/0xed0 kernel/workqueue.c:3389  kthread+0x2c1/0x3a0 kernel/kthread.c:389  ret_from_fork+0x45/0x80 arch/x86/kernel/process.c:147  ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:244 ...  Freed by task 5245:  kasan_save_stack+0x33/0x60 mm/kasan/common.c:47  kasan_save_track+0x14/0x30 mm/kasan/common.c:68  kasan_save_free_info+0x3b/0x60 mm/kasan/generic.c:579  poison_slab_object+0xf7/0x160 mm/kasan/common.c:240  __kasan_slab_free+0x32/0x50 mm/kasan/common.c:256  kasan_slab_free include/linux/kasan.h:184 [inline]  slab_free_hook mm/slub.c:2256 [inline]  slab_free mm/slub.c:4477 [inline]  kfree+0x12a/0x3b0 mm/slub.c:4598  l2cap_conn_free net/bluetooth/l2cap_core.c:1810 [inline]  kref_put include/linux/kref.h:65 [inline]  l2cap_conn_put net/bluetooth/l2cap_core.c:1822 [inline]  l2cap_conn_del+0x59d/0x730 net/bluetooth/l2cap_core.c:1802  l2cap_connect_cfm+0x9e6/0xf80 net/bluetooth/l2cap_core.c:7241  hci_connect_cfm include/net/bluetooth/hci_core.h:1960 [inline]  hci_conn_failed+0x1c3/0x370 net/bluetooth/hci_conn.c:1265  hci_abort_conn_sync+0x75a/0xb50 net/bluetooth/hci_sync.c:5583  abort_conn_sync+0x197/0x360 net/bluetooth/hci_conn.c:2917  hci_cmd_sync_work+0x1a4/0x410 net/bluetooth/hci_sync.c:328  process_one_work+0x9c5/0x1b40 kernel/workqueue.c:3231  process_scheduled_works kernel/workqueue.c:3312 [inline]  worker_thread+0x6c8/0xed0 kernel/workqueue.c:3389  kthread+0x2c1/0x3a0 kernel/kthread.c:389  ret_from_fork+0x45/0x80 arch/x86/kernel/process.c:147  ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:244(CVE-2024-49950)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  static_call: Replace pointless WARN_ON() in static_call_module_notify()  static_call_module_notify() triggers a WARN_ON(), when memory allocation fails in __static_call_add_module().  That\u0026apos;s not really justified, because the failure case must be correctly handled by the well known call chain and the error code is passed through to the initiating userspace application.  A memory allocation fail is not a fatal problem, but the WARN_ON() takes the machine out when panic_on_warn is set.  Replace it with a pr_warn().(CVE-2024-49954)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  ACPI: battery: Fix possible crash when unregistering a battery hook  When a battery hook returns an error when adding a new battery, then the battery hook is automatically unregistered. However the battery hook provider cannot know that, so it will later call battery_hook_unregister() on the already unregistered battery hook, resulting in a crash.  Fix this by using the list head to mark already unregistered battery hooks as already being unregistered so that they can be ignored by battery_hook_unregister().(CVE-2024-49955)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  ocfs2: reserve space for inline xattr before attaching reflink tree  One of our customers reported a crash and a corrupted ocfs2 filesystem.  The crash was due to the detection of corruption.  Upon troubleshooting, the fsck -fn output showed the below corruption  [EXTENT_LIST_FREE] Extent list in owner 33080590 claims 230 as the next free chain record, but fsck believes the largest valid value is 227.  Clamp the next record value? n  The stat output from the debugfs.ocfs2 showed the following corruption where the \u0026quot;Next Free Rec:\u0026quot; had overshot the \u0026quot;Count:\u0026quot; in the root metadata block.          Inode: 33080590   Mode: 0640   Generation: 2619713622 (0x9c25a856)         FS Generation: 904309833 (0x35e6ac49)         CRC32: 00000000   ECC: 0000         Type: Regular   Attr: 0x0   Flags: Valid         Dynamic Features: (0x16) HasXattr InlineXattr Refcounted         Extended Attributes Block: 0  Extended Attributes Inline Size: 256         User: 0 (root)   Group: 0 (root)   Size: 281320357888         Links: 1   Clusters: 141738         ctime: 0x66911b56 0x316edcb8 -- Fri Jul 12 06:02:30.829349048 2024         atime: 0x66911d6b 0x7f7a28d -- Fri Jul 12 06:11:23.133669517 2024         mtime: 0x66911b56 0x12ed75d7 -- Fri Jul 12 06:02:30.317552087 2024         dtime: 0x0 -- Wed Dec 31 17:00:00 1969         Refcount Block: 2777346         Last Extblk: 2886943   Orphan Slot: 0         Sub Alloc Slot: 0   Sub Alloc Bit: 14         Tree Depth: 1   Count: 227   Next Free Rec: 230         ## Offset        Clusters       Block#         0  0             2310           2776351         1  2310          2139           2777375         2  4449          1221           2778399         3  5670          731            2779423         4  6401          566            2780447         .......          ....           .......         .......          ....           .......  The issue was in the reflink workfow while reserving space for inline xattr.  The problematic function is ocfs2_reflink_xattr_inline().  By the time this function is called the reflink tree is already recreated at the destination inode from the source inode.  At this point, this function reserves space for inline xattrs at the destination inode without even checking if there is space at the root metadata block.  It simply reduces the l_count from 243 to 227 thereby making space of 256 bytes for inline xattr whereas the inode already has extents beyond this index (in this case up to 230), thereby causing corruption.  The fix for this is to reserve space for inline metadata at the destination inode before the reflink tree gets recreated. The customer has verified the fix.(CVE-2024-49958)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  r8169: add tally counter fields added with RTL8125  RTL8125 added fields to the tally counter, what may result in the chip dma\u0026apos;ing these new fields to unallocated memory. Therefore make sure that the allocated memory area is big enough to hold all of the tally counter values, even if we use only parts of it.(CVE-2024-49973)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  uprobes: fix kernel info leak via \u0026quot;[uprobes]\u0026quot; vma  xol_add_vma() maps the uninitialized page allocated by __create_xol_area() into userspace. On some architectures (x86) this memory is readable even without VM_READ, VM_EXEC results in the same pgprot_t as VM_EXEC|VM_READ, although this doesn\u0026apos;t really matter, debugger can read this memory anyway.(CVE-2024-49975)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  gso: fix udp gso fraglist segmentation after pull from frag_list  Detect gso fraglist skbs with corrupted geometry (see below) and pass these to skb_segment instead of skb_segment_list, as the first can segment them correctly.  Valid SKB_GSO_FRAGLIST skbs - consist of two or more segments - the head_skb holds the protocol headers plus first gso_size - one or more frag_list skbs hold exactly one segment - all but the last must be gso_size  Optional datapath hooks such as NAT and BPF (bpf_skb_pull_data) can modify these skbs, breaking these invariants.  In extreme cases they pull all data into skb linear. For UDP, this causes a NULL ptr deref in __udpv4_gso_segment_list_csum at udp_hdr(seg-\u0026gt;next)-\u0026gt;dest.  Detect invalid geometry due to pull, by checking head_skb size. Don\u0026apos;t just drop, as this may blackhole a destination. Convert to be able to pass to regular skb_segment.(CVE-2024-49978)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  media: venus: fix use after free bug in venus_remove due to race condition  in venus_probe, core-\u0026gt;work is bound with venus_sys_error_handler, which is used to handle error. The code use core-\u0026gt;sys_err_done to make sync work. The core-\u0026gt;work is started in venus_event_notify.  If we call venus_remove, there might be an unfished work. The possible sequence is as follows:  CPU0                  CPU1                       |venus_sys_error_handler venus_remove         | hfi_destroy     | venus_hfi_destroy  | kfree(hdev);      |                      |hfi_reinit       |venus_hfi_queues_reinit                      |//use hdev  Fix it by canceling the work in venus_remove.(CVE-2024-49981)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  drm/stm: Avoid use-after-free issues with crtc and plane  ltdc_load() calls functions drm_crtc_init_with_planes(), drm_universal_plane_init() and drm_encoder_init(). These functions should not be called with parameters allocated with devm_kzalloc() to avoid use-after-free issues [1].  Use allocations managed by the DRM framework.  Found by Linux Verification Center (linuxtesting.org).  [1] https://lore.kernel.org/lkml/u366i76e3qhh3ra5oxrtngjtm2u5lterkekcz6y2jkndhuxzli@diujon4h7qwb/(CVE-2024-49992)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  tipc: guard against string buffer overrun  Smatch reports that copying media_name and if_name to name_parts may overwrite the destination.   .../bearer.c:166 bearer_name_validate() error: strcpy() \u0026apos;media_name\u0026apos; too large for \u0026apos;name_parts-\u0026gt;media_name\u0026apos; (32 vs 16)  .../bearer.c:167 bearer_name_validate() error: strcpy() \u0026apos;if_name\u0026apos; too large for \u0026apos;name_parts-\u0026gt;if_name\u0026apos; (1010102 vs 16)  This does seem to be the case so guard against this possibility by using strscpy() and failing if truncation occurs.  Introduced by commit b97bf3fd8f6a (\u0026quot;[TIPC] Initial merge\u0026quot;)  Compile tested only.(CVE-2024-49995)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  cifs: Fix buffer overflow when parsing NFS reparse points  ReparseDataLength is sum of the InodeType size and DataBuffer size. So to get DataBuffer size it is needed to subtract InodeType\u0026apos;s size from ReparseDataLength.  Function cifs_strndup_from_utf16() is currentlly accessing buf-\u0026gt;DataBuffer at position after the end of the buffer because it does not subtract InodeType size from the length. Fix this problem and correctly subtract variable len.  Member InodeType is present only when reparse buffer is large enough. Check for ReparseDataLength before accessing InodeType to prevent another invalid memory access.  Major and minor rdev values are present also only when reparse buffer is large enough. Check for reparse buffer size before calling reparse_mkdev().(CVE-2024-49996)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  static_call: Handle module init failure correctly in static_call_del_module()  Module insertion invokes static_call_add_module() to initialize the static calls in a module. static_call_add_module() invokes __static_call_init(), which allocates a struct static_call_mod to either encapsulate the built-in static call sites of the associated key into it so further modules can be added or to append the module to the module chain.  If that allocation fails the function returns with an error code and the module core invokes static_call_del_module() to clean up eventually added static_call_mod entries.  This works correctly, when all keys used by the module were converted over to a module chain before the failure. If not then static_call_del_module() causes a #GP as it blindly assumes that key::mods points to a valid struct static_call_mod.  The problem is that key::mods is not a individual struct member of struct static_call_key, it\u0026apos;s part of a union to save space:          union {                 /* bit 0: 0 = mods, 1 = sites */                 unsigned long type;                 struct static_call_mod *mods;                 struct static_call_site *sites;  };  key::sites is a pointer to the list of built-in usage sites of the static call. The type of the pointer is differentiated by bit 0. A mods pointer has the bit clear, the sites pointer has the bit set.  As static_call_del_module() blidly assumes that the pointer is a valid static_call_mod type, it fails to check for this failure case and dereferences the pointer to the list of built-in call sites, which is obviously bogus.  Cure it by checking whether the key has a sites or a mods pointer.  If it\u0026apos;s a sites pointer then the key is not to be touched. As the sites are walked in the same order as in __static_call_init() the site walk can be terminated because all subsequent sites have not been touched by the init code due to the error exit.  If it was converted before the allocation fail, then the inner loop which searches for a module match will find nothing.  A fail in the second allocation in __static_call_init() is harmless and does not require special treatment. The first allocation succeeded and converted the key to a module chain. That first entry has mod::mod == NULL and mod::next == NULL, so the inner loop of static_call_del_module() will neither find a module match nor a module chain. The next site in the walk was either already converted, but can\u0026apos;t match the module, or it will exit the outer loop because it has a static_call_site pointer and not a static_call_mod pointer.(CVE-2024-50002)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  ALSA: asihpi: Fix potential OOB array access  ASIHPI driver stores some values in the static array upon a response from the driver, and its index depends on the firmware.  We shouldn\u0026apos;t trust it blindly.  This patch adds a sanity check of the array index to fit in the array size.(CVE-2024-50007)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  wifi: mwifiex: Fix memcpy() field-spanning write warning in mwifiex_cmd_802_11_scan_ext()  Replace one-element array with a flexible-array member in `struct host_cmd_ds_802_11_scan_ext`.  With this, fix the following warning:  elo 16 17:51:58 surfacebook kernel: ------------[ cut here ]------------ elo 16 17:51:58 surfacebook kernel: memcpy: detected field-spanning write (size 243) of single field \u0026quot;ext_scan-\u0026gt;tlv_buffer\u0026quot; at drivers/net/wireless/marvell/mwifiex/scan.c:2239 (size 1) elo 16 17:51:58 surfacebook kernel: WARNING: CPU: 0 PID: 498 at drivers/net/wireless/marvell/mwifiex/scan.c:2239 mwifiex_cmd_802_11_scan_ext+0x83/0x90 [mwifiex](CVE-2024-50008)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  ext4: dax: fix overflowing extents beyond inode size when partially writing  The dax_iomap_rw() does two things in each iteration: map written blocks and copy user data to blocks. If the process is killed by user(See signal handling in dax_iomap_iter()), the copied data will be returned and added on inode size, which means that the length of written extents may exceed the inode size, then fsck will fail. An example is given as:  dd if=/dev/urandom of=file bs=4M count=1  dax_iomap_rw   iomap_iter // round 1    ext4_iomap_begin     ext4_iomap_alloc // allocate 0~2M extents(written flag)   dax_iomap_iter // copy 2M data   iomap_iter // round 2    iomap_iter_advance     iter-\u0026gt;pos += iter-\u0026gt;processed // iter-\u0026gt;pos = 2M    ext4_iomap_begin     ext4_iomap_alloc // allocate 2~4M extents(written flag)   dax_iomap_iter    fatal_signal_pending   done = iter-\u0026gt;pos - iocb-\u0026gt;ki_pos // done = 2M  ext4_handle_inode_extension   ext4_update_inode_size // inode size = 2M  fsck reports: Inode 13, i_size is 2097152, should be 4194304.  Fix?  Fix the problem by truncating extents if the written length is smaller than expected.(CVE-2024-50015)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  drm/amd/display: Avoid overflow assignment in link_dp_cts  sampling_rate is an uint8_t but is assigned an unsigned int, and thus it can overflow. As a result, sampling_rate is changed to uint32_t.  Similarly, LINK_QUAL_PATTERN_SET has a size of 2 bits, and it should only be assigned to a value less or equal than 4.  This fixes 2 INTEGER_OVERFLOW issues reported by Coverity.(CVE-2024-50016)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  thermal: core: Reference count the zone in thermal_zone_get_by_id()  There are places in the thermal netlink code where nothing prevents the thermal zone object from going away while being accessed after it has been returned by thermal_zone_get_by_id().  To address this, make thermal_zone_get_by_id() get a reference on the thermal zone device object to be returned with the help of get_device(), under thermal_list_lock, and adjust all of its callers to this change with the help of the cleanup.h infrastructure.(CVE-2024-50028)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  slip: make slhc_remember() more robust against malicious packets  syzbot found that slhc_remember() was missing checks against malicious packets [1].  slhc_remember() only checked the size of the packet was at least 20, which is not good enough.  We need to make sure the packet includes the IPv4 and TCP header that are supposed to be carried.  Add iph and th pointers to make the code more readable.  [1]  BUG: KMSAN: uninit-value in slhc_remember+0x2e8/0x7b0 drivers/net/slip/slhc.c:666   slhc_remember+0x2e8/0x7b0 drivers/net/slip/slhc.c:666   ppp_receive_nonmp_frame+0xe45/0x35e0 drivers/net/ppp/ppp_generic.c:2455   ppp_receive_frame drivers/net/ppp/ppp_generic.c:2372 [inline]   ppp_do_recv+0x65f/0x40d0 drivers/net/ppp/ppp_generic.c:2212   ppp_input+0x7dc/0xe60 drivers/net/ppp/ppp_generic.c:2327   pppoe_rcv_core+0x1d3/0x720 drivers/net/ppp/pppoe.c:379   sk_backlog_rcv+0x13b/0x420 include/net/sock.h:1113   __release_sock+0x1da/0x330 net/core/sock.c:3072   release_sock+0x6b/0x250 net/core/sock.c:3626   pppoe_sendmsg+0x2b8/0xb90 drivers/net/ppp/pppoe.c:903   sock_sendmsg_nosec net/socket.c:729 [inline]   __sock_sendmsg+0x30f/0x380 net/socket.c:744   ____sys_sendmsg+0x903/0xb60 net/socket.c:2602   ___sys_sendmsg+0x28d/0x3c0 net/socket.c:2656   __sys_sendmmsg+0x3c1/0x960 net/socket.c:2742   __do_sys_sendmmsg net/socket.c:2771 [inline]   __se_sys_sendmmsg net/socket.c:2768 [inline]   __x64_sys_sendmmsg+0xbc/0x120 net/socket.c:2768   x64_sys_call+0xb6e/0x3ba0 arch/x86/include/generated/asm/syscalls_64.h:308   do_syscall_x64 arch/x86/entry/common.c:52 [inline]   do_syscall_64+0xcd/0x1e0 arch/x86/entry/common.c:83  entry_SYSCALL_64_after_hwframe+0x77/0x7f  Uninit was created at:   slab_post_alloc_hook mm/slub.c:4091 [inline]   slab_alloc_node mm/slub.c:4134 [inline]   kmem_cache_alloc_node_noprof+0x6bf/0xb80 mm/slub.c:4186   kmalloc_reserve+0x13d/0x4a0 net/core/skbuff.c:587   __alloc_skb+0x363/0x7b0 net/core/skbuff.c:678   alloc_skb include/linux/skbuff.h:1322 [inline]   sock_wmalloc+0xfe/0x1a0 net/core/sock.c:2732   pppoe_sendmsg+0x3a7/0xb90 drivers/net/ppp/pppoe.c:867   sock_sendmsg_nosec net/socket.c:729 [inline]   __sock_sendmsg+0x30f/0x380 net/socket.c:744   ____sys_sendmsg+0x903/0xb60 net/socket.c:2602   ___sys_sendmsg+0x28d/0x3c0 net/socket.c:2656   __sys_sendmmsg+0x3c1/0x960 net/socket.c:2742   __do_sys_sendmmsg net/socket.c:2771 [inline]   __se_sys_sendmmsg net/socket.c:2768 [inline]   __x64_sys_sendmmsg+0xbc/0x120 net/socket.c:2768   x64_sys_call+0xb6e/0x3ba0 arch/x86/include/generated/asm/syscalls_64.h:308   do_syscall_x64 arch/x86/entry/common.c:52 [inline]   do_syscall_64+0xcd/0x1e0 arch/x86/entry/common.c:83  entry_SYSCALL_64_after_hwframe+0x77/0x7f  CPU: 0 UID: 0 PID: 5460 Comm: syz.2.33 Not tainted 6.12.0-rc2-syzkaller-00006-g87d6aab2389e #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 09/13/2024(CVE-2024-50033)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  ppp: fix ppp_async_encode() illegal access  syzbot reported an issue in ppp_async_encode() [1]  In this case, pppoe_sendmsg() is called with a zero size. Then ppp_async_encode() is called with an empty skb.  BUG: KMSAN: uninit-value in ppp_async_encode drivers/net/ppp/ppp_async.c:545 [inline]  BUG: KMSAN: uninit-value in ppp_async_push+0xb4f/0x2660 drivers/net/ppp/ppp_async.c:675   ppp_async_encode drivers/net/ppp/ppp_async.c:545 [inline]   ppp_async_push+0xb4f/0x2660 drivers/net/ppp/ppp_async.c:675   ppp_async_send+0x130/0x1b0 drivers/net/ppp/ppp_async.c:634   ppp_channel_bridge_input drivers/net/ppp/ppp_generic.c:2280 [inline]   ppp_input+0x1f1/0xe60 drivers/net/ppp/ppp_generic.c:2304   pppoe_rcv_core+0x1d3/0x720 drivers/net/ppp/pppoe.c:379   sk_backlog_rcv+0x13b/0x420 include/net/sock.h:1113   __release_sock+0x1da/0x330 net/core/sock.c:3072   release_sock+0x6b/0x250 net/core/sock.c:3626   pppoe_sendmsg+0x2b8/0xb90 drivers/net/ppp/pppoe.c:903   sock_sendmsg_nosec net/socket.c:729 [inline]   __sock_sendmsg+0x30f/0x380 net/socket.c:744   ____sys_sendmsg+0x903/0xb60 net/socket.c:2602   ___sys_sendmsg+0x28d/0x3c0 net/socket.c:2656   __sys_sendmmsg+0x3c1/0x960 net/socket.c:2742   __do_sys_sendmmsg net/socket.c:2771 [inline]   __se_sys_sendmmsg net/socket.c:2768 [inline]   __x64_sys_sendmmsg+0xbc/0x120 net/socket.c:2768   x64_sys_call+0xb6e/0x3ba0 arch/x86/include/generated/asm/syscalls_64.h:308   do_syscall_x64 arch/x86/entry/common.c:52 [inline]   do_syscall_64+0xcd/0x1e0 arch/x86/entry/common.c:83  entry_SYSCALL_64_after_hwframe+0x77/0x7f  Uninit was created at:   slab_post_alloc_hook mm/slub.c:4092 [inline]   slab_alloc_node mm/slub.c:4135 [inline]   kmem_cache_alloc_node_noprof+0x6bf/0xb80 mm/slub.c:4187   kmalloc_reserve+0x13d/0x4a0 net/core/skbuff.c:587   __alloc_skb+0x363/0x7b0 net/core/skbuff.c:678   alloc_skb include/linux/skbuff.h:1322 [inline]   sock_wmalloc+0xfe/0x1a0 net/core/sock.c:2732   pppoe_sendmsg+0x3a7/0xb90 drivers/net/ppp/pppoe.c:867   sock_sendmsg_nosec net/socket.c:729 [inline]   __sock_sendmsg+0x30f/0x380 net/socket.c:744   ____sys_sendmsg+0x903/0xb60 net/socket.c:2602   ___sys_sendmsg+0x28d/0x3c0 net/socket.c:2656   __sys_sendmmsg+0x3c1/0x960 net/socket.c:2742   __do_sys_sendmmsg net/socket.c:2771 [inline]   __se_sys_sendmmsg net/socket.c:2768 [inline]   __x64_sys_sendmmsg+0xbc/0x120 net/socket.c:2768   x64_sys_call+0xb6e/0x3ba0 arch/x86/include/generated/asm/syscalls_64.h:308   do_syscall_x64 arch/x86/entry/common.c:52 [inline]   do_syscall_64+0xcd/0x1e0 arch/x86/entry/common.c:83  entry_SYSCALL_64_after_hwframe+0x77/0x7f  CPU: 1 UID: 0 PID: 5411 Comm: syz.1.14 Not tainted 6.12.0-rc1-syzkaller-00165-g360c1f1f24c6 #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 09/13/2024(CVE-2024-50035)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  igb: Do not bring the device up after non-fatal error  Commit 004d25060c78 (\u0026quot;igb: Fix igb_down hung on surprise removal\u0026quot;) changed igb_io_error_detected() to ignore non-fatal pcie errors in order to avoid hung task that can happen when igb_down() is called multiple times. This caused an issue when processing transient non-fatal errors. igb_io_resume(), which is called after igb_io_error_detected(), assumes that device is brought down by igb_io_error_detected() if the interface is up. This resulted in panic with stacktrace below.  [ T3256] igb 0000:09:00.0 haeth0: igb: haeth0 NIC Link is Down [  T292] pcieport 0000:00:1c.5: AER: Uncorrected (Non-Fatal) error received: 0000:09:00.0 [  T292] igb 0000:09:00.0: PCIe Bus Error: severity=Uncorrected (Non-Fatal), type=Transaction Layer, (Requester ID) [  T292] igb 0000:09:00.0:   device [8086:1537] error status/mask=00004000/00000000 [  T292] igb 0000:09:00.0:    [14] CmpltTO [  200.105524,009][  T292] igb 0000:09:00.0: AER:   TLP Header: 00000000 00000000 00000000 00000000 [  T292] pcieport 0000:00:1c.5: AER: broadcast error_detected message [  T292] igb 0000:09:00.0: Non-correctable non-fatal error reported. [  T292] pcieport 0000:00:1c.5: AER: broadcast mmio_enabled message [  T292] pcieport 0000:00:1c.5: AER: broadcast resume message [  T292] ------------[ cut here ]------------ [  T292] kernel BUG at net/core/dev.c:6539! [  T292] invalid opcode: 0000 [#1] PREEMPT SMP [  T292] RIP: 0010:napi_enable+0x37/0x40 [  T292] Call Trace: [  T292]  \u0026lt;TASK\u0026gt; [  T292]  ? die+0x33/0x90 [  T292]  ? do_trap+0xdc/0x110 [  T292]  ? napi_enable+0x37/0x40 [  T292]  ? do_error_trap+0x70/0xb0 [  T292]  ? napi_enable+0x37/0x40 [  T292]  ? napi_enable+0x37/0x40 [  T292]  ? exc_invalid_op+0x4e/0x70 [  T292]  ? napi_enable+0x37/0x40 [  T292]  ? asm_exc_invalid_op+0x16/0x20 [  T292]  ? napi_enable+0x37/0x40 [  T292]  igb_up+0x41/0x150 [  T292]  igb_io_resume+0x25/0x70 [  T292]  report_resume+0x54/0x70 [  T292]  ? report_frozen_detected+0x20/0x20 [  T292]  pci_walk_bus+0x6c/0x90 [  T292]  ? aer_print_port_info+0xa0/0xa0 [  T292]  pcie_do_recovery+0x22f/0x380 [  T292]  aer_process_err_devices+0x110/0x160 [  T292]  aer_isr+0x1c1/0x1e0 [  T292]  ? disable_irq_nosync+0x10/0x10 [  T292]  irq_thread_fn+0x1a/0x60 [  T292]  irq_thread+0xe3/0x1a0 [  T292]  ? irq_set_affinity_notifier+0x120/0x120 [  T292]  ? irq_affinity_notify+0x100/0x100 [  T292]  kthread+0xe2/0x110 [  T292]  ? kthread_complete_and_exit+0x20/0x20 [  T292]  ret_from_fork+0x2d/0x50 [  T292]  ? kthread_complete_and_exit+0x20/0x20 [  T292]  ret_from_fork_asm+0x11/0x20 [  T292]  \u0026lt;/TASK\u0026gt;  To fix this issue igb_io_resume() checks if the interface is running and the device is not down this means igb_io_error_detected() did not bring the device down and there is no need to bring it up.(CVE-2024-50040)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  smb: client: fix UAF in async decryption  Doing an async decryption (large read) crashes with a slab-use-after-free way down in the crypto API.  Reproducer:     # mount.cifs -o ...,seal,esize=1 //srv/share /mnt     # dd if=/mnt/largefile of=/dev/null     ...     [  194.196391] ==================================================================     [  194.196844] BUG: KASAN: slab-use-after-free in gf128mul_4k_lle+0xc1/0x110     [  194.197269] Read of size 8 at addr ffff888112bd0448 by task kworker/u77:2/899     [  194.197707]     [  194.197818] CPU: 12 UID: 0 PID: 899 Comm: kworker/u77:2 Not tainted 6.11.0-lku-00028-gfca3ca14a17a-dirty #43     [  194.198400] Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS rel-1.16.2-3-gd478f380-prebuilt.qemu.org 04/01/2014     [  194.199046] Workqueue: smb3decryptd smb2_decrypt_offload [cifs]     [  194.200032] Call Trace:     [  194.200191]  \u0026lt;TASK\u0026gt;     [  194.200327]  dump_stack_lvl+0x4e/0x70     [  194.200558]  ? gf128mul_4k_lle+0xc1/0x110     [  194.200809]  print_report+0x174/0x505     [  194.201040]  ? __pfx__raw_spin_lock_irqsave+0x10/0x10     [  194.201352]  ? srso_return_thunk+0x5/0x5f     [  194.201604]  ? __virt_addr_valid+0xdf/0x1c0     [  194.201868]  ? gf128mul_4k_lle+0xc1/0x110     [  194.202128]  kasan_report+0xc8/0x150     [  194.202361]  ? gf128mul_4k_lle+0xc1/0x110     [  194.202616]  gf128mul_4k_lle+0xc1/0x110     [  194.202863]  ghash_update+0x184/0x210     [  194.203103]  shash_ahash_update+0x184/0x2a0     [  194.203377]  ? __pfx_shash_ahash_update+0x10/0x10     [  194.203651]  ? srso_return_thunk+0x5/0x5f     [  194.203877]  ? crypto_gcm_init_common+0x1ba/0x340     [  194.204142]  gcm_hash_assoc_remain_continue+0x10a/0x140     [  194.204434]  crypt_message+0xec1/0x10a0 [cifs]     [  194.206489]  ? __pfx_crypt_message+0x10/0x10 [cifs]     [  194.208507]  ? srso_return_thunk+0x5/0x5f     [  194.209205]  ? srso_return_thunk+0x5/0x5f     [  194.209925]  ? srso_return_thunk+0x5/0x5f     [  194.210443]  ? srso_return_thunk+0x5/0x5f     [  194.211037]  decrypt_raw_data+0x15f/0x250 [cifs]     [  194.212906]  ? __pfx_decrypt_raw_data+0x10/0x10 [cifs]     [  194.214670]  ? srso_return_thunk+0x5/0x5f     [  194.215193]  smb2_decrypt_offload+0x12a/0x6c0 [cifs]  This is because TFM is being used in parallel.  Fix this by allocating a new AEAD TFM for async decryption, but keep the existing one for synchronous READ cases (similar to what is done in smb3_calc_signature()).  Also remove the calls to aead_request_set_callback() and crypto_wait_req() since it\u0026apos;s always going to be a synchronous operation.(CVE-2024-50047)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  serial: protect uart_port_dtr_rts() in uart_shutdown() too  Commit af224ca2df29 (serial: core: Prevent unsafe uart port access, part 3) added few uport == NULL checks. It added one to uart_shutdown(), so the commit assumes, uport can be NULL in there. But right after that protection, there is an unprotected \u0026quot;uart_port_dtr_rts(uport, false);\u0026quot; call. That is invoked only if HUPCL is set, so I assume that is the reason why we do not see lots of these reports.  Or it cannot be NULL at this point at all for some reason :P.  Until the above is investigated, stay on the safe side and move this dereference to the if too.  I got this inconsistency from Coverity under CID 1585130. Thanks.(CVE-2024-50058)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  ntb: ntb_hw_switchtec: Fix use after free vulnerability in switchtec_ntb_remove due to race condition  In the switchtec_ntb_add function, it can call switchtec_ntb_init_sndev function, then \u0026amp;sndev-\u0026gt;check_link_status_work is bound with check_link_status_work. switchtec_ntb_link_notification may be called to start the work.  If we remove the module which will call switchtec_ntb_remove to make cleanup, it will free sndev through kfree(sndev), while the work mentioned above will be used. The sequence of operations that may lead to a UAF bug is as follows:  CPU0                                 CPU1                          | check_link_status_work switchtec_ntb_remove    | kfree(sndev);           |                         | if (sndev-\u0026gt;link_force_down)                         | // use sndev  Fix it by ensuring that the work is canceled before proceeding with the cleanup in switchtec_ntb_remove.(CVE-2024-50059)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  io_uring: check if we need to reschedule during overflow flush  In terms of normal application usage, this list will always be empty. And if an application does overflow a bit, it\u0026apos;ll have a few entries. However, nothing obviously prevents syzbot from running a test case that generates a ton of overflow entries, and then flushing them can take quite a while.  Check for needing to reschedule while flushing, and drop our locks and do so if necessary. There\u0026apos;s no state to maintain here as overflows always prune from head-of-list, hence it\u0026apos;s fine to drop and reacquire the locks at the end of the loop.(CVE-2024-50060)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  bpf: Prevent tail call between progs attached to different hooks  bpf progs can be attached to kernel functions, and the attached functions can take different parameters or return different return values. If prog attached to one kernel function tail calls prog attached to another kernel function, the ctx access or return value verification could be bypassed.  For example, if prog1 is attached to func1 which takes only 1 parameter and prog2 is attached to func2 which takes two parameters. Since verifier assumes the bpf ctx passed to prog2 is constructed based on func2\u0026apos;s prototype, verifier allows prog2 to access the second parameter from the bpf ctx passed to it. The problem is that verifier does not prevent prog1 from passing its bpf ctx to prog2 via tail call. In this case, the bpf ctx passed to prog2 is constructed from func1 instead of func2, that is, the assumption for ctx access verification is bypassed.  Another example, if BPF LSM prog1 is attached to hook file_alloc_security, and BPF LSM prog2 is attached to hook bpf_lsm_audit_rule_known. Verifier knows the return value rules for these two hooks, e.g. it is legal for bpf_lsm_audit_rule_known to return positive number 1, and it is illegal for file_alloc_security to return positive number. So verifier allows prog2 to return positive number 1, but does not allow prog1 to return positive number. The problem is that verifier does not prevent prog1 from calling prog2 via tail call. In this case, prog2\u0026apos;s return value 1 will be used as the return value for prog1\u0026apos;s hook file_alloc_security. That is, the return value rule is bypassed.  This patch adds restriction for tail call to prevent such bypasses.(CVE-2024-50063)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  zram: free secondary algorithms names  We need to kfree() secondary algorithms names when reset zram device that had multi-streams, otherwise we leak memory.  [senozhatsky@chromium.org: kfree(NULL) is legal]   Link: https://lkml.kernel.org/r/20240917013021.868769-1-senozhatsky@chromium.org(CVE-2024-50064)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  uprobe: avoid out-of-bounds memory access of fetching args  Uprobe needs to fetch args into a percpu buffer, and then copy to ring buffer to avoid non-atomic context problem.  Sometimes user-space strings, arrays can be very large, but the size of percpu buffer is only page size. And store_trace_args() won\u0026apos;t check whether these data exceeds a single page or not, caused out-of-bounds memory access.  It could be reproduced by following steps: 1. build kernel with CONFIG_KASAN enabled 2. save follow program as test.c  ``` \\#include \u0026lt;stdio.h\u0026gt; \\#include \u0026lt;stdlib.h\u0026gt; \\#include \u0026lt;string.h\u0026gt;  // If string length large than MAX_STRING_SIZE, the fetch_store_strlen() // will return 0, cause __get_data_size() return shorter size, and // store_trace_args() will not trigger out-of-bounds access. // So make string length less than 4096. \\#define STRLEN 4093  void generate_string(char *str, int n) {     int i;     for (i = 0; i \u0026lt; n; ++i)     {         char c = i % 26 + \u0026apos;a\u0026apos;;         str[i] = c;     }     str[n-1] = \u0026apos;\\0\u0026apos;; }  void print_string(char *str) {     printf(\u0026quot;%s\\n\u0026quot;, str); }  int main() {     char tmp[STRLEN];      generate_string(tmp, STRLEN);     print_string(tmp);      return 0; } ``` 3. compile program `gcc -o test test.c`  4. get the offset of `print_string()` ``` objdump -t test | grep -w print_string 0000000000401199 g     F .text  000000000000001b              print_string ```  5. configure uprobe with offset 0x1199 ``` off=0x1199  cd /sys/kernel/debug/tracing/ echo \u0026quot;p /root/test:${off} arg1=+0(%di):ustring arg2=\\$comm arg3=+0(%di):ustring\u0026quot;  \u0026gt; uprobe_events echo 1 \u0026gt; events/uprobes/enable echo 1 \u0026gt; tracing_on ```  6. run `test`, and kasan will report error. ================================================================== BUG: KASAN: use-after-free in strncpy_from_user+0x1d6/0x1f0 Write of size 8 at addr ffff88812311c004 by task test/499CPU: 0 UID: 0 PID: 499 Comm: test Not tainted 6.12.0-rc3+ #18 Hardware name: Red Hat KVM, BIOS 1.16.0-4.al8 04/01/2014 Call Trace:  \u0026lt;TASK\u0026gt;  dump_stack_lvl+0x55/0x70  print_address_description.constprop.0+0x27/0x310  kasan_report+0x10f/0x120  ? strncpy_from_user+0x1d6/0x1f0  strncpy_from_user+0x1d6/0x1f0  ? rmqueue.constprop.0+0x70d/0x2ad0  process_fetch_insn+0xb26/0x1470  ? __pfx_process_fetch_insn+0x10/0x10  ? _raw_spin_lock+0x85/0xe0  ? __pfx__raw_spin_lock+0x10/0x10  ? __pte_offset_map+0x1f/0x2d0  ? unwind_next_frame+0xc5f/0x1f80  ? arch_stack_walk+0x68/0xf0  ? is_bpf_text_address+0x23/0x30  ? kernel_text_address.part.0+0xbb/0xd0  ? __kernel_text_address+0x66/0xb0  ? unwind_get_return_address+0x5e/0xa0  ? __pfx_stack_trace_consume_entry+0x10/0x10  ? arch_stack_walk+0xa2/0xf0  ? _raw_spin_lock_irqsave+0x8b/0xf0  ? __pfx__raw_spin_lock_irqsave+0x10/0x10  ? depot_alloc_stack+0x4c/0x1f0  ? _raw_spin_unlock_irqrestore+0xe/0x30  ? stack_depot_save_flags+0x35d/0x4f0  ? kasan_save_stack+0x34/0x50  ? kasan_save_stack+0x24/0x50  ? mutex_lock+0x91/0xe0  ? __pfx_mutex_lock+0x10/0x10  prepare_uprobe_buffer.part.0+0x2cd/0x500  uprobe_dispatcher+0x2c3/0x6a0  ? __pfx_uprobe_dispatcher+0x10/0x10  ? __kasan_slab_alloc+0x4d/0x90  handler_chain+0xdd/0x3e0  handle_swbp+0x26e/0x3d0  ? __pfx_handle_swbp+0x10/0x10  ? uprobe_pre_sstep_notifier+0x151/0x1b0  irqentry_exit_to_user_mode+0xe2/0x1b0  asm_exc_int3+0x39/0x40 RIP: 0033:0x401199 Code: 01 c2 0f b6 45 fb 88 02 83 45 fc 01 8b 45 fc 3b 45 e4 7c b7 8b 45 e4 48 98 48 8d 50 ff 48 8b 45 e8 48 01 d0 ce RSP: 002b:00007ffdf00576a8 EFLAGS: 00000206 RAX: 00007ffdf00576b0 RBX: 0000000000000000 RCX: 0000000000000ff2 RDX: 0000000000000ffc RSI: 0000000000000ffd RDI: 00007ffdf00576b0 RBP: 00007ffdf00586b0 R08: 00007feb2f9c0d20 R09: 00007feb2f9c0d20 R10: 0000000000000001 R11: 0000000000000202 R12: 0000000000401040 R13: 00007ffdf0058780 R14: 0000000000000000 R15: 0000000000000000  \u0026lt;/TASK\u0026gt;  This commit enforces the buffer\u0026apos;s maxlen less than a page-size to avoid store_trace_args() out-of-memory access.(CVE-2024-50067)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  parport: Proper fix for array out-of-bounds access  The recent fix for array out-of-bounds accesses replaced sprintf() calls blindly with snprintf().  However, since snprintf() returns the would-be-printed size, not the actually output size, the length calculation can still go over the given limit.  Use scnprintf() instead of snprintf(), which returns the actually output letters, for addressing the potential out-of-bounds access properly.(CVE-2024-50074)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  tcp: fix mptcp DSS corruption due to large pmtu xmit  Syzkaller was able to trigger a DSS corruption:    TCP: request_sock_subflow_v4: Possible SYN flooding on port [::]:20002. Sending cookies.   ------------[ cut here ]------------   WARNING: CPU: 0 PID: 5227 at net/mptcp/protocol.c:695 __mptcp_move_skbs_from_subflow+0x20a9/0x21f0 net/mptcp/protocol.c:695   Modules linked in:   CPU: 0 UID: 0 PID: 5227 Comm: syz-executor350 Not tainted 6.11.0-syzkaller-08829-gaf9c191ac2a0 #0   Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 08/06/2024   RIP: 0010:__mptcp_move_skbs_from_subflow+0x20a9/0x21f0 net/mptcp/protocol.c:695   Code: 0f b6 dc 31 ff 89 de e8 b5 dd ea f5 89 d8 48 81 c4 50 01 00 00 5b 41 5c 41 5d 41 5e 41 5f 5d c3 cc cc cc cc e8 98 da ea f5 90 \u0026lt;0f\u0026gt; 0b 90 e9 47 ff ff ff e8 8a da ea f5 90 0f 0b 90 e9 99 e0 ff ff   RSP: 0018:ffffc90000006db8 EFLAGS: 00010246   RAX: ffffffff8ba9df18 RBX: 00000000000055f0 RCX: ffff888030023c00   RDX: 0000000000000100 RSI: 00000000000081e5 RDI: 00000000000055f0   RBP: 1ffff110062bf1ae R08: ffffffff8ba9cf12 R09: 1ffff110062bf1b8   R10: dffffc0000000000 R11: ffffed10062bf1b9 R12: 0000000000000000   R13: dffffc0000000000 R14: 00000000700cec61 R15: 00000000000081e5   FS:  000055556679c380(0000) GS:ffff8880b8600000(0000) knlGS:0000000000000000   CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033   CR2: 0000000020287000 CR3: 0000000077892000 CR4: 00000000003506f0   DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000   DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400   Call Trace:    \u0026lt;IRQ\u0026gt;    move_skbs_to_msk net/mptcp/protocol.c:811 [inline]    mptcp_data_ready+0x29c/0xa90 net/mptcp/protocol.c:854    subflow_data_ready+0x34a/0x920 net/mptcp/subflow.c:1490    tcp_data_queue+0x20fd/0x76c0 net/ipv4/tcp_input.c:5283    tcp_rcv_established+0xfba/0x2020 net/ipv4/tcp_input.c:6237    tcp_v4_do_rcv+0x96d/0xc70 net/ipv4/tcp_ipv4.c:1915    tcp_v4_rcv+0x2dc0/0x37f0 net/ipv4/tcp_ipv4.c:2350    ip_protocol_deliver_rcu+0x22e/0x440 net/ipv4/ip_input.c:205    ip_local_deliver_finish+0x341/0x5f0 net/ipv4/ip_input.c:233    NF_HOOK+0x3a4/0x450 include/linux/netfilter.h:314    NF_HOOK+0x3a4/0x450 include/linux/netfilter.h:314    __netif_receive_skb_one_core net/core/dev.c:5662 [inline]    __netif_receive_skb+0x2bf/0x650 net/core/dev.c:5775    process_backlog+0x662/0x15b0 net/core/dev.c:6107    __napi_poll+0xcb/0x490 net/core/dev.c:6771    napi_poll net/core/dev.c:6840 [inline]    net_rx_action+0x89b/0x1240 net/core/dev.c:6962    handle_softirqs+0x2c5/0x980 kernel/softirq.c:554    do_softirq+0x11b/0x1e0 kernel/softirq.c:455    \u0026lt;/IRQ\u0026gt;    \u0026lt;TASK\u0026gt;    __local_bh_enable_ip+0x1bb/0x200 kernel/softirq.c:382    local_bh_enable include/linux/bottom_half.h:33 [inline]    rcu_read_unlock_bh include/linux/rcupdate.h:919 [inline]    __dev_queue_xmit+0x1764/0x3e80 net/core/dev.c:4451    dev_queue_xmit include/linux/netdevice.h:3094 [inline]    neigh_hh_output include/net/neighbour.h:526 [inline]    neigh_output include/net/neighbour.h:540 [inline]    ip_finish_output2+0xd41/0x1390 net/ipv4/ip_output.c:236    ip_local_out net/ipv4/ip_output.c:130 [inline]    __ip_queue_xmit+0x118c/0x1b80 net/ipv4/ip_output.c:536    __tcp_transmit_skb+0x2544/0x3b30 net/ipv4/tcp_output.c:1466    tcp_transmit_skb net/ipv4/tcp_output.c:1484 [inline]    tcp_mtu_probe net/ipv4/tcp_output.c:2547 [inline]    tcp_write_xmit+0x641d/0x6bf0 net/ipv4/tcp_output.c:2752    __tcp_push_pending_frames+0x9b/0x360 net/ipv4/tcp_output.c:3015    tcp_push_pending_frames include/net/tcp.h:2107 [inline]    tcp_data_snd_check net/ipv4/tcp_input.c:5714 [inline]    tcp_rcv_established+0x1026/0x2020 net/ipv4/tcp_input.c:6239    tcp_v4_do_rcv+0x96d/0xc70 net/ipv4/tcp_ipv4.c:1915    sk_backlog_rcv include/net/sock.h:1113 [inline]    __release_sock+0x214/0x350 net/core/sock.c:3072    release_sock+0x61/0x1f0 net/core/sock.c:3626    mptcp_push_ ---truncated---(CVE-2024-50083)","status":"published","published":"2024-11-08T11:07:50Z","modified":"2026-08-18T01:18:38.732529946Z","cvss":[{"version":"3.1","score":8.8,"vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H","level":"high"}],"updated_at":"2026-11-02T15:52:42.253598Z"},{"id":"OESA-2024-2371","title":"kernel security update","description":"The Linux Kernel, the operating system core itself.\r\n\r\nSecurity Fix(es):\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  ipv6: avoid use-after-free in ip6_fragment()  Blamed commit claimed rcu_read_lock() was held by ip6_fragment() callers.  It seems to not be always true, at least for UDP stack.  syzbot reported:  BUG: KASAN: use-after-free in ip6_dst_idev include/net/ip6_fib.h:245 [inline] BUG: KASAN: use-after-free in ip6_fragment+0x2724/0x2770 net/ipv6/ip6_output.c:951 Read of size 8 at addr ffff88801d403e80 by task syz-executor.3/7618  CPU: 1 PID: 7618 Comm: syz-executor.3 Not tainted 6.1.0-rc6-syzkaller-00012-g4312098baf37 #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 10/26/2022 Call Trace:  \u0026lt;TASK\u0026gt;  __dump_stack lib/dump_stack.c:88 [inline]  dump_stack_lvl+0xd1/0x138 lib/dump_stack.c:106  print_address_description mm/kasan/report.c:284 [inline]  print_report+0x15e/0x45d mm/kasan/report.c:395  kasan_report+0xbf/0x1f0 mm/kasan/report.c:495  ip6_dst_idev include/net/ip6_fib.h:245 [inline]  ip6_fragment+0x2724/0x2770 net/ipv6/ip6_output.c:951  __ip6_finish_output net/ipv6/ip6_output.c:193 [inline]  ip6_finish_output+0x9a3/0x1170 net/ipv6/ip6_output.c:206  NF_HOOK_COND include/linux/netfilter.h:291 [inline]  ip6_output+0x1f1/0x540 net/ipv6/ip6_output.c:227  dst_output include/net/dst.h:445 [inline]  ip6_local_out+0xb3/0x1a0 net/ipv6/output_core.c:161  ip6_send_skb+0xbb/0x340 net/ipv6/ip6_output.c:1966  udp_v6_send_skb+0x82a/0x18a0 net/ipv6/udp.c:1286  udp_v6_push_pending_frames+0x140/0x200 net/ipv6/udp.c:1313  udpv6_sendmsg+0x18da/0x2c80 net/ipv6/udp.c:1606  inet6_sendmsg+0x9d/0xe0 net/ipv6/af_inet6.c:665  sock_sendmsg_nosec net/socket.c:714 [inline]  sock_sendmsg+0xd3/0x120 net/socket.c:734  sock_write_iter+0x295/0x3d0 net/socket.c:1108  call_write_iter include/linux/fs.h:2191 [inline]  new_sync_write fs/read_write.c:491 [inline]  vfs_write+0x9ed/0xdd0 fs/read_write.c:584  ksys_write+0x1ec/0x250 fs/read_write.c:637  do_syscall_x64 arch/x86/entry/common.c:50 [inline]  do_syscall_64+0x39/0xb0 arch/x86/entry/common.c:80  entry_SYSCALL_64_after_hwframe+0x63/0xcd RIP: 0033:0x7fde3588c0d9 Code: 28 00 00 00 75 05 48 83 c4 28 c3 e8 f1 19 00 00 90 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 \u0026lt;48\u0026gt; 3d 01 f0 ff ff 73 01 c3 48 c7 c1 b8 ff ff ff f7 d8 64 89 01 48 RSP: 002b:00007fde365b6168 EFLAGS: 00000246 ORIG_RAX: 0000000000000001 RAX: ffffffffffffffda RBX: 00007fde359ac050 RCX: 00007fde3588c0d9 RDX: 000000000000ffdc RSI: 00000000200000c0 RDI: 000000000000000a RBP: 00007fde358e7ae9 R08: 0000000000000000 R09: 0000000000000000 R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000 R13: 00007fde35acfb1f R14: 00007fde365b6300 R15: 0000000000022000  \u0026lt;/TASK\u0026gt;  Allocated by task 7618:  kasan_save_stack+0x22/0x40 mm/kasan/common.c:45  kasan_set_track+0x25/0x30 mm/kasan/common.c:52  __kasan_slab_alloc+0x82/0x90 mm/kasan/common.c:325  kasan_slab_alloc include/linux/kasan.h:201 [inline]  slab_post_alloc_hook mm/slab.h:737 [inline]  slab_alloc_node mm/slub.c:3398 [inline]  slab_alloc mm/slub.c:3406 [inline]  __kmem_cache_alloc_lru mm/slub.c:3413 [inline]  kmem_cache_alloc+0x2b4/0x3d0 mm/slub.c:3422  dst_alloc+0x14a/0x1f0 net/core/dst.c:92  ip6_dst_alloc+0x32/0xa0 net/ipv6/route.c:344  ip6_rt_pcpu_alloc net/ipv6/route.c:1369 [inline]  rt6_make_pcpu_route net/ipv6/route.c:1417 [inline]  ip6_pol_route+0x901/0x1190 net/ipv6/route.c:2254  pol_lookup_func include/net/ip6_fib.h:582 [inline]  fib6_rule_lookup+0x52e/0x6f0 net/ipv6/fib6_rules.c:121  ip6_route_output_flags_noref+0x2e6/0x380 net/ipv6/route.c:2625  ip6_route_output_flags+0x76/0x320 net/ipv6/route.c:2638  ip6_route_output include/net/ip6_route.h:98 [inline]  ip6_dst_lookup_tail+0x5ab/0x1620 net/ipv6/ip6_output.c:1092  ip6_dst_lookup_flow+0x90/0x1d0 net/ipv6/ip6_output.c:1222  ip6_sk_dst_lookup_flow+0x553/0x980 net/ipv6/ip6_output.c:1260  udpv6_sendmsg+0x151d/0x2c80 net/ipv6/udp.c:1554  inet6_sendmsg+0x9d/0xe0 net/ipv6/af_inet6.c:665  sock_sendmsg_nosec n ---truncated---(CVE-2022-48956)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  ethernet: aeroflex: fix potential skb leak in greth_init_rings()  The greth_init_rings() function won\u0026apos;t free the newly allocated skb when dma_mapping_error() returns error, so add dev_kfree_skb() to fix it.  Compile tested only.(CVE-2022-48958)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  net: hisilicon: Fix potential use-after-free in hix5hd2_rx()  The skb is delivered to napi_gro_receive() which may free it, after calling this, dereferencing skb may trigger use-after-free.(CVE-2022-48960)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  net: mdio: fix unbalanced fwnode reference count in mdio_device_release()  There is warning report about of_node refcount leak while probing mdio device:  OF: ERROR: memory leak, expected refcount 1 instead of 2, of_node_get()/of_node_put() unbalanced - destroy cset entry: attach overlay node /spi/soc@0/mdio@710700c0/ethernet@4  In of_mdiobus_register_device(), we increase fwnode refcount by fwnode_handle_get() before associating the of_node with mdio device, but it has never been decreased in normal path. Since that, in mdio_device_release(), it needs to call fwnode_handle_put() in addition instead of calling kfree() directly.  After above, just calling mdio_device_free() in the error handle path of of_mdiobus_register_device() is enough to keep the refcount balanced.(CVE-2022-48961)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  net: hisilicon: Fix potential use-after-free in hisi_femac_rx()  The skb is delivered to napi_gro_receive() which may free it, after calling this, dereferencing skb may trigger use-after-free.(CVE-2022-48962)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  net: mvneta: Prevent out of bounds read in mvneta_config_rss()  The pp-\u0026gt;indir[0] value comes from the user.  It is passed to:   if (cpu_online(pp-\u0026gt;rxq_def))  inside the mvneta_percpu_elect() function.  It needs bounds checkeding to ensure that it is not beyond the end of the cpu bitmap.(CVE-2022-48966)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  mac802154: fix missing INIT_LIST_HEAD in ieee802154_if_add()  Kernel fault injection test reports null-ptr-deref as follows:  BUG: kernel NULL pointer dereference, address: 0000000000000008 RIP: 0010:cfg802154_netdev_notifier_call+0x120/0x310 include/linux/list.h:114 Call Trace:  \u0026lt;TASK\u0026gt;  raw_notifier_call_chain+0x6d/0xa0 kernel/notifier.c:87  call_netdevice_notifiers_info+0x6e/0xc0 net/core/dev.c:1944  unregister_netdevice_many_notify+0x60d/0xcb0 net/core/dev.c:1982  unregister_netdevice_queue+0x154/0x1a0 net/core/dev.c:10879  register_netdevice+0x9a8/0xb90 net/core/dev.c:10083  ieee802154_if_add+0x6ed/0x7e0 net/mac802154/iface.c:659  ieee802154_register_hw+0x29c/0x330 net/mac802154/main.c:229  mcr20a_probe+0xaaa/0xcb1 drivers/net/ieee802154/mcr20a.c:1316  ieee802154_if_add() allocates wpan_dev as netdev\u0026apos;s private data, but not init the list in struct wpan_dev. cfg802154_netdev_notifier_call() manage the list when device register/unregister, and may lead to null-ptr-deref.  Use INIT_LIST_HEAD() on it to initialize it correctly.(CVE-2022-48972)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  gpiolib: fix memory leak in gpiochip_setup_dev()  Here is a backtrace report about memory leak detected in gpiochip_setup_dev():  unreferenced object 0xffff88810b406400 (size 512):   comm \u0026quot;python3\u0026quot;, pid 1682, jiffies 4295346908 (age 24.090s)   backtrace:     kmalloc_trace     device_add  device_private_init at drivers/base/core.c:3361    (inlined by) device_add at drivers/base/core.c:3411     cdev_device_add     gpiolib_cdev_register     gpiochip_setup_dev     gpiochip_add_data_with_key  gcdev_register() \u0026amp; gcdev_unregister() would call device_add() \u0026amp; device_del() (no matter CONFIG_GPIO_CDEV is enabled or not) to register/unregister device.  However, if device_add() succeeds, some resource (like struct device_private allocated by device_private_init()) is not released by device_del().  Therefore, after device_add() succeeds by gcdev_register(), it needs to call put_device() to release resource in the error handle path.  Here we move forward the register of release function, and let it release every piece of resource by put_device() instead of kfree().  While at it, fix another subtle issue, i.e. when gc-\u0026gt;ngpio is equal to 0, we still call kcalloc() and, in case of further error, kfree() on the ZERO_PTR pointer, which is not NULL. It\u0026apos;s not a bug per se, but rather waste of the resources and potentially wrong expectation about contents of the gdev-\u0026gt;descs variable.(CVE-2022-48975)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  drm/shmem-helper: Remove errant put in error path  drm_gem_shmem_mmap() doesn\u0026apos;t own this reference, resulting in the GEM object getting prematurely freed leading to a later use-after-free.(CVE-2022-48981)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  Bluetooth: Fix crash when replugging CSR fake controllers  It seems fake CSR 5.0 clones can cause the suspend notifier to be registered twice causing the following kernel panic:  [   71.986122] Call Trace: [   71.986124]  \u0026lt;TASK\u0026gt; [   71.986125]  blocking_notifier_chain_register+0x33/0x60 [   71.986130]  hci_register_dev+0x316/0x3d0 [bluetooth 99b5497ea3d09708fa1366c1dc03288bf3cca8da] [   71.986154]  btusb_probe+0x979/0xd85 [btusb e1e0605a4f4c01984a4b9c8ac58c3666ae287477] [   71.986159]  ? __pm_runtime_set_status+0x1a9/0x300 [   71.986162]  ? ktime_get_mono_fast_ns+0x3e/0x90 [   71.986167]  usb_probe_interface+0xe3/0x2b0 [   71.986171]  really_probe+0xdb/0x380 [   71.986174]  ? pm_runtime_barrier+0x54/0x90 [   71.986177]  __driver_probe_device+0x78/0x170 [   71.986180]  driver_probe_device+0x1f/0x90 [   71.986183]  __device_attach_driver+0x89/0x110 [   71.986186]  ? driver_allows_async_probing+0x70/0x70 [   71.986189]  bus_for_each_drv+0x8c/0xe0 [   71.986192]  __device_attach+0xb2/0x1e0 [   71.986195]  bus_probe_device+0x92/0xb0 [   71.986198]  device_add+0x422/0x9a0 [   71.986201]  ? sysfs_merge_group+0xd4/0x110 [   71.986205]  usb_set_configuration+0x57a/0x820 [   71.986208]  usb_generic_driver_probe+0x4f/0x70 [   71.986211]  usb_probe_device+0x3a/0x110 [   71.986213]  really_probe+0xdb/0x380 [   71.986216]  ? pm_runtime_barrier+0x54/0x90 [   71.986219]  __driver_probe_device+0x78/0x170 [   71.986221]  driver_probe_device+0x1f/0x90 [   71.986224]  __device_attach_driver+0x89/0x110 [   71.986227]  ? driver_allows_async_probing+0x70/0x70 [   71.986230]  bus_for_each_drv+0x8c/0xe0 [   71.986232]  __device_attach+0xb2/0x1e0 [   71.986235]  bus_probe_device+0x92/0xb0 [   71.986237]  device_add+0x422/0x9a0 [   71.986239]  ? _dev_info+0x7d/0x98 [   71.986242]  ? blake2s_update+0x4c/0xc0 [   71.986246]  usb_new_device.cold+0x148/0x36d [   71.986250]  hub_event+0xa8a/0x1910 [   71.986255]  process_one_work+0x1c4/0x380 [   71.986259]  worker_thread+0x51/0x390 [   71.986262]  ? rescuer_thread+0x3b0/0x3b0 [   71.986264]  kthread+0xdb/0x110 [   71.986266]  ? kthread_complete_and_exit+0x20/0x20 [   71.986268]  ret_from_fork+0x1f/0x30 [   71.986273]  \u0026lt;/TASK\u0026gt; [   71.986274] ---[ end trace 0000000000000000 ]--- [   71.986284] btusb: probe of 2-1.6:1.0 failed with error -17(CVE-2022-48982)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  ASoC: soc-pcm: Add NULL check in BE reparenting  Add NULL check in dpcm_be_reparent API, to handle kernel NULL pointer dereference error. The issue occurred in fuzzing test.(CVE-2022-48992)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  Input: raydium_ts_i2c - fix memory leak in raydium_i2c_send()  There is a kmemleak when test the raydium_i2c_ts with bpf mock device:    unreferenced object 0xffff88812d3675a0 (size 8):     comm \u0026quot;python3\u0026quot;, pid 349, jiffies 4294741067 (age 95.695s)     hex dump (first 8 bytes):       11 0e 10 c0 01 00 04 00                          ........     backtrace:       [\u0026lt;0000000068427125\u0026gt;] __kmalloc+0x46/0x1b0       [\u0026lt;0000000090180f91\u0026gt;] raydium_i2c_send+0xd4/0x2bf [raydium_i2c_ts]       [\u0026lt;000000006e631aee\u0026gt;] raydium_i2c_initialize.cold+0xbc/0x3e4 [raydium_i2c_ts]       [\u0026lt;00000000dc6fcf38\u0026gt;] raydium_i2c_probe+0x3cd/0x6bc [raydium_i2c_ts]       [\u0026lt;00000000a310de16\u0026gt;] i2c_device_probe+0x651/0x680       [\u0026lt;00000000f5a96bf3\u0026gt;] really_probe+0x17c/0x3f0       [\u0026lt;00000000096ba499\u0026gt;] __driver_probe_device+0xe3/0x170       [\u0026lt;00000000c5acb4d9\u0026gt;] driver_probe_device+0x49/0x120       [\u0026lt;00000000264fe082\u0026gt;] __device_attach_driver+0xf7/0x150       [\u0026lt;00000000f919423c\u0026gt;] bus_for_each_drv+0x114/0x180       [\u0026lt;00000000e067feca\u0026gt;] __device_attach+0x1e5/0x2d0       [\u0026lt;0000000054301fc2\u0026gt;] bus_probe_device+0x126/0x140       [\u0026lt;00000000aad93b22\u0026gt;] device_add+0x810/0x1130       [\u0026lt;00000000c086a53f\u0026gt;] i2c_new_client_device+0x352/0x4e0       [\u0026lt;000000003c2c248c\u0026gt;] of_i2c_register_device+0xf1/0x110       [\u0026lt;00000000ffec4177\u0026gt;] of_i2c_notify+0x100/0x160   unreferenced object 0xffff88812d3675c8 (size 8):     comm \u0026quot;python3\u0026quot;, pid 349, jiffies 4294741070 (age 95.692s)     hex dump (first 8 bytes):       22 00 36 2d 81 88 ff ff                          \u0026quot;.6-....     backtrace:       [\u0026lt;0000000068427125\u0026gt;] __kmalloc+0x46/0x1b0       [\u0026lt;0000000090180f91\u0026gt;] raydium_i2c_send+0xd4/0x2bf [raydium_i2c_ts]       [\u0026lt;000000001d5c9620\u0026gt;] raydium_i2c_initialize.cold+0x223/0x3e4 [raydium_i2c_ts]       [\u0026lt;00000000dc6fcf38\u0026gt;] raydium_i2c_probe+0x3cd/0x6bc [raydium_i2c_ts]       [\u0026lt;00000000a310de16\u0026gt;] i2c_device_probe+0x651/0x680       [\u0026lt;00000000f5a96bf3\u0026gt;] really_probe+0x17c/0x3f0       [\u0026lt;00000000096ba499\u0026gt;] __driver_probe_device+0xe3/0x170       [\u0026lt;00000000c5acb4d9\u0026gt;] driver_probe_device+0x49/0x120       [\u0026lt;00000000264fe082\u0026gt;] __device_attach_driver+0xf7/0x150       [\u0026lt;00000000f919423c\u0026gt;] bus_for_each_drv+0x114/0x180       [\u0026lt;00000000e067feca\u0026gt;] __device_attach+0x1e5/0x2d0       [\u0026lt;0000000054301fc2\u0026gt;] bus_probe_device+0x126/0x140       [\u0026lt;00000000aad93b22\u0026gt;] device_add+0x810/0x1130       [\u0026lt;00000000c086a53f\u0026gt;] i2c_new_client_device+0x352/0x4e0       [\u0026lt;000000003c2c248c\u0026gt;] of_i2c_register_device+0xf1/0x110       [\u0026lt;00000000ffec4177\u0026gt;] of_i2c_notify+0x100/0x160  After BANK_SWITCH command from i2c BUS, no matter success or error happened, the tx_buf should be freed.(CVE-2022-48995)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  riscv: Sync efi page table\u0026apos;s kernel mappings before switching  The EFI page table is initially created as a copy of the kernel page table. With VMAP_STACK enabled, kernel stacks are allocated in the vmalloc area: if the stack is allocated in a new PGD (one that was not present at the moment of the efi page table creation or not synced in a previous vmalloc fault), the kernel will take a trap when switching to the efi page table when the vmalloc kernel stack is accessed, resulting in a kernel panic.  Fix that by updating the efi kernel mappings before switching to the efi page table.(CVE-2022-49004)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  ASoC: ops: Fix bounds check for _sx controls  For _sx controls the semantics of the max field is not the usual one, max is the number of steps rather than the maximum value. This means that our check in snd_soc_put_volsw_sx() needs to just check against the maximum value.(CVE-2022-49005)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  hwmon: (coretemp) fix pci device refcount leak in nv1a_ram_new()  As comment of pci_get_domain_bus_and_slot() says, it returns a pci device with refcount increment, when finish using it, the caller must decrement the reference count by calling pci_dev_put(). So call it after using to avoid refcount leak.(CVE-2022-49011)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  tipc: re-fetch skb cb after tipc_msg_validate  As the call trace shows, the original skb was freed in tipc_msg_validate(), and dereferencing the old skb cb would cause an use-after-free crash.    BUG: KASAN: use-after-free in tipc_crypto_rcv_complete+0x1835/0x2240 [tipc]   Call Trace:    \u0026lt;IRQ\u0026gt;    tipc_crypto_rcv_complete+0x1835/0x2240 [tipc]    tipc_crypto_rcv+0xd32/0x1ec0 [tipc]    tipc_rcv+0x744/0x1150 [tipc]   ...   Allocated by task 47078:    kmem_cache_alloc_node+0x158/0x4d0    __alloc_skb+0x1c1/0x270    tipc_buf_acquire+0x1e/0xe0 [tipc]    tipc_msg_create+0x33/0x1c0 [tipc]    tipc_link_build_proto_msg+0x38a/0x2100 [tipc]    tipc_link_timeout+0x8b8/0xef0 [tipc]    tipc_node_timeout+0x2a1/0x960 [tipc]    call_timer_fn+0x2d/0x1c0   ...   Freed by task 47078:    tipc_msg_validate+0x7b/0x440 [tipc]    tipc_crypto_rcv_complete+0x4b5/0x2240 [tipc]    tipc_crypto_rcv+0xd32/0x1ec0 [tipc]    tipc_rcv+0x744/0x1150 [tipc]  This patch fixes it by re-fetching the skb cb from the new allocated skb after calling tipc_msg_validate().(CVE-2022-49017)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  net/9p: Fix a potential socket leak in p9_socket_open  Both p9_fd_create_tcp() and p9_fd_create_unix() will call p9_socket_open(). If the creation of p9_trans_fd fails, p9_fd_create_tcp() and p9_fd_create_unix() will return an error directly instead of releasing the cscoket, which will result in a socket leak.  This patch adds sock_release() to fix the leak issue.(CVE-2022-49020)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  net: phy: fix null-ptr-deref while probe() failed  I got a null-ptr-deref report as following when doing fault injection test:  BUG: kernel NULL pointer dereference, address: 0000000000000058 Oops: 0000 [#1] PREEMPT SMP KASAN PTI CPU: 1 PID: 253 Comm: 507-spi-dm9051 Tainted: G    B            N 6.1.0-rc3+ Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.13.0-1ubuntu1.1 04/01/2014 RIP: 0010:klist_put+0x2d/0xd0 Call Trace:  \u0026lt;TASK\u0026gt;  klist_remove+0xf1/0x1c0  device_release_driver_internal+0x23e/0x2d0  bus_remove_device+0x1bd/0x240  device_del+0x357/0x770  phy_device_remove+0x11/0x30  mdiobus_unregister+0xa5/0x140  release_nodes+0x6a/0xa0  devres_release_all+0xf8/0x150  device_unbind_cleanup+0x19/0xd0  //probe path: phy_device_register()   device_add()  phy_connect   phy_attach_direct() //set device driver     probe() //it\u0026apos;s failed, driver is not bound     device_bind_driver() // probe failed, it\u0026apos;s not called  //remove path: phy_device_remove()   device_del()     device_release_driver_internal()       __device_release_driver() //dev-\u0026gt;drv is not NULL         klist_remove() \u0026lt;- knode_driver is not added yet, cause null-ptr-deref  In phy_attach_direct(), after setting the \u0026apos;dev-\u0026gt;driver\u0026apos;, probe() fails, device_bind_driver() is not called, so the knode_driver-\u0026gt;n_klist is not set, then it causes null-ptr-deref in __device_release_driver() while deleting device. Fix this by setting dev-\u0026gt;driver to NULL in the error path in phy_attach_direct().(CVE-2022-49021)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  wifi: cfg80211: fix buffer overflow in elem comparison  For vendor elements, the code here assumes that 5 octets are present without checking. Since the element itself is already checked to fit, we only need to check the length.(CVE-2022-49023)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  iio: health: afe4403: Fix oob read in afe4403_read_raw  KASAN report out-of-bounds read as follows:  BUG: KASAN: global-out-of-bounds in afe4403_read_raw+0x42e/0x4c0 Read of size 4 at addr ffffffffc02ac638 by task cat/279  Call Trace:  afe4403_read_raw  iio_read_channel_info  dev_attr_show  The buggy address belongs to the variable:  afe4403_channel_leds+0x18/0xffffffffffffe9e0  This issue can be reproduced by singe command:   $ cat /sys/bus/spi/devices/spi0.0/iio\\:device0/in_intensity6_raw  The array size of afe4403_channel_leds is less than channels, so access with chan-\u0026gt;address cause OOB read in afe4403_read_raw. Fix it by moving access before use it.(CVE-2022-49031)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  iio: health: afe4404: Fix oob read in afe4404_[read|write]_raw  KASAN report out-of-bounds read as follows:  BUG: KASAN: global-out-of-bounds in afe4404_read_raw+0x2ce/0x380 Read of size 4 at addr ffffffffc00e4658 by task cat/278  Call Trace:  afe4404_read_raw  iio_read_channel_info  dev_attr_show  The buggy address belongs to the variable:  afe4404_channel_leds+0x18/0xffffffffffffe9c0  This issue can be reproduce by singe command:   $ cat /sys/bus/i2c/devices/0-0058/iio\\:device0/in_intensity6_raw  The array size of afe4404_channel_leds and afe4404_channel_offdacs are less than channels, so access with chan-\u0026gt;address cause OOB read in afe4404_[read|write]_raw. Fix it by moving access before use them.(CVE-2022-49032)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nmemcg_write_event_control(): fix a user-triggerable oops\r\n\r\nwe are *not* guaranteed that anything past the terminating NUL\nis mapped (let alone initialized with anything sane).(CVE-2024-45021)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\ngtp: fix a potential NULL pointer dereference\r\n\r\nWhen sockfd_lookup() fails, gtp_encap_enable_socket() returns a\nNULL pointer, but its callers only check for error pointers thus miss\nthe NULL pointer case.\r\n\r\nFix it by returning an error pointer with the error code carried from\nsockfd_lookup().\r\n\r\n(I found this bug during code inspection.)(CVE-2024-46677)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\ndrm/amd/display: Check BIOS images before it is used\r\n\r\nBIOS images may fail to load and null checks are added before they are\nused.\r\n\r\nThis fixes 6 NULL_RETURNS issues reported by Coverity.(CVE-2024-46809)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nsmack: tcp: ipv4, fix incorrect labeling\r\n\r\nCurrently, Smack mirrors the label of incoming tcp/ipv4 connections:\nwhen a label \u0026apos;foo\u0026apos; connects to a label \u0026apos;bar\u0026apos; with tcp/ipv4,\n\u0026apos;foo\u0026apos; always gets \u0026apos;foo\u0026apos; in returned ipv4 packets. So,\n1) returned packets are incorrectly labeled (\u0026apos;foo\u0026apos; instead of \u0026apos;bar\u0026apos;)\n2) \u0026apos;bar\u0026apos; can write to \u0026apos;foo\u0026apos; without being authorized to write.\r\n\r\nHere is a scenario how to see this:\r\n\r\n* Take two machines, let\u0026apos;s call them C and S,\n   with active Smack in the default state\n   (no settings, no rules, no labeled hosts, only builtin labels)\r\n\r\n* At S, add Smack rule \u0026apos;foo bar w\u0026apos;\n   (labels \u0026apos;foo\u0026apos; and \u0026apos;bar\u0026apos; are instantiated at S at this moment)\r\n\r\n* At S, at label \u0026apos;bar\u0026apos;, launch a program\n   that listens for incoming tcp/ipv4 connections\r\n\r\n* From C, at label \u0026apos;foo\u0026apos;, connect to the listener at S.\n   (label \u0026apos;foo\u0026apos; is instantiated at C at this moment)\n   Connection succeedes and works.\r\n\r\n* Send some data in both directions.\n* Collect network traffic of this connection.\r\n\r\nAll packets in both directions are labeled with the CIPSO\nof the label \u0026apos;foo\u0026apos;. Hence, label \u0026apos;bar\u0026apos; writes to \u0026apos;foo\u0026apos; without\nbeing authorized, and even without ever being known at C.\r\n\r\nIf anybody cares: exactly the same happens with DCCP.\r\n\r\nThis behavior 1st manifested in release 2.6.29.4 (see Fixes below)\nand it looks unintentional. At least, no explanation was provided.\r\n\r\nI changed returned packes label into the \u0026apos;bar\u0026apos;,\nto bring it into line with the Smack documentation claims.(CVE-2024-47659)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nfsnotify: clear PARENT_WATCHED flags lazily\r\n\r\nIn some setups directories can have many (usually negative) dentries.\nHence __fsnotify_update_child_dentry_flags() function can take a\nsignificant amount of time. Since the bulk of this function happens\nunder inode-\u0026gt;i_lock this causes a significant contention on the lock\nwhen we remove the watch from the directory as the\n__fsnotify_update_child_dentry_flags() call from fsnotify_recalc_mask()\nraces with __fsnotify_update_child_dentry_flags() calls from\n__fsnotify_parent() happening on children. This can lead upto softlockup\nreports reported by users.\r\n\r\nFix the problem by calling fsnotify_update_children_dentry_flags() to\nset PARENT_WATCHED flags only when parent starts watching children.\r\n\r\nWhen parent stops watching children, clear false positive PARENT_WATCHED\nflags lazily in __fsnotify_parent() for each accessed child.(CVE-2024-47660)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nlib/generic-radix-tree.c: Fix rare race in __genradix_ptr_alloc()\r\n\r\nIf we need to increase the tree depth, allocate a new node, and then\nrace with another thread that increased the tree depth before us, we\u0026apos;ll\nstill have a preallocated node that might be used later.\r\n\r\nIf we then use that node for a new non-root node, it\u0026apos;ll still have a\npointer to the old root instead of being zeroed - fix this by zeroing it\nin the cmpxchg failure path.(CVE-2024-47668)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nwifi: iwlwifi: mvm: pause TCM when the firmware is stopped\r\n\r\nNot doing so will make us send a host command to the transport while the\nfirmware is not alive, which will trigger a WARNING.\r\n\r\nbad state = 0\nWARNING: CPU: 2 PID: 17434 at drivers/net/wireless/intel/iwlwifi/iwl-trans.c:115 iwl_trans_send_cmd+0x1cb/0x1e0 [iwlwifi]\nRIP: 0010:iwl_trans_send_cmd+0x1cb/0x1e0 [iwlwifi]\nCall Trace:\n \u0026lt;TASK\u0026gt;\n iwl_mvm_send_cmd+0x40/0xc0 [iwlmvm]\n iwl_mvm_config_scan+0x198/0x260 [iwlmvm]\n iwl_mvm_recalc_tcm+0x730/0x11d0 [iwlmvm]\n iwl_mvm_tcm_work+0x1d/0x30 [iwlmvm]\n process_one_work+0x29e/0x640\n worker_thread+0x2df/0x690\n ? rescuer_thread+0x540/0x540\n kthread+0x192/0x1e0\n ? set_kthread_struct+0x90/0x90\n ret_from_fork+0x22/0x30(CVE-2024-47673)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  f2fs: get rid of online repaire on corrupted directory  syzbot reports a f2fs bug as below:  kernel BUG at fs/f2fs/inode.c:896! RIP: 0010:f2fs_evict_inode+0x1598/0x15c0 fs/f2fs/inode.c:896 Call Trace:  evict+0x532/0x950 fs/inode.c:704  dispose_list fs/inode.c:747 [inline]  evict_inodes+0x5f9/0x690 fs/inode.c:797  generic_shutdown_super+0x9d/0x2d0 fs/super.c:627  kill_block_super+0x44/0x90 fs/super.c:1696  kill_f2fs_super+0x344/0x690 fs/f2fs/super.c:4898  deactivate_locked_super+0xc4/0x130 fs/super.c:473  cleanup_mnt+0x41f/0x4b0 fs/namespace.c:1373  task_work_run+0x24f/0x310 kernel/task_work.c:228  ptrace_notify+0x2d2/0x380 kernel/signal.c:2402  ptrace_report_syscall include/linux/ptrace.h:415 [inline]  ptrace_report_syscall_exit include/linux/ptrace.h:477 [inline]  syscall_exit_work+0xc6/0x190 kernel/entry/common.c:173  syscall_exit_to_user_mode_prepare kernel/entry/common.c:200 [inline]  __syscall_exit_to_user_mode_work kernel/entry/common.c:205 [inline]  syscall_exit_to_user_mode+0x279/0x370 kernel/entry/common.c:218  do_syscall_64+0x100/0x230 arch/x86/entry/common.c:89  entry_SYSCALL_64_after_hwframe+0x77/0x7f RIP: 0010:f2fs_evict_inode+0x1598/0x15c0 fs/f2fs/inode.c:896  Online repaire on corrupted directory in f2fs_lookup() can generate dirty data/meta while racing w/ readonly remount, it may leave dirty inode after filesystem becomes readonly, however, checkpoint() will skips flushing dirty inode in a state of readonly mode, result in above panic.  Let\u0026apos;s get rid of online repaire in f2fs_lookup(), and leave the work to fsck.f2fs.(CVE-2024-47690)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  f2fs: fix to avoid use-after-free in f2fs_stop_gc_thread()  syzbot reports a f2fs bug as below:   __dump_stack lib/dump_stack.c:88 [inline]  dump_stack_lvl+0x241/0x360 lib/dump_stack.c:114  print_report+0xe8/0x550 mm/kasan/report.c:491  kasan_report+0x143/0x180 mm/kasan/report.c:601  kasan_check_range+0x282/0x290 mm/kasan/generic.c:189  instrument_atomic_read_write include/linux/instrumented.h:96 [inline]  atomic_fetch_add_relaxed include/linux/atomic/atomic-instrumented.h:252 [inline]  __refcount_add include/linux/refcount.h:184 [inline]  __refcount_inc include/linux/refcount.h:241 [inline]  refcount_inc include/linux/refcount.h:258 [inline]  get_task_struct include/linux/sched/task.h:118 [inline]  kthread_stop+0xca/0x630 kernel/kthread.c:704  f2fs_stop_gc_thread+0x65/0xb0 fs/f2fs/gc.c:210  f2fs_do_shutdown+0x192/0x540 fs/f2fs/file.c:2283  f2fs_ioc_shutdown fs/f2fs/file.c:2325 [inline]  __f2fs_ioctl+0x443a/0xbe60 fs/f2fs/file.c:4325  vfs_ioctl fs/ioctl.c:51 [inline]  __do_sys_ioctl fs/ioctl.c:907 [inline]  __se_sys_ioctl+0xfc/0x170 fs/ioctl.c:893  do_syscall_x64 arch/x86/entry/common.c:52 [inline]  do_syscall_64+0xf3/0x230 arch/x86/entry/common.c:83  entry_SYSCALL_64_after_hwframe+0x77/0x7f  The root cause is below race condition, it may cause use-after-free issue in sbi-\u0026gt;gc_th pointer.  - remount  - f2fs_remount   - f2fs_stop_gc_thread    - kfree(gc_th)     - f2fs_ioc_shutdown      - f2fs_do_shutdown       - f2fs_stop_gc_thread        - kthread_stop(gc_th-\u0026gt;f2fs_gc_task)    : sbi-\u0026gt;gc_thread = NULL;  We will call f2fs_do_shutdown() in two paths: - for f2fs_ioc_shutdown() path, we should grab sb-\u0026gt;s_umount semaphore for fixing. - for f2fs_shutdown() path, it\u0026apos;s safe since caller has already grabbed sb-\u0026gt;s_umount semaphore.(CVE-2024-47691)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  nfsd: return -EINVAL when namelen is 0  When we have a corrupted main.sqlite in /var/lib/nfs/nfsdcld/, it may result in namelen being 0, which will cause memdup_user() to return ZERO_SIZE_PTR. When we access the name.data that has been assigned the value of ZERO_SIZE_PTR in nfs4_client_to_reclaim(), null pointer dereference is triggered.  [ T1205] ================================================================== [ T1205] BUG: KASAN: null-ptr-deref in nfs4_client_to_reclaim+0xe9/0x260 [ T1205] Read of size 1 at addr 0000000000000010 by task nfsdcld/1205 [ T1205] [ T1205] CPU: 11 PID: 1205 Comm: nfsdcld Not tainted 5.10.0-00003-g2c1423731b8d #406 [ T1205] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS ?-20190727_073836-buildvm-ppc64le-16.ppc.fedoraproject.org-3.fc31 04/01/2014 [ T1205] Call Trace: [ T1205]  dump_stack+0x9a/0xd0 [ T1205]  ? nfs4_client_to_reclaim+0xe9/0x260 [ T1205]  __kasan_report.cold+0x34/0x84 [ T1205]  ? nfs4_client_to_reclaim+0xe9/0x260 [ T1205]  kasan_report+0x3a/0x50 [ T1205]  nfs4_client_to_reclaim+0xe9/0x260 [ T1205]  ? nfsd4_release_lockowner+0x410/0x410 [ T1205]  cld_pipe_downcall+0x5ca/0x760 [ T1205]  ? nfsd4_cld_tracking_exit+0x1d0/0x1d0 [ T1205]  ? down_write_killable_nested+0x170/0x170 [ T1205]  ? avc_policy_seqno+0x28/0x40 [ T1205]  ? selinux_file_permission+0x1b4/0x1e0 [ T1205]  rpc_pipe_write+0x84/0xb0 [ T1205]  vfs_write+0x143/0x520 [ T1205]  ksys_write+0xc9/0x170 [ T1205]  ? __ia32_sys_read+0x50/0x50 [ T1205]  ? ktime_get_coarse_real_ts64+0xfe/0x110 [ T1205]  ? ktime_get_coarse_real_ts64+0xa2/0x110 [ T1205]  do_syscall_64+0x33/0x40 [ T1205]  entry_SYSCALL_64_after_hwframe+0x67/0xd1 [ T1205] RIP: 0033:0x7fdbdb761bc7 [ T1205] Code: 0f 00 f7 d8 64 89 02 48 c7 c0 ff ff ff ff eb b7 0f 1f 00 f3 0f 1e fa 64 8b 04 25 18 00 00 00 85 c0 75 10 b8 01 00 00 00 0f 05 \u0026lt;48\u0026gt; 3d 00 f0 ff ff 77 514 [ T1205] RSP: 002b:00007fff8c4b7248 EFLAGS: 00000246 ORIG_RAX: 0000000000000001 [ T1205] RAX: ffffffffffffffda RBX: 000000000000042b RCX: 00007fdbdb761bc7 [ T1205] RDX: 000000000000042b RSI: 00007fff8c4b75f0 RDI: 0000000000000008 [ T1205] RBP: 00007fdbdb761bb0 R08: 0000000000000000 R09: 0000000000000001 [ T1205] R10: 0000000000000000 R11: 0000000000000246 R12: 000000000000042b [ T1205] R13: 0000000000000008 R14: 00007fff8c4b75f0 R15: 0000000000000000 [ T1205] ==================================================================  Fix it by checking namelen.(CVE-2024-47692)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  IB/core: Fix ib_cache_setup_one error flow cleanup  When ib_cache_update return an error, we exit ib_cache_setup_one instantly with no proper cleanup, even though before this we had already successfully done gid_table_setup_one, that results in the kernel WARN below.  Do proper cleanup using gid_table_cleanup_one before returning the err in order to fix the issue.  WARNING: CPU: 4 PID: 922 at drivers/infiniband/core/cache.c:806 gid_table_release_one+0x181/0x1a0 Modules linked in: CPU: 4 UID: 0 PID: 922 Comm: c_repro Not tainted 6.11.0-rc1+ #3 Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS rel-1.13.0-0-gf21b5a4aeb02-prebuilt.qemu.org 04/01/2014 RIP: 0010:gid_table_release_one+0x181/0x1a0 Code: 44 8b 38 75 0c e8 2f cb 34 ff 4d 8b b5 28 05 00 00 e8 23 cb 34 ff 44 89 f9 89 da 4c 89 f6 48 c7 c7 d0 58 14 83 e8 4f de 21 ff \u0026lt;0f\u0026gt; 0b 4c 8b 75 30 e9 54 ff ff ff 48 8    3 c4 10 5b 5d 41 5c 41 5d 41 RSP: 0018:ffffc90002b835b0 EFLAGS: 00010286 RAX: 0000000000000000 RBX: 0000000000000000 RCX: ffffffff811c8527 RDX: 0000000000000000 RSI: ffffffff811c8534 RDI: 0000000000000001 RBP: ffff8881011b3d00 R08: ffff88810b3abe00 R09: 205d303839303631 R10: 666572207972746e R11: 72746e6520444947 R12: 0000000000000001 R13: ffff888106390000 R14: ffff8881011f2110 R15: 0000000000000001 FS:  00007fecc3b70800(0000) GS:ffff88813bd00000(0000) knlGS:0000000000000000 CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 0000000020000340 CR3: 000000010435a001 CR4: 00000000003706b0 DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400 Call Trace:  \u0026lt;TASK\u0026gt;  ? show_regs+0x94/0xa0  ? __warn+0x9e/0x1c0  ? gid_table_release_one+0x181/0x1a0  ? report_bug+0x1f9/0x340  ? gid_table_release_one+0x181/0x1a0  ? handle_bug+0xa2/0x110  ? exc_invalid_op+0x31/0xa0  ? asm_exc_invalid_op+0x16/0x20  ? __warn_printk+0xc7/0x180  ? __warn_printk+0xd4/0x180  ? gid_table_release_one+0x181/0x1a0  ib_device_release+0x71/0xe0  ? __pfx_ib_device_release+0x10/0x10  device_release+0x44/0xd0  kobject_put+0x135/0x3d0  put_device+0x20/0x30  rxe_net_add+0x7d/0xa0  rxe_newlink+0xd7/0x190  nldev_newlink+0x1b0/0x2a0  ? __pfx_nldev_newlink+0x10/0x10  rdma_nl_rcv_msg+0x1ad/0x2e0  rdma_nl_rcv_skb.constprop.0+0x176/0x210  netlink_unicast+0x2de/0x400  netlink_sendmsg+0x306/0x660  __sock_sendmsg+0x110/0x120  ____sys_sendmsg+0x30e/0x390  ___sys_sendmsg+0x9b/0xf0  ? kstrtouint+0x6e/0xa0  ? kstrtouint_from_user+0x7c/0xb0  ? get_pid_task+0xb0/0xd0  ? proc_fail_nth_write+0x5b/0x140  ? __fget_light+0x9a/0x200  ? preempt_count_add+0x47/0xa0  __sys_sendmsg+0x61/0xd0  do_syscall_64+0x50/0x110  entry_SYSCALL_64_after_hwframe+0x76/0x7e(CVE-2024-47693)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  RDMA/iwcm: Fix WARNING:at_kernel/workqueue.c:#check_flush_dependency  In the commit aee2424246f9 (\u0026quot;RDMA/iwcm: Fix a use-after-free related to destroying CM IDs\u0026quot;), the function flush_workqueue is invoked to flush the work queue iwcm_wq.  But at that time, the work queue iwcm_wq was created via the function alloc_ordered_workqueue without the flag WQ_MEM_RECLAIM.  Because the current process is trying to flush the whole iwcm_wq, if iwcm_wq doesn\u0026apos;t have the flag WQ_MEM_RECLAIM, verify that the current process is not reclaiming memory or running on a workqueue which doesn\u0026apos;t have the flag WQ_MEM_RECLAIM as that can break forward-progress guarantee leading to a deadlock.  The call trace is as below:  [  125.350876][ T1430] Call Trace: [  125.356281][ T1430]  \u0026lt;TASK\u0026gt; [ 125.361285][ T1430] ? __warn (kernel/panic.c:693) [ 125.367640][ T1430] ? check_flush_dependency (kernel/workqueue.c:3706 (discriminator 9)) [ 125.375689][ T1430] ? report_bug (lib/bug.c:180 lib/bug.c:219) [ 125.382505][ T1430] ? handle_bug (arch/x86/kernel/traps.c:239) [ 125.388987][ T1430] ? exc_invalid_op (arch/x86/kernel/traps.c:260 (discriminator 1)) [ 125.395831][ T1430] ? asm_exc_invalid_op (arch/x86/include/asm/idtentry.h:621) [ 125.403125][ T1430] ? check_flush_dependency (kernel/workqueue.c:3706 (discriminator 9)) [ 125.410984][ T1430] ? check_flush_dependency (kernel/workqueue.c:3706 (discriminator 9)) [ 125.418764][ T1430] __flush_workqueue (kernel/workqueue.c:3970) [ 125.426021][ T1430] ? __pfx___might_resched (kernel/sched/core.c:10151) [ 125.433431][ T1430] ? destroy_cm_id (drivers/infiniband/core/iwcm.c:375) iw_cm [ 125.441209][ T1430] ? __pfx___flush_workqueue (kernel/workqueue.c:3910) [ 125.473900][ T1430] ? _raw_spin_lock_irqsave (arch/x86/include/asm/atomic.h:107 include/linux/atomic/atomic-arch-fallback.h:2170 include/linux/atomic/atomic-instrumented.h:1302 include/asm-generic/qspinlock.h:111 include/linux/spinlock.h:187 include/linux/spinlock_api_smp.h:111 kernel/locking/spinlock.c:162) [ 125.473909][ T1430] ? __pfx__raw_spin_lock_irqsave (kernel/locking/spinlock.c:161) [ 125.482537][ T1430] _destroy_id (drivers/infiniband/core/cma.c:2044) rdma_cm [ 125.495072][ T1430] nvme_rdma_free_queue (drivers/nvme/host/rdma.c:656 drivers/nvme/host/rdma.c:650) nvme_rdma [ 125.505827][ T1430] nvme_rdma_reset_ctrl_work (drivers/nvme/host/rdma.c:2180) nvme_rdma [ 125.505831][ T1430] process_one_work (kernel/workqueue.c:3231) [ 125.515122][ T1430] worker_thread (kernel/workqueue.c:3306 kernel/workqueue.c:3393) [ 125.515127][ T1430] ? __pfx_worker_thread (kernel/workqueue.c:3339) [ 125.531837][ T1430] kthread (kernel/kthread.c:389) [ 125.539864][ T1430] ? __pfx_kthread (kernel/kthread.c:342) [ 125.550628][ T1430] ret_from_fork (arch/x86/kernel/process.c:147) [ 125.558840][ T1430] ? __pfx_kthread (kernel/kthread.c:342) [ 125.558844][ T1430] ret_from_fork_asm (arch/x86/entry/entry_64.S:257) [  125.566487][ T1430]  \u0026lt;/TASK\u0026gt; [  125.566488][ T1430] ---[ end trace 0000000000000000 ]---(CVE-2024-47696)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  nilfs2: fix potential null-ptr-deref in nilfs_btree_insert()  Patch series \u0026quot;nilfs2: fix potential issues with empty b-tree nodes\u0026quot;.  This series addresses three potential issues with empty b-tree nodes that can occur with corrupted filesystem images, including one recently discovered by syzbot.   This patch (of 3):  If a b-tree is broken on the device, and the b-tree height is greater than 2 (the level of the root node is greater than 1) even if the number of child nodes of the b-tree root is 0, a NULL pointer dereference occurs in nilfs_btree_prepare_insert(), which is called from nilfs_btree_insert().  This is because, when the number of child nodes of the b-tree root is 0, nilfs_btree_do_lookup() does not set the block buffer head in any of path[x].bp_bh, leaving it as the initial value of NULL, but if the level of the b-tree root node is greater than 1, nilfs_btree_get_nonroot_node(), which accesses the buffer memory of path[x].bp_bh, is called.  Fix this issue by adding a check to nilfs_btree_root_broken(), which performs sanity checks when reading the root node from the device, to detect this inconsistency.  Thanks to Lizhi Xu for trying to solve the bug and clarifying the cause early on.(CVE-2024-47699)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  ext4: avoid OOB when system.data xattr changes underneath the filesystem  When looking up for an entry in an inlined directory, if e_value_offs is changed underneath the filesystem by some change in the block device, it will lead to an out-of-bounds access that KASAN detects as an UAF.  EXT4-fs (loop0): mounted filesystem 00000000-0000-0000-0000-000000000000 r/w without journal. Quota mode: none. loop0: detected capacity change from 2048 to 2047 ================================================================== BUG: KASAN: use-after-free in ext4_search_dir+0xf2/0x1c0 fs/ext4/namei.c:1500 Read of size 1 at addr ffff88803e91130f by task syz-executor269/5103  CPU: 0 UID: 0 PID: 5103 Comm: syz-executor269 Not tainted 6.11.0-rc4-syzkaller #0 Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.16.3-debian-1.16.3-2~bpo12+1 04/01/2014 Call Trace:  \u0026lt;TASK\u0026gt;  __dump_stack lib/dump_stack.c:93 [inline]  dump_stack_lvl+0x241/0x360 lib/dump_stack.c:119  print_address_description mm/kasan/report.c:377 [inline]  print_report+0x169/0x550 mm/kasan/report.c:488  kasan_report+0x143/0x180 mm/kasan/report.c:601  ext4_search_dir+0xf2/0x1c0 fs/ext4/namei.c:1500  ext4_find_inline_entry+0x4be/0x5e0 fs/ext4/inline.c:1697  __ext4_find_entry+0x2b4/0x1b30 fs/ext4/namei.c:1573  ext4_lookup_entry fs/ext4/namei.c:1727 [inline]  ext4_lookup+0x15f/0x750 fs/ext4/namei.c:1795  lookup_one_qstr_excl+0x11f/0x260 fs/namei.c:1633  filename_create+0x297/0x540 fs/namei.c:3980  do_symlinkat+0xf9/0x3a0 fs/namei.c:4587  __do_sys_symlinkat fs/namei.c:4610 [inline]  __se_sys_symlinkat fs/namei.c:4607 [inline]  __x64_sys_symlinkat+0x95/0xb0 fs/namei.c:4607  do_syscall_x64 arch/x86/entry/common.c:52 [inline]  do_syscall_64+0xf3/0x230 arch/x86/entry/common.c:83  entry_SYSCALL_64_after_hwframe+0x77/0x7f RIP: 0033:0x7f3e73ced469 Code: 28 00 00 00 75 05 48 83 c4 28 c3 e8 21 18 00 00 90 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 \u0026lt;48\u0026gt; 3d 01 f0 ff ff 73 01 c3 48 c7 c1 b8 ff ff ff f7 d8 64 89 01 48 RSP: 002b:00007fff4d40c258 EFLAGS: 00000246 ORIG_RAX: 000000000000010a RAX: ffffffffffffffda RBX: 0032656c69662f2e RCX: 00007f3e73ced469 RDX: 0000000020000200 RSI: 00000000ffffff9c RDI: 00000000200001c0 RBP: 0000000000000000 R08: 00007fff4d40c290 R09: 00007fff4d40c290 R10: 0023706f6f6c2f76 R11: 0000000000000246 R12: 00007fff4d40c27c R13: 0000000000000003 R14: 431bde82d7b634db R15: 00007fff4d40c2b0  \u0026lt;/TASK\u0026gt;  Calling ext4_xattr_ibody_find right after reading the inode with ext4_get_inode_loc will lead to a check of the validity of the xattrs, avoiding this problem.(CVE-2024-47701)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  bpf, lsm: Add check for BPF LSM return value  A bpf prog returning a positive number attached to file_alloc_security hook makes kernel panic.  This happens because file system can not filter out the positive number returned by the LSM prog using IS_ERR, and misinterprets this positive number as a file pointer.  Given that hook file_alloc_security never returned positive number before the introduction of BPF LSM, and other BPF LSM hooks may encounter similar issues, this patch adds LSM return value check in verifier, to ensure no unexpected value is returned.(CVE-2024-47703)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  block: fix potential invalid pointer dereference in blk_add_partition  The blk_add_partition() function initially used a single if-condition (IS_ERR(part)) to check for errors when adding a partition. This was modified to handle the specific case of -ENXIO separately, allowing the function to proceed without logging the error in this case. However, this change unintentionally left a path where md_autodetect_dev() could be called without confirming that part is a valid pointer.  This commit separates the error handling logic by splitting the initial if-condition, improving code readability and handling specific error scenarios explicitly. The function now distinguishes the general error case from -ENXIO without altering the existing behavior of md_autodetect_dev() calls.(CVE-2024-47705)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  jfs: fix out-of-bounds in dbNextAG() and diAlloc()  In dbNextAG() , there is no check for the case where bmp-\u0026gt;db_numag is greater or same than MAXAG due to a polluted image, which causes an out-of-bounds. Therefore, a bounds check should be added in dbMount().  And in dbNextAG(), a check for the case where agpref is greater than bmp-\u0026gt;db_numag should be added, so an out-of-bounds exception should be prevented.  Additionally, a check for the case where agno is greater or same than MAXAG should be added in diAlloc() to prevent out-of-bounds.(CVE-2024-47723)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  padata: use integer wrap around to prevent deadlock on seq_nr overflow  When submitting more than 2^32 padata objects to padata_do_serial, the current sorting implementation incorrectly sorts padata objects with overflowed seq_nr, causing them to be placed before existing objects in the reorder list. This leads to a deadlock in the serialization process as padata_find_next cannot match padata-\u0026gt;seq_nr and pd-\u0026gt;processed because the padata instance with overflowed seq_nr will be selected next.  To fix this, we use an unsigned integer wrap around to correctly sort padata objects in scenarios with integer overflow.(CVE-2024-47739)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  firmware_loader: Block path traversal  Most firmware names are hardcoded strings, or are constructed from fairly constrained format strings where the dynamic parts are just some hex numbers or such.  However, there are a couple codepaths in the kernel where firmware file names contain string components that are passed through from a device or semi-privileged userspace; the ones I could find (not counting interfaces that require root privileges) are:   - lpfc_sli4_request_firmware_update() seems to construct the firmware    filename from \u0026quot;ModelName\u0026quot;, a string that was previously parsed out of    some descriptor (\u0026quot;Vital Product Data\u0026quot;) in lpfc_fill_vpd()  - nfp_net_fw_find() seems to construct a firmware filename from a model    name coming from nfp_hwinfo_lookup(pf-\u0026gt;hwinfo, \u0026quot;nffw.partno\u0026quot;), which I    think parses some descriptor that was read from the device.    (But this case likely isn\u0026apos;t exploitable because the format string looks    like \u0026quot;netronome/nic_%s\u0026quot;, and there shouldn\u0026apos;t be any *folders* starting    with \u0026quot;netronome/nic_\u0026quot;. The previous case was different because there,    the \u0026quot;%s\u0026quot; is *at the start* of the format string.)  - module_flash_fw_schedule() is reachable from the    ETHTOOL_MSG_MODULE_FW_FLASH_ACT netlink command, which is marked as    GENL_UNS_ADMIN_PERM (meaning CAP_NET_ADMIN inside a user namespace is    enough to pass the privilege check), and takes a userspace-provided    firmware name.    (But I think to reach this case, you need to have CAP_NET_ADMIN over a    network namespace that a special kind of ethernet device is mapped into,    so I think this is not a viable attack path in practice.)  Fix it by rejecting any firmware names containing \u0026quot;..\u0026quot; path components.  For what it\u0026apos;s worth, I went looking and haven\u0026apos;t found any USB device drivers that use the firmware loader dangerously.(CVE-2024-47742)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  vhost_vdpa: assign irq bypass producer token correctly  We used to call irq_bypass_unregister_producer() in vhost_vdpa_setup_vq_irq() which is problematic as we don\u0026apos;t know if the token pointer is still valid or not.  Actually, we use the eventfd_ctx as the token so the life cycle of the token should be bound to the VHOST_SET_VRING_CALL instead of vhost_vdpa_setup_vq_irq() which could be called by set_status().  Fixing this by setting up irq bypass producer\u0026apos;s token when handling VHOST_SET_VRING_CALL and un-registering the producer before calling vhost_vring_ioctl() to prevent a possible use after free as eventfd could have been released in vhost_vring_ioctl(). And such registering and unregistering will only be done if DRIVER_OK is set.(CVE-2024-47748)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  PCI: keystone: Fix if-statement expression in ks_pcie_quirk()  This code accidentally uses \u0026amp;\u0026amp; where || was intended.  It potentially results in a NULL dereference.  Thus, fix the if-statement expression to use the correct condition.  [kwilczynski: commit log](CVE-2024-47756)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  nbd: fix race between timeout and normal completion  If request timetout is handled by nbd_requeue_cmd(), normal completion has to be stopped for avoiding to complete this requeued request, other use-after-free can be triggered.  Fix the race by clearing NBD_CMD_INFLIGHT in nbd_requeue_cmd(), meantime make sure that cmd-\u0026gt;lock is grabbed for clearing the flag and the requeue.(CVE-2024-49855)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  efistub/tpm: Use ACPI reclaim memory for event log to avoid corruption  The TPM event log table is a Linux specific construct, where the data produced by the GetEventLog() boot service is cached in memory, and passed on to the OS using an EFI configuration table.  The use of EFI_LOADER_DATA here results in the region being left unreserved in the E820 memory map constructed by the EFI stub, and this is the memory description that is passed on to the incoming kernel by kexec, which is therefore unaware that the region should be reserved.  Even though the utility of the TPM2 event log after a kexec is questionable, any corruption might send the parsing code off into the weeds and crash the kernel. So let\u0026apos;s use EFI_ACPI_RECLAIM_MEMORY instead, which is always treated as reserved by the E820 conversion logic.(CVE-2024-49858)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  ACPI: sysfs: validate return type of _STR method  Only buffer objects are valid return values of _STR.  If something else is returned description_show() will access invalid memory.(CVE-2024-49860)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  vhost/scsi: null-ptr-dereference in vhost_scsi_get_req()  Since commit 3f8ca2e115e5 (\u0026quot;vhost/scsi: Extract common handling code from control queue handler\u0026quot;) a null pointer dereference bug can be triggered when guest sends an SCSI AN request.  In vhost_scsi_ctl_handle_vq(), `vc.target` is assigned with `\u0026amp;v_req.tmf.lun[1]` within a switch-case block and is then passed to vhost_scsi_get_req() which extracts `vc-\u0026gt;req` and `tpg`. However, for a `VIRTIO_SCSI_T_AN_*` request, tpg is not required, so `vc.target` is set to NULL in this branch. Later, in vhost_scsi_get_req(), `vc-\u0026gt;target` is dereferenced without being checked, leading to a null pointer dereference bug. This bug can be triggered from guest.  When this bug occurs, the vhost_worker process is killed while holding `vq-\u0026gt;mutex` and the corresponding tpg will remain occupied indefinitely.  Below is the KASAN report: Oops: general protection fault, probably for non-canonical address 0xdffffc0000000000: 0000 [#1] PREEMPT SMP KASAN NOPTI KASAN: null-ptr-deref in range [0x0000000000000000-0x0000000000000007] CPU: 1 PID: 840 Comm: poc Not tainted 6.10.0+ #1 Hardware name: QEMU Ubuntu 24.04 PC (i440FX + PIIX, 1996), BIOS 1.16.3-debian-1.16.3-2 04/01/2014 RIP: 0010:vhost_scsi_get_req+0x165/0x3a0 Code: 00 fc ff df 48 89 fa 48 c1 ea 03 80 3c 02 00 0f 85 2b 02 00 00 48 b8 00 00 00 00 00 fc ff df 4d 8b 65 30 4c 89 e2 48 c1 ea 03 \u0026lt;0f\u0026gt; b6 04 02 4c 89 e2 83 e2 07 38 d0 7f 08 84 c0 0f 85 be 01 00 00 RSP: 0018:ffff888017affb50 EFLAGS: 00010246 RAX: dffffc0000000000 RBX: ffff88801b000000 RCX: 0000000000000000 RDX: 0000000000000000 RSI: 0000000000000000 RDI: ffff888017affcb8 RBP: ffff888017affb80 R08: 0000000000000000 R09: 0000000000000000 R10: 0000000000000000 R11: 0000000000000000 R12: 0000000000000000 R13: ffff888017affc88 R14: ffff888017affd1c R15: ffff888017993000 FS:  000055556e076500(0000) GS:ffff88806b100000(0000) knlGS:0000000000000000 CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 00000000200027c0 CR3: 0000000010ed0004 CR4: 0000000000370ef0 Call Trace:  \u0026lt;TASK\u0026gt;  ? show_regs+0x86/0xa0  ? die_addr+0x4b/0xd0  ? exc_general_protection+0x163/0x260  ? asm_exc_general_protection+0x27/0x30  ? vhost_scsi_get_req+0x165/0x3a0  vhost_scsi_ctl_handle_vq+0x2a4/0xca0  ? __pfx_vhost_scsi_ctl_handle_vq+0x10/0x10  ? __switch_to+0x721/0xeb0  ? __schedule+0xda5/0x5710  ? __kasan_check_write+0x14/0x30  ? _raw_spin_lock+0x82/0xf0  vhost_scsi_ctl_handle_kick+0x52/0x90  vhost_run_work_list+0x134/0x1b0  vhost_task_fn+0x121/0x350 ...  \u0026lt;/TASK\u0026gt; ---[ end trace 0000000000000000 ]---  Let\u0026apos;s add a check in vhost_scsi_get_req.  [whitespace fixes](CVE-2024-49863)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  ocfs2: fix possible null-ptr-deref in ocfs2_set_buffer_uptodate  When doing cleanup, if flags without OCFS2_BH_READAHEAD, it may trigger NULL pointer dereference in the following ocfs2_set_buffer_uptodate() if bh is NULL.(CVE-2024-49877)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  drm: omapdrm: Add missing check for alloc_ordered_workqueue  As it may return NULL pointer and cause NULL pointer dereference. Add check for the return value of alloc_ordered_workqueue.(CVE-2024-49879)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  ext4: update orig_path in ext4_find_extent()  In ext4_find_extent(), if the path is not big enough, we free it and set *orig_path to NULL. But after reallocating and successfully initializing the path, we don\u0026apos;t update *orig_path, in which case the caller gets a valid path but a NULL ppath, and this may cause a NULL pointer dereference or a path memory leak. For example:  ext4_split_extent   path = *ppath = 2000   ext4_find_extent     if (depth \u0026gt; path[0].p_maxdepth)       kfree(path = 2000);       *orig_path = path = NULL;       path = kcalloc() = 3000   ext4_split_extent_at(*ppath = NULL)     path = *ppath;     ex = path[depth].p_ext;     // NULL pointer dereference!  ================================================================== BUG: kernel NULL pointer dereference, address: 0000000000000010 CPU: 6 UID: 0 PID: 576 Comm: fsstress Not tainted 6.11.0-rc2-dirty #847 RIP: 0010:ext4_split_extent_at+0x6d/0x560 Call Trace:  \u0026lt;TASK\u0026gt;  ext4_split_extent.isra.0+0xcb/0x1b0  ext4_ext_convert_to_initialized+0x168/0x6c0  ext4_ext_handle_unwritten_extents+0x325/0x4d0  ext4_ext_map_blocks+0x520/0xdb0  ext4_map_blocks+0x2b0/0x690  ext4_iomap_begin+0x20e/0x2c0 [...] ==================================================================  Therefore, *orig_path is updated when the extent lookup succeeds, so that the caller can safely use path or *ppath.(CVE-2024-49881)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  ext4: fix double brelse() the buffer of the extents path  In ext4_ext_try_to_merge_up(), set path[1].p_bh to NULL after it has been released, otherwise it may be released twice. An example of what triggers this is as follows:    split2    map    split1 |--------|-------|--------|  ext4_ext_map_blocks  ext4_ext_handle_unwritten_extents   ext4_split_convert_extents    // path-\u0026gt;p_depth == 0    ext4_split_extent      // 1. do split1      ext4_split_extent_at        |ext4_ext_insert_extent        |  ext4_ext_create_new_leaf        |    ext4_ext_grow_indepth        |      le16_add_cpu(\u0026amp;neh-\u0026gt;eh_depth, 1)        |    ext4_find_extent        |      // return -ENOMEM        |// get error and try zeroout        |path = ext4_find_extent        |  path-\u0026gt;p_depth = 1        |ext4_ext_try_to_merge        |  ext4_ext_try_to_merge_up        |    path-\u0026gt;p_depth = 0        |    brelse(path[1].p_bh)  ---\u0026gt; not set to NULL here        |// zeroout success      // 2. update path      ext4_find_extent      // 3. do split2      ext4_split_extent_at        ext4_ext_insert_extent          ext4_ext_create_new_leaf            ext4_ext_grow_indepth              le16_add_cpu(\u0026amp;neh-\u0026gt;eh_depth, 1)            ext4_find_extent              path[0].p_bh = NULL;              path-\u0026gt;p_depth = 1              read_extent_tree_block  ---\u0026gt; return err              // path[1].p_bh is still the old value              ext4_free_ext_path                ext4_ext_drop_refs                  // path-\u0026gt;p_depth == 1                  brelse(path[1].p_bh)  ---\u0026gt; brelse a buffer twice  Finally got the following WARRNING when removing the buffer from lru:  ============================================ VFS: brelse: Trying to free free buffer WARNING: CPU: 2 PID: 72 at fs/buffer.c:1241 __brelse+0x58/0x90 CPU: 2 PID: 72 Comm: kworker/u19:1 Not tainted 6.9.0-dirty #716 RIP: 0010:__brelse+0x58/0x90 Call Trace:  \u0026lt;TASK\u0026gt;  __find_get_block+0x6e7/0x810  bdev_getblk+0x2b/0x480  __ext4_get_inode_loc+0x48a/0x1240  ext4_get_inode_loc+0xb2/0x150  ext4_reserve_inode_write+0xb7/0x230  __ext4_mark_inode_dirty+0x144/0x6a0  ext4_ext_insert_extent+0x9c8/0x3230  ext4_ext_map_blocks+0xf45/0x2dc0  ext4_map_blocks+0x724/0x1700  ext4_do_writepages+0x12d6/0x2a70 [...] ============================================(CVE-2024-49882)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  ext4: aovid use-after-free in ext4_ext_insert_extent()  As Ojaswin mentioned in Link, in ext4_ext_insert_extent(), if the path is reallocated in ext4_ext_create_new_leaf(), we\u0026apos;ll use the stale path and cause UAF. Below is a sample trace with dummy values:  ext4_ext_insert_extent   path = *ppath = 2000   ext4_ext_create_new_leaf(ppath)     ext4_find_extent(ppath)       path = *ppath = 2000       if (depth \u0026gt; path[0].p_maxdepth)             kfree(path = 2000);             *ppath = path = NULL;       path = kcalloc() = 3000       *ppath = 3000;       return path;   /* here path is still 2000, UAF! */   eh = path[depth].p_hdr  ================================================================== BUG: KASAN: slab-use-after-free in ext4_ext_insert_extent+0x26d4/0x3330 Read of size 8 at addr ffff8881027bf7d0 by task kworker/u36:1/179 CPU: 3 UID: 0 PID: 179 Comm: kworker/u6:1 Not tainted 6.11.0-rc2-dirty #866 Call Trace:  \u0026lt;TASK\u0026gt;  ext4_ext_insert_extent+0x26d4/0x3330  ext4_ext_map_blocks+0xe22/0x2d40  ext4_map_blocks+0x71e/0x1700  ext4_do_writepages+0x1290/0x2800 [...]  Allocated by task 179:  ext4_find_extent+0x81c/0x1f70  ext4_ext_map_blocks+0x146/0x2d40  ext4_map_blocks+0x71e/0x1700  ext4_do_writepages+0x1290/0x2800  ext4_writepages+0x26d/0x4e0  do_writepages+0x175/0x700 [...]  Freed by task 179:  kfree+0xcb/0x240  ext4_find_extent+0x7c0/0x1f70  ext4_ext_insert_extent+0xa26/0x3330  ext4_ext_map_blocks+0xe22/0x2d40  ext4_map_blocks+0x71e/0x1700  ext4_do_writepages+0x1290/0x2800  ext4_writepages+0x26d/0x4e0  do_writepages+0x175/0x700 [...] ==================================================================  So use *ppath to update the path to avoid the above problem.(CVE-2024-49883)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  ext4: fix slab-use-after-free in ext4_split_extent_at()  We hit the following use-after-free:  ================================================================== BUG: KASAN: slab-use-after-free in ext4_split_extent_at+0xba8/0xcc0 Read of size 2 at addr ffff88810548ed08 by task kworker/u20:0/40 CPU: 0 PID: 40 Comm: kworker/u20:0 Not tainted 6.9.0-dirty #724 Call Trace:  \u0026lt;TASK\u0026gt;  kasan_report+0x93/0xc0  ext4_split_extent_at+0xba8/0xcc0  ext4_split_extent.isra.0+0x18f/0x500  ext4_split_convert_extents+0x275/0x750  ext4_ext_handle_unwritten_extents+0x73e/0x1580  ext4_ext_map_blocks+0xe20/0x2dc0  ext4_map_blocks+0x724/0x1700  ext4_do_writepages+0x12d6/0x2a70 [...]  Allocated by task 40:  __kmalloc_noprof+0x1ac/0x480  ext4_find_extent+0xf3b/0x1e70  ext4_ext_map_blocks+0x188/0x2dc0  ext4_map_blocks+0x724/0x1700  ext4_do_writepages+0x12d6/0x2a70 [...]  Freed by task 40:  kfree+0xf1/0x2b0  ext4_find_extent+0xa71/0x1e70  ext4_ext_insert_extent+0xa22/0x3260  ext4_split_extent_at+0x3ef/0xcc0  ext4_split_extent.isra.0+0x18f/0x500  ext4_split_convert_extents+0x275/0x750  ext4_ext_handle_unwritten_extents+0x73e/0x1580  ext4_ext_map_blocks+0xe20/0x2dc0  ext4_map_blocks+0x724/0x1700  ext4_do_writepages+0x12d6/0x2a70 [...] ==================================================================  The flow of issue triggering is as follows:  ext4_split_extent_at   path = *ppath   ext4_ext_insert_extent(ppath)     ext4_ext_create_new_leaf(ppath)       ext4_find_extent(orig_path)         path = *orig_path         read_extent_tree_block           // return -ENOMEM or -EIO         ext4_free_ext_path(path)           kfree(path)         *orig_path = NULL   a. If err is -ENOMEM:   ext4_ext_dirty(path + path-\u0026gt;p_depth)   // path use-after-free !!!   b. If err is -EIO and we have EXT_DEBUG defined:   ext4_ext_show_leaf(path)     eh = path[depth].p_hdr     // path also use-after-free !!!  So when trying to zeroout or fix the extent length, call ext4_find_extent() to update the path.  In addition we use *ppath directly as an ext4_ext_show_leaf() input to avoid possible use-after-free when EXT_DEBUG is defined, and to avoid unnecessary path updates.(CVE-2024-49884)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  platform/x86: ISST: Fix the KASAN report slab-out-of-bounds bug  Attaching SST PCI device to VM causes \u0026quot;BUG: KASAN: slab-out-of-bounds\u0026quot;. kasan report: [   19.411889] ================================================================== [   19.413702] BUG: KASAN: slab-out-of-bounds in _isst_if_get_pci_dev+0x3d5/0x400 [isst_if_common] [   19.415634] Read of size 8 at addr ffff888829e65200 by task cpuhp/16/113 [   19.417368] [   19.418627] CPU: 16 PID: 113 Comm: cpuhp/16 Tainted: G            E      6.9.0 #10 [   19.420435] Hardware name: VMware, Inc. VMware20,1/440BX Desktop Reference Platform, BIOS VMW201.00V.20192059.B64.2207280713 07/28/2022 [   19.422687] Call Trace: [   19.424091]  \u0026lt;TASK\u0026gt; [   19.425448]  dump_stack_lvl+0x5d/0x80 [   19.426963]  ? _isst_if_get_pci_dev+0x3d5/0x400 [isst_if_common] [   19.428694]  print_report+0x19d/0x52e [   19.430206]  ? __pfx__raw_spin_lock_irqsave+0x10/0x10 [   19.431837]  ? _isst_if_get_pci_dev+0x3d5/0x400 [isst_if_common] [   19.433539]  kasan_report+0xf0/0x170 [   19.435019]  ? _isst_if_get_pci_dev+0x3d5/0x400 [isst_if_common] [   19.436709]  _isst_if_get_pci_dev+0x3d5/0x400 [isst_if_common] [   19.438379]  ? __pfx_sched_clock_cpu+0x10/0x10 [   19.439910]  isst_if_cpu_online+0x406/0x58f [isst_if_common] [   19.441573]  ? __pfx_isst_if_cpu_online+0x10/0x10 [isst_if_common] [   19.443263]  ? ttwu_queue_wakelist+0x2c1/0x360 [   19.444797]  cpuhp_invoke_callback+0x221/0xec0 [   19.446337]  cpuhp_thread_fun+0x21b/0x610 [   19.447814]  ? __pfx_cpuhp_thread_fun+0x10/0x10 [   19.449354]  smpboot_thread_fn+0x2e7/0x6e0 [   19.450859]  ? __pfx_smpboot_thread_fn+0x10/0x10 [   19.452405]  kthread+0x29c/0x350 [   19.453817]  ? __pfx_kthread+0x10/0x10 [   19.455253]  ret_from_fork+0x31/0x70 [   19.456685]  ? __pfx_kthread+0x10/0x10 [   19.458114]  ret_from_fork_asm+0x1a/0x30 [   19.459573]  \u0026lt;/TASK\u0026gt; [   19.460853] [   19.462055] Allocated by task 1198: [   19.463410]  kasan_save_stack+0x30/0x50 [   19.464788]  kasan_save_track+0x14/0x30 [   19.466139]  __kasan_kmalloc+0xaa/0xb0 [   19.467465]  __kmalloc+0x1cd/0x470 [   19.468748]  isst_if_cdev_register+0x1da/0x350 [isst_if_common] [   19.470233]  isst_if_mbox_init+0x108/0xff0 [isst_if_mbox_msr] [   19.471670]  do_one_initcall+0xa4/0x380 [   19.472903]  do_init_module+0x238/0x760 [   19.474105]  load_module+0x5239/0x6f00 [   19.475285]  init_module_from_file+0xd1/0x130 [   19.476506]  idempotent_init_module+0x23b/0x650 [   19.477725]  __x64_sys_finit_module+0xbe/0x130 [   19.476506]  idempotent_init_module+0x23b/0x650 [   19.477725]  __x64_sys_finit_module+0xbe/0x130 [   19.478920]  do_syscall_64+0x82/0x160 [   19.480036]  entry_SYSCALL_64_after_hwframe+0x76/0x7e [   19.481292] [   19.482205] The buggy address belongs to the object at ffff888829e65000  which belongs to the cache kmalloc-512 of size 512 [   19.484818] The buggy address is located 0 bytes to the right of  allocated 512-byte region [ffff888829e65000, ffff888829e65200) [   19.487447] [   19.488328] The buggy address belongs to the physical page: [   19.489569] page: refcount:1 mapcount:0 mapping:0000000000000000 index:0xffff888829e60c00 pfn:0x829e60 [   19.491140] head: order:3 entire_mapcount:0 nr_pages_mapped:0 pincount:0 [   19.492466] anon flags: 0x57ffffc0000840(slab|head|node=1|zone=2|lastcpupid=0x1fffff) [   19.493914] page_type: 0xffffffff() [   19.494988] raw: 0057ffffc0000840 ffff88810004cc80 0000000000000000 0000000000000001 [   19.496451] raw: ffff888829e60c00 0000000080200018 00000001ffffffff 0000000000000000 [   19.497906] head: 0057ffffc0000840 ffff88810004cc80 0000000000000000 0000000000000001 [   19.499379] head: ffff888829e60c00 0000000080200018 00000001ffffffff 0000000000000000 [   19.500844] head: 0057ffffc0000003 ffffea0020a79801 ffffea0020a79848 00000000ffffffff [   19.502316] head: 0000000800000000 0000000000000000 00000000ffffffff 0000000000000000 [   19.503784] page dumped because: k ---truncated---(CVE-2024-49886)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  ext4: avoid use-after-free in ext4_ext_show_leaf()  In ext4_find_extent(), path may be freed by error or be reallocated, so using a previously saved *ppath may have been freed and thus may trigger use-after-free, as follows:  ext4_split_extent   path = *ppath;   ext4_split_extent_at(ppath)   path = ext4_find_extent(ppath)   ext4_split_extent_at(ppath)     // ext4_find_extent fails to free path     // but zeroout succeeds   ext4_ext_show_leaf(inode, path)     eh = path[depth].p_hdr     // path use-after-free !!!  Similar to ext4_split_extent_at(), we use *ppath directly as an input to ext4_ext_show_leaf(). Fix a spelling error by the way.  Same problem in ext4_ext_handle_unwritten_extents(). Since \u0026apos;path\u0026apos; is only used in ext4_ext_show_leaf(), remove \u0026apos;path\u0026apos; and use *ppath directly.  This issue is triggered only when EXT_DEBUG is defined and therefore does not affect functionality.(CVE-2024-49889)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  drm/amd/display: Add null check for top_pipe_to_program in commit_planes_for_stream  This commit addresses a null pointer dereference issue in the `commit_planes_for_stream` function at line 4140. The issue could occur when `top_pipe_to_program` is null.  The fix adds a check to ensure `top_pipe_to_program` is not null before accessing its stream_res. This prevents a null pointer dereference.  Reported by smatch: drivers/gpu/drm/amd/amdgpu/../display/dc/core/dc.c:4140 commit_planes_for_stream() error: we previously assumed \u0026apos;top_pipe_to_program\u0026apos; could be null (see line 3906)(CVE-2024-49913)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  drm/amd/display: Add NULL check for clk_mgr and clk_mgr-\u0026gt;funcs in dcn30_init_hw  This commit addresses a potential null pointer dereference issue in the `dcn30_init_hw` function. The issue could occur when `dc-\u0026gt;clk_mgr` or `dc-\u0026gt;clk_mgr-\u0026gt;funcs` is null.  The fix adds a check to ensure `dc-\u0026gt;clk_mgr` and `dc-\u0026gt;clk_mgr-\u0026gt;funcs` is not null before accessing its functions. This prevents a potential null pointer dereference.  Reported by smatch: drivers/gpu/drm/amd/amdgpu/../display/dc/hwss/dcn30/dcn30_hwseq.c:789 dcn30_init_hw() error: we previously assumed \u0026apos;dc-\u0026gt;clk_mgr\u0026apos; could be null (see line 628)(CVE-2024-49917)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  drm/amd/display: Check null pointers before using them  [WHAT \u0026amp; HOW] These pointers are null checked previously in the same function, indicating they might be null as reported by Coverity. As a result, they need to be checked when used again.  This fixes 3 FORWARD_NULL issue reported by Coverity.(CVE-2024-49922)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  fbdev: pxafb: Fix possible use after free in pxafb_task()  In the pxafb_probe function, it calls the pxafb_init_fbinfo function, after which \u0026amp;fbi-\u0026gt;task is associated with pxafb_task. Moreover, within this pxafb_init_fbinfo function, the pxafb_blank function within the \u0026amp;pxafb_ops struct is capable of scheduling work.  If we remove the module which will call pxafb_remove to make cleanup, it will call unregister_framebuffer function which can call do_unregister_framebuffer to free fbi-\u0026gt;fb through put_fb_info(fb_info), while the work mentioned above will be used. The sequence of operations that may lead to a UAF bug is as follows:  CPU0                                                CPU1                                     | pxafb_task pxafb_remove                       | unregister_framebuffer(info)       | do_unregister_framebuffer(fb_info) | put_fb_info(fb_info)               | // free fbi-\u0026gt;fb                    | set_ctrlr_state(fbi, state)                                    | __pxafb_lcd_power(fbi, 0)                                    | fbi-\u0026gt;lcd_power(on, \u0026amp;fbi-\u0026gt;fb.var)                                    | //use fbi-\u0026gt;fb  Fix it by ensuring that the work is canceled before proceeding with the cleanup in pxafb_remove.  Note that only root user can remove the driver at runtime.(CVE-2024-49924)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  blk_iocost: fix more out of bound shifts  Recently running UBSAN caught few out of bound shifts in the ioc_forgive_debts() function:  UBSAN: shift-out-of-bounds in block/blk-iocost.c:2142:38 shift exponent 80 is too large for 64-bit type \u0026apos;u64\u0026apos; (aka \u0026apos;unsigned long long\u0026apos;) ... UBSAN: shift-out-of-bounds in block/blk-iocost.c:2144:30 shift exponent 80 is too large for 64-bit type \u0026apos;u64\u0026apos; (aka \u0026apos;unsigned long long\u0026apos;) ... Call Trace: \u0026lt;IRQ\u0026gt; dump_stack_lvl+0xca/0x130 __ubsan_handle_shift_out_of_bounds+0x22c/0x280 ? __lock_acquire+0x6441/0x7c10 ioc_timer_fn+0x6cec/0x7750 ? blk_iocost_init+0x720/0x720 ? call_timer_fn+0x5d/0x470 call_timer_fn+0xfa/0x470 ? blk_iocost_init+0x720/0x720 __run_timer_base+0x519/0x700 ...  Actual impact of this issue was not identified but I propose to fix the undefined behaviour. The proposed fix to prevent those out of bound shifts consist of precalculating exponent before using it the shift operations by taking min value from the actual exponent and maximum possible number of bits.(CVE-2024-49933)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  fs/inode: Prevent dump_mapping() accessing invalid dentry.d_name.name  It\u0026apos;s observed that a crash occurs during hot-remove a memory device, in which user is accessing the hugetlb. See calltrace as following:  ------------[ cut here ]------------ WARNING: CPU: 1 PID: 14045 at arch/x86/mm/fault.c:1278 do_user_addr_fault+0x2a0/0x790 Modules linked in: kmem device_dax cxl_mem cxl_pmem cxl_port cxl_pci dax_hmem dax_pmem nd_pmem cxl_acpi nd_btt cxl_core crc32c_intel nvme virtiofs fuse nvme_core nfit libnvdimm dm_multipath scsi_dh_rdac scsi_dh_emc s mirror dm_region_hash dm_log dm_mod CPU: 1 PID: 14045 Comm: daxctl Not tainted 6.10.0-rc2-lizhijian+ #492 Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS rel-1.16.3-0-ga6ed6b701f0a-prebuilt.qemu.org 04/01/2014 RIP: 0010:do_user_addr_fault+0x2a0/0x790 Code: 48 8b 00 a8 04 0f 84 b5 fe ff ff e9 1c ff ff ff 4c 89 e9 4c 89 e2 be 01 00 00 00 bf 02 00 00 00 e8 b5 ef 24 00 e9 42 fe ff ff \u0026lt;0f\u0026gt; 0b 48 83 c4 08 4c 89 ea 48 89 ee 4c 89 e7 5b 5d 41 5c 41 5d 41 RSP: 0000:ffffc90000a575f0 EFLAGS: 00010046 RAX: ffff88800c303600 RBX: 0000000000000000 RCX: 0000000000000000 RDX: 0000000000001000 RSI: ffffffff82504162 RDI: ffffffff824b2c36 RBP: 0000000000000000 R08: 0000000000000000 R09: 0000000000000000 R10: 0000000000000000 R11: 0000000000000000 R12: ffffc90000a57658 R13: 0000000000001000 R14: ffff88800bc2e040 R15: 0000000000000000 FS:  00007f51cb57d880(0000) GS:ffff88807fd00000(0000) knlGS:0000000000000000 CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 0000000000001000 CR3: 00000000072e2004 CR4: 00000000001706f0 DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400 Call Trace:  \u0026lt;TASK\u0026gt;  ? __warn+0x8d/0x190  ? do_user_addr_fault+0x2a0/0x790  ? report_bug+0x1c3/0x1d0  ? handle_bug+0x3c/0x70  ? exc_invalid_op+0x14/0x70  ? asm_exc_invalid_op+0x16/0x20  ? do_user_addr_fault+0x2a0/0x790  ? exc_page_fault+0x31/0x200  exc_page_fault+0x68/0x200 \u0026lt;...snip...\u0026gt; BUG: unable to handle page fault for address: 0000000000001000  #PF: supervisor read access in kernel mode  #PF: error_code(0x0000) - not-present page  PGD 800000000ad92067 P4D 800000000ad92067 PUD 7677067 PMD 0  Oops: Oops: 0000 [#1] PREEMPT SMP PTI  ---[ end trace 0000000000000000 ]---  BUG: unable to handle page fault for address: 0000000000001000  #PF: supervisor read access in kernel mode  #PF: error_code(0x0000) - not-present page  PGD 800000000ad92067 P4D 800000000ad92067 PUD 7677067 PMD 0  Oops: Oops: 0000 [#1] PREEMPT SMP PTI  CPU: 1 PID: 14045 Comm: daxctl Kdump: loaded Tainted: G        W          6.10.0-rc2-lizhijian+ #492  Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS rel-1.16.3-0-ga6ed6b701f0a-prebuilt.qemu.org 04/01/2014  RIP: 0010:dentry_name+0x1f4/0x440 \u0026lt;...snip...\u0026gt; ? dentry_name+0x2fa/0x440 vsnprintf+0x1f3/0x4f0 vprintk_store+0x23a/0x540 vprintk_emit+0x6d/0x330 _printk+0x58/0x80 dump_mapping+0x10b/0x1a0 ? __pfx_free_object_rcu+0x10/0x10 __dump_page+0x26b/0x3e0 ? vprintk_emit+0xe0/0x330 ? _printk+0x58/0x80 ? dump_page+0x17/0x50 dump_page+0x17/0x50 do_migrate_range+0x2f7/0x7f0 ? do_migrate_range+0x42/0x7f0 ? offline_pages+0x2f4/0x8c0 offline_pages+0x60a/0x8c0 memory_subsys_offline+0x9f/0x1c0 ? lockdep_hardirqs_on+0x77/0x100 ? _raw_spin_unlock_irqrestore+0x38/0x60 device_offline+0xe3/0x110 state_store+0x6e/0xc0 kernfs_fop_write_iter+0x143/0x200 vfs_write+0x39f/0x560 ksys_write+0x65/0xf0 do_syscall_64+0x62/0x130  Previously, some sanity check have been done in dump_mapping() before the print facility parsing \u0026apos;%pd\u0026apos; though, it\u0026apos;s still possible to run into an invalid dentry.d_name.name.  Since dump_mapping() only needs to dump the filename only, retrieve it by itself in a safer way to prevent an unnecessary crash.  Note that either retrieving the filename with \u0026apos;%pd\u0026apos; or strncpy_from_kernel_nofault(), the filename could be unreliable.(CVE-2024-49934)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  net/xen-netback: prevent UAF in xenvif_flush_hash()  During the list_for_each_entry_rcu iteration call of xenvif_flush_hash, kfree_rcu does not exist inside the rcu read critical section, so if kfree_rcu is called when the rcu grace period ends during the iteration, UAF occurs when accessing head-\u0026gt;next after the entry becomes free.  Therefore, to solve this, you need to change it to list_for_each_entry_safe.(CVE-2024-49936)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  l2tp: prevent possible tunnel refcount underflow  When a session is created, it sets a backpointer to its tunnel. When the session refcount drops to 0, l2tp_session_free drops the tunnel refcount if session-\u0026gt;tunnel is non-NULL. However, session-\u0026gt;tunnel is set in l2tp_session_create, before the tunnel refcount is incremented by l2tp_session_register, which leaves a small window where session-\u0026gt;tunnel is non-NULL when the tunnel refcount hasn\u0026apos;t been bumped.  Moving the assignment to l2tp_session_register is trivial but l2tp_session_create calls l2tp_session_set_header_len which uses session-\u0026gt;tunnel to get the tunnel\u0026apos;s encap. Add an encap arg to l2tp_session_set_header_len to avoid using session-\u0026gt;tunnel.  If l2tpv3 sessions have colliding IDs, it is possible for l2tp_v3_session_get to race with l2tp_session_register and fetch a session which doesn\u0026apos;t yet have session-\u0026gt;tunnel set. Add a check for this case.(CVE-2024-49940)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  Bluetooth: L2CAP: Fix uaf in l2cap_connect  [Syzbot reported] BUG: KASAN: slab-use-after-free in l2cap_connect.constprop.0+0x10d8/0x1270 net/bluetooth/l2cap_core.c:3949 Read of size 8 at addr ffff8880241e9800 by task kworker/u9:0/54  CPU: 0 UID: 0 PID: 54 Comm: kworker/u9:0 Not tainted 6.11.0-rc6-syzkaller-00268-g788220eee30d #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 08/06/2024 Workqueue: hci2 hci_rx_work Call Trace:  \u0026lt;TASK\u0026gt;  __dump_stack lib/dump_stack.c:93 [inline]  dump_stack_lvl+0x116/0x1f0 lib/dump_stack.c:119  print_address_description mm/kasan/report.c:377 [inline]  print_report+0xc3/0x620 mm/kasan/report.c:488  kasan_report+0xd9/0x110 mm/kasan/report.c:601  l2cap_connect.constprop.0+0x10d8/0x1270 net/bluetooth/l2cap_core.c:3949  l2cap_connect_req net/bluetooth/l2cap_core.c:4080 [inline]  l2cap_bredr_sig_cmd net/bluetooth/l2cap_core.c:4772 [inline]  l2cap_sig_channel net/bluetooth/l2cap_core.c:5543 [inline]  l2cap_recv_frame+0xf0b/0x8eb0 net/bluetooth/l2cap_core.c:6825  l2cap_recv_acldata+0x9b4/0xb70 net/bluetooth/l2cap_core.c:7514  hci_acldata_packet net/bluetooth/hci_core.c:3791 [inline]  hci_rx_work+0xaab/0x1610 net/bluetooth/hci_core.c:4028  process_one_work+0x9c5/0x1b40 kernel/workqueue.c:3231  process_scheduled_works kernel/workqueue.c:3312 [inline]  worker_thread+0x6c8/0xed0 kernel/workqueue.c:3389  kthread+0x2c1/0x3a0 kernel/kthread.c:389  ret_from_fork+0x45/0x80 arch/x86/kernel/process.c:147  ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:244 ...  Freed by task 5245:  kasan_save_stack+0x33/0x60 mm/kasan/common.c:47  kasan_save_track+0x14/0x30 mm/kasan/common.c:68  kasan_save_free_info+0x3b/0x60 mm/kasan/generic.c:579  poison_slab_object+0xf7/0x160 mm/kasan/common.c:240  __kasan_slab_free+0x32/0x50 mm/kasan/common.c:256  kasan_slab_free include/linux/kasan.h:184 [inline]  slab_free_hook mm/slub.c:2256 [inline]  slab_free mm/slub.c:4477 [inline]  kfree+0x12a/0x3b0 mm/slub.c:4598  l2cap_conn_free net/bluetooth/l2cap_core.c:1810 [inline]  kref_put include/linux/kref.h:65 [inline]  l2cap_conn_put net/bluetooth/l2cap_core.c:1822 [inline]  l2cap_conn_del+0x59d/0x730 net/bluetooth/l2cap_core.c:1802  l2cap_connect_cfm+0x9e6/0xf80 net/bluetooth/l2cap_core.c:7241  hci_connect_cfm include/net/bluetooth/hci_core.h:1960 [inline]  hci_conn_failed+0x1c3/0x370 net/bluetooth/hci_conn.c:1265  hci_abort_conn_sync+0x75a/0xb50 net/bluetooth/hci_sync.c:5583  abort_conn_sync+0x197/0x360 net/bluetooth/hci_conn.c:2917  hci_cmd_sync_work+0x1a4/0x410 net/bluetooth/hci_sync.c:328  process_one_work+0x9c5/0x1b40 kernel/workqueue.c:3231  process_scheduled_works kernel/workqueue.c:3312 [inline]  worker_thread+0x6c8/0xed0 kernel/workqueue.c:3389  kthread+0x2c1/0x3a0 kernel/kthread.c:389  ret_from_fork+0x45/0x80 arch/x86/kernel/process.c:147  ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:244(CVE-2024-49950)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  static_call: Replace pointless WARN_ON() in static_call_module_notify()  static_call_module_notify() triggers a WARN_ON(), when memory allocation fails in __static_call_add_module().  That\u0026apos;s not really justified, because the failure case must be correctly handled by the well known call chain and the error code is passed through to the initiating userspace application.  A memory allocation fail is not a fatal problem, but the WARN_ON() takes the machine out when panic_on_warn is set.  Replace it with a pr_warn().(CVE-2024-49954)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  ACPI: battery: Fix possible crash when unregistering a battery hook  When a battery hook returns an error when adding a new battery, then the battery hook is automatically unregistered. However the battery hook provider cannot know that, so it will later call battery_hook_unregister() on the already unregistered battery hook, resulting in a crash.  Fix this by using the list head to mark already unregistered battery hooks as already being unregistered so that they can be ignored by battery_hook_unregister().(CVE-2024-49955)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  ocfs2: reserve space for inline xattr before attaching reflink tree  One of our customers reported a crash and a corrupted ocfs2 filesystem.  The crash was due to the detection of corruption.  Upon troubleshooting, the fsck -fn output showed the below corruption  [EXTENT_LIST_FREE] Extent list in owner 33080590 claims 230 as the next free chain record, but fsck believes the largest valid value is 227.  Clamp the next record value? n  The stat output from the debugfs.ocfs2 showed the following corruption where the \u0026quot;Next Free Rec:\u0026quot; had overshot the \u0026quot;Count:\u0026quot; in the root metadata block.          Inode: 33080590   Mode: 0640   Generation: 2619713622 (0x9c25a856)         FS Generation: 904309833 (0x35e6ac49)         CRC32: 00000000   ECC: 0000         Type: Regular   Attr: 0x0   Flags: Valid         Dynamic Features: (0x16) HasXattr InlineXattr Refcounted         Extended Attributes Block: 0  Extended Attributes Inline Size: 256         User: 0 (root)   Group: 0 (root)   Size: 281320357888         Links: 1   Clusters: 141738         ctime: 0x66911b56 0x316edcb8 -- Fri Jul 12 06:02:30.829349048 2024         atime: 0x66911d6b 0x7f7a28d -- Fri Jul 12 06:11:23.133669517 2024         mtime: 0x66911b56 0x12ed75d7 -- Fri Jul 12 06:02:30.317552087 2024         dtime: 0x0 -- Wed Dec 31 17:00:00 1969         Refcount Block: 2777346         Last Extblk: 2886943   Orphan Slot: 0         Sub Alloc Slot: 0   Sub Alloc Bit: 14         Tree Depth: 1   Count: 227   Next Free Rec: 230         ## Offset        Clusters       Block#         0  0             2310           2776351         1  2310          2139           2777375         2  4449          1221           2778399         3  5670          731            2779423         4  6401          566            2780447         .......          ....           .......         .......          ....           .......  The issue was in the reflink workfow while reserving space for inline xattr.  The problematic function is ocfs2_reflink_xattr_inline().  By the time this function is called the reflink tree is already recreated at the destination inode from the source inode.  At this point, this function reserves space for inline xattrs at the destination inode without even checking if there is space at the root metadata block.  It simply reduces the l_count from 243 to 227 thereby making space of 256 bytes for inline xattr whereas the inode already has extents beyond this index (in this case up to 230), thereby causing corruption.  The fix for this is to reserve space for inline metadata at the destination inode before the reflink tree gets recreated. The customer has verified the fix.(CVE-2024-49958)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  ocfs2: remove unreasonable unlock in ocfs2_read_blocks  Patch series \u0026quot;Misc fixes for ocfs2_read_blocks\u0026quot;, v5.  This series contains 2 fixes for ocfs2_read_blocks().  The first patch fix the issue reported by syzbot, which detects bad unlock balance in ocfs2_read_blocks().  The second patch fixes an issue reported by Heming Zhao when reviewing above fix.   This patch (of 2):  There was a lock release before exiting, so remove the unreasonable unlock.(CVE-2024-49965)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  r8169: add tally counter fields added with RTL8125  RTL8125 added fields to the tally counter, what may result in the chip dma\u0026apos;ing these new fields to unallocated memory. Therefore make sure that the allocated memory area is big enough to hold all of the tally counter values, even if we use only parts of it.(CVE-2024-49973)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  uprobes: fix kernel info leak via \u0026quot;[uprobes]\u0026quot; vma  xol_add_vma() maps the uninitialized page allocated by __create_xol_area() into userspace. On some architectures (x86) this memory is readable even without VM_READ, VM_EXEC results in the same pgprot_t as VM_EXEC|VM_READ, although this doesn\u0026apos;t really matter, debugger can read this memory anyway.(CVE-2024-49975)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  gso: fix udp gso fraglist segmentation after pull from frag_list  Detect gso fraglist skbs with corrupted geometry (see below) and pass these to skb_segment instead of skb_segment_list, as the first can segment them correctly.  Valid SKB_GSO_FRAGLIST skbs - consist of two or more segments - the head_skb holds the protocol headers plus first gso_size - one or more frag_list skbs hold exactly one segment - all but the last must be gso_size  Optional datapath hooks such as NAT and BPF (bpf_skb_pull_data) can modify these skbs, breaking these invariants.  In extreme cases they pull all data into skb linear. For UDP, this causes a NULL ptr deref in __udpv4_gso_segment_list_csum at udp_hdr(seg-\u0026gt;next)-\u0026gt;dest.  Detect invalid geometry due to pull, by checking head_skb size. Don\u0026apos;t just drop, as this may blackhole a destination. Convert to be able to pass to regular skb_segment.(CVE-2024-49978)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  media: venus: fix use after free bug in venus_remove due to race condition  in venus_probe, core-\u0026gt;work is bound with venus_sys_error_handler, which is used to handle error. The code use core-\u0026gt;sys_err_done to make sync work. The core-\u0026gt;work is started in venus_event_notify.  If we call venus_remove, there might be an unfished work. The possible sequence is as follows:  CPU0                  CPU1                       |venus_sys_error_handler venus_remove         | hfi_destroy     | venus_hfi_destroy  | kfree(hdev);      |                      |hfi_reinit       |venus_hfi_queues_reinit                      |//use hdev  Fix it by canceling the work in venus_remove.(CVE-2024-49981)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  drm/stm: Avoid use-after-free issues with crtc and plane  ltdc_load() calls functions drm_crtc_init_with_planes(), drm_universal_plane_init() and drm_encoder_init(). These functions should not be called with parameters allocated with devm_kzalloc() to avoid use-after-free issues [1].  Use allocations managed by the DRM framework.  Found by Linux Verification Center (linuxtesting.org).  [1] https://lore.kernel.org/lkml/u366i76e3qhh3ra5oxrtngjtm2u5lterkekcz6y2jkndhuxzli@diujon4h7qwb/(CVE-2024-49992)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  tipc: guard against string buffer overrun  Smatch reports that copying media_name and if_name to name_parts may overwrite the destination.   .../bearer.c:166 bearer_name_validate() error: strcpy() \u0026apos;media_name\u0026apos; too large for \u0026apos;name_parts-\u0026gt;media_name\u0026apos; (32 vs 16)  .../bearer.c:167 bearer_name_validate() error: strcpy() \u0026apos;if_name\u0026apos; too large for \u0026apos;name_parts-\u0026gt;if_name\u0026apos; (1010102 vs 16)  This does seem to be the case so guard against this possibility by using strscpy() and failing if truncation occurs.  Introduced by commit b97bf3fd8f6a (\u0026quot;[TIPC] Initial merge\u0026quot;)  Compile tested only.(CVE-2024-49995)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  cifs: Fix buffer overflow when parsing NFS reparse points  ReparseDataLength is sum of the InodeType size and DataBuffer size. So to get DataBuffer size it is needed to subtract InodeType\u0026apos;s size from ReparseDataLength.  Function cifs_strndup_from_utf16() is currentlly accessing buf-\u0026gt;DataBuffer at position after the end of the buffer because it does not subtract InodeType size from the length. Fix this problem and correctly subtract variable len.  Member InodeType is present only when reparse buffer is large enough. Check for ReparseDataLength before accessing InodeType to prevent another invalid memory access.  Major and minor rdev values are present also only when reparse buffer is large enough. Check for reparse buffer size before calling reparse_mkdev().(CVE-2024-49996)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  wifi: mwifiex: Fix memcpy() field-spanning write warning in mwifiex_cmd_802_11_scan_ext()  Replace one-element array with a flexible-array member in `struct host_cmd_ds_802_11_scan_ext`.  With this, fix the following warning:  elo 16 17:51:58 surfacebook kernel: ------------[ cut here ]------------ elo 16 17:51:58 surfacebook kernel: memcpy: detected field-spanning write (size 243) of single field \u0026quot;ext_scan-\u0026gt;tlv_buffer\u0026quot; at drivers/net/wireless/marvell/mwifiex/scan.c:2239 (size 1) elo 16 17:51:58 surfacebook kernel: WARNING: CPU: 0 PID: 498 at drivers/net/wireless/marvell/mwifiex/scan.c:2239 mwifiex_cmd_802_11_scan_ext+0x83/0x90 [mwifiex](CVE-2024-50008)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  ext4: dax: fix overflowing extents beyond inode size when partially writing  The dax_iomap_rw() does two things in each iteration: map written blocks and copy user data to blocks. If the process is killed by user(See signal handling in dax_iomap_iter()), the copied data will be returned and added on inode size, which means that the length of written extents may exceed the inode size, then fsck will fail. An example is given as:  dd if=/dev/urandom of=file bs=4M count=1  dax_iomap_rw   iomap_iter // round 1    ext4_iomap_begin     ext4_iomap_alloc // allocate 0~2M extents(written flag)   dax_iomap_iter // copy 2M data   iomap_iter // round 2    iomap_iter_advance     iter-\u0026gt;pos += iter-\u0026gt;processed // iter-\u0026gt;pos = 2M    ext4_iomap_begin     ext4_iomap_alloc // allocate 2~4M extents(written flag)   dax_iomap_iter    fatal_signal_pending   done = iter-\u0026gt;pos - iocb-\u0026gt;ki_pos // done = 2M  ext4_handle_inode_extension   ext4_update_inode_size // inode size = 2M  fsck reports: Inode 13, i_size is 2097152, should be 4194304.  Fix?  Fix the problem by truncating extents if the written length is smaller than expected.(CVE-2024-50015)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  drm/amd/display: Avoid overflow assignment in link_dp_cts  sampling_rate is an uint8_t but is assigned an unsigned int, and thus it can overflow. As a result, sampling_rate is changed to uint32_t.  Similarly, LINK_QUAL_PATTERN_SET has a size of 2 bits, and it should only be assigned to a value less or equal than 4.  This fixes 2 INTEGER_OVERFLOW issues reported by Coverity.(CVE-2024-50016)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  thermal: core: Reference count the zone in thermal_zone_get_by_id()  There are places in the thermal netlink code where nothing prevents the thermal zone object from going away while being accessed after it has been returned by thermal_zone_get_by_id().  To address this, make thermal_zone_get_by_id() get a reference on the thermal zone device object to be returned with the help of get_device(), under thermal_list_lock, and adjust all of its callers to this change with the help of the cleanup.h infrastructure.(CVE-2024-50028)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  slip: make slhc_remember() more robust against malicious packets  syzbot found that slhc_remember() was missing checks against malicious packets [1].  slhc_remember() only checked the size of the packet was at least 20, which is not good enough.  We need to make sure the packet includes the IPv4 and TCP header that are supposed to be carried.  Add iph and th pointers to make the code more readable.  [1]  BUG: KMSAN: uninit-value in slhc_remember+0x2e8/0x7b0 drivers/net/slip/slhc.c:666   slhc_remember+0x2e8/0x7b0 drivers/net/slip/slhc.c:666   ppp_receive_nonmp_frame+0xe45/0x35e0 drivers/net/ppp/ppp_generic.c:2455   ppp_receive_frame drivers/net/ppp/ppp_generic.c:2372 [inline]   ppp_do_recv+0x65f/0x40d0 drivers/net/ppp/ppp_generic.c:2212   ppp_input+0x7dc/0xe60 drivers/net/ppp/ppp_generic.c:2327   pppoe_rcv_core+0x1d3/0x720 drivers/net/ppp/pppoe.c:379   sk_backlog_rcv+0x13b/0x420 include/net/sock.h:1113   __release_sock+0x1da/0x330 net/core/sock.c:3072   release_sock+0x6b/0x250 net/core/sock.c:3626   pppoe_sendmsg+0x2b8/0xb90 drivers/net/ppp/pppoe.c:903   sock_sendmsg_nosec net/socket.c:729 [inline]   __sock_sendmsg+0x30f/0x380 net/socket.c:744   ____sys_sendmsg+0x903/0xb60 net/socket.c:2602   ___sys_sendmsg+0x28d/0x3c0 net/socket.c:2656   __sys_sendmmsg+0x3c1/0x960 net/socket.c:2742   __do_sys_sendmmsg net/socket.c:2771 [inline]   __se_sys_sendmmsg net/socket.c:2768 [inline]   __x64_sys_sendmmsg+0xbc/0x120 net/socket.c:2768   x64_sys_call+0xb6e/0x3ba0 arch/x86/include/generated/asm/syscalls_64.h:308   do_syscall_x64 arch/x86/entry/common.c:52 [inline]   do_syscall_64+0xcd/0x1e0 arch/x86/entry/common.c:83  entry_SYSCALL_64_after_hwframe+0x77/0x7f  Uninit was created at:   slab_post_alloc_hook mm/slub.c:4091 [inline]   slab_alloc_node mm/slub.c:4134 [inline]   kmem_cache_alloc_node_noprof+0x6bf/0xb80 mm/slub.c:4186   kmalloc_reserve+0x13d/0x4a0 net/core/skbuff.c:587   __alloc_skb+0x363/0x7b0 net/core/skbuff.c:678   alloc_skb include/linux/skbuff.h:1322 [inline]   sock_wmalloc+0xfe/0x1a0 net/core/sock.c:2732   pppoe_sendmsg+0x3a7/0xb90 drivers/net/ppp/pppoe.c:867   sock_sendmsg_nosec net/socket.c:729 [inline]   __sock_sendmsg+0x30f/0x380 net/socket.c:744   ____sys_sendmsg+0x903/0xb60 net/socket.c:2602   ___sys_sendmsg+0x28d/0x3c0 net/socket.c:2656   __sys_sendmmsg+0x3c1/0x960 net/socket.c:2742   __do_sys_sendmmsg net/socket.c:2771 [inline]   __se_sys_sendmmsg net/socket.c:2768 [inline]   __x64_sys_sendmmsg+0xbc/0x120 net/socket.c:2768   x64_sys_call+0xb6e/0x3ba0 arch/x86/include/generated/asm/syscalls_64.h:308   do_syscall_x64 arch/x86/entry/common.c:52 [inline]   do_syscall_64+0xcd/0x1e0 arch/x86/entry/common.c:83  entry_SYSCALL_64_after_hwframe+0x77/0x7f  CPU: 0 UID: 0 PID: 5460 Comm: syz.2.33 Not tainted 6.12.0-rc2-syzkaller-00006-g87d6aab2389e #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 09/13/2024(CVE-2024-50033)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  ppp: fix ppp_async_encode() illegal access  syzbot reported an issue in ppp_async_encode() [1]  In this case, pppoe_sendmsg() is called with a zero size. Then ppp_async_encode() is called with an empty skb.  BUG: KMSAN: uninit-value in ppp_async_encode drivers/net/ppp/ppp_async.c:545 [inline]  BUG: KMSAN: uninit-value in ppp_async_push+0xb4f/0x2660 drivers/net/ppp/ppp_async.c:675   ppp_async_encode drivers/net/ppp/ppp_async.c:545 [inline]   ppp_async_push+0xb4f/0x2660 drivers/net/ppp/ppp_async.c:675   ppp_async_send+0x130/0x1b0 drivers/net/ppp/ppp_async.c:634   ppp_channel_bridge_input drivers/net/ppp/ppp_generic.c:2280 [inline]   ppp_input+0x1f1/0xe60 drivers/net/ppp/ppp_generic.c:2304   pppoe_rcv_core+0x1d3/0x720 drivers/net/ppp/pppoe.c:379   sk_backlog_rcv+0x13b/0x420 include/net/sock.h:1113   __release_sock+0x1da/0x330 net/core/sock.c:3072   release_sock+0x6b/0x250 net/core/sock.c:3626   pppoe_sendmsg+0x2b8/0xb90 drivers/net/ppp/pppoe.c:903   sock_sendmsg_nosec net/socket.c:729 [inline]   __sock_sendmsg+0x30f/0x380 net/socket.c:744   ____sys_sendmsg+0x903/0xb60 net/socket.c:2602   ___sys_sendmsg+0x28d/0x3c0 net/socket.c:2656   __sys_sendmmsg+0x3c1/0x960 net/socket.c:2742   __do_sys_sendmmsg net/socket.c:2771 [inline]   __se_sys_sendmmsg net/socket.c:2768 [inline]   __x64_sys_sendmmsg+0xbc/0x120 net/socket.c:2768   x64_sys_call+0xb6e/0x3ba0 arch/x86/include/generated/asm/syscalls_64.h:308   do_syscall_x64 arch/x86/entry/common.c:52 [inline]   do_syscall_64+0xcd/0x1e0 arch/x86/entry/common.c:83  entry_SYSCALL_64_after_hwframe+0x77/0x7f  Uninit was created at:   slab_post_alloc_hook mm/slub.c:4092 [inline]   slab_alloc_node mm/slub.c:4135 [inline]   kmem_cache_alloc_node_noprof+0x6bf/0xb80 mm/slub.c:4187   kmalloc_reserve+0x13d/0x4a0 net/core/skbuff.c:587   __alloc_skb+0x363/0x7b0 net/core/skbuff.c:678   alloc_skb include/linux/skbuff.h:1322 [inline]   sock_wmalloc+0xfe/0x1a0 net/core/sock.c:2732   pppoe_sendmsg+0x3a7/0xb90 drivers/net/ppp/pppoe.c:867   sock_sendmsg_nosec net/socket.c:729 [inline]   __sock_sendmsg+0x30f/0x380 net/socket.c:744   ____sys_sendmsg+0x903/0xb60 net/socket.c:2602   ___sys_sendmsg+0x28d/0x3c0 net/socket.c:2656   __sys_sendmmsg+0x3c1/0x960 net/socket.c:2742   __do_sys_sendmmsg net/socket.c:2771 [inline]   __se_sys_sendmmsg net/socket.c:2768 [inline]   __x64_sys_sendmmsg+0xbc/0x120 net/socket.c:2768   x64_sys_call+0xb6e/0x3ba0 arch/x86/include/generated/asm/syscalls_64.h:308   do_syscall_x64 arch/x86/entry/common.c:52 [inline]   do_syscall_64+0xcd/0x1e0 arch/x86/entry/common.c:83  entry_SYSCALL_64_after_hwframe+0x77/0x7f  CPU: 1 UID: 0 PID: 5411 Comm: syz.1.14 Not tainted 6.12.0-rc1-syzkaller-00165-g360c1f1f24c6 #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 09/13/2024(CVE-2024-50035)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  NFSv4: Prevent NULL-pointer dereference in nfs42_complete_copies()  On the node of an NFS client, some files saved in the mountpoint of the NFS server were copied to another location of the same NFS server. Accidentally, the nfs42_complete_copies() got a NULL-pointer dereference crash with the following syslog:  [232064.838881] NFSv4: state recovery failed for open file nfs/pvc-12b5200d-cd0f-46a3-b9f0-af8f4fe0ef64.qcow2, error = -116 [232064.839360] NFSv4: state recovery failed for open file nfs/pvc-12b5200d-cd0f-46a3-b9f0-af8f4fe0ef64.qcow2, error = -116 [232066.588183] Unable to handle kernel NULL pointer dereference at virtual address 0000000000000058 [232066.588586] Mem abort info: [232066.588701]   ESR = 0x0000000096000007 [232066.588862]   EC = 0x25: DABT (current EL), IL = 32 bits [232066.589084]   SET = 0, FnV = 0 [232066.589216]   EA = 0, S1PTW = 0 [232066.589340]   FSC = 0x07: level 3 translation fault [232066.589559] Data abort info: [232066.589683]   ISV = 0, ISS = 0x00000007 [232066.589842]   CM = 0, WnR = 0 [232066.589967] user pgtable: 64k pages, 48-bit VAs, pgdp=00002000956ff400 [232066.590231] [0000000000000058] pgd=08001100ae100003, p4d=08001100ae100003, pud=08001100ae100003, pmd=08001100b3c00003, pte=0000000000000000 [232066.590757] Internal error: Oops: 96000007 [#1] SMP [232066.590958] Modules linked in: rpcsec_gss_krb5 auth_rpcgss nfsv4 dns_resolver nfs lockd grace fscache netfs ocfs2_dlmfs ocfs2_stack_o2cb ocfs2_dlm vhost_net vhost vhost_iotlb tap tun ipt_rpfilter xt_multiport ip_set_hash_ip ip_set_hash_net xfrm_interface xfrm6_tunnel tunnel4 tunnel6 esp4 ah4 wireguard libcurve25519_generic veth xt_addrtype xt_set nf_conntrack_netlink ip_set_hash_ipportnet ip_set_hash_ipportip ip_set_bitmap_port ip_set_hash_ipport dummy ip_set ip_vs_sh ip_vs_wrr ip_vs_rr ip_vs iptable_filter sch_ingress nfnetlink_cttimeout vport_gre ip_gre ip_tunnel gre vport_geneve geneve vport_vxlan vxlan ip6_udp_tunnel udp_tunnel openvswitch nf_conncount dm_round_robin dm_service_time dm_multipath xt_nat xt_MASQUERADE nft_chain_nat nf_nat xt_mark xt_conntrack xt_comment nft_compat nft_counter nf_tables nfnetlink ocfs2 ocfs2_nodemanager ocfs2_stackglue iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi ipmi_ssif nbd overlay 8021q garp mrp bonding tls rfkill sunrpc ext4 mbcache jbd2 [232066.591052]  vfat fat cas_cache cas_disk ses enclosure scsi_transport_sas sg acpi_ipmi ipmi_si ipmi_devintf ipmi_msghandler ip_tables vfio_pci vfio_pci_core vfio_virqfd vfio_iommu_type1 vfio dm_mirror dm_region_hash dm_log dm_mod nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 br_netfilter bridge stp llc fuse xfs libcrc32c ast drm_vram_helper qla2xxx drm_kms_helper syscopyarea crct10dif_ce sysfillrect ghash_ce sysimgblt sha2_ce fb_sys_fops cec sha256_arm64 sha1_ce drm_ttm_helper ttm nvme_fc igb sbsa_gwdt nvme_fabrics drm nvme_core i2c_algo_bit i40e scsi_transport_fc megaraid_sas aes_neon_bs [232066.596953] CPU: 6 PID: 4124696 Comm: 10.253.166.125- Kdump: loaded Not tainted 5.15.131-9.cl9_ocfs2.aarch64 #1 [232066.597356] Hardware name: Great Wall .\\x93\\x8e...RF6260 V5/GWMSSE2GL1T, BIOS T656FBE_V3.0.18 2024-01-06 [232066.597721] pstate: 20400009 (nzCv daif +PAN -UAO -TCO -DIT -SSBS BTYPE=--) [232066.598034] pc : nfs4_reclaim_open_state+0x220/0x800 [nfsv4] [232066.598327] lr : nfs4_reclaim_open_state+0x12c/0x800 [nfsv4] [232066.598595] sp : ffff8000f568fc70 [232066.598731] x29: ffff8000f568fc70 x28: 0000000000001000 x27: ffff21003db33000 [232066.599030] x26: ffff800005521ae0 x25: ffff0100f98fa3f0 x24: 0000000000000001 [232066.599319] x23: ffff800009920008 x22: ffff21003db33040 x21: ffff21003db33050 [232066.599628] x20: ffff410172fe9e40 x19: ffff410172fe9e00 x18: 0000000000000000 [232066.599914] x17: 0000000000000000 x16: 0000000000000004 x15: 0000000000000000 [232066.600195] x14: 0000000000000000 x13: ffff800008e685a8 x12: 00000000eac0c6e6 [232066.600498] x11: 00000000000000 ---truncated---(CVE-2024-50046)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  smb: client: fix UAF in async decryption  Doing an async decryption (large read) crashes with a slab-use-after-free way down in the crypto API.  Reproducer:     # mount.cifs -o ...,seal,esize=1 //srv/share /mnt     # dd if=/mnt/largefile of=/dev/null     ...     [  194.196391] ==================================================================     [  194.196844] BUG: KASAN: slab-use-after-free in gf128mul_4k_lle+0xc1/0x110     [  194.197269] Read of size 8 at addr ffff888112bd0448 by task kworker/u77:2/899     [  194.197707]     [  194.197818] CPU: 12 UID: 0 PID: 899 Comm: kworker/u77:2 Not tainted 6.11.0-lku-00028-gfca3ca14a17a-dirty #43     [  194.198400] Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS rel-1.16.2-3-gd478f380-prebuilt.qemu.org 04/01/2014     [  194.199046] Workqueue: smb3decryptd smb2_decrypt_offload [cifs]     [  194.200032] Call Trace:     [  194.200191]  \u0026lt;TASK\u0026gt;     [  194.200327]  dump_stack_lvl+0x4e/0x70     [  194.200558]  ? gf128mul_4k_lle+0xc1/0x110     [  194.200809]  print_report+0x174/0x505     [  194.201040]  ? __pfx__raw_spin_lock_irqsave+0x10/0x10     [  194.201352]  ? srso_return_thunk+0x5/0x5f     [  194.201604]  ? __virt_addr_valid+0xdf/0x1c0     [  194.201868]  ? gf128mul_4k_lle+0xc1/0x110     [  194.202128]  kasan_report+0xc8/0x150     [  194.202361]  ? gf128mul_4k_lle+0xc1/0x110     [  194.202616]  gf128mul_4k_lle+0xc1/0x110     [  194.202863]  ghash_update+0x184/0x210     [  194.203103]  shash_ahash_update+0x184/0x2a0     [  194.203377]  ? __pfx_shash_ahash_update+0x10/0x10     [  194.203651]  ? srso_return_thunk+0x5/0x5f     [  194.203877]  ? crypto_gcm_init_common+0x1ba/0x340     [  194.204142]  gcm_hash_assoc_remain_continue+0x10a/0x140     [  194.204434]  crypt_message+0xec1/0x10a0 [cifs]     [  194.206489]  ? __pfx_crypt_message+0x10/0x10 [cifs]     [  194.208507]  ? srso_return_thunk+0x5/0x5f     [  194.209205]  ? srso_return_thunk+0x5/0x5f     [  194.209925]  ? srso_return_thunk+0x5/0x5f     [  194.210443]  ? srso_return_thunk+0x5/0x5f     [  194.211037]  decrypt_raw_data+0x15f/0x250 [cifs]     [  194.212906]  ? __pfx_decrypt_raw_data+0x10/0x10 [cifs]     [  194.214670]  ? srso_return_thunk+0x5/0x5f     [  194.215193]  smb2_decrypt_offload+0x12a/0x6c0 [cifs]  This is because TFM is being used in parallel.  Fix this by allocating a new AEAD TFM for async decryption, but keep the existing one for synchronous READ cases (similar to what is done in smb3_calc_signature()).  Also remove the calls to aead_request_set_callback() and crypto_wait_req() since it\u0026apos;s always going to be a synchronous operation.(CVE-2024-50047)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  serial: protect uart_port_dtr_rts() in uart_shutdown() too  Commit af224ca2df29 (serial: core: Prevent unsafe uart port access, part 3) added few uport == NULL checks. It added one to uart_shutdown(), so the commit assumes, uport can be NULL in there. But right after that protection, there is an unprotected \u0026quot;uart_port_dtr_rts(uport, false);\u0026quot; call. That is invoked only if HUPCL is set, so I assume that is the reason why we do not see lots of these reports.  Or it cannot be NULL at this point at all for some reason :P.  Until the above is investigated, stay on the safe side and move this dereference to the if too.  I got this inconsistency from Coverity under CID 1585130. Thanks.(CVE-2024-50058)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  ntb: ntb_hw_switchtec: Fix use after free vulnerability in switchtec_ntb_remove due to race condition  In the switchtec_ntb_add function, it can call switchtec_ntb_init_sndev function, then \u0026amp;sndev-\u0026gt;check_link_status_work is bound with check_link_status_work. switchtec_ntb_link_notification may be called to start the work.  If we remove the module which will call switchtec_ntb_remove to make cleanup, it will free sndev through kfree(sndev), while the work mentioned above will be used. The sequence of operations that may lead to a UAF bug is as follows:  CPU0                                 CPU1                          | check_link_status_work switchtec_ntb_remove    | kfree(sndev);           |                         | if (sndev-\u0026gt;link_force_down)                         | // use sndev  Fix it by ensuring that the work is canceled before proceeding with the cleanup in switchtec_ntb_remove.(CVE-2024-50059)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  io_uring: check if we need to reschedule during overflow flush  In terms of normal application usage, this list will always be empty. And if an application does overflow a bit, it\u0026apos;ll have a few entries. However, nothing obviously prevents syzbot from running a test case that generates a ton of overflow entries, and then flushing them can take quite a while.  Check for needing to reschedule while flushing, and drop our locks and do so if necessary. There\u0026apos;s no state to maintain here as overflows always prune from head-of-list, hence it\u0026apos;s fine to drop and reacquire the locks at the end of the loop.(CVE-2024-50060)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  bpf: Prevent tail call between progs attached to different hooks  bpf progs can be attached to kernel functions, and the attached functions can take different parameters or return different return values. If prog attached to one kernel function tail calls prog attached to another kernel function, the ctx access or return value verification could be bypassed.  For example, if prog1 is attached to func1 which takes only 1 parameter and prog2 is attached to func2 which takes two parameters. Since verifier assumes the bpf ctx passed to prog2 is constructed based on func2\u0026apos;s prototype, verifier allows prog2 to access the second parameter from the bpf ctx passed to it. The problem is that verifier does not prevent prog1 from passing its bpf ctx to prog2 via tail call. In this case, the bpf ctx passed to prog2 is constructed from func1 instead of func2, that is, the assumption for ctx access verification is bypassed.  Another example, if BPF LSM prog1 is attached to hook file_alloc_security, and BPF LSM prog2 is attached to hook bpf_lsm_audit_rule_known. Verifier knows the return value rules for these two hooks, e.g. it is legal for bpf_lsm_audit_rule_known to return positive number 1, and it is illegal for file_alloc_security to return positive number. So verifier allows prog2 to return positive number 1, but does not allow prog1 to return positive number. The problem is that verifier does not prevent prog1 from calling prog2 via tail call. In this case, prog2\u0026apos;s return value 1 will be used as the return value for prog1\u0026apos;s hook file_alloc_security. That is, the return value rule is bypassed.  This patch adds restriction for tail call to prevent such bypasses.(CVE-2024-50063)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  uprobe: avoid out-of-bounds memory access of fetching args  Uprobe needs to fetch args into a percpu buffer, and then copy to ring buffer to avoid non-atomic context problem.  Sometimes user-space strings, arrays can be very large, but the size of percpu buffer is only page size. And store_trace_args() won\u0026apos;t check whether these data exceeds a single page or not, caused out-of-bounds memory access.  It could be reproduced by following steps: 1. build kernel with CONFIG_KASAN enabled 2. save follow program as test.c  ``` \\#include \u0026lt;stdio.h\u0026gt; \\#include \u0026lt;stdlib.h\u0026gt; \\#include \u0026lt;string.h\u0026gt;  // If string length large than MAX_STRING_SIZE, the fetch_store_strlen() // will return 0, cause __get_data_size() return shorter size, and // store_trace_args() will not trigger out-of-bounds access. // So make string length less than 4096. \\#define STRLEN 4093  void generate_string(char *str, int n) {     int i;     for (i = 0; i \u0026lt; n; ++i)     {         char c = i % 26 + \u0026apos;a\u0026apos;;         str[i] = c;     }     str[n-1] = \u0026apos;\\0\u0026apos;; }  void print_string(char *str) {     printf(\u0026quot;%s\\n\u0026quot;, str); }  int main() {     char tmp[STRLEN];      generate_string(tmp, STRLEN);     print_string(tmp);      return 0; } ``` 3. compile program `gcc -o test test.c`  4. get the offset of `print_string()` ``` objdump -t test | grep -w print_string 0000000000401199 g     F .text  000000000000001b              print_string ```  5. configure uprobe with offset 0x1199 ``` off=0x1199  cd /sys/kernel/debug/tracing/ echo \u0026quot;p /root/test:${off} arg1=+0(%di):ustring arg2=\\$comm arg3=+0(%di):ustring\u0026quot;  \u0026gt; uprobe_events echo 1 \u0026gt; events/uprobes/enable echo 1 \u0026gt; tracing_on ```  6. run `test`, and kasan will report error. ================================================================== BUG: KASAN: use-after-free in strncpy_from_user+0x1d6/0x1f0 Write of size 8 at addr ffff88812311c004 by task test/499CPU: 0 UID: 0 PID: 499 Comm: test Not tainted 6.12.0-rc3+ #18 Hardware name: Red Hat KVM, BIOS 1.16.0-4.al8 04/01/2014 Call Trace:  \u0026lt;TASK\u0026gt;  dump_stack_lvl+0x55/0x70  print_address_description.constprop.0+0x27/0x310  kasan_report+0x10f/0x120  ? strncpy_from_user+0x1d6/0x1f0  strncpy_from_user+0x1d6/0x1f0  ? rmqueue.constprop.0+0x70d/0x2ad0  process_fetch_insn+0xb26/0x1470  ? __pfx_process_fetch_insn+0x10/0x10  ? _raw_spin_lock+0x85/0xe0  ? __pfx__raw_spin_lock+0x10/0x10  ? __pte_offset_map+0x1f/0x2d0  ? unwind_next_frame+0xc5f/0x1f80  ? arch_stack_walk+0x68/0xf0  ? is_bpf_text_address+0x23/0x30  ? kernel_text_address.part.0+0xbb/0xd0  ? __kernel_text_address+0x66/0xb0  ? unwind_get_return_address+0x5e/0xa0  ? __pfx_stack_trace_consume_entry+0x10/0x10  ? arch_stack_walk+0xa2/0xf0  ? _raw_spin_lock_irqsave+0x8b/0xf0  ? __pfx__raw_spin_lock_irqsave+0x10/0x10  ? depot_alloc_stack+0x4c/0x1f0  ? _raw_spin_unlock_irqrestore+0xe/0x30  ? stack_depot_save_flags+0x35d/0x4f0  ? kasan_save_stack+0x34/0x50  ? kasan_save_stack+0x24/0x50  ? mutex_lock+0x91/0xe0  ? __pfx_mutex_lock+0x10/0x10  prepare_uprobe_buffer.part.0+0x2cd/0x500  uprobe_dispatcher+0x2c3/0x6a0  ? __pfx_uprobe_dispatcher+0x10/0x10  ? __kasan_slab_alloc+0x4d/0x90  handler_chain+0xdd/0x3e0  handle_swbp+0x26e/0x3d0  ? __pfx_handle_swbp+0x10/0x10  ? uprobe_pre_sstep_notifier+0x151/0x1b0  irqentry_exit_to_user_mode+0xe2/0x1b0  asm_exc_int3+0x39/0x40 RIP: 0033:0x401199 Code: 01 c2 0f b6 45 fb 88 02 83 45 fc 01 8b 45 fc 3b 45 e4 7c b7 8b 45 e4 48 98 48 8d 50 ff 48 8b 45 e8 48 01 d0 ce RSP: 002b:00007ffdf00576a8 EFLAGS: 00000206 RAX: 00007ffdf00576b0 RBX: 0000000000000000 RCX: 0000000000000ff2 RDX: 0000000000000ffc RSI: 0000000000000ffd RDI: 00007ffdf00576b0 RBP: 00007ffdf00586b0 R08: 00007feb2f9c0d20 R09: 00007feb2f9c0d20 R10: 0000000000000001 R11: 0000000000000202 R12: 0000000000401040 R13: 00007ffdf0058780 R14: 0000000000000000 R15: 0000000000000000  \u0026lt;/TASK\u0026gt;  This commit enforces the buffer\u0026apos;s maxlen less than a page-size to avoid store_trace_args() out-of-memory access.(CVE-2024-50067)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  parport: Proper fix for array out-of-bounds access  The recent fix for array out-of-bounds accesses replaced sprintf() calls blindly with snprintf().  However, since snprintf() returns the would-be-printed size, not the actually output size, the length calculation can still go over the given limit.  Use scnprintf() instead of snprintf(), which returns the actually output letters, for addressing the potential out-of-bounds access properly.(CVE-2024-50074)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  tcp: fix mptcp DSS corruption due to large pmtu xmit  Syzkaller was able to trigger a DSS corruption:    TCP: request_sock_subflow_v4: Possible SYN flooding on port [::]:20002. Sending cookies.   ------------[ cut here ]------------   WARNING: CPU: 0 PID: 5227 at net/mptcp/protocol.c:695 __mptcp_move_skbs_from_subflow+0x20a9/0x21f0 net/mptcp/protocol.c:695   Modules linked in:   CPU: 0 UID: 0 PID: 5227 Comm: syz-executor350 Not tainted 6.11.0-syzkaller-08829-gaf9c191ac2a0 #0   Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 08/06/2024   RIP: 0010:__mptcp_move_skbs_from_subflow+0x20a9/0x21f0 net/mptcp/protocol.c:695   Code: 0f b6 dc 31 ff 89 de e8 b5 dd ea f5 89 d8 48 81 c4 50 01 00 00 5b 41 5c 41 5d 41 5e 41 5f 5d c3 cc cc cc cc e8 98 da ea f5 90 \u0026lt;0f\u0026gt; 0b 90 e9 47 ff ff ff e8 8a da ea f5 90 0f 0b 90 e9 99 e0 ff ff   RSP: 0018:ffffc90000006db8 EFLAGS: 00010246   RAX: ffffffff8ba9df18 RBX: 00000000000055f0 RCX: ffff888030023c00   RDX: 0000000000000100 RSI: 00000000000081e5 RDI: 00000000000055f0   RBP: 1ffff110062bf1ae R08: ffffffff8ba9cf12 R09: 1ffff110062bf1b8   R10: dffffc0000000000 R11: ffffed10062bf1b9 R12: 0000000000000000   R13: dffffc0000000000 R14: 00000000700cec61 R15: 00000000000081e5   FS:  000055556679c380(0000) GS:ffff8880b8600000(0000) knlGS:0000000000000000   CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033   CR2: 0000000020287000 CR3: 0000000077892000 CR4: 00000000003506f0   DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000   DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400   Call Trace:    \u0026lt;IRQ\u0026gt;    move_skbs_to_msk net/mptcp/protocol.c:811 [inline]    mptcp_data_ready+0x29c/0xa90 net/mptcp/protocol.c:854    subflow_data_ready+0x34a/0x920 net/mptcp/subflow.c:1490    tcp_data_queue+0x20fd/0x76c0 net/ipv4/tcp_input.c:5283    tcp_rcv_established+0xfba/0x2020 net/ipv4/tcp_input.c:6237    tcp_v4_do_rcv+0x96d/0xc70 net/ipv4/tcp_ipv4.c:1915    tcp_v4_rcv+0x2dc0/0x37f0 net/ipv4/tcp_ipv4.c:2350    ip_protocol_deliver_rcu+0x22e/0x440 net/ipv4/ip_input.c:205    ip_local_deliver_finish+0x341/0x5f0 net/ipv4/ip_input.c:233    NF_HOOK+0x3a4/0x450 include/linux/netfilter.h:314    NF_HOOK+0x3a4/0x450 include/linux/netfilter.h:314    __netif_receive_skb_one_core net/core/dev.c:5662 [inline]    __netif_receive_skb+0x2bf/0x650 net/core/dev.c:5775    process_backlog+0x662/0x15b0 net/core/dev.c:6107    __napi_poll+0xcb/0x490 net/core/dev.c:6771    napi_poll net/core/dev.c:6840 [inline]    net_rx_action+0x89b/0x1240 net/core/dev.c:6962    handle_softirqs+0x2c5/0x980 kernel/softirq.c:554    do_softirq+0x11b/0x1e0 kernel/softirq.c:455    \u0026lt;/IRQ\u0026gt;    \u0026lt;TASK\u0026gt;    __local_bh_enable_ip+0x1bb/0x200 kernel/softirq.c:382    local_bh_enable include/linux/bottom_half.h:33 [inline]    rcu_read_unlock_bh include/linux/rcupdate.h:919 [inline]    __dev_queue_xmit+0x1764/0x3e80 net/core/dev.c:4451    dev_queue_xmit include/linux/netdevice.h:3094 [inline]    neigh_hh_output include/net/neighbour.h:526 [inline]    neigh_output include/net/neighbour.h:540 [inline]    ip_finish_output2+0xd41/0x1390 net/ipv4/ip_output.c:236    ip_local_out net/ipv4/ip_output.c:130 [inline]    __ip_queue_xmit+0x118c/0x1b80 net/ipv4/ip_output.c:536    __tcp_transmit_skb+0x2544/0x3b30 net/ipv4/tcp_output.c:1466    tcp_transmit_skb net/ipv4/tcp_output.c:1484 [inline]    tcp_mtu_probe net/ipv4/tcp_output.c:2547 [inline]    tcp_write_xmit+0x641d/0x6bf0 net/ipv4/tcp_output.c:2752    __tcp_push_pending_frames+0x9b/0x360 net/ipv4/tcp_output.c:3015    tcp_push_pending_frames include/net/tcp.h:2107 [inline]    tcp_data_snd_check net/ipv4/tcp_input.c:5714 [inline]    tcp_rcv_established+0x1026/0x2020 net/ipv4/tcp_input.c:6239    tcp_v4_do_rcv+0x96d/0xc70 net/ipv4/tcp_ipv4.c:1915    sk_backlog_rcv include/net/sock.h:1113 [inline]    __release_sock+0x214/0x350 net/core/sock.c:3072    release_sock+0x61/0x1f0 net/core/sock.c:3626    mptcp_push_ ---truncated---(CVE-2024-50083)","status":"published","published":"2024-11-08T11:07:51Z","modified":"2026-08-18T01:18:40.386686868Z","cvss":[{"version":"3.1","score":8.8,"vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H","level":"high"}],"updated_at":"2026-11-02T15:52:42.253598Z"},{"id":"ROOT-OS-DEBIAN-11-CVE-2024-49978","title":"CVE-2024-49978 in linux - Patched by Root","description":"Root has patched CVE-2024-49978 in the linux package for Root:Debian:11. Multiple fixed versions available.","status":"published","published":"2026-08-23T09:13:41Z","modified":"2026-08-23T10:17:46.708522633Z","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:53:29.077857Z"},{"id":"ROOT-OS-UBUNTU-2204-CVE-2024-49978","title":"CVE-2024-49978 in linux - Patched by Root","description":"Root has patched CVE-2024-49978 in the linux package for Root:Ubuntu:22.04. Multiple fixed versions available.","status":"published","published":"2026-11-06T13:52:25Z","modified":"2026-11-06T14:16:42.846887241Z","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-06T14:57:21.022388Z"},{"id":"UBUNTU-CVE-2024-49978","description":"In the Linux kernel, the following vulnerability has been resolved: gso: fix udp gso fraglist segmentation after pull from frag_list Detect gso fraglist skbs with corrupted geometry (see below) and pass these to skb_segment instead of skb_segment_list, as the first can segment them correctly. Valid SKB_GSO_FRAGLIST skbs - consist of two or more segments - the head_skb holds the protocol headers plus first gso_size - one or more frag_list skbs hold exactly one segment - all but the last must be gso_size Optional datapath hooks such as NAT and BPF (bpf_skb_pull_data) can modify these skbs, breaking these invariants. In extreme cases they pull all data into skb linear. For UDP, this causes a NULL ptr deref in __udpv4_gso_segment_list_csum at udp_hdr(seg-\u003enext)-\u003edest. Detect invalid geometry due to pull, by checking head_skb size. Don't just drop, as this may blackhole a destination. Convert to be able to pass to regular skb_segment.","status":"published","published":"2024-10-21T18:15:00Z","modified":"2026-11-11T09:38:34.982751862Z","cvss":[{"version":"4.0","score":6.8,"vector":"CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N","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"},{"version":"3.1","score":7.5,"vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H","level":"high"}],"updated_at":"2026-11-11T10:00:16.555633Z"},{"id":"DLA-4008-1","title":"linux-6.1 - security update","status":"published","published":"2025-01-02T00:00:00Z","modified":"2026-03-09T02:11:41.013831Z","updated_at":"2026-11-02T15:46:12.203458Z"},{"id":"MGASA-2024-0344","title":"Updated kernel-linus packages fix security vulnerabilities","description":"Vanilla upstream kernel version 6.6.58 fixes bugs and vulnerabilities.\nFor information about the vulnerabilities see the links.\n","status":"published","published":"2024-11-02T16:56:24Z","modified":"2026-04-16T04:43:08.190830944Z","updated_at":"2026-11-02T15:49:42.684501Z"},{"id":"MGASA-2024-0345","title":"Updated kernel, kmod-xtables-addons. kmod-virtualbox, kernel-firmware \u0026 kernel-firmware-nonfree radeon-firmware packages fix security vulnerabilities","description":"Upstream kernel version 6.6.58 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":"2024-11-02T16:56:24Z","modified":"2026-04-16T04:40:54.434421703Z","updated_at":"2026-11-02T15:49:42.684501Z"},{"id":"openSUSE-SU-2024:14500-1","title":"kernel-devel-6.11.8-1.1 on GA media","description":"These are all security issues fixed in the kernel-devel-6.11.8-1.1 package on the GA media of openSUSE Tumbleweed.","status":"published","published":"2024-11-15T00:00:00Z","modified":"2026-02-04T03:05:15.769912Z","updated_at":"2026-11-02T16:58:36.976155Z"},{"id":"openSUSE-SU-2025:14705-1","title":"kernel-devel-longterm-6.12.11-1.1 on GA media","description":"These are all security issues fixed in the kernel-devel-longterm-6.12.11-1.1 package on the GA media of openSUSE Tumbleweed.","status":"published","published":"2025-01-28T00:00:00Z","modified":"2026-02-04T03:17:00.28177Z","updated_at":"2026-11-02T16:58:36.976155Z"},{"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:0564-1","title":"Security update for the Linux Kernel","description":"\n\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-2024-40980: drop_monitor: replace spin_lock by raw_spin_lock (bsc#1227937).\n- CVE-2024-46858: mptcp: pm: Fix uaf in __timer_delete_sync (bsc#1231088).\n- CVE-2024-49948: net: add more sanity checks to qdisc_pkt_len_init() (bsc#1232161).\n- CVE-2024-49978: gso: fix udp gso fraglist segmentation after pull from frag_list (bsc#1232101).\n- CVE-2024-50142: xfrm: validate new SA's prefixlen using SA family when sel.family is unset (bsc#1233028).\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-50304: ipv4: ip_tunnel: Fix suspicious RCU usage warning in ip_tunnel_find() (bsc#1233522).\n- CVE-2024-53123: mptcp: error out earlier on disconnect (bsc#1234070).\n- CVE-2024-53187: io_uring: check for overflows in io_pin_pages (bsc#1234947).\n- CVE-2024-53203: usb: typec: fix potential array underflow in ucsi_ccg_sync_control() (bsc#1235001).\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-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-56633: tcp_bpf: Fix the sk_mem_uncharge logic in tcp_bpf_sendmsg (bsc#1235485).\n- CVE-2024-56650: netfilter: x_tables: fix LED ID check in led_tg_check() (bsc#1235430).\n- CVE-2024-56658: net: defer final 'struct net' free in netns dismantle (bsc#1235441).\n- CVE-2024-56665: bpf,perf: Fix invalid prog_array access in perf_event_detach_bpf_prog (bsc#1235489).\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-56707: octeontx2-pf: handle otx2_mbox_get_rsp errors in otx2_dmac_flt.c (bsc#1235545).\n- CVE-2024-56715: ionic: Fix netdev notifier unregister on failure (bsc#1235612).\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-56763: tracing: Prevent bad count for tracing_cpumask_write (bsc#1235638).\n- CVE-2024-57802: netrom: check buffer length before accessing it (bsc#1235941).\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-57917: topology: Keep the cpumask unchanged when printing cpumap (bsc#1236127).\n- CVE-2024-57931: selinux: ignore unknown extended permissions (bsc#1236192).\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-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-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-21665: filemap: avoid truncating 64-bit offset to 32 bits (bsc#1236684).\n- CVE-2025-21666: vsock: prevent null-ptr-deref in vsock_*[has_data|has_space] (bsc#1236680).\n- CVE-2025-21667: iomap: avoid avoid truncating 64-bit offset to 32 bits (bsc#1236681).\n- CVE-2025-21668: pmdomain: imx8mp-blk-ctrl: add missing loop break condition (bsc#1236682).\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-21673: smb: client: fix double free of TCP_Server_Info::hostname (bsc#1236689).\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-21681: openvswitch: fix lockup on tx to unregistering netdev with carrier (bsc#1236702).\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: PRM: Remove unnecessary strict handler address checks (git-fixes).\n- ACPI: fan: cleanup resources in the error path of .probe() (git-fixes).\n- ACPI: property: Fix return value for nval == 0 in acpi_data_prop_read() (git-fixes).\n- ACPI: resource: acpi_dev_irq_override(): Check DMI match last (stable-fixes).\n- ALSA: hda/realtek - Fixed headphone distorted sound on Acer Aspire A115-31 laptop (git-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: seq: Make dependency on UMP clearer (git-fixes).\n- ALSA: seq: remove redundant 'tristate' for SND_SEQ_UMP_CLIENT (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: Abstract IPC handling (stable-fixes).\n- ASoC: Intel: avs: Do not readq() u32 registers (git-fixes).\n- ASoC: Intel: avs: Fix theoretical infinite loop (git-fixes).\n- ASoC: Intel: avs: Prefix SKL/APL-specific members (stable-fixes).\n- ASoC: acp: Support microphone from Lenovo Go S (stable-fixes).\n- ASoC: rockchip: i2s_tdm: Re-add the set_sysclk callback (git-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: 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: btnxpuart: Fix glitches seen in dual A2DP streaming (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: 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: Allow page-sized MMU caches to be initialized with custom 64-bit values (jsc#PED-6143).\n- KVM: x86/mmu: Add Suppress VE bit to EPT shadow_mmio_mask/shadow_present_mask (jsc#PED-6143).\n- KVM: x86/mmu: Allow non-zero value for non-present SPTE and removed SPTE (jsc#PED-6143).\n- KVM: x86/mmu: Replace hardcoded value 0 for the initial value for SPTE (jsc#PED-6143).\n- KVM: x86/mmu: Track shadow MMIO value on a per-VM basis (jsc#PED-6143).\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: 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- Remove 'iommu/arm-smmu: Defer probe of clients after smmu device bound', reverted by upstream.\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 'usb: gadget: u_serial: Disable ep before setting port to null to fix the crash caused by port being null' (stable-fixes).\n- Revert 'Disable ceph'.\n- USB: serial: quatech2: fix null-ptr-deref in qt2_process_read_urb() (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- 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) Update arm64 default configuration file\n- arm64: dts: rockchip: Add sdmmc/sdio/emmc reset controls for RK3328 (git-fixes)\n- arm64: dts: rockchip: increase gmac rx_delay on rk3399-puma (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- bus: mhi: host: Free mhi_buf vector inside mhi_alloc_bhie_table() (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: imx6q: Do not disable 792 Mhz OPP unnecessarily (git-fixes).\n- cpufreq: imx6q: do not warn for disabling a non-existing frequency (git-fixes).\n- cpufreq: intel_pstate: Make hwp_notify_lock a raw spinlock (git-fixes).\n- cpufreq: intel_pstate: Use HWP to initialize ITMT if CPPC is missing (git-fixes).\n- cpufreq: intel_pstate: fix pstate limits enforcement for adjust_perf call back (git-fixes).\n- cpufreq: mediatek-hw: Do not error out if supply is not found (git-fixes).\n- cpufreq: mediatek-hw: Wait for CPU supplies before probing (git-fixes).\n- cpufreq: qcom-nvmem: Enable virtual power domain devices (git-fixes).\n- cpufreq: qcom-nvmem: Simplify driver data allocation (stable-fixes).\n- cpufreq: qcom-nvmem: add support for IPQ8064 (git-fixes).\n- cpufreq: qcom-nvmem: drop pvs_ver for format a fuses (git-fixes).\n- cpufreq: qcom-nvmem: fix memory leaks in probe error paths (git-fixes).\n- cpufreq: qcom-nvmem: use SoC ID-s from bindings (git-fixes).\n- cpufreq: qcom-nvmem: use helper to get SMEM SoC ID (git-fixes).\n- cpufreq: qcom: Fix qcom_cpufreq_hw_recalc_rate() to query LUT if LMh IRQ is not available (git-fixes).\n- cpufreq: qcom: Implement clk_ops::determine_rate() for qcom_cpufreq* clocks (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: hisilicon/sec2 - fix for aead icv error (git-fixes).\n- crypto: hisilicon/sec2 - fix for aead invalid authsize (git-fixes).\n- crypto: hisilicon/sec2 - optimize the error return process (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- dmaengine: ti: edma: fix OF node reference leaks in edma_driver (git-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: Use HW lock mgr for PSR1 (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: fix UVD contiguous CS mapping problem (bsc#1236759).\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/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/dp: Iterate DSC BPP from high to low on all platforms (git-fixes).\n- drm/i915/fb: Relax clear color alignment to 64 bytes (stable-fixes).\n- drm/i915/guc: Debug print LRC state entries only if the context is pinned (git-fixes).\n- drm/i915/pmu: Fix zero delta busyness issue (git-fixes).\n- drm/komeda: Add check for komeda_get_layer_fourcc_list() (git-fixes).\n- drm/mgag200: Added support for the new device G200eH5 (jsc#PED-12094)\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: move output interface related definition to rockchip_drm_drv.h (stable-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/rockchip: vop2: Fix the windows switch between different layers (git-fixes).\n- drm/rockchip: vop2: Set YUV/RGB overlay mode (stable-fixes).\n- drm/rockchip: vop2: include rockchip_drm_drv.h (git-fixes).\n- drm/rockchip: vop2: set bg dly and prescan dly at vop2_post_config (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: Stop active perfmon if it is being destroyed (git-fixes).\n- fbdev: omapfb: Fix an OF node leak in dss_of_port_get_parent_device() (git-fixes).\n- firmware: iscsi_ibft: fix ISCSI_IBFT Kconfig entry (git-fixes).\n- futex: Do not include process MM in futex key on no-MMU (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: pca953x: Improve interrupt support (git-fixes).\n- gpu: drm_dp_cec: fix broken CEC adapter properties check (git-fixes).\n- gtp: Use for_each_netdev_rcu() in gtp_genl_dump_pdp() (git-fixes).\n- hwmon: (drivetemp) Set scsi command timeout to 10s (stable-fixes).\n- hyperv: Do not overlap the hvcall IO areas in get_vtl() (git-fixes).\n- ibmvnic: Free any outstanding tx skbs during scrq reset (bsc#1226980).\n- iio: adc: ad_sigma_delta: Handle CS assertion as intended in ad_sd_read_reg_raw() (git-fixes).\n- iio: iio-mux: kzalloc instead of devm_kzalloc to ensure page alignment (git-fixes).\n- iio: light: as73211: fix channel handling in only-color triggered buffer (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- 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- lockdep: fix deadlock issue between lockdep and rcu (git-fixes).\n- locking/lockdep: Avoid creating new name string literals in lockdep_set_subclass() (git-fixes).\n- locking/rwsem: Add __always_inline annotation to __down_write_common() and inlined callers (git-fixes).\n- mac802154: check local interfaces before deleting sdata list (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: 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: 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: misc_minor_alloc to use ida for all dynamic/misc dynamic minors (git-fixes).\n- mm/compaction: fix UBSAN shift-out-of-bounds warning (git fixes (mm/compaction)).\n- mm/rodata_test: use READ_ONCE() to read const variable (git-fixes).\n- mptcp: fix recvbuffer adjust on sleeping rcvmsg (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: rtl8150: enable basic endpoint checking (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- 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/pseries/eeh: Fix get PE state translation (bsc#1215199).\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- 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/futex: pass _GNU_SOURCE without a value to the compiler (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: 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: sc16is7xx: use device_property APIs when configuring irda mode (stable-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: introduce qcom_smem_get_soc_id() (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: move SMEM item struct and defines to a header (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- 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- tools: Sync if_xdp.h uapi tooling header (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: chipidea: ci_hdrc_imx: decrement device's refcount in .remove() and in the error path of .probe() (git-fixes).\n- usb: dwc3-am62: Fix an OF node leak in phy_syscon_pll_refclk() (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: 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: 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- 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- 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 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: Fix common size calculation for ML element (git-fixes).\n- wifi: mac80211: do not flush non-uploaded STAs (git-fixes).\n- wifi: mac80211: fix tid removal during mesh forwarding (git-fixes).\n- wifi: mac80211: prohibit deactivating all links (git-fixes).\n- wifi: mt76: connac: move mt7615_mcu_del_wtbl_all to connac (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 omac index assignment after hardware reset (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: mt7915: improve hardware restart reliability (stable-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: 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- 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-17T13:26:35Z","modified":"2026-02-04T03:55:19.562217Z","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-7301-1","title":"linux, linux-lowlatency, linux-lowlatency-hwe-6.8 vulnerabilities","description":"Attila Szász discovered that the HFS+ file system implementation in the\nLinux Kernel contained a heap overflow vulnerability. An attacker could use\na specially crafted file system image that, when mounted, could cause a\ndenial of service (system crash) or possibly execute arbitrary code.\n(CVE-2025-0927)\n\nSeveral security issues were discovered in the Linux kernel.\nAn attacker could possibly use these to compromise the system.\nThis update corrects flaws in the following subsystems:\n  - ARM32 architecture;\n  - x86 architecture;\n  - Block layer subsystem;\n  - Cryptographic API;\n  - ACPI drivers;\n  - Drivers core;\n  - ATA over ethernet (AOE) driver;\n  - Network block device driver;\n  - TPM device driver;\n  - Hardware crypto device drivers;\n  - ARM SCMI message protocol;\n  - EFI core;\n  - GPU drivers;\n  - I2C subsystem;\n  - I3C subsystem;\n  - InfiniBand drivers;\n  - Input Device core drivers;\n  - IOMMU subsystem;\n  - Mailbox framework;\n  - Media drivers;\n  - Ethernet bonding driver;\n  - Network drivers;\n  - Mellanox network drivers;\n  - STMicroelectronics network drivers;\n  - NTB driver;\n  - PCI subsystem;\n  - Alibaba DDR Sub-System Driveway PMU driver;\n  - x86 platform drivers;\n  - Powercap sysfs driver;\n  - Remote Processor subsystem;\n  - SCSI subsystem;\n  - USB Device Class drivers;\n  - vDPA drivers;\n  - Virtio Host (VHOST) subsystem;\n  - Framebuffer layer;\n  - AFS file system;\n  - BTRFS file system;\n  - File systems infrastructure;\n  - Ceph distributed file system;\n  - Ext4 file system;\n  - F2FS file system;\n  - JFS file system;\n  - Network file systems library;\n  - Network file system (NFS) server daemon;\n  - NILFS2 file system;\n  - SMB network file system;\n  - BPF subsystem;\n  - Virtio network driver;\n  - TCP network protocol;\n  - Perf events;\n  - Padata parallel execution mechanism;\n  - RCU subsystem;\n  - Arbitrary resource management;\n  - Static call mechanism;\n  - Tracing infrastructure;\n  - Memory management;\n  - Bluetooth subsystem;\n  - CAN network layer;\n  - Networking core;\n  - Distributed Switch Architecture;\n  - IPv4 networking;\n  - IPv6 networking;\n  - MAC80211 subsystem;\n  - IEEE 802.15.4 subsystem;\n  - NCSI (Network Controller Sideband Interface) driver;\n  - RxRPC session sockets;\n  - SCTP protocol;\n  - TIPC protocol;\n  - Wireless networking;\n  - AudioScience HPI driver;\n  - KVM core;\n(CVE-2024-47748, CVE-2024-49935, CVE-2024-49892, CVE-2024-49960,\nCVE-2024-49886, CVE-2024-47757, CVE-2024-47741, CVE-2024-49879,\nCVE-2024-49983, CVE-2024-47687, CVE-2024-49948, CVE-2024-49902,\nCVE-2024-49969, CVE-2024-49903, CVE-2024-47675, CVE-2024-47713,\nCVE-2024-47750, CVE-2024-49951, CVE-2024-49936, CVE-2024-49913,\nCVE-2024-47684, CVE-2024-49917, CVE-2024-47693, CVE-2024-49871,\nCVE-2024-47740, CVE-2024-49927, CVE-2024-47698, CVE-2024-49996,\nCVE-2024-47682, CVE-2024-49889, CVE-2024-49888, CVE-2024-47737,\nCVE-2024-49881, CVE-2023-52917, CVE-2024-47695, CVE-2024-50015,\nCVE-2024-49965, CVE-2024-50179, CVE-2024-47677, CVE-2024-50013,\nCVE-2024-49855, CVE-2024-47751, CVE-2024-49895, CVE-2024-49930,\nCVE-2024-49905, CVE-2024-47709, CVE-2024-49953, CVE-2024-49896,\nCVE-2024-47688, CVE-2024-47712, CVE-2024-49907, CVE-2024-49955,\nCVE-2024-49933, CVE-2024-49880, CVE-2024-49860, CVE-2024-50176,\nCVE-2024-47727, CVE-2024-47673, CVE-2024-49878, CVE-2024-49862,\nCVE-2024-49911, CVE-2024-47734, CVE-2024-49995, CVE-2024-49924,\nCVE-2024-49925, CVE-2024-47749, CVE-2024-49945, CVE-2024-49950,\nCVE-2024-49891, CVE-2024-49915, CVE-2024-50006, CVE-2024-49962,\nCVE-2024-49952, CVE-2024-49982, CVE-2024-49939, CVE-2024-49985,\nCVE-2024-49928, CVE-2024-47692, CVE-2024-49884, CVE-2024-47756,\nCVE-2024-49918, CVE-2024-49976, CVE-2024-47671, CVE-2024-49859,\nCVE-2024-47705, CVE-2024-49864, CVE-2024-47733, CVE-2024-49961,\nCVE-2024-49973, CVE-2024-49989, CVE-2024-47719, CVE-2024-47685,\nCVE-2024-49988, CVE-2024-49975, CVE-2024-47681, CVE-2024-49944,\nCVE-2024-47718, CVE-2024-47689, CVE-2024-50008, CVE-2024-49959,\nCVE-2024-49868, CVE-2024-47743, CVE-2024-49885, CVE-2024-47742,\nCVE-2024-49946, CVE-2024-49876, CVE-2024-49875, CVE-2024-49894,\nCVE-2024-49957, CVE-2024-49980, CVE-2024-49851, CVE-2024-47732,\nCVE-2024-47716, CVE-2024-49938, CVE-2024-50016, CVE-2024-47735,\nCVE-2024-47696, CVE-2024-47691, CVE-2024-49994, CVE-2024-49863,\nCVE-2024-50000, CVE-2024-49919, CVE-2024-49947, CVE-2024-50001,\nCVE-2024-47678, CVE-2024-49870, CVE-2024-53144, CVE-2024-49929,\nCVE-2024-47730, CVE-2024-47700, CVE-2024-49900, CVE-2024-47723,\nCVE-2024-49934, CVE-2024-49883, CVE-2024-49897, CVE-2024-49912,\nCVE-2024-49991, CVE-2024-47701, CVE-2024-49987, CVE-2024-47753,\nCVE-2024-49923, CVE-2024-47707, CVE-2024-49853, CVE-2024-47720,\nCVE-2024-49999, CVE-2024-49958, CVE-2024-49861, CVE-2024-49937,\nCVE-2024-49852, CVE-2024-47703, CVE-2024-47710, CVE-2024-49942,\nCVE-2024-49963, CVE-2024-47697, CVE-2024-50175, CVE-2024-47745,\nCVE-2024-49909, CVE-2024-49997, CVE-2024-49874, CVE-2024-47706,\nCVE-2024-49922, CVE-2024-47739, CVE-2024-49974, CVE-2024-47744,\nCVE-2024-47754, CVE-2024-49931, CVE-2024-47690, CVE-2024-49986,\nCVE-2024-47715, CVE-2024-50014, CVE-2024-49898, CVE-2024-47731,\nCVE-2024-47670, CVE-2024-49877, CVE-2024-50007, CVE-2024-47699,\nCVE-2024-49998, CVE-2024-41016, CVE-2024-49850, CVE-2024-47752,\nCVE-2024-49901, CVE-2024-47728, CVE-2024-49856, CVE-2024-49992,\nCVE-2024-49926, CVE-2024-49978, CVE-2024-47672, CVE-2024-49954,\nCVE-2024-47704, CVE-2024-47747, CVE-2024-47738, CVE-2024-49966,\nCVE-2024-47714, CVE-2024-47686, CVE-2024-47702, CVE-2024-49882,\nCVE-2024-49858, CVE-2024-50002, CVE-2024-49866, CVE-2024-49981,\nCVE-2024-50012, CVE-2024-50017, CVE-2024-49890, CVE-2024-49977,\nCVE-2024-49949, CVE-2024-50005, CVE-2024-47679, CVE-2024-49867)\n","status":"published","published":"2025-02-25T17:02:56Z","modified":"2026-10-29T20:02:50.830388961Z","updated_at":"2026-11-02T16:58:18.876384Z"},{"id":"USN-7303-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  - ARM32 architecture;\n  - x86 architecture;\n  - Block layer subsystem;\n  - Cryptographic API;\n  - ACPI drivers;\n  - Drivers core;\n  - ATA over ethernet (AOE) driver;\n  - Network block device driver;\n  - TPM device driver;\n  - Hardware crypto device drivers;\n  - ARM SCMI message protocol;\n  - EFI core;\n  - GPU drivers;\n  - I2C subsystem;\n  - I3C subsystem;\n  - InfiniBand drivers;\n  - Input Device core drivers;\n  - IOMMU subsystem;\n  - Mailbox framework;\n  - Media drivers;\n  - Ethernet bonding driver;\n  - Network drivers;\n  - Mellanox network drivers;\n  - STMicroelectronics network drivers;\n  - NTB driver;\n  - PCI subsystem;\n  - Alibaba DDR Sub-System Driveway PMU driver;\n  - x86 platform drivers;\n  - Powercap sysfs driver;\n  - Remote Processor subsystem;\n  - SCSI subsystem;\n  - USB Device Class drivers;\n  - vDPA drivers;\n  - Virtio Host (VHOST) subsystem;\n  - Framebuffer layer;\n  - AFS file system;\n  - BTRFS file system;\n  - File systems infrastructure;\n  - Ceph distributed file system;\n  - Ext4 file system;\n  - F2FS file system;\n  - JFS file system;\n  - Network file systems library;\n  - Network file system (NFS) server daemon;\n  - NILFS2 file system;\n  - SMB network file system;\n  - BPF subsystem;\n  - Virtio network driver;\n  - TCP network protocol;\n  - Perf events;\n  - Padata parallel execution mechanism;\n  - RCU subsystem;\n  - Arbitrary resource management;\n  - Static call mechanism;\n  - Tracing infrastructure;\n  - Memory management;\n  - Bluetooth subsystem;\n  - CAN network layer;\n  - Networking core;\n  - Distributed Switch Architecture;\n  - IPv4 networking;\n  - IPv6 networking;\n  - MAC80211 subsystem;\n  - IEEE 802.15.4 subsystem;\n  - NCSI (Network Controller Sideband Interface) driver;\n  - RxRPC session sockets;\n  - SCTP protocol;\n  - TIPC protocol;\n  - Wireless networking;\n  - AudioScience HPI driver;\n  - KVM core;\n(CVE-2024-49852, CVE-2024-50175, CVE-2024-47709, CVE-2024-47671,\nCVE-2024-50179, CVE-2024-47743, CVE-2024-47687, CVE-2024-49934,\nCVE-2024-47700, CVE-2024-49892, CVE-2024-49866, CVE-2024-50012,\nCVE-2024-49860, CVE-2024-49948, CVE-2024-49882, CVE-2024-47744,\nCVE-2024-49905, CVE-2024-47728, CVE-2024-49874, CVE-2024-47678,\nCVE-2024-47688, CVE-2024-47737, CVE-2024-49859, CVE-2024-49947,\nCVE-2024-49994, CVE-2024-49986, CVE-2024-49917, CVE-2024-50000,\nCVE-2024-49962, CVE-2024-47733, CVE-2024-47741, CVE-2024-47685,\nCVE-2024-47752, CVE-2024-49960, CVE-2024-47754, CVE-2024-47675,\nCVE-2024-49958, CVE-2024-47748, CVE-2024-47679, CVE-2024-47690,\nCVE-2024-47740, CVE-2024-47672, CVE-2024-49883, CVE-2024-49928,\nCVE-2024-49961, CVE-2024-47677, CVE-2024-47706, CVE-2024-49955,\nCVE-2024-49907, CVE-2024-47745, CVE-2024-49963, CVE-2024-47723,\nCVE-2024-49897, CVE-2024-49927, CVE-2024-50008, CVE-2024-47713,\nCVE-2024-49894, CVE-2024-49903, CVE-2024-47747, CVE-2024-47705,\nCVE-2024-49976, CVE-2024-53144, CVE-2024-49983, CVE-2024-49937,\nCVE-2024-49953, CVE-2024-41016, CVE-2024-49969, CVE-2024-49982,\nCVE-2024-50007, CVE-2024-50015, CVE-2024-49889, CVE-2024-49923,\nCVE-2024-49850, CVE-2024-47720, CVE-2024-49973, CVE-2024-49991,\nCVE-2024-49901, CVE-2024-49881, CVE-2024-49911, CVE-2024-47710,\nCVE-2024-49981, CVE-2024-49918, CVE-2024-49861, CVE-2024-49959,\nCVE-2024-50005, CVE-2024-47701, CVE-2024-49855, CVE-2024-49987,\nCVE-2024-47704, CVE-2024-49977, CVE-2024-47670, CVE-2024-47707,\nCVE-2024-47735, CVE-2024-49996, CVE-2024-49868, CVE-2024-47749,\nCVE-2024-49985, CVE-2024-47753, CVE-2024-49877, CVE-2024-47716,\nCVE-2024-47731, CVE-2024-49880, CVE-2024-47715, CVE-2024-49931,\nCVE-2024-49856, CVE-2024-49929, CVE-2024-47689, CVE-2024-49885,\nCVE-2024-50002, CVE-2024-49999, CVE-2024-47734, CVE-2024-49909,\nCVE-2024-49871, CVE-2024-49915, CVE-2024-50013, CVE-2024-47682,\nCVE-2024-49864, CVE-2024-49949, CVE-2024-49933, CVE-2024-49975,\nCVE-2024-49863, CVE-2024-49867, CVE-2024-49951, CVE-2024-50014,\nCVE-2024-47739, CVE-2024-49886, CVE-2024-49891, CVE-2024-49879,\nCVE-2024-47696, CVE-2024-49896, CVE-2024-49988, CVE-2024-47691,\nCVE-2024-47732, CVE-2024-47742, CVE-2024-47698, CVE-2024-49925,\nCVE-2024-47695, CVE-2024-49898, CVE-2024-49989, CVE-2024-49913,\nCVE-2024-49935, CVE-2024-50017, CVE-2024-47703, CVE-2024-49954,\nCVE-2024-49875, CVE-2024-49858, CVE-2024-49997, CVE-2024-49895,\nCVE-2024-47719, CVE-2024-47750, CVE-2024-47693, CVE-2024-49926,\nCVE-2024-50001, CVE-2024-47718, CVE-2024-47714, CVE-2024-49919,\nCVE-2024-49938, CVE-2024-49952, CVE-2024-49942, CVE-2024-49957,\nCVE-2024-49930, CVE-2024-47702, CVE-2024-50006, CVE-2024-49888,\nCVE-2024-47756, CVE-2024-49890, CVE-2024-50176, CVE-2024-47686,\nCVE-2024-49978, CVE-2024-47697, CVE-2024-49974, CVE-2024-47751,\nCVE-2024-47712, CVE-2024-47727, CVE-2023-52917, CVE-2024-49980,\nCVE-2024-49965, CVE-2024-49878, CVE-2024-50016, CVE-2024-47738,\nCVE-2024-47681, CVE-2024-47699, CVE-2024-49998, CVE-2024-49902,\nCVE-2024-49966, CVE-2024-49884, CVE-2024-49936, CVE-2024-47757,\nCVE-2024-49851, CVE-2024-49924, CVE-2024-49944, CVE-2024-49912,\nCVE-2024-49992, CVE-2024-47684, CVE-2024-49950, CVE-2024-49939,\nCVE-2024-47730, CVE-2024-49853, CVE-2024-49862, CVE-2024-49900,\nCVE-2024-49876, CVE-2024-49945, CVE-2024-47673, CVE-2024-49870,\nCVE-2024-47692, CVE-2024-49946, CVE-2024-49995, CVE-2024-49922)\n","status":"published","published":"2025-02-26T10:38:31Z","modified":"2026-10-29T20:02:51.708551667Z","updated_at":"2026-11-02T16:58:18.876384Z"},{"id":"USN-7303-2","title":"linux-oracle, linux-oracle-6.8 vulnerabilities","description":"Several security issues were discovered in the Linux kernel.\nAn attacker could possibly use these to compromise the system.\nThis update corrects flaws in the following subsystems:\n  - ARM32 architecture;\n  - x86 architecture;\n  - Block layer subsystem;\n  - Cryptographic API;\n  - ACPI drivers;\n  - Drivers core;\n  - ATA over ethernet (AOE) driver;\n  - Network block device driver;\n  - TPM device driver;\n  - Hardware crypto device drivers;\n  - ARM SCMI message protocol;\n  - EFI core;\n  - GPU drivers;\n  - I2C subsystem;\n  - I3C subsystem;\n  - InfiniBand drivers;\n  - Input Device core drivers;\n  - IOMMU subsystem;\n  - Mailbox framework;\n  - Media drivers;\n  - Ethernet bonding driver;\n  - Network drivers;\n  - Mellanox network drivers;\n  - STMicroelectronics network drivers;\n  - NTB driver;\n  - PCI subsystem;\n  - Alibaba DDR Sub-System Driveway PMU driver;\n  - x86 platform drivers;\n  - Powercap sysfs driver;\n  - Remote Processor subsystem;\n  - SCSI subsystem;\n  - USB Device Class drivers;\n  - vDPA drivers;\n  - Virtio Host (VHOST) subsystem;\n  - Framebuffer layer;\n  - AFS file system;\n  - BTRFS file system;\n  - File systems infrastructure;\n  - Ceph distributed file system;\n  - Ext4 file system;\n  - F2FS file system;\n  - JFS file system;\n  - Network file systems library;\n  - Network file system (NFS) server daemon;\n  - NILFS2 file system;\n  - SMB network file system;\n  - BPF subsystem;\n  - Virtio network driver;\n  - TCP network protocol;\n  - Perf events;\n  - Padata parallel execution mechanism;\n  - RCU subsystem;\n  - Arbitrary resource management;\n  - Static call mechanism;\n  - Tracing infrastructure;\n  - Memory management;\n  - Bluetooth subsystem;\n  - CAN network layer;\n  - Networking core;\n  - Distributed Switch Architecture;\n  - IPv4 networking;\n  - IPv6 networking;\n  - MAC80211 subsystem;\n  - IEEE 802.15.4 subsystem;\n  - NCSI (Network Controller Sideband Interface) driver;\n  - RxRPC session sockets;\n  - SCTP protocol;\n  - TIPC protocol;\n  - Wireless networking;\n  - AudioScience HPI driver;\n  - KVM core;\n(CVE-2024-47718, CVE-2024-49942, CVE-2024-49897, CVE-2024-49871,\nCVE-2024-47687, CVE-2024-47692, CVE-2024-47740, CVE-2024-47691,\nCVE-2024-49973, CVE-2024-49958, CVE-2024-49889, CVE-2024-49927,\nCVE-2024-49883, CVE-2024-49885, CVE-2024-49912, CVE-2024-47686,\nCVE-2024-49985, CVE-2024-47732, CVE-2024-47685, CVE-2024-49935,\nCVE-2024-49995, CVE-2024-47731, CVE-2024-49931, CVE-2024-49886,\nCVE-2024-53144, CVE-2024-49917, CVE-2024-49868, CVE-2024-49999,\nCVE-2024-47684, CVE-2024-50013, CVE-2024-49962, CVE-2024-49981,\nCVE-2024-49858, CVE-2024-49878, CVE-2024-49852, CVE-2024-49928,\nCVE-2024-50006, CVE-2024-49988, CVE-2024-47697, CVE-2024-49923,\nCVE-2024-47704, CVE-2024-49947, CVE-2024-47751, CVE-2024-47672,\nCVE-2024-47737, CVE-2024-49909, CVE-2024-49992, CVE-2024-49944,\nCVE-2024-49950, CVE-2024-49850, CVE-2024-49951, CVE-2024-49996,\nCVE-2024-49934, CVE-2024-47705, CVE-2024-47741, CVE-2024-49957,\nCVE-2024-47682, CVE-2024-49976, CVE-2024-49895, CVE-2024-47689,\nCVE-2024-49937, CVE-2024-47702, CVE-2024-49959, CVE-2024-47719,\nCVE-2024-49922, CVE-2024-47743, CVE-2024-47696, CVE-2024-50017,\nCVE-2024-49864, CVE-2024-47747, CVE-2024-47748, CVE-2024-47701,\nCVE-2024-49915, CVE-2024-49877, CVE-2024-41016, CVE-2024-49961,\nCVE-2024-47730, CVE-2024-49924, CVE-2024-49974, CVE-2024-49875,\nCVE-2024-49918, CVE-2024-47712, CVE-2024-50014, CVE-2024-47679,\nCVE-2024-49894, CVE-2024-49911, CVE-2024-49855, CVE-2024-49948,\nCVE-2024-49955, CVE-2023-52917, CVE-2024-50015, CVE-2024-47754,\nCVE-2024-49929, CVE-2024-50005, CVE-2024-47742, CVE-2024-49991,\nCVE-2024-49913, CVE-2024-49980, CVE-2024-47749, CVE-2024-49975,\nCVE-2024-47671, CVE-2024-47677, CVE-2024-47727, CVE-2024-47716,\nCVE-2024-47707, CVE-2024-49870, CVE-2024-47703, CVE-2024-47710,\nCVE-2024-49977, CVE-2024-49997, CVE-2024-49853, CVE-2024-47681,\nCVE-2024-49986, CVE-2024-49969, CVE-2024-50000, CVE-2024-47690,\nCVE-2024-47709, CVE-2024-47713, CVE-2024-47720, CVE-2024-49879,\nCVE-2024-47699, CVE-2024-47714, CVE-2024-50012, CVE-2024-49880,\nCVE-2024-49946, CVE-2024-47735, CVE-2024-49876, CVE-2024-49963,\nCVE-2024-50176, CVE-2024-49952, CVE-2024-49881, CVE-2024-49987,\nCVE-2024-49919, CVE-2024-49860, CVE-2024-47744, CVE-2024-47723,\nCVE-2024-50001, CVE-2024-47756, CVE-2024-49867, CVE-2024-47728,\nCVE-2024-49933, CVE-2024-47752, CVE-2024-49998, CVE-2024-50179,\nCVE-2024-47706, CVE-2024-49989, CVE-2024-47670, CVE-2024-49965,\nCVE-2024-47673, CVE-2024-47700, CVE-2024-47688, CVE-2024-49953,\nCVE-2024-50016, CVE-2024-49907, CVE-2024-49930, CVE-2024-50002,\nCVE-2024-49859, CVE-2024-49939, CVE-2024-47675, CVE-2024-49861,\nCVE-2024-50175, CVE-2024-47757, CVE-2024-49900, CVE-2024-49954,\nCVE-2024-49982, CVE-2024-49891, CVE-2024-47678, CVE-2024-49936,\nCVE-2024-49901, CVE-2024-49898, CVE-2024-47693, CVE-2024-50007,\nCVE-2024-49896, CVE-2024-49863, CVE-2024-47750, CVE-2024-49949,\nCVE-2024-49888, CVE-2024-47739, CVE-2024-49983, CVE-2024-47695,\nCVE-2024-47738, CVE-2024-47734, CVE-2024-49892, CVE-2024-47698,\nCVE-2024-49902, CVE-2024-47715, CVE-2024-49926, CVE-2024-49882,\nCVE-2024-49978, CVE-2024-49945, CVE-2024-49925, CVE-2024-47733,\nCVE-2024-49874, CVE-2024-49856, CVE-2024-49966, CVE-2024-49960,\nCVE-2024-49905, CVE-2024-49866, CVE-2024-49903, CVE-2024-49862,\nCVE-2024-50008, CVE-2024-49994, CVE-2024-49851, CVE-2024-47745,\nCVE-2024-49884, CVE-2024-47753, CVE-2024-49938, CVE-2024-49890)\n","status":"published","published":"2025-02-28T10:53:13Z","modified":"2026-10-29T20:02:42.114843211Z","updated_at":"2026-11-02T16:58:18.876384Z"},{"id":"USN-7303-3","title":"linux-gcp-6.8, 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  - ARM32 architecture;\n  - x86 architecture;\n  - Block layer subsystem;\n  - Cryptographic API;\n  - ACPI drivers;\n  - Drivers core;\n  - ATA over ethernet (AOE) driver;\n  - Network block device driver;\n  - TPM device driver;\n  - Hardware crypto device drivers;\n  - ARM SCMI message protocol;\n  - EFI core;\n  - GPU drivers;\n  - I2C subsystem;\n  - I3C subsystem;\n  - InfiniBand drivers;\n  - Input Device core drivers;\n  - IOMMU subsystem;\n  - Mailbox framework;\n  - Media drivers;\n  - Ethernet bonding driver;\n  - Network drivers;\n  - Mellanox network drivers;\n  - STMicroelectronics network drivers;\n  - NTB driver;\n  - PCI subsystem;\n  - Alibaba DDR Sub-System Driveway PMU driver;\n  - x86 platform drivers;\n  - Powercap sysfs driver;\n  - Remote Processor subsystem;\n  - SCSI subsystem;\n  - USB Device Class drivers;\n  - vDPA drivers;\n  - Virtio Host (VHOST) subsystem;\n  - Framebuffer layer;\n  - AFS file system;\n  - BTRFS file system;\n  - File systems infrastructure;\n  - Ceph distributed file system;\n  - Ext4 file system;\n  - F2FS file system;\n  - JFS file system;\n  - Network file systems library;\n  - Network file system (NFS) server daemon;\n  - NILFS2 file system;\n  - SMB network file system;\n  - BPF subsystem;\n  - Virtio network driver;\n  - TCP network protocol;\n  - Perf events;\n  - Padata parallel execution mechanism;\n  - RCU subsystem;\n  - Arbitrary resource management;\n  - Static call mechanism;\n  - Tracing infrastructure;\n  - Memory management;\n  - Bluetooth subsystem;\n  - CAN network layer;\n  - Networking core;\n  - Distributed Switch Architecture;\n  - IPv4 networking;\n  - IPv6 networking;\n  - MAC80211 subsystem;\n  - IEEE 802.15.4 subsystem;\n  - NCSI (Network Controller Sideband Interface) driver;\n  - RxRPC session sockets;\n  - SCTP protocol;\n  - TIPC protocol;\n  - Wireless networking;\n  - AudioScience HPI driver;\n  - KVM core;\n(CVE-2024-47709, CVE-2024-49889, CVE-2024-49931, CVE-2024-50008,\nCVE-2024-49969, CVE-2024-49975, CVE-2024-49958, CVE-2024-47756,\nCVE-2024-49944, CVE-2024-47707, CVE-2024-47693, CVE-2024-47686,\nCVE-2024-47734, CVE-2024-47750, CVE-2024-50179, CVE-2024-49942,\nCVE-2024-49864, CVE-2024-49891, CVE-2024-49965, CVE-2024-49905,\nCVE-2024-47719, CVE-2024-49877, CVE-2024-47688, CVE-2024-47691,\nCVE-2024-47710, CVE-2024-47748, CVE-2024-49948, CVE-2024-49998,\nCVE-2024-47673, CVE-2024-47738, CVE-2024-47701, CVE-2024-47705,\nCVE-2024-49930, CVE-2024-49985, CVE-2024-50016, CVE-2024-53144,\nCVE-2023-52917, CVE-2024-47690, CVE-2024-47675, CVE-2024-50176,\nCVE-2024-49922, CVE-2024-47704, CVE-2024-49982, CVE-2024-47741,\nCVE-2024-49991, CVE-2024-49902, CVE-2024-49883, CVE-2024-49892,\nCVE-2024-50002, CVE-2024-49945, CVE-2024-49959, CVE-2024-47732,\nCVE-2024-49856, CVE-2024-47677, CVE-2024-49978, CVE-2024-49966,\nCVE-2024-49937, CVE-2024-47744, CVE-2024-49890, CVE-2024-47739,\nCVE-2024-50012, CVE-2024-47742, CVE-2024-49980, CVE-2024-47706,\nCVE-2024-49994, CVE-2024-50017, CVE-2024-47697, CVE-2024-49996,\nCVE-2024-49953, CVE-2024-49871, CVE-2024-47723, CVE-2024-49987,\nCVE-2024-49917, CVE-2024-49888, CVE-2024-49866, CVE-2024-50005,\nCVE-2024-47681, CVE-2024-49870, CVE-2024-49898, CVE-2024-49981,\nCVE-2024-49947, CVE-2024-49918, CVE-2024-49983, CVE-2024-47698,\nCVE-2024-49850, CVE-2024-50007, CVE-2024-49900, CVE-2024-49923,\nCVE-2024-49909, CVE-2024-47687, CVE-2024-50015, CVE-2024-47715,\nCVE-2024-47745, CVE-2024-49926, CVE-2024-49879, CVE-2024-49986,\nCVE-2024-49929, CVE-2024-49949, CVE-2024-49976, CVE-2024-47749,\nCVE-2024-47689, CVE-2024-47720, CVE-2024-47743, CVE-2024-49878,\nCVE-2024-49935, CVE-2024-49955, CVE-2024-49997, CVE-2024-49860,\nCVE-2024-47703, CVE-2024-50175, CVE-2024-49855, CVE-2024-49861,\nCVE-2024-49951, CVE-2024-49863, CVE-2024-49882, CVE-2024-50000,\nCVE-2024-49912, CVE-2024-49974, CVE-2024-49977, CVE-2024-47752,\nCVE-2024-47700, CVE-2024-49911, CVE-2024-49852, CVE-2024-47740,\nCVE-2024-47671, CVE-2024-49988, CVE-2024-47699, CVE-2024-47757,\nCVE-2024-49933, CVE-2024-49913, CVE-2024-49907, CVE-2024-49881,\nCVE-2024-47751, CVE-2024-47753, CVE-2024-47731, CVE-2024-47730,\nCVE-2024-49934, CVE-2024-49957, CVE-2024-49938, CVE-2024-47728,\nCVE-2024-49867, CVE-2024-47754, CVE-2024-49919, CVE-2024-49992,\nCVE-2024-49950, CVE-2024-49954, CVE-2024-49924, CVE-2024-47670,\nCVE-2024-50014, CVE-2024-47684, CVE-2024-49884, CVE-2024-47678,\nCVE-2024-49894, CVE-2024-49859, CVE-2024-47735, CVE-2024-47696,\nCVE-2024-49999, CVE-2024-49880, CVE-2024-47747, CVE-2024-49885,\nCVE-2024-49963, CVE-2024-49995, CVE-2024-49897, CVE-2024-49868,\nCVE-2024-49862, CVE-2024-49928, CVE-2024-47685, CVE-2024-47692,\nCVE-2024-49927, CVE-2024-47695, CVE-2024-49896, CVE-2024-49875,\nCVE-2024-49853, CVE-2024-47714, CVE-2024-49989, CVE-2024-49858,\nCVE-2024-49952, CVE-2024-49973, CVE-2024-49925, CVE-2024-49851,\nCVE-2024-47712, CVE-2024-49961, CVE-2024-47713, CVE-2024-47718,\nCVE-2024-49962, CVE-2024-47737, CVE-2024-50001, CVE-2024-49876,\nCVE-2024-49903, CVE-2024-49939, CVE-2024-49886, CVE-2024-47679,\nCVE-2024-50006, CVE-2024-49874, CVE-2024-47716, CVE-2024-49895,\nCVE-2024-47727, CVE-2024-47672, CVE-2024-49901, CVE-2024-47733,\nCVE-2024-47682, CVE-2024-47702, CVE-2024-50013, CVE-2024-41016,\nCVE-2024-49960, CVE-2024-49936, CVE-2024-49946, CVE-2024-49915)\n","status":"published","published":"2025-03-03T18:27:41Z","modified":"2026-10-29T20:02:41.955489796Z","updated_at":"2026-11-02T16:58:18.876384Z"},{"id":"USN-7304-1","title":"linux-gcp, linux-gke, linux-gkeop vulnerabilities","description":"Several security issues were discovered in the Linux kernel.\nAn attacker could possibly use these to compromise the system.\nThis update corrects flaws in the following subsystems:\n  - ARM32 architecture;\n  - x86 architecture;\n  - Block layer subsystem;\n  - Cryptographic API;\n  - ACPI drivers;\n  - Drivers core;\n  - ATA over ethernet (AOE) driver;\n  - Network block device driver;\n  - TPM device driver;\n  - Hardware crypto device drivers;\n  - ARM SCMI message protocol;\n  - EFI core;\n  - GPU drivers;\n  - I2C subsystem;\n  - I3C subsystem;\n  - InfiniBand drivers;\n  - Input Device core drivers;\n  - IOMMU subsystem;\n  - Mailbox framework;\n  - Media drivers;\n  - Ethernet bonding driver;\n  - Network drivers;\n  - Mellanox network drivers;\n  - STMicroelectronics network drivers;\n  - NTB driver;\n  - PCI subsystem;\n  - Alibaba DDR Sub-System Driveway PMU driver;\n  - x86 platform drivers;\n  - Powercap sysfs driver;\n  - Remote Processor subsystem;\n  - SCSI subsystem;\n  - USB Device Class drivers;\n  - vDPA drivers;\n  - Virtio Host (VHOST) subsystem;\n  - Framebuffer layer;\n  - AFS file system;\n  - BTRFS file system;\n  - File systems infrastructure;\n  - Ceph distributed file system;\n  - Ext4 file system;\n  - F2FS file system;\n  - JFS file system;\n  - Network file systems library;\n  - Network file system (NFS) server daemon;\n  - NILFS2 file system;\n  - SMB network file system;\n  - BPF subsystem;\n  - Virtio network driver;\n  - TCP network protocol;\n  - Perf events;\n  - Padata parallel execution mechanism;\n  - RCU subsystem;\n  - Arbitrary resource management;\n  - Static call mechanism;\n  - Tracing infrastructure;\n  - Memory management;\n  - Bluetooth subsystem;\n  - CAN network layer;\n  - Networking core;\n  - Distributed Switch Architecture;\n  - IPv4 networking;\n  - IPv6 networking;\n  - MAC80211 subsystem;\n  - IEEE 802.15.4 subsystem;\n  - NCSI (Network Controller Sideband Interface) driver;\n  - RxRPC session sockets;\n  - SCTP protocol;\n  - TIPC protocol;\n  - Wireless networking;\n  - AudioScience HPI driver;\n  - KVM core;\n(CVE-2024-47678, CVE-2024-49952, CVE-2024-47682, CVE-2024-47679,\nCVE-2024-47748, CVE-2024-47728, CVE-2024-49953, CVE-2024-49883,\nCVE-2024-47742, CVE-2024-50000, CVE-2024-47733, CVE-2024-47752,\nCVE-2024-49927, CVE-2024-47713, CVE-2024-49853, CVE-2024-49998,\nCVE-2024-47672, CVE-2024-49900, CVE-2024-49884, CVE-2024-49876,\nCVE-2024-47673, CVE-2024-49958, CVE-2024-50274, CVE-2024-49980,\nCVE-2024-47703, CVE-2024-49891, CVE-2024-47716, CVE-2024-49903,\nCVE-2024-49868, CVE-2024-47699, CVE-2024-50015, CVE-2024-49896,\nCVE-2024-49867, CVE-2024-50016, CVE-2024-49862, CVE-2024-49947,\nCVE-2024-47714, CVE-2024-50179, CVE-2024-50006, CVE-2024-49881,\nCVE-2024-49933, CVE-2024-49882, CVE-2024-47709, CVE-2024-47686,\nCVE-2024-49859, CVE-2024-49992, CVE-2024-49957, CVE-2024-47691,\nCVE-2024-49936, CVE-2024-49878, CVE-2024-49879, CVE-2024-49997,\nCVE-2024-47697, CVE-2024-49963, CVE-2024-49938, CVE-2024-47723,\nCVE-2024-47700, CVE-2024-49999, CVE-2024-49923, CVE-2024-49991,\nCVE-2024-50013, CVE-2024-47730, CVE-2024-47718, CVE-2024-47671,\nCVE-2024-49977, CVE-2024-53144, CVE-2024-49922, CVE-2024-49985,\nCVE-2024-47712, CVE-2024-49962, CVE-2024-49907, CVE-2024-49886,\nCVE-2024-49976, CVE-2024-49902, CVE-2024-47732, CVE-2024-49995,\nCVE-2024-49942, CVE-2024-47706, CVE-2024-47747, CVE-2024-49949,\nCVE-2024-49911, CVE-2024-49929, CVE-2024-47737, CVE-2024-47720,\nCVE-2024-47756, CVE-2024-47688, CVE-2024-47753, CVE-2024-49937,\nCVE-2024-47684, CVE-2024-47690, CVE-2024-49897, CVE-2024-47705,\nCVE-2024-49852, CVE-2024-49930, CVE-2024-47681, CVE-2024-50175,\nCVE-2024-49863, CVE-2024-49969, CVE-2024-49894, CVE-2024-49928,\nCVE-2024-47698, CVE-2024-47710, CVE-2024-49931, CVE-2024-50008,\nCVE-2024-49939, CVE-2024-49915, CVE-2024-47757, CVE-2024-49912,\nCVE-2024-47696, CVE-2024-47702, CVE-2024-49877, CVE-2024-49974,\nCVE-2024-49919, CVE-2024-49888, CVE-2024-49871, CVE-2024-47685,\nCVE-2024-47734, CVE-2024-49965, CVE-2024-47707, CVE-2024-49987,\nCVE-2024-47745, CVE-2024-50001, CVE-2024-49960, CVE-2024-50014,\nCVE-2024-49994, CVE-2024-49875, CVE-2024-49856, CVE-2024-49926,\nCVE-2024-47701, CVE-2024-47749, CVE-2024-47715, CVE-2024-49981,\nCVE-2024-49935, CVE-2024-47754, CVE-2024-47692, CVE-2024-49864,\nCVE-2024-49983, CVE-2024-49950, CVE-2024-49917, CVE-2024-49924,\nCVE-2024-47743, CVE-2024-47693, CVE-2024-50176, CVE-2024-47670,\nCVE-2024-47727, CVE-2024-47739, CVE-2024-49978, CVE-2024-49858,\nCVE-2024-49861, CVE-2024-49946, CVE-2024-50012, CVE-2024-49934,\nCVE-2024-49986, CVE-2023-52917, CVE-2024-49870, CVE-2024-49892,\nCVE-2024-47741, CVE-2024-47731, CVE-2024-47675, CVE-2024-49898,\nCVE-2024-49959, CVE-2024-49988, CVE-2024-49918, CVE-2024-50002,\nCVE-2024-49954, CVE-2024-49944, CVE-2024-49996, CVE-2024-49982,\nCVE-2024-49948, CVE-2024-49901, CVE-2024-47735, CVE-2024-49851,\nCVE-2024-50007, CVE-2024-49895, CVE-2024-47744, CVE-2024-49889,\nCVE-2024-50017, CVE-2024-49945, CVE-2024-49890, CVE-2024-49850,\nCVE-2024-47677, CVE-2024-47704, CVE-2024-49874, CVE-2024-49860,\nCVE-2024-49961, CVE-2024-49975, CVE-2024-41016, CVE-2024-49951,\nCVE-2024-49909, CVE-2024-49955, CVE-2024-49885, CVE-2024-50005,\nCVE-2024-47750, CVE-2024-47695, CVE-2024-49913, CVE-2024-49925,\nCVE-2024-47689, CVE-2024-49866, CVE-2024-49973, CVE-2024-47751,\nCVE-2024-49880, CVE-2024-49855, CVE-2024-49989, CVE-2024-47740,\nCVE-2024-47687, CVE-2024-47738, CVE-2024-47719, CVE-2024-49905,\nCVE-2024-53064, CVE-2024-49966)\n","status":"published","published":"2025-02-26T10:58:00Z","modified":"2026-10-29T20:02:51.173670159Z","updated_at":"2026-11-02T16:58:18.876384Z"},{"id":"USN-7310-1","title":"linux-oem-6.11 vulnerabilities","description":"Attila Szász discovered that the HFS+ file system implementation in the\nLinux Kernel contained a heap overflow vulnerability. An attacker could use\na specially crafted file system image that, when mounted, could cause a\ndenial of service (system crash) or possibly execute arbitrary code.\n(CVE-2025-0927)\n\nSeveral security issues were discovered in the Linux kernel.\nAn attacker could possibly use these to compromise the system.\nThis update corrects flaws in the following subsystems:\n  - ARM32 architecture;\n  - ARM64 architecture;\n  - PowerPC architecture;\n  - RISC-V architecture;\n  - S390 architecture;\n  - SuperH RISC architecture;\n  - User-Mode Linux (UML);\n  - x86 architecture;\n  - Block layer subsystem;\n  - Cryptographic API;\n  - Compute Acceleration Framework;\n  - ACPI drivers;\n  - Drivers core;\n  - ATA over ethernet (AOE) driver;\n  - RAM backed block device driver;\n  - Network block device driver;\n  - Ublk userspace block driver;\n  - Compressed RAM block device driver;\n  - Bluetooth drivers;\n  - TPM device driver;\n  - Clock framework and drivers;\n  - Data acquisition framework and drivers;\n  - CPU frequency scaling framework;\n  - Hardware crypto device drivers;\n  - CXL (Compute Express Link) drivers;\n  - DAX dirext access to differentiated memory framework;\n  - Buffer Sharing and Synchronization framework;\n  - EDAC drivers;\n  - FireWire subsystem;\n  - ARM SCMI message protocol;\n  - ARM SCPI message protocol;\n  - EFI core;\n  - Qualcomm firmware drivers;\n  - GPIO subsystem;\n  - GPU drivers;\n  - HID subsystem;\n  - I2C subsystem;\n  - I3C subsystem;\n  - IIO ADC drivers;\n  - IIO subsystem;\n  - InfiniBand drivers;\n  - Input Device core drivers;\n  - IOMMU subsystem;\n  - IRQ chip drivers;\n  - Mailbox framework;\n  - Multiple devices driver;\n  - Media drivers;\n  - Multifunction device drivers;\n  - MMC subsystem;\n  - MTD block device drivers;\n  - Ethernet bonding driver;\n  - Network drivers;\n  - Mellanox network drivers;\n  - STMicroelectronics network drivers;\n  - NTB driver;\n  - Virtio pmem driver;\n  - NVME drivers;\n  - Parport drivers;\n  - PCI subsystem;\n  - Alibaba DDR Sub-System Driveway PMU driver;\n  - PHY drivers;\n  - Pin controllers subsystem;\n  - x86 platform drivers;\n  - i.MX PM domains;\n  - Powercap sysfs driver;\n  - Voltage and Current Regulator drivers;\n  - Remote Processor subsystem;\n  - StarFive reset controller drivers;\n  - Real Time Clock drivers;\n  - SCSI subsystem;\n  - SuperH / SH-Mobile drivers;\n  - QCOM SoC drivers;\n  - Xilinx SoC drivers;\n  - SPI subsystem;\n  - Direct Digital Synthesis drivers;\n  - Media staging drivers;\n  - TCM subsystem;\n  - Thermal drivers;\n  - Thunderbolt and USB4 drivers;\n  - TTY drivers;\n  - UFS subsystem;\n  - USB Device Class drivers;\n  - DesignWare USB3 driver;\n  - USB Gadget drivers;\n  - USB Host Controller drivers;\n  - USB Dual Role (OTG-ready) Controller drivers;\n  - USB Serial drivers;\n  - USB Type-C support driver;\n  - USB Type-C Port Controller Manager driver;\n  - TI TPS6598x USB Power Delivery controller driver;\n  - USB Type-C Connector System Software Interface driver;\n  - vDPA drivers;\n  - VFIO drivers;\n  - Virtio Host (VHOST) subsystem;\n  - Framebuffer layer;\n  - Virtio drivers;\n  - Xen hypervisor drivers;\n  - AFS file system;\n  - BTRFS file system;\n  - File systems infrastructure;\n  - Ceph distributed file system;\n  - EROFS file system;\n  - Ext4 file system;\n  - F2FS file system;\n  - GFS2 file system;\n  - JFS file system;\n  - Network file systems library;\n  - Network file system (NFS) client;\n  - Network file system (NFS) server daemon;\n  - NILFS2 file system;\n  - File system notification infrastructure;\n  - NTFS3 file system;\n  - Proc file system;\n  - SMB network file system;\n  - UBI file system;\n  - BPF subsystem;\n  - Network file system (NFS) superblock;\n  - Virtio network driver;\n  - Bluetooth subsystem;\n  - Network traffic control;\n  - Network sockets;\n  - TCP network protocol;\n  - Tracing infrastructure;\n  - User-space API (UAPI);\n  - Kernel init infrastructure;\n  - io_uring subsystem;\n  - IPC subsystem;\n  - Perf events;\n  - Kernel fork() syscall;\n  - Kernel thread helper (kthread);\n  - Padata parallel execution mechanism;\n  - RCU subsystem;\n  - Arbitrary resource management;\n  - Scheduler infrastructure;\n  - Signal handling mechanism;\n  - Static call mechanism;\n  - Task handling mechanism;\n  - Timer substystem drivers;\n  - Maple Tree data structure library;\n  - Memory management;\n  - 9P file system network protocol;\n  - Ethernet bridge;\n  - CAN network layer;\n  - Networking core;\n  - DCCP (Datagram Congestion Control Protocol);\n  - Distributed Switch Architecture;\n  - IPv4 networking;\n  - IPv6 networking;\n  - IUCV driver;\n  - L2TP protocol;\n  - MAC80211 subsystem;\n  - IEEE 802.15.4 subsystem;\n  - Multipath TCP;\n  - NCSI (Network Controller Sideband Interface) driver;\n  - Netfilter;\n  - Netlink;\n  - RxRPC session sockets;\n  - SCTP protocol;\n  - SMC sockets;\n  - Sun RPC protocol;\n  - TIPC protocol;\n  - Unix domain sockets;\n  - VMware vSockets driver;\n  - Wireless networking;\n  - eXpress Data Path;\n  - XFRM subsystem;\n  - AppArmor security module;\n  - Integrity Measurement Architecture(IMA) framework;\n  - Key management;\n  - ALSA framework;\n  - FireWire sound drivers;\n  - AudioScience HPI driver;\n  - HD-audio driver;\n  - SoC Audio for Freescale CPUs drivers;\n  - MediaTek ASoC drivers;\n  - QCOM ASoC drivers;\n  - SoC audio core drivers;\n  - STMicroelectronics SoC drivers;\n  - USB sound devices;\n  - KVM core;\n(CVE-2024-50244, CVE-2024-56754, CVE-2024-50082, CVE-2024-47737,\nCVE-2024-50300, CVE-2024-49872, CVE-2024-50180, CVE-2024-50218,\nCVE-2024-49956, CVE-2024-53189, CVE-2024-56705, CVE-2024-50119,\nCVE-2024-53192, CVE-2024-49950, CVE-2024-56722, CVE-2024-49943,\nCVE-2024-50031, CVE-2024-47685, CVE-2024-50296, CVE-2024-49939,\nCVE-2024-47696, CVE-2024-47752, CVE-2024-49937, CVE-2024-53140,\nCVE-2024-50236, CVE-2024-50151, CVE-2024-50069, CVE-2024-50170,\nCVE-2024-50246, CVE-2024-50217, CVE-2024-53125, CVE-2024-50084,\nCVE-2024-50005, CVE-2024-53137, CVE-2024-50233, CVE-2024-49991,\nCVE-2024-50067, CVE-2024-50290, CVE-2024-47735, CVE-2024-53133,\nCVE-2024-50289, CVE-2024-49855, CVE-2024-49868, CVE-2024-56728,\nCVE-2024-56726, CVE-2024-50012, CVE-2024-53078, CVE-2024-50223,\nCVE-2024-50143, CVE-2024-50287, CVE-2024-49971, CVE-2024-49900,\nCVE-2024-50263, CVE-2024-50206, CVE-2024-47707, CVE-2024-47751,\nCVE-2024-56747, CVE-2024-50260, CVE-2024-50173, CVE-2024-47680,\nCVE-2024-50009, CVE-2024-53219, CVE-2024-53144, CVE-2024-50008,\nCVE-2024-53208, CVE-2024-49966, CVE-2024-50104, CVE-2024-50030,\nCVE-2024-53049, CVE-2024-53201, CVE-2024-50130, CVE-2024-49856,\nCVE-2024-53095, CVE-2024-50033, CVE-2024-47730, CVE-2024-53216,\nCVE-2024-50286, CVE-2024-50284, CVE-2024-47744, CVE-2023-52917,\nCVE-2024-50275, CVE-2024-53114, CVE-2024-49968, CVE-2024-50111,\nCVE-2024-50000, CVE-2024-53081, CVE-2024-49857, CVE-2024-50262,\nCVE-2024-50281, CVE-2024-53156, CVE-2024-50225, CVE-2024-53239,\nCVE-2024-50036, CVE-2024-50187, CVE-2024-53165, CVE-2024-49931,\nCVE-2024-53111, CVE-2024-49862, CVE-2024-47701, CVE-2024-53091,\nCVE-2024-50103, CVE-2024-53046, CVE-2024-56678, CVE-2024-56749,\nCVE-2024-53175, CVE-2024-49970, CVE-2024-50035, CVE-2024-50088,\nCVE-2024-50297, CVE-2024-47721, CVE-2024-50240, CVE-2024-50076,\nCVE-2024-56683, CVE-2024-53120, CVE-2024-50074, CVE-2024-50095,\nCVE-2024-49963, CVE-2024-50158, CVE-2024-50020, CVE-2024-53083,\nCVE-2024-50029, CVE-2024-56755, CVE-2024-49969, CVE-2024-50022,\nCVE-2024-50278, CVE-2024-50125, CVE-2024-47706, CVE-2024-50204,\nCVE-2024-56543, CVE-2024-53108, CVE-2024-49885, CVE-2024-50128,\nCVE-2024-50062, CVE-2024-50139, CVE-2024-50183, CVE-2024-50288,\nCVE-2024-56729, CVE-2024-49945, CVE-2024-47695, CVE-2024-56533,\nCVE-2024-53234, CVE-2024-50002, CVE-2024-50040, CVE-2024-49903,\nCVE-2024-47702, CVE-2024-47728, CVE-2024-49874, CVE-2024-47718,\nCVE-2024-53142, CVE-2024-49983, CVE-2024-50211, CVE-2024-50294,\nCVE-2024-50132, CVE-2024-53236, CVE-2024-50042, CVE-2024-49999,\nCVE-2024-50001, CVE-2024-50046, CVE-2024-50133, CVE-2024-50256,\nCVE-2024-49869, CVE-2024-49852, CVE-2024-47717, CVE-2024-56704,\nCVE-2024-50102, CVE-2024-50150, CVE-2024-49880, CVE-2024-50235,\nCVE-2024-49892, CVE-2024-53194, CVE-2024-53104, CVE-2024-50232,\nCVE-2024-50226, CVE-2024-56684, CVE-2024-47713, CVE-2024-50191,\nCVE-2024-49850, CVE-2024-50277, CVE-2024-53113, CVE-2024-50013,\nCVE-2024-53221, CVE-2024-50220, CVE-2024-49960, CVE-2024-53228,\nCVE-2024-50152, CVE-2024-56689, CVE-2024-53220, CVE-2024-50209,\nCVE-2024-50285, CVE-2024-50197, CVE-2024-53072, CVE-2024-50273,\nCVE-2024-49928, CVE-2024-53132, CVE-2024-56720, CVE-2024-50194,\nCVE-2024-50112, CVE-2024-53079, CVE-2024-56696, CVE-2024-47750,\nCVE-2024-53212, CVE-2024-56541, CVE-2024-50024, CVE-2024-53168,\nCVE-2024-50247, CVE-2024-50193, CVE-2024-47754, CVE-2024-56540,\nCVE-2024-50026, CVE-2024-53047, CVE-2024-53151, CVE-2024-50176,\nCVE-2024-49975, CVE-2024-50034, CVE-2024-50126, CVE-2024-49863,\nCVE-2024-47693, CVE-2024-49954, CVE-2024-49938, CVE-2024-50171,\nCVE-2024-50185, CVE-2024-50200, CVE-2024-50201, CVE-2024-53184,\nCVE-2024-47709, CVE-2024-50138, CVE-2024-49935, CVE-2024-50049,\nCVE-2024-56537, CVE-2024-50057, CVE-2024-56677, CVE-2024-47743,\nCVE-2024-50293, CVE-2024-50099, CVE-2024-47720, CVE-2024-50021,\nCVE-2024-50059, CVE-2024-49871, CVE-2024-49884, CVE-2024-47694,\nCVE-2024-56723, CVE-2024-47724, CVE-2024-50038, CVE-2024-53123,\nCVE-2024-53177, CVE-2024-49932, CVE-2024-50196, CVE-2024-50234,\nCVE-2024-50078, CVE-2024-53043, CVE-2024-49926, CVE-2024-49988,\nCVE-2024-53187, CVE-2024-53056, CVE-2024-53217, CVE-2024-56745,\nCVE-2024-47726, CVE-2024-50063, CVE-2024-49987, CVE-2024-49955,\nCVE-2024-50179, CVE-2024-49866, CVE-2024-50283, CVE-2024-49997,\nCVE-2024-47742, CVE-2024-56691, CVE-2024-50253, CVE-2024-56690,\nCVE-2024-47710, CVE-2024-53129, CVE-2024-50190, CVE-2024-50090,\nCVE-2024-56702, CVE-2024-50148, CVE-2024-53183, CVE-2024-50070,\nCVE-2024-50154, CVE-2024-50243, CVE-2024-50003, CVE-2024-50117,\nCVE-2024-56751, CVE-2024-56697, CVE-2024-53166, CVE-2024-53196,\nCVE-2024-47677, CVE-2024-56679, CVE-2024-49996, CVE-2024-47681,\nCVE-2024-53181, CVE-2024-47700, CVE-2024-53071, CVE-2024-50015,\nCVE-2024-53126, CVE-2024-50165, CVE-2024-50172, CVE-2024-53063,\nCVE-2024-53200, CVE-2024-53135, CVE-2024-49974, CVE-2024-53088,\nCVE-2024-49936, CVE-2024-53121, CVE-2024-50166, CVE-2024-50087,\nCVE-2024-53065, CVE-2024-53214, CVE-2024-53076, CVE-2024-53059,\nCVE-2024-50230, CVE-2024-49985, CVE-2024-50092, CVE-2024-53233,\nCVE-2024-50047, CVE-2024-56685, CVE-2024-47682, CVE-2024-47705,\nCVE-2024-50077, CVE-2024-53224, CVE-2024-49887, CVE-2024-49940,\nCVE-2024-47741, CVE-2024-49858, CVE-2024-56536, CVE-2024-53055,\nCVE-2024-56687, CVE-2024-50100, CVE-2024-53075, CVE-2024-47699,\nCVE-2024-53213, CVE-2024-49977, CVE-2024-50268, CVE-2024-53146,\nCVE-2024-50304, CVE-2024-50096, CVE-2024-53162, CVE-2024-56725,\nCVE-2024-49953, CVE-2024-53077, CVE-2024-50107, CVE-2024-53226,\nCVE-2024-53134, CVE-2024-49873, CVE-2024-56548, CVE-2024-53145,\nCVE-2024-53141, CVE-2024-56741, CVE-2024-53067, CVE-2024-53152,\nCVE-2024-50072, CVE-2024-50282, CVE-2024-53232, CVE-2024-50140,\nCVE-2024-53198, CVE-2024-53150, CVE-2024-49876, CVE-2024-50302,\nCVE-2024-53115, CVE-2024-47692, CVE-2024-50301, CVE-2024-50202,\nCVE-2024-50155, CVE-2024-56693, CVE-2024-53082, CVE-2024-53167,\nCVE-2024-56748, CVE-2024-53064, CVE-2024-50227, CVE-2024-56539,\nCVE-2024-50215, CVE-2024-50043, CVE-2024-50146, CVE-2024-50147,\nCVE-2024-56699, CVE-2024-50122, CVE-2024-53044, CVE-2024-47712,\nCVE-2024-53230, CVE-2024-50121, CVE-2024-50216, CVE-2024-53084,\nCVE-2024-56703, CVE-2024-50178, CVE-2024-49934, CVE-2024-47678,\nCVE-2024-50271, CVE-2024-50144, CVE-2024-50252, CVE-2024-47734,\nCVE-2024-47711, CVE-2024-50214, CVE-2024-53100, CVE-2024-56680,\nCVE-2024-50198, CVE-2024-50025, CVE-2024-50044, CVE-2024-50098,\nCVE-2024-47745, CVE-2024-49860, CVE-2024-49881, CVE-2024-53048,\nCVE-2024-56721, CVE-2024-56756, CVE-2024-53171, CVE-2024-49901,\nCVE-2024-53109, CVE-2024-53061, CVE-2024-49929, CVE-2024-47691,\nCVE-2024-50045, CVE-2024-47723, CVE-2024-56546, CVE-2024-50157,\nCVE-2024-53169, CVE-2024-47716, CVE-2024-53093, CVE-2024-50224,\nCVE-2024-53193, CVE-2024-49895, CVE-2024-47698, CVE-2024-49942,\nCVE-2024-50167, CVE-2024-53202, CVE-2024-49870, CVE-2024-50291,\nCVE-2024-50156, CVE-2024-53153, CVE-2024-50272, CVE-2024-50145,\nCVE-2024-50298, CVE-2024-50274, CVE-2024-56694, CVE-2024-50108,\nCVE-2024-50222, CVE-2024-53163, CVE-2024-50164, CVE-2024-53062,\nCVE-2024-50212, CVE-2024-53127, CVE-2024-47688, CVE-2024-49959,\nCVE-2024-50203, CVE-2024-49927, CVE-2024-50083, CVE-2024-53227,\nCVE-2024-47697, CVE-2024-53053, CVE-2024-53172, CVE-2024-56752,\nCVE-2024-50207, CVE-2024-50169, CVE-2024-53176, CVE-2024-53089,\nCVE-2024-56707, CVE-2024-53195, CVE-2024-49851, CVE-2024-53209,\nCVE-2024-49972, CVE-2024-53130, CVE-2024-53157, CVE-2024-53094,\nCVE-2024-50182, CVE-2024-49879, CVE-2024-53191, CVE-2024-49925,\nCVE-2024-49949, CVE-2024-56534, CVE-2024-47714, CVE-2024-53161,\nCVE-2024-49992, CVE-2024-47732, CVE-2024-53143, CVE-2024-53119,\nCVE-2024-50064, CVE-2024-50039, CVE-2024-53087, CVE-2024-49886,\nCVE-2024-49979, CVE-2024-50041, CVE-2024-50184, CVE-2024-49958,\nCVE-2024-50221, CVE-2024-56688, CVE-2024-49941, CVE-2024-50245,\nCVE-2024-50017, CVE-2024-53180, CVE-2024-56535, CVE-2024-50142,\nCVE-2024-50295, CVE-2024-56708, CVE-2024-50016, CVE-2024-49902,\nCVE-2024-50120, CVE-2024-47748, CVE-2024-49982, CVE-2024-50257,\nCVE-2024-50086, CVE-2024-50261, CVE-2024-53188, CVE-2024-49888,\nCVE-2024-53106, CVE-2024-50073, CVE-2024-50186, CVE-2024-56544,\nCVE-2024-47739, CVE-2024-50238, CVE-2024-56739, CVE-2024-49964,\nCVE-2024-47686, CVE-2024-46869, CVE-2024-53116, CVE-2024-50014,\nCVE-2024-53231, CVE-2024-53138, CVE-2024-50213, CVE-2024-50265,\nCVE-2024-49998, CVE-2024-50292, CVE-2024-50137, CVE-2024-50114,\nCVE-2024-53237, CVE-2024-49952, CVE-2024-53074, CVE-2024-49981,\nCVE-2024-47733, CVE-2024-50019, CVE-2024-47719, CVE-2024-53068,\nCVE-2024-49944, CVE-2024-50066, CVE-2024-50007, CVE-2024-53155,\nCVE-2024-47756, CVE-2024-49947, CVE-2024-49951, CVE-2024-50065,\nCVE-2024-49957, CVE-2024-50116, CVE-2024-50188, CVE-2024-50255,\nCVE-2024-53197, CVE-2024-50267, CVE-2024-50124, CVE-2024-53069,\nCVE-2024-53139, CVE-2024-47676, CVE-2024-56545, CVE-2024-53085,\nCVE-2024-50163, CVE-2024-53092, CVE-2024-53099, CVE-2024-49889,\nCVE-2024-53052, CVE-2024-49995, CVE-2024-49976, CVE-2024-50110,\nCVE-2024-50192, CVE-2024-50208, CVE-2024-50276, CVE-2024-53170,\nCVE-2024-50259, CVE-2024-47731, CVE-2024-49924, CVE-2024-56532,\nCVE-2024-50048, CVE-2024-49965, CVE-2024-53147, CVE-2024-50205,\nCVE-2024-49859, CVE-2024-53066, CVE-2024-47687, CVE-2024-50149,\nCVE-2024-49864, CVE-2024-49867, CVE-2024-50160, CVE-2024-53058,\nCVE-2024-47753, CVE-2024-49883, CVE-2024-53199, CVE-2024-56746,\nCVE-2024-50094, CVE-2024-49946, CVE-2024-50006, CVE-2024-53101,\nCVE-2024-49891, CVE-2024-50075, CVE-2024-47747, CVE-2024-47740,\nCVE-2024-50248, CVE-2024-50162, CVE-2024-53090, CVE-2024-53203,\nCVE-2024-50242, CVE-2024-49961, CVE-2024-50085, CVE-2024-50299,\nCVE-2024-49980, CVE-2024-50280, CVE-2024-53107, CVE-2024-50199,\nCVE-2024-53122, CVE-2024-56674, CVE-2024-50079, CVE-2024-50060,\nCVE-2024-53210, CVE-2024-50177, CVE-2024-53223, CVE-2024-50127,\nCVE-2024-53190, CVE-2022-49034, CVE-2024-56744, CVE-2024-50136,\nCVE-2024-47675, CVE-2024-50303, CVE-2024-50123, CVE-2024-47738,\nCVE-2024-50239, CVE-2024-50135, CVE-2024-53218, CVE-2024-50109,\nCVE-2024-56724, CVE-2024-56681, CVE-2024-50027, CVE-2024-50081,\nCVE-2024-50068, CVE-2024-50101, CVE-2024-50071, CVE-2024-50129,\nCVE-2024-50091, CVE-2024-53112, CVE-2024-50181, CVE-2024-50080,\nCVE-2024-47703, CVE-2024-47727, CVE-2024-53215, CVE-2024-53105,\nCVE-2024-50174, CVE-2024-50105, CVE-2024-56700, CVE-2024-53173,\nCVE-2024-49865, CVE-2024-49973, CVE-2024-56538, CVE-2024-50251,\nCVE-2024-56692, CVE-2024-47671, CVE-2024-50189, CVE-2024-49853,\nCVE-2024-50153, CVE-2024-53124, CVE-2024-56549, CVE-2024-53160,\nCVE-2024-53174, CVE-2024-53117, CVE-2024-50279, CVE-2024-50118,\nCVE-2024-47757, CVE-2024-50055, CVE-2024-49875, CVE-2024-50141,\nCVE-2024-49890, CVE-2024-49878, CVE-2024-50134, CVE-2024-53042,\nCVE-2024-56727, CVE-2024-49861, CVE-2024-49948, CVE-2024-50010,\nCVE-2024-49930, CVE-2024-49877, CVE-2024-47690, CVE-2024-50115,\nCVE-2024-50254, CVE-2024-50250, CVE-2024-47679, CVE-2024-50258,\nCVE-2024-53128, CVE-2024-49994, CVE-2024-53154, CVE-2024-50037,\nCVE-2024-53149, CVE-2024-50266, CVE-2024-50061, CVE-2024-56698,\nCVE-2024-53118, CVE-2024-47689, CVE-2024-47708, CVE-2024-50131,\nCVE-2024-50168, CVE-2024-53158, CVE-2024-49894, CVE-2024-50056,\nCVE-2024-50231, CVE-2024-50270, CVE-2024-50269, CVE-2024-50237,\nCVE-2024-56742, CVE-2024-49882, CVE-2024-47749, CVE-2024-49962,\nCVE-2024-49933, CVE-2024-53045, CVE-2024-50028, CVE-2024-53178,\nCVE-2024-50229, CVE-2024-50023, CVE-2024-50161, CVE-2024-56701,\nCVE-2024-49978, CVE-2024-50093, CVE-2024-50195, CVE-2024-49986,\nCVE-2024-53098, CVE-2024-53131, CVE-2024-47684, CVE-2024-53148,\nCVE-2024-50058, CVE-2024-53086, CVE-2024-50113, CVE-2024-49989,\nCVE-2024-50106, CVE-2024-53080, CVE-2024-53229, CVE-2024-50159,\nCVE-2024-56531, CVE-2024-53110, CVE-2024-47736, CVE-2024-56542,\nCVE-2024-47746)\n","status":"published","published":"2025-02-28T11:33:16Z","modified":"2026-11-03T21:17:33.180491814Z","updated_at":"2026-11-03T21:43:54.166508Z"},{"id":"USN-7311-1","title":"linux-aws, linux-aws-6.8 vulnerabilities","description":"Several security issues were discovered in the Linux kernel.\nAn attacker could possibly use these to compromise the system.\nThis update corrects flaws in the following subsystems:\n  - ARM32 architecture;\n  - x86 architecture;\n  - Block layer subsystem;\n  - Cryptographic API;\n  - ACPI drivers;\n  - Drivers core;\n  - ATA over ethernet (AOE) driver;\n  - Network block device driver;\n  - TPM device driver;\n  - Hardware crypto device drivers;\n  - ARM SCMI message protocol;\n  - EFI core;\n  - GPU drivers;\n  - I2C subsystem;\n  - I3C subsystem;\n  - InfiniBand drivers;\n  - Input Device core drivers;\n  - IOMMU subsystem;\n  - Mailbox framework;\n  - Media drivers;\n  - Ethernet bonding driver;\n  - Network drivers;\n  - Mellanox network drivers;\n  - STMicroelectronics network drivers;\n  - NTB driver;\n  - PCI subsystem;\n  - Alibaba DDR Sub-System Driveway PMU driver;\n  - x86 platform drivers;\n  - Powercap sysfs driver;\n  - Remote Processor subsystem;\n  - SCSI subsystem;\n  - USB Device Class drivers;\n  - vDPA drivers;\n  - Virtio Host (VHOST) subsystem;\n  - Framebuffer layer;\n  - AFS file system;\n  - BTRFS file system;\n  - File systems infrastructure;\n  - Ceph distributed file system;\n  - Ext4 file system;\n  - F2FS file system;\n  - JFS file system;\n  - Network file systems library;\n  - Network file system (NFS) server daemon;\n  - NILFS2 file system;\n  - SMB network file system;\n  - BPF subsystem;\n  - Virtio network driver;\n  - TCP network protocol;\n  - Perf events;\n  - Padata parallel execution mechanism;\n  - RCU subsystem;\n  - Arbitrary resource management;\n  - Static call mechanism;\n  - Tracing infrastructure;\n  - Memory management;\n  - Bluetooth subsystem;\n  - CAN network layer;\n  - Networking core;\n  - Distributed Switch Architecture;\n  - IPv4 networking;\n  - IPv6 networking;\n  - MAC80211 subsystem;\n  - IEEE 802.15.4 subsystem;\n  - NCSI (Network Controller Sideband Interface) driver;\n  - Netfilter;\n  - RxRPC session sockets;\n  - Network traffic control;\n  - SCTP protocol;\n  - TIPC protocol;\n  - VMware vSockets driver;\n  - Wireless networking;\n  - AudioScience HPI driver;\n  - KVM core;\n(CVE-2024-49867, CVE-2024-47675, CVE-2024-49999, CVE-2024-49884,\nCVE-2024-49992, CVE-2024-49945, CVE-2024-49889, CVE-2024-49890,\nCVE-2024-49900, CVE-2024-49934, CVE-2024-49976, CVE-2024-49878,\nCVE-2024-50008, CVE-2024-49919, CVE-2024-47698, CVE-2024-47731,\nCVE-2024-47673, CVE-2024-49959, CVE-2024-47715, CVE-2024-49912,\nCVE-2024-47702, CVE-2024-50007, CVE-2024-49953, CVE-2024-49929,\nCVE-2024-47730, CVE-2024-49966, CVE-2024-47756, CVE-2024-47687,\nCVE-2024-50002, CVE-2024-49911, CVE-2024-47714, CVE-2024-47704,\nCVE-2024-50017, CVE-2024-47709, CVE-2024-49858, CVE-2024-47712,\nCVE-2024-49870, CVE-2024-49883, CVE-2024-47672, CVE-2024-49963,\nCVE-2024-49926, CVE-2024-49860, CVE-2024-47748, CVE-2024-49928,\nCVE-2024-49931, CVE-2024-47749, CVE-2024-49913, CVE-2024-49957,\nCVE-2024-49948, CVE-2024-47732, CVE-2024-47753, CVE-2024-47727,\nCVE-2024-49896, CVE-2024-47707, CVE-2024-47743, CVE-2024-49915,\nCVE-2024-47695, CVE-2024-49960, CVE-2024-49935, CVE-2024-49868,\nCVE-2024-49918, CVE-2024-49969, CVE-2024-53164, CVE-2024-49879,\nCVE-2024-50012, CVE-2024-50000, CVE-2024-49974, CVE-2024-49998,\nCVE-2024-49933, CVE-2024-47733, CVE-2024-49924, CVE-2024-47757,\nCVE-2024-47699, CVE-2024-49983, CVE-2024-50016, CVE-2024-49907,\nCVE-2024-49965, CVE-2024-49859, CVE-2024-50013, CVE-2024-49871,\nCVE-2024-49994, CVE-2024-49850, CVE-2024-49947, CVE-2024-49955,\nCVE-2024-49962, CVE-2024-47692, CVE-2024-53141, CVE-2024-50014,\nCVE-2024-47689, CVE-2024-49874, CVE-2024-50005, CVE-2024-47741,\nCVE-2024-49880, CVE-2024-47738, CVE-2024-47745, CVE-2024-49917,\nCVE-2024-47728, CVE-2024-49856, CVE-2024-49925, CVE-2024-47671,\nCVE-2023-52917, CVE-2024-47679, CVE-2024-49975, CVE-2024-47734,\nCVE-2024-47720, CVE-2024-47686, CVE-2024-49892, CVE-2024-49936,\nCVE-2024-49888, CVE-2024-49909, CVE-2024-49986, CVE-2024-49930,\nCVE-2024-47740, CVE-2024-49923, CVE-2024-47754, CVE-2024-50179,\nCVE-2024-49978, CVE-2024-47735, CVE-2024-49886, CVE-2024-49903,\nCVE-2024-47681, CVE-2024-49897, CVE-2024-49951, CVE-2024-49946,\nCVE-2024-49954, CVE-2024-47691, CVE-2024-49863, CVE-2024-47719,\nCVE-2024-47693, CVE-2024-47713, CVE-2024-50006, CVE-2024-49855,\nCVE-2024-49851, CVE-2024-49894, CVE-2024-49895, CVE-2024-49987,\nCVE-2024-47700, CVE-2024-47688, CVE-2024-49982, CVE-2024-47685,\nCVE-2024-53144, CVE-2024-47670, CVE-2024-47696, CVE-2024-47710,\nCVE-2024-47737, CVE-2024-49988, CVE-2024-47684, CVE-2024-47718,\nCVE-2024-49876, CVE-2024-49852, CVE-2024-49980, CVE-2024-49877,\nCVE-2024-50175, CVE-2024-49981, CVE-2024-47677, CVE-2024-49973,\nCVE-2024-49922, CVE-2024-50015, CVE-2024-49938, CVE-2024-47752,\nCVE-2024-49902, CVE-2024-49944, CVE-2024-49952, CVE-2024-47747,\nCVE-2024-41016, CVE-2024-50001, CVE-2024-49891, CVE-2024-47703,\nCVE-2024-47744, CVE-2024-49861, CVE-2024-49875, CVE-2024-49901,\nCVE-2024-49881, CVE-2024-49937, CVE-2024-47706, CVE-2024-47690,\nCVE-2024-49958, CVE-2024-49961, CVE-2024-49882, CVE-2024-47739,\nCVE-2024-49996, CVE-2024-49905, CVE-2024-47705, CVE-2024-49942,\nCVE-2024-47697, CVE-2024-47723, CVE-2024-49853, CVE-2024-49862,\nCVE-2024-47751, CVE-2024-49950, CVE-2024-50176, CVE-2024-49939,\nCVE-2024-49864, CVE-2024-49997, CVE-2024-49995, CVE-2024-49885,\nCVE-2024-49949, CVE-2024-53103, CVE-2024-49991, CVE-2024-49866,\nCVE-2024-49977, CVE-2024-47682, CVE-2024-49927, CVE-2024-49985,\nCVE-2024-49898, CVE-2024-47678, CVE-2024-47701, CVE-2024-47742,\nCVE-2024-47750, CVE-2024-47716, CVE-2024-49989)\n","status":"published","published":"2025-02-28T12:11:55Z","modified":"2026-10-29T20:02:41.746464374Z","updated_at":"2026-11-02T16:58:18.876384Z"},{"id":"USN-7384-1","title":"linux-azure vulnerabilities","description":"Michael Randrianantenaina discovered that the Bluetooth driver in the Linux\nKernel contained an improper access control vulnerability. A nearby\nattacker could use this to connect a rougue device and possibly execute\narbitrary code. (CVE-2024-8805)\n\nAttila Szász discovered that the HFS+ file system implementation in the\nLinux Kernel contained a heap overflow vulnerability. An attacker could use\na specially crafted file system image that, when mounted, could cause a\ndenial of service (system crash) or possibly execute arbitrary code.\n(CVE-2025-0927)\n\nIt was discovered that the CIFS network file system implementation in the\nLinux kernel did not properly verify the target namespace when handling\nupcalls. An attacker could use this to expose sensitive information.\n(CVE-2025-2312)\n\nSeveral security issues were discovered in the Linux kernel.\nAn attacker could possibly use these to compromise the system.\nThis update corrects flaws in the following subsystems:\n  - ARM32 architecture;\n  - ARM64 architecture;\n  - x86 architecture;\n  - Block layer subsystem;\n  - Cryptographic API;\n  - ACPI drivers;\n  - Drivers core;\n  - ATA over ethernet (AOE) driver;\n  - Network block device driver;\n  - Ublk userspace block driver;\n  - Compressed RAM block device driver;\n  - TPM device driver;\n  - CPU frequency scaling framework;\n  - Hardware crypto device drivers;\n  - DAX dirext access to differentiated memory framework;\n  - ARM SCMI message protocol;\n  - EFI core;\n  - GPU drivers;\n  - HID subsystem;\n  - I2C subsystem;\n  - I3C subsystem;\n  - IIO subsystem;\n  - InfiniBand drivers;\n  - Input Device core drivers;\n  - IOMMU subsystem;\n  - IRQ chip drivers;\n  - Mailbox framework;\n  - Media drivers;\n  - Ethernet bonding driver;\n  - Network drivers;\n  - Mellanox network drivers;\n  - STMicroelectronics network drivers;\n  - NTB driver;\n  - Virtio pmem driver;\n  - Parport drivers;\n  - PCI subsystem;\n  - Alibaba DDR Sub-System Driveway PMU driver;\n  - Pin controllers subsystem;\n  - x86 platform drivers;\n  - Powercap sysfs driver;\n  - Remote Processor subsystem;\n  - SCSI subsystem;\n  - SuperH / SH-Mobile drivers;\n  - Direct Digital Synthesis drivers;\n  - Thermal drivers;\n  - TTY drivers;\n  - UFS subsystem;\n  - USB Device Class drivers;\n  - USB Gadget drivers;\n  - USB Host Controller drivers;\n  - TI TPS6598x USB Power Delivery controller driver;\n  - vDPA drivers;\n  - Virtio Host (VHOST) subsystem;\n  - Framebuffer layer;\n  - AFS file system;\n  - BTRFS file system;\n  - File systems infrastructure;\n  - Ceph distributed file system;\n  - Ext4 file system;\n  - F2FS 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  - SMB network file system;\n  - BPF subsystem;\n  - Network file system (NFS) superblock;\n  - Virtio network driver;\n  - Network traffic control;\n  - Network sockets;\n  - TCP network protocol;\n  - User-space API (UAPI);\n  - io_uring subsystem;\n  - Perf events;\n  - Kernel thread helper (kthread);\n  - Padata parallel execution mechanism;\n  - RCU subsystem;\n  - Arbitrary resource management;\n  - Static call mechanism;\n  - Timer subsystem;\n  - Tracing infrastructure;\n  - Maple Tree data structure library;\n  - Memory management;\n  - Bluetooth subsystem;\n  - Ethernet bridge;\n  - CAN network layer;\n  - Networking core;\n  - Distributed Switch Architecture;\n  - IPv4 networking;\n  - IPv6 networking;\n  - MAC80211 subsystem;\n  - IEEE 802.15.4 subsystem;\n  - Multipath TCP;\n  - NCSI (Network Controller Sideband Interface) driver;\n  - Netfilter;\n  - Netlink;\n  - RxRPC session sockets;\n  - SCTP protocol;\n  - TIPC protocol;\n  - Unix domain sockets;\n  - Wireless networking;\n  - eXpress Data Path;\n  - AudioScience HPI driver;\n  - KVM core;\n(CVE-2024-49994, CVE-2024-47740, CVE-2024-49936, CVE-2024-47716,\nCVE-2024-47733, CVE-2024-50075, CVE-2024-49870, CVE-2024-50007,\nCVE-2024-49897, CVE-2024-49915, CVE-2024-47756, CVE-2024-47700,\nCVE-2024-49946, CVE-2024-50012, CVE-2024-47750, CVE-2024-49863,\nCVE-2024-50059, CVE-2024-50026, CVE-2024-49995, CVE-2024-50035,\nCVE-2024-47751, CVE-2024-50096, CVE-2024-50082, CVE-2024-50090,\nCVE-2024-50000, CVE-2024-47690, CVE-2024-47741, CVE-2024-49898,\nCVE-2024-47685, CVE-2024-50038, CVE-2024-49957, CVE-2024-47682,\nCVE-2024-50002, CVE-2024-47709, CVE-2024-50201, CVE-2024-49927,\nCVE-2024-50076, CVE-2024-56582, CVE-2024-47742, CVE-2024-47734,\nCVE-2024-50040, CVE-2024-49862, CVE-2024-49942, CVE-2024-50193,\nCVE-2024-49880, CVE-2024-50008, CVE-2024-49949, CVE-2024-50056,\nCVE-2024-50099, CVE-2024-50180, CVE-2024-50045, CVE-2024-49923,\nCVE-2024-49987, CVE-2024-49884, CVE-2024-50031, CVE-2024-47705,\nCVE-2024-47728, CVE-2024-49969, CVE-2024-50077, CVE-2024-50188,\nCVE-2024-49852, CVE-2024-49890, CVE-2024-47745, CVE-2024-50058,\nCVE-2024-50186, CVE-2024-47749, CVE-2024-56614, CVE-2024-50021,\nCVE-2024-50055, CVE-2024-47727, CVE-2024-47677, CVE-2024-49922,\nCVE-2024-50015, CVE-2024-50084, CVE-2024-47689, CVE-2024-50101,\nCVE-2024-47699, CVE-2024-49947, CVE-2024-49999, CVE-2024-49868,\nCVE-2024-50184, CVE-2024-50187, CVE-2024-47757, CVE-2024-49900,\nCVE-2024-47703, CVE-2024-49975, CVE-2024-47692, CVE-2024-49980,\nCVE-2024-49951, CVE-2024-49930, CVE-2024-49867, CVE-2024-49860,\nCVE-2024-50009, CVE-2024-50072, CVE-2024-50229, CVE-2024-49954,\nCVE-2024-50183, CVE-2024-49858, CVE-2024-49909, CVE-2024-49926,\nCVE-2024-47754, CVE-2024-50027, CVE-2024-50200, CVE-2024-50196,\nCVE-2024-50086, CVE-2024-47739, CVE-2024-49978, CVE-2024-49983,\nCVE-2024-49894, CVE-2024-49973, CVE-2024-49888, CVE-2024-49974,\nCVE-2024-47672, CVE-2024-49977, CVE-2024-47738, CVE-2024-49893,\nCVE-2024-49876, CVE-2024-49960, CVE-2024-49955, CVE-2024-47670,\nCVE-2024-47706, CVE-2024-49931, CVE-2024-47686, CVE-2024-49855,\nCVE-2024-49901, CVE-2024-47752, CVE-2024-47675, CVE-2024-47704,\nCVE-2024-47735, CVE-2024-47744, CVE-2024-50088, CVE-2024-50070,\nCVE-2024-47707, CVE-2024-50176, CVE-2024-50080, CVE-2024-50175,\nCVE-2024-47731, CVE-2024-49853, CVE-2024-49929, CVE-2024-49989,\nCVE-2024-49921, CVE-2024-49965, CVE-2024-49891, CVE-2024-50005,\nCVE-2024-47715, CVE-2024-50085, CVE-2024-50189, CVE-2024-47723,\nCVE-2024-50020, CVE-2024-49902, CVE-2024-47730, CVE-2024-53156,\nCVE-2024-49895, CVE-2024-49997, CVE-2024-50192, CVE-2024-49850,\nCVE-2024-50062, CVE-2024-50033, CVE-2024-49972, CVE-2024-49945,\nCVE-2024-50036, CVE-2024-50202, CVE-2024-50095, CVE-2024-49913,\nCVE-2024-50049, CVE-2024-50148, CVE-2024-49948, CVE-2024-49866,\nCVE-2024-49963, CVE-2024-49907, CVE-2024-50117, CVE-2024-49885,\nCVE-2024-49874, CVE-2024-50198, CVE-2024-49856, CVE-2024-49986,\nCVE-2024-49871, CVE-2024-50028, CVE-2024-49889, CVE-2024-50024,\nCVE-2024-47687, CVE-2024-50065, CVE-2024-49953, CVE-2024-47748,\nCVE-2024-47747, CVE-2024-47673, CVE-2024-49928, CVE-2024-50191,\nCVE-2024-50016, CVE-2024-53170, CVE-2024-49933, CVE-2024-50029,\nCVE-2024-50098, CVE-2024-49988, CVE-2024-49985, CVE-2024-50042,\nCVE-2024-50171, CVE-2024-50233, CVE-2024-49976, CVE-2024-49996,\nCVE-2024-49950, CVE-2024-49968, CVE-2024-50083, CVE-2024-49966,\nCVE-2024-49851, CVE-2024-50066, CVE-2024-49864, CVE-2024-50048,\nCVE-2024-50069, CVE-2024-50001, CVE-2024-50194, CVE-2024-47693,\nCVE-2024-49905, CVE-2024-50134, CVE-2024-49944, CVE-2024-50060,\nCVE-2024-49892, CVE-2024-49982, CVE-2024-49883, CVE-2024-49875,\nCVE-2024-47691, CVE-2024-47714, CVE-2024-47712, CVE-2024-50025,\nCVE-2024-50023, CVE-2024-47726, CVE-2024-50041, CVE-2024-49896,\nCVE-2024-50195, CVE-2024-47679, CVE-2024-47678, CVE-2024-49877,\nCVE-2024-47684, CVE-2024-47719, CVE-2024-49937, CVE-2024-53144,\nCVE-2024-47737, CVE-2024-49998, CVE-2024-49879, CVE-2024-50019,\nCVE-2024-50093, CVE-2024-50073, CVE-2024-50064, CVE-2024-50006,\nCVE-2024-47695, CVE-2024-49882, CVE-2024-50179, CVE-2024-49865,\nCVE-2024-47702, CVE-2024-50046, CVE-2024-49919, CVE-2024-47697,\nCVE-2024-50017, CVE-2024-50014, CVE-2024-49861, CVE-2024-50197,\nCVE-2024-49886, CVE-2024-49938, CVE-2024-49991, CVE-2024-49981,\nCVE-2024-56663, CVE-2024-49914, CVE-2024-49920, CVE-2024-47671,\nCVE-2024-49961, CVE-2024-47698, CVE-2024-49952, CVE-2024-47688,\nCVE-2024-50078, CVE-2024-50199, CVE-2024-49918, CVE-2024-50044,\nCVE-2024-50013, CVE-2024-47711, CVE-2024-49917, CVE-2024-50057,\nCVE-2024-47718, CVE-2024-49911, CVE-2024-49912, CVE-2024-53165,\nCVE-2024-50068, CVE-2024-50087, CVE-2024-47720, CVE-2024-49958,\nCVE-2024-49934, CVE-2024-49859, CVE-2024-47710, CVE-2024-49903,\nCVE-2024-49925, CVE-2024-50061, CVE-2024-41016, CVE-2024-47696,\nCVE-2024-47701, CVE-2024-49939, CVE-2024-49924, CVE-2024-49935,\nCVE-2024-50030, CVE-2024-50074, CVE-2024-47681, CVE-2024-47743,\nCVE-2024-49992, CVE-2024-49881, CVE-2024-50063, CVE-2024-47713,\nCVE-2024-50039, CVE-2024-50185, CVE-2024-49962, CVE-2024-50182,\nCVE-2024-50022, CVE-2024-49959, CVE-2024-50047, CVE-2024-53104,\nCVE-2024-49878, CVE-2024-47732, CVE-2024-47753)\n","status":"published","published":"2025-03-27T19:11:01Z","modified":"2026-10-30T21:53:49.100009046Z","updated_at":"2026-11-02T16:58:19.988474Z"},{"id":"USN-7384-2","title":"linux-azure-6.8 vulnerabilities","description":"Michael Randrianantenaina discovered that the Bluetooth driver in the Linux\nKernel contained an improper access control vulnerability. A nearby\nattacker could use this to connect a rougue device and possibly execute\narbitrary code. (CVE-2024-8805)\n\nAttila Szász discovered that the HFS+ file system implementation in the\nLinux Kernel contained a heap overflow vulnerability. An attacker could use\na specially crafted file system image that, when mounted, could cause a\ndenial of service (system crash) or possibly execute arbitrary code.\n(CVE-2025-0927)\n\nIt was discovered that the CIFS network file system implementation in the\nLinux kernel did not properly verify the target namespace when handling\nupcalls. An attacker could use this to expose sensitive information.\n(CVE-2025-2312)\n\nSeveral security issues were discovered in the Linux kernel.\nAn attacker could possibly use these to compromise the system.\nThis update corrects flaws in the following subsystems:\n  - ARM32 architecture;\n  - ARM64 architecture;\n  - x86 architecture;\n  - Block layer subsystem;\n  - Cryptographic API;\n  - ACPI drivers;\n  - Drivers core;\n  - ATA over ethernet (AOE) driver;\n  - Network block device driver;\n  - Ublk userspace block driver;\n  - Compressed RAM block device driver;\n  - TPM device driver;\n  - CPU frequency scaling framework;\n  - Hardware crypto device drivers;\n  - DAX dirext access to differentiated memory framework;\n  - ARM SCMI message protocol;\n  - EFI core;\n  - GPU drivers;\n  - HID subsystem;\n  - I2C subsystem;\n  - I3C subsystem;\n  - IIO subsystem;\n  - InfiniBand drivers;\n  - Input Device core drivers;\n  - IOMMU subsystem;\n  - IRQ chip drivers;\n  - Mailbox framework;\n  - Media drivers;\n  - Ethernet bonding driver;\n  - Network drivers;\n  - Mellanox network drivers;\n  - STMicroelectronics network drivers;\n  - NTB driver;\n  - Virtio pmem driver;\n  - Parport drivers;\n  - PCI subsystem;\n  - Alibaba DDR Sub-System Driveway PMU driver;\n  - Pin controllers subsystem;\n  - x86 platform drivers;\n  - Powercap sysfs driver;\n  - Remote Processor subsystem;\n  - SCSI subsystem;\n  - SuperH / SH-Mobile drivers;\n  - Direct Digital Synthesis drivers;\n  - Thermal drivers;\n  - TTY drivers;\n  - UFS subsystem;\n  - USB Device Class drivers;\n  - USB Gadget drivers;\n  - USB Host Controller drivers;\n  - TI TPS6598x USB Power Delivery controller driver;\n  - vDPA drivers;\n  - Virtio Host (VHOST) subsystem;\n  - Framebuffer layer;\n  - AFS file system;\n  - BTRFS file system;\n  - File systems infrastructure;\n  - Ceph distributed file system;\n  - Ext4 file system;\n  - F2FS 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  - SMB network file system;\n  - BPF subsystem;\n  - Network file system (NFS) superblock;\n  - Virtio network driver;\n  - Network traffic control;\n  - Network sockets;\n  - TCP network protocol;\n  - User-space API (UAPI);\n  - io_uring subsystem;\n  - Perf events;\n  - Kernel thread helper (kthread);\n  - Padata parallel execution mechanism;\n  - RCU subsystem;\n  - Arbitrary resource management;\n  - Static call mechanism;\n  - Timer subsystem;\n  - Tracing infrastructure;\n  - Maple Tree data structure library;\n  - Memory management;\n  - Bluetooth subsystem;\n  - Ethernet bridge;\n  - CAN network layer;\n  - Networking core;\n  - Distributed Switch Architecture;\n  - IPv4 networking;\n  - IPv6 networking;\n  - MAC80211 subsystem;\n  - IEEE 802.15.4 subsystem;\n  - Multipath TCP;\n  - NCSI (Network Controller Sideband Interface) driver;\n  - Netfilter;\n  - Netlink;\n  - RxRPC session sockets;\n  - SCTP protocol;\n  - TIPC protocol;\n  - Unix domain sockets;\n  - Wireless networking;\n  - eXpress Data Path;\n  - AudioScience HPI driver;\n  - KVM core;\n(CVE-2024-49994, CVE-2024-47740, CVE-2024-49936, CVE-2024-47716,\nCVE-2024-47733, CVE-2024-50075, CVE-2024-49870, CVE-2024-50007,\nCVE-2024-49897, CVE-2024-49915, CVE-2024-47756, CVE-2024-47700,\nCVE-2024-49946, CVE-2024-50012, CVE-2024-47750, CVE-2024-49863,\nCVE-2024-50059, CVE-2024-50026, CVE-2024-49995, CVE-2024-50035,\nCVE-2024-47751, CVE-2024-50096, CVE-2024-50082, CVE-2024-50090,\nCVE-2024-50000, CVE-2024-47690, CVE-2024-47741, CVE-2024-49898,\nCVE-2024-47685, CVE-2024-50038, CVE-2024-49957, CVE-2024-47682,\nCVE-2024-50002, CVE-2024-47709, CVE-2024-50201, CVE-2024-49927,\nCVE-2024-50076, CVE-2024-56582, CVE-2024-47742, CVE-2024-47734,\nCVE-2024-50040, CVE-2024-49862, CVE-2024-49942, CVE-2024-50193,\nCVE-2024-49880, CVE-2024-50008, CVE-2024-49949, CVE-2024-50056,\nCVE-2024-50099, CVE-2024-50180, CVE-2024-50045, CVE-2024-49923,\nCVE-2024-49987, CVE-2024-49884, CVE-2024-50031, CVE-2024-47705,\nCVE-2024-47728, CVE-2024-49969, CVE-2024-50077, CVE-2024-50188,\nCVE-2024-49852, CVE-2024-49890, CVE-2024-47745, CVE-2024-50058,\nCVE-2024-50186, CVE-2024-47749, CVE-2024-56614, CVE-2024-50021,\nCVE-2024-50055, CVE-2024-47727, CVE-2024-47677, CVE-2024-49922,\nCVE-2024-50015, CVE-2024-50084, CVE-2024-47689, CVE-2024-50101,\nCVE-2024-47699, CVE-2024-49947, CVE-2024-49999, CVE-2024-49868,\nCVE-2024-50184, CVE-2024-50187, CVE-2024-47757, CVE-2024-49900,\nCVE-2024-47703, CVE-2024-49975, CVE-2024-47692, CVE-2024-49980,\nCVE-2024-49951, CVE-2024-49930, CVE-2024-49867, CVE-2024-49860,\nCVE-2024-50009, CVE-2024-50072, CVE-2024-50229, CVE-2024-49954,\nCVE-2024-50183, CVE-2024-49858, CVE-2024-49909, CVE-2024-49926,\nCVE-2024-47754, CVE-2024-50027, CVE-2024-50200, CVE-2024-50196,\nCVE-2024-50086, CVE-2024-47739, CVE-2024-49978, CVE-2024-49983,\nCVE-2024-49894, CVE-2024-49973, CVE-2024-49888, CVE-2024-49974,\nCVE-2024-47672, CVE-2024-49977, CVE-2024-47738, CVE-2024-49893,\nCVE-2024-49876, CVE-2024-49960, CVE-2024-49955, CVE-2024-47670,\nCVE-2024-47706, CVE-2024-49931, CVE-2024-47686, CVE-2024-49855,\nCVE-2024-49901, CVE-2024-47752, CVE-2024-47675, CVE-2024-47704,\nCVE-2024-47735, CVE-2024-47744, CVE-2024-50088, CVE-2024-50070,\nCVE-2024-47707, CVE-2024-50176, CVE-2024-50080, CVE-2024-50175,\nCVE-2024-47731, CVE-2024-49853, CVE-2024-49929, CVE-2024-49989,\nCVE-2024-49921, CVE-2024-49965, CVE-2024-49891, CVE-2024-50005,\nCVE-2024-47715, CVE-2024-50085, CVE-2024-50189, CVE-2024-47723,\nCVE-2024-50020, CVE-2024-49902, CVE-2024-47730, CVE-2024-53156,\nCVE-2024-49895, CVE-2024-49997, CVE-2024-50192, CVE-2024-49850,\nCVE-2024-50062, CVE-2024-50033, CVE-2024-49972, CVE-2024-49945,\nCVE-2024-50036, CVE-2024-50202, CVE-2024-50095, CVE-2024-49913,\nCVE-2024-50049, CVE-2024-50148, CVE-2024-49948, CVE-2024-49866,\nCVE-2024-49963, CVE-2024-49907, CVE-2024-50117, CVE-2024-49885,\nCVE-2024-49874, CVE-2024-50198, CVE-2024-49856, CVE-2024-49986,\nCVE-2024-49871, CVE-2024-50028, CVE-2024-49889, CVE-2024-50024,\nCVE-2024-47687, CVE-2024-50065, CVE-2024-49953, CVE-2024-47748,\nCVE-2024-47747, CVE-2024-47673, CVE-2024-49928, CVE-2024-50191,\nCVE-2024-50016, CVE-2024-53170, CVE-2024-49933, CVE-2024-50029,\nCVE-2024-50098, CVE-2024-49988, CVE-2024-49985, CVE-2024-50042,\nCVE-2024-50171, CVE-2024-50233, CVE-2024-49976, CVE-2024-49996,\nCVE-2024-49950, CVE-2024-49968, CVE-2024-50083, CVE-2024-49966,\nCVE-2024-49851, CVE-2024-50066, CVE-2024-49864, CVE-2024-50048,\nCVE-2024-50069, CVE-2024-50001, CVE-2024-50194, CVE-2024-47693,\nCVE-2024-49905, CVE-2024-50134, CVE-2024-49944, CVE-2024-50060,\nCVE-2024-49892, CVE-2024-49982, CVE-2024-49883, CVE-2024-49875,\nCVE-2024-47691, CVE-2024-47714, CVE-2024-47712, CVE-2024-50025,\nCVE-2024-50023, CVE-2024-47726, CVE-2024-50041, CVE-2024-49896,\nCVE-2024-50195, CVE-2024-47679, CVE-2024-47678, CVE-2024-49877,\nCVE-2024-47684, CVE-2024-47719, CVE-2024-49937, CVE-2024-53144,\nCVE-2024-47737, CVE-2024-49998, CVE-2024-49879, CVE-2024-50019,\nCVE-2024-50093, CVE-2024-50073, CVE-2024-50064, CVE-2024-50006,\nCVE-2024-47695, CVE-2024-49882, CVE-2024-50179, CVE-2024-49865,\nCVE-2024-47702, CVE-2024-50046, CVE-2024-49919, CVE-2024-47697,\nCVE-2024-50017, CVE-2024-50014, CVE-2024-49861, CVE-2024-50197,\nCVE-2024-49886, CVE-2024-49938, CVE-2024-49991, CVE-2024-49981,\nCVE-2024-56663, CVE-2024-49914, CVE-2024-49920, CVE-2024-47671,\nCVE-2024-49961, CVE-2024-47698, CVE-2024-49952, CVE-2024-47688,\nCVE-2024-50078, CVE-2024-50199, CVE-2024-49918, CVE-2024-50044,\nCVE-2024-50013, CVE-2024-47711, CVE-2024-49917, CVE-2024-50057,\nCVE-2024-47718, CVE-2024-49911, CVE-2024-49912, CVE-2024-53165,\nCVE-2024-50068, CVE-2024-50087, CVE-2024-47720, CVE-2024-49958,\nCVE-2024-49934, CVE-2024-49859, CVE-2024-47710, CVE-2024-49903,\nCVE-2024-49925, CVE-2024-50061, CVE-2024-41016, CVE-2024-47696,\nCVE-2024-47701, CVE-2024-49939, CVE-2024-49924, CVE-2024-49935,\nCVE-2024-50030, CVE-2024-50074, CVE-2024-47681, CVE-2024-47743,\nCVE-2024-49992, CVE-2024-49881, CVE-2024-50063, CVE-2024-47713,\nCVE-2024-50039, CVE-2024-50185, CVE-2024-49962, CVE-2024-50182,\nCVE-2024-50022, CVE-2024-49959, CVE-2024-50047, CVE-2024-53104,\nCVE-2024-49878, CVE-2024-47732, CVE-2024-47753)\n","status":"published","published":"2025-04-01T16:23:48Z","modified":"2026-10-30T21:53:57.799321819Z","updated_at":"2026-11-02T16:58:19.988474Z"},{"id":"USN-7385-1","title":"linux-ibm vulnerabilities","description":"Michael Randrianantenaina discovered that the Bluetooth driver in the Linux\nKernel contained an improper access control vulnerability. A nearby\nattacker could use this to connect a rougue device and possibly execute\narbitrary code. (CVE-2024-8805)\n\nAttila Szász discovered that the HFS+ file system implementation in the\nLinux Kernel contained a heap overflow vulnerability. An attacker could use\na specially crafted file system image that, when mounted, could cause a\ndenial of service (system crash) or possibly execute arbitrary code.\n(CVE-2025-0927)\n\nSeveral security issues were discovered in the Linux kernel.\nAn attacker could possibly use these to compromise the system.\nThis update corrects flaws in the following subsystems:\n  - ARM32 architecture;\n  - ARM64 architecture;\n  - x86 architecture;\n  - Block layer subsystem;\n  - Cryptographic API;\n  - ACPI drivers;\n  - Drivers core;\n  - ATA over ethernet (AOE) driver;\n  - Network block device driver;\n  - Ublk userspace block driver;\n  - Compressed RAM block device driver;\n  - TPM device driver;\n  - CPU frequency scaling framework;\n  - Hardware crypto device drivers;\n  - DAX dirext access to differentiated memory framework;\n  - ARM SCMI message protocol;\n  - EFI core;\n  - GPU drivers;\n  - HID subsystem;\n  - I2C subsystem;\n  - I3C subsystem;\n  - IIO subsystem;\n  - InfiniBand drivers;\n  - Input Device core drivers;\n  - IOMMU subsystem;\n  - IRQ chip drivers;\n  - Mailbox framework;\n  - Media drivers;\n  - Ethernet bonding driver;\n  - Network drivers;\n  - Mellanox network drivers;\n  - STMicroelectronics network drivers;\n  - NTB driver;\n  - Virtio pmem driver;\n  - Parport drivers;\n  - PCI subsystem;\n  - Alibaba DDR Sub-System Driveway PMU driver;\n  - Pin controllers subsystem;\n  - x86 platform drivers;\n  - Powercap sysfs driver;\n  - Remote Processor subsystem;\n  - SCSI subsystem;\n  - SuperH / SH-Mobile drivers;\n  - Direct Digital Synthesis drivers;\n  - Thermal drivers;\n  - TTY drivers;\n  - UFS subsystem;\n  - USB Device Class drivers;\n  - USB Gadget drivers;\n  - USB Host Controller drivers;\n  - TI TPS6598x USB Power Delivery controller driver;\n  - vDPA drivers;\n  - Virtio Host (VHOST) subsystem;\n  - Framebuffer layer;\n  - AFS file system;\n  - BTRFS file system;\n  - File systems infrastructure;\n  - Ceph distributed file system;\n  - Ext4 file system;\n  - F2FS 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  - SMB network file system;\n  - BPF subsystem;\n  - Network file system (NFS) superblock;\n  - Virtio network driver;\n  - Network traffic control;\n  - Network sockets;\n  - TCP network protocol;\n  - User-space API (UAPI);\n  - io_uring subsystem;\n  - Perf events;\n  - Kernel thread helper (kthread);\n  - Padata parallel execution mechanism;\n  - RCU subsystem;\n  - Arbitrary resource management;\n  - Static call mechanism;\n  - Timer subsystem;\n  - Tracing infrastructure;\n  - Maple Tree data structure library;\n  - Memory management;\n  - Bluetooth subsystem;\n  - Ethernet bridge;\n  - CAN network layer;\n  - Networking core;\n  - Distributed Switch Architecture;\n  - IPv4 networking;\n  - IPv6 networking;\n  - MAC80211 subsystem;\n  - IEEE 802.15.4 subsystem;\n  - Multipath TCP;\n  - NCSI (Network Controller Sideband Interface) driver;\n  - Netfilter;\n  - Netlink;\n  - RxRPC session sockets;\n  - SCTP protocol;\n  - TIPC protocol;\n  - Unix domain sockets;\n  - Wireless networking;\n  - eXpress Data Path;\n  - AudioScience HPI driver;\n  - KVM core;\n(CVE-2024-49927, CVE-2024-47719, CVE-2024-49878, CVE-2024-50200,\nCVE-2024-50013, CVE-2024-50187, CVE-2024-49852, CVE-2024-49913,\nCVE-2024-50080, CVE-2024-49903, CVE-2024-47745, CVE-2024-50184,\nCVE-2024-50117, CVE-2024-49863, CVE-2024-49973, CVE-2024-47727,\nCVE-2024-53170, CVE-2024-49933, CVE-2024-49900, CVE-2024-50095,\nCVE-2024-49928, CVE-2024-49858, CVE-2024-47731, CVE-2024-49896,\nCVE-2024-53104, CVE-2024-49972, CVE-2024-49969, CVE-2024-50176,\nCVE-2024-47739, CVE-2024-49995, CVE-2024-49982, CVE-2024-50044,\nCVE-2024-49957, CVE-2024-47748, CVE-2024-47744, CVE-2024-49978,\nCVE-2024-49879, CVE-2024-49987, CVE-2024-49929, CVE-2024-49905,\nCVE-2024-47723, CVE-2024-53144, CVE-2024-50066, CVE-2024-47735,\nCVE-2024-50057, CVE-2024-49890, CVE-2024-49963, CVE-2024-49955,\nCVE-2024-49974, CVE-2024-50049, CVE-2024-47710, CVE-2024-47682,\nCVE-2024-47734, CVE-2024-47691, CVE-2024-49999, CVE-2024-50098,\nCVE-2024-47672, CVE-2024-50056, CVE-2024-49983, CVE-2024-50005,\nCVE-2024-50045, CVE-2024-49866, CVE-2024-49953, CVE-2024-47750,\nCVE-2024-49917, CVE-2024-50026, CVE-2024-50009, CVE-2024-47718,\nCVE-2024-50070, CVE-2024-47700, CVE-2024-49986, CVE-2024-49907,\nCVE-2024-49884, CVE-2024-50085, CVE-2024-50087, CVE-2024-49875,\nCVE-2024-47728, CVE-2024-49861, CVE-2024-49851, CVE-2024-49980,\nCVE-2024-49898, CVE-2024-47681, CVE-2024-49965, CVE-2024-49960,\nCVE-2024-50020, CVE-2024-50012, CVE-2024-50186, CVE-2024-49889,\nCVE-2024-50030, CVE-2024-50046, CVE-2024-50180, CVE-2024-49966,\nCVE-2024-49897, CVE-2024-49985, CVE-2024-49918, CVE-2024-47754,\nCVE-2024-50082, CVE-2024-47757, CVE-2024-47711, CVE-2024-47737,\nCVE-2024-47716, CVE-2024-50069, CVE-2024-47696, CVE-2024-50031,\nCVE-2024-50202, CVE-2024-47713, CVE-2024-49894, CVE-2024-49921,\nCVE-2024-50022, CVE-2024-49856, CVE-2024-47740, CVE-2024-49868,\nCVE-2024-49919, CVE-2024-47679, CVE-2024-47695, CVE-2024-47714,\nCVE-2024-49996, CVE-2024-50196, CVE-2024-49997, CVE-2024-49883,\nCVE-2024-49936, CVE-2024-49962, CVE-2024-47673, CVE-2024-56663,\nCVE-2024-49892, CVE-2024-47685, CVE-2024-50233, CVE-2024-49891,\nCVE-2024-47738, CVE-2024-49870, CVE-2024-49885, CVE-2024-50025,\nCVE-2024-50006, CVE-2024-49968, CVE-2024-47709, CVE-2024-47751,\nCVE-2024-50058, CVE-2024-50086, CVE-2024-50072, CVE-2024-50195,\nCVE-2024-56582, CVE-2024-50014, CVE-2024-49886, CVE-2024-47743,\nCVE-2024-50185, CVE-2024-50193, CVE-2024-49909, CVE-2024-50077,\nCVE-2024-49930, CVE-2024-49946, CVE-2024-50192, CVE-2024-50041,\nCVE-2024-47698, CVE-2024-50188, CVE-2024-49977, CVE-2024-47687,\nCVE-2024-49945, CVE-2024-50008, CVE-2024-49859, CVE-2024-50062,\nCVE-2024-49880, CVE-2024-47671, CVE-2024-49867, CVE-2024-49912,\nCVE-2024-56614, CVE-2024-49862, CVE-2024-50021, CVE-2024-47670,\nCVE-2024-49911, CVE-2024-49855, CVE-2024-47712, CVE-2024-50229,\nCVE-2024-50096, CVE-2024-49895, CVE-2024-47677, CVE-2024-49934,\nCVE-2024-53156, CVE-2024-49893, CVE-2024-49925, CVE-2024-50063,\nCVE-2024-49926, CVE-2024-50201, CVE-2024-50033, CVE-2024-50199,\nCVE-2024-49874, CVE-2024-47732, CVE-2024-50078, CVE-2024-49935,\nCVE-2024-49902, CVE-2024-49989, CVE-2024-47675, CVE-2024-50064,\nCVE-2024-50015, CVE-2024-41016, CVE-2024-49949, CVE-2024-50090,\nCVE-2024-49860, CVE-2024-50036, CVE-2024-50084, CVE-2024-50182,\nCVE-2024-50061, CVE-2024-47702, CVE-2024-47730, CVE-2024-49951,\nCVE-2024-49938, CVE-2024-50088, CVE-2024-50198, CVE-2024-49998,\nCVE-2024-49931, CVE-2024-49944, CVE-2024-50000, CVE-2024-49954,\nCVE-2024-47753, CVE-2024-49976, CVE-2024-50048, CVE-2024-49881,\nCVE-2024-50093, CVE-2024-50019, CVE-2024-50059, CVE-2024-50016,\nCVE-2024-50068, CVE-2024-49920, CVE-2024-50035, CVE-2024-50197,\nCVE-2024-47699, CVE-2024-49914, CVE-2024-50191, CVE-2024-50083,\nCVE-2024-47701, CVE-2024-49877, CVE-2024-50017, CVE-2024-49915,\nCVE-2024-50001, CVE-2024-49864, CVE-2024-50189, CVE-2024-50101,\nCVE-2024-47704, CVE-2024-50024, CVE-2024-50038, CVE-2024-49850,\nCVE-2024-50027, CVE-2024-49952, CVE-2024-50074, CVE-2024-50171,\nCVE-2024-53165, CVE-2024-47689, CVE-2024-49865, CVE-2024-49853,\nCVE-2024-47742, CVE-2024-49994, CVE-2024-50179, CVE-2024-47686,\nCVE-2024-49975, CVE-2024-49948, CVE-2024-50099, CVE-2024-50175,\nCVE-2024-50028, CVE-2024-49947, CVE-2024-47741, CVE-2024-49888,\nCVE-2024-50055, CVE-2024-47749, CVE-2024-49992, CVE-2024-47715,\nCVE-2024-49922, CVE-2024-47756, CVE-2024-50023, CVE-2024-47720,\nCVE-2024-50194, CVE-2024-47688, CVE-2024-49991, CVE-2024-47705,\nCVE-2024-49942, CVE-2024-50047, CVE-2024-49981, CVE-2024-49950,\nCVE-2024-47684, CVE-2024-50065, CVE-2024-49939, CVE-2024-47726,\nCVE-2024-47697, CVE-2024-49959, CVE-2024-47690, CVE-2024-50040,\nCVE-2024-50002, CVE-2024-50029, CVE-2024-47752, CVE-2024-49924,\nCVE-2024-50073, CVE-2024-47733, CVE-2024-50075, CVE-2024-49937,\nCVE-2024-47707, CVE-2024-47692, CVE-2024-47703, CVE-2024-49988,\nCVE-2024-50060, CVE-2024-50039, CVE-2024-49961, CVE-2024-50042,\nCVE-2024-50148, CVE-2024-47678, CVE-2024-49923, CVE-2024-49901,\nCVE-2024-47706, CVE-2024-49882, CVE-2024-47693, CVE-2024-49876,\nCVE-2024-47747, CVE-2024-49871, CVE-2024-50076, CVE-2024-50183,\nCVE-2024-50007, CVE-2024-49958, CVE-2024-50134)\n","status":"published","published":"2025-03-27T19:34:38Z","modified":"2026-10-29T20:02:41.736344599Z","updated_at":"2026-11-02T16:58:19.988474Z"},{"id":"USN-7386-1","title":"linux-oem-6.8 vulnerabilities","description":"\nMichael Randrianantenaina discovered that the Bluetooth driver in the Linux\nKernel contained an improper access control vulnerability. A nearby\nattacker could use this to connect a rougue device and possibly execute\narbitrary code. (CVE-2024-8805)\n\nAttila Szász discovered that the HFS+ file system implementation in the\nLinux Kernel contained a heap overflow vulnerability. An attacker could use\na specially crafted file system image that, when mounted, could cause a\ndenial of service (system crash) or possibly execute arbitrary code.\n(CVE-2025-0927)\n\nSeveral security issues were discovered in the Linux kernel.\nAn attacker could possibly use these to compromise the system.\nThis update corrects flaws in the following subsystems:\n  - ARM32 architecture;\n  - ARM64 architecture;\n  - x86 architecture;\n  - Block layer subsystem;\n  - Cryptographic API;\n  - ACPI drivers;\n  - Drivers core;\n  - ATA over ethernet (AOE) driver;\n  - Network block device driver;\n  - Ublk userspace block driver;\n  - Compressed RAM block device driver;\n  - TPM device driver;\n  - CPU frequency scaling framework;\n  - Hardware crypto device drivers;\n  - DAX dirext access to differentiated memory framework;\n  - ARM SCMI message protocol;\n  - EFI core;\n  - GPU drivers;\n  - HID subsystem;\n  - I2C subsystem;\n  - I3C subsystem;\n  - IIO subsystem;\n  - InfiniBand drivers;\n  - Input Device core drivers;\n  - IOMMU subsystem;\n  - IRQ chip drivers;\n  - Mailbox framework;\n  - Media drivers;\n  - Ethernet bonding driver;\n  - Network drivers;\n  - Mellanox network drivers;\n  - STMicroelectronics network drivers;\n  - NTB driver;\n  - Virtio pmem driver;\n  - Parport drivers;\n  - PCI subsystem;\n  - Alibaba DDR Sub-System Driveway PMU driver;\n  - Pin controllers subsystem;\n  - x86 platform drivers;\n  - Powercap sysfs driver;\n  - Remote Processor subsystem;\n  - SCSI subsystem;\n  - SuperH / SH-Mobile drivers;\n  - Direct Digital Synthesis drivers;\n  - Thermal drivers;\n  - TTY drivers;\n  - UFS subsystem;\n  - USB Device Class drivers;\n  - USB Gadget drivers;\n  - USB Host Controller drivers;\n  - TI TPS6598x USB Power Delivery controller driver;\n  - vDPA drivers;\n  - Virtio Host (VHOST) subsystem;\n  - Framebuffer layer;\n  - AFS file system;\n  - BTRFS file system;\n  - File systems infrastructure;\n  - Ceph distributed file system;\n  - Ext4 file system;\n  - F2FS 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  - SMB network file system;\n  - BPF subsystem;\n  - Network file system (NFS) superblock;\n  - Virtio network driver;\n  - Network traffic control;\n  - Network sockets;\n  - TCP network protocol;\n  - User-space API (UAPI);\n  - io_uring subsystem;\n  - Perf events;\n  - Kernel thread helper (kthread);\n  - Padata parallel execution mechanism;\n  - RCU subsystem;\n  - Arbitrary resource management;\n  - Static call mechanism;\n  - Timer subsystem;\n  - Tracing infrastructure;\n  - Maple Tree data structure library;\n  - Memory management;\n  - Bluetooth subsystem;\n  - Ethernet bridge;\n  - CAN network layer;\n  - Networking core;\n  - Distributed Switch Architecture;\n  - IPv4 networking;\n  - IPv6 networking;\n  - MAC80211 subsystem;\n  - IEEE 802.15.4 subsystem;\n  - Multipath TCP;\n  - NCSI (Network Controller Sideband Interface) driver;\n  - Netfilter;\n  - Netlink;\n  - RxRPC session sockets;\n  - SCTP protocol;\n  - TIPC protocol;\n  - Unix domain sockets;\n  - Wireless networking;\n  - eXpress Data Path;\n  - AudioScience HPI driver;\n  - KVM core;\n(CVE-2024-49952, CVE-2024-49920, CVE-2024-49945, CVE-2024-50180,\nCVE-2024-49944, CVE-2024-49987, CVE-2024-50148, CVE-2024-49959,\nCVE-2024-50063, CVE-2024-50083, CVE-2024-49878, CVE-2024-49870,\nCVE-2024-49863, CVE-2024-49921, CVE-2024-49992, CVE-2024-47691,\nCVE-2024-49913, CVE-2024-47712, CVE-2024-49948, CVE-2024-49976,\nCVE-2024-50085, CVE-2024-49891, CVE-2024-56614, CVE-2024-47713,\nCVE-2024-47703, CVE-2024-50191, CVE-2024-50087, CVE-2024-49958,\nCVE-2024-49868, CVE-2024-49922, CVE-2024-49960, CVE-2024-50019,\nCVE-2024-47749, CVE-2024-49996, CVE-2024-47677, CVE-2024-50065,\nCVE-2024-47744, CVE-2024-49968, CVE-2024-49985, CVE-2024-47752,\nCVE-2024-50017, CVE-2024-50183, CVE-2024-47709, CVE-2024-49938,\nCVE-2024-49876, CVE-2024-49893, CVE-2024-50134, CVE-2024-49972,\nCVE-2024-49934, CVE-2024-50015, CVE-2024-49856, CVE-2024-49853,\nCVE-2024-47711, CVE-2024-49949, CVE-2024-50026, CVE-2024-47681,\nCVE-2024-50000, CVE-2024-50189, CVE-2024-47716, CVE-2024-47723,\nCVE-2024-50044, CVE-2024-50179, CVE-2024-49871, CVE-2024-50008,\nCVE-2024-49955, CVE-2024-50007, CVE-2024-47695, CVE-2024-49889,\nCVE-2024-49954, CVE-2024-49894, CVE-2024-50014, CVE-2024-47731,\nCVE-2024-50055, CVE-2024-50098, CVE-2024-49930, CVE-2024-47684,\nCVE-2024-47705, CVE-2024-50029, CVE-2024-49901, CVE-2024-47689,\nCVE-2024-50022, CVE-2024-50009, CVE-2024-49937, CVE-2024-50197,\nCVE-2024-49911, CVE-2024-50076, CVE-2024-50002, CVE-2024-50077,\nCVE-2024-47679, CVE-2024-50025, CVE-2024-50069, CVE-2024-50101,\nCVE-2024-49942, CVE-2024-49986, CVE-2024-50012, CVE-2024-49858,\nCVE-2024-49884, CVE-2024-50201, CVE-2024-47701, CVE-2024-49994,\nCVE-2024-49897, CVE-2024-47687, CVE-2024-47751, CVE-2024-50001,\nCVE-2024-50117, CVE-2024-49909, CVE-2024-50086, CVE-2024-50064,\nCVE-2024-50088, CVE-2024-50005, CVE-2024-50184, CVE-2024-49882,\nCVE-2024-49936, CVE-2024-49933, CVE-2024-49995, CVE-2024-47704,\nCVE-2024-50066, CVE-2024-49898, CVE-2024-50068, CVE-2024-50192,\nCVE-2024-53104, CVE-2024-49860, CVE-2024-47741, CVE-2024-50039,\nCVE-2024-47699, CVE-2024-49861, CVE-2024-49969, CVE-2024-49950,\nCVE-2024-50194, CVE-2024-49929, CVE-2024-50006, CVE-2024-49997,\nCVE-2024-49983, CVE-2024-47710, CVE-2024-50200, CVE-2024-47692,\nCVE-2024-47748, CVE-2024-49855, CVE-2024-50182, CVE-2024-47706,\nCVE-2024-50188, CVE-2024-47732, CVE-2024-47707, CVE-2024-50048,\nCVE-2024-50058, CVE-2024-49912, CVE-2024-49966, CVE-2024-49852,\nCVE-2024-47753, CVE-2024-50202, CVE-2024-50062, CVE-2024-50056,\nCVE-2024-49946, CVE-2024-49902, CVE-2024-50033, CVE-2024-47750,\nCVE-2024-50021, CVE-2024-49939, CVE-2024-50072, CVE-2024-49851,\nCVE-2024-49928, CVE-2024-50061, CVE-2024-49885, CVE-2024-50047,\nCVE-2024-47672, CVE-2024-47734, CVE-2024-47714, CVE-2024-49886,\nCVE-2024-47730, CVE-2024-47697, CVE-2024-49973, CVE-2024-47718,\nCVE-2024-49862, CVE-2024-49963, CVE-2024-49881, CVE-2024-53165,\nCVE-2024-49998, CVE-2024-47757, CVE-2024-49982, CVE-2024-50186,\nCVE-2024-50016, CVE-2024-47675, CVE-2024-50090, CVE-2024-49917,\nCVE-2024-50031, CVE-2024-50093, CVE-2024-49859, CVE-2024-49890,\nCVE-2024-47670, CVE-2024-49919, CVE-2024-53156, CVE-2024-49924,\nCVE-2024-50078, CVE-2024-49864, CVE-2024-49962, CVE-2024-47720,\nCVE-2024-49874, CVE-2024-41016, CVE-2024-49991, CVE-2024-47726,\nCVE-2024-50171, CVE-2024-47682, CVE-2024-49865, CVE-2024-49988,\nCVE-2024-49903, CVE-2024-50035, CVE-2024-50229, CVE-2024-50075,\nCVE-2024-50195, CVE-2024-49947, CVE-2024-49900, CVE-2024-50040,\nCVE-2024-50176, CVE-2024-47686, CVE-2024-49978, CVE-2024-49923,\nCVE-2024-50199, CVE-2024-49999, CVE-2024-50070, CVE-2024-49953,\nCVE-2024-47733, CVE-2024-49888, CVE-2024-49977, CVE-2024-50080,\nCVE-2024-49905, CVE-2024-47737, CVE-2024-49961, CVE-2024-50030,\nCVE-2024-49951, CVE-2024-49892, CVE-2024-50096, CVE-2024-47735,\nCVE-2024-47673, CVE-2024-56663, CVE-2024-49981, CVE-2024-50049,\nCVE-2024-50193, CVE-2024-49957, CVE-2024-47742, CVE-2024-49880,\nCVE-2024-49965, CVE-2024-49927, CVE-2024-47690, CVE-2024-50057,\nCVE-2024-50073, CVE-2024-49931, CVE-2024-49875, CVE-2024-50041,\nCVE-2024-47700, CVE-2024-47719, CVE-2024-56582, CVE-2024-47738,\nCVE-2024-47754, CVE-2024-49850, CVE-2024-47678, CVE-2024-49935,\nCVE-2024-47739, CVE-2024-50028, CVE-2024-47727, CVE-2024-47728,\nCVE-2024-50084, CVE-2024-50095, CVE-2024-50175, CVE-2024-50198,\nCVE-2024-47702, CVE-2024-50187, CVE-2024-50032, CVE-2024-50074,\nCVE-2024-50020, CVE-2024-53144, CVE-2024-50233, CVE-2024-47698,\nCVE-2024-49879, CVE-2024-49896, CVE-2024-47747, CVE-2024-49877,\nCVE-2024-50046, CVE-2024-49866, CVE-2024-47740, CVE-2024-50042,\nCVE-2024-50060, CVE-2024-49925, CVE-2024-50013, CVE-2024-49867,\nCVE-2024-47685, CVE-2024-47743, CVE-2024-49883, CVE-2024-53170,\nCVE-2024-50038, CVE-2024-47756, CVE-2024-47696, CVE-2024-49980,\nCVE-2024-50185, CVE-2024-47693, CVE-2024-49915, CVE-2024-49914,\nCVE-2024-49907, CVE-2024-49989, CVE-2024-50196, CVE-2024-50027,\nCVE-2024-47745, CVE-2024-50045, CVE-2024-50024, CVE-2024-49918,\nCVE-2024-49975, CVE-2024-49974, CVE-2024-50082, CVE-2024-49895,\nCVE-2024-47671, CVE-2024-50059, CVE-2024-50099, CVE-2024-50023,\nCVE-2024-47688, CVE-2024-49926, CVE-2024-50036)\n","status":"published","published":"2025-03-27T19:50:07Z","modified":"2026-10-29T20:02:57.467469851Z","updated_at":"2026-11-02T16:58:19.988474Z"},{"id":"USN-7403-1","title":"linux-hwe-6.8 vulnerabilities","description":"Michael Randrianantenaina discovered that the Bluetooth driver in the Linux\nKernel contained an improper access control vulnerability. A nearby\nattacker could use this to connect a rougue device and possibly execute\narbitrary code. (CVE-2024-8805)\n\nAttila Szász discovered that the HFS+ file system implementation in the\nLinux Kernel contained a heap overflow vulnerability. An attacker could use\na specially crafted file system image that, when mounted, could cause a\ndenial of service (system crash) or possibly execute arbitrary code.\n(CVE-2025-0927)\n\nSeveral security issues were discovered in the Linux kernel.\nAn attacker could possibly use these to compromise the system.\nThis update corrects flaws in the following subsystems:\n  - ARM32 architecture;\n  - ARM64 architecture;\n  - x86 architecture;\n  - Block layer subsystem;\n  - Cryptographic API;\n  - ACPI drivers;\n  - Drivers core;\n  - ATA over ethernet (AOE) driver;\n  - Network block device driver;\n  - Ublk userspace block driver;\n  - Compressed RAM block device driver;\n  - TPM device driver;\n  - CPU frequency scaling framework;\n  - Hardware crypto device drivers;\n  - DAX dirext access to differentiated memory framework;\n  - ARM SCMI message protocol;\n  - EFI core;\n  - GPU drivers;\n  - HID subsystem;\n  - I2C subsystem;\n  - I3C subsystem;\n  - IIO subsystem;\n  - InfiniBand drivers;\n  - Input Device core drivers;\n  - IOMMU subsystem;\n  - IRQ chip drivers;\n  - Mailbox framework;\n  - Media drivers;\n  - Ethernet bonding driver;\n  - Network drivers;\n  - Mellanox network drivers;\n  - STMicroelectronics network drivers;\n  - NTB driver;\n  - Virtio pmem driver;\n  - Parport drivers;\n  - PCI subsystem;\n  - Alibaba DDR Sub-System Driveway PMU driver;\n  - Pin controllers subsystem;\n  - x86 platform drivers;\n  - Powercap sysfs driver;\n  - Remote Processor subsystem;\n  - SCSI subsystem;\n  - SuperH / SH-Mobile drivers;\n  - Direct Digital Synthesis drivers;\n  - Thermal drivers;\n  - TTY drivers;\n  - UFS subsystem;\n  - USB Device Class drivers;\n  - USB Gadget drivers;\n  - USB Host Controller drivers;\n  - TI TPS6598x USB Power Delivery controller driver;\n  - vDPA drivers;\n  - Virtio Host (VHOST) subsystem;\n  - Framebuffer layer;\n  - AFS file system;\n  - BTRFS file system;\n  - File systems infrastructure;\n  - Ceph distributed file system;\n  - Ext4 file system;\n  - F2FS 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  - SMB network file system;\n  - BPF subsystem;\n  - Network file system (NFS) superblock;\n  - Virtio network driver;\n  - Network namespace;\n  - Network traffic control;\n  - Network sockets;\n  - TCP network protocol;\n  - User-space API (UAPI);\n  - io_uring subsystem;\n  - Perf events;\n  - Kernel thread helper (kthread);\n  - Padata parallel execution mechanism;\n  - RCU subsystem;\n  - Arbitrary resource management;\n  - Static call mechanism;\n  - Timer subsystem;\n  - Tracing infrastructure;\n  - Maple Tree data structure library;\n  - Memory management;\n  - Bluetooth subsystem;\n  - Ethernet bridge;\n  - CAN network layer;\n  - Networking core;\n  - Distributed Switch Architecture;\n  - IPv4 networking;\n  - IPv6 networking;\n  - MAC80211 subsystem;\n  - IEEE 802.15.4 subsystem;\n  - Multipath TCP;\n  - NCSI (Network Controller Sideband Interface) driver;\n  - Netfilter;\n  - Netlink;\n  - RxRPC session sockets;\n  - SCTP protocol;\n  - TIPC protocol;\n  - Unix domain sockets;\n  - Wireless networking;\n  - eXpress Data Path;\n  - AudioScience HPI driver;\n  - KVM core;\n(CVE-2024-49950, CVE-2024-49955, CVE-2024-50077, CVE-2024-57798,\nCVE-2024-47671, CVE-2024-49987, CVE-2024-50078, CVE-2024-49985,\nCVE-2024-49981, CVE-2024-49852, CVE-2024-49882, CVE-2024-49925,\nCVE-2024-50047, CVE-2024-47752, CVE-2024-49851, CVE-2024-50229,\nCVE-2024-47675, CVE-2024-50017, CVE-2024-47726, CVE-2024-50008,\nCVE-2024-49889, CVE-2024-50059, CVE-2024-53144, CVE-2024-49959,\nCVE-2024-49886, CVE-2024-50035, CVE-2024-50036, CVE-2024-47713,\nCVE-2024-47720, CVE-2024-47756, CVE-2024-49974, CVE-2024-49864,\nCVE-2024-47688, CVE-2024-47735, CVE-2024-50060, CVE-2024-50182,\nCVE-2024-49894, CVE-2024-50002, CVE-2024-47748, CVE-2024-49949,\nCVE-2024-47757, CVE-2024-47678, CVE-2024-47737, CVE-2024-49880,\nCVE-2024-50093, CVE-2024-49914, CVE-2024-50048, CVE-2024-56658,\nCVE-2024-50058, CVE-2024-49995, CVE-2024-50096, CVE-2024-49877,\nCVE-2024-47715, CVE-2024-50007, CVE-2024-56614, CVE-2024-49948,\nCVE-2024-49935, CVE-2024-50009, CVE-2024-50200, CVE-2024-50070,\nCVE-2024-49856, CVE-2024-50005, CVE-2024-49865, CVE-2024-50085,\nCVE-2024-49892, CVE-2024-53063, CVE-2024-47695, CVE-2024-49991,\nCVE-2024-47687, CVE-2024-53140, CVE-2024-50179, CVE-2024-47682,\nCVE-2024-50080, CVE-2024-50056, CVE-2024-47690, CVE-2024-49939,\nCVE-2024-56663, CVE-2024-49913, CVE-2024-47745, CVE-2024-47739,\nCVE-2024-49920, CVE-2024-47704, CVE-2024-50068, CVE-2024-49876,\nCVE-2024-49992, CVE-2024-49980, CVE-2024-49907, CVE-2024-50019,\nCVE-2024-47747, CVE-2024-50022, CVE-2024-49946, CVE-2024-56595,\nCVE-2024-49875, CVE-2024-49968, CVE-2024-47706, CVE-2024-56672,\nCVE-2024-47744, CVE-2024-49866, CVE-2024-47677, CVE-2024-49999,\nCVE-2024-47684, CVE-2024-49952, CVE-2024-47702, CVE-2024-50084,\nCVE-2024-49884, CVE-2024-53165, CVE-2024-49997, CVE-2024-50082,\nCVE-2024-47705, CVE-2024-49958, CVE-2024-50031, CVE-2024-49927,\nCVE-2024-50171, CVE-2024-50193, CVE-2024-49965, CVE-2024-49919,\nCVE-2024-49915, CVE-2024-47712, CVE-2024-47692, CVE-2024-47686,\nCVE-2024-47727, CVE-2024-50000, CVE-2024-50006, CVE-2024-47714,\nCVE-2024-49878, CVE-2024-49911, CVE-2024-49936, CVE-2024-50028,\nCVE-2024-50046, CVE-2024-49975, CVE-2024-47709, CVE-2024-47718,\nCVE-2024-50192, CVE-2024-49928, CVE-2024-50030, CVE-2024-49874,\nCVE-2024-49903, CVE-2024-47711, CVE-2024-50069, CVE-2024-49923,\nCVE-2024-47723, CVE-2024-50233, CVE-2024-50088, CVE-2024-49859,\nCVE-2024-49973, CVE-2024-47685, CVE-2024-47679, CVE-2024-49890,\nCVE-2024-53104, CVE-2024-47670, CVE-2024-47730, CVE-2024-49861,\nCVE-2024-50086, CVE-2025-0927, CVE-2024-49893, CVE-2024-56582,\nCVE-2024-47719, CVE-2024-49982, CVE-2024-47691, CVE-2024-50087,\nCVE-2024-50185, CVE-2024-50045, CVE-2024-50064, CVE-2024-47689,\nCVE-2024-50020, CVE-2024-47672, CVE-2024-49966, CVE-2024-50038,\nCVE-2024-49897, CVE-2024-49969, CVE-2024-50180, CVE-2024-49901,\nCVE-2024-47751, CVE-2024-49850, CVE-2024-49951, CVE-2024-49905,\nCVE-2024-49953, CVE-2024-50001, CVE-2024-50062, CVE-2024-49994,\nCVE-2024-47734, CVE-2024-50175, CVE-2024-50195, CVE-2024-50049,\nCVE-2024-47753, CVE-2024-50074, CVE-2024-50202, CVE-2024-47728,\nCVE-2024-49902, CVE-2024-50187, CVE-2024-49954, CVE-2024-50024,\nCVE-2024-49929, CVE-2024-53170, CVE-2024-49855, CVE-2024-50134,\nCVE-2024-50039, CVE-2024-47754, CVE-2024-47743, CVE-2024-50198,\nCVE-2024-47698, CVE-2024-49989, CVE-2024-50191, CVE-2024-50063,\nCVE-2024-49879, CVE-2024-49983, CVE-2024-50016, CVE-2024-47696,\nCVE-2024-50099, CVE-2024-50025, CVE-2024-47731, CVE-2024-49853,\nCVE-2024-47697, CVE-2024-56598, CVE-2024-50196, CVE-2024-49977,\nCVE-2024-49896, CVE-2024-50090, CVE-2024-49881, CVE-2024-50055,\nCVE-2024-50029, CVE-2024-49978, CVE-2024-49917, CVE-2024-49868,\nCVE-2024-50201, CVE-2024-47707, CVE-2024-50188, CVE-2024-49870,\nCVE-2024-49960, CVE-2024-50026, CVE-2024-50014, CVE-2024-50072,\nCVE-2024-49900, CVE-2024-49895, CVE-2024-47732, CVE-2024-50044,\nCVE-2024-47703, CVE-2024-47700, CVE-2024-49986, CVE-2024-49858,\nCVE-2024-49944, CVE-2024-49912, CVE-2024-50015, CVE-2024-50075,\nCVE-2024-47673, CVE-2024-49926, CVE-2024-49933, CVE-2024-50095,\nCVE-2024-50027, CVE-2024-49957, CVE-2024-49996, CVE-2024-49862,\nCVE-2024-49891, CVE-2024-49863, CVE-2024-49871, CVE-2024-50061,\nCVE-2024-53156, CVE-2024-47716, CVE-2024-50184, CVE-2024-49918,\nCVE-2024-50013, CVE-2024-50073, CVE-2024-50042, CVE-2024-50199,\nCVE-2024-49922, CVE-2024-50098, CVE-2024-50148, CVE-2024-49921,\nCVE-2024-50176, CVE-2024-50194, CVE-2024-49961, CVE-2024-49931,\nCVE-2024-50101, CVE-2024-50021, CVE-2024-47701, CVE-2024-50033,\nCVE-2024-47740, CVE-2024-50041, CVE-2024-49947, CVE-2024-49972,\nCVE-2024-47750, CVE-2024-49934, CVE-2024-49924, CVE-2024-49860,\nCVE-2024-50012, CVE-2024-47681, CVE-2024-49930, CVE-2024-49883,\nCVE-2024-47710, CVE-2024-50186, CVE-2024-49976, CVE-2024-47738,\nCVE-2024-47742, CVE-2024-50197, CVE-2024-50302, CVE-2024-49938,\nCVE-2024-49888, CVE-2024-47693, CVE-2024-49937, CVE-2024-41016,\nCVE-2024-49945, CVE-2024-50023, CVE-2024-47749, CVE-2024-50057,\nCVE-2024-49962, CVE-2024-49998, CVE-2024-50076, CVE-2024-50083,\nCVE-2024-49909, CVE-2024-47733, CVE-2024-50117, CVE-2024-47741,\nCVE-2024-50040, CVE-2024-50066, CVE-2024-49942, CVE-2024-50065,\nCVE-2024-49898, CVE-2024-49867, CVE-2024-49988, CVE-2024-50183,\nCVE-2024-47699, CVE-2024-49885, CVE-2024-50189, CVE-2024-49963)\n","status":"published","published":"2025-04-01T22:26:48Z","modified":"2026-10-29T20:02:46.828181225Z","updated_at":"2026-11-02T16:58:19.988474Z"},{"id":"USN-7468-1","title":"linux-azure-nvidia vulnerabilities","description":"Michael Randrianantenaina discovered that the Bluetooth driver in the Linux\nKernel contained an improper access control vulnerability. A nearby\nattacker could use this to connect a rougue device and possibly execute\narbitrary code. (CVE-2024-8805)\n\nAttila Szász discovered that the HFS+ file system implementation in the\nLinux Kernel contained a heap overflow vulnerability. An attacker could use\na specially crafted file system image that, when mounted, could cause a\ndenial of service (system crash) or possibly execute arbitrary code.\n(CVE-2025-0927)\n\nIt was discovered that the CIFS network file system implementation in the\nLinux kernel did not properly verify the target namespace when handling\nupcalls. An attacker could use this to expose sensitive information.\n(CVE-2025-2312)\n\nSeveral security issues were discovered in the Linux kernel.\nAn attacker could possibly use these to compromise the system.\nThis update corrects flaws in the following subsystems:\n  - ARM64 architecture;\n  - MIPS architecture;\n  - PowerPC architecture;\n  - RISC-V architecture;\n  - S390 architecture;\n  - SuperH RISC architecture;\n  - User-Mode Linux (UML);\n  - x86 architecture;\n  - Block layer subsystem;\n  - Cryptographic API;\n  - Compute Acceleration Framework;\n  - ACPI drivers;\n  - Drivers core;\n  - ATA over ethernet (AOE) driver;\n  - RAM backed block device driver;\n  - Network block device driver;\n  - Ublk userspace block driver;\n  - Compressed RAM block device driver;\n  - TPM device driver;\n  - Clock framework and drivers;\n  - Data acquisition framework and drivers;\n  - CPU frequency scaling framework;\n  - Hardware crypto device drivers;\n  - CXL (Compute Express Link) drivers;\n  - DAX dirext access to differentiated memory framework;\n  - EDAC drivers;\n  - ARM SCMI message protocol;\n  - ARM SCPI message protocol;\n  - EFI core;\n  - iSCSI Boot Firmware Table Attributes driver;\n  - GPIO subsystem;\n  - GPU drivers;\n  - HID subsystem;\n  - I2C subsystem;\n  - I3C subsystem;\n  - IIO ADC drivers;\n  - IIO subsystem;\n  - InfiniBand drivers;\n  - Input Device core drivers;\n  - IOMMU subsystem;\n  - IRQ chip drivers;\n  - LED subsystem;\n  - Mailbox framework;\n  - Multiple devices driver;\n  - Media drivers;\n  - Multifunction device drivers;\n  - MMC subsystem;\n  - MTD block device drivers;\n  - Ethernet bonding driver;\n  - Network drivers;\n  - Mellanox network drivers;\n  - STMicroelectronics network drivers;\n  - NTB driver;\n  - Virtio pmem driver;\n  - NVME drivers;\n  - Parport drivers;\n  - PCI subsystem;\n  - PHY drivers;\n  - Pin controllers subsystem;\n  - x86 platform drivers;\n  - i.MX PM domains;\n  - Voltage and Current Regulator drivers;\n  - StarFive reset controller drivers;\n  - Real Time Clock drivers;\n  - SCSI subsystem;\n  - SuperH / SH-Mobile drivers;\n  - i.MX SoC drivers;\n  - QCOM SoC drivers;\n  - Xilinx SoC drivers;\n  - SPI subsystem;\n  - Direct Digital Synthesis drivers;\n  - Media staging drivers;\n  - TCM subsystem;\n  - Thermal drivers;\n  - TTY drivers;\n  - UFS subsystem;\n  - USB Device Class drivers;\n  - DesignWare USB3 driver;\n  - USB Gadget drivers;\n  - USB Host Controller drivers;\n  - USB Dual Role (OTG-ready) Controller drivers;\n  - USB Serial drivers;\n  - USB Type-C support driver;\n  - USB Type-C Port Controller Manager driver;\n  - TI TPS6598x USB Power Delivery controller driver;\n  - USB Type-C Connector System Software Interface driver;\n  - vDPA drivers;\n  - VFIO drivers;\n  - Virtio Host (VHOST) subsystem;\n  - Framebuffer layer;\n  - Xen hypervisor drivers;\n  - AFS file system;\n  - BTRFS file system;\n  - File systems infrastructure;\n  - Ceph distributed file system;\n  - EROFS file system;\n  - Ext4 file system;\n  - F2FS file system;\n  - JFFS2 file system;\n  - JFS file system;\n  - Network file systems library;\n  - Network file system (NFS) client;\n  - Network file system (NFS) server daemon;\n  - NILFS2 file system;\n  - NTFS3 file system;\n  - Overlay file system;\n  - Proc file system;\n  - Diskquota system;\n  - SMB network file system;\n  - UBI file system;\n  - DRM display driver;\n  - BPF subsystem;\n  - Kernel Samepage Merging mechanism;\n  - Network file system (NFS) superblock;\n  - Kernel stack handling interfaces;\n  - StackDepot library;\n  - Task handling mechanism;\n  - userfaultfd() syscall;\n  - Bluetooth subsystem;\n  - IP tunnels definitions;\n  - Network namespace;\n  - Netfilter;\n  - Network traffic control;\n  - Network sockets;\n  - TCP network protocol;\n  - Tracing infrastructure;\n  - User-space API (UAPI);\n  - Kernel init infrastructure;\n  - io_uring subsystem;\n  - IPC subsystem;\n  - DMA mapping infrastructure;\n  - Perf events;\n  - Kernel fork() syscall;\n  - KCSAN framework;\n  - Kernel thread helper (kthread);\n  - Padata parallel execution mechanism;\n  - RCU subsystem;\n  - Arbitrary resource management;\n  - Scheduler infrastructure;\n  - Signal handling mechanism;\n  - Static call mechanism;\n  - Timer subsystem;\n  - Vector I/O iterator library;\n  - KUnit library;\n  - Maple Tree data structure library;\n  - Memory management;\n  - 9P file system network protocol;\n  - Ethernet bridge;\n  - CAN network layer;\n  - Networking core;\n  - DCCP (Datagram Congestion Control Protocol);\n  - Distributed Switch Architecture;\n  - Ethtool driver;\n  - HSR network protocol;\n  - IEEE802154.4 network protocol;\n  - IPv4 networking;\n  - IPv6 networking;\n  - IUCV driver;\n  - MAC80211 subsystem;\n  - Multipath TCP;\n  - NCSI (Network Controller Sideband Interface) driver;\n  - Netlink;\n  - Packet sockets;\n  - RxRPC session sockets;\n  - SCTP protocol;\n  - SMC sockets;\n  - Sun RPC protocol;\n  - TIPC protocol;\n  - Unix domain sockets;\n  - VMware vSockets driver;\n  - Wireless networking;\n  - eXpress Data Path;\n  - XFRM subsystem;\n  - Integrity Measurement Architecture(IMA) framework;\n  - Key management;\n  - ALSA framework;\n  - FireWire sound drivers;\n  - AudioScience HPI driver;\n  - HD-audio driver;\n  - MediaTek ASoC drivers;\n  - QCOM ASoC drivers;\n  - SoC audio core drivers;\n  - STMicroelectronics SoC drivers;\n  - USB sound devices;\n(CVE-2024-49996, CVE-2024-56693, CVE-2024-49928, CVE-2024-47728,\nCVE-2024-50218, CVE-2024-50197, CVE-2024-50084, CVE-2024-56698,\nCVE-2024-56623, CVE-2024-50203, CVE-2024-56786, CVE-2024-53198,\nCVE-2024-49939, CVE-2024-49852, CVE-2024-49920, CVE-2024-53117,\nCVE-2024-50023, CVE-2024-56581, CVE-2024-49954, CVE-2024-56658,\nCVE-2024-56688, CVE-2024-56574, CVE-2024-56690, CVE-2024-53158,\nCVE-2024-56777, CVE-2024-56582, CVE-2024-56629, CVE-2024-49997,\nCVE-2024-50041, CVE-2024-53052, CVE-2024-50126, CVE-2024-56726,\nCVE-2024-50007, CVE-2024-47712, CVE-2024-50225, CVE-2024-50269,\nCVE-2024-50200, CVE-2024-53099, CVE-2024-50083, CVE-2024-53162,\nCVE-2024-57876, CVE-2024-50180, CVE-2024-56678, CVE-2024-50179,\nCVE-2024-56776, CVE-2024-53151, CVE-2024-56631, CVE-2024-50160,\nCVE-2024-50302, CVE-2024-53126, CVE-2024-50151, CVE-2024-49917,\nCVE-2024-49899, CVE-2024-49927, CVE-2024-48875, CVE-2024-50298,\nCVE-2024-53148, CVE-2024-53160, CVE-2024-50187, CVE-2024-50072,\nCVE-2024-56756, CVE-2024-56625, CVE-2024-44955, CVE-2024-47671,\nCVE-2024-47141, CVE-2024-50047, CVE-2024-50048, CVE-2024-50245,\nCVE-2024-50096, CVE-2024-56602, CVE-2024-53232, CVE-2024-50284,\nCVE-2024-53129, CVE-2024-56724, CVE-2024-56632, CVE-2024-49924,\nCVE-2024-47756, CVE-2024-53226, CVE-2024-50189, CVE-2024-56573,\nCVE-2024-50257, CVE-2024-50300, CVE-2024-47673, CVE-2024-50152,\nCVE-2024-53215, CVE-2024-50295, CVE-2024-50111, CVE-2024-49865,\nCVE-2024-47691, CVE-2024-56649, CVE-2024-56567, CVE-2024-53061,\nCVE-2024-50153, CVE-2024-53091, CVE-2024-56692, CVE-2024-41932,\nCVE-2024-56650, CVE-2024-56645, CVE-2024-47670, CVE-2024-53130,\nCVE-2024-50066, CVE-2024-50020, CVE-2024-50154, CVE-2024-49998,\nCVE-2024-50290, CVE-2024-56594, CVE-2024-56627, CVE-2024-49882,\nCVE-2024-50220, CVE-2024-49914, CVE-2024-50019, CVE-2024-53213,\nCVE-2024-50015, CVE-2024-53172, CVE-2024-50198, CVE-2024-53051,\nCVE-2024-50280, CVE-2024-53187, CVE-2024-50136, CVE-2024-47672,\nCVE-2024-56606, CVE-2024-47699, CVE-2024-56780, CVE-2024-56672,\nCVE-2024-56637, CVE-2024-49946, CVE-2024-56752, CVE-2024-50199,\nCVE-2024-53119, CVE-2024-53084, CVE-2024-50076, CVE-2024-49938,\nCVE-2024-50237, CVE-2024-56779, CVE-2024-50108, CVE-2024-50162,\nCVE-2024-49936, CVE-2024-41935, CVE-2024-53046, CVE-2024-56572,\nCVE-2024-53107, CVE-2024-53150, CVE-2024-56539, CVE-2024-49949,\nCVE-2024-41014, CVE-2024-53217, CVE-2024-49977, CVE-2025-21702,\nCVE-2024-50267, CVE-2024-50138, CVE-2024-50229, CVE-2024-56586,\nCVE-2024-50057, CVE-2024-50070, CVE-2024-49898, CVE-2024-50085,\nCVE-2024-56746, CVE-2024-53106, CVE-2024-47695, CVE-2024-50009,\nCVE-2024-50103, CVE-2024-47693, CVE-2024-53135, CVE-2024-53127,\nCVE-2024-50067, CVE-2024-57850, CVE-2024-56615, CVE-2024-50167,\nCVE-2024-50042, CVE-2024-56546, CVE-2024-47749, CVE-2024-47705,\nCVE-2024-47747, CVE-2024-56570, CVE-2024-56604, CVE-2024-53112,\nCVE-2024-49988, CVE-2024-56597, CVE-2024-50268, CVE-2024-53121,\nCVE-2024-56635, CVE-2024-50002, CVE-2024-50127, CVE-2024-56603,\nCVE-2024-56531, CVE-2024-49890, CVE-2024-53157, CVE-2024-50246,\nCVE-2024-56562, CVE-2024-56722, CVE-2024-49912, CVE-2024-56774,\nCVE-2024-49893, CVE-2024-56593, CVE-2024-53131, CVE-2024-57798,\nCVE-2024-50275, CVE-2024-50075, CVE-2024-53174, CVE-2024-53087,\nCVE-2024-50155, CVE-2024-47696, CVE-2024-53155, CVE-2024-50201,\nCVE-2024-53134, CVE-2024-49922, CVE-2024-53138, CVE-2024-47711,\nCVE-2024-47742, CVE-2024-53043, CVE-2024-48881, CVE-2024-53203,\nCVE-2024-53053, CVE-2024-56589, CVE-2024-56679, CVE-2024-49892,\nCVE-2024-56677, CVE-2024-53144, CVE-2024-50107, CVE-2024-56583,\nCVE-2025-21701, CVE-2024-49911, CVE-2024-50244, CVE-2024-49969,\nCVE-2024-50098, CVE-2024-50166, CVE-2024-47809, CVE-2024-56781,\nCVE-2024-49894, CVE-2025-21700, CVE-2024-49930, CVE-2024-56548,\nCVE-2024-50134, CVE-2024-53194, CVE-2024-50285, CVE-2024-42122,\nCVE-2024-53171, CVE-2024-53120, CVE-2024-50279, CVE-2024-57838,\nCVE-2024-50082, CVE-2024-50168, CVE-2024-53175, CVE-2024-47710,\nCVE-2024-49972, CVE-2024-56727, CVE-2024-49919, CVE-2024-53066,\nCVE-2024-56708, CVE-2024-53142, CVE-2024-49896, CVE-2024-49950,\nCVE-2024-53114, CVE-2024-47737, CVE-2024-56721, CVE-2024-50030,\nCVE-2024-50063, CVE-2024-56704, CVE-2024-56694, CVE-2024-49937,\nCVE-2024-56596, CVE-2024-49855, CVE-2024-53231, CVE-2024-50259,\nCVE-2024-50163, CVE-2024-50263, CVE-2024-56579, CVE-2024-50148,\nCVE-2024-50252, CVE-2024-56775, CVE-2024-53195, CVE-2024-56771,\nCVE-2024-56765, CVE-2024-50192, CVE-2024-56705, CVE-2024-56566,\nCVE-2024-49851, CVE-2024-56575, CVE-2024-53222, CVE-2024-50014,\nCVE-2024-49891, CVE-2024-53128, CVE-2024-49921, CVE-2024-50024,\nCVE-2024-56703, CVE-2024-56787, CVE-2024-56723, CVE-2024-56687,\nCVE-2024-47718, CVE-2024-49902, CVE-2024-49963, CVE-2024-56691,\nCVE-2024-53173, CVE-2024-56599, CVE-2024-50080, CVE-2024-47704,\nCVE-2024-49934, CVE-2024-56707, CVE-2024-49958, CVE-2024-49888,\nCVE-2024-53095, CVE-2024-53089, CVE-2024-49935, CVE-2024-50022,\nCVE-2024-47748, CVE-2024-56634, CVE-2024-53090, CVE-2024-50242,\nCVE-2024-53085, CVE-2024-50073, CVE-2024-50068, CVE-2024-49877,\nCVE-2024-56642, CVE-2024-53067, CVE-2024-50118, CVE-2024-50061,\nCVE-2024-49948, CVE-2024-53100, CVE-2024-50194, CVE-2024-50116,\nCVE-2024-48873, CVE-2024-53180, CVE-2024-56663, CVE-2024-50303,\nCVE-2024-50250, CVE-2024-50045, CVE-2024-50296, CVE-2024-49961,\nCVE-2024-56549, CVE-2024-50027, CVE-2024-53227, CVE-2024-50292,\nCVE-2024-49900, CVE-2024-50074, CVE-2024-53115, CVE-2024-56747,\nCVE-2024-50078, CVE-2024-56772, CVE-2024-53141, CVE-2024-50301,\nCVE-2024-53079, CVE-2024-50255, CVE-2024-56565, CVE-2024-53165,\nCVE-2024-52332, CVE-2024-53140, CVE-2024-50286, CVE-2024-53088,\nCVE-2024-53139, CVE-2024-49881, CVE-2024-49859, CVE-2024-50247,\nCVE-2024-50278, CVE-2024-50124, CVE-2024-47709, CVE-2024-50128,\nCVE-2024-49962, CVE-2024-50258, CVE-2024-56532, CVE-2024-47684,\nCVE-2024-56633, CVE-2024-53210, CVE-2024-49867, CVE-2024-50056,\nCVE-2024-50137, CVE-2024-47730, CVE-2024-49960, CVE-2024-50060,\nCVE-2024-49925, CVE-2024-50195, CVE-2024-50031, CVE-2024-50099,\nCVE-2024-49863, CVE-2024-49992, CVE-2024-53083, CVE-2024-56751,\nCVE-2024-50141, CVE-2024-47701, CVE-2024-53122, CVE-2024-56576,\nCVE-2024-47689, CVE-2024-50121, CVE-2024-50147, CVE-2024-50226,\nCVE-2024-50239, CVE-2024-56578, CVE-2024-50062, CVE-2024-50033,\nCVE-2024-49982, CVE-2024-56545, CVE-2024-53118, CVE-2024-50231,\nCVE-2024-50125, CVE-2024-50191, CVE-2024-49875, CVE-2024-47794,\nCVE-2024-49983, CVE-2024-56595, CVE-2024-50224, CVE-2024-47690,\nCVE-2024-50272, CVE-2024-49901, CVE-2024-56538, CVE-2024-50010,\nCVE-2024-49959, CVE-2024-53154, CVE-2024-53221, CVE-2024-49886,\nCVE-2024-50145, CVE-2024-49884, CVE-2024-50028, CVE-2024-50232,\nCVE-2024-53208, CVE-2024-50000, CVE-2024-56728, CVE-2024-50304,\nCVE-2024-49989, CVE-2024-47739, CVE-2024-56550, CVE-2024-50055,\nCVE-2024-56590, CVE-2024-53055, CVE-2024-50270, CVE-2024-53164,\nCVE-2024-49856, CVE-2024-57849, CVE-2024-47697, CVE-2024-43098,\nCVE-2024-50170, CVE-2024-53196, CVE-2024-50251, CVE-2024-56533,\nCVE-2024-41016, CVE-2024-53105, CVE-2024-53230, CVE-2024-50164,\nCVE-2024-50101, CVE-2024-56607, CVE-2024-50186, CVE-2024-50105,\nCVE-2024-47679, CVE-2024-48876, CVE-2024-50243, CVE-2024-47720,\nCVE-2024-53239, CVE-2024-53062, CVE-2024-50021, CVE-2024-56614,\nCVE-2024-53224, CVE-2024-56619, CVE-2024-53072, CVE-2024-53223,\nCVE-2024-50039, CVE-2024-49981, CVE-2024-50230, CVE-2024-47143,\nCVE-2024-53082, CVE-2024-50216, CVE-2024-47713, CVE-2024-56720,\nCVE-2024-56543, CVE-2024-53094, CVE-2024-53111, CVE-2024-50036,\nCVE-2024-50065, CVE-2024-57874, CVE-2024-56689, CVE-2024-53183,\nCVE-2024-53108, CVE-2024-56643, CVE-2024-49868, CVE-2024-56611,\nCVE-2024-50185, CVE-2024-50223, CVE-2024-50193, CVE-2024-56616,\nCVE-2024-50265, CVE-2024-56701, CVE-2024-50112, CVE-2024-50297,\nCVE-2024-50207, CVE-2024-56558, CVE-2024-56782, CVE-2024-53081,\nCVE-2024-50044, CVE-2024-50040, CVE-2024-49991, CVE-2024-50013,\nCVE-2024-53170, CVE-2024-56540, CVE-2024-47723, CVE-2024-49913,\nCVE-2024-53169, CVE-2024-49974, CVE-2024-50256, CVE-2024-49858,\nCVE-2024-56609, CVE-2024-50282, CVE-2024-53168, CVE-2024-50182,\nCVE-2024-49973, CVE-2024-56638, CVE-2024-56683, CVE-2024-50059,\nCVE-2024-56648, CVE-2024-45828, CVE-2024-56610, CVE-2024-47740,\nCVE-2024-47692, CVE-2024-50026, CVE-2024-50117, CVE-2024-50221,\nCVE-2024-49931, CVE-2024-49994, CVE-2024-50184, CVE-2024-50171,\nCVE-2024-50261, CVE-2024-50283, CVE-2024-50233, CVE-2024-53184,\nCVE-2024-53220, CVE-2024-53191, CVE-2024-53190, CVE-2024-56592,\nCVE-2024-47703, CVE-2024-53048, CVE-2024-49955, CVE-2024-50150,\nCVE-2024-50208, CVE-2024-56577, CVE-2024-50159, CVE-2024-50131,\nCVE-2024-56755, CVE-2024-50172, CVE-2024-53146, CVE-2024-53161,\nCVE-2024-50222, CVE-2024-49879, CVE-2024-50146, CVE-2024-53063,\nCVE-2024-49889, CVE-2024-50287, CVE-2024-56647, CVE-2024-56613,\nCVE-2024-50017, CVE-2024-56551, CVE-2024-53145, CVE-2024-53166,\nCVE-2024-56622, CVE-2025-21993, CVE-2024-50133, CVE-2024-53234,\nCVE-2024-53133, CVE-2024-47735, CVE-2024-49861, CVE-2024-50143,\nCVE-2024-50169, CVE-2024-50046, CVE-2024-50069, CVE-2024-56742,\nCVE-2024-50104, CVE-2024-56636, CVE-2024-56745, CVE-2024-56630,\nCVE-2024-50276, CVE-2024-53228, CVE-2024-49945, CVE-2025-21756,\nCVE-2024-50142, CVE-2024-56729, CVE-2024-49569, CVE-2024-49952,\nCVE-2024-50006, CVE-2024-50273, CVE-2024-49906, CVE-2024-53058,\nCVE-2024-49895, CVE-2024-50240, CVE-2024-49987, CVE-2024-53233,\nCVE-2024-53086, CVE-2024-50110, CVE-2024-50064, CVE-2024-49878,\nCVE-2024-56644, CVE-2024-56605, CVE-2024-47698, CVE-2024-53147,\nCVE-2024-47745, CVE-2024-56685, CVE-2024-50016, CVE-2024-49871,\nCVE-2024-47757, CVE-2024-53103, CVE-2024-56580, CVE-2024-49883,\nCVE-2024-53163, CVE-2024-53110, CVE-2024-50058, CVE-2024-56640,\nCVE-2024-53101, CVE-2024-53156, CVE-2022-49034, CVE-2024-53109,\nCVE-2024-49978, CVE-2024-50235, CVE-2024-53680, CVE-2024-50299,\nCVE-2024-53177, CVE-2024-50008, CVE-2024-56744, CVE-2025-21831,\nCVE-2024-50038, CVE-2024-50271, CVE-2024-53178, CVE-2024-50012,\nCVE-2024-53188, CVE-2024-49860, CVE-2024-53237, CVE-2024-50188,\nCVE-2024-49880, CVE-2024-50077, CVE-2024-49968, CVE-2024-50236,\nCVE-2024-50206, CVE-2024-53197, CVE-2024-56587, CVE-2024-53236,\nCVE-2024-50139, CVE-2024-50120, CVE-2024-56681, CVE-2024-53059,\nCVE-2024-53113, CVE-2024-50209, CVE-2024-49957, CVE-2024-49944,\nCVE-2024-50087, CVE-2024-56754, CVE-2024-49903, CVE-2024-56600,\nCVE-2024-47706, CVE-2024-49907, CVE-2024-53202, CVE-2024-50215,\nCVE-2024-47734, CVE-2024-56785, CVE-2024-53229, CVE-2024-53050,\nCVE-2024-50051, CVE-2024-53209, CVE-2024-56739, CVE-2024-50262,\nCVE-2024-50088, CVE-2024-56621, CVE-2024-49929, CVE-2024-57843,\nCVE-2024-56569, CVE-2024-50140, CVE-2024-50135, CVE-2024-57872,\nCVE-2024-49866, CVE-2024-53214, CVE-2024-50090, CVE-2024-49985,\nCVE-2024-56608, CVE-2024-56598, CVE-2024-49915, CVE-2024-53104,\nCVE-2024-50035, CVE-2024-53047, CVE-2024-53176, CVE-2024-56700,\nCVE-2024-49975, CVE-2024-53200, CVE-2024-50274, CVE-2024-56748,\nCVE-2024-56601, CVE-2024-50289, CVE-2024-50086, CVE-2024-53044,\nCVE-2024-50029, CVE-2024-49909, CVE-2024-47738, CVE-2024-47726,\nCVE-2024-56568, CVE-2024-53181, CVE-2024-53218, CVE-2024-56725,\nCVE-2024-56778, CVE-2024-50115, CVE-2024-50288, CVE-2024-50291,\nCVE-2024-50049, CVE-2024-56773, CVE-2024-50001, CVE-2024-49933,\nCVE-2024-50211, CVE-2024-50095, CVE-2024-56651, CVE-2024-50238,\nCVE-2024-47707, CVE-2024-50205, CVE-2024-50093, CVE-2024-50183,\nCVE-2024-56588, CVE-2024-49965, CVE-2024-56584, CVE-2024-53096,\nCVE-2024-50248, CVE-2024-50234, CVE-2024-49926, CVE-2024-49923,\nCVE-2024-49918, CVE-2024-50130, CVE-2024-53093, CVE-2024-56626,\nCVE-2024-50156, CVE-2024-56557, CVE-2024-50196, CVE-2024-56620,\nCVE-2024-49870, CVE-2024-50294, CVE-2024-53042, CVE-2024-53076,\nCVE-2024-49905, CVE-2024-53045, CVE-2024-50202, CVE-2024-56641,\nCVE-2024-53219, CVE-2024-50158, CVE-2024-50025, CVE-2024-47685,\nCVE-2024-49966, CVE-2024-53123, CVE-2024-53068, CVE-2024-47678)\n","status":"published","published":"2025-04-28T15:04:12Z","modified":"2026-11-03T21:17:55.939905598Z","updated_at":"2026-11-03T21:43:54.166508Z"}]}}