{"id":"CVE-2024-42152","aliases":["ALSA-2024:5928","ALSA-2024:7000","ALSA-2024:7001","AZL-47660","AZL-47685","BELL-CVE-2024-42152","CLSA-2024-1728936982","DEBIAN-CVE-2024-42152","DLA-4008-1","DSA-5747-1","EUVD-2024-39983","GHSA-ghw9-6h55-qj7v","MGASA-2024-0277","MGASA-2024-0278","OESA-2024-2124","OESA-2024-2321","OESA-2024-2322","OESA-2024-2324","RHSA-2024:5928","RHSA-2024:7000","RHSA-2024:7001","RHSA-2024:8613","RHSA-2024:8614","RLSA-2024:7000","RLSA-2024:7001","SUSE-SU-2024:3190-1","SUSE-SU-2024:3194-1","SUSE-SU-2024:3195-1","SUSE-SU-2024:3209-1","SUSE-SU-2024:3383-1","SUSE-SU-2024:3483-1","SUSE-SU-2025:20044-1","SUSE-SU-2025:20047-1","UBUNTU-CVE-2024-42152","USN-7007-1","USN-7007-2","USN-7007-3","USN-7009-1","USN-7009-2","USN-7019-1","USN-7089-1","USN-7089-2","USN-7089-3","USN-7089-4","USN-7089-5","USN-7089-6","USN-7089-7","USN-7090-1","USN-7095-1","USN-7156-1"],"status":"published","title":"nvmet: fix a possible leak when destroy a ctrl during qp establishment","description":"In the Linux kernel, the following vulnerability has been resolved:\n\nnvmet: fix a possible leak when destroy a ctrl during qp establishment\n\nIn nvmet_sq_destroy we capture sq-\u003ectrl early and if it is non-NULL we\nknow that a ctrl was allocated (in the admin connect request handler)\nand we need to release pending AERs, clear ctrl-\u003esqs and sq-\u003ectrl\n(for nvme-loop primarily), and drop the final reference on the ctrl.\n\nHowever, a small window is possible where nvmet_sq_destroy starts (as\na result of the client giving up and disconnecting) concurrently with\nthe nvme admin connect cmd (which may be in an early stage). But *before*\nkill_and_confirm of sq-\u003eref (i.e. the admin connect managed to get an sq\nlive reference). In this case, sq-\u003ectrl was allocated however after it was\ncaptured in a local variable in nvmet_sq_destroy.\nThis prevented the final reference drop on the ctrl.\n\nSolve this by re-capturing the sq-\u003ectrl after all inflight request has\ncompleted, where for sure sq-\u003ectrl reference is final, and move forward\nbased on that.\n\nThis issue was observed in an environment with many hosts connecting\nmultiple ctrls simoutanuosly, creating a delay in allocating a ctrl\nleading up to this race window.","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-10","score":0.00733,"percentile":0.5469,"model":"v2026.06.15"},"facts":{"in_kev":false,"known_exploited":false,"public_exploit":false,"fix_available":true},"cwes":["CWE-401"],"published":"2024-07-30T07:46:44Z","modified":"2026-11-02T12:02:46Z","fixes":[{"ecosystem":"Azure Linux:3","package":"kernel","fixed_in":["6.6.43.1-7"],"sources":["osv"]},{"ecosystem":"Azure Linux:2","package":"kernel","fixed_in":["5.15.164.1-1"],"sources":["osv"]},{"ecosystem":"Alpaquita:23","package":"linux-lts","fixed_in":["6.1.99-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":["5.10.222","5.15.163","6.1.98","6.6.39","6.9.9"],"sources":["osv"]},{"ecosystem":"Debian:12","package":"linux","fixed_in":["6.1.98-1"],"sources":["osv"]},{"ecosystem":"Debian:13","package":"linux","fixed_in":["6.9.9-1"],"sources":["osv"]},{"ecosystem":"Debian:14","package":"linux","fixed_in":["6.9.9-1"],"sources":["osv"]},{"ecosystem":"Ubuntu:20.04:LTS","package":"linux-aws-5.15","fixed_in":["5.15.0-1069.75~20.04.1"],"sources":["osv"]},{"ecosystem":"Ubuntu:20.04:LTS","package":"linux-azure-5.15","fixed_in":["5.15.0-1072.81~20.04.1"],"sources":["osv"]},{"ecosystem":"Ubuntu:20.04:LTS","package":"linux-gcp-5.15","fixed_in":["5.15.0-1068.76~20.04.1"],"sources":["osv"]},{"ecosystem":"Ubuntu:20.04:LTS","package":"linux-gkeop-5.15","fixed_in":["5.15.0-1052.59~20.04.1"],"sources":["osv"]},{"ecosystem":"Ubuntu:20.04:LTS","package":"linux-hwe-5.15","fixed_in":["5.15.0-121.131~20.04.1"],"sources":["osv"]},{"ecosystem":"Ubuntu:20.04:LTS","package":"linux-ibm-5.15","fixed_in":["5.15.0-1062.65~20.04.1"],"sources":["osv"]},{"ecosystem":"Ubuntu:20.04:LTS","package":"linux-intel-iotg-5.15","fixed_in":["5.15.0-1064.70~20.04.1"],"sources":["osv"]},{"ecosystem":"Ubuntu:20.04:LTS","package":"linux-lowlatency-hwe-5.15","fixed_in":["5.15.0-121.131~20.04.1"],"sources":["osv"]},{"ecosystem":"Ubuntu:20.04:LTS","package":"linux-nvidia-tegra-5.15","fixed_in":["5.15.0-1030.30~20.04.1"],"sources":["osv"]},{"ecosystem":"Ubuntu:20.04:LTS","package":"linux-oracle-5.15","fixed_in":["5.15.0-1067.73~20.04.1"],"sources":["osv"]},{"ecosystem":"Ubuntu:20.04:LTS","package":"linux-riscv-5.15","fixed_in":["5.15.0-1065.69~20.04.1"],"sources":["osv"]},{"ecosystem":"Ubuntu:22.04:LTS","package":"linux","fixed_in":["5.15.0-121.131"],"sources":["osv"]},{"ecosystem":"Ubuntu:22.04:LTS","package":"linux-aws","fixed_in":["5.15.0-1069.75"],"sources":["osv"]},{"ecosystem":"Ubuntu:22.04:LTS","package":"linux-aws-6.8","fixed_in":["6.8.0-1018.19~22.04.1"],"sources":["osv"]},{"ecosystem":"Ubuntu:22.04:LTS","package":"linux-azure","fixed_in":["5.15.0-1072.81"],"sources":["osv"]},{"ecosystem":"Ubuntu:22.04:LTS","package":"linux-azure-6.8","fixed_in":["6.8.0-1017.20~22.04.1"],"sources":["osv"]},{"ecosystem":"Ubuntu:22.04:LTS","package":"linux-azure-fde","fixed_in":["5.15.0-1072.81.1"],"sources":["osv"]},{"ecosystem":"Ubuntu:22.04:LTS","package":"linux-gcp","fixed_in":["5.15.0-1068.76"],"sources":["osv"]},{"ecosystem":"Ubuntu:22.04:LTS","package":"linux-gcp-6.8","fixed_in":["6.8.0-1017.19~22.04.1"],"sources":["osv"]},{"ecosystem":"Ubuntu:22.04:LTS","package":"linux-gke","fixed_in":["5.15.0-1066.72"],"sources":["osv"]},{"ecosystem":"Ubuntu:22.04:LTS","package":"linux-gkeop","fixed_in":["5.15.0-1052.59"],"sources":["osv"]},{"ecosystem":"Ubuntu:22.04:LTS","package":"linux-hwe-6.8","fixed_in":["6.8.0-48.48~22.04.1"],"sources":["osv"]},{"ecosystem":"Ubuntu:22.04:LTS","package":"linux-ibm","fixed_in":["5.15.0-1062.65"],"sources":["osv"]},{"ecosystem":"Ubuntu:22.04:LTS","package":"linux-ibm-6.8","fixed_in":["6.8.0-1015.15~22.04.1"],"sources":["osv"]},{"ecosystem":"Ubuntu:22.04:LTS","package":"linux-intel-iotg","fixed_in":["5.15.0-1064.70"],"sources":["osv"]},{"ecosystem":"Ubuntu:22.04:LTS","package":"linux-kvm","fixed_in":["5.15.0-1066.71"],"sources":["osv"]},{"ecosystem":"Ubuntu:22.04:LTS","package":"linux-lowlatency","fixed_in":["5.15.0-121.131"],"sources":["osv"]},{"ecosystem":"Ubuntu:22.04:LTS","package":"linux-lowlatency-hwe-6.8","fixed_in":["6.8.0-48.48.3~22.04.1"],"sources":["osv"]},{"ecosystem":"Ubuntu:22.04:LTS","package":"linux-nvidia","fixed_in":["5.15.0-1064.65"],"sources":["osv"]},{"ecosystem":"Ubuntu:22.04:LTS","package":"linux-nvidia-6.8","fixed_in":["6.8.0-1017.19~22.04.1"],"sources":["osv"]},{"ecosystem":"Ubuntu:22.04:LTS","package":"linux-nvidia-tegra","fixed_in":["5.15.0-1028.28"],"sources":["osv"]},{"ecosystem":"Ubuntu:22.04:LTS","package":"linux-nvidia-tegra-igx","fixed_in":["5.15.0-1016.16"],"sources":["osv"]},{"ecosystem":"Ubuntu:22.04:LTS","package":"linux-oracle","fixed_in":["5.15.0-1067.73"],"sources":["osv"]},{"ecosystem":"Ubuntu:22.04:LTS","package":"linux-oracle-6.8","fixed_in":["6.8.0-1015.15~22.04.1"],"sources":["osv"]},{"ecosystem":"Ubuntu:22.04:LTS","package":"linux-raspi","fixed_in":["5.15.0-1062.65"],"sources":["osv"]},{"ecosystem":"Ubuntu:22.04:LTS","package":"linux-riscv-6.8","fixed_in":["6.8.0-48.48.1~22.04.2"],"sources":["osv"]},{"ecosystem":"Ubuntu:22.04:LTS","package":"linux-xilinx-zynqmp","fixed_in":["5.15.0-1035.39"],"sources":["osv"]},{"ecosystem":"Ubuntu:Nvidia-BlueField:22.04:LTS","package":"linux-bluefield","fixed_in":["5.15.0-1052.54"],"sources":["osv"]},{"ecosystem":"Ubuntu:Pro:Realtime:22.04:LTS","package":"linux-intel-iot-realtime","fixed_in":["5.15.0-1063.65"],"sources":["osv"]},{"ecosystem":"Ubuntu:Pro:Realtime:22.04:LTS","package":"linux-realtime","fixed_in":["5.15.0-1070.78"],"sources":["osv"]},{"ecosystem":"Ubuntu:Pro:Realtime:22.04:LTS","package":"linux-realtime-6.8","fixed_in":["6.8.1-1011.11~22.04.1"],"sources":["osv"]},{"ecosystem":"Ubuntu:Pro:FIPS-updates:22.04:LTS","package":"linux-aws-fips","fixed_in":["5.15.0-1069.75+fips1"],"sources":["osv"]},{"ecosystem":"Ubuntu:Pro:FIPS-updates:22.04:LTS","package":"linux-azure-fips","fixed_in":["5.15.0-1072.81+fips1"],"sources":["osv"]},{"ecosystem":"Ubuntu:Pro:FIPS-updates:22.04:LTS","package":"linux-fips","fixed_in":["5.15.0-121.131+fips1"],"sources":["osv"]},{"ecosystem":"Ubuntu:Pro:FIPS-updates:22.04:LTS","package":"linux-gcp-fips","fixed_in":["5.15.0-1068.76+fips1"],"sources":["osv"]},{"ecosystem":"Ubuntu:24.04:LTS","package":"linux","fixed_in":["6.8.0-48.48"],"sources":["osv"]},{"ecosystem":"Ubuntu:24.04:LTS","package":"linux-aws","fixed_in":["6.8.0-1018.20"],"sources":["osv"]},{"ecosystem":"Ubuntu:24.04:LTS","package":"linux-azure","fixed_in":["6.8.0-1017.20"],"sources":["osv"]},{"ecosystem":"Ubuntu:24.04:LTS","package":"linux-gcp","fixed_in":["6.8.0-1017.19"],"sources":["osv"]},{"ecosystem":"Ubuntu:24.04:LTS","package":"linux-gke","fixed_in":["6.8.0-1013.17"],"sources":["osv"]},{"ecosystem":"Ubuntu:24.04:LTS","package":"linux-gkeop","fixed_in":["6.8.0-1002.4"],"sources":["osv"]},{"ecosystem":"Ubuntu:24.04:LTS","package":"linux-ibm","fixed_in":["6.8.0-1015.15"],"sources":["osv"]},{"ecosystem":"Ubuntu:24.04:LTS","package":"linux-lowlatency","fixed_in":["6.8.0-48.48.3"],"sources":["osv"]},{"ecosystem":"Ubuntu:24.04:LTS","package":"linux-nvidia","fixed_in":["6.8.0-1017.19"],"sources":["osv"]},{"ecosystem":"Ubuntu:24.04:LTS","package":"linux-nvidia-lowlatency","fixed_in":["6.8.0-1017.19.1"],"sources":["osv"]},{"ecosystem":"Ubuntu:24.04:LTS","package":"linux-oem-6.8","fixed_in":["6.8.0-1016.16"],"sources":["osv"]},{"ecosystem":"Ubuntu:24.04:LTS","package":"linux-oracle","fixed_in":["6.8.0-1015.16"],"sources":["osv"]},{"ecosystem":"Ubuntu:24.04:LTS","package":"linux-raspi","fixed_in":["6.8.0-1014.16"],"sources":["osv"]},{"ecosystem":"Ubuntu:24.04:LTS","package":"linux-riscv","fixed_in":["6.8.0-48.48.1"],"sources":["osv"]},{"ecosystem":"Ubuntu:24.04:LTS","package":"linux-xilinx","fixed_in":["6.8.0-1009.10"],"sources":["osv"]},{"ecosystem":"Ubuntu:Pro:Realtime:24.04:LTS","package":"linux-raspi-realtime","fixed_in":["6.8.0-2013.14"],"sources":["osv"]},{"ecosystem":"Ubuntu:Pro:Realtime:24.04:LTS","package":"linux-realtime","fixed_in":["6.8.1-1011.11"],"sources":["osv"]},{"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":"AlmaLinux:9","package":"bpftool","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"7.3.0-427.33.1.el9_4"}]}],"bundled":41},{"source":"osv","ecosystem":"AlmaLinux:9","package":"kernel","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-427.33.1.el9_4"}]}],"bundled":41},{"source":"osv","ecosystem":"AlmaLinux:9","package":"kernel-64k","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-427.33.1.el9_4"}]}],"bundled":41},{"source":"osv","ecosystem":"AlmaLinux:9","package":"kernel-64k-core","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-427.33.1.el9_4"}]}],"bundled":41},{"source":"osv","ecosystem":"AlmaLinux:9","package":"kernel-64k-debug","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-427.33.1.el9_4"}]}],"bundled":41},{"source":"osv","ecosystem":"AlmaLinux:9","package":"kernel-64k-debug-core","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-427.33.1.el9_4"}]}],"bundled":41},{"source":"osv","ecosystem":"AlmaLinux:9","package":"kernel-64k-debug-devel","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-427.33.1.el9_4"}]}],"bundled":41},{"source":"osv","ecosystem":"AlmaLinux:9","package":"kernel-64k-debug-devel-matched","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-427.33.1.el9_4"}]}],"bundled":41},{"source":"osv","ecosystem":"AlmaLinux:9","package":"kernel-64k-debug-modules","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-427.33.1.el9_4"}]}],"bundled":41},{"source":"osv","ecosystem":"AlmaLinux:9","package":"kernel-64k-debug-modules-core","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-427.33.1.el9_4"}]}],"bundled":41},{"source":"osv","ecosystem":"AlmaLinux:9","package":"kernel-64k-debug-modules-extra","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-427.33.1.el9_4"}]}],"bundled":41},{"source":"osv","ecosystem":"AlmaLinux:9","package":"kernel-64k-devel","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-427.33.1.el9_4"}]}],"bundled":41},{"source":"osv","ecosystem":"AlmaLinux:9","package":"kernel-64k-devel-matched","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-427.33.1.el9_4"}]}],"bundled":41},{"source":"osv","ecosystem":"AlmaLinux:9","package":"kernel-64k-modules","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-427.33.1.el9_4"}]}],"bundled":41},{"source":"osv","ecosystem":"AlmaLinux:9","package":"kernel-64k-modules-core","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-427.33.1.el9_4"}]}],"bundled":41},{"source":"osv","ecosystem":"AlmaLinux:9","package":"kernel-64k-modules-extra","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-427.33.1.el9_4"}]}],"bundled":41},{"source":"osv","ecosystem":"AlmaLinux:9","package":"kernel-abi-stablelists","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-427.33.1.el9_4"}]}],"bundled":41},{"source":"osv","ecosystem":"AlmaLinux:9","package":"kernel-core","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-427.33.1.el9_4"}]}],"bundled":41},{"source":"osv","ecosystem":"AlmaLinux:9","package":"kernel-cross-headers","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-427.33.1.el9_4"}]}],"bundled":41},{"source":"osv","ecosystem":"AlmaLinux:9","package":"kernel-debug","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-427.33.1.el9_4"}]}],"bundled":41},{"source":"osv","ecosystem":"AlmaLinux:9","package":"kernel-debug-core","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-427.33.1.el9_4"}]}],"bundled":41},{"source":"osv","ecosystem":"AlmaLinux:9","package":"kernel-debug-devel","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-427.33.1.el9_4"}]}],"bundled":41},{"source":"osv","ecosystem":"AlmaLinux:9","package":"kernel-debug-devel-matched","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-427.33.1.el9_4"}]}],"bundled":41},{"source":"osv","ecosystem":"AlmaLinux:9","package":"kernel-debug-modules","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-427.33.1.el9_4"}]}],"bundled":41},{"source":"osv","ecosystem":"AlmaLinux:9","package":"kernel-debug-modules-core","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-427.33.1.el9_4"}]}],"bundled":41},{"source":"osv","ecosystem":"AlmaLinux:9","package":"kernel-debug-modules-extra","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-427.33.1.el9_4"}]}],"bundled":41},{"source":"osv","ecosystem":"AlmaLinux:9","package":"kernel-debug-uki-virt","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-427.33.1.el9_4"}]}],"bundled":41},{"source":"osv","ecosystem":"AlmaLinux:9","package":"kernel-devel","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-427.33.1.el9_4"}]}],"bundled":41},{"source":"osv","ecosystem":"AlmaLinux:9","package":"kernel-devel-matched","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-427.33.1.el9_4"}]}],"bundled":41},{"source":"osv","ecosystem":"AlmaLinux:9","package":"kernel-doc","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-427.33.1.el9_4"}]}],"bundled":41},{"source":"osv","ecosystem":"AlmaLinux:9","package":"kernel-headers","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-427.33.1.el9_4"}]}],"bundled":41},{"source":"osv","ecosystem":"AlmaLinux:9","package":"kernel-modules","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-427.33.1.el9_4"}]}],"bundled":41},{"source":"osv","ecosystem":"AlmaLinux:9","package":"kernel-modules-core","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-427.33.1.el9_4"}]}],"bundled":41},{"source":"osv","ecosystem":"AlmaLinux:9","package":"kernel-modules-extra","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-427.33.1.el9_4"}]}],"bundled":41},{"source":"osv","ecosystem":"AlmaLinux:9","package":"kernel-rt","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-427.33.1.el9_4"}]}],"bundled":41},{"source":"osv","ecosystem":"AlmaLinux:9","package":"kernel-rt-core","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-427.33.1.el9_4"}]}],"bundled":41},{"source":"osv","ecosystem":"AlmaLinux:9","package":"kernel-rt-debug","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-427.33.1.el9_4"}]}],"bundled":41},{"source":"osv","ecosystem":"AlmaLinux:9","package":"kernel-rt-debug-core","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-427.33.1.el9_4"}]}],"bundled":41},{"source":"osv","ecosystem":"AlmaLinux:9","package":"kernel-rt-debug-devel","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-427.33.1.el9_4"}]}],"bundled":41},{"source":"osv","ecosystem":"AlmaLinux:9","package":"kernel-rt-debug-modules","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-427.33.1.el9_4"}]}],"bundled":41},{"source":"osv","ecosystem":"AlmaLinux:9","package":"kernel-rt-debug-modules-core","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-427.33.1.el9_4"}]}],"bundled":41},{"source":"osv","ecosystem":"AlmaLinux:9","package":"kernel-rt-debug-modules-extra","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-427.33.1.el9_4"}]}],"bundled":41},{"source":"osv","ecosystem":"AlmaLinux:9","package":"kernel-rt-devel","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-427.33.1.el9_4"}]}],"bundled":41},{"source":"osv","ecosystem":"AlmaLinux:9","package":"kernel-rt-modules","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-427.33.1.el9_4"}]}],"bundled":41},{"source":"osv","ecosystem":"AlmaLinux:9","package":"kernel-rt-modules-core","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-427.33.1.el9_4"}]}],"bundled":41},{"source":"osv","ecosystem":"AlmaLinux:9","package":"kernel-rt-modules-extra","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-427.33.1.el9_4"}]}],"bundled":41},{"source":"osv","ecosystem":"AlmaLinux:9","package":"kernel-tools","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-427.33.1.el9_4"}]}],"bundled":41},{"source":"osv","ecosystem":"AlmaLinux:9","package":"kernel-tools-libs","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-427.33.1.el9_4"}]}],"bundled":41},{"source":"osv","ecosystem":"AlmaLinux:9","package":"kernel-tools-libs-devel","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-427.33.1.el9_4"}]}],"bundled":41},{"source":"osv","ecosystem":"AlmaLinux:9","package":"kernel-uki-virt","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-427.33.1.el9_4"}]}],"bundled":41},{"source":"osv","ecosystem":"AlmaLinux:9","package":"kernel-zfcpdump","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-427.33.1.el9_4"}]}],"bundled":41},{"source":"osv","ecosystem":"AlmaLinux:9","package":"kernel-zfcpdump-core","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-427.33.1.el9_4"}]}],"bundled":41},{"source":"osv","ecosystem":"AlmaLinux:9","package":"kernel-zfcpdump-devel","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-427.33.1.el9_4"}]}],"bundled":41},{"source":"osv","ecosystem":"AlmaLinux:9","package":"kernel-zfcpdump-devel-matched","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-427.33.1.el9_4"}]}],"bundled":41},{"source":"osv","ecosystem":"AlmaLinux:9","package":"kernel-zfcpdump-modules","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-427.33.1.el9_4"}]}],"bundled":41},{"source":"osv","ecosystem":"AlmaLinux:9","package":"kernel-zfcpdump-modules-core","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-427.33.1.el9_4"}]}],"bundled":41},{"source":"osv","ecosystem":"AlmaLinux:9","package":"kernel-zfcpdump-modules-extra","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-427.33.1.el9_4"}]}],"bundled":41},{"source":"osv","ecosystem":"AlmaLinux:9","package":"libperf","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-427.33.1.el9_4"}]}],"bundled":41},{"source":"osv","ecosystem":"AlmaLinux:9","package":"perf","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-427.33.1.el9_4"}]}],"bundled":41},{"source":"osv","ecosystem":"AlmaLinux:9","package":"python3-perf","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-427.33.1.el9_4"}]}],"bundled":41},{"source":"osv","ecosystem":"AlmaLinux:9","package":"rtla","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-427.33.1.el9_4"}]}],"bundled":41},{"source":"osv","ecosystem":"AlmaLinux:9","package":"rv","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-427.33.1.el9_4"}]}],"bundled":41},{"source":"osv","ecosystem":"AlmaLinux:8","package":"bpftool","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.18.0-553.22.1.el8_10"}]}],"bundled":145},{"source":"osv","ecosystem":"AlmaLinux:8","package":"kernel","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.18.0-553.22.1.el8_10"}]}],"bundled":145},{"source":"osv","ecosystem":"AlmaLinux:8","package":"kernel-abi-stablelists","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.18.0-553.22.1.el8_10"}]}],"bundled":145},{"source":"osv","ecosystem":"AlmaLinux:8","package":"kernel-core","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.18.0-553.22.1.el8_10"}]}],"bundled":145},{"source":"osv","ecosystem":"AlmaLinux:8","package":"kernel-cross-headers","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.18.0-553.22.1.el8_10"}]}],"bundled":145},{"source":"osv","ecosystem":"AlmaLinux:8","package":"kernel-debug","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.18.0-553.22.1.el8_10"}]}],"bundled":145},{"source":"osv","ecosystem":"AlmaLinux:8","package":"kernel-debug-core","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.18.0-553.22.1.el8_10"}]}],"bundled":145},{"source":"osv","ecosystem":"AlmaLinux:8","package":"kernel-debug-devel","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.18.0-553.22.1.el8_10"}]}],"bundled":145},{"source":"osv","ecosystem":"AlmaLinux:8","package":"kernel-debug-modules","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.18.0-553.22.1.el8_10"}]}],"bundled":145},{"source":"osv","ecosystem":"AlmaLinux:8","package":"kernel-debug-modules-extra","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.18.0-553.22.1.el8_10"}]}],"bundled":145},{"source":"osv","ecosystem":"AlmaLinux:8","package":"kernel-devel","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.18.0-553.22.1.el8_10"}]}],"bundled":145},{"source":"osv","ecosystem":"AlmaLinux:8","package":"kernel-doc","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.18.0-553.22.1.el8_10"}]}],"bundled":145},{"source":"osv","ecosystem":"AlmaLinux:8","package":"kernel-headers","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.18.0-553.22.1.el8_10"}]}],"bundled":145},{"source":"osv","ecosystem":"AlmaLinux:8","package":"kernel-modules","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.18.0-553.22.1.el8_10"}]}],"bundled":145},{"source":"osv","ecosystem":"AlmaLinux:8","package":"kernel-modules-extra","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.18.0-553.22.1.el8_10"}]}],"bundled":145},{"source":"osv","ecosystem":"AlmaLinux:8","package":"kernel-tools","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.18.0-553.22.1.el8_10"}]}],"bundled":145},{"source":"osv","ecosystem":"AlmaLinux:8","package":"kernel-tools-libs","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.18.0-553.22.1.el8_10"}]}],"bundled":145},{"source":"osv","ecosystem":"AlmaLinux:8","package":"kernel-tools-libs-devel","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.18.0-553.22.1.el8_10"}]}],"bundled":145},{"source":"osv","ecosystem":"AlmaLinux:8","package":"kernel-zfcpdump","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.18.0-553.22.1.el8_10"}]}],"bundled":145},{"source":"osv","ecosystem":"AlmaLinux:8","package":"kernel-zfcpdump-core","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.18.0-553.22.1.el8_10"}]}],"bundled":145},{"source":"osv","ecosystem":"AlmaLinux:8","package":"kernel-zfcpdump-devel","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.18.0-553.22.1.el8_10"}]}],"bundled":145},{"source":"osv","ecosystem":"AlmaLinux:8","package":"kernel-zfcpdump-modules","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.18.0-553.22.1.el8_10"}]}],"bundled":145},{"source":"osv","ecosystem":"AlmaLinux:8","package":"kernel-zfcpdump-modules-extra","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.18.0-553.22.1.el8_10"}]}],"bundled":145},{"source":"osv","ecosystem":"AlmaLinux:8","package":"perf","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.18.0-553.22.1.el8_10"}]}],"bundled":145},{"source":"osv","ecosystem":"AlmaLinux:8","package":"python3-perf","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.18.0-553.22.1.el8_10"}]}],"bundled":145},{"source":"osv","ecosystem":"AlmaLinux:8","package":"kernel-rt","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.18.0-553.22.1.rt7.363.el8_10"}]}],"bundled":129},{"source":"osv","ecosystem":"AlmaLinux:8","package":"kernel-rt-core","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.18.0-553.22.1.rt7.363.el8_10"}]}],"bundled":129},{"source":"osv","ecosystem":"AlmaLinux:8","package":"kernel-rt-debug","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.18.0-553.22.1.rt7.363.el8_10"}]}],"bundled":129},{"source":"osv","ecosystem":"AlmaLinux:8","package":"kernel-rt-debug-core","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.18.0-553.22.1.rt7.363.el8_10"}]}],"bundled":129},{"source":"osv","ecosystem":"AlmaLinux:8","package":"kernel-rt-debug-devel","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.18.0-553.22.1.rt7.363.el8_10"}]}],"bundled":129},{"source":"osv","ecosystem":"AlmaLinux:8","package":"kernel-rt-debug-kvm","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.18.0-553.22.1.rt7.363.el8_10"}]}],"bundled":129},{"source":"osv","ecosystem":"AlmaLinux:8","package":"kernel-rt-debug-modules","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.18.0-553.22.1.rt7.363.el8_10"}]}],"bundled":129},{"source":"osv","ecosystem":"AlmaLinux:8","package":"kernel-rt-debug-modules-extra","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.18.0-553.22.1.rt7.363.el8_10"}]}],"bundled":129},{"source":"osv","ecosystem":"AlmaLinux:8","package":"kernel-rt-devel","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.18.0-553.22.1.rt7.363.el8_10"}]}],"bundled":129},{"source":"osv","ecosystem":"AlmaLinux:8","package":"kernel-rt-kvm","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.18.0-553.22.1.rt7.363.el8_10"}]}],"bundled":129},{"source":"osv","ecosystem":"AlmaLinux:8","package":"kernel-rt-modules","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.18.0-553.22.1.rt7.363.el8_10"}]}],"bundled":129},{"source":"osv","ecosystem":"AlmaLinux:8","package":"kernel-rt-modules-extra","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.18.0-553.22.1.rt7.363.el8_10"}]}],"bundled":129},{"source":"osv","ecosystem":"Azure Linux:3","package":"kernel","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.6.43.1-7"}]}]},{"source":"osv","ecosystem":"Azure Linux:2","package":"kernel","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.164.1-1"}]}]},{"source":"osv","ecosystem":"Alpaquita:23","package":"linux-lts","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"6.1.97-r0"},{"fixed":"6.1.99-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":"TuxCare:AlmaLinux:9.2","package":"bpftool","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"7.0.0-284.30.1.el9_2.tuxcare.els8"}]}],"bundled":86},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.2","package":"kernel","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-284.30.1.el9_2.tuxcare.els8"}]}],"bundled":86},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.2","package":"kernel-abi-stablelists","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-284.30.1.el9_2.tuxcare.els8"}]}],"bundled":86},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.2","package":"kernel-core","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-284.30.1.el9_2.tuxcare.els8"}]}],"bundled":86},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.2","package":"kernel-cross-headers","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-284.30.1.el9_2.tuxcare.els8"}]}],"bundled":86},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.2","package":"kernel-debug","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-284.30.1.el9_2.tuxcare.els8"}]}],"bundled":86},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.2","package":"kernel-debug-core","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-284.30.1.el9_2.tuxcare.els8"}]}],"bundled":86},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.2","package":"kernel-debug-devel","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-284.30.1.el9_2.tuxcare.els8"}]}],"bundled":86},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.2","package":"kernel-debug-devel-matched","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-284.30.1.el9_2.tuxcare.els8"}]}],"bundled":86},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.2","package":"kernel-debug-modules","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-284.30.1.el9_2.tuxcare.els8"}]}],"bundled":86},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.2","package":"kernel-debug-modules-core","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-284.30.1.el9_2.tuxcare.els8"}]}],"bundled":86},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.2","package":"kernel-debug-modules-extra","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-284.30.1.el9_2.tuxcare.els8"}]}],"bundled":86},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.2","package":"kernel-debug-modules-internal","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-284.30.1.el9_2.tuxcare.els8"}]}],"bundled":86},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.2","package":"kernel-debug-modules-partner","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-284.30.1.el9_2.tuxcare.els8"}]}],"bundled":86},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.2","package":"kernel-debug-uki-virt","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-284.30.1.el9_2.tuxcare.els8"}]}],"bundled":86},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.2","package":"kernel-devel","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-284.30.1.el9_2.tuxcare.els8"}]}],"bundled":86},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.2","package":"kernel-devel-matched","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-284.30.1.el9_2.tuxcare.els8"}]}],"bundled":86},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.2","package":"kernel-doc","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-284.30.1.el9_2.tuxcare.els8"}]}],"bundled":86},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.2","package":"kernel-headers","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-284.30.1.el9_2.tuxcare.els8"}]}],"bundled":86},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.2","package":"kernel-ipaclones-internal","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-284.30.1.el9_2.tuxcare.els8"}]}],"bundled":86},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.2","package":"kernel-modules","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-284.30.1.el9_2.tuxcare.els8"}]}],"bundled":86},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.2","package":"kernel-modules-core","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-284.30.1.el9_2.tuxcare.els8"}]}],"bundled":86},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.2","package":"kernel-modules-extra","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-284.30.1.el9_2.tuxcare.els8"}]}],"bundled":86},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.2","package":"kernel-modules-internal","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-284.30.1.el9_2.tuxcare.els8"}]}],"bundled":86},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.2","package":"kernel-modules-partner","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-284.30.1.el9_2.tuxcare.els8"}]}],"bundled":86},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.2","package":"kernel-selftests-internal","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-284.30.1.el9_2.tuxcare.els8"}]}],"bundled":86},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.2","package":"kernel-tools","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-284.30.1.el9_2.tuxcare.els8"}]}],"bundled":86},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.2","package":"kernel-tools-libs","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-284.30.1.el9_2.tuxcare.els8"}]}],"bundled":86},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.2","package":"kernel-tools-libs-devel","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-284.30.1.el9_2.tuxcare.els8"}]}],"bundled":86},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.2","package":"kernel-uki-virt","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-284.30.1.el9_2.tuxcare.els8"}]}],"bundled":86},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.2","package":"perf","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-284.30.1.el9_2.tuxcare.els8"}]}],"bundled":86},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.2","package":"python3-perf","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-284.30.1.el9_2.tuxcare.els8"}]}],"bundled":86},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.2","package":"rtla","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-284.30.1.el9_2.tuxcare.els8"}]}],"bundled":86},{"source":"osv","ecosystem":"Linux","package":"Kernel","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"5.6.0"},{"fixed":"5.10.222"}]},{"type":"ECOSYSTEM","events":[{"introduced":"5.11.0"},{"fixed":"5.15.163"}]},{"type":"ECOSYSTEM","events":[{"introduced":"5.16.0"},{"fixed":"6.1.98"}]},{"type":"ECOSYSTEM","events":[{"introduced":"6.2.0"},{"fixed":"6.6.39"}]},{"type":"ECOSYSTEM","events":[{"introduced":"6.7.0"},{"fixed":"6.9.9"}]}]},{"source":"osv","ecosystem":"Debian:12","package":"linux","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.1.98-1"}]}],"versions":["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"]},{"source":"osv","ecosystem":"Debian:13","package":"linux","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.9.9-1"}]}]},{"source":"osv","ecosystem":"Debian:14","package":"linux","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.9.9-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":"Debian:11","package":"linux","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.10.223-1"}]}],"versions":["5.10.103-1","5.10.103-1~bpo10+1","5.10.106-1","5.10.113-1","5.10.120-1","5.10.120-1~bpo10+1","5.10.127-1","5.10.127-2","5.10.127-2~bpo10+1","5.10.136-1","5.10.140-1","5.10.148-1","5.10.149-1","5.10.149-2","5.10.158-1","5.10.158-2","5.10.162-1","5.10.178-1","5.10.178-2","5.10.178-3","5.10.179-1","5.10.179-2","5.10.179-3","5.10.179-4","5.10.179-5","5.10.191-1","5.10.197-1","5.10.205-1","5.10.205-2","5.10.209-1","5.10.209-2","5.10.216-1","5.10.218-1","5.10.221-1","5.10.46-4","5.10.46-5","5.10.70-1","5.10.70-1~bpo10+1","5.10.84-1","5.10.92-1","5.10.92-1~bpo10+1","5.10.92-2"],"bundled":60},{"source":"osv","ecosystem":"Mageia:9","package":"kernel","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.6.43-1.mga9"}]}],"bundled":109},{"source":"osv","ecosystem":"Mageia:9","package":"kmod-xtables-addons","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"3.24-60.mga9"}]}],"bundled":109},{"source":"osv","ecosystem":"Mageia:9","package":"kmod-virtualbox","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"7.0.20-52.mga9"}]}],"bundled":109},{"source":"osv","ecosystem":"Mageia:9","package":"kernel-linus","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.6.43-1.mga9"}]}],"bundled":109},{"source":"osv","ecosystem":"openEuler:24.03-LTS","package":"kernel","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.6.0-41.0.0.48.oe2403"}]}],"bundled":93},{"source":"osv","ecosystem":"openEuler:22.03-LTS-SP4","package":"kernel","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.10.0-234.0.0.133.oe2203sp4"}]}],"bundled":62},{"source":"osv","ecosystem":"openEuler:22.03-LTS-SP3","package":"kernel","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.10.0-234.0.0.136.oe2203sp3"}]}],"bundled":62},{"source":"osv","ecosystem":"openEuler:22.03-LTS-SP1","package":"kernel","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.10.0-136.99.0.180.oe2203sp1"}]}],"bundled":74},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::appstream","package":"bpftool-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:7.3.0-427.33.1.el9_4"}]}],"bundled":42},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::appstream","package":"kernel-64k-debug-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-427.33.1.el9_4"}]}],"bundled":42},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::appstream","package":"kernel-64k-debug-devel","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-427.33.1.el9_4"}]}],"bundled":42},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::appstream","package":"kernel-64k-debug-devel-matched","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-427.33.1.el9_4"}]}],"bundled":42},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::appstream","package":"kernel-64k-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-427.33.1.el9_4"}]}],"bundled":42},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::appstream","package":"kernel-64k-devel","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-427.33.1.el9_4"}]}],"bundled":42},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::appstream","package":"kernel-64k-devel-matched","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-427.33.1.el9_4"}]}],"bundled":42},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::appstream","package":"kernel-debug-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-427.33.1.el9_4"}]}],"bundled":42},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::appstream","package":"kernel-debug-devel","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-427.33.1.el9_4"}]}],"bundled":42},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::appstream","package":"kernel-debug-devel-matched","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-427.33.1.el9_4"}]}],"bundled":42},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::appstream","package":"kernel-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-427.33.1.el9_4"}]}],"bundled":42},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::appstream","package":"kernel-debuginfo-common-aarch64","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-427.33.1.el9_4"}]}],"bundled":42},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::appstream","package":"kernel-debuginfo-common-ppc64le","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-427.33.1.el9_4"}]}],"bundled":42},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::appstream","package":"kernel-debuginfo-common-s390x","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-427.33.1.el9_4"}]}],"bundled":42},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::appstream","package":"kernel-debuginfo-common-x86_64","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-427.33.1.el9_4"}]}],"bundled":42},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::appstream","package":"kernel-devel","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-427.33.1.el9_4"}]}],"bundled":42},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::appstream","package":"kernel-devel-matched","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-427.33.1.el9_4"}]}],"bundled":42},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::appstream","package":"kernel-doc","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-427.33.1.el9_4"}]}],"bundled":42},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::appstream","package":"kernel-rt-debug-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-427.33.1.el9_4"}]}],"bundled":42},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::appstream","package":"kernel-rt-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-427.33.1.el9_4"}]}],"bundled":42},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::appstream","package":"kernel-tools-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-427.33.1.el9_4"}]}],"bundled":42},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::appstream","package":"kernel-zfcpdump-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-427.33.1.el9_4"}]}],"bundled":42},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::appstream","package":"kernel-zfcpdump-devel","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-427.33.1.el9_4"}]}],"bundled":42},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::appstream","package":"kernel-zfcpdump-devel-matched","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-427.33.1.el9_4"}]}],"bundled":42},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::appstream","package":"libperf-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-427.33.1.el9_4"}]}],"bundled":42},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::appstream","package":"perf","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-427.33.1.el9_4"}]}],"bundled":42},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::appstream","package":"perf-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-427.33.1.el9_4"}]}],"bundled":42},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::appstream","package":"python3-perf-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-427.33.1.el9_4"}]}],"bundled":42},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::appstream","package":"rtla","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-427.33.1.el9_4"}]}],"bundled":42},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::appstream","package":"rv","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-427.33.1.el9_4"}]}],"bundled":42},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::baseos","package":"bpftool","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:7.3.0-427.33.1.el9_4"}]}],"bundled":42},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::baseos","package":"bpftool-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:7.3.0-427.33.1.el9_4"}]}],"bundled":42},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::baseos","package":"kernel","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-427.33.1.el9_4"}]}],"bundled":42},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::baseos","package":"kernel-64k","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-427.33.1.el9_4"}]}],"bundled":42},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::baseos","package":"kernel-64k-core","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-427.33.1.el9_4"}]}],"bundled":42},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::baseos","package":"kernel-64k-debug","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-427.33.1.el9_4"}]}],"bundled":42},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::baseos","package":"kernel-64k-debug-core","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-427.33.1.el9_4"}]}],"bundled":42},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::baseos","package":"kernel-64k-debug-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-427.33.1.el9_4"}]}],"bundled":42},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::baseos","package":"kernel-64k-debug-modules","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-427.33.1.el9_4"}]}],"bundled":42},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::baseos","package":"kernel-64k-debug-modules-core","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-427.33.1.el9_4"}]}],"bundled":42},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::baseos","package":"kernel-64k-debug-modules-extra","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-427.33.1.el9_4"}]}],"bundled":42},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::baseos","package":"kernel-64k-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-427.33.1.el9_4"}]}],"bundled":42},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::baseos","package":"kernel-64k-modules","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-427.33.1.el9_4"}]}],"bundled":42},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::baseos","package":"kernel-64k-modules-core","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-427.33.1.el9_4"}]}],"bundled":42},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::baseos","package":"kernel-64k-modules-extra","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-427.33.1.el9_4"}]}],"bundled":42},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::baseos","package":"kernel-abi-stablelists","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-427.33.1.el9_4"}]}],"bundled":42},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::baseos","package":"kernel-core","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-427.33.1.el9_4"}]}],"bundled":42},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::baseos","package":"kernel-debug","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-427.33.1.el9_4"}]}],"bundled":42},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::baseos","package":"kernel-debug-core","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-427.33.1.el9_4"}]}],"bundled":42},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::baseos","package":"kernel-debug-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-427.33.1.el9_4"}]}],"bundled":42},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::baseos","package":"kernel-debug-modules","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-427.33.1.el9_4"}]}],"bundled":42},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::baseos","package":"kernel-debug-modules-core","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-427.33.1.el9_4"}]}],"bundled":42},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::baseos","package":"kernel-debug-modules-extra","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-427.33.1.el9_4"}]}],"bundled":42},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::baseos","package":"kernel-debug-uki-virt","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-427.33.1.el9_4"}]}],"bundled":42},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::baseos","package":"kernel-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-427.33.1.el9_4"}]}],"bundled":42},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::baseos","package":"kernel-debuginfo-common-aarch64","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-427.33.1.el9_4"}]}],"bundled":42},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::baseos","package":"kernel-debuginfo-common-ppc64le","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-427.33.1.el9_4"}]}],"bundled":42},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::baseos","package":"kernel-debuginfo-common-s390x","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-427.33.1.el9_4"}]}],"bundled":42},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::baseos","package":"kernel-debuginfo-common-x86_64","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-427.33.1.el9_4"}]}],"bundled":42},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::baseos","package":"kernel-modules","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-427.33.1.el9_4"}]}],"bundled":42},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::baseos","package":"kernel-modules-core","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-427.33.1.el9_4"}]}],"bundled":42},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::baseos","package":"kernel-modules-extra","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-427.33.1.el9_4"}]}],"bundled":42},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::baseos","package":"kernel-rt-debug-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-427.33.1.el9_4"}]}],"bundled":42},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::baseos","package":"kernel-rt-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-427.33.1.el9_4"}]}],"bundled":42},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::baseos","package":"kernel-tools","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-427.33.1.el9_4"}]}],"bundled":42},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::baseos","package":"kernel-tools-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-427.33.1.el9_4"}]}],"bundled":42},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::baseos","package":"kernel-tools-libs","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-427.33.1.el9_4"}]}],"bundled":42},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::baseos","package":"kernel-uki-virt","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-427.33.1.el9_4"}]}],"bundled":42},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::baseos","package":"kernel-zfcpdump","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-427.33.1.el9_4"}]}],"bundled":42},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::baseos","package":"kernel-zfcpdump-core","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-427.33.1.el9_4"}]}],"bundled":42},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::baseos","package":"kernel-zfcpdump-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-427.33.1.el9_4"}]}],"bundled":42},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::baseos","package":"kernel-zfcpdump-modules","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-427.33.1.el9_4"}]}],"bundled":42},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::baseos","package":"kernel-zfcpdump-modules-core","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-427.33.1.el9_4"}]}],"bundled":42},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::baseos","package":"kernel-zfcpdump-modules-extra","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-427.33.1.el9_4"}]}],"bundled":42},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::baseos","package":"libperf-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-427.33.1.el9_4"}]}],"bundled":42},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::baseos","package":"perf-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-427.33.1.el9_4"}]}],"bundled":42},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::baseos","package":"python3-perf","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-427.33.1.el9_4"}]}],"bundled":42},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::baseos","package":"python3-perf-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-427.33.1.el9_4"}]}],"bundled":42},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::crb","package":"bpftool-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:7.3.0-427.33.1.el9_4"}]}],"bundled":42},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::crb","package":"kernel-64k-debug-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-427.33.1.el9_4"}]}],"bundled":42},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::crb","package":"kernel-64k-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-427.33.1.el9_4"}]}],"bundled":42},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::crb","package":"kernel-debug-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-427.33.1.el9_4"}]}],"bundled":42},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::crb","package":"kernel-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-427.33.1.el9_4"}]}],"bundled":42},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::crb","package":"kernel-debuginfo-common-aarch64","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-427.33.1.el9_4"}]}],"bundled":42},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::crb","package":"kernel-debuginfo-common-ppc64le","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-427.33.1.el9_4"}]}],"bundled":42},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::crb","package":"kernel-debuginfo-common-s390x","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-427.33.1.el9_4"}]}],"bundled":42},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::crb","package":"kernel-debuginfo-common-x86_64","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-427.33.1.el9_4"}]}],"bundled":42},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::crb","package":"kernel-rt-debug-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-427.33.1.el9_4"}]}],"bundled":42},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::crb","package":"kernel-rt-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-427.33.1.el9_4"}]}],"bundled":42},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::crb","package":"kernel-tools-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-427.33.1.el9_4"}]}],"bundled":42},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::crb","package":"kernel-tools-libs-devel","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-427.33.1.el9_4"}]}],"bundled":42},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::crb","package":"kernel-zfcpdump-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-427.33.1.el9_4"}]}],"bundled":42},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::crb","package":"libperf","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-427.33.1.el9_4"}]}],"bundled":42},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::crb","package":"libperf-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-427.33.1.el9_4"}]}],"bundled":42},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::crb","package":"perf-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-427.33.1.el9_4"}]}],"bundled":42},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::crb","package":"python3-perf-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-427.33.1.el9_4"}]}],"bundled":42},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::nfv","package":"bpftool-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:7.3.0-427.33.1.el9_4"}]}],"bundled":42},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::nfv","package":"kernel-debug-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-427.33.1.el9_4"}]}],"bundled":42},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::nfv","package":"kernel-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-427.33.1.el9_4"}]}],"bundled":42},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::nfv","package":"kernel-debuginfo-common-x86_64","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-427.33.1.el9_4"}]}],"bundled":42},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::nfv","package":"kernel-rt","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-427.33.1.el9_4"}]}],"bundled":42},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::nfv","package":"kernel-rt-core","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-427.33.1.el9_4"}]}],"bundled":42},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::nfv","package":"kernel-rt-debug","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-427.33.1.el9_4"}]}],"bundled":42},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::nfv","package":"kernel-rt-debug-core","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-427.33.1.el9_4"}]}],"bundled":42},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::nfv","package":"kernel-rt-debug-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-427.33.1.el9_4"}]}],"bundled":42},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::nfv","package":"kernel-rt-debug-devel","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-427.33.1.el9_4"}]}],"bundled":42},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::nfv","package":"kernel-rt-debug-kvm","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-427.33.1.el9_4"}]}],"bundled":42},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::nfv","package":"kernel-rt-debug-modules","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-427.33.1.el9_4"}]}],"bundled":42},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::nfv","package":"kernel-rt-debug-modules-core","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-427.33.1.el9_4"}]}],"bundled":42},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::nfv","package":"kernel-rt-debug-modules-extra","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-427.33.1.el9_4"}]}],"bundled":42},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::nfv","package":"kernel-rt-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-427.33.1.el9_4"}]}],"bundled":42},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::nfv","package":"kernel-rt-devel","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-427.33.1.el9_4"}]}],"bundled":42},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::nfv","package":"kernel-rt-kvm","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-427.33.1.el9_4"}]}],"bundled":42},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::nfv","package":"kernel-rt-modules","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-427.33.1.el9_4"}]}],"bundled":42},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::nfv","package":"kernel-rt-modules-core","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-427.33.1.el9_4"}]}],"bundled":42},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::nfv","package":"kernel-rt-modules-extra","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-427.33.1.el9_4"}]}],"bundled":42},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::nfv","package":"kernel-tools-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-427.33.1.el9_4"}]}],"bundled":42},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::nfv","package":"libperf-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-427.33.1.el9_4"}]}],"bundled":42},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::nfv","package":"perf-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-427.33.1.el9_4"}]}],"bundled":42},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::nfv","package":"python3-perf-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-427.33.1.el9_4"}]}],"bundled":42},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::realtime","package":"bpftool-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:7.3.0-427.33.1.el9_4"}]}],"bundled":42},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::realtime","package":"kernel-debug-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-427.33.1.el9_4"}]}],"bundled":42},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::realtime","package":"kernel-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-427.33.1.el9_4"}]}],"bundled":42},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::realtime","package":"kernel-debuginfo-common-x86_64","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-427.33.1.el9_4"}]}],"bundled":42},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::realtime","package":"kernel-rt","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-427.33.1.el9_4"}]}],"bundled":42},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::realtime","package":"kernel-rt-core","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-427.33.1.el9_4"}]}],"bundled":42},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::realtime","package":"kernel-rt-debug","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-427.33.1.el9_4"}]}],"bundled":42},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::realtime","package":"kernel-rt-debug-core","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-427.33.1.el9_4"}]}],"bundled":42},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::realtime","package":"kernel-rt-debug-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-427.33.1.el9_4"}]}],"bundled":42},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::realtime","package":"kernel-rt-debug-devel","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-427.33.1.el9_4"}]}],"bundled":42},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::realtime","package":"kernel-rt-debug-modules","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-427.33.1.el9_4"}]}],"bundled":42},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::realtime","package":"kernel-rt-debug-modules-core","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-427.33.1.el9_4"}]}],"bundled":42},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::realtime","package":"kernel-rt-debug-modules-extra","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-427.33.1.el9_4"}]}],"bundled":42},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::realtime","package":"kernel-rt-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-427.33.1.el9_4"}]}],"bundled":42},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::realtime","package":"kernel-rt-devel","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-427.33.1.el9_4"}]}],"bundled":42},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::realtime","package":"kernel-rt-modules","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-427.33.1.el9_4"}]}],"bundled":42},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::realtime","package":"kernel-rt-modules-core","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-427.33.1.el9_4"}]}],"bundled":42},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::realtime","package":"kernel-rt-modules-extra","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-427.33.1.el9_4"}]}],"bundled":42},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::realtime","package":"kernel-tools-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-427.33.1.el9_4"}]}],"bundled":42},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::realtime","package":"libperf-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-427.33.1.el9_4"}]}],"bundled":42},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::realtime","package":"perf-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-427.33.1.el9_4"}]}],"bundled":42},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::realtime","package":"python3-perf-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-427.33.1.el9_4"}]}],"bundled":42},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:8::baseos","package":"bpftool","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:4.18.0-553.22.1.el8_10"}]}],"bundled":151},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:8::baseos","package":"bpftool-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:4.18.0-553.22.1.el8_10"}]}],"bundled":151},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:8::baseos","package":"kernel","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:4.18.0-553.22.1.el8_10"}]}],"bundled":151},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:8::baseos","package":"kernel-abi-stablelists","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:4.18.0-553.22.1.el8_10"}]}],"bundled":151},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:8::baseos","package":"kernel-core","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:4.18.0-553.22.1.el8_10"}]}],"bundled":151},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:8::baseos","package":"kernel-debug","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:4.18.0-553.22.1.el8_10"}]}],"bundled":151},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:8::baseos","package":"kernel-debug-core","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:4.18.0-553.22.1.el8_10"}]}],"bundled":151},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:8::baseos","package":"kernel-debug-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:4.18.0-553.22.1.el8_10"}]}],"bundled":151},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:8::baseos","package":"kernel-debug-devel","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:4.18.0-553.22.1.el8_10"}]}],"bundled":151},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:8::baseos","package":"kernel-debug-modules","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:4.18.0-553.22.1.el8_10"}]}],"bundled":151},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:8::baseos","package":"kernel-debug-modules-extra","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:4.18.0-553.22.1.el8_10"}]}],"bundled":151},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:8::baseos","package":"kernel-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:4.18.0-553.22.1.el8_10"}]}],"bundled":151},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:8::baseos","package":"kernel-debuginfo-common-aarch64","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:4.18.0-553.22.1.el8_10"}]}],"bundled":151},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:8::baseos","package":"kernel-debuginfo-common-ppc64le","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:4.18.0-553.22.1.el8_10"}]}],"bundled":151},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:8::baseos","package":"kernel-debuginfo-common-s390x","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:4.18.0-553.22.1.el8_10"}]}],"bundled":151},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:8::baseos","package":"kernel-debuginfo-common-x86_64","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:4.18.0-553.22.1.el8_10"}]}],"bundled":151},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:8::baseos","package":"kernel-devel","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:4.18.0-553.22.1.el8_10"}]}],"bundled":151},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:8::baseos","package":"kernel-doc","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:4.18.0-553.22.1.el8_10"}]}],"bundled":151},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:8::baseos","package":"kernel-modules","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:4.18.0-553.22.1.el8_10"}]}],"bundled":151},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:8::baseos","package":"kernel-modules-extra","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:4.18.0-553.22.1.el8_10"}]}],"bundled":151},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:8::baseos","package":"kernel-tools","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:4.18.0-553.22.1.el8_10"}]}],"bundled":151},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:8::baseos","package":"kernel-tools-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:4.18.0-553.22.1.el8_10"}]}],"bundled":151},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:8::baseos","package":"kernel-tools-libs","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:4.18.0-553.22.1.el8_10"}]}],"bundled":151},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:8::baseos","package":"kernel-zfcpdump","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:4.18.0-553.22.1.el8_10"}]}],"bundled":151},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:8::baseos","package":"kernel-zfcpdump-core","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:4.18.0-553.22.1.el8_10"}]}],"bundled":151},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:8::baseos","package":"kernel-zfcpdump-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:4.18.0-553.22.1.el8_10"}]}],"bundled":151},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:8::baseos","package":"kernel-zfcpdump-devel","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:4.18.0-553.22.1.el8_10"}]}],"bundled":151},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:8::baseos","package":"kernel-zfcpdump-modules","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:4.18.0-553.22.1.el8_10"}]}],"bundled":151},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:8::baseos","package":"kernel-zfcpdump-modules-extra","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:4.18.0-553.22.1.el8_10"}]}],"bundled":151},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:8::baseos","package":"perf","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:4.18.0-553.22.1.el8_10"}]}],"bundled":151},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:8::baseos","package":"perf-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:4.18.0-553.22.1.el8_10"}]}],"bundled":151},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:8::baseos","package":"python3-perf","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:4.18.0-553.22.1.el8_10"}]}],"bundled":151},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:8::baseos","package":"python3-perf-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:4.18.0-553.22.1.el8_10"}]}],"bundled":151},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:8::crb","package":"bpftool-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:4.18.0-553.22.1.el8_10"}]}],"bundled":151},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:8::crb","package":"kernel-debug-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:4.18.0-553.22.1.el8_10"}]}],"bundled":151},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:8::crb","package":"kernel-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:4.18.0-553.22.1.el8_10"}]}],"bundled":151},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:8::crb","package":"kernel-debuginfo-common-aarch64","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:4.18.0-553.22.1.el8_10"}]}],"bundled":151},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:8::crb","package":"kernel-debuginfo-common-ppc64le","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:4.18.0-553.22.1.el8_10"}]}],"bundled":151},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:8::crb","package":"kernel-debuginfo-common-x86_64","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:4.18.0-553.22.1.el8_10"}]}],"bundled":151},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:8::crb","package":"kernel-tools-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:4.18.0-553.22.1.el8_10"}]}],"bundled":151},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:8::crb","package":"kernel-tools-libs-devel","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:4.18.0-553.22.1.el8_10"}]}],"bundled":151},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:8::crb","package":"perf-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:4.18.0-553.22.1.el8_10"}]}],"bundled":151},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:8::crb","package":"python3-perf-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:4.18.0-553.22.1.el8_10"}]}],"bundled":151},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:8::nfv","package":"kernel-rt","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:4.18.0-553.22.1.rt7.363.el8_10"}]}],"bundled":129},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:8::nfv","package":"kernel-rt-core","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:4.18.0-553.22.1.rt7.363.el8_10"}]}],"bundled":129},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:8::nfv","package":"kernel-rt-debug","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:4.18.0-553.22.1.rt7.363.el8_10"}]}],"bundled":129},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:8::nfv","package":"kernel-rt-debug-core","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:4.18.0-553.22.1.rt7.363.el8_10"}]}],"bundled":129},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:8::nfv","package":"kernel-rt-debug-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:4.18.0-553.22.1.rt7.363.el8_10"}]}],"bundled":129},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:8::nfv","package":"kernel-rt-debug-devel","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:4.18.0-553.22.1.rt7.363.el8_10"}]}],"bundled":129},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:8::nfv","package":"kernel-rt-debug-kvm","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:4.18.0-553.22.1.rt7.363.el8_10"}]}],"bundled":129},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:8::nfv","package":"kernel-rt-debug-modules","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:4.18.0-553.22.1.rt7.363.el8_10"}]}],"bundled":129},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:8::nfv","package":"kernel-rt-debug-modules-extra","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:4.18.0-553.22.1.rt7.363.el8_10"}]}],"bundled":129},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:8::nfv","package":"kernel-rt-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:4.18.0-553.22.1.rt7.363.el8_10"}]}],"bundled":129},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:8::nfv","package":"kernel-rt-debuginfo-common-x86_64","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:4.18.0-553.22.1.rt7.363.el8_10"}]}],"bundled":129},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:8::nfv","package":"kernel-rt-devel","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:4.18.0-553.22.1.rt7.363.el8_10"}]}],"bundled":129},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:8::nfv","package":"kernel-rt-kvm","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:4.18.0-553.22.1.rt7.363.el8_10"}]}],"bundled":129},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:8::nfv","package":"kernel-rt-modules","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:4.18.0-553.22.1.rt7.363.el8_10"}]}],"bundled":129},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:8::nfv","package":"kernel-rt-modules-extra","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:4.18.0-553.22.1.rt7.363.el8_10"}]}],"bundled":129},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:8::realtime","package":"kernel-rt","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:4.18.0-553.22.1.rt7.363.el8_10"}]}],"bundled":129},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:8::realtime","package":"kernel-rt-core","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:4.18.0-553.22.1.rt7.363.el8_10"}]}],"bundled":129},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:8::realtime","package":"kernel-rt-debug","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:4.18.0-553.22.1.rt7.363.el8_10"}]}],"bundled":129},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:8::realtime","package":"kernel-rt-debug-core","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:4.18.0-553.22.1.rt7.363.el8_10"}]}],"bundled":129},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:8::realtime","package":"kernel-rt-debug-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:4.18.0-553.22.1.rt7.363.el8_10"}]}],"bundled":129},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:8::realtime","package":"kernel-rt-debug-devel","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:4.18.0-553.22.1.rt7.363.el8_10"}]}],"bundled":129},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:8::realtime","package":"kernel-rt-debug-modules","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:4.18.0-553.22.1.rt7.363.el8_10"}]}],"bundled":129},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:8::realtime","package":"kernel-rt-debug-modules-extra","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:4.18.0-553.22.1.rt7.363.el8_10"}]}],"bundled":129},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:8::realtime","package":"kernel-rt-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:4.18.0-553.22.1.rt7.363.el8_10"}]}],"bundled":129},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:8::realtime","package":"kernel-rt-debuginfo-common-x86_64","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:4.18.0-553.22.1.rt7.363.el8_10"}]}],"bundled":129},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:8::realtime","package":"kernel-rt-devel","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:4.18.0-553.22.1.rt7.363.el8_10"}]}],"bundled":129},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:8::realtime","package":"kernel-rt-modules","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:4.18.0-553.22.1.rt7.363.el8_10"}]}],"bundled":129},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:8::realtime","package":"kernel-rt-modules-extra","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:4.18.0-553.22.1.rt7.363.el8_10"}]}],"bundled":129},{"source":"osv","ecosystem":"Red Hat:rhel_eus:9.2::appstream","package":"bpftool-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:7.0.0-284.90.1.el9_2"}]}],"bundled":16},{"source":"osv","ecosystem":"Red Hat:rhel_eus:9.2::appstream","package":"kernel-64k-debug-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-284.90.1.el9_2"}]}],"bundled":16},{"source":"osv","ecosystem":"Red Hat:rhel_eus:9.2::appstream","package":"kernel-64k-debug-devel","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-284.90.1.el9_2"}]}],"bundled":16},{"source":"osv","ecosystem":"Red Hat:rhel_eus:9.2::appstream","package":"kernel-64k-debug-devel-matched","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-284.90.1.el9_2"}]}],"bundled":16},{"source":"osv","ecosystem":"Red Hat:rhel_eus:9.2::appstream","package":"kernel-64k-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-284.90.1.el9_2"}]}],"bundled":16},{"source":"osv","ecosystem":"Red Hat:rhel_eus:9.2::appstream","package":"kernel-64k-devel","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-284.90.1.el9_2"}]}],"bundled":16},{"source":"osv","ecosystem":"Red Hat:rhel_eus:9.2::appstream","package":"kernel-64k-devel-matched","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-284.90.1.el9_2"}]}],"bundled":16},{"source":"osv","ecosystem":"Red Hat:rhel_eus:9.2::appstream","package":"kernel-debug-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-284.90.1.el9_2"}]}],"bundled":16},{"source":"osv","ecosystem":"Red Hat:rhel_eus:9.2::appstream","package":"kernel-debug-devel","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-284.90.1.el9_2"}]}],"bundled":16},{"source":"osv","ecosystem":"Red Hat:rhel_eus:9.2::appstream","package":"kernel-debug-devel-matched","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-284.90.1.el9_2"}]}],"bundled":16},{"source":"osv","ecosystem":"Red Hat:rhel_eus:9.2::appstream","package":"kernel-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-284.90.1.el9_2"}]}],"bundled":16},{"source":"osv","ecosystem":"Red Hat:rhel_eus:9.2::appstream","package":"kernel-debuginfo-common-aarch64","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-284.90.1.el9_2"}]}],"bundled":16},{"source":"osv","ecosystem":"Red Hat:rhel_eus:9.2::appstream","package":"kernel-debuginfo-common-ppc64le","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-284.90.1.el9_2"}]}],"bundled":16},{"source":"osv","ecosystem":"Red Hat:rhel_eus:9.2::appstream","package":"kernel-debuginfo-common-s390x","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-284.90.1.el9_2"}]}],"bundled":16},{"source":"osv","ecosystem":"Red Hat:rhel_eus:9.2::appstream","package":"kernel-debuginfo-common-x86_64","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-284.90.1.el9_2"}]}],"bundled":16},{"source":"osv","ecosystem":"Red Hat:rhel_eus:9.2::appstream","package":"kernel-devel","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-284.90.1.el9_2"}]}],"bundled":16},{"source":"osv","ecosystem":"Red Hat:rhel_eus:9.2::appstream","package":"kernel-devel-matched","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-284.90.1.el9_2"}]}],"bundled":16},{"source":"osv","ecosystem":"Red Hat:rhel_eus:9.2::appstream","package":"kernel-tools-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-284.90.1.el9_2"}]}],"bundled":16},{"source":"osv","ecosystem":"Red Hat:rhel_eus:9.2::appstream","package":"kernel-zfcpdump-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-284.90.1.el9_2"}]}],"bundled":16},{"source":"osv","ecosystem":"Red Hat:rhel_eus:9.2::appstream","package":"kernel-zfcpdump-devel","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-284.90.1.el9_2"}]}],"bundled":16},{"source":"osv","ecosystem":"Red Hat:rhel_eus:9.2::appstream","package":"kernel-zfcpdump-devel-matched","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-284.90.1.el9_2"}]}],"bundled":16},{"source":"osv","ecosystem":"Red Hat:rhel_eus:9.2::appstream","package":"perf","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-284.90.1.el9_2"}]}],"bundled":16},{"source":"osv","ecosystem":"Red Hat:rhel_eus:9.2::appstream","package":"perf-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-284.90.1.el9_2"}]}],"bundled":16},{"source":"osv","ecosystem":"Red Hat:rhel_eus:9.2::appstream","package":"python3-perf-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-284.90.1.el9_2"}]}],"bundled":16},{"source":"osv","ecosystem":"Red Hat:rhel_eus:9.2::appstream","package":"rtla","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-284.90.1.el9_2"}]}],"bundled":16},{"source":"osv","ecosystem":"Red Hat:rhel_eus:9.2::baseos","package":"bpftool","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:7.0.0-284.90.1.el9_2"}]}],"bundled":16},{"source":"osv","ecosystem":"Red Hat:rhel_eus:9.2::baseos","package":"bpftool-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:7.0.0-284.90.1.el9_2"}]}],"bundled":16},{"source":"osv","ecosystem":"Red Hat:rhel_eus:9.2::baseos","package":"kernel","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-284.90.1.el9_2"}]}],"bundled":16},{"source":"osv","ecosystem":"Red Hat:rhel_eus:9.2::baseos","package":"kernel-64k","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-284.90.1.el9_2"}]}],"bundled":16},{"source":"osv","ecosystem":"Red Hat:rhel_eus:9.2::baseos","package":"kernel-64k-core","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-284.90.1.el9_2"}]}],"bundled":16},{"source":"osv","ecosystem":"Red Hat:rhel_eus:9.2::baseos","package":"kernel-64k-debug","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-284.90.1.el9_2"}]}],"bundled":16},{"source":"osv","ecosystem":"Red Hat:rhel_eus:9.2::baseos","package":"kernel-64k-debug-core","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-284.90.1.el9_2"}]}],"bundled":16},{"source":"osv","ecosystem":"Red Hat:rhel_eus:9.2::baseos","package":"kernel-64k-debug-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-284.90.1.el9_2"}]}],"bundled":16},{"source":"osv","ecosystem":"Red Hat:rhel_eus:9.2::baseos","package":"kernel-64k-debug-modules","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-284.90.1.el9_2"}]}],"bundled":16},{"source":"osv","ecosystem":"Red Hat:rhel_eus:9.2::baseos","package":"kernel-64k-debug-modules-core","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-284.90.1.el9_2"}]}],"bundled":16},{"source":"osv","ecosystem":"Red Hat:rhel_eus:9.2::baseos","package":"kernel-64k-debug-modules-extra","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-284.90.1.el9_2"}]}],"bundled":16},{"source":"osv","ecosystem":"Red Hat:rhel_eus:9.2::baseos","package":"kernel-64k-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-284.90.1.el9_2"}]}],"bundled":16},{"source":"osv","ecosystem":"Red Hat:rhel_eus:9.2::baseos","package":"kernel-64k-modules","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-284.90.1.el9_2"}]}],"bundled":16},{"source":"osv","ecosystem":"Red Hat:rhel_eus:9.2::baseos","package":"kernel-64k-modules-core","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-284.90.1.el9_2"}]}],"bundled":16},{"source":"osv","ecosystem":"Red Hat:rhel_eus:9.2::baseos","package":"kernel-64k-modules-extra","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-284.90.1.el9_2"}]}],"bundled":16},{"source":"osv","ecosystem":"Red Hat:rhel_eus:9.2::baseos","package":"kernel-abi-stablelists","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-284.90.1.el9_2"}]}],"bundled":16},{"source":"osv","ecosystem":"Red Hat:rhel_eus:9.2::baseos","package":"kernel-core","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-284.90.1.el9_2"}]}],"bundled":16},{"source":"osv","ecosystem":"Red Hat:rhel_eus:9.2::baseos","package":"kernel-debug","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-284.90.1.el9_2"}]}],"bundled":16},{"source":"osv","ecosystem":"Red Hat:rhel_eus:9.2::baseos","package":"kernel-debug-core","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-284.90.1.el9_2"}]}],"bundled":16},{"source":"osv","ecosystem":"Red Hat:rhel_eus:9.2::baseos","package":"kernel-debug-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-284.90.1.el9_2"}]}],"bundled":16},{"source":"osv","ecosystem":"Red Hat:rhel_eus:9.2::baseos","package":"kernel-debug-modules","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-284.90.1.el9_2"}]}],"bundled":16},{"source":"osv","ecosystem":"Red Hat:rhel_eus:9.2::baseos","package":"kernel-debug-modules-core","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-284.90.1.el9_2"}]}],"bundled":16},{"source":"osv","ecosystem":"Red Hat:rhel_eus:9.2::baseos","package":"kernel-debug-modules-extra","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-284.90.1.el9_2"}]}],"bundled":16},{"source":"osv","ecosystem":"Red Hat:rhel_eus:9.2::baseos","package":"kernel-debug-uki-virt","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-284.90.1.el9_2"}]}],"bundled":16},{"source":"osv","ecosystem":"Red Hat:rhel_eus:9.2::baseos","package":"kernel-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-284.90.1.el9_2"}]}],"bundled":16},{"source":"osv","ecosystem":"Red Hat:rhel_eus:9.2::baseos","package":"kernel-debuginfo-common-aarch64","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-284.90.1.el9_2"}]}],"bundled":16},{"source":"osv","ecosystem":"Red Hat:rhel_eus:9.2::baseos","package":"kernel-debuginfo-common-ppc64le","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-284.90.1.el9_2"}]}],"bundled":16},{"source":"osv","ecosystem":"Red Hat:rhel_eus:9.2::baseos","package":"kernel-debuginfo-common-s390x","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-284.90.1.el9_2"}]}],"bundled":16},{"source":"osv","ecosystem":"Red Hat:rhel_eus:9.2::baseos","package":"kernel-debuginfo-common-x86_64","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-284.90.1.el9_2"}]}],"bundled":16},{"source":"osv","ecosystem":"Red Hat:rhel_eus:9.2::baseos","package":"kernel-modules","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-284.90.1.el9_2"}]}],"bundled":16},{"source":"osv","ecosystem":"Red Hat:rhel_eus:9.2::baseos","package":"kernel-modules-core","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-284.90.1.el9_2"}]}],"bundled":16},{"source":"osv","ecosystem":"Red Hat:rhel_eus:9.2::baseos","package":"kernel-modules-extra","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-284.90.1.el9_2"}]}],"bundled":16},{"source":"osv","ecosystem":"Red Hat:rhel_eus:9.2::baseos","package":"kernel-tools","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-284.90.1.el9_2"}]}],"bundled":16},{"source":"osv","ecosystem":"Red Hat:rhel_eus:9.2::baseos","package":"kernel-tools-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-284.90.1.el9_2"}]}],"bundled":16},{"source":"osv","ecosystem":"Red Hat:rhel_eus:9.2::baseos","package":"kernel-tools-libs","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-284.90.1.el9_2"}]}],"bundled":16},{"source":"osv","ecosystem":"Red Hat:rhel_eus:9.2::baseos","package":"kernel-uki-virt","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-284.90.1.el9_2"}]}],"bundled":16},{"source":"osv","ecosystem":"Red Hat:rhel_eus:9.2::baseos","package":"kernel-zfcpdump","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-284.90.1.el9_2"}]}],"bundled":16},{"source":"osv","ecosystem":"Red Hat:rhel_eus:9.2::baseos","package":"kernel-zfcpdump-core","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-284.90.1.el9_2"}]}],"bundled":16},{"source":"osv","ecosystem":"Red Hat:rhel_eus:9.2::baseos","package":"kernel-zfcpdump-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-284.90.1.el9_2"}]}],"bundled":16},{"source":"osv","ecosystem":"Red Hat:rhel_eus:9.2::baseos","package":"kernel-zfcpdump-modules","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-284.90.1.el9_2"}]}],"bundled":16},{"source":"osv","ecosystem":"Red Hat:rhel_eus:9.2::baseos","package":"kernel-zfcpdump-modules-core","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-284.90.1.el9_2"}]}],"bundled":16},{"source":"osv","ecosystem":"Red Hat:rhel_eus:9.2::baseos","package":"kernel-zfcpdump-modules-extra","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-284.90.1.el9_2"}]}],"bundled":16},{"source":"osv","ecosystem":"Red Hat:rhel_eus:9.2::baseos","package":"perf-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-284.90.1.el9_2"}]}],"bundled":16},{"source":"osv","ecosystem":"Red Hat:rhel_eus:9.2::baseos","package":"python3-perf","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-284.90.1.el9_2"}]}],"bundled":16},{"source":"osv","ecosystem":"Red Hat:rhel_eus:9.2::baseos","package":"python3-perf-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-284.90.1.el9_2"}]}],"bundled":16},{"source":"osv","ecosystem":"Red Hat:rhel_eus:9.2::crb","package":"bpftool-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:7.0.0-284.90.1.el9_2"}]}],"bundled":16},{"source":"osv","ecosystem":"Red Hat:rhel_eus:9.2::crb","package":"kernel-64k-debug-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-284.90.1.el9_2"}]}],"bundled":16},{"source":"osv","ecosystem":"Red Hat:rhel_eus:9.2::crb","package":"kernel-64k-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-284.90.1.el9_2"}]}],"bundled":16},{"source":"osv","ecosystem":"Red Hat:rhel_eus:9.2::crb","package":"kernel-debug-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-284.90.1.el9_2"}]}],"bundled":16},{"source":"osv","ecosystem":"Red Hat:rhel_eus:9.2::crb","package":"kernel-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-284.90.1.el9_2"}]}],"bundled":16},{"source":"osv","ecosystem":"Red Hat:rhel_eus:9.2::crb","package":"kernel-debuginfo-common-aarch64","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-284.90.1.el9_2"}]}],"bundled":16},{"source":"osv","ecosystem":"Red Hat:rhel_eus:9.2::crb","package":"kernel-debuginfo-common-ppc64le","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-284.90.1.el9_2"}]}],"bundled":16},{"source":"osv","ecosystem":"Red Hat:rhel_eus:9.2::crb","package":"kernel-debuginfo-common-s390x","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-284.90.1.el9_2"}]}],"bundled":16},{"source":"osv","ecosystem":"Red Hat:rhel_eus:9.2::crb","package":"kernel-debuginfo-common-x86_64","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-284.90.1.el9_2"}]}],"bundled":16},{"source":"osv","ecosystem":"Red Hat:rhel_eus:9.2::crb","package":"kernel-tools-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-284.90.1.el9_2"}]}],"bundled":16},{"source":"osv","ecosystem":"Red Hat:rhel_eus:9.2::crb","package":"kernel-tools-libs-devel","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-284.90.1.el9_2"}]}],"bundled":16},{"source":"osv","ecosystem":"Red Hat:rhel_eus:9.2::crb","package":"kernel-zfcpdump-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-284.90.1.el9_2"}]}],"bundled":16},{"source":"osv","ecosystem":"Red Hat:rhel_eus:9.2::crb","package":"perf-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-284.90.1.el9_2"}]}],"bundled":16},{"source":"osv","ecosystem":"Red Hat:rhel_eus:9.2::crb","package":"python3-perf-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-284.90.1.el9_2"}]}],"bundled":16},{"source":"osv","ecosystem":"Red Hat:rhel_eus:9.2::appstream","package":"kernel-doc","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-284.90.1.el9_2"}]}],"bundled":16},{"source":"osv","ecosystem":"Red Hat:rhel_eus:9.2::nfv","package":"kernel-rt","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-284.90.1.rt14.375.el9_2"}]}],"bundled":14},{"source":"osv","ecosystem":"Red Hat:rhel_eus:9.2::nfv","package":"kernel-rt-core","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-284.90.1.rt14.375.el9_2"}]}],"bundled":14},{"source":"osv","ecosystem":"Red Hat:rhel_eus:9.2::nfv","package":"kernel-rt-debug","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-284.90.1.rt14.375.el9_2"}]}],"bundled":14},{"source":"osv","ecosystem":"Red Hat:rhel_eus:9.2::nfv","package":"kernel-rt-debug-core","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-284.90.1.rt14.375.el9_2"}]}],"bundled":14},{"source":"osv","ecosystem":"Red Hat:rhel_eus:9.2::nfv","package":"kernel-rt-debug-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-284.90.1.rt14.375.el9_2"}]}],"bundled":14},{"source":"osv","ecosystem":"Red Hat:rhel_eus:9.2::nfv","package":"kernel-rt-debug-devel","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-284.90.1.rt14.375.el9_2"}]}],"bundled":14},{"source":"osv","ecosystem":"Red Hat:rhel_eus:9.2::nfv","package":"kernel-rt-debug-kvm","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-284.90.1.rt14.375.el9_2"}]}],"bundled":14},{"source":"osv","ecosystem":"Red Hat:rhel_eus:9.2::nfv","package":"kernel-rt-debug-modules","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-284.90.1.rt14.375.el9_2"}]}],"bundled":14},{"source":"osv","ecosystem":"Red Hat:rhel_eus:9.2::nfv","package":"kernel-rt-debug-modules-core","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-284.90.1.rt14.375.el9_2"}]}],"bundled":14},{"source":"osv","ecosystem":"Red Hat:rhel_eus:9.2::nfv","package":"kernel-rt-debug-modules-extra","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-284.90.1.rt14.375.el9_2"}]}],"bundled":14},{"source":"osv","ecosystem":"Red Hat:rhel_eus:9.2::nfv","package":"kernel-rt-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-284.90.1.rt14.375.el9_2"}]}],"bundled":14},{"source":"osv","ecosystem":"Red Hat:rhel_eus:9.2::nfv","package":"kernel-rt-debuginfo-common-x86_64","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-284.90.1.rt14.375.el9_2"}]}],"bundled":14},{"source":"osv","ecosystem":"Red Hat:rhel_eus:9.2::nfv","package":"kernel-rt-devel","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-284.90.1.rt14.375.el9_2"}]}],"bundled":14},{"source":"osv","ecosystem":"Red Hat:rhel_eus:9.2::nfv","package":"kernel-rt-kvm","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-284.90.1.rt14.375.el9_2"}]}],"bundled":14},{"source":"osv","ecosystem":"Red Hat:rhel_eus:9.2::nfv","package":"kernel-rt-modules","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-284.90.1.rt14.375.el9_2"}]}],"bundled":14},{"source":"osv","ecosystem":"Red Hat:rhel_eus:9.2::nfv","package":"kernel-rt-modules-core","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-284.90.1.rt14.375.el9_2"}]}],"bundled":14},{"source":"osv","ecosystem":"Red Hat:rhel_eus:9.2::nfv","package":"kernel-rt-modules-extra","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-284.90.1.rt14.375.el9_2"}]}],"bundled":14},{"source":"osv","ecosystem":"Red Hat:rhel_eus:9.2::realtime","package":"kernel-rt","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-284.90.1.rt14.375.el9_2"}]}],"bundled":14},{"source":"osv","ecosystem":"Red Hat:rhel_eus:9.2::realtime","package":"kernel-rt-core","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-284.90.1.rt14.375.el9_2"}]}],"bundled":14},{"source":"osv","ecosystem":"Red Hat:rhel_eus:9.2::realtime","package":"kernel-rt-debug","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-284.90.1.rt14.375.el9_2"}]}],"bundled":14},{"source":"osv","ecosystem":"Red Hat:rhel_eus:9.2::realtime","package":"kernel-rt-debug-core","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-284.90.1.rt14.375.el9_2"}]}],"bundled":14},{"source":"osv","ecosystem":"Red Hat:rhel_eus:9.2::realtime","package":"kernel-rt-debug-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-284.90.1.rt14.375.el9_2"}]}],"bundled":14},{"source":"osv","ecosystem":"Red Hat:rhel_eus:9.2::realtime","package":"kernel-rt-debug-devel","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-284.90.1.rt14.375.el9_2"}]}],"bundled":14},{"source":"osv","ecosystem":"Red Hat:rhel_eus:9.2::realtime","package":"kernel-rt-debug-modules","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-284.90.1.rt14.375.el9_2"}]}],"bundled":14},{"source":"osv","ecosystem":"Red Hat:rhel_eus:9.2::realtime","package":"kernel-rt-debug-modules-core","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-284.90.1.rt14.375.el9_2"}]}],"bundled":14},{"source":"osv","ecosystem":"Red Hat:rhel_eus:9.2::realtime","package":"kernel-rt-debug-modules-extra","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-284.90.1.rt14.375.el9_2"}]}],"bundled":14},{"source":"osv","ecosystem":"Red Hat:rhel_eus:9.2::realtime","package":"kernel-rt-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-284.90.1.rt14.375.el9_2"}]}],"bundled":14},{"source":"osv","ecosystem":"Red Hat:rhel_eus:9.2::realtime","package":"kernel-rt-debuginfo-common-x86_64","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-284.90.1.rt14.375.el9_2"}]}],"bundled":14},{"source":"osv","ecosystem":"Red Hat:rhel_eus:9.2::realtime","package":"kernel-rt-devel","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-284.90.1.rt14.375.el9_2"}]}],"bundled":14},{"source":"osv","ecosystem":"Red Hat:rhel_eus:9.2::realtime","package":"kernel-rt-modules","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-284.90.1.rt14.375.el9_2"}]}],"bundled":14},{"source":"osv","ecosystem":"Red Hat:rhel_eus:9.2::realtime","package":"kernel-rt-modules-core","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-284.90.1.rt14.375.el9_2"}]}],"bundled":14},{"source":"osv","ecosystem":"Red Hat:rhel_eus:9.2::realtime","package":"kernel-rt-modules-extra","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-284.90.1.rt14.375.el9_2"}]}],"bundled":14},{"source":"osv","ecosystem":"Rocky Linux:8","package":"kernel","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:4.18.0-553.22.1.el8_10"}]}],"bundled":147},{"source":"osv","ecosystem":"Rocky Linux:8","package":"kernel-rt","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:4.18.0-553.22.1.rt7.363.el8_10"}]}],"bundled":129},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Module for Public Cloud 15 SP5","package":"kernel-azure","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.21-150500.33.66.1"}]}],"bundled":292},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Module for Public Cloud 15 SP5","package":"kernel-source-azure","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.21-150500.33.66.1"}]}],"bundled":292},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Module for Public Cloud 15 SP5","package":"kernel-syms-azure","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.21-150500.33.66.1"}]}],"bundled":292},{"source":"osv","ecosystem":"openSUSE:Leap 15.5","package":"kernel-azure","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.21-150500.33.66.1"}]}],"bundled":292},{"source":"osv","ecosystem":"openSUSE:Leap 15.5","package":"kernel-source-azure","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.21-150500.33.66.1"}]}],"bundled":292},{"source":"osv","ecosystem":"openSUSE:Leap 15.5","package":"kernel-syms-azure","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.21-150500.33.66.1"}]}],"bundled":292},{"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.11.1"}]}],"bundled":394},{"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.11.1"}]}],"bundled":394},{"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.11.1"}]}],"bundled":394},{"source":"osv","ecosystem":"openSUSE:Leap 15.6","package":"kernel-azure","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.4.0-150600.8.11.1"}]}],"bundled":394},{"source":"osv","ecosystem":"openSUSE:Leap 15.6","package":"kernel-source-azure","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.4.0-150600.8.11.1"}]}],"bundled":394},{"source":"osv","ecosystem":"openSUSE:Leap 15.6","package":"kernel-syms-azure","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.4.0-150600.8.11.1"}]}],"bundled":394},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Live Patching 15 SP6","package":"kernel-livepatch-SLE15-SP6-RT_Update_2","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1-150600.1.3.2"}]}],"bundled":393},{"source":"osv","ecosystem":"SUSE:Real Time Module 15 SP6","package":"kernel-rt","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.4.0-150600.10.8.3"}]}],"bundled":393},{"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.8.3"}]}],"bundled":393},{"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.8.3"}]}],"bundled":393},{"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.8.1"}]}],"bundled":393},{"source":"osv","ecosystem":"openSUSE:Leap 15.6","package":"kernel-rt","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.4.0-150600.10.8.3"}]}],"bundled":393},{"source":"osv","ecosystem":"openSUSE:Leap 15.6","package":"kernel-rt_debug","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.4.0-150600.10.8.3"}]}],"bundled":393},{"source":"osv","ecosystem":"openSUSE:Leap 15.6","package":"kernel-source-rt","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.4.0-150600.10.8.3"}]}],"bundled":393},{"source":"osv","ecosystem":"openSUSE:Leap 15.6","package":"kernel-syms-rt","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.4.0-150600.10.8.1"}]}],"bundled":393},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Micro 5.5","package":"kernel-rt","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.21-150500.13.67.3"}]}],"bundled":292},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Micro 5.5","package":"kernel-source-rt","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.21-150500.13.67.3"}]}],"bundled":292},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Live Patching 15 SP5","package":"kernel-livepatch-SLE15-SP5-RT_Update_19","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1-150500.11.3.2"}]}],"bundled":292},{"source":"osv","ecosystem":"SUSE:Real Time Module 15 SP5","package":"kernel-rt","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.21-150500.13.67.3"}]}],"bundled":292},{"source":"osv","ecosystem":"SUSE:Real Time Module 15 SP5","package":"kernel-rt_debug","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.21-150500.13.67.3"}]}],"bundled":292},{"source":"osv","ecosystem":"SUSE:Real Time Module 15 SP5","package":"kernel-source-rt","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.21-150500.13.67.3"}]}],"bundled":292},{"source":"osv","ecosystem":"SUSE:Real Time Module 15 SP5","package":"kernel-syms-rt","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.21-150500.13.67.1"}]}],"bundled":292},{"source":"osv","ecosystem":"openSUSE:Leap Micro 5.5","package":"kernel-rt","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.21-150500.13.67.3"}]}],"bundled":292},{"source":"osv","ecosystem":"openSUSE:Leap 15.5","package":"kernel-rt","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.21-150500.13.67.3"}]}],"bundled":292},{"source":"osv","ecosystem":"openSUSE:Leap 15.5","package":"kernel-rt_debug","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.21-150500.13.67.3"}]}],"bundled":292},{"source":"osv","ecosystem":"openSUSE:Leap 15.5","package":"kernel-source-rt","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.21-150500.13.67.3"}]}],"bundled":292},{"source":"osv","ecosystem":"openSUSE:Leap 15.5","package":"kernel-syms-rt","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.21-150500.13.67.1"}]}],"bundled":292},{"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.22.1"}]}],"bundled":394},{"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.22.1"}]}],"bundled":394},{"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.22.1.150600.12.8.3"}]}],"bundled":394},{"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.22.1"}]}],"bundled":394},{"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.22.1"}]}],"bundled":394},{"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.22.1"}]}],"bundled":394},{"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.22.1"}]}],"bundled":394},{"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.22.1"}]}],"bundled":394},{"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.22.1"}]}],"bundled":394},{"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.22.1"}]}],"bundled":394},{"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.22.1"}]}],"bundled":394},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Live Patching 15 SP6","package":"kernel-livepatch-SLE15-SP6_Update_4","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1-150600.13.3.3"}]}],"bundled":394},{"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.22.1"}]}],"bundled":394},{"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.22.1"}]}],"bundled":394},{"source":"osv","ecosystem":"openSUSE:Leap 15.6","package":"dtb-aarch64","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.4.0-150600.23.22.1"}]}],"bundled":394},{"source":"osv","ecosystem":"openSUSE:Leap 15.6","package":"kernel-64kb","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.4.0-150600.23.22.1"}]}],"bundled":394},{"source":"osv","ecosystem":"openSUSE:Leap 15.6","package":"kernel-debug","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.4.0-150600.23.22.1"}]}],"bundled":394},{"source":"osv","ecosystem":"openSUSE:Leap 15.6","package":"kernel-default","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.4.0-150600.23.22.1"}]}],"bundled":394},{"source":"osv","ecosystem":"openSUSE:Leap 15.6","package":"kernel-default-base","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.4.0-150600.23.22.1.150600.12.8.3"}]}],"bundled":394},{"source":"osv","ecosystem":"openSUSE:Leap 15.6","package":"kernel-docs","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.4.0-150600.23.22.1"}]}],"bundled":394},{"source":"osv","ecosystem":"openSUSE:Leap 15.6","package":"kernel-kvmsmall","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.4.0-150600.23.22.1"}]}],"bundled":394},{"source":"osv","ecosystem":"openSUSE:Leap 15.6","package":"kernel-obs-build","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.4.0-150600.23.22.1"}]}],"bundled":394},{"source":"osv","ecosystem":"openSUSE:Leap 15.6","package":"kernel-obs-qa","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.4.0-150600.23.22.1"}]}],"bundled":394},{"source":"osv","ecosystem":"openSUSE:Leap 15.6","package":"kernel-source","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.4.0-150600.23.22.1"}]}],"bundled":394},{"source":"osv","ecosystem":"openSUSE:Leap 15.6","package":"kernel-syms","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.4.0-150600.23.22.1"}]}],"bundled":394},{"source":"osv","ecosystem":"openSUSE:Leap 15.6","package":"kernel-zfcpdump","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.4.0-150600.23.22.1"}]}],"bundled":394},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Micro 5.5","package":"kernel-default","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.21-150500.55.80.2"}]}],"bundled":296},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Micro 5.5","package":"kernel-default-base","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.21-150500.55.80.2.150500.6.35.6"}]}],"bundled":296},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Module for Basesystem 15 SP5","package":"kernel-64kb","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.21-150500.55.80.2"}]}],"bundled":296},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Module for Basesystem 15 SP5","package":"kernel-default","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.21-150500.55.80.2"}]}],"bundled":296},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Module for Basesystem 15 SP5","package":"kernel-default-base","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.21-150500.55.80.2.150500.6.35.6"}]}],"bundled":296},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Module for Basesystem 15 SP5","package":"kernel-source","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.21-150500.55.80.2"}]}],"bundled":296},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Module for Basesystem 15 SP5","package":"kernel-zfcpdump","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.21-150500.55.80.2"}]}],"bundled":296},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Module for Development Tools 15 SP5","package":"kernel-docs","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.21-150500.55.80.2"}]}],"bundled":296},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Module for Development Tools 15 SP5","package":"kernel-obs-build","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.21-150500.55.80.1"}]}],"bundled":296},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Module for Development Tools 15 SP5","package":"kernel-source","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.21-150500.55.80.2"}]}],"bundled":296},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Module for Development Tools 15 SP5","package":"kernel-syms","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.21-150500.55.80.1"}]}],"bundled":296},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Module for Legacy 15 SP5","package":"kernel-default","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.21-150500.55.80.2"}]}],"bundled":296},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Live Patching 15 SP5","package":"kernel-default","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.21-150500.55.80.2"}]}],"bundled":296},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Live Patching 15 SP5","package":"kernel-livepatch-SLE15-SP5_Update_19","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1-150500.11.3.2"}]}],"bundled":296},{"source":"osv","ecosystem":"SUSE:Linux Enterprise High Availability Extension 15 SP5","package":"kernel-default","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.21-150500.55.80.2"}]}],"bundled":296},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Workstation Extension 15 SP5","package":"kernel-default","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.21-150500.55.80.2"}]}],"bundled":296},{"source":"osv","ecosystem":"openSUSE:Leap Micro 5.5","package":"kernel-default","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.21-150500.55.80.2"}]}],"bundled":296},{"source":"osv","ecosystem":"openSUSE:Leap Micro 5.5","package":"kernel-default-base","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.21-150500.55.80.2.150500.6.35.6"}]}],"bundled":296},{"source":"osv","ecosystem":"openSUSE:Leap 15.5","package":"dtb-aarch64","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.21-150500.55.80.1"}]}],"bundled":296},{"source":"osv","ecosystem":"openSUSE:Leap 15.5","package":"kernel-64kb","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.21-150500.55.80.2"}]}],"bundled":296},{"source":"osv","ecosystem":"openSUSE:Leap 15.5","package":"kernel-debug","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.21-150500.55.80.2"}]}],"bundled":296},{"source":"osv","ecosystem":"openSUSE:Leap 15.5","package":"kernel-default","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.21-150500.55.80.2"}]}],"bundled":296},{"source":"osv","ecosystem":"openSUSE:Leap 15.5","package":"kernel-default-base","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.21-150500.55.80.2.150500.6.35.6"}]}],"bundled":296},{"source":"osv","ecosystem":"openSUSE:Leap 15.5","package":"kernel-docs","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.21-150500.55.80.2"}]}],"bundled":296},{"source":"osv","ecosystem":"openSUSE:Leap 15.5","package":"kernel-kvmsmall","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.21-150500.55.80.2"}]}],"bundled":296},{"source":"osv","ecosystem":"openSUSE:Leap 15.5","package":"kernel-obs-build","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.21-150500.55.80.1"}]}],"bundled":296},{"source":"osv","ecosystem":"openSUSE:Leap 15.5","package":"kernel-obs-qa","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.21-150500.55.80.1"}]}],"bundled":296},{"source":"osv","ecosystem":"openSUSE:Leap 15.5","package":"kernel-source","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.21-150500.55.80.2"}]}],"bundled":296},{"source":"osv","ecosystem":"openSUSE:Leap 15.5","package":"kernel-syms","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.21-150500.55.80.1"}]}],"bundled":296},{"source":"osv","ecosystem":"openSUSE:Leap 15.5","package":"kernel-zfcpdump","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.21-150500.55.80.2"}]}],"bundled":296},{"source":"osv","ecosystem":"SUSE:Linux Micro 6.0","package":"kernel-default","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.4.0-19.1"}]}],"bundled":383},{"source":"osv","ecosystem":"SUSE:Linux Micro 6.0","package":"kernel-default-base","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.4.0-17.1.1.51"}]}],"bundled":383},{"source":"osv","ecosystem":"SUSE:Linux Micro 6.0","package":"kernel-kvmsmall","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.4.0-19.1"}]}],"bundled":383},{"source":"osv","ecosystem":"SUSE:Linux Micro 6.0","package":"kernel-livepatch-MICRO-6-0_Update_2","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1-1.1"}]}],"bundled":383},{"source":"osv","ecosystem":"SUSE:Linux Micro 6.0","package":"kernel-source","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.4.0-19.1"}]}],"bundled":383},{"source":"osv","ecosystem":"SUSE:Linux Micro 6.0","package":"kernel-livepatch-MICRO-6-0-RT_Update_2","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1-1.1"}]}],"bundled":383},{"source":"osv","ecosystem":"SUSE:Linux Micro 6.0","package":"kernel-rt","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.4.0-10.1"}]}],"bundled":383},{"source":"osv","ecosystem":"SUSE:Linux Micro 6.0","package":"kernel-source-rt","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.4.0-10.1"}]}],"bundled":383},{"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.15","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-1069.75~20.04.1"}]}],"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"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-azure-5.15","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-1072.81~20.04.1"}]}],"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"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-gcp-5.15","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-1068.76~20.04.1"}]}],"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"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-gkeop-5.15","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-1052.59~20.04.1"}]}],"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"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-hwe-5.15","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-121.131~20.04.1"}]}],"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"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-ibm-5.15","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-1062.65~20.04.1"}]}],"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"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-intel-iotg-5.15","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-1064.70~20.04.1"}]}],"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"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-lowlatency-hwe-5.15","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-121.131~20.04.1"}]}],"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"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-nvidia-tegra-5.15","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-1030.30~20.04.1"}]}],"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"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-oracle-5.15","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-1067.73~20.04.1"}]}],"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"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-riscv-5.15","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-1065.69~20.04.1"}]}],"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"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-aws-5.11","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.11.0-1009.9~20.04.2","5.11.0-1014.15~20.04.1","5.11.0-1016.17~20.04.1","5.11.0-1017.18~20.04.1","5.11.0-1019.20~20.04.1","5.11.0-1020.21~20.04.2","5.11.0-1021.22~20.04.2","5.11.0-1022.23~20.04.1","5.11.0-1023.24~20.04.1","5.11.0-1025.27~20.04.1","5.11.0-1027.30~20.04.1","5.11.0-1028.31~20.04.1"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-aws-5.13","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.13.0-1008.9~20.04.2","5.13.0-1011.12~20.04.1","5.13.0-1012.13~20.04.1","5.13.0-1014.15~20.04.1","5.13.0-1017.19~20.04.1","5.13.0-1019.21~20.04.1","5.13.0-1021.23~20.04.2","5.13.0-1022.24~20.04.1","5.13.0-1023.25~20.04.1","5.13.0-1025.27~20.04.1","5.13.0-1028.31~20.04.1","5.13.0-1029.32~20.04.1","5.13.0-1031.35~20.04.1"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-aws-5.8","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.8.0-1035.37~20.04.1","5.8.0-1038.40~20.04.1","5.8.0-1041.43~20.04.1","5.8.0-1042.44~20.04.1"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-azure-5.11","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.11.0-1007.7~20.04.2","5.11.0-1012.13~20.04.1","5.11.0-1013.14~20.04.1","5.11.0-1015.16~20.04.1","5.11.0-1017.18~20.04.1","5.11.0-1019.20~20.04.1","5.11.0-1020.21~20.04.1","5.11.0-1021.22~20.04.1","5.11.0-1022.23~20.04.1","5.11.0-1023.24~20.04.1","5.11.0-1025.27~20.04.1","5.11.0-1027.30~20.04.1","5.11.0-1028.31~20.04.2"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-azure-5.13","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.13.0-1009.10~20.04.2","5.13.0-1012.14~20.04.1","5.13.0-1013.15~20.04.1","5.13.0-1014.16~20.04.1","5.13.0-1017.19~20.04.1","5.13.0-1021.24~20.04.1","5.13.0-1022.26~20.04.1","5.13.0-1023.27~20.04.1","5.13.0-1025.29~20.04.1","5.13.0-1028.33~20.04.1","5.13.0-1029.34~20.04.1","5.13.0-1031.37~20.04.1"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-azure-5.8","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.8.0-1033.35~20.04.1","5.8.0-1036.38~20.04.1","5.8.0-1039.42~20.04.1","5.8.0-1040.43~20.04.1","5.8.0-1041.44~20.04.1","5.8.0-1042.45~20.04.1","5.8.0-1043.46~20.04.1"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-azure-fde","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.4.0-1063.66+cvm2.2","5.4.0-1063.66+cvm3.2","5.4.0-1064.67+cvm1.1","5.4.0-1065.68+cvm2.1","5.4.0-1067.70+cvm1.1","5.4.0-1068.71+cvm1.1","5.4.0-1069.72+cvm1.1","5.4.0-1070.73+cvm1.1","5.4.0-1072.75+cvm1.1","5.4.0-1073.76+cvm1.1","5.4.0-1074.77+cvm1.1","5.4.0-1076.79+cvm1.1","5.4.0-1078.81+cvm1.1","5.4.0-1080.83+cvm1.1","5.4.0-1083.87+cvm1.1","5.4.0-1085.90+cvm1.1","5.4.0-1085.90+cvm2.1","5.4.0-1086.91+cvm1.1","5.4.0-1089.94+cvm1.2","5.4.0-1090.95+cvm1.1","5.4.0-1091.96+cvm1.1","5.4.0-1092.97+cvm1.1","5.4.0-1095.101+cvm1.1","5.4.0-1098.104+cvm1.1","5.4.0-1100.106+cvm1.1","5.4.0-1103.109+cvm1.1"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-gcp-5.11","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.11.0-1009.10~20.04.1","5.11.0-1014.16~20.04.1","5.11.0-1017.19~20.04.1","5.11.0-1018.20~20.04.2","5.11.0-1020.22~20.04.1","5.11.0-1021.23~20.04.1","5.11.0-1022.24~20.04.1","5.11.0-1023.25~20.04.1","5.11.0-1024.26~20.04.1","5.11.0-1026.29~20.04.1","5.11.0-1028.32~20.04.1","5.11.0-1029.33~20.04.3"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-gcp-5.13","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.13.0-1008.9~20.04.3","5.13.0-1012.15~20.04.1","5.13.0-1013.16~20.04.1","5.13.0-1015.18~20.04.1","5.13.0-1019.23~20.04.1","5.13.0-1021.25~20.04.1","5.13.0-1023.28~20.04.1","5.13.0-1024.29~20.04.1","5.13.0-1025.30~20.04.1","5.13.0-1027.32~20.04.1","5.13.0-1030.36~20.04.1","5.13.0-1031.37~20.04.1","5.13.0-1033.40~20.04.1"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-gcp-5.8","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.8.0-1032.34~20.04.1","5.8.0-1035.37~20.04.1","5.8.0-1038.40~20.04.1","5.8.0-1039.41"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-gke","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.4.0-1033.35","5.4.0-1035.37","5.4.0-1036.38","5.4.0-1037.39","5.4.0-1039.41","5.4.0-1041.43","5.4.0-1042.44","5.4.0-1043.45","5.4.0-1044.46","5.4.0-1046.48","5.4.0-1049.52","5.4.0-1051.54","5.4.0-1052.55","5.4.0-1053.56","5.4.0-1054.57","5.4.0-1055.58","5.4.0-1056.59","5.4.0-1057.60","5.4.0-1059.62","5.4.0-1061.64","5.4.0-1062.65","5.4.0-1063.66","5.4.0-1065.68","5.4.0-1066.69","5.4.0-1067.70","5.4.0-1068.71","5.4.0-1071.76","5.4.0-1072.77","5.4.0-1074.79","5.4.0-1076.82","5.4.0-1078.84","5.4.0-1080.86","5.4.0-1081.87","5.4.0-1083.89","5.4.0-1084.90","5.4.0-1086.93","5.4.0-1087.94","5.4.0-1090.97","5.4.0-1091.98","5.4.0-1094.101","5.4.0-1095.102","5.4.0-1096.103","5.4.0-1097.104","5.4.0-1098.105","5.4.0-1099.106","5.4.0-1100.107","5.4.0-1101.108","5.4.0-1102.109","5.4.0-1103.110","5.4.0-1104.111","5.4.0-1105.112"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-gke-5.15","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.15.0-1011.14~20.04.1","5.15.0-1014.17~20.04.1","5.15.0-1015.18~20.04.1","5.15.0-1016.19~20.04.1","5.15.0-1019.23~20.04.1","5.15.0-1020.25~20.04.1","5.15.0-1023.28~20.04.2","5.15.0-1027.32~20.04.1","5.15.0-1028.33~20.04.1","5.15.0-1029.34~20.04.1","5.15.0-1031.36~20.04.1","5.15.0-1032.37~20.04.1","5.15.0-1033.38~20.04.1","5.15.0-1034.39~20.04.1","5.15.0-1036.41~20.04.1","5.15.0-1037.42~20.04.1","5.15.0-1038.43~20.04.1","5.15.0-1039.44~20.04.1"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-gkeop","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.4.0-1008.9","5.4.0-1009.10","5.4.0-1010.11","5.4.0-1011.12","5.4.0-1012.13","5.4.0-1013.14","5.4.0-1014.15","5.4.0-1015.16","5.4.0-1016.17","5.4.0-1018.19","5.4.0-1021.22","5.4.0-1022.23","5.4.0-1023.24","5.4.0-1024.25","5.4.0-1025.26","5.4.0-1026.27","5.4.0-1027.28","5.4.0-1029.30","5.4.0-1031.32","5.4.0-1032.33","5.4.0-1033.34","5.4.0-1034.35","5.4.0-1036.37","5.4.0-1037.38","5.4.0-1038.39","5.4.0-1039.40","5.4.0-1040.41","5.4.0-1043.44","5.4.0-1046.48","5.4.0-1048.51","5.4.0-1049.52","5.4.0-1051.54","5.4.0-1052.55","5.4.0-1053.56","5.4.0-1054.57","5.4.0-1056.60","5.4.0-1057.61","5.4.0-1060.64","5.4.0-1061.65","5.4.0-1062.66","5.4.0-1064.68","5.4.0-1065.69","5.4.0-1066.70","5.4.0-1067.71","5.4.0-1068.72","5.4.0-1069.73","5.4.0-1070.74","5.4.0-1071.75","5.4.0-1072.76","5.4.0-1073.77","5.4.0-1074.78","5.4.0-1075.79","5.4.0-1076.80","5.4.0-1077.81","5.4.0-1078.82","5.4.0-1079.83","5.4.0-1080.84","5.4.0-1081.85","5.4.0-1083.87","5.4.0-1084.88","5.4.0-1085.89","5.4.0-1086.90","5.4.0-1087.91","5.4.0-1088.92","5.4.0-1089.93","5.4.0-1090.94","5.4.0-1091.95","5.4.0-1092.96","5.4.0-1093.97","5.4.0-1094.98","5.4.0-1095.99","5.4.0-1096.100","5.4.0-1097.101","5.4.0-1098.102","5.4.0-1099.103","5.4.0-1100.104","5.4.0-1101.105","5.4.0-1102.106"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-hwe-5.11","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.11.0-22.23~20.04.1","5.11.0-25.27~20.04.1","5.11.0-27.29~20.04.1","5.11.0-34.36~20.04.1","5.11.0-36.40~20.04.1","5.11.0-37.41~20.04.2","5.11.0-38.42~20.04.1","5.11.0-40.44~20.04.2","5.11.0-41.45~20.04.1","5.11.0-43.47~20.04.2","5.11.0-44.48~20.04.2","5.11.0-46.51~20.04.1"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-hwe-5.13","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.13.0-21.21~20.04.1","5.13.0-22.22~20.04.1","5.13.0-23.23~20.04.2","5.13.0-25.26~20.04.1","5.13.0-27.29~20.04.1","5.13.0-28.31~20.04.1","5.13.0-30.33~20.04.1","5.13.0-35.40~20.04.1","5.13.0-37.42~20.04.1","5.13.0-39.44~20.04.1","5.13.0-40.45~20.04.1","5.13.0-41.46~20.04.1","5.13.0-44.49~20.04.1","5.13.0-48.54~20.04.1","5.13.0-51.58~20.04.1","5.13.0-52.59~20.04.1"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-hwe-5.8","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.8.0-23.24~20.04.1","5.8.0-25.26~20.04.1","5.8.0-28.30~20.04.1","5.8.0-29.31~20.04.1","5.8.0-31.33~20.04.1","5.8.0-33.36~20.04.1","5.8.0-34.37~20.04.2","5.8.0-36.40~20.04.1","5.8.0-38.43~20.04.1","5.8.0-40.45~20.04.1","5.8.0-41.46~20.04.1","5.8.0-43.49~20.04.1","5.8.0-44.50~20.04.1","5.8.0-45.51~20.04.1","5.8.0-48.54~20.04.1","5.8.0-49.55~20.04.1","5.8.0-50.56~20.04.1","5.8.0-53.60~20.04.1","5.8.0-55.62~20.04.1","5.8.0-59.66~20.04.1","5.8.0-63.71~20.04.1"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-intel-5.13","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.13.0-1007.7","5.13.0-1008.8","5.13.0-1009.9","5.13.0-1010.10","5.13.0-1011.11","5.13.0-1014.15","5.13.0-1017.19"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-oem-5.10","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.10.0-1008.9","5.10.0-1011.12","5.10.0-1013.14","5.10.0-1014.15","5.10.0-1016.17","5.10.0-1017.18","5.10.0-1019.20","5.10.0-1021.22","5.10.0-1022.23","5.10.0-1023.24","5.10.0-1025.26","5.10.0-1026.27","5.10.0-1029.30","5.10.0-1032.33","5.10.0-1033.34","5.10.0-1034.35","5.10.0-1038.40","5.10.0-1044.46","5.10.0-1045.47","5.10.0-1049.51","5.10.0-1050.52","5.10.0-1051.53","5.10.0-1052.54","5.10.0-1053.55","5.10.0-1055.58","5.10.0-1057.61"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-oem-5.13","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.13.0-1009.10","5.13.0-1010.11","5.13.0-1012.16","5.13.0-1014.18","5.13.0-1017.21","5.13.0-1019.23","5.13.0-1020.24","5.13.0-1021.25","5.13.0-1022.26","5.13.0-1026.32","5.13.0-1028.35","5.13.0-1029.36"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-oem-5.14","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.14.0-1004.4","5.14.0-1005.5","5.14.0-1007.7","5.14.0-1008.8","5.14.0-1010.10","5.14.0-1011.11","5.14.0-1013.13","5.14.0-1018.19","5.14.0-1020.22","5.14.0-1022.24","5.14.0-1024.26","5.14.0-1027.30","5.14.0-1029.32","5.14.0-1031.34","5.14.0-1032.35","5.14.0-1033.36","5.14.0-1034.37","5.14.0-1036.40","5.14.0-1038.42","5.14.0-1042.47","5.14.0-1044.49","5.14.0-1045.51","5.14.0-1046.53","5.14.0-1047.54","5.14.0-1048.55","5.14.0-1049.56","5.14.0-1050.57","5.14.0-1051.58","5.14.0-1052.59","5.14.0-1054.61","5.14.0-1055.62","5.14.0-1056.63","5.14.0-1057.64","5.14.0-1058.66","5.14.0-1059.67"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-oem-5.6","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.6.0-1007.7","5.6.0-1008.8","5.6.0-1010.10","5.6.0-1011.11","5.6.0-1013.13","5.6.0-1017.17","5.6.0-1018.18","5.6.0-1020.20","5.6.0-1021.21","5.6.0-1023.23","5.6.0-1026.26","5.6.0-1027.27","5.6.0-1028.28","5.6.0-1031.32","5.6.0-1032.33","5.6.0-1033.35","5.6.0-1034.36","5.6.0-1035.37","5.6.0-1036.39","5.6.0-1039.43","5.6.0-1042.46","5.6.0-1047.51","5.6.0-1048.52","5.6.0-1050.54","5.6.0-1052.56","5.6.0-1053.57","5.6.0-1054.58","5.6.0-1055.59","5.6.0-1056.60"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-oracle-5.11","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.11.0-1008.8~20.04.1","5.11.0-1013.14~20.04.1","5.11.0-1016.17~20.04.1","5.11.0-1017.18~20.04.1","5.11.0-1019.20~20.04.1","5.11.0-1020.21~20.04.1","5.11.0-1021.22~20.04.1","5.11.0-1022.23~20.04.1","5.11.0-1023.24~20.04.1","5.11.0-1025.27~20.04.1","5.11.0-1027.30~20.04.1","5.11.0-1028.31~20.04.1"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-oracle-5.13","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.13.0-1011.13~20.04.2","5.13.0-1015.19~20.04.1","5.13.0-1016.20~20.04.1","5.13.0-1018.22~20.04.1","5.13.0-1021.26~20.04.1","5.13.0-1025.30~20.04.1","5.13.0-1027.32~20.04.1","5.13.0-1028.33~20.04.1","5.13.0-1030.35~20.04.1","5.13.0-1033.39~20.04.1","5.13.0-1034.40~20.04.1","5.13.0-1036.43~20.04.1"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-oracle-5.8","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.8.0-1031.32~20.04.2","5.8.0-1033.34~20.04.1","5.8.0-1034.35~20.04.2","5.8.0-1037.38~20.04.1","5.8.0-1038.39~20.04.1"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-raspi2","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.3.0-1007.8","5.3.0-1014.16","5.3.0-1015.17","5.3.0-1017.19","5.4.0-1004.4","5.4.0-1006.6"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-riscv","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.4.0-24.28","5.4.0-26.30","5.4.0-27.31","5.4.0-28.32","5.4.0-30.34","5.4.0-31.35","5.4.0-33.37","5.4.0-34.38","5.4.0-36.41","5.4.0-37.42","5.4.0-39.44","5.4.0-40.45"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-riscv-5.11","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.11.0-1015.16~20.04.1","5.11.0-1017.18~20.04.1","5.11.0-1018.19~20.04.2","5.11.0-1020.21~20.04.1","5.11.0-1021.22~20.04.1","5.11.0-1022.23~20.04.1","5.11.0-1023.24~20.04.1","5.11.0-1024.25~20.04.1","5.11.0-1026.28~20.04.1","5.11.0-1028.31~20.04.1","5.11.0-1029.32~20.04.1","5.11.0-1030.34","5.11.0-1031.35"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-riscv-5.8","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.8.0-14.16~20.04.1","5.8.0-14.16~20.04.3","5.8.0-16.18~20.04.1","5.8.0-17.19~20.04.1","5.8.0-18.20~20.04.1","5.8.0-20.22~20.04.1","5.8.0-22.24~20.04.1","5.8.0-25.27~20.04.1","5.8.0-26.28~20.04.1","5.8.0-29.31~20.04.1"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-121.131"}]}],"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"]},{"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"},{"fixed":"5.15.0-1069.75"}]}],"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"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-aws-5.19","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.19.0-1019.20~22.04.1","5.19.0-1020.21~22.04.1","5.19.0-1022.23~22.04.1","5.19.0-1023.24~22.04.1","5.19.0-1024.25~22.04.1","5.19.0-1025.26~22.04.1","5.19.0-1026.27~22.04.1","5.19.0-1027.28~22.04.1","5.19.0-1028.29~22.04.1","5.19.0-1029.30~22.04.1"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-aws-6.2","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["6.2.0-1005.5~22.04.1","6.2.0-1006.6~22.04.1","6.2.0-1007.7~22.04.1","6.2.0-1008.8~22.04.1","6.2.0-1009.9~22.04.3","6.2.0-1010.10~22.04.1","6.2.0-1011.11~22.04.1","6.2.0-1012.12~22.04.1","6.2.0-1013.13~22.04.1","6.2.0-1014.14~22.04.1","6.2.0-1015.15~22.04.1","6.2.0-1016.16~22.04.1","6.2.0-1017.17~22.04.1","6.2.0-1018.18~22.04.1"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-aws-6.5","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["6.5.0-1008.8~22.04.1","6.5.0-1010.10~22.04.1","6.5.0-1011.11~22.04.1","6.5.0-1012.12~22.04.1","6.5.0-1014.14~22.04.1","6.5.0-1015.15~22.04.1","6.5.0-1016.16~22.04.1","6.5.0-1017.17~22.04.2","6.5.0-1018.18~22.04.1","6.5.0-1020.20~22.04.1","6.5.0-1021.21~22.04.1","6.5.0-1022.22~22.04.1","6.5.0-1023.23~22.04.1","6.5.0-1024.24~22.04.1"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-aws-6.8","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1018.19~22.04.1"}]}],"versions":["6.8.0-1009.9~22.04.2","6.8.0-1010.10~22.04.2","6.8.0-1011.12~22.04.1","6.8.0-1013.14~22.04.1","6.8.0-1014.15~22.04.1","6.8.0-1015.16~22.04.1","6.8.0-1016.17~22.04.2","6.8.0-1017.18~22.04.1"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-azure","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-1072.81"}]}],"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"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-azure-5.19","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.19.0-1020.21~22.04.1","5.19.0-1021.22~22.04.1","5.19.0-1022.23~22.04.1","5.19.0-1023.24~22.04.1","5.19.0-1025.28~22.04.1","5.19.0-1026.29~22.04.1","5.19.0-1027.30~22.04.2"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-azure-6.2","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["6.2.0-1005.5~22.04.1","6.2.0-1006.6~22.04.1","6.2.0-1007.7~22.04.1","6.2.0-1008.8~22.04.1","6.2.0-1009.9~22.04.3","6.2.0-1011.11~22.04.1","6.2.0-1012.12~22.04.1","6.2.0-1014.14~22.04.1","6.2.0-1015.15~22.04.1","6.2.0-1016.16~22.04.1","6.2.0-1017.17~22.04.1","6.2.0-1018.18~22.04.1","6.2.0-1019.19~22.04.1"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-azure-6.5","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["6.5.0-1007.7~22.04.1","6.5.0-1009.9~22.04.1","6.5.0-1010.10~22.04.1","6.5.0-1011.11~22.04.1","6.5.0-1015.15~22.04.1","6.5.0-1016.16~22.04.1","6.5.0-1017.17~22.04.1","6.5.0-1018.19~22.04.2","6.5.0-1019.20~22.04.1","6.5.0-1021.22~22.04.1","6.5.0-1022.23~22.04.1","6.5.0-1023.24~22.04.1","6.5.0-1024.25~22.04.1","6.5.0-1025.26~22.04.1"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-azure-6.8","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1017.20~22.04.1"}]}],"versions":["6.8.0-1008.8~22.04.1","6.8.0-1009.9~22.04.1","6.8.0-1010.10~22.04.1","6.8.0-1012.14~22.04.1","6.8.0-1013.15~22.04.1","6.8.0-1014.16~22.04.1","6.8.0-1015.17~22.04.2"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-azure-fde","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-1072.81.1"}]}],"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"]},{"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"},{"fixed":"5.15.0-1068.76"}]}],"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"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-gcp-5.19","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.19.0-1020.22~22.04.2","5.19.0-1021.23~22.04.1","5.19.0-1022.24~22.04.1","5.19.0-1024.26~22.04.1","5.19.0-1025.27~22.04.1","5.19.0-1026.28~22.04.1","5.19.0-1027.29~22.04.1","5.19.0-1030.32~22.04.1"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-gcp-6.2","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["6.2.0-1009.9~22.04.3","6.2.0-1010.10~22.04.1","6.2.0-1011.11~22.04.1","6.2.0-1011.11~22.04.3","6.2.0-1012.12~22.04.1","6.2.0-1013.13~22.04.1","6.2.0-1014.14~22.04.1","6.2.0-1016.18~22.04.1","6.2.0-1017.19~22.04.1","6.2.0-1018.20~22.04.1","6.2.0-1019.21~22.04.1","6.2.0-1021.23~22.04.1"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-gcp-6.5","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["6.5.0-1010.10~22.04.3","6.5.0-1011.11~22.04.1","6.5.0-1013.13~22.04.1","6.5.0-1014.14~22.04.1","6.5.0-1015.15~22.04.1","6.5.0-1016.16~22.04.1","6.5.0-1017.17~22.04.1","6.5.0-1018.18~22.04.1","6.5.0-1020.20~22.04.1","6.5.0-1022.24~22.04.1","6.5.0-1023.25~22.04.1","6.5.0-1024.26~22.04.1","6.5.0-1025.27~22.04.1"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-gcp-6.8","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1017.19~22.04.1"}]}],"versions":["6.8.0-1010.11~22.04.1","6.8.0-1011.12~22.04.1","6.8.0-1012.13~22.04.1","6.8.0-1013.14~22.04.1","6.8.0-1014.16~22.04.1","6.8.0-1015.17~22.04.1","6.8.0-1016.18~22.04.1"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-gke","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-1066.72"}]}],"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"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-gkeop","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-1052.59"}]}],"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"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-hwe-5.19","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.19.0-28.29~22.04.1","5.19.0-32.33~22.04.1","5.19.0-35.36~22.04.1","5.19.0-38.39~22.04.1","5.19.0-40.41~22.04.1","5.19.0-41.42~22.04.1","5.19.0-42.43~22.04.1","5.19.0-43.44~22.04.1","5.19.0-45.46~22.04.1","5.19.0-46.47~22.04.1","5.19.0-50.50"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-hwe-6.2","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["6.2.0-25.25~22.04.2","6.2.0-26.26~22.04.1","6.2.0-31.31~22.04.1","6.2.0-32.32~22.04.1","6.2.0-33.33~22.04.1","6.2.0-34.34~22.04.1","6.2.0-35.35~22.04.1","6.2.0-36.37~22.04.1","6.2.0-37.38~22.04.1","6.2.0-39.40~22.04.1"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-hwe-6.5","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["6.5.0-14.14~22.04.1","6.5.0-15.15~22.04.1","6.5.0-17.17~22.04.1","6.5.0-18.18~22.04.1","6.5.0-21.21~22.04.1","6.5.0-25.25~22.04.1","6.5.0-26.26~22.04.1","6.5.0-27.28~22.04.1","6.5.0-28.29~22.04.1","6.5.0-35.35~22.04.1","6.5.0-41.41~22.04.2","6.5.0-44.44~22.04.1","6.5.0-45.45~22.04.1"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-hwe-6.8","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-48.48~22.04.1"}]}],"versions":["6.8.0-38.38~22.04.1","6.8.0-39.39~22.04.1","6.8.0-40.40~22.04.3","6.8.0-45.45~22.04.1","6.8.0-47.47~22.04.1"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-ibm","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-1062.65"}]}],"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"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-ibm-6.8","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1015.15~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"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-intel-iotg","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-1064.70"}]}],"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"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-kvm","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-1066.71"}]}],"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"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-lowlatency","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-121.131"}]}],"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"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-lowlatency-hwe-5.19","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.19.0-1017.18~22.04.1","5.19.0-1018.19~22.04.1","5.19.0-1021.22~22.04.1","5.19.0-1022.23~22.04.1","5.19.0-1023.24~22.04.1","5.19.0-1024.25~22.04.1","5.19.0-1025.26~22.04.1","5.19.0-1027.28~22.04.1","5.19.0-1028.29~22.04.1","5.19.0-1030.30"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-lowlatency-hwe-6.2","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["6.2.0-1008.8~22.04.1","6.2.0-1009.9~22.04.1","6.2.0-1011.11~22.04.1","6.2.0-1012.12~22.04.1","6.2.0-1013.13~22.04.1","6.2.0-1014.14~22.04.1","6.2.0-1015.15~22.04.1","6.2.0-1016.16~22.04.1","6.2.0-1017.17~22.04.1","6.2.0-1018.18~22.04.1"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-lowlatency-hwe-6.5","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["6.5.0-14.14.1~22.04.1","6.5.0-15.15.1.1~22.04.1","6.5.0-17.17.1.1.1~22.04.1","6.5.0-21.21.1~22.04.1","6.5.0-25.25.1~22.04.1","6.5.0-26.26.1~22.04.1","6.5.0-27.28.1~22.04.1","6.5.0-28.29.1~22.04.1","6.5.0-35.35.1~22.04.1","6.5.0-41.41.1~22.04.1","6.5.0-42.42.1~22.04.1","6.5.0-44.44.1~22.04.1","6.5.0-45.45.1~22.04.1"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-lowlatency-hwe-6.8","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-48.48.3~22.04.1"}]}],"versions":["6.8.0-38.38.1~22.04.2","6.8.0-40.40.1~22.04.1","6.8.0-44.44.1~22.04.1","6.8.0-45.45.1~22.04.1","6.8.0-47.47.1~22.04.1"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-nvidia","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-1064.65"}]}],"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"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-nvidia-6.2","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["6.2.0-1003.3~22.04.1","6.2.0-1009.9","6.2.0-1010.10","6.2.0-1011.11","6.2.0-1012.12","6.2.0-1013.13","6.2.0-1015.15"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-nvidia-6.5","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["6.5.0-1004.4","6.5.0-1007.7","6.5.0-1013.13","6.5.0-1014.14","6.5.0-1015.15","6.5.0-1018.18","6.5.0-1019.19","6.5.0-1021.22","6.5.0-1022.23","6.5.0-1023.24","6.5.0-1024.25"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-nvidia-6.8","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1017.19~22.04.1"}]}],"versions":["6.8.0-1008.8~22.04.1","6.8.0-1009.9~22.04.1","6.8.0-1010.10~22.04.1","6.8.0-1011.11~22.04.1","6.8.0-1012.12~22.04.1","6.8.0-1013.14~22.04.1","6.8.0-1014.15~22.04.1","6.8.0-1015.16~22.04.1"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-nvidia-tegra","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-1028.28"}]}],"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"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-nvidia-tegra-igx","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-1016.16"}]}],"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"]},{"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"},{"fixed":"5.15.0-1067.73"}]}],"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"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-oracle-6.5","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["6.5.0-1013.13~22.04.4","6.5.0-1014.14~22.04.1","6.5.0-1015.15~22.04.1","6.5.0-1016.16~22.04.1","6.5.0-1018.18~22.04.1","6.5.0-1019.19~22.04.1","6.5.0-1020.20~22.04.1","6.5.0-1021.21~22.04.1","6.5.0-1023.23~22.04.1","6.5.0-1024.24~22.04.1","6.5.0-1025.25~22.04.1","6.5.0-1026.26~22.04.1","6.5.0-1027.27~22.04.1"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-oracle-6.8","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1015.15~22.04.1"}]}],"versions":["6.8.0-1006.6~22.04.3","6.8.0-1008.8~22.04.1","6.8.0-1010.10~22.04.1","6.8.0-1011.11~22.04.1","6.8.0-1012.12~22.04.1","6.8.0-1013.13~22.04.1","6.8.0-1014.14~22.04.1"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-raspi","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-1062.65"}]}],"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"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-realtime","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.15.0-1032.35"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-riscv","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.13.0-1004.4","5.13.0-1006.6+22.04.1","5.13.0-1007.7+22.04.1","5.13.0-1010.11+22.04.1","5.15.0-1004.4","5.15.0-1005.5","5.15.0-1006.6","5.15.0-1007.7","5.15.0-1008.8","5.15.0-1011.12","5.15.0-1012.13","5.15.0-1014.16","5.15.0-1015.17","5.15.0-1016.18","5.15.0-1017.19","5.15.0-1018.21","5.15.0-1019.22","5.15.0-1020.23","5.15.0-1022.26","5.15.0-1023.27","5.15.0-1026.30","5.15.0-1027.31","5.15.0-1028.32"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-riscv-5.19","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.19.0-1012.13~22.04.1","5.19.0-1015.16~22.04.1","5.19.0-1016.17~22.04.1","5.19.0-1017.18~22.04.1","5.19.0-1018.19~22.04.1","5.19.0-1019.21~22.04.1","5.19.0-1020.22~22.04.1","5.19.0-1021.23~22.04.1"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-riscv-6.5","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["6.5.0-17.17.1.1~22.04.1","6.5.0-21.21.1~22.04.1","6.5.0-25.25.1~22.04.1","6.5.0-26.26.1~22.04.1","6.5.0-27.28.1~22.04.1","6.5.0-28.29.1~22.04.1","6.5.0-35.35.1~22.04.1","6.5.0-40.40.1~22.04.1","6.5.0-42.42.1~22.04.1","6.5.0-45.45.1~22.04.1"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-riscv-6.8","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-48.48.1~22.04.2"}]}],"versions":["6.8.0-38.38.1~22.04.1","6.8.0-39.39.1~22.04.1","6.8.0-40.40.1~22.04.1","6.8.0-41.41.1~22.04.1","6.8.0-44.44.1~22.04.1","6.8.0-47.47.1~22.04.1"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-starfive-5.19","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.19.0-1014.16~22.04.1","5.19.0-1015.17~22.04.1","5.19.0-1016.18~22.04.1","5.19.0-1017.19~22.04.1","5.19.0-1018.20~22.04.1","5.19.0-1019.21~22.04.1","5.19.0-1020.22~22.04.1"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-starfive-6.2","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["6.2.0-1006.7~22.04.1","6.2.0-1007.8~22.04.1","6.2.0-1009.10~22.04.1"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-starfive-6.5","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["6.5.0-1007.8~22.04.1","6.5.0-1008.9~22.04.1","6.5.0-1009.10~22.04.1","6.5.0-1010.11~22.04.1","6.5.0-1011.12~22.04.1","6.5.0-1012.13~22.04.1","6.5.0-1014.15~22.04.1","6.5.0-1015.16~22.04.1","6.5.0-1016.17~22.04.1","6.5.0-1017.18~22.04.1","6.5.0-1018.19~22.04.1"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-xilinx-zynqmp","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-1035.39"}]}],"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"]},{"source":"osv","ecosystem":"Ubuntu:Nvidia-BlueField:22.04:LTS","package":"linux-bluefield","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-1052.54"}]}],"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"]},{"source":"osv","ecosystem":"Ubuntu:Pro:Realtime:22.04:LTS","package":"linux-intel-iot-realtime","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-1063.65"}]}],"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"]},{"source":"osv","ecosystem":"Ubuntu:Pro:Realtime:22.04:LTS","package":"linux-realtime","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-1070.78"}]}],"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"]},{"source":"osv","ecosystem":"Ubuntu:Pro:Realtime:22.04:LTS","package":"linux-realtime-6.8","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.1-1011.11~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"]},{"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"},{"fixed":"5.15.0-1069.75+fips1"}]}],"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"]},{"source":"osv","ecosystem":"Ubuntu:Pro:FIPS-updates:22.04:LTS","package":"linux-azure-fips","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-1072.81+fips1"}]}],"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"]},{"source":"osv","ecosystem":"Ubuntu:Pro:FIPS-updates:22.04:LTS","package":"linux-fips","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-121.131+fips1"}]}],"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"]},{"source":"osv","ecosystem":"Ubuntu:Pro:FIPS-updates:22.04:LTS","package":"linux-gcp-fips","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-1068.76+fips1"}]}],"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"]},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-48.48"}]}],"versions":["6.5.0-9.9","6.6.0-14.14","6.8.0-11.11","6.8.0-20.20","6.8.0-22.22","6.8.0-28.28","6.8.0-31.31","6.8.0-35.35","6.8.0-36.36","6.8.0-38.38","6.8.0-39.39","6.8.0-40.40","6.8.0-41.41","6.8.0-44.44","6.8.0-45.45","6.8.0-47.47"]},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-aws","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1018.20"}]}],"versions":["6.5.0-1008.8","6.6.0-1001.1","6.8.0-1001.1","6.8.0-1006.6","6.8.0-1008.8","6.8.0-1009.9","6.8.0-1010.10","6.8.0-1011.12","6.8.0-1012.13","6.8.0-1013.14","6.8.0-1014.15","6.8.0-1015.16","6.8.0-1016.17","6.8.0-1017.18"]},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-azure","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1017.20"}]}],"versions":["6.5.0-1007.7","6.6.0-1001.1","6.8.0-1001.1","6.8.0-1005.5","6.8.0-1006.6","6.8.0-1007.7","6.8.0-1008.8","6.8.0-1009.9","6.8.0-1010.10","6.8.0-1012.14","6.8.0-1013.15","6.8.0-1014.16","6.8.0-1015.17","6.8.0-1016.18"]},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-gcp","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1017.19"}]}],"versions":["6.5.0-1007.7","6.6.0-1001.1","6.8.0-1002.2","6.8.0-1005.5","6.8.0-1006.6","6.8.0-1007.7","6.8.0-1008.9","6.8.0-1009.10","6.8.0-1010.11","6.8.0-1011.12","6.8.0-1012.13","6.8.0-1013.14","6.8.0-1014.16","6.8.0-1015.17","6.8.0-1016.18"]},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-gke","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1013.17"}]}],"versions":["6.8.0-1003.5","6.8.0-1004.7","6.8.0-1005.8","6.8.0-1006.9","6.8.0-1007.10","6.8.0-1008.11","6.8.0-1009.12","6.8.0-1010.13","6.8.0-1011.14","6.8.0-1012.15"]},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-gkeop","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1002.4"}]}],"versions":["6.8.0-1001.3"]},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-ibm","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1015.15"}]}],"versions":["6.5.0-1009.9","6.8.0-1001.1","6.8.0-1003.3","6.8.0-1004.4","6.8.0-1005.5","6.8.0-1006.6","6.8.0-1007.7","6.8.0-1008.8","6.8.0-1009.9","6.8.0-1010.10","6.8.0-1011.11","6.8.0-1012.12","6.8.0-1013.13","6.8.0-1014.14"]},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-lowlatency","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-48.48.3"}]}],"versions":["6.5.0-9.9.1","6.6.0-14.14.1","6.8.0-7.7.1","6.8.0-25.25.3","6.8.0-28.28.1","6.8.0-31.31.1","6.8.0-35.35.1","6.8.0-36.36.1","6.8.0-38.38.1","6.8.0-39.39.1","6.8.0-40.40.1","6.8.0-41.41.1","6.8.0-44.44.1","6.8.0-45.45.1","6.8.0-47.47.1"]},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-nvidia","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1017.19"}]}],"versions":["6.8.0-1007.7","6.8.0-1008.8","6.8.0-1009.9","6.8.0-1010.10","6.8.0-1011.11","6.8.0-1012.12","6.8.0-1013.14","6.8.0-1014.15","6.8.0-1015.16"]},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-nvidia-lowlatency","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1017.19.1"}]}],"versions":["6.8.0-1009.9.1","6.8.0-1011.11.1","6.8.0-1012.12.1","6.8.0-1013.14.1","6.8.0-1014.15.1","6.8.0-1015.16.1"]},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-oem-6.8","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1016.16"}]}],"versions":["6.8.0-1003.3","6.8.0-1004.4","6.8.0-1005.5","6.8.0-1006.6","6.8.0-1007.7","6.8.0-1008.8","6.8.0-1009.9","6.8.0-1010.10","6.8.0-1011.11","6.8.0-1012.12","6.8.0-1013.13","6.8.0-1014.14"]},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-oracle","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1015.16"}]}],"versions":["6.5.0-1010.10","6.6.0-1001.1","6.8.0-1001.1","6.8.0-1004.4","6.8.0-1005.5","6.8.0-1006.6","6.8.0-1008.8","6.8.0-1010.10","6.8.0-1011.11","6.8.0-1012.12","6.8.0-1013.13","6.8.0-1014.14"]},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-raspi","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1014.16"}]}],"versions":["6.5.0-1005.7","6.7.0-1001.1","6.8.0-1001.1","6.8.0-1002.2","6.8.0-1003.3","6.8.0-1004.4","6.8.0-1005.5","6.8.0-1006.6","6.8.0-1007.7","6.8.0-1008.8","6.8.0-1009.10","6.8.0-1010.11","6.8.0-1011.12","6.8.0-1012.13","6.8.0-1013.14"]},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-riscv","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-48.48.1"}]}],"versions":["6.5.0-9.9.1","6.8.0-20.20.1","6.8.0-28.28.1","6.8.0-31.31.1","6.8.0-35.35.1","6.8.0-36.36.1","6.8.0-38.38.1","6.8.0-39.39.1","6.8.0-40.40.1","6.8.0-41.41.1","6.8.0-44.44.1","6.8.0-47.47.1"]},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-xilinx","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1009.10"}]}],"versions":["6.8.0-1008.9"]},{"source":"osv","ecosystem":"Ubuntu:Pro:Realtime:24.04:LTS","package":"linux-raspi-realtime","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-2013.14"}]}],"versions":["6.7.0-2001.1","6.8.0-2001.1","6.8.0-2002.2","6.8.0-2004.4","6.8.0-2005.5","6.8.0-2006.6","6.8.0-2007.7","6.8.0-2008.8","6.8.0-2009.9","6.8.0-2010.10","6.8.0-2011.11","6.8.0-2012.12"]},{"source":"osv","ecosystem":"Ubuntu:Pro:Realtime:24.04:LTS","package":"linux-realtime","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.1-1011.11"}]}],"versions":["6.8.0-1008.19","6.8.1-1001.1","6.8.1-1002.2","6.8.1-1003.3","6.8.1-1004.4","6.8.1-1005.5","6.8.1-1006.6","6.8.1-1007.7","6.8.1-1008.8","6.8.1-1009.9","6.8.1-1010.10"]},{"source":"osv","ecosystem":"Ubuntu: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:20.04:LTS","package":"linux-aws-5.15","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-1069.75~20.04.1"}]}],"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"],"bundled":219},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-gcp-5.15","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-1068.76~20.04.1"}]}],"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"],"bundled":219},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-gkeop-5.15","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-1052.59~20.04.1"}]}],"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"],"bundled":219},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-hwe-5.15","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-121.131~20.04.1"}]}],"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"],"bundled":219},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-intel-iotg-5.15","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-1064.70~20.04.1"}]}],"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"],"bundled":219},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-121.131"}]}],"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"],"bundled":219},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-aws","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-1069.75"}]}],"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"],"bundled":219},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-gcp","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-1068.76"}]}],"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"],"bundled":219},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-gke","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-1066.72"}]}],"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"],"bundled":219},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-gkeop","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-1052.59"}]}],"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"],"bundled":219},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-ibm","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-1062.65"}]}],"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"],"bundled":219},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-intel-iotg","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-1064.70"}]}],"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"],"bundled":219},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-kvm","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-1066.71"}]}],"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"],"bundled":219},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-nvidia","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-1064.65"}]}],"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"],"bundled":219},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-oracle","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-1067.73"}]}],"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"],"bundled":219},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-raspi","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-1062.65"}]}],"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"],"bundled":219},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-ibm-5.15","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-1062.65~20.04.1"}]}],"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"],"bundled":219},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-oracle-5.15","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-1067.73~20.04.1"}]}],"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"],"bundled":219},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-lowlatency-hwe-5.15","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-121.131~20.04.1"}]}],"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"],"bundled":219},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-lowlatency","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-121.131"}]}],"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"],"bundled":219},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-azure-5.15","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-1072.81~20.04.1"}]}],"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"],"bundled":219},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-azure","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-1072.81"}]}],"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"],"bundled":219},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-azure-fde","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-1072.81.1"}]}],"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"],"bundled":219},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-azure-fde-5.15","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-1072.81~20.04.1.1"}]}],"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"],"bundled":219},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-xilinx-zynqmp","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-1035.39"}]}],"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"],"bundled":429},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-gcp-6.8","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1017.19~22.04.1"}]}],"versions":["6.8.0-1010.11~22.04.1","6.8.0-1011.12~22.04.1","6.8.0-1012.13~22.04.1","6.8.0-1013.14~22.04.1","6.8.0-1014.16~22.04.1","6.8.0-1015.17~22.04.1","6.8.0-1016.18~22.04.1"],"bundled":196},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-hwe-6.8","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-48.48~22.04.1"}]}],"versions":["6.8.0-38.38~22.04.1","6.8.0-39.39~22.04.1","6.8.0-40.40~22.04.3","6.8.0-45.45~22.04.1","6.8.0-47.47~22.04.1"],"bundled":196},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-48.48"}]}],"versions":["6.5.0-9.9","6.6.0-14.14","6.8.0-11.11","6.8.0-20.20","6.8.0-22.22","6.8.0-28.28","6.8.0-31.31","6.8.0-35.35","6.8.0-36.36","6.8.0-38.38","6.8.0-39.39","6.8.0-40.40","6.8.0-41.41","6.8.0-44.44","6.8.0-45.45","6.8.0-47.47"],"bundled":196},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-azure","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1017.20"}]}],"versions":["6.5.0-1007.7","6.6.0-1001.1","6.8.0-1001.1","6.8.0-1005.5","6.8.0-1006.6","6.8.0-1007.7","6.8.0-1008.8","6.8.0-1009.9","6.8.0-1010.10","6.8.0-1012.14","6.8.0-1013.15","6.8.0-1014.16","6.8.0-1015.17","6.8.0-1016.18"],"bundled":196},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-gcp","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1017.19"}]}],"versions":["6.5.0-1007.7","6.6.0-1001.1","6.8.0-1002.2","6.8.0-1005.5","6.8.0-1006.6","6.8.0-1007.7","6.8.0-1008.9","6.8.0-1009.10","6.8.0-1010.11","6.8.0-1011.12","6.8.0-1012.13","6.8.0-1013.14","6.8.0-1014.16","6.8.0-1015.17","6.8.0-1016.18"],"bundled":196},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-ibm","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1015.15"}]}],"versions":["6.5.0-1009.9","6.8.0-1001.1","6.8.0-1003.3","6.8.0-1004.4","6.8.0-1005.5","6.8.0-1006.6","6.8.0-1007.7","6.8.0-1008.8","6.8.0-1009.9","6.8.0-1010.10","6.8.0-1011.11","6.8.0-1012.12","6.8.0-1013.13","6.8.0-1014.14"],"bundled":196},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-aws-6.8","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1018.19~22.04.1"}]}],"versions":["6.8.0-1009.9~22.04.2","6.8.0-1010.10~22.04.2","6.8.0-1011.12~22.04.1","6.8.0-1013.14~22.04.1","6.8.0-1014.15~22.04.1","6.8.0-1015.16~22.04.1","6.8.0-1016.17~22.04.2","6.8.0-1017.18~22.04.1"],"bundled":196},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-oracle-6.8","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1015.15~22.04.1"}]}],"versions":["6.8.0-1006.6~22.04.3","6.8.0-1008.8~22.04.1","6.8.0-1010.10~22.04.1","6.8.0-1011.11~22.04.1","6.8.0-1012.12~22.04.1","6.8.0-1013.13~22.04.1","6.8.0-1014.14~22.04.1"],"bundled":196},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-aws","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1018.20"}]}],"versions":["6.5.0-1008.8","6.6.0-1001.1","6.8.0-1001.1","6.8.0-1006.6","6.8.0-1008.8","6.8.0-1009.9","6.8.0-1010.10","6.8.0-1011.12","6.8.0-1012.13","6.8.0-1013.14","6.8.0-1014.15","6.8.0-1015.16","6.8.0-1016.17","6.8.0-1017.18"],"bundled":196},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-oracle","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1015.16"}]}],"versions":["6.5.0-1010.10","6.6.0-1001.1","6.8.0-1001.1","6.8.0-1004.4","6.8.0-1005.5","6.8.0-1006.6","6.8.0-1008.8","6.8.0-1010.10","6.8.0-1011.11","6.8.0-1012.12","6.8.0-1013.13","6.8.0-1014.14"],"bundled":196},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-oem-6.8","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1016.16"}]}],"versions":["6.8.0-1003.3","6.8.0-1004.4","6.8.0-1005.5","6.8.0-1006.6","6.8.0-1007.7","6.8.0-1008.8","6.8.0-1009.9","6.8.0-1010.10","6.8.0-1011.11","6.8.0-1012.12","6.8.0-1013.13","6.8.0-1014.14"],"bundled":196},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-raspi","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1014.16"}]}],"versions":["6.5.0-1005.7","6.7.0-1001.1","6.8.0-1001.1","6.8.0-1002.2","6.8.0-1003.3","6.8.0-1004.4","6.8.0-1005.5","6.8.0-1006.6","6.8.0-1007.7","6.8.0-1008.8","6.8.0-1009.10","6.8.0-1010.11","6.8.0-1011.12","6.8.0-1012.13","6.8.0-1013.14"],"bundled":196},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-gke","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1013.17"}]}],"versions":["6.8.0-1003.5","6.8.0-1004.7","6.8.0-1005.8","6.8.0-1006.9","6.8.0-1007.10","6.8.0-1008.11","6.8.0-1009.12","6.8.0-1010.13","6.8.0-1011.14","6.8.0-1012.15"],"bundled":196},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-lowlatency-hwe-6.8","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-48.48.3~22.04.1"}]}],"versions":["6.8.0-38.38.1~22.04.2","6.8.0-40.40.1~22.04.1","6.8.0-44.44.1~22.04.1","6.8.0-45.45.1~22.04.1","6.8.0-47.47.1~22.04.1"],"bundled":196},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-lowlatency","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-48.48.3"}]}],"versions":["6.5.0-9.9.1","6.6.0-14.14.1","6.8.0-7.7.1","6.8.0-25.25.3","6.8.0-28.28.1","6.8.0-31.31.1","6.8.0-35.35.1","6.8.0-36.36.1","6.8.0-38.38.1","6.8.0-39.39.1","6.8.0-40.40.1","6.8.0-41.41.1","6.8.0-44.44.1","6.8.0-45.45.1","6.8.0-47.47.1"],"bundled":196},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-azure-6.8","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1017.20~22.04.1"}]}],"versions":["6.8.0-1008.8~22.04.1","6.8.0-1009.9~22.04.1","6.8.0-1010.10~22.04.1","6.8.0-1012.14~22.04.1","6.8.0-1013.15~22.04.1","6.8.0-1014.16~22.04.1","6.8.0-1015.17~22.04.2"],"bundled":198},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-nvidia-6.8","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1017.19~22.04.1"}]}],"versions":["6.8.0-1008.8~22.04.1","6.8.0-1009.9~22.04.1","6.8.0-1010.10~22.04.1","6.8.0-1011.11~22.04.1","6.8.0-1012.12~22.04.1","6.8.0-1013.14~22.04.1","6.8.0-1014.15~22.04.1","6.8.0-1015.16~22.04.1"],"bundled":197},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-nvidia","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1017.19"}]}],"versions":["6.8.0-1007.7","6.8.0-1008.8","6.8.0-1009.9","6.8.0-1010.10","6.8.0-1011.11","6.8.0-1012.12","6.8.0-1013.14","6.8.0-1014.15","6.8.0-1015.16"],"bundled":197},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-nvidia-lowlatency","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1017.19.1"}]}],"versions":["6.8.0-1009.9.1","6.8.0-1011.11.1","6.8.0-1012.12.1","6.8.0-1013.14.1","6.8.0-1014.15.1","6.8.0-1015.16.1"],"bundled":197},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-gkeop","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1002.4"}]}],"versions":["6.8.0-1001.3"],"bundled":607}],"products":[{"vendor":"linux","product":"linux"},{"vendor":"linux","product":"linux_kernel"}],"references":[{"url":"https://git.kernel.org/stable/c/2f3c22b1d3d7e86712253244797a651998c141fa","tags":["x_transferred","Patch","web","report"]},{"url":"https://git.kernel.org/stable/c/b4fed1443a6571d49c6ffe7d97af3bbe5ee6dff5","tags":["x_transferred","Patch","web","report"]},{"url":"https://git.kernel.org/stable/c/940a71f08ef153ef807f751310b0648d1fa5d0da","tags":["x_transferred","Patch","web","report"]},{"url":"https://git.kernel.org/stable/c/5502c1f1d0d7472706cc1f201aecf1c935d302d1","tags":["x_transferred","Patch","web","report"]},{"url":"https://git.kernel.org/stable/c/818004f2a380420c19872171be716174d4985e33","tags":["x_transferred","Patch","web","report"]},{"url":"https://git.kernel.org/stable/c/c758b77d4a0a0ed3a1292b3fd7a2aeccd1a169a4","tags":["x_transferred","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-42152","tags":["web","advisory"]},{"url":"https://github.com/advisories/GHSA-ghw9-6h55-qj7v"},{"url":"https://access.redhat.com/errata/RHSA-2024:5928","tags":["advisory"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-52771","tags":["report"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-52880","tags":["report"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-26581","tags":["report"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-26668","tags":["report"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-26810","tags":["report"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-26855","tags":["report"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-26908","tags":["report"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-26925","tags":["report"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-27016","tags":["report"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-27019","tags":["report"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-27020","tags":["report"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-27415","tags":["report"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-35839","tags":["report"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-35896","tags":["report"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-35897","tags":["report"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-35898","tags":["report"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-35962","tags":["report"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-36003","tags":["report"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-36025","tags":["report"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-38538","tags":["report"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-38540","tags":["report"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-38544","tags":["report"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-38579","tags":["report"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-38608","tags":["report"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-39476","tags":["report"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-40905","tags":["report"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-40911","tags":["report"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-40912","tags":["report"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-40914","tags":["report"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-40929","tags":["report"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-40939","tags":["report"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-40941","tags":["report"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-40957","tags":["report"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-40978","tags":["report"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-40983","tags":["report"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-41041","tags":["report"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-41076","tags":["report"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-41090","tags":["report"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-41091","tags":["report"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-42110","tags":["report"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-42152","tags":["report"]},{"url":"https://bugzilla.redhat.com/2265185","tags":["report"]},{"url":"https://bugzilla.redhat.com/2272797","tags":["report"]},{"url":"https://bugzilla.redhat.com/2273654","tags":["report"]},{"url":"https://bugzilla.redhat.com/2275742","tags":["report"]},{"url":"https://bugzilla.redhat.com/2275744","tags":["report"]},{"url":"https://bugzilla.redhat.com/2277166","tags":["report"]},{"url":"https://bugzilla.redhat.com/2278256","tags":["report"]},{"url":"https://bugzilla.redhat.com/2278258","tags":["report"]},{"url":"https://bugzilla.redhat.com/2278264","tags":["report"]},{"url":"https://bugzilla.redhat.com/2281101","tags":["report"]},{"url":"https://bugzilla.redhat.com/2281284","tags":["report"]},{"url":"https://bugzilla.redhat.com/2281669","tags":["report"]},{"url":"https://bugzilla.redhat.com/2281672","tags":["report"]},{"url":"https://bugzilla.redhat.com/2281675","tags":["report"]},{"url":"https://bugzilla.redhat.com/2281916","tags":["report"]},{"url":"https://bugzilla.redhat.com/2281958","tags":["report"]},{"url":"https://bugzilla.redhat.com/2282720","tags":["report"]},{"url":"https://bugzilla.redhat.com/2283468","tags":["report"]},{"url":"https://bugzilla.redhat.com/2284421","tags":["report"]},{"url":"https://bugzilla.redhat.com/2293356","tags":["report"]},{"url":"https://bugzilla.redhat.com/2293414","tags":["report"]},{"url":"https://bugzilla.redhat.com/2293455","tags":["report"]},{"url":"https://bugzilla.redhat.com/2293459","tags":["report"]},{"url":"https://bugzilla.redhat.com/2293461","tags":["report"]},{"url":"https://bugzilla.redhat.com/2295914","tags":["report"]},{"url":"https://bugzilla.redhat.com/2297489","tags":["report"]},{"url":"https://bugzilla.redhat.com/2297495","tags":["report"]},{"url":"https://bugzilla.redhat.com/2297496","tags":["report"]},{"url":"https://bugzilla.redhat.com/2297498","tags":["report"]},{"url":"https://bugzilla.redhat.com/2297513","tags":["report"]},{"url":"https://bugzilla.redhat.com/2297523","tags":["report"]},{"url":"https://bugzilla.redhat.com/2297525","tags":["report"]},{"url":"https://bugzilla.redhat.com/2297541","tags":["report"]},{"url":"https://bugzilla.redhat.com/2297562","tags":["report"]},{"url":"https://bugzilla.redhat.com/2297567","tags":["report"]},{"url":"https://bugzilla.redhat.com/2299240","tags":["report"]},{"url":"https://bugzilla.redhat.com/2299336","tags":["report"]},{"url":"https://bugzilla.redhat.com/2300410","tags":["report"]},{"url":"https://bugzilla.redhat.com/2300453","tags":["report"]},{"url":"https://bugzilla.redhat.com/2301473","tags":["report"]},{"url":"https://bugzilla.redhat.com/2301519","tags":["report"]},{"url":"https://errata.almalinux.org/9/ALSA-2024-5928.html","tags":["advisory"]},{"url":"https://access.redhat.com/errata/RHSA-2024:7000","tags":["advisory"]},{"url":"https://access.redhat.com/security/cve/CVE-2021-46984","tags":["report"]},{"url":"https://access.redhat.com/security/cve/CVE-2021-47097","tags":["report"]},{"url":"https://access.redhat.com/security/cve/CVE-2021-47101","tags":["report"]},{"url":"https://access.redhat.com/security/cve/CVE-2021-47287","tags":["report"]},{"url":"https://access.redhat.com/security/cve/CVE-2021-47289","tags":["report"]},{"url":"https://access.redhat.com/security/cve/CVE-2021-47321","tags":["report"]},{"url":"https://access.redhat.com/security/cve/CVE-2021-47338","tags":["report"]},{"url":"https://access.redhat.com/security/cve/CVE-2021-47352","tags":["report"]},{"url":"https://access.redhat.com/security/cve/CVE-2021-47383","tags":["report"]},{"url":"https://access.redhat.com/security/cve/CVE-2021-47384","tags":["report"]},{"url":"https://access.redhat.com/security/cve/CVE-2021-47385","tags":["report"]},{"url":"https://access.redhat.com/security/cve/CVE-2021-47386","tags":["report"]},{"url":"https://access.redhat.com/security/cve/CVE-2021-47393","tags":["report"]},{"url":"https://access.redhat.com/security/cve/CVE-2021-47412","tags":["report"]},{"url":"https://access.redhat.com/security/cve/CVE-2021-47432","tags":["report"]},{"url":"https://access.redhat.com/security/cve/CVE-2021-47441","tags":["report"]},{"url":"https://access.redhat.com/security/cve/CVE-2021-47455","tags":["report"]},{"url":"https://access.redhat.com/security/cve/CVE-2021-47466","tags":["report"]},{"url":"https://access.redhat.com/security/cve/CVE-2021-47497","tags":["report"]},{"url":"https://access.redhat.com/security/cve/CVE-2021-47527","tags":["report"]},{"url":"https://access.redhat.com/security/cve/CVE-2021-47560","tags":["report"]},{"url":"https://access.redhat.com/security/cve/CVE-2021-47582","tags":["report"]},{"url":"https://access.redhat.com/security/cve/CVE-2021-47609","tags":["report"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-48619","tags":["report"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-48754","tags":["report"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-48760","tags":["report"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-48804","tags":["report"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-48836","tags":["report"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-48866","tags":["report"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-52470","tags":["report"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-52476","tags":["report"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-52478","tags":["report"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-52522","tags":["report"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-52605","tags":["report"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-52683","tags":["report"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-52798","tags":["report"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-52800","tags":["report"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-52809","tags":["report"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-52817","tags":["report"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-52840","tags":["report"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-6040","tags":["report"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-23848","tags":["report"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-26595","tags":["report"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-26600","tags":["report"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-26638","tags":["report"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-26645","tags":["report"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-26649","tags":["report"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-26665","tags":["report"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-26717","tags":["report"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-26720","tags":["report"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-26769","tags":["report"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-26846","tags":["report"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-26880","tags":["report"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-26894","tags":["report"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-26923","tags":["report"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-26939","tags":["report"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-27013","tags":["report"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-27042","tags":["report"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-35809","tags":["report"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-35877","tags":["report"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-35884","tags":["report"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-35944","tags":["report"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-35989","tags":["report"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-36883","tags":["report"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-36901","tags":["report"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-36902","tags":["report"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-36919","tags":["report"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-36920","tags":["report"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-36922","tags":["report"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-36939","tags":["report"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-36953","tags":["report"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-37356","tags":["report"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-38558","tags":["report"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-38559","tags":["report"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-38570","tags":["report"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-38581","tags":["report"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-38619","tags":["report"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-39471","tags":["report"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-39499","tags":["report"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-39501","tags":["report"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-39506","tags":["report"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-40901","tags":["report"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-40904","tags":["report"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-40931","tags":["report"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-40954","tags":["report"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-40958","tags":["report"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-40959","tags":["report"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-40960","tags":["report"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-40972","tags":["report"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-40977","tags":["report"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-40988","tags":["report"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-40989","tags":["report"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-40995","tags":["report"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-40997","tags":["report"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-40998","tags":["report"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-41005","tags":["report"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-41007","tags":["report"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-41008","tags":["report"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-41012","tags":["report"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-41013","tags":["report"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-41014","tags":["report"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-41023","tags":["report"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-41035","tags":["report"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-41038","tags":["report"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-41039","tags":["report"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-41040","tags":["report"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-41044","tags":["report"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-41055","tags":["report"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-41056","tags":["report"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-41060","tags":["report"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-41064","tags":["report"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-41065","tags":["report"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-41071","tags":["report"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-41097","tags":["report"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-42084","tags":["report"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-42090","tags":["report"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-42094","tags":["report"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-42096","tags":["report"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-42114","tags":["report"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-42124","tags":["report"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-42131","tags":["report"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-42154","tags":["report"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-42225","tags":["report"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-42226","tags":["report"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-42228","tags":["report"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-42237","tags":["report"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-42238","tags":["report"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-42240","tags":["report"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-42246","tags":["report"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-42265","tags":["report"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-42322","tags":["report"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-43830","tags":["report"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-43871","tags":["report"]},{"url":"https://bugzilla.redhat.com/2258012","tags":["report"]},{"url":"https://bugzilla.redhat.com/2258013","tags":["report"]},{"url":"https://bugzilla.redhat.com/2260038","tags":["report"]},{"url":"https://bugzilla.redhat.com/2265799","tags":["report"]},{"url":"https://bugzilla.redhat.com/2265838","tags":["report"]},{"url":"https://bugzilla.redhat.com/2266358","tags":["report"]},{"url":"https://bugzilla.redhat.com/2266750","tags":["report"]},{"url":"https://bugzilla.redhat.com/2267036","tags":["report"]},{"url":"https://bugzilla.redhat.com/2267041","tags":["report"]},{"url":"https://bugzilla.redhat.com/2267795","tags":["report"]},{"url":"https://bugzilla.redhat.com/2267916","tags":["report"]},{"url":"https://bugzilla.redhat.com/2267925","tags":["report"]},{"url":"https://bugzilla.redhat.com/2268295","tags":["report"]},{"url":"https://bugzilla.redhat.com/2270103","tags":["report"]},{"url":"https://bugzilla.redhat.com/2271648","tags":["report"]},{"url":"https://bugzilla.redhat.com/2271796","tags":["report"]},{"url":"https://bugzilla.redhat.com/2272793","tags":["report"]},{"url":"https://bugzilla.redhat.com/2273141","tags":["report"]},{"url":"https://bugzilla.redhat.com/2273148","tags":["report"]},{"url":"https://bugzilla.redhat.com/2273180","tags":["report"]},{"url":"https://bugzilla.redhat.com/2275558","tags":["report"]},{"url":"https://bugzilla.redhat.com/2275661","tags":["report"]},{"url":"https://bugzilla.redhat.com/2275690","tags":["report"]},{"url":"https://bugzilla.redhat.com/2277171","tags":["report"]},{"url":"https://bugzilla.redhat.com/2278220","tags":["report"]},{"url":"https://bugzilla.redhat.com/2278270","tags":["report"]},{"url":"https://bugzilla.redhat.com/2278447","tags":["report"]},{"url":"https://bugzilla.redhat.com/2281217","tags":["report"]},{"url":"https://bugzilla.redhat.com/2281317","tags":["report"]},{"url":"https://bugzilla.redhat.com/2281704","tags":["report"]},{"url":"https://bugzilla.redhat.com/2281720","tags":["report"]},{"url":"https://bugzilla.redhat.com/2281807","tags":["report"]},{"url":"https://bugzilla.redhat.com/2281847","tags":["report"]},{"url":"https://bugzilla.redhat.com/2282324","tags":["report"]},{"url":"https://bugzilla.redhat.com/2282345","tags":["report"]},{"url":"https://bugzilla.redhat.com/2282354","tags":["report"]},{"url":"https://bugzilla.redhat.com/2282355","tags":["report"]},{"url":"https://bugzilla.redhat.com/2282356","tags":["report"]},{"url":"https://bugzilla.redhat.com/2282357","tags":["report"]},{"url":"https://bugzilla.redhat.com/2282366","tags":["report"]},{"url":"https://bugzilla.redhat.com/2282401","tags":["report"]},{"url":"https://bugzilla.redhat.com/2282422","tags":["report"]},{"url":"https://bugzilla.redhat.com/2282440","tags":["report"]},{"url":"https://bugzilla.redhat.com/2282508","tags":["report"]},{"url":"https://bugzilla.redhat.com/2282511","tags":["report"]},{"url":"https://bugzilla.redhat.com/2282648","tags":["report"]},{"url":"https://bugzilla.redhat.com/2282669","tags":["report"]},{"url":"https://bugzilla.redhat.com/2282676","tags":["report"]},{"url":"https://bugzilla.redhat.com/2282757","tags":["report"]},{"url":"https://bugzilla.redhat.com/2282764","tags":["report"]},{"url":"https://bugzilla.redhat.com/2282851","tags":["report"]},{"url":"https://bugzilla.redhat.com/2282890","tags":["report"]},{"url":"https://bugzilla.redhat.com/2282903","tags":["report"]},{"url":"https://bugzilla.redhat.com/2282918","tags":["report"]},{"url":"https://bugzilla.redhat.com/2283389","tags":["report"]},{"url":"https://bugzilla.redhat.com/2283424","tags":["report"]},{"url":"https://bugzilla.redhat.com/2284271","tags":["report"]},{"url":"https://bugzilla.redhat.com/2284511","tags":["report"]},{"url":"https://bugzilla.redhat.com/2284515","tags":["report"]},{"url":"https://bugzilla.redhat.com/2284545","tags":["report"]},{"url":"https://bugzilla.redhat.com/2284596","tags":["report"]},{"url":"https://bugzilla.redhat.com/2284628","tags":["report"]},{"url":"https://bugzilla.redhat.com/2284630","tags":["report"]},{"url":"https://bugzilla.redhat.com/2284634","tags":["report"]},{"url":"https://bugzilla.redhat.com/2293247","tags":["report"]},{"url":"https://bugzilla.redhat.com/2293270","tags":["report"]},{"url":"https://bugzilla.redhat.com/2293273","tags":["report"]},{"url":"https://bugzilla.redhat.com/2293304","tags":["report"]},{"url":"https://bugzilla.redhat.com/2293377","tags":["report"]},{"url":"https://bugzilla.redhat.com/2293408","tags":["report"]},{"url":"https://bugzilla.redhat.com/2293423","tags":["report"]},{"url":"https://bugzilla.redhat.com/2293440","tags":["report"]},{"url":"https://bugzilla.redhat.com/2293441","tags":["report"]},{"url":"https://bugzilla.redhat.com/2293658","tags":["report"]},{"url":"https://bugzilla.redhat.com/2294313","tags":["report"]},{"url":"https://bugzilla.redhat.com/2297471","tags":["report"]},{"url":"https://bugzilla.redhat.com/2297473","tags":["report"]},{"url":"https://bugzilla.redhat.com/2297478","tags":["report"]},{"url":"https://bugzilla.redhat.com/2297488","tags":["report"]},{"url":"https://bugzilla.redhat.com/2297515","tags":["report"]},{"url":"https://bugzilla.redhat.com/2297538","tags":["report"]},{"url":"https://bugzilla.redhat.com/2297542","tags":["report"]},{"url":"https://bugzilla.redhat.com/2297543","tags":["report"]},{"url":"https://bugzilla.redhat.com/2297544","tags":["report"]},{"url":"https://bugzilla.redhat.com/2297556","tags":["report"]},{"url":"https://bugzilla.redhat.com/2297561","tags":["report"]},{"url":"https://bugzilla.redhat.com/2297572","tags":["report"]},{"url":"https://bugzilla.redhat.com/2297573","tags":["report"]},{"url":"https://bugzilla.redhat.com/2297579","tags":["report"]},{"url":"https://bugzilla.redhat.com/2297581","tags":["report"]},{"url":"https://bugzilla.redhat.com/2297582","tags":["report"]},{"url":"https://bugzilla.redhat.com/2297589","tags":["report"]},{"url":"https://bugzilla.redhat.com/2297706","tags":["report"]},{"url":"https://bugzilla.redhat.com/2297909","tags":["report"]},{"url":"https://bugzilla.redhat.com/2298079","tags":["report"]},{"url":"https://bugzilla.redhat.com/2298140","tags":["report"]},{"url":"https://bugzilla.redhat.com/2298177","tags":["report"]},{"url":"https://bugzilla.redhat.com/2298640","tags":["report"]},{"url":"https://bugzilla.redhat.com/2299452","tags":["report"]},{"url":"https://bugzilla.redhat.com/2300296","tags":["report"]},{"url":"https://bugzilla.redhat.com/2300297","tags":["report"]},{"url":"https://bugzilla.redhat.com/2300381","tags":["report"]},{"url":"https://bugzilla.redhat.com/2300402","tags":["report"]},{"url":"https://bugzilla.redhat.com/2300407","tags":["report"]},{"url":"https://bugzilla.redhat.com/2300408","tags":["report"]},{"url":"https://bugzilla.redhat.com/2300409","tags":["report"]},{"url":"https://bugzilla.redhat.com/2300414","tags":["report"]},{"url":"https://bugzilla.redhat.com/2300429","tags":["report"]},{"url":"https://bugzilla.redhat.com/2300430","tags":["report"]},{"url":"https://bugzilla.redhat.com/2300434","tags":["report"]},{"url":"https://bugzilla.redhat.com/2300439","tags":["report"]},{"url":"https://bugzilla.redhat.com/2300440","tags":["report"]},{"url":"https://bugzilla.redhat.com/2300448","tags":["report"]},{"url":"https://bugzilla.redhat.com/2300492","tags":["report"]},{"url":"https://bugzilla.redhat.com/2300533","tags":["report"]},{"url":"https://bugzilla.redhat.com/2300552","tags":["report"]},{"url":"https://bugzilla.redhat.com/2300709","tags":["report"]},{"url":"https://bugzilla.redhat.com/2300713","tags":["report"]},{"url":"https://bugzilla.redhat.com/2301477","tags":["report"]},{"url":"https://bugzilla.redhat.com/2301489","tags":["report"]},{"url":"https://bugzilla.redhat.com/2301496","tags":["report"]},{"url":"https://bugzilla.redhat.com/2301522","tags":["report"]},{"url":"https://bugzilla.redhat.com/2301543","tags":["report"]},{"url":"https://bugzilla.redhat.com/2301544","tags":["report"]},{"url":"https://bugzilla.redhat.com/2303077","tags":["report"]},{"url":"https://bugzilla.redhat.com/2303505","tags":["report"]},{"url":"https://bugzilla.redhat.com/2303506","tags":["report"]},{"url":"https://bugzilla.redhat.com/2303508","tags":["report"]},{"url":"https://bugzilla.redhat.com/2303514","tags":["report"]},{"url":"https://bugzilla.redhat.com/2305410","tags":["report"]},{"url":"https://bugzilla.redhat.com/2305467","tags":["report"]},{"url":"https://bugzilla.redhat.com/2305488","tags":["report"]},{"url":"https://bugzilla.redhat.com/2306365","tags":["report"]},{"url":"https://errata.almalinux.org/8/ALSA-2024-7000.html","tags":["advisory"]},{"url":"https://access.redhat.com/errata/RHSA-2024:7001","tags":["advisory"]},{"url":"https://errata.almalinux.org/8/ALSA-2024-7001.html","tags":["advisory"]},{"url":"https://docs.bell-sw.com/security/cves/CVE-2024-42152","tags":["advisory"]},{"url":"https://errata.tuxcare.com/almalinux9.2-esu/CLSA-2024-1728936982.html","tags":["advisory"]},{"url":"https://github.com/CVEProject/cvelistV5/tree/main/cves/2024/42xxx/CVE-2024-42152.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-42152","tags":["advisory"]},{"url":"https://advisories.mageia.org/MGASA-2024-0277.html","tags":["advisory"]},{"url":"https://bugs.mageia.org/show_bug.cgi?id=33446","tags":["report"]},{"url":"https://cdn.kernel.org/pub/linux/kernel/v6.x/ChangeLog-6.6.38","tags":["web"]},{"url":"https://cdn.kernel.org/pub/linux/kernel/v6.x/ChangeLog-6.6.39","tags":["web"]},{"url":"https://cdn.kernel.org/pub/linux/kernel/v6.x/ChangeLog-6.6.40","tags":["web"]},{"url":"https://cdn.kernel.org/pub/linux/kernel/v6.x/ChangeLog-6.6.41","tags":["web"]},{"url":"https://cdn.kernel.org/pub/linux/kernel/v6.x/ChangeLog-6.6.42","tags":["web"]},{"url":"https://cdn.kernel.org/pub/linux/kernel/v6.x/ChangeLog-6.6.43","tags":["web"]},{"url":"https://advisories.mageia.org/MGASA-2024-0278.html","tags":["advisory"]},{"url":"https://bugs.mageia.org/show_bug.cgi?id=33447","tags":["report"]},{"url":"https://www.openeuler.org/zh/security/security-bulletins/detail/?id=openEuler-SA-2024-2124","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-36934","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-37078","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-40959","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-40976","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-40978","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-41012","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-41016","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-41037","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-41052","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-41071","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-41082","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-41098","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-42139","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-42153","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-42234","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-42235","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-42237","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-42238","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-42239","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-42240","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-42241","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-42243","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-42248","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-42250","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-42253","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-42258","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-42259","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-42271","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-42272","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-42276","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-42277","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-42279","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-42291","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-42294","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-42296","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-42298","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-42303","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-42307","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-42314","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-42315","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-42316","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-42317","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-42320","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-42321","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-43817","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-43818","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-43821","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-43825","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-43826","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-43829","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-43832","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-43833","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-43837","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-43841","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-43842","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-43845","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-43846","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-43847","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-43849","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-43850","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-43851","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-43855","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-43856","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-43859","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-43883","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-43884","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-43889","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-43890","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-43891","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-43895","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-43897","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-43898","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-43899","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-43900","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-43902","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-43905","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-43906","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-43907","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-43908","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-43909","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-43912","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-43913","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-43914","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-44934","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-44935","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-44940","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-44942","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-44946","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-44947","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-44961","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-44966","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-44971","tags":["advisory"]},{"url":"https://www.openeuler.org/zh/security/security-bulletins/detail/?id=openEuler-SA-2024-2321","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-48916","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-48952","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-52917","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-52918","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-35878","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-35990","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-36286","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-38605","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-38635","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-38667","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-42301","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-43858","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-43867","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-43871","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-43894","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-45009","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-46675","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-46689","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-46722","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-46724","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-46757","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-46802","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-46830","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-46853","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-47667","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-47669","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-47684","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-47685","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-47692","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-47695","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-47698","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-47709","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-47710","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-47720","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-47735","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-47737","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-47757","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-49866","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-49867","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-49868","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-49875","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-49892","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-49894","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-49895","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-49900","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-49902","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-49903","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-49911","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-49927","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-49959","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-49965","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-49966","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-49969","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-49974","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-49985","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-50025","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-50036","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-50046","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-50049","tags":["advisory"]},{"url":"https://www.openeuler.org/zh/security/security-bulletins/detail/?id=openEuler-SA-2024-2322","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-48988","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-52919","tags":["advisory"]},{"url":"https://www.openeuler.org/zh/security/security-bulletins/detail/?id=openEuler-SA-2024-2324","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-48946","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-48967","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-48973","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-48977","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-48986","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-48991","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-48994","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-49006","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-49007","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-49019","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-49029","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-49030","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-49033","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-52754","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-52855","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-26917","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-41015","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-50007","tags":["advisory"]},{"url":"https://access.redhat.com/security/updates/classification/#important","tags":["article"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2265185","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2272797","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2273654","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2275742","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2275744","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2277166","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2278256","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2278258","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2278264","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2281101","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2281284","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2281669","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2281672","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2281675","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2281916","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2281958","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2282720","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2283468","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2284421","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2293356","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2293414","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2293455","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2293459","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2293461","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2295914","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2297489","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2297495","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2297496","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2297498","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2297513","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2297523","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2297525","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2297541","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2297562","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2297567","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2299240","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2299336","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2300410","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2300453","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2301473","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2301519","tags":["report"]},{"url":"https://security.access.redhat.com/data/csaf/v2/advisories/2024/rhsa-2024_5928.json","tags":["advisory"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-50495","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2401512","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-50495","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-50495","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025100419-CVE-2022-50495-fdee@gregkh/T","tags":["article"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-52771","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-52771","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024052150-CVE-2023-52771-43ad@gregkh/T","tags":["article"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-52880","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-52880","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024052422-CVE-2023-52880-d2ff@gregkh/T","tags":["article"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-26581","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-26581","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024022024-uniquely-recluse-d893@gregkh/T/#u","tags":["article"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-26668","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-26668","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024040235-CVE-2024-26668-636e@gregkh/T","tags":["article"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-26810","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-26810","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024040548-CVE-2024-26810-4371@gregkh/T","tags":["article"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-26855","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-26855","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024041724-CVE-2024-26855-ac0d@gregkh/T","tags":["article"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-26908","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-26908","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024041747-CVE-2024-26908-4690@gregkh/T","tags":["article"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-26925","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-26925","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024042421-CVE-2024-26925-7c19@gregkh/T","tags":["article"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-27016","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-27016","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024050149-CVE-2024-27016-5114@gregkh/T","tags":["article"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-27019","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-27019","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024050150-CVE-2024-27019-e3d4@gregkh/T","tags":["article"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-27020","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-27020","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024050150-CVE-2024-27020-5158@gregkh/T","tags":["article"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-27415","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-27415","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024051702-CVE-2024-27415-dcae@gregkh/T","tags":["article"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-35839","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-35839","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024051756-CVE-2024-35839-4194@gregkh/T","tags":["article"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-35896","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-35896","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024051950-CVE-2024-35896-e6b5@gregkh/T","tags":["article"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-35897","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-35897","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024051951-CVE-2024-35897-1585@gregkh/T","tags":["article"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-35898","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-35898","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024051951-CVE-2024-35898-a10e@gregkh/T","tags":["article"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-35962","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-35962","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024052020-CVE-2024-35962-e5ce@gregkh/T","tags":["article"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-36003","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-36003","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024052024-CVE-2024-36003-33b4@gregkh/T","tags":["article"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-36025","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-36025","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024053034-CVE-2024-36025-95e0@gregkh/T","tags":["article"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-38538","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-38538","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024061947-CVE-2024-38538-e28a@gregkh/T","tags":["article"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-38540","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-38540","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024061947-CVE-2024-38540-1d0a@gregkh/T","tags":["article"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-38544","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-38544","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024061949-CVE-2024-38544-601b@gregkh/T","tags":["article"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-38579","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-38579","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024061947-CVE-2024-38579-e96a@gregkh/T","tags":["article"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-38608","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-38608","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024061920-CVE-2024-38608-4068@gregkh/T","tags":["article"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-39476","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-39476","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024070518-CVE-2024-39476-aa2d@gregkh/T","tags":["article"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-40905","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-40905","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024071208-CVE-2024-40905-44f9@gregkh/T","tags":["article"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-40911","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-40911","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024071210-CVE-2024-40911-2382@gregkh/T","tags":["article"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-40912","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-40912","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024071210-CVE-2024-40912-7286@gregkh/T","tags":["article"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-40914","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-40914","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024071210-CVE-2024-40914-0e04@gregkh/T","tags":["article"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-40929","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-40929","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024071215-CVE-2024-40929-e1cb@gregkh/T","tags":["article"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-40939","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-40939","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024071218-CVE-2024-40939-a56c@gregkh/T","tags":["article"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-40941","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-40941","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024071219-CVE-2024-40941-9e5c@gregkh/T","tags":["article"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-40957","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-40957","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024071224-CVE-2024-40957-94a5@gregkh/T","tags":["article"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-40978","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024071231-CVE-2024-40978-d135@gregkh/T","tags":["article"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-40983","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-40983","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024071201-CVE-2024-40983-e1b1@gregkh/T","tags":["article"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-41041","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-41041","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024072924-CVE-2024-41041-ae0c@gregkh/T","tags":["article"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-41076","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-41076","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024072910-CVE-2024-41076-6124@gregkh/T","tags":["article"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-41090","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-41090","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024072916-CVE-2024-41090-9830@gregkh","tags":["article"]},{"url":"https://www.openwall.com/lists/oss-security/2024/07/24/4","tags":["article"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-41091","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-41091","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024072918-CVE-2024-41091-35b7@gregkh","tags":["article"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-42110","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-42110","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024073021-CVE-2024-42110-4b28@gregkh/T","tags":["article"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-42152","tags":["advisory","report"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024073034-CVE-2024-42152-c248@gregkh/T","tags":["article"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2258012","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2258013","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2260038","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2265799","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2265838","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2266358","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2266750","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2267036","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2267041","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2267795","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2267916","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2267925","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2268295","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2270103","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2271648","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2271796","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2272793","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2273141","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2273148","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2273180","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2275558","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2275661","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2275690","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2277171","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2278220","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2278270","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2278447","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2281217","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2281317","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2281704","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2281720","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2281807","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2281847","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2282324","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2282345","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2282354","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2282355","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2282356","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2282357","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2282366","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2282401","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2282422","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2282440","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2282508","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2282511","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2282648","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2282669","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2282676","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2282757","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2282764","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2282851","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2282890","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2282903","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2282918","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2283389","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2283424","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2284271","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2284511","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2284515","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2284545","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2284596","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2284628","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2284630","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2284634","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2293247","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2293270","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2293273","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2293304","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2293377","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2293408","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2293423","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2293440","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2293441","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2293658","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2294313","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2297471","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2297473","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2297478","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2297488","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2297515","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2297538","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2297542","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2297543","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2297544","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2297556","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2297561","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2297572","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2297573","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2297579","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2297581","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2297582","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2297589","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2297706","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2297909","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2298079","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2298140","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2298177","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2298640","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2299452","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2300296","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2300297","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2300381","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2300402","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2300407","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2300408","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2300409","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2300414","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2300429","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2300430","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2300434","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2300439","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2300440","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2300448","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2300492","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2300533","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2300552","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2300709","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2300713","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2301477","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2301489","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2301496","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2301522","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2301543","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2301544","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2303077","tags":["report"]},{"url":"https://issues.redhat.com/browse/RHEL-31515","tags":["article"]},{"url":"https://security.access.redhat.com/data/csaf/v2/advisories/2024/rhsa-2024_7000.json","tags":["advisory"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2021-46984","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2021-46984","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024022824-CVE-2021-46984-e55e@gregkh/T/#u","tags":["article"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2021-47097","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2021-47097","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024030415-CVE-2021-47097-e7f4@gregkh/T","tags":["article"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2021-47101","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2021-47101","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024030415-CVE-2021-47101-f3fa@gregkh/T","tags":["article"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2021-47287","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2021-47287","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024052121-CVE-2021-47287-6345@gregkh/T","tags":["article"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2021-47289","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2021-47289","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024052122-CVE-2021-47289-7cbb@gregkh/T","tags":["article"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2021-47321","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2021-47321","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024052132-CVE-2021-47321-1b9b@gregkh/T","tags":["article"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2021-47338","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2021-47338","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024052137-CVE-2021-47338-cd10@gregkh/T","tags":["article"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2021-47352","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2021-47352","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024052141-CVE-2021-47352-df50@gregkh/T","tags":["article"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2021-47383","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2021-47383","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024052144-CVE-2021-47383-a8f4@gregkh/T","tags":["article"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2021-47384","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2021-47384","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024052144-CVE-2021-47384-f311@gregkh/T","tags":["article"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2021-47385","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2021-47385","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024052144-CVE-2021-47385-a7e7@gregkh/T","tags":["article"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2021-47386","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2021-47386","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024052145-CVE-2021-47386-2701@gregkh/T","tags":["article"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2021-47393","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2021-47393","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024052147-CVE-2021-47393-ea1c@gregkh/T","tags":["article"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2021-47412","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2021-47412","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024052152-CVE-2021-47412-b362@gregkh/T","tags":["article"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2021-47432","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2021-47432","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024052143-CVE-2021-47432-5e69@gregkh/T","tags":["article"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2021-47441","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2021-47441","tags":["advisory"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2021-47455","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2021-47455","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024052244-CVE-2021-47455-c4a1@gregkh/T","tags":["article"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2021-47466","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2021-47466","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024052227-CVE-2021-47466-ff03@gregkh/T","tags":["article"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2021-47497","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2021-47497","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024052242-CVE-2021-47497-449e@gregkh/T","tags":["article"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2021-47527","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2021-47527","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024052435-CVE-2021-47527-e6f5@gregkh/T","tags":["article"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2021-47560","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2021-47560","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024052451-CVE-2021-47560-4a52@gregkh/T","tags":["article"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2021-47582","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2021-47582","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024061916-CVE-2021-47582-69aa@gregkh/T","tags":["article"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2021-47609","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2021-47609","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024061907-CVE-2021-47609-5ebf@gregkh/T","tags":["article"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-48619","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-48619","tags":["advisory"]},{"url":"https://cdn.kernel.org/pub/linux/kernel/v5.x/ChangeLog-5.17.10","tags":["article"]},{"url":"https://github.com/torvalds/linux/commit/409353cbe9fe48f6bc196114c442b1cff05a39bc","tags":["article"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-48754","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-48754","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024062006-CVE-2022-48754-4012@gregkh/T","tags":["article"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-48760","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-48760","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024062008-CVE-2022-48760-b80e@gregkh/T","tags":["article"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-48804","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-48804","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024071645-CVE-2022-48804-f191@gregkh/T","tags":["article"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-48836","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-48836","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024071620-CVE-2022-48836-fb3d@gregkh/T","tags":["article"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-48866","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-48866","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024071629-CVE-2022-48866-93bd@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-49226","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2347965","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-49226","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-49226","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025022622-CVE-2022-49226-b30c@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-49316","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2347650","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-49316","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-49316","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025022636-CVE-2022-49316-3e10@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-50072","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2373562","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-50072","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-50072","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025061853-CVE-2022-50072-de2b@gregkh/T","tags":["article"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-6040","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-6040","tags":["advisory"]},{"url":"https://www.openwall.com/lists/oss-security/2024/01/12/1","tags":["article"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-52470","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-52470","tags":["advisory"]},{"url":"https://git.kernel.org/stable/c/0b813a6a0087451cb702b6eb841f10856f49d088","tags":["article"]},{"url":"https://git.kernel.org/stable/c/14bbfaa5df273b26cde6707f6e655585700e6fe1","tags":["article"]},{"url":"https://git.kernel.org/stable/c/21b1645660717d6126dd4866c850fcc5c4703a41","tags":["article"]},{"url":"https://git.kernel.org/stable/c/57ca7984806d79b38af528de88fd803babf27feb","tags":["article"]},{"url":"https://git.kernel.org/stable/c/5d12c5d75f7c78b83a738025947651ec5c95b4d4","tags":["article"]},{"url":"https://git.kernel.org/stable/c/7a2464fac80d42f6f8819fed97a553e9c2f43310","tags":["article"]},{"url":"https://git.kernel.org/stable/c/c4ff55408187f2595066967047363ca84e76db85","tags":["article"]},{"url":"https://git.kernel.org/stable/c/fb2d8bc9b5e55848b8a7c3c028e2ee8d49f28f97","tags":["article"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-52476","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-52476","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024022921-CVE-2023-52476-e307@gregkh/T/#u","tags":["article"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-52478","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-52478","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024022921-CVE-2023-52478-c0a1@gregkh/T/#u","tags":["article"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-52522","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-52522","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024030253-CVE-2023-52522-6abd@gregkh/T/#u","tags":["article"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-52605","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-52605","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024030647-CVE-2023-52605-292a@gregkh/T","tags":["article"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-52683","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-52683","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024051751-CVE-2023-52683-f280@gregkh/T","tags":["article"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-52798","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-52798","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024052158-CVE-2023-52798-374e@gregkh/T","tags":["article"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-52800","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-52800","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024052159-CVE-2023-52800-63da@gregkh/T","tags":["article"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-52809","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-52809","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024052102-CVE-2023-52809-f07c@gregkh/T","tags":["article"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-52817","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-52817","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024052104-CVE-2023-52817-ba29@gregkh/T","tags":["article"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-52840","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-52840","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024052111-CVE-2023-52840-8a3d@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-53847","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2420349","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-53847","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-53847","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025120959-CVE-2023-53847-1f94@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-54269","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2426013","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-54269","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-54269","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025123000-CVE-2023-54269-6fd7@gregkh/T","tags":["article"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-23848","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-23848","tags":["advisory"]},{"url":"https://lore.kernel.org/lkml/e9f42704-2f99-4f2c-ade5-f952e5fd53e5%40xs4all.nl/","tags":["article"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-26595","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-26595","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024022336-CVE-2024-26595-9a8d@gregkh/T/#u","tags":["article"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-26600","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-26600","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024022405-CVE-2024-26600-44a2@gregkh/T/#u","tags":["article"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-26638","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-26638","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/20240318101458.2835626-16-lee@kernel.org/T","tags":["article"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-26645","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-26645","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/20240326151722.1258576-4-lee@kernel.org/T","tags":["article"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-26649","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-26649","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/20240326175007.1388794-17-lee@kernel.org/T","tags":["article"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-26665","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-26665","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024040224-CVE-2024-26665-5daa@gregkh/T","tags":["article"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-26717","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-26717","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024040344-CVE-2024-26717-0d01@gregkh/T","tags":["article"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-26720","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-26720","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024040344-CVE-2024-26720-06fa@gregkh/T","tags":["article"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-26769","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-26769","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024040307-CVE-2024-26769-e9cc@gregkh/T","tags":["article"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-26846","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-26846","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024041717-CVE-2024-26846-9593@gregkh/T","tags":["article"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-26880","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-26880","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024041740-CVE-2024-26880-25d6@gregkh/T","tags":["article"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-26894","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-26894","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024041743-CVE-2024-26894-53ad@gregkh/T","tags":["article"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-26923","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-26923","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024042418-CVE-2024-26923-f7f6@gregkh/T","tags":["article"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-26939","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-26939","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024050124-CVE-2024-26939-5314@gregkh/T","tags":["article"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-27013","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-27013","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024050149-CVE-2024-27013-2c26@gregkh/T","tags":["article"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-27042","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-27042","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024050113-CVE-2024-27042-e812@gregkh/T","tags":["article"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-35809","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-35809","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024051740-CVE-2024-35809-4a4e@gregkh/T","tags":["article"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-35877","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-35877","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024051943-CVE-2024-35877-39e6@gregkh/T","tags":["article"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-35884","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-35884","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024051946-CVE-2024-35884-d4a4@gregkh/T","tags":["article"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-35944","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-35944","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024051920-CVE-2024-35944-a860@gregkh/T","tags":["article"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-35989","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-35989","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024052020-CVE-2024-35989-c5da@gregkh/T","tags":["article"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-36883","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-36883","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024053032-CVE-2024-36883-b892@gregkh/T","tags":["article"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-36901","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-36901","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024053035-CVE-2024-36901-fb16@gregkh/T","tags":["article"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-36902","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-36902","tags":["advisory"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-36919","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-36919","tags":["advisory"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-36920","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-36920","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024053039-CVE-2024-36920-b4a7@gregkh/T","tags":["article"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-36922","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-36922","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024053039-CVE-2024-36922-f0df@gregkh/T","tags":["article"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-36939","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-36939","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024053043-CVE-2024-36939-8453@gregkh/T","tags":["article"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-36953","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-36953","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024053040-CVE-2024-36953-fc12@gregkh/T","tags":["article"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-37356","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-37356","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024062137-CVE-2024-37356-cc7b@gregkh/T","tags":["article"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-38558","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-38558","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024061953-CVE-2024-38558-ddfd@gregkh/T","tags":["article"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-38559","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-38559","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024061953-CVE-2024-38559-3e03@gregkh/T","tags":["article"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-38570","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-38570","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024061956-CVE-2024-38570-a8ef@gregkh/T","tags":["article"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-38581","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-38581","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024061948-CVE-2024-38581-592d@gregkh/T","tags":["article"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-38619","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-38619","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024062035-CVE-2024-38619-97c7@gregkh/T","tags":["article"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-39471","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-39471","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024062501-CVE-2024-39471-3dee@gregkh/T","tags":["article"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-39499","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-39499","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024071203-CVE-2024-39499-ed0a@gregkh/T","tags":["article"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-39501","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-39501","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024071204-CVE-2024-39501-058b@gregkh/T","tags":["article"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-39506","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-39506","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024071205-CVE-2024-39506-b0cc@gregkh/T","tags":["article"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-40901","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-40901","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024071207-CVE-2024-40901-05c4@gregkh/T","tags":["article"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-40904","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-40904","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024071208-CVE-2024-40904-48b1@gregkh/T","tags":["article"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-40931","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-40931","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024071216-CVE-2024-40931-77b2@gregkh/T","tags":["article"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-40954","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-40954","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024071223-CVE-2024-40954-093b@gregkh/T","tags":["article"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-40958","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-40958","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024071225-CVE-2024-40958-8ed5@gregkh/T","tags":["article"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-40959","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024071225-CVE-2024-40959-228e@gregkh/T","tags":["article"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-40960","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-40960","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024071225-CVE-2024-40960-d46f@gregkh/T","tags":["article"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-40972","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-40972","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024071229-CVE-2024-40972-1569@gregkh/T","tags":["article"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-40977","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-40977","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024071230-CVE-2024-40977-07c8@gregkh/T","tags":["article"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-40988","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-40988","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024071249-CVE-2024-40988-490e@gregkh/T","tags":["article"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-40989","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-40989","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024071249-CVE-2024-40989-c8da@gregkh/T","tags":["article"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-40995","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-40995","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024071251-CVE-2024-40995-2a5c@gregkh/T","tags":["article"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-40997","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-40997","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024071251-CVE-2024-40997-df97@gregkh/T","tags":["article"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-40998","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-40998","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024071252-CVE-2024-40998-90d6@gregkh/T","tags":["article"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-41005","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-41005","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024071244-CVE-2024-41005-b2a5@gregkh/T","tags":["article"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-41007","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-41007","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024071513-CVE-2024-41007-777c@gregkh/T","tags":["article"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-41008","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-41008","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/20240716080357.2696435-2-lee@kernel.org/T","tags":["article"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-41012","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024072314-CVE-2024-41012-a1cf@gregkh/T","tags":["article"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-41013","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-41013","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024072908-CVE-2024-41013-2996@gregkh/T","tags":["article"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-41014","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-41014","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024072910-CVE-2024-41014-9186@gregkh/T","tags":["article"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-41023","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-41023","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024072917-CVE-2024-41023-32a0@gregkh/T","tags":["article"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-41035","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-41035","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024072922-CVE-2024-41035-5e6b@gregkh/T","tags":["article"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-41038","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-41038","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024072923-CVE-2024-41038-41ba@gregkh/T","tags":["article"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-41039","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-41039","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024072924-CVE-2024-41039-b3bc@gregkh/T","tags":["article"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-41040","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-41040","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024072924-CVE-2024-41040-63d5@gregkh/T","tags":["article"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-41044","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-41044","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024072925-CVE-2024-41044-5b26@gregkh/T","tags":["article"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-41055","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-41055","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024072928-CVE-2024-41055-5764@gregkh/T","tags":["article"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-41056","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-41056","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024072930-CVE-2024-41056-c324@gregkh/T","tags":["article"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-41060","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-41060","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024072905-CVE-2024-41060-b7de@gregkh/T","tags":["article"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-41064","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-41064","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024072907-CVE-2024-41064-6ecb@gregkh/T","tags":["article"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-41065","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-41065","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024072907-CVE-2024-41065-2501@gregkh/T","tags":["article"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-41071","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024072909-CVE-2024-41071-4eb6@gregkh/T","tags":["article"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-41097","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-41097","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024072954-CVE-2024-41097-248c@gregkh/T","tags":["article"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-42084","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-42084","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024072942-CVE-2024-42084-9283@gregkh/T","tags":["article"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-42090","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-42090","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024072946-CVE-2024-42090-5687@gregkh/T","tags":["article"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-42094","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-42094","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024072911-CVE-2024-42094-135f@gregkh/T","tags":["article"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-42096","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-42096","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024072911-CVE-2024-42096-67f3@gregkh/T","tags":["article"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-42114","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-42114","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024073022-CVE-2024-42114-4585@gregkh/T","tags":["article"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-42124","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-42124","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024073025-CVE-2024-42124-e4ad@gregkh/T","tags":["article"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-42131","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-42131","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024073027-CVE-2024-42131-2f7f@gregkh/T","tags":["article"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-42154","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-42154","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024073034-CVE-2024-42154-cf82@gregkh/T","tags":["article"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-42225","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-42225","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024073038-CVE-2024-42225-bdfa@gregkh/T","tags":["article"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-42226","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-42226","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024073038-CVE-2024-42226-fa39@gregkh/T","tags":["article"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-42228","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-42228","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024073038-CVE-2024-42228-86f5@gregkh/T","tags":["article"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2303505","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-42237","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024080740-CVE-2024-42237-eba4@gregkh/T","tags":["article"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2303506","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-42238","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024080740-CVE-2024-42238-a5fd@gregkh/T","tags":["article"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2303508","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-42240","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024080741-CVE-2024-42240-3d04@gregkh/T","tags":["article"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2303514","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-42246","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-42246","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024080742-CVE-2024-42246-0777@gregkh/T","tags":["article"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2305410","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-42265","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-42265","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024081737-CVE-2024-42265-a943@gregkh/T","tags":["article"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2305467","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-42322","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-42322","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024081755-CVE-2024-42322-e2ef@gregkh/T","tags":["article"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2305488","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-43830","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-43830","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024081727-CVE-2024-43830-3b85@gregkh/T","tags":["article"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2306365","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-43871","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024082136-CVE-2024-43871-c2cd@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-45026","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2311723","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-45026","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-45026","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024091110-CVE-2024-45026-eaa8@gregkh/T","tags":["article"]},{"url":"https://security.access.redhat.com/data/csaf/v2/advisories/2024/rhsa-2024_7001.json","tags":["advisory"]},{"url":"https://access.redhat.com/errata/RHSA-2024:8613","tags":["advisory"]},{"url":"https://access.redhat.com/security/updates/classification/#moderate","tags":["article"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2176140","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2268118","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2269189","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2272811","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2273109","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2275604","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2278176","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2284571","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2300422","tags":["report"]},{"url":"https://security.access.redhat.com/data/csaf/v2/advisories/2024/rhsa-2024_8613.json","tags":["advisory"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-50720","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2425047","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-50720","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-50720","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025122417-CVE-2022-50720-0297@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-1252","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-1252","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-1252","tags":["advisory"]},{"url":"https://lore.kernel.org/lkml/20211115165433.449951285@linuxfoundation.org/","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-52489","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-52489","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-52489","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/20240229155245.1571576-30-lee@kernel.org/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-2201","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-2201","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-2201","tags":["advisory"]},{"url":"https://download.vusec.net/papers/inspectre_sec24.pdf","tags":["article"]},{"url":"https://www.intel.com/content/www/us/en/developer/articles/technical/software-security-guidance/technical-documentation/branch-history-injection.html#inpage-nav-8","tags":["article"]},{"url":"https://www.openwall.com/lists/oss-security/2024/04/09/15","tags":["article"]},{"url":"https://www.vusec.net/projects/native-bhi/","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-26671","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-26671","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-26671","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024040219-CVE-2024-26671-2543@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-26686","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-26686","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-26686","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024040335-CVE-2024-26686-b22f@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-26826","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-26826","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-26826","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024041703-CVE-2024-26826-b984@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-26961","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-26961","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-26961","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024050129-CVE-2024-26961-408d@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-36889","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-36889","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-36889","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024053033-CVE-2024-36889-222d@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-41049","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-41049","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-41049","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024072927-CVE-2024-41049-bf28@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/errata/RHSA-2024:8614","tags":["advisory"]},{"url":"https://security.access.redhat.com/data/csaf/v2/advisories/2024/rhsa-2024_8614.json","tags":["advisory"]},{"url":"https://errata.rockylinux.org/RLSA-2024:7000","tags":["advisory"]},{"url":"https://errata.rockylinux.org/RLSA-2024:7001","tags":["advisory"]},{"url":"https://www.suse.com/support/update/announcement/2024/suse-su-20243190-1/","tags":["advisory"]},{"url":"https://bugzilla.suse.com/1193629","tags":["report"]},{"url":"https://bugzilla.suse.com/1194111","tags":["report"]},{"url":"https://bugzilla.suse.com/1194765","tags":["report"]},{"url":"https://bugzilla.suse.com/1194869","tags":["report"]},{"url":"https://bugzilla.suse.com/1196261","tags":["report"]},{"url":"https://bugzilla.suse.com/1196516","tags":["report"]},{"url":"https://bugzilla.suse.com/1196894","tags":["report"]},{"url":"https://bugzilla.suse.com/1198017","tags":["report"]},{"url":"https://bugzilla.suse.com/1203329","tags":["report"]},{"url":"https://bugzilla.suse.com/1203330","tags":["report"]},{"url":"https://bugzilla.suse.com/1203360","tags":["report"]},{"url":"https://bugzilla.suse.com/1205462","tags":["report"]},{"url":"https://bugzilla.suse.com/1206006","tags":["report"]},{"url":"https://bugzilla.suse.com/1206258","tags":["report"]},{"url":"https://bugzilla.suse.com/1206843","tags":["report"]},{"url":"https://bugzilla.suse.com/1207158","tags":["report"]},{"url":"https://bugzilla.suse.com/1208783","tags":["report"]},{"url":"https://bugzilla.suse.com/1210644","tags":["report"]},{"url":"https://bugzilla.suse.com/1213580","tags":["report"]},{"url":"https://bugzilla.suse.com/1213632","tags":["report"]},{"url":"https://bugzilla.suse.com/1214285","tags":["report"]},{"url":"https://bugzilla.suse.com/1216834","tags":["report"]},{"url":"https://bugzilla.suse.com/1220428","tags":["report"]},{"url":"https://bugzilla.suse.com/1220877","tags":["report"]},{"url":"https://bugzilla.suse.com/1220962","tags":["report"]},{"url":"https://bugzilla.suse.com/1221269","tags":["report"]},{"url":"https://bugzilla.suse.com/1221326","tags":["report"]},{"url":"https://bugzilla.suse.com/1221630","tags":["report"]},{"url":"https://bugzilla.suse.com/1221645","tags":["report"]},{"url":"https://bugzilla.suse.com/1222335","tags":["report"]},{"url":"https://bugzilla.suse.com/1222350","tags":["report"]},{"url":"https://bugzilla.suse.com/1222372","tags":["report"]},{"url":"https://bugzilla.suse.com/1222387","tags":["report"]},{"url":"https://bugzilla.suse.com/1222634","tags":["report"]},{"url":"https://bugzilla.suse.com/1222808","tags":["report"]},{"url":"https://bugzilla.suse.com/1222967","tags":["report"]},{"url":"https://bugzilla.suse.com/1223074","tags":["report"]},{"url":"https://bugzilla.suse.com/1223191","tags":["report"]},{"url":"https://bugzilla.suse.com/1223508","tags":["report"]},{"url":"https://bugzilla.suse.com/1223720","tags":["report"]},{"url":"https://bugzilla.suse.com/1223742","tags":["report"]},{"url":"https://bugzilla.suse.com/1223777","tags":["report"]},{"url":"https://bugzilla.suse.com/1223803","tags":["report"]},{"url":"https://bugzilla.suse.com/1223807","tags":["report"]},{"url":"https://bugzilla.suse.com/1224105","tags":["report"]},{"url":"https://bugzilla.suse.com/1224415","tags":["report"]},{"url":"https://bugzilla.suse.com/1224496","tags":["report"]},{"url":"https://bugzilla.suse.com/1224510","tags":["report"]},{"url":"https://bugzilla.suse.com/1224542","tags":["report"]},{"url":"https://bugzilla.suse.com/1224578","tags":["report"]},{"url":"https://bugzilla.suse.com/1224639","tags":["report"]},{"url":"https://bugzilla.suse.com/1225162","tags":["report"]},{"url":"https://bugzilla.suse.com/1225352","tags":["report"]},{"url":"https://bugzilla.suse.com/1225428","tags":["report"]},{"url":"https://bugzilla.suse.com/1225524","tags":["report"]},{"url":"https://bugzilla.suse.com/1225578","tags":["report"]},{"url":"https://bugzilla.suse.com/1225582","tags":["report"]},{"url":"https://bugzilla.suse.com/1225773","tags":["report"]},{"url":"https://bugzilla.suse.com/1225814","tags":["report"]},{"url":"https://bugzilla.suse.com/1225827","tags":["report"]},{"url":"https://bugzilla.suse.com/1225832","tags":["report"]},{"url":"https://bugzilla.suse.com/1225903","tags":["report"]},{"url":"https://bugzilla.suse.com/1226168","tags":["report"]},{"url":"https://bugzilla.suse.com/1226530","tags":["report"]},{"url":"https://bugzilla.suse.com/1226613","tags":["report"]},{"url":"https://bugzilla.suse.com/1226742","tags":["report"]},{"url":"https://bugzilla.suse.com/1226765","tags":["report"]},{"url":"https://bugzilla.suse.com/1226798","tags":["report"]},{"url":"https://bugzilla.suse.com/1226801","tags":["report"]},{"url":"https://bugzilla.suse.com/1226874","tags":["report"]},{"url":"https://bugzilla.suse.com/1226885","tags":["report"]},{"url":"https://bugzilla.suse.com/1227079","tags":["report"]},{"url":"https://bugzilla.suse.com/1227623","tags":["report"]},{"url":"https://bugzilla.suse.com/1227761","tags":["report"]},{"url":"https://bugzilla.suse.com/1227830","tags":["report"]},{"url":"https://bugzilla.suse.com/1227863","tags":["report"]},{"url":"https://bugzilla.suse.com/1227867","tags":["report"]},{"url":"https://bugzilla.suse.com/1227929","tags":["report"]},{"url":"https://bugzilla.suse.com/1227937","tags":["report"]},{"url":"https://bugzilla.suse.com/1227958","tags":["report"]},{"url":"https://bugzilla.suse.com/1228020","tags":["report"]},{"url":"https://bugzilla.suse.com/1228065","tags":["report"]},{"url":"https://bugzilla.suse.com/1228114","tags":["report"]},{"url":"https://bugzilla.suse.com/1228410","tags":["report"]},{"url":"https://bugzilla.suse.com/1228426","tags":["report"]},{"url":"https://bugzilla.suse.com/1228427","tags":["report"]},{"url":"https://bugzilla.suse.com/1228429","tags":["report"]},{"url":"https://bugzilla.suse.com/1228446","tags":["report"]},{"url":"https://bugzilla.suse.com/1228447","tags":["report"]},{"url":"https://bugzilla.suse.com/1228449","tags":["report"]},{"url":"https://bugzilla.suse.com/1228450","tags":["report"]},{"url":"https://bugzilla.suse.com/1228452","tags":["report"]},{"url":"https://bugzilla.suse.com/1228456","tags":["report"]},{"url":"https://bugzilla.suse.com/1228463","tags":["report"]},{"url":"https://bugzilla.suse.com/1228466","tags":["report"]},{"url":"https://bugzilla.suse.com/1228467","tags":["report"]},{"url":"https://bugzilla.suse.com/1228469","tags":["report"]},{"url":"https://bugzilla.suse.com/1228480","tags":["report"]},{"url":"https://bugzilla.suse.com/1228481","tags":["report"]},{"url":"https://bugzilla.suse.com/1228482","tags":["report"]},{"url":"https://bugzilla.suse.com/1228483","tags":["report"]},{"url":"https://bugzilla.suse.com/1228484","tags":["report"]},{"url":"https://bugzilla.suse.com/1228485","tags":["report"]},{"url":"https://bugzilla.suse.com/1228487","tags":["report"]},{"url":"https://bugzilla.suse.com/1228489","tags":["report"]},{"url":"https://bugzilla.suse.com/1228491","tags":["report"]},{"url":"https://bugzilla.suse.com/1228493","tags":["report"]},{"url":"https://bugzilla.suse.com/1228494","tags":["report"]},{"url":"https://bugzilla.suse.com/1228495","tags":["report"]},{"url":"https://bugzilla.suse.com/1228496","tags":["report"]},{"url":"https://bugzilla.suse.com/1228501","tags":["report"]},{"url":"https://bugzilla.suse.com/1228503","tags":["report"]},{"url":"https://bugzilla.suse.com/1228509","tags":["report"]},{"url":"https://bugzilla.suse.com/1228513","tags":["report"]},{"url":"https://bugzilla.suse.com/1228515","tags":["report"]},{"url":"https://bugzilla.suse.com/1228516","tags":["report"]},{"url":"https://bugzilla.suse.com/1228526","tags":["report"]},{"url":"https://bugzilla.suse.com/1228531","tags":["report"]},{"url":"https://bugzilla.suse.com/1228563","tags":["report"]},{"url":"https://bugzilla.suse.com/1228564","tags":["report"]},{"url":"https://bugzilla.suse.com/1228567","tags":["report"]},{"url":"https://bugzilla.suse.com/1228576","tags":["report"]},{"url":"https://bugzilla.suse.com/1228579","tags":["report"]},{"url":"https://bugzilla.suse.com/1228584","tags":["report"]},{"url":"https://bugzilla.suse.com/1228588","tags":["report"]},{"url":"https://bugzilla.suse.com/1228590","tags":["report"]},{"url":"https://bugzilla.suse.com/1228615","tags":["report"]},{"url":"https://bugzilla.suse.com/1228616","tags":["report"]},{"url":"https://bugzilla.suse.com/1228635","tags":["report"]},{"url":"https://bugzilla.suse.com/1228636","tags":["report"]},{"url":"https://bugzilla.suse.com/1228654","tags":["report"]},{"url":"https://bugzilla.suse.com/1228656","tags":["report"]},{"url":"https://bugzilla.suse.com/1228658","tags":["report"]},{"url":"https://bugzilla.suse.com/1228660","tags":["report"]},{"url":"https://bugzilla.suse.com/1228662","tags":["report"]},{"url":"https://bugzilla.suse.com/1228667","tags":["report"]},{"url":"https://bugzilla.suse.com/1228673","tags":["report"]},{"url":"https://bugzilla.suse.com/1228677","tags":["report"]},{"url":"https://bugzilla.suse.com/1228687","tags":["report"]},{"url":"https://bugzilla.suse.com/1228706","tags":["report"]},{"url":"https://bugzilla.suse.com/1228708","tags":["report"]},{"url":"https://bugzilla.suse.com/1228710","tags":["report"]},{"url":"https://bugzilla.suse.com/1228718","tags":["report"]},{"url":"https://bugzilla.suse.com/1228720","tags":["report"]},{"url":"https://bugzilla.suse.com/1228721","tags":["report"]},{"url":"https://bugzilla.suse.com/1228722","tags":["report"]},{"url":"https://bugzilla.suse.com/1228724","tags":["report"]},{"url":"https://bugzilla.suse.com/1228726","tags":["report"]},{"url":"https://bugzilla.suse.com/1228727","tags":["report"]},{"url":"https://bugzilla.suse.com/1228733","tags":["report"]},{"url":"https://bugzilla.suse.com/1228748","tags":["report"]},{"url":"https://bugzilla.suse.com/1228766","tags":["report"]},{"url":"https://bugzilla.suse.com/1228779","tags":["report"]},{"url":"https://bugzilla.suse.com/1228801","tags":["report"]},{"url":"https://bugzilla.suse.com/1228850","tags":["report"]},{"url":"https://bugzilla.suse.com/1228857","tags":["report"]},{"url":"https://bugzilla.suse.com/1228959","tags":["report"]},{"url":"https://bugzilla.suse.com/1228964","tags":["report"]},{"url":"https://bugzilla.suse.com/1228966","tags":["report"]},{"url":"https://bugzilla.suse.com/1228967","tags":["report"]},{"url":"https://bugzilla.suse.com/1228979","tags":["report"]},{"url":"https://bugzilla.suse.com/1228988","tags":["report"]},{"url":"https://bugzilla.suse.com/1228989","tags":["report"]},{"url":"https://bugzilla.suse.com/1228991","tags":["report"]},{"url":"https://bugzilla.suse.com/1228992","tags":["report"]},{"url":"https://bugzilla.suse.com/1229042","tags":["report"]},{"url":"https://bugzilla.suse.com/1229054","tags":["report"]},{"url":"https://bugzilla.suse.com/1229086","tags":["report"]},{"url":"https://bugzilla.suse.com/1229136","tags":["report"]},{"url":"https://bugzilla.suse.com/1229154","tags":["report"]},{"url":"https://bugzilla.suse.com/1229187","tags":["report"]},{"url":"https://bugzilla.suse.com/1229188","tags":["report"]},{"url":"https://bugzilla.suse.com/1229190","tags":["report"]},{"url":"https://bugzilla.suse.com/1229287","tags":["report"]},{"url":"https://bugzilla.suse.com/1229290","tags":["report"]},{"url":"https://bugzilla.suse.com/1229292","tags":["report"]},{"url":"https://bugzilla.suse.com/1229296","tags":["report"]},{"url":"https://bugzilla.suse.com/1229297","tags":["report"]},{"url":"https://bugzilla.suse.com/1229301","tags":["report"]},{"url":"https://bugzilla.suse.com/1229303","tags":["report"]},{"url":"https://bugzilla.suse.com/1229304","tags":["report"]},{"url":"https://bugzilla.suse.com/1229305","tags":["report"]},{"url":"https://bugzilla.suse.com/1229307","tags":["report"]},{"url":"https://bugzilla.suse.com/1229309","tags":["report"]},{"url":"https://bugzilla.suse.com/1229312","tags":["report"]},{"url":"https://bugzilla.suse.com/1229314","tags":["report"]},{"url":"https://bugzilla.suse.com/1229315","tags":["report"]},{"url":"https://bugzilla.suse.com/1229317","tags":["report"]},{"url":"https://bugzilla.suse.com/1229318","tags":["report"]},{"url":"https://bugzilla.suse.com/1229319","tags":["report"]},{"url":"https://bugzilla.suse.com/1229327","tags":["report"]},{"url":"https://bugzilla.suse.com/1229341","tags":["report"]},{"url":"https://bugzilla.suse.com/1229345","tags":["report"]},{"url":"https://bugzilla.suse.com/1229346","tags":["report"]},{"url":"https://bugzilla.suse.com/1229347","tags":["report"]},{"url":"https://bugzilla.suse.com/1229349","tags":["report"]},{"url":"https://bugzilla.suse.com/1229350","tags":["report"]},{"url":"https://bugzilla.suse.com/1229351","tags":["report"]},{"url":"https://bugzilla.suse.com/1229354","tags":["report"]},{"url":"https://bugzilla.suse.com/1229356","tags":["report"]},{"url":"https://bugzilla.suse.com/1229357","tags":["report"]},{"url":"https://bugzilla.suse.com/1229358","tags":["report"]},{"url":"https://bugzilla.suse.com/1229359","tags":["report"]},{"url":"https://bugzilla.suse.com/1229360","tags":["report"]},{"url":"https://bugzilla.suse.com/1229366","tags":["report"]},{"url":"https://bugzilla.suse.com/1229370","tags":["report"]},{"url":"https://bugzilla.suse.com/1229373","tags":["report"]},{"url":"https://bugzilla.suse.com/1229374","tags":["report"]},{"url":"https://bugzilla.suse.com/1229381","tags":["report"]},{"url":"https://bugzilla.suse.com/1229382","tags":["report"]},{"url":"https://bugzilla.suse.com/1229383","tags":["report"]},{"url":"https://bugzilla.suse.com/1229386","tags":["report"]},{"url":"https://bugzilla.suse.com/1229388","tags":["report"]},{"url":"https://bugzilla.suse.com/1229391","tags":["report"]},{"url":"https://bugzilla.suse.com/1229392","tags":["report"]},{"url":"https://bugzilla.suse.com/1229395","tags":["report"]},{"url":"https://bugzilla.suse.com/1229398","tags":["report"]},{"url":"https://bugzilla.suse.com/1229399","tags":["report"]},{"url":"https://bugzilla.suse.com/1229400","tags":["report"]},{"url":"https://bugzilla.suse.com/1229407","tags":["report"]},{"url":"https://bugzilla.suse.com/1229409","tags":["report"]},{"url":"https://bugzilla.suse.com/1229410","tags":["report"]},{"url":"https://bugzilla.suse.com/1229411","tags":["report"]},{"url":"https://bugzilla.suse.com/1229413","tags":["report"]},{"url":"https://bugzilla.suse.com/1229414","tags":["report"]},{"url":"https://bugzilla.suse.com/1229417","tags":["report"]},{"url":"https://bugzilla.suse.com/1229418","tags":["report"]},{"url":"https://bugzilla.suse.com/1229444","tags":["report"]},{"url":"https://bugzilla.suse.com/1229453","tags":["report"]},{"url":"https://bugzilla.suse.com/1229454","tags":["report"]},{"url":"https://bugzilla.suse.com/1229481","tags":["report"]},{"url":"https://bugzilla.suse.com/1229482","tags":["report"]},{"url":"https://bugzilla.suse.com/1229488","tags":["report"]},{"url":"https://bugzilla.suse.com/1229489","tags":["report"]},{"url":"https://bugzilla.suse.com/1229490","tags":["report"]},{"url":"https://bugzilla.suse.com/1229493","tags":["report"]},{"url":"https://bugzilla.suse.com/1229495","tags":["report"]},{"url":"https://bugzilla.suse.com/1229497","tags":["report"]},{"url":"https://bugzilla.suse.com/1229500","tags":["report"]},{"url":"https://bugzilla.suse.com/1229503","tags":["report"]},{"url":"https://bugzilla.suse.com/1229506","tags":["report"]},{"url":"https://bugzilla.suse.com/1229507","tags":["report"]},{"url":"https://bugzilla.suse.com/1229508","tags":["report"]},{"url":"https://bugzilla.suse.com/1229509","tags":["report"]},{"url":"https://bugzilla.suse.com/1229510","tags":["report"]},{"url":"https://bugzilla.suse.com/1229512","tags":["report"]},{"url":"https://bugzilla.suse.com/1229516","tags":["report"]},{"url":"https://bugzilla.suse.com/1229521","tags":["report"]},{"url":"https://bugzilla.suse.com/1229522","tags":["report"]},{"url":"https://bugzilla.suse.com/1229523","tags":["report"]},{"url":"https://bugzilla.suse.com/1229524","tags":["report"]},{"url":"https://bugzilla.suse.com/1229525","tags":["report"]},{"url":"https://bugzilla.suse.com/1229526","tags":["report"]},{"url":"https://bugzilla.suse.com/1229527","tags":["report"]},{"url":"https://bugzilla.suse.com/1229528","tags":["report"]},{"url":"https://bugzilla.suse.com/1229529","tags":["report"]},{"url":"https://bugzilla.suse.com/1229531","tags":["report"]},{"url":"https://bugzilla.suse.com/1229533","tags":["report"]},{"url":"https://bugzilla.suse.com/1229535","tags":["report"]},{"url":"https://bugzilla.suse.com/1229536","tags":["report"]},{"url":"https://bugzilla.suse.com/1229537","tags":["report"]},{"url":"https://bugzilla.suse.com/1229540","tags":["report"]},{"url":"https://bugzilla.suse.com/1229544","tags":["report"]},{"url":"https://bugzilla.suse.com/1229545","tags":["report"]},{"url":"https://bugzilla.suse.com/1229546","tags":["report"]},{"url":"https://bugzilla.suse.com/1229547","tags":["report"]},{"url":"https://bugzilla.suse.com/1229548","tags":["report"]},{"url":"https://bugzilla.suse.com/1229554","tags":["report"]},{"url":"https://bugzilla.suse.com/1229557","tags":["report"]},{"url":"https://bugzilla.suse.com/1229558","tags":["report"]},{"url":"https://bugzilla.suse.com/1229559","tags":["report"]},{"url":"https://bugzilla.suse.com/1229560","tags":["report"]},{"url":"https://bugzilla.suse.com/1229562","tags":["report"]},{"url":"https://bugzilla.suse.com/1229564","tags":["report"]},{"url":"https://bugzilla.suse.com/1229565","tags":["report"]},{"url":"https://bugzilla.suse.com/1229566","tags":["report"]},{"url":"https://bugzilla.suse.com/1229568","tags":["report"]},{"url":"https://bugzilla.suse.com/1229569","tags":["report"]},{"url":"https://bugzilla.suse.com/1229572","tags":["report"]},{"url":"https://bugzilla.suse.com/1229573","tags":["report"]},{"url":"https://bugzilla.suse.com/1229576","tags":["report"]},{"url":"https://bugzilla.suse.com/1229581","tags":["report"]},{"url":"https://bugzilla.suse.com/1229588","tags":["report"]},{"url":"https://bugzilla.suse.com/1229598","tags":["report"]},{"url":"https://bugzilla.suse.com/1229603","tags":["report"]},{"url":"https://bugzilla.suse.com/1229604","tags":["report"]},{"url":"https://bugzilla.suse.com/1229605","tags":["report"]},{"url":"https://bugzilla.suse.com/1229608","tags":["report"]},{"url":"https://bugzilla.suse.com/1229611","tags":["report"]},{"url":"https://bugzilla.suse.com/1229612","tags":["report"]},{"url":"https://bugzilla.suse.com/1229613","tags":["report"]},{"url":"https://bugzilla.suse.com/1229614","tags":["report"]},{"url":"https://bugzilla.suse.com/1229615","tags":["report"]},{"url":"https://bugzilla.suse.com/1229616","tags":["report"]},{"url":"https://bugzilla.suse.com/1229617","tags":["report"]},{"url":"https://bugzilla.suse.com/1229620","tags":["report"]},{"url":"https://bugzilla.suse.com/1229622","tags":["report"]},{"url":"https://bugzilla.suse.com/1229623","tags":["report"]},{"url":"https://bugzilla.suse.com/1229624","tags":["report"]},{"url":"https://bugzilla.suse.com/1229625","tags":["report"]},{"url":"https://bugzilla.suse.com/1229626","tags":["report"]},{"url":"https://bugzilla.suse.com/1229628","tags":["report"]},{"url":"https://bugzilla.suse.com/1229629","tags":["report"]},{"url":"https://bugzilla.suse.com/1229630","tags":["report"]},{"url":"https://bugzilla.suse.com/1229631","tags":["report"]},{"url":"https://bugzilla.suse.com/1229632","tags":["report"]},{"url":"https://bugzilla.suse.com/1229635","tags":["report"]},{"url":"https://bugzilla.suse.com/1229636","tags":["report"]},{"url":"https://bugzilla.suse.com/1229637","tags":["report"]},{"url":"https://bugzilla.suse.com/1229638","tags":["report"]},{"url":"https://bugzilla.suse.com/1229639","tags":["report"]},{"url":"https://bugzilla.suse.com/1229641","tags":["report"]},{"url":"https://bugzilla.suse.com/1229642","tags":["report"]},{"url":"https://bugzilla.suse.com/1229643","tags":["report"]},{"url":"https://bugzilla.suse.com/1229645","tags":["report"]},{"url":"https://bugzilla.suse.com/1229657","tags":["report"]},{"url":"https://bugzilla.suse.com/1229658","tags":["report"]},{"url":"https://bugzilla.suse.com/1229662","tags":["report"]},{"url":"https://bugzilla.suse.com/1229664","tags":["report"]},{"url":"https://bugzilla.suse.com/1229707","tags":["report"]},{"url":"https://bugzilla.suse.com/1229739","tags":["report"]},{"url":"https://bugzilla.suse.com/1229743","tags":["report"]},{"url":"https://bugzilla.suse.com/1229746","tags":["report"]},{"url":"https://bugzilla.suse.com/1229754","tags":["report"]},{"url":"https://bugzilla.suse.com/1229755","tags":["report"]},{"url":"https://bugzilla.suse.com/1229756","tags":["report"]},{"url":"https://bugzilla.suse.com/1229759","tags":["report"]},{"url":"https://bugzilla.suse.com/1229761","tags":["report"]},{"url":"https://bugzilla.suse.com/1229767","tags":["report"]},{"url":"https://bugzilla.suse.com/1229768","tags":["report"]},{"url":"https://bugzilla.suse.com/1229781","tags":["report"]},{"url":"https://bugzilla.suse.com/1229784","tags":["report"]},{"url":"https://bugzilla.suse.com/1229787","tags":["report"]},{"url":"https://bugzilla.suse.com/1229788","tags":["report"]},{"url":"https://bugzilla.suse.com/1229789","tags":["report"]},{"url":"https://bugzilla.suse.com/1229792","tags":["report"]},{"url":"https://bugzilla.suse.com/1229820","tags":["report"]},{"url":"https://www.suse.com/security/cve/CVE-2021-4441","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-47106","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-47517","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-47546","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-38457","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-40133","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-48645","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-48706","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-48808","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-48865","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-48868","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-48869","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-48870","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-48871","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-48872","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-48873","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-48875","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-48878","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-48880","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-48881","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-48882","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-48883","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-48884","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-48885","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-48886","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-48887","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-48888","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-48889","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-48890","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-48891","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-48893","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-48896","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-48898","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-48899","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-48903","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-48904","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-48905","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-48906","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-48907","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-48909","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-48910","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-48912","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-48913","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-48914","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-48915","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-48916","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-48917","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-48918","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-48919","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-48920","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-48921","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-48923","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-48924","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-48925","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-48926","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-48927","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-48928","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-48929","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-48930","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-48931","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-48932","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-48934","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-48937","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-48938","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-48939","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-48940","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-48941","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-48942","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-48943","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-3610","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-52458","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-52489","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-52498","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-52581","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-52859","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-52887","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-52889","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-52893","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-52894","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-52896","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-52898","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-52899","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-52900","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-52901","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-52904","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-52905","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-52906","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-52907","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-52908","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-52909","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-52910","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-52911","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-52912","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-52913","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-26631","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-26668","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-26669","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-26677","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-26735","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-26808","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-26812","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-26835","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-26851","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-27010","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-27011","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-27016","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-27024","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-27079","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-27403","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-31076","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-35897","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-35902","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-35945","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-35971","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-36009","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-36013","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-36270","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-36286","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-36489","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-36929","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-36933","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-36936","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-36962","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-38554","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-38602","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-38662","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-39489","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-40905","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-40978","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-40980","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-40995","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-41000","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-41007","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-41009","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-41011","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-41016","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-41020","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-41022","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-41035","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-41036","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-41038","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-41039","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-41042","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-41045","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-41056","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-41060","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-41062","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-41065","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-41068","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-41073","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-41079","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-41080","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-41087","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-41088","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-41089","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-41092","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-41093","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-41095","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-41097","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-41098","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-42069","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-42074","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-42076","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-42077","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-42080","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-42082","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-42085","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-42086","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-42087","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-42089","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-42090","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-42092","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-42095","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-42097","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-42098","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-42101","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-42104","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-42106","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-42107","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-42110","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-42114","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-42115","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-42119","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-42120","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-42121","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-42126","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-42127","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-42130","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-42137","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-42139","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-42142","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-42143","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-42148","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-42152","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-42155","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-42156","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-42157","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-42158","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-42162","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-42223","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-42225","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-42228","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-42229","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-42230","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-42232","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-42236","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-42237","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-42238","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-42239","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-42240","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-42244","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-42246","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-42247","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-42268","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-42271","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-42274","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-42276","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-42277","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-42280","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-42281","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-42283","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-42284","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-42285","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-42286","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-42287","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-42288","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-42289","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-42291","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-42292","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-42295","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-42301","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-42302","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-42308","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-42309","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-42310","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-42311","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-42312","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-42313","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-42315","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-42318","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-42319","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-42320","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-42322","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-43816","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-43818","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-43819","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-43821","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-43823","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-43829","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-43830","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-43831","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-43834","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-43837","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-43839","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-43841","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-43842","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-43846","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-43849","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-43853","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-43854","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-43856","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-43858","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-43860","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-43861","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-43863","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-43866","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-43867","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-43871","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-43872","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-43873","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-43879","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-43880","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-43882","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-43883","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-43884","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-43889","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-43892","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-43893","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-43894","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-43895","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-43899","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-43900","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-43902","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-43903","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-43904","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-43905","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-43907","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-43908","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-43909","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-44938","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-44939","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-44947","tags":["web"]},{"url":"https://www.suse.com/support/update/announcement/2024/suse-su-20243194-1/","tags":["advisory"]},{"url":"https://bugzilla.suse.com/1012628","tags":["report"]},{"url":"https://bugzilla.suse.com/1193454","tags":["report"]},{"url":"https://bugzilla.suse.com/1213123","tags":["report"]},{"url":"https://bugzilla.suse.com/1215199","tags":["report"]},{"url":"https://bugzilla.suse.com/1220066","tags":["report"]},{"url":"https://bugzilla.suse.com/1220252","tags":["report"]},{"url":"https://bugzilla.suse.com/1221652","tags":["report"]},{"url":"https://bugzilla.suse.com/1221857","tags":["report"]},{"url":"https://bugzilla.suse.com/1222254","tags":["report"]},{"url":"https://bugzilla.suse.com/1222364","tags":["report"]},{"url":"https://bugzilla.suse.com/1222433","tags":["report"]},{"url":"https://bugzilla.suse.com/1222434","tags":["report"]},{"url":"https://bugzilla.suse.com/1222463","tags":["report"]},{"url":"https://bugzilla.suse.com/1222625","tags":["report"]},{"url":"https://bugzilla.suse.com/1222633","tags":["report"]},{"url":"https://bugzilla.suse.com/1222973","tags":["report"]},{"url":"https://bugzilla.suse.com/1223053","tags":["report"]},{"url":"https://bugzilla.suse.com/1223395","tags":["report"]},{"url":"https://bugzilla.suse.com/1223635","tags":["report"]},{"url":"https://bugzilla.suse.com/1223731","tags":["report"]},{"url":"https://bugzilla.suse.com/1223763","tags":["report"]},{"url":"https://bugzilla.suse.com/1223767","tags":["report"]},{"url":"https://bugzilla.suse.com/1224485","tags":["report"]},{"url":"https://bugzilla.suse.com/1224535","tags":["report"]},{"url":"https://bugzilla.suse.com/1224631","tags":["report"]},{"url":"https://bugzilla.suse.com/1224636","tags":["report"]},{"url":"https://bugzilla.suse.com/1224690","tags":["report"]},{"url":"https://bugzilla.suse.com/1224694","tags":["report"]},{"url":"https://bugzilla.suse.com/1224700","tags":["report"]},{"url":"https://bugzilla.suse.com/1224711","tags":["report"]},{"url":"https://bugzilla.suse.com/1225475","tags":["report"]},{"url":"https://bugzilla.suse.com/1225607","tags":["report"]},{"url":"https://bugzilla.suse.com/1225717","tags":["report"]},{"url":"https://bugzilla.suse.com/1225718","tags":["report"]},{"url":"https://bugzilla.suse.com/1225744","tags":["report"]},{"url":"https://bugzilla.suse.com/1225745","tags":["report"]},{"url":"https://bugzilla.suse.com/1225751","tags":["report"]},{"url":"https://bugzilla.suse.com/1225838","tags":["report"]},{"url":"https://bugzilla.suse.com/1226031","tags":["report"]},{"url":"https://bugzilla.suse.com/1226127","tags":["report"]},{"url":"https://bugzilla.suse.com/1226502","tags":["report"]},{"url":"https://bugzilla.suse.com/1226588","tags":["report"]},{"url":"https://bugzilla.suse.com/1226604","tags":["report"]},{"url":"https://bugzilla.suse.com/1226743","tags":["report"]},{"url":"https://bugzilla.suse.com/1226751","tags":["report"]},{"url":"https://bugzilla.suse.com/1226834","tags":["report"]},{"url":"https://bugzilla.suse.com/1226920","tags":["report"]},{"url":"https://bugzilla.suse.com/1227149","tags":["report"]},{"url":"https://bugzilla.suse.com/1227182","tags":["report"]},{"url":"https://bugzilla.suse.com/1227383","tags":["report"]},{"url":"https://bugzilla.suse.com/1227437","tags":["report"]},{"url":"https://bugzilla.suse.com/1227492","tags":["report"]},{"url":"https://bugzilla.suse.com/1227493","tags":["report"]},{"url":"https://bugzilla.suse.com/1227494","tags":["report"]},{"url":"https://bugzilla.suse.com/1227618","tags":["report"]},{"url":"https://bugzilla.suse.com/1227620","tags":["report"]},{"url":"https://bugzilla.suse.com/1227627","tags":["report"]},{"url":"https://bugzilla.suse.com/1227634","tags":["report"]},{"url":"https://bugzilla.suse.com/1227706","tags":["report"]},{"url":"https://bugzilla.suse.com/1227722","tags":["report"]},{"url":"https://bugzilla.suse.com/1227724","tags":["report"]},{"url":"https://bugzilla.suse.com/1227725","tags":["report"]},{"url":"https://bugzilla.suse.com/1227728","tags":["report"]},{"url":"https://bugzilla.suse.com/1227729","tags":["report"]},{"url":"https://bugzilla.suse.com/1227732","tags":["report"]},{"url":"https://bugzilla.suse.com/1227733","tags":["report"]},{"url":"https://bugzilla.suse.com/1227734","tags":["report"]},{"url":"https://bugzilla.suse.com/1227747","tags":["report"]},{"url":"https://bugzilla.suse.com/1227750","tags":["report"]},{"url":"https://bugzilla.suse.com/1227754","tags":["report"]},{"url":"https://bugzilla.suse.com/1227758","tags":["report"]},{"url":"https://bugzilla.suse.com/1227760","tags":["report"]},{"url":"https://bugzilla.suse.com/1227764","tags":["report"]},{"url":"https://bugzilla.suse.com/1227766","tags":["report"]},{"url":"https://bugzilla.suse.com/1227770","tags":["report"]},{"url":"https://bugzilla.suse.com/1227771","tags":["report"]},{"url":"https://bugzilla.suse.com/1227772","tags":["report"]},{"url":"https://bugzilla.suse.com/1227774","tags":["report"]},{"url":"https://bugzilla.suse.com/1227781","tags":["report"]},{"url":"https://bugzilla.suse.com/1227784","tags":["report"]},{"url":"https://bugzilla.suse.com/1227785","tags":["report"]},{"url":"https://bugzilla.suse.com/1227787","tags":["report"]},{"url":"https://bugzilla.suse.com/1227790","tags":["report"]},{"url":"https://bugzilla.suse.com/1227791","tags":["report"]},{"url":"https://bugzilla.suse.com/1227792","tags":["report"]},{"url":"https://bugzilla.suse.com/1227796","tags":["report"]},{"url":"https://bugzilla.suse.com/1227798","tags":["report"]},{"url":"https://bugzilla.suse.com/1227799","tags":["report"]},{"url":"https://bugzilla.suse.com/1227802","tags":["report"]},{"url":"https://bugzilla.suse.com/1227808","tags":["report"]},{"url":"https://bugzilla.suse.com/1227810","tags":["report"]},{"url":"https://bugzilla.suse.com/1227811","tags":["report"]},{"url":"https://bugzilla.suse.com/1227812","tags":["report"]},{"url":"https://bugzilla.suse.com/1227815","tags":["report"]},{"url":"https://bugzilla.suse.com/1227816","tags":["report"]},{"url":"https://bugzilla.suse.com/1227818","tags":["report"]},{"url":"https://bugzilla.suse.com/1227820","tags":["report"]},{"url":"https://bugzilla.suse.com/1227823","tags":["report"]},{"url":"https://bugzilla.suse.com/1227824","tags":["report"]},{"url":"https://bugzilla.suse.com/1227826","tags":["report"]},{"url":"https://bugzilla.suse.com/1227828","tags":["report"]},{"url":"https://bugzilla.suse.com/1227829","tags":["report"]},{"url":"https://bugzilla.suse.com/1227832","tags":["report"]},{"url":"https://bugzilla.suse.com/1227833","tags":["report"]},{"url":"https://bugzilla.suse.com/1227834","tags":["report"]},{"url":"https://bugzilla.suse.com/1227839","tags":["report"]},{"url":"https://bugzilla.suse.com/1227840","tags":["report"]},{"url":"https://bugzilla.suse.com/1227846","tags":["report"]},{"url":"https://bugzilla.suse.com/1227849","tags":["report"]},{"url":"https://bugzilla.suse.com/1227851","tags":["report"]},{"url":"https://bugzilla.suse.com/1227853","tags":["report"]},{"url":"https://bugzilla.suse.com/1227864","tags":["report"]},{"url":"https://bugzilla.suse.com/1227865","tags":["report"]},{"url":"https://bugzilla.suse.com/1227869","tags":["report"]},{"url":"https://bugzilla.suse.com/1227870","tags":["report"]},{"url":"https://bugzilla.suse.com/1227883","tags":["report"]},{"url":"https://bugzilla.suse.com/1227884","tags":["report"]},{"url":"https://bugzilla.suse.com/1227891","tags":["report"]},{"url":"https://bugzilla.suse.com/1227893","tags":["report"]},{"url":"https://bugzilla.suse.com/1227950","tags":["report"]},{"url":"https://bugzilla.suse.com/1227957","tags":["report"]},{"url":"https://bugzilla.suse.com/1227981","tags":["report"]},{"url":"https://bugzilla.suse.com/1228021","tags":["report"]},{"url":"https://bugzilla.suse.com/1228192","tags":["report"]},{"url":"https://bugzilla.suse.com/1228195","tags":["report"]},{"url":"https://bugzilla.suse.com/1228202","tags":["report"]},{"url":"https://bugzilla.suse.com/1228235","tags":["report"]},{"url":"https://bugzilla.suse.com/1228236","tags":["report"]},{"url":"https://bugzilla.suse.com/1228237","tags":["report"]},{"url":"https://bugzilla.suse.com/1228247","tags":["report"]},{"url":"https://bugzilla.suse.com/1228321","tags":["report"]},{"url":"https://bugzilla.suse.com/1228409","tags":["report"]},{"url":"https://bugzilla.suse.com/1228457","tags":["report"]},{"url":"https://bugzilla.suse.com/1228458","tags":["report"]},{"url":"https://bugzilla.suse.com/1228459","tags":["report"]},{"url":"https://bugzilla.suse.com/1228460","tags":["report"]},{"url":"https://bugzilla.suse.com/1228462","tags":["report"]},{"url":"https://bugzilla.suse.com/1228468","tags":["report"]},{"url":"https://bugzilla.suse.com/1228470","tags":["report"]},{"url":"https://bugzilla.suse.com/1228472","tags":["report"]},{"url":"https://bugzilla.suse.com/1228479","tags":["report"]},{"url":"https://bugzilla.suse.com/1228486","tags":["report"]},{"url":"https://bugzilla.suse.com/1228492","tags":["report"]},{"url":"https://bugzilla.suse.com/1228499","tags":["report"]},{"url":"https://bugzilla.suse.com/1228500","tags":["report"]},{"url":"https://bugzilla.suse.com/1228502","tags":["report"]},{"url":"https://bugzilla.suse.com/1228505","tags":["report"]},{"url":"https://bugzilla.suse.com/1228508","tags":["report"]},{"url":"https://bugzilla.suse.com/1228510","tags":["report"]},{"url":"https://bugzilla.suse.com/1228511","tags":["report"]},{"url":"https://bugzilla.suse.com/1228518","tags":["report"]},{"url":"https://bugzilla.suse.com/1228520","tags":["report"]},{"url":"https://bugzilla.suse.com/1228525","tags":["report"]},{"url":"https://bugzilla.suse.com/1228527","tags":["report"]},{"url":"https://bugzilla.suse.com/1228530","tags":["report"]},{"url":"https://bugzilla.suse.com/1228539","tags":["report"]},{"url":"https://bugzilla.suse.com/1228561","tags":["report"]},{"url":"https://bugzilla.suse.com/1228565","tags":["report"]},{"url":"https://bugzilla.suse.com/1228568","tags":["report"]},{"url":"https://bugzilla.suse.com/1228572","tags":["report"]},{"url":"https://bugzilla.suse.com/1228580","tags":["report"]},{"url":"https://bugzilla.suse.com/1228581","tags":["report"]},{"url":"https://bugzilla.suse.com/1228582","tags":["report"]},{"url":"https://bugzilla.suse.com/1228586","tags":["report"]},{"url":"https://bugzilla.suse.com/1228591","tags":["report"]},{"url":"https://bugzilla.suse.com/1228599","tags":["report"]},{"url":"https://bugzilla.suse.com/1228617","tags":["report"]},{"url":"https://bugzilla.suse.com/1228625","tags":["report"]},{"url":"https://bugzilla.suse.com/1228626","tags":["report"]},{"url":"https://bugzilla.suse.com/1228633","tags":["report"]},{"url":"https://bugzilla.suse.com/1228640","tags":["report"]},{"url":"https://bugzilla.suse.com/1228643","tags":["report"]},{"url":"https://bugzilla.suse.com/1228644","tags":["report"]},{"url":"https://bugzilla.suse.com/1228646","tags":["report"]},{"url":"https://bugzilla.suse.com/1228649","tags":["report"]},{"url":"https://bugzilla.suse.com/1228650","tags":["report"]},{"url":"https://bugzilla.suse.com/1228655","tags":["report"]},{"url":"https://bugzilla.suse.com/1228665","tags":["report"]},{"url":"https://bugzilla.suse.com/1228666","tags":["report"]},{"url":"https://bugzilla.suse.com/1228672","tags":["report"]},{"url":"https://bugzilla.suse.com/1228674","tags":["report"]},{"url":"https://bugzilla.suse.com/1228680","tags":["report"]},{"url":"https://bugzilla.suse.com/1228705","tags":["report"]},{"url":"https://bugzilla.suse.com/1228707","tags":["report"]},{"url":"https://bugzilla.suse.com/1228709","tags":["report"]},{"url":"https://bugzilla.suse.com/1228723","tags":["report"]},{"url":"https://bugzilla.suse.com/1228737","tags":["report"]},{"url":"https://bugzilla.suse.com/1228743","tags":["report"]},{"url":"https://bugzilla.suse.com/1228754","tags":["report"]},{"url":"https://bugzilla.suse.com/1228756","tags":["report"]},{"url":"https://bugzilla.suse.com/1228757","tags":["report"]},{"url":"https://bugzilla.suse.com/1228758","tags":["report"]},{"url":"https://bugzilla.suse.com/1228764","tags":["report"]},{"url":"https://bugzilla.suse.com/1228849","tags":["report"]},{"url":"https://bugzilla.suse.com/1228973","tags":["report"]},{"url":"https://bugzilla.suse.com/1228977","tags":["report"]},{"url":"https://bugzilla.suse.com/1228978","tags":["report"]},{"url":"https://bugzilla.suse.com/1228986","tags":["report"]},{"url":"https://bugzilla.suse.com/1229005","tags":["report"]},{"url":"https://bugzilla.suse.com/1229024","tags":["report"]},{"url":"https://bugzilla.suse.com/1229045","tags":["report"]},{"url":"https://bugzilla.suse.com/1229046","tags":["report"]},{"url":"https://bugzilla.suse.com/1229056","tags":["report"]},{"url":"https://bugzilla.suse.com/1229134","tags":["report"]},{"url":"https://bugzilla.suse.com/1229156","tags":["report"]},{"url":"https://bugzilla.suse.com/1229160","tags":["report"]},{"url":"https://bugzilla.suse.com/1229167","tags":["report"]},{"url":"https://bugzilla.suse.com/1229168","tags":["report"]},{"url":"https://bugzilla.suse.com/1229169","tags":["report"]},{"url":"https://bugzilla.suse.com/1229170","tags":["report"]},{"url":"https://bugzilla.suse.com/1229171","tags":["report"]},{"url":"https://bugzilla.suse.com/1229172","tags":["report"]},{"url":"https://bugzilla.suse.com/1229173","tags":["report"]},{"url":"https://bugzilla.suse.com/1229174","tags":["report"]},{"url":"https://bugzilla.suse.com/1229239","tags":["report"]},{"url":"https://bugzilla.suse.com/1229240","tags":["report"]},{"url":"https://bugzilla.suse.com/1229241","tags":["report"]},{"url":"https://bugzilla.suse.com/1229243","tags":["report"]},{"url":"https://bugzilla.suse.com/1229244","tags":["report"]},{"url":"https://bugzilla.suse.com/1229245","tags":["report"]},{"url":"https://bugzilla.suse.com/1229246","tags":["report"]},{"url":"https://bugzilla.suse.com/1229247","tags":["report"]},{"url":"https://bugzilla.suse.com/1229248","tags":["report"]},{"url":"https://bugzilla.suse.com/1229249","tags":["report"]},{"url":"https://bugzilla.suse.com/1229250","tags":["report"]},{"url":"https://bugzilla.suse.com/1229251","tags":["report"]},{"url":"https://bugzilla.suse.com/1229252","tags":["report"]},{"url":"https://bugzilla.suse.com/1229253","tags":["report"]},{"url":"https://bugzilla.suse.com/1229254","tags":["report"]},{"url":"https://bugzilla.suse.com/1229255","tags":["report"]},{"url":"https://bugzilla.suse.com/1229256","tags":["report"]},{"url":"https://bugzilla.suse.com/1229291","tags":["report"]},{"url":"https://bugzilla.suse.com/1229294","tags":["report"]},{"url":"https://bugzilla.suse.com/1229298","tags":["report"]},{"url":"https://bugzilla.suse.com/1229299","tags":["report"]},{"url":"https://bugzilla.suse.com/1229313","tags":["report"]},{"url":"https://bugzilla.suse.com/1229316","tags":["report"]},{"url":"https://bugzilla.suse.com/1229320","tags":["report"]},{"url":"https://bugzilla.suse.com/1229342","tags":["report"]},{"url":"https://bugzilla.suse.com/1229344","tags":["report"]},{"url":"https://bugzilla.suse.com/1229353","tags":["report"]},{"url":"https://bugzilla.suse.com/1229355","tags":["report"]},{"url":"https://bugzilla.suse.com/1229365","tags":["report"]},{"url":"https://bugzilla.suse.com/1229369","tags":["report"]},{"url":"https://bugzilla.suse.com/1229379","tags":["report"]},{"url":"https://bugzilla.suse.com/1229390","tags":["report"]},{"url":"https://bugzilla.suse.com/1229402","tags":["report"]},{"url":"https://bugzilla.suse.com/1229403","tags":["report"]},{"url":"https://bugzilla.suse.com/1229404","tags":["report"]},{"url":"https://bugzilla.suse.com/1229451","tags":["report"]},{"url":"https://bugzilla.suse.com/1229452","tags":["report"]},{"url":"https://bugzilla.suse.com/1229455","tags":["report"]},{"url":"https://bugzilla.suse.com/1229456","tags":["report"]},{"url":"https://bugzilla.suse.com/1229480","tags":["report"]},{"url":"https://bugzilla.suse.com/1229484","tags":["report"]},{"url":"https://bugzilla.suse.com/1229485","tags":["report"]},{"url":"https://bugzilla.suse.com/1229486","tags":["report"]},{"url":"https://bugzilla.suse.com/1229487","tags":["report"]},{"url":"https://bugzilla.suse.com/1229496","tags":["report"]},{"url":"https://bugzilla.suse.com/1229747","tags":["report"]},{"url":"https://bugzilla.suse.com/1229752","tags":["report"]},{"url":"https://bugzilla.suse.com/1229785","tags":["report"]},{"url":"https://bugzilla.suse.com/1229827","tags":["report"]},{"url":"https://bugzilla.suse.com/1229830","tags":["report"]},{"url":"https://bugzilla.suse.com/1229837","tags":["report"]},{"url":"https://bugzilla.suse.com/1229940","tags":["report"]},{"url":"https://bugzilla.suse.com/1230056","tags":["report"]},{"url":"https://www.suse.com/security/cve/CVE-2023-52668","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-52688","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-52735","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-52885","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-52886","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-26590","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-26637","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-26682","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-26683","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-26691","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-26809","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-26837","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-26849","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-26889","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-26920","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-26944","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-26976","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-27049","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-27050","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-27433","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-27437","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-35854","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-35855","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-35913","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-35939","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-35949","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-36288","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-36881","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-36907","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-36909","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-36910","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-36911","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-36939","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-36970","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-36979","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-38548","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-38563","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-38609","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-39476","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-39483","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-39484","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-39486","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-39488","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-39491","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-39493","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-39497","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-39499","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-39500","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-39501","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-39505","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-39506","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-39508","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-39509","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-39510","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-40899","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-40900","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-40902","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-40903","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-40904","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-40909","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-40910","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-40911","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-40912","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-40913","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-40916","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-40920","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-40921","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-40922","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-40924","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-40926","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-40927","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-40929","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-40930","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-40932","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-40934","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-40936","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-40938","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-40939","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-40941","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-40942","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-40943","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-40944","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-40945","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-40954","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-40956","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-40957","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-40958","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-40959","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-40962","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-40964","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-40967","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-40976","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-40977","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-40981","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-40982","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-40984","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-40987","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-40988","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-40989","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-40990","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-40992","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-40994","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-40997","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-41001","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-41002","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-41004","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-41010","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-41012","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-41015","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-41024","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-41025","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-41028","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-41032","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-41037","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-41040","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-41041","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-41044","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-41048","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-41049","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-41050","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-41051","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-41057","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-41058","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-41059","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-41061","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-41063","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-41064","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-41066","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-41069","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-41070","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-41071","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-41072","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-41074","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-41075","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-41076","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-41078","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-41081","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-41084","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-41094","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-41096","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-42064","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-42070","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-42073","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-42079","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-42093","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-42096","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-42105","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-42109","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-42113","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-42117","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-42122","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-42124","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-42125","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-42131","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-42132","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-42133","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-42136","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-42138","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-42141","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-42144","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-42145","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-42147","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-42153","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-42159","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-42161","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-42224","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-42226","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-42227","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-42241","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-42245","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-42250","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-42253","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-42259","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-42269","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-42270","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-42278","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-42279","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-42290","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-42298","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-42303","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-42314","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-42316","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-43817","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-43824","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-43825","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-43826","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-43833","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-43840","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-43847","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-43850","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-43851","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-43855","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-43864","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-43874","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-43875","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-43876","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-43877","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-43881","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-43885","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-43897","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-43906","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-43911","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-43912","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-44931","tags":["web"]},{"url":"https://www.suse.com/support/update/announcement/2024/suse-su-20243195-1/","tags":["advisory"]},{"url":"https://bugzilla.suse.com/1219596","tags":["report"]},{"url":"https://bugzilla.suse.com/1222777","tags":["report"]},{"url":"https://bugzilla.suse.com/1225461","tags":["report"]},{"url":"https://bugzilla.suse.com/1225474","tags":["report"]},{"url":"https://www.suse.com/security/cve/CVE-2023-52756","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-52766","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-52800","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-52802","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-26758","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-26767","tags":["web"]},{"url":"https://www.suse.com/support/update/announcement/2024/suse-su-20243209-1/","tags":["advisory"]},{"url":"https://www.suse.com/support/update/announcement/2024/suse-su-20243383-1/","tags":["advisory"]},{"url":"https://bugzilla.suse.com/1230350","tags":["report"]},{"url":"https://bugzilla.suse.com/1230413","tags":["report"]},{"url":"https://www.suse.com/support/update/announcement/2024/suse-su-20243483-1/","tags":["advisory"]},{"url":"https://www.suse.com/security/cve/CVE-2021-4204","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-0500","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-23222","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-4382","tags":["web"]},{"url":"https://www.suse.com/support/update/announcement/2025/suse-su-202520044-1/","tags":["advisory"]},{"url":"https://bugzilla.suse.com/1228971","tags":["report"]},{"url":"https://www.suse.com/support/update/announcement/2025/suse-su-202520047-1/","tags":["advisory"]},{"url":"https://bugzilla.suse.com/1229025","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-42152","tags":["report"]},{"url":"https://git.kernel.org/linus/c758b77d4a0a0ed3a1292b3fd7a2aeccd1a169a4","tags":["report"]},{"url":"https://ubuntu.com/security/notices/USN-7007-1","tags":["advisory"]},{"url":"https://ubuntu.com/security/notices/USN-7009-1","tags":["advisory"]},{"url":"https://ubuntu.com/security/notices/USN-7019-1","tags":["advisory"]},{"url":"https://ubuntu.com/security/notices/USN-7007-2","tags":["advisory"]},{"url":"https://ubuntu.com/security/notices/USN-7007-3","tags":["advisory"]},{"url":"https://ubuntu.com/security/notices/USN-7009-2","tags":["advisory"]},{"url":"https://ubuntu.com/security/notices/USN-7089-1","tags":["advisory"]},{"url":"https://ubuntu.com/security/notices/USN-7090-1","tags":["advisory"]},{"url":"https://ubuntu.com/security/notices/USN-7089-2","tags":["advisory"]},{"url":"https://ubuntu.com/security/notices/USN-7089-3","tags":["advisory"]},{"url":"https://ubuntu.com/security/notices/USN-7095-1","tags":["advisory"]},{"url":"https://ubuntu.com/security/notices/USN-7089-4","tags":["advisory"]},{"url":"https://ubuntu.com/security/notices/USN-7089-5","tags":["advisory"]},{"url":"https://ubuntu.com/security/notices/USN-7089-6","tags":["advisory"]},{"url":"https://ubuntu.com/security/notices/USN-7089-7","tags":["advisory"]},{"url":"https://ubuntu.com/security/notices/USN-7156-1","tags":["advisory"]},{"url":"https://ubuntu.com/security/CVE-2022-48772","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2023-52884","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2023-52887","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-23848","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-25741","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-31076","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-33621","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-33847","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-34027","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-34777","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-35247","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-35927","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-36014","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-36015","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-36032","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-36270","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-36286","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-36489","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-36894","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-36971","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-36972","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-36974","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-36978","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-37078","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-37356","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-38381","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-38546","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-38547","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-38548","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-38549","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-38550","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-38552","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-38555","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-38558","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-38559","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-38560","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-38565","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-38567","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-38571","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-38573","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-38578","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-38579","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-38580","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-38582","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-38583","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-38586","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-38587","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-38588","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-38589","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-38590","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-38591","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-38596","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-38597","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-38598","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-38599","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-38601","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-38605","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-38607","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-38610","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-38612","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-38613","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-38615","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-38618","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-38619","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-38621","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-38623","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-38624","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-38627","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-38633","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-38634","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-38635","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-38637","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-38659","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-38661","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-38662","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-38780","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-39276","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-39277","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-39301","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-39466","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-39467","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-39468","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-39469","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-39471","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-39475","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-39480","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-39482","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-39487","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-39488","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-39489","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-39490","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-39493","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-39495","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-39499","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-39500","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-39501","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-39502","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-39503","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-39505","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-39506","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-39507","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-39509","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-40901","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-40902","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-40904","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-40905","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-40908","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-40911","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-40912","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-40914","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-40916","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-40927","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-40929","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-40931","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-40932","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-40934","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-40937","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-40941","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-40942","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-40943","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-40945","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-40954","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-40956","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-40957","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-40958","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-40959","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-40960","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-40961","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-40963","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-40967","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-40968","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-40970","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-40971","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-40974","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-40976","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-40978","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-40980","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-40981","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-40983","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-40984","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-40987","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-40988","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-40990","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-40994","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-40995","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-41000","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-41002","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-41004","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-41005","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-41006","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-41007","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-41027","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-41034","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-41035","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-41040","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-41041","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-41044","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-41046","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-41047","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-41048","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-41049","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-41055","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-41087","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-41089","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-41092","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-41093","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-41095","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-41097","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-42068","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-42070","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-42076","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-42077","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-42080","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-42082","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-42084","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-42085","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-42086","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-42087","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-42089","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-42090","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-42092","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-42093","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-42094","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-42095","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-42096","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-42097","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-42098","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-42101","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-42102","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-42104","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-42105","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-42106","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-42109","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-42115","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-42119","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-42120","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-42121","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-42124","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-42127","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-42130","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-42131","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-42137","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-42140","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-42145","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-42148","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-42153","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-42154","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-42157","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-42161","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-42223","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-42224","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-42225","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-42229","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-42232","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-42236","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-42240","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-42244","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-42247","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-42270","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2022-38096","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2022-48808","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2023-52488","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2023-52585","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2023-52629","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2023-52699","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2023-52752","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2023-52760","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2023-52880","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2023-52882","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-23307","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-24857","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-24858","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-24859","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-24861","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-25739","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-25742","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-26629","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-26642","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-26654","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-26680","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-26687","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-26810","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-26811","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-26812","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-26813","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-26814","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-26817","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-26828","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-26830","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-26886","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-26900","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-26921","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-26922","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-26923","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-26925","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-26926","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-26929","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-26931","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-26934","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-26935","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-26936","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-26937","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-26950","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-26951","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-26952","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-26955","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-26956","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-26957","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-26958","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-26960","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-26961","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-26964","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-26965","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-26966","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-26969","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-26970","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-26973","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-26974","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-26976","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-26977","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-26980","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-26981","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-26984","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-26988","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-26989","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-26993","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-26994","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-26996","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-26999","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-27000","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-27001","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-27004","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-27008","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-27009","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-27013","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-27015","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-27016","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-27017","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-27018","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-27019","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-27020","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-27059","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-27393","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-27395","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-27396","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-27398","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-27399","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-27401","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-27437","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-35785","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-35789","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-35791","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-35796","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-35804","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-35805","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-35806","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-35807","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-35809","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-35813","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-35815","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-35817","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-35819","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-35821","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-35822","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-35823","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-35825","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-35847","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-35848","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-35849","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-35851","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-35852","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-35853","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-35854","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-35855","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-35857","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-35871","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-35872","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-35877","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-35879","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-35884","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-35885","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-35886","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-35888","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-35890","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-35893","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-35895","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-35896","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-35897","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-35898","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-35899","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-35900","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-35902","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-35905","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-35907","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-35910","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-35912","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-35915","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-35922","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-35925","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-35930","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-35933","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-35934","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-35935","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-35936","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-35938","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-35940","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-35944","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-35947","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-35950","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-35955","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-35958","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-35960","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-35969","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-35970","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-35973","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-35976","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-35978","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-35982","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-35984","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-35988","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-35989","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-35990","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-35997","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-36004","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-36005","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-36006","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-36007","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-36008","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-36016","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-36017","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-36020","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-36025","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-36029","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-36031","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-36880","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-36883","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-36886","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-36889","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-36901","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-36902","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-36904","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-36905","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-36906","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-36916","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-36919","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-36928","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-36929","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-36931","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-36933","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-36934","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-36937","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-36938","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-36939","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-36940","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-36941","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-36946","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-36947","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-36950","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-36952","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-36953","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-36954","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-36955","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-36957","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-36959","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-36960","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-36964","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-36965","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-36967","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-36969","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-36975","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-38600","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-39292","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-39484","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2023-52888","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-39486","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-41010","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-41012","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-41015","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-41017","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-41018","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-41019","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-41020","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-41021","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-41022","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-41023","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-41025","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-41028","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-41029","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-41030","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-41031","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-41032","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-41033","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-41036","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-41037","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-41038","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-41039","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-41042","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-41045","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-41050","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-41051","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-41052","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-41053","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-41054","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-41056","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-41057","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-41058","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-41059","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-41060","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-41061","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-41062","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-41063","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-41064","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-41065","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-41066","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-41067","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-41068","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-41069","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-41070","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-41071","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-41072","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-41073","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-41074","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-41075","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-41076","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-41077","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-41078","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-41079","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-41080","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-41081","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-41082","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-41083","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-41084","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-41085","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-41086","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-41088","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-41090","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-41091","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-41094","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-41096","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-41098","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-42063","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-42064","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-42065","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-42066","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-42067","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-42069","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-42073","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-42074","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-42079","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-42088","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-42091","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-42100","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-42103","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-42108","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-42110","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-42111","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-42112","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-42113","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-42114","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-42117","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-42118","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-42126","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-42128","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-42129","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-42132","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-42133","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-42135","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-42136","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-42138","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-42141","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-42142","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-42144","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-42146","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-42147","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-42149","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-42150","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-42151","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-42155","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-42156","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-42158","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-42227","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-42230","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-42231","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-42234","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-42235","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-42237","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-42238","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-42239","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-42241","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-42243","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-42245","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-42246","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-42248","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-42250","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-42251","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-42252","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-42253","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-42271","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-42280","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-43855","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-43858","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-45001","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-45016","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2023-52889","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2023-52918","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-27022","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-39472","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-41009","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-42159","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-42160","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-42228","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-42258","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-42259","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-42260","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-42261","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-42262","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-42263","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-42264","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-42265","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-42267","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-42268","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-42269","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-42272","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-42273","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-42274","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-42276","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-42277","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-42278","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-42279","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-42281","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-42283","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-42284","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-42285","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-42286","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-42287","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-42288","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-42289","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-42290","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-42291","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-42292","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-42294","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-42295","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-42296","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-42297","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-42298","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-42299","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-42301","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-42302","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-42303","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-42304","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-42305","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-42306","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-42307","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-42309","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-42310","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-42311","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-42312","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-42313","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-42314","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-42315","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-42316","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-42317","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-42318","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-42319","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-42320","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-42321","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-42322","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-43817","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-43818","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-43819","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-43820","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-43821","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-43823","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-43824","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-43825","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-43826","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-43827","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-43828","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-43829","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-43830","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-43831","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-43832","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-43833","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-43834","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-43835","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-43837","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-43839","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-43840","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-43841","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-43842","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-43843","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-43845","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-43846","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-43847","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-43849","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-43850","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-43852","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-43853","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-43854","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-43856","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-43857","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-43859","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-43860","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-43861","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-43863","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-43864","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-43866","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-43867","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-43868","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-43869","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-43870","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-43871","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-43873","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-43875","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-43876","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-43877","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-43879","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-43880","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-43881","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-43882","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-43883","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-43884","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-43886","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-43887","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-43888","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-43889","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-43890","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-43891","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-43892","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-43893","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-43894","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-43895","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-43899","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-43900","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-43902","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-43904","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-43905","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-43906","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-43907","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-43908","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-43909","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-43910","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-43911","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-43912","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-43913","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-43914","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-44931","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-44934","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-44935","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-44937","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-44938","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-44939","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-44940","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-44941","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-44942","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-44943","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-44944","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-44946","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-44947","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-44948","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-44950","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-44953","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-44954","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-44956","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-44957","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-44958","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-44959","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-44960","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-44961","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-44962","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-44963","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-44965","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-44966","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-44967","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-44969","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-44970","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-44971","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-44972","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-44973","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-44974","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-44975","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-44977","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-44978","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-44979","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-44980","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-44982","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-44983","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-44984","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-44985","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-44986","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-44987","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-44988","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-44989","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-44990","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-44991","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-44993","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-44995","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-44996","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-44998","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-44999","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-45000","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-45002","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-45003","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-45005","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-45006","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-45007","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-45008","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-45009","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-45010","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-45011","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-45012","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-45013","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-45015","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-45017","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-45018","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-45019","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-45020","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-45021","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-45022","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-45025","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-45026","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-45027","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-45028","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-45029","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-45030","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-46672","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-46673","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-46675","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-46676","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-46677","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-46678","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-46679","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-46680","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-46681","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-46683","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-46685","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-46686","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-46687","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-46689","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-46691","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-46692","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-46693","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-46694","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-46695","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-46697","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-46698","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-46701","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-46702","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-46703","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-46705","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-46706","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-46707","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-46708","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-46709","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-46710","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-46711","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-46713","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-46714","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-46715","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-46716","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-46717","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-46718","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-46719","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-46720","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-46721","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-46722","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-46723","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-46724","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-46725","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-46726","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-46727","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-46728","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-46729","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-46730","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-46731","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-46732","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-46733","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-46735","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-46737","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-46738","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-46739","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-46740","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-46741","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-46743","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-46744","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-46745","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-46746","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-46747","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-46749","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-46750","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-46751","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-46752","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-46753","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-46754","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-46755","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-46756","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-46757","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-46758","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-46759","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-46760","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-46761","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-46762","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-46763","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-46765","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-46766","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-46767","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-46768","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-46770","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-46771","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-46772","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-46773","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-46774","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-46775","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-46776","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-46777","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-46778","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-46779","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-46780","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-46781","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-46782","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-46783","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-46784","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-46785","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-46786","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-46787","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-46788","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-46791","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-46792","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-46793","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-46794","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-46795","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-46797","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-46798","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-46800","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-46802","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-46803","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-46804","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-46805","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-46806","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-46807","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-46808","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-46809","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-46810","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-46811","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-46812","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-46813","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-46814","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-46815","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-46816","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-46817","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-46818","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-46819","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-46821","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-46822","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-46823","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-46824","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-46825","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-46826","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-46827","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-46828","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-46829","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-46830","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-46831","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-46832","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-46834","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-46835","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-46836","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-46838","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-46840","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-46841","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-46842","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-46843","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-46844","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-46845","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-46846","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-46848","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-46849","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-46850","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-46851","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-46852","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-46853","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-46854","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-46855","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-46857","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-46858","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-46859","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-46860","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-46861","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-46864","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-46866","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-46867","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-46868","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-46870","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-46871","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-47658","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-47659","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-47660","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-47661","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-47662","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-47663","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-47664","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-47665","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-47666","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-47667","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-47668","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-47669","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-47674","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-47683","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-49984","tags":["report"]}],"sources":{"cve":[{"id":"CVE-2024-42152","title":"nvmet: fix a possible leak when destroy a ctrl during qp establishment","description":"In the Linux kernel, the following vulnerability has been resolved:\n\nnvmet: fix a possible leak when destroy a ctrl during qp establishment\n\nIn nvmet_sq_destroy we capture sq-\u003ectrl early and if it is non-NULL we\nknow that a ctrl was allocated (in the admin connect request handler)\nand we need to release pending AERs, clear ctrl-\u003esqs and sq-\u003ectrl\n(for nvme-loop primarily), and drop the final reference on the ctrl.\n\nHowever, a small window is possible where nvmet_sq_destroy starts (as\na result of the client giving up and disconnecting) concurrently with\nthe nvme admin connect cmd (which may be in an early stage). But *before*\nkill_and_confirm of sq-\u003eref (i.e. the admin connect managed to get an sq\nlive reference). In this case, sq-\u003ectrl was allocated however after it was\ncaptured in a local variable in nvmet_sq_destroy.\nThis prevented the final reference drop on the ctrl.\n\nSolve this by re-capturing the sq-\u003ectrl after all inflight request has\ncompleted, where for sure sq-\u003ectrl reference is final, and move forward\nbased on that.\n\nThis issue was observed in an environment with many hosts connecting\nmultiple ctrls simoutanuosly, creating a delay in allocating a ctrl\nleading up to this race window.","status":"published","published":"2024-07-30T07:46:44.795Z","modified":"2026-08-05T11:35:52.904Z","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:34:03.00063Z"}],"euvd":[{"id":"EUVD-2024-39983","description":"In the Linux kernel, the following vulnerability has been resolved:\n\nnvmet: fix a possible leak when destroy a ctrl during qp establishment\n\nIn nvmet_sq_destroy we capture sq-\u003ectrl early and if it is non-NULL we\nknow that a ctrl was allocated (in the admin connect request handler)\nand we need to release pending AERs, clear ctrl-\u003esqs and sq-\u003ectrl\n(for nvme-loop primarily), and drop the final reference on the ctrl.\n\nHowever, a small window is possible where nvmet_sq_destroy starts (as\na result of the client giving up and disconnecting) concurrently with\nthe nvme admin connect cmd (which may be in an early stage). But *before*\nkill_and_confirm of sq-\u003eref (i.e. the admin connect managed to get an sq\nlive reference). In this case, sq-\u003ectrl was allocated however after it was\ncaptured in a local variable in nvmet_sq_destroy.\nThis prevented the final reference drop on the ctrl.\n\nSolve this by re-capturing the sq-\u003ectrl after all inflight request has\ncompleted, where for sure sq-\u003ectrl reference is final, and move forward\nbased on that.\n\nThis issue was observed in an environment with many hosts connecting\nmultiple ctrls simoutanuosly, creating a delay in allocating a ctrl\nleading up to this race window.","status":"published","published":"2024-07-30T07:46:44Z","modified":"2026-08-05T11:35:52Z","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:16.633095Z"}],"ghsa":[{"id":"GHSA-ghw9-6h55-qj7v","title":"In the Linux kernel, the following vulnerability has been resolved:\n\nnvmet: fix a possible leak...","description":"In the Linux kernel, the following vulnerability has been resolved:\n\nnvmet: fix a possible leak when destroy a ctrl during qp establishment\n\nIn nvmet_sq_destroy we capture sq-\u003ectrl early and if it is non-NULL we\nknow that a ctrl was allocated (in the admin connect request handler)\nand we need to release pending AERs, clear ctrl-\u003esqs and sq-\u003ectrl\n(for nvme-loop primarily), and drop the final reference on the ctrl.\n\nHowever, a small window is possible where nvmet_sq_destroy starts (as\na result of the client giving up and disconnecting) concurrently with\nthe nvme admin connect cmd (which may be in an early stage). But *before*\nkill_and_confirm of sq-\u003eref (i.e. the admin connect managed to get an sq\nlive reference). In this case, sq-\u003ectrl was allocated however after it was\ncaptured in a local variable in nvmet_sq_destroy.\nThis prevented the final reference drop on the ctrl.\n\nSolve this by re-capturing the sq-\u003ectrl after all inflight request has\ncompleted, where for sure sq-\u003ectrl reference is final, and move forward\nbased on that.\n\nThis issue was observed in an environment with many hosts connecting\nmultiple ctrls simoutanuosly, creating a delay in allocating a ctrl\nleading up to this race window.","status":"published","published":"2024-07-30T09:32:03Z","modified":"2025-11-04T00:31:08Z","cvss":[{"version":"3.1","score":4.7,"vector":"CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:H","level":"medium"}],"cwes":["CWE-401"],"updated_at":"2026-11-02T15:04:27.294317Z"}],"nvd":[{"id":"CVE-2024-42152","description":"In the Linux kernel, the following vulnerability has been resolved:\n\nnvmet: fix a possible leak when destroy a ctrl during qp establishment\n\nIn nvmet_sq_destroy we capture sq-\u003ectrl early and if it is non-NULL we\nknow that a ctrl was allocated (in the admin connect request handler)\nand we need to release pending AERs, clear ctrl-\u003esqs and sq-\u003ectrl\n(for nvme-loop primarily), and drop the final reference on the ctrl.\n\nHowever, a small window is possible where nvmet_sq_destroy starts (as\na result of the client giving up and disconnecting) concurrently with\nthe nvme admin connect cmd (which may be in an early stage). But *before*\nkill_and_confirm of sq-\u003eref (i.e. the admin connect managed to get an sq\nlive reference). In this case, sq-\u003ectrl was allocated however after it was\ncaptured in a local variable in nvmet_sq_destroy.\nThis prevented the final reference drop on the ctrl.\n\nSolve this by re-capturing the sq-\u003ectrl after all inflight request has\ncompleted, where for sure sq-\u003ectrl reference is final, and move forward\nbased on that.\n\nThis issue was observed in an environment with many hosts connecting\nmultiple ctrls simoutanuosly, creating a delay in allocating a ctrl\nleading up to this race window.","status":"published","published":"2024-07-30T08:15:06.763Z","modified":"2026-08-04T11:19:38.627Z","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":4.7,"vector":"CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:H","level":"medium","assessor":"primary"}],"cwes":["CWE-401"],"updated_at":"2026-11-02T14:10:15.933769Z"}],"osv":[{"id":"AZL-47660","title":"CVE-2024-42152 affecting package kernel for versions less than 6.6.43.1-7","description":"In the Linux kernel, the following vulnerability has been resolved:\n\nnvmet: fix a possible leak when destroy a ctrl during qp establishment\n\nIn nvmet_sq_destroy we capture sq-\u003ectrl early and if it is non-NULL we\nknow that a ctrl was allocated (in the admin connect request handler)\nand we need to release pending AERs, clear ctrl-\u003esqs and sq-\u003ectrl\n(for nvme-loop primarily), and drop the final reference on the ctrl.\n\nHowever, a small window is possible where nvmet_sq_destroy starts (as\na result of the client giving up and disconnecting) concurrently with\nthe nvme admin connect cmd (which may be in an early stage). But *before*\nkill_and_confirm of sq-\u003eref (i.e. the admin connect managed to get an sq\nlive reference). In this case, sq-\u003ectrl was allocated however after it was\ncaptured in a local variable in nvmet_sq_destroy.\nThis prevented the final reference drop on the ctrl.\n\nSolve this by re-capturing the sq-\u003ectrl after all inflight request has\ncompleted, where for sure sq-\u003ectrl reference is final, and move forward\nbased on that.\n\nThis issue was observed in an environment with many hosts connecting\nmultiple ctrls simoutanuosly, creating a delay in allocating a ctrl\nleading up to this race window.","status":"published","published":"2024-07-30T08:15:06Z","modified":"2026-04-21T04:55:17.758795Z","cvss":[{"version":"3.1","score":4.7,"vector":"CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:H","level":"medium"}],"updated_at":"2026-11-02T15:28:05.694722Z"},{"id":"AZL-47685","title":"CVE-2024-42152 affecting package kernel for versions less than 5.15.164.1-1","description":"In the Linux kernel, the following vulnerability has been resolved:\n\nnvmet: fix a possible leak when destroy a ctrl during qp establishment\n\nIn nvmet_sq_destroy we capture sq-\u003ectrl early and if it is non-NULL we\nknow that a ctrl was allocated (in the admin connect request handler)\nand we need to release pending AERs, clear ctrl-\u003esqs and sq-\u003ectrl\n(for nvme-loop primarily), and drop the final reference on the ctrl.\n\nHowever, a small window is possible where nvmet_sq_destroy starts (as\na result of the client giving up and disconnecting) concurrently with\nthe nvme admin connect cmd (which may be in an early stage). But *before*\nkill_and_confirm of sq-\u003eref (i.e. the admin connect managed to get an sq\nlive reference). In this case, sq-\u003ectrl was allocated however after it was\ncaptured in a local variable in nvmet_sq_destroy.\nThis prevented the final reference drop on the ctrl.\n\nSolve this by re-capturing the sq-\u003ectrl after all inflight request has\ncompleted, where for sure sq-\u003ectrl reference is final, and move forward\nbased on that.\n\nThis issue was observed in an environment with many hosts connecting\nmultiple ctrls simoutanuosly, creating a delay in allocating a ctrl\nleading up to this race window.","status":"published","published":"2024-07-30T08:15:06Z","modified":"2026-04-21T04:32:58.491981Z","cvss":[{"version":"3.1","score":4.7,"vector":"CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:H","level":"medium"}],"updated_at":"2026-11-02T15:28:05.694722Z"},{"id":"BELL-CVE-2024-42152","status":"published","published":"2024-07-31T05:59:07.760208Z","modified":"2026-01-26T09:36:51.613977Z","cvss":[{"version":"3.1","score":4.7,"vector":"CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:H","level":"medium"}],"updated_at":"2026-11-02T15:28:20.200735Z"},{"id":"CVE-2024-42152","title":"nvmet: fix a possible leak when destroy a ctrl during qp establishment","description":"In the Linux kernel, the following vulnerability has been resolved:\n\nnvmet: fix a possible leak when destroy a ctrl during qp establishment\n\nIn nvmet_sq_destroy we capture sq-\u003ectrl early and if it is non-NULL we\nknow that a ctrl was allocated (in the admin connect request handler)\nand we need to release pending AERs, clear ctrl-\u003esqs and sq-\u003ectrl\n(for nvme-loop primarily), and drop the final reference on the ctrl.\n\nHowever, a small window is possible where nvmet_sq_destroy starts (as\na result of the client giving up and disconnecting) concurrently with\nthe nvme admin connect cmd (which may be in an early stage). But *before*\nkill_and_confirm of sq-\u003eref (i.e. the admin connect managed to get an sq\nlive reference). In this case, sq-\u003ectrl was allocated however after it was\ncaptured in a local variable in nvmet_sq_destroy.\nThis prevented the final reference drop on the ctrl.\n\nSolve this by re-capturing the sq-\u003ectrl after all inflight request has\ncompleted, where for sure sq-\u003ectrl reference is final, and move forward\nbased on that.\n\nThis issue was observed in an environment with many hosts connecting\nmultiple ctrls simoutanuosly, creating a delay in allocating a ctrl\nleading up to this race window.","status":"published","published":"2024-07-30T07:46:44.795Z","modified":"2026-10-28T02:31:00.542615052Z","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:41.963899Z"},{"id":"DEBIAN-CVE-2024-42152","description":"In the Linux kernel, the following vulnerability has been resolved:  nvmet: fix a possible leak when destroy a ctrl during qp establishment  In nvmet_sq_destroy we capture sq-\u003ectrl early and if it is non-NULL we know that a ctrl was allocated (in the admin connect request handler) and we need to release pending AERs, clear ctrl-\u003esqs and sq-\u003ectrl (for nvme-loop primarily), and drop the final reference on the ctrl.  However, a small window is possible where nvmet_sq_destroy starts (as a result of the client giving up and disconnecting) concurrently with the nvme admin connect cmd (which may be in an early stage). But *before* kill_and_confirm of sq-\u003eref (i.e. the admin connect managed to get an sq live reference). In this case, sq-\u003ectrl was allocated however after it was captured in a local variable in nvmet_sq_destroy. This prevented the final reference drop on the ctrl.  Solve this by re-capturing the sq-\u003ectrl after all inflight request has completed, where for sure sq-\u003ectrl reference is final, and move forward based on that.  This issue was observed in an environment with many hosts connecting multiple ctrls simoutanuosly, creating a delay in allocating a ctrl leading up to this race window.","status":"published","published":"2024-07-30T08:15:06.763Z","modified":"2026-11-02T12:02:46.315289387Z","cvss":[{"version":"3.1","score":4.7,"vector":"CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:H","level":"medium"}],"updated_at":"2026-11-02T15:45:43.156294Z"},{"id":"OESA-2024-2124","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\nbna: ensure the copied buf is NUL terminated\r\n\r\nCurrently, we allocate a nbytes-sized kernel buffer and copy nbytes from\nuserspace to that buffer. Later, we use sscanf on this buffer but we don\u0026apos;t\nensure that the string is terminated inside the buffer, this can lead to\nOOB read when using sscanf. Fix this issue by using memdup_user_nul\ninstead of memdup_user.(CVE-2024-36934)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nnilfs2: fix potential kernel bug due to lack of writeback flag waiting\r\n\r\nDestructive writes to a block device on which nilfs2 is mounted can cause\na kernel bug in the folio/page writeback start routine or writeback end\nroutine (__folio_start_writeback in the log below):\r\n\r\n kernel BUG at mm/page-writeback.c:3070!\n Oops: invalid opcode: 0000 [#1] PREEMPT SMP KASAN PTI\n ...\n RIP: 0010:__folio_start_writeback+0xbaa/0x10e0\n Code: 25 ff 0f 00 00 0f 84 18 01 00 00 e8 40 ca c6 ff e9 17 f6 ff ff\n  e8 36 ca c6 ff 4c 89 f7 48 c7 c6 80 c0 12 84 e8 e7 b3 0f 00 90 \u0026lt;0f\u0026gt;\n  0b e8 1f ca c6 ff 4c 89 f7 48 c7 c6 a0 c6 12 84 e8 d0 b3 0f 00\n ...\n Call Trace:\n  \u0026lt;TASK\u0026gt;\n  nilfs_segctor_do_construct+0x4654/0x69d0 [nilfs2]\n  nilfs_segctor_construct+0x181/0x6b0 [nilfs2]\n  nilfs_segctor_thread+0x548/0x11c0 [nilfs2]\n  kthread+0x2f0/0x390\n  ret_from_fork+0x4b/0x80\n  ret_from_fork_asm+0x1a/0x30\n  \u0026lt;/TASK\u0026gt;\r\n\r\nThis is because when the log writer starts a writeback for segment summary\nblocks or a super root block that use the backing device\u0026apos;s page cache, it\ndoes not wait for the ongoing folio/page writeback, resulting in an\ninconsistent writeback state.\r\n\r\nFix this issue by waiting for ongoing writebacks when putting\nfolios/pages on the backing device into writeback state.(CVE-2024-37078)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nxfrm6: check ip6_dst_idev() return value in xfrm6_get_saddr()\r\n\r\nip6_dst_idev() can return NULL, xfrm6_get_saddr() must act accordingly.\r\n\r\nsyzbot reported:\r\n\r\nOops: general protection fault, probably for non-canonical address 0xdffffc0000000000: 0000 [#1] PREEMPT SMP KASAN PTI\nKASAN: null-ptr-deref in range [0x0000000000000000-0x0000000000000007]\nCPU: 1 PID: 12 Comm: kworker/u8:1 Not tainted 6.10.0-rc2-syzkaller-00383-gb8481381d4e2 #0\nHardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 04/02/2024\nWorkqueue: wg-kex-wg1 wg_packet_handshake_send_worker\n RIP: 0010:xfrm6_get_saddr+0x93/0x130 net/ipv6/xfrm6_policy.c:64\nCode: df 48 89 fa 48 c1 ea 03 80 3c 02 00 0f 85 97 00 00 00 4c 8b ab d8 00 00 00 48 b8 00 00 00 00 00 fc ff df 4c 89 ea 48 c1 ea 03 \u0026lt;80\u0026gt; 3c 02 00 0f 85 86 00 00 00 4d 8b 6d 00 e8 ca 13 47 01 48 b8 00\nRSP: 0018:ffffc90000117378 EFLAGS: 00010246\nRAX: dffffc0000000000 RBX: ffff88807b079dc0 RCX: ffffffff89a0d6d7\nRDX: 0000000000000000 RSI: ffffffff89a0d6e9 RDI: ffff88807b079e98\nRBP: ffff88807ad73248 R08: 0000000000000007 R09: fffffffffffff000\nR10: ffff88807b079dc0 R11: 0000000000000007 R12: ffffc90000117480\nR13: 0000000000000000 R14: 0000000000000000 R15: 0000000000000000\nFS:  0000000000000000(0000) GS:ffff8880b9300000(0000) knlGS:0000000000000000\nCS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033\nCR2: 00007f4586d00440 CR3: 0000000079042000 CR4: 00000000003506f0\nDR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000\nDR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400\nCall Trace:\n \u0026lt;TASK\u0026gt;\n  xfrm_get_saddr net/xfrm/xfrm_policy.c:2452 [inline]\n  xfrm_tmpl_resolve_one net/xfrm/xfrm_policy.c:2481 [inline]\n  xfrm_tmpl_resolve+0xa26/0xf10 net/xfrm/xfrm_policy.c:2541\n  xfrm_resolve_and_create_bundle+0x140/0x2570 net/xfrm/xfrm_policy.c:2835\n  xfrm_bundle_lookup net/xfrm/xfrm_policy.c:3070 [inline]\n  xfrm_lookup_with_ifid+0x4d1/0x1e60 net/xfrm/xfrm_policy.c:3201\n  xfrm_lookup net/xfrm/xfrm_policy.c:3298 [inline]\n  xfrm_lookup_route+0x3b/0x200 net/xfrm/xfrm_policy.c:3309\n  ip6_dst_lookup_flow+0x15c/0x1d0 net/ipv6/ip6_output.c:1256\n  send6+0x611/0xd20 drivers/net/wireguard/socket.c:139\n  wg_socket_send_skb_to_peer+0xf9/0x220 drivers/net/wireguard/socket.c:178\n  wg_socket_send_buffer_to_peer+0x12b/0x190 drivers/net/wireguard/socket.c:200\n  wg_packet_send_handshake_initiation+0x227/0x360 drivers/net/wireguard/send.c:40\n  wg_packet_handshake_send_worker+0x1c/0x30 drivers/net/wireguard/send.c:51\n  process_one_work+0x9fb/0x1b60 kernel/workqueue.c:3231\n  process_scheduled_works kernel/workqueue.c:3312 [inline]\n  worker_thread+0x6c8/0xf70 kernel/workqueue.c:3393\n  kthread+0x2c1/0x3a0 kernel/kthread.c:389\n  ret_from_fork+0x45/0x80 arch/x86/kernel/process.c:147\n  ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:244(CVE-2024-40959)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\ndrm/lima: mask irqs in timeout path before hard reset\r\n\r\nThere is a race condition in which a rendering job might take just long\nenough to trigger the drm sched job timeout handler but also still\ncomplete before the hard reset is done by the timeout handler.\nThis runs into race conditions not expected by the timeout handler.\nIn some very specific cases it currently may result in a refcount\nimbalance on lima_pm_idle, with a stack dump such as:\r\n\r\n[10136.669170] WARNING: CPU: 0 PID: 0 at drivers/gpu/drm/lima/lima_devfreq.c:205 lima_devfreq_record_idle+0xa0/0xb0\n...\n[10136.669459] pc : lima_devfreq_record_idle+0xa0/0xb0\n...\n[10136.669628] Call trace:\n[10136.669634]  lima_devfreq_record_idle+0xa0/0xb0\n[10136.669646]  lima_sched_pipe_task_done+0x5c/0xb0\n[10136.669656]  lima_gp_irq_handler+0xa8/0x120\n[10136.669666]  __handle_irq_event_percpu+0x48/0x160\n[10136.669679]  handle_irq_event+0x4c/0xc0\r\n\r\nWe can prevent that race condition entirely by masking the irqs at the\nbeginning of the timeout handler, at which point we give up on waiting\nfor that job entirely.\nThe irqs will be enabled again at the next hard reset which is already\ndone as a recovery by the timeout handler.(CVE-2024-40976)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nscsi: qedi: Fix crash while reading debugfs attribute\r\n\r\nThe qedi_dbg_do_not_recover_cmd_read() function invokes sprintf() directly\non a __user pointer, which results into the crash.\r\n\r\nTo fix this issue, use a small local stack buffer for sprintf() and then\ncall simple_read_from_buffer(), which in turns make the copy_to_user()\ncall.\r\n\r\nBUG: unable to handle page fault for address: 00007f4801111000\nPGD 8000000864df6067 P4D 8000000864df6067 PUD 864df7067 PMD 846028067 PTE 0\nOops: 0002 [#1] PREEMPT SMP PTI\nHardware name: HPE ProLiant DL380 Gen10/ProLiant DL380 Gen10, BIOS U30 06/15/2023\nRIP: 0010:memcpy_orig+0xcd/0x130\nRSP: 0018:ffffb7a18c3ffc40 EFLAGS: 00010202\nRAX: 00007f4801111000 RBX: 00007f4801111000 RCX: 000000000000000f\nRDX: 000000000000000f RSI: ffffffffc0bfd7a0 RDI: 00007f4801111000\nRBP: ffffffffc0bfd7a0 R08: 725f746f6e5f6f64 R09: 3d7265766f636572\nR10: ffffb7a18c3ffd08 R11: 0000000000000000 R12: 00007f4881110fff\nR13: 000000007fffffff R14: ffffb7a18c3ffca0 R15: ffffffffc0bfd7af\nFS:  00007f480118a740(0000) GS:ffff98e38af00000(0000) knlGS:0000000000000000\nCS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033\nCR2: 00007f4801111000 CR3: 0000000864b8e001 CR4: 00000000007706e0\nDR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000\nDR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400\nPKRU: 55555554\nCall Trace:\n \u0026lt;TASK\u0026gt;\n ? __die_body+0x1a/0x60\n ? page_fault_oops+0x183/0x510\n ? exc_page_fault+0x69/0x150\n ? asm_exc_page_fault+0x22/0x30\n ? memcpy_orig+0xcd/0x130\n vsnprintf+0x102/0x4c0\n sprintf+0x51/0x80\n qedi_dbg_do_not_recover_cmd_read+0x2f/0x50 [qedi 6bcfdeeecdea037da47069eca2ba717c84a77324]\n full_proxy_read+0x50/0x80\n vfs_read+0xa5/0x2e0\n ? folio_add_new_anon_rmap+0x44/0xa0\n ? set_pte_at+0x15/0x30\n ? do_pte_missing+0x426/0x7f0\n ksys_read+0xa5/0xe0\n do_syscall_64+0x58/0x80\n ? __count_memcg_events+0x46/0x90\n ? count_memcg_event_mm+0x3d/0x60\n ? handle_mm_fault+0x196/0x2f0\n ? do_user_addr_fault+0x267/0x890\n ? exc_page_fault+0x69/0x150\n entry_SYSCALL_64_after_hwframe+0x72/0xdc\nRIP: 0033:0x7f4800f20b4d(CVE-2024-40978)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nfilelock: Remove locks reliably when fcntl/close race is detected\r\n\r\nWhen fcntl_setlk() races with close(), it removes the created lock with\ndo_lock_file_wait().\nHowever, LSMs can allow the first do_lock_file_wait() that created the lock\nwhile denying the second do_lock_file_wait() that tries to remove the lock.\nSeparately, posix_lock_file() could also fail to\nremove a lock due to GFP_KERNEL allocation failure (when splitting a range\nin the middle).\r\n\r\nAfter the bug has been triggered, use-after-free reads will occur in\nlock_get_status() when userspace reads /proc/locks. This can likely be used\nto read arbitrary kernel memory, but can\u0026apos;t corrupt kernel memory.\r\n\r\nFix it by calling locks_remove_posix() instead, which is designed to\nreliably get rid of POSIX locks associated with the given file and\nfiles_struct and is also used by filp_flush().(CVE-2024-41012)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nocfs2: strict bound check before memcmp in ocfs2_xattr_find_entry()\r\n\r\nxattr in ocfs2 maybe \u0026apos;non-indexed\u0026apos;, which saved with additional space\nrequested.  It\u0026apos;s better to check if the memory is out of bound before\nmemcmp, although this possibility mainly comes from crafted poisonous\nimages.(CVE-2024-41016)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nASoC: SOF: Intel: hda: fix null deref on system suspend entry\r\n\r\nWhen system enters suspend with an active stream, SOF core\ncalls hw_params_upon_resume(). On Intel platforms with HDA DMA used\nto manage the link DMA, this leads to call chain of\r\n\r\n   hda_dsp_set_hw_params_upon_resume()\n -\u0026gt; hda_dsp_dais_suspend()\n -\u0026gt; hda_dai_suspend()\n -\u0026gt; hda_ipc4_post_trigger()\r\n\r\nA bug is hit in hda_dai_suspend() as hda_link_dma_cleanup() is run first,\nwhich clears hext_stream-\u0026gt;link_substream, and then hda_ipc4_post_trigger()\nis called with a NULL snd_pcm_substream pointer.(CVE-2024-41037)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nvfio/pci: Init the count variable in collecting hot-reset devices\r\n\r\nThe count variable is used without initialization, it results in mistakes\nin the device counting and crashes the userspace if the get hot reset info\npath is triggered.(CVE-2024-41052)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nwifi: mac80211: Avoid address calculations via out of bounds array indexing\r\n\r\nreq-\u0026gt;n_channels must be set before req-\u0026gt;channels[] can be used.\r\n\r\nThis patch fixes one of the issues encountered in [1].\r\n\r\n[   83.964255] UBSAN: array-index-out-of-bounds in net/mac80211/scan.c:364:4\n[   83.964258] index 0 is out of range for type \u0026apos;struct ieee80211_channel *[]\u0026apos;\n[...]\n[   83.964264] Call Trace:\n[   83.964267]  \u0026lt;TASK\u0026gt;\n[   83.964269]  dump_stack_lvl+0x3f/0xc0\n[   83.964274]  __ubsan_handle_out_of_bounds+0xec/0x110\n[   83.964278]  ieee80211_prep_hw_scan+0x2db/0x4b0\n[   83.964281]  __ieee80211_start_scan+0x601/0x990\n[   83.964291]  nl80211_trigger_scan+0x874/0x980\n[   83.964295]  genl_family_rcv_msg_doit+0xe8/0x160\n[   83.964298]  genl_rcv_msg+0x240/0x270\n[...]\r\n\r\n[1] https://bugzilla.kernel.org/show_bug.cgi?id=218810(CVE-2024-41071)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nnvme-fabrics: use reserved tag for reg read/write command\r\n\r\nIn some scenarios, if too many commands are issued by nvme command in\nthe same time by user tasks, this may exhaust all tags of admin_q. If\na reset (nvme reset or IO timeout) occurs before these commands finish,\nreconnect routine may fail to update nvme regs due to insufficient tags,\nwhich will cause kernel hang forever. In order to workaround this issue,\nmaybe we can let reg_read32()/reg_read64()/reg_write32() use reserved\ntags. This maybe safe for nvmf:\r\n\r\n1. For the disable ctrl path,  we will not issue connect command\n2. For the enable ctrl / fw activate path, since connect and reg_xx()\n   are called serially.\r\n\r\nSo the reserved tags may still be enough while reg_xx() use reserved tags.(CVE-2024-41082)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nata: libata-core: Fix null pointer dereference on error\r\n\r\nIf the ata_port_alloc() call in ata_host_alloc() fails,\nata_host_release() will get called.\r\n\r\nHowever, the code in ata_host_release() tries to free ata_port struct\nmembers unconditionally, which can lead to the following:\r\n\r\nBUG: unable to handle page fault for address: 0000000000003990\nPGD 0 P4D 0\nOops: Oops: 0000 [#1] PREEMPT SMP NOPTI\nCPU: 10 PID: 594 Comm: (udev-worker) Not tainted 6.10.0-rc5 #44\nHardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.16.3-2.fc40 04/01/2014\nRIP: 0010:ata_host_release.cold+0x2f/0x6e [libata]\nCode: e4 4d 63 f4 44 89 e2 48 c7 c6 90 ad 32 c0 48 c7 c7 d0 70 33 c0 49 83 c6 0e 41\nRSP: 0018:ffffc90000ebb968 EFLAGS: 00010246\nRAX: 0000000000000041 RBX: ffff88810fb52e78 RCX: 0000000000000000\nRDX: 0000000000000000 RSI: ffff88813b3218c0 RDI: ffff88813b3218c0\nRBP: ffff88810fb52e40 R08: 0000000000000000 R09: 6c65725f74736f68\nR10: ffffc90000ebb738 R11: 73692033203a746e R12: 0000000000000004\nR13: 0000000000000000 R14: 0000000000000011 R15: 0000000000000006\nFS:  00007f6cc55b9980(0000) GS:ffff88813b300000(0000) knlGS:0000000000000000\nCS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033\nCR2: 0000000000003990 CR3: 00000001122a2000 CR4: 0000000000750ef0\nPKRU: 55555554\nCall Trace:\n \u0026lt;TASK\u0026gt;\n ? __die_body.cold+0x19/0x27\n ? page_fault_oops+0x15a/0x2f0\n ? exc_page_fault+0x7e/0x180\n ? asm_exc_page_fault+0x26/0x30\n ? ata_host_release.cold+0x2f/0x6e [libata]\n ? ata_host_release.cold+0x2f/0x6e [libata]\n release_nodes+0x35/0xb0\n devres_release_group+0x113/0x140\n ata_host_alloc+0xed/0x120 [libata]\n ata_host_alloc_pinfo+0x14/0xa0 [libata]\n ahci_init_one+0x6c9/0xd20 [ahci]\r\n\r\nDo not access ata_port struct members unconditionally.(CVE-2024-41098)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nice: Fix improper extts handling\r\n\r\nExtts events are disabled and enabled by the application ts2phc.\nHowever, in case where the driver is removed when the application is\nrunning, a specific extts event remains enabled and can cause a kernel\ncrash.\nAs a side effect, when the driver is reloaded and application is started\nagain, remaining extts event for the channel from a previous run will\nkeep firing and the message \u0026quot;extts on unexpected channel\u0026quot; might be\nprinted to the user.\r\n\r\nTo avoid that, extts events shall be disabled when PTP is released.(CVE-2024-42139)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nnvmet: fix a possible leak when destroy a ctrl during qp establishment\r\n\r\nIn nvmet_sq_destroy we capture sq-\u0026gt;ctrl early and if it is non-NULL we\nknow that a ctrl was allocated (in the admin connect request handler)\nand we need to release pending AERs, clear ctrl-\u0026gt;sqs and sq-\u0026gt;ctrl\n(for nvme-loop primarily), and drop the final reference on the ctrl.\r\n\r\nHowever, a small window is possible where nvmet_sq_destroy starts (as\na result of the client giving up and disconnecting) concurrently with\nthe nvme admin connect cmd (which may be in an early stage). But *before*\nkill_and_confirm of sq-\u0026gt;ref (i.e. the admin connect managed to get an sq\nlive reference). In this case, sq-\u0026gt;ctrl was allocated however after it was\ncaptured in a local variable in nvmet_sq_destroy.\nThis prevented the final reference drop on the ctrl.\r\n\r\nSolve this by re-capturing the sq-\u0026gt;ctrl after all inflight request has\ncompleted, where for sure sq-\u0026gt;ctrl reference is final, and move forward\nbased on that.\r\n\r\nThis issue was observed in an environment with many hosts connecting\nmultiple ctrls simoutanuosly, creating a delay in allocating a ctrl\nleading up to this race window.(CVE-2024-42152)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\ni2c: pnx: Fix potential deadlock warning from del_timer_sync() call in isr\r\n\r\nWhen del_timer_sync() is called in an interrupt context it throws a warning\nbecause of potential deadlock. The timer is used only to exit from\nwait_for_completion() after a timeout so replacing the call with\nwait_for_completion_timeout() allows to remove the problematic timer and\nits related functions altogether.(CVE-2024-42153)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nmm: fix crashes from deferred split racing folio migration\r\n\r\nEven on 6.10-rc6, I\u0026apos;ve been seeing elusive \u0026quot;Bad page state\u0026quot;s (often on\nflags when freeing, yet the flags shown are not bad: PG_locked had been\nset and cleared??), and VM_BUG_ON_PAGE(page_ref_count(page) == 0)s from\ndeferred_split_scan()\u0026apos;s folio_put(), and a variety of other BUG and WARN\nsymptoms implying double free by deferred split and large folio migration.\r\n\r\n6.7 commit 9bcef5973e31 (\u0026quot;mm: memcg: fix split queue list crash when large\nfolio migration\u0026quot;) was right to fix the memcg-dependent locking broken in\n85ce2c517ade (\u0026quot;memcontrol: only transfer the memcg data for migration\u0026quot;),\nbut missed a subtlety of deferred_split_scan(): it moves folios to its own\nlocal list to work on them without split_queue_lock, during which time\nfolio-\u0026gt;_deferred_list is not empty, but even the \u0026quot;right\u0026quot; lock does nothing\nto secure the folio and the list it is on.\r\n\r\nFortunately, deferred_split_scan() is careful to use folio_try_get(): so\nfolio_migrate_mapping() can avoid the race by folio_undo_large_rmappable()\nwhile the old folio\u0026apos;s reference count is temporarily frozen to 0 - adding\nsuch a freeze in the !mapping case too (originally, folio lock and\nunmapping and no swap cache left an anon folio unreachable, so no freezing\nwas needed there: but the deferred split queue offers a way to reach it).(CVE-2024-42234)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\ns390/mm: Add NULL pointer check to crst_table_free() base_crst_free()\r\n\r\ncrst_table_free() used to work with NULL pointers before the conversion\nto ptdescs.  Since crst_table_free() can be called with a NULL pointer\n(error handling in crst_table_upgrade() add an explicit check.\r\n\r\nAlso add the same check to base_crst_free() for consistency reasons.\r\n\r\nIn real life this should not happen, since order two GFP_KERNEL\nallocations will not fail, unless FAIL_PAGE_ALLOC is enabled and used.(CVE-2024-42235)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nfirmware: cs_dsp: Validate payload length before processing block\r\n\r\nMove the payload length check in cs_dsp_load() and cs_dsp_coeff_load()\nto be done before the block is processed.\r\n\r\nThe check that the length of a block payload does not exceed the number\nof remaining bytes in the firwmware file buffer was being done near the\nend of the loop iteration. However, some code before that check used the\nlength field without validating it.(CVE-2024-42237)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nfirmware: cs_dsp: Return error if block header overflows file\r\n\r\nReturn an error from cs_dsp_power_up() if a block header is longer\nthan the amount of data left in the file.\r\n\r\nThe previous code in cs_dsp_load() and cs_dsp_load_coeff() would loop\nwhile there was enough data left in the file for a valid region. This\nprotected against overrunning the end of the file data, but it didn\u0026apos;t\nabort the file processing with an error.(CVE-2024-42238)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nbpf: Fail bpf_timer_cancel when callback is being cancelled\r\n\r\nGiven a schedule:\r\n\r\ntimer1 cb\t\t\ttimer2 cb\r\n\r\nbpf_timer_cancel(timer2);\tbpf_timer_cancel(timer1);\r\n\r\nBoth bpf_timer_cancel calls would wait for the other callback to finish\nexecuting, introducing a lockup.\r\n\r\nAdd an atomic_t count named \u0026apos;cancelling\u0026apos; in bpf_hrtimer. This keeps\ntrack of all in-flight cancellation requests for a given BPF timer.\nWhenever cancelling a BPF timer, we must check if we have outstanding\ncancellation requests, and if so, we must fail the operation with an\nerror (-EDEADLK) since cancellation is synchronous and waits for the\ncallback to finish executing. This implies that we can enter a deadlock\nsituation involving two or more timer callbacks executing in parallel\nand attempting to cancel one another.\r\n\r\nNote that we avoid incrementing the cancelling counter for the target\ntimer (the one being cancelled) if bpf_timer_cancel is not invoked from\na callback, to avoid spurious errors. The whole point of detecting\ncur-\u0026gt;cancelling and returning -EDEADLK is to not enter a busy wait loop\n(which may or may not lead to a lockup). This does not apply in case the\ncaller is in a non-callback context, the other side can continue to\ncancel as it sees fit without running into errors.\r\n\r\nBackground on prior attempts:\r\n\r\nEarlier versions of this patch used a bool \u0026apos;cancelling\u0026apos; bit and used the\nfollowing pattern under timer-\u0026gt;lock to publish cancellation status.\r\n\r\nlock(t-\u0026gt;lock);\nt-\u0026gt;cancelling = true;\nmb();\nif (cur-\u0026gt;cancelling)\n\treturn -EDEADLK;\nunlock(t-\u0026gt;lock);\nhrtimer_cancel(t-\u0026gt;timer);\nt-\u0026gt;cancelling = false;\r\n\r\nThe store outside the critical section could overwrite a parallel\nrequests t-\u0026gt;cancelling assignment to true, to ensure the parallely\nexecuting callback observes its cancellation status.\r\n\r\nIt would be necessary to clear this cancelling bit once hrtimer_cancel\nis done, but lack of serialization introduced races. Another option was\nexplored where bpf_timer_start would clear the bit when (re)starting the\ntimer under timer-\u0026gt;lock. This would ensure serialized access to the\ncancelling bit, but may allow it to be cleared before in-flight\nhrtimer_cancel has finished executing, such that lockups can occur\nagain.\r\n\r\nThus, we choose an atomic counter to keep track of all outstanding\ncancellation requests and use it to prevent lockups in case callbacks\nattempt to cancel each other while executing in parallel.(CVE-2024-42239)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nx86/bhi: Avoid warning in #DB handler due to BHI mitigation\r\n\r\nWhen BHI mitigation is enabled, if SYSENTER is invoked with the TF flag set\nthen entry_SYSENTER_compat() uses CLEAR_BRANCH_HISTORY and calls the\nclear_bhb_loop() before the TF flag is cleared. This causes the #DB handler\n(exc_debug_kernel()) to issue a warning because single-step is used outside the\nentry_SYSENTER_compat() function.\r\n\r\nTo address this issue, entry_SYSENTER_compat() should use CLEAR_BRANCH_HISTORY\nafter making sure the TF flag is cleared.\r\n\r\nThe problem can be reproduced with the following sequence:\r\n\r\n  $ cat sysenter_step.c\n  int main()\n  { asm(\u0026quot;pushf; pop %ax; bts $8,%ax; push %ax; popf; sysenter\u0026quot;); }\r\n\r\n  $ gcc -o sysenter_step sysenter_step.c\r\n\r\n  $ ./sysenter_step\n  Segmentation fault (core dumped)\r\n\r\nThe program is expected to crash, and the #DB handler will issue a warning.\r\n\r\nKernel log:\r\n\r\n  WARNING: CPU: 27 PID: 7000 at arch/x86/kernel/traps.c:1009 exc_debug_kernel+0xd2/0x160\n  ...\n  RIP: 0010:exc_debug_kernel+0xd2/0x160\n  ...\n  Call Trace:\n  \u0026lt;#DB\u0026gt;\n   ? show_regs+0x68/0x80\n   ? __warn+0x8c/0x140\n   ? exc_debug_kernel+0xd2/0x160\n   ? report_bug+0x175/0x1a0\n   ? handle_bug+0x44/0x90\n   ? exc_invalid_op+0x1c/0x70\n   ? asm_exc_invalid_op+0x1f/0x30\n   ? exc_debug_kernel+0xd2/0x160\n   exc_debug+0x43/0x50\n   asm_exc_debug+0x1e/0x40\n  RIP: 0010:clear_bhb_loop+0x0/0xb0\n  ...\n  \u0026lt;/#DB\u0026gt;\n  \u0026lt;TASK\u0026gt;\n   ? entry_SYSENTER_compat_after_hwframe+0x6e/0x8d\n  \u0026lt;/TASK\u0026gt;\r\n\r\n  [ bp: Massage commit message. ](CVE-2024-42240)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nmm/shmem: disable PMD-sized page cache if needed\r\n\r\nFor shmem files, it\u0026apos;s possible that PMD-sized page cache can\u0026apos;t be\nsupported by xarray.  For example, 512MB page cache on ARM64 when the base\npage size is 64KB can\u0026apos;t be supported by xarray.  It leads to errors as the\nfollowing messages indicate when this sort of xarray entry is split.\r\n\r\nWARNING: CPU: 34 PID: 7578 at lib/xarray.c:1025 xas_split_alloc+0xf8/0x128\nModules linked in: binfmt_misc nft_fib_inet nft_fib_ipv4 nft_fib_ipv6   \\\nnft_fib nft_reject_inet nf_reject_ipv4 nf_reject_ipv6 nft_reject        \\\nnft_ct nft_chain_nat nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4  \\\nip_set rfkill nf_tables nfnetlink vfat fat virtio_balloon drm fuse xfs  \\\nlibcrc32c crct10dif_ce ghash_ce sha2_ce sha256_arm64 sha1_ce virtio_net \\\nnet_failover virtio_console virtio_blk failover dimlib virtio_mmio\nCPU: 34 PID: 7578 Comm: test Kdump: loaded Tainted: G W 6.10.0-rc5-gavin+ #9\nHardware name: QEMU KVM Virtual Machine, BIOS edk2-20240524-1.el9 05/24/2024\npstate: 83400005 (Nzcv daif +PAN -UAO +TCO +DIT -SSBS BTYPE=--)\npc : xas_split_alloc+0xf8/0x128\nlr : split_huge_page_to_list_to_order+0x1c4/0x720\nsp : ffff8000882af5f0\nx29: ffff8000882af5f0 x28: ffff8000882af650 x27: ffff8000882af768\nx26: 0000000000000cc0 x25: 000000000000000d x24: ffff00010625b858\nx23: ffff8000882af650 x22: ffffffdfc0900000 x21: 0000000000000000\nx20: 0000000000000000 x19: ffffffdfc0900000 x18: 0000000000000000\nx17: 0000000000000000 x16: 0000018000000000 x15: 52f8004000000000\nx14: 0000e00000000000 x13: 0000000000002000 x12: 0000000000000020\nx11: 52f8000000000000 x10: 52f8e1c0ffff6000 x9 : ffffbeb9619a681c\nx8 : 0000000000000003 x7 : 0000000000000000 x6 : ffff00010b02ddb0\nx5 : ffffbeb96395e378 x4 : 0000000000000000 x3 : 0000000000000cc0\nx2 : 000000000000000d x1 : 000000000000000c x0 : 0000000000000000\nCall trace:\n xas_split_alloc+0xf8/0x128\n split_huge_page_to_list_to_order+0x1c4/0x720\n truncate_inode_partial_folio+0xdc/0x160\n shmem_undo_range+0x2bc/0x6a8\n shmem_fallocate+0x134/0x430\n vfs_fallocate+0x124/0x2e8\n ksys_fallocate+0x4c/0xa0\n __arm64_sys_fallocate+0x24/0x38\n invoke_syscall.constprop.0+0x7c/0xd8\n do_el0_svc+0xb4/0xd0\n el0_svc+0x44/0x1d8\n el0t_64_sync_handler+0x134/0x150\n el0t_64_sync+0x17c/0x180\r\n\r\nFix it by disabling PMD-sized page cache when HPAGE_PMD_ORDER is larger\nthan MAX_PAGECACHE_ORDER.  As Matthew Wilcox pointed, the page cache in a\nshmem file isn\u0026apos;t represented by a multi-index entry and doesn\u0026apos;t have this\nlimitation when the xarry entry is split until commit 6b24ca4a1a8d (\u0026quot;mm:\nUse multi-index entries in the page cache\u0026quot;).(CVE-2024-42241)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nmm/filemap: make MAX_PAGECACHE_ORDER acceptable to xarray\r\n\r\nPatch series \u0026quot;mm/filemap: Limit page cache size to that supported by\nxarray\u0026quot;, v2.\r\n\r\nCurrently, xarray can\u0026apos;t support arbitrary page cache size.  More details\ncan be found from the WARN_ON() statement in xas_split_alloc().  In our\ntest whose code is attached below, we hit the WARN_ON() on ARM64 system\nwhere the base page size is 64KB and huge page size is 512MB.  The issue\nwas reported long time ago and some discussions on it can be found here\n[1].\r\n\r\n[1] https://www.spinics.net/lists/linux-xfs/msg75404.html\r\n\r\nIn order to fix the issue, we need to adjust MAX_PAGECACHE_ORDER to one\nsupported by xarray and avoid PMD-sized page cache if needed.  The code\nchanges are suggested by David Hildenbrand.\r\n\r\nPATCH[1] adjusts MAX_PAGECACHE_ORDER to that supported by xarray\nPATCH[2-3] avoids PMD-sized page cache in the synchronous readahead path\nPATCH[4] avoids PMD-sized page cache for shmem files if needed\r\n\r\nTest program\n============\n# cat test.c\n#define _GNU_SOURCE\n#include \u0026lt;stdio.h\u0026gt;\n#include \u0026lt;stdlib.h\u0026gt;\n#include \u0026lt;unistd.h\u0026gt;\n#include \u0026lt;string.h\u0026gt;\n#include \u0026lt;fcntl.h\u0026gt;\n#include \u0026lt;errno.h\u0026gt;\n#include \u0026lt;sys/syscall.h\u0026gt;\n#include \u0026lt;sys/mman.h\u0026gt;\r\n\r\n#define TEST_XFS_FILENAME\t\u0026quot;/tmp/data\u0026quot;\n#define TEST_SHMEM_FILENAME\t\u0026quot;/dev/shm/data\u0026quot;\n#define TEST_MEM_SIZE\t\t0x20000000\r\n\r\nint main(int argc, char **argv)\n{\n\tconst char *filename;\n\tint fd = 0;\n\tvoid *buf = (void *)-1, *p;\n\tint pgsize = getpagesize();\n\tint ret;\r\n\r\n\tif (pgsize != 0x10000) {\n\t\tfprintf(stderr, \u0026quot;64KB base page size is required\\n\u0026quot;);\n\t\treturn -EPERM;\n\t}\r\n\r\n\tsystem(\u0026quot;echo force \u0026gt; /sys/kernel/mm/transparent_hugepage/shmem_enabled\u0026quot;);\n\tsystem(\u0026quot;rm -fr /tmp/data\u0026quot;);\n\tsystem(\u0026quot;rm -fr /dev/shm/data\u0026quot;);\n\tsystem(\u0026quot;echo 1 \u0026gt; /proc/sys/vm/drop_caches\u0026quot;);\r\n\r\n\t/* Open xfs or shmem file */\n\tfilename = TEST_XFS_FILENAME;\n\tif (argc \u0026gt; 1 \u0026amp;\u0026amp; !strcmp(argv[1], \u0026quot;shmem\u0026quot;))\n\t\tfilename = TEST_SHMEM_FILENAME;\r\n\r\n\tfd = open(filename, O_CREAT | O_RDWR | O_TRUNC);\n\tif (fd \u0026lt; 0) {\n\t\tfprintf(stderr, \u0026quot;Unable to open \u0026lt;%s\u0026gt;\\n\u0026quot;, filename);\n\t\treturn -EIO;\n\t}\r\n\r\n\t/* Extend file size */\n\tret = ftruncate(fd, TEST_MEM_SIZE);\n\tif (ret) {\n\t\tfprintf(stderr, \u0026quot;Error %d to ftruncate()\\n\u0026quot;, ret);\n\t\tgoto cleanup;\n\t}\r\n\r\n\t/* Create VMA */\n\tbuf = mmap(NULL, TEST_MEM_SIZE,\n\t\t   PROT_READ | PROT_WRITE, MAP_SHARED, fd, 0);\n\tif (buf == (void *)-1) {\n\t\tfprintf(stderr, \u0026quot;Unable to mmap \u0026lt;%s\u0026gt;\\n\u0026quot;, filename);\n\t\tgoto cleanup;\n\t}\r\n\r\n\tfprintf(stdout, \u0026quot;mapped buffer at 0x%p\\n\u0026quot;, buf);\n\tret = madvise(buf, TEST_MEM_SIZE, MADV_HUGEPAGE);\n        if (ret) {\n\t\tfprintf(stderr, \u0026quot;Unable to madvise(MADV_HUGEPAGE)\\n\u0026quot;);\n\t\tgoto cleanup;\n\t}\r\n\r\n\t/* Populate VMA */\n\tret = madvise(buf, TEST_MEM_SIZE, MADV_POPULATE_WRITE);\n\tif (ret) {\n\t\tfprintf(stderr, \u0026quot;Error %d to madvise(MADV_POPULATE_WRITE)\\n\u0026quot;, ret);\n\t\tgoto cleanup;\n\t}\r\n\r\n\t/* Punch the file to enforce xarray split */\n\tret = fallocate(fd, FALLOC_FL_KEEP_SIZE | FALLOC_FL_PUNCH_HOLE,\n        \t\tTEST_MEM_SIZE - pgsize, pgsize);\n\tif (ret)\n\t\tfprintf(stderr, \u0026quot;Error %d to fallocate()\\n\u0026quot;, ret);\r\n\r\ncleanup:\n\tif (buf != (void *)-1)\n\t\tmunmap(buf, TEST_MEM_SIZE);\n\tif (fd \u0026gt; 0)\n\t\tclose(fd);\r\n\r\n\treturn 0;\n}\r\n\r\n# gcc test.c -o test\n# cat /proc/1/smaps | grep KernelPageSize | head -n 1\nKernelPageSize:       64 kB\n# ./test shmem\n   :\n------------[ cut here ]------------\nWARNING: CPU: 17 PID: 5253 at lib/xarray.c:1025 xas_split_alloc+0xf8/0x128\nModules linked in: nft_fib_inet nft_fib_ipv4 nft_fib_ipv6 nft_fib  \\\nnft_reject_inet nf_reject_ipv4 nf_reject_ipv6 nft_reject nft_ct    \\\nnft_chain_nat nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4    \\\nip_set nf_tables rfkill nfnetlink vfat fat virtio_balloon          \\\ndrm fuse xfs libcrc32c crct10dif_ce ghash_ce sha2_ce sha256_arm64  \\\nvirtio_net sha1_ce net_failover failover virtio_console virtio_blk \\\ndimlib virtio_mmio\nCPU: 17 PID: 5253 Comm: test Kdump: loaded Tainted: G W 6.10.0-rc5-gavin+ #12\nHardware name: QEMU KVM Virtual Machine, BIOS edk2-20240524-1.el9 05/24/2024\npstate: 83400005 (Nzcv daif +PAN -UAO +TC\n---truncated---(CVE-2024-42243)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\ntty: serial: ma35d1: Add a NULL check for of_node\r\n\r\nThe pdev-\u0026gt;dev.of_node can be NULL if the \u0026quot;serial\u0026quot; node is absent.\nAdd a NULL check to return an error in such cases.(CVE-2024-42248)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\ncachefiles: add missing lock protection when polling\r\n\r\nAdd missing lock protection in poll routine when iterating xarray,\notherwise:\r\n\r\nEven with RCU read lock held, only the slot of the radix tree is\nensured to be pinned there, while the data structure (e.g. struct\ncachefiles_req) stored in the slot has no such guarantee.  The poll\nroutine will iterate the radix tree and dereference cachefiles_req\naccordingly.  Thus RCU read lock is not adequate in this case and\nspinlock is needed here.(CVE-2024-42250)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\ngpio: pca953x: fix pca953x_irq_bus_sync_unlock race\r\n\r\nEnsure that `i2c_lock\u0026apos; is held when setting interrupt latch and mask in\npca953x_irq_bus_sync_unlock() in order to avoid races.\r\n\r\nThe other (non-probe) call site pca953x_gpio_set_multiple() ensures the\nlock is held before calling pca953x_write_regs().\r\n\r\nThe problem occurred when a request raced against irq_bus_sync_unlock()\napproximately once per thousand reboots on an i.MX8MP based system.\r\n\r\n * Normal case\r\n\r\n   0-0022: write register AI|3a {03,02,00,00,01} Input latch P0\n   0-0022: write register AI|49 {fc,fd,ff,ff,fe} Interrupt mask P0\n   0-0022: write register AI|08 {ff,00,00,00,00} Output P3\n   0-0022: write register AI|12 {fc,00,00,00,00} Config P3\r\n\r\n * Race case\r\n\r\n   0-0022: write register AI|08 {ff,00,00,00,00} Output P3\n   0-0022: write register AI|08 {03,02,00,00,01} *** Wrong register ***\n   0-0022: write register AI|12 {fc,00,00,00,00} Config P3\n   0-0022: write register AI|49 {fc,fd,ff,ff,fe} Interrupt mask P0(CVE-2024-42253)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nmm: huge_memory: use !CONFIG_64BIT to relax huge page alignment on 32 bit machines\r\n\r\nYves-Alexis Perez reported commit 4ef9ad19e176 (\u0026quot;mm: huge_memory: don\u0026apos;t\nforce huge page alignment on 32 bit\u0026quot;) didn\u0026apos;t work for x86_32 [1].  It is\nbecause x86_32 uses CONFIG_X86_32 instead of CONFIG_32BIT.\r\n\r\n!CONFIG_64BIT should cover all 32 bit machines.\r\n\r\n[1] https://lore.kernel.org/linux-mm/CAHbLzkr1LwH3pcTgM+aGQ31ip2bKqiqEQ8=FQB+t2c3dhNKNHA@mail.gmail.com/(CVE-2024-42258)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\ndrm/i915/gem: Fix Virtual Memory mapping boundaries calculation\r\n\r\nCalculating the size of the mapped area as the lesser value\nbetween the requested size and the actual size does not consider\nthe partial mapping offset. This can cause page fault access.\r\n\r\nFix the calculation of the starting and ending addresses, the\ntotal size is now deduced from the difference between the end and\nstart addresses.\r\n\r\nAdditionally, the calculations have been rewritten in a clearer\nand more understandable form.\r\n\r\n[Joonas: Add Requires: tag]\nRequires: 60a2066c5005 (\u0026quot;drm/i915/gem: Adjust vma offset for framebuffer mmap offset\u0026quot;)\n(cherry picked from commit 97b6784753da06d9d40232328efc5c5367e53417)(CVE-2024-42259)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nnet/iucv: fix use after free in iucv_sock_close()\r\n\r\niucv_sever_path() is called from process context and from bh context.\niucv-\u0026gt;path is used as indicator whether somebody else is taking care of\nsevering the path (or it is already removed / never existed).\nThis needs to be done with atomic compare and swap, otherwise there is a\nsmall window where iucv_sock_close() will try to work with a path that has\nalready been severed and freed by iucv_callback_connrej() called by\niucv_tasklet_fn().\r\n\r\nExample:\n[452744.123844] Call Trace:\n[452744.123845] ([\u0026lt;0000001e87f03880\u0026gt;] 0x1e87f03880)\n[452744.123966]  [\u0026lt;00000000d593001e\u0026gt;] iucv_path_sever+0x96/0x138\n[452744.124330]  [\u0026lt;000003ff801ddbca\u0026gt;] iucv_sever_path+0xc2/0xd0 [af_iucv]\n[452744.124336]  [\u0026lt;000003ff801e01b6\u0026gt;] iucv_sock_close+0xa6/0x310 [af_iucv]\n[452744.124341]  [\u0026lt;000003ff801e08cc\u0026gt;] iucv_sock_release+0x3c/0xd0 [af_iucv]\n[452744.124345]  [\u0026lt;00000000d574794e\u0026gt;] __sock_release+0x5e/0xe8\n[452744.124815]  [\u0026lt;00000000d5747a0c\u0026gt;] sock_close+0x34/0x48\n[452744.124820]  [\u0026lt;00000000d5421642\u0026gt;] __fput+0xba/0x268\n[452744.124826]  [\u0026lt;00000000d51b382c\u0026gt;] task_work_run+0xbc/0xf0\n[452744.124832]  [\u0026lt;00000000d5145710\u0026gt;] do_notify_resume+0x88/0x90\n[452744.124841]  [\u0026lt;00000000d5978096\u0026gt;] system_call+0xe2/0x2c8\n[452744.125319] Last Breaking-Event-Address:\n[452744.125321]  [\u0026lt;00000000d5930018\u0026gt;] iucv_path_sever+0x90/0x138\n[452744.125324]\n[452744.125325] Kernel panic - not syncing: Fatal exception in interrupt\r\n\r\nNote that bh_lock_sock() is not serializing the tasklet context against\nprocess context, because the check for sock_owned_by_user() and\ncorresponding handling is missing.\r\n\r\nIdeas for a future clean-up patch:\nA) Correct usage of bh_lock_sock() in tasklet context, as described in\nRe-enqueue, if needed. This may require adding return values to the\ntasklet functions and thus changes to all users of iucv.\r\n\r\nB) Change iucv tasklet into worker and use only lock_sock() in af_iucv.(CVE-2024-42271)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nsched: act_ct: take care of padding in struct zones_ht_key\r\n\r\nBlamed commit increased lookup key size from 2 bytes to 16 bytes,\nbecause zones_ht_key got a struct net pointer.\r\n\r\nMake sure rhashtable_lookup() is not using the padding bytes\nwhich are not initialized.\r\n\r\n BUG: KMSAN: uninit-value in rht_ptr_rcu include/linux/rhashtable.h:376 [inline]\n BUG: KMSAN: uninit-value in __rhashtable_lookup include/linux/rhashtable.h:607 [inline]\n BUG: KMSAN: uninit-value in rhashtable_lookup include/linux/rhashtable.h:646 [inline]\n BUG: KMSAN: uninit-value in rhashtable_lookup_fast include/linux/rhashtable.h:672 [inline]\n BUG: KMSAN: uninit-value in tcf_ct_flow_table_get+0x611/0x2260 net/sched/act_ct.c:329\n  rht_ptr_rcu include/linux/rhashtable.h:376 [inline]\n  __rhashtable_lookup include/linux/rhashtable.h:607 [inline]\n  rhashtable_lookup include/linux/rhashtable.h:646 [inline]\n  rhashtable_lookup_fast include/linux/rhashtable.h:672 [inline]\n  tcf_ct_flow_table_get+0x611/0x2260 net/sched/act_ct.c:329\n  tcf_ct_init+0xa67/0x2890 net/sched/act_ct.c:1408\n  tcf_action_init_1+0x6cc/0xb30 net/sched/act_api.c:1425\n  tcf_action_init+0x458/0xf00 net/sched/act_api.c:1488\n  tcf_action_add net/sched/act_api.c:2061 [inline]\n  tc_ctl_action+0x4be/0x19d0 net/sched/act_api.c:2118\n  rtnetlink_rcv_msg+0x12fc/0x1410 net/core/rtnetlink.c:6647\n  netlink_rcv_skb+0x375/0x650 net/netlink/af_netlink.c:2550\n  rtnetlink_rcv+0x34/0x40 net/core/rtnetlink.c:6665\n  netlink_unicast_kernel net/netlink/af_netlink.c:1331 [inline]\n  netlink_unicast+0xf52/0x1260 net/netlink/af_netlink.c:1357\n  netlink_sendmsg+0x10da/0x11e0 net/netlink/af_netlink.c:1901\n  sock_sendmsg_nosec net/socket.c:730 [inline]\n  __sock_sendmsg+0x30f/0x380 net/socket.c:745\n  ____sys_sendmsg+0x877/0xb60 net/socket.c:2597\n  ___sys_sendmsg+0x28d/0x3c0 net/socket.c:2651\n  __sys_sendmsg net/socket.c:2680 [inline]\n  __do_sys_sendmsg net/socket.c:2689 [inline]\n  __se_sys_sendmsg net/socket.c:2687 [inline]\n  __x64_sys_sendmsg+0x307/0x4a0 net/socket.c:2687\n  x64_sys_call+0x2dd6/0x3c10 arch/x86/include/generated/asm/syscalls_64.h:47\n  do_syscall_x64 arch/x86/entry/common.c:52 [inline]\n  do_syscall_64+0xcd/0x1e0 arch/x86/entry/common.c:83\n entry_SYSCALL_64_after_hwframe+0x77/0x7f\r\n\r\nLocal variable key created at:\n  tcf_ct_flow_table_get+0x4a/0x2260 net/sched/act_ct.c:324\n  tcf_ct_init+0xa67/0x2890 net/sched/act_ct.c:1408(CVE-2024-42272)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nnvme-pci: add missing condition check for existence of mapped data\r\n\r\nnvme_map_data() is called when request has physical segments, hence\nthe nvme_unmap_data() should have same condition to avoid dereference.(CVE-2024-42276)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\niommu: sprd: Avoid NULL deref in sprd_iommu_hw_en\r\n\r\nIn sprd_iommu_cleanup() before calling function sprd_iommu_hw_en()\ndom-\u0026gt;sdev is equal to NULL, which leads to null dereference.\r\n\r\nFound by Linux Verification Center (linuxtesting.org) with SVACE.(CVE-2024-42277)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nspi: microchip-core: ensure TX and RX FIFOs are empty at start of a transfer\r\n\r\nWhile transmitting with rx_len == 0, the RX FIFO is not going to be\nemptied in the interrupt handler. A subsequent transfer could then\nread crap from the previous transfer out of the RX FIFO into the\nstart RX buffer. The core provides a register that will empty the RX and\nTX FIFOs, so do that before each transfer.(CVE-2024-42279)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nice: Add a per-VF limit on number of FDIR filters\r\n\r\nWhile the iavf driver adds a s/w limit (128) on the number of FDIR\nfilters that the VF can request, a malicious VF driver can request more\nthan that and exhaust the resources for other VFs.\r\n\r\nAdd a similar limit in ice.(CVE-2024-42291)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nblock: fix deadlock between sd_remove \u0026amp; sd_release\r\n\r\nOur test report the following hung task:\r\n\r\n[ 2538.459400] INFO: task \u0026quot;kworker/0:0\u0026quot;:7 blocked for more than 188 seconds.\n[ 2538.459427] Call trace:\n[ 2538.459430]  __switch_to+0x174/0x338\n[ 2538.459436]  __schedule+0x628/0x9c4\n[ 2538.459442]  schedule+0x7c/0xe8\n[ 2538.459447]  schedule_preempt_disabled+0x24/0x40\n[ 2538.459453]  __mutex_lock+0x3ec/0xf04\n[ 2538.459456]  __mutex_lock_slowpath+0x14/0x24\n[ 2538.459459]  mutex_lock+0x30/0xd8\n[ 2538.459462]  del_gendisk+0xdc/0x350\n[ 2538.459466]  sd_remove+0x30/0x60\n[ 2538.459470]  device_release_driver_internal+0x1c4/0x2c4\n[ 2538.459474]  device_release_driver+0x18/0x28\n[ 2538.459478]  bus_remove_device+0x15c/0x174\n[ 2538.459483]  device_del+0x1d0/0x358\n[ 2538.459488]  __scsi_remove_device+0xa8/0x198\n[ 2538.459493]  scsi_forget_host+0x50/0x70\n[ 2538.459497]  scsi_remove_host+0x80/0x180\n[ 2538.459502]  usb_stor_disconnect+0x68/0xf4\n[ 2538.459506]  usb_unbind_interface+0xd4/0x280\n[ 2538.459510]  device_release_driver_internal+0x1c4/0x2c4\n[ 2538.459514]  device_release_driver+0x18/0x28\n[ 2538.459518]  bus_remove_device+0x15c/0x174\n[ 2538.459523]  device_del+0x1d0/0x358\n[ 2538.459528]  usb_disable_device+0x84/0x194\n[ 2538.459532]  usb_disconnect+0xec/0x300\n[ 2538.459537]  hub_event+0xb80/0x1870\n[ 2538.459541]  process_scheduled_works+0x248/0x4dc\n[ 2538.459545]  worker_thread+0x244/0x334\n[ 2538.459549]  kthread+0x114/0x1bc\r\n\r\n[ 2538.461001] INFO: task \u0026quot;fsck.\u0026quot;:15415 blocked for more than 188 seconds.\n[ 2538.461014] Call trace:\n[ 2538.461016]  __switch_to+0x174/0x338\n[ 2538.461021]  __schedule+0x628/0x9c4\n[ 2538.461025]  schedule+0x7c/0xe8\n[ 2538.461030]  blk_queue_enter+0xc4/0x160\n[ 2538.461034]  blk_mq_alloc_request+0x120/0x1d4\n[ 2538.461037]  scsi_execute_cmd+0x7c/0x23c\n[ 2538.461040]  ioctl_internal_command+0x5c/0x164\n[ 2538.461046]  scsi_set_medium_removal+0x5c/0xb0\n[ 2538.461051]  sd_release+0x50/0x94\n[ 2538.461054]  blkdev_put+0x190/0x28c\n[ 2538.461058]  blkdev_release+0x28/0x40\n[ 2538.461063]  __fput+0xf8/0x2a8\n[ 2538.461066]  __fput_sync+0x28/0x5c\n[ 2538.461070]  __arm64_sys_close+0x84/0xe8\n[ 2538.461073]  invoke_syscall+0x58/0x114\n[ 2538.461078]  el0_svc_common+0xac/0xe0\n[ 2538.461082]  do_el0_svc+0x1c/0x28\n[ 2538.461087]  el0_svc+0x38/0x68\n[ 2538.461090]  el0t_64_sync_handler+0x68/0xbc\n[ 2538.461093]  el0t_64_sync+0x1a8/0x1ac\r\n\r\n  T1:\t\t\t\tT2:\n  sd_remove\n  del_gendisk\n  __blk_mark_disk_dead\n  blk_freeze_queue_start\n  ++q-\u0026gt;mq_freeze_depth\n  \t\t\t\tbdev_release\n \t\t\t\tmutex_lock(\u0026amp;disk-\u0026gt;open_mutex)\n  \t\t\t\tsd_release\n \t\t\t\tscsi_execute_cmd\n \t\t\t\tblk_queue_enter\n \t\t\t\twait_event(!q-\u0026gt;mq_freeze_depth)\n  mutex_lock(\u0026amp;disk-\u0026gt;open_mutex)\r\n\r\nSCSI does not set GD_OWNS_QUEUE, so QUEUE_FLAG_DYING is not set in\nthis scenario. This is a classic ABBA deadlock. To fix the deadlock,\nmake sure we don\u0026apos;t try to acquire disk-\u0026gt;open_mutex after freezing\nthe queue.(CVE-2024-42294)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nf2fs: fix return value of f2fs_convert_inline_inode()\r\n\r\nIf device is readonly, make f2fs_convert_inline_inode()\nreturn EROFS instead of zero, otherwise it may trigger\npanic during writeback of inline inode\u0026apos;s dirty page as\nbelow:\r\n\r\n f2fs_write_single_data_page+0xbb6/0x1e90 fs/f2fs/data.c:2888\n f2fs_write_cache_pages fs/f2fs/data.c:3187 [inline]\n __f2fs_write_data_pages fs/f2fs/data.c:3342 [inline]\n f2fs_write_data_pages+0x1efe/0x3a90 fs/f2fs/data.c:3369\n do_writepages+0x359/0x870 mm/page-writeback.c:2634\n filemap_fdatawrite_wbc+0x125/0x180 mm/filemap.c:397\n __filemap_fdatawrite_range mm/filemap.c:430 [inline]\n file_write_and_wait_range+0x1aa/0x290 mm/filemap.c:788\n f2fs_do_sync_file+0x68a/0x1ae0 fs/f2fs/file.c:276\n generic_write_sync include/linux/fs.h:2806 [inline]\n f2fs_file_write_iter+0x7bd/0x24e0 fs/f2fs/file.c:4977\n call_write_iter include/linux/fs.h:2114 [inline]\n new_sync_write fs/read_write.c:497 [inline]\n vfs_write+0xa72/0xc90 fs/read_write.c:590\n ksys_write+0x1a0/0x2c0 fs/read_write.c:643\n do_syscall_x64 arch/x86/entry/common.c:52 [inline]\n do_syscall_64+0xf5/0x240 arch/x86/entry/common.c:83\n entry_SYSCALL_64_after_hwframe+0x77/0x7f(CVE-2024-42296)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nASoC: fsl: fsl_qmc_audio: Check devm_kasprintf() returned value\r\n\r\ndevm_kasprintf() can return a NULL pointer on failure but this returned\nvalue is not checked.\r\n\r\nFix this lack and check the returned value.(CVE-2024-42298)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nmedia: imx-pxp: Fix ERR_PTR dereference in pxp_probe()\r\n\r\ndevm_regmap_init_mmio() can fail, add a check and bail out in case of\nerror.(CVE-2024-42303)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\ncifs: fix potential null pointer use in destroy_workqueue in init_cifs error path\r\n\r\nDan Carpenter reported a Smack static checker warning:\n   fs/smb/client/cifsfs.c:1981 init_cifs()\n   error: we previously assumed \u0026apos;serverclose_wq\u0026apos; could be null (see line 1895)\r\n\r\nThe patch which introduced the serverclose workqueue used the wrong\noredering in error paths in init_cifs() for freeing it on errors.(CVE-2024-42307)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nbtrfs: fix extent map use-after-free when adding pages to compressed bio\r\n\r\nAt add_ra_bio_pages() we are accessing the extent map to calculate\n\u0026apos;add_size\u0026apos; after we dropped our reference on the extent map, resulting\nin a use-after-free. Fix this by computing \u0026apos;add_size\u0026apos; before dropping our\nextent map reference.(CVE-2024-42314)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nexfat: fix potential deadlock on __exfat_get_dentry_set\r\n\r\nWhen accessing a file with more entries than ES_MAX_ENTRY_NUM, the bh-array\nis allocated in __exfat_get_entry_set. The problem is that the bh-array is\nallocated with GFP_KERNEL. It does not make sense. In the following cases,\na deadlock for sbi-\u0026gt;s_lock between the two processes may occur.\r\n\r\n       CPU0                CPU1\n       ----                ----\n  kswapd\n   balance_pgdat\n    lock(fs_reclaim)\n                      exfat_iterate\n                       lock(\u0026amp;sbi-\u0026gt;s_lock)\n                       exfat_readdir\n                        exfat_get_uniname_from_ext_entry\n                         exfat_get_dentry_set\n                          __exfat_get_dentry_set\n                           kmalloc_array\n                            ...\n                            lock(fs_reclaim)\n    ...\n    evict\n     exfat_evict_inode\n      lock(\u0026amp;sbi-\u0026gt;s_lock)\r\n\r\nTo fix this, let\u0026apos;s allocate bh-array with GFP_NOFS.(CVE-2024-42315)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nmm/mglru: fix div-by-zero in vmpressure_calc_level()\r\n\r\nevict_folios() uses a second pass to reclaim folios that have gone through\npage writeback and become clean before it finishes the first pass, since\nfolio_rotate_reclaimable() cannot handle those folios due to the\nisolation.\r\n\r\nThe second pass tries to avoid potential double counting by deducting\nscan_control-\u0026gt;nr_scanned.  However, this can result in underflow of\nnr_scanned, under a condition where shrink_folio_list() does not increment\nnr_scanned, i.e., when folio_trylock() fails.\r\n\r\nThe underflow can cause the divisor, i.e., scale=scanned+reclaimed in\nvmpressure_calc_level(), to become zero, resulting in the following crash:\r\n\r\n  [exception RIP: vmpressure_work_fn+101]\n  process_one_work at ffffffffa3313f2b\r\n\r\nSince scan_control-\u0026gt;nr_scanned has no established semantics, the potential\ndouble counting has minimal risks.  Therefore, fix the problem by not\ndeducting scan_control-\u0026gt;nr_scanned in evict_folios().(CVE-2024-42316)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nmm/huge_memory: avoid PMD-size page cache if needed\r\n\r\nxarray can\u0026apos;t support arbitrary page cache size.  the largest and supported\npage cache size is defined as MAX_PAGECACHE_ORDER by commit 099d90642a71\n(\u0026quot;mm/filemap: make MAX_PAGECACHE_ORDER acceptable to xarray\u0026quot;).  However,\nit\u0026apos;s possible to have 512MB page cache in the huge memory\u0026apos;s collapsing\npath on ARM64 system whose base page size is 64KB.  512MB page cache is\nbreaking the limitation and a warning is raised when the xarray entry is\nsplit as shown in the following example.\r\n\r\n[root@dhcp-10-26-1-207 ~]# cat /proc/1/smaps | grep KernelPageSize\nKernelPageSize:       64 kB\n[root@dhcp-10-26-1-207 ~]# cat /tmp/test.c\n   :\nint main(int argc, char **argv)\n{\n\tconst char *filename = TEST_XFS_FILENAME;\n\tint fd = 0;\n\tvoid *buf = (void *)-1, *p;\n\tint pgsize = getpagesize();\n\tint ret = 0;\r\n\r\n\tif (pgsize != 0x10000) {\n\t\tfprintf(stdout, \u0026quot;System with 64KB base page size is required!\\n\u0026quot;);\n\t\treturn -EPERM;\n\t}\r\n\r\n\tsystem(\u0026quot;echo 0 \u0026gt; /sys/devices/virtual/bdi/253:0/read_ahead_kb\u0026quot;);\n\tsystem(\u0026quot;echo 1 \u0026gt; /proc/sys/vm/drop_caches\u0026quot;);\r\n\r\n\t/* Open the xfs file */\n\tfd = open(filename, O_RDONLY);\n\tassert(fd \u0026gt; 0);\r\n\r\n\t/* Create VMA */\n\tbuf = mmap(NULL, TEST_MEM_SIZE, PROT_READ, MAP_SHARED, fd, 0);\n\tassert(buf != (void *)-1);\n\tfprintf(stdout, \u0026quot;mapped buffer at 0x%p\\n\u0026quot;, buf);\r\n\r\n\t/* Populate VMA */\n\tret = madvise(buf, TEST_MEM_SIZE, MADV_NOHUGEPAGE);\n\tassert(ret == 0);\n\tret = madvise(buf, TEST_MEM_SIZE, MADV_POPULATE_READ);\n\tassert(ret == 0);\r\n\r\n\t/* Collapse VMA */\n\tret = madvise(buf, TEST_MEM_SIZE, MADV_HUGEPAGE);\n\tassert(ret == 0);\n\tret = madvise(buf, TEST_MEM_SIZE, MADV_COLLAPSE);\n\tif (ret) {\n\t\tfprintf(stdout, \u0026quot;Error %d to madvise(MADV_COLLAPSE)\\n\u0026quot;, errno);\n\t\tgoto out;\n\t}\r\n\r\n\t/* Split xarray entry. Write permission is needed */\n\tmunmap(buf, TEST_MEM_SIZE);\n\tbuf = (void *)-1;\n\tclose(fd);\n\tfd = open(filename, O_RDWR);\n\tassert(fd \u0026gt; 0);\n\tfallocate(fd, FALLOC_FL_KEEP_SIZE | FALLOC_FL_PUNCH_HOLE,\n \t\t  TEST_MEM_SIZE - pgsize, pgsize);\nout:\n\tif (buf != (void *)-1)\n\t\tmunmap(buf, TEST_MEM_SIZE);\n\tif (fd \u0026gt; 0)\n\t\tclose(fd);\r\n\r\n\treturn ret;\n}\r\n\r\n[root@dhcp-10-26-1-207 ~]# gcc /tmp/test.c -o /tmp/test\n[root@dhcp-10-26-1-207 ~]# /tmp/test\n ------------[ cut here ]------------\n WARNING: CPU: 25 PID: 7560 at lib/xarray.c:1025 xas_split_alloc+0xf8/0x128\n Modules linked in: nft_fib_inet nft_fib_ipv4 nft_fib_ipv6 nft_fib    \\\n nft_reject_inet nf_reject_ipv4 nf_reject_ipv6 nft_reject nft_ct      \\\n nft_chain_nat nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4      \\\n ip_set rfkill nf_tables nfnetlink vfat fat virtio_balloon drm fuse   \\\n xfs libcrc32c crct10dif_ce ghash_ce sha2_ce sha256_arm64 virtio_net  \\\n sha1_ce net_failover virtio_blk virtio_console failover dimlib virtio_mmio\n CPU: 25 PID: 7560 Comm: test Kdump: loaded Not tainted 6.10.0-rc7-gavin+ #9\n Hardware name: QEMU KVM Virtual Machine, BIOS edk2-20240524-1.el9 05/24/2024\n pstate: 83400005 (Nzcv daif +PAN -UAO +TCO +DIT -SSBS BTYPE=--)\n pc : xas_split_alloc+0xf8/0x128\n lr : split_huge_page_to_list_to_order+0x1c4/0x780\n sp : ffff8000ac32f660\n x29: ffff8000ac32f660 x28: ffff0000e0969eb0 x27: ffff8000ac32f6c0\n x26: 0000000000000c40 x25: ffff0000e0969eb0 x24: 000000000000000d\n x23: ffff8000ac32f6c0 x22: ffffffdfc0700000 x21: 0000000000000000\n x20: 0000000000000000 x19: ffffffdfc0700000 x18: 0000000000000000\n x17: 0000000000000000 x16: ffffd5f3708ffc70 x15: 0000000000000000\n x14: 0000000000000000 x13: 0000000000000000 x12: 0000000000000000\n x11: ffffffffffffffc0 x10: 0000000000000040 x9 : ffffd5f3708e692c\n x8 : 0000000000000003 x7 : 0000000000000000 x6 : ffff0000e0969eb8\n x5 : ffffd5f37289e378 x4 : 0000000000000000 x3 : 0000000000000c40\n x2 : 000000000000000d x1 : 000000000000000c x0 : 0000000000000000\n Call trace:\n  xas_split_alloc+0xf8/0x128\n  split_huge_page_to_list_to_order+0x1c4/0x780\n  truncate_inode_partial_folio+0xdc/0x160\n  truncate_inode_pages_range+0x1b4/0x4a8\n  truncate_pagecache_range+0x84/0xa\n---truncated---(CVE-2024-42317)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\ns390/dasd: fix error checks in dasd_copy_pair_store()\r\n\r\ndasd_add_busid() can return an error via ERR_PTR() if an allocation\nfails. However, two callsites in dasd_copy_pair_store() do not check\nthe result, potentially resulting in a NULL pointer dereference. Fix\nthis by checking the result with IS_ERR() and returning the error up\nthe stack.(CVE-2024-42320)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nnet: flow_dissector: use DEBUG_NET_WARN_ON_ONCE\r\n\r\nThe following splat is easy to reproduce upstream as well as in -stable\nkernels. Florian Westphal provided the following commit:\r\n\r\n  d1dab4f71d37 (\u0026quot;net: add and use __skb_get_hash_symmetric_net\u0026quot;)\r\n\r\nbut this complementary fix has been also suggested by Willem de Bruijn\nand it can be easily backported to -stable kernel which consists in\nusing DEBUG_NET_WARN_ON_ONCE instead to silence the following splat\ngiven __skb_get_hash() is used by the nftables tracing infrastructure to\nto identify packets in traces.\r\n\r\n[69133.561393] ------------[ cut here ]------------\n[69133.561404] WARNING: CPU: 0 PID: 43576 at net/core/flow_dissector.c:1104 __skb_flow_dissect+0x134f/\n[...]\n[69133.561944] CPU: 0 PID: 43576 Comm: socat Not tainted 6.10.0-rc7+ #379\n[69133.561959] RIP: 0010:__skb_flow_dissect+0x134f/0x2ad0\n[69133.561970] Code: 83 f9 04 0f 84 b3 00 00 00 45 85 c9 0f 84 aa 00 00 00 41 83 f9 02 0f 84 81 fc ff\nff 44 0f b7 b4 24 80 00 00 00 e9 8b f9 ff ff \u0026lt;0f\u0026gt; 0b e9 20 f3 ff ff 41 f6 c6 20 0f 84 e4 ef ff ff 48 8d 7b 12 e8\n[69133.561979] RSP: 0018:ffffc90000006fc0 EFLAGS: 00010246\n[69133.561988] RAX: 0000000000000000 RBX: ffffffff82f33e20 RCX: ffffffff81ab7e19\n[69133.561994] RDX: dffffc0000000000 RSI: ffffc90000007388 RDI: ffff888103a1b418\n[69133.562001] RBP: ffffc90000007310 R08: 0000000000000000 R09: 0000000000000000\n[69133.562007] R10: ffffc90000007388 R11: ffffffff810cface R12: ffff888103a1b400\n[69133.562013] R13: 0000000000000000 R14: ffffffff82f33e2a R15: ffffffff82f33e28\n[69133.562020] FS:  00007f40f7131740(0000) GS:ffff888390800000(0000) knlGS:0000000000000000\n[69133.562027] CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033\n[69133.562033] CR2: 00007f40f7346ee0 CR3: 000000015d200001 CR4: 00000000001706f0\n[69133.562040] Call Trace:\n[69133.562044]  \u0026lt;IRQ\u0026gt;\n[69133.562049]  ? __warn+0x9f/0x1a0\n[ 1211.841384]  ? __skb_flow_dissect+0x107e/0x2860\n[...]\n[ 1211.841496]  ? bpf_flow_dissect+0x160/0x160\n[ 1211.841753]  __skb_get_hash+0x97/0x280\n[ 1211.841765]  ? __skb_get_hash_symmetric+0x230/0x230\n[ 1211.841776]  ? mod_find+0xbf/0xe0\n[ 1211.841786]  ? get_stack_info_noinstr+0x12/0xe0\n[ 1211.841798]  ? bpf_ksym_find+0x56/0xe0\n[ 1211.841807]  ? __rcu_read_unlock+0x2a/0x70\n[ 1211.841819]  nft_trace_init+0x1b9/0x1c0 [nf_tables]\n[ 1211.841895]  ? nft_trace_notify+0x830/0x830 [nf_tables]\n[ 1211.841964]  ? get_stack_info+0x2b/0x80\n[ 1211.841975]  ? nft_do_chain_arp+0x80/0x80 [nf_tables]\n[ 1211.842044]  nft_do_chain+0x79c/0x850 [nf_tables](CVE-2024-42321)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nnet: missing check virtio\r\n\r\nTwo missing check in virtio_net_hdr_to_skb() allowed syzbot\nto crash kernels again\r\n\r\n1. After the skb_segment function the buffer may become non-linear\n(nr_frags != 0), but since the SKBTX_SHARED_FRAG flag is not set anywhere\nthe __skb_linearize function will not be executed, then the buffer will\nremain non-linear. Then the condition (offset \u0026gt;= skb_headlen(skb))\nbecomes true, which causes WARN_ON_ONCE in skb_checksum_help.\r\n\r\n2. The struct sk_buff and struct virtio_net_hdr members must be\nmathematically related.\n(gso_size) must be greater than (needed) otherwise WARN_ON_ONCE.\n(remainder) must be greater than (needed) otherwise WARN_ON_ONCE.\n(remainder) may be 0 if division is without remainder.\r\n\r\noffset+2 (4191) \u0026gt; skb_headlen() (1116)\nWARNING: CPU: 1 PID: 5084 at net/core/dev.c:3303 skb_checksum_help+0x5e2/0x740 net/core/dev.c:3303\nModules linked in:\nCPU: 1 PID: 5084 Comm: syz-executor336 Not tainted 6.7.0-rc3-syzkaller-00014-gdf60cee26a2e #0\nHardware name: Google Compute Engine/Google Compute Engine, BIOS Google 11/10/2023\nRIP: 0010:skb_checksum_help+0x5e2/0x740 net/core/dev.c:3303\nCode: 89 e8 83 e0 07 83 c0 03 38 d0 7c 08 84 d2 0f 85 52 01 00 00 44 89 e2 2b 53 74 4c 89 ee 48 c7 c7 40 57 e9 8b e8 af 8f dd f8 90 \u0026lt;0f\u0026gt; 0b 90 90 e9 87 fe ff ff e8 40 0f 6e f9 e9 4b fa ff ff 48 89 ef\nRSP: 0018:ffffc90003a9f338 EFLAGS: 00010286\nRAX: 0000000000000000 RBX: ffff888025125780 RCX: ffffffff814db209\nRDX: ffff888015393b80 RSI: ffffffff814db216 RDI: 0000000000000001\nRBP: ffff8880251257f4 R08: 0000000000000001 R09: 0000000000000000\nR10: 0000000000000000 R11: 0000000000000001 R12: 000000000000045c\nR13: 000000000000105f R14: ffff8880251257f0 R15: 000000000000105d\nFS:  0000555555c24380(0000) GS:ffff8880b9900000(0000) knlGS:0000000000000000\nCS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033\nCR2: 000000002000f000 CR3: 0000000023151000 CR4: 00000000003506f0\nDR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000\nDR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400\nCall Trace:\n \u0026lt;TASK\u0026gt;\n ip_do_fragment+0xa1b/0x18b0 net/ipv4/ip_output.c:777\n ip_fragment.constprop.0+0x161/0x230 net/ipv4/ip_output.c:584\n ip_finish_output_gso net/ipv4/ip_output.c:286 [inline]\n __ip_finish_output net/ipv4/ip_output.c:308 [inline]\n __ip_finish_output+0x49c/0x650 net/ipv4/ip_output.c:295\n ip_finish_output+0x31/0x310 net/ipv4/ip_output.c:323\n NF_HOOK_COND include/linux/netfilter.h:303 [inline]\n ip_output+0x13b/0x2a0 net/ipv4/ip_output.c:433\n dst_output include/net/dst.h:451 [inline]\n ip_local_out+0xaf/0x1a0 net/ipv4/ip_output.c:129\n iptunnel_xmit+0x5b4/0x9b0 net/ipv4/ip_tunnel_core.c:82\n ipip6_tunnel_xmit net/ipv6/sit.c:1034 [inline]\n sit_tunnel_xmit+0xed2/0x28f0 net/ipv6/sit.c:1076\n __netdev_start_xmit include/linux/netdevice.h:4940 [inline]\n netdev_start_xmit include/linux/netdevice.h:4954 [inline]\n xmit_one net/core/dev.c:3545 [inline]\n dev_hard_start_xmit+0x13d/0x6d0 net/core/dev.c:3561\n __dev_queue_xmit+0x7c1/0x3d60 net/core/dev.c:4346\n dev_queue_xmit include/linux/netdevice.h:3134 [inline]\n packet_xmit+0x257/0x380 net/packet/af_packet.c:276\n packet_snd net/packet/af_packet.c:3087 [inline]\n packet_sendmsg+0x24ca/0x5240 net/packet/af_packet.c:3119\n sock_sendmsg_nosec net/socket.c:730 [inline]\n __sock_sendmsg+0xd5/0x180 net/socket.c:745\n __sys_sendto+0x255/0x340 net/socket.c:2190\n __do_sys_sendto net/socket.c:2202 [inline]\n __se_sys_sendto net/socket.c:2198 [inline]\n __x64_sys_sendto+0xe0/0x1b0 net/socket.c:2198\n do_syscall_x64 arch/x86/entry/common.c:51 [inline]\n do_syscall_64+0x40/0x110 arch/x86/entry/common.c:82\n entry_SYSCALL_64_after_hwframe+0x63/0x6b\r\n\r\nFound by Linux Verification Center (linuxtesting.org) with Syzkaller(CVE-2024-43817)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nASoC: amd: Adjust error handling in case of absent codec device\r\n\r\nacpi_get_first_physical_node() can return NULL in several cases (no such\ndevice, ACPI table error, reference count drop to 0, etc).\nExisting check just emit error message, but doesn\u0026apos;t perform return.\nThen this NULL pointer is passed to devm_acpi_dev_add_driver_gpios()\nwhere it is dereferenced.\r\n\r\nAdjust this error handling by adding error code return.\r\n\r\nFound by Linux Verification Center (linuxtesting.org) with SVACE.(CVE-2024-43818)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nscsi: lpfc: Fix a possible null pointer dereference\r\n\r\nIn function lpfc_xcvr_data_show, the memory allocation with kmalloc might\nfail, thereby making rdp_context a null pointer. In the following context\nand functions that use this pointer, there are dereferencing operations,\nleading to null pointer dereference.\r\n\r\nTo fix this issue, a null pointer check should be added. If it is null,\nuse scnprintf to notify the user and return len.(CVE-2024-43821)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\niio: Fix the sorting functionality in iio_gts_build_avail_time_table\r\n\r\nThe sorting in iio_gts_build_avail_time_table is not working as intended.\nIt could result in an out-of-bounds access when the time is zero.\r\n\r\nHere are more details:\r\n\r\n1. When the gts-\u0026gt;itime_table[i].time_us is zero, e.g., the time\nsequence is `3, 0, 1`, the inner for-loop will not terminate and do\nout-of-bound writes. This is because once `times[j] \u0026gt; new`, the value\n`new` will be added in the current position and the `times[j]` will be\nmoved to `j+1` position, which makes the if-condition always hold.\nMeanwhile, idx will be added one, making the loop keep running without\ntermination and out-of-bound write.\n2. If none of the gts-\u0026gt;itime_table[i].time_us is zero, the elements\nwill just be copied without being sorted as described in the comment\n\u0026quot;Sort times from all tables to one and remove duplicates\u0026quot;.\r\n\r\nFor more details, please refer to\nhttps://lore.kernel.org/all/6dd0d822-046c-4dd2-9532-79d7ab96ec05@gmail.com.(CVE-2024-43825)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nnfs: pass explicit offset/count to trace events\r\n\r\nnfs_folio_length is unsafe to use without having the folio locked and a\ncheck for a NULL -\u0026gt;f_mapping that protects against truncations and can\nlead to kernel crashes.  E.g. when running xfstests generic/065 with\nall nfs trace points enabled.\r\n\r\nFollow the model of the XFS trace points and pass in an explіcit offset\nand length.  This has the additional benefit that these values can\nbe more accurate as some of the users touch partial folio ranges.(CVE-2024-43826)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\ndrm/qxl: Add check for drm_cvt_mode\r\n\r\nAdd check for the return value of drm_cvt_mode() and return the error if\nit fails in order to avoid NULL pointer dereference.(CVE-2024-43829)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\ns390/uv: Don\u0026apos;t call folio_wait_writeback() without a folio reference\r\n\r\nfolio_wait_writeback() requires that no spinlocks are held and that\na folio reference is held, as documented. After we dropped the PTL, the\nfolio could get freed concurrently. So grab a temporary reference.(CVE-2024-43832)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nmedia: v4l: async: Fix NULL pointer dereference in adding ancillary links\r\n\r\nIn v4l2_async_create_ancillary_links(), ancillary links are created for\nlens and flash sub-devices. These are sub-device to sub-device links and\nif the async notifier is related to a V4L2 device, the source sub-device\nof the ancillary link is NULL, leading to a NULL pointer dereference.\nCheck the notifier\u0026apos;s sd field is non-NULL in\nv4l2_async_create_ancillary_links().\r\n\r\n[Sakari Ailus: Reword the subject and commit messages slightly.](CVE-2024-43833)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nbpf: Fix null pointer dereference in resolve_prog_type() for BPF_PROG_TYPE_EXT\r\n\r\nWhen loading a EXT program without specifying `attr-\u0026gt;attach_prog_fd`,\nthe `prog-\u0026gt;aux-\u0026gt;dst_prog` will be null. At this time, calling\nresolve_prog_type() anywhere will result in a null pointer dereference.\r\n\r\nExample stack trace:\r\n\r\n[    8.107863] Unable to handle kernel NULL pointer dereference at virtual address 0000000000000004\n[    8.108262] Mem abort info:\n[    8.108384]   ESR = 0x0000000096000004\n[    8.108547]   EC = 0x25: DABT (current EL), IL = 32 bits\n[    8.108722]   SET = 0, FnV = 0\n[    8.108827]   EA = 0, S1PTW = 0\n[    8.108939]   FSC = 0x04: level 0 translation fault\n[    8.109102] Data abort info:\n[    8.109203]   ISV = 0, ISS = 0x00000004, ISS2 = 0x00000000\n[    8.109399]   CM = 0, WnR = 0, TnD = 0, TagAccess = 0\n[    8.109614]   GCS = 0, Overlay = 0, DirtyBit = 0, Xs = 0\n[    8.109836] user pgtable: 4k pages, 48-bit VAs, pgdp=0000000101354000\n[    8.110011] [0000000000000004] pgd=0000000000000000, p4d=0000000000000000\n[    8.112624] Internal error: Oops: 0000000096000004 [#1] PREEMPT SMP\n[    8.112783] Modules linked in:\n[    8.113120] CPU: 0 PID: 99 Comm: may_access_dire Not tainted 6.10.0-rc3-next-20240613-dirty #1\n[    8.113230] Hardware name: linux,dummy-virt (DT)\n[    8.113390] pstate: 60000005 (nZCv daif -PAN -UAO -TCO -DIT -SSBS BTYPE=--)\n[    8.113429] pc : may_access_direct_pkt_data+0x24/0xa0\n[    8.113746] lr : add_subprog_and_kfunc+0x634/0x8e8\n[    8.113798] sp : ffff80008283b9f0\n[    8.113813] x29: ffff80008283b9f0 x28: ffff800082795048 x27: 0000000000000001\n[    8.113881] x26: ffff0000c0bb2600 x25: 0000000000000000 x24: 0000000000000000\n[    8.113897] x23: ffff0000c1134000 x22: 000000000001864f x21: ffff0000c1138000\n[    8.113912] x20: 0000000000000001 x19: ffff0000c12b8000 x18: ffffffffffffffff\n[    8.113929] x17: 0000000000000000 x16: 0000000000000000 x15: 0720072007200720\n[    8.113944] x14: 0720072007200720 x13: 0720072007200720 x12: 0720072007200720\n[    8.113958] x11: 0720072007200720 x10: 0000000000f9fca4 x9 : ffff80008021f4e4\n[    8.113991] x8 : 0101010101010101 x7 : 746f72705f6d656d x6 : 000000001e0e0f5f\n[    8.114006] x5 : 000000000001864f x4 : ffff0000c12b8000 x3 : 000000000000001c\n[    8.114020] x2 : 0000000000000002 x1 : 0000000000000000 x0 : 0000000000000000\n[    8.114126] Call trace:\n[    8.114159]  may_access_direct_pkt_data+0x24/0xa0\n[    8.114202]  bpf_check+0x3bc/0x28c0\n[    8.114214]  bpf_prog_load+0x658/0xa58\n[    8.114227]  __sys_bpf+0xc50/0x2250\n[    8.114240]  __arm64_sys_bpf+0x28/0x40\n[    8.114254]  invoke_syscall.constprop.0+0x54/0xf0\n[    8.114273]  do_el0_svc+0x4c/0xd8\n[    8.114289]  el0_svc+0x3c/0x140\n[    8.114305]  el0t_64_sync_handler+0x134/0x150\n[    8.114331]  el0t_64_sync+0x168/0x170\n[    8.114477] Code: 7100707f 54000081 f9401c00 f9403800 (b9400403)\n[    8.118672] ---[ end trace 0000000000000000 ]---\r\n\r\nOne way to fix it is by forcing `attach_prog_fd` non-empty when\nbpf_prog_load(). But this will lead to `libbpf_probe_bpf_prog_type`\nAPI broken which use verifier log to probe prog type and will log\nnothing if we reject invalid EXT prog before bpf_check().\r\n\r\nAnother way is by adding null check in resolve_prog_type().\r\n\r\nThe issue was introduced by commit 4a9c7bbe2ed4 (\u0026quot;bpf: Resolve to\nprog-\u0026gt;aux-\u0026gt;dst_prog-\u0026gt;type only for BPF_PROG_TYPE_EXT\u0026quot;) which wanted\nto correct type resolution for BPF_PROG_TYPE_TRACING programs. Before\nthat, the type resolution of BPF_PROG_TYPE_EXT prog actually follows\nthe logic below:\r\n\r\n  prog-\u0026gt;aux-\u0026gt;dst_prog ? prog-\u0026gt;aux-\u0026gt;dst_prog-\u0026gt;type : prog-\u0026gt;type;\r\n\r\nIt implies that when EXT program is not yet attached to `dst_prog`,\nthe prog type should be EXT itself. This code worked fine in the past.\nSo just keep using it.\r\n\r\nFix this by returning `prog-\u0026gt;type` for BPF_PROG_TYPE_EXT if `dst_prog`\nis not present in resolve_prog_type().(CVE-2024-43837)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nwifi: virt_wifi: avoid reporting connection success with wrong SSID\r\n\r\nWhen user issues a connection with a different SSID than the one\nvirt_wifi has advertised, the __cfg80211_connect_result() will\ntrigger the warning: WARN_ON(bss_not_found).\r\n\r\nThe issue is because the connection code in virt_wifi does not\ncheck the SSID from user space (it only checks the BSSID), and\nvirt_wifi will call cfg80211_connect_result() with WLAN_STATUS_SUCCESS\neven if the SSID is different from the one virt_wifi has advertised.\nEventually cfg80211 won\u0026apos;t be able to find the cfg80211_bss and generate\nthe warning.\r\n\r\nFixed it by checking the SSID (from user space) in the connection code.(CVE-2024-43841)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nwifi: rtw89: Fix array index mistake in rtw89_sta_info_get_iter()\r\n\r\nIn rtw89_sta_info_get_iter() \u0026apos;status-\u0026gt;he_gi\u0026apos; is compared to array size.\nBut then \u0026apos;rate-\u0026gt;he_gi\u0026apos; is used as array index instead of \u0026apos;status-\u0026gt;he_gi\u0026apos;.\nThis can lead to go beyond array boundaries in case of \u0026apos;rate-\u0026gt;he_gi\u0026apos; is\nnot equal to \u0026apos;status-\u0026gt;he_gi\u0026apos; and is bigger than array size. Looks like\n\u0026quot;copy-paste\u0026quot; mistake.\r\n\r\nFix this mistake by replacing \u0026apos;rate-\u0026gt;he_gi\u0026apos; with \u0026apos;status-\u0026gt;he_gi\u0026apos;.\r\n\r\nFound by Linux Verification Center (linuxtesting.org) with SVACE.(CVE-2024-43842)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nudf: Fix bogus checksum computation in udf_rename()\r\n\r\nSyzbot reports uninitialized memory access in udf_rename() when updating\nchecksum of \u0026apos;..\u0026apos; directory entry of a moved directory. This is indeed\ntrue as we pass on-stack diriter.fi to the udf_update_tag() and because\nthat has only struct fileIdentDesc included in it and not the impUse or\nname fields, the checksumming function is going to checksum random stack\ncontents beyond the end of the structure. This is actually harmless\nbecause the following udf_fiiter_write_fi() will recompute the checksum\nfrom on-disk buffers where everything is properly included. So all that\nis needed is just removing the bogus calculation.(CVE-2024-43845)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nlib: objagg: Fix general protection fault\r\n\r\nThe library supports aggregation of objects into other objects only if\nthe parent object does not have a parent itself. That is, nesting is not\nsupported.\r\n\r\nAggregation happens in two cases: Without and with hints, where hints\nare a pre-computed recommendation on how to aggregate the provided\nobjects.\r\n\r\nNesting is not possible in the first case due to a check that prevents\nit, but in the second case there is no check because the assumption is\nthat nesting cannot happen when creating objects based on hints. The\nviolation of this assumption leads to various warnings and eventually to\na general protection fault [1].\r\n\r\nBefore fixing the root cause, error out when nesting happens and warn.\r\n\r\n[1]\ngeneral protection fault, probably for non-canonical address 0xdead000000000d90: 0000 [#1] PREEMPT SMP PTI\nCPU: 1 PID: 1083 Comm: kworker/1:9 Tainted: G        W          6.9.0-rc6-custom-gd9b4f1cca7fb #7\nHardware name: Mellanox Technologies Ltd. MSN3700/VMOD0005, BIOS 5.11 01/06/2019\nWorkqueue: mlxsw_core mlxsw_sp_acl_tcam_vregion_rehash_work\nRIP: 0010:mlxsw_sp_acl_erp_bf_insert+0x25/0x80\n[...]\nCall Trace:\n \u0026lt;TASK\u0026gt;\n mlxsw_sp_acl_atcam_entry_add+0x256/0x3c0\n mlxsw_sp_acl_tcam_entry_create+0x5e/0xa0\n mlxsw_sp_acl_tcam_vchunk_migrate_one+0x16b/0x270\n mlxsw_sp_acl_tcam_vregion_rehash_work+0xbe/0x510\n process_one_work+0x151/0x370\n worker_thread+0x2cb/0x3e0\n kthread+0xd0/0x100\n ret_from_fork+0x34/0x50\n ret_from_fork_asm+0x1a/0x30\n \u0026lt;/TASK\u0026gt;(CVE-2024-43846)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nwifi: ath12k: fix invalid memory access while processing fragmented packets\r\n\r\nThe monitor ring and the reo reinject ring share the same ring mask index.\nWhen the driver receives an interrupt for the reo reinject ring, the\nmonitor ring is also processed, leading to invalid memory access. Since\nmonitor support is not yet enabled in ath12k, the ring mask for the monitor\nring should be removed.\r\n\r\nTested-on: QCN9274 hw2.0 PCI WLAN.WBE.1.1.1-00209-QCAHKSWPL_SILICONZ-1(CVE-2024-43847)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nsoc: qcom: pdr: protect locator_addr with the main mutex\r\n\r\nIf the service locator server is restarted fast enough, the PDR can\nrewrite locator_addr fields concurrently. Protect them by placing\nmodification of those fields under the main pdr-\u0026gt;lock.(CVE-2024-43849)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nsoc: qcom: icc-bwmon: Fix refcount imbalance seen during bwmon_remove\r\n\r\nThe following warning is seen during bwmon_remove due to refcount\nimbalance, fix this by releasing the OPPs after use.\r\n\r\nLogs:\nWARNING: at drivers/opp/core.c:1640 _opp_table_kref_release+0x150/0x158\nHardware name: Qualcomm Technologies, Inc. X1E80100 CRD (DT)\n...\nCall trace:\n_opp_table_kref_release+0x150/0x158\ndev_pm_opp_remove_table+0x100/0x1b4\ndevm_pm_opp_of_table_release+0x10/0x1c\ndevm_action_release+0x14/0x20\ndevres_release_all+0xa4/0x104\ndevice_unbind_cleanup+0x18/0x60\ndevice_release_driver_internal+0x1ec/0x228\ndriver_detach+0x50/0x98\nbus_remove_driver+0x6c/0xbc\ndriver_unregister+0x30/0x60\nplatform_driver_unregister+0x14/0x20\nbwmon_driver_exit+0x18/0x524 [icc_bwmon]\n__arm64_sys_delete_module+0x184/0x264\ninvoke_syscall+0x48/0x118\nel0_svc_common.constprop.0+0xc8/0xe8\ndo_el0_svc+0x20/0x2c\nel0_svc+0x34/0xdc\nel0t_64_sync_handler+0x13c/0x158\nel0t_64_sync+0x190/0x194\n--[ end trace 0000000000000000 ]---(CVE-2024-43850)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nsoc: xilinx: rename cpu_number1 to dummy_cpu_number\r\n\r\nThe per cpu variable cpu_number1 is passed to xlnx_event_handler as\nargument \u0026quot;dev_id\u0026quot;, but it is not used in this function. So drop the\ninitialization of this variable and rename it to dummy_cpu_number.\nThis patch is to fix the following call trace when the kernel option\nCONFIG_DEBUG_ATOMIC_SLEEP is enabled:\r\n\r\nBUG: sleeping function called from invalid context at include/linux/sched/mm.h:274\n    in_atomic(): 1, irqs_disabled(): 0, non_block: 0, pid: 1, name: swapper/0\n    preempt_count: 1, expected: 0\n    CPU: 0 PID: 1 Comm: swapper/0 Not tainted 6.1.0 #53\n    Hardware name: Xilinx Versal vmk180 Eval board rev1.1 (QSPI) (DT)\n    Call trace:\n     dump_backtrace+0xd0/0xe0\n     show_stack+0x18/0x40\n     dump_stack_lvl+0x7c/0xa0\n     dump_stack+0x18/0x34\n     __might_resched+0x10c/0x140\n     __might_sleep+0x4c/0xa0\n     __kmem_cache_alloc_node+0xf4/0x168\n     kmalloc_trace+0x28/0x38\n     __request_percpu_irq+0x74/0x138\n     xlnx_event_manager_probe+0xf8/0x298\n     platform_probe+0x68/0xd8(CVE-2024-43851)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nmd: fix deadlock between mddev_suspend and flush bio\r\n\r\nDeadlock occurs when mddev is being suspended while some flush bio is in\nprogress. It is a complex issue.\r\n\r\nT1. the first flush is at the ending stage, it clears \u0026apos;mddev-\u0026gt;flush_bio\u0026apos;\n    and tries to submit data, but is blocked because mddev is suspended\n    by T4.\nT2. the second flush sets \u0026apos;mddev-\u0026gt;flush_bio\u0026apos;, and attempts to queue\n    md_submit_flush_data(), which is already running (T1) and won\u0026apos;t\n    execute again if on the same CPU as T1.\nT3. the third flush inc active_io and tries to flush, but is blocked because\n    \u0026apos;mddev-\u0026gt;flush_bio\u0026apos; is not NULL (set by T2).\nT4. mddev_suspend() is called and waits for active_io dec to 0 which is inc\n    by T3.\r\n\r\n  T1\t\tT2\t\tT3\t\tT4\n  (flush 1)\t(flush 2)\t(third 3)\t(suspend)\n  md_submit_flush_data\n   mddev-\u0026gt;flush_bio = NULL;\n   .\n   .\t \tmd_flush_request\n   .\t  \t mddev-\u0026gt;flush_bio = bio\n   .\t  \t queue submit_flushes\n   .\t\t .\n   .\t\t .\t\tmd_handle_request\n   .\t\t .\t\t active_io + 1\n   .\t\t .\t\t md_flush_request\n   .\t\t .\t\t  wait !mddev-\u0026gt;flush_bio\n   .\t\t .\n   .\t\t .\t\t\t\tmddev_suspend\n   .\t\t .\t\t\t\t wait !active_io\n   .\t\t .\n   .\t\t submit_flushes\n   .\t\t queue_work md_submit_flush_data\n   .\t\t //md_submit_flush_data is already running (T1)\n   .\n   md_handle_request\n    wait resume\r\n\r\nThe root issue is non-atomic inc/dec of active_io during flush process.\nactive_io is dec before md_submit_flush_data is queued, and inc soon\nafter md_submit_flush_data() run.\n  md_flush_request\n    active_io + 1\n    submit_flushes\n      active_io - 1\n      md_submit_flush_data\n        md_handle_request\n        active_io + 1\n          make_request\n        active_io - 1\r\n\r\nIf active_io is dec after md_handle_request() instead of within\nsubmit_flushes(), make_request() can be called directly intead of\nmd_handle_request() in md_submit_flush_data(), and active_io will\nonly inc and dec once in the whole flush process. Deadlock will be\nfixed.\r\n\r\nAdditionally, the only difference between fixing the issue and before is\nthat there is no return error handling of make_request(). But after\nprevious patch cleaned md_write_start(), make_requst() only return error\nin raid5_make_request() by dm-raid, see commit 41425f96d7aa (\u0026quot;dm-raid456,\nmd/raid456: fix a deadlock for dm-raid456 while io concurrent with\nreshape)\u0026quot;. Since dm always splits data and flush operation into two\nseparate io, io size of flush submitted by dm always is 0, make_request()\nwill not be called in md_submit_flush_data(). To prevent future\nmodifications from introducing issues, add WARN_ON to ensure\nmake_request() no error is returned in this context.(CVE-2024-43855)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\ndma: fix call order in dmam_free_coherent\r\n\r\ndmam_free_coherent() frees a DMA allocation, which makes the\nfreed vaddr available for reuse, then calls devres_destroy()\nto remove and free the data structure used to track the DMA\nallocation. Between the two calls, it is possible for a\nconcurrent task to make an allocation with the same vaddr\nand add it to the devres list.\r\n\r\nIf this happens, there will be two entries in the devres list\nwith the same vaddr and devres_destroy() can free the wrong\nentry, triggering the WARN_ON() in dmam_match.\r\n\r\nFix by destroying the devres entry before freeing the DMA\nallocation.\r\n\r\n  kokonut //net/encryption\n    http://sponge2/b9145fe6-0f72-4325-ac2f-a84d81075b03(CVE-2024-43856)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nf2fs: fix to truncate preallocated blocks in f2fs_file_open()\r\n\r\nchenyuwen reports a f2fs bug as below:\r\n\r\nUnable to handle kernel NULL pointer dereference at virtual address 0000000000000011\n fscrypt_set_bio_crypt_ctx+0x78/0x1e8\n f2fs_grab_read_bio+0x78/0x208\n f2fs_submit_page_read+0x44/0x154\n f2fs_get_read_data_page+0x288/0x5f4\n f2fs_get_lock_data_page+0x60/0x190\n truncate_partial_data_page+0x108/0x4fc\n f2fs_do_truncate_blocks+0x344/0x5f0\n f2fs_truncate_blocks+0x6c/0x134\n f2fs_truncate+0xd8/0x200\n f2fs_iget+0x20c/0x5ac\n do_garbage_collect+0x5d0/0xf6c\n f2fs_gc+0x22c/0x6a4\n f2fs_disable_checkpoint+0xc8/0x310\n f2fs_fill_super+0x14bc/0x1764\n mount_bdev+0x1b4/0x21c\n f2fs_mount+0x20/0x30\n legacy_get_tree+0x50/0xbc\n vfs_get_tree+0x5c/0x1b0\n do_new_mount+0x298/0x4cc\n path_mount+0x33c/0x5fc\n __arm64_sys_mount+0xcc/0x15c\n invoke_syscall+0x60/0x150\n el0_svc_common+0xb8/0xf8\n do_el0_svc+0x28/0xa0\n el0_svc+0x24/0x84\n el0t_64_sync_handler+0x88/0xec\r\n\r\nIt is because inode.i_crypt_info is not initialized during below path:\n- mount\n - f2fs_fill_super\n  - f2fs_disable_checkpoint\n   - f2fs_gc\n    - f2fs_iget\n     - f2fs_truncate\r\n\r\nSo, let\u0026apos;s relocate truncation of preallocated blocks to f2fs_file_open(),\nafter fscrypt_file_open().(CVE-2024-43859)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nusb: vhci-hcd: Do not drop references before new references are gained\r\n\r\nAt a few places the driver carries stale pointers\nto references that can still be used. Make sure that does not happen.\nThis strictly speaking closes ZDI-CAN-22273, though there may be\nsimilar races in the driver.(CVE-2024-43883)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nBluetooth: MGMT: Add error handling to pair_device()\r\n\r\nhci_conn_params_add() never checks for a NULL value and could lead to a NULL\npointer dereference causing a crash.\r\n\r\nFixed by adding error handling in the function.(CVE-2024-43884)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\npadata: Fix possible divide-by-0 panic in padata_mt_helper()\r\n\r\nWe are hit with a not easily reproducible divide-by-0 panic in padata.c at\nbootup time.\r\n\r\n  [   10.017908] Oops: divide error: 0000 1 PREEMPT SMP NOPTI\n  [   10.017908] CPU: 26 PID: 2627 Comm: kworker/u1666:1 Not tainted 6.10.0-15.el10.x86_64 #1\n  [   10.017908] Hardware name: Lenovo ThinkSystem SR950 [7X12CTO1WW]/[7X12CTO1WW], BIOS [PSE140J-2.30] 07/20/2021\n  [   10.017908] Workqueue: events_unbound padata_mt_helper\n  [   10.017908] RIP: 0010:padata_mt_helper+0x39/0xb0\n    :\n  [   10.017963] Call Trace:\n  [   10.017968]  \u0026lt;TASK\u0026gt;\n  [   10.018004]  ? padata_mt_helper+0x39/0xb0\n  [   10.018084]  process_one_work+0x174/0x330\n  [   10.018093]  worker_thread+0x266/0x3a0\n  [   10.018111]  kthread+0xcf/0x100\n  [   10.018124]  ret_from_fork+0x31/0x50\n  [   10.018138]  ret_from_fork_asm+0x1a/0x30\n  [   10.018147]  \u0026lt;/TASK\u0026gt;\r\n\r\nLooking at the padata_mt_helper() function, the only way a divide-by-0\npanic can happen is when ps-\u0026gt;chunk_size is 0.  The way that chunk_size is\ninitialized in padata_do_multithreaded(), chunk_size can be 0 when the\nmin_chunk in the passed-in padata_mt_job structure is 0.\r\n\r\nFix this divide-by-0 panic by making sure that chunk_size will be at least\n1 no matter what the input parameters are.(CVE-2024-43889)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\ntracing: Fix overflow in get_free_elt()\r\n\r\n\u0026quot;tracing_map-\u0026gt;next_elt\u0026quot; in get_free_elt() is at risk of overflowing.\r\n\r\nOnce it overflows, new elements can still be inserted into the tracing_map\neven though the maximum number of elements (`max_elts`) has been reached.\nContinuing to insert elements after the overflow could result in the\ntracing_map containing \u0026quot;tracing_map-\u0026gt;max_size\u0026quot; elements, leaving no empty\nentries.\nIf any attempt is made to insert an element into a full tracing_map using\n`__tracing_map_insert()`, it will cause an infinite loop with preemption\ndisabled, leading to a CPU hang problem.\r\n\r\nFix this by preventing any further increments to \u0026quot;tracing_map-\u0026gt;next_elt\u0026quot;\nonce it reaches \u0026quot;tracing_map-\u0026gt;max_elt\u0026quot;.(CVE-2024-43890)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\ntracing: Have format file honor EVENT_FILE_FL_FREED\r\n\r\nWhen eventfs was introduced, special care had to be done to coordinate the\nfreeing of the file meta data with the files that are exposed to user\nspace. The file meta data would have a ref count that is set when the file\nis created and would be decremented and freed after the last user that\nopened the file closed it. When the file meta data was to be freed, it\nwould set a flag (EVENT_FILE_FL_FREED) to denote that the file is freed,\nand any new references made (like new opens or reads) would fail as it is\nmarked freed. This allowed other meta data to be freed after this flag was\nset (under the event_mutex).\r\n\r\nAll the files that were dynamically created in the events directory had a\npointer to the file meta data and would call event_release() when the last\nreference to the user space file was closed. This would be the time that it\nis safe to free the file meta data.\r\n\r\nA shortcut was made for the \u0026quot;format\u0026quot; file. It\u0026apos;s i_private would point to\nthe \u0026quot;call\u0026quot; entry directly and not point to the file\u0026apos;s meta data. This is\nbecause all format files are the same for the same \u0026quot;call\u0026quot;, so it was\nthought there was no reason to differentiate them.  The other files\nmaintain state (like the \u0026quot;enable\u0026quot;, \u0026quot;trigger\u0026quot;, etc). But this meant if the\nfile were to disappear, the \u0026quot;format\u0026quot; file would be unaware of it.\r\n\r\nThis caused a race that could be trigger via the user_events test (that\nwould create dynamic events and free them), and running a loop that would\nread the user_events format files:\r\n\r\nIn one console run:\r\n\r\n # cd tools/testing/selftests/user_events\n # while true; do ./ftrace_test; done\r\n\r\nAnd in another console run:\r\n\r\n # cd /sys/kernel/tracing/\n # while true; do cat events/user_events/__test_event/format; done 2\u0026gt;/dev/null\r\n\r\nWith KASAN memory checking, it would trigger a use-after-free bug report\n(which was a real bug). This was because the format file was not checking\nthe file\u0026apos;s meta data flag \u0026quot;EVENT_FILE_FL_FREED\u0026quot;, so it would access the\nevent that the file meta data pointed to after the event was freed.\r\n\r\nAfter inspection, there are other locations that were found to not check\nthe EVENT_FILE_FL_FREED flag when accessing the trace_event_file. Add a\nnew helper function: event_file_file() that will make sure that the\nevent_mutex is held, and will return NULL if the trace_event_file has the\nEVENT_FILE_FL_FREED flag set. Have the first reference of the struct file\npointer use event_file_file() and check for NULL. Later uses can still use\nthe event_file_data() helper function if the event_mutex is still held and\nwas not released since the event_file_file() call.(CVE-2024-43891)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\ndrm/amd/display: Skip Recompute DSC Params if no Stream on Link\r\n\r\n[why]\nEncounter NULL pointer dereference uner mst + dsc setup.\r\n\r\nBUG: kernel NULL pointer dereference, address: 0000000000000008\n    PGD 0 P4D 0\n    Oops: 0000 [#1] PREEMPT SMP NOPTI\n    CPU: 4 PID: 917 Comm: sway Not tainted 6.3.9-arch1-1 #1 124dc55df4f5272ccb409f39ef4872fc2b3376a2\n    Hardware name: LENOVO 20NKS01Y00/20NKS01Y00, BIOS R12ET61W(1.31 ) 07/28/2022\n    RIP: 0010:drm_dp_atomic_find_time_slots+0x5e/0x260 [drm_display_helper]\n    Code: 01 00 00 48 8b 85 60 05 00 00 48 63 80 88 00 00 00 3b 43 28 0f 8d 2e 01 00 00 48 8b 53 30 48 8d 04 80 48 8d 04 c2 48 8b 40 18 \u0026lt;48\u0026gt; 8\u0026gt;\n    RSP: 0018:ffff960cc2df77d8 EFLAGS: 00010293\n    RAX: 0000000000000000 RBX: ffff8afb87e81280 RCX: 0000000000000224\n    RDX: ffff8afb9ee37c00 RSI: ffff8afb8da1a578 RDI: ffff8afb87e81280\n    RBP: ffff8afb83d67000 R08: 0000000000000001 R09: ffff8afb9652f850\n    R10: ffff960cc2df7908 R11: 0000000000000002 R12: 0000000000000000\n    R13: ffff8afb8d7688a0 R14: ffff8afb8da1a578 R15: 0000000000000224\n    FS:  00007f4dac35ce00(0000) GS:ffff8afe30b00000(0000) knlGS:0000000000000000\n    CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033\n    CR2: 0000000000000008 CR3: 000000010ddc6000 CR4: 00000000003506e0\n    Call Trace:\n\u0026lt;TASK\u0026gt;\n     ? __die+0x23/0x70\n     ? page_fault_oops+0x171/0x4e0\n     ? plist_add+0xbe/0x100\n     ? exc_page_fault+0x7c/0x180\n     ? asm_exc_page_fault+0x26/0x30\n     ? drm_dp_atomic_find_time_slots+0x5e/0x260 [drm_display_helper 0e67723696438d8e02b741593dd50d80b44c2026]\n     ? drm_dp_atomic_find_time_slots+0x28/0x260 [drm_display_helper 0e67723696438d8e02b741593dd50d80b44c2026]\n     compute_mst_dsc_configs_for_link+0x2ff/0xa40 [amdgpu 62e600d2a75e9158e1cd0a243bdc8e6da040c054]\n     ? fill_plane_buffer_attributes+0x419/0x510 [amdgpu 62e600d2a75e9158e1cd0a243bdc8e6da040c054]\n     compute_mst_dsc_configs_for_state+0x1e1/0x250 [amdgpu 62e600d2a75e9158e1cd0a243bdc8e6da040c054]\n     amdgpu_dm_atomic_check+0xecd/0x1190 [amdgpu 62e600d2a75e9158e1cd0a243bdc8e6da040c054]\n     drm_atomic_check_only+0x5c5/0xa40\n     drm_mode_atomic_ioctl+0x76e/0xbc0\r\n\r\n[how]\ndsc recompute should be skipped if no mode change detected on the new\nrequest. If detected, keep checking whether the stream is already on\ncurrent state or not.\r\n\r\n(cherry picked from commit 8151a6c13111b465dbabe07c19f572f7cbd16fef)(CVE-2024-43895)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nnet: drop bad gso csum_start and offset in virtio_net_hdr\r\n\r\nTighten csum_start and csum_offset checks in virtio_net_hdr_to_skb\nfor GSO packets.\r\n\r\nThe function already checks that a checksum requested with\nVIRTIO_NET_HDR_F_NEEDS_CSUM is in skb linear. But for GSO packets\nthis might not hold for segs after segmentation.\r\n\r\nSyzkaller demonstrated to reach this warning in skb_checksum_help\r\n\r\n\toffset = skb_checksum_start_offset(skb);\n\tret = -EINVAL;\n\tif (WARN_ON_ONCE(offset \u0026gt;= skb_headlen(skb)))\r\n\r\nBy injecting a TSO packet:\r\n\r\nWARNING: CPU: 1 PID: 3539 at net/core/dev.c:3284 skb_checksum_help+0x3d0/0x5b0\n ip_do_fragment+0x209/0x1b20 net/ipv4/ip_output.c:774\n ip_finish_output_gso net/ipv4/ip_output.c:279 [inline]\n __ip_finish_output+0x2bd/0x4b0 net/ipv4/ip_output.c:301\n iptunnel_xmit+0x50c/0x930 net/ipv4/ip_tunnel_core.c:82\n ip_tunnel_xmit+0x2296/0x2c70 net/ipv4/ip_tunnel.c:813\n __gre_xmit net/ipv4/ip_gre.c:469 [inline]\n ipgre_xmit+0x759/0xa60 net/ipv4/ip_gre.c:661\n __netdev_start_xmit include/linux/netdevice.h:4850 [inline]\n netdev_start_xmit include/linux/netdevice.h:4864 [inline]\n xmit_one net/core/dev.c:3595 [inline]\n dev_hard_start_xmit+0x261/0x8c0 net/core/dev.c:3611\n __dev_queue_xmit+0x1b97/0x3c90 net/core/dev.c:4261\n packet_snd net/packet/af_packet.c:3073 [inline]\r\n\r\nThe geometry of the bad input packet at tcp_gso_segment:\r\n\r\n[   52.003050][ T8403] skb len=12202 headroom=244 headlen=12093 tailroom=0\n[   52.003050][ T8403] mac=(168,24) mac_len=24 net=(192,52) trans=244\n[   52.003050][ T8403] shinfo(txflags=0 nr_frags=1 gso(size=1552 type=3 segs=0))\n[   52.003050][ T8403] csum(0x60000c7 start=199 offset=1536\nip_summed=3 complete_sw=0 valid=0 level=0)\r\n\r\nMitigate with stricter input validation.\r\n\r\ncsum_offset: for GSO packets, deduce the correct value from gso_type.\nThis is already done for USO. Extend it to TSO. Let UFO be:\nudp[46]_ufo_fragment ignores these fields and always computes the\nchecksum in software.\r\n\r\ncsum_start: finding the real offset requires parsing to the transport\nheader. Do not add a parser, use existing segmentation parsing. Thanks\nto SKB_GSO_DODGY, that also catches bad packets that are hw offloaded.\nAgain test both TSO and USO. Do not test UFO for the above reason, and\ndo not test UDP tunnel offload.\r\n\r\nGSO packet are almost always CHECKSUM_PARTIAL. USO packets may be\nCHECKSUM_NONE since commit 10154dbded6d6 (\u0026quot;udp: Allow GSO transmit\nfrom devices with no checksum offload\u0026quot;), but then still these fields\nare initialized correctly in udp4_hwcsum/udp6_hwcsum_outgoing. So no\nneed to test for ip_summed == CHECKSUM_PARTIAL first.\r\n\r\nThis revises an existing fix mentioned in the Fixes tag, which broke\nsmall packets with GSO offload, as detected by kselftests.(CVE-2024-43897)\r\n\r\nRejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority.(CVE-2024-43898)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\ndrm/amd/display: Fix null pointer deref in dcn20_resource.c\r\n\r\nFixes a hang thats triggered when MPV is run on a DCN401 dGPU:\r\n\r\nmpv --hwdec=vaapi --vo=gpu --hwdec-codecs=all\r\n\r\nand then enabling fullscreen playback (double click on the video)\r\n\r\nThe following calltrace will be seen:\r\n\r\n[  181.843989] BUG: kernel NULL pointer dereference, address: 0000000000000000\n[  181.843997] #PF: supervisor instruction fetch in kernel mode\n[  181.844003] #PF: error_code(0x0010) - not-present page\n[  181.844009] PGD 0 P4D 0\n[  181.844020] Oops: 0010 [#1] PREEMPT SMP NOPTI\n[  181.844028] CPU: 6 PID: 1892 Comm: gnome-shell Tainted: G        W  OE      6.5.0-41-generic #41~22.04.2-Ubuntu\n[  181.844038] Hardware name: System manufacturer System Product Name/CROSSHAIR VI HERO, BIOS 6302 10/23/2018\n[  181.844044] RIP: 0010:0x0\n[  181.844079] Code: Unable to access opcode bytes at 0xffffffffffffffd6.\n[  181.844084] RSP: 0018:ffffb593c2b8f7b0 EFLAGS: 00010246\n[  181.844093] RAX: 0000000000000000 RBX: 0000000000000000 RCX: 0000000000000004\n[  181.844099] RDX: ffffb593c2b8f804 RSI: ffffb593c2b8f7e0 RDI: ffff9e3c8e758400\n[  181.844105] RBP: ffffb593c2b8f7b8 R08: ffffb593c2b8f9c8 R09: ffffb593c2b8f96c\n[  181.844110] R10: 0000000000000000 R11: 0000000000000000 R12: ffffb593c2b8f9c8\n[  181.844115] R13: 0000000000000001 R14: ffff9e3c88000000 R15: 0000000000000005\n[  181.844121] FS:  00007c6e323bb5c0(0000) GS:ffff9e3f85f80000(0000) knlGS:0000000000000000\n[  181.844128] CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033\n[  181.844134] CR2: ffffffffffffffd6 CR3: 0000000140fbe000 CR4: 00000000003506e0\n[  181.844141] Call Trace:\n[  181.844146]  \u0026lt;TASK\u0026gt;\n[  181.844153]  ? show_regs+0x6d/0x80\n[  181.844167]  ? __die+0x24/0x80\n[  181.844179]  ? page_fault_oops+0x99/0x1b0\n[  181.844192]  ? do_user_addr_fault+0x31d/0x6b0\n[  181.844204]  ? exc_page_fault+0x83/0x1b0\n[  181.844216]  ? asm_exc_page_fault+0x27/0x30\n[  181.844237]  dcn20_get_dcc_compression_cap+0x23/0x30 [amdgpu]\n[  181.845115]  amdgpu_dm_plane_validate_dcc.constprop.0+0xe5/0x180 [amdgpu]\n[  181.845985]  amdgpu_dm_plane_fill_plane_buffer_attributes+0x300/0x580 [amdgpu]\n[  181.846848]  fill_dc_plane_info_and_addr+0x258/0x350 [amdgpu]\n[  181.847734]  fill_dc_plane_attributes+0x162/0x350 [amdgpu]\n[  181.848748]  dm_update_plane_state.constprop.0+0x4e3/0x6b0 [amdgpu]\n[  181.849791]  ? dm_update_plane_state.constprop.0+0x4e3/0x6b0 [amdgpu]\n[  181.850840]  amdgpu_dm_atomic_check+0xdfe/0x1760 [amdgpu](CVE-2024-43899)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nmedia: xc2028: avoid use-after-free in load_firmware_cb()\r\n\r\nsyzkaller reported use-after-free in load_firmware_cb() [1].\nThe reason is because the module allocated a struct tuner in tuner_probe(),\nand then the module initialization failed, the struct tuner was released.\nA worker which created during module initialization accesses this struct\ntuner later, it caused use-after-free.\r\n\r\nThe process is as follows:\r\n\r\ntask-6504           worker_thread\ntuner_probe                             \u0026lt;= alloc dvb_frontend [2]\n...\nrequest_firmware_nowait                 \u0026lt;= create a worker\n...\ntuner_remove                            \u0026lt;= free dvb_frontend\n...\n                    request_firmware_work_func  \u0026lt;= the firmware is ready\n                    load_firmware_cb    \u0026lt;= but now the dvb_frontend has been freed\r\n\r\nTo fix the issue, check the dvd_frontend in load_firmware_cb(), if it is\nnull, report a warning and just return.\r\n\r\n[1]:\n    ==================================================================\n     BUG: KASAN: use-after-free in load_firmware_cb+0x1310/0x17a0\n     Read of size 8 at addr ffff8000d7ca2308 by task kworker/2:3/6504\r\n\r\n     Call trace:\n      load_firmware_cb+0x1310/0x17a0\n      request_firmware_work_func+0x128/0x220\n      process_one_work+0x770/0x1824\n      worker_thread+0x488/0xea0\n      kthread+0x300/0x430\n      ret_from_fork+0x10/0x20\r\n\r\n     Allocated by task 6504:\n      kzalloc\n      tuner_probe+0xb0/0x1430\n      i2c_device_probe+0x92c/0xaf0\n      really_probe+0x678/0xcd0\n      driver_probe_device+0x280/0x370\n      __device_attach_driver+0x220/0x330\n      bus_for_each_drv+0x134/0x1c0\n      __device_attach+0x1f4/0x410\n      device_initial_probe+0x20/0x30\n      bus_probe_device+0x184/0x200\n      device_add+0x924/0x12c0\n      device_register+0x24/0x30\n      i2c_new_device+0x4e0/0xc44\n      v4l2_i2c_new_subdev_board+0xbc/0x290\n      v4l2_i2c_new_subdev+0xc8/0x104\n      em28xx_v4l2_init+0x1dd0/0x3770\r\n\r\n     Freed by task 6504:\n      kfree+0x238/0x4e4\n      tuner_remove+0x144/0x1c0\n      i2c_device_remove+0xc8/0x290\n      __device_release_driver+0x314/0x5fc\n      device_release_driver+0x30/0x44\n      bus_remove_device+0x244/0x490\n      device_del+0x350/0x900\n      device_unregister+0x28/0xd0\n      i2c_unregister_device+0x174/0x1d0\n      v4l2_device_unregister+0x224/0x380\n      em28xx_v4l2_init+0x1d90/0x3770\r\n\r\n     The buggy address belongs to the object at ffff8000d7ca2000\n      which belongs to the cache kmalloc-2k of size 2048\n     The buggy address is located 776 bytes inside of\n      2048-byte region [ffff8000d7ca2000, ffff8000d7ca2800)\n     The buggy address belongs to the page:\n     page:ffff7fe00035f280 count:1 mapcount:0 mapping:ffff8000c001f000 index:0x0\n     flags: 0x7ff800000000100(slab)\n     raw: 07ff800000000100 ffff7fe00049d880 0000000300000003 ffff8000c001f000\n     raw: 0000000000000000 0000000080100010 00000001ffffffff 0000000000000000\n     page dumped because: kasan: bad access detected\r\n\r\n     Memory state around the buggy address:\n      ffff8000d7ca2200: fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb\n      ffff8000d7ca2280: fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb\n     \u0026gt;ffff8000d7ca2300: fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb\n                           ^\n      ffff8000d7ca2380: fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb\n      ffff8000d7ca2400: fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb\n     ==================================================================\r\n\r\n[2]\n    Actually, it is allocated for struct tuner, and dvb_frontend is inside.(CVE-2024-43900)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\ndrm/amd/display: Add null checker before passing variables\r\n\r\nChecks null pointer before passing variables to functions.\r\n\r\nThis fixes 3 NULL_RETURNS issues reported by Coverity.(CVE-2024-43902)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\ndrm/amd/pm: Fix the null pointer dereference for vega10_hwmgr\r\n\r\nCheck return value and conduct null pointer handling to avoid null pointer dereference.(CVE-2024-43905)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\ndrm/admgpu: fix dereferencing null pointer context\r\n\r\nWhen user space sets an invalid ta type, the pointer context will be empty.\nSo it need to check the pointer context before using it(CVE-2024-43906)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\ndrm/amdgpu/pm: Fix the null pointer dereference in apply_state_adjust_rules\r\n\r\nCheck the pointer value to fix potential null pointer\ndereference(CVE-2024-43907)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\ndrm/amdgpu: Fix the null pointer dereference to ras_manager\r\n\r\nCheck ras_manager before using it(CVE-2024-43908)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\ndrm/amdgpu/pm: Fix the null pointer dereference for smu7\r\n\r\noptimize the code to avoid pass a null pointer (hwmgr-\u0026gt;backend)\nto function smu7_update_edc_leakage_table.(CVE-2024-43909)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nwifi: nl80211: disallow setting special AP channel widths\r\n\r\nSetting the AP channel width is meant for use with the normal\n20/40/... MHz channel width progression, and switching around\nin S1G or narrow channels isn\u0026apos;t supported. Disallow that.(CVE-2024-43912)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nnvme: apple: fix device reference counting\r\n\r\nDrivers must call nvme_uninit_ctrl after a successful nvme_init_ctrl.\nSplit the allocation side out to make the error handling boundary easier\nto navigate. The apple driver had been doing this wrong, leaking the\ncontroller device memory on a tagset failure.(CVE-2024-43913)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nmd/raid5: avoid BUG_ON() while continue reshape after reassembling\r\n\r\nCurrently, mdadm support --revert-reshape to abort the reshape while\nreassembling, as the test 07revert-grow. However, following BUG_ON()\ncan be triggerred by the test:\r\n\r\nkernel BUG at drivers/md/raid5.c:6278!\ninvalid opcode: 0000 [#1] PREEMPT SMP PTI\nirq event stamp: 158985\nCPU: 6 PID: 891 Comm: md0_reshape Not tainted 6.9.0-03335-g7592a0b0049a #94\nRIP: 0010:reshape_request+0x3f1/0xe60\nCall Trace:\n \u0026lt;TASK\u0026gt;\n raid5_sync_request+0x43d/0x550\n md_do_sync+0xb7a/0x2110\n md_thread+0x294/0x2b0\n kthread+0x147/0x1c0\n ret_from_fork+0x59/0x70\n ret_from_fork_asm+0x1a/0x30\n \u0026lt;/TASK\u0026gt;\r\n\r\nRoot cause is that --revert-reshape update the raid_disks from 5 to 4,\nwhile reshape position is still set, and after reassembling the array,\nreshape position will be read from super block, then during reshape the\nchecking of \u0026apos;writepos\u0026apos; that is caculated by old reshape position will\nfail.\r\n\r\nFix this panic the easy way first, by converting the BUG_ON() to\nWARN_ON(), and stop the reshape if checkings fail.\r\n\r\nNoted that mdadm must fix --revert-shape as well, and probably md/raid\nshould enhance metadata validation as well, however this means\nreassemble will fail and there must be user tools to fix the wrong\nmetadata.(CVE-2024-43914)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nnet: bridge: mcast: wait for previous gc cycles when removing port\r\n\r\nsyzbot hit a use-after-free[1] which is caused because the bridge doesn\u0026apos;t\nmake sure that all previous garbage has been collected when removing a\nport. What happens is:\n      CPU 1                   CPU 2\n start gc cycle           remove port\n                         acquire gc lock first\n wait for lock\n                         call br_multicasg_gc() directly\n acquire lock now but    free port\n the port can be freed\n while grp timers still\n running\r\n\r\nMake sure all previous gc cycles have finished by using flush_work before\nfreeing the port.\r\n\r\n[1]\n  BUG: KASAN: slab-use-after-free in br_multicast_port_group_expired+0x4c0/0x550 net/bridge/br_multicast.c:861\n  Read of size 8 at addr ffff888071d6d000 by task syz.5.1232/9699\r\n\r\n  CPU: 1 PID: 9699 Comm: syz.5.1232 Not tainted 6.10.0-rc5-syzkaller-00021-g24ca36a562d6 #0\n  Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 06/07/2024\n  Call Trace:\n   \u0026lt;IRQ\u0026gt;\n   __dump_stack lib/dump_stack.c:88 [inline]\n   dump_stack_lvl+0x116/0x1f0 lib/dump_stack.c:114\n   print_address_description mm/kasan/report.c:377 [inline]\n   print_report+0xc3/0x620 mm/kasan/report.c:488\n   kasan_report+0xd9/0x110 mm/kasan/report.c:601\n   br_multicast_port_group_expired+0x4c0/0x550 net/bridge/br_multicast.c:861\n   call_timer_fn+0x1a3/0x610 kernel/time/timer.c:1792\n   expire_timers kernel/time/timer.c:1843 [inline]\n   __run_timers+0x74b/0xaf0 kernel/time/timer.c:2417\n   __run_timer_base kernel/time/timer.c:2428 [inline]\n   __run_timer_base kernel/time/timer.c:2421 [inline]\n   run_timer_base+0x111/0x190 kernel/time/timer.c:2437(CVE-2024-44934)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nsctp: Fix null-ptr-deref in reuseport_add_sock().\r\n\r\nsyzbot reported a null-ptr-deref while accessing sk2-\u0026gt;sk_reuseport_cb in\nreuseport_add_sock(). [0]\r\n\r\nThe repro first creates a listener with SO_REUSEPORT.  Then, it creates\nanother listener on the same port and concurrently closes the first\nlistener.\r\n\r\nThe second listen() calls reuseport_add_sock() with the first listener as\nsk2, where sk2-\u0026gt;sk_reuseport_cb is not expected to be cleared concurrently,\nbut the close() does clear it by reuseport_detach_sock().\r\n\r\nThe problem is SCTP does not properly synchronise reuseport_alloc(),\nreuseport_add_sock(), and reuseport_detach_sock().\r\n\r\nThe caller of reuseport_alloc() and reuseport_{add,detach}_sock() must\nprovide synchronisation for sockets that are classified into the same\nreuseport group.\r\n\r\nOtherwise, such sockets form multiple identical reuseport groups, and\nall groups except one would be silently dead.\r\n\r\n  1. Two sockets call listen() concurrently\n  2. No socket in the same group found in sctp_ep_hashtable[]\n  3. Two sockets call reuseport_alloc() and form two reuseport groups\n  4. Only one group hit first in __sctp_rcv_lookup_endpoint() receives\n      incoming packets\r\n\r\nAlso, the reported null-ptr-deref could occur.\r\n\r\nTCP/UDP guarantees that would not happen by holding the hash bucket lock.\r\n\r\nLet\u0026apos;s apply the locking strategy to __sctp_hash_endpoint() and\n__sctp_unhash_endpoint().\r\n\r\n[0]:\nOops: general protection fault, probably for non-canonical address 0xdffffc0000000002: 0000 [#1] PREEMPT SMP KASAN PTI\nKASAN: null-ptr-deref in range [0x0000000000000010-0x0000000000000017]\nCPU: 1 UID: 0 PID: 10230 Comm: syz-executor119 Not tainted 6.10.0-syzkaller-12585-g301927d2d2eb #0\nHardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 06/27/2024\nRIP: 0010:reuseport_add_sock+0x27e/0x5e0 net/core/sock_reuseport.c:350\nCode: 00 0f b7 5d 00 bf 01 00 00 00 89 de e8 1b a4 ff f7 83 fb 01 0f 85 a3 01 00 00 e8 6d a0 ff f7 49 8d 7e 12 48 89 f8 48 c1 e8 03 \u0026lt;42\u0026gt; 0f b6 04 28 84 c0 0f 85 4b 02 00 00 41 0f b7 5e 12 49 8d 7e 14\nRSP: 0018:ffffc9000b947c98 EFLAGS: 00010202\nRAX: 0000000000000002 RBX: ffff8880252ddf98 RCX: ffff888079478000\nRDX: 0000000000000000 RSI: 0000000000000001 RDI: 0000000000000012\nRBP: 0000000000000001 R08: ffffffff8993e18d R09: 1ffffffff1fef385\nR10: dffffc0000000000 R11: fffffbfff1fef386 R12: ffff8880252ddac0\nR13: dffffc0000000000 R14: 0000000000000000 R15: 0000000000000000\nFS:  00007f24e45b96c0(0000) GS:ffff8880b9300000(0000) knlGS:0000000000000000\nCS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033\nCR2: 00007ffcced5f7b8 CR3: 00000000241be000 CR4: 00000000003506f0\nDR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000\n DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400\nCall Trace:\n \u0026lt;TASK\u0026gt;\n __sctp_hash_endpoint net/sctp/input.c:762 [inline]\n sctp_hash_endpoint+0x52a/0x600 net/sctp/input.c:790\n sctp_listen_start net/sctp/socket.c:8570 [inline]\n sctp_inet_listen+0x767/0xa20 net/sctp/socket.c:8625\n __sys_listen_socket net/socket.c:1883 [inline]\n __sys_listen+0x1b7/0x230 net/socket.c:1894\n __do_sys_listen net/socket.c:1902 [inline]\n __se_sys_listen net/socket.c:1900 [inline]\n __x64_sys_listen+0x5a/0x70 net/socket.c:1900\n do_syscall_x64 arch/x86/entry/common.c:52 [inline]\n do_syscall_64+0xf3/0x230 arch/x86/entry/common.c:83\n entry_SYSCALL_64_after_hwframe+0x77/0x7f\nRIP: 0033:0x7f24e46039b9\nCode: 28 00 00 00 75 05 48 83 c4 28 c3 e8 91 1a 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 b0 ff ff ff f7 d8 64 89 01 48\nRSP: 002b:00007f24e45b9228 EFLAGS: 00000246 ORIG_RAX: 0000000000000032\nRAX: ffffffffffffffda RBX: 00007f24e468e428 RCX: 00007f24e46039b9\nRDX: 00007f24e46039b9 RSI: 0000000000000003 RDI: 0000000000000004\nRBP: 00007f24e468e420 R08: 00007f24e45b96c0 R09: 00007f24e45b96c0\nR10: 00007f24e45b96c0 R11: 0000000000000246 R12: 00007f24e468e42c\nR13:\n---truncated---(CVE-2024-44935)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nfou: remove warn in gue_gro_receive on unsupported protocol\r\n\r\nDrop the WARN_ON_ONCE inn gue_gro_receive if the encapsulated type is\nnot known or does not have a GRO handler.\r\n\r\nSuch a packet is easily constructed. Syzbot generates them and sets\noff this warning.\r\n\r\nRemove the warning as it is expected and not actionable.\r\n\r\nThe warning was previously reduced from WARN_ON to WARN_ON_ONCE in\ncommit 270136613bf7 (\u0026quot;fou: Do WARN_ON_ONCE in gue_gro_receive for bad\nproto callbacks\u0026quot;).(CVE-2024-44940)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nf2fs: fix to do sanity check on F2FS_INLINE_DATA flag in inode during GC\r\n\r\nsyzbot reports a f2fs bug as below:\r\n\r\n------------[ cut here ]------------\nkernel BUG at fs/f2fs/inline.c:258!\nCPU: 1 PID: 34 Comm: kworker/u8:2 Not tainted 6.9.0-rc6-syzkaller-00012-g9e4bc4bcae01 #0\nRIP: 0010:f2fs_write_inline_data+0x781/0x790 fs/f2fs/inline.c:258\nCall Trace:\n f2fs_write_single_data_page+0xb65/0x1d60 fs/f2fs/data.c:2834\n f2fs_write_cache_pages fs/f2fs/data.c:3133 [inline]\n __f2fs_write_data_pages fs/f2fs/data.c:3288 [inline]\n f2fs_write_data_pages+0x1efe/0x3a90 fs/f2fs/data.c:3315\n do_writepages+0x35b/0x870 mm/page-writeback.c:2612\n __writeback_single_inode+0x165/0x10b0 fs/fs-writeback.c:1650\n writeback_sb_inodes+0x905/0x1260 fs/fs-writeback.c:1941\n wb_writeback+0x457/0xce0 fs/fs-writeback.c:2117\n wb_do_writeback fs/fs-writeback.c:2264 [inline]\n wb_workfn+0x410/0x1090 fs/fs-writeback.c:2304\n process_one_work kernel/workqueue.c:3254 [inline]\n process_scheduled_works+0xa12/0x17c0 kernel/workqueue.c:3335\n worker_thread+0x86d/0xd70 kernel/workqueue.c:3416\n kthread+0x2f2/0x390 kernel/kthread.c:388\n ret_from_fork+0x4d/0x80 arch/x86/kernel/process.c:147\n ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:244\r\n\r\nThe root cause is: inline_data inode can be fuzzed, so that there may\nbe valid blkaddr in its direct node, once f2fs triggers background GC\nto migrate the block, it will hit f2fs_bug_on() during dirty page\nwriteback.\r\n\r\nLet\u0026apos;s add sanity check on F2FS_INLINE_DATA flag in inode during GC,\nso that, it can forbid migrating inline_data inode\u0026apos;s data block for\nfixing.(CVE-2024-44942)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nkcm: Serialise kcm_sendmsg() for the same socket.\r\n\r\nsyzkaller reported UAF in kcm_release(). [0]\r\n\r\nThe scenario is\r\n\r\n  1. Thread A builds a skb with MSG_MORE and sets kcm-\u0026gt;seq_skb.\r\n\r\n  2. Thread A resumes building skb from kcm-\u0026gt;seq_skb but is blocked\n     by sk_stream_wait_memory()\r\n\r\n  3. Thread B calls sendmsg() concurrently, finishes building kcm-\u0026gt;seq_skb\n     and puts the skb to the write queue\r\n\r\n  4. Thread A faces an error and finally frees skb that is already in the\n     write queue\r\n\r\n  5. kcm_release() does double-free the skb in the write queue\r\n\r\nWhen a thread is building a MSG_MORE skb, another thread must not touch it.\r\n\r\nLet\u0026apos;s add a per-sk mutex and serialise kcm_sendmsg().\r\n\r\n[0]:\nBUG: KASAN: slab-use-after-free in __skb_unlink include/linux/skbuff.h:2366 [inline]\nBUG: KASAN: slab-use-after-free in __skb_dequeue include/linux/skbuff.h:2385 [inline]\nBUG: KASAN: slab-use-after-free in __skb_queue_purge_reason include/linux/skbuff.h:3175 [inline]\nBUG: KASAN: slab-use-after-free in __skb_queue_purge include/linux/skbuff.h:3181 [inline]\nBUG: KASAN: slab-use-after-free in kcm_release+0x170/0x4c8 net/kcm/kcmsock.c:1691\nRead of size 8 at addr ffff0000ced0fc80 by task syz-executor329/6167\r\n\r\nCPU: 1 PID: 6167 Comm: syz-executor329 Tainted: G    B              6.8.0-rc5-syzkaller-g9abbc24128bc #0\nHardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/25/2024\nCall trace:\n dump_backtrace+0x1b8/0x1e4 arch/arm64/kernel/stacktrace.c:291\n show_stack+0x2c/0x3c arch/arm64/kernel/stacktrace.c:298\n __dump_stack lib/dump_stack.c:88 [inline]\n dump_stack_lvl+0xd0/0x124 lib/dump_stack.c:106\n print_address_description mm/kasan/report.c:377 [inline]\n print_report+0x178/0x518 mm/kasan/report.c:488\n kasan_report+0xd8/0x138 mm/kasan/report.c:601\n __asan_report_load8_noabort+0x20/0x2c mm/kasan/report_generic.c:381\n __skb_unlink include/linux/skbuff.h:2366 [inline]\n __skb_dequeue include/linux/skbuff.h:2385 [inline]\n __skb_queue_purge_reason include/linux/skbuff.h:3175 [inline]\n __skb_queue_purge include/linux/skbuff.h:3181 [inline]\n kcm_release+0x170/0x4c8 net/kcm/kcmsock.c:1691\n __sock_release net/socket.c:659 [inline]\n sock_close+0xa4/0x1e8 net/socket.c:1421\n __fput+0x30c/0x738 fs/file_table.c:376\n ____fput+0x20/0x30 fs/file_table.c:404\n task_work_run+0x230/0x2e0 kernel/task_work.c:180\n exit_task_work include/linux/task_work.h:38 [inline]\n do_exit+0x618/0x1f64 kernel/exit.c:871\n do_group_exit+0x194/0x22c kernel/exit.c:1020\n get_signal+0x1500/0x15ec kernel/signal.c:2893\n do_signal+0x23c/0x3b44 arch/arm64/kernel/signal.c:1249\n do_notify_resume+0x74/0x1f4 arch/arm64/kernel/entry-common.c:148\n exit_to_user_mode_prepare arch/arm64/kernel/entry-common.c:169 [inline]\n exit_to_user_mode arch/arm64/kernel/entry-common.c:178 [inline]\n el0_svc+0xac/0x168 arch/arm64/kernel/entry-common.c:713\n el0t_64_sync_handler+0x84/0xfc arch/arm64/kernel/entry-common.c:730\n el0t_64_sync+0x190/0x194 arch/arm64/kernel/entry.S:598\r\n\r\nAllocated by task 6166:\n kasan_save_stack mm/kasan/common.c:47 [inline]\n kasan_save_track+0x40/0x78 mm/kasan/common.c:68\n kasan_save_alloc_info+0x70/0x84 mm/kasan/generic.c:626\n unpoison_slab_object mm/kasan/common.c:314 [inline]\n __kasan_slab_alloc+0x74/0x8c mm/kasan/common.c:340\n kasan_slab_alloc include/linux/kasan.h:201 [inline]\n slab_post_alloc_hook mm/slub.c:3813 [inline]\n slab_alloc_node mm/slub.c:3860 [inline]\n kmem_cache_alloc_node+0x204/0x4c0 mm/slub.c:3903\n __alloc_skb+0x19c/0x3d8 net/core/skbuff.c:641\n alloc_skb include/linux/skbuff.h:1296 [inline]\n kcm_sendmsg+0x1d3c/0x2124 net/kcm/kcmsock.c:783\n sock_sendmsg_nosec net/socket.c:730 [inline]\n __sock_sendmsg net/socket.c:745 [inline]\n sock_sendmsg+0x220/0x2c0 net/socket.c:768\n splice_to_socket+0x7cc/0xd58 fs/splice.c:889\n do_splice_from fs/splice.c:941 [inline]\n direct_splice_actor+0xec/0x1d8 fs/splice.c:1164\n splice_direct_to_actor+0x438/0xa0c fs/splice.c:1108\n do_splice_direct_actor \n---truncated---(CVE-2024-44946)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nfuse: Initialize beyond-EOF page contents before setting uptodate\r\n\r\nfuse_notify_store(), unlike fuse_do_readpage(), does not enable page\nzeroing (because it can be used to change partial page contents).\r\n\r\nSo fuse_notify_store() must be more careful to fully initialize page\ncontents (including parts of the page that are beyond end-of-file)\nbefore marking the page uptodate.\r\n\r\nThe current code can leave beyond-EOF page contents uninitialized, which\nmakes these uninitialized page contents visible to userspace via mmap().\r\n\r\nThis is an information leak, but only affects systems which do not\nenable init-on-alloc (via CONFIG_INIT_ON_ALLOC_DEFAULT_ON=y or the\ncorresponding kernel command line parameter).(CVE-2024-44947)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\ndrm/amdgpu: Forward soft recovery errors to userspace\r\n\r\nAs we discussed before[1], soft recovery should be\nforwarded to userspace, or we can get into a really\nbad state where apps will keep submitting hanging\ncommand buffers cascading us to a hard reset.\r\n\r\n1: https://lore.kernel.org/all/bf23d5ed-9a6b-43e7-84ee-8cbfd0d60f18@froggi.es/\n(cherry picked from commit 434967aadbbbe3ad9103cc29e9a327de20fdba01)(CVE-2024-44961)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nbinfmt_flat: Fix corruption when not offsetting data start\r\n\r\nCommit 04d82a6d0881 (\u0026quot;binfmt_flat: allow not offsetting data start\u0026quot;)\nintroduced a RISC-V specific variant of the FLAT format which does\nnot allocate any space for the (obsolete) array of shared library\npointers. However, it did not disable the code which initializes the\narray, resulting in the corruption of sizeof(long) bytes before the DATA\nsegment, generally the end of the TEXT segment.\r\n\r\nIntroduce MAX_SHARED_LIBS_UPDATE which depends on the state of\nCONFIG_BINFMT_FLAT_NO_DATA_START_OFFSET to guard the initialization of\nthe shared library pointer region so that it will only be initialized\nif space is reserved for it.(CVE-2024-44966)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nnet: dsa: bcm_sf2: Fix a possible memory leak in bcm_sf2_mdio_register()\r\n\r\nbcm_sf2_mdio_register() calls of_phy_find_device() and then\nphy_device_remove() in a loop to remove existing PHY devices.\nof_phy_find_device() eventually calls bus_find_device(), which calls\nget_device() on the returned struct device * to increment the refcount.\nThe current implementation does not decrement the refcount, which causes\nmemory leak.\r\n\r\nThis commit adds the missing phy_device_free() call to decrement the\nrefcount via put_device() to balance the refcount.(CVE-2024-44971)","status":"published","published":"2024-09-14T11:07:36Z","modified":"2026-08-18T01:18:36.810734965Z","cvss":[{"version":"3.1","score":7.8,"vector":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H","level":"high"}],"updated_at":"2026-11-02T15:52:41.595342Z"},{"id":"OESA-2024-2321","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\niommu/vt-d: Fix double list_add when enabling VMD in scalable mode\r\n\r\nWhen enabling VMD and IOMMU scalable mode, the following kernel panic\ncall trace/kernel log is shown in Eagle Stream platform (Sapphire Rapids\nCPU) during booting:\r\n\r\npci 0000:59:00.5: Adding to iommu group 42\n...\nvmd 0000:59:00.5: PCI host bridge to bus 10000:80\npci 10000:80:01.0: [8086:352a] type 01 class 0x060400\npci 10000:80:01.0: reg 0x10: [mem 0x00000000-0x0001ffff 64bit]\npci 10000:80:01.0: enabling Extended Tags\npci 10000:80:01.0: PME# supported from D0 D3hot D3cold\npci 10000:80:01.0: DMAR: Setup RID2PASID failed\npci 10000:80:01.0: Failed to add to iommu group 42: -16\npci 10000:80:03.0: [8086:352b] type 01 class 0x060400\npci 10000:80:03.0: reg 0x10: [mem 0x00000000-0x0001ffff 64bit]\npci 10000:80:03.0: enabling Extended Tags\npci 10000:80:03.0: PME# supported from D0 D3hot D3cold\n------------[ cut here ]------------\nkernel BUG at lib/list_debug.c:29!\ninvalid opcode: 0000 [#1] PREEMPT SMP NOPTI\nCPU: 0 PID: 7 Comm: kworker/0:1 Not tainted 5.17.0-rc3+ #7\nHardware name: Lenovo ThinkSystem SR650V3/SB27A86647, BIOS ESE101Y-1.00 01/13/2022\nWorkqueue: events work_for_cpu_fn\nRIP: 0010:__list_add_valid.cold+0x26/0x3f\nCode: 9a 4a ab ff 4c 89 c1 48 c7 c7 40 0c d9 9e e8 b9 b1 fe ff 0f\n      0b 48 89 f2 4c 89 c1 48 89 fe 48 c7 c7 f0 0c d9 9e e8 a2 b1\n      fe ff \u0026lt;0f\u0026gt; 0b 48 89 d1 4c 89 c6 4c 89 ca 48 c7 c7 98 0c d9\n      9e e8 8b b1 fe\nRSP: 0000:ff5ad434865b3a40 EFLAGS: 00010246\nRAX: 0000000000000058 RBX: ff4d61160b74b880 RCX: ff4d61255e1fffa8\nRDX: 0000000000000000 RSI: 00000000fffeffff RDI: ffffffff9fd34f20\nRBP: ff4d611d8e245c00 R08: 0000000000000000 R09: ff5ad434865b3888\nR10: ff5ad434865b3880 R11: ff4d61257fdc6fe8 R12: ff4d61160b74b8a0\nR13: ff4d61160b74b8a0 R14: ff4d611d8e245c10 R15: ff4d611d8001ba70\nFS:  0000000000000000(0000) GS:ff4d611d5ea00000(0000) knlGS:0000000000000000\nCS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033\nCR2: ff4d611fa1401000 CR3: 0000000aa0210001 CR4: 0000000000771ef0\nDR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000\nDR3: 0000000000000000 DR6: 00000000fffe07f0 DR7: 0000000000000400\nPKRU: 55555554\nCall Trace:\n \u0026lt;TASK\u0026gt;\n intel_pasid_alloc_table+0x9c/0x1d0\n dmar_insert_one_dev_info+0x423/0x540\n ? device_to_iommu+0x12d/0x2f0\n intel_iommu_attach_device+0x116/0x290\n __iommu_attach_device+0x1a/0x90\n iommu_group_add_device+0x190/0x2c0\n __iommu_probe_device+0x13e/0x250\n iommu_probe_device+0x24/0x150\n iommu_bus_notifier+0x69/0x90\n blocking_notifier_call_chain+0x5a/0x80\n device_add+0x3db/0x7b0\n ? arch_memremap_can_ram_remap+0x19/0x50\n ? memremap+0x75/0x140\n pci_device_add+0x193/0x1d0\n pci_scan_single_device+0xb9/0xf0\n pci_scan_slot+0x4c/0x110\n pci_scan_child_bus_extend+0x3a/0x290\n vmd_enable_domain.constprop.0+0x63e/0x820\n vmd_probe+0x163/0x190\n local_pci_probe+0x42/0x80\n work_for_cpu_fn+0x13/0x20\n process_one_work+0x1e2/0x3b0\n worker_thread+0x1c4/0x3a0\n ? rescuer_thread+0x370/0x370\n kthread+0xc7/0xf0\n ? kthread_complete_and_exit+0x20/0x20\n ret_from_fork+0x1f/0x30\n \u0026lt;/TASK\u0026gt;\nModules linked in:\n---[ end trace 0000000000000000 ]---\n...\nKernel panic - not syncing: Fatal exception\nKernel Offset: 0x1ca00000 from 0xffffffff81000000 (relocation range: 0xffffffff80000000-0xffffffffbfffffff)\n---[ end Kernel panic - not syncing: Fatal exception ]---\r\n\r\nThe following \u0026apos;lspci\u0026apos; output shows devices \u0026apos;10000:80:*\u0026apos; are subdevices of\nthe VMD device 0000:59:00.5:\r\n\r\n  $ lspci\n  ...\n  0000:59:00.5 RAID bus controller: Intel Corporation Volume Management Device NVMe RAID Controller (rev 20)\n  ...\n  10000:80:01.0 PCI bridge: Intel Corporation Device 352a (rev 03)\n  10000:80:03.0 PCI bridge: Intel Corporation Device 352b (rev 03)\n  10000:80:05.0 PCI bridge: Intel Corporation Device 352c (rev 03)\n  10000:80:07.0 PCI bridge: Intel Corporation Device 352d (rev 03)\n  10000:81:00.0 Non-Volatile memory controller: Intel Corporation NVMe Datacenter SSD [3DNAND, Beta Rock Controller]\n  10000:82:00\n---truncated---(CVE-2022-48916)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  PCI: mt7621: Add sentinel to quirks table  Current driver is missing a sentinel in the struct soc_device_attribute array, which causes an oops when assessed by the soc_device_match(mt7621_pcie_quirks_match) call.  This was only exposed once the CONFIG_SOC_MT7621 mt7621 soc_dev_attr was fixed to register the SOC as a device, in:  commit 7c18b64bba3b (\u0026quot;mips: ralink: mt7621: do not use kzalloc too early\u0026quot;)  Fix it by adding the required sentinel.(CVE-2022-48952)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  ntb: intel: Fix the NULL vs IS_ERR() bug for debugfs_create_dir()  The debugfs_create_dir() function returns error pointers. It never returns NULL. So use IS_ERR() to check it.(CVE-2023-52917)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  media: pci: cx23885: check cx23885_vdev_init() return  cx23885_vdev_init() can return a NULL pointer, but that pointer is used in the next line without a check.  Add a NULL pointer check and go to the error unwind if it is NULL.(CVE-2023-52918)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nof: module: prevent NULL pointer dereference in vsnprintf()\r\n\r\nIn of_modalias(), we can get passed the str and len parameters which would\ncause a kernel oops in vsnprintf() since it only allows passing a NULL ptr\nwhen the length is also 0. Also, we need to filter out the negative values\nof the len parameter as these will result in a really huge buffer since\nsnprintf() takes size_t parameter while ours is ssize_t...\r\n\r\nFound by Linux Verification Center (linuxtesting.org) with the Svace static\nanalysis tool.(CVE-2024-35878)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\ndma: xilinx_dpdma: Fix locking\r\n\r\nThere are several places where either chan-\u0026gt;lock or chan-\u0026gt;vchan.lock was\nnot held. Add appropriate locking. This fixes lockdep warnings like\r\n\r\n[   31.077578] ------------[ cut here ]------------\n[   31.077831] WARNING: CPU: 2 PID: 40 at drivers/dma/xilinx/xilinx_dpdma.c:834 xilinx_dpdma_chan_queue_transfer+0x274/0x5e0\n[   31.077953] Modules linked in:\n[   31.078019] CPU: 2 PID: 40 Comm: kworker/u12:1 Not tainted 6.6.20+ #98\n[   31.078102] Hardware name: xlnx,zynqmp (DT)\n[   31.078169] Workqueue: events_unbound deferred_probe_work_func\n[   31.078272] pstate: 600000c5 (nZCv daIF -PAN -UAO -TCO -DIT -SSBS BTYPE=--)\n[   31.078377] pc : xilinx_dpdma_chan_queue_transfer+0x274/0x5e0\n[   31.078473] lr : xilinx_dpdma_chan_queue_transfer+0x270/0x5e0\n[   31.078550] sp : ffffffc083bb2e10\n[   31.078590] x29: ffffffc083bb2e10 x28: 0000000000000000 x27: ffffff880165a168\n[   31.078754] x26: ffffff880164e920 x25: ffffff880164eab8 x24: ffffff880164d480\n[   31.078920] x23: ffffff880165a148 x22: ffffff880164e988 x21: 0000000000000000\n[   31.079132] x20: ffffffc082aa3000 x19: ffffff880164e880 x18: 0000000000000000\n[   31.079295] x17: 0000000000000000 x16: 0000000000000000 x15: 0000000000000000\n[   31.079453] x14: 0000000000000000 x13: ffffff8802263dc0 x12: 0000000000000001\n[   31.079613] x11: 0001ffc083bb2e34 x10: 0001ff880164e98f x9 : 0001ffc082aa3def\n[   31.079824] x8 : 0001ffc082aa3dec x7 : 0000000000000000 x6 : 0000000000000516\n[   31.079982] x5 : ffffffc7f8d43000 x4 : ffffff88003c9c40 x3 : ffffffffffffffff\n[   31.080147] x2 : ffffffc7f8d43000 x1 : 00000000000000c0 x0 : 0000000000000000\n[   31.080307] Call trace:\n[   31.080340]  xilinx_dpdma_chan_queue_transfer+0x274/0x5e0\n[   31.080518]  xilinx_dpdma_issue_pending+0x11c/0x120\n[   31.080595]  zynqmp_disp_layer_update+0x180/0x3ac\n[   31.080712]  zynqmp_dpsub_plane_atomic_update+0x11c/0x21c\n[   31.080825]  drm_atomic_helper_commit_planes+0x20c/0x684\n[   31.080951]  drm_atomic_helper_commit_tail+0x5c/0xb0\n[   31.081139]  commit_tail+0x234/0x294\n[   31.081246]  drm_atomic_helper_commit+0x1f8/0x210\n[   31.081363]  drm_atomic_commit+0x100/0x140\n[   31.081477]  drm_client_modeset_commit_atomic+0x318/0x384\n[   31.081634]  drm_client_modeset_commit_locked+0x8c/0x24c\n[   31.081725]  drm_client_modeset_commit+0x34/0x5c\n[   31.081812]  __drm_fb_helper_restore_fbdev_mode_unlocked+0x104/0x168\n[   31.081899]  drm_fb_helper_set_par+0x50/0x70\n[   31.081971]  fbcon_init+0x538/0xc48\n[   31.082047]  visual_init+0x16c/0x23c\n[   31.082207]  do_bind_con_driver.isra.0+0x2d0/0x634\n[   31.082320]  do_take_over_console+0x24c/0x33c\n[   31.082429]  do_fbcon_takeover+0xbc/0x1b0\n[   31.082503]  fbcon_fb_registered+0x2d0/0x34c\n[   31.082663]  register_framebuffer+0x27c/0x38c\n[   31.082767]  __drm_fb_helper_initial_config_and_unlock+0x5c0/0x91c\n[   31.082939]  drm_fb_helper_initial_config+0x50/0x74\n[   31.083012]  drm_fbdev_dma_client_hotplug+0xb8/0x108\n[   31.083115]  drm_client_register+0xa0/0xf4\n[   31.083195]  drm_fbdev_dma_setup+0xb0/0x1cc\n[   31.083293]  zynqmp_dpsub_drm_init+0x45c/0x4e0\n[   31.083431]  zynqmp_dpsub_probe+0x444/0x5e0\n[   31.083616]  platform_probe+0x8c/0x13c\n[   31.083713]  really_probe+0x258/0x59c\n[   31.083793]  __driver_probe_device+0xc4/0x224\n[   31.083878]  driver_probe_device+0x70/0x1c0\n[   31.083961]  __device_attach_driver+0x108/0x1e0\n[   31.084052]  bus_for_each_drv+0x9c/0x100\n[   31.084125]  __device_attach+0x100/0x298\n[   31.084207]  device_initial_probe+0x14/0x20\n[   31.084292]  bus_probe_device+0xd8/0xdc\n[   31.084368]  deferred_probe_work_func+0x11c/0x180\n[   31.084451]  process_one_work+0x3ac/0x988\n[   31.084643]  worker_thread+0x398/0x694\n[   31.084752]  kthread+0x1bc/0x1c0\n[   31.084848]  ret_from_fork+0x10/0x20\n[   31.084932] irq event stamp: 64549\n[   31.084970] hardirqs last  enabled at (64548): [\u0026lt;ffffffc081adf35c\u0026gt;] _raw_spin_unlock_irqrestore+0x80/0x90\n[   31.085157]\n---truncated---(CVE-2024-35990)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nnetfilter: nfnetlink_queue: acquire rcu_read_lock() in instance_destroy_rcu()\r\n\r\nsyzbot reported that nf_reinject() could be called without rcu_read_lock() :\r\n\r\nWARNING: suspicious RCU usage\n6.9.0-rc7-syzkaller-02060-g5c1672705a1a #0 Not tainted\r\n\r\nnet/netfilter/nfnetlink_queue.c:263 suspicious rcu_dereference_check() usage!\r\n\r\nother info that might help us debug this:\r\n\r\nrcu_scheduler_active = 2, debug_locks = 1\n2 locks held by syz-executor.4/13427:\n  #0: ffffffff8e334f60 (rcu_callback){....}-{0:0}, at: rcu_lock_acquire include/linux/rcupdate.h:329 [inline]\n  #0: ffffffff8e334f60 (rcu_callback){....}-{0:0}, at: rcu_do_batch kernel/rcu/tree.c:2190 [inline]\n  #0: ffffffff8e334f60 (rcu_callback){....}-{0:0}, at: rcu_core+0xa86/0x1830 kernel/rcu/tree.c:2471\n  #1: ffff88801ca92958 (\u0026amp;inst-\u0026gt;lock){+.-.}-{2:2}, at: spin_lock_bh include/linux/spinlock.h:356 [inline]\n  #1: ffff88801ca92958 (\u0026amp;inst-\u0026gt;lock){+.-.}-{2:2}, at: nfqnl_flush net/netfilter/nfnetlink_queue.c:405 [inline]\n  #1: ffff88801ca92958 (\u0026amp;inst-\u0026gt;lock){+.-.}-{2:2}, at: instance_destroy_rcu+0x30/0x220 net/netfilter/nfnetlink_queue.c:172\r\n\r\nstack backtrace:\nCPU: 0 PID: 13427 Comm: syz-executor.4 Not tainted 6.9.0-rc7-syzkaller-02060-g5c1672705a1a #0\nHardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 04/02/2024\nCall Trace:\n \u0026lt;IRQ\u0026gt;\n  __dump_stack lib/dump_stack.c:88 [inline]\n  dump_stack_lvl+0x241/0x360 lib/dump_stack.c:114\n  lockdep_rcu_suspicious+0x221/0x340 kernel/locking/lockdep.c:6712\n  nf_reinject net/netfilter/nfnetlink_queue.c:323 [inline]\n  nfqnl_reinject+0x6ec/0x1120 net/netfilter/nfnetlink_queue.c:397\n  nfqnl_flush net/netfilter/nfnetlink_queue.c:410 [inline]\n  instance_destroy_rcu+0x1ae/0x220 net/netfilter/nfnetlink_queue.c:172\n  rcu_do_batch kernel/rcu/tree.c:2196 [inline]\n  rcu_core+0xafd/0x1830 kernel/rcu/tree.c:2471\n  handle_softirqs+0x2d6/0x990 kernel/softirq.c:554\n  __do_softirq kernel/softirq.c:588 [inline]\n  invoke_softirq kernel/softirq.c:428 [inline]\n  __irq_exit_rcu+0xf4/0x1c0 kernel/softirq.c:637\n  irq_exit_rcu+0x9/0x30 kernel/softirq.c:649\n  instr_sysvec_apic_timer_interrupt arch/x86/kernel/apic/apic.c:1043 [inline]\n  sysvec_apic_timer_interrupt+0xa6/0xc0 arch/x86/kernel/apic/apic.c:1043\n \u0026lt;/IRQ\u0026gt;\n \u0026lt;TASK\u0026gt;(CVE-2024-36286)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nALSA: core: Fix NULL module pointer assignment at card init\r\n\r\nThe commit 81033c6b584b (\u0026quot;ALSA: core: Warn on empty module\u0026quot;)\nintroduced a WARN_ON() for a NULL module pointer passed at snd_card\nobject creation, and it also wraps the code around it with \u0026apos;#ifdef\nMODULE\u0026apos;.  This works in most cases, but the devils are always in\ndetails.  \u0026quot;MODULE\u0026quot; is defined when the target code (i.e. the sound\ncore) is built as a module; but this doesn\u0026apos;t mean that the caller is\nalso built-in or not.  Namely, when only the sound core is built-in\n(CONFIG_SND=y) while the driver is a module (CONFIG_SND_USB_AUDIO=m),\nthe passed module pointer is ignored even if it\u0026apos;s non-NULL, and\ncard-\u0026gt;module remains as NULL.  This would result in the missing module\nreference up/down at the device open/close, leading to a race with the\ncode execution after the module removal.\r\n\r\nFor addressing the bug, move the assignment of card-\u0026gt;module again out\nof ifdef.  The WARN_ON() is still wrapped with ifdef because the\nmodule can be really NULL when all sound drivers are built-in.\r\n\r\nNote that we keep \u0026apos;ifdef MODULE\u0026apos; for WARN_ON(), otherwise it would\nlead to a false-positive NULL module check.  Admittedly it won\u0026apos;t catch\nperfectly, i.e. no check is performed when CONFIG_SND=y.  But, it\u0026apos;s no\nreal problem as it\u0026apos;s only for debugging, and the condition is pretty\nrare.(CVE-2024-38605)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nsoundwire: cadence: fix invalid PDI offset\r\n\r\nFor some reason, we add an offset to the PDI, presumably to skip the\nPDI0 and PDI1 which are reserved for BPT.\r\n\r\nThis code is however completely wrong and leads to an out-of-bounds\naccess. We were just lucky so far since we used only a couple of PDIs\nand remained within the PDI array bounds.\r\n\r\nA Fixes: tag is not provided since there are no known platforms where\nthe out-of-bounds would be accessed, and the initial code had problems\nas well.\r\n\r\nA follow-up patch completely removes this useless offset.(CVE-2024-38635)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nriscv: prevent pt_regs corruption for secondary idle threads\r\n\r\nTop of the kernel thread stack should be reserved for pt_regs. However\nthis is not the case for the idle threads of the secondary boot harts.\nTheir stacks overlap with their pt_regs, so both may get corrupted.\r\n\r\nSimilar issue has been fixed for the primary hart, see c7cdd96eca28\n(\u0026quot;riscv: prevent stack corruption by reserving task_pt_regs(p) early\u0026quot;).\nHowever that fix was not propagated to the secondary harts. The problem\nhas been noticed in some CPU hotplug tests with V enabled. The function\nsmp_callin stored several registers on stack, corrupting top of pt_regs\nstructure including status field. As a result, kernel attempted to save\nor restore inexistent V context.(CVE-2024-38667)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nnvmet: fix a possible leak when destroy a ctrl during qp establishment\r\n\r\nIn nvmet_sq_destroy we capture sq-\u0026gt;ctrl early and if it is non-NULL we\nknow that a ctrl was allocated (in the admin connect request handler)\nand we need to release pending AERs, clear ctrl-\u0026gt;sqs and sq-\u0026gt;ctrl\n(for nvme-loop primarily), and drop the final reference on the ctrl.\r\n\r\nHowever, a small window is possible where nvmet_sq_destroy starts (as\na result of the client giving up and disconnecting) concurrently with\nthe nvme admin connect cmd (which may be in an early stage). But *before*\nkill_and_confirm of sq-\u0026gt;ref (i.e. the admin connect managed to get an sq\nlive reference). In this case, sq-\u0026gt;ctrl was allocated however after it was\ncaptured in a local variable in nvmet_sq_destroy.\nThis prevented the final reference drop on the ctrl.\r\n\r\nSolve this by re-capturing the sq-\u0026gt;ctrl after all inflight request has\ncompleted, where for sure sq-\u0026gt;ctrl reference is final, and move forward\nbased on that.\r\n\r\nThis issue was observed in an environment with many hosts connecting\nmultiple ctrls simoutanuosly, creating a delay in allocating a ctrl\nleading up to this race window.(CVE-2024-42152)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\ndev/parport: fix the array out-of-bounds risk\r\n\r\nFixed array out-of-bounds issues caused by sprintf\nby replacing it with snprintf for safer data copying,\nensuring the destination buffer is not overflowed.\r\n\r\nBelow is the stack trace I encountered during the actual issue:\r\n\r\n[ 66.575408s] [pid:5118,cpu4,QThread,4]Kernel panic - not syncing: stack-protector:\nKernel stack is corrupted in: do_hardware_base_addr+0xcc/0xd0 [parport]\n[ 66.575408s] [pid:5118,cpu4,QThread,5]CPU: 4 PID: 5118 Comm:\nQThread Tainted: G S W O 5.10.97-arm64-desktop #7100.57021.2\n[ 66.575439s] [pid:5118,cpu4,QThread,6]TGID: 5087 Comm: EFileApp\n[ 66.575439s] [pid:5118,cpu4,QThread,7]Hardware name: HUAWEI HUAWEI QingYun\nPGUX-W515x-B081/SP1PANGUXM, BIOS 1.00.07 04/29/2024\n[ 66.575439s] [pid:5118,cpu4,QThread,8]Call trace:\n[ 66.575469s] [pid:5118,cpu4,QThread,9] dump_backtrace+0x0/0x1c0\n[ 66.575469s] [pid:5118,cpu4,QThread,0] show_stack+0x14/0x20\n[ 66.575469s] [pid:5118,cpu4,QThread,1] dump_stack+0xd4/0x10c\n[ 66.575500s] [pid:5118,cpu4,QThread,2] panic+0x1d8/0x3bc\n[ 66.575500s] [pid:5118,cpu4,QThread,3] __stack_chk_fail+0x2c/0x38\n[ 66.575500s] [pid:5118,cpu4,QThread,4] do_hardware_base_addr+0xcc/0xd0 [parport](CVE-2024-42301)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nexfat: fix potential deadlock on __exfat_get_dentry_set\r\n\r\nWhen accessing a file with more entries than ES_MAX_ENTRY_NUM, the bh-array\nis allocated in __exfat_get_entry_set. The problem is that the bh-array is\nallocated with GFP_KERNEL. It does not make sense. In the following cases,\na deadlock for sbi-\u0026gt;s_lock between the two processes may occur.\r\n\r\n       CPU0                CPU1\n       ----                ----\n  kswapd\n   balance_pgdat\n    lock(fs_reclaim)\n                      exfat_iterate\n                       lock(\u0026amp;sbi-\u0026gt;s_lock)\n                       exfat_readdir\n                        exfat_get_uniname_from_ext_entry\n                         exfat_get_dentry_set\n                          __exfat_get_dentry_set\n                           kmalloc_array\n                            ...\n                            lock(fs_reclaim)\n    ...\n    evict\n     exfat_evict_inode\n      lock(\u0026amp;sbi-\u0026gt;s_lock)\r\n\r\nTo fix this, let\u0026apos;s allocate bh-array with GFP_NOFS.(CVE-2024-42315)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nwifi: virt_wifi: avoid reporting connection success with wrong SSID\r\n\r\nWhen user issues a connection with a different SSID than the one\nvirt_wifi has advertised, the __cfg80211_connect_result() will\ntrigger the warning: WARN_ON(bss_not_found).\r\n\r\nThe issue is because the connection code in virt_wifi does not\ncheck the SSID from user space (it only checks the BSSID), and\nvirt_wifi will call cfg80211_connect_result() with WLAN_STATUS_SUCCESS\neven if the SSID is different from the one virt_wifi has advertised.\nEventually cfg80211 won\u0026apos;t be able to find the cfg80211_bss and generate\nthe warning.\r\n\r\nFixed it by checking the SSID (from user space) in the connection code.(CVE-2024-43841)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\njfs: Fix array-index-out-of-bounds in diFree(CVE-2024-43858)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\ndrm/nouveau: prime: fix refcount underflow\r\n\r\nCalling nouveau_bo_ref() on a nouveau_bo without initializing it (and\nhence the backing ttm_bo) leads to a refcount underflow.\r\n\r\nInstead of calling nouveau_bo_ref() in the unwind path of\ndrm_gem_object_init(), clean things up manually.\r\n\r\n(cherry picked from commit 1b93f3e89d03cfc576636e195466a0d728ad8de5)(CVE-2024-43867)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\ndevres: Fix memory leakage caused by driver API devm_free_percpu()\r\n\r\nIt will cause memory leakage when use driver API devm_free_percpu()\nto free memory allocated by devm_alloc_percpu(), fixed by using\ndevres_release() instead of devres_destroy() within devm_free_percpu().(CVE-2024-43871)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\ndrm/client: fix null pointer dereference in drm_client_modeset_probe\r\n\r\nIn drm_client_modeset_probe(), the return value of drm_mode_duplicate() is\nassigned to modeset-\u0026gt;mode, which will lead to a possible NULL pointer\ndereference on failure of drm_mode_duplicate(). Add a check to avoid npd.(CVE-2024-43894)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nmptcp: pm: only decrement add_addr_accepted for MPJ req\r\n\r\nAdding the following warning ...\r\n\r\n  WARN_ON_ONCE(msk-\u0026gt;pm.add_addr_accepted == 0)\r\n\r\n... before decrementing the add_addr_accepted counter helped to find a\nbug when running the \u0026quot;remove single subflow\u0026quot; subtest from the\nmptcp_join.sh selftest.\r\n\r\nRemoving a \u0026apos;subflow\u0026apos; endpoint will first trigger a RM_ADDR, then the\nsubflow closure. Before this patch, and upon the reception of the\nRM_ADDR, the other peer will then try to decrement this\nadd_addr_accepted. That\u0026apos;s not correct because the attached subflows have\nnot been created upon the reception of an ADD_ADDR.\r\n\r\nA way to solve that is to decrement the counter only if the attached\nsubflow was an MP_JOIN to a remote id that was not 0, and initiated by\nthe host receiving the RM_ADDR.(CVE-2024-45009)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nusb: dwc3: core: Prevent USB core invalid event buffer address access\r\n\r\nThis commit addresses an issue where the USB core could access an\ninvalid event buffer address during runtime suspend, potentially causing\nSMMU faults and other memory issues in Exynos platforms. The problem\narises from the following sequence.\n        1. In dwc3_gadget_suspend, there is a chance of a timeout when\n        moving the USB core to the halt state after clearing the\n        run/stop bit by software.\n        2. In dwc3_core_exit, the event buffer is cleared regardless of\n        the USB core\u0026apos;s status, which may lead to an SMMU faults and\n        other memory issues. if the USB core tries to access the event\n        buffer address.\r\n\r\nTo prevent this hardware quirk on Exynos platforms, this commit ensures\nthat the event buffer address is not cleared by software  when the USB\ncore is active during runtime suspend by checking its status before\nclearing the buffer address.(CVE-2024-46675)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nsoc: qcom: cmd-db: Map shared memory as WC, not WB\r\n\r\nLinux does not write into cmd-db region. This region of memory is write\nprotected by XPU. XPU may sometime falsely detect clean cache eviction\nas \u0026quot;write\u0026quot; into the write protected region leading to secure interrupt\nwhich causes an endless loop somewhere in Trust Zone.\r\n\r\nThe only reason it is working right now is because Qualcomm Hypervisor\nmaps the same region as Non-Cacheable memory in Stage 2 translation\ntables. The issue manifests if we want to use another hypervisor (like\nXen or KVM), which does not know anything about those specific mappings.\r\n\r\nChanging the mapping of cmd-db memory from MEMREMAP_WB to MEMREMAP_WT/WC\nremoves dependency on correct mappings in Stage 2 tables. This patch\nfixes the issue by updating the mapping to MEMREMAP_WC.\r\n\r\nI tested this on SA8155P with Xen.(CVE-2024-46689)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\ndrm/amdgpu: fix mc_data out-of-bounds read warning\r\n\r\nClear warning that read mc_data[i-1] may out-of-bounds.(CVE-2024-46722)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\ndrm/amdgpu: Fix out-of-bounds read of df_v1_7_channel_number\r\n\r\nCheck the fb_channel_number range to avoid the array out-of-bounds\nread error(CVE-2024-46724)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nhwmon: (nct6775-core) Fix underflows seen when writing limit attributes\r\n\r\nDIV_ROUND_CLOSEST() after kstrtol() results in an underflow if a large\nnegative number such as -9223372036854775808 is provided by the user.\nFix it by reordering clamp_val() and DIV_ROUND_CLOSEST() operations.(CVE-2024-46757)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\ndrm/amd/display: added NULL check at start of dc_validate_stream\r\n\r\n[Why]\nprevent invalid memory access\r\n\r\n[How]\ncheck if dc and stream are NULL(CVE-2024-46802)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nKVM: x86: Acquire kvm-\u0026gt;srcu when handling KVM_SET_VCPU_EVENTS\r\n\r\nGrab kvm-\u0026gt;srcu when processing KVM_SET_VCPU_EVENTS, as KVM will forcibly\nleave nested VMX/SVM if SMM mode is being toggled, and leaving nested VMX\nreads guest memory.\r\n\r\nNote, kvm_vcpu_ioctl_x86_set_vcpu_events() can also be called from KVM_RUN\nvia sync_regs(), which already holds SRCU.  I.e. trying to precisely use\nkvm_vcpu_srcu_read_lock() around the problematic SMM code would cause\nproblems.  Acquiring SRCU isn\u0026apos;t all that expensive, so for simplicity,\ngrab it unconditionally for KVM_SET_VCPU_EVENTS.\r\n\r\n =============================\n WARNING: suspicious RCU usage\n 6.10.0-rc7-332d2c1d713e-next-vm #552 Not tainted\n -----------------------------\n include/linux/kvm_host.h:1027 suspicious rcu_dereference_check() usage!\r\n\r\n other info that might help us debug this:\r\n\r\n rcu_scheduler_active = 2, debug_locks = 1\n 1 lock held by repro/1071:\n  #0: ffff88811e424430 (\u0026amp;vcpu-\u0026gt;mutex){+.+.}-{3:3}, at: kvm_vcpu_ioctl+0x7d/0x970 [kvm]\r\n\r\n stack backtrace:\n CPU: 15 PID: 1071 Comm: repro Not tainted 6.10.0-rc7-332d2c1d713e-next-vm #552\n Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 0.0.0 02/06/2015\n Call Trace:\n  \u0026lt;TASK\u0026gt;\n  dump_stack_lvl+0x7f/0x90\n  lockdep_rcu_suspicious+0x13f/0x1a0\n  kvm_vcpu_gfn_to_memslot+0x168/0x190 [kvm]\n  kvm_vcpu_read_guest+0x3e/0x90 [kvm]\n  nested_vmx_load_msr+0x6b/0x1d0 [kvm_intel]\n  load_vmcs12_host_state+0x432/0xb40 [kvm_intel]\n  vmx_leave_nested+0x30/0x40 [kvm_intel]\n  kvm_vcpu_ioctl_x86_set_vcpu_events+0x15d/0x2b0 [kvm]\n  kvm_arch_vcpu_ioctl+0x1107/0x1750 [kvm]\n  ? mark_held_locks+0x49/0x70\n  ? kvm_vcpu_ioctl+0x7d/0x970 [kvm]\n  ? kvm_vcpu_ioctl+0x497/0x970 [kvm]\n  kvm_vcpu_ioctl+0x497/0x970 [kvm]\n  ? lock_acquire+0xba/0x2d0\n  ? find_held_lock+0x2b/0x80\n  ? do_user_addr_fault+0x40c/0x6f0\n  ? lock_release+0xb7/0x270\n  __x64_sys_ioctl+0x82/0xb0\n  do_syscall_64+0x6c/0x170\n  entry_SYSCALL_64_after_hwframe+0x4b/0x53\n RIP: 0033:0x7ff11eb1b539\n  \u0026lt;/TASK\u0026gt;(CVE-2024-46830)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nspi: nxp-fspi: fix the KASAN report out-of-bounds bug\r\n\r\nChange the memcpy length to fix the out-of-bounds issue when writing the\ndata that is not 4 byte aligned to TX FIFO.\r\n\r\nTo reproduce the issue, write 3 bytes data to NOR chip.\r\n\r\ndd if=3b of=/dev/mtd0\n[   36.926103] ==================================================================\n[   36.933409] BUG: KASAN: slab-out-of-bounds in nxp_fspi_exec_op+0x26ec/0x2838\n[   36.940514] Read of size 4 at addr ffff00081037c2a0 by task dd/455\n[   36.946721]\n[   36.948235] CPU: 3 UID: 0 PID: 455 Comm: dd Not tainted 6.11.0-rc5-gc7b0e37c8434 #1070\n[   36.956185] Hardware name: Freescale i.MX8QM MEK (DT)\n[   36.961260] Call trace:\n[   36.963723]  dump_backtrace+0x90/0xe8\n[   36.967414]  show_stack+0x18/0x24\n[   36.970749]  dump_stack_lvl+0x78/0x90\n[   36.974451]  print_report+0x114/0x5cc\n[   36.978151]  kasan_report+0xa4/0xf0\n[   36.981670]  __asan_report_load_n_noabort+0x1c/0x28\n[   36.986587]  nxp_fspi_exec_op+0x26ec/0x2838\n[   36.990800]  spi_mem_exec_op+0x8ec/0xd30\n[   36.994762]  spi_mem_no_dirmap_read+0x190/0x1e0\n[   36.999323]  spi_mem_dirmap_write+0x238/0x32c\n[   37.003710]  spi_nor_write_data+0x220/0x374\n[   37.007932]  spi_nor_write+0x110/0x2e8\n[   37.011711]  mtd_write_oob_std+0x154/0x1f0\n[   37.015838]  mtd_write_oob+0x104/0x1d0\n[   37.019617]  mtd_write+0xb8/0x12c\n[   37.022953]  mtdchar_write+0x224/0x47c\n[   37.026732]  vfs_write+0x1e4/0x8c8\n[   37.030163]  ksys_write+0xec/0x1d0\n[   37.033586]  __arm64_sys_write+0x6c/0x9c\n[   37.037539]  invoke_syscall+0x6c/0x258\n[   37.041327]  el0_svc_common.constprop.0+0x160/0x22c\n[   37.046244]  do_el0_svc+0x44/0x5c\n[   37.049589]  el0_svc+0x38/0x78\n[   37.052681]  el0t_64_sync_handler+0x13c/0x158\n[   37.057077]  el0t_64_sync+0x190/0x194\n[   37.060775]\n[   37.062274] Allocated by task 455:\n[   37.065701]  kasan_save_stack+0x2c/0x54\n[   37.069570]  kasan_save_track+0x20/0x3c\n[   37.073438]  kasan_save_alloc_info+0x40/0x54\n[   37.077736]  __kasan_kmalloc+0xa0/0xb8\n[   37.081515]  __kmalloc_noprof+0x158/0x2f8\n[   37.085563]  mtd_kmalloc_up_to+0x120/0x154\n[   37.089690]  mtdchar_write+0x130/0x47c\n[   37.093469]  vfs_write+0x1e4/0x8c8\n[   37.096901]  ksys_write+0xec/0x1d0\n[   37.100332]  __arm64_sys_write+0x6c/0x9c\n[   37.104287]  invoke_syscall+0x6c/0x258\n[   37.108064]  el0_svc_common.constprop.0+0x160/0x22c\n[   37.112972]  do_el0_svc+0x44/0x5c\n[   37.116319]  el0_svc+0x38/0x78\n[   37.119401]  el0t_64_sync_handler+0x13c/0x158\n[   37.123788]  el0t_64_sync+0x190/0x194\n[   37.127474]\n[   37.128977] The buggy address belongs to the object at ffff00081037c2a0\n[   37.128977]  which belongs to the cache kmalloc-8 of size 8\n[   37.141177] The buggy address is located 0 bytes inside of\n[   37.141177]  allocated 3-byte region [ffff00081037c2a0, ffff00081037c2a3)\n[   37.153465]\n[   37.154971] The buggy address belongs to the physical page:\n[   37.160559] page: refcount:1 mapcount:0 mapping:0000000000000000 index:0x0 pfn:0x89037c\n[   37.168596] flags: 0xbfffe0000000000(node=0|zone=2|lastcpupid=0x1ffff)\n[   37.175149] page_type: 0xfdffffff(slab)\n[   37.179021] raw: 0bfffe0000000000 ffff000800002500 dead000000000122 0000000000000000\n[   37.186788] raw: 0000000000000000 0000000080800080 00000001fdffffff 0000000000000000\n[   37.194553] page dumped because: kasan: bad access detected\n[   37.200144]\n[   37.201647] Memory state around the buggy address:\n[   37.206460]  ffff00081037c180: fa fc fc fc fa fc fc fc fa fc fc fc fa fc fc fc\n[   37.213701]  ffff00081037c200: fa fc fc fc 05 fc fc fc 03 fc fc fc 02 fc fc fc\n[   37.220946] \u0026gt;ffff00081037c280: 06 fc fc fc 03 fc fc fc fc fc fc fc fc fc fc fc\n[   37.228186]                                ^\n[   37.232473]  ffff00081037c300: fc fc fc fc fc fc fc fc fc fc fc fc fc fc fc fc\n[   37.239718]  ffff00081037c380: fc fc fc fc fc fc fc fc fc fc fc fc fc fc fc fc\n[   37.246962] ==============================================================\n---truncated---(CVE-2024-46853)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nPCI: keystone: Add workaround for Errata #i2037 (AM65x SR 1.0)\r\n\r\nErrata #i2037 in AM65x/DRA80xM Processors Silicon Revision 1.0\n(SPRZ452D_July 2018_Revised December 2019 [1]) mentions when an\ninbound PCIe TLP spans more than two internal AXI 128-byte bursts,\nthe bus may corrupt the packet payload and the corrupt data may\ncause associated applications or the processor to hang.\r\n\r\nThe workaround for Errata #i2037 is to limit the maximum read\nrequest size and maximum payload size to 128 bytes. Add workaround\nfor Errata #i2037 here.\r\n\r\nThe errata and workaround is applicable only to AM65x SR 1.0 and\nlater versions of the silicon will have this fixed.\r\n\r\n[1] -\u0026gt; https://www.ti.com/lit/er/sprz452i/sprz452i.pdf(CVE-2024-47667)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nnilfs2: fix state management in error path of log writing function\r\n\r\nAfter commit a694291a6211 (\u0026quot;nilfs2: separate wait function from\nnilfs_segctor_write\u0026quot;) was applied, the log writing function\nnilfs_segctor_do_construct() was able to issue I/O requests continuously\neven if user data blocks were split into multiple logs across segments,\nbut two potential flaws were introduced in its error handling.\r\n\r\nFirst, if nilfs_segctor_begin_construction() fails while creating the\nsecond or subsequent logs, the log writing function returns without\ncalling nilfs_segctor_abort_construction(), so the writeback flag set on\npages/folios will remain uncleared.  This causes page cache operations to\nhang waiting for the writeback flag.  For example,\ntruncate_inode_pages_final(), which is called via nilfs_evict_inode() when\nan inode is evicted from memory, will hang.\r\n\r\nSecond, the NILFS_I_COLLECTED flag set on normal inodes remain uncleared. \nAs a result, if the next log write involves checkpoint creation, that\u0026apos;s\nfine, but if a partial log write is performed that does not, inodes with\nNILFS_I_COLLECTED set are erroneously removed from the \u0026quot;sc_dirty_files\u0026quot;\nlist, and their data and b-tree blocks may not be written to the device,\ncorrupting the block mapping.\r\n\r\nFix these issues by uniformly calling nilfs_segctor_abort_construction()\non failure of each step in the loop in nilfs_segctor_do_construct(),\nhaving it clean up logs and segment usages according to progress, and\ncorrecting the conditions for calling nilfs_redirty_inodes() to ensure\nthat the NILFS_I_COLLECTED flag is cleared.(CVE-2024-47669)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  tcp: check skb is non-NULL in tcp_rto_delta_us()  We have some machines running stock Ubuntu 20.04.6 which is their 5.4.0-174-generic kernel that are running ceph and recently hit a null ptr dereference in tcp_rearm_rto(). Initially hitting it from the TLP path, but then later we also saw it getting hit from the RACK case as well. Here are examples of the oops messages we saw in each of those cases:  Jul 26 15:05:02 rx [11061395.780353] BUG: kernel NULL pointer dereference, address: 0000000000000020 Jul 26 15:05:02 rx [11061395.787572] #PF: supervisor read access in kernel mode Jul 26 15:05:02 rx [11061395.792971] #PF: error_code(0x0000) - not-present page Jul 26 15:05:02 rx [11061395.798362] PGD 0 P4D 0 Jul 26 15:05:02 rx [11061395.801164] Oops: 0000 [#1] SMP NOPTI Jul 26 15:05:02 rx [11061395.805091] CPU: 0 PID: 9180 Comm: msgr-worker-1 Tainted: G W 5.4.0-174-generic #193-Ubuntu Jul 26 15:05:02 rx [11061395.814996] Hardware name: Supermicro SMC 2x26 os-gen8 64C NVME-Y 256G/H12SSW-NTR, BIOS 2.5.V1.2U.NVMe.UEFI 05/09/2023 Jul 26 15:05:02 rx [11061395.825952] RIP: 0010:tcp_rearm_rto+0xe4/0x160 Jul 26 15:05:02 rx [11061395.830656] Code: 87 ca 04 00 00 00 5b 41 5c 41 5d 5d c3 c3 49 8b bc 24 40 06 00 00 eb 8d 48 bb cf f7 53 e3 a5 9b c4 20 4c 89 ef e8 0c fe 0e 00 \u0026lt;48\u0026gt; 8b 78 20 48 c1 ef 03 48 89 f8 41 8b bc 24 80 04 00 00 48 f7 e3 Jul 26 15:05:02 rx [11061395.849665] RSP: 0018:ffffb75d40003e08 EFLAGS: 00010246 Jul 26 15:05:02 rx [11061395.855149] RAX: 0000000000000000 RBX: 20c49ba5e353f7cf RCX: 0000000000000000 Jul 26 15:05:02 rx [11061395.862542] RDX: 0000000062177c30 RSI: 000000000000231c RDI: ffff9874ad283a60 Jul 26 15:05:02 rx [11061395.869933] RBP: ffffb75d40003e20 R08: 0000000000000000 R09: ffff987605e20aa8 Jul 26 15:05:02 rx [11061395.877318] R10: ffffb75d40003f00 R11: ffffb75d4460f740 R12: ffff9874ad283900 Jul 26 15:05:02 rx [11061395.884710] R13: ffff9874ad283a60 R14: ffff9874ad283980 R15: ffff9874ad283d30 Jul 26 15:05:02 rx [11061395.892095] FS: 00007f1ef4a2e700(0000) GS:ffff987605e00000(0000) knlGS:0000000000000000 Jul 26 15:05:02 rx [11061395.900438] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 Jul 26 15:05:02 rx [11061395.906435] CR2: 0000000000000020 CR3: 0000003e450ba003 CR4: 0000000000760ef0 Jul 26 15:05:02 rx [11061395.913822] PKRU: 55555554 Jul 26 15:05:02 rx [11061395.916786] Call Trace: Jul 26 15:05:02 rx [11061395.919488] Jul 26 15:05:02 rx [11061395.921765] ? show_regs.cold+0x1a/0x1f Jul 26 15:05:02 rx [11061395.925859] ? __die+0x90/0xd9 Jul 26 15:05:02 rx [11061395.929169] ? no_context+0x196/0x380 Jul 26 15:05:02 rx [11061395.933088] ? ip6_protocol_deliver_rcu+0x4e0/0x4e0 Jul 26 15:05:02 rx [11061395.938216] ? ip6_sublist_rcv_finish+0x3d/0x50 Jul 26 15:05:02 rx [11061395.943000] ? __bad_area_nosemaphore+0x50/0x1a0 Jul 26 15:05:02 rx [11061395.947873] ? bad_area_nosemaphore+0x16/0x20 Jul 26 15:05:02 rx [11061395.952486] ? do_user_addr_fault+0x267/0x450 Jul 26 15:05:02 rx [11061395.957104] ? ipv6_list_rcv+0x112/0x140 Jul 26 15:05:02 rx [11061395.961279] ? __do_page_fault+0x58/0x90 Jul 26 15:05:02 rx [11061395.965458] ? do_page_fault+0x2c/0xe0 Jul 26 15:05:02 rx [11061395.969465] ? page_fault+0x34/0x40 Jul 26 15:05:02 rx [11061395.973217] ? tcp_rearm_rto+0xe4/0x160 Jul 26 15:05:02 rx [11061395.977313] ? tcp_rearm_rto+0xe4/0x160 Jul 26 15:05:02 rx [11061395.981408] tcp_send_loss_probe+0x10b/0x220 Jul 26 15:05:02 rx [11061395.985937] tcp_write_timer_handler+0x1b4/0x240 Jul 26 15:05:02 rx [11061395.990809] tcp_write_timer+0x9e/0xe0 Jul 26 15:05:02 rx [11061395.994814] ? tcp_write_timer_handler+0x240/0x240 Jul 26 15:05:02 rx [11061395.999866] call_timer_fn+0x32/0x130 Jul 26 15:05:02 rx [11061396.003782] __run_timers.part.0+0x180/0x280 Jul 26 15:05:02 rx [11061396.008309] ? recalibrate_cpu_khz+0x10/0x10 Jul 26 15:05:02 rx [11061396.012841] ? native_x2apic_icr_write+0x30/0x30 Jul 26 15:05:02 rx [11061396.017718] ? lapic_next_even ---truncated---(CVE-2024-47684)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  netfilter: nf_reject_ipv6: fix nf_reject_ip6_tcphdr_put()  syzbot reported that nf_reject_ip6_tcphdr_put() was possibly sending garbage on the four reserved tcp bits (th-\u0026gt;res1)  Use skb_put_zero() to clear the whole TCP header, as done in nf_reject_ip_tcphdr_put()  BUG: KMSAN: uninit-value in nf_reject_ip6_tcphdr_put+0x688/0x6c0 net/ipv6/netfilter/nf_reject_ipv6.c:255   nf_reject_ip6_tcphdr_put+0x688/0x6c0 net/ipv6/netfilter/nf_reject_ipv6.c:255   nf_send_reset6+0xd84/0x15b0 net/ipv6/netfilter/nf_reject_ipv6.c:344   nft_reject_inet_eval+0x3c1/0x880 net/netfilter/nft_reject_inet.c:48   expr_call_ops_eval net/netfilter/nf_tables_core.c:240 [inline]   nft_do_chain+0x438/0x22a0 net/netfilter/nf_tables_core.c:288   nft_do_chain_inet+0x41a/0x4f0 net/netfilter/nft_chain_filter.c:161   nf_hook_entry_hookfn include/linux/netfilter.h:154 [inline]   nf_hook_slow+0xf4/0x400 net/netfilter/core.c:626   nf_hook include/linux/netfilter.h:269 [inline]   NF_HOOK include/linux/netfilter.h:312 [inline]   ipv6_rcv+0x29b/0x390 net/ipv6/ip6_input.c:310   __netif_receive_skb_one_core net/core/dev.c:5661 [inline]   __netif_receive_skb+0x1da/0xa00 net/core/dev.c:5775   process_backlog+0x4ad/0xa50 net/core/dev.c:6108   __napi_poll+0xe7/0x980 net/core/dev.c:6772   napi_poll net/core/dev.c:6841 [inline]   net_rx_action+0xa5a/0x19b0 net/core/dev.c:6963   handle_softirqs+0x1ce/0x800 kernel/softirq.c:554   __do_softirq+0x14/0x1a kernel/softirq.c:588   do_softirq+0x9a/0x100 kernel/softirq.c:455   __local_bh_enable_ip+0x9f/0xb0 kernel/softirq.c:382   local_bh_enable include/linux/bottom_half.h:33 [inline]   rcu_read_unlock_bh include/linux/rcupdate.h:908 [inline]   __dev_queue_xmit+0x2692/0x5610 net/core/dev.c:4450   dev_queue_xmit include/linux/netdevice.h:3105 [inline]   neigh_resolve_output+0x9ca/0xae0 net/core/neighbour.c:1565   neigh_output include/net/neighbour.h:542 [inline]   ip6_finish_output2+0x2347/0x2ba0 net/ipv6/ip6_output.c:141   __ip6_finish_output net/ipv6/ip6_output.c:215 [inline]   ip6_finish_output+0xbb8/0x14b0 net/ipv6/ip6_output.c:226   NF_HOOK_COND include/linux/netfilter.h:303 [inline]   ip6_output+0x356/0x620 net/ipv6/ip6_output.c:247   dst_output include/net/dst.h:450 [inline]   NF_HOOK include/linux/netfilter.h:314 [inline]   ip6_xmit+0x1ba6/0x25d0 net/ipv6/ip6_output.c:366   inet6_csk_xmit+0x442/0x530 net/ipv6/inet6_connection_sock.c:135   __tcp_transmit_skb+0x3b07/0x4880 net/ipv4/tcp_output.c:1466   tcp_transmit_skb net/ipv4/tcp_output.c:1484 [inline]   tcp_connect+0x35b6/0x7130 net/ipv4/tcp_output.c:4143   tcp_v6_connect+0x1bcc/0x1e40 net/ipv6/tcp_ipv6.c:333   __inet_stream_connect+0x2ef/0x1730 net/ipv4/af_inet.c:679   inet_stream_connect+0x6a/0xd0 net/ipv4/af_inet.c:750   __sys_connect_file net/socket.c:2061 [inline]   __sys_connect+0x606/0x690 net/socket.c:2078   __do_sys_connect net/socket.c:2088 [inline]   __se_sys_connect net/socket.c:2085 [inline]   __x64_sys_connect+0x91/0xe0 net/socket.c:2085   x64_sys_call+0x27a5/0x3ba0 arch/x86/include/generated/asm/syscalls_64.h:43   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 stored to memory at:   nf_reject_ip6_tcphdr_put+0x60c/0x6c0 net/ipv6/netfilter/nf_reject_ipv6.c:249   nf_send_reset6+0xd84/0x15b0 net/ipv6/netfilter/nf_reject_ipv6.c:344   nft_reject_inet_eval+0x3c1/0x880 net/netfilter/nft_reject_inet.c:48   expr_call_ops_eval net/netfilter/nf_tables_core.c:240 [inline]   nft_do_chain+0x438/0x22a0 net/netfilter/nf_tables_core.c:288   nft_do_chain_inet+0x41a/0x4f0 net/netfilter/nft_chain_filter.c:161   nf_hook_entry_hookfn include/linux/netfilter.h:154 [inline]   nf_hook_slow+0xf4/0x400 net/netfilter/core.c:626   nf_hook include/linux/netfilter.h:269 [inline]   NF_HOOK include/linux/netfilter.h:312 [inline]   ipv6_rcv+0x29b/0x390 net/ipv6/ip6_input.c:310   __netif_receive_skb_one_core ---truncated---(CVE-2024-47685)\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:  RDMA/rtrs-clt: Reset cid to con_num - 1 to stay in bounds  In the function init_conns(), after the create_con() and create_cm() for loop if something fails. In the cleanup for loop after the destroy tag, we access out of bound memory because cid is set to clt_path-\u0026gt;s.con_num.  This commits resets the cid to clt_path-\u0026gt;s.con_num - 1, to stay in bounds in the cleanup loop later.(CVE-2024-47695)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  drivers: media: dvb-frontends/rtl2832: fix an out-of-bounds write error  Ensure index in rtl2832_pid_filter does not exceed 31 to prevent out-of-bounds access.  dev-\u0026gt;filters is a 32-bit value, so set_bit and clear_bit functions should only operate on indices from 0 to 31. If index is 32, it will attempt to access a non-existent 33rd bit, leading to out-of-bounds access. Change the boundary check from index \u0026gt; 32 to index \u0026gt;= 32 to resolve this issue.  [hverkuil: added fixes tag, rtl2830_pid_filter -\u0026gt; rtl2832_pid_filter in logmsg](CVE-2024-47698)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  can: bcm: Clear bo-\u0026gt;bcm_proc_read after remove_proc_entry().  syzbot reported a warning in bcm_release(). [0]  The blamed change fixed another warning that is triggered when connect() is issued again for a socket whose connect()ed device has been unregistered.  However, if the socket is just close()d without the 2nd connect(), the remaining bo-\u0026gt;bcm_proc_read triggers unnecessary remove_proc_entry() in bcm_release().  Let\u0026apos;s clear bo-\u0026gt;bcm_proc_read after remove_proc_entry() in bcm_notify().  [0] name \u0026apos;4986\u0026apos; WARNING: CPU: 0 PID: 5234 at fs/proc/generic.c:711 remove_proc_entry+0x2e7/0x5d0 fs/proc/generic.c:711 Modules linked in: CPU: 0 UID: 0 PID: 5234 Comm: syz-executor606 Not tainted 6.11.0-rc5-syzkaller-00178-g5517ae241919 #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 08/06/2024 RIP: 0010:remove_proc_entry+0x2e7/0x5d0 fs/proc/generic.c:711 Code: ff eb 05 e8 cb 1e 5e ff 48 8b 5c 24 10 48 c7 c7 e0 f7 aa 8e e8 2a 38 8e 09 90 48 c7 c7 60 3a 1b 8c 48 89 de e8 da 42 20 ff 90 \u0026lt;0f\u0026gt; 0b 90 90 48 8b 44 24 18 48 c7 44 24 40 0e 36 e0 45 49 c7 04 07 RSP: 0018:ffffc9000345fa20 EFLAGS: 00010246 RAX: 2a2d0aee2eb64600 RBX: ffff888032f1f548 RCX: ffff888029431e00 RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000000000000 RBP: ffffc9000345fb08 R08: ffffffff8155b2f2 R09: 1ffff1101710519a R10: dffffc0000000000 R11: ffffed101710519b R12: ffff888011d38640 R13: 0000000000000004 R14: 0000000000000000 R15: dffffc0000000000 FS:  0000000000000000(0000) GS:ffff8880b8800000(0000) knlGS:0000000000000000 CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 00007fcfb52722f0 CR3: 000000000e734000 CR4: 00000000003506f0 DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400 Call Trace:  \u0026lt;TASK\u0026gt;  bcm_release+0x250/0x880 net/can/bcm.c:1578  __sock_release net/socket.c:659 [inline]  sock_close+0xbc/0x240 net/socket.c:1421  __fput+0x24a/0x8a0 fs/file_table.c:422  task_work_run+0x24f/0x310 kernel/task_work.c:228  exit_task_work include/linux/task_work.h:40 [inline]  do_exit+0xa2f/0x27f0 kernel/exit.c:882  do_group_exit+0x207/0x2c0 kernel/exit.c:1031  __do_sys_exit_group kernel/exit.c:1042 [inline]  __se_sys_exit_group kernel/exit.c:1040 [inline]  __x64_sys_exit_group+0x3f/0x40 kernel/exit.c:1040  x64_sys_call+0x2634/0x2640 arch/x86/include/generated/asm/syscalls_64.h:232  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:0x7fcfb51ee969 Code: Unable to access opcode bytes at 0x7fcfb51ee93f. RSP: 002b:00007ffce0109ca8 EFLAGS: 00000246 ORIG_RAX: 00000000000000e7 RAX: ffffffffffffffda RBX: 0000000000000001 RCX: 00007fcfb51ee969 RDX: 000000000000003c RSI: 00000000000000e7 RDI: 0000000000000001 RBP: 00007fcfb526f3b0 R08: ffffffffffffffb8 R09: 0000555500000000 R10: 0000555500000000 R11: 0000000000000246 R12: 00007fcfb526f3b0 R13: 0000000000000000 R14: 00007fcfb5271ee0 R15: 00007fcfb51bf160  \u0026lt;/TASK\u0026gt;(CVE-2024-47709)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  sock_map: Add a cond_resched() in sock_hash_free()  Several syzbot soft lockup reports all have in common sock_hash_free()  If a map with a large number of buckets is destroyed, we need to yield the cpu when needed.(CVE-2024-47710)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  drm/amd/display: Add null check for set_output_gamma in dcn30_set_output_transfer_func  This commit adds a null check for the set_output_gamma function pointer in the  dcn30_set_output_transfer_func function. Previously, set_output_gamma was being checked for nullity at line 386, but then it was being dereferenced without any nullity check at line 401. This could potentially lead to a null pointer dereference error if set_output_gamma is indeed null.  To fix this, we now ensure that set_output_gamma is not null before dereferencing it. We do this by adding a nullity check for set_output_gamma before the call to set_output_gamma at line 401. If set_output_gamma is null, we log an error message and do not call the function.  This fix prevents a potential null pointer dereference error.  drivers/gpu/drm/amd/amdgpu/../display/dc/hwss/dcn30/dcn30_hwseq.c:401 dcn30_set_output_transfer_func() error: we previously assumed \u0026apos;mpc-\u0026gt;funcs-\u0026gt;set_output_gamma\u0026apos; could be null (see line 386)  drivers/gpu/drm/amd/amdgpu/../display/dc/hwss/dcn30/dcn30_hwseq.c     373 bool dcn30_set_output_transfer_func(struct dc *dc,     374                                 struct pipe_ctx *pipe_ctx,     375                                 const struct dc_stream_state *stream)     376 {     377         int mpcc_id = pipe_ctx-\u0026gt;plane_res.hubp-\u0026gt;inst;     378         struct mpc *mpc = pipe_ctx-\u0026gt;stream_res.opp-\u0026gt;ctx-\u0026gt;dc-\u0026gt;res_pool-\u0026gt;mpc;     379         const struct pwl_params *params = NULL;     380         bool ret = false;     381     382         /* program OGAM or 3DLUT only for the top pipe*/     383         if (pipe_ctx-\u0026gt;top_pipe == NULL) {     384                 /*program rmu shaper and 3dlut in MPC*/     385                 ret = dcn30_set_mpc_shaper_3dlut(pipe_ctx, stream);     386                 if (ret == false \u0026amp;\u0026amp; mpc-\u0026gt;funcs-\u0026gt;set_output_gamma) {                                             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^ If this is NULL      387                         if (stream-\u0026gt;out_transfer_func.type == TF_TYPE_HWPWL)     388                                 params = \u0026amp;stream-\u0026gt;out_transfer_func.pwl;     389                         else if (pipe_ctx-\u0026gt;stream-\u0026gt;out_transfer_func.type ==     390                                         TF_TYPE_DISTRIBUTED_POINTS \u0026amp;\u0026amp;     391                                         cm3_helper_translate_curve_to_hw_format(     392                                         \u0026amp;stream-\u0026gt;out_transfer_func,     393                                         \u0026amp;mpc-\u0026gt;blender_params, false))     394                                 params = \u0026amp;mpc-\u0026gt;blender_params;     395                          /* there are no ROM LUTs in OUTGAM */     396                         if (stream-\u0026gt;out_transfer_func.type == TF_TYPE_PREDEFINED)     397                                 BREAK_TO_DEBUGGER();     398                 }     399         }     400 --\u0026gt; 401         mpc-\u0026gt;funcs-\u0026gt;set_output_gamma(mpc, mpcc_id, params);                 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^ Then it will crash      402         return ret;     403 }(CVE-2024-47720)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  RDMA/hns: Fix spin_unlock_irqrestore() called with IRQs enabled  Fix missuse of spin_lock_irq()/spin_unlock_irq() when spin_lock_irqsave()/spin_lock_irqrestore() was hold.  This was discovered through the lock debugging, and the corresponding log is as follows:  raw_local_irq_restore() called with IRQs enabled WARNING: CPU: 96 PID: 2074 at kernel/locking/irqflag-debug.c:10 warn_bogus_irq_restore+0x30/0x40 ... Call trace:  warn_bogus_irq_restore+0x30/0x40  _raw_spin_unlock_irqrestore+0x84/0xc8  add_qp_to_list+0x11c/0x148 [hns_roce_hw_v2]  hns_roce_create_qp_common.constprop.0+0x240/0x780 [hns_roce_hw_v2]  hns_roce_create_qp+0x98/0x160 [hns_roce_hw_v2]  create_qp+0x138/0x258  ib_create_qp_kernel+0x50/0xe8  create_mad_qp+0xa8/0x128  ib_mad_port_open+0x218/0x448  ib_mad_init_device+0x70/0x1f8  add_client_context+0xfc/0x220  enable_device_and_get+0xd0/0x140  ib_register_device.part.0+0xf4/0x1c8  ib_register_device+0x34/0x50  hns_roce_register_device+0x174/0x3d0 [hns_roce_hw_v2]  hns_roce_init+0xfc/0x2c0 [hns_roce_hw_v2]  __hns_roce_hw_v2_init_instance+0x7c/0x1d0 [hns_roce_hw_v2]  hns_roce_hw_v2_init_instance+0x9c/0x180 [hns_roce_hw_v2](CVE-2024-47735)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  nfsd: call cache_put if xdr_reserve_space returns NULL  If not enough buffer space available, but idmap_lookup has triggered lookup_fn which calls cache_get and returns successfully. Then we missed to call cache_put here which pairs with cache_get.  Reviwed-by: Jeff Layton \u0026lt;jlayton@kernel.org\u0026gt;(CVE-2024-47737)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  nilfs2: fix potential oob read in nilfs_btree_check_delete()  The function nilfs_btree_check_delete(), which checks whether degeneration to direct mapping occurs before deleting a b-tree entry, causes memory access outside the block buffer when retrieving the maximum key if the root node has no entries.  This does not usually happen because b-tree mappings with 0 child nodes are never created by mkfs.nilfs2 or nilfs2 itself.  However, it can happen if the b-tree root node read from a device is configured that way, so fix this potential issue by adding a check for that case.(CVE-2024-47757)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  tracing/timerlat: Fix a race during cpuhp processing  There is another found exception that the \u0026quot;timerlat/1\u0026quot; thread was scheduled on CPU0, and lead to timer corruption finally:  ``` ODEBUG: init active (active state 0) object: ffff888237c2e108 object type: hrtimer hint: timerlat_irq+0x0/0x220 WARNING: CPU: 0 PID: 426 at lib/debugobjects.c:518 debug_print_object+0x7d/0xb0 Modules linked in: CPU: 0 UID: 0 PID: 426 Comm: timerlat/1 Not tainted 6.11.0-rc7+ #45 Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.13.0-1ubuntu1.1 04/01/2014 RIP: 0010:debug_print_object+0x7d/0xb0 ... Call Trace:  \u0026lt;TASK\u0026gt;  ? __warn+0x7c/0x110  ? debug_print_object+0x7d/0xb0  ? report_bug+0xf1/0x1d0  ? prb_read_valid+0x17/0x20  ? handle_bug+0x3f/0x70  ? exc_invalid_op+0x13/0x60  ? asm_exc_invalid_op+0x16/0x20  ? debug_print_object+0x7d/0xb0  ? debug_print_object+0x7d/0xb0  ? __pfx_timerlat_irq+0x10/0x10  __debug_object_init+0x110/0x150  hrtimer_init+0x1d/0x60  timerlat_main+0xab/0x2d0  ? __pfx_timerlat_main+0x10/0x10  kthread+0xb7/0xe0  ? __pfx_kthread+0x10/0x10  ret_from_fork+0x2d/0x40  ? __pfx_kthread+0x10/0x10  ret_from_fork_asm+0x1a/0x30  \u0026lt;/TASK\u0026gt; ```  After tracing the scheduling event, it was discovered that the migration of the \u0026quot;timerlat/1\u0026quot; thread was performed during thread creation. Further analysis confirmed that it is because the CPU online processing for osnoise is implemented through workers, which is asynchronous with the offline processing. When the worker was scheduled to create a thread, the CPU may has already been removed from the cpu_online_mask during the offline process, resulting in the inability to select the right CPU:  T1                       | T2 [CPUHP_ONLINE]           | cpu_device_down() osnoise_hotplug_workfn() |                          |     cpus_write_lock()                          |     takedown_cpu(1)                          |     cpus_write_unlock() [CPUHP_OFFLINE]          |     cpus_read_lock()     |     start_kthread(1)     |     cpus_read_unlock()   |  To fix this, skip online processing if the CPU is already offline.(CVE-2024-49866)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  btrfs: wait for fixup workers before stopping cleaner kthread during umount  During unmount, at close_ctree(), we have the following steps in this order:  1) Park the cleaner kthread - this doesn\u0026apos;t destroy the kthread, it basically    halts its execution (wake ups against it work but do nothing);  2) We stop the cleaner kthread - this results in freeing the respective    struct task_struct;  3) We call btrfs_stop_all_workers() which waits for any jobs running in all    the work queues and then free the work queues.  Syzbot reported a case where a fixup worker resulted in a crash when doing a delayed iput on its inode while attempting to wake up the cleaner at btrfs_add_delayed_iput(), because the task_struct of the cleaner kthread was already freed. This can happen during unmount because we don\u0026apos;t wait for any fixup workers still running before we call kthread_stop() against the cleaner kthread, which stops and free all its resources.  Fix this by waiting for any fixup workers at close_ctree() before we call kthread_stop() against the cleaner and run pending delayed iputs.  The stack traces reported by syzbot were the following:    BUG: KASAN: slab-use-after-free in __lock_acquire+0x77/0x2050 kernel/locking/lockdep.c:5065   Read of size 8 at addr ffff8880272a8a18 by task kworker/u8:3/52    CPU: 1 UID: 0 PID: 52 Comm: kworker/u8:3 Not tainted 6.12.0-rc1-syzkaller #0   Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 09/13/2024   Workqueue: btrfs-fixup btrfs_work_helper   Call Trace:    \u0026lt;TASK\u0026gt;    __dump_stack lib/dump_stack.c:94 [inline]    dump_stack_lvl+0x241/0x360 lib/dump_stack.c:120    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    __lock_acquire+0x77/0x2050 kernel/locking/lockdep.c:5065    lock_acquire+0x1ed/0x550 kernel/locking/lockdep.c:5825    __raw_spin_lock_irqsave include/linux/spinlock_api_smp.h:110 [inline]    _raw_spin_lock_irqsave+0xd5/0x120 kernel/locking/spinlock.c:162    class_raw_spinlock_irqsave_constructor include/linux/spinlock.h:551 [inline]    try_to_wake_up+0xb0/0x1480 kernel/sched/core.c:4154    btrfs_writepage_fixup_worker+0xc16/0xdf0 fs/btrfs/inode.c:2842    btrfs_work_helper+0x390/0xc50 fs/btrfs/async-thread.c:314    process_one_work kernel/workqueue.c:3229 [inline]    process_scheduled_works+0xa63/0x1850 kernel/workqueue.c:3310    worker_thread+0x870/0xd30 kernel/workqueue.c:3391    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;    Allocated by task 2:    kasan_save_stack mm/kasan/common.c:47 [inline]    kasan_save_track+0x3f/0x80 mm/kasan/common.c:68    unpoison_slab_object mm/kasan/common.c:319 [inline]    __kasan_slab_alloc+0x66/0x80 mm/kasan/common.c:345    kasan_slab_alloc include/linux/kasan.h:247 [inline]    slab_post_alloc_hook mm/slub.c:4086 [inline]    slab_alloc_node mm/slub.c:4135 [inline]    kmem_cache_alloc_node_noprof+0x16b/0x320 mm/slub.c:4187    alloc_task_struct_node kernel/fork.c:180 [inline]    dup_task_struct+0x57/0x8c0 kernel/fork.c:1107    copy_process+0x5d1/0x3d50 kernel/fork.c:2206    kernel_clone+0x223/0x880 kernel/fork.c:2787    kernel_thread+0x1bc/0x240 kernel/fork.c:2849    create_kthread kernel/kthread.c:412 [inline]    kthreadd+0x60d/0x810 kernel/kthread.c:765    ret_from_fork+0x4b/0x80 arch/x86/kernel/process.c:147    ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:244    Freed by task 61:    kasan_save_stack mm/kasan/common.c:47 [inline]    kasan_save_track+0x3f/0x80 mm/kasan/common.c:68    kasan_save_free_info+0x40/0x50 mm/kasan/generic.c:579    poison_slab_object mm/kasan/common.c:247 [inline]    __kasan_slab_free+0x59/0x70 mm/kasan/common.c:264    kasan_slab_free include/linux/kasan.h:230 [inline]    slab_free_h ---truncated---(CVE-2024-49867)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  btrfs: fix a NULL pointer dereference when failed to start a new trasacntion  [BUG] Syzbot reported a NULL pointer dereference with the following crash:    FAULT_INJECTION: forcing a failure.    start_transaction+0x830/0x1670 fs/btrfs/transaction.c:676    prepare_to_relocate+0x31f/0x4c0 fs/btrfs/relocation.c:3642    relocate_block_group+0x169/0xd20 fs/btrfs/relocation.c:3678   ...   BTRFS info (device loop0): balance: ended with status: -12   Oops: general protection fault, probably for non-canonical address 0xdffffc00000000cc: 0000 [#1] PREEMPT SMP KASAN NOPTI   KASAN: null-ptr-deref in range [0x0000000000000660-0x0000000000000667]   RIP: 0010:btrfs_update_reloc_root+0x362/0xa80 fs/btrfs/relocation.c:926   Call Trace:    \u0026lt;TASK\u0026gt;    commit_fs_roots+0x2ee/0x720 fs/btrfs/transaction.c:1496    btrfs_commit_transaction+0xfaf/0x3740 fs/btrfs/transaction.c:2430    del_balance_item fs/btrfs/volumes.c:3678 [inline]    reset_balance_state+0x25e/0x3c0 fs/btrfs/volumes.c:3742    btrfs_balance+0xead/0x10c0 fs/btrfs/volumes.c:4574    btrfs_ioctl_balance+0x493/0x7c0 fs/btrfs/ioctl.c:3673    vfs_ioctl fs/ioctl.c:51 [inline]    __do_sys_ioctl fs/ioctl.c:907 [inline]    __se_sys_ioctl+0xf9/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  [CAUSE] The allocation failure happens at the start_transaction() inside prepare_to_relocate(), and during the error handling we call unset_reloc_control(), which makes fs_info-\u0026gt;balance_ctl to be NULL.  Then we continue the error path cleanup in btrfs_balance() by calling reset_balance_state() which will call del_balance_item() to fully delete the balance item in the root tree.  However during the small window between set_reloc_contrl() and unset_reloc_control(), we can have a subvolume tree update and created a reloc_root for that subvolume.  Then we go into the final btrfs_commit_transaction() of del_balance_item(), and into btrfs_update_reloc_root() inside commit_fs_roots().  That function checks if fs_info-\u0026gt;reloc_ctl is in the merge_reloc_tree stage, but since fs_info-\u0026gt;reloc_ctl is NULL, it results a NULL pointer dereference.  [FIX] Just add extra check on fs_info-\u0026gt;reloc_ctl inside btrfs_update_reloc_root(), before checking fs_info-\u0026gt;reloc_ctl-\u0026gt;merge_reloc_tree.  That DEAD_RELOC_TREE handling is to prevent further modification to the reloc tree during merge stage, but since there is no reloc_ctl at all, we do not need to bother that.(CVE-2024-49868)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  nfsd: map the EBADMSG to nfserr_io to avoid warning  Ext4 will throw -EBADMSG through ext4_readdir when a checksum error occurs, resulting in the following WARNING.  Fix it by mapping EBADMSG to nfserr_io.  nfsd_buffered_readdir  iterate_dir // -EBADMSG -74   ext4_readdir // .iterate_shared    ext4_dx_readdir     ext4_htree_fill_tree      htree_dirblock_to_tree       ext4_read_dirblock        __ext4_read_dirblock         ext4_dirblock_csum_verify          warn_no_space_for_csum           __warn_no_space_for_csum         return ERR_PTR(-EFSBADCRC) // -EBADMSG -74  nfserrno // WARNING  [  161.115610] ------------[ cut here ]------------ [  161.116465] nfsd: non-standard errno: -74 [  161.117315] WARNING: CPU: 1 PID: 780 at fs/nfsd/nfsproc.c:878 nfserrno+0x9d/0xd0 [  161.118596] Modules linked in: [  161.119243] CPU: 1 PID: 780 Comm: nfsd Not tainted 5.10.0-00014-g79679361fd5d #138 [  161.120684] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS rel-1.14.0-0-g155821a1990b-prebuilt.qe mu.org 04/01/2014 [  161.123601] RIP: 0010:nfserrno+0x9d/0xd0 [  161.124676] Code: 0f 87 da 30 dd 00 83 e3 01 b8 00 00 00 05 75 d7 44 89 ee 48 c7 c7 c0 57 24 98 89 44 24 04 c6  05 ce 2b 61 03 01 e8 99 20 d8 00 \u0026lt;0f\u0026gt; 0b 8b 44 24 04 eb b5 4c 89 e6 48 c7 c7 a0 6d a4 99 e8 cc 15 33 [  161.127797] RSP: 0018:ffffc90000e2f9c0 EFLAGS: 00010286 [  161.128794] RAX: 0000000000000000 RBX: 0000000000000000 RCX: 0000000000000000 [  161.130089] RDX: 1ffff1103ee16f6d RSI: 0000000000000008 RDI: fffff520001c5f2a [  161.131379] RBP: 0000000000000022 R08: 0000000000000001 R09: ffff8881f70c1827 [  161.132664] R10: ffffed103ee18304 R11: 0000000000000001 R12: 0000000000000021 [  161.133949] R13: 00000000ffffffb6 R14: ffff8881317c0000 R15: ffffc90000e2fbd8 [  161.135244] FS:  0000000000000000(0000) GS:ffff8881f7080000(0000) knlGS:0000000000000000 [  161.136695] CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033 [  161.137761] CR2: 00007fcaad70b348 CR3: 0000000144256006 CR4: 0000000000770ee0 [  161.139041] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 [  161.140291] DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400 [  161.141519] PKRU: 55555554 [  161.142076] Call Trace: [  161.142575]  ? __warn+0x9b/0x140 [  161.143229]  ? nfserrno+0x9d/0xd0 [  161.143872]  ? report_bug+0x125/0x150 [  161.144595]  ? handle_bug+0x41/0x90 [  161.145284]  ? exc_invalid_op+0x14/0x70 [  161.146009]  ? asm_exc_invalid_op+0x12/0x20 [  161.146816]  ? nfserrno+0x9d/0xd0 [  161.147487]  nfsd_buffered_readdir+0x28b/0x2b0 [  161.148333]  ? nfsd4_encode_dirent_fattr+0x380/0x380 [  161.149258]  ? nfsd_buffered_filldir+0xf0/0xf0 [  161.150093]  ? wait_for_concurrent_writes+0x170/0x170 [  161.151004]  ? generic_file_llseek_size+0x48/0x160 [  161.151895]  nfsd_readdir+0x132/0x190 [  161.152606]  ? nfsd4_encode_dirent_fattr+0x380/0x380 [  161.153516]  ? nfsd_unlink+0x380/0x380 [  161.154256]  ? override_creds+0x45/0x60 [  161.155006]  nfsd4_encode_readdir+0x21a/0x3d0 [  161.155850]  ? nfsd4_encode_readlink+0x210/0x210 [  161.156731]  ? write_bytes_to_xdr_buf+0x97/0xe0 [  161.157598]  ? __write_bytes_to_xdr_buf+0xd0/0xd0 [  161.158494]  ? lock_downgrade+0x90/0x90 [  161.159232]  ? nfs4svc_decode_voidarg+0x10/0x10 [  161.160092]  nfsd4_encode_operation+0x15a/0x440 [  161.160959]  nfsd4_proc_compound+0x718/0xe90 [  161.161818]  nfsd_dispatch+0x18e/0x2c0 [  161.162586]  svc_process_common+0x786/0xc50 [  161.163403]  ? nfsd_svc+0x380/0x380 [  161.164137]  ? svc_printk+0x160/0x160 [  161.164846]  ? svc_xprt_do_enqueue.part.0+0x365/0x380 [  161.165808]  ? nfsd_svc+0x380/0x380 [  161.166523]  ? rcu_is_watching+0x23/0x40 [  161.167309]  svc_process+0x1a5/0x200 [  161.168019]  nfsd+0x1f5/0x380 [  161.168663]  ? nfsd_shutdown_threads+0x260/0x260 [  161.169554]  kthread+0x1c4/0x210 [  161.170224]  ? kthread_insert_work_sanity_check+0x80/0x80 [  161.171246]  ret_from_fork+0x1f/0x30(CVE-2024-49875)\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: Fix index out of bounds in degamma hardware format translation  Fixes index out of bounds issue in `cm_helper_translate_curve_to_degamma_hw_format` function. The issue could occur when the index \u0026apos;i\u0026apos; exceeds the number of transfer function points (TRANSFER_FUNC_POINTS).  The fix adds a check to ensure \u0026apos;i\u0026apos; is within bounds before accessing the transfer function points. If \u0026apos;i\u0026apos; is out of bounds the function returns false to indicate an error.  Reported by smatch: drivers/gpu/drm/amd/amdgpu/../display/dc/dcn10/dcn10_cm_common.c:594 cm_helper_translate_curve_to_degamma_hw_format() error: buffer overflow \u0026apos;output_tf-\u0026gt;tf_pts.red\u0026apos; 1025 \u0026lt;= s32max drivers/gpu/drm/amd/amdgpu/../display/dc/dcn10/dcn10_cm_common.c:595 cm_helper_translate_curve_to_degamma_hw_format() error: buffer overflow \u0026apos;output_tf-\u0026gt;tf_pts.green\u0026apos; 1025 \u0026lt;= s32max drivers/gpu/drm/amd/amdgpu/../display/dc/dcn10/dcn10_cm_common.c:596 cm_helper_translate_curve_to_degamma_hw_format() error: buffer overflow \u0026apos;output_tf-\u0026gt;tf_pts.blue\u0026apos; 1025 \u0026lt;= s32max(CVE-2024-49894)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  drm/amd/display: Fix index out of bounds in DCN30 degamma hardware format translation  This commit addresses a potential index out of bounds issue in the `cm3_helper_translate_curve_to_degamma_hw_format` function in the DCN30 color  management module. The issue could occur when the index \u0026apos;i\u0026apos; exceeds the  number of transfer function points (TRANSFER_FUNC_POINTS).  The fix adds a check to ensure \u0026apos;i\u0026apos; is within bounds before accessing the transfer function points. If \u0026apos;i\u0026apos; is out of bounds, the function returns false to indicate an error.  Reported by smatch: drivers/gpu/drm/amd/amdgpu/../display/dc/dcn30/dcn30_cm_common.c:338 cm3_helper_translate_curve_to_degamma_hw_format() error: buffer overflow \u0026apos;output_tf-\u0026gt;tf_pts.red\u0026apos; 1025 \u0026lt;= s32max drivers/gpu/drm/amd/amdgpu/../display/dc/dcn30/dcn30_cm_common.c:339 cm3_helper_translate_curve_to_degamma_hw_format() error: buffer overflow \u0026apos;output_tf-\u0026gt;tf_pts.green\u0026apos; 1025 \u0026lt;= s32max drivers/gpu/drm/amd/amdgpu/../display/dc/dcn30/dcn30_cm_common.c:340 cm3_helper_translate_curve_to_degamma_hw_format() error: buffer overflow \u0026apos;output_tf-\u0026gt;tf_pts.blue\u0026apos; 1025 \u0026lt;= s32max(CVE-2024-49895)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  jfs: Fix uninit-value access of new_ea in ea_buffer  syzbot reports that lzo1x_1_do_compress is using uninit-value:  ===================================================== BUG: KMSAN: uninit-value in lzo1x_1_do_compress+0x19f9/0x2510 lib/lzo/lzo1x_compress.c:178  ...  Uninit was stored to memory at:  ea_put fs/jfs/xattr.c:639 [inline]  ...  Local variable ea_buf created at:  __jfs_setxattr+0x5d/0x1ae0 fs/jfs/xattr.c:662  __jfs_xattr_set+0xe6/0x1f0 fs/jfs/xattr.c:934  =====================================================  The reason is ea_buf-\u0026gt;new_ea is not initialized properly.  Fix this by using memset to empty its content at the beginning in ea_get().(CVE-2024-49900)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  jfs: check if leafidx greater than num leaves per dmap tree  syzbot report a out of bounds in dbSplit, it because dmt_leafidx greater than num leaves per dmap tree, add a checking for dmt_leafidx in dbFindLeaf.  Shaggy: Modified sanity check to apply to control pages as well as leaf pages.(CVE-2024-49902)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  jfs: Fix uaf in dbFreeBits  [syzbot reported] ================================================================== BUG: KASAN: slab-use-after-free in __mutex_lock_common kernel/locking/mutex.c:587 [inline] BUG: KASAN: slab-use-after-free in __mutex_lock+0xfe/0xd70 kernel/locking/mutex.c:752 Read of size 8 at addr ffff8880229254b0 by task syz-executor357/5216  CPU: 0 UID: 0 PID: 5216 Comm: syz-executor357 Not tainted 6.11.0-rc3-syzkaller-00156-gd7a5aa4b3c00 #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 06/27/2024 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  __mutex_lock_common kernel/locking/mutex.c:587 [inline]  __mutex_lock+0xfe/0xd70 kernel/locking/mutex.c:752  dbFreeBits+0x7ea/0xd90 fs/jfs/jfs_dmap.c:2390  dbFreeDmap fs/jfs/jfs_dmap.c:2089 [inline]  dbFree+0x35b/0x680 fs/jfs/jfs_dmap.c:409  dbDiscardAG+0x8a9/0xa20 fs/jfs/jfs_dmap.c:1650  jfs_ioc_trim+0x433/0x670 fs/jfs/jfs_discard.c:100  jfs_ioctl+0x2d0/0x3e0 fs/jfs/ioctl.c:131  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  Freed by task 5218:  kasan_save_stack mm/kasan/common.c:47 [inline]  kasan_save_track+0x3f/0x80 mm/kasan/common.c:68  kasan_save_free_info+0x40/0x50 mm/kasan/generic.c:579  poison_slab_object+0xe0/0x150 mm/kasan/common.c:240  __kasan_slab_free+0x37/0x60 mm/kasan/common.c:256  kasan_slab_free include/linux/kasan.h:184 [inline]  slab_free_hook mm/slub.c:2252 [inline]  slab_free mm/slub.c:4473 [inline]  kfree+0x149/0x360 mm/slub.c:4594  dbUnmount+0x11d/0x190 fs/jfs/jfs_dmap.c:278  jfs_mount_rw+0x4ac/0x6a0 fs/jfs/jfs_mount.c:247  jfs_remount+0x3d1/0x6b0 fs/jfs/super.c:454  reconfigure_super+0x445/0x880 fs/super.c:1083  vfs_cmd_reconfigure fs/fsopen.c:263 [inline]  vfs_fsconfig_locked fs/fsopen.c:292 [inline]  __do_sys_fsconfig fs/fsopen.c:473 [inline]  __se_sys_fsconfig+0xb6e/0xf80 fs/fsopen.c:345  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  [Analysis] There are two paths (dbUnmount and jfs_ioc_trim) that generate race condition when accessing bmap, which leads to the occurrence of uaf.  Use the lock s_umount to synchronize them, in order to avoid uaf caused by race condition.(CVE-2024-49903)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  drm/amd/display: Add NULL check for function pointer in dcn20_set_output_transfer_func  This commit adds a null check for the set_output_gamma function pointer in the dcn20_set_output_transfer_func function. Previously, set_output_gamma was being checked for null at line 1030, but then it was being dereferenced without any null check at line 1048. This could potentially lead to a null pointer dereference error 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 at line 1048.(CVE-2024-49911)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  x86/ioapic: Handle allocation failures gracefully  Breno observed panics when using failslab under certain conditions during runtime:     can not alloc irq_pin_list (-1,0,20)    Kernel panic - not syncing: IO-APIC: failed to add irq-pin. Can not proceed     panic+0x4e9/0x590    mp_irqdomain_alloc+0x9ab/0xa80    irq_domain_alloc_irqs_locked+0x25d/0x8d0    __irq_domain_alloc_irqs+0x80/0x110    mp_map_pin_to_irq+0x645/0x890    acpi_register_gsi_ioapic+0xe6/0x150    hpet_open+0x313/0x480  That\u0026apos;s a pointless panic which is a leftover of the historic IO/APIC code which panic\u0026apos;ed during early boot when the interrupt allocation failed.  The only place which might justify panic is the PIT/HPET timer_check() code which tries to figure out whether the timer interrupt is delivered through the IO/APIC. But that code does not require to handle interrupt allocation failures. If the interrupt cannot be allocated then timer delivery fails and it either panics due to that or falls back to legacy mode.  Cure this by removing the panic wrapper around __add_pin_to_irq_node() and making mp_irqdomain_alloc() aware of the failure condition and handle it as any other failure in this function gracefully.(CVE-2024-49927)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  jbd2: stop waiting for space when jbd2_cleanup_journal_tail() returns error  In __jbd2_log_wait_for_space(), we might call jbd2_cleanup_journal_tail() to recover some journal space. But if an error occurs while executing jbd2_cleanup_journal_tail() (e.g., an EIO), we don\u0026apos;t stop waiting for free space right away, we try other branches, and if j_committing_transaction is NULL (i.e., the tid is 0), we will get the following complain:  ============================================ JBD2: I/O error when updating journal superblock for sdd-8. __jbd2_log_wait_for_space: needed 256 blocks and only had 217 space available __jbd2_log_wait_for_space: no way to get more journal space in sdd-8 ------------[ cut here ]------------ WARNING: CPU: 2 PID: 139804 at fs/jbd2/checkpoint.c:109 __jbd2_log_wait_for_space+0x251/0x2e0 Modules linked in: CPU: 2 PID: 139804 Comm: kworker/u8:3 Not tainted 6.6.0+ #1 RIP: 0010:__jbd2_log_wait_for_space+0x251/0x2e0 Call Trace:  \u0026lt;TASK\u0026gt;  add_transaction_credits+0x5d1/0x5e0  start_this_handle+0x1ef/0x6a0  jbd2__journal_start+0x18b/0x340  ext4_dirty_inode+0x5d/0xb0  __mark_inode_dirty+0xe4/0x5d0  generic_update_time+0x60/0x70 [...] ============================================  So only if jbd2_cleanup_journal_tail() returns 1, i.e., there is nothing to clean up at the moment, continue to try to reclaim free space in other ways.  Note that this fix relies on commit 6f6a6fda2945 (\u0026quot;jbd2: fix ocfs2 corrupt when updating journal superblock fails\u0026quot;) to make jbd2_cleanup_journal_tail return the correct error code.(CVE-2024-49959)\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:  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:  drm/amd/display: Fix index out of bounds in DCN30 color transformation  This commit addresses a potential index out of bounds issue in the `cm3_helper_translate_curve_to_hw_format` function in the DCN30 color management module. The issue could occur when the index \u0026apos;i\u0026apos; exceeds the number of transfer function points (TRANSFER_FUNC_POINTS).  The fix adds a check to ensure \u0026apos;i\u0026apos; is within bounds before accessing the transfer function points. If \u0026apos;i\u0026apos; is out of bounds, the function returns false to indicate an error.  drivers/gpu/drm/amd/amdgpu/../display/dc/dcn30/dcn30_cm_common.c:180 cm3_helper_translate_curve_to_hw_format() error: buffer overflow \u0026apos;output_tf-\u0026gt;tf_pts.red\u0026apos; 1025 \u0026lt;= s32max drivers/gpu/drm/amd/amdgpu/../display/dc/dcn30/dcn30_cm_common.c:181 cm3_helper_translate_curve_to_hw_format() error: buffer overflow \u0026apos;output_tf-\u0026gt;tf_pts.green\u0026apos; 1025 \u0026lt;= s32max drivers/gpu/drm/amd/amdgpu/../display/dc/dcn30/dcn30_cm_common.c:182 cm3_helper_translate_curve_to_hw_format() error: buffer overflow \u0026apos;output_tf-\u0026gt;tf_pts.blue\u0026apos; 1025 \u0026lt;= s32max(CVE-2024-49969)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  NFSD: Limit the number of concurrent async COPY operations  Nothing appears to limit the number of concurrent async COPY operations that clients can start. In addition, AFAICT each async COPY can copy an unlimited number of 4MB chunks, so can run for a long time. Thus IMO async COPY can become a DoS vector.  Add a restriction mechanism that bounds the number of concurrent background COPY operations. Start simple and try to be fair -- this patch implements a per-namespace limit.  An async COPY request that occurs while this limit is exceeded gets NFS4ERR_DELAY. The requesting client can choose to send the request again after a delay or fall back to a traditional read/write style copy.  If there is need to make the mechanism more sophisticated, we can visit that in future patches.(CVE-2024-49974)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  i2c: stm32f7: Do not prepare/unprepare clock during runtime suspend/resume  In case there is any sort of clock controller attached to this I2C bus controller, for example Versaclock or even an AIC32x4 I2C codec, then an I2C transfer triggered from the clock controller clk_ops .prepare callback may trigger a deadlock on drivers/clk/clk.c prepare_lock mutex.  This is because the clock controller first grabs the prepare_lock mutex and then performs the prepare operation, including its I2C access. The I2C access resumes this I2C bus controller via .runtime_resume callback, which calls clk_prepare_enable(), which attempts to grab the prepare_lock mutex again and deadlocks.  Since the clock are already prepared since probe() and unprepared in remove(), use simple clk_enable()/clk_disable() calls to enable and disable the clock on runtime suspend and resume, to avoid hitting the prepare_lock mutex.(CVE-2024-49985)\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:  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:  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:  drm/amd/display: Check null pointer before dereferencing se  [WHAT \u0026amp; HOW] se is null checked previously in the same function, indicating it might be null; therefore, it must be checked when used again.  This fixes 1 FORWARD_NULL issue reported by Coverity.(CVE-2024-50049)","status":"published","published":"2024-11-01T11:07:47Z","modified":"2026-08-18T01:17:36.529649285Z","cvss":[{"version":"3.1","score":9.1,"vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:H","level":"critical"}],"updated_at":"2026-11-02T15:52:41.595342Z"},{"id":"OESA-2024-2322","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\niommu/vt-d: Fix double list_add when enabling VMD in scalable mode\r\n\r\nWhen enabling VMD and IOMMU scalable mode, the following kernel panic\ncall trace/kernel log is shown in Eagle Stream platform (Sapphire Rapids\nCPU) during booting:\r\n\r\npci 0000:59:00.5: Adding to iommu group 42\n...\nvmd 0000:59:00.5: PCI host bridge to bus 10000:80\npci 10000:80:01.0: [8086:352a] type 01 class 0x060400\npci 10000:80:01.0: reg 0x10: [mem 0x00000000-0x0001ffff 64bit]\npci 10000:80:01.0: enabling Extended Tags\npci 10000:80:01.0: PME# supported from D0 D3hot D3cold\npci 10000:80:01.0: DMAR: Setup RID2PASID failed\npci 10000:80:01.0: Failed to add to iommu group 42: -16\npci 10000:80:03.0: [8086:352b] type 01 class 0x060400\npci 10000:80:03.0: reg 0x10: [mem 0x00000000-0x0001ffff 64bit]\npci 10000:80:03.0: enabling Extended Tags\npci 10000:80:03.0: PME# supported from D0 D3hot D3cold\n------------[ cut here ]------------\nkernel BUG at lib/list_debug.c:29!\ninvalid opcode: 0000 [#1] PREEMPT SMP NOPTI\nCPU: 0 PID: 7 Comm: kworker/0:1 Not tainted 5.17.0-rc3+ #7\nHardware name: Lenovo ThinkSystem SR650V3/SB27A86647, BIOS ESE101Y-1.00 01/13/2022\nWorkqueue: events work_for_cpu_fn\nRIP: 0010:__list_add_valid.cold+0x26/0x3f\nCode: 9a 4a ab ff 4c 89 c1 48 c7 c7 40 0c d9 9e e8 b9 b1 fe ff 0f\n      0b 48 89 f2 4c 89 c1 48 89 fe 48 c7 c7 f0 0c d9 9e e8 a2 b1\n      fe ff \u0026lt;0f\u0026gt; 0b 48 89 d1 4c 89 c6 4c 89 ca 48 c7 c7 98 0c d9\n      9e e8 8b b1 fe\nRSP: 0000:ff5ad434865b3a40 EFLAGS: 00010246\nRAX: 0000000000000058 RBX: ff4d61160b74b880 RCX: ff4d61255e1fffa8\nRDX: 0000000000000000 RSI: 00000000fffeffff RDI: ffffffff9fd34f20\nRBP: ff4d611d8e245c00 R08: 0000000000000000 R09: ff5ad434865b3888\nR10: ff5ad434865b3880 R11: ff4d61257fdc6fe8 R12: ff4d61160b74b8a0\nR13: ff4d61160b74b8a0 R14: ff4d611d8e245c10 R15: ff4d611d8001ba70\nFS:  0000000000000000(0000) GS:ff4d611d5ea00000(0000) knlGS:0000000000000000\nCS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033\nCR2: ff4d611fa1401000 CR3: 0000000aa0210001 CR4: 0000000000771ef0\nDR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000\nDR3: 0000000000000000 DR6: 00000000fffe07f0 DR7: 0000000000000400\nPKRU: 55555554\nCall Trace:\n \u0026lt;TASK\u0026gt;\n intel_pasid_alloc_table+0x9c/0x1d0\n dmar_insert_one_dev_info+0x423/0x540\n ? device_to_iommu+0x12d/0x2f0\n intel_iommu_attach_device+0x116/0x290\n __iommu_attach_device+0x1a/0x90\n iommu_group_add_device+0x190/0x2c0\n __iommu_probe_device+0x13e/0x250\n iommu_probe_device+0x24/0x150\n iommu_bus_notifier+0x69/0x90\n blocking_notifier_call_chain+0x5a/0x80\n device_add+0x3db/0x7b0\n ? arch_memremap_can_ram_remap+0x19/0x50\n ? memremap+0x75/0x140\n pci_device_add+0x193/0x1d0\n pci_scan_single_device+0xb9/0xf0\n pci_scan_slot+0x4c/0x110\n pci_scan_child_bus_extend+0x3a/0x290\n vmd_enable_domain.constprop.0+0x63e/0x820\n vmd_probe+0x163/0x190\n local_pci_probe+0x42/0x80\n work_for_cpu_fn+0x13/0x20\n process_one_work+0x1e2/0x3b0\n worker_thread+0x1c4/0x3a0\n ? rescuer_thread+0x370/0x370\n kthread+0xc7/0xf0\n ? kthread_complete_and_exit+0x20/0x20\n ret_from_fork+0x1f/0x30\n \u0026lt;/TASK\u0026gt;\nModules linked in:\n---[ end trace 0000000000000000 ]---\n...\nKernel panic - not syncing: Fatal exception\nKernel Offset: 0x1ca00000 from 0xffffffff81000000 (relocation range: 0xffffffff80000000-0xffffffffbfffffff)\n---[ end Kernel panic - not syncing: Fatal exception ]---\r\n\r\nThe following \u0026apos;lspci\u0026apos; output shows devices \u0026apos;10000:80:*\u0026apos; are subdevices of\nthe VMD device 0000:59:00.5:\r\n\r\n  $ lspci\n  ...\n  0000:59:00.5 RAID bus controller: Intel Corporation Volume Management Device NVMe RAID Controller (rev 20)\n  ...\n  10000:80:01.0 PCI bridge: Intel Corporation Device 352a (rev 03)\n  10000:80:03.0 PCI bridge: Intel Corporation Device 352b (rev 03)\n  10000:80:05.0 PCI bridge: Intel Corporation Device 352c (rev 03)\n  10000:80:07.0 PCI bridge: Intel Corporation Device 352d (rev 03)\n  10000:81:00.0 Non-Volatile memory controller: Intel Corporation NVMe Datacenter SSD [3DNAND, Beta Rock Controller]\n  10000:82:00\n---truncated---(CVE-2022-48916)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  PCI: mt7621: Add sentinel to quirks table  Current driver is missing a sentinel in the struct soc_device_attribute array, which causes an oops when assessed by the soc_device_match(mt7621_pcie_quirks_match) call.  This was only exposed once the CONFIG_SOC_MT7621 mt7621 soc_dev_attr was fixed to register the SOC as a device, in:  commit 7c18b64bba3b (\u0026quot;mips: ralink: mt7621: do not use kzalloc too early\u0026quot;)  Fix it by adding the required sentinel.(CVE-2022-48952)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  memcg: fix possible use-after-free in memcg_write_event_control()  memcg_write_event_control() accesses the dentry-\u0026gt;d_name of the specified control fd to route the write call.  As a cgroup interface file can\u0026apos;t be renamed, it\u0026apos;s safe to access d_name as long as the specified file is a regular cgroup file.  Also, as these cgroup interface files can\u0026apos;t be removed before the directory, it\u0026apos;s safe to access the parent too.  Prior to 347c4a874710 (\u0026quot;memcg: remove cgroup_event-\u0026gt;cft\u0026quot;), there was a call to __file_cft() which verified that the specified file is a regular cgroupfs file before further accesses.  The cftype pointer returned from __file_cft() was no longer necessary and the commit inadvertently dropped the file type check with it allowing any file to slip through.  With the invarients broken, the d_name and parent accesses can now race against renames and removals of arbitrary files and cause use-after-free\u0026apos;s.  Fix the bug by resurrecting the file type check in __file_cft().  Now that cgroupfs is implemented through kernfs, checking the file operations needs to go through a layer of indirection.  Instead, let\u0026apos;s check the superblock and dentry type.(CVE-2022-48988)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  ntb: intel: Fix the NULL vs IS_ERR() bug for debugfs_create_dir()  The debugfs_create_dir() function returns error pointers. It never returns NULL. So use IS_ERR() to check it.(CVE-2023-52917)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  media: pci: cx23885: check cx23885_vdev_init() return  cx23885_vdev_init() can return a NULL pointer, but that pointer is used in the next line without a check.  Add a NULL pointer check and go to the error unwind if it is NULL.(CVE-2023-52918)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  nfc: nci: fix possible NULL pointer dereference in send_acknowledge()  Handle memory allocation failure from nci_skb_alloc() (calling alloc_skb()) to avoid possible NULL pointer dereference.(CVE-2023-52919)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nof: module: prevent NULL pointer dereference in vsnprintf()\r\n\r\nIn of_modalias(), we can get passed the str and len parameters which would\ncause a kernel oops in vsnprintf() since it only allows passing a NULL ptr\nwhen the length is also 0. Also, we need to filter out the negative values\nof the len parameter as these will result in a really huge buffer since\nsnprintf() takes size_t parameter while ours is ssize_t...\r\n\r\nFound by Linux Verification Center (linuxtesting.org) with the Svace static\nanalysis tool.(CVE-2024-35878)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\ndma: xilinx_dpdma: Fix locking\r\n\r\nThere are several places where either chan-\u0026gt;lock or chan-\u0026gt;vchan.lock was\nnot held. Add appropriate locking. This fixes lockdep warnings like\r\n\r\n[   31.077578] ------------[ cut here ]------------\n[   31.077831] WARNING: CPU: 2 PID: 40 at drivers/dma/xilinx/xilinx_dpdma.c:834 xilinx_dpdma_chan_queue_transfer+0x274/0x5e0\n[   31.077953] Modules linked in:\n[   31.078019] CPU: 2 PID: 40 Comm: kworker/u12:1 Not tainted 6.6.20+ #98\n[   31.078102] Hardware name: xlnx,zynqmp (DT)\n[   31.078169] Workqueue: events_unbound deferred_probe_work_func\n[   31.078272] pstate: 600000c5 (nZCv daIF -PAN -UAO -TCO -DIT -SSBS BTYPE=--)\n[   31.078377] pc : xilinx_dpdma_chan_queue_transfer+0x274/0x5e0\n[   31.078473] lr : xilinx_dpdma_chan_queue_transfer+0x270/0x5e0\n[   31.078550] sp : ffffffc083bb2e10\n[   31.078590] x29: ffffffc083bb2e10 x28: 0000000000000000 x27: ffffff880165a168\n[   31.078754] x26: ffffff880164e920 x25: ffffff880164eab8 x24: ffffff880164d480\n[   31.078920] x23: ffffff880165a148 x22: ffffff880164e988 x21: 0000000000000000\n[   31.079132] x20: ffffffc082aa3000 x19: ffffff880164e880 x18: 0000000000000000\n[   31.079295] x17: 0000000000000000 x16: 0000000000000000 x15: 0000000000000000\n[   31.079453] x14: 0000000000000000 x13: ffffff8802263dc0 x12: 0000000000000001\n[   31.079613] x11: 0001ffc083bb2e34 x10: 0001ff880164e98f x9 : 0001ffc082aa3def\n[   31.079824] x8 : 0001ffc082aa3dec x7 : 0000000000000000 x6 : 0000000000000516\n[   31.079982] x5 : ffffffc7f8d43000 x4 : ffffff88003c9c40 x3 : ffffffffffffffff\n[   31.080147] x2 : ffffffc7f8d43000 x1 : 00000000000000c0 x0 : 0000000000000000\n[   31.080307] Call trace:\n[   31.080340]  xilinx_dpdma_chan_queue_transfer+0x274/0x5e0\n[   31.080518]  xilinx_dpdma_issue_pending+0x11c/0x120\n[   31.080595]  zynqmp_disp_layer_update+0x180/0x3ac\n[   31.080712]  zynqmp_dpsub_plane_atomic_update+0x11c/0x21c\n[   31.080825]  drm_atomic_helper_commit_planes+0x20c/0x684\n[   31.080951]  drm_atomic_helper_commit_tail+0x5c/0xb0\n[   31.081139]  commit_tail+0x234/0x294\n[   31.081246]  drm_atomic_helper_commit+0x1f8/0x210\n[   31.081363]  drm_atomic_commit+0x100/0x140\n[   31.081477]  drm_client_modeset_commit_atomic+0x318/0x384\n[   31.081634]  drm_client_modeset_commit_locked+0x8c/0x24c\n[   31.081725]  drm_client_modeset_commit+0x34/0x5c\n[   31.081812]  __drm_fb_helper_restore_fbdev_mode_unlocked+0x104/0x168\n[   31.081899]  drm_fb_helper_set_par+0x50/0x70\n[   31.081971]  fbcon_init+0x538/0xc48\n[   31.082047]  visual_init+0x16c/0x23c\n[   31.082207]  do_bind_con_driver.isra.0+0x2d0/0x634\n[   31.082320]  do_take_over_console+0x24c/0x33c\n[   31.082429]  do_fbcon_takeover+0xbc/0x1b0\n[   31.082503]  fbcon_fb_registered+0x2d0/0x34c\n[   31.082663]  register_framebuffer+0x27c/0x38c\n[   31.082767]  __drm_fb_helper_initial_config_and_unlock+0x5c0/0x91c\n[   31.082939]  drm_fb_helper_initial_config+0x50/0x74\n[   31.083012]  drm_fbdev_dma_client_hotplug+0xb8/0x108\n[   31.083115]  drm_client_register+0xa0/0xf4\n[   31.083195]  drm_fbdev_dma_setup+0xb0/0x1cc\n[   31.083293]  zynqmp_dpsub_drm_init+0x45c/0x4e0\n[   31.083431]  zynqmp_dpsub_probe+0x444/0x5e0\n[   31.083616]  platform_probe+0x8c/0x13c\n[   31.083713]  really_probe+0x258/0x59c\n[   31.083793]  __driver_probe_device+0xc4/0x224\n[   31.083878]  driver_probe_device+0x70/0x1c0\n[   31.083961]  __device_attach_driver+0x108/0x1e0\n[   31.084052]  bus_for_each_drv+0x9c/0x100\n[   31.084125]  __device_attach+0x100/0x298\n[   31.084207]  device_initial_probe+0x14/0x20\n[   31.084292]  bus_probe_device+0xd8/0xdc\n[   31.084368]  deferred_probe_work_func+0x11c/0x180\n[   31.084451]  process_one_work+0x3ac/0x988\n[   31.084643]  worker_thread+0x398/0x694\n[   31.084752]  kthread+0x1bc/0x1c0\n[   31.084848]  ret_from_fork+0x10/0x20\n[   31.084932] irq event stamp: 64549\n[   31.084970] hardirqs last  enabled at (64548): [\u0026lt;ffffffc081adf35c\u0026gt;] _raw_spin_unlock_irqrestore+0x80/0x90\n[   31.085157]\n---truncated---(CVE-2024-35990)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nnetfilter: nfnetlink_queue: acquire rcu_read_lock() in instance_destroy_rcu()\r\n\r\nsyzbot reported that nf_reinject() could be called without rcu_read_lock() :\r\n\r\nWARNING: suspicious RCU usage\n6.9.0-rc7-syzkaller-02060-g5c1672705a1a #0 Not tainted\r\n\r\nnet/netfilter/nfnetlink_queue.c:263 suspicious rcu_dereference_check() usage!\r\n\r\nother info that might help us debug this:\r\n\r\nrcu_scheduler_active = 2, debug_locks = 1\n2 locks held by syz-executor.4/13427:\n  #0: ffffffff8e334f60 (rcu_callback){....}-{0:0}, at: rcu_lock_acquire include/linux/rcupdate.h:329 [inline]\n  #0: ffffffff8e334f60 (rcu_callback){....}-{0:0}, at: rcu_do_batch kernel/rcu/tree.c:2190 [inline]\n  #0: ffffffff8e334f60 (rcu_callback){....}-{0:0}, at: rcu_core+0xa86/0x1830 kernel/rcu/tree.c:2471\n  #1: ffff88801ca92958 (\u0026amp;inst-\u0026gt;lock){+.-.}-{2:2}, at: spin_lock_bh include/linux/spinlock.h:356 [inline]\n  #1: ffff88801ca92958 (\u0026amp;inst-\u0026gt;lock){+.-.}-{2:2}, at: nfqnl_flush net/netfilter/nfnetlink_queue.c:405 [inline]\n  #1: ffff88801ca92958 (\u0026amp;inst-\u0026gt;lock){+.-.}-{2:2}, at: instance_destroy_rcu+0x30/0x220 net/netfilter/nfnetlink_queue.c:172\r\n\r\nstack backtrace:\nCPU: 0 PID: 13427 Comm: syz-executor.4 Not tainted 6.9.0-rc7-syzkaller-02060-g5c1672705a1a #0\nHardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 04/02/2024\nCall Trace:\n \u0026lt;IRQ\u0026gt;\n  __dump_stack lib/dump_stack.c:88 [inline]\n  dump_stack_lvl+0x241/0x360 lib/dump_stack.c:114\n  lockdep_rcu_suspicious+0x221/0x340 kernel/locking/lockdep.c:6712\n  nf_reinject net/netfilter/nfnetlink_queue.c:323 [inline]\n  nfqnl_reinject+0x6ec/0x1120 net/netfilter/nfnetlink_queue.c:397\n  nfqnl_flush net/netfilter/nfnetlink_queue.c:410 [inline]\n  instance_destroy_rcu+0x1ae/0x220 net/netfilter/nfnetlink_queue.c:172\n  rcu_do_batch kernel/rcu/tree.c:2196 [inline]\n  rcu_core+0xafd/0x1830 kernel/rcu/tree.c:2471\n  handle_softirqs+0x2d6/0x990 kernel/softirq.c:554\n  __do_softirq kernel/softirq.c:588 [inline]\n  invoke_softirq kernel/softirq.c:428 [inline]\n  __irq_exit_rcu+0xf4/0x1c0 kernel/softirq.c:637\n  irq_exit_rcu+0x9/0x30 kernel/softirq.c:649\n  instr_sysvec_apic_timer_interrupt arch/x86/kernel/apic/apic.c:1043 [inline]\n  sysvec_apic_timer_interrupt+0xa6/0xc0 arch/x86/kernel/apic/apic.c:1043\n \u0026lt;/IRQ\u0026gt;\n \u0026lt;TASK\u0026gt;(CVE-2024-36286)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nsoundwire: cadence: fix invalid PDI offset\r\n\r\nFor some reason, we add an offset to the PDI, presumably to skip the\nPDI0 and PDI1 which are reserved for BPT.\r\n\r\nThis code is however completely wrong and leads to an out-of-bounds\naccess. We were just lucky so far since we used only a couple of PDIs\nand remained within the PDI array bounds.\r\n\r\nA Fixes: tag is not provided since there are no known platforms where\nthe out-of-bounds would be accessed, and the initial code had problems\nas well.\r\n\r\nA follow-up patch completely removes this useless offset.(CVE-2024-38635)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nriscv: prevent pt_regs corruption for secondary idle threads\r\n\r\nTop of the kernel thread stack should be reserved for pt_regs. However\nthis is not the case for the idle threads of the secondary boot harts.\nTheir stacks overlap with their pt_regs, so both may get corrupted.\r\n\r\nSimilar issue has been fixed for the primary hart, see c7cdd96eca28\n(\u0026quot;riscv: prevent stack corruption by reserving task_pt_regs(p) early\u0026quot;).\nHowever that fix was not propagated to the secondary harts. The problem\nhas been noticed in some CPU hotplug tests with V enabled. The function\nsmp_callin stored several registers on stack, corrupting top of pt_regs\nstructure including status field. As a result, kernel attempted to save\nor restore inexistent V context.(CVE-2024-38667)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nnvmet: fix a possible leak when destroy a ctrl during qp establishment\r\n\r\nIn nvmet_sq_destroy we capture sq-\u0026gt;ctrl early and if it is non-NULL we\nknow that a ctrl was allocated (in the admin connect request handler)\nand we need to release pending AERs, clear ctrl-\u0026gt;sqs and sq-\u0026gt;ctrl\n(for nvme-loop primarily), and drop the final reference on the ctrl.\r\n\r\nHowever, a small window is possible where nvmet_sq_destroy starts (as\na result of the client giving up and disconnecting) concurrently with\nthe nvme admin connect cmd (which may be in an early stage). But *before*\nkill_and_confirm of sq-\u0026gt;ref (i.e. the admin connect managed to get an sq\nlive reference). In this case, sq-\u0026gt;ctrl was allocated however after it was\ncaptured in a local variable in nvmet_sq_destroy.\nThis prevented the final reference drop on the ctrl.\r\n\r\nSolve this by re-capturing the sq-\u0026gt;ctrl after all inflight request has\ncompleted, where for sure sq-\u0026gt;ctrl reference is final, and move forward\nbased on that.\r\n\r\nThis issue was observed in an environment with many hosts connecting\nmultiple ctrls simoutanuosly, creating a delay in allocating a ctrl\nleading up to this race window.(CVE-2024-42152)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\ndev/parport: fix the array out-of-bounds risk\r\n\r\nFixed array out-of-bounds issues caused by sprintf\nby replacing it with snprintf for safer data copying,\nensuring the destination buffer is not overflowed.\r\n\r\nBelow is the stack trace I encountered during the actual issue:\r\n\r\n[ 66.575408s] [pid:5118,cpu4,QThread,4]Kernel panic - not syncing: stack-protector:\nKernel stack is corrupted in: do_hardware_base_addr+0xcc/0xd0 [parport]\n[ 66.575408s] [pid:5118,cpu4,QThread,5]CPU: 4 PID: 5118 Comm:\nQThread Tainted: G S W O 5.10.97-arm64-desktop #7100.57021.2\n[ 66.575439s] [pid:5118,cpu4,QThread,6]TGID: 5087 Comm: EFileApp\n[ 66.575439s] [pid:5118,cpu4,QThread,7]Hardware name: HUAWEI HUAWEI QingYun\nPGUX-W515x-B081/SP1PANGUXM, BIOS 1.00.07 04/29/2024\n[ 66.575439s] [pid:5118,cpu4,QThread,8]Call trace:\n[ 66.575469s] [pid:5118,cpu4,QThread,9] dump_backtrace+0x0/0x1c0\n[ 66.575469s] [pid:5118,cpu4,QThread,0] show_stack+0x14/0x20\n[ 66.575469s] [pid:5118,cpu4,QThread,1] dump_stack+0xd4/0x10c\n[ 66.575500s] [pid:5118,cpu4,QThread,2] panic+0x1d8/0x3bc\n[ 66.575500s] [pid:5118,cpu4,QThread,3] __stack_chk_fail+0x2c/0x38\n[ 66.575500s] [pid:5118,cpu4,QThread,4] do_hardware_base_addr+0xcc/0xd0 [parport](CVE-2024-42301)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nexfat: fix potential deadlock on __exfat_get_dentry_set\r\n\r\nWhen accessing a file with more entries than ES_MAX_ENTRY_NUM, the bh-array\nis allocated in __exfat_get_entry_set. The problem is that the bh-array is\nallocated with GFP_KERNEL. It does not make sense. In the following cases,\na deadlock for sbi-\u0026gt;s_lock between the two processes may occur.\r\n\r\n       CPU0                CPU1\n       ----                ----\n  kswapd\n   balance_pgdat\n    lock(fs_reclaim)\n                      exfat_iterate\n                       lock(\u0026amp;sbi-\u0026gt;s_lock)\n                       exfat_readdir\n                        exfat_get_uniname_from_ext_entry\n                         exfat_get_dentry_set\n                          __exfat_get_dentry_set\n                           kmalloc_array\n                            ...\n                            lock(fs_reclaim)\n    ...\n    evict\n     exfat_evict_inode\n      lock(\u0026amp;sbi-\u0026gt;s_lock)\r\n\r\nTo fix this, let\u0026apos;s allocate bh-array with GFP_NOFS.(CVE-2024-42315)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nwifi: virt_wifi: avoid reporting connection success with wrong SSID\r\n\r\nWhen user issues a connection with a different SSID than the one\nvirt_wifi has advertised, the __cfg80211_connect_result() will\ntrigger the warning: WARN_ON(bss_not_found).\r\n\r\nThe issue is because the connection code in virt_wifi does not\ncheck the SSID from user space (it only checks the BSSID), and\nvirt_wifi will call cfg80211_connect_result() with WLAN_STATUS_SUCCESS\neven if the SSID is different from the one virt_wifi has advertised.\nEventually cfg80211 won\u0026apos;t be able to find the cfg80211_bss and generate\nthe warning.\r\n\r\nFixed it by checking the SSID (from user space) in the connection code.(CVE-2024-43841)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\njfs: Fix array-index-out-of-bounds in diFree(CVE-2024-43858)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\ndrm/nouveau: prime: fix refcount underflow\r\n\r\nCalling nouveau_bo_ref() on a nouveau_bo without initializing it (and\nhence the backing ttm_bo) leads to a refcount underflow.\r\n\r\nInstead of calling nouveau_bo_ref() in the unwind path of\ndrm_gem_object_init(), clean things up manually.\r\n\r\n(cherry picked from commit 1b93f3e89d03cfc576636e195466a0d728ad8de5)(CVE-2024-43867)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\ndevres: Fix memory leakage caused by driver API devm_free_percpu()\r\n\r\nIt will cause memory leakage when use driver API devm_free_percpu()\nto free memory allocated by devm_alloc_percpu(), fixed by using\ndevres_release() instead of devres_destroy() within devm_free_percpu().(CVE-2024-43871)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\ndrm/client: fix null pointer dereference in drm_client_modeset_probe\r\n\r\nIn drm_client_modeset_probe(), the return value of drm_mode_duplicate() is\nassigned to modeset-\u0026gt;mode, which will lead to a possible NULL pointer\ndereference on failure of drm_mode_duplicate(). Add a check to avoid npd.(CVE-2024-43894)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nmptcp: pm: only decrement add_addr_accepted for MPJ req\r\n\r\nAdding the following warning ...\r\n\r\n  WARN_ON_ONCE(msk-\u0026gt;pm.add_addr_accepted == 0)\r\n\r\n... before decrementing the add_addr_accepted counter helped to find a\nbug when running the \u0026quot;remove single subflow\u0026quot; subtest from the\nmptcp_join.sh selftest.\r\n\r\nRemoving a \u0026apos;subflow\u0026apos; endpoint will first trigger a RM_ADDR, then the\nsubflow closure. Before this patch, and upon the reception of the\nRM_ADDR, the other peer will then try to decrement this\nadd_addr_accepted. That\u0026apos;s not correct because the attached subflows have\nnot been created upon the reception of an ADD_ADDR.\r\n\r\nA way to solve that is to decrement the counter only if the attached\nsubflow was an MP_JOIN to a remote id that was not 0, and initiated by\nthe host receiving the RM_ADDR.(CVE-2024-45009)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nusb: dwc3: core: Prevent USB core invalid event buffer address access\r\n\r\nThis commit addresses an issue where the USB core could access an\ninvalid event buffer address during runtime suspend, potentially causing\nSMMU faults and other memory issues in Exynos platforms. The problem\narises from the following sequence.\n        1. In dwc3_gadget_suspend, there is a chance of a timeout when\n        moving the USB core to the halt state after clearing the\n        run/stop bit by software.\n        2. In dwc3_core_exit, the event buffer is cleared regardless of\n        the USB core\u0026apos;s status, which may lead to an SMMU faults and\n        other memory issues. if the USB core tries to access the event\n        buffer address.\r\n\r\nTo prevent this hardware quirk on Exynos platforms, this commit ensures\nthat the event buffer address is not cleared by software  when the USB\ncore is active during runtime suspend by checking its status before\nclearing the buffer address.(CVE-2024-46675)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nsoc: qcom: cmd-db: Map shared memory as WC, not WB\r\n\r\nLinux does not write into cmd-db region. This region of memory is write\nprotected by XPU. XPU may sometime falsely detect clean cache eviction\nas \u0026quot;write\u0026quot; into the write protected region leading to secure interrupt\nwhich causes an endless loop somewhere in Trust Zone.\r\n\r\nThe only reason it is working right now is because Qualcomm Hypervisor\nmaps the same region as Non-Cacheable memory in Stage 2 translation\ntables. The issue manifests if we want to use another hypervisor (like\nXen or KVM), which does not know anything about those specific mappings.\r\n\r\nChanging the mapping of cmd-db memory from MEMREMAP_WB to MEMREMAP_WT/WC\nremoves dependency on correct mappings in Stage 2 tables. This patch\nfixes the issue by updating the mapping to MEMREMAP_WC.\r\n\r\nI tested this on SA8155P with Xen.(CVE-2024-46689)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\ndrm/amdgpu: fix mc_data out-of-bounds read warning\r\n\r\nClear warning that read mc_data[i-1] may out-of-bounds.(CVE-2024-46722)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\ndrm/amdgpu: Fix out-of-bounds read of df_v1_7_channel_number\r\n\r\nCheck the fb_channel_number range to avoid the array out-of-bounds\nread error(CVE-2024-46724)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nhwmon: (nct6775-core) Fix underflows seen when writing limit attributes\r\n\r\nDIV_ROUND_CLOSEST() after kstrtol() results in an underflow if a large\nnegative number such as -9223372036854775808 is provided by the user.\nFix it by reordering clamp_val() and DIV_ROUND_CLOSEST() operations.(CVE-2024-46757)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\ndrm/amd/display: added NULL check at start of dc_validate_stream\r\n\r\n[Why]\nprevent invalid memory access\r\n\r\n[How]\ncheck if dc and stream are NULL(CVE-2024-46802)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nKVM: x86: Acquire kvm-\u0026gt;srcu when handling KVM_SET_VCPU_EVENTS\r\n\r\nGrab kvm-\u0026gt;srcu when processing KVM_SET_VCPU_EVENTS, as KVM will forcibly\nleave nested VMX/SVM if SMM mode is being toggled, and leaving nested VMX\nreads guest memory.\r\n\r\nNote, kvm_vcpu_ioctl_x86_set_vcpu_events() can also be called from KVM_RUN\nvia sync_regs(), which already holds SRCU.  I.e. trying to precisely use\nkvm_vcpu_srcu_read_lock() around the problematic SMM code would cause\nproblems.  Acquiring SRCU isn\u0026apos;t all that expensive, so for simplicity,\ngrab it unconditionally for KVM_SET_VCPU_EVENTS.\r\n\r\n =============================\n WARNING: suspicious RCU usage\n 6.10.0-rc7-332d2c1d713e-next-vm #552 Not tainted\n -----------------------------\n include/linux/kvm_host.h:1027 suspicious rcu_dereference_check() usage!\r\n\r\n other info that might help us debug this:\r\n\r\n rcu_scheduler_active = 2, debug_locks = 1\n 1 lock held by repro/1071:\n  #0: ffff88811e424430 (\u0026amp;vcpu-\u0026gt;mutex){+.+.}-{3:3}, at: kvm_vcpu_ioctl+0x7d/0x970 [kvm]\r\n\r\n stack backtrace:\n CPU: 15 PID: 1071 Comm: repro Not tainted 6.10.0-rc7-332d2c1d713e-next-vm #552\n Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 0.0.0 02/06/2015\n Call Trace:\n  \u0026lt;TASK\u0026gt;\n  dump_stack_lvl+0x7f/0x90\n  lockdep_rcu_suspicious+0x13f/0x1a0\n  kvm_vcpu_gfn_to_memslot+0x168/0x190 [kvm]\n  kvm_vcpu_read_guest+0x3e/0x90 [kvm]\n  nested_vmx_load_msr+0x6b/0x1d0 [kvm_intel]\n  load_vmcs12_host_state+0x432/0xb40 [kvm_intel]\n  vmx_leave_nested+0x30/0x40 [kvm_intel]\n  kvm_vcpu_ioctl_x86_set_vcpu_events+0x15d/0x2b0 [kvm]\n  kvm_arch_vcpu_ioctl+0x1107/0x1750 [kvm]\n  ? mark_held_locks+0x49/0x70\n  ? kvm_vcpu_ioctl+0x7d/0x970 [kvm]\n  ? kvm_vcpu_ioctl+0x497/0x970 [kvm]\n  kvm_vcpu_ioctl+0x497/0x970 [kvm]\n  ? lock_acquire+0xba/0x2d0\n  ? find_held_lock+0x2b/0x80\n  ? do_user_addr_fault+0x40c/0x6f0\n  ? lock_release+0xb7/0x270\n  __x64_sys_ioctl+0x82/0xb0\n  do_syscall_64+0x6c/0x170\n  entry_SYSCALL_64_after_hwframe+0x4b/0x53\n RIP: 0033:0x7ff11eb1b539\n  \u0026lt;/TASK\u0026gt;(CVE-2024-46830)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nspi: nxp-fspi: fix the KASAN report out-of-bounds bug\r\n\r\nChange the memcpy length to fix the out-of-bounds issue when writing the\ndata that is not 4 byte aligned to TX FIFO.\r\n\r\nTo reproduce the issue, write 3 bytes data to NOR chip.\r\n\r\ndd if=3b of=/dev/mtd0\n[   36.926103] ==================================================================\n[   36.933409] BUG: KASAN: slab-out-of-bounds in nxp_fspi_exec_op+0x26ec/0x2838\n[   36.940514] Read of size 4 at addr ffff00081037c2a0 by task dd/455\n[   36.946721]\n[   36.948235] CPU: 3 UID: 0 PID: 455 Comm: dd Not tainted 6.11.0-rc5-gc7b0e37c8434 #1070\n[   36.956185] Hardware name: Freescale i.MX8QM MEK (DT)\n[   36.961260] Call trace:\n[   36.963723]  dump_backtrace+0x90/0xe8\n[   36.967414]  show_stack+0x18/0x24\n[   36.970749]  dump_stack_lvl+0x78/0x90\n[   36.974451]  print_report+0x114/0x5cc\n[   36.978151]  kasan_report+0xa4/0xf0\n[   36.981670]  __asan_report_load_n_noabort+0x1c/0x28\n[   36.986587]  nxp_fspi_exec_op+0x26ec/0x2838\n[   36.990800]  spi_mem_exec_op+0x8ec/0xd30\n[   36.994762]  spi_mem_no_dirmap_read+0x190/0x1e0\n[   36.999323]  spi_mem_dirmap_write+0x238/0x32c\n[   37.003710]  spi_nor_write_data+0x220/0x374\n[   37.007932]  spi_nor_write+0x110/0x2e8\n[   37.011711]  mtd_write_oob_std+0x154/0x1f0\n[   37.015838]  mtd_write_oob+0x104/0x1d0\n[   37.019617]  mtd_write+0xb8/0x12c\n[   37.022953]  mtdchar_write+0x224/0x47c\n[   37.026732]  vfs_write+0x1e4/0x8c8\n[   37.030163]  ksys_write+0xec/0x1d0\n[   37.033586]  __arm64_sys_write+0x6c/0x9c\n[   37.037539]  invoke_syscall+0x6c/0x258\n[   37.041327]  el0_svc_common.constprop.0+0x160/0x22c\n[   37.046244]  do_el0_svc+0x44/0x5c\n[   37.049589]  el0_svc+0x38/0x78\n[   37.052681]  el0t_64_sync_handler+0x13c/0x158\n[   37.057077]  el0t_64_sync+0x190/0x194\n[   37.060775]\n[   37.062274] Allocated by task 455:\n[   37.065701]  kasan_save_stack+0x2c/0x54\n[   37.069570]  kasan_save_track+0x20/0x3c\n[   37.073438]  kasan_save_alloc_info+0x40/0x54\n[   37.077736]  __kasan_kmalloc+0xa0/0xb8\n[   37.081515]  __kmalloc_noprof+0x158/0x2f8\n[   37.085563]  mtd_kmalloc_up_to+0x120/0x154\n[   37.089690]  mtdchar_write+0x130/0x47c\n[   37.093469]  vfs_write+0x1e4/0x8c8\n[   37.096901]  ksys_write+0xec/0x1d0\n[   37.100332]  __arm64_sys_write+0x6c/0x9c\n[   37.104287]  invoke_syscall+0x6c/0x258\n[   37.108064]  el0_svc_common.constprop.0+0x160/0x22c\n[   37.112972]  do_el0_svc+0x44/0x5c\n[   37.116319]  el0_svc+0x38/0x78\n[   37.119401]  el0t_64_sync_handler+0x13c/0x158\n[   37.123788]  el0t_64_sync+0x190/0x194\n[   37.127474]\n[   37.128977] The buggy address belongs to the object at ffff00081037c2a0\n[   37.128977]  which belongs to the cache kmalloc-8 of size 8\n[   37.141177] The buggy address is located 0 bytes inside of\n[   37.141177]  allocated 3-byte region [ffff00081037c2a0, ffff00081037c2a3)\n[   37.153465]\n[   37.154971] The buggy address belongs to the physical page:\n[   37.160559] page: refcount:1 mapcount:0 mapping:0000000000000000 index:0x0 pfn:0x89037c\n[   37.168596] flags: 0xbfffe0000000000(node=0|zone=2|lastcpupid=0x1ffff)\n[   37.175149] page_type: 0xfdffffff(slab)\n[   37.179021] raw: 0bfffe0000000000 ffff000800002500 dead000000000122 0000000000000000\n[   37.186788] raw: 0000000000000000 0000000080800080 00000001fdffffff 0000000000000000\n[   37.194553] page dumped because: kasan: bad access detected\n[   37.200144]\n[   37.201647] Memory state around the buggy address:\n[   37.206460]  ffff00081037c180: fa fc fc fc fa fc fc fc fa fc fc fc fa fc fc fc\n[   37.213701]  ffff00081037c200: fa fc fc fc 05 fc fc fc 03 fc fc fc 02 fc fc fc\n[   37.220946] \u0026gt;ffff00081037c280: 06 fc fc fc 03 fc fc fc fc fc fc fc fc fc fc fc\n[   37.228186]                                ^\n[   37.232473]  ffff00081037c300: fc fc fc fc fc fc fc fc fc fc fc fc fc fc fc fc\n[   37.239718]  ffff00081037c380: fc fc fc fc fc fc fc fc fc fc fc fc fc fc fc fc\n[   37.246962] ==============================================================\n---truncated---(CVE-2024-46853)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nPCI: keystone: Add workaround for Errata #i2037 (AM65x SR 1.0)\r\n\r\nErrata #i2037 in AM65x/DRA80xM Processors Silicon Revision 1.0\n(SPRZ452D_July 2018_Revised December 2019 [1]) mentions when an\ninbound PCIe TLP spans more than two internal AXI 128-byte bursts,\nthe bus may corrupt the packet payload and the corrupt data may\ncause associated applications or the processor to hang.\r\n\r\nThe workaround for Errata #i2037 is to limit the maximum read\nrequest size and maximum payload size to 128 bytes. Add workaround\nfor Errata #i2037 here.\r\n\r\nThe errata and workaround is applicable only to AM65x SR 1.0 and\nlater versions of the silicon will have this fixed.\r\n\r\n[1] -\u0026gt; https://www.ti.com/lit/er/sprz452i/sprz452i.pdf(CVE-2024-47667)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nnilfs2: fix state management in error path of log writing function\r\n\r\nAfter commit a694291a6211 (\u0026quot;nilfs2: separate wait function from\nnilfs_segctor_write\u0026quot;) was applied, the log writing function\nnilfs_segctor_do_construct() was able to issue I/O requests continuously\neven if user data blocks were split into multiple logs across segments,\nbut two potential flaws were introduced in its error handling.\r\n\r\nFirst, if nilfs_segctor_begin_construction() fails while creating the\nsecond or subsequent logs, the log writing function returns without\ncalling nilfs_segctor_abort_construction(), so the writeback flag set on\npages/folios will remain uncleared.  This causes page cache operations to\nhang waiting for the writeback flag.  For example,\ntruncate_inode_pages_final(), which is called via nilfs_evict_inode() when\nan inode is evicted from memory, will hang.\r\n\r\nSecond, the NILFS_I_COLLECTED flag set on normal inodes remain uncleared. \nAs a result, if the next log write involves checkpoint creation, that\u0026apos;s\nfine, but if a partial log write is performed that does not, inodes with\nNILFS_I_COLLECTED set are erroneously removed from the \u0026quot;sc_dirty_files\u0026quot;\nlist, and their data and b-tree blocks may not be written to the device,\ncorrupting the block mapping.\r\n\r\nFix these issues by uniformly calling nilfs_segctor_abort_construction()\non failure of each step in the loop in nilfs_segctor_do_construct(),\nhaving it clean up logs and segment usages according to progress, and\ncorrecting the conditions for calling nilfs_redirty_inodes() to ensure\nthat the NILFS_I_COLLECTED flag is cleared.(CVE-2024-47669)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  tcp: check skb is non-NULL in tcp_rto_delta_us()  We have some machines running stock Ubuntu 20.04.6 which is their 5.4.0-174-generic kernel that are running ceph and recently hit a null ptr dereference in tcp_rearm_rto(). Initially hitting it from the TLP path, but then later we also saw it getting hit from the RACK case as well. Here are examples of the oops messages we saw in each of those cases:  Jul 26 15:05:02 rx [11061395.780353] BUG: kernel NULL pointer dereference, address: 0000000000000020 Jul 26 15:05:02 rx [11061395.787572] #PF: supervisor read access in kernel mode Jul 26 15:05:02 rx [11061395.792971] #PF: error_code(0x0000) - not-present page Jul 26 15:05:02 rx [11061395.798362] PGD 0 P4D 0 Jul 26 15:05:02 rx [11061395.801164] Oops: 0000 [#1] SMP NOPTI Jul 26 15:05:02 rx [11061395.805091] CPU: 0 PID: 9180 Comm: msgr-worker-1 Tainted: G W 5.4.0-174-generic #193-Ubuntu Jul 26 15:05:02 rx [11061395.814996] Hardware name: Supermicro SMC 2x26 os-gen8 64C NVME-Y 256G/H12SSW-NTR, BIOS 2.5.V1.2U.NVMe.UEFI 05/09/2023 Jul 26 15:05:02 rx [11061395.825952] RIP: 0010:tcp_rearm_rto+0xe4/0x160 Jul 26 15:05:02 rx [11061395.830656] Code: 87 ca 04 00 00 00 5b 41 5c 41 5d 5d c3 c3 49 8b bc 24 40 06 00 00 eb 8d 48 bb cf f7 53 e3 a5 9b c4 20 4c 89 ef e8 0c fe 0e 00 \u0026lt;48\u0026gt; 8b 78 20 48 c1 ef 03 48 89 f8 41 8b bc 24 80 04 00 00 48 f7 e3 Jul 26 15:05:02 rx [11061395.849665] RSP: 0018:ffffb75d40003e08 EFLAGS: 00010246 Jul 26 15:05:02 rx [11061395.855149] RAX: 0000000000000000 RBX: 20c49ba5e353f7cf RCX: 0000000000000000 Jul 26 15:05:02 rx [11061395.862542] RDX: 0000000062177c30 RSI: 000000000000231c RDI: ffff9874ad283a60 Jul 26 15:05:02 rx [11061395.869933] RBP: ffffb75d40003e20 R08: 0000000000000000 R09: ffff987605e20aa8 Jul 26 15:05:02 rx [11061395.877318] R10: ffffb75d40003f00 R11: ffffb75d4460f740 R12: ffff9874ad283900 Jul 26 15:05:02 rx [11061395.884710] R13: ffff9874ad283a60 R14: ffff9874ad283980 R15: ffff9874ad283d30 Jul 26 15:05:02 rx [11061395.892095] FS: 00007f1ef4a2e700(0000) GS:ffff987605e00000(0000) knlGS:0000000000000000 Jul 26 15:05:02 rx [11061395.900438] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 Jul 26 15:05:02 rx [11061395.906435] CR2: 0000000000000020 CR3: 0000003e450ba003 CR4: 0000000000760ef0 Jul 26 15:05:02 rx [11061395.913822] PKRU: 55555554 Jul 26 15:05:02 rx [11061395.916786] Call Trace: Jul 26 15:05:02 rx [11061395.919488] Jul 26 15:05:02 rx [11061395.921765] ? show_regs.cold+0x1a/0x1f Jul 26 15:05:02 rx [11061395.925859] ? __die+0x90/0xd9 Jul 26 15:05:02 rx [11061395.929169] ? no_context+0x196/0x380 Jul 26 15:05:02 rx [11061395.933088] ? ip6_protocol_deliver_rcu+0x4e0/0x4e0 Jul 26 15:05:02 rx [11061395.938216] ? ip6_sublist_rcv_finish+0x3d/0x50 Jul 26 15:05:02 rx [11061395.943000] ? __bad_area_nosemaphore+0x50/0x1a0 Jul 26 15:05:02 rx [11061395.947873] ? bad_area_nosemaphore+0x16/0x20 Jul 26 15:05:02 rx [11061395.952486] ? do_user_addr_fault+0x267/0x450 Jul 26 15:05:02 rx [11061395.957104] ? ipv6_list_rcv+0x112/0x140 Jul 26 15:05:02 rx [11061395.961279] ? __do_page_fault+0x58/0x90 Jul 26 15:05:02 rx [11061395.965458] ? do_page_fault+0x2c/0xe0 Jul 26 15:05:02 rx [11061395.969465] ? page_fault+0x34/0x40 Jul 26 15:05:02 rx [11061395.973217] ? tcp_rearm_rto+0xe4/0x160 Jul 26 15:05:02 rx [11061395.977313] ? tcp_rearm_rto+0xe4/0x160 Jul 26 15:05:02 rx [11061395.981408] tcp_send_loss_probe+0x10b/0x220 Jul 26 15:05:02 rx [11061395.985937] tcp_write_timer_handler+0x1b4/0x240 Jul 26 15:05:02 rx [11061395.990809] tcp_write_timer+0x9e/0xe0 Jul 26 15:05:02 rx [11061395.994814] ? tcp_write_timer_handler+0x240/0x240 Jul 26 15:05:02 rx [11061395.999866] call_timer_fn+0x32/0x130 Jul 26 15:05:02 rx [11061396.003782] __run_timers.part.0+0x180/0x280 Jul 26 15:05:02 rx [11061396.008309] ? recalibrate_cpu_khz+0x10/0x10 Jul 26 15:05:02 rx [11061396.012841] ? native_x2apic_icr_write+0x30/0x30 Jul 26 15:05:02 rx [11061396.017718] ? lapic_next_even ---truncated---(CVE-2024-47684)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  netfilter: nf_reject_ipv6: fix nf_reject_ip6_tcphdr_put()  syzbot reported that nf_reject_ip6_tcphdr_put() was possibly sending garbage on the four reserved tcp bits (th-\u0026gt;res1)  Use skb_put_zero() to clear the whole TCP header, as done in nf_reject_ip_tcphdr_put()  BUG: KMSAN: uninit-value in nf_reject_ip6_tcphdr_put+0x688/0x6c0 net/ipv6/netfilter/nf_reject_ipv6.c:255   nf_reject_ip6_tcphdr_put+0x688/0x6c0 net/ipv6/netfilter/nf_reject_ipv6.c:255   nf_send_reset6+0xd84/0x15b0 net/ipv6/netfilter/nf_reject_ipv6.c:344   nft_reject_inet_eval+0x3c1/0x880 net/netfilter/nft_reject_inet.c:48   expr_call_ops_eval net/netfilter/nf_tables_core.c:240 [inline]   nft_do_chain+0x438/0x22a0 net/netfilter/nf_tables_core.c:288   nft_do_chain_inet+0x41a/0x4f0 net/netfilter/nft_chain_filter.c:161   nf_hook_entry_hookfn include/linux/netfilter.h:154 [inline]   nf_hook_slow+0xf4/0x400 net/netfilter/core.c:626   nf_hook include/linux/netfilter.h:269 [inline]   NF_HOOK include/linux/netfilter.h:312 [inline]   ipv6_rcv+0x29b/0x390 net/ipv6/ip6_input.c:310   __netif_receive_skb_one_core net/core/dev.c:5661 [inline]   __netif_receive_skb+0x1da/0xa00 net/core/dev.c:5775   process_backlog+0x4ad/0xa50 net/core/dev.c:6108   __napi_poll+0xe7/0x980 net/core/dev.c:6772   napi_poll net/core/dev.c:6841 [inline]   net_rx_action+0xa5a/0x19b0 net/core/dev.c:6963   handle_softirqs+0x1ce/0x800 kernel/softirq.c:554   __do_softirq+0x14/0x1a kernel/softirq.c:588   do_softirq+0x9a/0x100 kernel/softirq.c:455   __local_bh_enable_ip+0x9f/0xb0 kernel/softirq.c:382   local_bh_enable include/linux/bottom_half.h:33 [inline]   rcu_read_unlock_bh include/linux/rcupdate.h:908 [inline]   __dev_queue_xmit+0x2692/0x5610 net/core/dev.c:4450   dev_queue_xmit include/linux/netdevice.h:3105 [inline]   neigh_resolve_output+0x9ca/0xae0 net/core/neighbour.c:1565   neigh_output include/net/neighbour.h:542 [inline]   ip6_finish_output2+0x2347/0x2ba0 net/ipv6/ip6_output.c:141   __ip6_finish_output net/ipv6/ip6_output.c:215 [inline]   ip6_finish_output+0xbb8/0x14b0 net/ipv6/ip6_output.c:226   NF_HOOK_COND include/linux/netfilter.h:303 [inline]   ip6_output+0x356/0x620 net/ipv6/ip6_output.c:247   dst_output include/net/dst.h:450 [inline]   NF_HOOK include/linux/netfilter.h:314 [inline]   ip6_xmit+0x1ba6/0x25d0 net/ipv6/ip6_output.c:366   inet6_csk_xmit+0x442/0x530 net/ipv6/inet6_connection_sock.c:135   __tcp_transmit_skb+0x3b07/0x4880 net/ipv4/tcp_output.c:1466   tcp_transmit_skb net/ipv4/tcp_output.c:1484 [inline]   tcp_connect+0x35b6/0x7130 net/ipv4/tcp_output.c:4143   tcp_v6_connect+0x1bcc/0x1e40 net/ipv6/tcp_ipv6.c:333   __inet_stream_connect+0x2ef/0x1730 net/ipv4/af_inet.c:679   inet_stream_connect+0x6a/0xd0 net/ipv4/af_inet.c:750   __sys_connect_file net/socket.c:2061 [inline]   __sys_connect+0x606/0x690 net/socket.c:2078   __do_sys_connect net/socket.c:2088 [inline]   __se_sys_connect net/socket.c:2085 [inline]   __x64_sys_connect+0x91/0xe0 net/socket.c:2085   x64_sys_call+0x27a5/0x3ba0 arch/x86/include/generated/asm/syscalls_64.h:43   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 stored to memory at:   nf_reject_ip6_tcphdr_put+0x60c/0x6c0 net/ipv6/netfilter/nf_reject_ipv6.c:249   nf_send_reset6+0xd84/0x15b0 net/ipv6/netfilter/nf_reject_ipv6.c:344   nft_reject_inet_eval+0x3c1/0x880 net/netfilter/nft_reject_inet.c:48   expr_call_ops_eval net/netfilter/nf_tables_core.c:240 [inline]   nft_do_chain+0x438/0x22a0 net/netfilter/nf_tables_core.c:288   nft_do_chain_inet+0x41a/0x4f0 net/netfilter/nft_chain_filter.c:161   nf_hook_entry_hookfn include/linux/netfilter.h:154 [inline]   nf_hook_slow+0xf4/0x400 net/netfilter/core.c:626   nf_hook include/linux/netfilter.h:269 [inline]   NF_HOOK include/linux/netfilter.h:312 [inline]   ipv6_rcv+0x29b/0x390 net/ipv6/ip6_input.c:310   __netif_receive_skb_one_core ---truncated---(CVE-2024-47685)\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:  RDMA/rtrs-clt: Reset cid to con_num - 1 to stay in bounds  In the function init_conns(), after the create_con() and create_cm() for loop if something fails. In the cleanup for loop after the destroy tag, we access out of bound memory because cid is set to clt_path-\u0026gt;s.con_num.  This commits resets the cid to clt_path-\u0026gt;s.con_num - 1, to stay in bounds in the cleanup loop later.(CVE-2024-47695)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  drivers: media: dvb-frontends/rtl2832: fix an out-of-bounds write error  Ensure index in rtl2832_pid_filter does not exceed 31 to prevent out-of-bounds access.  dev-\u0026gt;filters is a 32-bit value, so set_bit and clear_bit functions should only operate on indices from 0 to 31. If index is 32, it will attempt to access a non-existent 33rd bit, leading to out-of-bounds access. Change the boundary check from index \u0026gt; 32 to index \u0026gt;= 32 to resolve this issue.  [hverkuil: added fixes tag, rtl2830_pid_filter -\u0026gt; rtl2832_pid_filter in logmsg](CVE-2024-47698)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  can: bcm: Clear bo-\u0026gt;bcm_proc_read after remove_proc_entry().  syzbot reported a warning in bcm_release(). [0]  The blamed change fixed another warning that is triggered when connect() is issued again for a socket whose connect()ed device has been unregistered.  However, if the socket is just close()d without the 2nd connect(), the remaining bo-\u0026gt;bcm_proc_read triggers unnecessary remove_proc_entry() in bcm_release().  Let\u0026apos;s clear bo-\u0026gt;bcm_proc_read after remove_proc_entry() in bcm_notify().  [0] name \u0026apos;4986\u0026apos; WARNING: CPU: 0 PID: 5234 at fs/proc/generic.c:711 remove_proc_entry+0x2e7/0x5d0 fs/proc/generic.c:711 Modules linked in: CPU: 0 UID: 0 PID: 5234 Comm: syz-executor606 Not tainted 6.11.0-rc5-syzkaller-00178-g5517ae241919 #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 08/06/2024 RIP: 0010:remove_proc_entry+0x2e7/0x5d0 fs/proc/generic.c:711 Code: ff eb 05 e8 cb 1e 5e ff 48 8b 5c 24 10 48 c7 c7 e0 f7 aa 8e e8 2a 38 8e 09 90 48 c7 c7 60 3a 1b 8c 48 89 de e8 da 42 20 ff 90 \u0026lt;0f\u0026gt; 0b 90 90 48 8b 44 24 18 48 c7 44 24 40 0e 36 e0 45 49 c7 04 07 RSP: 0018:ffffc9000345fa20 EFLAGS: 00010246 RAX: 2a2d0aee2eb64600 RBX: ffff888032f1f548 RCX: ffff888029431e00 RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000000000000 RBP: ffffc9000345fb08 R08: ffffffff8155b2f2 R09: 1ffff1101710519a R10: dffffc0000000000 R11: ffffed101710519b R12: ffff888011d38640 R13: 0000000000000004 R14: 0000000000000000 R15: dffffc0000000000 FS:  0000000000000000(0000) GS:ffff8880b8800000(0000) knlGS:0000000000000000 CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 00007fcfb52722f0 CR3: 000000000e734000 CR4: 00000000003506f0 DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400 Call Trace:  \u0026lt;TASK\u0026gt;  bcm_release+0x250/0x880 net/can/bcm.c:1578  __sock_release net/socket.c:659 [inline]  sock_close+0xbc/0x240 net/socket.c:1421  __fput+0x24a/0x8a0 fs/file_table.c:422  task_work_run+0x24f/0x310 kernel/task_work.c:228  exit_task_work include/linux/task_work.h:40 [inline]  do_exit+0xa2f/0x27f0 kernel/exit.c:882  do_group_exit+0x207/0x2c0 kernel/exit.c:1031  __do_sys_exit_group kernel/exit.c:1042 [inline]  __se_sys_exit_group kernel/exit.c:1040 [inline]  __x64_sys_exit_group+0x3f/0x40 kernel/exit.c:1040  x64_sys_call+0x2634/0x2640 arch/x86/include/generated/asm/syscalls_64.h:232  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:0x7fcfb51ee969 Code: Unable to access opcode bytes at 0x7fcfb51ee93f. RSP: 002b:00007ffce0109ca8 EFLAGS: 00000246 ORIG_RAX: 00000000000000e7 RAX: ffffffffffffffda RBX: 0000000000000001 RCX: 00007fcfb51ee969 RDX: 000000000000003c RSI: 00000000000000e7 RDI: 0000000000000001 RBP: 00007fcfb526f3b0 R08: ffffffffffffffb8 R09: 0000555500000000 R10: 0000555500000000 R11: 0000000000000246 R12: 00007fcfb526f3b0 R13: 0000000000000000 R14: 00007fcfb5271ee0 R15: 00007fcfb51bf160  \u0026lt;/TASK\u0026gt;(CVE-2024-47709)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  sock_map: Add a cond_resched() in sock_hash_free()  Several syzbot soft lockup reports all have in common sock_hash_free()  If a map with a large number of buckets is destroyed, we need to yield the cpu when needed.(CVE-2024-47710)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  drm/amd/display: Add null check for set_output_gamma in dcn30_set_output_transfer_func  This commit adds a null check for the set_output_gamma function pointer in the  dcn30_set_output_transfer_func function. Previously, set_output_gamma was being checked for nullity at line 386, but then it was being dereferenced without any nullity check at line 401. This could potentially lead to a null pointer dereference error if set_output_gamma is indeed null.  To fix this, we now ensure that set_output_gamma is not null before dereferencing it. We do this by adding a nullity check for set_output_gamma before the call to set_output_gamma at line 401. If set_output_gamma is null, we log an error message and do not call the function.  This fix prevents a potential null pointer dereference error.  drivers/gpu/drm/amd/amdgpu/../display/dc/hwss/dcn30/dcn30_hwseq.c:401 dcn30_set_output_transfer_func() error: we previously assumed \u0026apos;mpc-\u0026gt;funcs-\u0026gt;set_output_gamma\u0026apos; could be null (see line 386)  drivers/gpu/drm/amd/amdgpu/../display/dc/hwss/dcn30/dcn30_hwseq.c     373 bool dcn30_set_output_transfer_func(struct dc *dc,     374                                 struct pipe_ctx *pipe_ctx,     375                                 const struct dc_stream_state *stream)     376 {     377         int mpcc_id = pipe_ctx-\u0026gt;plane_res.hubp-\u0026gt;inst;     378         struct mpc *mpc = pipe_ctx-\u0026gt;stream_res.opp-\u0026gt;ctx-\u0026gt;dc-\u0026gt;res_pool-\u0026gt;mpc;     379         const struct pwl_params *params = NULL;     380         bool ret = false;     381     382         /* program OGAM or 3DLUT only for the top pipe*/     383         if (pipe_ctx-\u0026gt;top_pipe == NULL) {     384                 /*program rmu shaper and 3dlut in MPC*/     385                 ret = dcn30_set_mpc_shaper_3dlut(pipe_ctx, stream);     386                 if (ret == false \u0026amp;\u0026amp; mpc-\u0026gt;funcs-\u0026gt;set_output_gamma) {                                             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^ If this is NULL      387                         if (stream-\u0026gt;out_transfer_func.type == TF_TYPE_HWPWL)     388                                 params = \u0026amp;stream-\u0026gt;out_transfer_func.pwl;     389                         else if (pipe_ctx-\u0026gt;stream-\u0026gt;out_transfer_func.type ==     390                                         TF_TYPE_DISTRIBUTED_POINTS \u0026amp;\u0026amp;     391                                         cm3_helper_translate_curve_to_hw_format(     392                                         \u0026amp;stream-\u0026gt;out_transfer_func,     393                                         \u0026amp;mpc-\u0026gt;blender_params, false))     394                                 params = \u0026amp;mpc-\u0026gt;blender_params;     395                          /* there are no ROM LUTs in OUTGAM */     396                         if (stream-\u0026gt;out_transfer_func.type == TF_TYPE_PREDEFINED)     397                                 BREAK_TO_DEBUGGER();     398                 }     399         }     400 --\u0026gt; 401         mpc-\u0026gt;funcs-\u0026gt;set_output_gamma(mpc, mpcc_id, params);                 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^ Then it will crash      402         return ret;     403 }(CVE-2024-47720)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  RDMA/hns: Fix spin_unlock_irqrestore() called with IRQs enabled  Fix missuse of spin_lock_irq()/spin_unlock_irq() when spin_lock_irqsave()/spin_lock_irqrestore() was hold.  This was discovered through the lock debugging, and the corresponding log is as follows:  raw_local_irq_restore() called with IRQs enabled WARNING: CPU: 96 PID: 2074 at kernel/locking/irqflag-debug.c:10 warn_bogus_irq_restore+0x30/0x40 ... Call trace:  warn_bogus_irq_restore+0x30/0x40  _raw_spin_unlock_irqrestore+0x84/0xc8  add_qp_to_list+0x11c/0x148 [hns_roce_hw_v2]  hns_roce_create_qp_common.constprop.0+0x240/0x780 [hns_roce_hw_v2]  hns_roce_create_qp+0x98/0x160 [hns_roce_hw_v2]  create_qp+0x138/0x258  ib_create_qp_kernel+0x50/0xe8  create_mad_qp+0xa8/0x128  ib_mad_port_open+0x218/0x448  ib_mad_init_device+0x70/0x1f8  add_client_context+0xfc/0x220  enable_device_and_get+0xd0/0x140  ib_register_device.part.0+0xf4/0x1c8  ib_register_device+0x34/0x50  hns_roce_register_device+0x174/0x3d0 [hns_roce_hw_v2]  hns_roce_init+0xfc/0x2c0 [hns_roce_hw_v2]  __hns_roce_hw_v2_init_instance+0x7c/0x1d0 [hns_roce_hw_v2]  hns_roce_hw_v2_init_instance+0x9c/0x180 [hns_roce_hw_v2](CVE-2024-47735)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  nfsd: call cache_put if xdr_reserve_space returns NULL  If not enough buffer space available, but idmap_lookup has triggered lookup_fn which calls cache_get and returns successfully. Then we missed to call cache_put here which pairs with cache_get.  Reviwed-by: Jeff Layton \u0026lt;jlayton@kernel.org\u0026gt;(CVE-2024-47737)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  nilfs2: fix potential oob read in nilfs_btree_check_delete()  The function nilfs_btree_check_delete(), which checks whether degeneration to direct mapping occurs before deleting a b-tree entry, causes memory access outside the block buffer when retrieving the maximum key if the root node has no entries.  This does not usually happen because b-tree mappings with 0 child nodes are never created by mkfs.nilfs2 or nilfs2 itself.  However, it can happen if the b-tree root node read from a device is configured that way, so fix this potential issue by adding a check for that case.(CVE-2024-47757)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  tracing/timerlat: Fix a race during cpuhp processing  There is another found exception that the \u0026quot;timerlat/1\u0026quot; thread was scheduled on CPU0, and lead to timer corruption finally:  ``` ODEBUG: init active (active state 0) object: ffff888237c2e108 object type: hrtimer hint: timerlat_irq+0x0/0x220 WARNING: CPU: 0 PID: 426 at lib/debugobjects.c:518 debug_print_object+0x7d/0xb0 Modules linked in: CPU: 0 UID: 0 PID: 426 Comm: timerlat/1 Not tainted 6.11.0-rc7+ #45 Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.13.0-1ubuntu1.1 04/01/2014 RIP: 0010:debug_print_object+0x7d/0xb0 ... Call Trace:  \u0026lt;TASK\u0026gt;  ? __warn+0x7c/0x110  ? debug_print_object+0x7d/0xb0  ? report_bug+0xf1/0x1d0  ? prb_read_valid+0x17/0x20  ? handle_bug+0x3f/0x70  ? exc_invalid_op+0x13/0x60  ? asm_exc_invalid_op+0x16/0x20  ? debug_print_object+0x7d/0xb0  ? debug_print_object+0x7d/0xb0  ? __pfx_timerlat_irq+0x10/0x10  __debug_object_init+0x110/0x150  hrtimer_init+0x1d/0x60  timerlat_main+0xab/0x2d0  ? __pfx_timerlat_main+0x10/0x10  kthread+0xb7/0xe0  ? __pfx_kthread+0x10/0x10  ret_from_fork+0x2d/0x40  ? __pfx_kthread+0x10/0x10  ret_from_fork_asm+0x1a/0x30  \u0026lt;/TASK\u0026gt; ```  After tracing the scheduling event, it was discovered that the migration of the \u0026quot;timerlat/1\u0026quot; thread was performed during thread creation. Further analysis confirmed that it is because the CPU online processing for osnoise is implemented through workers, which is asynchronous with the offline processing. When the worker was scheduled to create a thread, the CPU may has already been removed from the cpu_online_mask during the offline process, resulting in the inability to select the right CPU:  T1                       | T2 [CPUHP_ONLINE]           | cpu_device_down() osnoise_hotplug_workfn() |                          |     cpus_write_lock()                          |     takedown_cpu(1)                          |     cpus_write_unlock() [CPUHP_OFFLINE]          |     cpus_read_lock()     |     start_kthread(1)     |     cpus_read_unlock()   |  To fix this, skip online processing if the CPU is already offline.(CVE-2024-49866)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  btrfs: wait for fixup workers before stopping cleaner kthread during umount  During unmount, at close_ctree(), we have the following steps in this order:  1) Park the cleaner kthread - this doesn\u0026apos;t destroy the kthread, it basically    halts its execution (wake ups against it work but do nothing);  2) We stop the cleaner kthread - this results in freeing the respective    struct task_struct;  3) We call btrfs_stop_all_workers() which waits for any jobs running in all    the work queues and then free the work queues.  Syzbot reported a case where a fixup worker resulted in a crash when doing a delayed iput on its inode while attempting to wake up the cleaner at btrfs_add_delayed_iput(), because the task_struct of the cleaner kthread was already freed. This can happen during unmount because we don\u0026apos;t wait for any fixup workers still running before we call kthread_stop() against the cleaner kthread, which stops and free all its resources.  Fix this by waiting for any fixup workers at close_ctree() before we call kthread_stop() against the cleaner and run pending delayed iputs.  The stack traces reported by syzbot were the following:    BUG: KASAN: slab-use-after-free in __lock_acquire+0x77/0x2050 kernel/locking/lockdep.c:5065   Read of size 8 at addr ffff8880272a8a18 by task kworker/u8:3/52    CPU: 1 UID: 0 PID: 52 Comm: kworker/u8:3 Not tainted 6.12.0-rc1-syzkaller #0   Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 09/13/2024   Workqueue: btrfs-fixup btrfs_work_helper   Call Trace:    \u0026lt;TASK\u0026gt;    __dump_stack lib/dump_stack.c:94 [inline]    dump_stack_lvl+0x241/0x360 lib/dump_stack.c:120    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    __lock_acquire+0x77/0x2050 kernel/locking/lockdep.c:5065    lock_acquire+0x1ed/0x550 kernel/locking/lockdep.c:5825    __raw_spin_lock_irqsave include/linux/spinlock_api_smp.h:110 [inline]    _raw_spin_lock_irqsave+0xd5/0x120 kernel/locking/spinlock.c:162    class_raw_spinlock_irqsave_constructor include/linux/spinlock.h:551 [inline]    try_to_wake_up+0xb0/0x1480 kernel/sched/core.c:4154    btrfs_writepage_fixup_worker+0xc16/0xdf0 fs/btrfs/inode.c:2842    btrfs_work_helper+0x390/0xc50 fs/btrfs/async-thread.c:314    process_one_work kernel/workqueue.c:3229 [inline]    process_scheduled_works+0xa63/0x1850 kernel/workqueue.c:3310    worker_thread+0x870/0xd30 kernel/workqueue.c:3391    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;    Allocated by task 2:    kasan_save_stack mm/kasan/common.c:47 [inline]    kasan_save_track+0x3f/0x80 mm/kasan/common.c:68    unpoison_slab_object mm/kasan/common.c:319 [inline]    __kasan_slab_alloc+0x66/0x80 mm/kasan/common.c:345    kasan_slab_alloc include/linux/kasan.h:247 [inline]    slab_post_alloc_hook mm/slub.c:4086 [inline]    slab_alloc_node mm/slub.c:4135 [inline]    kmem_cache_alloc_node_noprof+0x16b/0x320 mm/slub.c:4187    alloc_task_struct_node kernel/fork.c:180 [inline]    dup_task_struct+0x57/0x8c0 kernel/fork.c:1107    copy_process+0x5d1/0x3d50 kernel/fork.c:2206    kernel_clone+0x223/0x880 kernel/fork.c:2787    kernel_thread+0x1bc/0x240 kernel/fork.c:2849    create_kthread kernel/kthread.c:412 [inline]    kthreadd+0x60d/0x810 kernel/kthread.c:765    ret_from_fork+0x4b/0x80 arch/x86/kernel/process.c:147    ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:244    Freed by task 61:    kasan_save_stack mm/kasan/common.c:47 [inline]    kasan_save_track+0x3f/0x80 mm/kasan/common.c:68    kasan_save_free_info+0x40/0x50 mm/kasan/generic.c:579    poison_slab_object mm/kasan/common.c:247 [inline]    __kasan_slab_free+0x59/0x70 mm/kasan/common.c:264    kasan_slab_free include/linux/kasan.h:230 [inline]    slab_free_h ---truncated---(CVE-2024-49867)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  btrfs: fix a NULL pointer dereference when failed to start a new trasacntion  [BUG] Syzbot reported a NULL pointer dereference with the following crash:    FAULT_INJECTION: forcing a failure.    start_transaction+0x830/0x1670 fs/btrfs/transaction.c:676    prepare_to_relocate+0x31f/0x4c0 fs/btrfs/relocation.c:3642    relocate_block_group+0x169/0xd20 fs/btrfs/relocation.c:3678   ...   BTRFS info (device loop0): balance: ended with status: -12   Oops: general protection fault, probably for non-canonical address 0xdffffc00000000cc: 0000 [#1] PREEMPT SMP KASAN NOPTI   KASAN: null-ptr-deref in range [0x0000000000000660-0x0000000000000667]   RIP: 0010:btrfs_update_reloc_root+0x362/0xa80 fs/btrfs/relocation.c:926   Call Trace:    \u0026lt;TASK\u0026gt;    commit_fs_roots+0x2ee/0x720 fs/btrfs/transaction.c:1496    btrfs_commit_transaction+0xfaf/0x3740 fs/btrfs/transaction.c:2430    del_balance_item fs/btrfs/volumes.c:3678 [inline]    reset_balance_state+0x25e/0x3c0 fs/btrfs/volumes.c:3742    btrfs_balance+0xead/0x10c0 fs/btrfs/volumes.c:4574    btrfs_ioctl_balance+0x493/0x7c0 fs/btrfs/ioctl.c:3673    vfs_ioctl fs/ioctl.c:51 [inline]    __do_sys_ioctl fs/ioctl.c:907 [inline]    __se_sys_ioctl+0xf9/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  [CAUSE] The allocation failure happens at the start_transaction() inside prepare_to_relocate(), and during the error handling we call unset_reloc_control(), which makes fs_info-\u0026gt;balance_ctl to be NULL.  Then we continue the error path cleanup in btrfs_balance() by calling reset_balance_state() which will call del_balance_item() to fully delete the balance item in the root tree.  However during the small window between set_reloc_contrl() and unset_reloc_control(), we can have a subvolume tree update and created a reloc_root for that subvolume.  Then we go into the final btrfs_commit_transaction() of del_balance_item(), and into btrfs_update_reloc_root() inside commit_fs_roots().  That function checks if fs_info-\u0026gt;reloc_ctl is in the merge_reloc_tree stage, but since fs_info-\u0026gt;reloc_ctl is NULL, it results a NULL pointer dereference.  [FIX] Just add extra check on fs_info-\u0026gt;reloc_ctl inside btrfs_update_reloc_root(), before checking fs_info-\u0026gt;reloc_ctl-\u0026gt;merge_reloc_tree.  That DEAD_RELOC_TREE handling is to prevent further modification to the reloc tree during merge stage, but since there is no reloc_ctl at all, we do not need to bother that.(CVE-2024-49868)\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: Fix index out of bounds in degamma hardware format translation  Fixes index out of bounds issue in `cm_helper_translate_curve_to_degamma_hw_format` function. The issue could occur when the index \u0026apos;i\u0026apos; exceeds the number of transfer function points (TRANSFER_FUNC_POINTS).  The fix adds a check to ensure \u0026apos;i\u0026apos; is within bounds before accessing the transfer function points. If \u0026apos;i\u0026apos; is out of bounds the function returns false to indicate an error.  Reported by smatch: drivers/gpu/drm/amd/amdgpu/../display/dc/dcn10/dcn10_cm_common.c:594 cm_helper_translate_curve_to_degamma_hw_format() error: buffer overflow \u0026apos;output_tf-\u0026gt;tf_pts.red\u0026apos; 1025 \u0026lt;= s32max drivers/gpu/drm/amd/amdgpu/../display/dc/dcn10/dcn10_cm_common.c:595 cm_helper_translate_curve_to_degamma_hw_format() error: buffer overflow \u0026apos;output_tf-\u0026gt;tf_pts.green\u0026apos; 1025 \u0026lt;= s32max drivers/gpu/drm/amd/amdgpu/../display/dc/dcn10/dcn10_cm_common.c:596 cm_helper_translate_curve_to_degamma_hw_format() error: buffer overflow \u0026apos;output_tf-\u0026gt;tf_pts.blue\u0026apos; 1025 \u0026lt;= s32max(CVE-2024-49894)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  drm/amd/display: Fix index out of bounds in DCN30 degamma hardware format translation  This commit addresses a potential index out of bounds issue in the `cm3_helper_translate_curve_to_degamma_hw_format` function in the DCN30 color  management module. The issue could occur when the index \u0026apos;i\u0026apos; exceeds the  number of transfer function points (TRANSFER_FUNC_POINTS).  The fix adds a check to ensure \u0026apos;i\u0026apos; is within bounds before accessing the transfer function points. If \u0026apos;i\u0026apos; is out of bounds, the function returns false to indicate an error.  Reported by smatch: drivers/gpu/drm/amd/amdgpu/../display/dc/dcn30/dcn30_cm_common.c:338 cm3_helper_translate_curve_to_degamma_hw_format() error: buffer overflow \u0026apos;output_tf-\u0026gt;tf_pts.red\u0026apos; 1025 \u0026lt;= s32max drivers/gpu/drm/amd/amdgpu/../display/dc/dcn30/dcn30_cm_common.c:339 cm3_helper_translate_curve_to_degamma_hw_format() error: buffer overflow \u0026apos;output_tf-\u0026gt;tf_pts.green\u0026apos; 1025 \u0026lt;= s32max drivers/gpu/drm/amd/amdgpu/../display/dc/dcn30/dcn30_cm_common.c:340 cm3_helper_translate_curve_to_degamma_hw_format() error: buffer overflow \u0026apos;output_tf-\u0026gt;tf_pts.blue\u0026apos; 1025 \u0026lt;= s32max(CVE-2024-49895)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  jfs: Fix uninit-value access of new_ea in ea_buffer  syzbot reports that lzo1x_1_do_compress is using uninit-value:  ===================================================== BUG: KMSAN: uninit-value in lzo1x_1_do_compress+0x19f9/0x2510 lib/lzo/lzo1x_compress.c:178  ...  Uninit was stored to memory at:  ea_put fs/jfs/xattr.c:639 [inline]  ...  Local variable ea_buf created at:  __jfs_setxattr+0x5d/0x1ae0 fs/jfs/xattr.c:662  __jfs_xattr_set+0xe6/0x1f0 fs/jfs/xattr.c:934  =====================================================  The reason is ea_buf-\u0026gt;new_ea is not initialized properly.  Fix this by using memset to empty its content at the beginning in ea_get().(CVE-2024-49900)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  jfs: check if leafidx greater than num leaves per dmap tree  syzbot report a out of bounds in dbSplit, it because dmt_leafidx greater than num leaves per dmap tree, add a checking for dmt_leafidx in dbFindLeaf.  Shaggy: Modified sanity check to apply to control pages as well as leaf pages.(CVE-2024-49902)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  jfs: Fix uaf in dbFreeBits  [syzbot reported] ================================================================== BUG: KASAN: slab-use-after-free in __mutex_lock_common kernel/locking/mutex.c:587 [inline] BUG: KASAN: slab-use-after-free in __mutex_lock+0xfe/0xd70 kernel/locking/mutex.c:752 Read of size 8 at addr ffff8880229254b0 by task syz-executor357/5216  CPU: 0 UID: 0 PID: 5216 Comm: syz-executor357 Not tainted 6.11.0-rc3-syzkaller-00156-gd7a5aa4b3c00 #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 06/27/2024 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  __mutex_lock_common kernel/locking/mutex.c:587 [inline]  __mutex_lock+0xfe/0xd70 kernel/locking/mutex.c:752  dbFreeBits+0x7ea/0xd90 fs/jfs/jfs_dmap.c:2390  dbFreeDmap fs/jfs/jfs_dmap.c:2089 [inline]  dbFree+0x35b/0x680 fs/jfs/jfs_dmap.c:409  dbDiscardAG+0x8a9/0xa20 fs/jfs/jfs_dmap.c:1650  jfs_ioc_trim+0x433/0x670 fs/jfs/jfs_discard.c:100  jfs_ioctl+0x2d0/0x3e0 fs/jfs/ioctl.c:131  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  Freed by task 5218:  kasan_save_stack mm/kasan/common.c:47 [inline]  kasan_save_track+0x3f/0x80 mm/kasan/common.c:68  kasan_save_free_info+0x40/0x50 mm/kasan/generic.c:579  poison_slab_object+0xe0/0x150 mm/kasan/common.c:240  __kasan_slab_free+0x37/0x60 mm/kasan/common.c:256  kasan_slab_free include/linux/kasan.h:184 [inline]  slab_free_hook mm/slub.c:2252 [inline]  slab_free mm/slub.c:4473 [inline]  kfree+0x149/0x360 mm/slub.c:4594  dbUnmount+0x11d/0x190 fs/jfs/jfs_dmap.c:278  jfs_mount_rw+0x4ac/0x6a0 fs/jfs/jfs_mount.c:247  jfs_remount+0x3d1/0x6b0 fs/jfs/super.c:454  reconfigure_super+0x445/0x880 fs/super.c:1083  vfs_cmd_reconfigure fs/fsopen.c:263 [inline]  vfs_fsconfig_locked fs/fsopen.c:292 [inline]  __do_sys_fsconfig fs/fsopen.c:473 [inline]  __se_sys_fsconfig+0xb6e/0xf80 fs/fsopen.c:345  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  [Analysis] There are two paths (dbUnmount and jfs_ioc_trim) that generate race condition when accessing bmap, which leads to the occurrence of uaf.  Use the lock s_umount to synchronize them, in order to avoid uaf caused by race condition.(CVE-2024-49903)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  drm/amd/display: Add NULL check for function pointer in dcn20_set_output_transfer_func  This commit adds a null check for the set_output_gamma function pointer in the dcn20_set_output_transfer_func function. Previously, set_output_gamma was being checked for null at line 1030, but then it was being dereferenced without any null check at line 1048. This could potentially lead to a null pointer dereference error 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 at line 1048.(CVE-2024-49911)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  x86/ioapic: Handle allocation failures gracefully  Breno observed panics when using failslab under certain conditions during runtime:     can not alloc irq_pin_list (-1,0,20)    Kernel panic - not syncing: IO-APIC: failed to add irq-pin. Can not proceed     panic+0x4e9/0x590    mp_irqdomain_alloc+0x9ab/0xa80    irq_domain_alloc_irqs_locked+0x25d/0x8d0    __irq_domain_alloc_irqs+0x80/0x110    mp_map_pin_to_irq+0x645/0x890    acpi_register_gsi_ioapic+0xe6/0x150    hpet_open+0x313/0x480  That\u0026apos;s a pointless panic which is a leftover of the historic IO/APIC code which panic\u0026apos;ed during early boot when the interrupt allocation failed.  The only place which might justify panic is the PIT/HPET timer_check() code which tries to figure out whether the timer interrupt is delivered through the IO/APIC. But that code does not require to handle interrupt allocation failures. If the interrupt cannot be allocated then timer delivery fails and it either panics due to that or falls back to legacy mode.  Cure this by removing the panic wrapper around __add_pin_to_irq_node() and making mp_irqdomain_alloc() aware of the failure condition and handle it as any other failure in this function gracefully.(CVE-2024-49927)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  jbd2: stop waiting for space when jbd2_cleanup_journal_tail() returns error  In __jbd2_log_wait_for_space(), we might call jbd2_cleanup_journal_tail() to recover some journal space. But if an error occurs while executing jbd2_cleanup_journal_tail() (e.g., an EIO), we don\u0026apos;t stop waiting for free space right away, we try other branches, and if j_committing_transaction is NULL (i.e., the tid is 0), we will get the following complain:  ============================================ JBD2: I/O error when updating journal superblock for sdd-8. __jbd2_log_wait_for_space: needed 256 blocks and only had 217 space available __jbd2_log_wait_for_space: no way to get more journal space in sdd-8 ------------[ cut here ]------------ WARNING: CPU: 2 PID: 139804 at fs/jbd2/checkpoint.c:109 __jbd2_log_wait_for_space+0x251/0x2e0 Modules linked in: CPU: 2 PID: 139804 Comm: kworker/u8:3 Not tainted 6.6.0+ #1 RIP: 0010:__jbd2_log_wait_for_space+0x251/0x2e0 Call Trace:  \u0026lt;TASK\u0026gt;  add_transaction_credits+0x5d1/0x5e0  start_this_handle+0x1ef/0x6a0  jbd2__journal_start+0x18b/0x340  ext4_dirty_inode+0x5d/0xb0  __mark_inode_dirty+0xe4/0x5d0  generic_update_time+0x60/0x70 [...] ============================================  So only if jbd2_cleanup_journal_tail() returns 1, i.e., there is nothing to clean up at the moment, continue to try to reclaim free space in other ways.  Note that this fix relies on commit 6f6a6fda2945 (\u0026quot;jbd2: fix ocfs2 corrupt when updating journal superblock fails\u0026quot;) to make jbd2_cleanup_journal_tail return the correct error code.(CVE-2024-49959)\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:  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:  drm/amd/display: Fix index out of bounds in DCN30 color transformation  This commit addresses a potential index out of bounds issue in the `cm3_helper_translate_curve_to_hw_format` function in the DCN30 color management module. The issue could occur when the index \u0026apos;i\u0026apos; exceeds the number of transfer function points (TRANSFER_FUNC_POINTS).  The fix adds a check to ensure \u0026apos;i\u0026apos; is within bounds before accessing the transfer function points. If \u0026apos;i\u0026apos; is out of bounds, the function returns false to indicate an error.  drivers/gpu/drm/amd/amdgpu/../display/dc/dcn30/dcn30_cm_common.c:180 cm3_helper_translate_curve_to_hw_format() error: buffer overflow \u0026apos;output_tf-\u0026gt;tf_pts.red\u0026apos; 1025 \u0026lt;= s32max drivers/gpu/drm/amd/amdgpu/../display/dc/dcn30/dcn30_cm_common.c:181 cm3_helper_translate_curve_to_hw_format() error: buffer overflow \u0026apos;output_tf-\u0026gt;tf_pts.green\u0026apos; 1025 \u0026lt;= s32max drivers/gpu/drm/amd/amdgpu/../display/dc/dcn30/dcn30_cm_common.c:182 cm3_helper_translate_curve_to_hw_format() error: buffer overflow \u0026apos;output_tf-\u0026gt;tf_pts.blue\u0026apos; 1025 \u0026lt;= s32max(CVE-2024-49969)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  NFSD: Limit the number of concurrent async COPY operations  Nothing appears to limit the number of concurrent async COPY operations that clients can start. In addition, AFAICT each async COPY can copy an unlimited number of 4MB chunks, so can run for a long time. Thus IMO async COPY can become a DoS vector.  Add a restriction mechanism that bounds the number of concurrent background COPY operations. Start simple and try to be fair -- this patch implements a per-namespace limit.  An async COPY request that occurs while this limit is exceeded gets NFS4ERR_DELAY. The requesting client can choose to send the request again after a delay or fall back to a traditional read/write style copy.  If there is need to make the mechanism more sophisticated, we can visit that in future patches.(CVE-2024-49974)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  i2c: stm32f7: Do not prepare/unprepare clock during runtime suspend/resume  In case there is any sort of clock controller attached to this I2C bus controller, for example Versaclock or even an AIC32x4 I2C codec, then an I2C transfer triggered from the clock controller clk_ops .prepare callback may trigger a deadlock on drivers/clk/clk.c prepare_lock mutex.  This is because the clock controller first grabs the prepare_lock mutex and then performs the prepare operation, including its I2C access. The I2C access resumes this I2C bus controller via .runtime_resume callback, which calls clk_prepare_enable(), which attempts to grab the prepare_lock mutex again and deadlocks.  Since the clock are already prepared since probe() and unprepared in remove(), use simple clk_enable()/clk_disable() calls to enable and disable the clock on runtime suspend and resume, to avoid hitting the prepare_lock mutex.(CVE-2024-49985)\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:  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:  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:  drm/amd/display: Check null pointer before dereferencing se  [WHAT \u0026amp; HOW] se is null checked previously in the same function, indicating it might be null; therefore, it must be checked when used again.  This fixes 1 FORWARD_NULL issue reported by Coverity.(CVE-2024-50049)","status":"published","published":"2024-11-01T11:07:48Z","modified":"2026-08-18T01:18:37.533351967Z","cvss":[{"version":"3.1","score":9.1,"vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:H","level":"critical"}],"updated_at":"2026-11-02T15:52:41.595342Z"},{"id":"OESA-2024-2324","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\niommu/vt-d: Fix double list_add when enabling VMD in scalable mode\r\n\r\nWhen enabling VMD and IOMMU scalable mode, the following kernel panic\ncall trace/kernel log is shown in Eagle Stream platform (Sapphire Rapids\nCPU) during booting:\r\n\r\npci 0000:59:00.5: Adding to iommu group 42\n...\nvmd 0000:59:00.5: PCI host bridge to bus 10000:80\npci 10000:80:01.0: [8086:352a] type 01 class 0x060400\npci 10000:80:01.0: reg 0x10: [mem 0x00000000-0x0001ffff 64bit]\npci 10000:80:01.0: enabling Extended Tags\npci 10000:80:01.0: PME# supported from D0 D3hot D3cold\npci 10000:80:01.0: DMAR: Setup RID2PASID failed\npci 10000:80:01.0: Failed to add to iommu group 42: -16\npci 10000:80:03.0: [8086:352b] type 01 class 0x060400\npci 10000:80:03.0: reg 0x10: [mem 0x00000000-0x0001ffff 64bit]\npci 10000:80:03.0: enabling Extended Tags\npci 10000:80:03.0: PME# supported from D0 D3hot D3cold\n------------[ cut here ]------------\nkernel BUG at lib/list_debug.c:29!\ninvalid opcode: 0000 [#1] PREEMPT SMP NOPTI\nCPU: 0 PID: 7 Comm: kworker/0:1 Not tainted 5.17.0-rc3+ #7\nHardware name: Lenovo ThinkSystem SR650V3/SB27A86647, BIOS ESE101Y-1.00 01/13/2022\nWorkqueue: events work_for_cpu_fn\nRIP: 0010:__list_add_valid.cold+0x26/0x3f\nCode: 9a 4a ab ff 4c 89 c1 48 c7 c7 40 0c d9 9e e8 b9 b1 fe ff 0f\n      0b 48 89 f2 4c 89 c1 48 89 fe 48 c7 c7 f0 0c d9 9e e8 a2 b1\n      fe ff \u0026lt;0f\u0026gt; 0b 48 89 d1 4c 89 c6 4c 89 ca 48 c7 c7 98 0c d9\n      9e e8 8b b1 fe\nRSP: 0000:ff5ad434865b3a40 EFLAGS: 00010246\nRAX: 0000000000000058 RBX: ff4d61160b74b880 RCX: ff4d61255e1fffa8\nRDX: 0000000000000000 RSI: 00000000fffeffff RDI: ffffffff9fd34f20\nRBP: ff4d611d8e245c00 R08: 0000000000000000 R09: ff5ad434865b3888\nR10: ff5ad434865b3880 R11: ff4d61257fdc6fe8 R12: ff4d61160b74b8a0\nR13: ff4d61160b74b8a0 R14: ff4d611d8e245c10 R15: ff4d611d8001ba70\nFS:  0000000000000000(0000) GS:ff4d611d5ea00000(0000) knlGS:0000000000000000\nCS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033\nCR2: ff4d611fa1401000 CR3: 0000000aa0210001 CR4: 0000000000771ef0\nDR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000\nDR3: 0000000000000000 DR6: 00000000fffe07f0 DR7: 0000000000000400\nPKRU: 55555554\nCall Trace:\n \u0026lt;TASK\u0026gt;\n intel_pasid_alloc_table+0x9c/0x1d0\n dmar_insert_one_dev_info+0x423/0x540\n ? device_to_iommu+0x12d/0x2f0\n intel_iommu_attach_device+0x116/0x290\n __iommu_attach_device+0x1a/0x90\n iommu_group_add_device+0x190/0x2c0\n __iommu_probe_device+0x13e/0x250\n iommu_probe_device+0x24/0x150\n iommu_bus_notifier+0x69/0x90\n blocking_notifier_call_chain+0x5a/0x80\n device_add+0x3db/0x7b0\n ? arch_memremap_can_ram_remap+0x19/0x50\n ? memremap+0x75/0x140\n pci_device_add+0x193/0x1d0\n pci_scan_single_device+0xb9/0xf0\n pci_scan_slot+0x4c/0x110\n pci_scan_child_bus_extend+0x3a/0x290\n vmd_enable_domain.constprop.0+0x63e/0x820\n vmd_probe+0x163/0x190\n local_pci_probe+0x42/0x80\n work_for_cpu_fn+0x13/0x20\n process_one_work+0x1e2/0x3b0\n worker_thread+0x1c4/0x3a0\n ? rescuer_thread+0x370/0x370\n kthread+0xc7/0xf0\n ? kthread_complete_and_exit+0x20/0x20\n ret_from_fork+0x1f/0x30\n \u0026lt;/TASK\u0026gt;\nModules linked in:\n---[ end trace 0000000000000000 ]---\n...\nKernel panic - not syncing: Fatal exception\nKernel Offset: 0x1ca00000 from 0xffffffff81000000 (relocation range: 0xffffffff80000000-0xffffffffbfffffff)\n---[ end Kernel panic - not syncing: Fatal exception ]---\r\n\r\nThe following \u0026apos;lspci\u0026apos; output shows devices \u0026apos;10000:80:*\u0026apos; are subdevices of\nthe VMD device 0000:59:00.5:\r\n\r\n  $ lspci\n  ...\n  0000:59:00.5 RAID bus controller: Intel Corporation Volume Management Device NVMe RAID Controller (rev 20)\n  ...\n  10000:80:01.0 PCI bridge: Intel Corporation Device 352a (rev 03)\n  10000:80:03.0 PCI bridge: Intel Corporation Device 352b (rev 03)\n  10000:80:05.0 PCI bridge: Intel Corporation Device 352c (rev 03)\n  10000:80:07.0 PCI bridge: Intel Corporation Device 352d (rev 03)\n  10000:81:00.0 Non-Volatile memory controller: Intel Corporation NVMe Datacenter SSD [3DNAND, Beta Rock Controller]\n  10000:82:00\n---truncated---(CVE-2022-48916)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  udf: Fix preallocation discarding at indirect extent boundary  When preallocation extent is the first one in the extent block, the code would corrupt extent tree header instead. Fix the problem and use udf_delete_aext() for deleting extent to avoid some code duplication.(CVE-2022-48946)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  PCI: mt7621: Add sentinel to quirks table  Current driver is missing a sentinel in the struct soc_device_attribute array, which causes an oops when assessed by the soc_device_match(mt7621_pcie_quirks_match) call.  This was only exposed once the CONFIG_SOC_MT7621 mt7621 soc_dev_attr was fixed to register the SOC as a device, in:  commit 7c18b64bba3b (\u0026quot;mips: ralink: mt7621: do not use kzalloc too early\u0026quot;)  Fix it by adding the required sentinel.(CVE-2022-48952)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  NFC: nci: Bounds check struct nfc_target arrays  While running under CONFIG_FORTIFY_SOURCE=y, syzkaller reported:    memcpy: detected field-spanning write (size 129) of single field \u0026quot;target-\u0026gt;sensf_res\u0026quot; at net/nfc/nci/ntf.c:260 (size 18)  This appears to be a legitimate lack of bounds checking in nci_add_new_protocol(). Add the missing checks.(CVE-2022-48967)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  gpio: amd8111: Fix PCI device reference count leak  for_each_pci_dev() is implemented by pci_get_device(). The comment of pci_get_device() says that it will increase the reference count for the returned pci_dev and also decrease the reference count for the input pci_dev @from if it is not NULL.  If we break for_each_pci_dev() loop with pdev not NULL, we need to call pci_dev_put() to decrease the reference count. Add the missing pci_dev_put() after the \u0026apos;out\u0026apos; label. Since pci_dev_put() can handle NULL input parameter, there is no problem for the \u0026apos;Device not found\u0026apos; branch. For the normal path, add pci_dev_put() in amd_gpio_exit().(CVE-2022-48973)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  can: af_can: fix NULL pointer dereference in can_rcv_filter  Analogue to commit 8aa59e355949 (\u0026quot;can: af_can: fix NULL pointer dereference in can_rx_register()\u0026quot;) we need to check for a missing initialization of ml_priv in the receive path of CAN frames.  Since commit 4e096a18867a (\u0026quot;net: introduce CAN specific pointer in the struct net_device\u0026quot;) the check for dev-\u0026gt;type to be ARPHRD_CAN is not sufficient anymore since bonding or tun netdevices claim to be CAN devices but do not initialize ml_priv accordingly.(CVE-2022-48977)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  mm/gup: fix gup_pud_range() for dax  For dax pud, pud_huge() returns true on x86. So the function works as long as hugetlb is configured. However, dax doesn\u0026apos;t depend on hugetlb. Commit 414fd080d125 (\u0026quot;mm/gup: fix gup_pmd_range() for dax\u0026quot;) fixed devmap-backed huge PMDs, but missed devmap-backed huge PUDs. Fix this as well.  This fixes the below kernel panic:  general protection fault, probably for non-canonical address 0x69e7c000cc478: 0000 [#1] SMP  \u0026lt; snip \u0026gt; Call Trace: \u0026lt;TASK\u0026gt; get_user_pages_fast+0x1f/0x40 iov_iter_get_pages+0xc6/0x3b0 ? mempool_alloc+0x5d/0x170 bio_iov_iter_get_pages+0x82/0x4e0 ? bvec_alloc+0x91/0xc0 ? bio_alloc_bioset+0x19a/0x2a0 blkdev_direct_IO+0x282/0x480 ? __io_complete_rw_common+0xc0/0xc0 ? filemap_range_has_page+0x82/0xc0 generic_file_direct_write+0x9d/0x1a0 ? inode_update_time+0x24/0x30 __generic_file_write_iter+0xbd/0x1e0 blkdev_write_iter+0xb4/0x150 ? io_import_iovec+0x8d/0x340 io_write+0xf9/0x300 io_issue_sqe+0x3c3/0x1d30 ? sysvec_reschedule_ipi+0x6c/0x80 __io_queue_sqe+0x33/0x240 ? fget+0x76/0xa0 io_submit_sqes+0xe6a/0x18d0 ? __fget_light+0xd1/0x100 __x64_sys_io_uring_enter+0x199/0x880 ? __context_tracking_enter+0x1f/0x70 ? irqentry_exit_to_user_mode+0x24/0x30 ? irqentry_exit+0x1d/0x30 ? __context_tracking_exit+0xe/0x70 do_syscall_64+0x3b/0x90 entry_SYSCALL_64_after_hwframe+0x61/0xcb RIP: 0033:0x7fc97c11a7be  \u0026lt; snip \u0026gt; \u0026lt;/TASK\u0026gt; ---[ end trace 48b2e0e67debcaeb ]--- RIP: 0010:internal_get_user_pages_fast+0x340/0x990  \u0026lt; snip \u0026gt; Kernel panic - not syncing: Fatal exception Kernel Offset: disabled(CVE-2022-48986)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  memcg: fix possible use-after-free in memcg_write_event_control()  memcg_write_event_control() accesses the dentry-\u0026gt;d_name of the specified control fd to route the write call.  As a cgroup interface file can\u0026apos;t be renamed, it\u0026apos;s safe to access d_name as long as the specified file is a regular cgroup file.  Also, as these cgroup interface files can\u0026apos;t be removed before the directory, it\u0026apos;s safe to access the parent too.  Prior to 347c4a874710 (\u0026quot;memcg: remove cgroup_event-\u0026gt;cft\u0026quot;), there was a call to __file_cft() which verified that the specified file is a regular cgroupfs file before further accesses.  The cftype pointer returned from __file_cft() was no longer necessary and the commit inadvertently dropped the file type check with it allowing any file to slip through.  With the invarients broken, the d_name and parent accesses can now race against renames and removals of arbitrary files and cause use-after-free\u0026apos;s.  Fix the bug by resurrecting the file type check in __file_cft().  Now that cgroupfs is implemented through kernfs, checking the file operations needs to go through a layer of indirection.  Instead, let\u0026apos;s check the superblock and dentry type.(CVE-2022-48988)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  mm/khugepaged: invoke MMU notifiers in shmem/file collapse paths  Any codepath that zaps page table entries must invoke MMU notifiers to ensure that secondary MMUs (like KVM) don\u0026apos;t keep accessing pages which aren\u0026apos;t mapped anymore.  Secondary MMUs don\u0026apos;t hold their own references to pages that are mirrored over, so failing to notify them can lead to page use-after-free.  I\u0026apos;m marking this as addressing an issue introduced in commit f3f0e1d2150b (\u0026quot;khugepaged: add support of collapse for tmpfs/shmem pages\u0026quot;), but most of the security impact of this only came in commit 27e1f8273113 (\u0026quot;khugepaged: enable collapse pmd for pte-mapped THP\u0026quot;), which actually omitted flushes for the removal of present PTEs, not just for the removal of empty page tables.(CVE-2022-48991)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  ALSA: seq: Fix function prototype mismatch in snd_seq_expand_var_event  With clang\u0026apos;s kernel control flow integrity (kCFI, CONFIG_CFI_CLANG), indirect call targets are validated against the expected function pointer prototype to make sure the call target is valid to help mitigate ROP attacks. If they are not identical, there is a failure at run time, which manifests as either a kernel panic or thread getting killed.  seq_copy_in_user() and seq_copy_in_kernel() did not have prototypes matching snd_seq_dump_func_t. Adjust this and remove the casts. There are not resulting binary output differences.  This was found as a result of Clang\u0026apos;s new -Wcast-function-type-strict flag, which is more sensitive than the simpler -Wcast-function-type, which only checks for type width mismatches.(CVE-2022-48994)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  tracing: Free buffers when a used dynamic event is removed(CVE-2022-49006)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  nilfs2: fix NULL pointer dereference in nilfs_palloc_commit_free_entry()  Syzbot reported a null-ptr-deref bug:   NILFS (loop0): segctord starting. Construction interval = 5 seconds, CP  frequency \u0026lt; 30 seconds  general protection fault, probably for non-canonical address  0xdffffc0000000002: 0000 [#1] PREEMPT SMP KASAN  KASAN: null-ptr-deref in range [0x0000000000000010-0x0000000000000017]  CPU: 1 PID: 3603 Comm: segctord Not tainted  6.1.0-rc2-syzkaller-00105-gb229b6ca5abb #0  Hardware name: Google Compute Engine/Google Compute Engine, BIOS Google  10/11/2022  RIP: 0010:nilfs_palloc_commit_free_entry+0xe5/0x6b0  fs/nilfs2/alloc.c:608  Code: 00 00 00 00 fc ff df 80 3c 02 00 0f 85 cd 05 00 00 48 b8 00 00 00  00 00 fc ff df 4c 8b 73 08 49 8d 7e 10 48 89 fa 48 c1 ea 03 \u0026lt;80\u0026gt; 3c 02  00 0f 85 26 05 00 00 49 8b 46 10 be a6 00 00 00 48 c7 c7  RSP: 0018:ffffc90003dff830 EFLAGS: 00010212  RAX: dffffc0000000000 RBX: ffff88802594e218 RCX: 000000000000000d  RDX: 0000000000000002 RSI: 0000000000002000 RDI: 0000000000000010  RBP: ffff888071880222 R08: 0000000000000005 R09: 000000000000003f  R10: 000000000000000d R11: 0000000000000000 R12: ffff888071880158  R13: ffff88802594e220 R14: 0000000000000000 R15: 0000000000000004  FS:  0000000000000000(0000) GS:ffff8880b9b00000(0000)  knlGS:0000000000000000  CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033  CR2: 00007fb1c08316a8 CR3: 0000000018560000 CR4: 0000000000350ee0  Call Trace:   \u0026lt;TASK\u0026gt;   nilfs_dat_commit_free fs/nilfs2/dat.c:114 [inline]   nilfs_dat_commit_end+0x464/0x5f0 fs/nilfs2/dat.c:193   nilfs_dat_commit_update+0x26/0x40 fs/nilfs2/dat.c:236   nilfs_btree_commit_update_v+0x87/0x4a0 fs/nilfs2/btree.c:1940   nilfs_btree_commit_propagate_v fs/nilfs2/btree.c:2016 [inline]   nilfs_btree_propagate_v fs/nilfs2/btree.c:2046 [inline]   nilfs_btree_propagate+0xa00/0xd60 fs/nilfs2/btree.c:2088   nilfs_bmap_propagate+0x73/0x170 fs/nilfs2/bmap.c:337   nilfs_collect_file_data+0x45/0xd0 fs/nilfs2/segment.c:568   nilfs_segctor_apply_buffers+0x14a/0x470 fs/nilfs2/segment.c:1018   nilfs_segctor_scan_file+0x3f4/0x6f0 fs/nilfs2/segment.c:1067   nilfs_segctor_collect_blocks fs/nilfs2/segment.c:1197 [inline]   nilfs_segctor_collect fs/nilfs2/segment.c:1503 [inline]   nilfs_segctor_do_construct+0x12fc/0x6af0 fs/nilfs2/segment.c:2045   nilfs_segctor_construct+0x8e3/0xb30 fs/nilfs2/segment.c:2379   nilfs_segctor_thread_construct fs/nilfs2/segment.c:2487 [inline]   nilfs_segctor_thread+0x3c3/0xf30 fs/nilfs2/segment.c:2570   kthread+0x2e4/0x3a0 kernel/kthread.c:376   ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:306   \u0026lt;/TASK\u0026gt;  ...  If DAT metadata file is corrupted on disk, there is a case where req-\u0026gt;pr_desc_bh is NULL and blocknr is 0 at nilfs_dat_commit_end() during a b-tree operation that cascadingly updates ancestor nodes of the b-tree, because nilfs_dat_commit_alloc() for a lower level block can initialize the blocknr on the same DAT entry between nilfs_dat_prepare_end() and nilfs_dat_commit_end().  If this happens, nilfs_dat_commit_end() calls nilfs_dat_commit_free() without valid buffer heads in req-\u0026gt;pr_desc_bh and req-\u0026gt;pr_bitmap_bh, and causes the NULL pointer dereference above in nilfs_palloc_commit_free_entry() function, which leads to a crash.  Fix this by adding a NULL check on req-\u0026gt;pr_desc_bh and req-\u0026gt;pr_bitmap_bh before nilfs_palloc_commit_free_entry() in nilfs_dat_commit_free().  This also calls nilfs_error() in that case to notify that there is a fatal flaw in the filesystem metadata and prevent further operations.(CVE-2022-49007)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  net: ethernet: nixge: fix NULL dereference  In function nixge_hw_dma_bd_release() dereference of NULL pointer priv-\u0026gt;rx_bd_v is possible for the case of its allocation failure in nixge_hw_dma_bd_init().  Move for() loop with priv-\u0026gt;rx_bd_v dereference under the check for its validity.  Found by Linux Verification Center (linuxtesting.org) with SVACE.(CVE-2022-49019)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  hwmon: (ibmpex) Fix possible UAF when ibmpex_register_bmc() fails  Smatch report warning as follows:  drivers/hwmon/ibmpex.c:509 ibmpex_register_bmc() warn:   \u0026apos;\u0026amp;data-\u0026gt;list\u0026apos; not removed from list  If ibmpex_find_sensors() fails in ibmpex_register_bmc(), data will be freed, but data-\u0026gt;list will not be removed from driver_data.bmc_data, then list traversal may cause UAF.  Fix by removeing it from driver_data.bmc_data before free().(CVE-2022-49029)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  libbpf: Handle size overflow for ringbuf mmap  The maximum size of ringbuf is 2GB on x86-64 host, so 2 * max_entries will overflow u32 when mapping producer page and data pages. Only casting max_entries to size_t is not enough, because for 32-bits application on 64-bits kernel the size of read-only mmap region also could overflow size_t.  So fixing it by casting the size of read-only mmap region into a __u64 and checking whether or not there will be overflow during mmap.(CVE-2022-49030)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  btrfs: qgroup: fix sleep from invalid context bug in btrfs_qgroup_inherit()  Syzkaller reported BUG as follows:    BUG: sleeping function called from invalid context at        include/linux/sched/mm.h:274   Call Trace:    \u0026lt;TASK\u0026gt;    dump_stack_lvl+0xcd/0x134    __might_resched.cold+0x222/0x26b    kmem_cache_alloc+0x2e7/0x3c0    update_qgroup_limit_item+0xe1/0x390    btrfs_qgroup_inherit+0x147b/0x1ee0    create_subvol+0x4eb/0x1710    btrfs_mksubvol+0xfe5/0x13f0    __btrfs_ioctl_snap_create+0x2b0/0x430    btrfs_ioctl_snap_create_v2+0x25a/0x520    btrfs_ioctl+0x2a1c/0x5ce0    __x64_sys_ioctl+0x193/0x200    do_syscall_64+0x35/0x80  Fix this by calling qgroup_dirty() on @dstqgroup, and update limit item in btrfs_run_qgroups() later outside of the spinlock context.(CVE-2022-49033)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nmedia: imon: fix access to invalid resource for the second interface\r\n\r\nimon driver probes two USB interfaces, and at the probe of the second\ninterface, the driver assumes blindly that the first interface got\nbound with the same imon driver.  It\u0026apos;s usually true, but it\u0026apos;s still\npossible that the first interface is bound with another driver via a\nmalformed descriptor.  Then it may lead to a memory corruption, as\nspotted by syzkaller; imon driver accesses the data from drvdata as\nstruct imon_context object although it\u0026apos;s a completely different one\nthat was assigned by another driver.\r\n\r\nThis patch adds a sanity check -- whether the first interface is\nreally bound with the imon driver or not -- for avoiding the problem\nabove at the probe time.(CVE-2023-52754)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nusb: dwc2: fix possible NULL pointer dereference caused by driver concurrency\r\n\r\nIn _dwc2_hcd_urb_enqueue(), \u0026quot;urb-\u0026gt;hcpriv = NULL\u0026quot; is executed without\nholding the lock \u0026quot;hsotg-\u0026gt;lock\u0026quot;. In _dwc2_hcd_urb_dequeue():\r\n\r\n    spin_lock_irqsave(\u0026amp;hsotg-\u0026gt;lock, flags);\n    ...\n\tif (!urb-\u0026gt;hcpriv) {\n\t\tdev_dbg(hsotg-\u0026gt;dev, \u0026quot;## urb-\u0026gt;hcpriv is NULL ##\\n\u0026quot;);\n\t\tgoto out;\n\t}\n    rc = dwc2_hcd_urb_dequeue(hsotg, urb-\u0026gt;hcpriv); // Use urb-\u0026gt;hcpriv\n    ...\nout:\n    spin_unlock_irqrestore(\u0026amp;hsotg-\u0026gt;lock, flags);\r\n\r\nWhen _dwc2_hcd_urb_enqueue() and _dwc2_hcd_urb_dequeue() are\nconcurrently executed, the NULL check of \u0026quot;urb-\u0026gt;hcpriv\u0026quot; can be executed\nbefore \u0026quot;urb-\u0026gt;hcpriv = NULL\u0026quot;. After urb-\u0026gt;hcpriv is NULL, it can be used\nin the function call to dwc2_hcd_urb_dequeue(), which can cause a NULL\npointer dereference.\r\n\r\nThis possible bug is found by an experimental static analysis tool\ndeveloped by myself. This tool analyzes the locking APIs to extract\nfunction pairs that can be concurrently executed, and then analyzes the\ninstructions in the paired functions to identify possible concurrency\nbugs including data races and atomicity violations. The above possible\nbug is reported, when my tool analyzes the source code of Linux 6.5.\r\n\r\nTo fix this possible bug, \u0026quot;urb-\u0026gt;hcpriv = NULL\u0026quot; should be executed with\nholding the lock \u0026quot;hsotg-\u0026gt;lock\u0026quot;. After using this patch, my tool never\nreports the possible bug, with the kernelconfiguration allyesconfig for\nx86_64. Because I have no associated hardware, I cannot test the patch\nin runtime testing, and just verify it according to the code logic.(CVE-2023-52855)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  ntb: intel: Fix the NULL vs IS_ERR() bug for debugfs_create_dir()  The debugfs_create_dir() function returns error pointers. It never returns NULL. So use IS_ERR() to check it.(CVE-2023-52917)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  media: pci: cx23885: check cx23885_vdev_init() return  cx23885_vdev_init() can return a NULL pointer, but that pointer is used in the next line without a check.  Add a NULL pointer check and go to the error unwind if it is NULL.(CVE-2023-52918)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  nfc: nci: fix possible NULL pointer dereference in send_acknowledge()  Handle memory allocation failure from nci_skb_alloc() (calling alloc_skb()) to avoid possible NULL pointer dereference.(CVE-2023-52919)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nscsi: Revert \u0026quot;scsi: fcoe: Fix potential deadlock on \u0026amp;fip-\u0026gt;ctlr_lock\u0026quot;\r\n\r\nThis reverts commit 1a1975551943f681772720f639ff42fbaa746212.\r\n\r\nThis commit causes interrupts to be lost for FCoE devices, since it changed\nsping locks from \u0026quot;bh\u0026quot; to \u0026quot;irqsave\u0026quot;.\r\n\r\nInstead, a work queue should be used, and will be addressed in a separate\ncommit.(CVE-2024-26917)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nof: module: prevent NULL pointer dereference in vsnprintf()\r\n\r\nIn of_modalias(), we can get passed the str and len parameters which would\ncause a kernel oops in vsnprintf() since it only allows passing a NULL ptr\nwhen the length is also 0. Also, we need to filter out the negative values\nof the len parameter as these will result in a really huge buffer since\nsnprintf() takes size_t parameter while ours is ssize_t...\r\n\r\nFound by Linux Verification Center (linuxtesting.org) with the Svace static\nanalysis tool.(CVE-2024-35878)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\ndma: xilinx_dpdma: Fix locking\r\n\r\nThere are several places where either chan-\u0026gt;lock or chan-\u0026gt;vchan.lock was\nnot held. Add appropriate locking. This fixes lockdep warnings like\r\n\r\n[   31.077578] ------------[ cut here ]------------\n[   31.077831] WARNING: CPU: 2 PID: 40 at drivers/dma/xilinx/xilinx_dpdma.c:834 xilinx_dpdma_chan_queue_transfer+0x274/0x5e0\n[   31.077953] Modules linked in:\n[   31.078019] CPU: 2 PID: 40 Comm: kworker/u12:1 Not tainted 6.6.20+ #98\n[   31.078102] Hardware name: xlnx,zynqmp (DT)\n[   31.078169] Workqueue: events_unbound deferred_probe_work_func\n[   31.078272] pstate: 600000c5 (nZCv daIF -PAN -UAO -TCO -DIT -SSBS BTYPE=--)\n[   31.078377] pc : xilinx_dpdma_chan_queue_transfer+0x274/0x5e0\n[   31.078473] lr : xilinx_dpdma_chan_queue_transfer+0x270/0x5e0\n[   31.078550] sp : ffffffc083bb2e10\n[   31.078590] x29: ffffffc083bb2e10 x28: 0000000000000000 x27: ffffff880165a168\n[   31.078754] x26: ffffff880164e920 x25: ffffff880164eab8 x24: ffffff880164d480\n[   31.078920] x23: ffffff880165a148 x22: ffffff880164e988 x21: 0000000000000000\n[   31.079132] x20: ffffffc082aa3000 x19: ffffff880164e880 x18: 0000000000000000\n[   31.079295] x17: 0000000000000000 x16: 0000000000000000 x15: 0000000000000000\n[   31.079453] x14: 0000000000000000 x13: ffffff8802263dc0 x12: 0000000000000001\n[   31.079613] x11: 0001ffc083bb2e34 x10: 0001ff880164e98f x9 : 0001ffc082aa3def\n[   31.079824] x8 : 0001ffc082aa3dec x7 : 0000000000000000 x6 : 0000000000000516\n[   31.079982] x5 : ffffffc7f8d43000 x4 : ffffff88003c9c40 x3 : ffffffffffffffff\n[   31.080147] x2 : ffffffc7f8d43000 x1 : 00000000000000c0 x0 : 0000000000000000\n[   31.080307] Call trace:\n[   31.080340]  xilinx_dpdma_chan_queue_transfer+0x274/0x5e0\n[   31.080518]  xilinx_dpdma_issue_pending+0x11c/0x120\n[   31.080595]  zynqmp_disp_layer_update+0x180/0x3ac\n[   31.080712]  zynqmp_dpsub_plane_atomic_update+0x11c/0x21c\n[   31.080825]  drm_atomic_helper_commit_planes+0x20c/0x684\n[   31.080951]  drm_atomic_helper_commit_tail+0x5c/0xb0\n[   31.081139]  commit_tail+0x234/0x294\n[   31.081246]  drm_atomic_helper_commit+0x1f8/0x210\n[   31.081363]  drm_atomic_commit+0x100/0x140\n[   31.081477]  drm_client_modeset_commit_atomic+0x318/0x384\n[   31.081634]  drm_client_modeset_commit_locked+0x8c/0x24c\n[   31.081725]  drm_client_modeset_commit+0x34/0x5c\n[   31.081812]  __drm_fb_helper_restore_fbdev_mode_unlocked+0x104/0x168\n[   31.081899]  drm_fb_helper_set_par+0x50/0x70\n[   31.081971]  fbcon_init+0x538/0xc48\n[   31.082047]  visual_init+0x16c/0x23c\n[   31.082207]  do_bind_con_driver.isra.0+0x2d0/0x634\n[   31.082320]  do_take_over_console+0x24c/0x33c\n[   31.082429]  do_fbcon_takeover+0xbc/0x1b0\n[   31.082503]  fbcon_fb_registered+0x2d0/0x34c\n[   31.082663]  register_framebuffer+0x27c/0x38c\n[   31.082767]  __drm_fb_helper_initial_config_and_unlock+0x5c0/0x91c\n[   31.082939]  drm_fb_helper_initial_config+0x50/0x74\n[   31.083012]  drm_fbdev_dma_client_hotplug+0xb8/0x108\n[   31.083115]  drm_client_register+0xa0/0xf4\n[   31.083195]  drm_fbdev_dma_setup+0xb0/0x1cc\n[   31.083293]  zynqmp_dpsub_drm_init+0x45c/0x4e0\n[   31.083431]  zynqmp_dpsub_probe+0x444/0x5e0\n[   31.083616]  platform_probe+0x8c/0x13c\n[   31.083713]  really_probe+0x258/0x59c\n[   31.083793]  __driver_probe_device+0xc4/0x224\n[   31.083878]  driver_probe_device+0x70/0x1c0\n[   31.083961]  __device_attach_driver+0x108/0x1e0\n[   31.084052]  bus_for_each_drv+0x9c/0x100\n[   31.084125]  __device_attach+0x100/0x298\n[   31.084207]  device_initial_probe+0x14/0x20\n[   31.084292]  bus_probe_device+0xd8/0xdc\n[   31.084368]  deferred_probe_work_func+0x11c/0x180\n[   31.084451]  process_one_work+0x3ac/0x988\n[   31.084643]  worker_thread+0x398/0x694\n[   31.084752]  kthread+0x1bc/0x1c0\n[   31.084848]  ret_from_fork+0x10/0x20\n[   31.084932] irq event stamp: 64549\n[   31.084970] hardirqs last  enabled at (64548): [\u0026lt;ffffffc081adf35c\u0026gt;] _raw_spin_unlock_irqrestore+0x80/0x90\n[   31.085157]\n---truncated---(CVE-2024-35990)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nnetfilter: nfnetlink_queue: acquire rcu_read_lock() in instance_destroy_rcu()\r\n\r\nsyzbot reported that nf_reinject() could be called without rcu_read_lock() :\r\n\r\nWARNING: suspicious RCU usage\n6.9.0-rc7-syzkaller-02060-g5c1672705a1a #0 Not tainted\r\n\r\nnet/netfilter/nfnetlink_queue.c:263 suspicious rcu_dereference_check() usage!\r\n\r\nother info that might help us debug this:\r\n\r\nrcu_scheduler_active = 2, debug_locks = 1\n2 locks held by syz-executor.4/13427:\n  #0: ffffffff8e334f60 (rcu_callback){....}-{0:0}, at: rcu_lock_acquire include/linux/rcupdate.h:329 [inline]\n  #0: ffffffff8e334f60 (rcu_callback){....}-{0:0}, at: rcu_do_batch kernel/rcu/tree.c:2190 [inline]\n  #0: ffffffff8e334f60 (rcu_callback){....}-{0:0}, at: rcu_core+0xa86/0x1830 kernel/rcu/tree.c:2471\n  #1: ffff88801ca92958 (\u0026amp;inst-\u0026gt;lock){+.-.}-{2:2}, at: spin_lock_bh include/linux/spinlock.h:356 [inline]\n  #1: ffff88801ca92958 (\u0026amp;inst-\u0026gt;lock){+.-.}-{2:2}, at: nfqnl_flush net/netfilter/nfnetlink_queue.c:405 [inline]\n  #1: ffff88801ca92958 (\u0026amp;inst-\u0026gt;lock){+.-.}-{2:2}, at: instance_destroy_rcu+0x30/0x220 net/netfilter/nfnetlink_queue.c:172\r\n\r\nstack backtrace:\nCPU: 0 PID: 13427 Comm: syz-executor.4 Not tainted 6.9.0-rc7-syzkaller-02060-g5c1672705a1a #0\nHardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 04/02/2024\nCall Trace:\n \u0026lt;IRQ\u0026gt;\n  __dump_stack lib/dump_stack.c:88 [inline]\n  dump_stack_lvl+0x241/0x360 lib/dump_stack.c:114\n  lockdep_rcu_suspicious+0x221/0x340 kernel/locking/lockdep.c:6712\n  nf_reinject net/netfilter/nfnetlink_queue.c:323 [inline]\n  nfqnl_reinject+0x6ec/0x1120 net/netfilter/nfnetlink_queue.c:397\n  nfqnl_flush net/netfilter/nfnetlink_queue.c:410 [inline]\n  instance_destroy_rcu+0x1ae/0x220 net/netfilter/nfnetlink_queue.c:172\n  rcu_do_batch kernel/rcu/tree.c:2196 [inline]\n  rcu_core+0xafd/0x1830 kernel/rcu/tree.c:2471\n  handle_softirqs+0x2d6/0x990 kernel/softirq.c:554\n  __do_softirq kernel/softirq.c:588 [inline]\n  invoke_softirq kernel/softirq.c:428 [inline]\n  __irq_exit_rcu+0xf4/0x1c0 kernel/softirq.c:637\n  irq_exit_rcu+0x9/0x30 kernel/softirq.c:649\n  instr_sysvec_apic_timer_interrupt arch/x86/kernel/apic/apic.c:1043 [inline]\n  sysvec_apic_timer_interrupt+0xa6/0xc0 arch/x86/kernel/apic/apic.c:1043\n \u0026lt;/IRQ\u0026gt;\n \u0026lt;TASK\u0026gt;(CVE-2024-36286)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nsoundwire: cadence: fix invalid PDI offset\r\n\r\nFor some reason, we add an offset to the PDI, presumably to skip the\nPDI0 and PDI1 which are reserved for BPT.\r\n\r\nThis code is however completely wrong and leads to an out-of-bounds\naccess. We were just lucky so far since we used only a couple of PDIs\nand remained within the PDI array bounds.\r\n\r\nA Fixes: tag is not provided since there are no known platforms where\nthe out-of-bounds would be accessed, and the initial code had problems\nas well.\r\n\r\nA follow-up patch completely removes this useless offset.(CVE-2024-38635)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nriscv: prevent pt_regs corruption for secondary idle threads\r\n\r\nTop of the kernel thread stack should be reserved for pt_regs. However\nthis is not the case for the idle threads of the secondary boot harts.\nTheir stacks overlap with their pt_regs, so both may get corrupted.\r\n\r\nSimilar issue has been fixed for the primary hart, see c7cdd96eca28\n(\u0026quot;riscv: prevent stack corruption by reserving task_pt_regs(p) early\u0026quot;).\nHowever that fix was not propagated to the secondary harts. The problem\nhas been noticed in some CPU hotplug tests with V enabled. The function\nsmp_callin stored several registers on stack, corrupting top of pt_regs\nstructure including status field. As a result, kernel attempted to save\nor restore inexistent V context.(CVE-2024-38667)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nocfs2: add bounds checking to ocfs2_check_dir_entry()\r\n\r\nThis adds sanity checks for ocfs2_dir_entry to make sure all members of\nocfs2_dir_entry don\u0026apos;t stray beyond valid memory region.(CVE-2024-41015)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nnvmet: fix a possible leak when destroy a ctrl during qp establishment\r\n\r\nIn nvmet_sq_destroy we capture sq-\u0026gt;ctrl early and if it is non-NULL we\nknow that a ctrl was allocated (in the admin connect request handler)\nand we need to release pending AERs, clear ctrl-\u0026gt;sqs and sq-\u0026gt;ctrl\n(for nvme-loop primarily), and drop the final reference on the ctrl.\r\n\r\nHowever, a small window is possible where nvmet_sq_destroy starts (as\na result of the client giving up and disconnecting) concurrently with\nthe nvme admin connect cmd (which may be in an early stage). But *before*\nkill_and_confirm of sq-\u0026gt;ref (i.e. the admin connect managed to get an sq\nlive reference). In this case, sq-\u0026gt;ctrl was allocated however after it was\ncaptured in a local variable in nvmet_sq_destroy.\nThis prevented the final reference drop on the ctrl.\r\n\r\nSolve this by re-capturing the sq-\u0026gt;ctrl after all inflight request has\ncompleted, where for sure sq-\u0026gt;ctrl reference is final, and move forward\nbased on that.\r\n\r\nThis issue was observed in an environment with many hosts connecting\nmultiple ctrls simoutanuosly, creating a delay in allocating a ctrl\nleading up to this race window.(CVE-2024-42152)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\ndev/parport: fix the array out-of-bounds risk\r\n\r\nFixed array out-of-bounds issues caused by sprintf\nby replacing it with snprintf for safer data copying,\nensuring the destination buffer is not overflowed.\r\n\r\nBelow is the stack trace I encountered during the actual issue:\r\n\r\n[ 66.575408s] [pid:5118,cpu4,QThread,4]Kernel panic - not syncing: stack-protector:\nKernel stack is corrupted in: do_hardware_base_addr+0xcc/0xd0 [parport]\n[ 66.575408s] [pid:5118,cpu4,QThread,5]CPU: 4 PID: 5118 Comm:\nQThread Tainted: G S W O 5.10.97-arm64-desktop #7100.57021.2\n[ 66.575439s] [pid:5118,cpu4,QThread,6]TGID: 5087 Comm: EFileApp\n[ 66.575439s] [pid:5118,cpu4,QThread,7]Hardware name: HUAWEI HUAWEI QingYun\nPGUX-W515x-B081/SP1PANGUXM, BIOS 1.00.07 04/29/2024\n[ 66.575439s] [pid:5118,cpu4,QThread,8]Call trace:\n[ 66.575469s] [pid:5118,cpu4,QThread,9] dump_backtrace+0x0/0x1c0\n[ 66.575469s] [pid:5118,cpu4,QThread,0] show_stack+0x14/0x20\n[ 66.575469s] [pid:5118,cpu4,QThread,1] dump_stack+0xd4/0x10c\n[ 66.575500s] [pid:5118,cpu4,QThread,2] panic+0x1d8/0x3bc\n[ 66.575500s] [pid:5118,cpu4,QThread,3] __stack_chk_fail+0x2c/0x38\n[ 66.575500s] [pid:5118,cpu4,QThread,4] do_hardware_base_addr+0xcc/0xd0 [parport](CVE-2024-42301)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nwifi: virt_wifi: avoid reporting connection success with wrong SSID\r\n\r\nWhen user issues a connection with a different SSID than the one\nvirt_wifi has advertised, the __cfg80211_connect_result() will\ntrigger the warning: WARN_ON(bss_not_found).\r\n\r\nThe issue is because the connection code in virt_wifi does not\ncheck the SSID from user space (it only checks the BSSID), and\nvirt_wifi will call cfg80211_connect_result() with WLAN_STATUS_SUCCESS\neven if the SSID is different from the one virt_wifi has advertised.\nEventually cfg80211 won\u0026apos;t be able to find the cfg80211_bss and generate\nthe warning.\r\n\r\nFixed it by checking the SSID (from user space) in the connection code.(CVE-2024-43841)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\njfs: Fix array-index-out-of-bounds in diFree(CVE-2024-43858)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\ndrm/nouveau: prime: fix refcount underflow\r\n\r\nCalling nouveau_bo_ref() on a nouveau_bo without initializing it (and\nhence the backing ttm_bo) leads to a refcount underflow.\r\n\r\nInstead of calling nouveau_bo_ref() in the unwind path of\ndrm_gem_object_init(), clean things up manually.\r\n\r\n(cherry picked from commit 1b93f3e89d03cfc576636e195466a0d728ad8de5)(CVE-2024-43867)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\ndevres: Fix memory leakage caused by driver API devm_free_percpu()\r\n\r\nIt will cause memory leakage when use driver API devm_free_percpu()\nto free memory allocated by devm_alloc_percpu(), fixed by using\ndevres_release() instead of devres_destroy() within devm_free_percpu().(CVE-2024-43871)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\ndrm/client: fix null pointer dereference in drm_client_modeset_probe\r\n\r\nIn drm_client_modeset_probe(), the return value of drm_mode_duplicate() is\nassigned to modeset-\u0026gt;mode, which will lead to a possible NULL pointer\ndereference on failure of drm_mode_duplicate(). Add a check to avoid npd.(CVE-2024-43894)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nusb: dwc3: core: Prevent USB core invalid event buffer address access\r\n\r\nThis commit addresses an issue where the USB core could access an\ninvalid event buffer address during runtime suspend, potentially causing\nSMMU faults and other memory issues in Exynos platforms. The problem\narises from the following sequence.\n        1. In dwc3_gadget_suspend, there is a chance of a timeout when\n        moving the USB core to the halt state after clearing the\n        run/stop bit by software.\n        2. In dwc3_core_exit, the event buffer is cleared regardless of\n        the USB core\u0026apos;s status, which may lead to an SMMU faults and\n        other memory issues. if the USB core tries to access the event\n        buffer address.\r\n\r\nTo prevent this hardware quirk on Exynos platforms, this commit ensures\nthat the event buffer address is not cleared by software  when the USB\ncore is active during runtime suspend by checking its status before\nclearing the buffer address.(CVE-2024-46675)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nsoc: qcom: cmd-db: Map shared memory as WC, not WB\r\n\r\nLinux does not write into cmd-db region. This region of memory is write\nprotected by XPU. XPU may sometime falsely detect clean cache eviction\nas \u0026quot;write\u0026quot; into the write protected region leading to secure interrupt\nwhich causes an endless loop somewhere in Trust Zone.\r\n\r\nThe only reason it is working right now is because Qualcomm Hypervisor\nmaps the same region as Non-Cacheable memory in Stage 2 translation\ntables. The issue manifests if we want to use another hypervisor (like\nXen or KVM), which does not know anything about those specific mappings.\r\n\r\nChanging the mapping of cmd-db memory from MEMREMAP_WB to MEMREMAP_WT/WC\nremoves dependency on correct mappings in Stage 2 tables. This patch\nfixes the issue by updating the mapping to MEMREMAP_WC.\r\n\r\nI tested this on SA8155P with Xen.(CVE-2024-46689)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\ndrm/amdgpu: fix mc_data out-of-bounds read warning\r\n\r\nClear warning that read mc_data[i-1] may out-of-bounds.(CVE-2024-46722)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\ndrm/amdgpu: Fix out-of-bounds read of df_v1_7_channel_number\r\n\r\nCheck the fb_channel_number range to avoid the array out-of-bounds\nread error(CVE-2024-46724)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nhwmon: (nct6775-core) Fix underflows seen when writing limit attributes\r\n\r\nDIV_ROUND_CLOSEST() after kstrtol() results in an underflow if a large\nnegative number such as -9223372036854775808 is provided by the user.\nFix it by reordering clamp_val() and DIV_ROUND_CLOSEST() operations.(CVE-2024-46757)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\ndrm/amd/display: added NULL check at start of dc_validate_stream\r\n\r\n[Why]\nprevent invalid memory access\r\n\r\n[How]\ncheck if dc and stream are NULL(CVE-2024-46802)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nKVM: x86: Acquire kvm-\u0026gt;srcu when handling KVM_SET_VCPU_EVENTS\r\n\r\nGrab kvm-\u0026gt;srcu when processing KVM_SET_VCPU_EVENTS, as KVM will forcibly\nleave nested VMX/SVM if SMM mode is being toggled, and leaving nested VMX\nreads guest memory.\r\n\r\nNote, kvm_vcpu_ioctl_x86_set_vcpu_events() can also be called from KVM_RUN\nvia sync_regs(), which already holds SRCU.  I.e. trying to precisely use\nkvm_vcpu_srcu_read_lock() around the problematic SMM code would cause\nproblems.  Acquiring SRCU isn\u0026apos;t all that expensive, so for simplicity,\ngrab it unconditionally for KVM_SET_VCPU_EVENTS.\r\n\r\n =============================\n WARNING: suspicious RCU usage\n 6.10.0-rc7-332d2c1d713e-next-vm #552 Not tainted\n -----------------------------\n include/linux/kvm_host.h:1027 suspicious rcu_dereference_check() usage!\r\n\r\n other info that might help us debug this:\r\n\r\n rcu_scheduler_active = 2, debug_locks = 1\n 1 lock held by repro/1071:\n  #0: ffff88811e424430 (\u0026amp;vcpu-\u0026gt;mutex){+.+.}-{3:3}, at: kvm_vcpu_ioctl+0x7d/0x970 [kvm]\r\n\r\n stack backtrace:\n CPU: 15 PID: 1071 Comm: repro Not tainted 6.10.0-rc7-332d2c1d713e-next-vm #552\n Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 0.0.0 02/06/2015\n Call Trace:\n  \u0026lt;TASK\u0026gt;\n  dump_stack_lvl+0x7f/0x90\n  lockdep_rcu_suspicious+0x13f/0x1a0\n  kvm_vcpu_gfn_to_memslot+0x168/0x190 [kvm]\n  kvm_vcpu_read_guest+0x3e/0x90 [kvm]\n  nested_vmx_load_msr+0x6b/0x1d0 [kvm_intel]\n  load_vmcs12_host_state+0x432/0xb40 [kvm_intel]\n  vmx_leave_nested+0x30/0x40 [kvm_intel]\n  kvm_vcpu_ioctl_x86_set_vcpu_events+0x15d/0x2b0 [kvm]\n  kvm_arch_vcpu_ioctl+0x1107/0x1750 [kvm]\n  ? mark_held_locks+0x49/0x70\n  ? kvm_vcpu_ioctl+0x7d/0x970 [kvm]\n  ? kvm_vcpu_ioctl+0x497/0x970 [kvm]\n  kvm_vcpu_ioctl+0x497/0x970 [kvm]\n  ? lock_acquire+0xba/0x2d0\n  ? find_held_lock+0x2b/0x80\n  ? do_user_addr_fault+0x40c/0x6f0\n  ? lock_release+0xb7/0x270\n  __x64_sys_ioctl+0x82/0xb0\n  do_syscall_64+0x6c/0x170\n  entry_SYSCALL_64_after_hwframe+0x4b/0x53\n RIP: 0033:0x7ff11eb1b539\n  \u0026lt;/TASK\u0026gt;(CVE-2024-46830)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nspi: nxp-fspi: fix the KASAN report out-of-bounds bug\r\n\r\nChange the memcpy length to fix the out-of-bounds issue when writing the\ndata that is not 4 byte aligned to TX FIFO.\r\n\r\nTo reproduce the issue, write 3 bytes data to NOR chip.\r\n\r\ndd if=3b of=/dev/mtd0\n[   36.926103] ==================================================================\n[   36.933409] BUG: KASAN: slab-out-of-bounds in nxp_fspi_exec_op+0x26ec/0x2838\n[   36.940514] Read of size 4 at addr ffff00081037c2a0 by task dd/455\n[   36.946721]\n[   36.948235] CPU: 3 UID: 0 PID: 455 Comm: dd Not tainted 6.11.0-rc5-gc7b0e37c8434 #1070\n[   36.956185] Hardware name: Freescale i.MX8QM MEK (DT)\n[   36.961260] Call trace:\n[   36.963723]  dump_backtrace+0x90/0xe8\n[   36.967414]  show_stack+0x18/0x24\n[   36.970749]  dump_stack_lvl+0x78/0x90\n[   36.974451]  print_report+0x114/0x5cc\n[   36.978151]  kasan_report+0xa4/0xf0\n[   36.981670]  __asan_report_load_n_noabort+0x1c/0x28\n[   36.986587]  nxp_fspi_exec_op+0x26ec/0x2838\n[   36.990800]  spi_mem_exec_op+0x8ec/0xd30\n[   36.994762]  spi_mem_no_dirmap_read+0x190/0x1e0\n[   36.999323]  spi_mem_dirmap_write+0x238/0x32c\n[   37.003710]  spi_nor_write_data+0x220/0x374\n[   37.007932]  spi_nor_write+0x110/0x2e8\n[   37.011711]  mtd_write_oob_std+0x154/0x1f0\n[   37.015838]  mtd_write_oob+0x104/0x1d0\n[   37.019617]  mtd_write+0xb8/0x12c\n[   37.022953]  mtdchar_write+0x224/0x47c\n[   37.026732]  vfs_write+0x1e4/0x8c8\n[   37.030163]  ksys_write+0xec/0x1d0\n[   37.033586]  __arm64_sys_write+0x6c/0x9c\n[   37.037539]  invoke_syscall+0x6c/0x258\n[   37.041327]  el0_svc_common.constprop.0+0x160/0x22c\n[   37.046244]  do_el0_svc+0x44/0x5c\n[   37.049589]  el0_svc+0x38/0x78\n[   37.052681]  el0t_64_sync_handler+0x13c/0x158\n[   37.057077]  el0t_64_sync+0x190/0x194\n[   37.060775]\n[   37.062274] Allocated by task 455:\n[   37.065701]  kasan_save_stack+0x2c/0x54\n[   37.069570]  kasan_save_track+0x20/0x3c\n[   37.073438]  kasan_save_alloc_info+0x40/0x54\n[   37.077736]  __kasan_kmalloc+0xa0/0xb8\n[   37.081515]  __kmalloc_noprof+0x158/0x2f8\n[   37.085563]  mtd_kmalloc_up_to+0x120/0x154\n[   37.089690]  mtdchar_write+0x130/0x47c\n[   37.093469]  vfs_write+0x1e4/0x8c8\n[   37.096901]  ksys_write+0xec/0x1d0\n[   37.100332]  __arm64_sys_write+0x6c/0x9c\n[   37.104287]  invoke_syscall+0x6c/0x258\n[   37.108064]  el0_svc_common.constprop.0+0x160/0x22c\n[   37.112972]  do_el0_svc+0x44/0x5c\n[   37.116319]  el0_svc+0x38/0x78\n[   37.119401]  el0t_64_sync_handler+0x13c/0x158\n[   37.123788]  el0t_64_sync+0x190/0x194\n[   37.127474]\n[   37.128977] The buggy address belongs to the object at ffff00081037c2a0\n[   37.128977]  which belongs to the cache kmalloc-8 of size 8\n[   37.141177] The buggy address is located 0 bytes inside of\n[   37.141177]  allocated 3-byte region [ffff00081037c2a0, ffff00081037c2a3)\n[   37.153465]\n[   37.154971] The buggy address belongs to the physical page:\n[   37.160559] page: refcount:1 mapcount:0 mapping:0000000000000000 index:0x0 pfn:0x89037c\n[   37.168596] flags: 0xbfffe0000000000(node=0|zone=2|lastcpupid=0x1ffff)\n[   37.175149] page_type: 0xfdffffff(slab)\n[   37.179021] raw: 0bfffe0000000000 ffff000800002500 dead000000000122 0000000000000000\n[   37.186788] raw: 0000000000000000 0000000080800080 00000001fdffffff 0000000000000000\n[   37.194553] page dumped because: kasan: bad access detected\n[   37.200144]\n[   37.201647] Memory state around the buggy address:\n[   37.206460]  ffff00081037c180: fa fc fc fc fa fc fc fc fa fc fc fc fa fc fc fc\n[   37.213701]  ffff00081037c200: fa fc fc fc 05 fc fc fc 03 fc fc fc 02 fc fc fc\n[   37.220946] \u0026gt;ffff00081037c280: 06 fc fc fc 03 fc fc fc fc fc fc fc fc fc fc fc\n[   37.228186]                                ^\n[   37.232473]  ffff00081037c300: fc fc fc fc fc fc fc fc fc fc fc fc fc fc fc fc\n[   37.239718]  ffff00081037c380: fc fc fc fc fc fc fc fc fc fc fc fc fc fc fc fc\n[   37.246962] ==============================================================\n---truncated---(CVE-2024-46853)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nPCI: keystone: Add workaround for Errata #i2037 (AM65x SR 1.0)\r\n\r\nErrata #i2037 in AM65x/DRA80xM Processors Silicon Revision 1.0\n(SPRZ452D_July 2018_Revised December 2019 [1]) mentions when an\ninbound PCIe TLP spans more than two internal AXI 128-byte bursts,\nthe bus may corrupt the packet payload and the corrupt data may\ncause associated applications or the processor to hang.\r\n\r\nThe workaround for Errata #i2037 is to limit the maximum read\nrequest size and maximum payload size to 128 bytes. Add workaround\nfor Errata #i2037 here.\r\n\r\nThe errata and workaround is applicable only to AM65x SR 1.0 and\nlater versions of the silicon will have this fixed.\r\n\r\n[1] -\u0026gt; https://www.ti.com/lit/er/sprz452i/sprz452i.pdf(CVE-2024-47667)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nnilfs2: fix state management in error path of log writing function\r\n\r\nAfter commit a694291a6211 (\u0026quot;nilfs2: separate wait function from\nnilfs_segctor_write\u0026quot;) was applied, the log writing function\nnilfs_segctor_do_construct() was able to issue I/O requests continuously\neven if user data blocks were split into multiple logs across segments,\nbut two potential flaws were introduced in its error handling.\r\n\r\nFirst, if nilfs_segctor_begin_construction() fails while creating the\nsecond or subsequent logs, the log writing function returns without\ncalling nilfs_segctor_abort_construction(), so the writeback flag set on\npages/folios will remain uncleared.  This causes page cache operations to\nhang waiting for the writeback flag.  For example,\ntruncate_inode_pages_final(), which is called via nilfs_evict_inode() when\nan inode is evicted from memory, will hang.\r\n\r\nSecond, the NILFS_I_COLLECTED flag set on normal inodes remain uncleared. \nAs a result, if the next log write involves checkpoint creation, that\u0026apos;s\nfine, but if a partial log write is performed that does not, inodes with\nNILFS_I_COLLECTED set are erroneously removed from the \u0026quot;sc_dirty_files\u0026quot;\nlist, and their data and b-tree blocks may not be written to the device,\ncorrupting the block mapping.\r\n\r\nFix these issues by uniformly calling nilfs_segctor_abort_construction()\non failure of each step in the loop in nilfs_segctor_do_construct(),\nhaving it clean up logs and segment usages according to progress, and\ncorrecting the conditions for calling nilfs_redirty_inodes() to ensure\nthat the NILFS_I_COLLECTED flag is cleared.(CVE-2024-47669)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  tcp: check skb is non-NULL in tcp_rto_delta_us()  We have some machines running stock Ubuntu 20.04.6 which is their 5.4.0-174-generic kernel that are running ceph and recently hit a null ptr dereference in tcp_rearm_rto(). Initially hitting it from the TLP path, but then later we also saw it getting hit from the RACK case as well. Here are examples of the oops messages we saw in each of those cases:  Jul 26 15:05:02 rx [11061395.780353] BUG: kernel NULL pointer dereference, address: 0000000000000020 Jul 26 15:05:02 rx [11061395.787572] #PF: supervisor read access in kernel mode Jul 26 15:05:02 rx [11061395.792971] #PF: error_code(0x0000) - not-present page Jul 26 15:05:02 rx [11061395.798362] PGD 0 P4D 0 Jul 26 15:05:02 rx [11061395.801164] Oops: 0000 [#1] SMP NOPTI Jul 26 15:05:02 rx [11061395.805091] CPU: 0 PID: 9180 Comm: msgr-worker-1 Tainted: G W 5.4.0-174-generic #193-Ubuntu Jul 26 15:05:02 rx [11061395.814996] Hardware name: Supermicro SMC 2x26 os-gen8 64C NVME-Y 256G/H12SSW-NTR, BIOS 2.5.V1.2U.NVMe.UEFI 05/09/2023 Jul 26 15:05:02 rx [11061395.825952] RIP: 0010:tcp_rearm_rto+0xe4/0x160 Jul 26 15:05:02 rx [11061395.830656] Code: 87 ca 04 00 00 00 5b 41 5c 41 5d 5d c3 c3 49 8b bc 24 40 06 00 00 eb 8d 48 bb cf f7 53 e3 a5 9b c4 20 4c 89 ef e8 0c fe 0e 00 \u0026lt;48\u0026gt; 8b 78 20 48 c1 ef 03 48 89 f8 41 8b bc 24 80 04 00 00 48 f7 e3 Jul 26 15:05:02 rx [11061395.849665] RSP: 0018:ffffb75d40003e08 EFLAGS: 00010246 Jul 26 15:05:02 rx [11061395.855149] RAX: 0000000000000000 RBX: 20c49ba5e353f7cf RCX: 0000000000000000 Jul 26 15:05:02 rx [11061395.862542] RDX: 0000000062177c30 RSI: 000000000000231c RDI: ffff9874ad283a60 Jul 26 15:05:02 rx [11061395.869933] RBP: ffffb75d40003e20 R08: 0000000000000000 R09: ffff987605e20aa8 Jul 26 15:05:02 rx [11061395.877318] R10: ffffb75d40003f00 R11: ffffb75d4460f740 R12: ffff9874ad283900 Jul 26 15:05:02 rx [11061395.884710] R13: ffff9874ad283a60 R14: ffff9874ad283980 R15: ffff9874ad283d30 Jul 26 15:05:02 rx [11061395.892095] FS: 00007f1ef4a2e700(0000) GS:ffff987605e00000(0000) knlGS:0000000000000000 Jul 26 15:05:02 rx [11061395.900438] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 Jul 26 15:05:02 rx [11061395.906435] CR2: 0000000000000020 CR3: 0000003e450ba003 CR4: 0000000000760ef0 Jul 26 15:05:02 rx [11061395.913822] PKRU: 55555554 Jul 26 15:05:02 rx [11061395.916786] Call Trace: Jul 26 15:05:02 rx [11061395.919488] Jul 26 15:05:02 rx [11061395.921765] ? show_regs.cold+0x1a/0x1f Jul 26 15:05:02 rx [11061395.925859] ? __die+0x90/0xd9 Jul 26 15:05:02 rx [11061395.929169] ? no_context+0x196/0x380 Jul 26 15:05:02 rx [11061395.933088] ? ip6_protocol_deliver_rcu+0x4e0/0x4e0 Jul 26 15:05:02 rx [11061395.938216] ? ip6_sublist_rcv_finish+0x3d/0x50 Jul 26 15:05:02 rx [11061395.943000] ? __bad_area_nosemaphore+0x50/0x1a0 Jul 26 15:05:02 rx [11061395.947873] ? bad_area_nosemaphore+0x16/0x20 Jul 26 15:05:02 rx [11061395.952486] ? do_user_addr_fault+0x267/0x450 Jul 26 15:05:02 rx [11061395.957104] ? ipv6_list_rcv+0x112/0x140 Jul 26 15:05:02 rx [11061395.961279] ? __do_page_fault+0x58/0x90 Jul 26 15:05:02 rx [11061395.965458] ? do_page_fault+0x2c/0xe0 Jul 26 15:05:02 rx [11061395.969465] ? page_fault+0x34/0x40 Jul 26 15:05:02 rx [11061395.973217] ? tcp_rearm_rto+0xe4/0x160 Jul 26 15:05:02 rx [11061395.977313] ? tcp_rearm_rto+0xe4/0x160 Jul 26 15:05:02 rx [11061395.981408] tcp_send_loss_probe+0x10b/0x220 Jul 26 15:05:02 rx [11061395.985937] tcp_write_timer_handler+0x1b4/0x240 Jul 26 15:05:02 rx [11061395.990809] tcp_write_timer+0x9e/0xe0 Jul 26 15:05:02 rx [11061395.994814] ? tcp_write_timer_handler+0x240/0x240 Jul 26 15:05:02 rx [11061395.999866] call_timer_fn+0x32/0x130 Jul 26 15:05:02 rx [11061396.003782] __run_timers.part.0+0x180/0x280 Jul 26 15:05:02 rx [11061396.008309] ? recalibrate_cpu_khz+0x10/0x10 Jul 26 15:05:02 rx [11061396.012841] ? native_x2apic_icr_write+0x30/0x30 Jul 26 15:05:02 rx [11061396.017718] ? lapic_next_even ---truncated---(CVE-2024-47684)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  netfilter: nf_reject_ipv6: fix nf_reject_ip6_tcphdr_put()  syzbot reported that nf_reject_ip6_tcphdr_put() was possibly sending garbage on the four reserved tcp bits (th-\u0026gt;res1)  Use skb_put_zero() to clear the whole TCP header, as done in nf_reject_ip_tcphdr_put()  BUG: KMSAN: uninit-value in nf_reject_ip6_tcphdr_put+0x688/0x6c0 net/ipv6/netfilter/nf_reject_ipv6.c:255   nf_reject_ip6_tcphdr_put+0x688/0x6c0 net/ipv6/netfilter/nf_reject_ipv6.c:255   nf_send_reset6+0xd84/0x15b0 net/ipv6/netfilter/nf_reject_ipv6.c:344   nft_reject_inet_eval+0x3c1/0x880 net/netfilter/nft_reject_inet.c:48   expr_call_ops_eval net/netfilter/nf_tables_core.c:240 [inline]   nft_do_chain+0x438/0x22a0 net/netfilter/nf_tables_core.c:288   nft_do_chain_inet+0x41a/0x4f0 net/netfilter/nft_chain_filter.c:161   nf_hook_entry_hookfn include/linux/netfilter.h:154 [inline]   nf_hook_slow+0xf4/0x400 net/netfilter/core.c:626   nf_hook include/linux/netfilter.h:269 [inline]   NF_HOOK include/linux/netfilter.h:312 [inline]   ipv6_rcv+0x29b/0x390 net/ipv6/ip6_input.c:310   __netif_receive_skb_one_core net/core/dev.c:5661 [inline]   __netif_receive_skb+0x1da/0xa00 net/core/dev.c:5775   process_backlog+0x4ad/0xa50 net/core/dev.c:6108   __napi_poll+0xe7/0x980 net/core/dev.c:6772   napi_poll net/core/dev.c:6841 [inline]   net_rx_action+0xa5a/0x19b0 net/core/dev.c:6963   handle_softirqs+0x1ce/0x800 kernel/softirq.c:554   __do_softirq+0x14/0x1a kernel/softirq.c:588   do_softirq+0x9a/0x100 kernel/softirq.c:455   __local_bh_enable_ip+0x9f/0xb0 kernel/softirq.c:382   local_bh_enable include/linux/bottom_half.h:33 [inline]   rcu_read_unlock_bh include/linux/rcupdate.h:908 [inline]   __dev_queue_xmit+0x2692/0x5610 net/core/dev.c:4450   dev_queue_xmit include/linux/netdevice.h:3105 [inline]   neigh_resolve_output+0x9ca/0xae0 net/core/neighbour.c:1565   neigh_output include/net/neighbour.h:542 [inline]   ip6_finish_output2+0x2347/0x2ba0 net/ipv6/ip6_output.c:141   __ip6_finish_output net/ipv6/ip6_output.c:215 [inline]   ip6_finish_output+0xbb8/0x14b0 net/ipv6/ip6_output.c:226   NF_HOOK_COND include/linux/netfilter.h:303 [inline]   ip6_output+0x356/0x620 net/ipv6/ip6_output.c:247   dst_output include/net/dst.h:450 [inline]   NF_HOOK include/linux/netfilter.h:314 [inline]   ip6_xmit+0x1ba6/0x25d0 net/ipv6/ip6_output.c:366   inet6_csk_xmit+0x442/0x530 net/ipv6/inet6_connection_sock.c:135   __tcp_transmit_skb+0x3b07/0x4880 net/ipv4/tcp_output.c:1466   tcp_transmit_skb net/ipv4/tcp_output.c:1484 [inline]   tcp_connect+0x35b6/0x7130 net/ipv4/tcp_output.c:4143   tcp_v6_connect+0x1bcc/0x1e40 net/ipv6/tcp_ipv6.c:333   __inet_stream_connect+0x2ef/0x1730 net/ipv4/af_inet.c:679   inet_stream_connect+0x6a/0xd0 net/ipv4/af_inet.c:750   __sys_connect_file net/socket.c:2061 [inline]   __sys_connect+0x606/0x690 net/socket.c:2078   __do_sys_connect net/socket.c:2088 [inline]   __se_sys_connect net/socket.c:2085 [inline]   __x64_sys_connect+0x91/0xe0 net/socket.c:2085   x64_sys_call+0x27a5/0x3ba0 arch/x86/include/generated/asm/syscalls_64.h:43   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 stored to memory at:   nf_reject_ip6_tcphdr_put+0x60c/0x6c0 net/ipv6/netfilter/nf_reject_ipv6.c:249   nf_send_reset6+0xd84/0x15b0 net/ipv6/netfilter/nf_reject_ipv6.c:344   nft_reject_inet_eval+0x3c1/0x880 net/netfilter/nft_reject_inet.c:48   expr_call_ops_eval net/netfilter/nf_tables_core.c:240 [inline]   nft_do_chain+0x438/0x22a0 net/netfilter/nf_tables_core.c:288   nft_do_chain_inet+0x41a/0x4f0 net/netfilter/nft_chain_filter.c:161   nf_hook_entry_hookfn include/linux/netfilter.h:154 [inline]   nf_hook_slow+0xf4/0x400 net/netfilter/core.c:626   nf_hook include/linux/netfilter.h:269 [inline]   NF_HOOK include/linux/netfilter.h:312 [inline]   ipv6_rcv+0x29b/0x390 net/ipv6/ip6_input.c:310   __netif_receive_skb_one_core ---truncated---(CVE-2024-47685)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  RDMA/rtrs-clt: Reset cid to con_num - 1 to stay in bounds  In the function init_conns(), after the create_con() and create_cm() for loop if something fails. In the cleanup for loop after the destroy tag, we access out of bound memory because cid is set to clt_path-\u0026gt;s.con_num.  This commits resets the cid to clt_path-\u0026gt;s.con_num - 1, to stay in bounds in the cleanup loop later.(CVE-2024-47695)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  drivers: media: dvb-frontends/rtl2832: fix an out-of-bounds write error  Ensure index in rtl2832_pid_filter does not exceed 31 to prevent out-of-bounds access.  dev-\u0026gt;filters is a 32-bit value, so set_bit and clear_bit functions should only operate on indices from 0 to 31. If index is 32, it will attempt to access a non-existent 33rd bit, leading to out-of-bounds access. Change the boundary check from index \u0026gt; 32 to index \u0026gt;= 32 to resolve this issue.  [hverkuil: added fixes tag, rtl2830_pid_filter -\u0026gt; rtl2832_pid_filter in logmsg](CVE-2024-47698)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  can: bcm: Clear bo-\u0026gt;bcm_proc_read after remove_proc_entry().  syzbot reported a warning in bcm_release(). [0]  The blamed change fixed another warning that is triggered when connect() is issued again for a socket whose connect()ed device has been unregistered.  However, if the socket is just close()d without the 2nd connect(), the remaining bo-\u0026gt;bcm_proc_read triggers unnecessary remove_proc_entry() in bcm_release().  Let\u0026apos;s clear bo-\u0026gt;bcm_proc_read after remove_proc_entry() in bcm_notify().  [0] name \u0026apos;4986\u0026apos; WARNING: CPU: 0 PID: 5234 at fs/proc/generic.c:711 remove_proc_entry+0x2e7/0x5d0 fs/proc/generic.c:711 Modules linked in: CPU: 0 UID: 0 PID: 5234 Comm: syz-executor606 Not tainted 6.11.0-rc5-syzkaller-00178-g5517ae241919 #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 08/06/2024 RIP: 0010:remove_proc_entry+0x2e7/0x5d0 fs/proc/generic.c:711 Code: ff eb 05 e8 cb 1e 5e ff 48 8b 5c 24 10 48 c7 c7 e0 f7 aa 8e e8 2a 38 8e 09 90 48 c7 c7 60 3a 1b 8c 48 89 de e8 da 42 20 ff 90 \u0026lt;0f\u0026gt; 0b 90 90 48 8b 44 24 18 48 c7 44 24 40 0e 36 e0 45 49 c7 04 07 RSP: 0018:ffffc9000345fa20 EFLAGS: 00010246 RAX: 2a2d0aee2eb64600 RBX: ffff888032f1f548 RCX: ffff888029431e00 RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000000000000 RBP: ffffc9000345fb08 R08: ffffffff8155b2f2 R09: 1ffff1101710519a R10: dffffc0000000000 R11: ffffed101710519b R12: ffff888011d38640 R13: 0000000000000004 R14: 0000000000000000 R15: dffffc0000000000 FS:  0000000000000000(0000) GS:ffff8880b8800000(0000) knlGS:0000000000000000 CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 00007fcfb52722f0 CR3: 000000000e734000 CR4: 00000000003506f0 DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400 Call Trace:  \u0026lt;TASK\u0026gt;  bcm_release+0x250/0x880 net/can/bcm.c:1578  __sock_release net/socket.c:659 [inline]  sock_close+0xbc/0x240 net/socket.c:1421  __fput+0x24a/0x8a0 fs/file_table.c:422  task_work_run+0x24f/0x310 kernel/task_work.c:228  exit_task_work include/linux/task_work.h:40 [inline]  do_exit+0xa2f/0x27f0 kernel/exit.c:882  do_group_exit+0x207/0x2c0 kernel/exit.c:1031  __do_sys_exit_group kernel/exit.c:1042 [inline]  __se_sys_exit_group kernel/exit.c:1040 [inline]  __x64_sys_exit_group+0x3f/0x40 kernel/exit.c:1040  x64_sys_call+0x2634/0x2640 arch/x86/include/generated/asm/syscalls_64.h:232  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:0x7fcfb51ee969 Code: Unable to access opcode bytes at 0x7fcfb51ee93f. RSP: 002b:00007ffce0109ca8 EFLAGS: 00000246 ORIG_RAX: 00000000000000e7 RAX: ffffffffffffffda RBX: 0000000000000001 RCX: 00007fcfb51ee969 RDX: 000000000000003c RSI: 00000000000000e7 RDI: 0000000000000001 RBP: 00007fcfb526f3b0 R08: ffffffffffffffb8 R09: 0000555500000000 R10: 0000555500000000 R11: 0000000000000246 R12: 00007fcfb526f3b0 R13: 0000000000000000 R14: 00007fcfb5271ee0 R15: 00007fcfb51bf160  \u0026lt;/TASK\u0026gt;(CVE-2024-47709)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  sock_map: Add a cond_resched() in sock_hash_free()  Several syzbot soft lockup reports all have in common sock_hash_free()  If a map with a large number of buckets is destroyed, we need to yield the cpu when needed.(CVE-2024-47710)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  drm/amd/display: Add null check for set_output_gamma in dcn30_set_output_transfer_func  This commit adds a null check for the set_output_gamma function pointer in the  dcn30_set_output_transfer_func function. Previously, set_output_gamma was being checked for nullity at line 386, but then it was being dereferenced without any nullity check at line 401. This could potentially lead to a null pointer dereference error if set_output_gamma is indeed null.  To fix this, we now ensure that set_output_gamma is not null before dereferencing it. We do this by adding a nullity check for set_output_gamma before the call to set_output_gamma at line 401. If set_output_gamma is null, we log an error message and do not call the function.  This fix prevents a potential null pointer dereference error.  drivers/gpu/drm/amd/amdgpu/../display/dc/hwss/dcn30/dcn30_hwseq.c:401 dcn30_set_output_transfer_func() error: we previously assumed \u0026apos;mpc-\u0026gt;funcs-\u0026gt;set_output_gamma\u0026apos; could be null (see line 386)  drivers/gpu/drm/amd/amdgpu/../display/dc/hwss/dcn30/dcn30_hwseq.c     373 bool dcn30_set_output_transfer_func(struct dc *dc,     374                                 struct pipe_ctx *pipe_ctx,     375                                 const struct dc_stream_state *stream)     376 {     377         int mpcc_id = pipe_ctx-\u0026gt;plane_res.hubp-\u0026gt;inst;     378         struct mpc *mpc = pipe_ctx-\u0026gt;stream_res.opp-\u0026gt;ctx-\u0026gt;dc-\u0026gt;res_pool-\u0026gt;mpc;     379         const struct pwl_params *params = NULL;     380         bool ret = false;     381     382         /* program OGAM or 3DLUT only for the top pipe*/     383         if (pipe_ctx-\u0026gt;top_pipe == NULL) {     384                 /*program rmu shaper and 3dlut in MPC*/     385                 ret = dcn30_set_mpc_shaper_3dlut(pipe_ctx, stream);     386                 if (ret == false \u0026amp;\u0026amp; mpc-\u0026gt;funcs-\u0026gt;set_output_gamma) {                                             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^ If this is NULL      387                         if (stream-\u0026gt;out_transfer_func.type == TF_TYPE_HWPWL)     388                                 params = \u0026amp;stream-\u0026gt;out_transfer_func.pwl;     389                         else if (pipe_ctx-\u0026gt;stream-\u0026gt;out_transfer_func.type ==     390                                         TF_TYPE_DISTRIBUTED_POINTS \u0026amp;\u0026amp;     391                                         cm3_helper_translate_curve_to_hw_format(     392                                         \u0026amp;stream-\u0026gt;out_transfer_func,     393                                         \u0026amp;mpc-\u0026gt;blender_params, false))     394                                 params = \u0026amp;mpc-\u0026gt;blender_params;     395                          /* there are no ROM LUTs in OUTGAM */     396                         if (stream-\u0026gt;out_transfer_func.type == TF_TYPE_PREDEFINED)     397                                 BREAK_TO_DEBUGGER();     398                 }     399         }     400 --\u0026gt; 401         mpc-\u0026gt;funcs-\u0026gt;set_output_gamma(mpc, mpcc_id, params);                 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^ Then it will crash      402         return ret;     403 }(CVE-2024-47720)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  nfsd: call cache_put if xdr_reserve_space returns NULL  If not enough buffer space available, but idmap_lookup has triggered lookup_fn which calls cache_get and returns successfully. Then we missed to call cache_put here which pairs with cache_get.  Reviwed-by: Jeff Layton \u0026lt;jlayton@kernel.org\u0026gt;(CVE-2024-47737)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  nilfs2: fix potential oob read in nilfs_btree_check_delete()  The function nilfs_btree_check_delete(), which checks whether degeneration to direct mapping occurs before deleting a b-tree entry, causes memory access outside the block buffer when retrieving the maximum key if the root node has no entries.  This does not usually happen because b-tree mappings with 0 child nodes are never created by mkfs.nilfs2 or nilfs2 itself.  However, it can happen if the b-tree root node read from a device is configured that way, so fix this potential issue by adding a check for that case.(CVE-2024-47757)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  tracing/timerlat: Fix a race during cpuhp processing  There is another found exception that the \u0026quot;timerlat/1\u0026quot; thread was scheduled on CPU0, and lead to timer corruption finally:  ``` ODEBUG: init active (active state 0) object: ffff888237c2e108 object type: hrtimer hint: timerlat_irq+0x0/0x220 WARNING: CPU: 0 PID: 426 at lib/debugobjects.c:518 debug_print_object+0x7d/0xb0 Modules linked in: CPU: 0 UID: 0 PID: 426 Comm: timerlat/1 Not tainted 6.11.0-rc7+ #45 Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.13.0-1ubuntu1.1 04/01/2014 RIP: 0010:debug_print_object+0x7d/0xb0 ... Call Trace:  \u0026lt;TASK\u0026gt;  ? __warn+0x7c/0x110  ? debug_print_object+0x7d/0xb0  ? report_bug+0xf1/0x1d0  ? prb_read_valid+0x17/0x20  ? handle_bug+0x3f/0x70  ? exc_invalid_op+0x13/0x60  ? asm_exc_invalid_op+0x16/0x20  ? debug_print_object+0x7d/0xb0  ? debug_print_object+0x7d/0xb0  ? __pfx_timerlat_irq+0x10/0x10  __debug_object_init+0x110/0x150  hrtimer_init+0x1d/0x60  timerlat_main+0xab/0x2d0  ? __pfx_timerlat_main+0x10/0x10  kthread+0xb7/0xe0  ? __pfx_kthread+0x10/0x10  ret_from_fork+0x2d/0x40  ? __pfx_kthread+0x10/0x10  ret_from_fork_asm+0x1a/0x30  \u0026lt;/TASK\u0026gt; ```  After tracing the scheduling event, it was discovered that the migration of the \u0026quot;timerlat/1\u0026quot; thread was performed during thread creation. Further analysis confirmed that it is because the CPU online processing for osnoise is implemented through workers, which is asynchronous with the offline processing. When the worker was scheduled to create a thread, the CPU may has already been removed from the cpu_online_mask during the offline process, resulting in the inability to select the right CPU:  T1                       | T2 [CPUHP_ONLINE]           | cpu_device_down() osnoise_hotplug_workfn() |                          |     cpus_write_lock()                          |     takedown_cpu(1)                          |     cpus_write_unlock() [CPUHP_OFFLINE]          |     cpus_read_lock()     |     start_kthread(1)     |     cpus_read_unlock()   |  To fix this, skip online processing if the CPU is already offline.(CVE-2024-49866)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  btrfs: wait for fixup workers before stopping cleaner kthread during umount  During unmount, at close_ctree(), we have the following steps in this order:  1) Park the cleaner kthread - this doesn\u0026apos;t destroy the kthread, it basically    halts its execution (wake ups against it work but do nothing);  2) We stop the cleaner kthread - this results in freeing the respective    struct task_struct;  3) We call btrfs_stop_all_workers() which waits for any jobs running in all    the work queues and then free the work queues.  Syzbot reported a case where a fixup worker resulted in a crash when doing a delayed iput on its inode while attempting to wake up the cleaner at btrfs_add_delayed_iput(), because the task_struct of the cleaner kthread was already freed. This can happen during unmount because we don\u0026apos;t wait for any fixup workers still running before we call kthread_stop() against the cleaner kthread, which stops and free all its resources.  Fix this by waiting for any fixup workers at close_ctree() before we call kthread_stop() against the cleaner and run pending delayed iputs.  The stack traces reported by syzbot were the following:    BUG: KASAN: slab-use-after-free in __lock_acquire+0x77/0x2050 kernel/locking/lockdep.c:5065   Read of size 8 at addr ffff8880272a8a18 by task kworker/u8:3/52    CPU: 1 UID: 0 PID: 52 Comm: kworker/u8:3 Not tainted 6.12.0-rc1-syzkaller #0   Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 09/13/2024   Workqueue: btrfs-fixup btrfs_work_helper   Call Trace:    \u0026lt;TASK\u0026gt;    __dump_stack lib/dump_stack.c:94 [inline]    dump_stack_lvl+0x241/0x360 lib/dump_stack.c:120    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    __lock_acquire+0x77/0x2050 kernel/locking/lockdep.c:5065    lock_acquire+0x1ed/0x550 kernel/locking/lockdep.c:5825    __raw_spin_lock_irqsave include/linux/spinlock_api_smp.h:110 [inline]    _raw_spin_lock_irqsave+0xd5/0x120 kernel/locking/spinlock.c:162    class_raw_spinlock_irqsave_constructor include/linux/spinlock.h:551 [inline]    try_to_wake_up+0xb0/0x1480 kernel/sched/core.c:4154    btrfs_writepage_fixup_worker+0xc16/0xdf0 fs/btrfs/inode.c:2842    btrfs_work_helper+0x390/0xc50 fs/btrfs/async-thread.c:314    process_one_work kernel/workqueue.c:3229 [inline]    process_scheduled_works+0xa63/0x1850 kernel/workqueue.c:3310    worker_thread+0x870/0xd30 kernel/workqueue.c:3391    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;    Allocated by task 2:    kasan_save_stack mm/kasan/common.c:47 [inline]    kasan_save_track+0x3f/0x80 mm/kasan/common.c:68    unpoison_slab_object mm/kasan/common.c:319 [inline]    __kasan_slab_alloc+0x66/0x80 mm/kasan/common.c:345    kasan_slab_alloc include/linux/kasan.h:247 [inline]    slab_post_alloc_hook mm/slub.c:4086 [inline]    slab_alloc_node mm/slub.c:4135 [inline]    kmem_cache_alloc_node_noprof+0x16b/0x320 mm/slub.c:4187    alloc_task_struct_node kernel/fork.c:180 [inline]    dup_task_struct+0x57/0x8c0 kernel/fork.c:1107    copy_process+0x5d1/0x3d50 kernel/fork.c:2206    kernel_clone+0x223/0x880 kernel/fork.c:2787    kernel_thread+0x1bc/0x240 kernel/fork.c:2849    create_kthread kernel/kthread.c:412 [inline]    kthreadd+0x60d/0x810 kernel/kthread.c:765    ret_from_fork+0x4b/0x80 arch/x86/kernel/process.c:147    ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:244    Freed by task 61:    kasan_save_stack mm/kasan/common.c:47 [inline]    kasan_save_track+0x3f/0x80 mm/kasan/common.c:68    kasan_save_free_info+0x40/0x50 mm/kasan/generic.c:579    poison_slab_object mm/kasan/common.c:247 [inline]    __kasan_slab_free+0x59/0x70 mm/kasan/common.c:264    kasan_slab_free include/linux/kasan.h:230 [inline]    slab_free_h ---truncated---(CVE-2024-49867)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  btrfs: fix a NULL pointer dereference when failed to start a new trasacntion  [BUG] Syzbot reported a NULL pointer dereference with the following crash:    FAULT_INJECTION: forcing a failure.    start_transaction+0x830/0x1670 fs/btrfs/transaction.c:676    prepare_to_relocate+0x31f/0x4c0 fs/btrfs/relocation.c:3642    relocate_block_group+0x169/0xd20 fs/btrfs/relocation.c:3678   ...   BTRFS info (device loop0): balance: ended with status: -12   Oops: general protection fault, probably for non-canonical address 0xdffffc00000000cc: 0000 [#1] PREEMPT SMP KASAN NOPTI   KASAN: null-ptr-deref in range [0x0000000000000660-0x0000000000000667]   RIP: 0010:btrfs_update_reloc_root+0x362/0xa80 fs/btrfs/relocation.c:926   Call Trace:    \u0026lt;TASK\u0026gt;    commit_fs_roots+0x2ee/0x720 fs/btrfs/transaction.c:1496    btrfs_commit_transaction+0xfaf/0x3740 fs/btrfs/transaction.c:2430    del_balance_item fs/btrfs/volumes.c:3678 [inline]    reset_balance_state+0x25e/0x3c0 fs/btrfs/volumes.c:3742    btrfs_balance+0xead/0x10c0 fs/btrfs/volumes.c:4574    btrfs_ioctl_balance+0x493/0x7c0 fs/btrfs/ioctl.c:3673    vfs_ioctl fs/ioctl.c:51 [inline]    __do_sys_ioctl fs/ioctl.c:907 [inline]    __se_sys_ioctl+0xf9/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  [CAUSE] The allocation failure happens at the start_transaction() inside prepare_to_relocate(), and during the error handling we call unset_reloc_control(), which makes fs_info-\u0026gt;balance_ctl to be NULL.  Then we continue the error path cleanup in btrfs_balance() by calling reset_balance_state() which will call del_balance_item() to fully delete the balance item in the root tree.  However during the small window between set_reloc_contrl() and unset_reloc_control(), we can have a subvolume tree update and created a reloc_root for that subvolume.  Then we go into the final btrfs_commit_transaction() of del_balance_item(), and into btrfs_update_reloc_root() inside commit_fs_roots().  That function checks if fs_info-\u0026gt;reloc_ctl is in the merge_reloc_tree stage, but since fs_info-\u0026gt;reloc_ctl is NULL, it results a NULL pointer dereference.  [FIX] Just add extra check on fs_info-\u0026gt;reloc_ctl inside btrfs_update_reloc_root(), before checking fs_info-\u0026gt;reloc_ctl-\u0026gt;merge_reloc_tree.  That DEAD_RELOC_TREE handling is to prevent further modification to the reloc tree during merge stage, but since there is no reloc_ctl at all, we do not need to bother that.(CVE-2024-49868)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  nfsd: map the EBADMSG to nfserr_io to avoid warning  Ext4 will throw -EBADMSG through ext4_readdir when a checksum error occurs, resulting in the following WARNING.  Fix it by mapping EBADMSG to nfserr_io.  nfsd_buffered_readdir  iterate_dir // -EBADMSG -74   ext4_readdir // .iterate_shared    ext4_dx_readdir     ext4_htree_fill_tree      htree_dirblock_to_tree       ext4_read_dirblock        __ext4_read_dirblock         ext4_dirblock_csum_verify          warn_no_space_for_csum           __warn_no_space_for_csum         return ERR_PTR(-EFSBADCRC) // -EBADMSG -74  nfserrno // WARNING  [  161.115610] ------------[ cut here ]------------ [  161.116465] nfsd: non-standard errno: -74 [  161.117315] WARNING: CPU: 1 PID: 780 at fs/nfsd/nfsproc.c:878 nfserrno+0x9d/0xd0 [  161.118596] Modules linked in: [  161.119243] CPU: 1 PID: 780 Comm: nfsd Not tainted 5.10.0-00014-g79679361fd5d #138 [  161.120684] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS rel-1.14.0-0-g155821a1990b-prebuilt.qe mu.org 04/01/2014 [  161.123601] RIP: 0010:nfserrno+0x9d/0xd0 [  161.124676] Code: 0f 87 da 30 dd 00 83 e3 01 b8 00 00 00 05 75 d7 44 89 ee 48 c7 c7 c0 57 24 98 89 44 24 04 c6  05 ce 2b 61 03 01 e8 99 20 d8 00 \u0026lt;0f\u0026gt; 0b 8b 44 24 04 eb b5 4c 89 e6 48 c7 c7 a0 6d a4 99 e8 cc 15 33 [  161.127797] RSP: 0018:ffffc90000e2f9c0 EFLAGS: 00010286 [  161.128794] RAX: 0000000000000000 RBX: 0000000000000000 RCX: 0000000000000000 [  161.130089] RDX: 1ffff1103ee16f6d RSI: 0000000000000008 RDI: fffff520001c5f2a [  161.131379] RBP: 0000000000000022 R08: 0000000000000001 R09: ffff8881f70c1827 [  161.132664] R10: ffffed103ee18304 R11: 0000000000000001 R12: 0000000000000021 [  161.133949] R13: 00000000ffffffb6 R14: ffff8881317c0000 R15: ffffc90000e2fbd8 [  161.135244] FS:  0000000000000000(0000) GS:ffff8881f7080000(0000) knlGS:0000000000000000 [  161.136695] CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033 [  161.137761] CR2: 00007fcaad70b348 CR3: 0000000144256006 CR4: 0000000000770ee0 [  161.139041] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 [  161.140291] DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400 [  161.141519] PKRU: 55555554 [  161.142076] Call Trace: [  161.142575]  ? __warn+0x9b/0x140 [  161.143229]  ? nfserrno+0x9d/0xd0 [  161.143872]  ? report_bug+0x125/0x150 [  161.144595]  ? handle_bug+0x41/0x90 [  161.145284]  ? exc_invalid_op+0x14/0x70 [  161.146009]  ? asm_exc_invalid_op+0x12/0x20 [  161.146816]  ? nfserrno+0x9d/0xd0 [  161.147487]  nfsd_buffered_readdir+0x28b/0x2b0 [  161.148333]  ? nfsd4_encode_dirent_fattr+0x380/0x380 [  161.149258]  ? nfsd_buffered_filldir+0xf0/0xf0 [  161.150093]  ? wait_for_concurrent_writes+0x170/0x170 [  161.151004]  ? generic_file_llseek_size+0x48/0x160 [  161.151895]  nfsd_readdir+0x132/0x190 [  161.152606]  ? nfsd4_encode_dirent_fattr+0x380/0x380 [  161.153516]  ? nfsd_unlink+0x380/0x380 [  161.154256]  ? override_creds+0x45/0x60 [  161.155006]  nfsd4_encode_readdir+0x21a/0x3d0 [  161.155850]  ? nfsd4_encode_readlink+0x210/0x210 [  161.156731]  ? write_bytes_to_xdr_buf+0x97/0xe0 [  161.157598]  ? __write_bytes_to_xdr_buf+0xd0/0xd0 [  161.158494]  ? lock_downgrade+0x90/0x90 [  161.159232]  ? nfs4svc_decode_voidarg+0x10/0x10 [  161.160092]  nfsd4_encode_operation+0x15a/0x440 [  161.160959]  nfsd4_proc_compound+0x718/0xe90 [  161.161818]  nfsd_dispatch+0x18e/0x2c0 [  161.162586]  svc_process_common+0x786/0xc50 [  161.163403]  ? nfsd_svc+0x380/0x380 [  161.164137]  ? svc_printk+0x160/0x160 [  161.164846]  ? svc_xprt_do_enqueue.part.0+0x365/0x380 [  161.165808]  ? nfsd_svc+0x380/0x380 [  161.166523]  ? rcu_is_watching+0x23/0x40 [  161.167309]  svc_process+0x1a5/0x200 [  161.168019]  nfsd+0x1f5/0x380 [  161.168663]  ? nfsd_shutdown_threads+0x260/0x260 [  161.169554]  kthread+0x1c4/0x210 [  161.170224]  ? kthread_insert_work_sanity_check+0x80/0x80 [  161.171246]  ret_from_fork+0x1f/0x30(CVE-2024-49875)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  drm/amd/display: Fix index out of bounds in degamma hardware format translation  Fixes index out of bounds issue in `cm_helper_translate_curve_to_degamma_hw_format` function. The issue could occur when the index \u0026apos;i\u0026apos; exceeds the number of transfer function points (TRANSFER_FUNC_POINTS).  The fix adds a check to ensure \u0026apos;i\u0026apos; is within bounds before accessing the transfer function points. If \u0026apos;i\u0026apos; is out of bounds the function returns false to indicate an error.  Reported by smatch: drivers/gpu/drm/amd/amdgpu/../display/dc/dcn10/dcn10_cm_common.c:594 cm_helper_translate_curve_to_degamma_hw_format() error: buffer overflow \u0026apos;output_tf-\u0026gt;tf_pts.red\u0026apos; 1025 \u0026lt;= s32max drivers/gpu/drm/amd/amdgpu/../display/dc/dcn10/dcn10_cm_common.c:595 cm_helper_translate_curve_to_degamma_hw_format() error: buffer overflow \u0026apos;output_tf-\u0026gt;tf_pts.green\u0026apos; 1025 \u0026lt;= s32max drivers/gpu/drm/amd/amdgpu/../display/dc/dcn10/dcn10_cm_common.c:596 cm_helper_translate_curve_to_degamma_hw_format() error: buffer overflow \u0026apos;output_tf-\u0026gt;tf_pts.blue\u0026apos; 1025 \u0026lt;= s32max(CVE-2024-49894)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  drm/amd/display: Fix index out of bounds in DCN30 degamma hardware format translation  This commit addresses a potential index out of bounds issue in the `cm3_helper_translate_curve_to_degamma_hw_format` function in the DCN30 color  management module. The issue could occur when the index \u0026apos;i\u0026apos; exceeds the  number of transfer function points (TRANSFER_FUNC_POINTS).  The fix adds a check to ensure \u0026apos;i\u0026apos; is within bounds before accessing the transfer function points. If \u0026apos;i\u0026apos; is out of bounds, the function returns false to indicate an error.  Reported by smatch: drivers/gpu/drm/amd/amdgpu/../display/dc/dcn30/dcn30_cm_common.c:338 cm3_helper_translate_curve_to_degamma_hw_format() error: buffer overflow \u0026apos;output_tf-\u0026gt;tf_pts.red\u0026apos; 1025 \u0026lt;= s32max drivers/gpu/drm/amd/amdgpu/../display/dc/dcn30/dcn30_cm_common.c:339 cm3_helper_translate_curve_to_degamma_hw_format() error: buffer overflow \u0026apos;output_tf-\u0026gt;tf_pts.green\u0026apos; 1025 \u0026lt;= s32max drivers/gpu/drm/amd/amdgpu/../display/dc/dcn30/dcn30_cm_common.c:340 cm3_helper_translate_curve_to_degamma_hw_format() error: buffer overflow \u0026apos;output_tf-\u0026gt;tf_pts.blue\u0026apos; 1025 \u0026lt;= s32max(CVE-2024-49895)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  jfs: Fix uninit-value access of new_ea in ea_buffer  syzbot reports that lzo1x_1_do_compress is using uninit-value:  ===================================================== BUG: KMSAN: uninit-value in lzo1x_1_do_compress+0x19f9/0x2510 lib/lzo/lzo1x_compress.c:178  ...  Uninit was stored to memory at:  ea_put fs/jfs/xattr.c:639 [inline]  ...  Local variable ea_buf created at:  __jfs_setxattr+0x5d/0x1ae0 fs/jfs/xattr.c:662  __jfs_xattr_set+0xe6/0x1f0 fs/jfs/xattr.c:934  =====================================================  The reason is ea_buf-\u0026gt;new_ea is not initialized properly.  Fix this by using memset to empty its content at the beginning in ea_get().(CVE-2024-49900)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  jfs: check if leafidx greater than num leaves per dmap tree  syzbot report a out of bounds in dbSplit, it because dmt_leafidx greater than num leaves per dmap tree, add a checking for dmt_leafidx in dbFindLeaf.  Shaggy: Modified sanity check to apply to control pages as well as leaf pages.(CVE-2024-49902)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  jfs: Fix uaf in dbFreeBits  [syzbot reported] ================================================================== BUG: KASAN: slab-use-after-free in __mutex_lock_common kernel/locking/mutex.c:587 [inline] BUG: KASAN: slab-use-after-free in __mutex_lock+0xfe/0xd70 kernel/locking/mutex.c:752 Read of size 8 at addr ffff8880229254b0 by task syz-executor357/5216  CPU: 0 UID: 0 PID: 5216 Comm: syz-executor357 Not tainted 6.11.0-rc3-syzkaller-00156-gd7a5aa4b3c00 #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 06/27/2024 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  __mutex_lock_common kernel/locking/mutex.c:587 [inline]  __mutex_lock+0xfe/0xd70 kernel/locking/mutex.c:752  dbFreeBits+0x7ea/0xd90 fs/jfs/jfs_dmap.c:2390  dbFreeDmap fs/jfs/jfs_dmap.c:2089 [inline]  dbFree+0x35b/0x680 fs/jfs/jfs_dmap.c:409  dbDiscardAG+0x8a9/0xa20 fs/jfs/jfs_dmap.c:1650  jfs_ioc_trim+0x433/0x670 fs/jfs/jfs_discard.c:100  jfs_ioctl+0x2d0/0x3e0 fs/jfs/ioctl.c:131  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  Freed by task 5218:  kasan_save_stack mm/kasan/common.c:47 [inline]  kasan_save_track+0x3f/0x80 mm/kasan/common.c:68  kasan_save_free_info+0x40/0x50 mm/kasan/generic.c:579  poison_slab_object+0xe0/0x150 mm/kasan/common.c:240  __kasan_slab_free+0x37/0x60 mm/kasan/common.c:256  kasan_slab_free include/linux/kasan.h:184 [inline]  slab_free_hook mm/slub.c:2252 [inline]  slab_free mm/slub.c:4473 [inline]  kfree+0x149/0x360 mm/slub.c:4594  dbUnmount+0x11d/0x190 fs/jfs/jfs_dmap.c:278  jfs_mount_rw+0x4ac/0x6a0 fs/jfs/jfs_mount.c:247  jfs_remount+0x3d1/0x6b0 fs/jfs/super.c:454  reconfigure_super+0x445/0x880 fs/super.c:1083  vfs_cmd_reconfigure fs/fsopen.c:263 [inline]  vfs_fsconfig_locked fs/fsopen.c:292 [inline]  __do_sys_fsconfig fs/fsopen.c:473 [inline]  __se_sys_fsconfig+0xb6e/0xf80 fs/fsopen.c:345  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  [Analysis] There are two paths (dbUnmount and jfs_ioc_trim) that generate race condition when accessing bmap, which leads to the occurrence of uaf.  Use the lock s_umount to synchronize them, in order to avoid uaf caused by race condition.(CVE-2024-49903)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  drm/amd/display: Add NULL check for function pointer in dcn20_set_output_transfer_func  This commit adds a null check for the set_output_gamma function pointer in the dcn20_set_output_transfer_func function. Previously, set_output_gamma was being checked for null at line 1030, but then it was being dereferenced without any null check at line 1048. This could potentially lead to a null pointer dereference error 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 at line 1048.(CVE-2024-49911)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  x86/ioapic: Handle allocation failures gracefully  Breno observed panics when using failslab under certain conditions during runtime:     can not alloc irq_pin_list (-1,0,20)    Kernel panic - not syncing: IO-APIC: failed to add irq-pin. Can not proceed     panic+0x4e9/0x590    mp_irqdomain_alloc+0x9ab/0xa80    irq_domain_alloc_irqs_locked+0x25d/0x8d0    __irq_domain_alloc_irqs+0x80/0x110    mp_map_pin_to_irq+0x645/0x890    acpi_register_gsi_ioapic+0xe6/0x150    hpet_open+0x313/0x480  That\u0026apos;s a pointless panic which is a leftover of the historic IO/APIC code which panic\u0026apos;ed during early boot when the interrupt allocation failed.  The only place which might justify panic is the PIT/HPET timer_check() code which tries to figure out whether the timer interrupt is delivered through the IO/APIC. But that code does not require to handle interrupt allocation failures. If the interrupt cannot be allocated then timer delivery fails and it either panics due to that or falls back to legacy mode.  Cure this by removing the panic wrapper around __add_pin_to_irq_node() and making mp_irqdomain_alloc() aware of the failure condition and handle it as any other failure in this function gracefully.(CVE-2024-49927)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  jbd2: stop waiting for space when jbd2_cleanup_journal_tail() returns error  In __jbd2_log_wait_for_space(), we might call jbd2_cleanup_journal_tail() to recover some journal space. But if an error occurs while executing jbd2_cleanup_journal_tail() (e.g., an EIO), we don\u0026apos;t stop waiting for free space right away, we try other branches, and if j_committing_transaction is NULL (i.e., the tid is 0), we will get the following complain:  ============================================ JBD2: I/O error when updating journal superblock for sdd-8. __jbd2_log_wait_for_space: needed 256 blocks and only had 217 space available __jbd2_log_wait_for_space: no way to get more journal space in sdd-8 ------------[ cut here ]------------ WARNING: CPU: 2 PID: 139804 at fs/jbd2/checkpoint.c:109 __jbd2_log_wait_for_space+0x251/0x2e0 Modules linked in: CPU: 2 PID: 139804 Comm: kworker/u8:3 Not tainted 6.6.0+ #1 RIP: 0010:__jbd2_log_wait_for_space+0x251/0x2e0 Call Trace:  \u0026lt;TASK\u0026gt;  add_transaction_credits+0x5d1/0x5e0  start_this_handle+0x1ef/0x6a0  jbd2__journal_start+0x18b/0x340  ext4_dirty_inode+0x5d/0xb0  __mark_inode_dirty+0xe4/0x5d0  generic_update_time+0x60/0x70 [...] ============================================  So only if jbd2_cleanup_journal_tail() returns 1, i.e., there is nothing to clean up at the moment, continue to try to reclaim free space in other ways.  Note that this fix relies on commit 6f6a6fda2945 (\u0026quot;jbd2: fix ocfs2 corrupt when updating journal superblock fails\u0026quot;) to make jbd2_cleanup_journal_tail return the correct error code.(CVE-2024-49959)\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:  drm/amd/display: Fix index out of bounds in DCN30 color transformation  This commit addresses a potential index out of bounds issue in the `cm3_helper_translate_curve_to_hw_format` function in the DCN30 color management module. The issue could occur when the index \u0026apos;i\u0026apos; exceeds the number of transfer function points (TRANSFER_FUNC_POINTS).  The fix adds a check to ensure \u0026apos;i\u0026apos; is within bounds before accessing the transfer function points. If \u0026apos;i\u0026apos; is out of bounds, the function returns false to indicate an error.  drivers/gpu/drm/amd/amdgpu/../display/dc/dcn30/dcn30_cm_common.c:180 cm3_helper_translate_curve_to_hw_format() error: buffer overflow \u0026apos;output_tf-\u0026gt;tf_pts.red\u0026apos; 1025 \u0026lt;= s32max drivers/gpu/drm/amd/amdgpu/../display/dc/dcn30/dcn30_cm_common.c:181 cm3_helper_translate_curve_to_hw_format() error: buffer overflow \u0026apos;output_tf-\u0026gt;tf_pts.green\u0026apos; 1025 \u0026lt;= s32max drivers/gpu/drm/amd/amdgpu/../display/dc/dcn30/dcn30_cm_common.c:182 cm3_helper_translate_curve_to_hw_format() error: buffer overflow \u0026apos;output_tf-\u0026gt;tf_pts.blue\u0026apos; 1025 \u0026lt;= s32max(CVE-2024-49969)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  NFSD: Limit the number of concurrent async COPY operations  Nothing appears to limit the number of concurrent async COPY operations that clients can start. In addition, AFAICT each async COPY can copy an unlimited number of 4MB chunks, so can run for a long time. Thus IMO async COPY can become a DoS vector.  Add a restriction mechanism that bounds the number of concurrent background COPY operations. Start simple and try to be fair -- this patch implements a per-namespace limit.  An async COPY request that occurs while this limit is exceeded gets NFS4ERR_DELAY. The requesting client can choose to send the request again after a delay or fall back to a traditional read/write style copy.  If there is need to make the mechanism more sophisticated, we can visit that in future patches.(CVE-2024-49974)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:  i2c: stm32f7: Do not prepare/unprepare clock during runtime suspend/resume  In case there is any sort of clock controller attached to this I2C bus controller, for example Versaclock or even an AIC32x4 I2C codec, then an I2C transfer triggered from the clock controller clk_ops .prepare callback may trigger a deadlock on drivers/clk/clk.c prepare_lock mutex.  This is because the clock controller first grabs the prepare_lock mutex and then performs the prepare operation, including its I2C access. The I2C access resumes this I2C bus controller via .runtime_resume callback, which calls clk_prepare_enable(), which attempts to grab the prepare_lock mutex again and deadlocks.  Since the clock are already prepared since probe() and unprepared in remove(), use simple clk_enable()/clk_disable() calls to enable and disable the clock on runtime suspend and resume, to avoid hitting the prepare_lock mutex.(CVE-2024-49985)\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:  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:  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:  drm/amd/display: Check null pointer before dereferencing se  [WHAT \u0026amp; HOW] se is null checked previously in the same function, indicating it might be null; therefore, it must be checked when used again.  This fixes 1 FORWARD_NULL issue reported by Coverity.(CVE-2024-50049)","status":"published","published":"2024-11-01T11:07:48Z","modified":"2026-08-18T01:17:36.430422624Z","cvss":[{"version":"3.1","score":9.1,"vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:H","level":"critical"}],"updated_at":"2026-11-02T15:52:41.595342Z"},{"id":"RHSA-2024:5928","title":"Red Hat Security Advisory: kernel security update","status":"published","published":"2024-10-02T05:06:38Z","modified":"2026-09-13T10:02:21Z","cvss":[{"version":"3.1","score":7.1,"vector":"CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:C/C:N/I:N/A:H","level":"high"}],"updated_at":"2026-11-02T15:53:14.03234Z"},{"id":"RHSA-2024:7000","title":"Red Hat Security Advisory: kernel security update","status":"published","published":"2024-10-02T05:07:40Z","modified":"2026-10-17T10:04:01Z","cvss":[{"version":"3.1","score":7.8,"vector":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H","level":"high"}],"updated_at":"2026-11-02T15:53:14.610978Z"},{"id":"RHSA-2024:7001","title":"Red Hat Security Advisory: kernel-rt security update","status":"published","published":"2024-10-02T05:07:25Z","modified":"2026-10-17T10:04:02Z","cvss":[{"version":"3.1","score":7.8,"vector":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H","level":"high"}],"updated_at":"2026-11-02T15:53:14.610978Z"},{"id":"RHSA-2024:8613","title":"Red Hat Security Advisory: kernel security update","status":"published","published":"2024-10-30T12:46:53Z","modified":"2026-10-17T10:04:14Z","cvss":[{"version":"3.1","score":7,"vector":"CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H","level":"high"}],"updated_at":"2026-11-02T15:53:14.610978Z"},{"id":"RHSA-2024:8614","title":"Red Hat Security Advisory: kernel-rt security update","status":"published","published":"2024-10-30T12:47:10Z","modified":"2026-10-17T10:04:14Z","cvss":[{"version":"3.1","score":7,"vector":"CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H","level":"high"}],"updated_at":"2026-11-02T15:53:14.610978Z"},{"id":"RLSA-2024:7000","title":"Important: kernel security update","description":"The kernel packages contain the Linux kernel, the core of any Linux operating system.  \nSecurity Fix(es):\n\n CVE-2023-6040  CVE-2024-26595  CVE-2024-26600  CVE-2021-46984  CVE-2023-52478  CVE-2023-52476  CVE-2023-52522  CVE-2021-47101  CVE-2021-47097  CVE-2023-52605  CVE-2024-26638  CVE-2024-26645  CVE-2024-26665  CVE-2024-26720  CVE-2024-26717  CVE-2024-26769  CVE-2024-26846  CVE-2024-26894  CVE-2024-26880  CVE-2024-26855  CVE-2024-26923  CVE-2024-26939  CVE-2024-27013  CVE-2024-27042  CVE-2024-35809  CVE-2023-52683  CVE-2024-35884  CVE-2024-35877  CVE-2024-35944  CVE-2024-35989  CVE-2021-47412  CVE-2021-47393  CVE-2021-47386  CVE-2021-47385  CVE-2021-47384  CVE-2021-47383  CVE-2021-47432  CVE-2021-47352  CVE-2021-47338  CVE-2021-47321  CVE-2021-47289  CVE-2021-47287  CVE-2023-52798  CVE-2023-52809  CVE-2023-52817  CVE-2023-52840  CVE-2023-52800  CVE-2021-47441  CVE-2021-47466  CVE-2021-47455  CVE-2021-47497  CVE-2021-47560  CVE-2021-47527  CVE-2024-36883  CVE-2024-36922  CVE-2024-36920  CVE-2024-36902  CVE-2024-36953  CVE-2024-36939  CVE-2024-36919  CVE-2024-36901  CVE-2021-47582  CVE-2021-47609  CVE-2024-38619  CVE-2022-48754  CVE-2022-48760  CVE-2024-38581  CVE-2024-38579  CVE-2024-38570  CVE-2024-38559  CVE-2024-38558  CVE-2024-37356  CVE-2024-39471  CVE-2024-39499  CVE-2024-39501  CVE-2024-39506  CVE-2024-40904  CVE-2024-40911  CVE-2024-40912  CVE-2024-40929  CVE-2024-40931  CVE-2024-40941  CVE-2024-40954  CVE-2024-40958  CVE-2024-40959  CVE-2024-40960  CVE-2024-40972  CVE-2024-40977  CVE-2024-40978  CVE-2024-40988  CVE-2024-40989  CVE-2024-40995  CVE-2024-40997  CVE-2024-40998  CVE-2024-41005  CVE-2024-40901  CVE-2024-41007  CVE-2024-41008  CVE-2022-48804  CVE-2022-48836  CVE-2022-48866  CVE-2024-41090  CVE-2024-41091  CVE-2024-41012  CVE-2024-41013  CVE-2024-41014  CVE-2024-41023  CVE-2024-41035  CVE-2024-41038  CVE-2024-41039  CVE-2024-41040  CVE-2024-41041  CVE-2024-41044  CVE-2024-41055  CVE-2024-41056  CVE-2024-41060  CVE-2024-41064  CVE-2024-41065  CVE-2024-41071  CVE-2024-41076  CVE-2024-41097  CVE-2024-42084  CVE-2024-42090  CVE-2024-42094  CVE-2024-42096  CVE-2024-42114  CVE-2024-42124  CVE-2024-42131  CVE-2024-42152  CVE-2024-42154  CVE-2024-42225  CVE-2024-42226  CVE-2024-42228  CVE-2024-42237  CVE-2024-42238  CVE-2024-42240  CVE-2024-42246  CVE-2024-42322  CVE-2024-43830  CVE-2024-43871  For more details about the security issue(s), including the impact, a CVSS score, acknowledgments, and other related information, refer to the CVE page(s) listed in the References section.","status":"published","published":"2025-05-07T19:11:34.309952Z","modified":"2025-05-07T19:38:05.008508Z","cvss":[{"version":"3.1","score":7.8,"vector":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H","level":"high"}],"updated_at":"2026-11-02T15:53:24.923365Z"},{"id":"UBUNTU-CVE-2024-42152","description":"In the Linux kernel, the following vulnerability has been resolved: nvmet: fix a possible leak when destroy a ctrl during qp establishment In nvmet_sq_destroy we capture sq-\u003ectrl early and if it is non-NULL we know that a ctrl was allocated (in the admin connect request handler) and we need to release pending AERs, clear ctrl-\u003esqs and sq-\u003ectrl (for nvme-loop primarily), and drop the final reference on the ctrl. However, a small window is possible where nvmet_sq_destroy starts (as a result of the client giving up and disconnecting) concurrently with the nvme admin connect cmd (which may be in an early stage). But *before* kill_and_confirm of sq-\u003eref (i.e. the admin connect managed to get an sq live reference). In this case, sq-\u003ectrl was allocated however after it was captured in a local variable in nvmet_sq_destroy. This prevented the final reference drop on the ctrl. Solve this by re-capturing the sq-\u003ectrl after all inflight request has completed, where for sure sq-\u003ectrl reference is final, and move forward based on that. This issue was observed in an environment with many hosts connecting multiple ctrls simoutanuosly, creating a delay in allocating a ctrl leading up to this race window.","status":"published","published":"2024-07-30T08:15:00Z","modified":"2026-10-26T22:34:34.81191245Z","cvss":[{"version":"4.0","score":8.2,"vector":"CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N","level":"high"},{"version":"3.1","score":4.7,"vector":"CVSS:3.1/AV:L/AC:H/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-02T16:54:58.679387Z"},{"id":"ALSA-2024:5928","title":"Important: kernel security update","description":"The kernel packages contain the Linux kernel, the core of any Linux operating system.  \n\nSecurity Fix(es):  \n\n  * kernel: nftables: nft_set_rbtree skip end interval element from gc (CVE-2024-26581)\n  * kernel: netfilter: nft_limit: reject configurations that cause integer overflow (CVE-2024-26668)\n  * kernel: vfio/pci: Lock external INTx masking ops (CVE-2024-26810)\n  * kernel: net: ice: Fix potential NULL pointer dereference in ice_bridge_setlink() (CVE-2024-26855)\n  * kernel: x86/xen: Add some null pointer checking to smp.c (CVE-2024-26908)\n  * kernel: netfilter: nf_tables: release mutex after nft_gc_seq_end from abort path (CVE-2024-26925)\n  * kernel: netfilter: nf_tables: Fix potential data-race in __nft_expr_type_get() (CVE-2024-27020)\n  * kernel: netfilter: nf_tables: Fix potential data-race in __nft_obj_type_get() (CVE-2024-27019)\n  * kernel: netfilter: flowtable: validate pppoe header (CVE-2024-27016)\n  * kernel: netfilter: bridge: confirm multicast packets before passing them up the stack (CVE-2024-27415)\n  * kernel: netfilter: bridge: replace physindev with physinif in nf_bridge_info (CVE-2024-35839)\n  * kernel: netfilter: nf_tables: Fix potential data-race in __nft_flowtable_type_get() (CVE-2024-35898)\n  * kernel: netfilter: nf_tables: discard table flag update with pending basechain deletion (CVE-2024-35897)\n  * kernel: netfilter: validate user input for expected length (CVE-2024-35896)\n  * kernel: netfilter: complete validation of user input (CVE-2024-35962)\n  * kernel: ice: fix LAG and VF lock dependency in ice_reset_vf() (CVE-2024-36003)\n  * kernel: cxl/port: Fix delete_endpoint() vs parent unregistration race (CVE-2023-52771)\n  * kernel: tty: n_gsm: require CAP_NET_ADMIN to attach N_GSM0710 ldisc (CVE-2023-52880)\n  * kernel: scsi: qla2xxx: Fix off by one in qla_edif_app_getstats() (CVE-2024-36025)\n  * kernel: net/mlx5e: Fix netif state handling (CVE-2024-38608)\n  * kernel: crypto: bcm - Fix pointer arithmetic (CVE-2024-38579)\n  * kernel: RDMA/rxe: Fix seg fault in rxe_comp_queue_pkt (CVE-2024-38544)\n  * kernel: bnxt_re: avoid shift undefined behavior in bnxt_qplib_alloc_init_hwq (CVE-2024-38540)\n  * kernel: net: bridge: xmit: make sure we have at least eth header len bytes (CVE-2024-38538)\n  * kernel: md/raid5: fix deadlock that raid5d() wait for itself to clear MD_SB_CHANGE_PENDING (CVE-2024-39476)\n  * kernel: ipv6: fix possible race in __fib6_drop_pcpu_from() (CVE-2024-40905)\n  * kernel: wifi: cfg80211: Lock wiphy in cfg80211_get_station (CVE-2024-40911)\n  * kernel: wifi: mac80211: Fix deadlock in ieee80211_sta_ps_deliver_wakeup() (CVE-2024-40912)\n  * kernel: mm/huge_memory: don\u0026#39;t unpoison huge_zero_folio (CVE-2024-40914)\n  * kernel: wifi: iwlwifi: mvm: check n_ssids before accessing the ssids (CVE-2024-40929)\n  * kernel: net: wwan: iosm: Fix tainted pointer delete is case of region creation fail (CVE-2024-40939)\n  * kernel: wifi: iwlwifi: mvm: don\u0026#39;t read past the mfuart notifcation (CVE-2024-40941)\n  * kernel: seg6: fix parameter passing when calling NF_HOOK() in End.DX4 and End.DX6 behaviors (CVE-2024-40957)\n  * kernel: scsi: qedi: Fix crash while reading debugfs attribute (CVE-2024-40978)\n  * kernel: tipc: force a dst refcount before doing decryption (CVE-2024-40983)\n  * kernel: virtio-net: tap: mlx5_core short frame denial of service (CVE-2024-41090)\n  * kernel: virtio-net: tun: mlx5_core short frame denial of service (CVE-2024-41091)\n  * kernel: udp: Set SOCK_RCU_FREE earlier in udp_lib_get_port() (CVE-2024-41041)\n  * kernel: NFSv4: Fix memory leak in nfs4_set_security_label (CVE-2024-41076)\n  * kernel: net: ntb_netdev: Move ntb_netdev_rx_handler() to call netif_rx() from __netif_rx() (CVE-2024-42110)\n  * kernel: nvmet: fix a possible leak when destroy a ctrl during qp establishment (CVE-2024-42152)\n\n\nFor more details about the security issue(s), including the impact, a CVSS score, acknowledgments, and other related information, refer to the CVE page(s) listed in the References section.\n","status":"published","published":"2024-08-28T00:00:00Z","modified":"2026-10-29T11:31:50.194358891Z","updated_at":"2026-11-02T15:27:52.553233Z"},{"id":"ALSA-2024:7000","title":"Important: kernel security update","description":"The kernel packages contain the Linux kernel, the core of any Linux operating system.  \nSecurity Fix(es):\n\n CVE-2023-6040  CVE-2024-26595  CVE-2024-26600  CVE-2021-46984  CVE-2023-52478  CVE-2023-52476  CVE-2023-52522  CVE-2021-47101  CVE-2021-47097  CVE-2023-52605  CVE-2024-26638  CVE-2024-26645  CVE-2024-26665  CVE-2024-26720  CVE-2024-26717  CVE-2024-26769  CVE-2024-26846  CVE-2024-26894  CVE-2024-26880  CVE-2024-26855  CVE-2024-26923  CVE-2024-26939  CVE-2024-27013  CVE-2024-27042  CVE-2024-35809  CVE-2023-52683  CVE-2024-35884  CVE-2024-35877  CVE-2024-35944  CVE-2024-35989  CVE-2021-47412  CVE-2021-47393  CVE-2021-47386  CVE-2021-47385  CVE-2021-47384  CVE-2021-47383  CVE-2021-47432  CVE-2021-47352  CVE-2021-47338  CVE-2021-47321  CVE-2021-47289  CVE-2021-47287  CVE-2023-52798  CVE-2023-52809  CVE-2023-52817  CVE-2023-52840  CVE-2023-52800  CVE-2021-47441  CVE-2021-47466  CVE-2021-47455  CVE-2021-47497  CVE-2021-47560  CVE-2021-47527  CVE-2024-36883  CVE-2024-36922  CVE-2024-36920  CVE-2024-36902  CVE-2024-36953  CVE-2024-36939  CVE-2024-36919  CVE-2024-36901  CVE-2021-47582  CVE-2021-47609  CVE-2024-38619  CVE-2022-48754  CVE-2022-48760  CVE-2024-38581  CVE-2024-38579  CVE-2024-38570  CVE-2024-38559  CVE-2024-38558  CVE-2024-37356  CVE-2024-39471  CVE-2024-39499  CVE-2024-39501  CVE-2024-39506  CVE-2024-40904  CVE-2024-40911  CVE-2024-40912  CVE-2024-40929  CVE-2024-40931  CVE-2024-40941  CVE-2024-40954  CVE-2024-40958  CVE-2024-40959  CVE-2024-40960  CVE-2024-40972  CVE-2024-40977  CVE-2024-40978  CVE-2024-40988  CVE-2024-40989  CVE-2024-40995  CVE-2024-40997  CVE-2024-40998  CVE-2024-41005  CVE-2024-40901  CVE-2024-41007  CVE-2024-41008  CVE-2022-48804  CVE-2022-48836  CVE-2022-48866  CVE-2024-41090  CVE-2024-41091  CVE-2024-41012  CVE-2024-41013  CVE-2024-41014  CVE-2024-41023  CVE-2024-41035  CVE-2024-41038  CVE-2024-41039  CVE-2024-41040  CVE-2024-41041  CVE-2024-41044  CVE-2024-41055  CVE-2024-41056  CVE-2024-41060  CVE-2024-41064  CVE-2024-41065  CVE-2024-41071  CVE-2024-41076  CVE-2024-41097  CVE-2024-42084  CVE-2024-42090  CVE-2024-42094  CVE-2024-42096  CVE-2024-42114  CVE-2024-42124  CVE-2024-42131  CVE-2024-42152  CVE-2024-42154  CVE-2024-42225  CVE-2024-42226  CVE-2024-42228  CVE-2024-42237  CVE-2024-42238  CVE-2024-42240  CVE-2024-42246  CVE-2024-42322  CVE-2024-43830  CVE-2024-43871  For more details about the security issue(s), including the impact, a CVSS score, acknowledgments, and other related information, refer to the CVE page(s) listed in the References section.","status":"published","published":"2024-09-24T00:00:00Z","modified":"2026-10-29T11:12:05.203537698Z","updated_at":"2026-11-02T15:27:53.030731Z"},{"id":"ALSA-2024:7001","title":"Important: kernel-rt security update","description":"The kernel-rt packages provide the Real Time Linux Kernel, which enables fine-tuning for systems with extremely high determinism requirements.  \nSecurity Fix(es):\n\n CVE-2023-6040  CVE-2024-26595  CVE-2021-46984  CVE-2023-52478  CVE-2023-52476  CVE-2023-52522  CVE-2021-47101  CVE-2021-47097  CVE-2023-52605  CVE-2024-26645  CVE-2024-26665  CVE-2024-26720  CVE-2024-26717  CVE-2024-26769  CVE-2024-26894  CVE-2024-26880  CVE-2024-26855  CVE-2024-26923  CVE-2024-26939  CVE-2024-27013  CVE-2024-27042  CVE-2024-35809  CVE-2023-52683  CVE-2024-35884  CVE-2024-35877  CVE-2024-35944  CVE-2024-35989  CVE-2021-47412  CVE-2021-47393  CVE-2021-47386  CVE-2021-47385  CVE-2021-47384  CVE-2021-47383  CVE-2021-47432  CVE-2021-47352  CVE-2021-47338  CVE-2021-47321  CVE-2021-47289  CVE-2021-47287  CVE-2023-52817  CVE-2023-52840  CVE-2021-47441  CVE-2021-47466  CVE-2021-47455  CVE-2021-47497  CVE-2021-47560  CVE-2021-47527  CVE-2024-36883  CVE-2024-36920  CVE-2024-36902  CVE-2024-36953  CVE-2024-36939  CVE-2024-36901  CVE-2021-47582  CVE-2021-47609  CVE-2024-38619  CVE-2022-48754  CVE-2022-48760  CVE-2024-38581  CVE-2024-38570  CVE-2024-38559  CVE-2024-38558  CVE-2024-37356  CVE-2024-39471  CVE-2024-39499  CVE-2024-39501  CVE-2024-39506  CVE-2024-40904  CVE-2024-40911  CVE-2024-40912  CVE-2024-40929  CVE-2024-40931  CVE-2024-40941  CVE-2024-40954  CVE-2024-40958  CVE-2024-40959  CVE-2024-40960  CVE-2024-40972  CVE-2024-40977  CVE-2024-40978  CVE-2024-40988  CVE-2024-40989  CVE-2024-40995  CVE-2024-40997  CVE-2024-40998  CVE-2024-41005  CVE-2024-40901  CVE-2024-41007  CVE-2024-41008  CVE-2022-48804  CVE-2022-48836  CVE-2022-48866  CVE-2024-41090  CVE-2024-41091  CVE-2024-41012  CVE-2024-41013  CVE-2024-41014  CVE-2024-41035  CVE-2024-41038  CVE-2024-41039  CVE-2024-41040  CVE-2024-41041  CVE-2024-41044  CVE-2024-41055  CVE-2024-41056  CVE-2024-41060  CVE-2024-41071  CVE-2024-41076  CVE-2024-41097  CVE-2024-42084  CVE-2024-42090  CVE-2024-42096  CVE-2024-42114  CVE-2024-42124  CVE-2024-42131  CVE-2024-42152  CVE-2024-42154  CVE-2024-42226  CVE-2024-42228  CVE-2024-42237  CVE-2024-42238  CVE-2024-42240  CVE-2024-42246  CVE-2024-42322  CVE-2024-43871  For more details about the security issue(s), including the impact, a CVSS score, acknowledgments, and other related information, refer to the CVE page(s) listed in the References section.","status":"published","published":"2024-09-24T00:00:00Z","modified":"2026-10-29T11:12:09.653003898Z","updated_at":"2026-11-02T15:27:53.030731Z"},{"id":"CLSA-2024-1728936982","title":"kernel: Fix of 86 CVEs","description":"- drm/amd/pm: Fix negative array index read {CVE-2024-46821}\n- drm/amd/display: Check gpio_id before used as array index {CVE-2024-46818}\n- drm/amd/display: Check link_index before accessing dc-\u003elinks[] {CVE-2024-46813}\n- drm/amd/display: Fix index may exceed array range within fpu_update_bw_bounding_box {CVE-2024-46811}\n- Squashfs: sanity check symbolic link size {CVE-2024-46744}\n- platform/x86: panasonic-laptop: Fix SINF array out of bounds accesses {CVE-2024-46859}\n- net/sched: act_api: fix possible infinite loop in tcf_idr_check_alloc() {CVE-2024-40995}\n- net/sched: act_api: rely on rcu in tcf_idr_check_alloc {CVE-2024-40995}\n- netfilter: bridge: confirm multicast packets before passing them up the stack {CVE-2024-27415}\n- netfilter: let reset rules clean out conntrack entries {CVE-2024-27415}\n- mm/filemap: make MAX_PAGECACHE_ORDER acceptable to xarray {CVE-2024-42243}\n- gpiolib: cdev: Fix use after free in lineinfo_changed_notify {CVE-2024-36899}\n- bpf, sockmap: Prevent lock inversion deadlock in map delete elem {CVE-2024-35895}\n- bpf, sockmap: Fix preempt_rt splat when using raw_spin_lock_t {CVE-2024-35895}\n- mm/huge_memory: don't unpoison huge_zero_folio {CVE-2024-40914}\n- cxgb4: fix use after free bugs caused by circular dependency problem {CVE-2023-4133}\n- timers: Restore ABI Compatibility with timer_delete Functions {CVE-2023-4133}\n- timers: Provide timer_shutdown[_sync]() {CVE-2023-4133}\n- timers: Add shutdown mechanism to the internal functions {CVE-2023-4133}\n- timers: Split [try_to_]del_timer[_sync]() to prepare for shutdown mode {CVE-2023-4133}\n- timers: Silently ignore timers with a NULL function {CVE-2023-4133}\n- timers: Rename del_timer() to timer_delete() {CVE-2023-4133}\n- timers: Rename del_timer_sync() to timer_delete_sync() {CVE-2023-4133}\n- timers: Use del_timer_sync() even on UP {CVE-2023-4133}\n- timers: Update kernel-doc for various functions {CVE-2023-4133}\n- timers: Replace BUG_ON()s {CVE-2023-4133}\n- timers: Get rid of del_singleshot_timer_sync() {CVE-2023-4133}\n- clocksource/drivers/sp804: Do not use timer namespace for timer_shutdown() function {CVE-2023-4133}\n- clocksource/drivers/arm_arch_timer: Do not use timer namespace for timer_shutdown() function {CVE-2023-4133}\n- mm: avoid overflows in dirty throttling logic {CVE-2024-42131}\n- ring-buffer: Fix a race between readers and resize checks {CVE-2024-38601}\n- igc: avoid returning frame twice in XDP_REDIRECT {CVE-2024-26853}\n- igc: Avoid transmit queue timeout for XDP {CVE-2024-26853}\n- nfsd: fix RELEASE_LOCKOWNER {CVE-2024-26629}\n- tty: n_gsm: require CAP_NET_ADMIN to attach N_GSM0710 ldisc {CVE-2023-52880}\n- nvmet: fix a possible leak when destroy a ctrl during qp establishment {CVE-2024-42152}\n- net: ntb_netdev: Move ntb_netdev_rx_handler() to call netif_rx() from __netif_rx() {CVE-2024-42110}\n- x86: stop playing stack games in profile_pc() {CVE-2024-42096}\n- xdp: Remove WARN() from __xdp_reg_mem_model() {CVE-2024-42082}\n- NFSv4: Fix memory leak in nfs4_set_security_label {CVE-2024-41076}\n- ppp: reject claimed-as-LCP but actually malformed packets {CVE-2024-41044}\n- udp: Set SOCK_RCU_FREE earlier in udp_lib_get_port(). {CVE-2024-41041}\n- sched/deadline: Fix task_struct reference leak {CVE-2024-41023}\n- tipc: force a dst refcount before doing decryption {CVE-2024-40983}\n- scsi: qedi: Fix crash while reading debugfs attribute {CVE-2024-40978}\n- wifi: iwlwifi: mvm: don't read past the mfuart notifcation {CVE-2024-40941}\n- wifi: iwlwifi: mvm: check n_ssids before accessing the ssids {CVE-2024-40929}\n- xhci: Handle TD clearing for multiple streams case {CVE-2024-40927}\n- wifi: mac80211: Fix deadlock in ieee80211_sta_ps_deliver_wakeup() {CVE-2024-40912}\n- wifi: cfg80211: Lock wiphy in cfg80211_get_station {CVE-2024-40911}\n- ipv6: fix possible race in __fib6_drop_pcpu_from() {CVE-2024-40905}\n- md/raid5: fix deadlock that raid5d() wait for itself to clear MD_SB_CHANGE_PENDING {CVE-2024-39476}\n- usb-storage: alauda: Check whether the media is initialized {CVE-2024-38619}\n- usb-storage: alauda: Fix uninit-value in alauda_check_media() {CVE-2024-38619}\n- crypto: bcm - Fix pointer arithmetic {CVE-2024-38579}\n- scsi: qedf: Ensure the copied buf is NUL terminated {CVE-2024-38559}\n- wifi: nl80211: don't free NULL coalescing rule {CVE-2024-36941}\n- scsi: qla2xxx: Fix off by one in qla_edif_app_getstats() {CVE-2024-36025}\n- netfilter: nf_tables: Fix potential data-race in __nft_flowtable_type_get() {CVE-2024-35898}\n- mlxsw: spectrum_acl_tcam: Fix memory leak when canceling rehash work {CVE-2024-35852}\n- wifi: iwlwifi: dbg-tlv: ensure NUL termination {CVE-2024-35845}\n- KVM: SVM: Flush pages under kvm-\u003elock to fix UAF in svm_register_enc_region() {CVE-2024-35791}\n- wifi: mac80211: check/clear fast rx for non-4addr sta VLAN changes {CVE-2024-35789}\n- wifi: rtl8xxxu: add cancel_work_sync() for c2hcmd_work {CVE-2024-27052}\n- nfp: flower: handle acti_netdevs allocation failure {CVE-2024-27046}\n- octeontx2-af: Use separate handlers for interrupts {CVE-2024-27030}\n- netfilter: flowtable: validate pppoe header {CVE-2024-27016}\n- kprobes/x86: Use copy_from_kernel_nofault() to read from unsafe address {CVE-2024-26946}\n- scsi: qla2xxx: Fix command flush on cable pull {CVE-2024-26931}\n- net: ice: Fix potential NULL pointer dereference in ice_bridge_setlink() {CVE-2024-26855}\n- bpf: Fix racing between bpf_timer_cancel_and_free and bpf_timer_cancel {CVE-2024-26737}\n- Input: cyapa - add missing input core locking to suspend/resume functions {CVE-2023-52884}\n- bpf, sockmap: Don't let sock_map_{close,destroy,unhash} call itself {CVE-2023-52735}\n- wifi: ath10k: fix NULL pointer dereference in ath10k_wmi_tlv_op_pull_mgmt_tx_compl_ev() {CVE-2023-52651}\n- net: tap_open(): set sk_uid from current_fsuid() {CVE-2023-4194}\n- net: tun_chr_open(): set sk_uid from current_fsuid() {CVE-2023-4194}\n- seg6: fix the iif in the IPv6 socket control block {CVE-2021-47515}\n- tty: Fix out-of-bound vmalloc access in imageblit {CVE-2021-47383}\n- bnx2x: Fix multiple UBSAN array-index-out-of-bounds {CVE-2024-42148}\n- hwmon: (adc128d818) Fix underflows seen when writing limit attributes {CVE-2024-46759}\n- net: bridge: mst: fix vlan use-after-free {CVE-2024-36979}\n- stm class: Fix a double free in stm_register_device() {CVE-2024-38627}\n- wifi: mac80211: Avoid address calculations via out of bounds array indexing {CVE-2024-41071}\n- of/irq: Prevent device address out-of-bounds read in interrupt map walk {CVE-2024-46743}\n- HID: cougar: fix slab-out-of-bounds Read in cougar_report_fixup {CVE-2024-46747}\n- drm/amdgpu: fix mc_data out-of-bounds read warning {CVE-2024-46722}\n- drm/amdgpu: Fix out-of-bounds write warning {CVE-2024-46725}\n- drm/amdgpu: Fix out-of-bounds read of df_v1_7_channel_number {CVE-2024-46724}\n- wifi: nl80211: Avoid address calculations via out of bounds array indexing {CVE-2024-38562}\n- wifi: nl80211: convert cfg80211_scan_request allocation to *_size macros {CVE-2024-38562}\n- overflow: Implement size_t saturating arithmetic helpers {CVE-2024-38562}\n- cdrom: rearrange last_media_change check to avoid unintentional overflow {CVE-2024-42136}\n- ftrace: Fix possible use-after-free issue in ftrace_location() {CVE-2024-38588}\n- ftrace: Fix possible warning on checking all pages used in ftrace_process_locs() {CVE-2024-38588}\n- drm/amdgpu: fix ucode out-of-bounds read warning {CVE-2024-46723}\n- VMCI: Fix use-after-free when removing resource in vmci_resource_remove() {CVE-2024-46738}\n- sch/netem: fix use after free in netem_dequeue {CVE-2024-46800}\n- firmware: cs_dsp: Fix overflow checking of wmfw header {CVE-2024-41039}\n- hwmon: (lm95234) Fix underflows seen when writing limit attributes {CVE-2024-46758}\n- HID: amd_sfh: free driver_data after destroying hid device {CVE-2024-46746}\n- xfs: don't walk off the end of a directory data block {CVE-2024-41013}\n- hwmon: (w83627ehf) Fix underflows seen when writing limit attributes {CVE-2024-46756}\n- tunnels: fix out of bounds access when building IPv6 PMTU error {CVE-2024-26665}\n- hwmon: (nct6775-core) Fix underflows seen when writing limit attributes {CVE-2024-46757}\n- drm/amd/pm: fix the Out-of-bounds read warning {CVE-2024-46731}\n- drm/amdgpu/mes: fix mes ring buffer overflow {CVE-2024-46700}\n- exec: Fix ToCToU between perm check and set-uid/gid usage {CVE-2024-43882}\n- PCI/MSI: Fix UAF in msi_capability_init {CVE-2024-41096}","status":"published","published":"2024-10-14T20:16:26Z","modified":"2026-10-21T10:45:20.569978861Z","updated_at":"2026-11-02T15:43:41.281406Z"},{"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":"DSA-5747-1","title":"linux - security update","status":"published","published":"2024-08-12T00:00:00Z","modified":"2026-03-09T02:11:28.383934Z","updated_at":"2026-11-02T15:46:17.892347Z"},{"id":"MGASA-2024-0277","title":"Updated kernel, kmod-xtables-addons \u0026 kmod-virtualbox packages fix security vulnerabilities","description":"Upstream kernel version 6.6.43 fix 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-08-07T05:49:38Z","modified":"2026-04-16T04:44:39.180015787Z","updated_at":"2026-11-02T15:49:42.684501Z"},{"id":"MGASA-2024-0278","title":"Updated kernel-linus packages fix security vulnerabilities","description":"Vanilla upstream kernel version 6.6.43 fix bugs and vulnerabilities.\nFor information about the vulnerabilities see the links.\n","status":"published","published":"2024-08-07T05:49:38Z","modified":"2026-04-16T04:42:04.810853602Z","updated_at":"2026-11-02T15:49:42.684501Z"},{"id":"RLSA-2024:7001","title":"Important: kernel-rt security update","description":"The kernel-rt packages provide the Real Time Linux Kernel, which enables fine-tuning for systems with extremely high determinism requirements.  \nSecurity Fix(es):\n\n CVE-2023-6040  CVE-2024-26595  CVE-2021-46984  CVE-2023-52478  CVE-2023-52476  CVE-2023-52522  CVE-2021-47101  CVE-2021-47097  CVE-2023-52605  CVE-2024-26645  CVE-2024-26665  CVE-2024-26720  CVE-2024-26717  CVE-2024-26769  CVE-2024-26894  CVE-2024-26880  CVE-2024-26855  CVE-2024-26923  CVE-2024-26939  CVE-2024-27013  CVE-2024-27042  CVE-2024-35809  CVE-2023-52683  CVE-2024-35884  CVE-2024-35877  CVE-2024-35944  CVE-2024-35989  CVE-2021-47412  CVE-2021-47393  CVE-2021-47386  CVE-2021-47385  CVE-2021-47384  CVE-2021-47383  CVE-2021-47432  CVE-2021-47352  CVE-2021-47338  CVE-2021-47321  CVE-2021-47289  CVE-2021-47287  CVE-2023-52817  CVE-2023-52840  CVE-2021-47441  CVE-2021-47466  CVE-2021-47455  CVE-2021-47497  CVE-2021-47560  CVE-2021-47527  CVE-2024-36883  CVE-2024-36920  CVE-2024-36902  CVE-2024-36953  CVE-2024-36939  CVE-2024-36901  CVE-2021-47582  CVE-2021-47609  CVE-2024-38619  CVE-2022-48754  CVE-2022-48760  CVE-2024-38581  CVE-2024-38570  CVE-2024-38559  CVE-2024-38558  CVE-2024-37356  CVE-2024-39471  CVE-2024-39499  CVE-2024-39501  CVE-2024-39506  CVE-2024-40904  CVE-2024-40911  CVE-2024-40912  CVE-2024-40929  CVE-2024-40931  CVE-2024-40941  CVE-2024-40954  CVE-2024-40958  CVE-2024-40959  CVE-2024-40960  CVE-2024-40972  CVE-2024-40977  CVE-2024-40978  CVE-2024-40988  CVE-2024-40989  CVE-2024-40995  CVE-2024-40997  CVE-2024-40998  CVE-2024-41005  CVE-2024-40901  CVE-2024-41007  CVE-2024-41008  CVE-2022-48804  CVE-2022-48836  CVE-2022-48866  CVE-2024-41090  CVE-2024-41091  CVE-2024-41012  CVE-2024-41013  CVE-2024-41014  CVE-2024-41035  CVE-2024-41038  CVE-2024-41039  CVE-2024-41040  CVE-2024-41041  CVE-2024-41044  CVE-2024-41055  CVE-2024-41056  CVE-2024-41060  CVE-2024-41071  CVE-2024-41076  CVE-2024-41097  CVE-2024-42084  CVE-2024-42090  CVE-2024-42096  CVE-2024-42114  CVE-2024-42124  CVE-2024-42131  CVE-2024-42152  CVE-2024-42154  CVE-2024-42226  CVE-2024-42228  CVE-2024-42237  CVE-2024-42238  CVE-2024-42240  CVE-2024-42246  CVE-2024-42322  CVE-2024-43871  For more details about the security issue(s), including the impact, a CVSS score, acknowledgments, and other related information, refer to the CVE page(s) listed in the References section.","status":"published","published":"2024-09-30T14:30:43.714585Z","modified":"2026-02-05T07:45:08.276415Z","updated_at":"2026-11-02T15:53:24.923365Z"},{"id":"SUSE-SU-2024:3190-1","title":"Security update for the Linux Kernel","description":"\nThe SUSE Linux Enterprise 15 SP5 Azure kernel was updated to receive various security bugfixes.\n\nThe following security bugs were fixed:\n\n- CVE-2024-44947: Initialize beyond-EOF page contents before setting uptodate (bsc#1229454).\n- CVE-2024-36936: Touch soft lockup during memory accept (bsc#1225773).\n- CVE-2022-48706: Do proper cleanup if IFCVF init fails (bsc#1225524).\n- CVE-2024-43883: Do not drop references before new references are gained (bsc#1229707).\n- CVE-2024-41062: Sync sock recv cb and release (bsc#1228576).\n- CVE-2024-43861: Fix memory leak for not ip packets (bsc#1229500).\n- CVE-2023-52489: Fix race in accessing memory_section-\u003eusage (bsc#1221326).\n- CVE-2024-43893: Check uartclk for zero to avoid divide by zero (bsc#1229759).\n- CVE-2024-43821: Fix a possible null pointer dereference (bsc#1229315).\n- CVE-2024-43900: Avoid use-after-free in load_firmware_cb() (bsc#1229756).\n- CVE-2024-44938: Fix shift-out-of-bounds in dbDiscardAG (bsc#1229792).\n- CVE-2024-44939: fix null ptr deref in dtInsertEntry (bsc#1229820).\n- CVE-2024-41087: Fix double free on error (CVE-2024-41087,bsc#1228466).\n- CVE-2024-42277: Avoid NULL deref in sprd_iommu_hw_en (bsc#1229409).\n- CVE-2024-43902: Add null checker before passing variables (bsc#1229767).\n- CVE-2024-43904: Add null checks for 'stream' and 'plane' before dereferencing (bsc#1229768)\n- CVE-2024-43880: Put back removed metod in struct objagg_ops (bsc#1229481).\n- CVE-2024-43884: Add error handling to pair_device() (bsc#1229739)\n- CVE-2024-43899: Fix null pointer deref in dcn20_resource.c (bsc#1229754).\n- CVE-2022-48920: Get rid of warning on transaction commit when using flushoncommit (bsc#1229658).\n- CVE-2023-52906: Fix warning during failed attribute validation (bsc#1229527).\n- CVE-2024-43882: Fixed ToCToU between perm check and set-uid/gid usage. (bsc#1229503)\n- CVE-2024-43866: Always drain health in shutdown callback (bsc#1229495).\n- CVE-2024-26812: Struct virqfd kABI workaround (bsc#1222808).\n- CVE-2022-48912: Fix use-after-free in __nf_register_net_hook() (bsc#1229641)\n- CVE-2024-27010: Fix mirred deadlock on device recursion (bsc#1223720).\n- CVE-2022-48906: Correctly set DATA_FIN timeout when number of retransmits is large (bsc#1229605)\n- CVE-2024-42155: Wipe copies of protected- and secure-keys (bsc#1228733).\n- CVE-2024-42156: Wipe copies of clear-key structures on failure (bsc#1228722).\n- CVE-2023-52899: Add exception protection processing for vd in axi_chan_handle_err function (bsc#1229569).\n- CVE-2024-42158: Use kfree_sensitive() to fix Coccinelle warnings (bsc#1228720).\n- CVE-2024-26631: Fix data-race in ipv6_mc_down / mld_ifc_work (bsc#1221630).\n- CVE-2024-43873: Always initialize seqpacket_allow (bsc#1229488)\n- CVE-2024-40905: Fix possible race in __fib6_drop_pcpu_from() (bsc#1227761)\n- CVE-2024-39489: Fix memleak in seg6_hmac_init_algo (bsc#1227623)\n- CVE-2021-47106: Fix use-after-free in nft_set_catchall_destroy() (bsc#1220962)\n- CVE-2021-47517: Fix panic when interrupt coaleceing is set via ethtool (bsc#1225428).\n- CVE-2024-36489: Fix missing memory barrier in tls_init (bsc#1226874)\n- CVE-2024-41020: Fix fcntl/close race recovery compat path (bsc#1228427).\n- CVE-2024-27079: Fix NULL domain on device release (bsc#1223742).\n- CVE-2024-35897: Discard table flag update with pending basechain deletion (bsc#1224510).\n- CVE-2024-27403: Restore const specifier in flow_offload_route_init() (bsc#1224415).\n- CVE-2024-27011: Fix memleak in map from abort path (bsc#1223803).\n- CVE-2024-43819: Reject memory region operations for ucontrol VMs (bsc#1229290 git-fixes).\n- CVE-2024-26668: Reject configurations that cause integer overflow (bsc#1222335).\n- CVE-2024-26835: Set dormant flag on hook register failure (bsc#1222967).\n- CVE-2024-26808: Handle NETDEV_UNREGISTER for inet/ingress basechain (bsc#1222634).\n- CVE-2024-27016: Validate pppoe header (bsc#1223807).\n- CVE-2024-35945: Prevent nullptr exceptions on ISR (bsc#1224639).\n- CVE-2023-52581: Fix memleak when more than 255 elements expired (bsc#1220877).\n- CVE-2024-36013: Fix slab-use-after-free in l2cap_connect() (bsc#1225578).\n- CVE-2024-43837: Fix updating attached freplace prog in prog_array map (bsc#1229297).\n- CVE-2024-42291: Add a per-VF limit on number of FDIR filters (bsc#1229374).\n- CVE-2024-42268: Fix missing lock on sync reset reload (bsc#1229391).\n- CVE-2024-43834: Fix invalid wait context of page_pool_destroy() (bsc#1229314)\n- CVE-2024-36286: Acquire rcu_read_lock() in instance_destroy_rcu() (bsc#1226801)\n- CVE-2024-26851: Add protection for bmp length out of range (bsc#1223074)\n- CVE-2024-42157: Wipe sensitive data on failure (bsc#1228727 CVE-2024-42157 git-fixes).\n- CVE-2024-26677: Blacklist e7870cf13d20 ('rxrpc: Fix delayed ACKs to not set the reference serial number') (bsc#1222387)\n- CVE-2024-36009: Blacklist 467324bcfe1a ('ax25: Fix netdev refcount issue') (bsc#1224542)\n- CVE-2023-52859: Fix use-after-free when register pmu fails (bsc#1225582).\n- CVE-2024-42280: Fix a use after free in hfcmulti_tx() (bsc#1229388)\n- CVE-2024-42284: Return non-zero value from tipc_udp_addr2str() on error (bsc#1229382)\n- CVE-2024-42283: Initialize all fields in dumped nexthops (bsc#1229383)\n- CVE-2024-42312: Always initialize i_uid/i_gid (bsc#1229357)\n- CVE-2024-43854: Initialize integrity buffer to zero before writing it to media (bsc#1229345)\n- CVE-2024-42322: Properly dereference pe in ip_vs_add_service (bsc#1229347)\n- CVE-2024-42301: Fix the array out-of-bounds risk (bsc#1229407).\n- CVE-2024-42318: Do not lose track of restrictions on cred_transfer (bsc#1229351).\n- CVE-2024-26669: Fix chain template offload (bsc#1222350).\n- CVE-2023-52889: Fix null pointer deref when receiving skb during sock creation (bsc#1229287,).\n- CVE-2022-48645: Move enetc_set_psfp() out of the common enetc_set_features() (bsc#1223508).\n- CVE-2024-41007: Use signed arithmetic in tcp_rtx_probe0_timed_out() (bsc#1227863).\n- CVE-2024-36933: Use correct mac_offset to unwind gso skb in nsh_gso_segment() (bsc#1225832).\n- CVE-2024-42295: Handle inconsistent state in nilfs_btnode_create_block() (bsc#1229370).\n- CVE-2024-42319: Move devm_mbox_controller_register() after devm_pm_runtime_enable() (bsc#1229350).\n- CVE-2024-43860: Skip over memory region when node value is NULL (bsc#1229319).\n- CVE-2024-43831: Handle invalid decoder vsi (bsc#1229309).\n- CVE-2024-43849: Protect locator_addr with the main mutex (bsc#1229307).\n- CVE-2024-43841: Do not use strlen() in const context (bsc#1229304).\n- CVE-2024-43839: Adjust 'name' buf size of bna_tcb and bna_ccb structures (bsc#1229301).\n- CVE-2024-41088: Fix infinite loop when xmit fails (bsc#1228469).\n- CVE-2024-42281: Fix a segment issue when downgrading gso_size (bsc#1229386).\n- CVE-2024-42271: Fixed a use after free in iucv_sock_close(). (bsc#1229400)\n- CVE-2024-41080: Fix possible deadlock in io_register_iowq_max_workers() (bsc#1228616).\n- CVE-2024-42246: Remap EPERM in case of connection failure in xs_tcp_setup_socket (bsc#1228989).\n- CVE-2024-42232: Fixed a race between delayed_work() and ceph_monc_stop(). (bsc#1228959)\n- CVE-2024-26735: Fix possible use-after-free and null-ptr-deref (bsc#1222372).\n- CVE-2024-42106: Initialize pad field in struct inet_diag_req_v2 (bsc#1228493).\n- CVE-2024-38662: Cover verifier checks for mutating sockmap/sockhash (bsc#1226885).\n- CVE-2024-42110: Move ntb_netdev_rx_handler() to call netif_rx() from __netif_rx() (bsc#1228501).\n- CVE-2024-42247: Avoid unaligned 64-bit memory accesses (bsc#1228988).\n- CVE-2022-48865: Fix kernel panic when enabling bearer (bsc#1228065).\n- CVE-2023-52498: Fix possible deadlocks in core system-wide PM code (bsc#1221269).\n- CVE-2024-41068: Fix sclp_init() cleanup on failure (bsc#1228579).\n- CVE-2022-48808: Fix panic when DSA master device unbinds on shutdown (bsc#1227958).\n- CVE-2024-42095: Fix Errata i2310 with RX FIFO level check (bsc#1228446).\n- CVE-2024-40978: Fix crash while reading debugfs attribute (bsc#1227929).\n- CVE-2024-42107: Do not process extts if PTP is disabled (bsc#1228494).\n- CVE-2024-42139: Fix improper extts handling (bsc#1228503).\n- CVE-2024-42148: Fix multiple UBSAN array-index-out-of-bounds (bsc#1228487).\n- CVE-2024-42142: E-switch, Create ingress ACL when needed (bsc#1228491).\n- CVE-2024-42162: Account for stopped queues when reading NIC stats (bsc#1228706).\n- CVE-2024-42082: Remove WARN() from __xdp_reg_mem_model() (bsc#1228482).\n- CVE-2024-41042: Prefer nft_chain_validate (bsc#1228526).\n- CVE-2023-3610: Fixed use-after-free vulnerability in nf_tables can be exploited to achieve local privilege escalation (bsc#1213580).\n- CVE-2024-42228: Using uninitialized value *size when calling amdgpu_vce_cs_reloc (bsc#1228667).\n- CVE-2024-40995: Fix possible infinite loop in tcf_idr_check_alloc() (bsc#1227830).\n- CVE-2024-38602: Merge repeat codes in ax25_dev_device_down() (git-fixes CVE-2024-38602 bsc#1226613).\n- CVE-2024-38554: Fix reference count leak issue of net_device (bsc#1226742).\n- CVE-2024-36929: Reject skb_copy(_expand) for fraglist GSO skbs (bsc#1225814).\n- CVE-2024-41009: Fix overrunning reservations in ringbuf (bsc#1228020).\n- CVE-2024-27024: Fix WARNING in rds_conn_connect_if_down (bsc#1223777).\n\nThe following non-security bugs were fixed:\n\n- ACPI: bus: Indicate support for IRQ ResourceSource thru _OSC (git-fixes).\n- ACPI: bus: Indicate support for the Generic Event Device thru _OSC (git-fixes).\n- ACPI: bus: Rework system-level device notification handling (git-fixes).\n- ACPI: thermal: Drop nocrt parameter (git-fixes).\n- ACPI: x86: s2idle: Post-increment variables when getting constraints (git-fixes).\n- afs: Do not cross .backup mountpoint from backup volume (git-fixes).\n- ALSA: hda: Add HP MP9 G4 Retail System AMS to force connect list (stable-fixes).\n- ALSA: hda/hdmi: Yet more pin fix for HP EliteDesk 800 G4 (stable-fixes).\n- ALSA: hda/realtek: Add Framework Laptop 13 (Intel Core Ultra) to quirks (stable-fixes).\n- ALSA: hda/realtek: Fix noise from speakers on Lenovo IdeaPad 3 15IAU7 (git-fixes).\n- ALSA: line6: Fix racy access to midibuf (stable-fixes).\n- ALSA: timer: Relax start tick time check for slave timer elements (git-fixes).\n- ALSA: usb-audio: Add delay quirk for VIVO USB-C-XE710 HEADSET (stable-fixes).\n- ALSA: usb-audio: Re-add ScratchAmp quirk entries (git-fixes).\n- ALSA: usb-audio: Support Yamaha P-125 quirk entry (stable-fixes).\n- ALSA: usb: Fix UBSAN warning in parse_audio_unit() (stable-fixes).\n- arm64: ACPI: NUMA: initialize all values of acpi_early_node_map to (git-fixes)\n- arm64: ACPI: NUMA: initialize all values of acpi_early_node_map to (git-fixes)\n- arm64: Add Neoverse-V2 part (git-fixes)\n- arm64: armv8_deprecated: Fix warning in isndep cpuhp starting process (git-fixes)\n- arm64: armv8_deprecated: Fix warning in isndep cpuhp starting process (git-fixes)\n- arm64: barrier: Restore spec_bar() macro (git-fixes)\n- arm64: cpufeature: Add missing .field_width for GIC system registers (git-fixes)\n- arm64: cpufeature: Fix the visibility of compat hwcaps (git-fixes)\n- arm64: cpufeature: Force HWCAP to be based on the sysreg visible to (git-fixes)\n- arm64: cputype: Add Cortex-A720 definitions (git-fixes)\n- arm64: cputype: Add Cortex-A725 definitions (git-fixes)\n- arm64: cputype: Add Cortex-X1C definitions (git-fixes)\n- arm64: cputype: Add Cortex-X3 definitions (git-fixes)\n- arm64: cputype: Add Cortex-X4 definitions (git-fixes)\n- arm64: cputype: Add Cortex-X925 definitions (git-fixes)\n- arm64: cputype: Add Neoverse-V3 definitions (git-fixes)\n- arm64: dts: rockchip: Increase VOP clk rate on RK3328 (git-fixes)\n- arm64: dts: rockchip: Increase VOP clk rate on RK3328 (git-fixes)\n- arm64: errata: Add workaround for Arm errata 3194386 and 3312417 (git-fixes)\n- arm64: errata: Expand speculative SSBS workaround (again) (git-fixes)\n- arm64: errata: Expand speculative SSBS workaround (git-fixes)\n- arm64: errata: Unify speculative SSBS errata logic (git-fixes) Also update default configuration.\n- arm64: Fix KASAN random tag seed initialization (git-fixes)\n- arm64: Fix KASAN random tag seed initialization (git-fixes)\n- ASoC: codecs: wcd938x-sdw: Correct Soundwire ports mask (git-fixes).\n- ASoC: codecs: wsa881x: Correct Soundwire ports mask (git-fixes).\n- ASoC: meson: axg-fifo: fix irq scheduling issue with PREEMPT_RT (git-fixes).\n- async: Introduce async_schedule_dev_nocall() (bsc#1221269).\n- async: Split async_schedule_node_domain() (bsc#1221269).\n- Bluetooth: Fix usage of __hci_cmd_sync_status (git-fixes).\n- Bluetooth: hci_core: Fix not handling hibernation actions (git-fixes).\n- Bluetooth: l2cap: always unlock channel in l2cap_conless_channel() (git-fixes).\n- Bluetooth: L2CAP: Fix deadlock (git-fixes).\n- bpf: Fix a kernel verifier crash in stacksafe() (bsc#1225903).\n- bpf: kprobe: remove unused declaring of bpf_kprobe_override (git-fixes).\n- btrfs: fix leak of qgroup extent records after transaction abort (git-fixes).\n- btrfs: make btrfs_destroy_delayed_refs() return void (git-fixes).\n- btrfs: remove unnecessary prototype declarations at disk-io.c (git-fixes).\n- btrfs: sysfs: update fs features directory asynchronously (bsc#1226168).\n- cachefiles: propagate errors from vfs_getxattr() to avoid infinite loop (bsc#1229418).\n- ceph: issue a cap release immediately if no cap exists (bsc#1225162).\n- ceph: periodically flush the cap releases (bsc#1225162).\n- cpu/SMT: Enable SMT only if a core is online (bsc#1214285 bsc#1205462 ltc#200161 ltc#200588 git-fixes).\n- cpuidle, ACPI: Evaluate LPI arch_flags for broadcast timer (git-fixes).\n- docs: KVM: Fix register ID of SPSR_FIQ (git-fixes).\n- drm: add missing MODULE_DESCRIPTION() macros (stable-fixes).\n- drm: panel-orientation-quirks: Add labels for both Valve Steam Deck revisions (stable-fixes).\n- drm: panel-orientation-quirks: Add quirk for Aya Neo KUN (stable-fixes).\n- drm: panel-orientation-quirks: Add quirk for Lenovo Yoga Tab 3 X90F (stable-fixes).\n- drm: panel-orientation-quirks: Add quirk for Nanote UMPC-01 (stable-fixes).\n- drm: panel-orientation-quirks: Add quirk for OrangePi Neo (stable-fixes).\n- drm/amd/amdgpu/imu_v11_0: Increase buffer size to ensure all possible values can be stored (stable-fixes).\n- drm/amd/display: Add NULL check for 'afb' before dereferencing in amdgpu_dm_plane_handle_cursor_update (stable-fixes).\n- drm/amd/display: avoid using null object of framebuffer (git-fixes).\n- drm/amd/display: Fix \u0026\u0026 vs || typos (git-fixes).\n- drm/amd/display: Skip Recompute DSC Params if no Stream on Link (stable-fixes).\n- drm/amd/display: Validate hw_points_num before using it (stable-fixes).\n- drm/amd/pm: Fix the null pointer dereference for vega10_hwmgr (stable-fixes).\n- drm/amdgpu: Actually check flags for all context ops (stable-fixes).\n- drm/amdgpu: Add lock around VF RLCG interface (stable-fixes).\n- drm/amdgpu: fix dereference null return value for the function amdgpu_vm_pt_parent (stable-fixes).\n- drm/amdgpu: Fix the null pointer dereference to ras_manager (stable-fixes).\n- drm/amdgpu: Validate TA binary size (stable-fixes).\n- drm/amdgpu/jpeg2: properly set atomics vmid field (stable-fixes).\n- drm/amdgpu/pm: Fix the null pointer dereference for smu7 (stable-fixes).\n- drm/amdgpu/pm: Fix the null pointer dereference in apply_state_adjust_rules (stable-fixes).\n- drm/amdgpu/pm: Fix the param type of set_power_profile_mode (stable-fixes).\n- drm/bridge: analogix_dp: properly handle zero sized AUX transactions (stable-fixes).\n- drm/bridge: tc358768: Attempt to fix DSI horizontal timings (stable-fixes).\n- drm/client: fix null pointer dereference in drm_client_modeset_probe (git-fixes).\n- drm/dp_mst: Skip CSN if topology probing is not done yet (stable-fixes).\n- drm/lima: set gp bus_stop bit before hard reset (stable-fixes).\n- drm/msm/dp: reset the link phy params before link training (git-fixes).\n- drm/msm/dpu: cleanup FB if dpu_format_populate_layout fails (git-fixes).\n- drm/msm/dpu: do not play tricks with debug macros (git-fixes).\n- drm/tegra: Zero-initialize iosys_map (stable-fixes).\n- exfat: fix inode-\u003ei_blocks for non-512 byte sector size device (git-fixes).\n- exfat: fix potential deadlock on __exfat_get_dentry_set (git-fixes).\n- exfat: redefine DIR_DELETED as the bad cluster number (git-fixes).\n- exfat: support dynamic allocate bh for exfat_entry_set_cache (git-fixes).\n- fs/netfs/fscache_cookie: add missing 'n_accesses' check (bsc#1229453).\n- fuse: Initialize beyond-EOF page contents before setting uptodate (bsc#1229454).\n- genirq: Add might_sleep() to disable_irq() (git-fixes).\n- genirq: Always limit the affinity to online CPUs (git-fixes).\n- genirq: Do not return error on missing optional irq_request_resources() (git-fixes).\n- genirq: Take the proposed affinity at face value if force==true (git-fixes).\n- genirq/cpuhotplug, x86/vector: Prevent vector leak during CPU offline (git-fixes).\n- genirq/generic_chip: Make irq_remove_generic_chip() irqdomain aware (git-fixes).\n- genirq/ipi: Fix NULL pointer deref in irq_data_get_affinity_mask() (git-fixes).\n- genirq/irqdesc: Do not try to remove non-existing sysfs files (git-fixes).\n- genirq/matrix: Exclude managed interrupts in irq_matrix_allocated() (git-fixes).\n- genirq/msi: Shutdown managed interrupts with unsatifiable affinities (git-fixes).\n- gss_krb5: Fix the error handling path for crypto_sync_skcipher_setkey (git-fixes).\n- hfs: fix to initialize fields of hfs_inode_info after hfs_alloc_inode() (git-fixes).\n- i2c: smbus: Improve handling of stuck alerts (git-fixes).\n- i2c: smbus: Send alert notifications to all devices if source not found (git-fixes).\n- iommu/amd: Convert comma to semicolon (git-fixes).\n- ip6_tunnel: Fix broken GRO (bsc#1229444).\n- ipv6: sr: fix incorrect unregister order (git-fixes).\n- irqdomain: Drop bogus fwspec-mapping error handling (git-fixes).\n- irqdomain: Fix association race (git-fixes).\n- irqdomain: Fix disassociation race (git-fixes).\n- irqdomain: Fix domain registration race (git-fixes).\n- irqdomain: Fix mapping-creation race (git-fixes).\n- irqdomain: Fixed unbalanced fwnode get and put (git-fixes).\n- irqdomain: Look for existing mapping only once (git-fixes).\n- irqdomain: Refactor __irq_domain_alloc_irqs() (git-fixes).\n- irqdomain: Report irq number for NOMAP domains (git-fixes).\n- kprobes: Fix to check symbol prefixes correctly (git-fixes).\n- lockd: move from strlcpy with unused retval to strscpy (git-fixes).\n- memcg: protect concurrent access to mem_cgroup_idr (git-fixes).\n- mm, kmsan: fix infinite recursion due to RCU critical section (git-fixes).\n- mm: prevent derefencing NULL ptr in pfn_section_valid() (git-fixes).\n- mmc: dw_mmc: allow biu and ciu clocks to defer (git-fixes).\n- mmc: mmc_test: Fix NULL dereference on allocation failure (git-fixes).\n- net: ks8851: Fix another TX stall caused by wrong ISR flag handling (git-fixes).\n- net: ks8851: Fix deadlock with the SPI chip variant (git-fixes).\n- net: ks8851: Fix potential TX stall after interface reopen (git-fixes).\n- net: ks8851: Fix TX stall caused by TX buffer overrun (gix-fixes).\n- net: mana: Add support for page sizes other than 4KB on ARM64 (jsc#PED-8491 bsc#1226530).\n- net: mana: Fix doorbell out of order violation and avoid unnecessary doorbell rings (bsc#1229154).\n- net: mana: Fix race of mana_hwc_post_rx_wqe and new hwc response (git-fixes).\n- net: mana: Fix RX buf alloc_size alignment and atomic op panic (bsc#1229086).\n- net: remove two BUG() from skb_checksum_help() (bsc#1229312).\n- net: usb: qmi_wwan: fix memory leak for not ip packets (git-fixes).\n- net/rds: fix possible cp null dereference (git-fixes).\n- net/sched: initialize noop_qdisc owner (git-fixes).\n- nfc: pn533: Add poll mod list filling check (git-fixes).\n- nfs: expose /proc/net/sunrpc/nfs in net namespaces (git-fixes).\n- nfs: make the rpc_stat per net namespace (git-fixes).\n- NFSD: add posix ACLs to struct nfsd_attrs (git-fixes).\n- NFSD: add security label to struct nfsd_attrs (git-fixes).\n- NFSD: fix regression with setting ACLs (git-fixes).\n- NFSD: Fix strncpy() fortify warning (git-fixes).\n- NFSD: Increase NFSD_MAX_OPS_PER_COMPOUND (git-fixes).\n- NFSD: introduce struct nfsd_attrs (git-fixes).\n- NFSD: move from strlcpy with unused retval to strscpy (git-fixes).\n- NFSD: Optimize DRC bucket pruning (git-fixes).\n- nfsd: return error if nfs4_setacl fails (git-fixes).\n- NFSD: set attributes when creating symlinks (git-fixes).\n- nfsd: use locks_inode_context helper (git-fixes).\n- nilfs2: Remove check for PageError (git-fixes).\n- nvme_core: scan namespaces asynchronously (bsc#1224105).\n- ocfs2: use coarse time for new created files (git-fixes).\n- padata: Fix possible divide-by-0 panic in padata_mt_helper() (git-fixes).\n- perf/smmuv3: Enable HiSilicon Erratum 162001900 quirk for HIP08/09 (git-fixes).\n- platform/x86/amd/hsmp: Add support for ACPI based probing (jsc#PED-8779).\n- platform/x86/amd/hsmp: Cache pci_dev in struct hsmp_socket (jsc#PED-8779).\n- platform/x86/amd/hsmp: Change devm_kzalloc() to devm_kcalloc() (jsc#PED-8779).\n- platform/x86/amd/hsmp: Check HSMP support on AMD family of processors (jsc#PED-8779).\n- platform/x86/amd/hsmp: Check num_sockets against MAX_AMD_SOCKETS (jsc#PED-8779).\n- platform/x86/amd/hsmp: Create static func to handle platdev (jsc#PED-8779).\n- platform/x86/amd/hsmp: Define a struct to hold mailbox regs (jsc#PED-8779).\n- platform/x86/amd/hsmp: Move dev from platdev to hsmp_socket (jsc#PED-8779).\n- platform/x86/amd/hsmp: Move hsmp_test to probe (jsc#PED-8779).\n- platform/x86/amd/hsmp: Non-ACPI support for AMD F1A_M00~0Fh (jsc#PED-8779).\n- platform/x86/amd/hsmp: Remove extra parenthesis and add a space (jsc#PED-8779).\n- platform/x86/amd/hsmp: Restructure sysfs group creation (jsc#PED-8779).\n- platform/x86/amd/hsmp: switch to use device_add_groups() (jsc#PED-8779).\n- power: supply: axp288_charger: Fix constant_charge_voltage writes (git-fixes).\n- power: supply: axp288_charger: Round constant_charge_voltage writes down (git-fixes).\n- powerpc: Fail build if using recordmcount with binutils v2.37 (bsc#1194869).\n- powerpc: Mark .opd section read-only (bsc#1194869).\n- powerpc: use generic version of arch_is_kernel_initmem_freed() (bsc#1194869).\n- powerpc: xor_vmx: Add '-mhard-float' to CFLAGS (bsc#1194869).\n- powerpc/64: Set _IO_BASE to POISON_POINTER_DELTA not 0 for CONFIG_PCI=n (bsc#1194869).\n- powerpc/io: Avoid clang null pointer arithmetic warnings (bsc#1194869).\n- powerpc/kexec_file: fix cpus node update to FDT (bsc#1194869).\n- powerpc/kexec: make the update_cpus_node() function public (bsc#1194869).\n- powerpc/kexec: split CONFIG_KEXEC_FILE and CONFIG_CRASH_DUMP (bsc#1194869).\n- powerpc/pseries: Add failure related checks for h_get_mpp and h_get_ppp (bsc#1194869).\n- powerpc/pseries: Whitelist dtl slub object for copying to userspace (bsc#1194869).\n- powerpc/radix: Move some functions into #ifdef CONFIG_KVM_BOOK3S_HV_POSSIBLE (bsc#1194869).\n- powerpc/topology: Check if a core is online (bsc#1214285 bsc#1205462 ltc#200161 ltc#200588 git-fixes).\n- powerpc/xmon: Check cpu id in commands 'c#', 'dp#' and 'dx#' (bsc#1194869).\n- RDMA/mana_ib: Use virtual address in dma regions for MRs (git-fixes).\n- RDMA/rxe: Fix incomplete state save in rxe_requester (git-fixes)\n- RDMA/rxe: Fix rxe_modify_srq (git-fixes)\n- RDMA/rxe: Move work queue code to subroutines (git-fixes)\n- s390/cpacf: get rid of register asm (git-fixes bsc#1227079 bsc#1229187).\n- s390/cpacf: Make use of invalid opcode produce a link error (git-fixes bsc#1227079).\n- s390/cpacf: Split and rework cpacf query functions (git-fixes bsc#1229187).\n- s390/dasd: fix error checks in dasd_copy_pair_store() (git-fixes bsc#1229190).\n- s390/dasd: fix error recovery leading to data corruption on ESE devices (git-fixes bsc#1229573).\n- s390/sclp: Prevent release of buffer in I/O (git-fixes bsc#1229572).\n- s390/uv: Panic for set and remove shared access UVC errors (git-fixes bsc#1229188).\n- spi: spi-fsl-lpspi: Fix scldiv calculation (git-fixes).\n- RDMA/rxe: Handle zero length rdma (git-fixes)\n- sunrpc: add a struct rpc_stats arg to rpc_create_args (git-fixes).\n- SUNRPC: Fix a race to wake a sync task (git-fixes).\n- swiotlb: fix swiotlb_bounce() to do partial sync's correctly (git-fixes).\n- syscalls: fix compat_sys_io_pgetevents_time64 usage (git-fixes).\n- tracing: Return from tracing_buffers_read() if the file has been closed (bsc#1229136 git-fixes).\n- ubifs: add check for crypto_shash_tfm_digest (git-fixes).\n- ubifs: dbg_orphan_check: Fix missed key type checking (git-fixes).\n- ubifs: Fix adding orphan entry twice for the same inode (git-fixes).\n- ubifs: Fix unattached xattr inode if powercut happens after deleting (git-fixes).\n- vfio/pci: fix potential memory leak in vfio_intx_enable() (git-fixes).\n- wifi: iwlwifi: fw: fix wgds rev 3 exact size (git-fixes).\n- wifi: mwifiex: duplicate static structs used in driver instances (git-fixes).\n- x86/APM: drop the duplicate APM_MINOR_DEV macro (git-fixes).\n- x86/insn: Fix PUSH instruction in x86 instruction decoder opcode map (git-fixes).\n- x86/mm: Fix pti_clone_entry_text() for i386 (git-fixes).\n- x86/mtrr: Check if fixed MTRRs exist before saving them (git-fixes).\n- x86/pm: Work around false positive kmemleak report in msr_build_context() (git-fixes).\n- xfs: Fix missing interval for missing_owner in xfs fsmap (git-fixes).\n- xfs: Fix the owner setting issue for rmap query in xfs fsmap (git-fixes).\n- xfs: use XFS_BUF_DADDR_NULL for daddrs in getfsmap code (git-fixes).\n- xhci: Fix Panther point NULL pointer deref at full-speed re-enumeration (git-fixes).\n- xprtrdma: Fix rpcrdma_reqs_reset() (git-fixes).\n","status":"published","published":"2024-09-10T08:46:37Z","modified":"2026-02-04T02:34:20.347313Z","updated_at":"2026-11-02T15:53:55.639015Z"},{"id":"SUSE-SU-2024:3194-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\nThe following security bugs were fixed:\n\n- CVE-2024-41062: Sync sock recv cb and release (bsc#1228576).\n- CVE-2023-52489: Fix race in accessing memory_section-\u003eusage (bsc#1221326).\n- CVE-2024-43821: Fix a possible null pointer dereference (bsc#1229315).\n- CVE-2024-43911: Fix NULL dereference at band check in starting tx ba session (bsc#1229827).\n- CVE-2024-42277: Avoid NULL deref in sprd_iommu_hw_en (bsc#1229409).\n- CVE-2024-43880: Put back removed metod in struct objagg_ops (bsc#1229481).\n- CVE-2024-43899: Fix null pointer deref in dcn20_resource.c (bsc#1229754).\n- CVE-2024-43882: Fixed ToCToU between perm check and set-uid/gid usage. (bsc#1229503)\n- CVE-2024-43866: Always drain health in shutdown callback (bsc#1229495).\n- CVE-2024-26812: Struct virqfd kABI workaround (bsc#1222808).\n- CVE-2024-27010: Fix mirred deadlock on device recursion (bsc#1223720).\n- CVE-2024-36270: Fix reference in patches.suse/netfilter-tproxy-bail-out-if-IP-has-been-disabled-on.patch (bsc#1226798)\n- CVE-2024-36881: Reset ptes when close() for wr-protected ones (bsc#1225718).\n- CVE-2024-42316: Fix div-by-zero in vmpressure_calc_level() (bsc#1229353).\n- CVE-2024-43855: Fix deadlock between mddev_suspend and flush bio (bsc#1229342,).\n- CVE-2024-43864: Fix CT entry update leaks of modify header context (bsc#1229496)\n- CVE-2024-26631: Fix data-race in ipv6_mc_down / mld_ifc_work (bsc#1221630).\n- CVE-2024-42109: Unconditionally flush pending work before notifier (bsc#1228505)\n- CVE-2024-41084: Avoid null pointer dereference in region lookup (bsc#1228472)\n- CVE-2024-40905: Fix possible race in __fib6_drop_pcpu_from() (bsc#1227761)\n- CVE-2024-39489: Fix memleak in seg6_hmac_init_algo (bsc#1227623)\n- CVE-2024-36489: Fix missing memory barrier in tls_init (bsc#1226874)\n- CVE-2024-27079: Add kABI workaround patch (bsc#1223742).\n- CVE-2024-41020: Fix fcntl/close race recovery compat path (bsc#1228427).\n- CVE-2024-35897: Discard table flag update with pending basechain deletion (bsc#1224510).\n- CVE-2024-27403: Restore const specifier in flow_offload_route_init() (bsc#1224415).\n- CVE-2024-27011: Fix memleak in map from abort path (bsc#1223803).\n- CVE-2024-26668: Reject configurations that cause integer overflow (bsc#1222335).\n- CVE-2024-26835: Set dormant flag on hook register failure (bsc#1222967).\n- CVE-2024-26808: Handle NETDEV_UNREGISTER for inet/ingress basechain (bsc#1222634).\n- CVE-2024-26809: Release elements in clone only from destroy path (bsc#1222633).\n- CVE-2023-52581: Fix memleak when more than 255 elements expired (bsc#1220877).\n- CVE-2024-43837: Fix updating attached freplace prog in prog_array map (bsc#1229297).\n- CVE-2024-35939: Fixed leak pages on dma_set_decrypted() failure (bsc#1224535).\n- CVE-2024-42291: Add a per-VF limit on number of FDIR filters (bsc#1229374).\n- CVE-2024-42268: Fix missing lock on sync reset reload (bsc#1229391).\n- CVE-2024-43834: Fix invalid wait context of page_pool_destroy() (bsc#1229314)\n- CVE-2024-27433: Fix an error handling path in clk_mt8135_apmixed_probe() (bsc#1224711).\n- CVE-2024-36286: Acquire rcu_read_lock() in instance_destroy_rcu() (bsc#1226801)\n- CVE-2024-26851: Add protection for bmp length out of range (bsc#1223074)\n- CVE-2024-40920: Fix suspicious rcu usage in br_mst_set_state (bsc#1227781).\n- CVE-2024-40921: Pass vlan group directly to br_mst_vlan_set_state (bsc#1227784).\n- CVE-2024-36979: Fix vlan use-after-free (bsc#1226604).\n- CVE-2024-26590: Fix inconsistent per-file compression format (bsc#1220252,).\n- CVE-2023-52859: Fix use-after-free when register pmu fails (bsc#1225582).\n- CVE-2024-42270: Fix null-ptr-deref in iptable_nat_table_init() (bsc#1229404)\n- CVE-2024-42269: Fix potential null-ptr-deref in ip6table_nat_table_init() (bsc#1229402)\n- CVE-2024-42284: Return non-zero value from tipc_udp_addr2str() on error (bsc#1229382)\n- CVE-2024-42283: Initialize all fields in dumped nexthops (bsc#1229383)\n- CVE-2024-42312: Always initialize i_uid/i_gid (bsc#1229357)\n- CVE-2024-43854: Initialize integrity buffer to zero before writing it to media (bsc#1229345)\n- CVE-2024-42322: Properly dereference pe in ip_vs_add_service (bsc#1229347)\n- CVE-2024-42308: Update DRM patch reference (bsc#1229411)\n- CVE-2024-42301: Update parport patch reference (bsc#1229407)\n- CVE-2024-42290: Handle runtime power management correctly (bsc#1229379).\n- CVE-2024-42318: Do not lose track of restrictions on cred_transfer (bsc#1229351).\n- CVE-2023-52889: Fix null pointer deref when receiving skb during sock creation (bsc#1229287,).\n- CVE-2024-42295: Handle inconsistent state in nilfs_btnode_create_block() (bsc#1229370).\n- CVE-2024-43850: Fix refcount imbalance seen during bwmon_remove (bsc#1229316).\n- CVE-2024-43831: Handle invalid decoder vsi (bsc#1229309).\n- CVE-2024-43839: Adjust 'name' buf size of bna_tcb and bna_ccb structures (bsc#1229301).\n- CVE-2024-41007: Use signed arithmetic in tcp_rtx_probe0_timed_out() (bsc#1227863).\n- CVE-2024-42281: Fix a segment issue when downgrading gso_size (bsc#1229386).\n- CVE-2024-26669: kABI fix for --Fix chain template offload (bsc#1222350).\n- CVE-2024-26677: kABI fix for -Fix delayed ACKs to not set the reference serial number (bsc#1222387).\n- CVE-2024-41050: Cyclic allocation of msg_id to avoid reuse (bsc#1228499).\n- CVE-2024-41051: Wait for ondemand_object_worker to finish when dropping object (bsc#1228468).\n- CVE-2024-41074: Set object to close if ondemand_id \u003e 0 in copen (bsc#1228643).\n- CVE-2024-41075: Add consistency check for copen/cread (bsc#1228646).\n- CVE-2024-41012: Remove locks reliably when fcntl/close race is detected (bsc#1228247).\n- CVE-2024-41080: Fix possible deadlock in io_register_iowq_max_workers() (bsc#1228616).\n- CVE-2024-42246: Remap EPERM in case of connection failure in xs_tcp_setup_socket (bsc#1228989).\n- CVE-2024-42159: Use proper format specifier in mpi3mr_sas_port_add() (bsc#1228754 CVE-2024-42159 git-fixes).\n- CVE-2024-42241: Disable PMD-sized page cache if needed (bsc#1228986).\n- CVE-2024-42245: Revert 'Make sure to try to detach at least one movable task' (bsc#1228978).\n- CVE-2024-26735: Fix possible use-after-free and null-ptr-deref (bsc#1222372).\n- CVE-2024-26837: Skip MDB replays of deferred events on offload (bsc#1222973).\n- CVE-2024-42155: Wipe copies of protected- and secure-keys (bsc#1228733).\n- CVE-2024-42156: Wipe copies of clear-key structures on failure (bsc#1228722).\n- CVE-2024-42157: Wipe sensitive data on failure (bsc#1228727).\n- CVE-2024-42158: Use kfree_sensitive() to fix Coccinelle warnings (bsc#1228720).\n- CVE-2024-38662: Cover verifier checks for mutating sockmap/sockhash (bsc#1226885).\n- CVE-2024-36911: Do not free decrypted memory (bsc#1225745).\n- CVE-2024-36910: Do not free decrypted memory (bsc#1225717).\n- CVE-2024-36909: Do not free ring buffers that couldn't be re-encrypted (bsc#1225744).\n- CVE-2024-40938: Fix d_parent walk (bsc#1227840).\n- CVE-2024-42247: Avoid unaligned 64-bit memory accesses (bsc#1228988).\n- CVE-2024-41010: Add netlink helper library (bsc#1228021).\n- CVE-2024-42106: Initialize pad field in struct inet_diag_req_v2 (bsc#1228493).\n- CVE-2024-42095: Fix Errata i2310 with RX FIFO level check (bsc#1228446).\n- CVE-2024-41068: Fix sclp_init() cleanup on failure (bsc#1228579).\n- CVE-2024-42138: Fix double memory deallocation in case of invalid INI file (bsc#1228500).\n- CVE-2024-42107: Do not process extts if PTP is disabled (bsc#1228494).\n- CVE-2024-42139: Fix improper extts handling (bsc#1228503).\n- CVE-2024-42110: Move ntb_netdev_rx_handler() to call netif_rx() from __netif_rx() (bsc#1228501).\n- CVE-2024-42113: Initialize num_q_vectors for MSI/INTx interrupts (bsc#1228568).\n- CVE-2024-42148: Fix multiple UBSAN array-index-out-of-bounds (bsc#1228487).\n- CVE-2024-42142: E-switch, Create ingress ACL when needed (bsc#1228491).\n- CVE-2024-42073: Fix memory corruptions on Spectrum-4 systems (bsc#1228457).\n- CVE-2024-42162: Account for stopped queues when reading NIC stats (bsc#1228706).\n- CVE-2024-42082: Remove WARN() from __xdp_reg_mem_model() (bsc#1228482).\n- CVE-2024-40978: Fix crash while reading debugfs attribute (bsc#1227929).\n- CVE-2024-41000: Prefer different overflow check (bsc#1227867).\n- CVE-2024-40995: Fix possible infinite loop in tcf_idr_check_alloc() (bsc#1227830).\n- CVE-2024-42161: Avoid uninitialized value in BPF_CORE_READ_BITFIELD (bsc#1228756).\n- CVE-2024-41069: Fix route memory corruption (bsc#1228644).\n- CVE-2024-39506: Adjust a NULL pointer handling path in lio_vf_rep_copy_packet (bsc#1227729).\n- CVE-2024-42145: Implement a limit on UMAD receive List (bsc#1228743).\n- CVE-2024-40994: Fix integer overflow in max_vclocks_store (bsc#1227829).\n- CVE-2024-42124: Make qedf_execute_tmf() non-preemptible (bsc#1228705).\n- CVE-2024-42096: Stop playing stack games in profile_pc() (bsc#1228633).\n- CVE-2024-42224: Correct check for empty list (bsc#1228723).\n- CVE-2024-41048: Skip zero length skb in sk_msg_recvmsg (bsc#1228565).\n- CVE-2024-40958: Make get_net_ns() handle zero refcount net (bsc#1227812).\n- CVE-2024-40939: Fix tainted pointer delete is case of region creation fail (bsc#1227799).\n- CVE-2024-36933: Restore skb-\u003e{protocol,data,mac_header} for outer header in nsh_gso_segment() (bsc#1225832).\n- CVE-2024-36929: Reject skb_copy(_expand) for fraglist GSO skbs (bsc#1225814).\n- CVE-2024-41044: Reject claimed-as-LCP but actually malformed packets (bsc#1228530).\n- CVE-2024-41066: Add tx check to prevent skb leak (bsc#1228640).\n- CVE-2024-42093: Avoid explicit cpumask var allocation on stack (bsc#1228680).\n- CVE-2024-42122: Add NULL pointer check for kzalloc (bsc#1228591).\n- CVE-2024-41078: Fix quota root leak after quota disable failure (bsc#1228655).\n- CVE-2024-40989: Disassociate vcpus from redistributor region on teardown (bsc#1227823).\n- CVE-2024-41064: Avoid possible crash when edev-\u003epdev changes (bsc#1228599).\n- CVE-2024-41036: Fix deadlock with the SPI chip variant (bsc#1228496)\n- CVE-2024-41040: Fix UAF when resolving a clash (bsc#1228518).\n- CVE-2024-35949: Make sure that WRITTEN is set on all metadata blocks (bsc#1224700).\n- CVE-2024-41081: Block BH in ila_output() (bsc#1228617).\n- CVE-2024-41076: Fix memory leak in nfs4_set_security_label (bsc#1228649).\n- CVE-2024-42079: Fix NULL pointer dereference in gfs2_log_flush (bsc#1228672).\n- CVE-2024-41057: Fix slab-use-after-free in cachefiles_withdraw_cookie() (bsc#1228462).\n- CVE-2024-41058: Fix slab-use-after-free in fscache_withdraw_volume() (bsc#1228459).\n- CVE-2024-41015: Add bounds checking to ocfs2_check_dir_entry() (bsc#1228409).\n- CVE-2024-40956: Fix possible Use-After-Free in irq_process_work_list (bsc#1227810).\n- CVE-2024-27437: Disable auto-enable of exclusive INTx IRQ (bsc#1222625).\n- CVE-2024-41032: Check if a hash-index is in cpu_possible_mask (bsc#1228460)\n- CVE-2024-40957: Fix parameter passing when calling NF_HOOK() in End.DX4 and End.DX6 behaviors (bsc#1227811)\n- CVE-2024-41041: Set SOCK_RCU_FREE earlier in udp_lib_get_port() (bsc#1228520).\n- CVE-2024-40954: Do not leave a dangling sk pointer, when socket creation fails (bsc#1227808)\n- CVE-2024-42070: Fully validate NFT_DATA_VALUE on store to data registers (bsc#1228470).\n- CVE-2024-41070: Prevent UAF in kvm_spapr_tce_attach_iommu_group() (bsc#1228581).\n- CVE-2024-40959: Check ip6_dst_idev() return value in xfrm6_get_saddr() (bsc#1227884).\n- CVE-2024-41009: Fix overrunning reservations in ringbuf (bsc#1228020).\n- CVE-2024-40909: Fix a potential use-after-free in bpf_link_free() (bsc#1227798).\n- CVE-2024-27024: Fix WARNING in rds_conn_connect_if_down (bsc#1223777).\n\nThe following non-security bugs were fixed:\n\n- ACPI: battery: create alarm sysfs attribute atomically (stable-fixes).\n- ACPI: processor_idle: use raw_safe_halt() in acpi_idle_play_dead() (git-fixes).\n- ACPI: SBS: manage alarm sysfs attribute through psy core (stable-fixes).\n- ACPI/NUMA: Apply SRAT proximity domain to entire CFMWS window (git-fixes).\n- afs: fix __afs_break_callback() / afs_drop_open_mmap() race (git-fixes).\n- ALSA: hda: Add HP MP9 G4 Retail System AMS to force connect list (stable-fixes).\n- ALSA: hda: Add HP MP9 G4 Retail System AMS to force connect list (stable-fixes).\n- ALSA: hda: Conditionally use snooping for AMD HDMI (git-fixes).\n- ALSA: hda: conexant: Fix headset auto detect fail in the polling mode (git-fixes).\n- ALSA: hda/hdmi: Yet more pin fix for HP EliteDesk 800 G4 (stable-fixes).\n- ALSA: hda/hdmi: Yet more pin fix for HP EliteDesk 800 G4 (stable-fixes).\n- ALSA: hda/realtek - Fixed ALC256 headphone no sound (stable-fixes).\n- ALSA: hda/realtek - FIxed ALC285 headphone no sound (stable-fixes).\n- ALSA: hda/realtek: Add Framework Laptop 13 (Intel Core Ultra) to quirks (stable-fixes).\n- ALSA: hda/realtek: Add Framework Laptop 13 (Intel Core Ultra) to quirks (stable-fixes).\n- ALSA: hda/realtek: Add quirk for Acer Aspire E5-574G (stable-fixes).\n- ALSA: hda/realtek: Add support for new HP G12 laptops (stable-fixes).\n- ALSA: hda/realtek: Enable mute/micmute LEDs on HP Laptop 14-ey0xxx (stable-fixes).\n- ALSA: hda/realtek: Fix noise from speakers on Lenovo IdeaPad 3 15IAU7 (git-fixes).\n- ALSA: hda/realtek: Fix the speaker output on Samsung Galaxy Book3 Ultra (stable-fixes).\n- ALSA: hda/realtek: Implement sound init sequence for Samsung Galaxy Book3 Pro 360 (stable-fixes).\n- ALSA: hda/realtek: support HP Pavilion Aero 13-bg0xxx Mute LED (stable-fixes).\n- ALSA: hda/tas2781: fix wrong calibrated data order (git-fixes).\n- ALSA: hda/tas2781: Use correct endian conversion (git-fixes).\n- ALSA: line6: Fix racy access to midibuf (stable-fixes).\n- ALSA: line6: Fix racy access to midibuf (stable-fixes).\n- ALSA: seq: Skip event type filtering for UMP events (git-fixes).\n- ALSA: seq: ump: Explicitly reset RPN with Null RPN (stable-fixes).\n- ALSA: seq: ump: Optimize conversions from SysEx to UMP (git-fixes).\n- ALSA: seq: ump: Transmit RPN/NRPN message at each MSB/LSB data reception (stable-fixes).\n- ALSA: seq: ump: Use the common RPN/bank conversion context (stable-fixes).\n- ALSA: timer: Relax start tick time check for slave timer elements (git-fixes).\n- ALSA: ump: Explicitly reset RPN with Null RPN (stable-fixes).\n- ALSA: ump: Transmit RPN/NRPN message at each MSB/LSB data reception (stable-fixes).\n- ALSA: usb-audio: Add delay quirk for VIVO USB-C-XE710 HEADSET (stable-fixes).\n- ALSA: usb-audio: Correct surround channels in UAC1 channel map (git-fixes).\n- ALSA: usb-audio: Re-add ScratchAmp quirk entries (git-fixes).\n- ALSA: usb-audio: Re-add ScratchAmp quirk entries (git-fixes).\n- ALSA: usb-audio: Support Yamaha P-125 quirk entry (stable-fixes).\n- ALSA: usb: Fix UBSAN warning in parse_audio_unit() (stable-fixes).\n- apparmor: unpack transition table if dfa is not present (bsc#1226031).\n- arm64: ACPI: NUMA: initialize all values of acpi_early_node_map to (git-fixes)\n- arm64: Add Neoverse-V2 part (git-fixes)\n- arm64: armv8_deprecated: Fix warning in isndep cpuhp starting process (git-fixes)\n- arm64: barrier: Restore spec_bar() macro (git-fixes)\n- arm64: cputype: Add Cortex-A720 definitions (git-fixes)\n- arm64: cputype: Add Cortex-A725 definitions (git-fixes)\n- arm64: cputype: Add Cortex-X1C definitions (git-fixes)\n- arm64: cputype: Add Cortex-X3 definitions (git-fixes)\n- arm64: cputype: Add Cortex-X4 definitions (git-fixes)\n- arm64: cputype: Add Cortex-X925 definitions (git-fixes)\n- arm64: cputype: Add Neoverse-V3 definitions (git-fixes)\n- arm64: dts: imx8mp: add HDMI power-domains (git-fixes)\n- arm64: dts: imx8mp: Add NPU Node (git-fixes)\n- arm64: dts: imx8mp: Fix pgc vpu locations (git-fixes)\n- arm64: dts: imx8mp: Fix pgc_mlmix location (git-fixes)\n- arm64: errata: Expand speculative SSBS workaround (again) (git-fixes)\n- arm64: errata: Expand speculative SSBS workaround (git-fixes)\n- arm64: errata: Unify speculative SSBS errata logic (git-fixes). Update config files.\n- arm64: Fix KASAN random tag seed initialization (git-fixes)\n- arm64: jump_label: Ensure patched jump_labels are visible to all CPUs (git-fixes)\n- ASoC: allow module autoloading for table board_ids (stable-fixes).\n- ASoC: allow module autoloading for table db1200_pids (stable-fixes).\n- ASoC: amd: acp: fix module autoloading (git-fixes).\n- ASoC: amd: yc: Add quirk entry for OMEN by HP Gaming Laptop 16-n0xxx (bsc#1227182).\n- ASoC: amd: yc: Support mic on HP 14-em0002la (stable-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: Support mic on Lenovo Thinkpad E14 Gen 6 (stable-fixes).\n- ASoC: codecs: wcd938x-sdw: Correct Soundwire ports mask (git-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: wsa881x: Correct Soundwire ports mask (git-fixes).\n- ASoC: codecs: wsa883x: 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: codecs: wsa884x: Correct Soundwire ports mask (git-fixes).\n- ASoC: cs35l45: Checks index of cs35l45_irqs[] (stable-fixes).\n- ASoC: cs35l56: Handle OTP read latency over SoundWire (stable-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: 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: fsl_micfil: Expand the range of FIFO watermark mask (stable-fixes).\n- ASoC: mediatek: mt8188: Mark AFE_DAC_CON0 register as volatile (stable-fixes).\n- ASoC: meson: axg-fifo: fix irq scheduling issue with PREEMPT_RT (git-fixes).\n- ASoC: meson: axg-fifo: fix irq scheduling issue with PREEMPT_RT (git-fixes).\n- ASoC: nau8822: Lower debug print priority (stable-fixes).\n- ASoC: nau8822: Lower debug print priority (stable-fixes).\n- ASoC: SOF: amd: Fix for acp init sequence (git-fixes).\n- ASoC: SOF: Intel: hda-dsp: Make sure that no irq handler is pending before suspend (stable-fixes).\n- ASoC: SOF: ipc4: check return value of snd_sof_ipc_msg_data (stable-fixes).\n- ASoC: SOF: mediatek: Add missing board compatible (stable-fixes).\n- ASoC: SOF: Remove libraries from topology lookups (git-fixes).\n- ASoC: SOF: Remove libraries from topology lookups (git-fixes).\n- ata: libata-scsi: Do not overwrite valid sense data when CK_COND=1 (stable-fixes).\n- ata: libata-scsi: Honor the D_SENSE bit for CK_COND=1 and no error (stable-fixes).\n- Bluetooth: Add device 13d3:3572 IMC Networks Bluetooth Radio (stable-fixes).\n- Bluetooth: bnep: Fix out-of-bound access (stable-fixes).\n- Bluetooth: btintel: Fail setup on error (git-fixes).\n- Bluetooth: btnxpuart: Shutdown timer and prevent rearming when driver unloading (stable-fixes).\n- Bluetooth: btusb: Add Realtek RTL8852BE support ID 0x13d3:0x3591 (stable-fixes).\n- Bluetooth: btusb: Add RTL8852BE device 0489:e125 to device tables (stable-fixes).\n- Bluetooth: Fix usage of __hci_cmd_sync_status (git-fixes).\n- Bluetooth: hci_conn: Check non NULL function before calling for HFP offload (stable-fixes).\n- Bluetooth: hci_core: Fix LE quote calculation (git-fixes).\n- Bluetooth: hci_core: Fix not handling hibernation actions (git-fixes).\n- Bluetooth: hci_sync: avoid dup filtering when passive scanning with adv monitor (git-fixes).\n- Bluetooth: hci_sync: Fix suspending with wrong filter policy (git-fixes).\n- Bluetooth: l2cap: always unlock channel in l2cap_conless_channel() (git-fixes).\n- Bluetooth: L2CAP: Fix deadlock (git-fixes).\n- Bluetooth: MGMT: Add error handling to pair_device() (git-fixes).\n- Bluetooth: SMP: Fix assumption of Central always being Initiator (git-fixes).\n- bnxt_re: Fix imm_data endianness (git-fixes)\n- bpf, arm64: Fix trampoline for BPF_TRAMP_F_CALL_ORIG (git-fixes)\n- bpf, lpm: Fix check prefixlen before walking trie (git-fixes).\n- bpf: Add crosstask check to __bpf_get_stack (git-fixes).\n- bpf: Detect IP == ksym.end as part of BPF program (git-fixes).\n- bpf: do not infer PTR_TO_CTX for programs with unnamed context type (git-fixes).\n- bpf: enforce precision of R0 on callback return (git-fixes).\n- bpf: Ensure proper register state printing for cond jumps (git-fixes).\n- bpf: extract bpf_ctx_convert_map logic and make it more reusable (git-fixes).\n- bpf: Fix a few selftest failures due to llvm18 change (git-fixes).\n- bpf: Fix a kernel verifier crash in stacksafe() (bsc#1225903).\n- bpf: Fix check_stack_write_fixed_off() to correctly spill imm (git-fixes).\n- bpf: fix control-flow graph checking in privileged mode (git-fixes).\n- bpf: Fix kfunc callback register type handling (git-fixes).\n- bpf: Fix prog_array_map_poke_run map poke update (git-fixes).\n- bpf: Fix unnecessary -EBUSY from htab_lock_bucket (git-fixes).\n- bpf: handle bpf_user_pt_regs_t typedef explicitly for PTR_TO_CTX global arg (git-fixes).\n- bpf: hardcode BPF_PROG_PACK_SIZE to 2MB * num_possible_nodes() (git-fixes).\n- bpf: kprobe: remove unused declaring of bpf_kprobe_override (git-fixes).\n- bpf: Mark bpf_spin_{lock,unlock}() helpers with notrace correctly (git-fixes).\n- bpf: Remove unnecessary wait from bpf_map_copy_value() (git-fixes).\n- bpf: Set uattr-\u003ebatch.count as zero before batched update or deletion (git-fixes).\n- bpf: simplify btf_get_prog_ctx_type() into btf_is_prog_ctx_type() (git-fixes).\n- bpf/tests: Remove duplicate JSGT tests (git-fixes).\n- bpftool: Align output skeleton ELF code (git-fixes).\n- bpftool: Fix -Wcast-qual warning (git-fixes).\n- bpftool: mark orphaned programs during prog show (git-fixes).\n- bpftool: Silence build warning about calloc() (git-fixes).\n- btrfs: add a btrfs_finish_ordered_extent helper (git-fixes).\n- btrfs: add a is_data_bbio helper (git-fixes).\n- btrfs: add an ordered_extent pointer to struct btrfs_bio (git-fixes).\n- btrfs: copy dir permission and time when creating a stub subvolume (bsc#1228321).\n- btrfs: ensure fast fsync waits for ordered extents after a write failure (git-fixes).\n- btrfs: factor out a btrfs_queue_ordered_fn helper (git-fixes).\n- btrfs: factor out a can_finish_ordered_extent helper (git-fixes).\n- btrfs: fix corruption after buffer fault in during direct IO append write (git-fixes).\n- btrfs: fix double inode unlock for direct IO sync writes (git-fixes).\n- btrfs: fix extent map use-after-free when adding pages to compressed bio (git-fixes).\n- btrfs: fix leak of qgroup extent records after transaction abort (git-fixes).\n- btrfs: fix ordered extent split error handling in btrfs_dio_submit_io (git-fixes).\n- btrfs: limit write bios to a single ordered extent (git-fixes).\n- btrfs: make btrfs_finish_ordered_extent() return void (git-fixes).\n- btrfs: merge the two calls to btrfs_add_ordered_extent in run_delalloc_nocow (git-fixes).\n- btrfs: open code btrfs_bio_end_io in btrfs_dio_submit_io (git-fixes).\n- btrfs: open code end_extent_writepage in end_bio_extent_writepage (git-fixes).\n- btrfs: pass a btrfs_inode to btrfs_fdatawrite_range() (git-fixes).\n- btrfs: pass a btrfs_inode to btrfs_wait_ordered_range() (git-fixes).\n- btrfs: pass an ordered_extent to btrfs_reloc_clone_csums (git-fixes).\n- btrfs: pass an ordered_extent to btrfs_submit_compressed_write (git-fixes).\n- btrfs: remove btrfs_add_ordered_extent (git-fixes).\n- btrfs: rename err to ret in btrfs_direct_write() (git-fixes).\n- btrfs: uninline some static inline helpers from tree-log.h (git-fixes).\n- btrfs: use a btrfs_inode in the log context (struct btrfs_log_ctx) (git-fixes).\n- btrfs: use a btrfs_inode local variable at btrfs_sync_file() (git-fixes).\n- btrfs: use bbio-\u003eordered in btrfs_csum_one_bio (git-fixes).\n- btrfs: use btrfs_finish_ordered_extent to complete buffered writes (git-fixes).\n- btrfs: use btrfs_finish_ordered_extent to complete compressed writes (git-fixes).\n- btrfs: use btrfs_finish_ordered_extent to complete direct writes (git-fixes).\n- btrfs: use irq safe locking when running and adding delayed iputs (git-fixes).\n- cachefiles, erofs: Fix NULL deref in when cachefiles is not doing ondemand-mode (bsc#1229245).\n- cachefiles: add missing lock protection when polling (bsc#1229256).\n- cachefiles: add restore command to recover inflight ondemand read requests (bsc#1229244).\n- cachefiles: add spin_lock for cachefiles_ondemand_info (bsc#1229249).\n- cachefiles: cancel all requests for the object that is being dropped (bsc#1229255).\n- cachefiles: defer exposing anon_fd until after copy_to_user() succeeds (bsc#1229251).\n- cachefiles: extract ondemand info field from cachefiles_object (bsc#1229240).\n- cachefiles: fix slab-use-after-free in cachefiles_ondemand_daemon_read() (bsc#1229247).\n- cachefiles: fix slab-use-after-free in cachefiles_ondemand_get_fd() (bsc#1229246).\n- cachefiles: introduce object ondemand state (bsc#1229239).\n- cachefiles: make on-demand read killable (bsc#1229252).\n- cachefiles: narrow the scope of triggering EPOLLIN events in ondemand mode (bsc#1229243).\n- cachefiles: never get a new anonymous fd if ondemand_id is valid (bsc#1229250).\n- cachefiles: propagate errors from vfs_getxattr() to avoid infinite loop (bsc#1229253).\n- cachefiles: remove err_put_fd label in cachefiles_ondemand_daemon_read() (bsc#1229248).\n- cachefiles: resend an open request if the read request's object is closed (bsc#1229241).\n- cachefiles: stop sending new request when dropping object (bsc#1229254).\n- can: mcp251xfd: tef: prepare to workaround broken TEF FIFO tail index erratum (stable-fixes).\n- can: mcp251xfd: tef: update workaround for erratum DS80000789E 6 of mcp2518fd (stable-fixes).\n- ceph: periodically flush the cap releases (bsc#1230056).\n- cgroup: Add annotation for holding namespace_sem in current_cgns_cgroup_from_root() (bsc#1222254).\n- cgroup: Eliminate the need for cgroup_mutex in proc_cgroup_show() (bsc#1222254).\n- cgroup: Make operations on the cgroup root_list RCU safe (bsc#1222254).\n- cgroup: preserve KABI of cgroup_root (bsc#1222254).\n- cgroup: Remove unnecessary list_empty() (bsc#1222254).\n- cgroup/cpuset: Prevent UAF in proc_cpuset_show() (bsc#1228801).\n- char: xillybus: Check USB endpoints when probing device (git-fixes).\n- char: xillybus: Do not destroy workqueue from work item running on it (stable-fixes).\n- char: xillybus: Refine workqueue handling (git-fixes).\n- clk: en7523: fix rate divider for slic and spi clocks (git-fixes).\n- clk: qcom: camcc-sc7280: Add parent dependency to all camera GDSCs (git-fixes).\n- clk: qcom: gcc-sa8775p: Update the GDSC wait_val fields and flags (git-fixes).\n- clk: qcom: gcc-sc7280: Update force mem core bit for UFS ICE clock (git-fixes).\n- clk: qcom: gpucc-sa8775p: Park RCG's clk source at XO during disable (git-fixes).\n- clk: qcom: gpucc-sa8775p: Remove the CLK_IS_CRITICAL and ALWAYS_ON flags (git-fixes).\n- clk: qcom: gpucc-sa8775p: Update wait_val fields for GPU GDSC's (git-fixes).\n- clk: qcom: gpucc-sm8350: Park RCG's clk source at XO during disable (git-fixes).\n- clk: qcom: kpss-xcc: Return of_clk_add_hw_provider to transfer the error (git-fixes).\n- clk: qcom: Park shared RCGs upon registration (git-fixes).\n- clk: visconti: Add bounds-checking coverage for struct visconti_pll_provider (stable-fixes).\n- clocksource/drivers/sh_cmt: Address race condition for clock events (stable-fixes).\n- cpu/SMT: Enable SMT only if a core is online (bsc#1214285 bsc#1205462 ltc#200161 ltc#200588 git-fixes).\n- cxl/region: Move cxl_dpa_to_region() work to the region driver (bsc#1228472)\n- dev/parport: fix the array out-of-bounds risk (stable-fixes).\n- device property: Add cleanup.h based fwnode_handle_put() scope based cleanup (stable-fixes).\n- dmaengine: dw: Add memory bus width verification (git-fixes).\n- dmaengine: dw: Add peripheral bus width verification (git-fixes).\n- docs: KVM: Fix register ID of SPSR_FIQ (git-fixes).\n- driver core: Fix uevent_show() vs driver detach race (git-fixes).\n- drm/admgpu: fix dereferencing null pointer context (stable-fixes).\n- drm/amd/display: Add delay to improve LTTPR UHBR interop (stable-fixes).\n- drm/amd/display: Add NULL check for 'afb' before dereferencing in amdgpu_dm_plane_handle_cursor_update (stable-fixes).\n- drm/amd/display: Add null checker before passing variables (stable-fixes).\n- drm/amd/display: Adjust cursor position (git-fixes).\n- drm/amd/display: avoid using null object of framebuffer (git-fixes).\n- drm/amd/display: Check for NULL pointer (stable-fixes).\n- drm/amd/display: fix cursor offset on rotation 180 (git-fixes).\n- drm/amd/display: fix s2idle entry for DCN3.5+ (stable-fixes).\n- drm/amd/display: Skip Recompute DSC Params if no Stream on Link (stable-fixes).\n- drm/amd/pm: Fix the null pointer dereference for vega10_hwmgr (stable-fixes).\n- drm/amdgpu: Actually check flags for all context ops (stable-fixes).\n- drm/amdgpu: Add lock around VF RLCG interface (stable-fixes).\n- drm/amdgpu: fix dereference null return value for the function amdgpu_vm_pt_parent (stable-fixes).\n- drm/amdgpu: fix potential resource leak warning (stable-fixes).\n- drm/amdgpu: Fix the null pointer dereference to ras_manager (stable-fixes).\n- drm/amdgpu: Forward soft recovery errors to userspace (stable-fixes).\n- drm/amdgpu: reset vm state machine after gpu reset(vram lost) (stable-fixes).\n- drm/amdgpu: Validate TA binary size (stable-fixes).\n- drm/amdgpu/jpeg2: properly set atomics vmid field (stable-fixes).\n- drm/amdgpu/jpeg4: properly set atomics vmid field (stable-fixes).\n- drm/amdgpu/pm: Fix the null pointer dereference for smu7 (stable-fixes).\n- drm/amdgpu/pm: Fix the null pointer dereference in apply_state_adjust_rules (stable-fixes).\n- drm/amdgpu/pm: Fix the param type of set_power_profile_mode (stable-fixes).\n- drm/amdgpu/sdma5.2: limit wptr workaround to sdma 5.2.1 (git-fixes).\n- drm/amdgpu/sdma5.2: Update wptr registers as well as doorbell (stable-fixes).\n- drm/bridge: analogix_dp: properly handle zero sized AUX transactions (stable-fixes).\n- drm/client: fix null pointer dereference in drm_client_modeset_probe (git-fixes).\n- drm/dp_mst: Skip CSN if topology probing is not done yet (stable-fixes).\n- drm/etnaviv: do not block scheduler when GPU is still active (stable-fixes).\n- drm/i915: Fix possible int overflow in skl_ddi_calculate_wrpll() (git-fixes).\n- drm/i915/dsi: Make Lenovo Yoga Tab 3 X90F DMI match less strict (git-fixes).\n- drm/i915/gem: Adjust vma offset for framebuffer mmap offset (stable-fixes).\n- drm/i915/gem: Fix Virtual Memory mapping boundaries calculation (git-fixes).\n- drm/i915/hdcp: Fix HDCP2_STREAM_STATUS macro (git-fixes).\n- drm/lima: set gp bus_stop bit before hard reset (stable-fixes).\n- drm/mediatek/dp: Fix spurious kfree() (git-fixes).\n- drm/msm: Reduce fallout of fence signaling vs reclaim hangs (stable-fixes).\n- drm/msm/dp: fix the max supported bpp logic (git-fixes).\n- drm/msm/dp: reset the link phy params before link training (git-fixes).\n- drm/msm/dpu: capture snapshot on the first commit_done timeout (stable-fixes).\n- drm/msm/dpu: cleanup FB if dpu_format_populate_layout fails (git-fixes).\n- drm/msm/dpu: do not play tricks with debug macros (git-fixes).\n- drm/msm/dpu: drop MSM_ENC_VBLANK support (stable-fixes).\n- drm/msm/dpu: move dpu_encoder's connector assignment to atomic_enable() (git-fixes).\n- drm/msm/dpu: split dpu_encoder_wait_for_event into two functions (stable-fixes).\n- drm/msm/dpu: take plane rotation into account for wide planes (git-fixes).\n- drm/msm/dpu: try multirect based on mdp clock limits (stable-fixes).\n- drm/msm/dpu: use drmm-managed allocation for dpu_encoder_phys (stable-fixes).\n- drm/msm/mdss: Rename path references to mdp_path (stable-fixes).\n- drm/msm/mdss: switch mdss to use devm_of_icc_get() (stable-fixes).\n- drm/nouveau: prime: fix refcount underflow (git-fixes).\n- drm/panel: nt36523: Set 120Hz fps for xiaomi,elish panels (stable-fixes).\n- drm/radeon: Remove __counted_by from StateArray.states[] (git-fixes).\n- drm/radeon/evergreen_cs: Clean up errors in evergreen_cs.c (bsc#1229024).\n- drm/rockchip: vop2: clear afbc en and transform bit for cluster window at linear mode (stable-fixes).\n- drm/virtio: Fix type of dma-fence context variable (git-fixes).\n- drm/vmwgfx: Fix a deadlock in dma buf fence polling (git-fixes).\n- drm/vmwgfx: Fix overlay when using Screen Targets (git-fixes).\n- drm/vmwgfx: Fix prime with external buffers (git-fixes).\n- efi/libstub: Zero initialize heap allocated struct screen_info (git-fixes).\n- evm: do not copy up 'security.evm' xattr (git-fixes).\n- firmware: cirrus: cs_dsp: Initialize debugfs_root to invalid (stable-fixes).\n- fs/netfs/fscache_cookie: add missing 'n_accesses' check (bsc#1229455).\n- fuse: Initialize beyond-EOF page contents before setting uptodate (bsc#1229456).\n- genirq/cpuhotplug, x86/vector: Prevent vector leak during CPU offline (git-fixes).\n- genirq/generic_chip: Make irq_remove_generic_chip() irqdomain aware (git-fixes).\n- genirq/matrix: Exclude managed interrupts in irq_matrix_allocated() (git-fixes).\n- gfs2: setattr_chown: Add missing initialization (git-fixes).\n- gpio: mlxbf3: Support shutdown() function (git-fixes).\n- gpio: prevent potential speculation leaks in gpio_device_get_desc() (stable-fixes).\n- gpio: sysfs: extend the critical section for unregistering sysfs devices (stable-fixes).\n- gss_krb5: Fix the error handling path for crypto_sync_skcipher_setkey (git-fixes).\n- hfs: fix to initialize fields of hfs_inode_info after hfs_alloc_inode() (git-fixes).\n- HID: wacom: Defer calculation of resolution until resolution_code is known (git-fixes).\n- hwmon: (ltc2992) Avoid division by zero (stable-fixes).\n- hwmon: (ltc2992) Fix memory leak in ltc2992_parse_dt() (git-fixes).\n- hwmon: (pc87360) Bounds check data-\u003einnr usage (stable-fixes).\n- i2c: Fix conditional for substituting empty ACPI functions (stable-fixes).\n- i2c: qcom-geni: Add missing clk_disable_unprepare in geni_i2c_runtime_resume (git-fixes).\n- i2c: qcom-geni: Add missing geni_icc_disable in geni_i2c_runtime_resume (git-fixes).\n- i2c: qcom-geni: Add missing geni_icc_disable in geni_i2c_runtime_resume (git-fixes).\n- i2c: riic: avoid potential division by zero (stable-fixes).\n- i2c: smbus: Improve handling of stuck alerts (git-fixes).\n- i2c: smbus: Send alert notifications to all devices if source not found (git-fixes).\n- i2c: stm32f7: Add atomic_xfer method to driver (stable-fixes).\n- i2c: Use IS_REACHABLE() for substituting empty ACPI functions (git-fixes).\n- i3c: mipi-i3c-hci: Do not unmap region not mapped for transfer (stable-fixes).\n- i3c: mipi-i3c-hci: Remove BUG() when Ring Abort request times out (stable-fixes).\n- i915/perf: Remove code to update PWR_CLK_STATE for gen12 (git-fixes).\n- ice: Fix NULL pointer access, if PF does not support SRIOV_LAG (bsc#1228737).\n- Input: i8042 - add forcenorestore quirk to leave controller untouched even on s3 (stable-fixes).\n- Input: i8042 - add Fujitsu Lifebook E756 to i8042 quirk table (bsc#1229056).\n- Input: i8042 - use new forcenorestore quirk to replace old buggy quirk combination (stable-fixes).\n- Input: MT - limit max slots (stable-fixes).\n- io_uring: Drop per-ctx dummy_ubuf (git-fixes).\n- io_uring: fix io_match_task must_hold (git-fixes).\n- io_uring: Fix probe of disabled operations (git-fixes).\n- io_uring: tighten task exit cancellations (git-fixes).\n- io_uring/advise: support 64-bit lengths (git-fixes).\n- iommu/amd: Convert comma to semicolon (git-fixes).\n- iommu/vt-d: Fix identity map bounds in si_domain_init() (git-fixes).\n- iommufd/device: Fix hwpt at err_unresv in iommufd_device_do_replace() (git-fixes).\n- ip6_tunnel: Fix broken GRO (bsc#1229444).\n- ipv6: sr: fix incorrect unregister order (git-fixes).\n- irqdomain: Fixed unbalanced fwnode get and put (git-fixes).\n- jfs: define xtree root and page independently (git-fixes).\n- jfs: fix null ptr deref in dtInsertEntry (git-fixes).\n- jfs: Fix shift-out-of-bounds in dbDiscardAG (git-fixes).\n- jump_label: Clarify condition in static_key_fast_inc_not_disabled() (git-fixes).\n- jump_label: Fix concurrency issues in static_key_slow_dec() (git-fixes).\n- jump_label: Fix the fix, brown paper bags galore (git-fixes).\n- jump_label: Simplify and clarify static_key_fast_inc_cpus_locked() (git-fixes).\n- kabi fix for KVM: s390: fix LPSWEY handling (bsc#1227634 git-fixes).\n- kabi fix for SUNRPC: add a missing rpc_stat for TCP TLS (git-fixes).\n- kABI fix of: virtio-crypto: handle config changed by work queue (git-fixes).\n- kABI workaround for sound core UMP conversion (stable-fixes).\n- kabi/severities: ignore kABI for FireWire sound local symbols (bsc#1208783)\n- kabi/severity: add nvme common code The nvme common code is also allowed to change the data structures, there are only internal users.\n- kcov: properly check for softirq context (git-fixes).\n- kernfs: Convert kernfs_path_from_node_locked() from strlcpy() to strscpy() (bsc#1229134).\n- kernfs: fix false-positive WARN(nr_mmapped) in kernfs_drain_open_files (git-fixes).\n- kprobes: Fix to check symbol prefixes correctly (git-fixes).\n- kprobes: Prohibit probing on CFI preamble symbol (git-fixes).\n- KVM: Always flush async #PF workqueue when vCPU is being destroyed (git-fixes).\n- KVM: arm64: AArch32: Fix spurious trapping of conditional instructions (git-fixes).\n- KVM: arm64: Add missing memory barriers when switching to pKVM's hyp pgd (git-fixes).\n- KVM: arm64: Allow AArch32 PSTATE.M to be restored as System mode (git-fixes).\n- KVM: arm64: Fix __pkvm_init_switch_pgd call ABI (git-fixes).\n- KVM: arm64: Fix AArch32 register narrowing on userspace write (git-fixes).\n- KVM: arm64: Fix clobbered ELR in sync abort/SError (git-fixes)\n- KVM: arm64: GICv4: Do not perform a map to a mapped vLPI (git-fixes).\n- KVM: arm64: timers: Correctly handle TGE flip with CNTPOFF_EL2 (git-fixes).\n- KVM: arm64: timers: Fix resource leaks in kvm_timer_hyp_init() (git-fixes).\n- KVM: arm64: vgic-its: Test for valid IRQ in its_sync_lpi_pending_table() (git-fixes).\n- KVM: arm64: vgic-its: Test for valid IRQ in MOVALL handler (git-fixes).\n- KVM: arm64: vgic-v2: Use cpuid from userspace as vcpu_id (git-fixes).\n- KVM: arm64: vgic-v4: Restore pending state on host userspace write (git-fixes).\n- KVM: arm64: vgic: Add a non-locking primitive for kvm_vgic_vcpu_destroy() (git-fixes).\n- KVM: arm64: vgic: Force vcpu vgic teardown on vcpu destroy (git-fixes).\n- KVM: arm64: vgic: Simplify kvm_vgic_destroy() (git-fixes).\n- KVM: fix kvm_mmu_memory_cache allocation warning (git-fixes).\n- KVM: Make KVM_MEM_GUEST_MEMFD mutually exclusive with KVM_MEM_READONLY (git-fixes).\n- KVM: nVMX: Add a helper to get highest pending from Posted Interrupt vector (git-fixes).\n- KVM: nVMX: Check for pending posted interrupts when looking for nested events (git-fixes).\n- KVM: nVMX: Request immediate exit iff pending nested event needs injection (git-fixes).\n- KVM: PPC: Book3S HV: Fix the set_one_reg for MMCR3 (bsc#1194869).\n- KVM: PPC: Book3S HV: Handle pending exceptions on guest entry with MSR_EE (bsc#1215199).\n- KVM: Protect vcpu-\u003epid dereference via debugfs with RCU (git-fixes).\n- KVM: Reject overly excessive IDs in KVM_CREATE_VCPU (git-fixes).\n- KVM: s390: fix LPSWEY handling (bsc#1227634 git-fixes).\n- KVM: s390: fix validity interception issue when gisa is switched off (git-fixes bsc#1229167).\n- kvm: s390: Reject memory region operations for ucontrol VMs (git-fixes bsc#1229168).\n- KVM: Stop processing *all* memslots when 'null' mmu_notifier handler is found (git-fixes).\n- KVM: VMX: Move posted interrupt descriptor out of VMX code (git-fixes).\n- KVM: VMX: Split out the non-virtualization part of vmx_interrupt_blocked() (git-fixes).\n- KVM: VMX: Switch __vmx_exit() and kvm_x86_vendor_exit() in vmx_exit() (git-fixes).\n- KVM: x86: Limit check IDs for KVM_SET_BOOT_CPU_ID (git-fixes).\n- KVM: x86/mmu: Bug the VM if KVM tries to split a !hugepage SPTE (git-fixes).\n- libbpf: Add missing LIBBPF_API annotation to libbpf_set_memlock_rlim API (git-fixes).\n- libbpf: Apply map_set_def_max_entries() for inner_maps on creation (git-fixes).\n- libbpf: Fix faccessat() usage on Android (git-fixes).\n- libbpf: Use OPTS_SET() macro in bpf_xdp_query() (git-fixes).\n- md-cluster: fix hanging issue while a new disk adding (bsc#1223395).\n- md-cluster: fix hanging issue while a new disk adding (bsc#1223395).\n- md-cluster: fix no recovery job when adding/re-adding a disk (bsc#1223395).\n- md-cluster: fix no recovery job when adding/re-adding a disk (bsc#1223395).\n- md-cluster: keeping kabi compatibility for upstream commit 35a0a409fa26 (bsc#1223395).\n- md: add a mddev_add_trace_msg helper (git-fixes).\n- md: add check for sleepers in md_wakeup_thread() (git-fixes).\n- md: change the return value type of md_write_start to void (git-fixes).\n- md: do not account sync_io if iostats of the disk is disabled (git-fixes).\n- md: do not delete safemode_timer in mddev_suspend (git-fixes).\n- md: Do not wait for MD_RECOVERY_NEEDED for HOT_REMOVE_DISK ioctl (git-fixes).\n- md: factor out a helper exceed_read_errors() to check read_errors (git-fixes).\n- md: fix a suspicious RCU usage warning (git-fixes).\n- md/md-bitmap: fix writing non bitmap pages (git-fixes).\n- md/raid1: set max_sectors during early return from choose_slow_rdev() (git-fixes).\n- md/raid1: support read error check (git-fixes).\n- md/raid5: fix deadlock that raid5d() wait for itself to clear MD_SB_CHANGE_PENDING (git-fixes).\n- md/raid5: fix spares errors about rcu usage (git-fixes).\n- md/raid5: recheck if reshape has finished with device_lock held (git-fixes).\n- media: amphion: Remove lock in s_ctrl callback (stable-fixes).\n- media: drivers/media/dvb-core: copy user arrays safely (stable-fixes).\n- media: pci: cx23885: check cx23885_vdev_init() return (stable-fixes).\n- media: Revert 'media: dvb-usb: Fix unexpected infinite loop in dvb_usb_read_remote_control()' (git-fixes).\n- media: uvcvideo: Add quirk for invalid dev_sof in Logitech C920 (git-fixes).\n- media: uvcvideo: Disable autosuspend for Insta360 Link (stable-fixes).\n- media: uvcvideo: Fix the bandwdith quirk on USB 3.x (stable-fixes).\n- media: uvcvideo: Ignore empty TS packets (stable-fixes).\n- media: uvcvideo: Quirk for invalid dev_sof in Logitech C922 (stable-fixes).\n- media: xc2028: avoid use-after-free in load_firmware_cb() (stable-fixes).\n- memcg: protect concurrent access to mem_cgroup_idr (git-fixes).\n- memory: stm32-fmc2-ebi: check regmap_read return value (stable-fixes).\n- memory: tegra: Skip SID programming if SID registers are not set (stable-fixes).\n- minmax: add a few more MIN_T/MAX_T users (bsc#1229024).\n- minmax: avoid overly complicated constant expressions in VM code (bsc#1229024).\n- minmax: do not use max() in situations that want a C constant expression (bsc#1229024).\n- minmax: fix up min3() and max3() too (bsc#1229024).\n- minmax: improve macro expansion and type checking (bsc#1229024).\n- minmax: make generic MIN() and MAX() macros available everywhere (bsc#1229024).\n- minmax: simplify and clarify min_t()/max_t() implementation (bsc#1229024).\n- minmax: simplify min()/max()/clamp() implementation (bsc#1229024).\n- mm, kmsan: fix infinite recursion due to RCU critical section (git-fixes).\n- mm: prevent derefencing NULL ptr in pfn_section_valid() (git-fixes).\n- mmc: dw_mmc: allow biu and ciu clocks to defer (git-fixes).\n- mmc: mmc_test: Fix NULL dereference on allocation failure (git-fixes).\n- mmc: mtk-sd: receive cmd8 data when hs400 tuning fail (git-fixes).\n- net: drop bad gso csum_start and offset in virtio_net_hdr (git-fixes).\n- net: ethernet: mtk_wed: fix use-after-free panic in mtk_wed_setup_tc_block_cb() (git-fixes).\n- net: fix sk_memory_allocated_{add|sub} vs softirqs (bsc#1228757).\n- net: mana: Add support for page sizes other than 4KB on ARM64 (jsc#PED-8491 bsc#1226530).\n- net: mana: Fix doorbell out of order violation and avoid unnecessary doorbell rings (bsc#1229154).\n- net: mana: Fix race of mana_hwc_post_rx_wqe and new hwc response (git-fixes).\n- net: mana: Fix RX buf alloc_size alignment and atomic op panic (bsc#1229086).\n- net: missing check virtio (git-fixes).\n- net: phy: micrel: Fix the KSZ9131 MDI-X status issue (git-fixes).\n- net: phy: realtek: add support for RTL8366S Gigabit PHY (git-fixes).\n- net: usb: qmi_wwan: fix memory leak for not ip packets (git-fixes).\n- net: usb: sr9700: fix uninitialized variable use in sr_mdio_read (git-fixes).\n- net/iucv: fix the allocation size of iucv_path_table array (git-fixes bsc#1229451).\n- net/iucv: fix use after free in iucv_sock_close() (bsc#1228973).\n- net/rds: fix possible cp null dereference (git-fixes).\n- net/sched: initialize noop_qdisc owner (git-fixes).\n- netfs, fscache: export fscache_put_volume() and add fscache_try_get_volume() (bsc#1228459 bsc#1228462).\n- nfc: pn533: Add poll mod list filling check (git-fixes).\n- nfs: do not invalidate dentries on transient errors (git-fixes).\n- nfs: expose /proc/net/sunrpc/nfs in net namespaces (git-fixes).\n- nfs: make the rpc_stat per net namespace (git-fixes).\n- nfs: pass explicit offset/count to trace events (git-fixes).\n- nfs: propagate readlink errors in nfs_symlink_filler (git-fixes).\n- NFSD: Support write delegations in LAYOUTGET (git-fixes).\n- NFSv4.1 another fix for EXCHGID4_FLAG_USE_PNFS_DS for DS server (git-fixes).\n- nouveau/firmware: use dma non-coherent allocator (git-fixes).\n- nvme_core: scan namespaces asynchronously (bsc#1224105).\n- nvme-multipath: find NUMA path only for online numa-node (git-fixes).\n- nvme-multipath: implement 'queue-depth' iopolicy (bsc#1227706).\n- nvme-multipath: prepare for 'queue-depth' iopolicy (bsc#1227706).\n- nvme-pci: add missing condition check for existence of mapped data (git-fixes).\n- nvme-pci: do not directly handle subsys reset fallout (bsc#1220066).\n- nvme-pci: Fix the instructions for disabling power management (git-fixes).\n- nvme-sysfs: add 'tls_configured_key' sysfs attribute (bsc#1221857).\n- nvme-sysfs: add 'tls_keyring' attribute (bsc#1221857).\n- nvme-tcp: check for invalidated or revoked key (bsc#1221857).\n- nvme-tcp: sanitize TLS key handling (bsc#1221857).\n- nvme: add a newline to the 'tls_key' sysfs attribute (bsc#1221857).\n- nvme: adjust multiples of NVME_CTRL_PAGE_SIZE in offset (git-fixes).\n- nvme: avoid double free special payload (git-fixes).\n- nvme: fix NVME_NS_DEAC may incorrectly identifying the disk as EXT_LBA (git-fixes).\n- nvme: fixup comment for nvme RDMA Provider Type (git-fixes).\n- nvme: split off TLS sysfs attributes into a separate group (bsc#1221857).\n- nvme: tcp: remove unnecessary goto statement (bsc#1221857).\n- nvmet-auth: fix nvmet_auth hash error handling (git-fixes).\n- nvmet: always initialize cqe.result (git-fixes).\n- nvmet: do not return 'reserved' for empty TSAS values (git-fixes).\n- nvmet: fix a possible leak when destroy a ctrl during qp establishment (git-fixes).\n- nvmet: make 'tsas' attribute idempotent for RDMA (git-fixes).\n- ocfs2: strict bound check before memcmp in ocfs2_xattr_find_entry() (bsc#1228410).\n- padata: Fix possible divide-by-0 panic in padata_mt_helper() (git-fixes).\n- PCI: Add Edimax Vendor ID to pci_ids.h (stable-fixes).\n- PCI: hv: Return zero, not garbage, when reading PCI_INTERRUPT_PIN (git-fixes).\n- PCI: loongson: Enable MSI in LS7A Root Complex (stable-fixes).\n- perf/smmuv3: Enable HiSilicon Erratum 162001900 quirk for HIP08/09 (git-fixes).\n- pinctrl: mediatek: common-v2: Fix broken bias-disable for PULL_PU_PD_RSEL_TYPE (git-fixes).\n- pinctrl: rockchip: correct RK3328 iomux width flag for GPIO2-B pins (git-fixes).\n- pinctrl: single: fix potential NULL dereference in pcs_get_function() (git-fixes).\n- pinctrl: starfive: jh7110: Correct the level trigger configuration of iev register (git-fixes).\n- platform/chrome: cros_ec_proto: Lock device when updating MKBP version (git-fixes).\n- platform/chrome: cros_ec_proto: Lock device when updating MKBP version (git-fixes).\n- platform/surface: aggregator: Fix warning when controller is destroyed in probe (git-fixes).\n- platform/x86: lg-laptop: fix %s null argument warning (stable-fixes).\n- platform/x86/amd/hsmp: Add support for ACPI based probing (jsc#PED-8779).\n- platform/x86/amd/hsmp: Cache pci_dev in struct hsmp_socket (jsc#PED-8779).\n- platform/x86/amd/hsmp: Change devm_kzalloc() to devm_kcalloc() (jsc#PED-8779).\n- platform/x86/amd/hsmp: Check HSMP support on AMD family of processors (jsc#PED-8779).\n- platform/x86/amd/hsmp: Check num_sockets against MAX_AMD_SOCKETS (jsc#PED-8779).\n- platform/x86/amd/hsmp: Create static func to handle platdev (jsc#PED-8779).\n- platform/x86/amd/hsmp: Define a struct to hold mailbox regs (jsc#PED-8779).\n- platform/x86/amd/hsmp: Move dev from platdev to hsmp_socket (jsc#PED-8779).\n- platform/x86/amd/hsmp: Move hsmp_test to probe (jsc#PED-8779).\n- platform/x86/amd/hsmp: Non-ACPI support for AMD F1A_M00~0Fh (jsc#PED-8779).\n- platform/x86/amd/hsmp: Remove extra parenthesis and add a space (jsc#PED-8779).\n- platform/x86/amd/hsmp: Restructure sysfs group creation (jsc#PED-8779).\n- platform/x86/amd/hsmp: switch to use device_add_groups() (jsc#PED-8779).\n- platform/x86/intel/ifs: Initialize union ifs_status to zero (git-fixes).\n- power: supply: axp288_charger: Fix constant_charge_voltage writes (git-fixes).\n- power: supply: axp288_charger: Round constant_charge_voltage writes down (git-fixes).\n- power: supply: qcom_battmgr: return EAGAIN when firmware service is not up (git-fixes).\n- powerpc: fix a file leak in kvm_vcpu_ioctl_enable_cap() (bsc#1194869).\n- powerpc: xor_vmx: Add '-mhard-float' to CFLAGS (bsc#1194869).\n- powerpc/64: Set _IO_BASE to POISON_POINTER_DELTA not 0 for CONFIG_PCI=n (bsc#1194869).\n- powerpc/io: Avoid clang null pointer arithmetic warnings (bsc#1194869).\n- powerpc/kexec_file: fix cpus node update to FDT (bsc#1194869).\n- powerpc/kexec: make the update_cpus_node() function public (bsc#1194869).\n- powerpc/kexec: split CONFIG_KEXEC_FILE and CONFIG_CRASH_DUMP (bsc#1194869).\n- powerpc/pseries: Add failure related checks for h_get_mpp and h_get_ppp (bsc#1194869).\n- powerpc/pseries: Whitelist dtl slub object for copying to userspace (bsc#1194869).\n- powerpc/radix: Move some functions into #ifdef CONFIG_KVM_BOOK3S_HV_POSSIBLE (bsc#1194869).\n- powerpc/topology: Check if a core is online (bsc#1214285 bsc#1205462 ltc#200161 ltc#200588 git-fixes).\n- powerpc/xmon: Check cpu id in commands 'c#', 'dp#' and 'dx#' (bsc#1194869).\n- printk/panic: Allow cpu backtraces to be written into ringbuffer during panic (bsc#1225607).\n- RDMA: Fix netdev tracker in ib_device_set_netdev (git-fixes)\n- RDMA/cache: Release GID table even if leak is detected (git-fixes)\n- RDMA/device: Return error earlier if port in not valid (git-fixes)\n- RDMA/hns: Check atomic wr length (git-fixes)\n- RDMA/hns: Fix insufficient extend DB for VFs. (git-fixes)\n- RDMA/hns: Fix mbx timing out before CMD execution is completed (git-fixes)\n- RDMA/hns: Fix missing pagesize and alignment check in FRMR (git-fixes)\n- RDMA/hns: Fix shift-out-bounds when max_inline_data is 0 (git-fixes)\n- RDMA/hns: Fix soft lockup under heavy CEQE load (git-fixes)\n- RDMA/hns: Fix undifined behavior caused by invalid max_sge (git-fixes)\n- RDMA/hns: Fix unmatch exception handling when init eq table fails (git-fixes)\n- RDMA/iwcm: Fix a use-after-free related to destroying CM IDs (git-fixes)\n- RDMA/mana_ib: Use virtual address in dma regions for MRs (git-fixes).\n- RDMA/mlx4: Fix truncated output warning in alias_GUID.c (git-fixes)\n- RDMA/mlx4: Fix truncated output warning in mad.c (git-fixes)\n- RDMA/mlx5: Set mkeys for dmabuf at PAGE_SIZE (git-fixes)\n- RDMA/rxe: Do not set BTH_ACK_MASK for UC or UD QPs (git-fixes)\n- reiserfs: fix uninit-value in comp_keys (git-fixes).\n- rtc: nct3018y: fix possible NULL dereference (stable-fixes).\n- s390/cpum_cf: Fix endless loop in CF_DIAG event stop (git-fixes bsc#1229171).\n- s390/dasd: fix error checks in dasd_copy_pair_store() (git-fixes bsc#1229173).\n- s390/dasd: fix error recovery leading to data corruption on ESE devices (git-fixes bsc#1229452).\n- s390/pci: Add missing virt_to_phys() for directed DIBV (git-fixes bsc#1229174).\n- s390/pci: Allow allocation of more than 1 MSI interrupt (git-fixes bsc#1229172).\n- s390/pci: Refactor arch_setup_msi_irqs() (git-fixes bsc#1229172).\n- s390/pkey: harmonize pkey s390 debug feature calls (bsc#1228720).\n- s390/pkey: introduce dynamic debugging for pkey (bsc#1228720).\n- s390/sclp: Prevent release of buffer in I/O (git-fixes bsc#1229169).\n- s390/uv: Panic for set and remove shared access UVC errors (git-fixes bsc#1229170).\n- samples/bpf: syscall_tp_user: Fix array out-of-bound access (git-fixes).\n- samples/bpf: syscall_tp_user: Rename num_progs into nr_tests (git-fixes).\n- sbitmap: use READ_ONCE to access map-\u003eword (stable-fixes).\n- scsi: lpfc: Allow DEVICE_RECOVERY mode after RSCN receipt if in PRLI_ISSUE state (bsc#1228857).\n- scsi: lpfc: Cancel ELS WQE instead of issuing abort when SLI port is inactive (bsc#1228857).\n- scsi: lpfc: Fix handling of fully recovered fabric node in dev_loss callbk (bsc#1228857).\n- scsi: lpfc: Fix incorrect request len mbox field when setting trunking via sysfs (bsc#1228857).\n- scsi: lpfc: Handle mailbox timeouts in lpfc_get_sfp_info (bsc#1228857).\n- scsi: lpfc: Relax PRLI issue conditions after GID_FT response (bsc#1228857).\n- scsi: lpfc: Revise lpfc_prep_embed_io routine with proper endian macro usages (bsc#1228857).\n- scsi: lpfc: Update lpfc version to 14.4.0.3 (bsc#1228857).\n- scsi: qla2xxx: Avoid possible run-time warning with long model_num (bsc#1228850).\n- scsi: qla2xxx: Complete command early within lock (bsc#1228850).\n- scsi: qla2xxx: Convert comma to semicolon (bsc#1228850).\n- scsi: qla2xxx: Drop driver owner assignment (bsc#1228850).\n- scsi: qla2xxx: During vport delete send async logout explicitly (bsc#1228850).\n- scsi: qla2xxx: Fix debugfs output for fw_resource_count (bsc#1228850).\n- scsi: qla2xxx: Fix flash read failure (bsc#1228850).\n- scsi: qla2xxx: Fix for possible memory corruption (bsc#1228850).\n- scsi: qla2xxx: Fix optrom version displayed in FDMI (bsc#1228850).\n- scsi: qla2xxx: Indent help text (bsc#1228850).\n- scsi: qla2xxx: Reduce fabric scan duplicate code (bsc#1228850).\n- scsi: qla2xxx: Remove unused struct 'scsi_dif_tuple' (bsc#1228850).\n- scsi: qla2xxx: Return ENOBUFS if sg_cnt is more than one for ELS cmds (bsc#1228850).\n- scsi: qla2xxx: Unable to act on RSCN for port online (bsc#1228850).\n- scsi: qla2xxx: Update version to 10.02.09.300-k (bsc#1228850).\n- scsi: qla2xxx: Use QP lock to search for bsg (bsc#1228850).\n- scsi: qla2xxx: validate nvme_local_port correctly (bsc#1228850).\n- selftest/bpf: Add map_in_maps with BPF_MAP_TYPE_PERF_EVENT_ARRAY values (git-fixes).\n- selftests/bpf: Add a test to verify previous stacksafe() fix (bsc#1225903).\n- selftests/bpf: Add assert for user stacks in test_task_stack (git-fixes).\n- selftests/bpf: Add netkit to tc_redirect selftest (git-fixes).\n- selftests/bpf: De-veth-ize the tc_redirect test case (git-fixes).\n- selftests/bpf: Disable IPv6 for lwt_redirect test (git-fixes).\n- selftests/bpf: fix bpf_loop_bench for new callback verification scheme (git-fixes).\n- selftests/bpf: fix compiler warnings in RELEASE=1 mode (git-fixes).\n- selftests/bpf: Fix erroneous bitmask operation (git-fixes).\n- selftests/bpf: Fix issues in setup_classid_environment() (git-fixes).\n- selftests/bpf: Fix potential premature unload in bpf_testmod (git-fixes).\n- selftests/bpf: Fix pyperf180 compilation failure with clang18 (git-fixes).\n- selftests/bpf: fix RELEASE=1 build for tc_opts (git-fixes).\n- selftests/bpf: Fix the flaky tc_redirect_dtime test (git-fixes).\n- selftests/bpf: Fix up xdp bonding test wrt feature flags (git-fixes).\n- selftests/bpf: Make linked_list failure test more robust (git-fixes).\n- selftests/bpf: Relax time_tai test for equal timestamps in tai_forward (git-fixes).\n- selftests/bpf: satisfy compiler by having explicit return in btf test (git-fixes).\n- selftests/bpf: Skip module_fentry_shadow test when bpf_testmod is not available (git-fixes).\n- selftests/bpf: Wait for the netstamp_needed_key static key to be turned on (git-fixes).\n- serial: core: check uartclk for zero to avoid divide by zero (stable-fixes).\n- soc: qcom: cmd-db: Map shared memory as WC, not WB (git-fixes).\n- soc: qcom: pmic_glink: Actually communicate when remote goes down (git-fixes).\n- soundwire: stream: fix programming slave ports for non-continous port maps (git-fixes).\n- spi: Add empty versions of ACPI functions (stable-fixes).\n- spi: microchip-core: fix init function not setting the master and motorola modes (git-fixes).\n- spi: microchip-core: switch to use modern name (stable-fixes).\n- spi: spi-fsl-lpspi: Fix scldiv calculation (git-fixes).\n- spi: spidev: Add missing spi_device_id for bh2228fv (git-fixes).\n- Squashfs: fix variable overflow triggered by sysbot (git-fixes).\n- squashfs: squashfs_read_data need to check if the length is 0 (git-fixes).\n- ssb: Fix division by zero issue in ssb_calc_clock_rate (stable-fixes).\n- staging: iio: resolver: ad2s1210: fix use before initialization (stable-fixes).\n- staging: ks7010: disable bh on tx_dev_lock (stable-fixes).\n- string.h: Introduce memtostr() and memtostr_pad() (bsc#1228849).\n- SUNRPC: add a missing rpc_stat for TCP TLS (git-fixes).\n- sunrpc: add a struct rpc_stats arg to rpc_create_args (git-fixes).\n- SUNRPC: Fix a race to wake a sync task (git-fixes).\n- swiotlb: do not set total_used to 0 in swiotlb_create_debugfs_files() (git-fixes).\n- swiotlb: fix swiotlb_bounce() to do partial sync's correctly (git-fixes).\n- syscalls: fix compat_sys_io_pgetevents_time64 usage (git-fixes).\n- thermal: bcm2835: Convert to platform remove callback returning void (stable-fixes).\n- thermal/drivers/broadcom: Fix race between removal and clock disable (git-fixes).\n- thunderbolt: Mark XDomain as unplugged when router is removed (stable-fixes).\n- tools/perf: Fix perf bench epoll to enable the run when some CPU's are offline (bsc#1227747).\n- tools/perf: Fix perf bench futex to enable the run when some CPU's are offline (bsc#1227747).\n- tools/perf: Fix timing issue with parallel threads in perf bench wake-up-parallel (bsc#1227747).\n- tools/resolve_btfids: fix build with musl libc (git-fixes).\n- tools/resolve_btfids: Fix comparison of distinct pointer types warning in resolve_btfids (git-fixes).\n- tools/resolve_btfids: Fix cross-compilation to non-host endianness (git-fixes).\n- tools/resolve_btfids: Refactor set sorting with types from btf_ids.h (git-fixes).\n- trace/pid_list: Change gfp flags in pid_list_fill_irq() (git-fixes).\n- tracing: Return from tracing_buffers_read() if the file has been closed (bsc#1229136 git-fixes).\n- tty: atmel_serial: use the correct RTS flag (git-fixes).\n- tty: serial: fsl_lpuart: mark last busy before uart_add_one_port (git-fixes).\n- usb: cdnsp: fix for Link TRB with TC (git-fixes).\n- usb: cdnsp: fix incorrect index in cdnsp_get_hw_deq function (git-fixes).\n- usb: core: sysfs: Unmerge @usb3_hardware_lpm_attr_group in remove_power_attributes() (git-fixes).\n- usb: dwc3: core: Skip setting event buffers for host only controllers (stable-fixes).\n- usb: dwc3: omap: add missing depopulate in probe error path (git-fixes).\n- usb: dwc3: st: add missing depopulate in probe error path (git-fixes).\n- usb: dwc3: st: fix probed platform device ref count on probe error path (git-fixes).\n- usb: gadget: core: Check for unset descriptor (git-fixes).\n- usb: gadget: fsl: Increase size of name buffer for endpoints (stable-fixes).\n- usb: gadget: u_audio: Check return codes from usb_ep_enable and config_ep_by_speed (git-fixes).\n- usb: gadget: u_serial: Set start_delayed during suspend (git-fixes).\n- usb: gadget: uvc: cleanup request when not in correct state (stable-fixes).\n- USB: serial: debug: do not echo input by default (stable-fixes).\n- usb: typec: fsa4480: add support for Audio Accessory Mode (git-fixes).\n- usb: typec: fsa4480: Add support to swap SBU orientation (git-fixes).\n- usb: typec: fsa4480: Check if the chip is really there (git-fixes).\n- usb: typec: fsa4480: Relax CHIP_ID check (git-fixes).\n- usb: typec: fsa4480: rework mux \u0026 switch setup to handle more states (git-fixes).\n- usb: vhci-hcd: Do not drop references before new references are gained (stable-fixes).\n- vfio/pci: fix potential memory leak in vfio_intx_enable() (git-fixes).\n- vhost-scsi: Handle vhost_vq_work_queue failures for events (git-fixes).\n- vhost-vdpa: switch to use vmf_insert_pfn() in the fault handler (git-fixes).\n- vhost: Release worker mutex during flushes (git-fixes).\n- vhost: Use virtqueue mutex for swapping worker (git-fixes).\n- vhost/vsock: always initialize seqpacket_allow (git-fixes).\n- virt: guest_memfd: fix reference leak on hwpoisoned page (git-fixes).\n- virtio_net: use u64_stats_t infra to avoid data-races (git-fixes).\n- virtio-crypto: handle config changed by work queue (git-fixes).\n- virtio: reenable config if freezing device failed (git-fixes).\n- virtiofs: forbid newlines in tags (bsc#1229940).\n- wifi: ath12k: fix memory leak in ath12k_dp_rx_peer_frag_setup() (stable-fixes).\n- wifi: ath12k: fix soft lockup on suspend (git-fixes).\n- wifi: brcmfmac: cfg80211: Handle SSID based pmksa deletion (git-fixes).\n- wifi: cfg80211: fix reporting failed MLO links status with cfg80211_connect_done (git-fixes).\n- wifi: iwlwifi: fw: fix wgds rev 3 exact size (git-fixes).\n- wifi: mac80211: use monitor sdata with driver only if desired (git-fixes).\n- wifi: mwifiex: duplicate static structs used in driver instances (git-fixes).\n- wifi: nl80211: disallow setting special AP channel widths (stable-fixes).\n- wifi: nl80211: do not give key data to userspace (stable-fixes).\n- wifi: rtw88: usb: Fix disconnection after beacon loss (stable-fixes).\n- wifi: wfx: repair open network AP mode (git-fixes).\n- workqueue: Improve scalability of workqueue watchdog touch (bsc#1193454).\n- workqueue: wq_watchdog_touch is always called with valid CPU (bsc#1193454).\n- x86/asm: Use %c/%n instead of %P operand modifier in asm templates (git-fixes).\n- x86/entry/64: Remove obsolete comment on tracing vs. SYSRET (git-fixes).\n- x86/mm: Fix pti_clone_entry_text() for i386 (git-fixes).\n- x86/mm: Fix pti_clone_pgtable() alignment assumption (git-fixes).\n- x86/mtrr: Check if fixed MTRRs exist before saving them (git-fixes).\n- x86/numa: Fix SRAT lookup of CFMWS ranges with numa_fill_memblks() (git-fixes).\n- x86/numa: Fix the address overlap check in numa_fill_memblks() (git-fixes).\n- x86/numa: Fix the sort compare func used in numa_fill_memblks() (git-fixes).\n- x86/numa: Introduce numa_fill_memblks() (git-fixes).\n- x86/pci: Skip early E820 check for ECAM region (git-fixes).\n- x86/xen: Convert comma to semicolon (git-fixes).\n- xfs: allow cross-linking special files without project quota (git-fixes).\n- xfs: allow symlinks with short remote targets (bsc#1229160).\n- xfs: allow unlinked symlinks and dirs with zero size (git-fixes).\n- xfs: attr forks require attr, not attr2 (git-fixes).\n- xfs: convert comma to semicolon (git-fixes).\n- xfs: do not use current-\u003ejournal_info (git-fixes).\n- xfs: Fix missing interval for missing_owner in xfs fsmap (git-fixes).\n- xfs: Fix the owner setting issue for rmap query in xfs fsmap (git-fixes).\n- xfs: fix unlink vs cluster buffer instantiation race (git-fixes).\n- xfs: honor init_xattrs in xfs_init_new_inode for !ATTR fs (git-fixes).\n- xfs: journal geometry is not properly bounds checked (git-fixes).\n- xfs: match lock mode in xfs_buffered_write_iomap_begin() (git-fixes).\n- xfs: require XFS_SB_FEAT_INCOMPAT_LOG_XATTRS for attr log intent item recovery (git-fixes).\n- xfs: upgrade the extent counters in xfs_reflink_end_cow_extent later (git-fixes).\n- xfs: use consistent uid/gid when grabbing dquots for inodes (git-fixes).\n- xfs: use XFS_BUF_DADDR_NULL for daddrs in getfsmap code (git-fixes).\n- xhci: Fix Panther point NULL pointer deref at full-speed re-enumeration (git-fixes).\n- xprtrdma: Fix rpcrdma_reqs_reset() (git-fixes).\n","status":"published","published":"2024-09-10T09:06:25Z","modified":"2026-02-04T02:14:25.258066Z","updated_at":"2026-11-02T15:53:55.639015Z"},{"id":"SUSE-SU-2024:3195-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\nThe following security bugs were fixed:\n\n- CVE-2024-41062: Sync sock recv cb and release (bsc#1228576).\n- CVE-2023-52489: Fix race in accessing memory_section-\u003eusage (bsc#1221326).\n- CVE-2024-43821: Fix a possible null pointer dereference (bsc#1229315).\n- CVE-2024-43911: Fix NULL dereference at band check in starting tx ba session (bsc#1229827).\n- CVE-2024-42277: Avoid NULL deref in sprd_iommu_hw_en (bsc#1229409).\n- CVE-2024-43880: Put back removed metod in struct objagg_ops (bsc#1229481).\n- CVE-2024-43899: Fix null pointer deref in dcn20_resource.c (bsc#1229754).\n- CVE-2024-43882: Fixed ToCToU between perm check and set-uid/gid usage. (bsc#1229503)\n- CVE-2024-43866: Always drain health in shutdown callback (bsc#1229495).\n- CVE-2024-26812: Struct virqfd kABI workaround (bsc#1222808).\n- CVE-2024-27010: Fix mirred deadlock on device recursion (bsc#1223720).\n- CVE-2024-36881: Fix reset ptes when close() for wr-protected (bsc#1225718).\n- CVE-2024-42316: Fix div-by-zero in vmpressure_calc_level() (bsc#1229353).\n- CVE-2024-43855: Fix deadlock between mddev_suspend and flush bio (bsc#1229342).\n- CVE-2024-43864: Fix CT entry update leaks of modify header context (bsc#1229496).\n- CVE-2024-26631: Fix data-race in ipv6_mc_down / mld_ifc_work (bsc#1221630).\n- CVE-2024-42109: Unconditionally flush pending work before notifier (bsc#1228505).\n- CVE-2024-41084: Avoid null pointer dereference in region lookup (bsc#1228472).\n- CVE-2024-40905: Fix possible race in __fib6_drop_pcpu_from() (bsc#1227761)\n- CVE-2024-39489: Fix memleak in seg6_hmac_init_algo (bsc#1227623)\n- CVE-2024-36489: Fix missing memory barrier in tls_init (bsc#1226874)\n- CVE-2024-27079: Fix NULL domain on device release (bsc#1223742).\n- CVE-2024-41020: Fix fcntl/close race recovery compat path (bsc#1228427).\n- CVE-2024-35897: Discard table flag update with pending basechain deletion (bsc#1224510).\n- CVE-2024-27403: Restore const specifier in flow_offload_route_init() (bsc#1224415).\n- CVE-2024-27011: Fix memleak in map from abort path (bsc#1223803).\n- CVE-2024-26668: Reject configurations that cause integer overflow (bsc#1222335).\n- CVE-2024-26835: Set dormant flag on hook register failure (bsc#1222967).\n- CVE-2024-26808: Handle NETDEV_UNREGISTER for inet/ingress basechain (bsc#1222634).\n- CVE-2024-26809: Release elements in clone only from destroy path (bsc#1222633).\n- CVE-2023-52581: Fix memleak when more than 255 elements expired (bsc#1220877).\n- CVE-2024-43837: Fix updating attached freplace prog in prog_array map (bsc#1229297).\n- CVE-2024-35939: Fixed leak pages on dma_set_decrypted() failure (bsc#1224535).\n- CVE-2024-42291: Add a per-VF limit on number of FDIR filters (bsc#1229374).\n- CVE-2024-42268: Fix missing lock on sync reset reload (bsc#1229391).\n- CVE-2024-43834: Fix invalid wait context of page_pool_destroy() (bsc#1229314)\n- CVE-2024-27433: Fix an error handling path in clk_mt8135_apmixed_probe() (bsc#1224711).\n- CVE-2024-36286: Acquire rcu_read_lock() in instance_destroy_rcu() (bsc#1226801)\n- CVE-2024-26851: Add protection for bmp length out of range (bsc#1223074)\n- CVE-2024-40920: Fix suspicious rcu usage in br_mst_set_state (bsc#1227781).\n- CVE-2024-40921: Pass vlan group directly to br_mst_vlan_set_state (bsc#1227784).\n- CVE-2024-36979: Fix vlan use-after-free (bsc#1226604).\n- CVE-2024-26590: Fix inconsistent per-file compression format (bsc#1220252).\n- CVE-2023-52859: Fix use-after-free when register pmu fails (bsc#1225582).\n- CVE-2024-42270: Fix null-ptr-deref in iptable_nat_table_init() (bsc#1229404).\n- CVE-2024-42269: Fix potential null-ptr-deref in ip6table_nat_table_init() (bsc#1229402).\n- CVE-2024-42284: Return non-zero value from tipc_udp_addr2str() on error (bsc#1229382)\n- CVE-2024-42283: Initialize all fields in dumped nexthops (bsc#1229383)\n- CVE-2024-42312: Always initialize i_uid/i_gid (bsc#1229357)\n- CVE-2024-43854: Initialize integrity buffer to zero before writing it to media (bsc#1229345)\n- CVE-2024-42322: Properly dereference pe in ip_vs_add_service (bsc#1229347)\n- CVE-2024-42290: Handle runtime power management correctly (bsc#1229379).\n- CVE-2024-42318: Do not lose track of restrictions on cred_transfer (bsc#1229351).\n- CVE-2023-52889: Fix null pointer deref when receiving skb during sock creation (bsc#1229287).\n- CVE-2024-42295: Handle inconsistent state in nilfs_btnode_create_block() (bsc#1229370).\n- CVE-2024-43850: Fix refcount imbalance seen during bwmon_remove (bsc#1229316).\n- CVE-2024-43831: Handle invalid decoder vsi (bsc#1229309).\n- CVE-2024-43839: Adjust 'name' buf size of bna_tcb and bna_ccb structures (bsc#1229301).\n- CVE-2024-41007: Use signed arithmetic in tcp_rtx_probe0_timed_out() (bsc#1227863).\n- CVE-2024-42281: Fix a segment issue when downgrading gso_size (bsc#1229386).\n- CVE-2024-26669: Fix chain template offload (bsc#1222350).\n- CVE-2024-26677: Blacklist e7870cf13d20 (' Fix delayed ACKs to not set the reference serial number') (bsc#1222387)\n- CVE-2024-41050: Cyclic allocation of msg_id to avoid reuse (bsc#1228499).\n- CVE-2024-41051: Wait for ondemand_object_worker to finish when dropping object (bsc#1228468).\n- CVE-2024-41074: Set object to close if ondemand_id \u003c 0 in copen (bsc#1228643).\n- CVE-2024-41075: Add consistency check for copen/cread (bsc#1228646).\n- CVE-2024-41012: Remove locks reliably when fcntl/close race is detected (bsc#1228247).\n- CVE-2024-41080: Fix possible deadlock in io_register_iowq_max_workers() (bsc#1228616).\n- CVE-2024-42246: Remap EPERM in case of connection failure in xs_tcp_setup_socket (bsc#1228989).\n- CVE-2024-42159: Fix sanitise num_phys (bsc#1228754).\n- CVE-2024-42241: Disable PMD-sized page cache if needed (bsc#1228986).\n- CVE-2024-42245: Revert 'sched/fair: Make sure to try to detach at least one movable task' (bsc#1228978).\n- CVE-2024-26735: Fix possible use-after-free and null-ptr-deref (bsc#1222372).\n- CVE-2024-26837: Race between creation of new group memberships and generation of the list of MDB events to replay (bsc#1222973).\n- CVE-2024-42155: Wipe copies of protected- and secure-keys (bsc#1228733).\n- CVE-2024-42156: Wipe copies of clear-key structures on failure (bsc#1228722).\n- CVE-2024-42157: Wipe sensitive data on failure (bsc#1228727).\n- CVE-2024-42158: Use kfree_sensitive() to fix Coccinelle warnings (bsc#1228720).\n- CVE-2024-38662: Cover verifier checks for mutating sockmap/sockhash (bsc#1226885).\n- CVE-2024-40938: Fix d_parent walk (bsc#1227840).\n- CVE-2024-42247: Avoid unaligned 64-bit memory accesses (bsc#1228988).\n- CVE-2024-41010: Fix too early release of tcx_entry (bsc#1228021).\n- CVE-2024-42106: Initialize pad field in struct inet_diag_req_v2 (bsc#1228493).\n- CVE-2024-42095: Fix Errata i2310 with RX FIFO level check (bsc#1228446).\n- CVE-2024-41068: Fix sclp_init() cleanup on failure (bsc#1228579).\n- CVE-2024-42138: Fix double memory deallocation in case of invalid INI file (bsc#1228500).\n- CVE-2024-42107: Do not process extts if PTP is disabled (bsc#1228494).\n- CVE-2024-42139: Fix improper extts handling (bsc#1228503).\n- CVE-2024-42110: Move ntb_netdev_rx_handler() to call netif_rx() from __netif_rx() (bsc#1228501).\n- CVE-2024-42113: Initialize num_q_vectors for MSI/INTx interrupts (bsc#1228568).\n- CVE-2024-42148: Fix multiple UBSAN array-index-out-of-bounds (bsc#1228487).\n- CVE-2024-42142: E-switch, Create ingress ACL when needed (bsc#1228491).\n- CVE-2024-42073: Fix memory corruptions on Spectrum-4 systems (bsc#1228457).\n- CVE-2024-42162: Account for stopped queues when reading NIC stats (bsc#1228706).\n- CVE-2024-42082: Remove WARN() from __xdp_reg_mem_model() (bsc#1228482).\n- CVE-2024-40978: Fix crash while reading debugfs attribute (bsc#1227929).\n- CVE-2024-41000: Prefer different overflow check (bsc#1227867).\n- CVE-2024-40995: Fix possible infinite loop in tcf_idr_check_alloc() (bsc#1227830).\n- CVE-2024-42161: Avoid uninitialized value in BPF_CORE_READ_BITFIELD (bsc#1228756).\n- CVE-2024-41069: Fix route memory corruption (bsc#1228644).\n- CVE-2024-39506: Adjust a NULL pointer handling path in lio_vf_rep_copy_packet (bsc#1227729).\n- CVE-2024-42145: Implement a limit on UMAD receive List (bsc#1228743).\n- CVE-2024-40994: Fix integer overflow in max_vclocks_store (bsc#1227829).\n- CVE-2024-42124: Make qedf_execute_tmf() non-preemptible (bsc#1228705).\n- CVE-2024-42096: Stop playing stack games in profile_pc() (bsc#1228633).\n- CVE-2024-42224: Correct check for empty list (bsc#1228723).\n- CVE-2024-41048: Skip zero length skb in sk_msg_recvmsg (bsc#1228565).\n- CVE-2024-40958: Make get_net_ns() handle zero refcount net (bsc#1227812).\n- CVE-2024-40939: Fix tainted pointer delete is case of region creation fail (bsc#1227799).\n- CVE-2024-36933: Use correct mac_offset to unwind gso skb in nsh_gso_segment() (bsc#1225832).\n- CVE-2024-36929: Reject skb_copy(_expand) for fraglist GSO skbs (bsc#1225814).\n- CVE-2024-41044: Reject claimed-as-LCP but actually malformed packets (bsc#1228530).\n- CVE-2024-41066: Add tx check to prevent skb leak (bsc#1228640).\n- CVE-2024-42093: Avoid explicit cpumask var allocation on stack (bsc#1228680).\n- CVE-2024-42122: Add NULL pointer check for kzalloc (bsc#1228591).\n- CVE-2024-41078: Fix quota root leak after quota disable failure (bsc#1228655).\n- CVE-2024-40989: Disassociate vcpus from redistributor region on teardown (bsc#1227823).\n- CVE-2024-41064: Avoid possible crash when edev-\u003epdev changes (bsc#1228599).\n- CVE-2024-41036: Fix deadlock with the SPI chip variant (bsc#1228496).\n- CVE-2024-41040: Fix UAF when resolving a clash (bsc#1228518).\n- CVE-2024-35949: Make sure that WRITTEN is set on all metadata blocks (bsc#1224700).\n- CVE-2024-41081: Block BH in ila_output() (bsc#1228617).\n- CVE-2024-41076: Fix memory leak in nfs4_set_security_label (bsc#1228649).\n- CVE-2024-42079: Fix NULL pointer dereference in gfs2_log_flush (bsc#1228672).\n- CVE-2024-41057: Fix slab-use-after-free in cachefiles_withdraw_cookie() (bsc#1228462).\n- CVE-2024-41058: Fix slab-use-after-free in fscache_withdraw_volume() (bsc#1228459).\n- CVE-2024-41015: Add bounds checking to ocfs2_check_dir_entry() (bsc#1228409).\n- CVE-2024-40956: Fix possible Use-After-Free in irq_process_work_list (bsc#1227810).\n- CVE-2024-27437: Disable auto-enable of exclusive INTx IRQ (bsc#1222625).\n- CVE-2024-41032: Check if a hash-index is in cpu_possible_mask (bsc#1228460).\n- CVE-2024-40957: Fix parameter passing when calling NF_HOOK() in End.DX4 and End.DX6 behaviors (bsc#1227811).\n- CVE-2024-41041: Set SOCK_RCU_FREE earlier in udp_lib_get_port() (bsc#1228520).\n- CVE-2024-40954: Do not leave a dangling sk pointer, when socket creation fails (bsc#1227808)\n- CVE-2024-42070: Fully validate NFT_DATA_VALUE on store to data registers (bsc#1228470).\n- CVE-2024-41070: Prevent UAF in kvm_spapr_tce_attach_iommu_group() (bsc#1228581).\n- CVE-2024-40959: Check ip6_dst_idev() return value in xfrm6_get_saddr() (bsc#1227884).\n- CVE-2024-41009: Fix overrunning reservations in ringbuf (bsc#1228020).\n- CVE-2024-40909: Fix a potential use-after-free in bpf_link_free() (bsc#1227798).\n- CVE-2024-27024: Fix WARNING in rds_conn_connect_if_down (bsc#1223777).\n\nThe following non-security bugs were fixed:\n\n- ACPI: battery: create alarm sysfs attribute atomically (stable-fixes).\n- ACPI: processor_idle: use raw_safe_halt() in acpi_idle_play_dead() (git-fixes).\n- ACPI: SBS: manage alarm sysfs attribute through psy core (stable-fixes).\n- ACPI/NUMA: Apply SRAT proximity domain to entire CFMWS window (git-fixes).\n- afs: fix __afs_break_callback() / afs_drop_open_mmap() race (git-fixes).\n- ALSA: hda: Add HP MP9 G4 Retail System AMS to force connect list (stable-fixes).\n- ALSA: hda: Add HP MP9 G4 Retail System AMS to force connect list (stable-fixes).\n- ALSA: hda: Conditionally use snooping for AMD HDMI (git-fixes).\n- ALSA: hda: conexant: Fix headset auto detect fail in the polling mode (git-fixes).\n- ALSA: hda/hdmi: Yet more pin fix for HP EliteDesk 800 G4 (stable-fixes).\n- ALSA: hda/hdmi: Yet more pin fix for HP EliteDesk 800 G4 (stable-fixes).\n- ALSA: hda/realtek - Fixed ALC256 headphone no sound (stable-fixes).\n- ALSA: hda/realtek - FIxed ALC285 headphone no sound (stable-fixes).\n- ALSA: hda/realtek: Add Framework Laptop 13 (Intel Core Ultra) to quirks (stable-fixes).\n- ALSA: hda/realtek: Add Framework Laptop 13 (Intel Core Ultra) to quirks (stable-fixes).\n- ALSA: hda/realtek: Add quirk for Acer Aspire E5-574G (stable-fixes).\n- ALSA: hda/realtek: Add support for new HP G12 laptops (stable-fixes).\n- ALSA: hda/realtek: Enable mute/micmute LEDs on HP Laptop 14-ey0xxx (stable-fixes).\n- ALSA: hda/realtek: Fix noise from speakers on Lenovo IdeaPad 3 15IAU7 (git-fixes).\n- ALSA: hda/realtek: Fix the speaker output on Samsung Galaxy Book3 Ultra (stable-fixes).\n- ALSA: hda/realtek: Implement sound init sequence for Samsung Galaxy Book3 Pro 360 (stable-fixes).\n- ALSA: hda/realtek: support HP Pavilion Aero 13-bg0xxx Mute LED (stable-fixes).\n- ALSA: hda/tas2781: fix wrong calibrated data order (git-fixes).\n- ALSA: hda/tas2781: Use correct endian conversion (git-fixes).\n- ALSA: line6: Fix racy access to midibuf (stable-fixes).\n- ALSA: line6: Fix racy access to midibuf (stable-fixes).\n- ALSA: seq: Skip event type filtering for UMP events (git-fixes).\n- ALSA: seq: ump: Explicitly reset RPN with Null RPN (stable-fixes).\n- ALSA: seq: ump: Optimize conversions from SysEx to UMP (git-fixes).\n- ALSA: seq: ump: Transmit RPN/NRPN message at each MSB/LSB data reception (stable-fixes).\n- ALSA: seq: ump: Use the common RPN/bank conversion context (stable-fixes).\n- ALSA: timer: Relax start tick time check for slave timer elements (git-fixes).\n- ALSA: ump: Explicitly reset RPN with Null RPN (stable-fixes).\n- ALSA: ump: Transmit RPN/NRPN message at each MSB/LSB data reception (stable-fixes).\n- ALSA: usb-audio: Add delay quirk for VIVO USB-C-XE710 HEADSET (stable-fixes).\n- ALSA: usb-audio: Correct surround channels in UAC1 channel map (git-fixes).\n- ALSA: usb-audio: Re-add ScratchAmp quirk entries (git-fixes).\n- ALSA: usb-audio: Re-add ScratchAmp quirk entries (git-fixes).\n- ALSA: usb-audio: Support Yamaha P-125 quirk entry (stable-fixes).\n- ALSA: usb: Fix UBSAN warning in parse_audio_unit() (stable-fixes).\n- apparmor: unpack transition table if dfa is not present (bsc#1226031).\n- arm64: ACPI: NUMA: initialize all values of acpi_early_node_map to (git-fixes)\n- arm64: Add Neoverse-V2 part (git-fixes)\n- arm64: armv8_deprecated: Fix warning in isndep cpuhp starting process (git-fixes)\n- arm64: barrier: Restore spec_bar() macro (git-fixes)\n- arm64: cputype: Add Cortex-A720 definitions (git-fixes)\n- arm64: cputype: Add Cortex-A725 definitions (git-fixes)\n- arm64: cputype: Add Cortex-X1C definitions (git-fixes)\n- arm64: cputype: Add Cortex-X3 definitions (git-fixes)\n- arm64: cputype: Add Cortex-X4 definitions (git-fixes)\n- arm64: cputype: Add Cortex-X925 definitions (git-fixes)\n- arm64: cputype: Add Neoverse-V3 definitions (git-fixes)\n- arm64: dts: imx8mp: add HDMI power-domains (git-fixes)\n- arm64: dts: imx8mp: Add NPU Node (git-fixes)\n- arm64: dts: imx8mp: Fix pgc vpu locations (git-fixes)\n- arm64: dts: imx8mp: Fix pgc_mlmix location (git-fixes)\n- arm64: errata: Expand speculative SSBS workaround (again) (git-fixes)\n- arm64: errata: Expand speculative SSBS workaround (git-fixes)\n- arm64: errata: Unify speculative SSBS errata logic (git-fixes). Update config files.\n- arm64: Fix KASAN random tag seed initialization (git-fixes)\n- arm64: jump_label: Ensure patched jump_labels are visible to all CPUs (git-fixes)\n- ASoC: allow module autoloading for table board_ids (stable-fixes).\n- ASoC: allow module autoloading for table db1200_pids (stable-fixes).\n- ASoC: amd: acp: fix module autoloading (git-fixes).\n- ASoC: amd: yc: Add quirk entry for OMEN by HP Gaming Laptop 16-n0xxx (bsc#1227182).\n- ASoC: amd: yc: Support mic on HP 14-em0002la (stable-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: Support mic on Lenovo Thinkpad E14 Gen 6 (stable-fixes).\n- ASoC: codecs: wcd938x-sdw: Correct Soundwire ports mask (git-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: wsa881x: Correct Soundwire ports mask (git-fixes).\n- ASoC: codecs: wsa883x: 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: codecs: wsa884x: Correct Soundwire ports mask (git-fixes).\n- ASoC: cs35l45: Checks index of cs35l45_irqs[] (stable-fixes).\n- ASoC: cs35l56: Handle OTP read latency over SoundWire (stable-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: 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: fsl_micfil: Expand the range of FIFO watermark mask (stable-fixes).\n- ASoC: mediatek: mt8188: Mark AFE_DAC_CON0 register as volatile (stable-fixes).\n- ASoC: meson: axg-fifo: fix irq scheduling issue with PREEMPT_RT (git-fixes).\n- ASoC: meson: axg-fifo: fix irq scheduling issue with PREEMPT_RT (git-fixes).\n- ASoC: nau8822: Lower debug print priority (stable-fixes).\n- ASoC: nau8822: Lower debug print priority (stable-fixes).\n- ASoC: SOF: amd: Fix for acp init sequence (git-fixes).\n- ASoC: SOF: Intel: hda-dsp: Make sure that no irq handler is pending before suspend (stable-fixes).\n- ASoC: SOF: ipc4: check return value of snd_sof_ipc_msg_data (stable-fixes).\n- ASoC: SOF: mediatek: Add missing board compatible (stable-fixes).\n- ASoC: SOF: Remove libraries from topology lookups (git-fixes).\n- ASoC: SOF: Remove libraries from topology lookups (git-fixes).\n- ata: libata-scsi: Do not overwrite valid sense data when CK_COND=1 (stable-fixes).\n- ata: libata-scsi: Honor the D_SENSE bit for CK_COND=1 and no error (stable-fixes).\n- Bluetooth: Add device 13d3:3572 IMC Networks Bluetooth Radio (stable-fixes).\n- Bluetooth: bnep: Fix out-of-bound access (stable-fixes).\n- Bluetooth: btintel: Fail setup on error (git-fixes).\n- Bluetooth: btnxpuart: Shutdown timer and prevent rearming when driver unloading (stable-fixes).\n- Bluetooth: btusb: Add Realtek RTL8852BE support ID 0x13d3:0x3591 (stable-fixes).\n- Bluetooth: btusb: Add RTL8852BE device 0489:e125 to device tables (stable-fixes).\n- Bluetooth: Fix usage of __hci_cmd_sync_status (git-fixes).\n- Bluetooth: hci_conn: Check non NULL function before calling for HFP offload (stable-fixes).\n- Bluetooth: hci_core: Fix LE quote calculation (git-fixes).\n- Bluetooth: hci_core: Fix not handling hibernation actions (git-fixes).\n- Bluetooth: hci_sync: avoid dup filtering when passive scanning with adv monitor (git-fixes).\n- Bluetooth: hci_sync: Fix suspending with wrong filter policy (git-fixes).\n- Bluetooth: l2cap: always unlock channel in l2cap_conless_channel() (git-fixes).\n- Bluetooth: L2CAP: Fix deadlock (git-fixes).\n- Bluetooth: MGMT: Add error handling to pair_device() (git-fixes).\n- Bluetooth: SMP: Fix assumption of Central always being Initiator (git-fixes).\n- bnxt_re: Fix imm_data endianness (git-fixes)\n- bpf, arm64: Fix trampoline for BPF_TRAMP_F_CALL_ORIG (git-fixes)\n- bpf, lpm: Fix check prefixlen before walking trie (git-fixes).\n- bpf: Add crosstask check to __bpf_get_stack (git-fixes).\n- bpf: Detect IP == ksym.end as part of BPF program (git-fixes).\n- bpf: do not infer PTR_TO_CTX for programs with unnamed context type (git-fixes).\n- bpf: enforce precision of R0 on callback return (git-fixes).\n- bpf: Ensure proper register state printing for cond jumps (git-fixes).\n- bpf: extract bpf_ctx_convert_map logic and make it more reusable (git-fixes).\n- bpf: Fix a few selftest failures due to llvm18 change (git-fixes).\n- bpf: Fix a kernel verifier crash in stacksafe() (bsc#1225903).\n- bpf: Fix check_stack_write_fixed_off() to correctly spill imm (git-fixes).\n- bpf: fix control-flow graph checking in privileged mode (git-fixes).\n- bpf: Fix kfunc callback register type handling (git-fixes).\n- bpf: Fix prog_array_map_poke_run map poke update (git-fixes).\n- bpf: Fix unnecessary -EBUSY from htab_lock_bucket (git-fixes).\n- bpf: handle bpf_user_pt_regs_t typedef explicitly for PTR_TO_CTX global arg (git-fixes).\n- bpf: hardcode BPF_PROG_PACK_SIZE to 2MB * num_possible_nodes() (git-fixes).\n- bpf: kprobe: remove unused declaring of bpf_kprobe_override (git-fixes).\n- bpf: Mark bpf_spin_{lock,unlock}() helpers with notrace correctly (git-fixes).\n- bpf: Remove unnecessary wait from bpf_map_copy_value() (git-fixes).\n- bpf: Set uattr-\u003ebatch.count as zero before batched update or deletion (git-fixes).\n- bpf: simplify btf_get_prog_ctx_type() into btf_is_prog_ctx_type() (git-fixes).\n- bpf/tests: Remove duplicate JSGT tests (git-fixes).\n- bpftool: Align output skeleton ELF code (git-fixes).\n- bpftool: Fix -Wcast-qual warning (git-fixes).\n- bpftool: mark orphaned programs during prog show (git-fixes).\n- bpftool: Silence build warning about calloc() (git-fixes).\n- btrfs: add a btrfs_finish_ordered_extent helper (git-fixes).\n- btrfs: add a is_data_bbio helper (git-fixes).\n- btrfs: add an ordered_extent pointer to struct btrfs_bio (git-fixes).\n- btrfs: copy dir permission and time when creating a stub subvolume (bsc#1228321).\n- btrfs: ensure fast fsync waits for ordered extents after a write failure (git-fixes).\n- btrfs: factor out a btrfs_queue_ordered_fn helper (git-fixes).\n- btrfs: factor out a can_finish_ordered_extent helper (git-fixes).\n- btrfs: fix corruption after buffer fault in during direct IO append write (git-fixes).\n- btrfs: fix double inode unlock for direct IO sync writes (git-fixes).\n- btrfs: fix extent map use-after-free when adding pages to compressed bio (git-fixes).\n- btrfs: fix leak of qgroup extent records after transaction abort (git-fixes).\n- btrfs: fix ordered extent split error handling in btrfs_dio_submit_io (git-fixes).\n- btrfs: limit write bios to a single ordered extent (git-fixes).\n- btrfs: make btrfs_finish_ordered_extent() return void (git-fixes).\n- btrfs: merge the two calls to btrfs_add_ordered_extent in run_delalloc_nocow (git-fixes).\n- btrfs: open code btrfs_bio_end_io in btrfs_dio_submit_io (git-fixes).\n- btrfs: open code end_extent_writepage in end_bio_extent_writepage (git-fixes).\n- btrfs: pass a btrfs_inode to btrfs_fdatawrite_range() (git-fixes).\n- btrfs: pass a btrfs_inode to btrfs_wait_ordered_range() (git-fixes).\n- btrfs: pass an ordered_extent to btrfs_reloc_clone_csums (git-fixes).\n- btrfs: pass an ordered_extent to btrfs_submit_compressed_write (git-fixes).\n- btrfs: remove btrfs_add_ordered_extent (git-fixes).\n- btrfs: rename err to ret in btrfs_direct_write() (git-fixes).\n- btrfs: uninline some static inline helpers from tree-log.h (git-fixes).\n- btrfs: use a btrfs_inode in the log context (struct btrfs_log_ctx) (git-fixes).\n- btrfs: use a btrfs_inode local variable at btrfs_sync_file() (git-fixes).\n- btrfs: use bbio-\u003eordered in btrfs_csum_one_bio (git-fixes).\n- btrfs: use btrfs_finish_ordered_extent to complete buffered writes (git-fixes).\n- btrfs: use btrfs_finish_ordered_extent to complete compressed writes (git-fixes).\n- btrfs: use btrfs_finish_ordered_extent to complete direct writes (git-fixes).\n- btrfs: use irq safe locking when running and adding delayed iputs (git-fixes).\n- cachefiles, erofs: Fix NULL deref in when cachefiles is not doing ondemand-mode (bsc#1229245).\n- cachefiles: add missing lock protection when polling (bsc#1229256).\n- cachefiles: add restore command to recover inflight ondemand read requests (bsc#1229244).\n- cachefiles: add spin_lock for cachefiles_ondemand_info (bsc#1229249).\n- cachefiles: cancel all requests for the object that is being dropped (bsc#1229255).\n- cachefiles: defer exposing anon_fd until after copy_to_user() succeeds (bsc#1229251).\n- cachefiles: extract ondemand info field from cachefiles_object (bsc#1229240).\n- cachefiles: fix slab-use-after-free in cachefiles_ondemand_daemon_read() (bsc#1229247).\n- cachefiles: fix slab-use-after-free in cachefiles_ondemand_get_fd() (bsc#1229246).\n- cachefiles: introduce object ondemand state (bsc#1229239).\n- cachefiles: make on-demand read killable (bsc#1229252).\n- cachefiles: narrow the scope of triggering EPOLLIN events in ondemand mode (bsc#1229243).\n- cachefiles: never get a new anonymous fd if ondemand_id is valid (bsc#1229250).\n- cachefiles: propagate errors from vfs_getxattr() to avoid infinite loop (bsc#1229253).\n- cachefiles: remove err_put_fd label in cachefiles_ondemand_daemon_read() (bsc#1229248).\n- cachefiles: resend an open request if the read request's object is closed (bsc#1229241).\n- cachefiles: stop sending new request when dropping object (bsc#1229254).\n- can: mcp251xfd: tef: prepare to workaround broken TEF FIFO tail index erratum (stable-fixes).\n- can: mcp251xfd: tef: update workaround for erratum DS80000789E 6 of mcp2518fd (stable-fixes).\n- ceph: periodically flush the cap releases (bsc#1230056).\n- certs: Move RSA self-test data to separate file (bsc#1222777).\n- cgroup: Add annotation for holding namespace_sem in current_cgns_cgroup_from_root() (bsc#1222254).\n- cgroup: Eliminate the need for cgroup_mutex in proc_cgroup_show() (bsc#1222254).\n- cgroup: Make operations on the cgroup root_list RCU safe (bsc#1222254).\n- cgroup: preserve KABI of cgroup_root (bsc#1222254).\n- cgroup: Remove unnecessary list_empty() (bsc#1222254).\n- cgroup/cpuset: Prevent UAF in proc_cpuset_show() (bsc#1228801).\n- char: xillybus: Check USB endpoints when probing device (git-fixes).\n- char: xillybus: Do not destroy workqueue from work item running on it (stable-fixes).\n- char: xillybus: Refine workqueue handling (git-fixes).\n- clk: en7523: fix rate divider for slic and spi clocks (git-fixes).\n- clk: qcom: camcc-sc7280: Add parent dependency to all camera GDSCs (git-fixes).\n- clk: qcom: gcc-sa8775p: Update the GDSC wait_val fields and flags (git-fixes).\n- clk: qcom: gcc-sc7280: Update force mem core bit for UFS ICE clock (git-fixes).\n- clk: qcom: gpucc-sa8775p: Park RCG's clk source at XO during disable (git-fixes).\n- clk: qcom: gpucc-sa8775p: Remove the CLK_IS_CRITICAL and ALWAYS_ON flags (git-fixes).\n- clk: qcom: gpucc-sa8775p: Update wait_val fields for GPU GDSC's (git-fixes).\n- clk: qcom: gpucc-sm8350: Park RCG's clk source at XO during disable (git-fixes).\n- clk: qcom: kpss-xcc: Return of_clk_add_hw_provider to transfer the error (git-fixes).\n- clk: qcom: Park shared RCGs upon registration (git-fixes).\n- clk: visconti: Add bounds-checking coverage for struct visconti_pll_provider (stable-fixes).\n- clocksource/drivers/sh_cmt: Address race condition for clock events (stable-fixes).\n- cpu/SMT: Enable SMT only if a core is online (bsc#1214285 bsc#1205462 ltc#200161 ltc#200588 git-fixes).\n- cxl/region: Move cxl_dpa_to_region() work to the region driver (bsc#1228472)\n- dev/parport: fix the array out-of-bounds risk (stable-fixes).\n- device property: Add cleanup.h based fwnode_handle_put() scope based cleanup (stable-fixes).\n- dmaengine: dw: Add memory bus width verification (git-fixes).\n- dmaengine: dw: Add peripheral bus width verification (git-fixes).\n- docs: KVM: Fix register ID of SPSR_FIQ (git-fixes).\n- driver core: Fix uevent_show() vs driver detach race (git-fixes).\n- drm/admgpu: fix dereferencing null pointer context (stable-fixes).\n- drm/amd/display: Add delay to improve LTTPR UHBR interop (stable-fixes).\n- drm/amd/display: Add NULL check for 'afb' before dereferencing in amdgpu_dm_plane_handle_cursor_update (stable-fixes).\n- drm/amd/display: Add null checker before passing variables (stable-fixes).\n- drm/amd/display: Adjust cursor position (git-fixes).\n- drm/amd/display: avoid using null object of framebuffer (git-fixes).\n- drm/amd/display: Check for NULL pointer (stable-fixes).\n- drm/amd/display: fix cursor offset on rotation 180 (git-fixes).\n- drm/amd/display: fix s2idle entry for DCN3.5+ (stable-fixes).\n- drm/amd/display: Skip Recompute DSC Params if no Stream on Link (stable-fixes).\n- drm/amd/pm: Fix the null pointer dereference for vega10_hwmgr (stable-fixes).\n- drm/amdgpu: Actually check flags for all context ops (stable-fixes).\n- drm/amdgpu: Add lock around VF RLCG interface (stable-fixes).\n- drm/amdgpu: fix dereference null return value for the function amdgpu_vm_pt_parent (stable-fixes).\n- drm/amdgpu: fix potential resource leak warning (stable-fixes).\n- drm/amdgpu: Fix the null pointer dereference to ras_manager (stable-fixes).\n- drm/amdgpu: Forward soft recovery errors to userspace (stable-fixes).\n- drm/amdgpu: reset vm state machine after gpu reset(vram lost) (stable-fixes).\n- drm/amdgpu: Validate TA binary size (stable-fixes).\n- drm/amdgpu/jpeg2: properly set atomics vmid field (stable-fixes).\n- drm/amdgpu/jpeg4: properly set atomics vmid field (stable-fixes).\n- drm/amdgpu/pm: Fix the null pointer dereference for smu7 (stable-fixes).\n- drm/amdgpu/pm: Fix the null pointer dereference in apply_state_adjust_rules (stable-fixes).\n- drm/amdgpu/pm: Fix the param type of set_power_profile_mode (stable-fixes).\n- drm/amdgpu/sdma5.2: limit wptr workaround to sdma 5.2.1 (git-fixes).\n- drm/amdgpu/sdma5.2: Update wptr registers as well as doorbell (stable-fixes).\n- drm/bridge: analogix_dp: properly handle zero sized AUX transactions (stable-fixes).\n- drm/client: fix null pointer dereference in drm_client_modeset_probe (git-fixes).\n- drm/dp_mst: Skip CSN if topology probing is not done yet (stable-fixes).\n- drm/etnaviv: do not block scheduler when GPU is still active (stable-fixes).\n- drm/i915: Fix possible int overflow in skl_ddi_calculate_wrpll() (git-fixes).\n- drm/i915/dsi: Make Lenovo Yoga Tab 3 X90F DMI match less strict (git-fixes).\n- drm/i915/gem: Adjust vma offset for framebuffer mmap offset (stable-fixes).\n- drm/i915/gem: Fix Virtual Memory mapping boundaries calculation (git-fixes).\n- drm/i915/hdcp: Fix HDCP2_STREAM_STATUS macro (git-fixes).\n- drm/lima: set gp bus_stop bit before hard reset (stable-fixes).\n- drm/mediatek/dp: Fix spurious kfree() (git-fixes).\n- drm/msm: Reduce fallout of fence signaling vs reclaim hangs (stable-fixes).\n- drm/msm/dp: fix the max supported bpp logic (git-fixes).\n- drm/msm/dp: reset the link phy params before link training (git-fixes).\n- drm/msm/dpu: capture snapshot on the first commit_done timeout (stable-fixes).\n- drm/msm/dpu: cleanup FB if dpu_format_populate_layout fails (git-fixes).\n- drm/msm/dpu: do not play tricks with debug macros (git-fixes).\n- drm/msm/dpu: drop MSM_ENC_VBLANK support (stable-fixes).\n- drm/msm/dpu: move dpu_encoder's connector assignment to atomic_enable() (git-fixes).\n- drm/msm/dpu: split dpu_encoder_wait_for_event into two functions (stable-fixes).\n- drm/msm/dpu: take plane rotation into account for wide planes (git-fixes).\n- drm/msm/dpu: try multirect based on mdp clock limits (stable-fixes).\n- drm/msm/dpu: use drmm-managed allocation for dpu_encoder_phys (stable-fixes).\n- drm/msm/mdss: Rename path references to mdp_path (stable-fixes).\n- drm/msm/mdss: switch mdss to use devm_of_icc_get() (stable-fixes).\n- drm/nouveau: prime: fix refcount underflow (git-fixes).\n- drm/panel: nt36523: Set 120Hz fps for xiaomi,elish panels (stable-fixes).\n- drm/radeon: Remove __counted_by from StateArray.states[] (git-fixes).\n- drm/radeon/evergreen_cs: Clean up errors in evergreen_cs.c (bsc#1229024).\n- drm/rockchip: vop2: clear afbc en and transform bit for cluster window at linear mode (stable-fixes).\n- drm/virtio: Fix type of dma-fence context variable (git-fixes).\n- drm/vmwgfx: Fix a deadlock in dma buf fence polling (git-fixes).\n- drm/vmwgfx: Fix overlay when using Screen Targets (git-fixes).\n- drm/vmwgfx: Fix prime with external buffers (git-fixes).\n- efi/libstub: Zero initialize heap allocated struct screen_info (git-fixes).\n- evm: do not copy up 'security.evm' xattr (git-fixes).\n- firmware: cirrus: cs_dsp: Initialize debugfs_root to invalid (stable-fixes).\n- fs/netfs/fscache_cookie: add missing 'n_accesses' check (bsc#1229455).\n- fuse: Initialize beyond-EOF page contents before setting uptodate (bsc#1229456).\n- genirq/cpuhotplug, x86/vector: Prevent vector leak during CPU offline (git-fixes).\n- genirq/generic_chip: Make irq_remove_generic_chip() irqdomain aware (git-fixes).\n- genirq/matrix: Exclude managed interrupts in irq_matrix_allocated() (git-fixes).\n- gfs2: setattr_chown: Add missing initialization (git-fixes).\n- gpio: mlxbf3: Support shutdown() function (git-fixes).\n- gpio: prevent potential speculation leaks in gpio_device_get_desc() (stable-fixes).\n- gpio: sysfs: extend the critical section for unregistering sysfs devices (stable-fixes).\n- gss_krb5: Fix the error handling path for crypto_sync_skcipher_setkey (git-fixes).\n- hfs: fix to initialize fields of hfs_inode_info after hfs_alloc_inode() (git-fixes).\n- HID: wacom: Defer calculation of resolution until resolution_code is known (git-fixes).\n- hwmon: (ltc2992) Avoid division by zero (stable-fixes).\n- hwmon: (ltc2992) Fix memory leak in ltc2992_parse_dt() (git-fixes).\n- hwmon: (pc87360) Bounds check data-\u003einnr usage (stable-fixes).\n- i2c: Fix conditional for substituting empty ACPI functions (stable-fixes).\n- i2c: qcom-geni: Add missing clk_disable_unprepare in geni_i2c_runtime_resume (git-fixes).\n- i2c: qcom-geni: Add missing geni_icc_disable in geni_i2c_runtime_resume (git-fixes).\n- i2c: qcom-geni: Add missing geni_icc_disable in geni_i2c_runtime_resume (git-fixes).\n- i2c: riic: avoid potential division by zero (stable-fixes).\n- i2c: smbus: Improve handling of stuck alerts (git-fixes).\n- i2c: smbus: Send alert notifications to all devices if source not found (git-fixes).\n- i2c: stm32f7: Add atomic_xfer method to driver (stable-fixes).\n- i2c: Use IS_REACHABLE() for substituting empty ACPI functions (git-fixes).\n- i3c: mipi-i3c-hci: Do not unmap region not mapped for transfer (stable-fixes).\n- i3c: mipi-i3c-hci: Remove BUG() when Ring Abort request times out (stable-fixes).\n- i915/perf: Remove code to update PWR_CLK_STATE for gen12 (git-fixes).\n- ice: Fix NULL pointer access, if PF does not support SRIOV_LAG (bsc#1228737).\n- Input: i8042 - add forcenorestore quirk to leave controller untouched even on s3 (stable-fixes).\n- Input: i8042 - add Fujitsu Lifebook E756 to i8042 quirk table (bsc#1229056).\n- Input: i8042 - use new forcenorestore quirk to replace old buggy quirk combination (stable-fixes).\n- Input: MT - limit max slots (stable-fixes).\n- io_uring: Drop per-ctx dummy_ubuf (git-fixes).\n- io_uring: fix io_match_task must_hold (git-fixes).\n- io_uring: Fix probe of disabled operations (git-fixes).\n- io_uring: tighten task exit cancellations (git-fixes).\n- io_uring/advise: support 64-bit lengths (git-fixes).\n- iommu/amd: Convert comma to semicolon (git-fixes).\n- iommu/vt-d: Fix identity map bounds in si_domain_init() (git-fixes).\n- iommufd/device: Fix hwpt at err_unresv in iommufd_device_do_replace() (git-fixes).\n- ip6_tunnel: Fix broken GRO (bsc#1229444).\n- ipv6: sr: fix incorrect unregister order (git-fixes).\n- irqdomain: Fixed unbalanced fwnode get and put (git-fixes).\n- jfs: define xtree root and page independently (git-fixes).\n- jfs: fix null ptr deref in dtInsertEntry (git-fixes).\n- jfs: Fix shift-out-of-bounds in dbDiscardAG (git-fixes).\n- jump_label: Clarify condition in static_key_fast_inc_not_disabled() (git-fixes).\n- jump_label: Fix concurrency issues in static_key_slow_dec() (git-fixes).\n- jump_label: Fix the fix, brown paper bags galore (git-fixes).\n- jump_label: Simplify and clarify static_key_fast_inc_cpus_locked() (git-fixes).\n- kabi fix for KVM: s390: fix LPSWEY handling (bsc#1227634 git-fixes).\n- kabi fix for SUNRPC: add a missing rpc_stat for TCP TLS (git-fixes).\n- kABI fix of: virtio-crypto: handle config changed by work queue (git-fixes).\n- kABI workaround for sound core UMP conversion (stable-fixes).\n- kabi/severities: ignore kABI for FireWire sound local symbols (bsc#1208783)\n- kabi/severity: add nvme common code The nvme common code is also allowed to change the data structures, there are only internal users.\n- kcov: properly check for softirq context (git-fixes).\n- kernfs: Convert kernfs_path_from_node_locked() from strlcpy() to strscpy() (bsc#1229134).\n- kernfs: fix false-positive WARN(nr_mmapped) in kernfs_drain_open_files (git-fixes).\n- kprobes: Fix to check symbol prefixes correctly (git-fixes).\n- kprobes: Prohibit probing on CFI preamble symbol (git-fixes).\n- KVM: Always flush async #PF workqueue when vCPU is being destroyed (git-fixes).\n- KVM: arm64: AArch32: Fix spurious trapping of conditional instructions (git-fixes).\n- KVM: arm64: Add missing memory barriers when switching to pKVM's hyp pgd (git-fixes).\n- KVM: arm64: Allow AArch32 PSTATE.M to be restored as System mode (git-fixes).\n- KVM: arm64: Fix __pkvm_init_switch_pgd call ABI (git-fixes).\n- KVM: arm64: Fix AArch32 register narrowing on userspace write (git-fixes).\n- KVM: arm64: Fix clobbered ELR in sync abort/SError (git-fixes)\n- KVM: arm64: GICv4: Do not perform a map to a mapped vLPI (git-fixes).\n- KVM: arm64: timers: Correctly handle TGE flip with CNTPOFF_EL2 (git-fixes).\n- KVM: arm64: timers: Fix resource leaks in kvm_timer_hyp_init() (git-fixes).\n- KVM: arm64: vgic-its: Test for valid IRQ in its_sync_lpi_pending_table() (git-fixes).\n- KVM: arm64: vgic-its: Test for valid IRQ in MOVALL handler (git-fixes).\n- KVM: arm64: vgic-v2: Use cpuid from userspace as vcpu_id (git-fixes).\n- KVM: arm64: vgic-v4: Restore pending state on host userspace write (git-fixes).\n- KVM: arm64: vgic: Add a non-locking primitive for kvm_vgic_vcpu_destroy() (git-fixes).\n- KVM: arm64: vgic: Force vcpu vgic teardown on vcpu destroy (git-fixes).\n- KVM: arm64: vgic: Simplify kvm_vgic_destroy() (git-fixes).\n- KVM: fix kvm_mmu_memory_cache allocation warning (git-fixes).\n- KVM: Make KVM_MEM_GUEST_MEMFD mutually exclusive with KVM_MEM_READONLY (git-fixes).\n- KVM: nVMX: Add a helper to get highest pending from Posted Interrupt vector (git-fixes).\n- KVM: nVMX: Check for pending posted interrupts when looking for nested events (git-fixes).\n- KVM: nVMX: Request immediate exit iff pending nested event needs injection (git-fixes).\n- KVM: PPC: Book3S HV: Fix the set_one_reg for MMCR3 (bsc#1194869).\n- KVM: PPC: Book3S HV: Handle pending exceptions on guest entry with MSR_EE (bsc#1215199).\n- KVM: Protect vcpu-\u003epid dereference via debugfs with RCU (git-fixes).\n- KVM: Reject overly excessive IDs in KVM_CREATE_VCPU (git-fixes).\n- KVM: s390: fix LPSWEY handling (bsc#1227634 git-fixes).\n- KVM: s390: fix validity interception issue when gisa is switched off (git-fixes bsc#1229167).\n- kvm: s390: Reject memory region operations for ucontrol VMs (git-fixes bsc#1229168).\n- KVM: Stop processing *all* memslots when 'null' mmu_notifier handler is found (git-fixes).\n- KVM: VMX: Move posted interrupt descriptor out of VMX code (git-fixes).\n- KVM: VMX: Split out the non-virtualization part of vmx_interrupt_blocked() (git-fixes).\n- KVM: VMX: Switch __vmx_exit() and kvm_x86_vendor_exit() in vmx_exit() (git-fixes).\n- KVM: x86: Limit check IDs for KVM_SET_BOOT_CPU_ID (git-fixes).\n- KVM: x86/mmu: Bug the VM if KVM tries to split a !hugepage SPTE (git-fixes).\n- libbpf: Add missing LIBBPF_API annotation to libbpf_set_memlock_rlim API (git-fixes).\n- libbpf: Apply map_set_def_max_entries() for inner_maps on creation (git-fixes).\n- libbpf: Fix faccessat() usage on Android (git-fixes).\n- libbpf: Use OPTS_SET() macro in bpf_xdp_query() (git-fixes).\n- md-cluster: fix hanging issue while a new disk adding (bsc#1223395).\n- md-cluster: fix hanging issue while a new disk adding (bsc#1223395).\n- md-cluster: fix no recovery job when adding/re-adding a disk (bsc#1223395).\n- md-cluster: fix no recovery job when adding/re-adding a disk (bsc#1223395).\n- md-cluster: keeping kabi compatibility for upstream commit 35a0a409fa26 (bsc#1223395).\n- md: add a mddev_add_trace_msg helper (git-fixes).\n- md: add check for sleepers in md_wakeup_thread() (git-fixes).\n- md: change the return value type of md_write_start to void (git-fixes).\n- md: do not account sync_io if iostats of the disk is disabled (git-fixes).\n- md: do not delete safemode_timer in mddev_suspend (git-fixes).\n- md: Do not wait for MD_RECOVERY_NEEDED for HOT_REMOVE_DISK ioctl (git-fixes).\n- md: factor out a helper exceed_read_errors() to check read_errors (git-fixes).\n- md: fix a suspicious RCU usage warning (git-fixes).\n- md/md-bitmap: fix writing non bitmap pages (git-fixes).\n- md/raid1: set max_sectors during early return from choose_slow_rdev() (git-fixes).\n- md/raid1: support read error check (git-fixes).\n- md/raid5: fix deadlock that raid5d() wait for itself to clear MD_SB_CHANGE_PENDING (git-fixes).\n- md/raid5: fix spares errors about rcu usage (git-fixes).\n- md/raid5: recheck if reshape has finished with device_lock held (git-fixes).\n- media: amphion: Remove lock in s_ctrl callback (stable-fixes).\n- media: drivers/media/dvb-core: copy user arrays safely (stable-fixes).\n- media: pci: cx23885: check cx23885_vdev_init() return (stable-fixes).\n- media: Revert 'media: dvb-usb: Fix unexpected infinite loop in dvb_usb_read_remote_control()' (git-fixes).\n- media: uvcvideo: Add quirk for invalid dev_sof in Logitech C920 (git-fixes).\n- media: uvcvideo: Disable autosuspend for Insta360 Link (stable-fixes).\n- media: uvcvideo: Fix the bandwdith quirk on USB 3.x (stable-fixes).\n- media: uvcvideo: Ignore empty TS packets (stable-fixes).\n- media: uvcvideo: Quirk for invalid dev_sof in Logitech C922 (stable-fixes).\n- media: xc2028: avoid use-after-free in load_firmware_cb() (stable-fixes).\n- memcg: protect concurrent access to mem_cgroup_idr (git-fixes).\n- memory: stm32-fmc2-ebi: check regmap_read return value (stable-fixes).\n- memory: tegra: Skip SID programming if SID registers are not set (stable-fixes).\n- minmax: add a few more MIN_T/MAX_T users (bsc#1229024).\n- minmax: avoid overly complicated constant expressions in VM code (bsc#1229024).\n- minmax: do not use max() in situations that want a C constant expression (bsc#1229024).\n- minmax: fix up min3() and max3() too (bsc#1229024).\n- minmax: improve macro expansion and type checking (bsc#1229024).\n- minmax: make generic MIN() and MAX() macros available everywhere (bsc#1229024).\n- minmax: simplify and clarify min_t()/max_t() implementation (bsc#1229024).\n- minmax: simplify min()/max()/clamp() implementation (bsc#1229024).\n- mm, kmsan: fix infinite recursion due to RCU critical section (git-fixes).\n- mm: prevent derefencing NULL ptr in pfn_section_valid() (git-fixes).\n- mmc: dw_mmc: allow biu and ciu clocks to defer (git-fixes).\n- mmc: mmc_test: Fix NULL dereference on allocation failure (git-fixes).\n- mmc: mtk-sd: receive cmd8 data when hs400 tuning fail (git-fixes).\n- net: drop bad gso csum_start and offset in virtio_net_hdr (git-fixes).\n- net: ethernet: mtk_wed: fix use-after-free panic in mtk_wed_setup_tc_block_cb() (git-fixes).\n- net: fix sk_memory_allocated_{add|sub} vs softirqs (bsc#1228757).\n- net: mana: Add support for page sizes other than 4KB on ARM64 (jsc#PED-8491 bsc#1226530).\n- net: mana: Fix doorbell out of order violation and avoid unnecessary doorbell rings (bsc#1229154).\n- net: mana: Fix race of mana_hwc_post_rx_wqe and new hwc response (git-fixes).\n- net: mana: Fix RX buf alloc_size alignment and atomic op panic (bsc#1229086).\n- net: missing check virtio (git-fixes).\n- net: phy: micrel: Fix the KSZ9131 MDI-X status issue (git-fixes).\n- net: phy: realtek: add support for RTL8366S Gigabit PHY (git-fixes).\n- net: usb: qmi_wwan: fix memory leak for not ip packets (git-fixes).\n- net: usb: sr9700: fix uninitialized variable use in sr_mdio_read (git-fixes).\n- net/iucv: fix the allocation size of iucv_path_table array (git-fixes bsc#1229451).\n- net/iucv: fix use after free in iucv_sock_close() (bsc#1228973).\n- net/rds: fix possible cp null dereference (git-fixes).\n- net/sched: initialize noop_qdisc owner (git-fixes).\n- netfs, fscache: export fscache_put_volume() and add fscache_try_get_volume() (bsc#1228459 bsc#1228462).\n- nfc: pn533: Add poll mod list filling check (git-fixes).\n- nfs: do not invalidate dentries on transient errors (git-fixes).\n- nfs: expose /proc/net/sunrpc/nfs in net namespaces (git-fixes).\n- nfs: make the rpc_stat per net namespace (git-fixes).\n- nfs: pass explicit offset/count to trace events (git-fixes).\n- nfs: propagate readlink errors in nfs_symlink_filler (git-fixes).\n- NFSD: Support write delegations in LAYOUTGET (git-fixes).\n- NFSv4.1 another fix for EXCHGID4_FLAG_USE_PNFS_DS for DS server (git-fixes).\n- nouveau/firmware: use dma non-coherent allocator (git-fixes).\n- nvme_core: scan namespaces asynchronously (bsc#1224105).\n- nvme-multipath: find NUMA path only for online numa-node (git-fixes).\n- nvme-multipath: implement 'queue-depth' iopolicy (bsc#1227706).\n- nvme-multipath: prepare for 'queue-depth' iopolicy (bsc#1227706).\n- nvme-pci: add missing condition check for existence of mapped data (git-fixes).\n- nvme-pci: do not directly handle subsys reset fallout (bsc#1220066).\n- nvme-pci: Fix the instructions for disabling power management (git-fixes).\n- nvme-sysfs: add 'tls_configured_key' sysfs attribute (bsc#1221857).\n- nvme-sysfs: add 'tls_keyring' attribute (bsc#1221857).\n- nvme-tcp: check for invalidated or revoked key (bsc#1221857).\n- nvme-tcp: sanitize TLS key handling (bsc#1221857).\n- nvme: add a newline to the 'tls_key' sysfs attribute (bsc#1221857).\n- nvme: adjust multiples of NVME_CTRL_PAGE_SIZE in offset (git-fixes).\n- nvme: avoid double free special payload (git-fixes).\n- nvme: fix NVME_NS_DEAC may incorrectly identifying the disk as EXT_LBA (git-fixes).\n- nvme: fixup comment for nvme RDMA Provider Type (git-fixes).\n- nvme: split off TLS sysfs attributes into a separate group (bsc#1221857).\n- nvme: tcp: remove unnecessary goto statement (bsc#1221857).\n- nvmet-auth: fix nvmet_auth hash error handling (git-fixes).\n- nvmet: always initialize cqe.result (git-fixes).\n- nvmet: do not return 'reserved' for empty TSAS values (git-fixes).\n- nvmet: fix a possible leak when destroy a ctrl during qp establishment (git-fixes).\n- nvmet: make 'tsas' attribute idempotent for RDMA (git-fixes).\n- ocfs2: strict bound check before memcmp in ocfs2_xattr_find_entry() (bsc#1228410).\n- padata: Fix possible divide-by-0 panic in padata_mt_helper() (git-fixes).\n- PCI: Add Edimax Vendor ID to pci_ids.h (stable-fixes).\n- PCI: hv: Return zero, not garbage, when reading PCI_INTERRUPT_PIN (git-fixes).\n- PCI: loongson: Enable MSI in LS7A Root Complex (stable-fixes).\n- perf/smmuv3: Enable HiSilicon Erratum 162001900 quirk for HIP08/09 (git-fixes).\n- pinctrl: mediatek: common-v2: Fix broken bias-disable for PULL_PU_PD_RSEL_TYPE (git-fixes).\n- pinctrl: rockchip: correct RK3328 iomux width flag for GPIO2-B pins (git-fixes).\n- pinctrl: single: fix potential NULL dereference in pcs_get_function() (git-fixes).\n- pinctrl: starfive: jh7110: Correct the level trigger configuration of iev register (git-fixes).\n- platform/chrome: cros_ec_proto: Lock device when updating MKBP version (git-fixes).\n- platform/chrome: cros_ec_proto: Lock device when updating MKBP version (git-fixes).\n- platform/surface: aggregator: Fix warning when controller is destroyed in probe (git-fixes).\n- platform/x86: lg-laptop: fix %s null argument warning (stable-fixes).\n- platform/x86/amd/hsmp: Add support for ACPI based probing (jsc#PED-8779).\n- platform/x86/amd/hsmp: Cache pci_dev in struct hsmp_socket (jsc#PED-8779).\n- platform/x86/amd/hsmp: Change devm_kzalloc() to devm_kcalloc() (jsc#PED-8779).\n- platform/x86/amd/hsmp: Check HSMP support on AMD family of processors (jsc#PED-8779).\n- platform/x86/amd/hsmp: Check num_sockets against MAX_AMD_SOCKETS (jsc#PED-8779).\n- platform/x86/amd/hsmp: Create static func to handle platdev (jsc#PED-8779).\n- platform/x86/amd/hsmp: Define a struct to hold mailbox regs (jsc#PED-8779).\n- platform/x86/amd/hsmp: Move dev from platdev to hsmp_socket (jsc#PED-8779).\n- platform/x86/amd/hsmp: Move hsmp_test to probe (jsc#PED-8779).\n- platform/x86/amd/hsmp: Non-ACPI support for AMD F1A_M00~0Fh (jsc#PED-8779).\n- platform/x86/amd/hsmp: Remove extra parenthesis and add a space (jsc#PED-8779).\n- platform/x86/amd/hsmp: Restructure sysfs group creation (jsc#PED-8779).\n- platform/x86/amd/hsmp: switch to use device_add_groups() (jsc#PED-8779).\n- platform/x86/intel/ifs: Initialize union ifs_status to zero (git-fixes).\n- power: supply: axp288_charger: Fix constant_charge_voltage writes (git-fixes).\n- power: supply: axp288_charger: Round constant_charge_voltage writes down (git-fixes).\n- power: supply: qcom_battmgr: return EAGAIN when firmware service is not up (git-fixes).\n- powerpc: fix a file leak in kvm_vcpu_ioctl_enable_cap() (bsc#1194869).\n- powerpc: xor_vmx: Add '-mhard-float' to CFLAGS (bsc#1194869).\n- powerpc/64: Set _IO_BASE to POISON_POINTER_DELTA not 0 for CONFIG_PCI=n (bsc#1194869).\n- powerpc/io: Avoid clang null pointer arithmetic warnings (bsc#1194869).\n- powerpc/kexec_file: fix cpus node update to FDT (bsc#1194869).\n- powerpc/kexec: make the update_cpus_node() function public (bsc#1194869).\n- powerpc/kexec: split CONFIG_KEXEC_FILE and CONFIG_CRASH_DUMP (bsc#1194869).\n- powerpc/pseries: Add failure related checks for h_get_mpp and h_get_ppp (bsc#1194869).\n- powerpc/pseries: Whitelist dtl slub object for copying to userspace (bsc#1194869).\n- powerpc/radix: Move some functions into #ifdef CONFIG_KVM_BOOK3S_HV_POSSIBLE (bsc#1194869).\n- powerpc/topology: Check if a core is online (bsc#1214285 bsc#1205462 ltc#200161 ltc#200588 git-fixes).\n- powerpc/xmon: Check cpu id in commands 'c#', 'dp#' and 'dx#' (bsc#1194869).\n- printk/panic: Allow cpu backtraces to be written into ringbuffer during panic (bsc#1225607).\n- RDMA: Fix netdev tracker in ib_device_set_netdev (git-fixes)\n- RDMA/cache: Release GID table even if leak is detected (git-fixes)\n- RDMA/device: Return error earlier if port in not valid (git-fixes)\n- RDMA/hns: Check atomic wr length (git-fixes)\n- RDMA/hns: Fix insufficient extend DB for VFs. (git-fixes)\n- RDMA/hns: Fix mbx timing out before CMD execution is completed (git-fixes)\n- RDMA/hns: Fix missing pagesize and alignment check in FRMR (git-fixes)\n- RDMA/hns: Fix shift-out-bounds when max_inline_data is 0 (git-fixes)\n- RDMA/hns: Fix soft lockup under heavy CEQE load (git-fixes)\n- RDMA/hns: Fix undifined behavior caused by invalid max_sge (git-fixes)\n- RDMA/hns: Fix unmatch exception handling when init eq table fails (git-fixes)\n- RDMA/iwcm: Fix a use-after-free related to destroying CM IDs (git-fixes)\n- RDMA/mana_ib: Use virtual address in dma regions for MRs (git-fixes).\n- RDMA/mlx4: Fix truncated output warning in alias_GUID.c (git-fixes)\n- RDMA/mlx4: Fix truncated output warning in mad.c (git-fixes)\n- RDMA/mlx5: Set mkeys for dmabuf at PAGE_SIZE (git-fixes)\n- RDMA/rxe: Do not set BTH_ACK_MASK for UC or UD QPs (git-fixes)\n- reiserfs: fix uninit-value in comp_keys (git-fixes).\n- rtc: nct3018y: fix possible NULL dereference (stable-fixes).\n- s390/cpum_cf: Fix endless loop in CF_DIAG event stop (git-fixes bsc#1229171).\n- s390/dasd: fix error checks in dasd_copy_pair_store() (git-fixes bsc#1229173).\n- s390/dasd: fix error recovery leading to data corruption on ESE devices (git-fixes bsc#1229452).\n- s390/pci: Add missing virt_to_phys() for directed DIBV (git-fixes bsc#1229174).\n- s390/pci: Allow allocation of more than 1 MSI interrupt (git-fixes bsc#1229172).\n- s390/pci: Refactor arch_setup_msi_irqs() (git-fixes bsc#1229172).\n- s390/pkey: harmonize pkey s390 debug feature calls (bsc#1228720).\n- s390/pkey: introduce dynamic debugging for pkey (bsc#1228720).\n- s390/sclp: Prevent release of buffer in I/O (git-fixes bsc#1229169).\n- s390/uv: Panic for set and remove shared access UVC errors (git-fixes bsc#1229170).\n- samples/bpf: syscall_tp_user: Fix array out-of-bound access (git-fixes).\n- samples/bpf: syscall_tp_user: Rename num_progs into nr_tests (git-fixes).\n- sbitmap: use READ_ONCE to access map-\u003eword (stable-fixes).\n- scsi: lpfc: Allow DEVICE_RECOVERY mode after RSCN receipt if in PRLI_ISSUE state (bsc#1228857).\n- scsi: lpfc: Cancel ELS WQE instead of issuing abort when SLI port is inactive (bsc#1228857).\n- scsi: lpfc: Fix handling of fully recovered fabric node in dev_loss callbk (bsc#1228857).\n- scsi: lpfc: Fix incorrect request len mbox field when setting trunking via sysfs (bsc#1228857).\n- scsi: lpfc: Handle mailbox timeouts in lpfc_get_sfp_info (bsc#1228857).\n- scsi: lpfc: Relax PRLI issue conditions after GID_FT response (bsc#1228857).\n- scsi: lpfc: Revise lpfc_prep_embed_io routine with proper endian macro usages (bsc#1228857).\n- scsi: lpfc: Update lpfc version to 14.4.0.3 (bsc#1228857).\n- scsi: qla2xxx: Avoid possible run-time warning with long model_num (bsc#1228850).\n- scsi: qla2xxx: Complete command early within lock (bsc#1228850).\n- scsi: qla2xxx: Convert comma to semicolon (bsc#1228850).\n- scsi: qla2xxx: Drop driver owner assignment (bsc#1228850).\n- scsi: qla2xxx: During vport delete send async logout explicitly (bsc#1228850).\n- scsi: qla2xxx: Fix debugfs output for fw_resource_count (bsc#1228850).\n- scsi: qla2xxx: Fix flash read failure (bsc#1228850).\n- scsi: qla2xxx: Fix for possible memory corruption (bsc#1228850).\n- scsi: qla2xxx: Fix optrom version displayed in FDMI (bsc#1228850).\n- scsi: qla2xxx: Indent help text (bsc#1228850).\n- scsi: qla2xxx: Reduce fabric scan duplicate code (bsc#1228850).\n- scsi: qla2xxx: Remove unused struct 'scsi_dif_tuple' (bsc#1228850).\n- scsi: qla2xxx: Return ENOBUFS if sg_cnt is more than one for ELS cmds (bsc#1228850).\n- scsi: qla2xxx: Unable to act on RSCN for port online (bsc#1228850).\n- scsi: qla2xxx: Update version to 10.02.09.300-k (bsc#1228850).\n- scsi: qla2xxx: Use QP lock to search for bsg (bsc#1228850).\n- scsi: qla2xxx: validate nvme_local_port correctly (bsc#1228850).\n- selftest/bpf: Add map_in_maps with BPF_MAP_TYPE_PERF_EVENT_ARRAY values (git-fixes).\n- selftests/bpf: Add a test to verify previous stacksafe() fix (bsc#1225903).\n- selftests/bpf: Add assert for user stacks in test_task_stack (git-fixes).\n- selftests/bpf: Add netkit to tc_redirect selftest (git-fixes).\n- selftests/bpf: De-veth-ize the tc_redirect test case (git-fixes).\n- selftests/bpf: Disable IPv6 for lwt_redirect test (git-fixes).\n- selftests/bpf: fix bpf_loop_bench for new callback verification scheme (git-fixes).\n- selftests/bpf: fix compiler warnings in RELEASE=1 mode (git-fixes).\n- selftests/bpf: Fix erroneous bitmask operation (git-fixes).\n- selftests/bpf: Fix issues in setup_classid_environment() (git-fixes).\n- selftests/bpf: Fix potential premature unload in bpf_testmod (git-fixes).\n- selftests/bpf: Fix pyperf180 compilation failure with clang18 (git-fixes).\n- selftests/bpf: fix RELEASE=1 build for tc_opts (git-fixes).\n- selftests/bpf: Fix the flaky tc_redirect_dtime test (git-fixes).\n- selftests/bpf: Fix up xdp bonding test wrt feature flags (git-fixes).\n- selftests/bpf: Make linked_list failure test more robust (git-fixes).\n- selftests/bpf: Relax time_tai test for equal timestamps in tai_forward (git-fixes).\n- selftests/bpf: satisfy compiler by having explicit return in btf test (git-fixes).\n- selftests/bpf: Skip module_fentry_shadow test when bpf_testmod is not available (git-fixes).\n- selftests/bpf: Wait for the netstamp_needed_key static key to be turned on (git-fixes).\n- serial: core: check uartclk for zero to avoid divide by zero (stable-fixes).\n- soc: qcom: cmd-db: Map shared memory as WC, not WB (git-fixes).\n- soc: qcom: pmic_glink: Actually communicate when remote goes down (git-fixes).\n- soundwire: stream: fix programming slave ports for non-continous port maps (git-fixes).\n- spi: Add empty versions of ACPI functions (stable-fixes).\n- spi: microchip-core: fix init function not setting the master and motorola modes (git-fixes).\n- spi: microchip-core: switch to use modern name (stable-fixes).\n- spi: spi-fsl-lpspi: Fix scldiv calculation (git-fixes).\n- spi: spidev: Add missing spi_device_id for bh2228fv (git-fixes).\n- Squashfs: fix variable overflow triggered by sysbot (git-fixes).\n- squashfs: squashfs_read_data need to check if the length is 0 (git-fixes).\n- ssb: Fix division by zero issue in ssb_calc_clock_rate (stable-fixes).\n- staging: iio: resolver: ad2s1210: fix use before initialization (stable-fixes).\n- staging: ks7010: disable bh on tx_dev_lock (stable-fixes).\n- string.h: Introduce memtostr() and memtostr_pad() (bsc#1228849).\n- SUNRPC: add a missing rpc_stat for TCP TLS (git-fixes).\n- sunrpc: add a struct rpc_stats arg to rpc_create_args (git-fixes).\n- SUNRPC: Fix a race to wake a sync task (git-fixes).\n- swiotlb: do not set total_used to 0 in swiotlb_create_debugfs_files() (git-fixes).\n- swiotlb: fix swiotlb_bounce() to do partial sync's correctly (git-fixes).\n- syscalls: fix compat_sys_io_pgetevents_time64 usage (git-fixes).\n- thermal: bcm2835: Convert to platform remove callback returning void (stable-fixes).\n- thermal/drivers/broadcom: Fix race between removal and clock disable (git-fixes).\n- thunderbolt: Mark XDomain as unplugged when router is removed (stable-fixes).\n- tools/perf: Fix perf bench epoll to enable the run when some CPU's are offline (bsc#1227747).\n- tools/perf: Fix perf bench futex to enable the run when some CPU's are offline (bsc#1227747).\n- tools/perf: Fix timing issue with parallel threads in perf bench wake-up-parallel (bsc#1227747).\n- tools/resolve_btfids: fix build with musl libc (git-fixes).\n- tools/resolve_btfids: Fix comparison of distinct pointer types warning in resolve_btfids (git-fixes).\n- tools/resolve_btfids: Fix cross-compilation to non-host endianness (git-fixes).\n- tools/resolve_btfids: Refactor set sorting with types from btf_ids.h (git-fixes).\n- trace/pid_list: Change gfp flags in pid_list_fill_irq() (git-fixes).\n- tracing: Return from tracing_buffers_read() if the file has been closed (bsc#1229136 git-fixes).\n- tty: atmel_serial: use the correct RTS flag (git-fixes).\n- tty: serial: fsl_lpuart: mark last busy before uart_add_one_port (git-fixes).\n- usb: cdnsp: fix for Link TRB with TC (git-fixes).\n- usb: cdnsp: fix incorrect index in cdnsp_get_hw_deq function (git-fixes).\n- usb: core: sysfs: Unmerge @usb3_hardware_lpm_attr_group in remove_power_attributes() (git-fixes).\n- usb: dwc3: core: Skip setting event buffers for host only controllers (stable-fixes).\n- usb: dwc3: omap: add missing depopulate in probe error path (git-fixes).\n- usb: dwc3: st: add missing depopulate in probe error path (git-fixes).\n- usb: dwc3: st: fix probed platform device ref count on probe error path (git-fixes).\n- usb: gadget: core: Check for unset descriptor (git-fixes).\n- usb: gadget: fsl: Increase size of name buffer for endpoints (stable-fixes).\n- usb: gadget: u_audio: Check return codes from usb_ep_enable and config_ep_by_speed (git-fixes).\n- usb: gadget: u_serial: Set start_delayed during suspend (git-fixes).\n- usb: gadget: uvc: cleanup request when not in correct state (stable-fixes).\n- USB: serial: debug: do not echo input by default (stable-fixes).\n- usb: typec: fsa4480: add support for Audio Accessory Mode (git-fixes).\n- usb: typec: fsa4480: Add support to swap SBU orientation (git-fixes).\n- usb: typec: fsa4480: Check if the chip is really there (git-fixes).\n- usb: typec: fsa4480: Relax CHIP_ID check (git-fixes).\n- usb: typec: fsa4480: rework mux \u0026 switch setup to handle more states (git-fixes).\n- usb: vhci-hcd: Do not drop references before new references are gained (stable-fixes).\n- vfio/pci: fix potential memory leak in vfio_intx_enable() (git-fixes).\n- vhost-scsi: Handle vhost_vq_work_queue failures for events (git-fixes).\n- vhost-vdpa: switch to use vmf_insert_pfn() in the fault handler (git-fixes).\n- vhost: Release worker mutex during flushes (git-fixes).\n- vhost: Use virtqueue mutex for swapping worker (git-fixes).\n- vhost/vsock: always initialize seqpacket_allow (git-fixes).\n- virt: guest_memfd: fix reference leak on hwpoisoned page (git-fixes).\n- virtio_net: use u64_stats_t infra to avoid data-races (git-fixes).\n- virtio-crypto: handle config changed by work queue (git-fixes).\n- virtio: reenable config if freezing device failed (git-fixes).\n- virtiofs: forbid newlines in tags (bsc#1229940).\n- wifi: ath12k: fix memory leak in ath12k_dp_rx_peer_frag_setup() (stable-fixes).\n- wifi: ath12k: fix soft lockup on suspend (git-fixes).\n- wifi: brcmfmac: cfg80211: Handle SSID based pmksa deletion (git-fixes).\n- wifi: cfg80211: fix reporting failed MLO links status with cfg80211_connect_done (git-fixes).\n- wifi: iwlwifi: fw: fix wgds rev 3 exact size (git-fixes).\n- wifi: mac80211: use monitor sdata with driver only if desired (git-fixes).\n- wifi: mwifiex: duplicate static structs used in driver instances (git-fixes).\n- wifi: nl80211: disallow setting special AP channel widths (stable-fixes).\n- wifi: nl80211: do not give key data to userspace (stable-fixes).\n- wifi: rtw88: usb: Fix disconnection after beacon loss (stable-fixes).\n- wifi: wfx: repair open network AP mode (git-fixes).\n- workqueue: Improve scalability of workqueue watchdog touch (bsc#1193454).\n- workqueue: wq_watchdog_touch is always called with valid CPU (bsc#1193454).\n- x86/asm: Use %c/%n instead of %P operand modifier in asm templates (git-fixes).\n- x86/entry/64: Remove obsolete comment on tracing vs. SYSRET (git-fixes).\n- x86/mm: Fix pti_clone_entry_text() for i386 (git-fixes).\n- x86/mm: Fix pti_clone_pgtable() alignment assumption (git-fixes).\n- x86/mtrr: Check if fixed MTRRs exist before saving them (git-fixes).\n- x86/numa: Fix SRAT lookup of CFMWS ranges with numa_fill_memblks() (git-fixes).\n- x86/numa: Fix the address overlap check in numa_fill_memblks() (git-fixes).\n- x86/numa: Fix the sort compare func used in numa_fill_memblks() (git-fixes).\n- x86/numa: Introduce numa_fill_memblks() (git-fixes).\n- x86/pci: Skip early E820 check for ECAM region (git-fixes).\n- x86/xen: Convert comma to semicolon (git-fixes).\n- xfs: allow cross-linking special files without project quota (git-fixes).\n- xfs: allow symlinks with short remote targets (bsc#1229160).\n- xfs: allow unlinked symlinks and dirs with zero size (git-fixes).\n- xfs: attr forks require attr, not attr2 (git-fixes).\n- xfs: convert comma to semicolon (git-fixes).\n- xfs: do not use current-\u003ejournal_info (git-fixes).\n- xfs: Fix missing interval for missing_owner in xfs fsmap (git-fixes).\n- xfs: Fix the owner setting issue for rmap query in xfs fsmap (git-fixes).\n- xfs: fix unlink vs cluster buffer instantiation race (git-fixes).\n- xfs: honor init_xattrs in xfs_init_new_inode for !ATTR fs (git-fixes).\n- xfs: journal geometry is not properly bounds checked (git-fixes).\n- xfs: match lock mode in xfs_buffered_write_iomap_begin() (git-fixes).\n- xfs: require XFS_SB_FEAT_INCOMPAT_LOG_XATTRS for attr log intent item recovery (git-fixes).\n- xfs: upgrade the extent counters in xfs_reflink_end_cow_extent later (git-fixes).\n- xfs: use consistent uid/gid when grabbing dquots for inodes (git-fixes).\n- xfs: use XFS_BUF_DADDR_NULL for daddrs in getfsmap code (git-fixes).\n- xhci: Fix Panther point NULL pointer deref at full-speed re-enumeration (git-fixes).\n- xprtrdma: Fix rpcrdma_reqs_reset() (git-fixes).\n","status":"published","published":"2024-09-10T14:10:24Z","modified":"2026-02-04T02:36:48.443793Z","updated_at":"2026-11-02T15:53:55.639015Z"},{"id":"SUSE-SU-2024:3209-1","title":"Security update for the Linux Kernel","description":"\nThe SUSE Linux Enterprise 15 SP5 RT kernel was updated to receive various security bugfixes.\n\nThe following security bugs were fixed:\n\n- CVE-2024-44947: Initialize beyond-EOF page contents before setting uptodate (bsc#1229454).\n- CVE-2024-36936: Touch soft lockup during memory accept (bsc#1225773).\n- CVE-2022-48706: Do proper cleanup if IFCVF init fails (bsc#1225524).\n- CVE-2024-43883: Do not drop references before new references are gained (bsc#1229707).\n- CVE-2024-41062: Sync sock recv cb and release (bsc#1228576).\n- CVE-2024-43861: Fix memory leak for not ip packets (bsc#1229500).\n- CVE-2023-52489: Fix race in accessing memory_section-\u003eusage (bsc#1221326).\n- CVE-2024-43893: Check uartclk for zero to avoid divide by zero (bsc#1229759).\n- CVE-2024-43821: Fix a possible null pointer dereference (bsc#1229315).\n- CVE-2024-43900: Avoid use-after-free in load_firmware_cb() (bsc#1229756).\n- CVE-2024-44938: Fix shift-out-of-bounds in dbDiscardAG (bsc#1229792).\n- CVE-2024-44939: Fix null ptr deref in dtInsertEntry (bsc#1229820).\n- CVE-2024-41087: Fix double free on error (bsc#1228466).\n- CVE-2024-42277: Avoid NULL deref in sprd_iommu_hw_en (bsc#1229409).\n- CVE-2024-43902: Add null checker before passing variables (bsc#1229767).\n- CVE-2024-43904: Add null checks for 'stream' and 'plane' before dereferencing (bsc#1229768)\n- CVE-2024-43880: Put back removed metod in struct objagg_ops (bsc#1229481).\n- CVE-2024-43884: Add error handling to pair_device() (bsc#1229739)\n- CVE-2024-43899: Fix null pointer deref in dcn20_resource.c (bsc#1229754).\n- CVE-2022-48920: Get rid of warning on transaction commit when using flushoncommit (bsc#1229658).\n- CVE-2023-52906: Fix warning during failed attribute validation (bsc#1229527).\n- CVE-2024-43882: Fixed ToCToU between perm check and set-uid/gid usage. (bsc#1229503)\n- CVE-2024-43866: Always drain health in shutdown callback (bsc#1229495).\n- CVE-2024-26812: struct virqfd kABI workaround (bsc#1222808).\n- CVE-2022-48912: Fix use-after-free in __nf_register_net_hook() (bsc#1229641)\n- CVE-2024-27010: Fix mirred deadlock on device recursion (bsc#1223720).\n- CVE-2022-48906: Correctly set DATA_FIN timeout when number of retransmits is large (bsc#1229605)\n- CVE-2024-42155: Wipe copies of protected- and secure-keys (bsc#1228733).\n- CVE-2024-42156: Wipe copies of clear-key structures on failure (bsc#1228722).\n- CVE-2023-52899: Add exception protection processing for vd in axi_chan_handle_err function (bsc#1229569).\n- CVE-2024-42158: Use kfree_sensitive() to fix Coccinelle warnings (bsc#1228720).\n- CVE-2024-26631: Fix data-race in ipv6_mc_down / mld_ifc_work (bsc#1221630).\n- CVE-2024-43873: Always initialize seqpacket_allow (bsc#1229488)\n- CVE-2024-40905: Fix possible race in __fib6_drop_pcpu_from() (bsc#1227761)\n- CVE-2024-39489: Fix memleak in seg6_hmac_init_algo (bsc#1227623)\n- CVE-2021-47106: Fix use-after-free in nft_set_catchall_destroy() (bsc#1220962)\n- CVE-2021-47517: Fix panic when interrupt coaleceing is set via ethtool (bsc#1225428).\n- CVE-2024-36489: Fix missing memory barrier in tls_init (bsc#1226874)\n- CVE-2024-41020: Fix fcntl/close race recovery compat path (bsc#1228427).\n- CVE-2024-27079: Fix NULL domain on device release (bsc#1223742).\n- CVE-2024-35897: Discard table flag update with pending basechain deletion (bsc#1224510).\n- CVE-2024-27403: Restore const specifier in flow_offload_route_init() (bsc#1224415).\n- CVE-2024-27011: Fix memleak in map from abort path (bsc#1223803).\n- CVE-2024-43819: Reject memory region operations for ucontrol VMs (bsc#1229290).\n- CVE-2024-26668: Reject configurations that cause integer overflow (bsc#1222335).\n- CVE-2024-26835: Set dormant flag on hook register failure (bsc#1222967).\n- CVE-2024-26808: Handle NETDEV_UNREGISTER for inet/ingress basechain (bsc#1222634).\n- CVE-2024-27016: Validate pppoe header (bsc#1223807).\n- CVE-2024-35945: Prevent nullptr exceptions on ISR (bsc#1224639).\n- CVE-2023-52581: Fix memleak when more than 255 elements expired (bsc#1220877).\n- CVE-2024-36013: Fix slab-use-after-free in l2cap_connect() (bsc#1225578).\n- CVE-2024-43837: Fix updating attached freplace prog in prog_array map (bsc#1229297).\n- CVE-2024-42291: Add a per-VF limit on number of FDIR filters (bsc#1229374).\n- CVE-2024-42268: Fix missing lock on sync reset reload (bsc#1229391).\n- CVE-2024-43834: Fix invalid wait context of page_pool_destroy() (bsc#1229314)\n- CVE-2024-36286: Acquire rcu_read_lock() in instance_destroy_rcu() (bsc#1226801)\n- CVE-2024-26851: Add protection for bmp length out of range (bsc#1223074)\n- CVE-2024-42157: Wipe sensitive data on failure (bsc#1228727).\n- CVE-2024-26677: Blacklist e7870cf13d20 (' Fix delayed ACKs to not set the reference serial number') (bsc#1222387)\n- CVE-2024-36009: Blacklist 467324bcfe1a ('ax25: Fix netdev refcount issue') (bsc#1224542)\n- CVE-2023-52859: Fix use-after-free when register pmu fails (bsc#1225582).\n- CVE-2024-42280: Fix a use after free in hfcmulti_tx() (bsc#1229388)\n- CVE-2024-42284: Return non-zero value from tipc_udp_addr2str() on error (bsc#1229382)\n- CVE-2024-42283: Initialize all fields in dumped nexthops (bsc#1229383)\n- CVE-2024-42312: Always initialize i_uid/i_gid (bsc#1229357)\n- CVE-2024-43854: Initialize integrity buffer to zero before writing it to media (bsc#1229345)\n- CVE-2024-42322: Properly dereference pe in ip_vs_add_service (bsc#1229347)\n- CVE-2024-42301: Fix the array out-of-bounds risk (bsc#1229407).\n- CVE-2024-42318: Do not lose track of restrictions on cred_transfer (bsc#1229351).\n- CVE-2024-26669: Fix chain template offload (bsc#1222350).\n- CVE-2023-52889: Fix null pointer deref when receiving skb during sock creation (bsc#1229287).\n- CVE-2022-48645: Move enetc_set_psfp() out of the common enetc_set_features() (bsc#1223508).\n- CVE-2024-41007: Use signed arithmetic in tcp_rtx_probe0_timed_out() (bsc#1227863).\n- CVE-2024-36933: Use correct mac_offset to unwind gso skb in nsh_gso_segment() (bsc#1225832).\n- CVE-2024-42295: Handle inconsistent state in nilfs_btnode_create_block() (bsc#1229370).\n- CVE-2024-42319: Move devm_mbox_controller_register() after devm_pm_runtime_enable() (bsc#1229350).\n- CVE-2024-43860: Skip over memory region when node value is NULL (bsc#1229319).\n- CVE-2024-43831: Handle invalid decoder vsi (bsc#1229309).\n- CVE-2024-43849: Protect locator_addr with the main mutex (bsc#1229307).\n- CVE-2024-43841: Do not use strlen() in const context (bsc#1229304).\n- CVE-2024-43839: Adjust 'name' buf size of bna_tcb and bna_ccb structures (bsc#1229301).\n- CVE-2024-41088: Fix infinite loop when xmit fails (bsc#1228469).\n- CVE-2024-42281: Fix a segment issue when downgrading gso_size (bsc#1229386).\n- CVE-2024-42271: Fixed a use after free in iucv_sock_close(). (bsc#1229400)\n- CVE-2024-41080: Fix possible deadlock in io_register_iowq_max_workers() (bsc#1228616).\n- CVE-2024-42246: Remap EPERM in case of connection failure in xs_tcp_setup_socket (bsc#1228989).\n- CVE-2024-42232: Fixed a race between delayed_work() and ceph_monc_stop(). (bsc#1228959)\n- CVE-2024-26735: Fix possible use-after-free and null-ptr-deref (bsc#1222372).\n- CVE-2024-42106: Initialize pad field in struct inet_diag_req_v2 (bsc#1228493).\n- CVE-2024-38662: Cover verifier checks for mutating sockmap/sockhash (bsc#1226885).\n- CVE-2024-42110: Move ntb_netdev_rx_handler() to call netif_rx() from __netif_rx() (bsc#1228501).\n- CVE-2024-42247: Avoid unaligned 64-bit memory accesses (bsc#1228988).\n- CVE-2022-48865: Fix kernel panic when enabling bearer (bsc#1228065).\n- CVE-2023-52498: Fix possible deadlocks in core system-wide PM code (bsc#1221269).\n- CVE-2024-41068: Fix sclp_init() cleanup on failure (bsc#1228579).\n- CVE-2022-48808: Fix panic when DSA master device unbinds on shutdown (bsc#1227958).\n- CVE-2024-42095: Fix Errata i2310 with RX FIFO level check (bsc#1228446).\n- CVE-2024-40978: Fix crash while reading debugfs attribute (bsc#1227929).\n- CVE-2024-42107: Do not process extts if PTP is disabled (bsc#1228494).\n- CVE-2024-42139: Fix improper extts handling (bsc#1228503).\n- CVE-2024-42148: Fix multiple UBSAN array-index-out-of-bounds (bsc#1228487).\n- CVE-2024-42142: E-switch, Create ingress ACL when needed (bsc#1228491).\n- CVE-2024-42162: Account for stopped queues when reading NIC stats (bsc#1228706).\n- CVE-2024-42082: Remove WARN() from __xdp_reg_mem_model() (bsc#1228482).\n- CVE-2024-41042: Prefer nft_chain_validate (bsc#1228526).\n- CVE-2023-3610: Fixed use-after-free vulnerability in nf_tables can be exploited to achieve local privilege escalation (bsc#1213580).\n- CVE-2024-42228: Using uninitialized value *size when calling amdgpu_vce_cs_reloc (bsc#1228667).\n- CVE-2024-40995: Fix possible infinite loop in tcf_idr_check_alloc() (bsc#1227830).\n- CVE-2024-38602: Merge repeat codes in ax25_dev_device_down() (bsc#1226613).\n- CVE-2024-38554: Fix reference count leak issue of net_device (bsc#1226742).\n- CVE-2024-36929: Reject skb_copy(_expand) for fraglist GSO skbs (bsc#1225814).\n- CVE-2024-41009: Fix overrunning reservations in ringbuf (bsc#1228020).\n- CVE-2024-27024: Fix WARNING in rds_conn_connect_if_down (bsc#1223777).\n\nThe following non-security bugs were fixed:\n\n- ACPI: bus: Indicate support for IRQ ResourceSource thru _OSC (git-fixes).\n- ACPI: bus: Indicate support for the Generic Event Device thru _OSC (git-fixes).\n- ACPI: bus: Rework system-level device notification handling (git-fixes).\n- ACPI: thermal: Drop nocrt parameter (git-fixes).\n- ACPI: x86: s2idle: Post-increment variables when getting constraints (git-fixes).\n- afs: Do not cross .backup mountpoint from backup volume (git-fixes).\n- ALSA: hda: Add HP MP9 G4 Retail System AMS to force connect list (stable-fixes).\n- ALSA: hda/hdmi: Yet more pin fix for HP EliteDesk 800 G4 (stable-fixes).\n- ALSA: hda/realtek: Add Framework Laptop 13 (Intel Core Ultra) to quirks (stable-fixes).\n- ALSA: hda/realtek: Fix noise from speakers on Lenovo IdeaPad 3 15IAU7 (git-fixes).\n- ALSA: line6: Fix racy access to midibuf (stable-fixes).\n- ALSA: timer: Relax start tick time check for slave timer elements (git-fixes).\n- ALSA: usb-audio: Add delay quirk for VIVO USB-C-XE710 HEADSET (stable-fixes).\n- ALSA: usb-audio: Re-add ScratchAmp quirk entries (git-fixes).\n- ALSA: usb-audio: Support Yamaha P-125 quirk entry (stable-fixes).\n- ALSA: usb: Fix UBSAN warning in parse_audio_unit() (stable-fixes).\n- arm64: ACPI: NUMA: initialize all values of acpi_early_node_map to (git-fixes)\n- arm64: ACPI: NUMA: initialize all values of acpi_early_node_map to (git-fixes)\n- arm64: Add Neoverse-V2 part (git-fixes)\n- arm64: armv8_deprecated: Fix warning in isndep cpuhp starting process (git-fixes)\n- arm64: armv8_deprecated: Fix warning in isndep cpuhp starting process (git-fixes)\n- arm64: barrier: Restore spec_bar() macro (git-fixes)\n- arm64: cpufeature: Add missing .field_width for GIC system registers (git-fixes)\n- arm64: cpufeature: Fix the visibility of compat hwcaps (git-fixes)\n- arm64: cpufeature: Force HWCAP to be based on the sysreg visible to (git-fixes)\n- arm64: cputype: Add Cortex-A720 definitions (git-fixes)\n- arm64: cputype: Add Cortex-A725 definitions (git-fixes)\n- arm64: cputype: Add Cortex-X1C definitions (git-fixes)\n- arm64: cputype: Add Cortex-X3 definitions (git-fixes)\n- arm64: cputype: Add Cortex-X4 definitions (git-fixes)\n- arm64: cputype: Add Cortex-X925 definitions (git-fixes)\n- arm64: cputype: Add Neoverse-V3 definitions (git-fixes)\n- arm64: dts: rockchip: Increase VOP clk rate on RK3328 (git-fixes)\n- arm64: dts: rockchip: Increase VOP clk rate on RK3328 (git-fixes)\n- arm64: errata: Expand speculative SSBS workaround (again) (git-fixes)\n- arm64: errata: Expand speculative SSBS workaround (git-fixes)\n- arm64: errata: Unify speculative SSBS errata logic (git-fixes) Also update default configuration.\n- arm64: Fix KASAN random tag seed initialization (git-fixes)\n- arm64: Fix KASAN random tag seed initialization (git-fixes)\n- ASoC: codecs: wcd938x-sdw: Correct Soundwire ports mask (git-fixes).\n- ASoC: codecs: wsa881x: Correct Soundwire ports mask (git-fixes).\n- ASoC: meson: axg-fifo: fix irq scheduling issue with PREEMPT_RT (git-fixes).\n- async: Introduce async_schedule_dev_nocall() (bsc#1221269).\n- async: Split async_schedule_node_domain() (bsc#1221269).\n- Bluetooth: Fix usage of __hci_cmd_sync_status (git-fixes).\n- Bluetooth: hci_core: Fix not handling hibernation actions (git-fixes).\n- Bluetooth: l2cap: always unlock channel in l2cap_conless_channel() (git-fixes).\n- Bluetooth: L2CAP: Fix deadlock (git-fixes).\n- bpf: Fix a kernel verifier crash in stacksafe() (bsc#1225903).\n- bpf: kprobe: remove unused declaring of bpf_kprobe_override (git-fixes).\n- btrfs: fix leak of qgroup extent records after transaction abort (git-fixes).\n- btrfs: make btrfs_destroy_delayed_refs() return void (git-fixes).\n- btrfs: remove unnecessary prototype declarations at disk-io.c (git-fixes).\n- btrfs: sysfs: update fs features directory asynchronously (bsc#1226168).\n- cachefiles: propagate errors from vfs_getxattr() to avoid infinite loop (bsc#1229418).\n- ceph: issue a cap release immediately if no cap exists (bsc#1225162).\n- ceph: periodically flush the cap releases (bsc#1225162).\n- cpu/SMT: Enable SMT only if a core is online (bsc#1214285 bsc#1205462 ltc#200161 ltc#200588 git-fixes).\n- cpuidle, ACPI: Evaluate LPI arch_flags for broadcast timer (git-fixes).\n- docs: KVM: Fix register ID of SPSR_FIQ (git-fixes).\n- drm: add missing MODULE_DESCRIPTION() macros (stable-fixes).\n- drm: panel-orientation-quirks: Add labels for both Valve Steam Deck revisions (stable-fixes).\n- drm: panel-orientation-quirks: Add quirk for Aya Neo KUN (stable-fixes).\n- drm: panel-orientation-quirks: Add quirk for Lenovo Yoga Tab 3 X90F (stable-fixes).\n- drm: panel-orientation-quirks: Add quirk for Nanote UMPC-01 (stable-fixes).\n- drm: panel-orientation-quirks: Add quirk for OrangePi Neo (stable-fixes).\n- drm/amd/amdgpu/imu_v11_0: Increase buffer size to ensure all possible values can be stored (stable-fixes).\n- drm/amd/display: Add NULL check for 'afb' before dereferencing in amdgpu_dm_plane_handle_cursor_update (stable-fixes).\n- drm/amd/display: avoid using null object of framebuffer (git-fixes).\n- drm/amd/display: Fix \u0026\u0026 vs || typos (git-fixes).\n- drm/amd/display: Skip Recompute DSC Params if no Stream on Link (stable-fixes).\n- drm/amd/display: Validate hw_points_num before using it (stable-fixes).\n- drm/amd/pm: Fix the null pointer dereference for vega10_hwmgr (stable-fixes).\n- drm/amdgpu: Actually check flags for all context ops (stable-fixes).\n- drm/amdgpu: Add lock around VF RLCG interface (stable-fixes).\n- drm/amdgpu: fix dereference null return value for the function amdgpu_vm_pt_parent (stable-fixes).\n- drm/amdgpu: Fix the null pointer dereference to ras_manager (stable-fixes).\n- drm/amdgpu: Validate TA binary size (stable-fixes).\n- drm/amdgpu/jpeg2: properly set atomics vmid field (stable-fixes).\n- drm/amdgpu/pm: Fix the null pointer dereference for smu7 (stable-fixes).\n- drm/amdgpu/pm: Fix the null pointer dereference in apply_state_adjust_rules (stable-fixes).\n- drm/amdgpu/pm: Fix the param type of set_power_profile_mode (stable-fixes).\n- drm/bridge: analogix_dp: properly handle zero sized AUX transactions (stable-fixes).\n- drm/bridge: tc358768: Attempt to fix DSI horizontal timings (stable-fixes).\n- drm/client: fix null pointer dereference in drm_client_modeset_probe (git-fixes).\n- drm/dp_mst: Skip CSN if topology probing is not done yet (stable-fixes).\n- drm/lima: set gp bus_stop bit before hard reset (stable-fixes).\n- drm/msm/dp: reset the link phy params before link training (git-fixes).\n- drm/msm/dpu: cleanup FB if dpu_format_populate_layout fails (git-fixes).\n- drm/msm/dpu: do not play tricks with debug macros (git-fixes).\n- drm/tegra: Zero-initialize iosys_map (stable-fixes).\n- exfat: fix inode-\u003ei_blocks for non-512 byte sector size device (git-fixes).\n- exfat: fix potential deadlock on __exfat_get_dentry_set (git-fixes).\n- exfat: redefine DIR_DELETED as the bad cluster number (git-fixes).\n- exfat: support dynamic allocate bh for exfat_entry_set_cache (git-fixes).\n- fs/netfs/fscache_cookie: add missing 'n_accesses' check (bsc#1229453).\n- fuse: Initialize beyond-EOF page contents before setting uptodate (bsc#1229454).\n- genirq: Add might_sleep() to disable_irq() (git-fixes).\n- genirq: Always limit the affinity to online CPUs (git-fixes).\n- genirq: Do not return error on missing optional irq_request_resources() (git-fixes).\n- genirq: Take the proposed affinity at face value if force==true (git-fixes).\n- genirq/cpuhotplug, x86/vector: Prevent vector leak during CPU offline (git-fixes).\n- genirq/generic_chip: Make irq_remove_generic_chip() irqdomain aware (git-fixes).\n- genirq/ipi: Fix NULL pointer deref in irq_data_get_affinity_mask() (git-fixes).\n- genirq/irqdesc: Do not try to remove non-existing sysfs files (git-fixes).\n- genirq/matrix: Exclude managed interrupts in irq_matrix_allocated() (git-fixes).\n- genirq/msi: Shutdown managed interrupts with unsatifiable affinities (git-fixes).\n- gss_krb5: Fix the error handling path for crypto_sync_skcipher_setkey (git-fixes).\n- hfs: fix to initialize fields of hfs_inode_info after hfs_alloc_inode() (git-fixes).\n- i2c: smbus: Improve handling of stuck alerts (git-fixes).\n- i2c: smbus: Send alert notifications to all devices if source not found (git-fixes).\n- iommu/amd: Convert comma to semicolon (git-fixes).\n- ip6_tunnel: Fix broken GRO (bsc#1229444).\n- ipv6: sr: fix incorrect unregister order (git-fixes).\n- irqdomain: Drop bogus fwspec-mapping error handling (git-fixes).\n- irqdomain: Fix association race (git-fixes).\n- irqdomain: Fix disassociation race (git-fixes).\n- irqdomain: Fix domain registration race (git-fixes).\n- irqdomain: Fix mapping-creation race (git-fixes).\n- irqdomain: Fixed unbalanced fwnode get and put (git-fixes).\n- irqdomain: Look for existing mapping only once (git-fixes).\n- irqdomain: Refactor __irq_domain_alloc_irqs() (git-fixes).\n- irqdomain: Report irq number for NOMAP domains (git-fixes).\n- kprobes: Fix to check symbol prefixes correctly (git-fixes).\n- lockd: move from strlcpy with unused retval to strscpy (git-fixes).\n- memcg: protect concurrent access to mem_cgroup_idr (git-fixes).\n- mm, kmsan: fix infinite recursion due to RCU critical section (git-fixes).\n- mm: prevent derefencing NULL ptr in pfn_section_valid() (git-fixes).\n- mmc: dw_mmc: allow biu and ciu clocks to defer (git-fixes).\n- mmc: mmc_test: Fix NULL dereference on allocation failure (git-fixes).\n- net: ks8851: Fix another TX stall caused by wrong ISR flag handling (git-fixes).\n- net: ks8851: Fix deadlock with the SPI chip variant (git-fixes).\n- net: ks8851: Fix potential TX stall after interface reopen (git-fixes).\n- net: ks8851: Fix TX stall caused by TX buffer overrun (gix-fixes).\n- net: mana: Add support for page sizes other than 4KB on ARM64 (jsc#PED-8491 bsc#1226530).\n- net: mana: Fix doorbell out of order violation and avoid unnecessary doorbell rings (bsc#1229154).\n- net: mana: Fix race of mana_hwc_post_rx_wqe and new hwc response (git-fixes).\n- net: mana: Fix RX buf alloc_size alignment and atomic op panic (bsc#1229086).\n- net: remove two BUG() from skb_checksum_help() (bsc#1229312).\n- net: usb: qmi_wwan: fix memory leak for not ip packets (git-fixes).\n- net/rds: fix possible cp null dereference (git-fixes).\n- net/sched: initialize noop_qdisc owner (git-fixes).\n- nfc: pn533: Add poll mod list filling check (git-fixes).\n- nfs: expose /proc/net/sunrpc/nfs in net namespaces (git-fixes).\n- nfs: make the rpc_stat per net namespace (git-fixes).\n- NFSD: add posix ACLs to struct nfsd_attrs (git-fixes).\n- NFSD: add security label to struct nfsd_attrs (git-fixes).\n- NFSD: fix regression with setting ACLs (git-fixes).\n- NFSD: Fix strncpy() fortify warning (git-fixes).\n- NFSD: Increase NFSD_MAX_OPS_PER_COMPOUND (git-fixes).\n- NFSD: introduce struct nfsd_attrs (git-fixes).\n- NFSD: move from strlcpy with unused retval to strscpy (git-fixes).\n- NFSD: Optimize DRC bucket pruning (git-fixes).\n- nfsd: return error if nfs4_setacl fails (git-fixes).\n- NFSD: set attributes when creating symlinks (git-fixes).\n- nfsd: use locks_inode_context helper (git-fixes).\n- nilfs2: Remove check for PageError (git-fixes).\n- nvme_core: scan namespaces asynchronously (bsc#1224105).\n- ocfs2: use coarse time for new created files (git-fixes).\n- padata: Fix possible divide-by-0 panic in padata_mt_helper() (git-fixes).\n- perf/smmuv3: Enable HiSilicon Erratum 162001900 quirk for HIP08/09 (git-fixes).\n- platform/x86/amd/hsmp: Add support for ACPI based probing (jsc#PED-8779).\n- platform/x86/amd/hsmp: Cache pci_dev in struct hsmp_socket (jsc#PED-8779).\n- platform/x86/amd/hsmp: Change devm_kzalloc() to devm_kcalloc() (jsc#PED-8779).\n- platform/x86/amd/hsmp: Check HSMP support on AMD family of processors (jsc#PED-8779).\n- platform/x86/amd/hsmp: Check num_sockets against MAX_AMD_SOCKETS (jsc#PED-8779).\n- platform/x86/amd/hsmp: Create static func to handle platdev (jsc#PED-8779).\n- platform/x86/amd/hsmp: Define a struct to hold mailbox regs (jsc#PED-8779).\n- platform/x86/amd/hsmp: Move dev from platdev to hsmp_socket (jsc#PED-8779).\n- platform/x86/amd/hsmp: Move hsmp_test to probe (jsc#PED-8779).\n- platform/x86/amd/hsmp: Non-ACPI support for AMD F1A_M00~0Fh (jsc#PED-8779).\n- platform/x86/amd/hsmp: Remove extra parenthesis and add a space (jsc#PED-8779).\n- platform/x86/amd/hsmp: Restructure sysfs group creation (jsc#PED-8779).\n- platform/x86/amd/hsmp: switch to use device_add_groups() (jsc#PED-8779).\n- power: supply: axp288_charger: Fix constant_charge_voltage writes (git-fixes).\n- power: supply: axp288_charger: Round constant_charge_voltage writes down (git-fixes).\n- powerpc: Fail build if using recordmcount with binutils v2.37 (bsc#1194869).\n- powerpc: Mark .opd section read-only (bsc#1194869).\n- powerpc: use generic version of arch_is_kernel_initmem_freed() (bsc#1194869).\n- powerpc: xor_vmx: Add '-mhard-float' to CFLAGS (bsc#1194869).\n- powerpc/64: Set _IO_BASE to POISON_POINTER_DELTA not 0 for CONFIG_PCI=n (bsc#1194869).\n- powerpc/io: Avoid clang null pointer arithmetic warnings (bsc#1194869).\n- powerpc/kexec_file: fix cpus node update to FDT (bsc#1194869).\n- powerpc/kexec: make the update_cpus_node() function public (bsc#1194869).\n- powerpc/kexec: split CONFIG_KEXEC_FILE and CONFIG_CRASH_DUMP (bsc#1194869).\n- powerpc/pseries: Add failure related checks for h_get_mpp and h_get_ppp (bsc#1194869).\n- powerpc/pseries: Whitelist dtl slub object for copying to userspace (bsc#1194869).\n- powerpc/radix: Move some functions into #ifdef CONFIG_KVM_BOOK3S_HV_POSSIBLE (bsc#1194869).\n- powerpc/topology: Check if a core is online (bsc#1214285 bsc#1205462 ltc#200161 ltc#200588 git-fixes).\n- powerpc/xmon: Check cpu id in commands 'c#', 'dp#' and 'dx#' (bsc#1194869).\n- RDMA/mana_ib: Use virtual address in dma regions for MRs (git-fixes).\n- RDMA/rxe: Fix incomplete state save in rxe_requester (git-fixes)\n- RDMA/rxe: Fix rxe_modify_srq (git-fixes)\n- RDMA/rxe: Handle zero length rdma (git-fixes)\n- RDMA/rxe: Move work queue code to subroutines (git-fixes)\n- s390/cpacf: get rid of register asm (git-fixes bsc#1227079 bsc#1229187).\n- s390/cpacf: Make use of invalid opcode produce a link error (git-fixes bsc#1227079).\n- s390/cpacf: Split and rework cpacf query functions (git-fixes bsc#1229187).\n- s390/dasd: fix error checks in dasd_copy_pair_store() (git-fixes bsc#1229190).\n- s390/dasd: fix error recovery leading to data corruption on ESE devices (git-fixes bsc#1229573).\n- s390/sclp: Prevent release of buffer in I/O (git-fixes bsc#1229572).\n- s390/uv: Panic for set and remove shared access UVC errors (git-fixes bsc#1229188).\n- spi: spi-fsl-lpspi: Fix scldiv calculation (git-fixes).\n- sunrpc: add a struct rpc_stats arg to rpc_create_args (git-fixes).\n- SUNRPC: Fix a race to wake a sync task (git-fixes).\n- swiotlb: fix swiotlb_bounce() to do partial sync's correctly (git-fixes).\n- syscalls: fix compat_sys_io_pgetevents_time64 usage (git-fixes).\n- tracing: Return from tracing_buffers_read() if the file has been closed (bsc#1229136 git-fixes).\n- ubifs: add check for crypto_shash_tfm_digest (git-fixes).\n- ubifs: dbg_orphan_check: Fix missed key type checking (git-fixes).\n- ubifs: Fix adding orphan entry twice for the same inode (git-fixes).\n- ubifs: Fix unattached xattr inode if powercut happens after deleting (git-fixes).\n- vfio/pci: fix potential memory leak in vfio_intx_enable() (git-fixes).\n- wifi: iwlwifi: fw: fix wgds rev 3 exact size (git-fixes).\n- wifi: mwifiex: duplicate static structs used in driver instances (git-fixes).\n- x86/APM: drop the duplicate APM_MINOR_DEV macro (git-fixes).\n- x86/insn: Fix PUSH instruction in x86 instruction decoder opcode map (git-fixes).\n- x86/mm: Fix pti_clone_entry_text() for i386 (git-fixes).\n- x86/mtrr: Check if fixed MTRRs exist before saving them (git-fixes).\n- x86/pm: Work around false positive kmemleak report in msr_build_context() (git-fixes).\n- xfs: Fix missing interval for missing_owner in xfs fsmap (git-fixes).\n- xfs: Fix the owner setting issue for rmap query in xfs fsmap (git-fixes).\n- xfs: use XFS_BUF_DADDR_NULL for daddrs in getfsmap code (git-fixes).\n- xhci: Fix Panther point NULL pointer deref at full-speed re-enumeration (git-fixes).\n- xprtrdma: Fix rpcrdma_reqs_reset() (git-fixes).\n","status":"published","published":"2024-09-11T15:39:03Z","modified":"2026-02-04T03:59:23.624917Z","updated_at":"2026-11-02T15:53:55.639015Z"},{"id":"SUSE-SU-2024:3383-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-2024-43911: wifi: mac80211: fix NULL dereference at band check in starting tx ba session (bsc#1229827).\n- CVE-2024-43899: drm/amd/display: Fix null pointer deref in dcn20_resource.c (bsc#1229754).\n- CVE-2024-43882: Fixed ToCToU between perm check and set-uid/gid usage. (bsc#1229503)\n- CVE-2024-43880: kabi: lib: objagg: Put back removed metod in struct objagg_ops (bsc#1229481).\n- CVE-2024-43866: net/mlx5: Always drain health in shutdown callback (bsc#1229495).\n- CVE-2024-43864: net/mlx5e: Fix CT entry update leaks of modify header context (bsc#1229496).\n- CVE-2024-43855: md: fix deadlock between mddev_suspend and flush bio (bsc#1229342).\n- CVE-2024-43854: block: initialize integrity buffer to zero before writing it to media (bsc#1229345)\n- CVE-2024-43850: soc: qcom: icc-bwmon: Fix refcount imbalance seen during bwmon_remove (bsc#1229316).\n- CVE-2024-43839: bna: adjust 'name' buf size of bna_tcb and bna_ccb structures (bsc#1229301).\n- CVE-2024-43837: bpf: Fix updating attached freplace prog in prog_array map (bsc#1229297).\n- CVE-2024-43834: xdp: fix invalid wait context of page_pool_destroy() (bsc#1229314)\n- CVE-2024-43831: media: mediatek: vcodec: Handle invalid decoder vsi (bsc#1229309).\n- CVE-2024-43821: scsi: lpfc: Fix a possible null pointer dereference (bsc#1229315).\n- CVE-2024-42322: ipvs: properly dereference pe in ip_vs_add_service (bsc#1229347)\n- CVE-2024-42318: landlock: Do not lose track of restrictions on cred_transfer (bsc#1229351).\n- CVE-2024-42316: mm/mglru: fix div-by-zero in vmpressure_calc_level() (bsc#1229353).\n- CVE-2024-42312: sysctl: always initialize i_uid/i_gid (bsc#1229357)\n- CVE-2024-42308: Update DRM patch reference (bsc#1229411)\n- CVE-2024-42301: dev/parport: fix the array out-of-bounds risk (bsc#1229407).\n- CVE-2024-42295: nilfs2: handle inconsistent state in nilfs_btnode_create_block() (bsc#1229370).\n- CVE-2024-42291: ice: Add a per-VF limit on number of FDIR filters (bsc#1229374).\n- CVE-2024-42290: irqchip/imx-irqsteer: Handle runtime power management correctly (bsc#1229379).\n- CVE-2024-42284: tipc: Return non-zero value from tipc_udp_addr2str() on error (bsc#1229382)\n- CVE-2024-42283: net: nexthop: Initialize all fields in dumped nexthops (bsc#1229383)\n- CVE-2024-42281: bpf: Fix a segment issue when downgrading gso_size (bsc#1229386).\n- CVE-2024-42277: iommu: sprd: Avoid NULL deref in sprd_iommu_hw_en (bsc#1229409).\n- CVE-2024-42270: netfilter: iptables: Fix null-ptr-deref in iptable_nat_table_init() (bsc#1229404).\n- CVE-2024-42269: netfilter: iptables: Fix potential null-ptr-deref in ip6table_nat_table_init() (bsc#1229402).\n- CVE-2024-42268: net/mlx5: Fix missing lock on sync reset reload (bsc#1229391).\n- CVE-2024-42247: wireguard: allowedips: avoid unaligned 64-bit memory accesses (bsc#1228988).\n- CVE-2024-42246: net, sunrpc: Remap EPERM in case of connection failure in xs_tcp_setup_socket (bsc#1228989).\n- CVE-2024-42245: Revert 'sched/fair: Make sure to try to detach at least one movable task' (bsc#1228978).\n- CVE-2024-42241: mm/shmem: disable PMD-sized page cache if needed (bsc#1228986).\n- CVE-2024-42224: net: dsa: mv88e6xxx: Correct check for empty list (bsc#1228723).\n- CVE-2024-42162: gve: Account for stopped queues when reading NIC stats (bsc#1228706).\n- CVE-2024-42161: bpf: avoid uninitialized value in BPF_CORE_READ_BITFIELD (bsc#1228756).\n- CVE-2024-42159: scsi: mpi3mr: fix sanitise num_phys (bsc#1228754).\n- CVE-2024-42158: s390/pkey: Use kfree_sensitive() to fix Coccinelle warnings (bsc#1228720).\n- CVE-2024-42157: s390/pkey: Wipe sensitive data on failure (bsc#1228727).\n- CVE-2024-42156: s390/pkey: Wipe copies of clear-key structures on failure (bsc#1228722).\n- CVE-2024-42155: s390/pkey: Wipe copies of protected- and secure-keys (bsc#1228733).\n- CVE-2024-42148: bnx2x: Fix multiple UBSAN array-index-out-of-bounds (bsc#1228487).\n- CVE-2024-42145: IB/core: Implement a limit on UMAD receive List (bsc#1228743).\n- CVE-2024-42142: net/mlx5: E-switch, Create ingress ACL when needed (bsc#1228491).\n- CVE-2024-42139: ice: Fix improper extts handling (bsc#1228503).\n- CVE-2024-42138: mlxsw: core_linecards: Fix double memory deallocation in case of invalid INI file (bsc#1228500).\n- CVE-2024-42124: scsi: qedf: Make qedf_execute_tmf() non-preemptible (bsc#1228705).\n- CVE-2024-42122: drm/amd/display: Add NULL pointer check for kzalloc (bsc#1228591).\n- CVE-2024-42113: net: txgbe: initialize num_q_vectors for MSI/INTx interrupts (bsc#1228568).\n- CVE-2024-42110: net: ntb_netdev: Move ntb_netdev_rx_handler() to call netif_rx() from __netif_rx() (bsc#1228501).\n- CVE-2024-42109: netfilter: nf_tables: unconditionally flush pending work before notifier (bsc#1228505).\n- CVE-2024-42107: ice: Do not process extts if PTP is disabled (bsc#1228494).\n- CVE-2024-42106: inet_diag: Initialize pad field in struct inet_diag_req_v2 (bsc#1228493).\n- CVE-2024-42096: x86: stop playing stack games in profile_pc() (bsc#1228633).\n- CVE-2024-42095: serial: 8250_omap: Fix Errata i2310 with RX FIFO level check (bsc#1228446).\n- CVE-2024-42093: net/dpaa2: Avoid explicit cpumask var allocation on stack (bsc#1228680).\n- CVE-2024-42082: xdp: Remove WARN() from __xdp_reg_mem_model() (bsc#1228482).\n- CVE-2024-42079: gfs2: Fix NULL pointer dereference in gfs2_log_flush (bsc#1228672).\n- CVE-2024-42073: mlxsw: spectrum_buffers: Fix memory corruptions on Spectrum-4 systems (bsc#1228457).\n- CVE-2024-42070: netfilter: nf_tables: fully validate NFT_DATA_VALUE on store to data registers (bsc#1228470).\n- CVE-2024-41084: cxl/region: Avoid null pointer dereference in region lookup (bsc#1228472).\n- CVE-2024-41081: ila: block BH in ila_output() (bsc#1228617).\n- CVE-2024-41080: io_uring: fix possible deadlock in io_register_iowq_max_workers() (bsc#1228616).\n- CVE-2024-41078: btrfs: qgroup: fix quota root leak after quota disable failure (bsc#1228655).\n- CVE-2024-41076: NFSv4: Fix memory leak in nfs4_set_security_label (bsc#1228649).\n- CVE-2024-41075: cachefiles: add consistency check for copen/cread (bsc#1228646).\n- CVE-2024-41074: cachefiles: Set object to close if ondemand_id \u003c 0 in copen (bsc#1228643).\n- CVE-2024-41070: KVM: PPC: Book3S HV: Prevent UAF in kvm_spapr_tce_attach_iommu_group() (bsc#1228581).\n- CVE-2024-41069: ASoC: topology: Fix route memory corruption (bsc#1228644).\n- CVE-2024-41068: s390/sclp: Fix sclp_init() cleanup on failure (bsc#1228579).\n- CVE-2024-41066: ibmvnic: add tx check to prevent skb leak (bsc#1228640).\n- CVE-2024-41064: powerpc/eeh: avoid possible crash when edev-\u003epdev changes (bsc#1228599).\n- CVE-2024-41062: bluetooth/l2cap: sync sock recv cb and release (bsc#1228576).\n- CVE-2024-41058: cachefiles: fix slab-use-after-free in fscache_withdraw_volume() (bsc#1228459).\n- CVE-2024-41057: cachefiles: fix slab-use-after-free in cachefiles_withdraw_cookie() (bsc#1228462).\n- CVE-2024-41051: cachefiles: wait for ondemand_object_worker to finish when dropping object (bsc#1228468).\n- CVE-2024-41050: cachefiles: cyclic allocation of msg_id to avoid reuse (bsc#1228499).\n- CVE-2024-41048: skmsg: Skip zero length skb in sk_msg_recvmsg (bsc#1228565).\n- CVE-2024-41044: ppp: reject claimed-as-LCP but actually malformed packets (bsc#1228530).\n- CVE-2024-41041: udp: Set SOCK_RCU_FREE earlier in udp_lib_get_port() (bsc#1228520).\n- CVE-2024-41040: net/sched: Fix UAF when resolving a clash (bsc#1228518).\n- CVE-2024-41036: net: ks8851: Fix deadlock with the SPI chip variant (bsc#1228496).\n- CVE-2024-41032: mm: vmalloc: check if a hash-index is in cpu_possible_mask (bsc#1228460).\n- CVE-2024-41020: filelock: Fix fcntl/close race recovery compat path (bsc#1228427).\n- CVE-2024-41015: ocfs2: add bounds checking to ocfs2_check_dir_entry() (bsc#1228409).\n- CVE-2024-41012: filelock: Remove locks reliably when fcntl/close race is detected (bsc#1228247).\n- CVE-2024-41010: bpf: Fix too early release of tcx_entry (bsc#1228021).\n- CVE-2024-41009: bpf: Fix overrunning reservations in ringbuf (bsc#1228020).\n- CVE-2024-41007: tcp: use signed arithmetic in tcp_rtx_probe0_timed_out() (bsc#1227863).\n- CVE-2024-41000: block/ioctl: prefer different overflow check (bsc#1227867).\n- CVE-2024-40995: net/sched: act_api: fix possible infinite loop in tcf_idr_check_alloc() (bsc#1227830).\n- CVE-2024-40994: ptp: fix integer overflow in max_vclocks_store (bsc#1227829).\n- CVE-2024-40989: KVM: arm64: Disassociate vcpus from redistributor region on teardown (bsc#1227823).\n- CVE-2024-40978: scsi: qedi: Fix crash while reading debugfs attribute (bsc#1227929).\n- CVE-2024-40959: xfrm6: check ip6_dst_idev() return value in xfrm6_get_saddr() (bsc#1227884).\n- CVE-2024-40958: netns: Make get_net_ns() handle zero refcount net (bsc#1227812).\n- CVE-2024-40957: seg6: fix parameter passing when calling NF_HOOK() in End.DX4 and End.DX6 behaviors (bsc#1227811).\n- CVE-2024-40956: dmaengine: idxd: Fix possible Use-After-Free in irq_process_work_list (bsc#1227810).\n- CVE-2024-40954: net: do not leave a dangling sk pointer, when socket creation fails (bsc#1227808)\n- CVE-2024-40939: net: wwan: iosm: Fix tainted pointer delete is case of region creation fail (bsc#1227799).\n- CVE-2024-40938: landlock: fix d_parent walk (bsc#1227840).\n- CVE-2024-40921: net: bridge: mst: pass vlan group directly to br_mst_vlan_set_state (bsc#1227784).\n- CVE-2024-40920: net: bridge: mst: fix suspicious rcu usage in br_mst_set_state (bsc#1227781).\n- CVE-2024-40909: bpf: Fix a potential use-after-free in bpf_link_free() (bsc#1227798).\n- CVE-2024-40905: ipv6: fix possible race in __fib6_drop_pcpu_from() (bsc#1227761)\n- CVE-2024-39506: liquidio: adjust a NULL pointer handling path in lio_vf_rep_copy_packet (bsc#1227729).\n- CVE-2024-39489: ipv6: sr: fix memleak in seg6_hmac_init_algo (bsc#1227623)\n- CVE-2024-38662: selftests/bpf: Cover verifier checks for mutating sockmap/sockhash (bsc#1226885).\n- CVE-2024-36979: net: bridge: mst: fix vlan use-after-free (bsc#1226604).\n- CVE-2024-36933: net: nsh: Use correct mac_offset to unwind gso skb in nsh_gso_segment() (bsc#1225832).\n- CVE-2024-36929: net: core: reject skb_copy(_expand) for fraglist GSO skbs (bsc#1225814).\n- CVE-2024-36911: hv_netvsc: Do not free decrypted memory (bsc#1225745).\n- CVE-2024-36910: uio_hv_generic: Do not free decrypted memory (bsc#1225717).\n- CVE-2024-36909: Drivers: hv: vmbus: Do not free ring buffers that couldn't be re-encrypted (bsc#1225744).\n- CVE-2024-36881: mm/userfaultfd: Fix reset ptes when close() for wr-protected (bsc#1225718).\n- CVE-2024-36489: tls: fix missing memory barrier in tls_init (bsc#1226874)\n- CVE-2024-36286: netfilter: nfnetlink_queue: acquire rcu_read_lock() in instance_destroy_rcu() (bsc#1226801)\n- CVE-2024-36270: Fix reference in patches.suse/netfilter-tproxy-bail-out-if-IP-has-been-disabled-on.patch (bsc#1226798)\n- CVE-2024-35949: btrfs: make sure that WRITTEN is set on all metadata blocks (bsc#1224700).\n- CVE-2024-35939: Fixed leak pages on dma_set_decrypted() failure (bsc#1224535).\n- CVE-2024-35897: netfilter: nf_tables: discard table flag update with pending basechain deletion (bsc#1224510).\n- CVE-2024-27437: vfio/pci: Disable auto-enable of exclusive INTx IRQ (bsc#1222625).\n- CVE-2024-27433: clk: mediatek: mt7622-apmixedsys: Fix an error handling path in clk_mt8135_apmixed_probe() (bsc#1224711).\n- CVE-2024-27403: kabi: restore const specifier in flow_offload_route_init() (bsc#1224415).\n- CVE-2024-27079: iommu/vt-d: Fix NULL domain on device release (bsc#1223742).\n- CVE-2024-27024: net/rds: fix WARNING in rds_conn_connect_if_down (bsc#1223777).\n- CVE-2024-27011: netfilter: nf_tables: fix memleak in map from abort path (bsc#1223803).\n- CVE-2024-27010: net/sched: Fix mirred deadlock on device recursion (bsc#1223720).\n- CVE-2024-26851: netfilter: nf_conntrack_h323: Add protection for bmp length out of range (bsc#1223074)\n- CVE-2024-26837: net: bridge: switchdev: race between creation of new group memberships and generation of the list of MDB events to replay (bsc#1222973).\n- CVE-2024-26835: netfilter: nf_tables: set dormant flag on hook register failure (bsc#1222967).\n- CVE-2024-26812: kABI: vfio: struct virqfd kABI workaround (bsc#1222808).\n- CVE-2024-26809: netfilter: nft_set_pipapo: release elements in clone only from destroy path (bsc#1222633).\n- CVE-2024-26808: netfilter: nft_chain_filter: handle NETDEV_UNREGISTER for inet/ingress basechain (bsc#1222634).\n- CVE-2024-26735: ipv6: sr: fix possible use-after-free and null-ptr-deref (bsc#1222372).\n- CVE-2024-26677: blacklist.conf: Add e7870cf13d20 ('rxrpc: Fix delayed ACKs to not set the reference serial number') (bsc#1222387)\n- CVE-2024-26669: kABI fix for net/sched: flower: Fix chain template offload (bsc#1222350).\n- CVE-2024-26668: netfilter: nft_limit: reject configurations that cause integer overflow (bsc#1222335).\n- CVE-2024-26631: ipv6: mcast: fix data-race in ipv6_mc_down / mld_ifc_work (bsc#1221630).\n- CVE-2024-26590: erofs: fix inconsistent per-file compression format (bsc#1220252).\n- CVE-2023-52889: apparmor: Fix null pointer deref when receiving skb during sock creation (bsc#1229287).\n- CVE-2023-52859: perf: hisi: Fix use-after-free when register pmu fails (bsc#1225582).\n- CVE-2023-52581: netfilter: nf_tables: fix memleak when more than 255 elements expired (bsc#1220877).\n- CVE-2023-52489: mm/sparsemem: fix race in accessing memory_section-\u003eusage (bsc#1221326).\n\n\nThe following non-security bugs were fixed:\n\n- ACPI/NUMA: Apply SRAT proximity domain to entire CFMWS window (git-fixes).\n- ACPI: SBS: manage alarm sysfs attribute through psy core (stable-fixes).\n- ACPI: battery: create alarm sysfs attribute atomically (stable-fixes).\n- ACPI: processor_idle: use raw_safe_halt() in acpi_idle_play_dead() (git-fixes).\n- ALSA: hda/hdmi: Yet more pin fix for HP EliteDesk 800 G4 (stable-fixes).\n- ALSA: hda/hdmi: Yet more pin fix for HP EliteDesk 800 G4 (stable-fixes).\n- ALSA: hda/realtek - Fixed ALC256 headphone no sound (stable-fixes).\n- ALSA: hda/realtek - Fixed ALC285 headphone no sound (stable-fixes).\n- ALSA: hda/realtek: Add Framework Laptop 13 (Intel Core Ultra) to quirks (stable-fixes).\n- ALSA: hda/realtek: Add Framework Laptop 13 (Intel Core Ultra) to quirks (stable-fixes).\n- ALSA: hda/realtek: Add quirk for Acer Aspire E5-574G (stable-fixes).\n- ALSA: hda/realtek: Add support for new HP G12 laptops (stable-fixes).\n- ALSA: hda/realtek: Enable mute/micmute LEDs on HP Laptop 14-ey0xxx (stable-fixes).\n- ALSA: hda/realtek: Fix noise from speakers on Lenovo IdeaPad 3 15IAU7 (git-fixes).\n- ALSA: hda/realtek: Fix the speaker output on Samsung Galaxy Book3 Ultra (stable-fixes).\n- ALSA: hda/realtek: Implement sound init sequence for Samsung Galaxy Book3 Pro 360 (stable-fixes).\n- ALSA: hda/realtek: support HP Pavilion Aero 13-bg0xxx Mute LED (stable-fixes).\n- ALSA: hda/tas2781: Use correct endian conversion (git-fixes).\n- ALSA: hda/tas2781: fix wrong calibrated data order (git-fixes).\n- ALSA: hda: Add HP MP9 G4 Retail System AMS to force connect list (stable-fixes).\n- ALSA: hda: Add HP MP9 G4 Retail System AMS to force connect list (stable-fixes).\n- ALSA: hda: Conditionally use snooping for AMD HDMI (git-fixes).\n- ALSA: hda: conexant: Fix headset auto detect fail in the polling mode (git-fixes).\n- ALSA: line6: Fix racy access to midibuf (stable-fixes).\n- ALSA: line6: Fix racy access to midibuf (stable-fixes).\n- ALSA: seq: Skip event type filtering for UMP events (git-fixes).\n- ALSA: seq: ump: Explicitly reset RPN with Null RPN (stable-fixes).\n- ALSA: seq: ump: Optimize conversions from SysEx to UMP (git-fixes).\n- ALSA: seq: ump: Transmit RPN/NRPN message at each MSB/LSB data reception (stable-fixes).\n- ALSA: seq: ump: Use the common RPN/bank conversion context (stable-fixes).\n- ALSA: timer: Relax start tick time check for slave timer elements (git-fixes).\n- ALSA: ump: Explicitly reset RPN with Null RPN (stable-fixes).\n- ALSA: ump: Transmit RPN/NRPN message at each MSB/LSB data reception (stable-fixes).\n- ALSA: usb-audio: Add delay quirk for VIVO USB-C-XE710 HEADSET (stable-fixes).\n- ALSA: usb-audio: Correct surround channels in UAC1 channel map (git-fixes).\n- ALSA: usb-audio: Re-add ScratchAmp quirk entries (git-fixes).\n- ALSA: usb-audio: Re-add ScratchAmp quirk entries (git-fixes).\n- ALSA: usb-audio: Support Yamaha P-125 quirk entry (stable-fixes).\n- ALSA: usb: Fix UBSAN warning in parse_audio_unit() (stable-fixes).\n- ASoC: SOF: Intel: hda-dsp: Make sure that no irq handler is pending before suspend (stable-fixes).\n- ASoC: SOF: Remove libraries from topology lookups (git-fixes).\n- ASoC: SOF: Remove libraries from topology lookups (git-fixes).\n- ASoC: SOF: amd: Fix for acp init sequence (git-fixes).\n- ASoC: SOF: ipc4: check return value of snd_sof_ipc_msg_data (stable-fixes).\n- ASoC: SOF: mediatek: Add missing board compatible (stable-fixes).\n- ASoC: allow module autoloading for table board_ids (stable-fixes).\n- ASoC: allow module autoloading for table db1200_pids (stable-fixes).\n- ASoC: amd: acp: fix module autoloading (git-fixes).\n- ASoC: amd: yc: Add quirk entry for OMEN by HP Gaming Laptop 16-n0xxx (bsc#1227182).\n- ASoC: amd: yc: Support mic on HP 14-em0002la (stable-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: Support mic on Lenovo Thinkpad E14 Gen 6 (stable-fixes).\n- ASoC: codecs: wcd938x-sdw: Correct Soundwire ports mask (git-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: wsa881x: Correct Soundwire ports mask (git-fixes).\n- ASoC: codecs: wsa883x: 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: codecs: wsa884x: Correct Soundwire ports mask (git-fixes).\n- ASoC: cs35l45: Checks index of cs35l45_irqs[] (stable-fixes).\n- ASoC: cs35l56: Handle OTP read latency over SoundWire (stable-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: 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: fsl_micfil: Expand the range of FIFO watermark mask (stable-fixes).\n- ASoC: mediatek: mt8188: Mark AFE_DAC_CON0 register as volatile (stable-fixes).\n- ASoC: meson: axg-fifo: fix irq scheduling issue with PREEMPT_RT (git-fixes).\n- ASoC: meson: axg-fifo: fix irq scheduling issue with PREEMPT_RT (git-fixes).\n- ASoC: nau8822: Lower debug print priority (stable-fixes).\n- ASoC: nau8822: Lower debug print priority (stable-fixes).\n- Bluetooth: Add device 13d3:3572 IMC Networks Bluetooth Radio (stable-fixes).\n- Bluetooth: Fix usage of __hci_cmd_sync_status (git-fixes).\n- Bluetooth: L2CAP: Fix deadlock (git-fixes).\n- Bluetooth: MGMT: Add error handling to pair_device() (git-fixes).\n- Bluetooth: SMP: Fix assumption of Central always being Initiator (git-fixes).\n- Bluetooth: bnep: Fix out-of-bound access (stable-fixes).\n- Bluetooth: btintel: Fail setup on error (git-fixes).\n- Bluetooth: btnxpuart: Shutdown timer and prevent rearming when driver unloading (stable-fixes).\n- Bluetooth: btusb: Add RTL8852BE device 0489:e125 to device tables (stable-fixes).\n- Bluetooth: btusb: Add Realtek RTL8852BE support ID 0x13d3:0x3591 (stable-fixes).\n- Bluetooth: hci_conn: Check non NULL function before calling for HFP offload (stable-fixes).\n- Bluetooth: hci_core: Fix LE quote calculation (git-fixes).\n- Bluetooth: hci_core: Fix not handling hibernation actions (git-fixes).\n- Bluetooth: hci_sync: Fix suspending with wrong filter policy (git-fixes).\n- Bluetooth: hci_sync: avoid dup filtering when passive scanning with adv monitor (git-fixes).\n- Bluetooth: l2cap: always unlock channel in l2cap_conless_channel() (git-fixes).\n- Drop libata patch that caused a regression (bsc#1229054)\n- HID: wacom: Defer calculation of resolution until resolution_code is known (git-fixes).\n- Input: i8042 - add Fujitsu Lifebook E756 to i8042 quirk table (bsc#1229056).\n- Input: i8042 - add forcenorestore quirk to leave controller untouched even on s3 (stable-fixes).\n- Input: i8042 - use new forcenorestore quirk to replace old buggy quirk combination (stable-fixes).\n- KVM: Always flush async #PF workqueue when vCPU is being destroyed (git-fixes).\n- KVM: Make KVM_MEM_GUEST_MEMFD mutually exclusive with KVM_MEM_READONLY (git-fixes).\n- KVM: PPC: Book3S HV: Fix the set_one_reg for MMCR3 (bsc#1194869).\n- KVM: PPC: Book3S HV: Handle pending exceptions on guest entry with MSR_EE (bsc#1215199).\n- KVM: Protect vcpu-\u003epid dereference via debugfs with RCU (git-fixes).\n- KVM: Reject overly excessive IDs in KVM_CREATE_VCPU (git-fixes).\n- KVM: Stop processing *all* memslots when 'null' mmu_notifier handler is found (git-fixes).\n- KVM: VMX: Move posted interrupt descriptor out of VMX code (git-fixes).\n- KVM: VMX: Split out the non-virtualization part of vmx_interrupt_blocked() (git-fixes).\n- KVM: VMX: Switch __vmx_exit() and kvm_x86_vendor_exit() in vmx_exit() (git-fixes).\n- KVM: arm64: AArch32: Fix spurious trapping of conditional instructions (git-fixes).\n- KVM: arm64: Add missing memory barriers when switching to pKVM's hyp pgd (git-fixes).\n- KVM: arm64: Allow AArch32 PSTATE.M to be restored as System mode (git-fixes).\n- KVM: arm64: Fix AArch32 register narrowing on userspace write (git-fixes).\n- KVM: arm64: Fix __pkvm_init_switch_pgd call ABI (git-fixes).\n- KVM: arm64: Fix clobbered ELR in sync abort/SError (git-fixes)\n- KVM: arm64: GICv4: Do not perform a map to a mapped vLPI (git-fixes).\n- KVM: arm64: timers: Correctly handle TGE flip with CNTPOFF_EL2 (git-fixes).\n- KVM: arm64: timers: Fix resource leaks in kvm_timer_hyp_init() (git-fixes).\n- KVM: arm64: vgic-its: Test for valid IRQ in MOVALL handler (git-fixes).\n- KVM: arm64: vgic-its: Test for valid IRQ in its_sync_lpi_pending_table() (git-fixes).\n- KVM: arm64: vgic-v2: Use cpuid from userspace as vcpu_id (git-fixes).\n- KVM: arm64: vgic-v4: Restore pending state on host userspace write (git-fixes).\n- KVM: arm64: vgic: Add a non-locking primitive for kvm_vgic_vcpu_destroy() (git-fixes).\n- KVM: arm64: vgic: Force vcpu vgic teardown on vcpu destroy (git-fixes).\n- KVM: arm64: vgic: Simplify kvm_vgic_destroy() (git-fixes).\n- KVM: fix kvm_mmu_memory_cache allocation warning (git-fixes).\n- KVM: nVMX: Add a helper to get highest pending from Posted Interrupt vector (git-fixes).\n- KVM: nVMX: Check for pending posted interrupts when looking for nested events (git-fixes).\n- KVM: nVMX: Request immediate exit iff pending nested event needs injection (git-fixes).\n- KVM: s390: fix LPSWEY handling (bsc#1227634 git-fixes).\n- KVM: s390: fix validity interception issue when gisa is switched off (git-fixes bsc#1229167).\n- KVM: x86/mmu: Bug the VM if KVM tries to split a !hugepage SPTE (git-fixes).\n- KVM: x86: Limit check IDs for KVM_SET_BOOT_CPU_ID (git-fixes).\n- Move upstreamed powerpc patches into sorted section\n- Move upstreamed sound patches into sorted section\n- Moved upstreamed ASoC patch into sorted section\n- NFSD: Support write delegations in LAYOUTGET (git-fixes).\n- NFSv4.1 another fix for EXCHGID4_FLAG_USE_PNFS_DS for DS server (git-fixes).\n- PCI: Add Edimax Vendor ID to pci_ids.h (stable-fixes).\n- PCI: hv: Return zero, not garbage, when reading PCI_INTERRUPT_PIN (git-fixes).\n- PCI: loongson: Enable MSI in LS7A Root Complex (stable-fixes).\n- RDMA/cache: Release GID table even if leak is detected (git-fixes)\n- RDMA/device: Return error earlier if port in not valid (git-fixes)\n- RDMA/hns: Check atomic wr length (git-fixes)\n- RDMA/hns: Fix insufficient extend DB for VFs. (git-fixes)\n- RDMA/hns: Fix mbx timing out before CMD execution is completed (git-fixes)\n- RDMA/hns: Fix missing pagesize and alignment check in FRMR (git-fixes)\n- RDMA/hns: Fix shift-out-bounds when max_inline_data is 0 (git-fixes)\n- RDMA/hns: Fix soft lockup under heavy CEQE load (git-fixes)\n- RDMA/hns: Fix undifined behavior caused by invalid max_sge (git-fixes)\n- RDMA/hns: Fix unmatch exception handling when init eq table fails (git-fixes)\n- RDMA/iwcm: Fix a use-after-free related to destroying CM IDs (git-fixes)\n- RDMA/mana_ib: Use virtual address in dma regions for MRs (git-fixes).\n- RDMA/mlx4: Fix truncated output warning in alias_GUID.c (git-fixes)\n- RDMA/mlx4: Fix truncated output warning in mad.c (git-fixes)\n- RDMA/mlx5: Set mkeys for dmabuf at PAGE_SIZE (git-fixes)\n- RDMA/rxe: Do not set BTH_ACK_MASK for UC or UD QPs (git-fixes)\n- RDMA: Fix netdev tracker in ib_device_set_netdev (git-fixes)\n- Revert 'ALSA: firewire-lib: obsolete workqueue for period update' (bsc#1208783).\n- Revert 'ALSA: firewire-lib: operate for period elapse event in process context' (bsc#1208783).\n- Revert 'KVM: Prevent module exit until all VMs are freed' (git-fixes).\n- Revert 'Revert 'md/raid5: Wait for MD_SB_CHANGE_PENDING in raid5d'' (git-fixes).\n- Revert 'md/raid5: Wait for MD_SB_CHANGE_PENDING in raid5d' (git-fixes).\n- Revert 'misc: fastrpc: Restrict untrusted app to attach to privileged PD' (git-fixes).\n- Revert 'mm: prevent derefencing NULL ptr in pfn_section_valid()' (bsc#1230413).\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 'usb: gadget: uvc: cleanup request when not in correct state' (stable-fixes).\n- Revert 'usb: typec: tcpm: clear pd_event queue in PORT_RESET' (git-fixes).\n- SUNRPC: Fix a race to wake a sync task (git-fixes).\n- SUNRPC: add a missing rpc_stat for TCP TLS (git-fixes).\n- Squashfs: fix variable overflow triggered by sysbot (git-fixes).\n- USB: serial: debug: do not echo input by default (stable-fixes).\n- Update config files. Disable CONFIG_KFENCE on ppc64le (bsc#1226920)\n- Update config files. Disable vdpa drivers for Alibaba ENI and SolidNET (jsc#PED-8954, bsc#1227834)\n- Update patch references for ASoC regression fixes (bsc#1229045, bsc#1229046)\n- afs: fix __afs_break_callback() / afs_drop_open_mmap() race (git-fixes).\n- apparmor: unpack transition table if dfa is not present (bsc#1226031).\n- arm64: ACPI: NUMA: initialize all values of acpi_early_node_map to (git-fixes)\n- arm64: Add Neoverse-V2 part (git-fixes)\n- arm64: Fix KASAN random tag seed initialization (git-fixes)\n- arm64: armv8_deprecated: Fix warning in isndep cpuhp starting process (git-fixes)\n- arm64: barrier: Restore spec_bar() macro (git-fixes)\n- arm64: cputype: Add Cortex-A720 definitions (git-fixes)\n- arm64: cputype: Add Cortex-A725 definitions (git-fixes)\n- arm64: cputype: Add Cortex-X1C definitions (git-fixes)\n- arm64: cputype: Add Cortex-X3 definitions (git-fixes)\n- arm64: cputype: Add Cortex-X4 definitions (git-fixes)\n- arm64: cputype: Add Cortex-X925 definitions (git-fixes)\n- arm64: cputype: Add Neoverse-V3 definitions (git-fixes)\n- arm64: dts: imx8mp: Add NPU Node (git-fixes)\n- arm64: dts: imx8mp: Fix pgc vpu locations (git-fixes)\n- arm64: dts: imx8mp: Fix pgc_mlmix location (git-fixes)\n- arm64: dts: imx8mp: add HDMI power-domains (git-fixes)\n- arm64: errata: Expand speculative SSBS workaround (again) (git-fixes)\n- arm64: errata: Expand speculative SSBS workaround (git-fixes)\n- arm64: errata: Unify speculative SSBS errata logic (git-fixes). Update config files.\n- arm64: jump_label: Ensure patched jump_labels are visible to all CPUs (git-fixes)\n- ata: libata-scsi: Do not overwrite valid sense data when CK_COND=1 (stable-fixes).\n- ata: libata-scsi: Honor the D_SENSE bit for CK_COND=1 and no error (stable-fixes).\n- blacklist.conf: Add libata upstream revert entry (bsc#1229054)\n- bnxt_re: Fix imm_data endianness (git-fixes)\n- bpf, arm64: Fix trampoline for BPF_TRAMP_F_CALL_ORIG (git-fixes)\n- bpf, lpm: Fix check prefixlen before walking trie (git-fixes).\n- bpf/tests: Remove duplicate JSGT tests (git-fixes).\n- bpf: Add crosstask check to __bpf_get_stack (git-fixes).\n- bpf: Detect IP == ksym.end as part of BPF program (git-fixes).\n- bpf: Ensure proper register state printing for cond jumps (git-fixes).\n- bpf: Fix a few selftest failures due to llvm18 change (git-fixes).\n- bpf: Fix a kernel verifier crash in stacksafe() (bsc#1225903).\n- bpf: Fix check_stack_write_fixed_off() to correctly spill imm (git-fixes).\n- bpf: Fix kfunc callback register type handling (git-fixes).\n- bpf: Fix prog_array_map_poke_run map poke update (git-fixes).\n- bpf: Fix unnecessary -EBUSY from htab_lock_bucket (git-fixes).\n- bpf: Mark bpf_spin_{lock,unlock}() helpers with notrace correctly (git-fixes).\n- bpf: Remove unnecessary wait from bpf_map_copy_value() (git-fixes).\n- bpf: Set uattr-\u003ebatch.count as zero before batched update or deletion (git-fixes).\n- bpf: do not infer PTR_TO_CTX for programs with unnamed context type (git-fixes).\n- bpf: enforce precision of R0 on callback return (git-fixes).\n- bpf: extract bpf_ctx_convert_map logic and make it more reusable (git-fixes).\n- bpf: fix control-flow graph checking in privileged mode (git-fixes).\n- bpf: handle bpf_user_pt_regs_t typedef explicitly for PTR_TO_CTX global arg (git-fixes).\n- bpf: hardcode BPF_PROG_PACK_SIZE to 2MB * num_possible_nodes() (git-fixes).\n- bpf: kprobe: remove unused declaring of bpf_kprobe_override (git-fixes).\n- bpf: simplify btf_get_prog_ctx_type() into btf_is_prog_ctx_type() (git-fixes).\n- bpftool: Align output skeleton ELF code (git-fixes).\n- bpftool: Fix -Wcast-qual warning (git-fixes).\n- bpftool: Silence build warning about calloc() (git-fixes).\n- bpftool: mark orphaned programs during prog show (git-fixes).\n- btrfs: add a btrfs_finish_ordered_extent helper (git-fixes).\n- btrfs: add a is_data_bbio helper (git-fixes).\n- btrfs: add an ordered_extent pointer to struct btrfs_bio (git-fixes).\n- btrfs: copy dir permission and time when creating a stub subvolume (bsc#1228321).\n- btrfs: ensure fast fsync waits for ordered extents after a write failure (git-fixes).\n- btrfs: factor out a btrfs_queue_ordered_fn helper (git-fixes).\n- btrfs: factor out a can_finish_ordered_extent helper (git-fixes).\n- btrfs: fix corruption after buffer fault in during direct IO append write (git-fixes).\n- btrfs: fix double inode unlock for direct IO sync writes (git-fixes).\n- btrfs: fix extent map use-after-free when adding pages to compressed bio (git-fixes).\n- btrfs: fix leak of qgroup extent records after transaction abort (git-fixes).\n- btrfs: fix ordered extent split error handling in btrfs_dio_submit_io (git-fixes).\n- btrfs: limit write bios to a single ordered extent (git-fixes).\n- btrfs: make btrfs_finish_ordered_extent() return void (git-fixes).\n- btrfs: merge the two calls to btrfs_add_ordered_extent in run_delalloc_nocow (git-fixes).\n- btrfs: open code btrfs_bio_end_io in btrfs_dio_submit_io (git-fixes).\n- btrfs: open code end_extent_writepage in end_bio_extent_writepage (git-fixes).\n- btrfs: pass a btrfs_inode to btrfs_fdatawrite_range() (git-fixes).\n- btrfs: pass a btrfs_inode to btrfs_wait_ordered_range() (git-fixes).\n- btrfs: pass an ordered_extent to btrfs_reloc_clone_csums (git-fixes).\n- btrfs: pass an ordered_extent to btrfs_submit_compressed_write (git-fixes).\n- btrfs: remove btrfs_add_ordered_extent (git-fixes).\n- btrfs: rename err to ret in btrfs_direct_write() (git-fixes).\n- btrfs: uninline some static inline helpers from tree-log.h (git-fixes).\n- btrfs: use a btrfs_inode in the log context (struct btrfs_log_ctx) (git-fixes).\n- btrfs: use a btrfs_inode local variable at btrfs_sync_file() (git-fixes).\n- btrfs: use bbio-\u003eordered in btrfs_csum_one_bio (git-fixes).\n- btrfs: use btrfs_finish_ordered_extent to complete buffered writes (git-fixes).\n- btrfs: use btrfs_finish_ordered_extent to complete compressed writes (git-fixes).\n- btrfs: use btrfs_finish_ordered_extent to complete direct writes (git-fixes).\n- btrfs: use irq safe locking when running and adding delayed iputs (git-fixes).\n- cachefiles, erofs: Fix NULL deref in when cachefiles is not doing ondemand-mode (bsc#1229245).\n- cachefiles: add missing lock protection when polling (bsc#1229256).\n- cachefiles: add restore command to recover inflight ondemand read requests (bsc#1229244).\n- cachefiles: add spin_lock for cachefiles_ondemand_info (bsc#1229249).\n- cachefiles: cancel all requests for the object that is being dropped (bsc#1229255).\n- cachefiles: defer exposing anon_fd until after copy_to_user() succeeds (bsc#1229251).\n- cachefiles: extract ondemand info field from cachefiles_object (bsc#1229240).\n- cachefiles: fix slab-use-after-free in cachefiles_ondemand_daemon_read() (bsc#1229247).\n- cachefiles: fix slab-use-after-free in cachefiles_ondemand_get_fd() (bsc#1229246).\n- cachefiles: introduce object ondemand state (bsc#1229239).\n- cachefiles: make on-demand read killable (bsc#1229252).\n- cachefiles: narrow the scope of triggering EPOLLIN events in ondemand mode (bsc#1229243).\n- cachefiles: never get a new anonymous fd if ondemand_id is valid (bsc#1229250).\n- cachefiles: propagate errors from vfs_getxattr() to avoid infinite loop (bsc#1229253).\n- cachefiles: remove err_put_fd label in cachefiles_ondemand_daemon_read() (bsc#1229248).\n- cachefiles: resend an open request if the read request's object is closed (bsc#1229241).\n- cachefiles: stop sending new request when dropping object (bsc#1229254).\n- can: mcp251xfd: tef: prepare to workaround broken TEF FIFO tail index erratum (stable-fixes).\n- can: mcp251xfd: tef: update workaround for erratum DS80000789E 6 of mcp2518fd (stable-fixes).\n- ceph: periodically flush the cap releases (bsc#1230056).\n- cgroup/cpuset: Prevent UAF in proc_cpuset_show() (bsc#1228801).\n- cgroup: Add annotation for holding namespace_sem in current_cgns_cgroup_from_root() (bsc#1222254).\n- cgroup: Eliminate the need for cgroup_mutex in proc_cgroup_show() (bsc#1222254).\n- cgroup: Make operations on the cgroup root_list RCU safe (bsc#1222254).\n- cgroup: Remove unnecessary list_empty() (bsc#1222254).\n- cgroup: preserve KABI of cgroup_root (bsc#1222254).\n- char: xillybus: Check USB endpoints when probing device (git-fixes).\n- char: xillybus: Do not destroy workqueue from work item running on it (stable-fixes).\n- char: xillybus: Refine workqueue handling (git-fixes).\n- clk: en7523: fix rate divider for slic and spi clocks (git-fixes).\n- clk: qcom: Park shared RCGs upon registration (git-fixes).\n- clk: qcom: camcc-sc7280: Add parent dependency to all camera GDSCs (git-fixes).\n- clk: qcom: gcc-sa8775p: Update the GDSC wait_val fields and flags (git-fixes).\n- clk: qcom: gcc-sc7280: Update force mem core bit for UFS ICE clock (git-fixes).\n- clk: qcom: gpucc-sa8775p: Park RCG's clk source at XO during disable (git-fixes).\n- clk: qcom: gpucc-sa8775p: Remove the CLK_IS_CRITICAL and ALWAYS_ON flags (git-fixes).\n- clk: qcom: gpucc-sa8775p: Update wait_val fields for GPU GDSC's (git-fixes).\n- clk: qcom: gpucc-sm8350: Park RCG's clk source at XO during disable (git-fixes).\n- clk: qcom: kpss-xcc: Return of_clk_add_hw_provider to transfer the error (git-fixes).\n- clk: visconti: Add bounds-checking coverage for struct visconti_pll_provider (stable-fixes).\n- clocksource/drivers/sh_cmt: Address race condition for clock events (stable-fixes).\n- cpu/SMT: Enable SMT only if a core is online (bsc#1214285 bsc#1205462 ltc#200161 ltc#200588 git-fixes).\n- dev/parport: fix the array out-of-bounds risk (stable-fixes).\n- device property: Add cleanup.h based fwnode_handle_put() scope based cleanup (stable-fixes).\n- dmaengine: dw: Add memory bus width verification (git-fixes).\n- dmaengine: dw: Add peripheral bus width verification (git-fixes).\n- docs: KVM: Fix register ID of SPSR_FIQ (git-fixes).\n- driver core: Fix uevent_show() vs driver detach race (git-fixes).\n- drm/admgpu: fix dereferencing null pointer context (stable-fixes).\n- drm/amd/display: Add delay to improve LTTPR UHBR interop (stable-fixes).\n- drm/amd/display: Add null checker before passing variables (stable-fixes).\n- drm/amd/display: Adjust cursor position (git-fixes).\n- drm/amd/display: Check for NULL pointer (stable-fixes).\n- drm/amd/display: Skip Recompute DSC Params if no Stream on Link (stable-fixes).\n- drm/amd/display: avoid using null object of framebuffer (git-fixes).\n- drm/amd/display: fix cursor offset on rotation 180 (git-fixes).\n- drm/amd/display: fix s2idle entry for DCN3.5+ (stable-fixes).\n- drm/amd/pm: Fix the null pointer dereference for vega10_hwmgr (stable-fixes).\n- drm/amdgpu/jpeg2: properly set atomics vmid field (stable-fixes).\n- drm/amdgpu/jpeg4: properly set atomics vmid field (stable-fixes).\n- drm/amdgpu/pm: Fix the null pointer dereference for smu7 (stable-fixes).\n- drm/amdgpu/pm: Fix the null pointer dereference in apply_state_adjust_rules (stable-fixes).\n- drm/amdgpu/pm: Fix the param type of set_power_profile_mode (stable-fixes).\n- drm/amdgpu/sdma5.2: Update wptr registers as well as doorbell (stable-fixes).\n- drm/amdgpu/sdma5.2: limit wptr workaround to sdma 5.2.1 (git-fixes).\n- drm/amdgpu: Actually check flags for all context ops (stable-fixes).\n- drm/amdgpu: Add lock around VF RLCG interface (stable-fixes).\n- drm/amdgpu: Fix the null pointer dereference to ras_manager (stable-fixes).\n- drm/amdgpu: Forward soft recovery errors to userspace (stable-fixes).\n- drm/amdgpu: Validate TA binary size (stable-fixes).\n- drm/amdgpu: fix dereference null return value for the function amdgpu_vm_pt_parent (stable-fixes).\n- drm/amdgpu: fix potential resource leak warning (stable-fixes).\n- drm/amdgpu: reset vm state machine after gpu reset(vram lost) (stable-fixes).\n- drm/bridge: analogix_dp: properly handle zero sized AUX transactions (stable-fixes).\n- drm/client: fix null pointer dereference in drm_client_modeset_probe (git-fixes).\n- drm/dp_mst: Skip CSN if topology probing is not done yet (stable-fixes).\n- drm/etnaviv: do not block scheduler when GPU is still active (stable-fixes).\n- drm/i915/dsi: Make Lenovo Yoga Tab 3 X90F DMI match less strict (git-fixes).\n- drm/i915/gem: Adjust vma offset for framebuffer mmap offset (stable-fixes).\n- drm/i915/gem: Fix Virtual Memory mapping boundaries calculation (git-fixes).\n- drm/i915/hdcp: Fix HDCP2_STREAM_STATUS macro (git-fixes).\n- drm/i915: Fix possible int overflow in skl_ddi_calculate_wrpll() (git-fixes).\n- drm/lima: set gp bus_stop bit before hard reset (stable-fixes).\n- drm/mediatek/dp: Fix spurious kfree() (git-fixes).\n- drm/msm/dp: fix the max supported bpp logic (git-fixes).\n- drm/msm/dp: reset the link phy params before link training (git-fixes).\n- drm/msm/dpu: capture snapshot on the first commit_done timeout (stable-fixes).\n- drm/msm/dpu: cleanup FB if dpu_format_populate_layout fails (git-fixes).\n- drm/msm/dpu: do not play tricks with debug macros (git-fixes).\n- drm/msm/dpu: drop MSM_ENC_VBLANK support (stable-fixes).\n- drm/msm/dpu: move dpu_encoder's connector assignment to atomic_enable() (git-fixes).\n- drm/msm/dpu: split dpu_encoder_wait_for_event into two functions (stable-fixes).\n- drm/msm/dpu: take plane rotation into account for wide planes (git-fixes).\n- drm/msm/dpu: try multirect based on mdp clock limits (stable-fixes).\n- drm/msm/dpu: use drmm-managed allocation for dpu_encoder_phys (stable-fixes).\n- drm/msm/mdss: Rename path references to mdp_path (stable-fixes).\n- drm/msm/mdss: switch mdss to use devm_of_icc_get() (stable-fixes).\n- drm/msm: Reduce fallout of fence signaling vs reclaim hangs (stable-fixes).\n- drm/nouveau: prime: fix refcount underflow (git-fixes).\n- drm/panel: nt36523: Set 120Hz fps for xiaomi,elish panels (stable-fixes).\n- drm/radeon/evergreen_cs: Clean up errors in evergreen_cs.c (bsc#1229024).\n- drm/radeon: Remove __counted_by from StateArray.states[] (git-fixes).\n- drm/rockchip: vop2: clear afbc en and transform bit for cluster window at linear mode (stable-fixes).\n- drm/virtio: Fix type of dma-fence context variable (git-fixes).\n- drm/vmwgfx: Fix a deadlock in dma buf fence polling (git-fixes).\n- drm/vmwgfx: Fix overlay when using Screen Targets (git-fixes).\n- drm/vmwgfx: Fix prime with external buffers (git-fixes).\n- efi/libstub: Zero initialize heap allocated struct screen_info (git-fixes).\n- evm: do not copy up 'security.evm' xattr (git-fixes).\n- firmware: cirrus: cs_dsp: Initialize debugfs_root to invalid (stable-fixes).\n- fs/netfs/fscache_cookie: add missing 'n_accesses' check (bsc#1229455).\n- fuse: Initialize beyond-EOF page contents before setting uptodate (bsc#1229456).\n- genirq/cpuhotplug, x86/vector: Prevent vector leak during CPU offline (git-fixes).\n- genirq/generic_chip: Make irq_remove_generic_chip() irqdomain aware (git-fixes).\n- genirq/matrix: Exclude managed interrupts in irq_matrix_allocated() (git-fixes).\n- gfs2: setattr_chown: Add missing initialization (git-fixes).\n- gpio: mlxbf3: Support shutdown() function (git-fixes).\n- gpio: prevent potential speculation leaks in gpio_device_get_desc() (stable-fixes).\n- gpio: sysfs: extend the critical section for unregistering sysfs devices (stable-fixes).\n- gss_krb5: Fix the error handling path for crypto_sync_skcipher_setkey (git-fixes).\n- hfs: fix to initialize fields of hfs_inode_info after hfs_alloc_inode() (git-fixes).\n- hwmon: (ltc2992) Avoid division by zero (stable-fixes).\n- hwmon: (ltc2992) Fix memory leak in ltc2992_parse_dt() (git-fixes).\n- hwmon: (pc87360) Bounds check data-\u003einnr usage (stable-fixes).\n- i2c: Fix conditional for substituting empty ACPI functions (stable-fixes).\n- i2c: Use IS_REACHABLE() for substituting empty ACPI functions (git-fixes).\n- i2c: qcom-geni: Add missing clk_disable_unprepare in geni_i2c_runtime_resume (git-fixes).\n- i2c: qcom-geni: Add missing geni_icc_disable in geni_i2c_runtime_resume (git-fixes).\n- i2c: qcom-geni: Add missing geni_icc_disable in geni_i2c_runtime_resume (git-fixes).\n- i2c: riic: avoid potential division by zero (stable-fixes).\n- i2c: smbus: Improve handling of stuck alerts (git-fixes).\n- i2c: smbus: Send alert notifications to all devices if source not found (git-fixes).\n- i2c: stm32f7: Add atomic_xfer method to driver (stable-fixes).\n- i3c: mipi-i3c-hci: Do not unmap region not mapped for transfer (stable-fixes).\n- i3c: mipi-i3c-hci: Remove BUG() when Ring Abort request times out (stable-fixes).\n- i915/perf: Remove code to update PWR_CLK_STATE for gen12 (git-fixes).\n- ice: Fix NULL pointer access, if PF does not support SRIOV_LAG (bsc#1228737).\n- io_uring/advise: support 64-bit lengths (git-fixes).\n- io_uring: Drop per-ctx dummy_ubuf (git-fixes).\n- io_uring: Fix probe of disabled operations (git-fixes).\n- io_uring: fix io_match_task must_hold (git-fixes).\n- io_uring: tighten task exit cancellations (git-fixes).\n- iommu/amd: Convert comma to semicolon (git-fixes).\n- iommu/vt-d: Fix identity map bounds in si_domain_init() (git-fixes).\n- iommufd/device: Fix hwpt at err_unresv in iommufd_device_do_replace() (git-fixes).\n- ip6_tunnel: Fix broken GRO (bsc#1229444).\n- ipv6: sr: fix incorrect unregister order (git-fixes).\n- irqdomain: Fixed unbalanced fwnode get and put (git-fixes).\n- jfs: Fix shift-out-of-bounds in dbDiscardAG (git-fixes).\n- jfs: define xtree root and page independently (git-fixes).\n- jfs: fix null ptr deref in dtInsertEntry (git-fixes).\n- jump_label: Clarify condition in static_key_fast_inc_not_disabled() (git-fixes).\n- jump_label: Fix concurrency issues in static_key_slow_dec() (git-fixes).\n- jump_label: Fix the fix, brown paper bags galore (git-fixes).\n- jump_label: Simplify and clarify static_key_fast_inc_cpus_locked() (git-fixes).\n- kABI fix of: virtio-crypto: handle config changed by work queue (git-fixes).\n- kABI workaround for sound core UMP conversion (stable-fixes).\n- kabi fix for KVM: s390: fix LPSWEY handling (bsc#1227634 git-fixes).\n- kabi fix for SUNRPC: add a missing rpc_stat for TCP TLS (git-fixes).\n- kabi/severities: ignore kABI for FireWire sound local symbols (bsc#1208783)\n- kabi: more build fix without patches.kabi (bsc#1226502)\n- kcov: properly check for softirq context (git-fixes).\n- kernel-binary.spec.in: Enable klp_symbols on openSUSE Tumbleweed (boo#1229042). \n- kernel-binary: generate and install compile_commands.json (bsc#1228971). \n- kernfs: Convert kernfs_path_from_node_locked() from strlcpy() to strscpy() (bsc#1229134).\n- kernfs: fix false-positive WARN(nr_mmapped) in kernfs_drain_open_files (git-fixes).\n- kprobes: Fix to check symbol prefixes correctly (git-fixes).\n- kprobes: Prohibit probing on CFI preamble symbol (git-fixes).\n- kvm: s390: Reject memory region operations for ucontrol VMs (git-fixes bsc#1229168).\n- libbpf: Add missing LIBBPF_API annotation to libbpf_set_memlock_rlim API (git-fixes).\n- libbpf: Apply map_set_def_max_entries() for inner_maps on creation (git-fixes).\n- libbpf: Fix faccessat() usage on Android (git-fixes).\n- libbpf: Use OPTS_SET() macro in bpf_xdp_query() (git-fixes).\n- md-cluster: fix hanging issue while a new disk adding (bsc#1223395).\n- md-cluster: fix hanging issue while a new disk adding (bsc#1223395).\n- md-cluster: fix no recovery job when adding/re-adding a disk (bsc#1223395).\n- md-cluster: fix no recovery job when adding/re-adding a disk (bsc#1223395).\n- md-cluster: keeping kabi compatibility for upstream commit 35a0a409fa26 (bsc#1223395).\n- md/md-bitmap: fix writing non bitmap pages (git-fixes).\n- md/raid1: set max_sectors during early return from choose_slow_rdev() (git-fixes).\n- md/raid1: support read error check (git-fixes).\n- md/raid5: fix deadlock that raid5d() wait for itself to clear MD_SB_CHANGE_PENDING (git-fixes).\n- md/raid5: fix spares errors about rcu usage (git-fixes).\n- md/raid5: recheck if reshape has finished with device_lock held (git-fixes).\n- md: Do not wait for MD_RECOVERY_NEEDED for HOT_REMOVE_DISK ioctl (git-fixes).\n- md: add a mddev_add_trace_msg helper (git-fixes).\n- md: add check for sleepers in md_wakeup_thread() (git-fixes).\n- md: change the return value type of md_write_start to void (git-fixes).\n- md: do not account sync_io if iostats of the disk is disabled (git-fixes).\n- md: do not delete safemode_timer in mddev_suspend (git-fixes).\n- md: factor out a helper exceed_read_errors() to check read_errors (git-fixes).\n- md: fix a suspicious RCU usage warning (git-fixes).\n- media: Revert 'media: dvb-usb: Fix unexpected infinite loop in dvb_usb_read_remote_control()' (git-fixes).\n- media: amphion: Remove lock in s_ctrl callback (stable-fixes).\n- media: drivers/media/dvb-core: copy user arrays safely (stable-fixes).\n- media: pci: cx23885: check cx23885_vdev_init() return (stable-fixes).\n- media: uvcvideo: Add quirk for invalid dev_sof in Logitech C920 (git-fixes).\n- media: uvcvideo: Disable autosuspend for Insta360 Link (stable-fixes).\n- media: uvcvideo: Fix the bandwdith quirk on USB 3.x (stable-fixes).\n- media: uvcvideo: Ignore empty TS packets (stable-fixes).\n- media: uvcvideo: Quirk for invalid dev_sof in Logitech C922 (stable-fixes).\n- media: xc2028: avoid use-after-free in load_firmware_cb() (stable-fixes).\n- memcg: protect concurrent access to mem_cgroup_idr (git-fixes).\n- memory: stm32-fmc2-ebi: check regmap_read return value (stable-fixes).\n- memory: tegra: Skip SID programming if SID registers are not set (stable-fixes).\n- minmax: add a few more MIN_T/MAX_T users (bsc#1229024).\n- minmax: avoid overly complicated constant expressions in VM code (bsc#1229024).\n- minmax: do not use max() in situations that want a C constant expression (bsc#1229024).\n- minmax: fix up min3() and max3() too (bsc#1229024).\n- minmax: improve macro expansion and type checking (bsc#1229024).\n- minmax: make generic MIN() and MAX() macros available everywhere (bsc#1229024).\n- minmax: simplify and clarify min_t()/max_t() implementation (bsc#1229024).\n- minmax: simplify min()/max()/clamp() implementation (bsc#1229024).\n- mm, kmsan: fix infinite recursion due to RCU critical section (git-fixes).\n- mm: prevent derefencing NULL ptr in pfn_section_valid() (git-fixes).\n- mmc: dw_mmc: allow biu and ciu clocks to defer (git-fixes).\n- mmc: mmc_test: Fix NULL dereference on allocation failure (git-fixes).\n- mmc: mtk-sd: receive cmd8 data when hs400 tuning fail (git-fixes).\n- net/iucv: fix the allocation size of iucv_path_table array (git-fixes bsc#1229451).\n- net/iucv: fix use after free in iucv_sock_close() (bsc#1228973).\n- net/rds: fix possible cp null dereference (git-fixes).\n- net/sched: initialize noop_qdisc owner (git-fixes).\n- net: drop bad gso csum_start and offset in virtio_net_hdr (git-fixes).\n- net: ethernet: mtk_wed: fix use-after-free panic in mtk_wed_setup_tc_block_cb() (git-fixes).\n- net: fix sk_memory_allocated_{add|sub} vs softirqs (bsc#1228757).\n- net: mana: Add support for page sizes other than 4KB on ARM64 (jsc#PED-8491 bsc#1226530).\n- net: mana: Fix RX buf alloc_size alignment and atomic op panic (bsc#1229086).\n- net: mana: Fix doorbell out of order violation and avoid unnecessary doorbell rings (bsc#1229154).\n- net: mana: Fix race of mana_hwc_post_rx_wqe and new hwc response (git-fixes).\n- net: missing check virtio (git-fixes).\n- net: phy: micrel: Fix the KSZ9131 MDI-X status issue (git-fixes).\n- net: phy: realtek: add support for RTL8366S Gigabit PHY (git-fixes).\n- net: usb: qmi_wwan: fix memory leak for not ip packets (git-fixes).\n- net: usb: sr9700: fix uninitialized variable use in sr_mdio_read (git-fixes).\n- netfs, fscache: export fscache_put_volume() and add fscache_try_get_volume() (bsc#1228459 bsc#1228462).\n- nfc: pn533: Add poll mod list filling check (git-fixes).\n- nfs: do not invalidate dentries on transient errors (git-fixes).\n- nfs: expose /proc/net/sunrpc/nfs in net namespaces (git-fixes).\n- nfs: make the rpc_stat per net namespace (git-fixes).\n- nfs: pass explicit offset/count to trace events (git-fixes).\n- nfs: propagate readlink errors in nfs_symlink_filler (git-fixes).\n- nouveau/firmware: use dma non-coherent allocator (git-fixes).\n- nvme-multipath: find NUMA path only for online numa-node (git-fixes).\n- nvme-multipath: implement 'queue-depth' iopolicy (bsc#1227706).\n- nvme-multipath: prepare for 'queue-depth' iopolicy (bsc#1227706).\n- nvme-pci: Fix the instructions for disabling power management (git-fixes).\n- nvme-pci: add missing condition check for existence of mapped data (git-fixes).\n- nvme-pci: do not directly handle subsys reset fallout (bsc#1220066).\n- nvme-sysfs: add 'tls_configured_key' sysfs attribute (bsc#1221857).\n- nvme-sysfs: add 'tls_keyring' attribute (bsc#1221857).\n- nvme-tcp: check for invalidated or revoked key (bsc#1221857).\n- nvme-tcp: sanitize TLS key handling (bsc#1221857).\n- nvme: add a newline to the 'tls_key' sysfs attribute (bsc#1221857).\n- nvme: adjust multiples of NVME_CTRL_PAGE_SIZE in offset (git-fixes).\n- nvme: avoid double free special payload (git-fixes).\n- nvme: fix NVME_NS_DEAC may incorrectly identifying the disk as EXT_LBA (git-fixes).\n- nvme: fixup comment for nvme RDMA Provider Type (git-fixes).\n- nvme: split off TLS sysfs attributes into a separate group (bsc#1221857).\n- nvme: tcp: remove unnecessary goto statement (bsc#1221857).\n- nvme_core: scan namespaces asynchronously (bsc#1224105).\n- nvmet-auth: fix nvmet_auth hash error handling (git-fixes).\n- nvmet: always initialize cqe.result (git-fixes).\n- nvmet: do not return 'reserved' for empty TSAS values (git-fixes).\n- nvmet: fix a possible leak when destroy a ctrl during qp establishment (git-fixes).\n- nvmet: make 'tsas' attribute idempotent for RDMA (git-fixes).\n- ocfs2: strict bound check before memcmp in ocfs2_xattr_find_entry() (bsc#1228410).\n- padata: Fix possible divide-by-0 panic in padata_mt_helper() (git-fixes).\n- perf/smmuv3: Enable HiSilicon Erratum 162001900 quirk for HIP08/09 (git-fixes).\n- pinctrl: mediatek: common-v2: Fix broken bias-disable for PULL_PU_PD_RSEL_TYPE (git-fixes).\n- pinctrl: rockchip: correct RK3328 iomux width flag for GPIO2-B pins (git-fixes).\n- pinctrl: single: fix potential NULL dereference in pcs_get_function() (git-fixes).\n- pinctrl: starfive: jh7110: Correct the level trigger configuration of iev register (git-fixes).\n- platform/chrome: cros_ec_proto: Lock device when updating MKBP version (git-fixes).\n- platform/chrome: cros_ec_proto: Lock device when updating MKBP version (git-fixes).\n- platform/surface: aggregator: Fix warning when controller is destroyed in probe (git-fixes).\n- platform/x86/amd/hsmp: Add support for ACPI based probing (jsc#PED-8779).\n- platform/x86/amd/hsmp: Cache pci_dev in struct hsmp_socket (jsc#PED-8779).\n- platform/x86/amd/hsmp: Change devm_kzalloc() to devm_kcalloc() (jsc#PED-8779).\n- platform/x86/amd/hsmp: Check HSMP support on AMD family of processors (jsc#PED-8779).\n- platform/x86/amd/hsmp: Check num_sockets against MAX_AMD_SOCKETS (jsc#PED-8779).\n- platform/x86/amd/hsmp: Create static func to handle platdev (jsc#PED-8779).\n- platform/x86/amd/hsmp: Define a struct to hold mailbox regs (jsc#PED-8779).\n- platform/x86/amd/hsmp: Move dev from platdev to hsmp_socket (jsc#PED-8779).\n- platform/x86/amd/hsmp: Move hsmp_test to probe (jsc#PED-8779).\n- platform/x86/amd/hsmp: Non-ACPI support for AMD F1A_M00~0Fh (jsc#PED-8779).\n- platform/x86/amd/hsmp: Remove extra parenthesis and add a space (jsc#PED-8779).\n- platform/x86/amd/hsmp: Restructure sysfs group creation (jsc#PED-8779).\n- platform/x86/amd/hsmp: switch to use device_add_groups() (jsc#PED-8779).\n- platform/x86/intel/ifs: Initialize union ifs_status to zero (git-fixes).\n- platform/x86: lg-laptop: fix %s null argument warning (stable-fixes).\n- power: supply: axp288_charger: Fix constant_charge_voltage writes (git-fixes).\n- power: supply: axp288_charger: Round constant_charge_voltage writes down (git-fixes).\n- power: supply: qcom_battmgr: return EAGAIN when firmware service is not up (git-fixes).\n- powerpc/64: Set _IO_BASE to POISON_POINTER_DELTA not 0 for CONFIG_PCI=n (bsc#1194869).\n- powerpc/io: Avoid clang null pointer arithmetic warnings (bsc#1194869).\n- powerpc/kexec: make the update_cpus_node() function public (bsc#1194869).\n- powerpc/kexec: split CONFIG_KEXEC_FILE and CONFIG_CRASH_DUMP (bsc#1194869).\n- powerpc/kexec_file: fix cpus node update to FDT (bsc#1194869).\n- powerpc/pseries: Add failure related checks for h_get_mpp and h_get_ppp (bsc#1194869).\n- powerpc/pseries: Whitelist dtl slub object for copying to userspace (bsc#1194869).\n- powerpc/radix: Move some functions into #ifdef CONFIG_KVM_BOOK3S_HV_POSSIBLE (bsc#1194869).\n- powerpc/topology: Check if a core is online (bsc#1214285 bsc#1205462 ltc#200161 ltc#200588 git-fixes).\n- powerpc/xmon: Check cpu id in commands 'c#', 'dp#' and 'dx#' (bsc#1194869).\n- powerpc: fix a file leak in kvm_vcpu_ioctl_enable_cap() (bsc#1194869).\n- powerpc: xor_vmx: Add '-mhard-float' to CFLAGS (bsc#1194869).\n- printk/panic: Allow cpu backtraces to be written into ringbuffer during panic (bsc#1225607).\n- reiserfs: fix uninit-value in comp_keys (git-fixes).\n- rtc: nct3018y: fix possible NULL dereference (stable-fixes).\n- s390/cpum_cf: Fix endless loop in CF_DIAG event stop (git-fixes bsc#1229171).\n- s390/dasd: fix error checks in dasd_copy_pair_store() (git-fixes bsc#1229173).\n- s390/dasd: fix error recovery leading to data corruption on ESE devices (git-fixes bsc#1229452).\n- s390/pci: Add missing virt_to_phys() for directed DIBV (git-fixes bsc#1229174).\n- s390/pci: Allow allocation of more than 1 MSI interrupt (git-fixes bsc#1229172).\n- s390/pci: Refactor arch_setup_msi_irqs() (git-fixes bsc#1229172).\n- s390/pkey: harmonize pkey s390 debug feature calls (bsc#1228720).\n- s390/pkey: introduce dynamic debugging for pkey (bsc#1228720).\n- s390/sclp: Prevent release of buffer in I/O (git-fixes bsc#1229169).\n- s390/uv: Panic for set and remove shared access UVC errors (git-fixes bsc#1229170).\n- samples/bpf: syscall_tp_user: Fix array out-of-bound access (git-fixes).\n- samples/bpf: syscall_tp_user: Rename num_progs into nr_tests (git-fixes).\n- sbitmap: use READ_ONCE to access map-\u003eword (stable-fixes).\n- scsi: lpfc: Allow DEVICE_RECOVERY mode after RSCN receipt if in PRLI_ISSUE state (bsc#1228857).\n- scsi: lpfc: Cancel ELS WQE instead of issuing abort when SLI port is inactive (bsc#1228857).\n- scsi: lpfc: Fix handling of fully recovered fabric node in dev_loss callbk (bsc#1228857).\n- scsi: lpfc: Fix incorrect request len mbox field when setting trunking via sysfs (bsc#1228857).\n- scsi: lpfc: Handle mailbox timeouts in lpfc_get_sfp_info (bsc#1228857).\n- scsi: lpfc: Relax PRLI issue conditions after GID_FT response (bsc#1228857).\n- scsi: lpfc: Revise lpfc_prep_embed_io routine with proper endian macro usages (bsc#1228857).\n- scsi: lpfc: Update lpfc version to 14.4.0.3 (bsc#1228857).\n- scsi: qla2xxx: Avoid possible run-time warning with long model_num (bsc#1228850).\n- scsi: qla2xxx: Complete command early within lock (bsc#1228850).\n- scsi: qla2xxx: Convert comma to semicolon (bsc#1228850).\n- scsi: qla2xxx: Drop driver owner assignment (bsc#1228850).\n- scsi: qla2xxx: During vport delete send async logout explicitly (bsc#1228850).\n- scsi: qla2xxx: Fix debugfs output for fw_resource_count (bsc#1228850).\n- scsi: qla2xxx: Fix flash read failure (bsc#1228850).\n- scsi: qla2xxx: Fix for possible memory corruption (bsc#1228850).\n- scsi: qla2xxx: Fix optrom version displayed in FDMI (bsc#1228850).\n- scsi: qla2xxx: Indent help text (bsc#1228850).\n- scsi: qla2xxx: Reduce fabric scan duplicate code (bsc#1228850).\n- scsi: qla2xxx: Remove unused struct 'scsi_dif_tuple' (bsc#1228850).\n- scsi: qla2xxx: Return ENOBUFS if sg_cnt is more than one for ELS cmds (bsc#1228850).\n- scsi: qla2xxx: Unable to act on RSCN for port online (bsc#1228850).\n- scsi: qla2xxx: Update version to 10.02.09.300-k (bsc#1228850).\n- scsi: qla2xxx: Use QP lock to search for bsg (bsc#1228850).\n- scsi: qla2xxx: validate nvme_local_port correctly (bsc#1228850).\n- selftest/bpf: Add map_in_maps with BPF_MAP_TYPE_PERF_EVENT_ARRAY values (git-fixes).\n- selftests/bpf: Add a test to verify previous stacksafe() fix (bsc#1225903).\n- selftests/bpf: Add assert for user stacks in test_task_stack (git-fixes).\n- selftests/bpf: Add netkit to tc_redirect selftest (git-fixes).\n- selftests/bpf: De-veth-ize the tc_redirect test case (git-fixes).\n- selftests/bpf: Disable IPv6 for lwt_redirect test (git-fixes).\n- selftests/bpf: Fix erroneous bitmask operation (git-fixes).\n- selftests/bpf: Fix issues in setup_classid_environment() (git-fixes).\n- selftests/bpf: Fix potential premature unload in bpf_testmod (git-fixes).\n- selftests/bpf: Fix pyperf180 compilation failure with clang18 (git-fixes).\n- selftests/bpf: Fix the flaky tc_redirect_dtime test (git-fixes).\n- selftests/bpf: Fix up xdp bonding test wrt feature flags (git-fixes).\n- selftests/bpf: Make linked_list failure test more robust (git-fixes).\n- selftests/bpf: Relax time_tai test for equal timestamps in tai_forward (git-fixes).\n- selftests/bpf: Skip module_fentry_shadow test when bpf_testmod is not available (git-fixes).\n- selftests/bpf: Wait for the netstamp_needed_key static key to be turned on (git-fixes).\n- selftests/bpf: fix RELEASE=1 build for tc_opts (git-fixes).\n- selftests/bpf: fix bpf_loop_bench for new callback verification scheme (git-fixes).\n- selftests/bpf: fix compiler warnings in RELEASE=1 mode (git-fixes).\n- selftests/bpf: satisfy compiler by having explicit return in btf test (git-fixes).\n- serial: core: check uartclk for zero to avoid divide by zero (stable-fixes).\n- soc: qcom: cmd-db: Map shared memory as WC, not WB (git-fixes).\n- soc: qcom: pmic_glink: Actually communicate when remote goes down (git-fixes).\n- soundwire: stream: fix programming slave ports for non-continous port maps (git-fixes).\n- spi: Add empty versions of ACPI functions (stable-fixes).\n- spi: microchip-core: fix init function not setting the master and motorola modes (git-fixes).\n- spi: microchip-core: switch to use modern name (stable-fixes).\n- spi: spi-fsl-lpspi: Fix scldiv calculation (git-fixes).\n- spi: spidev: Add missing spi_device_id for bh2228fv (git-fixes).\n- squashfs: squashfs_read_data need to check if the length is 0 (git-fixes).\n- ssb: Fix division by zero issue in ssb_calc_clock_rate (stable-fixes).\n- staging: iio: resolver: ad2s1210: fix use before initialization (stable-fixes).\n- staging: ks7010: disable bh on tx_dev_lock (stable-fixes).\n- string.h: Introduce memtostr() and memtostr_pad() (bsc#1228849).\n- sunrpc: add a struct rpc_stats arg to rpc_create_args (git-fixes).\n- swiotlb: do not set total_used to 0 in swiotlb_create_debugfs_files() (git-fixes).\n- swiotlb: fix swiotlb_bounce() to do partial sync's correctly (git-fixes).\n- syscalls: fix compat_sys_io_pgetevents_time64 usage (git-fixes).\n- thermal/drivers/broadcom: Fix race between removal and clock disable (git-fixes).\n- thermal: bcm2835: Convert to platform remove callback returning void (stable-fixes).\n- thunderbolt: Mark XDomain as unplugged when router is removed (stable-fixes).\n- tools/perf: Fix perf bench epoll to enable the run when some CPU's are offline (bsc#1227747).\n- tools/perf: Fix perf bench futex to enable the run when some CPU's are offline (bsc#1227747).\n- tools/perf: Fix timing issue with parallel threads in perf bench wake-up-parallel (bsc#1227747).\n- tools/resolve_btfids: Fix comparison of distinct pointer types warning in resolve_btfids (git-fixes).\n- tools/resolve_btfids: Fix cross-compilation to non-host endianness (git-fixes).\n- tools/resolve_btfids: Refactor set sorting with types from btf_ids.h (git-fixes).\n- tools/resolve_btfids: fix build with musl libc (git-fixes).\n- trace/pid_list: Change gfp flags in pid_list_fill_irq() (git-fixes).\n- tracing: Return from tracing_buffers_read() if the file has been closed (bsc#1229136 git-fixes).\n- tty: atmel_serial: use the correct RTS flag (git-fixes).\n- tty: serial: fsl_lpuart: mark last busy before uart_add_one_port (git-fixes).\n- usb: cdnsp: fix for Link TRB with TC (git-fixes).\n- usb: cdnsp: fix incorrect index in cdnsp_get_hw_deq function (git-fixes).\n- usb: core: sysfs: Unmerge @usb3_hardware_lpm_attr_group in remove_power_attributes() (git-fixes).\n- usb: dwc3: core: Skip setting event buffers for host only controllers (stable-fixes).\n- usb: dwc3: omap: add missing depopulate in probe error path (git-fixes).\n- usb: dwc3: st: add missing depopulate in probe error path (git-fixes).\n- usb: dwc3: st: fix probed platform device ref count on probe error path (git-fixes).\n- usb: gadget: core: Check for unset descriptor (git-fixes).\n- usb: gadget: fsl: Increase size of name buffer for endpoints (stable-fixes).\n- usb: gadget: u_audio: Check return codes from usb_ep_enable and config_ep_by_speed (git-fixes).\n- usb: gadget: u_serial: Set start_delayed during suspend (git-fixes).\n- usb: gadget: uvc: cleanup request when not in correct state (stable-fixes).\n- usb: typec: fsa4480: Add support to swap SBU orientation (git-fixes).\n- usb: typec: fsa4480: Check if the chip is really there (git-fixes).\n- usb: typec: fsa4480: Relax CHIP_ID check (git-fixes).\n- usb: typec: fsa4480: add support for Audio Accessory Mode (git-fixes).\n- usb: typec: fsa4480: rework mux \u0026 switch setup to handle more states (git-fixes).\n- usb: vhci-hcd: Do not drop references before new references are gained (stable-fixes).\n- vfio/pci: fix potential memory leak in vfio_intx_enable() (git-fixes).\n- vhost-scsi: Handle vhost_vq_work_queue failures for events (git-fixes).\n- vhost-vdpa: switch to use vmf_insert_pfn() in the fault handler (git-fixes).\n- vhost/vsock: always initialize seqpacket_allow (git-fixes).\n- vhost: Release worker mutex during flushes (git-fixes).\n- vhost: Use virtqueue mutex for swapping worker (git-fixes).\n- virt: guest_memfd: fix reference leak on hwpoisoned page (git-fixes).\n- virtio-crypto: handle config changed by work queue (git-fixes).\n- virtio: reenable config if freezing device failed (git-fixes).\n- virtio_net: use u64_stats_t infra to avoid data-races (git-fixes).\n- virtiofs: forbid newlines in tags (bsc#1229940).\n- wifi: ath12k: fix memory leak in ath12k_dp_rx_peer_frag_setup() (stable-fixes).\n- wifi: ath12k: fix soft lockup on suspend (git-fixes).\n- wifi: brcmfmac: cfg80211: Handle SSID based pmksa deletion (git-fixes).\n- wifi: cfg80211: fix reporting failed MLO links status with cfg80211_connect_done (git-fixes).\n- wifi: iwlwifi: fw: fix wgds rev 3 exact size (git-fixes).\n- wifi: mac80211: use monitor sdata with driver only if desired (git-fixes).\n- wifi: mwifiex: duplicate static structs used in driver instances (git-fixes).\n- wifi: nl80211: disallow setting special AP channel widths (stable-fixes).\n- wifi: nl80211: do not give key data to userspace (stable-fixes).\n- wifi: rtw88: usb: Fix disconnection after beacon loss (stable-fixes).\n- wifi: wfx: repair open network AP mode (git-fixes).\n- workqueue: Improve scalability of workqueue watchdog touch (bsc#1193454).\n- workqueue: wq_watchdog_touch is always called with valid CPU (bsc#1193454).\n- x86/asm: Use %c/%n instead of %P operand modifier in asm templates (git-fixes).\n- x86/entry/64: Remove obsolete comment on tracing vs. SYSRET (git-fixes).\n- x86/mm: Fix pti_clone_entry_text() for i386 (git-fixes).\n- x86/mm: Fix pti_clone_pgtable() alignment assumption (git-fixes).\n- x86/mtrr: Check if fixed MTRRs exist before saving them (git-fixes).\n- x86/numa: Fix SRAT lookup of CFMWS ranges with numa_fill_memblks() (git-fixes).\n- x86/numa: Fix the address overlap check in numa_fill_memblks() (git-fixes).\n- x86/numa: Fix the sort compare func used in numa_fill_memblks() (git-fixes).\n- x86/numa: Introduce numa_fill_memblks() (git-fixes).\n- x86/pci: Skip early E820 check for ECAM region (git-fixes).\n- x86/xen: Convert comma to semicolon (git-fixes).\n- xfs: Fix missing interval for missing_owner in xfs fsmap (git-fixes).\n- xfs: Fix the owner setting issue for rmap query in xfs fsmap (git-fixes).\n- xfs: allow cross-linking special files without project quota (git-fixes).\n- xfs: allow symlinks with short remote targets (bsc#1229160).\n- xfs: allow unlinked symlinks and dirs with zero size (git-fixes).\n- xfs: attr forks require attr, not attr2 (git-fixes).\n- xfs: convert comma to semicolon (git-fixes).\n- xfs: do not use current-\u003ejournal_info (git-fixes).\n- xfs: fix unlink vs cluster buffer instantiation race (git-fixes).\n- xfs: honor init_xattrs in xfs_init_new_inode for !ATTR fs (git-fixes).\n- xfs: journal geometry is not properly bounds checked (git-fixes).\n- xfs: match lock mode in xfs_buffered_write_iomap_begin() (git-fixes).\n- xfs: require XFS_SB_FEAT_INCOMPAT_LOG_XATTRS for attr log intent item recovery (git-fixes).\n- xfs: upgrade the extent counters in xfs_reflink_end_cow_extent later (git-fixes).\n- xfs: use XFS_BUF_DADDR_NULL for daddrs in getfsmap code (git-fixes).\n- xfs: use consistent uid/gid when grabbing dquots for inodes (git-fixes).\n- xhci: Fix Panther point NULL pointer deref at full-speed re-enumeration (git-fixes).\n- xprtrdma: Fix rpcrdma_reqs_reset() (git-fixes).\n","status":"published","published":"2024-09-23T08:29:55Z","modified":"2026-02-04T02:30:48.4895Z","updated_at":"2026-11-02T15:53:55.639015Z"},{"id":"SUSE-SU-2024:3483-1","title":"Security update for the Linux Kernel","description":"\nThe SUSE Linux Enterprise 15 SP5 kernel was updated to receive various security bugfixes.\n\nThe following security bugs were fixed:\n\n- CVE-2024-44947: Initialize beyond-EOF page contents before setting uptodate (bsc#1229454).\n- CVE-2024-36936: Touch soft lockup during memory accept (bsc#1225773).\n- CVE-2022-48706: Do proper cleanup if IFCVF init fails (bsc#1225524).\n- CVE-2024-43883: Do not drop references before new references are gained (bsc#1229707).\n- CVE-2024-41062: Sync sock recv cb and release (bsc#1228576).\n- CVE-2024-43861: Fix memory leak for not ip packets (bsc#1229500).\n- CVE-2024-36270: Fix reference in patches.suse/netfilter-tproxy-bail-out-if-IP-has-been-disabled-on.patch (bsc#1226798)\n- CVE-2023-52489: Fix race in accessing memory_section-\u003eusage (bsc#1221326).\n- CVE-2024-43893: Check uartclk for zero to avoid divide by zero (bsc#1229759).\n- CVE-2024-43821: Fix a possible null pointer dereference (bsc#1229315).\n- CVE-2024-43900: Avoid use-after-free in load_firmware_cb() (bsc#1229756).\n- CVE-2024-44938: Fix shift-out-of-bounds in dbDiscardAG (bsc#1229792).\n- CVE-2024-44939: Fix null ptr deref in dtInsertEntry (bsc#1229820).\n- CVE-2024-41087: Fix double free on error (CVE-2024-41087,bsc#1228466).\n- CVE-2024-42277: Avoid NULL deref in sprd_iommu_hw_en (bsc#1229409).\n- CVE-2024-43902: Add null checker before passing variables (bsc#1229767).\n- CVE-2024-43904: Add null checks for 'stream' and 'plane' before dereferencing (bsc#1229768)\n- CVE-2024-43880: Put back removed metod in struct objagg_ops (bsc#1229481).\n- CVE-2024-43884: Add error handling to pair_device() (bsc#1229739)\n- CVE-2024-43899: Fix null pointer deref in dcn20_resource.c (bsc#1229754).\n- CVE-2022-48920: Get rid of warning on transaction commit when using flushoncommit (bsc#1229658).\n- CVE-2023-52906: Fix warning during failed attribute validation (bsc#1229527).\n- CVE-2024-43882: Fixed ToCToU between perm check and set-uid/gid usage. (bsc#1229503)\n- CVE-2024-43866: Always drain health in shutdown callback (bsc#1229495).\n- CVE-2024-26812: Struct virqfd kABI workaround (bsc#1222808).\n- CVE-2022-48912: Fix use-after-free in __nf_register_net_hook() (bsc#1229641)\n- CVE-2024-27010: Fix mirred deadlock on device recursion (bsc#1223720).\n- CVE-2022-48906: Correctly set DATA_FIN timeout when number of retransmits is large (bsc#1229605)\n- CVE-2024-42155: Wipe copies of protected- and secure-keys (bsc#1228733).\n- CVE-2024-42156: Wipe copies of clear-key structures on failure (bsc#1228722).\n- CVE-2023-52899: Add exception protection processing for vd in axi_chan_handle_err function (bsc#1229569).\n- CVE-2024-42158: Use kfree_sensitive() to fix Coccinelle warnings (bsc#1228720).\n- CVE-2024-26631: Fix data-race in ipv6_mc_down / mld_ifc_work (bsc#1221630).\n- CVE-2024-43873: Always initialize seqpacket_allow (bsc#1229488)\n- CVE-2024-40905: Fix possible race in __fib6_drop_pcpu_from() (bsc#1227761)\n- CVE-2024-39489: Fix memleak in seg6_hmac_init_algo (bsc#1227623)\n- CVE-2021-47106: Fix use-after-free in nft_set_catchall_destroy() (bsc#1220962)\n- CVE-2021-47517: Fix panic when interrupt coaleceing is set via ethtool (bsc#1225428).\n- CVE-2024-36489: Fix missing memory barrier in tls_init (bsc#1226874)\n- CVE-2024-41020: Fix fcntl/close race recovery compat path (bsc#1228427).\n- CVE-2024-27079: Fix NULL domain on device release (bsc#1223742).\n- CVE-2024-35897: Discard table flag update with pending basechain deletion (bsc#1224510).\n- CVE-2024-27403: Restore const specifier in flow_offload_route_init() (bsc#1224415).\n- CVE-2024-27011: Fix memleak in map from abort path (bsc#1223803).\n- CVE-2024-43819: Reject memory region operations for ucontrol VMs (bsc#1229290 git-fixes).\n- CVE-2024-26668: Reject configurations that cause integer overflow (bsc#1222335).\n- CVE-2024-26835: Set dormant flag on hook register failure (bsc#1222967).\n- CVE-2024-26808: Handle NETDEV_UNREGISTER for inet/ingress basechain (bsc#1222634).\n- CVE-2024-27016: Validate pppoe header (bsc#1223807).\n- CVE-2024-35945: Prevent nullptr exceptions on ISR (bsc#1224639).\n- CVE-2023-52581: Fix memleak when more than 255 elements expired (bsc#1220877).\n- CVE-2024-36013: Fix slab-use-after-free in l2cap_connect() (bsc#1225578).\n- CVE-2024-43837: Fix updating attached freplace prog in prog_array map (bsc#1229297).\n- CVE-2024-42291: Add a per-VF limit on number of FDIR filters (bsc#1229374).\n- CVE-2024-42268: Fix missing lock on sync reset reload (bsc#1229391).\n- CVE-2024-43834: Fix invalid wait context of page_pool_destroy() (bsc#1229314)\n- CVE-2024-36286: Acquire rcu_read_lock() in instance_destroy_rcu() (bsc#1226801)\n- CVE-2024-26851: Add protection for bmp length out of range (bsc#1223074)\n- CVE-2024-42157: Wipe sensitive data on failure (bsc#1228727 CVE-2024-42157 git-fixes).\n- CVE-2024-26677: Blacklist e7870cf13d20 (' Fix delayed ACKs to not set the reference serial number') (bsc#1222387)\n- CVE-2024-36009: Blacklist 467324bcfe1a ('ax25: Fix netdev refcount issue') (bsc#1224542)\n- CVE-2023-52859: Fix use-after-free when register pmu fails (bsc#1225582).\n- CVE-2024-42280: Fix a use after free in hfcmulti_tx() (bsc#1229388)\n- CVE-2024-42284: Return non-zero value from tipc_udp_addr2str() on error (bsc#1229382)\n- CVE-2024-42283: Initialize all fields in dumped nexthops (bsc#1229383)\n- CVE-2024-42312: Always initialize i_uid/i_gid (bsc#1229357)\n- CVE-2024-43854: Initialize integrity buffer to zero before writing it to media (bsc#1229345)\n- CVE-2024-42322: Properly dereference pe in ip_vs_add_service (bsc#1229347)\n- CVE-2024-42308: Update DRM patch reference (bsc#1229411)\n- CVE-2024-42301: Fix the array out-of-bounds risk (bsc#1229407).\n- CVE-2024-42318: Do not lose track of restrictions on cred_transfer (bsc#1229351).\n- CVE-2024-26669: Fix chain template offload (bsc#1222350).\n- CVE-2023-52889: Fix null pointer deref when receiving skb during sock creation (bsc#1229287,).\n- CVE-2022-48645: Move enetc_set_psfp() out of the common enetc_set_features() (bsc#1223508).\n- CVE-2024-41007: Use signed arithmetic in tcp_rtx_probe0_timed_out() (bsc#1227863).\n- CVE-2024-36933: Use correct mac_offset to unwind gso skb in nsh_gso_segment() (bsc#1225832).\n- CVE-2024-42295: Handle inconsistent state in nilfs_btnode_create_block() (bsc#1229370).\n- CVE-2024-42319: Move devm_mbox_controller_register() after devm_pm_runtime_enable() (bsc#1229350).\n- CVE-2024-43860: Skip over memory region when node value is NULL (bsc#1229319).\n- CVE-2024-43831: Handle invalid decoder vsi (bsc#1229309).\n- CVE-2024-43849: Protect locator_addr with the main mutex (bsc#1229307).\n- CVE-2024-43841: Do not use strlen() in const context (bsc#1229304).\n- CVE-2024-43839: Adjust 'name' buf size of bna_tcb and bna_ccb structures (bsc#1229301).\n- CVE-2024-41088: Fix infinite loop when xmit fails (bsc#1228469).\n- CVE-2024-42281: Fix a segment issue when downgrading gso_size (bsc#1229386).\n- CVE-2024-42271: Fixed a use after free in iucv_sock_close(). (bsc#1229400)\n- CVE-2024-41080: Fix possible deadlock in io_register_iowq_max_workers() (bsc#1228616).\n- CVE-2024-42246: Remap EPERM in case of connection failure in xs_tcp_setup_socket (bsc#1228989).\n- CVE-2024-42232: Fixed a race between delayed_work() and ceph_monc_stop(). (bsc#1228959)\n- CVE-2024-26735: Fix possible use-after-free and null-ptr-deref (bsc#1222372).\n- CVE-2024-42106: Initialize pad field in struct inet_diag_req_v2 (bsc#1228493).\n- CVE-2024-38662: Cover verifier checks for mutating sockmap/sockhash (bsc#1226885).\n- CVE-2024-42110: Move ntb_netdev_rx_handler() to call netif_rx() from __netif_rx() (bsc#1228501).\n- CVE-2024-42247: Avoid unaligned 64-bit memory accesses (bsc#1228988).\n- CVE-2022-48865: Fix kernel panic when enabling bearer (bsc#1228065).\n- CVE-2023-52498: Fix possible deadlocks in core system-wide PM code (bsc#1221269).\n- CVE-2024-41068: Fix sclp_init() cleanup on failure (bsc#1228579).\n- CVE-2022-48808: Fix panic when DSA master device unbinds on shutdown (bsc#1227958).\n- CVE-2024-42095: Fix Errata i2310 with RX FIFO level check (bsc#1228446).\n- CVE-2024-40978: Fix crash while reading debugfs attribute (bsc#1227929).\n- CVE-2024-42107: Do not process extts if PTP is disabled (bsc#1228494).\n- CVE-2024-42139: Fix improper extts handling (bsc#1228503).\n- CVE-2024-42148: Fix multiple UBSAN array-index-out-of-bounds (bsc#1228487).\n- CVE-2024-42142: E-switch, Create ingress ACL when needed (bsc#1228491).\n- CVE-2024-42162: Account for stopped queues when reading NIC stats (bsc#1228706).\n- CVE-2024-42082: Remove WARN() from __xdp_reg_mem_model() (bsc#1228482).\n- CVE-2024-41042: Prefer nft_chain_validate (bsc#1228526).\n- CVE-2023-3610: Fixed use-after-free vulnerability in nf_tables can be exploited to achieve local privilege escalation (bsc#1213580).\n- CVE-2024-42228: Using uninitialized value *size when calling amdgpu_vce_cs_reloc (bsc#1228667).\n- CVE-2024-40995: Fix possible infinite loop in tcf_idr_check_alloc() (bsc#1227830).\n- CVE-2024-38602: Merge repeat codes in ax25_dev_device_down() (git-fixes CVE-2024-38602 bsc#1226613).\n- CVE-2024-38554: Fix reference count leak issue of net_device (bsc#1226742).\n- CVE-2024-36929: Reject skb_copy(_expand) for fraglist GSO skbs (bsc#1225814).\n- CVE-2024-41009: Fix overrunning reservations in ringbuf (bsc#1228020).\n- CVE-2024-27024: Fix WARNING in rds_conn_connect_if_down (bsc#1223777).\n\nThe following non-security bugs were fixed:\n\n- Indicate support for IRQ ResourceSource thru _OSC (git-fixes).\n- Indicate support for the Generic Event Device thru _OSC (git-fixes).\n- Rework system-level device notification handling (git-fixes).\n- Drop nocrt parameter (git-fixes).\n- x86: s2 Post-increment variables when getting constraints (git-fixes).\n- Do not cross .backup mountpoint from backup volume (git-fixes).\n- Add HP MP9 G4 Retail System AMS to force connect list (stable-fixes).\n- Yet more pin fix for HP EliteDesk 800 G4 (stable-fixes).\n- Add Framework Laptop 13 (Intel Core Ultra) to quirks (stable-fixes).\n- Fix noise from speakers on Lenovo IdeaPad 3 15IAU7 (git-fixes).\n- line6: Fix racy access to midibuf (stable-fixes).\n- Relax start tick time check for slave timer elements (git-fixes).\n- Add delay quirk for VIVO USB-C-XE710 HEADSET (stable-fixes).\n- Re-add ScratchAmp quirk entries (git-fixes).\n- Support Yamaha P-125 quirk entry (stable-fixes).\n- Fix UBSAN warning in parse_audio_unit() (stable-fixes).\n- arm64: initialize all values of acpi_early_node_map to (git-fixes)\n- arm64: initialize all values of acpi_early_node_map to (git-fixes)\n- arm64: Add Neoverse-V2 part (git-fixes)\n- arm64: armv8_ Fix warning in isndep cpuhp starting process (git-fixes)\n- arm64: armv8_ Fix warning in isndep cpuhp starting process (git-fixes)\n- arm64: Restore spec_bar() macro (git-fixes)\n- arm64: Add missing .field_width for GIC system registers (git-fixes)\n- arm64: Fix the visibility of compat hwcaps (git-fixes)\n- arm64: Force HWCAP to be based on the sysreg visible to (git-fixes)\n- arm64: Add Cortex-A720 definitions (git-fixes)\n- arm64: Add Cortex-A725 definitions (git-fixes)\n- arm64: Add Cortex-X1C definitions (git-fixes)\n- arm64: Add Cortex-X3 definitions (git-fixes)\n- arm64: Add Cortex-X4 definitions (git-fixes)\n- arm64: Add Cortex-X925 definitions (git-fixes)\n- arm64: Add Neoverse-V3 definitions (git-fixes)\n- arm64: Increase VOP clk rate on RK3328 (git-fixes)\n- arm64: Increase VOP clk rate on RK3328 (git-fixes)\n- arm64: Expand speculative SSBS workaround (again) (git-fixes)\n- arm64: Expand speculative SSBS workaround (git-fixes)\n- arm64: Unify speculative SSBS errata logic (git-fixes) Also update default configuration.\n- arm64: Fix KASAN random tag seed initialization (git-fixes)\n- arm64: Fix KASAN random tag seed initialization (git-fixes)\n- wcd938 Correct Soundwire ports mask (git-fixes).\n- wsa881 Correct Soundwire ports mask (git-fixes).\n- fix irq scheduling issue with PREEMPT_RT (git-fixes).\n- Introduce async_schedule_dev_nocall() (bsc#1221269).\n- Split async_schedule_node_domain() (bsc#1221269).\n- Fix usage of __hci_cmd_sync_status (git-fixes).\n- hci_ Fix not handling hibernation actions (git-fixes).\n- l2 always unlock channel in l2cap_conless_channel() (git-fixes).\n- L2 Fix deadlock (git-fixes).\n- Fix a kernel verifier crash in stacksafe() (bsc#1225903).\n- remove unused declaring of bpf_kprobe_override (git-fixes).\n- fix leak of qgroup extent records after transaction abort (git-fixes).\n- make btrfs_destroy_delayed_refs() return void (git-fixes).\n- remove unnecessary prototype declarations at disk-io.c (git-fixes).\n- update fs features directory asynchronously (bsc#1226168).\n- propagate errors from vfs_getxattr() to avoid infinite loop (bsc#1229418).\n- issue a cap release immediately if no cap exists (bsc#1225162).\n- periodically flush the cap releases (bsc#1225162).\n- Enable SMT only if a core is online (bsc#1214285 bsc#1205462 ltc#200161 ltc#200588 git-fixes).\n- cpuidle, Evaluate LPI arch_flags for broadcast timer (git-fixes).\n- Fix register ID of SPSR_FIQ (git-fixes).\n- add missing MODULE_DESCRIPTION() macros (stable-fixes).\n- Add labels for both Valve Steam Deck revisions (stable-fixes).\n- Add quirk for Aya Neo KUN (stable-fixes).\n- Add quirk for Lenovo Yoga Tab 3 X90F (stable-fixes).\n- Add quirk for Nanote UMPC-01 (stable-fixes).\n- Add quirk for OrangePi Neo (stable-fixes).\n- drm/amd/amdgpu/imu_v11_0: Increase buffer size to ensure all possible values can be stored (stable-fixes).\n- Add NULL check for 'afb' before dereferencing in amdgpu_dm_plane_handle_cursor_update (stable-fixes).\n- avoid using null object of framebuffer (git-fixes).\n- Fix \u0026\u0026 vs || typos (git-fixes).\n- Skip Recompute DSC Params if no Stream on Link (stable-fixes).\n- Validate hw_points_num before using it (stable-fixes).\n- Fix the null pointer dereference for vega10_hwmgr (stable-fixes).\n- Actually check flags for all context ops (stable-fixes).\n- Add lock around VF RLCG interface (stable-fixes).\n- fix dereference null return value for the function amdgpu_vm_pt_parent (stable-fixes).\n- Fix the null pointer dereference to ras_manager (stable-fixes).\n- Validate TA binary size (stable-fixes).\n- drm/amdgpu/jpeg2: properly set atomics vmid field (stable-fixes).\n- Fix the null pointer dereference for smu7 (stable-fixes).\n- Fix the null pointer dereference in apply_state_adjust_rules (stable-fixes).\n- Fix the param type of set_power_profile_mode (stable-fixes).\n- analogix_ properly handle zero sized AUX transactions (stable-fixes).\n- tc358768: Attempt to fix DSI horizontal timings (stable-fixes).\n- fix null pointer dereference in drm_client_modeset_probe (git-fixes).\n- drm/dp_ Skip CSN if topology probing is not done yet (stable-fixes).\n- set gp bus_stop bit before hard reset (stable-fixes).\n- reset the link phy params before link training (git-fixes).\n- cleanup FB if dpu_format_populate_layout fails (git-fixes).\n- do not play tricks with debug macros (git-fixes).\n- Zero-initialize iosys_map (stable-fixes).\n- fix inode-\u003ei_blocks for non-512 byte sector size device (git-fixes).\n- fix potential deadlock on __exfat_get_dentry_set (git-fixes).\n- redefine DIR_DELETED as the bad cluster number (git-fixes).\n- support dynamic allocate bh for exfat_entry_set_cache (git-fixes).\n- fs/netfs/fscache_ add missing 'n_accesses' check (bsc#1229453).\n- Initialize beyond-EOF page contents before setting uptodate (bsc#1229454).\n- Add might_sleep() to disable_irq() (git-fixes).\n- Always limit the affinity to online CPUs (git-fixes).\n- Do not return error on missing optional irq_request_resources() (git-fixes).\n- Take the proposed affinity at face value if force==true (git-fixes).\n- genirq/cpuhotplug, x86 Prevent vector leak during CPU offline (git-fixes).\n- genirq/generic_ Make irq_remove_generic_chip() irqdomain aware (git-fixes).\n- Fix NULL pointer deref in irq_data_get_affinity_mask() (git-fixes).\n- Do not try to remove non-existing sysfs files (git-fixes).\n- Exclude managed interrupts in irq_matrix_allocated() (git-fixes).\n- Shutdown managed interrupts with unsatifiable affinities (git-fixes).\n- gss_krb5: Fix the error handling path for crypto_sync_skcipher_setkey (git-fixes).\n- fix to initialize fields of hfs_inode_info after hfs_alloc_inode() (git-fixes).\n- i2 Improve handling of stuck alerts (git-fixes).\n- i2 Send alert notifications to all devices if source not found (git-fixes).\n- Convert comma to semicolon (git-fixes).\n- ip6_ Fix broken GRO (bsc#1229444).\n- ipv6: fix incorrect unregister order (git-fixes).\n- Drop bogus fwspec-mapping error handling (git-fixes).\n- Fix association race (git-fixes).\n- Fix disassociation race (git-fixes).\n- Fix domain registration race (git-fixes).\n- Fix mapping-creation race (git-fixes).\n- Fixed unbalanced fwnode get and put (git-fixes).\n- Look for existing mapping only once (git-fixes).\n- Refactor __irq_domain_alloc_irqs() (git-fixes).\n- Report irq number for NOMAP domains (git-fixes).\n- Revert 'mm: prevent derefencing NULL ptr in pfn_section_valid()' (bsc#1230413).\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- kernel/irq/irqdomain. fix memory leak with using debugfs_lookup() (git-fixes).\n- Fix to check symbol prefixes correctly (git-fixes).\n- move from strlcpy with unused retval to strscpy (git-fixes).\n- protect concurrent access to mem_cgroup_idr (git-fixes).\n- mm, fix infinite recursion due to RCU critical section (git-fixes).\n- prevent derefencing NULL ptr in pfn_section_valid() (git-fixes).\n- dw_ allow biu and ciu clocks to defer (git-fixes).\n- mmc_ Fix NULL dereference on allocation failure (git-fixes).\n- ks8851: Fix another TX stall caused by wrong ISR flag handling (git-fixes).\n- ks8851: Fix deadlock with the SPI chip variant (git-fixes).\n- ks8851: Fix potential TX stall after interface reopen (git-fixes).\n- ks8851: Fix TX stall caused by TX buffer overrun (gix-fixes).\n- Add support for page sizes other than 4KB on ARM64 (jsc#PED-8491 bsc#1226530).\n- Fix doorbell out of order violation and avoid unnecessary doorbell rings (bsc#1229154).\n- Fix race of mana_hwc_post_rx_wqe and new hwc response (git-fixes).\n- Fix RX buf alloc_size alignment and atomic op panic (bsc#1229086).\n- remove two BUG() from skb_checksum_help() (bsc#1229312).\n- qmi_ fix memory leak for not ip packets (git-fixes).\n- fix possible cp null dereference (git-fixes).\n- initialize noop_qdisc owner (git-fixes).\n- pn533: Add poll mod list filling check (git-fixes).\n- expose /proc/net/sunrpc/nfs in net namespaces (git-fixes).\n- make the rpc_stat per net namespace (git-fixes).\n- add posix ACLs to struct nfsd_attrs (git-fixes).\n- add security label to struct nfsd_attrs (git-fixes).\n- fix regression with setting ACLs (git-fixes).\n- Fix strncpy() fortify warning (git-fixes).\n- Increase NFSD_MAX_OPS_PER_COMPOUND (git-fixes).\n- introduce struct nfsd_attrs (git-fixes).\n- move from strlcpy with unused retval to strscpy (git-fixes).\n- Optimize DRC bucket pruning (git-fixes).\n- return error if nfs4_setacl fails (git-fixes).\n- set attributes when creating symlinks (git-fixes).\n- use locks_inode_context helper (git-fixes).\n- nilfs2: Remove check for PageError (git-fixes).\n- nvme_ scan namespaces asynchronously (bsc#1224105).\n- ocfs2: use coarse time for new created files (git-fixes).\n- Fix possible divide-by-0 panic in padata_mt_helper() (git-fixes).\n- perf/smmuv3: Enable HiSilicon Erratum 162001900 quirk for HIP08/09 (git-fixes).\n- platform/x86 Add support for ACPI based probing (jsc#PED-8779).\n- platform/x86 Cache pci_dev in struct hsmp_socket (jsc#PED-8779).\n- platform/x86 Change devm_kzalloc() to devm_kcalloc() (jsc#PED-8779).\n- platform/x86 Check HSMP support on AMD family of processors (jsc#PED-8779).\n- platform/x86 Check num_sockets against MAX_AMD_SOCKETS (jsc#PED-8779).\n- platform/x86 Create static func to handle platdev (jsc#PED-8779).\n- platform/x86 Define a struct to hold mailbox regs (jsc#PED-8779).\n- platform/x86 Move dev from platdev to hsmp_socket (jsc#PED-8779).\n- platform/x86 Move hsmp_test to probe (jsc#PED-8779).\n- platform/x86 Non-ACPI support for AMD F1A_M00~0Fh (jsc#PED-8779).\n- platform/x86 Remove extra parenthesis and add a space (jsc#PED-8779).\n- platform/x86 Restructure sysfs group creation (jsc#PED-8779).\n- platform/x86 switch to use device_add_groups() (jsc#PED-8779).\n- axp288_ Fix constant_charge_voltage writes (git-fixes).\n- axp288_ Round constant_charge_voltage writes down (git-fixes).\n- Fail build if using recordmcount with binutils v2.37 (bsc#1194869).\n- Mark .opd section read-only (bsc#1194869).\n- use generic version of arch_is_kernel_initmem_freed() (bsc#1194869).\n- xor_ Add '-mhard-float' to CFLAGS (bsc#1194869).\n- powerpc/64: Set _IO_BASE to POISON_POINTER_DELTA not 0 for CONFIG_PCI=n (bsc#1194869).\n- Avoid clang null pointer arithmetic warnings (bsc#1194869).\n- powerpc/kexec_ fix cpus node update to FDT (bsc#1194869).\n- make the update_cpus_node() function public (bsc#1194869).\n- split CONFIG_KEXEC_FILE and CONFIG_CRASH_DUMP (bsc#1194869).\n- Add failure related checks for h_get_mpp and h_get_ppp (bsc#1194869).\n- Whitelist dtl slub object for copying to userspace (bsc#1194869).\n- Move some functions into #ifdef CONFIG_KVM_BOOK3S_HV_POSSIBLE (bsc#1194869).\n- Check if a core is online (bsc#1214285 bsc#1205462 ltc#200161 ltc#200588 git-fixes).\n- Check cpu id in commands 'c#', 'dp#' and 'dx#' (bsc#1194869).\n- RDMA/mana_ Use virtual address in dma regions for MRs (git-fixes).\n- Fix incomplete state save in rxe_requester (git-fixes)\n- Fix rxe_modify_srq (git-fixes)\n- Handle zero length rdma (git-fixes)\n- Move work queue code to subroutines (git-fixes)\n- s390 get rid of register asm (git-fixes bsc#1227079 bsc#1229187).\n- s390 Make use of invalid opcode produce a link error (git-fixes bsc#1227079).\n- s390 Split and rework cpacf query functions (git-fixes bsc#1229187).\n- s390 fix error checks in dasd_copy_pair_store() (git-fixes bsc#1229190).\n- s390 fix error recovery leading to data corruption on ESE devices (git-fixes bsc#1229573).\n- s390 Prevent release of buffer in I/O (git-fixes bsc#1229572).\n- s390 Panic for set and remove shared access UVC errors (git-fixes bsc#1229188).\n- Fix scldiv calculation (git-fixes).\n- add a struct rpc_stats arg to rpc_create_args (git-fixes).\n- Fix a race to wake a sync task (git-fixes).\n- fix swiotlb_bounce() to do partial sync's correctly (git-fixes).\n- fix compat_sys_io_pgetevents_time64 usage (git-fixes).\n- Return from tracing_buffers_read() if the file has been closed (bsc#1229136 git-fixes).\n- add check for crypto_shash_tfm_digest (git-fixes).\n- dbg_orphan_ Fix missed key type checking (git-fixes).\n- Fix adding orphan entry twice for the same inode (git-fixes).\n- Fix unattached xattr inode if powercut happens after deleting (git-fixes).\n- fix potential memory leak in vfio_intx_enable() (git-fixes).\n- fix wgds rev 3 exact size (git-fixes).\n- duplicate static structs used in driver instances (git-fixes).\n- x86 drop the duplicate APM_MINOR_DEV macro (git-fixes).\n- x86 Fix PUSH instruction in x86 instruction decoder opcode map (git-fixes).\n- x86 Fix pti_clone_entry_text() for i386 (git-fixes).\n- x86 Check if fixed MTRRs exist before saving them (git-fixes).\n- x86 Work around false positive kmemleak report in msr_build_context() (git-fixes).\n- Fix missing interval for missing_owner in xfs fsmap (git-fixes).\n- Fix the owner setting issue for rmap query in xfs fsmap (git-fixes).\n- use XFS_BUF_DADDR_NULL for daddrs in getfsmap code (git-fixes).\n- Fix Panther point NULL pointer deref at full-speed re-enumeration (git-fixes).\n- Fix rpcrdma_reqs_reset() (git-fixes).\n","status":"published","published":"2024-09-27T15:11:57Z","modified":"2026-02-04T04:18:47.136888Z","updated_at":"2026-11-02T15:53:55.639015Z"},{"id":"SUSE-SU-2025:20044-1","title":"Security update for the Linux Kernel","description":"\n\nThe SUSE Linux Enterprise Micro 6.0 kernel was updated to receive various security bugfixes.\n\nThis release includes the first live patch.\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-2023-52581: netfilter: nf_tables: fix memleak when more than 255 elements expired (bsc#1220877).\n- CVE-2023-52859: perf: hisi: Fix use-after-free when register pmu fails (bsc#1225582).\n- CVE-2023-52889: apparmor: Fix null pointer deref when receiving skb during sock creation (bsc#1229287,).\n- CVE-2024-26590: erofs: fix inconsistent per-file compression format (bsc#1220252).\n- CVE-2024-26631: ipv6: mcast: fix data-race in ipv6_mc_down / mld_ifc_work (bsc#1221630).\n- CVE-2024-26668: netfilter: nft_limit: reject configurations that cause integer overflow (bsc#1222335).\n- CVE-2024-26669: kABI fix for net/sched: flower: Fix chain template offload (bsc#1222350).\n- CVE-2024-26677: blacklist.conf: Add e7870cf13d20 (\"rxrpc: Fix delayed ACKs to not set the reference serial number\") (bsc#1222387)\n- CVE-2024-26735: ipv6: sr: fix possible use-after-free and null-ptr-deref (bsc#1222372).\n- CVE-2024-26808: netfilter: nft_chain_filter: handle NETDEV_UNREGISTER for inet/ingress basechain (bsc#1222634).\n- CVE-2024-26809: netfilter: nft_set_pipapo: release elements in clone only from destroy path (bsc#1222633).\n- CVE-2024-26812: kABI: vfio: struct virqfd kABI workaround (bsc#1222808).\n- CVE-2024-26835: netfilter: nf_tables: set dormant flag on hook register failure (bsc#1222967).\n- CVE-2024-26837: net: bridge: switchdev: Skip MDB replays of deferred events on offload (bsc#1222973).\n- CVE-2024-26851: netfilter: nf_conntrack_h323: Add protection for bmp length out of range (bsc#1223074)\n- CVE-2024-27010: net/sched: Fix mirred deadlock on device recursion (bsc#1223720).\n- CVE-2024-27011: netfilter: nf_tables: fix memleak in map from abort path (bsc#1223803).\n- CVE-2024-27024: net/rds: fix WARNING in rds_conn_connect_if_down (bsc#1223777).\n- CVE-2024-27079: iommu/vt-d: Fix NULL domain on device release (bsc#1223742).\n- CVE-2024-27403: kabi: restore const specifier in flow_offload_route_init() (bsc#1224415).\n- CVE-2024-27433: clk: mediatek: mt7622-apmixedsys: Fix an error handling path in clk_mt8135_apmixed_probe() (bsc#1224711).\n- CVE-2024-27437: vfio/pci: Disable auto-enable of exclusive INTx IRQ (bsc#1222625).\n- CVE-2024-35897: netfilter: nf_tables: discard table flag update with pending basechain deletion (bsc#1224510).\n- CVE-2024-35939: Fixed leak pages on dma_set_decrypted() failure (bsc#1224535).\n- CVE-2024-35949: btrfs: make sure that WRITTEN is set on all metadata blocks (bsc#1224700).\n- CVE-2024-36286: netfilter: nfnetlink_queue: acquire rcu_read_lock() in instance_destroy_rcu() (bsc#1226801)\n- CVE-2024-36489: tls: fix missing memory barrier in tls_init (bsc#1226874)\n- CVE-2024-36881: mm/userfaultfd: reset ptes when close() for wr-protected ones (bsc#1225718).\n- CVE-2024-36929: net: core: reject skb_copy(_expand) for fraglist GSO skbs (bsc#1225814).\n- CVE-2024-36933: net: nsh: Use correct mac_offset to unwind gso skb in nsh_gso_segment() (bsc#1225832).\n- CVE-2024-36979: net: bridge: mst: fix vlan use-after-free syzbot reported a suspicious rcu usage[1] in bridge's mst code. (bsc#1226604).\n- CVE-2024-38662: selftests/bpf: Cover verifier checks for mutating sockmap/sockhash (bsc#1226885).\n- CVE-2024-39489: ipv6: sr: fix memleak in seg6_hmac_init_algo (bsc#1227623)\n- CVE-2024-39506: liquidio: adjust a NULL pointer handling path in lio_vf_rep_copy_packet (bsc#1227729).\n- CVE-2024-40905: ipv6: fix possible race in __fib6_drop_pcpu_from() (bsc#1227761)\n- CVE-2024-40909: bpf: Fix a potential use-after-free in bpf_link_free() (bsc#1227798).\n- CVE-2024-40920: net: bridge: mst: fix suspicious rcu usage in br_mst_set_state (bsc#1227781).\n- CVE-2024-40921: net: bridge: mst: pass vlan group directly to br_mst_vlan_set_state (bsc#1227784).\n- CVE-2024-40938: landlock: fix d_parent walk (bsc#1227840).\n- CVE-2024-40939: net: wwan: iosm: Fix tainted pointer delete is case of region creation fail (bsc#1227799).\n- CVE-2024-40954: net: do not leave a dangling sk pointer, when socket creation fails (bsc#1227808)\n- CVE-2024-40956: dmaengine: idxd: Fix possible Use-After-Free in irq_process_work_list (bsc#1227810).\n- CVE-2024-40957: seg6: fix parameter passing when calling NF_HOOK() in End.DX4 and End.DX6 behaviors (bsc#1227811).\n- CVE-2024-40958: netns: Make get_net_ns() handle zero refcount net (bsc#1227812).\n- CVE-2024-40959: xfrm6: check ip6_dst_idev() return value in xfrm6_get_saddr() (bsc#1227884).\n- CVE-2024-40978: scsi: qedi: Fix crash while reading debugfs attribute (bsc#1227929).\n- CVE-2024-40989: KVM: arm64: Disassociate vcpus from redistributor region on teardown (bsc#1227823).\n- CVE-2024-40994: ptp: fix integer overflow in max_vclocks_store (bsc#1227829).\n- CVE-2024-40995: net/sched: act_api: fix possible infinite loop in tcf_idr_check_alloc() (bsc#1227830).\n- CVE-2024-41000: block/ioctl: prefer different overflow check (bsc#1227867).\n- CVE-2024-41007: tcp: use signed arithmetic in tcp_rtx_probe0_timed_out() (bsc#1227863).\n- CVE-2024-41009: bpf: Fix overrunning reservations in ringbuf (bsc#1228020).\n- CVE-2024-41010: bpf: Fix too early release of tcx_entry (bsc#1228021).\n- CVE-2024-41012: filelock: Remove locks reliably when fcntl/close race is detected (bsc#1228247).\n- CVE-2024-41015: ocfs2: add bounds checking to ocfs2_check_dir_entry() (bsc#1228409).\n- CVE-2024-41020: filelock: Fix fcntl/close race recovery compat path (bsc#1228427).\n- CVE-2024-41032: mm: vmalloc: check if a hash-index is in cpu_possible_mask (bsc#1228460).\n- CVE-2024-41036: net: ks8851: Fix deadlock with the SPI chip variant (bsc#1228496).\n- CVE-2024-41040: net/sched: Fix UAF when resolving a clash (bsc#1228518).\n- CVE-2024-41041: udp: Set SOCK_RCU_FREE earlier in udp_lib_get_port() (bsc#1228520).\n- CVE-2024-41044: ppp: reject claimed-as-LCP but actually malformed packets (bsc#1228530).\n- CVE-2024-41048: skmsg: Skip zero length skb in sk_msg_recvmsg (bsc#1228565).\n- CVE-2024-41050: cachefiles: cyclic allocation of msg_id to avoid reuse (bsc#1228499).\n- CVE-2024-41051: cachefiles: wait for ondemand_object_worker to finish when dropping object (bsc#1228468).\n- CVE-2024-41057: cachefiles: fix slab-use-after-free in cachefiles_withdraw_cookie() (bsc#1228462).\n- CVE-2024-41058: cachefiles: fix slab-use-after-free in fscache_withdraw_volume() (bsc#1228459).\n- CVE-2024-41062: bluetooth/l2cap: sync sock recv cb and release (bsc#1228576).\n- CVE-2024-41064: powerpc/eeh: avoid possible crash when edev-\u003epdev changes (bsc#1228599).\n- CVE-2024-41066: ibmvnic: add tx check to prevent skb leak (bsc#1228640).\n- CVE-2024-41068: s390/sclp: Fix sclp_init() cleanup on failure (bsc#1228579).\n- CVE-2024-41069: ASoC: topology: Fix route memory corruption (bsc#1228644).\n- CVE-2024-41070: KVM: PPC: Book3S HV: Prevent UAF in kvm_spapr_tce_attach_iommu_group() (bsc#1228581).\n- CVE-2024-41074: cachefiles: Set object to close if ondemand_id \u003c 0 in copen (bsc#1228643).\n- CVE-2024-41075: cachefiles: add consistency check for copen/cread (bsc#1228646).\n- CVE-2024-41076: NFSv4: Fix memory leak in nfs4_set_security_label (bsc#1228649).\n- CVE-2024-41078: btrfs: qgroup: fix quota root leak after quota disable failure (bsc#1228655).\n- CVE-2024-41080: io_uring: fix possible deadlock in io_register_iowq_max_workers() (bsc#1228616).\n- CVE-2024-41081: ila: block BH in ila_output() (bsc#1228617).\n- CVE-2024-41084: cxl/region: Avoid null pointer dereference in region lookup (bsc#1228472).\n- CVE-2024-42070: netfilter: nf_tables: fully validate NFT_DATA_VALUE on store to data registers (bsc#1228470).\n- CVE-2024-42073: mlxsw: spectrum_buffers: Fix memory corruptions on Spectrum-4 systems (bsc#1228457).\n- CVE-2024-42079: gfs2: Fix NULL pointer dereference in gfs2_log_flush (bsc#1228672).\n- CVE-2024-42082: xdp: Remove WARN() from __xdp_reg_mem_model() (bsc#1228482).\n- CVE-2024-42093: net/dpaa2: Avoid explicit cpumask var allocation on stack (bsc#1228680).\n- CVE-2024-42095: serial: 8250_omap: Fix Errata i2310 with RX FIFO level check (bsc#1228446).\n- CVE-2024-42096: x86: stop playing stack games in profile_pc() (bsc#1228633).\n- CVE-2024-42106: inet_diag: Initialize pad field in struct inet_diag_req_v2 (bsc#1228493).\n- CVE-2024-42107: ice: Do not process extts if PTP is disabled (bsc#1228494).\n- CVE-2024-42109: netfilter: nf_tables: unconditionall (bsc#1228505).\n- CVE-2024-42110: net: ntb_netdev: Move ntb_netdev_rx_handler() to call netif_rx() from __netif_rx() (bsc#1228501).\n- CVE-2024-42113: net: txgbe: initialize num_q_vectors for MSI/INTx interrupts (bsc#1228568).\n- CVE-2024-42122: drm/amd/display: Add NULL pointer check for kzalloc (bsc#1228591).\n- CVE-2024-42124: scsi: qedf: Make qedf_execute_tmf() non-preemptible (bsc#1228705).\n- CVE-2024-42138: mlxsw: core_linecards: Fix double memory deallocation in case of invalid INI file (bsc#1228500).\n- CVE-2024-42139: ice: Fix improper extts handling (bsc#1228503).\n- CVE-2024-42142: net/mlx5: E-switch, Create ingress ACL when needed (bsc#1228491).\n- CVE-2024-42145: IB/core: Implement a limit on UMAD receive List (bsc#1228743).\n- CVE-2024-42148: bnx2x: Fix multiple UBSAN array-index-out-of-bounds (bsc#1228487).\n- CVE-2024-42155: s390/pkey: Wipe copies of protected- and secure-keys (bsc#1228733).\n- CVE-2024-42156: s390/pkey: Wipe copies of clear-key structures on failure (bsc#1228722).\n- CVE-2024-42157: s390/pkey: Wipe sensitive data on failure (bsc#1228727 CVE-2024-42157 git-fixes).\n- CVE-2024-42158: s390/pkey: Use kfree_sensitive() to fix Coccinelle warnings (bsc#1228720).\n- CVE-2024-42159: scsi: mpi3mr: sanitise num_phys (bsc#1228754).\n- CVE-2024-42161: bpf: avoid uninitialized value in BPF_CORE_READ_BITFIELD (bsc#1228756).\n- CVE-2024-42162: gve: Account for stopped queues when reading NIC stats (bsc#1228706).\n- CVE-2024-42224: net: dsa: mv88e6xxx: Correct check for empty list (bsc#1228723).\n- CVE-2024-42241: mm/shmem: disable PMD-sized page cache if needed (bsc#1228986).\n- CVE-2024-42245: Revert \"sched/fair: Make sure to try to detach at least one movable task\" (bsc#1228978).\n- CVE-2024-42246: net, sunrpc: Remap EPERM in case of connection failure in xs_tcp_setup_socket (bsc#1228989).\n- CVE-2024-42247: wireguard: allowedips: avoid unaligned 64-bit memory accesses (bsc#1228988).\n- CVE-2024-42268: net/mlx5: Fix missing lock on sync reset reload (bsc#1229391).\n- CVE-2024-42269: netfilter: iptables: Fix potential null-ptr-deref in ip6table_nat_table_init(). (bsc#1229402).\n- CVE-2024-42270: netfilter: iptables: Fix null-ptr-deref in iptable_nat_table_init(). (bsc#1229404).\n- CVE-2024-42277: iommu: sprd: Avoid NULL deref in sprd_iommu_hw_en (bsc#1229409).\n- CVE-2024-42281: bpf: Fix a segment issue when downgrading gso_size (bsc#1229386).\n- CVE-2024-42283: net: nexthop: Initialize all fields in dumped nexthops (bsc#1229383)\n- CVE-2024-42284: tipc: Return non-zero value from tipc_udp_addr2str() on error (bsc#1229382)\n- CVE-2024-42290: irqchip/imx-irqsteer: Handle runtime power management correctly (bsc#1229379).\n- CVE-2024-42291: ice: Add a per-VF limit on number of FDIR filters (bsc#1229374).\n- CVE-2024-42295: nilfs2: handle inconsistent state in nilfs_btnode_create_block() (bsc#1229370).\n- CVE-2024-42301: dev/parport: fix the array out-of-bounds risk (bsc#1229407).\n- CVE-2024-42308: Update DRM patch reference (bsc#1229411)\n- CVE-2024-42312: sysctl: always initialize i_uid/i_gid (bsc#1229357)\n- CVE-2024-42316: mm/mglru: fix div-by-zero in vmpressure_calc_level()  (bsc#1229353).\n- CVE-2024-42318: landlock: Do not lose track of restrictions on cred_transfer (bsc#1229351).\n- CVE-2024-42322: ipvs: properly dereference pe in ip_vs_add_service (bsc#1229347)\n- CVE-2024-43821: scsi: lpfc: Fix a possible null pointer dereference (bsc#1229315).\n- CVE-2024-43831: media: mediatek: vcodec: Handle invalid decoder vsi (bsc#1229309).\n- CVE-2024-43834: xdp: fix invalid wait context of page_pool_destroy() (bsc#1229314)\n- CVE-2024-43837: bpf: Fix updating attached freplace prog in prog_array map (bsc#1229297).\n- CVE-2024-43839: bna: adjust 'name' buf size of bna_tcb and bna_ccb structures (bsc#1229301).\n- CVE-2024-43850: soc: qcom: icc-bwmon: Fix refcount imbalance seen during bwmon_remove (bsc#1229316).\n- CVE-2024-43854: block: initialize integrity buffer to zero before writing it to media (bsc#1229345)\n- CVE-2024-43855: md: fix deadlock between mddev_suspend and flush bio (bsc#1229342).\n- CVE-2024-43864: net/mlx5e: Fix CT entry update leaks of modify header context (bsc#1229496).\n- CVE-2024-43866: net/mlx5: Always drain health in shutdown callback (bsc#1229495).\n- CVE-2024-43880: kabi: lib: objagg: Put back removed metod in struct objagg_ops (bsc#1229481).\n- CVE-2024-43882: Fixed ToCToU between perm check and set-uid/gid usage. (bsc#1229503)\n- CVE-2024-43899: drm/amd/display: Fix null pointer deref in dcn20_resource.c (bsc#1229754).\n- CVE-2024-43911: wifi: mac80211: fix NULL dereference at band check in starting tx ba session  (bsc#1229827).\n\nAdditional CVEs were previously fixed and are only mentioned in the metadata.\n\nThe following non-security bugs were fixed:\n\n- ACPI/NUMA: Apply SRAT proximity domain to entire CFMWS window (git-fixes).\n- ACPI: SBS: manage alarm sysfs attribute through psy core (stable-fixes).\n- ACPI: battery: create alarm sysfs attribute atomically (stable-fixes).\n- ACPI: processor_idle: use raw_safe_halt() in acpi_idle_play_dead() (git-fixes).\n- ALSA: hda/hdmi: Yet more pin fix for HP EliteDesk 800 G4 (stable-fixes).\n- ALSA: hda/hdmi: Yet more pin fix for HP EliteDesk 800 G4 (stable-fixes).\n- ALSA: hda/realtek - FIxed ALC285 headphone no sound (stable-fixes).\n- ALSA: hda/realtek - Fixed ALC256 headphone no sound (stable-fixes).\n- ALSA: hda/realtek: Add Framework Laptop 13 (Intel Core Ultra) to quirks (stable-fixes).\n- ALSA: hda/realtek: Add Framework Laptop 13 (Intel Core Ultra) to quirks (stable-fixes).\n- ALSA: hda/realtek: Add quirk for Acer Aspire E5-574G (stable-fixes).\n- ALSA: hda/realtek: Add support for new HP G12 laptops (stable-fixes).\n- ALSA: hda/realtek: Enable mute/micmute LEDs on HP Laptop 14-ey0xxx (stable-fixes).\n- ALSA: hda/realtek: Fix noise from speakers on Lenovo IdeaPad 3 15IAU7 (git-fixes).\n- ALSA: hda/realtek: Fix the speaker output on Samsung Galaxy Book3 Ultra (stable-fixes).\n- ALSA: hda/realtek: Implement sound init sequence for Samsung Galaxy Book3 Pro 360 (stable-fixes).\n- ALSA: hda/realtek: support HP Pavilion Aero 13-bg0xxx Mute LED (stable-fixes).\n- ALSA: hda/tas2781: Use correct endian conversion (git-fixes).\n- ALSA: hda/tas2781: fix wrong calibrated data order (git-fixes).\n- ALSA: hda: Add HP MP9 G4 Retail System AMS to force connect list (stable-fixes).\n- ALSA: hda: Add HP MP9 G4 Retail System AMS to force connect list (stable-fixes).\n- ALSA: hda: Conditionally use snooping for AMD HDMI (git-fixes).\n- ALSA: hda: conexant: Fix headset auto detect fail in the polling mode (git-fixes).\n- ALSA: line6: Fix racy access to midibuf (stable-fixes).\n- ALSA: line6: Fix racy access to midibuf (stable-fixes).\n- ALSA: seq: Skip event type filtering for UMP events (git-fixes).\n- ALSA: seq: ump: Explicitly reset RPN with Null RPN (stable-fixes).\n- ALSA: seq: ump: Optimize conversions from SysEx to UMP (git-fixes).\n- ALSA: seq: ump: Transmit RPN/NRPN message at each MSB/LSB data reception (stable-fixes).\n- ALSA: seq: ump: Use the common RPN/bank conversion context (stable-fixes).\n- ALSA: timer: Relax start tick time check for slave timer elements (git-fixes).\n- ALSA: ump: Explicitly reset RPN with Null RPN (stable-fixes).\n- ALSA: ump: Transmit RPN/NRPN message at each MSB/LSB data reception (stable-fixes).\n- ALSA: usb-audio: Add delay quirk for VIVO USB-C-XE710 HEADSET (stable-fixes).\n- ALSA: usb-audio: Correct surround channels in UAC1 channel map (git-fixes).\n- ALSA: usb-audio: Re-add ScratchAmp quirk entries (git-fixes).\n- ALSA: usb-audio: Re-add ScratchAmp quirk entries (git-fixes).\n- ALSA: usb-audio: Support Yamaha P-125 quirk entry (stable-fixes).\n- ALSA: usb: Fix UBSAN warning in parse_audio_unit() (stable-fixes).\n- ASoC: SOF: Intel: hda-dsp: Make sure that no irq handler is pending before suspend (stable-fixes).\n- ASoC: SOF: Remove libraries from topology lookups (git-fixes).\n- ASoC: SOF: Remove libraries from topology lookups (git-fixes).\n- ASoC: SOF: amd: Fix for acp init sequence (git-fixes).\n- ASoC: SOF: ipc4: check return value of snd_sof_ipc_msg_data (stable-fixes).\n- ASoC: SOF: mediatek: Add missing board compatible (stable-fixes).\n- ASoC: allow module autoloading for table board_ids (stable-fixes).\n- ASoC: allow module autoloading for table db1200_pids (stable-fixes).\n- ASoC: amd: acp: fix module autoloading (git-fixes).\n- ASoC: amd: yc: Add quirk entry for OMEN by HP Gaming Laptop 16-n0xxx (bsc#1227182).\n- ASoC: amd: yc: Support mic on HP 14-em0002la (stable-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: Support mic on Lenovo Thinkpad E14 Gen 6 (stable-fixes).\n- ASoC: codecs: wcd938x-sdw: Correct Soundwire ports mask (git-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: wsa881x: Correct Soundwire ports mask (git-fixes).\n- ASoC: codecs: wsa883x: 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: codecs: wsa884x: Correct Soundwire ports mask (git-fixes).\n- ASoC: cs35l45: Checks index of cs35l45_irqs[] (stable-fixes).\n- ASoC: cs35l56: Handle OTP read latency over SoundWire (stable-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: 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: fsl_micfil: Expand the range of FIFO watermark mask (stable-fixes).\n- ASoC: mediatek: mt8188: Mark AFE_DAC_CON0 register as volatile (stable-fixes).\n- ASoC: meson: axg-fifo: fix irq scheduling issue with PREEMPT_RT (git-fixes).\n- ASoC: meson: axg-fifo: fix irq scheduling issue with PREEMPT_RT (git-fixes).\n- ASoC: nau8822: Lower debug print priority (stable-fixes).\n- ASoC: nau8822: Lower debug print priority (stable-fixes).\n- Bluetooth: Add device 13d3:3572 IMC Networks Bluetooth Radio (stable-fixes).\n- Bluetooth: Fix usage of __hci_cmd_sync_status (git-fixes).\n- Bluetooth: L2CAP: Fix deadlock (git-fixes).\n- Bluetooth: MGMT: Add error handling to pair_device() (git-fixes).\n- Bluetooth: SMP: Fix assumption of Central always being Initiator (git-fixes).\n- Bluetooth: bnep: Fix out-of-bound access (stable-fixes).\n- Bluetooth: btintel: Fail setup on error (git-fixes).\n- Bluetooth: btnxpuart: Shutdown timer and prevent rearming when driver unloading (stable-fixes).\n- Bluetooth: btusb: Add RTL8852BE device 0489:e125 to device tables (stable-fixes).\n- Bluetooth: btusb: Add Realtek RTL8852BE support ID 0x13d3:0x3591 (stable-fixes).\n- Bluetooth: hci_conn: Check non NULL function before calling for HFP offload (stable-fixes).\n- Bluetooth: hci_core: Fix LE quote calculation (git-fixes).\n- Bluetooth: hci_core: Fix not handling hibernation actions (git-fixes).\n- Bluetooth: hci_sync: Fix suspending with wrong filter policy (git-fixes).\n- Bluetooth: hci_sync: avoid dup filtering when passive scanning with adv monitor (git-fixes).\n- Bluetooth: l2cap: always unlock channel in l2cap_conless_channel() (git-fixes).\n- Drop libata patch that caused a regression (bsc#1229054)\n- HID: wacom: Defer calculation of resolution until resolution_code is known (git-fixes).\n- Input: MT - limit max slots (stable-fixes).\n- Input: i8042 - add Fujitsu Lifebook E756 to i8042 quirk table (bsc#1229056).\n- Input: i8042 - add forcenorestore quirk to leave controller untouched even on s3 (stable-fixes).\n- Input: i8042 - use new forcenorestore quirk to replace old buggy quirk combination (stable-fixes).\n- KVM: Always flush async #PF workqueue when vCPU is being destroyed (git-fixes).\n- KVM: Make KVM_MEM_GUEST_MEMFD mutually exclusive with KVM_MEM_READONLY (git-fixes).\n- KVM: PPC: Book3S HV: Fix the set_one_reg for MMCR3 (bsc#1194869).\n- KVM: PPC: Book3S HV: Handle pending exceptions on guest entry with MSR_EE (bsc#1215199).\n- KVM: Protect vcpu-\u003epid dereference via debugfs with RCU (git-fixes).\n- KVM: Reject overly excessive IDs in KVM_CREATE_VCPU (git-fixes).\n- KVM: Stop processing *all* memslots when \"null\" mmu_notifier handler is found (git-fixes).\n- KVM: VMX: Move posted interrupt descriptor out of VMX code (git-fixes).\n- KVM: VMX: Split out the non-virtualization part of vmx_interrupt_blocked() (git-fixes).\n- KVM: VMX: Switch __vmx_exit() and kvm_x86_vendor_exit() in vmx_exit() (git-fixes).\n- KVM: arm64: AArch32: Fix spurious trapping of conditional instructions (git-fixes).\n- KVM: arm64: Add missing memory barriers when switching to pKVM's hyp pgd (git-fixes).\n- KVM: arm64: Allow AArch32 PSTATE.M to be restored as System mode (git-fixes).\n- KVM: arm64: Fix AArch32 register narrowing on userspace write (git-fixes).\n- KVM: arm64: Fix __pkvm_init_switch_pgd call ABI (git-fixes).\n- KVM: arm64: Fix clobbered ELR in sync abort/SError (git-fixes)\n- KVM: arm64: GICv4: Do not perform a map to a mapped vLPI (git-fixes).\n- KVM: arm64: timers: Correctly handle TGE flip with CNTPOFF_EL2 (git-fixes).\n- KVM: arm64: timers: Fix resource leaks in kvm_timer_hyp_init() (git-fixes).\n- KVM: arm64: vgic-its: Test for valid IRQ in its_sync_lpi_pending_table() (git-fixes).\n- KVM: arm64: vgic-its: Test for valid IRQ in MOVALL handler (git-fixes).\n- KVM: arm64: vgic-v2: Use cpuid from userspace as vcpu_id (git-fixes).\n- KVM: arm64: vgic-v4: Restore pending state on host userspace write (git-fixes).\n- KVM: arm64: vgic: Add a non-locking primitive for kvm_vgic_vcpu_destroy() (git-fixes).\n- KVM: arm64: vgic: Force vcpu vgic teardown on vcpu destroy (git-fixes).\n- KVM: arm64: vgic: Simplify kvm_vgic_destroy() (git-fixes).\n- KVM: fix kvm_mmu_memory_cache allocation warning (git-fixes).\n- KVM: nVMX: Add a helper to get highest pending from Posted Interrupt vector (git-fixes).\n- KVM: nVMX: Check for pending posted interrupts when looking for nested events (git-fixes).\n- KVM: nVMX: Request immediate exit iff pending nested event needs injection (git-fixes).\n- KVM: s390: fix LPSWEY handling (bsc#1227634 git-fixes).\n- KVM: s390: fix validity interception issue when gisa is switched off (git-fixes bsc#1229167).\n- KVM: x86/mmu: Bug the VM if KVM tries to split a !hugepage SPTE (git-fixes).\n- KVM: x86: Limit check IDs for KVM_SET_BOOT_CPU_ID (git-fixes).\n- Move upstreamed powerpc patches into sorted section\n- Move upstreamed sound patches into sorted section\n- Moved upstreamed ASoC patch into sorted section\n- NFSD: Support write delegations in LAYOUTGET (git-fixes).\n- NFSv4.1 another fix for EXCHGID4_FLAG_USE_PNFS_DS for DS server (git-fixes).\n- PCI: Add Edimax Vendor ID to pci_ids.h (stable-fixes).\n- PCI: hv: Return zero, not garbage, when reading PCI_INTERRUPT_PIN (git-fixes).\n- PCI: loongson: Enable MSI in LS7A Root Complex (stable-fixes).\n- RDMA/cache: Release GID table even if leak is detected (git-fixes)\n- RDMA/device: Return error earlier if port in not valid (git-fixes)\n- RDMA/hns: Check atomic wr length (git-fixes)\n- RDMA/hns: Fix insufficient extend DB for VFs. (git-fixes)\n- RDMA/hns: Fix mbx timing out before CMD execution is completed (git-fixes)\n- RDMA/hns: Fix missing pagesize and alignment check in FRMR (git-fixes)\n- RDMA/hns: Fix shift-out-bounds when max_inline_data is 0 (git-fixes)\n- RDMA/hns: Fix soft lockup under heavy CEQE load (git-fixes)\n- RDMA/hns: Fix undifined behavior caused by invalid max_sge (git-fixes)\n- RDMA/hns: Fix unmatch exception handling when init eq table fails (git-fixes)\n- RDMA/iwcm: Fix a use-after-free related to destroying CM IDs (git-fixes)\n- RDMA/mana_ib: Use virtual address in dma regions for MRs (git-fixes).\n- RDMA/mlx4: Fix truncated output warning in alias_GUID.c (git-fixes)\n- RDMA/mlx4: Fix truncated output warning in mad.c (git-fixes)\n- RDMA/mlx5: Set mkeys for dmabuf at PAGE_SIZE (git-fixes)\n- RDMA/rxe: Do not set BTH_ACK_MASK for UC or UD QPs (git-fixes)\n- RDMA: Fix netdev tracker in ib_device_set_netdev (git-fixes)\n- Revert \"ALSA: firewire-lib: obsolete workqueue for period update\" (bsc#1208783).\n- Revert \"ALSA: firewire-lib: operate for period elapse event in process context\" (bsc#1208783).\n- Revert \"KVM: Prevent module exit until all VMs are freed\" (git-fixes).\n- Revert \"Revert \"md/raid5: Wait for MD_SB_CHANGE_PENDING in raid5d\"\" (git-fixes).\n- Revert \"md/raid5: Wait for MD_SB_CHANGE_PENDING in raid5d\" (git-fixes).\n- Revert \"misc: fastrpc: Restrict untrusted app to attach to privileged PD\" (git-fixes).\n- Revert \"usb: gadget: uvc: cleanup request when not in correct state\" (stable-fixes).\n- Revert \"usb: typec: tcpm: clear pd_event queue in PORT_RESET\" (git-fixes).\n- SUNRPC: Fix a race to wake a sync task (git-fixes).\n- SUNRPC: add a missing rpc_stat for TCP TLS (git-fixes).\n- Squashfs: fix variable overflow triggered by sysbot (git-fixes).\n- USB: serial: debug: do not echo input by default (stable-fixes).\n- Update config files. Disable vdpa drivers for Alibaba ENI and SolidNET (jsc#PED-8954, bsc#1227834)\n- Update config files. Disable CONFIG_KFENCE on ppc64le (bsc#1226920)\n- Update patch references for ASoC regression fixes (bsc#1229045 bsc#1229046)\n- afs: fix __afs_break_callback() / afs_drop_open_mmap() race (git-fixes).\n- apparmor: unpack transition table if dfa is not present (bsc#1226031).\n- arm64: ACPI: NUMA: initialize all values of acpi_early_node_map to (git-fixes)\n- arm64: Add Neoverse-V2 part (git-fixes)\n- arm64: Fix KASAN random tag seed initialization (git-fixes)\n- arm64: armv8_deprecated: Fix warning in isndep cpuhp starting process (git-fixes)\n- arm64: barrier: Restore spec_bar() macro (git-fixes)\n- arm64: cputype: Add Cortex-A720 definitions (git-fixes)\n- arm64: cputype: Add Cortex-A725 definitions (git-fixes)\n- arm64: cputype: Add Cortex-X1C definitions (git-fixes)\n- arm64: cputype: Add Cortex-X3 definitions (git-fixes)\n- arm64: cputype: Add Cortex-X4 definitions (git-fixes)\n- arm64: cputype: Add Cortex-X925 definitions (git-fixes)\n- arm64: cputype: Add Neoverse-V3 definitions (git-fixes)\n- arm64: dts: imx8mp: Add NPU Node (git-fixes)\n- arm64: dts: imx8mp: Fix pgc vpu locations (git-fixes)\n- arm64: dts: imx8mp: Fix pgc_mlmix location (git-fixes)\n- arm64: dts: imx8mp: add HDMI power-domains (git-fixes)\n- arm64: errata: Expand speculative SSBS workaround (again) (git-fixes)\n- arm64: errata: Expand speculative SSBS workaround (git-fixes)\n- arm64: errata: Unify speculative SSBS errata logic (git-fixes). Update config files.\n- arm64: jump_label: Ensure patched jump_labels are visible to all CPUs (git-fixes)\n- ata: libata-scsi: Do not overwrite valid sense data when CK_COND=1 (stable-fixes).\n- ata: libata-scsi: Honor the D_SENSE bit for CK_COND=1 and no error (stable-fixes).\n- blacklist.conf: Add libata upstream revert entry (bsc#1229054)\n- bnxt_re: Fix imm_data endianness (git-fixes)\n- bpf, arm64: Fix trampoline for BPF_TRAMP_F_CALL_ORIG (git-fixes)\n- bpf, lpm: Fix check prefixlen before walking trie (git-fixes).\n- bpf/tests: Remove duplicate JSGT tests (git-fixes).\n- bpf: Add crosstask check to __bpf_get_stack (git-fixes).\n- bpf: Detect IP == ksym.end as part of BPF program (git-fixes).\n- bpf: Ensure proper register state printing for cond jumps (git-fixes).\n- bpf: Fix a few selftest failures due to llvm18 change (git-fixes).\n- bpf: Fix a kernel verifier crash in stacksafe() (bsc#1225903).\n- bpf: Fix check_stack_write_fixed_off() to correctly spill imm (git-fixes).\n- bpf: Fix kfunc callback register type handling (git-fixes).\n- bpf: Fix prog_array_map_poke_run map poke update (git-fixes).\n- bpf: Fix unnecessary -EBUSY from htab_lock_bucket (git-fixes).\n- bpf: Mark bpf_spin_{lock,unlock}() helpers with notrace correctly (git-fixes).\n- bpf: Remove unnecessary wait from bpf_map_copy_value() (git-fixes).\n- bpf: Set uattr-\u003ebatch.count as zero before batched update or deletion (git-fixes).\n- bpf: do not infer PTR_TO_CTX for programs with unnamed context type (git-fixes).\n- bpf: enforce precision of R0 on callback return (git-fixes).\n- bpf: extract bpf_ctx_convert_map logic and make it more reusable (git-fixes).\n- bpf: fix control-flow graph checking in privileged mode (git-fixes).\n- bpf: handle bpf_user_pt_regs_t typedef explicitly for PTR_TO_CTX global arg (git-fixes).\n- bpf: hardcode BPF_PROG_PACK_SIZE to 2MB * num_possible_nodes() (git-fixes).\n- bpf: kprobe: remove unused declaring of bpf_kprobe_override (git-fixes).\n- bpf: simplify btf_get_prog_ctx_type() into btf_is_prog_ctx_type() (git-fixes).\n- bpftool: Align output skeleton ELF code (git-fixes).\n- bpftool: Fix -Wcast-qual warning (git-fixes).\n- bpftool: Silence build warning about calloc() (git-fixes).\n- bpftool: mark orphaned programs during prog show (git-fixes).\n- btrfs: add a btrfs_finish_ordered_extent helper (git-fixes).\n- btrfs: add a is_data_bbio helper (git-fixes).\n- btrfs: add an ordered_extent pointer to struct btrfs_bio (git-fixes).\n- btrfs: copy dir permission and time when creating a stub subvolume (bsc#1228321).\n- btrfs: ensure fast fsync waits for ordered extents after a write failure (git-fixes).\n- btrfs: factor out a btrfs_queue_ordered_fn helper (git-fixes).\n- btrfs: factor out a can_finish_ordered_extent helper (git-fixes).\n- btrfs: fix corruption after buffer fault in during direct IO append write (git-fixes).\n- btrfs: fix double inode unlock for direct IO sync writes (git-fixes).\n- btrfs: fix extent map use-after-free when adding pages to compressed bio (git-fixes).\n- btrfs: fix leak of qgroup extent records after transaction abort (git-fixes).\n- btrfs: fix ordered extent split error handling in btrfs_dio_submit_io (git-fixes).\n- btrfs: limit write bios to a single ordered extent (git-fixes).\n- btrfs: make btrfs_finish_ordered_extent() return void (git-fixes).\n- btrfs: merge the two calls to btrfs_add_ordered_extent in run_delalloc_nocow (git-fixes).\n- btrfs: open code btrfs_bio_end_io in btrfs_dio_submit_io (git-fixes).\n- btrfs: open code end_extent_writepage in end_bio_extent_writepage (git-fixes).\n- btrfs: pass a btrfs_inode to btrfs_fdatawrite_range() (git-fixes).\n- btrfs: pass a btrfs_inode to btrfs_wait_ordered_range() (git-fixes).\n- btrfs: pass an ordered_extent to btrfs_reloc_clone_csums (git-fixes).\n- btrfs: pass an ordered_extent to btrfs_submit_compressed_write (git-fixes).\n- btrfs: remove btrfs_add_ordered_extent (git-fixes).\n- btrfs: rename err to ret in btrfs_direct_write() (git-fixes).\n- btrfs: uninline some static inline helpers from tree-log.h (git-fixes).\n- btrfs: use a btrfs_inode in the log context (struct btrfs_log_ctx) (git-fixes).\n- btrfs: use a btrfs_inode local variable at btrfs_sync_file() (git-fixes).\n- btrfs: use bbio-\u003eordered in btrfs_csum_one_bio (git-fixes).\n- btrfs: use btrfs_finish_ordered_extent to complete buffered writes (git-fixes).\n- btrfs: use btrfs_finish_ordered_extent to complete compressed writes (git-fixes).\n- btrfs: use btrfs_finish_ordered_extent to complete direct writes (git-fixes).\n- btrfs: use irq safe locking when running and adding delayed iputs (git-fixes).\n- cachefiles, erofs: Fix NULL deref in when cachefiles is not doing ondemand-mode (bsc#1229245).\n- cachefiles: add missing lock protection when polling (bsc#1229256).\n- cachefiles: add restore command to recover inflight ondemand read requests (bsc#1229244).\n- cachefiles: add spin_lock for cachefiles_ondemand_info (bsc#1229249).\n- cachefiles: cancel all requests for the object that is being dropped (bsc#1229255).\n- cachefiles: defer exposing anon_fd until after copy_to_user() succeeds (bsc#1229251).\n- cachefiles: extract ondemand info field from cachefiles_object (bsc#1229240).\n- cachefiles: fix slab-use-after-free in cachefiles_ondemand_daemon_read() (bsc#1229247).\n- cachefiles: fix slab-use-after-free in cachefiles_ondemand_get_fd() (bsc#1229246).\n- cachefiles: introduce object ondemand state (bsc#1229239).\n- cachefiles: make on-demand read killable (bsc#1229252).\n- cachefiles: narrow the scope of triggering EPOLLIN events in ondemand mode (bsc#1229243).\n- cachefiles: never get a new anonymous fd if ondemand_id is valid (bsc#1229250).\n- cachefiles: propagate errors from vfs_getxattr() to avoid infinite loop (bsc#1229253).\n- cachefiles: remove err_put_fd label in cachefiles_ondemand_daemon_read() (bsc#1229248).\n- cachefiles: resend an open request if the read request's object is closed (bsc#1229241).\n- cachefiles: stop sending new request when dropping object (bsc#1229254).\n- can: mcp251xfd: tef: prepare to workaround broken TEF FIFO tail index erratum (stable-fixes).\n- can: mcp251xfd: tef: update workaround for erratum DS80000789E 6 of mcp2518fd (stable-fixes).\n- ceph: periodically flush the cap releases (bsc#1230056).\n- cgroup/cpuset: Prevent UAF in proc_cpuset_show() (bsc#1228801).\n- cgroup: Add annotation for holding namespace_sem in current_cgns_cgroup_from_root() (bsc#1222254).\n- cgroup: Eliminate the need for cgroup_mutex in proc_cgroup_show() (bsc#1222254).\n- cgroup: Make operations on the cgroup root_list RCU safe (bsc#1222254).\n- cgroup: Remove unnecessary list_empty() (bsc#1222254).\n- cgroup: preserve KABI of cgroup_root (bsc#1222254).\n- char: xillybus: Check USB endpoints when probing device (git-fixes).\n- char: xillybus: Do not destroy workqueue from work item running on it (stable-fixes).\n- char: xillybus: Refine workqueue handling (git-fixes).\n- clk: en7523: fix rate divider for slic and spi clocks (git-fixes).\n- clk: qcom: Park shared RCGs upon registration (git-fixes).\n- clk: qcom: camcc-sc7280: Add parent dependency to all camera GDSCs (git-fixes).\n- clk: qcom: gcc-sa8775p: Update the GDSC wait_val fields and flags (git-fixes).\n- clk: qcom: gcc-sc7280: Update force mem core bit for UFS ICE clock (git-fixes).\n- clk: qcom: gpucc-sa8775p: Park RCG's clk source at XO during disable (git-fixes).\n- clk: qcom: gpucc-sa8775p: Remove the CLK_IS_CRITICAL and ALWAYS_ON flags (git-fixes).\n- clk: qcom: gpucc-sa8775p: Update wait_val fields for GPU GDSC's (git-fixes).\n- clk: qcom: gpucc-sm8350: Park RCG's clk source at XO during disable (git-fixes).\n- clk: qcom: kpss-xcc: Return of_clk_add_hw_provider to transfer the error (git-fixes).\n- clk: visconti: Add bounds-checking coverage for struct visconti_pll_provider (stable-fixes).\n- clocksource/drivers/sh_cmt: Address race condition for clock events (stable-fixes).\n- cpu/SMT: Enable SMT only if a core is online (bsc#1214285 bsc#1205462 ltc#200161 ltc#200588 git-fixes).\n- cxl/region: Move cxl_dpa_to_region() work to the region driver (bsc#1228472)\n- dev/parport: fix the array out-of-bounds risk (stable-fixes).\n- device property: Add cleanup.h based fwnode_handle_put() scope based cleanup (stable-fixes).\n- dmaengine: dw: Add memory bus width verification (git-fixes).\n- dmaengine: dw: Add peripheral bus width verification (git-fixes).\n- docs: KVM: Fix register ID of SPSR_FIQ (git-fixes).\n- driver core: Fix uevent_show() vs driver detach race (git-fixes).\n- drm/admgpu: fix dereferencing null pointer context (stable-fixes).\n- drm/amd/display: Add delay to improve LTTPR UHBR interop (stable-fixes).\n- drm/amd/display: Add null checker before passing variables (stable-fixes).\n- drm/amd/display: Adjust cursor position (git-fixes).\n- drm/amd/display: Check for NULL pointer (stable-fixes).\n- drm/amd/display: Skip Recompute DSC Params if no Stream on Link (stable-fixes).\n- drm/amd/display: avoid using null object of framebuffer (git-fixes).\n- drm/amd/display: fix cursor offset on rotation 180 (git-fixes).\n- drm/amd/display: fix s2idle entry for DCN3.5+ (stable-fixes).\n- drm/amd/pm: Fix the null pointer dereference for vega10_hwmgr (stable-fixes).\n- drm/amdgpu/jpeg2: properly set atomics vmid field (stable-fixes).\n- drm/amdgpu/jpeg4: properly set atomics vmid field (stable-fixes).\n- drm/amdgpu/pm: Fix the null pointer dereference for smu7 (stable-fixes).\n- drm/amdgpu/pm: Fix the null pointer dereference in apply_state_adjust_rules (stable-fixes).\n- drm/amdgpu/pm: Fix the param type of set_power_profile_mode (stable-fixes).\n- drm/amdgpu/sdma5.2: Update wptr registers as well as doorbell (stable-fixes).\n- drm/amdgpu/sdma5.2: limit wptr workaround to sdma 5.2.1 (git-fixes).\n- drm/amdgpu: Actually check flags for all context ops (stable-fixes).\n- drm/amdgpu: Add lock around VF RLCG interface (stable-fixes).\n- drm/amdgpu: Fix the null pointer dereference to ras_manager (stable-fixes).\n- drm/amdgpu: Forward soft recovery errors to userspace (stable-fixes).\n- drm/amdgpu: Validate TA binary size (stable-fixes).\n- drm/amdgpu: fix dereference null return value for the function amdgpu_vm_pt_parent (stable-fixes).\n- drm/amdgpu: fix potential resource leak warning (stable-fixes).\n- drm/amdgpu: reset vm state machine after gpu reset(vram lost) (stable-fixes).\n- drm/bridge: analogix_dp: properly handle zero sized AUX transactions (stable-fixes).\n- drm/client: fix null pointer dereference in drm_client_modeset_probe (git-fixes).\n- drm/dp_mst: Skip CSN if topology probing is not done yet (stable-fixes).\n- drm/etnaviv: do not block scheduler when GPU is still active (stable-fixes).\n- drm/i915/dsi: Make Lenovo Yoga Tab 3 X90F DMI match less strict (git-fixes).\n- drm/i915/gem: Adjust vma offset for framebuffer mmap offset (stable-fixes).\n- drm/i915/gem: Fix Virtual Memory mapping boundaries calculation (git-fixes).\n- drm/i915/hdcp: Fix HDCP2_STREAM_STATUS macro (git-fixes).\n- drm/i915: Fix possible int overflow in skl_ddi_calculate_wrpll() (git-fixes).\n- drm/lima: set gp bus_stop bit before hard reset (stable-fixes).\n- drm/mediatek/dp: Fix spurious kfree() (git-fixes).\n- drm/msm/dp: fix the max supported bpp logic (git-fixes).\n- drm/msm/dp: reset the link phy params before link training (git-fixes).\n- drm/msm/dpu: capture snapshot on the first commit_done timeout (stable-fixes).\n- drm/msm/dpu: cleanup FB if dpu_format_populate_layout fails (git-fixes).\n- drm/msm/dpu: do not play tricks with debug macros (git-fixes).\n- drm/msm/dpu: drop MSM_ENC_VBLANK support (stable-fixes).\n- drm/msm/dpu: move dpu_encoder's connector assignment to atomic_enable() (git-fixes).\n- drm/msm/dpu: split dpu_encoder_wait_for_event into two functions (stable-fixes).\n- drm/msm/dpu: take plane rotation into account for wide planes (git-fixes).\n- drm/msm/dpu: try multirect based on mdp clock limits (stable-fixes).\n- drm/msm/dpu: use drmm-managed allocation for dpu_encoder_phys (stable-fixes).\n- drm/msm/mdss: Rename path references to mdp_path (stable-fixes).\n- drm/msm/mdss: switch mdss to use devm_of_icc_get() (stable-fixes).\n- drm/msm: Reduce fallout of fence signaling vs reclaim hangs (stable-fixes).\n- drm/nouveau: prime: fix refcount underflow (git-fixes).\n- drm/panel: nt36523: Set 120Hz fps for xiaomi,elish panels (stable-fixes).\n- drm/radeon/evergreen_cs: Clean up errors in evergreen_cs.c (bsc#1229024).\n- drm/radeon: Remove __counted_by from StateArray.states[] (git-fixes).\n- drm/rockchip: vop2: clear afbc en and transform bit for cluster window at linear mode (stable-fixes).\n- drm/virtio: Fix type of dma-fence context variable (git-fixes).\n- drm/vmwgfx: Fix a deadlock in dma buf fence polling (git-fixes).\n- drm/vmwgfx: Fix overlay when using Screen Targets (git-fixes).\n- drm/vmwgfx: Fix prime with external buffers (git-fixes).\n- efi/libstub: Zero initialize heap allocated struct screen_info (git-fixes).\n- evm: do not copy up 'security.evm' xattr (git-fixes).\n- firmware: cirrus: cs_dsp: Initialize debugfs_root to invalid (stable-fixes).\n- fs/netfs/fscache_cookie: add missing \"n_accesses\" check (bsc#1229455).\n- fuse: Initialize beyond-EOF page contents before setting uptodate (bsc#1229456).\n- genirq/cpuhotplug, x86/vector: Prevent vector leak during CPU offline (git-fixes).\n- genirq/generic_chip: Make irq_remove_generic_chip() irqdomain aware (git-fixes).\n- genirq/matrix: Exclude managed interrupts in irq_matrix_allocated() (git-fixes).\n- gfs2: setattr_chown: Add missing initialization (git-fixes).\n- gpio: mlxbf3: Support shutdown() function (git-fixes).\n- gpio: prevent potential speculation leaks in gpio_device_get_desc() (stable-fixes).\n- gpio: sysfs: extend the critical section for unregistering sysfs devices (stable-fixes).\n- gss_krb5: Fix the error handling path for crypto_sync_skcipher_setkey (git-fixes).\n- hfs: fix to initialize fields of hfs_inode_info after hfs_alloc_inode() (git-fixes).\n- hwmon: (ltc2992) Avoid division by zero (stable-fixes).\n- hwmon: (ltc2992) Fix memory leak in ltc2992_parse_dt() (git-fixes).\n- hwmon: (pc87360) Bounds check data-\u003einnr usage (stable-fixes).\n- i2c: Fix conditional for substituting empty ACPI functions (stable-fixes).\n- i2c: Use IS_REACHABLE() for substituting empty ACPI functions (git-fixes).\n- i2c: qcom-geni: Add missing clk_disable_unprepare in geni_i2c_runtime_resume (git-fixes).\n- i2c: qcom-geni: Add missing geni_icc_disable in geni_i2c_runtime_resume (git-fixes).\n- i2c: qcom-geni: Add missing geni_icc_disable in geni_i2c_runtime_resume (git-fixes).\n- i2c: riic: avoid potential division by zero (stable-fixes).\n- i2c: smbus: Improve handling of stuck alerts (git-fixes).\n- i2c: smbus: Send alert notifications to all devices if source not found (git-fixes).\n- i2c: stm32f7: Add atomic_xfer method to driver (stable-fixes).\n- i3c: mipi-i3c-hci: Do not unmap region not mapped for transfer (stable-fixes).\n- i3c: mipi-i3c-hci: Remove BUG() when Ring Abort request times out (stable-fixes).\n- i915/perf: Remove code to update PWR_CLK_STATE for gen12 (git-fixes).\n- ice: Fix NULL pointer access, if PF does not support SRIOV_LAG (bsc#1228737).\n- io_uring/advise: support 64-bit lengths (git-fixes).\n- io_uring: Drop per-ctx dummy_ubuf (git-fixes).\n- io_uring: Fix probe of disabled operations (git-fixes).\n- io_uring: fix io_match_task must_hold (git-fixes).\n- io_uring: tighten task exit cancellations (git-fixes).\n- iommu/amd: Convert comma to semicolon (git-fixes).\n- iommu/vt-d: Fix identity map bounds in si_domain_init() (git-fixes).\n- iommufd/device: Fix hwpt at err_unresv in iommufd_device_do_replace() (git-fixes).\n- ip6_tunnel: Fix broken GRO (bsc#1229444).\n- ipv6: sr: fix incorrect unregister order (git-fixes).\n- irqdomain: Fixed unbalanced fwnode get and put (git-fixes).\n- jfs: Fix shift-out-of-bounds in dbDiscardAG (git-fixes).\n- jfs: define xtree root and page independently (git-fixes).\n- jfs: fix null ptr deref in dtInsertEntry (git-fixes).\n- jump_label: Clarify condition in static_key_fast_inc_not_disabled() (git-fixes).\n- jump_label: Fix concurrency issues in static_key_slow_dec() (git-fixes).\n- jump_label: Fix the fix, brown paper bags galore (git-fixes).\n- jump_label: Simplify and clarify static_key_fast_inc_cpus_locked() (git-fixes).\n- kABI fix of: virtio-crypto: handle config changed by work queue (git-fixes).\n- kABI workaround for sound core UMP conversion (stable-fixes).\n- kabi fix for KVM: s390: fix LPSWEY handling (bsc#1227634 git-fixes).\n- kabi fix for SUNRPC: add a missing rpc_stat for TCP TLS (git-fixes).\n- kabi/severities: ignore kABI for FireWire sound local symbols (bsc#1208783)\n- kcov: properly check for softirq context (git-fixes).\n- kernel-binary: generate and install compile_commands.json (bsc#1228971)\n- kernfs: Convert kernfs_path_from_node_locked() from strlcpy() to strscpy() (bsc#1229134).\n- kernfs: fix false-positive WARN(nr_mmapped) in kernfs_drain_open_files (git-fixes).\n- kprobes: Fix to check symbol prefixes correctly (git-fixes).\n- kprobes: Prohibit probing on CFI preamble symbol (git-fixes).\n- kvm: s390: Reject memory region operations for ucontrol VMs (git-fixes bsc#1229168).\n- libbpf: Add missing LIBBPF_API annotation to libbpf_set_memlock_rlim API (git-fixes).\n- libbpf: Apply map_set_def_max_entries() for inner_maps on creation (git-fixes).\n- libbpf: Fix faccessat() usage on Android (git-fixes).\n- libbpf: Use OPTS_SET() macro in bpf_xdp_query() (git-fixes).\n- md-cluster: fix hanging issue while a new disk adding (bsc#1223395).\n- md-cluster: fix hanging issue while a new disk adding (bsc#1223395).\n- md-cluster: fix no recovery job when adding/re-adding a disk (bsc#1223395).\n- md-cluster: fix no recovery job when adding/re-adding a disk (bsc#1223395).\n- md-cluster: keeping kabi compatibility for upstream commit 35a0a409fa26 (bsc#1223395).\n- md/md-bitmap: fix writing non bitmap pages (git-fixes).\n- md/raid1: set max_sectors during early return from choose_slow_rdev() (git-fixes).\n- md/raid1: support read error check (git-fixes).\n- md/raid5: fix deadlock that raid5d() wait for itself to clear MD_SB_CHANGE_PENDING (git-fixes).\n- md/raid5: fix spares errors about rcu usage (git-fixes).\n- md/raid5: recheck if reshape has finished with device_lock held (git-fixes).\n- md: Do not wait for MD_RECOVERY_NEEDED for HOT_REMOVE_DISK ioctl (git-fixes).\n- md: add a mddev_add_trace_msg helper (git-fixes).\n- md: add check for sleepers in md_wakeup_thread() (git-fixes).\n- md: change the return value type of md_write_start to void (git-fixes).\n- md: do not account sync_io if iostats of the disk is disabled (git-fixes).\n- md: do not delete safemode_timer in mddev_suspend (git-fixes).\n- md: factor out a helper exceed_read_errors() to check read_errors (git-fixes).\n- md: fix a suspicious RCU usage warning (git-fixes).\n- media: Revert \"media: dvb-usb: Fix unexpected infinite loop in dvb_usb_read_remote_control()\" (git-fixes).\n- media: amphion: Remove lock in s_ctrl callback (stable-fixes).\n- media: drivers/media/dvb-core: copy user arrays safely (stable-fixes).\n- media: pci: cx23885: check cx23885_vdev_init() return (stable-fixes).\n- media: uvcvideo: Add quirk for invalid dev_sof in Logitech C920 (git-fixes).\n- media: uvcvideo: Disable autosuspend for Insta360 Link (stable-fixes).\n- media: uvcvideo: Fix the bandwdith quirk on USB 3.x (stable-fixes).\n- media: uvcvideo: Ignore empty TS packets (stable-fixes).\n- media: uvcvideo: Quirk for invalid dev_sof in Logitech C922 (stable-fixes).\n- media: xc2028: avoid use-after-free in load_firmware_cb() (stable-fixes).\n- memcg: protect concurrent access to mem_cgroup_idr (git-fixes).\n- memory: stm32-fmc2-ebi: check regmap_read return value (stable-fixes).\n- memory: tegra: Skip SID programming if SID registers are not set (stable-fixes).\n- minmax: add a few more MIN_T/MAX_T users (bsc#1229024).\n- minmax: avoid overly complicated constant expressions in VM code (bsc#1229024).\n- minmax: do not use max() in situations that want a C constant expression (bsc#1229024).\n- minmax: fix up min3() and max3() too (bsc#1229024).\n- minmax: improve macro expansion and type checking (bsc#1229024).\n- minmax: make generic MIN() and MAX() macros available everywhere (bsc#1229024).\n- minmax: simplify and clarify min_t()/max_t() implementation (bsc#1229024).\n- minmax: simplify min()/max()/clamp() implementation (bsc#1229024).\n- mm, kmsan: fix infinite recursion due to RCU critical section (git-fixes).\n- mm: prevent derefencing NULL ptr in pfn_section_valid() (git-fixes).\n- mmc: dw_mmc: allow biu and ciu clocks to defer (git-fixes).\n- mmc: mmc_test: Fix NULL dereference on allocation failure (git-fixes).\n- mmc: mtk-sd: receive cmd8 data when hs400 tuning fail (git-fixes).\n- net/iucv: fix the allocation size of iucv_path_table array (git-fixes bsc#1229451).\n- net/iucv: fix use after free in iucv_sock_close() (bsc#1228973).\n- net/rds: fix possible cp null dereference (git-fixes).\n- net/sched: initialize noop_qdisc owner (git-fixes).\n- net: drop bad gso csum_start and offset in virtio_net_hdr (git-fixes).\n- net: ethernet: mtk_wed: fix use-after-free panic in mtk_wed_setup_tc_block_cb() (git-fixes).\n- net: fix sk_memory_allocated_{add|sub} vs softirqs (bsc#1228757).\n- net: mana: Add support for page sizes other than 4KB on ARM64 (jsc#PED-8491 bsc#1226530).\n- net: mana: Fix RX buf alloc_size alignment and atomic op panic (bsc#1229086).\n- net: mana: Fix doorbell out of order violation and avoid unnecessary doorbell rings (bsc#1229154).\n- net: mana: Fix race of mana_hwc_post_rx_wqe and new hwc response (git-fixes).\n- net: missing check virtio (git-fixes).\n- net: phy: micrel: Fix the KSZ9131 MDI-X status issue (git-fixes).\n- net: phy: realtek: add support for RTL8366S Gigabit PHY (git-fixes).\n- net: usb: qmi_wwan: fix memory leak for not ip packets (git-fixes).\n- net: usb: sr9700: fix uninitialized variable use in sr_mdio_read (git-fixes).\n- netfs, fscache: export fscache_put_volume() and add fscache_try_get_volume() (bsc#1228459 bsc#1228462).\n- nfc: pn533: Add poll mod list filling check (git-fixes).\n- nfs: do not invalidate dentries on transient errors (git-fixes).\n- nfs: expose /proc/net/sunrpc/nfs in net namespaces (git-fixes).\n- nfs: make the rpc_stat per net namespace (git-fixes).\n- nfs: pass explicit offset/count to trace events (git-fixes).\n- nfs: propagate readlink errors in nfs_symlink_filler (git-fixes).\n- nouveau/firmware: use dma non-coherent allocator (git-fixes).\n- nvme-multipath: find NUMA path only for online numa-node (git-fixes).\n- nvme-multipath: implement \"queue-depth\" iopolicy (bsc#1227706).\n- nvme-multipath: prepare for \"queue-depth\" iopolicy (bsc#1227706).\n- nvme-pci: Fix the instructions for disabling power management (git-fixes).\n- nvme-pci: add missing condition check for existence of mapped data (git-fixes).\n- nvme-pci: do not directly handle subsys reset fallout (bsc#1220066).\n- nvme-sysfs: add 'tls_configured_key' sysfs attribute (bsc#1221857).\n- nvme-sysfs: add 'tls_keyring' attribute (bsc#1221857).\n- nvme-tcp: check for invalidated or revoked key (bsc#1221857).\n- nvme-tcp: sanitize TLS key handling (bsc#1221857).\n- nvme: add a newline to the 'tls_key' sysfs attribute (bsc#1221857).\n- nvme: adjust multiples of NVME_CTRL_PAGE_SIZE in offset (git-fixes).\n- nvme: avoid double free special payload (git-fixes).\n- nvme: fix NVME_NS_DEAC may incorrectly identifying the disk as EXT_LBA (git-fixes).\n- nvme: fixup comment for nvme RDMA Provider Type (git-fixes).\n- nvme: split off TLS sysfs attributes into a separate group (bsc#1221857).\n- nvme: tcp: remove unnecessary goto statement (bsc#1221857).\n- nvme_core: scan namespaces asynchronously (bsc#1224105).\n- nvmet-auth: fix nvmet_auth hash error handling (git-fixes).\n- nvmet: always initialize cqe.result (git-fixes).\n- nvmet: do not return 'reserved' for empty TSAS values (git-fixes).\n- nvmet: fix a possible leak when destroy a ctrl during qp establishment (git-fixes).\n- nvmet: make 'tsas' attribute idempotent for RDMA (git-fixes).\n- ocfs2: strict bound check before memcmp in ocfs2_xattr_find_entry() (bsc#1228410).\n- padata: Fix possible divide-by-0 panic in padata_mt_helper() (git-fixes).\n- perf/smmuv3: Enable HiSilicon Erratum 162001900 quirk for HIP08/09 (git-fixes).\n- pinctrl: mediatek: common-v2: Fix broken bias-disable for PULL_PU_PD_RSEL_TYPE (git-fixes).\n- pinctrl: rockchip: correct RK3328 iomux width flag for GPIO2-B pins (git-fixes).\n- pinctrl: single: fix potential NULL dereference in pcs_get_function() (git-fixes).\n- pinctrl: starfive: jh7110: Correct the level trigger configuration of iev register (git-fixes).\n- platform/chrome: cros_ec_proto: Lock device when updating MKBP version (git-fixes).\n- platform/chrome: cros_ec_proto: Lock device when updating MKBP version (git-fixes).\n- platform/surface: aggregator: Fix warning when controller is destroyed in probe (git-fixes).\n- platform/x86/amd/hsmp: Add support for ACPI based probing (jsc#PED-8779).\n- platform/x86/amd/hsmp: Cache pci_dev in struct hsmp_socket (jsc#PED-8779).\n- platform/x86/amd/hsmp: Change devm_kzalloc() to devm_kcalloc() (jsc#PED-8779).\n- platform/x86/amd/hsmp: Check HSMP support on AMD family of processors (jsc#PED-8779).\n- platform/x86/amd/hsmp: Check num_sockets against MAX_AMD_SOCKETS (jsc#PED-8779).\n- platform/x86/amd/hsmp: Create static func to handle platdev (jsc#PED-8779).\n- platform/x86/amd/hsmp: Define a struct to hold mailbox regs (jsc#PED-8779).\n- platform/x86/amd/hsmp: Move dev from platdev to hsmp_socket (jsc#PED-8779).\n- platform/x86/amd/hsmp: Move hsmp_test to probe (jsc#PED-8779).\n- platform/x86/amd/hsmp: Non-ACPI support for AMD F1A_M00~0Fh (jsc#PED-8779).\n- platform/x86/amd/hsmp: Remove extra parenthesis and add a space (jsc#PED-8779).\n- platform/x86/amd/hsmp: Restructure sysfs group creation (jsc#PED-8779).\n- platform/x86/amd/hsmp: switch to use device_add_groups() (jsc#PED-8779).\n- platform/x86/intel/ifs: Initialize union ifs_status to zero (git-fixes).\n- platform/x86: lg-laptop: fix %s null argument warning (stable-fixes).\n- power: supply: axp288_charger: Fix constant_charge_voltage writes (git-fixes).\n- power: supply: axp288_charger: Round constant_charge_voltage writes down (git-fixes).\n- power: supply: qcom_battmgr: return EAGAIN when firmware service is not up (git-fixes).\n- powerpc/64: Set _IO_BASE to POISON_POINTER_DELTA not 0 for CONFIG_PCI=n (bsc#1194869).\n- powerpc/io: Avoid clang null pointer arithmetic warnings (bsc#1194869).\n- powerpc/kexec: make the update_cpus_node() function public (bsc#1194869).\n- powerpc/kexec: split CONFIG_KEXEC_FILE and CONFIG_CRASH_DUMP (bsc#1194869).\n- powerpc/kexec_file: fix cpus node update to FDT (bsc#1194869).\n- powerpc/pseries: Add failure related checks for h_get_mpp and h_get_ppp (bsc#1194869).\n- powerpc/pseries: Whitelist dtl slub object for copying to userspace (bsc#1194869).\n- powerpc/radix: Move some functions into #ifdef CONFIG_KVM_BOOK3S_HV_POSSIBLE (bsc#1194869).\n- powerpc/topology: Check if a core is online (bsc#1214285 bsc#1205462 ltc#200161 ltc#200588 git-fixes).\n- powerpc/xmon: Check cpu id in commands \"c#\", \"dp#\" and \"dx#\" (bsc#1194869).\n- powerpc: fix a file leak in kvm_vcpu_ioctl_enable_cap() (bsc#1194869).\n- powerpc: xor_vmx: Add '-mhard-float' to CFLAGS (bsc#1194869).\n- printk/panic: Allow cpu backtraces to be written into ringbuffer during panic (bsc#1225607).\n- reiserfs: fix uninit-value in comp_keys (git-fixes).\n- rtc: nct3018y: fix possible NULL dereference (stable-fixes).\n- s390/cpum_cf: Fix endless loop in CF_DIAG event stop (git-fixes bsc#1229171).\n- s390/dasd: fix error checks in dasd_copy_pair_store() (git-fixes bsc#1229173).\n- s390/dasd: fix error recovery leading to data corruption on ESE devices (git-fixes bsc#1229452).\n- s390/pci: Add missing virt_to_phys() for directed DIBV (git-fixes bsc#1229174).\n- s390/pci: Allow allocation of more than 1 MSI interrupt (git-fixes bsc#1229172).\n- s390/pci: Refactor arch_setup_msi_irqs() (git-fixes bsc#1229172).\n- s390/pkey: harmonize pkey s390 debug feature calls (bsc#1228720).\n- s390/pkey: introduce dynamic debugging for pkey (bsc#1228720).\n- s390/sclp: Prevent release of buffer in I/O (git-fixes bsc#1229169).\n- s390/uv: Panic for set and remove shared access UVC errors (git-fixes bsc#1229170).\n- samples/bpf: syscall_tp_user: Fix array out-of-bound access (git-fixes).\n- samples/bpf: syscall_tp_user: Rename num_progs into nr_tests (git-fixes).\n- sbitmap: use READ_ONCE to access map-\u003eword (stable-fixes).\n- scsi: lpfc: Allow DEVICE_RECOVERY mode after RSCN receipt if in PRLI_ISSUE state (bsc#1228857).\n- scsi: lpfc: Cancel ELS WQE instead of issuing abort when SLI port is inactive (bsc#1228857).\n- scsi: lpfc: Fix handling of fully recovered fabric node in dev_loss callbk (bsc#1228857).\n- scsi: lpfc: Fix incorrect request len mbox field when setting trunking via sysfs (bsc#1228857).\n- scsi: lpfc: Handle mailbox timeouts in lpfc_get_sfp_info (bsc#1228857).\n- scsi: lpfc: Relax PRLI issue conditions after GID_FT response (bsc#1228857).\n- scsi: lpfc: Revise lpfc_prep_embed_io routine with proper endian macro usages (bsc#1228857).\n- scsi: lpfc: Update lpfc version to 14.4.0.3 (bsc#1228857).\n- scsi: qla2xxx: Avoid possible run-time warning with long model_num (bsc#1228850).\n- scsi: qla2xxx: Complete command early within lock (bsc#1228850).\n- scsi: qla2xxx: Convert comma to semicolon (bsc#1228850).\n- scsi: qla2xxx: Drop driver owner assignment (bsc#1228850).\n- scsi: qla2xxx: During vport delete send async logout explicitly (bsc#1228850).\n- scsi: qla2xxx: Fix debugfs output for fw_resource_count (bsc#1228850).\n- scsi: qla2xxx: Fix flash read failure (bsc#1228850).\n- scsi: qla2xxx: Fix for possible memory corruption (bsc#1228850).\n- scsi: qla2xxx: Fix optrom version displayed in FDMI (bsc#1228850).\n- scsi: qla2xxx: Indent help text (bsc#1228850).\n- scsi: qla2xxx: Reduce fabric scan duplicate code (bsc#1228850).\n- scsi: qla2xxx: Remove unused struct 'scsi_dif_tuple' (bsc#1228850).\n- scsi: qla2xxx: Return ENOBUFS if sg_cnt is more than one for ELS cmds (bsc#1228850).\n- scsi: qla2xxx: Unable to act on RSCN for port online (bsc#1228850).\n- scsi: qla2xxx: Update version to 10.02.09.300-k (bsc#1228850).\n- scsi: qla2xxx: Use QP lock to search for bsg (bsc#1228850).\n- scsi: qla2xxx: validate nvme_local_port correctly (bsc#1228850).\n- selftest/bpf: Add map_in_maps with BPF_MAP_TYPE_PERF_EVENT_ARRAY values (git-fixes).\n- selftests/bpf: Add a test to verify previous stacksafe() fix (bsc#1225903).\n- selftests/bpf: Add assert for user stacks in test_task_stack (git-fixes).\n- selftests/bpf: Add netkit to tc_redirect selftest (git-fixes).\n- selftests/bpf: De-veth-ize the tc_redirect test case (git-fixes).\n- selftests/bpf: Disable IPv6 for lwt_redirect test (git-fixes).\n- selftests/bpf: Fix erroneous bitmask operation (git-fixes).\n- selftests/bpf: Fix issues in setup_classid_environment() (git-fixes).\n- selftests/bpf: Fix potential premature unload in bpf_testmod (git-fixes).\n- selftests/bpf: Fix pyperf180 compilation failure with clang18 (git-fixes).\n- selftests/bpf: Fix the flaky tc_redirect_dtime test (git-fixes).\n- selftests/bpf: Fix up xdp bonding test wrt feature flags (git-fixes).\n- selftests/bpf: Make linked_list failure test more robust (git-fixes).\n- selftests/bpf: Relax time_tai test for equal timestamps in tai_forward (git-fixes).\n- selftests/bpf: Skip module_fentry_shadow test when bpf_testmod is not available (git-fixes).\n- selftests/bpf: Wait for the netstamp_needed_key static key to be turned on (git-fixes).\n- selftests/bpf: fix RELEASE=1 build for tc_opts (git-fixes).\n- selftests/bpf: fix bpf_loop_bench for new callback verification scheme (git-fixes).\n- selftests/bpf: fix compiler warnings in RELEASE=1 mode (git-fixes).\n- selftests/bpf: satisfy compiler by having explicit return in btf test (git-fixes).\n- serial: core: check uartclk for zero to avoid divide by zero (stable-fixes).\n- soc: qcom: cmd-db: Map shared memory as WC, not WB (git-fixes).\n- soc: qcom: pmic_glink: Actually communicate when remote goes down (git-fixes).\n- soundwire: stream: fix programming slave ports for non-continous port maps (git-fixes).\n- spi: Add empty versions of ACPI functions (stable-fixes).\n- spi: microchip-core: fix init function not setting the master and motorola modes (git-fixes).\n- spi: microchip-core: switch to use modern name (stable-fixes).\n- spi: spi-fsl-lpspi: Fix scldiv calculation (git-fixes).\n- spi: spidev: Add missing spi_device_id for bh2228fv (git-fixes).\n- squashfs: squashfs_read_data need to check if the length is 0 (git-fixes).\n- ssb: Fix division by zero issue in ssb_calc_clock_rate (stable-fixes).\n- staging: iio: resolver: ad2s1210: fix use before initialization (stable-fixes).\n- staging: ks7010: disable bh on tx_dev_lock (stable-fixes).\n- string.h: Introduce memtostr() and memtostr_pad() (bsc#1228849).\n- sunrpc: add a struct rpc_stats arg to rpc_create_args (git-fixes).\n- swiotlb: do not set total_used to 0 in swiotlb_create_debugfs_files() (git-fixes).\n- swiotlb: fix swiotlb_bounce() to do partial sync's correctly (git-fixes).\n- syscalls: fix compat_sys_io_pgetevents_time64 usage (git-fixes).\n- thermal/drivers/broadcom: Fix race between removal and clock disable (git-fixes).\n- thermal: bcm2835: Convert to platform remove callback returning void (stable-fixes).\n- thunderbolt: Mark XDomain as unplugged when router is removed (stable-fixes).\n- tools/perf: Fix perf bench epoll to enable the run when some CPU's are offline (bsc#1227747).\n- tools/perf: Fix perf bench futex to enable the run when some CPU's are offline (bsc#1227747).\n- tools/perf: Fix timing issue with parallel threads in perf bench wake-up-parallel (bsc#1227747).\n- tools/resolve_btfids: Fix comparison of distinct pointer types warning in resolve_btfids (git-fixes).\n- tools/resolve_btfids: Fix cross-compilation to non-host endianness (git-fixes).\n- tools/resolve_btfids: Refactor set sorting with types from btf_ids.h (git-fixes).\n- tools/resolve_btfids: fix build with musl libc (git-fixes).\n- trace/pid_list: Change gfp flags in pid_list_fill_irq() (git-fixes).\n- tracing: Return from tracing_buffers_read() if the file has been closed (bsc#1229136 git-fixes).\n- tty: atmel_serial: use the correct RTS flag (git-fixes).\n- tty: serial: fsl_lpuart: mark last busy before uart_add_one_port (git-fixes).\n- usb: cdnsp: fix for Link TRB with TC (git-fixes).\n- usb: cdnsp: fix incorrect index in cdnsp_get_hw_deq function (git-fixes).\n- usb: core: sysfs: Unmerge @usb3_hardware_lpm_attr_group in remove_power_attributes() (git-fixes).\n- usb: dwc3: core: Skip setting event buffers for host only controllers (stable-fixes).\n- usb: dwc3: omap: add missing depopulate in probe error path (git-fixes).\n- usb: dwc3: st: add missing depopulate in probe error path (git-fixes).\n- usb: dwc3: st: fix probed platform device ref count on probe error path (git-fixes).\n- usb: gadget: core: Check for unset descriptor (git-fixes).\n- usb: gadget: fsl: Increase size of name buffer for endpoints (stable-fixes).\n- usb: gadget: u_audio: Check return codes from usb_ep_enable and config_ep_by_speed (git-fixes).\n- usb: gadget: u_serial: Set start_delayed during suspend (git-fixes).\n- usb: gadget: uvc: cleanup request when not in correct state (stable-fixes).\n- usb: typec: fsa4480: Add support to swap SBU orientation (git-fixes).\n- usb: typec: fsa4480: Check if the chip is really there (git-fixes).\n- usb: typec: fsa4480: Relax CHIP_ID check (git-fixes).\n- usb: typec: fsa4480: add support for Audio Accessory Mode (git-fixes).\n- usb: typec: fsa4480: rework mux \u0026 switch setup to handle more states (git-fixes).\n- usb: vhci-hcd: Do not drop references before new references are gained (stable-fixes).\n- vfio/pci: fix potential memory leak in vfio_intx_enable() (git-fixes).\n- vhost-scsi: Handle vhost_vq_work_queue failures for events (git-fixes).\n- vhost-vdpa: switch to use vmf_insert_pfn() in the fault handler (git-fixes).\n- vhost/vsock: always initialize seqpacket_allow (git-fixes).\n- vhost: Release worker mutex during flushes (git-fixes).\n- vhost: Use virtqueue mutex for swapping worker (git-fixes).\n- virt: guest_memfd: fix reference leak on hwpoisoned page (git-fixes).\n- virtio-crypto: handle config changed by work queue (git-fixes).\n- virtio: reenable config if freezing device failed (git-fixes).\n- virtio_net: use u64_stats_t infra to avoid data-races (git-fixes).\n- virtiofs: forbid newlines in tags (bsc#1229940).\n- wifi: ath12k: fix memory leak in ath12k_dp_rx_peer_frag_setup() (stable-fixes).\n- wifi: ath12k: fix soft lockup on suspend (git-fixes).\n- wifi: brcmfmac: cfg80211: Handle SSID based pmksa deletion (git-fixes).\n- wifi: cfg80211: fix reporting failed MLO links status with cfg80211_connect_done (git-fixes).\n- wifi: iwlwifi: fw: fix wgds rev 3 exact size (git-fixes).\n- wifi: mac80211: use monitor sdata with driver only if desired (git-fixes).\n- wifi: mwifiex: duplicate static structs used in driver instances (git-fixes).\n- wifi: nl80211: disallow setting special AP channel widths (stable-fixes).\n- wifi: nl80211: do not give key data to userspace (stable-fixes).\n- wifi: rtw88: usb: Fix disconnection after beacon loss (stable-fixes).\n- wifi: wfx: repair open network AP mode (git-fixes).\n- workqueue: Improve scalability of workqueue watchdog touch (bsc#1193454).\n- workqueue: wq_watchdog_touch is always called with valid CPU (bsc#1193454).\n- x86/asm: Use %c/%n instead of %P operand modifier in asm templates (git-fixes).\n- x86/entry/64: Remove obsolete comment on tracing vs. SYSRET (git-fixes).\n- x86/mm: Fix pti_clone_entry_text() for i386 (git-fixes).\n- x86/mm: Fix pti_clone_pgtable() alignment assumption (git-fixes).\n- x86/mtrr: Check if fixed MTRRs exist before saving them (git-fixes).\n- x86/numa: Fix SRAT lookup of CFMWS ranges with numa_fill_memblks() (git-fixes).\n- x86/numa: Fix the address overlap check in numa_fill_memblks() (git-fixes).\n- x86/numa: Fix the sort compare func used in numa_fill_memblks() (git-fixes).\n- x86/numa: Introduce numa_fill_memblks() (git-fixes).\n- x86/pci: Skip early E820 check for ECAM region (git-fixes).\n- x86/xen: Convert comma to semicolon (git-fixes).\n- xfs: Fix missing interval for missing_owner in xfs fsmap (git-fixes).\n- xfs: Fix the owner setting issue for rmap query in xfs fsmap (git-fixes).\n- xfs: allow cross-linking special files without project quota (git-fixes).\n- xfs: allow symlinks with short remote targets (bsc#1229160).\n- xfs: allow unlinked symlinks and dirs with zero size (git-fixes).\n- xfs: attr forks require attr, not attr2 (git-fixes).\n- xfs: convert comma to semicolon (git-fixes).\n- xfs: do not use current-\u003ejournal_info (git-fixes).\n- xfs: fix unlink vs cluster buffer instantiation race (git-fixes).\n- xfs: honor init_xattrs in xfs_init_new_inode for !ATTR fs (git-fixes).\n- xfs: journal geometry is not properly bounds checked (git-fixes).\n- xfs: match lock mode in xfs_buffered_write_iomap_begin() (git-fixes).\n- xfs: require XFS_SB_FEAT_INCOMPAT_LOG_XATTRS for attr log intent item recovery (git-fixes).\n- xfs: upgrade the extent counters in xfs_reflink_end_cow_extent later (git-fixes).\n- xfs: use XFS_BUF_DADDR_NULL for daddrs in getfsmap code (git-fixes).\n- xfs: use consistent uid/gid when grabbing dquots for inodes (git-fixes).\n- xhci: Fix Panther point NULL pointer deref at full-speed re-enumeration (git-fixes).\n- xprtrdma: Fix rpcrdma_reqs_reset() (git-fixes).\n","status":"published","published":"2025-02-03T08:54:39Z","modified":"2026-03-23T04:50:03.568046Z","updated_at":"2026-11-02T15:53:59.381172Z"},{"id":"SUSE-SU-2025:20047-1","title":"Security update for the Linux Kernel","description":"\n\nThe SUSE Linux Enterprise Micro 6.0 RT kernel was updated to receive various security bugfixes.\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-2023-52581: netfilter: nf_tables: fix memleak when more than 255 elements expired (bsc#1220877).\n- CVE-2023-52859: perf: hisi: Fix use-after-free when register pmu fails (bsc#1225582).\n- CVE-2023-52889: apparmor: Fix null pointer deref when receiving skb during sock creation (bsc#1229287).\n- CVE-2024-26590: erofs: fix inconsistent per-file compression format (bsc#1220252).\n- CVE-2024-26631: ipv6: mcast: fix data-race in ipv6_mc_down / mld_ifc_work (bsc#1221630).\n- CVE-2024-26668: netfilter: nft_limit: reject configurations that cause integer overflow (bsc#1222335).\n- CVE-2024-26669: kABI fix for net/sched: flower: Fix chain template offload (bsc#1222350).\n- CVE-2024-26677: Blacklist e7870cf13d20 (\" Fix delayed ACKs to not set the reference serial number\") (bsc#1222387)\n- CVE-2024-26735: ipv6: sr: fix possible use-after-free and null-ptr-deref (bsc#1222372).\n- CVE-2024-26808: netfilter: nft_chain_filter: handle NETDEV_UNREGISTER for inet/ingress basechain (bsc#1222634).\n- CVE-2024-26809: netfilter: nft_set_pipapo: release elements in clone only from destroy path (bsc#1222633).\n- CVE-2024-26812: kABI: vfio: struct virqfd kABI workaround (bsc#1222808).\n- CVE-2024-26835: netfilter: nf_tables: set dormant flag on hook register failure (bsc#1222967).\n- CVE-2024-26837: net: bridge: switchdev: race between creation of new group memberships and generation of the list of MDB events to replay (bsc#1222973).\n- CVE-2024-26851: netfilter: nf_conntrack_h323: Add protection for bmp length out of range (bsc#1223074)\n- CVE-2024-27010: net/sched: Fix mirred deadlock on device recursion (bsc#1223720).\n- CVE-2024-27011: netfilter: nf_tables: fix memleak in map from abort path (bsc#1223803).\n- CVE-2024-27024: net/rds: fix WARNING in rds_conn_connect_if_down (bsc#1223777).\n- CVE-2024-27079: iommu/vt-d: Fix NULL domain on device release (bsc#1223742).\n- CVE-2024-27403: kabi: restore const specifier in flow_offload_route_init() (bsc#1224415).\n- CVE-2024-27433: clk: mediatek: mt7622-apmixedsys: Fix an error handling path in clk_mt8135_apmixed_probe() (bsc#1224711).\n- CVE-2024-27437: vfio/pci: Disable auto-enable of exclusive INTx IRQ (bsc#1222625).\n- CVE-2024-35897: netfilter: nf_tables: discard table flag update with pending basechain deletion (bsc#1224510).\n- CVE-2024-35939: Fixed leak pages on dma_set_decrypted() failure (bsc#1224535).\n- CVE-2024-35949: btrfs: make sure that WRITTEN is set on all metadata blocks (bsc#1224700).\n- CVE-2024-36286: netfilter: nfnetlink_queue: acquire rcu_read_lock() in instance_destroy_rcu() (bsc#1226801)\n- CVE-2024-36489: tls: fix missing memory barrier in tls_init (bsc#1226874)\n- CVE-2024-36881: mm/userfaultfd: Fix reset ptes when close() for wr-protected (bsc#1225718).\n- CVE-2024-36929: net: core: reject skb_copy(_expand) for fraglist GSO skbs (bsc#1225814).\n- CVE-2024-36933: net: nsh: Use correct mac_offset to unwind gso skb in nsh_gso_segment() (bsc#1225832).\n- CVE-2024-36979: net: bridge: mst: fix vlan use-after-free (bsc#1226604).\n- CVE-2024-38662: selftests/bpf: Cover verifier checks for mutating sockmap/sockhash (bsc#1226885).\n- CVE-2024-39489: ipv6: sr: fix memleak in seg6_hmac_init_algo (bsc#1227623)\n- CVE-2024-39506: liquidio: adjust a NULL pointer handling path in lio_vf_rep_copy_packet (bsc#1227729).\n- CVE-2024-40905: ipv6: fix possible race in __fib6_drop_pcpu_from() (bsc#1227761)\n- CVE-2024-40909: bpf: Fix a potential use-after-free in bpf_link_free() (bsc#1227798).\n- CVE-2024-40920: net: bridge: mst: fix suspicious rcu usage in br_mst_set_state (bsc#1227781).\n- CVE-2024-40921: net: bridge: mst: pass vlan group directly to br_mst_vlan_set_state (bsc#1227784).\n- CVE-2024-40938: landlock: fix d_parent walk (bsc#1227840).\n- CVE-2024-40939: net: wwan: iosm: Fix tainted pointer delete is case of region creation fail (bsc#1227799).\n- CVE-2024-40954: net: do not leave a dangling sk pointer, when socket creation fails (bsc#1227808)\n- CVE-2024-40956: dmaengine: idxd: Fix possible Use-After-Free in irq_process_work_list (bsc#1227810).\n- CVE-2024-40957: seg6: fix parameter passing when calling NF_HOOK() in End.DX4 and End.DX6 behaviors (bsc#1227811).\n- CVE-2024-40958: netns: Make get_net_ns() handle zero refcount net (bsc#1227812).\n- CVE-2024-40959: xfrm6: check ip6_dst_idev() return value in xfrm6_get_saddr() (bsc#1227884).\n- CVE-2024-40978: scsi: qedi: Fix crash while reading debugfs attribute (bsc#1227929).\n- CVE-2024-40989: KVM: arm64: Disassociate vcpus from redistributor region on teardown (bsc#1227823).\n- CVE-2024-40994: ptp: fix integer overflow in max_vclocks_store (bsc#1227829).\n- CVE-2024-40995: net/sched: act_api: fix possible infinite loop in tcf_idr_check_alloc() (bsc#1227830).\n- CVE-2024-41000: block/ioctl: prefer different overflow check (bsc#1227867).\n- CVE-2024-41007: tcp: use signed arithmetic in tcp_rtx_probe0_timed_out() (bsc#1227863).\n- CVE-2024-41009: bpf: Fix overrunning reservations in ringbuf (bsc#1228020).\n- CVE-2024-41010: bpf: Fix too early release of tcx_entry (bsc#1228021).\n- CVE-2024-41012: filelock: Remove locks reliably when fcntl/close race is detected (bsc#1228247).\n- CVE-2024-41015: ocfs2: add bounds checking to ocfs2_check_dir_entry() (bsc#1228409).\n- CVE-2024-41020: filelock: Fix fcntl/close race recovery compat path (bsc#1228427).\n- CVE-2024-41032: mm: vmalloc: check if a hash-index is in cpu_possible_mask (bsc#1228460).\n- CVE-2024-41036: net: ks8851: Fix deadlock with the SPI chip variant (bsc#1228496).\n- CVE-2024-41040: net/sched: Fix UAF when resolving a clash (bsc#1228518).\n- CVE-2024-41041: udp: Set SOCK_RCU_FREE earlier in udp_lib_get_port() (bsc#1228520).\n- CVE-2024-41044: ppp: reject claimed-as-LCP but actually malformed packets (bsc#1228530).\n- CVE-2024-41048: skmsg: Skip zero length skb in sk_msg_recvmsg (bsc#1228565).\n- CVE-2024-41050: cachefiles: cyclic allocation of msg_id to avoid reuse (bsc#1228499).\n- CVE-2024-41051: cachefiles: wait for ondemand_object_worker to finish when dropping object (bsc#1228468).\n- CVE-2024-41057: cachefiles: fix slab-use-after-free in cachefiles_withdraw_cookie() (bsc#1228462).\n- CVE-2024-41058: cachefiles: fix slab-use-after-free in fscache_withdraw_volume() (bsc#1228459).\n- CVE-2024-41062: bluetooth/l2cap: sync sock recv cb and release (bsc#1228576).\n- CVE-2024-41064: powerpc/eeh: avoid possible crash when edev-\u003epdev changes (bsc#1228599).\n- CVE-2024-41066: ibmvnic: add tx check to prevent skb leak (bsc#1228640).\n- CVE-2024-41068: s390/sclp: Fix sclp_init() cleanup on failure (bsc#1228579).\n- CVE-2024-41069: ASoC: topology: Fix route memory corruption (bsc#1228644).\n- CVE-2024-41070: KVM: PPC: Book3S HV: Prevent UAF in kvm_spapr_tce_attach_iommu_group() (bsc#1228581).\n- CVE-2024-41074: cachefiles: Set object to close if ondemand_id \u003c 0 in copen (bsc#1228643).\n- CVE-2024-41075: cachefiles: add consistency check for copen/cread (bsc#1228646).\n- CVE-2024-41076: NFSv4: Fix memory leak in nfs4_set_security_label (bsc#1228649).\n- CVE-2024-41078: btrfs: qgroup: fix quota root leak after quota disable failure (bsc#1228655).\n- CVE-2024-41080: io_uring: fix possible deadlock in io_register_iowq_max_workers() (bsc#1228616).\n- CVE-2024-41081: ila: block BH in ila_output() (bsc#1228617).\n- CVE-2024-41084: cxl/region: Avoid null pointer dereference in region lookup (bsc#1228472).\n- CVE-2024-42070: netfilter: nf_tables: fully validate NFT_DATA_VALUE on store to data registers (bsc#1228470).\n- CVE-2024-42073: mlxsw: spectrum_buffers: Fix memory corruptions on Spectrum-4 systems (bsc#1228457).\n- CVE-2024-42079: gfs2: Fix NULL pointer dereference in gfs2_log_flush (bsc#1228672).\n- CVE-2024-42082: xdp: Remove WARN() from __xdp_reg_mem_model() (bsc#1228482).\n- CVE-2024-42093: net/dpaa2: Avoid explicit cpumask var allocation on stack (bsc#1228680).\n- CVE-2024-42095: serial: 8250_omap: Fix Errata i2310 with RX FIFO level check (bsc#1228446).\n- CVE-2024-42096: x86: stop playing stack games in profile_pc() (bsc#1228633).\n- CVE-2024-42106: inet_diag: Initialize pad field in struct inet_diag_req_v2 (bsc#1228493).\n- CVE-2024-42107: ice: Do not process extts if PTP is disabled (bsc#1228494).\n- CVE-2024-42109: netfilter: nf_tables: unconditionally flush pending work before notifier (bsc#1228505).\n- CVE-2024-42110: net: ntb_netdev: Move ntb_netdev_rx_handler() to call netif_rx() from __netif_rx() (bsc#1228501).\n- CVE-2024-42113: net: txgbe: initialize num_q_vectors for MSI/INTx interrupts (bsc#1228568).\n- CVE-2024-42122: drm/amd/display: Add NULL pointer check for kzalloc (bsc#1228591).\n- CVE-2024-42124: scsi: qedf: Make qedf_execute_tmf() non-preemptible (bsc#1228705).\n- CVE-2024-42138: mlxsw: core_linecards: Fix double memory deallocation in case of invalid INI file (bsc#1228500).\n- CVE-2024-42139: ice: Fix improper extts handling (bsc#1228503).\n- CVE-2024-42142: net/mlx5: E-switch, Create ingress ACL when needed (bsc#1228491).\n- CVE-2024-42145: IB/core: Implement a limit on UMAD receive List (bsc#1228743).\n- CVE-2024-42148: bnx2x: Fix multiple UBSAN array-index-out-of-bounds (bsc#1228487).\n- CVE-2024-42155: s390/pkey: Wipe copies of protected- and secure-keys (bsc#1228733).\n- CVE-2024-42156: s390/pkey: Wipe copies of clear-key structures on failure (bsc#1228722).\n- CVE-2024-42157: s390/pkey: Wipe sensitive data on failure (bsc#1228727).\n- CVE-2024-42158: s390/pkey: Use kfree_sensitive() to fix Coccinelle warnings (bsc#1228720).\n- CVE-2024-42159: scsi: mpi3mr: fix sanitise num_phys (bsc#1228754).\n- CVE-2024-42161: bpf: avoid uninitialized value in BPF_CORE_READ_BITFIELD (bsc#1228756).\n- CVE-2024-42162: gve: Account for stopped queues when reading NIC stats (bsc#1228706).\n- CVE-2024-42224: net: dsa: mv88e6xxx: Correct check for empty list (bsc#1228723).\n- CVE-2024-42241: mm/shmem: disable PMD-sized page cache if needed (bsc#1228986).\n- CVE-2024-42245: Revert \"sched/fair: Make sure to try to detach at least one movable task\" (bsc#1228978).\n- CVE-2024-42246: net, sunrpc: Remap EPERM in case of connection failure in xs_tcp_setup_socket (bsc#1228989).\n- CVE-2024-42247: wireguard: allowedips: avoid unaligned 64-bit memory accesses (bsc#1228988).\n- CVE-2024-42268: net/mlx5: Fix missing lock on sync reset reload (bsc#1229391).\n- CVE-2024-42269: netfilter: iptables: Fix potential null-ptr-deref in ip6table_nat_table_init() (bsc#1229402).\n- CVE-2024-42270: netfilter: iptables: Fix null-ptr-deref in iptable_nat_table_init() (bsc#1229404).\n- CVE-2024-42277: iommu: sprd: Avoid NULL deref in sprd_iommu_hw_en (bsc#1229409).\n- CVE-2024-42281: bpf: Fix a segment issue when downgrading gso_size (bsc#1229386).\n- CVE-2024-42283: net: nexthop: Initialize all fields in dumped nexthops (bsc#1229383)\n- CVE-2024-42284: tipc: Return non-zero value from tipc_udp_addr2str() on error (bsc#1229382)\n- CVE-2024-42290: irqchip/imx-irqsteer: Handle runtime power management correctly (bsc#1229379).\n- CVE-2024-42291: ice: Add a per-VF limit on number of FDIR filters (bsc#1229374).\n- CVE-2024-42295: nilfs2: handle inconsistent state in nilfs_btnode_create_block() (bsc#1229370).\n- CVE-2024-42301: dev/parport: fix the array out-of-bounds risk (bsc#1229407).\n- CVE-2024-42312: sysctl: always initialize i_uid/i_gid (bsc#1229357)\n- CVE-2024-42316: mm/mglru: fix div-by-zero in vmpressure_calc_level() (bsc#1229353).\n- CVE-2024-42318: landlock: Do not lose track of restrictions on cred_transfer (bsc#1229351).\n- CVE-2024-42322: ipvs: properly dereference pe in ip_vs_add_service (bsc#1229347)\n- CVE-2024-43821: scsi: lpfc: Fix a possible null pointer dereference (bsc#1229315).\n- CVE-2024-43831: media: mediatek: vcodec: Handle invalid decoder vsi (bsc#1229309).\n- CVE-2024-43834: xdp: fix invalid wait context of page_pool_destroy() (bsc#1229314)\n- CVE-2024-43837: bpf: Fix updating attached freplace prog in prog_array map (bsc#1229297).\n- CVE-2024-43839: bna: adjust 'name' buf size of bna_tcb and bna_ccb structures (bsc#1229301).\n- CVE-2024-43850: soc: qcom: icc-bwmon: Fix refcount imbalance seen during bwmon_remove (bsc#1229316).\n- CVE-2024-43854: block: initialize integrity buffer to zero before writing it to media (bsc#1229345)\n- CVE-2024-43855: md: fix deadlock between mddev_suspend and flush bio (bsc#1229342).\n- CVE-2024-43864: net/mlx5e: Fix CT entry update leaks of modify header context (bsc#1229496).\n- CVE-2024-43866: net/mlx5: Always drain health in shutdown callback (bsc#1229495).\n- CVE-2024-43880: kabi: lib: objagg: Put back removed metod in struct objagg_ops (bsc#1229481).\n- CVE-2024-43882: Fixed ToCToU between perm check and set-uid/gid usage. (bsc#1229503)\n- CVE-2024-43899: drm/amd/display: Fix null pointer deref in dcn20_resource.c (bsc#1229754).\n- CVE-2024-43911: wifi: mac80211: fix NULL dereference at band check in starting tx ba session (bsc#1229827).\n\nThe following non-security bugs were fixed:\n\n- ACPI/NUMA: Apply SRAT proximity domain to entire CFMWS window (git-fixes).\n- ACPI: SBS: manage alarm sysfs attribute through psy core (stable-fixes).\n- ACPI: battery: create alarm sysfs attribute atomically (stable-fixes).\n- ACPI: processor_idle: use raw_safe_halt() in acpi_idle_play_dead() (git-fixes).\n- ALSA: hda/hdmi: Yet more pin fix for HP EliteDesk 800 G4 (stable-fixes).\n- ALSA: hda/hdmi: Yet more pin fix for HP EliteDesk 800 G4 (stable-fixes).\n- ALSA: hda/realtek - FIxed ALC285 headphone no sound (stable-fixes).\n- ALSA: hda/realtek - Fixed ALC256 headphone no sound (stable-fixes).\n- ALSA: hda/realtek: Add Framework Laptop 13 (Intel Core Ultra) to quirks (stable-fixes).\n- ALSA: hda/realtek: Add Framework Laptop 13 (Intel Core Ultra) to quirks (stable-fixes).\n- ALSA: hda/realtek: Add quirk for Acer Aspire E5-574G (stable-fixes).\n- ALSA: hda/realtek: Add support for new HP G12 laptops (stable-fixes).\n- ALSA: hda/realtek: Enable mute/micmute LEDs on HP Laptop 14-ey0xxx (stable-fixes).\n- ALSA: hda/realtek: Fix noise from speakers on Lenovo IdeaPad 3 15IAU7 (git-fixes).\n- ALSA: hda/realtek: Fix the speaker output on Samsung Galaxy Book3 Ultra (stable-fixes).\n- ALSA: hda/realtek: Implement sound init sequence for Samsung Galaxy Book3 Pro 360 (stable-fixes).\n- ALSA: hda/realtek: support HP Pavilion Aero 13-bg0xxx Mute LED (stable-fixes).\n- ALSA: hda/tas2781: Use correct endian conversion (git-fixes).\n- ALSA: hda/tas2781: fix wrong calibrated data order (git-fixes).\n- ALSA: hda: Add HP MP9 G4 Retail System AMS to force connect list (stable-fixes).\n- ALSA: hda: Add HP MP9 G4 Retail System AMS to force connect list (stable-fixes).\n- ALSA: hda: Conditionally use snooping for AMD HDMI (git-fixes).\n- ALSA: hda: conexant: Fix headset auto detect fail in the polling mode (git-fixes).\n- ALSA: line6: Fix racy access to midibuf (stable-fixes).\n- ALSA: line6: Fix racy access to midibuf (stable-fixes).\n- ALSA: seq: Skip event type filtering for UMP events (git-fixes).\n- ALSA: seq: ump: Explicitly reset RPN with Null RPN (stable-fixes).\n- ALSA: seq: ump: Optimize conversions from SysEx to UMP (git-fixes).\n- ALSA: seq: ump: Transmit RPN/NRPN message at each MSB/LSB data reception (stable-fixes).\n- ALSA: seq: ump: Use the common RPN/bank conversion context (stable-fixes).\n- ALSA: timer: Relax start tick time check for slave timer elements (git-fixes).\n- ALSA: ump: Explicitly reset RPN with Null RPN (stable-fixes).\n- ALSA: ump: Transmit RPN/NRPN message at each MSB/LSB data reception (stable-fixes).\n- ALSA: usb-audio: Add delay quirk for VIVO USB-C-XE710 HEADSET (stable-fixes).\n- ALSA: usb-audio: Correct surround channels in UAC1 channel map (git-fixes).\n- ALSA: usb-audio: Re-add ScratchAmp quirk entries (git-fixes).\n- ALSA: usb-audio: Re-add ScratchAmp quirk entries (git-fixes).\n- ALSA: usb-audio: Support Yamaha P-125 quirk entry (stable-fixes).\n- ALSA: usb: Fix UBSAN warning in parse_audio_unit() (stable-fixes).\n- ASoC: SOF: Intel: hda-dsp: Make sure that no irq handler is pending before suspend (stable-fixes).\n- ASoC: SOF: Remove libraries from topology lookups (git-fixes).\n- ASoC: SOF: Remove libraries from topology lookups (git-fixes).\n- ASoC: SOF: amd: Fix for acp init sequence (git-fixes).\n- ASoC: SOF: ipc4: check return value of snd_sof_ipc_msg_data (stable-fixes).\n- ASoC: SOF: mediatek: Add missing board compatible (stable-fixes).\n- ASoC: allow module autoloading for table board_ids (stable-fixes).\n- ASoC: allow module autoloading for table db1200_pids (stable-fixes).\n- ASoC: amd: acp: fix module autoloading (git-fixes).\n- ASoC: amd: yc: Add quirk entry for OMEN by HP Gaming Laptop 16-n0xxx (bsc#1227182).\n- ASoC: amd: yc: Support mic on HP 14-em0002la (stable-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: Support mic on Lenovo Thinkpad E14 Gen 6 (stable-fixes).\n- ASoC: codecs: wcd938x-sdw: Correct Soundwire ports mask (git-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: wsa881x: Correct Soundwire ports mask (git-fixes).\n- ASoC: codecs: wsa883x: 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: codecs: wsa884x: Correct Soundwire ports mask (git-fixes).\n- ASoC: cs35l45: Checks index of cs35l45_irqs[] (stable-fixes).\n- ASoC: cs35l56: Handle OTP read latency over SoundWire (stable-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: 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: fsl_micfil: Expand the range of FIFO watermark mask (stable-fixes).\n- ASoC: mediatek: mt8188: Mark AFE_DAC_CON0 register as volatile (stable-fixes).\n- ASoC: meson: axg-fifo: fix irq scheduling issue with PREEMPT_RT (git-fixes).\n- ASoC: meson: axg-fifo: fix irq scheduling issue with PREEMPT_RT (git-fixes).\n- ASoC: nau8822: Lower debug print priority (stable-fixes).\n- ASoC: nau8822: Lower debug print priority (stable-fixes).\n- Bluetooth: Add device 13d3:3572 IMC Networks Bluetooth Radio (stable-fixes).\n- Bluetooth: Fix usage of __hci_cmd_sync_status (git-fixes).\n- Bluetooth: L2CAP: Fix deadlock (git-fixes).\n- Bluetooth: MGMT: Add error handling to pair_device() (git-fixes).\n- Bluetooth: SMP: Fix assumption of Central always being Initiator (git-fixes).\n- Bluetooth: bnep: Fix out-of-bound access (stable-fixes).\n- Bluetooth: btintel: Fail setup on error (git-fixes).\n- Bluetooth: btnxpuart: Shutdown timer and prevent rearming when driver unloading (stable-fixes).\n- Bluetooth: btusb: Add RTL8852BE device 0489:e125 to device tables (stable-fixes).\n- Bluetooth: btusb: Add Realtek RTL8852BE support ID 0x13d3:0x3591 (stable-fixes).\n- Bluetooth: hci_conn: Check non NULL function before calling for HFP offload (stable-fixes).\n- Bluetooth: hci_core: Fix LE quote calculation (git-fixes).\n- Bluetooth: hci_core: Fix not handling hibernation actions (git-fixes).\n- Bluetooth: hci_sync: Fix suspending with wrong filter policy (git-fixes).\n- Bluetooth: hci_sync: avoid dup filtering when passive scanning with adv monitor (git-fixes).\n- Bluetooth: l2cap: always unlock channel in l2cap_conless_channel() (git-fixes).\n- Drop libata patch that caused a regression (bsc#1229054)\n- Fix build errors without patches.kabi (bsc#1226502)\n- HID: wacom: Defer calculation of resolution until resolution_code is known (git-fixes).\n- Input: MT - limit max slots (stable-fixes).\n- Input: i8042 - add Fujitsu Lifebook E756 to i8042 quirk table (bsc#1229056).\n- Input: i8042 - add forcenorestore quirk to leave controller untouched even on s3 (stable-fixes).\n- Input: i8042 - use new forcenorestore quirk to replace old buggy quirk combination (stable-fixes).\n- KVM: Always flush async #PF workqueue when vCPU is being destroyed (git-fixes).\n- KVM: Make KVM_MEM_GUEST_MEMFD mutually exclusive with KVM_MEM_READONLY (git-fixes).\n- KVM: PPC: Book3S HV: Fix the set_one_reg for MMCR3 (bsc#1194869).\n- KVM: PPC: Book3S HV: Handle pending exceptions on guest entry with MSR_EE (bsc#1215199).\n- KVM: Protect vcpu-\u003epid dereference via debugfs with RCU (git-fixes).\n- KVM: Reject overly excessive IDs in KVM_CREATE_VCPU (git-fixes).\n- KVM: Stop processing *all* memslots when \"null\" mmu_notifier handler is found (git-fixes).\n- KVM: VMX: Move posted interrupt descriptor out of VMX code (git-fixes).\n- KVM: VMX: Split out the non-virtualization part of vmx_interrupt_blocked() (git-fixes).\n- KVM: VMX: Switch __vmx_exit() and kvm_x86_vendor_exit() in vmx_exit() (git-fixes).\n- KVM: arm64: AArch32: Fix spurious trapping of conditional instructions (git-fixes).\n- KVM: arm64: Add missing memory barriers when switching to pKVM's hyp pgd (git-fixes).\n- KVM: arm64: Allow AArch32 PSTATE.M to be restored as System mode (git-fixes).\n- KVM: arm64: Fix AArch32 register narrowing on userspace write (git-fixes).\n- KVM: arm64: Fix __pkvm_init_switch_pgd call ABI (git-fixes).\n- KVM: arm64: Fix clobbered ELR in sync abort/SError (git-fixes)\n- KVM: arm64: GICv4: Do not perform a map to a mapped vLPI (git-fixes).\n- KVM: arm64: timers: Correctly handle TGE flip with CNTPOFF_EL2 (git-fixes).\n- KVM: arm64: timers: Fix resource leaks in kvm_timer_hyp_init() (git-fixes).\n- KVM: arm64: vgic-its: Test for valid IRQ in its_sync_lpi_pending_table() (git-fixes).\n- KVM: arm64: vgic-its: Test for valid IRQ in MOVALL handler (git-fixes).\n- KVM: arm64: vgic-v2: Use cpuid from userspace as vcpu_id (git-fixes).\n- KVM: arm64: vgic-v4: Restore pending state on host userspace write (git-fixes).\n- KVM: arm64: vgic: Add a non-locking primitive for kvm_vgic_vcpu_destroy() (git-fixes).\n- KVM: arm64: vgic: Force vcpu vgic teardown on vcpu destroy (git-fixes).\n- KVM: arm64: vgic: Simplify kvm_vgic_destroy() (git-fixes).\n- KVM: fix kvm_mmu_memory_cache allocation warning (git-fixes).\n- KVM: nVMX: Add a helper to get highest pending from Posted Interrupt vector (git-fixes).\n- KVM: nVMX: Check for pending posted interrupts when looking for nested events (git-fixes).\n- KVM: nVMX: Request immediate exit iff pending nested event needs injection (git-fixes).\n- KVM: s390: fix LPSWEY handling (bsc#1227634 git-fixes).\n- KVM: s390: fix validity interception issue when gisa is switched off (git-fixes bsc#1229167).\n- KVM: x86/mmu: Bug the VM if KVM tries to split a !hugepage SPTE (git-fixes).\n- KVM: x86: Limit check IDs for KVM_SET_BOOT_CPU_ID (git-fixes).\n- Move upstreamed powerpc patches into sorted section\n- Move upstreamed sound patches into sorted section\n- Moved upstreamed ASoC patch into sorted section\n- NFSD: Support write delegations in LAYOUTGET (git-fixes).\n- NFSv4.1 another fix for EXCHGID4_FLAG_USE_PNFS_DS for DS server (git-fixes).\n- PCI: Add Edimax Vendor ID to pci_ids.h (stable-fixes).\n- PCI: hv: Return zero, not garbage, when reading PCI_INTERRUPT_PIN (git-fixes).\n- PCI: loongson: Enable MSI in LS7A Root Complex (stable-fixes).\n- RDMA/cache: Release GID table even if leak is detected (git-fixes)\n- RDMA/device: Return error earlier if port in not valid (git-fixes)\n- RDMA/hns: Check atomic wr length (git-fixes)\n- RDMA/hns: Fix insufficient extend DB for VFs. (git-fixes)\n- RDMA/hns: Fix mbx timing out before CMD execution is completed (git-fixes)\n- RDMA/hns: Fix missing pagesize and alignment check in FRMR (git-fixes)\n- RDMA/hns: Fix shift-out-bounds when max_inline_data is 0 (git-fixes)\n- RDMA/hns: Fix soft lockup under heavy CEQE load (git-fixes)\n- RDMA/hns: Fix undifined behavior caused by invalid max_sge (git-fixes)\n- RDMA/hns: Fix unmatch exception handling when init eq table fails (git-fixes)\n- RDMA/iwcm: Fix a use-after-free related to destroying CM IDs (git-fixes)\n- RDMA/mana_ib: Use virtual address in dma regions for MRs (git-fixes).\n- RDMA/mlx4: Fix truncated output warning in alias_GUID.c (git-fixes)\n- RDMA/mlx4: Fix truncated output warning in mad.c (git-fixes)\n- RDMA/mlx5: Set mkeys for dmabuf at PAGE_SIZE (git-fixes)\n- RDMA/rxe: Do not set BTH_ACK_MASK for UC or UD QPs (git-fixes)\n- RDMA: Fix netdev tracker in ib_device_set_netdev (git-fixes)\n- README.BRANCH: Add Petr Tesarik as branch maintainer\n- Revert \"ALSA: firewire-lib: obsolete workqueue for period update\" (bsc#1208783).\n- Revert \"ALSA: firewire-lib: operate for period elapse event in process context\" (bsc#1208783).\n- Revert \"KVM: Prevent module exit until all VMs are freed\" (git-fixes).\n- Revert \"Revert \"md/raid5: Wait for MD_SB_CHANGE_PENDING in raid5d\"\" (git-fixes).\n- Revert \"md/raid5: Wait for MD_SB_CHANGE_PENDING in raid5d\" (git-fixes).\n- Revert \"misc: fastrpc: Restrict untrusted app to attach to privileged PD\" (git-fixes).\n- Revert \"usb: gadget: uvc: cleanup request when not in correct state\" (stable-fixes).\n- Revert \"usb: typec: tcpm: clear pd_event queue in PORT_RESET\" (git-fixes).\n- SUNRPC: Fix a race to wake a sync task (git-fixes).\n- SUNRPC: add a missing rpc_stat for TCP TLS (git-fixes).\n- Squashfs: fix variable overflow triggered by sysbot (git-fixes).\n- USB: serial: debug: do not echo input by default (stable-fixes).\n- Update config files. Disable vdpa drivers for Alibaba ENI and SolidNET (jsc#PED-8954, bsc#1227834)\n- Update config files. Disable CONFIG_KFENCE on ppc64le (bsc#1226920)\n- Update patch refefernce for MFD patch (jsc#PED-10029)\n- Update patch reference for MD patch (jsc#PED-10029 jsc#PED-10045)\n- Update patch reference for SPI patch (jsc#PED-10105)\n- Update patch reference for iwlwifi fix (jsc#PED-10055)\n- Update patch reference of USB patch (jsc#PED-10108)\n- Update patch references for ASoC regression fixes (bsc#1229045 bsc#1229046)\n- afs: fix __afs_break_callback() / afs_drop_open_mmap() race (git-fixes).\n- apparmor: unpack transition table if dfa is not present (bsc#1226031).\n- arm64: ACPI: NUMA: initialize all values of acpi_early_node_map to (git-fixes)\n- arm64: Add Neoverse-V2 part (git-fixes)\n- arm64: Fix KASAN random tag seed initialization (git-fixes)\n- arm64: armv8_deprecated: Fix warning in isndep cpuhp starting process (git-fixes)\n- arm64: barrier: Restore spec_bar() macro (git-fixes)\n- arm64: cputype: Add Cortex-A720 definitions (git-fixes)\n- arm64: cputype: Add Cortex-A725 definitions (git-fixes)\n- arm64: cputype: Add Cortex-X1C definitions (git-fixes)\n- arm64: cputype: Add Cortex-X3 definitions (git-fixes)\n- arm64: cputype: Add Cortex-X4 definitions (git-fixes)\n- arm64: cputype: Add Cortex-X925 definitions (git-fixes)\n- arm64: cputype: Add Neoverse-V3 definitions (git-fixes)\n- arm64: dts: imx8mp: Add NPU Node (git-fixes)\n- arm64: dts: imx8mp: Fix pgc vpu locations (git-fixes)\n- arm64: dts: imx8mp: Fix pgc_mlmix location (git-fixes)\n- arm64: dts: imx8mp: add HDMI power-domains (git-fixes)\n- arm64: errata: Expand speculative SSBS workaround (again) (git-fixes)\n- arm64: errata: Expand speculative SSBS workaround (git-fixes)\n- arm64: errata: Unify speculative SSBS errata logic (git-fixes). Update config files.\n- arm64: jump_label: Ensure patched jump_labels are visible to all CPUs (git-fixes)\n- ata: libata-scsi: Do not overwrite valid sense data when CK_COND=1 (stable-fixes).\n- ata: libata-scsi: Honor the D_SENSE bit for CK_COND=1 and no error (stable-fixes).\n- blacklist.conf: Add libata upstream revert entry (bsc#1229054)\n- blacklist.conf: printk/sysctl: breaks kernel without pre-requisite patches (bsc#1229025)\n- bnxt_re: Fix imm_data endianness (git-fixes)\n- bpf, arm64: Fix trampoline for BPF_TRAMP_F_CALL_ORIG (git-fixes)\n- bpf, lpm: Fix check prefixlen before walking trie (git-fixes).\n- bpf/tests: Remove duplicate JSGT tests (git-fixes).\n- bpf: Add crosstask check to __bpf_get_stack (git-fixes).\n- bpf: Detect IP == ksym.end as part of BPF program (git-fixes).\n- bpf: Ensure proper register state printing for cond jumps (git-fixes).\n- bpf: Fix a few selftest failures due to llvm18 change (git-fixes).\n- bpf: Fix a kernel verifier crash in stacksafe() (bsc#1225903).\n- bpf: Fix check_stack_write_fixed_off() to correctly spill imm (git-fixes).\n- bpf: Fix kfunc callback register type handling (git-fixes).\n- bpf: Fix prog_array_map_poke_run map poke update (git-fixes).\n- bpf: Fix unnecessary -EBUSY from htab_lock_bucket (git-fixes).\n- bpf: Mark bpf_spin_{lock,unlock}() helpers with notrace correctly (git-fixes).\n- bpf: Remove unnecessary wait from bpf_map_copy_value() (git-fixes).\n- bpf: Set uattr-\u003ebatch.count as zero before batched update or deletion (git-fixes).\n- bpf: do not infer PTR_TO_CTX for programs with unnamed context type (git-fixes).\n- bpf: enforce precision of R0 on callback return (git-fixes).\n- bpf: extract bpf_ctx_convert_map logic and make it more reusable (git-fixes).\n- bpf: fix control-flow graph checking in privileged mode (git-fixes).\n- bpf: handle bpf_user_pt_regs_t typedef explicitly for PTR_TO_CTX global arg (git-fixes).\n- bpf: hardcode BPF_PROG_PACK_SIZE to 2MB * num_possible_nodes() (git-fixes).\n- bpf: kprobe: remove unused declaring of bpf_kprobe_override (git-fixes).\n- bpf: simplify btf_get_prog_ctx_type() into btf_is_prog_ctx_type() (git-fixes).\n- bpftool: Align output skeleton ELF code (git-fixes).\n- bpftool: Fix -Wcast-qual warning (git-fixes).\n- bpftool: Silence build warning about calloc() (git-fixes).\n- bpftool: mark orphaned programs during prog show (git-fixes).\n- btrfs: add a btrfs_finish_ordered_extent helper (git-fixes).\n- btrfs: add a is_data_bbio helper (git-fixes).\n- btrfs: add an ordered_extent pointer to struct btrfs_bio (git-fixes).\n- btrfs: copy dir permission and time when creating a stub subvolume (bsc#1228321).\n- btrfs: ensure fast fsync waits for ordered extents after a write failure (git-fixes).\n- btrfs: factor out a btrfs_queue_ordered_fn helper (git-fixes).\n- btrfs: factor out a can_finish_ordered_extent helper (git-fixes).\n- btrfs: fix corruption after buffer fault in during direct IO append write (git-fixes).\n- btrfs: fix double inode unlock for direct IO sync writes (git-fixes).\n- btrfs: fix extent map use-after-free when adding pages to compressed bio (git-fixes).\n- btrfs: fix leak of qgroup extent records after transaction abort (git-fixes).\n- btrfs: fix ordered extent split error handling in btrfs_dio_submit_io (git-fixes).\n- btrfs: limit write bios to a single ordered extent (git-fixes).\n- btrfs: make btrfs_finish_ordered_extent() return void (git-fixes).\n- btrfs: merge the two calls to btrfs_add_ordered_extent in run_delalloc_nocow (git-fixes).\n- btrfs: open code btrfs_bio_end_io in btrfs_dio_submit_io (git-fixes).\n- btrfs: open code end_extent_writepage in end_bio_extent_writepage (git-fixes).\n- btrfs: pass a btrfs_inode to btrfs_fdatawrite_range() (git-fixes).\n- btrfs: pass a btrfs_inode to btrfs_wait_ordered_range() (git-fixes).\n- btrfs: pass an ordered_extent to btrfs_reloc_clone_csums (git-fixes).\n- btrfs: pass an ordered_extent to btrfs_submit_compressed_write (git-fixes).\n- btrfs: remove btrfs_add_ordered_extent (git-fixes).\n- btrfs: rename err to ret in btrfs_direct_write() (git-fixes).\n- btrfs: uninline some static inline helpers from tree-log.h (git-fixes).\n- btrfs: use a btrfs_inode in the log context (struct btrfs_log_ctx) (git-fixes).\n- btrfs: use a btrfs_inode local variable at btrfs_sync_file() (git-fixes).\n- btrfs: use bbio-\u003eordered in btrfs_csum_one_bio (git-fixes).\n- btrfs: use btrfs_finish_ordered_extent to complete buffered writes (git-fixes).\n- btrfs: use btrfs_finish_ordered_extent to complete compressed writes (git-fixes).\n- btrfs: use btrfs_finish_ordered_extent to complete direct writes (git-fixes).\n- btrfs: use irq safe locking when running and adding delayed iputs (git-fixes).\n- cachefiles, erofs: Fix NULL deref in when cachefiles is not doing ondemand-mode (bsc#1229245).\n- cachefiles: add missing lock protection when polling (bsc#1229256).\n- cachefiles: add restore command to recover inflight ondemand read requests (bsc#1229244).\n- cachefiles: add spin_lock for cachefiles_ondemand_info (bsc#1229249).\n- cachefiles: cancel all requests for the object that is being dropped (bsc#1229255).\n- cachefiles: defer exposing anon_fd until after copy_to_user() succeeds (bsc#1229251).\n- cachefiles: extract ondemand info field from cachefiles_object (bsc#1229240).\n- cachefiles: fix slab-use-after-free in cachefiles_ondemand_daemon_read() (bsc#1229247).\n- cachefiles: fix slab-use-after-free in cachefiles_ondemand_get_fd() (bsc#1229246).\n- cachefiles: introduce object ondemand state (bsc#1229239).\n- cachefiles: make on-demand read killable (bsc#1229252).\n- cachefiles: narrow the scope of triggering EPOLLIN events in ondemand mode (bsc#1229243).\n- cachefiles: never get a new anonymous fd if ondemand_id is valid (bsc#1229250).\n- cachefiles: propagate errors from vfs_getxattr() to avoid infinite loop (bsc#1229253).\n- cachefiles: remove err_put_fd label in cachefiles_ondemand_daemon_read() (bsc#1229248).\n- cachefiles: resend an open request if the read request's object is closed (bsc#1229241).\n- cachefiles: stop sending new request when dropping object (bsc#1229254).\n- can: mcp251xfd: tef: prepare to workaround broken TEF FIFO tail index erratum (stable-fixes).\n- can: mcp251xfd: tef: update workaround for erratum DS80000789E 6 of mcp2518fd (stable-fixes).\n- ceph: periodically flush the cap releases (bsc#1230056).\n- cgroup/cpuset: Prevent UAF in proc_cpuset_show() (bsc#1228801).\n- cgroup: Add annotation for holding namespace_sem in current_cgns_cgroup_from_root() (bsc#1222254).\n- cgroup: Eliminate the need for cgroup_mutex in proc_cgroup_show() (bsc#1222254).\n- cgroup: Make operations on the cgroup root_list RCU safe (bsc#1222254).\n- cgroup: Remove unnecessary list_empty() (bsc#1222254).\n- cgroup: preserve KABI of cgroup_root (bsc#1222254).\n- char: xillybus: Check USB endpoints when probing device (git-fixes).\n- char: xillybus: Do not destroy workqueue from work item running on it (stable-fixes).\n- char: xillybus: Refine workqueue handling (git-fixes).\n- check-for-config-changes: ignore also GCC_ASM_GOTO_OUTPUT_BROKEN Mainline commit f2f6a8e88717 (\"init/Kconfig: remove CONFIG_GCC_ASM_GOTO_OUTPUT_WORKAROUND\") replaced GCC_ASM_GOTO_OUTPUT_WORKAROUND with GCC_ASM_GOTO_OUTPUT_BROKEN. Ignore both when checking config changes.\n- clk: en7523: fix rate divider for slic and spi clocks (git-fixes).\n- clk: qcom: Park shared RCGs upon registration (git-fixes).\n- clk: qcom: camcc-sc7280: Add parent dependency to all camera GDSCs (git-fixes).\n- clk: qcom: gcc-sa8775p: Update the GDSC wait_val fields and flags (git-fixes).\n- clk: qcom: gcc-sc7280: Update force mem core bit for UFS ICE clock (git-fixes).\n- clk: qcom: gpucc-sa8775p: Park RCG's clk source at XO during disable (git-fixes).\n- clk: qcom: gpucc-sa8775p: Remove the CLK_IS_CRITICAL and ALWAYS_ON flags (git-fixes).\n- clk: qcom: gpucc-sa8775p: Update wait_val fields for GPU GDSC's (git-fixes).\n- clk: qcom: gpucc-sm8350: Park RCG's clk source at XO during disable (git-fixes).\n- clk: qcom: kpss-xcc: Return of_clk_add_hw_provider to transfer the error (git-fixes).\n- clk: visconti: Add bounds-checking coverage for struct visconti_pll_provider (stable-fixes).\n- clocksource/drivers/sh_cmt: Address race condition for clock events (stable-fixes).\n- config.sh: generate and install compile_commands.json (bsc#1228971) This file contains the command line options used to compile every C file. It's useful for the livepatching team.\n- cpu/SMT: Enable SMT only if a core is online (bsc#1214285 bsc#1205462 ltc#200161 ltc#200588 git-fixes).\n- cxl/region: Move cxl_dpa_to_region() work to the region driver (bsc#1228472)\n- dev/parport: fix the array out-of-bounds risk (stable-fixes).\n- device property: Add cleanup.h based fwnode_handle_put() scope based cleanup (stable-fixes).\n- dmaengine: dw: Add memory bus width verification (git-fixes).\n- dmaengine: dw: Add peripheral bus width verification (git-fixes).\n- docs: KVM: Fix register ID of SPSR_FIQ (git-fixes).\n- driver core: Fix uevent_show() vs driver detach race (git-fixes).\n- drm/admgpu: fix dereferencing null pointer context (stable-fixes).\n- drm/amd/display: Add delay to improve LTTPR UHBR interop (stable-fixes).\n- drm/amd/display: Add null checker before passing variables (stable-fixes).\n- drm/amd/display: Adjust cursor position (git-fixes).\n- drm/amd/display: Check for NULL pointer (stable-fixes).\n- drm/amd/display: Skip Recompute DSC Params if no Stream on Link (stable-fixes).\n- drm/amd/display: avoid using null object of framebuffer (git-fixes).\n- drm/amd/display: fix cursor offset on rotation 180 (git-fixes).\n- drm/amd/display: fix s2idle entry for DCN3.5+ (stable-fixes).\n- drm/amd/pm: Fix the null pointer dereference for vega10_hwmgr (stable-fixes).\n- drm/amdgpu/jpeg2: properly set atomics vmid field (stable-fixes).\n- drm/amdgpu/jpeg4: properly set atomics vmid field (stable-fixes).\n- drm/amdgpu/pm: Fix the null pointer dereference for smu7 (stable-fixes).\n- drm/amdgpu/pm: Fix the null pointer dereference in apply_state_adjust_rules (stable-fixes).\n- drm/amdgpu/pm: Fix the param type of set_power_profile_mode (stable-fixes).\n- drm/amdgpu/sdma5.2: Update wptr registers as well as doorbell (stable-fixes).\n- drm/amdgpu/sdma5.2: limit wptr workaround to sdma 5.2.1 (git-fixes).\n- drm/amdgpu: Actually check flags for all context ops (stable-fixes).\n- drm/amdgpu: Add lock around VF RLCG interface (stable-fixes).\n- drm/amdgpu: Fix the null pointer dereference to ras_manager (stable-fixes).\n- drm/amdgpu: Forward soft recovery errors to userspace (stable-fixes).\n- drm/amdgpu: Validate TA binary size (stable-fixes).\n- drm/amdgpu: fix dereference null return value for the function amdgpu_vm_pt_parent (stable-fixes).\n- drm/amdgpu: fix potential resource leak warning (stable-fixes).\n- drm/amdgpu: reset vm state machine after gpu reset(vram lost) (stable-fixes).\n- drm/bridge: analogix_dp: properly handle zero sized AUX transactions (stable-fixes).\n- drm/client: fix null pointer dereference in drm_client_modeset_probe (git-fixes).\n- drm/dp_mst: Skip CSN if topology probing is not done yet (stable-fixes).\n- drm/etnaviv: do not block scheduler when GPU is still active (stable-fixes).\n- drm/i915/dsi: Make Lenovo Yoga Tab 3 X90F DMI match less strict (git-fixes).\n- drm/i915/gem: Adjust vma offset for framebuffer mmap offset (stable-fixes).\n- drm/i915/gem: Fix Virtual Memory mapping boundaries calculation (git-fixes).\n- drm/i915/hdcp: Fix HDCP2_STREAM_STATUS macro (git-fixes).\n- drm/i915: Fix possible int overflow in skl_ddi_calculate_wrpll() (git-fixes).\n- drm/lima: set gp bus_stop bit before hard reset (stable-fixes).\n- drm/mediatek/dp: Fix spurious kfree() (git-fixes).\n- drm/msm/dp: fix the max supported bpp logic (git-fixes).\n- drm/msm/dp: reset the link phy params before link training (git-fixes).\n- drm/msm/dpu: capture snapshot on the first commit_done timeout (stable-fixes).\n- drm/msm/dpu: cleanup FB if dpu_format_populate_layout fails (git-fixes).\n- drm/msm/dpu: do not play tricks with debug macros (git-fixes).\n- drm/msm/dpu: drop MSM_ENC_VBLANK support (stable-fixes).\n- drm/msm/dpu: move dpu_encoder's connector assignment to atomic_enable() (git-fixes).\n- drm/msm/dpu: split dpu_encoder_wait_for_event into two functions (stable-fixes).\n- drm/msm/dpu: take plane rotation into account for wide planes (git-fixes).\n- drm/msm/dpu: try multirect based on mdp clock limits (stable-fixes).\n- drm/msm/dpu: use drmm-managed allocation for dpu_encoder_phys (stable-fixes).\n- drm/msm/mdss: Rename path references to mdp_path (stable-fixes).\n- drm/msm/mdss: switch mdss to use devm_of_icc_get() (stable-fixes).\n- drm/msm: Reduce fallout of fence signaling vs reclaim hangs (stable-fixes).\n- drm/nouveau: prime: fix refcount underflow (git-fixes).\n- drm/panel: nt36523: Set 120Hz fps for xiaomi,elish panels (stable-fixes).\n- drm/radeon/evergreen_cs: Clean up errors in evergreen_cs.c (bsc#1229024).\n- drm/radeon: Remove __counted_by from StateArray.states[] (git-fixes).\n- drm/rockchip: vop2: clear afbc en and transform bit for cluster window at linear mode (stable-fixes).\n- drm/virtio: Fix type of dma-fence context variable (git-fixes).\n- drm/vmwgfx: Fix a deadlock in dma buf fence polling (git-fixes).\n- drm/vmwgfx: Fix overlay when using Screen Targets (git-fixes).\n- drm/vmwgfx: Fix prime with external buffers (git-fixes).\n- efi/libstub: Zero initialize heap allocated struct screen_info (git-fixes).\n- evm: do not copy up 'security.evm' xattr (git-fixes).\n- firmware: cirrus: cs_dsp: Initialize debugfs_root to invalid (stable-fixes).\n- fs/netfs/fscache_cookie: add missing \"n_accesses\" check (bsc#1229455).\n- fuse: Initialize beyond-EOF page contents before setting uptodate (bsc#1229456).\n- genirq/cpuhotplug, x86/vector: Prevent vector leak during CPU offline (git-fixes).\n- genirq/generic_chip: Make irq_remove_generic_chip() irqdomain aware (git-fixes).\n- genirq/matrix: Exclude managed interrupts in irq_matrix_allocated() (git-fixes).\n- gfs2: setattr_chown: Add missing initialization (git-fixes).\n- gpio: mlxbf3: Support shutdown() function (git-fixes).\n- gpio: prevent potential speculation leaks in gpio_device_get_desc() (stable-fixes).\n- gpio: sysfs: extend the critical section for unregistering sysfs devices (stable-fixes).\n- gss_krb5: Fix the error handling path for crypto_sync_skcipher_setkey (git-fixes).\n- hfs: fix to initialize fields of hfs_inode_info after hfs_alloc_inode() (git-fixes).\n- hwmon: (ltc2992) Avoid division by zero (stable-fixes).\n- hwmon: (ltc2992) Fix memory leak in ltc2992_parse_dt() (git-fixes).\n- hwmon: (pc87360) Bounds check data-\u003einnr usage (stable-fixes).\n- i2c: Fix conditional for substituting empty ACPI functions (stable-fixes).\n- i2c: Use IS_REACHABLE() for substituting empty ACPI functions (git-fixes).\n- i2c: qcom-geni: Add missing clk_disable_unprepare in geni_i2c_runtime_resume (git-fixes).\n- i2c: qcom-geni: Add missing geni_icc_disable in geni_i2c_runtime_resume (git-fixes).\n- i2c: qcom-geni: Add missing geni_icc_disable in geni_i2c_runtime_resume (git-fixes).\n- i2c: riic: avoid potential division by zero (stable-fixes).\n- i2c: smbus: Improve handling of stuck alerts (git-fixes).\n- i2c: smbus: Send alert notifications to all devices if source not found (git-fixes).\n- i2c: stm32f7: Add atomic_xfer method to driver (stable-fixes).\n- i3c: mipi-i3c-hci: Do not unmap region not mapped for transfer (stable-fixes).\n- i3c: mipi-i3c-hci: Remove BUG() when Ring Abort request times out (stable-fixes).\n- i915/perf: Remove code to update PWR_CLK_STATE for gen12 (git-fixes).\n- ice: Fix NULL pointer access, if PF does not support SRIOV_LAG (bsc#1228737).\n- io_uring/advise: support 64-bit lengths (git-fixes).\n- io_uring: Drop per-ctx dummy_ubuf (git-fixes).\n- io_uring: Fix probe of disabled operations (git-fixes).\n- io_uring: fix io_match_task must_hold (git-fixes).\n- io_uring: tighten task exit cancellations (git-fixes).\n- iommu/amd: Convert comma to semicolon (git-fixes).\n- iommu/vt-d: Fix identity map bounds in si_domain_init() (git-fixes).\n- iommufd/device: Fix hwpt at err_unresv in iommufd_device_do_replace() (git-fixes).\n- ip6_tunnel: Fix broken GRO (bsc#1229444).\n- ipv6: sr: fix incorrect unregister order (git-fixes).\n- irqdomain: Fixed unbalanced fwnode get and put (git-fixes).\n- jfs: Fix shift-out-of-bounds in dbDiscardAG (git-fixes).\n- jfs: define xtree root and page independently (git-fixes).\n- jfs: fix null ptr deref in dtInsertEntry (git-fixes).\n- jump_label: Clarify condition in static_key_fast_inc_not_disabled() (git-fixes).\n- jump_label: Fix concurrency issues in static_key_slow_dec() (git-fixes).\n- jump_label: Fix the fix, brown paper bags galore (git-fixes).\n- jump_label: Simplify and clarify static_key_fast_inc_cpus_locked() (git-fixes).\n- kABI fix of: virtio-crypto: handle config changed by work queue (git-fixes).\n- kABI workaround for sound core UMP conversion (stable-fixes).\n- kabi fix for KVM: s390: fix LPSWEY handling (bsc#1227634 git-fixes).\n- kabi fix for SUNRPC: add a missing rpc_stat for TCP TLS (git-fixes).\n- kabi/severities: ignore kABI for FireWire sound local symbols (bsc#1208783)\n- kabi/severity: add nvme common code The nvme common code is also allowed to change the data structures, there are only internal users.\n- kcov: properly check for softirq context (git-fixes).\n- kernel-binary: generate and install compile_commands.json (bsc#1228971)\n- kernfs: Convert kernfs_path_from_node_locked() from strlcpy() to strscpy() (bsc#1229134).\n- kernfs: fix false-positive WARN(nr_mmapped) in kernfs_drain_open_files (git-fixes).\n- kprobes: Fix to check symbol prefixes correctly (git-fixes).\n- kprobes: Prohibit probing on CFI preamble symbol (git-fixes).\n- kvm: s390: Reject memory region operations for ucontrol VMs (git-fixes bsc#1229168).\n- libbpf: Add missing LIBBPF_API annotation to libbpf_set_memlock_rlim API (git-fixes).\n- libbpf: Apply map_set_def_max_entries() for inner_maps on creation (git-fixes).\n- libbpf: Fix faccessat() usage on Android (git-fixes).\n- libbpf: Use OPTS_SET() macro in bpf_xdp_query() (git-fixes).\n- md-cluster: fix hanging issue while a new disk adding (bsc#1223395).\n- md-cluster: fix hanging issue while a new disk adding (bsc#1223395).\n- md-cluster: fix no recovery job when adding/re-adding a disk (bsc#1223395).\n- md-cluster: fix no recovery job when adding/re-adding a disk (bsc#1223395).\n- md-cluster: keeping kabi compatibility for upstream commit 35a0a409fa26 (bsc#1223395).\n- md/md-bitmap: fix writing non bitmap pages (git-fixes).\n- md/raid1: set max_sectors during early return from choose_slow_rdev() (git-fixes).\n- md/raid1: support read error check (git-fixes).\n- md/raid5: fix deadlock that raid5d() wait for itself to clear MD_SB_CHANGE_PENDING (git-fixes).\n- md/raid5: fix spares errors about rcu usage (git-fixes).\n- md/raid5: recheck if reshape has finished with device_lock held (git-fixes).\n- md: Do not wait for MD_RECOVERY_NEEDED for HOT_REMOVE_DISK ioctl (git-fixes).\n- md: add a mddev_add_trace_msg helper (git-fixes).\n- md: add check for sleepers in md_wakeup_thread() (git-fixes).\n- md: change the return value type of md_write_start to void (git-fixes).\n- md: do not account sync_io if iostats of the disk is disabled (git-fixes).\n- md: do not delete safemode_timer in mddev_suspend (git-fixes).\n- md: factor out a helper exceed_read_errors() to check read_errors (git-fixes).\n- md: fix a suspicious RCU usage warning (git-fixes).\n- media: Revert \"media: dvb-usb: Fix unexpected infinite loop in dvb_usb_read_remote_control()\" (git-fixes).\n- media: amphion: Remove lock in s_ctrl callback (stable-fixes).\n- media: drivers/media/dvb-core: copy user arrays safely (stable-fixes).\n- media: pci: cx23885: check cx23885_vdev_init() return (stable-fixes).\n- media: uvcvideo: Add quirk for invalid dev_sof in Logitech C920 (git-fixes).\n- media: uvcvideo: Disable autosuspend for Insta360 Link (stable-fixes).\n- media: uvcvideo: Fix the bandwdith quirk on USB 3.x (stable-fixes).\n- media: uvcvideo: Ignore empty TS packets (stable-fixes).\n- media: uvcvideo: Quirk for invalid dev_sof in Logitech C922 (stable-fixes).\n- media: xc2028: avoid use-after-free in load_firmware_cb() (stable-fixes).\n- memcg: protect concurrent access to mem_cgroup_idr (git-fixes).\n- memory: stm32-fmc2-ebi: check regmap_read return value (stable-fixes).\n- memory: tegra: Skip SID programming if SID registers are not set (stable-fixes).\n- minmax: add a few more MIN_T/MAX_T users (bsc#1229024).\n- minmax: avoid overly complicated constant expressions in VM code (bsc#1229024).\n- minmax: do not use max() in situations that want a C constant expression (bsc#1229024).\n- minmax: fix up min3() and max3() too (bsc#1229024).\n- minmax: improve macro expansion and type checking (bsc#1229024).\n- minmax: make generic MIN() and MAX() macros available everywhere (bsc#1229024).\n- minmax: simplify and clarify min_t()/max_t() implementation (bsc#1229024).\n- minmax: simplify min()/max()/clamp() implementation (bsc#1229024).\n- mm, kmsan: fix infinite recursion due to RCU critical section (git-fixes).\n- mm: prevent derefencing NULL ptr in pfn_section_valid() (git-fixes).\n- mmc: dw_mmc: allow biu and ciu clocks to defer (git-fixes).\n- mmc: mmc_test: Fix NULL dereference on allocation failure (git-fixes).\n- mmc: mtk-sd: receive cmd8 data when hs400 tuning fail (git-fixes).\n- net/iucv: fix the allocation size of iucv_path_table array (git-fixes bsc#1229451).\n- net/iucv: fix use after free in iucv_sock_close() (bsc#1228973).\n- net/rds: fix possible cp null dereference (git-fixes).\n- net/sched: initialize noop_qdisc owner (git-fixes).\n- net: drop bad gso csum_start and offset in virtio_net_hdr (git-fixes).\n- net: ethernet: mtk_wed: fix use-after-free panic in mtk_wed_setup_tc_block_cb() (git-fixes).\n- net: fix sk_memory_allocated_{add|sub} vs softirqs (bsc#1228757).\n- net: mana: Add support for page sizes other than 4KB on ARM64 (jsc#PED-8491 bsc#1226530).\n- net: mana: Fix RX buf alloc_size alignment and atomic op panic (bsc#1229086).\n- net: mana: Fix doorbell out of order violation and avoid unnecessary doorbell rings (bsc#1229154).\n- net: mana: Fix race of mana_hwc_post_rx_wqe and new hwc response (git-fixes).\n- net: missing check virtio (git-fixes).\n- net: phy: micrel: Fix the KSZ9131 MDI-X status issue (git-fixes).\n- net: phy: realtek: add support for RTL8366S Gigabit PHY (git-fixes).\n- net: usb: qmi_wwan: fix memory leak for not ip packets (git-fixes).\n- net: usb: sr9700: fix uninitialized variable use in sr_mdio_read (git-fixes).\n- netfs, fscache: export fscache_put_volume() and add fscache_try_get_volume() (bsc#1228459 bsc#1228462).\n- nfc: pn533: Add poll mod list filling check (git-fixes).\n- nfs: do not invalidate dentries on transient errors (git-fixes).\n- nfs: expose /proc/net/sunrpc/nfs in net namespaces (git-fixes).\n- nfs: make the rpc_stat per net namespace (git-fixes).\n- nfs: pass explicit offset/count to trace events (git-fixes).\n- nfs: propagate readlink errors in nfs_symlink_filler (git-fixes).\n- nouveau/firmware: use dma non-coherent allocator (git-fixes).\n- nvme-multipath: find NUMA path only for online numa-node (git-fixes).\n- nvme-multipath: implement \"queue-depth\" iopolicy (bsc#1227706).\n- nvme-multipath: prepare for \"queue-depth\" iopolicy (bsc#1227706).\n- nvme-pci: Fix the instructions for disabling power management (git-fixes).\n- nvme-pci: add missing condition check for existence of mapped data (git-fixes).\n- nvme-pci: do not directly handle subsys reset fallout (bsc#1220066).\n- nvme-sysfs: add 'tls_configured_key' sysfs attribute (bsc#1221857).\n- nvme-sysfs: add 'tls_keyring' attribute (bsc#1221857).\n- nvme-tcp: check for invalidated or revoked key (bsc#1221857).\n- nvme-tcp: sanitize TLS key handling (bsc#1221857).\n- nvme: add a newline to the 'tls_key' sysfs attribute (bsc#1221857).\n- nvme: adjust multiples of NVME_CTRL_PAGE_SIZE in offset (git-fixes).\n- nvme: avoid double free special payload (git-fixes).\n- nvme: fix NVME_NS_DEAC may incorrectly identifying the disk as EXT_LBA (git-fixes).\n- nvme: fixup comment for nvme RDMA Provider Type (git-fixes).\n- nvme: split off TLS sysfs attributes into a separate group (bsc#1221857).\n- nvme: tcp: remove unnecessary goto statement (bsc#1221857).\n- nvme_core: scan namespaces asynchronously (bsc#1224105).\n- nvmet-auth: fix nvmet_auth hash error handling (git-fixes).\n- nvmet: always initialize cqe.result (git-fixes).\n- nvmet: do not return 'reserved' for empty TSAS values (git-fixes).\n- nvmet: fix a possible leak when destroy a ctrl during qp establishment (git-fixes).\n- nvmet: make 'tsas' attribute idempotent for RDMA (git-fixes).\n- ocfs2: strict bound check before memcmp in ocfs2_xattr_find_entry() (bsc#1228410).\n- padata: Fix possible divide-by-0 panic in padata_mt_helper() (git-fixes).\n- perf/smmuv3: Enable HiSilicon Erratum 162001900 quirk for HIP08/09 (git-fixes).\n- pinctrl: mediatek: common-v2: Fix broken bias-disable for PULL_PU_PD_RSEL_TYPE (git-fixes).\n- pinctrl: rockchip: correct RK3328 iomux width flag for GPIO2-B pins (git-fixes).\n- pinctrl: single: fix potential NULL dereference in pcs_get_function() (git-fixes).\n- pinctrl: starfive: jh7110: Correct the level trigger configuration of iev register (git-fixes).\n- platform/chrome: cros_ec_proto: Lock device when updating MKBP version (git-fixes).\n- platform/chrome: cros_ec_proto: Lock device when updating MKBP version (git-fixes).\n- platform/surface: aggregator: Fix warning when controller is destroyed in probe (git-fixes).\n- platform/x86/amd/hsmp: Add support for ACPI based probing (jsc#PED-8779).\n- platform/x86/amd/hsmp: Cache pci_dev in struct hsmp_socket (jsc#PED-8779).\n- platform/x86/amd/hsmp: Change devm_kzalloc() to devm_kcalloc() (jsc#PED-8779).\n- platform/x86/amd/hsmp: Check HSMP support on AMD family of processors (jsc#PED-8779).\n- platform/x86/amd/hsmp: Check num_sockets against MAX_AMD_SOCKETS (jsc#PED-8779).\n- platform/x86/amd/hsmp: Create static func to handle platdev (jsc#PED-8779).\n- platform/x86/amd/hsmp: Define a struct to hold mailbox regs (jsc#PED-8779).\n- platform/x86/amd/hsmp: Move dev from platdev to hsmp_socket (jsc#PED-8779).\n- platform/x86/amd/hsmp: Move hsmp_test to probe (jsc#PED-8779).\n- platform/x86/amd/hsmp: Non-ACPI support for AMD F1A_M00~0Fh (jsc#PED-8779).\n- platform/x86/amd/hsmp: Remove extra parenthesis and add a space (jsc#PED-8779).\n- platform/x86/amd/hsmp: Restructure sysfs group creation (jsc#PED-8779).\n- platform/x86/amd/hsmp: switch to use device_add_groups() (jsc#PED-8779).\n- platform/x86/intel/ifs: Initialize union ifs_status to zero (git-fixes).\n- platform/x86: lg-laptop: fix %s null argument warning (stable-fixes).\n- power: supply: axp288_charger: Fix constant_charge_voltage writes (git-fixes).\n- power: supply: axp288_charger: Round constant_charge_voltage writes down (git-fixes).\n- power: supply: qcom_battmgr: return EAGAIN when firmware service is not up (git-fixes).\n- powerpc/64: Set _IO_BASE to POISON_POINTER_DELTA not 0 for CONFIG_PCI=n (bsc#1194869).\n- powerpc/io: Avoid clang null pointer arithmetic warnings (bsc#1194869).\n- powerpc/kexec: make the update_cpus_node() function public (bsc#1194869).\n- powerpc/kexec: split CONFIG_KEXEC_FILE and CONFIG_CRASH_DUMP (bsc#1194869).\n- powerpc/kexec_file: fix cpus node update to FDT (bsc#1194869).\n- powerpc/pseries: Add failure related checks for h_get_mpp and h_get_ppp (bsc#1194869).\n- powerpc/pseries: Whitelist dtl slub object for copying to userspace (bsc#1194869).\n- powerpc/radix: Move some functions into #ifdef CONFIG_KVM_BOOK3S_HV_POSSIBLE (bsc#1194869).\n- powerpc/topology: Check if a core is online (bsc#1214285 bsc#1205462 ltc#200161 ltc#200588 git-fixes).\n- powerpc/xmon: Check cpu id in commands \"c#\", \"dp#\" and \"dx#\" (bsc#1194869).\n- powerpc: fix a file leak in kvm_vcpu_ioctl_enable_cap() (bsc#1194869).\n- powerpc: xor_vmx: Add '-mhard-float' to CFLAGS (bsc#1194869).\n- printk/panic: Allow cpu backtraces to be written into ringbuffer during panic (bsc#1225607).\n- reiserfs: fix uninit-value in comp_keys (git-fixes).\n- rtc: nct3018y: fix possible NULL dereference (stable-fixes).\n- s390/cpum_cf: Fix endless loop in CF_DIAG event stop (git-fixes bsc#1229171).\n- s390/dasd: fix error checks in dasd_copy_pair_store() (git-fixes bsc#1229173).\n- s390/dasd: fix error recovery leading to data corruption on ESE devices (git-fixes bsc#1229452).\n- s390/pci: Add missing virt_to_phys() for directed DIBV (git-fixes bsc#1229174).\n- s390/pci: Allow allocation of more than 1 MSI interrupt (git-fixes bsc#1229172).\n- s390/pci: Refactor arch_setup_msi_irqs() (git-fixes bsc#1229172).\n- s390/pkey: harmonize pkey s390 debug feature calls (bsc#1228720).\n- s390/pkey: introduce dynamic debugging for pkey (bsc#1228720).\n- s390/sclp: Prevent release of buffer in I/O (git-fixes bsc#1229169).\n- s390/uv: Panic for set and remove shared access UVC errors (git-fixes bsc#1229170).\n- samples/bpf: syscall_tp_user: Fix array out-of-bound access (git-fixes).\n- samples/bpf: syscall_tp_user: Rename num_progs into nr_tests (git-fixes).\n- sbitmap: use READ_ONCE to access map-\u003eword (stable-fixes).\n- scsi: lpfc: Allow DEVICE_RECOVERY mode after RSCN receipt if in PRLI_ISSUE state (bsc#1228857).\n- scsi: lpfc: Cancel ELS WQE instead of issuing abort when SLI port is inactive (bsc#1228857).\n- scsi: lpfc: Fix handling of fully recovered fabric node in dev_loss callbk (bsc#1228857).\n- scsi: lpfc: Fix incorrect request len mbox field when setting trunking via sysfs (bsc#1228857).\n- scsi: lpfc: Handle mailbox timeouts in lpfc_get_sfp_info (bsc#1228857).\n- scsi: lpfc: Relax PRLI issue conditions after GID_FT response (bsc#1228857).\n- scsi: lpfc: Revise lpfc_prep_embed_io routine with proper endian macro usages (bsc#1228857).\n- scsi: lpfc: Update lpfc version to 14.4.0.3 (bsc#1228857).\n- scsi: qla2xxx: Avoid possible run-time warning with long model_num (bsc#1228850).\n- scsi: qla2xxx: Complete command early within lock (bsc#1228850).\n- scsi: qla2xxx: Convert comma to semicolon (bsc#1228850).\n- scsi: qla2xxx: Drop driver owner assignment (bsc#1228850).\n- scsi: qla2xxx: During vport delete send async logout explicitly (bsc#1228850).\n- scsi: qla2xxx: Fix debugfs output for fw_resource_count (bsc#1228850).\n- scsi: qla2xxx: Fix flash read failure (bsc#1228850).\n- scsi: qla2xxx: Fix for possible memory corruption (bsc#1228850).\n- scsi: qla2xxx: Fix optrom version displayed in FDMI (bsc#1228850).\n- scsi: qla2xxx: Indent help text (bsc#1228850).\n- scsi: qla2xxx: Reduce fabric scan duplicate code (bsc#1228850).\n- scsi: qla2xxx: Remove unused struct 'scsi_dif_tuple' (bsc#1228850).\n- scsi: qla2xxx: Return ENOBUFS if sg_cnt is more than one for ELS cmds (bsc#1228850).\n- scsi: qla2xxx: Unable to act on RSCN for port online (bsc#1228850).\n- scsi: qla2xxx: Update version to 10.02.09.300-k (bsc#1228850).\n- scsi: qla2xxx: Use QP lock to search for bsg (bsc#1228850).\n- scsi: qla2xxx: validate nvme_local_port correctly (bsc#1228850).\n- selftest/bpf: Add map_in_maps with BPF_MAP_TYPE_PERF_EVENT_ARRAY values (git-fixes).\n- selftests/bpf: Add a test to verify previous stacksafe() fix (bsc#1225903).\n- selftests/bpf: Add assert for user stacks in test_task_stack (git-fixes).\n- selftests/bpf: Add netkit to tc_redirect selftest (git-fixes).\n- selftests/bpf: De-veth-ize the tc_redirect test case (git-fixes).\n- selftests/bpf: Disable IPv6 for lwt_redirect test (git-fixes).\n- selftests/bpf: Fix erroneous bitmask operation (git-fixes).\n- selftests/bpf: Fix issues in setup_classid_environment() (git-fixes).\n- selftests/bpf: Fix potential premature unload in bpf_testmod (git-fixes).\n- selftests/bpf: Fix pyperf180 compilation failure with clang18 (git-fixes).\n- selftests/bpf: Fix the flaky tc_redirect_dtime test (git-fixes).\n- selftests/bpf: Fix up xdp bonding test wrt feature flags (git-fixes).\n- selftests/bpf: Make linked_list failure test more robust (git-fixes).\n- selftests/bpf: Relax time_tai test for equal timestamps in tai_forward (git-fixes).\n- selftests/bpf: Skip module_fentry_shadow test when bpf_testmod is not available (git-fixes).\n- selftests/bpf: Wait for the netstamp_needed_key static key to be turned on (git-fixes).\n- selftests/bpf: fix RELEASE=1 build for tc_opts (git-fixes).\n- selftests/bpf: fix bpf_loop_bench for new callback verification scheme (git-fixes).\n- selftests/bpf: fix compiler warnings in RELEASE=1 mode (git-fixes).\n- selftests/bpf: satisfy compiler by having explicit return in btf test (git-fixes).\n- serial: core: check uartclk for zero to avoid divide by zero (stable-fixes).\n- soc: qcom: cmd-db: Map shared memory as WC, not WB (git-fixes).\n- soc: qcom: pmic_glink: Actually communicate when remote goes down (git-fixes).\n- soundwire: stream: fix programming slave ports for non-continous port maps (git-fixes).\n- spi: Add empty versions of ACPI functions (stable-fixes).\n- spi: microchip-core: fix init function not setting the master and motorola modes (git-fixes).\n- spi: microchip-core: switch to use modern name (stable-fixes).\n- spi: spi-fsl-lpspi: Fix scldiv calculation (git-fixes).\n- spi: spidev: Add missing spi_device_id for bh2228fv (git-fixes).\n- squashfs: squashfs_read_data need to check if the length is 0 (git-fixes).\n- ssb: Fix division by zero issue in ssb_calc_clock_rate (stable-fixes).\n- staging: iio: resolver: ad2s1210: fix use before initialization (stable-fixes).\n- staging: ks7010: disable bh on tx_dev_lock (stable-fixes).\n- string.h: Introduce memtostr() and memtostr_pad() (bsc#1228849).\n- sunrpc: add a struct rpc_stats arg to rpc_create_args (git-fixes).\n- swiotlb: do not set total_used to 0 in swiotlb_create_debugfs_files() (git-fixes).\n- swiotlb: fix swiotlb_bounce() to do partial sync's correctly (git-fixes).\n- syscalls: fix compat_sys_io_pgetevents_time64 usage (git-fixes).\n- thermal/drivers/broadcom: Fix race between removal and clock disable (git-fixes).\n- thermal: bcm2835: Convert to platform remove callback returning void (stable-fixes).\n- thunderbolt: Mark XDomain as unplugged when router is removed (stable-fixes).\n- tools/perf: Fix perf bench epoll to enable the run when some CPU's are offline (bsc#1227747).\n- tools/perf: Fix perf bench futex to enable the run when some CPU's are offline (bsc#1227747).\n- tools/perf: Fix timing issue with parallel threads in perf bench wake-up-parallel (bsc#1227747).\n- tools/resolve_btfids: Fix comparison of distinct pointer types warning in resolve_btfids (git-fixes).\n- tools/resolve_btfids: Fix cross-compilation to non-host endianness (git-fixes).\n- tools/resolve_btfids: Refactor set sorting with types from btf_ids.h (git-fixes).\n- tools/resolve_btfids: fix build with musl libc (git-fixes).\n- trace/pid_list: Change gfp flags in pid_list_fill_irq() (git-fixes).\n- tracing: Return from tracing_buffers_read() if the file has been closed (bsc#1229136 git-fixes).\n- tty: atmel_serial: use the correct RTS flag (git-fixes).\n- tty: serial: fsl_lpuart: mark last busy before uart_add_one_port (git-fixes).\n- usb: cdnsp: fix for Link TRB with TC (git-fixes).\n- usb: cdnsp: fix incorrect index in cdnsp_get_hw_deq function (git-fixes).\n- usb: core: sysfs: Unmerge @usb3_hardware_lpm_attr_group in remove_power_attributes() (git-fixes).\n- usb: dwc3: core: Skip setting event buffers for host only controllers (stable-fixes).\n- usb: dwc3: omap: add missing depopulate in probe error path (git-fixes).\n- usb: dwc3: st: add missing depopulate in probe error path (git-fixes).\n- usb: dwc3: st: fix probed platform device ref count on probe error path (git-fixes).\n- usb: gadget: core: Check for unset descriptor (git-fixes).\n- usb: gadget: fsl: Increase size of name buffer for endpoints (stable-fixes).\n- usb: gadget: u_audio: Check return codes from usb_ep_enable and config_ep_by_speed (git-fixes).\n- usb: gadget: u_serial: Set start_delayed during suspend (git-fixes).\n- usb: gadget: uvc: cleanup request when not in correct state (stable-fixes).\n- usb: typec: fsa4480: Add support to swap SBU orientation (git-fixes).\n- usb: typec: fsa4480: Check if the chip is really there (git-fixes).\n- usb: typec: fsa4480: Relax CHIP_ID check (git-fixes).\n- usb: typec: fsa4480: add support for Audio Accessory Mode (git-fixes).\n- usb: typec: fsa4480: rework mux \u0026 switch setup to handle more states (git-fixes).\n- usb: vhci-hcd: Do not drop references before new references are gained (stable-fixes).\n- vfio/pci: fix potential memory leak in vfio_intx_enable() (git-fixes).\n- vhost-scsi: Handle vhost_vq_work_queue failures for events (git-fixes).\n- vhost-vdpa: switch to use vmf_insert_pfn() in the fault handler (git-fixes).\n- vhost/vsock: always initialize seqpacket_allow (git-fixes).\n- vhost: Release worker mutex during flushes (git-fixes).\n- vhost: Use virtqueue mutex for swapping worker (git-fixes).\n- virt: guest_memfd: fix reference leak on hwpoisoned page (git-fixes).\n- virtio-crypto: handle config changed by work queue (git-fixes).\n- virtio: reenable config if freezing device failed (git-fixes).\n- virtio_net: use u64_stats_t infra to avoid data-races (git-fixes).\n- virtiofs: forbid newlines in tags (bsc#1229940).\n- wifi: ath12k: fix memory leak in ath12k_dp_rx_peer_frag_setup() (stable-fixes).\n- wifi: ath12k: fix soft lockup on suspend (git-fixes).\n- wifi: brcmfmac: cfg80211: Handle SSID based pmksa deletion (git-fixes).\n- wifi: cfg80211: fix reporting failed MLO links status with cfg80211_connect_done (git-fixes).\n- wifi: iwlwifi: fw: fix wgds rev 3 exact size (git-fixes).\n- wifi: mac80211: use monitor sdata with driver only if desired (git-fixes).\n- wifi: mwifiex: duplicate static structs used in driver instances (git-fixes).\n- wifi: nl80211: disallow setting special AP channel widths (stable-fixes).\n- wifi: nl80211: do not give key data to userspace (stable-fixes).\n- wifi: rtw88: usb: Fix disconnection after beacon loss (stable-fixes).\n- wifi: wfx: repair open network AP mode (git-fixes).\n- workqueue: Improve scalability of workqueue watchdog touch (bsc#1193454).\n- workqueue: wq_watchdog_touch is always called with valid CPU (bsc#1193454).\n- x86/asm: Use %c/%n instead of %P operand modifier in asm templates (git-fixes).\n- x86/entry/64: Remove obsolete comment on tracing vs. SYSRET (git-fixes).\n- x86/mm: Fix pti_clone_entry_text() for i386 (git-fixes).\n- x86/mm: Fix pti_clone_pgtable() alignment assumption (git-fixes).\n- x86/mtrr: Check if fixed MTRRs exist before saving them (git-fixes).\n- x86/numa: Fix SRAT lookup of CFMWS ranges with numa_fill_memblks() (git-fixes).\n- x86/numa: Fix the address overlap check in numa_fill_memblks() (git-fixes).\n- x86/numa: Fix the sort compare func used in numa_fill_memblks() (git-fixes).\n- x86/numa: Introduce numa_fill_memblks() (git-fixes).\n- x86/pci: Skip early E820 check for ECAM region (git-fixes).\n- x86/xen: Convert comma to semicolon (git-fixes).\n- xfs: Fix missing interval for missing_owner in xfs fsmap (git-fixes).\n- xfs: Fix the owner setting issue for rmap query in xfs fsmap (git-fixes).\n- xfs: allow cross-linking special files without project quota (git-fixes).\n- xfs: allow symlinks with short remote targets (bsc#1229160).\n- xfs: allow unlinked symlinks and dirs with zero size (git-fixes).\n- xfs: attr forks require attr, not attr2 (git-fixes).\n- xfs: convert comma to semicolon (git-fixes).\n- xfs: do not use current-\u003ejournal_info (git-fixes).\n- xfs: fix unlink vs cluster buffer instantiation race (git-fixes).\n- xfs: honor init_xattrs in xfs_init_new_inode for !ATTR fs (git-fixes).\n- xfs: journal geometry is not properly bounds checked (git-fixes).\n- xfs: match lock mode in xfs_buffered_write_iomap_begin() (git-fixes).\n- xfs: require XFS_SB_FEAT_INCOMPAT_LOG_XATTRS for attr log intent item recovery (git-fixes).\n- xfs: upgrade the extent counters in xfs_reflink_end_cow_extent later (git-fixes).\n- xfs: use XFS_BUF_DADDR_NULL for daddrs in getfsmap code (git-fixes).\n- xfs: use consistent uid/gid when grabbing dquots for inodes (git-fixes).\n- xhci: Fix Panther point NULL pointer deref at full-speed re-enumeration (git-fixes).\n- xprtrdma: Fix rpcrdma_reqs_reset() (git-fixes).\n","status":"published","published":"2025-02-03T08:55:15Z","modified":"2026-03-23T04:50:42.230219Z","updated_at":"2026-11-02T15:53:59.381172Z"},{"id":"USN-7007-1","title":"linux, linux-aws, linux-aws-5.15, linux-gcp, linux-gcp-5.15, linux-gke, linux-gkeop, linux-gkeop-5.15, linux-hwe-5.15, linux-ibm, linux-intel-iotg, linux-intel-iotg-5.15, linux-kvm, linux-nvidia, linux-oracle, linux-raspi vulnerabilities","description":"\nChenyuan Yang discovered that the CEC driver driver in the Linux kernel\ncontained a use-after-free vulnerability. A local attacker could use this\nto cause a denial of service (system crash) or possibly execute arbitrary\ncode. (CVE-2024-23848)\n\nChenyuan Yang discovered that the USB Gadget subsystem in the Linux kernel\ndid not properly check for the device to be enabled before writing. A local\nattacker could possibly use this to cause a denial of service.\n(CVE-2024-25741)\n\nIt was discovered that the JFS file system contained an out-of-bounds read\nvulnerability when printing xattr debug information. A local attacker could\nuse this to cause a denial of service (system crash). (CVE-2024-40902)\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  - M68K architecture;\n  - MIPS architecture;\n  - PowerPC architecture;\n  - RISC-V architecture;\n  - x86 architecture;\n  - Block layer subsystem;\n  - Cryptographic API;\n  - Accessibility subsystem;\n  - ACPI drivers;\n  - Serial ATA and Parallel ATA drivers;\n  - Drivers core;\n  - Bluetooth drivers;\n  - Character device driver;\n  - CPU frequency scaling framework;\n  - Hardware crypto device drivers;\n  - Buffer Sharing and Synchronization framework;\n  - DMA engine subsystem;\n  - FPGA Framework;\n  - GPIO subsystem;\n  - GPU drivers;\n  - Greybus drivers;\n  - HID subsystem;\n  - HW tracing;\n  - I2C subsystem;\n  - IIO subsystem;\n  - InfiniBand drivers;\n  - Input Device (Mouse) drivers;\n  - Macintosh device drivers;\n  - Multiple devices driver;\n  - Media drivers;\n  - VMware VMCI Driver;\n  - Network drivers;\n  - Near Field Communication (NFC) drivers;\n  - NVME drivers;\n  - Pin controllers subsystem;\n  - PTP clock framework;\n  - S/390 drivers;\n  - SCSI drivers;\n  - SoundWire subsystem;\n  - Greybus lights staging drivers;\n  - Media staging drivers;\n  - Thermal drivers;\n  - TTY drivers;\n  - USB subsystem;\n  - DesignWare USB3 driver;\n  - Framebuffer layer;\n  - ACRN Hypervisor Service Module driver;\n  - eCrypt file system;\n  - File systems infrastructure;\n  - Ext4 file system;\n  - F2FS file system;\n  - JFFS2 file system;\n  - JFS file system;\n  - NILFS2 file system;\n  - NTFS3 file system;\n  - SMB network file system;\n  - IOMMU subsystem;\n  - Memory management;\n  - Netfilter;\n  - BPF subsystem;\n  - Kernel debugger infrastructure;\n  - DMA mapping infrastructure;\n  - IRQ subsystem;\n  - Tracing infrastructure;\n  - 9P file system network protocol;\n  - B.A.T.M.A.N. meshing protocol;\n  - CAN network layer;\n  - Ceph Core library;\n  - Networking core;\n  - IPv4 networking;\n  - IPv6 networking;\n  - IUCV driver;\n  - MAC80211 subsystem;\n  - Multipath TCP;\n  - NET/ROM layer;\n  - NFC subsystem;\n  - Open vSwitch;\n  - Network traffic control;\n  - TIPC protocol;\n  - TLS protocol;\n  - Unix domain sockets;\n  - Wireless networking;\n  - XFRM subsystem;\n  - ALSA framework;\n  - SoC Audio for Freescale CPUs drivers;\n  - Kirkwood ASoC drivers;\n(CVE-2024-40961, CVE-2024-38597, CVE-2024-39468, CVE-2024-36978,\nCVE-2024-42161, CVE-2024-38573, CVE-2024-40905, CVE-2024-42094,\nCVE-2024-36894, CVE-2024-40914, CVE-2024-40956, CVE-2024-42106,\nCVE-2024-38610, CVE-2024-39506, CVE-2024-42098, CVE-2024-42232,\nCVE-2024-38590, CVE-2024-39488, CVE-2024-42127, CVE-2024-41006,\nCVE-2024-42131, CVE-2024-41005, CVE-2024-40963, CVE-2024-38559,\nCVE-2024-42130, CVE-2024-37078, CVE-2024-42082, CVE-2024-40984,\nCVE-2024-38560, CVE-2024-42090, CVE-2024-33621, CVE-2024-40974,\nCVE-2024-42115, CVE-2024-40971, CVE-2024-40943, CVE-2024-38627,\nCVE-2024-38548, CVE-2024-40934, CVE-2024-38579, CVE-2024-38558,\nCVE-2024-39495, CVE-2023-52884, CVE-2024-42225, CVE-2024-38659,\nCVE-2024-40927, CVE-2024-40967, CVE-2024-38624, CVE-2024-38583,\nCVE-2024-41047, CVE-2024-38623, CVE-2024-39509, CVE-2024-36971,\nCVE-2024-42120, CVE-2024-38589, CVE-2024-36270, CVE-2024-42105,\nCVE-2024-36032, CVE-2024-42101, CVE-2024-40908, CVE-2024-42089,\nCVE-2024-39482, CVE-2024-38662, CVE-2024-41007, CVE-2024-38635,\nCVE-2023-52887, CVE-2024-40912, CVE-2024-41027, CVE-2024-38598,\nCVE-2024-38381, CVE-2024-39503, CVE-2024-39301, CVE-2024-40988,\nCVE-2024-41000, CVE-2024-39507, CVE-2024-35247, CVE-2024-39277,\nCVE-2024-42229, CVE-2024-42085, CVE-2024-35927, CVE-2024-42224,\nCVE-2024-38567, CVE-2024-42097, CVE-2024-41049, CVE-2024-39466,\nCVE-2024-40957, CVE-2024-40978, CVE-2024-42093, CVE-2024-40937,\nCVE-2024-41034, CVE-2024-41048, CVE-2024-39471, CVE-2024-39502,\nCVE-2024-38555, CVE-2024-40970, CVE-2024-36972, CVE-2024-40995,\nCVE-2024-42154, CVE-2024-40916, CVE-2024-39505, CVE-2024-39475,\nCVE-2024-38599, CVE-2024-38596, CVE-2024-39493, CVE-2024-42124,\nCVE-2024-38549, CVE-2024-42084, CVE-2024-40942, CVE-2024-42077,\nCVE-2024-42152, CVE-2024-40904, CVE-2024-31076, CVE-2024-40960,\nCVE-2024-41035, CVE-2024-40945, CVE-2024-38605, CVE-2024-42140,\nCVE-2024-41041, CVE-2024-36014, CVE-2024-38612, CVE-2024-41092,\nCVE-2024-38546, CVE-2024-40902, CVE-2024-42068, CVE-2024-42121,\nCVE-2024-42236, CVE-2024-34777, CVE-2024-39467, CVE-2024-42087,\nCVE-2024-39501, CVE-2024-40980, CVE-2024-38550, CVE-2024-42223,\nCVE-2024-38607, CVE-2024-42247, CVE-2024-41046, CVE-2024-42080,\nCVE-2024-40901, CVE-2024-38571, CVE-2024-39480, CVE-2024-42070,\nCVE-2024-41093, CVE-2024-42148, CVE-2024-38601, CVE-2024-39500,\nCVE-2024-41097, CVE-2024-38565, CVE-2024-38661, CVE-2024-38615,\nCVE-2024-41040, CVE-2024-34027, CVE-2024-37356, CVE-2024-42157,\nCVE-2024-40941, CVE-2024-38634, CVE-2024-41004, CVE-2024-38780,\nCVE-2024-38552, CVE-2024-39276, CVE-2024-38618, CVE-2024-38588,\nCVE-2024-42086, CVE-2024-41087, CVE-2024-38582, CVE-2024-40932,\nCVE-2024-39489, CVE-2024-40968, CVE-2024-42119, CVE-2024-42137,\nCVE-2024-40929, CVE-2024-38591, CVE-2024-36489, CVE-2022-48772,\nCVE-2024-42153, CVE-2024-40959, CVE-2024-40987, CVE-2024-36015,\nCVE-2024-41044, CVE-2024-41002, CVE-2024-42109, CVE-2024-38587,\nCVE-2024-36286, CVE-2024-41055, CVE-2024-39469, CVE-2024-39487,\nCVE-2024-38580, CVE-2024-38619, CVE-2024-38613, CVE-2024-42145,\nCVE-2024-41095, CVE-2024-40958, CVE-2024-40911, CVE-2024-42102,\nCVE-2024-33847, CVE-2024-36974, CVE-2024-40994, CVE-2024-38633,\nCVE-2024-40981, CVE-2024-40983, CVE-2024-42096, CVE-2024-42104,\nCVE-2024-42092, CVE-2024-40954, CVE-2024-38637, CVE-2024-42240,\nCVE-2024-38621, CVE-2024-38578, CVE-2024-38547, CVE-2024-39490,\nCVE-2024-42076, CVE-2024-42244, CVE-2024-39499, CVE-2024-38586,\nCVE-2024-41089, CVE-2024-40976, CVE-2024-42095, CVE-2024-40931,\nCVE-2024-40990)\n","status":"published","published":"2024-09-13T09:38:11Z","modified":"2026-10-26T22:35:38.116170981Z","updated_at":"2026-11-02T16:58:18.876384Z"},{"id":"USN-7007-2","title":"linux-ibm-5.15, linux-oracle-5.15 vulnerabilities","description":"\nChenyuan Yang discovered that the CEC driver driver in the Linux kernel\ncontained a use-after-free vulnerability. A local attacker could use this\nto cause a denial of service (system crash) or possibly execute arbitrary\ncode. (CVE-2024-23848)\n\nChenyuan Yang discovered that the USB Gadget subsystem in the Linux kernel\ndid not properly check for the device to be enabled before writing. A local\nattacker could possibly use this to cause a denial of service.\n(CVE-2024-25741)\n\nIt was discovered that the JFS file system contained an out-of-bounds read\nvulnerability when printing xattr debug information. A local attacker could\nuse this to cause a denial of service (system crash). (CVE-2024-40902)\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  - M68K architecture;\n  - MIPS architecture;\n  - PowerPC architecture;\n  - RISC-V architecture;\n  - x86 architecture;\n  - Block layer subsystem;\n  - Cryptographic API;\n  - Accessibility subsystem;\n  - ACPI drivers;\n  - Serial ATA and Parallel ATA drivers;\n  - Drivers core;\n  - Bluetooth drivers;\n  - Character device driver;\n  - CPU frequency scaling framework;\n  - Hardware crypto device drivers;\n  - Buffer Sharing and Synchronization framework;\n  - DMA engine subsystem;\n  - FPGA Framework;\n  - GPIO subsystem;\n  - GPU drivers;\n  - Greybus drivers;\n  - HID subsystem;\n  - HW tracing;\n  - I2C subsystem;\n  - IIO subsystem;\n  - InfiniBand drivers;\n  - Input Device (Mouse) drivers;\n  - Macintosh device drivers;\n  - Multiple devices driver;\n  - Media drivers;\n  - VMware VMCI Driver;\n  - Network drivers;\n  - Near Field Communication (NFC) drivers;\n  - NVME drivers;\n  - Pin controllers subsystem;\n  - PTP clock framework;\n  - S/390 drivers;\n  - SCSI drivers;\n  - SoundWire subsystem;\n  - Greybus lights staging drivers;\n  - Media staging drivers;\n  - Thermal drivers;\n  - TTY drivers;\n  - USB subsystem;\n  - DesignWare USB3 driver;\n  - Framebuffer layer;\n  - ACRN Hypervisor Service Module driver;\n  - eCrypt file system;\n  - File systems infrastructure;\n  - Ext4 file system;\n  - F2FS file system;\n  - JFFS2 file system;\n  - JFS file system;\n  - NILFS2 file system;\n  - NTFS3 file system;\n  - SMB network file system;\n  - IOMMU subsystem;\n  - Memory management;\n  - Netfilter;\n  - BPF subsystem;\n  - Kernel debugger infrastructure;\n  - DMA mapping infrastructure;\n  - IRQ subsystem;\n  - Tracing infrastructure;\n  - 9P file system network protocol;\n  - B.A.T.M.A.N. meshing protocol;\n  - CAN network layer;\n  - Ceph Core library;\n  - Networking core;\n  - IPv4 networking;\n  - IPv6 networking;\n  - IUCV driver;\n  - MAC80211 subsystem;\n  - Multipath TCP;\n  - NET/ROM layer;\n  - NFC subsystem;\n  - Open vSwitch;\n  - Network traffic control;\n  - TIPC protocol;\n  - TLS protocol;\n  - Unix domain sockets;\n  - Wireless networking;\n  - XFRM subsystem;\n  - ALSA framework;\n  - SoC Audio for Freescale CPUs drivers;\n  - Kirkwood ASoC drivers;\n(CVE-2024-42140, CVE-2024-38580, CVE-2024-38555, CVE-2024-38591,\nCVE-2024-40942, CVE-2024-42130, CVE-2024-41095, CVE-2024-40994,\nCVE-2024-39469, CVE-2024-38610, CVE-2024-42097, CVE-2024-42137,\nCVE-2024-31076, CVE-2024-38552, CVE-2024-36489, CVE-2024-40983,\nCVE-2024-40908, CVE-2024-39493, CVE-2024-40970, CVE-2024-40901,\nCVE-2024-38567, CVE-2024-38599, CVE-2024-38605, CVE-2024-42119,\nCVE-2024-38590, CVE-2024-38558, CVE-2023-52884, CVE-2024-41000,\nCVE-2024-42101, CVE-2024-40943, CVE-2024-39507, CVE-2024-42115,\nCVE-2024-40968, CVE-2024-42095, CVE-2024-41034, CVE-2024-38618,\nCVE-2024-38633, CVE-2024-40904, CVE-2024-42070, CVE-2024-38583,\nCVE-2024-39471, CVE-2024-38578, CVE-2024-38637, CVE-2024-40987,\nCVE-2024-39506, CVE-2024-39482, CVE-2024-42124, CVE-2024-40981,\nCVE-2024-35927, CVE-2022-48772, CVE-2024-38588, CVE-2023-52887,\nCVE-2024-40941, CVE-2024-34027, CVE-2024-38627, CVE-2024-42106,\nCVE-2024-40927, CVE-2024-38559, CVE-2024-39499, CVE-2024-39505,\nCVE-2024-42120, CVE-2024-38615, CVE-2024-39467, CVE-2024-42232,\nCVE-2024-38589, CVE-2024-38621, CVE-2024-41002, CVE-2024-40934,\nCVE-2024-38582, CVE-2024-39480, CVE-2024-38571, CVE-2024-39301,\nCVE-2024-38612, CVE-2024-39495, CVE-2024-39276, CVE-2024-42096,\nCVE-2024-41041, CVE-2024-40912, CVE-2024-41089, CVE-2024-41093,\nCVE-2024-40931, CVE-2024-42092, CVE-2024-41047, CVE-2024-40956,\nCVE-2024-42229, CVE-2024-40914, CVE-2024-39490, CVE-2024-38548,\nCVE-2024-41044, CVE-2024-40967, CVE-2024-38596, CVE-2024-40902,\nCVE-2024-41055, CVE-2024-38601, CVE-2024-42153, CVE-2024-38623,\nCVE-2024-35247, CVE-2024-38635, CVE-2024-38662, CVE-2024-42086,\nCVE-2024-42102, CVE-2024-42154, CVE-2024-38587, CVE-2024-39466,\nCVE-2024-40911, CVE-2024-39503, CVE-2024-42090, CVE-2024-42087,\nCVE-2024-40929, CVE-2024-37078, CVE-2024-39489, CVE-2024-42244,\nCVE-2024-40980, CVE-2024-38624, CVE-2024-42105, CVE-2024-36270,\nCVE-2024-41092, CVE-2024-40937, CVE-2024-38780, CVE-2024-41035,\nCVE-2024-42104, CVE-2024-40988, CVE-2024-36894, CVE-2024-42157,\nCVE-2024-38613, CVE-2024-40916, CVE-2024-41040, CVE-2024-36032,\nCVE-2024-40978, CVE-2024-38579, CVE-2024-38550, CVE-2024-41049,\nCVE-2024-40959, CVE-2024-42131, CVE-2024-42161, CVE-2024-42247,\nCVE-2024-37356, CVE-2024-40905, CVE-2024-42098, CVE-2024-40932,\nCVE-2024-42236, CVE-2024-38565, CVE-2024-38661, CVE-2024-40963,\nCVE-2024-42240, CVE-2024-40984, CVE-2024-39277, CVE-2024-38573,\nCVE-2024-39509, CVE-2024-41006, CVE-2024-34777, CVE-2024-42152,\nCVE-2024-40954, CVE-2024-39501, CVE-2024-42109, CVE-2024-42080,\nCVE-2024-42225, CVE-2024-41007, CVE-2024-42077, CVE-2024-38634,\nCVE-2024-40995, CVE-2024-42084, CVE-2024-40974, CVE-2024-38586,\nCVE-2024-42224, CVE-2024-40960, CVE-2024-39500, CVE-2024-41004,\nCVE-2024-42145, CVE-2024-38619, CVE-2024-36974, CVE-2024-39502,\nCVE-2024-41097, CVE-2024-40958, CVE-2024-41027, CVE-2024-36972,\nCVE-2024-36286, CVE-2024-40990, CVE-2024-42082, CVE-2024-40945,\nCVE-2024-36014, CVE-2024-42068, CVE-2024-41087, CVE-2024-36978,\nCVE-2024-42148, CVE-2024-40971, CVE-2024-38546, CVE-2024-39488,\nCVE-2024-41048, CVE-2024-42121, CVE-2024-38381, CVE-2024-41046,\nCVE-2024-36971, CVE-2024-42085, CVE-2024-39487, CVE-2024-33847,\nCVE-2024-38607, CVE-2024-33621, CVE-2024-40957, CVE-2024-42127,\nCVE-2024-38547, CVE-2024-36015, CVE-2024-38549, CVE-2024-38597,\nCVE-2024-42093, CVE-2024-42089, CVE-2024-39468, CVE-2024-38560,\nCVE-2024-42223, CVE-2024-38659, CVE-2024-38598, CVE-2024-40976,\nCVE-2024-42094, CVE-2024-41005, CVE-2024-39475, CVE-2024-40961,\nCVE-2024-42076)\n","status":"published","published":"2024-09-23T09:59:41Z","modified":"2026-10-26T22:33:05.953947064Z","updated_at":"2026-11-02T16:58:18.876384Z"},{"id":"USN-7007-3","title":"linux-lowlatency, linux-lowlatency-hwe-5.15 vulnerabilities","description":"Chenyuan Yang discovered that the CEC driver driver in the Linux kernel\ncontained a use-after-free vulnerability. A local attacker could use this\nto cause a denial of service (system crash) or possibly execute arbitrary\ncode. (CVE-2024-23848)\n\nChenyuan Yang discovered that the USB Gadget subsystem in the Linux kernel\ndid not properly check for the device to be enabled before writing. A local\nattacker could possibly use this to cause a denial of service.\n(CVE-2024-25741)\n\nIt was discovered that the JFS file system contained an out-of-bounds read\nvulnerability when printing xattr debug information. A local attacker could\nuse this to cause a denial of service (system crash). (CVE-2024-40902)\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  - M68K architecture;\n  - MIPS architecture;\n  - PowerPC architecture;\n  - RISC-V architecture;\n  - x86 architecture;\n  - Block layer subsystem;\n  - Cryptographic API;\n  - Accessibility subsystem;\n  - ACPI drivers;\n  - Serial ATA and Parallel ATA drivers;\n  - Drivers core;\n  - Bluetooth drivers;\n  - Character device driver;\n  - CPU frequency scaling framework;\n  - Hardware crypto device drivers;\n  - Buffer Sharing and Synchronization framework;\n  - DMA engine subsystem;\n  - FPGA Framework;\n  - GPIO subsystem;\n  - GPU drivers;\n  - Greybus drivers;\n  - HID subsystem;\n  - HW tracing;\n  - I2C subsystem;\n  - IIO subsystem;\n  - InfiniBand drivers;\n  - Input Device (Mouse) drivers;\n  - Macintosh device drivers;\n  - Multiple devices driver;\n  - Media drivers;\n  - VMware VMCI Driver;\n  - Network drivers;\n  - Near Field Communication (NFC) drivers;\n  - NVME drivers;\n  - Pin controllers subsystem;\n  - PTP clock framework;\n  - S/390 drivers;\n  - SCSI drivers;\n  - SoundWire subsystem;\n  - Greybus lights staging drivers;\n  - Media staging drivers;\n  - Thermal drivers;\n  - TTY drivers;\n  - USB subsystem;\n  - DesignWare USB3 driver;\n  - Framebuffer layer;\n  - ACRN Hypervisor Service Module driver;\n  - eCrypt file system;\n  - File systems infrastructure;\n  - Ext4 file system;\n  - F2FS file system;\n  - JFFS2 file system;\n  - JFS file system;\n  - NILFS2 file system;\n  - NTFS3 file system;\n  - SMB network file system;\n  - IOMMU subsystem;\n  - Memory management;\n  - Netfilter;\n  - BPF subsystem;\n  - Kernel debugger infrastructure;\n  - DMA mapping infrastructure;\n  - IRQ subsystem;\n  - Tracing infrastructure;\n  - 9P file system network protocol;\n  - B.A.T.M.A.N. meshing protocol;\n  - CAN network layer;\n  - Ceph Core library;\n  - Networking core;\n  - IPv4 networking;\n  - IPv6 networking;\n  - IUCV driver;\n  - MAC80211 subsystem;\n  - Multipath TCP;\n  - NET/ROM layer;\n  - NFC subsystem;\n  - Open vSwitch;\n  - Network traffic control;\n  - TIPC protocol;\n  - TLS protocol;\n  - Unix domain sockets;\n  - Wireless networking;\n  - XFRM subsystem;\n  - ALSA framework;\n  - SoC Audio for Freescale CPUs drivers;\n  - Kirkwood ASoC drivers;\n(CVE-2024-42105, CVE-2024-41002, CVE-2024-38558, CVE-2023-52887,\nCVE-2024-39487, CVE-2024-39276, CVE-2024-42077, CVE-2024-39493,\nCVE-2024-40934, CVE-2024-39277, CVE-2024-42087, CVE-2024-38598,\nCVE-2024-38618, CVE-2024-40981, CVE-2024-42127, CVE-2024-38607,\nCVE-2024-38586, CVE-2024-40901, CVE-2024-40916, CVE-2024-42247,\nCVE-2024-42093, CVE-2024-36489, CVE-2024-38615, CVE-2024-42120,\nCVE-2024-38567, CVE-2024-40957, CVE-2024-39501, CVE-2024-42140,\nCVE-2024-33621, CVE-2024-38573, CVE-2023-52884, CVE-2024-39468,\nCVE-2024-41092, CVE-2024-40931, CVE-2024-42145, CVE-2024-39490,\nCVE-2024-38555, CVE-2024-42086, CVE-2024-38597, CVE-2024-40956,\nCVE-2024-42223, CVE-2024-36894, CVE-2024-40961, CVE-2024-42076,\nCVE-2024-40994, CVE-2024-38619, CVE-2024-39467, CVE-2024-39466,\nCVE-2022-48772, CVE-2024-39507, CVE-2024-40914, CVE-2024-41046,\nCVE-2024-42094, CVE-2024-38591, CVE-2024-42098, CVE-2024-41027,\nCVE-2024-41040, CVE-2024-41089, CVE-2024-40945, CVE-2024-39503,\nCVE-2024-37356, CVE-2024-36286, CVE-2024-39495, CVE-2024-42101,\nCVE-2024-40941, CVE-2024-42137, CVE-2024-38381, CVE-2024-38627,\nCVE-2024-31076, CVE-2024-42092, CVE-2024-40932, CVE-2024-40995,\nCVE-2024-40937, CVE-2024-39489, CVE-2024-42084, CVE-2024-40929,\nCVE-2024-36978, CVE-2024-36015, CVE-2024-36014, CVE-2024-42124,\nCVE-2024-40976, CVE-2024-39502, CVE-2024-38599, CVE-2024-38661,\nCVE-2024-42104, CVE-2024-42096, CVE-2024-40904, CVE-2024-40990,\nCVE-2024-38579, CVE-2024-40974, CVE-2024-41055, CVE-2024-38633,\nCVE-2024-38659, CVE-2024-41093, CVE-2024-42154, CVE-2024-38624,\nCVE-2024-41049, CVE-2024-38552, CVE-2024-38578, CVE-2024-38605,\nCVE-2024-40970, CVE-2024-38601, CVE-2024-38550, CVE-2024-38559,\nCVE-2024-38571, CVE-2024-40971, CVE-2024-41097, CVE-2024-40967,\nCVE-2024-38612, CVE-2024-38587, CVE-2024-41004, CVE-2024-33847,\nCVE-2024-38580, CVE-2024-39506, CVE-2024-42102, CVE-2024-36032,\nCVE-2024-38548, CVE-2024-39499, CVE-2024-38610, CVE-2024-42152,\nCVE-2024-40943, CVE-2024-40959, CVE-2024-39488, CVE-2024-36972,\nCVE-2024-38637, CVE-2024-40942, CVE-2024-42106, CVE-2024-38546,\nCVE-2024-38634, CVE-2024-39471, CVE-2024-39482, CVE-2024-41095,\nCVE-2024-42229, CVE-2024-42131, CVE-2024-41007, CVE-2024-42095,\nCVE-2024-42097, CVE-2024-39480, CVE-2024-35927, CVE-2024-42153,\nCVE-2024-42080, CVE-2024-42089, CVE-2024-41087, CVE-2024-39475,\nCVE-2024-42119, CVE-2024-41041, CVE-2024-38623, CVE-2024-39469,\nCVE-2024-34777, CVE-2024-42157, CVE-2024-42085, CVE-2024-36270,\nCVE-2024-34027, CVE-2024-35247, CVE-2024-38549, CVE-2024-40954,\nCVE-2024-41034, CVE-2024-41044, CVE-2024-39509, CVE-2024-40987,\nCVE-2024-42161, CVE-2024-40911, CVE-2024-42070, CVE-2024-42109,\nCVE-2024-37078, CVE-2024-40912, CVE-2024-40988, CVE-2024-40978,\nCVE-2024-41048, CVE-2024-41005, CVE-2024-40905, CVE-2024-41047,\nCVE-2024-41006, CVE-2024-38560, CVE-2024-42225, CVE-2024-42148,\nCVE-2024-38596, CVE-2024-38588, CVE-2024-39301, CVE-2024-38613,\nCVE-2024-38635, CVE-2024-40960, CVE-2024-39505, CVE-2024-42244,\nCVE-2024-40963, CVE-2024-39500, CVE-2024-42082, CVE-2024-36971,\nCVE-2024-42068, CVE-2024-40984, CVE-2024-41035, CVE-2024-38583,\nCVE-2024-42121, CVE-2024-40968, CVE-2024-40958, CVE-2024-40927,\nCVE-2024-40980, CVE-2024-40908, CVE-2024-38780, CVE-2024-38590,\nCVE-2024-42115, CVE-2024-42224, CVE-2024-42232, CVE-2024-42240,\nCVE-2024-42236, CVE-2024-38547, CVE-2024-38565, CVE-2024-40902,\nCVE-2024-38662, CVE-2024-42090, CVE-2024-36974, CVE-2024-38621,\nCVE-2024-41000, CVE-2024-40983, CVE-2024-42130, CVE-2024-38582,\nCVE-2024-38589)\n","status":"published","published":"2024-09-23T15:52:38Z","modified":"2026-10-26T22:33:37.683464668Z","updated_at":"2026-11-02T16:58:18.876384Z"},{"id":"USN-7009-1","title":"linux-azure, linux-azure-5.15, linux-azure-fde vulnerabilities","description":"\nChenyuan Yang discovered that the CEC driver driver in the Linux kernel\ncontained a use-after-free vulnerability. A local attacker could use this\nto cause a denial of service (system crash) or possibly execute arbitrary\ncode. (CVE-2024-23848)\n\nChenyuan Yang discovered that the USB Gadget subsystem in the Linux kernel\ndid not properly check for the device to be enabled before writing. A local\nattacker could possibly use this to cause a denial of service.\n(CVE-2024-25741)\n\nIt was discovered that the JFS file system contained an out-of-bounds read\nvulnerability when printing xattr debug information. A local attacker could\nuse this to cause a denial of service (system crash). (CVE-2024-40902)\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  - M68K architecture;\n  - MIPS architecture;\n  - PowerPC architecture;\n  - RISC-V architecture;\n  - x86 architecture;\n  - Block layer subsystem;\n  - Cryptographic API;\n  - Accessibility subsystem;\n  - ACPI drivers;\n  - Serial ATA and Parallel ATA drivers;\n  - Drivers core;\n  - Bluetooth drivers;\n  - Character device driver;\n  - CPU frequency scaling framework;\n  - Hardware crypto device drivers;\n  - Buffer Sharing and Synchronization framework;\n  - DMA engine subsystem;\n  - FPGA Framework;\n  - GPIO subsystem;\n  - GPU drivers;\n  - Greybus drivers;\n  - HID subsystem;\n  - HW tracing;\n  - I2C subsystem;\n  - IIO subsystem;\n  - InfiniBand drivers;\n  - Input Device (Mouse) drivers;\n  - Macintosh device drivers;\n  - Multiple devices driver;\n  - Media drivers;\n  - VMware VMCI Driver;\n  - Network drivers;\n  - Near Field Communication (NFC) drivers;\n  - NVME drivers;\n  - Pin controllers subsystem;\n  - PTP clock framework;\n  - S/390 drivers;\n  - SCSI drivers;\n  - SoundWire subsystem;\n  - Greybus lights staging drivers;\n  - Media staging drivers;\n  - Thermal drivers;\n  - TTY drivers;\n  - USB subsystem;\n  - DesignWare USB3 driver;\n  - Framebuffer layer;\n  - ACRN Hypervisor Service Module driver;\n  - eCrypt file system;\n  - File systems infrastructure;\n  - Ext4 file system;\n  - F2FS file system;\n  - JFFS2 file system;\n  - JFS file system;\n  - NILFS2 file system;\n  - NTFS3 file system;\n  - SMB network file system;\n  - IOMMU subsystem;\n  - Memory management;\n  - Netfilter;\n  - BPF subsystem;\n  - Kernel debugger infrastructure;\n  - DMA mapping infrastructure;\n  - IRQ subsystem;\n  - Tracing infrastructure;\n  - 9P file system network protocol;\n  - B.A.T.M.A.N. meshing protocol;\n  - CAN network layer;\n  - Ceph Core library;\n  - Networking core;\n  - IPv4 networking;\n  - IPv6 networking;\n  - IUCV driver;\n  - MAC80211 subsystem;\n  - Multipath TCP;\n  - NET/ROM layer;\n  - NFC subsystem;\n  - Open vSwitch;\n  - Network traffic control;\n  - TIPC protocol;\n  - TLS protocol;\n  - Unix domain sockets;\n  - Wireless networking;\n  - XFRM subsystem;\n  - ALSA framework;\n  - SoC Audio for Freescale CPUs drivers;\n  - Kirkwood ASoC drivers;\n(CVE-2024-38613, CVE-2024-42096, CVE-2024-40908, CVE-2024-42137,\nCVE-2024-38590, CVE-2024-41044, CVE-2024-39480, CVE-2024-39469,\nCVE-2024-39471, CVE-2024-42089, CVE-2024-38588, CVE-2024-41092,\nCVE-2024-42120, CVE-2024-40901, CVE-2024-40981, CVE-2024-42127,\nCVE-2024-40932, CVE-2024-39475, CVE-2024-40957, CVE-2024-39501,\nCVE-2024-42090, CVE-2024-40904, CVE-2024-40978, CVE-2022-48772,\nCVE-2024-40934, CVE-2024-38548, CVE-2024-41005, CVE-2024-36489,\nCVE-2024-36978, CVE-2024-38573, CVE-2024-42106, CVE-2024-42104,\nCVE-2024-42085, CVE-2024-38621, CVE-2024-42098, CVE-2024-38662,\nCVE-2024-38587, CVE-2024-41089, CVE-2024-42095, CVE-2024-40916,\nCVE-2024-39487, CVE-2024-42229, CVE-2023-52884, CVE-2024-40974,\nCVE-2024-40980, CVE-2024-42225, CVE-2024-39502, CVE-2024-37356,\nCVE-2024-39488, CVE-2024-40912, CVE-2024-39507, CVE-2024-38591,\nCVE-2024-31076, CVE-2024-40984, CVE-2024-39500, CVE-2024-38582,\nCVE-2024-34027, CVE-2024-36270, CVE-2024-42076, CVE-2024-42247,\nCVE-2024-42154, CVE-2024-41047, CVE-2024-42244, CVE-2024-41049,\nCVE-2024-33847, CVE-2024-36015, CVE-2024-42161, CVE-2024-42082,\nCVE-2024-41048, CVE-2024-40961, CVE-2024-41000, CVE-2024-38598,\nCVE-2024-41040, CVE-2024-36971, CVE-2024-41007, CVE-2024-36972,\nCVE-2024-38610, CVE-2024-40937, CVE-2024-38615, CVE-2024-38555,\nCVE-2024-40943, CVE-2024-39466, CVE-2024-40990, CVE-2024-42115,\nCVE-2024-40995, CVE-2024-38612, CVE-2024-40987, CVE-2024-38558,\nCVE-2024-42236, CVE-2024-38381, CVE-2024-42157, CVE-2024-38560,\nCVE-2024-42101, CVE-2024-40970, CVE-2024-42094, CVE-2024-42148,\nCVE-2024-35247, CVE-2024-40963, CVE-2024-38580, CVE-2024-38633,\nCVE-2024-38637, CVE-2024-40905, CVE-2024-41093, CVE-2024-38619,\nCVE-2024-42093, CVE-2024-40945, CVE-2024-42092, CVE-2024-36286,\nCVE-2024-40954, CVE-2024-41041, CVE-2024-38571, CVE-2024-39503,\nCVE-2024-38546, CVE-2024-40976, CVE-2024-36014, CVE-2024-41087,\nCVE-2024-42109, CVE-2024-42070, CVE-2024-42080, CVE-2024-41006,\nCVE-2024-42145, CVE-2024-40960, CVE-2024-38597, CVE-2024-42086,\nCVE-2024-40967, CVE-2024-42130, CVE-2024-42153, CVE-2024-39509,\nCVE-2024-40914, CVE-2024-39277, CVE-2024-41055, CVE-2024-41095,\nCVE-2024-38780, CVE-2024-36974, CVE-2024-38607, CVE-2024-38583,\nCVE-2024-40927, CVE-2024-39490, CVE-2024-38599, CVE-2023-52887,\nCVE-2024-38565, CVE-2024-38552, CVE-2024-40942, CVE-2024-37078,\nCVE-2024-40911, CVE-2024-41035, CVE-2024-38550, CVE-2024-42102,\nCVE-2024-42121, CVE-2024-36032, CVE-2024-42240, CVE-2024-42140,\nCVE-2024-38589, CVE-2024-40931, CVE-2024-39505, CVE-2024-38596,\nCVE-2024-42223, CVE-2024-38567, CVE-2024-39495, CVE-2024-40959,\nCVE-2024-38586, CVE-2024-42087, CVE-2024-38661, CVE-2024-41097,\nCVE-2024-38559, CVE-2024-38618, CVE-2024-39493, CVE-2024-41002,\nCVE-2024-40958, CVE-2024-39468, CVE-2024-38601, CVE-2024-39499,\nCVE-2024-39482, CVE-2024-38579, CVE-2024-42077, CVE-2024-38578,\nCVE-2024-34777, CVE-2024-39301, CVE-2024-38605, CVE-2024-42131,\nCVE-2024-42084, CVE-2024-41027, CVE-2024-40968, CVE-2024-38547,\nCVE-2024-42119, CVE-2024-38627, CVE-2024-40941, CVE-2024-40994,\nCVE-2024-40988, CVE-2024-40902, CVE-2024-41046, CVE-2024-38549,\nCVE-2024-39506, CVE-2024-38634, CVE-2024-42124, CVE-2024-42105,\nCVE-2024-38623, CVE-2024-38624, CVE-2024-33621, CVE-2024-42068,\nCVE-2024-36894, CVE-2024-39489, CVE-2024-42270, CVE-2024-40929,\nCVE-2024-39276, CVE-2024-42152, CVE-2024-41034, CVE-2024-40983,\nCVE-2024-42224, CVE-2024-40956, CVE-2024-40971, CVE-2024-38635,\nCVE-2024-42097, CVE-2024-42232, CVE-2024-38659, CVE-2024-39467,\nCVE-2024-41004)\n","status":"published","published":"2024-09-13T11:47:02Z","modified":"2026-10-26T22:33:39.46132957Z","updated_at":"2026-11-02T16:58:18.876384Z"},{"id":"USN-7009-2","title":"linux-azure-fde-5.15 vulnerabilities","description":"Chenyuan Yang discovered that the CEC driver driver in the Linux kernel\ncontained a use-after-free vulnerability. A local attacker could use this\nto cause a denial of service (system crash) or possibly execute arbitrary\ncode. (CVE-2024-23848)\n\nChenyuan Yang discovered that the USB Gadget subsystem in the Linux kernel\ndid not properly check for the device to be enabled before writing. A local\nattacker could possibly use this to cause a denial of service.\n(CVE-2024-25741)\n\nIt was discovered that the JFS file system contained an out-of-bounds read\nvulnerability when printing xattr debug information. A local attacker could\nuse this to cause a denial of service (system crash). (CVE-2024-40902)\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  - M68K architecture;\n  - MIPS architecture;\n  - PowerPC architecture;\n  - RISC-V architecture;\n  - x86 architecture;\n  - Block layer subsystem;\n  - Cryptographic API;\n  - Accessibility subsystem;\n  - ACPI drivers;\n  - Serial ATA and Parallel ATA drivers;\n  - Drivers core;\n  - Bluetooth drivers;\n  - Character device driver;\n  - CPU frequency scaling framework;\n  - Hardware crypto device drivers;\n  - Buffer Sharing and Synchronization framework;\n  - DMA engine subsystem;\n  - FPGA Framework;\n  - GPIO subsystem;\n  - GPU drivers;\n  - Greybus drivers;\n  - HID subsystem;\n  - HW tracing;\n  - I2C subsystem;\n  - IIO subsystem;\n  - InfiniBand drivers;\n  - Input Device (Mouse) drivers;\n  - Macintosh device drivers;\n  - Multiple devices driver;\n  - Media drivers;\n  - VMware VMCI Driver;\n  - Network drivers;\n  - Near Field Communication (NFC) drivers;\n  - NVME drivers;\n  - Pin controllers subsystem;\n  - PTP clock framework;\n  - S/390 drivers;\n  - SCSI drivers;\n  - SoundWire subsystem;\n  - Greybus lights staging drivers;\n  - Media staging drivers;\n  - Thermal drivers;\n  - TTY drivers;\n  - USB subsystem;\n  - DesignWare USB3 driver;\n  - Framebuffer layer;\n  - ACRN Hypervisor Service Module driver;\n  - eCrypt file system;\n  - File systems infrastructure;\n  - Ext4 file system;\n  - F2FS file system;\n  - JFFS2 file system;\n  - JFS file system;\n  - NILFS2 file system;\n  - NTFS3 file system;\n  - SMB network file system;\n  - IOMMU subsystem;\n  - Memory management;\n  - Netfilter;\n  - BPF subsystem;\n  - Kernel debugger infrastructure;\n  - DMA mapping infrastructure;\n  - IRQ subsystem;\n  - Tracing infrastructure;\n  - 9P file system network protocol;\n  - B.A.T.M.A.N. meshing protocol;\n  - CAN network layer;\n  - Ceph Core library;\n  - Networking core;\n  - IPv4 networking;\n  - IPv6 networking;\n  - IUCV driver;\n  - MAC80211 subsystem;\n  - Multipath TCP;\n  - NET/ROM layer;\n  - NFC subsystem;\n  - Open vSwitch;\n  - Network traffic control;\n  - TIPC protocol;\n  - TLS protocol;\n  - Unix domain sockets;\n  - Wireless networking;\n  - XFRM subsystem;\n  - ALSA framework;\n  - SoC Audio for Freescale CPUs drivers;\n  - Kirkwood ASoC drivers;\n(CVE-2024-42076, CVE-2024-40994, CVE-2024-40932, CVE-2024-41000,\nCVE-2024-42224, CVE-2024-38633, CVE-2024-40954, CVE-2024-36270,\nCVE-2024-38623, CVE-2024-38549, CVE-2024-42225, CVE-2024-42085,\nCVE-2024-42157, CVE-2024-42229, CVE-2024-42109, CVE-2024-41040,\nCVE-2024-38607, CVE-2024-39493, CVE-2024-38546, CVE-2024-41046,\nCVE-2024-38567, CVE-2024-42092, CVE-2024-39501, CVE-2024-41005,\nCVE-2024-42223, CVE-2024-39480, CVE-2024-38571, CVE-2024-41048,\nCVE-2024-38605, CVE-2024-42094, CVE-2024-38598, CVE-2024-38559,\nCVE-2024-38558, CVE-2024-40931, CVE-2024-40942, CVE-2024-39495,\nCVE-2024-40981, CVE-2024-40911, CVE-2024-42148, CVE-2024-33621,\nCVE-2024-39502, CVE-2024-41095, CVE-2024-40960, CVE-2024-36286,\nCVE-2024-42232, CVE-2024-42130, CVE-2024-42154, CVE-2024-41087,\nCVE-2024-41004, CVE-2024-39277, CVE-2024-38560, CVE-2024-36978,\nCVE-2024-42089, CVE-2024-37356, CVE-2024-38547, CVE-2024-38381,\nCVE-2024-36015, CVE-2024-38548, CVE-2024-42120, CVE-2024-41092,\nCVE-2024-40978, CVE-2024-38619, CVE-2024-40914, CVE-2024-41089,\nCVE-2024-40988, CVE-2024-41047, CVE-2024-38565, CVE-2024-38550,\nCVE-2023-52887, CVE-2024-38552, CVE-2024-38583, CVE-2024-38613,\nCVE-2024-40967, CVE-2024-40927, CVE-2024-42124, CVE-2024-42244,\nCVE-2024-42152, CVE-2024-39509, CVE-2024-38662, CVE-2024-38618,\nCVE-2024-42140, CVE-2024-38579, CVE-2024-40945, CVE-2024-42101,\nCVE-2024-42104, CVE-2024-41044, CVE-2024-42161, CVE-2024-42093,\nCVE-2024-42270, CVE-2024-42097, CVE-2024-40970, CVE-2024-40908,\nCVE-2024-38582, CVE-2024-42247, CVE-2024-38661, CVE-2024-40941,\nCVE-2024-42084, CVE-2024-42090, CVE-2024-42131, CVE-2024-42077,\nCVE-2024-40995, CVE-2024-42105, CVE-2024-41035, CVE-2024-41097,\nCVE-2024-38780, CVE-2024-35247, CVE-2024-36974, CVE-2024-42070,\nCVE-2024-40902, CVE-2024-36972, CVE-2024-38586, CVE-2024-38573,\nCVE-2024-38612, CVE-2024-42121, CVE-2023-52884, CVE-2024-39276,\nCVE-2024-38615, CVE-2024-42095, CVE-2024-42086, CVE-2024-39507,\nCVE-2024-40983, CVE-2024-40943, CVE-2024-41002, CVE-2024-40958,\nCVE-2024-41049, CVE-2024-38596, CVE-2024-37078, CVE-2024-38637,\nCVE-2024-38621, CVE-2024-42153, CVE-2024-38659, CVE-2024-39468,\nCVE-2024-38589, CVE-2024-38587, CVE-2024-36971, CVE-2024-38599,\nCVE-2024-31076, CVE-2024-39490, CVE-2024-40959, CVE-2024-38634,\nCVE-2024-38624, CVE-2024-42240, CVE-2024-42127, CVE-2024-42102,\nCVE-2024-38578, CVE-2024-34027, CVE-2024-38601, CVE-2024-42087,\nCVE-2024-38597, CVE-2024-38591, CVE-2024-39503, CVE-2024-42236,\nCVE-2024-42082, CVE-2024-40956, CVE-2024-41041, CVE-2024-38580,\nCVE-2024-39506, CVE-2024-36894, CVE-2024-40987, CVE-2024-39475,\nCVE-2024-38635, CVE-2024-41007, CVE-2024-39471, CVE-2024-39467,\nCVE-2022-48772, CVE-2024-40934, CVE-2024-42106, CVE-2024-39469,\nCVE-2024-40963, CVE-2024-39482, CVE-2024-39505, CVE-2024-36014,\nCVE-2024-39500, CVE-2024-42096, CVE-2024-41055, CVE-2024-40937,\nCVE-2024-38590, CVE-2024-38610, CVE-2024-41034, CVE-2024-42115,\nCVE-2024-40974, CVE-2024-40968, CVE-2024-42080, CVE-2024-40957,\nCVE-2024-40971, CVE-2024-36032, CVE-2024-39499, CVE-2024-42137,\nCVE-2024-39489, CVE-2024-40976, CVE-2024-39466, CVE-2024-42145,\nCVE-2024-36489, CVE-2024-40980, CVE-2024-39301, CVE-2024-40905,\nCVE-2024-41093, CVE-2024-40912, CVE-2024-42119, CVE-2024-38588,\nCVE-2024-40916, CVE-2024-39488, CVE-2024-41027, CVE-2024-42068,\nCVE-2024-40904, CVE-2024-40961, CVE-2024-33847, CVE-2024-38555,\nCVE-2024-41006, CVE-2024-40929, CVE-2024-34777, CVE-2024-38627,\nCVE-2024-40984, CVE-2024-40990, CVE-2024-39487, CVE-2024-42098,\nCVE-2024-40901)\n","status":"published","published":"2024-09-25T08:27:37Z","modified":"2026-08-06T03:07:31.441367086Z","updated_at":"2026-11-02T16:58:18.876384Z"},{"id":"USN-7019-1","title":"linux-xilinx-zynqmp vulnerabilities","description":"\nZiming Zhang discovered that the DRM driver for VMware Virtual GPU did not\nproperly handle certain error conditions, leading to a NULL pointer\ndereference. A local attacker could possibly trigger this vulnerability to\ncause a denial of service. (CVE-2022-38096)\n\nGui-Dong Han discovered that the software RAID driver in the Linux kernel\ncontained a race condition, leading to an integer overflow vulnerability. A\nprivileged attacker could possibly use this to cause a denial of service\n(system crash). (CVE-2024-23307)\n\nChenyuan Yang discovered that the CEC driver driver in the Linux kernel\ncontained a use-after-free vulnerability. A local attacker could use this\nto cause a denial of service (system crash) or possibly execute arbitrary\ncode. (CVE-2024-23848)\n\nIt was discovered that a race condition existed in the Bluetooth subsystem\nin the Linux kernel when modifying certain settings values through debugfs.\nA privileged local attacker could use this to cause a denial of service.\n(CVE-2024-24857, CVE-2024-24858, CVE-2024-24859)\n\nBai Jiaju discovered that the Xceive XC4000 silicon tuner device driver in\nthe Linux kernel contained a race condition, leading to an integer overflow\nvulnerability. An attacker could possibly use this to cause a denial of\nservice (system crash). (CVE-2024-24861)\n\nChenyuan Yang discovered that the Unsorted Block Images (UBI) flash device\nvolume management subsystem did not properly validate logical eraseblock\nsizes in certain situations. An attacker could possibly use this to cause a\ndenial of service (system crash). (CVE-2024-25739)\n\nChenyuan Yang discovered that the USB Gadget subsystem in the Linux kernel\ndid not properly check for the device to be enabled before writing. A local\nattacker could possibly use this to cause a denial of service.\n(CVE-2024-25741)\n\nBenedict Schlüter, Supraja Sridhara, Andrin Bertschi, and Shweta Shinde\ndiscovered that an untrusted hypervisor could inject malicious #VC\ninterrupts and compromise the security guarantees of AMD SEV-SNP. This flaw\nis known as WeSee. A local attacker in control of the hypervisor could use\nthis to expose sensitive information or possibly execute arbitrary code in\nthe trusted execution environment. (CVE-2024-25742)\n\nIt was discovered that the JFS file system contained an out-of-bounds read\nvulnerability when printing xattr debug information. A local attacker could\nuse this to cause a denial of service (system crash). (CVE-2024-40902)\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  - M68K architecture;\n  - MIPS architecture;\n  - PowerPC architecture;\n  - RISC-V architecture;\n  - SuperH RISC architecture;\n  - User-Mode Linux (UML);\n  - x86 architecture;\n  - Block layer subsystem;\n  - Cryptographic API;\n  - Accessibility subsystem;\n  - ACPI drivers;\n  - Android drivers;\n  - Serial ATA and Parallel ATA drivers;\n  - Drivers core;\n  - Bluetooth drivers;\n  - Character device driver;\n  - Clock framework and drivers;\n  - Data acquisition framework and drivers;\n  - CPU frequency scaling framework;\n  - Hardware crypto device drivers;\n  - Buffer Sharing and Synchronization framework;\n  - DMA engine subsystem;\n  - FireWire subsystem;\n  - FPGA Framework;\n  - GPIO subsystem;\n  - GPU drivers;\n  - Greybus drivers;\n  - HID subsystem;\n  - HW tracing;\n  - I2C subsystem;\n  - IIO subsystem;\n  - InfiniBand drivers;\n  - Input Device (Mouse) drivers;\n  - IRQ chip drivers;\n  - Macintosh device drivers;\n  - Multiple devices driver;\n  - Media drivers;\n  - EEPROM drivers;\n  - VMware VMCI Driver;\n  - MMC subsystem;\n  - Network drivers;\n  - Near Field Communication (NFC) drivers;\n  - NVME drivers;\n  - Device tree and open firmware driver;\n  - PCI subsystem;\n  - Pin controllers subsystem;\n  - PTP clock framework;\n  - Remote Processor subsystem;\n  - S/390 drivers;\n  - SCSI drivers;\n  - Freescale SoC drivers;\n  - SoundWire subsystem;\n  - Greybus lights staging drivers;\n  - Media staging drivers;\n  - Trusted Execution Environment drivers;\n  - Thermal drivers;\n  - TTY drivers;\n  - USB subsystem;\n  - DesignWare USB3 driver;\n  - VFIO drivers;\n  - Framebuffer layer;\n  - ACRN Hypervisor Service Module driver;\n  - Xen hypervisor drivers;\n  - 9P distributed file system;\n  - File systems infrastructure;\n  - BTRFS file system;\n  - eCrypt file system;\n  - Ext4 file system;\n  - F2FS file system;\n  - FAT file system;\n  - GFS2 file system;\n  - JFFS2 file system;\n  - JFS file system;\n  - Network file system client;\n  - Network file system server daemon;\n  - NILFS2 file system;\n  - NTFS3 file system;\n  - Pstore file system;\n  - SMB network file system;\n  - UBI file system;\n  - IOMMU subsystem;\n  - Memory management;\n  - Socket messages infrastructure;\n  - Netfilter;\n  - BPF subsystem;\n  - Kernel debugger infrastructure;\n  - DMA mapping infrastructure;\n  - IRQ subsystem;\n  - Core kernel;\n  - Tracing infrastructure;\n  - Dynamic debug library;\n  - PCI iomap interfaces;\n  - 9P file system network protocol;\n  - B.A.T.M.A.N. meshing protocol;\n  - Bluetooth subsystem;\n  - Ethernet bridge;\n  - CAN network layer;\n  - Ceph Core library;\n  - Networking core;\n  - Distributed Switch Architecture;\n  - IPv4 networking;\n  - IPv6 networking;\n  - IUCV driver;\n  - MAC80211 subsystem;\n  - IEEE 802.15.4 subsystem;\n  - Multipath TCP;\n  - NET/ROM layer;\n  - NFC subsystem;\n  - NSH protocol;\n  - Open vSwitch;\n  - Phonet protocol;\n  - RDS protocol;\n  - Network traffic control;\n  - SMC sockets;\n  - TIPC protocol;\n  - TLS protocol;\n  - Unix domain sockets;\n  - Wireless networking;\n  - eXpress Data Path;\n  - XFRM subsystem;\n  - Key management;\n  - ALSA framework;\n  - HD-audio driver;\n  - ALSA SH drivers;\n  - SoC Audio for Freescale CPUs drivers;\n  - Kirkwood ASoC drivers;\n  - KVM core;\n(CVE-2024-42085, CVE-2024-42154, CVE-2024-42229, CVE-2024-38548,\nCVE-2024-42120, CVE-2024-38555, CVE-2024-38598, CVE-2024-40954,\nCVE-2024-38571, CVE-2024-36020, CVE-2024-36270, CVE-2024-39482,\nCVE-2024-39468, CVE-2024-38607, CVE-2024-26923, CVE-2024-42145,\nCVE-2024-41040, CVE-2024-35852, CVE-2024-35805, CVE-2024-35890,\nCVE-2024-36965, CVE-2024-42077, CVE-2024-26958, CVE-2024-35823,\nCVE-2024-42124, CVE-2024-26680, CVE-2024-38549, CVE-2024-36286,\nCVE-2024-27398, CVE-2024-35990, CVE-2024-36975, CVE-2024-27437,\nCVE-2024-35848, CVE-2024-26900, CVE-2024-26654, CVE-2024-40971,\nCVE-2024-35847, CVE-2024-35982, CVE-2024-42232, CVE-2022-48808,\nCVE-2024-35822, CVE-2024-36950, CVE-2024-33621, CVE-2024-39276,\nCVE-2024-40968, CVE-2024-35857, CVE-2024-40905, CVE-2023-52880,\nCVE-2024-35819, CVE-2024-35791, CVE-2024-42076, CVE-2024-40904,\nCVE-2024-35976, CVE-2024-35854, CVE-2024-26642, CVE-2024-27393,\nCVE-2024-26934, CVE-2024-26960, CVE-2024-42137, CVE-2024-38588,\nCVE-2024-40970, CVE-2024-36972, CVE-2024-26977, CVE-2024-38546,\nCVE-2024-41095, CVE-2024-39292, CVE-2024-41087, CVE-2024-33847,\nCVE-2024-40978, CVE-2024-41049, CVE-2024-35895, CVE-2024-35804,\nCVE-2024-42093, CVE-2024-36017, CVE-2024-38591, CVE-2024-42080,\nCVE-2024-41089, CVE-2024-38613, CVE-2024-39466, CVE-2024-40931,\nCVE-2024-35907, CVE-2024-36919, CVE-2024-36934, CVE-2024-42240,\nCVE-2024-35940, CVE-2024-36938, CVE-2024-42121, CVE-2024-39490,\nCVE-2024-40961, CVE-2024-42223, CVE-2024-41041, CVE-2024-41093,\nCVE-2024-42068, CVE-2024-41044, CVE-2024-42086, CVE-2024-42105,\nCVE-2024-36954, CVE-2024-35796, CVE-2024-38610, CVE-2024-36929,\nCVE-2024-35893, CVE-2024-38601, CVE-2024-40981, CVE-2024-36889,\nCVE-2024-27015, CVE-2024-35897, CVE-2024-39469, CVE-2024-35825,\nCVE-2024-26922, CVE-2024-38573, CVE-2024-42130, CVE-2024-38580,\nCVE-2024-26814, CVE-2024-36955, CVE-2024-26813, CVE-2024-27396,\nCVE-2024-36937, CVE-2024-36928, CVE-2024-42224, CVE-2024-27004,\nCVE-2024-42104, CVE-2024-42225, CVE-2024-38659, CVE-2024-35955,\nCVE-2024-42106, CVE-2024-39489, CVE-2024-31076, CVE-2024-26817,\nCVE-2024-35884, CVE-2024-42095, CVE-2024-42131, CVE-2024-40956,\nCVE-2024-40941, CVE-2024-36007, CVE-2024-27009, CVE-2024-40959,\nCVE-2024-42089, CVE-2024-37078, CVE-2024-35960, CVE-2024-41002,\nCVE-2024-39301, CVE-2024-35988, CVE-2023-52887, CVE-2024-35885,\nCVE-2024-39484, CVE-2024-35872, CVE-2024-40974, CVE-2024-35851,\nCVE-2024-26957, CVE-2024-38623, CVE-2024-35944, CVE-2024-41005,\nCVE-2024-42152, CVE-2024-35888, CVE-2024-38621, CVE-2024-26989,\nCVE-2024-42148, CVE-2024-27401, CVE-2024-36883, CVE-2024-35855,\nCVE-2024-26936, CVE-2024-26935, CVE-2022-48772, CVE-2024-35853,\nCVE-2024-35997, CVE-2024-27059, CVE-2024-36953, CVE-2024-35969,\nCVE-2024-42094, CVE-2024-38661, CVE-2024-35925, CVE-2024-40914,\nCVE-2024-36940, CVE-2024-27016, CVE-2024-26828, CVE-2024-40911,\nCVE-2024-38634, CVE-2024-38558, CVE-2024-38582, CVE-2023-52629,\nCVE-2024-27020, CVE-2024-35247, CVE-2024-26999, CVE-2024-26687,\nCVE-2024-38565, CVE-2024-38612, CVE-2024-39495, CVE-2024-26974,\nCVE-2024-42101, CVE-2024-38597, CVE-2024-26929, CVE-2024-40927,\nCVE-2024-26830, CVE-2024-26973, CVE-2024-40980, CVE-2024-38560,\nCVE-2024-41047, CVE-2024-42098, CVE-2024-39507, CVE-2024-38599,\nCVE-2024-35789, CVE-2024-27395, CVE-2024-41092, CVE-2024-42161,\nCVE-2024-41006, CVE-2024-36931, CVE-2024-38619, CVE-2024-35813,\nCVE-2024-35898, CVE-2024-41027, CVE-2024-40932, CVE-2024-40960,\nCVE-2024-26925, CVE-2024-41048, CVE-2024-36886, CVE-2024-35877,\nCVE-2024-40963, CVE-2024-36960, CVE-2024-38590, CVE-2024-40902,\nCVE-2024-35871, CVE-2024-38579, CVE-2024-40987, CVE-2024-36025,\nCVE-2024-35806, CVE-2024-35899, CVE-2024-26993, CVE-2024-41097,\nCVE-2024-39488, CVE-2024-42115, CVE-2024-42127, CVE-2024-37356,\nCVE-2024-26812, CVE-2024-36939, CVE-2024-35807, CVE-2024-26886,\nCVE-2024-35809, CVE-2024-40937, CVE-2024-35970, CVE-2024-35817,\nCVE-2024-35973, CVE-2024-40945, CVE-2024-42153, CVE-2024-36964,\nCVE-2024-42090, CVE-2024-38552, CVE-2024-39467, CVE-2024-26961,\nCVE-2024-38615, CVE-2024-38618, CVE-2024-40988, CVE-2024-38605,\nCVE-2024-41004, CVE-2024-26966, CVE-2024-42096, CVE-2024-26996,\nCVE-2024-36969, CVE-2024-36489, CVE-2024-40957, CVE-2024-36974,\nCVE-2024-39502, CVE-2024-26976, CVE-2024-27399, CVE-2024-36905,\nCVE-2024-35958, CVE-2024-35927, CVE-2024-27001, CVE-2024-39487,\nCVE-2024-41034, CVE-2024-36904, CVE-2024-41055, CVE-2024-38550,\nCVE-2024-38567, CVE-2024-38586, CVE-2024-40916, CVE-2024-38589,\nCVE-2023-52884, CVE-2024-26810, CVE-2024-35989, CVE-2024-36894,\nCVE-2024-39471, CVE-2024-35900, CVE-2024-42097, CVE-2024-36959,\nCVE-2024-26931, CVE-2024-40934, CVE-2024-36947, CVE-2024-34777,\nCVE-2024-27018, CVE-2024-39499, CVE-2024-36906, CVE-2024-35984,\nCVE-2024-39500, CVE-2024-26965, CVE-2024-26921, CVE-2024-27013,\nCVE-2024-39509, CVE-2024-27008, CVE-2024-36916, CVE-2024-40942,\nCVE-2024-35978, CVE-2024-26969, CVE-2024-26964, CVE-2024-35879,\nCVE-2024-36016, CVE-2024-26629, CVE-2024-42236, CVE-2024-40943,\nCVE-2024-36902, CVE-2024-42247, CVE-2024-36006, CVE-2024-36014,\nCVE-2024-26955, CVE-2024-39277, CVE-2024-39506, CVE-2024-35936,\nCVE-2024-26950, CVE-2024-35938, CVE-2024-41035, CVE-2024-42140,\nCVE-2024-36971, CVE-2024-35910, CVE-2024-34027, CVE-2024-35933,\nCVE-2024-35886, CVE-2024-39501, CVE-2024-42109, CVE-2024-42157,\nCVE-2024-35905, CVE-2024-41007, CVE-2024-40912, CVE-2024-26984,\nCVE-2024-35915, CVE-2024-35934, CVE-2024-38633, CVE-2024-26952,\nCVE-2024-27017, CVE-2024-38627, CVE-2024-42070, CVE-2024-41046,\nCVE-2024-35821, CVE-2024-35815, CVE-2024-36978, CVE-2024-36967,\nCVE-2023-52752, CVE-2024-38583, CVE-2024-38578, CVE-2024-26926,\nCVE-2023-52699, CVE-2024-36952, CVE-2024-38600, CVE-2024-42102,\nCVE-2024-38559, CVE-2024-38637, CVE-2024-42082, CVE-2023-52488,\nCVE-2024-36032, CVE-2024-35950, CVE-2024-35930, CVE-2024-38780,\nCVE-2024-40995, CVE-2024-36004, CVE-2024-26956, CVE-2024-35896,\nCVE-2024-26994, CVE-2024-38624, CVE-2024-39480, CVE-2023-52882,\nCVE-2024-35912, CVE-2024-36015, CVE-2024-27019, CVE-2024-40983,\nCVE-2023-52760, CVE-2024-39503, CVE-2024-36957, CVE-2024-26980,\nCVE-2024-40908, CVE-2024-40958, CVE-2024-35902, CVE-2024-42087,\nCVE-2024-36933, CVE-2024-38635, CVE-2024-26988, CVE-2024-36941,\nCVE-2024-26970, CVE-2024-36005, CVE-2024-36029, CVE-2024-36008,\nCVE-2024-42244, CVE-2024-40967, CVE-2023-52585, CVE-2024-26951,\nCVE-2024-39475, CVE-2024-35922, CVE-2024-36901, CVE-2024-40901,\nCVE-2024-36031, CVE-2024-41000, CVE-2024-40929, CVE-2024-40994,\nCVE-2024-42084, CVE-2024-38547, CVE-2024-26937, CVE-2024-40984,\nCVE-2024-27000, CVE-2024-35785, CVE-2024-35849, CVE-2024-42119,\nCVE-2024-35947, CVE-2024-39505, CVE-2024-42092, CVE-2024-26811,\nCVE-2024-35935, CVE-2024-36946, CVE-2024-40990, CVE-2024-26981,\nCVE-2024-38596, CVE-2024-40976, CVE-2024-36880)\n","status":"published","published":"2024-09-18T10:00:09Z","modified":"2026-10-26T22:33:18.442136814Z","updated_at":"2026-11-02T16:58:18.876384Z"},{"id":"USN-7089-1","title":"linux, linux-gcp-6.8, linux-hwe-6.8 vulnerabilities","description":"Chenyuan Yang discovered that the USB Gadget subsystem in the Linux kernel\ndid not properly check for the device to be enabled before writing. A local\nattacker could possibly use this to cause a denial of service. (CVE-2024-25741)\n\nSeveral security issues were discovered in the Linux kernel.\nAn attacker could possibly use these to compromise the system.\nThis update corrects flaws in the following subsystems:\n  - ARM32 architecture;\n  - MIPS architecture;\n  - PA-RISC architecture;\n  - PowerPC architecture;\n  - RISC-V architecture;\n  - S390 architecture;\n  - x86 architecture;\n  - Cryptographic API;\n  - Serial ATA and Parallel ATA drivers;\n  - Null block device driver;\n  - Bluetooth drivers;\n  - Cdrom driver;\n  - Clock framework and drivers;\n  - Hardware crypto device drivers;\n  - CXL (Compute Express Link) drivers;\n  - Cirrus firmware drivers;\n  - GPIO subsystem;\n  - GPU drivers;\n  - I2C subsystem;\n  - IIO subsystem;\n  - InfiniBand drivers;\n  - ISDN/mISDN subsystem;\n  - LED subsystem;\n  - Multiple devices driver;\n  - Media drivers;\n  - Fastrpc Driver;\n  - Network drivers;\n  - Microsoft Azure Network Adapter (MANA) driver;\n  - Near Field Communication (NFC) drivers;\n  - NVME drivers;\n  - NVMEM (Non Volatile Memory) drivers;\n  - PCI subsystem;\n  - Pin controllers subsystem;\n  - x86 platform drivers;\n  - S/390 drivers;\n  - SCSI drivers;\n  - Thermal drivers;\n  - TTY drivers;\n  - UFS subsystem;\n  - USB DSL drivers;\n  - USB core drivers;\n  - DesignWare USB3 driver;\n  - USB Gadget drivers;\n  - USB Serial drivers;\n  - VFIO drivers;\n  - VHOST drivers;\n  - File systems infrastructure;\n  - BTRFS file system;\n  - GFS2 file system;\n  - JFFS2 file system;\n  - JFS file system;\n  - Network file systems library;\n  - Network file system client;\n  - NILFS2 file system;\n  - NTFS3 file system;\n  - SMB network file system;\n  - Memory management;\n  - Netfilter;\n  - Tracing infrastructure;\n  - io_uring subsystem;\n  - BPF subsystem;\n  - Core kernel;\n  - Bluetooth subsystem;\n  - CAN network layer;\n  - Ceph Core library;\n  - Networking core;\n  - IPv4 networking;\n  - IPv6 networking;\n  - IUCV driver;\n  - MAC80211 subsystem;\n  - Network traffic control;\n  - Sun RPC protocol;\n  - Wireless networking;\n  - AMD SoC Alsa drivers;\n  - SoC Audio for Freescale CPUs drivers;\n  - MediaTek ASoC drivers;\n  - SoC audio core drivers;\n  - SOF drivers;\n  - Sound sequencer drivers;\n(CVE-2024-42104, CVE-2024-42084, CVE-2024-42252, CVE-2024-41096,\nCVE-2024-42237, CVE-2024-42140, CVE-2024-42150, CVE-2024-41031,\nCVE-2024-41059, CVE-2024-41062, CVE-2024-41051, CVE-2024-41028,\nCVE-2024-41090, CVE-2024-41092, CVE-2024-43855, CVE-2024-41021,\nCVE-2024-42229, CVE-2024-41056, CVE-2024-41048, CVE-2024-41036,\nCVE-2024-42094, CVE-2024-41089, CVE-2024-41068, CVE-2024-41039,\nCVE-2024-41095, CVE-2024-41069, CVE-2024-42234, CVE-2024-42136,\nCVE-2024-41025, CVE-2024-42157, CVE-2024-42248, CVE-2024-42087,\nCVE-2024-41041, CVE-2024-42230, CVE-2024-42151, CVE-2024-42130,\nCVE-2024-42244, CVE-2024-41079, CVE-2024-42253, CVE-2024-42092,\nCVE-2024-41022, CVE-2024-42137, CVE-2024-42132, CVE-2024-42108,\nCVE-2024-42155, CVE-2024-42127, CVE-2024-41060, CVE-2024-42074,\nCVE-2024-41081, CVE-2024-42066, CVE-2024-42098, CVE-2024-42082,\nCVE-2024-42093, CVE-2024-42245, CVE-2024-41072, CVE-2024-41052,\nCVE-2024-42161, CVE-2024-42096, CVE-2024-42115, CVE-2024-41074,\nCVE-2024-42120, CVE-2024-41046, CVE-2024-42239, CVE-2024-41063,\nCVE-2024-42090, CVE-2024-41023, CVE-2024-42069, CVE-2024-41087,\nCVE-2024-42158, CVE-2024-41067, CVE-2024-41084, CVE-2024-41077,\nCVE-2024-42240, CVE-2024-42145, CVE-2024-42102, CVE-2024-41020,\nCVE-2024-42231, CVE-2024-41053, CVE-2024-42131, CVE-2024-42089,\nCVE-2024-41083, CVE-2024-42247, CVE-2024-42105, CVE-2024-41044,\nCVE-2024-42128, CVE-2024-42271, CVE-2024-41037, CVE-2024-42114,\nCVE-2024-42106, CVE-2024-41076, CVE-2024-42088, CVE-2024-41057,\nCVE-2024-41091, CVE-2024-42152, CVE-2024-41070, CVE-2024-41035,\nCVE-2024-41050, CVE-2024-39487, CVE-2024-42113, CVE-2024-42250,\nCVE-2024-41047, CVE-2024-42149, CVE-2024-42079, CVE-2024-42091,\nCVE-2024-42227, CVE-2024-42095, CVE-2024-42109, CVE-2024-41033,\nCVE-2023-52888, CVE-2024-41061, CVE-2024-42223, CVE-2024-42235,\nCVE-2024-41086, CVE-2024-42133, CVE-2024-41082, CVE-2024-41071,\nCVE-2024-41007, CVE-2023-52887, CVE-2024-39486, CVE-2024-41075,\nCVE-2024-42101, CVE-2024-42077, CVE-2024-41042, CVE-2024-42225,\nCVE-2024-42126, CVE-2024-41094, CVE-2024-41085, CVE-2024-41019,\nCVE-2024-41058, CVE-2024-41066, CVE-2024-42156, CVE-2024-42119,\nCVE-2024-41032, CVE-2024-41088, CVE-2024-42100, CVE-2024-42142,\nCVE-2024-41054, CVE-2024-42103, CVE-2024-42124, CVE-2024-41034,\nCVE-2024-42251, CVE-2024-42153, CVE-2024-41045, CVE-2024-42086,\nCVE-2024-42243, CVE-2024-41055, CVE-2024-41078, CVE-2024-42117,\nCVE-2024-41030, CVE-2024-42068, CVE-2024-42110, CVE-2024-42147,\nCVE-2024-42121, CVE-2024-41080, CVE-2024-41027, CVE-2024-43858,\nCVE-2024-42085, CVE-2024-42111, CVE-2024-42238, CVE-2024-41018,\nCVE-2024-42138, CVE-2024-41038, CVE-2024-42070, CVE-2024-42141,\nCVE-2024-41098, CVE-2024-42118, CVE-2024-41073, CVE-2024-42144,\nCVE-2024-42280, CVE-2024-41049, CVE-2024-42076, CVE-2024-41065,\nCVE-2024-42063, CVE-2024-41064, CVE-2024-41017, CVE-2024-42112,\nCVE-2024-42064, CVE-2024-42135, CVE-2024-42146, CVE-2024-41010,\nCVE-2024-41097, CVE-2024-41012, CVE-2024-42097, CVE-2024-42067,\nCVE-2024-42236, CVE-2024-42080, CVE-2024-42241, CVE-2024-42065,\nCVE-2024-42232, CVE-2024-42246, CVE-2024-41093, CVE-2024-41015,\nCVE-2024-42129, CVE-2024-42073, CVE-2024-41029)\n","status":"published","published":"2024-11-01T13:15:22Z","modified":"2026-10-26T22:33:59.398740884Z","updated_at":"2026-11-02T16:58:18.876384Z"},{"id":"USN-7089-2","title":"linux-azure, linux-gcp, linux-ibm vulnerabilities","description":"\nChenyuan Yang discovered that the USB Gadget subsystem in the Linux\nkernel did not properly check for the device to be enabled before\nwriting. A local attacker could possibly use this to cause a denial of\nservice. (CVE-2024-25741)\n\nSeveral security issues were discovered in the Linux kernel.\nAn attacker could possibly use these to compromise the system.\nThis update corrects flaws in the following subsystems:\n  - ARM32 architecture;\n  - MIPS architecture;\n  - PA-RISC architecture;\n  - PowerPC architecture;\n  - RISC-V architecture;\n  - S390 architecture;\n  - x86 architecture;\n  - Cryptographic API;\n  - Serial ATA and Parallel ATA drivers;\n  - Null block device driver;\n  - Bluetooth drivers;\n  - Cdrom driver;\n  - Clock framework and drivers;\n  - Hardware crypto device drivers;\n  - CXL (Compute Express Link) drivers;\n  - Cirrus firmware drivers;\n  - GPIO subsystem;\n  - GPU drivers;\n  - I2C subsystem;\n  - IIO subsystem;\n  - InfiniBand drivers;\n  - ISDN/mISDN subsystem;\n  - LED subsystem;\n  - Multiple devices driver;\n  - Media drivers;\n  - Fastrpc Driver;\n  - Network drivers;\n  - Microsoft Azure Network Adapter (MANA) driver;\n  - Near Field Communication (NFC) drivers;\n  - NVME drivers;\n  - NVMEM (Non Volatile Memory) drivers;\n  - PCI subsystem;\n  - Pin controllers subsystem;\n  - x86 platform drivers;\n  - S/390 drivers;\n  - SCSI drivers;\n  - Thermal drivers;\n  - TTY drivers;\n  - UFS subsystem;\n  - USB DSL drivers;\n  - USB core drivers;\n  - DesignWare USB3 driver;\n  - USB Gadget drivers;\n  - USB Serial drivers;\n  - VFIO drivers;\n  - VHOST drivers;\n  - File systems infrastructure;\n  - BTRFS file system;\n  - GFS2 file system;\n  - JFFS2 file system;\n  - JFS file system;\n  - Network file systems library;\n  - Network file system client;\n  - NILFS2 file system;\n  - NTFS3 file system;\n  - SMB network file system;\n  - Memory management;\n  - Netfilter;\n  - Tracing infrastructure;\n  - io_uring subsystem;\n  - BPF subsystem;\n  - Core kernel;\n  - Bluetooth subsystem;\n  - CAN network layer;\n  - Ceph Core library;\n  - Networking core;\n  - IPv4 networking;\n  - IPv6 networking;\n  - IUCV driver;\n  - MAC80211 subsystem;\n  - Network traffic control;\n  - Sun RPC protocol;\n  - Wireless networking;\n  - AMD SoC Alsa drivers;\n  - SoC Audio for Freescale CPUs drivers;\n  - MediaTek ASoC drivers;\n  - SoC audio core drivers;\n  - SOF drivers;\n  - Sound sequencer drivers;\n(CVE-2024-42104, CVE-2024-42101, CVE-2024-41052, CVE-2024-42157,\nCVE-2024-41020, CVE-2024-41055, CVE-2024-42124, CVE-2023-52888,\nCVE-2024-42079, CVE-2024-43858, CVE-2024-41075, CVE-2024-42073,\nCVE-2024-42113, CVE-2024-42110, CVE-2024-41080, CVE-2024-42097,\nCVE-2024-41046, CVE-2024-42076, CVE-2024-41010, CVE-2024-41018,\nCVE-2024-42115, CVE-2024-41048, CVE-2024-42231, CVE-2024-42241,\nCVE-2024-41034, CVE-2024-42065, CVE-2024-42140, CVE-2024-42094,\nCVE-2024-41029, CVE-2024-42225, CVE-2024-41096, CVE-2024-42088,\nCVE-2024-41087, CVE-2023-52887, CVE-2024-42141, CVE-2024-42135,\nCVE-2024-42247, CVE-2024-39487, CVE-2024-42229, CVE-2024-42147,\nCVE-2024-42252, CVE-2024-41038, CVE-2024-41083, CVE-2024-42091,\nCVE-2024-42156, CVE-2024-42149, CVE-2024-41015, CVE-2024-41047,\nCVE-2024-42129, CVE-2024-42120, CVE-2024-41097, CVE-2024-42243,\nCVE-2024-42084, CVE-2024-42250, CVE-2024-41023, CVE-2024-41028,\nCVE-2024-42108, CVE-2024-41045, CVE-2024-42098, CVE-2024-41064,\nCVE-2024-42087, CVE-2024-42080, CVE-2024-41049, CVE-2024-42271,\nCVE-2024-41037, CVE-2024-42114, CVE-2024-41044, CVE-2024-42126,\nCVE-2024-42119, CVE-2024-42223, CVE-2024-42280, CVE-2024-42112,\nCVE-2024-41019, CVE-2024-42133, CVE-2024-42152, CVE-2024-41074,\nCVE-2024-41042, CVE-2024-41093, CVE-2024-41025, CVE-2024-42253,\nCVE-2024-42136, CVE-2024-42127, CVE-2024-41036, CVE-2024-42237,\nCVE-2024-42111, CVE-2024-41031, CVE-2024-41069, CVE-2024-41084,\nCVE-2024-41076, CVE-2024-41090, CVE-2024-41088, CVE-2024-41070,\nCVE-2024-42118, CVE-2024-42238, CVE-2024-42234, CVE-2024-41089,\nCVE-2024-41095, CVE-2024-41085, CVE-2024-42106, CVE-2024-42155,\nCVE-2024-42146, CVE-2024-42130, CVE-2024-42089, CVE-2024-42132,\nCVE-2024-41091, CVE-2024-42153, CVE-2024-42236, CVE-2024-42085,\nCVE-2024-41065, CVE-2024-41032, CVE-2024-42090, CVE-2024-41030,\nCVE-2024-41017, CVE-2024-42230, CVE-2024-42144, CVE-2024-42137,\nCVE-2024-41082, CVE-2024-41056, CVE-2024-42145, CVE-2024-41041,\nCVE-2024-42240, CVE-2024-41081, CVE-2024-42103, CVE-2024-41053,\nCVE-2024-42070, CVE-2024-42121, CVE-2024-42105, CVE-2024-41022,\nCVE-2024-42151, CVE-2024-42142, CVE-2024-41035, CVE-2024-42232,\nCVE-2024-41058, CVE-2024-42109, CVE-2024-41077, CVE-2024-42095,\nCVE-2024-39486, CVE-2024-42131, CVE-2024-42068, CVE-2024-41073,\nCVE-2024-41079, CVE-2024-42082, CVE-2024-41071, CVE-2024-41066,\nCVE-2024-42102, CVE-2024-43855, CVE-2024-41061, CVE-2024-41072,\nCVE-2024-41059, CVE-2024-41094, CVE-2024-41021, CVE-2024-41098,\nCVE-2024-42158, CVE-2024-41033, CVE-2024-42096, CVE-2024-42251,\nCVE-2024-42077, CVE-2024-42063, CVE-2024-42227, CVE-2024-41007,\nCVE-2024-41057, CVE-2024-41063, CVE-2024-41039, CVE-2024-41067,\nCVE-2024-41062, CVE-2024-42100, CVE-2024-42074, CVE-2024-42064,\nCVE-2024-41092, CVE-2024-42128, CVE-2024-41086, CVE-2024-41054,\nCVE-2024-42239, CVE-2024-41027, CVE-2024-42093, CVE-2024-42244,\nCVE-2024-41050, CVE-2024-41012, CVE-2024-42246, CVE-2024-42117,\nCVE-2024-42069, CVE-2024-42067, CVE-2024-42086, CVE-2024-42066,\nCVE-2024-41060, CVE-2024-42248, CVE-2024-41068, CVE-2024-42161,\nCVE-2024-42092, CVE-2024-42245, CVE-2024-41078, CVE-2024-42235,\nCVE-2024-42150, CVE-2024-41051, CVE-2024-42138)\n","status":"published","published":"2024-11-04T17:30:30Z","modified":"2026-10-26T22:34:00.39355758Z","updated_at":"2026-11-02T16:58:18.876384Z"},{"id":"USN-7089-3","title":"linux-aws, linux-aws-6.8, linux-oracle, linux-oracle-6.8 vulnerabilities","description":"\nChenyuan Yang discovered that the USB Gadget subsystem in the Linux\nkernel did not properly check for the device to be enabled before\nwriting. A local attacker could possibly use this to cause a denial of\nservice. (CVE-2024-25741)\n\nSeveral security issues were discovered in the Linux kernel.\nAn attacker could possibly use these to compromise the system.\nThis update corrects flaws in the following subsystems:\n  - ARM32 architecture;\n  - MIPS architecture;\n  - PA-RISC architecture;\n  - PowerPC architecture;\n  - RISC-V architecture;\n  - S390 architecture;\n  - x86 architecture;\n  - Cryptographic API;\n  - Serial ATA and Parallel ATA drivers;\n  - Null block device driver;\n  - Bluetooth drivers;\n  - Cdrom driver;\n  - Clock framework and drivers;\n  - Hardware crypto device drivers;\n  - CXL (Compute Express Link) drivers;\n  - Cirrus firmware drivers;\n  - GPIO subsystem;\n  - GPU drivers;\n  - I2C subsystem;\n  - IIO subsystem;\n  - InfiniBand drivers;\n  - ISDN/mISDN subsystem;\n  - LED subsystem;\n  - Multiple devices driver;\n  - Media drivers;\n  - Fastrpc Driver;\n  - Network drivers;\n  - Microsoft Azure Network Adapter (MANA) driver;\n  - Near Field Communication (NFC) drivers;\n  - NVME drivers;\n  - NVMEM (Non Volatile Memory) drivers;\n  - PCI subsystem;\n  - Pin controllers subsystem;\n  - x86 platform drivers;\n  - S/390 drivers;\n  - SCSI drivers;\n  - Thermal drivers;\n  - TTY drivers;\n  - UFS subsystem;\n  - USB DSL drivers;\n  - USB core drivers;\n  - DesignWare USB3 driver;\n  - USB Gadget drivers;\n  - USB Serial drivers;\n  - VFIO drivers;\n  - VHOST drivers;\n  - File systems infrastructure;\n  - BTRFS file system;\n  - GFS2 file system;\n  - JFFS2 file system;\n  - JFS file system;\n  - Network file systems library;\n  - Network file system client;\n  - NILFS2 file system;\n  - NTFS3 file system;\n  - SMB network file system;\n  - Memory management;\n  - Netfilter;\n  - Tracing infrastructure;\n  - io_uring subsystem;\n  - BPF subsystem;\n  - Core kernel;\n  - Bluetooth subsystem;\n  - CAN network layer;\n  - Ceph Core library;\n  - Networking core;\n  - IPv4 networking;\n  - IPv6 networking;\n  - IUCV driver;\n  - MAC80211 subsystem;\n  - Network traffic control;\n  - Sun RPC protocol;\n  - Wireless networking;\n  - AMD SoC Alsa drivers;\n  - SoC Audio for Freescale CPUs drivers;\n  - MediaTek ASoC drivers;\n  - SoC audio core drivers;\n  - SOF drivers;\n  - Sound sequencer drivers;\n(CVE-2024-42239, CVE-2024-42079, CVE-2024-41080, CVE-2024-42064,\nCVE-2024-42127, CVE-2024-41049, CVE-2024-41086, CVE-2024-42142,\nCVE-2024-42244, CVE-2024-41060, CVE-2024-42131, CVE-2024-42085,\nCVE-2024-42246, CVE-2024-41062, CVE-2024-42115, CVE-2024-42234,\nCVE-2024-42080, CVE-2024-41095, CVE-2024-41063, CVE-2024-42227,\nCVE-2024-41089, CVE-2024-42133, CVE-2024-43858, CVE-2024-42135,\nCVE-2024-42113, CVE-2024-42120, CVE-2024-42149, CVE-2024-42132,\nCVE-2024-41038, CVE-2024-41069, CVE-2024-41090, CVE-2024-41059,\nCVE-2024-41028, CVE-2024-42126, CVE-2024-42121, CVE-2024-42155,\nCVE-2024-42110, CVE-2024-41021, CVE-2024-41044, CVE-2024-42098,\nCVE-2024-42235, CVE-2024-41083, CVE-2024-41065, CVE-2024-42094,\nCVE-2024-42229, CVE-2024-42240, CVE-2024-42225, CVE-2024-42230,\nCVE-2024-41088, CVE-2024-42073, CVE-2024-42145, CVE-2024-42076,\nCVE-2024-42087, CVE-2024-42241, CVE-2024-41019, CVE-2024-41052,\nCVE-2024-42093, CVE-2024-42063, CVE-2024-41039, CVE-2024-42106,\nCVE-2024-42108, CVE-2024-42237, CVE-2024-41048, CVE-2024-41033,\nCVE-2023-52888, CVE-2024-41096, CVE-2024-41032, CVE-2024-41091,\nCVE-2024-42238, CVE-2024-41056, CVE-2024-42091, CVE-2024-42088,\nCVE-2024-41047, CVE-2024-42271, CVE-2024-41064, CVE-2024-42223,\nCVE-2024-42129, CVE-2024-42102, CVE-2024-42146, CVE-2024-42138,\nCVE-2024-41079, CVE-2024-42232, CVE-2024-42112, CVE-2024-39487,\nCVE-2024-42245, CVE-2024-41093, CVE-2024-41066, CVE-2024-43855,\nCVE-2024-41055, CVE-2024-42100, CVE-2024-41053, CVE-2024-42069,\nCVE-2024-42252, CVE-2024-42243, CVE-2024-42124, CVE-2024-41054,\nCVE-2024-42151, CVE-2024-42118, CVE-2024-42251, CVE-2024-42137,\nCVE-2024-41071, CVE-2024-41010, CVE-2024-41087, CVE-2024-41050,\nCVE-2024-42068, CVE-2024-42158, CVE-2024-41075, CVE-2024-42141,\nCVE-2024-42236, CVE-2024-41068, CVE-2024-42157, CVE-2024-42140,\nCVE-2024-41058, CVE-2024-41076, CVE-2024-42097, CVE-2024-41029,\nCVE-2024-41097, CVE-2024-42109, CVE-2024-41051, CVE-2024-41061,\nCVE-2024-42156, CVE-2024-42101, CVE-2024-41031, CVE-2024-41017,\nCVE-2024-42247, CVE-2024-42128, CVE-2024-41085, CVE-2024-41072,\nCVE-2024-42248, CVE-2024-41045, CVE-2024-42104, CVE-2024-42253,\nCVE-2024-42117, CVE-2024-41078, CVE-2024-42130, CVE-2024-42090,\nCVE-2024-42280, CVE-2024-42250, CVE-2024-42231, CVE-2024-41042,\nCVE-2024-42077, CVE-2024-42153, CVE-2024-41015, CVE-2024-41035,\nCVE-2024-41082, CVE-2024-42114, CVE-2024-41007, CVE-2024-41073,\nCVE-2024-42161, CVE-2024-42082, CVE-2024-42150, CVE-2024-42111,\nCVE-2024-42086, CVE-2024-42095, CVE-2024-41025, CVE-2024-41081,\nCVE-2024-42105, CVE-2024-41027, CVE-2024-42089, CVE-2024-39486,\nCVE-2024-41084, CVE-2024-42092, CVE-2024-42152, CVE-2024-41022,\nCVE-2024-41077, CVE-2024-41098, CVE-2024-41023, CVE-2024-42066,\nCVE-2024-41034, CVE-2024-41037, CVE-2024-41046, CVE-2023-52887,\nCVE-2024-42147, CVE-2024-42065, CVE-2024-42096, CVE-2024-41018,\nCVE-2024-42067, CVE-2024-41041, CVE-2024-42103, CVE-2024-42084,\nCVE-2024-42074, CVE-2024-41094, CVE-2024-42119, CVE-2024-41012,\nCVE-2024-41020, CVE-2024-41074, CVE-2024-42144, CVE-2024-41067,\nCVE-2024-42070, CVE-2024-41057, CVE-2024-41036, CVE-2024-42136,\nCVE-2024-41030, CVE-2024-41070, CVE-2024-41092)\n","status":"published","published":"2024-11-07T09:15:50Z","modified":"2026-10-26T22:34:10.691578849Z","updated_at":"2026-11-02T16:58:18.876384Z"},{"id":"USN-7089-4","title":"linux-oem-6.8 vulnerabilities","description":"\nChenyuan Yang discovered that the USB Gadget subsystem in the Linux\nkernel did not properly check for the device to be enabled before\nwriting. A local attacker could possibly use this to cause a denial of\nservice. (CVE-2024-25741)\n\nSeveral security issues were discovered in the Linux kernel.\nAn attacker could possibly use these to compromise the system.\nThis update corrects flaws in the following subsystems:\n  - ARM32 architecture;\n  - MIPS architecture;\n  - PA-RISC architecture;\n  - PowerPC architecture;\n  - RISC-V architecture;\n  - S390 architecture;\n  - x86 architecture;\n  - Cryptographic API;\n  - Serial ATA and Parallel ATA drivers;\n  - Null block device driver;\n  - Bluetooth drivers;\n  - Cdrom driver;\n  - Clock framework and drivers;\n  - Hardware crypto device drivers;\n  - CXL (Compute Express Link) drivers;\n  - Cirrus firmware drivers;\n  - GPIO subsystem;\n  - GPU drivers;\n  - I2C subsystem;\n  - IIO subsystem;\n  - InfiniBand drivers;\n  - ISDN/mISDN subsystem;\n  - LED subsystem;\n  - Multiple devices driver;\n  - Media drivers;\n  - Fastrpc Driver;\n  - Network drivers;\n  - Microsoft Azure Network Adapter (MANA) driver;\n  - Near Field Communication (NFC) drivers;\n  - NVME drivers;\n  - NVMEM (Non Volatile Memory) drivers;\n  - PCI subsystem;\n  - Pin controllers subsystem;\n  - x86 platform drivers;\n  - S/390 drivers;\n  - SCSI drivers;\n  - Thermal drivers;\n  - TTY drivers;\n  - UFS subsystem;\n  - USB DSL drivers;\n  - USB core drivers;\n  - DesignWare USB3 driver;\n  - USB Gadget drivers;\n  - USB Serial drivers;\n  - VFIO drivers;\n  - VHOST drivers;\n  - File systems infrastructure;\n  - BTRFS file system;\n  - GFS2 file system;\n  - JFFS2 file system;\n  - JFS file system;\n  - Network file systems library;\n  - Network file system client;\n  - NILFS2 file system;\n  - NTFS3 file system;\n  - SMB network file system;\n  - Memory management;\n  - Netfilter;\n  - Tracing infrastructure;\n  - io_uring subsystem;\n  - BPF subsystem;\n  - Core kernel;\n  - Bluetooth subsystem;\n  - CAN network layer;\n  - Ceph Core library;\n  - Networking core;\n  - IPv4 networking;\n  - IPv6 networking;\n  - IUCV driver;\n  - MAC80211 subsystem;\n  - Network traffic control;\n  - Sun RPC protocol;\n  - Wireless networking;\n  - AMD SoC Alsa drivers;\n  - SoC Audio for Freescale CPUs drivers;\n  - MediaTek ASoC drivers;\n  - SoC audio core drivers;\n  - SOF drivers;\n  - Sound sequencer drivers;\n(CVE-2024-41064, CVE-2024-41087, CVE-2023-52888, CVE-2024-42098,\nCVE-2024-42111, CVE-2024-42076, CVE-2024-42088, CVE-2024-42135,\nCVE-2024-42145, CVE-2024-42142, CVE-2024-41036, CVE-2024-41071,\nCVE-2024-41012, CVE-2024-42091, CVE-2024-42253, CVE-2024-42119,\nCVE-2024-42097, CVE-2024-42243, CVE-2024-39487, CVE-2024-42235,\nCVE-2024-42120, CVE-2024-42149, CVE-2024-41015, CVE-2024-41074,\nCVE-2024-42067, CVE-2024-42090, CVE-2024-42128, CVE-2024-41038,\nCVE-2024-42113, CVE-2024-42102, CVE-2024-42231, CVE-2024-42080,\nCVE-2024-42241, CVE-2024-42106, CVE-2024-42130, CVE-2024-42073,\nCVE-2024-42153, CVE-2024-42156, CVE-2024-42118, CVE-2024-41007,\nCVE-2024-41049, CVE-2024-39486, CVE-2024-42240, CVE-2024-41018,\nCVE-2024-42251, CVE-2024-42280, CVE-2024-42096, CVE-2024-42121,\nCVE-2024-42246, CVE-2024-42092, CVE-2024-41090, CVE-2024-42157,\nCVE-2024-43858, CVE-2024-42150, CVE-2024-42110, CVE-2024-41010,\nCVE-2024-41081, CVE-2024-41061, CVE-2024-41078, CVE-2024-41094,\nCVE-2024-41039, CVE-2024-42114, CVE-2024-42109, CVE-2024-41030,\nCVE-2024-42066, CVE-2024-41035, CVE-2024-42146, CVE-2024-42131,\nCVE-2024-41059, CVE-2024-41067, CVE-2024-42138, CVE-2024-41050,\nCVE-2024-41034, CVE-2024-41077, CVE-2024-41076, CVE-2024-41088,\nCVE-2024-41096, CVE-2024-41073, CVE-2024-41037, CVE-2024-42232,\nCVE-2024-41063, CVE-2024-42117, CVE-2024-42155, CVE-2024-41080,\nCVE-2024-42132, CVE-2024-42084, CVE-2024-42136, CVE-2024-42223,\nCVE-2024-41068, CVE-2024-42225, CVE-2024-42065, CVE-2024-41051,\nCVE-2024-43855, CVE-2024-42238, CVE-2024-42250, CVE-2024-42112,\nCVE-2024-41070, CVE-2023-52887, CVE-2024-42094, CVE-2024-42095,\nCVE-2024-41086, CVE-2024-41020, CVE-2024-41082, CVE-2024-42115,\nCVE-2024-42152, CVE-2024-42239, CVE-2024-42093, CVE-2024-42126,\nCVE-2024-41022, CVE-2024-41017, CVE-2024-41092, CVE-2024-41044,\nCVE-2024-42140, CVE-2024-41029, CVE-2024-41054, CVE-2024-42158,\nCVE-2024-41066, CVE-2024-42244, CVE-2024-42070, CVE-2024-41025,\nCVE-2024-42229, CVE-2024-42085, CVE-2024-41084, CVE-2024-41060,\nCVE-2024-41062, CVE-2024-42105, CVE-2024-42124, CVE-2024-41045,\nCVE-2024-42227, CVE-2024-41047, CVE-2024-41042, CVE-2024-42100,\nCVE-2024-42247, CVE-2024-41041, CVE-2024-42087, CVE-2024-42252,\nCVE-2024-41058, CVE-2024-42063, CVE-2024-42271, CVE-2024-41027,\nCVE-2024-42079, CVE-2024-42104, CVE-2024-41098, CVE-2024-41033,\nCVE-2024-41072, CVE-2024-41031, CVE-2024-42089, CVE-2024-41032,\nCVE-2024-42127, CVE-2024-41093, CVE-2024-42082, CVE-2024-41023,\nCVE-2024-41075, CVE-2024-42151, CVE-2024-42141, CVE-2024-42108,\nCVE-2024-42068, CVE-2024-41085, CVE-2024-42103, CVE-2024-41057,\nCVE-2024-42064, CVE-2024-42161, CVE-2024-41052, CVE-2024-41053,\nCVE-2024-42069, CVE-2024-41021, CVE-2024-42147, CVE-2024-41065,\nCVE-2024-41091, CVE-2024-41079, CVE-2024-42086, CVE-2024-42234,\nCVE-2024-41055, CVE-2024-41083, CVE-2024-42101, CVE-2024-42230,\nCVE-2024-41095, CVE-2024-41019, CVE-2024-42245, CVE-2024-42129,\nCVE-2024-42144, CVE-2024-42236, CVE-2024-41028, CVE-2024-42077,\nCVE-2024-42248, CVE-2024-41046, CVE-2024-42133, CVE-2024-42074,\nCVE-2024-41089, CVE-2024-42237, CVE-2024-41056, CVE-2024-41048,\nCVE-2024-42137, CVE-2024-41069, CVE-2024-41097)\n","status":"published","published":"2024-11-13T12:05:57Z","modified":"2026-10-26T22:33:54.911543556Z","updated_at":"2026-11-02T16:58:18.876384Z"},{"id":"USN-7089-5","title":"linux-raspi vulnerabilities","description":"Chenyuan Yang discovered that the USB Gadget subsystem in the Linux\nkernel did not properly check for the device to be enabled before\nwriting. A local attacker could possibly use this to cause a denial of\nservice. (CVE-2024-25741)\n\nSeveral security issues were discovered in the Linux kernel.\nAn attacker could possibly use these to compromise the system.\nThis update corrects flaws in the following subsystems:\n  - ARM32 architecture;\n  - MIPS architecture;\n  - PA-RISC architecture;\n  - PowerPC architecture;\n  - RISC-V architecture;\n  - S390 architecture;\n  - x86 architecture;\n  - Cryptographic API;\n  - Serial ATA and Parallel ATA drivers;\n  - Null block device driver;\n  - Bluetooth drivers;\n  - Cdrom driver;\n  - Clock framework and drivers;\n  - Hardware crypto device drivers;\n  - CXL (Compute Express Link) drivers;\n  - Cirrus firmware drivers;\n  - GPIO subsystem;\n  - GPU drivers;\n  - I2C subsystem;\n  - IIO subsystem;\n  - InfiniBand drivers;\n  - ISDN/mISDN subsystem;\n  - LED subsystem;\n  - Multiple devices driver;\n  - Media drivers;\n  - Fastrpc Driver;\n  - Network drivers;\n  - Microsoft Azure Network Adapter (MANA) driver;\n  - Near Field Communication (NFC) drivers;\n  - NVME drivers;\n  - NVMEM (Non Volatile Memory) drivers;\n  - PCI subsystem;\n  - Pin controllers subsystem;\n  - x86 platform drivers;\n  - S/390 drivers;\n  - SCSI drivers;\n  - Thermal drivers;\n  - TTY drivers;\n  - UFS subsystem;\n  - USB DSL drivers;\n  - USB core drivers;\n  - DesignWare USB3 driver;\n  - USB Gadget drivers;\n  - USB Serial drivers;\n  - VFIO drivers;\n  - VHOST drivers;\n  - File systems infrastructure;\n  - BTRFS file system;\n  - GFS2 file system;\n  - JFFS2 file system;\n  - JFS file system;\n  - Network file systems library;\n  - Network file system client;\n  - NILFS2 file system;\n  - NTFS3 file system;\n  - SMB network file system;\n  - Memory management;\n  - Netfilter;\n  - Tracing infrastructure;\n  - io_uring subsystem;\n  - BPF subsystem;\n  - Core kernel;\n  - Bluetooth subsystem;\n  - CAN network layer;\n  - Ceph Core library;\n  - Networking core;\n  - IPv4 networking;\n  - IPv6 networking;\n  - IUCV driver;\n  - MAC80211 subsystem;\n  - Network traffic control;\n  - Sun RPC protocol;\n  - Wireless networking;\n  - AMD SoC Alsa drivers;\n  - SoC Audio for Freescale CPUs drivers;\n  - MediaTek ASoC drivers;\n  - SoC audio core drivers;\n  - SOF drivers;\n  - Sound sequencer drivers;\n(CVE-2024-42223, CVE-2024-42244, CVE-2024-42105, CVE-2024-42100,\nCVE-2024-42235, CVE-2024-41007, CVE-2024-41047, CVE-2024-42088,\nCVE-2024-42079, CVE-2024-41053, CVE-2024-41094, CVE-2024-42227,\nCVE-2024-42253, CVE-2024-42150, CVE-2024-41049, CVE-2024-42096,\nCVE-2024-42093, CVE-2024-41079, CVE-2024-41037, CVE-2024-42129,\nCVE-2024-41031, CVE-2024-39486, CVE-2024-41065, CVE-2024-42101,\nCVE-2024-41082, CVE-2024-42135, CVE-2024-42236, CVE-2024-41078,\nCVE-2024-42098, CVE-2024-41056, CVE-2024-41096, CVE-2024-41074,\nCVE-2024-42246, CVE-2024-42137, CVE-2024-42232, CVE-2024-42121,\nCVE-2024-41093, CVE-2024-41076, CVE-2024-42157, CVE-2024-41062,\nCVE-2024-42104, CVE-2024-42085, CVE-2024-41092, CVE-2024-41034,\nCVE-2024-41036, CVE-2024-41072, CVE-2024-41012, CVE-2024-39487,\nCVE-2024-42124, CVE-2024-42065, CVE-2024-41061, CVE-2024-41064,\nCVE-2024-41091, CVE-2024-42119, CVE-2024-41088, CVE-2024-42089,\nCVE-2024-41048, CVE-2024-41032, CVE-2024-41020, CVE-2024-42066,\nCVE-2024-42068, CVE-2024-42238, CVE-2024-41069, CVE-2024-41044,\nCVE-2024-41025, CVE-2024-42161, CVE-2023-52887, CVE-2024-42127,\nCVE-2024-42239, CVE-2024-42149, CVE-2024-42091, CVE-2024-42097,\nCVE-2024-41054, CVE-2024-41041, CVE-2024-42131, CVE-2024-41089,\nCVE-2024-41018, CVE-2024-42067, CVE-2024-41039, CVE-2024-42128,\nCVE-2024-42248, CVE-2024-41090, CVE-2024-42073, CVE-2024-43858,\nCVE-2024-42225, CVE-2024-42077, CVE-2024-42247, CVE-2024-42109,\nCVE-2024-41045, CVE-2024-41019, CVE-2024-42231, CVE-2024-41017,\nCVE-2024-42145, CVE-2024-41046, CVE-2024-42063, CVE-2024-41087,\nCVE-2024-41033, CVE-2024-41021, CVE-2024-42241, CVE-2024-42229,\nCVE-2024-41015, CVE-2024-42087, CVE-2024-42133, CVE-2024-41073,\nCVE-2024-42070, CVE-2024-41067, CVE-2024-41077, CVE-2024-42102,\nCVE-2024-42158, CVE-2024-42126, CVE-2024-41042, CVE-2024-41055,\nCVE-2024-42092, CVE-2024-42114, CVE-2024-41059, CVE-2024-41058,\nCVE-2024-41071, CVE-2024-42144, CVE-2024-42146, CVE-2024-41084,\nCVE-2024-42155, CVE-2024-42245, CVE-2024-42156, CVE-2024-41050,\nCVE-2024-42141, CVE-2024-42095, CVE-2024-41097, CVE-2024-42103,\nCVE-2024-42152, CVE-2024-42140, CVE-2024-41023, CVE-2024-41083,\nCVE-2024-42138, CVE-2024-42271, CVE-2024-42252, CVE-2024-42237,\nCVE-2024-42132, CVE-2024-41098, CVE-2024-42086, CVE-2024-41063,\nCVE-2024-42153, CVE-2024-41070, CVE-2024-42115, CVE-2024-42111,\nCVE-2024-42142, CVE-2024-42069, CVE-2024-41027, CVE-2024-42130,\nCVE-2024-42090, CVE-2024-42251, CVE-2024-42118, CVE-2024-41060,\nCVE-2024-41029, CVE-2024-41095, CVE-2024-41038, CVE-2024-42243,\nCVE-2024-42112, CVE-2024-41035, CVE-2024-42240, CVE-2024-41066,\nCVE-2024-41085, CVE-2024-42082, CVE-2024-42117, CVE-2024-42250,\nCVE-2024-41080, CVE-2024-42147, CVE-2024-41081, CVE-2024-42113,\nCVE-2023-52888, CVE-2024-42136, CVE-2024-41057, CVE-2024-41086,\nCVE-2024-42064, CVE-2024-42234, CVE-2024-42076, CVE-2024-42084,\nCVE-2024-42094, CVE-2024-42230, CVE-2024-41068, CVE-2024-43855,\nCVE-2024-42080, CVE-2024-41052, CVE-2024-41051, CVE-2024-42074,\nCVE-2024-41010, CVE-2024-41028, CVE-2024-41030, CVE-2024-41022,\nCVE-2024-42120, CVE-2024-42108, CVE-2024-41075, CVE-2024-42106,\nCVE-2024-42280, CVE-2024-42110, CVE-2024-42151)\n","status":"published","published":"2024-11-14T16:55:06Z","modified":"2026-10-26T22:33:56.031381167Z","updated_at":"2026-11-02T16:58:18.876384Z"},{"id":"USN-7089-6","title":"linux-gke vulnerabilities","description":"\nChenyuan Yang discovered that the USB Gadget subsystem in the Linux\nkernel did not properly check for the device to be enabled before\nwriting. A local attacker could possibly use this to cause a denial of\nservice. (CVE-2024-25741)\n\nSeveral security issues were discovered in the Linux kernel.\nAn attacker could possibly use these to compromise the system.\nThis update corrects flaws in the following subsystems:\n  - ARM32 architecture;\n  - MIPS architecture;\n  - PA-RISC architecture;\n  - PowerPC architecture;\n  - RISC-V architecture;\n  - S390 architecture;\n  - x86 architecture;\n  - Cryptographic API;\n  - Serial ATA and Parallel ATA drivers;\n  - Null block device driver;\n  - Bluetooth drivers;\n  - Cdrom driver;\n  - Clock framework and drivers;\n  - Hardware crypto device drivers;\n  - CXL (Compute Express Link) drivers;\n  - Cirrus firmware drivers;\n  - GPIO subsystem;\n  - GPU drivers;\n  - I2C subsystem;\n  - IIO subsystem;\n  - InfiniBand drivers;\n  - ISDN/mISDN subsystem;\n  - LED subsystem;\n  - Multiple devices driver;\n  - Media drivers;\n  - Fastrpc Driver;\n  - Network drivers;\n  - Microsoft Azure Network Adapter (MANA) driver;\n  - Near Field Communication (NFC) drivers;\n  - NVME drivers;\n  - NVMEM (Non Volatile Memory) drivers;\n  - PCI subsystem;\n  - Pin controllers subsystem;\n  - x86 platform drivers;\n  - S/390 drivers;\n  - SCSI drivers;\n  - Thermal drivers;\n  - TTY drivers;\n  - UFS subsystem;\n  - USB DSL drivers;\n  - USB core drivers;\n  - DesignWare USB3 driver;\n  - USB Gadget drivers;\n  - USB Serial drivers;\n  - VFIO drivers;\n  - VHOST drivers;\n  - File systems infrastructure;\n  - BTRFS file system;\n  - GFS2 file system;\n  - JFFS2 file system;\n  - JFS file system;\n  - Network file systems library;\n  - Network file system client;\n  - NILFS2 file system;\n  - NTFS3 file system;\n  - SMB network file system;\n  - Memory management;\n  - Netfilter;\n  - Tracing infrastructure;\n  - io_uring subsystem;\n  - BPF subsystem;\n  - Core kernel;\n  - Bluetooth subsystem;\n  - CAN network layer;\n  - Ceph Core library;\n  - Networking core;\n  - IPv4 networking;\n  - IPv6 networking;\n  - IUCV driver;\n  - MAC80211 subsystem;\n  - Network traffic control;\n  - Sun RPC protocol;\n  - Wireless networking;\n  - AMD SoC Alsa drivers;\n  - SoC Audio for Freescale CPUs drivers;\n  - MediaTek ASoC drivers;\n  - SoC audio core drivers;\n  - SOF drivers;\n  - Sound sequencer drivers;\n(CVE-2024-41062, CVE-2024-41029, CVE-2024-42142, CVE-2024-41070,\nCVE-2024-41066, CVE-2024-42150, CVE-2024-42120, CVE-2023-52888,\nCVE-2024-42141, CVE-2024-41032, CVE-2024-42245, CVE-2024-41053,\nCVE-2024-42247, CVE-2024-42161, CVE-2024-42094, CVE-2024-41072,\nCVE-2024-42076, CVE-2024-42091, CVE-2024-42103, CVE-2024-41007,\nCVE-2024-42064, CVE-2024-41075, CVE-2024-42157, CVE-2024-42069,\nCVE-2024-41045, CVE-2024-42068, CVE-2024-42090, CVE-2024-41071,\nCVE-2024-42082, CVE-2024-42146, CVE-2024-41018, CVE-2024-42238,\nCVE-2024-41079, CVE-2024-42241, CVE-2024-42067, CVE-2024-42132,\nCVE-2024-42121, CVE-2024-41025, CVE-2024-42231, CVE-2024-42225,\nCVE-2024-41080, CVE-2024-41086, CVE-2024-41012, CVE-2024-42234,\nCVE-2024-41088, CVE-2024-42129, CVE-2024-42158, CVE-2024-41078,\nCVE-2024-41038, CVE-2024-41055, CVE-2024-42106, CVE-2024-42227,\nCVE-2024-42102, CVE-2024-41082, CVE-2024-42108, CVE-2024-41085,\nCVE-2024-41020, CVE-2024-41054, CVE-2024-42085, CVE-2024-42140,\nCVE-2024-42089, CVE-2024-41047, CVE-2024-42092, CVE-2024-41044,\nCVE-2024-42246, CVE-2024-41035, CVE-2024-42250, CVE-2024-42070,\nCVE-2024-41039, CVE-2024-41061, CVE-2024-42147, CVE-2024-42104,\nCVE-2024-41090, CVE-2024-41096, CVE-2024-41063, CVE-2024-41084,\nCVE-2024-41059, CVE-2024-41097, CVE-2024-41089, CVE-2024-42093,\nCVE-2024-42126, CVE-2024-42135, CVE-2024-42128, CVE-2024-42098,\nCVE-2024-42105, CVE-2024-42124, CVE-2024-42101, CVE-2024-41091,\nCVE-2024-42127, CVE-2024-41077, CVE-2024-42111, CVE-2024-41037,\nCVE-2024-42136, CVE-2024-41083, CVE-2024-42243, CVE-2024-41033,\nCVE-2024-41046, CVE-2024-42230, CVE-2024-42080, CVE-2024-42096,\nCVE-2024-42100, CVE-2024-42236, CVE-2024-41022, CVE-2024-42086,\nCVE-2024-42251, CVE-2024-41015, CVE-2024-41027, CVE-2024-42155,\nCVE-2024-42117, CVE-2024-41036, CVE-2024-42133, CVE-2024-41010,\nCVE-2024-42151, CVE-2024-42118, CVE-2024-39486, CVE-2024-42066,\nCVE-2024-42131, CVE-2024-42223, CVE-2024-41081, CVE-2024-42244,\nCVE-2024-41073, CVE-2024-42114, CVE-2024-42252, CVE-2024-42248,\nCVE-2024-42110, CVE-2024-41051, CVE-2023-52887, CVE-2024-42156,\nCVE-2024-41074, CVE-2024-41017, CVE-2024-42079, CVE-2024-41034,\nCVE-2024-41028, CVE-2024-42109, CVE-2024-42235, CVE-2024-41058,\nCVE-2024-42232, CVE-2024-42084, CVE-2024-41076, CVE-2024-41030,\nCVE-2024-41023, CVE-2024-42271, CVE-2024-41050, CVE-2024-41042,\nCVE-2024-41031, CVE-2024-42112, CVE-2024-41092, CVE-2024-42253,\nCVE-2024-42152, CVE-2024-41049, CVE-2024-42237, CVE-2024-41095,\nCVE-2024-42280, CVE-2024-42153, CVE-2024-42115, CVE-2024-42130,\nCVE-2024-41064, CVE-2024-42077, CVE-2024-41067, CVE-2024-42137,\nCVE-2024-41019, CVE-2024-42240, CVE-2024-41093, CVE-2024-41048,\nCVE-2024-42063, CVE-2024-42113, CVE-2024-42145, CVE-2024-42073,\nCVE-2024-43858, CVE-2024-42088, CVE-2024-41069, CVE-2024-41068,\nCVE-2024-42138, CVE-2024-41065, CVE-2024-42087, CVE-2024-42239,\nCVE-2024-42149, CVE-2024-41021, CVE-2024-42065, CVE-2024-39487,\nCVE-2024-41052, CVE-2024-42095, CVE-2024-42074, CVE-2024-42097,\nCVE-2024-41098, CVE-2024-41057, CVE-2024-41060, CVE-2024-42119,\nCVE-2024-42229, CVE-2024-43855, CVE-2024-41056, CVE-2024-41041,\nCVE-2024-42144, CVE-2024-41087, CVE-2024-41094)\n","status":"published","published":"2024-11-15T10:36:16Z","modified":"2026-10-26T22:34:10.328493163Z","updated_at":"2026-11-02T16:58:18.876384Z"},{"id":"USN-7089-7","title":"linux-lowlatency, linux-lowlatency-hwe-6.8 vulnerabilities","description":"Chenyuan Yang discovered that the USB Gadget subsystem in the Linux\nkernel did not properly check for the device to be enabled before\nwriting. A local attacker could possibly use this to cause a denial of\nservice. (CVE-2024-25741)\n\nSeveral security issues were discovered in the Linux kernel.\nAn attacker could possibly use these to compromise the system.\nThis update corrects flaws in the following subsystems:\n  - ARM32 architecture;\n  - MIPS architecture;\n  - PA-RISC architecture;\n  - PowerPC architecture;\n  - RISC-V architecture;\n  - S390 architecture;\n  - x86 architecture;\n  - Cryptographic API;\n  - Serial ATA and Parallel ATA drivers;\n  - Null block device driver;\n  - Bluetooth drivers;\n  - Cdrom driver;\n  - Clock framework and drivers;\n  - Hardware crypto device drivers;\n  - CXL (Compute Express Link) drivers;\n  - Cirrus firmware drivers;\n  - GPIO subsystem;\n  - GPU drivers;\n  - I2C subsystem;\n  - IIO subsystem;\n  - InfiniBand drivers;\n  - ISDN/mISDN subsystem;\n  - LED subsystem;\n  - Multiple devices driver;\n  - Media drivers;\n  - Fastrpc Driver;\n  - Network drivers;\n  - Microsoft Azure Network Adapter (MANA) driver;\n  - Near Field Communication (NFC) drivers;\n  - NVME drivers;\n  - NVMEM (Non Volatile Memory) drivers;\n  - PCI subsystem;\n  - Pin controllers subsystem;\n  - x86 platform drivers;\n  - S/390 drivers;\n  - SCSI drivers;\n  - Thermal drivers;\n  - TTY drivers;\n  - UFS subsystem;\n  - USB DSL drivers;\n  - USB core drivers;\n  - DesignWare USB3 driver;\n  - USB Gadget drivers;\n  - USB Serial drivers;\n  - VFIO drivers;\n  - VHOST drivers;\n  - File systems infrastructure;\n  - BTRFS file system;\n  - GFS2 file system;\n  - JFFS2 file system;\n  - JFS file system;\n  - Network file systems library;\n  - Network file system client;\n  - NILFS2 file system;\n  - NTFS3 file system;\n  - SMB network file system;\n  - Memory management;\n  - Netfilter;\n  - Tracing infrastructure;\n  - io_uring subsystem;\n  - BPF subsystem;\n  - Core kernel;\n  - Bluetooth subsystem;\n  - CAN network layer;\n  - Ceph Core library;\n  - Networking core;\n  - IPv4 networking;\n  - IPv6 networking;\n  - IUCV driver;\n  - MAC80211 subsystem;\n  - Network traffic control;\n  - Sun RPC protocol;\n  - Wireless networking;\n  - AMD SoC Alsa drivers;\n  - SoC Audio for Freescale CPUs drivers;\n  - MediaTek ASoC drivers;\n  - SoC audio core drivers;\n  - SOF drivers;\n  - Sound sequencer drivers;\n(CVE-2024-42104, CVE-2024-42084, CVE-2024-42252, CVE-2024-41096,\nCVE-2024-42237, CVE-2024-42140, CVE-2024-42150, CVE-2024-41031,\nCVE-2024-41059, CVE-2024-41062, CVE-2024-41051, CVE-2024-41028,\nCVE-2024-41090, CVE-2024-41092, CVE-2024-43855, CVE-2024-41021,\nCVE-2024-42229, CVE-2024-41056, CVE-2024-41048, CVE-2024-41036,\nCVE-2024-42094, CVE-2024-41089, CVE-2024-41068, CVE-2024-41039,\nCVE-2024-41095, CVE-2024-41069, CVE-2024-42234, CVE-2024-42136,\nCVE-2024-41025, CVE-2024-42157, CVE-2024-42248, CVE-2024-42087,\nCVE-2024-41041, CVE-2024-42230, CVE-2024-42151, CVE-2024-42130,\nCVE-2024-42244, CVE-2024-41079, CVE-2024-42253, CVE-2024-42092,\nCVE-2024-41022, CVE-2024-42137, CVE-2024-42132, CVE-2024-42108,\nCVE-2024-42155, CVE-2024-42127, CVE-2024-41060, CVE-2024-42074,\nCVE-2024-41081, CVE-2024-42066, CVE-2024-42098, CVE-2024-42082,\nCVE-2024-42093, CVE-2024-42245, CVE-2024-41072, CVE-2024-41052,\nCVE-2024-42161, CVE-2024-42096, CVE-2024-42115, CVE-2024-41074,\nCVE-2024-42120, CVE-2024-41046, CVE-2024-42239, CVE-2024-41063,\nCVE-2024-42090, CVE-2024-41023, CVE-2024-42069, CVE-2024-41087,\nCVE-2024-42158, CVE-2024-41067, CVE-2024-41084, CVE-2024-41077,\nCVE-2024-42240, CVE-2024-42145, CVE-2024-42102, CVE-2024-41020,\nCVE-2024-42231, CVE-2024-41053, CVE-2024-42131, CVE-2024-42089,\nCVE-2024-41083, CVE-2024-42247, CVE-2024-42105, CVE-2024-41044,\nCVE-2024-42128, CVE-2024-42271, CVE-2024-41037, CVE-2024-42114,\nCVE-2024-42106, CVE-2024-41076, CVE-2024-42088, CVE-2024-41057,\nCVE-2024-41091, CVE-2024-42152, CVE-2024-41070, CVE-2024-41035,\nCVE-2024-41050, CVE-2024-39487, CVE-2024-42113, CVE-2024-42250,\nCVE-2024-41047, CVE-2024-42149, CVE-2024-42079, CVE-2024-42091,\nCVE-2024-42227, CVE-2024-42095, CVE-2024-42109, CVE-2024-41033,\nCVE-2023-52888, CVE-2024-41061, CVE-2024-42223, CVE-2024-42235,\nCVE-2024-41086, CVE-2024-42133, CVE-2024-41082, CVE-2024-41071,\nCVE-2024-41007, CVE-2023-52887, CVE-2024-39486, CVE-2024-41075,\nCVE-2024-42101, CVE-2024-42077, CVE-2024-41042, CVE-2024-42225,\nCVE-2024-42126, CVE-2024-41094, CVE-2024-41085, CVE-2024-41019,\nCVE-2024-41058, CVE-2024-41066, CVE-2024-42156, CVE-2024-42119,\nCVE-2024-41032, CVE-2024-41088, CVE-2024-42100, CVE-2024-42142,\nCVE-2024-41054, CVE-2024-42103, CVE-2024-42124, CVE-2024-41034,\nCVE-2024-42251, CVE-2024-42153, CVE-2024-41045, CVE-2024-42086,\nCVE-2024-42243, CVE-2024-41055, CVE-2024-41078, CVE-2024-42117,\nCVE-2024-41030, CVE-2024-42068, CVE-2024-42110, CVE-2024-42147,\nCVE-2024-42121, CVE-2024-41080, CVE-2024-41027, CVE-2024-43858,\nCVE-2024-42085, CVE-2024-42111, CVE-2024-42238, CVE-2024-41018,\nCVE-2024-42138, CVE-2024-41038, CVE-2024-42070, CVE-2024-42141,\nCVE-2024-41098, CVE-2024-42118, CVE-2024-41073, CVE-2024-42144,\nCVE-2024-42280, CVE-2024-41049, CVE-2024-42076, CVE-2024-41065,\nCVE-2024-42063, CVE-2024-41064, CVE-2024-41017, CVE-2024-42112,\nCVE-2024-42064, CVE-2024-42135, CVE-2024-42146, CVE-2024-41010,\nCVE-2024-41097, CVE-2024-41012, CVE-2024-42097, CVE-2024-42067,\nCVE-2024-42236, CVE-2024-42080, CVE-2024-42241, CVE-2024-42065,\nCVE-2024-42232, CVE-2024-42246, CVE-2024-41093, CVE-2024-41015,\nCVE-2024-42129, CVE-2024-42073, CVE-2024-41029)\n","status":"published","published":"2024-11-19T22:35:31Z","modified":"2026-10-26T22:34:04.239512543Z","updated_at":"2026-11-02T16:58:18.876384Z"},{"id":"USN-7090-1","title":"linux-azure-6.8 vulnerabilities","description":"\nChenyuan Yang discovered that the USB Gadget subsystem in the Linux\nkernel did not properly check for the device to be enabled before\nwriting. A local attacker could possibly use this to cause a denial of\nservice. (CVE-2024-25741)\n\nSeveral security issues were discovered in the Linux kernel.\nAn attacker could possibly use these to compromise the system.\nThis update corrects flaws in the following subsystems:\n  - ARM32 architecture;\n  - MIPS architecture;\n  - PA-RISC architecture;\n  - PowerPC architecture;\n  - RISC-V architecture;\n  - S390 architecture;\n  - x86 architecture;\n  - Cryptographic API;\n  - Serial ATA and Parallel ATA drivers;\n  - Null block device driver;\n  - Bluetooth drivers;\n  - Cdrom driver;\n  - Clock framework and drivers;\n  - Hardware crypto device drivers;\n  - CXL (Compute Express Link) drivers;\n  - Cirrus firmware drivers;\n  - GPIO subsystem;\n  - GPU drivers;\n  - I2C subsystem;\n  - IIO subsystem;\n  - InfiniBand drivers;\n  - ISDN/mISDN subsystem;\n  - LED subsystem;\n  - Multiple devices driver;\n  - Media drivers;\n  - Fastrpc Driver;\n  - Network drivers;\n  - Microsoft Azure Network Adapter (MANA) driver;\n  - Near Field Communication (NFC) drivers;\n  - NVME drivers;\n  - NVMEM (Non Volatile Memory) drivers;\n  - PCI subsystem;\n  - Pin controllers subsystem;\n  - x86 platform drivers;\n  - S/390 drivers;\n  - SCSI drivers;\n  - Thermal drivers;\n  - TTY drivers;\n  - UFS subsystem;\n  - USB DSL drivers;\n  - USB core drivers;\n  - DesignWare USB3 driver;\n  - USB Gadget drivers;\n  - USB Serial drivers;\n  - VFIO drivers;\n  - VHOST drivers;\n  - File systems infrastructure;\n  - BTRFS file system;\n  - GFS2 file system;\n  - JFFS2 file system;\n  - JFS file system;\n  - Network file systems library;\n  - Network file system client;\n  - NILFS2 file system;\n  - NTFS3 file system;\n  - SMB network file system;\n  - Memory management;\n  - Netfilter;\n  - Tracing infrastructure;\n  - io_uring subsystem;\n  - BPF subsystem;\n  - Core kernel;\n  - Bluetooth subsystem;\n  - CAN network layer;\n  - Ceph Core library;\n  - Networking core;\n  - IPv4 networking;\n  - IPv6 networking;\n  - IUCV driver;\n  - MAC80211 subsystem;\n  - Network traffic control;\n  - Sun RPC protocol;\n  - Wireless networking;\n  - AMD SoC Alsa drivers;\n  - SoC Audio for Freescale CPUs drivers;\n  - MediaTek ASoC drivers;\n  - SoC audio core drivers;\n  - SOF drivers;\n  - Sound sequencer drivers;\n(CVE-2024-42064, CVE-2024-43858, CVE-2024-42251, CVE-2024-42113,\nCVE-2024-41020, CVE-2024-41093, CVE-2024-45016, CVE-2024-42150,\nCVE-2024-42069, CVE-2024-42157, CVE-2024-42126, CVE-2024-42144,\nCVE-2024-42093, CVE-2024-41035, CVE-2024-41032, CVE-2024-41077,\nCVE-2024-42097, CVE-2024-41071, CVE-2024-42227, CVE-2024-42253,\nCVE-2024-42237, CVE-2024-41060, CVE-2024-42080, CVE-2024-42068,\nCVE-2024-41058, CVE-2024-42140, CVE-2024-42231, CVE-2024-42127,\nCVE-2024-42243, CVE-2023-52887, CVE-2024-39486, CVE-2024-41063,\nCVE-2024-42128, CVE-2024-42074, CVE-2024-41028, CVE-2024-42110,\nCVE-2024-45001, CVE-2024-41090, CVE-2024-41084, CVE-2024-41088,\nCVE-2024-42118, CVE-2024-41094, CVE-2024-41091, CVE-2024-41007,\nCVE-2024-42280, CVE-2024-41044, CVE-2024-41012, CVE-2024-42063,\nCVE-2024-41078, CVE-2024-42082, CVE-2024-41055, CVE-2024-41031,\nCVE-2024-42142, CVE-2024-41083, CVE-2024-42145, CVE-2024-41039,\nCVE-2024-41019, CVE-2024-42149, CVE-2024-42248, CVE-2024-42111,\nCVE-2024-41074, CVE-2024-42096, CVE-2024-42100, CVE-2024-41010,\nCVE-2024-43855, CVE-2024-42136, CVE-2024-41054, CVE-2024-41053,\nCVE-2024-41061, CVE-2024-42104, CVE-2024-41025, CVE-2024-42129,\nCVE-2024-41086, CVE-2024-42133, CVE-2024-42115, CVE-2024-42158,\nCVE-2024-42091, CVE-2024-42088, CVE-2024-42161, CVE-2024-42236,\nCVE-2024-41065, CVE-2024-41062, CVE-2024-42153, CVE-2024-41030,\nCVE-2024-41079, CVE-2023-52888, CVE-2024-42223, CVE-2024-42119,\nCVE-2024-42238, CVE-2024-41052, CVE-2024-41064, CVE-2024-42138,\nCVE-2024-41081, CVE-2024-41034, CVE-2024-42147, CVE-2024-41095,\nCVE-2024-42132, CVE-2024-42137, CVE-2024-42106, CVE-2024-41041,\nCVE-2024-41073, CVE-2024-41033, CVE-2024-41075, CVE-2024-42112,\nCVE-2024-41070, CVE-2024-42234, CVE-2024-41027, CVE-2024-42105,\nCVE-2024-41089, CVE-2024-41098, CVE-2024-42152, CVE-2024-42101,\nCVE-2024-41050, CVE-2024-41069, CVE-2024-42120, CVE-2024-42130,\nCVE-2024-42084, CVE-2024-41066, CVE-2024-42108, CVE-2024-42087,\nCVE-2024-41067, CVE-2024-41023, CVE-2024-41046, CVE-2024-42079,\nCVE-2024-42065, CVE-2024-42098, CVE-2024-42070, CVE-2024-41076,\nCVE-2024-41082, CVE-2024-41096, CVE-2024-42235, CVE-2024-42085,\nCVE-2024-42246, CVE-2024-41049, CVE-2024-42076, CVE-2024-41048,\nCVE-2024-41038, CVE-2024-42241, CVE-2024-41092, CVE-2024-42114,\nCVE-2024-41036, CVE-2024-41047, CVE-2024-41029, CVE-2024-42092,\nCVE-2024-41068, CVE-2024-42067, CVE-2024-42094, CVE-2024-42245,\nCVE-2024-41051, CVE-2024-42250, CVE-2024-42151, CVE-2024-41059,\nCVE-2024-41056, CVE-2024-42095, CVE-2024-42131, CVE-2024-42271,\nCVE-2024-42066, CVE-2024-42240, CVE-2024-41017, CVE-2024-42141,\nCVE-2024-41072, CVE-2024-42229, CVE-2024-42239, CVE-2024-42073,\nCVE-2024-42124, CVE-2024-41080, CVE-2024-42146, CVE-2024-41018,\nCVE-2024-41021, CVE-2024-39487, CVE-2024-42086, CVE-2024-42109,\nCVE-2024-41045, CVE-2024-41037, CVE-2024-41097, CVE-2024-42225,\nCVE-2024-42102, CVE-2024-42117, CVE-2024-42077, CVE-2024-42230,\nCVE-2024-41087, CVE-2024-42089, CVE-2024-42252, CVE-2024-42247,\nCVE-2024-41057, CVE-2024-42121, CVE-2024-42232, CVE-2024-42090,\nCVE-2024-41042, CVE-2024-42244, CVE-2024-42156, CVE-2024-42135,\nCVE-2024-42155, CVE-2024-42103, CVE-2024-41015, CVE-2024-41022,\nCVE-2024-41085)\n","status":"published","published":"2024-11-01T13:48:18Z","modified":"2026-10-29T20:02:33.244524175Z","updated_at":"2026-11-02T16:58:18.876384Z"},{"id":"USN-7095-1","title":"linux-nvidia, linux-nvidia-6.8, linux-nvidia-lowlatency vulnerabilities","description":"\nChenyuan Yang discovered that the USB Gadget subsystem in the Linux\nkernel did not properly check for the device to be enabled before\nwriting. A local attacker could possibly use this to cause a denial of\nservice. (CVE-2024-25741)\n\nSeveral security issues were discovered in the Linux kernel.\nAn attacker could possibly use these to compromise the system.\nThis update corrects flaws in the following subsystems:\n  - ARM32 architecture;\n  - MIPS architecture;\n  - PA-RISC architecture;\n  - PowerPC architecture;\n  - RISC-V architecture;\n  - S390 architecture;\n  - x86 architecture;\n  - Cryptographic API;\n  - Serial ATA and Parallel ATA drivers;\n  - Null block device driver;\n  - Bluetooth drivers;\n  - Cdrom driver;\n  - Clock framework and drivers;\n  - Hardware crypto device drivers;\n  - CXL (Compute Express Link) drivers;\n  - Cirrus firmware drivers;\n  - GPIO subsystem;\n  - GPU drivers;\n  - I2C subsystem;\n  - IIO subsystem;\n  - InfiniBand drivers;\n  - ISDN/mISDN subsystem;\n  - LED subsystem;\n  - Multiple devices driver;\n  - Media drivers;\n  - Fastrpc Driver;\n  - Network drivers;\n  - Microsoft Azure Network Adapter (MANA) driver;\n  - Near Field Communication (NFC) drivers;\n  - NVME drivers;\n  - NVMEM (Non Volatile Memory) drivers;\n  - PCI subsystem;\n  - Pin controllers subsystem;\n  - x86 platform drivers;\n  - S/390 drivers;\n  - SCSI drivers;\n  - Thermal drivers;\n  - TTY drivers;\n  - UFS subsystem;\n  - USB DSL drivers;\n  - USB core drivers;\n  - DesignWare USB3 driver;\n  - USB Gadget drivers;\n  - USB Serial drivers;\n  - VFIO drivers;\n  - VHOST drivers;\n  - File systems infrastructure;\n  - BTRFS file system;\n  - GFS2 file system;\n  - JFFS2 file system;\n  - JFS file system;\n  - Network file systems library;\n  - Network file system client;\n  - NILFS2 file system;\n  - NTFS3 file system;\n  - SMB network file system;\n  - Memory management;\n  - Netfilter;\n  - Tracing infrastructure;\n  - io_uring subsystem;\n  - BPF subsystem;\n  - Core kernel;\n  - Bluetooth subsystem;\n  - CAN network layer;\n  - Ceph Core library;\n  - Networking core;\n  - IPv4 networking;\n  - IPv6 networking;\n  - IUCV driver;\n  - MAC80211 subsystem;\n  - Network traffic control;\n  - Sun RPC protocol;\n  - Wireless networking;\n  - AMD SoC Alsa drivers;\n  - SoC Audio for Freescale CPUs drivers;\n  - MediaTek ASoC drivers;\n  - SoC audio core drivers;\n  - SOF drivers;\n  - Sound sequencer drivers;\n(CVE-2024-42271, CVE-2024-42068, CVE-2024-42086, CVE-2024-42132,\nCVE-2024-42074, CVE-2024-41017, CVE-2024-42090, CVE-2024-42280,\nCVE-2024-41030, CVE-2024-41037, CVE-2024-42248, CVE-2024-42084,\nCVE-2024-41057, CVE-2024-42252, CVE-2024-41055, CVE-2024-42158,\nCVE-2024-42097, CVE-2024-42101, CVE-2024-42095, CVE-2024-41084,\nCVE-2024-41051, CVE-2024-41032, CVE-2024-41046, CVE-2024-42231,\nCVE-2024-42133, CVE-2024-42089, CVE-2024-41062, CVE-2024-41033,\nCVE-2024-41012, CVE-2024-41077, CVE-2024-41064, CVE-2024-41082,\nCVE-2024-41090, CVE-2024-42065, CVE-2024-41096, CVE-2024-42119,\nCVE-2024-41054, CVE-2024-42064, CVE-2024-42253, CVE-2024-42237,\nCVE-2024-42120, CVE-2024-41066, CVE-2024-41083, CVE-2024-42129,\nCVE-2024-41085, CVE-2024-41058, CVE-2024-42146, CVE-2024-42156,\nCVE-2024-42076, CVE-2024-42149, CVE-2024-42069, CVE-2024-41039,\nCVE-2024-42110, CVE-2024-42150, CVE-2024-41015, CVE-2024-39486,\nCVE-2024-42144, CVE-2024-42131, CVE-2024-42087, CVE-2024-42091,\nCVE-2024-42236, CVE-2024-42088, CVE-2024-42112, CVE-2024-42142,\nCVE-2024-42082, CVE-2024-42111, CVE-2024-41028, CVE-2024-45001,\nCVE-2024-42077, CVE-2024-42102, CVE-2024-42239, CVE-2024-42140,\nCVE-2024-41091, CVE-2024-41050, CVE-2024-41034, CVE-2024-43858,\nCVE-2024-42145, CVE-2024-42227, CVE-2024-41029, CVE-2024-42230,\nCVE-2024-42096, CVE-2024-42238, CVE-2024-41027, CVE-2024-42063,\nCVE-2024-41023, CVE-2024-41041, CVE-2024-41038, CVE-2024-41073,\nCVE-2024-41067, CVE-2024-41025, CVE-2024-42152, CVE-2024-42247,\nCVE-2024-41065, CVE-2024-42121, CVE-2024-42157, CVE-2024-42080,\nCVE-2024-41076, CVE-2024-41059, CVE-2024-42108, CVE-2024-42251,\nCVE-2024-42093, CVE-2024-42130, CVE-2024-42126, CVE-2024-42079,\nCVE-2024-42246, CVE-2024-41081, CVE-2024-42092, CVE-2024-43855,\nCVE-2024-42235, CVE-2024-42118, CVE-2024-42067, CVE-2024-41047,\nCVE-2024-42155, CVE-2024-41010, CVE-2024-41061, CVE-2024-41007,\nCVE-2024-42245, CVE-2024-42106, CVE-2024-42066, CVE-2024-41078,\nCVE-2024-42113, CVE-2024-41087, CVE-2024-41092, CVE-2024-42234,\nCVE-2024-42124, CVE-2024-42100, CVE-2024-42128, CVE-2024-41072,\nCVE-2024-41022, CVE-2024-41049, CVE-2024-42229, CVE-2024-42225,\nCVE-2024-41052, CVE-2024-42151, CVE-2024-41094, CVE-2024-41098,\nCVE-2024-41035, CVE-2024-41042, CVE-2024-42114, CVE-2024-42250,\nCVE-2024-41095, CVE-2024-42138, CVE-2024-42241, CVE-2024-42103,\nCVE-2024-42094, CVE-2024-41045, CVE-2024-41075, CVE-2024-42073,\nCVE-2024-42153, CVE-2024-41048, CVE-2024-42085, CVE-2024-41074,\nCVE-2024-42244, CVE-2024-41018, CVE-2024-41079, CVE-2024-42127,\nCVE-2023-52887, CVE-2023-52888, CVE-2024-41071, CVE-2024-41020,\nCVE-2024-41036, CVE-2024-42117, CVE-2024-41068, CVE-2024-41056,\nCVE-2024-39487, CVE-2024-42243, CVE-2024-41019, CVE-2024-41070,\nCVE-2024-41044, CVE-2024-41060, CVE-2024-41088, CVE-2024-41021,\nCVE-2024-41053, CVE-2024-42137, CVE-2024-41086, CVE-2024-42104,\nCVE-2024-42109, CVE-2024-42105, CVE-2024-42136, CVE-2024-41080,\nCVE-2024-42098, CVE-2024-41093, CVE-2024-41063, CVE-2024-42161,\nCVE-2024-42147, CVE-2024-42223, CVE-2024-41097, CVE-2024-41069,\nCVE-2024-42240, CVE-2024-42135, CVE-2024-42070, CVE-2024-41089,\nCVE-2024-42141, CVE-2024-42115, CVE-2024-41031, CVE-2024-42232)\n","status":"published","published":"2024-11-07T09:49:52Z","modified":"2026-10-29T20:02:37.125807872Z","updated_at":"2026-11-02T16:58:18.876384Z"},{"id":"USN-7156-1","title":"linux-gkeop vulnerabilities","description":"\nChenyuan Yang discovered that the USB Gadget subsystem in the Linux kernel\ndid not properly check for the device to be enabled before writing. A local\nattacker could possibly use this to cause a denial of service.\n(CVE-2024-25741)\n\nSeveral security issues were discovered in the Linux kernel.\nAn attacker could possibly use these to compromise the system.\nThis update corrects flaws in the following subsystems:\n  - ARM32 architecture;\n  - ARM64 architecture;\n  - MIPS architecture;\n  - PA-RISC architecture;\n  - PowerPC architecture;\n  - RISC-V architecture;\n  - S390 architecture;\n  - User-Mode Linux (UML);\n  - x86 architecture;\n  - Block layer subsystem;\n  - Cryptographic API;\n  - Android drivers;\n  - Serial ATA and Parallel ATA drivers;\n  - ATM drivers;\n  - Drivers core;\n  - Null block device driver;\n  - Ublk userspace block driver;\n  - Bluetooth drivers;\n  - Cdrom driver;\n  - Character device driver;\n  - Clock framework and drivers;\n  - Hardware crypto device drivers;\n  - CXL (Compute Express Link) drivers;\n  - Buffer Sharing and Synchronization framework;\n  - DMA engine subsystem;\n  - Cirrus firmware drivers;\n  - Qualcomm firmware drivers;\n  - GPIO subsystem;\n  - GPU drivers;\n  - HID subsystem;\n  - Hardware monitoring drivers;\n  - I2C subsystem;\n  - I3C subsystem;\n  - IIO subsystem;\n  - InfiniBand drivers;\n  - Input Device core drivers;\n  - Input Device (Miscellaneous) drivers;\n  - IOMMU subsystem;\n  - IRQ chip drivers;\n  - ISDN/mISDN subsystem;\n  - LED subsystem;\n  - Mailbox framework;\n  - Multiple devices driver;\n  - Media drivers;\n  - Fastrpc Driver;\n  - VMware VMCI Driver;\n  - MMC subsystem;\n  - Ethernet bonding driver;\n  - Network drivers;\n  - Mellanox network drivers;\n  - Microsoft Azure Network Adapter (MANA) driver;\n  - Near Field Communication (NFC) drivers;\n  - NVME drivers;\n  - NVMEM (Non Volatile Memory) drivers;\n  - Device tree and open firmware driver;\n  - Parport drivers;\n  - PCI subsystem;\n  - Pin controllers subsystem;\n  - x86 platform drivers;\n  - Power supply drivers;\n  - Remote Processor subsystem;\n  - S/390 drivers;\n  - SCSI subsystem;\n  - QCOM SoC drivers;\n  - SPI subsystem;\n  - Direct Digital Synthesis drivers;\n  - Thermal drivers;\n  - Thunderbolt and USB4 drivers;\n  - TTY drivers;\n  - UFS subsystem;\n  - Userspace I/O drivers;\n  - USB DSL drivers;\n  - USB core drivers;\n  - DesignWare USB3 driver;\n  - USB Gadget drivers;\n  - USB Host Controller drivers;\n  - USB Serial drivers;\n  - USB Type-C Connector System Software Interface driver;\n  - USB over IP driver;\n  - VFIO drivers;\n  - Virtio Host (VHOST) subsystem;\n  - Framebuffer layer;\n  - Xen hypervisor drivers;\n  - File systems infrastructure;\n  - BTRFS file system;\n  - Ext4 file system;\n  - F2FS file system;\n  - GFS2 file system;\n  - JFFS2 file system;\n  - JFS file system;\n  - Network file systems library;\n  - Network file system (NFS) client;\n  - Network file system (NFS) server daemon;\n  - NILFS2 file system;\n  - File system notification infrastructure;\n  - NTFS3 file system;\n  - Proc file system;\n  - SMB network file system;\n  - Tracing file system;\n  - Bitmap API;\n  - BPF subsystem;\n  - Syscall compatibility layer;\n  - Memory Management;\n  - Memory management;\n  - Objagg library;\n  - Perf events;\n  - Syscall interfaces;\n  - Virtio network driver;\n  - VMware vSockets driver;\n  - KCM (Kernel Connection Multiplexor) sockets driver;\n  - Netfilter;\n  - Tracing infrastructure;\n  - io_uring subsystem;\n  - Control group (cgroup);\n  - DMA mapping infrastructure;\n  - Locking primitives;\n  - Padata parallel execution mechanism;\n  - Scheduler infrastructure;\n  - Closures library;\n  - Radix Tree data structure library;\n  - Kernel userspace event delivery library;\n  - KUnit for arithmetic overflow checks;\n  - Bluetooth subsystem;\n  - Ethernet bridge;\n  - CAN network layer;\n  - Ceph Core library;\n  - Networking core;\n  - Ethtool driver;\n  - IPv4 networking;\n  - IPv6 networking;\n  - IUCV driver;\n  - MAC80211 subsystem;\n  - Multipath TCP;\n  - Network traffic control;\n  - SCTP protocol;\n  - Sun RPC protocol;\n  - TIPC protocol;\n  - Wireless networking;\n  - AppArmor security module;\n  - Landlock security;\n  - SELinux security module;\n  - Simplified Mandatory Access Control Kernel framework;\n  - FireWire sound drivers;\n  - AMD SoC Alsa drivers;\n  - Texas InstrumentS Audio (ASoC/HDA) drivers;\n  - SoC Audio for Freescale CPUs drivers;\n  - Intel ASoC drivers;\n  - MediaTek ASoC drivers;\n  - Amlogic Meson SoC drivers;\n  - SoC audio core drivers;\n  - SOF drivers;\n  - Sound sequencer drivers;\n  - USB sound devices;\n  - Real-Time Linux Analysis tools;\n(CVE-2024-43911, CVE-2024-46762, CVE-2024-46794, CVE-2024-43843,\nCVE-2024-42229, CVE-2024-43888, CVE-2024-44978, CVE-2024-46693,\nCVE-2024-46695, CVE-2024-42290, CVE-2024-42067, CVE-2024-45012,\nCVE-2024-42316, CVE-2024-47665, CVE-2024-41052, CVE-2024-42074,\nCVE-2024-41058, CVE-2024-44975, CVE-2024-46709, CVE-2024-46871,\nCVE-2024-42090, CVE-2024-42296, CVE-2024-42096, CVE-2024-42146,\nCVE-2024-46855, CVE-2024-39487, CVE-2024-43825, CVE-2024-42066,\nCVE-2024-42126, CVE-2024-41022, CVE-2024-41025, CVE-2023-52888,\nCVE-2024-46702, CVE-2024-42269, CVE-2024-41082, CVE-2024-42284,\nCVE-2024-42227, CVE-2024-41017, CVE-2024-42250, CVE-2024-46778,\nCVE-2024-47661, CVE-2024-46727, CVE-2024-46845, CVE-2024-44953,\nCVE-2024-47659, CVE-2024-42137, CVE-2024-42245, CVE-2024-41096,\nCVE-2024-46829, CVE-2024-41053, CVE-2024-46782, CVE-2024-44972,\nCVE-2024-41095, CVE-2024-42239, CVE-2024-42127, CVE-2024-42292,\nCVE-2024-46752, CVE-2024-46679, CVE-2024-41076, CVE-2024-46784,\nCVE-2024-46786, CVE-2024-46678, CVE-2024-44957, CVE-2024-46755,\nCVE-2024-47660, CVE-2024-41067, CVE-2024-46838, CVE-2024-43879,\nCVE-2024-45007, CVE-2024-45025, CVE-2024-45001, CVE-2024-41009,\nCVE-2024-41051, CVE-2024-46836, CVE-2024-49984, CVE-2024-45028,\nCVE-2024-43871, CVE-2024-46783, CVE-2024-42272, CVE-2024-42087,\nCVE-2024-46785, CVE-2024-42276, CVE-2024-47658, CVE-2024-46761,\nCVE-2024-46715, CVE-2024-46676, CVE-2024-43824, CVE-2024-42100,\nCVE-2024-46745, CVE-2024-41084, CVE-2024-41086, CVE-2024-45015,\nCVE-2024-46797, CVE-2024-42160, CVE-2024-46706, CVE-2024-46803,\nCVE-2024-46708, CVE-2024-47669, CVE-2024-45009, CVE-2024-41021,\nCVE-2024-42159, CVE-2024-42321, CVE-2024-46868, CVE-2024-41078,\nCVE-2024-42303, CVE-2024-45027, CVE-2024-42309, CVE-2024-43849,\nCVE-2024-43907, CVE-2024-43899, CVE-2024-43823, CVE-2024-42232,\nCVE-2024-44937, CVE-2024-41046, CVE-2024-42237, CVE-2024-42063,\nCVE-2024-42065, CVE-2024-42154, CVE-2024-42259, CVE-2024-46698,\nCVE-2024-46741, CVE-2024-45020, CVE-2024-42151, CVE-2024-41073,\nCVE-2024-46719, CVE-2024-42295, CVE-2024-46859, CVE-2024-41035,\nCVE-2024-46751, CVE-2024-47667, CVE-2024-46728, CVE-2024-46824,\nCVE-2024-42121, CVE-2024-46776, CVE-2024-46768, CVE-2024-43908,\nCVE-2024-43900, CVE-2024-46707, CVE-2024-44934, CVE-2024-41062,\nCVE-2024-42304, CVE-2024-42312, CVE-2024-42157, CVE-2024-41092,\nCVE-2024-41041, CVE-2024-43832, CVE-2024-41039, CVE-2024-44962,\nCVE-2024-46858, CVE-2024-43856, CVE-2024-41060, CVE-2024-45010,\nCVE-2024-41044, CVE-2024-44942, CVE-2024-42307, CVE-2024-44984,\nCVE-2024-41075, CVE-2024-43817, CVE-2024-46791, CVE-2024-46853,\nCVE-2024-42301, CVE-2024-44993, CVE-2024-41094, CVE-2024-27022,\nCVE-2024-41088, CVE-2024-43883, CVE-2024-41087, CVE-2024-46780,\nCVE-2024-42070, CVE-2024-44965, CVE-2024-46823, CVE-2024-46737,\nCVE-2024-44982, CVE-2024-46697, CVE-2024-45021, CVE-2024-44987,\nCVE-2024-41072, CVE-2024-41063, CVE-2024-46757, CVE-2024-46831,\nCVE-2024-44966, CVE-2024-42322, CVE-2024-42231, CVE-2024-46717,\nCVE-2024-41065, CVE-2024-44969, CVE-2023-52887, CVE-2024-42105,\nCVE-2024-44971, CVE-2024-46798, CVE-2024-42262, CVE-2024-44938,\nCVE-2024-42088, CVE-2024-44970, CVE-2024-43876, CVE-2024-46800,\nCVE-2024-42086, CVE-2024-43826, CVE-2024-46729, CVE-2024-46747,\nCVE-2024-46691, CVE-2024-46723, CVE-2024-41018, CVE-2024-42258,\nCVE-2024-41081, CVE-2024-41049, CVE-2024-43837, CVE-2024-45008,\nCVE-2024-41047, CVE-2024-41019, CVE-2024-42152, CVE-2024-41090,\nCVE-2024-46716, CVE-2024-42104, CVE-2024-46804, CVE-2024-43852,\nCVE-2024-42129, CVE-2024-46870, CVE-2024-41093, CVE-2024-45011,\nCVE-2024-41064, CVE-2024-46722, CVE-2024-42286, CVE-2024-45026,\nCVE-2024-46818, CVE-2024-42281, CVE-2024-43854, CVE-2024-41037,\nCVE-2024-44946, CVE-2024-41012, CVE-2024-41098, CVE-2024-42263,\nCVE-2024-42095, CVE-2024-46756, CVE-2024-43913, CVE-2024-46822,\nCVE-2024-44944, CVE-2024-42156, CVE-2024-42073, CVE-2024-42093,\nCVE-2024-44931, CVE-2024-42223, CVE-2024-42264, CVE-2024-42278,\nCVE-2024-46759, CVE-2024-46826, CVE-2024-43828, CVE-2024-42318,\nCVE-2024-42240, CVE-2024-45000, CVE-2024-43909, CVE-2024-46792,\nCVE-2024-42109, CVE-2024-43867, CVE-2024-42130, CVE-2024-42244,\nCVE-2024-44977, CVE-2024-46774, CVE-2024-41030, CVE-2024-42310,\nCVE-2024-42138, CVE-2024-42317, CVE-2024-42224, CVE-2024-46694,\nCVE-2024-46815, CVE-2024-46677, CVE-2024-46763, CVE-2024-46860,\nCVE-2024-46767, CVE-2024-42111, CVE-2024-41020, CVE-2024-46726,\nCVE-2024-42117, CVE-2024-43831, CVE-2024-42285, CVE-2024-46842,\nCVE-2024-43857, CVE-2024-41031, CVE-2024-43834, CVE-2024-42135,\nCVE-2024-42241, CVE-2024-46846, CVE-2024-44988, CVE-2024-43892,\nCVE-2024-44991, CVE-2024-46806, CVE-2024-41015, CVE-2024-43906,\nCVE-2024-42238, CVE-2024-46779, CVE-2024-41010, CVE-2024-41068,\nCVE-2024-46730, CVE-2024-46827, CVE-2024-42120, CVE-2024-41059,\nCVE-2024-46850, CVE-2023-52889, CVE-2024-45017, CVE-2024-45003,\nCVE-2024-46844, CVE-2024-46816, CVE-2024-46811, CVE-2024-41023,\nCVE-2024-44948, CVE-2024-46753, CVE-2024-45002, CVE-2024-42251,\nCVE-2024-46713, CVE-2024-42273, CVE-2024-46733, CVE-2024-46739,\nCVE-2024-42108, CVE-2024-41085, CVE-2024-41033, CVE-2024-42298,\nCVE-2024-46835, CVE-2024-39472, CVE-2024-47663, CVE-2024-43859,\nCVE-2024-43820, CVE-2024-42118, CVE-2024-41036, CVE-2024-47683,\nCVE-2024-42161, CVE-2024-42235, CVE-2024-43861, CVE-2024-43863,\nCVE-2024-47668, CVE-2024-46685, CVE-2024-43864, CVE-2024-46749,\nCVE-2024-44983, CVE-2024-46841, CVE-2024-42082, CVE-2024-43818,\nCVE-2024-41071, CVE-2024-45006, CVE-2024-42080, CVE-2024-46825,\nCVE-2024-46687, CVE-2024-44959, CVE-2024-43835, CVE-2024-43891,\nCVE-2024-46851, CVE-2024-42248, CVE-2024-42103, CVE-2024-42079,\nCVE-2024-42068, CVE-2024-47664, CVE-2024-46854, CVE-2024-44973,\nCVE-2024-42077, CVE-2024-46821, CVE-2024-43886, CVE-2024-41089,\nCVE-2024-43850, CVE-2024-44995, CVE-2024-46809, CVE-2024-42084,\nCVE-2024-46758, CVE-2024-47662, CVE-2024-43839, CVE-2024-46738,\nCVE-2024-41034, CVE-2024-42228, CVE-2024-42147, CVE-2024-43855,\nCVE-2024-41032, CVE-2024-46819, CVE-2024-44989, CVE-2024-42265,\nCVE-2024-42110, CVE-2024-42155, CVE-2024-45005, CVE-2024-45016,\nCVE-2024-42141, CVE-2024-43821, CVE-2024-42299, CVE-2024-44950,\nCVE-2024-42279, CVE-2024-44943, CVE-2024-43904, CVE-2024-42268,\nCVE-2024-42089, CVE-2024-46807, CVE-2024-44996, CVE-2024-42069,\nCVE-2024-46672, CVE-2024-44940, CVE-2024-42270, CVE-2024-46735,\nCVE-2024-42319, CVE-2024-46754, CVE-2024-46861, CVE-2024-42277,\nCVE-2024-41054, CVE-2024-42131, CVE-2024-41056, CVE-2024-44963,\nCVE-2024-42267, CVE-2024-42283, CVE-2024-42320, CVE-2024-46740,\nCVE-2024-46787, CVE-2024-43895, CVE-2024-43881, CVE-2024-44961,\nCVE-2024-43910, CVE-2024-43875, CVE-2024-42289, CVE-2024-43853,\nCVE-2024-42315, CVE-2024-43884, CVE-2024-46867, CVE-2024-43912,\nCVE-2024-41007, CVE-2024-46743, CVE-2024-46675, CVE-2024-43877,\nCVE-2024-39486, CVE-2024-41050, CVE-2024-43858, CVE-2024-45018,\nCVE-2024-46744, CVE-2024-46750, CVE-2024-46840, CVE-2024-42150,\nCVE-2024-41028, CVE-2024-42091, CVE-2024-43894, CVE-2024-43869,\nCVE-2024-42132, CVE-2024-46777, CVE-2024-42106, CVE-2024-46848,\nCVE-2024-41038, CVE-2024-46711, CVE-2024-43833, CVE-2024-46710,\nCVE-2024-46812, CVE-2024-42311, CVE-2024-46701, CVE-2024-46683,\nCVE-2024-45029, CVE-2024-46830, CVE-2024-46857, CVE-2024-44979,\nCVE-2024-44999, CVE-2024-44985, CVE-2024-46773, CVE-2024-45022,\nCVE-2024-46772, CVE-2024-44960, CVE-2024-42243, CVE-2024-42158,\nCVE-2024-43819, CVE-2024-45030, CVE-2024-42085, CVE-2024-42274,\nCVE-2024-44986, CVE-2024-41048, CVE-2024-42098, CVE-2024-46680,\nCVE-2023-52918, CVE-2024-46673, CVE-2024-46834, CVE-2024-42288,\nCVE-2024-44998, CVE-2024-42113, CVE-2024-42094, CVE-2024-42225,\nCVE-2024-42112, CVE-2024-42153, CVE-2024-43880, CVE-2024-43905,\nCVE-2024-43902, CVE-2024-46681, CVE-2024-42236, CVE-2024-42294,\nCVE-2024-46793, CVE-2024-43882, CVE-2024-44947, CVE-2024-46849,\nCVE-2024-44954, CVE-2024-46852, CVE-2024-41070, CVE-2024-41069,\nCVE-2024-46864, CVE-2024-46703, CVE-2024-43829, CVE-2024-46802,\nCVE-2024-42101, CVE-2024-44990, CVE-2024-43830, CVE-2024-41029,\nCVE-2024-43866, CVE-2024-43889, CVE-2024-42230, CVE-2024-46692,\nCVE-2024-42133, CVE-2024-45013, CVE-2024-42076, CVE-2024-46810,\nCVE-2024-42128, CVE-2024-46718, CVE-2024-46814, CVE-2024-43841,\nCVE-2024-43873, CVE-2024-42092, CVE-2024-41074, CVE-2024-41083,\nCVE-2024-46731, CVE-2024-43842, CVE-2024-41077, CVE-2024-46720,\nCVE-2024-46795, CVE-2024-46813, CVE-2024-46805, CVE-2024-42142,\nCVE-2024-42291, CVE-2024-43846, CVE-2024-41057, CVE-2024-43870,\nCVE-2024-44980, CVE-2024-46866, CVE-2024-43827, CVE-2024-43840,\nCVE-2024-42280, CVE-2024-42261, CVE-2024-42246, CVE-2024-42115,\nCVE-2024-46686, CVE-2024-43860, CVE-2024-46808, CVE-2024-42149,\nCVE-2024-46828, CVE-2024-44935, CVE-2024-43847, CVE-2024-44967,\nCVE-2024-46817, CVE-2024-46721, CVE-2024-42305, CVE-2024-46766,\nCVE-2024-43914, CVE-2024-46760, CVE-2024-41061, CVE-2024-41091,\nCVE-2024-43890, CVE-2024-42314, CVE-2024-42064, CVE-2024-42302,\nCVE-2024-43887, CVE-2024-46832, CVE-2024-46765, CVE-2024-46770,\nCVE-2024-41080, CVE-2024-42253, CVE-2024-44941, CVE-2024-42306,\nCVE-2024-41027, CVE-2024-46689, CVE-2024-46781, CVE-2024-42247,\nCVE-2024-41066, CVE-2024-42287, CVE-2024-41097, CVE-2024-44939,\nCVE-2024-45019, CVE-2024-47674, CVE-2024-46705, CVE-2024-42119,\nCVE-2024-46725, CVE-2024-46746, CVE-2024-46732, CVE-2024-41042,\nCVE-2024-44958, CVE-2024-42114, CVE-2024-43893, CVE-2024-47666,\nCVE-2024-46843, CVE-2024-42252, CVE-2024-42102, CVE-2024-42136,\nCVE-2024-41045, CVE-2024-42260, CVE-2024-46771, CVE-2024-42124,\nCVE-2024-42297, CVE-2024-42271, CVE-2024-43845, CVE-2024-46775,\nCVE-2024-41079, CVE-2024-43868, CVE-2024-42140, CVE-2024-42313,\nCVE-2024-42145, CVE-2024-46724, CVE-2024-46788, CVE-2024-42234,\nCVE-2024-42144, CVE-2024-44974, CVE-2024-42097, CVE-2024-46714,\nCVE-2024-41055, CVE-2024-44956)\n","status":"published","published":"2024-12-12T17:47:44Z","modified":"2026-10-29T20:02:38.448595714Z","updated_at":"2026-11-02T16:58:18.876384Z"}]}}