<?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://db.gcve.eu</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 12:18:29 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-90303 — ARM: 9485/1: mm: acquire mmap write lock around show_pte() for user faults</title>
      <link>https://db.gcve.eu/vuln/cve-2026-90303</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;ARM: 9485/1: mm: acquire mmap write lock around show_pte() for user faults&lt;/p&gt;
&lt;p&gt;When CONFIG_DEBUG_USER=y, and cmdline &amp;#34;user_debug=31&amp;#34; is set,
a user fault may trigger show_pte() without any lock.
If another thread in the same process concurrently calls munmap(),
the page table pages may be freed while show_pte() is still traversing
them, causing a use-after-free in show_pte().&lt;/p&gt;
&lt;p&gt;If CONFIG_ARM_LPAE=y, this may cause a kernel panic if the pages table
of PMD are freed when show_pte() is running.&lt;/p&gt;
&lt;p&gt;Acquire mmap_write_lock() around show_pte() for user faults to fix the
contention.&lt;/p&gt;
&lt;p&gt;For user faults, additionally restrict that show_pte() is called only
when the addr is a user-space address (addr &amp;lt; TASK_SIZE). This is because
the lock of tsk-&amp;gt;mm only protects the virtual memory of user address space,
furthermore, dumping the page tables of a kernel-space address for user
faults is unnecessary and may have security implications.&lt;/p&gt;
&lt;p&gt;Keep everything unchanged for kernel faults, because the kernel is
already in the &amp;#34;oops&amp;#34; state, acquiring a lock may risk a deadlock.&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;ARM: 9485/1: mm: acquire mmap write lock around show_pte() for user faults&lt;/p&gt;
&lt;p&gt;When CONFIG_DEBUG_USER=y, and cmdline &amp;#34;user_debug=31&amp;#34; is set,
a user fault may trigger show_pte() without any lock.
If another thread in the same process concurrently calls munmap(),
the page table pages may be freed while show_pte() is still traversing
them, causing a use-after-free in show_pte().&lt;/p&gt;
&lt;p&gt;If CONFIG_ARM_LPAE=y, this may cause a kernel panic if the pages table
of PMD are freed when show_pte() is running.&lt;/p&gt;
&lt;p&gt;Acquire mmap_write_lock() around show_pte() for user faults to fix the
contention.&lt;/p&gt;
&lt;p&gt;For user faults, additionally restrict that show_pte() is called only
when the addr is a user-space address (addr &amp;lt; TASK_SIZE). This is because
the lock of tsk-&amp;gt;mm only protects the virtual memory of user address space,
furthermore, dumping the page tables of a kernel-space address for user
faults is unnecessary and may have security implications.&lt;/p&gt;
&lt;p&gt;Keep everything unchanged for kernel faults, because the kernel is
already in the &amp;#34;oops&amp;#34; state, acquiring a lock may risk a deadlock.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/cve-2026-90303</guid>
    </item>
  </channel>
</rss>
