<?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 06:25:22 +0000</lastBuildDate>
    <item>
      <title>CVE-2021-46988 — userfaultfd: release page in error path to avoid BUG_ON</title>
      <link>https://cve.radiocsirt.org/vuln/cve-2021-46988</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;userfaultfd: release page in error path to avoid BUG_ON&lt;/p&gt;
&lt;p&gt;Consider the following sequence of events:&lt;/p&gt;
&lt;p&gt;1. Userspace issues a UFFD ioctl, which ends up calling into
   shmem_mfill_atomic_pte(). We successfully account the blocks, we
   shmem_alloc_page(), but then the copy_from_user() fails. We return
   -ENOENT. We don&amp;#39;t release the page we allocated.
2. Our caller detects this error code, tries the copy_from_user() after
   dropping the mmap_lock, and retries, calling back into
   shmem_mfill_atomic_pte().
3. Meanwhile, let&amp;#39;s say another process filled up the tmpfs being used.
4. So shmem_mfill_atomic_pte() fails to account blocks this time, and
   immediately returns - without releasing the page.&lt;/p&gt;
&lt;p&gt;This triggers a BUG_ON in our caller, which asserts that the page
should always be consumed, unless -ENOENT is returned.&lt;/p&gt;
&lt;p&gt;To fix this, detect if we have such a &amp;#34;dangling&amp;#34; page when accounting
fails, and if so, release it before returning.&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;userfaultfd: release page in error path to avoid BUG_ON&lt;/p&gt;
&lt;p&gt;Consider the following sequence of events:&lt;/p&gt;
&lt;p&gt;1. Userspace issues a UFFD ioctl, which ends up calling into
   shmem_mfill_atomic_pte(). We successfully account the blocks, we
   shmem_alloc_page(), but then the copy_from_user() fails. We return
   -ENOENT. We don&amp;#39;t release the page we allocated.
2. Our caller detects this error code, tries the copy_from_user() after
   dropping the mmap_lock, and retries, calling back into
   shmem_mfill_atomic_pte().
3. Meanwhile, let&amp;#39;s say another process filled up the tmpfs being used.
4. So shmem_mfill_atomic_pte() fails to account blocks this time, and
   immediately returns - without releasing the page.&lt;/p&gt;
&lt;p&gt;This triggers a BUG_ON in our caller, which asserts that the page
should always be consumed, unless -ENOENT is returned.&lt;/p&gt;
&lt;p&gt;To fix this, detect if we have such a &amp;#34;dangling&amp;#34; page when accounting
fails, and if so, release it before returning.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/cve-2021-46988</guid>
    </item>
  </channel>
</rss>
