<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
  <id>https://db.gcve.eu/rss/recent/all/10</id>
  <title>Most recent entries from all</title>
  <updated>2026-11-20T21:22:51.775626+00:00</updated>
  <author>
    <name>Vulnerability-Lookup</name>
    <email>info@gcve.eu</email>
  </author>
  <link href="https://db.gcve.eu" rel="alternate"/>
  <generator uri="https://lkiesow.github.io/python-feedgen" version="1.0.0">python-feedgen</generator>
  <subtitle>Contains only the most 10 recent entries.</subtitle>
  <entry>
    <id>https://db.gcve.eu/vuln/cve-2026-99650</id>
    <title>CVE-2026-99650 — mm/ksm: fix use of a freed anon_vma at swap-in</title>
    <updated>2026-11-20T21:22:51.777719+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> Linux</p>
<p>In the Linux kernel, the following vulnerability has been resolved:</p>
<p>mm/ksm: fix use of a freed anon_vma at swap-in</p>
<p>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.</p>
<p>Doing so can result in some false-positives, resulting in the reverse
mapping missing the new folio mapping, preventing migration and reclaim.</p>
<p>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.</p>
<p>Move the anonymous rmap compatibility checks into
folio_anon_rmap_compatible(). Keep the page-index check and compare the
folio's anon_vma pointer against the VMA's own anon_vma and root first.</p>
<p>If neither matches, bite the bullet and walk the VMA's anon_vma_chain.
The VMA keeps these anon_vmas alive, and finding a match guarantees that
reverse mapping can find the new mapping.</p>
<p>Lorenzo Stoakes says in a private discussion:</p>
<p>"This isn't quite equivalent to the existing check.</p>
<p>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:</p>
<p>VMA A
               /        \         &lt;split&gt;
            VMA B      VMA C
               \        /
        root &lt;- anon_vma 1
               ----^ ^----…</p></div>
    </content>
    <link href="https://db.gcve.eu/vuln/cve-2026-99650"/>
  </entry>
</feed>
