<?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:20:16 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-99653 — mm: fix unkillable fault loop on MAP_DROPPABLE memory</title>
      <link>https://db.gcve.eu/vuln/cve-2026-99653</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Linux&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;mm: fix unkillable fault loop on MAP_DROPPABLE memory&lt;/p&gt;
&lt;p&gt;handle_mm_fault() suppresses VM_FAULT_OOM for VM_DROPPABLE mappings.&lt;/p&gt;
&lt;p&gt;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.&lt;/p&gt;
&lt;p&gt;With persistent allocation failures (esp. memcg limits), a syscall,
such as write(), can therefore loop while not dropping locks.&lt;/p&gt;
&lt;p&gt;Only suppress VM_FAULT_OOM when FAULT_FLAG_USER is set, allowing
kernel-mode faults and GUP to fail and signal allocation errors.&lt;/p&gt;
&lt;p&gt;Fix generated by an LLM and sent by Chris Mason in private.&lt;/p&gt;
&lt;p&gt;[ david: simplify description ]&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Linux&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;mm: fix unkillable fault loop on MAP_DROPPABLE memory&lt;/p&gt;
&lt;p&gt;handle_mm_fault() suppresses VM_FAULT_OOM for VM_DROPPABLE mappings.&lt;/p&gt;
&lt;p&gt;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.&lt;/p&gt;
&lt;p&gt;With persistent allocation failures (esp. memcg limits), a syscall,
such as write(), can therefore loop while not dropping locks.&lt;/p&gt;
&lt;p&gt;Only suppress VM_FAULT_OOM when FAULT_FLAG_USER is set, allowing
kernel-mode faults and GUP to fail and signal allocation errors.&lt;/p&gt;
&lt;p&gt;Fix generated by an LLM and sent by Chris Mason in private.&lt;/p&gt;
&lt;p&gt;[ david: simplify description ]&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/cve-2026-99653</guid>
    </item>
  </channel>
</rss>
