<?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:03:58 +0000</lastBuildDate>
    <item>
      <title>fkie_cve-2026-99735</title>
      <link>https://db.gcve.eu/vuln/fkie_cve-2026-99735</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;mm/mglru: don&amp;#39;t use stack pointers when walking PUD and PMD tables&lt;/p&gt;
&lt;p&gt;MGLRU passes stack copies of page-table entries in walk_pud_range() and
walk_pmd_range() when walking to the next level. These copies can become
stale when khugepaged or MADV_DONTNEED (CONFIG_PT_RECLAIM) removes a PTE
table concurrently.&lt;/p&gt;
&lt;p&gt;This pattern dates back to commit bd74fdaea146 (&amp;#34;mm: multi-gen LRU:
support page table walks&amp;#34;). Likely, earlier locking masked the latent
bug. Later changes exposed it: commit 1d65b771bc08 (&amp;#34;mm/khugepaged:
retract_page_tables() without mmap or vma lock&amp;#34;) allowed concurrent
retraction, and commit cf4a65539c13 (&amp;#34;memcg-v1: no need for memcg locking
for MGLRU&amp;#34;) dropped the walker&amp;#39;s outer RCU protection.&lt;/p&gt;
&lt;p&gt;The fix is simple, so just fix the original commit so we don&amp;#39;t have to
speculate. To fix it, pass the actual PMD/PUD pointers. This restores the
RCU-protected lookup and validation against the live PMD. Note that the PUD
handling is required as well to handle folded page tables correctly in all
cases.&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: handle walk_pud_range() as well, clarify+simplify description,
         adjust Fixes: ]&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;mm/mglru: don&amp;#39;t use stack pointers when walking PUD and PMD tables&lt;/p&gt;
&lt;p&gt;MGLRU passes stack copies of page-table entries in walk_pud_range() and
walk_pmd_range() when walking to the next level. These copies can become
stale when khugepaged or MADV_DONTNEED (CONFIG_PT_RECLAIM) removes a PTE
table concurrently.&lt;/p&gt;
&lt;p&gt;This pattern dates back to commit bd74fdaea146 (&amp;#34;mm: multi-gen LRU:
support page table walks&amp;#34;). Likely, earlier locking masked the latent
bug. Later changes exposed it: commit 1d65b771bc08 (&amp;#34;mm/khugepaged:
retract_page_tables() without mmap or vma lock&amp;#34;) allowed concurrent
retraction, and commit cf4a65539c13 (&amp;#34;memcg-v1: no need for memcg locking
for MGLRU&amp;#34;) dropped the walker&amp;#39;s outer RCU protection.&lt;/p&gt;
&lt;p&gt;The fix is simple, so just fix the original commit so we don&amp;#39;t have to
speculate. To fix it, pass the actual PMD/PUD pointers. This restores the
RCU-protected lookup and validation against the live PMD. Note that the PUD
handling is required as well to handle folded page tables correctly in all
cases.&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: handle walk_pud_range() as well, clarify+simplify description,
         adjust Fixes: ]&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/fkie_cve-2026-99735</guid>
    </item>
    <item>
      <title>GHSA-6737-4m3c-x4x3</title>
      <link>https://db.gcve.eu/vuln/ghsa-6737-4m3c-x4x3</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;mm/mglru: don&amp;#39;t use stack pointers when walking PUD and PMD tables&lt;/p&gt;
&lt;p&gt;MGLRU passes stack copies of page-table entries in walk_pud_range() and
walk_pmd_range() when walking to the next level. These copies can become
stale when khugepaged or MADV_DONTNEED (CONFIG_PT_RECLAIM) removes a PTE
table concurrently.&lt;/p&gt;
&lt;p&gt;This pattern dates back to commit bd74fdaea146 (&amp;#34;mm: multi-gen LRU:
support page table walks&amp;#34;). Likely, earlier locking masked the latent
bug. Later changes exposed it: commit 1d65b771bc08 (&amp;#34;mm/khugepaged:
retract_page_tables() without mmap or vma lock&amp;#34;) allowed concurrent
retraction, and commit cf4a65539c13 (&amp;#34;memcg-v1: no need for memcg locking
for MGLRU&amp;#34;) dropped the walker&amp;#39;s outer RCU protection.&lt;/p&gt;
&lt;p&gt;The fix is simple, so just fix the original commit so we don&amp;#39;t have to
speculate. To fix it, pass the actual PMD/PUD pointers. This restores the
RCU-protected lookup and validation against the live PMD. Note that the PUD
handling is required as well to handle folded page tables correctly in all
cases.&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: handle walk_pud_range() as well, clarify+simplify description,
         adjust Fixes: ]&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;mm/mglru: don&amp;#39;t use stack pointers when walking PUD and PMD tables&lt;/p&gt;
&lt;p&gt;MGLRU passes stack copies of page-table entries in walk_pud_range() and
walk_pmd_range() when walking to the next level. These copies can become
stale when khugepaged or MADV_DONTNEED (CONFIG_PT_RECLAIM) removes a PTE
table concurrently.&lt;/p&gt;
&lt;p&gt;This pattern dates back to commit bd74fdaea146 (&amp;#34;mm: multi-gen LRU:
support page table walks&amp;#34;). Likely, earlier locking masked the latent
bug. Later changes exposed it: commit 1d65b771bc08 (&amp;#34;mm/khugepaged:
retract_page_tables() without mmap or vma lock&amp;#34;) allowed concurrent
retraction, and commit cf4a65539c13 (&amp;#34;memcg-v1: no need for memcg locking
for MGLRU&amp;#34;) dropped the walker&amp;#39;s outer RCU protection.&lt;/p&gt;
&lt;p&gt;The fix is simple, so just fix the original commit so we don&amp;#39;t have to
speculate. To fix it, pass the actual PMD/PUD pointers. This restores the
RCU-protected lookup and validation against the live PMD. Note that the PUD
handling is required as well to handle folded page tables correctly in all
cases.&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: handle walk_pud_range() as well, clarify+simplify description,
         adjust Fixes: ]&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/ghsa-6737-4m3c-x4x3</guid>
    </item>
    <item>
      <title>WID-SEC-W-2026-4695 — Linux Kernel: Mehrere Schwachstellen ermöglichen nicht spezifizierten Angriff</title>
      <link>https://db.gcve.eu/vuln/wid-sec-w-2026-4695</link>
      <description>&lt;p&gt;Ein Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um einen nicht näher spezifizierten Angriff durchzuführen, möglicherweise einen Denial-of-Service-Angriff auszulösen, Daten zu manipulieren oder offenzulegen oder Sicherheitsmaßnahmen zu umgehen&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Ein Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um einen nicht näher spezifizierten Angriff durchzuführen, möglicherweise einen Denial-of-Service-Angriff auszulösen, Daten zu manipulieren oder offenzulegen oder Sicherheitsmaßnahmen zu umgehen&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/wid-sec-w-2026-4695</guid>
    </item>
  </channel>
</rss>
