<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
  <id>https://vulnerability.circl.lu/rss/recent/all/10</id>
  <title>Most recent entries from all</title>
  <updated>2026-09-29T22:38:15.248206+00:00</updated>
  <author>
    <name>Vulnerability-Lookup</name>
    <email>info@circl.lu</email>
  </author>
  <link href="https://vulnerability.circl.lu" rel="alternate"/>
  <generator uri="https://lkiesow.github.io/python-feedgen" version="1.0.0">python-feedgen</generator>
  <subtitle>Contains only the most 10 recent entries.</subtitle>
  <entry>
    <id>https://vulnerability.circl.lu/vuln/cve-2025-40347</id>
    <title>CVE-2025-40347 — net: enetc: fix the deadlock of enetc_mdio_lock</title>
    <updated>2026-09-29T22:38:15.249313+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> Linux</p>
<p>In the Linux kernel, the following vulnerability has been resolved:</p>
<p>net: enetc: fix the deadlock of enetc_mdio_lock</p>
<p>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:</p>
<p>enetc_poll
  -&gt; enetc_lock_mdio
  -&gt; enetc_clean_rx_ring OR napi_complete_done
     -&gt; napi_gro_receive
        -&gt; enetc_start_xmit
           -&gt; enetc_lock_mdio
           -&gt; enetc_map_tx_buffs
           -&gt; enetc_unlock_mdio
  -&gt; enetc_unlock_mdio</p>
<p>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.</p>
<p>Currently, the deadlock is avoided by adjusting enetc_lock_mdio to prevent
recursive lock acquisition.</p></div>
    </content>
    <link href="https://vulnerability.circl.lu/vuln/cve-2025-40347"/>
  </entry>
</feed>
