https://cve.radiocsirt.org Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Fri, 02 Oct 2026 16:11:57 +0000 https://cve.radiocsirt.org/vuln/bell-cve-2026-46170 <p><strong>Affected:</strong> Alpaquita:23: linux-lts, Alpaquita:25: linux-lts, Alpaquita:stream: linux-lts</p> <p><strong>Affected:</strong> Alpaquita:23: linux-lts, Alpaquita:25: linux-lts, Alpaquita:stream: linux-lts</p> https://cve.radiocsirt.org/vuln/bell-cve-2026-46170 https://cve.radiocsirt.org/vuln/certfr-2026-avi-0809 certfr-2026-avi-0809 https://cve.radiocsirt.org/vuln/certfr-2026-avi-0809 https://cve.radiocsirt.org/vuln/euvd-2026-367487 EUVD-2026-367487 https://cve.radiocsirt.org/vuln/euvd-2026-367487 https://cve.radiocsirt.org/vuln/fkie_cve-2026-46170 <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>mptcp: pm: ADD_ADDR rtx: free sk if last</p> <p>When an ADD_ADDR is retransmitted, the sk is held in sk_reset_timer(), and released at the end.</p> <p>If at that moment, it was the last reference being held, the sk would not be freed. sock_put() should then be called instead of __sock_put().</p> <p>But that&#39;s not enough: if it is the last reference, sock_put() will call sk_free(), which will end up calling sk_stop_timer_sync() on the same timer, and waiting indefinitely to finish. So it is needed to mark that the timer is done at the end of the timer handler when it has not been rescheduled, not to call sk_stop_timer_sync() on &#34;itself&#34;.</p> <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>mptcp: pm: ADD_ADDR rtx: free sk if last</p> <p>When an ADD_ADDR is retransmitted, the sk is held in sk_reset_timer(), and released at the end.</p> <p>If at that moment, it was the last reference being held, the sk would not be freed. sock_put() should then be called instead of __sock_put().</p> <p>But that&#39;s not enough: if it is the last reference, sock_put() will call sk_free(), which will end up calling sk_stop_timer_sync() on the same timer, and waiting indefinitely to finish. So it is needed to mark that the timer is done at the end of the timer handler when it has not been rescheduled, not to call sk_stop_timer_sync() on &#34;itself&#34;.</p> https://cve.radiocsirt.org/vuln/fkie_cve-2026-46170 https://cve.radiocsirt.org/vuln/ghsa-xrpw-xx6g-3jg3 <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>mptcp: pm: ADD_ADDR rtx: free sk if last</p> <p>When an ADD_ADDR is retransmitted, the sk is held in sk_reset_timer(), and released at the end.</p> <p>If at that moment, it was the last reference being held, the sk would not be freed. sock_put() should then be called instead of __sock_put().</p> <p>But that&#39;s not enough: if it is the last reference, sock_put() will call sk_free(), which will end up calling sk_stop_timer_sync() on the same timer, and waiting indefinitely to finish. So it is needed to mark that the timer is done at the end of the timer handler when it has not been rescheduled, not to call sk_stop_timer_sync() on &#34;itself&#34;.</p> <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>mptcp: pm: ADD_ADDR rtx: free sk if last</p> <p>When an ADD_ADDR is retransmitted, the sk is held in sk_reset_timer(), and released at the end.</p> <p>If at that moment, it was the last reference being held, the sk would not be freed. sock_put() should then be called instead of __sock_put().</p> <p>But that&#39;s not enough: if it is the last reference, sock_put() will call sk_free(), which will end up calling sk_stop_timer_sync() on the same timer, and waiting indefinitely to finish. So it is needed to mark that the timer is done at the end of the timer handler when it has not been rescheduled, not to call sk_stop_timer_sync() on &#34;itself&#34;.</p> https://cve.radiocsirt.org/vuln/ghsa-xrpw-xx6g-3jg3 https://cve.radiocsirt.org/vuln/msrc_cve-2026-46170 msrc_CVE-2026-46170 https://cve.radiocsirt.org/vuln/msrc_cve-2026-46170 https://cve.radiocsirt.org/vuln/opensuse-su-2026:10954-1 <p>kernel-devel-7.0.11-1.1 on GA media</p> <p>kernel-devel-7.0.11-1.1 on GA media</p> https://cve.radiocsirt.org/vuln/opensuse-su-2026:10954-1 https://cve.radiocsirt.org/vuln/suse-su-2026:23066-1 <p>Security update for the Linux Kernel</p> <p>Security update for the Linux Kernel</p> https://cve.radiocsirt.org/vuln/suse-su-2026:23066-1 https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-46170 <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 201 more</p> <p>In the Linux kernel, the following vulnerability has been resolved: mptcp: pm: ADD_ADDR rtx: free sk if last When an ADD_ADDR is retransmitted, the sk is held in sk_reset_timer(), and released at the end. If at that moment, it was the last reference being held, the sk would not be freed. sock_put() should then be called instead of __sock_put(). But that&#39;s not enough: if it is the last reference, sock_put() will call sk_free(), which will end up calling sk_stop_timer_sync() on the same timer, and waiting indefinitely to finish. So it is needed to mark that the timer is done at the end of the timer handler when it has not been rescheduled, not to call sk_stop_timer_sync() on &#34;itself&#34;.</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 201 more</p> <p>In the Linux kernel, the following vulnerability has been resolved: mptcp: pm: ADD_ADDR rtx: free sk if last When an ADD_ADDR is retransmitted, the sk is held in sk_reset_timer(), and released at the end. If at that moment, it was the last reference being held, the sk would not be freed. sock_put() should then be called instead of __sock_put(). But that&#39;s not enough: if it is the last reference, sock_put() will call sk_free(), which will end up calling sk_stop_timer_sync() on the same timer, and waiting indefinitely to finish. So it is needed to mark that the timer is done at the end of the timer handler when it has not been rescheduled, not to call sk_stop_timer_sync() on &#34;itself&#34;.</p> https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-46170 https://cve.radiocsirt.org/vuln/wid-sec-w-2026-1700 <p>Ein Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um einen Denial of Service Angriff durchzuführen oder andere nicht näher spezifizierte Auswirkungen zu erzielen.</p> <p>Ein Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um einen Denial of Service Angriff durchzuführen oder andere nicht näher spezifizierte Auswirkungen zu erzielen.</p> https://cve.radiocsirt.org/vuln/wid-sec-w-2026-1700