https://vulnerability.circl.lu Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Tue, 29 Sep 2026 01:09:42 +0000 https://vulnerability.circl.lu/vuln/cve-2026-53231 <p><strong>Affected:</strong> Linux</p> <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>net: phy: don&#39;t try to setup PHY-driven SFP cages when using genphy</p> <p>We don&#39;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&#39;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&#39;s therefore only run phy_sfp_probe when not using genphy.</p> <p><strong>Affected:</strong> Linux</p> <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>net: phy: don&#39;t try to setup PHY-driven SFP cages when using genphy</p> <p>We don&#39;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&#39;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&#39;s therefore only run phy_sfp_probe when not using genphy.</p> https://vulnerability.circl.lu/vuln/cve-2026-53231