<?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>Sun, 04 Oct 2026 06:41:20 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-64075 — fprobe: Fix unregister_fprobe() to wait for RCU grace period</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2026-64075</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;fprobe: Fix unregister_fprobe() to wait for RCU grace period&lt;/p&gt;
&lt;p&gt;Commit 4346ba1604093 (&amp;#34;fprobe: Rewrite fprobe on function-graph tracer&amp;#34;)
changed fprobe to register struct fprobe to an rcu-hlist, but it forgot
to wait for RCU GP. Thus there can be use-after-free if the fprobe is
released right after unregistering. This can be happened on fprobe
event and sample module code.&lt;/p&gt;
&lt;p&gt;To fix this issue, add synchronize_rcu() in unregister_fprobe().&lt;/p&gt;
&lt;p&gt;Note that BPF is OK because fprobe is used as a part of
bpf_kprobe_multi_link. This unregisters its fprobe in
bpf_kprobe_multi_link_release() and it is deallocated via
bpf_kprobe_multi_link_dealloc(), which is invoked from
bpf_link_defer_dealloc_rcu_gp() RCU callback.&lt;/p&gt;
&lt;p&gt;For BPF, this also introduced unregister_fprobe_async() which does
NOT wait for RCU grace priod.&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;fprobe: Fix unregister_fprobe() to wait for RCU grace period&lt;/p&gt;
&lt;p&gt;Commit 4346ba1604093 (&amp;#34;fprobe: Rewrite fprobe on function-graph tracer&amp;#34;)
changed fprobe to register struct fprobe to an rcu-hlist, but it forgot
to wait for RCU GP. Thus there can be use-after-free if the fprobe is
released right after unregistering. This can be happened on fprobe
event and sample module code.&lt;/p&gt;
&lt;p&gt;To fix this issue, add synchronize_rcu() in unregister_fprobe().&lt;/p&gt;
&lt;p&gt;Note that BPF is OK because fprobe is used as a part of
bpf_kprobe_multi_link. This unregisters its fprobe in
bpf_kprobe_multi_link_release() and it is deallocated via
bpf_kprobe_multi_link_dealloc(), which is invoked from
bpf_link_defer_dealloc_rcu_gp() RCU callback.&lt;/p&gt;
&lt;p&gt;For BPF, this also introduced unregister_fprobe_async() which does
NOT wait for RCU grace priod.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2026-64075</guid>
    </item>
  </channel>
</rss>
