<?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-10-01T10:19:35.259498+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-2025-37884</id>
    <title>CVE-2025-37884 — bpf: Fix deadlock between rcu_tasks_trace and event_mutex.</title>
    <updated>2026-10-01T10:19:36.268446+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>bpf: Fix deadlock between rcu_tasks_trace and event_mutex.</p>
<p>Fix the following deadlock:
CPU A
_free_event()
  perf_kprobe_destroy()
    mutex_lock(&amp;event_mutex)
      perf_trace_event_unreg()
        synchronize_rcu_tasks_trace()</p>
<p>There are several paths where _free_event() grabs event_mutex
and calls sync_rcu_tasks_trace. Above is one such case.</p>
<p>CPU B
bpf_prog_test_run_syscall()
  rcu_read_lock_trace()
    bpf_prog_run_pin_on_cpu()
      bpf_prog_load()
        bpf_tracing_func_proto()
          trace_set_clr_event()
            mutex_lock(&amp;event_mutex)</p>
<p>Delegate trace_set_clr_event() to workqueue to avoid
such lock dependency.</p></div>
    </content>
    <link href="https://vulnerability.circl.lu/vuln/cve-2025-37884"/>
  </entry>
</feed>
