<?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 18:08:34 +0000</lastBuildDate>
    <item>
      <title>bdu:2025-00823</title>
      <link>https://cve.radiocsirt.org/vuln/bdu:2025-00823</link>
      <description>bdu:2025-00823</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/bdu:2025-00823</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-309462</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-309462</link>
      <description>EUVD-2026-309462</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-309462</guid>
    </item>
    <item>
      <title>fkie_cve-2021-46956</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2021-46956</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;virtiofs: fix memory leak in virtio_fs_probe()&lt;/p&gt;
&lt;p&gt;When accidentally passing twice the same tag to qemu, kmemleak ended up
reporting a memory leak in virtiofs.  Also, looking at the log I saw the
following error (that&amp;#39;s when I realised the duplicated tag):&lt;/p&gt;
&lt;p&gt;virtiofs: probe of virtio5 failed with error -17&lt;/p&gt;
&lt;p&gt;Here&amp;#39;s the kmemleak log for reference:&lt;/p&gt;
&lt;p&gt;unreferenced object 0xffff888103d47800 (size 1024):
  comm &amp;#34;systemd-udevd&amp;#34;, pid 118, jiffies 4294893780 (age 18.340s)
  hex dump (first 32 bytes):
    00 00 00 00 ad 4e ad de ff ff ff ff 00 00 00 00  .....N..........
    ff ff ff ff ff ff ff ff 80 90 02 a0 ff ff ff ff  ................
  backtrace:
    [&amp;lt;000000000ebb87c1&amp;gt;] virtio_fs_probe+0x171/0x7ae [virtiofs]
    [&amp;lt;00000000f8aca419&amp;gt;] virtio_dev_probe+0x15f/0x210
    [&amp;lt;000000004d6baf3c&amp;gt;] really_probe+0xea/0x430
    [&amp;lt;00000000a6ceeac8&amp;gt;] device_driver_attach+0xa8/0xb0
    [&amp;lt;00000000196f47a7&amp;gt;] __driver_attach+0x98/0x140
    [&amp;lt;000000000b20601d&amp;gt;] bus_for_each_dev+0x7b/0xc0
    [&amp;lt;00000000399c7b7f&amp;gt;] bus_add_driver+0x11b/0x1f0
    [&amp;lt;0000000032b09ba7&amp;gt;] driver_register+0x8f/0xe0
    [&amp;lt;00000000cdd55998&amp;gt;] 0xffffffffa002c013
    [&amp;lt;000000000ea196a2&amp;gt;] do_one_initcall+0x64/0x2e0
    [&amp;lt;0000000008f727ce&amp;gt;] do_init_module+0x5c/0x260
    [&amp;lt;000000003cdedab6&amp;gt;] __do_sys_finit_module+0xb5/0x120
    [&amp;lt;00000000ad2f48c6&amp;gt;] do_syscall_64+0x33/0x40
    [&amp;lt;00000000809526b5&amp;gt;] entry_SYSCALL_64_after_hwframe+0x44/0xae&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;virtiofs: fix memory leak in virtio_fs_probe()&lt;/p&gt;
&lt;p&gt;When accidentally passing twice the same tag to qemu, kmemleak ended up
reporting a memory leak in virtiofs.  Also, looking at the log I saw the
following error (that&amp;#39;s when I realised the duplicated tag):&lt;/p&gt;
&lt;p&gt;virtiofs: probe of virtio5 failed with error -17&lt;/p&gt;
&lt;p&gt;Here&amp;#39;s the kmemleak log for reference:&lt;/p&gt;
&lt;p&gt;unreferenced object 0xffff888103d47800 (size 1024):
  comm &amp;#34;systemd-udevd&amp;#34;, pid 118, jiffies 4294893780 (age 18.340s)
  hex dump (first 32 bytes):
    00 00 00 00 ad 4e ad de ff ff ff ff 00 00 00 00  .....N..........
    ff ff ff ff ff ff ff ff 80 90 02 a0 ff ff ff ff  ................
  backtrace:
    [&amp;lt;000000000ebb87c1&amp;gt;] virtio_fs_probe+0x171/0x7ae [virtiofs]
    [&amp;lt;00000000f8aca419&amp;gt;] virtio_dev_probe+0x15f/0x210
    [&amp;lt;000000004d6baf3c&amp;gt;] really_probe+0xea/0x430
    [&amp;lt;00000000a6ceeac8&amp;gt;] device_driver_attach+0xa8/0xb0
    [&amp;lt;00000000196f47a7&amp;gt;] __driver_attach+0x98/0x140
    [&amp;lt;000000000b20601d&amp;gt;] bus_for_each_dev+0x7b/0xc0
    [&amp;lt;00000000399c7b7f&amp;gt;] bus_add_driver+0x11b/0x1f0
    [&amp;lt;0000000032b09ba7&amp;gt;] driver_register+0x8f/0xe0
    [&amp;lt;00000000cdd55998&amp;gt;] 0xffffffffa002c013
    [&amp;lt;000000000ea196a2&amp;gt;] do_one_initcall+0x64/0x2e0
    [&amp;lt;0000000008f727ce&amp;gt;] do_init_module+0x5c/0x260
    [&amp;lt;000000003cdedab6&amp;gt;] __do_sys_finit_module+0xb5/0x120
    [&amp;lt;00000000ad2f48c6&amp;gt;] do_syscall_64+0x33/0x40
    [&amp;lt;00000000809526b5&amp;gt;] entry_SYSCALL_64_after_hwframe+0x44/0xae&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2021-46956</guid>
    </item>
    <item>
      <title>GHSA-7r25-m49h-vw58</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-7r25-m49h-vw58</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;virtiofs: fix memory leak in virtio_fs_probe()&lt;/p&gt;
&lt;p&gt;When accidentally passing twice the same tag to qemu, kmemleak ended up
reporting a memory leak in virtiofs.  Also, looking at the log I saw the
following error (that&amp;#39;s when I realised the duplicated tag):&lt;/p&gt;
&lt;p&gt;virtiofs: probe of virtio5 failed with error -17&lt;/p&gt;
&lt;p&gt;Here&amp;#39;s the kmemleak log for reference:&lt;/p&gt;
&lt;p&gt;unreferenced object 0xffff888103d47800 (size 1024):
  comm &amp;#34;systemd-udevd&amp;#34;, pid 118, jiffies 4294893780 (age 18.340s)
  hex dump (first 32 bytes):
    00 00 00 00 ad 4e ad de ff ff ff ff 00 00 00 00  .....N..........
    ff ff ff ff ff ff ff ff 80 90 02 a0 ff ff ff ff  ................
  backtrace:
    [&amp;lt;000000000ebb87c1&amp;gt;] virtio_fs_probe+0x171/0x7ae [virtiofs]
    [&amp;lt;00000000f8aca419&amp;gt;] virtio_dev_probe+0x15f/0x210
    [&amp;lt;000000004d6baf3c&amp;gt;] really_probe+0xea/0x430
    [&amp;lt;00000000a6ceeac8&amp;gt;] device_driver_attach+0xa8/0xb0
    [&amp;lt;00000000196f47a7&amp;gt;] __driver_attach+0x98/0x140
    [&amp;lt;000000000b20601d&amp;gt;] bus_for_each_dev+0x7b/0xc0
    [&amp;lt;00000000399c7b7f&amp;gt;] bus_add_driver+0x11b/0x1f0
    [&amp;lt;0000000032b09ba7&amp;gt;] driver_register+0x8f/0xe0
    [&amp;lt;00000000cdd55998&amp;gt;] 0xffffffffa002c013
    [&amp;lt;000000000ea196a2&amp;gt;] do_one_initcall+0x64/0x2e0
    [&amp;lt;0000000008f727ce&amp;gt;] do_init_module+0x5c/0x260
    [&amp;lt;000000003cdedab6&amp;gt;] __do_sys_finit_module+0xb5/0x120
    [&amp;lt;00000000ad2f48c6&amp;gt;] do_syscall_64+0x33/0x40
    [&amp;lt;00000000809526b5&amp;gt;] entry_SYSCALL_64_after_hwframe+0x44/0xae&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;virtiofs: fix memory leak in virtio_fs_probe()&lt;/p&gt;
&lt;p&gt;When accidentally passing twice the same tag to qemu, kmemleak ended up
reporting a memory leak in virtiofs.  Also, looking at the log I saw the
following error (that&amp;#39;s when I realised the duplicated tag):&lt;/p&gt;
&lt;p&gt;virtiofs: probe of virtio5 failed with error -17&lt;/p&gt;
&lt;p&gt;Here&amp;#39;s the kmemleak log for reference:&lt;/p&gt;
&lt;p&gt;unreferenced object 0xffff888103d47800 (size 1024):
  comm &amp;#34;systemd-udevd&amp;#34;, pid 118, jiffies 4294893780 (age 18.340s)
  hex dump (first 32 bytes):
    00 00 00 00 ad 4e ad de ff ff ff ff 00 00 00 00  .....N..........
    ff ff ff ff ff ff ff ff 80 90 02 a0 ff ff ff ff  ................
  backtrace:
    [&amp;lt;000000000ebb87c1&amp;gt;] virtio_fs_probe+0x171/0x7ae [virtiofs]
    [&amp;lt;00000000f8aca419&amp;gt;] virtio_dev_probe+0x15f/0x210
    [&amp;lt;000000004d6baf3c&amp;gt;] really_probe+0xea/0x430
    [&amp;lt;00000000a6ceeac8&amp;gt;] device_driver_attach+0xa8/0xb0
    [&amp;lt;00000000196f47a7&amp;gt;] __driver_attach+0x98/0x140
    [&amp;lt;000000000b20601d&amp;gt;] bus_for_each_dev+0x7b/0xc0
    [&amp;lt;00000000399c7b7f&amp;gt;] bus_add_driver+0x11b/0x1f0
    [&amp;lt;0000000032b09ba7&amp;gt;] driver_register+0x8f/0xe0
    [&amp;lt;00000000cdd55998&amp;gt;] 0xffffffffa002c013
    [&amp;lt;000000000ea196a2&amp;gt;] do_one_initcall+0x64/0x2e0
    [&amp;lt;0000000008f727ce&amp;gt;] do_init_module+0x5c/0x260
    [&amp;lt;000000003cdedab6&amp;gt;] __do_sys_finit_module+0xb5/0x120
    [&amp;lt;00000000ad2f48c6&amp;gt;] do_syscall_64+0x33/0x40
    [&amp;lt;00000000809526b5&amp;gt;] entry_SYSCALL_64_after_hwframe+0x44/0xae&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-7r25-m49h-vw58</guid>
    </item>
    <item>
      <title>gsd-2021-46956</title>
      <link>https://cve.radiocsirt.org/vuln/gsd-2021-46956</link>
      <description>gsd-2021-46956</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/gsd-2021-46956</guid>
    </item>
    <item>
      <title>SUSE-SU-2024:1465-1 — Security update for the Linux Kernel</title>
      <link>https://cve.radiocsirt.org/vuln/suse-su-2024:1465-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:1465-1</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2021-46956</title>
      <link>https://cve.radiocsirt.org/vuln/ubuntu-cve-2021-46956</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.4, Ubuntu:18.04:LTS: linux-azure-5.4, Ubuntu:18.04:LTS: linux-gcp-5.4, Ubuntu:18.04:LTS: linux-hwe-5.4, Ubuntu:18.04:LTS: linux-oracle-5.4, Ubuntu:18.04:LTS: linux-raspi-5.4, Ubuntu:18.04:LTS: linux-aws-5.0, Ubuntu:18.04:LTS: linux-aws-5.3, Ubuntu:18.04:LTS: linux-azure and 79 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: virtiofs: fix memory leak in virtio_fs_probe() When accidentally passing twice the same tag to qemu, kmemleak ended up reporting a memory leak in virtiofs.  Also, looking at the log I saw the following error (that&amp;#39;s when I realised the duplicated tag):   virtiofs: probe of virtio5 failed with error -17 Here&amp;#39;s the kmemleak log for reference: unreferenced object 0xffff888103d47800 (size 1024):   comm &amp;#34;systemd-udevd&amp;#34;, pid 118, jiffies 4294893780 (age 18.340s)   hex dump (first 32 bytes):     00 00 00 00 ad 4e ad de ff ff ff ff 00 00 00 00  .....N..........     ff ff ff ff ff ff ff ff 80 90 02 a0 ff ff ff ff  ................   backtrace:     [&amp;lt;000000000ebb87c1&amp;gt;] virtio_fs_probe+0x171/0x7ae [virtiofs]     [&amp;lt;00000000f8aca419&amp;gt;] virtio_dev_probe+0x15f/0x210     [&amp;lt;000000004d6baf3c&amp;gt;] really_probe+0xea/0x430     [&amp;lt;00000000a6ceeac8&amp;gt;] device_driver_attach+0xa8/0xb0     [&amp;lt;00000000196f47a7&amp;gt;] __driver_attach+0x98/0x140     [&amp;lt;000000000b20601d&amp;gt;] bus_for_each_dev+0x7b/0xc0     [&amp;lt;00000000399c7b7f&amp;gt;] bus_add_driver+0x11b/0x1f0     [&amp;lt;0000000032b09ba7&amp;gt;] driver_register+0x8f/0xe0     [&amp;lt;00000000cdd55998&amp;gt;] 0xffffffffa002c013     [&amp;lt;000000000ea196a2&amp;gt;] do_one_initcall+0x64/0x2e0     [&amp;lt;0000000008f727ce&amp;gt;] do_init_module+0x5c/0x260     [&amp;lt;000000003cdedab6&amp;gt;] __do_sys_finit_module+0xb5/0x120     [&amp;lt;00000000ad2f48c6&amp;gt;] do_syscall_64+0x33/0x40     [&amp;lt;00000000809526b5&amp;gt;] entry_SYSCALL_64_after_hwframe+0x44/0xae&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.4, Ubuntu:18.04:LTS: linux-azure-5.4, Ubuntu:18.04:LTS: linux-gcp-5.4, Ubuntu:18.04:LTS: linux-hwe-5.4, Ubuntu:18.04:LTS: linux-oracle-5.4, Ubuntu:18.04:LTS: linux-raspi-5.4, Ubuntu:18.04:LTS: linux-aws-5.0, Ubuntu:18.04:LTS: linux-aws-5.3, Ubuntu:18.04:LTS: linux-azure and 79 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: virtiofs: fix memory leak in virtio_fs_probe() When accidentally passing twice the same tag to qemu, kmemleak ended up reporting a memory leak in virtiofs.  Also, looking at the log I saw the following error (that&amp;#39;s when I realised the duplicated tag):   virtiofs: probe of virtio5 failed with error -17 Here&amp;#39;s the kmemleak log for reference: unreferenced object 0xffff888103d47800 (size 1024):   comm &amp;#34;systemd-udevd&amp;#34;, pid 118, jiffies 4294893780 (age 18.340s)   hex dump (first 32 bytes):     00 00 00 00 ad 4e ad de ff ff ff ff 00 00 00 00  .....N..........     ff ff ff ff ff ff ff ff 80 90 02 a0 ff ff ff ff  ................   backtrace:     [&amp;lt;000000000ebb87c1&amp;gt;] virtio_fs_probe+0x171/0x7ae [virtiofs]     [&amp;lt;00000000f8aca419&amp;gt;] virtio_dev_probe+0x15f/0x210     [&amp;lt;000000004d6baf3c&amp;gt;] really_probe+0xea/0x430     [&amp;lt;00000000a6ceeac8&amp;gt;] device_driver_attach+0xa8/0xb0     [&amp;lt;00000000196f47a7&amp;gt;] __driver_attach+0x98/0x140     [&amp;lt;000000000b20601d&amp;gt;] bus_for_each_dev+0x7b/0xc0     [&amp;lt;00000000399c7b7f&amp;gt;] bus_add_driver+0x11b/0x1f0     [&amp;lt;0000000032b09ba7&amp;gt;] driver_register+0x8f/0xe0     [&amp;lt;00000000cdd55998&amp;gt;] 0xffffffffa002c013     [&amp;lt;000000000ea196a2&amp;gt;] do_one_initcall+0x64/0x2e0     [&amp;lt;0000000008f727ce&amp;gt;] do_init_module+0x5c/0x260     [&amp;lt;000000003cdedab6&amp;gt;] __do_sys_finit_module+0xb5/0x120     [&amp;lt;00000000ad2f48c6&amp;gt;] do_syscall_64+0x33/0x40     [&amp;lt;00000000809526b5&amp;gt;] entry_SYSCALL_64_after_hwframe+0x44/0xae&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ubuntu-cve-2021-46956</guid>
    </item>
    <item>
      <title>WID-SEC-W-2024-0500 — Linux Kernel: Mehrere Schwachstellen ermöglichen nicht spezifizierten Angriff</title>
      <link>https://cve.radiocsirt.org/vuln/wid-sec-w-2024-0500</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-0500</guid>
    </item>
  </channel>
</rss>
