<?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 17:46:09 +0000</lastBuildDate>
    <item>
      <title>bdu:2025-14125</title>
      <link>https://cve.radiocsirt.org/vuln/bdu:2025-14125</link>
      <description>bdu:2025-14125</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/bdu:2025-14125</guid>
    </item>
    <item>
      <title>BELL-CVE-2024-58237</title>
      <link>https://cve.radiocsirt.org/vuln/bell-cve-2024-58237</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-58237</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-346606</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-346606</link>
      <description>EUVD-2026-346606</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-346606</guid>
    </item>
    <item>
      <title>fkie_cve-2024-58237</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2024-58237</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;bpf: consider that tail calls invalidate packet pointers&lt;/p&gt;
&lt;p&gt;Tail-called programs could execute any of the helpers that invalidate
packet pointers. Hence, conservatively assume that each tail call
invalidates packet pointers.&lt;/p&gt;
&lt;p&gt;Making the change in bpf_helper_changes_pkt_data() automatically makes
use of check_cfg() logic that computes &amp;#39;changes_pkt_data&amp;#39; effect for
global sub-programs, such that the following program could be
rejected:&lt;/p&gt;
&lt;p&gt;int tail_call(struct __sk_buff *sk)
    {
    	bpf_tail_call_static(sk, &amp;amp;jmp_table, 0);
    	return 0;
    }&lt;/p&gt;
&lt;p&gt;SEC(&amp;#34;tc&amp;#34;)
    int not_safe(struct __sk_buff *sk)
    {
    	int *p = (void *)(long)sk-&amp;gt;data;
    	... make p valid ...
    	tail_call(sk);
    	*p = 42; /* this is unsafe */
    	...
    }&lt;/p&gt;
&lt;p&gt;The tc_bpf2bpf.c:subprog_tc() needs change: mark it as a function that
can invalidate packet pointers. Otherwise, it can&amp;#39;t be freplaced with
tailcall_freplace.c:entry_freplace() that does a tail call.&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: consider that tail calls invalidate packet pointers&lt;/p&gt;
&lt;p&gt;Tail-called programs could execute any of the helpers that invalidate
packet pointers. Hence, conservatively assume that each tail call
invalidates packet pointers.&lt;/p&gt;
&lt;p&gt;Making the change in bpf_helper_changes_pkt_data() automatically makes
use of check_cfg() logic that computes &amp;#39;changes_pkt_data&amp;#39; effect for
global sub-programs, such that the following program could be
rejected:&lt;/p&gt;
&lt;p&gt;int tail_call(struct __sk_buff *sk)
    {
    	bpf_tail_call_static(sk, &amp;amp;jmp_table, 0);
    	return 0;
    }&lt;/p&gt;
&lt;p&gt;SEC(&amp;#34;tc&amp;#34;)
    int not_safe(struct __sk_buff *sk)
    {
    	int *p = (void *)(long)sk-&amp;gt;data;
    	... make p valid ...
    	tail_call(sk);
    	*p = 42; /* this is unsafe */
    	...
    }&lt;/p&gt;
&lt;p&gt;The tc_bpf2bpf.c:subprog_tc() needs change: mark it as a function that
can invalidate packet pointers. Otherwise, it can&amp;#39;t be freplaced with
tailcall_freplace.c:entry_freplace() that does a tail call.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2024-58237</guid>
    </item>
    <item>
      <title>GHSA-hv6f-p3fq-464p</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-hv6f-p3fq-464p</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;bpf: consider that tail calls invalidate packet pointers&lt;/p&gt;
&lt;p&gt;Tail-called programs could execute any of the helpers that invalidate
packet pointers. Hence, conservatively assume that each tail call
invalidates packet pointers.&lt;/p&gt;
&lt;p&gt;Making the change in bpf_helper_changes_pkt_data() automatically makes
use of check_cfg() logic that computes &amp;#39;changes_pkt_data&amp;#39; effect for
global sub-programs, such that the following program could be
rejected:&lt;/p&gt;
&lt;p&gt;int tail_call(struct __sk_buff *sk)
    {
    	bpf_tail_call_static(sk, &amp;amp;jmp_table, 0);
    	return 0;
    }&lt;/p&gt;
&lt;p&gt;SEC(&amp;#34;tc&amp;#34;)
    int not_safe(struct __sk_buff *sk)
    {
    	int *p = (void *)(long)sk-&amp;gt;data;
    	... make p valid ...
    	tail_call(sk);
    	*p = 42; /* this is unsafe */
    	...
    }&lt;/p&gt;
&lt;p&gt;The tc_bpf2bpf.c:subprog_tc() needs change: mark it as a function that
can invalidate packet pointers. Otherwise, it can&amp;#39;t be freplaced with
tailcall_freplace.c:entry_freplace() that does a tail call.&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: consider that tail calls invalidate packet pointers&lt;/p&gt;
&lt;p&gt;Tail-called programs could execute any of the helpers that invalidate
packet pointers. Hence, conservatively assume that each tail call
invalidates packet pointers.&lt;/p&gt;
&lt;p&gt;Making the change in bpf_helper_changes_pkt_data() automatically makes
use of check_cfg() logic that computes &amp;#39;changes_pkt_data&amp;#39; effect for
global sub-programs, such that the following program could be
rejected:&lt;/p&gt;
&lt;p&gt;int tail_call(struct __sk_buff *sk)
    {
    	bpf_tail_call_static(sk, &amp;amp;jmp_table, 0);
    	return 0;
    }&lt;/p&gt;
&lt;p&gt;SEC(&amp;#34;tc&amp;#34;)
    int not_safe(struct __sk_buff *sk)
    {
    	int *p = (void *)(long)sk-&amp;gt;data;
    	... make p valid ...
    	tail_call(sk);
    	*p = 42; /* this is unsafe */
    	...
    }&lt;/p&gt;
&lt;p&gt;The tc_bpf2bpf.c:subprog_tc() needs change: mark it as a function that
can invalidate packet pointers. Otherwise, it can&amp;#39;t be freplaced with
tailcall_freplace.c:entry_freplace() that does a tail call.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-hv6f-p3fq-464p</guid>
    </item>
    <item>
      <title>msrc_CVE-2024-58237 — bpf: consider that tail calls invalidate packet pointers</title>
      <link>https://cve.radiocsirt.org/vuln/msrc_cve-2024-58237</link>
      <description>msrc_CVE-2024-58237</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/msrc_cve-2024-58237</guid>
    </item>
    <item>
      <title>OESA-2025-1878 — kernel security update</title>
      <link>https://cve.radiocsirt.org/vuln/oesa-2025-1878</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;bpf: consider that tail calls invalidate packet pointers&lt;/p&gt;
&lt;p&gt;Tail-called programs could execute any of the helpers that invalidate
packet pointers. Hence, conservatively assume that each tail call
invalidates packet pointers.&lt;/p&gt;
&lt;p&gt;Making the change in bpf_helper_changes_pkt_data() automatically makes
use of check_cfg() logic that computes &amp;amp;apos;changes_pkt_data&amp;amp;apos; effect for
global sub-programs, such that the following program could be
rejected:&lt;/p&gt;
&lt;p&gt;int tail_call(struct __sk_buff *sk)
    {
    	bpf_tail_call_static(sk, &amp;amp;amp;jmp_table, 0);
    	return 0;
    }&lt;/p&gt;
&lt;p&gt;SEC(&amp;amp;quot;tc&amp;amp;quot;)
    int not_safe(struct __sk_buff *sk)
    {
    	int *p = (void *)(long)sk-&amp;amp;gt;data;
    	... make p valid ...
    	tail_call(sk);
    	*p = 42; /* this is unsafe */
    	...
    }&lt;/p&gt;
&lt;p&gt;The tc_bpf2bpf.c:subprog_tc() needs change: mark it as a function that
can invalidate packet pointers. Otherwise, it can&amp;amp;apos;t be freplaced with
tailcall_freplace.c:entry_freplace() that does a tail call.(CVE-2024-58237)&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;RDMA/rxe: Fix the warning &amp;amp;quot;__rxe_cleanup+0x12c/0x170 [rdma_rxe]&amp;amp;quot;&lt;/p&gt;
&lt;p&gt;The Call Trace is as below:
&amp;amp;quot;
  &amp;amp;lt;TASK&amp;amp;gt;
  ? show_regs.cold+0x1a/0x1f
  ? __rxe_cleanup+0x12c/0x170 [rdma_rxe]
  ? __warn+0x84/0xd0
  ? __rxe_cleanup+0x12c/0x170 [rdma_rxe]
  ? report_bug+0x105/0x180
  ? han…&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;bpf: consider that tail calls invalidate packet pointers&lt;/p&gt;
&lt;p&gt;Tail-called programs could execute any of the helpers that invalidate
packet pointers. Hence, conservatively assume that each tail call
invalidates packet pointers.&lt;/p&gt;
&lt;p&gt;Making the change in bpf_helper_changes_pkt_data() automatically makes
use of check_cfg() logic that computes &amp;amp;apos;changes_pkt_data&amp;amp;apos; effect for
global sub-programs, such that the following program could be
rejected:&lt;/p&gt;
&lt;p&gt;int tail_call(struct __sk_buff *sk)
    {
    	bpf_tail_call_static(sk, &amp;amp;amp;jmp_table, 0);
    	return 0;
    }&lt;/p&gt;
&lt;p&gt;SEC(&amp;amp;quot;tc&amp;amp;quot;)
    int not_safe(struct __sk_buff *sk)
    {
    	int *p = (void *)(long)sk-&amp;amp;gt;data;
    	... make p valid ...
    	tail_call(sk);
    	*p = 42; /* this is unsafe */
    	...
    }&lt;/p&gt;
&lt;p&gt;The tc_bpf2bpf.c:subprog_tc() needs change: mark it as a function that
can invalidate packet pointers. Otherwise, it can&amp;amp;apos;t be freplaced with
tailcall_freplace.c:entry_freplace() that does a tail call.(CVE-2024-58237)&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;RDMA/rxe: Fix the warning &amp;amp;quot;__rxe_cleanup+0x12c/0x170 [rdma_rxe]&amp;amp;quot;&lt;/p&gt;
&lt;p&gt;The Call Trace is as below:
&amp;amp;quot;
  &amp;amp;lt;TASK&amp;amp;gt;
  ? show_regs.cold+0x1a/0x1f
  ? __rxe_cleanup+0x12c/0x170 [rdma_rxe]
  ? __warn+0x84/0xd0
  ? __rxe_cleanup+0x12c/0x170 [rdma_rxe]
  ? report_bug+0x105/0x180
  ? han…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/oesa-2025-1878</guid>
    </item>
    <item>
      <title>SUSE-SU-2025:01964-1 — Security update for the Linux Kernel</title>
      <link>https://cve.radiocsirt.org/vuln/suse-su-2025:01964-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:01964-1</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2024-58237</title>
      <link>https://cve.radiocsirt.org/vuln/ubuntu-cve-2024-58237</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 144 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: bpf: consider that tail calls invalidate packet pointers Tail-called programs could execute any of the helpers that invalidate packet pointers. Hence, conservatively assume that each tail call invalidates packet pointers. Making the change in bpf_helper_changes_pkt_data() automatically makes use of check_cfg() logic that computes &amp;#39;changes_pkt_data&amp;#39; effect for global sub-programs, such that the following program could be rejected:     int tail_call(struct __sk_buff *sk)     {     	bpf_tail_call_static(sk, &amp;amp;jmp_table, 0);     	return 0;     }     SEC(&amp;#34;tc&amp;#34;)     int not_safe(struct __sk_buff *sk)     {     	int *p = (void *)(long)sk-&amp;gt;data;     	... make p valid ...     	tail_call(sk);     	*p = 42; /* this is unsafe */     	...     } The tc_bpf2bpf.c:subprog_tc() needs change: mark it as a function that can invalidate packet pointers. Otherwise, it can&amp;#39;t be freplaced with tailcall_freplace.c:entry_freplace() that does a tail call.&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 144 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: bpf: consider that tail calls invalidate packet pointers Tail-called programs could execute any of the helpers that invalidate packet pointers. Hence, conservatively assume that each tail call invalidates packet pointers. Making the change in bpf_helper_changes_pkt_data() automatically makes use of check_cfg() logic that computes &amp;#39;changes_pkt_data&amp;#39; effect for global sub-programs, such that the following program could be rejected:     int tail_call(struct __sk_buff *sk)     {     	bpf_tail_call_static(sk, &amp;amp;jmp_table, 0);     	return 0;     }     SEC(&amp;#34;tc&amp;#34;)     int not_safe(struct __sk_buff *sk)     {     	int *p = (void *)(long)sk-&amp;gt;data;     	... make p valid ...     	tail_call(sk);     	*p = 42; /* this is unsafe */     	...     } The tc_bpf2bpf.c:subprog_tc() needs change: mark it as a function that can invalidate packet pointers. Otherwise, it can&amp;#39;t be freplaced with tailcall_freplace.c:entry_freplace() that does a tail call.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ubuntu-cve-2024-58237</guid>
    </item>
    <item>
      <title>WID-SEC-W-2025-0945 — Linux Kernel: Mehrere Schwachstellen</title>
      <link>https://cve.radiocsirt.org/vuln/wid-sec-w-2025-0945</link>
      <description>&lt;p&gt;Ein entfernter, anonymer Angreifer kann mehrere Schwachstellen in Linux Kernel ausnutzen, um einen Denial-of-Service auszulösen und weitere unbekannte Auswirkungen herbeizurufen.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Ein entfernter, anonymer Angreifer kann mehrere Schwachstellen in Linux Kernel ausnutzen, um einen Denial-of-Service auszulösen und weitere unbekannte Auswirkungen herbeizurufen.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/wid-sec-w-2025-0945</guid>
    </item>
  </channel>
</rss>
