<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<rss xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/" version="2.0">
  <channel>
    <title>Most recent entries from all</title>
    <link>https://cve.radiocsirt.org</link>
    <description>Contains only the most 10 recent entries.</description>
    <docs>http://www.rssboard.org/rss-specification</docs>
    <generator>python-feedgen</generator>
    <language>en</language>
    <lastBuildDate>Sun, 04 Oct 2026 07:43:42 +0000</lastBuildDate>
    <item>
      <title>bdu:2026-13767</title>
      <link>https://cve.radiocsirt.org/vuln/bdu:2026-13767</link>
      <description>bdu:2026-13767</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/bdu:2026-13767</guid>
    </item>
    <item>
      <title>BELL-CVE-2023-54211</title>
      <link>https://cve.radiocsirt.org/vuln/bell-cve-2023-54211</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Alpaquita:23: linux-lts, Alpaquita:stream: linux-lts&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Alpaquita:23: linux-lts, Alpaquita:stream: linux-lts&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/bell-cve-2023-54211</guid>
    </item>
    <item>
      <title>certfr-2026-avi-0108 — De multiples vulnérabilités ont été découvertes dans le noyau Linux de SUSE. Certaines d'entre elles permettent à un at…</title>
      <link>https://cve.radiocsirt.org/vuln/certfr-2026-avi-0108</link>
      <description>certfr-2026-avi-0108</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/certfr-2026-avi-0108</guid>
    </item>
    <item>
      <title>EUVD-2026-312425</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-312425</link>
      <description>EUVD-2026-312425</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-312425</guid>
    </item>
    <item>
      <title>fkie_cve-2023-54211</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2023-54211</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;tracing: Fix warning in trace_buffered_event_disable()&lt;/p&gt;
&lt;p&gt;Warning happened in trace_buffered_event_disable() at
  WARN_ON_ONCE(!trace_buffered_event_ref)&lt;/p&gt;
&lt;p&gt;Call Trace:
   ? __warn+0xa5/0x1b0
   ? trace_buffered_event_disable+0x189/0x1b0
   __ftrace_event_enable_disable+0x19e/0x3e0
   free_probe_data+0x3b/0xa0
   unregister_ftrace_function_probe_func+0x6b8/0x800
   event_enable_func+0x2f0/0x3d0
   ftrace_process_regex.isra.0+0x12d/0x1b0
   ftrace_filter_write+0xe6/0x140
   vfs_write+0x1c9/0x6f0
   [...]&lt;/p&gt;
&lt;p&gt;The cause of the warning is in __ftrace_event_enable_disable(),
trace_buffered_event_enable() was called once while
trace_buffered_event_disable() was called twice.
Reproduction script show as below, for analysis, see the comments:
 ```
 #!/bin/bash&lt;/p&gt;
&lt;p&gt;cd /sys/kernel/tracing/&lt;/p&gt;
&lt;p&gt;# 1. Register a &amp;#39;disable_event&amp;#39; command, then:
 #    1) SOFT_DISABLED_BIT was set;
 #    2) trace_buffered_event_enable() was called first time;
 echo &amp;#39;cmdline_proc_show:disable_event:initcall:initcall_finish&amp;#39; &amp;gt; \
     set_ftrace_filter&lt;/p&gt;
&lt;p&gt;# 2. Enable the event registered, then:
 #    1) SOFT_DISABLED_BIT was cleared;
 #    2) trace_buffered_event_disable() was called first time;
 echo 1 &amp;gt; events/initcall/initcall_finish/enable&lt;/p&gt;
&lt;p&gt;# 3. Try to call into cmdline_proc_show(), then SOFT_DISABLED_BIT was
 #    set again!!!
 cat /proc/cmdline&lt;/p&gt;
&lt;p&gt;# 4. Unregister the &amp;#39;disable_event&amp;#39; command, then:
 #    1) SOFT_DISABLED_BIT was cleared again;
 #…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;tracing: Fix warning in trace_buffered_event_disable()&lt;/p&gt;
&lt;p&gt;Warning happened in trace_buffered_event_disable() at
  WARN_ON_ONCE(!trace_buffered_event_ref)&lt;/p&gt;
&lt;p&gt;Call Trace:
   ? __warn+0xa5/0x1b0
   ? trace_buffered_event_disable+0x189/0x1b0
   __ftrace_event_enable_disable+0x19e/0x3e0
   free_probe_data+0x3b/0xa0
   unregister_ftrace_function_probe_func+0x6b8/0x800
   event_enable_func+0x2f0/0x3d0
   ftrace_process_regex.isra.0+0x12d/0x1b0
   ftrace_filter_write+0xe6/0x140
   vfs_write+0x1c9/0x6f0
   [...]&lt;/p&gt;
&lt;p&gt;The cause of the warning is in __ftrace_event_enable_disable(),
trace_buffered_event_enable() was called once while
trace_buffered_event_disable() was called twice.
Reproduction script show as below, for analysis, see the comments:
 ```
 #!/bin/bash&lt;/p&gt;
&lt;p&gt;cd /sys/kernel/tracing/&lt;/p&gt;
&lt;p&gt;# 1. Register a &amp;#39;disable_event&amp;#39; command, then:
 #    1) SOFT_DISABLED_BIT was set;
 #    2) trace_buffered_event_enable() was called first time;
 echo &amp;#39;cmdline_proc_show:disable_event:initcall:initcall_finish&amp;#39; &amp;gt; \
     set_ftrace_filter&lt;/p&gt;
&lt;p&gt;# 2. Enable the event registered, then:
 #    1) SOFT_DISABLED_BIT was cleared;
 #    2) trace_buffered_event_disable() was called first time;
 echo 1 &amp;gt; events/initcall/initcall_finish/enable&lt;/p&gt;
&lt;p&gt;# 3. Try to call into cmdline_proc_show(), then SOFT_DISABLED_BIT was
 #    set again!!!
 cat /proc/cmdline&lt;/p&gt;
&lt;p&gt;# 4. Unregister the &amp;#39;disable_event&amp;#39; command, then:
 #    1) SOFT_DISABLED_BIT was cleared again;
 #…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2023-54211</guid>
    </item>
    <item>
      <title>GHSA-m579-rv75-wvgq</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-m579-rv75-wvgq</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;tracing: Fix warning in trace_buffered_event_disable()&lt;/p&gt;
&lt;p&gt;Warning happened in trace_buffered_event_disable() at
  WARN_ON_ONCE(!trace_buffered_event_ref)&lt;/p&gt;
&lt;p&gt;Call Trace:
   ? __warn+0xa5/0x1b0
   ? trace_buffered_event_disable+0x189/0x1b0
   __ftrace_event_enable_disable+0x19e/0x3e0
   free_probe_data+0x3b/0xa0
   unregister_ftrace_function_probe_func+0x6b8/0x800
   event_enable_func+0x2f0/0x3d0
   ftrace_process_regex.isra.0+0x12d/0x1b0
   ftrace_filter_write+0xe6/0x140
   vfs_write+0x1c9/0x6f0
   [...]&lt;/p&gt;
&lt;p&gt;The cause of the warning is in __ftrace_event_enable_disable(),
trace_buffered_event_enable() was called once while
trace_buffered_event_disable() was called twice.
Reproduction script show as below, for analysis, see the comments:
 ```
 #!/bin/bash&lt;/p&gt;
&lt;p&gt;cd /sys/kernel/tracing/&lt;/p&gt;
&lt;p&gt;# 1. Register a &amp;#39;disable_event&amp;#39; command, then:
 #    1) SOFT_DISABLED_BIT was set;
 #    2) trace_buffered_event_enable() was called first time;
 echo &amp;#39;cmdline_proc_show:disable_event:initcall:initcall_finish&amp;#39; &amp;gt; \
     set_ftrace_filter&lt;/p&gt;
&lt;p&gt;# 2. Enable the event registered, then:
 #    1) SOFT_DISABLED_BIT was cleared;
 #    2) trace_buffered_event_disable() was called first time;
 echo 1 &amp;gt; events/initcall/initcall_finish/enable&lt;/p&gt;
&lt;p&gt;# 3. Try to call into cmdline_proc_show(), then SOFT_DISABLED_BIT was
 #    set again!!!
 cat /proc/cmdline&lt;/p&gt;
&lt;p&gt;# 4. Unregister the &amp;#39;disable_event&amp;#39; command, then:
 #    1) SOFT_DISABLED_BIT was cleared again;
 #…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;tracing: Fix warning in trace_buffered_event_disable()&lt;/p&gt;
&lt;p&gt;Warning happened in trace_buffered_event_disable() at
  WARN_ON_ONCE(!trace_buffered_event_ref)&lt;/p&gt;
&lt;p&gt;Call Trace:
   ? __warn+0xa5/0x1b0
   ? trace_buffered_event_disable+0x189/0x1b0
   __ftrace_event_enable_disable+0x19e/0x3e0
   free_probe_data+0x3b/0xa0
   unregister_ftrace_function_probe_func+0x6b8/0x800
   event_enable_func+0x2f0/0x3d0
   ftrace_process_regex.isra.0+0x12d/0x1b0
   ftrace_filter_write+0xe6/0x140
   vfs_write+0x1c9/0x6f0
   [...]&lt;/p&gt;
&lt;p&gt;The cause of the warning is in __ftrace_event_enable_disable(),
trace_buffered_event_enable() was called once while
trace_buffered_event_disable() was called twice.
Reproduction script show as below, for analysis, see the comments:
 ```
 #!/bin/bash&lt;/p&gt;
&lt;p&gt;cd /sys/kernel/tracing/&lt;/p&gt;
&lt;p&gt;# 1. Register a &amp;#39;disable_event&amp;#39; command, then:
 #    1) SOFT_DISABLED_BIT was set;
 #    2) trace_buffered_event_enable() was called first time;
 echo &amp;#39;cmdline_proc_show:disable_event:initcall:initcall_finish&amp;#39; &amp;gt; \
     set_ftrace_filter&lt;/p&gt;
&lt;p&gt;# 2. Enable the event registered, then:
 #    1) SOFT_DISABLED_BIT was cleared;
 #    2) trace_buffered_event_disable() was called first time;
 echo 1 &amp;gt; events/initcall/initcall_finish/enable&lt;/p&gt;
&lt;p&gt;# 3. Try to call into cmdline_proc_show(), then SOFT_DISABLED_BIT was
 #    set again!!!
 cat /proc/cmdline&lt;/p&gt;
&lt;p&gt;# 4. Unregister the &amp;#39;disable_event&amp;#39; command, then:
 #    1) SOFT_DISABLED_BIT was cleared again;
 #…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-m579-rv75-wvgq</guid>
    </item>
    <item>
      <title>SUSE-SU-2026:0263-1 — Security update for the Linux Kernel</title>
      <link>https://cve.radiocsirt.org/vuln/suse-su-2026:0263-1</link>
      <description>&lt;p&gt;Security update for the Linux Kernel&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Security update for the Linux Kernel&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/suse-su-2026:0263-1</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2023-54211</title>
      <link>https://cve.radiocsirt.org/vuln/ubuntu-cve-2023-54211</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; 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:16.04:LTS: linux-hwe-edge, Ubuntu:Pro:16.04:LTS: linux-oracle, Ubuntu:Pro:18.04:LTS: linux, Ubuntu:Pro:18.04:LTS: linux-aws, Ubuntu:18.04:LTS: linux-aws-5.0 and 156 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: tracing: Fix warning in trace_buffered_event_disable() Warning happened in trace_buffered_event_disable() at   WARN_ON_ONCE(!trace_buffered_event_ref)   Call Trace:    ? __warn+0xa5/0x1b0    ? trace_buffered_event_disable+0x189/0x1b0    __ftrace_event_enable_disable+0x19e/0x3e0    free_probe_data+0x3b/0xa0    unregister_ftrace_function_probe_func+0x6b8/0x800    event_enable_func+0x2f0/0x3d0    ftrace_process_regex.isra.0+0x12d/0x1b0    ftrace_filter_write+0xe6/0x140    vfs_write+0x1c9/0x6f0    [...] The cause of the warning is in __ftrace_event_enable_disable(), trace_buffered_event_enable() was called once while trace_buffered_event_disable() was called twice. Reproduction script show as below, for analysis, see the comments:  ```  #!/bin/bash  cd /sys/kernel/tracing/  # 1. Register a &amp;#39;disable_event&amp;#39; command, then:  #    1) SOFT_DISABLED_BIT was set;  #    2) trace_buffered_event_enable() was called first time;  echo &amp;#39;cmdline_proc_show:disable_event:initcall:initcall_finish&amp;#39; &amp;gt; \      set_ftrace_filter  # 2. Enable the event registered, then:  #    1) SOFT_DISABLED_BIT was cleared;  #    2) trace_buffered_event_disable() was called first time;  echo 1 &amp;gt; events/initcall/initcall_finish/enable  # 3. Try to call into cmdline_proc_show(), then SOFT_DISABLED_BIT was  #    set again!!!  cat /proc/cmdline  # 4. Unregister the &amp;#39;disable_event&amp;#39; command, then:  #    1) SOFT_DISABLED_BIT was cleared again;  #    2) trac…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; 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:16.04:LTS: linux-hwe-edge, Ubuntu:Pro:16.04:LTS: linux-oracle, Ubuntu:Pro:18.04:LTS: linux, Ubuntu:Pro:18.04:LTS: linux-aws, Ubuntu:18.04:LTS: linux-aws-5.0 and 156 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: tracing: Fix warning in trace_buffered_event_disable() Warning happened in trace_buffered_event_disable() at   WARN_ON_ONCE(!trace_buffered_event_ref)   Call Trace:    ? __warn+0xa5/0x1b0    ? trace_buffered_event_disable+0x189/0x1b0    __ftrace_event_enable_disable+0x19e/0x3e0    free_probe_data+0x3b/0xa0    unregister_ftrace_function_probe_func+0x6b8/0x800    event_enable_func+0x2f0/0x3d0    ftrace_process_regex.isra.0+0x12d/0x1b0    ftrace_filter_write+0xe6/0x140    vfs_write+0x1c9/0x6f0    [...] The cause of the warning is in __ftrace_event_enable_disable(), trace_buffered_event_enable() was called once while trace_buffered_event_disable() was called twice. Reproduction script show as below, for analysis, see the comments:  ```  #!/bin/bash  cd /sys/kernel/tracing/  # 1. Register a &amp;#39;disable_event&amp;#39; command, then:  #    1) SOFT_DISABLED_BIT was set;  #    2) trace_buffered_event_enable() was called first time;  echo &amp;#39;cmdline_proc_show:disable_event:initcall:initcall_finish&amp;#39; &amp;gt; \      set_ftrace_filter  # 2. Enable the event registered, then:  #    1) SOFT_DISABLED_BIT was cleared;  #    2) trace_buffered_event_disable() was called first time;  echo 1 &amp;gt; events/initcall/initcall_finish/enable  # 3. Try to call into cmdline_proc_show(), then SOFT_DISABLED_BIT was  #    set again!!!  cat /proc/cmdline  # 4. Unregister the &amp;#39;disable_event&amp;#39; command, then:  #    1) SOFT_DISABLED_BIT was cleared again;  #    2) trac…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ubuntu-cve-2023-54211</guid>
    </item>
    <item>
      <title>WID-SEC-W-2025-2941 — Linux Kernel: Mehrere Schwachstellen ermöglichen Denial of Service</title>
      <link>https://cve.radiocsirt.org/vuln/wid-sec-w-2025-2941</link>
      <description>&lt;p&gt;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.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;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.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/wid-sec-w-2025-2941</guid>
    </item>
  </channel>
</rss>
