<?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>Tue, 06 Oct 2026 00:28:11 +0000</lastBuildDate>
    <item>
      <title>CVE-2021-47214 — hugetlb, userfaultfd: fix reservation restore on userfaultfd error</title>
      <link>https://cve.radiocsirt.org/vuln/cve-2021-47214</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;hugetlb, userfaultfd: fix reservation restore on userfaultfd error&lt;/p&gt;
&lt;p&gt;Currently in the is_continue case in hugetlb_mcopy_atomic_pte(), if we
bail out using &amp;#34;goto out_release_unlock;&amp;#34; in the cases where idx &amp;gt;=
size, or !huge_pte_none(), the code will detect that new_pagecache_page
== false, and so call restore_reserve_on_error().  In this case I see
restore_reserve_on_error() delete the reservation, and the following
call to remove_inode_hugepages() will increment h-&amp;gt;resv_hugepages
causing a 100% reproducible leak.&lt;/p&gt;
&lt;p&gt;We should treat the is_continue case similar to adding a page into the
pagecache and set new_pagecache_page to true, to indicate that there is
no reservation to restore on the error path, and we need not call
restore_reserve_on_error().  Rename new_pagecache_page to
page_in_pagecache to make that clear.&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;hugetlb, userfaultfd: fix reservation restore on userfaultfd error&lt;/p&gt;
&lt;p&gt;Currently in the is_continue case in hugetlb_mcopy_atomic_pte(), if we
bail out using &amp;#34;goto out_release_unlock;&amp;#34; in the cases where idx &amp;gt;=
size, or !huge_pte_none(), the code will detect that new_pagecache_page
== false, and so call restore_reserve_on_error().  In this case I see
restore_reserve_on_error() delete the reservation, and the following
call to remove_inode_hugepages() will increment h-&amp;gt;resv_hugepages
causing a 100% reproducible leak.&lt;/p&gt;
&lt;p&gt;We should treat the is_continue case similar to adding a page into the
pagecache and set new_pagecache_page to true, to indicate that there is
no reservation to restore on the error path, and we need not call
restore_reserve_on_error().  Rename new_pagecache_page to
page_in_pagecache to make that clear.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/cve-2021-47214</guid>
    </item>
  </channel>
</rss>
