https://cve.radiocsirt.org Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Sun, 04 Oct 2026 19:34:28 +0000 https://cve.radiocsirt.org/vuln/bdu:2024-06658 bdu:2024-06658 https://cve.radiocsirt.org/vuln/bdu:2024-06658 https://cve.radiocsirt.org/vuln/certfr-2024-avi-0779 certfr-2024-avi-0779 https://cve.radiocsirt.org/vuln/certfr-2024-avi-0779 https://cve.radiocsirt.org/vuln/euvd-2026-344623 EUVD-2026-344623 https://cve.radiocsirt.org/vuln/euvd-2026-344623 https://cve.radiocsirt.org/vuln/fkie_cve-2022-48941 <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>ice: fix concurrent reset and removal of VFs</p> <p>Commit c503e63200c6 (&#34;ice: Stop processing VF messages during teardown&#34;) introduced a driver state flag, ICE_VF_DEINIT_IN_PROGRESS, which is intended to prevent some issues with concurrently handling messages from VFs while tearing down the VFs.</p> <p>This change was motivated by crashes caused while tearing down and bringing up VFs in rapid succession.</p> <p>It turns out that the fix actually introduces issues with the VF driver caused because the PF no longer responds to any messages sent by the VF during its .remove routine. This results in the VF potentially removing its DMA memory before the PF has shut down the device queues.</p> <p>Additionally, the fix doesn&#39;t actually resolve concurrency issues within the ice driver. It is possible for a VF to initiate a reset just prior to the ice driver removing VFs. This can result in the remove task concurrently operating while the VF is being reset. This results in similar memory corruption and panics purportedly fixed by that commit.</p> <p>Fix this concurrency at its root by protecting both the reset and removal flows using the existing VF cfg_lock. This ensures that we cannot remove the VF while any outstanding critical tasks such as a virtchnl message or a reset are occurring.</p> <p>This locking change also fixes the root cause originally fixed by commit c503e63200c6 (&#34;ice: Stop processing VF messages during teardown&#34;), so we can simply…</p> <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>ice: fix concurrent reset and removal of VFs</p> <p>Commit c503e63200c6 (&#34;ice: Stop processing VF messages during teardown&#34;) introduced a driver state flag, ICE_VF_DEINIT_IN_PROGRESS, which is intended to prevent some issues with concurrently handling messages from VFs while tearing down the VFs.</p> <p>This change was motivated by crashes caused while tearing down and bringing up VFs in rapid succession.</p> <p>It turns out that the fix actually introduces issues with the VF driver caused because the PF no longer responds to any messages sent by the VF during its .remove routine. This results in the VF potentially removing its DMA memory before the PF has shut down the device queues.</p> <p>Additionally, the fix doesn&#39;t actually resolve concurrency issues within the ice driver. It is possible for a VF to initiate a reset just prior to the ice driver removing VFs. This can result in the remove task concurrently operating while the VF is being reset. This results in similar memory corruption and panics purportedly fixed by that commit.</p> <p>Fix this concurrency at its root by protecting both the reset and removal flows using the existing VF cfg_lock. This ensures that we cannot remove the VF while any outstanding critical tasks such as a virtchnl message or a reset are occurring.</p> <p>This locking change also fixes the root cause originally fixed by commit c503e63200c6 (&#34;ice: Stop processing VF messages during teardown&#34;), so we can simply…</p> https://cve.radiocsirt.org/vuln/fkie_cve-2022-48941 https://cve.radiocsirt.org/vuln/ghsa-2862-5xjv-8phr <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>ice: fix concurrent reset and removal of VFs</p> <p>Commit c503e63200c6 (&#34;ice: Stop processing VF messages during teardown&#34;) introduced a driver state flag, ICE_VF_DEINIT_IN_PROGRESS, which is intended to prevent some issues with concurrently handling messages from VFs while tearing down the VFs.</p> <p>This change was motivated by crashes caused while tearing down and bringing up VFs in rapid succession.</p> <p>It turns out that the fix actually introduces issues with the VF driver caused because the PF no longer responds to any messages sent by the VF during its .remove routine. This results in the VF potentially removing its DMA memory before the PF has shut down the device queues.</p> <p>Additionally, the fix doesn&#39;t actually resolve concurrency issues within the ice driver. It is possible for a VF to initiate a reset just prior to the ice driver removing VFs. This can result in the remove task concurrently operating while the VF is being reset. This results in similar memory corruption and panics purportedly fixed by that commit.</p> <p>Fix this concurrency at its root by protecting both the reset and removal flows using the existing VF cfg_lock. This ensures that we cannot remove the VF while any outstanding critical tasks such as a virtchnl message or a reset are occurring.</p> <p>This locking change also fixes the root cause originally fixed by commit c503e63200c6 (&#34;ice: Stop processing VF messages during teardown&#34;), so we can simply…</p> <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>ice: fix concurrent reset and removal of VFs</p> <p>Commit c503e63200c6 (&#34;ice: Stop processing VF messages during teardown&#34;) introduced a driver state flag, ICE_VF_DEINIT_IN_PROGRESS, which is intended to prevent some issues with concurrently handling messages from VFs while tearing down the VFs.</p> <p>This change was motivated by crashes caused while tearing down and bringing up VFs in rapid succession.</p> <p>It turns out that the fix actually introduces issues with the VF driver caused because the PF no longer responds to any messages sent by the VF during its .remove routine. This results in the VF potentially removing its DMA memory before the PF has shut down the device queues.</p> <p>Additionally, the fix doesn&#39;t actually resolve concurrency issues within the ice driver. It is possible for a VF to initiate a reset just prior to the ice driver removing VFs. This can result in the remove task concurrently operating while the VF is being reset. This results in similar memory corruption and panics purportedly fixed by that commit.</p> <p>Fix this concurrency at its root by protecting both the reset and removal flows using the existing VF cfg_lock. This ensures that we cannot remove the VF while any outstanding critical tasks such as a virtchnl message or a reset are occurring.</p> <p>This locking change also fixes the root cause originally fixed by commit c503e63200c6 (&#34;ice: Stop processing VF messages during teardown&#34;), so we can simply…</p> https://cve.radiocsirt.org/vuln/ghsa-2862-5xjv-8phr https://cve.radiocsirt.org/vuln/suse-su-2024:3190-1 <p>Security update for the Linux Kernel</p> <p>Security update for the Linux Kernel</p> https://cve.radiocsirt.org/vuln/suse-su-2024:3190-1 https://cve.radiocsirt.org/vuln/ubuntu-cve-2022-48941 <p><strong>Affected:</strong> Ubuntu:16.04:LTS: linux-hwe-edge, Ubuntu:18.04:LTS: linux-aws-5.0, Ubuntu:18.04:LTS: linux-aws-5.3, Ubuntu:18.04:LTS: linux-azure, Ubuntu:18.04:LTS: linux-azure-5.3, Ubuntu:18.04:LTS: linux-azure-edge, Ubuntu:18.04:LTS: linux-gcp, Ubuntu:18.04:LTS: linux-gcp-5.3, Ubuntu:18.04:LTS: linux-gke-4.15, Ubuntu:18.04:LTS: linux-gke-5.4 and 67 more</p> <p>In the Linux kernel, the following vulnerability has been resolved: ice: fix concurrent reset and removal of VFs Commit c503e63200c6 (&#34;ice: Stop processing VF messages during teardown&#34;) introduced a driver state flag, ICE_VF_DEINIT_IN_PROGRESS, which is intended to prevent some issues with concurrently handling messages from VFs while tearing down the VFs. This change was motivated by crashes caused while tearing down and bringing up VFs in rapid succession. It turns out that the fix actually introduces issues with the VF driver caused because the PF no longer responds to any messages sent by the VF during its .remove routine. This results in the VF potentially removing its DMA memory before the PF has shut down the device queues. Additionally, the fix doesn&#39;t actually resolve concurrency issues within the ice driver. It is possible for a VF to initiate a reset just prior to the ice driver removing VFs. This can result in the remove task concurrently operating while the VF is being reset. This results in similar memory corruption and panics purportedly fixed by that commit. Fix this concurrency at its root by protecting both the reset and removal flows using the existing VF cfg_lock. This ensures that we cannot remove the VF while any outstanding critical tasks such as a virtchnl message or a reset are occurring. This locking change also fixes the root cause originally fixed by commit c503e63200c6 (&#34;ice: Stop processing VF messages during teardown&#34;), so we can simply revert…</p> <p><strong>Affected:</strong> Ubuntu:16.04:LTS: linux-hwe-edge, Ubuntu:18.04:LTS: linux-aws-5.0, Ubuntu:18.04:LTS: linux-aws-5.3, Ubuntu:18.04:LTS: linux-azure, Ubuntu:18.04:LTS: linux-azure-5.3, Ubuntu:18.04:LTS: linux-azure-edge, Ubuntu:18.04:LTS: linux-gcp, Ubuntu:18.04:LTS: linux-gcp-5.3, Ubuntu:18.04:LTS: linux-gke-4.15, Ubuntu:18.04:LTS: linux-gke-5.4 and 67 more</p> <p>In the Linux kernel, the following vulnerability has been resolved: ice: fix concurrent reset and removal of VFs Commit c503e63200c6 (&#34;ice: Stop processing VF messages during teardown&#34;) introduced a driver state flag, ICE_VF_DEINIT_IN_PROGRESS, which is intended to prevent some issues with concurrently handling messages from VFs while tearing down the VFs. This change was motivated by crashes caused while tearing down and bringing up VFs in rapid succession. It turns out that the fix actually introduces issues with the VF driver caused because the PF no longer responds to any messages sent by the VF during its .remove routine. This results in the VF potentially removing its DMA memory before the PF has shut down the device queues. Additionally, the fix doesn&#39;t actually resolve concurrency issues within the ice driver. It is possible for a VF to initiate a reset just prior to the ice driver removing VFs. This can result in the remove task concurrently operating while the VF is being reset. This results in similar memory corruption and panics purportedly fixed by that commit. Fix this concurrency at its root by protecting both the reset and removal flows using the existing VF cfg_lock. This ensures that we cannot remove the VF while any outstanding critical tasks such as a virtchnl message or a reset are occurring. This locking change also fixes the root cause originally fixed by commit c503e63200c6 (&#34;ice: Stop processing VF messages during teardown&#34;), so we can simply revert…</p> https://cve.radiocsirt.org/vuln/ubuntu-cve-2022-48941 https://cve.radiocsirt.org/vuln/wid-sec-w-2024-1898 <p>Ein lokaler Angreifer kann mehrere Schwachstellen im Linux-Kernel ausnutzen, um einen Denial-of-Service-Zustand zu erzeugen oder einen unspezifischen Angriff durchzuführen.</p> <p>Ein lokaler Angreifer kann mehrere Schwachstellen im Linux-Kernel ausnutzen, um einen Denial-of-Service-Zustand zu erzeugen oder einen unspezifischen Angriff durchzuführen.</p> https://cve.radiocsirt.org/vuln/wid-sec-w-2024-1898