<?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>Mon, 05 Oct 2026 06:25:03 +0000</lastBuildDate>
    <item>
      <title>bdu:2025-12338</title>
      <link>https://cve.radiocsirt.org/vuln/bdu:2025-12338</link>
      <description>bdu:2025-12338</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/bdu:2025-12338</guid>
    </item>
    <item>
      <title>BELL-CVE-2025-37884</title>
      <link>https://cve.radiocsirt.org/vuln/bell-cve-2025-37884</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Alpaquita:stream: linux-lts&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Alpaquita:stream: linux-lts&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/bell-cve-2025-37884</guid>
    </item>
    <item>
      <title>certfr-2025-avi-0463 — 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-0463</link>
      <description>certfr-2025-avi-0463</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/certfr-2025-avi-0463</guid>
    </item>
    <item>
      <title>EUVD-2026-314302</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-314302</link>
      <description>EUVD-2026-314302</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-314302</guid>
    </item>
    <item>
      <title>fkie_cve-2025-37884</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2025-37884</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;bpf: Fix deadlock between rcu_tasks_trace and event_mutex.&lt;/p&gt;
&lt;p&gt;Fix the following deadlock:
CPU A
_free_event()
  perf_kprobe_destroy()
    mutex_lock(&amp;amp;event_mutex)
      perf_trace_event_unreg()
        synchronize_rcu_tasks_trace()&lt;/p&gt;
&lt;p&gt;There are several paths where _free_event() grabs event_mutex
and calls sync_rcu_tasks_trace. Above is one such case.&lt;/p&gt;
&lt;p&gt;CPU B
bpf_prog_test_run_syscall()
  rcu_read_lock_trace()
    bpf_prog_run_pin_on_cpu()
      bpf_prog_load()
        bpf_tracing_func_proto()
          trace_set_clr_event()
            mutex_lock(&amp;amp;event_mutex)&lt;/p&gt;
&lt;p&gt;Delegate trace_set_clr_event() to workqueue to avoid
such lock dependency.&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: Fix deadlock between rcu_tasks_trace and event_mutex.&lt;/p&gt;
&lt;p&gt;Fix the following deadlock:
CPU A
_free_event()
  perf_kprobe_destroy()
    mutex_lock(&amp;amp;event_mutex)
      perf_trace_event_unreg()
        synchronize_rcu_tasks_trace()&lt;/p&gt;
&lt;p&gt;There are several paths where _free_event() grabs event_mutex
and calls sync_rcu_tasks_trace. Above is one such case.&lt;/p&gt;
&lt;p&gt;CPU B
bpf_prog_test_run_syscall()
  rcu_read_lock_trace()
    bpf_prog_run_pin_on_cpu()
      bpf_prog_load()
        bpf_tracing_func_proto()
          trace_set_clr_event()
            mutex_lock(&amp;amp;event_mutex)&lt;/p&gt;
&lt;p&gt;Delegate trace_set_clr_event() to workqueue to avoid
such lock dependency.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2025-37884</guid>
    </item>
    <item>
      <title>GHSA-9x8p-g64x-m5j5</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-9x8p-g64x-m5j5</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;bpf: Fix deadlock between rcu_tasks_trace and event_mutex.&lt;/p&gt;
&lt;p&gt;Fix the following deadlock:
CPU A
_free_event()
  perf_kprobe_destroy()
    mutex_lock(&amp;amp;event_mutex)
      perf_trace_event_unreg()
        synchronize_rcu_tasks_trace()&lt;/p&gt;
&lt;p&gt;There are several paths where _free_event() grabs event_mutex
and calls sync_rcu_tasks_trace. Above is one such case.&lt;/p&gt;
&lt;p&gt;CPU B
bpf_prog_test_run_syscall()
  rcu_read_lock_trace()
    bpf_prog_run_pin_on_cpu()
      bpf_prog_load()
        bpf_tracing_func_proto()
          trace_set_clr_event()
            mutex_lock(&amp;amp;event_mutex)&lt;/p&gt;
&lt;p&gt;Delegate trace_set_clr_event() to workqueue to avoid
such lock dependency.&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: Fix deadlock between rcu_tasks_trace and event_mutex.&lt;/p&gt;
&lt;p&gt;Fix the following deadlock:
CPU A
_free_event()
  perf_kprobe_destroy()
    mutex_lock(&amp;amp;event_mutex)
      perf_trace_event_unreg()
        synchronize_rcu_tasks_trace()&lt;/p&gt;
&lt;p&gt;There are several paths where _free_event() grabs event_mutex
and calls sync_rcu_tasks_trace. Above is one such case.&lt;/p&gt;
&lt;p&gt;CPU B
bpf_prog_test_run_syscall()
  rcu_read_lock_trace()
    bpf_prog_run_pin_on_cpu()
      bpf_prog_load()
        bpf_tracing_func_proto()
          trace_set_clr_event()
            mutex_lock(&amp;amp;event_mutex)&lt;/p&gt;
&lt;p&gt;Delegate trace_set_clr_event() to workqueue to avoid
such lock dependency.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-9x8p-g64x-m5j5</guid>
    </item>
    <item>
      <title>msrc_CVE-2025-37884 — bpf: Fix deadlock between rcu_tasks_trace and event_mutex.</title>
      <link>https://cve.radiocsirt.org/vuln/msrc_cve-2025-37884</link>
      <description>msrc_CVE-2025-37884</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/msrc_cve-2025-37884</guid>
    </item>
    <item>
      <title>OESA-2025-1539 — kernel security update</title>
      <link>https://cve.radiocsirt.org/vuln/oesa-2025-1539</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: track changes_pkt_data property for global functions&lt;/p&gt;
&lt;p&gt;When processing calls to certain helpers, verifier invalidates all
packet pointers in a current state. For example, consider the
following program:&lt;/p&gt;
&lt;p&gt;__attribute__((__noinline__))
    long skb_pull_data(struct __sk_buff *sk, __u32 len)
    {
        return bpf_skb_pull_data(sk, len);
    }&lt;/p&gt;
&lt;p&gt;SEC(&amp;amp;quot;tc&amp;amp;quot;)
    int test_invalidate_checks(struct __sk_buff *sk)
    {
        int *p = (void *)(long)sk-&amp;amp;gt;data;
        if ((void *)(p + 1) &amp;amp;gt; (void *)(long)sk-&amp;amp;gt;data_end) return TCX_DROP;
        skb_pull_data(sk, 0);
        *p = 42;
        return TCX_PASS;
    }&lt;/p&gt;
&lt;p&gt;After a call to bpf_skb_pull_data() the pointer &amp;amp;apos;p&amp;amp;apos; can&amp;amp;apos;t be used
safely. See function filter.c:bpf_helper_changes_pkt_data() for a list
of such helpers.&lt;/p&gt;
&lt;p&gt;At the moment verifier invalidates packet pointers when processing
helper function calls, and does not traverse global sub-programs when
processing calls to global sub-programs. This means that calls to
helpers done from global sub-programs do not invalidate pointers in
the caller state. E.g. the program above is unsafe, but is not
rejected by verifier.&lt;/p&gt;
&lt;p&gt;This commit fixes the omission by computing field
bpf_subprog_info-&amp;amp;gt;changes_pkt_data for each sub-program before main
verification pass.
changes_pkt_data should be set if:
- subprogram…&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: track changes_pkt_data property for global functions&lt;/p&gt;
&lt;p&gt;When processing calls to certain helpers, verifier invalidates all
packet pointers in a current state. For example, consider the
following program:&lt;/p&gt;
&lt;p&gt;__attribute__((__noinline__))
    long skb_pull_data(struct __sk_buff *sk, __u32 len)
    {
        return bpf_skb_pull_data(sk, len);
    }&lt;/p&gt;
&lt;p&gt;SEC(&amp;amp;quot;tc&amp;amp;quot;)
    int test_invalidate_checks(struct __sk_buff *sk)
    {
        int *p = (void *)(long)sk-&amp;amp;gt;data;
        if ((void *)(p + 1) &amp;amp;gt; (void *)(long)sk-&amp;amp;gt;data_end) return TCX_DROP;
        skb_pull_data(sk, 0);
        *p = 42;
        return TCX_PASS;
    }&lt;/p&gt;
&lt;p&gt;After a call to bpf_skb_pull_data() the pointer &amp;amp;apos;p&amp;amp;apos; can&amp;amp;apos;t be used
safely. See function filter.c:bpf_helper_changes_pkt_data() for a list
of such helpers.&lt;/p&gt;
&lt;p&gt;At the moment verifier invalidates packet pointers when processing
helper function calls, and does not traverse global sub-programs when
processing calls to global sub-programs. This means that calls to
helpers done from global sub-programs do not invalidate pointers in
the caller state. E.g. the program above is unsafe, but is not
rejected by verifier.&lt;/p&gt;
&lt;p&gt;This commit fixes the omission by computing field
bpf_subprog_info-&amp;amp;gt;changes_pkt_data for each sub-program before main
verification pass.
changes_pkt_data should be set if:
- subprogram…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/oesa-2025-1539</guid>
    </item>
    <item>
      <title>SUSE-SU-2025:02249-1 — Security update for the Linux Kernel</title>
      <link>https://cve.radiocsirt.org/vuln/suse-su-2025:02249-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:02249-1</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2025-37884</title>
      <link>https://cve.radiocsirt.org/vuln/ubuntu-cve-2025-37884</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:Pro:14.04:LTS: linux, Ubuntu:Pro:14.04:LTS: linux-aws, Ubuntu:Pro:14.04:LTS: linux-azure, Ubuntu:Pro:14.04:LTS: linux-lts-xenial, Ubuntu:Pro:16.04:LTS: linux, Ubuntu:Pro:16.04:LTS: linux-aws, Ubuntu:Pro:16.04:LTS: linux-aws-hwe, Ubuntu:Pro:16.04:LTS: linux-azure, Ubuntu:Pro:16.04:LTS: linux-gcp, Ubuntu:Pro:16.04:LTS: linux-hwe and 208 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: bpf: Fix deadlock between rcu_tasks_trace and event_mutex. Fix the following deadlock: CPU A _free_event()   perf_kprobe_destroy()     mutex_lock(&amp;amp;event_mutex)       perf_trace_event_unreg()         synchronize_rcu_tasks_trace() There are several paths where _free_event() grabs event_mutex and calls sync_rcu_tasks_trace. Above is one such case. CPU B bpf_prog_test_run_syscall()   rcu_read_lock_trace()     bpf_prog_run_pin_on_cpu()       bpf_prog_load()         bpf_tracing_func_proto()           trace_set_clr_event()             mutex_lock(&amp;amp;event_mutex) Delegate trace_set_clr_event() to workqueue to avoid such lock dependency.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:Pro:14.04:LTS: linux, Ubuntu:Pro:14.04:LTS: linux-aws, Ubuntu:Pro:14.04:LTS: linux-azure, Ubuntu:Pro:14.04:LTS: linux-lts-xenial, Ubuntu:Pro:16.04:LTS: linux, Ubuntu:Pro:16.04:LTS: linux-aws, Ubuntu:Pro:16.04:LTS: linux-aws-hwe, Ubuntu:Pro:16.04:LTS: linux-azure, Ubuntu:Pro:16.04:LTS: linux-gcp, Ubuntu:Pro:16.04:LTS: linux-hwe and 208 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: bpf: Fix deadlock between rcu_tasks_trace and event_mutex. Fix the following deadlock: CPU A _free_event()   perf_kprobe_destroy()     mutex_lock(&amp;amp;event_mutex)       perf_trace_event_unreg()         synchronize_rcu_tasks_trace() There are several paths where _free_event() grabs event_mutex and calls sync_rcu_tasks_trace. Above is one such case. CPU B bpf_prog_test_run_syscall()   rcu_read_lock_trace()     bpf_prog_run_pin_on_cpu()       bpf_prog_load()         bpf_tracing_func_proto()           trace_set_clr_event()             mutex_lock(&amp;amp;event_mutex) Delegate trace_set_clr_event() to workqueue to avoid such lock dependency.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ubuntu-cve-2025-37884</guid>
    </item>
    <item>
      <title>WID-SEC-W-2025-0991 — Linux Kernel: Mehrere Schwachstellen</title>
      <link>https://cve.radiocsirt.org/vuln/wid-sec-w-2025-0991</link>
      <description>&lt;p&gt;Ein Angreifer kann mehrere Schwachstellen in Linux Kernel ausnutzen, um einen Denial of Service Angriff und weitere, 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 weitere, nicht näher spezifizierte Angriffe durchzuführen.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/wid-sec-w-2025-0991</guid>
    </item>
  </channel>
</rss>
