<?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://vulnerability.circl.lu</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>Tue, 29 Sep 2026 09:28:00 +0000</lastBuildDate>
    <item>
      <title>CVE-2024-43835 — virtio_net: Fix napi_skb_cache_put warning</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2024-43835</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Linux&lt;/p&gt;
&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;&lt;strong&gt;Affected:&lt;/strong&gt; Linux&lt;/p&gt;
&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://vulnerability.circl.lu/vuln/cve-2024-43835</guid>
    </item>
  </channel>
</rss>
