https://cve.radiocsirt.org/rss/recent/all/10 Most recent entries from all 2026-10-02T17:29:56.487385+00:00 Vulnerability-Lookup csirt@opendfir.org python-feedgen Contains only the most 10 recent entries. https://cve.radiocsirt.org/vuln/bdu:2025-13892 bdu:2025-13892 2026-10-02T17:29:57.209689+00:00 bdu:2025-13892 https://cve.radiocsirt.org/vuln/bell-cve-2025-39873 BELL-CVE-2025-39873 2026-10-02T17:29:57.209750+00:00

Affected: Alpaquita:23: linux-lts, Alpaquita:25: linux-lts, Alpaquita:stream: linux-lts

 https://cve.radiocsirt.org/vuln/certfr-2025-avi-0894 certfr-2025-avi-0894 — De multiples vulnérabilités ont été découvertes dans le noyau Linux de Debian LTS. Certaines d'entre elles permettent à… 2026-10-02T17:29:57.209788+00:00 certfr-2025-avi-0894 https://cve.radiocsirt.org/vuln/euvd-2026-347237 EUVD-2026-347237 2026-10-02T17:29:57.209807+00:00 EUVD-2026-347237 https://cve.radiocsirt.org/vuln/fkie_cve-2025-39873 fkie_cve-2025-39873 2026-10-02T17:29:57.209820+00:00

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 ("can: xilinx_can: Fix usage of skb memory") did not move the can_put_echo_skb() call far enough.

[mkl: add "commit" in front of sha1 in patch description] [mkl: fix indention]

 https://cve.radiocsirt.org/vuln/ghsa-9mp7-jx47-xv3h GHSA-9mp7-jx47-xv3h 2026-10-02T17:29:57.209854+00:00

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 ("can: xilinx_can: Fix usage of skb memory") did not move the can_put_echo_skb() call far enough.

[mkl: add "commit" in front of sha1 in patch description] [mkl: fix indention]

 https://cve.radiocsirt.org/vuln/msrc_cve-2025-39873 msrc_CVE-2025-39873 — can: xilinx_can: xcan_write_frame(): fix use-after-free of transmitted SKB 2026-10-02T17:29:57.209877+00:00 msrc_CVE-2025-39873 https://cve.radiocsirt.org/vuln/opensuse-su-2025:20081-1 openSUSE-SU-2025:20081-1 — Security update for the Linux Kernel 2026-10-02T17:29:57.209895+00:00

Security update for the Linux Kernel

 https://cve.radiocsirt.org/vuln/suse-su-2025:03600-1 SUSE-SU-2025:03600-1 — Security update for the Linux Kernel 2026-10-02T17:29:57.210228+00:00

Security update for the Linux Kernel

 https://cve.radiocsirt.org/vuln/ubuntu-cve-2025-39873 UBUNTU-CVE-2025-39873 2026-10-02T17:29:57.210454+00:00

Affected: 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

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 ("can: xilinx_can: Fix usage of skb memory") did not move the can_put_echo_skb() call far enough. [mkl: add "commit" in front of sha1 in patch description] [mkl: fix indention]

 https://cve.radiocsirt.org/vuln/wid-sec-w-2025-2107 WID-SEC-W-2025-2107 — Linux Kernel: Mehrere Schwachstellen 2026-10-02T17:29:57.210692+00:00

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.