<?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-29T12:07:16.142947+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-2026-53231</id>
    <title>CVE-2026-53231 — net: phy: don't try to setup PHY-driven SFP cages when using genphy</title>
    <updated>2026-09-29T12:07:16.761273+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: phy: don't try to setup PHY-driven SFP cages when using genphy</p>
<p>We don't have support for PHY-driver SFP cages with the genphy code.</p>
<p>On top of that, it was found by sashiko that running
sfp_bus_add_upstream() for genphy deadlocks, as for genphy the PHY
probing runs under RTNL, which isn't the case for non-genphy drivers.</p>
<p>This problem was reproduced, and does lead to a deadlock on RTNL.</p>
<p>Before the blamed commit, the phy_sfp_probe() call was made by
individual PHY drivers, so there was no way to get to the SFP probing
path when using genphy.</p>
<p>Let's therefore only run phy_sfp_probe when not using genphy.</p></div>
    </content>
    <link href="https://vulnerability.circl.lu/vuln/cve-2026-53231"/>
  </entry>
</feed>
