<?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 19:43:09 +0000</lastBuildDate>
    <item>
      <title>bdu:2026-03848</title>
      <link>https://cve.radiocsirt.org/vuln/bdu:2026-03848</link>
      <description>bdu:2026-03848</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/bdu:2026-03848</guid>
    </item>
    <item>
      <title>certfr-2025-avi-1032 — 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-1032</link>
      <description>certfr-2025-avi-1032</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/certfr-2025-avi-1032</guid>
    </item>
    <item>
      <title>EUVD-2026-311316</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-311316</link>
      <description>EUVD-2026-311316</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-311316</guid>
    </item>
    <item>
      <title>fkie_cve-2022-50566</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2022-50566</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;mtd: Fix device name leak when register device failed in add_mtd_device()&lt;/p&gt;
&lt;p&gt;There is a kmemleak when register device failed:
  unreferenced object 0xffff888101aab550 (size 8):
    comm &amp;#34;insmod&amp;#34;, pid 3922, jiffies 4295277753 (age 925.408s)
    hex dump (first 8 bytes):
      6d 74 64 30 00 88 ff ff                          mtd0....
    backtrace:
      [&amp;lt;00000000bde26724&amp;gt;] __kmalloc_node_track_caller+0x4e/0x150
      [&amp;lt;000000003c32b416&amp;gt;] kvasprintf+0xb0/0x130
      [&amp;lt;000000001f7a8f15&amp;gt;] kobject_set_name_vargs+0x2f/0xb0
      [&amp;lt;000000006e781163&amp;gt;] dev_set_name+0xab/0xe0
      [&amp;lt;00000000e30d0c78&amp;gt;] add_mtd_device+0x4bb/0x700
      [&amp;lt;00000000f3d34de7&amp;gt;] mtd_device_parse_register+0x2ac/0x3f0
      [&amp;lt;00000000c0d88488&amp;gt;] 0xffffffffa0238457
      [&amp;lt;00000000b40d0922&amp;gt;] 0xffffffffa02a008f
      [&amp;lt;0000000023d17b9d&amp;gt;] do_one_initcall+0x87/0x2a0
      [&amp;lt;00000000770f6ca6&amp;gt;] do_init_module+0xdf/0x320
      [&amp;lt;000000007b6768fe&amp;gt;] load_module+0x2f98/0x3330
      [&amp;lt;00000000346bed5a&amp;gt;] __do_sys_finit_module+0x113/0x1b0
      [&amp;lt;00000000674c2290&amp;gt;] do_syscall_64+0x35/0x80
      [&amp;lt;000000004c6a8d97&amp;gt;] entry_SYSCALL_64_after_hwframe+0x46/0xb0&lt;/p&gt;
&lt;p&gt;If register device failed, should call put_device() to give up the
reference.&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;mtd: Fix device name leak when register device failed in add_mtd_device()&lt;/p&gt;
&lt;p&gt;There is a kmemleak when register device failed:
  unreferenced object 0xffff888101aab550 (size 8):
    comm &amp;#34;insmod&amp;#34;, pid 3922, jiffies 4295277753 (age 925.408s)
    hex dump (first 8 bytes):
      6d 74 64 30 00 88 ff ff                          mtd0....
    backtrace:
      [&amp;lt;00000000bde26724&amp;gt;] __kmalloc_node_track_caller+0x4e/0x150
      [&amp;lt;000000003c32b416&amp;gt;] kvasprintf+0xb0/0x130
      [&amp;lt;000000001f7a8f15&amp;gt;] kobject_set_name_vargs+0x2f/0xb0
      [&amp;lt;000000006e781163&amp;gt;] dev_set_name+0xab/0xe0
      [&amp;lt;00000000e30d0c78&amp;gt;] add_mtd_device+0x4bb/0x700
      [&amp;lt;00000000f3d34de7&amp;gt;] mtd_device_parse_register+0x2ac/0x3f0
      [&amp;lt;00000000c0d88488&amp;gt;] 0xffffffffa0238457
      [&amp;lt;00000000b40d0922&amp;gt;] 0xffffffffa02a008f
      [&amp;lt;0000000023d17b9d&amp;gt;] do_one_initcall+0x87/0x2a0
      [&amp;lt;00000000770f6ca6&amp;gt;] do_init_module+0xdf/0x320
      [&amp;lt;000000007b6768fe&amp;gt;] load_module+0x2f98/0x3330
      [&amp;lt;00000000346bed5a&amp;gt;] __do_sys_finit_module+0x113/0x1b0
      [&amp;lt;00000000674c2290&amp;gt;] do_syscall_64+0x35/0x80
      [&amp;lt;000000004c6a8d97&amp;gt;] entry_SYSCALL_64_after_hwframe+0x46/0xb0&lt;/p&gt;
&lt;p&gt;If register device failed, should call put_device() to give up the
reference.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2022-50566</guid>
    </item>
    <item>
      <title>GHSA-vc9x-p9c7-wp9p</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-vc9x-p9c7-wp9p</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;mtd: Fix device name leak when register device failed in add_mtd_device()&lt;/p&gt;
&lt;p&gt;There is a kmemleak when register device failed:
  unreferenced object 0xffff888101aab550 (size 8):
    comm &amp;#34;insmod&amp;#34;, pid 3922, jiffies 4295277753 (age 925.408s)
    hex dump (first 8 bytes):
      6d 74 64 30 00 88 ff ff                          mtd0....
    backtrace:
      [&amp;lt;00000000bde26724&amp;gt;] __kmalloc_node_track_caller+0x4e/0x150
      [&amp;lt;000000003c32b416&amp;gt;] kvasprintf+0xb0/0x130
      [&amp;lt;000000001f7a8f15&amp;gt;] kobject_set_name_vargs+0x2f/0xb0
      [&amp;lt;000000006e781163&amp;gt;] dev_set_name+0xab/0xe0
      [&amp;lt;00000000e30d0c78&amp;gt;] add_mtd_device+0x4bb/0x700
      [&amp;lt;00000000f3d34de7&amp;gt;] mtd_device_parse_register+0x2ac/0x3f0
      [&amp;lt;00000000c0d88488&amp;gt;] 0xffffffffa0238457
      [&amp;lt;00000000b40d0922&amp;gt;] 0xffffffffa02a008f
      [&amp;lt;0000000023d17b9d&amp;gt;] do_one_initcall+0x87/0x2a0
      [&amp;lt;00000000770f6ca6&amp;gt;] do_init_module+0xdf/0x320
      [&amp;lt;000000007b6768fe&amp;gt;] load_module+0x2f98/0x3330
      [&amp;lt;00000000346bed5a&amp;gt;] __do_sys_finit_module+0x113/0x1b0
      [&amp;lt;00000000674c2290&amp;gt;] do_syscall_64+0x35/0x80
      [&amp;lt;000000004c6a8d97&amp;gt;] entry_SYSCALL_64_after_hwframe+0x46/0xb0&lt;/p&gt;
&lt;p&gt;If register device failed, should call put_device() to give up the
reference.&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;mtd: Fix device name leak when register device failed in add_mtd_device()&lt;/p&gt;
&lt;p&gt;There is a kmemleak when register device failed:
  unreferenced object 0xffff888101aab550 (size 8):
    comm &amp;#34;insmod&amp;#34;, pid 3922, jiffies 4295277753 (age 925.408s)
    hex dump (first 8 bytes):
      6d 74 64 30 00 88 ff ff                          mtd0....
    backtrace:
      [&amp;lt;00000000bde26724&amp;gt;] __kmalloc_node_track_caller+0x4e/0x150
      [&amp;lt;000000003c32b416&amp;gt;] kvasprintf+0xb0/0x130
      [&amp;lt;000000001f7a8f15&amp;gt;] kobject_set_name_vargs+0x2f/0xb0
      [&amp;lt;000000006e781163&amp;gt;] dev_set_name+0xab/0xe0
      [&amp;lt;00000000e30d0c78&amp;gt;] add_mtd_device+0x4bb/0x700
      [&amp;lt;00000000f3d34de7&amp;gt;] mtd_device_parse_register+0x2ac/0x3f0
      [&amp;lt;00000000c0d88488&amp;gt;] 0xffffffffa0238457
      [&amp;lt;00000000b40d0922&amp;gt;] 0xffffffffa02a008f
      [&amp;lt;0000000023d17b9d&amp;gt;] do_one_initcall+0x87/0x2a0
      [&amp;lt;00000000770f6ca6&amp;gt;] do_init_module+0xdf/0x320
      [&amp;lt;000000007b6768fe&amp;gt;] load_module+0x2f98/0x3330
      [&amp;lt;00000000346bed5a&amp;gt;] __do_sys_finit_module+0x113/0x1b0
      [&amp;lt;00000000674c2290&amp;gt;] do_syscall_64+0x35/0x80
      [&amp;lt;000000004c6a8d97&amp;gt;] entry_SYSCALL_64_after_hwframe+0x46/0xb0&lt;/p&gt;
&lt;p&gt;If register device failed, should call put_device() to give up the
reference.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-vc9x-p9c7-wp9p</guid>
    </item>
    <item>
      <title>OESA-2025-2553 — kernel security update</title>
      <link>https://cve.radiocsirt.org/vuln/oesa-2025-2553</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; openEuler:20.03-LTS-SP4: kernel&lt;/p&gt;
&lt;p&gt;The Linux Kernel, the operating system core itself.&#13;
&#13;
Security Fix(es):&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;net/tunnel: wait until all sk_user_data reader finish before releasing the sock&lt;/p&gt;
&lt;p&gt;There is a race condition in vxlan that when deleting a vxlan device
during receiving packets, there is a possibility that the sock is
released after getting vxlan_sock vs from sk_user_data. Then in
later vxlan_ecn_decapsulate(), vxlan_get_sk_family() we will got
NULL pointer dereference. e.g.&lt;/p&gt;
&lt;p&gt;#0 [ffffa25ec6978a38] machine_kexec at ffffffff8c669757
   #1 [ffffa25ec6978a90] __crash_kexec at ffffffff8c7c0a4d
   #2 [ffffa25ec6978b58] crash_kexec at ffffffff8c7c1c48
   #3 [ffffa25ec6978b60] oops_end at ffffffff8c627f2b
   #4 [ffffa25ec6978b80] page_fault_oops at ffffffff8c678fcb
   #5 [ffffa25ec6978bd8] exc_page_fault at ffffffff8d109542
   #6 [ffffa25ec6978c00] asm_exc_page_fault at ffffffff8d200b62
      [exception RIP: vxlan_ecn_decapsulate+0x3b]
      RIP: ffffffffc1014e7b  RSP: ffffa25ec6978cb0  RFLAGS: 00010246
      RAX: 0000000000000008  RBX: ffff8aa000888000  RCX: 0000000000000000
      RDX: 000000000000000e  RSI: ffff8a9fc7ab803e  RDI: ffff8a9fd1168700
      RBP: ffff8a9fc7ab803e   R8: 0000000000700000   R9: 00000000000010ae
      R10: ffff8a9fcb748980  R11: 0000000000000000  R12: ffff8a9fd1168700
      R13: ffff8aa000888000  R14: 00000000002a0000  R15: 00000000000010ae
      ORIG_RAX: ffffffffffffffff  CS: 0010  SS: 0018
   #7 [ffffa25ec6978ce8…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; openEuler:20.03-LTS-SP4: kernel&lt;/p&gt;
&lt;p&gt;The Linux Kernel, the operating system core itself.&#13;
&#13;
Security Fix(es):&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;net/tunnel: wait until all sk_user_data reader finish before releasing the sock&lt;/p&gt;
&lt;p&gt;There is a race condition in vxlan that when deleting a vxlan device
during receiving packets, there is a possibility that the sock is
released after getting vxlan_sock vs from sk_user_data. Then in
later vxlan_ecn_decapsulate(), vxlan_get_sk_family() we will got
NULL pointer dereference. e.g.&lt;/p&gt;
&lt;p&gt;#0 [ffffa25ec6978a38] machine_kexec at ffffffff8c669757
   #1 [ffffa25ec6978a90] __crash_kexec at ffffffff8c7c0a4d
   #2 [ffffa25ec6978b58] crash_kexec at ffffffff8c7c1c48
   #3 [ffffa25ec6978b60] oops_end at ffffffff8c627f2b
   #4 [ffffa25ec6978b80] page_fault_oops at ffffffff8c678fcb
   #5 [ffffa25ec6978bd8] exc_page_fault at ffffffff8d109542
   #6 [ffffa25ec6978c00] asm_exc_page_fault at ffffffff8d200b62
      [exception RIP: vxlan_ecn_decapsulate+0x3b]
      RIP: ffffffffc1014e7b  RSP: ffffa25ec6978cb0  RFLAGS: 00010246
      RAX: 0000000000000008  RBX: ffff8aa000888000  RCX: 0000000000000000
      RDX: 000000000000000e  RSI: ffff8a9fc7ab803e  RDI: ffff8a9fd1168700
      RBP: ffff8a9fc7ab803e   R8: 0000000000700000   R9: 00000000000010ae
      R10: ffff8a9fcb748980  R11: 0000000000000000  R12: ffff8a9fd1168700
      R13: ffff8aa000888000  R14: 00000000002a0000  R15: 00000000000010ae
      ORIG_RAX: ffffffffffffffff  CS: 0010  SS: 0018
   #7 [ffffa25ec6978ce8…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/oesa-2025-2553</guid>
    </item>
    <item>
      <title>SUSE-SU-2025:4139-1 — Security update for the Linux Kernel</title>
      <link>https://cve.radiocsirt.org/vuln/suse-su-2025:4139-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:4139-1</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2022-50566</title>
      <link>https://cve.radiocsirt.org/vuln/ubuntu-cve-2022-50566</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:Pro:14.04:LTS: linux-azure, Ubuntu:Pro:14.04:LTS: linux, Ubuntu:Pro:14.04:LTS: linux-aws, Ubuntu:Pro:14.04:LTS: linux-lts-xenial, 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:Pro:16.04:LTS: linux and 156 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: mtd: Fix device name leak when register device failed in add_mtd_device() There is a kmemleak when register device failed:   unreferenced object 0xffff888101aab550 (size 8):     comm &amp;#34;insmod&amp;#34;, pid 3922, jiffies 4295277753 (age 925.408s)     hex dump (first 8 bytes):       6d 74 64 30 00 88 ff ff                          mtd0....     backtrace:       [&amp;lt;00000000bde26724&amp;gt;] __kmalloc_node_track_caller+0x4e/0x150       [&amp;lt;000000003c32b416&amp;gt;] kvasprintf+0xb0/0x130       [&amp;lt;000000001f7a8f15&amp;gt;] kobject_set_name_vargs+0x2f/0xb0       [&amp;lt;000000006e781163&amp;gt;] dev_set_name+0xab/0xe0       [&amp;lt;00000000e30d0c78&amp;gt;] add_mtd_device+0x4bb/0x700       [&amp;lt;00000000f3d34de7&amp;gt;] mtd_device_parse_register+0x2ac/0x3f0       [&amp;lt;00000000c0d88488&amp;gt;] 0xffffffffa0238457       [&amp;lt;00000000b40d0922&amp;gt;] 0xffffffffa02a008f       [&amp;lt;0000000023d17b9d&amp;gt;] do_one_initcall+0x87/0x2a0       [&amp;lt;00000000770f6ca6&amp;gt;] do_init_module+0xdf/0x320       [&amp;lt;000000007b6768fe&amp;gt;] load_module+0x2f98/0x3330       [&amp;lt;00000000346bed5a&amp;gt;] __do_sys_finit_module+0x113/0x1b0       [&amp;lt;00000000674c2290&amp;gt;] do_syscall_64+0x35/0x80       [&amp;lt;000000004c6a8d97&amp;gt;] entry_SYSCALL_64_after_hwframe+0x46/0xb0 If register device failed, should call put_device() to give up the reference.&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:14.04:LTS: linux, Ubuntu:Pro:14.04:LTS: linux-aws, Ubuntu:Pro:14.04:LTS: linux-lts-xenial, 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:Pro:16.04:LTS: linux and 156 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: mtd: Fix device name leak when register device failed in add_mtd_device() There is a kmemleak when register device failed:   unreferenced object 0xffff888101aab550 (size 8):     comm &amp;#34;insmod&amp;#34;, pid 3922, jiffies 4295277753 (age 925.408s)     hex dump (first 8 bytes):       6d 74 64 30 00 88 ff ff                          mtd0....     backtrace:       [&amp;lt;00000000bde26724&amp;gt;] __kmalloc_node_track_caller+0x4e/0x150       [&amp;lt;000000003c32b416&amp;gt;] kvasprintf+0xb0/0x130       [&amp;lt;000000001f7a8f15&amp;gt;] kobject_set_name_vargs+0x2f/0xb0       [&amp;lt;000000006e781163&amp;gt;] dev_set_name+0xab/0xe0       [&amp;lt;00000000e30d0c78&amp;gt;] add_mtd_device+0x4bb/0x700       [&amp;lt;00000000f3d34de7&amp;gt;] mtd_device_parse_register+0x2ac/0x3f0       [&amp;lt;00000000c0d88488&amp;gt;] 0xffffffffa0238457       [&amp;lt;00000000b40d0922&amp;gt;] 0xffffffffa02a008f       [&amp;lt;0000000023d17b9d&amp;gt;] do_one_initcall+0x87/0x2a0       [&amp;lt;00000000770f6ca6&amp;gt;] do_init_module+0xdf/0x320       [&amp;lt;000000007b6768fe&amp;gt;] load_module+0x2f98/0x3330       [&amp;lt;00000000346bed5a&amp;gt;] __do_sys_finit_module+0x113/0x1b0       [&amp;lt;00000000674c2290&amp;gt;] do_syscall_64+0x35/0x80       [&amp;lt;000000004c6a8d97&amp;gt;] entry_SYSCALL_64_after_hwframe+0x46/0xb0 If register device failed, should call put_device() to give up the reference.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ubuntu-cve-2022-50566</guid>
    </item>
    <item>
      <title>WID-SEC-W-2025-2394 — Linux Kernel: Mehrere Schwachstellen</title>
      <link>https://cve.radiocsirt.org/vuln/wid-sec-w-2025-2394</link>
      <description>&lt;p&gt;Ein Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um einen Denial of Service Angriff oder andere, nicht näher spezifizierte Angriffe durchzuführen.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Ein Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um einen Denial of Service Angriff oder andere, nicht näher spezifizierte Angriffe durchzuführen.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/wid-sec-w-2025-2394</guid>
    </item>
  </channel>
</rss>
