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:15:15 +0000 https://cve.radiocsirt.org/vuln/bdu:2025-13892 bdu:2025-13892 https://cve.radiocsirt.org/vuln/bdu:2025-13892 https://cve.radiocsirt.org/vuln/bell-cve-2025-39873 <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-2025-39873 https://cve.radiocsirt.org/vuln/certfr-2025-avi-0894 certfr-2025-avi-0894 https://cve.radiocsirt.org/vuln/certfr-2025-avi-0894 https://cve.radiocsirt.org/vuln/euvd-2026-347237 EUVD-2026-347237 https://cve.radiocsirt.org/vuln/euvd-2026-347237 https://cve.radiocsirt.org/vuln/fkie_cve-2025-39873 <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>can: xilinx_can: xcan_write_frame(): fix use-after-free of transmitted SKB</p> <p>can_put_echo_skb() takes ownership of the SKB and it may be freed during or after the call.</p> <p>However, xilinx_can xcan_write_frame() keeps using SKB after the call.</p> <p>Fix that by only calling can_put_echo_skb() after the code is done touching the SKB.</p> <p>The tx_lock is held for the entire xcan_write_frame() execution and also on the can_get_echo_skb() side so the order of operations does not matter.</p> <p>An earlier fix commit 3d3c817c3a40 (&#34;can: xilinx_can: Fix usage of skb memory&#34;) did not move the can_put_echo_skb() call far enough.</p> <p>[mkl: add &#34;commit&#34; in front of sha1 in patch description] [mkl: fix indention]</p> <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>can: xilinx_can: xcan_write_frame(): fix use-after-free of transmitted SKB</p> <p>can_put_echo_skb() takes ownership of the SKB and it may be freed during or after the call.</p> <p>However, xilinx_can xcan_write_frame() keeps using SKB after the call.</p> <p>Fix that by only calling can_put_echo_skb() after the code is done touching the SKB.</p> <p>The tx_lock is held for the entire xcan_write_frame() execution and also on the can_get_echo_skb() side so the order of operations does not matter.</p> <p>An earlier fix commit 3d3c817c3a40 (&#34;can: xilinx_can: Fix usage of skb memory&#34;) did not move the can_put_echo_skb() call far enough.</p> <p>[mkl: add &#34;commit&#34; in front of sha1 in patch description] [mkl: fix indention]</p> https://cve.radiocsirt.org/vuln/fkie_cve-2025-39873 https://cve.radiocsirt.org/vuln/ghsa-9mp7-jx47-xv3h <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>can: xilinx_can: xcan_write_frame(): fix use-after-free of transmitted SKB</p> <p>can_put_echo_skb() takes ownership of the SKB and it may be freed during or after the call.</p> <p>However, xilinx_can xcan_write_frame() keeps using SKB after the call.</p> <p>Fix that by only calling can_put_echo_skb() after the code is done touching the SKB.</p> <p>The tx_lock is held for the entire xcan_write_frame() execution and also on the can_get_echo_skb() side so the order of operations does not matter.</p> <p>An earlier fix commit 3d3c817c3a40 (&#34;can: xilinx_can: Fix usage of skb memory&#34;) did not move the can_put_echo_skb() call far enough.</p> <p>[mkl: add &#34;commit&#34; in front of sha1 in patch description] [mkl: fix indention]</p> <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>can: xilinx_can: xcan_write_frame(): fix use-after-free of transmitted SKB</p> <p>can_put_echo_skb() takes ownership of the SKB and it may be freed during or after the call.</p> <p>However, xilinx_can xcan_write_frame() keeps using SKB after the call.</p> <p>Fix that by only calling can_put_echo_skb() after the code is done touching the SKB.</p> <p>The tx_lock is held for the entire xcan_write_frame() execution and also on the can_get_echo_skb() side so the order of operations does not matter.</p> <p>An earlier fix commit 3d3c817c3a40 (&#34;can: xilinx_can: Fix usage of skb memory&#34;) did not move the can_put_echo_skb() call far enough.</p> <p>[mkl: add &#34;commit&#34; in front of sha1 in patch description] [mkl: fix indention]</p> https://cve.radiocsirt.org/vuln/ghsa-9mp7-jx47-xv3h https://cve.radiocsirt.org/vuln/msrc_cve-2025-39873 msrc_CVE-2025-39873 https://cve.radiocsirt.org/vuln/msrc_cve-2025-39873 https://cve.radiocsirt.org/vuln/opensuse-su-2025:20081-1 <p>Security update for the Linux Kernel</p> <p>Security update for the Linux Kernel</p> https://cve.radiocsirt.org/vuln/opensuse-su-2025:20081-1 https://cve.radiocsirt.org/vuln/suse-su-2025:03600-1 <p>Security update for the Linux Kernel</p> <p>Security update for the Linux Kernel</p> https://cve.radiocsirt.org/vuln/suse-su-2025:03600-1 https://cve.radiocsirt.org/vuln/ubuntu-cve-2025-39873 <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:Pro:18.04:LTS: linux-aws-5.4, Ubuntu:18.04:LTS: linux-azure, Ubuntu:18.04:LTS: linux-azure-5.3, Ubuntu:Pro:18.04:LTS: linux-azure-5.4, Ubuntu:18.04:LTS: linux-azure-edge, Ubuntu:18.04:LTS: linux-gcp, Ubuntu:18.04:LTS: linux-gcp-5.3 and 188 more</p> <p>In the Linux kernel, the following vulnerability has been resolved: can: xilinx_can: xcan_write_frame(): fix use-after-free of transmitted SKB can_put_echo_skb() takes ownership of the SKB and it may be freed during or after the call. However, xilinx_can xcan_write_frame() keeps using SKB after the call. Fix that by only calling can_put_echo_skb() after the code is done touching the SKB. The tx_lock is held for the entire xcan_write_frame() execution and also on the can_get_echo_skb() side so the order of operations does not matter. An earlier fix commit 3d3c817c3a40 (&#34;can: xilinx_can: Fix usage of skb memory&#34;) did not move the can_put_echo_skb() call far enough. [mkl: add &#34;commit&#34; in front of sha1 in patch description] [mkl: fix indention]</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:Pro:18.04:LTS: linux-aws-5.4, Ubuntu:18.04:LTS: linux-azure, Ubuntu:18.04:LTS: linux-azure-5.3, Ubuntu:Pro:18.04:LTS: linux-azure-5.4, Ubuntu:18.04:LTS: linux-azure-edge, Ubuntu:18.04:LTS: linux-gcp, Ubuntu:18.04:LTS: linux-gcp-5.3 and 188 more</p> <p>In the Linux kernel, the following vulnerability has been resolved: can: xilinx_can: xcan_write_frame(): fix use-after-free of transmitted SKB can_put_echo_skb() takes ownership of the SKB and it may be freed during or after the call. However, xilinx_can xcan_write_frame() keeps using SKB after the call. Fix that by only calling can_put_echo_skb() after the code is done touching the SKB. The tx_lock is held for the entire xcan_write_frame() execution and also on the can_get_echo_skb() side so the order of operations does not matter. An earlier fix commit 3d3c817c3a40 (&#34;can: xilinx_can: Fix usage of skb memory&#34;) did not move the can_put_echo_skb() call far enough. [mkl: add &#34;commit&#34; in front of sha1 in patch description] [mkl: fix indention]</p> https://cve.radiocsirt.org/vuln/ubuntu-cve-2025-39873 https://cve.radiocsirt.org/vuln/wid-sec-w-2025-2107 <p>Ein Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um einen Denial of Service Angriff durchzuführen oder nicht näher beschriebene Auswirkungen zu erzielen.</p> <p>Ein Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um einen Denial of Service Angriff durchzuführen oder nicht näher beschriebene Auswirkungen zu erzielen.</p> https://cve.radiocsirt.org/vuln/wid-sec-w-2025-2107