<?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 14:36:38 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-74623 — net: atlantic: free stranded TX buffers on ring deinit</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2026-74623</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: atlantic: free stranded TX buffers on ring deinit&lt;/p&gt;
&lt;p&gt;aq_vec_deinit() drains the TX rings with a single aq_ring_tx_clean()
call, which frees at most AQ_CFG_TX_CLEAN_BUDGET (256) descriptors and
stops at hw_head, which no longer moves once aq_vec_stop() has stopped
the hardware and NAPI. Completed descriptors beyond the budget and
everything still posted in [hw_head, sw_tail) keep their skb or
xdp_frame when the interface goes down: aq_vec_ring_free() then frees
the buffer ring and the references are lost for good.&lt;/p&gt;
&lt;p&gt;Today this is a silent memory leak on every interface down under
TX/XDP_TX load. With the conversion of the RX path to page_pool posted
for net-next it becomes much more visible: XDP_TX frames carry fragment
references on the RX ring&amp;#39;s page_pool, so a single stranded frame keeps
the pool&amp;#39;s inflight count above zero forever. page_pool_destroy() then
never completes, the pool is leaked together with its pages, and
&amp;#34;page_pool_release_retry() stalled pool shutdown&amp;#34; is warned every 60
seconds from that point on, on every ifdown, XDP detach or ring resize
under XDP_TX load.&lt;/p&gt;
&lt;p&gt;Bring back aq_ring_tx_deinit() as it was before the removal and use it
for teardown again, with one extension: TX rings can hold xdp_frames
nowadays, so release those too. They are returned with
xdp_return_frame() since this runs in process 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;net: atlantic: free stranded TX buffers on ring deinit&lt;/p&gt;
&lt;p&gt;aq_vec_deinit() drains the TX rings with a single aq_ring_tx_clean()
call, which frees at most AQ_CFG_TX_CLEAN_BUDGET (256) descriptors and
stops at hw_head, which no longer moves once aq_vec_stop() has stopped
the hardware and NAPI. Completed descriptors beyond the budget and
everything still posted in [hw_head, sw_tail) keep their skb or
xdp_frame when the interface goes down: aq_vec_ring_free() then frees
the buffer ring and the references are lost for good.&lt;/p&gt;
&lt;p&gt;Today this is a silent memory leak on every interface down under
TX/XDP_TX load. With the conversion of the RX path to page_pool posted
for net-next it becomes much more visible: XDP_TX frames carry fragment
references on the RX ring&amp;#39;s page_pool, so a single stranded frame keeps
the pool&amp;#39;s inflight count above zero forever. page_pool_destroy() then
never completes, the pool is leaked together with its pages, and
&amp;#34;page_pool_release_retry() stalled pool shutdown&amp;#34; is warned every 60
seconds from that point on, on every ifdown, XDP detach or ring resize
under XDP_TX load.&lt;/p&gt;
&lt;p&gt;Bring back aq_ring_tx_deinit() as it was before the removal and use it
for teardown again, with one extension: TX rings can hold xdp_frames
nowadays, so release those too. They are returned with
xdp_return_frame() since this runs in process context.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2026-74623</guid>
    </item>
  </channel>
</rss>
