<?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>Sun, 04 Oct 2026 09:03:55 +0000</lastBuildDate>
    <item>
      <title>bdu:2024-06300</title>
      <link>https://cve.radiocsirt.org/vuln/bdu:2024-06300</link>
      <description>bdu:2024-06300</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/bdu:2024-06300</guid>
    </item>
    <item>
      <title>certfr-2024-avi-0329 — 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-0329</link>
      <description>certfr-2024-avi-0329</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/certfr-2024-avi-0329</guid>
    </item>
    <item>
      <title>EUVD-2026-309440</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-309440</link>
      <description>EUVD-2026-309440</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-309440</guid>
    </item>
    <item>
      <title>fkie_cve-2021-46927</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2021-46927</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;nitro_enclaves: Use get_user_pages_unlocked() call to handle mmap assert&lt;/p&gt;
&lt;p&gt;After commit 5b78ed24e8ec (&amp;#34;mm/pagemap: add mmap_assert_locked()
annotations to find_vma*()&amp;#34;), the call to get_user_pages() will trigger
the mmap assert.&lt;/p&gt;
&lt;p&gt;static inline void mmap_assert_locked(struct mm_struct *mm)
{
	lockdep_assert_held(&amp;amp;mm-&amp;gt;mmap_lock);
	VM_BUG_ON_MM(!rwsem_is_locked(&amp;amp;mm-&amp;gt;mmap_lock), mm);
}&lt;/p&gt;
&lt;p&gt;[   62.521410] kernel BUG at include/linux/mmap_lock.h:156!
...........................................................
[   62.538938] RIP: 0010:find_vma+0x32/0x80
...........................................................
[   62.605889] Call Trace:
[   62.608502]  &amp;lt;TASK&amp;gt;
[   62.610956]  ? lock_timer_base+0x61/0x80
[   62.614106]  find_extend_vma+0x19/0x80
[   62.617195]  __get_user_pages+0x9b/0x6a0
[   62.620356]  __gup_longterm_locked+0x42d/0x450
[   62.623721]  ? finish_wait+0x41/0x80
[   62.626748]  ? __kmalloc+0x178/0x2f0
[   62.629768]  ne_set_user_memory_region_ioctl.isra.0+0x225/0x6a0 [nitro_enclaves]
[   62.635776]  ne_enclave_ioctl+0x1cf/0x6d7 [nitro_enclaves]
[   62.639541]  __x64_sys_ioctl+0x82/0xb0
[   62.642620]  do_syscall_64+0x3b/0x90
[   62.645642]  entry_SYSCALL_64_after_hwframe+0x44/0xae&lt;/p&gt;
&lt;p&gt;Use get_user_pages_unlocked() when setting the enclave memory regions.
That&amp;#39;s a similar pattern as mmap_read_lock() used together with
get_user_pages().&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;nitro_enclaves: Use get_user_pages_unlocked() call to handle mmap assert&lt;/p&gt;
&lt;p&gt;After commit 5b78ed24e8ec (&amp;#34;mm/pagemap: add mmap_assert_locked()
annotations to find_vma*()&amp;#34;), the call to get_user_pages() will trigger
the mmap assert.&lt;/p&gt;
&lt;p&gt;static inline void mmap_assert_locked(struct mm_struct *mm)
{
	lockdep_assert_held(&amp;amp;mm-&amp;gt;mmap_lock);
	VM_BUG_ON_MM(!rwsem_is_locked(&amp;amp;mm-&amp;gt;mmap_lock), mm);
}&lt;/p&gt;
&lt;p&gt;[   62.521410] kernel BUG at include/linux/mmap_lock.h:156!
...........................................................
[   62.538938] RIP: 0010:find_vma+0x32/0x80
...........................................................
[   62.605889] Call Trace:
[   62.608502]  &amp;lt;TASK&amp;gt;
[   62.610956]  ? lock_timer_base+0x61/0x80
[   62.614106]  find_extend_vma+0x19/0x80
[   62.617195]  __get_user_pages+0x9b/0x6a0
[   62.620356]  __gup_longterm_locked+0x42d/0x450
[   62.623721]  ? finish_wait+0x41/0x80
[   62.626748]  ? __kmalloc+0x178/0x2f0
[   62.629768]  ne_set_user_memory_region_ioctl.isra.0+0x225/0x6a0 [nitro_enclaves]
[   62.635776]  ne_enclave_ioctl+0x1cf/0x6d7 [nitro_enclaves]
[   62.639541]  __x64_sys_ioctl+0x82/0xb0
[   62.642620]  do_syscall_64+0x3b/0x90
[   62.645642]  entry_SYSCALL_64_after_hwframe+0x44/0xae&lt;/p&gt;
&lt;p&gt;Use get_user_pages_unlocked() when setting the enclave memory regions.
That&amp;#39;s a similar pattern as mmap_read_lock() used together with
get_user_pages().&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2021-46927</guid>
    </item>
    <item>
      <title>GHSA-4f2m-qf8w-84rw</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-4f2m-qf8w-84rw</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;nitro_enclaves: Use get_user_pages_unlocked() call to handle mmap assert&lt;/p&gt;
&lt;p&gt;After commit 5b78ed24e8ec (&amp;#34;mm/pagemap: add mmap_assert_locked()
annotations to find_vma*()&amp;#34;), the call to get_user_pages() will trigger
the mmap assert.&lt;/p&gt;
&lt;p&gt;static inline void mmap_assert_locked(struct mm_struct *mm)
{
	lockdep_assert_held(&amp;amp;mm-&amp;gt;mmap_lock);
	VM_BUG_ON_MM(!rwsem_is_locked(&amp;amp;mm-&amp;gt;mmap_lock), mm);
}&lt;/p&gt;
&lt;p&gt;[   62.521410] kernel BUG at include/linux/mmap_lock.h:156!
...........................................................
[   62.538938] RIP: 0010:find_vma+0x32/0x80
...........................................................
[   62.605889] Call Trace:
[   62.608502]  &amp;lt;TASK&amp;gt;
[   62.610956]  ? lock_timer_base+0x61/0x80
[   62.614106]  find_extend_vma+0x19/0x80
[   62.617195]  __get_user_pages+0x9b/0x6a0
[   62.620356]  __gup_longterm_locked+0x42d/0x450
[   62.623721]  ? finish_wait+0x41/0x80
[   62.626748]  ? __kmalloc+0x178/0x2f0
[   62.629768]  ne_set_user_memory_region_ioctl.isra.0+0x225/0x6a0 [nitro_enclaves]
[   62.635776]  ne_enclave_ioctl+0x1cf/0x6d7 [nitro_enclaves]
[   62.639541]  __x64_sys_ioctl+0x82/0xb0
[   62.642620]  do_syscall_64+0x3b/0x90
[   62.645642]  entry_SYSCALL_64_after_hwframe+0x44/0xae&lt;/p&gt;
&lt;p&gt;Use get_user_pages_unlocked() when setting the enclave memory regions.
That&amp;#39;s a similar pattern as mmap_read_lock() used together with
get_user_pages().&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;nitro_enclaves: Use get_user_pages_unlocked() call to handle mmap assert&lt;/p&gt;
&lt;p&gt;After commit 5b78ed24e8ec (&amp;#34;mm/pagemap: add mmap_assert_locked()
annotations to find_vma*()&amp;#34;), the call to get_user_pages() will trigger
the mmap assert.&lt;/p&gt;
&lt;p&gt;static inline void mmap_assert_locked(struct mm_struct *mm)
{
	lockdep_assert_held(&amp;amp;mm-&amp;gt;mmap_lock);
	VM_BUG_ON_MM(!rwsem_is_locked(&amp;amp;mm-&amp;gt;mmap_lock), mm);
}&lt;/p&gt;
&lt;p&gt;[   62.521410] kernel BUG at include/linux/mmap_lock.h:156!
...........................................................
[   62.538938] RIP: 0010:find_vma+0x32/0x80
...........................................................
[   62.605889] Call Trace:
[   62.608502]  &amp;lt;TASK&amp;gt;
[   62.610956]  ? lock_timer_base+0x61/0x80
[   62.614106]  find_extend_vma+0x19/0x80
[   62.617195]  __get_user_pages+0x9b/0x6a0
[   62.620356]  __gup_longterm_locked+0x42d/0x450
[   62.623721]  ? finish_wait+0x41/0x80
[   62.626748]  ? __kmalloc+0x178/0x2f0
[   62.629768]  ne_set_user_memory_region_ioctl.isra.0+0x225/0x6a0 [nitro_enclaves]
[   62.635776]  ne_enclave_ioctl+0x1cf/0x6d7 [nitro_enclaves]
[   62.639541]  __x64_sys_ioctl+0x82/0xb0
[   62.642620]  do_syscall_64+0x3b/0x90
[   62.645642]  entry_SYSCALL_64_after_hwframe+0x44/0xae&lt;/p&gt;
&lt;p&gt;Use get_user_pages_unlocked() when setting the enclave memory regions.
That&amp;#39;s a similar pattern as mmap_read_lock() used together with
get_user_pages().&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-4f2m-qf8w-84rw</guid>
    </item>
    <item>
      <title>gsd-2021-46927</title>
      <link>https://cve.radiocsirt.org/vuln/gsd-2021-46927</link>
      <description>gsd-2021-46927</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/gsd-2021-46927</guid>
    </item>
    <item>
      <title>SUSE-SU-2024:1320-1 — Security update for the Linux Kernel</title>
      <link>https://cve.radiocsirt.org/vuln/suse-su-2024:1320-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:1320-1</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2021-46927</title>
      <link>https://cve.radiocsirt.org/vuln/ubuntu-cve-2021-46927</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:16.04:LTS: linux-hwe-edge, Ubuntu:18.04:LTS: linux-aws-5.0, Ubuntu:18.04:LTS: linux-aws-5.3, Ubuntu:18.04:LTS: linux-azure, Ubuntu:18.04:LTS: linux-azure-5.3, Ubuntu:18.04:LTS: linux-azure-edge, Ubuntu:18.04:LTS: linux-gcp, Ubuntu:18.04:LTS: linux-gcp-5.3, Ubuntu:18.04:LTS: linux-gke-4.15, Ubuntu:18.04:LTS: linux-gke-5.4 and 54 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: nitro_enclaves: Use get_user_pages_unlocked() call to handle mmap assert After commit 5b78ed24e8ec (&amp;#34;mm/pagemap: add mmap_assert_locked() annotations to find_vma*()&amp;#34;), the call to get_user_pages() will trigger the mmap assert. static inline void mmap_assert_locked(struct mm_struct *mm) { 	lockdep_assert_held(&amp;amp;mm-&amp;gt;mmap_lock); 	VM_BUG_ON_MM(!rwsem_is_locked(&amp;amp;mm-&amp;gt;mmap_lock), mm); } [   62.521410] kernel BUG at include/linux/mmap_lock.h:156! ........................................................... [   62.538938] RIP: 0010:find_vma+0x32/0x80 ........................................................... [   62.605889] Call Trace: [   62.608502]  &amp;lt;TASK&amp;gt; [   62.610956]  ? lock_timer_base+0x61/0x80 [   62.614106]  find_extend_vma+0x19/0x80 [   62.617195]  __get_user_pages+0x9b/0x6a0 [   62.620356]  __gup_longterm_locked+0x42d/0x450 [   62.623721]  ? finish_wait+0x41/0x80 [   62.626748]  ? __kmalloc+0x178/0x2f0 [   62.629768]  ne_set_user_memory_region_ioctl.isra.0+0x225/0x6a0 [nitro_enclaves] [   62.635776]  ne_enclave_ioctl+0x1cf/0x6d7 [nitro_enclaves] [   62.639541]  __x64_sys_ioctl+0x82/0xb0 [   62.642620]  do_syscall_64+0x3b/0x90 [   62.645642]  entry_SYSCALL_64_after_hwframe+0x44/0xae Use get_user_pages_unlocked() when setting the enclave memory regions. That&amp;#39;s a similar pattern as mmap_read_lock() used together with get_user_pages().&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:16.04:LTS: linux-hwe-edge, Ubuntu:18.04:LTS: linux-aws-5.0, Ubuntu:18.04:LTS: linux-aws-5.3, Ubuntu:18.04:LTS: linux-azure, Ubuntu:18.04:LTS: linux-azure-5.3, Ubuntu:18.04:LTS: linux-azure-edge, Ubuntu:18.04:LTS: linux-gcp, Ubuntu:18.04:LTS: linux-gcp-5.3, Ubuntu:18.04:LTS: linux-gke-4.15, Ubuntu:18.04:LTS: linux-gke-5.4 and 54 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: nitro_enclaves: Use get_user_pages_unlocked() call to handle mmap assert After commit 5b78ed24e8ec (&amp;#34;mm/pagemap: add mmap_assert_locked() annotations to find_vma*()&amp;#34;), the call to get_user_pages() will trigger the mmap assert. static inline void mmap_assert_locked(struct mm_struct *mm) { 	lockdep_assert_held(&amp;amp;mm-&amp;gt;mmap_lock); 	VM_BUG_ON_MM(!rwsem_is_locked(&amp;amp;mm-&amp;gt;mmap_lock), mm); } [   62.521410] kernel BUG at include/linux/mmap_lock.h:156! ........................................................... [   62.538938] RIP: 0010:find_vma+0x32/0x80 ........................................................... [   62.605889] Call Trace: [   62.608502]  &amp;lt;TASK&amp;gt; [   62.610956]  ? lock_timer_base+0x61/0x80 [   62.614106]  find_extend_vma+0x19/0x80 [   62.617195]  __get_user_pages+0x9b/0x6a0 [   62.620356]  __gup_longterm_locked+0x42d/0x450 [   62.623721]  ? finish_wait+0x41/0x80 [   62.626748]  ? __kmalloc+0x178/0x2f0 [   62.629768]  ne_set_user_memory_region_ioctl.isra.0+0x225/0x6a0 [nitro_enclaves] [   62.635776]  ne_enclave_ioctl+0x1cf/0x6d7 [nitro_enclaves] [   62.639541]  __x64_sys_ioctl+0x82/0xb0 [   62.642620]  do_syscall_64+0x3b/0x90 [   62.645642]  entry_SYSCALL_64_after_hwframe+0x44/0xae Use get_user_pages_unlocked() when setting the enclave memory regions. That&amp;#39;s a similar pattern as mmap_read_lock() used together with get_user_pages().&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ubuntu-cve-2021-46927</guid>
    </item>
    <item>
      <title>WID-SEC-W-2024-0488 — Linux Kernel: Mehrere Schwachstellen ermöglichen nicht spezifizierten Angriff</title>
      <link>https://cve.radiocsirt.org/vuln/wid-sec-w-2024-0488</link>
      <description>&lt;p&gt;Ein lokaler Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um einen nicht näher spezifizierten Angriff durchzuführen.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Ein lokaler Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um einen nicht näher spezifizierten Angriff durchzuführen.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/wid-sec-w-2024-0488</guid>
    </item>
  </channel>
</rss>
