<?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://db.gcve.eu</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>Wed, 30 Sep 2026 21:16:13 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-97443 — perf/ftrace: Fix WARNING in __unregister_ftrace_function</title>
      <link>https://db.gcve.eu/vuln/cve-2026-97443</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;perf/ftrace: Fix WARNING in __unregister_ftrace_function&lt;/p&gt;
&lt;p&gt;perf_ftrace_function_unregister() unconditionally calls
unregister_ftrace_function() without checking whether the ftrace_ops
was ever successfully registered. This triggers a WARN_ON in
__unregister_ftrace_function() when the ops doesn&amp;#39;t have
FTRACE_OPS_FL_ENABLED set.&lt;/p&gt;
&lt;p&gt;This can happen during perf_event_alloc() error cleanup when
perf_trace_destroy() is called via __free_event() on an event whose
ftrace_ops registration failed or was already torn down by
perf_try_init_event()&amp;#39;s err_destroy path.&lt;/p&gt;
&lt;p&gt;The call path is:
  perf_event_alloc() error cleanup
    -&amp;gt; __free_event()
      -&amp;gt; event-&amp;gt;destroy() [tp_perf_event_destroy]
        -&amp;gt; perf_trace_destroy()
          -&amp;gt; perf_trace_event_close()
            -&amp;gt; TRACE_REG_PERF_CLOSE
              -&amp;gt; perf_ftrace_function_unregister()
                -&amp;gt; unregister_ftrace_function()
                  -&amp;gt; __unregister_ftrace_function()
                    -&amp;gt; WARN_ON(!(ops-&amp;gt;flags &amp;amp; FTRACE_OPS_FL_ENABLED))&lt;/p&gt;
&lt;p&gt;Fix this by checking FTRACE_OPS_FL_ENABLED before attempting to
unregister. If the ops is not enabled, just free the filter and
return success.&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;perf/ftrace: Fix WARNING in __unregister_ftrace_function&lt;/p&gt;
&lt;p&gt;perf_ftrace_function_unregister() unconditionally calls
unregister_ftrace_function() without checking whether the ftrace_ops
was ever successfully registered. This triggers a WARN_ON in
__unregister_ftrace_function() when the ops doesn&amp;#39;t have
FTRACE_OPS_FL_ENABLED set.&lt;/p&gt;
&lt;p&gt;This can happen during perf_event_alloc() error cleanup when
perf_trace_destroy() is called via __free_event() on an event whose
ftrace_ops registration failed or was already torn down by
perf_try_init_event()&amp;#39;s err_destroy path.&lt;/p&gt;
&lt;p&gt;The call path is:
  perf_event_alloc() error cleanup
    -&amp;gt; __free_event()
      -&amp;gt; event-&amp;gt;destroy() [tp_perf_event_destroy]
        -&amp;gt; perf_trace_destroy()
          -&amp;gt; perf_trace_event_close()
            -&amp;gt; TRACE_REG_PERF_CLOSE
              -&amp;gt; perf_ftrace_function_unregister()
                -&amp;gt; unregister_ftrace_function()
                  -&amp;gt; __unregister_ftrace_function()
                    -&amp;gt; WARN_ON(!(ops-&amp;gt;flags &amp;amp; FTRACE_OPS_FL_ENABLED))&lt;/p&gt;
&lt;p&gt;Fix this by checking FTRACE_OPS_FL_ENABLED before attempting to
unregister. If the ops is not enabled, just free the filter and
return success.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/cve-2026-97443</guid>
    </item>
  </channel>
</rss>
