<?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>Fri, 02 Oct 2026 13:39:58 +0000</lastBuildDate>
    <item>
      <title>certfr-2026-avi-0108 — 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-2026-avi-0108</link>
      <description>certfr-2026-avi-0108</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/certfr-2026-avi-0108</guid>
    </item>
    <item>
      <title>EUVD-2026-311383</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-311383</link>
      <description>EUVD-2026-311383</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-311383</guid>
    </item>
    <item>
      <title>fkie_cve-2022-50702</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2022-50702</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;vdpa_sim: fix possible memory leak in vdpasim_net_init() and vdpasim_blk_init()&lt;/p&gt;
&lt;p&gt;Inject fault while probing module, if device_register() fails in
vdpasim_net_init() or vdpasim_blk_init(), but the refcount of kobject is
not decreased to 0, the name allocated in dev_set_name() is leaked.
Fix this by calling put_device(), so that name can be freed in
callback function kobject_cleanup().&lt;/p&gt;
&lt;p&gt;(vdpa_sim_net)
unreferenced object 0xffff88807eebc370 (size 16):
  comm &amp;#34;modprobe&amp;#34;, pid 3848, jiffies 4362982860 (age 18.153s)
  hex dump (first 16 bytes):
    76 64 70 61 73 69 6d 5f 6e 65 74 00 6b 6b 6b a5  vdpasim_net.kkk.
  backtrace:
    [&amp;lt;ffffffff8174f19e&amp;gt;] __kmalloc_node_track_caller+0x4e/0x150
    [&amp;lt;ffffffff81731d53&amp;gt;] kstrdup+0x33/0x60
    [&amp;lt;ffffffff83a5d421&amp;gt;] kobject_set_name_vargs+0x41/0x110
    [&amp;lt;ffffffff82d87aab&amp;gt;] dev_set_name+0xab/0xe0
    [&amp;lt;ffffffff82d91a23&amp;gt;] device_add+0xe3/0x1a80
    [&amp;lt;ffffffffa0270013&amp;gt;] 0xffffffffa0270013
    [&amp;lt;ffffffff81001c27&amp;gt;] do_one_initcall+0x87/0x2e0
    [&amp;lt;ffffffff813739cb&amp;gt;] do_init_module+0x1ab/0x640
    [&amp;lt;ffffffff81379d20&amp;gt;] load_module+0x5d00/0x77f0
    [&amp;lt;ffffffff8137bc40&amp;gt;] __do_sys_finit_module+0x110/0x1b0
    [&amp;lt;ffffffff83c4d505&amp;gt;] do_syscall_64+0x35/0x80
    [&amp;lt;ffffffff83e0006a&amp;gt;] entry_SYSCALL_64_after_hwframe+0x46/0xb0&lt;/p&gt;
&lt;p&gt;(vdpa_sim_blk)
unreferenced object 0xffff8881070c1250 (size 16):
  comm &amp;#34;modprobe&amp;#34;, pid 6844, jiffies 4364069319 (age 17.572s)
  hex dump (first 16 bytes):
    76 64 7…&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;vdpa_sim: fix possible memory leak in vdpasim_net_init() and vdpasim_blk_init()&lt;/p&gt;
&lt;p&gt;Inject fault while probing module, if device_register() fails in
vdpasim_net_init() or vdpasim_blk_init(), but the refcount of kobject is
not decreased to 0, the name allocated in dev_set_name() is leaked.
Fix this by calling put_device(), so that name can be freed in
callback function kobject_cleanup().&lt;/p&gt;
&lt;p&gt;(vdpa_sim_net)
unreferenced object 0xffff88807eebc370 (size 16):
  comm &amp;#34;modprobe&amp;#34;, pid 3848, jiffies 4362982860 (age 18.153s)
  hex dump (first 16 bytes):
    76 64 70 61 73 69 6d 5f 6e 65 74 00 6b 6b 6b a5  vdpasim_net.kkk.
  backtrace:
    [&amp;lt;ffffffff8174f19e&amp;gt;] __kmalloc_node_track_caller+0x4e/0x150
    [&amp;lt;ffffffff81731d53&amp;gt;] kstrdup+0x33/0x60
    [&amp;lt;ffffffff83a5d421&amp;gt;] kobject_set_name_vargs+0x41/0x110
    [&amp;lt;ffffffff82d87aab&amp;gt;] dev_set_name+0xab/0xe0
    [&amp;lt;ffffffff82d91a23&amp;gt;] device_add+0xe3/0x1a80
    [&amp;lt;ffffffffa0270013&amp;gt;] 0xffffffffa0270013
    [&amp;lt;ffffffff81001c27&amp;gt;] do_one_initcall+0x87/0x2e0
    [&amp;lt;ffffffff813739cb&amp;gt;] do_init_module+0x1ab/0x640
    [&amp;lt;ffffffff81379d20&amp;gt;] load_module+0x5d00/0x77f0
    [&amp;lt;ffffffff8137bc40&amp;gt;] __do_sys_finit_module+0x110/0x1b0
    [&amp;lt;ffffffff83c4d505&amp;gt;] do_syscall_64+0x35/0x80
    [&amp;lt;ffffffff83e0006a&amp;gt;] entry_SYSCALL_64_after_hwframe+0x46/0xb0&lt;/p&gt;
&lt;p&gt;(vdpa_sim_blk)
unreferenced object 0xffff8881070c1250 (size 16):
  comm &amp;#34;modprobe&amp;#34;, pid 6844, jiffies 4364069319 (age 17.572s)
  hex dump (first 16 bytes):
    76 64 7…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2022-50702</guid>
    </item>
    <item>
      <title>GHSA-p22c-78xj-4fp8</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-p22c-78xj-4fp8</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;vdpa_sim: fix possible memory leak in vdpasim_net_init() and vdpasim_blk_init()&lt;/p&gt;
&lt;p&gt;Inject fault while probing module, if device_register() fails in
vdpasim_net_init() or vdpasim_blk_init(), but the refcount of kobject is
not decreased to 0, the name allocated in dev_set_name() is leaked.
Fix this by calling put_device(), so that name can be freed in
callback function kobject_cleanup().&lt;/p&gt;
&lt;p&gt;(vdpa_sim_net)
unreferenced object 0xffff88807eebc370 (size 16):
  comm &amp;#34;modprobe&amp;#34;, pid 3848, jiffies 4362982860 (age 18.153s)
  hex dump (first 16 bytes):
    76 64 70 61 73 69 6d 5f 6e 65 74 00 6b 6b 6b a5  vdpasim_net.kkk.
  backtrace:
    [&amp;lt;ffffffff8174f19e&amp;gt;] __kmalloc_node_track_caller+0x4e/0x150
    [&amp;lt;ffffffff81731d53&amp;gt;] kstrdup+0x33/0x60
    [&amp;lt;ffffffff83a5d421&amp;gt;] kobject_set_name_vargs+0x41/0x110
    [&amp;lt;ffffffff82d87aab&amp;gt;] dev_set_name+0xab/0xe0
    [&amp;lt;ffffffff82d91a23&amp;gt;] device_add+0xe3/0x1a80
    [&amp;lt;ffffffffa0270013&amp;gt;] 0xffffffffa0270013
    [&amp;lt;ffffffff81001c27&amp;gt;] do_one_initcall+0x87/0x2e0
    [&amp;lt;ffffffff813739cb&amp;gt;] do_init_module+0x1ab/0x640
    [&amp;lt;ffffffff81379d20&amp;gt;] load_module+0x5d00/0x77f0
    [&amp;lt;ffffffff8137bc40&amp;gt;] __do_sys_finit_module+0x110/0x1b0
    [&amp;lt;ffffffff83c4d505&amp;gt;] do_syscall_64+0x35/0x80
    [&amp;lt;ffffffff83e0006a&amp;gt;] entry_SYSCALL_64_after_hwframe+0x46/0xb0&lt;/p&gt;
&lt;p&gt;(vdpa_sim_blk)
unreferenced object 0xffff8881070c1250 (size 16):
  comm &amp;#34;modprobe&amp;#34;, pid 6844, jiffies 4364069319 (age 17.572s)
  hex dump (first 16 bytes):
    76 64 7…&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;vdpa_sim: fix possible memory leak in vdpasim_net_init() and vdpasim_blk_init()&lt;/p&gt;
&lt;p&gt;Inject fault while probing module, if device_register() fails in
vdpasim_net_init() or vdpasim_blk_init(), but the refcount of kobject is
not decreased to 0, the name allocated in dev_set_name() is leaked.
Fix this by calling put_device(), so that name can be freed in
callback function kobject_cleanup().&lt;/p&gt;
&lt;p&gt;(vdpa_sim_net)
unreferenced object 0xffff88807eebc370 (size 16):
  comm &amp;#34;modprobe&amp;#34;, pid 3848, jiffies 4362982860 (age 18.153s)
  hex dump (first 16 bytes):
    76 64 70 61 73 69 6d 5f 6e 65 74 00 6b 6b 6b a5  vdpasim_net.kkk.
  backtrace:
    [&amp;lt;ffffffff8174f19e&amp;gt;] __kmalloc_node_track_caller+0x4e/0x150
    [&amp;lt;ffffffff81731d53&amp;gt;] kstrdup+0x33/0x60
    [&amp;lt;ffffffff83a5d421&amp;gt;] kobject_set_name_vargs+0x41/0x110
    [&amp;lt;ffffffff82d87aab&amp;gt;] dev_set_name+0xab/0xe0
    [&amp;lt;ffffffff82d91a23&amp;gt;] device_add+0xe3/0x1a80
    [&amp;lt;ffffffffa0270013&amp;gt;] 0xffffffffa0270013
    [&amp;lt;ffffffff81001c27&amp;gt;] do_one_initcall+0x87/0x2e0
    [&amp;lt;ffffffff813739cb&amp;gt;] do_init_module+0x1ab/0x640
    [&amp;lt;ffffffff81379d20&amp;gt;] load_module+0x5d00/0x77f0
    [&amp;lt;ffffffff8137bc40&amp;gt;] __do_sys_finit_module+0x110/0x1b0
    [&amp;lt;ffffffff83c4d505&amp;gt;] do_syscall_64+0x35/0x80
    [&amp;lt;ffffffff83e0006a&amp;gt;] entry_SYSCALL_64_after_hwframe+0x46/0xb0&lt;/p&gt;
&lt;p&gt;(vdpa_sim_blk)
unreferenced object 0xffff8881070c1250 (size 16):
  comm &amp;#34;modprobe&amp;#34;, pid 6844, jiffies 4364069319 (age 17.572s)
  hex dump (first 16 bytes):
    76 64 7…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-p22c-78xj-4fp8</guid>
    </item>
    <item>
      <title>RHSA-2023:2458 — Red Hat Security Advisory: kernel security, bug fix, and enhancement update</title>
      <link>https://cve.radiocsirt.org/vuln/rhsa-2023:2458</link>
      <description>&lt;p&gt;hw: cpu: AMD CPUs may transiently execute beyond unconditional direct branch kernel: ext4: kernel bug in ext4_write_inline_data_end() kernel: malicious data for FBIOPUT_VSCREENINFO ioctl may cause OOB write memory kernel: hwmon: (mlxreg-fan) Return non-zero value when fan current state is enforced from sysfs kernel: mlxsw: thermal: Fix out-of-bounds memory accesses kernel: mlxsw: spectrum: Protect driver from buggy firmware kernel: net: stmmac: fix tc flower deletion for VLAN priority Rx steering kernel: can: etas_es58x: es58x_rx_err_msg(): fix memory leak in error path kernel: possible race condition in drivers/tty/tty_buffers.c kernel: KVM: NULL pointer dereference in kvm_mmu_invpcid_gva kernel: use-after-free in free_pipe_info() could lead to privilege escalation kernel: KVM: nVMX: missing IBPB when exiting from nested guest can lead to Spectre v2 attacks kernel: netfilter: nf_conntrack_irc message handling issue kernel: race condition in xfrm_probe_algs can lead to OOB read/write kernel: out-of-bounds read in fib_nh_match of the file net/ipv4/fib_semantics.c kernel: race condition in hugetlb_no_page() in mm/hugetlb.c kernel: memory leak in ipv6_renew_options() kernel: data races around icsk-&amp;gt;icsk_af_ops in do_ipv6_setsockopt kernel: data races around sk-&amp;gt;sk_prot kernel: memory leak in l2cap_recv_acldata of the file net/bluetooth/l2cap_core.c kernel: denial of service in follow_page_pte in mm/gup.c due to poisoned pte entry kernel: use-after-free after failed devlink relo…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;hw: cpu: AMD CPUs may transiently execute beyond unconditional direct branch kernel: ext4: kernel bug in ext4_write_inline_data_end() kernel: malicious data for FBIOPUT_VSCREENINFO ioctl may cause OOB write memory kernel: hwmon: (mlxreg-fan) Return non-zero value when fan current state is enforced from sysfs kernel: mlxsw: thermal: Fix out-of-bounds memory accesses kernel: mlxsw: spectrum: Protect driver from buggy firmware kernel: net: stmmac: fix tc flower deletion for VLAN priority Rx steering kernel: can: etas_es58x: es58x_rx_err_msg(): fix memory leak in error path kernel: possible race condition in drivers/tty/tty_buffers.c kernel: KVM: NULL pointer dereference in kvm_mmu_invpcid_gva kernel: use-after-free in free_pipe_info() could lead to privilege escalation kernel: KVM: nVMX: missing IBPB when exiting from nested guest can lead to Spectre v2 attacks kernel: netfilter: nf_conntrack_irc message handling issue kernel: race condition in xfrm_probe_algs can lead to OOB read/write kernel: out-of-bounds read in fib_nh_match of the file net/ipv4/fib_semantics.c kernel: race condition in hugetlb_no_page() in mm/hugetlb.c kernel: memory leak in ipv6_renew_options() kernel: data races around icsk-&amp;gt;icsk_af_ops in do_ipv6_setsockopt kernel: data races around sk-&amp;gt;sk_prot kernel: memory leak in l2cap_recv_acldata of the file net/bluetooth/l2cap_core.c kernel: denial of service in follow_page_pte in mm/gup.c due to poisoned pte entry kernel: use-after-free after failed devlink relo…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/rhsa-2023:2458</guid>
    </item>
    <item>
      <title>SUSE-SU-2026:0263-1 — Security update for the Linux Kernel</title>
      <link>https://cve.radiocsirt.org/vuln/suse-su-2026:0263-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-2026:0263-1</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2022-50702</title>
      <link>https://cve.radiocsirt.org/vuln/ubuntu-cve-2022-50702</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 105 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: vdpa_sim: fix possible memory leak in vdpasim_net_init() and vdpasim_blk_init() Inject fault while probing module, if device_register() fails in vdpasim_net_init() or vdpasim_blk_init(), but the refcount of kobject is not decreased to 0, the name allocated in dev_set_name() is leaked. Fix this by calling put_device(), so that name can be freed in callback function kobject_cleanup(). (vdpa_sim_net) unreferenced object 0xffff88807eebc370 (size 16):   comm &amp;#34;modprobe&amp;#34;, pid 3848, jiffies 4362982860 (age 18.153s)   hex dump (first 16 bytes):     76 64 70 61 73 69 6d 5f 6e 65 74 00 6b 6b 6b a5  vdpasim_net.kkk.   backtrace:     [&amp;lt;ffffffff8174f19e&amp;gt;] __kmalloc_node_track_caller+0x4e/0x150     [&amp;lt;ffffffff81731d53&amp;gt;] kstrdup+0x33/0x60     [&amp;lt;ffffffff83a5d421&amp;gt;] kobject_set_name_vargs+0x41/0x110     [&amp;lt;ffffffff82d87aab&amp;gt;] dev_set_name+0xab/0xe0     [&amp;lt;ffffffff82d91a23&amp;gt;] device_add+0xe3/0x1a80     [&amp;lt;ffffffffa0270013&amp;gt;] 0xffffffffa0270013     [&amp;lt;ffffffff81001c27&amp;gt;] do_one_initcall+0x87/0x2e0     [&amp;lt;ffffffff813739cb&amp;gt;] do_init_module+0x1ab/0x640     [&amp;lt;ffffffff81379d20&amp;gt;] load_module+0x5d00/0x77f0     [&amp;lt;ffffffff8137bc40&amp;gt;] __do_sys_finit_module+0x110/0x1b0     [&amp;lt;ffffffff83c4d505&amp;gt;] do_syscall_64+0x35/0x80     [&amp;lt;ffffffff83e0006a&amp;gt;] entry_SYSCALL_64_after_hwframe+0x46/0xb0 (vdpa_sim_blk) unreferenced object 0xffff8881070c1250 (size 16):   comm &amp;#34;modprobe&amp;#34;, pid 6844, jiffies 4364069319 (age 17.572s)   hex dump (first 16 bytes):     76 64 70 61…&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 105 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: vdpa_sim: fix possible memory leak in vdpasim_net_init() and vdpasim_blk_init() Inject fault while probing module, if device_register() fails in vdpasim_net_init() or vdpasim_blk_init(), but the refcount of kobject is not decreased to 0, the name allocated in dev_set_name() is leaked. Fix this by calling put_device(), so that name can be freed in callback function kobject_cleanup(). (vdpa_sim_net) unreferenced object 0xffff88807eebc370 (size 16):   comm &amp;#34;modprobe&amp;#34;, pid 3848, jiffies 4362982860 (age 18.153s)   hex dump (first 16 bytes):     76 64 70 61 73 69 6d 5f 6e 65 74 00 6b 6b 6b a5  vdpasim_net.kkk.   backtrace:     [&amp;lt;ffffffff8174f19e&amp;gt;] __kmalloc_node_track_caller+0x4e/0x150     [&amp;lt;ffffffff81731d53&amp;gt;] kstrdup+0x33/0x60     [&amp;lt;ffffffff83a5d421&amp;gt;] kobject_set_name_vargs+0x41/0x110     [&amp;lt;ffffffff82d87aab&amp;gt;] dev_set_name+0xab/0xe0     [&amp;lt;ffffffff82d91a23&amp;gt;] device_add+0xe3/0x1a80     [&amp;lt;ffffffffa0270013&amp;gt;] 0xffffffffa0270013     [&amp;lt;ffffffff81001c27&amp;gt;] do_one_initcall+0x87/0x2e0     [&amp;lt;ffffffff813739cb&amp;gt;] do_init_module+0x1ab/0x640     [&amp;lt;ffffffff81379d20&amp;gt;] load_module+0x5d00/0x77f0     [&amp;lt;ffffffff8137bc40&amp;gt;] __do_sys_finit_module+0x110/0x1b0     [&amp;lt;ffffffff83c4d505&amp;gt;] do_syscall_64+0x35/0x80     [&amp;lt;ffffffff83e0006a&amp;gt;] entry_SYSCALL_64_after_hwframe+0x46/0xb0 (vdpa_sim_blk) unreferenced object 0xffff8881070c1250 (size 16):   comm &amp;#34;modprobe&amp;#34;, pid 6844, jiffies 4364069319 (age 17.572s)   hex dump (first 16 bytes):     76 64 70 61…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ubuntu-cve-2022-50702</guid>
    </item>
    <item>
      <title>WID-SEC-W-2025-2920 — Linux Kernel: Mehrere Schwachstellen</title>
      <link>https://cve.radiocsirt.org/vuln/wid-sec-w-2025-2920</link>
      <description>&lt;p&gt;Ein Angreifer kann mehrere Schwachstellen im Linux-Kernel ausnutzen, um nicht näher spezifizierte Angriffe durchzuführen, die möglicherweise zu einer Denial-of-Service- Bedingung führen oder eine Speicherbeschädigung verursachen können.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Ein Angreifer kann mehrere Schwachstellen im Linux-Kernel ausnutzen, um nicht näher spezifizierte Angriffe durchzuführen, die möglicherweise zu einer Denial-of-Service- Bedingung führen oder eine Speicherbeschädigung verursachen können.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/wid-sec-w-2025-2920</guid>
    </item>
  </channel>
</rss>
