<?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:21:18 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-99655 — mm/memory: reject remote COW faults on PFN mappings</title>
      <link>https://db.gcve.eu/vuln/cve-2026-99655</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/memory: reject remote COW faults on PFN mappings&lt;/p&gt;
&lt;p&gt;When handling a COW fault without a normal source page (PFN mappings),
__wp_page_copy_user() copies from the faulting user address. For remote
faults, this accesses the wrong address space, resulting in wrong data
getting copied.&lt;/p&gt;
&lt;p&gt;For example, user_events updates an enable bit in the registering
process&amp;#39;s memory. If that memory needs to be faulted in,
user_event_enabler_fault_fixup() calls fixup_user_fault() from a work
item. Placing the enable bit in a private PFN mapping can trigger this
remote COW path.&lt;/p&gt;
&lt;p&gt;Reject these faults with VM_FAULT_SIGBUS when the target mm differs from
current-&amp;gt;mm: remote faults. Ordinary (non-PFN) mappings are not affected.&lt;/p&gt;
&lt;p&gt;The user-address copy dates back to commit 6aab341e0a28 (&amp;#34;mm: re-architect
the VM_UNPAGED logic&amp;#34;); likely, actual ways to get remote faults in
there on COW PFN mappings appeared afterwards. But the fix is simple and
straight forward.&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 comment and 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/memory: reject remote COW faults on PFN mappings&lt;/p&gt;
&lt;p&gt;When handling a COW fault without a normal source page (PFN mappings),
__wp_page_copy_user() copies from the faulting user address. For remote
faults, this accesses the wrong address space, resulting in wrong data
getting copied.&lt;/p&gt;
&lt;p&gt;For example, user_events updates an enable bit in the registering
process&amp;#39;s memory. If that memory needs to be faulted in,
user_event_enabler_fault_fixup() calls fixup_user_fault() from a work
item. Placing the enable bit in a private PFN mapping can trigger this
remote COW path.&lt;/p&gt;
&lt;p&gt;Reject these faults with VM_FAULT_SIGBUS when the target mm differs from
current-&amp;gt;mm: remote faults. Ordinary (non-PFN) mappings are not affected.&lt;/p&gt;
&lt;p&gt;The user-address copy dates back to commit 6aab341e0a28 (&amp;#34;mm: re-architect
the VM_UNPAGED logic&amp;#34;); likely, actual ways to get remote faults in
there on COW PFN mappings appeared afterwards. But the fix is simple and
straight forward.&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 comment and description ]&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/cve-2026-99655</guid>
    </item>
  </channel>
</rss>
