<?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>Wed, 30 Sep 2026 08:26:38 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-93137 — bpf: Fix use-after-free on mm_struct in bpf_find_vma()</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2026-93137</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 use-after-free on mm_struct in bpf_find_vma()&lt;/p&gt;
&lt;p&gt;bpf_find_vma() reads task-&amp;gt;mm and calls mmap_read_trylock(mm) without
holding a reference on the mm. On a foreign task, a concurrent exit_mm()
can free the mm_struct between the lockless read and the trylock,
resulting in a use-after-free. mm_struct is not SLAB_TYPESAFE_BY_RCU.&lt;/p&gt;
&lt;p&gt;For the current task, task-&amp;gt;mm is stable. For a foreign task, pin the mm
under task-&amp;gt;alloc_lock and release it with mmput_async(), mirroring commit
d8e27d2d22b6 (&amp;#34;bpf: fix mm lifecycle in open-coded task_vma iterator&amp;#34;).
Use spin_trylock() instead of get_task_mm() so BPF context does not block
on alloc_lock. Reject irqs-disabled contexts and !CONFIG_MMU on the
foreign-task path because dropping the mm reference is not safe there.&lt;/p&gt;
&lt;p&gt;Race:&lt;/p&gt;
&lt;p&gt;CPU0 (BPF program)                  CPU1 (exiting task)
  ============================        ==========================
  bpf_find_vma(foreign_task):
    mm = task-&amp;gt;mm
                                      exit_mm():
                                        task-&amp;gt;mm = NULL
                                        mmput(mm) -&amp;gt; frees mm_struct
    mmap_read_trylock(mm)
        // UAF on mm&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 use-after-free on mm_struct in bpf_find_vma()&lt;/p&gt;
&lt;p&gt;bpf_find_vma() reads task-&amp;gt;mm and calls mmap_read_trylock(mm) without
holding a reference on the mm. On a foreign task, a concurrent exit_mm()
can free the mm_struct between the lockless read and the trylock,
resulting in a use-after-free. mm_struct is not SLAB_TYPESAFE_BY_RCU.&lt;/p&gt;
&lt;p&gt;For the current task, task-&amp;gt;mm is stable. For a foreign task, pin the mm
under task-&amp;gt;alloc_lock and release it with mmput_async(), mirroring commit
d8e27d2d22b6 (&amp;#34;bpf: fix mm lifecycle in open-coded task_vma iterator&amp;#34;).
Use spin_trylock() instead of get_task_mm() so BPF context does not block
on alloc_lock. Reject irqs-disabled contexts and !CONFIG_MMU on the
foreign-task path because dropping the mm reference is not safe there.&lt;/p&gt;
&lt;p&gt;Race:&lt;/p&gt;
&lt;p&gt;CPU0 (BPF program)                  CPU1 (exiting task)
  ============================        ==========================
  bpf_find_vma(foreign_task):
    mm = task-&amp;gt;mm
                                      exit_mm():
                                        task-&amp;gt;mm = NULL
                                        mmput(mm) -&amp;gt; frees mm_struct
    mmap_read_trylock(mm)
        // UAF on mm&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2026-93137</guid>
    </item>
  </channel>
</rss>
