<?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 02:47:18 +0000</lastBuildDate>
    <item>
      <title>bdu:2025-15095</title>
      <link>https://cve.radiocsirt.org/vuln/bdu:2025-15095</link>
      <description>bdu:2025-15095</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/bdu:2025-15095</guid>
    </item>
    <item>
      <title>BELL-CVE-2024-50254</title>
      <link>https://cve.radiocsirt.org/vuln/bell-cve-2024-50254</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; 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:25: linux-lts, Alpaquita:stream: linux-lts&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/bell-cve-2024-50254</guid>
    </item>
    <item>
      <title>certfr-2025-avi-0152 — De multiples vulnérabilités ont été découvertes dans le noyau Linux d'Ubuntu. Certaines d'entre elles permettent à un a…</title>
      <link>https://cve.radiocsirt.org/vuln/certfr-2025-avi-0152</link>
      <description>certfr-2025-avi-0152</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/certfr-2025-avi-0152</guid>
    </item>
    <item>
      <title>EUVD-2026-313558</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-313558</link>
      <description>EUVD-2026-313558</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-313558</guid>
    </item>
    <item>
      <title>fkie_cve-2024-50254</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2024-50254</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;bpf: Free dynamically allocated bits in bpf_iter_bits_destroy()&lt;/p&gt;
&lt;p&gt;bpf_iter_bits_destroy() uses &amp;#34;kit-&amp;gt;nr_bits &amp;lt;= 64&amp;#34; to check whether the
bits are dynamically allocated. However, the check is incorrect and may
cause a kmemleak as shown below:&lt;/p&gt;
&lt;p&gt;unreferenced object 0xffff88812628c8c0 (size 32):
  comm &amp;#34;swapper/0&amp;#34;, pid 1, jiffies 4294727320
  hex dump (first 32 bytes):
	b0 c1 55 f5 81 88 ff ff f0 f0 f0 f0 f0 f0 f0 f0  ..U...........
	f0 f0 f0 f0 f0 f0 f0 f0 00 00 00 00 00 00 00 00  ..............
  backtrace (crc 781e32cc):
	[&amp;lt;00000000c452b4ab&amp;gt;] kmemleak_alloc+0x4b/0x80
	[&amp;lt;0000000004e09f80&amp;gt;] __kmalloc_node_noprof+0x480/0x5c0
	[&amp;lt;00000000597124d6&amp;gt;] __alloc.isra.0+0x89/0xb0
	[&amp;lt;000000004ebfffcd&amp;gt;] alloc_bulk+0x2af/0x720
	[&amp;lt;00000000d9c10145&amp;gt;] prefill_mem_cache+0x7f/0xb0
	[&amp;lt;00000000ff9738ff&amp;gt;] bpf_mem_alloc_init+0x3e2/0x610
	[&amp;lt;000000008b616eac&amp;gt;] bpf_global_ma_init+0x19/0x30
	[&amp;lt;00000000fc473efc&amp;gt;] do_one_initcall+0xd3/0x3c0
	[&amp;lt;00000000ec81498c&amp;gt;] kernel_init_freeable+0x66a/0x940
	[&amp;lt;00000000b119f72f&amp;gt;] kernel_init+0x20/0x160
	[&amp;lt;00000000f11ac9a7&amp;gt;] ret_from_fork+0x3c/0x70
	[&amp;lt;0000000004671da4&amp;gt;] ret_from_fork_asm+0x1a/0x30&lt;/p&gt;
&lt;p&gt;That is because nr_bits will be set as zero in bpf_iter_bits_next()
after all bits have been iterated.&lt;/p&gt;
&lt;p&gt;Fix the issue by setting kit-&amp;gt;bit to kit-&amp;gt;nr_bits instead of setting
kit-&amp;gt;nr_bits to zero when the iteration completes in
bpf_iter_bits_next(). In addition, use &amp;#34;!nr_bits || bits &amp;gt;= nr_bits&amp;#34; to
check whethe…&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: Free dynamically allocated bits in bpf_iter_bits_destroy()&lt;/p&gt;
&lt;p&gt;bpf_iter_bits_destroy() uses &amp;#34;kit-&amp;gt;nr_bits &amp;lt;= 64&amp;#34; to check whether the
bits are dynamically allocated. However, the check is incorrect and may
cause a kmemleak as shown below:&lt;/p&gt;
&lt;p&gt;unreferenced object 0xffff88812628c8c0 (size 32):
  comm &amp;#34;swapper/0&amp;#34;, pid 1, jiffies 4294727320
  hex dump (first 32 bytes):
	b0 c1 55 f5 81 88 ff ff f0 f0 f0 f0 f0 f0 f0 f0  ..U...........
	f0 f0 f0 f0 f0 f0 f0 f0 00 00 00 00 00 00 00 00  ..............
  backtrace (crc 781e32cc):
	[&amp;lt;00000000c452b4ab&amp;gt;] kmemleak_alloc+0x4b/0x80
	[&amp;lt;0000000004e09f80&amp;gt;] __kmalloc_node_noprof+0x480/0x5c0
	[&amp;lt;00000000597124d6&amp;gt;] __alloc.isra.0+0x89/0xb0
	[&amp;lt;000000004ebfffcd&amp;gt;] alloc_bulk+0x2af/0x720
	[&amp;lt;00000000d9c10145&amp;gt;] prefill_mem_cache+0x7f/0xb0
	[&amp;lt;00000000ff9738ff&amp;gt;] bpf_mem_alloc_init+0x3e2/0x610
	[&amp;lt;000000008b616eac&amp;gt;] bpf_global_ma_init+0x19/0x30
	[&amp;lt;00000000fc473efc&amp;gt;] do_one_initcall+0xd3/0x3c0
	[&amp;lt;00000000ec81498c&amp;gt;] kernel_init_freeable+0x66a/0x940
	[&amp;lt;00000000b119f72f&amp;gt;] kernel_init+0x20/0x160
	[&amp;lt;00000000f11ac9a7&amp;gt;] ret_from_fork+0x3c/0x70
	[&amp;lt;0000000004671da4&amp;gt;] ret_from_fork_asm+0x1a/0x30&lt;/p&gt;
&lt;p&gt;That is because nr_bits will be set as zero in bpf_iter_bits_next()
after all bits have been iterated.&lt;/p&gt;
&lt;p&gt;Fix the issue by setting kit-&amp;gt;bit to kit-&amp;gt;nr_bits instead of setting
kit-&amp;gt;nr_bits to zero when the iteration completes in
bpf_iter_bits_next(). In addition, use &amp;#34;!nr_bits || bits &amp;gt;= nr_bits&amp;#34; to
check whethe…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2024-50254</guid>
    </item>
    <item>
      <title>GHSA-c7cg-c752-q6q2</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-c7cg-c752-q6q2</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;bpf: Free dynamically allocated bits in bpf_iter_bits_destroy()&lt;/p&gt;
&lt;p&gt;bpf_iter_bits_destroy() uses &amp;#34;kit-&amp;gt;nr_bits &amp;lt;= 64&amp;#34; to check whether the
bits are dynamically allocated. However, the check is incorrect and may
cause a kmemleak as shown below:&lt;/p&gt;
&lt;p&gt;unreferenced object 0xffff88812628c8c0 (size 32):
  comm &amp;#34;swapper/0&amp;#34;, pid 1, jiffies 4294727320
  hex dump (first 32 bytes):
	b0 c1 55 f5 81 88 ff ff f0 f0 f0 f0 f0 f0 f0 f0  ..U...........
	f0 f0 f0 f0 f0 f0 f0 f0 00 00 00 00 00 00 00 00  ..............
  backtrace (crc 781e32cc):
	[&amp;lt;00000000c452b4ab&amp;gt;] kmemleak_alloc+0x4b/0x80
	[&amp;lt;0000000004e09f80&amp;gt;] __kmalloc_node_noprof+0x480/0x5c0
	[&amp;lt;00000000597124d6&amp;gt;] __alloc.isra.0+0x89/0xb0
	[&amp;lt;000000004ebfffcd&amp;gt;] alloc_bulk+0x2af/0x720
	[&amp;lt;00000000d9c10145&amp;gt;] prefill_mem_cache+0x7f/0xb0
	[&amp;lt;00000000ff9738ff&amp;gt;] bpf_mem_alloc_init+0x3e2/0x610
	[&amp;lt;000000008b616eac&amp;gt;] bpf_global_ma_init+0x19/0x30
	[&amp;lt;00000000fc473efc&amp;gt;] do_one_initcall+0xd3/0x3c0
	[&amp;lt;00000000ec81498c&amp;gt;] kernel_init_freeable+0x66a/0x940
	[&amp;lt;00000000b119f72f&amp;gt;] kernel_init+0x20/0x160
	[&amp;lt;00000000f11ac9a7&amp;gt;] ret_from_fork+0x3c/0x70
	[&amp;lt;0000000004671da4&amp;gt;] ret_from_fork_asm+0x1a/0x30&lt;/p&gt;
&lt;p&gt;That is because nr_bits will be set as zero in bpf_iter_bits_next()
after all bits have been iterated.&lt;/p&gt;
&lt;p&gt;Fix the issue by setting kit-&amp;gt;bit to kit-&amp;gt;nr_bits instead of setting
kit-&amp;gt;nr_bits to zero when the iteration completes in
bpf_iter_bits_next(). In addition, use &amp;#34;!nr_bits || bits &amp;gt;= nr_bits&amp;#34; to
check whethe…&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: Free dynamically allocated bits in bpf_iter_bits_destroy()&lt;/p&gt;
&lt;p&gt;bpf_iter_bits_destroy() uses &amp;#34;kit-&amp;gt;nr_bits &amp;lt;= 64&amp;#34; to check whether the
bits are dynamically allocated. However, the check is incorrect and may
cause a kmemleak as shown below:&lt;/p&gt;
&lt;p&gt;unreferenced object 0xffff88812628c8c0 (size 32):
  comm &amp;#34;swapper/0&amp;#34;, pid 1, jiffies 4294727320
  hex dump (first 32 bytes):
	b0 c1 55 f5 81 88 ff ff f0 f0 f0 f0 f0 f0 f0 f0  ..U...........
	f0 f0 f0 f0 f0 f0 f0 f0 00 00 00 00 00 00 00 00  ..............
  backtrace (crc 781e32cc):
	[&amp;lt;00000000c452b4ab&amp;gt;] kmemleak_alloc+0x4b/0x80
	[&amp;lt;0000000004e09f80&amp;gt;] __kmalloc_node_noprof+0x480/0x5c0
	[&amp;lt;00000000597124d6&amp;gt;] __alloc.isra.0+0x89/0xb0
	[&amp;lt;000000004ebfffcd&amp;gt;] alloc_bulk+0x2af/0x720
	[&amp;lt;00000000d9c10145&amp;gt;] prefill_mem_cache+0x7f/0xb0
	[&amp;lt;00000000ff9738ff&amp;gt;] bpf_mem_alloc_init+0x3e2/0x610
	[&amp;lt;000000008b616eac&amp;gt;] bpf_global_ma_init+0x19/0x30
	[&amp;lt;00000000fc473efc&amp;gt;] do_one_initcall+0xd3/0x3c0
	[&amp;lt;00000000ec81498c&amp;gt;] kernel_init_freeable+0x66a/0x940
	[&amp;lt;00000000b119f72f&amp;gt;] kernel_init+0x20/0x160
	[&amp;lt;00000000f11ac9a7&amp;gt;] ret_from_fork+0x3c/0x70
	[&amp;lt;0000000004671da4&amp;gt;] ret_from_fork_asm+0x1a/0x30&lt;/p&gt;
&lt;p&gt;That is because nr_bits will be set as zero in bpf_iter_bits_next()
after all bits have been iterated.&lt;/p&gt;
&lt;p&gt;Fix the issue by setting kit-&amp;gt;bit to kit-&amp;gt;nr_bits instead of setting
kit-&amp;gt;nr_bits to zero when the iteration completes in
bpf_iter_bits_next(). In addition, use &amp;#34;!nr_bits || bits &amp;gt;= nr_bits&amp;#34; to
check whethe…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-c7cg-c752-q6q2</guid>
    </item>
    <item>
      <title>openSUSE-SU-2024:14500-1 — kernel-devel-6.11.8-1.1 on GA media</title>
      <link>https://cve.radiocsirt.org/vuln/opensuse-su-2024:14500-1</link>
      <description>&lt;p&gt;kernel-devel-6.11.8-1.1 on GA media&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;kernel-devel-6.11.8-1.1 on GA media&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/opensuse-su-2024:14500-1</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2024-50254</title>
      <link>https://cve.radiocsirt.org/vuln/ubuntu-cve-2024-50254</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 67 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: bpf: Free dynamically allocated bits in bpf_iter_bits_destroy() bpf_iter_bits_destroy() uses &amp;#34;kit-&amp;gt;nr_bits &amp;lt;= 64&amp;#34; to check whether the bits are dynamically allocated. However, the check is incorrect and may cause a kmemleak as shown below: unreferenced object 0xffff88812628c8c0 (size 32):   comm &amp;#34;swapper/0&amp;#34;, pid 1, jiffies 4294727320   hex dump (first 32 bytes): 	b0 c1 55 f5 81 88 ff ff f0 f0 f0 f0 f0 f0 f0 f0  ..U........... 	f0 f0 f0 f0 f0 f0 f0 f0 00 00 00 00 00 00 00 00  ..............   backtrace (crc 781e32cc): 	[&amp;lt;00000000c452b4ab&amp;gt;] kmemleak_alloc+0x4b/0x80 	[&amp;lt;0000000004e09f80&amp;gt;] __kmalloc_node_noprof+0x480/0x5c0 	[&amp;lt;00000000597124d6&amp;gt;] __alloc.isra.0+0x89/0xb0 	[&amp;lt;000000004ebfffcd&amp;gt;] alloc_bulk+0x2af/0x720 	[&amp;lt;00000000d9c10145&amp;gt;] prefill_mem_cache+0x7f/0xb0 	[&amp;lt;00000000ff9738ff&amp;gt;] bpf_mem_alloc_init+0x3e2/0x610 	[&amp;lt;000000008b616eac&amp;gt;] bpf_global_ma_init+0x19/0x30 	[&amp;lt;00000000fc473efc&amp;gt;] do_one_initcall+0xd3/0x3c0 	[&amp;lt;00000000ec81498c&amp;gt;] kernel_init_freeable+0x66a/0x940 	[&amp;lt;00000000b119f72f&amp;gt;] kernel_init+0x20/0x160 	[&amp;lt;00000000f11ac9a7&amp;gt;] ret_from_fork+0x3c/0x70 	[&amp;lt;0000000004671da4&amp;gt;] ret_from_fork_asm+0x1a/0x30 That is because nr_bits will be set as zero in bpf_iter_bits_next() after all bits have been iterated. Fix the issue by setting kit-&amp;gt;bit to kit-&amp;gt;nr_bits instead of setting kit-&amp;gt;nr_bits to zero when the iteration completes in bpf_iter_bits_next(). In addition, use &amp;#34;!nr_bits || bits &amp;gt;= nr_bits&amp;#34; to check whether the…&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 67 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: bpf: Free dynamically allocated bits in bpf_iter_bits_destroy() bpf_iter_bits_destroy() uses &amp;#34;kit-&amp;gt;nr_bits &amp;lt;= 64&amp;#34; to check whether the bits are dynamically allocated. However, the check is incorrect and may cause a kmemleak as shown below: unreferenced object 0xffff88812628c8c0 (size 32):   comm &amp;#34;swapper/0&amp;#34;, pid 1, jiffies 4294727320   hex dump (first 32 bytes): 	b0 c1 55 f5 81 88 ff ff f0 f0 f0 f0 f0 f0 f0 f0  ..U........... 	f0 f0 f0 f0 f0 f0 f0 f0 00 00 00 00 00 00 00 00  ..............   backtrace (crc 781e32cc): 	[&amp;lt;00000000c452b4ab&amp;gt;] kmemleak_alloc+0x4b/0x80 	[&amp;lt;0000000004e09f80&amp;gt;] __kmalloc_node_noprof+0x480/0x5c0 	[&amp;lt;00000000597124d6&amp;gt;] __alloc.isra.0+0x89/0xb0 	[&amp;lt;000000004ebfffcd&amp;gt;] alloc_bulk+0x2af/0x720 	[&amp;lt;00000000d9c10145&amp;gt;] prefill_mem_cache+0x7f/0xb0 	[&amp;lt;00000000ff9738ff&amp;gt;] bpf_mem_alloc_init+0x3e2/0x610 	[&amp;lt;000000008b616eac&amp;gt;] bpf_global_ma_init+0x19/0x30 	[&amp;lt;00000000fc473efc&amp;gt;] do_one_initcall+0xd3/0x3c0 	[&amp;lt;00000000ec81498c&amp;gt;] kernel_init_freeable+0x66a/0x940 	[&amp;lt;00000000b119f72f&amp;gt;] kernel_init+0x20/0x160 	[&amp;lt;00000000f11ac9a7&amp;gt;] ret_from_fork+0x3c/0x70 	[&amp;lt;0000000004671da4&amp;gt;] ret_from_fork_asm+0x1a/0x30 That is because nr_bits will be set as zero in bpf_iter_bits_next() after all bits have been iterated. Fix the issue by setting kit-&amp;gt;bit to kit-&amp;gt;nr_bits instead of setting kit-&amp;gt;nr_bits to zero when the iteration completes in bpf_iter_bits_next(). In addition, use &amp;#34;!nr_bits || bits &amp;gt;= nr_bits&amp;#34; to check whether the…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ubuntu-cve-2024-50254</guid>
    </item>
    <item>
      <title>WID-SEC-W-2024-3397 — Linux Kernel: Mehrere Schwachstellen ermöglichen nicht spezifizierten Angriff</title>
      <link>https://cve.radiocsirt.org/vuln/wid-sec-w-2024-3397</link>
      <description>&lt;p&gt;Ein lokaler Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um einen nicht näher spezifizierten Angriff durchzuführen.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Ein lokaler Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um einen nicht näher spezifizierten Angriff durchzuführen.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/wid-sec-w-2024-3397</guid>
    </item>
  </channel>
</rss>
