<?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>Mon, 05 Oct 2026 01:21:13 +0000</lastBuildDate>
    <item>
      <title>bdu:2025-06527</title>
      <link>https://cve.radiocsirt.org/vuln/bdu:2025-06527</link>
      <description>bdu:2025-06527</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/bdu:2025-06527</guid>
    </item>
    <item>
      <title>certfr-2024-avi-0363 — De multiples vulnérabilités ont été découvertes dans &lt;span
class="textit"&gt;le noyau Linux de SUSE&lt;/span&gt;. Certaines d'en…</title>
      <link>https://cve.radiocsirt.org/vuln/certfr-2024-avi-0363</link>
      <description>certfr-2024-avi-0363</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/certfr-2024-avi-0363</guid>
    </item>
    <item>
      <title>EUVD-2026-309477</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-309477</link>
      <description>EUVD-2026-309477</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-309477</guid>
    </item>
    <item>
      <title>fkie_cve-2021-46988</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2021-46988</link>
      <description>&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;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/fkie_cve-2021-46988</guid>
    </item>
    <item>
      <title>GHSA-w36p-947m-7c32</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-w36p-947m-7c32</link>
      <description>&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;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/ghsa-w36p-947m-7c32</guid>
    </item>
    <item>
      <title>gsd-2021-46988</title>
      <link>https://cve.radiocsirt.org/vuln/gsd-2021-46988</link>
      <description>gsd-2021-46988</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/gsd-2021-46988</guid>
    </item>
    <item>
      <title>SUSE-SU-2024:1454-1 — Security update for the Linux Kernel</title>
      <link>https://cve.radiocsirt.org/vuln/suse-su-2024:1454-1</link>
      <description>&lt;p&gt;Security update for the Linux Kernel&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Security update for the Linux Kernel&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/suse-su-2024:1454-1</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2021-46988</title>
      <link>https://cve.radiocsirt.org/vuln/ubuntu-cve-2021-46988</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:Pro:14.04:LTS: linux-azure, Ubuntu:Pro:16.04:LTS: linux-aws-hwe, Ubuntu:Pro:16.04:LTS: linux-azure, Ubuntu:Pro:16.04:LTS: linux-gcp, Ubuntu:Pro:16.04:LTS: linux-hwe, Ubuntu:Pro:16.04:LTS: linux-oracle, Ubuntu:16.04:LTS: linux-hwe-edge, Ubuntu:18.04:LTS: linux, Ubuntu:18.04:LTS: linux-aws, Ubuntu:18.04:LTS: linux-aws-5.4 and 100 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: userfaultfd: release page in error path to avoid BUG_ON Consider the following sequence of events: 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. This triggers a BUG_ON in our caller, which asserts that the page should always be consumed, unless -ENOENT is returned. 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; Ubuntu:Pro:14.04:LTS: linux-azure, Ubuntu:Pro:16.04:LTS: linux-aws-hwe, Ubuntu:Pro:16.04:LTS: linux-azure, Ubuntu:Pro:16.04:LTS: linux-gcp, Ubuntu:Pro:16.04:LTS: linux-hwe, Ubuntu:Pro:16.04:LTS: linux-oracle, Ubuntu:16.04:LTS: linux-hwe-edge, Ubuntu:18.04:LTS: linux, Ubuntu:18.04:LTS: linux-aws, Ubuntu:18.04:LTS: linux-aws-5.4 and 100 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: userfaultfd: release page in error path to avoid BUG_ON Consider the following sequence of events: 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. This triggers a BUG_ON in our caller, which asserts that the page should always be consumed, unless -ENOENT is returned. 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/ubuntu-cve-2021-46988</guid>
    </item>
  </channel>
</rss>
