<?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:17:50.534560+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-99738</id>
    <title>CVE-2026-99738 — mm/shmem: preserve allocation errors when swapping in large entries</title>
    <updated>2026-11-20T21:17:50.535824+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/shmem: preserve allocation errors when swapping in large entries</p>
<p>shmem_swapin_folio() adjusts swap to the requested slot within a large
swap entry before allocating a folio. If allocation or charging fails,
the error path compares this adjusted value with the original entry
still stored in the XArray in shmem_confirm_swap().</p>
<p>Unless the index is at the start of the entry, this turns -ENOMEM into
-EEXIST even though nothing changed.</p>
<p>The caller retries -EEXIST, so persistent allocation failures can leave
the task spinning instead of returning the error.</p>
<p>Restore swap to index_entry on allocation failure so the existing error
path checks the original entry. This preserves the allocation error if
the entry is unchanged and still retries if it changed concurrently.</p></div>
    </content>
    <link href="https://db.gcve.eu/vuln/cve-2026-99738"/>
  </entry>
</feed>
