<?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>Fri, 20 Nov 2026 21:20:06 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-99666 — mm/khugepaged: fix PMD table lock leak in try_collapse_pte_mapped_thp()</title>
      <link>https://db.gcve.eu/vuln/cve-2026-99666</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;mm/khugepaged: fix PMD table lock leak in try_collapse_pte_mapped_thp()&lt;/p&gt;
&lt;p&gt;For a private mapping with userfaultfd, try_collapse_pte_mapped_thp()
takes the PMD table lock before it maps the page table for the second time.
If that (pte_offset_map_rw_nolock) fails, because the page table vanished
in the meantime due to concurrent page table reclaim, it leaves through
the abort label, where the PMD table lock is unlocked if it differs from
PTE table lock.&lt;/p&gt;
&lt;p&gt;In case the PMD table lock and the PTE table lock match, which is the
case without CONFIG_SPLIT_PTE_PTLOCKS after pte_offset_map_rw_nolock()
failed, we miss to unlock the PMD table.&lt;/p&gt;
&lt;p&gt;To fix it, forget the PTE table lock when we unmap+unlock the PTE table.&lt;/p&gt;
&lt;p&gt;Fix generated by an LLM and sent by Josef Bacik in private.&lt;/p&gt;
&lt;p&gt;[ david: move the ptl = NULL handling; rewrite description, drop wrong comments ]&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;mm/khugepaged: fix PMD table lock leak in try_collapse_pte_mapped_thp()&lt;/p&gt;
&lt;p&gt;For a private mapping with userfaultfd, try_collapse_pte_mapped_thp()
takes the PMD table lock before it maps the page table for the second time.
If that (pte_offset_map_rw_nolock) fails, because the page table vanished
in the meantime due to concurrent page table reclaim, it leaves through
the abort label, where the PMD table lock is unlocked if it differs from
PTE table lock.&lt;/p&gt;
&lt;p&gt;In case the PMD table lock and the PTE table lock match, which is the
case without CONFIG_SPLIT_PTE_PTLOCKS after pte_offset_map_rw_nolock()
failed, we miss to unlock the PMD table.&lt;/p&gt;
&lt;p&gt;To fix it, forget the PTE table lock when we unmap+unlock the PTE table.&lt;/p&gt;
&lt;p&gt;Fix generated by an LLM and sent by Josef Bacik in private.&lt;/p&gt;
&lt;p&gt;[ david: move the ptl = NULL handling; rewrite description, drop wrong comments ]&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/cve-2026-99666</guid>
    </item>
  </channel>
</rss>
