https://cve.radiocsirt.org Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Fri, 02 Oct 2026 15:34:41 +0000 https://cve.radiocsirt.org/vuln/bdu:2026-13932 bdu:2026-13932 https://cve.radiocsirt.org/vuln/bdu:2026-13932 https://cve.radiocsirt.org/vuln/bell-cve-2026-52979 <p><strong>Affected:</strong> Alpaquita:stream: linux-lts</p> <p><strong>Affected:</strong> Alpaquita:stream: linux-lts</p> https://cve.radiocsirt.org/vuln/bell-cve-2026-52979 https://cve.radiocsirt.org/vuln/certfr-2026-avi-0926 certfr-2026-avi-0926 https://cve.radiocsirt.org/vuln/certfr-2026-avi-0926 https://cve.radiocsirt.org/vuln/euvd-2026-329919 EUVD-2026-329919 https://cve.radiocsirt.org/vuln/euvd-2026-329919 https://cve.radiocsirt.org/vuln/fkie_cve-2026-52979 <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>net: psp: check for device unregister when creating assoc</p> <p>psp_assoc_device_get_locked() obtains a psp_dev reference via psp_dev_get_for_sock() (which uses psp_dev_tryget() under RCU); it then acquires psd-&gt;lock and drops the reference. Before the lock is taken, psp_dev_unregister() can run to completion: take psd-&gt;lock, clear out state, unlock, drop the registration reference.</p> <p>The expectation is that the lock prevents device unregistration, but much like with netdevs special care has to be taken when &#34;upgrading&#34; a reference to a locked device. Add the missing check if device is still alive. psp_dev_is_registered() exists already but had no callers, which makes me wonder if I either forgot to add this or lost the check during refactoring...</p> <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>net: psp: check for device unregister when creating assoc</p> <p>psp_assoc_device_get_locked() obtains a psp_dev reference via psp_dev_get_for_sock() (which uses psp_dev_tryget() under RCU); it then acquires psd-&gt;lock and drops the reference. Before the lock is taken, psp_dev_unregister() can run to completion: take psd-&gt;lock, clear out state, unlock, drop the registration reference.</p> <p>The expectation is that the lock prevents device unregistration, but much like with netdevs special care has to be taken when &#34;upgrading&#34; a reference to a locked device. Add the missing check if device is still alive. psp_dev_is_registered() exists already but had no callers, which makes me wonder if I either forgot to add this or lost the check during refactoring...</p> https://cve.radiocsirt.org/vuln/fkie_cve-2026-52979 https://cve.radiocsirt.org/vuln/ghsa-gf8v-7h89-7w9j <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>net: psp: check for device unregister when creating assoc</p> <p>psp_assoc_device_get_locked() obtains a psp_dev reference via psp_dev_get_for_sock() (which uses psp_dev_tryget() under RCU); it then acquires psd-&gt;lock and drops the reference. Before the lock is taken, psp_dev_unregister() can run to completion: take psd-&gt;lock, clear out state, unlock, drop the registration reference.</p> <p>The expectation is that the lock prevents device unregistration, but much like with netdevs special care has to be taken when &#34;upgrading&#34; a reference to a locked device. Add the missing check if device is still alive. psp_dev_is_registered() exists already but had no callers, which makes me wonder if I either forgot to add this or lost the check during refactoring...</p> <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>net: psp: check for device unregister when creating assoc</p> <p>psp_assoc_device_get_locked() obtains a psp_dev reference via psp_dev_get_for_sock() (which uses psp_dev_tryget() under RCU); it then acquires psd-&gt;lock and drops the reference. Before the lock is taken, psp_dev_unregister() can run to completion: take psd-&gt;lock, clear out state, unlock, drop the registration reference.</p> <p>The expectation is that the lock prevents device unregistration, but much like with netdevs special care has to be taken when &#34;upgrading&#34; a reference to a locked device. Add the missing check if device is still alive. psp_dev_is_registered() exists already but had no callers, which makes me wonder if I either forgot to add this or lost the check during refactoring...</p> https://cve.radiocsirt.org/vuln/ghsa-gf8v-7h89-7w9j https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-52979 <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 109 more</p> <p>In the Linux kernel, the following vulnerability has been resolved: net: psp: check for device unregister when creating assoc psp_assoc_device_get_locked() obtains a psp_dev reference via psp_dev_get_for_sock() (which uses psp_dev_tryget() under RCU); it then acquires psd-&gt;lock and drops the reference. Before the lock is taken, psp_dev_unregister() can run to completion: take psd-&gt;lock, clear out state, unlock, drop the registration reference. The expectation is that the lock prevents device unregistration, but much like with netdevs special care has to be taken when &#34;upgrading&#34; a reference to a locked device. Add the missing check if device is still alive. psp_dev_is_registered() exists already but had no callers, which makes me wonder if I either forgot to add this or lost the check during refactoring...</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 109 more</p> <p>In the Linux kernel, the following vulnerability has been resolved: net: psp: check for device unregister when creating assoc psp_assoc_device_get_locked() obtains a psp_dev reference via psp_dev_get_for_sock() (which uses psp_dev_tryget() under RCU); it then acquires psd-&gt;lock and drops the reference. Before the lock is taken, psp_dev_unregister() can run to completion: take psd-&gt;lock, clear out state, unlock, drop the registration reference. The expectation is that the lock prevents device unregistration, but much like with netdevs special care has to be taken when &#34;upgrading&#34; a reference to a locked device. Add the missing check if device is still alive. psp_dev_is_registered() exists already but had no callers, which makes me wonder if I either forgot to add this or lost the check during refactoring...</p> https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-52979 https://cve.radiocsirt.org/vuln/wid-sec-w-2026-2077 <p>Ein entfernter Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um Sicherheitsvorkehrungen zu umgehen, einen Denial-of-Service-Zustand herbeizuführen und weitere, nicht näher spezifizierte Auswirkungen zu erzielen.</p> <p>Ein entfernter Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um Sicherheitsvorkehrungen zu umgehen, einen Denial-of-Service-Zustand herbeizuführen und weitere, nicht näher spezifizierte Auswirkungen zu erzielen.</p> https://cve.radiocsirt.org/vuln/wid-sec-w-2026-2077