https://cve.radiocsirt.org Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Sat, 03 Oct 2026 06:07:25 +0000 https://cve.radiocsirt.org/vuln/bdu:2026-14407 bdu:2026-14407 https://cve.radiocsirt.org/vuln/bdu:2026-14407 https://cve.radiocsirt.org/vuln/bell-cve-2026-53389 <p><strong>Affected:</strong> Alpaquita:25: linux-lts, Alpaquita:stream: linux-lts</p> <p><strong>Affected:</strong> Alpaquita:25: linux-lts, Alpaquita:stream: linux-lts</p> https://cve.radiocsirt.org/vuln/bell-cve-2026-53389 https://cve.radiocsirt.org/vuln/certfr-2026-avi-1162 certfr-2026-avi-1162 https://cve.radiocsirt.org/vuln/certfr-2026-avi-1162 https://cve.radiocsirt.org/vuln/euvd-2026-353101 EUVD-2026-353101 https://cve.radiocsirt.org/vuln/euvd-2026-353101 https://cve.radiocsirt.org/vuln/fkie_cve-2026-53389 <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>net/tcp-ao: fix use-after-free of key in del_async path</p> <p>In tcp_ao_delete_key(), the del_async path skips the current_key and rnext_key validity checks present in the synchronous path, assuming these pointers are always NULL on LISTEN sockets. However, if a key was added with set_current=1/set_rnext=1 while the socket was in CLOSE state, current_key and rnext_key will be non-NULL after listen() transitions the socket to LISTEN.</p> <p>When such a key is deleted with del_async=1, hlist_del_rcu() and call_rcu() free the key without clearing the dangling pointers. After the RCU grace period, getsockopt(TCP_AO_INFO) dereferences current_key-&gt;sndid and rnext_key-&gt;rcvid from freed slab memory.</p> <p>Clear current_key and rnext_key in the del_async path when they reference the key being deleted.</p> <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>net/tcp-ao: fix use-after-free of key in del_async path</p> <p>In tcp_ao_delete_key(), the del_async path skips the current_key and rnext_key validity checks present in the synchronous path, assuming these pointers are always NULL on LISTEN sockets. However, if a key was added with set_current=1/set_rnext=1 while the socket was in CLOSE state, current_key and rnext_key will be non-NULL after listen() transitions the socket to LISTEN.</p> <p>When such a key is deleted with del_async=1, hlist_del_rcu() and call_rcu() free the key without clearing the dangling pointers. After the RCU grace period, getsockopt(TCP_AO_INFO) dereferences current_key-&gt;sndid and rnext_key-&gt;rcvid from freed slab memory.</p> <p>Clear current_key and rnext_key in the del_async path when they reference the key being deleted.</p> https://cve.radiocsirt.org/vuln/fkie_cve-2026-53389 https://cve.radiocsirt.org/vuln/ghsa-x37v-hm75-xvf9 <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>net/tcp-ao: fix use-after-free of key in del_async path</p> <p>In tcp_ao_delete_key(), the del_async path skips the current_key and rnext_key validity checks present in the synchronous path, assuming these pointers are always NULL on LISTEN sockets. However, if a key was added with set_current=1/set_rnext=1 while the socket was in CLOSE state, current_key and rnext_key will be non-NULL after listen() transitions the socket to LISTEN.</p> <p>When such a key is deleted with del_async=1, hlist_del_rcu() and call_rcu() free the key without clearing the dangling pointers. After the RCU grace period, getsockopt(TCP_AO_INFO) dereferences current_key-&gt;sndid and rnext_key-&gt;rcvid from freed slab memory.</p> <p>Clear current_key and rnext_key in the del_async path when they reference the key being deleted.</p> <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>net/tcp-ao: fix use-after-free of key in del_async path</p> <p>In tcp_ao_delete_key(), the del_async path skips the current_key and rnext_key validity checks present in the synchronous path, assuming these pointers are always NULL on LISTEN sockets. However, if a key was added with set_current=1/set_rnext=1 while the socket was in CLOSE state, current_key and rnext_key will be non-NULL after listen() transitions the socket to LISTEN.</p> <p>When such a key is deleted with del_async=1, hlist_del_rcu() and call_rcu() free the key without clearing the dangling pointers. After the RCU grace period, getsockopt(TCP_AO_INFO) dereferences current_key-&gt;sndid and rnext_key-&gt;rcvid from freed slab memory.</p> <p>Clear current_key and rnext_key in the del_async path when they reference the key being deleted.</p> https://cve.radiocsirt.org/vuln/ghsa-x37v-hm75-xvf9 https://cve.radiocsirt.org/vuln/opensuse-su-2026:11339-1 <p>kernel-devel-7.1.4-1.1 on GA media</p> <p>kernel-devel-7.1.4-1.1 on GA media</p> https://cve.radiocsirt.org/vuln/opensuse-su-2026:11339-1 https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-53389 <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 154 more</p> <p>In the Linux kernel, the following vulnerability has been resolved: net/tcp-ao: fix use-after-free of key in del_async path In tcp_ao_delete_key(), the del_async path skips the current_key and rnext_key validity checks present in the synchronous path, assuming these pointers are always NULL on LISTEN sockets. However, if a key was added with set_current=1/set_rnext=1 while the socket was in CLOSE state, current_key and rnext_key will be non-NULL after listen() transitions the socket to LISTEN. When such a key is deleted with del_async=1, hlist_del_rcu() and call_rcu() free the key without clearing the dangling pointers. After the RCU grace period, getsockopt(TCP_AO_INFO) dereferences current_key-&gt;sndid and rnext_key-&gt;rcvid from freed slab memory. Clear current_key and rnext_key in the del_async path when they reference the key being deleted.</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 154 more</p> <p>In the Linux kernel, the following vulnerability has been resolved: net/tcp-ao: fix use-after-free of key in del_async path In tcp_ao_delete_key(), the del_async path skips the current_key and rnext_key validity checks present in the synchronous path, assuming these pointers are always NULL on LISTEN sockets. However, if a key was added with set_current=1/set_rnext=1 while the socket was in CLOSE state, current_key and rnext_key will be non-NULL after listen() transitions the socket to LISTEN. When such a key is deleted with del_async=1, hlist_del_rcu() and call_rcu() free the key without clearing the dangling pointers. After the RCU grace period, getsockopt(TCP_AO_INFO) dereferences current_key-&gt;sndid and rnext_key-&gt;rcvid from freed slab memory. Clear current_key and rnext_key in the del_async path when they reference the key being deleted.</p> https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-53389 https://cve.radiocsirt.org/vuln/wid-sec-w-2026-2403 <p>Ein Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um einen nicht näher spezifizierten Angriff durchzuführen, möglicherweise Sicherheitsmaßnahmen zu umgehen, einen Denial-of-Service-Zustand herbeizuführen oder vertrauliche Informationen offenzulegen.</p> <p>Ein Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um einen nicht näher spezifizierten Angriff durchzuführen, möglicherweise Sicherheitsmaßnahmen zu umgehen, einen Denial-of-Service-Zustand herbeizuführen oder vertrauliche Informationen offenzulegen.</p> https://cve.radiocsirt.org/vuln/wid-sec-w-2026-2403