<?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://vulnerability.circl.lu</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>Mon, 28 Sep 2026 18:31:57 +0000</lastBuildDate>
    <item>
      <title>CVE-2023-54211 — tracing: Fix warning in trace_buffered_event_disable()</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2023-54211</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Linux&lt;/p&gt;
&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;&lt;strong&gt;Affected:&lt;/strong&gt; Linux&lt;/p&gt;
&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://vulnerability.circl.lu/vuln/cve-2023-54211</guid>
    </item>
  </channel>
</rss>
