<?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 19:05:56 +0000</lastBuildDate>
    <item>
      <title>bdu:2024-06533</title>
      <link>https://cve.radiocsirt.org/vuln/bdu:2024-06533</link>
      <description>bdu:2024-06533</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/bdu:2024-06533</guid>
    </item>
    <item>
      <title>certfr-2024-avi-0693 — De multiples vulnérabilités ont été découvertes dans le noyau Linux de SUSE. Certaines d'entre elles permettent à un at…</title>
      <link>https://cve.radiocsirt.org/vuln/certfr-2024-avi-0693</link>
      <description>certfr-2024-avi-0693</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/certfr-2024-avi-0693</guid>
    </item>
    <item>
      <title>EUVD-2026-344600</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-344600</link>
      <description>EUVD-2026-344600</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-344600</guid>
    </item>
    <item>
      <title>fkie_cve-2022-48847</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2022-48847</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;watch_queue: Fix filter limit check&lt;/p&gt;
&lt;p&gt;In watch_queue_set_filter(), there are a couple of places where we check
that the filter type value does not exceed what the type_filter bitmap
can hold.  One place calculates the number of bits by:&lt;/p&gt;
&lt;p&gt;if (tf[i].type &amp;gt;= sizeof(wfilter-&amp;gt;type_filter) * 8)&lt;/p&gt;
&lt;p&gt;which is fine, but the second does:&lt;/p&gt;
&lt;p&gt;if (tf[i].type &amp;gt;= sizeof(wfilter-&amp;gt;type_filter) * BITS_PER_LONG)&lt;/p&gt;
&lt;p&gt;which is not.  This can lead to a couple of out-of-bounds writes due to
a too-large type:&lt;/p&gt;
&lt;p&gt;(1) __set_bit() on wfilter-&amp;gt;type_filter
 (2) Writing more elements in wfilter-&amp;gt;filters[] than we allocated.&lt;/p&gt;
&lt;p&gt;Fix this by just using the proper WATCH_TYPE__NR instead, which is the
number of types we actually know about.&lt;/p&gt;
&lt;p&gt;The bug may cause an oops looking something like:&lt;/p&gt;
&lt;p&gt;BUG: KASAN: slab-out-of-bounds in watch_queue_set_filter+0x659/0x740
  Write of size 4 at addr ffff88800d2c66bc by task watch_queue_oob/611
  ...
  Call Trace:
   &amp;lt;TASK&amp;gt;
   dump_stack_lvl+0x45/0x59
   print_address_description.constprop.0+0x1f/0x150
   ...
   kasan_report.cold+0x7f/0x11b
   ...
   watch_queue_set_filter+0x659/0x740
   ...
   __x64_sys_ioctl+0x127/0x190
   do_syscall_64+0x43/0x90
   entry_SYSCALL_64_after_hwframe+0x44/0xae&lt;/p&gt;
&lt;p&gt;Allocated by task 611:
   kasan_save_stack+0x1e/0x40
   __kasan_kmalloc+0x81/0xa0
   watch_queue_set_filter+0x23a/0x740
   __x64_sys_ioctl+0x127/0x190
   do_syscall_64+0x43/0x90
   entry_SYSCALL_64_after_hwframe+0x44/0xa…&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;watch_queue: Fix filter limit check&lt;/p&gt;
&lt;p&gt;In watch_queue_set_filter(), there are a couple of places where we check
that the filter type value does not exceed what the type_filter bitmap
can hold.  One place calculates the number of bits by:&lt;/p&gt;
&lt;p&gt;if (tf[i].type &amp;gt;= sizeof(wfilter-&amp;gt;type_filter) * 8)&lt;/p&gt;
&lt;p&gt;which is fine, but the second does:&lt;/p&gt;
&lt;p&gt;if (tf[i].type &amp;gt;= sizeof(wfilter-&amp;gt;type_filter) * BITS_PER_LONG)&lt;/p&gt;
&lt;p&gt;which is not.  This can lead to a couple of out-of-bounds writes due to
a too-large type:&lt;/p&gt;
&lt;p&gt;(1) __set_bit() on wfilter-&amp;gt;type_filter
 (2) Writing more elements in wfilter-&amp;gt;filters[] than we allocated.&lt;/p&gt;
&lt;p&gt;Fix this by just using the proper WATCH_TYPE__NR instead, which is the
number of types we actually know about.&lt;/p&gt;
&lt;p&gt;The bug may cause an oops looking something like:&lt;/p&gt;
&lt;p&gt;BUG: KASAN: slab-out-of-bounds in watch_queue_set_filter+0x659/0x740
  Write of size 4 at addr ffff88800d2c66bc by task watch_queue_oob/611
  ...
  Call Trace:
   &amp;lt;TASK&amp;gt;
   dump_stack_lvl+0x45/0x59
   print_address_description.constprop.0+0x1f/0x150
   ...
   kasan_report.cold+0x7f/0x11b
   ...
   watch_queue_set_filter+0x659/0x740
   ...
   __x64_sys_ioctl+0x127/0x190
   do_syscall_64+0x43/0x90
   entry_SYSCALL_64_after_hwframe+0x44/0xae&lt;/p&gt;
&lt;p&gt;Allocated by task 611:
   kasan_save_stack+0x1e/0x40
   __kasan_kmalloc+0x81/0xa0
   watch_queue_set_filter+0x23a/0x740
   __x64_sys_ioctl+0x127/0x190
   do_syscall_64+0x43/0x90
   entry_SYSCALL_64_after_hwframe+0x44/0xa…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2022-48847</guid>
    </item>
    <item>
      <title>GHSA-wgcq-m83r-f344</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-wgcq-m83r-f344</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;watch_queue: Fix filter limit check&lt;/p&gt;
&lt;p&gt;In watch_queue_set_filter(), there are a couple of places where we check
that the filter type value does not exceed what the type_filter bitmap
can hold.  One place calculates the number of bits by:&lt;/p&gt;
&lt;p&gt;if (tf[i].type &amp;gt;= sizeof(wfilter-&amp;gt;type_filter) * 8)&lt;/p&gt;
&lt;p&gt;which is fine, but the second does:&lt;/p&gt;
&lt;p&gt;if (tf[i].type &amp;gt;= sizeof(wfilter-&amp;gt;type_filter) * BITS_PER_LONG)&lt;/p&gt;
&lt;p&gt;which is not.  This can lead to a couple of out-of-bounds writes due to
a too-large type:&lt;/p&gt;
&lt;p&gt;(1) __set_bit() on wfilter-&amp;gt;type_filter
 (2) Writing more elements in wfilter-&amp;gt;filters[] than we allocated.&lt;/p&gt;
&lt;p&gt;Fix this by just using the proper WATCH_TYPE__NR instead, which is the
number of types we actually know about.&lt;/p&gt;
&lt;p&gt;The bug may cause an oops looking something like:&lt;/p&gt;
&lt;p&gt;BUG: KASAN: slab-out-of-bounds in watch_queue_set_filter+0x659/0x740
  Write of size 4 at addr ffff88800d2c66bc by task watch_queue_oob/611
  ...
  Call Trace:
   &amp;lt;TASK&amp;gt;
   dump_stack_lvl+0x45/0x59
   print_address_description.constprop.0+0x1f/0x150
   ...
   kasan_report.cold+0x7f/0x11b
   ...
   watch_queue_set_filter+0x659/0x740
   ...
   __x64_sys_ioctl+0x127/0x190
   do_syscall_64+0x43/0x90
   entry_SYSCALL_64_after_hwframe+0x44/0xae&lt;/p&gt;
&lt;p&gt;Allocated by task 611:
   kasan_save_stack+0x1e/0x40
   __kasan_kmalloc+0x81/0xa0
   watch_queue_set_filter+0x23a/0x740
   __x64_sys_ioctl+0x127/0x190
   do_syscall_64+0x43/0x90
   entry_SYSCALL_64_after_hwframe+0x44/0xa…&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;watch_queue: Fix filter limit check&lt;/p&gt;
&lt;p&gt;In watch_queue_set_filter(), there are a couple of places where we check
that the filter type value does not exceed what the type_filter bitmap
can hold.  One place calculates the number of bits by:&lt;/p&gt;
&lt;p&gt;if (tf[i].type &amp;gt;= sizeof(wfilter-&amp;gt;type_filter) * 8)&lt;/p&gt;
&lt;p&gt;which is fine, but the second does:&lt;/p&gt;
&lt;p&gt;if (tf[i].type &amp;gt;= sizeof(wfilter-&amp;gt;type_filter) * BITS_PER_LONG)&lt;/p&gt;
&lt;p&gt;which is not.  This can lead to a couple of out-of-bounds writes due to
a too-large type:&lt;/p&gt;
&lt;p&gt;(1) __set_bit() on wfilter-&amp;gt;type_filter
 (2) Writing more elements in wfilter-&amp;gt;filters[] than we allocated.&lt;/p&gt;
&lt;p&gt;Fix this by just using the proper WATCH_TYPE__NR instead, which is the
number of types we actually know about.&lt;/p&gt;
&lt;p&gt;The bug may cause an oops looking something like:&lt;/p&gt;
&lt;p&gt;BUG: KASAN: slab-out-of-bounds in watch_queue_set_filter+0x659/0x740
  Write of size 4 at addr ffff88800d2c66bc by task watch_queue_oob/611
  ...
  Call Trace:
   &amp;lt;TASK&amp;gt;
   dump_stack_lvl+0x45/0x59
   print_address_description.constprop.0+0x1f/0x150
   ...
   kasan_report.cold+0x7f/0x11b
   ...
   watch_queue_set_filter+0x659/0x740
   ...
   __x64_sys_ioctl+0x127/0x190
   do_syscall_64+0x43/0x90
   entry_SYSCALL_64_after_hwframe+0x44/0xae&lt;/p&gt;
&lt;p&gt;Allocated by task 611:
   kasan_save_stack+0x1e/0x40
   __kasan_kmalloc+0x81/0xa0
   watch_queue_set_filter+0x23a/0x740
   __x64_sys_ioctl+0x127/0x190
   do_syscall_64+0x43/0x90
   entry_SYSCALL_64_after_hwframe+0x44/0xa…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-wgcq-m83r-f344</guid>
    </item>
    <item>
      <title>SUSE-SU-2024:2894-1 — Security update for the Linux Kernel</title>
      <link>https://cve.radiocsirt.org/vuln/suse-su-2024:2894-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:2894-1</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2022-48847</title>
      <link>https://cve.radiocsirt.org/vuln/ubuntu-cve-2022-48847</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 61 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: watch_queue: Fix filter limit check In watch_queue_set_filter(), there are a couple of places where we check that the filter type value does not exceed what the type_filter bitmap can hold.  One place calculates the number of bits by:    if (tf[i].type &amp;gt;= sizeof(wfilter-&amp;gt;type_filter) * 8) which is fine, but the second does:    if (tf[i].type &amp;gt;= sizeof(wfilter-&amp;gt;type_filter) * BITS_PER_LONG) which is not.  This can lead to a couple of out-of-bounds writes due to a too-large type:  (1) __set_bit() on wfilter-&amp;gt;type_filter  (2) Writing more elements in wfilter-&amp;gt;filters[] than we allocated. Fix this by just using the proper WATCH_TYPE__NR instead, which is the number of types we actually know about. The bug may cause an oops looking something like:   BUG: KASAN: slab-out-of-bounds in watch_queue_set_filter+0x659/0x740   Write of size 4 at addr ffff88800d2c66bc by task watch_queue_oob/611   ...   Call Trace:    &amp;lt;TASK&amp;gt;    dump_stack_lvl+0x45/0x59    print_address_description.constprop.0+0x1f/0x150    ...    kasan_report.cold+0x7f/0x11b    ...    watch_queue_set_filter+0x659/0x740    ...    __x64_sys_ioctl+0x127/0x190    do_syscall_64+0x43/0x90    entry_SYSCALL_64_after_hwframe+0x44/0xae   Allocated by task 611:    kasan_save_stack+0x1e/0x40    __kasan_kmalloc+0x81/0xa0    watch_queue_set_filter+0x23a/0x740    __x64_sys_ioctl+0x127/0x190    do_syscall_64+0x43/0x90    entry_SYSCALL_64_after_hwframe+0x44/0xae   The bug…&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 61 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: watch_queue: Fix filter limit check In watch_queue_set_filter(), there are a couple of places where we check that the filter type value does not exceed what the type_filter bitmap can hold.  One place calculates the number of bits by:    if (tf[i].type &amp;gt;= sizeof(wfilter-&amp;gt;type_filter) * 8) which is fine, but the second does:    if (tf[i].type &amp;gt;= sizeof(wfilter-&amp;gt;type_filter) * BITS_PER_LONG) which is not.  This can lead to a couple of out-of-bounds writes due to a too-large type:  (1) __set_bit() on wfilter-&amp;gt;type_filter  (2) Writing more elements in wfilter-&amp;gt;filters[] than we allocated. Fix this by just using the proper WATCH_TYPE__NR instead, which is the number of types we actually know about. The bug may cause an oops looking something like:   BUG: KASAN: slab-out-of-bounds in watch_queue_set_filter+0x659/0x740   Write of size 4 at addr ffff88800d2c66bc by task watch_queue_oob/611   ...   Call Trace:    &amp;lt;TASK&amp;gt;    dump_stack_lvl+0x45/0x59    print_address_description.constprop.0+0x1f/0x150    ...    kasan_report.cold+0x7f/0x11b    ...    watch_queue_set_filter+0x659/0x740    ...    __x64_sys_ioctl+0x127/0x190    do_syscall_64+0x43/0x90    entry_SYSCALL_64_after_hwframe+0x44/0xae   Allocated by task 611:    kasan_save_stack+0x1e/0x40    __kasan_kmalloc+0x81/0xa0    watch_queue_set_filter+0x23a/0x740    __x64_sys_ioctl+0x127/0x190    do_syscall_64+0x43/0x90    entry_SYSCALL_64_after_hwframe+0x44/0xae   The bug…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ubuntu-cve-2022-48847</guid>
    </item>
    <item>
      <title>WID-SEC-W-2024-1625 — Linux Kernel: Mehrere Schwachstellen ermöglichen nicht spezifizierten Angriff</title>
      <link>https://cve.radiocsirt.org/vuln/wid-sec-w-2024-1625</link>
      <description>&lt;p&gt;Ein 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 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-1625</guid>
    </item>
  </channel>
</rss>
