<?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:20:18.585848+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-99653</id>
    <title>CVE-2026-99653 — mm: fix unkillable fault loop on MAP_DROPPABLE memory</title>
    <updated>2026-11-20T21:20:18.586665+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: fix unkillable fault loop on MAP_DROPPABLE memory</p>
<p>handle_mm_fault() suppresses VM_FAULT_OOM for VM_DROPPABLE mappings.</p>
<p>For user-mode faults, pending signals are processed before retrying the
access. Kernel-mode faults on user buffers instead return directly to
the faulting instruction.</p>
<p>With persistent allocation failures (esp. memcg limits), a syscall,
such as write(), can therefore loop while not dropping locks.</p>
<p>Only suppress VM_FAULT_OOM when FAULT_FLAG_USER is set, allowing
kernel-mode faults and GUP to fail and signal allocation errors.</p>
<p>Fix generated by an LLM and sent by Chris Mason in private.</p>
<p>[ david: simplify description ]</p></div>
    </content>
    <link href="https://db.gcve.eu/vuln/cve-2026-99653"/>
  </entry>
</feed>
