<?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 10:56:22 +0000</lastBuildDate>
    <item>
      <title>bdu:2024-06620</title>
      <link>https://cve.radiocsirt.org/vuln/bdu:2024-06620</link>
      <description>bdu:2024-06620</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/bdu:2024-06620</guid>
    </item>
    <item>
      <title>certfr-2024-avi-0779 — 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-0779</link>
      <description>certfr-2024-avi-0779</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/certfr-2024-avi-0779</guid>
    </item>
    <item>
      <title>EUVD-2026-310202</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-310202</link>
      <description>EUVD-2026-310202</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-310202</guid>
    </item>
    <item>
      <title>fkie_cve-2022-48865</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2022-48865</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;tipc: fix kernel panic when enabling bearer&lt;/p&gt;
&lt;p&gt;When enabling a bearer on a node, a kernel panic is observed:&lt;/p&gt;
&lt;p&gt;[    4.498085] RIP: 0010:tipc_mon_prep+0x4e/0x130 [tipc]
...
[    4.520030] Call Trace:
[    4.520689]  &amp;lt;IRQ&amp;gt;
[    4.521236]  tipc_link_build_proto_msg+0x375/0x750 [tipc]
[    4.522654]  tipc_link_build_state_msg+0x48/0xc0 [tipc]
[    4.524034]  __tipc_node_link_up+0xd7/0x290 [tipc]
[    4.525292]  tipc_rcv+0x5da/0x730 [tipc]
[    4.526346]  ? __netif_receive_skb_core+0xb7/0xfc0
[    4.527601]  tipc_l2_rcv_msg+0x5e/0x90 [tipc]
[    4.528737]  __netif_receive_skb_list_core+0x20b/0x260
[    4.530068]  netif_receive_skb_list_internal+0x1bf/0x2e0
[    4.531450]  ? dev_gro_receive+0x4c2/0x680
[    4.532512]  napi_complete_done+0x6f/0x180
[    4.533570]  virtnet_poll+0x29c/0x42e [virtio_net]
...&lt;/p&gt;
&lt;p&gt;The node in question is receiving activate messages in another
thread after changing bearer status to allow message sending/
receiving in current thread:&lt;/p&gt;
&lt;p&gt;thread 1           |              thread 2
         --------           |              --------
                            |
tipc_enable_bearer()        |
  test_and_set_bit_lock()   |
    tipc_bearer_xmit_skb()  |
                            | tipc_l2_rcv_msg()
                            |   tipc_rcv()
                            |     __tipc_node_link_up()
                            |       tipc_link_build_state_msg()
                            |…&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;tipc: fix kernel panic when enabling bearer&lt;/p&gt;
&lt;p&gt;When enabling a bearer on a node, a kernel panic is observed:&lt;/p&gt;
&lt;p&gt;[    4.498085] RIP: 0010:tipc_mon_prep+0x4e/0x130 [tipc]
...
[    4.520030] Call Trace:
[    4.520689]  &amp;lt;IRQ&amp;gt;
[    4.521236]  tipc_link_build_proto_msg+0x375/0x750 [tipc]
[    4.522654]  tipc_link_build_state_msg+0x48/0xc0 [tipc]
[    4.524034]  __tipc_node_link_up+0xd7/0x290 [tipc]
[    4.525292]  tipc_rcv+0x5da/0x730 [tipc]
[    4.526346]  ? __netif_receive_skb_core+0xb7/0xfc0
[    4.527601]  tipc_l2_rcv_msg+0x5e/0x90 [tipc]
[    4.528737]  __netif_receive_skb_list_core+0x20b/0x260
[    4.530068]  netif_receive_skb_list_internal+0x1bf/0x2e0
[    4.531450]  ? dev_gro_receive+0x4c2/0x680
[    4.532512]  napi_complete_done+0x6f/0x180
[    4.533570]  virtnet_poll+0x29c/0x42e [virtio_net]
...&lt;/p&gt;
&lt;p&gt;The node in question is receiving activate messages in another
thread after changing bearer status to allow message sending/
receiving in current thread:&lt;/p&gt;
&lt;p&gt;thread 1           |              thread 2
         --------           |              --------
                            |
tipc_enable_bearer()        |
  test_and_set_bit_lock()   |
    tipc_bearer_xmit_skb()  |
                            | tipc_l2_rcv_msg()
                            |   tipc_rcv()
                            |     __tipc_node_link_up()
                            |       tipc_link_build_state_msg()
                            |…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2022-48865</guid>
    </item>
    <item>
      <title>GHSA-97c5-prqj-77gq</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-97c5-prqj-77gq</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;tipc: fix kernel panic when enabling bearer&lt;/p&gt;
&lt;p&gt;When enabling a bearer on a node, a kernel panic is observed:&lt;/p&gt;
&lt;p&gt;[    4.498085] RIP: 0010:tipc_mon_prep+0x4e/0x130 [tipc]
...
[    4.520030] Call Trace:
[    4.520689]  &amp;lt;IRQ&amp;gt;
[    4.521236]  tipc_link_build_proto_msg+0x375/0x750 [tipc]
[    4.522654]  tipc_link_build_state_msg+0x48/0xc0 [tipc]
[    4.524034]  __tipc_node_link_up+0xd7/0x290 [tipc]
[    4.525292]  tipc_rcv+0x5da/0x730 [tipc]
[    4.526346]  ? __netif_receive_skb_core+0xb7/0xfc0
[    4.527601]  tipc_l2_rcv_msg+0x5e/0x90 [tipc]
[    4.528737]  __netif_receive_skb_list_core+0x20b/0x260
[    4.530068]  netif_receive_skb_list_internal+0x1bf/0x2e0
[    4.531450]  ? dev_gro_receive+0x4c2/0x680
[    4.532512]  napi_complete_done+0x6f/0x180
[    4.533570]  virtnet_poll+0x29c/0x42e [virtio_net]
...&lt;/p&gt;
&lt;p&gt;The node in question is receiving activate messages in another
thread after changing bearer status to allow message sending/
receiving in current thread:&lt;/p&gt;
&lt;p&gt;thread 1           |              thread 2
         --------           |              --------
                            |
tipc_enable_bearer()        |
  test_and_set_bit_lock()   |
    tipc_bearer_xmit_skb()  |
                            | tipc_l2_rcv_msg()
                            |   tipc_rcv()
                            |     __tipc_node_link_up()
                            |       tipc_link_build_state_msg()
                            |…&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;tipc: fix kernel panic when enabling bearer&lt;/p&gt;
&lt;p&gt;When enabling a bearer on a node, a kernel panic is observed:&lt;/p&gt;
&lt;p&gt;[    4.498085] RIP: 0010:tipc_mon_prep+0x4e/0x130 [tipc]
...
[    4.520030] Call Trace:
[    4.520689]  &amp;lt;IRQ&amp;gt;
[    4.521236]  tipc_link_build_proto_msg+0x375/0x750 [tipc]
[    4.522654]  tipc_link_build_state_msg+0x48/0xc0 [tipc]
[    4.524034]  __tipc_node_link_up+0xd7/0x290 [tipc]
[    4.525292]  tipc_rcv+0x5da/0x730 [tipc]
[    4.526346]  ? __netif_receive_skb_core+0xb7/0xfc0
[    4.527601]  tipc_l2_rcv_msg+0x5e/0x90 [tipc]
[    4.528737]  __netif_receive_skb_list_core+0x20b/0x260
[    4.530068]  netif_receive_skb_list_internal+0x1bf/0x2e0
[    4.531450]  ? dev_gro_receive+0x4c2/0x680
[    4.532512]  napi_complete_done+0x6f/0x180
[    4.533570]  virtnet_poll+0x29c/0x42e [virtio_net]
...&lt;/p&gt;
&lt;p&gt;The node in question is receiving activate messages in another
thread after changing bearer status to allow message sending/
receiving in current thread:&lt;/p&gt;
&lt;p&gt;thread 1           |              thread 2
         --------           |              --------
                            |
tipc_enable_bearer()        |
  test_and_set_bit_lock()   |
    tipc_bearer_xmit_skb()  |
                            | tipc_l2_rcv_msg()
                            |   tipc_rcv()
                            |     __tipc_node_link_up()
                            |       tipc_link_build_state_msg()
                            |…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-97c5-prqj-77gq</guid>
    </item>
    <item>
      <title>OESA-2024-1895 — kernel security update</title>
      <link>https://cve.radiocsirt.org/vuln/oesa-2024-1895</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):&#13;
&#13;
In the Linux kernel, the following vulnerability has been resolved:&#13;
&#13;
nfc: fix segfault in nfc_genl_dump_devices_done&#13;
&#13;
When kmalloc in nfc_genl_dump_devices() fails then
nfc_genl_dump_devices_done() segfaults as below&#13;
&#13;
KASAN: null-ptr-deref in range [0x0000000000000008-0x000000000000000f]
CPU: 0 PID: 25 Comm: kworker/0:1 Not tainted 5.16.0-rc4-01180-g2a987e65025e-dirty #5
Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.14.0-6.fc35 04/01/2014
Workqueue: events netlink_sock_destruct_work
RIP: 0010:klist_iter_exit+0x26/0x80
Call Trace:
&amp;amp;lt;TASK&amp;amp;gt;
class_dev_iter_exit+0x15/0x20
nfc_genl_dump_devices_done+0x3b/0x50
genl_lock_done+0x84/0xd0
netlink_sock_destruct+0x8f/0x270
__sk_destruct+0x64/0x3b0
sk_destruct+0xa8/0xd0
__sk_free+0x2e8/0x3d0
sk_free+0x51/0x90
netlink_sock_destruct_work+0x1c/0x20
process_one_work+0x411/0x710
worker_thread+0x6fd/0xa80(CVE-2021-47612)&#13;
&#13;
In the Linux kernel, the following vulnerability has been resolved:&#13;
&#13;
Drivers: hv: vmbus: Fix memory leak in vmbus_add_channel_kobj&#13;
&#13;
kobject_init_and_add() takes reference even when it fails.
According to the doc of kobject_init_and_add()?&#13;
&#13;
   If this function returns an error, kobject_put() must be called to
   properly clean up the memory associated with the object.&#13;
&#13;
Fix memory leak by calling kobject_put().(CVE-2022-48775)&#13;
&#13;
In the Linux kernel, the following vulnerability has been resolved:&#13;
&#13;
nvme-rdma: fix pos…&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):&#13;
&#13;
In the Linux kernel, the following vulnerability has been resolved:&#13;
&#13;
nfc: fix segfault in nfc_genl_dump_devices_done&#13;
&#13;
When kmalloc in nfc_genl_dump_devices() fails then
nfc_genl_dump_devices_done() segfaults as below&#13;
&#13;
KASAN: null-ptr-deref in range [0x0000000000000008-0x000000000000000f]
CPU: 0 PID: 25 Comm: kworker/0:1 Not tainted 5.16.0-rc4-01180-g2a987e65025e-dirty #5
Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.14.0-6.fc35 04/01/2014
Workqueue: events netlink_sock_destruct_work
RIP: 0010:klist_iter_exit+0x26/0x80
Call Trace:
&amp;amp;lt;TASK&amp;amp;gt;
class_dev_iter_exit+0x15/0x20
nfc_genl_dump_devices_done+0x3b/0x50
genl_lock_done+0x84/0xd0
netlink_sock_destruct+0x8f/0x270
__sk_destruct+0x64/0x3b0
sk_destruct+0xa8/0xd0
__sk_free+0x2e8/0x3d0
sk_free+0x51/0x90
netlink_sock_destruct_work+0x1c/0x20
process_one_work+0x411/0x710
worker_thread+0x6fd/0xa80(CVE-2021-47612)&#13;
&#13;
In the Linux kernel, the following vulnerability has been resolved:&#13;
&#13;
Drivers: hv: vmbus: Fix memory leak in vmbus_add_channel_kobj&#13;
&#13;
kobject_init_and_add() takes reference even when it fails.
According to the doc of kobject_init_and_add()?&#13;
&#13;
   If this function returns an error, kobject_put() must be called to
   properly clean up the memory associated with the object.&#13;
&#13;
Fix memory leak by calling kobject_put().(CVE-2022-48775)&#13;
&#13;
In the Linux kernel, the following vulnerability has been resolved:&#13;
&#13;
nvme-rdma: fix pos…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/oesa-2024-1895</guid>
    </item>
    <item>
      <title>SUSE-SU-2024:3189-1 — Security update for the Linux Kernel</title>
      <link>https://cve.radiocsirt.org/vuln/suse-su-2024:3189-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:3189-1</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2022-48865</title>
      <link>https://cve.radiocsirt.org/vuln/ubuntu-cve-2022-48865</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:Pro:14.04:LTS: linux-azure, 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:16.04:LTS: linux-hwe-edge, Ubuntu:Pro:16.04:LTS: linux-oracle, Ubuntu:Pro:18.04:LTS: linux, Ubuntu:Pro:18.04:LTS: linux-aws, Ubuntu:18.04:LTS: linux-aws-5.0 and 109 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: tipc: fix kernel panic when enabling bearer When enabling a bearer on a node, a kernel panic is observed: [    4.498085] RIP: 0010:tipc_mon_prep+0x4e/0x130 [tipc] ... [    4.520030] Call Trace: [    4.520689]  &amp;lt;IRQ&amp;gt; [    4.521236]  tipc_link_build_proto_msg+0x375/0x750 [tipc] [    4.522654]  tipc_link_build_state_msg+0x48/0xc0 [tipc] [    4.524034]  __tipc_node_link_up+0xd7/0x290 [tipc] [    4.525292]  tipc_rcv+0x5da/0x730 [tipc] [    4.526346]  ? __netif_receive_skb_core+0xb7/0xfc0 [    4.527601]  tipc_l2_rcv_msg+0x5e/0x90 [tipc] [    4.528737]  __netif_receive_skb_list_core+0x20b/0x260 [    4.530068]  netif_receive_skb_list_internal+0x1bf/0x2e0 [    4.531450]  ? dev_gro_receive+0x4c2/0x680 [    4.532512]  napi_complete_done+0x6f/0x180 [    4.533570]  virtnet_poll+0x29c/0x42e [virtio_net] ... The node in question is receiving activate messages in another thread after changing bearer status to allow message sending/ receiving in current thread:          thread 1           |              thread 2          --------           |              --------                             | tipc_enable_bearer()        |   test_and_set_bit_lock()   |     tipc_bearer_xmit_skb()  |                             | tipc_l2_rcv_msg()                             |   tipc_rcv()                             |     __tipc_node_link_up()                             |       tipc_link_build_state_msg()                             |…&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: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:16.04:LTS: linux-hwe-edge, Ubuntu:Pro:16.04:LTS: linux-oracle, Ubuntu:Pro:18.04:LTS: linux, Ubuntu:Pro:18.04:LTS: linux-aws, Ubuntu:18.04:LTS: linux-aws-5.0 and 109 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: tipc: fix kernel panic when enabling bearer When enabling a bearer on a node, a kernel panic is observed: [    4.498085] RIP: 0010:tipc_mon_prep+0x4e/0x130 [tipc] ... [    4.520030] Call Trace: [    4.520689]  &amp;lt;IRQ&amp;gt; [    4.521236]  tipc_link_build_proto_msg+0x375/0x750 [tipc] [    4.522654]  tipc_link_build_state_msg+0x48/0xc0 [tipc] [    4.524034]  __tipc_node_link_up+0xd7/0x290 [tipc] [    4.525292]  tipc_rcv+0x5da/0x730 [tipc] [    4.526346]  ? __netif_receive_skb_core+0xb7/0xfc0 [    4.527601]  tipc_l2_rcv_msg+0x5e/0x90 [tipc] [    4.528737]  __netif_receive_skb_list_core+0x20b/0x260 [    4.530068]  netif_receive_skb_list_internal+0x1bf/0x2e0 [    4.531450]  ? dev_gro_receive+0x4c2/0x680 [    4.532512]  napi_complete_done+0x6f/0x180 [    4.533570]  virtnet_poll+0x29c/0x42e [virtio_net] ... The node in question is receiving activate messages in another thread after changing bearer status to allow message sending/ receiving in current thread:          thread 1           |              thread 2          --------           |              --------                             | tipc_enable_bearer()        |   test_and_set_bit_lock()   |     tipc_bearer_xmit_skb()  |                             | tipc_l2_rcv_msg()                             |   tipc_rcv()                             |     __tipc_node_link_up()                             |       tipc_link_build_state_msg()                             |…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ubuntu-cve-2022-48865</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>
