<?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 19:52:26 +0000</lastBuildDate>
    <item>
      <title>bdu:2026-03255</title>
      <link>https://cve.radiocsirt.org/vuln/bdu:2026-03255</link>
      <description>bdu:2026-03255</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/bdu:2026-03255</guid>
    </item>
    <item>
      <title>certfr-2025-avi-0587 — 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-0587</link>
      <description>certfr-2025-avi-0587</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/certfr-2025-avi-0587</guid>
    </item>
    <item>
      <title>EUVD-2026-344852</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-344852</link>
      <description>EUVD-2026-344852</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-344852</guid>
    </item>
    <item>
      <title>fkie_cve-2022-50136</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2022-50136</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;RDMA/siw: Fix duplicated reported IW_CM_EVENT_CONNECT_REPLY event&lt;/p&gt;
&lt;p&gt;If siw_recv_mpa_rr returns -EAGAIN, it means that the MPA reply hasn&amp;#39;t
been received completely, and should not report IW_CM_EVENT_CONNECT_REPLY
in this case. This may trigger a call trace in iw_cm. A simple way to
trigger this:
 server: ib_send_lat
 client: ib_send_lat -R &amp;lt;server_ip&amp;gt;&lt;/p&gt;
&lt;p&gt;The call trace looks like this:&lt;/p&gt;
&lt;p&gt;kernel BUG at drivers/infiniband/core/iwcm.c:894!
 invalid opcode: 0000 [#1] PREEMPT SMP NOPTI
 &amp;lt;...&amp;gt;
 Workqueue: iw_cm_wq cm_work_handler [iw_cm]
 Call Trace:
  &amp;lt;TASK&amp;gt;
  cm_work_handler+0x1dd/0x370 [iw_cm]
  process_one_work+0x1e2/0x3b0
  worker_thread+0x49/0x2e0
  ? rescuer_thread+0x370/0x370
  kthread+0xe5/0x110
  ? kthread_complete_and_exit+0x20/0x20
  ret_from_fork+0x1f/0x30
  &amp;lt;/TASK&amp;gt;&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;RDMA/siw: Fix duplicated reported IW_CM_EVENT_CONNECT_REPLY event&lt;/p&gt;
&lt;p&gt;If siw_recv_mpa_rr returns -EAGAIN, it means that the MPA reply hasn&amp;#39;t
been received completely, and should not report IW_CM_EVENT_CONNECT_REPLY
in this case. This may trigger a call trace in iw_cm. A simple way to
trigger this:
 server: ib_send_lat
 client: ib_send_lat -R &amp;lt;server_ip&amp;gt;&lt;/p&gt;
&lt;p&gt;The call trace looks like this:&lt;/p&gt;
&lt;p&gt;kernel BUG at drivers/infiniband/core/iwcm.c:894!
 invalid opcode: 0000 [#1] PREEMPT SMP NOPTI
 &amp;lt;...&amp;gt;
 Workqueue: iw_cm_wq cm_work_handler [iw_cm]
 Call Trace:
  &amp;lt;TASK&amp;gt;
  cm_work_handler+0x1dd/0x370 [iw_cm]
  process_one_work+0x1e2/0x3b0
  worker_thread+0x49/0x2e0
  ? rescuer_thread+0x370/0x370
  kthread+0xe5/0x110
  ? kthread_complete_and_exit+0x20/0x20
  ret_from_fork+0x1f/0x30
  &amp;lt;/TASK&amp;gt;&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2022-50136</guid>
    </item>
    <item>
      <title>GHSA-mgp7-42mx-57gj</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-mgp7-42mx-57gj</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;RDMA/siw: Fix duplicated reported IW_CM_EVENT_CONNECT_REPLY event&lt;/p&gt;
&lt;p&gt;If siw_recv_mpa_rr returns -EAGAIN, it means that the MPA reply hasn&amp;#39;t
been received completely, and should not report IW_CM_EVENT_CONNECT_REPLY
in this case. This may trigger a call trace in iw_cm. A simple way to
trigger this:
 server: ib_send_lat
 client: ib_send_lat -R &amp;lt;server_ip&amp;gt;&lt;/p&gt;
&lt;p&gt;The call trace looks like this:&lt;/p&gt;
&lt;p&gt;kernel BUG at drivers/infiniband/core/iwcm.c:894!
 invalid opcode: 0000 [#1] PREEMPT SMP NOPTI
 &amp;lt;...&amp;gt;
 Workqueue: iw_cm_wq cm_work_handler [iw_cm]
 Call Trace:
  &amp;lt;TASK&amp;gt;
  cm_work_handler+0x1dd/0x370 [iw_cm]
  process_one_work+0x1e2/0x3b0
  worker_thread+0x49/0x2e0
  ? rescuer_thread+0x370/0x370
  kthread+0xe5/0x110
  ? kthread_complete_and_exit+0x20/0x20
  ret_from_fork+0x1f/0x30
  &amp;lt;/TASK&amp;gt;&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;RDMA/siw: Fix duplicated reported IW_CM_EVENT_CONNECT_REPLY event&lt;/p&gt;
&lt;p&gt;If siw_recv_mpa_rr returns -EAGAIN, it means that the MPA reply hasn&amp;#39;t
been received completely, and should not report IW_CM_EVENT_CONNECT_REPLY
in this case. This may trigger a call trace in iw_cm. A simple way to
trigger this:
 server: ib_send_lat
 client: ib_send_lat -R &amp;lt;server_ip&amp;gt;&lt;/p&gt;
&lt;p&gt;The call trace looks like this:&lt;/p&gt;
&lt;p&gt;kernel BUG at drivers/infiniband/core/iwcm.c:894!
 invalid opcode: 0000 [#1] PREEMPT SMP NOPTI
 &amp;lt;...&amp;gt;
 Workqueue: iw_cm_wq cm_work_handler [iw_cm]
 Call Trace:
  &amp;lt;TASK&amp;gt;
  cm_work_handler+0x1dd/0x370 [iw_cm]
  process_one_work+0x1e2/0x3b0
  worker_thread+0x49/0x2e0
  ? rescuer_thread+0x370/0x370
  kthread+0xe5/0x110
  ? kthread_complete_and_exit+0x20/0x20
  ret_from_fork+0x1f/0x30
  &amp;lt;/TASK&amp;gt;&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-mgp7-42mx-57gj</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-2025:02264-1 — Security update for the Linux Kernel</title>
      <link>https://cve.radiocsirt.org/vuln/suse-su-2025:02264-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:02264-1</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2022-50136</title>
      <link>https://cve.radiocsirt.org/vuln/ubuntu-cve-2022-50136</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-ibm-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 and 119 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: RDMA/siw: Fix duplicated reported IW_CM_EVENT_CONNECT_REPLY event If siw_recv_mpa_rr returns -EAGAIN, it means that the MPA reply hasn&amp;#39;t been received completely, and should not report IW_CM_EVENT_CONNECT_REPLY in this case. This may trigger a call trace in iw_cm. A simple way to trigger this:  server: ib_send_lat  client: ib_send_lat -R &amp;lt;server_ip&amp;gt; The call trace looks like this:  kernel BUG at drivers/infiniband/core/iwcm.c:894!  invalid opcode: 0000 [#1] PREEMPT SMP NOPTI  &amp;lt;...&amp;gt;  Workqueue: iw_cm_wq cm_work_handler [iw_cm]  Call Trace:   &amp;lt;TASK&amp;gt;   cm_work_handler+0x1dd/0x370 [iw_cm]   process_one_work+0x1e2/0x3b0   worker_thread+0x49/0x2e0   ? rescuer_thread+0x370/0x370   kthread+0xe5/0x110   ? kthread_complete_and_exit+0x20/0x20   ret_from_fork+0x1f/0x30   &amp;lt;/TASK&amp;gt;&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-ibm-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 and 119 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: RDMA/siw: Fix duplicated reported IW_CM_EVENT_CONNECT_REPLY event If siw_recv_mpa_rr returns -EAGAIN, it means that the MPA reply hasn&amp;#39;t been received completely, and should not report IW_CM_EVENT_CONNECT_REPLY in this case. This may trigger a call trace in iw_cm. A simple way to trigger this:  server: ib_send_lat  client: ib_send_lat -R &amp;lt;server_ip&amp;gt; The call trace looks like this:  kernel BUG at drivers/infiniband/core/iwcm.c:894!  invalid opcode: 0000 [#1] PREEMPT SMP NOPTI  &amp;lt;...&amp;gt;  Workqueue: iw_cm_wq cm_work_handler [iw_cm]  Call Trace:   &amp;lt;TASK&amp;gt;   cm_work_handler+0x1dd/0x370 [iw_cm]   process_one_work+0x1e2/0x3b0   worker_thread+0x49/0x2e0   ? rescuer_thread+0x370/0x370   kthread+0xe5/0x110   ? kthread_complete_and_exit+0x20/0x20   ret_from_fork+0x1f/0x30   &amp;lt;/TASK&amp;gt;&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ubuntu-cve-2022-50136</guid>
    </item>
    <item>
      <title>WID-SEC-W-2025-1350 — Linux Kernel: Mehrere Schwachstellen ermöglichen Denial of Service</title>
      <link>https://cve.radiocsirt.org/vuln/wid-sec-w-2025-1350</link>
      <description>&lt;p&gt;Ein lokaler Angreifer kann mehrere Schwachstellen in Linux Kernel ausnutzen, um einen Denial of Service Angriff durchzuführen.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Ein lokaler Angreifer kann mehrere Schwachstellen in Linux Kernel ausnutzen, um einen Denial of Service Angriff durchzuführen.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/wid-sec-w-2025-1350</guid>
    </item>
  </channel>
</rss>
