<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
  <id>https://vulnerability.circl.lu/rss/recent/all/10</id>
  <title>Most recent entries from all</title>
  <updated>2026-09-29T02:21:13.168777+00:00</updated>
  <author>
    <name>Vulnerability-Lookup</name>
    <email>info@circl.lu</email>
  </author>
  <link href="https://vulnerability.circl.lu" rel="alternate"/>
  <generator uri="https://lkiesow.github.io/python-feedgen" version="1.0.0">python-feedgen</generator>
  <subtitle>Contains only the most 10 recent entries.</subtitle>
  <entry>
    <id>https://vulnerability.circl.lu/vuln/cve-2026-97443</id>
    <title>CVE-2026-97443 — perf/ftrace: Fix WARNING in __unregister_ftrace_function</title>
    <updated>2026-09-29T02:21:13.418976+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> Linux</p>
<p>In the Linux kernel, the following vulnerability has been resolved:</p>
<p>perf/ftrace: Fix WARNING in __unregister_ftrace_function</p>
<p>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't have
FTRACE_OPS_FL_ENABLED set.</p>
<p>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()'s err_destroy path.</p>
<p>The call path is:
  perf_event_alloc() error cleanup
    -&gt; __free_event()
      -&gt; event-&gt;destroy() [tp_perf_event_destroy]
        -&gt; perf_trace_destroy()
          -&gt; perf_trace_event_close()
            -&gt; TRACE_REG_PERF_CLOSE
              -&gt; perf_ftrace_function_unregister()
                -&gt; unregister_ftrace_function()
                  -&gt; __unregister_ftrace_function()
                    -&gt; WARN_ON(!(ops-&gt;flags &amp; FTRACE_OPS_FL_ENABLED))</p>
<p>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.</p></div>
    </content>
    <link href="https://vulnerability.circl.lu/vuln/cve-2026-97443"/>
  </entry>
</feed>
