<?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 00:43:49 +0000</lastBuildDate>
    <item>
      <title>bdu:2025-04478</title>
      <link>https://cve.radiocsirt.org/vuln/bdu:2025-04478</link>
      <description>bdu:2025-04478</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/bdu:2025-04478</guid>
    </item>
    <item>
      <title>BELL-CVE-2024-57841</title>
      <link>https://cve.radiocsirt.org/vuln/bell-cve-2024-57841</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Alpaquita:23: linux-lts, Alpaquita:25: linux-lts, Alpaquita:stream: linux-lts&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Alpaquita:23: linux-lts, Alpaquita:25: linux-lts, Alpaquita:stream: linux-lts&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/bell-cve-2024-57841</guid>
    </item>
    <item>
      <title>certfr-2025-avi-0184 — De multiples vulnérabilités ont été découvertes dans le noyau Linux de Debian LTS. Elles permettent à un attaquant de p…</title>
      <link>https://cve.radiocsirt.org/vuln/certfr-2025-avi-0184</link>
      <description>certfr-2025-avi-0184</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/certfr-2025-avi-0184</guid>
    </item>
    <item>
      <title>cnvd-2025-02110</title>
      <link>https://cve.radiocsirt.org/vuln/cnvd-2025-02110</link>
      <description>cnvd-2025-02110</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/cnvd-2025-02110</guid>
    </item>
    <item>
      <title>EUVD-2026-320761</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-320761</link>
      <description>EUVD-2026-320761</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-320761</guid>
    </item>
    <item>
      <title>fkie_cve-2024-57841</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2024-57841</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;net: fix memory leak in tcp_conn_request()&lt;/p&gt;
&lt;p&gt;If inet_csk_reqsk_queue_hash_add() return false, tcp_conn_request() will
return without free the dst memory, which allocated in af_ops-&amp;gt;route_req.&lt;/p&gt;
&lt;p&gt;Here is the kmemleak stack:&lt;/p&gt;
&lt;p&gt;unreferenced object 0xffff8881198631c0 (size 240):
  comm &amp;#34;softirq&amp;#34;, pid 0, jiffies 4299266571 (age 1802.392s)
  hex dump (first 32 bytes):
    00 10 9b 03 81 88 ff ff 80 98 da bc ff ff ff ff  ................
    81 55 18 bb ff ff ff ff 00 00 00 00 00 00 00 00  .U..............
  backtrace:
    [&amp;lt;ffffffffb93e8d4c&amp;gt;] kmem_cache_alloc+0x60c/0xa80
    [&amp;lt;ffffffffba11b4c5&amp;gt;] dst_alloc+0x55/0x250
    [&amp;lt;ffffffffba227bf6&amp;gt;] rt_dst_alloc+0x46/0x1d0
    [&amp;lt;ffffffffba23050a&amp;gt;] __mkroute_output+0x29a/0xa50
    [&amp;lt;ffffffffba23456b&amp;gt;] ip_route_output_key_hash+0x10b/0x240
    [&amp;lt;ffffffffba2346bd&amp;gt;] ip_route_output_flow+0x1d/0x90
    [&amp;lt;ffffffffba254855&amp;gt;] inet_csk_route_req+0x2c5/0x500
    [&amp;lt;ffffffffba26b331&amp;gt;] tcp_conn_request+0x691/0x12c0
    [&amp;lt;ffffffffba27bd08&amp;gt;] tcp_rcv_state_process+0x3c8/0x11b0
    [&amp;lt;ffffffffba2965c6&amp;gt;] tcp_v4_do_rcv+0x156/0x3b0
    [&amp;lt;ffffffffba299c98&amp;gt;] tcp_v4_rcv+0x1cf8/0x1d80
    [&amp;lt;ffffffffba239656&amp;gt;] ip_protocol_deliver_rcu+0xf6/0x360
    [&amp;lt;ffffffffba2399a6&amp;gt;] ip_local_deliver_finish+0xe6/0x1e0
    [&amp;lt;ffffffffba239b8e&amp;gt;] ip_local_deliver+0xee/0x360
    [&amp;lt;ffffffffba239ead&amp;gt;] ip_rcv+0xad/0x2f0
    [&amp;lt;ffffffffba110943&amp;gt;] __netif_receive_skb_one_core+0x123/0x140&lt;/p&gt;
&lt;p&gt;Call dst_release() to free the dst memor…&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;net: fix memory leak in tcp_conn_request()&lt;/p&gt;
&lt;p&gt;If inet_csk_reqsk_queue_hash_add() return false, tcp_conn_request() will
return without free the dst memory, which allocated in af_ops-&amp;gt;route_req.&lt;/p&gt;
&lt;p&gt;Here is the kmemleak stack:&lt;/p&gt;
&lt;p&gt;unreferenced object 0xffff8881198631c0 (size 240):
  comm &amp;#34;softirq&amp;#34;, pid 0, jiffies 4299266571 (age 1802.392s)
  hex dump (first 32 bytes):
    00 10 9b 03 81 88 ff ff 80 98 da bc ff ff ff ff  ................
    81 55 18 bb ff ff ff ff 00 00 00 00 00 00 00 00  .U..............
  backtrace:
    [&amp;lt;ffffffffb93e8d4c&amp;gt;] kmem_cache_alloc+0x60c/0xa80
    [&amp;lt;ffffffffba11b4c5&amp;gt;] dst_alloc+0x55/0x250
    [&amp;lt;ffffffffba227bf6&amp;gt;] rt_dst_alloc+0x46/0x1d0
    [&amp;lt;ffffffffba23050a&amp;gt;] __mkroute_output+0x29a/0xa50
    [&amp;lt;ffffffffba23456b&amp;gt;] ip_route_output_key_hash+0x10b/0x240
    [&amp;lt;ffffffffba2346bd&amp;gt;] ip_route_output_flow+0x1d/0x90
    [&amp;lt;ffffffffba254855&amp;gt;] inet_csk_route_req+0x2c5/0x500
    [&amp;lt;ffffffffba26b331&amp;gt;] tcp_conn_request+0x691/0x12c0
    [&amp;lt;ffffffffba27bd08&amp;gt;] tcp_rcv_state_process+0x3c8/0x11b0
    [&amp;lt;ffffffffba2965c6&amp;gt;] tcp_v4_do_rcv+0x156/0x3b0
    [&amp;lt;ffffffffba299c98&amp;gt;] tcp_v4_rcv+0x1cf8/0x1d80
    [&amp;lt;ffffffffba239656&amp;gt;] ip_protocol_deliver_rcu+0xf6/0x360
    [&amp;lt;ffffffffba2399a6&amp;gt;] ip_local_deliver_finish+0xe6/0x1e0
    [&amp;lt;ffffffffba239b8e&amp;gt;] ip_local_deliver+0xee/0x360
    [&amp;lt;ffffffffba239ead&amp;gt;] ip_rcv+0xad/0x2f0
    [&amp;lt;ffffffffba110943&amp;gt;] __netif_receive_skb_one_core+0x123/0x140&lt;/p&gt;
&lt;p&gt;Call dst_release() to free the dst memor…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2024-57841</guid>
    </item>
    <item>
      <title>GHSA-qxf9-65gj-mxj8</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-qxf9-65gj-mxj8</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;net: fix memory leak in tcp_conn_request()&lt;/p&gt;
&lt;p&gt;If inet_csk_reqsk_queue_hash_add() return false, tcp_conn_request() will
return without free the dst memory, which allocated in af_ops-&amp;gt;route_req.&lt;/p&gt;
&lt;p&gt;Here is the kmemleak stack:&lt;/p&gt;
&lt;p&gt;unreferenced object 0xffff8881198631c0 (size 240):
  comm &amp;#34;softirq&amp;#34;, pid 0, jiffies 4299266571 (age 1802.392s)
  hex dump (first 32 bytes):
    00 10 9b 03 81 88 ff ff 80 98 da bc ff ff ff ff  ................
    81 55 18 bb ff ff ff ff 00 00 00 00 00 00 00 00  .U..............
  backtrace:
    [&amp;lt;ffffffffb93e8d4c&amp;gt;] kmem_cache_alloc+0x60c/0xa80
    [&amp;lt;ffffffffba11b4c5&amp;gt;] dst_alloc+0x55/0x250
    [&amp;lt;ffffffffba227bf6&amp;gt;] rt_dst_alloc+0x46/0x1d0
    [&amp;lt;ffffffffba23050a&amp;gt;] __mkroute_output+0x29a/0xa50
    [&amp;lt;ffffffffba23456b&amp;gt;] ip_route_output_key_hash+0x10b/0x240
    [&amp;lt;ffffffffba2346bd&amp;gt;] ip_route_output_flow+0x1d/0x90
    [&amp;lt;ffffffffba254855&amp;gt;] inet_csk_route_req+0x2c5/0x500
    [&amp;lt;ffffffffba26b331&amp;gt;] tcp_conn_request+0x691/0x12c0
    [&amp;lt;ffffffffba27bd08&amp;gt;] tcp_rcv_state_process+0x3c8/0x11b0
    [&amp;lt;ffffffffba2965c6&amp;gt;] tcp_v4_do_rcv+0x156/0x3b0
    [&amp;lt;ffffffffba299c98&amp;gt;] tcp_v4_rcv+0x1cf8/0x1d80
    [&amp;lt;ffffffffba239656&amp;gt;] ip_protocol_deliver_rcu+0xf6/0x360
    [&amp;lt;ffffffffba2399a6&amp;gt;] ip_local_deliver_finish+0xe6/0x1e0
    [&amp;lt;ffffffffba239b8e&amp;gt;] ip_local_deliver+0xee/0x360
    [&amp;lt;ffffffffba239ead&amp;gt;] ip_rcv+0xad/0x2f0
    [&amp;lt;ffffffffba110943&amp;gt;] __netif_receive_skb_one_core+0x123/0x140&lt;/p&gt;
&lt;p&gt;Call dst_release() to free the dst memor…&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;net: fix memory leak in tcp_conn_request()&lt;/p&gt;
&lt;p&gt;If inet_csk_reqsk_queue_hash_add() return false, tcp_conn_request() will
return without free the dst memory, which allocated in af_ops-&amp;gt;route_req.&lt;/p&gt;
&lt;p&gt;Here is the kmemleak stack:&lt;/p&gt;
&lt;p&gt;unreferenced object 0xffff8881198631c0 (size 240):
  comm &amp;#34;softirq&amp;#34;, pid 0, jiffies 4299266571 (age 1802.392s)
  hex dump (first 32 bytes):
    00 10 9b 03 81 88 ff ff 80 98 da bc ff ff ff ff  ................
    81 55 18 bb ff ff ff ff 00 00 00 00 00 00 00 00  .U..............
  backtrace:
    [&amp;lt;ffffffffb93e8d4c&amp;gt;] kmem_cache_alloc+0x60c/0xa80
    [&amp;lt;ffffffffba11b4c5&amp;gt;] dst_alloc+0x55/0x250
    [&amp;lt;ffffffffba227bf6&amp;gt;] rt_dst_alloc+0x46/0x1d0
    [&amp;lt;ffffffffba23050a&amp;gt;] __mkroute_output+0x29a/0xa50
    [&amp;lt;ffffffffba23456b&amp;gt;] ip_route_output_key_hash+0x10b/0x240
    [&amp;lt;ffffffffba2346bd&amp;gt;] ip_route_output_flow+0x1d/0x90
    [&amp;lt;ffffffffba254855&amp;gt;] inet_csk_route_req+0x2c5/0x500
    [&amp;lt;ffffffffba26b331&amp;gt;] tcp_conn_request+0x691/0x12c0
    [&amp;lt;ffffffffba27bd08&amp;gt;] tcp_rcv_state_process+0x3c8/0x11b0
    [&amp;lt;ffffffffba2965c6&amp;gt;] tcp_v4_do_rcv+0x156/0x3b0
    [&amp;lt;ffffffffba299c98&amp;gt;] tcp_v4_rcv+0x1cf8/0x1d80
    [&amp;lt;ffffffffba239656&amp;gt;] ip_protocol_deliver_rcu+0xf6/0x360
    [&amp;lt;ffffffffba2399a6&amp;gt;] ip_local_deliver_finish+0xe6/0x1e0
    [&amp;lt;ffffffffba239b8e&amp;gt;] ip_local_deliver+0xee/0x360
    [&amp;lt;ffffffffba239ead&amp;gt;] ip_rcv+0xad/0x2f0
    [&amp;lt;ffffffffba110943&amp;gt;] __netif_receive_skb_one_core+0x123/0x140&lt;/p&gt;
&lt;p&gt;Call dst_release() to free the dst memor…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-qxf9-65gj-mxj8</guid>
    </item>
    <item>
      <title>msrc_CVE-2024-57841 — net: fix memory leak in tcp_conn_request()</title>
      <link>https://cve.radiocsirt.org/vuln/msrc_cve-2024-57841</link>
      <description>msrc_CVE-2024-57841</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/msrc_cve-2024-57841</guid>
    </item>
    <item>
      <title>OESA-2025-1110 — kernel security update</title>
      <link>https://cve.radiocsirt.org/vuln/oesa-2025-1110</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; openEuler:24.03-LTS: 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;i3c: Use i3cdev-&amp;amp;gt;desc-&amp;amp;gt;info instead of calling i3c_device_get_info() to avoid deadlock&lt;/p&gt;
&lt;p&gt;A deadlock may happen since the i3c_master_register() acquires
&amp;amp;amp;i3cbus-&amp;amp;gt;lock twice. See the log below.
Use i3cdev-&amp;amp;gt;desc-&amp;amp;gt;info instead of calling i3c_device_info() to
avoid acquiring the lock twice.&lt;/p&gt;
&lt;p&gt;v2:
  - Modified the title and commit message&lt;/p&gt;
&lt;p&gt;============================================
WARNING: possible recursive locking detected
6.11.0-mainline
--------------------------------------------
init/1 is trying to acquire lock:
f1ffff80a6a40dc0 (&amp;amp;amp;i3cbus-&amp;amp;gt;lock){++++}-{3:3}, at: i3c_bus_normaluse_lock&lt;/p&gt;
&lt;p&gt;but task is already holding lock:
f1ffff80a6a40dc0 (&amp;amp;amp;i3cbus-&amp;amp;gt;lock){++++}-{3:3}, at: i3c_master_register&lt;/p&gt;
&lt;p&gt;other info that might help us debug this:
 Possible unsafe locking scenario:&lt;/p&gt;
&lt;p&gt;CPU0
       ----
  lock(&amp;amp;amp;i3cbus-&amp;amp;gt;lock);
  lock(&amp;amp;amp;i3cbus-&amp;amp;gt;lock);&lt;/p&gt;
&lt;p&gt;*** DEADLOCK ***&lt;/p&gt;
&lt;p&gt;May be due to missing lock nesting notation&lt;/p&gt;
&lt;p&gt;2 locks held by init/1:
 #0: fcffff809b6798f8 (&amp;amp;amp;dev-&amp;amp;gt;mutex){....}-{3:3}, at: __driver_attach
 #1: f1ffff80a6a40dc0 (&amp;amp;amp;i3cbus-&amp;amp;gt;lock){++++}-{3:3}, at: i3c_master_register&lt;/p&gt;
&lt;p&gt;stack backtrace:
CPU: 6 UID: 0 PID: 1 Comm: init
Call trace:
 dump_backtrace+0xfc/0x17c
 show_stack+0x18/0x28
 dump_stack_lvl+0x40/0xc0
 dump_stack+0x18/0x24
 print_deadlock_bug+0x388/0x390
 __lock_acquire+0x18bc/0…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; openEuler:24.03-LTS: 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;i3c: Use i3cdev-&amp;amp;gt;desc-&amp;amp;gt;info instead of calling i3c_device_get_info() to avoid deadlock&lt;/p&gt;
&lt;p&gt;A deadlock may happen since the i3c_master_register() acquires
&amp;amp;amp;i3cbus-&amp;amp;gt;lock twice. See the log below.
Use i3cdev-&amp;amp;gt;desc-&amp;amp;gt;info instead of calling i3c_device_info() to
avoid acquiring the lock twice.&lt;/p&gt;
&lt;p&gt;v2:
  - Modified the title and commit message&lt;/p&gt;
&lt;p&gt;============================================
WARNING: possible recursive locking detected
6.11.0-mainline
--------------------------------------------
init/1 is trying to acquire lock:
f1ffff80a6a40dc0 (&amp;amp;amp;i3cbus-&amp;amp;gt;lock){++++}-{3:3}, at: i3c_bus_normaluse_lock&lt;/p&gt;
&lt;p&gt;but task is already holding lock:
f1ffff80a6a40dc0 (&amp;amp;amp;i3cbus-&amp;amp;gt;lock){++++}-{3:3}, at: i3c_master_register&lt;/p&gt;
&lt;p&gt;other info that might help us debug this:
 Possible unsafe locking scenario:&lt;/p&gt;
&lt;p&gt;CPU0
       ----
  lock(&amp;amp;amp;i3cbus-&amp;amp;gt;lock);
  lock(&amp;amp;amp;i3cbus-&amp;amp;gt;lock);&lt;/p&gt;
&lt;p&gt;*** DEADLOCK ***&lt;/p&gt;
&lt;p&gt;May be due to missing lock nesting notation&lt;/p&gt;
&lt;p&gt;2 locks held by init/1:
 #0: fcffff809b6798f8 (&amp;amp;amp;dev-&amp;amp;gt;mutex){....}-{3:3}, at: __driver_attach
 #1: f1ffff80a6a40dc0 (&amp;amp;amp;i3cbus-&amp;amp;gt;lock){++++}-{3:3}, at: i3c_master_register&lt;/p&gt;
&lt;p&gt;stack backtrace:
CPU: 6 UID: 0 PID: 1 Comm: init
Call trace:
 dump_backtrace+0xfc/0x17c
 show_stack+0x18/0x28
 dump_stack_lvl+0x40/0xc0
 dump_stack+0x18/0x24
 print_deadlock_bug+0x388/0x390
 __lock_acquire+0x18bc/0…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/oesa-2025-1110</guid>
    </item>
    <item>
      <title>SUSE-SU-2026:23477-1 — Security update for the Linux Kernel</title>
      <link>https://cve.radiocsirt.org/vuln/suse-su-2026:23477-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:23477-1</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2024-57841</title>
      <link>https://cve.radiocsirt.org/vuln/ubuntu-cve-2024-57841</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 137 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: net: fix memory leak in tcp_conn_request() If inet_csk_reqsk_queue_hash_add() return false, tcp_conn_request() will return without free the dst memory, which allocated in af_ops-&amp;gt;route_req. Here is the kmemleak stack: unreferenced object 0xffff8881198631c0 (size 240):   comm &amp;#34;softirq&amp;#34;, pid 0, jiffies 4299266571 (age 1802.392s)   hex dump (first 32 bytes):     00 10 9b 03 81 88 ff ff 80 98 da bc ff ff ff ff  ................     81 55 18 bb ff ff ff ff 00 00 00 00 00 00 00 00  .U..............   backtrace:     [&amp;lt;ffffffffb93e8d4c&amp;gt;] kmem_cache_alloc+0x60c/0xa80     [&amp;lt;ffffffffba11b4c5&amp;gt;] dst_alloc+0x55/0x250     [&amp;lt;ffffffffba227bf6&amp;gt;] rt_dst_alloc+0x46/0x1d0     [&amp;lt;ffffffffba23050a&amp;gt;] __mkroute_output+0x29a/0xa50     [&amp;lt;ffffffffba23456b&amp;gt;] ip_route_output_key_hash+0x10b/0x240     [&amp;lt;ffffffffba2346bd&amp;gt;] ip_route_output_flow+0x1d/0x90     [&amp;lt;ffffffffba254855&amp;gt;] inet_csk_route_req+0x2c5/0x500     [&amp;lt;ffffffffba26b331&amp;gt;] tcp_conn_request+0x691/0x12c0     [&amp;lt;ffffffffba27bd08&amp;gt;] tcp_rcv_state_process+0x3c8/0x11b0     [&amp;lt;ffffffffba2965c6&amp;gt;] tcp_v4_do_rcv+0x156/0x3b0     [&amp;lt;ffffffffba299c98&amp;gt;] tcp_v4_rcv+0x1cf8/0x1d80     [&amp;lt;ffffffffba239656&amp;gt;] ip_protocol_deliver_rcu+0xf6/0x360     [&amp;lt;ffffffffba2399a6&amp;gt;] ip_local_deliver_finish+0xe6/0x1e0     [&amp;lt;ffffffffba239b8e&amp;gt;] ip_local_deliver+0xee/0x360     [&amp;lt;ffffffffba239ead&amp;gt;] ip_rcv+0xad/0x2f0     [&amp;lt;ffffffffba110943&amp;gt;] __netif_receive_skb_one_core+0x123/0x140 Call dst_release() to free the dst memory whe…&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 137 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: net: fix memory leak in tcp_conn_request() If inet_csk_reqsk_queue_hash_add() return false, tcp_conn_request() will return without free the dst memory, which allocated in af_ops-&amp;gt;route_req. Here is the kmemleak stack: unreferenced object 0xffff8881198631c0 (size 240):   comm &amp;#34;softirq&amp;#34;, pid 0, jiffies 4299266571 (age 1802.392s)   hex dump (first 32 bytes):     00 10 9b 03 81 88 ff ff 80 98 da bc ff ff ff ff  ................     81 55 18 bb ff ff ff ff 00 00 00 00 00 00 00 00  .U..............   backtrace:     [&amp;lt;ffffffffb93e8d4c&amp;gt;] kmem_cache_alloc+0x60c/0xa80     [&amp;lt;ffffffffba11b4c5&amp;gt;] dst_alloc+0x55/0x250     [&amp;lt;ffffffffba227bf6&amp;gt;] rt_dst_alloc+0x46/0x1d0     [&amp;lt;ffffffffba23050a&amp;gt;] __mkroute_output+0x29a/0xa50     [&amp;lt;ffffffffba23456b&amp;gt;] ip_route_output_key_hash+0x10b/0x240     [&amp;lt;ffffffffba2346bd&amp;gt;] ip_route_output_flow+0x1d/0x90     [&amp;lt;ffffffffba254855&amp;gt;] inet_csk_route_req+0x2c5/0x500     [&amp;lt;ffffffffba26b331&amp;gt;] tcp_conn_request+0x691/0x12c0     [&amp;lt;ffffffffba27bd08&amp;gt;] tcp_rcv_state_process+0x3c8/0x11b0     [&amp;lt;ffffffffba2965c6&amp;gt;] tcp_v4_do_rcv+0x156/0x3b0     [&amp;lt;ffffffffba299c98&amp;gt;] tcp_v4_rcv+0x1cf8/0x1d80     [&amp;lt;ffffffffba239656&amp;gt;] ip_protocol_deliver_rcu+0xf6/0x360     [&amp;lt;ffffffffba2399a6&amp;gt;] ip_local_deliver_finish+0xe6/0x1e0     [&amp;lt;ffffffffba239b8e&amp;gt;] ip_local_deliver+0xee/0x360     [&amp;lt;ffffffffba239ead&amp;gt;] ip_rcv+0xad/0x2f0     [&amp;lt;ffffffffba110943&amp;gt;] __netif_receive_skb_one_core+0x123/0x140 Call dst_release() to free the dst memory whe…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ubuntu-cve-2024-57841</guid>
    </item>
    <item>
      <title>WID-SEC-W-2025-0105 — Linux Kernel: Mehrere Schwachstellen ermöglichen Denial of Service</title>
      <link>https://cve.radiocsirt.org/vuln/wid-sec-w-2025-0105</link>
      <description>&lt;p&gt;Ein lokaler Angreifer kann mehrere Schwachstellen im 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 im 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-0105</guid>
    </item>
  </channel>
</rss>
