<?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 20:25:58 +0000</lastBuildDate>
    <item>
      <title>bdu:2026-06056</title>
      <link>https://cve.radiocsirt.org/vuln/bdu:2026-06056</link>
      <description>bdu:2026-06056</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/bdu:2026-06056</guid>
    </item>
    <item>
      <title>certfr-2025-avi-0529 — 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-0529</link>
      <description>certfr-2025-avi-0529</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/certfr-2025-avi-0529</guid>
    </item>
    <item>
      <title>EUVD-2026-320332</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-320332</link>
      <description>EUVD-2026-320332</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-320332</guid>
    </item>
    <item>
      <title>fkie_cve-2022-49877</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2022-49877</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;bpf, sockmap: Fix the sk-&amp;gt;sk_forward_alloc warning of sk_stream_kill_queues&lt;/p&gt;
&lt;p&gt;When running `test_sockmap` selftests, the following warning appears:&lt;/p&gt;
&lt;p&gt;WARNING: CPU: 2 PID: 197 at net/core/stream.c:205 sk_stream_kill_queues+0xd3/0xf0
  Call Trace:
  &amp;lt;TASK&amp;gt;
  inet_csk_destroy_sock+0x55/0x110
  tcp_rcv_state_process+0xd28/0x1380
  ? tcp_v4_do_rcv+0x77/0x2c0
  tcp_v4_do_rcv+0x77/0x2c0
  __release_sock+0x106/0x130
  __tcp_close+0x1a7/0x4e0
  tcp_close+0x20/0x70
  inet_release+0x3c/0x80
  __sock_release+0x3a/0xb0
  sock_close+0x14/0x20
  __fput+0xa3/0x260
  task_work_run+0x59/0xb0
  exit_to_user_mode_prepare+0x1b3/0x1c0
  syscall_exit_to_user_mode+0x19/0x50
  do_syscall_64+0x48/0x90
  entry_SYSCALL_64_after_hwframe+0x44/0xae&lt;/p&gt;
&lt;p&gt;The root case is in commit 84472b436e76 (&amp;#34;bpf, sockmap: Fix more uncharged
while msg has more_data&amp;#34;), where I used msg-&amp;gt;sg.size to replace the tosend,
causing breakage:&lt;/p&gt;
&lt;p&gt;if (msg-&amp;gt;apply_bytes &amp;amp;&amp;amp; msg-&amp;gt;apply_bytes &amp;lt; tosend)
    tosend = psock-&amp;gt;apply_bytes;&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 the sk-&amp;gt;sk_forward_alloc warning of sk_stream_kill_queues&lt;/p&gt;
&lt;p&gt;When running `test_sockmap` selftests, the following warning appears:&lt;/p&gt;
&lt;p&gt;WARNING: CPU: 2 PID: 197 at net/core/stream.c:205 sk_stream_kill_queues+0xd3/0xf0
  Call Trace:
  &amp;lt;TASK&amp;gt;
  inet_csk_destroy_sock+0x55/0x110
  tcp_rcv_state_process+0xd28/0x1380
  ? tcp_v4_do_rcv+0x77/0x2c0
  tcp_v4_do_rcv+0x77/0x2c0
  __release_sock+0x106/0x130
  __tcp_close+0x1a7/0x4e0
  tcp_close+0x20/0x70
  inet_release+0x3c/0x80
  __sock_release+0x3a/0xb0
  sock_close+0x14/0x20
  __fput+0xa3/0x260
  task_work_run+0x59/0xb0
  exit_to_user_mode_prepare+0x1b3/0x1c0
  syscall_exit_to_user_mode+0x19/0x50
  do_syscall_64+0x48/0x90
  entry_SYSCALL_64_after_hwframe+0x44/0xae&lt;/p&gt;
&lt;p&gt;The root case is in commit 84472b436e76 (&amp;#34;bpf, sockmap: Fix more uncharged
while msg has more_data&amp;#34;), where I used msg-&amp;gt;sg.size to replace the tosend,
causing breakage:&lt;/p&gt;
&lt;p&gt;if (msg-&amp;gt;apply_bytes &amp;amp;&amp;amp; msg-&amp;gt;apply_bytes &amp;lt; tosend)
    tosend = psock-&amp;gt;apply_bytes;&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2022-49877</guid>
    </item>
    <item>
      <title>GHSA-h8g4-6mrj-mfm8</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-h8g4-6mrj-mfm8</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;bpf, sockmap: Fix the sk-&amp;gt;sk_forward_alloc warning of sk_stream_kill_queues&lt;/p&gt;
&lt;p&gt;When running `test_sockmap` selftests, the following warning appears:&lt;/p&gt;
&lt;p&gt;WARNING: CPU: 2 PID: 197 at net/core/stream.c:205 sk_stream_kill_queues+0xd3/0xf0
  Call Trace:
  &amp;lt;TASK&amp;gt;
  inet_csk_destroy_sock+0x55/0x110
  tcp_rcv_state_process+0xd28/0x1380
  ? tcp_v4_do_rcv+0x77/0x2c0
  tcp_v4_do_rcv+0x77/0x2c0
  __release_sock+0x106/0x130
  __tcp_close+0x1a7/0x4e0
  tcp_close+0x20/0x70
  inet_release+0x3c/0x80
  __sock_release+0x3a/0xb0
  sock_close+0x14/0x20
  __fput+0xa3/0x260
  task_work_run+0x59/0xb0
  exit_to_user_mode_prepare+0x1b3/0x1c0
  syscall_exit_to_user_mode+0x19/0x50
  do_syscall_64+0x48/0x90
  entry_SYSCALL_64_after_hwframe+0x44/0xae&lt;/p&gt;
&lt;p&gt;The root case is in commit 84472b436e76 (&amp;#34;bpf, sockmap: Fix more uncharged
while msg has more_data&amp;#34;), where I used msg-&amp;gt;sg.size to replace the tosend,
causing breakage:&lt;/p&gt;
&lt;p&gt;if (msg-&amp;gt;apply_bytes &amp;amp;&amp;amp; msg-&amp;gt;apply_bytes &amp;lt; tosend)
    tosend = psock-&amp;gt;apply_bytes;&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 the sk-&amp;gt;sk_forward_alloc warning of sk_stream_kill_queues&lt;/p&gt;
&lt;p&gt;When running `test_sockmap` selftests, the following warning appears:&lt;/p&gt;
&lt;p&gt;WARNING: CPU: 2 PID: 197 at net/core/stream.c:205 sk_stream_kill_queues+0xd3/0xf0
  Call Trace:
  &amp;lt;TASK&amp;gt;
  inet_csk_destroy_sock+0x55/0x110
  tcp_rcv_state_process+0xd28/0x1380
  ? tcp_v4_do_rcv+0x77/0x2c0
  tcp_v4_do_rcv+0x77/0x2c0
  __release_sock+0x106/0x130
  __tcp_close+0x1a7/0x4e0
  tcp_close+0x20/0x70
  inet_release+0x3c/0x80
  __sock_release+0x3a/0xb0
  sock_close+0x14/0x20
  __fput+0xa3/0x260
  task_work_run+0x59/0xb0
  exit_to_user_mode_prepare+0x1b3/0x1c0
  syscall_exit_to_user_mode+0x19/0x50
  do_syscall_64+0x48/0x90
  entry_SYSCALL_64_after_hwframe+0x44/0xae&lt;/p&gt;
&lt;p&gt;The root case is in commit 84472b436e76 (&amp;#34;bpf, sockmap: Fix more uncharged
while msg has more_data&amp;#34;), where I used msg-&amp;gt;sg.size to replace the tosend,
causing breakage:&lt;/p&gt;
&lt;p&gt;if (msg-&amp;gt;apply_bytes &amp;amp;&amp;amp; msg-&amp;gt;apply_bytes &amp;lt; tosend)
    tosend = psock-&amp;gt;apply_bytes;&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-h8g4-6mrj-mfm8</guid>
    </item>
    <item>
      <title>SUSE-SU-2025:01983-1 — Security update for the Linux Kernel</title>
      <link>https://cve.radiocsirt.org/vuln/suse-su-2025:01983-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:01983-1</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2022-49877</title>
      <link>https://cve.radiocsirt.org/vuln/ubuntu-cve-2022-49877</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 117 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: bpf, sockmap: Fix the sk-&amp;gt;sk_forward_alloc warning of sk_stream_kill_queues When running `test_sockmap` selftests, the following warning appears:   WARNING: CPU: 2 PID: 197 at net/core/stream.c:205 sk_stream_kill_queues+0xd3/0xf0   Call Trace:   &amp;lt;TASK&amp;gt;   inet_csk_destroy_sock+0x55/0x110   tcp_rcv_state_process+0xd28/0x1380   ? tcp_v4_do_rcv+0x77/0x2c0   tcp_v4_do_rcv+0x77/0x2c0   __release_sock+0x106/0x130   __tcp_close+0x1a7/0x4e0   tcp_close+0x20/0x70   inet_release+0x3c/0x80   __sock_release+0x3a/0xb0   sock_close+0x14/0x20   __fput+0xa3/0x260   task_work_run+0x59/0xb0   exit_to_user_mode_prepare+0x1b3/0x1c0   syscall_exit_to_user_mode+0x19/0x50   do_syscall_64+0x48/0x90   entry_SYSCALL_64_after_hwframe+0x44/0xae The root case is in commit 84472b436e76 (&amp;#34;bpf, sockmap: Fix more uncharged while msg has more_data&amp;#34;), where I used msg-&amp;gt;sg.size to replace the tosend, causing breakage:   if (msg-&amp;gt;apply_bytes &amp;amp;&amp;amp; msg-&amp;gt;apply_bytes &amp;lt; tosend)     tosend = psock-&amp;gt;apply_bytes;&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 117 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: bpf, sockmap: Fix the sk-&amp;gt;sk_forward_alloc warning of sk_stream_kill_queues When running `test_sockmap` selftests, the following warning appears:   WARNING: CPU: 2 PID: 197 at net/core/stream.c:205 sk_stream_kill_queues+0xd3/0xf0   Call Trace:   &amp;lt;TASK&amp;gt;   inet_csk_destroy_sock+0x55/0x110   tcp_rcv_state_process+0xd28/0x1380   ? tcp_v4_do_rcv+0x77/0x2c0   tcp_v4_do_rcv+0x77/0x2c0   __release_sock+0x106/0x130   __tcp_close+0x1a7/0x4e0   tcp_close+0x20/0x70   inet_release+0x3c/0x80   __sock_release+0x3a/0xb0   sock_close+0x14/0x20   __fput+0xa3/0x260   task_work_run+0x59/0xb0   exit_to_user_mode_prepare+0x1b3/0x1c0   syscall_exit_to_user_mode+0x19/0x50   do_syscall_64+0x48/0x90   entry_SYSCALL_64_after_hwframe+0x44/0xae The root case is in commit 84472b436e76 (&amp;#34;bpf, sockmap: Fix more uncharged while msg has more_data&amp;#34;), where I used msg-&amp;gt;sg.size to replace the tosend, causing breakage:   if (msg-&amp;gt;apply_bytes &amp;amp;&amp;amp; msg-&amp;gt;apply_bytes &amp;lt; tosend)     tosend = psock-&amp;gt;apply_bytes;&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ubuntu-cve-2022-49877</guid>
    </item>
    <item>
      <title>WID-SEC-W-2025-0922 — Linux Kernel: Mehrere Schwachstellen</title>
      <link>https://cve.radiocsirt.org/vuln/wid-sec-w-2025-0922</link>
      <description>&lt;p&gt;Ein Angreifer kann mehrere Schwachstellen in Linux Kernel ausnutzen, um einen Denial of Service Angriff und nicht näher spezifizierte Angriffe durchzuführen.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Ein Angreifer kann mehrere Schwachstellen in Linux Kernel ausnutzen, um einen Denial of Service Angriff und nicht näher spezifizierte Angriffe durchzuführen.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/wid-sec-w-2025-0922</guid>
    </item>
  </channel>
</rss>
