<?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>Wed, 30 Sep 2026 10:00:22 +0000</lastBuildDate>
    <item>
      <title>CVE-2025-68245 — net: netpoll: fix incorrect refcount handling causing incorrect cleanup</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2025-68245</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;net: netpoll: fix incorrect refcount handling causing incorrect cleanup&lt;/p&gt;
&lt;p&gt;commit efa95b01da18 (&amp;#34;netpoll: fix use after free&amp;#34;) incorrectly
ignored the refcount and prematurely set dev-&amp;gt;npinfo to NULL during
netpoll cleanup, leading to improper behavior and memory leaks.&lt;/p&gt;
&lt;p&gt;Scenario causing lack of proper cleanup:&lt;/p&gt;
&lt;p&gt;1) A netpoll is associated with a NIC (e.g., eth0) and netdev-&amp;gt;npinfo is
   allocated, and refcnt = 1
   - Keep in mind that npinfo is shared among all netpoll instances. In
     this case, there is just one.&lt;/p&gt;
&lt;p&gt;2) Another netpoll is also associated with the same NIC and
   npinfo-&amp;gt;refcnt += 1.
   - Now dev-&amp;gt;npinfo-&amp;gt;refcnt = 2;
   - There is just one npinfo associated to the netdev.&lt;/p&gt;
&lt;p&gt;3) When the first netpolls goes to clean up:
   - The first cleanup succeeds and clears np-&amp;gt;dev-&amp;gt;npinfo, ignoring
     refcnt.
     - It basically calls `RCU_INIT_POINTER(np-&amp;gt;dev-&amp;gt;npinfo, NULL);`
   - Set dev-&amp;gt;npinfo = NULL, without proper cleanup
   - No -&amp;gt;ndo_netpoll_cleanup() is either called&lt;/p&gt;
&lt;p&gt;4) Now the second target tries to clean up
   - The second cleanup fails because np-&amp;gt;dev-&amp;gt;npinfo is already NULL.
     * In this case, ops-&amp;gt;ndo_netpoll_cleanup() was never called, and
       the skb pool is not cleaned as well (for the second netpoll
       instance)
  - This leaks npinfo and skbpool skbs, which is clearly reported by
    kmemleak.&lt;/p&gt;
&lt;p&gt;Revert commit efa95b01da18 (&amp;#34;netpoll: fix use after free&amp;#34;) and adds
clarifying comm…&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;net: netpoll: fix incorrect refcount handling causing incorrect cleanup&lt;/p&gt;
&lt;p&gt;commit efa95b01da18 (&amp;#34;netpoll: fix use after free&amp;#34;) incorrectly
ignored the refcount and prematurely set dev-&amp;gt;npinfo to NULL during
netpoll cleanup, leading to improper behavior and memory leaks.&lt;/p&gt;
&lt;p&gt;Scenario causing lack of proper cleanup:&lt;/p&gt;
&lt;p&gt;1) A netpoll is associated with a NIC (e.g., eth0) and netdev-&amp;gt;npinfo is
   allocated, and refcnt = 1
   - Keep in mind that npinfo is shared among all netpoll instances. In
     this case, there is just one.&lt;/p&gt;
&lt;p&gt;2) Another netpoll is also associated with the same NIC and
   npinfo-&amp;gt;refcnt += 1.
   - Now dev-&amp;gt;npinfo-&amp;gt;refcnt = 2;
   - There is just one npinfo associated to the netdev.&lt;/p&gt;
&lt;p&gt;3) When the first netpolls goes to clean up:
   - The first cleanup succeeds and clears np-&amp;gt;dev-&amp;gt;npinfo, ignoring
     refcnt.
     - It basically calls `RCU_INIT_POINTER(np-&amp;gt;dev-&amp;gt;npinfo, NULL);`
   - Set dev-&amp;gt;npinfo = NULL, without proper cleanup
   - No -&amp;gt;ndo_netpoll_cleanup() is either called&lt;/p&gt;
&lt;p&gt;4) Now the second target tries to clean up
   - The second cleanup fails because np-&amp;gt;dev-&amp;gt;npinfo is already NULL.
     * In this case, ops-&amp;gt;ndo_netpoll_cleanup() was never called, and
       the skb pool is not cleaned as well (for the second netpoll
       instance)
  - This leaks npinfo and skbpool skbs, which is clearly reported by
    kmemleak.&lt;/p&gt;
&lt;p&gt;Revert commit efa95b01da18 (&amp;#34;netpoll: fix use after free&amp;#34;) and adds
clarifying comm…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2025-68245</guid>
    </item>
  </channel>
</rss>
