<?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 06:46:00 +0000</lastBuildDate>
    <item>
      <title>CVE-2023-53221 — bpf: Fix memleak due to fentry attach failure</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2023-53221</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;bpf: Fix memleak due to fentry attach failure&lt;/p&gt;
&lt;p&gt;If it fails to attach fentry, the allocated bpf trampoline image will be
left in the system. That can be verified by checking /proc/kallsyms.&lt;/p&gt;
&lt;p&gt;This meamleak can be verified by a simple bpf program as follows:&lt;/p&gt;
&lt;p&gt;SEC(&amp;#34;fentry/trap_init&amp;#34;)
  int fentry_run()
  {
      return 0;
  }&lt;/p&gt;
&lt;p&gt;It will fail to attach trap_init because this function is freed after
kernel init, and then we can find the trampoline image is left in the
system by checking /proc/kallsyms.&lt;/p&gt;
&lt;p&gt;$ tail /proc/kallsyms
  ffffffffc0613000 t bpf_trampoline_6442453466_1  [bpf]
  ffffffffc06c3000 t bpf_trampoline_6442453466_1  [bpf]&lt;/p&gt;
&lt;p&gt;$ bpftool btf dump file /sys/kernel/btf/vmlinux | grep &amp;#34;FUNC &amp;#39;trap_init&amp;#39;&amp;#34;
  [2522] FUNC &amp;#39;trap_init&amp;#39; type_id=119 linkage=static&lt;/p&gt;
&lt;p&gt;$ echo $((6442453466 &amp;amp; 0x7fffffff))
  2522&lt;/p&gt;
&lt;p&gt;Note that there are two left bpf trampoline images, that is because the
libbpf will fallback to raw tracepoint if -EINVAL is returned.&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;bpf: Fix memleak due to fentry attach failure&lt;/p&gt;
&lt;p&gt;If it fails to attach fentry, the allocated bpf trampoline image will be
left in the system. That can be verified by checking /proc/kallsyms.&lt;/p&gt;
&lt;p&gt;This meamleak can be verified by a simple bpf program as follows:&lt;/p&gt;
&lt;p&gt;SEC(&amp;#34;fentry/trap_init&amp;#34;)
  int fentry_run()
  {
      return 0;
  }&lt;/p&gt;
&lt;p&gt;It will fail to attach trap_init because this function is freed after
kernel init, and then we can find the trampoline image is left in the
system by checking /proc/kallsyms.&lt;/p&gt;
&lt;p&gt;$ tail /proc/kallsyms
  ffffffffc0613000 t bpf_trampoline_6442453466_1  [bpf]
  ffffffffc06c3000 t bpf_trampoline_6442453466_1  [bpf]&lt;/p&gt;
&lt;p&gt;$ bpftool btf dump file /sys/kernel/btf/vmlinux | grep &amp;#34;FUNC &amp;#39;trap_init&amp;#39;&amp;#34;
  [2522] FUNC &amp;#39;trap_init&amp;#39; type_id=119 linkage=static&lt;/p&gt;
&lt;p&gt;$ echo $((6442453466 &amp;amp; 0x7fffffff))
  2522&lt;/p&gt;
&lt;p&gt;Note that there are two left bpf trampoline images, that is because the
libbpf will fallback to raw tracepoint if -EINVAL is returned.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2023-53221</guid>
    </item>
  </channel>
</rss>
