<?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 10:55:44 +0000</lastBuildDate>
    <item>
      <title>bdu:2026-12373</title>
      <link>https://cve.radiocsirt.org/vuln/bdu:2026-12373</link>
      <description>bdu:2026-12373</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/bdu:2026-12373</guid>
    </item>
    <item>
      <title>certfr-2025-avi-0307 — 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-0307</link>
      <description>certfr-2025-avi-0307</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/certfr-2025-avi-0307</guid>
    </item>
    <item>
      <title>EUVD-2026-310395</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-310395</link>
      <description>EUVD-2026-310395</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-310395</guid>
    </item>
    <item>
      <title>fkie_cve-2022-49204</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2022-49204</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;bpf, sockmap: Fix more uncharged while msg has more_data&lt;/p&gt;
&lt;p&gt;In tcp_bpf_send_verdict(), if msg has more data after
tcp_bpf_sendmsg_redir():&lt;/p&gt;
&lt;p&gt;tcp_bpf_send_verdict()
 tosend = msg-&amp;gt;sg.size  //msg-&amp;gt;sg.size = 22220
 case __SK_REDIRECT:
  sk_msg_return()  //uncharged msg-&amp;gt;sg.size(22220) sk-&amp;gt;sk_forward_alloc
  tcp_bpf_sendmsg_redir() //after tcp_bpf_sendmsg_redir, msg-&amp;gt;sg.size=11000
 goto more_data;
 tosend = msg-&amp;gt;sg.size  //msg-&amp;gt;sg.size = 11000
 case __SK_REDIRECT:
  sk_msg_return()  //uncharged msg-&amp;gt;sg.size(11000) to sk-&amp;gt;sk_forward_alloc&lt;/p&gt;
&lt;p&gt;The msg-&amp;gt;sg.size(11000) has been uncharged twice, to fix we can charge the
remaining msg-&amp;gt;sg.size before goto more data.&lt;/p&gt;
&lt;p&gt;This issue can cause the following info:
WARNING: CPU: 0 PID: 9860 at net/core/stream.c:208 sk_stream_kill_queues+0xd4/0x1a0
Call Trace:
 &amp;lt;TASK&amp;gt;
 inet_csk_destroy_sock+0x55/0x110
 __tcp_close+0x279/0x470
 tcp_close+0x1f/0x60
 inet_release+0x3f/0x80
 __sock_release+0x3d/0xb0
 sock_close+0x11/0x20
 __fput+0x92/0x250
 task_work_run+0x6a/0xa0
 do_exit+0x33b/0xb60
 do_group_exit+0x2f/0xa0
 get_signal+0xb6/0x950
 arch_do_signal_or_restart+0xac/0x2a0
 ? vfs_write+0x237/0x290
 exit_to_user_mode_prepare+0xa9/0x200
 syscall_exit_to_user_mode+0x12/0x30
 do_syscall_64+0x46/0x80
 entry_SYSCALL_64_after_hwframe+0x44/0xae
 &amp;lt;/TASK&amp;gt;&lt;/p&gt;
&lt;p&gt;WARNING: CPU: 0 PID: 2136 at net/ipv4/af_inet.c:155 inet_sock_destruct+0x13c/0x260
Call Trace:
 &amp;lt;TASK&amp;gt;
 __sk_destruct+0x24/0x1f0
 sk_psock_destro…&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;bpf, sockmap: Fix more uncharged while msg has more_data&lt;/p&gt;
&lt;p&gt;In tcp_bpf_send_verdict(), if msg has more data after
tcp_bpf_sendmsg_redir():&lt;/p&gt;
&lt;p&gt;tcp_bpf_send_verdict()
 tosend = msg-&amp;gt;sg.size  //msg-&amp;gt;sg.size = 22220
 case __SK_REDIRECT:
  sk_msg_return()  //uncharged msg-&amp;gt;sg.size(22220) sk-&amp;gt;sk_forward_alloc
  tcp_bpf_sendmsg_redir() //after tcp_bpf_sendmsg_redir, msg-&amp;gt;sg.size=11000
 goto more_data;
 tosend = msg-&amp;gt;sg.size  //msg-&amp;gt;sg.size = 11000
 case __SK_REDIRECT:
  sk_msg_return()  //uncharged msg-&amp;gt;sg.size(11000) to sk-&amp;gt;sk_forward_alloc&lt;/p&gt;
&lt;p&gt;The msg-&amp;gt;sg.size(11000) has been uncharged twice, to fix we can charge the
remaining msg-&amp;gt;sg.size before goto more data.&lt;/p&gt;
&lt;p&gt;This issue can cause the following info:
WARNING: CPU: 0 PID: 9860 at net/core/stream.c:208 sk_stream_kill_queues+0xd4/0x1a0
Call Trace:
 &amp;lt;TASK&amp;gt;
 inet_csk_destroy_sock+0x55/0x110
 __tcp_close+0x279/0x470
 tcp_close+0x1f/0x60
 inet_release+0x3f/0x80
 __sock_release+0x3d/0xb0
 sock_close+0x11/0x20
 __fput+0x92/0x250
 task_work_run+0x6a/0xa0
 do_exit+0x33b/0xb60
 do_group_exit+0x2f/0xa0
 get_signal+0xb6/0x950
 arch_do_signal_or_restart+0xac/0x2a0
 ? vfs_write+0x237/0x290
 exit_to_user_mode_prepare+0xa9/0x200
 syscall_exit_to_user_mode+0x12/0x30
 do_syscall_64+0x46/0x80
 entry_SYSCALL_64_after_hwframe+0x44/0xae
 &amp;lt;/TASK&amp;gt;&lt;/p&gt;
&lt;p&gt;WARNING: CPU: 0 PID: 2136 at net/ipv4/af_inet.c:155 inet_sock_destruct+0x13c/0x260
Call Trace:
 &amp;lt;TASK&amp;gt;
 __sk_destruct+0x24/0x1f0
 sk_psock_destro…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2022-49204</guid>
    </item>
    <item>
      <title>GHSA-49f2-6m7x-xrh9</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-49f2-6m7x-xrh9</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;bpf, sockmap: Fix more uncharged while msg has more_data&lt;/p&gt;
&lt;p&gt;In tcp_bpf_send_verdict(), if msg has more data after
tcp_bpf_sendmsg_redir():&lt;/p&gt;
&lt;p&gt;tcp_bpf_send_verdict()
 tosend = msg-&amp;gt;sg.size  //msg-&amp;gt;sg.size = 22220
 case __SK_REDIRECT:
  sk_msg_return()  //uncharged msg-&amp;gt;sg.size(22220) sk-&amp;gt;sk_forward_alloc
  tcp_bpf_sendmsg_redir() //after tcp_bpf_sendmsg_redir, msg-&amp;gt;sg.size=11000
 goto more_data;
 tosend = msg-&amp;gt;sg.size  //msg-&amp;gt;sg.size = 11000
 case __SK_REDIRECT:
  sk_msg_return()  //uncharged msg-&amp;gt;sg.size(11000) to sk-&amp;gt;sk_forward_alloc&lt;/p&gt;
&lt;p&gt;The msg-&amp;gt;sg.size(11000) has been uncharged twice, to fix we can charge the
remaining msg-&amp;gt;sg.size before goto more data.&lt;/p&gt;
&lt;p&gt;This issue can cause the following info:
WARNING: CPU: 0 PID: 9860 at net/core/stream.c:208 sk_stream_kill_queues+0xd4/0x1a0
Call Trace:
 &amp;lt;TASK&amp;gt;
 inet_csk_destroy_sock+0x55/0x110
 __tcp_close+0x279/0x470
 tcp_close+0x1f/0x60
 inet_release+0x3f/0x80
 __sock_release+0x3d/0xb0
 sock_close+0x11/0x20
 __fput+0x92/0x250
 task_work_run+0x6a/0xa0
 do_exit+0x33b/0xb60
 do_group_exit+0x2f/0xa0
 get_signal+0xb6/0x950
 arch_do_signal_or_restart+0xac/0x2a0
 ? vfs_write+0x237/0x290
 exit_to_user_mode_prepare+0xa9/0x200
 syscall_exit_to_user_mode+0x12/0x30
 do_syscall_64+0x46/0x80
 entry_SYSCALL_64_after_hwframe+0x44/0xae
 &amp;lt;/TASK&amp;gt;&lt;/p&gt;
&lt;p&gt;WARNING: CPU: 0 PID: 2136 at net/ipv4/af_inet.c:155 inet_sock_destruct+0x13c/0x260
Call Trace:
 &amp;lt;TASK&amp;gt;
 __sk_destruct+0x24/0x1f0
 sk_psock_destro…&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;bpf, sockmap: Fix more uncharged while msg has more_data&lt;/p&gt;
&lt;p&gt;In tcp_bpf_send_verdict(), if msg has more data after
tcp_bpf_sendmsg_redir():&lt;/p&gt;
&lt;p&gt;tcp_bpf_send_verdict()
 tosend = msg-&amp;gt;sg.size  //msg-&amp;gt;sg.size = 22220
 case __SK_REDIRECT:
  sk_msg_return()  //uncharged msg-&amp;gt;sg.size(22220) sk-&amp;gt;sk_forward_alloc
  tcp_bpf_sendmsg_redir() //after tcp_bpf_sendmsg_redir, msg-&amp;gt;sg.size=11000
 goto more_data;
 tosend = msg-&amp;gt;sg.size  //msg-&amp;gt;sg.size = 11000
 case __SK_REDIRECT:
  sk_msg_return()  //uncharged msg-&amp;gt;sg.size(11000) to sk-&amp;gt;sk_forward_alloc&lt;/p&gt;
&lt;p&gt;The msg-&amp;gt;sg.size(11000) has been uncharged twice, to fix we can charge the
remaining msg-&amp;gt;sg.size before goto more data.&lt;/p&gt;
&lt;p&gt;This issue can cause the following info:
WARNING: CPU: 0 PID: 9860 at net/core/stream.c:208 sk_stream_kill_queues+0xd4/0x1a0
Call Trace:
 &amp;lt;TASK&amp;gt;
 inet_csk_destroy_sock+0x55/0x110
 __tcp_close+0x279/0x470
 tcp_close+0x1f/0x60
 inet_release+0x3f/0x80
 __sock_release+0x3d/0xb0
 sock_close+0x11/0x20
 __fput+0x92/0x250
 task_work_run+0x6a/0xa0
 do_exit+0x33b/0xb60
 do_group_exit+0x2f/0xa0
 get_signal+0xb6/0x950
 arch_do_signal_or_restart+0xac/0x2a0
 ? vfs_write+0x237/0x290
 exit_to_user_mode_prepare+0xa9/0x200
 syscall_exit_to_user_mode+0x12/0x30
 do_syscall_64+0x46/0x80
 entry_SYSCALL_64_after_hwframe+0x44/0xae
 &amp;lt;/TASK&amp;gt;&lt;/p&gt;
&lt;p&gt;WARNING: CPU: 0 PID: 2136 at net/ipv4/af_inet.c:155 inet_sock_destruct+0x13c/0x260
Call Trace:
 &amp;lt;TASK&amp;gt;
 __sk_destruct+0x24/0x1f0
 sk_psock_destro…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-49f2-6m7x-xrh9</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:1176-1 — Security update for the Linux Kernel</title>
      <link>https://cve.radiocsirt.org/vuln/suse-su-2025:1176-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:1176-1</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2022-49204</title>
      <link>https://cve.radiocsirt.org/vuln/ubuntu-cve-2022-49204</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 110 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: bpf, sockmap: Fix more uncharged while msg has more_data In tcp_bpf_send_verdict(), if msg has more data after tcp_bpf_sendmsg_redir(): tcp_bpf_send_verdict()  tosend = msg-&amp;gt;sg.size  //msg-&amp;gt;sg.size = 22220  case __SK_REDIRECT:   sk_msg_return()  //uncharged msg-&amp;gt;sg.size(22220) sk-&amp;gt;sk_forward_alloc   tcp_bpf_sendmsg_redir() //after tcp_bpf_sendmsg_redir, msg-&amp;gt;sg.size=11000  goto more_data;  tosend = msg-&amp;gt;sg.size  //msg-&amp;gt;sg.size = 11000  case __SK_REDIRECT:   sk_msg_return()  //uncharged msg-&amp;gt;sg.size(11000) to sk-&amp;gt;sk_forward_alloc The msg-&amp;gt;sg.size(11000) has been uncharged twice, to fix we can charge the remaining msg-&amp;gt;sg.size before goto more data. This issue can cause the following info: WARNING: CPU: 0 PID: 9860 at net/core/stream.c:208 sk_stream_kill_queues+0xd4/0x1a0 Call Trace:  &amp;lt;TASK&amp;gt;  inet_csk_destroy_sock+0x55/0x110  __tcp_close+0x279/0x470  tcp_close+0x1f/0x60  inet_release+0x3f/0x80  __sock_release+0x3d/0xb0  sock_close+0x11/0x20  __fput+0x92/0x250  task_work_run+0x6a/0xa0  do_exit+0x33b/0xb60  do_group_exit+0x2f/0xa0  get_signal+0xb6/0x950  arch_do_signal_or_restart+0xac/0x2a0  ? vfs_write+0x237/0x290  exit_to_user_mode_prepare+0xa9/0x200  syscall_exit_to_user_mode+0x12/0x30  do_syscall_64+0x46/0x80  entry_SYSCALL_64_after_hwframe+0x44/0xae  &amp;lt;/TASK&amp;gt; WARNING: CPU: 0 PID: 2136 at net/ipv4/af_inet.c:155 inet_sock_destruct+0x13c/0x260 Call Trace:  &amp;lt;TASK&amp;gt;  __sk_destruct+0x24/0x1f0  sk_psock_destroy+0x19…&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 110 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: bpf, sockmap: Fix more uncharged while msg has more_data In tcp_bpf_send_verdict(), if msg has more data after tcp_bpf_sendmsg_redir(): tcp_bpf_send_verdict()  tosend = msg-&amp;gt;sg.size  //msg-&amp;gt;sg.size = 22220  case __SK_REDIRECT:   sk_msg_return()  //uncharged msg-&amp;gt;sg.size(22220) sk-&amp;gt;sk_forward_alloc   tcp_bpf_sendmsg_redir() //after tcp_bpf_sendmsg_redir, msg-&amp;gt;sg.size=11000  goto more_data;  tosend = msg-&amp;gt;sg.size  //msg-&amp;gt;sg.size = 11000  case __SK_REDIRECT:   sk_msg_return()  //uncharged msg-&amp;gt;sg.size(11000) to sk-&amp;gt;sk_forward_alloc The msg-&amp;gt;sg.size(11000) has been uncharged twice, to fix we can charge the remaining msg-&amp;gt;sg.size before goto more data. This issue can cause the following info: WARNING: CPU: 0 PID: 9860 at net/core/stream.c:208 sk_stream_kill_queues+0xd4/0x1a0 Call Trace:  &amp;lt;TASK&amp;gt;  inet_csk_destroy_sock+0x55/0x110  __tcp_close+0x279/0x470  tcp_close+0x1f/0x60  inet_release+0x3f/0x80  __sock_release+0x3d/0xb0  sock_close+0x11/0x20  __fput+0x92/0x250  task_work_run+0x6a/0xa0  do_exit+0x33b/0xb60  do_group_exit+0x2f/0xa0  get_signal+0xb6/0x950  arch_do_signal_or_restart+0xac/0x2a0  ? vfs_write+0x237/0x290  exit_to_user_mode_prepare+0xa9/0x200  syscall_exit_to_user_mode+0x12/0x30  do_syscall_64+0x46/0x80  entry_SYSCALL_64_after_hwframe+0x44/0xae  &amp;lt;/TASK&amp;gt; WARNING: CPU: 0 PID: 2136 at net/ipv4/af_inet.c:155 inet_sock_destruct+0x13c/0x260 Call Trace:  &amp;lt;TASK&amp;gt;  __sk_destruct+0x24/0x1f0  sk_psock_destroy+0x19…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ubuntu-cve-2022-49204</guid>
    </item>
  </channel>
</rss>
