{"id":"CVE-2021-47382","aliases":["DEBIAN-CVE-2021-47382","EUVD-2021-34387","GHSA-q77h-85v7-m3mw","OESA-2024-1962","OESA-2024-1964","OESA-2024-2258","ROOT-OS-DEBIAN-11-CVE-2021-47382","SUSE-SU-2024:1979-1","SUSE-SU-2024:1983-1","SUSE-SU-2024:2008-1","SUSE-SU-2024:2010-1","SUSE-SU-2024:2011-1","SUSE-SU-2024:2019-1","SUSE-SU-2024:2183-1","SUSE-SU-2024:2184-1","SUSE-SU-2024:2185-1","SUSE-SU-2024:2189-1","SUSE-SU-2024:2190-1","UBUNTU-CVE-2021-47382"],"status":"published","title":"s390/qeth: fix deadlock during failing recovery","description":"In the Linux kernel, the following vulnerability has been resolved:\n\ns390/qeth: fix deadlock during failing recovery\n\nCommit 0b9902c1fcc5 (\"s390/qeth: fix deadlock during recovery\") removed\ntaking discipline_mutex inside qeth_do_reset(), fixing potential\ndeadlocks. An error path was missed though, that still takes\ndiscipline_mutex and thus has the original deadlock potential.\n\nIntermittent deadlocks were seen when a qeth channel path is configured\noffline, causing a race between qeth_do_reset and ccwgroup_remove.\nCall qeth_set_offline() directly in the qeth_do_reset() error case and\nthen a new variant of ccwgroup_set_offline(), without taking\ndiscipline_mutex.","severity":{"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","from":"nvd"},"epss":{"day":"2026-11-12","score":0.00152,"percentile":0.04448,"model":"v2026.06.15"},"facts":{"in_kev":false,"known_exploited":false,"public_exploit":false,"fix_available":true},"cwes":["CWE-362","CWE-667"],"published":"2024-05-21T15:03:43Z","modified":"2026-10-23T18:05:06Z","fixes":[{"ecosystem":"Debian:12","package":"linux","fixed_in":["5.14.12-1"],"sources":["osv"]},{"ecosystem":"Debian:13","package":"linux","fixed_in":["5.14.12-1"],"sources":["osv"]},{"ecosystem":"Debian:14","package":"linux","fixed_in":["5.14.12-1"],"sources":["osv"]},{"ecosystem":"Root:Debian:11","package":"linux","fixed_in":["5.10.262-1.aikido.113","5.10.262-1.aikido.114"],"sources":["osv"]},{"ecosystem":"Root:Debian:11","package":"rootio-linux","fixed_in":["5.10.262-1.aikido.113","5.10.262-1.aikido.114"],"sources":["osv"]}],"affected":[{"source":"osv","ecosystem":"Debian:12","package":"linux","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.12-1"}]}]},{"source":"osv","ecosystem":"Debian:13","package":"linux","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.12-1"}]}]},{"source":"osv","ecosystem":"Debian:14","package":"linux","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.12-1"}]}]},{"source":"osv","ecosystem":"openEuler:22.03-LTS-SP3","package":"kernel","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.10.0-222.0.0.125.oe2203sp3"}]}],"bundled":75},{"source":"osv","ecosystem":"openEuler:22.03-LTS-SP1","package":"kernel","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.10.0-136.88.0.169.oe2203sp1"}]}],"bundled":70},{"source":"osv","ecosystem":"openEuler:22.03-LTS-SP4","package":"kernel","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.10.0-232.0.0.131.oe2203sp4"}]}],"bundled":72},{"source":"osv","ecosystem":"Root:Debian:11","package":"linux","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.10.262-1.aikido.113"},{"fixed":"5.10.262-1.aikido.114"}]}]},{"source":"osv","ecosystem":"Root:Debian:11","package":"rootio-linux","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.10.262-1.aikido.113"},{"fixed":"5.10.262-1.aikido.114"}]}]},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server 12 SP5","package":"kernel-azure","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.12.14-16.188.1"}]}],"bundled":180},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server 12 SP5","package":"kernel-source-azure","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.12.14-16.188.1"}]}],"bundled":180},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server 12 SP5","package":"kernel-syms-azure","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.12.14-16.188.1"}]}],"bundled":180},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server for SAP Applications 12 SP5","package":"kernel-azure","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.12.14-16.188.1"}]}],"bundled":180},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server for SAP Applications 12 SP5","package":"kernel-source-azure","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.12.14-16.188.1"}]}],"bundled":180},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server for SAP Applications 12 SP5","package":"kernel-syms-azure","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.12.14-16.188.1"}]}],"bundled":180},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Real Time 12 SP5","package":"kernel-rt","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.12.14-10.188.1"}]}],"bundled":199},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Real Time 12 SP5","package":"kernel-rt_debug","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.12.14-10.188.1"}]}],"bundled":199},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Real Time 12 SP5","package":"kernel-source-rt","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.12.14-10.188.1"}]}],"bundled":199},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Real Time 12 SP5","package":"kernel-syms-rt","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.12.14-10.188.1"}]}],"bundled":199},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Micro 5.5","package":"kernel-rt","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.21-150500.13.58.1"}]}],"bundled":561},{"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.58.1"}]}],"bundled":561},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Live Patching 15 SP5","package":"kernel-livepatch-SLE15-SP5-RT_Update_16","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1-150500.11.3.1"}]}],"bundled":561},{"source":"osv","ecosystem":"SUSE:Real Time Module 15 SP5","package":"kernel-rt","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.21-150500.13.58.1"}]}],"bundled":561},{"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.58.1"}]}],"bundled":561},{"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.58.1"}]}],"bundled":561},{"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.58.1"}]}],"bundled":561},{"source":"osv","ecosystem":"openSUSE:Leap 15.5","package":"kernel-rt","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.21-150500.13.58.1"}]}],"bundled":561},{"source":"osv","ecosystem":"openSUSE:Leap 15.5","package":"kernel-rt_debug","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.21-150500.13.58.1"}]}],"bundled":561},{"source":"osv","ecosystem":"openSUSE:Leap 15.5","package":"kernel-source-rt","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.21-150500.13.58.1"}]}],"bundled":561},{"source":"osv","ecosystem":"openSUSE:Leap 15.5","package":"kernel-syms-rt","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.21-150500.13.58.1"}]}],"bundled":561},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Micro 5.1","package":"kernel-rt","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.3.18-150300.172.1"}]}],"bundled":186},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Micro 5.1","package":"kernel-source-rt","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.3.18-150300.172.1"}]}],"bundled":186},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Micro 5.2","package":"kernel-rt","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.3.18-150300.172.1"}]}],"bundled":186},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Micro 5.2","package":"kernel-source-rt","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.3.18-150300.172.1"}]}],"bundled":186},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Micro 5.3","package":"kernel-rt","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.21-150400.15.82.1"}]}],"bundled":308},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Micro 5.3","package":"kernel-source-rt","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.21-150400.15.82.1"}]}],"bundled":308},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Micro 5.4","package":"kernel-rt","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.21-150400.15.82.1"}]}],"bundled":308},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Micro 5.4","package":"kernel-source-rt","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.21-150400.15.82.1"}]}],"bundled":308},{"source":"osv","ecosystem":"openSUSE:Leap Micro 5.3","package":"kernel-rt","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.21-150400.15.82.1"}]}],"bundled":308},{"source":"osv","ecosystem":"openSUSE:Leap Micro 5.4","package":"kernel-rt","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.21-150400.15.82.1"}]}],"bundled":308},{"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.57.1"}]}],"bundled":541},{"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.57.1"}]}],"bundled":541},{"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.57.1"}]}],"bundled":541},{"source":"osv","ecosystem":"openSUSE:Leap 15.5","package":"kernel-azure","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.21-150500.33.57.1"}]}],"bundled":541},{"source":"osv","ecosystem":"openSUSE:Leap 15.5","package":"kernel-source-azure","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.21-150500.33.57.1"}]}],"bundled":541},{"source":"osv","ecosystem":"openSUSE:Leap 15.5","package":"kernel-syms-azure","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.21-150500.33.57.1"}]}],"bundled":541},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Live Patching 15 SP2","package":"kernel-default","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.3.18-150200.24.194.1"}]}],"bundled":130},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Live Patching 15 SP2","package":"kernel-livepatch-SLE15-SP2_Update_49","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1-150200.5.3.1"}]}],"bundled":130},{"source":"osv","ecosystem":"SUSE:Linux Enterprise High Availability Extension 15 SP2","package":"kernel-default","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.3.18-150200.24.194.1"}]}],"bundled":130},{"source":"osv","ecosystem":"SUSE:Linux Enterprise High Performance Computing 15 SP2-LTSS","package":"kernel-default","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.3.18-150200.24.194.1"}]}],"bundled":130},{"source":"osv","ecosystem":"SUSE:Linux Enterprise High Performance Computing 15 SP2-LTSS","package":"kernel-default-base","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.3.18-150200.24.194.1.150200.9.99.1"}]}],"bundled":130},{"source":"osv","ecosystem":"SUSE:Linux Enterprise High Performance Computing 15 SP2-LTSS","package":"kernel-docs","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.3.18-150200.24.194.1"}]}],"bundled":130},{"source":"osv","ecosystem":"SUSE:Linux Enterprise High Performance Computing 15 SP2-LTSS","package":"kernel-obs-build","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.3.18-150200.24.194.1"}]}],"bundled":130},{"source":"osv","ecosystem":"SUSE:Linux Enterprise High Performance Computing 15 SP2-LTSS","package":"kernel-preempt","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.3.18-150200.24.194.1"}]}],"bundled":130},{"source":"osv","ecosystem":"SUSE:Linux Enterprise High Performance Computing 15 SP2-LTSS","package":"kernel-source","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.3.18-150200.24.194.1"}]}],"bundled":130},{"source":"osv","ecosystem":"SUSE:Linux Enterprise High Performance Computing 15 SP2-LTSS","package":"kernel-syms","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.3.18-150200.24.194.1"}]}],"bundled":130},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server 15 SP2-LTSS","package":"kernel-default","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.3.18-150200.24.194.1"}]}],"bundled":130},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server 15 SP2-LTSS","package":"kernel-default-base","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.3.18-150200.24.194.1.150200.9.99.1"}]}],"bundled":130},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server 15 SP2-LTSS","package":"kernel-docs","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.3.18-150200.24.194.1"}]}],"bundled":130},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server 15 SP2-LTSS","package":"kernel-obs-build","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.3.18-150200.24.194.1"}]}],"bundled":130},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server 15 SP2-LTSS","package":"kernel-preempt","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.3.18-150200.24.194.1"}]}],"bundled":130},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server 15 SP2-LTSS","package":"kernel-source","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.3.18-150200.24.194.1"}]}],"bundled":130},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server 15 SP2-LTSS","package":"kernel-syms","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.3.18-150200.24.194.1"}]}],"bundled":130},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server for SAP Applications 15 SP2","package":"kernel-default","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.3.18-150200.24.194.1"}]}],"bundled":130},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server for SAP Applications 15 SP2","package":"kernel-default-base","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.3.18-150200.24.194.1.150200.9.99.1"}]}],"bundled":130},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server for SAP Applications 15 SP2","package":"kernel-docs","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.3.18-150200.24.194.1"}]}],"bundled":130},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server for SAP Applications 15 SP2","package":"kernel-obs-build","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.3.18-150200.24.194.1"}]}],"bundled":130},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server for SAP Applications 15 SP2","package":"kernel-preempt","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.3.18-150200.24.194.1"}]}],"bundled":130},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server for SAP Applications 15 SP2","package":"kernel-source","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.3.18-150200.24.194.1"}]}],"bundled":130},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server for SAP Applications 15 SP2","package":"kernel-syms","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.3.18-150200.24.194.1"}]}],"bundled":130},{"source":"osv","ecosystem":"SUSE:Linux Enterprise High Availability Extension 12 SP5","package":"kernel-default","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.12.14-122.219.1"}]}],"bundled":198},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Live Patching 12 SP5","package":"kernel-default","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.12.14-122.219.1"}]}],"bundled":198},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Live Patching 12 SP5","package":"kgraft-patch-SLE12-SP5_Update_57","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1-8.3.1"}]}],"bundled":198},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Software Development Kit 12 SP5","package":"kernel-docs","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.12.14-122.219.1"}]}],"bundled":198},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Software Development Kit 12 SP5","package":"kernel-obs-build","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.12.14-122.219.1"}]}],"bundled":198},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server 12 SP5","package":"kernel-default","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.12.14-122.219.1"}]}],"bundled":198},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server 12 SP5","package":"kernel-source","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.12.14-122.219.1"}]}],"bundled":198},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server 12 SP5","package":"kernel-syms","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.12.14-122.219.1"}]}],"bundled":198},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server for SAP Applications 12 SP5","package":"kernel-default","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.12.14-122.219.1"}]}],"bundled":198},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server for SAP Applications 12 SP5","package":"kernel-source","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.12.14-122.219.1"}]}],"bundled":198},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server for SAP Applications 12 SP5","package":"kernel-syms","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.12.14-122.219.1"}]}],"bundled":198},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Workstation Extension 12 SP5","package":"kernel-default","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.12.14-122.219.1"}]}],"bundled":198},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Live Patching 15 SP3","package":"kernel-default","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.3.18-150300.59.164.1"}]}],"bundled":186},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Live Patching 15 SP3","package":"kernel-livepatch-SLE15-SP3_Update_45","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1-150300.7.3.1"}]}],"bundled":186},{"source":"osv","ecosystem":"SUSE:Linux Enterprise High Availability Extension 15 SP3","package":"kernel-default","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.3.18-150300.59.164.1"}]}],"bundled":186},{"source":"osv","ecosystem":"SUSE:Linux Enterprise High Performance Computing 15 SP3-LTSS","package":"kernel-64kb","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.3.18-150300.59.164.1"}]}],"bundled":186},{"source":"osv","ecosystem":"SUSE:Linux Enterprise High Performance Computing 15 SP3-LTSS","package":"kernel-default","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.3.18-150300.59.164.1"}]}],"bundled":186},{"source":"osv","ecosystem":"SUSE:Linux Enterprise High Performance Computing 15 SP3-LTSS","package":"kernel-default-base","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.3.18-150300.59.164.1.150300.18.96.1"}]}],"bundled":186},{"source":"osv","ecosystem":"SUSE:Linux Enterprise High Performance Computing 15 SP3-LTSS","package":"kernel-docs","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.3.18-150300.59.164.1"}]}],"bundled":186},{"source":"osv","ecosystem":"SUSE:Linux Enterprise High Performance Computing 15 SP3-LTSS","package":"kernel-obs-build","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.3.18-150300.59.164.1"}]}],"bundled":186},{"source":"osv","ecosystem":"SUSE:Linux Enterprise High Performance Computing 15 SP3-LTSS","package":"kernel-preempt","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.3.18-150300.59.164.1"}]}],"bundled":186},{"source":"osv","ecosystem":"SUSE:Linux Enterprise High Performance Computing 15 SP3-LTSS","package":"kernel-source","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.3.18-150300.59.164.1"}]}],"bundled":186},{"source":"osv","ecosystem":"SUSE:Linux Enterprise High Performance Computing 15 SP3-LTSS","package":"kernel-syms","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.3.18-150300.59.164.1"}]}],"bundled":186},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server 15 SP3-LTSS","package":"kernel-64kb","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.3.18-150300.59.164.1"}]}],"bundled":186},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server 15 SP3-LTSS","package":"kernel-default","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.3.18-150300.59.164.1"}]}],"bundled":186},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server 15 SP3-LTSS","package":"kernel-default-base","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.3.18-150300.59.164.1.150300.18.96.1"}]}],"bundled":186},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server 15 SP3-LTSS","package":"kernel-docs","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.3.18-150300.59.164.1"}]}],"bundled":186},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server 15 SP3-LTSS","package":"kernel-obs-build","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.3.18-150300.59.164.1"}]}],"bundled":186},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server 15 SP3-LTSS","package":"kernel-preempt","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.3.18-150300.59.164.1"}]}],"bundled":186},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server 15 SP3-LTSS","package":"kernel-source","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.3.18-150300.59.164.1"}]}],"bundled":186},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server 15 SP3-LTSS","package":"kernel-syms","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.3.18-150300.59.164.1"}]}],"bundled":186},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server 15 SP3-LTSS","package":"kernel-zfcpdump","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.3.18-150300.59.164.1"}]}],"bundled":186},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server for SAP Applications 15 SP3","package":"kernel-default","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.3.18-150300.59.164.1"}]}],"bundled":186},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server for SAP Applications 15 SP3","package":"kernel-default-base","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.3.18-150300.59.164.1.150300.18.96.1"}]}],"bundled":186},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server for SAP Applications 15 SP3","package":"kernel-docs","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.3.18-150300.59.164.1"}]}],"bundled":186},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server for SAP Applications 15 SP3","package":"kernel-obs-build","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.3.18-150300.59.164.1"}]}],"bundled":186},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server for SAP Applications 15 SP3","package":"kernel-preempt","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.3.18-150300.59.164.1"}]}],"bundled":186},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server for SAP Applications 15 SP3","package":"kernel-source","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.3.18-150300.59.164.1"}]}],"bundled":186},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server for SAP Applications 15 SP3","package":"kernel-syms","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.3.18-150300.59.164.1"}]}],"bundled":186},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Micro 5.1","package":"kernel-default","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.3.18-150300.59.164.1"}]}],"bundled":186},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Micro 5.1","package":"kernel-default-base","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.3.18-150300.59.164.1.150300.18.96.1"}]}],"bundled":186},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Micro 5.2","package":"kernel-default","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.3.18-150300.59.164.1"}]}],"bundled":186},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Micro 5.2","package":"kernel-default-base","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.3.18-150300.59.164.1.150300.18.96.1"}]}],"bundled":186},{"source":"osv","ecosystem":"SUSE:Enterprise Storage 7.1","package":"kernel-64kb","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.3.18-150300.59.164.1"}]}],"bundled":186},{"source":"osv","ecosystem":"SUSE:Enterprise Storage 7.1","package":"kernel-default","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.3.18-150300.59.164.1"}]}],"bundled":186},{"source":"osv","ecosystem":"SUSE:Enterprise Storage 7.1","package":"kernel-default-base","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.3.18-150300.59.164.1.150300.18.96.1"}]}],"bundled":186},{"source":"osv","ecosystem":"SUSE:Enterprise Storage 7.1","package":"kernel-docs","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.3.18-150300.59.164.1"}]}],"bundled":186},{"source":"osv","ecosystem":"SUSE:Enterprise Storage 7.1","package":"kernel-obs-build","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.3.18-150300.59.164.1"}]}],"bundled":186},{"source":"osv","ecosystem":"SUSE:Enterprise Storage 7.1","package":"kernel-preempt","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.3.18-150300.59.164.1"}]}],"bundled":186},{"source":"osv","ecosystem":"SUSE:Enterprise Storage 7.1","package":"kernel-source","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.3.18-150300.59.164.1"}]}],"bundled":186},{"source":"osv","ecosystem":"SUSE:Enterprise Storage 7.1","package":"kernel-syms","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.3.18-150300.59.164.1"}]}],"bundled":186},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Micro 5.3","package":"kernel-default","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.21-150400.24.122.2"}]}],"bundled":320},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Micro 5.3","package":"kernel-default-base","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.21-150400.24.122.2.150400.24.58.2"}]}],"bundled":320},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Micro 5.4","package":"kernel-default","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.21-150400.24.122.2"}]}],"bundled":320},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Micro 5.4","package":"kernel-default-base","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.21-150400.24.122.2.150400.24.58.2"}]}],"bundled":320},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Live Patching 15 SP4","package":"kernel-default","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.21-150400.24.122.2"}]}],"bundled":320},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Live Patching 15 SP4","package":"kernel-livepatch-SLE15-SP4_Update_27","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1-150400.9.3.2"}]}],"bundled":320},{"source":"osv","ecosystem":"SUSE:Linux Enterprise High Availability Extension 15 SP4","package":"kernel-default","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.21-150400.24.122.2"}]}],"bundled":320},{"source":"osv","ecosystem":"SUSE:Linux Enterprise High Performance Computing 15 SP4-ESPOS","package":"kernel-64kb","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.21-150400.24.122.2"}]}],"bundled":320},{"source":"osv","ecosystem":"SUSE:Linux Enterprise High Performance Computing 15 SP4-ESPOS","package":"kernel-default","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.21-150400.24.122.2"}]}],"bundled":320},{"source":"osv","ecosystem":"SUSE:Linux Enterprise High Performance Computing 15 SP4-ESPOS","package":"kernel-default-base","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.21-150400.24.122.2.150400.24.58.2"}]}],"bundled":320},{"source":"osv","ecosystem":"SUSE:Linux Enterprise High Performance Computing 15 SP4-ESPOS","package":"kernel-docs","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.21-150400.24.122.2"}]}],"bundled":320},{"source":"osv","ecosystem":"SUSE:Linux Enterprise High Performance Computing 15 SP4-ESPOS","package":"kernel-obs-build","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.21-150400.24.122.2"}]}],"bundled":320},{"source":"osv","ecosystem":"SUSE:Linux Enterprise High Performance Computing 15 SP4-ESPOS","package":"kernel-source","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.21-150400.24.122.1"}]}],"bundled":320},{"source":"osv","ecosystem":"SUSE:Linux Enterprise High Performance Computing 15 SP4-ESPOS","package":"kernel-syms","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.21-150400.24.122.1"}]}],"bundled":320},{"source":"osv","ecosystem":"SUSE:Linux Enterprise High Performance Computing 15 SP4-LTSS","package":"kernel-64kb","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.21-150400.24.122.2"}]}],"bundled":320},{"source":"osv","ecosystem":"SUSE:Linux Enterprise High Performance Computing 15 SP4-LTSS","package":"kernel-default","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.21-150400.24.122.2"}]}],"bundled":320},{"source":"osv","ecosystem":"SUSE:Linux Enterprise High Performance Computing 15 SP4-LTSS","package":"kernel-default-base","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.21-150400.24.122.2.150400.24.58.2"}]}],"bundled":320},{"source":"osv","ecosystem":"SUSE:Linux Enterprise High Performance Computing 15 SP4-LTSS","package":"kernel-docs","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.21-150400.24.122.2"}]}],"bundled":320},{"source":"osv","ecosystem":"SUSE:Linux Enterprise High Performance Computing 15 SP4-LTSS","package":"kernel-obs-build","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.21-150400.24.122.2"}]}],"bundled":320},{"source":"osv","ecosystem":"SUSE:Linux Enterprise High Performance Computing 15 SP4-LTSS","package":"kernel-source","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.21-150400.24.122.1"}]}],"bundled":320},{"source":"osv","ecosystem":"SUSE:Linux Enterprise High Performance Computing 15 SP4-LTSS","package":"kernel-syms","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.21-150400.24.122.1"}]}],"bundled":320},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server 15 SP4-LTSS","package":"kernel-64kb","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.21-150400.24.122.2"}]}],"bundled":320},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server 15 SP4-LTSS","package":"kernel-default","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.21-150400.24.122.2"}]}],"bundled":320},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server 15 SP4-LTSS","package":"kernel-default-base","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.21-150400.24.122.2.150400.24.58.2"}]}],"bundled":320},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server 15 SP4-LTSS","package":"kernel-docs","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.21-150400.24.122.2"}]}],"bundled":320},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server 15 SP4-LTSS","package":"kernel-obs-build","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.21-150400.24.122.2"}]}],"bundled":320},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server 15 SP4-LTSS","package":"kernel-source","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.21-150400.24.122.1"}]}],"bundled":320},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server 15 SP4-LTSS","package":"kernel-syms","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.21-150400.24.122.1"}]}],"bundled":320},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server 15 SP4-LTSS","package":"kernel-zfcpdump","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.21-150400.24.122.2"}]}],"bundled":320},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server for SAP Applications 15 SP4","package":"kernel-default","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.21-150400.24.122.2"}]}],"bundled":320},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server for SAP Applications 15 SP4","package":"kernel-default-base","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.21-150400.24.122.2.150400.24.58.2"}]}],"bundled":320},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server for SAP Applications 15 SP4","package":"kernel-docs","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.21-150400.24.122.2"}]}],"bundled":320},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server for SAP Applications 15 SP4","package":"kernel-obs-build","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.21-150400.24.122.2"}]}],"bundled":320},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server for SAP Applications 15 SP4","package":"kernel-source","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.21-150400.24.122.1"}]}],"bundled":320},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server for SAP Applications 15 SP4","package":"kernel-syms","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.21-150400.24.122.1"}]}],"bundled":320},{"source":"osv","ecosystem":"SUSE:Manager Proxy 4.3","package":"kernel-default","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.21-150400.24.122.2"}]}],"bundled":320},{"source":"osv","ecosystem":"SUSE:Manager Proxy 4.3","package":"kernel-default-base","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.21-150400.24.122.2.150400.24.58.2"}]}],"bundled":320},{"source":"osv","ecosystem":"SUSE:Manager Proxy 4.3","package":"kernel-source","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.21-150400.24.122.1"}]}],"bundled":320},{"source":"osv","ecosystem":"SUSE:Manager Proxy 4.3","package":"kernel-syms","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.21-150400.24.122.1"}]}],"bundled":320},{"source":"osv","ecosystem":"SUSE:Manager Server 4.3","package":"kernel-default","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.21-150400.24.122.2"}]}],"bundled":320},{"source":"osv","ecosystem":"SUSE:Manager Server 4.3","package":"kernel-default-base","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.21-150400.24.122.2.150400.24.58.2"}]}],"bundled":320},{"source":"osv","ecosystem":"SUSE:Manager Server 4.3","package":"kernel-source","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.21-150400.24.122.1"}]}],"bundled":320},{"source":"osv","ecosystem":"SUSE:Manager Server 4.3","package":"kernel-syms","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.21-150400.24.122.1"}]}],"bundled":320},{"source":"osv","ecosystem":"SUSE:Manager Server 4.3","package":"kernel-zfcpdump","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.21-150400.24.122.2"}]}],"bundled":320},{"source":"osv","ecosystem":"openSUSE:Leap Micro 5.3","package":"kernel-default","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.21-150400.24.122.2"}]}],"bundled":320},{"source":"osv","ecosystem":"openSUSE:Leap Micro 5.3","package":"kernel-default-base","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.21-150400.24.122.2.150400.24.58.2"}]}],"bundled":320},{"source":"osv","ecosystem":"openSUSE:Leap Micro 5.4","package":"kernel-default","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.21-150400.24.122.2"}]}],"bundled":320},{"source":"osv","ecosystem":"openSUSE:Leap Micro 5.4","package":"kernel-default-base","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.21-150400.24.122.2.150400.24.58.2"}]}],"bundled":320},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Micro 5.5","package":"kernel-default","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.21-150500.55.68.1"}]}],"bundled":557},{"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.68.1.150500.6.31.1"}]}],"bundled":557},{"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.68.1"}]}],"bundled":557},{"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.68.1"}]}],"bundled":557},{"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.68.1.150500.6.31.1"}]}],"bundled":557},{"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.68.1"}]}],"bundled":557},{"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.68.1"}]}],"bundled":557},{"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.68.1"}]}],"bundled":557},{"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.68.1"}]}],"bundled":557},{"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.68.1"}]}],"bundled":557},{"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.68.1"}]}],"bundled":557},{"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.68.1"}]}],"bundled":557},{"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.68.1"}]}],"bundled":557},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Live Patching 15 SP5","package":"kernel-livepatch-SLE15-SP5_Update_15","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1-150500.11.3.1"}]}],"bundled":557},{"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.68.1"}]}],"bundled":557},{"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.68.1"}]}],"bundled":557},{"source":"osv","ecosystem":"openSUSE:Leap 15.5","package":"dtb-aarch64","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.21-150500.55.68.1"}]}],"bundled":557},{"source":"osv","ecosystem":"openSUSE:Leap 15.5","package":"kernel-64kb","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.21-150500.55.68.1"}]}],"bundled":557},{"source":"osv","ecosystem":"openSUSE:Leap 15.5","package":"kernel-debug","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.21-150500.55.68.1"}]}],"bundled":557},{"source":"osv","ecosystem":"openSUSE:Leap 15.5","package":"kernel-default","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.21-150500.55.68.1"}]}],"bundled":557},{"source":"osv","ecosystem":"openSUSE:Leap 15.5","package":"kernel-default-base","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.21-150500.55.68.1.150500.6.31.1"}]}],"bundled":557},{"source":"osv","ecosystem":"openSUSE:Leap 15.5","package":"kernel-docs","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.21-150500.55.68.1"}]}],"bundled":557},{"source":"osv","ecosystem":"openSUSE:Leap 15.5","package":"kernel-kvmsmall","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.21-150500.55.68.1"}]}],"bundled":557},{"source":"osv","ecosystem":"openSUSE:Leap 15.5","package":"kernel-obs-build","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.21-150500.55.68.1"}]}],"bundled":557},{"source":"osv","ecosystem":"openSUSE:Leap 15.5","package":"kernel-obs-qa","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.21-150500.55.68.1"}]}],"bundled":557},{"source":"osv","ecosystem":"openSUSE:Leap 15.5","package":"kernel-source","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.21-150500.55.68.1"}]}],"bundled":557},{"source":"osv","ecosystem":"openSUSE:Leap 15.5","package":"kernel-syms","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.21-150500.55.68.1"}]}],"bundled":557},{"source":"osv","ecosystem":"openSUSE:Leap 15.5","package":"kernel-zfcpdump","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.21-150500.55.68.1"}]}],"bundled":557},{"source":"osv","ecosystem":"Ubuntu:16.04:LTS","package":"linux-hwe-edge","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["4.8.0-28.30~16.04.1","4.8.0-30.32~16.04.1","4.8.0-32.34~16.04.1","4.8.0-34.36~16.04.1","4.10.0-14.16~16.04.1","4.10.0-19.21~16.04.1","4.10.0-20.22~16.04.1","4.10.0-21.23~16.04.1","4.10.0-22.24~16.04.1","4.10.0-24.28~16.04.1","4.10.0-26.30~16.04.1","4.11.0-13.19~16.04.1","4.11.0-14.20~16.04.1","4.13.0-16.19~16.04.3","4.13.0-17.20~16.04.1","4.13.0-19.22~16.04.1","4.13.0-21.24~16.04.1","4.13.0-25.29~16.04.2","4.15.0-13.14~16.04.1","4.15.0-15.16~16.04.1","4.15.0-20.21~16.04.1","4.15.0-22.24~16.04.1","4.15.0-23.25~16.04.1"]},{"source":"osv","ecosystem":"Ubuntu:18.04:LTS","package":"linux-aws-5.0","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.0.0-1021.24~18.04.1","5.0.0-1022.25~18.04.1","5.0.0-1023.26~18.04.1","5.0.0-1024.27~18.04.1","5.0.0-1025.28","5.0.0-1027.30"]},{"source":"osv","ecosystem":"Ubuntu:18.04:LTS","package":"linux-aws-5.3","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.3.0-1016.17~18.04.1","5.3.0-1017.18~18.04.1","5.3.0-1019.21~18.04.1","5.3.0-1023.25~18.04.1","5.3.0-1028.30~18.04.1","5.3.0-1030.32~18.04.1","5.3.0-1032.34~18.04.2","5.3.0-1033.35","5.3.0-1034.36","5.3.0-1035.37"]},{"source":"osv","ecosystem":"Ubuntu:18.04:LTS","package":"linux-azure","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["4.15.0-1002.2","4.15.0-1003.3","4.15.0-1004.4","4.15.0-1008.8","4.15.0-1009.9","4.15.0-1012.12","4.15.0-1013.13","4.15.0-1014.14","4.15.0-1018.18","4.15.0-1019.19","4.15.0-1021.21","4.15.0-1022.23","4.15.0-1023.24","4.15.0-1025.26","4.15.0-1028.29","4.15.0-1030.31","4.15.0-1031.32","4.15.0-1032.33","4.15.0-1035.36","4.15.0-1036.38","4.15.0-1037.39","4.18.0-1011.11~18.04.1","4.18.0-1013.13~18.04.1","4.18.0-1014.14~18.04.1","4.18.0-1018.18~18.04.1","4.18.0-1019.19~18.04.1","4.18.0-1020.20~18.04.1","4.18.0-1023.24~18.04.1","4.18.0-1024.25~18.04.1","4.18.0-1025.27~18.04.1","5.0.0-1014.14~18.04.1","5.0.0-1016.17~18.04.1","5.0.0-1018.19~18.04.1","5.0.0-1020.21~18.04.1","5.0.0-1022.23~18.04.1","5.0.0-1023.24~18.04.1","5.0.0-1025.27~18.04.1","5.0.0-1027.29~18.04.1","5.0.0-1028.30~18.04.1","5.0.0-1029.31~18.04.1","5.0.0-1031.33","5.0.0-1032.34","5.0.0-1035.37","5.0.0-1036.38"]},{"source":"osv","ecosystem":"Ubuntu:18.04:LTS","package":"linux-azure-5.3","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.3.0-1007.8~18.04.1","5.3.0-1008.9~18.04.1","5.3.0-1009.10~18.04.1","5.3.0-1010.11~18.04.1","5.3.0-1012.13~18.04.1","5.3.0-1013.14~18.04.1","5.3.0-1016.17~18.04.1","5.3.0-1018.19~18.04.1","5.3.0-1019.20~18.04.1","5.3.0-1020.21~18.04.1","5.3.0-1022.23~18.04.1","5.3.0-1028.29~18.04.1","5.3.0-1031.32~18.04.1","5.3.0-1032.33~18.04.1","5.3.0-1034.35~18.04.1","5.3.0-1035.36"]},{"source":"osv","ecosystem":"Ubuntu:18.04:LTS","package":"linux-azure-edge","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["4.18.0-1006.6~18.04.1","4.18.0-1007.7~18.04.1","4.18.0-1008.8~18.04.1","5.0.0-1012.12~18.04.2"]},{"source":"osv","ecosystem":"Ubuntu:18.04:LTS","package":"linux-gcp","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["4.15.0-1001.1","4.15.0-1003.3","4.15.0-1005.5","4.15.0-1006.6","4.15.0-1008.8","4.15.0-1009.9","4.15.0-1010.10","4.15.0-1014.14","4.15.0-1015.15","4.15.0-1017.18","4.15.0-1018.19","4.15.0-1019.20","4.15.0-1021.22","4.15.0-1023.24","4.15.0-1024.25","4.15.0-1025.26","4.15.0-1026.27","4.15.0-1027.28","4.15.0-1028.29","4.15.0-1029.31","4.15.0-1030.32","4.15.0-1032.34","4.15.0-1033.35","4.15.0-1034.36","4.15.0-1036.38","4.15.0-1037.39","4.15.0-1040.42","4.15.0-1042.45","4.15.0-1044.70","5.0.0-1020.20~18.04.1","5.0.0-1021.21~18.04.1","5.0.0-1025.26~18.04.1","5.0.0-1026.27~18.04.1","5.0.0-1028.29~18.04.1","5.0.0-1029.30~18.04.1","5.0.0-1031.32","5.0.0-1033.34","5.0.0-1034.35"]},{"source":"osv","ecosystem":"Ubuntu:18.04:LTS","package":"linux-gcp-5.3","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.3.0-1008.9~18.04.1","5.3.0-1009.10~18.04.1","5.3.0-1010.11~18.04.1","5.3.0-1012.13~18.04.1","5.3.0-1014.15~18.04.1","5.3.0-1016.17~18.04.1","5.3.0-1017.18~18.04.1","5.3.0-1018.19~18.04.1","5.3.0-1020.22~18.04.1","5.3.0-1026.28~18.04.1","5.3.0-1029.31~18.04.1","5.3.0-1030.32~18.04.1","5.3.0-1032.34~18.04.1"]},{"source":"osv","ecosystem":"Ubuntu:18.04:LTS","package":"linux-gke-4.15","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["4.15.0-1030.32","4.15.0-1032.34","4.15.0-1033.35","4.15.0-1034.36","4.15.0-1036.38","4.15.0-1037.39","4.15.0-1040.42","4.15.0-1041.43","4.15.0-1042.44","4.15.0-1044.46","4.15.0-1045.48","4.15.0-1046.49","4.15.0-1048.51","4.15.0-1049.52","4.15.0-1050.53","4.15.0-1052.55","4.15.0-1055.58","4.15.0-1057.60","4.15.0-1058.61","4.15.0-1059.62","4.15.0-1063.66","4.15.0-1064.67","4.15.0-1066.69","4.15.0-1067.70","4.15.0-1069.72","4.15.0-1070.73","4.15.0-1072.76","4.15.0-1073.78","4.15.0-1074.79","4.15.0-1076.81","4.15.0-1077.82","4.15.0-1078.83","4.15.0-1079.84"]},{"source":"osv","ecosystem":"Ubuntu:18.04:LTS","package":"linux-gke-5.4","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.4.0-1025.25~18.04.1","5.4.0-1027.28~18.04.1","5.4.0-1029.31~18.04.1","5.4.0-1030.32~18.04.1","5.4.0-1032.34~18.04.1","5.4.0-1033.35~18.04.1","5.4.0-1035.37~18.04.1","5.4.0-1036.38~18.04.1","5.4.0-1037.39~18.04.1","5.4.0-1039.41~18.04.1","5.4.0-1040.42~18.04.1","5.4.0-1042.44~18.04.1","5.4.0-1043.45~18.04.1","5.4.0-1044.46~18.04.1","5.4.0-1046.48~18.04.1","5.4.0-1049.52~18.04.1","5.4.0-1051.54~18.04.1","5.4.0-1052.55~18.04.1","5.4.0-1053.56~18.04.1","5.4.0-1054.57~18.04.1","5.4.0-1055.58~18.04.1","5.4.0-1056.59~18.04.1","5.4.0-1057.60~18.04.1","5.4.0-1059.62~18.04.1","5.4.0-1061.64~18.04.1","5.4.0-1062.65~18.04.1","5.4.0-1063.66~18.04.1","5.4.0-1065.68~18.04.1","5.4.0-1066.69~18.04.1","5.4.0-1067.70~18.04.1","5.4.0-1068.71~18.04.1","5.4.0-1071.76~18.04.3","5.4.0-1072.77~18.04.1","5.4.0-1074.79~18.04.1","5.4.0-1076.82~18.04.1","5.4.0-1078.84~18.04.1","5.4.0-1080.86~18.04.1"]},{"source":"osv","ecosystem":"Ubuntu:18.04:LTS","package":"linux-gkeop-5.4","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.4.0-1001.1","5.4.0-1003.3","5.4.0-1004.5","5.4.0-1005.6","5.4.0-1007.8~18.04.1","5.4.0-1008.9~18.04.1","5.4.0-1009.10~18.04.1","5.4.0-1010.11~18.04.1","5.4.0-1011.12~18.04.2","5.4.0-1012.13~18.04.1","5.4.0-1013.14~18.04.1","5.4.0-1014.15~18.04.1","5.4.0-1015.16~18.04.1","5.4.0-1016.17~18.04.1","5.4.0-1018.19~18.04.1","5.4.0-1021.22~18.04.1","5.4.0-1022.23~18.04.1","5.4.0-1023.24~18.04.1","5.4.0-1024.25~18.04.1","5.4.0-1025.26~18.04.1","5.4.0-1026.27~18.04.1","5.4.0-1027.28~18.04.1","5.4.0-1029.30~18.04.2","5.4.0-1031.32~18.04.1","5.4.0-1032.33~18.04.1","5.4.0-1033.34~18.04.1","5.4.0-1034.35~18.04.1","5.4.0-1036.37~18.04.1","5.4.0-1037.38~18.04.1","5.4.0-1038.39~18.04.1","5.4.0-1039.40~18.04.1","5.4.0-1040.41~18.04.1","5.4.0-1043.44~18.04.1","5.4.0-1046.48~18.04.1","5.4.0-1048.51~18.04.1","5.4.0-1049.52~18.04.1","5.4.0-1051.54~18.04.1"]},{"source":"osv","ecosystem":"Ubuntu:18.04:LTS","package":"linux-hwe","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["4.18.0-13.14~18.04.1","4.18.0-14.15~18.04.1","4.18.0-15.16~18.04.1","4.18.0-16.17~18.04.1","4.18.0-17.18~18.04.1","4.18.0-18.19~18.04.1","4.18.0-20.21~18.04.1","4.18.0-21.22~18.04.1","4.18.0-22.23~18.04.1","4.18.0-24.25~18.04.1","4.18.0-25.26~18.04.1","5.0.0-23.24~18.04.1","5.0.0-25.26~18.04.1","5.0.0-27.28~18.04.1","5.0.0-29.31~18.04.1","5.0.0-31.33~18.04.1","5.0.0-32.34~18.04.2","5.0.0-35.38~18.04.1","5.0.0-36.39~18.04.1","5.0.0-37.40~18.04.1","5.3.0-26.28~18.04.1","5.3.0-28.30~18.04.1","5.3.0-40.32~18.04.1","5.3.0-42.34~18.04.1","5.3.0-45.37~18.04.1","5.3.0-46.38~18.04.1","5.3.0-51.44~18.04.2","5.3.0-53.47~18.04.1","5.3.0-59.53~18.04.1","5.3.0-61.55~18.04.1","5.3.0-62.56~18.04.1","5.3.0-64.58~18.04.1","5.3.0-65.59","5.3.0-66.60","5.3.0-67.61","5.3.0-68.63","5.3.0-69.65","5.3.0-70.66","5.3.0-72.68","5.3.0-73.69","5.3.0-74.70","5.3.0-75.71","5.3.0-76.72"]},{"source":"osv","ecosystem":"Ubuntu:18.04:LTS","package":"linux-hwe-edge","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.0.0-15.16~18.04.1","5.0.0-16.17~18.04.1","5.0.0-17.18~18.04.1","5.0.0-19.20~18.04.1","5.0.0-20.21~18.04.1","5.3.0-19.20~18.04.2","5.3.0-22.24~18.04.1","5.3.0-23.25~18.04.1","5.3.0-23.25~18.04.2","5.3.0-24.26~18.04.2"]},{"source":"osv","ecosystem":"Ubuntu:18.04:LTS","package":"linux-oem","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["4.15.0-1002.3","4.15.0-1004.5","4.15.0-1006.9","4.15.0-1008.11","4.15.0-1009.12","4.15.0-1012.15","4.15.0-1013.16","4.15.0-1015.18","4.15.0-1017.20","4.15.0-1018.21","4.15.0-1021.24","4.15.0-1024.29","4.15.0-1026.31","4.15.0-1028.33","4.15.0-1030.35","4.15.0-1033.38","4.15.0-1034.39","4.15.0-1035.40","4.15.0-1036.41","4.15.0-1038.43","4.15.0-1039.44","4.15.0-1043.48","4.15.0-1045.50","4.15.0-1050.57","4.15.0-1056.65","4.15.0-1057.66","4.15.0-1059.68","4.15.0-1063.72","4.15.0-1064.73","4.15.0-1065.75","4.15.0-1066.76","4.15.0-1067.77","4.15.0-1069.79","4.15.0-1073.83","4.15.0-1076.86","4.15.0-1079.89","4.15.0-1080.90","4.15.0-1081.91","4.15.0-1087.97","4.15.0-1090.100","4.15.0-1091.101","4.15.0-1093.103","4.15.0-1094.104","4.15.0-1096.106","4.15.0-1097.107","4.15.0-1099.109","4.15.0-1100.110","4.15.0-1101.112","4.15.0-1102.113","4.15.0-1103.114"]},{"source":"osv","ecosystem":"Ubuntu:18.04:LTS","package":"linux-oracle-5.0","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.0.0-1007.12~18.04.1","5.0.0-1008.13~18.04.1","5.0.0-1009.14~18.04.1","5.0.0-1010.15~18.04.1","5.0.0-1011.16","5.0.0-1013.18","5.0.0-1014.19"]},{"source":"osv","ecosystem":"Ubuntu:18.04:LTS","package":"linux-oracle-5.3","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.3.0-1011.12~18.04.1","5.3.0-1013.14~18.04.1","5.3.0-1014.15~18.04.1","5.3.0-1016.18~18.04.1","5.3.0-1018.20~18.04.1","5.3.0-1024.26~18.04.1","5.3.0-1027.29~18.04.1","5.3.0-1028.30~18.04.1","5.3.0-1030.32~18.04.1"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-aws-5.11","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.11.0-1009.9~20.04.2","5.11.0-1014.15~20.04.1","5.11.0-1016.17~20.04.1","5.11.0-1017.18~20.04.1","5.11.0-1019.20~20.04.1","5.11.0-1020.21~20.04.2","5.11.0-1021.22~20.04.2","5.11.0-1022.23~20.04.1","5.11.0-1023.24~20.04.1","5.11.0-1025.27~20.04.1","5.11.0-1027.30~20.04.1","5.11.0-1028.31~20.04.1"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-aws-5.13","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.13.0-1008.9~20.04.2","5.13.0-1011.12~20.04.1","5.13.0-1012.13~20.04.1","5.13.0-1014.15~20.04.1","5.13.0-1017.19~20.04.1","5.13.0-1019.21~20.04.1","5.13.0-1021.23~20.04.2","5.13.0-1022.24~20.04.1","5.13.0-1023.25~20.04.1","5.13.0-1025.27~20.04.1","5.13.0-1028.31~20.04.1","5.13.0-1029.32~20.04.1","5.13.0-1031.35~20.04.1"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-aws-5.8","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.8.0-1035.37~20.04.1","5.8.0-1038.40~20.04.1","5.8.0-1041.43~20.04.1","5.8.0-1042.44~20.04.1"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-azure-5.11","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.11.0-1007.7~20.04.2","5.11.0-1012.13~20.04.1","5.11.0-1013.14~20.04.1","5.11.0-1015.16~20.04.1","5.11.0-1017.18~20.04.1","5.11.0-1019.20~20.04.1","5.11.0-1020.21~20.04.1","5.11.0-1021.22~20.04.1","5.11.0-1022.23~20.04.1","5.11.0-1023.24~20.04.1","5.11.0-1025.27~20.04.1","5.11.0-1027.30~20.04.1","5.11.0-1028.31~20.04.2"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-azure-5.13","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.13.0-1009.10~20.04.2","5.13.0-1012.14~20.04.1","5.13.0-1013.15~20.04.1","5.13.0-1014.16~20.04.1","5.13.0-1017.19~20.04.1","5.13.0-1021.24~20.04.1","5.13.0-1022.26~20.04.1","5.13.0-1023.27~20.04.1","5.13.0-1025.29~20.04.1","5.13.0-1028.33~20.04.1","5.13.0-1029.34~20.04.1","5.13.0-1031.37~20.04.1"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-azure-5.8","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.8.0-1033.35~20.04.1","5.8.0-1036.38~20.04.1","5.8.0-1039.42~20.04.1","5.8.0-1040.43~20.04.1","5.8.0-1041.44~20.04.1","5.8.0-1042.45~20.04.1","5.8.0-1043.46~20.04.1"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-azure-fde","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.4.0-1063.66+cvm2.2","5.4.0-1063.66+cvm3.2","5.4.0-1064.67+cvm1.1","5.4.0-1065.68+cvm2.1","5.4.0-1067.70+cvm1.1","5.4.0-1068.71+cvm1.1","5.4.0-1069.72+cvm1.1","5.4.0-1070.73+cvm1.1","5.4.0-1072.75+cvm1.1","5.4.0-1073.76+cvm1.1","5.4.0-1074.77+cvm1.1","5.4.0-1076.79+cvm1.1","5.4.0-1078.81+cvm1.1","5.4.0-1080.83+cvm1.1","5.4.0-1083.87+cvm1.1","5.4.0-1085.90+cvm1.1","5.4.0-1085.90+cvm2.1","5.4.0-1086.91+cvm1.1","5.4.0-1089.94+cvm1.2","5.4.0-1090.95+cvm1.1","5.4.0-1091.96+cvm1.1","5.4.0-1092.97+cvm1.1","5.4.0-1095.101+cvm1.1","5.4.0-1098.104+cvm1.1","5.4.0-1100.106+cvm1.1","5.4.0-1103.109+cvm1.1"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-gcp-5.11","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.11.0-1009.10~20.04.1","5.11.0-1014.16~20.04.1","5.11.0-1017.19~20.04.1","5.11.0-1018.20~20.04.2","5.11.0-1020.22~20.04.1","5.11.0-1021.23~20.04.1","5.11.0-1022.24~20.04.1","5.11.0-1023.25~20.04.1","5.11.0-1024.26~20.04.1","5.11.0-1026.29~20.04.1","5.11.0-1028.32~20.04.1","5.11.0-1029.33~20.04.3"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-gcp-5.13","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.13.0-1008.9~20.04.3","5.13.0-1012.15~20.04.1","5.13.0-1013.16~20.04.1","5.13.0-1015.18~20.04.1","5.13.0-1019.23~20.04.1","5.13.0-1021.25~20.04.1","5.13.0-1023.28~20.04.1","5.13.0-1024.29~20.04.1","5.13.0-1025.30~20.04.1","5.13.0-1027.32~20.04.1","5.13.0-1030.36~20.04.1","5.13.0-1031.37~20.04.1","5.13.0-1033.40~20.04.1"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-gcp-5.8","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.8.0-1032.34~20.04.1","5.8.0-1035.37~20.04.1","5.8.0-1038.40~20.04.1","5.8.0-1039.41"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-gke","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.4.0-1033.35","5.4.0-1035.37","5.4.0-1036.38","5.4.0-1037.39","5.4.0-1039.41","5.4.0-1041.43","5.4.0-1042.44","5.4.0-1043.45","5.4.0-1044.46","5.4.0-1046.48","5.4.0-1049.52","5.4.0-1051.54","5.4.0-1052.55","5.4.0-1053.56","5.4.0-1054.57","5.4.0-1055.58","5.4.0-1056.59","5.4.0-1057.60","5.4.0-1059.62","5.4.0-1061.64","5.4.0-1062.65","5.4.0-1063.66","5.4.0-1065.68","5.4.0-1066.69","5.4.0-1067.70","5.4.0-1068.71","5.4.0-1071.76","5.4.0-1072.77","5.4.0-1074.79","5.4.0-1076.82","5.4.0-1078.84","5.4.0-1080.86","5.4.0-1081.87","5.4.0-1083.89","5.4.0-1084.90","5.4.0-1086.93","5.4.0-1087.94","5.4.0-1090.97","5.4.0-1091.98","5.4.0-1094.101","5.4.0-1095.102","5.4.0-1096.103","5.4.0-1097.104","5.4.0-1098.105","5.4.0-1099.106","5.4.0-1100.107","5.4.0-1101.108","5.4.0-1102.109","5.4.0-1103.110","5.4.0-1104.111","5.4.0-1105.112"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-gke-5.15","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.15.0-1011.14~20.04.1","5.15.0-1014.17~20.04.1","5.15.0-1015.18~20.04.1","5.15.0-1016.19~20.04.1","5.15.0-1019.23~20.04.1","5.15.0-1020.25~20.04.1","5.15.0-1023.28~20.04.2","5.15.0-1027.32~20.04.1","5.15.0-1028.33~20.04.1","5.15.0-1029.34~20.04.1","5.15.0-1031.36~20.04.1","5.15.0-1032.37~20.04.1","5.15.0-1033.38~20.04.1","5.15.0-1034.39~20.04.1","5.15.0-1036.41~20.04.1","5.15.0-1037.42~20.04.1","5.15.0-1038.43~20.04.1","5.15.0-1039.44~20.04.1"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-hwe-5.11","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.11.0-22.23~20.04.1","5.11.0-25.27~20.04.1","5.11.0-27.29~20.04.1","5.11.0-34.36~20.04.1","5.11.0-36.40~20.04.1","5.11.0-37.41~20.04.2","5.11.0-38.42~20.04.1","5.11.0-40.44~20.04.2","5.11.0-41.45~20.04.1","5.11.0-43.47~20.04.2","5.11.0-44.48~20.04.2","5.11.0-46.51~20.04.1"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-hwe-5.13","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.13.0-21.21~20.04.1","5.13.0-22.22~20.04.1","5.13.0-23.23~20.04.2","5.13.0-25.26~20.04.1","5.13.0-27.29~20.04.1","5.13.0-28.31~20.04.1","5.13.0-30.33~20.04.1","5.13.0-35.40~20.04.1","5.13.0-37.42~20.04.1","5.13.0-39.44~20.04.1","5.13.0-40.45~20.04.1","5.13.0-41.46~20.04.1","5.13.0-44.49~20.04.1","5.13.0-48.54~20.04.1","5.13.0-51.58~20.04.1","5.13.0-52.59~20.04.1"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-hwe-5.8","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.8.0-23.24~20.04.1","5.8.0-25.26~20.04.1","5.8.0-28.30~20.04.1","5.8.0-29.31~20.04.1","5.8.0-31.33~20.04.1","5.8.0-33.36~20.04.1","5.8.0-34.37~20.04.2","5.8.0-36.40~20.04.1","5.8.0-38.43~20.04.1","5.8.0-40.45~20.04.1","5.8.0-41.46~20.04.1","5.8.0-43.49~20.04.1","5.8.0-44.50~20.04.1","5.8.0-45.51~20.04.1","5.8.0-48.54~20.04.1","5.8.0-49.55~20.04.1","5.8.0-50.56~20.04.1","5.8.0-53.60~20.04.1","5.8.0-55.62~20.04.1","5.8.0-59.66~20.04.1","5.8.0-63.71~20.04.1"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-intel-5.13","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.13.0-1007.7","5.13.0-1008.8","5.13.0-1009.9","5.13.0-1010.10","5.13.0-1011.11","5.13.0-1014.15","5.13.0-1017.19"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-oem-5.10","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.10.0-1008.9","5.10.0-1011.12","5.10.0-1013.14","5.10.0-1014.15","5.10.0-1016.17","5.10.0-1017.18","5.10.0-1019.20","5.10.0-1021.22","5.10.0-1022.23","5.10.0-1023.24","5.10.0-1025.26","5.10.0-1026.27","5.10.0-1029.30","5.10.0-1032.33","5.10.0-1033.34","5.10.0-1034.35","5.10.0-1038.40","5.10.0-1044.46","5.10.0-1045.47","5.10.0-1049.51","5.10.0-1050.52","5.10.0-1051.53","5.10.0-1052.54","5.10.0-1053.55","5.10.0-1055.58","5.10.0-1057.61"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-oem-5.13","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.13.0-1009.10","5.13.0-1010.11","5.13.0-1012.16","5.13.0-1014.18","5.13.0-1017.21","5.13.0-1019.23","5.13.0-1020.24","5.13.0-1021.25","5.13.0-1022.26","5.13.0-1026.32","5.13.0-1028.35","5.13.0-1029.36"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-oem-5.14","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.14.0-1004.4","5.14.0-1005.5","5.14.0-1007.7","5.14.0-1008.8","5.14.0-1010.10","5.14.0-1011.11","5.14.0-1013.13","5.14.0-1018.19","5.14.0-1020.22","5.14.0-1022.24","5.14.0-1024.26","5.14.0-1027.30","5.14.0-1029.32","5.14.0-1031.34","5.14.0-1032.35","5.14.0-1033.36","5.14.0-1034.37","5.14.0-1036.40","5.14.0-1038.42","5.14.0-1042.47","5.14.0-1044.49","5.14.0-1045.51","5.14.0-1046.53","5.14.0-1047.54","5.14.0-1048.55","5.14.0-1049.56","5.14.0-1050.57","5.14.0-1051.58","5.14.0-1052.59","5.14.0-1054.61","5.14.0-1055.62","5.14.0-1056.63","5.14.0-1057.64","5.14.0-1058.66","5.14.0-1059.67"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-oem-5.6","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.6.0-1007.7","5.6.0-1008.8","5.6.0-1010.10","5.6.0-1011.11","5.6.0-1013.13","5.6.0-1017.17","5.6.0-1018.18","5.6.0-1020.20","5.6.0-1021.21","5.6.0-1023.23","5.6.0-1026.26","5.6.0-1027.27","5.6.0-1028.28","5.6.0-1031.32","5.6.0-1032.33","5.6.0-1033.35","5.6.0-1034.36","5.6.0-1035.37","5.6.0-1036.39","5.6.0-1039.43","5.6.0-1042.46","5.6.0-1047.51","5.6.0-1048.52","5.6.0-1050.54","5.6.0-1052.56","5.6.0-1053.57","5.6.0-1054.58","5.6.0-1055.59","5.6.0-1056.60"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-oracle-5.11","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.11.0-1008.8~20.04.1","5.11.0-1013.14~20.04.1","5.11.0-1016.17~20.04.1","5.11.0-1017.18~20.04.1","5.11.0-1019.20~20.04.1","5.11.0-1020.21~20.04.1","5.11.0-1021.22~20.04.1","5.11.0-1022.23~20.04.1","5.11.0-1023.24~20.04.1","5.11.0-1025.27~20.04.1","5.11.0-1027.30~20.04.1","5.11.0-1028.31~20.04.1"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-oracle-5.13","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.13.0-1011.13~20.04.2","5.13.0-1015.19~20.04.1","5.13.0-1016.20~20.04.1","5.13.0-1018.22~20.04.1","5.13.0-1021.26~20.04.1","5.13.0-1025.30~20.04.1","5.13.0-1027.32~20.04.1","5.13.0-1028.33~20.04.1","5.13.0-1030.35~20.04.1","5.13.0-1033.39~20.04.1","5.13.0-1034.40~20.04.1","5.13.0-1036.43~20.04.1"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-oracle-5.8","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.8.0-1031.32~20.04.2","5.8.0-1033.34~20.04.1","5.8.0-1034.35~20.04.2","5.8.0-1037.38~20.04.1","5.8.0-1038.39~20.04.1"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-raspi2","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.3.0-1007.8","5.3.0-1014.16","5.3.0-1015.17","5.3.0-1017.19","5.4.0-1004.4","5.4.0-1006.6"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-riscv","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.4.0-24.28","5.4.0-26.30","5.4.0-27.31","5.4.0-28.32","5.4.0-30.34","5.4.0-31.35","5.4.0-33.37","5.4.0-34.38","5.4.0-36.41","5.4.0-37.42","5.4.0-39.44","5.4.0-40.45"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-riscv-5.11","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.11.0-1015.16~20.04.1","5.11.0-1017.18~20.04.1","5.11.0-1018.19~20.04.2","5.11.0-1020.21~20.04.1","5.11.0-1021.22~20.04.1","5.11.0-1022.23~20.04.1","5.11.0-1023.24~20.04.1","5.11.0-1024.25~20.04.1","5.11.0-1026.28~20.04.1","5.11.0-1028.31~20.04.1","5.11.0-1029.32~20.04.1","5.11.0-1030.34","5.11.0-1031.35"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-riscv-5.8","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.8.0-14.16~20.04.1","5.8.0-14.16~20.04.3","5.8.0-16.18~20.04.1","5.8.0-17.19~20.04.1","5.8.0-18.20~20.04.1","5.8.0-20.22~20.04.1","5.8.0-22.24~20.04.1","5.8.0-25.27~20.04.1","5.8.0-26.28~20.04.1","5.8.0-29.31~20.04.1"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-allwinner-5.19","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.19.0-1007.7~22.04.1","5.19.0-1009.9~22.04.1","5.19.0-1010.10~22.04.1","5.19.0-1011.11~22.04.1","5.19.0-1012.12~22.04.1","5.19.0-1013.13~22.04.1","5.19.0-1014.14~22.04.1","5.19.0-1015.15~22.04.1"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-aws-5.19","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.19.0-1019.20~22.04.1","5.19.0-1020.21~22.04.1","5.19.0-1022.23~22.04.1","5.19.0-1023.24~22.04.1","5.19.0-1024.25~22.04.1","5.19.0-1025.26~22.04.1","5.19.0-1026.27~22.04.1","5.19.0-1027.28~22.04.1","5.19.0-1028.29~22.04.1","5.19.0-1029.30~22.04.1"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-aws-6.2","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["6.2.0-1005.5~22.04.1","6.2.0-1006.6~22.04.1","6.2.0-1007.7~22.04.1","6.2.0-1008.8~22.04.1","6.2.0-1009.9~22.04.3","6.2.0-1010.10~22.04.1","6.2.0-1011.11~22.04.1","6.2.0-1012.12~22.04.1","6.2.0-1013.13~22.04.1","6.2.0-1014.14~22.04.1","6.2.0-1015.15~22.04.1","6.2.0-1016.16~22.04.1","6.2.0-1017.17~22.04.1","6.2.0-1018.18~22.04.1"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-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-fde-5.19","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.19.0-1025.28~22.04.1.1","5.19.0-1026.29~22.04.1.1","5.19.0-1027.30~22.04.2.1"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-azure-fde-6.2","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["6.2.0-1008.8~22.04.1.1","6.2.0-1009.9~22.04.3.1","6.2.0-1011.11~22.04.1.1","6.2.0-1012.12~22.04.1.1","6.2.0-1014.14~22.04.1.1","6.2.0-1015.15~22.04.1.1","6.2.0-1016.16~22.04.1.1","6.2.0-1017.17~22.04.1.1","6.2.0-1018.18~22.04.1.1","6.2.0-1019.19~22.04.1.1"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-gcp-5.19","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.19.0-1020.22~22.04.2","5.19.0-1021.23~22.04.1","5.19.0-1022.24~22.04.1","5.19.0-1024.26~22.04.1","5.19.0-1025.27~22.04.1","5.19.0-1026.28~22.04.1","5.19.0-1027.29~22.04.1","5.19.0-1030.32~22.04.1"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-gcp-6.2","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["6.2.0-1009.9~22.04.3","6.2.0-1010.10~22.04.1","6.2.0-1011.11~22.04.1","6.2.0-1011.11~22.04.3","6.2.0-1012.12~22.04.1","6.2.0-1013.13~22.04.1","6.2.0-1014.14~22.04.1","6.2.0-1016.18~22.04.1","6.2.0-1017.19~22.04.1","6.2.0-1018.20~22.04.1","6.2.0-1019.21~22.04.1","6.2.0-1021.23~22.04.1"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-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-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-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-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-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-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"]}],"products":[{"vendor":"linux","product":"linux"},{"vendor":"linux","product":"linux_kernel"}],"references":[{"url":"https://git.kernel.org/stable/c/0bfe741741327822d1482c7edef0184636d08b40","tags":["x_transferred","Patch","fix","report"]},{"url":"https://git.kernel.org/stable/c/d2b59bd4b06d84a4eadb520b0f71c62fe8ec0a62","tags":["x_transferred","Patch","fix","report"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2021-47382","tags":["advisory"]},{"url":"https://github.com/advisories/GHSA-q77h-85v7-m3mw"},{"url":"https://security-tracker.debian.org/tracker/CVE-2021-47382","tags":["advisory"]},{"url":"https://www.openeuler.org/zh/security/security-bulletins/detail/?id=openEuler-SA-2024-1962","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-48827","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-52887","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-33621","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-35825","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-38546","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-38561","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-38594","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-38627","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-39497","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-39507","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-40910","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-40953","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-40959","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-40961","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-40976","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-40988","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-40999","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-41006","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-41013","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-41014","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-41019","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-41020","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-41022","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-41023","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-41027","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-41040","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-41041","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-41044","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-41048","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-41049","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-41055","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-41062","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-41063","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-41064","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-41066","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-41069","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-41070","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-41072","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-41073","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-41077","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-41079","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-41080","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-41081","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-41087","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-41089","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-41090","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-41091","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-41097","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-42068","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-42076","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-42077","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-42080","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-42082","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-42084","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-42086","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-42089","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-42090","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-42092","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-42093","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-42094","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-42097","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-42101","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-42106","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-42115","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-42124","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-42129","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-42137","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-42145","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-42155","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-42160","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-42161","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-42162","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-42224","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-42228","tags":["advisory"]},{"url":"https://www.openeuler.org/zh/security/security-bulletins/detail/?id=openEuler-SA-2024-1964","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-52674","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-52764","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-35904","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-39471","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-40982","tags":["advisory"]},{"url":"https://www.openeuler.org/zh/security/security-bulletins/detail/?id=openEuler-SA-2024-2258","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-48893","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-35969","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-36005","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-36031","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-36270","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-36880","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-36915","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-36934","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-36946","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-38560","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-38611","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-38613","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-38659","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-39292","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-39494","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-40932","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-42067","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-42283","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-42290","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-42306","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-42309","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-42313","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-42322","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-43823","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-43830","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-43840","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-43855","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-43872","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-43892","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-43893","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-44940","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-44954","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-44998","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-45006","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-45026","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-46676","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-46719","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-46754","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-46770","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-46795","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-46819","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-46826","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-46828","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-46840","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-46848","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-46854","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-46855","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-46858","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-47658","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-47664","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-47670","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-47671","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-47672","tags":["advisory"]},{"url":"https://www.suse.com/support/update/announcement/2024/suse-su-20241979-1/","tags":["advisory"]},{"url":"https://bugzilla.suse.com/1065729","tags":["report"]},{"url":"https://bugzilla.suse.com/1101816","tags":["report"]},{"url":"https://bugzilla.suse.com/1181674","tags":["report"]},{"url":"https://bugzilla.suse.com/1185902","tags":["report"]},{"url":"https://bugzilla.suse.com/1187716","tags":["report"]},{"url":"https://bugzilla.suse.com/1188616","tags":["report"]},{"url":"https://bugzilla.suse.com/1190317","tags":["report"]},{"url":"https://bugzilla.suse.com/1190795","tags":["report"]},{"url":"https://bugzilla.suse.com/1191452","tags":["report"]},{"url":"https://bugzilla.suse.com/1194591","tags":["report"]},{"url":"https://bugzilla.suse.com/1197760","tags":["report"]},{"url":"https://bugzilla.suse.com/1206213","tags":["report"]},{"url":"https://bugzilla.suse.com/1206646","tags":["report"]},{"url":"https://bugzilla.suse.com/1207186","tags":["report"]},{"url":"https://bugzilla.suse.com/1209657","tags":["report"]},{"url":"https://bugzilla.suse.com/1210335","tags":["report"]},{"url":"https://bugzilla.suse.com/1215702","tags":["report"]},{"url":"https://bugzilla.suse.com/1216702","tags":["report"]},{"url":"https://bugzilla.suse.com/1217169","tags":["report"]},{"url":"https://bugzilla.suse.com/1217519","tags":["report"]},{"url":"https://bugzilla.suse.com/1220487","tags":["report"]},{"url":"https://bugzilla.suse.com/1220854","tags":["report"]},{"url":"https://bugzilla.suse.com/1220928","tags":["report"]},{"url":"https://bugzilla.suse.com/1221044","tags":["report"]},{"url":"https://bugzilla.suse.com/1221081","tags":["report"]},{"url":"https://bugzilla.suse.com/1221086","tags":["report"]},{"url":"https://bugzilla.suse.com/1221977","tags":["report"]},{"url":"https://bugzilla.suse.com/1221994","tags":["report"]},{"url":"https://bugzilla.suse.com/1222619","tags":["report"]},{"url":"https://bugzilla.suse.com/1222627","tags":["report"]},{"url":"https://bugzilla.suse.com/1222667","tags":["report"]},{"url":"https://bugzilla.suse.com/1222671","tags":["report"]},{"url":"https://bugzilla.suse.com/1222893","tags":["report"]},{"url":"https://bugzilla.suse.com/1222894","tags":["report"]},{"url":"https://bugzilla.suse.com/1223023","tags":["report"]},{"url":"https://bugzilla.suse.com/1223046","tags":["report"]},{"url":"https://bugzilla.suse.com/1223048","tags":["report"]},{"url":"https://bugzilla.suse.com/1223084","tags":["report"]},{"url":"https://bugzilla.suse.com/1223138","tags":["report"]},{"url":"https://bugzilla.suse.com/1223207","tags":["report"]},{"url":"https://bugzilla.suse.com/1223360","tags":["report"]},{"url":"https://bugzilla.suse.com/1223384","tags":["report"]},{"url":"https://bugzilla.suse.com/1223633","tags":["report"]},{"url":"https://bugzilla.suse.com/1223653","tags":["report"]},{"url":"https://bugzilla.suse.com/1223666","tags":["report"]},{"url":"https://bugzilla.suse.com/1223671","tags":["report"]},{"url":"https://bugzilla.suse.com/1223738","tags":["report"]},{"url":"https://bugzilla.suse.com/1223752","tags":["report"]},{"url":"https://bugzilla.suse.com/1223834","tags":["report"]},{"url":"https://bugzilla.suse.com/1223922","tags":["report"]},{"url":"https://bugzilla.suse.com/1223932","tags":["report"]},{"url":"https://bugzilla.suse.com/1223948","tags":["report"]},{"url":"https://bugzilla.suse.com/1224096","tags":["report"]},{"url":"https://bugzilla.suse.com/1224174","tags":["report"]},{"url":"https://bugzilla.suse.com/1224181","tags":["report"]},{"url":"https://bugzilla.suse.com/1224347","tags":["report"]},{"url":"https://bugzilla.suse.com/1224482","tags":["report"]},{"url":"https://bugzilla.suse.com/1224511","tags":["report"]},{"url":"https://bugzilla.suse.com/1224525","tags":["report"]},{"url":"https://bugzilla.suse.com/1224566","tags":["report"]},{"url":"https://bugzilla.suse.com/1224580","tags":["report"]},{"url":"https://bugzilla.suse.com/1224592","tags":["report"]},{"url":"https://bugzilla.suse.com/1224601","tags":["report"]},{"url":"https://bugzilla.suse.com/1224607","tags":["report"]},{"url":"https://bugzilla.suse.com/1224621","tags":["report"]},{"url":"https://bugzilla.suse.com/1224644","tags":["report"]},{"url":"https://bugzilla.suse.com/1224645","tags":["report"]},{"url":"https://bugzilla.suse.com/1224648","tags":["report"]},{"url":"https://bugzilla.suse.com/1224650","tags":["report"]},{"url":"https://bugzilla.suse.com/1224663","tags":["report"]},{"url":"https://bugzilla.suse.com/1224671","tags":["report"]},{"url":"https://bugzilla.suse.com/1224676","tags":["report"]},{"url":"https://bugzilla.suse.com/1224680","tags":["report"]},{"url":"https://bugzilla.suse.com/1224682","tags":["report"]},{"url":"https://bugzilla.suse.com/1224725","tags":["report"]},{"url":"https://bugzilla.suse.com/1224728","tags":["report"]},{"url":"https://bugzilla.suse.com/1224733","tags":["report"]},{"url":"https://bugzilla.suse.com/1224738","tags":["report"]},{"url":"https://bugzilla.suse.com/1224747","tags":["report"]},{"url":"https://bugzilla.suse.com/1224749","tags":["report"]},{"url":"https://bugzilla.suse.com/1224759","tags":["report"]},{"url":"https://bugzilla.suse.com/1224803","tags":["report"]},{"url":"https://bugzilla.suse.com/1224827","tags":["report"]},{"url":"https://bugzilla.suse.com/1224830","tags":["report"]},{"url":"https://bugzilla.suse.com/1224831","tags":["report"]},{"url":"https://bugzilla.suse.com/1224834","tags":["report"]},{"url":"https://bugzilla.suse.com/1224838","tags":["report"]},{"url":"https://bugzilla.suse.com/1224841","tags":["report"]},{"url":"https://bugzilla.suse.com/1224844","tags":["report"]},{"url":"https://bugzilla.suse.com/1224846","tags":["report"]},{"url":"https://bugzilla.suse.com/1224847","tags":["report"]},{"url":"https://bugzilla.suse.com/1224849","tags":["report"]},{"url":"https://bugzilla.suse.com/1224854","tags":["report"]},{"url":"https://bugzilla.suse.com/1224859","tags":["report"]},{"url":"https://bugzilla.suse.com/1224867","tags":["report"]},{"url":"https://bugzilla.suse.com/1224880","tags":["report"]},{"url":"https://bugzilla.suse.com/1224882","tags":["report"]},{"url":"https://bugzilla.suse.com/1224888","tags":["report"]},{"url":"https://bugzilla.suse.com/1224889","tags":["report"]},{"url":"https://bugzilla.suse.com/1224892","tags":["report"]},{"url":"https://bugzilla.suse.com/1224893","tags":["report"]},{"url":"https://bugzilla.suse.com/1224899","tags":["report"]},{"url":"https://bugzilla.suse.com/1224904","tags":["report"]},{"url":"https://bugzilla.suse.com/1224907","tags":["report"]},{"url":"https://bugzilla.suse.com/1224916","tags":["report"]},{"url":"https://bugzilla.suse.com/1224917","tags":["report"]},{"url":"https://bugzilla.suse.com/1224922","tags":["report"]},{"url":"https://bugzilla.suse.com/1224926","tags":["report"]},{"url":"https://bugzilla.suse.com/1224930","tags":["report"]},{"url":"https://bugzilla.suse.com/1224931","tags":["report"]},{"url":"https://bugzilla.suse.com/1224942","tags":["report"]},{"url":"https://bugzilla.suse.com/1224954","tags":["report"]},{"url":"https://bugzilla.suse.com/1224957","tags":["report"]},{"url":"https://bugzilla.suse.com/1224959","tags":["report"]},{"url":"https://bugzilla.suse.com/1224960","tags":["report"]},{"url":"https://bugzilla.suse.com/1224961","tags":["report"]},{"url":"https://bugzilla.suse.com/1224963","tags":["report"]},{"url":"https://bugzilla.suse.com/1224966","tags":["report"]},{"url":"https://bugzilla.suse.com/1224968","tags":["report"]},{"url":"https://bugzilla.suse.com/1224981","tags":["report"]},{"url":"https://bugzilla.suse.com/1224982","tags":["report"]},{"url":"https://bugzilla.suse.com/1224983","tags":["report"]},{"url":"https://bugzilla.suse.com/1224987","tags":["report"]},{"url":"https://bugzilla.suse.com/1224990","tags":["report"]},{"url":"https://bugzilla.suse.com/1224996","tags":["report"]},{"url":"https://bugzilla.suse.com/1225008","tags":["report"]},{"url":"https://bugzilla.suse.com/1225009","tags":["report"]},{"url":"https://bugzilla.suse.com/1225010","tags":["report"]},{"url":"https://bugzilla.suse.com/1225022","tags":["report"]},{"url":"https://bugzilla.suse.com/1225026","tags":["report"]},{"url":"https://bugzilla.suse.com/1225030","tags":["report"]},{"url":"https://bugzilla.suse.com/1225054","tags":["report"]},{"url":"https://bugzilla.suse.com/1225058","tags":["report"]},{"url":"https://bugzilla.suse.com/1225059","tags":["report"]},{"url":"https://bugzilla.suse.com/1225060","tags":["report"]},{"url":"https://bugzilla.suse.com/1225062","tags":["report"]},{"url":"https://bugzilla.suse.com/1225082","tags":["report"]},{"url":"https://bugzilla.suse.com/1225084","tags":["report"]},{"url":"https://bugzilla.suse.com/1225086","tags":["report"]},{"url":"https://bugzilla.suse.com/1225092","tags":["report"]},{"url":"https://bugzilla.suse.com/1225096","tags":["report"]},{"url":"https://bugzilla.suse.com/1225112","tags":["report"]},{"url":"https://bugzilla.suse.com/1225124","tags":["report"]},{"url":"https://bugzilla.suse.com/1225128","tags":["report"]},{"url":"https://bugzilla.suse.com/1225132","tags":["report"]},{"url":"https://bugzilla.suse.com/1225141","tags":["report"]},{"url":"https://bugzilla.suse.com/1225143","tags":["report"]},{"url":"https://bugzilla.suse.com/1225144","tags":["report"]},{"url":"https://bugzilla.suse.com/1225151","tags":["report"]},{"url":"https://bugzilla.suse.com/1225153","tags":["report"]},{"url":"https://bugzilla.suse.com/1225155","tags":["report"]},{"url":"https://bugzilla.suse.com/1225157","tags":["report"]},{"url":"https://bugzilla.suse.com/1225164","tags":["report"]},{"url":"https://bugzilla.suse.com/1225177","tags":["report"]},{"url":"https://bugzilla.suse.com/1225189","tags":["report"]},{"url":"https://bugzilla.suse.com/1225192","tags":["report"]},{"url":"https://bugzilla.suse.com/1225193","tags":["report"]},{"url":"https://bugzilla.suse.com/1225198","tags":["report"]},{"url":"https://bugzilla.suse.com/1225201","tags":["report"]},{"url":"https://bugzilla.suse.com/1225207","tags":["report"]},{"url":"https://bugzilla.suse.com/1225208","tags":["report"]},{"url":"https://bugzilla.suse.com/1225222","tags":["report"]},{"url":"https://bugzilla.suse.com/1225230","tags":["report"]},{"url":"https://bugzilla.suse.com/1225242","tags":["report"]},{"url":"https://bugzilla.suse.com/1225244","tags":["report"]},{"url":"https://bugzilla.suse.com/1225247","tags":["report"]},{"url":"https://bugzilla.suse.com/1225251","tags":["report"]},{"url":"https://bugzilla.suse.com/1225252","tags":["report"]},{"url":"https://bugzilla.suse.com/1225256","tags":["report"]},{"url":"https://bugzilla.suse.com/1225303","tags":["report"]},{"url":"https://bugzilla.suse.com/1225318","tags":["report"]},{"url":"https://bugzilla.suse.com/1225322","tags":["report"]},{"url":"https://bugzilla.suse.com/1225329","tags":["report"]},{"url":"https://bugzilla.suse.com/1225330","tags":["report"]},{"url":"https://bugzilla.suse.com/1225336","tags":["report"]},{"url":"https://bugzilla.suse.com/1225347","tags":["report"]},{"url":"https://bugzilla.suse.com/1225351","tags":["report"]},{"url":"https://bugzilla.suse.com/1225354","tags":["report"]},{"url":"https://bugzilla.suse.com/1225355","tags":["report"]},{"url":"https://bugzilla.suse.com/1225360","tags":["report"]},{"url":"https://bugzilla.suse.com/1225366","tags":["report"]},{"url":"https://bugzilla.suse.com/1225367","tags":["report"]},{"url":"https://bugzilla.suse.com/1225384","tags":["report"]},{"url":"https://bugzilla.suse.com/1225390","tags":["report"]},{"url":"https://bugzilla.suse.com/1225404","tags":["report"]},{"url":"https://bugzilla.suse.com/1225409","tags":["report"]},{"url":"https://bugzilla.suse.com/1225411","tags":["report"]},{"url":"https://bugzilla.suse.com/1225438","tags":["report"]},{"url":"https://bugzilla.suse.com/1225453","tags":["report"]},{"url":"https://bugzilla.suse.com/1225479","tags":["report"]},{"url":"https://bugzilla.suse.com/1225482","tags":["report"]},{"url":"https://bugzilla.suse.com/1225506","tags":["report"]},{"url":"https://bugzilla.suse.com/1225549","tags":["report"]},{"url":"https://bugzilla.suse.com/1225560","tags":["report"]},{"url":"https://bugzilla.suse.com/1225572","tags":["report"]},{"url":"https://bugzilla.suse.com/1225640","tags":["report"]},{"url":"https://bugzilla.suse.com/1225708","tags":["report"]},{"url":"https://bugzilla.suse.com/1225764","tags":["report"]},{"url":"https://www.suse.com/security/cve/CVE-2021-46933","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-47074","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-47162","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-47171","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-47188","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-47206","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-47220","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-47229","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-47231","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-47235","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-47236","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-47237","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-47238","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-47239","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-47245","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-47246","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-47248","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-47249","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-47250","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-47252","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-47254","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-47258","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-47260","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-47261","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-47265","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-47269","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-47274","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-47276","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-47277","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-47280","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-47281","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-47284","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-47285","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-47288","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-47301","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-47302","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-47305","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-47307","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-47308","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-47310","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-47311","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-47314","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-47315","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-47319","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-47320","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-47321","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-47323","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-47324","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-47330","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-47334","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-47337","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-47343","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-47344","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-47345","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-47347","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-47352","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-47353","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-47355","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-47356","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-47357","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-47361","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-47362","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-47369","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-47375","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-47378","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-47382","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-47383","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-47391","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-47397","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-47400","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-47401","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-47404","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-47409","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-47416","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-47423","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-47424","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-47431","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-47435","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-47436","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-47456","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-47458","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-47460","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-47469","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-47472","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-47473","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-47478","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-47480","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-47483","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-47485","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-47495","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-47496","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-47497","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-47500","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-47506","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-47509","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-47511","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-47523","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-47541","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-47548","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-47565","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-48686","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-48697","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-48704","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-48708","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-48710","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-0160","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-1829","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-42755","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-47233","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-52527","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-52586","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-52591","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-52655","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-52664","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-52685","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-52686","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-52691","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-52696","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-52698","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-52703","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-52730","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-52732","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-52741","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-52742","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-52747","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-52759","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-52774","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-52781","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-52796","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-52803","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-52821","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-52864","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-52865","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-52867","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-52875","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-52880","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-26625","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-26752","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-26775","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-26828","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-26846","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-26874","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-26900","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-26915","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-26920","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-26921","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-26934","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-26957","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-26958","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-26984","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-26996","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-27059","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-27062","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-27396","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-27398","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-27401","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-27419","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-27436","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-35789","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-35791","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-35809","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-35811","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-35830","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-35849","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-35877","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-35878","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-35887","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-35895","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-35914","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-35932","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-35935","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-35936","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-35944","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-35955","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-35969","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-35982","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-35984","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-36015","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-36029","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-36954","tags":["web"]},{"url":"https://www.suse.com/support/update/announcement/2024/suse-su-20241983-1/","tags":["advisory"]},{"url":"https://bugzilla.suse.com/1141539","tags":["report"]},{"url":"https://bugzilla.suse.com/1197894","tags":["report"]},{"url":"https://bugzilla.suse.com/1203935","tags":["report"]},{"url":"https://bugzilla.suse.com/1218917","tags":["report"]},{"url":"https://bugzilla.suse.com/1220513","tags":["report"]},{"url":"https://bugzilla.suse.com/1221543","tags":["report"]},{"url":"https://bugzilla.suse.com/1221545","tags":["report"]},{"url":"https://bugzilla.suse.com/1221816","tags":["report"]},{"url":"https://bugzilla.suse.com/1222559","tags":["report"]},{"url":"https://bugzilla.suse.com/1222793","tags":["report"]},{"url":"https://bugzilla.suse.com/1223119","tags":["report"]},{"url":"https://bugzilla.suse.com/1223432","tags":["report"]},{"url":"https://bugzilla.suse.com/1223509","tags":["report"]},{"url":"https://bugzilla.suse.com/1223512","tags":["report"]},{"url":"https://bugzilla.suse.com/1223539","tags":["report"]},{"url":"https://bugzilla.suse.com/1223540","tags":["report"]},{"url":"https://bugzilla.suse.com/1223626","tags":["report"]},{"url":"https://bugzilla.suse.com/1223627","tags":["report"]},{"url":"https://bugzilla.suse.com/1223712","tags":["report"]},{"url":"https://bugzilla.suse.com/1223715","tags":["report"]},{"url":"https://bugzilla.suse.com/1223744","tags":["report"]},{"url":"https://bugzilla.suse.com/1223802","tags":["report"]},{"url":"https://bugzilla.suse.com/1223819","tags":["report"]},{"url":"https://bugzilla.suse.com/1223923","tags":["report"]},{"url":"https://bugzilla.suse.com/1223931","tags":["report"]},{"url":"https://bugzilla.suse.com/1223969","tags":["report"]},{"url":"https://bugzilla.suse.com/1224956","tags":["report"]},{"url":"https://www.suse.com/security/cve/CVE-2021-46955","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-47113","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-47131","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-48636","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-48650","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-48672","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-48702","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-52646","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-52653","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-0639","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-26739","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-26791","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-26876","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-26929","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-26930","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-26931","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-27008","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-27054","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-27388","tags":["web"]},{"url":"https://www.suse.com/support/update/announcement/2024/suse-su-20242008-1/","tags":["advisory"]},{"url":"https://bugzilla.suse.com/1174585","tags":["report"]},{"url":"https://bugzilla.suse.com/1190569","tags":["report"]},{"url":"https://bugzilla.suse.com/1191949","tags":["report"]},{"url":"https://bugzilla.suse.com/1192107","tags":["report"]},{"url":"https://bugzilla.suse.com/1193983","tags":["report"]},{"url":"https://bugzilla.suse.com/1194288","tags":["report"]},{"url":"https://bugzilla.suse.com/1194869","tags":["report"]},{"url":"https://bugzilla.suse.com/1196956","tags":["report"]},{"url":"https://bugzilla.suse.com/1197915","tags":["report"]},{"url":"https://bugzilla.suse.com/1200465","tags":["report"]},{"url":"https://bugzilla.suse.com/1205205","tags":["report"]},{"url":"https://bugzilla.suse.com/1207284","tags":["report"]},{"url":"https://bugzilla.suse.com/1207361","tags":["report"]},{"url":"https://bugzilla.suse.com/1207948","tags":["report"]},{"url":"https://bugzilla.suse.com/1208149","tags":["report"]},{"url":"https://bugzilla.suse.com/1209799","tags":["report"]},{"url":"https://bugzilla.suse.com/1209834","tags":["report"]},{"url":"https://bugzilla.suse.com/1209980","tags":["report"]},{"url":"https://bugzilla.suse.com/1213863","tags":["report"]},{"url":"https://bugzilla.suse.com/1214852","tags":["report"]},{"url":"https://bugzilla.suse.com/1215322","tags":["report"]},{"url":"https://bugzilla.suse.com/1216358","tags":["report"]},{"url":"https://bugzilla.suse.com/1217339","tags":["report"]},{"url":"https://bugzilla.suse.com/1217515","tags":["report"]},{"url":"https://bugzilla.suse.com/1218447","tags":["report"]},{"url":"https://bugzilla.suse.com/1220021","tags":["report"]},{"url":"https://bugzilla.suse.com/1220267","tags":["report"]},{"url":"https://bugzilla.suse.com/1220363","tags":["report"]},{"url":"https://bugzilla.suse.com/1220783","tags":["report"]},{"url":"https://bugzilla.suse.com/1221615","tags":["report"]},{"url":"https://bugzilla.suse.com/1221777","tags":["report"]},{"url":"https://bugzilla.suse.com/1221829","tags":["report"]},{"url":"https://bugzilla.suse.com/1222011","tags":["report"]},{"url":"https://bugzilla.suse.com/1222374","tags":["report"]},{"url":"https://bugzilla.suse.com/1222385","tags":["report"]},{"url":"https://bugzilla.suse.com/1222413","tags":["report"]},{"url":"https://bugzilla.suse.com/1222464","tags":["report"]},{"url":"https://bugzilla.suse.com/1222513","tags":["report"]},{"url":"https://bugzilla.suse.com/1222561","tags":["report"]},{"url":"https://bugzilla.suse.com/1222608","tags":["report"]},{"url":"https://bugzilla.suse.com/1222721","tags":["report"]},{"url":"https://bugzilla.suse.com/1222765","tags":["report"]},{"url":"https://bugzilla.suse.com/1222770","tags":["report"]},{"url":"https://bugzilla.suse.com/1222783","tags":["report"]},{"url":"https://bugzilla.suse.com/1222838","tags":["report"]},{"url":"https://bugzilla.suse.com/1222870","tags":["report"]},{"url":"https://bugzilla.suse.com/1222960","tags":["report"]},{"url":"https://bugzilla.suse.com/1222961","tags":["report"]},{"url":"https://bugzilla.suse.com/1222974","tags":["report"]},{"url":"https://bugzilla.suse.com/1222975","tags":["report"]},{"url":"https://bugzilla.suse.com/1222976","tags":["report"]},{"url":"https://bugzilla.suse.com/1223011","tags":["report"]},{"url":"https://bugzilla.suse.com/1223027","tags":["report"]},{"url":"https://bugzilla.suse.com/1223031","tags":["report"]},{"url":"https://bugzilla.suse.com/1223043","tags":["report"]},{"url":"https://bugzilla.suse.com/1223049","tags":["report"]},{"url":"https://bugzilla.suse.com/1223113","tags":["report"]},{"url":"https://bugzilla.suse.com/1223137","tags":["report"]},{"url":"https://bugzilla.suse.com/1223140","tags":["report"]},{"url":"https://bugzilla.suse.com/1223188","tags":["report"]},{"url":"https://bugzilla.suse.com/1223203","tags":["report"]},{"url":"https://bugzilla.suse.com/1223315","tags":["report"]},{"url":"https://bugzilla.suse.com/1223390","tags":["report"]},{"url":"https://bugzilla.suse.com/1223489","tags":["report"]},{"url":"https://bugzilla.suse.com/1223505","tags":["report"]},{"url":"https://bugzilla.suse.com/1223532","tags":["report"]},{"url":"https://bugzilla.suse.com/1223575","tags":["report"]},{"url":"https://bugzilla.suse.com/1223595","tags":["report"]},{"url":"https://bugzilla.suse.com/1223628","tags":["report"]},{"url":"https://bugzilla.suse.com/1223631","tags":["report"]},{"url":"https://bugzilla.suse.com/1223638","tags":["report"]},{"url":"https://bugzilla.suse.com/1223650","tags":["report"]},{"url":"https://bugzilla.suse.com/1223670","tags":["report"]},{"url":"https://bugzilla.suse.com/1223675","tags":["report"]},{"url":"https://bugzilla.suse.com/1223677","tags":["report"]},{"url":"https://bugzilla.suse.com/1223678","tags":["report"]},{"url":"https://bugzilla.suse.com/1223679","tags":["report"]},{"url":"https://bugzilla.suse.com/1223698","tags":["report"]},{"url":"https://bugzilla.suse.com/1223717","tags":["report"]},{"url":"https://bugzilla.suse.com/1223718","tags":["report"]},{"url":"https://bugzilla.suse.com/1223737","tags":["report"]},{"url":"https://bugzilla.suse.com/1223741","tags":["report"]},{"url":"https://bugzilla.suse.com/1223747","tags":["report"]},{"url":"https://bugzilla.suse.com/1223748","tags":["report"]},{"url":"https://bugzilla.suse.com/1223750","tags":["report"]},{"url":"https://bugzilla.suse.com/1223754","tags":["report"]},{"url":"https://bugzilla.suse.com/1223756","tags":["report"]},{"url":"https://bugzilla.suse.com/1223757","tags":["report"]},{"url":"https://bugzilla.suse.com/1223762","tags":["report"]},{"url":"https://bugzilla.suse.com/1223769","tags":["report"]},{"url":"https://bugzilla.suse.com/1223770","tags":["report"]},{"url":"https://bugzilla.suse.com/1223779","tags":["report"]},{"url":"https://bugzilla.suse.com/1223780","tags":["report"]},{"url":"https://bugzilla.suse.com/1223781","tags":["report"]},{"url":"https://bugzilla.suse.com/1223788","tags":["report"]},{"url":"https://bugzilla.suse.com/1223823","tags":["report"]},{"url":"https://bugzilla.suse.com/1223826","tags":["report"]},{"url":"https://bugzilla.suse.com/1223828","tags":["report"]},{"url":"https://bugzilla.suse.com/1223829","tags":["report"]},{"url":"https://bugzilla.suse.com/1223837","tags":["report"]},{"url":"https://bugzilla.suse.com/1223842","tags":["report"]},{"url":"https://bugzilla.suse.com/1223843","tags":["report"]},{"url":"https://bugzilla.suse.com/1223844","tags":["report"]},{"url":"https://bugzilla.suse.com/1223847","tags":["report"]},{"url":"https://bugzilla.suse.com/1223858","tags":["report"]},{"url":"https://bugzilla.suse.com/1223875","tags":["report"]},{"url":"https://bugzilla.suse.com/1223879","tags":["report"]},{"url":"https://bugzilla.suse.com/1223895","tags":["report"]},{"url":"https://bugzilla.suse.com/1223959","tags":["report"]},{"url":"https://bugzilla.suse.com/1223961","tags":["report"]},{"url":"https://bugzilla.suse.com/1223991","tags":["report"]},{"url":"https://bugzilla.suse.com/1223996","tags":["report"]},{"url":"https://bugzilla.suse.com/1224020","tags":["report"]},{"url":"https://bugzilla.suse.com/1224076","tags":["report"]},{"url":"https://bugzilla.suse.com/1224098","tags":["report"]},{"url":"https://bugzilla.suse.com/1224099","tags":["report"]},{"url":"https://bugzilla.suse.com/1224137","tags":["report"]},{"url":"https://bugzilla.suse.com/1224166","tags":["report"]},{"url":"https://bugzilla.suse.com/1224177","tags":["report"]},{"url":"https://bugzilla.suse.com/1224180","tags":["report"]},{"url":"https://bugzilla.suse.com/1224187","tags":["report"]},{"url":"https://bugzilla.suse.com/1224331","tags":["report"]},{"url":"https://bugzilla.suse.com/1224346","tags":["report"]},{"url":"https://bugzilla.suse.com/1224423","tags":["report"]},{"url":"https://bugzilla.suse.com/1224432","tags":["report"]},{"url":"https://bugzilla.suse.com/1224437","tags":["report"]},{"url":"https://bugzilla.suse.com/1224438","tags":["report"]},{"url":"https://bugzilla.suse.com/1224442","tags":["report"]},{"url":"https://bugzilla.suse.com/1224443","tags":["report"]},{"url":"https://bugzilla.suse.com/1224445","tags":["report"]},{"url":"https://bugzilla.suse.com/1224449","tags":["report"]},{"url":"https://bugzilla.suse.com/1224479","tags":["report"]},{"url":"https://bugzilla.suse.com/1224487","tags":["report"]},{"url":"https://bugzilla.suse.com/1224488","tags":["report"]},{"url":"https://bugzilla.suse.com/1224492","tags":["report"]},{"url":"https://bugzilla.suse.com/1224494","tags":["report"]},{"url":"https://bugzilla.suse.com/1224495","tags":["report"]},{"url":"https://bugzilla.suse.com/1224502","tags":["report"]},{"url":"https://bugzilla.suse.com/1224508","tags":["report"]},{"url":"https://bugzilla.suse.com/1224509","tags":["report"]},{"url":"https://bugzilla.suse.com/1224519","tags":["report"]},{"url":"https://bugzilla.suse.com/1224524","tags":["report"]},{"url":"https://bugzilla.suse.com/1224530","tags":["report"]},{"url":"https://bugzilla.suse.com/1224531","tags":["report"]},{"url":"https://bugzilla.suse.com/1224534","tags":["report"]},{"url":"https://bugzilla.suse.com/1224535","tags":["report"]},{"url":"https://bugzilla.suse.com/1224537","tags":["report"]},{"url":"https://bugzilla.suse.com/1224541","tags":["report"]},{"url":"https://bugzilla.suse.com/1224543","tags":["report"]},{"url":"https://bugzilla.suse.com/1224549","tags":["report"]},{"url":"https://bugzilla.suse.com/1224550","tags":["report"]},{"url":"https://bugzilla.suse.com/1224558","tags":["report"]},{"url":"https://bugzilla.suse.com/1224559","tags":["report"]},{"url":"https://bugzilla.suse.com/1224567","tags":["report"]},{"url":"https://bugzilla.suse.com/1224571","tags":["report"]},{"url":"https://bugzilla.suse.com/1224575","tags":["report"]},{"url":"https://bugzilla.suse.com/1224576","tags":["report"]},{"url":"https://bugzilla.suse.com/1224579","tags":["report"]},{"url":"https://bugzilla.suse.com/1224581","tags":["report"]},{"url":"https://bugzilla.suse.com/1224582","tags":["report"]},{"url":"https://bugzilla.suse.com/1224586","tags":["report"]},{"url":"https://bugzilla.suse.com/1224587","tags":["report"]},{"url":"https://bugzilla.suse.com/1224598","tags":["report"]},{"url":"https://bugzilla.suse.com/1224608","tags":["report"]},{"url":"https://bugzilla.suse.com/1224611","tags":["report"]},{"url":"https://bugzilla.suse.com/1224615","tags":["report"]},{"url":"https://bugzilla.suse.com/1224617","tags":["report"]},{"url":"https://bugzilla.suse.com/1224618","tags":["report"]},{"url":"https://bugzilla.suse.com/1224622","tags":["report"]},{"url":"https://bugzilla.suse.com/1224624","tags":["report"]},{"url":"https://bugzilla.suse.com/1224627","tags":["report"]},{"url":"https://bugzilla.suse.com/1224628","tags":["report"]},{"url":"https://bugzilla.suse.com/1224629","tags":["report"]},{"url":"https://bugzilla.suse.com/1224632","tags":["report"]},{"url":"https://bugzilla.suse.com/1224636","tags":["report"]},{"url":"https://bugzilla.suse.com/1224637","tags":["report"]},{"url":"https://bugzilla.suse.com/1224638","tags":["report"]},{"url":"https://bugzilla.suse.com/1224640","tags":["report"]},{"url":"https://bugzilla.suse.com/1224643","tags":["report"]},{"url":"https://bugzilla.suse.com/1224647","tags":["report"]},{"url":"https://bugzilla.suse.com/1224649","tags":["report"]},{"url":"https://bugzilla.suse.com/1224651","tags":["report"]},{"url":"https://bugzilla.suse.com/1224657","tags":["report"]},{"url":"https://bugzilla.suse.com/1224659","tags":["report"]},{"url":"https://bugzilla.suse.com/1224660","tags":["report"]},{"url":"https://bugzilla.suse.com/1224664","tags":["report"]},{"url":"https://bugzilla.suse.com/1224665","tags":["report"]},{"url":"https://bugzilla.suse.com/1224666","tags":["report"]},{"url":"https://bugzilla.suse.com/1224667","tags":["report"]},{"url":"https://bugzilla.suse.com/1224668","tags":["report"]},{"url":"https://bugzilla.suse.com/1224672","tags":["report"]},{"url":"https://bugzilla.suse.com/1224678","tags":["report"]},{"url":"https://bugzilla.suse.com/1224679","tags":["report"]},{"url":"https://bugzilla.suse.com/1224681","tags":["report"]},{"url":"https://bugzilla.suse.com/1224685","tags":["report"]},{"url":"https://bugzilla.suse.com/1224686","tags":["report"]},{"url":"https://bugzilla.suse.com/1224692","tags":["report"]},{"url":"https://bugzilla.suse.com/1224697","tags":["report"]},{"url":"https://bugzilla.suse.com/1224699","tags":["report"]},{"url":"https://bugzilla.suse.com/1224701","tags":["report"]},{"url":"https://bugzilla.suse.com/1224703","tags":["report"]},{"url":"https://bugzilla.suse.com/1224705","tags":["report"]},{"url":"https://bugzilla.suse.com/1224707","tags":["report"]},{"url":"https://bugzilla.suse.com/1224717","tags":["report"]},{"url":"https://bugzilla.suse.com/1224718","tags":["report"]},{"url":"https://bugzilla.suse.com/1224721","tags":["report"]},{"url":"https://bugzilla.suse.com/1224722","tags":["report"]},{"url":"https://bugzilla.suse.com/1224723","tags":["report"]},{"url":"https://bugzilla.suse.com/1224727","tags":["report"]},{"url":"https://bugzilla.suse.com/1224729","tags":["report"]},{"url":"https://bugzilla.suse.com/1224730","tags":["report"]},{"url":"https://bugzilla.suse.com/1224731","tags":["report"]},{"url":"https://bugzilla.suse.com/1224732","tags":["report"]},{"url":"https://bugzilla.suse.com/1224736","tags":["report"]},{"url":"https://bugzilla.suse.com/1224739","tags":["report"]},{"url":"https://bugzilla.suse.com/1224740","tags":["report"]},{"url":"https://bugzilla.suse.com/1224763","tags":["report"]},{"url":"https://bugzilla.suse.com/1224764","tags":["report"]},{"url":"https://bugzilla.suse.com/1224765","tags":["report"]},{"url":"https://bugzilla.suse.com/1224766","tags":["report"]},{"url":"https://bugzilla.suse.com/1224794","tags":["report"]},{"url":"https://bugzilla.suse.com/1224795","tags":["report"]},{"url":"https://bugzilla.suse.com/1224796","tags":["report"]},{"url":"https://bugzilla.suse.com/1224816","tags":["report"]},{"url":"https://bugzilla.suse.com/1224895","tags":["report"]},{"url":"https://bugzilla.suse.com/1224898","tags":["report"]},{"url":"https://bugzilla.suse.com/1224900","tags":["report"]},{"url":"https://bugzilla.suse.com/1224901","tags":["report"]},{"url":"https://bugzilla.suse.com/1224902","tags":["report"]},{"url":"https://bugzilla.suse.com/1224903","tags":["report"]},{"url":"https://bugzilla.suse.com/1224905","tags":["report"]},{"url":"https://bugzilla.suse.com/1224909","tags":["report"]},{"url":"https://bugzilla.suse.com/1224910","tags":["report"]},{"url":"https://bugzilla.suse.com/1224911","tags":["report"]},{"url":"https://bugzilla.suse.com/1224912","tags":["report"]},{"url":"https://bugzilla.suse.com/1224913","tags":["report"]},{"url":"https://bugzilla.suse.com/1224914","tags":["report"]},{"url":"https://bugzilla.suse.com/1224915","tags":["report"]},{"url":"https://bugzilla.suse.com/1224920","tags":["report"]},{"url":"https://bugzilla.suse.com/1224928","tags":["report"]},{"url":"https://bugzilla.suse.com/1224929","tags":["report"]},{"url":"https://bugzilla.suse.com/1224932","tags":["report"]},{"url":"https://bugzilla.suse.com/1224936","tags":["report"]},{"url":"https://bugzilla.suse.com/1224937","tags":["report"]},{"url":"https://bugzilla.suse.com/1224941","tags":["report"]},{"url":"https://bugzilla.suse.com/1224944","tags":["report"]},{"url":"https://bugzilla.suse.com/1224945","tags":["report"]},{"url":"https://bugzilla.suse.com/1224947","tags":["report"]},{"url":"https://bugzilla.suse.com/1224988","tags":["report"]},{"url":"https://bugzilla.suse.com/1224992","tags":["report"]},{"url":"https://bugzilla.suse.com/1225000","tags":["report"]},{"url":"https://bugzilla.suse.com/1225003","tags":["report"]},{"url":"https://bugzilla.suse.com/1225005","tags":["report"]},{"url":"https://bugzilla.suse.com/1225031","tags":["report"]},{"url":"https://bugzilla.suse.com/1225032","tags":["report"]},{"url":"https://bugzilla.suse.com/1225036","tags":["report"]},{"url":"https://bugzilla.suse.com/1225041","tags":["report"]},{"url":"https://bugzilla.suse.com/1225044","tags":["report"]},{"url":"https://bugzilla.suse.com/1225053","tags":["report"]},{"url":"https://bugzilla.suse.com/1225076","tags":["report"]},{"url":"https://bugzilla.suse.com/1225077","tags":["report"]},{"url":"https://bugzilla.suse.com/1225085","tags":["report"]},{"url":"https://bugzilla.suse.com/1225095","tags":["report"]},{"url":"https://bugzilla.suse.com/1225097","tags":["report"]},{"url":"https://bugzilla.suse.com/1225106","tags":["report"]},{"url":"https://bugzilla.suse.com/1225108","tags":["report"]},{"url":"https://bugzilla.suse.com/1225109","tags":["report"]},{"url":"https://bugzilla.suse.com/1225114","tags":["report"]},{"url":"https://bugzilla.suse.com/1225118","tags":["report"]},{"url":"https://bugzilla.suse.com/1225121","tags":["report"]},{"url":"https://bugzilla.suse.com/1225122","tags":["report"]},{"url":"https://bugzilla.suse.com/1225123","tags":["report"]},{"url":"https://bugzilla.suse.com/1225125","tags":["report"]},{"url":"https://bugzilla.suse.com/1225126","tags":["report"]},{"url":"https://bugzilla.suse.com/1225127","tags":["report"]},{"url":"https://bugzilla.suse.com/1225129","tags":["report"]},{"url":"https://bugzilla.suse.com/1225131","tags":["report"]},{"url":"https://bugzilla.suse.com/1225138","tags":["report"]},{"url":"https://bugzilla.suse.com/1225139","tags":["report"]},{"url":"https://bugzilla.suse.com/1225145","tags":["report"]},{"url":"https://bugzilla.suse.com/1225156","tags":["report"]},{"url":"https://bugzilla.suse.com/1225158","tags":["report"]},{"url":"https://bugzilla.suse.com/1225160","tags":["report"]},{"url":"https://bugzilla.suse.com/1225161","tags":["report"]},{"url":"https://bugzilla.suse.com/1225167","tags":["report"]},{"url":"https://bugzilla.suse.com/1225180","tags":["report"]},{"url":"https://bugzilla.suse.com/1225183","tags":["report"]},{"url":"https://bugzilla.suse.com/1225184","tags":["report"]},{"url":"https://bugzilla.suse.com/1225186","tags":["report"]},{"url":"https://bugzilla.suse.com/1225187","tags":["report"]},{"url":"https://bugzilla.suse.com/1225190","tags":["report"]},{"url":"https://bugzilla.suse.com/1225191","tags":["report"]},{"url":"https://bugzilla.suse.com/1225195","tags":["report"]},{"url":"https://bugzilla.suse.com/1225203","tags":["report"]},{"url":"https://bugzilla.suse.com/1225205","tags":["report"]},{"url":"https://bugzilla.suse.com/1225206","tags":["report"]},{"url":"https://bugzilla.suse.com/1225209","tags":["report"]},{"url":"https://bugzilla.suse.com/1225210","tags":["report"]},{"url":"https://bugzilla.suse.com/1225214","tags":["report"]},{"url":"https://bugzilla.suse.com/1225223","tags":["report"]},{"url":"https://bugzilla.suse.com/1225224","tags":["report"]},{"url":"https://bugzilla.suse.com/1225225","tags":["report"]},{"url":"https://bugzilla.suse.com/1225227","tags":["report"]},{"url":"https://bugzilla.suse.com/1225228","tags":["report"]},{"url":"https://bugzilla.suse.com/1225229","tags":["report"]},{"url":"https://bugzilla.suse.com/1225232","tags":["report"]},{"url":"https://bugzilla.suse.com/1225233","tags":["report"]},{"url":"https://bugzilla.suse.com/1225235","tags":["report"]},{"url":"https://bugzilla.suse.com/1225236","tags":["report"]},{"url":"https://bugzilla.suse.com/1225237","tags":["report"]},{"url":"https://bugzilla.suse.com/1225238","tags":["report"]},{"url":"https://bugzilla.suse.com/1225239","tags":["report"]},{"url":"https://bugzilla.suse.com/1225240","tags":["report"]},{"url":"https://bugzilla.suse.com/1225241","tags":["report"]},{"url":"https://bugzilla.suse.com/1225243","tags":["report"]},{"url":"https://bugzilla.suse.com/1225245","tags":["report"]},{"url":"https://bugzilla.suse.com/1225246","tags":["report"]},{"url":"https://bugzilla.suse.com/1225248","tags":["report"]},{"url":"https://bugzilla.suse.com/1225249","tags":["report"]},{"url":"https://bugzilla.suse.com/1225250","tags":["report"]},{"url":"https://bugzilla.suse.com/1225253","tags":["report"]},{"url":"https://bugzilla.suse.com/1225254","tags":["report"]},{"url":"https://bugzilla.suse.com/1225255","tags":["report"]},{"url":"https://bugzilla.suse.com/1225257","tags":["report"]},{"url":"https://bugzilla.suse.com/1225258","tags":["report"]},{"url":"https://bugzilla.suse.com/1225259","tags":["report"]},{"url":"https://bugzilla.suse.com/1225260","tags":["report"]},{"url":"https://bugzilla.suse.com/1225261","tags":["report"]},{"url":"https://bugzilla.suse.com/1225262","tags":["report"]},{"url":"https://bugzilla.suse.com/1225263","tags":["report"]},{"url":"https://bugzilla.suse.com/1225268","tags":["report"]},{"url":"https://bugzilla.suse.com/1225301","tags":["report"]},{"url":"https://bugzilla.suse.com/1225304","tags":["report"]},{"url":"https://bugzilla.suse.com/1225306","tags":["report"]},{"url":"https://bugzilla.suse.com/1225316","tags":["report"]},{"url":"https://bugzilla.suse.com/1225320","tags":["report"]},{"url":"https://bugzilla.suse.com/1225321","tags":["report"]},{"url":"https://bugzilla.suse.com/1225323","tags":["report"]},{"url":"https://bugzilla.suse.com/1225326","tags":["report"]},{"url":"https://bugzilla.suse.com/1225327","tags":["report"]},{"url":"https://bugzilla.suse.com/1225328","tags":["report"]},{"url":"https://bugzilla.suse.com/1225331","tags":["report"]},{"url":"https://bugzilla.suse.com/1225332","tags":["report"]},{"url":"https://bugzilla.suse.com/1225333","tags":["report"]},{"url":"https://bugzilla.suse.com/1225334","tags":["report"]},{"url":"https://bugzilla.suse.com/1225335","tags":["report"]},{"url":"https://bugzilla.suse.com/1225337","tags":["report"]},{"url":"https://bugzilla.suse.com/1225338","tags":["report"]},{"url":"https://bugzilla.suse.com/1225339","tags":["report"]},{"url":"https://bugzilla.suse.com/1225341","tags":["report"]},{"url":"https://bugzilla.suse.com/1225342","tags":["report"]},{"url":"https://bugzilla.suse.com/1225344","tags":["report"]},{"url":"https://bugzilla.suse.com/1225346","tags":["report"]},{"url":"https://bugzilla.suse.com/1225353","tags":["report"]},{"url":"https://bugzilla.suse.com/1225357","tags":["report"]},{"url":"https://bugzilla.suse.com/1225358","tags":["report"]},{"url":"https://bugzilla.suse.com/1225361","tags":["report"]},{"url":"https://bugzilla.suse.com/1225368","tags":["report"]},{"url":"https://bugzilla.suse.com/1225369","tags":["report"]},{"url":"https://bugzilla.suse.com/1225370","tags":["report"]},{"url":"https://bugzilla.suse.com/1225372","tags":["report"]},{"url":"https://bugzilla.suse.com/1225373","tags":["report"]},{"url":"https://bugzilla.suse.com/1225374","tags":["report"]},{"url":"https://bugzilla.suse.com/1225375","tags":["report"]},{"url":"https://bugzilla.suse.com/1225376","tags":["report"]},{"url":"https://bugzilla.suse.com/1225377","tags":["report"]},{"url":"https://bugzilla.suse.com/1225379","tags":["report"]},{"url":"https://bugzilla.suse.com/1225380","tags":["report"]},{"url":"https://bugzilla.suse.com/1225382","tags":["report"]},{"url":"https://bugzilla.suse.com/1225383","tags":["report"]},{"url":"https://bugzilla.suse.com/1225386","tags":["report"]},{"url":"https://bugzilla.suse.com/1225387","tags":["report"]},{"url":"https://bugzilla.suse.com/1225388","tags":["report"]},{"url":"https://bugzilla.suse.com/1225392","tags":["report"]},{"url":"https://bugzilla.suse.com/1225393","tags":["report"]},{"url":"https://bugzilla.suse.com/1225396","tags":["report"]},{"url":"https://bugzilla.suse.com/1225400","tags":["report"]},{"url":"https://bugzilla.suse.com/1225405","tags":["report"]},{"url":"https://bugzilla.suse.com/1225408","tags":["report"]},{"url":"https://bugzilla.suse.com/1225410","tags":["report"]},{"url":"https://bugzilla.suse.com/1225424","tags":["report"]},{"url":"https://bugzilla.suse.com/1225425","tags":["report"]},{"url":"https://bugzilla.suse.com/1225427","tags":["report"]},{"url":"https://bugzilla.suse.com/1225431","tags":["report"]},{"url":"https://bugzilla.suse.com/1225435","tags":["report"]},{"url":"https://bugzilla.suse.com/1225436","tags":["report"]},{"url":"https://bugzilla.suse.com/1225437","tags":["report"]},{"url":"https://bugzilla.suse.com/1225439","tags":["report"]},{"url":"https://bugzilla.suse.com/1225441","tags":["report"]},{"url":"https://bugzilla.suse.com/1225442","tags":["report"]},{"url":"https://bugzilla.suse.com/1225443","tags":["report"]},{"url":"https://bugzilla.suse.com/1225444","tags":["report"]},{"url":"https://bugzilla.suse.com/1225445","tags":["report"]},{"url":"https://bugzilla.suse.com/1225446","tags":["report"]},{"url":"https://bugzilla.suse.com/1225447","tags":["report"]},{"url":"https://bugzilla.suse.com/1225450","tags":["report"]},{"url":"https://bugzilla.suse.com/1225455","tags":["report"]},{"url":"https://bugzilla.suse.com/1225461","tags":["report"]},{"url":"https://bugzilla.suse.com/1225463","tags":["report"]},{"url":"https://bugzilla.suse.com/1225464","tags":["report"]},{"url":"https://bugzilla.suse.com/1225466","tags":["report"]},{"url":"https://bugzilla.suse.com/1225467","tags":["report"]},{"url":"https://bugzilla.suse.com/1225468","tags":["report"]},{"url":"https://bugzilla.suse.com/1225471","tags":["report"]},{"url":"https://bugzilla.suse.com/1225472","tags":["report"]},{"url":"https://bugzilla.suse.com/1225478","tags":["report"]},{"url":"https://bugzilla.suse.com/1225480","tags":["report"]},{"url":"https://bugzilla.suse.com/1225483","tags":["report"]},{"url":"https://bugzilla.suse.com/1225486","tags":["report"]},{"url":"https://bugzilla.suse.com/1225488","tags":["report"]},{"url":"https://bugzilla.suse.com/1225490","tags":["report"]},{"url":"https://bugzilla.suse.com/1225492","tags":["report"]},{"url":"https://bugzilla.suse.com/1225495","tags":["report"]},{"url":"https://bugzilla.suse.com/1225499","tags":["report"]},{"url":"https://bugzilla.suse.com/1225500","tags":["report"]},{"url":"https://bugzilla.suse.com/1225501","tags":["report"]},{"url":"https://bugzilla.suse.com/1225502","tags":["report"]},{"url":"https://bugzilla.suse.com/1225508","tags":["report"]},{"url":"https://bugzilla.suse.com/1225510","tags":["report"]},{"url":"https://bugzilla.suse.com/1225513","tags":["report"]},{"url":"https://bugzilla.suse.com/1225515","tags":["report"]},{"url":"https://bugzilla.suse.com/1225529","tags":["report"]},{"url":"https://bugzilla.suse.com/1225530","tags":["report"]},{"url":"https://bugzilla.suse.com/1225532","tags":["report"]},{"url":"https://bugzilla.suse.com/1225534","tags":["report"]},{"url":"https://bugzilla.suse.com/1225535","tags":["report"]},{"url":"https://bugzilla.suse.com/1225548","tags":["report"]},{"url":"https://bugzilla.suse.com/1225550","tags":["report"]},{"url":"https://bugzilla.suse.com/1225553","tags":["report"]},{"url":"https://bugzilla.suse.com/1225554","tags":["report"]},{"url":"https://bugzilla.suse.com/1225555","tags":["report"]},{"url":"https://bugzilla.suse.com/1225556","tags":["report"]},{"url":"https://bugzilla.suse.com/1225557","tags":["report"]},{"url":"https://bugzilla.suse.com/1225559","tags":["report"]},{"url":"https://bugzilla.suse.com/1225565","tags":["report"]},{"url":"https://bugzilla.suse.com/1225566","tags":["report"]},{"url":"https://bugzilla.suse.com/1225568","tags":["report"]},{"url":"https://bugzilla.suse.com/1225569","tags":["report"]},{"url":"https://bugzilla.suse.com/1225570","tags":["report"]},{"url":"https://bugzilla.suse.com/1225571","tags":["report"]},{"url":"https://bugzilla.suse.com/1225577","tags":["report"]},{"url":"https://bugzilla.suse.com/1225583","tags":["report"]},{"url":"https://bugzilla.suse.com/1225584","tags":["report"]},{"url":"https://bugzilla.suse.com/1225587","tags":["report"]},{"url":"https://bugzilla.suse.com/1225588","tags":["report"]},{"url":"https://bugzilla.suse.com/1225589","tags":["report"]},{"url":"https://bugzilla.suse.com/1225590","tags":["report"]},{"url":"https://bugzilla.suse.com/1225591","tags":["report"]},{"url":"https://bugzilla.suse.com/1225592","tags":["report"]},{"url":"https://bugzilla.suse.com/1225593","tags":["report"]},{"url":"https://bugzilla.suse.com/1225595","tags":["report"]},{"url":"https://bugzilla.suse.com/1225599","tags":["report"]},{"url":"https://bugzilla.suse.com/1225616","tags":["report"]},{"url":"https://bugzilla.suse.com/1225642","tags":["report"]},{"url":"https://bugzilla.suse.com/1225705","tags":["report"]},{"url":"https://bugzilla.suse.com/1225715","tags":["report"]},{"url":"https://bugzilla.suse.com/1225720","tags":["report"]},{"url":"https://bugzilla.suse.com/1225722","tags":["report"]},{"url":"https://bugzilla.suse.com/1225734","tags":["report"]},{"url":"https://bugzilla.suse.com/1225735","tags":["report"]},{"url":"https://bugzilla.suse.com/1225747","tags":["report"]},{"url":"https://bugzilla.suse.com/1225748","tags":["report"]},{"url":"https://bugzilla.suse.com/1225756","tags":["report"]},{"url":"https://bugzilla.suse.com/1225761","tags":["report"]},{"url":"https://bugzilla.suse.com/1225766","tags":["report"]},{"url":"https://bugzilla.suse.com/1225775","tags":["report"]},{"url":"https://bugzilla.suse.com/1225810","tags":["report"]},{"url":"https://bugzilla.suse.com/1225820","tags":["report"]},{"url":"https://bugzilla.suse.com/1225829","tags":["report"]},{"url":"https://bugzilla.suse.com/1225835","tags":["report"]},{"url":"https://bugzilla.suse.com/1225842","tags":["report"]},{"url":"https://www.suse.com/security/cve/CVE-2020-36788","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-39698","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-4148","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-42327","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-43056","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-43527","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-47200","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-47358","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-47359","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-47360","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-47363","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-47364","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-47365","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-47366","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-47367","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-47368","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-47370","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-47371","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-47372","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-47373","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-47374","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-47376","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-47379","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-47380","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-47381","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-47384","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-47385","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-47386","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-47387","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-47388","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-47389","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-47390","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-47392","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-47393","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-47394","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-47395","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-47396","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-47398","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-47399","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-47402","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-47403","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-47405","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-47406","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-47407","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-47408","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-47410","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-47412","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-47413","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-47414","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-47415","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-47417","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-47418","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-47419","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-47420","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-47421","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-47422","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-47425","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-47426","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-47427","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-47428","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-47429","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-47430","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-47433","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-47434","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-47437","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-47438","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-47439","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-47440","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-47441","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-47442","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-47443","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-47444","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-47445","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-47446","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-47447","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-47448","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-47449","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-47450","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-47451","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-47452","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-47453","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-47454","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-47455","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-47457","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-47459","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-47461","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-47462","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-47463","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-47464","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-47465","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-47466","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-47467","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-47468","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-47470","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-47471","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-47474","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-47475","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-47476","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-47477","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-47479","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-47481","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-47482","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-47484","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-47486","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-47488","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-47489","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-47490","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-47491","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-47492","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-47493","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-47494","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-47498","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-47499","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-47501","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-47502","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-47503","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-47504","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-47505","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-47507","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-47508","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-47510","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-47512","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-47513","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-47514","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-47516","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-47518","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-47520","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-47521","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-47522","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-47524","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-47525","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-47526","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-47528","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-47529","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-47530","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-47531","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-47532","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-47533","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-47534","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-47535","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-47536","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-47537","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-47540","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-47542","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-47544","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-47549","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-47550","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-47551","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-47552","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-47553","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-47554","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-47555","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-47556","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-47557","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-47558","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-47559","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-47560","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-47562","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-47563","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-47564","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-47569","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-48633","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-48662","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-48669","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-48689","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-48691","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-48699","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-48705","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-48709","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-52618","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-52642","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-52643","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-52644","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-52650","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-52654","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-52656","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-52657","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-52659","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-52660","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-52661","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-52662","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-52669","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-52671","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-52674","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-52676","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-52678","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-52679","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-52680","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-52683","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-52690","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-52692","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-52693","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-52694","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-52699","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-52702","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-52705","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-52707","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-52708","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-52731","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-52733","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-52736","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-52738","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-52739","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-52740","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-52743","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-52744","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-52745","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-52746","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-52753","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-52754","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-52756","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-52757","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-52763","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-52764","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-52766","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-52773","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-52777","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-52788","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-52789","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-52791","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-52795","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-52798","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-52799","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-52800","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-52804","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-52805","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-52806","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-52807","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-52808","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-52809","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-52810","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-52811","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-52814","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-52815","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-52816","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-52817","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-52818","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-52819","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-52825","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-52826","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-52832","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-52833","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-52834","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-52838","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-52840","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-52841","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-52844","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-52847","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-52851","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-52853","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-52854","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-52855","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-52856","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-52858","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-52860","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-52861","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-52868","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-52870","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-52871","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-52872","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-52873","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-52876","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-52877","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-52878","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-6531","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-2201","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-26597","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-26643","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-26679","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-26692","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-26698","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-26700","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-26715","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-26742","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-26748","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-26758","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-26764","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-26777","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-26778","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-26788","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-26801","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-26822","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-26829","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-26838","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-26839","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-26840","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-26859","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-26870","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-26877","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-26880","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-26889","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-26894","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-26907","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-26916","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-26919","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-26922","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-26925","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-26928","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-26933","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-26935","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-26937","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-26938","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-26939","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-26940","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-26943","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-26964","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-26974","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-26977","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-26979","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-26988","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-26989","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-26994","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-26997","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-26999","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-27000","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-27001","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-27004","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-27028","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-27037","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-27042","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-27045","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-27047","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-27051","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-27052","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-27053","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-27072","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-27073","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-27074","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-27075","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-27076","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-27077","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-27078","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-27393","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-27395","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-27399","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-27400","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-27405","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-27410","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-27412","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-27413","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-27416","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-27417","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-27431","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-27435","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-35796","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-35799","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-35801","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-35804","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-35806","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-35812","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-35813","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-35815","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-35817","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-35821","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-35822","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-35823","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-35825","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-35828","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-35829","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-35833","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-35845","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-35847","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-35851","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-35852","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-35854","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-35860","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-35861","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-35862","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-35863","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-35864","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-35865","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-35866","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-35867","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-35868","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-35869","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-35870","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-35872","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-35875","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-35879","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-35885","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-35901","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-35904","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-35905","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-35907","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-35912","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-35915","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-35922","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-35924","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-35930","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-35933","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-35938","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-35939","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-35940","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-35943","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-35947","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-35950","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-35951","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-35952","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-35959","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-35963","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-35964","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-35965","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-35966","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-35967","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-35973","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-35976","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-35978","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-35989","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-35990","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-35998","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-35999","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-36006","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-36007","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-36012","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-36014","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-36016","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-36026","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-36032","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-36880","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-36893","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-36896","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-36897","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-36906","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-36918","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-36924","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-36926","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-36928","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-36931","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-36938","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-36940","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-36941","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-36942","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-36944","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-36947","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-36950","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-36952","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-36955","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-36959","tags":["web"]},{"url":"https://www.suse.com/support/update/announcement/2024/suse-su-20242010-1/","tags":["advisory"]},{"url":"https://bugzilla.suse.com/1151927","tags":["report"]},{"url":"https://bugzilla.suse.com/1152472","tags":["report"]},{"url":"https://bugzilla.suse.com/1154353","tags":["report"]},{"url":"https://bugzilla.suse.com/1156395","tags":["report"]},{"url":"https://bugzilla.suse.com/1176447","tags":["report"]},{"url":"https://bugzilla.suse.com/1176774","tags":["report"]},{"url":"https://bugzilla.suse.com/1176869","tags":["report"]},{"url":"https://bugzilla.suse.com/1178134","tags":["report"]},{"url":"https://bugzilla.suse.com/1181147","tags":["report"]},{"url":"https://bugzilla.suse.com/1184631","tags":["report"]},{"url":"https://bugzilla.suse.com/1185589","tags":["report"]},{"url":"https://bugzilla.suse.com/1186885","tags":["report"]},{"url":"https://bugzilla.suse.com/1188772","tags":["report"]},{"url":"https://bugzilla.suse.com/1189883","tags":["report"]},{"url":"https://bugzilla.suse.com/1198029","tags":["report"]},{"url":"https://bugzilla.suse.com/1199304","tags":["report"]},{"url":"https://bugzilla.suse.com/1200619","tags":["report"]},{"url":"https://bugzilla.suse.com/1203389","tags":["report"]},{"url":"https://bugzilla.suse.com/1210629","tags":["report"]},{"url":"https://bugzilla.suse.com/1213476","tags":["report"]},{"url":"https://bugzilla.suse.com/1215420","tags":["report"]},{"url":"https://bugzilla.suse.com/1220137","tags":["report"]},{"url":"https://bugzilla.suse.com/1220144","tags":["report"]},{"url":"https://bugzilla.suse.com/1220754","tags":["report"]},{"url":"https://bugzilla.suse.com/1220877","tags":["report"]},{"url":"https://bugzilla.suse.com/1220960","tags":["report"]},{"url":"https://bugzilla.suse.com/1221113","tags":["report"]},{"url":"https://bugzilla.suse.com/1222251","tags":["report"]},{"url":"https://bugzilla.suse.com/1222867","tags":["report"]},{"url":"https://bugzilla.suse.com/1223934","tags":["report"]},{"url":"https://bugzilla.suse.com/1224826","tags":["report"]},{"url":"https://bugzilla.suse.com/1224832","tags":["report"]},{"url":"https://bugzilla.suse.com/1224842","tags":["report"]},{"url":"https://bugzilla.suse.com/1224843","tags":["report"]},{"url":"https://bugzilla.suse.com/1224852","tags":["report"]},{"url":"https://bugzilla.suse.com/1224853","tags":["report"]},{"url":"https://bugzilla.suse.com/1224886","tags":["report"]},{"url":"https://bugzilla.suse.com/1224891","tags":["report"]},{"url":"https://bugzilla.suse.com/1224923","tags":["report"]},{"url":"https://bugzilla.suse.com/1224924","tags":["report"]},{"url":"https://bugzilla.suse.com/1224953","tags":["report"]},{"url":"https://bugzilla.suse.com/1224955","tags":["report"]},{"url":"https://bugzilla.suse.com/1224965","tags":["report"]},{"url":"https://bugzilla.suse.com/1224984","tags":["report"]},{"url":"https://bugzilla.suse.com/1224993","tags":["report"]},{"url":"https://bugzilla.suse.com/1224997","tags":["report"]},{"url":"https://bugzilla.suse.com/1225083","tags":["report"]},{"url":"https://bugzilla.suse.com/1225091","tags":["report"]},{"url":"https://bugzilla.suse.com/1225113","tags":["report"]},{"url":"https://bugzilla.suse.com/1225140","tags":["report"]},{"url":"https://bugzilla.suse.com/1225148","tags":["report"]},{"url":"https://bugzilla.suse.com/1225178","tags":["report"]},{"url":"https://bugzilla.suse.com/1225181","tags":["report"]},{"url":"https://bugzilla.suse.com/1225448","tags":["report"]},{"url":"https://www.suse.com/security/cve/CVE-2021-3743","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-47104","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-47192","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-47227","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-47228","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-47230","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-47240","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-47241","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-47253","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-47255","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-47259","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-47263","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-47267","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-47270","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-47275","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-47289","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-47296","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-47329","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-47332","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-47333","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-47338","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-47340","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-47341","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-47348","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-47350","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-47354","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-47538","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-1195","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-20132","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-48673","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-2176","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-4244","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-52433","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-52581","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-26581","tags":["web"]},{"url":"https://www.suse.com/support/update/announcement/2024/suse-su-20242011-1/","tags":["advisory"]},{"url":"https://bugzilla.suse.com/1196869","tags":["report"]},{"url":"https://bugzilla.suse.com/1200313","tags":["report"]},{"url":"https://bugzilla.suse.com/1201308","tags":["report"]},{"url":"https://bugzilla.suse.com/1201489","tags":["report"]},{"url":"https://bugzilla.suse.com/1211592","tags":["report"]},{"url":"https://bugzilla.suse.com/1220492","tags":["report"]},{"url":"https://bugzilla.suse.com/1221645","tags":["report"]},{"url":"https://bugzilla.suse.com/1221958","tags":["report"]},{"url":"https://bugzilla.suse.com/1223057","tags":["report"]},{"url":"https://bugzilla.suse.com/1223111","tags":["report"]},{"url":"https://bugzilla.suse.com/1223191","tags":["report"]},{"url":"https://bugzilla.suse.com/1223481","tags":["report"]},{"url":"https://bugzilla.suse.com/1223501","tags":["report"]},{"url":"https://bugzilla.suse.com/1223520","tags":["report"]},{"url":"https://bugzilla.suse.com/1223894","tags":["report"]},{"url":"https://bugzilla.suse.com/1223921","tags":["report"]},{"url":"https://bugzilla.suse.com/1223924","tags":["report"]},{"url":"https://bugzilla.suse.com/1223929","tags":["report"]},{"url":"https://bugzilla.suse.com/1223941","tags":["report"]},{"url":"https://bugzilla.suse.com/1223952","tags":["report"]},{"url":"https://bugzilla.suse.com/1223953","tags":["report"]},{"url":"https://bugzilla.suse.com/1223957","tags":["report"]},{"url":"https://bugzilla.suse.com/1223962","tags":["report"]},{"url":"https://bugzilla.suse.com/1223963","tags":["report"]},{"url":"https://bugzilla.suse.com/1223964","tags":["report"]},{"url":"https://bugzilla.suse.com/1224085","tags":["report"]},{"url":"https://www.suse.com/security/cve/CVE-2022-48632","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-48634","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-48652","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-48671","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-48675","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-48687","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-48688","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-48692","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-48693","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-48694","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-48695","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-48700","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-48701","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-48703","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-26852","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-26862","tags":["web"]},{"url":"https://www.suse.com/support/update/announcement/2024/suse-su-20242019-1/","tags":["advisory"]},{"url":"https://www.suse.com/support/update/announcement/2024/suse-su-20242183-1/","tags":["advisory"]},{"url":"https://bugzilla.suse.com/1208813","tags":["report"]},{"url":"https://bugzilla.suse.com/1215356","tags":["report"]},{"url":"https://www.suse.com/support/update/announcement/2024/suse-su-20242184-1/","tags":["advisory"]},{"url":"https://bugzilla.suse.com/1223062","tags":["report"]},{"url":"https://www.suse.com/support/update/announcement/2024/suse-su-20242185-1/","tags":["advisory"]},{"url":"https://bugzilla.suse.com/1185570","tags":["report"]},{"url":"https://bugzilla.suse.com/1187357","tags":["report"]},{"url":"https://www.suse.com/support/update/announcement/2024/suse-su-20242189-1/","tags":["advisory"]},{"url":"https://www.suse.com/security/cve/CVE-2023-2860","tags":["web"]},{"url":"https://www.suse.com/support/update/announcement/2024/suse-su-20242190-1/","tags":["advisory"]},{"url":"https://ubuntu.com/security/CVE-2021-47382","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2021-47382","tags":["report"]},{"url":"https://git.kernel.org/linus/d2b59bd4b06d84a4eadb520b0f71c62fe8ec0a62","tags":["report"]}],"sources":{"cve":[{"id":"CVE-2021-47382","title":"s390/qeth: fix deadlock during failing recovery","description":"In the Linux kernel, the following vulnerability has been resolved:\n\ns390/qeth: fix deadlock during failing recovery\n\nCommit 0b9902c1fcc5 (\"s390/qeth: fix deadlock during recovery\") removed\ntaking discipline_mutex inside qeth_do_reset(), fixing potential\ndeadlocks. An error path was missed though, that still takes\ndiscipline_mutex and thus has the original deadlock potential.\n\nIntermittent deadlocks were seen when a qeth channel path is configured\noffline, causing a race between qeth_do_reset and ccwgroup_remove.\nCall qeth_set_offline() directly in the qeth_do_reset() error case and\nthen a new variant of ccwgroup_set_offline(), without taking\ndiscipline_mutex.","status":"published","published":"2024-05-21T15:03:43.621Z","modified":"2026-05-23T15:19:52.681Z","updated_at":"2026-11-02T14:32:55.905855Z"}],"euvd":[{"id":"EUVD-2021-34387","description":"In the Linux kernel, the following vulnerability has been resolved:\n\ns390/qeth: fix deadlock during failing recovery\n\nCommit 0b9902c1fcc5 (\"s390/qeth: fix deadlock during recovery\") removed\ntaking discipline_mutex inside qeth_do_reset(), fixing potential\ndeadlocks. An error path was missed though, that still takes\ndiscipline_mutex and thus has the original deadlock potential.\n\nIntermittent deadlocks were seen when a qeth channel path is configured\noffline, causing a race between qeth_do_reset and ccwgroup_remove.\nCall qeth_set_offline() directly in the qeth_do_reset() error case and\nthen a new variant of ccwgroup_set_offline(), without taking\ndiscipline_mutex.","status":"published","published":"2024-05-21T15:03:43Z","modified":"2026-05-23T15:19:52Z","updated_at":"2026-11-02T18:21:12.112235Z"}],"ghsa":[{"id":"GHSA-q77h-85v7-m3mw","title":"In the Linux kernel, the following vulnerability has been resolved:\n\ns390/qeth: fix deadlock...","description":"In the Linux kernel, the following vulnerability has been resolved:\n\ns390/qeth: fix deadlock during failing recovery\n\nCommit 0b9902c1fcc5 (\"s390/qeth: fix deadlock during recovery\") removed\ntaking discipline_mutex inside qeth_do_reset(), fixing potential\ndeadlocks. An error path was missed though, that still takes\ndiscipline_mutex and thus has the original deadlock potential.\n\nIntermittent deadlocks were seen when a qeth channel path is configured\noffline, causing a race between qeth_do_reset and ccwgroup_remove.\nCall qeth_set_offline() directly in the qeth_do_reset() error case and\nthen a new variant of ccwgroup_set_offline(), without taking\ndiscipline_mutex.","status":"published","published":"2024-05-21T15:31:44Z","modified":"2024-12-23T21:31:56Z","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-362"],"updated_at":"2026-11-02T14:59:15.851629Z"}],"nvd":[{"id":"CVE-2021-47382","description":"In the Linux kernel, the following vulnerability has been resolved:\n\ns390/qeth: fix deadlock during failing recovery\n\nCommit 0b9902c1fcc5 (\"s390/qeth: fix deadlock during recovery\") removed\ntaking discipline_mutex inside qeth_do_reset(), fixing potential\ndeadlocks. An error path was missed though, that still takes\ndiscipline_mutex and thus has the original deadlock potential.\n\nIntermittent deadlocks were seen when a qeth channel path is configured\noffline, causing a race between qeth_do_reset and ccwgroup_remove.\nCall qeth_set_offline() directly in the qeth_do_reset() error case and\nthen a new variant of ccwgroup_set_offline(), without taking\ndiscipline_mutex.","status":"published","published":"2024-05-21T15:15:23.803Z","modified":"2026-06-17T04:17:20.463Z","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","assessor":"primary"}],"cwes":["CWE-362","CWE-667"],"updated_at":"2026-11-02T14:07:08.629518Z"}],"osv":[{"id":"CVE-2021-47382","description":"In the Linux kernel, the following vulnerability has been resolved:\n\ns390/qeth: fix deadlock during failing recovery\n\nCommit 0b9902c1fcc5 (\"s390/qeth: fix deadlock during recovery\") removed\ntaking discipline_mutex inside qeth_do_reset(), fixing potential\ndeadlocks. An error path was missed though, that still takes\ndiscipline_mutex and thus has the original deadlock potential.\n\nIntermittent deadlocks were seen when a qeth channel path is configured\noffline, causing a race between qeth_do_reset and ccwgroup_remove.\nCall qeth_set_offline() directly in the qeth_do_reset() error case and\nthen a new variant of ccwgroup_set_offline(), without taking\ndiscipline_mutex.","status":"published","published":"2024-05-21T15:15:23.803Z","modified":"2026-03-14T11:19:09.35857Z","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:44:22.470367Z"},{"id":"DEBIAN-CVE-2021-47382","description":"In the Linux kernel, the following vulnerability has been resolved:  s390/qeth: fix deadlock during failing recovery  Commit 0b9902c1fcc5 (\"s390/qeth: fix deadlock during recovery\") removed taking discipline_mutex inside qeth_do_reset(), fixing potential deadlocks. An error path was missed though, that still takes discipline_mutex and thus has the original deadlock potential.  Intermittent deadlocks were seen when a qeth channel path is configured offline, causing a race between qeth_do_reset and ccwgroup_remove. Call qeth_set_offline() directly in the qeth_do_reset() error case and then a new variant of ccwgroup_set_offline(), without taking discipline_mutex.","status":"published","published":"2024-05-21T15:15:23.803Z","modified":"2026-10-23T18:05:06.853277403Z","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:36.081807Z"},{"id":"OESA-2024-1962","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\ns390/qeth: fix deadlock during failing recovery\r\n\r\nCommit 0b9902c1fcc5 (\u0026quot;s390/qeth: fix deadlock during recovery\u0026quot;) removed\ntaking discipline_mutex inside qeth_do_reset(), fixing potential\ndeadlocks. An error path was missed though, that still takes\ndiscipline_mutex and thus has the original deadlock potential.\r\n\r\nIntermittent deadlocks were seen when a qeth channel path is configured\noffline, causing a race between qeth_do_reset and ccwgroup_remove.\nCall qeth_set_offline() directly in the qeth_do_reset() error case and\nthen a new variant of ccwgroup_set_offline(), without taking\ndiscipline_mutex.(CVE-2021-47382)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nNFSD: Fix the behavior of READ near OFFSET_MAX\r\n\r\nDan Aloni reports:\n\u0026gt; Due to commit 8cfb9015280d (\u0026quot;NFS: Always provide aligned buffers to\n\u0026gt; the RPC read layers\u0026quot;) on the client, a read of 0xfff is aligned up\n\u0026gt; to server rsize of 0x1000.\n\u0026gt;\n\u0026gt; As a result, in a test where the server has a file of size\n\u0026gt; 0x7fffffffffffffff, and the client tries to read from the offset\n\u0026gt; 0x7ffffffffffff000, the read causes loff_t overflow in the server\n\u0026gt; and it returns an NFS code of EINVAL to the client. The client as\n\u0026gt; a result indefinitely retries the request.\r\n\r\nThe Linux NFS client does not handle NFS?ERR_INVAL, even though all\nNFS specifications permit servers to return that status code for a\nREAD.\r\n\r\nInstead of NFS?ERR_INVAL, have out-of-range READ requests succeed\nand return a short result. Set the EOF flag in the result to prevent\nthe client from retrying the READ request. This behavior appears to\nbe consistent with Solaris NFS servers.\r\n\r\nNote that NFSv3 and NFSv4 use u64 offset values on the wire. These\nmust be converted to loff_t internally before use -- an implicit\ntype cast is not adequate for this purpose. Otherwise VFS checks\nagainst sb-\u0026gt;s_maxbytes do not work properly.(CVE-2022-48827)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nnet: can: j1939: enhanced error handling for tightly received RTS messages in xtp_rx_rts_session_new\r\n\r\nThis patch enhances error handling in scenarios with RTS (Request to\nSend) messages arriving closely. It replaces the less informative WARN_ON_ONCE\nbacktraces with a new error handling method. This provides clearer error\nmessages and allows for the early termination of problematic sessions.\nPreviously, sessions were only released at the end of j1939_xtp_rx_rts().\r\n\r\nPotentially this could be reproduced with something like:\ntestj1939 -r vcan0:0x80 \u0026amp;\nwhile true; do\n\t# send first RTS\n\tcansend vcan0 18EC8090#1014000303002301;\n\t# send second RTS\n\tcansend vcan0 18EC8090#1014000303002301;\n\t# send abort\n\tcansend vcan0 18EC8090#ff00000000002301;\ndone(CVE-2023-52887)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nipvlan: Dont Use skb-\u0026gt;sk in ipvlan_process_v{4,6}_outbound\r\n\r\nRaw packet from PF_PACKET socket ontop of an IPv6-backed ipvlan device will\nhit WARN_ON_ONCE() in sk_mc_loop() through sch_direct_xmit() path.\r\n\r\nWARNING: CPU: 2 PID: 0 at net/core/sock.c:775 sk_mc_loop+0x2d/0x70\nModules linked in: sch_netem ipvlan rfkill cirrus drm_shmem_helper sg drm_kms_helper\nCPU: 2 PID: 0 Comm: swapper/2 Kdump: loaded Not tainted 6.9.0+ #279\nHardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.15.0-1 04/01/2014\nRIP: 0010:sk_mc_loop+0x2d/0x70\nCode: fa 0f 1f 44 00 00 65 0f b7 15 f7 96 a3 4f 31 c0 66 85 d2 75 26 48 85 ff 74 1c\nRSP: 0018:ffffa9584015cd78 EFLAGS: 00010212\nRAX: 0000000000000011 RBX: ffff91e585793e00 RCX: 0000000002c6a001\nRDX: 0000000000000000 RSI: 0000000000000040 RDI: ffff91e589c0f000\nRBP: ffff91e5855bd100 R08: 0000000000000000 R09: 3d00545216f43d00\nR10: ffff91e584fdcc50 R11: 00000060dd8616f4 R12: ffff91e58132d000\nR13: ffff91e584fdcc68 R14: ffff91e5869ce800 R15: ffff91e589c0f000\nFS:  0000000000000000(0000) GS:ffff91e898100000(0000) knlGS:0000000000000000\nCS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033\nCR2: 00007f788f7c44c0 CR3: 0000000008e1a000 CR4: 00000000000006f0\nDR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000\nDR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400\nCall Trace:\n\u0026lt;IRQ\u0026gt;\n ? __warn (kernel/panic.c:693)\n ? sk_mc_loop (net/core/sock.c:760)\n ? report_bug (lib/bug.c:201 lib/bug.c:219)\n ? handle_bug (arch/x86/kernel/traps.c:239)\n ? exc_invalid_op (arch/x86/kernel/traps.c:260 (discriminator 1))\n ? asm_exc_invalid_op (./arch/x86/include/asm/idtentry.h:621)\n ? sk_mc_loop (net/core/sock.c:760)\n ip6_finish_output2 (net/ipv6/ip6_output.c:83 (discriminator 1))\n ? nf_hook_slow (net/netfilter/core.c:626)\n ip6_finish_output (net/ipv6/ip6_output.c:222)\n ? __pfx_ip6_finish_output (net/ipv6/ip6_output.c:215)\n ipvlan_xmit_mode_l3 (drivers/net/ipvlan/ipvlan_core.c:602) ipvlan\n ipvlan_start_xmit (drivers/net/ipvlan/ipvlan_main.c:226) ipvlan\n dev_hard_start_xmit (net/core/dev.c:3594)\n sch_direct_xmit (net/sched/sch_generic.c:343)\n __qdisc_run (net/sched/sch_generic.c:416)\n net_tx_action (net/core/dev.c:5286)\n handle_softirqs (kernel/softirq.c:555)\n __irq_exit_rcu (kernel/softirq.c:589)\n sysvec_apic_timer_interrupt (arch/x86/kernel/apic/apic.c:1043)\r\n\r\nThe warning triggers as this:\npacket_sendmsg\n   packet_snd //skb-\u0026gt;sk is packet sk\n      __dev_queue_xmit\n         __dev_xmit_skb //q-\u0026gt;enqueue is not NULL\n             __qdisc_run\n               sch_direct_xmit\n                 dev_hard_start_xmit\n                   ipvlan_start_xmit\n                      ipvlan_xmit_mode_l3 //l3 mode\n                        ipvlan_process_outbound //vepa flag\n                          ipvlan_process_v6_outbound\n                            ip6_local_out\n                                __ip6_finish_output\n                                  ip6_finish_output2 //multicast packet\n                                    sk_mc_loop //sk-\u0026gt;sk_family is AF_PACKET\r\n\r\nCall ip{6}_local_out() with NULL sk in ipvlan as other tunnels to fix this.(CVE-2024-33621)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nusb: gadget: ncm: Fix handling of zero block length packets\r\n\r\nWhile connecting to a Linux host with CDC_NCM_NTB_DEF_SIZE_TX\nset to 65536, it has been observed that we receive short packets,\nwhich come at interval of 5-10 seconds sometimes and have block\nlength zero but still contain 1-2 valid datagrams present.\r\n\r\nAccording to the NCM spec:\r\n\r\n\u0026quot;If wBlockLength = 0x0000, the block is terminated by a\nshort packet. In this case, the USB transfer must still\nbe shorter than dwNtbInMaxSize or dwNtbOutMaxSize. If\nexactly dwNtbInMaxSize or dwNtbOutMaxSize bytes are sent,\nand the size is a multiple of wMaxPacketSize for the\ngiven pipe, then no ZLP shall be sent.\r\n\r\nwBlockLength= 0x0000 must be used with extreme care, because\nof the possibility that the host and device may get out of\nsync, and because of test issues.\r\n\r\nwBlockLength = 0x0000 allows the sender to reduce latency by\nstarting to send a very large NTB, and then shortening it when\nthe sender discovers that there’s not sufficient data to justify\nsending a large NTB\u0026quot;\r\n\r\nHowever, there is a potential issue with the current implementation,\nas it checks for the occurrence of multiple NTBs in a single\ngiveback by verifying if the leftover bytes to be processed is zero\nor not. If the block length reads zero, we would process the same\nNTB infintely because the leftover bytes is never zero and it leads\nto a crash. Fix this by bailing out if block length reads zero.(CVE-2024-35825)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\ndrm: vc4: Fix possible null pointer dereference\r\n\r\nIn vc4_hdmi_audio_init() of_get_address() may return\nNULL which is later dereferenced. Fix this bug by adding NULL check.\r\n\r\nFound by Linux Verification Center (linuxtesting.org) with SVACE.(CVE-2024-38546)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nkunit: Fix kthread reference\r\n\r\nThere is a race condition when a kthread finishes after the deadline and\nbefore the call to kthread_stop(), which may lead to use after free.(CVE-2024-38561)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nnet: stmmac: move the EST lock to struct stmmac_priv\r\n\r\nReinitialize the whole EST structure would also reset the mutex\nlock which is embedded in the EST structure, and then trigger\nthe following warning. To address this, move the lock to struct\nstmmac_priv. We also need to reacquire the mutex lock when doing\nthis initialization.\r\n\r\nDEBUG_LOCKS_WARN_ON(lock-\u0026gt;magic != lock)\nWARNING: CPU: 3 PID: 505 at kernel/locking/mutex.c:587 __mutex_lock+0xd84/0x1068\n Modules linked in:\n CPU: 3 PID: 505 Comm: tc Not tainted 6.9.0-rc6-00053-g0106679839f7-dirty #29\n Hardware name: NXP i.MX8MPlus EVK board (DT)\n pstate: 60000005 (nZCv daif -PAN -UAO -TCO -DIT -SSBS BTYPE=--)\n pc : __mutex_lock+0xd84/0x1068\n lr : __mutex_lock+0xd84/0x1068\n sp : ffffffc0864e3570\n x29: ffffffc0864e3570 x28: ffffffc0817bdc78 x27: 0000000000000003\n x26: ffffff80c54f1808 x25: ffffff80c9164080 x24: ffffffc080d723ac\n x23: 0000000000000000 x22: 0000000000000002 x21: 0000000000000000\n x20: 0000000000000000 x19: ffffffc083bc3000 x18: ffffffffffffffff\n x17: ffffffc08117b080 x16: 0000000000000002 x15: ffffff80d2d40000\n x14: 00000000000002da x13: ffffff80d2d404b8 x12: ffffffc082b5a5c8\n x11: ffffffc082bca680 x10: ffffffc082bb2640 x9 : ffffffc082bb2698\n x8 : 0000000000017fe8 x7 : c0000000ffffefff x6 : 0000000000000001\n x5 : ffffff8178fe0d48 x4 : 0000000000000000 x3 : 0000000000000027\n x2 : ffffff8178fe0d50 x1 : 0000000000000000 x0 : 0000000000000000\n Call trace:\n  __mutex_lock+0xd84/0x1068\n  mutex_lock_nested+0x28/0x34\n  tc_setup_taprio+0x118/0x68c\n  stmmac_setup_tc+0x50/0xf0\n  taprio_change+0x868/0xc9c(CVE-2024-38594)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nstm class: Fix a double free in stm_register_device()\r\n\r\nThe put_device(\u0026amp;stm-\u0026gt;dev) call will trigger stm_device_release() which\nfrees \u0026quot;stm\u0026quot; so the vfree(stm) on the next line is a double free.(CVE-2024-38627)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\ndrm/shmem-helper: Fix BUG_ON() on mmap(PROT_WRITE, MAP_PRIVATE)\r\n\r\nLack of check for copy-on-write (COW) mapping in drm_gem_shmem_mmap\nallows users to call mmap with PROT_WRITE and MAP_PRIVATE flag\ncausing a kernel panic due to BUG_ON in vmf_insert_pfn_prot:\nBUG_ON((vma-\u0026gt;vm_flags \u0026amp; VM_PFNMAP) \u0026amp;\u0026amp; is_cow_mapping(vma-\u0026gt;vm_flags));\r\n\r\nReturn -EINVAL early if COW mapping is detected.\r\n\r\nThis bug affects all drm drivers using default shmem helpers.\nIt can be reproduced by this simple example:\nvoid *ptr = mmap(0, size, PROT_WRITE, MAP_PRIVATE, fd, mmap_offset);\nptr[0] = 0;(CVE-2024-39497)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nnet: hns3: fix kernel crash problem in concurrent scenario\r\n\r\nWhen link status change, the nic driver need to notify the roce\ndriver to handle this event, but at this time, the roce driver\nmay uninit, then cause kernel crash.\r\n\r\nTo fix the problem, when link status change, need to check\nwhether the roce registered, and when uninit, need to wait link\nupdate finish.(CVE-2024-39507)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nax25: Fix refcount imbalance on inbound connections\r\n\r\nWhen releasing a socket in ax25_release(), we call netdev_put() to\ndecrease the refcount on the associated ax.25 device. However, the\nexecution path for accepting an incoming connection never calls\nnetdev_hold(). This imbalance leads to refcount errors, and ultimately\nto kernel crashes.\r\n\r\nA typical call trace for the above situation will start with one of the\nfollowing errors:\r\n\r\n    refcount_t: decrement hit 0; leaking memory.\n    refcount_t: underflow; use-after-free.\r\n\r\nAnd will then have a trace like:\r\n\r\n    Call Trace:\n    \u0026lt;TASK\u0026gt;\n    ? show_regs+0x64/0x70\n    ? __warn+0x83/0x120\n    ? refcount_warn_saturate+0xb2/0x100\n    ? report_bug+0x158/0x190\n    ? prb_read_valid+0x20/0x30\n    ? handle_bug+0x3e/0x70\n    ? exc_invalid_op+0x1c/0x70\n    ? asm_exc_invalid_op+0x1f/0x30\n    ? refcount_warn_saturate+0xb2/0x100\n    ? refcount_warn_saturate+0xb2/0x100\n    ax25_release+0x2ad/0x360\n    __sock_release+0x35/0xa0\n    sock_close+0x19/0x20\n    [...]\r\n\r\nOn reboot (or any attempt to remove the interface), the kernel gets\nstuck in an infinite loop:\r\n\r\n    unregister_netdevice: waiting for ax0 to become free. Usage count = 0\r\n\r\nThis patch corrects these issues by ensuring that we call netdev_hold()\nand ax25_dev_hold() for new connections in ax25_accept(). This makes the\nlogic leading to ax25_accept() match the logic for ax25_bind(): in both\ncases we increment the refcount, which is ultimately decremented in\nax25_release().(CVE-2024-40910)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nKVM: Fix a data race on last_boosted_vcpu in kvm_vcpu_on_spin()\r\n\r\nUse {READ,WRITE}_ONCE() to access kvm-\u0026gt;last_boosted_vcpu to ensure the\nloads and stores are atomic.  In the extremely unlikely scenario the\ncompiler tears the stores, it\u0026apos;s theoretically possible for KVM to attempt\nto get a vCPU using an out-of-bounds index, e.g. if the write is split\ninto multiple 8-bit stores, and is paired with a 32-bit load on a VM with\n257 vCPUs:\r\n\r\n  CPU0                              CPU1\n  last_boosted_vcpu = 0xff;\r\n\r\n                                    (last_boosted_vcpu = 0x100)\n                                    last_boosted_vcpu[15:8] = 0x01;\n  i = (last_boosted_vcpu = 0x1ff)\n                                    last_boosted_vcpu[7:0] = 0x00;\r\n\r\n  vcpu = kvm-\u0026gt;vcpu_array[0x1ff];\r\n\r\nAs detected by KCSAN:\r\n\r\n  BUG: KCSAN: data-race in kvm_vcpu_on_spin [kvm] / kvm_vcpu_on_spin [kvm]\r\n\r\n  write to 0xffffc90025a92344 of 4 bytes by task 4340 on cpu 16:\n  kvm_vcpu_on_spin (arch/x86/kvm/../../../virt/kvm/kvm_main.c:4112) kvm\n  handle_pause (arch/x86/kvm/vmx/vmx.c:5929) kvm_intel\n  vmx_handle_exit (arch/x86/kvm/vmx/vmx.c:?\n\t\t arch/x86/kvm/vmx/vmx.c:6606) kvm_intel\n  vcpu_run (arch/x86/kvm/x86.c:11107 arch/x86/kvm/x86.c:11211) kvm\n  kvm_arch_vcpu_ioctl_run (arch/x86/kvm/x86.c:?) kvm\n  kvm_vcpu_ioctl (arch/x86/kvm/../../../virt/kvm/kvm_main.c:?) kvm\n  __se_sys_ioctl (fs/ioctl.c:52 fs/ioctl.c:904 fs/ioctl.c:890)\n  __x64_sys_ioctl (fs/ioctl.c:890)\n  x64_sys_call (arch/x86/entry/syscall_64.c:33)\n  do_syscall_64 (arch/x86/entry/common.c:?)\n  entry_SYSCALL_64_after_hwframe (arch/x86/entry/entry_64.S:130)\r\n\r\n  read to 0xffffc90025a92344 of 4 bytes by task 4342 on cpu 4:\n  kvm_vcpu_on_spin (arch/x86/kvm/../../../virt/kvm/kvm_main.c:4069) kvm\n  handle_pause (arch/x86/kvm/vmx/vmx.c:5929) kvm_intel\n  vmx_handle_exit (arch/x86/kvm/vmx/vmx.c:?\n\t\t\tarch/x86/kvm/vmx/vmx.c:6606) kvm_intel\n  vcpu_run (arch/x86/kvm/x86.c:11107 arch/x86/kvm/x86.c:11211) kvm\n  kvm_arch_vcpu_ioctl_run (arch/x86/kvm/x86.c:?) kvm\n  kvm_vcpu_ioctl (arch/x86/kvm/../../../virt/kvm/kvm_main.c:?) kvm\n  __se_sys_ioctl (fs/ioctl.c:52 fs/ioctl.c:904 fs/ioctl.c:890)\n  __x64_sys_ioctl (fs/ioctl.c:890)\n  x64_sys_call (arch/x86/entry/syscall_64.c:33)\n  do_syscall_64 (arch/x86/entry/common.c:?)\n  entry_SYSCALL_64_after_hwframe (arch/x86/entry/entry_64.S:130)\r\n\r\n  value changed: 0x00000012 -\u0026gt; 0x00000000(CVE-2024-40953)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\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\nipv6: prevent possible NULL deref in fib6_nh_init()\r\n\r\nsyzbot reminds us that in6_dev_get() can return NULL.\r\n\r\nfib6_nh_init()\n    ip6_validate_gw(  \u0026amp;idev  )\n        ip6_route_check_nh(  idev  )\n            *idev = in6_dev_get(dev); // can be NULL\r\n\r\nOops: general protection fault, probably for non-canonical address 0xdffffc00000000bc: 0000 [#1] PREEMPT SMP KASAN PTI\nKASAN: null-ptr-deref in range [0x00000000000005e0-0x00000000000005e7]\nCPU: 0 PID: 11237 Comm: syz-executor.3 Not tainted 6.10.0-rc2-syzkaller-00249-gbe27b8965297 #0\nHardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 06/07/2024\n RIP: 0010:fib6_nh_init+0x640/0x2160 net/ipv6/route.c:3606\nCode: 00 00 fc ff df 4c 8b 64 24 58 48 8b 44 24 28 4c 8b 74 24 30 48 89 c1 48 89 44 24 28 48 8d 98 e0 05 00 00 48 89 d8 48 c1 e8 03 \u0026lt;42\u0026gt; 0f b6 04 38 84 c0 0f 85 b3 17 00 00 8b 1b 31 ff 89 de e8 b8 8b\nRSP: 0018:ffffc900032775a0 EFLAGS: 00010202\nRAX: 00000000000000bc RBX: 00000000000005e0 RCX: 0000000000000000\nRDX: 0000000000000010 RSI: ffffc90003277a54 RDI: ffff88802b3a08d8\nRBP: ffffc900032778b0 R08: 00000000000002fc R09: 0000000000000000\nR10: 00000000000002fc R11: 0000000000000000 R12: ffff88802b3a08b8\nR13: 1ffff9200064eec8 R14: ffffc90003277a00 R15: dffffc0000000000\nFS:  00007f940feb06c0(0000) GS:ffff8880b9400000(0000) knlGS:0000000000000000\nCS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033\nCR2: 0000000000000000 CR3: 00000000245e8000 CR4: 00000000003506f0\nDR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000\nDR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400\nCall Trace:\n \u0026lt;TASK\u0026gt;\n  ip6_route_info_create+0x99e/0x12b0 net/ipv6/route.c:3809\n  ip6_route_add+0x28/0x160 net/ipv6/route.c:3853\n  ipv6_route_ioctl+0x588/0x870 net/ipv6/route.c:4483\n  inet6_ioctl+0x21a/0x280 net/ipv6/af_inet6.c:579\n  sock_do_ioctl+0x158/0x460 net/socket.c:1222\n  sock_ioctl+0x629/0x8e0 net/socket.c:1341\n  vfs_ioctl fs/ioctl.c:51 [inline]\n  __do_sys_ioctl fs/ioctl.c:907 [inline]\n  __se_sys_ioctl+0xfc/0x170 fs/ioctl.c:893\n  do_syscall_x64 arch/x86/entry/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:0x7f940f07cea9(CVE-2024-40961)\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\ndrm/radeon: fix UBSAN warning in kv_dpm.c\r\n\r\nAdds bounds check for sumo_vid_mapping_entry.(CVE-2024-40988)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nnet: ena: Add validation for completion descriptors consistency\r\n\r\nValidate that `first` flag is set only for the first\ndescriptor in multi-buffer packets.\nIn case of an invalid descriptor, a reset will occur.\nA new reset reason for RX data corruption has been added.(CVE-2024-40999)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nnetrom: Fix a memory leak in nr_heartbeat_expiry()\r\n\r\nsyzbot reported a memory leak in nr_create() [0].\r\n\r\nCommit 409db27e3a2e (\u0026quot;netrom: Fix use-after-free of a listening socket.\u0026quot;)\nadded sock_hold() to the nr_heartbeat_expiry() function, where\na) a socket has a SOCK_DESTROY flag or\nb) a listening socket has a SOCK_DEAD flag.\r\n\r\nBut in the case \u0026quot;a,\u0026quot; when the SOCK_DESTROY flag is set, the file descriptor\nhas already been closed and the nr_release() function has been called.\nSo it makes no sense to hold the reference count because no one will\ncall another nr_destroy_socket() and put it as in the case \u0026quot;b.\u0026quot;\r\n\r\nnr_connect\n  nr_establish_data_link\n    nr_start_heartbeat\r\n\r\nnr_release\n  switch (nr-\u0026gt;state)\n  case NR_STATE_3\n    nr-\u0026gt;state = NR_STATE_2\n    sock_set_flag(sk, SOCK_DESTROY);\r\n\r\n                        nr_rx_frame\n                          nr_process_rx_frame\n                            switch (nr-\u0026gt;state)\n                            case NR_STATE_2\n                              nr_state2_machine()\n                                nr_disconnect()\n                                  nr_sk(sk)-\u0026gt;state = NR_STATE_0\n                                  sock_set_flag(sk, SOCK_DEAD)\r\n\r\n                        nr_heartbeat_expiry\n                          switch (nr-\u0026gt;state)\n                          case NR_STATE_0\n                            if (sock_flag(sk, SOCK_DESTROY) ||\n                               (sk-\u0026gt;sk_state == TCP_LISTEN\n                                 \u0026amp;\u0026amp; sock_flag(sk, SOCK_DEAD)))\n                               sock_hold()  // ( !!! )\n                               nr_destroy_socket()\r\n\r\nTo fix the memory leak, let\u0026apos;s call sock_hold() only for a listening socket.\r\n\r\nFound by InfoTeCS on behalf of Linux Verification Center\n(linuxtesting.org) with Syzkaller.\r\n\r\n[0]: https://syzkaller.appspot.com/bug?extid=d327a1f3b12e1e206c16(CVE-2024-41006)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nxfs: don\u0026apos;t walk off the end of a directory data block\r\n\r\nThis adds sanity checks for xfs_dir2_data_unused and xfs_dir2_data_entry\nto make sure don\u0026apos;t stray beyond valid memory region. Before patching, the\nloop simply checks that the start offset of the dup and dep is within the\nrange. So in a crafted image, if last entry is xfs_dir2_data_unused, we\ncan change dup-\u0026gt;length to dup-\u0026gt;length-1 and leave 1 byte of space. In the\nnext traversal, this space will be considered as dup or dep. We may\nencounter an out of bound read when accessing the fixed members.\r\n\r\nIn the patch, we make sure that the remaining bytes large enough to hold\nan unused entry before accessing xfs_dir2_data_unused and\nxfs_dir2_data_unused is XFS_DIR2_DATA_ALIGN byte aligned. We also make\nsure that the remaining bytes large enough to hold a dirent with a\nsingle-byte name before accessing xfs_dir2_data_entry.(CVE-2024-41013)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nxfs: add bounds checking to xlog_recover_process_data\r\n\r\nThere is a lack of verification of the space occupied by fixed members\nof xlog_op_header in the xlog_recover_process_data.\r\n\r\nWe can create a crafted image to trigger an out of bounds read by\nfollowing these steps:\n    1) Mount an image of xfs, and do some file operations to leave records\n    2) Before umounting, copy the image for subsequent steps to simulate\n       abnormal exit. Because umount will ensure that tail_blk and\n       head_blk are the same, which will result in the inability to enter\n       xlog_recover_process_data\n    3) Write a tool to parse and modify the copied image in step 2\n    4) Make the end of the xlog_op_header entries only 1 byte away from\n       xlog_rec_header-\u0026gt;h_size\n    5) xlog_rec_header-\u0026gt;h_num_logops++\n    6) Modify xlog_rec_header-\u0026gt;h_crc\r\n\r\nFix:\nAdd a check to make sure there is sufficient space to access fixed members\nof xlog_op_header.(CVE-2024-41014)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nfs/ntfs3: Validate ff offset\r\n\r\nThis adds sanity checks for ff offset. There is a check\non rt-\u0026gt;first_free at first, but walking through by ff\nwithout any check. If the second ff is a large offset.\nWe may encounter an out-of-bound read.(CVE-2024-41019)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nfilelock: Fix fcntl/close race recovery compat path\r\n\r\nWhen I wrote commit 3cad1bc01041 (\u0026quot;filelock: Remove locks reliably when\nfcntl/close race is detected\u0026quot;), I missed that there are two copies of the\ncode I was patching: The normal version, and the version for 64-bit offsets\non 32-bit kernels.\nThanks to Greg KH for stumbling over this while doing the stable\nbackport...\r\n\r\nApply exactly the same fix to the compat path for 32-bit kernels.(CVE-2024-41020)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\ndrm/amdgpu: Fix signedness bug in sdma_v4_0_process_trap_irq()\r\n\r\nThe \u0026quot;instance\u0026quot; variable needs to be signed for the error handling to work.(CVE-2024-41022)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nsched/deadline: Fix task_struct reference leak\r\n\r\nDuring the execution of the following stress test with linux-rt:\r\n\r\nstress-ng --cyclic 30 --timeout 30 --minimize --quiet\r\n\r\nkmemleak frequently reported a memory leak concerning the task_struct:\r\n\r\nunreferenced object 0xffff8881305b8000 (size 16136):\n  comm \u0026quot;stress-ng\u0026quot;, pid 614, jiffies 4294883961 (age 286.412s)\n  object hex dump (first 32 bytes):\n    02 40 00 00 00 00 00 00 00 00 00 00 00 00 00 00  .@..............\n    00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................\n  debug hex dump (first 16 bytes):\n    53 09 00 00 00 00 00 00 00 00 00 00 00 00 00 00  S...............\n  backtrace:\n    [\u0026lt;00000000046b6790\u0026gt;] dup_task_struct+0x30/0x540\n    [\u0026lt;00000000c5ca0f0b\u0026gt;] copy_process+0x3d9/0x50e0\n    [\u0026lt;00000000ced59777\u0026gt;] kernel_clone+0xb0/0x770\n    [\u0026lt;00000000a50befdc\u0026gt;] __do_sys_clone+0xb6/0xf0\n    [\u0026lt;000000001dbf2008\u0026gt;] do_syscall_64+0x5d/0xf0\n    [\u0026lt;00000000552900ff\u0026gt;] entry_SYSCALL_64_after_hwframe+0x6e/0x76\r\n\r\nThe issue occurs in start_dl_timer(), which increments the task_struct\nreference count and sets a timer. The timer callback, dl_task_timer,\nis supposed to decrement the reference count upon expiration. However,\nif enqueue_task_dl() is called before the timer expires and cancels it,\nthe reference count is not decremented, leading to the leak.\r\n\r\nThis patch fixes the reference leak by ensuring the task_struct\nreference count is properly decremented when the timer is canceled.(CVE-2024-41023)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nFix userfaultfd_api to return EINVAL as expected\r\n\r\nCurrently if we request a feature that is not set in the Kernel config we\nfail silently and return all the available features.  However, the man\npage indicates we should return an EINVAL.\r\n\r\nWe need to fix this issue since we can end up with a Kernel warning should\na program request the feature UFFD_FEATURE_WP_UNPOPULATED on a kernel with\nthe config not set with this feature.\r\n\r\n [  200.812896] WARNING: CPU: 91 PID: 13634 at mm/memory.c:1660 zap_pte_range+0x43d/0x660\n [  200.820738] Modules linked in:\n [  200.869387] CPU: 91 PID: 13634 Comm: userfaultfd Kdump: loaded Not tainted 6.9.0-rc5+ #8\n [  200.877477] Hardware name: Dell Inc. PowerEdge R6525/0N7YGH, BIOS 2.7.3 03/30/2022\n [  200.885052] RIP: 0010:zap_pte_range+0x43d/0x660(CVE-2024-41027)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nnet/sched: Fix UAF when resolving a clash\r\n\r\nKASAN reports the following UAF:\r\n\r\n BUG: KASAN: slab-use-after-free in tcf_ct_flow_table_process_conn+0x12b/0x380 [act_ct]\n Read of size 1 at addr ffff888c07603600 by task handler130/6469\r\n\r\n Call Trace:\n  \u0026lt;IRQ\u0026gt;\n  dump_stack_lvl+0x48/0x70\n  print_address_description.constprop.0+0x33/0x3d0\n  print_report+0xc0/0x2b0\n  kasan_report+0xd0/0x120\n  __asan_load1+0x6c/0x80\n  tcf_ct_flow_table_process_conn+0x12b/0x380 [act_ct]\n  tcf_ct_act+0x886/0x1350 [act_ct]\n  tcf_action_exec+0xf8/0x1f0\n  fl_classify+0x355/0x360 [cls_flower]\n  __tcf_classify+0x1fd/0x330\n  tcf_classify+0x21c/0x3c0\n  sch_handle_ingress.constprop.0+0x2c5/0x500\n  __netif_receive_skb_core.constprop.0+0xb25/0x1510\n  __netif_receive_skb_list_core+0x220/0x4c0\n  netif_receive_skb_list_internal+0x446/0x620\n  napi_complete_done+0x157/0x3d0\n  gro_cell_poll+0xcf/0x100\n  __napi_poll+0x65/0x310\n  net_rx_action+0x30c/0x5c0\n  __do_softirq+0x14f/0x491\n  __irq_exit_rcu+0x82/0xc0\n  irq_exit_rcu+0xe/0x20\n  common_interrupt+0xa1/0xb0\n  \u0026lt;/IRQ\u0026gt;\n  \u0026lt;TASK\u0026gt;\n  asm_common_interrupt+0x27/0x40\r\n\r\n Allocated by task 6469:\n  kasan_save_stack+0x38/0x70\n  kasan_set_track+0x25/0x40\n  kasan_save_alloc_info+0x1e/0x40\n  __kasan_krealloc+0x133/0x190\n  krealloc+0xaa/0x130\n  nf_ct_ext_add+0xed/0x230 [nf_conntrack]\n  tcf_ct_act+0x1095/0x1350 [act_ct]\n  tcf_action_exec+0xf8/0x1f0\n  fl_classify+0x355/0x360 [cls_flower]\n  __tcf_classify+0x1fd/0x330\n  tcf_classify+0x21c/0x3c0\n  sch_handle_ingress.constprop.0+0x2c5/0x500\n  __netif_receive_skb_core.constprop.0+0xb25/0x1510\n  __netif_receive_skb_list_core+0x220/0x4c0\n  netif_receive_skb_list_internal+0x446/0x620\n  napi_complete_done+0x157/0x3d0\n  gro_cell_poll+0xcf/0x100\n  __napi_poll+0x65/0x310\n  net_rx_action+0x30c/0x5c0\n  __do_softirq+0x14f/0x491\r\n\r\n Freed by task 6469:\n  kasan_save_stack+0x38/0x70\n  kasan_set_track+0x25/0x40\n  kasan_save_free_info+0x2b/0x60\n  ____kasan_slab_free+0x180/0x1f0\n  __kasan_slab_free+0x12/0x30\n  slab_free_freelist_hook+0xd2/0x1a0\n  __kmem_cache_free+0x1a2/0x2f0\n  kfree+0x78/0x120\n  nf_conntrack_free+0x74/0x130 [nf_conntrack]\n  nf_ct_destroy+0xb2/0x140 [nf_conntrack]\n  __nf_ct_resolve_clash+0x529/0x5d0 [nf_conntrack]\n  nf_ct_resolve_clash+0xf6/0x490 [nf_conntrack]\n  __nf_conntrack_confirm+0x2c6/0x770 [nf_conntrack]\n  tcf_ct_act+0x12ad/0x1350 [act_ct]\n  tcf_action_exec+0xf8/0x1f0\n  fl_classify+0x355/0x360 [cls_flower]\n  __tcf_classify+0x1fd/0x330\n  tcf_classify+0x21c/0x3c0\n  sch_handle_ingress.constprop.0+0x2c5/0x500\n  __netif_receive_skb_core.constprop.0+0xb25/0x1510\n  __netif_receive_skb_list_core+0x220/0x4c0\n  netif_receive_skb_list_internal+0x446/0x620\n  napi_complete_done+0x157/0x3d0\n  gro_cell_poll+0xcf/0x100\n  __napi_poll+0x65/0x310\n  net_rx_action+0x30c/0x5c0\n  __do_softirq+0x14f/0x491\r\n\r\nThe ct may be dropped if a clash has been resolved but is still passed to\nthe tcf_ct_flow_table_process_conn function for further usage. This issue\ncan be fixed by retrieving ct from skb again after confirming conntrack.(CVE-2024-41040)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nudp: Set SOCK_RCU_FREE earlier in udp_lib_get_port().\r\n\r\nsyzkaller triggered the warning [0] in udp_v4_early_demux().\r\n\r\nIn udp_v[46]_early_demux() and sk_lookup(), we do not touch the refcount\nof the looked-up sk and use sock_pfree() as skb-\u0026gt;destructor, so we check\nSOCK_RCU_FREE to ensure that the sk is safe to access during the RCU grace\nperiod.\r\n\r\nCurrently, SOCK_RCU_FREE is flagged for a bound socket after being put\ninto the hash table.  Moreover, the SOCK_RCU_FREE check is done too early\nin udp_v[46]_early_demux() and sk_lookup(), so there could be a small race\nwindow:\r\n\r\n  CPU1                                 CPU2\n  ----                                 ----\n  udp_v4_early_demux()                 udp_lib_get_port()\n  |                                    |- hlist_add_head_rcu()\n  |- sk = __udp4_lib_demux_lookup()    |\n  |- DEBUG_NET_WARN_ON_ONCE(sk_is_refcounted(sk));\n                                       `- sock_set_flag(sk, SOCK_RCU_FREE)\r\n\r\nWe had the same bug in TCP and fixed it in commit 871019b22d1b (\u0026quot;net:\nset SOCK_RCU_FREE before inserting socket into hashtable\u0026quot;).\r\n\r\nLet\u0026apos;s apply the same fix for UDP.\r\n\r\n[0]:\nWARNING: CPU: 0 PID: 11198 at net/ipv4/udp.c:2599 udp_v4_early_demux+0x481/0xb70 net/ipv4/udp.c:2599\nModules linked in:\nCPU: 0 PID: 11198 Comm: syz-executor.1 Not tainted 6.9.0-g93bda33046e7 #13\nHardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS rel-1.16.0-0-gd239552ce722-prebuilt.qemu.org 04/01/2014\nRIP: 0010:udp_v4_early_demux+0x481/0xb70 net/ipv4/udp.c:2599\nCode: c5 7a 15 fe bb 01 00 00 00 44 89 e9 31 ff d3 e3 81 e3 bf ef ff ff 89 de e8 2c 74 15 fe 85 db 0f 85 02 06 00 00 e8 9f 7a 15 fe \u0026lt;0f\u0026gt; 0b e8 98 7a 15 fe 49 8d 7e 60 e8 4f 39 2f fe 49 c7 46 60 20 52\nRSP: 0018:ffffc9000ce3fa58 EFLAGS: 00010293\nRAX: 0000000000000000 RBX: 0000000000000000 RCX: ffffffff8318c92c\nRDX: ffff888036ccde00 RSI: ffffffff8318c2f1 RDI: 0000000000000001\nRBP: ffff88805a2dd6e0 R08: 0000000000000001 R09: 0000000000000000\nR10: 0000000000000000 R11: 0001ffffffffffff R12: ffff88805a2dd680\nR13: 0000000000000007 R14: ffff88800923f900 R15: ffff88805456004e\nFS:  00007fc449127640(0000) GS:ffff88807dc00000(0000) knlGS:0000000000000000\nCS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033\nCR2: 00007fc449126e38 CR3: 000000003de4b002 CR4: 0000000000770ef0\nDR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000\nDR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000600\nPKRU: 55555554\nCall Trace:\n \u0026lt;TASK\u0026gt;\n ip_rcv_finish_core.constprop.0+0xbdd/0xd20 net/ipv4/ip_input.c:349\n ip_rcv_finish+0xda/0x150 net/ipv4/ip_input.c:447\n NF_HOOK include/linux/netfilter.h:314 [inline]\n NF_HOOK include/linux/netfilter.h:308 [inline]\n ip_rcv+0x16c/0x180 net/ipv4/ip_input.c:569\n __netif_receive_skb_one_core+0xb3/0xe0 net/core/dev.c:5624\n __netif_receive_skb+0x21/0xd0 net/core/dev.c:5738\n netif_receive_skb_internal net/core/dev.c:5824 [inline]\n netif_receive_skb+0x271/0x300 net/core/dev.c:5884\n tun_rx_batched drivers/net/tun.c:1549 [inline]\n tun_get_user+0x24db/0x2c50 drivers/net/tun.c:2002\n tun_chr_write_iter+0x107/0x1a0 drivers/net/tun.c:2048\n new_sync_write fs/read_write.c:497 [inline]\n vfs_write+0x76f/0x8d0 fs/read_write.c:590\n ksys_write+0xbf/0x190 fs/read_write.c:643\n __do_sys_write fs/read_write.c:655 [inline]\n __se_sys_write fs/read_write.c:652 [inline]\n __x64_sys_write+0x41/0x50 fs/read_write.c:652\n x64_sys_call+0xe66/0x1990 arch/x86/include/generated/asm/syscalls_64.h:2\n do_syscall_x64 arch/x86/entry/common.c:52 [inline]\n do_syscall_64+0x4b/0x110 arch/x86/entry/common.c:83\n entry_SYSCALL_64_after_hwframe+0x4b/0x53\nRIP: 0033:0x7fc44a68bc1f\nCode: 89 54 24 18 48 89 74 24 10 89 7c 24 08 e8 e9 cf f5 ff 48 8b 54 24 18 48 8b 74 24 10 41 89 c0 8b 7c 24 08 b8 01 00 00 00 0f 05 \u0026lt;48\u0026gt; 3d 00 f0 ff ff 77 31 44 89 c7 48 89 44 24 08 e8 3c d0 f5 ff 48\nRSP: 002b:00007fc449126c90 EFLAGS: 00000293 ORIG_RAX: 0000000000000001\nRAX: ffffffffffffffda RBX: 00000000004bc050 RCX: 00007fc44a68bc1f\nR\n---truncated---(CVE-2024-41041)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nppp: reject claimed-as-LCP but actually malformed packets\r\n\r\nSince \u0026apos;ppp_async_encode()\u0026apos; assumes valid LCP packets (with code\nfrom 1 to 7 inclusive), add \u0026apos;ppp_check_packet()\u0026apos; to ensure that\nLCP packet has an actual body beyond PPP_LCP header bytes, and\nreject claimed-as-LCP but actually malformed data otherwise.(CVE-2024-41044)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nskmsg: Skip zero length skb in sk_msg_recvmsg\r\n\r\nWhen running BPF selftests (./test_progs -t sockmap_basic) on a Loongarch\nplatform, the following kernel panic occurs:\r\n\r\n  [...]\n  Oops[#1]:\n  CPU: 22 PID: 2824 Comm: test_progs Tainted: G           OE  6.10.0-rc2+ #18\n  Hardware name: LOONGSON Dabieshan/Loongson-TC542F0, BIOS Loongson-UDK2018\n     ... ...\n     ra: 90000000048bf6c0 sk_msg_recvmsg+0x120/0x560\n    ERA: 9000000004162774 copy_page_to_iter+0x74/0x1c0\n   CRMD: 000000b0 (PLV0 -IE -DA +PG DACF=CC DACM=CC -WE)\n   PRMD: 0000000c (PPLV0 +PIE +PWE)\n   EUEN: 00000007 (+FPE +SXE +ASXE -BTE)\n   ECFG: 00071c1d (LIE=0,2-4,10-12 VS=7)\n  ESTAT: 00010000 [PIL] (IS= ECode=1 EsubCode=0)\n   BADV: 0000000000000040\n   PRID: 0014c011 (Loongson-64bit, Loongson-3C5000)\n  Modules linked in: bpf_testmod(OE) xt_CHECKSUM xt_MASQUERADE xt_conntrack\n  Process test_progs (pid: 2824, threadinfo=0000000000863a31, task=...)\n  Stack : ...\n  Call Trace:\n  [\u0026lt;9000000004162774\u0026gt;] copy_page_to_iter+0x74/0x1c0\n  [\u0026lt;90000000048bf6c0\u0026gt;] sk_msg_recvmsg+0x120/0x560\n  [\u0026lt;90000000049f2b90\u0026gt;] tcp_bpf_recvmsg_parser+0x170/0x4e0\n  [\u0026lt;90000000049aae34\u0026gt;] inet_recvmsg+0x54/0x100\n  [\u0026lt;900000000481ad5c\u0026gt;] sock_recvmsg+0x7c/0xe0\n  [\u0026lt;900000000481e1a8\u0026gt;] __sys_recvfrom+0x108/0x1c0\n  [\u0026lt;900000000481e27c\u0026gt;] sys_recvfrom+0x1c/0x40\n  [\u0026lt;9000000004c076ec\u0026gt;] do_syscall+0x8c/0xc0\n  [\u0026lt;9000000003731da4\u0026gt;] handle_syscall+0xc4/0x160\n  Code: ...\n  ---[ end trace 0000000000000000 ]---\n  Kernel panic - not syncing: Fatal exception\n  Kernel relocated by 0x3510000\n   .text @ 0x9000000003710000\n   .data @ 0x9000000004d70000\n   .bss  @ 0x9000000006469400\n  ---[ end Kernel panic - not syncing: Fatal exception ]---\n  [...]\r\n\r\nThis crash happens every time when running sockmap_skb_verdict_shutdown\nsubtest in sockmap_basic.\r\n\r\nThis crash is because a NULL pointer is passed to page_address() in the\nsk_msg_recvmsg(). Due to the different implementations depending on the\narchitecture, page_address(NULL) will trigger a panic on Loongarch\nplatform but not on x86 platform. So this bug was hidden on x86 platform\nfor a while, but now it is exposed on Loongarch platform. The root cause\nis that a zero length skb (skb-\u0026gt;len == 0) was put on the queue.\r\n\r\nThis zero length skb is a TCP FIN packet, which was sent by shutdown(),\ninvoked in test_sockmap_skb_verdict_shutdown():\r\n\r\n\tshutdown(p1, SHUT_WR);\r\n\r\nIn this case, in sk_psock_skb_ingress_enqueue(), num_sge is zero, and no\npage is put to this sge (see sg_set_page in sg_set_page), but this empty\nsge is queued into ingress_msg list.\r\n\r\nAnd in sk_msg_recvmsg(), this empty sge is used, and a NULL page is got by\nsg_page(sge). Pass this NULL page to copy_page_to_iter(), which passes it\nto kmap_local_page() and to page_address(), then kernel panics.\r\n\r\nTo solve this, we should skip this zero length skb. So in sk_msg_recvmsg(),\nif copy is zero, that means it\u0026apos;s a zero length skb, skip invoking\ncopy_page_to_iter(). We are using the EFAULT return triggered by\ncopy_page_to_iter to check for is_fin in tcp_bpf.c.(CVE-2024-41048)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nfilelock: fix potential use-after-free in posix_lock_inode\r\n\r\nLight Hsieh reported a KASAN UAF warning in trace_posix_lock_inode().\nThe request pointer had been changed earlier to point to a lock entry\nthat was added to the inode\u0026apos;s list. However, before the tracepoint could\nfire, another task raced in and freed that lock.\r\n\r\nFix this by moving the tracepoint inside the spinlock, which should\nensure that this doesn\u0026apos;t happen.(CVE-2024-41049)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nmm: prevent derefencing NULL ptr in pfn_section_valid()\r\n\r\nCommit 5ec8e8ea8b77 (\u0026quot;mm/sparsemem: fix race in accessing\nmemory_section-\u0026gt;usage\u0026quot;) changed pfn_section_valid() to add a READ_ONCE()\ncall around \u0026quot;ms-\u0026gt;usage\u0026quot; to fix a race with section_deactivate() where\nms-\u0026gt;usage can be cleared.  The READ_ONCE() call, by itself, is not enough\nto prevent NULL pointer dereference.  We need to check its value before\ndereferencing it.(CVE-2024-41055)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nbluetooth/l2cap: sync sock recv cb and release\r\n\r\nThe problem occurs between the system call to close the sock and hci_rx_work,\nwhere the former releases the sock and the latter accesses it without lock protection.\r\n\r\n           CPU0                       CPU1\n           ----                       ----\n           sock_close                 hci_rx_work\n\t   l2cap_sock_release         hci_acldata_packet\n\t   l2cap_sock_kill            l2cap_recv_frame\n\t   sk_free                    l2cap_conless_channel\n\t                              l2cap_sock_recv_cb\r\n\r\nIf hci_rx_work processes the data that needs to be received before the sock is\nclosed, then everything is normal; Otherwise, the work thread may access the\nreleased sock when receiving data.\r\n\r\nAdd a chan mutex in the rx callback of the sock to achieve synchronization between\nthe sock release and recv cb.\r\n\r\nSock is dead, so set chan data to NULL, avoid others use invalid sock pointer.(CVE-2024-41062)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nBluetooth: hci_core: cancel all works upon hci_unregister_dev()\r\n\r\nsyzbot is reporting that calling hci_release_dev() from hci_error_reset()\ndue to hci_dev_put() from hci_error_reset() can cause deadlock at\ndestroy_workqueue(), for hci_error_reset() is called from\nhdev-\u0026gt;req_workqueue which destroy_workqueue() needs to flush.\r\n\r\nWe need to make sure that hdev-\u0026gt;{rx_work,cmd_work,tx_work} which are\nqueued into hdev-\u0026gt;workqueue and hdev-\u0026gt;{power_on,error_reset} which are\nqueued into hdev-\u0026gt;req_workqueue are no longer running by the moment\r\n\r\n       destroy_workqueue(hdev-\u0026gt;workqueue);\n       destroy_workqueue(hdev-\u0026gt;req_workqueue);\r\n\r\nare called from hci_release_dev().\r\n\r\nCall cancel_work_sync() on these work items from hci_unregister_dev()\nas soon as hdev-\u0026gt;list is removed from hci_dev_list.(CVE-2024-41063)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\npowerpc/eeh: avoid possible crash when edev-\u0026gt;pdev changes\r\n\r\nIf a PCI device is removed during eeh_pe_report_edev(), edev-\u0026gt;pdev\nwill change and can cause a crash, hold the PCI rescan/remove lock\nwhile taking a copy of edev-\u0026gt;pdev-\u0026gt;bus.(CVE-2024-41064)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nibmvnic: Add tx check to prevent skb leak\r\n\r\nBelow is a summary of how the driver stores a reference to an skb during\ntransmit:\n    tx_buff[free_map[consumer_index]]-\u0026gt;skb = new_skb;\n    free_map[consumer_index] = IBMVNIC_INVALID_MAP;\n    consumer_index ++;\nWhere variable data looks like this:\n    free_map == [4, IBMVNIC_INVALID_MAP, IBMVNIC_INVALID_MAP, 0, 3]\n                                               \tconsumer_index^\n    tx_buff == [skb=null, skb=\u0026lt;ptr\u0026gt;, skb=\u0026lt;ptr\u0026gt;, skb=null, skb=null]\r\n\r\nThe driver has checks to ensure that free_map[consumer_index] pointed to\na valid index but there was no check to ensure that this index pointed\nto an unused/null skb address. So, if, by some chance, our free_map and\ntx_buff lists become out of sync then we were previously risking an\nskb memory leak. This could then cause tcp congestion control to stop\nsending packets, eventually leading to ETIMEDOUT.\r\n\r\nTherefore, add a conditional to ensure that the skb address is null. If\nnot then warn the user (because this is still a bug that should be\npatched) and free the old pointer to prevent memleak/tcp problems.(CVE-2024-41066)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nASoC: topology: Fix references to freed memory\r\n\r\nMost users after parsing a topology file, release memory used by it, so\nhaving pointer references directly into topology file contents is wrong.\nUse devm_kmemdup(), to allocate memory as needed.(CVE-2024-41069)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nKVM: PPC: Book3S HV: Prevent UAF in kvm_spapr_tce_attach_iommu_group()\r\n\r\nAl reported a possible use-after-free (UAF) in kvm_spapr_tce_attach_iommu_group().\r\n\r\nIt looks up `stt` from tablefd, but then continues to use it after doing\nfdput() on the returned fd. After the fdput() the tablefd is free to be\nclosed by another thread. The close calls kvm_spapr_tce_release() and\nthen release_spapr_tce_table() (via call_rcu()) which frees `stt`.\r\n\r\nAlthough there are calls to rcu_read_lock() in\nkvm_spapr_tce_attach_iommu_group() they are not sufficient to prevent\nthe UAF, because `stt` is used outside the locked regions.\r\n\r\nWith an artifcial delay after the fdput() and a userspace program which\ntriggers the race, KASAN detects the UAF:\r\n\r\n  BUG: KASAN: slab-use-after-free in kvm_spapr_tce_attach_iommu_group+0x298/0x720 [kvm]\n  Read of size 4 at addr c000200027552c30 by task kvm-vfio/2505\n  CPU: 54 PID: 2505 Comm: kvm-vfio Not tainted 6.10.0-rc3-next-20240612-dirty #1\n  Hardware name: 8335-GTH POWER9 0x4e1202 opal:skiboot-v6.5.3-35-g1851b2a06 PowerNV\n  Call Trace:\n    dump_stack_lvl+0xb4/0x108 (unreliable)\n    print_report+0x2b4/0x6ec\n    kasan_report+0x118/0x2b0\n    __asan_load4+0xb8/0xd0\n    kvm_spapr_tce_attach_iommu_group+0x298/0x720 [kvm]\n    kvm_vfio_set_attr+0x524/0xac0 [kvm]\n    kvm_device_ioctl+0x144/0x240 [kvm]\n    sys_ioctl+0x62c/0x1810\n    system_call_exception+0x190/0x440\n    system_call_vectored_common+0x15c/0x2ec\n  ...\n  Freed by task 0:\n   ...\n   kfree+0xec/0x3e0\n   release_spapr_tce_table+0xd4/0x11c [kvm]\n   rcu_core+0x568/0x16a0\n   handle_softirqs+0x23c/0x920\n   do_softirq_own_stack+0x6c/0x90\n   do_softirq_own_stack+0x58/0x90\n   __irq_exit_rcu+0x218/0x2d0\n   irq_exit+0x30/0x80\n   arch_local_irq_restore+0x128/0x230\n   arch_local_irq_enable+0x1c/0x30\n   cpuidle_enter_state+0x134/0x5cc\n   cpuidle_enter+0x6c/0xb0\n   call_cpuidle+0x7c/0x100\n   do_idle+0x394/0x410\n   cpu_startup_entry+0x60/0x70\n   start_secondary+0x3fc/0x410\n   start_secondary_prolog+0x10/0x14\r\n\r\nFix it by delaying the fdput() until `stt` is no longer in use, which\nis effectively the entire function. To keep the patch minimal add a call\nto fdput() at each of the existing return paths. Future work can convert\nthe function to goto or __cleanup style cleanup.\r\n\r\nWith the fix in place the test case no longer triggers the UAF.(CVE-2024-41070)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nwifi: cfg80211: wext: add extra SIOCSIWSCAN data check\r\n\r\nIn \u0026apos;cfg80211_wext_siwscan()\u0026apos;, add extra check whether number of\nchannels passed via \u0026apos;ioctl(sock, SIOCSIWSCAN, ...)\u0026apos; doesn\u0026apos;t exceed\nIW_MAX_FREQUENCIES and reject invalid request with -EINVAL otherwise.(CVE-2024-41072)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nnvme: avoid double free special payload\r\n\r\nIf a discard request needs to be retried, and that retry may fail before\na new special payload is added, a double free will result. Clear the\nRQF_SPECIAL_LOAD when the request is cleaned.(CVE-2024-41073)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nnull_blk: fix validation of block size\r\n\r\nBlock size should be between 512 and PAGE_SIZE and be a power of 2. The current\ncheck does not validate this, so update the check.\r\n\r\nWithout this patch, null_blk would Oops due to a null pointer deref when\nloaded with bs=1536 [1].\r\n\r\n\n[axboe: remove unnecessary braces and != 0 check](CVE-2024-41077)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nnvmet: always initialize cqe.result\r\n\r\nThe spec doesn\u0026apos;t mandate that the first two double words (aka results)\nfor the command queue entry need to be set to 0 when they are not\nused (not specified). Though, the target implemention returns 0 for TCP\nand FC but not for RDMA.\r\n\r\nLet\u0026apos;s make RDMA behave the same and thus explicitly initializing the\nresult field. This prevents leaking any data from the stack.(CVE-2024-41079)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nio_uring: fix possible deadlock in io_register_iowq_max_workers()\r\n\r\nThe io_register_iowq_max_workers() function calls io_put_sq_data(),\nwhich acquires the sqd-\u0026gt;lock without releasing the uring_lock.\nSimilar to the commit 009ad9f0c6ee (\u0026quot;io_uring: drop ctx-\u0026gt;uring_lock\nbefore acquiring sqd-\u0026gt;lock\u0026quot;), this can lead to a potential deadlock\nsituation.\r\n\r\nTo resolve this issue, the uring_lock is released before calling\nio_put_sq_data(), and then it is re-acquired after the function call.\r\n\r\nThis change ensures that the locks are acquired in the correct\norder, preventing the possibility of a deadlock.(CVE-2024-41080)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nila: block BH in ila_output()\r\n\r\nAs explained in commit 1378817486d6 (\u0026quot;tipc: block BH\nbefore using dst_cache\u0026quot;), net/core/dst_cache.c\nhelpers need to be called with BH disabled.\r\n\r\nila_output() is called from lwtunnel_output()\npossibly from process context, and under rcu_read_lock().\r\n\r\nWe might be interrupted by a softirq, re-enter ila_output()\nand corrupt dst_cache data structures.\r\n\r\nFix the race by using local_bh_disable().(CVE-2024-41081)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nata: libata-core: Fix double free on error\r\n\r\nIf e.g. the ata_port_alloc() call in ata_host_alloc() fails, we will jump\nto the err_out label, which will call devres_release_group().\ndevres_release_group() will trigger a call to ata_host_release().\nata_host_release() calls kfree(host), so executing the kfree(host) in\nata_host_alloc() will lead to a double free:\r\n\r\nkernel BUG at mm/slub.c:553!\nOops: invalid opcode: 0000 [#1] PREEMPT SMP NOPTI\nCPU: 11 PID: 599 Comm: (udev-worker) Not tainted 6.10.0-rc5 #47\nHardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.16.3-2.fc40 04/01/2014\nRIP: 0010:kfree+0x2cf/0x2f0\nCode: 5d 41 5e 41 5f 5d e9 80 d6 ff ff 4d 89 f1 41 b8 01 00 00 00 48 89 d9 48 89 da\nRSP: 0018:ffffc90000f377f0 EFLAGS: 00010246\nRAX: ffff888112b1f2c0 RBX: ffff888112b1f2c0 RCX: ffff888112b1f320\nRDX: 000000000000400b RSI: ffffffffc02c9de5 RDI: ffff888112b1f2c0\nRBP: ffffc90000f37830 R08: 0000000000000000 R09: 0000000000000000\nR10: ffffc90000f37610 R11: 617461203a736b6e R12: ffffea00044ac780\nR13: ffff888100046400 R14: ffffffffc02c9de5 R15: 0000000000000006\nFS:  00007f2f1cabe980(0000) GS:ffff88813b380000(0000) knlGS:0000000000000000\nCS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033\nCR2: 00007f2f1c3acf75 CR3: 0000000111724000 CR4: 0000000000750ef0\nPKRU: 55555554\nCall Trace:\n \u0026lt;TASK\u0026gt;\n ? __die_body.cold+0x19/0x27\n ? die+0x2e/0x50\n ? do_trap+0xca/0x110\n ? do_error_trap+0x6a/0x90\n ? kfree+0x2cf/0x2f0\n ? exc_invalid_op+0x50/0x70\n ? kfree+0x2cf/0x2f0\n ? asm_exc_invalid_op+0x1a/0x20\n ? ata_host_alloc+0xf5/0x120 [libata]\n ? ata_host_alloc+0xf5/0x120 [libata]\n ? kfree+0x2cf/0x2f0\n ata_host_alloc+0xf5/0x120 [libata]\n ata_host_alloc_pinfo+0x14/0xa0 [libata]\n ahci_init_one+0x6c9/0xd20 [ahci]\r\n\r\nEnsure that we will not call kfree(host) twice, by performing the kfree()\nonly if the devres_open_group() call failed.(CVE-2024-41087)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\ndrm/nouveau/dispnv04: fix null pointer dereference in nv17_tv_get_hd_modes\r\n\r\nIn nv17_tv_get_hd_modes(), the return value of drm_mode_duplicate() is\nassigned to mode, which will lead to a possible NULL pointer dereference\non failure of drm_mode_duplicate(). The same applies to drm_cvt_mode().\nAdd a check to avoid null pointer dereference.(CVE-2024-41089)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\ntap: add missing verification for short frame\r\n\r\nThe cited commit missed to check against the validity of the frame length\nin the tap_get_user_xdp() path, which could cause a corrupted skb to be\nsent downstack. Even before the skb is transmitted, the\ntap_get_user_xdp()--\u0026gt;skb_set_network_header() may assume the size is more\nthan ETH_HLEN. Once transmitted, this could either cause out-of-bound\naccess beyond the actual length, or confuse the underlayer with incorrect\nor inconsistent header length in the skb metadata.\r\n\r\nIn the alternative path, tap_get_user() already prohibits short frame which\nhas the length less than Ethernet header size from being transmitted.\r\n\r\nThis is to drop any frame shorter than the Ethernet header size just like\nhow tap_get_user() does.\r\n\r\nCVE: CVE-2024-41090(CVE-2024-41090)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\ntun: add missing verification for short frame\r\n\r\nThe cited commit missed to check against the validity of the frame length\nin the tun_xdp_one() path, which could cause a corrupted skb to be sent\ndownstack. Even before the skb is transmitted, the\ntun_xdp_one--\u0026gt;eth_type_trans() may access the Ethernet header although it\ncan be less than ETH_HLEN. Once transmitted, this could either cause\nout-of-bound access beyond the actual length, or confuse the underlayer\nwith incorrect or inconsistent header length in the skb metadata.\r\n\r\nIn the alternative path, tun_get_user() already prohibits short frame which\nhas the length less than Ethernet header size from being transmitted for\nIFF_TAP.\r\n\r\nThis is to drop any frame shorter than the Ethernet header size just like\nhow tun_get_user() does.\r\n\r\nCVE: CVE-2024-41091(CVE-2024-41091)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nusb: atm: cxacru: fix endpoint checking in cxacru_bind()\r\n\r\nSyzbot is still reporting quite an old issue [1] that occurs due to\nincomplete checking of present usb endpoints. As such, wrong\nendpoints types may be used at urb sumbitting stage which in turn\ntriggers a warning in usb_submit_urb().\r\n\r\nFix the issue by verifying that required endpoint types are present\nfor both in and out endpoints, taking into account cmd endpoint type.\r\n\r\nUnfortunately, this patch has not been tested on real hardware.\r\n\r\n[1] Syzbot report:\nusb 1-1: BOGUS urb xfer, pipe 1 != type 3\nWARNING: CPU: 0 PID: 8667 at drivers/usb/core/urb.c:502 usb_submit_urb+0xed2/0x18a0 drivers/usb/core/urb.c:502\nModules linked in:\nCPU: 0 PID: 8667 Comm: kworker/0:4 Not tainted 5.14.0-rc4-syzkaller #0\nHardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011\nWorkqueue: usb_hub_wq hub_event\nRIP: 0010:usb_submit_urb+0xed2/0x18a0 drivers/usb/core/urb.c:502\n...\nCall Trace:\n cxacru_cm+0x3c0/0x8e0 drivers/usb/atm/cxacru.c:649\n cxacru_card_status+0x22/0xd0 drivers/usb/atm/cxacru.c:760\n cxacru_bind+0x7ac/0x11a0 drivers/usb/atm/cxacru.c:1209\n usbatm_usb_probe+0x321/0x1ae0 drivers/usb/atm/usbatm.c:1055\n cxacru_usb_probe+0xdf/0x1e0 drivers/usb/atm/cxacru.c:1363\n usb_probe_interface+0x315/0x7f0 drivers/usb/core/driver.c:396\n call_driver_probe drivers/base/dd.c:517 [inline]\n really_probe+0x23c/0xcd0 drivers/base/dd.c:595\n __driver_probe_device+0x338/0x4d0 drivers/base/dd.c:747\n driver_probe_device+0x4c/0x1a0 drivers/base/dd.c:777\n __device_attach_driver+0x20b/0x2f0 drivers/base/dd.c:894\n bus_for_each_drv+0x15f/0x1e0 drivers/base/bus.c:427\n __device_attach+0x228/0x4a0 drivers/base/dd.c:965\n bus_probe_device+0x1e4/0x290 drivers/base/bus.c:487\n device_add+0xc2f/0x2180 drivers/base/core.c:3354\n usb_set_configuration+0x113a/0x1910 drivers/usb/core/message.c:2170\n usb_generic_driver_probe+0xba/0x100 drivers/usb/core/generic.c:238\n usb_probe_device+0xd9/0x2c0 drivers/usb/core/driver.c:293(CVE-2024-41097)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nbpf: Take return from set_memory_ro() into account with bpf_prog_lock_ro()\r\n\r\nset_memory_ro() can fail, leaving memory unprotected.\r\n\r\nCheck its return and take it into account as an error.(CVE-2024-42068)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nnet: can: j1939: Initialize unused data in j1939_send_one()\r\n\r\nsyzbot reported kernel-infoleak in raw_recvmsg() [1]. j1939_send_one()\ncreates full frame including unused data, but it doesn\u0026apos;t initialize\nit. This causes the kernel-infoleak issue. Fix this by initializing\nunused data.\r\n\r\n[1]\nBUG: KMSAN: kernel-infoleak in instrument_copy_to_user include/linux/instrumented.h:114 [inline]\nBUG: KMSAN: kernel-infoleak in copy_to_user_iter lib/iov_iter.c:24 [inline]\nBUG: KMSAN: kernel-infoleak in iterate_ubuf include/linux/iov_iter.h:29 [inline]\nBUG: KMSAN: kernel-infoleak in iterate_and_advance2 include/linux/iov_iter.h:245 [inline]\nBUG: KMSAN: kernel-infoleak in iterate_and_advance include/linux/iov_iter.h:271 [inline]\nBUG: KMSAN: kernel-infoleak in _copy_to_iter+0x366/0x2520 lib/iov_iter.c:185\n instrument_copy_to_user include/linux/instrumented.h:114 [inline]\n copy_to_user_iter lib/iov_iter.c:24 [inline]\n iterate_ubuf include/linux/iov_iter.h:29 [inline]\n iterate_and_advance2 include/linux/iov_iter.h:245 [inline]\n iterate_and_advance include/linux/iov_iter.h:271 [inline]\n _copy_to_iter+0x366/0x2520 lib/iov_iter.c:185\n copy_to_iter include/linux/uio.h:196 [inline]\n memcpy_to_msg include/linux/skbuff.h:4113 [inline]\n raw_recvmsg+0x2b8/0x9e0 net/can/raw.c:1008\n sock_recvmsg_nosec net/socket.c:1046 [inline]\n sock_recvmsg+0x2c4/0x340 net/socket.c:1068\n ____sys_recvmsg+0x18a/0x620 net/socket.c:2803\n ___sys_recvmsg+0x223/0x840 net/socket.c:2845\n do_recvmmsg+0x4fc/0xfd0 net/socket.c:2939\n __sys_recvmmsg net/socket.c:3018 [inline]\n __do_sys_recvmmsg net/socket.c:3041 [inline]\n __se_sys_recvmmsg net/socket.c:3034 [inline]\n __x64_sys_recvmmsg+0x397/0x490 net/socket.c:3034\n x64_sys_call+0xf6c/0x3b50 arch/x86/include/generated/asm/syscalls_64.h:300\n do_syscall_x64 arch/x86/entry/common.c:52 [inline]\n do_syscall_64+0xcf/0x1e0 arch/x86/entry/common.c:83\n entry_SYSCALL_64_after_hwframe+0x77/0x7f\r\n\r\nUninit was created at:\n slab_post_alloc_hook mm/slub.c:3804 [inline]\n slab_alloc_node mm/slub.c:3845 [inline]\n kmem_cache_alloc_node+0x613/0xc50 mm/slub.c:3888\n kmalloc_reserve+0x13d/0x4a0 net/core/skbuff.c:577\n __alloc_skb+0x35b/0x7a0 net/core/skbuff.c:668\n alloc_skb include/linux/skbuff.h:1313 [inline]\n alloc_skb_with_frags+0xc8/0xbf0 net/core/skbuff.c:6504\n sock_alloc_send_pskb+0xa81/0xbf0 net/core/sock.c:2795\n sock_alloc_send_skb include/net/sock.h:1842 [inline]\n j1939_sk_alloc_skb net/can/j1939/socket.c:878 [inline]\n j1939_sk_send_loop net/can/j1939/socket.c:1142 [inline]\n j1939_sk_sendmsg+0xc0a/0x2730 net/can/j1939/socket.c:1277\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:2584\n ___sys_sendmsg+0x28d/0x3c0 net/socket.c:2638\n __sys_sendmsg net/socket.c:2667 [inline]\n __do_sys_sendmsg net/socket.c:2676 [inline]\n __se_sys_sendmsg net/socket.c:2674 [inline]\n __x64_sys_sendmsg+0x307/0x4a0 net/socket.c:2674\n x64_sys_call+0xc4b/0x3b50 arch/x86/include/generated/asm/syscalls_64.h:47\n do_syscall_x64 arch/x86/entry/common.c:52 [inline]\n do_syscall_64+0xcf/0x1e0 arch/x86/entry/common.c:83\n entry_SYSCALL_64_after_hwframe+0x77/0x7f\r\n\r\nBytes 12-15 of 16 are uninitialized\nMemory access of size 16 starts at ffff888120969690\nData copied to user address 00000000200017c0\r\n\r\nCPU: 1 PID: 5050 Comm: syz-executor198 Not tainted 6.9.0-rc5-syzkaller-00031-g71b1543c83d6 #0\nHardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 03/27/2024(CVE-2024-42076)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nocfs2: fix DIO failure due to insufficient transaction credits\r\n\r\nThe code in ocfs2_dio_end_io_write() estimates number of necessary\ntransaction credits using ocfs2_calc_extend_credits().  This however does\nnot take into account that the IO could be arbitrarily large and can\ncontain arbitrary number of extents.\r\n\r\nExtent tree manipulations do often extend the current transaction but not\nin all of the cases.  For example if we have only single block extents in\nthe tree, ocfs2_mark_extent_written() will end up calling\nocfs2_replace_extent_rec() all the time and we will never extend the\ncurrent transaction and eventually exhaust all the transaction credits if\nthe IO contains many single block extents.  Once that happens a\nWARN_ON(jbd2_handle_buffer_credits(handle) \u0026lt;= 0) is triggered in\njbd2_journal_dirty_metadata() and subsequently OCFS2 aborts in response to\nthis error.  This was actually triggered by one of our customers on a\nheavily fragmented OCFS2 filesystem.\r\n\r\nTo fix the issue make sure the transaction always has enough credits for\none extent insert before each call of ocfs2_mark_extent_written().\r\n\r\nHeming Zhao said:\r\n\r\n------\nPANIC: \u0026quot;Kernel panic - not syncing: OCFS2: (device dm-1): panic forced after error\u0026quot;\r\n\r\nPID: xxx  TASK: xxxx  CPU: 5  COMMAND: \u0026quot;SubmitThread-CA\u0026quot;\n  #0 machine_kexec at ffffffff8c069932\n  #1 __crash_kexec at ffffffff8c1338fa\n  #2 panic at ffffffff8c1d69b9\n  #3 ocfs2_handle_error at ffffffffc0c86c0c [ocfs2]\n  #4 __ocfs2_abort at ffffffffc0c88387 [ocfs2]\n  #5 ocfs2_journal_dirty at ffffffffc0c51e98 [ocfs2]\n  #6 ocfs2_split_extent at ffffffffc0c27ea3 [ocfs2]\n  #7 ocfs2_change_extent_flag at ffffffffc0c28053 [ocfs2]\n  #8 ocfs2_mark_extent_written at ffffffffc0c28347 [ocfs2]\n  #9 ocfs2_dio_end_io_write at ffffffffc0c2bef9 [ocfs2]\n#10 ocfs2_dio_end_io at ffffffffc0c2c0f5 [ocfs2]\n#11 dio_complete at ffffffff8c2b9fa7\n#12 do_blockdev_direct_IO at ffffffff8c2bc09f\n#13 ocfs2_direct_IO at ffffffffc0c2b653 [ocfs2]\n#14 generic_file_direct_write at ffffffff8c1dcf14\n#15 __generic_file_write_iter at ffffffff8c1dd07b\n#16 ocfs2_file_write_iter at ffffffffc0c49f1f [ocfs2]\n#17 aio_write at ffffffff8c2cc72e\n#18 kmem_cache_alloc at ffffffff8c248dde\n#19 do_io_submit at ffffffff8c2ccada\n#20 do_syscall_64 at ffffffff8c004984\n#21 entry_SYSCALL_64_after_hwframe at ffffffff8c8000ba(CVE-2024-42077)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nRDMA/restrack: Fix potential invalid address access\r\n\r\nstruct rdma_restrack_entry\u0026apos;s kern_name was set to KBUILD_MODNAME\nin ib_create_cq(), while if the module exited but forgot del this\nrdma_restrack_entry, it would cause a invalid address access in\nrdma_restrack_clean() when print the owner of this rdma_restrack_entry.\r\n\r\nThese code is used to help find one forgotten PD release in one of the\nULPs. But it is not needed anymore, so delete them.(CVE-2024-42080)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nxdp: Remove WARN() from __xdp_reg_mem_model()\r\n\r\nsyzkaller reports a warning in __xdp_reg_mem_model().\r\n\r\nThe warning occurs only if __mem_id_init_hash_table() returns an error. It\nreturns the error in two cases:\r\n\r\n  1. memory allocation fails;\n  2. rhashtable_init() fails when some fields of rhashtable_params\n     struct are not initialized properly.\r\n\r\nThe second case cannot happen since there is a static const rhashtable_params\nstruct with valid fields. So, warning is only triggered when there is a\nproblem with memory allocation.\r\n\r\nThus, there is no sense in using WARN() to handle this error and it can be\nsafely removed.\r\n\r\nWARNING: CPU: 0 PID: 5065 at net/core/xdp.c:299 __xdp_reg_mem_model+0x2d9/0x650 net/core/xdp.c:299\r\n\r\nCPU: 0 PID: 5065 Comm: syz-executor883 Not tainted 6.8.0-syzkaller-05271-gf99c5f563c17 #0\nHardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 03/27/2024\nRIP: 0010:__xdp_reg_mem_model+0x2d9/0x650 net/core/xdp.c:299\r\n\r\nCall Trace:\n xdp_reg_mem_model+0x22/0x40 net/core/xdp.c:344\n xdp_test_run_setup net/bpf/test_run.c:188 [inline]\n bpf_test_run_xdp_live+0x365/0x1e90 net/bpf/test_run.c:377\n bpf_prog_test_run_xdp+0x813/0x11b0 net/bpf/test_run.c:1267\n bpf_prog_test_run+0x33a/0x3b0 kernel/bpf/syscall.c:4240\n __sys_bpf+0x48d/0x810 kernel/bpf/syscall.c:5649\n __do_sys_bpf kernel/bpf/syscall.c:5738 [inline]\n __se_sys_bpf kernel/bpf/syscall.c:5736 [inline]\n __x64_sys_bpf+0x7c/0x90 kernel/bpf/syscall.c:5736\n do_syscall_64+0xfb/0x240\n entry_SYSCALL_64_after_hwframe+0x6d/0x75\r\n\r\nFound by Linux Verification Center (linuxtesting.org) with syzkaller.(CVE-2024-42082)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nftruncate: pass a signed offset\r\n\r\nThe old ftruncate() syscall, using the 32-bit off_t misses a sign\nextension when called in compat mode on 64-bit architectures.  As a\nresult, passing a negative length accidentally succeeds in truncating\nto file size between 2GiB and 4GiB.\r\n\r\nChanging the type of the compat syscall to the signed compat_off_t\nchanges the behavior so it instead returns -EINVAL.\r\n\r\nThe native entry point, the truncate() syscall and the corresponding\nloff_t based variants are all correct already and do not suffer\nfrom this mistake.(CVE-2024-42084)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\niio: chemical: bme680: Fix overflows in compensate() functions\r\n\r\nThere are cases in the compensate functions of the driver that\nthere could be overflows of variables due to bit shifting ops.\nThese implications were initially discussed here [1] and they\nwere mentioned in log message of Commit 1b3bd8592780 (\u0026quot;iio:\nchemical: Add support for Bosch BME680 sensor\u0026quot;).\r\n\r\n[1]: https://lore.kernel.org/linux-iio/20180728114028.3c1bbe81@archlinux/(CVE-2024-42086)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nASoC: fsl-asoc-card: set priv-\u0026gt;pdev before using it\r\n\r\npriv-\u0026gt;pdev pointer was set after being used in\nfsl_asoc_card_audmux_init().\nMove this assignment at the start of the probe function, so\nsub-functions can correctly use pdev through priv.\r\n\r\nfsl_asoc_card_audmux_init() dereferences priv-\u0026gt;pdev to get access to the\ndev struct, used with dev_err macros.\nAs priv is zero-initialised, there would be a NULL pointer dereference.\nNote that if priv-\u0026gt;dev is dereferenced before assignment but never used,\nfor example if there is no error to be printed, the driver won\u0026apos;t crash\nprobably due to compiler optimisations.(CVE-2024-42089)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\npinctrl: fix deadlock in create_pinctrl() when handling -EPROBE_DEFER\r\n\r\nIn create_pinctrl(), pinctrl_maps_mutex is acquired before calling\nadd_setting(). If add_setting() returns -EPROBE_DEFER, create_pinctrl()\ncalls pinctrl_free(). However, pinctrl_free() attempts to acquire\npinctrl_maps_mutex, which is already held by create_pinctrl(), leading to\na potential deadlock.\r\n\r\nThis patch resolves the issue by releasing pinctrl_maps_mutex before\ncalling pinctrl_free(), preventing the deadlock.\r\n\r\nThis bug was discovered and resolved using Coverity Static Analysis\nSecurity Testing (SAST) by Synopsys, Inc.(CVE-2024-42090)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\ngpio: davinci: Validate the obtained number of IRQs\r\n\r\nValue of pdata-\u0026gt;gpio_unbanked is taken from Device Tree. In case of broken\nDT due to any error this value can be any. Without this value validation\nthere can be out of chips-\u0026gt;irqs array boundaries access in\ndavinci_gpio_probe().\r\n\r\nValidate the obtained nirq value so that it won\u0026apos;t exceed the maximum\nnumber of IRQs per bank.\r\n\r\nFound by Linux Verification Center (linuxtesting.org) with SVACE.(CVE-2024-42092)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nnet/dpaa2: Avoid explicit cpumask var allocation on stack\r\n\r\nFor CONFIG_CPUMASK_OFFSTACK=y kernel, explicit allocation of cpumask\nvariable on stack is not recommended since it can cause potential stack\noverflow.\r\n\r\nInstead, kernel code should always use *cpumask_var API(s) to allocate\ncpumask var in config-neutral way, leaving allocation strategy to\nCONFIG_CPUMASK_OFFSTACK.\r\n\r\nUse *cpumask_var API(s) to address it.(CVE-2024-42093)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nnet/iucv: Avoid explicit cpumask var allocation on stack\r\n\r\nFor CONFIG_CPUMASK_OFFSTACK=y kernel, explicit allocation of cpumask\nvariable on stack is not recommended since it can cause potential stack\noverflow.\r\n\r\nInstead, kernel code should always use *cpumask_var API(s) to allocate\ncpumask var in config-neutral way, leaving allocation strategy to\nCONFIG_CPUMASK_OFFSTACK.\r\n\r\nUse *cpumask_var API(s) to address it.(CVE-2024-42094)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nALSA: emux: improve patch ioctl data validation\r\n\r\nIn load_data(), make the validation of and skipping over the main info\nblock match that in load_guspatch().\r\n\r\nIn load_guspatch(), add checking that the specified patch length matches\nthe actually supplied data, like load_data() already did.(CVE-2024-42097)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\ndrm/nouveau: fix null pointer dereference in nouveau_connector_get_modes\r\n\r\nIn nouveau_connector_get_modes(), the return value of drm_mode_duplicate()\nis assigned to mode, which will lead to a possible NULL pointer\ndereference on failure of drm_mode_duplicate(). Add a check to avoid npd.(CVE-2024-42101)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\ninet_diag: Initialize pad field in struct inet_diag_req_v2\r\n\r\nKMSAN reported uninit-value access in raw_lookup() [1]. Diag for raw\nsockets uses the pad field in struct inet_diag_req_v2 for the\nunderlying protocol. This field corresponds to the sdiag_raw_protocol\nfield in struct inet_diag_req_raw.\r\n\r\ninet_diag_get_exact_compat() converts inet_diag_req to\ninet_diag_req_v2, but leaves the pad field uninitialized. So the issue\noccurs when raw_lookup() accesses the sdiag_raw_protocol field.\r\n\r\nFix this by initializing the pad field in\ninet_diag_get_exact_compat(). Also, do the same fix in\ninet_diag_dump_compat() to avoid the similar issue in the future.\r\n\r\n[1]\nBUG: KMSAN: uninit-value in raw_lookup net/ipv4/raw_diag.c:49 [inline]\nBUG: KMSAN: uninit-value in raw_sock_get+0x657/0x800 net/ipv4/raw_diag.c:71\n raw_lookup net/ipv4/raw_diag.c:49 [inline]\n raw_sock_get+0x657/0x800 net/ipv4/raw_diag.c:71\n raw_diag_dump_one+0xa1/0x660 net/ipv4/raw_diag.c:99\n inet_diag_cmd_exact+0x7d9/0x980\n inet_diag_get_exact_compat net/ipv4/inet_diag.c:1404 [inline]\n inet_diag_rcv_msg_compat+0x469/0x530 net/ipv4/inet_diag.c:1426\n sock_diag_rcv_msg+0x23d/0x740 net/core/sock_diag.c:282\n netlink_rcv_skb+0x537/0x670 net/netlink/af_netlink.c:2564\n sock_diag_rcv+0x35/0x40 net/core/sock_diag.c:297\n netlink_unicast_kernel net/netlink/af_netlink.c:1335 [inline]\n netlink_unicast+0xe74/0x1240 net/netlink/af_netlink.c:1361\n netlink_sendmsg+0x10c6/0x1260 net/netlink/af_netlink.c:1905\n sock_sendmsg_nosec net/socket.c:730 [inline]\n __sock_sendmsg+0x332/0x3d0 net/socket.c:745\n ____sys_sendmsg+0x7f0/0xb70 net/socket.c:2585\n ___sys_sendmsg+0x271/0x3b0 net/socket.c:2639\n __sys_sendmsg net/socket.c:2668 [inline]\n __do_sys_sendmsg net/socket.c:2677 [inline]\n __se_sys_sendmsg net/socket.c:2675 [inline]\n __x64_sys_sendmsg+0x27e/0x4a0 net/socket.c:2675\n x64_sys_call+0x135e/0x3ce0 arch/x86/include/generated/asm/syscalls_64.h:47\n do_syscall_x64 arch/x86/entry/common.c:52 [inline]\n do_syscall_64+0xd9/0x1e0 arch/x86/entry/common.c:83\n entry_SYSCALL_64_after_hwframe+0x77/0x7f\r\n\r\nUninit was stored to memory at:\n raw_sock_get+0x650/0x800 net/ipv4/raw_diag.c:71\n raw_diag_dump_one+0xa1/0x660 net/ipv4/raw_diag.c:99\n inet_diag_cmd_exact+0x7d9/0x980\n inet_diag_get_exact_compat net/ipv4/inet_diag.c:1404 [inline]\n inet_diag_rcv_msg_compat+0x469/0x530 net/ipv4/inet_diag.c:1426\n sock_diag_rcv_msg+0x23d/0x740 net/core/sock_diag.c:282\n netlink_rcv_skb+0x537/0x670 net/netlink/af_netlink.c:2564\n sock_diag_rcv+0x35/0x40 net/core/sock_diag.c:297\n netlink_unicast_kernel net/netlink/af_netlink.c:1335 [inline]\n netlink_unicast+0xe74/0x1240 net/netlink/af_netlink.c:1361\n netlink_sendmsg+0x10c6/0x1260 net/netlink/af_netlink.c:1905\n sock_sendmsg_nosec net/socket.c:730 [inline]\n __sock_sendmsg+0x332/0x3d0 net/socket.c:745\n ____sys_sendmsg+0x7f0/0xb70 net/socket.c:2585\n ___sys_sendmsg+0x271/0x3b0 net/socket.c:2639\n __sys_sendmsg net/socket.c:2668 [inline]\n __do_sys_sendmsg net/socket.c:2677 [inline]\n __se_sys_sendmsg net/socket.c:2675 [inline]\n __x64_sys_sendmsg+0x27e/0x4a0 net/socket.c:2675\n x64_sys_call+0x135e/0x3ce0 arch/x86/include/generated/asm/syscalls_64.h:47\n do_syscall_x64 arch/x86/entry/common.c:52 [inline]\n do_syscall_64+0xd9/0x1e0 arch/x86/entry/common.c:83\n entry_SYSCALL_64_after_hwframe+0x77/0x7f\r\n\r\nLocal variable req.i created at:\n inet_diag_get_exact_compat net/ipv4/inet_diag.c:1396 [inline]\n inet_diag_rcv_msg_compat+0x2a6/0x530 net/ipv4/inet_diag.c:1426\n sock_diag_rcv_msg+0x23d/0x740 net/core/sock_diag.c:282\r\n\r\nCPU: 1 PID: 8888 Comm: syz-executor.6 Not tainted 6.10.0-rc4-00217-g35bb670d65fc #32\nHardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.16.3-2.fc40 04/01/2014(CVE-2024-42106)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\njffs2: Fix potential illegal address access in jffs2_free_inode\r\n\r\nDuring the stress testing of the jffs2 file system,the following\nabnormal printouts were found:\n[ 2430.649000] Unable to handle kernel paging request at virtual address 0069696969696948\n[ 2430.649622] Mem abort info:\n[ 2430.649829]   ESR = 0x96000004\n[ 2430.650115]   EC = 0x25: DABT (current EL), IL = 32 bits\n[ 2430.650564]   SET = 0, FnV = 0\n[ 2430.650795]   EA = 0, S1PTW = 0\n[ 2430.651032]   FSC = 0x04: level 0 translation fault\n[ 2430.651446] Data abort info:\n[ 2430.651683]   ISV = 0, ISS = 0x00000004\n[ 2430.652001]   CM = 0, WnR = 0\n[ 2430.652558] [0069696969696948] address between user and kernel address ranges\n[ 2430.653265] Internal error: Oops: 96000004 [#1] PREEMPT SMP\n[ 2430.654512] CPU: 2 PID: 20919 Comm: cat Not tainted 5.15.25-g512f31242bf6 #33\n[ 2430.655008] Hardware name: linux,dummy-virt (DT)\n[ 2430.655517] pstate: 20000005 (nzCv daif -PAN -UAO -TCO -DIT -SSBS BTYPE=--)\n[ 2430.656142] pc : kfree+0x78/0x348\n[ 2430.656630] lr : jffs2_free_inode+0x24/0x48\n[ 2430.657051] sp : ffff800009eebd10\n[ 2430.657355] x29: ffff800009eebd10 x28: 0000000000000001 x27: 0000000000000000\n[ 2430.658327] x26: ffff000038f09d80 x25: 0080000000000000 x24: ffff800009d38000\n[ 2430.658919] x23: 5a5a5a5a5a5a5a5a x22: ffff000038f09d80 x21: ffff8000084f0d14\n[ 2430.659434] x20: ffff0000bf9a6ac0 x19: 0169696969696940 x18: 0000000000000000\n[ 2430.659969] x17: ffff8000b6506000 x16: ffff800009eec000 x15: 0000000000004000\n[ 2430.660637] x14: 0000000000000000 x13: 00000001000820a1 x12: 00000000000d1b19\n[ 2430.661345] x11: 0004000800000000 x10: 0000000000000001 x9 : ffff8000084f0d14\n[ 2430.662025] x8 : ffff0000bf9a6b40 x7 : ffff0000bf9a6b48 x6 : 0000000003470302\n[ 2430.662695] x5 : ffff00002e41dcc0 x4 : ffff0000bf9aa3b0 x3 : 0000000003470342\n[ 2430.663486] x2 : 0000000000000000 x1 : ffff8000084f0d14 x0 : fffffc0000000000\n[ 2430.664217] Call trace:\n[ 2430.664528]  kfree+0x78/0x348\n[ 2430.664855]  jffs2_free_inode+0x24/0x48\n[ 2430.665233]  i_callback+0x24/0x50\n[ 2430.665528]  rcu_do_batch+0x1ac/0x448\n[ 2430.665892]  rcu_core+0x28c/0x3c8\n[ 2430.666151]  rcu_core_si+0x18/0x28\n[ 2430.666473]  __do_softirq+0x138/0x3cc\n[ 2430.666781]  irq_exit+0xf0/0x110\n[ 2430.667065]  handle_domain_irq+0x6c/0x98\n[ 2430.667447]  gic_handle_irq+0xac/0xe8\n[ 2430.667739]  call_on_irq_stack+0x28/0x54\nThe parameter passed to kfree was 5a5a5a5a, which corresponds to the target field of\nthe jffs_inode_info structure. It was found that all variables in the jffs_inode_info\nstructure were 5a5a5a5a, except for the first member sem. It is suspected that these\nvariables are not initialized because they were set to 5a5a5a5a during memory testing,\nwhich is meant to detect uninitialized memory.The sem variable is initialized in the\nfunction jffs2_i_init_once, while other members are initialized in\nthe function jffs2_init_inode_info.\r\n\r\nThe function jffs2_init_inode_info is called after iget_locked,\nbut in the iget_locked function, the destroy_inode process is triggered,\nwhich releases the inode and consequently, the target member of the inode\nis not initialized.In concurrent high pressure scenarios, iget_locked\nmay enter the destroy_inode branch as described in the code.\r\n\r\nSince the destroy_inode functionality of jffs2 only releases the target,\nthe fix method is to set target to NULL in jffs2_i_init_once.(CVE-2024-42115)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nscsi: qedf: Make qedf_execute_tmf() non-preemptible\r\n\r\nStop calling smp_processor_id() from preemptible code in\nqedf_execute_tmf90.  This results in BUG_ON() when running an RT kernel.\r\n\r\n[ 659.343280] BUG: using smp_processor_id() in preemptible [00000000] code: sg_reset/3646\n[ 659.343282] caller is qedf_execute_tmf+0x8b/0x360 [qedf](CVE-2024-42124)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nleds: mlxreg: Use devm_mutex_init() for mutex initialization\r\n\r\nIn this driver LEDs are registered using devm_led_classdev_register()\nso they are automatically unregistered after module\u0026apos;s remove() is done.\nled_classdev_unregister() calls module\u0026apos;s led_set_brightness() to turn off\nthe LEDs and that callback uses mutex which was destroyed already\nin module\u0026apos;s remove() so use devm API instead.(CVE-2024-42129)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nBluetooth: qca: Fix BT enable failure again for QCA6390 after warm reboot\r\n\r\nCommit 272970be3dab (\u0026quot;Bluetooth: hci_qca: Fix driver shutdown on closed\nserdev\u0026quot;) will cause below regression issue:\r\n\r\nBT can\u0026apos;t be enabled after below steps:\ncold boot -\u0026gt; enable BT -\u0026gt; disable BT -\u0026gt; warm reboot -\u0026gt; BT enable failure\nif property enable-gpios is not configured within DT|ACPI for QCA6390.\r\n\r\nThe commit is to fix a use-after-free issue within qca_serdev_shutdown()\nby adding condition to avoid the serdev is flushed or wrote after closed\nbut also introduces this regression issue regarding above steps since the\nVSC is not sent to reset controller during warm reboot.\r\n\r\nFixed by sending the VSC to reset controller within qca_serdev_shutdown()\nonce BT was ever enabled, and the use-after-free issue is also fixed by\nthis change since the serdev is still opened before it is flushed or wrote.\r\n\r\nVerified by the reported machine Dell XPS 13 9310 laptop over below two\nkernel commits:\ncommit e00fc2700a3f (\u0026quot;Bluetooth: btusb: Fix triggering coredump\nimplementation for QCA\u0026quot;) of bluetooth-next tree.\ncommit b23d98d46d28 (\u0026quot;Bluetooth: btusb: Fix triggering coredump\nimplementation for QCA\u0026quot;) of linus mainline tree.(CVE-2024-42137)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nIB/core: Implement a limit on UMAD receive List\r\n\r\nThe existing behavior of ib_umad, which maintains received MAD\npackets in an unbounded list, poses a risk of uncontrolled growth.\nAs user-space applications extract packets from this list, the rate\nof extraction may not match the rate of incoming packets, leading\nto potential list overflow.\r\n\r\nTo address this, we introduce a limit to the size of the list. After\nconsidering typical scenarios, such as OpenSM processing, which can\nhandle approximately 100k packets per second, and the 1-second retry\ntimeout for most packets, we set the list size limit to 200k. Packets\nreceived beyond this limit are dropped, assuming they are likely timed\nout by the time they are handled by user-space.\r\n\r\nNotably, packets queued on the receive list due to reasons like\ntimed-out sends are preserved even when the list is full.(CVE-2024-42145)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\ns390/pkey: Wipe copies of protected- and secure-keys\r\n\r\nAlthough the clear-key of neither protected- nor secure-keys is\naccessible, this key material should only be visible to the calling\nprocess. So wipe all copies of protected- or secure-keys from stack,\neven in case of an error.(CVE-2024-42155)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nf2fs: check validation of fault attrs in f2fs_build_fault_attr()\r\n\r\n- It missed to check validation of fault attrs in parse_options(),\nlet\u0026apos;s fix to add check condition in f2fs_build_fault_attr().\n- Use f2fs_build_fault_attr() in __sbi_store() to clean up code.(CVE-2024-42160)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nbpf: Avoid uninitialized value in BPF_CORE_READ_BITFIELD\r\n\r\n[Changes from V1:\n - Use a default branch in the switch statement to initialize `val\u0026apos;.]\r\n\r\nGCC warns that `val\u0026apos; may be used uninitialized in the\nBPF_CRE_READ_BITFIELD macro, defined in bpf_core_read.h as:\r\n\r\n\t[...]\n\tunsigned long long val;\t\t\t\t\t\t      \\\n\t[...]\t\t\t\t\t\t\t\t      \\\n\tswitch (__CORE_RELO(s, field, BYTE_SIZE)) {\t\t\t      \\\n\tcase 1: val = *(const unsigned char *)p; break;\t\t\t      \\\n\tcase 2: val = *(const unsigned short *)p; break;\t\t      \\\n\tcase 4: val = *(const unsigned int *)p; break;\t\t\t      \\\n\tcase 8: val = *(const unsigned long long *)p; break;\t\t      \\\n        }       \t\t\t\t\t\t\t      \\\n\t[...]\n\tval;\t\t\t\t\t\t\t\t      \\\n\t}\t\t\t\t\t\t\t\t      \\\r\n\r\nThis patch adds a default entry in the switch statement that sets\n`val\u0026apos; to zero in order to avoid the warning, and random values to be\nused in case __builtin_preserve_field_info returns unexpected values\nfor BPF_FIELD_BYTE_SIZE.\r\n\r\nTested in bpf-next master.\nNo regressions.(CVE-2024-42161)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\ngve: Account for stopped queues when reading NIC stats\r\n\r\nWe now account for the fact that the NIC might send us stats for a\nsubset of queues. Without this change, gve_get_ethtool_stats might make\nan invalid access on the priv-\u0026gt;stats_report-\u0026gt;stats array.(CVE-2024-42162)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nnet: dsa: mv88e6xxx: Correct check for empty list\r\n\r\nSince commit a3c53be55c95 (\u0026quot;net: dsa: mv88e6xxx: Support multiple MDIO\nbusses\u0026quot;) mv88e6xxx_default_mdio_bus() has checked that the\nreturn value of list_first_entry() is non-NULL.\r\n\r\nThis appears to be intended to guard against the list chip-\u0026gt;mdios being\nempty.  However, it is not the correct check as the implementation of\nlist_first_entry is not designed to return NULL for empty lists.\r\n\r\nInstead, use list_first_entry_or_null() which does return NULL if the\nlist is empty.\r\n\r\nFlagged by Smatch.\nCompile tested only.(CVE-2024-42224)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\ndrm/amdgpu: Using uninitialized value *size when calling amdgpu_vce_cs_reloc\r\n\r\nInitialize the size before calling amdgpu_vce_cs_reloc, such as case 0x03000001.\nV2: To really improve the handling we would actually\n   need to have a separate value of 0xffffffff.(Christian)(CVE-2024-42228)","status":"published","published":"2024-08-09T11:07:26Z","modified":"2026-08-18T01:18:33.347974108Z","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-1964","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\ns390/qeth: fix deadlock during failing recovery\r\n\r\nCommit 0b9902c1fcc5 (\u0026quot;s390/qeth: fix deadlock during recovery\u0026quot;) removed\ntaking discipline_mutex inside qeth_do_reset(), fixing potential\ndeadlocks. An error path was missed though, that still takes\ndiscipline_mutex and thus has the original deadlock potential.\r\n\r\nIntermittent deadlocks were seen when a qeth channel path is configured\noffline, causing a race between qeth_do_reset and ccwgroup_remove.\nCall qeth_set_offline() directly in the qeth_do_reset() error case and\nthen a new variant of ccwgroup_set_offline(), without taking\ndiscipline_mutex.(CVE-2021-47382)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nALSA: scarlett2: Add clamp() in scarlett2_mixer_ctl_put()\r\n\r\nEnsure the value passed to scarlett2_mixer_ctl_put() is between 0 and\nSCARLETT2_MIXER_MAX_VALUE so we don\u0026apos;t attempt to access outside\nscarlett2_mixer_values[].(CVE-2023-52674)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nmedia: gspca: cpia1: shift-out-of-bounds in set_flicker\r\n\r\nSyzkaller reported the following issue:\nUBSAN: shift-out-of-bounds in drivers/media/usb/gspca/cpia1.c:1031:27\nshift exponent 245 is too large for 32-bit type \u0026apos;int\u0026apos;\r\n\r\nWhen the value of the variable \u0026quot;sd-\u0026gt;params.exposure.gain\u0026quot; exceeds the\nnumber of bits in an integer, a shift-out-of-bounds error is reported. It\nis triggered because the variable \u0026quot;currentexp\u0026quot; cannot be left-shifted by\nmore than the number of bits in an integer. In order to avoid invalid\nrange during left-shift, the conditional expression is added.(CVE-2023-52764)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nnet: can: j1939: enhanced error handling for tightly received RTS messages in xtp_rx_rts_session_new\r\n\r\nThis patch enhances error handling in scenarios with RTS (Request to\nSend) messages arriving closely. It replaces the less informative WARN_ON_ONCE\nbacktraces with a new error handling method. This provides clearer error\nmessages and allows for the early termination of problematic sessions.\nPreviously, sessions were only released at the end of j1939_xtp_rx_rts().\r\n\r\nPotentially this could be reproduced with something like:\ntestj1939 -r vcan0:0x80 \u0026amp;\nwhile true; do\n\t# send first RTS\n\tcansend vcan0 18EC8090#1014000303002301;\n\t# send second RTS\n\tcansend vcan0 18EC8090#1014000303002301;\n\t# send abort\n\tcansend vcan0 18EC8090#ff00000000002301;\ndone(CVE-2023-52887)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nipvlan: Dont Use skb-\u0026gt;sk in ipvlan_process_v{4,6}_outbound\r\n\r\nRaw packet from PF_PACKET socket ontop of an IPv6-backed ipvlan device will\nhit WARN_ON_ONCE() in sk_mc_loop() through sch_direct_xmit() path.\r\n\r\nWARNING: CPU: 2 PID: 0 at net/core/sock.c:775 sk_mc_loop+0x2d/0x70\nModules linked in: sch_netem ipvlan rfkill cirrus drm_shmem_helper sg drm_kms_helper\nCPU: 2 PID: 0 Comm: swapper/2 Kdump: loaded Not tainted 6.9.0+ #279\nHardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.15.0-1 04/01/2014\nRIP: 0010:sk_mc_loop+0x2d/0x70\nCode: fa 0f 1f 44 00 00 65 0f b7 15 f7 96 a3 4f 31 c0 66 85 d2 75 26 48 85 ff 74 1c\nRSP: 0018:ffffa9584015cd78 EFLAGS: 00010212\nRAX: 0000000000000011 RBX: ffff91e585793e00 RCX: 0000000002c6a001\nRDX: 0000000000000000 RSI: 0000000000000040 RDI: ffff91e589c0f000\nRBP: ffff91e5855bd100 R08: 0000000000000000 R09: 3d00545216f43d00\nR10: ffff91e584fdcc50 R11: 00000060dd8616f4 R12: ffff91e58132d000\nR13: ffff91e584fdcc68 R14: ffff91e5869ce800 R15: ffff91e589c0f000\nFS:  0000000000000000(0000) GS:ffff91e898100000(0000) knlGS:0000000000000000\nCS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033\nCR2: 00007f788f7c44c0 CR3: 0000000008e1a000 CR4: 00000000000006f0\nDR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000\nDR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400\nCall Trace:\n\u0026lt;IRQ\u0026gt;\n ? __warn (kernel/panic.c:693)\n ? sk_mc_loop (net/core/sock.c:760)\n ? report_bug (lib/bug.c:201 lib/bug.c:219)\n ? handle_bug (arch/x86/kernel/traps.c:239)\n ? exc_invalid_op (arch/x86/kernel/traps.c:260 (discriminator 1))\n ? asm_exc_invalid_op (./arch/x86/include/asm/idtentry.h:621)\n ? sk_mc_loop (net/core/sock.c:760)\n ip6_finish_output2 (net/ipv6/ip6_output.c:83 (discriminator 1))\n ? nf_hook_slow (net/netfilter/core.c:626)\n ip6_finish_output (net/ipv6/ip6_output.c:222)\n ? __pfx_ip6_finish_output (net/ipv6/ip6_output.c:215)\n ipvlan_xmit_mode_l3 (drivers/net/ipvlan/ipvlan_core.c:602) ipvlan\n ipvlan_start_xmit (drivers/net/ipvlan/ipvlan_main.c:226) ipvlan\n dev_hard_start_xmit (net/core/dev.c:3594)\n sch_direct_xmit (net/sched/sch_generic.c:343)\n __qdisc_run (net/sched/sch_generic.c:416)\n net_tx_action (net/core/dev.c:5286)\n handle_softirqs (kernel/softirq.c:555)\n __irq_exit_rcu (kernel/softirq.c:589)\n sysvec_apic_timer_interrupt (arch/x86/kernel/apic/apic.c:1043)\r\n\r\nThe warning triggers as this:\npacket_sendmsg\n   packet_snd //skb-\u0026gt;sk is packet sk\n      __dev_queue_xmit\n         __dev_xmit_skb //q-\u0026gt;enqueue is not NULL\n             __qdisc_run\n               sch_direct_xmit\n                 dev_hard_start_xmit\n                   ipvlan_start_xmit\n                      ipvlan_xmit_mode_l3 //l3 mode\n                        ipvlan_process_outbound //vepa flag\n                          ipvlan_process_v6_outbound\n                            ip6_local_out\n                                __ip6_finish_output\n                                  ip6_finish_output2 //multicast packet\n                                    sk_mc_loop //sk-\u0026gt;sk_family is AF_PACKET\r\n\r\nCall ip{6}_local_out() with NULL sk in ipvlan as other tunnels to fix this.(CVE-2024-33621)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nselinux: avoid dereference of garbage after mount failure\r\n\r\nIn case kern_mount() fails and returns an error pointer return in the\nerror branch instead of continuing and dereferencing the error pointer.\r\n\r\nWhile on it drop the never read static variable selinuxfs_mount.(CVE-2024-35904)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\ndrm: vc4: Fix possible null pointer dereference\r\n\r\nIn vc4_hdmi_audio_init() of_get_address() may return\nNULL which is later dereferenced. Fix this bug by adding NULL check.\r\n\r\nFound by Linux Verification Center (linuxtesting.org) with SVACE.(CVE-2024-38546)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nkunit: Fix kthread reference\r\n\r\nThere is a race condition when a kthread finishes after the deadline and\nbefore the call to kthread_stop(), which may lead to use after free.(CVE-2024-38561)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nnet: stmmac: move the EST lock to struct stmmac_priv\r\n\r\nReinitialize the whole EST structure would also reset the mutex\nlock which is embedded in the EST structure, and then trigger\nthe following warning. To address this, move the lock to struct\nstmmac_priv. We also need to reacquire the mutex lock when doing\nthis initialization.\r\n\r\nDEBUG_LOCKS_WARN_ON(lock-\u0026gt;magic != lock)\nWARNING: CPU: 3 PID: 505 at kernel/locking/mutex.c:587 __mutex_lock+0xd84/0x1068\n Modules linked in:\n CPU: 3 PID: 505 Comm: tc Not tainted 6.9.0-rc6-00053-g0106679839f7-dirty #29\n Hardware name: NXP i.MX8MPlus EVK board (DT)\n pstate: 60000005 (nZCv daif -PAN -UAO -TCO -DIT -SSBS BTYPE=--)\n pc : __mutex_lock+0xd84/0x1068\n lr : __mutex_lock+0xd84/0x1068\n sp : ffffffc0864e3570\n x29: ffffffc0864e3570 x28: ffffffc0817bdc78 x27: 0000000000000003\n x26: ffffff80c54f1808 x25: ffffff80c9164080 x24: ffffffc080d723ac\n x23: 0000000000000000 x22: 0000000000000002 x21: 0000000000000000\n x20: 0000000000000000 x19: ffffffc083bc3000 x18: ffffffffffffffff\n x17: ffffffc08117b080 x16: 0000000000000002 x15: ffffff80d2d40000\n x14: 00000000000002da x13: ffffff80d2d404b8 x12: ffffffc082b5a5c8\n x11: ffffffc082bca680 x10: ffffffc082bb2640 x9 : ffffffc082bb2698\n x8 : 0000000000017fe8 x7 : c0000000ffffefff x6 : 0000000000000001\n x5 : ffffff8178fe0d48 x4 : 0000000000000000 x3 : 0000000000000027\n x2 : ffffff8178fe0d50 x1 : 0000000000000000 x0 : 0000000000000000\n Call trace:\n  __mutex_lock+0xd84/0x1068\n  mutex_lock_nested+0x28/0x34\n  tc_setup_taprio+0x118/0x68c\n  stmmac_setup_tc+0x50/0xf0\n  taprio_change+0x868/0xc9c(CVE-2024-38594)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nstm class: Fix a double free in stm_register_device()\r\n\r\nThe put_device(\u0026amp;stm-\u0026gt;dev) call will trigger stm_device_release() which\nfrees \u0026quot;stm\u0026quot; so the vfree(stm) on the next line is a double free.(CVE-2024-38627)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\ndrm/amdgpu: add error handle to avoid out-of-bounds\r\n\r\nif the sdma_v4_0_irq_id_to_seq return -EINVAL, the process should\nbe stop to avoid out-of-bounds read, so directly return -EINVAL.(CVE-2024-39471)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\ndrm/shmem-helper: Fix BUG_ON() on mmap(PROT_WRITE, MAP_PRIVATE)\r\n\r\nLack of check for copy-on-write (COW) mapping in drm_gem_shmem_mmap\nallows users to call mmap with PROT_WRITE and MAP_PRIVATE flag\ncausing a kernel panic due to BUG_ON in vmf_insert_pfn_prot:\nBUG_ON((vma-\u0026gt;vm_flags \u0026amp; VM_PFNMAP) \u0026amp;\u0026amp; is_cow_mapping(vma-\u0026gt;vm_flags));\r\n\r\nReturn -EINVAL early if COW mapping is detected.\r\n\r\nThis bug affects all drm drivers using default shmem helpers.\nIt can be reproduced by this simple example:\nvoid *ptr = mmap(0, size, PROT_WRITE, MAP_PRIVATE, fd, mmap_offset);\nptr[0] = 0;(CVE-2024-39497)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nax25: Fix refcount imbalance on inbound connections\r\n\r\nWhen releasing a socket in ax25_release(), we call netdev_put() to\ndecrease the refcount on the associated ax.25 device. However, the\nexecution path for accepting an incoming connection never calls\nnetdev_hold(). This imbalance leads to refcount errors, and ultimately\nto kernel crashes.\r\n\r\nA typical call trace for the above situation will start with one of the\nfollowing errors:\r\n\r\n    refcount_t: decrement hit 0; leaking memory.\n    refcount_t: underflow; use-after-free.\r\n\r\nAnd will then have a trace like:\r\n\r\n    Call Trace:\n    \u0026lt;TASK\u0026gt;\n    ? show_regs+0x64/0x70\n    ? __warn+0x83/0x120\n    ? refcount_warn_saturate+0xb2/0x100\n    ? report_bug+0x158/0x190\n    ? prb_read_valid+0x20/0x30\n    ? handle_bug+0x3e/0x70\n    ? exc_invalid_op+0x1c/0x70\n    ? asm_exc_invalid_op+0x1f/0x30\n    ? refcount_warn_saturate+0xb2/0x100\n    ? refcount_warn_saturate+0xb2/0x100\n    ax25_release+0x2ad/0x360\n    __sock_release+0x35/0xa0\n    sock_close+0x19/0x20\n    [...]\r\n\r\nOn reboot (or any attempt to remove the interface), the kernel gets\nstuck in an infinite loop:\r\n\r\n    unregister_netdevice: waiting for ax0 to become free. Usage count = 0\r\n\r\nThis patch corrects these issues by ensuring that we call netdev_hold()\nand ax25_dev_hold() for new connections in ax25_accept(). This makes the\nlogic leading to ax25_accept() match the logic for ax25_bind(): in both\ncases we increment the refcount, which is ultimately decremented in\nax25_release().(CVE-2024-40910)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nKVM: Fix a data race on last_boosted_vcpu in kvm_vcpu_on_spin()\r\n\r\nUse {READ,WRITE}_ONCE() to access kvm-\u0026gt;last_boosted_vcpu to ensure the\nloads and stores are atomic.  In the extremely unlikely scenario the\ncompiler tears the stores, it\u0026apos;s theoretically possible for KVM to attempt\nto get a vCPU using an out-of-bounds index, e.g. if the write is split\ninto multiple 8-bit stores, and is paired with a 32-bit load on a VM with\n257 vCPUs:\r\n\r\n  CPU0                              CPU1\n  last_boosted_vcpu = 0xff;\r\n\r\n                                    (last_boosted_vcpu = 0x100)\n                                    last_boosted_vcpu[15:8] = 0x01;\n  i = (last_boosted_vcpu = 0x1ff)\n                                    last_boosted_vcpu[7:0] = 0x00;\r\n\r\n  vcpu = kvm-\u0026gt;vcpu_array[0x1ff];\r\n\r\nAs detected by KCSAN:\r\n\r\n  BUG: KCSAN: data-race in kvm_vcpu_on_spin [kvm] / kvm_vcpu_on_spin [kvm]\r\n\r\n  write to 0xffffc90025a92344 of 4 bytes by task 4340 on cpu 16:\n  kvm_vcpu_on_spin (arch/x86/kvm/../../../virt/kvm/kvm_main.c:4112) kvm\n  handle_pause (arch/x86/kvm/vmx/vmx.c:5929) kvm_intel\n  vmx_handle_exit (arch/x86/kvm/vmx/vmx.c:?\n\t\t arch/x86/kvm/vmx/vmx.c:6606) kvm_intel\n  vcpu_run (arch/x86/kvm/x86.c:11107 arch/x86/kvm/x86.c:11211) kvm\n  kvm_arch_vcpu_ioctl_run (arch/x86/kvm/x86.c:?) kvm\n  kvm_vcpu_ioctl (arch/x86/kvm/../../../virt/kvm/kvm_main.c:?) kvm\n  __se_sys_ioctl (fs/ioctl.c:52 fs/ioctl.c:904 fs/ioctl.c:890)\n  __x64_sys_ioctl (fs/ioctl.c:890)\n  x64_sys_call (arch/x86/entry/syscall_64.c:33)\n  do_syscall_64 (arch/x86/entry/common.c:?)\n  entry_SYSCALL_64_after_hwframe (arch/x86/entry/entry_64.S:130)\r\n\r\n  read to 0xffffc90025a92344 of 4 bytes by task 4342 on cpu 4:\n  kvm_vcpu_on_spin (arch/x86/kvm/../../../virt/kvm/kvm_main.c:4069) kvm\n  handle_pause (arch/x86/kvm/vmx/vmx.c:5929) kvm_intel\n  vmx_handle_exit (arch/x86/kvm/vmx/vmx.c:?\n\t\t\tarch/x86/kvm/vmx/vmx.c:6606) kvm_intel\n  vcpu_run (arch/x86/kvm/x86.c:11107 arch/x86/kvm/x86.c:11211) kvm\n  kvm_arch_vcpu_ioctl_run (arch/x86/kvm/x86.c:?) kvm\n  kvm_vcpu_ioctl (arch/x86/kvm/../../../virt/kvm/kvm_main.c:?) kvm\n  __se_sys_ioctl (fs/ioctl.c:52 fs/ioctl.c:904 fs/ioctl.c:890)\n  __x64_sys_ioctl (fs/ioctl.c:890)\n  x64_sys_call (arch/x86/entry/syscall_64.c:33)\n  do_syscall_64 (arch/x86/entry/common.c:?)\n  entry_SYSCALL_64_after_hwframe (arch/x86/entry/entry_64.S:130)\r\n\r\n  value changed: 0x00000012 -\u0026gt; 0x00000000(CVE-2024-40953)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\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\nipv6: prevent possible NULL deref in fib6_nh_init()\r\n\r\nsyzbot reminds us that in6_dev_get() can return NULL.\r\n\r\nfib6_nh_init()\n    ip6_validate_gw(  \u0026amp;idev  )\n        ip6_route_check_nh(  idev  )\n            *idev = in6_dev_get(dev); // can be NULL\r\n\r\nOops: general protection fault, probably for non-canonical address 0xdffffc00000000bc: 0000 [#1] PREEMPT SMP KASAN PTI\nKASAN: null-ptr-deref in range [0x00000000000005e0-0x00000000000005e7]\nCPU: 0 PID: 11237 Comm: syz-executor.3 Not tainted 6.10.0-rc2-syzkaller-00249-gbe27b8965297 #0\nHardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 06/07/2024\n RIP: 0010:fib6_nh_init+0x640/0x2160 net/ipv6/route.c:3606\nCode: 00 00 fc ff df 4c 8b 64 24 58 48 8b 44 24 28 4c 8b 74 24 30 48 89 c1 48 89 44 24 28 48 8d 98 e0 05 00 00 48 89 d8 48 c1 e8 03 \u0026lt;42\u0026gt; 0f b6 04 38 84 c0 0f 85 b3 17 00 00 8b 1b 31 ff 89 de e8 b8 8b\nRSP: 0018:ffffc900032775a0 EFLAGS: 00010202\nRAX: 00000000000000bc RBX: 00000000000005e0 RCX: 0000000000000000\nRDX: 0000000000000010 RSI: ffffc90003277a54 RDI: ffff88802b3a08d8\nRBP: ffffc900032778b0 R08: 00000000000002fc R09: 0000000000000000\nR10: 00000000000002fc R11: 0000000000000000 R12: ffff88802b3a08b8\nR13: 1ffff9200064eec8 R14: ffffc90003277a00 R15: dffffc0000000000\nFS:  00007f940feb06c0(0000) GS:ffff8880b9400000(0000) knlGS:0000000000000000\nCS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033\nCR2: 0000000000000000 CR3: 00000000245e8000 CR4: 00000000003506f0\nDR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000\nDR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400\nCall Trace:\n \u0026lt;TASK\u0026gt;\n  ip6_route_info_create+0x99e/0x12b0 net/ipv6/route.c:3809\n  ip6_route_add+0x28/0x160 net/ipv6/route.c:3853\n  ipv6_route_ioctl+0x588/0x870 net/ipv6/route.c:4483\n  inet6_ioctl+0x21a/0x280 net/ipv6/af_inet6.c:579\n  sock_do_ioctl+0x158/0x460 net/socket.c:1222\n  sock_ioctl+0x629/0x8e0 net/socket.c:1341\n  vfs_ioctl fs/ioctl.c:51 [inline]\n  __do_sys_ioctl fs/ioctl.c:907 [inline]\n  __se_sys_ioctl+0xfc/0x170 fs/ioctl.c:893\n  do_syscall_x64 arch/x86/entry/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:0x7f940f07cea9(CVE-2024-40961)\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\nssb: Fix potential NULL pointer dereference in ssb_device_uevent()\r\n\r\nThe ssb_device_uevent() function first attempts to convert the \u0026apos;dev\u0026apos; pointer\nto \u0026apos;struct ssb_device *\u0026apos;. However, it mistakenly dereferences \u0026apos;dev\u0026apos; before\nperforming the NULL check, potentially leading to a NULL pointer\ndereference if \u0026apos;dev\u0026apos; is NULL.\r\n\r\nTo fix this issue, move the NULL check before dereferencing the \u0026apos;dev\u0026apos; pointer,\nensuring that the pointer is valid before attempting to use it.\r\n\r\nFound by Linux Verification Center (linuxtesting.org) with SVACE.(CVE-2024-40982)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\ndrm/radeon: fix UBSAN warning in kv_dpm.c\r\n\r\nAdds bounds check for sumo_vid_mapping_entry.(CVE-2024-40988)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nnet: ena: Add validation for completion descriptors consistency\r\n\r\nValidate that `first` flag is set only for the first\ndescriptor in multi-buffer packets.\nIn case of an invalid descriptor, a reset will occur.\nA new reset reason for RX data corruption has been added.(CVE-2024-40999)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nxfs: don\u0026apos;t walk off the end of a directory data block\r\n\r\nThis adds sanity checks for xfs_dir2_data_unused and xfs_dir2_data_entry\nto make sure don\u0026apos;t stray beyond valid memory region. Before patching, the\nloop simply checks that the start offset of the dup and dep is within the\nrange. So in a crafted image, if last entry is xfs_dir2_data_unused, we\ncan change dup-\u0026gt;length to dup-\u0026gt;length-1 and leave 1 byte of space. In the\nnext traversal, this space will be considered as dup or dep. We may\nencounter an out of bound read when accessing the fixed members.\r\n\r\nIn the patch, we make sure that the remaining bytes large enough to hold\nan unused entry before accessing xfs_dir2_data_unused and\nxfs_dir2_data_unused is XFS_DIR2_DATA_ALIGN byte aligned. We also make\nsure that the remaining bytes large enough to hold a dirent with a\nsingle-byte name before accessing xfs_dir2_data_entry.(CVE-2024-41013)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nxfs: add bounds checking to xlog_recover_process_data\r\n\r\nThere is a lack of verification of the space occupied by fixed members\nof xlog_op_header in the xlog_recover_process_data.\r\n\r\nWe can create a crafted image to trigger an out of bounds read by\nfollowing these steps:\n    1) Mount an image of xfs, and do some file operations to leave records\n    2) Before umounting, copy the image for subsequent steps to simulate\n       abnormal exit. Because umount will ensure that tail_blk and\n       head_blk are the same, which will result in the inability to enter\n       xlog_recover_process_data\n    3) Write a tool to parse and modify the copied image in step 2\n    4) Make the end of the xlog_op_header entries only 1 byte away from\n       xlog_rec_header-\u0026gt;h_size\n    5) xlog_rec_header-\u0026gt;h_num_logops++\n    6) Modify xlog_rec_header-\u0026gt;h_crc\r\n\r\nFix:\nAdd a check to make sure there is sufficient space to access fixed members\nof xlog_op_header.(CVE-2024-41014)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nfs/ntfs3: Validate ff offset\r\n\r\nThis adds sanity checks for ff offset. There is a check\non rt-\u0026gt;first_free at first, but walking through by ff\nwithout any check. If the second ff is a large offset.\nWe may encounter an out-of-bound read.(CVE-2024-41019)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nfilelock: Fix fcntl/close race recovery compat path\r\n\r\nWhen I wrote commit 3cad1bc01041 (\u0026quot;filelock: Remove locks reliably when\nfcntl/close race is detected\u0026quot;), I missed that there are two copies of the\ncode I was patching: The normal version, and the version for 64-bit offsets\non 32-bit kernels.\nThanks to Greg KH for stumbling over this while doing the stable\nbackport...\r\n\r\nApply exactly the same fix to the compat path for 32-bit kernels.(CVE-2024-41020)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\ndrm/amdgpu: Fix signedness bug in sdma_v4_0_process_trap_irq()\r\n\r\nThe \u0026quot;instance\u0026quot; variable needs to be signed for the error handling to work.(CVE-2024-41022)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nsched/deadline: Fix task_struct reference leak\r\n\r\nDuring the execution of the following stress test with linux-rt:\r\n\r\nstress-ng --cyclic 30 --timeout 30 --minimize --quiet\r\n\r\nkmemleak frequently reported a memory leak concerning the task_struct:\r\n\r\nunreferenced object 0xffff8881305b8000 (size 16136):\n  comm \u0026quot;stress-ng\u0026quot;, pid 614, jiffies 4294883961 (age 286.412s)\n  object hex dump (first 32 bytes):\n    02 40 00 00 00 00 00 00 00 00 00 00 00 00 00 00  .@..............\n    00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................\n  debug hex dump (first 16 bytes):\n    53 09 00 00 00 00 00 00 00 00 00 00 00 00 00 00  S...............\n  backtrace:\n    [\u0026lt;00000000046b6790\u0026gt;] dup_task_struct+0x30/0x540\n    [\u0026lt;00000000c5ca0f0b\u0026gt;] copy_process+0x3d9/0x50e0\n    [\u0026lt;00000000ced59777\u0026gt;] kernel_clone+0xb0/0x770\n    [\u0026lt;00000000a50befdc\u0026gt;] __do_sys_clone+0xb6/0xf0\n    [\u0026lt;000000001dbf2008\u0026gt;] do_syscall_64+0x5d/0xf0\n    [\u0026lt;00000000552900ff\u0026gt;] entry_SYSCALL_64_after_hwframe+0x6e/0x76\r\n\r\nThe issue occurs in start_dl_timer(), which increments the task_struct\nreference count and sets a timer. The timer callback, dl_task_timer,\nis supposed to decrement the reference count upon expiration. However,\nif enqueue_task_dl() is called before the timer expires and cancels it,\nthe reference count is not decremented, leading to the leak.\r\n\r\nThis patch fixes the reference leak by ensuring the task_struct\nreference count is properly decremented when the timer is canceled.(CVE-2024-41023)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nFix userfaultfd_api to return EINVAL as expected\r\n\r\nCurrently if we request a feature that is not set in the Kernel config we\nfail silently and return all the available features.  However, the man\npage indicates we should return an EINVAL.\r\n\r\nWe need to fix this issue since we can end up with a Kernel warning should\na program request the feature UFFD_FEATURE_WP_UNPOPULATED on a kernel with\nthe config not set with this feature.\r\n\r\n [  200.812896] WARNING: CPU: 91 PID: 13634 at mm/memory.c:1660 zap_pte_range+0x43d/0x660\n [  200.820738] Modules linked in:\n [  200.869387] CPU: 91 PID: 13634 Comm: userfaultfd Kdump: loaded Not tainted 6.9.0-rc5+ #8\n [  200.877477] Hardware name: Dell Inc. PowerEdge R6525/0N7YGH, BIOS 2.7.3 03/30/2022\n [  200.885052] RIP: 0010:zap_pte_range+0x43d/0x660(CVE-2024-41027)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nnet/sched: Fix UAF when resolving a clash\r\n\r\nKASAN reports the following UAF:\r\n\r\n BUG: KASAN: slab-use-after-free in tcf_ct_flow_table_process_conn+0x12b/0x380 [act_ct]\n Read of size 1 at addr ffff888c07603600 by task handler130/6469\r\n\r\n Call Trace:\n  \u0026lt;IRQ\u0026gt;\n  dump_stack_lvl+0x48/0x70\n  print_address_description.constprop.0+0x33/0x3d0\n  print_report+0xc0/0x2b0\n  kasan_report+0xd0/0x120\n  __asan_load1+0x6c/0x80\n  tcf_ct_flow_table_process_conn+0x12b/0x380 [act_ct]\n  tcf_ct_act+0x886/0x1350 [act_ct]\n  tcf_action_exec+0xf8/0x1f0\n  fl_classify+0x355/0x360 [cls_flower]\n  __tcf_classify+0x1fd/0x330\n  tcf_classify+0x21c/0x3c0\n  sch_handle_ingress.constprop.0+0x2c5/0x500\n  __netif_receive_skb_core.constprop.0+0xb25/0x1510\n  __netif_receive_skb_list_core+0x220/0x4c0\n  netif_receive_skb_list_internal+0x446/0x620\n  napi_complete_done+0x157/0x3d0\n  gro_cell_poll+0xcf/0x100\n  __napi_poll+0x65/0x310\n  net_rx_action+0x30c/0x5c0\n  __do_softirq+0x14f/0x491\n  __irq_exit_rcu+0x82/0xc0\n  irq_exit_rcu+0xe/0x20\n  common_interrupt+0xa1/0xb0\n  \u0026lt;/IRQ\u0026gt;\n  \u0026lt;TASK\u0026gt;\n  asm_common_interrupt+0x27/0x40\r\n\r\n Allocated by task 6469:\n  kasan_save_stack+0x38/0x70\n  kasan_set_track+0x25/0x40\n  kasan_save_alloc_info+0x1e/0x40\n  __kasan_krealloc+0x133/0x190\n  krealloc+0xaa/0x130\n  nf_ct_ext_add+0xed/0x230 [nf_conntrack]\n  tcf_ct_act+0x1095/0x1350 [act_ct]\n  tcf_action_exec+0xf8/0x1f0\n  fl_classify+0x355/0x360 [cls_flower]\n  __tcf_classify+0x1fd/0x330\n  tcf_classify+0x21c/0x3c0\n  sch_handle_ingress.constprop.0+0x2c5/0x500\n  __netif_receive_skb_core.constprop.0+0xb25/0x1510\n  __netif_receive_skb_list_core+0x220/0x4c0\n  netif_receive_skb_list_internal+0x446/0x620\n  napi_complete_done+0x157/0x3d0\n  gro_cell_poll+0xcf/0x100\n  __napi_poll+0x65/0x310\n  net_rx_action+0x30c/0x5c0\n  __do_softirq+0x14f/0x491\r\n\r\n Freed by task 6469:\n  kasan_save_stack+0x38/0x70\n  kasan_set_track+0x25/0x40\n  kasan_save_free_info+0x2b/0x60\n  ____kasan_slab_free+0x180/0x1f0\n  __kasan_slab_free+0x12/0x30\n  slab_free_freelist_hook+0xd2/0x1a0\n  __kmem_cache_free+0x1a2/0x2f0\n  kfree+0x78/0x120\n  nf_conntrack_free+0x74/0x130 [nf_conntrack]\n  nf_ct_destroy+0xb2/0x140 [nf_conntrack]\n  __nf_ct_resolve_clash+0x529/0x5d0 [nf_conntrack]\n  nf_ct_resolve_clash+0xf6/0x490 [nf_conntrack]\n  __nf_conntrack_confirm+0x2c6/0x770 [nf_conntrack]\n  tcf_ct_act+0x12ad/0x1350 [act_ct]\n  tcf_action_exec+0xf8/0x1f0\n  fl_classify+0x355/0x360 [cls_flower]\n  __tcf_classify+0x1fd/0x330\n  tcf_classify+0x21c/0x3c0\n  sch_handle_ingress.constprop.0+0x2c5/0x500\n  __netif_receive_skb_core.constprop.0+0xb25/0x1510\n  __netif_receive_skb_list_core+0x220/0x4c0\n  netif_receive_skb_list_internal+0x446/0x620\n  napi_complete_done+0x157/0x3d0\n  gro_cell_poll+0xcf/0x100\n  __napi_poll+0x65/0x310\n  net_rx_action+0x30c/0x5c0\n  __do_softirq+0x14f/0x491\r\n\r\nThe ct may be dropped if a clash has been resolved but is still passed to\nthe tcf_ct_flow_table_process_conn function for further usage. This issue\ncan be fixed by retrieving ct from skb again after confirming conntrack.(CVE-2024-41040)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nudp: Set SOCK_RCU_FREE earlier in udp_lib_get_port().\r\n\r\nsyzkaller triggered the warning [0] in udp_v4_early_demux().\r\n\r\nIn udp_v[46]_early_demux() and sk_lookup(), we do not touch the refcount\nof the looked-up sk and use sock_pfree() as skb-\u0026gt;destructor, so we check\nSOCK_RCU_FREE to ensure that the sk is safe to access during the RCU grace\nperiod.\r\n\r\nCurrently, SOCK_RCU_FREE is flagged for a bound socket after being put\ninto the hash table.  Moreover, the SOCK_RCU_FREE check is done too early\nin udp_v[46]_early_demux() and sk_lookup(), so there could be a small race\nwindow:\r\n\r\n  CPU1                                 CPU2\n  ----                                 ----\n  udp_v4_early_demux()                 udp_lib_get_port()\n  |                                    |- hlist_add_head_rcu()\n  |- sk = __udp4_lib_demux_lookup()    |\n  |- DEBUG_NET_WARN_ON_ONCE(sk_is_refcounted(sk));\n                                       `- sock_set_flag(sk, SOCK_RCU_FREE)\r\n\r\nWe had the same bug in TCP and fixed it in commit 871019b22d1b (\u0026quot;net:\nset SOCK_RCU_FREE before inserting socket into hashtable\u0026quot;).\r\n\r\nLet\u0026apos;s apply the same fix for UDP.\r\n\r\n[0]:\nWARNING: CPU: 0 PID: 11198 at net/ipv4/udp.c:2599 udp_v4_early_demux+0x481/0xb70 net/ipv4/udp.c:2599\nModules linked in:\nCPU: 0 PID: 11198 Comm: syz-executor.1 Not tainted 6.9.0-g93bda33046e7 #13\nHardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS rel-1.16.0-0-gd239552ce722-prebuilt.qemu.org 04/01/2014\nRIP: 0010:udp_v4_early_demux+0x481/0xb70 net/ipv4/udp.c:2599\nCode: c5 7a 15 fe bb 01 00 00 00 44 89 e9 31 ff d3 e3 81 e3 bf ef ff ff 89 de e8 2c 74 15 fe 85 db 0f 85 02 06 00 00 e8 9f 7a 15 fe \u0026lt;0f\u0026gt; 0b e8 98 7a 15 fe 49 8d 7e 60 e8 4f 39 2f fe 49 c7 46 60 20 52\nRSP: 0018:ffffc9000ce3fa58 EFLAGS: 00010293\nRAX: 0000000000000000 RBX: 0000000000000000 RCX: ffffffff8318c92c\nRDX: ffff888036ccde00 RSI: ffffffff8318c2f1 RDI: 0000000000000001\nRBP: ffff88805a2dd6e0 R08: 0000000000000001 R09: 0000000000000000\nR10: 0000000000000000 R11: 0001ffffffffffff R12: ffff88805a2dd680\nR13: 0000000000000007 R14: ffff88800923f900 R15: ffff88805456004e\nFS:  00007fc449127640(0000) GS:ffff88807dc00000(0000) knlGS:0000000000000000\nCS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033\nCR2: 00007fc449126e38 CR3: 000000003de4b002 CR4: 0000000000770ef0\nDR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000\nDR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000600\nPKRU: 55555554\nCall Trace:\n \u0026lt;TASK\u0026gt;\n ip_rcv_finish_core.constprop.0+0xbdd/0xd20 net/ipv4/ip_input.c:349\n ip_rcv_finish+0xda/0x150 net/ipv4/ip_input.c:447\n NF_HOOK include/linux/netfilter.h:314 [inline]\n NF_HOOK include/linux/netfilter.h:308 [inline]\n ip_rcv+0x16c/0x180 net/ipv4/ip_input.c:569\n __netif_receive_skb_one_core+0xb3/0xe0 net/core/dev.c:5624\n __netif_receive_skb+0x21/0xd0 net/core/dev.c:5738\n netif_receive_skb_internal net/core/dev.c:5824 [inline]\n netif_receive_skb+0x271/0x300 net/core/dev.c:5884\n tun_rx_batched drivers/net/tun.c:1549 [inline]\n tun_get_user+0x24db/0x2c50 drivers/net/tun.c:2002\n tun_chr_write_iter+0x107/0x1a0 drivers/net/tun.c:2048\n new_sync_write fs/read_write.c:497 [inline]\n vfs_write+0x76f/0x8d0 fs/read_write.c:590\n ksys_write+0xbf/0x190 fs/read_write.c:643\n __do_sys_write fs/read_write.c:655 [inline]\n __se_sys_write fs/read_write.c:652 [inline]\n __x64_sys_write+0x41/0x50 fs/read_write.c:652\n x64_sys_call+0xe66/0x1990 arch/x86/include/generated/asm/syscalls_64.h:2\n do_syscall_x64 arch/x86/entry/common.c:52 [inline]\n do_syscall_64+0x4b/0x110 arch/x86/entry/common.c:83\n entry_SYSCALL_64_after_hwframe+0x4b/0x53\nRIP: 0033:0x7fc44a68bc1f\nCode: 89 54 24 18 48 89 74 24 10 89 7c 24 08 e8 e9 cf f5 ff 48 8b 54 24 18 48 8b 74 24 10 41 89 c0 8b 7c 24 08 b8 01 00 00 00 0f 05 \u0026lt;48\u0026gt; 3d 00 f0 ff ff 77 31 44 89 c7 48 89 44 24 08 e8 3c d0 f5 ff 48\nRSP: 002b:00007fc449126c90 EFLAGS: 00000293 ORIG_RAX: 0000000000000001\nRAX: ffffffffffffffda RBX: 00000000004bc050 RCX: 00007fc44a68bc1f\nR\n---truncated---(CVE-2024-41041)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nppp: reject claimed-as-LCP but actually malformed packets\r\n\r\nSince \u0026apos;ppp_async_encode()\u0026apos; assumes valid LCP packets (with code\nfrom 1 to 7 inclusive), add \u0026apos;ppp_check_packet()\u0026apos; to ensure that\nLCP packet has an actual body beyond PPP_LCP header bytes, and\nreject claimed-as-LCP but actually malformed data otherwise.(CVE-2024-41044)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nskmsg: Skip zero length skb in sk_msg_recvmsg\r\n\r\nWhen running BPF selftests (./test_progs -t sockmap_basic) on a Loongarch\nplatform, the following kernel panic occurs:\r\n\r\n  [...]\n  Oops[#1]:\n  CPU: 22 PID: 2824 Comm: test_progs Tainted: G           OE  6.10.0-rc2+ #18\n  Hardware name: LOONGSON Dabieshan/Loongson-TC542F0, BIOS Loongson-UDK2018\n     ... ...\n     ra: 90000000048bf6c0 sk_msg_recvmsg+0x120/0x560\n    ERA: 9000000004162774 copy_page_to_iter+0x74/0x1c0\n   CRMD: 000000b0 (PLV0 -IE -DA +PG DACF=CC DACM=CC -WE)\n   PRMD: 0000000c (PPLV0 +PIE +PWE)\n   EUEN: 00000007 (+FPE +SXE +ASXE -BTE)\n   ECFG: 00071c1d (LIE=0,2-4,10-12 VS=7)\n  ESTAT: 00010000 [PIL] (IS= ECode=1 EsubCode=0)\n   BADV: 0000000000000040\n   PRID: 0014c011 (Loongson-64bit, Loongson-3C5000)\n  Modules linked in: bpf_testmod(OE) xt_CHECKSUM xt_MASQUERADE xt_conntrack\n  Process test_progs (pid: 2824, threadinfo=0000000000863a31, task=...)\n  Stack : ...\n  Call Trace:\n  [\u0026lt;9000000004162774\u0026gt;] copy_page_to_iter+0x74/0x1c0\n  [\u0026lt;90000000048bf6c0\u0026gt;] sk_msg_recvmsg+0x120/0x560\n  [\u0026lt;90000000049f2b90\u0026gt;] tcp_bpf_recvmsg_parser+0x170/0x4e0\n  [\u0026lt;90000000049aae34\u0026gt;] inet_recvmsg+0x54/0x100\n  [\u0026lt;900000000481ad5c\u0026gt;] sock_recvmsg+0x7c/0xe0\n  [\u0026lt;900000000481e1a8\u0026gt;] __sys_recvfrom+0x108/0x1c0\n  [\u0026lt;900000000481e27c\u0026gt;] sys_recvfrom+0x1c/0x40\n  [\u0026lt;9000000004c076ec\u0026gt;] do_syscall+0x8c/0xc0\n  [\u0026lt;9000000003731da4\u0026gt;] handle_syscall+0xc4/0x160\n  Code: ...\n  ---[ end trace 0000000000000000 ]---\n  Kernel panic - not syncing: Fatal exception\n  Kernel relocated by 0x3510000\n   .text @ 0x9000000003710000\n   .data @ 0x9000000004d70000\n   .bss  @ 0x9000000006469400\n  ---[ end Kernel panic - not syncing: Fatal exception ]---\n  [...]\r\n\r\nThis crash happens every time when running sockmap_skb_verdict_shutdown\nsubtest in sockmap_basic.\r\n\r\nThis crash is because a NULL pointer is passed to page_address() in the\nsk_msg_recvmsg(). Due to the different implementations depending on the\narchitecture, page_address(NULL) will trigger a panic on Loongarch\nplatform but not on x86 platform. So this bug was hidden on x86 platform\nfor a while, but now it is exposed on Loongarch platform. The root cause\nis that a zero length skb (skb-\u0026gt;len == 0) was put on the queue.\r\n\r\nThis zero length skb is a TCP FIN packet, which was sent by shutdown(),\ninvoked in test_sockmap_skb_verdict_shutdown():\r\n\r\n\tshutdown(p1, SHUT_WR);\r\n\r\nIn this case, in sk_psock_skb_ingress_enqueue(), num_sge is zero, and no\npage is put to this sge (see sg_set_page in sg_set_page), but this empty\nsge is queued into ingress_msg list.\r\n\r\nAnd in sk_msg_recvmsg(), this empty sge is used, and a NULL page is got by\nsg_page(sge). Pass this NULL page to copy_page_to_iter(), which passes it\nto kmap_local_page() and to page_address(), then kernel panics.\r\n\r\nTo solve this, we should skip this zero length skb. So in sk_msg_recvmsg(),\nif copy is zero, that means it\u0026apos;s a zero length skb, skip invoking\ncopy_page_to_iter(). We are using the EFAULT return triggered by\ncopy_page_to_iter to check for is_fin in tcp_bpf.c.(CVE-2024-41048)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nbluetooth/l2cap: sync sock recv cb and release\r\n\r\nThe problem occurs between the system call to close the sock and hci_rx_work,\nwhere the former releases the sock and the latter accesses it without lock protection.\r\n\r\n           CPU0                       CPU1\n           ----                       ----\n           sock_close                 hci_rx_work\n\t   l2cap_sock_release         hci_acldata_packet\n\t   l2cap_sock_kill            l2cap_recv_frame\n\t   sk_free                    l2cap_conless_channel\n\t                              l2cap_sock_recv_cb\r\n\r\nIf hci_rx_work processes the data that needs to be received before the sock is\nclosed, then everything is normal; Otherwise, the work thread may access the\nreleased sock when receiving data.\r\n\r\nAdd a chan mutex in the rx callback of the sock to achieve synchronization between\nthe sock release and recv cb.\r\n\r\nSock is dead, so set chan data to NULL, avoid others use invalid sock pointer.(CVE-2024-41062)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nBluetooth: hci_core: cancel all works upon hci_unregister_dev()\r\n\r\nsyzbot is reporting that calling hci_release_dev() from hci_error_reset()\ndue to hci_dev_put() from hci_error_reset() can cause deadlock at\ndestroy_workqueue(), for hci_error_reset() is called from\nhdev-\u0026gt;req_workqueue which destroy_workqueue() needs to flush.\r\n\r\nWe need to make sure that hdev-\u0026gt;{rx_work,cmd_work,tx_work} which are\nqueued into hdev-\u0026gt;workqueue and hdev-\u0026gt;{power_on,error_reset} which are\nqueued into hdev-\u0026gt;req_workqueue are no longer running by the moment\r\n\r\n       destroy_workqueue(hdev-\u0026gt;workqueue);\n       destroy_workqueue(hdev-\u0026gt;req_workqueue);\r\n\r\nare called from hci_release_dev().\r\n\r\nCall cancel_work_sync() on these work items from hci_unregister_dev()\nas soon as hdev-\u0026gt;list is removed from hci_dev_list.(CVE-2024-41063)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\npowerpc/eeh: avoid possible crash when edev-\u0026gt;pdev changes\r\n\r\nIf a PCI device is removed during eeh_pe_report_edev(), edev-\u0026gt;pdev\nwill change and can cause a crash, hold the PCI rescan/remove lock\nwhile taking a copy of edev-\u0026gt;pdev-\u0026gt;bus.(CVE-2024-41064)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nASoC: topology: Fix references to freed memory\r\n\r\nMost users after parsing a topology file, release memory used by it, so\nhaving pointer references directly into topology file contents is wrong.\nUse devm_kmemdup(), to allocate memory as needed.(CVE-2024-41069)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nKVM: PPC: Book3S HV: Prevent UAF in kvm_spapr_tce_attach_iommu_group()\r\n\r\nAl reported a possible use-after-free (UAF) in kvm_spapr_tce_attach_iommu_group().\r\n\r\nIt looks up `stt` from tablefd, but then continues to use it after doing\nfdput() on the returned fd. After the fdput() the tablefd is free to be\nclosed by another thread. The close calls kvm_spapr_tce_release() and\nthen release_spapr_tce_table() (via call_rcu()) which frees `stt`.\r\n\r\nAlthough there are calls to rcu_read_lock() in\nkvm_spapr_tce_attach_iommu_group() they are not sufficient to prevent\nthe UAF, because `stt` is used outside the locked regions.\r\n\r\nWith an artifcial delay after the fdput() and a userspace program which\ntriggers the race, KASAN detects the UAF:\r\n\r\n  BUG: KASAN: slab-use-after-free in kvm_spapr_tce_attach_iommu_group+0x298/0x720 [kvm]\n  Read of size 4 at addr c000200027552c30 by task kvm-vfio/2505\n  CPU: 54 PID: 2505 Comm: kvm-vfio Not tainted 6.10.0-rc3-next-20240612-dirty #1\n  Hardware name: 8335-GTH POWER9 0x4e1202 opal:skiboot-v6.5.3-35-g1851b2a06 PowerNV\n  Call Trace:\n    dump_stack_lvl+0xb4/0x108 (unreliable)\n    print_report+0x2b4/0x6ec\n    kasan_report+0x118/0x2b0\n    __asan_load4+0xb8/0xd0\n    kvm_spapr_tce_attach_iommu_group+0x298/0x720 [kvm]\n    kvm_vfio_set_attr+0x524/0xac0 [kvm]\n    kvm_device_ioctl+0x144/0x240 [kvm]\n    sys_ioctl+0x62c/0x1810\n    system_call_exception+0x190/0x440\n    system_call_vectored_common+0x15c/0x2ec\n  ...\n  Freed by task 0:\n   ...\n   kfree+0xec/0x3e0\n   release_spapr_tce_table+0xd4/0x11c [kvm]\n   rcu_core+0x568/0x16a0\n   handle_softirqs+0x23c/0x920\n   do_softirq_own_stack+0x6c/0x90\n   do_softirq_own_stack+0x58/0x90\n   __irq_exit_rcu+0x218/0x2d0\n   irq_exit+0x30/0x80\n   arch_local_irq_restore+0x128/0x230\n   arch_local_irq_enable+0x1c/0x30\n   cpuidle_enter_state+0x134/0x5cc\n   cpuidle_enter+0x6c/0xb0\n   call_cpuidle+0x7c/0x100\n   do_idle+0x394/0x410\n   cpu_startup_entry+0x60/0x70\n   start_secondary+0x3fc/0x410\n   start_secondary_prolog+0x10/0x14\r\n\r\nFix it by delaying the fdput() until `stt` is no longer in use, which\nis effectively the entire function. To keep the patch minimal add a call\nto fdput() at each of the existing return paths. Future work can convert\nthe function to goto or __cleanup style cleanup.\r\n\r\nWith the fix in place the test case no longer triggers the UAF.(CVE-2024-41070)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nwifi: cfg80211: wext: add extra SIOCSIWSCAN data check\r\n\r\nIn \u0026apos;cfg80211_wext_siwscan()\u0026apos;, add extra check whether number of\nchannels passed via \u0026apos;ioctl(sock, SIOCSIWSCAN, ...)\u0026apos; doesn\u0026apos;t exceed\nIW_MAX_FREQUENCIES and reject invalid request with -EINVAL otherwise.(CVE-2024-41072)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nnull_blk: fix validation of block size\r\n\r\nBlock size should be between 512 and PAGE_SIZE and be a power of 2. The current\ncheck does not validate this, so update the check.\r\n\r\nWithout this patch, null_blk would Oops due to a null pointer deref when\nloaded with bs=1536 [1].\r\n\r\n\n[axboe: remove unnecessary braces and != 0 check](CVE-2024-41077)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nnvmet: always initialize cqe.result\r\n\r\nThe spec doesn\u0026apos;t mandate that the first two double words (aka results)\nfor the command queue entry need to be set to 0 when they are not\nused (not specified). Though, the target implemention returns 0 for TCP\nand FC but not for RDMA.\r\n\r\nLet\u0026apos;s make RDMA behave the same and thus explicitly initializing the\nresult field. This prevents leaking any data from the stack.(CVE-2024-41079)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nio_uring: fix possible deadlock in io_register_iowq_max_workers()\r\n\r\nThe io_register_iowq_max_workers() function calls io_put_sq_data(),\nwhich acquires the sqd-\u0026gt;lock without releasing the uring_lock.\nSimilar to the commit 009ad9f0c6ee (\u0026quot;io_uring: drop ctx-\u0026gt;uring_lock\nbefore acquiring sqd-\u0026gt;lock\u0026quot;), this can lead to a potential deadlock\nsituation.\r\n\r\nTo resolve this issue, the uring_lock is released before calling\nio_put_sq_data(), and then it is re-acquired after the function call.\r\n\r\nThis change ensures that the locks are acquired in the correct\norder, preventing the possibility of a deadlock.(CVE-2024-41080)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nila: block BH in ila_output()\r\n\r\nAs explained in commit 1378817486d6 (\u0026quot;tipc: block BH\nbefore using dst_cache\u0026quot;), net/core/dst_cache.c\nhelpers need to be called with BH disabled.\r\n\r\nila_output() is called from lwtunnel_output()\npossibly from process context, and under rcu_read_lock().\r\n\r\nWe might be interrupted by a softirq, re-enter ila_output()\nand corrupt dst_cache data structures.\r\n\r\nFix the race by using local_bh_disable().(CVE-2024-41081)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\ndrm/nouveau/dispnv04: fix null pointer dereference in nv17_tv_get_hd_modes\r\n\r\nIn nv17_tv_get_hd_modes(), the return value of drm_mode_duplicate() is\nassigned to mode, which will lead to a possible NULL pointer dereference\non failure of drm_mode_duplicate(). The same applies to drm_cvt_mode().\nAdd a check to avoid null pointer dereference.(CVE-2024-41089)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\ntap: add missing verification for short frame\r\n\r\nThe cited commit missed to check against the validity of the frame length\nin the tap_get_user_xdp() path, which could cause a corrupted skb to be\nsent downstack. Even before the skb is transmitted, the\ntap_get_user_xdp()--\u0026gt;skb_set_network_header() may assume the size is more\nthan ETH_HLEN. Once transmitted, this could either cause out-of-bound\naccess beyond the actual length, or confuse the underlayer with incorrect\nor inconsistent header length in the skb metadata.\r\n\r\nIn the alternative path, tap_get_user() already prohibits short frame which\nhas the length less than Ethernet header size from being transmitted.\r\n\r\nThis is to drop any frame shorter than the Ethernet header size just like\nhow tap_get_user() does.\r\n\r\nCVE: CVE-2024-41090(CVE-2024-41090)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\ntun: add missing verification for short frame\r\n\r\nThe cited commit missed to check against the validity of the frame length\nin the tun_xdp_one() path, which could cause a corrupted skb to be sent\ndownstack. Even before the skb is transmitted, the\ntun_xdp_one--\u0026gt;eth_type_trans() may access the Ethernet header although it\ncan be less than ETH_HLEN. Once transmitted, this could either cause\nout-of-bound access beyond the actual length, or confuse the underlayer\nwith incorrect or inconsistent header length in the skb metadata.\r\n\r\nIn the alternative path, tun_get_user() already prohibits short frame which\nhas the length less than Ethernet header size from being transmitted for\nIFF_TAP.\r\n\r\nThis is to drop any frame shorter than the Ethernet header size just like\nhow tun_get_user() does.\r\n\r\nCVE: CVE-2024-41091(CVE-2024-41091)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nusb: atm: cxacru: fix endpoint checking in cxacru_bind()\r\n\r\nSyzbot is still reporting quite an old issue [1] that occurs due to\nincomplete checking of present usb endpoints. As such, wrong\nendpoints types may be used at urb sumbitting stage which in turn\ntriggers a warning in usb_submit_urb().\r\n\r\nFix the issue by verifying that required endpoint types are present\nfor both in and out endpoints, taking into account cmd endpoint type.\r\n\r\nUnfortunately, this patch has not been tested on real hardware.\r\n\r\n[1] Syzbot report:\nusb 1-1: BOGUS urb xfer, pipe 1 != type 3\nWARNING: CPU: 0 PID: 8667 at drivers/usb/core/urb.c:502 usb_submit_urb+0xed2/0x18a0 drivers/usb/core/urb.c:502\nModules linked in:\nCPU: 0 PID: 8667 Comm: kworker/0:4 Not tainted 5.14.0-rc4-syzkaller #0\nHardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011\nWorkqueue: usb_hub_wq hub_event\nRIP: 0010:usb_submit_urb+0xed2/0x18a0 drivers/usb/core/urb.c:502\n...\nCall Trace:\n cxacru_cm+0x3c0/0x8e0 drivers/usb/atm/cxacru.c:649\n cxacru_card_status+0x22/0xd0 drivers/usb/atm/cxacru.c:760\n cxacru_bind+0x7ac/0x11a0 drivers/usb/atm/cxacru.c:1209\n usbatm_usb_probe+0x321/0x1ae0 drivers/usb/atm/usbatm.c:1055\n cxacru_usb_probe+0xdf/0x1e0 drivers/usb/atm/cxacru.c:1363\n usb_probe_interface+0x315/0x7f0 drivers/usb/core/driver.c:396\n call_driver_probe drivers/base/dd.c:517 [inline]\n really_probe+0x23c/0xcd0 drivers/base/dd.c:595\n __driver_probe_device+0x338/0x4d0 drivers/base/dd.c:747\n driver_probe_device+0x4c/0x1a0 drivers/base/dd.c:777\n __device_attach_driver+0x20b/0x2f0 drivers/base/dd.c:894\n bus_for_each_drv+0x15f/0x1e0 drivers/base/bus.c:427\n __device_attach+0x228/0x4a0 drivers/base/dd.c:965\n bus_probe_device+0x1e4/0x290 drivers/base/bus.c:487\n device_add+0xc2f/0x2180 drivers/base/core.c:3354\n usb_set_configuration+0x113a/0x1910 drivers/usb/core/message.c:2170\n usb_generic_driver_probe+0xba/0x100 drivers/usb/core/generic.c:238\n usb_probe_device+0xd9/0x2c0 drivers/usb/core/driver.c:293(CVE-2024-41097)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nbpf: Take return from set_memory_ro() into account with bpf_prog_lock_ro()\r\n\r\nset_memory_ro() can fail, leaving memory unprotected.\r\n\r\nCheck its return and take it into account as an error.(CVE-2024-42068)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nnet: can: j1939: Initialize unused data in j1939_send_one()\r\n\r\nsyzbot reported kernel-infoleak in raw_recvmsg() [1]. j1939_send_one()\ncreates full frame including unused data, but it doesn\u0026apos;t initialize\nit. This causes the kernel-infoleak issue. Fix this by initializing\nunused data.\r\n\r\n[1]\nBUG: KMSAN: kernel-infoleak in instrument_copy_to_user include/linux/instrumented.h:114 [inline]\nBUG: KMSAN: kernel-infoleak in copy_to_user_iter lib/iov_iter.c:24 [inline]\nBUG: KMSAN: kernel-infoleak in iterate_ubuf include/linux/iov_iter.h:29 [inline]\nBUG: KMSAN: kernel-infoleak in iterate_and_advance2 include/linux/iov_iter.h:245 [inline]\nBUG: KMSAN: kernel-infoleak in iterate_and_advance include/linux/iov_iter.h:271 [inline]\nBUG: KMSAN: kernel-infoleak in _copy_to_iter+0x366/0x2520 lib/iov_iter.c:185\n instrument_copy_to_user include/linux/instrumented.h:114 [inline]\n copy_to_user_iter lib/iov_iter.c:24 [inline]\n iterate_ubuf include/linux/iov_iter.h:29 [inline]\n iterate_and_advance2 include/linux/iov_iter.h:245 [inline]\n iterate_and_advance include/linux/iov_iter.h:271 [inline]\n _copy_to_iter+0x366/0x2520 lib/iov_iter.c:185\n copy_to_iter include/linux/uio.h:196 [inline]\n memcpy_to_msg include/linux/skbuff.h:4113 [inline]\n raw_recvmsg+0x2b8/0x9e0 net/can/raw.c:1008\n sock_recvmsg_nosec net/socket.c:1046 [inline]\n sock_recvmsg+0x2c4/0x340 net/socket.c:1068\n ____sys_recvmsg+0x18a/0x620 net/socket.c:2803\n ___sys_recvmsg+0x223/0x840 net/socket.c:2845\n do_recvmmsg+0x4fc/0xfd0 net/socket.c:2939\n __sys_recvmmsg net/socket.c:3018 [inline]\n __do_sys_recvmmsg net/socket.c:3041 [inline]\n __se_sys_recvmmsg net/socket.c:3034 [inline]\n __x64_sys_recvmmsg+0x397/0x490 net/socket.c:3034\n x64_sys_call+0xf6c/0x3b50 arch/x86/include/generated/asm/syscalls_64.h:300\n do_syscall_x64 arch/x86/entry/common.c:52 [inline]\n do_syscall_64+0xcf/0x1e0 arch/x86/entry/common.c:83\n entry_SYSCALL_64_after_hwframe+0x77/0x7f\r\n\r\nUninit was created at:\n slab_post_alloc_hook mm/slub.c:3804 [inline]\n slab_alloc_node mm/slub.c:3845 [inline]\n kmem_cache_alloc_node+0x613/0xc50 mm/slub.c:3888\n kmalloc_reserve+0x13d/0x4a0 net/core/skbuff.c:577\n __alloc_skb+0x35b/0x7a0 net/core/skbuff.c:668\n alloc_skb include/linux/skbuff.h:1313 [inline]\n alloc_skb_with_frags+0xc8/0xbf0 net/core/skbuff.c:6504\n sock_alloc_send_pskb+0xa81/0xbf0 net/core/sock.c:2795\n sock_alloc_send_skb include/net/sock.h:1842 [inline]\n j1939_sk_alloc_skb net/can/j1939/socket.c:878 [inline]\n j1939_sk_send_loop net/can/j1939/socket.c:1142 [inline]\n j1939_sk_sendmsg+0xc0a/0x2730 net/can/j1939/socket.c:1277\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:2584\n ___sys_sendmsg+0x28d/0x3c0 net/socket.c:2638\n __sys_sendmsg net/socket.c:2667 [inline]\n __do_sys_sendmsg net/socket.c:2676 [inline]\n __se_sys_sendmsg net/socket.c:2674 [inline]\n __x64_sys_sendmsg+0x307/0x4a0 net/socket.c:2674\n x64_sys_call+0xc4b/0x3b50 arch/x86/include/generated/asm/syscalls_64.h:47\n do_syscall_x64 arch/x86/entry/common.c:52 [inline]\n do_syscall_64+0xcf/0x1e0 arch/x86/entry/common.c:83\n entry_SYSCALL_64_after_hwframe+0x77/0x7f\r\n\r\nBytes 12-15 of 16 are uninitialized\nMemory access of size 16 starts at ffff888120969690\nData copied to user address 00000000200017c0\r\n\r\nCPU: 1 PID: 5050 Comm: syz-executor198 Not tainted 6.9.0-rc5-syzkaller-00031-g71b1543c83d6 #0\nHardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 03/27/2024(CVE-2024-42076)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nocfs2: fix DIO failure due to insufficient transaction credits\r\n\r\nThe code in ocfs2_dio_end_io_write() estimates number of necessary\ntransaction credits using ocfs2_calc_extend_credits().  This however does\nnot take into account that the IO could be arbitrarily large and can\ncontain arbitrary number of extents.\r\n\r\nExtent tree manipulations do often extend the current transaction but not\nin all of the cases.  For example if we have only single block extents in\nthe tree, ocfs2_mark_extent_written() will end up calling\nocfs2_replace_extent_rec() all the time and we will never extend the\ncurrent transaction and eventually exhaust all the transaction credits if\nthe IO contains many single block extents.  Once that happens a\nWARN_ON(jbd2_handle_buffer_credits(handle) \u0026lt;= 0) is triggered in\njbd2_journal_dirty_metadata() and subsequently OCFS2 aborts in response to\nthis error.  This was actually triggered by one of our customers on a\nheavily fragmented OCFS2 filesystem.\r\n\r\nTo fix the issue make sure the transaction always has enough credits for\none extent insert before each call of ocfs2_mark_extent_written().\r\n\r\nHeming Zhao said:\r\n\r\n------\nPANIC: \u0026quot;Kernel panic - not syncing: OCFS2: (device dm-1): panic forced after error\u0026quot;\r\n\r\nPID: xxx  TASK: xxxx  CPU: 5  COMMAND: \u0026quot;SubmitThread-CA\u0026quot;\n  #0 machine_kexec at ffffffff8c069932\n  #1 __crash_kexec at ffffffff8c1338fa\n  #2 panic at ffffffff8c1d69b9\n  #3 ocfs2_handle_error at ffffffffc0c86c0c [ocfs2]\n  #4 __ocfs2_abort at ffffffffc0c88387 [ocfs2]\n  #5 ocfs2_journal_dirty at ffffffffc0c51e98 [ocfs2]\n  #6 ocfs2_split_extent at ffffffffc0c27ea3 [ocfs2]\n  #7 ocfs2_change_extent_flag at ffffffffc0c28053 [ocfs2]\n  #8 ocfs2_mark_extent_written at ffffffffc0c28347 [ocfs2]\n  #9 ocfs2_dio_end_io_write at ffffffffc0c2bef9 [ocfs2]\n#10 ocfs2_dio_end_io at ffffffffc0c2c0f5 [ocfs2]\n#11 dio_complete at ffffffff8c2b9fa7\n#12 do_blockdev_direct_IO at ffffffff8c2bc09f\n#13 ocfs2_direct_IO at ffffffffc0c2b653 [ocfs2]\n#14 generic_file_direct_write at ffffffff8c1dcf14\n#15 __generic_file_write_iter at ffffffff8c1dd07b\n#16 ocfs2_file_write_iter at ffffffffc0c49f1f [ocfs2]\n#17 aio_write at ffffffff8c2cc72e\n#18 kmem_cache_alloc at ffffffff8c248dde\n#19 do_io_submit at ffffffff8c2ccada\n#20 do_syscall_64 at ffffffff8c004984\n#21 entry_SYSCALL_64_after_hwframe at ffffffff8c8000ba(CVE-2024-42077)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nRDMA/restrack: Fix potential invalid address access\r\n\r\nstruct rdma_restrack_entry\u0026apos;s kern_name was set to KBUILD_MODNAME\nin ib_create_cq(), while if the module exited but forgot del this\nrdma_restrack_entry, it would cause a invalid address access in\nrdma_restrack_clean() when print the owner of this rdma_restrack_entry.\r\n\r\nThese code is used to help find one forgotten PD release in one of the\nULPs. But it is not needed anymore, so delete them.(CVE-2024-42080)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nxdp: Remove WARN() from __xdp_reg_mem_model()\r\n\r\nsyzkaller reports a warning in __xdp_reg_mem_model().\r\n\r\nThe warning occurs only if __mem_id_init_hash_table() returns an error. It\nreturns the error in two cases:\r\n\r\n  1. memory allocation fails;\n  2. rhashtable_init() fails when some fields of rhashtable_params\n     struct are not initialized properly.\r\n\r\nThe second case cannot happen since there is a static const rhashtable_params\nstruct with valid fields. So, warning is only triggered when there is a\nproblem with memory allocation.\r\n\r\nThus, there is no sense in using WARN() to handle this error and it can be\nsafely removed.\r\n\r\nWARNING: CPU: 0 PID: 5065 at net/core/xdp.c:299 __xdp_reg_mem_model+0x2d9/0x650 net/core/xdp.c:299\r\n\r\nCPU: 0 PID: 5065 Comm: syz-executor883 Not tainted 6.8.0-syzkaller-05271-gf99c5f563c17 #0\nHardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 03/27/2024\nRIP: 0010:__xdp_reg_mem_model+0x2d9/0x650 net/core/xdp.c:299\r\n\r\nCall Trace:\n xdp_reg_mem_model+0x22/0x40 net/core/xdp.c:344\n xdp_test_run_setup net/bpf/test_run.c:188 [inline]\n bpf_test_run_xdp_live+0x365/0x1e90 net/bpf/test_run.c:377\n bpf_prog_test_run_xdp+0x813/0x11b0 net/bpf/test_run.c:1267\n bpf_prog_test_run+0x33a/0x3b0 kernel/bpf/syscall.c:4240\n __sys_bpf+0x48d/0x810 kernel/bpf/syscall.c:5649\n __do_sys_bpf kernel/bpf/syscall.c:5738 [inline]\n __se_sys_bpf kernel/bpf/syscall.c:5736 [inline]\n __x64_sys_bpf+0x7c/0x90 kernel/bpf/syscall.c:5736\n do_syscall_64+0xfb/0x240\n entry_SYSCALL_64_after_hwframe+0x6d/0x75\r\n\r\nFound by Linux Verification Center (linuxtesting.org) with syzkaller.(CVE-2024-42082)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nftruncate: pass a signed offset\r\n\r\nThe old ftruncate() syscall, using the 32-bit off_t misses a sign\nextension when called in compat mode on 64-bit architectures.  As a\nresult, passing a negative length accidentally succeeds in truncating\nto file size between 2GiB and 4GiB.\r\n\r\nChanging the type of the compat syscall to the signed compat_off_t\nchanges the behavior so it instead returns -EINVAL.\r\n\r\nThe native entry point, the truncate() syscall and the corresponding\nloff_t based variants are all correct already and do not suffer\nfrom this mistake.(CVE-2024-42084)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\niio: chemical: bme680: Fix overflows in compensate() functions\r\n\r\nThere are cases in the compensate functions of the driver that\nthere could be overflows of variables due to bit shifting ops.\nThese implications were initially discussed here [1] and they\nwere mentioned in log message of Commit 1b3bd8592780 (\u0026quot;iio:\nchemical: Add support for Bosch BME680 sensor\u0026quot;).\r\n\r\n[1]: https://lore.kernel.org/linux-iio/20180728114028.3c1bbe81@archlinux/(CVE-2024-42086)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nASoC: fsl-asoc-card: set priv-\u0026gt;pdev before using it\r\n\r\npriv-\u0026gt;pdev pointer was set after being used in\nfsl_asoc_card_audmux_init().\nMove this assignment at the start of the probe function, so\nsub-functions can correctly use pdev through priv.\r\n\r\nfsl_asoc_card_audmux_init() dereferences priv-\u0026gt;pdev to get access to the\ndev struct, used with dev_err macros.\nAs priv is zero-initialised, there would be a NULL pointer dereference.\nNote that if priv-\u0026gt;dev is dereferenced before assignment but never used,\nfor example if there is no error to be printed, the driver won\u0026apos;t crash\nprobably due to compiler optimisations.(CVE-2024-42089)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\npinctrl: fix deadlock in create_pinctrl() when handling -EPROBE_DEFER\r\n\r\nIn create_pinctrl(), pinctrl_maps_mutex is acquired before calling\nadd_setting(). If add_setting() returns -EPROBE_DEFER, create_pinctrl()\ncalls pinctrl_free(). However, pinctrl_free() attempts to acquire\npinctrl_maps_mutex, which is already held by create_pinctrl(), leading to\na potential deadlock.\r\n\r\nThis patch resolves the issue by releasing pinctrl_maps_mutex before\ncalling pinctrl_free(), preventing the deadlock.\r\n\r\nThis bug was discovered and resolved using Coverity Static Analysis\nSecurity Testing (SAST) by Synopsys, Inc.(CVE-2024-42090)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\ngpio: davinci: Validate the obtained number of IRQs\r\n\r\nValue of pdata-\u0026gt;gpio_unbanked is taken from Device Tree. In case of broken\nDT due to any error this value can be any. Without this value validation\nthere can be out of chips-\u0026gt;irqs array boundaries access in\ndavinci_gpio_probe().\r\n\r\nValidate the obtained nirq value so that it won\u0026apos;t exceed the maximum\nnumber of IRQs per bank.\r\n\r\nFound by Linux Verification Center (linuxtesting.org) with SVACE.(CVE-2024-42092)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nnet/dpaa2: Avoid explicit cpumask var allocation on stack\r\n\r\nFor CONFIG_CPUMASK_OFFSTACK=y kernel, explicit allocation of cpumask\nvariable on stack is not recommended since it can cause potential stack\noverflow.\r\n\r\nInstead, kernel code should always use *cpumask_var API(s) to allocate\ncpumask var in config-neutral way, leaving allocation strategy to\nCONFIG_CPUMASK_OFFSTACK.\r\n\r\nUse *cpumask_var API(s) to address it.(CVE-2024-42093)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nnet/iucv: Avoid explicit cpumask var allocation on stack\r\n\r\nFor CONFIG_CPUMASK_OFFSTACK=y kernel, explicit allocation of cpumask\nvariable on stack is not recommended since it can cause potential stack\noverflow.\r\n\r\nInstead, kernel code should always use *cpumask_var API(s) to allocate\ncpumask var in config-neutral way, leaving allocation strategy to\nCONFIG_CPUMASK_OFFSTACK.\r\n\r\nUse *cpumask_var API(s) to address it.(CVE-2024-42094)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nALSA: emux: improve patch ioctl data validation\r\n\r\nIn load_data(), make the validation of and skipping over the main info\nblock match that in load_guspatch().\r\n\r\nIn load_guspatch(), add checking that the specified patch length matches\nthe actually supplied data, like load_data() already did.(CVE-2024-42097)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\ndrm/nouveau: fix null pointer dereference in nouveau_connector_get_modes\r\n\r\nIn nouveau_connector_get_modes(), the return value of drm_mode_duplicate()\nis assigned to mode, which will lead to a possible NULL pointer\ndereference on failure of drm_mode_duplicate(). Add a check to avoid npd.(CVE-2024-42101)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\ninet_diag: Initialize pad field in struct inet_diag_req_v2\r\n\r\nKMSAN reported uninit-value access in raw_lookup() [1]. Diag for raw\nsockets uses the pad field in struct inet_diag_req_v2 for the\nunderlying protocol. This field corresponds to the sdiag_raw_protocol\nfield in struct inet_diag_req_raw.\r\n\r\ninet_diag_get_exact_compat() converts inet_diag_req to\ninet_diag_req_v2, but leaves the pad field uninitialized. So the issue\noccurs when raw_lookup() accesses the sdiag_raw_protocol field.\r\n\r\nFix this by initializing the pad field in\ninet_diag_get_exact_compat(). Also, do the same fix in\ninet_diag_dump_compat() to avoid the similar issue in the future.\r\n\r\n[1]\nBUG: KMSAN: uninit-value in raw_lookup net/ipv4/raw_diag.c:49 [inline]\nBUG: KMSAN: uninit-value in raw_sock_get+0x657/0x800 net/ipv4/raw_diag.c:71\n raw_lookup net/ipv4/raw_diag.c:49 [inline]\n raw_sock_get+0x657/0x800 net/ipv4/raw_diag.c:71\n raw_diag_dump_one+0xa1/0x660 net/ipv4/raw_diag.c:99\n inet_diag_cmd_exact+0x7d9/0x980\n inet_diag_get_exact_compat net/ipv4/inet_diag.c:1404 [inline]\n inet_diag_rcv_msg_compat+0x469/0x530 net/ipv4/inet_diag.c:1426\n sock_diag_rcv_msg+0x23d/0x740 net/core/sock_diag.c:282\n netlink_rcv_skb+0x537/0x670 net/netlink/af_netlink.c:2564\n sock_diag_rcv+0x35/0x40 net/core/sock_diag.c:297\n netlink_unicast_kernel net/netlink/af_netlink.c:1335 [inline]\n netlink_unicast+0xe74/0x1240 net/netlink/af_netlink.c:1361\n netlink_sendmsg+0x10c6/0x1260 net/netlink/af_netlink.c:1905\n sock_sendmsg_nosec net/socket.c:730 [inline]\n __sock_sendmsg+0x332/0x3d0 net/socket.c:745\n ____sys_sendmsg+0x7f0/0xb70 net/socket.c:2585\n ___sys_sendmsg+0x271/0x3b0 net/socket.c:2639\n __sys_sendmsg net/socket.c:2668 [inline]\n __do_sys_sendmsg net/socket.c:2677 [inline]\n __se_sys_sendmsg net/socket.c:2675 [inline]\n __x64_sys_sendmsg+0x27e/0x4a0 net/socket.c:2675\n x64_sys_call+0x135e/0x3ce0 arch/x86/include/generated/asm/syscalls_64.h:47\n do_syscall_x64 arch/x86/entry/common.c:52 [inline]\n do_syscall_64+0xd9/0x1e0 arch/x86/entry/common.c:83\n entry_SYSCALL_64_after_hwframe+0x77/0x7f\r\n\r\nUninit was stored to memory at:\n raw_sock_get+0x650/0x800 net/ipv4/raw_diag.c:71\n raw_diag_dump_one+0xa1/0x660 net/ipv4/raw_diag.c:99\n inet_diag_cmd_exact+0x7d9/0x980\n inet_diag_get_exact_compat net/ipv4/inet_diag.c:1404 [inline]\n inet_diag_rcv_msg_compat+0x469/0x530 net/ipv4/inet_diag.c:1426\n sock_diag_rcv_msg+0x23d/0x740 net/core/sock_diag.c:282\n netlink_rcv_skb+0x537/0x670 net/netlink/af_netlink.c:2564\n sock_diag_rcv+0x35/0x40 net/core/sock_diag.c:297\n netlink_unicast_kernel net/netlink/af_netlink.c:1335 [inline]\n netlink_unicast+0xe74/0x1240 net/netlink/af_netlink.c:1361\n netlink_sendmsg+0x10c6/0x1260 net/netlink/af_netlink.c:1905\n sock_sendmsg_nosec net/socket.c:730 [inline]\n __sock_sendmsg+0x332/0x3d0 net/socket.c:745\n ____sys_sendmsg+0x7f0/0xb70 net/socket.c:2585\n ___sys_sendmsg+0x271/0x3b0 net/socket.c:2639\n __sys_sendmsg net/socket.c:2668 [inline]\n __do_sys_sendmsg net/socket.c:2677 [inline]\n __se_sys_sendmsg net/socket.c:2675 [inline]\n __x64_sys_sendmsg+0x27e/0x4a0 net/socket.c:2675\n x64_sys_call+0x135e/0x3ce0 arch/x86/include/generated/asm/syscalls_64.h:47\n do_syscall_x64 arch/x86/entry/common.c:52 [inline]\n do_syscall_64+0xd9/0x1e0 arch/x86/entry/common.c:83\n entry_SYSCALL_64_after_hwframe+0x77/0x7f\r\n\r\nLocal variable req.i created at:\n inet_diag_get_exact_compat net/ipv4/inet_diag.c:1396 [inline]\n inet_diag_rcv_msg_compat+0x2a6/0x530 net/ipv4/inet_diag.c:1426\n sock_diag_rcv_msg+0x23d/0x740 net/core/sock_diag.c:282\r\n\r\nCPU: 1 PID: 8888 Comm: syz-executor.6 Not tainted 6.10.0-rc4-00217-g35bb670d65fc #32\nHardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.16.3-2.fc40 04/01/2014(CVE-2024-42106)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\njffs2: Fix potential illegal address access in jffs2_free_inode\r\n\r\nDuring the stress testing of the jffs2 file system,the following\nabnormal printouts were found:\n[ 2430.649000] Unable to handle kernel paging request at virtual address 0069696969696948\n[ 2430.649622] Mem abort info:\n[ 2430.649829]   ESR = 0x96000004\n[ 2430.650115]   EC = 0x25: DABT (current EL), IL = 32 bits\n[ 2430.650564]   SET = 0, FnV = 0\n[ 2430.650795]   EA = 0, S1PTW = 0\n[ 2430.651032]   FSC = 0x04: level 0 translation fault\n[ 2430.651446] Data abort info:\n[ 2430.651683]   ISV = 0, ISS = 0x00000004\n[ 2430.652001]   CM = 0, WnR = 0\n[ 2430.652558] [0069696969696948] address between user and kernel address ranges\n[ 2430.653265] Internal error: Oops: 96000004 [#1] PREEMPT SMP\n[ 2430.654512] CPU: 2 PID: 20919 Comm: cat Not tainted 5.15.25-g512f31242bf6 #33\n[ 2430.655008] Hardware name: linux,dummy-virt (DT)\n[ 2430.655517] pstate: 20000005 (nzCv daif -PAN -UAO -TCO -DIT -SSBS BTYPE=--)\n[ 2430.656142] pc : kfree+0x78/0x348\n[ 2430.656630] lr : jffs2_free_inode+0x24/0x48\n[ 2430.657051] sp : ffff800009eebd10\n[ 2430.657355] x29: ffff800009eebd10 x28: 0000000000000001 x27: 0000000000000000\n[ 2430.658327] x26: ffff000038f09d80 x25: 0080000000000000 x24: ffff800009d38000\n[ 2430.658919] x23: 5a5a5a5a5a5a5a5a x22: ffff000038f09d80 x21: ffff8000084f0d14\n[ 2430.659434] x20: ffff0000bf9a6ac0 x19: 0169696969696940 x18: 0000000000000000\n[ 2430.659969] x17: ffff8000b6506000 x16: ffff800009eec000 x15: 0000000000004000\n[ 2430.660637] x14: 0000000000000000 x13: 00000001000820a1 x12: 00000000000d1b19\n[ 2430.661345] x11: 0004000800000000 x10: 0000000000000001 x9 : ffff8000084f0d14\n[ 2430.662025] x8 : ffff0000bf9a6b40 x7 : ffff0000bf9a6b48 x6 : 0000000003470302\n[ 2430.662695] x5 : ffff00002e41dcc0 x4 : ffff0000bf9aa3b0 x3 : 0000000003470342\n[ 2430.663486] x2 : 0000000000000000 x1 : ffff8000084f0d14 x0 : fffffc0000000000\n[ 2430.664217] Call trace:\n[ 2430.664528]  kfree+0x78/0x348\n[ 2430.664855]  jffs2_free_inode+0x24/0x48\n[ 2430.665233]  i_callback+0x24/0x50\n[ 2430.665528]  rcu_do_batch+0x1ac/0x448\n[ 2430.665892]  rcu_core+0x28c/0x3c8\n[ 2430.666151]  rcu_core_si+0x18/0x28\n[ 2430.666473]  __do_softirq+0x138/0x3cc\n[ 2430.666781]  irq_exit+0xf0/0x110\n[ 2430.667065]  handle_domain_irq+0x6c/0x98\n[ 2430.667447]  gic_handle_irq+0xac/0xe8\n[ 2430.667739]  call_on_irq_stack+0x28/0x54\nThe parameter passed to kfree was 5a5a5a5a, which corresponds to the target field of\nthe jffs_inode_info structure. It was found that all variables in the jffs_inode_info\nstructure were 5a5a5a5a, except for the first member sem. It is suspected that these\nvariables are not initialized because they were set to 5a5a5a5a during memory testing,\nwhich is meant to detect uninitialized memory.The sem variable is initialized in the\nfunction jffs2_i_init_once, while other members are initialized in\nthe function jffs2_init_inode_info.\r\n\r\nThe function jffs2_init_inode_info is called after iget_locked,\nbut in the iget_locked function, the destroy_inode process is triggered,\nwhich releases the inode and consequently, the target member of the inode\nis not initialized.In concurrent high pressure scenarios, iget_locked\nmay enter the destroy_inode branch as described in the code.\r\n\r\nSince the destroy_inode functionality of jffs2 only releases the target,\nthe fix method is to set target to NULL in jffs2_i_init_once.(CVE-2024-42115)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nscsi: qedf: Make qedf_execute_tmf() non-preemptible\r\n\r\nStop calling smp_processor_id() from preemptible code in\nqedf_execute_tmf90.  This results in BUG_ON() when running an RT kernel.\r\n\r\n[ 659.343280] BUG: using smp_processor_id() in preemptible [00000000] code: sg_reset/3646\n[ 659.343282] caller is qedf_execute_tmf+0x8b/0x360 [qedf](CVE-2024-42124)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nleds: mlxreg: Use devm_mutex_init() for mutex initialization\r\n\r\nIn this driver LEDs are registered using devm_led_classdev_register()\nso they are automatically unregistered after module\u0026apos;s remove() is done.\nled_classdev_unregister() calls module\u0026apos;s led_set_brightness() to turn off\nthe LEDs and that callback uses mutex which was destroyed already\nin module\u0026apos;s remove() so use devm API instead.(CVE-2024-42129)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nIB/core: Implement a limit on UMAD receive List\r\n\r\nThe existing behavior of ib_umad, which maintains received MAD\npackets in an unbounded list, poses a risk of uncontrolled growth.\nAs user-space applications extract packets from this list, the rate\nof extraction may not match the rate of incoming packets, leading\nto potential list overflow.\r\n\r\nTo address this, we introduce a limit to the size of the list. After\nconsidering typical scenarios, such as OpenSM processing, which can\nhandle approximately 100k packets per second, and the 1-second retry\ntimeout for most packets, we set the list size limit to 200k. Packets\nreceived beyond this limit are dropped, assuming they are likely timed\nout by the time they are handled by user-space.\r\n\r\nNotably, packets queued on the receive list due to reasons like\ntimed-out sends are preserved even when the list is full.(CVE-2024-42145)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\ns390/pkey: Wipe copies of protected- and secure-keys\r\n\r\nAlthough the clear-key of neither protected- nor secure-keys is\naccessible, this key material should only be visible to the calling\nprocess. So wipe all copies of protected- or secure-keys from stack,\neven in case of an error.(CVE-2024-42155)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nf2fs: check validation of fault attrs in f2fs_build_fault_attr()\r\n\r\n- It missed to check validation of fault attrs in parse_options(),\nlet\u0026apos;s fix to add check condition in f2fs_build_fault_attr().\n- Use f2fs_build_fault_attr() in __sbi_store() to clean up code.(CVE-2024-42160)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nbpf: Avoid uninitialized value in BPF_CORE_READ_BITFIELD\r\n\r\n[Changes from V1:\n - Use a default branch in the switch statement to initialize `val\u0026apos;.]\r\n\r\nGCC warns that `val\u0026apos; may be used uninitialized in the\nBPF_CRE_READ_BITFIELD macro, defined in bpf_core_read.h as:\r\n\r\n\t[...]\n\tunsigned long long val;\t\t\t\t\t\t      \\\n\t[...]\t\t\t\t\t\t\t\t      \\\n\tswitch (__CORE_RELO(s, field, BYTE_SIZE)) {\t\t\t      \\\n\tcase 1: val = *(const unsigned char *)p; break;\t\t\t      \\\n\tcase 2: val = *(const unsigned short *)p; break;\t\t      \\\n\tcase 4: val = *(const unsigned int *)p; break;\t\t\t      \\\n\tcase 8: val = *(const unsigned long long *)p; break;\t\t      \\\n        }       \t\t\t\t\t\t\t      \\\n\t[...]\n\tval;\t\t\t\t\t\t\t\t      \\\n\t}\t\t\t\t\t\t\t\t      \\\r\n\r\nThis patch adds a default entry in the switch statement that sets\n`val\u0026apos; to zero in order to avoid the warning, and random values to be\nused in case __builtin_preserve_field_info returns unexpected values\nfor BPF_FIELD_BYTE_SIZE.\r\n\r\nTested in bpf-next master.\nNo regressions.(CVE-2024-42161)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\ngve: Account for stopped queues when reading NIC stats\r\n\r\nWe now account for the fact that the NIC might send us stats for a\nsubset of queues. Without this change, gve_get_ethtool_stats might make\nan invalid access on the priv-\u0026gt;stats_report-\u0026gt;stats array.(CVE-2024-42162)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nnet: dsa: mv88e6xxx: Correct check for empty list\r\n\r\nSince commit a3c53be55c95 (\u0026quot;net: dsa: mv88e6xxx: Support multiple MDIO\nbusses\u0026quot;) mv88e6xxx_default_mdio_bus() has checked that the\nreturn value of list_first_entry() is non-NULL.\r\n\r\nThis appears to be intended to guard against the list chip-\u0026gt;mdios being\nempty.  However, it is not the correct check as the implementation of\nlist_first_entry is not designed to return NULL for empty lists.\r\n\r\nInstead, use list_first_entry_or_null() which does return NULL if the\nlist is empty.\r\n\r\nFlagged by Smatch.\nCompile tested only.(CVE-2024-42224)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\ndrm/amdgpu: Using uninitialized value *size when calling amdgpu_vce_cs_reloc\r\n\r\nInitialize the size before calling amdgpu_vce_cs_reloc, such as case 0x03000001.\nV2: To really improve the handling we would actually\n   need to have a separate value of 0xffffffff.(Christian)(CVE-2024-42228)","status":"published","published":"2024-08-09T11:07:26Z","modified":"2026-08-18T01:18:33.326705664Z","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-2258","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\ns390/qeth: fix deadlock during failing recovery\r\n\r\nCommit 0b9902c1fcc5 (\u0026quot;s390/qeth: fix deadlock during recovery\u0026quot;) removed\ntaking discipline_mutex inside qeth_do_reset(), fixing potential\ndeadlocks. An error path was missed though, that still takes\ndiscipline_mutex and thus has the original deadlock potential.\r\n\r\nIntermittent deadlocks were seen when a qeth channel path is configured\noffline, causing a race between qeth_do_reset and ccwgroup_remove.\nCall qeth_set_offline() directly in the qeth_do_reset() error case and\nthen a new variant of ccwgroup_set_offline(), without taking\ndiscipline_mutex.(CVE-2021-47382)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\ndrm/i915/gt: Cleanup partial engine discovery failures\r\n\r\nIf we abort driver initialisation in the middle of gt/engine discovery,\nsome engines will be fully setup and some not. Those incompletely setup\nengines only have \u0026apos;engine-\u0026gt;release == NULL\u0026apos; and so will leak any of the\ncommon objects allocated.\r\n\r\nv2:\n - Drop the destroy_pinned_context() helper for now.  It\u0026apos;s not really\n   worth it with just a single callsite at the moment.  (Janusz)(CVE-2022-48893)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nusb: gadget: ncm: Fix handling of zero block length packets\r\n\r\nWhile connecting to a Linux host with CDC_NCM_NTB_DEF_SIZE_TX\nset to 65536, it has been observed that we receive short packets,\nwhich come at interval of 5-10 seconds sometimes and have block\nlength zero but still contain 1-2 valid datagrams present.\r\n\r\nAccording to the NCM spec:\r\n\r\n\u0026quot;If wBlockLength = 0x0000, the block is terminated by a\nshort packet. In this case, the USB transfer must still\nbe shorter than dwNtbInMaxSize or dwNtbOutMaxSize. If\nexactly dwNtbInMaxSize or dwNtbOutMaxSize bytes are sent,\nand the size is a multiple of wMaxPacketSize for the\ngiven pipe, then no ZLP shall be sent.\r\n\r\nwBlockLength= 0x0000 must be used with extreme care, because\nof the possibility that the host and device may get out of\nsync, and because of test issues.\r\n\r\nwBlockLength = 0x0000 allows the sender to reduce latency by\nstarting to send a very large NTB, and then shortening it when\nthe sender discovers that there’s not sufficient data to justify\nsending a large NTB\u0026quot;\r\n\r\nHowever, there is a potential issue with the current implementation,\nas it checks for the occurrence of multiple NTBs in a single\ngiveback by verifying if the leftover bytes to be processed is zero\nor not. If the block length reads zero, we would process the same\nNTB infintely because the leftover bytes is never zero and it leads\nto a crash. Fix this by bailing out if block length reads zero.(CVE-2024-35825)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nipv6: fix race condition between ipv6_get_ifaddr and ipv6_del_addr\r\n\r\nAlthough ipv6_get_ifaddr walks inet6_addr_lst under the RCU lock, it\nstill means hlist_for_each_entry_rcu can return an item that got removed\nfrom the list. The memory itself of such item is not freed thanks to RCU\nbut nothing guarantees the actual content of the memory is sane.\r\n\r\nIn particular, the reference count can be zero. This can happen if\nipv6_del_addr is called in parallel. ipv6_del_addr removes the entry\nfrom inet6_addr_lst (hlist_del_init_rcu(\u0026amp;ifp-\u0026gt;addr_lst)) and drops all\nreferences (__in6_ifa_put(ifp) + in6_ifa_put(ifp)). With bad enough\ntiming, this can happen:\r\n\r\n1. In ipv6_get_ifaddr, hlist_for_each_entry_rcu returns an entry.\r\n\r\n2. Then, the whole ipv6_del_addr is executed for the given entry. The\n   reference count drops to zero and kfree_rcu is scheduled.\r\n\r\n3. ipv6_get_ifaddr continues and tries to increments the reference count\n   (in6_ifa_hold).\r\n\r\n4. The rcu is unlocked and the entry is freed.\r\n\r\n5. The freed entry is returned.\r\n\r\nPrevent increasing of the reference count in such case. The name\nin6_ifa_hold_safe is chosen to mimic the existing fib6_info_hold_safe.\r\n\r\n[   41.506330] refcount_t: addition on 0; use-after-free.\n[   41.506760] WARNING: CPU: 0 PID: 595 at lib/refcount.c:25 refcount_warn_saturate+0xa5/0x130\n[   41.507413] Modules linked in: veth bridge stp llc\n[   41.507821] CPU: 0 PID: 595 Comm: python3 Not tainted 6.9.0-rc2.main-00208-g49563be82afa #14\n[   41.508479] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996)\n[   41.509163] RIP: 0010:refcount_warn_saturate+0xa5/0x130\n[   41.509586] Code: ad ff 90 0f 0b 90 90 c3 cc cc cc cc 80 3d c0 30 ad 01 00 75 a0 c6 05 b7 30 ad 01 01 90 48 c7 c7 38 cc 7a 8c e8 cc 18 ad ff 90 \u0026lt;0f\u0026gt; 0b 90 90 c3 cc cc cc cc 80 3d 98 30 ad 01 00 0f 85 75 ff ff ff\n[   41.510956] RSP: 0018:ffffbda3c026baf0 EFLAGS: 00010282\n[   41.511368] RAX: 0000000000000000 RBX: ffff9e9c46914800 RCX: 0000000000000000\n[   41.511910] RDX: ffff9e9c7ec29c00 RSI: ffff9e9c7ec1c900 RDI: ffff9e9c7ec1c900\n[   41.512445] RBP: ffff9e9c43660c9c R08: 0000000000009ffb R09: 00000000ffffdfff\n[   41.512998] R10: 00000000ffffdfff R11: ffffffff8ca58a40 R12: ffff9e9c4339a000\n[   41.513534] R13: 0000000000000001 R14: ffff9e9c438a0000 R15: ffffbda3c026bb48\n[   41.514086] FS:  00007fbc4cda1740(0000) GS:ffff9e9c7ec00000(0000) knlGS:0000000000000000\n[   41.514726] CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033\n[   41.515176] CR2: 000056233b337d88 CR3: 000000000376e006 CR4: 0000000000370ef0\n[   41.515713] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000\n[   41.516252] DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400\n[   41.516799] Call Trace:\n[   41.517037]  \u0026lt;TASK\u0026gt;\n[   41.517249]  ? __warn+0x7b/0x120\n[   41.517535]  ? refcount_warn_saturate+0xa5/0x130\n[   41.517923]  ? report_bug+0x164/0x190\n[   41.518240]  ? handle_bug+0x3d/0x70\n[   41.518541]  ? exc_invalid_op+0x17/0x70\n[   41.520972]  ? asm_exc_invalid_op+0x1a/0x20\n[   41.521325]  ? refcount_warn_saturate+0xa5/0x130\n[   41.521708]  ipv6_get_ifaddr+0xda/0xe0\n[   41.522035]  inet6_rtm_getaddr+0x342/0x3f0\n[   41.522376]  ? __pfx_inet6_rtm_getaddr+0x10/0x10\n[   41.522758]  rtnetlink_rcv_msg+0x334/0x3d0\n[   41.523102]  ? netlink_unicast+0x30f/0x390\n[   41.523445]  ? __pfx_rtnetlink_rcv_msg+0x10/0x10\n[   41.523832]  netlink_rcv_skb+0x53/0x100\n[   41.524157]  netlink_unicast+0x23b/0x390\n[   41.524484]  netlink_sendmsg+0x1f2/0x440\n[   41.524826]  __sys_sendto+0x1d8/0x1f0\n[   41.525145]  __x64_sys_sendto+0x1f/0x30\n[   41.525467]  do_syscall_64+0xa5/0x1b0\n[   41.525794]  entry_SYSCALL_64_after_hwframe+0x72/0x7a\n[   41.526213] RIP: 0033:0x7fbc4cfcea9a\n[   41.526528] Code: d8 64 89 02 48 c7 c0 ff ff ff ff eb b8 0f 1f 00 f3 0f 1e fa 41 89 ca 64 8b 04 25 18 00 00 00 85 c0 75 15 b8 2c 00 00 00 0f 05 \u0026lt;48\u0026gt; 3d 00 f0 ff ff 77 7e c3 0f 1f 44 00 00 41 54 48 83 ec 30 44 89\n[   41.527942] RSP: 002b:00007f\n---truncated---(CVE-2024-35969)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nnetfilter: nf_tables: honor table dormant flag from netdev release event path\r\n\r\nCheck for table dormant flag otherwise netdev release event path tries\nto unregister an already unregistered hook.\r\n\r\n[524854.857999] ------------[ cut here ]------------\n[524854.858010] WARNING: CPU: 0 PID: 3386599 at net/netfilter/core.c:501 __nf_unregister_net_hook+0x21a/0x260\n[...]\n[524854.858848] CPU: 0 PID: 3386599 Comm: kworker/u32:2 Not tainted 6.9.0-rc3+ #365\n[524854.858869] Workqueue: netns cleanup_net\n[524854.858886] RIP: 0010:__nf_unregister_net_hook+0x21a/0x260\n[524854.858903] Code: 24 e8 aa 73 83 ff 48 63 43 1c 83 f8 01 0f 85 3d ff ff ff e8 98 d1 f0 ff 48 8b 3c 24 e8 8f 73 83 ff 48 63 43 1c e9 26 ff ff ff \u0026lt;0f\u0026gt; 0b 48 83 c4 18 48 c7 c7 00 68 e9 82 5b 5d 41 5c 41 5d 41 5e 41\n[524854.858914] RSP: 0018:ffff8881e36d79e0 EFLAGS: 00010246\n[524854.858926] RAX: 0000000000000000 RBX: ffff8881339ae790 RCX: ffffffff81ba524a\n[524854.858936] RDX: dffffc0000000000 RSI: 0000000000000008 RDI: ffff8881c8a16438\n[524854.858945] RBP: ffff8881c8a16438 R08: 0000000000000001 R09: ffffed103c6daf34\n[524854.858954] R10: ffff8881e36d79a7 R11: 0000000000000000 R12: 0000000000000005\n[524854.858962] R13: ffff8881c8a16000 R14: 0000000000000000 R15: ffff8881351b5a00\n[524854.858971] FS:  0000000000000000(0000) GS:ffff888390800000(0000) knlGS:0000000000000000\n[524854.858982] CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033\n[524854.858991] CR2: 00007fc9be0f16f4 CR3: 00000001437cc004 CR4: 00000000001706f0\n[524854.859000] Call Trace:\n[524854.859006]  \u0026lt;TASK\u0026gt;\n[524854.859013]  ? __warn+0x9f/0x1a0\n[524854.859027]  ? __nf_unregister_net_hook+0x21a/0x260\n[524854.859044]  ? report_bug+0x1b1/0x1e0\n[524854.859060]  ? handle_bug+0x3c/0x70\n[524854.859071]  ? exc_invalid_op+0x17/0x40\n[524854.859083]  ? asm_exc_invalid_op+0x1a/0x20\n[524854.859100]  ? __nf_unregister_net_hook+0x6a/0x260\n[524854.859116]  ? __nf_unregister_net_hook+0x21a/0x260\n[524854.859135]  nf_tables_netdev_event+0x337/0x390 [nf_tables]\n[524854.859304]  ? __pfx_nf_tables_netdev_event+0x10/0x10 [nf_tables]\n[524854.859461]  ? packet_notifier+0xb3/0x360\n[524854.859476]  ? _raw_spin_unlock_irqrestore+0x11/0x40\n[524854.859489]  ? dcbnl_netdevice_event+0x35/0x140\n[524854.859507]  ? __pfx_nf_tables_netdev_event+0x10/0x10 [nf_tables]\n[524854.859661]  notifier_call_chain+0x7d/0x140\n[524854.859677]  unregister_netdevice_many_notify+0x5e1/0xae0(CVE-2024-36005)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nkeys: Fix overwrite of key expiration on instantiation\r\n\r\nThe expiry time of a key is unconditionally overwritten during\ninstantiation, defaulting to turn it permanent. This causes a problem\nfor DNS resolution as the expiration set by user-space is overwritten to\nTIME64_MAX, disabling further DNS updates. Fix this by restoring the\ncondition that key_set_expiry is only called when the pre-parser sets a\nspecific expiry.(CVE-2024-36031)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nnetfilter: tproxy: bail out if IP has been disabled on the device\r\n\r\nsyzbot reports:\ngeneral protection fault, probably for non-canonical address 0xdffffc0000000003: 0000 [#1] PREEMPT SMP KASAN PTI\nKASAN: null-ptr-deref in range [0x0000000000000018-0x000000000000001f]\n[..]\nRIP: 0010:nf_tproxy_laddr4+0xb7/0x340 net/ipv4/netfilter/nf_tproxy_ipv4.c:62\nCall Trace:\n nft_tproxy_eval_v4 net/netfilter/nft_tproxy.c:56 [inline]\n nft_tproxy_eval+0xa9a/0x1a00 net/netfilter/nft_tproxy.c:168\r\n\r\n__in_dev_get_rcu() can return NULL, so check for this.(CVE-2024-36270)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nBluetooth: qca: add missing firmware sanity checks\r\n\r\nAdd the missing sanity checks when parsing the firmware files before\ndownloading them to avoid accessing and corrupting memory beyond the\nvmalloced buffer.(CVE-2024-36880)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nnfc: llcp: fix nfc_llcp_setsockopt() unsafe copies\r\n\r\nsyzbot reported unsafe calls to copy_from_sockptr() [1]\r\n\r\nUse copy_safe_from_sockptr() instead.\r\n\r\n[1]\r\n\r\nBUG: KASAN: slab-out-of-bounds in copy_from_sockptr_offset include/linux/sockptr.h:49 [inline]\n BUG: KASAN: slab-out-of-bounds in copy_from_sockptr include/linux/sockptr.h:55 [inline]\n BUG: KASAN: slab-out-of-bounds in nfc_llcp_setsockopt+0x6c2/0x850 net/nfc/llcp_sock.c:255\nRead of size 4 at addr ffff88801caa1ec3 by task syz-executor459/5078\r\n\r\nCPU: 0 PID: 5078 Comm: syz-executor459 Not tainted 6.8.0-syzkaller-08951-gfe46a7dd189e #0\nHardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 03/27/2024\nCall Trace:\n \u0026lt;TASK\u0026gt;\n  __dump_stack lib/dump_stack.c:88 [inline]\n  dump_stack_lvl+0x241/0x360 lib/dump_stack.c:114\n  print_address_description mm/kasan/report.c:377 [inline]\n  print_report+0x169/0x550 mm/kasan/report.c:488\n  kasan_report+0x143/0x180 mm/kasan/report.c:601\n  copy_from_sockptr_offset include/linux/sockptr.h:49 [inline]\n  copy_from_sockptr include/linux/sockptr.h:55 [inline]\n  nfc_llcp_setsockopt+0x6c2/0x850 net/nfc/llcp_sock.c:255\n  do_sock_setsockopt+0x3b1/0x720 net/socket.c:2311\n  __sys_setsockopt+0x1ae/0x250 net/socket.c:2334\n  __do_sys_setsockopt net/socket.c:2343 [inline]\n  __se_sys_setsockopt net/socket.c:2340 [inline]\n  __x64_sys_setsockopt+0xb5/0xd0 net/socket.c:2340\n do_syscall_64+0xfd/0x240\n entry_SYSCALL_64_after_hwframe+0x6d/0x75\nRIP: 0033:0x7f7fac07fd89\nCode: 28 00 00 00 75 05 48 83 c4 28 c3 e8 91 18 00 00 90 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 \u0026lt;48\u0026gt; 3d 01 f0 ff ff 73 01 c3 48 c7 c1 b8 ff ff ff f7 d8 64 89 01 48\nRSP: 002b:00007fff660eb788 EFLAGS: 00000246 ORIG_RAX: 0000000000000036\nRAX: ffffffffffffffda RBX: 0000000000000003 RCX: 00007f7fac07fd89\nRDX: 0000000000000000 RSI: 0000000000000118 RDI: 0000000000000004\nRBP: 0000000000000000 R08: 0000000000000002 R09: 0000000000000000\nR10: 0000000020000a80 R11: 0000000000000246 R12: 0000000000000000\nR13: 0000000000000000 R14: 0000000000000000 R15: 0000000000000000(CVE-2024-36915)\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\nphonet: fix rtm_phonet_notify() skb allocation\r\n\r\nfill_route() stores three components in the skb:\r\n\r\n- struct rtmsg\n- RTA_DST (u8)\n- RTA_OIF (u32)\r\n\r\nTherefore, rtm_phonet_notify() should use\r\n\r\nNLMSG_ALIGN(sizeof(struct rtmsg)) +\nnla_total_size(1) +\nnla_total_size(4)(CVE-2024-36946)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\ndrm: vc4: Fix possible null pointer dereference\r\n\r\nIn vc4_hdmi_audio_init() of_get_address() may return\nNULL which is later dereferenced. Fix this bug by adding NULL check.\r\n\r\nFound by Linux Verification Center (linuxtesting.org) with SVACE.(CVE-2024-38546)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nscsi: bfa: 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 instead\nof memdup_user.(CVE-2024-38560)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nmedia: i2c: et8ek8: Don\u0026apos;t strip remove function when driver is builtin\r\n\r\nUsing __exit for the remove function results in the remove callback\nbeing discarded with CONFIG_VIDEO_ET8EK8=y. When such a device gets\nunbound (e.g. using sysfs or hotplug), the driver is just removed\nwithout the cleanup being performed. This results in resource leaks. Fix\nit by compiling in the remove callback unconditionally.\r\n\r\nThis also fixes a W=1 modpost warning:\r\n\r\n\tWARNING: modpost: drivers/media/i2c/et8ek8/et8ek8: section mismatch in reference: et8ek8_i2c_driver+0x10 (section: .data) -\u0026gt; et8ek8_remove (section: .exit.text)(CVE-2024-38611)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nm68k: Fix spinlock race in kernel thread creation\r\n\r\nContext switching does take care to retain the correct lock owner across\nthe switch from \u0026apos;prev\u0026apos; to \u0026apos;next\u0026apos; tasks.  This does rely on interrupts\nremaining disabled for the entire duration of the switch.\r\n\r\nThis condition is guaranteed for normal process creation and context\nswitching between already running processes, because both \u0026apos;prev\u0026apos; and\n\u0026apos;next\u0026apos; already have interrupts disabled in their saved copies of the\nstatus register.\r\n\r\nThe situation is different for newly created kernel threads.  The status\nregister is set to PS_S in copy_thread(), which does leave the IPL at 0.\nUpon restoring the \u0026apos;next\u0026apos; thread\u0026apos;s status register in switch_to() aka\nresume(), interrupts then become enabled prematurely.  resume() then\nreturns via ret_from_kernel_thread() and schedule_tail() where run queue\nlock is released (see finish_task_switch() and finish_lock_switch()).\r\n\r\nA timer interrupt calling scheduler_tick() before the lock is released\nin finish_task_switch() will find the lock already taken, with the\ncurrent task as lock owner.  This causes a spinlock recursion warning as\nreported by Guenter Roeck.\r\n\r\nAs far as I can ascertain, this race has been opened in commit\n533e6903bea0 (\u0026quot;m68k: split ret_from_fork(), simplify kernel_thread()\u0026quot;)\nbut I haven\u0026apos;t done a detailed study of kernel history so it may well\npredate that commit.\r\n\r\nInterrupts cannot be disabled in the saved status register copy for\nkernel threads (init will complain about interrupts disabled when\nfinally starting user space).  Disable interrupts temporarily when\nswitching the tasks\u0026apos; register sets in resume().\r\n\r\nNote that a simple oriw 0x700,%sr after restoring sr is not enough here\n- this leaves enough of a race for the \u0026apos;spinlock recursion\u0026apos; warning to\nstill be observed.\r\n\r\nTested on ARAnyM and qemu (Quadra 800 emulation).(CVE-2024-38613)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nenic: Validate length of nl attributes in enic_set_vf_port\r\n\r\nenic_set_vf_port assumes that the nl attribute IFLA_PORT_PROFILE\nis of length PORT_PROFILE_MAX and that the nl attributes\nIFLA_PORT_INSTANCE_UUID, IFLA_PORT_HOST_UUID are of length PORT_UUID_MAX.\nThese attributes are validated (in the function do_setlink in rtnetlink.c)\nusing the nla_policy ifla_port_policy. The policy defines IFLA_PORT_PROFILE\nas NLA_STRING, IFLA_PORT_INSTANCE_UUID as NLA_BINARY and\nIFLA_PORT_HOST_UUID as NLA_STRING. That means that the length validation\nusing the policy is for the max size of the attributes and not on exact\nsize so the length of these attributes might be less than the sizes that\nenic_set_vf_port expects. This might cause an out of bands\nread access in the memcpys of the data of these\nattributes in enic_set_vf_port.(CVE-2024-38659)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\num: Add winch to winch_handlers before registering winch IRQ\r\n\r\nRegistering a winch IRQ is racy, an interrupt may occur before the winch is\nadded to the winch_handlers list.\r\n\r\nIf that happens, register_winch_irq() adds to that list a winch that is\nscheduled to be (or has already been) freed, causing a panic later in\nwinch_cleanup().\r\n\r\nAvoid the race by adding the winch to the winch_handlers list before\nregistering the IRQ, and rolling back if um_request_irq() fails.(CVE-2024-39292)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nima: Fix use-after-free on a dentry\u0026apos;s dname.name\r\n\r\n-\u0026gt;d_name.name can change on rename and the earlier value can be freed;\nthere are conditions sufficient to stabilize it (-\u0026gt;d_lock on dentry,\n-\u0026gt;d_lock on its parent, -\u0026gt;i_rwsem exclusive on the parent\u0026apos;s inode,\nrename_lock), but none of those are met at any of the sites. Take a stable\nsnapshot of the name instead.(CVE-2024-39494)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\ndrm/exynos/vidi: fix memory leak in .get_modes()\r\n\r\nThe duplicated EDID is never freed. Fix it.(CVE-2024-40932)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\ndrm/radeon: fix UBSAN warning in kv_dpm.c\r\n\r\nAdds bounds check for sumo_vid_mapping_entry.(CVE-2024-40988)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nfs/ntfs3: Validate ff offset\r\n\r\nThis adds sanity checks for ff offset. There is a check\non rt-\u0026gt;first_free at first, but walking through by ff\nwithout any check. If the second ff is a large offset.\nWe may encounter an out-of-bound read.(CVE-2024-41019)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nnet/sched: Fix UAF when resolving a clash\r\n\r\nKASAN reports the following UAF:\r\n\r\n BUG: KASAN: slab-use-after-free in tcf_ct_flow_table_process_conn+0x12b/0x380 [act_ct]\n Read of size 1 at addr ffff888c07603600 by task handler130/6469\r\n\r\n Call Trace:\n  \u0026lt;IRQ\u0026gt;\n  dump_stack_lvl+0x48/0x70\n  print_address_description.constprop.0+0x33/0x3d0\n  print_report+0xc0/0x2b0\n  kasan_report+0xd0/0x120\n  __asan_load1+0x6c/0x80\n  tcf_ct_flow_table_process_conn+0x12b/0x380 [act_ct]\n  tcf_ct_act+0x886/0x1350 [act_ct]\n  tcf_action_exec+0xf8/0x1f0\n  fl_classify+0x355/0x360 [cls_flower]\n  __tcf_classify+0x1fd/0x330\n  tcf_classify+0x21c/0x3c0\n  sch_handle_ingress.constprop.0+0x2c5/0x500\n  __netif_receive_skb_core.constprop.0+0xb25/0x1510\n  __netif_receive_skb_list_core+0x220/0x4c0\n  netif_receive_skb_list_internal+0x446/0x620\n  napi_complete_done+0x157/0x3d0\n  gro_cell_poll+0xcf/0x100\n  __napi_poll+0x65/0x310\n  net_rx_action+0x30c/0x5c0\n  __do_softirq+0x14f/0x491\n  __irq_exit_rcu+0x82/0xc0\n  irq_exit_rcu+0xe/0x20\n  common_interrupt+0xa1/0xb0\n  \u0026lt;/IRQ\u0026gt;\n  \u0026lt;TASK\u0026gt;\n  asm_common_interrupt+0x27/0x40\r\n\r\n Allocated by task 6469:\n  kasan_save_stack+0x38/0x70\n  kasan_set_track+0x25/0x40\n  kasan_save_alloc_info+0x1e/0x40\n  __kasan_krealloc+0x133/0x190\n  krealloc+0xaa/0x130\n  nf_ct_ext_add+0xed/0x230 [nf_conntrack]\n  tcf_ct_act+0x1095/0x1350 [act_ct]\n  tcf_action_exec+0xf8/0x1f0\n  fl_classify+0x355/0x360 [cls_flower]\n  __tcf_classify+0x1fd/0x330\n  tcf_classify+0x21c/0x3c0\n  sch_handle_ingress.constprop.0+0x2c5/0x500\n  __netif_receive_skb_core.constprop.0+0xb25/0x1510\n  __netif_receive_skb_list_core+0x220/0x4c0\n  netif_receive_skb_list_internal+0x446/0x620\n  napi_complete_done+0x157/0x3d0\n  gro_cell_poll+0xcf/0x100\n  __napi_poll+0x65/0x310\n  net_rx_action+0x30c/0x5c0\n  __do_softirq+0x14f/0x491\r\n\r\n Freed by task 6469:\n  kasan_save_stack+0x38/0x70\n  kasan_set_track+0x25/0x40\n  kasan_save_free_info+0x2b/0x60\n  ____kasan_slab_free+0x180/0x1f0\n  __kasan_slab_free+0x12/0x30\n  slab_free_freelist_hook+0xd2/0x1a0\n  __kmem_cache_free+0x1a2/0x2f0\n  kfree+0x78/0x120\n  nf_conntrack_free+0x74/0x130 [nf_conntrack]\n  nf_ct_destroy+0xb2/0x140 [nf_conntrack]\n  __nf_ct_resolve_clash+0x529/0x5d0 [nf_conntrack]\n  nf_ct_resolve_clash+0xf6/0x490 [nf_conntrack]\n  __nf_conntrack_confirm+0x2c6/0x770 [nf_conntrack]\n  tcf_ct_act+0x12ad/0x1350 [act_ct]\n  tcf_action_exec+0xf8/0x1f0\n  fl_classify+0x355/0x360 [cls_flower]\n  __tcf_classify+0x1fd/0x330\n  tcf_classify+0x21c/0x3c0\n  sch_handle_ingress.constprop.0+0x2c5/0x500\n  __netif_receive_skb_core.constprop.0+0xb25/0x1510\n  __netif_receive_skb_list_core+0x220/0x4c0\n  netif_receive_skb_list_internal+0x446/0x620\n  napi_complete_done+0x157/0x3d0\n  gro_cell_poll+0xcf/0x100\n  __napi_poll+0x65/0x310\n  net_rx_action+0x30c/0x5c0\n  __do_softirq+0x14f/0x491\r\n\r\nThe ct may be dropped if a clash has been resolved but is still passed to\nthe tcf_ct_flow_table_process_conn function for further usage. This issue\ncan be fixed by retrieving ct from skb again after confirming conntrack.(CVE-2024-41040)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nudp: Set SOCK_RCU_FREE earlier in udp_lib_get_port().\r\n\r\nsyzkaller triggered the warning [0] in udp_v4_early_demux().\r\n\r\nIn udp_v[46]_early_demux() and sk_lookup(), we do not touch the refcount\nof the looked-up sk and use sock_pfree() as skb-\u0026gt;destructor, so we check\nSOCK_RCU_FREE to ensure that the sk is safe to access during the RCU grace\nperiod.\r\n\r\nCurrently, SOCK_RCU_FREE is flagged for a bound socket after being put\ninto the hash table.  Moreover, the SOCK_RCU_FREE check is done too early\nin udp_v[46]_early_demux() and sk_lookup(), so there could be a small race\nwindow:\r\n\r\n  CPU1                                 CPU2\n  ----                                 ----\n  udp_v4_early_demux()                 udp_lib_get_port()\n  |                                    |- hlist_add_head_rcu()\n  |- sk = __udp4_lib_demux_lookup()    |\n  |- DEBUG_NET_WARN_ON_ONCE(sk_is_refcounted(sk));\n                                       `- sock_set_flag(sk, SOCK_RCU_FREE)\r\n\r\nWe had the same bug in TCP and fixed it in commit 871019b22d1b (\u0026quot;net:\nset SOCK_RCU_FREE before inserting socket into hashtable\u0026quot;).\r\n\r\nLet\u0026apos;s apply the same fix for UDP.\r\n\r\n[0]:\nWARNING: CPU: 0 PID: 11198 at net/ipv4/udp.c:2599 udp_v4_early_demux+0x481/0xb70 net/ipv4/udp.c:2599\nModules linked in:\nCPU: 0 PID: 11198 Comm: syz-executor.1 Not tainted 6.9.0-g93bda33046e7 #13\nHardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS rel-1.16.0-0-gd239552ce722-prebuilt.qemu.org 04/01/2014\nRIP: 0010:udp_v4_early_demux+0x481/0xb70 net/ipv4/udp.c:2599\nCode: c5 7a 15 fe bb 01 00 00 00 44 89 e9 31 ff d3 e3 81 e3 bf ef ff ff 89 de e8 2c 74 15 fe 85 db 0f 85 02 06 00 00 e8 9f 7a 15 fe \u0026lt;0f\u0026gt; 0b e8 98 7a 15 fe 49 8d 7e 60 e8 4f 39 2f fe 49 c7 46 60 20 52\nRSP: 0018:ffffc9000ce3fa58 EFLAGS: 00010293\nRAX: 0000000000000000 RBX: 0000000000000000 RCX: ffffffff8318c92c\nRDX: ffff888036ccde00 RSI: ffffffff8318c2f1 RDI: 0000000000000001\nRBP: ffff88805a2dd6e0 R08: 0000000000000001 R09: 0000000000000000\nR10: 0000000000000000 R11: 0001ffffffffffff R12: ffff88805a2dd680\nR13: 0000000000000007 R14: ffff88800923f900 R15: ffff88805456004e\nFS:  00007fc449127640(0000) GS:ffff88807dc00000(0000) knlGS:0000000000000000\nCS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033\nCR2: 00007fc449126e38 CR3: 000000003de4b002 CR4: 0000000000770ef0\nDR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000\nDR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000600\nPKRU: 55555554\nCall Trace:\n \u0026lt;TASK\u0026gt;\n ip_rcv_finish_core.constprop.0+0xbdd/0xd20 net/ipv4/ip_input.c:349\n ip_rcv_finish+0xda/0x150 net/ipv4/ip_input.c:447\n NF_HOOK include/linux/netfilter.h:314 [inline]\n NF_HOOK include/linux/netfilter.h:308 [inline]\n ip_rcv+0x16c/0x180 net/ipv4/ip_input.c:569\n __netif_receive_skb_one_core+0xb3/0xe0 net/core/dev.c:5624\n __netif_receive_skb+0x21/0xd0 net/core/dev.c:5738\n netif_receive_skb_internal net/core/dev.c:5824 [inline]\n netif_receive_skb+0x271/0x300 net/core/dev.c:5884\n tun_rx_batched drivers/net/tun.c:1549 [inline]\n tun_get_user+0x24db/0x2c50 drivers/net/tun.c:2002\n tun_chr_write_iter+0x107/0x1a0 drivers/net/tun.c:2048\n new_sync_write fs/read_write.c:497 [inline]\n vfs_write+0x76f/0x8d0 fs/read_write.c:590\n ksys_write+0xbf/0x190 fs/read_write.c:643\n __do_sys_write fs/read_write.c:655 [inline]\n __se_sys_write fs/read_write.c:652 [inline]\n __x64_sys_write+0x41/0x50 fs/read_write.c:652\n x64_sys_call+0xe66/0x1990 arch/x86/include/generated/asm/syscalls_64.h:2\n do_syscall_x64 arch/x86/entry/common.c:52 [inline]\n do_syscall_64+0x4b/0x110 arch/x86/entry/common.c:83\n entry_SYSCALL_64_after_hwframe+0x4b/0x53\nRIP: 0033:0x7fc44a68bc1f\nCode: 89 54 24 18 48 89 74 24 10 89 7c 24 08 e8 e9 cf f5 ff 48 8b 54 24 18 48 8b 74 24 10 41 89 c0 8b 7c 24 08 b8 01 00 00 00 0f 05 \u0026lt;48\u0026gt; 3d 00 f0 ff ff 77 31 44 89 c7 48 89 44 24 08 e8 3c d0 f5 ff 48\nRSP: 002b:00007fc449126c90 EFLAGS: 00000293 ORIG_RAX: 0000000000000001\nRAX: ffffffffffffffda RBX: 00000000004bc050 RCX: 00007fc44a68bc1f\nR\n---truncated---(CVE-2024-41041)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nskmsg: Skip zero length skb in sk_msg_recvmsg\r\n\r\nWhen running BPF selftests (./test_progs -t sockmap_basic) on a Loongarch\nplatform, the following kernel panic occurs:\r\n\r\n  [...]\n  Oops[#1]:\n  CPU: 22 PID: 2824 Comm: test_progs Tainted: G           OE  6.10.0-rc2+ #18\n  Hardware name: LOONGSON Dabieshan/Loongson-TC542F0, BIOS Loongson-UDK2018\n     ... ...\n     ra: 90000000048bf6c0 sk_msg_recvmsg+0x120/0x560\n    ERA: 9000000004162774 copy_page_to_iter+0x74/0x1c0\n   CRMD: 000000b0 (PLV0 -IE -DA +PG DACF=CC DACM=CC -WE)\n   PRMD: 0000000c (PPLV0 +PIE +PWE)\n   EUEN: 00000007 (+FPE +SXE +ASXE -BTE)\n   ECFG: 00071c1d (LIE=0,2-4,10-12 VS=7)\n  ESTAT: 00010000 [PIL] (IS= ECode=1 EsubCode=0)\n   BADV: 0000000000000040\n   PRID: 0014c011 (Loongson-64bit, Loongson-3C5000)\n  Modules linked in: bpf_testmod(OE) xt_CHECKSUM xt_MASQUERADE xt_conntrack\n  Process test_progs (pid: 2824, threadinfo=0000000000863a31, task=...)\n  Stack : ...\n  Call Trace:\n  [\u0026lt;9000000004162774\u0026gt;] copy_page_to_iter+0x74/0x1c0\n  [\u0026lt;90000000048bf6c0\u0026gt;] sk_msg_recvmsg+0x120/0x560\n  [\u0026lt;90000000049f2b90\u0026gt;] tcp_bpf_recvmsg_parser+0x170/0x4e0\n  [\u0026lt;90000000049aae34\u0026gt;] inet_recvmsg+0x54/0x100\n  [\u0026lt;900000000481ad5c\u0026gt;] sock_recvmsg+0x7c/0xe0\n  [\u0026lt;900000000481e1a8\u0026gt;] __sys_recvfrom+0x108/0x1c0\n  [\u0026lt;900000000481e27c\u0026gt;] sys_recvfrom+0x1c/0x40\n  [\u0026lt;9000000004c076ec\u0026gt;] do_syscall+0x8c/0xc0\n  [\u0026lt;9000000003731da4\u0026gt;] handle_syscall+0xc4/0x160\n  Code: ...\n  ---[ end trace 0000000000000000 ]---\n  Kernel panic - not syncing: Fatal exception\n  Kernel relocated by 0x3510000\n   .text @ 0x9000000003710000\n   .data @ 0x9000000004d70000\n   .bss  @ 0x9000000006469400\n  ---[ end Kernel panic - not syncing: Fatal exception ]---\n  [...]\r\n\r\nThis crash happens every time when running sockmap_skb_verdict_shutdown\nsubtest in sockmap_basic.\r\n\r\nThis crash is because a NULL pointer is passed to page_address() in the\nsk_msg_recvmsg(). Due to the different implementations depending on the\narchitecture, page_address(NULL) will trigger a panic on Loongarch\nplatform but not on x86 platform. So this bug was hidden on x86 platform\nfor a while, but now it is exposed on Loongarch platform. The root cause\nis that a zero length skb (skb-\u0026gt;len == 0) was put on the queue.\r\n\r\nThis zero length skb is a TCP FIN packet, which was sent by shutdown(),\ninvoked in test_sockmap_skb_verdict_shutdown():\r\n\r\n\tshutdown(p1, SHUT_WR);\r\n\r\nIn this case, in sk_psock_skb_ingress_enqueue(), num_sge is zero, and no\npage is put to this sge (see sg_set_page in sg_set_page), but this empty\nsge is queued into ingress_msg list.\r\n\r\nAnd in sk_msg_recvmsg(), this empty sge is used, and a NULL page is got by\nsg_page(sge). Pass this NULL page to copy_page_to_iter(), which passes it\nto kmap_local_page() and to page_address(), then kernel panics.\r\n\r\nTo solve this, we should skip this zero length skb. So in sk_msg_recvmsg(),\nif copy is zero, that means it\u0026apos;s a zero length skb, skip invoking\ncopy_page_to_iter(). We are using the EFAULT return triggered by\ncopy_page_to_iter to check for is_fin in tcp_bpf.c.(CVE-2024-41048)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nfilelock: fix potential use-after-free in posix_lock_inode\r\n\r\nLight Hsieh reported a KASAN UAF warning in trace_posix_lock_inode().\nThe request pointer had been changed earlier to point to a lock entry\nthat was added to the inode\u0026apos;s list. However, before the tracepoint could\nfire, another task raced in and freed that lock.\r\n\r\nFix this by moving the tracepoint inside the spinlock, which should\nensure that this doesn\u0026apos;t happen.(CVE-2024-41049)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nBluetooth: hci_core: cancel all works upon hci_unregister_dev()\r\n\r\nsyzbot is reporting that calling hci_release_dev() from hci_error_reset()\ndue to hci_dev_put() from hci_error_reset() can cause deadlock at\ndestroy_workqueue(), for hci_error_reset() is called from\nhdev-\u0026gt;req_workqueue which destroy_workqueue() needs to flush.\r\n\r\nWe need to make sure that hdev-\u0026gt;{rx_work,cmd_work,tx_work} which are\nqueued into hdev-\u0026gt;workqueue and hdev-\u0026gt;{power_on,error_reset} which are\nqueued into hdev-\u0026gt;req_workqueue are no longer running by the moment\r\n\r\n       destroy_workqueue(hdev-\u0026gt;workqueue);\n       destroy_workqueue(hdev-\u0026gt;req_workqueue);\r\n\r\nare called from hci_release_dev().\r\n\r\nCall cancel_work_sync() on these work items from hci_unregister_dev()\nas soon as hdev-\u0026gt;list is removed from hci_dev_list.(CVE-2024-41063)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nASoC: topology: Fix references to freed memory\r\n\r\nMost users after parsing a topology file, release memory used by it, so\nhaving pointer references directly into topology file contents is wrong.\nUse devm_kmemdup(), to allocate memory as needed.(CVE-2024-41069)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nio_uring: fix possible deadlock in io_register_iowq_max_workers()\r\n\r\nThe io_register_iowq_max_workers() function calls io_put_sq_data(),\nwhich acquires the sqd-\u0026gt;lock without releasing the uring_lock.\nSimilar to the commit 009ad9f0c6ee (\u0026quot;io_uring: drop ctx-\u0026gt;uring_lock\nbefore acquiring sqd-\u0026gt;lock\u0026quot;), this can lead to a potential deadlock\nsituation.\r\n\r\nTo resolve this issue, the uring_lock is released before calling\nio_put_sq_data(), and then it is re-acquired after the function call.\r\n\r\nThis change ensures that the locks are acquired in the correct\norder, preventing the possibility of a deadlock.(CVE-2024-41080)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\ntap: add missing verification for short frame\r\n\r\nThe cited commit missed to check against the validity of the frame length\nin the tap_get_user_xdp() path, which could cause a corrupted skb to be\nsent downstack. Even before the skb is transmitted, the\ntap_get_user_xdp()--\u0026gt;skb_set_network_header() may assume the size is more\nthan ETH_HLEN. Once transmitted, this could either cause out-of-bound\naccess beyond the actual length, or confuse the underlayer with incorrect\nor inconsistent header length in the skb metadata.\r\n\r\nIn the alternative path, tap_get_user() already prohibits short frame which\nhas the length less than Ethernet header size from being transmitted.\r\n\r\nThis is to drop any frame shorter than the Ethernet header size just like\nhow tap_get_user() does.\r\n\r\nCVE: CVE-2024-41090(CVE-2024-41090)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\ntun: add missing verification for short frame\r\n\r\nThe cited commit missed to check against the validity of the frame length\nin the tun_xdp_one() path, which could cause a corrupted skb to be sent\ndownstack. Even before the skb is transmitted, the\ntun_xdp_one--\u0026gt;eth_type_trans() may access the Ethernet header although it\ncan be less than ETH_HLEN. Once transmitted, this could either cause\nout-of-bound access beyond the actual length, or confuse the underlayer\nwith incorrect or inconsistent header length in the skb metadata.\r\n\r\nIn the alternative path, tun_get_user() already prohibits short frame which\nhas the length less than Ethernet header size from being transmitted for\nIFF_TAP.\r\n\r\nThis is to drop any frame shorter than the Ethernet header size just like\nhow tun_get_user() does.\r\n\r\nCVE: CVE-2024-41091(CVE-2024-41091)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nbpf: Take return from set_memory_rox() into account with bpf_jit_binary_lock_ro()\r\n\r\nset_memory_rox() can fail, leaving memory unprotected.\r\n\r\nCheck return and bail out when bpf_jit_binary_lock_ro() returns\nan error.(CVE-2024-42067)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\niio: chemical: bme680: Fix overflows in compensate() functions\r\n\r\nThere are cases in the compensate functions of the driver that\nthere could be overflows of variables due to bit shifting ops.\nThese implications were initially discussed here [1] and they\nwere mentioned in log message of Commit 1b3bd8592780 (\u0026quot;iio:\nchemical: Add support for Bosch BME680 sensor\u0026quot;).\r\n\r\n[1]: https://lore.kernel.org/linux-iio/20180728114028.3c1bbe81@archlinux/(CVE-2024-42086)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nALSA: emux: improve patch ioctl data validation\r\n\r\nIn load_data(), make the validation of and skipping over the main info\nblock match that in load_guspatch().\r\n\r\nIn load_guspatch(), add checking that the specified patch length matches\nthe actually supplied data, like load_data() already did.(CVE-2024-42097)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\njffs2: Fix potential illegal address access in jffs2_free_inode\r\n\r\nDuring the stress testing of the jffs2 file system,the following\nabnormal printouts were found:\n[ 2430.649000] Unable to handle kernel paging request at virtual address 0069696969696948\n[ 2430.649622] Mem abort info:\n[ 2430.649829]   ESR = 0x96000004\n[ 2430.650115]   EC = 0x25: DABT (current EL), IL = 32 bits\n[ 2430.650564]   SET = 0, FnV = 0\n[ 2430.650795]   EA = 0, S1PTW = 0\n[ 2430.651032]   FSC = 0x04: level 0 translation fault\n[ 2430.651446] Data abort info:\n[ 2430.651683]   ISV = 0, ISS = 0x00000004\n[ 2430.652001]   CM = 0, WnR = 0\n[ 2430.652558] [0069696969696948] address between user and kernel address ranges\n[ 2430.653265] Internal error: Oops: 96000004 [#1] PREEMPT SMP\n[ 2430.654512] CPU: 2 PID: 20919 Comm: cat Not tainted 5.15.25-g512f31242bf6 #33\n[ 2430.655008] Hardware name: linux,dummy-virt (DT)\n[ 2430.655517] pstate: 20000005 (nzCv daif -PAN -UAO -TCO -DIT -SSBS BTYPE=--)\n[ 2430.656142] pc : kfree+0x78/0x348\n[ 2430.656630] lr : jffs2_free_inode+0x24/0x48\n[ 2430.657051] sp : ffff800009eebd10\n[ 2430.657355] x29: ffff800009eebd10 x28: 0000000000000001 x27: 0000000000000000\n[ 2430.658327] x26: ffff000038f09d80 x25: 0080000000000000 x24: ffff800009d38000\n[ 2430.658919] x23: 5a5a5a5a5a5a5a5a x22: ffff000038f09d80 x21: ffff8000084f0d14\n[ 2430.659434] x20: ffff0000bf9a6ac0 x19: 0169696969696940 x18: 0000000000000000\n[ 2430.659969] x17: ffff8000b6506000 x16: ffff800009eec000 x15: 0000000000004000\n[ 2430.660637] x14: 0000000000000000 x13: 00000001000820a1 x12: 00000000000d1b19\n[ 2430.661345] x11: 0004000800000000 x10: 0000000000000001 x9 : ffff8000084f0d14\n[ 2430.662025] x8 : ffff0000bf9a6b40 x7 : ffff0000bf9a6b48 x6 : 0000000003470302\n[ 2430.662695] x5 : ffff00002e41dcc0 x4 : ffff0000bf9aa3b0 x3 : 0000000003470342\n[ 2430.663486] x2 : 0000000000000000 x1 : ffff8000084f0d14 x0 : fffffc0000000000\n[ 2430.664217] Call trace:\n[ 2430.664528]  kfree+0x78/0x348\n[ 2430.664855]  jffs2_free_inode+0x24/0x48\n[ 2430.665233]  i_callback+0x24/0x50\n[ 2430.665528]  rcu_do_batch+0x1ac/0x448\n[ 2430.665892]  rcu_core+0x28c/0x3c8\n[ 2430.666151]  rcu_core_si+0x18/0x28\n[ 2430.666473]  __do_softirq+0x138/0x3cc\n[ 2430.666781]  irq_exit+0xf0/0x110\n[ 2430.667065]  handle_domain_irq+0x6c/0x98\n[ 2430.667447]  gic_handle_irq+0xac/0xe8\n[ 2430.667739]  call_on_irq_stack+0x28/0x54\nThe parameter passed to kfree was 5a5a5a5a, which corresponds to the target field of\nthe jffs_inode_info structure. It was found that all variables in the jffs_inode_info\nstructure were 5a5a5a5a, except for the first member sem. It is suspected that these\nvariables are not initialized because they were set to 5a5a5a5a during memory testing,\nwhich is meant to detect uninitialized memory.The sem variable is initialized in the\nfunction jffs2_i_init_once, while other members are initialized in\nthe function jffs2_init_inode_info.\r\n\r\nThe function jffs2_init_inode_info is called after iget_locked,\nbut in the iget_locked function, the destroy_inode process is triggered,\nwhich releases the inode and consequently, the target member of the inode\nis not initialized.In concurrent high pressure scenarios, iget_locked\nmay enter the destroy_inode branch as described in the code.\r\n\r\nSince the destroy_inode functionality of jffs2 only releases the target,\nthe fix method is to set target to NULL in jffs2_i_init_once.(CVE-2024-42115)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nleds: mlxreg: Use devm_mutex_init() for mutex initialization\r\n\r\nIn this driver LEDs are registered using devm_led_classdev_register()\nso they are automatically unregistered after module\u0026apos;s remove() is done.\nled_classdev_unregister() calls module\u0026apos;s led_set_brightness() to turn off\nthe LEDs and that callback uses mutex which was destroyed already\nin module\u0026apos;s remove() so use devm API instead.(CVE-2024-42129)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\ndrm/amdgpu: Using uninitialized value *size when calling amdgpu_vce_cs_reloc\r\n\r\nInitialize the size before calling amdgpu_vce_cs_reloc, such as case 0x03000001.\nV2: To really improve the handling we would actually\n   need to have a separate value of 0xffffffff.(Christian)(CVE-2024-42228)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nnet: nexthop: Initialize all fields in dumped nexthops\r\n\r\nstruct nexthop_grp contains two reserved fields that are not initialized by\nnla_put_nh_group(), and carry garbage. This can be observed e.g. with\nstrace (edited for clarity):\r\n\r\n    # ip nexthop add id 1 dev lo\n    # ip nexthop add id 101 group 1\n    # strace -e recvmsg ip nexthop get id 101\n    ...\n    recvmsg(... [{nla_len=12, nla_type=NHA_GROUP},\n                 [{id=1, weight=0, resvd1=0x69, resvd2=0x67}]] ...) = 52\r\n\r\nThe fields are reserved and therefore not currently used. But as they are, they\nleak kernel memory, and the fact they are not just zero complicates repurposing\nof the fields for new ends. Initialize the full structure.(CVE-2024-42283)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nirqchip/imx-irqsteer: Handle runtime power management correctly\r\n\r\nThe power domain is automatically activated from clk_prepare(). However, on\ncertain platforms like i.MX8QM and i.MX8QXP, the power-on handling invokes\nsleeping functions, which triggers the \u0026apos;scheduling while atomic\u0026apos; bug in the\ncontext switch path during device probing:\r\n\r\n BUG: scheduling while atomic: kworker/u13:1/48/0x00000002\n Call trace:\n  __schedule_bug+0x54/0x6c\n  __schedule+0x7f0/0xa94\n  schedule+0x5c/0xc4\n  schedule_preempt_disabled+0x24/0x40\n  __mutex_lock.constprop.0+0x2c0/0x540\n  __mutex_lock_slowpath+0x14/0x20\n  mutex_lock+0x48/0x54\n  clk_prepare_lock+0x44/0xa0\n  clk_prepare+0x20/0x44\n  imx_irqsteer_resume+0x28/0xe0\n  pm_generic_runtime_resume+0x2c/0x44\n  __genpd_runtime_resume+0x30/0x80\n  genpd_runtime_resume+0xc8/0x2c0\n  __rpm_callback+0x48/0x1d8\n  rpm_callback+0x6c/0x78\n  rpm_resume+0x490/0x6b4\n  __pm_runtime_resume+0x50/0x94\n  irq_chip_pm_get+0x2c/0xa0\n  __irq_do_set_handler+0x178/0x24c\n  irq_set_chained_handler_and_data+0x60/0xa4\n  mxc_gpio_probe+0x160/0x4b0\r\n\r\nCure this by implementing the irq_bus_lock/sync_unlock() interrupt chip\ncallbacks and handle power management in them as they are invoked from\nnon-atomic context.\r\n\r\n[ tglx: Rewrote change log, added Fixes tag ](CVE-2024-42290)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nudf: Avoid using corrupted block bitmap buffer\r\n\r\nWhen the filesystem block bitmap is corrupted, we detect the corruption\nwhile loading the bitmap and fail the allocation with error. However the\nnext allocation from the same bitmap will notice the bitmap buffer is\nalready loaded and tries to allocate from the bitmap with mixed results\n(depending on the exact nature of the bitmap corruption). Fix the\nproblem by using BH_verified bit to indicate whether the bitmap is valid\nor not.(CVE-2024-42306)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\ndrm/gma500: fix null pointer dereference in psb_intel_lvds_get_modes\r\n\r\nIn psb_intel_lvds_get_modes(), the return value of drm_mode_duplicate() is\nassigned to mode, which will lead to a possible NULL pointer dereference\non failure of drm_mode_duplicate(). Add a check to avoid npd.(CVE-2024-42309)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nmedia: venus: fix use after free in vdec_close\r\n\r\nThere appears to be a possible use after free with vdec_close().\nThe firmware will add buffer release work to the work queue through\nHFI callbacks as a normal part of decoding. Randomly closing the\ndecoder device from userspace during normal decoding can incur\na read after free for inst.\r\n\r\nFix it by cancelling the work in vdec_close.(CVE-2024-42313)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nipvs: properly dereference pe in ip_vs_add_service\r\n\r\nUse pe directly to resolve sparse warning:\r\n\r\n  net/netfilter/ipvs/ip_vs_ctl.c:1471:27: warning: dereference of noderef expression(CVE-2024-42322)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nPCI: keystone: Fix NULL pointer dereference in case of DT error in ks_pcie_setup_rc_app_regs()\r\n\r\nIf IORESOURCE_MEM is not provided in Device Tree due to\nany error, resource_list_first_type() will return NULL and\npci_parse_request_of_pci_ranges() will just emit a warning.\r\n\r\nThis will cause a NULL pointer dereference. Fix this bug by adding NULL\nreturn check.\r\n\r\nFound by Linux Verification Center (linuxtesting.org) with SVACE.(CVE-2024-43823)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nleds: trigger: Unregister sysfs attributes before calling deactivate()\r\n\r\nTriggers which have trigger specific sysfs attributes typically store\nrelated data in trigger-data allocated by the activate() callback and\nfreed by the deactivate() callback.\r\n\r\nCalling device_remove_groups() after calling deactivate() leaves a window\nwhere the sysfs attributes show/store functions could be called after\ndeactivation and then operate on the just freed trigger-data.\r\n\r\nMove the device_remove_groups() call to before deactivate() to close\nthis race window.\r\n\r\nThis also makes the deactivation path properly do things in reverse order\nof the activation path which calls the activate() callback before calling\ndevice_add_groups().(CVE-2024-43830)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nbpf, arm64: Fix trampoline for BPF_TRAMP_F_CALL_ORIG\r\n\r\nWhen BPF_TRAMP_F_CALL_ORIG is set, the trampoline calls\n__bpf_tramp_enter() and __bpf_tramp_exit() functions, passing them\nthe struct bpf_tramp_image *im pointer as an argument in R0.\r\n\r\nThe trampoline generation code uses emit_addr_mov_i64() to emit\ninstructions for moving the bpf_tramp_image address into R0, but\nemit_addr_mov_i64() assumes the address to be in the vmalloc() space\nand uses only 48 bits. Because bpf_tramp_image is allocated using\nkzalloc(), its address can use more than 48-bits, in this case the\ntrampoline will pass an invalid address to __bpf_tramp_enter/exit()\ncausing a kernel crash.\r\n\r\nFix this by using emit_a64_mov_i64() in place of emit_addr_mov_i64()\nas it can work with addresses that are greater than 48-bits.(CVE-2024-43840)\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\nRDMA/hns: Fix soft lockup under heavy CEQE load\r\n\r\nCEQEs are handled in interrupt handler currently. This may cause the\nCPU core staying in interrupt context too long and lead to soft lockup\nunder heavy load.\r\n\r\nHandle CEQEs in BH workqueue and set an upper limit for the number of\nCEQE handled by a single call of work handler.(CVE-2024-43872)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nmemcg: protect concurrent access to mem_cgroup_idr\r\n\r\nCommit 73f576c04b94 (\u0026quot;mm: memcontrol: fix cgroup creation failure after\nmany small jobs\u0026quot;) decoupled the memcg IDs from the CSS ID space to fix the\ncgroup creation failures.  It introduced IDR to maintain the memcg ID\nspace.  The IDR depends on external synchronization mechanisms for\nmodifications.  For the mem_cgroup_idr, the idr_alloc() and idr_replace()\nhappen within css callback and thus are protected through cgroup_mutex\nfrom concurrent modifications.  However idr_remove() for mem_cgroup_idr\nwas not protected against concurrency and can be run concurrently for\ndifferent memcgs when they hit their refcnt to zero.  Fix that.\r\n\r\nWe have been seeing list_lru based kernel crashes at a low frequency in\nour fleet for a long time.  These crashes were in different part of\nlist_lru code including list_lru_add(), list_lru_del() and reparenting\ncode.  Upon further inspection, it looked like for a given object (dentry\nand inode), the super_block\u0026apos;s list_lru didn\u0026apos;t have list_lru_one for the\nmemcg of that object.  The initial suspicions were either the object is\nnot allocated through kmem_cache_alloc_lru() or somehow\nmemcg_list_lru_alloc() failed to allocate list_lru_one() for a memcg but\nreturned success.  No evidence were found for these cases.\r\n\r\nLooking more deeply, we started seeing situations where valid memcg\u0026apos;s id\nis not present in mem_cgroup_idr and in some cases multiple valid memcgs\nhave same id and mem_cgroup_idr is pointing to one of them.  So, the most\nreasonable explanation is that these situations can happen due to race\nbetween multiple idr_remove() calls or race between\nidr_alloc()/idr_replace() and idr_remove().  These races are causing\nmultiple memcgs to acquire the same ID and then offlining of one of them\nwould cleanup list_lrus on the system for all of them.  Later access from\nother memcgs to the list_lru cause crashes due to missing list_lru_one.(CVE-2024-43892)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nserial: core: check uartclk for zero to avoid divide by zero\r\n\r\nCalling ioctl TIOCSSERIAL with an invalid baud_base can\nresult in uartclk being zero, which will result in a\ndivide by zero error in uart_get_divisor(). The check for\nuartclk being zero in uart_set_info() needs to be done\nbefore other settings are made as subsequent calls to\nioctl TIOCSSERIAL for the same port would be impacted if\nthe uartclk check was done where uartclk gets set.\r\n\r\nOops: divide error: 0000  PREEMPT SMP KASAN PTI\nRIP: 0010:uart_get_divisor (drivers/tty/serial/serial_core.c:580)\nCall Trace:\n \u0026lt;TASK\u0026gt;\nserial8250_get_divisor (drivers/tty/serial/8250/8250_port.c:2576\n    drivers/tty/serial/8250/8250_port.c:2589)\nserial8250_do_set_termios (drivers/tty/serial/8250/8250_port.c:502\n    drivers/tty/serial/8250/8250_port.c:2741)\nserial8250_set_termios (drivers/tty/serial/8250/8250_port.c:2862)\nuart_change_line_settings (./include/linux/spinlock.h:376\n    ./include/linux/serial_core.h:608 drivers/tty/serial/serial_core.c:222)\nuart_port_startup (drivers/tty/serial/serial_core.c:342)\nuart_startup (drivers/tty/serial/serial_core.c:368)\nuart_set_info (drivers/tty/serial/serial_core.c:1034)\nuart_set_info_user (drivers/tty/serial/serial_core.c:1059)\ntty_set_serial (drivers/tty/tty_io.c:2637)\ntty_ioctl (drivers/tty/tty_io.c:2647 drivers/tty/tty_io.c:2791)\n__x64_sys_ioctl (fs/ioctl.c:52 fs/ioctl.c:907\n    fs/ioctl.c:893 fs/ioctl.c:893)\ndo_syscall_64 (arch/x86/entry/common.c:52\n    (discriminator 1) arch/x86/entry/common.c:83 (discriminator 1))\nentry_SYSCALL_64_after_hwframe (arch/x86/entry/entry_64.S:130)\r\n\r\nRule: add(CVE-2024-43893)\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\nALSA: line6: Fix racy access to midibuf\r\n\r\nThere can be concurrent accesses to line6 midibuf from both the URB\ncompletion callback and the rawmidi API access.  This could be a cause\nof KMSAN warning triggered by syzkaller below (so put as reported-by\nhere).\r\n\r\nThis patch protects the midibuf call of the former code path with a\nspinlock for avoiding the possible races.(CVE-2024-44954)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\natm: idt77252: prevent use after free in dequeue_rx()\r\n\r\nWe can\u0026apos;t dereference \u0026quot;skb\u0026quot; after calling vcc-\u0026gt;push() because the skb\nis released.(CVE-2024-44998)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nxhci: Fix Panther point NULL pointer deref at full-speed re-enumeration\r\n\r\nre-enumerating full-speed devices after a failed address device command\ncan trigger a NULL pointer dereference.\r\n\r\nFull-speed devices may need to reconfigure the endpoint 0 Max Packet Size\nvalue during enumeration. Usb core calls usb_ep0_reinit() in this case,\nwhich ends up calling xhci_configure_endpoint().\r\n\r\nOn Panther point xHC the xhci_configure_endpoint() function will\nadditionally check and reserve bandwidth in software. Other hosts do\nthis in hardware\r\n\r\nIf xHC address device command fails then a new xhci_virt_device structure\nis allocated as part of re-enabling the slot, but the bandwidth table\npointers are not set up properly here.\nThis triggers the NULL pointer dereference the next time usb_ep0_reinit()\nis called and xhci_configure_endpoint() tries to check and reserve\nbandwidth\r\n\r\n[46710.713538] usb 3-1: new full-speed USB device number 5 using xhci_hcd\n[46710.713699] usb 3-1: Device not responding to setup address.\n[46710.917684] usb 3-1: Device not responding to setup address.\n[46711.125536] usb 3-1: device not accepting address 5, error -71\n[46711.125594] BUG: kernel NULL pointer dereference, address: 0000000000000008\n[46711.125600] #PF: supervisor read access in kernel mode\n[46711.125603] #PF: error_code(0x0000) - not-present page\n[46711.125606] PGD 0 P4D 0\n[46711.125610] Oops: Oops: 0000 [#1] PREEMPT SMP PTI\n[46711.125615] CPU: 1 PID: 25760 Comm: kworker/1:2 Not tainted 6.10.3_2 #1\n[46711.125620] Hardware name: Gigabyte Technology Co., Ltd.\n[46711.125623] Workqueue: usb_hub_wq hub_event [usbcore]\n[46711.125668] RIP: 0010:xhci_reserve_bandwidth (drivers/usb/host/xhci.c\r\n\r\nFix this by making sure bandwidth table pointers are set up correctly\nafter a failed address device command, and additionally by avoiding\nchecking for bandwidth in cases like this where no actual endpoints are\nadded or removed, i.e. only context for default control endpoint 0 is\nevaluated.(CVE-2024-45006)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\ns390/dasd: fix error recovery leading to data corruption on ESE devices\r\n\r\nExtent Space Efficient (ESE) or thin provisioned volumes need to be\nformatted on demand during usual IO processing.\r\n\r\nThe dasd_ese_needs_format function checks for error codes that signal\nthe non existence of a proper track format.\r\n\r\nThe check for incorrect length is to imprecise since other error cases\nleading to transport of insufficient data also have this flag set.\nThis might lead to data corruption in certain error cases for example\nduring a storage server warmstart.\r\n\r\nFix by removing the check for incorrect length and replacing by\nexplicitly checking for invalid track format in transport mode.\r\n\r\nAlso remove the check for file protected since this is not a valid\nESE handling case.(CVE-2024-45026)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nnfc: pn533: Add poll mod list filling check\r\n\r\nIn case of im_protocols value is 1 and tm_protocols value is 0 this\ncombination successfully passes the check\n\u0026apos;if (!im_protocols \u0026amp;\u0026amp; !tm_protocols)\u0026apos; in the nfc_start_poll().\nBut then after pn533_poll_create_mod_list() call in pn533_start_poll()\npoll mod list will remain empty and dev-\u0026gt;poll_mod_count will remain 0\nwhich lead to division by zero.\r\n\r\nNormally no im protocol has value 1 in the mask, so this combination is\nnot expected by driver. But these protocol values actually come from\nuserspace via Netlink interface (NFC_CMD_START_POLL operation). So a\nbroken or malicious program may pass a message containing a \u0026quot;bad\u0026quot;\ncombination of protocol parameter values so that dev-\u0026gt;poll_mod_count\nis not incremented inside pn533_poll_create_mod_list(), thus leading\nto division by zero.\nCall trace looks like:\nnfc_genl_start_poll()\n  nfc_start_poll()\n    -\u0026gt;start_poll()\n    pn533_start_poll()\r\n\r\nAdd poll mod list filling check.\r\n\r\nFound by Linux Verification Center (linuxtesting.org) with SVACE.(CVE-2024-46676)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nusb: typec: ucsi: Fix null pointer dereference in trace\r\n\r\nucsi_register_altmode checks IS_ERR for the alt pointer and treats\nNULL as valid. When CONFIG_TYPEC_DP_ALTMODE is not enabled,\nucsi_register_displayport returns NULL which causes a NULL pointer\ndereference in trace. Rather than return NULL, call\ntypec_port_register_altmode to register DisplayPort alternate mode\nas a non-controllable mode when CONFIG_TYPEC_DP_ALTMODE is not enabled.(CVE-2024-46719)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nbpf: Remove tst_run from lwt_seg6local_prog_ops.\r\n\r\nThe syzbot reported that the lwt_seg6 related BPF ops can be invoked\nvia bpf_test_run() without without entering input_action_end_bpf()\nfirst.\r\n\r\nMartin KaFai Lau said that self test for BPF_PROG_TYPE_LWT_SEG6LOCAL\nprobably didn\u0026apos;t work since it was introduced in commit 04d4b274e2a\n(\u0026quot;ipv6: sr: Add seg6local action End.BPF\u0026quot;). The reason is that the\nper-CPU variable seg6_bpf_srh_states::srh is never assigned in the self\ntest case but each BPF function expects it.\r\n\r\nRemove test_run for BPF_PROG_TYPE_LWT_SEG6LOCAL.(CVE-2024-46754)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nice: Add netif_device_attach/detach into PF reset flow\r\n\r\nEthtool callbacks can be executed while reset is in progress and try to\naccess deleted resources, e.g. getting coalesce settings can result in a\nNULL pointer dereference seen below.\r\n\r\nReproduction steps:\nOnce the driver is fully initialized, trigger reset:\n\t# echo 1 \u0026gt; /sys/class/net/\u0026lt;interface\u0026gt;/device/reset\nwhen reset is in progress try to get coalesce settings using ethtool:\n\t# ethtool -c \u0026lt;interface\u0026gt;\r\n\r\nBUG: kernel NULL pointer dereference, address: 0000000000000020\nPGD 0 P4D 0\nOops: Oops: 0000 [#1] PREEMPT SMP PTI\nCPU: 11 PID: 19713 Comm: ethtool Tainted: G S                 6.10.0-rc7+ #7\nRIP: 0010:ice_get_q_coalesce+0x2e/0xa0 [ice]\nRSP: 0018:ffffbab1e9bcf6a8 EFLAGS: 00010206\nRAX: 000000000000000c RBX: ffff94512305b028 RCX: 0000000000000000\nRDX: 0000000000000000 RSI: ffff9451c3f2e588 RDI: ffff9451c3f2e588\nRBP: 0000000000000000 R08: 0000000000000000 R09: 0000000000000000\nR10: ffff9451c3f2e580 R11: 000000000000001f R12: ffff945121fa9000\nR13: ffffbab1e9bcf760 R14: 0000000000000013 R15: ffffffff9e65dd40\nFS:  00007faee5fbe740(0000) GS:ffff94546fd80000(0000) knlGS:0000000000000000\nCS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033\nCR2: 0000000000000020 CR3: 0000000106c2e005 CR4: 00000000001706f0\nCall Trace:\n\u0026lt;TASK\u0026gt;\nice_get_coalesce+0x17/0x30 [ice]\ncoalesce_prepare_data+0x61/0x80\nethnl_default_doit+0xde/0x340\ngenl_family_rcv_msg_doit+0xf2/0x150\ngenl_rcv_msg+0x1b3/0x2c0\nnetlink_rcv_skb+0x5b/0x110\ngenl_rcv+0x28/0x40\nnetlink_unicast+0x19c/0x290\nnetlink_sendmsg+0x222/0x490\n__sys_sendto+0x1df/0x1f0\n__x64_sys_sendto+0x24/0x30\ndo_syscall_64+0x82/0x160\nentry_SYSCALL_64_after_hwframe+0x76/0x7e\nRIP: 0033:0x7faee60d8e27\r\n\r\nCalling netif_device_detach() before reset makes the net core not call\nthe driver when ethtool command is issued, the attempt to execute an\nethtool command during reset will result in the following message:\r\n\r\n    netlink error: No such device\r\n\r\ninstead of NULL pointer dereference. Once reset is done and\nice_rebuild() is executing, the netif_device_attach() is called to allow\nfor ethtool operations to occur again in a safe manner.(CVE-2024-46770)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nksmbd: unset the binding mark of a reused connection\r\n\r\nSteve French reported null pointer dereference error from sha256 lib.\ncifs.ko can send session setup requests on reused connection.\nIf reused connection is used for binding session, conn-\u0026gt;binding can\nstill remain true and generate_preauth_hash() will not set\nsess-\u0026gt;Preauth_HashValue and it will be NULL.\nIt is used as a material to create an encryption key in\nksmbd_gen_smb311_encryptionkey. -\u0026gt;Preauth_HashValue cause null pointer\ndereference error from crypto_shash_update().\r\n\r\nBUG: kernel NULL pointer dereference, address: 0000000000000000\n#PF: supervisor read access in kernel mode\n#PF: error_code(0x0000) - not-present page\nPGD 0 P4D 0\nOops: 0000 [#1] PREEMPT SMP PTI\nCPU: 8 PID: 429254 Comm: kworker/8:39\nHardware name: LENOVO 20MAS08500/20MAS08500, BIOS N2CET69W (1.52 )\nWorkqueue: ksmbd-io handle_ksmbd_work [ksmbd]\nRIP: 0010:lib_sha256_base_do_update.isra.0+0x11e/0x1d0 [sha256_ssse3]\n\u0026lt;TASK\u0026gt;\n? show_regs+0x6d/0x80\n? __die+0x24/0x80\n? page_fault_oops+0x99/0x1b0\n? do_user_addr_fault+0x2ee/0x6b0\n? exc_page_fault+0x83/0x1b0\n? asm_exc_page_fault+0x27/0x30\n? __pfx_sha256_transform_rorx+0x10/0x10 [sha256_ssse3]\n? lib_sha256_base_do_update.isra.0+0x11e/0x1d0 [sha256_ssse3]\n? __pfx_sha256_transform_rorx+0x10/0x10 [sha256_ssse3]\n? __pfx_sha256_transform_rorx+0x10/0x10 [sha256_ssse3]\n_sha256_update+0x77/0xa0 [sha256_ssse3]\nsha256_avx2_update+0x15/0x30 [sha256_ssse3]\ncrypto_shash_update+0x1e/0x40\nhmac_update+0x12/0x20\ncrypto_shash_update+0x1e/0x40\ngenerate_key+0x234/0x380 [ksmbd]\ngenerate_smb3encryptionkey+0x40/0x1c0 [ksmbd]\nksmbd_gen_smb311_encryptionkey+0x72/0xa0 [ksmbd]\nntlm_authenticate.isra.0+0x423/0x5d0 [ksmbd]\nsmb2_sess_setup+0x952/0xaa0 [ksmbd]\n__process_request+0xa3/0x1d0 [ksmbd]\n__handle_ksmbd_work+0x1c4/0x2f0 [ksmbd]\nhandle_ksmbd_work+0x2d/0xa0 [ksmbd]\nprocess_one_work+0x16c/0x350\nworker_thread+0x306/0x440\n? __pfx_worker_thread+0x10/0x10\nkthread+0xef/0x120\n? __pfx_kthread+0x10/0x10\nret_from_fork+0x44/0x70\n? __pfx_kthread+0x10/0x10\nret_from_fork_asm+0x1b/0x30\n\u0026lt;/TASK\u0026gt;(CVE-2024-46795)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\ndrm/amdgpu: the warning dereferencing obj for nbio_v7_4\r\n\r\nif ras_manager obj null, don\u0026apos;t print NBIO err data(CVE-2024-46819)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nELF: fix kernel.randomize_va_space double read\r\n\r\nELF loader uses \u0026quot;randomize_va_space\u0026quot; twice. It is sysctl and can change\nat any moment, so 2 loads could see 2 different values in theory with\nunpredictable consequences.\r\n\r\nIssue exactly one load for consistent value across one exec.(CVE-2024-46826)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nsched: sch_cake: fix bulk flow accounting logic for host fairness\r\n\r\nIn sch_cake, we keep track of the count of active bulk flows per host,\nwhen running in dst/src host fairness mode, which is used as the\nround-robin weight when iterating through flows. The count of active\nbulk flows is updated whenever a flow changes state.\r\n\r\nThis has a peculiar interaction with the hash collision handling: when a\nhash collision occurs (after the set-associative hashing), the state of\nthe hash bucket is simply updated to match the new packet that collided,\nand if host fairness is enabled, that also means assigning new per-host\nstate to the flow. For this reason, the bulk flow counters of the\nhost(s) assigned to the flow are decremented, before new state is\nassigned (and the counters, which may not belong to the same host\nanymore, are incremented again).\r\n\r\nBack when this code was introduced, the host fairness mode was always\nenabled, so the decrement was unconditional. When the configuration\nflags were introduced the *increment* was made conditional, but\nthe *decrement* was not. Which of course can lead to a spurious\ndecrement (and associated wrap-around to U16_MAX).\r\n\r\nAFAICT, when host fairness is disabled, the decrement and wrap-around\nhappens as soon as a hash collision occurs (which is not that common in\nitself, due to the set-associative hashing). However, in most cases this\nis harmless, as the value is only used when host fairness mode is\nenabled. So in order to trigger an array overflow, sch_cake has to first\nbe configured with host fairness disabled, and while running in this\nmode, a hash collision has to occur to cause the overflow. Then, the\nqdisc has to be reconfigured to enable host fairness, which leads to the\narray out-of-bounds because the wrapped-around value is retained and\nused as an array index. It seems that syzbot managed to trigger this,\nwhich is quite impressive in its own right.\r\n\r\nThis patch fixes the issue by introducing the same conditional check on\ndecrement as is used on increment.\r\n\r\nThe original bug predates the upstreaming of cake, but the commit listed\nin the Fixes tag touched that code, meaning that this patch won\u0026apos;t apply\nbefore that.(CVE-2024-46828)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nbtrfs: clean up our handling of refs == 0 in snapshot delete\r\n\r\nIn reada we BUG_ON(refs == 0), which could be unkind since we aren\u0026apos;t\nholding a lock on the extent leaf and thus could get a transient\nincorrect answer.  In walk_down_proc we also BUG_ON(refs == 0), which\ncould happen if we have extent tree corruption.  Change that to return\n-EUCLEAN.  In do_walk_down() we catch this case and handle it correctly,\nhowever we return -EIO, which -EUCLEAN is a more appropriate error code.\nFinally in walk_up_proc we have the same BUG_ON(refs == 0), so convert\nthat to proper error handling.  Also adjust the error message so we can\nactually do something with the information.(CVE-2024-46840)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nperf/x86/intel: Limit the period on Haswell\r\n\r\nRunning the ltp test cve-2015-3290 concurrently reports the following\nwarnings.\r\n\r\nperfevents: irq loop stuck!\n  WARNING: CPU: 31 PID: 32438 at arch/x86/events/intel/core.c:3174\n  intel_pmu_handle_irq+0x285/0x370\n  Call Trace:\n   \u0026lt;NMI\u0026gt;\n   ? __warn+0xa4/0x220\n   ? intel_pmu_handle_irq+0x285/0x370\n   ? __report_bug+0x123/0x130\n   ? intel_pmu_handle_irq+0x285/0x370\n   ? __report_bug+0x123/0x130\n   ? intel_pmu_handle_irq+0x285/0x370\n   ? report_bug+0x3e/0xa0\n   ? handle_bug+0x3c/0x70\n   ? exc_invalid_op+0x18/0x50\n   ? asm_exc_invalid_op+0x1a/0x20\n   ? irq_work_claim+0x1e/0x40\n   ? intel_pmu_handle_irq+0x285/0x370\n   perf_event_nmi_handler+0x3d/0x60\n   nmi_handle+0x104/0x330\r\n\r\nThanks to Thomas Gleixner\u0026apos;s analysis, the issue is caused by the low\ninitial period (1) of the frequency estimation algorithm, which triggers\nthe defects of the HW, specifically erratum HSW11 and HSW143. (For the\ndetails, please refer https://lore.kernel.org/lkml/87plq9l5d2.ffs@tglx/)\r\n\r\nThe HSW11 requires a period larger than 100 for the INST_RETIRED.ALL\nevent, but the initial period in the freq mode is 1. The erratum is the\nsame as the BDM11, which has been supported in the kernel. A minimum\nperiod of 128 is enforced as well on HSW.\r\n\r\nHSW143 is regarding that the fixed counter 1 may overcount 32 with the\nHyper-Threading is enabled. However, based on the test, the hardware\nhas more issues than it tells. Besides the fixed counter 1, the message\n\u0026apos;interrupt took too long\u0026apos; can be observed on any counter which was armed\nwith a period \u0026lt; 32 and two events expired in the same NMI. A minimum\nperiod of 32 is enforced for the rest of the events.\nThe recommended workaround code of the HSW143 is not implemented.\nBecause it only addresses the issue for the fixed counter. It brings\nextra overhead through extra MSR writing. No related overcounting issue\nhas been reported so far.(CVE-2024-46848)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nnet: dpaa: Pad packets to ETH_ZLEN\r\n\r\nWhen sending packets under 60 bytes, up to three bytes of the buffer\nfollowing the data may be leaked. Avoid this by extending all packets to\nETH_ZLEN, ensuring nothing is leaked in the padding. This bug can be\nreproduced by running\r\n\r\n\t$ ping -s 11 destination(CVE-2024-46854)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nnetfilter: nft_socket: fix sk refcount leaks\r\n\r\nWe must put \u0026apos;sk\u0026apos; reference before returning.(CVE-2024-46855)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nmptcp: pm: Fix uaf in __timer_delete_sync\r\n\r\nThere are two paths to access mptcp_pm_del_add_timer, result in a race\ncondition:\r\n\r\n     CPU1\t\t\t\tCPU2\n     ====                               ====\n     net_rx_action\n     napi_poll                          netlink_sendmsg\n     __napi_poll                        netlink_unicast\n     process_backlog                    netlink_unicast_kernel\n     __netif_receive_skb                genl_rcv\n     __netif_receive_skb_one_core       netlink_rcv_skb\n     NF_HOOK                            genl_rcv_msg\n     ip_local_deliver_finish            genl_family_rcv_msg\n     ip_protocol_deliver_rcu            genl_family_rcv_msg_doit\n     tcp_v4_rcv                         mptcp_pm_nl_flush_addrs_doit\n     tcp_v4_do_rcv                      mptcp_nl_remove_addrs_list\n     tcp_rcv_established                mptcp_pm_remove_addrs_and_subflows\n     tcp_data_queue                     remove_anno_list_by_saddr\n     mptcp_incoming_options             mptcp_pm_del_add_timer\n     mptcp_pm_del_add_timer             kfree(entry)\r\n\r\nIn remove_anno_list_by_saddr(running on CPU2), after leaving the critical\nzone protected by \u0026quot;pm.lock\u0026quot;, the entry will be released, which leads to the\noccurrence of uaf in the mptcp_pm_del_add_timer(running on CPU1).\r\n\r\nKeeping a reference to add_timer inside the lock, and calling\nsk_stop_timer_sync() with this reference, instead of \u0026quot;entry-\u0026gt;add_timer\u0026quot;.\r\n\r\nMove list_del(\u0026amp;entry-\u0026gt;list) to mptcp_pm_del_add_timer and inside the pm lock,\ndo not directly access any members of the entry outside the pm lock, which\ncan avoid similar \u0026quot;entry-\u0026gt;x\u0026quot; uaf.(CVE-2024-46858)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\ncrypto: stm32/cryp - call finalize with bh disabled\r\n\r\nThe finalize operation in interrupt mode produce a produces a spinlock\nrecursion warning. The reason is the fact that BH must be disabled\nduring this process.(CVE-2024-47658)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nspi: hisi-kunpeng: Add verification for the max_frequency provided by the firmware\r\n\r\nIf the value of max_speed_hz is 0, it may cause a division by zero\nerror in hisi_calc_effective_speed().\nThe value of max_speed_hz is provided by firmware.\nFirmware is generally considered as a trusted domain. However, as\ndivision by zero errors can cause system failure, for defense measure,\nthe value of max_speed is validated here. So 0 is regarded as invalid\nand an error code is returned.(CVE-2024-47664)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nocfs2: add bounds checking to ocfs2_xattr_find_entry()\r\n\r\nAdd a paranoia check to make sure it doesn\u0026apos;t stray beyond valid memory\nregion containing ocfs2 xattr entries when scanning for a match.  It will\nprevent out-of-bound access in case of crafted images.(CVE-2024-47670)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nUSB: usbtmc: prevent kernel-usb-infoleak\r\n\r\nThe syzbot reported a kernel-usb-infoleak in usbtmc_write,\nwe need to clear the structure before filling fields.(CVE-2024-47671)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nwifi: iwlwifi: mvm: don\u0026apos;t wait for tx queues if firmware is dead\r\n\r\nThere is a WARNING in iwl_trans_wait_tx_queues_empty() (that was\nrecently converted from just a message), that can be hit if we\nwait for TX queues to become empty after firmware died. Clearly,\nwe can\u0026apos;t expect anything from the firmware after it\u0026apos;s declared dead.\r\n\r\nDon\u0026apos;t call iwl_trans_wait_tx_queues_empty() in this case. While it could\nbe a good idea to stop the flow earlier, the flush functions do some\nmaintenance work that is not related to the firmware, so keep that part\nof the code running even when the firmware is not running.\r\n\r\n[edit commit message](CVE-2024-47672)","status":"published","published":"2024-10-18T11:07:44Z","modified":"2026-08-18T01:17:34.647251189Z","cvss":[{"version":"3.1","score":9.8,"vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H","level":"critical"}],"updated_at":"2026-11-02T15:52:41.595342Z"},{"id":"ROOT-OS-DEBIAN-11-CVE-2021-47382","title":"CVE-2021-47382 in linux - Patched by Root","description":"Root has patched CVE-2021-47382 in the linux package for Root:Debian:11. Multiple fixed versions available.","status":"published","published":"2026-08-23T09:13:41Z","modified":"2026-08-23T10:15:51.12806048Z","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:53:28.544053Z"},{"id":"UBUNTU-CVE-2021-47382","description":"In the Linux kernel, the following vulnerability has been resolved: s390/qeth: fix deadlock during failing recovery Commit 0b9902c1fcc5 (\"s390/qeth: fix deadlock during recovery\") removed taking discipline_mutex inside qeth_do_reset(), fixing potential deadlocks. An error path was missed though, that still takes discipline_mutex and thus has the original deadlock potential. Intermittent deadlocks were seen when a qeth channel path is configured offline, causing a race between qeth_do_reset and ccwgroup_remove. Call qeth_set_offline() directly in the qeth_do_reset() error case and then a new variant of ccwgroup_set_offline(), without taking discipline_mutex.","status":"published","published":"2024-05-21T15:15:00Z","modified":"2025-10-24T04:52:00Z","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-02T16:53:48.688001Z"},{"id":"SUSE-SU-2024:1979-1","title":"Security update for the Linux Kernel","description":"\nThe SUSE Linux Enterprise 12 SP5 Azure kernel was updated to receive various security bugfixes.\n\nThe following security bugs were fixed:\n\n- CVE-2024-26921: Preserve kabi for sk_buff (bsc#1223138).\n- CVE-2022-48686: Fix UAF when detecting digest errors (bsc#1223948). Update blacklist.conf: remove entry\n- CVE-2021-47074: Fixed memory leak in nvme_loop_create_ctrl() (bsc#1220854).\n- CVE-2021-47378: Destroy cm id before destroy qp to avoid use after free (bsc#1225201).\n- CVE-2022-48697: Fix a use-after-free (bsc#1223922). Update blacklist.conf: drop entry from it\n- CVE-2024-26846: Do not wait in vain when unloading module (bsc#1223023).\n- CVE-2021-47496: Fix flipped sign in tls_err_abort() calls (bsc#1225354)\n- CVE-2023-42755: Check user supplied offsets (bsc#1215702).\n- CVE-2023-52664: Eliminate double free in error handling logic (bsc#1224747).\n- CVE-2023-52796: Add ipvlan_route_v6_outbound() helper (bsc#1224930).\n- CVE-2021-47246: Fix page reclaim for dead peer hairpin (bsc#1224831).\n- CVE-2023-52732: Blocklist the kclient when receiving corrupted snap trace (bsc#1225222 CVE-2023-52732).\n- CVE-2024-35936: Add missing mutex_unlock in btrfs_relocate_sys_chunks() (bsc#1224644)\n- CVE-2021-47548: Fixed a possible array out-of=bounds (bsc#1225506)\n- CVE-2024-36029: Pervent access to suspended controller (bsc#1225708 CVE-2024-36029)\n- CVE-2024-26625: Call sock_orphan() at release time (bsc#1221086)\n- CVE-2021-47352: Add validation for used length (bsc#1225124).\n- CVE-2023-52698: Fixed memory leak in netlbl_calipso_add_pass() (bsc#1224621)\n- CVE-2021-47431: Fix gart.bo pin_count leak (bsc#1225390).\n- CVE-2024-35935: Handle path ref underflow in header iterate_inode_ref() (bsc#1224645)\n- CVE-2024-26828: Fixed underflow in parse_server_interfaces() (bsc#1223084).\n- CVE-2021-47423: Fix file release memory leak (bsc#1225366).\n- CVE-2022-48710: Fix a possible null pointer dereference (bsc#1225230).\n- CVE-2021-47497: Fixed shift-out-of-bound (UBSAN) with byte size cells (bsc#1225355).\n- CVE-2024-35932: Do not check if plane-\u003estate-\u003efb == state-\u003efb (bsc#1224650).\n- CVE-2021-47500: Fixed trigger reference couting (bsc#1225360).\n- CVE-2024-35809: Drain runtime-idle callbacks before driver removal (bsc#1224738).\n- CVE-2021-47383: Fiedx out-of-bound vmalloc access in imageblit (bsc#1225208).\n- CVE-2021-47511: Fixed negative period/buffer sizes (bsc#1225411).\n- CVE-2021-47509: Limit the period size to 16MB (bsc#1225409).\n- CVE-2024-35877: Fixed VM_PAT handling in COW mappings (bsc#1224525).\n- CVE-2024-35982: Avoid infinite loop trying to resize local TT (bsc#1224566)\n- CVE-2024-35969: Fixed race condition between ipv6_get_ifaddr and ipv6_del_addr (bsc#1224580).\n- CVE-2021-47277: Avoid speculation-based attacks from out-of-range memslot accesses (bsc#1224960, CVE-2021-47277).\n- CVE-2024-35791: Flush pages under kvm-\u003elock to fix UAF in svm_register_enc_region() (bsc#1224725).\n- CVE-2021-47401: Fix stack information leak (bsc#1225242).\n- CVE-2023-52867: Fix possible buffer overflow (bsc#1225009).\n- CVE-2023-52821: Fix a possible null pointer dereference (bsc#1225022).\n- CVE-2021-47265: Verify port when creating flow rule (bsc#1224957)\n- CVE-2021-47362: Update intermediate power state for SI (bsc#1225153).\n- CVE-2021-47361: Fix error handling in mcb_alloc_bus() (bsc#1225151).\n- CVE-2023-52864: Fix opening of char device (bsc#1225132).\n- CVE-2022-48708: Fix potential NULL dereference (bsc#1224942).\n- CVE-2024-35944: Fixed memcpy() run-time warning in dg_dispatch_as_host() (bsc#1224648).\n- CVE-2021-47238: Fix memory leak in ip_mc_add1_src (bsc#1224847)\n- CVE-2023-52730: Fix possible resource leaks in some error paths (bsc#1224956).\n- CVE-2021-47355: Fix possible use-after-free in nicstar_cleanup() (bsc#1225141).\n- CVE-2021-47245: Fix out of bounds when parsing TCP options (bsc#1224838)\n- CVE-2024-35878: Prevent NULL pointer dereference in vsnprintf() (bsc#1224671).\n- CVE-2023-52747: Restore allocated resources on failed copyout (bsc#1224931)\n- CVE-2021-47249: Fix memory leak in rds_recvmsg (bsc#1224880)\n- CVE-2021-47397: Break out if skb_header_pointer returns NULL in sctp_rcv_ootb (bsc#1225082)\n- CVE-2021-47250: Fix memory leak in netlbl_cipsov4_add_std (bsc#1224827)\n- CVE-2024-35849: Fix information leak in btrfs_ioctl_logical_to_ino() (bsc#1224733).\n- CVE-2024-27436: Stop parsing channels bits when all channels are found (bsc#1224803).\n- CVE-2021-47281: Fix race of snd_seq_timer_open() (bsc#1224983).\n- CVE-2024-35789: Clear fast rx for non-4addr in VLAN netdev (bsc#1224749).\n- CVE-2024-35830: Register v4l2 async device only after successful setup (bsc#1224680).\n- CVE-2021-47334: Fix two use after free in ibmasm_init_one (bsc#1225112).\n- CVE-2021-47357: Fix possible use-after-free in ia_module_exit() (bsc#1225144).\n- CVE-2023-52875: Add check for mtk_alloc_clk_data (bsc#1225096).\n- CVE-2023-52865: Add check for mtk_alloc_clk_data (bsc#1225086).\n- CVE-2024-35887: Fix use-after-free bugs caused by ax25_ds_del_timer (bsc#1224663)\n- CVE-2021-47483: Fixed possible double-free in regcache_rbtree_exit() (bsc#1224907).\n- CVE-2024-26957: Fix reference counting on zcrypt card objects (bsc#1223666).\n- CVE-2023-52691: Fix a double-free in si_dpm_init (bsc#1224607).\n- CVE-2024-27398: Fixed use-after-free bugs caused by sco_sock_timeout (bsc#1224174).\n- CVE-2023-52586: Fixed mutex lock in control vblank irq (bsc#1221081).\n- CVE-2024-27062: Fixed nouveau lock inside client object tree (bsc#1223834).\n- CVE-2024-26984: Fix instmem race condition around ptr stores (bsc#1223633)\n- CVE-2021-46933: Fixed possible underflow in ffs_data_clear() (bsc#1220487).\n- CVE-2024-27396: Fixed Use-After-Free in gtp_dellink (bsc#1224096).\n- CVE-2023-52655: Check packet for fixup for true limit (bsc#1217169).\n- CVE-2024-26900: Fixed kmemleak of rdev-\u003eserial (bsc#1223046).\n- CVE-2024-27401: Fixed user_length taken into account when fetching packet contents (bsc#1224181).\n- CVE-2024-26775: Fixed potential deadlock at set_capacity (bsc#1222627).\n- CVE-2024-26958: Fixed UAF in direct writes (bsc#1223653).\n- CVE-2022-48704: Add a force flush to delay work when radeon (bsc#1223932)\n- CVE-2021-47206: Check return value after calling platform_get_resource() (bsc#1222894).\n- CVE-2024-26915: Reset IH OVERFLOW_CLEAR bit (bsc#1223207)\n- CVE-2024-26996: Fix UAF ncm object at re-bind after usb transport error (bsc#1223752).\n- CVE-2024-26874: Fix a null pointer crash in mtk_drm_crtc_finish_page_flip (bsc#1223048)\n- CVE-2023-1829: Fixed a use-after-free vulnerability in the control index filter (tcindex) (bsc#1210335).\n\nThe following non-security bugs were fixed:\n\n- af_unix: annote lockless accesses to unix_tot_inflight \u0026 gc_in_progress (bsc#1223384).\n- af_unix: Do not use atomic ops for unix_sk(sk)-\u003einflight (bsc#1223384).\n- af_unix: Replace BUG_ON() with WARN_ON_ONCE() (bsc#1223384).\n- ASoC: tracing: Export SND_SOC_DAPM_DIR_OUT to its value (git-fixes).\n- assoc_array: Fix BUG_ON during garbage collect.\n- autofs: fix a leak in autofs_expire_indirect() (git-fixes)\n- Bluetooth: btusb: Some Qualcomm Bluetooth adapters stop working (git-fixes).\n- btrfs: avoid null pointer dereference on fs_info when calling btrfs_crit (git-fixes)\n- btrfs: check if root is readonly while setting security xattr (git-fixes)\n- btrfs: defrag: use btrfs_mod_outstanding_extents in cluster_pages_for_defrag (git-fixes)\n- btrfs: do not get an EINTR during drop_snapshot for reloc (git-fixes)\n- btrfs: do not stop integrity writeback too early (git-fixes)\n- btrfs: Explicitly handle btrfs_update_root failure (git-fixes)\n- btrfs: fail mount when sb flag is not in BTRFS_SUPER_FLAG_SUPP (git-fixes)\n- btrfs: fix btrfs_prev_leaf() to not return the same key twice (git-fixes)\n- btrfs: fix deadlock when writing out space cache (git-fixes)\n- Btrfs: fix incorrect {node,sector}size endianness from BTRFS_IOC_FS_INFO (git-fixes)\n- btrfs: fix lockdep splat and potential deadlock after failure running delayed items (git-fixes)\n- btrfs: fix lost error handling when looking up extended ref on log replay (git-fixes)\n- btrfs: Fix NULL pointer exception in find_bio_stripe (git-fixes)\n- btrfs: Fix out of bounds access in btrfs_search_slot (git-fixes)\n- btrfs: fix race when deleting quota root from the dirty cow roots list (git-fixes)\n- btrfs: fix range_end calculation in extent_write_locked_range (git-fixes)\n- btrfs: fix return value mixup in btrfs_get_extent (git-fixes)\n- btrfs: fix unaligned access in readdir (git-fixes)\n- btrfs: limit device extents to the device size (git-fixes)\n- btrfs: prevent to set invalid default subvolid (git-fixes)\n- btrfs: record delayed inode root in transaction (git-fixes)\n- btrfs: scrub: reject unsupported scrub flags (git-fixes)\n- btrfs: send: ensure send_fd is writable (git-fixes)\n- btrfs: send: in case of IO error log it (git-fixes)\n- btrfs: send: limit number of clones and allocated memory size (git-fixes)\n- btrfs: sysfs: use NOFS for device creation (git-fixes) Adjustment: add #include\n- btrfs: tree-checker: add missing return after error in root_item (git-fixes)\n- btrfs: tree-checker: add missing returns after data_ref alignment checks (git-fixes)\n- btrfs: tree-checker: do not error out if extent ref hash does not match (git-fixes)\n- btrfs: tree-checker: fix inline ref size in error messages (git-fixes)\n- btrfs: tree-checker: Fix misleading group system information (git-fixes)\n- btrfs: undo writable superblocke when sprouting fails (git-fixes)\n- btrfs: validate qgroup inherit for SNAP_CREATE_V2 ioctl (git-fixes)\n- ecryptfs: fix a memory leak bug in ecryptfs_init_messaging() (git-fixes)\n- ecryptfs: fix a memory leak bug in parse_tag_1_packet() (git-fixes)\n- ecryptfs: fix kernel panic with null dev_name (git-fixes)\n- ecryptfs: Fix typo in message (git-fixes)\n- ep_create_wakeup_source(): dentry name can change under you (git-fixes)\n- exportfs_decode_fh(): negative pinned may become positive without the parent locked (git-fixes)\n- fs/proc/proc_sysctl.c: fix the default values of i_uid/i_gid on /proc/sys inodes (git-fixes)\n- fscrypt: clean up some BUG_ON()s in block encryption/decryption (git-fixes)\n- ila: do not generate empty messages in ila_xlat_nl_cmd_get_mapping() (git-fixes).\n- ipv4, ipv6: Fix handling of transhdrlen in __ip{,6}_append_data() (git-fixes).\n- kprobes: Fix possible use-after-free issue on kprobe registration (git-fixes).\n- KVM: s390: Check kvm pointer when testing KVM_CAP_S390_HPAGE_1M (git-fixes bsc#1225059).\n- l2tp: pass correct message length to ip6_append_data (git-fixes).\n- lib/mpi: use kcalloc in mpi_resize (git-fixes).\n- list: fix a data-race around ep-\u003erdllist (git-fixes).\n- net: 9p: avoid freeing uninit memory in p9pdu_vreadf (git-fixes).\n- net: tcp: fix unexcepted socket die when snd_wnd is 0 (git-fixes).\n- net: usb: ax88179_178a: stop lying about skb-\u003etruesize (git-fixes).\n- net: usb: smsc95xx: stop lying about skb-\u003etruesize (git-fixes).\n- net: usb: sr9700: stop lying about skb-\u003etruesize (git-fixes).\n- net: vmxnet3: Fix NULL pointer dereference in vmxnet3_rq_rx_complete() (bsc#1223360).\n- net/smc: fix fallback failed while sendmsg with fastopen (git-fixes).\n- netfilter: nf_queue: augment nfqa_cfg_policy (git-fixes).\n- netfilter: nft_compat: explicitly reject ERROR and standard target (git-fixes).\n- netfilter: x_tables: set module owner for icmp(6) matches (git-fixes).\n- nfc: change order inside nfc_se_io error path (git-fixes).\n- powerpc/pseries/lparcfg: drop error message from guest name lookup (bsc#1187716 ltc#193451 git-fixes).\n- ppdev: Add an error check in register_device (git-fixes).\n- rds: avoid unenecessary cong_update in loop transport (git-fixes).\n- rds: ib: Fix missing call to rds_ib_dev_put in rds_ib_setup_qp (git-fixes).\n- ring-buffer: Clean ring_buffer_poll_wait() error return (git-fixes).\n- ring-buffer: Fix a race between readers and resize checks (bsc#1222893).\n- rxrpc: Do not put crypto buffers on the stack (git-fixes).\n- rxrpc: Fix a memory leak in rxkad_verify_response() (git-fixes).\n- rxrpc: Provide a different lockdep key for call-\u003euser_mutex for kernel calls (git-fixes).\n- rxrpc: The mutex lock returned by rxrpc_accept_call() needs releasing (git-fixes).\n- rxrpc: Work around usercopy check (git-fixes).\n- s390/cpum_cf: make crypto counters upward compatible across machine types (bsc#1224347).\n- s390/pci: fix max size calculation in zpci_memcpy_toio() (git-fixes bsc#1225062).\n- tcp: tcp_make_synack() can be called from process context (git-fixes).\n- tracing: Fix blocked reader of snapshot buffer (git-fixes).\n- tracing: hide unused ftrace_event_id_fops (git-fixes).\n- tracing: Use .flush() call to wake up readers (git-fixes).\n- tracing: Use strncpy instead of memcpy when copying comm in trace.c (git-fixes).\n- usb: aqc111: stop lying about skb-\u003etruesize (git-fixes).\n- wifi: cfg80211: avoid leaking stack data into trace (git-fixes).\n- wifi: radiotap: fix kernel-doc notation warnings (git-fixes).\n","status":"published","published":"2024-06-11T07:41:39Z","modified":"2026-02-04T04:21:09.752601Z","updated_at":"2026-11-02T15:53:54.652421Z"},{"id":"SUSE-SU-2024:1983-1","title":"Security update for the Linux Kernel","description":"\nThe SUSE Linux Enterprise 12 SP5 RT kernel was updated to receive various security bugfixes.\n\nThe following security bugs were fixed:\n\n- CVE-2024-26921: Preserve kabi for sk_buff (bsc#1223138).\n- CVE-2022-48686: Fix UAF when detecting digest errors (bsc#1223948).\n- CVE-2021-47074: Fixed memory leak in nvme_loop_create_ctrl() (bsc#1220854).\n- CVE-2021-47378: Destroy cm id before destroy qp to avoid use after free (bsc#1225201).\n- CVE-2022-48697: Fix a use-after-free (bsc#1223922).\n- CVE-2024-26846: Do not wait in vain when unloading module (bsc#1223023).\n- CVE-2021-47496: Fix flipped sign in tls_err_abort() calls (bsc#1225354)\n- CVE-2023-42755: Check user supplied offsets (bsc#1215702).\n- CVE-2023-52664: Eliminate double free in error handling logic (bsc#1224747).\n- CVE-2023-52796: Add ipvlan_route_v6_outbound() helper (bsc#1224930).\n- CVE-2021-47246: Fix page reclaim for dead peer hairpin (bsc#1224831).\n- CVE-2023-52732: Blocklist the kclient when receiving corrupted snap trace (bsc#1225222).\n- CVE-2024-35936: Add missing mutex_unlock in btrfs_relocate_sys_chunks() (bsc#1224644)\n- CVE-2021-47548: Fixed a possible array out-of-bounds (bsc#1225506)\n- CVE-2024-36029: Pervent access to suspended controller (bsc#1225708)\n- CVE-2024-26625: Call sock_orphan() at release time (bsc#1221086)\n- CVE-2021-47352: Add validation for used length (bsc#1225124).\n- CVE-2023-52698: Fixed memory leak in netlbl_calipso_add_pass() (bsc#1224621)\n- CVE-2021-47431: Fix gart.bo pin_count leak (bsc#1225390).\n- CVE-2024-35935: Handle path ref underflow in header iterate_inode_ref() (bsc#1224645)\n- CVE-2024-26828: Fixed underflow in parse_server_interfaces() (bsc#1223084).\n- CVE-2021-47423: Fix file release memory leak (bsc#1225366).\n- CVE-2022-48710: Fix a possible null pointer dereference (bsc#1225230).\n- CVE-2021-47497: Fixed shift-out-of-bound (UBSAN) with byte size cells (bsc#1225355).\n- CVE-2024-35932: Do not check if plane-\u003estate-\u003efb == state-\u003efb (bsc#1224650).\n- CVE-2021-47500: Fixed trigger reference couting (bsc#1225360).\n- CVE-2024-35809: Drain runtime-idle callbacks before driver removal (bsc#1224738).\n- CVE-2021-47383: Fiedx out-of-bound vmalloc access in imageblit (bsc#1225208).\n- CVE-2021-47511: Fixed negative period/buffer sizes (bsc#1225411).\n- CVE-2021-47509: Limit the period size to 16MB (bsc#1225409).\n- CVE-2024-35877: Fixed VM_PAT handling in COW mappings (bsc#1224525).\n- CVE-2024-35982: Avoid infinite loop trying to resize local TT (bsc#1224566)\n- CVE-2024-35969: Fixed race condition between ipv6_get_ifaddr and ipv6_del_addr (bsc#1224580).\n- CVE-2021-47277: Avoid speculation-based attacks from out-of-range memslot accesses (bsc#1224960).\n- CVE-2024-35791: Flush pages under kvm-\u003elock to fix UAF in svm_register_enc_region() (bsc#1224725).\n- CVE-2021-47401: Fix stack information leak (bsc#1225242).\n- CVE-2023-52867: Fix possible buffer overflow (bsc#1225009).\n- CVE-2023-52821: Fix a possible null pointer dereference (bsc#1225022).\n- CVE-2021-47265: Verify port when creating flow rule (bsc#1224957)\n- CVE-2021-47362: Update intermediate power state for SI (bsc#1225153).\n- CVE-2021-47361: Fix error handling in mcb_alloc_bus() (bsc#1225151).\n- CVE-2023-52864: Fix opening of char device (bsc#1225132).\n- CVE-2022-48708: Fix potential NULL dereference (bsc#1224942).\n- CVE-2024-35944: Fixed memcpy() run-time warning in dg_dispatch_as_host() (bsc#1224648).\n- CVE-2021-47238: Fix memory leak in ip_mc_add1_src (bsc#1224847)\n- CVE-2023-52730: Fix possible resource leaks in some error paths (bsc#1224956).\n- CVE-2021-47355: Fix possible use-after-free in nicstar_cleanup() (bsc#1225141).\n- CVE-2021-47245: Fix out of bounds when parsing TCP options (bsc#1224838)\n- CVE-2024-35878: Prevent NULL pointer dereference in vsnprintf() (bsc#1224671).\n- CVE-2023-52747: Restore allocated resources on failed copyout (bsc#1224931)\n- CVE-2021-47249: Fix memory leak in rds_recvmsg (bsc#1224880)\n- CVE-2021-47397: Break out if skb_header_pointer returns NULL in sctp_rcv_ootb (bsc#1225082)\n- CVE-2021-47250: Fix memory leak in netlbl_cipsov4_add_std (bsc#1224827)\n- CVE-2024-35849: Fix information leak in btrfs_ioctl_logical_to_ino() (bsc#1224733).\n- CVE-2024-27436: Stop parsing channels bits when all channels are found (bsc#1224803).\n- CVE-2021-47281: Fix race of snd_seq_timer_open() (bsc#1224983).\n- CVE-2024-35789: Clear fast rx for non-4addr sta VLAN changes (bsc#1224749).\n- CVE-2024-35830: Register v4l2 async device only after successful setup (bsc#1224680).\n- CVE-2021-47334: Fix two use after free in ibmasm_init_one (bsc#1225112).\n- CVE-2021-47357: Fix possible use-after-free in ia_module_exit() (bsc#1225144).\n- CVE-2023-52875: Add check for mtk_alloc_clk_data (bsc#1225096).\n- CVE-2023-52865: Add check for mtk_alloc_clk_data (bsc#1225086).\n- CVE-2024-35887: Fix use-after-free bugs caused by ax25_ds_del_timer (bzg#1224663)\n- CVE-2021-47483: Fixed possible double-free in regcache_rbtree_exit() (bsc#1224907).\n- CVE-2024-26957: Fix reference counting on zcrypt card objects (bsc#1223666).\n- CVE-2023-52691: Fix a double-free in si_dpm_init (bsc#1224607).\n- CVE-2024-27398: Fixed use-after-free bugs caused by sco_sock_timeout (bsc#1224174).\n- CVE-2023-52586: Fixed mutex lock in control vblank irq (bsc#1221081).\n- CVE-2024-27062: Fixed nouveau lock inside client object tree (bsc#1223834).\n- CVE-2024-26984: Fix instmem race condition around ptr stores (bsc#1223633)\n- CVE-2021-46933: Fixed possible underflow in ffs_data_clear() (bsc#1220487).\n- CVE-2024-27396: Fixed Use-After-Free in gtp_dellink (bsc#1224096).\n- CVE-2023-52655: Check packet for fixup for true limit (bsc#1217169).\n- CVE-2024-26900: Fixed kmemleak of rdev-\u003eserial (bsc#1223046).\n- CVE-2024-27401: Fixed user_length taken into account when fetching packet contents (bsc#1224181).\n- CVE-2024-26775: Fixed potential deadlock at set_capacity (bsc#1222627).\n- CVE-2024-26958: Fixed UAF in direct writes (bsc#1223653).\n- CVE-2022-48704: Add a force flush to delay work when radeon (bsc#1223932)\n- CVE-2021-47206: Check return value after calling platform_get_resource() (bsc#1222894).\n- CVE-2024-26915: Reset IH OVERFLOW_CLEAR bit (bsc#1223207)\n- CVE-2024-26996: Fix UAF ncm object at re-bind after usb ep transport error (bsc#1223752).\n- CVE-2024-26874: Fix a null pointer crash in mtk_drm_crtc_finish_page_flip (bsc#1223048)\n- CVE-2022-48702: Fix out of bounds access in snd_emu10k1_pcm_channel_alloc() (bsc#1223923).\n- CVE-2022-48672: Fix off-by-one error in unflatten_dt_nodes() (bsc#1223931).\n- CVE-2021-47113: Abort btrfs rename_exchange if we fail to insert the second ref (bsc#1221543).\n- CVE-2024-26791: Fixed properly validate device names in btrfs (bsc#1222793)\n- CVE-2021-47131: Fixed a use-after-free after the TLS device goes down and up (bsc#1221545).\n- CVE-2021-46955: Fixed an out-of-bounds read with openvswitch, when fragmenting IPv4 packets (bsc#1220513).\n- CVE-2024-0639: Fixed a denial-of-service vulnerability due to a deadlock found in sctp_auto_asconf_init in net/sctp/socket.c (bsc#1218917).\n- CVE-2024-27008: Fix out of bounds access (bsc#1223802).\n- CVE-2024-26876: Fixed crash on irq during probe (bsc#1223119).\n- CVE-2023-1829: Fixed a use-after-free vulnerability in the control index filter (tcindex) (bsc#1210335).\n\nThe following non-security bugs were fixed:\n\n- af_unix: annote lockless accesses to unix_tot_inflight \u0026 gc_in_progress (bsc#1223384).\n- af_unix: Do not use atomic ops for unix_sk(sk)-\u003einflight (bsc#1223384).\n- af_unix: Replace BUG_ON() with WARN_ON_ONCE() (bsc#1223384).\n- ASoC: tracing: Export SND_SOC_DAPM_DIR_OUT to its value (git-fixes).\n- assoc_array: Fix BUG_ON during garbage collect.\n- autofs: fix a leak in autofs_expire_indirect() (git-fixes)\n- Bluetooth: btusb: Some Qualcomm Bluetooth adapters stop working (git-fixes).\n- btrfs: avoid null pointer dereference on fs_info when calling btrfs_crit (git-fixes)\n- btrfs: check if root is readonly while setting security xattr (git-fixes)\n- btrfs: defrag: use btrfs_mod_outstanding_extents in cluster_pages_for_defrag (git-fixes)\n- btrfs: do not get an EINTR during drop_snapshot for reloc (git-fixes)\n- btrfs: do not stop integrity writeback too early (git-fixes)\n- btrfs: Explicitly handle btrfs_update_root failure (git-fixes)\n- btrfs: fail mount when sb flag is not in BTRFS_SUPER_FLAG_SUPP (git-fixes)\n- btrfs: fix btrfs_prev_leaf() to not return the same key twice (git-fixes)\n- btrfs: fix deadlock when writing out space cache (git-fixes)\n- Btrfs: fix incorrect {node,sector}size endianness from BTRFS_IOC_FS_INFO (git-fixes)\n- btrfs: fix lockdep splat and potential deadlock after failure running delayed items (git-fixes)\n- btrfs: fix lost error handling when looking up extended ref on log replay (git-fixes)\n- btrfs: Fix NULL pointer exception in find_bio_stripe (git-fixes)\n- btrfs: Fix out of bounds access in btrfs_search_slot (git-fixes)\n- btrfs: fix race when deleting quota root from the dirty cow roots list (git-fixes)\n- btrfs: fix range_end calculation in extent_write_locked_range (git-fixes)\n- btrfs: fix return value mixup in btrfs_get_extent (git-fixes)\n- btrfs: fix unaligned access in readdir (git-fixes)\n- btrfs: limit device extents to the device size (git-fixes)\n- btrfs: prevent to set invalid default subvolid (git-fixes)\n- btrfs: record delayed inode root in transaction (git-fixes)\n- btrfs: scrub: reject unsupported scrub flags (git-fixes)\n- btrfs: send: ensure send_fd is writable (git-fixes)\n- btrfs: send: in case of IO error log it (git-fixes)\n- btrfs: send: limit number of clones and allocated memory size (git-fixes)\n- btrfs: sysfs: use NOFS for device creation (git-fixes) Adjustment: add #include\n- btrfs: tree-checker: add missing return after error in root_item (git-fixes)\n- btrfs: tree-checker: add missing returns after data_ref alignment checks (git-fixes)\n- btrfs: tree-checker: do not error out if extent ref hash does not match (git-fixes)\n- btrfs: tree-checker: fix inline ref size in error messages (git-fixes)\n- btrfs: tree-checker: Fix misleading group system information (git-fixes)\n- btrfs: undo writable superblocke when sprouting fails (git-fixes)\n- btrfs: validate qgroup inherit for SNAP_CREATE_V2 ioctl (git-fixes)\n- ecryptfs: fix a memory leak bug in ecryptfs_init_messaging() (git-fixes)\n- ecryptfs: fix a memory leak bug in parse_tag_1_packet() (git-fixes)\n- ecryptfs: fix kernel panic with null dev_name (git-fixes)\n- ecryptfs: Fix typo in message (git-fixes)\n- ep_create_wakeup_source(): dentry name can change under you (git-fixes)\n- exportfs_decode_fh(): negative pinned may become positive without the parent locked (git-fixes)\n- fs/proc/proc_sysctl.c: fix the default values of i_uid/i_gid on /proc/sys inodes (git-fixes)\n- fscrypt: clean up some BUG_ON()s in block encryption/decryption (git-fixes)\n- ila: do not generate empty messages in ila_xlat_nl_cmd_get_mapping() (git-fixes).\n- ipv4, ipv6: Fix handling of transhdrlen in __ip{,6}_append_data() (git-fixes).\n- kprobes: Fix possible use-after-free issue on kprobe registration (git-fixes).\n- KVM: s390: Check kvm pointer when testing KVM_CAP_S390_HPAGE_1M (git-fixes bsc#1225059).\n- l2tp: pass correct message length to ip6_append_data (git-fixes).\n- lib/mpi: use kcalloc in mpi_resize (git-fixes).\n- list: fix a data-race around ep-\u003erdllist (git-fixes).\n- net: 9p: avoid freeing uninit memory in p9pdu_vreadf (git-fixes).\n- net: tcp: fix unexcepted socket die when snd_wnd is 0 (git-fixes).\n- net: usb: ax88179_178a: stop lying about skb-\u003etruesize (git-fixes).\n- net: usb: smsc95xx: stop lying about skb-\u003etruesize (git-fixes).\n- net: usb: sr9700: stop lying about skb-\u003etruesize (git-fixes).\n- net: vmxnet3: Fix NULL pointer dereference in vmxnet3_rq_rx_complete() (bsc#1223360).\n- net/smc: fix fallback failed while sendmsg with fastopen (git-fixes).\n- net/tls: Remove the context from the list in tls_device_down (bsc#1221545).\n- netfilter: nf_queue: augment nfqa_cfg_policy (git-fixes).\n- netfilter: nft_compat: explicitly reject ERROR and standard target (git-fixes).\n- netfilter: x_tables: set module owner for icmp(6) matches (git-fixes).\n- nfc: change order inside nfc_se_io error path (git-fixes).\n- powerpc/pseries/lparcfg: drop error message from guest name lookup (bsc#1187716 ltc#193451 git-fixes).\n- ppdev: Add an error check in register_device (git-fixes).\n- printk: Disable passing console lock owner completely during panic() (bsc#1197894).\n- printk: Update @console_may_schedule in console_trylock_spinning() (bsc#1223969).\n- rds: avoid unenecessary cong_update in loop transport (git-fixes).\n- rds: ib: Fix missing call to rds_ib_dev_put in rds_ib_setup_qp (git-fixes).\n- ring-buffer: Clean ring_buffer_poll_wait() error return (git-fixes).\n- ring-buffer: Fix a race between readers and resize checks (bsc#1222893).\n- rxrpc: Do not put crypto buffers on the stack (git-fixes).\n- rxrpc: Fix a memory leak in rxkad_verify_response() (git-fixes).\n- rxrpc: Provide a different lockdep key for call-\u003euser_mutex for kernel calls (git-fixes).\n- rxrpc: The mutex lock returned by rxrpc_accept_call() needs releasing (git-fixes).\n- rxrpc: Work around usercopy check (git-fixes).\n- s390/cpum_cf: make crypto counters upward compatible across machine types (bsc#1224347).\n- s390/pci: fix max size calculation in zpci_memcpy_toio() (git-fixes bsc#1225062).\n- tcp: tcp_make_synack() can be called from process context (git-fixes).\n- tls: Fix context leak on tls_device_down (bsc#1221545).\n- tracing: Fix blocked reader of snapshot buffer (git-fixes).\n- tracing: hide unused ftrace_event_id_fops (git-fixes).\n- tracing: Use .flush() call to wake up readers (git-fixes).\n- tracing: Use strncpy instead of memcpy when copying comm in trace.c (git-fixes).\n- tty/sysrq: replace smp_processor_id() with get_cpu() (bsc#1223540).\n- usb: aqc111: stop lying about skb-\u003etruesize (git-fixes).\n- wifi: cfg80211: avoid leaking stack data into trace (git-fixes).\n- wifi: radiotap: fix kernel-doc notation warnings (git-fixes).\n","status":"published","published":"2024-06-11T10:56:58Z","modified":"2026-02-04T03:51:56.608318Z","updated_at":"2026-11-02T15:53:54.652421Z"},{"id":"SUSE-SU-2024:2008-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\n\nThe following security bugs were fixed:\n\n- CVE-2021-47548: Fixed a possible array out-of=bounds (bsc#1225506)\n- CVE-2022-48689: Fixed data-race in lru_add_fn (bsc#1223959)\n- CVE-2022-48691: Fixed memory leak in netfilter (bsc#1223961)\n- CVE-2023-1829: Fixed a use-after-free vulnerability in the control index filter (tcindex) (bsc#1210335).\n- CVE-2023-42755: Check user supplied offsets (bsc#1215702).\n- CVE-2023-52586: Fixed  mutex lock in control vblank irq (bsc#1221081).\n- CVE-2023-52618: Fixed string overflow in block/rnbd-srv (bsc#1221615).\n- CVE-2023-52656: Dropped any code related to SCM_RIGHTS (bsc#1224187).\n- CVE-2023-52660: Fiedx IRQ handling due to shared interrupts  (bsc#1224443).\n- CVE-2023-52664: Eliminate double free in error handling logic  (bsc#1224747).\n- CVE-2023-52671: Fixed hang/underflow when transitioning to ODM4:1 (bsc#1224729).\n- CVE-2023-52674: Add clamp() in scarlett2_mixer_ctl_put()  (bsc#1224727).\n- CVE-2023-52680: Fixed missing error checks to *_ctl_get()  (bsc#1224608).\n- CVE-2023-52692: Fixed missing error check to  scarlett2_usb_set_config() (bsc#1224628).\n- CVE-2023-52698: Fixed memory leak in netlbl_calipso_add_pass()  (CVE-2023-52698 bsc#1224621)\n- CVE-2023-52746: Prevent potential spectre v1 gadget in xfrm_xlate32_attr()  (bsc#1225114)\n- CVE-2023-52757: Fixed potential deadlock when releasing mids  (bsc#1225548).\n- CVE-2023-52795: Fixed use after free in vhost_vdpa_probe()  (bsc#1225085).\n- CVE-2023-52796: Add ipvlan_route_v6_outbound() helper (bsc#1224930).\n- CVE-2023-52807: Fixed out-of-bounds access may occur when coalesce  info is read via debugfs (bsc#1225097).\n- CVE-2023-52860: Fixed null pointer dereference in hisi_hns3 (bsc#1224936).\n- CVE-2024-2201: Fixed information leak in x86/BHI (bsc#1217339).\n- CVE-2024-26643: Fixed mark set as dead when unbinding anonymous  set with timeout (bsc#1221829).\n- CVE-2024-26679: Fixed read sk-\u003esk_family once in inet_recv_error() (bsc#1222385).\n- CVE-2024-26692: Fixed regression in writes when non-standard maximum write  size negotiated (bsc#1222464).\n- CVE-2024-26715: Fixed NULL pointer dereference in  dwc3_gadget_suspend (bsc#1222561).\n- CVE-2024-26742: Fixed disable_managed_interrupts (git-fixes  bsc#1222608).\n- CVE-2024-26775: Fixed potential deadlock at set_capacity (bsc#1222627).\n- CVE-2024-26791: Fixed properly validate device names in btrfs (bsc#1222793)\n- CVE-2024-26822: Set correct id, uid and cruid for multiuser  automounts (bsc#1223011).\n- CVE-2024-26828: Fixed underflow in parse_server_interfaces() (bsc#1223084).\n- CVE-2024-26876: Fixed crash on irq during probe (bsc#1223119).\n- CVE-2024-26900: Fixed kmemleak of rdev-\u003eserial (bsc#1223046).\n- CVE-2024-26915: Reset IH OVERFLOW_CLEAR bit (bsc#1223207)\n- CVE-2024-26919: Fixed debugfs directory leak (bsc#1223847).\n- CVE-2024-26921: Preserve kabi for sk_buff (bsc#1223138).\n- CVE-2024-26925: Release mutex after nft_gc_seq_end from abort path (bsc#1223390).\n- CVE-2024-26928: Fixed potential UAF in cifs_debug_files_proc_show() (bsc#1223532).\n- CVE-2024-26939: Fixed UAF on destroy against retire race (bsc#1223679).\n- CVE-2024-26958: Fixed UAF in direct writes (bsc#1223653).\n- CVE-2024-27042: Fixed potential out-of-bounds access in 'amdgpu_discovery_reg_base_init()' (bsc#1223823).\n- CVE-2024-27395: Fixed Use-After-Free in ovs_ct_exit (bsc#1224098).\n- CVE-2024-27396: Fixed Use-After-Free in gtp_dellink (bsc#1224096).\n- CVE-2024-27398: Fixed use-after-free bugs caused by sco_sock_timeout (bsc#1224174).\n- CVE-2024-27401: Fixed user_length taken into account when  fetching packet contents (bsc#1224181).\n- CVE-2024-27417: Fixed potential 'struct net' leak in inet6_rtm_getaddr()  (bsc#1224721)\n- CVE-2024-27419: Fixed data-races around sysctl_net_busy_read  (bsc#1224759)\n- CVE-2024-27431: Fixed Zero-initialise xdp_rxq_info struct before running  XDP program (bsc#1224718).\n- CVE-2024-35791: Flush pages under kvm-\u003elock to fix UAF in  svm_register_enc_region() (bsc#1224725).\n- CVE-2024-35799: Prevent crash when disable stream (bsc#1224740).\n- CVE-2024-35804: Mark target gfn of emulated atomic instruction as  dirty (bsc#1224638).\n- CVE-2024-35852: Fixed memory leak when canceling rehash  work (bsc#1224502).\n- CVE-2024-35854: Fixed possible use-after-free during  rehash (bsc#1224636).\n- CVE-2024-35860: struct bpf_link and bpf_link_ops kABI workaround  (bsc#1224531).\n- CVE-2024-35861: Fixed potential UAF in  cifs_signal_cifsd_for_reconnect() (bsc#1224766).\n- CVE-2024-35862: Fixed potential UAF in smb2_is_network_name_deleted()  (bsc#1224764).\n- CVE-2024-35863: Fixed potential UAF in is_valid_oplock_break() (bsc#1224763).\n- CVE-2024-35864: Fixed potential UAF in smb2_is_valid_lease_break()  (bsc#1224765).\n- CVE-2024-35865: Fixed potential UAF in smb2_is_valid_oplock_break()  (bsc#1224668).\n- CVE-2024-35866: Fixed potential UAF in cifs_dump_full_key()  (bsc#1224667).\n- CVE-2024-35867: Fixed potential UAF in cifs_stats_proc_show() (bsc#1224664).\n- CVE-2024-35868: Fixed potential UAF in cifs_stats_proc_write() (bsc#1224678).\n- CVE-2024-35869: Guarantee refcounted children from parent session  (bsc#1224679).\n- CVE-2024-35870: Fixed UAF in smb2_reconnect_server() (bsc#1224672).\n- CVE-2024-35872: Fixed GUP-fast succeeding on secretmem folios  (bsc#1224530).\n- CVE-2024-35875: Require seeding RNG with RDRAND on CoCo systems (bsc#1224665).\n- CVE-2024-35877: Fixed VM_PAT handling in COW mappings (bsc#1224525).\n- CVE-2024-35878: Prevent NULL pointer dereference in vsnprintf()  (bsc#1224671).\n- CVE-2024-35879: kABI workaround for drivers/of/dynamic.c (bsc#1224524).\n- CVE-2024-35885: Stop interface during shutdown (bsc#1224519).\n- CVE-2024-35904: Fixed dereference of garbage after mount failure (bsc#1224494).\n- CVE-2024-35905: Fixed int overflow for stack access size  (bsc#1224488).\n- CVE-2024-35907: Call request_irq() after NAPI initialized  (bsc#1224492).\n- CVE-2024-35924: Limit read size on v1.2 (bsc#1224657).\n- CVE-2024-35939: Fixed leak pages on dma_set_decrypted() failure (bsc#1224535).\n- CVE-2024-35943: Fixed a null pointer dereference in omap_prm_domain_init (bsc#1224649).\n- CVE-2024-35944: Fixed memcpy() run-time warning in dg_dispatch_as_host()  (bsc#1224648).\n- CVE-2024-35951: Fixed the error path in panfrost_mmu_map_fault_addr() (bsc#1224701).\n- CVE-2024-35959: Fixed mlx5e_priv_init() cleanup flow (bsc#1224666).\n- CVE-2024-35964: Fixed not validating setsockopt user input  (bsc#1224581).\n- CVE-2024-35969: Fixed race condition between ipv6_get_ifaddr and ipv6_del_addr  (bsc#1224580).\n- CVE-2024-35973: Fixed header validation in geneve[6]_xmit_skb  (bsc#1224586).\n- CVE-2024-35976: Validate user input for XDP_{UMEM|COMPLETION}_FILL_RING  (bsc#1224575).\n- CVE-2024-35998: Fixed lock ordering potential deadlock in  cifs_sync_mid_result (bsc#1224549).\n- CVE-2024-35999: Fixed missing lock when picking channel (bsc#1224550).\n- CVE-2024-36006: Fixed incorrect list API usage  (bsc#1224541).\n- CVE-2024-36007: Fixed warning during rehash  (bsc#1224543).\n- CVE-2024-36938: Fixed NULL pointer dereference in  sk_psock_skb_ingress_enqueue (bsc#1225761).\n\nThe following non-security bugs were fixed:\n\n- 9p: explicitly deny setlease attempts (git-fixes).\n- ACPI: bus: Indicate support for _TFP thru _OSC (git-fixes).\n- ACPI: disable -Wstringop-truncation (git-fixes).\n- ACPI: Fix Generic Initiator Affinity _OSC bit (git-fixes).\n- ACPI: LPSS: Advertise number of chip selects via property (git-fixes).\n- admin-guide/hw-vuln/core-scheduling: fix return type of PR_SCHED_CORE_GET (git-fixes).\n- af_unix: annote lockless accesses to unix_tot_inflight \u0026 gc_in_progress (bsc#1223384).\n- af_unix: Do not use atomic ops for unix_sk(sk)-\u003einflight (bsc#1223384).\n- af_unix: Replace BUG_ON() with WARN_ON_ONCE() (bsc#1223384).\n- ALSA: core: Fix NULL module pointer assignment at card init (git-fixes).\n- ALSA: hda/cs_dsp_ctl: Use private_free for control cleanup (git-fixes).\n- ALSA: line6: Zero-initialize message buffers (stable-fixes).\n- ARM: 9381/1: kasan: clear stale stack poison (git-fixes).\n- ASoC: Intel: avs: Fix ASRC module initialization (git-fixes).\n- ASoC: Intel: avs: Fix potential integer overflow (git-fixes).\n- ASoC: Intel: avs: ssm4567: Do not ignore route checks (git-fixes).\n- ASoC: Intel: Disable route checks for Skylake boards (git-fixes).\n- ASoC: kirkwood: Fix potential NULL dereference (git-fixes).\n- ASoC: mediatek: mt8192: fix register configuration for tdm (git-fixes).\n- ASoC: meson: axg-fifo: use FIELD helpers (stable-fixes).\n- ASoC: meson: axg-fifo: use threaded irq to check periods (git-fixes).\n- ASoC: tas2552: Add TX path for capturing AUDIO-OUT data (git-fixes).\n- ASoC: tracing: Export SND_SOC_DAPM_DIR_OUT to its value (git-fixes).\n- ata: pata_legacy: make legacy_exit() work again (git-fixes).\n- ata: sata_gemini: Check clk_enable() result (stable-fixes).\n- autofs: use wake_up() instead of wake_up_interruptible(() (bsc#1224166).\n- Bluetooth: Fix use-after-free bugs caused by sco_sock_timeout (git-fixes).\n- Bluetooth: hci_sync: Avoid use-after-free in dbg for hci_add_adv_monitor() (git-fixes).\n- Bluetooth: hci_sync: Do not double print name in add/remove adv_monitor (bsc#1216358).\n- Bluetooth: l2cap: fix null-ptr-deref in l2cap_chan_timeout (git-fixes).\n- Bluetooth: msft: fix slab-use-after-free in msft_do_close() (git-fixes).\n- Bluetooth: qca: add missing firmware sanity checks (git-fixes).\n- Bluetooth: qca: Fix error code in qca_read_fw_build_info() (git-fixes).\n- Bluetooth: qca: fix firmware check error path (git-fixes).\n- Bluetooth: qca: fix info leak when fetching fw build id (git-fixes).\n- Bluetooth: qca: fix NVM configuration parsing (git-fixes).\n- bnxt_re: avoid shift undefined behavior in bnxt_qplib_alloc_init_hwq (git-fixes)\n- bpf: decouple prune and jump points (bsc#1225756).\n- bpf: fix precision backtracking instruction iteration (bsc#1225756).\n- bpf: Fix precision tracking for BPF_ALU | BPF_TO_BE | BPF_END (git-fixes).\n- bpf: handle ldimm64 properly in check_cfg() (bsc#1225756).\n- bpf: mostly decouple jump history management from is_state_visited() (bsc#1225756).\n- bpf: remove unnecessary prune and jump points (bsc#1225756).\n- btrfs: add error messages to all unrecognized mount options (git-fixes)\n- btrfs: add missing mutex_unlock in btrfs_relocate_sys_chunks() (git-fixes)\n- btrfs: export: handle invalid inode or root reference in btrfs_get_parent() (git-fixes)\n- btrfs: extend locking to all space_info members accesses (git-fixes)\n- btrfs: fix btrfs_submit_compressed_write cgroup attribution (git-fixes)\n- btrfs: fix fallocate to use file_modified to update permissions consistently (git-fixes)\n- btrfs: fix information leak in btrfs_ioctl_logical_to_ino() (git-fixes)\n- btrfs: fix missing blkdev_put() call in btrfs_scan_one_device() (git-fixes)\n- btrfs: fix off-by-one chunk length calculation at contains_pending_extent() (git-fixes)\n- btrfs: fix qgroup reserve overflow the qgroup limit (git-fixes)\n- btrfs: fix silent failure when deleting root reference (git-fixes)\n- btrfs: fix use-after-free after failure to create a snapshot (git-fixes)\n- btrfs: free exchange changeset on failures (git-fixes)\n- btrfs: handle chunk tree lookup error in btrfs_relocate_sys_chunks() (git-fixes)\n- btrfs: make search_csum_tree return 0 if we get -EFBIG (git-fixes)\n- btrfs: prevent copying too big compressed lzo segment (git-fixes)\n- btrfs: remove BUG_ON(!eie) in find_parent_nodes (git-fixes)\n- btrfs: remove BUG_ON() in find_parent_nodes() (git-fixes)\n- btrfs: repair super block num_devices automatically (git-fixes)\n- btrfs: replace the BUG_ON in btrfs_del_root_ref with proper error handling (git-fixes)\n- btrfs: send: ensure send_fd is writable (git-fixes)\n- btrfs: send: handle path ref underflow in header iterate_inode_ref() (git-fixes)\n- btrfs: send: in case of IO error log it (git-fixes)\n- btrfs: send: return EOPNOTSUPP on unknown flags (git-fixes)\n- btrfs: tree-checker: check item_size for dev_item (git-fixes)\n- btrfs: tree-checker: check item_size for inode_item (git-fixes)\n- cifs: account for primary channel in the interface list (bsc#1224020).\n- cifs: cifs_chan_is_iface_active should be called with chan_lock held (bsc#1224020).\n- cifs: distribute channels across interfaces based on speed (bsc#1224020).\n- cifs: do not pass cifs_sb when trying to add channels (bsc#1224020).\n- cifs: failure to add channel on iface should bump up weight (git-fixes, bsc#1224020).\n- cifs: fix charset issue in reconnection (bsc#1224020).\n- cifs: fix leak of iface for primary channel (git-fixes, bsc#1224020).\n- cifs: handle cases where a channel is closed (bsc#1224020).\n- cifs: handle cases where multiple sessions share connection (bsc#1224020).\n- cifs: reconnect work should have reference on server struct (bsc#1224020).\n- clk: Do not hold prepare_lock when calling kref_put() (stable-fixes).\n- clk: qcom: mmcc-msm8998: fix venus clock issue (git-fixes).\n- counter: stm32-lptimer-cnt: Provide defines for clock polarities (git-fixes).\n- counter: stm32-timer-cnt: Provide defines for slave mode selection (git-fixes).\n- cppc_cpufreq: Fix possible null pointer dereference (git-fixes).\n- cpu/hotplug: Remove the 'cpu' member of cpuhp_cpu_state (git-fixes).\n- cpumask: Add for_each_cpu_from() (bsc#1225053).\n- crypto: bcm - Fix pointer arithmetic (git-fixes).\n- crypto: ccp - drop platform ifdef checks (git-fixes).\n- crypto: ecdsa - Fix module auto-load on add-key (git-fixes).\n- crypto: x86/nh-avx2 - add missing vzeroupper (git-fixes).\n- crypto: x86/sha256-avx2 - add missing vzeroupper (git-fixes).\n- crypto: x86/sha512-avx2 - add missing vzeroupper (git-fixes).\n- dmaengine: axi-dmac: fix possible race in remove() (git-fixes).\n- dmaengine: idma64: Add check for dma_set_max_seg_size (git-fixes).\n- dm/amd/pm: Fix problems with reboot/shutdown for some SMU 13.0.4/13.0.11 users (git-fixes).\n- dm-multipath: dont't attempt SG_IO on non-SCSI-disks (bsc#1223575).\n- docs: kernel_include.py: Cope with docutils 0.21 (stable-fixes).\n- drivers/nvme: Add quirks for device 126f:2262 (git-fixes).\n- drm/amd/display: Atom Integrated System Info v2_2 for DCN35 (stable-fixes).\n- drm/amd/display: Fix division by zero in setup_dsc_config (stable-fixes).\n- drm/amd/display: Fix potential index out of bounds in color transformation function (git-fixes).\n- drm/amd/display: Handle Y carry-over in VCP X.Y calculation (stable-fixes).\n- drm/amd: Flush GFXOFF requests in prepare stage (git-fixes).\n- drm/amdgpu: Refine IB schedule error logging (stable-fixes).\n- drm/amdkfd: do not allow mapping the MMIO HDP page with large pages (git-fixes).\n- drm/arm/malidp: fix a possible null pointer dereference (git-fixes).\n- drm/bridge: anx7625: Do not log an error when DSI host can't be found (git-fixes).\n- drm: bridge: cdns-mhdp8546: Fix possible null pointer dereference (git-fixes).\n- drm/bridge: dpc3433: Do not log an error when DSI host can't be found (git-fixes).\n- drm/bridge: icn6211: Do not log an error when DSI host can't be found (git-fixes).\n- drm/bridge: lt8912b: Do not log an error when DSI host can't be found (git-fixes).\n- drm/bridge: lt9611: Do not log an error when DSI host can't be found (git-fixes).\n- drm/bridge: tc358775: Do not log an error when DSI host can't be found (git-fixes).\n- drm/bridge: tc358775: fix support for jeida-18 and jeida-24 (git-fixes).\n- drm/connector: Add \\n to message about demoting connector force-probes (git-fixes).\n- drm/i915/bios: Fix parsing backlight BDB data (git-fixes).\n- drm/lcdif: Do not disable clocks on already suspended hardware (git-fixes).\n- drm/mediatek: Add 0 size check to mtk_drm_gem_obj (git-fixes).\n- drm/meson: dw-hdmi: add bandgap setting for g12 (git-fixes).\n- drm/meson: dw-hdmi: power up phy on device init (git-fixes).\n- drm/meson: vclk: fix calculation of 59.94 fractional rates (git-fixes).\n- drm/msm/dp: allow voltage swing / pre emphasis of 3 (git-fixes).\n- drm/msm/dpu: Always flush the slave INTF on the CTL (git-fixes).\n- drm/msm/dsi: Print dual-DSI-adjusted pclk instead of original mode pclk (git-fixes).\n- drm/nouveau/dp: Do not probe eDP ports twice harder (stable-fixes).\n- drm/panel: atna33xc20: Fix unbalanced regulator in the case HPD does not assert (git-fixes).\n- drm/panel: novatek-nt35950: Do not log an error when DSI host can't be found (git-fixes).\n- drm/panel: simple: Add missing Innolux G121X1-L03 format, flags, connector (git-fixes).\n- drm: vc4: Fix possible null pointer dereference (git-fixes).\n- dt-bindings: clock: qcom: Add missing UFS QREF clocks (git-fixes)\n- dyndbg: fix old BUG_ON in \u003econtrol parser (stable-fixes).\n- efi: libstub: only free priv.runtime_map when allocated (git-fixes).\n- extcon: max8997: select IRQ_DOMAIN instead of depending on it (git-fixes).\n- fail_function: fix wrong use of fei_attr_remove().\n- fbdev: savage: Handle err return when savagefb_check_var failed (git-fixes).\n- fbdev: shmobile: fix snprintf truncation (git-fixes).\n- fbdev: sisfb: hide unused variables (git-fixes).\n- firewire: ohci: mask bus reset interrupts between ISR and bottom half (stable-fixes).\n- firmware: dmi-id: add a release callback function (git-fixes).\n- firmware: raspberrypi: Use correct device for DMA mappings (git-fixes).\n- fs/9p: drop inodes immediately on non-.L too (git-fixes).\n- fs/9p: only translate RWX permissions for plain 9P2000 (git-fixes).\n- fs/9p: translate O_TRUNC into OTRUNC (git-fixes).\n- gpio: crystalcove: Use -ENOTSUPP consistently (stable-fixes).\n- gpio: wcove: Use -ENOTSUPP consistently (stable-fixes).\n- gpu: host1x: Do not setup DMA for virtual devices (stable-fixes).\n- HID: intel-ish-hid: ipc: Add check for pci_alloc_irq_vectors (git-fixes).\n- hwmon: (corsair-cpro) Protect ccp-\u003ewait_input_report with a spinlock (git-fixes).\n- hwmon: (corsair-cpro) Use a separate buffer for sending commands (git-fixes).\n- hwmon: (corsair-cpro) Use complete_all() instead of complete() in ccp_raw_event() (git-fixes).\n- hwmon: (lm70) fix links in doc and comments (git-fixes).\n- hwmon: (pmbus/ucd9000) Increase delay from 250 to 500us (git-fixes).\n- i3c: master: svc: change ENXIO to EAGAIN when IBI occurs during start frame (git-fixes).\n- i3c: master: svc: fix invalidate IBI type and miss call client IBI handler (git-fixes).\n- IB/mlx5: Use __iowrite64_copy() for write combining stores (git-fixes)\n- idpf: extend tx watchdog timeout (bsc#1224137).\n- iio: core: Leave private pointer NULL when no private data supplied (git-fixes).\n- iio: pressure: dps310: support negative temperature values (git-fixes).\n- Input: cyapa - add missing input core locking to suspend/resume functions (git-fixes).\n- Input: ims-pcu - fix printf string overflow (git-fixes).\n- Input: pm8xxx-vibrator - correct VIB_MAX_LEVELS calculation (git-fixes).\n- iomap: Fix inline extent handling in iomap_readpage (git-fixes)\n- iomap: iomap: fix memory corruption when recording errors during writeback (git-fixes)\n- iomap: Support partial direct I/O on user copy failures (git-fixes)\n- iommu/dma: Force swiotlb_max_mapping_size on an untrusted device (bsc#1224331)\n- io_uring/unix: drop usage of io_uring socket (git-fixes).\n- irqchip/gic-v3-its: Prevent double free on error (git-fixes).\n- jffs2: prevent xattr node from overflowing the eraseblock (git-fixes).\n- kABI: bpf: struct bpf_insn_aux_data kABI workaround (bsc#1225756).\n- kcm: do not sense pfmemalloc status in kcm_sendpage() (git-fixes bsc#1223959)\n- KEYS: trusted: Do not use WARN when encode fails (git-fixes).\n- KEYS: trusted: Fix memory leak in tpm2_key_encode() (git-fixes).\n- KVM: s390: Check kvm pointer when testing KVM_CAP_S390_HPAGE_1M (git-fixes bsc#1224794).\n- KVM: x86: Delete duplicate documentation for KVM_X86_SET_MSR_FILTER (git-fixes).\n- leds: pwm: Disable PWM when going to suspend (git-fixes).\n- libsubcmd: Fix parse-options memory leak (git-fixes).\n- locking/atomic: Make test_and_*_bit() ordered on failure (git-fixes).\n- media: atomisp: ssh_css: Fix a null-pointer dereference in load_video_binaries (git-fixes).\n- media: dt-bindings: ovti,ov2680: Fix the power supply names (git-fixes).\n- media: mc: mark the media devnode as registered from the, start (git-fixes).\n- media: ngene: Add dvb_ca_en50221_init return value check (git-fixes).\n- media: stk1160: fix bounds checking in stk1160_copy_video() (git-fixes).\n- mei: me: add lunar lake point M DID (stable-fixes).\n- mfd: intel-lpss: Revert 'Add missing check for platform_get_resource' (git-fixes).\n- mfd: ti_am335x_tscadc: Support the correctly spelled DT property (git-fixes).\n- mfd: tqmx86: Specify IO port register range more precisely (git-fixes).\n- mlxbf_gige: Enable the GigE port in mlxbf_gige_open (git-fixes).\n- mlxbf_gige: Fix intermittent no ip issue (git-fixes).\n- mlxbf_gige: stop PHY during open() error paths (git-fixes).\n- mmc: sdhci_am654: Add tuning algorithm for delay chain (git-fixes).\n- mmc: sdhci_am654: Write ITAPDLY for DDR52 timing (git-fixes).\n- mtd: core: Report error if first mtd_otp_size() call fails in mtd_otp_nvmem_add() (git-fixes).\n- mtd: rawnand: hynix: fixed typo (git-fixes).\n- net: do not sense pfmemalloc status in skb_append_pagefrags() (git-fixes bsc#1223959)\n- netfilter: nf_tables: bail out early if hardware offload is not supported (git-fixes bsc#1223961)\n- net: introduce __skb_fill_page_desc_noacc (git-fixes bsc#1223959)\n- net: nfc: remove inappropriate attrs check (stable-fixes).\n- net: qualcomm: rmnet: fix global oob in rmnet_policy (git-fixes).\n- net: usb: ax88179_178a: fix link status when link is set to down/up (git-fixes).\n- net:usb:qmi_wwan: support Rolling modules (stable-fixes).\n- net: usb: smsc95xx: stop lying about skb-\u003etruesize (git-fixes).\n- net: usb: sr9700: stop lying about skb-\u003etruesize (git-fixes).\n- net: vmxnet3: Fix NULL pointer dereference in vmxnet3_rq_rx_complete() (bsc#1223360).\n- nfc: nci: Fix handling of zero-length payload packets in nci_rx_work() (git-fixes).\n- nfc: nci: Fix uninit-value in nci_rx_work (git-fixes).\n- nilfs2: fix out-of-range warning (git-fixes).\n- nilfs2: fix unexpected freezing of nilfs_segctor_sync() (git-fixes).\n- nilfs2: fix use-after-free of timer for log writer thread (git-fixes).\n- nilfs2: make superblock data array index computation sparse friendly (git-fixes).\n- nvme: ensure disabling pairs with unquiesce (bsc#1224534).\n- nvme: fix miss command type check (git-fixes).\n- nvme: fix multipath batched completion accounting (git-fixes).\n- nvme-multipath: fix io accounting on failover (git-fixes).\n- nvmet: fix ns enable/disable possible hang (git-fixes).\n- PCI: dwc: Detect iATU settings after getting 'addr_space' resource (git-fixes).\n- PCI: dwc: ep: Fix DBI access failure for drivers requiring refclk from host (git-fixes).\n- PCI: dwc: Use the bitmap API to allocate bitmaps (git-fixes).\n- PCI/EDR: Align EDR_PORT_DPC_ENABLE_DSM with PCI Firmware r3.3 (git-fixes).\n- PCI/EDR: Align EDR_PORT_LOCATE_DSM with PCI Firmware r3.3 (git-fixes).\n- PCI: rockchip-ep: Remove wrong mask on subsys_vendor_id (git-fixes).\n- PCI: tegra194: Fix probe path for Endpoint mode (git-fixes).\n- pinctrl: armada-37xx: remove an unused variable (git-fixes).\n- pinctrl: core: delete incorrect free in pinctrl_enable() (git-fixes).\n- pinctrl: core: handle radix_tree_insert() errors in pinctrl_register_one_pin() (stable-fixes).\n- pinctrl: devicetree: fix refcount leak in pinctrl_dt_to_map() (git-fixes).\n- pinctrl/meson: fix typo in PDM's pin name (git-fixes).\n- pinctrl: pinctrl-aspeed-g6: Fix register offset for pinconf of GPIOR-T (git-fixes).\n- platform/x86/intel-uncore-freq: Do not present root domain on error (git-fixes).\n- platform/x86: xiaomi-wmi: Fix race condition when reporting key events (git-fixes).\n- powerpc/eeh: Permanently disable the removed device (bsc#1223991 ltc#205740).\n- powerpc/eeh: Small refactor of eeh_handle_normal_event() (bsc#1223991 ltc#205740).\n- powerpc/eeh: Use a goto for recovery failures (bsc#1223991 ltc#205740).\n- powerpc/powernv: Add a null pointer check in opal_event_init() (bsc#1065729).\n- powerpc/pseries/lparcfg: drop error message from guest name lookup (bsc#1187716 ltc#193451 git-fixes).\n- powerpc/pseries/vio: Do not return ENODEV if node or compatible missing (bsc#1220783).\n- powerpc/uaccess: Fix build errors seen with GCC 13/14 (bsc#1194869).\n- powerpc/uaccess: Use YZ asm constraint for ld (bsc#1194869).\n- power: rt9455: hide unused rt9455_boost_voltage_values (git-fixes).\n- ppdev: Add an error check in register_device (git-fixes).\n- printk: Update @console_may_schedule in console_trylock_spinning() (bsc#1225616).\n- qibfs: fix dentry leak (git-fixes)\n- RDMA/hns: Add max_ah and cq moderation capacities in query_device() (git-fixes)\n- RDMA/hns: Fix deadlock on SRQ async events. (git-fixes)\n- RDMA/hns: Fix GMV table pagesize (git-fixes)\n- RDMA/hns: Fix return value in hns_roce_map_mr_sg (git-fixes)\n- RDMA/hns: Fix UAF for cq async event (git-fixes)\n- RDMA/hns: Modify the print level of CQE error (git-fixes)\n- RDMA/hns: Use complete parentheses in macros (git-fixes)\n- RDMA/IPoIB: Fix format truncation compilation errors (git-fixes)\n- RDMA/mlx5: Adding remote atomic access flag to updatable flags (git-fixes)\n- RDMA/mlx5: Fix port number for counter query in multi-port configuration (git-fixes)\n- RDMA/rxe: Add ibdev_dbg macros for rxe (git-fixes)\n- RDMA/rxe: Fix incorrect rxe_put in error path (git-fixes)\n- RDMA/rxe: Fix seg fault in rxe_comp_queue_pkt (git-fixes)\n- RDMA/rxe: Fix the problem 'mutex_destroy missing' (git-fixes)\n- RDMA/rxe: Replace pr_xxx by rxe_dbg_xxx in rxe_net.c (git-fixes)\n- RDMA/rxe: Split rxe_run_task() into two subroutines (git-fixes)\n- regulator: bd71828: Do not overwrite runtime voltages (git-fixes).\n- regulator: core: fix debugfs creation regression (git-fixes).\n- regulator: mt6360: De-capitalize devicetree regulator subnodes (git-fixes).\n- remoteproc: mediatek: Make sure IPI buffer fits in L2TCM (git-fixes).\n- Rename colliding patches before origin/cve/linux-5.14-LTSS -\u003e SLE15-SP5 merge\n- Revert 'cifs: reconnect work should have reference on server struct' (git-fixes, bsc#1224020).\n- Revert 'drm/bridge: ti-sn65dsi83: Fix enable error path' (git-fixes).\n- ring-buffer: Fix a race between readers and resize checks (git-fixes).\n- s390/bpf: Emit a barrier for BPF_FETCH instructions (git-fixes bsc#1224795).\n- s390/cio: fix tracepoint subchannel type field (git-fixes bsc#1224796).\n- s390/cpum_cf: make crypto counters upward compatible across machine types (bsc#1224346).\n- s390/ipl: Fix incorrect initialization of len fields in nvme reipl block (git-fixes bsc#1225139).\n- s390/ipl: Fix incorrect initialization of nvme dump block (git-fixes bsc#1225138).\n- sched/topology: Optimize topology_span_sane() (bsc#1225053).\n- scsi: arcmsr: Support new PCI device IDs 1883 and 1886 (git-fixes).\n- scsi: bfa: Fix function pointer type mismatch for hcb_qe-\u003ecbfn (git-fixes).\n- scsi: core: Consult supported VPD page list prior to fetching page (git-fixes).\n- scsi: core: Fix unremoved procfs host directory regression (git-fixes).\n- scsi: csiostor: Avoid function pointer casts (git-fixes).\n- scsi: libfc: Do not schedule abort twice (git-fixes).\n- scsi: libfc: Fix up timeout error in fc_fcp_rec_error() (git-fixes).\n- scsi: lpfc: Add support for 32 byte CDBs (bsc#1225842).\n- scsi: lpfc: Change default logging level for unsolicited CT MIB commands (bsc#1225842).\n- scsi: lpfc: Change lpfc_hba hba_flag member into a bitmask (bsc#1225842).\n- scsi: lpfc: Clear deferred RSCN processing flag when driver is unloading (bsc#1225842).\n- scsi: lpfc: Copyright updates for 14.4.0.2 patches (bsc#1225842).\n- scsi: lpfc: Introduce rrq_list_lock to protect active_rrq_list (bsc#1225842).\n- scsi: lpfc: Update logging of protection type for T10 DIF I/O (bsc#1225842).\n- scsi: lpfc: Update lpfc version to 14.4.0.2 (bsc#1225842).\n- scsi: mpt3sas: Prevent sending diag_reset when the controller is ready (git-fixes).\n- scsi: mylex: Fix sysfs buffer lengths (git-fixes).\n- scsi: qla2xxx: Fix off by one in qla_edif_app_getstats() (git-fixes).\n- scsi: sd: Unregister device if device_add_disk() failed in sd_probe() (git-fixes).\n- selftests/pidfd: Fix config for pidfd_setns_test (git-fixes).\n- serial: 8250_bcm7271: use default_mux_rate if possible (git-fixes).\n- serial: kgdboc: Fix NMI-safety problems from keyboard reset code (stable-fixes).\n- serial: max3100: Fix bitwise types (git-fixes).\n- serial: max3100: Lock port-\u003elock when calling uart_handle_cts_change() (git-fixes).\n- serial: max3100: Update uart_driver_registered on driver removal (git-fixes).\n- serial: sc16is7xx: add proper sched.h include for sched_set_fifo() (git-fixes).\n- serial: sc16is7xx: fix bug in sc16is7xx_set_baud() when using prescaler (git-fixes).\n- serial: sh-sci: protect invalidating RXDMA on shutdown (git-fixes).\n- smb3: show beginning time for per share stats (bsc#1224020).\n- smb: client: ensure to try all targets when finding nested links (bsc#1224020).\n- smb: client: fix mount when dns_resolver key is not available (git-fixes, bsc#1224020).\n- smb: client: get rid of dfs code dep in namespace.c (bsc#1224020).\n- smb: client: get rid of dfs naming in automount code (bsc#1224020).\n- smb: client: introduce DFS_CACHE_TGT_LIST() (bsc#1224020).\n- smb: client: reduce stack usage in cifs_try_adding_channels() (bsc#1224020).\n- smb: client: remove extra @chan_count check in __cifs_put_smb_ses() (bsc#1224020).\n- smb: client: rename cifs_dfs_ref.c to namespace.c (bsc#1224020).\n- soc: mediatek: cmdq: Fix typo of CMDQ_JUMP_RELATIVE (git-fixes).\n- soc: qcom: rpmh-rsc: Enhance check for VRM in-flight request (git-fixes).\n- Sort recent BHI patches\n- speakup: Fix sizeof() vs ARRAY_SIZE() bug (git-fixes).\n- spmi: Add a check for remove callback when removing a SPMI driver (git-fixes).\n- spmi: hisi-spmi-controller: Do not override device identifier (git-fixes).\n- swiotlb: extend buffer pre-padding to alloc_align_mask if necessary (bsc#1224331). \n- swiotlb: Fix alignment checks when both allocation and DMA masks are (bsc#1224331)\n- swiotlb: Fix double-allocation of slots due to broken alignment (bsc#1224331)\n- swiotlb: Honour dma_alloc_coherent() alignment in swiotlb_alloc() (bsc#1224331)\n- sysv: do not call sb_bread() with pointers_lock held (git-fixes).\n- thermal/drivers/tsens: Fix null pointer dereference (git-fixes).\n- tools/latency-collector: Fix -Wformat-security compile warns (git-fixes).\n- tpm_tis_spi: Account for SPI header when allocating TPM SPI xfer (bsc#1225535)\n- tpm_tis_spi: Account for SPI header when allocating TPM SPI xfer buffer (git-fixes).\n- tracing: Add MODULE_DESCRIPTION() to preemptirq_delay_test (git-fixes).\n- tracing: hide unused ftrace_event_id_fops (git-fixes).\n- tty: n_gsm: fix missing receive state reset after mode switch (git-fixes).\n- tty: n_gsm: fix possible out-of-bounds in gsm0_receive() (git-fixes).\n- Update patches.suse/ring-buffer-Fix-a-race-between-readers-and-resize-checks.patch (bsc#1222893).\n- Update patches.suse/scsi-qedf-Don-t-process-stag-work-during-unload.patch (bsc#1214852)\n- Update patches.suse/scsi-qedf-Wait-for-stag-work-during-unload.patch (bsc#1214852)\n- usb: aqc111: stop lying about skb-\u003etruesize (git-fixes).\n- USB: core: Add hub_get() and hub_put() routines (git-fixes).\n- USB: core: Fix access violation during port device removal (git-fixes).\n- USB: core: Fix deadlock in port 'disable' sysfs attribute (git-fixes).\n- usb: dwc3: core: Prevent phy suspend during init (Git-fixes).\n- usb: gadget: u_audio: Clear uac pointer when freed (git-fixes).\n- usb: typec: tipd: fix event checking for tps6598x (git-fixes).\n- usb: typec: ucsi: displayport: Fix potential deadlock (git-fixes).\n- VMCI: Fix an error handling path in vmci_guest_probe_device() (git-fixes).\n- VMCI: Fix possible memcpy() run-time warning in vmci_datagram_invoke_guest_handler() (stable-fixes).\n- vmci: prevent speculation leaks by sanitizing event in event_deliver() (git-fixes).\n- watchdog: cpu5wdt.c: Fix use-after-free bug caused by cpu5wdt_trigger (git-fixes).\n- watchdog: ixp4xx: Make sure restart always works (git-fixes).\n- watchdog: rti_wdt: Set min_hw_heartbeat_ms to accommodate a safety margin (git-fixes).\n- wifi: ar5523: enable proper endpoint verification (git-fixes).\n- wifi: ath10k: Fix an error code problem in ath10k_dbg_sta_write_peer_debug_trigger() (git-fixes).\n- wifi: ath10k: poll service ready message before failing (git-fixes).\n- wifi: ath10k: populate board data for WCN3990 (git-fixes).\n- wifi: ath11k: do not force enable power save on non-running vdevs (git-fixes).\n- wifi: carl9170: add a proper sanity check for endpoints (git-fixes).\n- wifi: carl9170: re-fix fortified-memset warning (git-fixes).\n- wifi: cfg80211: fix rdev_dump_mpp() arguments order (stable-fixes).\n- wifi: mac80211: fix ieee80211_bss_*_flags kernel-doc (stable-fixes).\n- wifi: mwl8k: initialize cmd-\u003eaddr[] properly (git-fixes).\n- x86/boot: Ignore NMIs during very early boot (git-fixes).\n- x86/bugs: Cache the value of MSR_IA32_ARCH_CAPABILITIES (git-fixes).\n- x86/bugs: Change commas to semicolons in 'spectre_v2' sysfs file (git-fixes).\n- x86/bugs: Fix BHI documentation (git-fixes).\n- x86/bugs: Fix BHI handling of RRSBA (git-fixes).\n- x86/bugs: Fix BHI retpoline check (git-fixes).\n- x86/bugs: Fix return type of spectre_bhi_state() (git-fixes).\n- x86/bugs: Remove CONFIG_BHI_MITIGATION_AUTO and spectre_bhi=auto (git-fixes).\n- x86/bugs: Rename various 'ia32_cap' variables to 'x86_arch_cap_msr' (git-fixes).\n- x86/bugs: Replace CONFIG_SPECTRE_BHI_{ON,OFF} with CONFIG_MITIGATION_SPECTRE_BHI (git-fixes).\n- x86: Fix CPUIDLE_FLAG_IRQ_ENABLE leaking timer reprogram (git-fixes).\n- x86/kvm: Do not try to disable kvmclock if it was not enabled (git-fixes).\n- x86/lib: Fix overflow when counting digits (git-fixes).\n- x86/mce: Make sure to grab mce_sysfs_mutex in set_bank() (git-fixes).\n- x86/nmi: Drop unused declaration of proc_nmi_enabled() (git-fixes).\n- x86/retpoline: Do the necessary fixup to the Zen3/4 srso return thunk for !SRSO (git-fixes).\n- x86/sev: Check for MWAITX and MONITORX opcodes in the #VC handler (git-fixes).\n- x86/sme: Fix memory encryption setting if enabled by default and not overridden (git-fixes).\n- x86/tdx: Preserve shared bit on mprotect() (git-fixes).\n- xfs: add missing cmap-\u003ebr_state = XFS_EXT_NORM update (git-fixes).\n- xfs: fix exception caused by unexpected illegal bestcount in leaf dir (git-fixes).\n- xfs: Fix false ENOSPC when performing direct write on a delalloc extent in cow fork (git-fixes).\n- xfs: fix imprecise logic in xchk_btree_check_block_owner (git-fixes).\n- xfs: fix inode reservation space for removing transaction (git-fixes).\n- xfs: shrink failure needs to hold AGI buffer (git-fixes).\n","status":"published","published":"2024-06-12T11:33:43Z","modified":"2026-02-04T03:04:59.394977Z","updated_at":"2026-11-02T15:53:54.652421Z"},{"id":"SUSE-SU-2024:2010-1","title":"Security update for the Linux Kernel","description":"\nThe SUSE Linux Enterprise 15 SP3 RT kernel was updated to receive various security bugfixes.\n\nThe following security bugs were fixed:\n\n- CVE-2024-26921: Preserve kabi for sk_buff (bsc#1223138).\n- CVE-2021-47378: Destroy cm id before destroy qp to avoid use after free (bsc#1225201).\n- CVE-2021-47496: Fix flipped sign in tls_err_abort() calls (bsc#1225354)\n- CVE-2021-47402: Protect fl_walk() with rcu (bsc#1225301)\n- CVE-2022-48673: kABI workarounds for struct smc_link (bsc#1223934).\n- CVE-2023-52871: Handle a second device without data corruption (bsc#1225534)\n- CVE-2024-26828: Fixed underflow in parse_server_interfaces() (bsc#1223084).\n- CVE-2021-47497: Fixed shift-out-of-bound (UBSAN) with byte size cells (bsc#1225355).\n- CVE-2021-47500: Fixed trigger reference couting (bsc#1225360).\n- CVE-2024-27413: Fixed incorrect allocation size (bsc#1224438).\n- CVE-2021-47383: Fiedx out-of-bound vmalloc access in imageblit (bsc#1225208).\n- CVE-2021-47511: Fixed negative period/buffer sizes (bsc#1225411).\n- CVE-2023-52840: Fix use after free in rmi_unregister_function() (bsc#1224928).\n- CVE-2021-47261: Fix initializing CQ fragments buffer (bsc#1224954)\n- CVE-2021-47254: Fix use-after-free in gfs2_glock_shrink_scan (bsc#1224888).\n- CVE-2024-27398: Fixed use-after-free bugs caused by sco_sock_timeout (bsc#1224174).\n- CVE-2024-26929: Fixed double free of fcport (bsc#1223715).\n- CVE-2024-26930: Fixed double free of the ha-\u003evp_map pointer (bsc#1223626).\n- CVE-2023-52655: Check packet for fixup for true limit (bsc#1217169).\n- CVE-2023-4244: Fixed a use-after-free in the nf_tables component, which could be exploited to achieve local privilege escalation (bsc#1215420).\n- CVE-2023-1829: Fixed a use-after-free vulnerability in the control index filter (tcindex) (bsc#1210335).\n- CVE-2023-52686: Fix a null pointer in opal_event_init() (bsc#1065729).\n\nThe following non-security bugs were fixed:\n\n- af_unix: annote lockless accesses to unix_tot_inflight \u0026 gc_in_progress (bsc#1223384).\n- af_unix: Do not use atomic ops for unix_sk(sk)-\u003einflight (bsc#1223384).\n- af_unix: Replace BUG_ON() with WARN_ON_ONCE() (bsc#1223384).\n- btrfs: do not start relocation until in progress drops are done (bsc#1222251).\n- btrfs: do not start relocation until in progress drops are done (bsc#1222251).\n- cifs: add missing spinlock around tcon refcount (bsc#1213476).\n- cifs: avoid dup prefix path in dfs_get_automount_devname() (bsc#1213476).\n- cifs: avoid race conditions with parallel reconnects (bsc#1213476).\n- cifs: avoid re-lookups in dfs_cache_find() (bsc#1213476).\n- cifs: avoid use of global locks for high contention data (bsc#1213476).\n- cifs: check only tcon status on tcon related functions (bsc#1213476).\n- cifs: do all necessary checks for credits within or before locking (bsc#1213476).\n- cifs: do not block in dfs_cache_noreq_update_tgthint() (bsc#1213476).\n- cifs: do not refresh cached referrals from unactive mounts (bsc#1213476).\n- cifs: do not take exclusive lock for updating target hints (bsc#1213476).\n- cifs: fix confusing debug message (bsc#1213476).\n- cifs: fix missing unload_nls() in smb2_reconnect() (bsc#1213476).\n- cifs: fix potential deadlock in cache_refresh_path() (bsc#1213476).\n- cifs: fix refresh of cached referrals (bsc#1213476).\n- cifs: fix return of uninitialized rc in dfs_cache_update_tgthint() (bsc#1213476).\n- cifs: fix source pathname comparison of dfs supers (bsc#1213476).\n- cifs: fix status checks in cifs_tree_connect (bsc#1213476).\n- cifs: fix use-after-free bug in refresh_cache_worker() (bsc#1213476).\n- cifs: get rid of dns resolve worker (bsc#1213476).\n- cifs: get rid of mount options string parsing (bsc#1213476).\n- cifs: handle cache lookup errors different than -ENOENT (bsc#1213476).\n- cifs: ignore ipc reconnect failures during dfs failover (bsc#1213476).\n- cifs: match even the scope id for ipv6 addresses (bsc#1213476).\n- cifs: optimize reconnect of nested links (bsc#1213476).\n- cifs: prevent data race in smb2_reconnect() (bsc#1213476).\n- cifs: refresh root referrals (bsc#1213476).\n- cifs: remove duplicate code in __refresh_tcon() (bsc#1213476).\n- cifs: remove unused function (bsc#1213476).\n- cifs: remove unused smb3_fs_context::mount_options (bsc#1213476).\n- cifs: return DFS root session id in DebugData (bsc#1213476).\n- cifs: reuse cifs_match_ipaddr for comparison of dstaddr too (bsc#1213476).\n- cifs: set correct ipc status after initial tree connect (bsc#1213476).\n- cifs: set correct status of tcon ipc when reconnecting (bsc#1213476).\n- cifs: set correct tcon status after initial tree connect (bsc#1213476).\n- cifs: set DFS root session in cifs_get_smb_ses() (bsc#1213476).\n- cifs: set resolved ip in sockaddr (bsc#1213476).\n- cifs: share dfs connections and supers (bsc#1213476).\n- cifs: split out ses and tcon retrieval from mount_get_conns() (bsc#1213476).\n- cifs: use fs_context for automounts (bsc#1213476).\n- cifs: use origin fullpath for automounts (bsc#1213476).\n- cifs: use tcon allocation functions even for dummy tcon (bsc#1213476).\n- netfilter: nf_tables: defer gc run if previous batch is still pending (git-fixes).\n- netfilter: nf_tables: fix GC transaction races with netns and netlink event exit path (git-fixes).\n- netfilter: nf_tables: fix kdoc warnings after gc rework (git-fixes).\n- netfilter: nf_tables: fix memleak when more than 255 elements expired (git-fixes).\n- netfilter: nf_tables: GC transaction race with abort path (git-fixes).\n- netfilter: nf_tables: GC transaction race with netns dismantle (git-fixes).\n- netfilter: nf_tables: mark newset as dead on transaction abort (git-fixes).\n- netfilter: nf_tables: mark set as dead when unbinding anonymous set with timeout (git-fixes).\n- netfilter: nf_tables: nft_set_rbtree: fix spurious insertion failure (git-fixes).\n- netfilter: nf_tables: release mutex after nft_gc_seq_end from abort path (git-fixes).\n- netfilter: nf_tables: skip dead set elements in netlink dump (git-fixes).\n- netfilter: nf_tables: use correct lock to protect gc_list (git-fixes).\n- netfilter: nft_set_hash: try later when GC hits EAGAIN on iteration (git-fixes).\n- netfilter: nft_set_rbtree: Add missing expired checks (git-fixes).\n- netfilter: nft_set_rbtree: bogus lookup/get on consecutive elements in named sets (git-fixes).\n- netfilter: nft_set_rbtree: Detect partial overlap with start endpoint match (git-fixes).\n- netfilter: nft_set_rbtree: Detect partial overlaps on insertion (git-fixes).\n- netfilter: nft_set_rbtree: Do not account for expired elements on insertion (git-fixes).\n- netfilter: nft_set_rbtree: Drop spurious condition for overlap detection on insertion (git-fixes).\n- netfilter: nft_set_rbtree: fix null deref on element insertion (git-fixes).\n- netfilter: nft_set_rbtree: fix overlap expiration walk (git-fixes).\n- netfilter: nft_set_rbtree: Handle outcomes of tree rotations in overlap detection (git-fixes).\n- netfilter: nft_set_rbtree: Introduce and use nft_rbtree_interval_start() (git-fixes).\n- netfilter: nft_set_rbtree: overlap detection with element re-addition after deletion (git-fixes).\n- netfilter: nft_set_rbtree: skip elements in transaction from garbage collection (git-fixes).\n- netfilter: nft_set_rbtree: skip end interval element from gc (git-fixes).\n- netfilter: nft_set_rbtree: skip sync GC for new elements in this transaction (git-fixes).\n- netfilter: nft_set_rbtree: Switch to node list walk for overlap detection (git-fixes).\n- netfilter: nft_set_rbtree: use read spinlock to avoid datapath contention (git-fixes).\n- NFC: nxp: add NXP1002 (bsc#1185589).\n- PCI: rpaphp: Add MODULE_DESCRIPTION (bsc#1176869 ltc#188243).\n- smb: client: fix dfs link mount against w2k8 (git-fixes).\n- smb: client: fix null auth (bsc#1213476).\n- smb: client: set correct id, uid and cruid for multiuser automounts (git-fixes).\n- x86/xen: Drop USERGS_SYSRET64 paravirt call (git-fixes).\n","status":"published","published":"2024-06-12T16:39:35Z","modified":"2026-02-04T03:31:05.409372Z","updated_at":"2026-11-02T15:53:54.652421Z"},{"id":"SUSE-SU-2024:2011-1","title":"Security update for the Linux Kernel","description":"\n\nThe SUSE Linux Enterprise 15 SP4 RT kernel was updated to receive various security bugfixes.\n\n\nThe following security bugs were fixed:\n\n- CVE-2024-0639: Fixed a denial-of-service vulnerability due to a deadlock found in sctp_auto_asconf_init in net/sctp/socket.c (bsc#1218917).\n- CVE-2024-26828: Fixed underflow in parse_server_interfaces() (bsc#1223084).\n- CVE-2024-26840: Fixed a memory leak in cachefiles_add_cache() (bsc#1222976).\n- CVE-2024-26852: Fixed use-after-free in ip6_route_mpath_notify() (bsc#1223057).\n- CVE-2024-26862: Fixed packet annotate data-races around ignore_outgoing (bsc#1223111).\n- CVE-2024-26921: Preserve kabi for sk_buff (bsc#1223138).\n- CVE-2024-26925: Release mutex after nft_gc_seq_end from abort path (bsc#1223390).\n- CVE-2024-26928: Fixed potential UAF in cifs_debug_files_proc_show() (bsc#1223532).\n- CVE-2024-26929: Fixed double free of fcport (bsc#1223715).\n- CVE-2024-26930: Fixed double free of the ha-\u003evp_map pointer (bsc#1223626).\n- CVE-2024-27398: Fixed use-after-free bugs caused by sco_sock_timeout (bsc#1224174).\n- CVE-2024-27413: Fixed incorrect allocation size (bsc#1224438).\n- CVE-2024-35817: Set gtt bound flag in amdgpu_ttm_gart_bind (bsc#1224736).\n- CVE-2024-35863: Fixed potential UAF in is_valid_oplock_break() (bsc#1224763).\n- CVE-2024-35867: Fixed potential UAF in cifs_stats_proc_show() (bsc#1224664).\n- CVE-2024-35868: Fixed potential UAF in cifs_stats_proc_write() (bsc#1224678).\n- CVE-2024-35904: Fixed dereference of garbage after mount failure (bsc#1224494).\n- CVE-2024-35905: Fixed int overflow for stack access size  (bsc#1224488).\n- CVE-2024-36926: Fixed LPAR panics during boot up with a frozen PE (bsc#1222011).\n\nThe following non-security bugs were fixed:\n\n- af_unix: annote lockless accesses to unix_tot_inflight \u0026 gc_in_progress (bsc#1223384).\n- af_unix: Do not use atomic ops for unix_sk(sk)-\u003einflight (bsc#1223384).\n- af_unix: Replace BUG_ON() with WARN_ON_ONCE() (bsc#1223384).\n- filemap: remove use of wait bookmarks (bsc#1224085).\n- idpf: extend tx watchdog timeout (bsc#1224137).\n- ipvs: Fix checksumming on GSO of SCTP packets (bsc#1221958)\n- powerpc: Avoid nmi_enter/nmi_exit in real mode interrupt (bsc#1221645 ltc#205739 bsc#1223191).\n- powerpc/kasan: Do not instrument non-maskable or raw interrupts (bsc#1223191).\n- powerpc/powernv: Add a null pointer check in opal_event_init() (bsc#1065729).\n- powerpc/powernv: Add a null pointer check to scom_debug_init_one() (bsc#1194869).\n- powerpc/pseries/iommu: IOMMU table is not initialized for kdump over SR-IOV (bsc#1220492 ltc#205270).\n- powerpc/pseries/vio: Do not return ENODEV if node or compatible missing (bsc#1220783).\n- powerpc: Refactor verification of MSR_RI (bsc#1223191).\n- supported.conf: support tcp_dctcp module (jsc#PED-8111)\n","status":"published","published":"2024-06-12T16:39:51Z","modified":"2026-02-04T02:22:35.130887Z","updated_at":"2026-11-02T15:53:54.652421Z"},{"id":"SUSE-SU-2024:2019-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-35924: Limit read size on v1.2 (bsc#1224657).\n- CVE-2024-26921: Preserve kabi for sk_buff (bsc#1223138).\n- CVE-2024-35976: Validate user input for XDP_{UMEM|COMPLETION}_FILL_RING  (bsc#1224575).\n- CVE-2024-36938: Fixed NULL pointer dereference in  sk_psock_skb_ingress_enqueue (bsc#1225761).\n- CVE-2024-35905: Fixed int overflow for stack access size  (bsc#1224488).\n- CVE-2023-52795: Fixed use after free in vhost_vdpa_probe()  (bsc#1225085).\n- CVE-2024-35998: Fixed lock ordering potential deadlock in  cifs_sync_mid_result (bsc#1224549).\n- CVE-2023-52757: Fixed potential deadlock when releasing mids  (bsc#1225548).\n- CVE-2021-47548: Fixed a possible array out-of=bounds (bsc#1225506)\n- CVE-2024-26828: Fixed underflow in parse_server_interfaces() (bsc#1223084).\n- CVE-2024-26822: Set correct id, uid and cruid for multiuser  automounts (bsc#1223011).\n- CVE-2024-35999: Fixed missing lock when picking channel (bsc#1224550).\n- CVE-2024-35861: Fixed potential UAF in  cifs_signal_cifsd_for_reconnect() (bsc#1224766).\n- CVE-2024-35862: Fixed potential UAF in smb2_is_network_name_deleted()  (bsc#1224764).\n- CVE-2024-35863: Fixed potential UAF in is_valid_oplock_break() (bsc#1224763).\n- CVE-2024-35865: Fixed potential UAF in smb2_is_valid_oplock_break()  (bsc#1224668).\n- CVE-2024-35864: Fixed potential UAF in smb2_is_valid_lease_break()  (bsc#1224765).\n- CVE-2024-35867: Fixed potential UAF in cifs_stats_proc_show() (bsc#1224664).\n- CVE-2024-35868: Fixed potential UAF in cifs_stats_proc_write() (bsc#1224678).\n- CVE-2024-35866: Fixed potential UAF in cifs_dump_full_key()  (bsc#1224667).\n- CVE-2024-26928: Fixed potential UAF in cifs_debug_files_proc_show() (bsc#1223532).\n- CVE-2024-35869: Guarantee refcounted children from parent session  (bsc#1224679).\n- CVE-2024-35870: Fixed UAF in smb2_reconnect_server() (bsc#1224672).\n- CVE-2024-26692: Fixed regression in writes when non-standard maximum write  size negotiated (bsc#1222464).\n- CVE-2024-26925: Release mutex after nft_gc_seq_end from abort path (bsc#1223390).\n- CVE-2023-42755: Check user supplied offsets (bsc#1215702).\n- CVE-2024-35964: Fixed not validating setsockopt user input  (bsc#1224581).\n- CVE-2023-52698: Fixed memory leak in netlbl_calipso_add_pass()  (CVE-2023-52698 bsc#1224621)\n- CVE-2023-52664: Eliminate double free in error handling logic  (bsc#1224747).\n- CVE-2023-52807: Fixed out-of-bounds access may occur when coalesce  info is read via debugfs (bsc#1225097).\n- CVE-2024-27431: Fixed Zero-initialise xdp_rxq_info struct before running  XDP program (bsc#1224718).\n- CVE-2024-35860: struct bpf_link and bpf_link_ops kABI workaround  (bsc#1224531).\n- CVE-2023-52671: Fixed hang/underflow when transitioning to ODM4:1 (bsc#1224729).\n- CVE-2024-35799: Prevent crash when disable stream (bsc#1224740).\n- CVE-2024-35951: Fixed the error path in panfrost_mmu_map_fault_addr() (bsc#1224701).\n- CVE-2024-27413: Fixed incorrect allocation size (bsc#1224438).\n- CVE-2024-35817: Set gtt bound flag in amdgpu_ttm_gart_bind (bsc#1224736).\n- CVE-2024-35877: Fixed VM_PAT handling in COW mappings (bsc#1224525).\n- CVE-2024-35969: Fixed race condition between ipv6_get_ifaddr and ipv6_del_addr  (bsc#1224580).\n- CVE-2023-52746: Prevent potential spectre v1 gadget in xfrm_xlate32_attr()  (bsc#1225114)\n- CVE-2024-35872: Fixed GUP-fast succeeding on secretmem folios  (bsc#1224530).\n- CVE-2024-35852: Fixed memory leak when canceling rehash  work (bsc#1224502).\n- CVE-2024-36006: Fixed incorrect list API usage  (bsc#1224541).\n- CVE-2024-36007: Fixed warning during rehash  (bsc#1224543).\n- CVE-2024-35885: Stop interface during shutdown (bsc#1224519).\n- CVE-2024-35907: Call request_irq() after NAPI initialized  (bsc#1224492).\n- CVE-2023-52796: Add ipvlan_route_v6_outbound() helper (bsc#1224930).\n- CVE-2024-35939: Fixed leak pages on dma_set_decrypted() failure (bsc#1224535).\n- CVE-2024-35875: Require seeding RNG with RDRAND on CoCo systems (bsc#1224665).\n- CVE-2024-35804: Mark target gfn of emulated atomic instruction as  dirty (bsc#1224638).\n- CVE-2024-35791: Flush pages under kvm-\u003elock to fix UAF in  svm_register_enc_region() (bsc#1224725).\n- CVE-2024-35904: Fixed dereference of garbage after mount failure (bsc#1224494).\n- CVE-2023-52660: Fiedx IRQ handling due to shared interrupts  (bsc#1224443).\n- CVE-2024-35879: kABI workaround for drivers/of/dynamic.c (bsc#1224524).\n- CVE-2024-35943: Fixed a null pointer dereference in omap_prm_domain_init (bsc#1224649).\n- CVE-2024-35878: Prevent NULL pointer dereference in vsnprintf()  (bsc#1224671).\n- CVE-2023-52860: Fixed null pointer dereference in hisi_hns3 (bsc#1224936).\n- CVE-2024-35959: Fixed mlx5e_priv_init() cleanup flow (bsc#1224666).\n- CVE-2024-35854: Fixed possible use-after-free during  rehash (bsc#1224636).\n- CVE-2024-35973: Fixed header validation in geneve[6]_xmit_skb  (bsc#1224586).\n- CVE-2024-27417: Fixed potential 'struct net' leak in inet6_rtm_getaddr()  (bsc#1224721)\n- CVE-2023-52656: Dropped any code related to SCM_RIGHTS (bsc#1224187).\n- CVE-2023-52674: Add clamp() in scarlett2_mixer_ctl_put()  (bsc#1224727).\n- CVE-2023-52680: Fixed missing error checks to *_ctl_get()  (bsc#1224608).\n- CVE-2023-52692: Fixed missing error check to  scarlett2_usb_set_config() (bsc#1224628).\n- CVE-2024-35944: Fixed memcpy() run-time warning in dg_dispatch_as_host()  (bsc#1224648).\n- CVE-2024-26742: Fixed disable_managed_interrupts (git-fixes  bsc#1222608).\n- CVE-2024-27398: Fixed use-after-free bugs caused by sco_sock_timeout (bsc#1224174).\n- CVE-2023-52586: Fixed  mutex lock in control vblank irq (bsc#1221081).\n- CVE-2024-27395: Fixed Use-After-Free in ovs_ct_exit (bsc#1224098).\n- CVE-2024-27396: Fixed Use-After-Free in gtp_dellink (bsc#1224096).\n- CVE-2024-26715: Fixed NULL pointer dereference in  dwc3_gadget_suspend (bsc#1222561).\n- CVE-2024-26919: Fixed debugfs directory leak (bsc#1223847).\n- CVE-2024-27401: Fixed user_length taken into account when  fetching packet contents (bsc#1224181).\n- CVE-2024-26900: Fixed kmemleak of rdev-\u003eserial (bsc#1223046).\n- CVE-2024-26775: Fixed potential deadlock at set_capacity (bsc#1222627).\n- CVE-2024-26958: Fixed UAF in direct writes (bsc#1223653).\n- CVE-2024-26643: Fixed mark set as dead when unbinding anonymous  set with timeout (bsc#1221829).\n- CVE-2023-52618: Fixed string overflow in block/rnbd-srv (bsc#1221615).\n- CVE-2022-48689: Fixed data-race in lru_add_fn (bsc#1223959)\n- CVE-2022-48691: Fixed memory leak in netfilter (bsc#1223961)\n- CVE-2023-1829: Fixed a use-after-free vulnerability in the control index filter (tcindex) (bsc#1210335).\n\nThe following non-security bugs were fixed:\n\n- 9p: explicitly deny setlease attempts (git-fixes).\n- ACPI: bus: Indicate support for _TFP thru _OSC (git-fixes).\n- ACPI: disable -Wstringop-truncation (git-fixes).\n- ACPI: Fix Generic Initiator Affinity _OSC bit (git-fixes).\n- ACPI: LPSS: Advertise number of chip selects via property (git-fixes).\n- admin-guide/hw-vuln/core-scheduling: fix return type of PR_SCHED_CORE_GET (git-fixes).\n- af_unix: annote lockless accesses to unix_tot_inflight \u0026 gc_in_progress (bsc#1223384).\n- af_unix: Do not use atomic ops for unix_sk(sk)-\u003einflight (bsc#1223384).\n- af_unix: Replace BUG_ON() with WARN_ON_ONCE() (bsc#1223384).\n- ALSA: core: Fix NULL module pointer assignment at card init (git-fixes).\n- ALSA: hda/cs_dsp_ctl: Use private_free for control cleanup (git-fixes).\n- ALSA: line6: Zero-initialize message buffers (stable-fixes).\n- ARM: 9381/1: kasan: clear stale stack poison (git-fixes).\n- ASoC: Intel: avs: Fix ASRC module initialization (git-fixes).\n- ASoC: Intel: avs: Fix potential integer overflow (git-fixes).\n- ASoC: Intel: avs: ssm4567: Do not ignore route checks (git-fixes).\n- ASoC: Intel: Disable route checks for Skylake boards (git-fixes).\n- ASoC: kirkwood: Fix potential NULL dereference (git-fixes).\n- ASoC: mediatek: mt8192: fix register configuration for tdm (git-fixes).\n- ASoC: meson: axg-fifo: use FIELD helpers (stable-fixes).\n- ASoC: meson: axg-fifo: use threaded irq to check periods (git-fixes).\n- ASoC: tas2552: Add TX path for capturing AUDIO-OUT data (git-fixes).\n- ASoC: tracing: Export SND_SOC_DAPM_DIR_OUT to its value (git-fixes).\n- ata: pata_legacy: make legacy_exit() work again (git-fixes).\n- ata: sata_gemini: Check clk_enable() result (stable-fixes).\n- autofs: use wake_up() instead of wake_up_interruptible(() (bsc#1224166).\n- Bluetooth: Fix use-after-free bugs caused by sco_sock_timeout (git-fixes).\n- Bluetooth: hci_sync: Avoid use-after-free in dbg for hci_add_adv_monitor() (git-fixes).\n- Bluetooth: hci_sync: Do not double print name in add/remove adv_monitor (bsc#1216358).\n- Bluetooth: l2cap: fix null-ptr-deref in l2cap_chan_timeout (git-fixes).\n- Bluetooth: msft: fix slab-use-after-free in msft_do_close() (git-fixes).\n- Bluetooth: qca: add missing firmware sanity checks (git-fixes).\n- Bluetooth: qca: Fix error code in qca_read_fw_build_info() (git-fixes).\n- Bluetooth: qca: fix firmware check error path (git-fixes).\n- Bluetooth: qca: fix info leak when fetching fw build id (git-fixes).\n- Bluetooth: qca: fix NVM configuration parsing (git-fixes).\n- bnxt_re: avoid shift undefined behavior in bnxt_qplib_alloc_init_hwq (git-fixes)\n- bpf: decouple prune and jump points (bsc#1225756).\n- bpf: fix precision backtracking instruction iteration (bsc#1225756).\n- bpf: Fix precision tracking for BPF_ALU | BPF_TO_BE | BPF_END (git-fixes).\n- bpf: handle ldimm64 properly in check_cfg() (bsc#1225756).\n- bpf: mostly decouple jump history management from is_state_visited() (bsc#1225756).\n- bpf: remove unnecessary prune and jump points (bsc#1225756).\n- btrfs: add error messages to all unrecognized mount options (git-fixes)\n- btrfs: add missing mutex_unlock in btrfs_relocate_sys_chunks() (git-fixes)\n- btrfs: export: handle invalid inode or root reference in btrfs_get_parent() (git-fixes)\n- btrfs: extend locking to all space_info members accesses (git-fixes)\n- btrfs: fix btrfs_submit_compressed_write cgroup attribution (git-fixes)\n- btrfs: fix fallocate to use file_modified to update permissions consistently (git-fixes)\n- btrfs: fix information leak in btrfs_ioctl_logical_to_ino() (git-fixes)\n- btrfs: fix missing blkdev_put() call in btrfs_scan_one_device() (git-fixes)\n- btrfs: fix off-by-one chunk length calculation at contains_pending_extent() (git-fixes)\n- btrfs: fix qgroup reserve overflow the qgroup limit (git-fixes)\n- btrfs: fix silent failure when deleting root reference (git-fixes)\n- btrfs: fix use-after-free after failure to create a snapshot (git-fixes)\n- btrfs: free exchange changeset on failures (git-fixes)\n- btrfs: handle chunk tree lookup error in btrfs_relocate_sys_chunks() (git-fixes)\n- btrfs: make search_csum_tree return 0 if we get -EFBIG (git-fixes)\n- btrfs: prevent copying too big compressed lzo segment (git-fixes)\n- btrfs: remove BUG_ON(!eie) in find_parent_nodes (git-fixes)\n- btrfs: remove BUG_ON() in find_parent_nodes() (git-fixes)\n- btrfs: repair super block num_devices automatically (git-fixes)\n- btrfs: replace the BUG_ON in btrfs_del_root_ref with proper error handling (git-fixes)\n- btrfs: send: ensure send_fd is writable (git-fixes)\n- btrfs: send: handle path ref underflow in header iterate_inode_ref() (git-fixes)\n- btrfs: send: in case of IO error log it (git-fixes)\n- btrfs: send: return EOPNOTSUPP on unknown flags (git-fixes)\n- btrfs: tree-checker: check item_size for dev_item (git-fixes)\n- btrfs: tree-checker: check item_size for inode_item (git-fixes)\n- cifs: account for primary channel in the interface list (bsc#1224020).\n- cifs: cifs_chan_is_iface_active should be called with chan_lock held (bsc#1224020).\n- cifs: distribute channels across interfaces based on speed (bsc#1224020).\n- cifs: do not pass cifs_sb when trying to add channels (bsc#1224020).\n- cifs: failure to add channel on iface should bump up weight (git-fixes, bsc#1224020).\n- cifs: fix charset issue in reconnection (bsc#1224020).\n- cifs: fix leak of iface for primary channel (git-fixes, bsc#1224020).\n- cifs: handle cases where a channel is closed (bsc#1224020).\n- cifs: handle cases where multiple sessions share connection (bsc#1224020).\n- cifs: reconnect work should have reference on server struct (bsc#1224020).\n- clk: Do not hold prepare_lock when calling kref_put() (stable-fixes).\n- clk: qcom: mmcc-msm8998: fix venus clock issue (git-fixes).\n- counter: stm32-lptimer-cnt: Provide defines for clock polarities (git-fixes).\n- counter: stm32-timer-cnt: Provide defines for slave mode selection (git-fixes).\n- cppc_cpufreq: Fix possible null pointer dereference (git-fixes).\n- cpu/hotplug: Remove the 'cpu' member of cpuhp_cpu_state (git-fixes).\n- cpumask: Add for_each_cpu_from() (bsc#1225053).\n- crypto: bcm - Fix pointer arithmetic (git-fixes).\n- crypto: ccp - drop platform ifdef checks (git-fixes).\n- crypto: ecdsa - Fix module auto-load on add-key (git-fixes).\n- crypto: x86/nh-avx2 - add missing vzeroupper (git-fixes).\n- crypto: x86/sha256-avx2 - add missing vzeroupper (git-fixes).\n- crypto: x86/sha512-avx2 - add missing vzeroupper (git-fixes).\n- dm-multipath: dont't attempt SG_IO on non-SCSI-disks (bsc#1223575).\n- dm/amd/pm: Fix problems with reboot/shutdown for some SMU 13.0.4/13.0.11 users (git-fixes).\n- dmaengine: axi-dmac: fix possible race in remove() (git-fixes).\n- dmaengine: idma64: Add check for dma_set_max_seg_size (git-fixes).\n- docs: kernel_include.py: Cope with docutils 0.21 (stable-fixes).\n- drivers/nvme: Add quirks for device 126f:2262 (git-fixes).\n- drm: bridge: cdns-mhdp8546: Fix possible null pointer dereference (git-fixes).\n- drm: vc4: Fix possible null pointer dereference (git-fixes).\n- drm/amd: Flush GFXOFF requests in prepare stage (git-fixes).\n- drm/amd/display: Atom Integrated System Info v2_2 for DCN35 (stable-fixes).\n- drm/amd/display: Fix division by zero in setup_dsc_config (stable-fixes).\n- drm/amd/display: Fix potential index out of bounds in color transformation function (git-fixes).\n- drm/amd/display: Handle Y carry-over in VCP X.Y calculation (stable-fixes).\n- drm/amdgpu: Refine IB schedule error logging (stable-fixes).\n- drm/amdkfd: do not allow mapping the MMIO HDP page with large pages (git-fixes).\n- drm/arm/malidp: fix a possible null pointer dereference (git-fixes).\n- drm/bridge: anx7625: Do not log an error when DSI host can't be found (git-fixes).\n- drm/bridge: dpc3433: Do not log an error when DSI host can't be found (git-fixes).\n- drm/bridge: icn6211: Do not log an error when DSI host can't be found (git-fixes).\n- drm/bridge: lt8912b: Do not log an error when DSI host can't be found (git-fixes).\n- drm/bridge: lt9611: Do not log an error when DSI host can't be found (git-fixes).\n- drm/bridge: tc358775: Do not log an error when DSI host can't be found (git-fixes).\n- drm/bridge: tc358775: fix support for jeida-18 and jeida-24 (git-fixes).\n- drm/connector: Add \\n to message about demoting connector force-probes (git-fixes).\n- drm/i915/bios: Fix parsing backlight BDB data (git-fixes).\n- drm/lcdif: Do not disable clocks on already suspended hardware (git-fixes).\n- drm/mediatek: Add 0 size check to mtk_drm_gem_obj (git-fixes).\n- drm/meson: dw-hdmi: add bandgap setting for g12 (git-fixes).\n- drm/meson: dw-hdmi: power up phy on device init (git-fixes).\n- drm/meson: vclk: fix calculation of 59.94 fractional rates (git-fixes).\n- drm/msm/dp: allow voltage swing / pre emphasis of 3 (git-fixes).\n- drm/msm/dpu: Always flush the slave INTF on the CTL (git-fixes).\n- drm/msm/dsi: Print dual-DSI-adjusted pclk instead of original mode pclk (git-fixes).\n- drm/nouveau/dp: Do not probe eDP ports twice harder (stable-fixes).\n- drm/panel: atna33xc20: Fix unbalanced regulator in the case HPD does not assert (git-fixes).\n- drm/panel: novatek-nt35950: Do not log an error when DSI host can't be found (git-fixes).\n- drm/panel: simple: Add missing Innolux G121X1-L03 format, flags, connector (git-fixes).\n- dt-bindings: clock: qcom: Add missing UFS QREF clocks (git-fixes)\n- dyndbg: fix old BUG_ON in \u003econtrol parser (stable-fixes).\n- efi: libstub: only free priv.runtime_map when allocated (git-fixes).\n- extcon: max8997: select IRQ_DOMAIN instead of depending on it (git-fixes).\n- fail_function: fix wrong use of fei_attr_remove().\n- fbdev: savage: Handle err return when savagefb_check_var failed (git-fixes).\n- fbdev: shmobile: fix snprintf truncation (git-fixes).\n- fbdev: sisfb: hide unused variables (git-fixes).\n- firewire: ohci: mask bus reset interrupts between ISR and bottom half (stable-fixes).\n- firmware: dmi-id: add a release callback function (git-fixes).\n- firmware: raspberrypi: Use correct device for DMA mappings (git-fixes).\n- fs/9p: drop inodes immediately on non-.L too (git-fixes).\n- fs/9p: only translate RWX permissions for plain 9P2000 (git-fixes).\n- fs/9p: translate O_TRUNC into OTRUNC (git-fixes).\n- gpio: crystalcove: Use -ENOTSUPP consistently (stable-fixes).\n- gpio: wcove: Use -ENOTSUPP consistently (stable-fixes).\n- gpu: host1x: Do not setup DMA for virtual devices (stable-fixes).\n- HID: intel-ish-hid: ipc: Add check for pci_alloc_irq_vectors (git-fixes).\n- hwmon: (corsair-cpro) Protect ccp-\u003ewait_input_report with a spinlock (git-fixes).\n- hwmon: (corsair-cpro) Use a separate buffer for sending commands (git-fixes).\n- hwmon: (corsair-cpro) Use complete_all() instead of complete() in ccp_raw_event() (git-fixes).\n- hwmon: (lm70) fix links in doc and comments (git-fixes).\n- hwmon: (pmbus/ucd9000) Increase delay from 250 to 500us (git-fixes).\n- i3c: master: svc: change ENXIO to EAGAIN when IBI occurs during start frame (git-fixes).\n- i3c: master: svc: fix invalidate IBI type and miss call client IBI handler (git-fixes).\n- IB/mlx5: Use __iowrite64_copy() for write combining stores (git-fixes)\n- idpf: extend tx watchdog timeout (bsc#1224137).\n- iio: core: Leave private pointer NULL when no private data supplied (git-fixes).\n- iio: pressure: dps310: support negative temperature values (git-fixes).\n- Input: cyapa - add missing input core locking to suspend/resume functions (git-fixes).\n- Input: ims-pcu - fix printf string overflow (git-fixes).\n- Input: pm8xxx-vibrator - correct VIB_MAX_LEVELS calculation (git-fixes).\n- io_uring/unix: drop usage of io_uring socket (git-fixes).\n- iomap: Fix inline extent handling in iomap_readpage (git-fixes)\n- iomap: iomap: fix memory corruption when recording errors during writeback (git-fixes)\n- iomap: Support partial direct I/O on user copy failures (git-fixes)\n- iommu/dma: Force swiotlb_max_mapping_size on an untrusted device (bsc#1224331)\n- jffs2: prevent xattr node from overflowing the eraseblock (git-fixes).\n- kABI: bpf: struct bpf_insn_aux_data kABI workaround (bsc#1225756).\n- kcm: do not sense pfmemalloc status in kcm_sendpage() (git-fixes bsc#1223959)\n- KEYS: trusted: Do not use WARN when encode fails (git-fixes).\n- KEYS: trusted: Fix memory leak in tpm2_key_encode() (git-fixes).\n- KVM: s390: Check kvm pointer when testing KVM_CAP_S390_HPAGE_1M (git-fixes bsc#1224794).\n- KVM: x86: Delete duplicate documentation for KVM_X86_SET_MSR_FILTER (git-fixes).\n- leds: pwm: Disable PWM when going to suspend (git-fixes).\n- libsubcmd: Fix parse-options memory leak (git-fixes).\n- locking/atomic: Make test_and_*_bit() ordered on failure (git-fixes).\n- media: atomisp: ssh_css: Fix a null-pointer dereference in load_video_binaries (git-fixes).\n- media: dt-bindings: ovti,ov2680: Fix the power supply names (git-fixes).\n- media: mc: mark the media devnode as registered from the, start (git-fixes).\n- media: ngene: Add dvb_ca_en50221_init return value check (git-fixes).\n- media: stk1160: fix bounds checking in stk1160_copy_video() (git-fixes).\n- mei: me: add lunar lake point M DID (stable-fixes).\n- mfd: intel-lpss: Revert 'Add missing check for platform_get_resource' (git-fixes).\n- mfd: ti_am335x_tscadc: Support the correctly spelled DT property (git-fixes).\n- mfd: tqmx86: Specify IO port register range more precisely (git-fixes).\n- mlxbf_gige: Enable the GigE port in mlxbf_gige_open (git-fixes).\n- mlxbf_gige: Fix intermittent no ip issue (git-fixes).\n- mlxbf_gige: stop PHY during open() error paths (git-fixes).\n- mmc: sdhci_am654: Add tuning algorithm for delay chain (git-fixes).\n- mmc: sdhci_am654: Write ITAPDLY for DDR52 timing (git-fixes).\n- mtd: core: Report error if first mtd_otp_size() call fails in mtd_otp_nvmem_add() (git-fixes).\n- mtd: rawnand: hynix: fixed typo (git-fixes).\n- net: do not sense pfmemalloc status in skb_append_pagefrags() (git-fixes bsc#1223959)\n- net: introduce __skb_fill_page_desc_noacc (git-fixes bsc#1223959)\n- net: nfc: remove inappropriate attrs check (stable-fixes).\n- net: qualcomm: rmnet: fix global oob in rmnet_policy (git-fixes).\n- net: usb: ax88179_178a: fix link status when link is set to down/up (git-fixes).\n- net: usb: smsc95xx: stop lying about skb-\u003etruesize (git-fixes).\n- net: usb: sr9700: stop lying about skb-\u003etruesize (git-fixes).\n- net:usb:qmi_wwan: support Rolling modules (stable-fixes).\n- netfilter: nf_tables: bail out early if hardware offload is not supported (git-fixes bsc#1223961)\n- nfc: nci: Fix handling of zero-length payload packets in nci_rx_work() (git-fixes).\n- nfc: nci: Fix uninit-value in nci_rx_work (git-fixes).\n- nilfs2: fix out-of-range warning (git-fixes).\n- nilfs2: fix unexpected freezing of nilfs_segctor_sync() (git-fixes).\n- nilfs2: fix use-after-free of timer for log writer thread (git-fixes).\n- nilfs2: make superblock data array index computation sparse friendly (git-fixes).\n- nvme-multipath: fix io accounting on failover (git-fixes).\n- nvme: ensure disabling pairs with unquiesce (bsc#1224534).\n- nvme: fix miss command type check (git-fixes).\n- nvme: fix multipath batched completion accounting (git-fixes).\n- nvmet: fix ns enable/disable possible hang (git-fixes).\n- PCI: dwc: Detect iATU settings after getting 'addr_space' resource (git-fixes).\n- PCI: dwc: ep: Fix DBI access failure for drivers requiring refclk from host (git-fixes).\n- PCI: dwc: Use the bitmap API to allocate bitmaps (git-fixes).\n- PCI: rockchip-ep: Remove wrong mask on subsys_vendor_id (git-fixes).\n- PCI: tegra194: Fix probe path for Endpoint mode (git-fixes).\n- PCI/EDR: Align EDR_PORT_DPC_ENABLE_DSM with PCI Firmware r3.3 (git-fixes).\n- PCI/EDR: Align EDR_PORT_LOCATE_DSM with PCI Firmware r3.3 (git-fixes).\n- pinctrl: armada-37xx: remove an unused variable (git-fixes).\n- pinctrl: core: delete incorrect free in pinctrl_enable() (git-fixes).\n- pinctrl: core: handle radix_tree_insert() errors in pinctrl_register_one_pin() (stable-fixes).\n- pinctrl: devicetree: fix refcount leak in pinctrl_dt_to_map() (git-fixes).\n- pinctrl: pinctrl-aspeed-g6: Fix register offset for pinconf of GPIOR-T (git-fixes).\n- pinctrl/meson: fix typo in PDM's pin name (git-fixes).\n- platform/x86: xiaomi-wmi: Fix race condition when reporting key events (git-fixes).\n- platform/x86/intel-uncore-freq: Do not present root domain on error (git-fixes).\n- power: rt9455: hide unused rt9455_boost_voltage_values (git-fixes).\n- powerpc/eeh: Permanently disable the removed device (bsc#1223991 ltc#205740).\n- powerpc/eeh: Small refactor of eeh_handle_normal_event() (bsc#1223991 ltc#205740).\n- powerpc/eeh: Use a goto for recovery failures (bsc#1223991 ltc#205740).\n- powerpc/powernv: Add a null pointer check in opal_event_init() (bsc#1065729).\n- powerpc/pseries/lparcfg: drop error message from guest name lookup (bsc#1187716 ltc#193451 git-fixes).\n- powerpc/pseries/vio: Do not return ENODEV if node or compatible missing (bsc#1220783).\n- powerpc/uaccess: Fix build errors seen with GCC 13/14 (bsc#1194869).\n- powerpc/uaccess: Use YZ asm constraint for ld (bsc#1194869).\n- ppdev: Add an error check in register_device (git-fixes).\n- printk: Update @console_may_schedule in console_trylock_spinning() (bsc#1225616).\n- qibfs: fix dentry leak (git-fixes)\n- RDMA/hns: Add max_ah and cq moderation capacities in query_device() (git-fixes)\n- RDMA/hns: Fix deadlock on SRQ async events. (git-fixes)\n- RDMA/hns: Fix GMV table pagesize (git-fixes)\n- RDMA/hns: Fix return value in hns_roce_map_mr_sg (git-fixes)\n- RDMA/hns: Fix UAF for cq async event (git-fixes)\n- RDMA/hns: Modify the print level of CQE error (git-fixes)\n- RDMA/hns: Use complete parentheses in macros (git-fixes)\n- RDMA/IPoIB: Fix format truncation compilation errors (git-fixes)\n- RDMA/mlx5: Adding remote atomic access flag to updatable flags (git-fixes)\n- RDMA/mlx5: Fix port number for counter query in multi-port configuration (git-fixes)\n- RDMA/rxe: Add ibdev_dbg macros for rxe (git-fixes)\n- RDMA/rxe: Fix incorrect rxe_put in error path (git-fixes)\n- RDMA/rxe: Fix seg fault in rxe_comp_queue_pkt (git-fixes)\n- RDMA/rxe: Fix the problem 'mutex_destroy missing' (git-fixes)\n- RDMA/rxe: Replace pr_xxx by rxe_dbg_xxx in rxe_net.c (git-fixes)\n- RDMA/rxe: Split rxe_run_task() into two subroutines (git-fixes)\n- regulator: bd71828: Do not overwrite runtime voltages (git-fixes).\n- regulator: core: fix debugfs creation regression (git-fixes).\n- regulator: mt6360: De-capitalize devicetree regulator subnodes (git-fixes).\n- remoteproc: mediatek: Make sure IPI buffer fits in L2TCM (git-fixes).\n- ring-buffer: Fix a race between readers and resize checks (git-fixes).\n- s390/bpf: Emit a barrier for BPF_FETCH instructions (git-fixes bsc#1224795).\n- s390/cio: fix tracepoint subchannel type field (git-fixes bsc#1224796).\n- s390/cpum_cf: make crypto counters upward compatible across machine types (bsc#1224346).\n- s390/ipl: Fix incorrect initialization of len fields in nvme reipl block (git-fixes bsc#1225139).\n- s390/ipl: Fix incorrect initialization of nvme dump block (git-fixes bsc#1225138).\n- sched/topology: Optimize topology_span_sane() (bsc#1225053).\n- scsi: arcmsr: Support new PCI device IDs 1883 and 1886 (git-fixes).\n- scsi: bfa: Fix function pointer type mismatch for hcb_qe-\u003ecbfn (git-fixes).\n- scsi: core: Consult supported VPD page list prior to fetching page (git-fixes).\n- scsi: core: Fix unremoved procfs host directory regression (git-fixes).\n- scsi: csiostor: Avoid function pointer casts (git-fixes).\n- scsi: libfc: Do not schedule abort twice (git-fixes).\n- scsi: libfc: Fix up timeout error in fc_fcp_rec_error() (git-fixes).\n- scsi: lpfc: Add support for 32 byte CDBs (bsc#1225842).\n- scsi: lpfc: Change default logging level for unsolicited CT MIB commands (bsc#1225842).\n- scsi: lpfc: Change lpfc_hba hba_flag member into a bitmask (bsc#1225842).\n- scsi: lpfc: Clear deferred RSCN processing flag when driver is unloading (bsc#1225842).\n- scsi: lpfc: Copyright updates for 14.4.0.2 patches (bsc#1225842).\n- scsi: lpfc: Introduce rrq_list_lock to protect active_rrq_list (bsc#1225842).\n- scsi: lpfc: Update logging of protection type for T10 DIF I/O (bsc#1225842).\n- scsi: lpfc: Update lpfc version to 14.4.0.2 (bsc#1225842).\n- scsi: mpt3sas: Prevent sending diag_reset when the controller is ready (git-fixes).\n- scsi: mylex: Fix sysfs buffer lengths (git-fixes).\n- scsi: qla2xxx: Fix off by one in qla_edif_app_getstats() (git-fixes).\n- scsi: sd: Unregister device if device_add_disk() failed in sd_probe() (git-fixes).\n- selftests/pidfd: Fix config for pidfd_setns_test (git-fixes).\n- serial: 8250_bcm7271: use default_mux_rate if possible (git-fixes).\n- serial: kgdboc: Fix NMI-safety problems from keyboard reset code (stable-fixes).\n- serial: max3100: Fix bitwise types (git-fixes).\n- serial: max3100: Lock port-\u003elock when calling uart_handle_cts_change() (git-fixes).\n- serial: max3100: Update uart_driver_registered on driver removal (git-fixes).\n- serial: sc16is7xx: add proper sched.h include for sched_set_fifo() (git-fixes).\n- serial: sc16is7xx: fix bug in sc16is7xx_set_baud() when using prescaler (git-fixes).\n- serial: sh-sci: protect invalidating RXDMA on shutdown (git-fixes).\n- smb: client: ensure to try all targets when finding nested links (bsc#1224020).\n- smb: client: fix mount when dns_resolver key is not available (git-fixes, bsc#1224020).\n- smb: client: get rid of dfs code dep in namespace.c (bsc#1224020).\n- smb: client: get rid of dfs naming in automount code (bsc#1224020).\n- smb: client: introduce DFS_CACHE_TGT_LIST() (bsc#1224020).\n- smb: client: reduce stack usage in cifs_try_adding_channels() (bsc#1224020).\n- smb: client: remove extra @chan_count check in __cifs_put_smb_ses() (bsc#1224020).\n- smb: client: rename cifs_dfs_ref.c to namespace.c (bsc#1224020).\n- smb3: show beginning time for per share stats (bsc#1224020).\n- soc: mediatek: cmdq: Fix typo of CMDQ_JUMP_RELATIVE (git-fixes).\n- soc: qcom: rpmh-rsc: Enhance check for VRM in-flight request (git-fixes).\n- speakup: Fix sizeof() vs ARRAY_SIZE() bug (git-fixes).\n- spmi: Add a check for remove callback when removing a SPMI driver (git-fixes).\n- spmi: hisi-spmi-controller: Do not override device identifier (git-fixes).\n- swiotlb: extend buffer pre-padding to alloc_align_mask if necessary (bsc#1224331).\n- swiotlb: Fix alignment checks when both allocation and DMA masks are (bsc#1224331)\n- swiotlb: Fix double-allocation of slots due to broken alignment (bsc#1224331)\n- swiotlb: Honour dma_alloc_coherent() alignment in swiotlb_alloc() (bsc#1224331)\n- sysv: do not call sb_bread() with pointers_lock held (git-fixes).\n- thermal/drivers/tsens: Fix null pointer dereference (git-fixes).\n- tools/latency-collector: Fix -Wformat-security compile warns (git-fixes).\n- tpm_tis_spi: Account for SPI header when allocating TPM SPI xfer (bsc#1225535)\n- tpm_tis_spi: Account for SPI header when allocating TPM SPI xfer buffer (git-fixes).\n- tracing: Add MODULE_DESCRIPTION() to preemptirq_delay_test (git-fixes).\n- tracing: hide unused ftrace_event_id_fops (git-fixes).\n- tty: n_gsm: fix missing receive state reset after mode switch (git-fixes).\n- tty: n_gsm: fix possible out-of-bounds in gsm0_receive() (git-fixes).\n- usb: aqc111: stop lying about skb-\u003etruesize (git-fixes).\n- usb: gadget: u_audio: Clear uac pointer when freed (git-fixes).\n- usb: typec: tipd: fix event checking for tps6598x (git-fixes).\n- usb: typec: ucsi: displayport: Fix potential deadlock (git-fixes).\n- VMCI: Fix an error handling path in vmci_guest_probe_device() (git-fixes).\n- VMCI: Fix possible memcpy() run-time warning in vmci_datagram_invoke_guest_handler() (stable-fixes).\n- vmci: prevent speculation leaks by sanitizing event in event_deliver() (git-fixes).\n- watchdog: cpu5wdt.c: Fix use-after-free bug caused by cpu5wdt_trigger (git-fixes).\n- watchdog: ixp4xx: Make sure restart always works (git-fixes).\n- watchdog: rti_wdt: Set min_hw_heartbeat_ms to accommodate a safety margin (git-fixes).\n- wifi: ar5523: enable proper endpoint verification (git-fixes).\n- wifi: ath10k: Fix an error code problem in ath10k_dbg_sta_write_peer_debug_trigger() (git-fixes).\n- wifi: ath10k: poll service ready message before failing (git-fixes).\n- wifi: ath10k: populate board data for WCN3990 (git-fixes).\n- wifi: ath11k: do not force enable power save on non-running vdevs (git-fixes).\n- wifi: carl9170: add a proper sanity check for endpoints (git-fixes).\n- wifi: carl9170: re-fix fortified-memset warning (git-fixes).\n- wifi: cfg80211: fix rdev_dump_mpp() arguments order (stable-fixes).\n- wifi: mac80211: fix ieee80211_bss_*_flags kernel-doc (stable-fixes).\n- wifi: mwl8k: initialize cmd-\u003eaddr[] properly (git-fixes).\n- x86: Fix CPUIDLE_FLAG_IRQ_ENABLE leaking timer reprogram (git-fixes).\n- x86/boot: Ignore NMIs during very early boot (git-fixes).\n- x86/bugs: Change commas to semicolons in 'spectre_v2' sysfs file (git-fixes).\n- x86/bugs: Remove CONFIG_BHI_MITIGATION_AUTO and spectre_bhi=auto (git-fixes).\n- x86/bugs: Replace CONFIG_SPECTRE_BHI_{ON,OFF} with CONFIG_MITIGATION_SPECTRE_BHI (git-fixes).\n- x86/kvm: Do not try to disable kvmclock if it was not enabled (git-fixes).\n- x86/lib: Fix overflow when counting digits (git-fixes).\n- x86/mce: Make sure to grab mce_sysfs_mutex in set_bank() (git-fixes).\n- x86/nmi: Drop unused declaration of proc_nmi_enabled() (git-fixes).\n- x86/retpoline: Do the necessary fixup to the Zen3/4 srso return thunk for !SRSO (git-fixes).\n- x86/sev: Check for MWAITX and MONITORX opcodes in the #VC handler (git-fixes).\n- x86/sme: Fix memory encryption setting if enabled by default and not overridden (git-fixes).\n- x86/tdx: Preserve shared bit on mprotect() (git-fixes).\n- xfs: add missing cmap-\u003ebr_state = XFS_EXT_NORM update (git-fixes).\n- xfs: fix exception caused by unexpected illegal bestcount in leaf dir (git-fixes).\n- xfs: Fix false ENOSPC when performing direct write on a delalloc extent in cow fork (git-fixes).\n- xfs: fix imprecise logic in xchk_btree_check_block_owner (git-fixes).\n- xfs: fix inode reservation space for removing transaction (git-fixes).\n- xfs: shrink failure needs to hold AGI buffer (git-fixes).\n","status":"published","published":"2024-06-13T10:40:58Z","modified":"2026-02-04T04:34:29.47959Z","updated_at":"2026-11-02T15:53:54.652421Z"},{"id":"SUSE-SU-2024:2183-1","title":"Security update for the Linux Kernel","description":"\nThe SUSE Linux Enterprise 15 SP2 kernel was updated to receive various security bugfixes.\n\nThe following security bugs were fixed:\n\n- CVE-2021-47497: Fixed shift-out-of-bound (UBSAN) with byte size cells (bsc#1225355).\n- CVE-2021-47500: Fixed trigger reference couting (bsc#1225360).\n- CVE-2021-47383: Fiedx out-of-bound vmalloc access in imageblit (bsc#1225208).\n- CVE-2021-47511: Fixed negative period/buffer sizes (bsc#1225411).\n- CVE-2024-27398: Fixed use-after-free bugs caused by sco_sock_timeout (bsc#1224174).\n- CVE-2023-4244: Fixed a use-after-free in the nf_tables component, which could be exploited to achieve local privilege escalation (bsc#1215420).\n- CVE-2023-4244: Fixed a use-after-free in the nf_tables component, which could be exploited to achieve local privilege escalation (bsc#1215420).\n- CVE-2023-1829: Fixed a use-after-free vulnerability in the control index filter (tcindex) (bsc#1210335).\n- CVE-2021-47378: Destroy cm id before destroy qp to avoid use after free (bsc#1225201).\n- CVE-2021-47496: Fix flipped sign in tls_err_abort() calls (bsc#1225354)\n- CVE-2021-47402: Protect fl_walk() with rcu (bsc#1225301)\n- CVE-2022-48673: kABI workarounds for struct smc_link (bsc#1223934).\n- CVE-2023-52871: Handle a second device without data corruption (bsc#1225534)\n- CVE-2024-26828: Fix underflow in parse_server_interfaces() (bsc#1223084).\n- CVE-2024-27413: Fix incorrect allocation size (bsc#1224438).\n- CVE-2023-52840: Fix use after free in rmi_unregister_function() (bsc#1224928).\n- CVE-2021-47261: Fix initializing CQ fragments buffer (bsc#1224954)\n- CVE-2021-47254: Fix use-after-free in gfs2_glock_shrink_scan (bsc#1224888).\n- CVE-2023-52655: Check packet for fixup for true limit (bsc#1217169).\n- CVE-2023-52686: Fix a null pointer in opal_event_init() (bsc#1065729).\n\nThe following non-security bugs were fixed:\n\n- NFC: nxp: add NXP1002 (bsc#1185589).\n- PCI: rpaphp: Add MODULE_DESCRIPTION (bsc#1176869 ltc#188243).\n- af_unix: Do not use atomic ops for unix_sk(sk)-\u003einflight (bsc#1223384).\n- af_unix: Replace BUG_ON() with WARN_ON_ONCE() (bsc#1223384).\n- af_unix: annote lockless accesses to unix_tot_inflight \u0026 gc_in_progress (bsc#1223384).\n- btrfs: do not start relocation until in progress drops are done (bsc#1222251).\n- md: Replace snprintf with scnprintf (git-fixes).\n- netfilter: nf_tables: GC transaction race with abort path (git-fixes).\n- netfilter: nf_tables: GC transaction race with netns dismantle (git-fixes).\n- netfilter: nf_tables: defer gc run if previous batch is still pending (git-fixes).\n- netfilter: nf_tables: fix GC transaction races with netns and netlink event exit path (git-fixes).\n- netfilter: nf_tables: fix kdoc warnings after gc rework (git-fixes).\n- netfilter: nf_tables: fix memleak when more than 255 elements expired (git-fixes).\n- netfilter: nf_tables: mark newset as dead on transaction abort (git-fixes).\n- netfilter: nf_tables: mark set as dead when unbinding anonymous set with timeout (git-fixes).\n- netfilter: nf_tables: nft_set_rbtree: fix spurious insertion failure (git-fixes).\n- netfilter: nf_tables: release mutex after nft_gc_seq_end from abort path (git-fixes).\n- netfilter: nf_tables: skip dead set elements in netlink dump (git-fixes).\n- netfilter: nf_tables: use correct lock to protect gc_list (git-fixes).\n- netfilter: nft_set_hash: try later when GC hits EAGAIN on iteration (git-fixes).\n- netfilter: nft_set_rbtree: Add missing expired checks (git-fixes).\n- netfilter: nft_set_rbtree: Detect partial overlap with start endpoint match (git-fixes).\n- netfilter: nft_set_rbtree: Detect partial overlaps on insertion (git-fixes).\n- netfilter: nft_set_rbtree: Do not account for expired elements on insertion (git-fixes).\n- netfilter: nft_set_rbtree: Drop spurious condition for overlap detection on insertion (git-fixes).\n- netfilter: nft_set_rbtree: Handle outcomes of tree rotations in overlap detection (git-fixes).\n- netfilter: nft_set_rbtree: Introduce and use nft_rbtree_interval_start() (git-fixes).\n- netfilter: nft_set_rbtree: Switch to node list walk for overlap detection (git-fixes).\n- netfilter: nft_set_rbtree: bogus lookup/get on consecutive elements in named sets (git-fixes).\n- netfilter: nft_set_rbtree: fix null deref on element insertion (git-fixes).\n- netfilter: nft_set_rbtree: fix overlap expiration walk (git-fixes).\n- netfilter: nft_set_rbtree: overlap detection with element re-addition after deletion (git-fixes).\n- netfilter: nft_set_rbtree: skip elements in transaction from garbage collection (git-fixes).\n- netfilter: nft_set_rbtree: skip end interval element from gc (git-fixes).\n- netfilter: nft_set_rbtree: skip sync GC for new elements in this transaction (git-fixes).\n- netfilter: nft_set_rbtree: use read spinlock to avoid datapath contention (git-fixes).\n- x86/pkeys: Revert a5eff7259790 ('x86/pkeys: Add PKRU value to init_fpstate') (bsc#1215356).\n","status":"published","published":"2024-06-24T17:04:16Z","modified":"2026-02-04T02:25:32.153722Z","updated_at":"2026-11-02T15:53:55.136363Z"},{"id":"SUSE-SU-2024:2184-1","title":"Security update for the Linux Kernel","description":"\n\nThe SUSE Linux Enterprise 12 SP5 kernel was updated to receive various security bugfixes.\n\n\nThe following security bugs were fixed:\n\n- CVE-2021-46933: Fixed possible underflow in ffs_data_clear() (bsc#1220487).\n- CVE-2021-46955: Fixed an out-of-bounds read with openvswitch, when fragmenting IPv4 packets (bsc#1220513).\n- CVE-2021-47074: Fixed memory leak in nvme_loop_create_ctrl() (bsc#1220854).\n- CVE-2021-47113: Abort btrfs rename_exchange if we fail to insert the second ref (bsc#1221543).\n- CVE-2021-47131: Fixed a use-after-free after the TLS device goes down and up (bsc#1221545).\n- CVE-2021-47206: Check return value after calling  platform_get_resource() (bsc#1222894).\n- CVE-2021-47238: Fixed memory leak in ip_mc_add1_src  (bsc#1224847)\n- CVE-2021-47245: Fixed out of bounds when parsing TCP options  (bsc#1224838)\n- CVE-2021-47246: Fixed page reclaim for dead peer hairpin  (CVE-2021-47246 bsc#1224831).\n- CVE-2021-47249: Fixed memory leak in rds_recvmsg  (bsc#1224880)\n- CVE-2021-47250: Fixed memory leak in netlbl_cipsov4_add_std  (bsc#1224827)\n- CVE-2021-47265: Verify port when creating flow rule (bsc#1224957)\n- CVE-2021-47277: Avoid speculation-based attacks from out-of-range memslot  accesses (bsc#1224960).\n- CVE-2021-47281: Fixed race of snd_seq_timer_open() (bsc#1224983).\n- CVE-2021-47334: Fixed two use after free in ibmasm_init_one  (bsc#1225112).\n- CVE-2021-47352: Add validation for used length (bsc#1225124).\n- CVE-2021-47355: Fixed possible use-after-free in nicstar_cleanup()  (bsc#1225141).\n- CVE-2021-47357: Fixed possible use-after-free in ia_module_exit()  (bsc#1225144).\n- CVE-2021-47361: Fixed error handling in mcb_alloc_bus() (bsc#1225151).\n- CVE-2021-47362: Update intermediate power state for SI (bsc#1225153).\n- CVE-2021-47378: Destroy cm id before destroy qp to avoid use after free (bsc#1225201).\n- CVE-2021-47383: Fixed out-of-bound vmalloc access in imageblit (bsc#1225208).\n- CVE-2021-47397: Break out if skb_header_pointer returns NULL in sctp_rcv_ootb  (bsc#1225082)\n- CVE-2021-47401: Fixed stack information leak (bsc#1225242).\n- CVE-2021-47423: Fixed file release memory leak (bsc#1225366).\n- CVE-2021-47431: Fixed gart.bo pin_count leak (bsc#1225390).\n- CVE-2021-47469: Add SPI fix commit to be ignored (bsc#1225347)\n- CVE-2021-47483: Fixed possible double-free in regcache_rbtree_exit()  (bsc#1224907).\n- CVE-2021-47496: Fix flipped sign in tls_err_abort() calls (bsc#1225354)\n- CVE-2021-47497: Fixed shift-out-of-bound (UBSAN) with byte size cells (bsc#1225355).\n- CVE-2021-47500: Fixed trigger reference couting (bsc#1225360).\n- CVE-2021-47509: Limit the period size to 16MB (bsc#1225409).\n- CVE-2021-47511: Fixed negative period/buffer sizes (bsc#1225411).\n- CVE-2021-47548: Fixed a possible array out-of=bounds (bsc#1225506)\n- CVE-2022-48672: Fixed off-by-one error in unflatten_dt_nodes()  (CVE-2022-48672 bsc#1223931).\n- CVE-2022-48686: Fixed UAF when detecting digest errors (bsc#1223948).\n- CVE-2022-48697: Fixed a use-after-free (bsc#1223922). \n- CVE-2022-48702: Fixed out of bounds access in  snd_emu10k1_pcm_channel_alloc() (bsc#1223923).\n- CVE-2022-48704: Add a force flush to delay work when radeon (bsc#1223932)\n- CVE-2022-48708: Fixed potential NULL dereference (bsc#1224942).\n- CVE-2022-48710: Fixed a possible null pointer dereference (bsc#1225230).\n- CVE-2023-1829: Fixed a use-after-free vulnerability in the control index filter (tcindex) (bsc#1210335).\n- CVE-2023-42755: Check user supplied offsets (bsc#1215702).\n- CVE-2023-52586: Fixed  mutex lock in control vblank irq (bsc#1221081).\n- CVE-2023-52655: Check packet for fixup for true limit (bsc#1217169).\n- CVE-2023-52664: Eliminate double free in error handling logic  (bsc#1224747).\n- CVE-2023-52691: Fixed a double-free in si_dpm_init (bsc#1224607).\n- CVE-2023-52698: Fixed memory leak in netlbl_calipso_add_pass()  (bsc#1224621)\n- CVE-2023-52730: Fixed possible resource leaks in some error paths  (bsc#1224956).\n- CVE-2023-52732: Blocklist the kclient when receiving corrupted snap trace  (bsc#1225222).\n- CVE-2023-52747: Restore allocated resources on failed copyout (bsc#1224931)\n- CVE-2023-52796: Add ipvlan_route_v6_outbound() helper (bsc#1224930).\n- CVE-2023-52821: Fixed a possible null pointer dereference (bsc#1225022).\n- CVE-2023-52864: Fixed opening of char device (bsc#1225132).\n- CVE-2023-52865: Add check for mtk_alloc_clk_data  (bsc#1225086).\n- CVE-2023-52867: Fixed possible buffer overflow (bsc#1225009).\n- CVE-2023-52875: Add check for mtk_alloc_clk_data  (bsc#1225096).\n- CVE-2024-0639: Fixed a denial-of-service vulnerability due to a deadlock found in sctp_auto_asconf_init in net/sctp/socket.c (bsc#1218917).\n- CVE-2024-26625: Call sock_orphan() at release time  (bsc#1221086)\n- CVE-2024-26775: Fixed potential deadlock at set_capacity (bsc#1222627).\n- CVE-2024-26791: Fixed properly validate device names in btrfs (bsc#1222793)\n- CVE-2024-26828: Fixed underflow in parse_server_interfaces() (bsc#1223084).\n- CVE-2024-26846: Do not wait in vain when unloading module  (bsc#1223023).\n- CVE-2024-26874: Fixed a null pointer crash in (bsc#1223048)\n- CVE-2024-26876: Fixed crash on irq during probe (bsc#1223119).\n- CVE-2024-26900: Fixed kmemleak of rdev-\u003eserial (bsc#1223046).\n- CVE-2024-26915: Reset IH OVERFLOW_CLEAR bit (bsc#1223207)\n- CVE-2024-26921: Preserve kabi for sk_buff (bsc#1223138).\n- CVE-2024-26957: Fixed reference counting on zcrypt card objects  (bsc#1223666).\n- CVE-2024-26958: Fixed UAF in direct writes (bsc#1223653).\n- CVE-2024-26984: Fixed instmem race condition around ptr stores (bsc#1223633)\n- CVE-2024-26996: Fixed UAF ncm object at re-bind after usb  ep transport error (bsc#1223752).\n- CVE-2024-27008: Fixed out of bounds access (CVE-2024-27008 bsc#1223802).\n- CVE-2024-27062: Fixed nouveau lock inside client object tree (bsc#1223834).\n- CVE-2024-27396: Fixed Use-After-Free in gtp_dellink (bsc#1224096).\n- CVE-2024-27398: Fixed use-after-free bugs caused by sco_sock_timeout (bsc#1224174).\n- CVE-2024-27401: Fixed user_length taken into account when  fetching packet contents (bsc#1224181).\n- CVE-2024-27419: Fixed data-races around sysctl_net_busy_read  (bsc#1224759)\n- CVE-2024-27436: Stop parsing channels bits when all channels  are found (bsc#1224803).\n- CVE-2024-35789: Check fast rx for non-4addr sta VLAN  changes (bsc#1224749).\n- CVE-2024-35791: Flush pages under kvm-\u003elock to fix UAF in  svm_register_enc_region() (bsc#1224725).\n- CVE-2024-35809: Drain runtime-idle callbacks before driver removal  (bsc#1224738).\n- CVE-2024-35830: Register v4l2 async device only after  successful setup (bsc#1224680).\n- CVE-2024-35849: Fixed information leak in btrfs_ioctl_logical_to_ino()  (bsc#1224733).\n- CVE-2024-35877: Fixed VM_PAT handling in COW mappings (bsc#1224525).\n- CVE-2024-35878: Prevent NULL pointer dereference in vsnprintf()  (bsc#1224671).\n- CVE-2024-35887: Fixed use-after-free bugs caused by ax25_ds_del_timer  (bsc#1224663)\n- CVE-2024-35932: Do not check if plane-\u003estate-\u003efb == state-\u003efb (bsc#1224650).\n- CVE-2024-35935: Handle path ref underflow in header iterate_inode_ref() (bsc#1224645)\n- CVE-2024-35936: Add missing mutex_unlock in btrfs_relocate_sys_chunks() (bsc#1224644)\n- CVE-2024-35944: Fixed memcpy() run-time warning in dg_dispatch_as_host()  (bsc#1224648).\n- CVE-2024-35969: Fixed race condition between ipv6_get_ifaddr and ipv6_del_addr  (bsc#1224580).\n- CVE-2024-35982: Avoid infinite loop trying to resize local TT  (bsc#1224566)\n- CVE-2024-36029: Prevent access to suspended controller (bsc#1225708)\n\nThe following non-security bugs were fixed:\n\n- af_unix: annote lockless accesses to unix_tot_inflight \u0026 gc_in_progress (bsc#1223384).\n- af_unix: Do not use atomic ops for unix_sk(sk)-\u003einflight (bsc#1223384).\n- af_unix: Replace BUG_ON() with WARN_ON_ONCE() (bsc#1223384).\n- ASoC: tracing: Export SND_SOC_DAPM_DIR_OUT to its value (git-fixes).\n- assoc_array: Fix BUG_ON during garbage collect.\n- autofs: fix a leak in autofs_expire_indirect() (git-fixes)\n- Bluetooth: btusb: Some Qualcomm Bluetooth adapters stop working (git-fixes).\n- btrfs: avoid null pointer dereference on fs_info when calling btrfs_crit (git-fixes)\n- btrfs: check if root is readonly while setting security xattr (git-fixes)\n- btrfs: defrag: use btrfs_mod_outstanding_extents in cluster_pages_for_defrag (git-fixes)\n- btrfs: do not get an EINTR during drop_snapshot for reloc (git-fixes)\n- btrfs: do not stop integrity writeback too early (git-fixes)\n- btrfs: Explicitly handle btrfs_update_root failure (git-fixes)\n- btrfs: fail mount when sb flag is not in BTRFS_SUPER_FLAG_SUPP (git-fixes)\n- btrfs: fix btrfs_prev_leaf() to not return the same key twice (git-fixes)\n- btrfs: fix deadlock when writing out space cache (git-fixes)\n- Btrfs: fix incorrect {node,sector}size endianness from BTRFS_IOC_FS_INFO (git-fixes)\n- btrfs: fix lockdep splat and potential deadlock after failure running delayed items (git-fixes)\n- btrfs: fix lost error handling when looking up extended ref on log replay (git-fixes)\n- btrfs: Fix NULL pointer exception in find_bio_stripe (git-fixes)\n- btrfs: Fix out of bounds access in btrfs_search_slot (git-fixes)\n- btrfs: fix race when deleting quota root from the dirty cow roots list (git-fixes)\n- btrfs: fix range_end calculation in extent_write_locked_range (git-fixes)\n- btrfs: fix return value mixup in btrfs_get_extent (git-fixes)\n- btrfs: fix unaligned access in readdir (git-fixes)\n- btrfs: limit device extents to the device size (git-fixes)\n- btrfs: prevent to set invalid default subvolid (git-fixes)\n- btrfs: record delayed inode root in transaction (git-fixes)\n- btrfs: scrub: reject unsupported scrub flags (git-fixes)\n- btrfs: send: ensure send_fd is writable (git-fixes)\n- btrfs: send: in case of IO error log it (git-fixes)\n- btrfs: send: limit number of clones and allocated memory size (git-fixes)\n- btrfs: sysfs: use NOFS for device creation (git-fixes) Adjustment: add #include\n- btrfs: tree-checker: add missing return after error in root_item (git-fixes)\n- btrfs: tree-checker: add missing returns after data_ref alignment checks (git-fixes)\n- btrfs: tree-checker: do not error out if extent ref hash does not match (git-fixes)\n- btrfs: tree-checker: fix inline ref size in error messages (git-fixes)\n- btrfs: tree-checker: Fix misleading group system information (git-fixes)\n- btrfs: undo writable superblocke when sprouting fails (git-fixes)\n- btrfs: validate qgroup inherit for SNAP_CREATE_V2 ioctl (git-fixes)\n- ecryptfs: fix a memory leak bug in ecryptfs_init_messaging() (git-fixes)\n- ecryptfs: fix a memory leak bug in parse_tag_1_packet() (git-fixes)\n- ecryptfs: fix kernel panic with null dev_name (git-fixes)\n- ecryptfs: Fix typo in message (git-fixes)\n- ep_create_wakeup_source(): dentry name can change under you (git-fixes)\n- exportfs_decode_fh(): negative pinned may become positive without the parent locked (git-fixes)\n- fscrypt: clean up some BUG_ON()s in block encryption/decryption (git-fixes)\n- fs/proc/proc_sysctl.c: fix the default values of i_uid/i_gid on /proc/sys inodes (git-fixes)\n- ila: do not generate empty messages in ila_xlat_nl_cmd_get_mapping() (git-fixes).\n- ipv4, ipv6: Fix handling of transhdrlen in __ip{,6}_append_data() (git-fixes).\n- kprobes: Fix possible use-after-free issue on kprobe registration (git-fixes).\n- KVM: s390: Check kvm pointer when testing KVM_CAP_S390_HPAGE_1M (git-fixes bsc#1225059).\n- l2tp: pass correct message length to ip6_append_data (git-fixes).\n- lib/mpi: use kcalloc in mpi_resize (git-fixes).\n- list: fix a data-race around ep-\u003erdllist (git-fixes).\n- livepatch: Fix missing newline character in klp_resolve_symbols() (bsc#1223539).\n- mass-cve: Add convenience KBUILD_USER environment variable\n- mass-cve: Always use bash in Makefile Some constrcts are just too convenient to leave them in favor of POSIX'd /bin/sh. Switch to explicit bash.\n- mass-cve: Fail early without data files curl \u003e$@ would create/update the file even if download fails. Use explicit argument to prevent continuation with empty cve2bugzilla file.\n- mass-cve: Fix update detection with packed-refs Per-branch files are thing of the past, git may non-deterministically pack the ref files. Therefore use the timestamp of the whole packed-ref file (better false positive detection of update than breakage or false negative). Add unified approach to read packed-refs regardless of KSOURCE_GIT worktree or not.\n- mass-cve: Make BRANCH mandatory\n- mass-cve: Use dedicated worktree for reference updates So that any checkout in KSOURCE_GIT is not changed.\n- net: 9p: avoid freeing uninit memory in p9pdu_vreadf (git-fixes).\n- netfilter: nf_queue: augment nfqa_cfg_policy (git-fixes).\n- netfilter: nft_compat: explicitly reject ERROR and standard target (git-fixes).\n- netfilter: x_tables: set module owner for icmp(6) matches (git-fixes).\n- net/smc: fix fallback failed while sendmsg with fastopen (git-fixes).\n- net: tcp: fix unexcepted socket die when snd_wnd is 0 (git-fixes).\n- net/tls: Remove the context from the list in tls_device_down (bsc#1221545).\n- net: usb: ax88179_178a: stop lying about skb-\u003etruesize (git-fixes).\n- net: usb: smsc95xx: stop lying about skb-\u003etruesize (git-fixes).\n- net: usb: sr9700: stop lying about skb-\u003etruesize (git-fixes).\n- net: vmxnet3: Fix NULL pointer dereference in vmxnet3_rq_rx_complete() (bsc#1223360).\n- nfc: change order inside nfc_se_io error path (git-fixes).\n- powerpc/pseries/lparcfg: drop error message from guest name lookup (bsc#1187716 ltc#193451 git-fixes).\n- ppdev: Add an error check in register_device (git-fixes).\n- printk: Disable passing console lock owner completely during panic() (bsc#1197894).\n- printk: Update @console_may_schedule in console_trylock_spinning() (bsc#1223969).\n- rds: avoid unenecessary cong_update in loop transport (git-fixes).\n- rds: ib: Fix missing call to rds_ib_dev_put in rds_ib_setup_qp (git-fixes).\n- ring-buffer: Clean ring_buffer_poll_wait() error return (git-fixes).\n- ring-buffer: Fix a race between readers and resize checks (bsc#1222893).\n- rxrpc: Do not put crypto buffers on the stack (git-fixes).\n- rxrpc: Fix a memory leak in rxkad_verify_response() (git-fixes).\n- rxrpc: Provide a different lockdep key for call-\u003euser_mutex for kernel calls (git-fixes).\n- rxrpc: The mutex lock returned by rxrpc_accept_call() needs releasing (git-fixes).\n- rxrpc: Work around usercopy check (git-fixes).\n- s390/cpum_cf: make crypto counters upward compatible across machine types (bsc#1224347).\n- s390/pci: fix max size calculation in zpci_memcpy_toio() (git-fixes bsc#1225062).\n- scripts/check-kernel-fix: add -F parameter\n- scripts/check-kernel-fix: avoid rechecking child branches when parents are OK Topological sorted dependency tree allows to optimize check-kernel-fixe in cases where parent already has the fix. There is not reason to check branches which merge from that branch as they will get the fix eventually.\n- scripts/check-kernel-fix: print a message when no action is needed. Script exits without printing anything about the actions necessary in non-verbose mode. This can be confusing to a beginner user.\n- scripts/common-functions: for_each_build_branch traverse branches in dependency topo sorted list\n- scripts/common-functions: There are cases where Fixes tag is incorrect. Example would be bsc1223062 comment 3.\n- scripts/cve_tools: Update README Issue was fixed in ad3235427c3\n- scripts/git_sort/git_sort.py: add rafael/linux-pm.git#linux-next to remotes\n- scripts/log2: Fix References: update detection The following change -REferences: git-fixes +REferences: git-fixes bsc#123456 (note the typo in E) will not be detected as a reference update and generates a commit message like \n- scripts/PMU: Always use 12 digits for abbreviated hash references Kernel developers tend to use 12 digits for abbreviated hash references as this is mandatory for upstream work. Enforce this count in PMU for consistency.\n- tcp: tcp_make_synack() can be called from process context (git-fixes).\n- tls: Fix context leak on tls_device_down (bsc#1221545).\n- tracing: Fix blocked reader of snapshot buffer (git-fixes).\n- tracing: hide unused ftrace_event_id_fops (git-fixes).\n- tracing: Use .flush() call to wake up readers (git-fixes).\n- tracing: Use strncpy instead of memcpy when copying comm in trace.c (git-fixes).\n- tty/sysrq: replace smp_processor_id() with get_cpu() (bsc#1223540).\n- usb: aqc111: stop lying about skb-\u003etruesize (git-fixes).\n- wifi: cfg80211: avoid leaking stack data into trace (git-fixes).\n- wifi: radiotap: fix kernel-doc notation warnings (git-fixes).\n","status":"published","published":"2024-06-24T18:34:20Z","modified":"2026-02-04T02:22:33.44664Z","updated_at":"2026-11-02T15:53:55.136363Z"},{"id":"SUSE-SU-2024:2185-1","title":"Security update for the Linux Kernel","description":"\nThe SUSE Linux Enterprise 15 SP3 kernel was updated to receive various security bugfixes.\n\nThe following security bugs were fixed:\n\n- CVE-2021-47378: Destroy cm id before destroy qp to avoid use after free (bsc#1225201).\n- CVE-2021-47496: Fix flipped sign in tls_err_abort() calls (bsc#1225354)\n- CVE-2021-47402: Protect fl_walk() with rcu (bsc#1225301)\n- CVE-2022-48673: kABI workarounds for struct smc_link (bsc#1223934).\n- CVE-2023-52871: Handle a second device without data corruption (bsc#1225534)\n- CVE-2024-26828: Fix underflow in parse_server_interfaces() (bsc#1223084).\n- CVE-2021-47497: Fixed shift-out-of-bound (UBSAN) with byte size cells (bsc#1225355).\n- CVE-2021-47500: Fixed trigger reference couting (bsc#1225360).\n- CVE-2024-27413: Fix incorrect allocation size (bsc#1224438).\n- CVE-2021-47383: Fiedx out-of-bound vmalloc access in imageblit (bsc#1225208).\n- CVE-2021-47511: Fixed negative period/buffer sizes (bsc#1225411).\n- CVE-2023-52840: Fix use after free in rmi_unregister_function() (bsc#1224928).\n- CVE-2021-47261: Fix initializing CQ fragments buffer (bsc#1224954)\n- CVE-2021-47254: Fix use-after-free in gfs2_glock_shrink_scan (bsc#1224888).\n- CVE-2024-27398: Fixed use-after-free bugs caused by sco_sock_timeout (bsc#1224174).\n- CVE-2024-26921: Preserve kabi for sk_buff (bsc#1223138).\n- CVE-2023-52655: Check packet for fixup for true limit (bsc#1217169).\n- CVE-2023-4244: Fixed a use-after-free in the nf_tables component, which could be exploited to achieve local privilege escalation (bsc#1215420).\n- CVE-2023-4244: Fixed a use-after-free in the nf_tables component, which could be exploited to achieve local privilege escalation (bsc#1215420).\n- CVE-2023-1829: Fixed a use-after-free vulnerability in the control index filter (tcindex) (bsc#1210335).\n- CVE-2023-52686: Fix a null pointer in opal_event_init() (bsc#1065729).\n\nThe following non-security bugs were fixed:\n\n- af_unix: annote lockless accesses to unix_tot_inflight \u0026 gc_in_progress (bsc#1223384).\n- af_unix: Do not use atomic ops for unix_sk(sk)-\u003einflight (bsc#1223384).\n- af_unix: Replace BUG_ON() with WARN_ON_ONCE() (bsc#1223384).\n- btrfs: do not start relocation until in progress drops are done (bsc#1222251).\n- btrfs: do not start relocation until in progress drops are done (bsc#1222251).\n- cifs: add missing spinlock around tcon refcount (bsc#1213476).\n- cifs: avoid dup prefix path in dfs_get_automount_devname() (bsc#1213476).\n- cifs: avoid race conditions with parallel reconnects (bsc#1213476).\n- cifs: avoid re-lookups in dfs_cache_find() (bsc#1213476).\n- cifs: avoid use of global locks for high contention data (bsc#1213476).\n- cifs: check only tcon status on tcon related functions (bsc#1213476).\n- cifs: do all necessary checks for credits within or before locking (bsc#1213476).\n- cifs: do not block in dfs_cache_noreq_update_tgthint() (bsc#1213476).\n- cifs: do not refresh cached referrals from unactive mounts (bsc#1213476).\n- cifs: do not take exclusive lock for updating target hints (bsc#1213476).\n- cifs: fix confusing debug message (bsc#1213476).\n- cifs: fix missing unload_nls() in smb2_reconnect() (bsc#1213476).\n- cifs: fix potential deadlock in cache_refresh_path() (bsc#1213476).\n- cifs: fix refresh of cached referrals (bsc#1213476).\n- cifs: fix return of uninitialized rc in dfs_cache_update_tgthint() (bsc#1213476).\n- cifs: fix source pathname comparison of dfs supers (bsc#1213476).\n- cifs: fix status checks in cifs_tree_connect (bsc#1213476).\n- cifs: fix use-after-free bug in refresh_cache_worker() (bsc#1213476).\n- cifs: get rid of dns resolve worker (bsc#1213476).\n- cifs: get rid of mount options string parsing (bsc#1213476).\n- cifs: handle cache lookup errors different than -ENOENT (bsc#1213476).\n- cifs: ignore ipc reconnect failures during dfs failover (bsc#1213476).\n- cifs: match even the scope id for ipv6 addresses (bsc#1213476).\n- cifs: optimize reconnect of nested links (bsc#1213476).\n- cifs: prevent data race in smb2_reconnect() (bsc#1213476).\n- cifs: refresh root referrals (bsc#1213476).\n- cifs: remove duplicate code in __refresh_tcon() (bsc#1213476).\n- cifs: remove unused function (bsc#1213476).\n- cifs: remove unused smb3_fs_context::mount_options (bsc#1213476).\n- cifs: return DFS root session id in DebugData (bsc#1213476).\n- cifs: reuse cifs_match_ipaddr for comparison of dstaddr too (bsc#1213476).\n- cifs: set correct ipc status after initial tree connect (bsc#1213476).\n- cifs: set correct status of tcon ipc when reconnecting (bsc#1213476).\n- cifs: set correct tcon status after initial tree connect (bsc#1213476).\n- cifs: set DFS root session in cifs_get_smb_ses() (bsc#1213476).\n- cifs: set resolved ip in sockaddr (bsc#1213476).\n- cifs: share dfs connections and supers (bsc#1213476).\n- cifs: split out ses and tcon retrieval from mount_get_conns() (bsc#1213476).\n- cifs: use fs_context for automounts (bsc#1213476).\n- cifs: use origin fullpath for automounts (bsc#1213476).\n- cifs: use tcon allocation functions even for dummy tcon (bsc#1213476).\n- netfilter: nf_tables: defer gc run if previous batch is still pending (git-fixes).\n- netfilter: nf_tables: fix GC transaction races with netns and netlink event exit path (git-fixes).\n- netfilter: nf_tables: fix kdoc warnings after gc rework (git-fixes).\n- netfilter: nf_tables: fix memleak when more than 255 elements expired (git-fixes).\n- netfilter: nf_tables: GC transaction race with abort path (git-fixes).\n- netfilter: nf_tables: GC transaction race with netns dismantle (git-fixes).\n- netfilter: nf_tables: mark newset as dead on transaction abort (git-fixes).\n- netfilter: nf_tables: mark set as dead when unbinding anonymous set with timeout (git-fixes).\n- netfilter: nf_tables: nft_set_rbtree: fix spurious insertion failure (git-fixes).\n- netfilter: nf_tables: release mutex after nft_gc_seq_end from abort path (git-fixes).\n- netfilter: nf_tables: skip dead set elements in netlink dump (git-fixes).\n- netfilter: nf_tables: use correct lock to protect gc_list (git-fixes).\n- netfilter: nft_set_hash: try later when GC hits EAGAIN on iteration (git-fixes).\n- netfilter: nft_set_rbtree: Add missing expired checks (git-fixes).\n- netfilter: nft_set_rbtree: bogus lookup/get on consecutive elements in named sets (git-fixes).\n- netfilter: nft_set_rbtree: Detect partial overlap with start endpoint match (git-fixes).\n- netfilter: nft_set_rbtree: Detect partial overlaps on insertion (git-fixes).\n- netfilter: nft_set_rbtree: Do not account for expired elements on insertion (git-fixes).\n- netfilter: nft_set_rbtree: Drop spurious condition for overlap detection on insertion (git-fixes).\n- netfilter: nft_set_rbtree: fix null deref on element insertion (git-fixes).\n- netfilter: nft_set_rbtree: fix overlap expiration walk (git-fixes).\n- netfilter: nft_set_rbtree: Handle outcomes of tree rotations in overlap detection (git-fixes).\n- netfilter: nft_set_rbtree: Introduce and use nft_rbtree_interval_start() (git-fixes).\n- netfilter: nft_set_rbtree: overlap detection with element re-addition after deletion (git-fixes).\n- netfilter: nft_set_rbtree: skip elements in transaction from garbage collection (git-fixes).\n- netfilter: nft_set_rbtree: skip end interval element from gc (git-fixes).\n- netfilter: nft_set_rbtree: skip sync GC for new elements in this transaction (git-fixes).\n- netfilter: nft_set_rbtree: Switch to node list walk for overlap detection (git-fixes).\n- netfilter: nft_set_rbtree: use read spinlock to avoid datapath contention (git-fixes).\n- NFC: nxp: add NXP1002 (bsc#1185589).\n- PCI: rpaphp: Add MODULE_DESCRIPTION (bsc#1176869 ltc#188243).\n- smb: client: fix dfs link mount against w2k8 (git-fixes).\n- smb: client: fix null auth (bsc#1213476).\n- smb: client: set correct id, uid and cruid for multiuser automounts (git-fixes).\n- x86/xen: Drop USERGS_SYSRET64 paravirt call (git-fixes).\n","status":"published","published":"2024-06-24T19:04:59Z","modified":"2025-05-02T04:30:55.876578Z","updated_at":"2026-11-02T15:53:55.136363Z"},{"id":"SUSE-SU-2024:2189-1","title":"Security update for the Linux Kernel","description":"\nThe SUSE Linux Enterprise 15 SP4 kernel was updated to receive various security bugfixes.\n\nThe following security bugs were fixed:\n\n- CVE-2024-35905: Fixed int overflow for stack access size (bsc#1224488).\n- CVE-2024-26828: Fix underflow in parse_server_interfaces() (bsc#1223084).\n- CVE-2024-35863: Fix potential UAF in is_valid_oplock_break() (bsc#1224763).\n- CVE-2024-35867: Fix potential UAF in cifs_stats_proc_show() (bsc#1224664).\n- CVE-2024-35868: Fix potential UAF in cifs_stats_proc_write() (bsc#1224678).\n- CVE-2024-26928: Fix potential UAF in cifs_debug_files_proc_show() (bsc#1223532).\n- CVE-2024-36926: Fixed LPAR panics during boot up with a frozen PE (bsc#1222011).\n- CVE-2024-26925: Release mutex after nft_gc_seq_end from abort path (bsc#1223390).\n- CVE-2024-27413: Fix incorrect allocation size (bsc#1224438).\n- CVE-2024-35817: Set gtt bound flag in amdgpu_ttm_gart_bind (bsc#1224736).\n- CVE-2024-35904: Avoid dereference of garbage after mount failure (bsc#1224494).\n- CVE-2024-26929: Fixed double free of fcport (bsc#1223715).\n- CVE-2024-27398: Fixed use-after-free bugs caused by sco_sock_timeout (bsc#1224174).\n- CVE-2024-26930: Fixed double free of the ha-\u003evp_map pointer (bsc#1223626).\n- CVE-2024-26840: Fixed a memory leak in cachefiles_add_cache() (bsc#1222976).\n- CVE-2024-26862: Fixed packet annotate data-races around ignore_outgoing (bsc#1223111).\n- CVE-2024-0639: Fixed a denial-of-service vulnerability due to a deadlock found in sctp_auto_asconf_init in net/sctp/socket.c (bsc#1218917).\n- CVE-2024-26921: Preserve kabi for sk_buff (bsc#1223138).\n- CVE-2024-26852: Fixed use-after-free in ip6_route_mpath_notify() (bsc#1223057).\n- CVE-2023-1829: Fixed a use-after-free vulnerability in the control index filter (tcindex) (bsc#1210335).\n\nThe following non-security bugs were fixed:\n\n- af_unix: Do not use atomic ops for unix_sk(sk)-\u003einflight (bsc#1223384).\n- af_unix: Replace BUG_ON() with WARN_ON_ONCE() (bsc#1223384).\n- af_unix: annote lockless accesses to unix_tot_inflight \u0026 gc_in_progress (bsc#1223384).\n- filemap: remove use of wait bookmarks (bsc#1224085).\n- idpf: extend tx watchdog timeout (bsc#1224137).\n- ipvs: Fix checksumming on GSO of SCTP packets (bsc#1221958)\n- powerpc/kasan: Do not instrument non-maskable or raw interrupts (bsc#1223191).\n- powerpc/powernv: Add a null pointer check in opal_event_init() (bsc#1065729).\n- powerpc/powernv: Add a null pointer check to scom_debug_init_one() (bsc#1194869).\n- powerpc/pseries/iommu: IOMMU table is not initialized for kdump over SR-IOV (bsc#1220492 ltc#205270).\n- powerpc/pseries/vio: Do not return ENODEV if node or compatible missing (bsc#1220783).\n- powerpc: Avoid nmi_enter/nmi_exit in real mode interrupt (bsc#1221645 ltc#205739 bsc#1223191).\n- powerpc: Refactor verification of MSR_RI (bsc#1223191).\n","status":"published","published":"2024-06-25T06:34:56Z","modified":"2026-02-04T03:48:02.097364Z","updated_at":"2026-11-02T15:53:55.136363Z"},{"id":"SUSE-SU-2024:2190-1","title":"Security update for the Linux Kernel","description":"\n\nThe SUSE Linux Enterprise 15 SP5 kernel was updated to receive various security bugfixes.\n\n\nThe following security bugs were fixed:\n\n- CVE-2021-47548: Fixed a possible array out-of=bounds (bsc#1225506)\n- CVE-2022-48689: Fixed data-race in lru_add_fn (bsc#1223959)\n- CVE-2022-48691: Fixed memory leak in netfilter (bsc#1223961)\n- CVE-2023-1829: Fixed a use-after-free vulnerability in the control index filter (tcindex) (bsc#1210335).\n- CVE-2023-42755: Check user supplied offsets (bsc#1215702).\n- CVE-2023-52586: Fixed  mutex lock in control vblank irq (bsc#1221081).\n- CVE-2023-52618: Fixed string overflow in block/rnbd-srv (bsc#1221615).\n- CVE-2023-52655: Check packet for fixup for true limit (bsc#1217169).\n- CVE-2023-52656: Dropped any code related to SCM_RIGHTS (bsc#1224187).\n- CVE-2023-52660: Fiedx IRQ handling due to shared interrupts  (bsc#1224443).\n- CVE-2023-52664: Eliminate double free in error handling logic  (bsc#1224747).\n- CVE-2023-52671: Fixed hang/underflow when transitioning to ODM4:1 (bsc#1224729).\n- CVE-2023-52674: Add clamp() in scarlett2_mixer_ctl_put()  (bsc#1224727).\n- CVE-2023-52680: Fixed missing error checks to *_ctl_get()  (bsc#1224608).\n- CVE-2023-52692: Fixed missing error check to  scarlett2_usb_set_config() (bsc#1224628).\n- CVE-2023-52698: Fixed memory leak in netlbl_calipso_add_pass()  (bsc#1224621)\n- CVE-2023-52746: Prevent potential spectre v1 gadget in xfrm_xlate32_attr()  (bsc#1225114)\n- CVE-2023-52757: Fixed potential deadlock when releasing mids  (bsc#1225548).\n- CVE-2023-52795: Fixed use after free in vhost_vdpa_probe()  (bsc#1225085).\n- CVE-2023-52796: Add ipvlan_route_v6_outbound() helper (bsc#1224930).\n- CVE-2023-52807: Fixed out-of-bounds access may occur when coalesce  info is read via debugfs (bsc#1225097).\n- CVE-2023-52860: Fixed null pointer dereference in hisi_hns3 (bsc#1224936).\n- CVE-2023-6531: Fixed a use-after-free flaw due to a race problem in the unix garbage collector's deletion of SKB races with unix_stream_read_generic()on the socket that the SKB is queued on (bsc#1218447).\n- CVE-2024-2201: Fixed information leak in x86/BHI (bsc#1217339).\n- CVE-2024-26643: Fixed mark set as dead when unbinding anonymous  set with timeout (bsc#1221829).\n- CVE-2024-26679: Fixed read sk-\u003esk_family once in inet_recv_error() (bsc#1222385).\n- CVE-2024-26692: Fixed regression in writes when non-standard maximum write  size negotiated (bsc#1222464).\n- CVE-2024-26700: Fixed drm/amd/display: Fix MST Null Ptr for RV (bsc#1222870) \n- CVE-2024-26715: Fixed NULL pointer dereference in  dwc3_gadget_suspend (bsc#1222561).\n- CVE-2024-26742: Fixed disable_managed_interrupts (git-fixes  bsc#1222608).\n- CVE-2024-26775: Fixed potential deadlock at set_capacity (bsc#1222627).\n- CVE-2024-26777: Error out if pixclock equals zero in fbdev/sis (bsc#1222765)\n- CVE-2024-26778: Error out if pixclock equals zero in fbdev/savage (bsc#1222770)\n- CVE-2024-26791: Fixed properly validate device names in btrfs (bsc#1222793)\n- CVE-2024-26822: Set correct id, uid and cruid for multiuser  automounts (bsc#1223011).\n- CVE-2024-26828: Fixed underflow in parse_server_interfaces() (bsc#1223084).\n- CVE-2024-26839: Fixed a memleak in init_credit_return() (bsc#1222975)\n- CVE-2024-26876: Fixed crash on irq during probe (bsc#1223119).\n- CVE-2024-26900: Fixed kmemleak of rdev-\u003eserial (bsc#1223046).\n- CVE-2024-26907: Fixed a fortify source warning while accessing Eth segment in mlx5 (bsc#1223203).\n- CVE-2024-26915: Reset IH OVERFLOW_CLEAR bit (bsc#1223207)\n- CVE-2024-26919: Fixed debugfs directory leak (bsc#1223847).\n- CVE-2024-26921: Preserve kabi for sk_buff (bsc#1223138).\n- CVE-2024-26925: Release mutex after nft_gc_seq_end from abort path (bsc#1223390).\n- CVE-2024-26928: Fixed potential UAF in cifs_debug_files_proc_show() (bsc#1223532).\n- CVE-2024-26939: Fixed UAF on destroy against retire race (bsc#1223679).\n- CVE-2024-26958: Fixed UAF in direct writes (bsc#1223653).\n- CVE-2024-27042: Fixed potential out-of-bounds access in 'amdgpu_discovery_reg_base_init()' (bsc#1223823).\n- CVE-2024-27395: Fixed Use-After-Free in ovs_ct_exit (bsc#1224098).\n- CVE-2024-27396: Fixed Use-After-Free in gtp_dellink (bsc#1224096).\n- CVE-2024-27398: Fixed use-after-free bugs caused by sco_sock_timeout (bsc#1224174).\n- CVE-2024-27401: Fixed user_length taken into account when  fetching packet contents (bsc#1224181).\n- CVE-2024-27413: Fixed incorrect allocation size (bsc#1224438).\n- CVE-2024-27417: Fixed potential 'struct net' leak in inet6_rtm_getaddr()  (bsc#1224721)\n- CVE-2024-27419: Fixed data-races around sysctl_net_busy_read  (bsc#1224759)\n- CVE-2024-27431: Zero-initialise xdp_rxq_info struct before running  XDP program (bsc#1224718).\n- CVE-2024-35791: Flush pages under kvm-\u003elock to fix UAF in  svm_register_enc_region() (bsc#1224725).\n- CVE-2024-35799: Prevent crash when disable stream (bsc#1224740).\n- CVE-2024-35804: Mark target gfn of emulated atomic instruction as  dirty (bsc#1224638).\n- CVE-2024-35817: Set gtt bound flag in amdgpu_ttm_gart_bind (bsc#1224736).\n- CVE-2024-35852: Fixed memory leak when canceling rehash  work (bsc#1224502).\n- CVE-2024-35854: Fixed possible use-after-free during  rehash (bsc#1224636).\n- CVE-2024-35860: Struct bpf_link and bpf_link_ops kABI workaround  (bsc#1224531).\n- CVE-2024-35861: Fixed potential UAF in  cifs_signal_cifsd_for_reconnect() (bsc#1224766).\n- CVE-2024-35862: Fixed potential UAF in smb2_is_network_name_deleted()  (bsc#1224764).\n- CVE-2024-35863: Fixed potential UAF in is_valid_oplock_break() (bsc#1224763).\n- CVE-2024-35864: Fixed potential UAF in smb2_is_valid_lease_break()  (bsc#1224765,).\n- CVE-2024-35865: Fixed potential UAF in smb2_is_valid_oplock_break()  (bsc#1224668).\n- CVE-2024-35866: Fixed potential UAF in cifs_dump_full_key()  (bsc#1224667).\n- CVE-2024-35867: Fixed potential UAF in cifs_stats_proc_show() (bsc#1224664).\n- CVE-2024-35868: Fixed potential UAF in cifs_stats_proc_write() (bsc#1224678).\n- CVE-2024-35869: Guarantee refcounted children from parent session  (bsc#1224679).\n- CVE-2024-35870: Fixed UAF in smb2_reconnect_server() (bsc#1224020,  bsc#1224672).\n- CVE-2024-35872: Fixed GUP-fast succeeding on secretmem folios  (bsc#1224530).\n- CVE-2024-35875: Require seeding RNG with RDRAND on CoCo systems (bsc#1224665).\n- CVE-2024-35877: Fixed VM_PAT handling in COW mappings (bsc#1224525).\n- CVE-2024-35878: Prevent NULL pointer dereference in vsnprintf()  (bsc#1224671).\n- CVE-2024-35879: kABI workaround for drivers/of/dynamic.c (bsc#1224524).\n- CVE-2024-35885: Stop interface during shutdown (bsc#1224519).\n- CVE-2024-35904: Fixed dereference of garbage after mount failure (bsc#1224494).\n- CVE-2024-35905: Fixed int overflow for stack access size  (bsc#1224488).\n- CVE-2024-35907: Call request_irq() after NAPI initialized  (bsc#1224492).\n- CVE-2024-35924: Limit read size on v1.2 (bsc#1224657).\n- CVE-2024-35939: Fixed leak pages on dma_set_decrypted() failure (bsc#1224535).\n- CVE-2024-35943: Fixed a null pointer dereference in omap_prm_domain_init (bsc#1224649).\n- CVE-2024-35944: Fixed memcpy() run-time warning in dg_dispatch_as_host()  (bsc#1224648).\n- CVE-2024-35951: Fixed the error path in panfrost_mmu_map_fault_addr() (bsc#1224701).\n- CVE-2024-35959: Fixed mlx5e_priv_init() cleanup flow (bsc#1224666).\n- CVE-2024-35964: Fixed not validating setsockopt user input  (bsc#1224581).\n- CVE-2024-35969: Fixed race condition between ipv6_get_ifaddr and ipv6_del_addr  (bsc#1224580).\n- CVE-2024-35973: Fixed header validation in geneve[6]_xmit_skb  (bsc#1224586).\n- CVE-2024-35976: Validate user input for XDP_{UMEM|COMPLETION}_FILL_RING  (bsc#1224575).\n- CVE-2024-35998: Fixed lock ordering potential deadlock in  cifs_sync_mid_result (bsc#1224549).\n- CVE-2024-35999: Fixed missing lock when picking channel (bsc#1224550).\n- CVE-2024-36006: Fixed incorrect list API usage  (bsc#1224541).\n- CVE-2024-36007: Fixed warning during rehash  (bsc#1224543).\n- CVE-2024-36938: Fixed NULL pointer dereference in  sk_psock_skb_ingress_enqueue (bsc#1225761).\n\nThe following non-security bugs were fixed:\n\n- 9p: explicitly deny setlease attempts (git-fixes).\n- ACPI: bus: Indicate support for _TFP thru _OSC (git-fixes).\n- ACPI: disable -Wstringop-truncation (git-fixes).\n- ACPI: Fix Generic Initiator Affinity _OSC bit (git-fixes).\n- ACPI: LPSS: Advertise number of chip selects via property (git-fixes).\n- admin-guide/hw-vuln/core-scheduling: fix return type of PR_SCHED_CORE_GET (git-fixes).\n- af_unix: annote lockless accesses to unix_tot_inflight \u0026 gc_in_progress (bsc#1223384).\n- af_unix: Do not use atomic ops for unix_sk(sk)-\u003einflight (bsc#1223384).\n- af_unix: Replace BUG_ON() with WARN_ON_ONCE() (bsc#1223384).\n- ALSA: core: Fix NULL module pointer assignment at card init (git-fixes).\n- ALSA: hda/cs_dsp_ctl: Use private_free for control cleanup (git-fixes).\n- ALSA: line6: Zero-initialize message buffers (stable-fixes).\n- ARM: 9381/1: kasan: clear stale stack poison (git-fixes).\n- ASoC: Intel: avs: Fix ASRC module initialization (git-fixes).\n- ASoC: Intel: avs: Fix potential integer overflow (git-fixes).\n- ASoC: Intel: avs: ssm4567: Do not ignore route checks (git-fixes).\n- ASoC: Intel: Disable route checks for Skylake boards (git-fixes).\n- ASoC: kirkwood: Fix potential NULL dereference (git-fixes).\n- ASoC: mediatek: mt8192: fix register configuration for tdm (git-fixes).\n- ASoC: meson: axg-fifo: use FIELD helpers (stable-fixes).\n- ASoC: meson: axg-fifo: use threaded irq to check periods (git-fixes).\n- ASoC: tas2552: Add TX path for capturing AUDIO-OUT data (git-fixes).\n- ASoC: tracing: Export SND_SOC_DAPM_DIR_OUT to its value (git-fixes).\n- ata: pata_legacy: make legacy_exit() work again (git-fixes).\n- ata: sata_gemini: Check clk_enable() result (stable-fixes).\n- autofs: use wake_up() instead of wake_up_interruptible(() (bsc#1224166).\n- Bluetooth: Fix use-after-free bugs caused by sco_sock_timeout (git-fixes).\n- Bluetooth: hci_sync: Avoid use-after-free in dbg for hci_add_adv_monitor() (git-fixes).\n- Bluetooth: hci_sync: Do not double print name in add/remove adv_monitor (bsc#1216358).\n- Bluetooth: l2cap: fix null-ptr-deref in l2cap_chan_timeout (git-fixes).\n- Bluetooth: msft: fix slab-use-after-free in msft_do_close() (git-fixes).\n- Bluetooth: qca: add missing firmware sanity checks (git-fixes).\n- Bluetooth: qca: Fix error code in qca_read_fw_build_info() (git-fixes).\n- Bluetooth: qca: fix firmware check error path (git-fixes).\n- Bluetooth: qca: fix info leak when fetching fw build id (git-fixes).\n- Bluetooth: qca: fix NVM configuration parsing (git-fixes).\n- bnxt_re: avoid shift undefined behavior in bnxt_qplib_alloc_init_hwq (git-fixes)\n- bpf: decouple prune and jump points (bsc#1225756).\n- bpf: fix precision backtracking instruction iteration (bsc#1225756).\n- bpf: Fix precision tracking for BPF_ALU | BPF_TO_BE | BPF_END (git-fixes).\n- bpf: handle ldimm64 properly in check_cfg() (bsc#1225756).\n- bpf: mostly decouple jump history management from is_state_visited() (bsc#1225756).\n- bpf: remove unnecessary prune and jump points (bsc#1225756).\n- btrfs: add error messages to all unrecognized mount options (git-fixes)\n- btrfs: add missing mutex_unlock in btrfs_relocate_sys_chunks() (git-fixes)\n- btrfs: export: handle invalid inode or root reference in btrfs_get_parent() (git-fixes)\n- btrfs: extend locking to all space_info members accesses (git-fixes)\n- btrfs: fix btrfs_submit_compressed_write cgroup attribution (git-fixes)\n- btrfs: fix information leak in btrfs_ioctl_logical_to_ino() (git-fixes)\n- btrfs: fix missing blkdev_put() call in btrfs_scan_one_device() (git-fixes)\n- btrfs: fix off-by-one chunk length calculation at contains_pending_extent() (git-fixes)\n- btrfs: fix qgroup reserve overflow the qgroup limit (git-fixes)\n- btrfs: fix silent failure when deleting root reference (git-fixes)\n- btrfs: fix use-after-free after failure to create a snapshot (git-fixes)\n- btrfs: free exchange changeset on failures (git-fixes)\n- btrfs: handle chunk tree lookup error in btrfs_relocate_sys_chunks() (git-fixes)\n- btrfs: make search_csum_tree return 0 if we get -EFBIG (git-fixes)\n- btrfs: prevent copying too big compressed lzo segment (git-fixes)\n- btrfs: remove BUG_ON(!eie) in find_parent_nodes (git-fixes)\n- btrfs: remove BUG_ON() in find_parent_nodes() (git-fixes)\n- btrfs: repair super block num_devices automatically (git-fixes)\n- btrfs: replace the BUG_ON in btrfs_del_root_ref with proper error handling (git-fixes)\n- btrfs: send: ensure send_fd is writable (git-fixes)\n- btrfs: send: handle path ref underflow in header iterate_inode_ref() (git-fixes)\n- btrfs: send: in case of IO error log it (git-fixes)\n- btrfs: send: return EOPNOTSUPP on unknown flags (git-fixes)\n- btrfs: tree-checker: check item_size for dev_item (git-fixes)\n- btrfs: tree-checker: check item_size for inode_item (git-fixes)\n- cifs: account for primary channel in the interface list (bsc#1224020).\n- cifs: cifs_chan_is_iface_active should be called with chan_lock held (bsc#1224020).\n- cifs: distribute channels across interfaces based on speed (bsc#1224020).\n- cifs: do not pass cifs_sb when trying to add channels (bsc#1224020).\n- cifs: failure to add channel on iface should bump up weight (git-fixes, bsc#1224020).\n- cifs: fix charset issue in reconnection (bsc#1224020).\n- cifs: fix leak of iface for primary channel (git-fixes, bsc#1224020).\n- cifs: handle cases where a channel is closed (bsc#1224020).\n- cifs: handle cases where multiple sessions share connection (bsc#1224020).\n- cifs: reconnect work should have reference on server struct (bsc#1224020).\n- clk: Do not hold prepare_lock when calling kref_put() (stable-fixes).\n- clk: qcom: mmcc-msm8998: fix venus clock issue (git-fixes).\n- counter: stm32-lptimer-cnt: Provide defines for clock polarities (git-fixes).\n- counter: stm32-timer-cnt: Provide defines for slave mode selection (git-fixes).\n- cppc_cpufreq: Fix possible null pointer dereference (git-fixes).\n- cpu/hotplug: Remove the 'cpu' member of cpuhp_cpu_state (git-fixes).\n- cpumask: Add for_each_cpu_from() (bsc#1225053).\n- crypto: bcm - Fix pointer arithmetic (git-fixes).\n- crypto: ccp - drop platform ifdef checks (git-fixes).\n- crypto: ecdsa - Fix module auto-load on add-key (git-fixes).\n- crypto: x86/nh-avx2 - add missing vzeroupper (git-fixes).\n- crypto: x86/sha256-avx2 - add missing vzeroupper (git-fixes).\n- crypto: x86/sha512-avx2 - add missing vzeroupper (git-fixes).\n- dmaengine: axi-dmac: fix possible race in remove() (git-fixes).\n- dmaengine: idma64: Add check for dma_set_max_seg_size (git-fixes).\n- dm/amd/pm: Fix problems with reboot/shutdown for some SMU 13.0.4/13.0.11 users (git-fixes).\n- dm-multipath: dont't attempt SG_IO on non-SCSI-disks (bsc#1223575).\n- docs: kernel_include.py: Cope with docutils 0.21 (stable-fixes).\n- drivers/nvme: Add quirks for device 126f:2262 (git-fixes).\n- drm/amd/display: Atom Integrated System Info v2_2 for DCN35 (stable-fixes).\n- drm/amd/display: Fix division by zero in setup_dsc_config (stable-fixes).\n- drm/amd/display: Fix potential index out of bounds in color transformation function (git-fixes).\n- drm/amd/display: Handle Y carry-over in VCP X.Y calculation (stable-fixes).\n- drm/amd: Flush GFXOFF requests in prepare stage (git-fixes).\n- drm/amdgpu: Refine IB schedule error logging (stable-fixes).\n- drm/amdkfd: do not allow mapping the MMIO HDP page with large pages (git-fixes).\n- drm/arm/malidp: fix a possible null pointer dereference (git-fixes).\n- drm/bridge: anx7625: Do not log an error when DSI host can't be found (git-fixes).\n- drm: bridge: cdns-mhdp8546: Fix possible null pointer dereference (git-fixes).\n- drm/bridge: dpc3433: Do not log an error when DSI host can't be found (git-fixes).\n- drm/bridge: icn6211: Do not log an error when DSI host can't be found (git-fixes).\n- drm/bridge: lt8912b: Do not log an error when DSI host can't be found (git-fixes).\n- drm/bridge: lt9611: Do not log an error when DSI host can't be found (git-fixes).\n- drm/bridge: tc358775: Do not log an error when DSI host can't be found (git-fixes).\n- drm/bridge: tc358775: fix support for jeida-18 and jeida-24 (git-fixes).\n- drm/connector: Add \\n to message about demoting connector force-probes (git-fixes).\n- drm/i915/bios: Fix parsing backlight BDB data (git-fixes).\n- drm/lcdif: Do not disable clocks on already suspended hardware (git-fixes).\n- drm/mediatek: Add 0 size check to mtk_drm_gem_obj (git-fixes).\n- drm/meson: dw-hdmi: add bandgap setting for g12 (git-fixes).\n- drm/meson: dw-hdmi: power up phy on device init (git-fixes).\n- drm/meson: vclk: fix calculation of 59.94 fractional rates (git-fixes).\n- drm/msm/dp: allow voltage swing / pre emphasis of 3 (git-fixes).\n- drm/msm/dpu: Always flush the slave INTF on the CTL (git-fixes).\n- drm/msm/dsi: Print dual-DSI-adjusted pclk instead of original mode pclk (git-fixes).\n- drm/nouveau/dp: Do not probe eDP ports twice harder (stable-fixes).\n- drm/panel: atna33xc20: Fix unbalanced regulator in the case HPD does not assert (git-fixes).\n- drm/panel: novatek-nt35950: Do not log an error when DSI host can't be found (git-fixes).\n- drm/panel: simple: Add missing Innolux G121X1-L03 format, flags, connector (git-fixes).\n- drm: vc4: Fix possible null pointer dereference (git-fixes).\n- dt-bindings: clock: qcom: Add missing UFS QREF clocks (git-fixes)\n- dyndbg: fix old BUG_ON in \u003econtrol parser (stable-fixes).\n- efi: libstub: only free priv.runtime_map when allocated (git-fixes).\n- extcon: max8997: select IRQ_DOMAIN instead of depending on it (git-fixes).\n- fail_function: fix wrong use of fei_attr_remove().\n- fbdev: savage: Handle err return when savagefb_check_var failed (git-fixes).\n- fbdev: shmobile: fix snprintf truncation (git-fixes).\n- fbdev: sisfb: hide unused variables (git-fixes).\n- firewire: ohci: mask bus reset interrupts between ISR and bottom half (stable-fixes).\n- firmware: dmi-id: add a release callback function (git-fixes).\n- firmware: raspberrypi: Use correct device for DMA mappings (git-fixes).\n- fs/9p: drop inodes immediately on non-.L too (git-fixes).\n- fs/9p: only translate RWX permissions for plain 9P2000 (git-fixes).\n- fs/9p: translate O_TRUNC into OTRUNC (git-fixes).\n- gpio: crystalcove: Use -ENOTSUPP consistently (stable-fixes).\n- gpio: wcove: Use -ENOTSUPP consistently (stable-fixes).\n- gpu: host1x: Do not setup DMA for virtual devices (stable-fixes).\n- HID: intel-ish-hid: ipc: Add check for pci_alloc_irq_vectors (git-fixes).\n- hwmon: (corsair-cpro) Protect ccp-\u003ewait_input_report with a spinlock (git-fixes).\n- hwmon: (corsair-cpro) Use a separate buffer for sending commands (git-fixes).\n- hwmon: (corsair-cpro) Use complete_all() instead of complete() in ccp_raw_event() (git-fixes).\n- hwmon: (lm70) fix links in doc and comments (git-fixes).\n- hwmon: (pmbus/ucd9000) Increase delay from 250 to 500us (git-fixes).\n- i3c: master: svc: change ENXIO to EAGAIN when IBI occurs during start frame (git-fixes).\n- i3c: master: svc: fix invalidate IBI type and miss call client IBI handler (git-fixes).\n- IB/mlx5: Use __iowrite64_copy() for write combining stores (git-fixes)\n- idpf: extend tx watchdog timeout (bsc#1224137).\n- iio: core: Leave private pointer NULL when no private data supplied (git-fixes).\n- iio: pressure: dps310: support negative temperature values (git-fixes).\n- Input: cyapa - add missing input core locking to suspend/resume functions (git-fixes).\n- Input: ims-pcu - fix printf string overflow (git-fixes).\n- Input: pm8xxx-vibrator - correct VIB_MAX_LEVELS calculation (git-fixes).\n- iomap: Fix inline extent handling in iomap_readpage (git-fixes)\n- iomap: iomap: fix memory corruption when recording errors during writeback (git-fixes)\n- iomap: Support partial direct I/O on user copy failures (git-fixes)\n- iommu/dma: Force swiotlb_max_mapping_size on an untrusted device (bsc#1224331)\n- io_uring/unix: drop usage of io_uring socket (git-fixes).\n- irqchip/gic-v3-its: Prevent double free on error (git-fixes).\n- jffs2: prevent xattr node from overflowing the eraseblock (git-fixes).\n- kABI: bpf: struct bpf_insn_aux_data kABI workaround (bsc#1225756).\n- kcm: do not sense pfmemalloc status in kcm_sendpage() (git-fixes bsc#1223959)\n- KEYS: trusted: Do not use WARN when encode fails (git-fixes).\n- KEYS: trusted: Fix memory leak in tpm2_key_encode() (git-fixes).\n- KVM: s390: Check kvm pointer when testing KVM_CAP_S390_HPAGE_1M (git-fixes bsc#1224794).\n- leds: pwm: Disable PWM when going to suspend (git-fixes).\n- libsubcmd: Fix parse-options memory leak (git-fixes).\n- locking/atomic: Make test_and_*_bit() ordered on failure (git-fixes).\n- media: atomisp: ssh_css: Fix a null-pointer dereference in load_video_binaries (git-fixes).\n- media: dt-bindings: ovti,ov2680: Fix the power supply names (git-fixes).\n- media: mc: mark the media devnode as registered from the, start (git-fixes).\n- media: ngene: Add dvb_ca_en50221_init return value check (git-fixes).\n- media: stk1160: fix bounds checking in stk1160_copy_video() (git-fixes).\n- mei: me: add lunar lake point M DID (stable-fixes).\n- mfd: intel-lpss: Revert 'Add missing check for platform_get_resource' (git-fixes).\n- mfd: ti_am335x_tscadc: Support the correctly spelled DT property (git-fixes).\n- mfd: tqmx86: Specify IO port register range more precisely (git-fixes).\n- mlxbf_gige: Enable the GigE port in mlxbf_gige_open (git-fixes).\n- mlxbf_gige: Fix intermittent no ip issue (git-fixes).\n- mlxbf_gige: stop PHY during open() error paths (git-fixes).\n- mmc: sdhci_am654: Add tuning algorithm for delay chain (git-fixes).\n- mmc: sdhci_am654: Write ITAPDLY for DDR52 timing (git-fixes).\n- Move upstreamed patches into sorted section\n- mtd: core: Report error if first mtd_otp_size() call fails in mtd_otp_nvmem_add() (git-fixes).\n- mtd: rawnand: hynix: fixed typo (git-fixes).\n- net: do not sense pfmemalloc status in skb_append_pagefrags() (git-fixes bsc#1223959)\n- netfilter: nf_tables: bail out early if hardware offload is not supported (git-fixes bsc#1223961)\n- net: introduce __skb_fill_page_desc_noacc (git-fixes bsc#1223959)\n- net: nfc: remove inappropriate attrs check (stable-fixes).\n- net: qualcomm: rmnet: fix global oob in rmnet_policy (git-fixes).\n- net: usb: ax88179_178a: fix link status when link is set to down/up (git-fixes).\n- net:usb:qmi_wwan: support Rolling modules (stable-fixes).\n- net: usb: smsc95xx: stop lying about skb-\u003etruesize (git-fixes).\n- net: usb: sr9700: stop lying about skb-\u003etruesize (git-fixes).\n- net: vmxnet3: Fix NULL pointer dereference in vmxnet3_rq_rx_complete() (bsc#1223360).\n- nfc: nci: Fix handling of zero-length payload packets in nci_rx_work() (git-fixes).\n- nfc: nci: Fix uninit-value in nci_rx_work (git-fixes).\n- nilfs2: fix out-of-range warning (git-fixes).\n- nilfs2: fix unexpected freezing of nilfs_segctor_sync() (git-fixes).\n- nilfs2: fix use-after-free of timer for log writer thread (git-fixes).\n- nilfs2: make superblock data array index computation sparse friendly (git-fixes).\n- nvme: ensure disabling pairs with unquiesce (bsc#1224534).\n- nvme: fix miss command type check (git-fixes).\n- nvme: fix multipath batched completion accounting (git-fixes).\n- nvme-multipath: fix io accounting on failover (git-fixes).\n- nvmet: fix ns enable/disable possible hang (git-fixes).\n- PCI: dwc: Detect iATU settings after getting 'addr_space' resource (git-fixes).\n- PCI: dwc: ep: Fix DBI access failure for drivers requiring refclk from host (git-fixes).\n- PCI: dwc: Use the bitmap API to allocate bitmaps (git-fixes).\n- PCI/EDR: Align EDR_PORT_DPC_ENABLE_DSM with PCI Firmware r3.3 (git-fixes).\n- PCI/EDR: Align EDR_PORT_LOCATE_DSM with PCI Firmware r3.3 (git-fixes).\n- PCI: rockchip-ep: Remove wrong mask on subsys_vendor_id (git-fixes).\n- PCI: tegra194: Fix probe path for Endpoint mode (git-fixes).\n- pinctrl: armada-37xx: remove an unused variable (git-fixes).\n- pinctrl: core: delete incorrect free in pinctrl_enable() (git-fixes).\n- pinctrl: core: handle radix_tree_insert() errors in pinctrl_register_one_pin() (stable-fixes).\n- pinctrl: devicetree: fix refcount leak in pinctrl_dt_to_map() (git-fixes).\n- pinctrl/meson: fix typo in PDM's pin name (git-fixes).\n- pinctrl: pinctrl-aspeed-g6: Fix register offset for pinconf of GPIOR-T (git-fixes).\n- platform/x86/intel-uncore-freq: Do not present root domain on error (git-fixes).\n- platform/x86: xiaomi-wmi: Fix race condition when reporting key events (git-fixes).\n- powerpc/eeh: Permanently disable the removed device (bsc#1223991 ltc#205740).\n- powerpc/eeh: Small refactor of eeh_handle_normal_event() (bsc#1223991 ltc#205740).\n- powerpc/eeh: Use a goto for recovery failures (bsc#1223991 ltc#205740).\n- powerpc/powernv: Add a null pointer check in opal_event_init() (bsc#1065729).\n- powerpc/pseries/lparcfg: drop error message from guest name lookup (bsc#1187716 ltc#193451 git-fixes).\n- powerpc/pseries/vio: Do not return ENODEV if node or compatible missing (bsc#1220783).\n- powerpc/uaccess: Fix build errors seen with GCC 13/14 (bsc#1194869).\n- powerpc/uaccess: Use YZ asm constraint for ld (bsc#1194869).\n- power: rt9455: hide unused rt9455_boost_voltage_values (git-fixes).\n- ppdev: Add an error check in register_device (git-fixes).\n- printk: Update @console_may_schedule in console_trylock_spinning() (bsc#1225616).\n- qibfs: fix dentry leak (git-fixes)\n- RDMA/hns: Add max_ah and cq moderation capacities in query_device() (git-fixes)\n- RDMA/hns: Fix deadlock on SRQ async events. (git-fixes)\n- RDMA/hns: Fix GMV table pagesize (git-fixes)\n- RDMA/hns: Fix return value in hns_roce_map_mr_sg (git-fixes)\n- RDMA/hns: Fix UAF for cq async event (git-fixes)\n- RDMA/hns: Modify the print level of CQE error (git-fixes)\n- RDMA/hns: Use complete parentheses in macros (git-fixes)\n- RDMA/IPoIB: Fix format truncation compilation errors (git-fixes)\n- RDMA/mlx5: Adding remote atomic access flag to updatable flags (git-fixes)\n- RDMA/mlx5: Fix port number for counter query in multi-port configuration (git-fixes)\n- RDMA/rxe: Add ibdev_dbg macros for rxe (git-fixes)\n- RDMA/rxe: Fix incorrect rxe_put in error path (git-fixes)\n- RDMA/rxe: Fix seg fault in rxe_comp_queue_pkt (git-fixes)\n- RDMA/rxe: Fix the problem 'mutex_destroy missing' (git-fixes)\n- RDMA/rxe: Replace pr_xxx by rxe_dbg_xxx in rxe_net.c (git-fixes)\n- RDMA/rxe: Split rxe_run_task() into two subroutines (git-fixes)\n- regulator: bd71828: Do not overwrite runtime voltages (git-fixes).\n- regulator: core: fix debugfs creation regression (git-fixes).\n- regulator: mt6360: De-capitalize devicetree regulator subnodes (git-fixes).\n- remoteproc: mediatek: Make sure IPI buffer fits in L2TCM (git-fixes).\n- Revert 'cifs: reconnect work should have reference on server struct' (git-fixes, bsc#1224020).\n- Revert 'drm/bridge: ti-sn65dsi83: Fix enable error path' (git-fixes).\n- ring-buffer: Fix a race between readers and resize checks (git-fixes).\n- s390/bpf: Emit a barrier for BPF_FETCH instructions (git-fixes bsc#1224795).\n- s390/cio: fix tracepoint subchannel type field (git-fixes bsc#1224796).\n- s390/cpum_cf: make crypto counters upward compatible across machine types (bsc#1224346).\n- s390/ipl: Fix incorrect initialization of len fields in nvme reipl block (git-fixes bsc#1225139).\n- s390/ipl: Fix incorrect initialization of nvme dump block (git-fixes bsc#1225138).\n- sched/topology: Optimize topology_span_sane() (bsc#1225053).\n- scsi: arcmsr: Support new PCI device IDs 1883 and 1886 (git-fixes).\n- scsi: bfa: Fix function pointer type mismatch for hcb_qe-\u003ecbfn (git-fixes).\n- scsi: core: Consult supported VPD page list prior to fetching page (git-fixes).\n- scsi: core: Fix unremoved procfs host directory regression (git-fixes).\n- scsi: csiostor: Avoid function pointer casts (git-fixes).\n- scsi: libfc: Do not schedule abort twice (git-fixes).\n- scsi: libfc: Fix up timeout error in fc_fcp_rec_error() (git-fixes).\n- scsi: lpfc: Add support for 32 byte CDBs (bsc#1225842).\n- scsi: lpfc: Change default logging level for unsolicited CT MIB commands (bsc#1225842).\n- scsi: lpfc: Change lpfc_hba hba_flag member into a bitmask (bsc#1225842).\n- scsi: lpfc: Clear deferred RSCN processing flag when driver is unloading (bsc#1225842).\n- scsi: lpfc: Copyright updates for 14.4.0.2 patches (bsc#1225842).\n- scsi: lpfc: Introduce rrq_list_lock to protect active_rrq_list (bsc#1225842).\n- scsi: lpfc: Update logging of protection type for T10 DIF I/O (bsc#1225842).\n- scsi: lpfc: Update lpfc version to 14.4.0.2 (bsc#1225842).\n- scsi: mpt3sas: Prevent sending diag_reset when the controller is ready (git-fixes).\n- scsi: mylex: Fix sysfs buffer lengths (git-fixes).\n- scsi: qla2xxx: Fix off by one in qla_edif_app_getstats() (git-fixes).\n- scsi: sd: Unregister device if device_add_disk() failed in sd_probe() (git-fixes).\n- selftests/pidfd: Fix config for pidfd_setns_test (git-fixes).\n- serial: 8250_bcm7271: use default_mux_rate if possible (git-fixes).\n- serial: kgdboc: Fix NMI-safety problems from keyboard reset code (stable-fixes).\n- serial: max3100: Fix bitwise types (git-fixes).\n- serial: max3100: Lock port-\u003elock when calling uart_handle_cts_change() (git-fixes).\n- serial: sc16is7xx: add proper sched.h include for sched_set_fifo() (git-fixes).\n- serial: sc16is7xx: fix bug in sc16is7xx_set_baud() when using prescaler (git-fixes).\n- serial: sh-sci: protect invalidating RXDMA on shutdown (git-fixes).\n- smb3: show beginning time for per share stats (bsc#1224020).\n- smb: client: ensure to try all targets when finding nested links (bsc#1224020).\n- smb: client: fix mount when dns_resolver key is not available (git-fixes, bsc#1224020).\n- smb: client: get rid of dfs code dep in namespace.c (bsc#1224020).\n- smb: client: get rid of dfs naming in automount code (bsc#1224020).\n- smb: client: introduce DFS_CACHE_TGT_LIST() (bsc#1224020).\n- smb: client: reduce stack usage in cifs_try_adding_channels() (bsc#1224020).\n- smb: client: remove extra @chan_count check in __cifs_put_smb_ses() (bsc#1224020).\n- smb: client: rename cifs_dfs_ref.c to namespace.c (bsc#1224020).\n- soc: mediatek: cmdq: Fix typo of CMDQ_JUMP_RELATIVE (git-fixes).\n- soc: qcom: rpmh-rsc: Enhance check for VRM in-flight request (git-fixes).\n- Sort recent BHI patches\n- speakup: Fix sizeof() vs ARRAY_SIZE() bug (git-fixes).\n- spmi: Add a check for remove callback when removing a SPMI driver (git-fixes).\n- spmi: hisi-spmi-controller: Do not override device identifier (git-fixes).\n- swiotlb: extend buffer pre-padding to alloc_align_mask if necessary (bsc#1224331). \n- swiotlb: Fix alignment checks when both allocation and DMA masks are (bsc#1224331)\n- swiotlb: Fix double-allocation of slots due to broken alignment (bsc#1224331)\n- swiotlb: Honour dma_alloc_coherent() alignment in swiotlb_alloc() (bsc#1224331)\n- sysv: do not call sb_bread() with pointers_lock held (git-fixes).\n- thermal/drivers/tsens: Fix null pointer dereference (git-fixes).\n- tools/latency-collector: Fix -Wformat-security compile warns (git-fixes).\n- tpm_tis_spi: Account for SPI header when allocating TPM SPI xfer (bsc#1225535)\n- tpm_tis_spi: Account for SPI header when allocating TPM SPI xfer buffer (git-fixes).\n- tracing: Add MODULE_DESCRIPTION() to preemptirq_delay_test (git-fixes).\n- tracing: hide unused ftrace_event_id_fops (git-fixes).\n- tty: n_gsm: fix missing receive state reset after mode switch (git-fixes).\n- tty: n_gsm: fix possible out-of-bounds in gsm0_receive() (git-fixes).\n- usb: aqc111: stop lying about skb-\u003etruesize (git-fixes).\n- USB: core: Add hub_get() and hub_put() routines (git-fixes).\n- USB: core: Fix access violation during port device removal (git-fixes).\n- USB: core: Fix deadlock in port 'disable' sysfs attribute (git-fixes).\n- usb: dwc3: core: Prevent phy suspend during init (Git-fixes).\n- usb: gadget: u_audio: Clear uac pointer when freed (git-fixes).\n- usb: typec: tipd: fix event checking for tps6598x (git-fixes).\n- usb: typec: ucsi: displayport: Fix potential deadlock (git-fixes).\n- VMCI: Fix an error handling path in vmci_guest_probe_device() (git-fixes).\n- VMCI: Fix possible memcpy() run-time warning in vmci_datagram_invoke_guest_handler() (stable-fixes).\n- vmci: prevent speculation leaks by sanitizing event in event_deliver() (git-fixes).\n- watchdog: cpu5wdt.c: Fix use-after-free bug caused by cpu5wdt_trigger (git-fixes).\n- watchdog: ixp4xx: Make sure restart always works (git-fixes).\n- watchdog: rti_wdt: Set min_hw_heartbeat_ms to accommodate a safety margin (git-fixes).\n- wifi: ar5523: enable proper endpoint verification (git-fixes).\n- wifi: ath10k: Fix an error code problem in ath10k_dbg_sta_write_peer_debug_trigger() (git-fixes).\n- wifi: ath10k: poll service ready message before failing (git-fixes).\n- wifi: ath10k: populate board data for WCN3990 (git-fixes).\n- wifi: ath11k: do not force enable power save on non-running vdevs (git-fixes).\n- wifi: carl9170: add a proper sanity check for endpoints (git-fixes).\n- wifi: carl9170: re-fix fortified-memset warning (git-fixes).\n- wifi: cfg80211: fix rdev_dump_mpp() arguments order (stable-fixes).\n- wifi: mac80211: fix ieee80211_bss_*_flags kernel-doc (stable-fixes).\n- wifi: mwl8k: initialize cmd-\u003eaddr[] properly (git-fixes).\n- x86/boot: Ignore NMIs during very early boot (git-fixes).\n- x86/bugs: Cache the value of MSR_IA32_ARCH_CAPABILITIES (git-fixes).\n- x86/bugs: Change commas to semicolons in 'spectre_v2' sysfs file (git-fixes).\n- x86/bugs: Fix BHI documentation (git-fixes).\n- x86/bugs: Fix BHI handling of RRSBA (git-fixes).\n- x86/bugs: Fix BHI retpoline check (git-fixes).\n- x86/bugs: Fix return type of spectre_bhi_state() (git-fixes).\n- x86/bugs: Remove CONFIG_BHI_MITIGATION_AUTO and spectre_bhi=auto (git-fixes).\n- x86/bugs: Rename various 'ia32_cap' variables to 'x86_arch_cap_msr' (git-fixes).\n- x86/bugs: Replace CONFIG_SPECTRE_BHI_{ON,OFF} with CONFIG_MITIGATION_SPECTRE_BHI (git-fixes).\n- x86: Fix CPUIDLE_FLAG_IRQ_ENABLE leaking timer reprogram (git-fixes).\n- x86/kvm: Do not try to disable kvmclock if it was not enabled (git-fixes).\n- x86/lib: Fix overflow when counting digits (git-fixes).\n- x86/mce: Make sure to grab mce_sysfs_mutex in set_bank() (git-fixes).\n- x86/nmi: Drop unused declaration of proc_nmi_enabled() (git-fixes).\n- x86/retpoline: Do the necessary fixup to the Zen3/4 srso return thunk for !SRSO (git-fixes).\n- x86/sev: Check for MWAITX and MONITORX opcodes in the #VC handler (git-fixes).\n- x86/sme: Fix memory encryption setting if enabled by default and not overridden (git-fixes).\n- x86/tdx: Preserve shared bit on mprotect() (git-fixes).\n- xfs: fix exception caused by unexpected illegal bestcount in leaf dir (git-fixes).\n- xfs: Fix false ENOSPC when performing direct write on a delalloc extent in cow fork (git-fixes).\n- xfs: fix imprecise logic in xchk_btree_check_block_owner (git-fixes).\n- xfs: fix inode reservation space for removing transaction (git-fixes).\n- xfs: shrink failure needs to hold AGI buffer (git-fixes).\n","status":"published","published":"2024-06-25T08:50:52Z","modified":"2026-02-04T03:07:05.716244Z","updated_at":"2026-11-02T15:53:55.136363Z"}]}}