<?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 21:18:09 +0000</lastBuildDate>
    <item>
      <title>bdu:2025-03303</title>
      <link>https://cve.radiocsirt.org/vuln/bdu:2025-03303</link>
      <description>bdu:2025-03303</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/bdu:2025-03303</guid>
    </item>
    <item>
      <title>BELL-CVE-2024-53125</title>
      <link>https://cve.radiocsirt.org/vuln/bell-cve-2024-53125</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-53125</guid>
    </item>
    <item>
      <title>certfr-2025-avi-0047 — De multiples vulnérabilités ont été découvertes dans les produits SUSE. Certaines d'entre elles permettent à un attaqua…</title>
      <link>https://cve.radiocsirt.org/vuln/certfr-2025-avi-0047</link>
      <description>certfr-2025-avi-0047</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/certfr-2025-avi-0047</guid>
    </item>
    <item>
      <title>EUVD-2026-346407</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-346407</link>
      <description>EUVD-2026-346407</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-346407</guid>
    </item>
    <item>
      <title>fkie_cve-2024-53125</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2024-53125</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;bpf: sync_linked_regs() must preserve subreg_def&lt;/p&gt;
&lt;p&gt;Range propagation must not affect subreg_def marks, otherwise the
following example is rewritten by verifier incorrectly when
BPF_F_TEST_RND_HI32 flag is set:&lt;/p&gt;
&lt;p&gt;0: call bpf_ktime_get_ns                   call bpf_ktime_get_ns
  1: r0 &amp;amp;= 0x7fffffff       after verifier   r0 &amp;amp;= 0x7fffffff
  2: w1 = w0                rewrites         w1 = w0
  3: if w0 &amp;lt; 10 goto +0     --------------&amp;gt;  r11 = 0x2f5674a6     (r)
  4: r1 &amp;gt;&amp;gt;= 32                               r11 &amp;lt;&amp;lt;= 32           (r)
  5: r0 = r1                                 r1 |= r11            (r)
  6: exit;                                   if w0 &amp;lt; 0xa goto pc+0
                                             r1 &amp;gt;&amp;gt;= 32
                                             r0 = r1
                                             exit&lt;/p&gt;
&lt;p&gt;(or zero extension of w1 at (2) is missing for architectures that
 require zero extension for upper register half).&lt;/p&gt;
&lt;p&gt;The following happens w/o this patch:
- r0 is marked as not a subreg at (0);
- w1 is marked as subreg at (2);
- w1 subreg_def is overridden at (3) by copy_register_state();
- w1 is read at (5) but mark_insn_zext() does not mark (2)
  for zero extension, because w1 subreg_def is not set;
- because of BPF_F_TEST_RND_HI32 flag verifier inserts random
  value for hi32 bits of (2) (marked (r));
- this random value is read at (5).&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: sync_linked_regs() must preserve subreg_def&lt;/p&gt;
&lt;p&gt;Range propagation must not affect subreg_def marks, otherwise the
following example is rewritten by verifier incorrectly when
BPF_F_TEST_RND_HI32 flag is set:&lt;/p&gt;
&lt;p&gt;0: call bpf_ktime_get_ns                   call bpf_ktime_get_ns
  1: r0 &amp;amp;= 0x7fffffff       after verifier   r0 &amp;amp;= 0x7fffffff
  2: w1 = w0                rewrites         w1 = w0
  3: if w0 &amp;lt; 10 goto +0     --------------&amp;gt;  r11 = 0x2f5674a6     (r)
  4: r1 &amp;gt;&amp;gt;= 32                               r11 &amp;lt;&amp;lt;= 32           (r)
  5: r0 = r1                                 r1 |= r11            (r)
  6: exit;                                   if w0 &amp;lt; 0xa goto pc+0
                                             r1 &amp;gt;&amp;gt;= 32
                                             r0 = r1
                                             exit&lt;/p&gt;
&lt;p&gt;(or zero extension of w1 at (2) is missing for architectures that
 require zero extension for upper register half).&lt;/p&gt;
&lt;p&gt;The following happens w/o this patch:
- r0 is marked as not a subreg at (0);
- w1 is marked as subreg at (2);
- w1 subreg_def is overridden at (3) by copy_register_state();
- w1 is read at (5) but mark_insn_zext() does not mark (2)
  for zero extension, because w1 subreg_def is not set;
- because of BPF_F_TEST_RND_HI32 flag verifier inserts random
  value for hi32 bits of (2) (marked (r));
- this random value is read at (5).&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2024-53125</guid>
    </item>
    <item>
      <title>GHSA-jgf3-fmmf-vj4h</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-jgf3-fmmf-vj4h</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;bpf: sync_linked_regs() must preserve subreg_def&lt;/p&gt;
&lt;p&gt;Range propagation must not affect subreg_def marks, otherwise the
following example is rewritten by verifier incorrectly when
BPF_F_TEST_RND_HI32 flag is set:&lt;/p&gt;
&lt;p&gt;0: call bpf_ktime_get_ns                   call bpf_ktime_get_ns
  1: r0 &amp;amp;= 0x7fffffff       after verifier   r0 &amp;amp;= 0x7fffffff
  2: w1 = w0                rewrites         w1 = w0
  3: if w0 &amp;lt; 10 goto +0     --------------&amp;gt;  r11 = 0x2f5674a6     (r)
  4: r1 &amp;gt;&amp;gt;= 32                               r11 &amp;lt;&amp;lt;= 32           (r)
  5: r0 = r1                                 r1 |= r11            (r)
  6: exit;                                   if w0 &amp;lt; 0xa goto pc+0
                                             r1 &amp;gt;&amp;gt;= 32
                                             r0 = r1
                                             exit&lt;/p&gt;
&lt;p&gt;(or zero extension of w1 at (2) is missing for architectures that
 require zero extension for upper register half).&lt;/p&gt;
&lt;p&gt;The following happens w/o this patch:
- r0 is marked as not a subreg at (0);
- w1 is marked as subreg at (2);
- w1 subreg_def is overridden at (3) by copy_register_state();
- w1 is read at (5) but mark_insn_zext() does not mark (2)
  for zero extension, because w1 subreg_def is not set;
- because of BPF_F_TEST_RND_HI32 flag verifier inserts random
  value for hi32 bits of (2) (marked (r));
- this random value is read at (5).&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: sync_linked_regs() must preserve subreg_def&lt;/p&gt;
&lt;p&gt;Range propagation must not affect subreg_def marks, otherwise the
following example is rewritten by verifier incorrectly when
BPF_F_TEST_RND_HI32 flag is set:&lt;/p&gt;
&lt;p&gt;0: call bpf_ktime_get_ns                   call bpf_ktime_get_ns
  1: r0 &amp;amp;= 0x7fffffff       after verifier   r0 &amp;amp;= 0x7fffffff
  2: w1 = w0                rewrites         w1 = w0
  3: if w0 &amp;lt; 10 goto +0     --------------&amp;gt;  r11 = 0x2f5674a6     (r)
  4: r1 &amp;gt;&amp;gt;= 32                               r11 &amp;lt;&amp;lt;= 32           (r)
  5: r0 = r1                                 r1 |= r11            (r)
  6: exit;                                   if w0 &amp;lt; 0xa goto pc+0
                                             r1 &amp;gt;&amp;gt;= 32
                                             r0 = r1
                                             exit&lt;/p&gt;
&lt;p&gt;(or zero extension of w1 at (2) is missing for architectures that
 require zero extension for upper register half).&lt;/p&gt;
&lt;p&gt;The following happens w/o this patch:
- r0 is marked as not a subreg at (0);
- w1 is marked as subreg at (2);
- w1 subreg_def is overridden at (3) by copy_register_state();
- w1 is read at (5) but mark_insn_zext() does not mark (2)
  for zero extension, because w1 subreg_def is not set;
- because of BPF_F_TEST_RND_HI32 flag verifier inserts random
  value for hi32 bits of (2) (marked (r));
- this random value is read at (5).&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-jgf3-fmmf-vj4h</guid>
    </item>
    <item>
      <title>OESA-2024-2533 — kernel security update</title>
      <link>https://cve.radiocsirt.org/vuln/oesa-2024-2533</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; openEuler:22.03-LTS-SP4: kernel&lt;/p&gt;
&lt;p&gt;The Linux Kernel, the operating system core itself.&#13;
&#13;
Security Fix(es):&#13;
&#13;
In the Linux kernel, the following vulnerability has been resolved:  wifi: mac80211: use two-phase skb reclamation in ieee80211_do_stop()  Since &amp;amp;apos;__dev_queue_xmit()&amp;amp;apos; should be called with interrupts enabled, the following backtrace:  ieee80211_do_stop()  ...  spin_lock_irqsave(&amp;amp;amp;local-&amp;amp;gt;queue_stop_reason_lock, flags)  ...  ieee80211_free_txskb()   ieee80211_report_used_skb()    ieee80211_report_ack_skb()     cfg80211_mgmt_tx_status_ext()      nl80211_frame_tx_status()       genlmsg_multicast_netns()        genlmsg_multicast_netns_filtered()         nlmsg_multicast_filtered()   netlink_broadcast_filtered()    do_one_broadcast()     netlink_broadcast_deliver()      __netlink_sendskb()       netlink_deliver_tap()        __netlink_deliver_tap_skb()         dev_queue_xmit()          __dev_queue_xmit() ; with IRQS disabled  ...  spin_unlock_irqrestore(&amp;amp;amp;local-&amp;amp;gt;queue_stop_reason_lock, flags)  issues the warning (as reported by syzbot reproducer):  WARNING: CPU: 2 PID: 5128 at kernel/softirq.c:362 __local_bh_enable_ip+0xc3/0x120  Fix this by implementing a two-phase skb reclamation in &amp;amp;apos;ieee80211_do_stop()&amp;amp;apos;, where actual work is performed outside of a section with interrupts disabled.(CVE-2024-47713)&#13;
&#13;
In the Linux kernel, the following vulnerability has been resolved:  bpf: Fix helper writes to read-only maps  Lonial found an issue that despite user- and BPF-side frozen BPF ma…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; openEuler:22.03-LTS-SP4: kernel&lt;/p&gt;
&lt;p&gt;The Linux Kernel, the operating system core itself.&#13;
&#13;
Security Fix(es):&#13;
&#13;
In the Linux kernel, the following vulnerability has been resolved:  wifi: mac80211: use two-phase skb reclamation in ieee80211_do_stop()  Since &amp;amp;apos;__dev_queue_xmit()&amp;amp;apos; should be called with interrupts enabled, the following backtrace:  ieee80211_do_stop()  ...  spin_lock_irqsave(&amp;amp;amp;local-&amp;amp;gt;queue_stop_reason_lock, flags)  ...  ieee80211_free_txskb()   ieee80211_report_used_skb()    ieee80211_report_ack_skb()     cfg80211_mgmt_tx_status_ext()      nl80211_frame_tx_status()       genlmsg_multicast_netns()        genlmsg_multicast_netns_filtered()         nlmsg_multicast_filtered()   netlink_broadcast_filtered()    do_one_broadcast()     netlink_broadcast_deliver()      __netlink_sendskb()       netlink_deliver_tap()        __netlink_deliver_tap_skb()         dev_queue_xmit()          __dev_queue_xmit() ; with IRQS disabled  ...  spin_unlock_irqrestore(&amp;amp;amp;local-&amp;amp;gt;queue_stop_reason_lock, flags)  issues the warning (as reported by syzbot reproducer):  WARNING: CPU: 2 PID: 5128 at kernel/softirq.c:362 __local_bh_enable_ip+0xc3/0x120  Fix this by implementing a two-phase skb reclamation in &amp;amp;apos;ieee80211_do_stop()&amp;amp;apos;, where actual work is performed outside of a section with interrupts disabled.(CVE-2024-47713)&#13;
&#13;
In the Linux kernel, the following vulnerability has been resolved:  bpf: Fix helper writes to read-only maps  Lonial found an issue that despite user- and BPF-side frozen BPF ma…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/oesa-2024-2533</guid>
    </item>
    <item>
      <title>SUSE-SU-2025:0117-1 — Security update for the Linux Kernel</title>
      <link>https://cve.radiocsirt.org/vuln/suse-su-2025:0117-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:0117-1</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2024-53125</title>
      <link>https://cve.radiocsirt.org/vuln/ubuntu-cve-2024-53125</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 140 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: bpf: sync_linked_regs() must preserve subreg_def Range propagation must not affect subreg_def marks, otherwise the following example is rewritten by verifier incorrectly when BPF_F_TEST_RND_HI32 flag is set:   0: call bpf_ktime_get_ns                   call bpf_ktime_get_ns   1: r0 &amp;amp;= 0x7fffffff       after verifier   r0 &amp;amp;= 0x7fffffff   2: w1 = w0                rewrites         w1 = w0   3: if w0 &amp;lt; 10 goto +0     --------------&amp;gt;  r11 = 0x2f5674a6     (r)   4: r1 &amp;gt;&amp;gt;= 32                               r11 &amp;lt;&amp;lt;= 32           (r)   5: r0 = r1                                 r1 |= r11            (r)   6: exit;                                   if w0 &amp;lt; 0xa goto pc+0                                              r1 &amp;gt;&amp;gt;= 32                                              r0 = r1                                              exit (or zero extension of w1 at (2) is missing for architectures that  require zero extension for upper register half). The following happens w/o this patch: - r0 is marked as not a subreg at (0); - w1 is marked as subreg at (2); - w1 subreg_def is overridden at (3) by copy_register_state(); - w1 is read at (5) but mark_insn_zext() does not mark (2)   for zero extension, because w1 subreg_def is not set; - because of BPF_F_TEST_RND_HI32 flag verifier inserts random   value for hi32 bits of (2) (marked (r)); - this random value is read at (5).&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 140 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: bpf: sync_linked_regs() must preserve subreg_def Range propagation must not affect subreg_def marks, otherwise the following example is rewritten by verifier incorrectly when BPF_F_TEST_RND_HI32 flag is set:   0: call bpf_ktime_get_ns                   call bpf_ktime_get_ns   1: r0 &amp;amp;= 0x7fffffff       after verifier   r0 &amp;amp;= 0x7fffffff   2: w1 = w0                rewrites         w1 = w0   3: if w0 &amp;lt; 10 goto +0     --------------&amp;gt;  r11 = 0x2f5674a6     (r)   4: r1 &amp;gt;&amp;gt;= 32                               r11 &amp;lt;&amp;lt;= 32           (r)   5: r0 = r1                                 r1 |= r11            (r)   6: exit;                                   if w0 &amp;lt; 0xa goto pc+0                                              r1 &amp;gt;&amp;gt;= 32                                              r0 = r1                                              exit (or zero extension of w1 at (2) is missing for architectures that  require zero extension for upper register half). The following happens w/o this patch: - r0 is marked as not a subreg at (0); - w1 is marked as subreg at (2); - w1 subreg_def is overridden at (3) by copy_register_state(); - w1 is read at (5) but mark_insn_zext() does not mark (2)   for zero extension, because w1 subreg_def is not set; - because of BPF_F_TEST_RND_HI32 flag verifier inserts random   value for hi32 bits of (2) (marked (r)); - this random value is read at (5).&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ubuntu-cve-2024-53125</guid>
    </item>
    <item>
      <title>WID-SEC-W-2024-3608 — Linux Kernel: Mehrere Schwachstellen ermöglichen Denial of Service</title>
      <link>https://cve.radiocsirt.org/vuln/wid-sec-w-2024-3608</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-2024-3608</guid>
    </item>
  </channel>
</rss>
