<?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>Tue, 29 Sep 2026 06:55:18 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-90342 — bpf: Fix mmap_lock deadlock on arena lock failure</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2026-90342</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 mmap_lock deadlock on arena lock failure&lt;/p&gt;
&lt;p&gt;Reported by the Sashiko AI review.&lt;/p&gt;
&lt;p&gt;arena_vm_fault() returns VM_FAULT_RETRY when it can&amp;#39;t take
arena-&amp;gt;spinlock, but it never took mmap_lock. The fault path assumes a
VM_FAULT_RETRY handler already dropped mmap_lock and re-takes it on the
retry, so mmap_lock gets taken twice and can deadlock:&lt;/p&gt;
&lt;p&gt;do_user_addr_fault()
	{
		fault = handle_mm_fault(...);   // calls arena_vm_fault()
		if (fault &amp;amp; VM_FAULT_RETRY)
			goto retry;   // re-locks mmap_lock
		mmap_read_unlock(mm);
	}&lt;/p&gt;
&lt;p&gt;Return VM_FAULT_SIGBUS instead, for two reasons:&lt;/p&gt;
&lt;p&gt;1. We could keep VM_FAULT_RETRY, but then we&amp;#39;d have to drop the fault
   lock first and cap the retry ourselves, the way __folio_lock_or_retry()
   does.&lt;/p&gt;
&lt;p&gt;2. A failed raw_res_spin_lock_irqsave() already means a possible deadlock
   was detected, so retrying just hits the same lock again.&lt;/p&gt;
&lt;p&gt;So returning VM_FAULT_RETRY here is overkill.&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 mmap_lock deadlock on arena lock failure&lt;/p&gt;
&lt;p&gt;Reported by the Sashiko AI review.&lt;/p&gt;
&lt;p&gt;arena_vm_fault() returns VM_FAULT_RETRY when it can&amp;#39;t take
arena-&amp;gt;spinlock, but it never took mmap_lock. The fault path assumes a
VM_FAULT_RETRY handler already dropped mmap_lock and re-takes it on the
retry, so mmap_lock gets taken twice and can deadlock:&lt;/p&gt;
&lt;p&gt;do_user_addr_fault()
	{
		fault = handle_mm_fault(...);   // calls arena_vm_fault()
		if (fault &amp;amp; VM_FAULT_RETRY)
			goto retry;   // re-locks mmap_lock
		mmap_read_unlock(mm);
	}&lt;/p&gt;
&lt;p&gt;Return VM_FAULT_SIGBUS instead, for two reasons:&lt;/p&gt;
&lt;p&gt;1. We could keep VM_FAULT_RETRY, but then we&amp;#39;d have to drop the fault
   lock first and cap the retry ourselves, the way __folio_lock_or_retry()
   does.&lt;/p&gt;
&lt;p&gt;2. A failed raw_res_spin_lock_irqsave() already means a possible deadlock
   was detected, so retrying just hits the same lock again.&lt;/p&gt;
&lt;p&gt;So returning VM_FAULT_RETRY here is overkill.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2026-90342</guid>
    </item>
  </channel>
</rss>
