<?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 10:28:05 +0000</lastBuildDate>
    <item>
      <title>bdu:2025-01742</title>
      <link>https://cve.radiocsirt.org/vuln/bdu:2025-01742</link>
      <description>bdu:2025-01742</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/bdu:2025-01742</guid>
    </item>
    <item>
      <title>BELL-CVE-2024-43835</title>
      <link>https://cve.radiocsirt.org/vuln/bell-cve-2024-43835</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-43835</guid>
    </item>
    <item>
      <title>certfr-2024-avi-0837 — De multiples vulnérabilités ont été découvertes dans le noyau Linux de Debian. Elles permettent à un attaquant de provo…</title>
      <link>https://cve.radiocsirt.org/vuln/certfr-2024-avi-0837</link>
      <description>certfr-2024-avi-0837</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/certfr-2024-avi-0837</guid>
    </item>
    <item>
      <title>EUVD-2026-313130</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-313130</link>
      <description>EUVD-2026-313130</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-313130</guid>
    </item>
    <item>
      <title>fkie_cve-2024-43835</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2024-43835</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;virtio_net: Fix napi_skb_cache_put warning&lt;/p&gt;
&lt;p&gt;After the commit bdacf3e34945 (&amp;#34;net: Use nested-BH locking for
napi_alloc_cache.&amp;#34;) was merged, the following warning began to appear:&lt;/p&gt;
&lt;p&gt;WARNING: CPU: 5 PID: 1 at net/core/skbuff.c:1451 napi_skb_cache_put+0x82/0x4b0&lt;/p&gt;
&lt;p&gt;__warn+0x12f/0x340
	  napi_skb_cache_put+0x82/0x4b0
	  napi_skb_cache_put+0x82/0x4b0
	  report_bug+0x165/0x370
	  handle_bug+0x3d/0x80
	  exc_invalid_op+0x1a/0x50
	  asm_exc_invalid_op+0x1a/0x20
	  __free_old_xmit+0x1c8/0x510
	  napi_skb_cache_put+0x82/0x4b0
	  __free_old_xmit+0x1c8/0x510
	  __free_old_xmit+0x1c8/0x510
	  __pfx___free_old_xmit+0x10/0x10&lt;/p&gt;
&lt;p&gt;The issue arises because virtio is assuming it&amp;#39;s running in NAPI context
even when it&amp;#39;s not, such as in the netpoll case.&lt;/p&gt;
&lt;p&gt;To resolve this, modify virtnet_poll_tx() to only set NAPI when budget
is available. Same for virtnet_poll_cleantx(), which always assumed that
it was in a NAPI context.&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;virtio_net: Fix napi_skb_cache_put warning&lt;/p&gt;
&lt;p&gt;After the commit bdacf3e34945 (&amp;#34;net: Use nested-BH locking for
napi_alloc_cache.&amp;#34;) was merged, the following warning began to appear:&lt;/p&gt;
&lt;p&gt;WARNING: CPU: 5 PID: 1 at net/core/skbuff.c:1451 napi_skb_cache_put+0x82/0x4b0&lt;/p&gt;
&lt;p&gt;__warn+0x12f/0x340
	  napi_skb_cache_put+0x82/0x4b0
	  napi_skb_cache_put+0x82/0x4b0
	  report_bug+0x165/0x370
	  handle_bug+0x3d/0x80
	  exc_invalid_op+0x1a/0x50
	  asm_exc_invalid_op+0x1a/0x20
	  __free_old_xmit+0x1c8/0x510
	  napi_skb_cache_put+0x82/0x4b0
	  __free_old_xmit+0x1c8/0x510
	  __free_old_xmit+0x1c8/0x510
	  __pfx___free_old_xmit+0x10/0x10&lt;/p&gt;
&lt;p&gt;The issue arises because virtio is assuming it&amp;#39;s running in NAPI context
even when it&amp;#39;s not, such as in the netpoll case.&lt;/p&gt;
&lt;p&gt;To resolve this, modify virtnet_poll_tx() to only set NAPI when budget
is available. Same for virtnet_poll_cleantx(), which always assumed that
it was in a NAPI context.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2024-43835</guid>
    </item>
    <item>
      <title>GHSA-vgj5-hqjj-6hcj</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-vgj5-hqjj-6hcj</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;virtio_net: Fix napi_skb_cache_put warning&lt;/p&gt;
&lt;p&gt;After the commit bdacf3e34945 (&amp;#34;net: Use nested-BH locking for
napi_alloc_cache.&amp;#34;) was merged, the following warning began to appear:&lt;/p&gt;
&lt;p&gt;WARNING: CPU: 5 PID: 1 at net/core/skbuff.c:1451 napi_skb_cache_put+0x82/0x4b0&lt;/p&gt;
&lt;p&gt;__warn+0x12f/0x340
	  napi_skb_cache_put+0x82/0x4b0
	  napi_skb_cache_put+0x82/0x4b0
	  report_bug+0x165/0x370
	  handle_bug+0x3d/0x80
	  exc_invalid_op+0x1a/0x50
	  asm_exc_invalid_op+0x1a/0x20
	  __free_old_xmit+0x1c8/0x510
	  napi_skb_cache_put+0x82/0x4b0
	  __free_old_xmit+0x1c8/0x510
	  __free_old_xmit+0x1c8/0x510
	  __pfx___free_old_xmit+0x10/0x10&lt;/p&gt;
&lt;p&gt;The issue arises because virtio is assuming it&amp;#39;s running in NAPI context
even when it&amp;#39;s not, such as in the netpoll case.&lt;/p&gt;
&lt;p&gt;To resolve this, modify virtnet_poll_tx() to only set NAPI when budget
is available. Same for virtnet_poll_cleantx(), which always assumed that
it was in a NAPI context.&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;virtio_net: Fix napi_skb_cache_put warning&lt;/p&gt;
&lt;p&gt;After the commit bdacf3e34945 (&amp;#34;net: Use nested-BH locking for
napi_alloc_cache.&amp;#34;) was merged, the following warning began to appear:&lt;/p&gt;
&lt;p&gt;WARNING: CPU: 5 PID: 1 at net/core/skbuff.c:1451 napi_skb_cache_put+0x82/0x4b0&lt;/p&gt;
&lt;p&gt;__warn+0x12f/0x340
	  napi_skb_cache_put+0x82/0x4b0
	  napi_skb_cache_put+0x82/0x4b0
	  report_bug+0x165/0x370
	  handle_bug+0x3d/0x80
	  exc_invalid_op+0x1a/0x50
	  asm_exc_invalid_op+0x1a/0x20
	  __free_old_xmit+0x1c8/0x510
	  napi_skb_cache_put+0x82/0x4b0
	  __free_old_xmit+0x1c8/0x510
	  __free_old_xmit+0x1c8/0x510
	  __pfx___free_old_xmit+0x10/0x10&lt;/p&gt;
&lt;p&gt;The issue arises because virtio is assuming it&amp;#39;s running in NAPI context
even when it&amp;#39;s not, such as in the netpoll case.&lt;/p&gt;
&lt;p&gt;To resolve this, modify virtnet_poll_tx() to only set NAPI when budget
is available. Same for virtnet_poll_cleantx(), which always assumed that
it was in a NAPI context.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-vgj5-hqjj-6hcj</guid>
    </item>
    <item>
      <title>msrc_CVE-2024-43835 — virtio_net: Fix napi_skb_cache_put warning</title>
      <link>https://cve.radiocsirt.org/vuln/msrc_cve-2024-43835</link>
      <description>msrc_CVE-2024-43835</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/msrc_cve-2024-43835</guid>
    </item>
    <item>
      <title>OESA-2024-2446 — kernel security update</title>
      <link>https://cve.radiocsirt.org/vuln/oesa-2024-2446</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):&#13;
&#13;
In the Linux kernel, the following vulnerability has been resolved:&#13;
&#13;
btrfs: zoned: fix use-after-free in do_zone_finish()&#13;
&#13;
Shinichiro reported the following use-after-free triggered by the device
replace operation in fstests btrfs/070.&#13;
&#13;
 BTRFS info (device nullb1): scrub: finished on devid 1 with status: 0
 ==================================================================
 BUG: KASAN: slab-use-after-free in do_zone_finish+0x91a/0xb90 [btrfs]
 Read of size 8 at addr ffff8881543c8060 by task btrfs-cleaner/3494007&#13;
&#13;
 CPU: 0 PID: 3494007 Comm: btrfs-cleaner Tainted: G        W          6.8.0-rc5-kts #1
 Hardware name: Supermicro Super Server/X11SPi-TF, BIOS 3.3 02/21/2020
 Call Trace:
  &amp;amp;lt;TASK&amp;amp;gt;
  dump_stack_lvl+0x5b/0x90
  print_report+0xcf/0x670
  ? __virt_addr_valid+0x200/0x3e0
  kasan_report+0xd8/0x110
  ? do_zone_finish+0x91a/0xb90 [btrfs]
  ? do_zone_finish+0x91a/0xb90 [btrfs]
  do_zone_finish+0x91a/0xb90 [btrfs]
  btrfs_delete_unused_bgs+0x5e1/0x1750 [btrfs]
  ? __pfx_btrfs_delete_unused_bgs+0x10/0x10 [btrfs]
  ? btrfs_put_root+0x2d/0x220 [btrfs]
  ? btrfs_clean_one_deleted_snapshot+0x299/0x430 [btrfs]
  cleaner_kthread+0x21e/0x380 [btrfs]
  ? __pfx_cleaner_kthread+0x10/0x10 [btrfs]
  kthread+0x2e3/0x3c0
  ? __pfx_kthread+0x10/0x10
  ret_from_fork+0x31/0x70
  ? __pfx_kthread+0x10/0x10
  ret_from_fork_asm+0x1b/0x30
  &amp;amp;lt;/TASK&amp;amp;gt;&#13;
&#13;
 Allocated by task 3493983:
  kasan_save_stack+0x33/0…&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):&#13;
&#13;
In the Linux kernel, the following vulnerability has been resolved:&#13;
&#13;
btrfs: zoned: fix use-after-free in do_zone_finish()&#13;
&#13;
Shinichiro reported the following use-after-free triggered by the device
replace operation in fstests btrfs/070.&#13;
&#13;
 BTRFS info (device nullb1): scrub: finished on devid 1 with status: 0
 ==================================================================
 BUG: KASAN: slab-use-after-free in do_zone_finish+0x91a/0xb90 [btrfs]
 Read of size 8 at addr ffff8881543c8060 by task btrfs-cleaner/3494007&#13;
&#13;
 CPU: 0 PID: 3494007 Comm: btrfs-cleaner Tainted: G        W          6.8.0-rc5-kts #1
 Hardware name: Supermicro Super Server/X11SPi-TF, BIOS 3.3 02/21/2020
 Call Trace:
  &amp;amp;lt;TASK&amp;amp;gt;
  dump_stack_lvl+0x5b/0x90
  print_report+0xcf/0x670
  ? __virt_addr_valid+0x200/0x3e0
  kasan_report+0xd8/0x110
  ? do_zone_finish+0x91a/0xb90 [btrfs]
  ? do_zone_finish+0x91a/0xb90 [btrfs]
  do_zone_finish+0x91a/0xb90 [btrfs]
  btrfs_delete_unused_bgs+0x5e1/0x1750 [btrfs]
  ? __pfx_btrfs_delete_unused_bgs+0x10/0x10 [btrfs]
  ? btrfs_put_root+0x2d/0x220 [btrfs]
  ? btrfs_clean_one_deleted_snapshot+0x299/0x430 [btrfs]
  cleaner_kthread+0x21e/0x380 [btrfs]
  ? __pfx_cleaner_kthread+0x10/0x10 [btrfs]
  kthread+0x2e3/0x3c0
  ? __pfx_kthread+0x10/0x10
  ret_from_fork+0x31/0x70
  ? __pfx_kthread+0x10/0x10
  ret_from_fork_asm+0x1b/0x30
  &amp;amp;lt;/TASK&amp;amp;gt;&#13;
&#13;
 Allocated by task 3493983:
  kasan_save_stack+0x33/0…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/oesa-2024-2446</guid>
    </item>
    <item>
      <title>SUSE-SU-2024:3551-1 — Security update for the Linux Kernel</title>
      <link>https://cve.radiocsirt.org/vuln/suse-su-2024:3551-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-2024:3551-1</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2024-43835</title>
      <link>https://cve.radiocsirt.org/vuln/ubuntu-cve-2024-43835</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:Pro:18.04:LTS: linux-aws-5.4, Ubuntu:18.04:LTS: linux-azure, Ubuntu:18.04:LTS: linux-azure-5.3, Ubuntu:Pro:18.04:LTS: linux-azure-5.4, Ubuntu:18.04:LTS: linux-azure-edge, Ubuntu:18.04:LTS: linux-gcp, Ubuntu:18.04:LTS: linux-gcp-5.3 and 159 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: virtio_net: Fix napi_skb_cache_put warning After the commit bdacf3e34945 (&amp;#34;net: Use nested-BH locking for napi_alloc_cache.&amp;#34;) was merged, the following warning began to appear: 	 WARNING: CPU: 5 PID: 1 at net/core/skbuff.c:1451 napi_skb_cache_put+0x82/0x4b0 	  __warn+0x12f/0x340 	  napi_skb_cache_put+0x82/0x4b0 	  napi_skb_cache_put+0x82/0x4b0 	  report_bug+0x165/0x370 	  handle_bug+0x3d/0x80 	  exc_invalid_op+0x1a/0x50 	  asm_exc_invalid_op+0x1a/0x20 	  __free_old_xmit+0x1c8/0x510 	  napi_skb_cache_put+0x82/0x4b0 	  __free_old_xmit+0x1c8/0x510 	  __free_old_xmit+0x1c8/0x510 	  __pfx___free_old_xmit+0x10/0x10 The issue arises because virtio is assuming it&amp;#39;s running in NAPI context even when it&amp;#39;s not, such as in the netpoll case. To resolve this, modify virtnet_poll_tx() to only set NAPI when budget is available. Same for virtnet_poll_cleantx(), which always assumed that it was in a NAPI context.&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:Pro:18.04:LTS: linux-aws-5.4, Ubuntu:18.04:LTS: linux-azure, Ubuntu:18.04:LTS: linux-azure-5.3, Ubuntu:Pro:18.04:LTS: linux-azure-5.4, Ubuntu:18.04:LTS: linux-azure-edge, Ubuntu:18.04:LTS: linux-gcp, Ubuntu:18.04:LTS: linux-gcp-5.3 and 159 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: virtio_net: Fix napi_skb_cache_put warning After the commit bdacf3e34945 (&amp;#34;net: Use nested-BH locking for napi_alloc_cache.&amp;#34;) was merged, the following warning began to appear: 	 WARNING: CPU: 5 PID: 1 at net/core/skbuff.c:1451 napi_skb_cache_put+0x82/0x4b0 	  __warn+0x12f/0x340 	  napi_skb_cache_put+0x82/0x4b0 	  napi_skb_cache_put+0x82/0x4b0 	  report_bug+0x165/0x370 	  handle_bug+0x3d/0x80 	  exc_invalid_op+0x1a/0x50 	  asm_exc_invalid_op+0x1a/0x20 	  __free_old_xmit+0x1c8/0x510 	  napi_skb_cache_put+0x82/0x4b0 	  __free_old_xmit+0x1c8/0x510 	  __free_old_xmit+0x1c8/0x510 	  __pfx___free_old_xmit+0x10/0x10 The issue arises because virtio is assuming it&amp;#39;s running in NAPI context even when it&amp;#39;s not, such as in the netpoll case. To resolve this, modify virtnet_poll_tx() to only set NAPI when budget is available. Same for virtnet_poll_cleantx(), which always assumed that it was in a NAPI context.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ubuntu-cve-2024-43835</guid>
    </item>
    <item>
      <title>WID-SEC-W-2024-1875 — Linux Kernel: Mehrere Schwachstellen ermöglichen Denial of Service</title>
      <link>https://cve.radiocsirt.org/vuln/wid-sec-w-2024-1875</link>
      <description>&lt;p&gt;Ein lokaler Angreifer kann mehrere Schwachstellen in Linux Kernel ausnutzen, um einen Denial of Service Angriff durchzuführen oder unbekannte Auswirkungen 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 oder unbekannte Auswirkungen zu erzielen.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/wid-sec-w-2024-1875</guid>
    </item>
  </channel>
</rss>
