<?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 15:00:34 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-53084 — bpf: return VMA snapshot from task_vma iterator</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2026-53084</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: return VMA snapshot from task_vma iterator&lt;/p&gt;
&lt;p&gt;Holding the per-VMA lock across the BPF program body creates a lock
ordering problem when helpers acquire locks that depend on mmap_lock:&lt;/p&gt;
&lt;p&gt;vm_lock -&amp;gt; i_rwsem -&amp;gt; mmap_lock -&amp;gt; vm_lock&lt;/p&gt;
&lt;p&gt;Snapshot the VMA under the per-VMA lock in _next() via memcpy(), then
drop the lock before returning. The BPF program accesses only the
snapshot.&lt;/p&gt;
&lt;p&gt;The verifier only trusts vm_mm and vm_file pointers (see
BTF_TYPE_SAFE_TRUSTED_OR_NULL in verifier.c). vm_file is reference-
counted with get_file() under the lock and released via fput() on the
next iteration or in _destroy(). vm_mm is already correct because
lock_vma_under_rcu() verifies vma-&amp;gt;vm_mm == mm. All other pointers
are left as-is by memcpy() since the verifier treats them as untrusted.&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: return VMA snapshot from task_vma iterator&lt;/p&gt;
&lt;p&gt;Holding the per-VMA lock across the BPF program body creates a lock
ordering problem when helpers acquire locks that depend on mmap_lock:&lt;/p&gt;
&lt;p&gt;vm_lock -&amp;gt; i_rwsem -&amp;gt; mmap_lock -&amp;gt; vm_lock&lt;/p&gt;
&lt;p&gt;Snapshot the VMA under the per-VMA lock in _next() via memcpy(), then
drop the lock before returning. The BPF program accesses only the
snapshot.&lt;/p&gt;
&lt;p&gt;The verifier only trusts vm_mm and vm_file pointers (see
BTF_TYPE_SAFE_TRUSTED_OR_NULL in verifier.c). vm_file is reference-
counted with get_file() under the lock and released via fput() on the
next iteration or in _destroy(). vm_mm is already correct because
lock_vma_under_rcu() verifies vma-&amp;gt;vm_mm == mm. All other pointers
are left as-is by memcpy() since the verifier treats them as untrusted.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2026-53084</guid>
    </item>
  </channel>
</rss>
