<?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 07:20:00 +0000</lastBuildDate>
    <item>
      <title>bdu:2025-07855</title>
      <link>https://cve.radiocsirt.org/vuln/bdu:2025-07855</link>
      <description>bdu:2025-07855</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/bdu:2025-07855</guid>
    </item>
    <item>
      <title>BELL-CVE-2024-56665</title>
      <link>https://cve.radiocsirt.org/vuln/bell-cve-2024-56665</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-56665</guid>
    </item>
    <item>
      <title>certfr-2025-avi-0133 — De multiples vulnérabilités ont été découvertes dans le noyau Linux de SUSE. Elles permettent à un attaquant de provoqu…</title>
      <link>https://cve.radiocsirt.org/vuln/certfr-2025-avi-0133</link>
      <description>certfr-2025-avi-0133</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/certfr-2025-avi-0133</guid>
    </item>
    <item>
      <title>cnvd-2025-01673</title>
      <link>https://cve.radiocsirt.org/vuln/cnvd-2025-01673</link>
      <description>cnvd-2025-01673</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/cnvd-2025-01673</guid>
    </item>
    <item>
      <title>EUVD-2026-320750</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-320750</link>
      <description>EUVD-2026-320750</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-320750</guid>
    </item>
    <item>
      <title>fkie_cve-2024-56665</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2024-56665</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;bpf,perf: Fix invalid prog_array access in perf_event_detach_bpf_prog&lt;/p&gt;
&lt;p&gt;Syzbot reported [1] crash that happens for following tracing scenario:&lt;/p&gt;
&lt;p&gt;- create tracepoint perf event with attr.inherit=1, attach it to the
    process and set bpf program to it
  - attached process forks -&amp;gt; chid creates inherited event&lt;/p&gt;
&lt;p&gt;the new child event shares the parent&amp;#39;s bpf program and tp_event
    (hence prog_array) which is global for tracepoint&lt;/p&gt;
&lt;p&gt;- exit both process and its child -&amp;gt; release both events
  - first perf_event_detach_bpf_prog call will release tp_event-&amp;gt;prog_array
    and second perf_event_detach_bpf_prog will crash, because
    tp_event-&amp;gt;prog_array is NULL&lt;/p&gt;
&lt;p&gt;The fix makes sure the perf_event_detach_bpf_prog checks prog_array
is valid before it tries to remove the bpf program from it.&lt;/p&gt;
&lt;p&gt;[1] https://lore.kernel.org/bpf/Z1MR6dCIKajNS6nU@krava/T/#m91dbf0688221ec7a7fc95e896a7ef9ff93b0b8ad&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,perf: Fix invalid prog_array access in perf_event_detach_bpf_prog&lt;/p&gt;
&lt;p&gt;Syzbot reported [1] crash that happens for following tracing scenario:&lt;/p&gt;
&lt;p&gt;- create tracepoint perf event with attr.inherit=1, attach it to the
    process and set bpf program to it
  - attached process forks -&amp;gt; chid creates inherited event&lt;/p&gt;
&lt;p&gt;the new child event shares the parent&amp;#39;s bpf program and tp_event
    (hence prog_array) which is global for tracepoint&lt;/p&gt;
&lt;p&gt;- exit both process and its child -&amp;gt; release both events
  - first perf_event_detach_bpf_prog call will release tp_event-&amp;gt;prog_array
    and second perf_event_detach_bpf_prog will crash, because
    tp_event-&amp;gt;prog_array is NULL&lt;/p&gt;
&lt;p&gt;The fix makes sure the perf_event_detach_bpf_prog checks prog_array
is valid before it tries to remove the bpf program from it.&lt;/p&gt;
&lt;p&gt;[1] https://lore.kernel.org/bpf/Z1MR6dCIKajNS6nU@krava/T/#m91dbf0688221ec7a7fc95e896a7ef9ff93b0b8ad&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2024-56665</guid>
    </item>
    <item>
      <title>GHSA-2x5w-q4pc-79qx</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-2x5w-q4pc-79qx</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;bpf,perf: Fix invalid prog_array access in perf_event_detach_bpf_prog&lt;/p&gt;
&lt;p&gt;Syzbot reported [1] crash that happens for following tracing scenario:&lt;/p&gt;
&lt;p&gt;- create tracepoint perf event with attr.inherit=1, attach it to the
    process and set bpf program to it
  - attached process forks -&amp;gt; chid creates inherited event&lt;/p&gt;
&lt;p&gt;the new child event shares the parent&amp;#39;s bpf program and tp_event
    (hence prog_array) which is global for tracepoint&lt;/p&gt;
&lt;p&gt;- exit both process and its child -&amp;gt; release both events
  - first perf_event_detach_bpf_prog call will release tp_event-&amp;gt;prog_array
    and second perf_event_detach_bpf_prog will crash, because
    tp_event-&amp;gt;prog_array is NULL&lt;/p&gt;
&lt;p&gt;The fix makes sure the perf_event_detach_bpf_prog checks prog_array
is valid before it tries to remove the bpf program from it.&lt;/p&gt;
&lt;p&gt;[1] https://lore.kernel.org/bpf/Z1MR6dCIKajNS6nU@krava/T/#m91dbf0688221ec7a7fc95e896a7ef9ff93b0b8ad&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,perf: Fix invalid prog_array access in perf_event_detach_bpf_prog&lt;/p&gt;
&lt;p&gt;Syzbot reported [1] crash that happens for following tracing scenario:&lt;/p&gt;
&lt;p&gt;- create tracepoint perf event with attr.inherit=1, attach it to the
    process and set bpf program to it
  - attached process forks -&amp;gt; chid creates inherited event&lt;/p&gt;
&lt;p&gt;the new child event shares the parent&amp;#39;s bpf program and tp_event
    (hence prog_array) which is global for tracepoint&lt;/p&gt;
&lt;p&gt;- exit both process and its child -&amp;gt; release both events
  - first perf_event_detach_bpf_prog call will release tp_event-&amp;gt;prog_array
    and second perf_event_detach_bpf_prog will crash, because
    tp_event-&amp;gt;prog_array is NULL&lt;/p&gt;
&lt;p&gt;The fix makes sure the perf_event_detach_bpf_prog checks prog_array
is valid before it tries to remove the bpf program from it.&lt;/p&gt;
&lt;p&gt;[1] https://lore.kernel.org/bpf/Z1MR6dCIKajNS6nU@krava/T/#m91dbf0688221ec7a7fc95e896a7ef9ff93b0b8ad&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-2x5w-q4pc-79qx</guid>
    </item>
    <item>
      <title>msrc_CVE-2024-56665 — bpf,perf: Fix invalid prog_array access in perf_event_detach_bpf_prog</title>
      <link>https://cve.radiocsirt.org/vuln/msrc_cve-2024-56665</link>
      <description>msrc_CVE-2024-56665</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/msrc_cve-2024-56665</guid>
    </item>
    <item>
      <title>OESA-2025-1032 — kernel security update</title>
      <link>https://cve.radiocsirt.org/vuln/oesa-2025-1032</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; openEuler:24.03-LTS-SP1: 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:  sh: cpuinfo: Fix a warning for CONFIG_CPUMASK_OFFSTACK  When CONFIG_CPUMASK_OFFSTACK and CONFIG_DEBUG_PER_CPU_MAPS are selected, cpu_max_bits_warn() generates a runtime warning similar as below when showing /proc/cpuinfo. Fix this by using nr_cpu_ids (the runtime limit) instead of NR_CPUS to iterate CPUs.  [    3.052463] ------------[ cut here ]------------ [    3.059679] WARNING: CPU: 3 PID: 1 at include/linux/cpumask.h:108 show_cpuinfo+0x5e8/0x5f0 [    3.070072] Modules linked in: efivarfs autofs4 [    3.076257] CPU: 0 PID: 1 Comm: systemd Not tainted 5.19-rc5+ #1052 [    3.099465] Stack : 9000000100157b08 9000000000f18530 9000000000cf846c 9000000100154000 [    3.109127]         9000000100157a50 0000000000000000 9000000100157a58 9000000000ef7430 [    3.118774]         90000001001578e8 0000000000000040 0000000000000020 ffffffffffffffff [    3.128412]         0000000000aaaaaa 1ab25f00eec96a37 900000010021de80 900000000101c890 [    3.138056]         0000000000000000 0000000000000000 0000000000000000 0000000000aaaaaa [    3.147711]         ffff8000339dc220 0000000000000001 0000000006ab4000 0000000000000000 [    3.157364]         900000000101c998 0000000000000004 9000000000ef7430 0000000000000000 [    3.167012]         0000000000000009 000000000000006c 0000000000000000 0000000000000000 [    3.176641]         9000000000d3de08 9000000001…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; openEuler:24.03-LTS-SP1: 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:  sh: cpuinfo: Fix a warning for CONFIG_CPUMASK_OFFSTACK  When CONFIG_CPUMASK_OFFSTACK and CONFIG_DEBUG_PER_CPU_MAPS are selected, cpu_max_bits_warn() generates a runtime warning similar as below when showing /proc/cpuinfo. Fix this by using nr_cpu_ids (the runtime limit) instead of NR_CPUS to iterate CPUs.  [    3.052463] ------------[ cut here ]------------ [    3.059679] WARNING: CPU: 3 PID: 1 at include/linux/cpumask.h:108 show_cpuinfo+0x5e8/0x5f0 [    3.070072] Modules linked in: efivarfs autofs4 [    3.076257] CPU: 0 PID: 1 Comm: systemd Not tainted 5.19-rc5+ #1052 [    3.099465] Stack : 9000000100157b08 9000000000f18530 9000000000cf846c 9000000100154000 [    3.109127]         9000000100157a50 0000000000000000 9000000100157a58 9000000000ef7430 [    3.118774]         90000001001578e8 0000000000000040 0000000000000020 ffffffffffffffff [    3.128412]         0000000000aaaaaa 1ab25f00eec96a37 900000010021de80 900000000101c890 [    3.138056]         0000000000000000 0000000000000000 0000000000000000 0000000000aaaaaa [    3.147711]         ffff8000339dc220 0000000000000001 0000000006ab4000 0000000000000000 [    3.157364]         900000000101c998 0000000000000004 9000000000ef7430 0000000000000000 [    3.167012]         0000000000000009 000000000000006c 0000000000000000 0000000000000000 [    3.176641]         9000000000d3de08 9000000001…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/oesa-2025-1032</guid>
    </item>
    <item>
      <title>SUSE-SU-2025:0428-1 — Security update for the Linux Kernel</title>
      <link>https://cve.radiocsirt.org/vuln/suse-su-2025:0428-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:0428-1</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2024-56665</title>
      <link>https://cve.radiocsirt.org/vuln/ubuntu-cve-2024-56665</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 131 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: bpf,perf: Fix invalid prog_array access in perf_event_detach_bpf_prog Syzbot reported [1] crash that happens for following tracing scenario:   - create tracepoint perf event with attr.inherit=1, attach it to the     process and set bpf program to it   - attached process forks -&amp;gt; chid creates inherited event     the new child event shares the parent&amp;#39;s bpf program and tp_event     (hence prog_array) which is global for tracepoint   - exit both process and its child -&amp;gt; release both events   - first perf_event_detach_bpf_prog call will release tp_event-&amp;gt;prog_array     and second perf_event_detach_bpf_prog will crash, because     tp_event-&amp;gt;prog_array is NULL The fix makes sure the perf_event_detach_bpf_prog checks prog_array is valid before it tries to remove the bpf program from it. [1] https://lore.kernel.org/bpf/Z1MR6dCIKajNS6nU@krava/T/#m91dbf0688221ec7a7fc95e896a7ef9ff93b0b8ad&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 131 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: bpf,perf: Fix invalid prog_array access in perf_event_detach_bpf_prog Syzbot reported [1] crash that happens for following tracing scenario:   - create tracepoint perf event with attr.inherit=1, attach it to the     process and set bpf program to it   - attached process forks -&amp;gt; chid creates inherited event     the new child event shares the parent&amp;#39;s bpf program and tp_event     (hence prog_array) which is global for tracepoint   - exit both process and its child -&amp;gt; release both events   - first perf_event_detach_bpf_prog call will release tp_event-&amp;gt;prog_array     and second perf_event_detach_bpf_prog will crash, because     tp_event-&amp;gt;prog_array is NULL The fix makes sure the perf_event_detach_bpf_prog checks prog_array is valid before it tries to remove the bpf program from it. [1] https://lore.kernel.org/bpf/Z1MR6dCIKajNS6nU@krava/T/#m91dbf0688221ec7a7fc95e896a7ef9ff93b0b8ad&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ubuntu-cve-2024-56665</guid>
    </item>
    <item>
      <title>WID-SEC-W-2024-3762 — Linux Kernel: Mehrere Schwachstellen ermöglichen Denial of Service</title>
      <link>https://cve.radiocsirt.org/vuln/wid-sec-w-2024-3762</link>
      <description>&lt;p&gt;Ein lokaler Angreifer kann mehrere Schwachstellen in Linux Kernel ausnutzen, um einen Denial of Service Angriff durchzuführen und um nicht näher beschriebene Effekte zu erzielen.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Ein lokaler Angreifer kann mehrere Schwachstellen in Linux Kernel ausnutzen, um einen Denial of Service Angriff durchzuführen und um nicht näher beschriebene Effekte zu erzielen.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/wid-sec-w-2024-3762</guid>
    </item>
  </channel>
</rss>
