<?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:30:34 +0000</lastBuildDate>
    <item>
      <title>fkie_cve-2026-99650</title>
      <link>https://db.gcve.eu/vuln/fkie_cve-2026-99650</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;mm/ksm: fix use of a freed anon_vma at swap-in&lt;/p&gt;
&lt;p&gt;A folio read from a swap slot previously shared by KSM can remain in the
swap cache after the process that first mapped it exits. Its anon_vma
can then be freed, so ksm_might_need_to_copy() must not dereference it
to compare roots.&lt;/p&gt;
&lt;p&gt;Doing so can result in some false-positives, resulting in the reverse
mapping missing the new folio mapping, preventing migration and reclaim.&lt;/p&gt;
&lt;p&gt;SLAB_TYPESAFE_BY_RCU allows individual anon_vma objects to be reused
immediately after freeing. A stale pointer can then refer to another
anon_vma whose root matches, even though the target VMA is not linked
to that anon_vma.&lt;/p&gt;
&lt;p&gt;Move the anonymous rmap compatibility checks into
folio_anon_rmap_compatible(). Keep the page-index check and compare the
folio&amp;#39;s anon_vma pointer against the VMA&amp;#39;s own anon_vma and root first.&lt;/p&gt;
&lt;p&gt;If neither matches, bite the bullet and walk the VMA&amp;#39;s anon_vma_chain.
The VMA keeps these anon_vmas alive, and finding a match guarantees that
reverse mapping can find the new mapping.&lt;/p&gt;
&lt;p&gt;Lorenzo Stoakes says in a private discussion:&lt;/p&gt;
&lt;p&gt;&amp;#34;This isn&amp;#39;t quite equivalent to the existing check.&lt;/p&gt;
&lt;p&gt;Every anon_vma in an anon_vma_chain shares the same root, but if you
  split a VMA then fork both of them like this:&lt;/p&gt;
&lt;p&gt;VMA A
               /        \         &amp;lt;split&amp;gt;
            VMA B      VMA C
               \        /
        root &amp;lt;- anon_vma 1
               ----^ ^----…&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/ksm: fix use of a freed anon_vma at swap-in&lt;/p&gt;
&lt;p&gt;A folio read from a swap slot previously shared by KSM can remain in the
swap cache after the process that first mapped it exits. Its anon_vma
can then be freed, so ksm_might_need_to_copy() must not dereference it
to compare roots.&lt;/p&gt;
&lt;p&gt;Doing so can result in some false-positives, resulting in the reverse
mapping missing the new folio mapping, preventing migration and reclaim.&lt;/p&gt;
&lt;p&gt;SLAB_TYPESAFE_BY_RCU allows individual anon_vma objects to be reused
immediately after freeing. A stale pointer can then refer to another
anon_vma whose root matches, even though the target VMA is not linked
to that anon_vma.&lt;/p&gt;
&lt;p&gt;Move the anonymous rmap compatibility checks into
folio_anon_rmap_compatible(). Keep the page-index check and compare the
folio&amp;#39;s anon_vma pointer against the VMA&amp;#39;s own anon_vma and root first.&lt;/p&gt;
&lt;p&gt;If neither matches, bite the bullet and walk the VMA&amp;#39;s anon_vma_chain.
The VMA keeps these anon_vmas alive, and finding a match guarantees that
reverse mapping can find the new mapping.&lt;/p&gt;
&lt;p&gt;Lorenzo Stoakes says in a private discussion:&lt;/p&gt;
&lt;p&gt;&amp;#34;This isn&amp;#39;t quite equivalent to the existing check.&lt;/p&gt;
&lt;p&gt;Every anon_vma in an anon_vma_chain shares the same root, but if you
  split a VMA then fork both of them like this:&lt;/p&gt;
&lt;p&gt;VMA A
               /        \         &amp;lt;split&amp;gt;
            VMA B      VMA C
               \        /
        root &amp;lt;- anon_vma 1
               ----^ ^----…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/fkie_cve-2026-99650</guid>
    </item>
    <item>
      <title>GHSA-jrv6-2gpm-h6x6</title>
      <link>https://db.gcve.eu/vuln/ghsa-jrv6-2gpm-h6x6</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;mm/ksm: fix use of a freed anon_vma at swap-in&lt;/p&gt;
&lt;p&gt;A folio read from a swap slot previously shared by KSM can remain in the
swap cache after the process that first mapped it exits. Its anon_vma
can then be freed, so ksm_might_need_to_copy() must not dereference it
to compare roots.&lt;/p&gt;
&lt;p&gt;Doing so can result in some false-positives, resulting in the reverse
mapping missing the new folio mapping, preventing migration and reclaim.&lt;/p&gt;
&lt;p&gt;SLAB_TYPESAFE_BY_RCU allows individual anon_vma objects to be reused
immediately after freeing. A stale pointer can then refer to another
anon_vma whose root matches, even though the target VMA is not linked
to that anon_vma.&lt;/p&gt;
&lt;p&gt;Move the anonymous rmap compatibility checks into
folio_anon_rmap_compatible(). Keep the page-index check and compare the
folio&amp;#39;s anon_vma pointer against the VMA&amp;#39;s own anon_vma and root first.&lt;/p&gt;
&lt;p&gt;If neither matches, bite the bullet and walk the VMA&amp;#39;s anon_vma_chain.
The VMA keeps these anon_vmas alive, and finding a match guarantees that
reverse mapping can find the new mapping.&lt;/p&gt;
&lt;p&gt;Lorenzo Stoakes says in a private discussion:&lt;/p&gt;
&lt;p&gt;&amp;#34;This isn&amp;#39;t quite equivalent to the existing check.&lt;/p&gt;
&lt;p&gt;Every anon_vma in an anon_vma_chain shares the same root, but if you
  split a VMA then fork both of them like this:&lt;/p&gt;
&lt;p&gt;VMA A
               /        \         &amp;lt;split&amp;gt;
            VMA B      VMA C
               \        /
        root &amp;lt;- anon_vma 1
               ----^ ^----…&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/ksm: fix use of a freed anon_vma at swap-in&lt;/p&gt;
&lt;p&gt;A folio read from a swap slot previously shared by KSM can remain in the
swap cache after the process that first mapped it exits. Its anon_vma
can then be freed, so ksm_might_need_to_copy() must not dereference it
to compare roots.&lt;/p&gt;
&lt;p&gt;Doing so can result in some false-positives, resulting in the reverse
mapping missing the new folio mapping, preventing migration and reclaim.&lt;/p&gt;
&lt;p&gt;SLAB_TYPESAFE_BY_RCU allows individual anon_vma objects to be reused
immediately after freeing. A stale pointer can then refer to another
anon_vma whose root matches, even though the target VMA is not linked
to that anon_vma.&lt;/p&gt;
&lt;p&gt;Move the anonymous rmap compatibility checks into
folio_anon_rmap_compatible(). Keep the page-index check and compare the
folio&amp;#39;s anon_vma pointer against the VMA&amp;#39;s own anon_vma and root first.&lt;/p&gt;
&lt;p&gt;If neither matches, bite the bullet and walk the VMA&amp;#39;s anon_vma_chain.
The VMA keeps these anon_vmas alive, and finding a match guarantees that
reverse mapping can find the new mapping.&lt;/p&gt;
&lt;p&gt;Lorenzo Stoakes says in a private discussion:&lt;/p&gt;
&lt;p&gt;&amp;#34;This isn&amp;#39;t quite equivalent to the existing check.&lt;/p&gt;
&lt;p&gt;Every anon_vma in an anon_vma_chain shares the same root, but if you
  split a VMA then fork both of them like this:&lt;/p&gt;
&lt;p&gt;VMA A
               /        \         &amp;lt;split&amp;gt;
            VMA B      VMA C
               \        /
        root &amp;lt;- anon_vma 1
               ----^ ^----…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/ghsa-jrv6-2gpm-h6x6</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>
