<?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 01:55:57 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-43371 — net: macb: Shuffle the tx ring before enabling tx</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2026-43371</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: macb: Shuffle the tx ring before enabling tx&lt;/p&gt;
&lt;p&gt;Quanyang observed that when using an NFS rootfs on an AMD ZynqMp board,
the rootfs may take an extended time to recover after a suspend.
Upon investigation, it was determined that the issue originates from a
problem in the macb driver.&lt;/p&gt;
&lt;p&gt;According to the Zynq UltraScale TRM [1], when transmit is disabled,
the transmit buffer queue pointer resets to point to the address
specified by the transmit buffer queue base address register.&lt;/p&gt;
&lt;p&gt;In the current implementation, the code merely resets `queue-&amp;gt;tx_head`
and `queue-&amp;gt;tx_tail` to &amp;#39;0&amp;#39;. This approach presents several issues:&lt;/p&gt;
&lt;p&gt;- Packets already queued in the tx ring are silently lost,
  leading to memory leaks since the associated skbs cannot be released.&lt;/p&gt;
&lt;p&gt;- Concurrent write access to `queue-&amp;gt;tx_head` and `queue-&amp;gt;tx_tail` may
  occur from `macb_tx_poll()` or `macb_start_xmit()` when these values
  are reset to &amp;#39;0&amp;#39;.&lt;/p&gt;
&lt;p&gt;- The transmission may become stuck on a packet that has already been sent
  out, with its &amp;#39;TX_USED&amp;#39; bit set, but has not yet been processed. However,
  due to the manipulation of &amp;#39;queue-&amp;gt;tx_head&amp;#39; and &amp;#39;queue-&amp;gt;tx_tail&amp;#39;,
  `macb_tx_poll()` incorrectly assumes there are no packets to handle
  because `queue-&amp;gt;tx_head == queue-&amp;gt;tx_tail`. This issue is only resolved
  when a new packet is placed at this position. This is the root cause of
  the prolonged recovery time observed for the NFS root filesystem.&lt;/p&gt;
&lt;p&gt;To r…&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: macb: Shuffle the tx ring before enabling tx&lt;/p&gt;
&lt;p&gt;Quanyang observed that when using an NFS rootfs on an AMD ZynqMp board,
the rootfs may take an extended time to recover after a suspend.
Upon investigation, it was determined that the issue originates from a
problem in the macb driver.&lt;/p&gt;
&lt;p&gt;According to the Zynq UltraScale TRM [1], when transmit is disabled,
the transmit buffer queue pointer resets to point to the address
specified by the transmit buffer queue base address register.&lt;/p&gt;
&lt;p&gt;In the current implementation, the code merely resets `queue-&amp;gt;tx_head`
and `queue-&amp;gt;tx_tail` to &amp;#39;0&amp;#39;. This approach presents several issues:&lt;/p&gt;
&lt;p&gt;- Packets already queued in the tx ring are silently lost,
  leading to memory leaks since the associated skbs cannot be released.&lt;/p&gt;
&lt;p&gt;- Concurrent write access to `queue-&amp;gt;tx_head` and `queue-&amp;gt;tx_tail` may
  occur from `macb_tx_poll()` or `macb_start_xmit()` when these values
  are reset to &amp;#39;0&amp;#39;.&lt;/p&gt;
&lt;p&gt;- The transmission may become stuck on a packet that has already been sent
  out, with its &amp;#39;TX_USED&amp;#39; bit set, but has not yet been processed. However,
  due to the manipulation of &amp;#39;queue-&amp;gt;tx_head&amp;#39; and &amp;#39;queue-&amp;gt;tx_tail&amp;#39;,
  `macb_tx_poll()` incorrectly assumes there are no packets to handle
  because `queue-&amp;gt;tx_head == queue-&amp;gt;tx_tail`. This issue is only resolved
  when a new packet is placed at this position. This is the root cause of
  the prolonged recovery time observed for the NFS root filesystem.&lt;/p&gt;
&lt;p&gt;To r…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2026-43371</guid>
    </item>
  </channel>
</rss>
