<?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://cve.radiocsirt.org</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>Thu, 08 Oct 2026 18:38:23 +0000</lastBuildDate>
    <item>
      <title>CVE-2025-38085 — mm/hugetlb: fix huge_pmd_unshare() vs GUP-fast race</title>
      <link>https://cve.radiocsirt.org/vuln/cve-2025-38085</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/hugetlb: fix huge_pmd_unshare() vs GUP-fast race&lt;/p&gt;
&lt;p&gt;huge_pmd_unshare() drops a reference on a page table that may have
previously been shared across processes, potentially turning it into a
normal page table used in another process in which unrelated VMAs can
afterwards be installed.&lt;/p&gt;
&lt;p&gt;If this happens in the middle of a concurrent gup_fast(), gup_fast() could
end up walking the page tables of another process.  While I don&amp;#39;t see any
way in which that immediately leads to kernel memory corruption, it is
really weird and unexpected.&lt;/p&gt;
&lt;p&gt;Fix it with an explicit broadcast IPI through tlb_remove_table_sync_one(),
just like we do in khugepaged when removing page tables for a THP
collapse.&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/hugetlb: fix huge_pmd_unshare() vs GUP-fast race&lt;/p&gt;
&lt;p&gt;huge_pmd_unshare() drops a reference on a page table that may have
previously been shared across processes, potentially turning it into a
normal page table used in another process in which unrelated VMAs can
afterwards be installed.&lt;/p&gt;
&lt;p&gt;If this happens in the middle of a concurrent gup_fast(), gup_fast() could
end up walking the page tables of another process.  While I don&amp;#39;t see any
way in which that immediately leads to kernel memory corruption, it is
really weird and unexpected.&lt;/p&gt;
&lt;p&gt;Fix it with an explicit broadcast IPI through tlb_remove_table_sync_one(),
just like we do in khugepaged when removing page tables for a THP
collapse.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/cve-2025-38085</guid>
    </item>
  </channel>
</rss>
