<?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 22:38:14 +0000</lastBuildDate>
    <item>
      <title>CVE-2025-40347 — net: enetc: fix the deadlock of enetc_mdio_lock</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2025-40347</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: enetc: fix the deadlock of enetc_mdio_lock&lt;/p&gt;
&lt;p&gt;After applying the workaround for err050089, the LS1028A platform
experiences RCU stalls on RT kernel. This issue is caused by the
recursive acquisition of the read lock enetc_mdio_lock. Here list some
of the call stacks identified under the enetc_poll path that may lead to
a deadlock:&lt;/p&gt;
&lt;p&gt;enetc_poll
  -&amp;gt; enetc_lock_mdio
  -&amp;gt; enetc_clean_rx_ring OR napi_complete_done
     -&amp;gt; napi_gro_receive
        -&amp;gt; enetc_start_xmit
           -&amp;gt; enetc_lock_mdio
           -&amp;gt; enetc_map_tx_buffs
           -&amp;gt; enetc_unlock_mdio
  -&amp;gt; enetc_unlock_mdio&lt;/p&gt;
&lt;p&gt;After enetc_poll acquires the read lock, a higher-priority writer attempts
to acquire the lock, causing preemption. The writer detects that a
read lock is already held and is scheduled out. However, readers under
enetc_poll cannot acquire the read lock again because a writer is already
waiting, leading to a thread hang.&lt;/p&gt;
&lt;p&gt;Currently, the deadlock is avoided by adjusting enetc_lock_mdio to prevent
recursive lock acquisition.&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: enetc: fix the deadlock of enetc_mdio_lock&lt;/p&gt;
&lt;p&gt;After applying the workaround for err050089, the LS1028A platform
experiences RCU stalls on RT kernel. This issue is caused by the
recursive acquisition of the read lock enetc_mdio_lock. Here list some
of the call stacks identified under the enetc_poll path that may lead to
a deadlock:&lt;/p&gt;
&lt;p&gt;enetc_poll
  -&amp;gt; enetc_lock_mdio
  -&amp;gt; enetc_clean_rx_ring OR napi_complete_done
     -&amp;gt; napi_gro_receive
        -&amp;gt; enetc_start_xmit
           -&amp;gt; enetc_lock_mdio
           -&amp;gt; enetc_map_tx_buffs
           -&amp;gt; enetc_unlock_mdio
  -&amp;gt; enetc_unlock_mdio&lt;/p&gt;
&lt;p&gt;After enetc_poll acquires the read lock, a higher-priority writer attempts
to acquire the lock, causing preemption. The writer detects that a
read lock is already held and is scheduled out. However, readers under
enetc_poll cannot acquire the read lock again because a writer is already
waiting, leading to a thread hang.&lt;/p&gt;
&lt;p&gt;Currently, the deadlock is avoided by adjusting enetc_lock_mdio to prevent
recursive lock acquisition.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2025-40347</guid>
    </item>
  </channel>
</rss>
