https://cve.radiocsirt.org Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Sat, 03 Oct 2026 18:17:53 +0000 https://cve.radiocsirt.org/vuln/bdu:2026-02415 bdu:2026-02415 https://cve.radiocsirt.org/vuln/bdu:2026-02415 https://cve.radiocsirt.org/vuln/certfr-2026-avi-0108 certfr-2026-avi-0108 https://cve.radiocsirt.org/vuln/certfr-2026-avi-0108 https://cve.radiocsirt.org/vuln/euvd-2026-320395 EUVD-2026-320395 https://cve.radiocsirt.org/vuln/euvd-2026-320395 https://cve.radiocsirt.org/vuln/fkie_cve-2022-50838 <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>net: stream: purge sk_error_queue in sk_stream_kill_queues()</p> <p>Changheon Lee reported TCP socket leaks, with a nice repro.</p> <p>It seems we leak TCP sockets with the following sequence:</p> <p>1) SOF_TIMESTAMPING_TX_ACK is enabled on the socket.</p> <p>Each ACK will cook an skb put in error queue, from __skb_tstamp_tx(). __skb_tstamp_tx() is using skb_clone(), unless SOF_TIMESTAMPING_OPT_TSONLY was also requested.</p> <p>2) If the application is also using MSG_ZEROCOPY, then we put in the error queue cloned skbs that had a struct ubuf_info attached to them.</p> <p>Whenever an struct ubuf_info is allocated, sock_zerocopy_alloc() does a sock_hold().</p> <p>As long as the cloned skbs are still in sk_error_queue, socket refcount is kept elevated.</p> <p>3) Application closes the socket, while error queue is not empty.</p> <p>Since tcp_close() no longer purges the socket error queue, we might end up with a TCP socket with at least one skb in error queue keeping the socket alive forever.</p> <p>This bug can be (ab)used to consume all kernel memory and freeze the host.</p> <p>We need to purge the error queue, with proper synchronization against concurrent writers.</p> <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>net: stream: purge sk_error_queue in sk_stream_kill_queues()</p> <p>Changheon Lee reported TCP socket leaks, with a nice repro.</p> <p>It seems we leak TCP sockets with the following sequence:</p> <p>1) SOF_TIMESTAMPING_TX_ACK is enabled on the socket.</p> <p>Each ACK will cook an skb put in error queue, from __skb_tstamp_tx(). __skb_tstamp_tx() is using skb_clone(), unless SOF_TIMESTAMPING_OPT_TSONLY was also requested.</p> <p>2) If the application is also using MSG_ZEROCOPY, then we put in the error queue cloned skbs that had a struct ubuf_info attached to them.</p> <p>Whenever an struct ubuf_info is allocated, sock_zerocopy_alloc() does a sock_hold().</p> <p>As long as the cloned skbs are still in sk_error_queue, socket refcount is kept elevated.</p> <p>3) Application closes the socket, while error queue is not empty.</p> <p>Since tcp_close() no longer purges the socket error queue, we might end up with a TCP socket with at least one skb in error queue keeping the socket alive forever.</p> <p>This bug can be (ab)used to consume all kernel memory and freeze the host.</p> <p>We need to purge the error queue, with proper synchronization against concurrent writers.</p> https://cve.radiocsirt.org/vuln/fkie_cve-2022-50838 https://cve.radiocsirt.org/vuln/ghsa-rgwv-j5f3-fh36 <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>net: stream: purge sk_error_queue in sk_stream_kill_queues()</p> <p>Changheon Lee reported TCP socket leaks, with a nice repro.</p> <p>It seems we leak TCP sockets with the following sequence:</p> <p>1) SOF_TIMESTAMPING_TX_ACK is enabled on the socket.</p> <p>Each ACK will cook an skb put in error queue, from __skb_tstamp_tx(). __skb_tstamp_tx() is using skb_clone(), unless SOF_TIMESTAMPING_OPT_TSONLY was also requested.</p> <p>2) If the application is also using MSG_ZEROCOPY, then we put in the error queue cloned skbs that had a struct ubuf_info attached to them.</p> <p>Whenever an struct ubuf_info is allocated, sock_zerocopy_alloc() does a sock_hold().</p> <p>As long as the cloned skbs are still in sk_error_queue, socket refcount is kept elevated.</p> <p>3) Application closes the socket, while error queue is not empty.</p> <p>Since tcp_close() no longer purges the socket error queue, we might end up with a TCP socket with at least one skb in error queue keeping the socket alive forever.</p> <p>This bug can be (ab)used to consume all kernel memory and freeze the host.</p> <p>We need to purge the error queue, with proper synchronization against concurrent writers.</p> <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>net: stream: purge sk_error_queue in sk_stream_kill_queues()</p> <p>Changheon Lee reported TCP socket leaks, with a nice repro.</p> <p>It seems we leak TCP sockets with the following sequence:</p> <p>1) SOF_TIMESTAMPING_TX_ACK is enabled on the socket.</p> <p>Each ACK will cook an skb put in error queue, from __skb_tstamp_tx(). __skb_tstamp_tx() is using skb_clone(), unless SOF_TIMESTAMPING_OPT_TSONLY was also requested.</p> <p>2) If the application is also using MSG_ZEROCOPY, then we put in the error queue cloned skbs that had a struct ubuf_info attached to them.</p> <p>Whenever an struct ubuf_info is allocated, sock_zerocopy_alloc() does a sock_hold().</p> <p>As long as the cloned skbs are still in sk_error_queue, socket refcount is kept elevated.</p> <p>3) Application closes the socket, while error queue is not empty.</p> <p>Since tcp_close() no longer purges the socket error queue, we might end up with a TCP socket with at least one skb in error queue keeping the socket alive forever.</p> <p>This bug can be (ab)used to consume all kernel memory and freeze the host.</p> <p>We need to purge the error queue, with proper synchronization against concurrent writers.</p> https://cve.radiocsirt.org/vuln/ghsa-rgwv-j5f3-fh36 https://cve.radiocsirt.org/vuln/suse-su-2026:0263-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:0263-1 https://cve.radiocsirt.org/vuln/ubuntu-cve-2022-50838 <p><strong>Affected:</strong> Ubuntu:Pro:14.04:LTS: linux-azure, Ubuntu:Pro:16.04:LTS: linux-aws-hwe, Ubuntu:Pro:16.04:LTS: linux-azure, Ubuntu:Pro:16.04:LTS: linux-gcp, Ubuntu:Pro:16.04:LTS: linux-hwe, Ubuntu:Pro:16.04:LTS: linux-oracle, Ubuntu:16.04:LTS: linux-hwe-edge, Ubuntu:18.04:LTS: linux, Ubuntu:18.04:LTS: linux-aws, Ubuntu:18.04:LTS: linux-aws-5.4 and 143 more</p> <p>In the Linux kernel, the following vulnerability has been resolved: net: stream: purge sk_error_queue in sk_stream_kill_queues() Changheon Lee reported TCP socket leaks, with a nice repro. It seems we leak TCP sockets with the following sequence: 1) SOF_TIMESTAMPING_TX_ACK is enabled on the socket. Each ACK will cook an skb put in error queue, from __skb_tstamp_tx(). __skb_tstamp_tx() is using skb_clone(), unless SOF_TIMESTAMPING_OPT_TSONLY was also requested. 2) If the application is also using MSG_ZEROCOPY, then we put in the error queue cloned skbs that had a struct ubuf_info attached to them. Whenever an struct ubuf_info is allocated, sock_zerocopy_alloc() does a sock_hold(). As long as the cloned skbs are still in sk_error_queue, socket refcount is kept elevated. 3) Application closes the socket, while error queue is not empty. Since tcp_close() no longer purges the socket error queue, we might end up with a TCP socket with at least one skb in error queue keeping the socket alive forever. This bug can be (ab)used to consume all kernel memory and freeze the host. We need to purge the error queue, with proper synchronization against concurrent writers.</p> <p><strong>Affected:</strong> Ubuntu:Pro:14.04:LTS: linux-azure, Ubuntu:Pro:16.04:LTS: linux-aws-hwe, Ubuntu:Pro:16.04:LTS: linux-azure, Ubuntu:Pro:16.04:LTS: linux-gcp, Ubuntu:Pro:16.04:LTS: linux-hwe, Ubuntu:Pro:16.04:LTS: linux-oracle, Ubuntu:16.04:LTS: linux-hwe-edge, Ubuntu:18.04:LTS: linux, Ubuntu:18.04:LTS: linux-aws, Ubuntu:18.04:LTS: linux-aws-5.4 and 143 more</p> <p>In the Linux kernel, the following vulnerability has been resolved: net: stream: purge sk_error_queue in sk_stream_kill_queues() Changheon Lee reported TCP socket leaks, with a nice repro. It seems we leak TCP sockets with the following sequence: 1) SOF_TIMESTAMPING_TX_ACK is enabled on the socket. Each ACK will cook an skb put in error queue, from __skb_tstamp_tx(). __skb_tstamp_tx() is using skb_clone(), unless SOF_TIMESTAMPING_OPT_TSONLY was also requested. 2) If the application is also using MSG_ZEROCOPY, then we put in the error queue cloned skbs that had a struct ubuf_info attached to them. Whenever an struct ubuf_info is allocated, sock_zerocopy_alloc() does a sock_hold(). As long as the cloned skbs are still in sk_error_queue, socket refcount is kept elevated. 3) Application closes the socket, while error queue is not empty. Since tcp_close() no longer purges the socket error queue, we might end up with a TCP socket with at least one skb in error queue keeping the socket alive forever. This bug can be (ab)used to consume all kernel memory and freeze the host. We need to purge the error queue, with proper synchronization against concurrent writers.</p> https://cve.radiocsirt.org/vuln/ubuntu-cve-2022-50838 https://cve.radiocsirt.org/vuln/wid-sec-w-2025-2941 <p>Ein Angreifer kann diese Schwachstellen ausnutzen, um nicht näher spezifizierte Angriffe durchzuführen, die möglicherweise zu Denial‑of‑Service, Speicherbeschädigung oder weiteren nicht definierten Auswirkungen führen.</p> <p>Ein Angreifer kann diese Schwachstellen ausnutzen, um nicht näher spezifizierte Angriffe durchzuführen, die möglicherweise zu Denial‑of‑Service, Speicherbeschädigung oder weiteren nicht definierten Auswirkungen führen.</p> https://cve.radiocsirt.org/vuln/wid-sec-w-2025-2941