<?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>Sat, 03 Oct 2026 09:03:20 +0000</lastBuildDate>
    <item>
      <title>bdu:2026-05774</title>
      <link>https://cve.radiocsirt.org/vuln/bdu:2026-05774</link>
      <description>bdu:2026-05774</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/bdu:2026-05774</guid>
    </item>
    <item>
      <title>certfr-2025-avi-0509 — 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-2025-avi-0509</link>
      <description>certfr-2025-avi-0509</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/certfr-2025-avi-0509</guid>
    </item>
    <item>
      <title>EUVD-2026-310846</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-310846</link>
      <description>EUVD-2026-310846</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-310846</guid>
    </item>
    <item>
      <title>fkie_cve-2022-49830</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2022-49830</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;drm/drv: Fix potential memory leak in drm_dev_init()&lt;/p&gt;
&lt;p&gt;drm_dev_init() will add drm_dev_init_release() as a callback. When
drmm_add_action() failed, the release function won&amp;#39;t be added. As the
result, the ref cnt added by device_get() in drm_dev_init() won&amp;#39;t be put
by drm_dev_init_release(), which leads to the memleak. Use
drmm_add_action_or_reset() instead of drmm_add_action() to prevent
memleak.&lt;/p&gt;
&lt;p&gt;unreferenced object 0xffff88810bc0c800 (size 2048):
  comm &amp;#34;modprobe&amp;#34;, pid 8322, jiffies 4305809845 (age 15.292s)
  hex dump (first 32 bytes):
    e8 cc c0 0b 81 88 ff ff ff ff ff ff 00 00 00 00  ................
    20 24 3c 0c 81 88 ff ff 18 c8 c0 0b 81 88 ff ff   $&amp;lt;.............
  backtrace:
    [&amp;lt;000000007251f72d&amp;gt;] __kmalloc+0x4b/0x1c0
    [&amp;lt;0000000045f21f26&amp;gt;] platform_device_alloc+0x2d/0xe0
    [&amp;lt;000000004452a479&amp;gt;] platform_device_register_full+0x24/0x1c0
    [&amp;lt;0000000089f4ea61&amp;gt;] 0xffffffffa0736051
    [&amp;lt;00000000235b2441&amp;gt;] do_one_initcall+0x7a/0x380
    [&amp;lt;0000000001a4a177&amp;gt;] do_init_module+0x5c/0x230
    [&amp;lt;000000002bf8a8e2&amp;gt;] load_module+0x227d/0x2420
    [&amp;lt;00000000637d6d0a&amp;gt;] __do_sys_finit_module+0xd5/0x140
    [&amp;lt;00000000c99fc324&amp;gt;] do_syscall_64+0x3f/0x90
    [&amp;lt;000000004d85aa77&amp;gt;] entry_SYSCALL_64_after_hwframe+0x63/0xcd&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;drm/drv: Fix potential memory leak in drm_dev_init()&lt;/p&gt;
&lt;p&gt;drm_dev_init() will add drm_dev_init_release() as a callback. When
drmm_add_action() failed, the release function won&amp;#39;t be added. As the
result, the ref cnt added by device_get() in drm_dev_init() won&amp;#39;t be put
by drm_dev_init_release(), which leads to the memleak. Use
drmm_add_action_or_reset() instead of drmm_add_action() to prevent
memleak.&lt;/p&gt;
&lt;p&gt;unreferenced object 0xffff88810bc0c800 (size 2048):
  comm &amp;#34;modprobe&amp;#34;, pid 8322, jiffies 4305809845 (age 15.292s)
  hex dump (first 32 bytes):
    e8 cc c0 0b 81 88 ff ff ff ff ff ff 00 00 00 00  ................
    20 24 3c 0c 81 88 ff ff 18 c8 c0 0b 81 88 ff ff   $&amp;lt;.............
  backtrace:
    [&amp;lt;000000007251f72d&amp;gt;] __kmalloc+0x4b/0x1c0
    [&amp;lt;0000000045f21f26&amp;gt;] platform_device_alloc+0x2d/0xe0
    [&amp;lt;000000004452a479&amp;gt;] platform_device_register_full+0x24/0x1c0
    [&amp;lt;0000000089f4ea61&amp;gt;] 0xffffffffa0736051
    [&amp;lt;00000000235b2441&amp;gt;] do_one_initcall+0x7a/0x380
    [&amp;lt;0000000001a4a177&amp;gt;] do_init_module+0x5c/0x230
    [&amp;lt;000000002bf8a8e2&amp;gt;] load_module+0x227d/0x2420
    [&amp;lt;00000000637d6d0a&amp;gt;] __do_sys_finit_module+0xd5/0x140
    [&amp;lt;00000000c99fc324&amp;gt;] do_syscall_64+0x3f/0x90
    [&amp;lt;000000004d85aa77&amp;gt;] entry_SYSCALL_64_after_hwframe+0x63/0xcd&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2022-49830</guid>
    </item>
    <item>
      <title>GHSA-7fmq-qw39-x2x2</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-7fmq-qw39-x2x2</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;drm/drv: Fix potential memory leak in drm_dev_init()&lt;/p&gt;
&lt;p&gt;drm_dev_init() will add drm_dev_init_release() as a callback. When
drmm_add_action() failed, the release function won&amp;#39;t be added. As the
result, the ref cnt added by device_get() in drm_dev_init() won&amp;#39;t be put
by drm_dev_init_release(), which leads to the memleak. Use
drmm_add_action_or_reset() instead of drmm_add_action() to prevent
memleak.&lt;/p&gt;
&lt;p&gt;unreferenced object 0xffff88810bc0c800 (size 2048):
  comm &amp;#34;modprobe&amp;#34;, pid 8322, jiffies 4305809845 (age 15.292s)
  hex dump (first 32 bytes):
    e8 cc c0 0b 81 88 ff ff ff ff ff ff 00 00 00 00  ................
    20 24 3c 0c 81 88 ff ff 18 c8 c0 0b 81 88 ff ff   $&amp;lt;.............
  backtrace:
    [&amp;lt;000000007251f72d&amp;gt;] __kmalloc+0x4b/0x1c0
    [&amp;lt;0000000045f21f26&amp;gt;] platform_device_alloc+0x2d/0xe0
    [&amp;lt;000000004452a479&amp;gt;] platform_device_register_full+0x24/0x1c0
    [&amp;lt;0000000089f4ea61&amp;gt;] 0xffffffffa0736051
    [&amp;lt;00000000235b2441&amp;gt;] do_one_initcall+0x7a/0x380
    [&amp;lt;0000000001a4a177&amp;gt;] do_init_module+0x5c/0x230
    [&amp;lt;000000002bf8a8e2&amp;gt;] load_module+0x227d/0x2420
    [&amp;lt;00000000637d6d0a&amp;gt;] __do_sys_finit_module+0xd5/0x140
    [&amp;lt;00000000c99fc324&amp;gt;] do_syscall_64+0x3f/0x90
    [&amp;lt;000000004d85aa77&amp;gt;] entry_SYSCALL_64_after_hwframe+0x63/0xcd&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;drm/drv: Fix potential memory leak in drm_dev_init()&lt;/p&gt;
&lt;p&gt;drm_dev_init() will add drm_dev_init_release() as a callback. When
drmm_add_action() failed, the release function won&amp;#39;t be added. As the
result, the ref cnt added by device_get() in drm_dev_init() won&amp;#39;t be put
by drm_dev_init_release(), which leads to the memleak. Use
drmm_add_action_or_reset() instead of drmm_add_action() to prevent
memleak.&lt;/p&gt;
&lt;p&gt;unreferenced object 0xffff88810bc0c800 (size 2048):
  comm &amp;#34;modprobe&amp;#34;, pid 8322, jiffies 4305809845 (age 15.292s)
  hex dump (first 32 bytes):
    e8 cc c0 0b 81 88 ff ff ff ff ff ff 00 00 00 00  ................
    20 24 3c 0c 81 88 ff ff 18 c8 c0 0b 81 88 ff ff   $&amp;lt;.............
  backtrace:
    [&amp;lt;000000007251f72d&amp;gt;] __kmalloc+0x4b/0x1c0
    [&amp;lt;0000000045f21f26&amp;gt;] platform_device_alloc+0x2d/0xe0
    [&amp;lt;000000004452a479&amp;gt;] platform_device_register_full+0x24/0x1c0
    [&amp;lt;0000000089f4ea61&amp;gt;] 0xffffffffa0736051
    [&amp;lt;00000000235b2441&amp;gt;] do_one_initcall+0x7a/0x380
    [&amp;lt;0000000001a4a177&amp;gt;] do_init_module+0x5c/0x230
    [&amp;lt;000000002bf8a8e2&amp;gt;] load_module+0x227d/0x2420
    [&amp;lt;00000000637d6d0a&amp;gt;] __do_sys_finit_module+0xd5/0x140
    [&amp;lt;00000000c99fc324&amp;gt;] do_syscall_64+0x3f/0x90
    [&amp;lt;000000004d85aa77&amp;gt;] entry_SYSCALL_64_after_hwframe+0x63/0xcd&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-7fmq-qw39-x2x2</guid>
    </item>
    <item>
      <title>SUSE-SU-2025:01918-1 — Security update for the Linux Kernel</title>
      <link>https://cve.radiocsirt.org/vuln/suse-su-2025:01918-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-2025:01918-1</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2022-49830</title>
      <link>https://cve.radiocsirt.org/vuln/ubuntu-cve-2022-49830</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 95 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: drm/drv: Fix potential memory leak in drm_dev_init() drm_dev_init() will add drm_dev_init_release() as a callback. When drmm_add_action() failed, the release function won&amp;#39;t be added. As the result, the ref cnt added by device_get() in drm_dev_init() won&amp;#39;t be put by drm_dev_init_release(), which leads to the memleak. Use drmm_add_action_or_reset() instead of drmm_add_action() to prevent memleak. unreferenced object 0xffff88810bc0c800 (size 2048):   comm &amp;#34;modprobe&amp;#34;, pid 8322, jiffies 4305809845 (age 15.292s)   hex dump (first 32 bytes):     e8 cc c0 0b 81 88 ff ff ff ff ff ff 00 00 00 00  ................     20 24 3c 0c 81 88 ff ff 18 c8 c0 0b 81 88 ff ff   $&amp;lt;.............   backtrace:     [&amp;lt;000000007251f72d&amp;gt;] __kmalloc+0x4b/0x1c0     [&amp;lt;0000000045f21f26&amp;gt;] platform_device_alloc+0x2d/0xe0     [&amp;lt;000000004452a479&amp;gt;] platform_device_register_full+0x24/0x1c0     [&amp;lt;0000000089f4ea61&amp;gt;] 0xffffffffa0736051     [&amp;lt;00000000235b2441&amp;gt;] do_one_initcall+0x7a/0x380     [&amp;lt;0000000001a4a177&amp;gt;] do_init_module+0x5c/0x230     [&amp;lt;000000002bf8a8e2&amp;gt;] load_module+0x227d/0x2420     [&amp;lt;00000000637d6d0a&amp;gt;] __do_sys_finit_module+0xd5/0x140     [&amp;lt;00000000c99fc324&amp;gt;] do_syscall_64+0x3f/0x90     [&amp;lt;000000004d85aa77&amp;gt;] entry_SYSCALL_64_after_hwframe+0x63/0xcd&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 95 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: drm/drv: Fix potential memory leak in drm_dev_init() drm_dev_init() will add drm_dev_init_release() as a callback. When drmm_add_action() failed, the release function won&amp;#39;t be added. As the result, the ref cnt added by device_get() in drm_dev_init() won&amp;#39;t be put by drm_dev_init_release(), which leads to the memleak. Use drmm_add_action_or_reset() instead of drmm_add_action() to prevent memleak. unreferenced object 0xffff88810bc0c800 (size 2048):   comm &amp;#34;modprobe&amp;#34;, pid 8322, jiffies 4305809845 (age 15.292s)   hex dump (first 32 bytes):     e8 cc c0 0b 81 88 ff ff ff ff ff ff 00 00 00 00  ................     20 24 3c 0c 81 88 ff ff 18 c8 c0 0b 81 88 ff ff   $&amp;lt;.............   backtrace:     [&amp;lt;000000007251f72d&amp;gt;] __kmalloc+0x4b/0x1c0     [&amp;lt;0000000045f21f26&amp;gt;] platform_device_alloc+0x2d/0xe0     [&amp;lt;000000004452a479&amp;gt;] platform_device_register_full+0x24/0x1c0     [&amp;lt;0000000089f4ea61&amp;gt;] 0xffffffffa0736051     [&amp;lt;00000000235b2441&amp;gt;] do_one_initcall+0x7a/0x380     [&amp;lt;0000000001a4a177&amp;gt;] do_init_module+0x5c/0x230     [&amp;lt;000000002bf8a8e2&amp;gt;] load_module+0x227d/0x2420     [&amp;lt;00000000637d6d0a&amp;gt;] __do_sys_finit_module+0xd5/0x140     [&amp;lt;00000000c99fc324&amp;gt;] do_syscall_64+0x3f/0x90     [&amp;lt;000000004d85aa77&amp;gt;] entry_SYSCALL_64_after_hwframe+0x63/0xcd&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ubuntu-cve-2022-49830</guid>
    </item>
  </channel>
</rss>
