Most recent entries from all

Most recent entries from all https://cve.radiocsirt.org Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Sat, 03 Oct 2026 10:40:22 +0000 bdu:2026-08802 https://cve.radiocsirt.org/vuln/bdu:2026-08802 bdu:2026-08802 https://cve.radiocsirt.org/vuln/bdu:2026-08802 BELL-CVE-2023-53478 https://cve.radiocsirt.org/vuln/bell-cve-2023-53478 <p><strong>Affected:</strong> Alpaquita:stream: linux-lts</p> <p><strong>Affected:</strong> Alpaquita:stream: linux-lts</p> https://cve.radiocsirt.org/vuln/bell-cve-2023-53478 certfr-2026-avi-0316 — De multiples vulnérabilités ont été découvertes dans les produits VMware. Elles permettent à un attaquant de provoquer… https://cve.radiocsirt.org/vuln/certfr-2026-avi-0316 certfr-2026-avi-0316 https://cve.radiocsirt.org/vuln/certfr-2026-avi-0316 EUVD-2026-345217 https://cve.radiocsirt.org/vuln/euvd-2026-345217 EUVD-2026-345217 https://cve.radiocsirt.org/vuln/euvd-2026-345217 fkie_cve-2023-53478 https://cve.radiocsirt.org/vuln/fkie_cve-2023-53478 <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>tracing/synthetic: Fix races on freeing last_cmd</p> <p>Currently, the "last_cmd" variable can be accessed by multiple processes asynchronously when multiple users manipulate synthetic_events node at the same time, it could lead to use-after-free or double-free.</p> <p>This patch add "lastcmd_mutex" to prevent "last_cmd" from being accessed asynchronously.</p> <p>================================================================</p> <p>It's easy to reproduce in the KASAN environment by running the two scripts below in different shells.</p> <p>script 1: while : do echo -n -e '\x88' > /sys/kernel/tracing/synthetic_events done</p> <p>script 2: while : do echo -n -e '\xb0' > /sys/kernel/tracing/synthetic_events done</p> <p>================================================================ double-free scenario:</p> <p>process A process B ------------------- --------------- 1.kstrdup last_cmd 2.free last_cmd 3.free last_cmd(double-free)</p> <p>================================================================ use-after-free scenario:</p> <p>process A process B ------------------- --------------- 1.kstrdup last_cmd 2.free last_cmd 3.tracing_log_err(use-after-free)</p> <p>================================================================</p> <p>Appendix 1. KASAN report…</p> <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>tracing/synthetic: Fix races on freeing last_cmd</p> <p>Currently, the "last_cmd" variable can be accessed by multiple processes asynchronously when multiple users manipulate synthetic_events node at the same time, it could lead to use-after-free or double-free.</p> <p>This patch add "lastcmd_mutex" to prevent "last_cmd" from being accessed asynchronously.</p> <p>================================================================</p> <p>It's easy to reproduce in the KASAN environment by running the two scripts below in different shells.</p> <p>script 1: while : do echo -n -e '\x88' > /sys/kernel/tracing/synthetic_events done</p> <p>script 2: while : do echo -n -e '\xb0' > /sys/kernel/tracing/synthetic_events done</p> <p>================================================================ double-free scenario:</p> <p>process A process B ------------------- --------------- 1.kstrdup last_cmd 2.free last_cmd 3.free last_cmd(double-free)</p> <p>================================================================ use-after-free scenario:</p> <p>process A process B ------------------- --------------- 1.kstrdup last_cmd 2.free last_cmd 3.tracing_log_err(use-after-free)</p> <p>================================================================</p> <p>Appendix 1. KASAN report…</p> https://cve.radiocsirt.org/vuln/fkie_cve-2023-53478 GHSA-q32w-2qjp-8m8q https://cve.radiocsirt.org/vuln/ghsa-q32w-2qjp-8m8q <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>tracing/synthetic: Fix races on freeing last_cmd</p> <p>Currently, the "last_cmd" variable can be accessed by multiple processes asynchronously when multiple users manipulate synthetic_events node at the same time, it could lead to use-after-free or double-free.</p> <p>This patch add "lastcmd_mutex" to prevent "last_cmd" from being accessed asynchronously.</p> <p>================================================================</p> <p>It's easy to reproduce in the KASAN environment by running the two scripts below in different shells.</p> <p>script 1: while : do echo -n -e '\x88' > /sys/kernel/tracing/synthetic_events done</p> <p>script 2: while : do echo -n -e '\xb0' > /sys/kernel/tracing/synthetic_events done</p> <p>================================================================ double-free scenario:</p> <p>process A process B ------------------- --------------- 1.kstrdup last_cmd 2.free last_cmd 3.free last_cmd(double-free)</p> <p>================================================================ use-after-free scenario:</p> <p>process A process B ------------------- --------------- 1.kstrdup last_cmd 2.free last_cmd 3.tracing_log_err(use-after-free)</p> <p>================================================================</p> <p>Appendix 1. KASAN report…</p> <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>tracing/synthetic: Fix races on freeing last_cmd</p> <p>Currently, the "last_cmd" variable can be accessed by multiple processes asynchronously when multiple users manipulate synthetic_events node at the same time, it could lead to use-after-free or double-free.</p> <p>This patch add "lastcmd_mutex" to prevent "last_cmd" from being accessed asynchronously.</p> <p>================================================================</p> <p>It's easy to reproduce in the KASAN environment by running the two scripts below in different shells.</p> <p>script 1: while : do echo -n -e '\x88' > /sys/kernel/tracing/synthetic_events done</p> <p>script 2: while : do echo -n -e '\xb0' > /sys/kernel/tracing/synthetic_events done</p> <p>================================================================ double-free scenario:</p> <p>process A process B ------------------- --------------- 1.kstrdup last_cmd 2.free last_cmd 3.free last_cmd(double-free)</p> <p>================================================================ use-after-free scenario:</p> <p>process A process B ------------------- --------------- 1.kstrdup last_cmd 2.free last_cmd 3.tracing_log_err(use-after-free)</p> <p>================================================================</p> <p>Appendix 1. KASAN report…</p> https://cve.radiocsirt.org/vuln/ghsa-q32w-2qjp-8m8q UBUNTU-CVE-2023-53478 https://cve.radiocsirt.org/vuln/ubuntu-cve-2023-53478 <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 78 more</p> <p>In the Linux kernel, the following vulnerability has been resolved: tracing/synthetic: Fix races on freeing last_cmd Currently, the "last_cmd" variable can be accessed by multiple processes asynchronously when multiple users manipulate synthetic_events node at the same time, it could lead to use-after-free or double-free. This patch add "lastcmd_mutex" to prevent "last_cmd" from being accessed asynchronously. ================================================================ It's easy to reproduce in the KASAN environment by running the two scripts below in different shells. script 1: while : do echo -n -e '\x88' > /sys/kernel/tracing/synthetic_events done script 2: while : do echo -n -e '\xb0' > /sys/kernel/tracing/synthetic_events done ================================================================ double-free scenario: process A process B ------------------- --------------- 1.kstrdup last_cmd 2.free last_cmd 3.free last_cmd(double-free) ================================================================ use-after-free scenario: process A process B ------------------- --------------- 1.kstrdup last_cmd 2.free last_cmd 3.tracing_log_err(use-after-free) ================================================================ Appendix 1. KASAN report double-free:…</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 78 more</p> <p>In the Linux kernel, the following vulnerability has been resolved: tracing/synthetic: Fix races on freeing last_cmd Currently, the "last_cmd" variable can be accessed by multiple processes asynchronously when multiple users manipulate synthetic_events node at the same time, it could lead to use-after-free or double-free. This patch add "lastcmd_mutex" to prevent "last_cmd" from being accessed asynchronously. ================================================================ It's easy to reproduce in the KASAN environment by running the two scripts below in different shells. script 1: while : do echo -n -e '\x88' > /sys/kernel/tracing/synthetic_events done script 2: while : do echo -n -e '\xb0' > /sys/kernel/tracing/synthetic_events done ================================================================ double-free scenario: process A process B ------------------- --------------- 1.kstrdup last_cmd 2.free last_cmd 3.free last_cmd(double-free) ================================================================ use-after-free scenario: process A process B ------------------- --------------- 1.kstrdup last_cmd 2.free last_cmd 3.tracing_log_err(use-after-free) ================================================================ Appendix 1. KASAN report double-free:…</p> https://cve.radiocsirt.org/vuln/ubuntu-cve-2023-53478 WID-SEC-W-2025-2187 — Linux Kernel: Mehrere Schwachstellen ermöglichen Denial of Service https://cve.radiocsirt.org/vuln/wid-sec-w-2025-2187 <p>Ein Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um einen Denial of Service Angriff durchzuführen und um nicht nähere beschriebene Effekte zu verursachen.</p> <p>Ein Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um einen Denial of Service Angriff durchzuführen und um nicht nähere beschriebene Effekte zu verursachen.</p> https://cve.radiocsirt.org/vuln/wid-sec-w-2025-2187